Apr 25 16:04:01 192.168.122.209 [33877.973561] systemd-shutdown[1]: Syncing filesystems and block devices. Apr 25 16:04:01 192.168.122.209 [33878.099521] systemd-shutdown[1]: Sending SIGTERM to remaining processes... Apr 25 16:04:01 192.168.122.209 [33878.190314] systemd-journald[417]: Received SIGTERM from PID 1 (systemd-shutdow). Apr 25 16:04:01 192.168.122.209 [33878.256544] systemd-shutdown[1]: Sending SIGKILL to remaining processes... Apr 25 16:04:01 192.168.122.209 [33878.315418] systemd-shutdown[1]: Unmounting file systems. Apr 25 16:04:01 192.168.122.209 [33878.332643] (sd-remount)[895167]: Remounting '/' read-only with options ''. Apr 25 16:04:01 192.168.122.209 [33878.347006] EXT4-fs (dm-0): re-mounted. Opts: (null) Apr 25 16:04:02 192.168.122.209 [33878.480272] systemd-shutdown[1]: All filesystems unmounted. Apr 25 16:04:02 192.168.122.209 [33878.480826] systemd-shutdown[1]: Deactivating swaps. Apr 25 16:04:02 192.168.122.209 [33878.481406] systemd-shutdown[1]: All swaps deactivated. Apr 25 16:04:02 192.168.122.209 [33878.481897] systemd-shutdown[1]: Detaching loop devices. Apr 25 16:04:02 192.168.122.209 [33878.531333] systemd-shutdown[1]: All loop devices detached. Apr 25 16:04:02 192.168.122.209 [33878.531871] systemd-shutdown[1]: Stopping MD devices. Apr 25 16:04:02 192.168.122.209 [33878.533792] systemd-shutdown[1]: All MD devices stopped. Apr 25 16:04:02 192.168.122.209 [33878.534314] systemd-shutdown[1]: Detaching DM devices. Apr 25 16:04:02 192.168.122.209 [33878.536567] systemd-shutdown[1]: Not all DM devices detached, 1 left. Apr 25 16:04:02 192.168.122.209 [33878.537178] systemd-shutdown[1]: Cannot finalize remaining DM devices, continuing. Apr 25 16:04:02 192.168.122.209 [33878.695743] systemd-shutdown[1]: Successfully changed into root pivot. Apr 25 16:04:02 192.168.122.209 [33878.696366] systemd-shutdown[1]: Returning to initrd... Apr 25 16:04:02 192.168.122.209 [33878.736030] shutdown[1]: Syncing filesystems and block devices. Apr 25 16:04:02 192.168.122.209 [33878.741876] shutdown[1]: Sending SIGTERM to remaining processes... Apr 25 16:04:02 192.168.122.209 [33878.784356] shutdown[1]: Sending SIGKILL to remaining processes... Apr 25 16:04:02 192.168.122.209 [33878.837517] shutdown[1]: Unmounting file systems. Apr 25 16:04:02 192.168.122.209 [33878.845408] (sd-umoun[895175]: Unmounting '/oldroot/sys/kernel/config'. Apr 25 16:04:02 192.168.122.209 [33878.874751] (sd-umoun[895176]: Unmounting '/oldroot/sys/fs/fuse/connections'. Apr 25 16:04:02 192.168.122.209 [33878.890365] (sd-umoun[895177]: Unmounting '/oldroot/sys/kernel/tracing'. Apr 25 16:04:02 192.168.122.209 [33878.906173] (sd-umoun[895178]: Unmounting '/oldroot/dev/hugepages'. Apr 25 16:04:02 192.168.122.209 [33878.924069] (sd-umoun[895179]: Unmounting '/oldroot/dev/mqueue'. Apr 25 16:04:02 192.168.122.209 [33878.936261] (sd-umoun[895180]: Unmounting '/oldroot/sys/kernel/debug'. Apr 25 16:04:02 192.168.122.209 [33878.945719] (sd-umoun[895181]: Unmounting '/oldroot/sys/fs/bpf'. Apr 25 16:04:02 192.168.122.209 [33878.952953] (sd-umoun[895182]: Unmounting '/oldroot/sys/fs/pstore'. Apr 25 16:04:02 192.168.122.209 [33878.963079] (sd-umoun[895183]: Unmounting '/oldroot/sys/fs/cgroup'. Apr 25 16:04:02 192.168.122.209 [33878.972661] (sd-umoun[895184]: Unmounting '/oldroot/run/lock'. Apr 25 16:04:02 192.168.122.209 [33878.986006] (sd-umoun[895185]: Unmounting '/oldroot/dev/shm'. Apr 25 16:04:02 192.168.122.209 [33878.995839] (sd-umoun[895186]: Unmounting '/oldroot/sys/kernel/security'. Apr 25 16:04:02 192.168.122.209 [33879.007025] (sd-umoun[895187]: Unmounting '/oldroot'. Apr 25 16:04:02 192.168.122.209 [33879.007837] (sd-umoun[895187]: Failed to unmount /oldroot: Device or resource busy Apr 25 16:04:02 192.168.122.209 [33879.016670] (sd-umoun[895188]: Unmounting '/oldroot/run'. Apr 25 16:04:02 192.168.122.209 [33879.027642] (sd-umoun[895189]: Unmounting '/oldroot/dev/pts'. Apr 25 16:04:02 192.168.122.209 [33879.039600] (sd-umoun[895190]: Unmounting '/oldroot/dev'. Apr 25 16:04:02 192.168.122.209 [33879.049679] (sd-umoun[895191]: Unmounting '/oldroot/proc'. Apr 25 16:04:02 192.168.122.209 [33879.063140] (sd-umoun[895192]: Unmounting '/oldroot/sys'. Apr 25 16:04:02 192.168.122.209 [33879.074949] (sd-umoun[895193]: Unmounting '/oldroot'. Apr 25 16:04:03 192.168.122.209 [33880.416335] shutdown[1]: All filesystems unmounted. Apr 25 16:04:03 192.168.122.209 [33880.416852] shutdown[1]: Deactivating swaps. Apr 25 16:04:03 192.168.122.209 [33880.417357] shutdown[1]: All swaps deactivated. Apr 25 16:04:03 192.168.122.209 [33880.417780] shutdown[1]: Detaching loop devices. Apr 25 16:04:03 192.168.122.209 [33880.428417] shutdown[1]: All loop devices detached. Apr 25 16:04:03 192.168.122.209 [33880.428896] shutdown[1]: Stopping MD devices. Apr 25 16:04:03 192.168.122.209 [33880.429778] shutdown[1]: All MD devices stopped. Apr 25 16:04:03 192.168.122.209 [33880.430216] shutdown[1]: Detaching DM devices. Apr 25 16:04:03 192.168.122.209 [33880.432522] shutdown[1]: Detaching DM /dev/dm-0 (253:0). Apr 25 16:04:04 192.168.122.209 [33880.484244] shutdown[1]: All DM devices detached. Apr 25 16:04:04 192.168.122.209 [33880.484709] shutdown[1]: All filesystems, swaps, loop devices, MD devices and DM devices detached. Apr 25 16:04:04 192.168.122.209 [33880.580914] shutdown[1]: Syncing filesystems and block devices. Apr 25 16:04:04 192.168.122.209 [33880.598983] shutdown[1]: Rebooting. Apr 25 16:04:04 192.168.122.209 [33880.599520] kvm-guest: Unregister pv shared memory for cpu 1 Apr 25 16:04:04 192.168.122.209 [33880.599586] kvm-guest: Unregister pv shared memory for cpu 2 Apr 25 16:04:04 192.168.122.209 [33880.599606] kvm-guest: Unregister pv shared memory for cpu 0 Apr 25 16:04:04 192.168.122.209 [33880.612277] kvm-guest: Unregister pv shared memory for cpu 3 Apr 25 16:04:04 192.168.122.209 [33880.612955] kvm: exiting hardware virtualization Apr 25 16:04:04 192.168.122.209 [33881.110945] reboot: Restarting system Apr 25 16:04:04 192.168.122.209 [33881.112038] reboot: machine restart Apr 25 16:04:04 192.168.122.209 [33881.115109] ACPI MEMORY or I/O RESET_REG. Apr 25 16:04:28 192.168.122.209 [ 5.783219] shpchp 0000:07:00.0: pci_hp_register failed with error -16 Apr 25 16:04:28 192.168.122.209 [ 5.783841] shpchp 0000:07:00.0: Slot initialization failed Apr 26 01:24:49 192.168.122.209 [33640.106573] [tempesta fw] ERROR: the required entry is not found: 'incr2' Apr 26 01:24:49 192.168.122.209 [33640.108640] [tempesta fw] ERROR: configuration parsing error Apr 26 01:24:50 192.168.122.209 [33640.474776] [tempesta fw] ERROR: configuration parsing error: [33640.474776] 1: single; repeat; repeat; err; repeat; [33640.474776] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 01:24:50 192.168.122.209 [33640.974821] [tempesta fw] ERROR: the value -16 is out of range: [10, 20] Apr 26 01:24:50 192.168.122.209 [33640.976753] [tempesta fw] ERROR: can't parse integer Apr 26 01:24:50 192.168.122.209 [33640.976761] [tempesta fw] ERROR: configuration parsing error: [33640.976761] 1: val -16; [33640.976761] ^^^^^^^^ Apr 26 01:24:50 192.168.122.209 [33640.994863] [tempesta fw] ERROR: the value 0 is out of range: [10, 20] Apr 26 01:24:50 192.168.122.209 [33640.996711] [tempesta fw] ERROR: can't parse integer Apr 26 01:24:50 192.168.122.209 [33640.996719] [tempesta fw] ERROR: configuration parsing error: [33640.996719] 1: val 0; [33640.996719] ^^^^^^ Apr 26 01:24:50 192.168.122.209 [33641.018853] [tempesta fw] ERROR: the value 2 is out of range: [10, 20] Apr 26 01:24:50 192.168.122.209 [33641.020699] [tempesta fw] ERROR: can't parse integer Apr 26 01:24:50 192.168.122.209 [33641.020707] [tempesta fw] ERROR: configuration parsing error: [33641.020707] 1: val 2; [33641.020707] ^^^^^^ Apr 26 01:24:50 192.168.122.209 [33641.046969] [tempesta fw] ERROR: the value of 9 is not a multiple of 2 Apr 26 01:24:50 192.168.122.209 [33641.048838] [tempesta fw] ERROR: the value 9 is out of range: [10, 20] Apr 26 01:24:50 192.168.122.209 [33641.050713] [tempesta fw] ERROR: can't parse integer Apr 26 01:24:50 192.168.122.209 [33641.050721] [tempesta fw] ERROR: configuration parsing error: [33641.050721] 1: val 9; [33641.050721] ^^^^^^ Apr 26 01:24:50 192.168.122.209 [33641.098808] [tempesta fw] ERROR: the value of 15 is not a multiple of 2 Apr 26 01:24:50 192.168.122.209 [33641.100676] [tempesta fw] ERROR: can't parse integer Apr 26 01:24:50 192.168.122.209 [33641.100684] [tempesta fw] ERROR: configuration parsing error: [33641.100684] 1: val 15; [33641.100684] ^^^^^^^ Apr 26 01:24:50 192.168.122.209 [33641.170860] [tempesta fw] ERROR: the value of 21 is not a multiple of 2 Apr 26 01:24:50 192.168.122.209 [33641.172748] [tempesta fw] ERROR: the value 21 is out of range: [10, 20] Apr 26 01:24:50 192.168.122.209 [33641.174628] [tempesta fw] ERROR: can't parse integer Apr 26 01:24:50 192.168.122.209 [33641.174637] [tempesta fw] ERROR: configuration parsing error: [33641.174637] 1: val 21; [33641.174637] ^^^^^^^ Apr 26 01:24:50 192.168.122.209 [33641.206838] [tempesta fw] ERROR: the value 65536 is out of range: [10, 20] Apr 26 01:24:50 192.168.122.209 [33641.208793] [tempesta fw] ERROR: can't parse integer Apr 26 01:24:50 192.168.122.209 [33641.208801] [tempesta fw] ERROR: configuration parsing error: [33641.208801] 1: val 65536; [33641.208801] ^^^^^^^^^^ Apr 26 01:24:51 192.168.122.209 [33641.322706] [tempesta fw] ERROR: Zero interval left bound in '7-' Apr 26 01:24:51 192.168.122.209 [33641.324493] [tempesta fw] ERROR: Bad interval delimiter Apr 26 01:24:51 192.168.122.209 [33641.406825] [tempesta fw] ERROR: no value specified Apr 26 01:24:51 192.168.122.209 [33641.408278] [tempesta fw] ERROR: configuration parsing error: [33641.408278] 1: str; [33641.408278] ^^^^ Apr 26 01:24:51 192.168.122.209 [33641.434780] [tempesta fw] ERROR: no value specified Apr 26 01:24:51 192.168.122.209 [33641.436184] [tempesta fw] ERROR: configuration parsing error: [33641.436184] 1: str ; [33641.436184] ^^^^^ Apr 26 01:24:51 192.168.122.209 [33641.498799] [tempesta fw] ERROR: the string length (1) is out of valid range (2, 8): '1' Apr 26 01:24:51 192.168.122.209 [33641.501051] [tempesta fw] ERROR: configuration parsing error: [33641.501051] 1: str 1; [33641.501051] ^^^^^^ Apr 26 01:24:51 192.168.122.209 [33641.658824] [tempesta fw] ERROR: the string length (9) is out of valid range (2, 8): '123456789' Apr 26 01:24:51 192.168.122.209 [33641.661295] [tempesta fw] ERROR: configuration parsing error: [33641.661295] 1: str 123456789; [33641.661295] ^^^^^^^^^^^^^^ Apr 26 01:24:51 192.168.122.209 [33641.782819] [tempesta fw] ERROR: invalid characters found: '4z2' Apr 26 01:24:51 192.168.122.209 [33641.784536] [tempesta fw] ERROR: configuration parsing error: [33641.784536] 1: hex 4z2; [33641.784536] ^^^^^^^^ Apr 26 01:24:51 192.168.122.209 [33641.814805] [tempesta fw] ERROR: invalid characters found: 'abc!' Apr 26 01:24:51 192.168.122.209 [33641.816536] [tempesta fw] ERROR: configuration parsing error: [33641.816536] 1: hex abc!; [33641.816536] ^^^^^^^^^ Apr 26 01:24:51 192.168.122.209 [33641.842880] [tempesta fw] ERROR: invalid characters found: '-42' Apr 26 01:24:51 192.168.122.209 [33641.844582] [tempesta fw] ERROR: configuration parsing error: [33641.844582] 1: hex -42; [33641.844582] ^^^^^^^^ Apr 26 01:26:49 192.168.122.209 [33759.554645] kobject_add_internal failed for test with -EEXIST, don't try to register things with the same name in the same directory. Apr 26 01:26:49 192.168.122.209 [33759.556057] [tempesta fw] ERROR: Class creation failed for test Apr 26 01:33:45 192.168.122.209 [34175.356540] [tdb] Start Tempesta DB Apr 26 01:33:45 192.168.122.209 [34175.574934] net_ratelimit: 1320 callbacks suppressed Apr 26 01:33:45 192.168.122.209 [34175.574937] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:33:46 192.168.122.209 [34176.475194] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34176.475194] Maybe that's fine, but it's worth checking the [34176.475194] config - if there is no relations between the [34176.475194] names, then host name confusion attack is possible. Apr 26 01:33:46 192.168.122.209 [34176.539647] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [34176.539647] Maybe that's fine, but it's worth checking the [34176.539647] config - if there is no relations between the [34176.539647] names, then host name confusion attack is possible. Apr 26 01:33:46 192.168.122.209 [34176.633668] [tempesta fw] Configuration processing is completed. Apr 26 01:33:46 192.168.122.209 [34176.697812] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:33:46 192.168.122.209 [34176.744343] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:33:46 192.168.122.209 [34176.787009] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:33:46 192.168.122.209 [34176.937712] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:33:46 192.168.122.209 [34176.993648] [tempesta fw] Tempesta FW is ready Apr 26 01:33:47 192.168.122.209 [34177.709075] device enp1s0 entered promiscuous mode Apr 26 01:33:47 192.168.122.209 [34177.854259] device enp1s0 left promiscuous mode Apr 26 01:33:47 192.168.122.209 [34177.876612] device enp1s0 entered promiscuous mode Apr 26 01:33:47 192.168.122.209 [34177.965891] device enp1s0 left promiscuous mode Apr 26 01:33:48 192.168.122.209 [34178.516155] [tdb] Close table 'client0.tdb' Apr 26 01:33:48 192.168.122.209 [34178.702250] [tdb] Close table 'sessions0.tdb' Apr 26 01:33:48 192.168.122.209 [34178.988544] [tdb] Close table 'filter0.tdb' Apr 26 01:33:48 192.168.122.209 [34178.988992] [tempesta fw] modules are stopped Apr 26 01:33:48 192.168.122.209 [34179.195495] [tempesta fw] exiting... Apr 26 01:33:49 192.168.122.209 [34179.342148] [tdb] Shutdown Tempesta DB Apr 26 01:33:49 192.168.122.209 [34179.572035] End test: tls.test_tls_tickets.TlsVhostConfusionDfltVhost.test Apr 26 01:33:49 192.168.122.209 [34179.581482] Start test: tls.test_tls_tickets.TlsVhostConfusionDfltCertsWithUnknown.test Apr 26 01:33:50 192.168.122.209 [34180.813226] [tdb] Start Tempesta DB Apr 26 01:33:50 192.168.122.209 [34181.014596] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:33:51 192.168.122.209 [34181.979017] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34181.979017] Maybe that's fine, but it's worth checking the [34181.979017] config - if there is no relations between the [34181.979017] names, then host name confusion attack is possible. Apr 26 01:33:51 192.168.122.209 [34182.109833] [tempesta fw] Configuration processing is completed. Apr 26 01:33:51 192.168.122.209 [34182.166390] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:33:51 192.168.122.209 [34182.196988] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:33:52 192.168.122.209 [34182.237123] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:33:52 192.168.122.209 [34182.349788] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:33:52 192.168.122.209 [34182.393700] [tempesta fw] Tempesta FW is ready Apr 26 01:33:52 192.168.122.209 [34182.530723] device enp1s0 entered promiscuous mode Apr 26 01:33:52 192.168.122.209 [34182.638032] device enp1s0 left promiscuous mode Apr 26 01:33:52 192.168.122.209 [34182.664463] device enp1s0 entered promiscuous mode Apr 26 01:33:52 192.168.122.209 [34182.754195] device enp1s0 left promiscuous mode Apr 26 01:33:53 192.168.122.209 [34183.240928] [tdb] Close table 'client0.tdb' Apr 26 01:33:53 192.168.122.209 [34183.429926] [tdb] Close table 'sessions0.tdb' Apr 26 01:33:53 192.168.122.209 [34183.682670] [tdb] Close table 'filter0.tdb' Apr 26 01:33:53 192.168.122.209 [34183.683103] [tempesta fw] modules are stopped Apr 26 01:33:53 192.168.122.209 [34183.938408] [tempesta fw] exiting... Apr 26 01:33:53 192.168.122.209 [34184.108188] [tdb] Shutdown Tempesta DB Apr 26 01:33:54 192.168.122.209 [34184.358468] End test: tls.test_tls_tickets.TlsVhostConfusionDfltCertsWithUnknown.test Apr 26 01:33:54 192.168.122.209 [34184.381127] Start test: tls.test_tls_tickets.TlsVhostConfusionDfltCerts.test Apr 26 01:33:55 192.168.122.209 [34185.528269] [tdb] Start Tempesta DB Apr 26 01:33:55 192.168.122.209 [34185.691393] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:33:56 192.168.122.209 [34186.703632] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [34186.703632] Maybe that's fine, but it's worth checking the [34186.703632] config - if there is no relations between the [34186.703632] names, then host name confusion attack is possible. Apr 26 01:33:56 192.168.122.209 [34186.731662] [tempesta fw] Warning: Vhost tempesta.com doesn't have certificate with matching SAN/CN. [34186.731662] Maybe that's fine, but it's worth checking the [34186.731662] config - if there is no relations between the [34186.731662] names, then host name confusion attack is possible. Apr 26 01:33:56 192.168.122.209 [34186.797916] [tempesta fw] Configuration processing is completed. Apr 26 01:33:56 192.168.122.209 [34186.855253] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:33:56 192.168.122.209 [34186.887415] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:33:56 192.168.122.209 [34186.915803] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:33:56 192.168.122.209 [34186.993828] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:33:56 192.168.122.209 [34187.049762] [tempesta fw] Tempesta FW is ready Apr 26 01:33:56 192.168.122.209 [34187.192180] device enp1s0 entered promiscuous mode Apr 26 01:33:57 192.168.122.209 [34187.298140] device enp1s0 left promiscuous mode Apr 26 01:33:57 192.168.122.209 [34187.324578] device enp1s0 entered promiscuous mode Apr 26 01:33:57 192.168.122.209 [34187.414102] device enp1s0 left promiscuous mode Apr 26 01:33:57 192.168.122.209 [34187.928031] [tdb] Close table 'client0.tdb' Apr 26 01:33:57 192.168.122.209 [34188.114796] [tdb] Close table 'sessions0.tdb' Apr 26 01:33:58 192.168.122.209 [34188.338198] [tdb] Close table 'filter0.tdb' Apr 26 01:33:58 192.168.122.209 [34188.338638] [tempesta fw] modules are stopped Apr 26 01:33:58 192.168.122.209 [34188.593860] [tempesta fw] exiting... Apr 26 01:33:58 192.168.122.209 [34188.725351] [tdb] Shutdown Tempesta DB Apr 26 01:33:58 192.168.122.209 [34188.939330] End test: tls.test_tls_tickets.TlsVhostConfusionDfltCerts.test Apr 26 01:33:58 192.168.122.209 [34188.952625] Start test: tls.test_tls_tickets.TlsVhostConfusion.test Apr 26 01:33:59 192.168.122.209 [34190.159525] [tdb] Start Tempesta DB Apr 26 01:34:00 192.168.122.209 [34190.325359] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:34:01 192.168.122.209 [34191.343852] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [34191.343852] Maybe that's fine, but it's worth checking the [34191.343852] config - if there is no relations between the [34191.343852] names, then host name confusion attack is possible. Apr 26 01:34:01 192.168.122.209 [34191.371623] [tempesta fw] Warning: Vhost tempesta.com doesn't have certificate with matching SAN/CN. [34191.371623] Maybe that's fine, but it's worth checking the [34191.371623] config - if there is no relations between the [34191.371623] names, then host name confusion attack is possible. Apr 26 01:34:01 192.168.122.209 [34191.445947] [tempesta fw] Configuration processing is completed. Apr 26 01:34:01 192.168.122.209 [34191.504109] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:34:01 192.168.122.209 [34191.532234] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:34:01 192.168.122.209 [34191.558768] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:34:01 192.168.122.209 [34191.649878] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:34:01 192.168.122.209 [34191.689812] [tempesta fw] Tempesta FW is ready Apr 26 01:34:01 192.168.122.209 [34191.831540] device enp1s0 entered promiscuous mode Apr 26 01:34:01 192.168.122.209 [34191.930112] device enp1s0 left promiscuous mode Apr 26 01:34:01 192.168.122.209 [34191.945036] device enp1s0 entered promiscuous mode Apr 26 01:34:01 192.168.122.209 [34192.026130] device enp1s0 left promiscuous mode Apr 26 01:34:02 192.168.122.209 [34192.552511] [tdb] Close table 'client0.tdb' Apr 26 01:34:02 192.168.122.209 [34192.741715] [tdb] Close table 'sessions0.tdb' Apr 26 01:34:02 192.168.122.209 [34192.970069] [tdb] Close table 'filter0.tdb' Apr 26 01:34:02 192.168.122.209 [34192.970504] [tempesta fw] modules are stopped Apr 26 01:34:02 192.168.122.209 [34193.182856] [tempesta fw] exiting... Apr 26 01:34:03 192.168.122.209 [34193.304728] [tdb] Shutdown Tempesta DB Apr 26 01:34:03 192.168.122.209 [34193.529949] End test: tls.test_tls_tickets.TlsVhostConfusion.test Apr 26 01:34:03 192.168.122.209 [34193.541991] Start test: tls.test_tls_tickets.TlsTicketTest.test_no_ticket_support Apr 26 01:34:04 192.168.122.209 [34194.660522] [tdb] Start Tempesta DB Apr 26 01:34:04 192.168.122.209 [34194.803587] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:34:05 192.168.122.209 [34195.442472] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34195.442472] Maybe that's fine, but it's worth checking the [34195.442472] config - if there is no relations between the [34195.442472] names, then host name confusion attack is possible. Apr 26 01:34:05 192.168.122.209 [34195.553966] [tempesta fw] Configuration processing is completed. Apr 26 01:34:05 192.168.122.209 [34195.601560] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:34:05 192.168.122.209 [34195.630478] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:34:05 192.168.122.209 [34195.657035] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:34:05 192.168.122.209 [34195.701936] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:34:05 192.168.122.209 [34195.749882] [tempesta fw] Tempesta FW is ready Apr 26 01:34:05 192.168.122.209 [34195.885922] device enp1s0 entered promiscuous mode Apr 26 01:34:05 192.168.122.209 [34195.990189] device enp1s0 left promiscuous mode Apr 26 01:34:06 192.168.122.209 [34196.413791] [tdb] Close table 'client0.tdb' Apr 26 01:34:06 192.168.122.209 [34196.608614] [tdb] Close table 'sessions0.tdb' Apr 26 01:34:06 192.168.122.209 [34196.852065] [tdb] Close table 'filter0.tdb' Apr 26 01:34:06 192.168.122.209 [34196.852503] [tempesta fw] modules are stopped Apr 26 01:34:06 192.168.122.209 [34197.086269] [tempesta fw] exiting... Apr 26 01:34:07 192.168.122.209 [34197.256569] [tdb] Shutdown Tempesta DB Apr 26 01:34:07 192.168.122.209 [34197.487282] End test: tls.test_tls_tickets.TlsTicketTest.test_no_ticket_support Apr 26 01:34:07 192.168.122.209 [34197.507485] Start test: tls.test_tls_tickets.TlsTicketTest.test_invalid_ticket Apr 26 01:34:08 192.168.122.209 [34198.669899] [tdb] Start Tempesta DB Apr 26 01:34:08 192.168.122.209 [34198.824448] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:34:09 192.168.122.209 [34199.603362] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34199.603362] Maybe that's fine, but it's worth checking the [34199.603362] config - if there is no relations between the [34199.603362] names, then host name confusion attack is possible. Apr 26 01:34:09 192.168.122.209 [34199.718051] [tempesta fw] Configuration processing is completed. Apr 26 01:34:09 192.168.122.209 [34199.774165] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:34:09 192.168.122.209 [34199.811916] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:34:09 192.168.122.209 [34199.841289] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:34:09 192.168.122.209 [34199.893995] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:34:09 192.168.122.209 [34199.933942] [tempesta fw] Tempesta FW is ready Apr 26 01:34:09 192.168.122.209 [34200.069222] device enp1s0 entered promiscuous mode Apr 26 01:34:09 192.168.122.209 [34200.170187] device enp1s0 left promiscuous mode Apr 26 01:34:09 192.168.122.209 [34200.200947] device enp1s0 entered promiscuous mode Apr 26 01:34:10 192.168.122.209 [34200.252897] [tempesta tls] Warning: AEAD decryption failed while ticket decryption: -74 Apr 26 01:34:10 192.168.122.209 [34200.306496] device enp1s0 left promiscuous mode Apr 26 01:34:10 192.168.122.209 [34200.753278] [tdb] Close table 'client0.tdb' Apr 26 01:34:10 192.168.122.209 [34200.943490] [tdb] Close table 'sessions0.tdb' Apr 26 01:34:10 192.168.122.209 [34201.194852] [tdb] Close table 'filter0.tdb' Apr 26 01:34:10 192.168.122.209 [34201.195283] [tempesta fw] modules are stopped Apr 26 01:34:11 192.168.122.209 [34201.442205] [tempesta fw] exiting... Apr 26 01:34:11 192.168.122.209 [34201.603508] [tdb] Shutdown Tempesta DB Apr 26 01:34:11 192.168.122.209 [34201.833612] End test: tls.test_tls_tickets.TlsTicketTest.test_invalid_ticket Apr 26 01:34:11 192.168.122.209 [34201.843907] Start test: tls.test_tls_tickets.TlsTicketTest.test_empty_ticket Apr 26 01:34:12 192.168.122.209 [34202.972747] [tdb] Start Tempesta DB Apr 26 01:34:12 192.168.122.209 [34203.123432] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:34:13 192.168.122.209 [34203.842693] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34203.842693] Maybe that's fine, but it's worth checking the [34203.842693] config - if there is no relations between the [34203.842693] names, then host name confusion attack is possible. Apr 26 01:34:13 192.168.122.209 [34203.958119] [tempesta fw] Configuration processing is completed. Apr 26 01:34:13 192.168.122.209 [34204.013963] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:34:13 192.168.122.209 [34204.045957] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:34:13 192.168.122.209 [34204.074029] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:34:13 192.168.122.209 [34204.113978] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:34:13 192.168.122.209 [34204.153991] [tempesta fw] Tempesta FW is ready Apr 26 01:34:14 192.168.122.209 [34204.299196] device enp1s0 entered promiscuous mode Apr 26 01:34:14 192.168.122.209 [34204.394254] device enp1s0 left promiscuous mode Apr 26 01:34:14 192.168.122.209 [34204.417241] device enp1s0 entered promiscuous mode Apr 26 01:34:14 192.168.122.209 [34204.494217] device enp1s0 left promiscuous mode Apr 26 01:34:14 192.168.122.209 [34204.930840] [tdb] Close table 'client0.tdb' Apr 26 01:34:14 192.168.122.209 [34205.125641] [tdb] Close table 'sessions0.tdb' Apr 26 01:34:15 192.168.122.209 [34205.365391] [tdb] Close table 'filter0.tdb' Apr 26 01:34:15 192.168.122.209 [34205.365822] [tempesta fw] modules are stopped Apr 26 01:34:15 192.168.122.209 [34205.597280] [tempesta fw] exiting... Apr 26 01:34:15 192.168.122.209 [34205.743256] [tdb] Shutdown Tempesta DB Apr 26 01:34:15 192.168.122.209 [34205.939142] End test: tls.test_tls_tickets.TlsTicketTest.test_empty_ticket Apr 26 01:34:15 192.168.122.209 [34205.950443] Start test: tls.test_tls_tickets.StandardTlsClient.test Apr 26 01:34:16 192.168.122.209 [34207.156837] [tdb] Start Tempesta DB Apr 26 01:34:17 192.168.122.209 [34207.295842] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:34:17 192.168.122.209 [34208.055391] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34208.055391] Maybe that's fine, but it's worth checking the [34208.055391] config - if there is no relations between the [34208.055391] names, then host name confusion attack is possible. Apr 26 01:34:17 192.168.122.209 [34208.210161] [tempesta fw] Configuration processing is completed. Apr 26 01:34:18 192.168.122.209 [34208.266163] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:34:18 192.168.122.209 [34208.296463] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:34:18 192.168.122.209 [34208.324813] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:34:18 192.168.122.209 [34208.378106] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:34:18 192.168.122.209 [34208.418038] [tempesta fw] Tempesta FW is ready Apr 26 01:34:19 192.168.122.209 [34210.060670] [tdb] Close table 'client0.tdb' Apr 26 01:34:20 192.168.122.209 [34210.262967] [tdb] Close table 'sessions0.tdb' Apr 26 01:34:20 192.168.122.209 [34210.518099] [tdb] Close table 'filter0.tdb' Apr 26 01:34:20 192.168.122.209 [34210.518530] [tempesta fw] modules are stopped Apr 26 01:34:20 192.168.122.209 [34210.751926] [tempesta fw] exiting... Apr 26 01:34:20 192.168.122.209 [34210.919501] [tdb] Shutdown Tempesta DB Apr 26 01:34:20 192.168.122.209 [34211.147204] End test: tls.test_tls_tickets.StandardTlsClient.test Apr 26 01:34:20 192.168.122.209 [34211.159403] Start test: tls.test_tls_stress.TlsHandshakeDheRsaTest.test_stress_DHE_RSA_AES256_GCM_SHA384 Apr 26 01:34:23 192.168.122.209 [34213.578895] [tdb] Start Tempesta DB Apr 26 01:34:23 192.168.122.209 [34213.744076] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:34:24 192.168.122.209 [34214.531694] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34214.531694] Maybe that's fine, but it's worth checking the [34214.531694] config - if there is no relations between the [34214.531694] names, then host name confusion attack is possible. Apr 26 01:34:24 192.168.122.209 [34214.706241] [tempesta fw] Configuration processing is completed. Apr 26 01:34:24 192.168.122.209 [34214.767456] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:34:24 192.168.122.209 [34214.799296] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:34:24 192.168.122.209 [34214.826991] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:34:24 192.168.122.209 [34214.894207] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:34:24 192.168.122.209 [34214.942138] [tempesta fw] Tempesta FW is ready Apr 26 01:34:25 192.168.122.209 [34216.077581] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 01:34:26 192.168.122.209 [34216.680132] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34216.680132] Maybe that's fine, but it's worth checking the [34216.680132] config - if there is no relations between the [34216.680132] names, then host name confusion attack is possible. Apr 26 01:34:26 192.168.122.209 [34216.774287] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:34:26 192.168.122.209 [34216.779565] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:34:26 192.168.122.209 [34216.832297] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:34:26 192.168.122.209 [34216.849713] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:34:26 192.168.122.209 [34216.869803] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:34:26 192.168.122.209 [34216.885579] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:34:26 192.168.122.209 [34216.918585] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:34:26 192.168.122.209 [34216.919699] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:34:30 192.168.122.209 [34220.594701] [tempesta fw] Tempesta FW is ready Apr 26 01:34:31 192.168.122.209 [34221.924774] net_ratelimit: 25 callbacks suppressed Apr 26 01:34:31 192.168.122.209 [34221.924776] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 01:34:32 192.168.122.209 [34222.313111] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34222.313111] Maybe that's fine, but it's worth checking the [34222.313111] config - if there is no relations between the [34222.313111] names, then host name confusion attack is possible. Apr 26 01:34:33 192.168.122.209 [34224.226912] [tempesta fw] Configuration processing is completed. Apr 26 01:34:36 192.168.122.209 [34226.458625] [tempesta fw] Tempesta FW is ready Apr 26 01:34:38 192.168.122.209 [34228.401951] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 01:34:38 192.168.122.209 [34229.019514] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34229.019514] Maybe that's fine, but it's worth checking the [34229.019514] config - if there is no relations between the [34229.019514] names, then host name confusion attack is possible. Apr 26 01:34:40 192.168.122.209 [34230.954281] [tempesta fw] Configuration processing is completed. Apr 26 01:34:42 192.168.122.209 [34233.170903] [tempesta fw] Tempesta FW is ready Apr 26 01:34:43 192.168.122.209 [34234.064881] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 01:34:44 192.168.122.209 [34234.458507] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34234.458507] Maybe that's fine, but it's worth checking the [34234.458507] config - if there is no relations between the [34234.458507] names, then host name confusion attack is possible. Apr 26 01:34:45 192.168.122.209 [34235.953446] [tempesta fw] Configuration processing is completed. Apr 26 01:34:48 192.168.122.209 [34238.710158] [tempesta fw] Tempesta FW is ready Apr 26 01:34:49 192.168.122.209 [34240.046134] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 01:34:50 192.168.122.209 [34240.817265] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34240.817265] Maybe that's fine, but it's worth checking the [34240.817265] config - if there is no relations between the [34240.817265] names, then host name confusion attack is possible. Apr 26 01:34:52 192.168.122.209 [34242.381071] [tempesta fw] Configuration processing is completed. Apr 26 01:34:55 192.168.122.209 [34245.336180] [tempesta fw] Tempesta FW is ready Apr 26 01:34:56 192.168.122.209 [34246.818854] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 01:34:57 192.168.122.209 [34247.388873] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34247.388873] Maybe that's fine, but it's worth checking the [34247.388873] config - if there is no relations between the [34247.388873] names, then host name confusion attack is possible. Apr 26 01:34:58 192.168.122.209 [34249.150809] [tempesta fw] Configuration processing is completed. Apr 26 01:35:01 192.168.122.209 [34251.990977] [tempesta fw] Tempesta FW is ready Apr 26 01:35:03 192.168.122.209 [34253.680059] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 01:35:04 192.168.122.209 [34254.445694] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34254.445694] Maybe that's fine, but it's worth checking the [34254.445694] config - if there is no relations between the [34254.445694] names, then host name confusion attack is possible. Apr 26 01:35:05 192.168.122.209 [34255.782788] [tempesta fw] Configuration processing is completed. Apr 26 01:35:07 192.168.122.209 [34257.779601] [tempesta fw] Tempesta FW is ready Apr 26 01:35:09 192.168.122.209 [34259.530652] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 01:35:09 192.168.122.209 [34260.074969] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34260.074969] Maybe that's fine, but it's worth checking the [34260.074969] config - if there is no relations between the [34260.074969] names, then host name confusion attack is possible. Apr 26 01:35:11 192.168.122.209 [34261.725443] [tempesta fw] Configuration processing is completed. Apr 26 01:35:14 192.168.122.209 [34264.487562] [tempesta fw] Tempesta FW is ready Apr 26 01:35:15 192.168.122.209 [34266.126346] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 01:35:16 192.168.122.209 [34266.275915] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34266.275915] Maybe that's fine, but it's worth checking the [34266.275915] config - if there is no relations between the [34266.275915] names, then host name confusion attack is possible. Apr 26 01:35:16 192.168.122.209 [34266.430930] [tempesta fw] Configuration processing is completed. Apr 26 01:35:16 192.168.122.209 [34266.619585] [tempesta fw] Tempesta FW is ready Apr 26 01:35:16 192.168.122.209 [34267.188410] [tdb] Close table 'client0.tdb' Apr 26 01:35:17 192.168.122.209 [34267.384337] [tdb] Close table 'sessions0.tdb' Apr 26 01:35:17 192.168.122.209 [34267.616759] [tdb] Close table 'filter0.tdb' Apr 26 01:35:17 192.168.122.209 [34267.617178] [tempesta fw] modules are stopped Apr 26 01:35:17 192.168.122.209 [34267.828733] [tempesta fw] exiting... Apr 26 01:35:17 192.168.122.209 [34268.003678] [tdb] Shutdown Tempesta DB Apr 26 01:35:18 192.168.122.209 [34268.324031] End test: tls.test_tls_stress.TlsHandshakeDheRsaTest.test_stress_DHE_RSA_AES256_GCM_SHA384 Apr 26 01:35:18 192.168.122.209 [34268.334413] Start test: tls.test_tls_stress.TlsHandshakeDheRsaTest.test_stress_DHE_RSA_AES256_CCM Apr 26 01:35:20 192.168.122.209 [34270.747471] [tdb] Start Tempesta DB Apr 26 01:35:20 192.168.122.209 [34270.919627] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:35:21 192.168.122.209 [34271.758166] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34271.758166] Maybe that's fine, but it's worth checking the [34271.758166] config - if there is no relations between the [34271.758166] names, then host name confusion attack is possible. Apr 26 01:35:21 192.168.122.209 [34271.930988] [tempesta fw] Configuration processing is completed. Apr 26 01:35:21 192.168.122.209 [34271.998888] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:35:21 192.168.122.209 [34272.038197] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:35:21 192.168.122.209 [34272.073753] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:35:21 192.168.122.209 [34272.142947] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:35:21 192.168.122.209 [34272.186897] [tempesta fw] Tempesta FW is ready Apr 26 01:35:23 192.168.122.209 [34273.593044] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 01:35:23 192.168.122.209 [34274.060064] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:35:23 192.168.122.209 [34274.061235] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:35:23 192.168.122.209 [34274.065329] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:35:23 192.168.122.209 [34274.067134] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:35:23 192.168.122.209 [34274.075000] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:35:23 192.168.122.209 [34274.088389] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:35:28 192.168.122.209 [34278.435200] [tempesta fw] Tempesta FW is ready Apr 26 01:35:30 192.168.122.209 [34280.309743] net_ratelimit: 28 callbacks suppressed Apr 26 01:35:30 192.168.122.209 [34280.309745] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 01:35:30 192.168.122.209 [34280.821575] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34280.821575] Maybe that's fine, but it's worth checking the [34280.821575] config - if there is no relations between the [34280.821575] names, then host name confusion attack is possible. Apr 26 01:35:32 192.168.122.209 [34282.531243] [tempesta fw] Configuration processing is completed. Apr 26 01:35:33 192.168.122.209 [34284.033628] [tempesta fw] Tempesta FW is ready Apr 26 01:35:34 192.168.122.209 [34284.933952] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 01:35:35 192.168.122.209 [34285.433962] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34285.433962] Maybe that's fine, but it's worth checking the [34285.433962] config - if there is no relations between the [34285.433962] names, then host name confusion attack is possible. Apr 26 01:35:37 192.168.122.209 [34287.348758] [tempesta fw] Configuration processing is completed. Apr 26 01:35:39 192.168.122.209 [34289.755612] [tempesta fw] Tempesta FW is ready Apr 26 01:35:40 192.168.122.209 [34291.018591] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 01:35:41 192.168.122.209 [34291.547306] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34291.547306] Maybe that's fine, but it's worth checking the [34291.547306] config - if there is no relations between the [34291.547306] names, then host name confusion attack is possible. Apr 26 01:35:42 192.168.122.209 [34292.981944] [tempesta fw] Configuration processing is completed. Apr 26 01:35:45 192.168.122.209 [34295.548895] [tempesta fw] Tempesta FW is ready Apr 26 01:35:46 192.168.122.209 [34297.042071] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 01:35:47 192.168.122.209 [34297.479212] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34297.479212] Maybe that's fine, but it's worth checking the [34297.479212] config - if there is no relations between the [34297.479212] names, then host name confusion attack is possible. Apr 26 01:35:48 192.168.122.209 [34299.007535] [tempesta fw] Configuration processing is completed. Apr 26 01:35:52 192.168.122.209 [34302.282479] [tempesta fw] Tempesta FW is ready Apr 26 01:35:53 192.168.122.209 [34303.800099] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 01:35:54 192.168.122.209 [34304.435330] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34304.435330] Maybe that's fine, but it's worth checking the [34304.435330] config - if there is no relations between the [34304.435330] names, then host name confusion attack is possible. Apr 26 01:35:55 192.168.122.209 [34306.124751] [tempesta fw] Configuration processing is completed. Apr 26 01:35:58 192.168.122.209 [34308.526380] [tempesta fw] Tempesta FW is ready Apr 26 01:35:59 192.168.122.209 [34309.748233] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 01:36:00 192.168.122.209 [34310.415277] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34310.415277] Maybe that's fine, but it's worth checking the [34310.415277] config - if there is no relations between the [34310.415277] names, then host name confusion attack is possible. Apr 26 01:36:01 192.168.122.209 [34312.015427] [tempesta fw] Configuration processing is completed. Apr 26 01:36:03 192.168.122.209 [34313.996215] [tempesta fw] Tempesta FW is ready Apr 26 01:36:05 192.168.122.209 [34315.416956] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 01:36:05 192.168.122.209 [34316.018888] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34316.018888] Maybe that's fine, but it's worth checking the [34316.018888] config - if there is no relations between the [34316.018888] names, then host name confusion attack is possible. Apr 26 01:36:07 192.168.122.209 [34317.804736] [tempesta fw] Configuration processing is completed. Apr 26 01:36:09 192.168.122.209 [34319.996053] [tempesta fw] Tempesta FW is ready Apr 26 01:36:11 192.168.122.209 [34321.835739] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 01:36:12 192.168.122.209 [34322.290990] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34322.290990] Maybe that's fine, but it's worth checking the [34322.290990] config - if there is no relations between the [34322.290990] names, then host name confusion attack is possible. Apr 26 01:36:13 192.168.122.209 [34323.619771] [tempesta fw] Configuration processing is completed. Apr 26 01:36:13 192.168.122.209 [34323.808379] [tempesta fw] Tempesta FW is ready Apr 26 01:36:14 192.168.122.209 [34324.420366] [tdb] Close table 'client0.tdb' Apr 26 01:36:14 192.168.122.209 [34324.676905] [tdb] Close table 'sessions0.tdb' Apr 26 01:36:14 192.168.122.209 [34324.979140] [tdb] Close table 'filter0.tdb' Apr 26 01:36:14 192.168.122.209 [34324.979652] [tempesta fw] modules are stopped Apr 26 01:36:14 192.168.122.209 [34325.194206] [tempesta fw] exiting... Apr 26 01:36:15 192.168.122.209 [34325.376375] [tdb] Shutdown Tempesta DB Apr 26 01:36:15 192.168.122.209 [34325.660378] End test: tls.test_tls_stress.TlsHandshakeDheRsaTest.test_stress_DHE_RSA_AES256_CCM Apr 26 01:36:15 192.168.122.209 [34325.681764] Start test: tls.test_tls_stress.TlsHandshakeDheRsaTest.test_stress_DHE_RSA_AES128_GCM_SHA256 Apr 26 01:36:18 192.168.122.209 [34328.625006] [tdb] Start Tempesta DB Apr 26 01:36:18 192.168.122.209 [34328.835981] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:36:19 192.168.122.209 [34329.733187] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34329.733187] Maybe that's fine, but it's worth checking the [34329.733187] config - if there is no relations between the [34329.733187] names, then host name confusion attack is possible. Apr 26 01:36:19 192.168.122.209 [34329.911822] [tempesta fw] Configuration processing is completed. Apr 26 01:36:19 192.168.122.209 [34329.974172] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:36:19 192.168.122.209 [34330.009587] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:36:19 192.168.122.209 [34330.039765] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:36:19 192.168.122.209 [34330.115826] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:36:19 192.168.122.209 [34330.159654] [tempesta fw] Tempesta FW is ready Apr 26 01:36:21 192.168.122.209 [34332.015435] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:36:21 192.168.122.209 [34332.048133] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:36:21 192.168.122.209 [34332.103540] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:36:21 192.168.122.209 [34332.104699] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:36:21 192.168.122.209 [34332.107734] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:36:21 192.168.122.209 [34332.118203] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:36:23 192.168.122.209 [34334.102993] net_ratelimit: 28 callbacks suppressed Apr 26 01:36:23 192.168.122.209 [34334.102997] [tempesta fw] Configuration processing is completed. Apr 26 01:36:26 192.168.122.209 [34336.803747] [tempesta fw] Tempesta FW is ready Apr 26 01:36:27 192.168.122.209 [34338.012486] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 01:36:28 192.168.122.209 [34338.737814] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34338.737814] Maybe that's fine, but it's worth checking the [34338.737814] config - if there is no relations between the [34338.737814] names, then host name confusion attack is possible. Apr 26 01:36:30 192.168.122.209 [34340.506102] [tempesta fw] Configuration processing is completed. Apr 26 01:36:32 192.168.122.209 [34342.929894] [tempesta fw] Tempesta FW is ready Apr 26 01:36:34 192.168.122.209 [34344.455579] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 01:36:34 192.168.122.209 [34345.053596] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34345.053596] Maybe that's fine, but it's worth checking the [34345.053596] config - if there is no relations between the [34345.053596] names, then host name confusion attack is possible. Apr 26 01:36:36 192.168.122.209 [34346.832256] [tempesta fw] Configuration processing is completed. Apr 26 01:36:39 192.168.122.209 [34349.728470] [tempesta fw] Tempesta FW is ready Apr 26 01:36:40 192.168.122.209 [34351.220537] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 01:36:41 192.168.122.209 [34351.656885] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34351.656885] Maybe that's fine, but it's worth checking the [34351.656885] config - if there is no relations between the [34351.656885] names, then host name confusion attack is possible. Apr 26 01:36:43 192.168.122.209 [34353.628088] [tempesta fw] Configuration processing is completed. Apr 26 01:36:45 192.168.122.209 [34356.212333] [tempesta fw] Tempesta FW is ready Apr 26 01:36:47 192.168.122.209 [34357.532255] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 01:36:47 192.168.122.209 [34358.031485] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34358.031485] Maybe that's fine, but it's worth checking the [34358.031485] config - if there is no relations between the [34358.031485] names, then host name confusion attack is possible. Apr 26 01:36:49 192.168.122.209 [34359.855973] [tempesta fw] Configuration processing is completed. Apr 26 01:36:51 192.168.122.209 [34361.260525] [tempesta fw] Tempesta FW is ready Apr 26 01:36:52 192.168.122.209 [34362.824424] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 01:36:53 192.168.122.209 [34363.421173] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34363.421173] Maybe that's fine, but it's worth checking the [34363.421173] config - if there is no relations between the [34363.421173] names, then host name confusion attack is possible. Apr 26 01:36:55 192.168.122.209 [34365.259961] [tempesta fw] Configuration processing is completed. Apr 26 01:36:57 192.168.122.209 [34367.538840] [tempesta fw] Tempesta FW is ready Apr 26 01:36:58 192.168.122.209 [34368.713927] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 01:36:59 192.168.122.209 [34369.289838] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34369.289838] Maybe that's fine, but it's worth checking the [34369.289838] config - if there is no relations between the [34369.289838] names, then host name confusion attack is possible. Apr 26 01:37:00 192.168.122.209 [34370.876660] [tempesta fw] Configuration processing is completed. Apr 26 01:37:02 192.168.122.209 [34372.577618] [tempesta fw] Tempesta FW is ready Apr 26 01:37:03 192.168.122.209 [34373.863154] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 01:37:04 192.168.122.209 [34374.714777] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34374.714777] Maybe that's fine, but it's worth checking the [34374.714777] config - if there is no relations between the [34374.714777] names, then host name confusion attack is possible. Apr 26 01:37:06 192.168.122.209 [34376.690050] [tempesta fw] Configuration processing is completed. Apr 26 01:37:08 192.168.122.209 [34379.220508] [tempesta fw] Tempesta FW is ready Apr 26 01:37:10 192.168.122.209 [34380.608624] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 01:37:11 192.168.122.209 [34381.381956] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34381.381956] Maybe that's fine, but it's worth checking the [34381.381956] config - if there is no relations between the [34381.381956] names, then host name confusion attack is possible. Apr 26 01:37:11 192.168.122.209 [34381.916434] [tempesta fw] Configuration processing is completed. Apr 26 01:37:11 192.168.122.209 [34382.053106] [tempesta fw] Tempesta FW is ready Apr 26 01:37:12 192.168.122.209 [34382.603383] [tdb] Close table 'client0.tdb' Apr 26 01:37:12 192.168.122.209 [34382.817327] [tdb] Close table 'sessions0.tdb' Apr 26 01:37:12 192.168.122.209 [34383.064908] [tdb] Close table 'filter0.tdb' Apr 26 01:37:12 192.168.122.209 [34383.065387] [tempesta fw] modules are stopped Apr 26 01:37:13 192.168.122.209 [34383.334138] [tempesta fw] exiting... Apr 26 01:37:13 192.168.122.209 [34383.491340] [tdb] Shutdown Tempesta DB Apr 26 01:37:13 192.168.122.209 [34383.804229] End test: tls.test_tls_stress.TlsHandshakeDheRsaTest.test_stress_DHE_RSA_AES128_GCM_SHA256 Apr 26 01:37:13 192.168.122.209 [34383.825384] Start test: tls.test_tls_stress.TlsHandshakeDheRsaTest.test_stress_DHE_RSA_AES128_CCM Apr 26 01:37:16 192.168.122.209 [34386.266897] [tdb] Start Tempesta DB Apr 26 01:37:16 192.168.122.209 [34386.441974] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:37:17 192.168.122.209 [34387.317887] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34387.317887] Maybe that's fine, but it's worth checking the [34387.317887] config - if there is no relations between the [34387.317887] names, then host name confusion attack is possible. Apr 26 01:37:17 192.168.122.209 [34387.488397] [tempesta fw] Configuration processing is completed. Apr 26 01:37:17 192.168.122.209 [34387.549450] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:37:17 192.168.122.209 [34387.583295] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:37:17 192.168.122.209 [34387.616301] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:37:17 192.168.122.209 [34387.680380] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:37:17 192.168.122.209 [34387.740331] [tempesta fw] Tempesta FW is ready Apr 26 01:37:19 192.168.122.209 [34389.414634] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 01:37:19 192.168.122.209 [34389.639155] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:37:19 192.168.122.209 [34389.639267] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:37:19 192.168.122.209 [34389.640146] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:37:19 192.168.122.209 [34389.641139] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:37:19 192.168.122.209 [34389.641672] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:37:19 192.168.122.209 [34389.641718] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:37:24 192.168.122.209 [34394.680642] [tempesta fw] Tempesta FW is ready Apr 26 01:37:25 192.168.122.209 [34396.158631] net_ratelimit: 28 callbacks suppressed Apr 26 01:37:25 192.168.122.209 [34396.158634] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 01:37:26 192.168.122.209 [34396.634498] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34396.634498] Maybe that's fine, but it's worth checking the [34396.634498] config - if there is no relations between the [34396.634498] names, then host name confusion attack is possible. Apr 26 01:37:27 192.168.122.209 [34398.225590] [tempesta fw] Configuration processing is completed. Apr 26 01:37:30 192.168.122.209 [34400.301140] [tempesta fw] Tempesta FW is ready Apr 26 01:37:31 192.168.122.209 [34401.839945] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 01:37:32 192.168.122.209 [34402.278168] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34402.278168] Maybe that's fine, but it's worth checking the [34402.278168] config - if there is no relations between the [34402.278168] names, then host name confusion attack is possible. Apr 26 01:37:34 192.168.122.209 [34404.284393] [tempesta fw] Configuration processing is completed. Apr 26 01:37:37 192.168.122.209 [34407.351900] [tempesta fw] Tempesta FW is ready Apr 26 01:37:38 192.168.122.209 [34408.676052] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 01:37:38 192.168.122.209 [34409.127702] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34409.127702] Maybe that's fine, but it's worth checking the [34409.127702] config - if there is no relations between the [34409.127702] names, then host name confusion attack is possible. Apr 26 01:37:40 192.168.122.209 [34410.548735] [tempesta fw] Configuration processing is completed. Apr 26 01:37:43 192.168.122.209 [34413.297027] [tempesta fw] Tempesta FW is ready Apr 26 01:37:44 192.168.122.209 [34414.672008] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 01:37:44 192.168.122.209 [34415.169299] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34415.169299] Maybe that's fine, but it's worth checking the [34415.169299] config - if there is no relations between the [34415.169299] names, then host name confusion attack is possible. Apr 26 01:37:46 192.168.122.209 [34416.821231] [tempesta fw] Configuration processing is completed. Apr 26 01:37:49 192.168.122.209 [34419.541928] [tempesta fw] Tempesta FW is ready Apr 26 01:37:51 192.168.122.209 [34421.465797] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 01:37:51 192.168.122.209 [34421.793123] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34421.793123] Maybe that's fine, but it's worth checking the [34421.793123] config - if there is no relations between the [34421.793123] names, then host name confusion attack is possible. Apr 26 01:37:53 192.168.122.209 [34423.521150] [tempesta fw] Configuration processing is completed. Apr 26 01:37:55 192.168.122.209 [34426.040875] [tempesta fw] Tempesta FW is ready Apr 26 01:37:57 192.168.122.209 [34427.916132] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 01:37:58 192.168.122.209 [34428.490853] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34428.490853] Maybe that's fine, but it's worth checking the [34428.490853] config - if there is no relations between the [34428.490853] names, then host name confusion attack is possible. Apr 26 01:37:58 192.168.122.209 [34429.227210] [tempesta fw] Configuration processing is completed. Apr 26 01:38:02 192.168.122.209 [34432.372342] [tempesta fw] Tempesta FW is ready Apr 26 01:38:04 192.168.122.209 [34434.287288] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 01:38:04 192.168.122.209 [34434.887464] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34434.887464] Maybe that's fine, but it's worth checking the [34434.887464] config - if there is no relations between the [34434.887464] names, then host name confusion attack is possible. Apr 26 01:38:06 192.168.122.209 [34436.321493] [tempesta fw] Configuration processing is completed. Apr 26 01:38:08 192.168.122.209 [34438.957653] [tempesta fw] Tempesta FW is ready Apr 26 01:38:09 192.168.122.209 [34439.840172] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 01:38:09 192.168.122.209 [34439.918783] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34439.918783] Maybe that's fine, but it's worth checking the [34439.918783] config - if there is no relations between the [34439.918783] names, then host name confusion attack is possible. Apr 26 01:38:09 192.168.122.209 [34440.105186] [tempesta fw] Configuration processing is completed. Apr 26 01:38:10 192.168.122.209 [34440.245896] [tempesta fw] Tempesta FW is ready Apr 26 01:38:10 192.168.122.209 [34440.794420] [tdb] Close table 'client0.tdb' Apr 26 01:38:10 192.168.122.209 [34440.989228] [tdb] Close table 'sessions0.tdb' Apr 26 01:38:10 192.168.122.209 [34441.224002] [tdb] Close table 'filter0.tdb' Apr 26 01:38:10 192.168.122.209 [34441.224448] [tempesta fw] modules are stopped Apr 26 01:38:11 192.168.122.209 [34441.470982] [tempesta fw] exiting... Apr 26 01:38:11 192.168.122.209 [34441.615928] [tdb] Shutdown Tempesta DB Apr 26 01:38:11 192.168.122.209 [34441.910267] End test: tls.test_tls_stress.TlsHandshakeDheRsaTest.test_stress_DHE_RSA_AES128_CCM Apr 26 01:38:11 192.168.122.209 [34441.927977] Start test: tls.test_tls_stress.TlsHandshakeDheRsaTest.test_DHE_RSA_AES256_GCM_SHA384 Apr 26 01:38:14 192.168.122.209 [34444.290923] [tdb] Start Tempesta DB Apr 26 01:38:14 192.168.122.209 [34444.438611] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:38:15 192.168.122.209 [34445.366461] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34445.366461] Maybe that's fine, but it's worth checking the [34445.366461] config - if there is no relations between the [34445.366461] names, then host name confusion attack is possible. Apr 26 01:38:15 192.168.122.209 [34445.541241] [tempesta fw] Configuration processing is completed. Apr 26 01:38:15 192.168.122.209 [34445.602111] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:38:15 192.168.122.209 [34445.639235] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:38:15 192.168.122.209 [34445.672824] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:38:15 192.168.122.209 [34445.737199] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:38:15 192.168.122.209 [34445.785193] [tempesta fw] Tempesta FW is ready Apr 26 01:38:17 192.168.122.209 [34447.711392] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:38:17 192.168.122.209 [34447.736392] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:38:17 192.168.122.209 [34447.738062] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:38:17 192.168.122.209 [34447.771015] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:38:17 192.168.122.209 [34447.772007] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:38:17 192.168.122.209 [34447.776690] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:38:17 192.168.122.209 [34447.811749] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:38:26 192.168.122.209 [34456.551515] [tdb] Close table 'client0.tdb' Apr 26 01:38:26 192.168.122.209 [34456.759211] [tdb] Close table 'sessions0.tdb' Apr 26 01:38:26 192.168.122.209 [34456.998315] [tdb] Close table 'filter0.tdb' Apr 26 01:38:26 192.168.122.209 [34456.998792] net_ratelimit: 25 callbacks suppressed Apr 26 01:38:26 192.168.122.209 [34456.998793] [tempesta fw] modules are stopped Apr 26 01:38:26 192.168.122.209 [34457.234221] [tempesta fw] exiting... Apr 26 01:38:27 192.168.122.209 [34457.420990] [tdb] Shutdown Tempesta DB Apr 26 01:38:27 192.168.122.209 [34457.684343] End test: tls.test_tls_stress.TlsHandshakeDheRsaTest.test_DHE_RSA_AES256_GCM_SHA384 Apr 26 01:38:27 192.168.122.209 [34457.711005] Start test: tls.test_tls_stress.TlsHandshakeDheRsaTest.test_DHE_RSA_AES256_CCM Apr 26 01:38:29 192.168.122.209 [34459.858499] [tdb] Start Tempesta DB Apr 26 01:38:29 192.168.122.209 [34460.022243] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:38:30 192.168.122.209 [34460.934841] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34460.934841] Maybe that's fine, but it's worth checking the [34460.934841] config - if there is no relations between the [34460.934841] names, then host name confusion attack is possible. Apr 26 01:38:30 192.168.122.209 [34461.093441] [tempesta fw] Configuration processing is completed. Apr 26 01:38:30 192.168.122.209 [34461.154044] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:38:30 192.168.122.209 [34461.188400] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:38:30 192.168.122.209 [34461.218271] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:38:31 192.168.122.209 [34461.289394] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:38:31 192.168.122.209 [34461.337370] [tempesta fw] Tempesta FW is ready Apr 26 01:38:33 192.168.122.209 [34463.334734] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:38:33 192.168.122.209 [34463.336261] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:38:33 192.168.122.209 [34463.336382] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:38:33 192.168.122.209 [34463.336415] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:38:33 192.168.122.209 [34463.336447] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:38:33 192.168.122.209 [34463.339291] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:38:33 192.168.122.209 [34463.347697] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:38:33 192.168.122.209 [34463.349626] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:38:33 192.168.122.209 [34463.368147] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:38:33 192.168.122.209 [34463.370705] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:38:42 192.168.122.209 [34472.271155] [tdb] Close table 'client0.tdb' Apr 26 01:38:42 192.168.122.209 [34472.486343] [tdb] Close table 'sessions0.tdb' Apr 26 01:38:42 192.168.122.209 [34472.715930] [tdb] Close table 'filter0.tdb' Apr 26 01:38:42 192.168.122.209 [34472.716356] net_ratelimit: 22 callbacks suppressed Apr 26 01:38:42 192.168.122.209 [34472.716357] [tempesta fw] modules are stopped Apr 26 01:38:42 192.168.122.209 [34472.923166] [tempesta fw] exiting... Apr 26 01:38:42 192.168.122.209 [34473.092202] [tdb] Shutdown Tempesta DB Apr 26 01:38:43 192.168.122.209 [34473.334153] End test: tls.test_tls_stress.TlsHandshakeDheRsaTest.test_DHE_RSA_AES256_CCM Apr 26 01:38:43 192.168.122.209 [34473.353969] Start test: tls.test_tls_stress.TlsHandshakeDheRsaTest.test_DHE_RSA_AES128_GCM_SHA256 Apr 26 01:38:46 192.168.122.209 [34476.443066] [tdb] Start Tempesta DB Apr 26 01:38:46 192.168.122.209 [34476.574407] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:38:47 192.168.122.209 [34477.478636] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34477.478636] Maybe that's fine, but it's worth checking the [34477.478636] config - if there is no relations between the [34477.478636] names, then host name confusion attack is possible. Apr 26 01:38:47 192.168.122.209 [34477.645637] [tempesta fw] Configuration processing is completed. Apr 26 01:38:47 192.168.122.209 [34477.704071] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:38:47 192.168.122.209 [34477.738055] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:38:47 192.168.122.209 [34477.770170] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:38:47 192.168.122.209 [34477.845634] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:38:47 192.168.122.209 [34477.885623] [tempesta fw] Tempesta FW is ready Apr 26 01:38:49 192.168.122.209 [34479.762761] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:38:49 192.168.122.209 [34479.766285] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:38:49 192.168.122.209 [34479.766302] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:38:49 192.168.122.209 [34479.767308] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:38:49 192.168.122.209 [34479.768269] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:38:49 192.168.122.209 [34479.770172] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:38:49 192.168.122.209 [34479.834472] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:38:49 192.168.122.209 [34479.836590] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:38:49 192.168.122.209 [34479.864175] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:38:58 192.168.122.209 [34488.775545] [tdb] Close table 'client0.tdb' Apr 26 01:38:58 192.168.122.209 [34488.971074] [tdb] Close table 'sessions0.tdb' Apr 26 01:38:58 192.168.122.209 [34489.222005] [tdb] Close table 'filter0.tdb' Apr 26 01:38:58 192.168.122.209 [34489.222436] net_ratelimit: 23 callbacks suppressed Apr 26 01:38:58 192.168.122.209 [34489.222437] [tempesta fw] modules are stopped Apr 26 01:38:59 192.168.122.209 [34489.430819] [tempesta fw] exiting... Apr 26 01:38:59 192.168.122.209 [34489.607689] [tdb] Shutdown Tempesta DB Apr 26 01:38:59 192.168.122.209 [34489.893042] End test: tls.test_tls_stress.TlsHandshakeDheRsaTest.test_DHE_RSA_AES128_GCM_SHA256 Apr 26 01:38:59 192.168.122.209 [34489.908879] Start test: tls.test_tls_stress.TlsHandshakeDheRsaTest.test_DHE_RSA_AES128_CCM Apr 26 01:39:02 192.168.122.209 [34492.653995] [tdb] Start Tempesta DB Apr 26 01:39:02 192.168.122.209 [34492.821798] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:39:03 192.168.122.209 [34493.706102] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34493.706102] Maybe that's fine, but it's worth checking the [34493.706102] config - if there is no relations between the [34493.706102] names, then host name confusion attack is possible. Apr 26 01:39:03 192.168.122.209 [34493.877891] [tempesta fw] Configuration processing is completed. Apr 26 01:39:03 192.168.122.209 [34493.943102] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:39:03 192.168.122.209 [34493.981009] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:39:03 192.168.122.209 [34494.015099] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:39:03 192.168.122.209 [34494.085824] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:39:03 192.168.122.209 [34494.125683] [tempesta fw] Tempesta FW is ready Apr 26 01:39:05 192.168.122.209 [34496.059690] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:39:05 192.168.122.209 [34496.061300] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:39:05 192.168.122.209 [34496.062307] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:39:05 192.168.122.209 [34496.063727] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:39:05 192.168.122.209 [34496.095421] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:39:05 192.168.122.209 [34496.096381] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:39:05 192.168.122.209 [34496.097445] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:39:05 192.168.122.209 [34496.098577] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:39:05 192.168.122.209 [34496.112671] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:39:05 192.168.122.209 [34496.123006] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 01:39:14 192.168.122.209 [34504.935677] [tdb] Close table 'client0.tdb' Apr 26 01:39:14 192.168.122.209 [34505.130455] [tdb] Close table 'sessions0.tdb' Apr 26 01:39:15 192.168.122.209 [34505.380422] [tdb] Close table 'filter0.tdb' Apr 26 01:39:15 192.168.122.209 [34505.380866] net_ratelimit: 22 callbacks suppressed Apr 26 01:39:15 192.168.122.209 [34505.380868] [tempesta fw] modules are stopped Apr 26 01:39:15 192.168.122.209 [34505.595694] [tempesta fw] exiting... Apr 26 01:39:15 192.168.122.209 [34505.754101] [tdb] Shutdown Tempesta DB Apr 26 01:39:15 192.168.122.209 [34506.043627] End test: tls.test_tls_stress.TlsHandshakeDheRsaTest.test_DHE_RSA_AES128_CCM Apr 26 01:39:15 192.168.122.209 [34506.069483] Start test: tls.test_tls_stress.StressTls.test Apr 26 01:39:17 192.168.122.209 [34507.638683] [tdb] Start Tempesta DB Apr 26 01:39:17 192.168.122.209 [34507.797659] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:39:18 192.168.122.209 [34508.431609] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34508.431609] Maybe that's fine, but it's worth checking the [34508.431609] config - if there is no relations between the [34508.431609] names, then host name confusion attack is possible. Apr 26 01:39:18 192.168.122.209 [34508.557981] [tempesta fw] Configuration processing is completed. Apr 26 01:39:18 192.168.122.209 [34508.622712] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:39:19 192.168.122.209 [34509.306231] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:39:19 192.168.122.209 [34509.358109] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:39:19 192.168.122.209 [34509.446414] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:39:19 192.168.122.209 [34509.538017] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:39:19 192.168.122.209 [34509.602020] [tempesta fw] Tempesta FW is ready Apr 26 01:39:30 192.168.122.209 [34520.444798] [tdb] Close table 'client0.tdb' Apr 26 01:39:30 192.168.122.209 [34520.650102] [tdb] Close table 'sessions0.tdb' Apr 26 01:39:33 192.168.122.209 [34524.089958] [tdb] Close table 'cache0.tdb' Apr 26 01:39:34 192.168.122.209 [34524.469863] [tdb] Close table 'filter0.tdb' Apr 26 01:39:34 192.168.122.209 [34524.470390] [tempesta fw] modules are stopped Apr 26 01:39:34 192.168.122.209 [34524.677140] [tempesta fw] exiting... Apr 26 01:39:34 192.168.122.209 [34524.851461] [tdb] Shutdown Tempesta DB Apr 26 01:39:34 192.168.122.209 [34525.183757] End test: tls.test_tls_stress.StressTls.test Apr 26 01:39:34 192.168.122.209 [34525.202092] Start test: tls.test_tls_limits.TLSMatchHostSni.test_host_sni_mismatch Apr 26 01:39:36 192.168.122.209 [34526.583886] [tdb] Start Tempesta DB Apr 26 01:39:36 192.168.122.209 [34526.789392] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:39:38 192.168.122.209 [34528.516216] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34528.516216] Maybe that's fine, but it's worth checking the [34528.516216] config - if there is no relations between the [34528.516216] names, then host name confusion attack is possible. Apr 26 01:39:38 192.168.122.209 [34528.646355] [tempesta fw] Configuration processing is completed. Apr 26 01:39:38 192.168.122.209 [34528.712299] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:39:38 192.168.122.209 [34528.753375] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:39:38 192.168.122.209 [34528.794862] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:39:38 192.168.122.209 [34528.838273] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:39:38 192.168.122.209 [34528.878252] [tempesta fw] Tempesta FW is ready Apr 26 01:39:38 192.168.122.209 [34529.142314] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.2 ('default' vs 'dummy') Apr 26 01:39:38 192.168.122.209 [34529.144105] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 01:39:39 192.168.122.209 [34529.723778] [tdb] Close table 'client0.tdb' Apr 26 01:39:39 192.168.122.209 [34529.941670] [tdb] Close table 'sessions0.tdb' Apr 26 01:39:39 192.168.122.209 [34530.188738] [tdb] Close table 'filter0.tdb' Apr 26 01:39:39 192.168.122.209 [34530.189211] [tempesta fw] modules are stopped Apr 26 01:39:40 192.168.122.209 [34530.446954] [tempesta fw] exiting... Apr 26 01:39:40 192.168.122.209 [34530.600118] [tdb] Shutdown Tempesta DB Apr 26 01:39:40 192.168.122.209 [34530.860140] End test: tls.test_tls_limits.TLSMatchHostSni.test_host_sni_mismatch Apr 26 01:39:40 192.168.122.209 [34530.878929] Start test: tls.test_tls_kernel.TCrypt.test_tcrypt Apr 26 01:39:41 192.168.122.209 [34531.368979] End test: tls.test_tls_kernel.TCrypt.test_tcrypt Apr 26 01:39:41 192.168.122.209 [34531.385904] Start test: tls.test_tls_integrity.ProxyH2.test_various_req_resp_sizes Apr 26 01:39:42 192.168.122.209 [34532.869254] [tdb] Start Tempesta DB Apr 26 01:39:42 192.168.122.209 [34533.033118] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:39:43 192.168.122.209 [34533.569209] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34533.569209] Maybe that's fine, but it's worth checking the [34533.569209] config - if there is no relations between the [34533.569209] names, then host name confusion attack is possible. Apr 26 01:39:43 192.168.122.209 [34533.650416] [tempesta fw] Configuration processing is completed. Apr 26 01:39:43 192.168.122.209 [34533.713839] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:39:43 192.168.122.209 [34533.752275] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:39:43 192.168.122.209 [34533.789358] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:39:43 192.168.122.209 [34533.834335] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:39:43 192.168.122.209 [34533.882319] [tempesta fw] Tempesta FW is ready Apr 26 01:39:44 192.168.122.209 [34534.860691] [tdb] Close table 'client0.tdb' Apr 26 01:39:44 192.168.122.209 [34535.057449] [tdb] Close table 'sessions0.tdb' Apr 26 01:39:45 192.168.122.209 [34535.313647] [tdb] Close table 'filter0.tdb' Apr 26 01:39:45 192.168.122.209 [34535.314081] [tempesta fw] modules are stopped Apr 26 01:39:45 192.168.122.209 [34535.513684] [tempesta fw] exiting... Apr 26 01:39:45 192.168.122.209 [34535.666575] [tdb] Shutdown Tempesta DB Apr 26 01:39:45 192.168.122.209 [34535.931166] End test: tls.test_tls_integrity.ProxyH2.test_various_req_resp_sizes Apr 26 01:39:45 192.168.122.209 [34535.970467] Start test: tls.test_tls_integrity.Proxy.test_various_req_resp_sizes Apr 26 01:39:47 192.168.122.209 [34537.353181] [tdb] Start Tempesta DB Apr 26 01:39:47 192.168.122.209 [34537.507097] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:39:47 192.168.122.209 [34538.111719] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34538.111719] Maybe that's fine, but it's worth checking the [34538.111719] config - if there is no relations between the [34538.111719] names, then host name confusion attack is possible. Apr 26 01:39:47 192.168.122.209 [34538.230481] [tempesta fw] Configuration processing is completed. Apr 26 01:39:48 192.168.122.209 [34538.292270] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:39:48 192.168.122.209 [34538.328882] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:39:48 192.168.122.209 [34538.363896] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:39:48 192.168.122.209 [34538.414421] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:39:48 192.168.122.209 [34538.458350] [tempesta fw] Tempesta FW is ready Apr 26 01:39:49 192.168.122.209 [34539.448853] [tdb] Close table 'client0.tdb' Apr 26 01:39:49 192.168.122.209 [34539.648395] [tdb] Close table 'sessions0.tdb' Apr 26 01:39:49 192.168.122.209 [34539.865867] [tdb] Close table 'filter0.tdb' Apr 26 01:39:49 192.168.122.209 [34539.866317] [tempesta fw] modules are stopped Apr 26 01:39:49 192.168.122.209 [34540.083766] [tempesta fw] exiting... Apr 26 01:39:49 192.168.122.209 [34540.226039] [tdb] Shutdown Tempesta DB Apr 26 01:39:50 192.168.122.209 [34540.490632] End test: tls.test_tls_integrity.Proxy.test_various_req_resp_sizes Apr 26 01:39:50 192.168.122.209 [34540.504658] Start test: tls.test_tls_integrity.ManyClientsH2.test_various_req_resp_sizes Apr 26 01:39:51 192.168.122.209 [34541.852392] [tdb] Start Tempesta DB Apr 26 01:39:51 192.168.122.209 [34541.991928] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:39:52 192.168.122.209 [34542.643753] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34542.643753] Maybe that's fine, but it's worth checking the [34542.643753] config - if there is no relations between the [34542.643753] names, then host name confusion attack is possible. Apr 26 01:39:52 192.168.122.209 [34542.766687] [tempesta fw] Configuration processing is completed. Apr 26 01:39:52 192.168.122.209 [34542.833571] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:39:52 192.168.122.209 [34542.872306] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:39:52 192.168.122.209 [34542.906663] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:39:52 192.168.122.209 [34542.974483] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:39:52 192.168.122.209 [34543.014364] [tempesta fw] Tempesta FW is ready Apr 26 01:39:54 192.168.122.209 [34544.891200] [tdb] Close table 'client0.tdb' Apr 26 01:39:54 192.168.122.209 [34545.082624] [tdb] Close table 'sessions0.tdb' Apr 26 01:39:55 192.168.122.209 [34545.333327] [tdb] Close table 'filter0.tdb' Apr 26 01:39:55 192.168.122.209 [34545.333763] [tempesta fw] modules are stopped Apr 26 01:39:55 192.168.122.209 [34545.605028] [tempesta fw] exiting... Apr 26 01:39:55 192.168.122.209 [34545.768195] [tdb] Shutdown Tempesta DB Apr 26 01:39:55 192.168.122.209 [34546.018415] End test: tls.test_tls_integrity.ManyClientsH2.test_various_req_resp_sizes Apr 26 01:39:55 192.168.122.209 [34546.033230] Start test: tls.test_tls_integrity.ManyClients.test_various_req_resp_sizes Apr 26 01:39:57 192.168.122.209 [34547.488144] [tdb] Start Tempesta DB Apr 26 01:39:57 192.168.122.209 [34547.665480] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:39:57 192.168.122.209 [34548.220055] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34548.220055] Maybe that's fine, but it's worth checking the [34548.220055] config - if there is no relations between the [34548.220055] names, then host name confusion attack is possible. Apr 26 01:39:58 192.168.122.209 [34548.318592] [tempesta fw] Configuration processing is completed. Apr 26 01:39:58 192.168.122.209 [34548.384549] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:39:58 192.168.122.209 [34548.426239] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:39:58 192.168.122.209 [34548.464434] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:39:58 192.168.122.209 [34548.514611] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:39:58 192.168.122.209 [34548.554485] [tempesta fw] Tempesta FW is ready Apr 26 01:40:00 192.168.122.209 [34551.001654] [tdb] Close table 'client0.tdb' Apr 26 01:40:00 192.168.122.209 [34551.191361] [tdb] Close table 'sessions0.tdb' Apr 26 01:40:01 192.168.122.209 [34551.438483] [tdb] Close table 'filter0.tdb' Apr 26 01:40:01 192.168.122.209 [34551.438940] [tempesta fw] modules are stopped Apr 26 01:40:01 192.168.122.209 [34551.640795] [tempesta fw] exiting... Apr 26 01:40:01 192.168.122.209 [34551.776181] [tdb] Shutdown Tempesta DB Apr 26 01:40:01 192.168.122.209 [34552.006792] End test: tls.test_tls_integrity.ManyClients.test_various_req_resp_sizes Apr 26 01:40:01 192.168.122.209 [34552.025066] Start test: tls.test_tls_integrity.CloseConnection.test8 Apr 26 01:40:03 192.168.122.209 [34553.297152] [tdb] Start Tempesta DB Apr 26 01:40:03 192.168.122.209 [34553.455588] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:40:03 192.168.122.209 [34554.076214] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34554.076214] Maybe that's fine, but it's worth checking the [34554.076214] config - if there is no relations between the [34554.076214] names, then host name confusion attack is possible. Apr 26 01:40:03 192.168.122.209 [34554.186669] [tempesta fw] Configuration processing is completed. Apr 26 01:40:04 192.168.122.209 [34554.244549] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:40:04 192.168.122.209 [34554.279847] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:40:04 192.168.122.209 [34554.321946] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:40:04 192.168.122.209 [34554.378645] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:40:04 192.168.122.209 [34554.422593] [tempesta fw] Tempesta FW is ready Apr 26 01:40:04 192.168.122.209 [34555.225812] [tdb] Close table 'client0.tdb' Apr 26 01:40:05 192.168.122.209 [34555.413581] [tdb] Close table 'sessions0.tdb' Apr 26 01:40:05 192.168.122.209 [34555.673939] [tdb] Close table 'filter0.tdb' Apr 26 01:40:05 192.168.122.209 [34555.674817] [tempesta fw] modules are stopped Apr 26 01:40:05 192.168.122.209 [34555.880167] [tempesta fw] exiting... Apr 26 01:40:05 192.168.122.209 [34556.066661] [tdb] Shutdown Tempesta DB Apr 26 01:40:06 192.168.122.209 [34556.361344] End test: tls.test_tls_integrity.CloseConnection.test8 Apr 26 01:40:06 192.168.122.209 [34556.376649] Start test: tls.test_tls_integrity.CloseConnection.test7 Apr 26 01:40:07 192.168.122.209 [34557.732866] [tdb] Start Tempesta DB Apr 26 01:40:07 192.168.122.209 [34557.871693] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:40:08 192.168.122.209 [34558.440259] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34558.440259] Maybe that's fine, but it's worth checking the [34558.440259] config - if there is no relations between the [34558.440259] names, then host name confusion attack is possible. Apr 26 01:40:08 192.168.122.209 [34558.538762] [tempesta fw] Configuration processing is completed. Apr 26 01:40:08 192.168.122.209 [34558.603883] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:40:08 192.168.122.209 [34558.639700] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:40:08 192.168.122.209 [34558.673785] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:40:08 192.168.122.209 [34558.718684] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:40:08 192.168.122.209 [34558.758618] [tempesta fw] Tempesta FW is ready Apr 26 01:40:09 192.168.122.209 [34559.323259] [tdb] Close table 'client0.tdb' Apr 26 01:40:09 192.168.122.209 [34559.495785] [tdb] Close table 'sessions0.tdb' Apr 26 01:40:09 192.168.122.209 [34559.747433] [tdb] Close table 'filter0.tdb' Apr 26 01:40:09 192.168.122.209 [34559.747860] [tempesta fw] modules are stopped Apr 26 01:40:09 192.168.122.209 [34559.953137] [tempesta fw] exiting... Apr 26 01:40:09 192.168.122.209 [34560.142001] [tdb] Shutdown Tempesta DB Apr 26 01:40:10 192.168.122.209 [34560.392602] End test: tls.test_tls_integrity.CloseConnection.test7 Apr 26 01:40:10 192.168.122.209 [34560.410591] Start test: tls.test_tls_integrity.CloseConnection.test6 Apr 26 01:40:11 192.168.122.209 [34561.829399] [tdb] Start Tempesta DB Apr 26 01:40:11 192.168.122.209 [34561.983598] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:40:12 192.168.122.209 [34562.616114] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34562.616114] Maybe that's fine, but it's worth checking the [34562.616114] config - if there is no relations between the [34562.616114] names, then host name confusion attack is possible. Apr 26 01:40:12 192.168.122.209 [34562.726793] [tempesta fw] Configuration processing is completed. Apr 26 01:40:12 192.168.122.209 [34562.787622] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:40:12 192.168.122.209 [34562.824835] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:40:12 192.168.122.209 [34562.858913] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:40:12 192.168.122.209 [34562.914683] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:40:12 192.168.122.209 [34562.954674] [tempesta fw] Tempesta FW is ready Apr 26 01:40:13 192.168.122.209 [34563.513636] [tdb] Close table 'client0.tdb' Apr 26 01:40:13 192.168.122.209 [34563.721758] [tdb] Close table 'sessions0.tdb' Apr 26 01:40:13 192.168.122.209 [34563.947358] [tdb] Close table 'filter0.tdb' Apr 26 01:40:13 192.168.122.209 [34563.947799] [tempesta fw] modules are stopped Apr 26 01:40:13 192.168.122.209 [34564.170585] [tempesta fw] exiting... Apr 26 01:40:14 192.168.122.209 [34564.284248] [tdb] Shutdown Tempesta DB Apr 26 01:40:14 192.168.122.209 [34564.520800] End test: tls.test_tls_integrity.CloseConnection.test6 Apr 26 01:40:14 192.168.122.209 [34564.537720] Start test: tls.test_tls_integrity.CloseConnection.test5 Apr 26 01:40:15 192.168.122.209 [34565.904334] [tdb] Start Tempesta DB Apr 26 01:40:15 192.168.122.209 [34566.057856] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:40:16 192.168.122.209 [34566.744085] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34566.744085] Maybe that's fine, but it's worth checking the [34566.744085] config - if there is no relations between the [34566.744085] names, then host name confusion attack is possible. Apr 26 01:40:16 192.168.122.209 [34566.850845] [tempesta fw] Configuration processing is completed. Apr 26 01:40:16 192.168.122.209 [34566.912398] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:40:16 192.168.122.209 [34566.948459] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:40:16 192.168.122.209 [34566.982947] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:40:16 192.168.122.209 [34567.018763] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:40:16 192.168.122.209 [34567.058720] [tempesta fw] Tempesta FW is ready Apr 26 01:40:17 192.168.122.209 [34567.748926] [tdb] Close table 'client0.tdb' Apr 26 01:40:17 192.168.122.209 [34567.932650] [tdb] Close table 'sessions0.tdb' Apr 26 01:40:17 192.168.122.209 [34568.166392] [tdb] Close table 'filter0.tdb' Apr 26 01:40:17 192.168.122.209 [34568.167200] [tempesta fw] modules are stopped Apr 26 01:40:18 192.168.122.209 [34568.372217] [tempesta fw] exiting... Apr 26 01:40:18 192.168.122.209 [34568.514238] [tdb] Shutdown Tempesta DB Apr 26 01:40:18 192.168.122.209 [34568.718119] End test: tls.test_tls_integrity.CloseConnection.test5 Apr 26 01:40:18 192.168.122.209 [34568.730408] Start test: tls.test_tls_integrity.CloseConnection.test4 Apr 26 01:40:19 192.168.122.209 [34570.024585] [tdb] Start Tempesta DB Apr 26 01:40:19 192.168.122.209 [34570.175127] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:40:20 192.168.122.209 [34570.776246] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34570.776246] Maybe that's fine, but it's worth checking the [34570.776246] config - if there is no relations between the [34570.776246] names, then host name confusion attack is possible. Apr 26 01:40:20 192.168.122.209 [34570.874949] [tempesta fw] Configuration processing is completed. Apr 26 01:40:20 192.168.122.209 [34570.942177] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:40:20 192.168.122.209 [34570.979317] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:40:20 192.168.122.209 [34571.012674] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:40:20 192.168.122.209 [34571.058822] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:40:20 192.168.122.209 [34571.110821] [tempesta fw] Tempesta FW is ready Apr 26 01:40:21 192.168.122.209 [34571.698091] [tdb] Close table 'client0.tdb' Apr 26 01:40:21 192.168.122.209 [34571.886504] [tdb] Close table 'sessions0.tdb' Apr 26 01:40:21 192.168.122.209 [34572.133411] [tdb] Close table 'filter0.tdb' Apr 26 01:40:21 192.168.122.209 [34572.133834] [tempesta fw] modules are stopped Apr 26 01:40:22 192.168.122.209 [34572.346894] [tempesta fw] exiting... Apr 26 01:40:22 192.168.122.209 [34572.474039] [tdb] Shutdown Tempesta DB Apr 26 01:40:22 192.168.122.209 [34572.704591] End test: tls.test_tls_integrity.CloseConnection.test4 Apr 26 01:40:22 192.168.122.209 [34572.723896] Start test: tls.test_tls_integrity.CloseConnection.test3 Apr 26 01:40:23 192.168.122.209 [34574.056124] [tdb] Start Tempesta DB Apr 26 01:40:23 192.168.122.209 [34574.219475] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:40:24 192.168.122.209 [34574.860193] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34574.860193] Maybe that's fine, but it's worth checking the [34574.860193] config - if there is no relations between the [34574.860193] names, then host name confusion attack is possible. Apr 26 01:40:24 192.168.122.209 [34574.958945] [tempesta fw] Configuration processing is completed. Apr 26 01:40:24 192.168.122.209 [34575.018110] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:40:24 192.168.122.209 [34575.053502] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:40:24 192.168.122.209 [34575.087819] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:40:24 192.168.122.209 [34575.130834] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:40:24 192.168.122.209 [34575.170847] [tempesta fw] Tempesta FW is ready Apr 26 01:40:25 192.168.122.209 [34575.749286] [tdb] Close table 'client0.tdb' Apr 26 01:40:25 192.168.122.209 [34575.930077] [tdb] Close table 'sessions0.tdb' Apr 26 01:40:25 192.168.122.209 [34576.189093] [tdb] Close table 'filter0.tdb' Apr 26 01:40:25 192.168.122.209 [34576.189505] [tempesta fw] modules are stopped Apr 26 01:40:26 192.168.122.209 [34576.432468] [tempesta fw] exiting... Apr 26 01:40:26 192.168.122.209 [34576.558157] [tdb] Shutdown Tempesta DB Apr 26 01:40:26 192.168.122.209 [34576.785377] End test: tls.test_tls_integrity.CloseConnection.test3 Apr 26 01:40:26 192.168.122.209 [34576.807420] Start test: tls.test_tls_integrity.CloseConnection.test2 Apr 26 01:40:27 192.168.122.209 [34578.006266] [tdb] Start Tempesta DB Apr 26 01:40:27 192.168.122.209 [34578.173770] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:40:28 192.168.122.209 [34578.792299] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34578.792299] Maybe that's fine, but it's worth checking the [34578.792299] config - if there is no relations between the [34578.792299] names, then host name confusion attack is possible. Apr 26 01:40:28 192.168.122.209 [34578.902922] [tempesta fw] Configuration processing is completed. Apr 26 01:40:28 192.168.122.209 [34578.982107] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:40:28 192.168.122.209 [34579.023197] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:40:28 192.168.122.209 [34579.060471] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:40:28 192.168.122.209 [34579.110957] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:40:28 192.168.122.209 [34579.170902] [tempesta fw] Tempesta FW is ready Apr 26 01:40:29 192.168.122.209 [34579.741043] [tdb] Close table 'client0.tdb' Apr 26 01:40:29 192.168.122.209 [34579.927889] [tdb] Close table 'sessions0.tdb' Apr 26 01:40:29 192.168.122.209 [34580.163775] [tdb] Close table 'filter0.tdb' Apr 26 01:40:29 192.168.122.209 [34580.164221] [tempesta fw] modules are stopped Apr 26 01:40:30 192.168.122.209 [34580.346906] [tempesta fw] exiting... Apr 26 01:40:30 192.168.122.209 [34580.483350] [tdb] Shutdown Tempesta DB Apr 26 01:40:30 192.168.122.209 [34580.699273] End test: tls.test_tls_integrity.CloseConnection.test2 Apr 26 01:40:30 192.168.122.209 [34580.719621] Start test: tls.test_tls_integrity.CloseConnection.test1 Apr 26 01:40:31 192.168.122.209 [34582.090653] [tdb] Start Tempesta DB Apr 26 01:40:32 192.168.122.209 [34582.262714] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:40:32 192.168.122.209 [34582.864295] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34582.864295] Maybe that's fine, but it's worth checking the [34582.864295] config - if there is no relations between the [34582.864295] names, then host name confusion attack is possible. Apr 26 01:40:32 192.168.122.209 [34582.979046] [tempesta fw] Configuration processing is completed. Apr 26 01:40:32 192.168.122.209 [34583.041055] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:40:32 192.168.122.209 [34583.076000] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:40:32 192.168.122.209 [34583.109377] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:40:32 192.168.122.209 [34583.171012] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:40:32 192.168.122.209 [34583.214957] [tempesta fw] Tempesta FW is ready Apr 26 01:40:33 192.168.122.209 [34583.743745] [tdb] Close table 'client0.tdb' Apr 26 01:40:33 192.168.122.209 [34583.928597] [tdb] Close table 'sessions0.tdb' Apr 26 01:40:33 192.168.122.209 [34584.208759] [tdb] Close table 'filter0.tdb' Apr 26 01:40:33 192.168.122.209 [34584.209293] [tempesta fw] modules are stopped Apr 26 01:40:34 192.168.122.209 [34584.405114] [tempesta fw] exiting... Apr 26 01:40:34 192.168.122.209 [34584.571235] [tdb] Shutdown Tempesta DB Apr 26 01:40:34 192.168.122.209 [34584.800894] End test: tls.test_tls_integrity.CloseConnection.test1 Apr 26 01:40:34 192.168.122.209 [34584.808757] Start test: tls.test_tls_integrity.CacheH2.test_various_req_resp_sizes Apr 26 01:40:35 192.168.122.209 [34586.142591] [tdb] Start Tempesta DB Apr 26 01:40:36 192.168.122.209 [34586.298118] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:40:36 192.168.122.209 [34586.912296] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34586.912296] Maybe that's fine, but it's worth checking the [34586.912296] config - if there is no relations between the [34586.912296] names, then host name confusion attack is possible. Apr 26 01:40:36 192.168.122.209 [34587.003019] [tempesta fw] Configuration processing is completed. Apr 26 01:40:36 192.168.122.209 [34587.063854] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:40:37 192.168.122.209 [34587.633956] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:40:37 192.168.122.209 [34587.703255] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:40:37 192.168.122.209 [34587.746466] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:40:37 192.168.122.209 [34587.835071] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:40:37 192.168.122.209 [34587.887020] [tempesta fw] Tempesta FW is ready Apr 26 01:40:39 192.168.122.209 [34589.554489] [tdb] Close table 'client0.tdb' Apr 26 01:40:39 192.168.122.209 [34589.750465] [tdb] Close table 'sessions0.tdb' Apr 26 01:40:42 192.168.122.209 [34593.062708] [tdb] Close table 'cache0.tdb' Apr 26 01:40:43 192.168.122.209 [34593.325972] [tdb] Close table 'filter0.tdb' Apr 26 01:40:43 192.168.122.209 [34593.326412] [tempesta fw] modules are stopped Apr 26 01:40:43 192.168.122.209 [34593.542560] [tempesta fw] exiting... Apr 26 01:40:43 192.168.122.209 [34593.713741] [tdb] Shutdown Tempesta DB Apr 26 01:40:43 192.168.122.209 [34593.967324] End test: tls.test_tls_integrity.CacheH2.test_various_req_resp_sizes Apr 26 01:40:43 192.168.122.209 [34593.983656] Start test: tls.test_tls_integrity.Cache.test_various_req_resp_sizes Apr 26 01:40:45 192.168.122.209 [34595.245652] [tdb] Start Tempesta DB Apr 26 01:40:45 192.168.122.209 [34595.415275] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:40:46 192.168.122.209 [34596.980426] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34596.980426] Maybe that's fine, but it's worth checking the [34596.980426] config - if there is no relations between the [34596.980426] names, then host name confusion attack is possible. Apr 26 01:40:46 192.168.122.209 [34597.103227] [tempesta fw] Configuration processing is completed. Apr 26 01:40:46 192.168.122.209 [34597.162876] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:40:47 192.168.122.209 [34597.613439] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:40:47 192.168.122.209 [34597.639946] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:40:47 192.168.122.209 [34597.665957] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:40:47 192.168.122.209 [34597.707190] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:40:47 192.168.122.209 [34597.751136] [tempesta fw] Tempesta FW is ready Apr 26 01:40:49 192.168.122.209 [34599.864021] [tdb] Close table 'client0.tdb' Apr 26 01:40:49 192.168.122.209 [34600.058299] [tdb] Close table 'sessions0.tdb' Apr 26 01:40:53 192.168.122.209 [34603.256206] [tdb] Close table 'cache0.tdb' Apr 26 01:40:53 192.168.122.209 [34603.524677] [tdb] Close table 'filter0.tdb' Apr 26 01:40:53 192.168.122.209 [34603.525111] [tempesta fw] modules are stopped Apr 26 01:40:53 192.168.122.209 [34603.698971] [tempesta fw] exiting... Apr 26 01:40:53 192.168.122.209 [34603.884454] [tdb] Shutdown Tempesta DB Apr 26 01:40:53 192.168.122.209 [34604.145466] End test: tls.test_tls_integrity.Cache.test_various_req_resp_sizes Apr 26 01:40:53 192.168.122.209 [34604.176150] Start test: tls.test_tls_handshake.TlsVhostHandshakeTest.test_vhost_sni Apr 26 01:40:55 192.168.122.209 [34605.640309] [tdb] Start Tempesta DB Apr 26 01:40:55 192.168.122.209 [34605.824832] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:40:57 192.168.122.209 [34607.764701] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34607.764701] Maybe that's fine, but it's worth checking the [34607.764701] config - if there is no relations between the [34607.764701] names, then host name confusion attack is possible. Apr 26 01:40:57 192.168.122.209 [34607.825490] [tempesta fw] Warning: Vhost vhost2.net doesn't have certificate with matching SAN/CN. [34607.825490] Maybe that's fine, but it's worth checking the [34607.825490] config - if there is no relations between the [34607.825490] names, then host name confusion attack is possible. Apr 26 01:40:57 192.168.122.209 [34607.891367] [tempesta fw] Configuration processing is completed. Apr 26 01:40:57 192.168.122.209 [34607.953828] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:40:57 192.168.122.209 [34607.990559] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:40:57 192.168.122.209 [34608.032995] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:40:57 192.168.122.209 [34608.091309] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:40:57 192.168.122.209 [34608.131283] [tempesta fw] Tempesta FW is ready Apr 26 01:40:58 192.168.122.209 [34608.293176] device enp1s0 entered promiscuous mode Apr 26 01:40:58 192.168.122.209 [34608.392050] device enp1s0 left promiscuous mode Apr 26 01:40:58 192.168.122.209 [34608.445070] device enp1s0 entered promiscuous mode Apr 26 01:40:58 192.168.122.209 [34608.575952] device enp1s0 left promiscuous mode Apr 26 01:40:58 192.168.122.209 [34609.151711] [tdb] Close table 'client0.tdb' Apr 26 01:40:59 192.168.122.209 [34609.377011] [tdb] Close table 'sessions0.tdb' Apr 26 01:40:59 192.168.122.209 [34609.617717] [tdb] Close table 'filter0.tdb' Apr 26 01:40:59 192.168.122.209 [34609.618168] [tempesta fw] modules are stopped Apr 26 01:40:59 192.168.122.209 [34609.891160] [tempesta fw] exiting... Apr 26 01:40:59 192.168.122.209 [34610.031601] [tdb] Shutdown Tempesta DB Apr 26 01:41:00 192.168.122.209 [34610.242422] End test: tls.test_tls_handshake.TlsVhostHandshakeTest.test_vhost_sni Apr 26 01:41:00 192.168.122.209 [34610.253661] Start test: tls.test_tls_handshake.TlsVhostHandshakeTest.test_empty_sni_default Apr 26 01:41:01 192.168.122.209 [34611.667367] [tdb] Start Tempesta DB Apr 26 01:41:01 192.168.122.209 [34611.813991] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:41:02 192.168.122.209 [34612.844709] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34612.844709] Maybe that's fine, but it's worth checking the [34612.844709] config - if there is no relations between the [34612.844709] names, then host name confusion attack is possible. Apr 26 01:41:02 192.168.122.209 [34612.905369] [tempesta fw] Warning: Vhost vhost2.net doesn't have certificate with matching SAN/CN. [34612.905369] Maybe that's fine, but it's worth checking the [34612.905369] config - if there is no relations between the [34612.905369] names, then host name confusion attack is possible. Apr 26 01:41:02 192.168.122.209 [34612.971370] [tempesta fw] Configuration processing is completed. Apr 26 01:41:02 192.168.122.209 [34613.033398] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:41:02 192.168.122.209 [34613.067786] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:41:02 192.168.122.209 [34613.099939] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:41:02 192.168.122.209 [34613.175403] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:41:02 192.168.122.209 [34613.215324] [tempesta fw] Tempesta FW is ready Apr 26 01:41:03 192.168.122.209 [34613.363110] device enp1s0 entered promiscuous mode Apr 26 01:41:03 192.168.122.209 [34613.405782] [tempesta fw] Warning: client 127.0.0.1 requested missing server name, reject connection. Apr 26 01:41:03 192.168.122.209 [34613.440059] device enp1s0 left promiscuous mode Apr 26 01:41:03 192.168.122.209 [34613.461901] device enp1s0 entered promiscuous mode Apr 26 01:41:03 192.168.122.209 [34613.560084] device enp1s0 left promiscuous mode Apr 26 01:41:03 192.168.122.209 [34614.109624] [tdb] Close table 'client0.tdb' Apr 26 01:41:04 192.168.122.209 [34614.306454] [tdb] Close table 'sessions0.tdb' Apr 26 01:41:04 192.168.122.209 [34614.543169] [tdb] Close table 'filter0.tdb' Apr 26 01:41:04 192.168.122.209 [34614.543637] [tempesta fw] modules are stopped Apr 26 01:41:04 192.168.122.209 [34614.837036] [tempesta fw] exiting... Apr 26 01:41:04 192.168.122.209 [34614.980903] [tdb] Shutdown Tempesta DB Apr 26 01:41:04 192.168.122.209 [34615.234746] End test: tls.test_tls_handshake.TlsVhostHandshakeTest.test_empty_sni_default Apr 26 01:41:05 192.168.122.209 [34615.248152] Start test: tls.test_tls_handshake.TlsVhostHandshakeTest.test_bad_host Apr 26 01:41:06 192.168.122.209 [34616.538156] [tdb] Start Tempesta DB Apr 26 01:41:06 192.168.122.209 [34616.677333] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:41:07 192.168.122.209 [34617.780753] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34617.780753] Maybe that's fine, but it's worth checking the [34617.780753] config - if there is no relations between the [34617.780753] names, then host name confusion attack is possible. Apr 26 01:41:07 192.168.122.209 [34617.845489] [tempesta fw] Warning: Vhost vhost2.net doesn't have certificate with matching SAN/CN. [34617.845489] Maybe that's fine, but it's worth checking the [34617.845489] config - if there is no relations between the [34617.845489] names, then host name confusion attack is possible. Apr 26 01:41:07 192.168.122.209 [34617.923503] [tempesta fw] Configuration processing is completed. Apr 26 01:41:07 192.168.122.209 [34617.985024] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:41:07 192.168.122.209 [34618.023340] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:41:07 192.168.122.209 [34618.056909] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:41:07 192.168.122.209 [34618.115493] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:41:07 192.168.122.209 [34618.155349] [tempesta fw] Tempesta FW is ready Apr 26 01:41:08 192.168.122.209 [34618.300842] device enp1s0 entered promiscuous mode Apr 26 01:41:08 192.168.122.209 [34618.387340] [tempesta fw] Warning: request has been filtered out via http table: 127.0.0.1 Apr 26 01:41:08 192.168.122.209 [34618.419385] device enp1s0 left promiscuous mode Apr 26 01:41:13 192.168.122.209 [34623.904341] [tdb] Close table 'client0.tdb' Apr 26 01:41:13 192.168.122.209 [34624.095668] [tdb] Close table 'sessions0.tdb' Apr 26 01:41:14 192.168.122.209 [34624.335038] [tdb] Close table 'filter0.tdb' Apr 26 01:41:14 192.168.122.209 [34624.335839] [tempesta fw] modules are stopped Apr 26 01:41:14 192.168.122.209 [34624.682750] [tempesta fw] exiting... Apr 26 01:41:14 192.168.122.209 [34624.838435] [tdb] Shutdown Tempesta DB Apr 26 01:41:16 192.168.122.209 [34627.125107] [tdb] Start Tempesta DB Apr 26 01:41:17 192.168.122.209 [34627.262262] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:41:18 192.168.122.209 [34628.281379] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34628.281379] Maybe that's fine, but it's worth checking the [34628.281379] config - if there is no relations between the [34628.281379] names, then host name confusion attack is possible. Apr 26 01:41:18 192.168.122.209 [34628.357547] [tempesta fw] Warning: Vhost vhost2.net doesn't have certificate with matching SAN/CN. [34628.357547] Maybe that's fine, but it's worth checking the [34628.357547] config - if there is no relations between the [34628.357547] names, then host name confusion attack is possible. Apr 26 01:41:18 192.168.122.209 [34628.439646] [tempesta fw] Configuration processing is completed. Apr 26 01:41:18 192.168.122.209 [34628.506673] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:41:18 192.168.122.209 [34628.544748] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:41:18 192.168.122.209 [34628.579130] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:41:18 192.168.122.209 [34628.651587] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:41:18 192.168.122.209 [34628.699553] [tempesta fw] Tempesta FW is ready Apr 26 01:41:18 192.168.122.209 [34628.855239] device enp1s0 entered promiscuous mode Apr 26 01:41:18 192.168.122.209 [34628.945939] [tempesta fw] Warning: request has been filtered out via http table: 127.0.0.1 Apr 26 01:41:18 192.168.122.209 [34628.964365] device enp1s0 left promiscuous mode Apr 26 01:41:24 192.168.122.209 [34634.441223] [tdb] Close table 'client0.tdb' Apr 26 01:41:24 192.168.122.209 [34634.649968] [tdb] Close table 'sessions0.tdb' Apr 26 01:41:24 192.168.122.209 [34634.889505] [tdb] Close table 'filter0.tdb' Apr 26 01:41:24 192.168.122.209 [34634.889935] [tempesta fw] modules are stopped Apr 26 01:41:24 192.168.122.209 [34635.184334] [tempesta fw] exiting... Apr 26 01:41:25 192.168.122.209 [34635.330467] [tdb] Shutdown Tempesta DB Apr 26 01:41:25 192.168.122.209 [34635.552039] End test: tls.test_tls_handshake.TlsVhostHandshakeTest.test_bad_host Apr 26 01:41:25 192.168.122.209 [34635.560831] Start test: tls.test_tls_handshake.TlsMissingDefaultKey.test Apr 26 01:41:26 192.168.122.209 [34636.797838] [tdb] Start Tempesta DB Apr 26 01:41:26 192.168.122.209 [34636.956423] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:41:27 192.168.122.209 [34637.748451] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [34637.748451] Maybe that's fine, but it's worth checking the [34637.748451] config - if there is no relations between the [34637.748451] names, then host name confusion attack is possible. Apr 26 01:41:27 192.168.122.209 [34637.799778] [tempesta fw] Configuration processing is completed. Apr 26 01:41:27 192.168.122.209 [34637.864447] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:41:27 192.168.122.209 [34637.901799] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:41:27 192.168.122.209 [34637.934466] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:41:27 192.168.122.209 [34637.975721] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:41:27 192.168.122.209 [34638.015649] [tempesta fw] Tempesta FW is ready Apr 26 01:41:27 192.168.122.209 [34638.148849] device enp1s0 entered promiscuous mode Apr 26 01:41:28 192.168.122.209 [34638.244075] device enp1s0 left promiscuous mode Apr 26 01:41:28 192.168.122.209 [34638.265775] device enp1s0 entered promiscuous mode Apr 26 01:41:28 192.168.122.209 [34638.314847] [tempesta fw] Warning: client 127.0.0.1 requested unknown server name 'example.com' in TLS SNI, reject connection. Apr 26 01:41:28 192.168.122.209 [34638.344397] device enp1s0 left promiscuous mode Apr 26 01:41:28 192.168.122.209 [34638.378349] device enp1s0 entered promiscuous mode Apr 26 01:41:28 192.168.122.209 [34638.426795] [tempesta fw] Warning: client 127.0.0.1 requested missing server name, reject connection. Apr 26 01:41:28 192.168.122.209 [34638.448417] device enp1s0 left promiscuous mode Apr 26 01:41:28 192.168.122.209 [34639.043992] [tdb] Close table 'client0.tdb' Apr 26 01:41:28 192.168.122.209 [34639.234041] [tdb] Close table 'sessions0.tdb' Apr 26 01:41:29 192.168.122.209 [34639.475627] [tdb] Close table 'filter0.tdb' Apr 26 01:41:29 192.168.122.209 [34639.476059] [tempesta fw] modules are stopped Apr 26 01:41:29 192.168.122.209 [34639.708976] [tempesta fw] exiting... Apr 26 01:41:29 192.168.122.209 [34639.860042] [tdb] Shutdown Tempesta DB Apr 26 01:41:29 192.168.122.209 [34640.085562] End test: tls.test_tls_handshake.TlsMissingDefaultKey.test Apr 26 01:41:29 192.168.122.209 [34640.108300] Start test: tls.test_tls_handshake.TlsHandshakeTest.test_tls12_synthetic Apr 26 01:41:31 192.168.122.209 [34641.458237] [tdb] Start Tempesta DB Apr 26 01:41:31 192.168.122.209 [34641.628049] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:41:32 192.168.122.209 [34642.445129] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34642.445129] Maybe that's fine, but it's worth checking the [34642.445129] config - if there is no relations between the [34642.445129] names, then host name confusion attack is possible. Apr 26 01:41:32 192.168.122.209 [34642.563793] [tempesta fw] Configuration processing is completed. Apr 26 01:41:32 192.168.122.209 [34642.631717] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:41:32 192.168.122.209 [34642.668326] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:41:32 192.168.122.209 [34642.703086] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:41:32 192.168.122.209 [34642.779809] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:41:32 192.168.122.209 [34642.819723] [tempesta fw] Tempesta FW is ready Apr 26 01:41:32 192.168.122.209 [34642.958512] device enp1s0 entered promiscuous mode Apr 26 01:41:32 192.168.122.209 [34643.076351] device enp1s0 left promiscuous mode Apr 26 01:41:33 192.168.122.209 [34643.512248] [tdb] Close table 'client0.tdb' Apr 26 01:41:33 192.168.122.209 [34643.706043] [tdb] Close table 'sessions0.tdb' Apr 26 01:41:33 192.168.122.209 [34643.943265] [tdb] Close table 'filter0.tdb' Apr 26 01:41:33 192.168.122.209 [34643.943702] [tempesta fw] modules are stopped Apr 26 01:41:33 192.168.122.209 [34644.155857] [tempesta fw] exiting... Apr 26 01:41:34 192.168.122.209 [34644.299168] [tdb] Shutdown Tempesta DB Apr 26 01:41:34 192.168.122.209 [34644.514282] End test: tls.test_tls_handshake.TlsHandshakeTest.test_tls12_synthetic Apr 26 01:41:34 192.168.122.209 [34644.532186] Start test: tls.test_tls_handshake.TlsHandshakeTest.test_regression_1 Apr 26 01:41:35 192.168.122.209 [34645.902224] [tdb] Start Tempesta DB Apr 26 01:41:35 192.168.122.209 [34646.055819] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:41:36 192.168.122.209 [34646.881109] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34646.881109] Maybe that's fine, but it's worth checking the [34646.881109] config - if there is no relations between the [34646.881109] names, then host name confusion attack is possible. Apr 26 01:41:36 192.168.122.209 [34647.003866] [tempesta fw] Configuration processing is completed. Apr 26 01:41:36 192.168.122.209 [34647.062212] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:41:36 192.168.122.209 [34647.095852] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:41:36 192.168.122.209 [34647.126780] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:41:36 192.168.122.209 [34647.183810] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:41:36 192.168.122.209 [34647.231771] [tempesta fw] Tempesta FW is ready Apr 26 01:41:37 192.168.122.209 [34647.370351] device enp1s0 entered promiscuous mode Apr 26 01:41:37 192.168.122.209 [34647.453846] [tempesta tls] Warning: [::ffff:127.0.0.1] TLS context isn't ready after handshake Apr 26 01:41:37 192.168.122.209 [34647.468205] device enp1s0 left promiscuous mode Apr 26 01:41:37 192.168.122.209 [34647.920320] [tdb] Close table 'client0.tdb' Apr 26 01:41:37 192.168.122.209 [34648.108146] [tdb] Close table 'sessions0.tdb' Apr 26 01:41:38 192.168.122.209 [34648.328207] [tdb] Close table 'filter0.tdb' Apr 26 01:41:38 192.168.122.209 [34648.328649] [tempesta fw] modules are stopped Apr 26 01:41:38 192.168.122.209 [34648.573323] [tempesta fw] exiting... Apr 26 01:41:38 192.168.122.209 [34648.702507] [tdb] Shutdown Tempesta DB Apr 26 01:41:38 192.168.122.209 [34648.943762] End test: tls.test_tls_handshake.TlsHandshakeTest.test_regression_1 Apr 26 01:41:38 192.168.122.209 [34648.952256] Start test: tls.test_tls_handshake.TlsHandshakeTest.test_old_handshakes Apr 26 01:41:40 192.168.122.209 [34650.318415] [tdb] Start Tempesta DB Apr 26 01:41:40 192.168.122.209 [34650.478098] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:41:41 192.168.122.209 [34651.255941] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34651.255941] Maybe that's fine, but it's worth checking the [34651.255941] config - if there is no relations between the [34651.255941] names, then host name confusion attack is possible. Apr 26 01:41:41 192.168.122.209 [34651.372335] [tempesta fw] Configuration processing is completed. Apr 26 01:41:41 192.168.122.209 [34651.429822] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:41:41 192.168.122.209 [34651.463233] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:41:41 192.168.122.209 [34651.495191] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:41:41 192.168.122.209 [34651.547901] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:41:41 192.168.122.209 [34651.595823] [tempesta fw] Tempesta FW is ready Apr 26 01:41:42 192.168.122.209 [34652.298688] [tdb] Close table 'client0.tdb' Apr 26 01:41:42 192.168.122.209 [34652.490602] [tdb] Close table 'sessions0.tdb' Apr 26 01:41:42 192.168.122.209 [34652.718920] [tdb] Close table 'filter0.tdb' Apr 26 01:41:42 192.168.122.209 [34652.719371] [tempesta fw] modules are stopped Apr 26 01:41:42 192.168.122.209 [34652.973286] [tempesta fw] exiting... Apr 26 01:41:42 192.168.122.209 [34653.119986] [tdb] Shutdown Tempesta DB Apr 26 01:41:43 192.168.122.209 [34653.306694] End test: tls.test_tls_handshake.TlsHandshakeTest.test_old_handshakes Apr 26 01:41:43 192.168.122.209 [34653.318873] Start test: tls.test_tls_handshake.TlsHandshakeTest.test_many_ciphers Apr 26 01:41:44 192.168.122.209 [34654.451796] [tdb] Start Tempesta DB Apr 26 01:41:44 192.168.122.209 [34654.597774] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:41:45 192.168.122.209 [34655.341251] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34655.341251] Maybe that's fine, but it's worth checking the [34655.341251] config - if there is no relations between the [34655.341251] names, then host name confusion attack is possible. Apr 26 01:41:45 192.168.122.209 [34655.464299] [tempesta fw] Configuration processing is completed. Apr 26 01:41:45 192.168.122.209 [34655.527775] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:41:45 192.168.122.209 [34655.567347] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:41:45 192.168.122.209 [34655.602277] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:41:45 192.168.122.209 [34655.644038] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:41:45 192.168.122.209 [34655.691877] [tempesta fw] Tempesta FW is ready Apr 26 01:41:45 192.168.122.209 [34655.908905] device enp1s0 entered promiscuous mode Apr 26 01:41:45 192.168.122.209 [34656.004165] device enp1s0 left promiscuous mode Apr 26 01:41:46 192.168.122.209 [34656.467405] [tdb] Close table 'client0.tdb' Apr 26 01:41:46 192.168.122.209 [34656.653704] [tdb] Close table 'sessions0.tdb' Apr 26 01:41:46 192.168.122.209 [34656.895309] [tdb] Close table 'filter0.tdb' Apr 26 01:41:46 192.168.122.209 [34656.895761] [tempesta fw] modules are stopped Apr 26 01:41:46 192.168.122.209 [34657.123956] [tempesta fw] exiting... Apr 26 01:41:47 192.168.122.209 [34657.241299] [tdb] Shutdown Tempesta DB Apr 26 01:41:47 192.168.122.209 [34657.474483] End test: tls.test_tls_handshake.TlsHandshakeTest.test_many_ciphers Apr 26 01:41:47 192.168.122.209 [34657.483994] Start test: tls.test_tls_handshake.TlsHandshakeTest.test_long_sni Apr 26 01:41:48 192.168.122.209 [34658.677265] [tdb] Start Tempesta DB Apr 26 01:41:48 192.168.122.209 [34658.822744] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:41:49 192.168.122.209 [34659.533367] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34659.533367] Maybe that's fine, but it's worth checking the [34659.533367] config - if there is no relations between the [34659.533367] names, then host name confusion attack is possible. Apr 26 01:41:49 192.168.122.209 [34659.640022] [tempesta fw] Configuration processing is completed. Apr 26 01:41:49 192.168.122.209 [34659.699179] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:41:49 192.168.122.209 [34659.734589] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:41:49 192.168.122.209 [34659.767657] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:41:49 192.168.122.209 [34659.811993] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:41:49 192.168.122.209 [34659.859941] [tempesta fw] Tempesta FW is ready Apr 26 01:41:49 192.168.122.209 [34660.004414] device enp1s0 entered promiscuous mode Apr 26 01:41:49 192.168.122.209 [34660.050667] [tempesta tls] Warning: [::ffff:127.0.0.1] ClientHello: bad extension size 1005 (remaining extensions size 1065) Apr 26 01:41:49 192.168.122.209 [34660.072436] device enp1s0 left promiscuous mode Apr 26 01:41:50 192.168.122.209 [34660.555229] [tdb] Close table 'client0.tdb' Apr 26 01:41:50 192.168.122.209 [34660.745501] [tdb] Close table 'sessions0.tdb' Apr 26 01:41:50 192.168.122.209 [34661.005085] [tdb] Close table 'filter0.tdb' Apr 26 01:41:50 192.168.122.209 [34661.005531] [tempesta fw] modules are stopped Apr 26 01:41:51 192.168.122.209 [34661.293079] [tempesta fw] exiting... Apr 26 01:41:51 192.168.122.209 [34661.452022] [tdb] Shutdown Tempesta DB Apr 26 01:41:51 192.168.122.209 [34661.705201] End test: tls.test_tls_handshake.TlsHandshakeTest.test_long_sni Apr 26 01:41:51 192.168.122.209 [34661.715499] Start test: tls.test_tls_handshake.TlsHandshakeTest.test_fuzzing Apr 26 01:41:52 192.168.122.209 [34662.818983] [tdb] Start Tempesta DB Apr 26 01:41:52 192.168.122.209 [34662.965618] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:41:53 192.168.122.209 [34663.729361] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34663.729361] Maybe that's fine, but it's worth checking the [34663.729361] config - if there is no relations between the [34663.729361] names, then host name confusion attack is possible. Apr 26 01:41:53 192.168.122.209 [34663.860084] [tempesta fw] Configuration processing is completed. Apr 26 01:41:53 192.168.122.209 [34663.930312] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:41:53 192.168.122.209 [34663.968511] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:41:53 192.168.122.209 [34664.001818] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:41:53 192.168.122.209 [34664.056059] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:41:53 192.168.122.209 [34664.107999] [tempesta fw] Tempesta FW is ready Apr 26 01:41:54 192.168.122.209 [34664.725714] [tdb] Close table 'client0.tdb' Apr 26 01:41:54 192.168.122.209 [34664.910203] [tdb] Close table 'sessions0.tdb' Apr 26 01:41:54 192.168.122.209 [34665.150034] [tdb] Close table 'filter0.tdb' Apr 26 01:41:54 192.168.122.209 [34665.150472] [tempesta fw] modules are stopped Apr 26 01:41:55 192.168.122.209 [34665.383211] [tempesta fw] exiting... Apr 26 01:41:55 192.168.122.209 [34665.541699] [tdb] Shutdown Tempesta DB Apr 26 01:41:55 192.168.122.209 [34665.805216] End test: tls.test_tls_handshake.TlsHandshakeTest.test_fuzzing Apr 26 01:41:55 192.168.122.209 [34665.814070] Start test: tls.test_tls_handshake.TlsHandshakeTest.test_empty_sni_default Apr 26 01:41:56 192.168.122.209 [34666.918386] [tdb] Start Tempesta DB Apr 26 01:41:56 192.168.122.209 [34667.064150] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:41:57 192.168.122.209 [34667.761361] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34667.761361] Maybe that's fine, but it's worth checking the [34667.761361] config - if there is no relations between the [34667.761361] names, then host name confusion attack is possible. Apr 26 01:41:57 192.168.122.209 [34667.884086] [tempesta fw] Configuration processing is completed. Apr 26 01:41:57 192.168.122.209 [34667.943659] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:41:57 192.168.122.209 [34667.974937] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:41:57 192.168.122.209 [34668.006123] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:41:57 192.168.122.209 [34668.056112] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:41:57 192.168.122.209 [34668.104053] [tempesta fw] Tempesta FW is ready Apr 26 01:41:57 192.168.122.209 [34668.237515] device enp1s0 entered promiscuous mode Apr 26 01:41:58 192.168.122.209 [34668.279373] [tempesta fw] Warning: client 127.0.0.1 requested missing server name, reject connection. Apr 26 01:41:58 192.168.122.209 [34668.296316] device enp1s0 left promiscuous mode Apr 26 01:41:58 192.168.122.209 [34668.735847] [tdb] Close table 'client0.tdb' Apr 26 01:41:58 192.168.122.209 [34668.913541] [tdb] Close table 'sessions0.tdb' Apr 26 01:41:58 192.168.122.209 [34669.145942] [tdb] Close table 'filter0.tdb' Apr 26 01:41:58 192.168.122.209 [34669.146391] [tempesta fw] modules are stopped Apr 26 01:41:59 192.168.122.209 [34669.385664] [tempesta fw] exiting... Apr 26 01:41:59 192.168.122.209 [34669.528137] [tdb] Shutdown Tempesta DB Apr 26 01:41:59 192.168.122.209 [34669.771372] End test: tls.test_tls_handshake.TlsHandshakeTest.test_empty_sni_default Apr 26 01:41:59 192.168.122.209 [34669.780550] Start test: tls.test_tls_handshake.TlsHandshakeTest.test_close_notify Apr 26 01:42:00 192.168.122.209 [34670.853023] [tdb] Start Tempesta DB Apr 26 01:42:00 192.168.122.209 [34670.981907] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:42:01 192.168.122.209 [34671.689478] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34671.689478] Maybe that's fine, but it's worth checking the [34671.689478] config - if there is no relations between the [34671.689478] names, then host name confusion attack is possible. Apr 26 01:42:01 192.168.122.209 [34671.808495] [tempesta fw] Configuration processing is completed. Apr 26 01:42:01 192.168.122.209 [34671.877509] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:42:01 192.168.122.209 [34671.917744] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:42:01 192.168.122.209 [34671.951187] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:42:01 192.168.122.209 [34672.004169] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:42:01 192.168.122.209 [34672.052131] [tempesta fw] Tempesta FW is ready Apr 26 01:42:01 192.168.122.209 [34672.192429] device enp1s0 entered promiscuous mode Apr 26 01:42:02 192.168.122.209 [34672.304563] device enp1s0 left promiscuous mode Apr 26 01:42:02 192.168.122.209 [34672.753919] [tdb] Close table 'client0.tdb' Apr 26 01:42:02 192.168.122.209 [34672.941686] [tdb] Close table 'sessions0.tdb' Apr 26 01:42:02 192.168.122.209 [34673.176694] [tdb] Close table 'filter0.tdb' Apr 26 01:42:02 192.168.122.209 [34673.177140] [tempesta fw] modules are stopped Apr 26 01:42:03 192.168.122.209 [34673.420932] [tempesta fw] exiting... Apr 26 01:42:03 192.168.122.209 [34673.581786] [tdb] Shutdown Tempesta DB Apr 26 01:42:03 192.168.122.209 [34673.814600] End test: tls.test_tls_handshake.TlsHandshakeTest.test_close_notify Apr 26 01:42:03 192.168.122.209 [34673.824717] Start test: tls.test_tls_handshake.TlsHandshakeTest.test_bad_sni Apr 26 01:42:04 192.168.122.209 [34674.975438] [tdb] Start Tempesta DB Apr 26 01:42:04 192.168.122.209 [34675.120521] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:42:05 192.168.122.209 [34675.818262] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34675.818262] Maybe that's fine, but it's worth checking the [34675.818262] config - if there is no relations between the [34675.818262] names, then host name confusion attack is possible. Apr 26 01:42:05 192.168.122.209 [34675.948267] [tempesta fw] Configuration processing is completed. Apr 26 01:42:05 192.168.122.209 [34676.019763] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:42:05 192.168.122.209 [34676.057794] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:42:05 192.168.122.209 [34676.093558] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:42:05 192.168.122.209 [34676.148218] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:42:05 192.168.122.209 [34676.196177] [tempesta fw] Tempesta FW is ready Apr 26 01:42:06 192.168.122.209 [34676.329315] device enp1s0 entered promiscuous mode Apr 26 01:42:06 192.168.122.209 [34676.379703] [tempesta fw] Warning: client 127.0.0.1 requested unknown server name 'badservername' in TLS SNI, reject connection. Apr 26 01:42:06 192.168.122.209 [34676.392407] device enp1s0 left promiscuous mode Apr 26 01:42:06 192.168.122.209 [34676.903481] [tdb] Close table 'client0.tdb' Apr 26 01:42:06 192.168.122.209 [34677.085971] [tdb] Close table 'sessions0.tdb' Apr 26 01:42:07 192.168.122.209 [34677.347785] [tdb] Close table 'filter0.tdb' Apr 26 01:42:07 192.168.122.209 [34677.348245] [tempesta fw] modules are stopped Apr 26 01:42:07 192.168.122.209 [34677.594382] [tempesta fw] exiting... Apr 26 01:42:07 192.168.122.209 [34677.749229] [tdb] Shutdown Tempesta DB Apr 26 01:42:07 192.168.122.209 [34677.999507] End test: tls.test_tls_handshake.TlsHandshakeTest.test_bad_sni Apr 26 01:42:07 192.168.122.209 [34678.012731] Start test: tls.test_tls_handshake.TlsHandshakeTest.test_bad_sign_algs Apr 26 01:42:08 192.168.122.209 [34679.161644] [tdb] Start Tempesta DB Apr 26 01:42:09 192.168.122.209 [34679.315210] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:42:09 192.168.122.209 [34680.053568] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34680.053568] Maybe that's fine, but it's worth checking the [34680.053568] config - if there is no relations between the [34680.053568] names, then host name confusion attack is possible. Apr 26 01:42:09 192.168.122.209 [34680.172324] [tempesta fw] Configuration processing is completed. Apr 26 01:42:09 192.168.122.209 [34680.233864] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:42:10 192.168.122.209 [34680.269359] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:42:10 192.168.122.209 [34680.301704] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:42:10 192.168.122.209 [34680.356269] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:42:10 192.168.122.209 [34680.396217] [tempesta fw] Tempesta FW is ready Apr 26 01:42:10 192.168.122.209 [34680.547984] device enp1s0 entered promiscuous mode Apr 26 01:42:10 192.168.122.209 [34680.598341] [tempesta tls] Warning: [::ffff:127.0.0.1] ClientHello: bad signature algorithm extension Apr 26 01:42:10 192.168.122.209 [34680.616473] device enp1s0 left promiscuous mode Apr 26 01:42:10 192.168.122.209 [34681.118411] [tdb] Close table 'client0.tdb' Apr 26 01:42:11 192.168.122.209 [34681.301806] [tdb] Close table 'sessions0.tdb' Apr 26 01:42:11 192.168.122.209 [34681.566862] [tdb] Close table 'filter0.tdb' Apr 26 01:42:11 192.168.122.209 [34681.567299] [tempesta fw] modules are stopped Apr 26 01:42:11 192.168.122.209 [34681.808781] [tempesta fw] exiting... Apr 26 01:42:11 192.168.122.209 [34681.966635] [tdb] Shutdown Tempesta DB Apr 26 01:42:11 192.168.122.209 [34682.191876] End test: tls.test_tls_handshake.TlsHandshakeTest.test_bad_sign_algs Apr 26 01:42:11 192.168.122.209 [34682.207097] Start test: tls.test_tls_handshake.TlsHandshakeTest.test_bad_renegotiation_info Apr 26 01:42:13 192.168.122.209 [34683.397474] [tdb] Start Tempesta DB Apr 26 01:42:13 192.168.122.209 [34683.534344] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:42:14 192.168.122.209 [34684.265594] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34684.265594] Maybe that's fine, but it's worth checking the [34684.265594] config - if there is no relations between the [34684.265594] names, then host name confusion attack is possible. Apr 26 01:42:14 192.168.122.209 [34684.376386] [tempesta fw] Configuration processing is completed. Apr 26 01:42:14 192.168.122.209 [34684.439556] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:42:14 192.168.122.209 [34684.477567] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:42:14 192.168.122.209 [34684.511336] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:42:14 192.168.122.209 [34684.552309] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:42:14 192.168.122.209 [34684.592211] [tempesta fw] Tempesta FW is ready Apr 26 01:42:14 192.168.122.209 [34684.731294] device enp1s0 entered promiscuous mode Apr 26 01:42:14 192.168.122.209 [34684.788710] [tempesta tls] Warning: [::ffff:127.0.0.1] ClientHello: bad renegotiation_info extension Apr 26 01:42:14 192.168.122.209 [34684.816590] device enp1s0 left promiscuous mode Apr 26 01:42:15 192.168.122.209 [34685.341787] [tdb] Close table 'client0.tdb' Apr 26 01:42:15 192.168.122.209 [34685.526276] [tdb] Close table 'sessions0.tdb' Apr 26 01:42:15 192.168.122.209 [34685.758414] [tdb] Close table 'filter0.tdb' Apr 26 01:42:15 192.168.122.209 [34685.758847] [tempesta fw] modules are stopped Apr 26 01:42:15 192.168.122.209 [34685.993775] [tempesta fw] exiting... Apr 26 01:42:15 192.168.122.209 [34686.131909] [tdb] Shutdown Tempesta DB Apr 26 01:42:16 192.168.122.209 [34686.357459] End test: tls.test_tls_handshake.TlsHandshakeTest.test_bad_renegotiation_info Apr 26 01:42:16 192.168.122.209 [34686.374166] Start test: tls.test_tls_handshake.TlsHandshakeTest.test_bad_elliptic_curves Apr 26 01:42:17 192.168.122.209 [34687.532430] [tdb] Start Tempesta DB Apr 26 01:42:17 192.168.122.209 [34687.691444] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:42:18 192.168.122.209 [34688.373679] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34688.373679] Maybe that's fine, but it's worth checking the [34688.373679] config - if there is no relations between the [34688.373679] names, then host name confusion attack is possible. Apr 26 01:42:18 192.168.122.209 [34688.484417] [tempesta fw] Configuration processing is completed. Apr 26 01:42:18 192.168.122.209 [34688.545679] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:42:18 192.168.122.209 [34688.583190] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:42:18 192.168.122.209 [34688.618039] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:42:18 192.168.122.209 [34688.660354] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:42:18 192.168.122.209 [34688.700320] [tempesta fw] Tempesta FW is ready Apr 26 01:42:18 192.168.122.209 [34688.830899] device enp1s0 entered promiscuous mode Apr 26 01:42:18 192.168.122.209 [34688.878026] [tempesta tls] Warning: [::ffff:127.0.0.1] None of the common ciphersuites is usable (e.g. no suitable certificate), like TLS-ECDHE-RSA-WITH-AES-256-GCM-SHA384 Apr 26 01:42:18 192.168.122.209 [34688.904990] device enp1s0 left promiscuous mode Apr 26 01:42:19 192.168.122.209 [34689.403834] [tdb] Close table 'client0.tdb' Apr 26 01:42:19 192.168.122.209 [34689.609021] [tdb] Close table 'sessions0.tdb' Apr 26 01:42:19 192.168.122.209 [34689.870312] [tdb] Close table 'filter0.tdb' Apr 26 01:42:19 192.168.122.209 [34689.870750] [tempesta fw] modules are stopped Apr 26 01:42:19 192.168.122.209 [34690.145787] [tempesta fw] exiting... Apr 26 01:42:20 192.168.122.209 [34690.342279] [tdb] Shutdown Tempesta DB Apr 26 01:42:20 192.168.122.209 [34690.585833] End test: tls.test_tls_handshake.TlsHandshakeTest.test_bad_elliptic_curves Apr 26 01:42:20 192.168.122.209 [34690.597112] Start test: tls.test_tls_handshake.TlsHandshakeTest.test_alert Apr 26 01:42:21 192.168.122.209 [34691.681108] [tdb] Start Tempesta DB Apr 26 01:42:21 192.168.122.209 [34691.838903] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:42:22 192.168.122.209 [34692.609783] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34692.609783] Maybe that's fine, but it's worth checking the [34692.609783] config - if there is no relations between the [34692.609783] names, then host name confusion attack is possible. Apr 26 01:42:22 192.168.122.209 [34692.756519] [tempesta fw] Configuration processing is completed. Apr 26 01:42:22 192.168.122.209 [34692.820613] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:42:22 192.168.122.209 [34692.860077] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:42:22 192.168.122.209 [34692.895846] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:42:22 192.168.122.209 [34692.940413] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:42:22 192.168.122.209 [34692.984313] [tempesta fw] Tempesta FW is ready Apr 26 01:42:22 192.168.122.209 [34693.115702] device enp1s0 entered promiscuous mode Apr 26 01:42:23 192.168.122.209 [34693.541556] device enp1s0 left promiscuous mode Apr 26 01:42:23 192.168.122.209 [34693.568282] device enp1s0 entered promiscuous mode Apr 26 01:42:23 192.168.122.209 [34693.976971] device enp1s0 left promiscuous mode Apr 26 01:42:23 192.168.122.209 [34694.011869] device enp1s0 entered promiscuous mode Apr 26 01:42:23 192.168.122.209 [34694.116568] device enp1s0 left promiscuous mode Apr 26 01:42:24 192.168.122.209 [34694.560148] [tdb] Close table 'client0.tdb' Apr 26 01:42:24 192.168.122.209 [34694.760028] [tdb] Close table 'sessions0.tdb' Apr 26 01:42:24 192.168.122.209 [34695.003780] [tdb] Close table 'filter0.tdb' Apr 26 01:42:24 192.168.122.209 [34695.004252] [tempesta fw] modules are stopped Apr 26 01:42:25 192.168.122.209 [34695.255065] [tempesta fw] exiting... Apr 26 01:42:25 192.168.122.209 [34695.393288] [tdb] Shutdown Tempesta DB Apr 26 01:42:25 192.168.122.209 [34695.611379] End test: tls.test_tls_handshake.TlsHandshakeTest.test_alert Apr 26 01:42:25 192.168.122.209 [34695.621804] Start test: tls.test_tls_handshake.TlsHandshakeTest.test_9byte_transfer Apr 26 01:42:26 192.168.122.209 [34696.790271] [tdb] Start Tempesta DB Apr 26 01:42:26 192.168.122.209 [34696.941713] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:42:27 192.168.122.209 [34697.697826] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34697.697826] Maybe that's fine, but it's worth checking the [34697.697826] config - if there is no relations between the [34697.697826] names, then host name confusion attack is possible. Apr 26 01:42:27 192.168.122.209 [34697.828551] [tempesta fw] Configuration processing is completed. Apr 26 01:42:27 192.168.122.209 [34697.893669] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:42:27 192.168.122.209 [34697.929914] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:42:27 192.168.122.209 [34697.963229] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:42:27 192.168.122.209 [34698.024493] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:42:27 192.168.122.209 [34698.064437] [tempesta fw] Tempesta FW is ready Apr 26 01:42:27 192.168.122.209 [34698.207923] device enp1s0 entered promiscuous mode Apr 26 01:42:28 192.168.122.209 [34698.296757] device enp1s0 left promiscuous mode Apr 26 01:42:28 192.168.122.209 [34698.718877] [tdb] Close table 'client0.tdb' Apr 26 01:42:28 192.168.122.209 [34698.915022] [tdb] Close table 'sessions0.tdb' Apr 26 01:42:28 192.168.122.209 [34699.174161] [tdb] Close table 'filter0.tdb' Apr 26 01:42:28 192.168.122.209 [34699.174606] [tempesta fw] modules are stopped Apr 26 01:42:29 192.168.122.209 [34699.388633] [tempesta fw] exiting... Apr 26 01:42:29 192.168.122.209 [34699.543035] [tdb] Shutdown Tempesta DB Apr 26 01:42:29 192.168.122.209 [34699.756731] End test: tls.test_tls_handshake.TlsHandshakeTest.test_9byte_transfer Apr 26 01:42:29 192.168.122.209 [34699.766496] Start test: tls.test_tls_handshake.TlsHandshakeTest.test_1byte_transfer Apr 26 01:42:30 192.168.122.209 [34700.926614] [tdb] Start Tempesta DB Apr 26 01:42:30 192.168.122.209 [34701.093996] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:42:31 192.168.122.209 [34701.837764] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34701.837764] Maybe that's fine, but it's worth checking the [34701.837764] config - if there is no relations between the [34701.837764] names, then host name confusion attack is possible. Apr 26 01:42:31 192.168.122.209 [34701.976611] [tempesta fw] Configuration processing is completed. Apr 26 01:42:31 192.168.122.209 [34702.039462] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:42:31 192.168.122.209 [34702.076922] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:42:31 192.168.122.209 [34702.109941] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:42:31 192.168.122.209 [34702.156537] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:42:31 192.168.122.209 [34702.204486] [tempesta fw] Tempesta FW is ready Apr 26 01:42:32 192.168.122.209 [34702.334257] device enp1s0 entered promiscuous mode Apr 26 01:42:32 192.168.122.209 [34702.428689] device enp1s0 left promiscuous mode Apr 26 01:42:32 192.168.122.209 [34702.866038] [tdb] Close table 'client0.tdb' Apr 26 01:42:32 192.168.122.209 [34703.048898] [tdb] Close table 'sessions0.tdb' Apr 26 01:42:33 192.168.122.209 [34703.258821] [tdb] Close table 'filter0.tdb' Apr 26 01:42:33 192.168.122.209 [34703.259288] [tempesta fw] modules are stopped Apr 26 01:42:33 192.168.122.209 [34703.517248] [tempesta fw] exiting... Apr 26 01:42:33 192.168.122.209 [34703.661060] [tdb] Shutdown Tempesta DB Apr 26 01:42:33 192.168.122.209 [34703.871131] End test: tls.test_tls_handshake.TlsHandshakeTest.test_1byte_transfer Apr 26 01:42:33 192.168.122.209 [34703.883699] Start test: tls.test_tls_handshake.TlsHandshakeTest.test_10byte_transfer Apr 26 01:42:34 192.168.122.209 [34704.988992] [tdb] Start Tempesta DB Apr 26 01:42:34 192.168.122.209 [34705.126547] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:42:35 192.168.122.209 [34705.833854] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34705.833854] Maybe that's fine, but it's worth checking the [34705.833854] config - if there is no relations between the [34705.833854] names, then host name confusion attack is possible. Apr 26 01:42:35 192.168.122.209 [34705.944886] [tempesta fw] Configuration processing is completed. Apr 26 01:42:35 192.168.122.209 [34706.007861] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:42:35 192.168.122.209 [34706.045085] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:42:35 192.168.122.209 [34706.078342] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:42:35 192.168.122.209 [34706.136592] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:42:35 192.168.122.209 [34706.180543] [tempesta fw] Tempesta FW is ready Apr 26 01:42:36 192.168.122.209 [34706.323679] device enp1s0 entered promiscuous mode Apr 26 01:42:36 192.168.122.209 [34706.420780] device enp1s0 left promiscuous mode Apr 26 01:42:36 192.168.122.209 [34706.846880] [tdb] Close table 'client0.tdb' Apr 26 01:42:36 192.168.122.209 [34707.032459] [tdb] Close table 'sessions0.tdb' Apr 26 01:42:37 192.168.122.209 [34707.272241] [tdb] Close table 'filter0.tdb' Apr 26 01:42:37 192.168.122.209 [34707.272701] [tempesta fw] modules are stopped Apr 26 01:42:37 192.168.122.209 [34707.468299] [tempesta fw] exiting... Apr 26 01:42:37 192.168.122.209 [34707.627876] [tdb] Shutdown Tempesta DB Apr 26 01:42:37 192.168.122.209 [34707.845533] End test: tls.test_tls_handshake.TlsHandshakeTest.test_10byte_transfer Apr 26 01:42:37 192.168.122.209 [34707.861718] Start test: tls.test_tls_handshake.TlsCertReconfig.test Apr 26 01:42:38 192.168.122.209 [34708.948527] [tdb] Start Tempesta DB Apr 26 01:42:38 192.168.122.209 [34709.098925] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:42:39 192.168.122.209 [34709.853918] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34709.853918] Maybe that's fine, but it's worth checking the [34709.853918] config - if there is no relations between the [34709.853918] names, then host name confusion attack is possible. Apr 26 01:42:39 192.168.122.209 [34709.980688] [tempesta fw] Configuration processing is completed. Apr 26 01:42:39 192.168.122.209 [34710.050109] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:42:39 192.168.122.209 [34710.086979] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:42:39 192.168.122.209 [34710.119760] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:42:39 192.168.122.209 [34710.164619] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:42:39 192.168.122.209 [34710.204609] [tempesta fw] Tempesta FW is ready Apr 26 01:42:40 192.168.122.209 [34710.352327] device enp1s0 entered promiscuous mode Apr 26 01:42:40 192.168.122.209 [34710.444941] device enp1s0 left promiscuous mode Apr 26 01:42:40 192.168.122.209 [34710.973977] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 01:42:40 192.168.122.209 [34711.017924] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34711.017924] Maybe that's fine, but it's worth checking the [34711.017924] config - if there is no relations between the [34711.017924] names, then host name confusion attack is possible. Apr 26 01:42:40 192.168.122.209 [34711.176711] [tempesta fw] Configuration processing is completed. Apr 26 01:42:41 192.168.122.209 [34711.437285] [tempesta fw] Tempesta FW is ready Apr 26 01:42:41 192.168.122.209 [34711.488171] device enp1s0 entered promiscuous mode Apr 26 01:42:41 192.168.122.209 [34711.584851] device enp1s0 left promiscuous mode Apr 26 01:42:41 192.168.122.209 [34712.033727] [tdb] Close table 'client0.tdb' Apr 26 01:42:42 192.168.122.209 [34712.242600] [tdb] Close table 'sessions0.tdb' Apr 26 01:42:42 192.168.122.209 [34712.502671] [tdb] Close table 'filter0.tdb' Apr 26 01:42:42 192.168.122.209 [34712.503163] [tempesta fw] modules are stopped Apr 26 01:42:42 192.168.122.209 [34712.755944] [tempesta fw] exiting... Apr 26 01:42:42 192.168.122.209 [34712.908651] [tdb] Shutdown Tempesta DB Apr 26 01:42:42 192.168.122.209 [34713.119489] End test: tls.test_tls_handshake.TlsCertReconfig.test Apr 26 01:42:42 192.168.122.209 [34713.141501] Start test: tls.test_tls_cert.WrkTestsMultipleVhosts.test_wrk Apr 26 01:42:44 192.168.122.209 [34714.502788] [tdb] Start Tempesta DB Apr 26 01:42:44 192.168.122.209 [34714.639805] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:42:45 192.168.122.209 [34715.458970] [tempesta fw] Warning: Vhost localhost doesn't have certificate with matching SAN/CN. [34715.458970] Maybe that's fine, but it's worth checking the [34715.458970] config - if there is no relations between the [34715.458970] names, then host name confusion attack is possible. Apr 26 01:42:45 192.168.122.209 [34715.486891] [tempesta fw] Warning: Vhost private.example.com doesn't have certificate with matching SAN/CN. [34715.486891] Maybe that's fine, but it's worth checking the [34715.486891] config - if there is no relations between the [34715.486891] names, then host name confusion attack is possible. Apr 26 01:42:45 192.168.122.209 [34715.552777] [tempesta fw] Configuration processing is completed. Apr 26 01:42:45 192.168.122.209 [34715.613533] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:42:45 192.168.122.209 [34715.649628] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:42:45 192.168.122.209 [34715.685570] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:42:45 192.168.122.209 [34715.756750] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:42:45 192.168.122.209 [34715.804679] [tempesta fw] Tempesta FW is ready Apr 26 01:42:46 192.168.122.209 [34716.991619] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 01:42:46 192.168.122.209 [34717.117556] [tempesta fw] Warning: Vhost private.example.com doesn't have certificate with matching SAN/CN. [34717.117556] Maybe that's fine, but it's worth checking the [34717.117556] config - if there is no relations between the [34717.117556] names, then host name confusion attack is possible. Apr 26 01:42:46 192.168.122.209 [34717.141532] [tempesta fw] Warning: Vhost localhost doesn't have certificate with matching SAN/CN. [34717.141532] Maybe that's fine, but it's worth checking the [34717.141532] config - if there is no relations between the [34717.141532] names, then host name confusion attack is possible. Apr 26 01:42:46 192.168.122.209 [34717.220729] [tempesta fw] Configuration processing is completed. Apr 26 01:42:47 192.168.122.209 [34717.584552] [tempesta fw] Tempesta FW is ready Apr 26 01:42:48 192.168.122.209 [34718.503658] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 01:42:48 192.168.122.209 [34718.617379] [tempesta fw] Warning: Vhost localhost doesn't have certificate with matching SAN/CN. [34718.617379] Maybe that's fine, but it's worth checking the [34718.617379] config - if there is no relations between the [34718.617379] names, then host name confusion attack is possible. Apr 26 01:42:48 192.168.122.209 [34718.641745] [tempesta fw] Warning: Vhost private.example.com doesn't have certificate with matching SAN/CN. [34718.641745] Maybe that's fine, but it's worth checking the [34718.641745] config - if there is no relations between the [34718.641745] names, then host name confusion attack is possible. Apr 26 01:42:48 192.168.122.209 [34718.716833] [tempesta fw] Configuration processing is completed. Apr 26 01:42:48 192.168.122.209 [34719.092948] [tempesta fw] Tempesta FW is ready Apr 26 01:42:49 192.168.122.209 [34720.174534] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 01:42:50 192.168.122.209 [34720.290483] [tempesta fw] Warning: Vhost private.example.com doesn't have certificate with matching SAN/CN. [34720.290483] Maybe that's fine, but it's worth checking the [34720.290483] config - if there is no relations between the [34720.290483] names, then host name confusion attack is possible. Apr 26 01:42:50 192.168.122.209 [34720.785061] [tempesta fw] Tempesta FW is ready Apr 26 01:42:51 192.168.122.209 [34722.209233] [tempesta fw] Tempesta FW is ready Apr 26 01:42:52 192.168.122.209 [34723.104687] net_ratelimit: 6 callbacks suppressed Apr 26 01:42:52 192.168.122.209 [34723.104689] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 01:42:52 192.168.122.209 [34723.201524] [tempesta fw] Warning: Vhost private.example.com doesn't have certificate with matching SAN/CN. [34723.201524] Maybe that's fine, but it's worth checking the [34723.201524] config - if there is no relations between the [34723.201524] names, then host name confusion attack is possible. Apr 26 01:42:52 192.168.122.209 [34723.229511] [tempesta fw] Warning: Vhost localhost doesn't have certificate with matching SAN/CN. [34723.229511] Maybe that's fine, but it's worth checking the [34723.229511] config - if there is no relations between the [34723.229511] names, then host name confusion attack is possible. Apr 26 01:42:53 192.168.122.209 [34723.312782] [tempesta fw] Configuration processing is completed. Apr 26 01:42:53 192.168.122.209 [34723.616912] [tempesta fw] Tempesta FW is ready Apr 26 01:42:54 192.168.122.209 [34724.998891] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 01:42:54 192.168.122.209 [34725.093742] [tempesta fw] Warning: Vhost localhost doesn't have certificate with matching SAN/CN. [34725.093742] Maybe that's fine, but it's worth checking the [34725.093742] config - if there is no relations between the [34725.093742] names, then host name confusion attack is possible. Apr 26 01:42:54 192.168.122.209 [34725.123188] [tempesta fw] Warning: Vhost private.example.com doesn't have certificate with matching SAN/CN. [34725.123188] Maybe that's fine, but it's worth checking the [34725.123188] config - if there is no relations between the [34725.123188] names, then host name confusion attack is possible. Apr 26 01:42:54 192.168.122.209 [34725.192748] [tempesta fw] Configuration processing is completed. Apr 26 01:42:55 192.168.122.209 [34725.493428] [tempesta fw] Tempesta FW is ready Apr 26 01:42:56 192.168.122.209 [34726.332226] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 01:42:56 192.168.122.209 [34726.426930] [tempesta fw] Warning: Vhost private.example.com doesn't have certificate with matching SAN/CN. [34726.426930] Maybe that's fine, but it's worth checking the [34726.426930] config - if there is no relations between the [34726.426930] names, then host name confusion attack is possible. Apr 26 01:42:56 192.168.122.209 [34726.709242] [tempesta fw] Tempesta FW is ready Apr 26 01:42:57 192.168.122.209 [34727.725241] [tempesta fw] Tempesta FW is ready Apr 26 01:42:58 192.168.122.209 [34728.471492] net_ratelimit: 6 callbacks suppressed Apr 26 01:42:58 192.168.122.209 [34728.471496] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 01:42:58 192.168.122.209 [34728.573894] [tempesta fw] Warning: Vhost private.example.com doesn't have certificate with matching SAN/CN. [34728.573894] Maybe that's fine, but it's worth checking the [34728.573894] config - if there is no relations between the [34728.573894] names, then host name confusion attack is possible. Apr 26 01:42:58 192.168.122.209 [34728.597859] [tempesta fw] Warning: Vhost localhost doesn't have certificate with matching SAN/CN. [34728.597859] Maybe that's fine, but it's worth checking the [34728.597859] config - if there is no relations between the [34728.597859] names, then host name confusion attack is possible. Apr 26 01:42:58 192.168.122.209 [34728.660948] [tempesta fw] Configuration processing is completed. Apr 26 01:42:58 192.168.122.209 [34728.821308] [tempesta fw] Tempesta FW is ready Apr 26 01:42:59 192.168.122.209 [34729.481715] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 01:42:59 192.168.122.209 [34729.558924] [tempesta fw] Warning: Vhost localhost doesn't have certificate with matching SAN/CN. [34729.558924] Maybe that's fine, but it's worth checking the [34729.558924] config - if there is no relations between the [34729.558924] names, then host name confusion attack is possible. Apr 26 01:42:59 192.168.122.209 [34729.586893] [tempesta fw] Warning: Vhost private.example.com doesn't have certificate with matching SAN/CN. [34729.586893] Maybe that's fine, but it's worth checking the [34729.586893] config - if there is no relations between the [34729.586893] names, then host name confusion attack is possible. Apr 26 01:42:59 192.168.122.209 [34729.676922] [tempesta fw] Configuration processing is completed. Apr 26 01:42:59 192.168.122.209 [34729.841349] [tempesta fw] Tempesta FW is ready Apr 26 01:43:00 192.168.122.209 [34730.332633] [tdb] Close table 'client0.tdb' Apr 26 01:43:00 192.168.122.209 [34730.525389] [tdb] Close table 'sessions0.tdb' Apr 26 01:43:00 192.168.122.209 [34730.753728] [tdb] Close table 'filter0.tdb' Apr 26 01:43:00 192.168.122.209 [34730.754186] [tempesta fw] modules are stopped Apr 26 01:43:00 192.168.122.209 [34730.993980] [tempesta fw] exiting... Apr 26 01:43:00 192.168.122.209 [34731.121842] [tdb] Shutdown Tempesta DB Apr 26 01:43:01 192.168.122.209 [34731.371261] End test: tls.test_tls_cert.WrkTestsMultipleVhosts.test_wrk Apr 26 01:43:01 192.168.122.209 [34731.385124] Start test: tls.test_tls_cert.TlsSniWithHttpTableMultiH2.test_alternating_access Apr 26 01:43:02 192.168.122.209 [34732.734320] [tdb] Start Tempesta DB Apr 26 01:43:02 192.168.122.209 [34732.874635] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:43:03 192.168.122.209 [34733.963084] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [34733.963084] Maybe that's fine, but it's worth checking the [34733.963084] config - if there is no relations between the [34733.963084] names, then host name confusion attack is possible. Apr 26 01:43:03 192.168.122.209 [34734.073093] [tempesta fw] Configuration processing is completed. Apr 26 01:43:03 192.168.122.209 [34734.134241] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:43:03 192.168.122.209 [34734.172740] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:43:03 192.168.122.209 [34734.205714] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:43:04 192.168.122.209 [34734.301824] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:43:04 192.168.122.209 [34734.348931] [tempesta fw] Tempesta FW is ready Apr 26 01:43:04 192.168.122.209 [34734.532277] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.2 ('example.com' vs 'localhost-vhost') Apr 26 01:43:04 192.168.122.209 [34734.535790] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 01:43:04 192.168.122.209 [34735.075616] [tdb] Close table 'client0.tdb' Apr 26 01:43:05 192.168.122.209 [34735.268165] [tdb] Close table 'sessions0.tdb' Apr 26 01:43:05 192.168.122.209 [34735.479041] [tdb] Close table 'filter0.tdb' Apr 26 01:43:05 192.168.122.209 [34735.479479] [tempesta fw] modules are stopped Apr 26 01:43:05 192.168.122.209 [34735.727123] [tempesta fw] exiting... Apr 26 01:43:05 192.168.122.209 [34735.884366] [tdb] Shutdown Tempesta DB Apr 26 01:43:05 192.168.122.209 [34736.111262] End test: tls.test_tls_cert.TlsSniWithHttpTableMultiH2.test_alternating_access Apr 26 01:43:05 192.168.122.209 [34736.126833] Start test: tls.test_tls_cert.TlsSniWithHttpTableMulti.test_alternating_access Apr 26 01:43:07 192.168.122.209 [34737.443986] [tdb] Start Tempesta DB Apr 26 01:43:07 192.168.122.209 [34737.599884] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:43:08 192.168.122.209 [34738.695094] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [34738.695094] Maybe that's fine, but it's worth checking the [34738.695094] config - if there is no relations between the [34738.695094] names, then host name confusion attack is possible. Apr 26 01:43:08 192.168.122.209 [34738.797179] [tempesta fw] Configuration processing is completed. Apr 26 01:43:08 192.168.122.209 [34738.863387] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:43:08 192.168.122.209 [34738.902355] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:43:08 192.168.122.209 [34738.935358] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:43:08 192.168.122.209 [34739.005074] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:43:08 192.168.122.209 [34739.049010] [tempesta fw] Tempesta FW is ready Apr 26 01:43:08 192.168.122.209 [34739.200523] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.2 ('example.com' vs 'localhost-vhost') Apr 26 01:43:08 192.168.122.209 [34739.203306] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 01:43:09 192.168.122.209 [34739.705879] [tdb] Close table 'client0.tdb' Apr 26 01:43:09 192.168.122.209 [34739.919660] [tdb] Close table 'sessions0.tdb' Apr 26 01:43:09 192.168.122.209 [34740.160114] [tdb] Close table 'filter0.tdb' Apr 26 01:43:09 192.168.122.209 [34740.160555] [tempesta fw] modules are stopped Apr 26 01:43:10 192.168.122.209 [34740.427959] [tempesta fw] exiting... Apr 26 01:43:10 192.168.122.209 [34740.624618] [tdb] Shutdown Tempesta DB Apr 26 01:43:10 192.168.122.209 [34740.842652] End test: tls.test_tls_cert.TlsSniWithHttpTableMulti.test_alternating_access Apr 26 01:43:10 192.168.122.209 [34740.863830] Start test: tls.test_tls_cert.TlsSniWithHttpTable.test_with_san Apr 26 01:43:11 192.168.122.209 [34742.151220] [tdb] Start Tempesta DB Apr 26 01:43:12 192.168.122.209 [34742.317590] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:43:13 192.168.122.209 [34743.866965] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [34743.866965] Maybe that's fine, but it's worth checking the [34743.866965] config - if there is no relations between the [34743.866965] names, then host name confusion attack is possible. Apr 26 01:43:13 192.168.122.209 [34743.895244] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [34743.895244] Maybe that's fine, but it's worth checking the [34743.895244] config - if there is no relations between the [34743.895244] names, then host name confusion attack is possible. Apr 26 01:43:13 192.168.122.209 [34744.021196] [tempesta fw] Configuration processing is completed. Apr 26 01:43:13 192.168.122.209 [34744.082197] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:43:13 192.168.122.209 [34744.128935] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:43:13 192.168.122.209 [34744.167545] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:43:14 192.168.122.209 [34744.277121] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:43:14 192.168.122.209 [34744.341065] [tempesta fw] Tempesta FW is ready Apr 26 01:43:14 192.168.122.209 [34744.496670] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.2 ('tempesta-tech.com' vs 'localhost-vhost') Apr 26 01:43:14 192.168.122.209 [34744.500261] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 01:43:14 192.168.122.209 [34745.208442] [tdb] Close table 'client0.tdb' Apr 26 01:43:15 192.168.122.209 [34745.407939] [tdb] Close table 'sessions0.tdb' Apr 26 01:43:15 192.168.122.209 [34745.659137] [tdb] Close table 'filter0.tdb' Apr 26 01:43:15 192.168.122.209 [34745.659580] [tempesta fw] modules are stopped Apr 26 01:43:15 192.168.122.209 [34745.981530] [tempesta fw] exiting... Apr 26 01:43:15 192.168.122.209 [34746.145894] [tdb] Shutdown Tempesta DB Apr 26 01:43:16 192.168.122.209 [34746.382373] End test: tls.test_tls_cert.TlsSniWithHttpTable.test_with_san Apr 26 01:43:16 192.168.122.209 [34746.392645] Start test: tls.test_tls_cert.TlsSniWithHttpTable.test_with_common_name Apr 26 01:43:17 192.168.122.209 [34747.817904] [tdb] Start Tempesta DB Apr 26 01:43:17 192.168.122.209 [34747.966045] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:43:19 192.168.122.209 [34749.427176] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [34749.427176] Maybe that's fine, but it's worth checking the [34749.427176] config - if there is no relations between the [34749.427176] names, then host name confusion attack is possible. Apr 26 01:43:19 192.168.122.209 [34749.450488] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [34749.450488] Maybe that's fine, but it's worth checking the [34749.450488] config - if there is no relations between the [34749.450488] names, then host name confusion attack is possible. Apr 26 01:43:19 192.168.122.209 [34749.545223] [tempesta fw] Configuration processing is completed. Apr 26 01:43:19 192.168.122.209 [34749.605463] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:43:19 192.168.122.209 [34749.640634] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:43:19 192.168.122.209 [34749.674948] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:43:19 192.168.122.209 [34749.813177] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:43:19 192.168.122.209 [34749.857114] [tempesta fw] Tempesta FW is ready Apr 26 01:43:19 192.168.122.209 [34750.018098] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.2 ('tempesta-tech.com' vs 'localhost-vhost') Apr 26 01:43:19 192.168.122.209 [34750.021663] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 01:43:20 192.168.122.209 [34750.760322] [tdb] Close table 'client0.tdb' Apr 26 01:43:20 192.168.122.209 [34750.995727] [tdb] Close table 'sessions0.tdb' Apr 26 01:43:20 192.168.122.209 [34751.238545] [tdb] Close table 'filter0.tdb' Apr 26 01:43:20 192.168.122.209 [34751.238993] [tempesta fw] modules are stopped Apr 26 01:43:21 192.168.122.209 [34751.572906] [tempesta fw] exiting... Apr 26 01:43:21 192.168.122.209 [34751.707050] [tdb] Shutdown Tempesta DB Apr 26 01:43:21 192.168.122.209 [34751.942692] End test: tls.test_tls_cert.TlsSniWithHttpTable.test_with_common_name Apr 26 01:43:21 192.168.122.209 [34751.967033] Start test: tls.test_tls_cert.TlsSniWithHttpTable.test_with_any_host Apr 26 01:43:23 192.168.122.209 [34753.258108] [tdb] Start Tempesta DB Apr 26 01:43:23 192.168.122.209 [34753.398721] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:43:24 192.168.122.209 [34754.863171] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [34754.863171] Maybe that's fine, but it's worth checking the [34754.863171] config - if there is no relations between the [34754.863171] names, then host name confusion attack is possible. Apr 26 01:43:24 192.168.122.209 [34754.895325] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [34754.895325] Maybe that's fine, but it's worth checking the [34754.895325] config - if there is no relations between the [34754.895325] names, then host name confusion attack is possible. Apr 26 01:43:24 192.168.122.209 [34755.005227] [tempesta fw] Configuration processing is completed. Apr 26 01:43:24 192.168.122.209 [34755.065711] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:43:24 192.168.122.209 [34755.102823] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:43:24 192.168.122.209 [34755.135702] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:43:24 192.168.122.209 [34755.237210] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:43:25 192.168.122.209 [34755.285231] [tempesta fw] Tempesta FW is ready Apr 26 01:43:25 192.168.122.209 [34755.435242] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.2 ('tempesta-tech.com' vs 'default-vhost') Apr 26 01:43:25 192.168.122.209 [34755.436760] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 01:43:25 192.168.122.209 [34756.149874] [tdb] Close table 'client0.tdb' Apr 26 01:43:26 192.168.122.209 [34756.324987] [tdb] Close table 'sessions0.tdb' Apr 26 01:43:26 192.168.122.209 [34756.553007] [tdb] Close table 'filter0.tdb' Apr 26 01:43:26 192.168.122.209 [34756.553459] [tempesta fw] modules are stopped Apr 26 01:43:26 192.168.122.209 [34756.839463] [tempesta fw] exiting... Apr 26 01:43:26 192.168.122.209 [34756.983850] [tdb] Shutdown Tempesta DB Apr 26 01:43:26 192.168.122.209 [34757.240079] End test: tls.test_tls_cert.TlsSniWithHttpTable.test_with_any_host Apr 26 01:43:27 192.168.122.209 [34757.251525] Start test: tls.test_tls_cert.TlsSniWithHttpTable.test_valid Apr 26 01:43:28 192.168.122.209 [34758.579023] [tdb] Start Tempesta DB Apr 26 01:43:28 192.168.122.209 [34758.731580] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:43:30 192.168.122.209 [34760.235446] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [34760.235446] Maybe that's fine, but it's worth checking the [34760.235446] config - if there is no relations between the [34760.235446] names, then host name confusion attack is possible. Apr 26 01:43:30 192.168.122.209 [34760.262496] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [34760.262496] Maybe that's fine, but it's worth checking the [34760.262496] config - if there is no relations between the [34760.262496] names, then host name confusion attack is possible. Apr 26 01:43:30 192.168.122.209 [34760.365369] [tempesta fw] Configuration processing is completed. Apr 26 01:43:30 192.168.122.209 [34760.433435] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:43:30 192.168.122.209 [34760.468675] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:43:30 192.168.122.209 [34760.501174] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:43:30 192.168.122.209 [34760.617319] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:43:30 192.168.122.209 [34760.657308] [tempesta fw] Tempesta FW is ready Apr 26 01:43:31 192.168.122.209 [34761.502518] [tdb] Close table 'client0.tdb' Apr 26 01:43:31 192.168.122.209 [34761.726516] [tdb] Close table 'sessions0.tdb' Apr 26 01:43:31 192.168.122.209 [34761.949365] [tdb] Close table 'filter0.tdb' Apr 26 01:43:31 192.168.122.209 [34761.949791] [tempesta fw] modules are stopped Apr 26 01:43:31 192.168.122.209 [34762.212266] [tempesta fw] exiting... Apr 26 01:43:32 192.168.122.209 [34762.369112] [tdb] Shutdown Tempesta DB Apr 26 01:43:32 192.168.122.209 [34762.618483] End test: tls.test_tls_cert.TlsSniWithHttpTable.test_valid Apr 26 01:43:32 192.168.122.209 [34762.635092] Start test: tls.test_tls_cert.TlsCertSelectBySanwitMultipleSections.test Apr 26 01:43:33 192.168.122.209 [34763.873416] [tdb] Start Tempesta DB Apr 26 01:43:33 192.168.122.209 [34764.035072] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:43:34 192.168.122.209 [34764.832199] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [34764.832199] Maybe that's fine, but it's worth checking the [34764.832199] config - if there is no relations between the [34764.832199] names, then host name confusion attack is possible. Apr 26 01:43:34 192.168.122.209 [34764.863568] [tempesta fw] Warning: Vhost private.example.com doesn't have certificate with matching SAN/CN. [34764.863568] Maybe that's fine, but it's worth checking the [34764.863568] config - if there is no relations between the [34764.863568] names, then host name confusion attack is possible. Apr 26 01:43:34 192.168.122.209 [34764.917422] [tempesta fw] Configuration processing is completed. Apr 26 01:43:34 192.168.122.209 [34764.983185] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:43:34 192.168.122.209 [34765.024343] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:43:34 192.168.122.209 [34765.059315] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:43:34 192.168.122.209 [34765.097366] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:43:34 192.168.122.209 [34765.137245] [tempesta fw] Tempesta FW is ready Apr 26 01:43:35 192.168.122.209 [34765.285338] device enp1s0 entered promiscuous mode Apr 26 01:43:35 192.168.122.209 [34765.366821] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.1 ('private.example.com' vs 'default') Apr 26 01:43:35 192.168.122.209 [34765.370300] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.1 Apr 26 01:43:35 192.168.122.209 [34765.385630] device enp1s0 left promiscuous mode Apr 26 01:43:35 192.168.122.209 [34765.408179] device enp1s0 entered promiscuous mode Apr 26 01:43:35 192.168.122.209 [34765.505015] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.1 ('private.example.com' vs 'default') Apr 26 01:43:35 192.168.122.209 [34765.508458] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.1 Apr 26 01:43:35 192.168.122.209 [34765.525985] device enp1s0 left promiscuous mode Apr 26 01:43:35 192.168.122.209 [34765.552023] device enp1s0 entered promiscuous mode Apr 26 01:43:35 192.168.122.209 [34765.629284] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.1 ('example.com' vs 'default') Apr 26 01:43:35 192.168.122.209 [34765.630340] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.1 Apr 26 01:43:35 192.168.122.209 [34765.650071] device enp1s0 left promiscuous mode Apr 26 01:43:35 192.168.122.209 [34766.112423] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 01:43:35 192.168.122.209 [34766.187384] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [34766.187384] Maybe that's fine, but it's worth checking the [34766.187384] config - if there is no relations between the [34766.187384] names, then host name confusion attack is possible. Apr 26 01:43:35 192.168.122.209 [34766.237752] [tempesta fw] Configuration processing is completed. Apr 26 01:43:36 192.168.122.209 [34766.537475] [tempesta fw] Tempesta FW is ready Apr 26 01:43:36 192.168.122.209 [34766.580014] device enp1s0 entered promiscuous mode Apr 26 01:43:36 192.168.122.209 [34766.661740] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.1 ('example.com' vs 'default') Apr 26 01:43:36 192.168.122.209 [34766.681650] device enp1s0 left promiscuous mode Apr 26 01:43:36 192.168.122.209 [34766.711920] device enp1s0 entered promiscuous mode Apr 26 01:43:36 192.168.122.209 [34766.814016] device enp1s0 left promiscuous mode Apr 26 01:43:36 192.168.122.209 [34766.840211] device enp1s0 entered promiscuous mode Apr 26 01:43:36 192.168.122.209 [34766.954051] device enp1s0 left promiscuous mode Apr 26 01:43:37 192.168.122.209 [34767.833431] [tempesta fw] Tempesta FW is ready Apr 26 01:43:37 192.168.122.209 [34767.883249] device enp1s0 entered promiscuous mode Apr 26 01:43:37 192.168.122.209 [34767.993998] device enp1s0 left promiscuous mode Apr 26 01:43:37 192.168.122.209 [34768.016154] device enp1s0 entered promiscuous mode Apr 26 01:43:37 192.168.122.209 [34768.106057] device enp1s0 left promiscuous mode Apr 26 01:43:37 192.168.122.209 [34768.132265] device enp1s0 entered promiscuous mode Apr 26 01:43:37 192.168.122.209 [34768.205809] device enp1s0 left promiscuous mode Apr 26 01:43:38 192.168.122.209 [34769.234683] [tempesta fw] Tempesta FW is ready Apr 26 01:43:39 192.168.122.209 [34769.288408] device enp1s0 entered promiscuous mode Apr 26 01:43:39 192.168.122.209 [34769.385637] device enp1s0 left promiscuous mode Apr 26 01:43:39 192.168.122.209 [34769.416216] device enp1s0 entered promiscuous mode Apr 26 01:43:39 192.168.122.209 [34769.522024] device enp1s0 left promiscuous mode Apr 26 01:43:39 192.168.122.209 [34769.560302] device enp1s0 entered promiscuous mode Apr 26 01:43:39 192.168.122.209 [34769.669964] device enp1s0 left promiscuous mode Apr 26 01:43:39 192.168.122.209 [34770.136262] [tdb] Close table 'client0.tdb' Apr 26 01:43:40 192.168.122.209 [34770.343940] [tdb] Close table 'sessions0.tdb' Apr 26 01:43:40 192.168.122.209 [34770.604317] [tdb] Close table 'filter0.tdb' Apr 26 01:43:40 192.168.122.209 [34770.604764] net_ratelimit: 23 callbacks suppressed Apr 26 01:43:40 192.168.122.209 [34770.604765] [tempesta fw] modules are stopped Apr 26 01:43:40 192.168.122.209 [34770.853707] [tempesta fw] exiting... Apr 26 01:43:40 192.168.122.209 [34771.015010] [tdb] Shutdown Tempesta DB Apr 26 01:43:41 192.168.122.209 [34771.251150] End test: tls.test_tls_cert.TlsCertSelectBySanwitMultipleSections.test Apr 26 01:43:41 192.168.122.209 [34771.280222] Start test: tls.test_tls_cert.TlsCertSelectBySan.test_various_san_and_sni_not_matched Apr 26 01:43:42 192.168.122.209 [34772.661626] [tdb] Start Tempesta DB Apr 26 01:43:42 192.168.122.209 [34772.829952] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:43:43 192.168.122.209 [34773.475431] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [34773.475431] Maybe that's fine, but it's worth checking the [34773.475431] config - if there is no relations between the [34773.475431] names, then host name confusion attack is possible. Apr 26 01:43:43 192.168.122.209 [34773.533585] [tempesta fw] Configuration processing is completed. Apr 26 01:43:43 192.168.122.209 [34773.594950] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:43:43 192.168.122.209 [34773.630124] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:43:43 192.168.122.209 [34773.662629] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:43:43 192.168.122.209 [34773.729510] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:43:43 192.168.122.209 [34773.789391] [tempesta fw] Tempesta FW is ready Apr 26 01:43:44 192.168.122.209 [34774.349150] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 01:43:44 192.168.122.209 [34774.411627] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [34774.411627] Maybe that's fine, but it's worth checking the [34774.411627] config - if there is no relations between the [34774.411627] names, then host name confusion attack is possible. Apr 26 01:43:44 192.168.122.209 [34774.461505] [tempesta fw] Configuration processing is completed. Apr 26 01:43:44 192.168.122.209 [34774.689463] [tempesta fw] Tempesta FW is ready Apr 26 01:43:44 192.168.122.209 [34774.747245] device enp1s0 entered promiscuous mode Apr 26 01:43:44 192.168.122.209 [34774.799993] [tempesta fw] Warning: client 127.0.0.1 requested unknown server name 'a.b.example.com' in TLS SNI, reject connection. Apr 26 01:43:44 192.168.122.209 [34774.822105] device enp1s0 left promiscuous mode Apr 26 01:43:45 192.168.122.209 [34775.368356] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 01:43:45 192.168.122.209 [34775.713516] [tempesta fw] Tempesta FW is ready Apr 26 01:43:45 192.168.122.209 [34775.763902] device enp1s0 entered promiscuous mode Apr 26 01:43:45 192.168.122.209 [34775.827073] net_ratelimit: 2 callbacks suppressed Apr 26 01:43:45 192.168.122.209 [34775.827075] [tempesta fw] Warning: client 127.0.0.1 requested unknown server name 'www.example.com' in TLS SNI, reject connection. Apr 26 01:43:45 192.168.122.209 [34775.849793] device enp1s0 left promiscuous mode Apr 26 01:43:46 192.168.122.209 [34776.352887] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 01:43:46 192.168.122.209 [34776.427651] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [34776.427651] Maybe that's fine, but it's worth checking the [34776.427651] config - if there is no relations between the [34776.427651] names, then host name confusion attack is possible. Apr 26 01:43:46 192.168.122.209 [34776.477568] [tempesta fw] Configuration processing is completed. Apr 26 01:43:46 192.168.122.209 [34776.709503] [tempesta fw] Tempesta FW is ready Apr 26 01:43:46 192.168.122.209 [34776.760981] device enp1s0 entered promiscuous mode Apr 26 01:43:46 192.168.122.209 [34776.803970] [tempesta fw] Warning: client 127.0.0.1 requested unknown server name 'b.example.com' in TLS SNI, reject connection. Apr 26 01:43:46 192.168.122.209 [34776.830140] device enp1s0 left promiscuous mode Apr 26 01:43:47 192.168.122.209 [34777.306703] [tdb] Close table 'client0.tdb' Apr 26 01:43:47 192.168.122.209 [34777.492927] [tdb] Close table 'sessions0.tdb' Apr 26 01:43:47 192.168.122.209 [34777.741128] [tdb] Close table 'filter0.tdb' Apr 26 01:43:47 192.168.122.209 [34777.741592] [tempesta fw] modules are stopped Apr 26 01:43:47 192.168.122.209 [34777.986661] [tempesta fw] exiting... Apr 26 01:43:47 192.168.122.209 [34778.152739] [tdb] Shutdown Tempesta DB Apr 26 01:43:48 192.168.122.209 [34778.421275] End test: tls.test_tls_cert.TlsCertSelectBySan.test_various_san_and_sni_not_matched Apr 26 01:43:48 192.168.122.209 [34778.454464] Start test: tls.test_tls_cert.TlsCertSelectBySan.test_various_san_and_sni_matched Apr 26 01:43:49 192.168.122.209 [34779.893540] [tdb] Start Tempesta DB Apr 26 01:43:49 192.168.122.209 [34780.036469] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:43:50 192.168.122.209 [34780.699581] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [34780.699581] Maybe that's fine, but it's worth checking the [34780.699581] config - if there is no relations between the [34780.699581] names, then host name confusion attack is possible. Apr 26 01:43:50 192.168.122.209 [34780.745884] [tempesta fw] Configuration processing is completed. Apr 26 01:43:50 192.168.122.209 [34780.807499] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:43:50 192.168.122.209 [34780.845338] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:43:50 192.168.122.209 [34780.878794] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:43:50 192.168.122.209 [34780.925606] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:43:50 192.168.122.209 [34780.973461] [tempesta fw] Tempesta FW is ready Apr 26 01:43:51 192.168.122.209 [34781.524980] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 01:43:51 192.168.122.209 [34781.595481] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [34781.595481] Maybe that's fine, but it's worth checking the [34781.595481] config - if there is no relations between the [34781.595481] names, then host name confusion attack is possible. Apr 26 01:43:51 192.168.122.209 [34781.653551] [tempesta fw] Configuration processing is completed. Apr 26 01:43:51 192.168.122.209 [34781.897897] [tempesta fw] Tempesta FW is ready Apr 26 01:43:51 192.168.122.209 [34781.944246] device enp1s0 entered promiscuous mode Apr 26 01:43:51 192.168.122.209 [34782.024659] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.1 ('example.com' vs 'default') Apr 26 01:43:51 192.168.122.209 [34782.027847] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.1 Apr 26 01:43:51 192.168.122.209 [34782.050180] device enp1s0 left promiscuous mode Apr 26 01:43:52 192.168.122.209 [34782.559381] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 01:43:52 192.168.122.209 [34782.639523] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [34782.639523] Maybe that's fine, but it's worth checking the [34782.639523] config - if there is no relations between the [34782.639523] names, then host name confusion attack is possible. Apr 26 01:43:52 192.168.122.209 [34782.693658] [tempesta fw] Configuration processing is completed. Apr 26 01:43:52 192.168.122.209 [34782.941620] [tempesta fw] Tempesta FW is ready Apr 26 01:43:52 192.168.122.209 [34782.998410] device enp1s0 entered promiscuous mode Apr 26 01:43:52 192.168.122.209 [34783.092298] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.1 ('example.com' vs 'default') Apr 26 01:43:52 192.168.122.209 [34783.113819] device enp1s0 left promiscuous mode Apr 26 01:43:53 192.168.122.209 [34783.985627] [tempesta fw] Tempesta FW is ready Apr 26 01:43:53 192.168.122.209 [34784.046355] device enp1s0 entered promiscuous mode Apr 26 01:43:53 192.168.122.209 [34784.154519] device enp1s0 left promiscuous mode Apr 26 01:43:54 192.168.122.209 [34784.937589] [tempesta fw] Tempesta FW is ready Apr 26 01:43:54 192.168.122.209 [34784.999035] device enp1s0 entered promiscuous mode Apr 26 01:43:54 192.168.122.209 [34785.106223] device enp1s0 left promiscuous mode Apr 26 01:43:55 192.168.122.209 [34785.933647] [tempesta fw] Tempesta FW is ready Apr 26 01:43:55 192.168.122.209 [34785.987339] device enp1s0 entered promiscuous mode Apr 26 01:43:55 192.168.122.209 [34786.077624] net_ratelimit: 14 callbacks suppressed Apr 26 01:43:55 192.168.122.209 [34786.077631] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.1 ('example.com' vs 'default') Apr 26 01:43:55 192.168.122.209 [34786.082180] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.1 Apr 26 01:43:55 192.168.122.209 [34786.106328] device enp1s0 left promiscuous mode Apr 26 01:43:56 192.168.122.209 [34786.529388] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 01:43:56 192.168.122.209 [34786.599612] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [34786.599612] Maybe that's fine, but it's worth checking the [34786.599612] config - if there is no relations between the [34786.599612] names, then host name confusion attack is possible. Apr 26 01:43:56 192.168.122.209 [34786.657672] [tempesta fw] Configuration processing is completed. Apr 26 01:43:56 192.168.122.209 [34786.905667] [tempesta fw] Tempesta FW is ready Apr 26 01:43:56 192.168.122.209 [34786.959846] device enp1s0 entered promiscuous mode Apr 26 01:43:56 192.168.122.209 [34787.052035] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.1 ('example.com' vs 'default') Apr 26 01:43:56 192.168.122.209 [34787.055323] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.1 Apr 26 01:43:56 192.168.122.209 [34787.078157] device enp1s0 left promiscuous mode Apr 26 01:43:57 192.168.122.209 [34787.519862] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 01:43:57 192.168.122.209 [34787.591529] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [34787.591529] Maybe that's fine, but it's worth checking the [34787.591529] config - if there is no relations between the [34787.591529] names, then host name confusion attack is possible. Apr 26 01:43:57 192.168.122.209 [34787.641719] [tempesta fw] Configuration processing is completed. Apr 26 01:43:57 192.168.122.209 [34787.865680] [tempesta fw] Tempesta FW is ready Apr 26 01:43:57 192.168.122.209 [34787.932415] device enp1s0 entered promiscuous mode Apr 26 01:43:57 192.168.122.209 [34788.033911] device enp1s0 left promiscuous mode Apr 26 01:43:58 192.168.122.209 [34788.517886] [tdb] Close table 'client0.tdb' Apr 26 01:43:58 192.168.122.209 [34788.709638] [tdb] Close table 'sessions0.tdb' Apr 26 01:43:58 192.168.122.209 [34788.949297] [tdb] Close table 'filter0.tdb' Apr 26 01:43:58 192.168.122.209 [34789.154501] [tempesta fw] exiting... Apr 26 01:43:59 192.168.122.209 [34789.322126] [tdb] Shutdown Tempesta DB Apr 26 01:43:59 192.168.122.209 [34789.552053] End test: tls.test_tls_cert.TlsCertSelectBySan.test_various_san_and_sni_matched Apr 26 01:43:59 192.168.122.209 [34789.564016] Start test: tls.test_tls_cert.TlsCertSelectBySan.test_unknown_server_name_warning Apr 26 01:44:00 192.168.122.209 [34790.948543] [tdb] Start Tempesta DB Apr 26 01:44:00 192.168.122.209 [34791.106127] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:44:01 192.168.122.209 [34791.727755] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [34791.727755] Maybe that's fine, but it's worth checking the [34791.727755] config - if there is no relations between the [34791.727755] names, then host name confusion attack is possible. Apr 26 01:44:01 192.168.122.209 [34791.793788] [tempesta fw] Configuration processing is completed. Apr 26 01:44:01 192.168.122.209 [34791.849000] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:44:01 192.168.122.209 [34791.881108] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:44:01 192.168.122.209 [34791.912733] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:44:01 192.168.122.209 [34791.989737] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:44:01 192.168.122.209 [34792.029659] [tempesta fw] Tempesta FW is ready Apr 26 01:44:01 192.168.122.209 [34792.232055] device enp1s0 entered promiscuous mode Apr 26 01:44:02 192.168.122.209 [34792.284515] [tempesta fw] Warning: client 127.0.0.1 requested unknown server name 'localhost' in TLS SNI, reject connection. Apr 26 01:44:02 192.168.122.209 [34792.310217] device enp1s0 left promiscuous mode Apr 26 01:44:02 192.168.122.209 [34792.478848] device enp1s0 entered promiscuous mode Apr 26 01:44:02 192.168.122.209 [34792.531578] [tempesta fw] Warning: client 127.0.0.1 requested unknown server name 'a.localhost' in TLS SNI, reject connection. Apr 26 01:44:02 192.168.122.209 [34792.554354] device enp1s0 left promiscuous mode Apr 26 01:44:02 192.168.122.209 [34792.713480] device enp1s0 entered promiscuous mode Apr 26 01:44:02 192.168.122.209 [34792.765905] [tempesta fw] Warning: client 127.0.0.1 requested unknown server name 'a.b.localhost' in TLS SNI, reject connection. Apr 26 01:44:02 192.168.122.209 [34792.798127] device enp1s0 left promiscuous mode Apr 26 01:44:02 192.168.122.209 [34792.954506] device enp1s0 entered promiscuous mode Apr 26 01:44:02 192.168.122.209 [34793.008392] [tempesta fw] Warning: client 127.0.0.1 requested unknown server name 'a.b.c.localhost' in TLS SNI, reject connection. Apr 26 01:44:02 192.168.122.209 [34793.026006] device enp1s0 left promiscuous mode Apr 26 01:44:02 192.168.122.209 [34793.208297] device enp1s0 entered promiscuous mode Apr 26 01:44:03 192.168.122.209 [34793.252520] [tempesta fw] Warning: client 127.0.0.1 requested unknown server name 'a.b.c.localhost.com' in TLS SNI, reject connection. Apr 26 01:44:03 192.168.122.209 [34793.265944] device enp1s0 left promiscuous mode Apr 26 01:44:03 192.168.122.209 [34793.430343] device enp1s0 entered promiscuous mode Apr 26 01:44:03 192.168.122.209 [34793.488542] [tempesta fw] Warning: client 127.0.0.1 requested unknown server name 'a.b.c.example.com' in TLS SNI, reject connection. Apr 26 01:44:03 192.168.122.209 [34793.514003] device enp1s0 left promiscuous mode Apr 26 01:44:03 192.168.122.209 [34793.698986] device enp1s0 entered promiscuous mode Apr 26 01:44:03 192.168.122.209 [34793.751884] [tempesta fw] Warning: client 127.0.0.1 requested unknown server name '' in TLS SNI, reject connection. Apr 26 01:44:03 192.168.122.209 [34793.774349] device enp1s0 left promiscuous mode Apr 26 01:44:03 192.168.122.209 [34793.942975] device enp1s0 entered promiscuous mode Apr 26 01:44:03 192.168.122.209 [34793.989026] [tempesta fw] Warning: client 127.0.0.1 requested unknown server name ' [34793.989026] [34793.989026] [34793.989026] ' in TLS SNI, reject connection. Apr 26 01:44:03 192.168.122.209 [34794.018289] device enp1s0 left promiscuous mode Apr 26 01:44:04 192.168.122.209 [34794.570906] [tdb] Close table 'client0.tdb' Apr 26 01:44:04 192.168.122.209 [34794.781842] [tdb] Close table 'sessions0.tdb' Apr 26 01:44:04 192.168.122.209 [34795.025609] [tdb] Close table 'filter0.tdb' Apr 26 01:44:04 192.168.122.209 [34795.026050] net_ratelimit: 3 callbacks suppressed Apr 26 01:44:04 192.168.122.209 [34795.026051] [tempesta fw] modules are stopped Apr 26 01:44:05 192.168.122.209 [34795.263293] [tempesta fw] exiting... Apr 26 01:44:05 192.168.122.209 [34795.423867] [tdb] Shutdown Tempesta DB Apr 26 01:44:05 192.168.122.209 [34795.672307] End test: tls.test_tls_cert.TlsCertSelectBySan.test_unknown_server_name_warning Apr 26 01:44:05 192.168.122.209 [34795.690774] Start test: tls.test_tls_cert.TlsCertSelectBySan.test_sni_not_matched Apr 26 01:44:06 192.168.122.209 [34797.101928] [tdb] Start Tempesta DB Apr 26 01:44:07 192.168.122.209 [34797.260146] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:44:07 192.168.122.209 [34797.931876] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [34797.931876] Maybe that's fine, but it's worth checking the [34797.931876] config - if there is no relations between the [34797.931876] names, then host name confusion attack is possible. Apr 26 01:44:07 192.168.122.209 [34798.002228] [tempesta fw] Configuration processing is completed. Apr 26 01:44:07 192.168.122.209 [34798.059749] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:44:07 192.168.122.209 [34798.097360] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:44:07 192.168.122.209 [34798.131801] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:44:07 192.168.122.209 [34798.177808] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:44:07 192.168.122.209 [34798.217739] [tempesta fw] Tempesta FW is ready Apr 26 01:44:08 192.168.122.209 [34798.365315] device enp1s0 entered promiscuous mode Apr 26 01:44:08 192.168.122.209 [34798.409963] [tempesta fw] Warning: client 127.0.0.1 requested unknown server name 'b.a.example.com' in TLS SNI, reject connection. Apr 26 01:44:08 192.168.122.209 [34798.430334] device enp1s0 left promiscuous mode Apr 26 01:44:08 192.168.122.209 [34798.452945] device enp1s0 entered promiscuous mode Apr 26 01:44:08 192.168.122.209 [34798.491498] [tempesta fw] Warning: client 127.0.0.1 requested unknown server name '..example.com' in TLS SNI, reject connection. Apr 26 01:44:08 192.168.122.209 [34798.514384] device enp1s0 left promiscuous mode Apr 26 01:44:08 192.168.122.209 [34798.545835] device enp1s0 entered promiscuous mode Apr 26 01:44:08 192.168.122.209 [34798.600181] [tempesta fw] Warning: client 127.0.0.1 requested unknown server name '.a.example.com' in TLS SNI, reject connection. Apr 26 01:44:08 192.168.122.209 [34798.622287] device enp1s0 left promiscuous mode Apr 26 01:44:08 192.168.122.209 [34798.644803] device enp1s0 entered promiscuous mode Apr 26 01:44:08 192.168.122.209 [34798.703965] [tempesta fw] Warning: client 127.0.0.1 requested unknown server name 'www.www.example.com' in TLS SNI, reject connection. Apr 26 01:44:08 192.168.122.209 [34798.726343] device enp1s0 left promiscuous mode Apr 26 01:44:08 192.168.122.209 [34798.764084] device enp1s0 entered promiscuous mode Apr 26 01:44:08 192.168.122.209 [34798.807958] [tempesta fw] Warning: client 127.0.0.1 requested unknown server name 'example.com.www' in TLS SNI, reject connection. Apr 26 01:44:08 192.168.122.209 [34798.830326] device enp1s0 left promiscuous mode Apr 26 01:44:08 192.168.122.209 [34798.856284] device enp1s0 entered promiscuous mode Apr 26 01:44:08 192.168.122.209 [34798.926424] device enp1s0 left promiscuous mode Apr 26 01:44:08 192.168.122.209 [34798.952102] device enp1s0 entered promiscuous mode Apr 26 01:44:08 192.168.122.209 [34799.022385] device enp1s0 left promiscuous mode Apr 26 01:44:08 192.168.122.209 [34799.052917] device enp1s0 entered promiscuous mode Apr 26 01:44:08 192.168.122.209 [34799.142409] device enp1s0 left promiscuous mode Apr 26 01:44:08 192.168.122.209 [34799.173316] device enp1s0 entered promiscuous mode Apr 26 01:44:09 192.168.122.209 [34799.250427] device enp1s0 left promiscuous mode Apr 26 01:44:09 192.168.122.209 [34799.272262] device enp1s0 entered promiscuous mode Apr 26 01:44:09 192.168.122.209 [34799.346474] device enp1s0 left promiscuous mode Apr 26 01:44:09 192.168.122.209 [34799.376009] device enp1s0 entered promiscuous mode Apr 26 01:44:09 192.168.122.209 [34799.430696] device enp1s0 left promiscuous mode Apr 26 01:44:09 192.168.122.209 [34799.456340] device enp1s0 entered promiscuous mode Apr 26 01:44:09 192.168.122.209 [34799.526184] device enp1s0 left promiscuous mode Apr 26 01:44:09 192.168.122.209 [34799.552258] device enp1s0 entered promiscuous mode Apr 26 01:44:09 192.168.122.209 [34799.626435] device enp1s0 left promiscuous mode Apr 26 01:44:09 192.168.122.209 [34800.060654] [tdb] Close table 'client0.tdb' Apr 26 01:44:10 192.168.122.209 [34800.259326] [tdb] Close table 'sessions0.tdb' Apr 26 01:44:10 192.168.122.209 [34800.485268] [tdb] Close table 'filter0.tdb' Apr 26 01:44:10 192.168.122.209 [34800.485753] net_ratelimit: 8 callbacks suppressed Apr 26 01:44:10 192.168.122.209 [34800.485754] [tempesta fw] modules are stopped Apr 26 01:44:10 192.168.122.209 [34800.694854] [tempesta fw] exiting... Apr 26 01:44:10 192.168.122.209 [34800.841148] [tdb] Shutdown Tempesta DB Apr 26 01:44:10 192.168.122.209 [34801.075767] End test: tls.test_tls_cert.TlsCertSelectBySan.test_sni_not_matched Apr 26 01:44:10 192.168.122.209 [34801.104167] Start test: tls.test_tls_cert.TlsCertSelectBySan.test_sni_matched Apr 26 01:44:12 192.168.122.209 [34802.400957] [tdb] Start Tempesta DB Apr 26 01:44:12 192.168.122.209 [34802.544635] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:44:13 192.168.122.209 [34803.251955] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [34803.251955] Maybe that's fine, but it's worth checking the [34803.251955] config - if there is no relations between the [34803.251955] names, then host name confusion attack is possible. Apr 26 01:44:13 192.168.122.209 [34803.317840] [tempesta fw] Configuration processing is completed. Apr 26 01:44:13 192.168.122.209 [34803.377968] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:44:13 192.168.122.209 [34803.414317] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:44:13 192.168.122.209 [34803.447180] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:44:13 192.168.122.209 [34803.481877] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:44:13 192.168.122.209 [34803.521824] [tempesta fw] Tempesta FW is ready Apr 26 01:44:13 192.168.122.209 [34803.674764] device enp1s0 entered promiscuous mode Apr 26 01:44:13 192.168.122.209 [34803.773353] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.1 ('example.com' vs 'default') Apr 26 01:44:13 192.168.122.209 [34803.775916] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.1 Apr 26 01:44:13 192.168.122.209 [34803.798449] device enp1s0 left promiscuous mode Apr 26 01:44:13 192.168.122.209 [34803.832779] device enp1s0 entered promiscuous mode Apr 26 01:44:13 192.168.122.209 [34803.924502] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.1 ('example.com' vs 'default') Apr 26 01:44:13 192.168.122.209 [34803.927757] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.1 Apr 26 01:44:13 192.168.122.209 [34803.950515] device enp1s0 left promiscuous mode Apr 26 01:44:13 192.168.122.209 [34803.984836] device enp1s0 entered promiscuous mode Apr 26 01:44:13 192.168.122.209 [34804.078879] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.1 ('example.com' vs 'default') Apr 26 01:44:13 192.168.122.209 [34804.102533] device enp1s0 left promiscuous mode Apr 26 01:44:13 192.168.122.209 [34804.128964] device enp1s0 entered promiscuous mode Apr 26 01:44:13 192.168.122.209 [34804.234160] device enp1s0 left promiscuous mode Apr 26 01:44:14 192.168.122.209 [34804.264970] device enp1s0 entered promiscuous mode Apr 26 01:44:14 192.168.122.209 [34804.370374] device enp1s0 left promiscuous mode Apr 26 01:44:14 192.168.122.209 [34804.401085] device enp1s0 entered promiscuous mode Apr 26 01:44:14 192.168.122.209 [34804.498193] device enp1s0 left promiscuous mode Apr 26 01:44:14 192.168.122.209 [34804.524736] device enp1s0 entered promiscuous mode Apr 26 01:44:14 192.168.122.209 [34804.630531] device enp1s0 left promiscuous mode Apr 26 01:44:14 192.168.122.209 [34804.656635] device enp1s0 entered promiscuous mode Apr 26 01:44:14 192.168.122.209 [34804.762030] device enp1s0 left promiscuous mode Apr 26 01:44:14 192.168.122.209 [34804.784343] device enp1s0 entered promiscuous mode Apr 26 01:44:14 192.168.122.209 [34804.882567] device enp1s0 left promiscuous mode Apr 26 01:44:14 192.168.122.209 [34804.904815] device enp1s0 entered promiscuous mode Apr 26 01:44:14 192.168.122.209 [34805.010254] device enp1s0 left promiscuous mode Apr 26 01:44:15 192.168.122.209 [34805.471135] [tdb] Close table 'client0.tdb' Apr 26 01:44:15 192.168.122.209 [34805.676789] [tdb] Close table 'sessions0.tdb' Apr 26 01:44:15 192.168.122.209 [34805.940062] [tdb] Close table 'filter0.tdb' Apr 26 01:44:15 192.168.122.209 [34805.940524] net_ratelimit: 15 callbacks suppressed Apr 26 01:44:15 192.168.122.209 [34805.940526] [tempesta fw] modules are stopped Apr 26 01:44:15 192.168.122.209 [34806.178304] [tempesta fw] exiting... Apr 26 01:44:16 192.168.122.209 [34806.321311] [tdb] Shutdown Tempesta DB Apr 26 01:44:16 192.168.122.209 [34806.556299] End test: tls.test_tls_cert.TlsCertSelectBySan.test_sni_matched Apr 26 01:44:16 192.168.122.209 [34806.581467] Start test: tls.test_tls_cert.TlsCertSelectBySan.test_sni_match_after_reload Apr 26 01:44:17 192.168.122.209 [34807.879008] [tdb] Start Tempesta DB Apr 26 01:44:17 192.168.122.209 [34808.019703] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:44:18 192.168.122.209 [34808.675886] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [34808.675886] Maybe that's fine, but it's worth checking the [34808.675886] config - if there is no relations between the [34808.675886] names, then host name confusion attack is possible. Apr 26 01:44:18 192.168.122.209 [34808.726306] [tempesta fw] Configuration processing is completed. Apr 26 01:44:18 192.168.122.209 [34808.789408] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:44:18 192.168.122.209 [34808.827831] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:44:18 192.168.122.209 [34808.860786] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:44:18 192.168.122.209 [34808.933950] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:44:18 192.168.122.209 [34808.973895] [tempesta fw] Tempesta FW is ready Apr 26 01:44:19 192.168.122.209 [34809.526423] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 01:44:19 192.168.122.209 [34809.607754] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [34809.607754] Maybe that's fine, but it's worth checking the [34809.607754] config - if there is no relations between the [34809.607754] names, then host name confusion attack is possible. Apr 26 01:44:19 192.168.122.209 [34809.661953] [tempesta fw] Configuration processing is completed. Apr 26 01:44:19 192.168.122.209 [34809.921963] [tempesta fw] Tempesta FW is ready Apr 26 01:44:19 192.168.122.209 [34809.974051] device enp1s0 entered promiscuous mode Apr 26 01:44:19 192.168.122.209 [34810.052169] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.1 ('example.com' vs 'default') Apr 26 01:44:19 192.168.122.209 [34810.053185] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.1 Apr 26 01:44:19 192.168.122.209 [34810.074127] device enp1s0 left promiscuous mode Apr 26 01:44:19 192.168.122.209 [34810.103810] device enp1s0 entered promiscuous mode Apr 26 01:44:19 192.168.122.209 [34810.182176] device enp1s0 left promiscuous mode Apr 26 01:44:20 192.168.122.209 [34811.005926] [tempesta fw] Tempesta FW is ready Apr 26 01:44:20 192.168.122.209 [34811.060164] device enp1s0 entered promiscuous mode Apr 26 01:44:20 192.168.122.209 [34811.149460] net_ratelimit: 4 callbacks suppressed Apr 26 01:44:20 192.168.122.209 [34811.149468] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.1 ('example.com' vs 'default') Apr 26 01:44:20 192.168.122.209 [34811.154125] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.1 Apr 26 01:44:20 192.168.122.209 [34811.174279] device enp1s0 left promiscuous mode Apr 26 01:44:20 192.168.122.209 [34811.201930] device enp1s0 entered promiscuous mode Apr 26 01:44:21 192.168.122.209 [34811.255350] [tempesta fw] Warning: client 127.0.0.1 requested unknown server name 'a.example.com' in TLS SNI, reject connection. Apr 26 01:44:21 192.168.122.209 [34811.282148] device enp1s0 left promiscuous mode Apr 26 01:44:21 192.168.122.209 [34811.716192] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 01:44:21 192.168.122.209 [34811.780052] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [34811.780052] Maybe that's fine, but it's worth checking the [34811.780052] config - if there is no relations between the [34811.780052] names, then host name confusion attack is possible. Apr 26 01:44:21 192.168.122.209 [34811.830345] [tempesta fw] Configuration processing is completed. Apr 26 01:44:21 192.168.122.209 [34812.094004] [tempesta fw] Tempesta FW is ready Apr 26 01:44:21 192.168.122.209 [34812.144336] device enp1s0 entered promiscuous mode Apr 26 01:44:21 192.168.122.209 [34812.218518] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.1 ('example.com' vs 'default') Apr 26 01:44:21 192.168.122.209 [34812.221788] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.1 Apr 26 01:44:22 192.168.122.209 [34812.242494] device enp1s0 left promiscuous mode Apr 26 01:44:22 192.168.122.209 [34812.264629] device enp1s0 entered promiscuous mode Apr 26 01:44:22 192.168.122.209 [34812.320666] [tempesta fw] Warning: client 127.0.0.1 requested unknown server name 'b.tempesta-tech.com' in TLS SNI, reject connection. Apr 26 01:44:22 192.168.122.209 [34812.346321] device enp1s0 left promiscuous mode Apr 26 01:44:22 192.168.122.209 [34812.846346] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 01:44:22 192.168.122.209 [34813.198024] [tempesta fw] Tempesta FW is ready Apr 26 01:44:23 192.168.122.209 [34813.243914] device enp1s0 entered promiscuous mode Apr 26 01:44:23 192.168.122.209 [34813.350622] device enp1s0 left promiscuous mode Apr 26 01:44:23 192.168.122.209 [34813.376669] device enp1s0 entered promiscuous mode Apr 26 01:44:23 192.168.122.209 [34813.454367] device enp1s0 left promiscuous mode Apr 26 01:44:23 192.168.122.209 [34814.206688] [tempesta fw] Tempesta FW is ready Apr 26 01:44:24 192.168.122.209 [34814.250060] device enp1s0 entered promiscuous mode Apr 26 01:44:24 192.168.122.209 [34814.350252] device enp1s0 left promiscuous mode Apr 26 01:44:24 192.168.122.209 [34814.374189] device enp1s0 entered promiscuous mode Apr 26 01:44:24 192.168.122.209 [34814.446639] device enp1s0 left promiscuous mode Apr 26 01:44:24 192.168.122.209 [34814.969648] [tdb] Close table 'client0.tdb' Apr 26 01:44:24 192.168.122.209 [34815.136544] [tdb] Close table 'sessions0.tdb' Apr 26 01:44:25 192.168.122.209 [34815.370648] [tdb] Close table 'filter0.tdb' Apr 26 01:44:25 192.168.122.209 [34815.608775] [tempesta fw] exiting... Apr 26 01:44:25 192.168.122.209 [34815.729258] [tdb] Shutdown Tempesta DB Apr 26 01:44:25 192.168.122.209 [34815.966650] End test: tls.test_tls_cert.TlsCertSelectBySan.test_sni_match_after_reload Apr 26 01:44:25 192.168.122.209 [34815.979268] Start test: tls.test_tls_cert.TlsCertSelect.test_vhost_cert_selection Apr 26 01:44:27 192.168.122.209 [34817.846151] [tdb] Start Tempesta DB Apr 26 01:44:27 192.168.122.209 [34817.997447] net_ratelimit: 12 callbacks suppressed Apr 26 01:44:27 192.168.122.209 [34817.997450] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:44:28 192.168.122.209 [34819.012257] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34819.012257] Maybe that's fine, but it's worth checking the [34819.012257] config - if there is no relations between the [34819.012257] names, then host name confusion attack is possible. Apr 26 01:44:28 192.168.122.209 [34819.098626] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [34819.098626] Maybe that's fine, but it's worth checking the [34819.098626] config - if there is no relations between the [34819.098626] names, then host name confusion attack is possible. Apr 26 01:44:28 192.168.122.209 [34819.112519] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [34819.112519] Maybe that's fine, but it's worth checking the [34819.112519] config - if there is no relations between the [34819.112519] names, then host name confusion attack is possible. Apr 26 01:44:28 192.168.122.209 [34819.186461] [tempesta fw] Configuration processing is completed. Apr 26 01:44:29 192.168.122.209 [34819.254828] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:44:29 192.168.122.209 [34819.298946] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:44:29 192.168.122.209 [34819.333431] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:44:29 192.168.122.209 [34819.382077] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:44:29 192.168.122.209 [34819.426027] [tempesta fw] Tempesta FW is ready Apr 26 01:44:29 192.168.122.209 [34819.578881] device enp1s0 entered promiscuous mode Apr 26 01:44:29 192.168.122.209 [34819.682610] device enp1s0 left promiscuous mode Apr 26 01:44:29 192.168.122.209 [34819.709008] device enp1s0 entered promiscuous mode Apr 26 01:44:29 192.168.122.209 [34819.748445] [tempesta fw] Warning: client 127.0.0.1 requested unknown server name 'example.com' in TLS SNI, reject connection. Apr 26 01:44:29 192.168.122.209 [34819.770683] device enp1s0 left promiscuous mode Apr 26 01:44:29 192.168.122.209 [34820.204538] [tdb] Close table 'client0.tdb' Apr 26 01:44:30 192.168.122.209 [34820.415002] [tdb] Close table 'sessions0.tdb' Apr 26 01:44:30 192.168.122.209 [34820.659802] [tdb] Close table 'filter0.tdb' Apr 26 01:44:30 192.168.122.209 [34820.660246] [tempesta fw] modules are stopped Apr 26 01:44:30 192.168.122.209 [34820.922142] [tempesta fw] exiting... Apr 26 01:44:30 192.168.122.209 [34821.062973] [tdb] Shutdown Tempesta DB Apr 26 01:44:31 192.168.122.209 [34821.316341] End test: tls.test_tls_cert.TlsCertSelect.test_vhost_cert_selection Apr 26 01:44:31 192.168.122.209 [34821.334669] Start test: tls.test_tls_cert.StaleCert.test Apr 26 01:44:32 192.168.122.209 [34822.767939] [tdb] Start Tempesta DB Apr 26 01:44:32 192.168.122.209 [34822.918667] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:44:33 192.168.122.209 [34823.459403] [tempesta fw] Warning: The certificate '/tmp/host/tempesta.crt' has expired! Please renew [34823.459403] the certificate to maintain functionality. Apr 26 01:44:33 192.168.122.209 [34823.459478] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34823.459478] Maybe that's fine, but it's worth checking the [34823.459478] config - if there is no relations between the [34823.459478] names, then host name confusion attack is possible. Apr 26 01:44:33 192.168.122.209 [34823.546168] [tempesta fw] Configuration processing is completed. Apr 26 01:44:33 192.168.122.209 [34823.607026] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:44:33 192.168.122.209 [34823.643033] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:44:33 192.168.122.209 [34823.676455] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:44:33 192.168.122.209 [34823.722139] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:44:33 192.168.122.209 [34823.762088] [tempesta fw] Tempesta FW is ready Apr 26 01:44:34 192.168.122.209 [34824.333159] [tdb] Close table 'client0.tdb' Apr 26 01:44:34 192.168.122.209 [34824.552463] [tdb] Close table 'sessions0.tdb' Apr 26 01:44:34 192.168.122.209 [34824.768746] [tdb] Close table 'filter0.tdb' Apr 26 01:44:34 192.168.122.209 [34824.769186] [tempesta fw] modules are stopped Apr 26 01:44:34 192.168.122.209 [34824.953858] [tempesta fw] exiting... Apr 26 01:44:34 192.168.122.209 [34825.104834] [tdb] Shutdown Tempesta DB Apr 26 01:44:35 192.168.122.209 [34825.348268] End test: tls.test_tls_cert.StaleCert.test Apr 26 01:44:35 192.168.122.209 [34825.371013] Start test: tls.test_tls_cert.RSA512_SHA256.test Apr 26 01:44:36 192.168.122.209 [34826.775698] [tdb] Start Tempesta DB Apr 26 01:44:36 192.168.122.209 [34826.916328] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:44:37 192.168.122.209 [34827.451310] [tempesta tls] Warning: Trying to load an RSA key smaller than 1024 bits. Please use stronger keys. Apr 26 01:44:37 192.168.122.209 [34827.454503] [tempesta fw] ERROR: tls_certificate: Invalid certificate specified, err=c Apr 26 01:44:37 192.168.122.209 [34827.456552] [tempesta fw] ERROR: configuration parsing error: [34827.456552] 4: tls_certificate /tmp/host/tempesta.crt; [34827.456552] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 01:44:37 192.168.122.209 [34827.460509] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 01:44:37 192.168.122.209 [34827.601105] [tempesta fw] exiting... Apr 26 01:44:37 192.168.122.209 [34827.714983] [tdb] Shutdown Tempesta DB Apr 26 01:44:38 192.168.122.209 [34828.324324] End test: tls.test_tls_cert.RSA512_SHA256.test Apr 26 01:44:38 192.168.122.209 [34828.350698] Start test: tls.test_tls_cert.RSA4096_SHA512.test Apr 26 01:44:40 192.168.122.209 [34830.908852] [tdb] Start Tempesta DB Apr 26 01:44:40 192.168.122.209 [34831.050513] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:44:41 192.168.122.209 [34831.425409] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34831.425409] Maybe that's fine, but it's worth checking the [34831.425409] config - if there is no relations between the [34831.425409] names, then host name confusion attack is possible. Apr 26 01:44:41 192.168.122.209 [34831.558281] [tempesta fw] Configuration processing is completed. Apr 26 01:44:41 192.168.122.209 [34831.630986] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:44:41 192.168.122.209 [34831.666692] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:44:41 192.168.122.209 [34831.699373] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:44:41 192.168.122.209 [34831.742209] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:44:41 192.168.122.209 [34831.782117] [tempesta fw] Tempesta FW is ready Apr 26 01:44:42 192.168.122.209 [34832.381273] [tdb] Close table 'client0.tdb' Apr 26 01:44:42 192.168.122.209 [34832.559640] [tdb] Close table 'sessions0.tdb' Apr 26 01:44:42 192.168.122.209 [34832.779764] [tdb] Close table 'filter0.tdb' Apr 26 01:44:42 192.168.122.209 [34832.780218] [tempesta fw] modules are stopped Apr 26 01:44:42 192.168.122.209 [34832.970733] [tempesta fw] exiting... Apr 26 01:44:42 192.168.122.209 [34833.104076] [tdb] Shutdown Tempesta DB Apr 26 01:44:43 192.168.122.209 [34833.328189] End test: tls.test_tls_cert.RSA4096_SHA512.test Apr 26 01:44:43 192.168.122.209 [34833.344977] Start test: tls.test_tls_cert.RSA2048_SHA512.test Apr 26 01:44:45 192.168.122.209 [34835.257390] [tdb] Start Tempesta DB Apr 26 01:44:45 192.168.122.209 [34835.386042] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:44:45 192.168.122.209 [34835.897927] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34835.897927] Maybe that's fine, but it's worth checking the [34835.897927] config - if there is no relations between the [34835.897927] names, then host name confusion attack is possible. Apr 26 01:44:45 192.168.122.209 [34836.002350] [tempesta fw] Configuration processing is completed. Apr 26 01:44:45 192.168.122.209 [34836.067351] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:44:45 192.168.122.209 [34836.104350] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:44:45 192.168.122.209 [34836.136752] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:44:45 192.168.122.209 [34836.194281] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:44:46 192.168.122.209 [34836.246224] [tempesta fw] Tempesta FW is ready Apr 26 01:44:46 192.168.122.209 [34836.858078] [tdb] Close table 'client0.tdb' Apr 26 01:44:46 192.168.122.209 [34837.036802] [tdb] Close table 'sessions0.tdb' Apr 26 01:44:47 192.168.122.209 [34837.258597] [tdb] Close table 'filter0.tdb' Apr 26 01:44:47 192.168.122.209 [34837.259035] [tempesta fw] modules are stopped Apr 26 01:44:47 192.168.122.209 [34837.468212] [tempesta fw] exiting... Apr 26 01:44:47 192.168.122.209 [34837.641566] [tdb] Shutdown Tempesta DB Apr 26 01:44:47 192.168.122.209 [34837.897779] End test: tls.test_tls_cert.RSA2048_SHA512.test Apr 26 01:44:47 192.168.122.209 [34837.910987] Start test: tls.test_tls_cert.RSA1024_SHA384.test Apr 26 01:44:49 192.168.122.209 [34839.363229] [tdb] Start Tempesta DB Apr 26 01:44:49 192.168.122.209 [34839.508459] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:44:49 192.168.122.209 [34840.047525] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34840.047525] Maybe that's fine, but it's worth checking the [34840.047525] config - if there is no relations between the [34840.047525] names, then host name confusion attack is possible. Apr 26 01:44:49 192.168.122.209 [34840.138337] [tempesta fw] Configuration processing is completed. Apr 26 01:44:49 192.168.122.209 [34840.199857] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:44:49 192.168.122.209 [34840.240084] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:44:50 192.168.122.209 [34840.286460] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:44:50 192.168.122.209 [34840.334359] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:44:50 192.168.122.209 [34840.374291] [tempesta fw] Tempesta FW is ready Apr 26 01:44:50 192.168.122.209 [34840.947013] [tdb] Close table 'client0.tdb' Apr 26 01:44:50 192.168.122.209 [34841.132475] [tdb] Close table 'sessions0.tdb' Apr 26 01:44:51 192.168.122.209 [34841.336599] [tdb] Close table 'filter0.tdb' Apr 26 01:44:51 192.168.122.209 [34841.337047] [tempesta fw] modules are stopped Apr 26 01:44:51 192.168.122.209 [34841.527313] [tempesta fw] exiting... Apr 26 01:44:51 192.168.122.209 [34841.659176] [tdb] Shutdown Tempesta DB Apr 26 01:44:51 192.168.122.209 [34841.891051] End test: tls.test_tls_cert.RSA1024_SHA384.test Apr 26 01:44:51 192.168.122.209 [34841.901017] Start test: tls.test_tls_cert.InvalidKeyWithGoodCert.test Apr 26 01:44:52 192.168.122.209 [34843.123036] [tdb] Start Tempesta DB Apr 26 01:44:53 192.168.122.209 [34843.258881] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:44:53 192.168.122.209 [34843.667855] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34843.667855] Maybe that's fine, but it's worth checking the [34843.667855] config - if there is no relations between the [34843.667855] names, then host name confusion attack is possible. Apr 26 01:44:53 192.168.122.209 [34843.702900] [tempesta tls] Warning: PK - Elliptic curve with OID 1.2.840.10045.3.1.1 is unsupported Apr 26 01:44:53 192.168.122.209 [34843.705545] [tempesta fw] ERROR: tls_certificate_key: Invalid private key specified (16) Apr 26 01:44:53 192.168.122.209 [34843.707874] [tempesta fw] ERROR: configuration parsing error: [34843.707874] 5: tls_certificate_key /tmp/host/tempesta.key; [34843.707874] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 01:44:53 192.168.122.209 [34843.713462] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 01:44:53 192.168.122.209 [34843.877378] [tempesta fw] exiting... Apr 26 01:44:53 192.168.122.209 [34844.010434] [tdb] Shutdown Tempesta DB Apr 26 01:44:54 192.168.122.209 [34844.489967] End test: tls.test_tls_cert.InvalidKeyWithGoodCert.test Apr 26 01:44:54 192.168.122.209 [34844.507781] Start test: tls.test_tls_cert.InvalidHash.test Apr 26 01:44:55 192.168.122.209 [34845.694143] [tdb] Start Tempesta DB Apr 26 01:44:55 192.168.122.209 [34845.842163] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:44:55 192.168.122.209 [34846.155035] [tempesta tls] Warning: X509 - Signature algorithm with OID 1.2.840.10045.4.1 is unsupported Apr 26 01:44:55 192.168.122.209 [34846.155070] [tempesta fw] ERROR: tls_certificate: Invalid certificate specified, err=2600 Apr 26 01:44:55 192.168.122.209 [34846.159988] [tempesta fw] ERROR: configuration parsing error: [34846.159988] 4: tls_certificate /tmp/host/tempesta.crt; [34846.159988] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 01:44:55 192.168.122.209 [34846.164845] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 01:44:56 192.168.122.209 [34846.292126] [tempesta fw] exiting... Apr 26 01:44:56 192.168.122.209 [34846.424516] [tdb] Shutdown Tempesta DB Apr 26 01:44:56 192.168.122.209 [34846.953921] End test: tls.test_tls_cert.InvalidHash.test Apr 26 01:44:56 192.168.122.209 [34846.979114] Start test: tls.test_tls_cert.ECDSA_SHA384_SECP521.test Apr 26 01:44:57 192.168.122.209 [34848.015123] [tdb] Start Tempesta DB Apr 26 01:44:57 192.168.122.209 [34848.158837] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:44:58 192.168.122.209 [34848.439651] [tempesta tls] Warning: PK - Elliptic curve with OID 1.3.132.0.35 is unsupported Apr 26 01:44:58 192.168.122.209 [34848.441854] [tempesta fw] ERROR: tls_certificate: Invalid certificate specified, err=16 Apr 26 01:44:58 192.168.122.209 [34848.444096] [tempesta fw] ERROR: configuration parsing error: [34848.444096] 4: tls_certificate /tmp/host/tempesta.crt; [34848.444096] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 01:44:58 192.168.122.209 [34848.448909] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 01:44:58 192.168.122.209 [34848.573289] [tempesta fw] exiting... Apr 26 01:44:58 192.168.122.209 [34848.699622] [tdb] Shutdown Tempesta DB Apr 26 01:44:58 192.168.122.209 [34849.190358] End test: tls.test_tls_cert.ECDSA_SHA384_SECP521.test Apr 26 01:44:58 192.168.122.209 [34849.203880] Start test: tls.test_tls_cert.ECDSA_SHA384_SECP256.test Apr 26 01:44:59 192.168.122.209 [34850.160365] [tdb] Start Tempesta DB Apr 26 01:45:00 192.168.122.209 [34850.306415] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:45:00 192.168.122.209 [34850.584167] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34850.584167] Maybe that's fine, but it's worth checking the [34850.584167] config - if there is no relations between the [34850.584167] names, then host name confusion attack is possible. Apr 26 01:45:00 192.168.122.209 [34850.670529] [tempesta fw] Configuration processing is completed. Apr 26 01:45:00 192.168.122.209 [34850.739263] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:45:00 192.168.122.209 [34850.775920] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:45:00 192.168.122.209 [34850.808551] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:45:00 192.168.122.209 [34850.862506] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:45:00 192.168.122.209 [34850.906643] [tempesta fw] Tempesta FW is ready Apr 26 01:45:01 192.168.122.209 [34851.452619] [tdb] Close table 'client0.tdb' Apr 26 01:45:01 192.168.122.209 [34851.636773] [tdb] Close table 'sessions0.tdb' Apr 26 01:45:01 192.168.122.209 [34851.837508] [tdb] Close table 'filter0.tdb' Apr 26 01:45:01 192.168.122.209 [34851.837948] [tempesta fw] modules are stopped Apr 26 01:45:01 192.168.122.209 [34852.125607] [tempesta fw] exiting... Apr 26 01:45:02 192.168.122.209 [34852.246988] [tdb] Shutdown Tempesta DB Apr 26 01:45:02 192.168.122.209 [34852.479215] End test: tls.test_tls_cert.ECDSA_SHA384_SECP256.test Apr 26 01:45:02 192.168.122.209 [34852.509327] Start test: tls.test_tls_cert.ECDSA_SHA256_SECP256.test Apr 26 01:45:03 192.168.122.209 [34853.657180] [tdb] Start Tempesta DB Apr 26 01:45:03 192.168.122.209 [34853.817317] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:45:04 192.168.122.209 [34854.292232] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34854.292232] Maybe that's fine, but it's worth checking the [34854.292232] config - if there is no relations between the [34854.292232] names, then host name confusion attack is possible. Apr 26 01:45:04 192.168.122.209 [34854.374610] [tempesta fw] Configuration processing is completed. Apr 26 01:45:04 192.168.122.209 [34854.437830] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:45:04 192.168.122.209 [34854.474134] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:45:04 192.168.122.209 [34854.505657] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:45:04 192.168.122.209 [34854.578531] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:45:04 192.168.122.209 [34854.622492] [tempesta fw] Tempesta FW is ready Apr 26 01:45:04 192.168.122.209 [34855.223851] [tdb] Close table 'client0.tdb' Apr 26 01:45:05 192.168.122.209 [34855.414677] [tdb] Close table 'sessions0.tdb' Apr 26 01:45:05 192.168.122.209 [34855.646161] [tdb] Close table 'filter0.tdb' Apr 26 01:45:05 192.168.122.209 [34855.646657] [tempesta fw] modules are stopped Apr 26 01:45:05 192.168.122.209 [34855.842731] [tempesta fw] exiting... Apr 26 01:45:05 192.168.122.209 [34855.985640] [tdb] Shutdown Tempesta DB Apr 26 01:45:06 192.168.122.209 [34856.273595] End test: tls.test_tls_cert.ECDSA_SHA256_SECP256.test Apr 26 01:45:06 192.168.122.209 [34856.291761] Start test: tls.test_tls_cert.ECDSA_SHA256_SECP192.test Apr 26 01:45:07 192.168.122.209 [34857.494794] [tdb] Start Tempesta DB Apr 26 01:45:07 192.168.122.209 [34857.640681] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:45:07 192.168.122.209 [34858.080550] [tempesta tls] Warning: PK - Elliptic curve with OID 1.2.840.10045.3.1.1 is unsupported Apr 26 01:45:07 192.168.122.209 [34858.083363] [tempesta fw] ERROR: tls_certificate: Invalid certificate specified, err=16 Apr 26 01:45:07 192.168.122.209 [34858.085083] [tempesta fw] ERROR: configuration parsing error: [34858.085083] 4: tls_certificate /tmp/host/tempesta.crt; [34858.085083] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 01:45:07 192.168.122.209 [34858.087140] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 01:45:07 192.168.122.209 [34858.215778] [tempesta fw] exiting... Apr 26 01:45:08 192.168.122.209 [34858.336187] [tdb] Shutdown Tempesta DB Apr 26 01:45:08 192.168.122.209 [34858.864678] End test: tls.test_tls_cert.ECDSA_SHA256_SECP192.test Apr 26 01:45:08 192.168.122.209 [34858.884545] Start test: tls.test_tls_cert.BaseTlsSniWithHttpTable.test_with_san Apr 26 01:45:08 192.168.122.209 [34858.898502] End test: tls.test_tls_cert.BaseTlsSniWithHttpTable.test_with_san Apr 26 01:45:08 192.168.122.209 [34858.917214] Start test: tls.test_tls_cert.BaseTlsSniWithHttpTable.test_with_common_name Apr 26 01:45:08 192.168.122.209 [34858.932406] End test: tls.test_tls_cert.BaseTlsSniWithHttpTable.test_with_common_name Apr 26 01:45:08 192.168.122.209 [34858.946239] Start test: tls.test_tls_cert.BaseTlsSniWithHttpTable.test_with_any_host Apr 26 01:45:08 192.168.122.209 [34858.959998] End test: tls.test_tls_cert.BaseTlsSniWithHttpTable.test_with_any_host Apr 26 01:45:08 192.168.122.209 [34858.980273] Start test: tls.test_tls_cert.BaseTlsSniWithHttpTable.test_valid Apr 26 01:45:08 192.168.122.209 [34858.991562] End test: tls.test_tls_cert.BaseTlsSniWithHttpTable.test_valid Apr 26 01:45:08 192.168.122.209 [34859.004757] Start test: tls.test_tls_basic.TlsBasic.test_connection_close Apr 26 01:45:09 192.168.122.209 [34860.062620] [tdb] Start Tempesta DB Apr 26 01:45:09 192.168.122.209 [34860.195612] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:45:10 192.168.122.209 [34860.504011] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34860.504011] Maybe that's fine, but it's worth checking the [34860.504011] config - if there is no relations between the [34860.504011] names, then host name confusion attack is possible. Apr 26 01:45:10 192.168.122.209 [34860.586700] [tempesta fw] Configuration processing is completed. Apr 26 01:45:10 192.168.122.209 [34860.655425] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:45:10 192.168.122.209 [34860.695178] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:45:10 192.168.122.209 [34860.731754] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:45:10 192.168.122.209 [34860.770627] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:45:10 192.168.122.209 [34860.810571] [tempesta fw] Tempesta FW is ready Apr 26 01:45:11 192.168.122.209 [34861.382698] [tdb] Close table 'client0.tdb' Apr 26 01:45:11 192.168.122.209 [34861.588017] [tdb] Close table 'sessions0.tdb' Apr 26 01:45:11 192.168.122.209 [34861.815912] [tdb] Close table 'filter0.tdb' Apr 26 01:45:11 192.168.122.209 [34861.816386] [tempesta fw] modules are stopped Apr 26 01:45:11 192.168.122.209 [34862.019132] [tempesta fw] exiting... Apr 26 01:45:11 192.168.122.209 [34862.152056] [tdb] Shutdown Tempesta DB Apr 26 01:45:12 192.168.122.209 [34862.371485] End test: tls.test_tls_basic.TlsBasic.test_connection_close Apr 26 01:45:12 192.168.122.209 [34862.401580] Start test: tls.test_tls_basic.TlsBasic.test_bad_request Apr 26 01:45:13 192.168.122.209 [34863.580466] [tdb] Start Tempesta DB Apr 26 01:45:13 192.168.122.209 [34863.765066] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:45:13 192.168.122.209 [34864.223912] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34864.223912] Maybe that's fine, but it's worth checking the [34864.223912] config - if there is no relations between the [34864.223912] names, then host name confusion attack is possible. Apr 26 01:45:14 192.168.122.209 [34864.306673] [tempesta fw] Configuration processing is completed. Apr 26 01:45:14 192.168.122.209 [34864.364910] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:45:14 192.168.122.209 [34864.400977] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:45:14 192.168.122.209 [34864.437749] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:45:14 192.168.122.209 [34864.518700] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:45:14 192.168.122.209 [34864.558641] [tempesta fw] Tempesta FW is ready Apr 26 01:45:14 192.168.122.209 [34864.709693] [tempesta fw] Warning: Parser error: state=Req_HttpVer input(-6)=0x48('GET / HTxTP/1.1 [34864.709693] Host: localhost [34864.709693] [34864.709693] ') data_len=33 off=6 Apr 26 01:45:14 192.168.122.209 [34865.138364] [tdb] Close table 'client0.tdb' Apr 26 01:45:15 192.168.122.209 [34865.344136] [tdb] Close table 'sessions0.tdb' Apr 26 01:45:15 192.168.122.209 [34865.588163] [tdb] Close table 'filter0.tdb' Apr 26 01:45:15 192.168.122.209 [34865.588600] [tempesta fw] modules are stopped Apr 26 01:45:15 192.168.122.209 [34865.815342] [tempesta fw] exiting... Apr 26 01:45:15 192.168.122.209 [34865.979884] [tdb] Shutdown Tempesta DB Apr 26 01:45:15 192.168.122.209 [34866.235786] End test: tls.test_tls_basic.TlsBasic.test_bad_request Apr 26 01:45:16 192.168.122.209 [34866.249614] Start test: tls.test_tls_alpn_basic.TestALPN.test_proto_order_https_least_prio Apr 26 01:45:17 192.168.122.209 [34867.483654] [tdb] Start Tempesta DB Apr 26 01:45:17 192.168.122.209 [34867.639309] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:45:18 192.168.122.209 [34868.296074] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [34868.296074] Maybe that's fine, but it's worth checking the [34868.296074] config - if there is no relations between the [34868.296074] names, then host name confusion attack is possible. Apr 26 01:45:18 192.168.122.209 [34868.358790] [tempesta fw] Configuration processing is completed. Apr 26 01:45:18 192.168.122.209 [34868.424136] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:45:18 192.168.122.209 [34869.061109] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:45:18 192.168.122.209 [34869.103597] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:45:18 192.168.122.209 [34869.147328] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:45:18 192.168.122.209 [34869.238715] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:45:19 192.168.122.209 [34869.294721] [tempesta fw] Tempesta FW is ready Apr 26 01:45:19 192.168.122.209 [34869.951133] [tdb] Close table 'client0.tdb' Apr 26 01:45:19 192.168.122.209 [34870.141803] [tdb] Close table 'sessions0.tdb' Apr 26 01:45:23 192.168.122.209 [34873.450946] [tdb] Close table 'cache0.tdb' Apr 26 01:45:23 192.168.122.209 [34873.696019] [tdb] Close table 'filter0.tdb' Apr 26 01:45:23 192.168.122.209 [34873.696463] [tempesta fw] modules are stopped Apr 26 01:45:23 192.168.122.209 [34873.884796] [tempesta fw] exiting... Apr 26 01:45:23 192.168.122.209 [34874.087663] [tdb] Shutdown Tempesta DB Apr 26 01:45:24 192.168.122.209 [34874.357886] End test: tls.test_tls_alpn_basic.TestALPN.test_proto_order_https_least_prio Apr 26 01:45:24 192.168.122.209 [34874.374181] Start test: tls.test_tls_alpn_basic.TestALPN.test_proto_order_https Apr 26 01:45:25 192.168.122.209 [34875.685950] [tdb] Start Tempesta DB Apr 26 01:45:25 192.168.122.209 [34875.842907] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:45:27 192.168.122.209 [34877.368733] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [34877.368733] Maybe that's fine, but it's worth checking the [34877.368733] config - if there is no relations between the [34877.368733] names, then host name confusion attack is possible. Apr 26 01:45:27 192.168.122.209 [34877.411175] [tempesta fw] Configuration processing is completed. Apr 26 01:45:27 192.168.122.209 [34877.469929] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:45:27 192.168.122.209 [34877.910500] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:45:27 192.168.122.209 [34877.937551] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:45:27 192.168.122.209 [34877.964973] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:45:27 192.168.122.209 [34878.038878] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:45:27 192.168.122.209 [34878.086795] [tempesta fw] Tempesta FW is ready Apr 26 01:45:28 192.168.122.209 [34878.705216] [tdb] Close table 'client0.tdb' Apr 26 01:45:28 192.168.122.209 [34878.878470] [tdb] Close table 'sessions0.tdb' Apr 26 01:45:31 192.168.122.209 [34882.018503] [tdb] Close table 'cache0.tdb' Apr 26 01:45:32 192.168.122.209 [34882.271701] [tdb] Close table 'filter0.tdb' Apr 26 01:45:32 192.168.122.209 [34882.272150] [tempesta fw] modules are stopped Apr 26 01:45:32 192.168.122.209 [34882.461274] [tempesta fw] exiting... Apr 26 01:45:32 192.168.122.209 [34882.604106] [tdb] Shutdown Tempesta DB Apr 26 01:45:32 192.168.122.209 [34882.877067] End test: tls.test_tls_alpn_basic.TestALPN.test_proto_order_https Apr 26 01:45:32 192.168.122.209 [34882.895662] Start test: tls.test_tls_alpn_basic.TestALPN.test_proto_order_h2_least_prio Apr 26 01:45:33 192.168.122.209 [34883.966929] [tdb] Start Tempesta DB Apr 26 01:45:33 192.168.122.209 [34884.094915] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:45:35 192.168.122.209 [34885.568710] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [34885.568710] Maybe that's fine, but it's worth checking the [34885.568710] config - if there is no relations between the [34885.568710] names, then host name confusion attack is possible. Apr 26 01:45:35 192.168.122.209 [34885.619020] [tempesta fw] Configuration processing is completed. Apr 26 01:45:35 192.168.122.209 [34885.678695] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:45:35 192.168.122.209 [34886.096579] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:45:35 192.168.122.209 [34886.153225] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:45:35 192.168.122.209 [34886.179131] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:45:36 192.168.122.209 [34886.266939] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:45:36 192.168.122.209 [34886.318704] [tempesta fw] Tempesta FW is ready Apr 26 01:45:36 192.168.122.209 [34887.002407] [tdb] Close table 'client0.tdb' Apr 26 01:45:36 192.168.122.209 [34887.193337] [tdb] Close table 'sessions0.tdb' Apr 26 01:45:40 192.168.122.209 [34890.380315] [tdb] Close table 'cache0.tdb' Apr 26 01:45:40 192.168.122.209 [34890.632211] [tdb] Close table 'filter0.tdb' Apr 26 01:45:40 192.168.122.209 [34890.632687] [tempesta fw] modules are stopped Apr 26 01:45:40 192.168.122.209 [34890.811615] [tempesta fw] exiting... Apr 26 01:45:40 192.168.122.209 [34890.941222] [tdb] Shutdown Tempesta DB Apr 26 01:45:40 192.168.122.209 [34891.199633] End test: tls.test_tls_alpn_basic.TestALPN.test_proto_order_h2_least_prio Apr 26 01:45:40 192.168.122.209 [34891.217753] Start test: tls.test_tls_alpn_basic.TestALPN.test_proto_order_h2 Apr 26 01:45:42 192.168.122.209 [34892.463336] [tdb] Start Tempesta DB Apr 26 01:45:42 192.168.122.209 [34892.610217] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:45:43 192.168.122.209 [34894.112849] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [34894.112849] Maybe that's fine, but it's worth checking the [34894.112849] config - if there is no relations between the [34894.112849] names, then host name confusion attack is possible. Apr 26 01:45:43 192.168.122.209 [34894.163331] [tempesta fw] Configuration processing is completed. Apr 26 01:45:43 192.168.122.209 [34894.215819] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:45:44 192.168.122.209 [34894.631696] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:45:44 192.168.122.209 [34894.656822] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:45:44 192.168.122.209 [34894.682305] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:45:44 192.168.122.209 [34894.755041] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:45:44 192.168.122.209 [34894.798990] [tempesta fw] Tempesta FW is ready Apr 26 01:45:45 192.168.122.209 [34895.500711] [tdb] Close table 'client0.tdb' Apr 26 01:45:45 192.168.122.209 [34895.692102] [tdb] Close table 'sessions0.tdb' Apr 26 01:45:48 192.168.122.209 [34898.883868] [tdb] Close table 'cache0.tdb' Apr 26 01:45:48 192.168.122.209 [34899.150053] [tdb] Close table 'filter0.tdb' Apr 26 01:45:48 192.168.122.209 [34899.150458] [tempesta fw] modules are stopped Apr 26 01:45:49 192.168.122.209 [34899.319921] [tempesta fw] exiting... Apr 26 01:45:49 192.168.122.209 [34899.480085] [tdb] Shutdown Tempesta DB Apr 26 01:45:49 192.168.122.209 [34899.742720] End test: tls.test_tls_alpn_basic.TestALPN.test_proto_order_h2 Apr 26 01:45:49 192.168.122.209 [34899.762272] Start test: tls.test_tls_alpn_basic.TestALPN.test_proto_mixed_https Apr 26 01:45:50 192.168.122.209 [34901.031828] [tdb] Start Tempesta DB Apr 26 01:45:50 192.168.122.209 [34901.170036] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:45:52 192.168.122.209 [34902.621003] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [34902.621003] Maybe that's fine, but it's worth checking the [34902.621003] config - if there is no relations between the [34902.621003] names, then host name confusion attack is possible. Apr 26 01:45:52 192.168.122.209 [34902.663496] [tempesta fw] Configuration processing is completed. Apr 26 01:45:52 192.168.122.209 [34902.720096] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:45:52 192.168.122.209 [34903.139048] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:45:52 192.168.122.209 [34903.164834] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:45:52 192.168.122.209 [34903.190516] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:45:53 192.168.122.209 [34903.271156] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:45:53 192.168.122.209 [34903.327851] [tempesta fw] Tempesta FW is ready Apr 26 01:45:53 192.168.122.209 [34904.025997] [tdb] Close table 'client0.tdb' Apr 26 01:45:53 192.168.122.209 [34904.233276] [tdb] Close table 'sessions0.tdb' Apr 26 01:45:57 192.168.122.209 [34907.325838] [tdb] Close table 'cache0.tdb' Apr 26 01:45:57 192.168.122.209 [34907.584756] [tdb] Close table 'filter0.tdb' Apr 26 01:45:57 192.168.122.209 [34907.585217] [tempesta fw] modules are stopped Apr 26 01:45:57 192.168.122.209 [34907.776608] [tempesta fw] exiting... Apr 26 01:45:57 192.168.122.209 [34907.931184] [tdb] Shutdown Tempesta DB Apr 26 01:45:57 192.168.122.209 [34908.179900] End test: tls.test_tls_alpn_basic.TestALPN.test_proto_mixed_https Apr 26 01:45:57 192.168.122.209 [34908.197303] Start test: tls.test_tls_alpn_basic.TestALPN.test_proto_mixed_h2_only Apr 26 01:45:59 192.168.122.209 [34909.480768] [tdb] Start Tempesta DB Apr 26 01:45:59 192.168.122.209 [34909.626703] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:46:00 192.168.122.209 [34911.096749] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [34911.096749] Maybe that's fine, but it's worth checking the [34911.096749] config - if there is no relations between the [34911.096749] names, then host name confusion attack is possible. Apr 26 01:46:00 192.168.122.209 [34911.147331] [tempesta fw] Configuration processing is completed. Apr 26 01:46:00 192.168.122.209 [34911.207546] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:46:01 192.168.122.209 [34911.624583] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:46:01 192.168.122.209 [34911.650081] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:46:01 192.168.122.209 [34911.677356] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:46:01 192.168.122.209 [34911.755286] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:46:01 192.168.122.209 [34911.815202] [tempesta fw] Tempesta FW is ready Apr 26 01:46:02 192.168.122.209 [34912.508488] [tdb] Close table 'client0.tdb' Apr 26 01:46:02 192.168.122.209 [34912.695232] [tdb] Close table 'sessions0.tdb' Apr 26 01:46:05 192.168.122.209 [34915.850661] [tdb] Close table 'cache0.tdb' Apr 26 01:46:05 192.168.122.209 [34916.111522] [tdb] Close table 'filter0.tdb' Apr 26 01:46:05 192.168.122.209 [34916.111976] [tempesta fw] modules are stopped Apr 26 01:46:06 192.168.122.209 [34916.307704] [tempesta fw] exiting... Apr 26 01:46:06 192.168.122.209 [34916.478876] [tdb] Shutdown Tempesta DB Apr 26 01:46:06 192.168.122.209 [34916.731131] End test: tls.test_tls_alpn_basic.TestALPN.test_proto_mixed_h2_only Apr 26 01:46:06 192.168.122.209 [34916.752321] Start test: tls.test_tls_alpn_basic.TestALPN.test_proto_mixed_h2_https Apr 26 01:46:07 192.168.122.209 [34917.962034] [tdb] Start Tempesta DB Apr 26 01:46:07 192.168.122.209 [34918.120451] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:46:09 192.168.122.209 [34919.625477] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [34919.625477] Maybe that's fine, but it's worth checking the [34919.625477] config - if there is no relations between the [34919.625477] names, then host name confusion attack is possible. Apr 26 01:46:09 192.168.122.209 [34919.691640] [tempesta fw] Configuration processing is completed. Apr 26 01:46:09 192.168.122.209 [34919.763218] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:46:09 192.168.122.209 [34920.175575] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:46:09 192.168.122.209 [34920.202139] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:46:09 192.168.122.209 [34920.227540] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:46:10 192.168.122.209 [34920.295402] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:46:10 192.168.122.209 [34920.335313] [tempesta fw] Tempesta FW is ready Apr 26 01:46:10 192.168.122.209 [34921.004970] [tdb] Close table 'client0.tdb' Apr 26 01:46:10 192.168.122.209 [34921.229958] [tdb] Close table 'sessions0.tdb' Apr 26 01:46:14 192.168.122.209 [34924.366422] [tdb] Close table 'cache0.tdb' Apr 26 01:46:14 192.168.122.209 [34924.615266] [tdb] Close table 'filter0.tdb' Apr 26 01:46:14 192.168.122.209 [34924.615719] [tempesta fw] modules are stopped Apr 26 01:46:14 192.168.122.209 [34924.833866] [tempesta fw] exiting... Apr 26 01:46:14 192.168.122.209 [34924.986389] [tdb] Shutdown Tempesta DB Apr 26 01:46:15 192.168.122.209 [34925.271035] End test: tls.test_tls_alpn_basic.TestALPN.test_proto_mixed_h2_https Apr 26 01:46:15 192.168.122.209 [34925.282341] Start test: tls.test_tls_alpn_basic.TestALPN.test_negative_https Apr 26 01:46:16 192.168.122.209 [34926.542158] [tdb] Start Tempesta DB Apr 26 01:46:16 192.168.122.209 [34926.683362] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:46:17 192.168.122.209 [34928.193281] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [34928.193281] Maybe that's fine, but it's worth checking the [34928.193281] config - if there is no relations between the [34928.193281] names, then host name confusion attack is possible. Apr 26 01:46:18 192.168.122.209 [34928.243606] [tempesta fw] Configuration processing is completed. Apr 26 01:46:18 192.168.122.209 [34928.345187] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:46:18 192.168.122.209 [34928.773123] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:46:18 192.168.122.209 [34928.798854] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:46:18 192.168.122.209 [34928.825090] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:46:18 192.168.122.209 [34928.891479] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:46:18 192.168.122.209 [34928.931420] [tempesta fw] Tempesta FW is ready Apr 26 01:46:18 192.168.122.209 [34929.128898] [tempesta tls] Warning: [::ffff:127.0.0.1] ClientHello: cannot find matching ALPN for h2 Apr 26 01:46:19 192.168.122.209 [34929.687002] [tdb] Close table 'client0.tdb' Apr 26 01:46:19 192.168.122.209 [34929.882741] [tdb] Close table 'sessions0.tdb' Apr 26 01:46:22 192.168.122.209 [34933.015415] [tdb] Close table 'cache0.tdb' Apr 26 01:46:23 192.168.122.209 [34933.256314] [tdb] Close table 'filter0.tdb' Apr 26 01:46:23 192.168.122.209 [34933.256755] [tempesta fw] modules are stopped Apr 26 01:46:23 192.168.122.209 [34933.529695] [tempesta fw] exiting... Apr 26 01:46:23 192.168.122.209 [34933.716995] [tdb] Shutdown Tempesta DB Apr 26 01:46:23 192.168.122.209 [34933.998841] End test: tls.test_tls_alpn_basic.TestALPN.test_negative_https Apr 26 01:46:23 192.168.122.209 [34934.019090] Start test: tls.test_tls_alpn_basic.TestALPN.test_negative_h2 Apr 26 01:46:25 192.168.122.209 [34935.276527] [tdb] Start Tempesta DB Apr 26 01:46:25 192.168.122.209 [34935.427095] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:46:26 192.168.122.209 [34936.981332] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [34936.981332] Maybe that's fine, but it's worth checking the [34936.981332] config - if there is no relations between the [34936.981332] names, then host name confusion attack is possible. Apr 26 01:46:26 192.168.122.209 [34937.044030] [tempesta fw] Configuration processing is completed. Apr 26 01:46:26 192.168.122.209 [34937.107699] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:46:27 192.168.122.209 [34937.528641] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:46:27 192.168.122.209 [34937.554222] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:46:27 192.168.122.209 [34937.579502] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:46:27 192.168.122.209 [34937.659600] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:46:27 192.168.122.209 [34937.699551] [tempesta fw] Tempesta FW is ready Apr 26 01:46:27 192.168.122.209 [34937.877960] [tempesta tls] Warning: [::ffff:127.0.0.1] ClientHello: cannot find matching ALPN for http/1.1 Apr 26 01:46:28 192.168.122.209 [34938.471769] [tdb] Close table 'client0.tdb' Apr 26 01:46:28 192.168.122.209 [34938.660413] [tdb] Close table 'sessions0.tdb' Apr 26 01:46:31 192.168.122.209 [34941.862943] [tdb] Close table 'cache0.tdb' Apr 26 01:46:31 192.168.122.209 [34942.125291] [tdb] Close table 'filter0.tdb' Apr 26 01:46:31 192.168.122.209 [34942.125736] [tempesta fw] modules are stopped Apr 26 01:46:32 192.168.122.209 [34942.304999] [tempesta fw] exiting... Apr 26 01:46:32 192.168.122.209 [34942.465541] [tdb] Shutdown Tempesta DB Apr 26 01:46:32 192.168.122.209 [34942.720541] End test: tls.test_tls_alpn_basic.TestALPN.test_negative_h2 Apr 26 01:46:32 192.168.122.209 [34942.741321] Start test: tls.test_tls_alpn_basic.TestALPN.test_alpn_default Apr 26 01:46:33 192.168.122.209 [34944.000313] [tdb] Start Tempesta DB Apr 26 01:46:33 192.168.122.209 [34944.145347] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:46:35 192.168.122.209 [34945.725558] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [34945.725558] Maybe that's fine, but it's worth checking the [34945.725558] config - if there is no relations between the [34945.725558] names, then host name confusion attack is possible. Apr 26 01:46:35 192.168.122.209 [34945.787747] [tempesta fw] Configuration processing is completed. Apr 26 01:46:35 192.168.122.209 [34945.848008] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:46:36 192.168.122.209 [34946.271040] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:46:36 192.168.122.209 [34946.296470] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:46:36 192.168.122.209 [34946.322291] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:46:36 192.168.122.209 [34946.371692] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:46:36 192.168.122.209 [34946.423642] [tempesta fw] Tempesta FW is ready Apr 26 01:46:36 192.168.122.209 [34947.122817] [tdb] Close table 'client0.tdb' Apr 26 01:46:37 192.168.122.209 [34947.325315] [tdb] Close table 'sessions0.tdb' Apr 26 01:46:40 192.168.122.209 [34950.571377] [tdb] Close table 'cache0.tdb' Apr 26 01:46:40 192.168.122.209 [34950.822888] [tdb] Close table 'filter0.tdb' Apr 26 01:46:40 192.168.122.209 [34950.823334] [tempesta fw] modules are stopped Apr 26 01:46:40 192.168.122.209 [34951.071927] [tempesta fw] exiting... Apr 26 01:46:40 192.168.122.209 [34951.229784] [tdb] Shutdown Tempesta DB Apr 26 01:46:41 192.168.122.209 [34951.513226] End test: tls.test_tls_alpn_basic.TestALPN.test_alpn_default Apr 26 01:46:41 192.168.122.209 [34951.524874] Start test: cache.test_cache.TestCacheAgeInResponseH2.test Apr 26 01:46:42 192.168.122.209 [34953.056949] [tdb] Start Tempesta DB Apr 26 01:46:42 192.168.122.209 [34953.224299] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:46:44 192.168.122.209 [34954.793249] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34954.793249] Maybe that's fine, but it's worth checking the [34954.793249] config - if there is no relations between the [34954.793249] names, then host name confusion attack is possible. Apr 26 01:46:44 192.168.122.209 [34954.887839] [tempesta fw] Configuration processing is completed. Apr 26 01:46:44 192.168.122.209 [34954.986610] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:46:45 192.168.122.209 [34955.517067] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:46:45 192.168.122.209 [34955.548093] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:46:45 192.168.122.209 [34955.578041] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:46:45 192.168.122.209 [34955.619824] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:46:45 192.168.122.209 [34955.621542] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:46:45 192.168.122.209 [34955.671778] [tempesta fw] Tempesta FW is ready Apr 26 01:46:46 192.168.122.209 [34956.345666] [tdb] Close table 'client0.tdb' Apr 26 01:46:46 192.168.122.209 [34956.530699] [tdb] Close table 'sessions0.tdb' Apr 26 01:46:49 192.168.122.209 [34959.855897] [tdb] Close table 'cache0.tdb' Apr 26 01:46:49 192.168.122.209 [34960.132315] [tdb] Close table 'filter0.tdb' Apr 26 01:46:49 192.168.122.209 [34960.132816] [tempesta fw] modules are stopped Apr 26 01:46:50 192.168.122.209 [34960.401700] [tempesta fw] exiting... Apr 26 01:46:50 192.168.122.209 [34960.594460] [tdb] Shutdown Tempesta DB Apr 26 01:46:50 192.168.122.209 [34960.865111] End test: cache.test_cache.TestCacheAgeInResponseH2.test Apr 26 01:46:50 192.168.122.209 [34960.901327] Start test: cache.test_cache.TestCacheAgeInResponseHttp.test Apr 26 01:46:52 192.168.122.209 [34962.407766] [tdb] Start Tempesta DB Apr 26 01:46:52 192.168.122.209 [34962.576593] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:46:54 192.168.122.209 [34964.245366] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34964.245366] Maybe that's fine, but it's worth checking the [34964.245366] config - if there is no relations between the [34964.245366] names, then host name confusion attack is possible. Apr 26 01:46:54 192.168.122.209 [34964.331982] [tempesta fw] Configuration processing is completed. Apr 26 01:46:54 192.168.122.209 [34964.396093] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:46:54 192.168.122.209 [34964.831168] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:46:54 192.168.122.209 [34964.857372] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:46:54 192.168.122.209 [34964.886842] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:46:54 192.168.122.209 [34964.927930] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:46:54 192.168.122.209 [34964.929850] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:46:54 192.168.122.209 [34964.971904] [tempesta fw] Tempesta FW is ready Apr 26 01:46:55 192.168.122.209 [34965.608297] [tdb] Close table 'client0.tdb' Apr 26 01:46:55 192.168.122.209 [34965.795667] [tdb] Close table 'sessions0.tdb' Apr 26 01:46:58 192.168.122.209 [34969.058552] [tdb] Close table 'cache0.tdb' Apr 26 01:46:59 192.168.122.209 [34969.340231] [tdb] Close table 'filter0.tdb' Apr 26 01:46:59 192.168.122.209 [34969.340693] [tempesta fw] modules are stopped Apr 26 01:46:59 192.168.122.209 [34969.564690] [tempesta fw] exiting... Apr 26 01:46:59 192.168.122.209 [34969.738102] [tdb] Shutdown Tempesta DB Apr 26 01:46:59 192.168.122.209 [34970.003649] End test: cache.test_cache.TestCacheAgeInResponseHttp.test Apr 26 01:46:59 192.168.122.209 [34970.019433] Start test: cache.test_cache.TestCacheClean.test Apr 26 01:47:01 192.168.122.209 [34971.398721] [tdb] Start Tempesta DB Apr 26 01:47:01 192.168.122.209 [34971.573303] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:47:03 192.168.122.209 [34973.258114] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [34973.258114] Maybe that's fine, but it's worth checking the [34973.258114] config - if there is no relations between the [34973.258114] names, then host name confusion attack is possible. Apr 26 01:47:03 192.168.122.209 [34973.364153] [tempesta fw] Configuration processing is completed. Apr 26 01:47:03 192.168.122.209 [34973.427820] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:47:03 192.168.122.209 [34974.010329] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:47:03 192.168.122.209 [34974.045101] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:47:03 192.168.122.209 [34974.086185] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:47:03 192.168.122.209 [34974.136119] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:47:03 192.168.122.209 [34974.200006] [tempesta fw] Tempesta FW is ready Apr 26 01:47:07 192.168.122.209 [34977.906368] [tdb] Close table 'client0.tdb' Apr 26 01:47:07 192.168.122.209 [34978.092940] [tdb] Close table 'sessions0.tdb' Apr 26 01:47:10 192.168.122.209 [34981.238977] [tdb] Close table 'cache0.tdb' Apr 26 01:47:11 192.168.122.209 [34981.458271] [tdb] Close table 'filter0.tdb' Apr 26 01:47:11 192.168.122.209 [34981.458716] [tempesta fw] modules are stopped Apr 26 01:47:11 192.168.122.209 [34981.707186] [tempesta fw] exiting... Apr 26 01:47:11 192.168.122.209 [34981.878517] [tdb] Shutdown Tempesta DB Apr 26 01:47:11 192.168.122.209 [34982.153920] End test: cache.test_cache.TestCacheClean.test Apr 26 01:47:11 192.168.122.209 [34982.180448] Start test: cache.test_cache.TestCacheDockerH2Body.test Apr 26 01:47:15 192.168.122.209 [34985.753414] docker0: port 1(veth211189d) entered blocking state Apr 26 01:47:15 192.168.122.209 [34985.754029] docker0: port 1(veth211189d) entered disabled state Apr 26 01:47:15 192.168.122.209 [34985.756467] device veth211189d entered promiscuous mode Apr 26 01:47:16 192.168.122.209 [34986.885580] eth0: renamed from veth9aeef1b Apr 26 01:47:16 192.168.122.209 [34986.920994] IPv6: ADDRCONF(NETDEV_CHANGE): veth211189d: link becomes ready Apr 26 01:47:16 192.168.122.209 [34986.922612] docker0: port 1(veth211189d) entered blocking state Apr 26 01:47:16 192.168.122.209 [34986.923459] docker0: port 1(veth211189d) entered forwarding state Apr 26 01:47:16 192.168.122.209 [34986.924878] IPv6: ADDRCONF(NETDEV_CHANGE): docker0: link becomes ready Apr 26 01:47:18 192.168.122.209 [34988.405555] [tdb] Start Tempesta DB Apr 26 01:47:18 192.168.122.209 [34988.586646] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:47:19 192.168.122.209 [34989.701702] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [34989.701702] Maybe that's fine, but it's worth checking the [34989.701702] config - if there is no relations between the [34989.701702] names, then host name confusion attack is possible. Apr 26 01:47:19 192.168.122.209 [34989.840302] [tempesta fw] Configuration processing is completed. Apr 26 01:47:19 192.168.122.209 [34989.904702] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:47:20 192.168.122.209 [34990.450276] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:47:20 192.168.122.209 [34990.499125] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:47:20 192.168.122.209 [34990.549029] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:47:20 192.168.122.209 [34990.648490] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:47:20 192.168.122.209 [34990.650227] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:47:20 192.168.122.209 [34990.700150] [tempesta fw] Tempesta FW is ready Apr 26 01:47:21 192.168.122.209 [34991.702794] [tdb] Close table 'client0.tdb' Apr 26 01:47:21 192.168.122.209 [34991.904158] [tdb] Close table 'sessions0.tdb' Apr 26 01:47:24 192.168.122.209 [34995.205881] [tdb] Close table 'cache0.tdb' Apr 26 01:47:25 192.168.122.209 [34995.474610] [tdb] Close table 'filter0.tdb' Apr 26 01:47:25 192.168.122.209 [34995.475070] [tempesta fw] modules are stopped Apr 26 01:47:25 192.168.122.209 [34995.752981] [tempesta fw] exiting... Apr 26 01:47:25 192.168.122.209 [34995.916841] [tdb] Shutdown Tempesta DB Apr 26 01:47:26 192.168.122.209 [34996.452339] docker0: port 1(veth211189d) entered disabled state Apr 26 01:47:26 192.168.122.209 [34996.453048] veth9aeef1b: renamed from eth0 Apr 26 01:47:26 192.168.122.209 [34996.520808] docker0: port 1(veth211189d) entered disabled state Apr 26 01:47:26 192.168.122.209 [34996.526777] device veth211189d left promiscuous mode Apr 26 01:47:26 192.168.122.209 [34996.527437] docker0: port 1(veth211189d) entered disabled state Apr 26 01:47:26 192.168.122.209 [34996.813342] End test: cache.test_cache.TestCacheDockerH2Body.test Apr 26 01:47:26 192.168.122.209 [34996.834229] Start test: cache.test_cache.TestCacheDockerH2Headers.test Apr 26 01:47:28 192.168.122.209 [34998.474864] docker0: port 1(vethdd3d1a9) entered blocking state Apr 26 01:47:28 192.168.122.209 [34998.475531] docker0: port 1(vethdd3d1a9) entered disabled state Apr 26 01:47:28 192.168.122.209 [34998.481410] device vethdd3d1a9 entered promiscuous mode Apr 26 01:47:28 192.168.122.209 [34999.092622] eth0: renamed from vethb27b810 Apr 26 01:47:28 192.168.122.209 [34999.123962] IPv6: ADDRCONF(NETDEV_CHANGE): vethdd3d1a9: link becomes ready Apr 26 01:47:28 192.168.122.209 [34999.126939] docker0: port 1(vethdd3d1a9) entered blocking state Apr 26 01:47:28 192.168.122.209 [34999.127678] docker0: port 1(vethdd3d1a9) entered forwarding state Apr 26 01:47:30 192.168.122.209 [35000.484962] [tdb] Start Tempesta DB Apr 26 01:47:30 192.168.122.209 [35000.645165] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:47:31 192.168.122.209 [35002.125880] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35002.125880] Maybe that's fine, but it's worth checking the [35002.125880] config - if there is no relations between the [35002.125880] names, then host name confusion attack is possible. Apr 26 01:47:31 192.168.122.209 [35002.228484] [tempesta fw] Configuration processing is completed. Apr 26 01:47:32 192.168.122.209 [35002.291638] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:47:32 192.168.122.209 [35002.843347] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:47:32 192.168.122.209 [35002.876738] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:47:32 192.168.122.209 [35002.921618] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:47:32 192.168.122.209 [35003.028431] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:47:32 192.168.122.209 [35003.030239] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:47:32 192.168.122.209 [35003.068381] [tempesta fw] Tempesta FW is ready Apr 26 01:47:33 192.168.122.209 [35004.006107] [tdb] Close table 'client0.tdb' Apr 26 01:47:33 192.168.122.209 [35004.206707] [tdb] Close table 'sessions0.tdb' Apr 26 01:47:37 192.168.122.209 [35007.608879] [tdb] Close table 'cache0.tdb' Apr 26 01:47:37 192.168.122.209 [35007.870622] [tdb] Close table 'filter0.tdb' Apr 26 01:47:37 192.168.122.209 [35007.871065] [tempesta fw] modules are stopped Apr 26 01:47:37 192.168.122.209 [35008.118453] [tempesta fw] exiting... Apr 26 01:47:38 192.168.122.209 [35008.284963] [tdb] Shutdown Tempesta DB Apr 26 01:47:38 192.168.122.209 [35008.860567] docker0: port 1(vethdd3d1a9) entered disabled state Apr 26 01:47:38 192.168.122.209 [35008.861288] vethb27b810: renamed from eth0 Apr 26 01:47:38 192.168.122.209 [35008.943074] docker0: port 1(vethdd3d1a9) entered disabled state Apr 26 01:47:38 192.168.122.209 [35008.952095] device vethdd3d1a9 left promiscuous mode Apr 26 01:47:38 192.168.122.209 [35008.952924] docker0: port 1(vethdd3d1a9) entered disabled state Apr 26 01:47:39 192.168.122.209 [35009.248513] End test: cache.test_cache.TestCacheDockerH2Headers.test Apr 26 01:47:39 192.168.122.209 [35009.272572] Start test: cache.test_cache.TestCacheDockerHttpBody.test Apr 26 01:47:40 192.168.122.209 [35011.083635] docker0: port 1(veth69b9215) entered blocking state Apr 26 01:47:40 192.168.122.209 [35011.084426] docker0: port 1(veth69b9215) entered disabled state Apr 26 01:47:40 192.168.122.209 [35011.087372] device veth69b9215 entered promiscuous mode Apr 26 01:47:41 192.168.122.209 [35011.648264] eth0: renamed from veth9e802d0 Apr 26 01:47:41 192.168.122.209 [35011.682349] IPv6: ADDRCONF(NETDEV_CHANGE): veth69b9215: link becomes ready Apr 26 01:47:41 192.168.122.209 [35011.685188] docker0: port 1(veth69b9215) entered blocking state Apr 26 01:47:41 192.168.122.209 [35011.686080] docker0: port 1(veth69b9215) entered forwarding state Apr 26 01:47:42 192.168.122.209 [35013.088068] [tdb] Start Tempesta DB Apr 26 01:47:43 192.168.122.209 [35013.251618] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:47:44 192.168.122.209 [35014.709970] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35014.709970] Maybe that's fine, but it's worth checking the [35014.709970] config - if there is no relations between the [35014.709970] names, then host name confusion attack is possible. Apr 26 01:47:44 192.168.122.209 [35014.808695] [tempesta fw] Configuration processing is completed. Apr 26 01:47:44 192.168.122.209 [35014.869245] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:47:45 192.168.122.209 [35015.417157] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:47:45 192.168.122.209 [35015.463855] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:47:45 192.168.122.209 [35015.493318] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:47:45 192.168.122.209 [35015.572677] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:47:45 192.168.122.209 [35015.574454] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:47:45 192.168.122.209 [35015.612486] [tempesta fw] Tempesta FW is ready Apr 26 01:47:46 192.168.122.209 [35016.525490] [tdb] Close table 'client0.tdb' Apr 26 01:47:46 192.168.122.209 [35016.751192] [tdb] Close table 'sessions0.tdb' Apr 26 01:47:49 192.168.122.209 [35020.010803] [tdb] Close table 'cache0.tdb' Apr 26 01:47:50 192.168.122.209 [35020.291007] [tdb] Close table 'filter0.tdb' Apr 26 01:47:50 192.168.122.209 [35020.291499] [tempesta fw] modules are stopped Apr 26 01:47:50 192.168.122.209 [35020.509622] [tempesta fw] exiting... Apr 26 01:47:50 192.168.122.209 [35020.682581] [tdb] Shutdown Tempesta DB Apr 26 01:47:51 192.168.122.209 [35021.285701] docker0: port 1(veth69b9215) entered disabled state Apr 26 01:47:51 192.168.122.209 [35021.288638] veth9e802d0: renamed from eth0 Apr 26 01:47:51 192.168.122.209 [35021.360962] docker0: port 1(veth69b9215) entered disabled state Apr 26 01:47:51 192.168.122.209 [35021.367489] device veth69b9215 left promiscuous mode Apr 26 01:47:51 192.168.122.209 [35021.368328] docker0: port 1(veth69b9215) entered disabled state Apr 26 01:47:51 192.168.122.209 [35021.658818] End test: cache.test_cache.TestCacheDockerHttpBody.test Apr 26 01:47:51 192.168.122.209 [35021.683852] Start test: cache.test_cache.TestCacheDockerHttpHeaders.test Apr 26 01:47:53 192.168.122.209 [35023.301604] docker0: port 1(veth5e3d15c) entered blocking state Apr 26 01:47:53 192.168.122.209 [35023.302649] docker0: port 1(veth5e3d15c) entered disabled state Apr 26 01:47:53 192.168.122.209 [35023.306557] device veth5e3d15c entered promiscuous mode Apr 26 01:47:53 192.168.122.209 [35023.308375] docker0: port 1(veth5e3d15c) entered blocking state Apr 26 01:47:53 192.168.122.209 [35023.309460] docker0: port 1(veth5e3d15c) entered forwarding state Apr 26 01:47:53 192.168.122.209 [35023.310746] docker0: port 1(veth5e3d15c) entered disabled state Apr 26 01:47:53 192.168.122.209 [35023.877215] eth0: renamed from vetha140f96 Apr 26 01:47:53 192.168.122.209 [35023.903811] IPv6: ADDRCONF(NETDEV_CHANGE): veth5e3d15c: link becomes ready Apr 26 01:47:53 192.168.122.209 [35023.906113] docker0: port 1(veth5e3d15c) entered blocking state Apr 26 01:47:53 192.168.122.209 [35023.907349] docker0: port 1(veth5e3d15c) entered forwarding state Apr 26 01:47:55 192.168.122.209 [35025.282307] [tdb] Start Tempesta DB Apr 26 01:47:55 192.168.122.209 [35025.430811] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:47:56 192.168.122.209 [35026.954124] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35026.954124] Maybe that's fine, but it's worth checking the [35026.954124] config - if there is no relations between the [35026.954124] names, then host name confusion attack is possible. Apr 26 01:47:56 192.168.122.209 [35027.056815] [tempesta fw] Configuration processing is completed. Apr 26 01:47:56 192.168.122.209 [35027.129219] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:47:57 192.168.122.209 [35027.688844] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:47:57 192.168.122.209 [35027.740428] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:47:57 192.168.122.209 [35027.768222] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:47:57 192.168.122.209 [35027.864811] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:47:57 192.168.122.209 [35027.866588] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:47:57 192.168.122.209 [35027.904681] [tempesta fw] Tempesta FW is ready Apr 26 01:47:58 192.168.122.209 [35028.840941] [tdb] Close table 'client0.tdb' Apr 26 01:47:58 192.168.122.209 [35029.044218] [tdb] Close table 'sessions0.tdb' Apr 26 01:48:02 192.168.122.209 [35032.329189] [tdb] Close table 'cache0.tdb' Apr 26 01:48:02 192.168.122.209 [35032.575676] [tdb] Close table 'filter0.tdb' Apr 26 01:48:02 192.168.122.209 [35032.576144] [tempesta fw] modules are stopped Apr 26 01:48:02 192.168.122.209 [35032.758694] [tempesta fw] exiting... Apr 26 01:48:02 192.168.122.209 [35032.925001] [tdb] Shutdown Tempesta DB Apr 26 01:48:03 192.168.122.209 [35033.454630] docker0: port 1(veth5e3d15c) entered disabled state Apr 26 01:48:03 192.168.122.209 [35033.455366] vetha140f96: renamed from eth0 Apr 26 01:48:03 192.168.122.209 [35033.525848] docker0: port 1(veth5e3d15c) entered disabled state Apr 26 01:48:03 192.168.122.209 [35033.531703] device veth5e3d15c left promiscuous mode Apr 26 01:48:03 192.168.122.209 [35033.532217] docker0: port 1(veth5e3d15c) entered disabled state Apr 26 01:48:03 192.168.122.209 [35033.836743] End test: cache.test_cache.TestCacheDockerHttpHeaders.test Apr 26 01:48:03 192.168.122.209 [35033.860845] Start test: cache.test_cache.TestCacheDockerHttpsBody.test Apr 26 01:48:05 192.168.122.209 [35035.678660] docker0: port 1(vetha364999) entered blocking state Apr 26 01:48:05 192.168.122.209 [35035.679334] docker0: port 1(vetha364999) entered disabled state Apr 26 01:48:05 192.168.122.209 [35035.681884] device vetha364999 entered promiscuous mode Apr 26 01:48:06 192.168.122.209 [35036.245983] eth0: renamed from veth37785ea Apr 26 01:48:06 192.168.122.209 [35036.268167] IPv6: ADDRCONF(NETDEV_CHANGE): vetha364999: link becomes ready Apr 26 01:48:06 192.168.122.209 [35036.269867] docker0: port 1(vetha364999) entered blocking state Apr 26 01:48:06 192.168.122.209 [35036.270737] docker0: port 1(vetha364999) entered forwarding state Apr 26 01:48:07 192.168.122.209 [35037.606527] [tdb] Start Tempesta DB Apr 26 01:48:07 192.168.122.209 [35037.755513] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:48:09 192.168.122.209 [35039.242260] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35039.242260] Maybe that's fine, but it's worth checking the [35039.242260] config - if there is no relations between the [35039.242260] names, then host name confusion attack is possible. Apr 26 01:48:09 192.168.122.209 [35039.344980] [tempesta fw] Configuration processing is completed. Apr 26 01:48:09 192.168.122.209 [35039.403820] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:48:09 192.168.122.209 [35039.830840] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:48:09 192.168.122.209 [35039.856850] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:48:09 192.168.122.209 [35039.883516] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:48:09 192.168.122.209 [35039.965343] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:48:09 192.168.122.209 [35039.965940] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:48:09 192.168.122.209 [35040.032853] [tempesta fw] Tempesta FW is ready Apr 26 01:48:10 192.168.122.209 [35040.888407] [tdb] Close table 'client0.tdb' Apr 26 01:48:10 192.168.122.209 [35041.121827] [tdb] Close table 'sessions0.tdb' Apr 26 01:48:14 192.168.122.209 [35044.413049] [tdb] Close table 'cache0.tdb' Apr 26 01:48:14 192.168.122.209 [35044.673425] [tdb] Close table 'filter0.tdb' Apr 26 01:48:14 192.168.122.209 [35044.673891] [tempesta fw] modules are stopped Apr 26 01:48:14 192.168.122.209 [35044.942099] [tempesta fw] exiting... Apr 26 01:48:14 192.168.122.209 [35045.111994] [tdb] Shutdown Tempesta DB Apr 26 01:48:15 192.168.122.209 [35045.774271] docker0: port 1(vetha364999) entered disabled state Apr 26 01:48:15 192.168.122.209 [35045.775024] veth37785ea: renamed from eth0 Apr 26 01:48:15 192.168.122.209 [35045.839321] docker0: port 1(vetha364999) entered disabled state Apr 26 01:48:15 192.168.122.209 [35045.843555] device vetha364999 left promiscuous mode Apr 26 01:48:15 192.168.122.209 [35045.844060] docker0: port 1(vetha364999) entered disabled state Apr 26 01:48:15 192.168.122.209 [35046.136364] End test: cache.test_cache.TestCacheDockerHttpsBody.test Apr 26 01:48:15 192.168.122.209 [35046.162618] Start test: cache.test_cache.TestCacheDockerHttpsHeaders.test Apr 26 01:48:17 192.168.122.209 [35047.793707] docker0: port 1(vethe78311e) entered blocking state Apr 26 01:48:17 192.168.122.209 [35047.794336] docker0: port 1(vethe78311e) entered disabled state Apr 26 01:48:17 192.168.122.209 [35047.797172] device vethe78311e entered promiscuous mode Apr 26 01:48:18 192.168.122.209 [35048.342695] eth0: renamed from veth220f737 Apr 26 01:48:18 192.168.122.209 [35048.373200] IPv6: ADDRCONF(NETDEV_CHANGE): vethe78311e: link becomes ready Apr 26 01:48:18 192.168.122.209 [35048.376564] docker0: port 1(vethe78311e) entered blocking state Apr 26 01:48:18 192.168.122.209 [35048.377724] docker0: port 1(vethe78311e) entered forwarding state Apr 26 01:48:19 192.168.122.209 [35049.801999] [tdb] Start Tempesta DB Apr 26 01:48:19 192.168.122.209 [35049.952991] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:48:21 192.168.122.209 [35051.446402] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35051.446402] Maybe that's fine, but it's worth checking the [35051.446402] config - if there is no relations between the [35051.446402] names, then host name confusion attack is possible. Apr 26 01:48:21 192.168.122.209 [35051.549088] [tempesta fw] Configuration processing is completed. Apr 26 01:48:21 192.168.122.209 [35051.618263] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:48:21 192.168.122.209 [35052.119471] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:48:21 192.168.122.209 [35052.149579] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:48:21 192.168.122.209 [35052.179875] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:48:22 192.168.122.209 [35052.277161] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:48:22 192.168.122.209 [35052.278953] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:48:22 192.168.122.209 [35052.317035] [tempesta fw] Tempesta FW is ready Apr 26 01:48:22 192.168.122.209 [35053.149405] [tdb] Close table 'client0.tdb' Apr 26 01:48:23 192.168.122.209 [35053.394530] [tdb] Close table 'sessions0.tdb' Apr 26 01:48:26 192.168.122.209 [35056.772200] [tdb] Close table 'cache0.tdb' Apr 26 01:48:26 192.168.122.209 [35057.018258] [tdb] Close table 'filter0.tdb' Apr 26 01:48:26 192.168.122.209 [35057.018702] [tempesta fw] modules are stopped Apr 26 01:48:27 192.168.122.209 [35057.349370] [tempesta fw] exiting... Apr 26 01:48:27 192.168.122.209 [35057.545693] [tdb] Shutdown Tempesta DB Apr 26 01:48:27 192.168.122.209 [35058.174749] docker0: port 1(vethe78311e) entered disabled state Apr 26 01:48:27 192.168.122.209 [35058.176677] veth220f737: renamed from eth0 Apr 26 01:48:27 192.168.122.209 [35058.225978] docker0: port 1(vethe78311e) entered disabled state Apr 26 01:48:27 192.168.122.209 [35058.235710] device vethe78311e left promiscuous mode Apr 26 01:48:27 192.168.122.209 [35058.236444] docker0: port 1(vethe78311e) entered disabled state Apr 26 01:48:28 192.168.122.209 [35058.590320] End test: cache.test_cache.TestCacheDockerHttpsHeaders.test Apr 26 01:48:28 192.168.122.209 [35058.606384] Start test: cache.test_cache.TestCacheDublicateHeadersH2.test_raw Apr 26 01:48:29 192.168.122.209 [35059.995702] [tdb] Start Tempesta DB Apr 26 01:48:29 192.168.122.209 [35060.182862] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:48:31 192.168.122.209 [35061.782477] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35061.782477] Maybe that's fine, but it's worth checking the [35061.782477] config - if there is no relations between the [35061.782477] names, then host name confusion attack is possible. Apr 26 01:48:31 192.168.122.209 [35061.877238] [tempesta fw] Configuration processing is completed. Apr 26 01:48:31 192.168.122.209 [35061.937442] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:48:32 192.168.122.209 [35062.458355] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:48:32 192.168.122.209 [35062.497223] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:48:32 192.168.122.209 [35062.529000] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:48:32 192.168.122.209 [35062.609196] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:48:32 192.168.122.209 [35062.610938] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:48:32 192.168.122.209 [35062.657125] [tempesta fw] Tempesta FW is ready Apr 26 01:48:33 192.168.122.209 [35063.381779] [tdb] Close table 'client0.tdb' Apr 26 01:48:33 192.168.122.209 [35063.607154] [tdb] Close table 'sessions0.tdb' Apr 26 01:48:36 192.168.122.209 [35067.184432] [tdb] Close table 'cache0.tdb' Apr 26 01:48:37 192.168.122.209 [35067.463931] [tdb] Close table 'filter0.tdb' Apr 26 01:48:37 192.168.122.209 [35067.464418] [tempesta fw] modules are stopped Apr 26 01:48:37 192.168.122.209 [35067.684819] [tempesta fw] exiting... Apr 26 01:48:37 192.168.122.209 [35067.931891] [tdb] Shutdown Tempesta DB Apr 26 01:48:37 192.168.122.209 [35068.206808] End test: cache.test_cache.TestCacheDublicateHeadersH2.test_raw Apr 26 01:48:37 192.168.122.209 [35068.233061] Start test: cache.test_cache.TestCacheDublicateHeadersH2.test_regular Apr 26 01:48:39 192.168.122.209 [35069.770650] [tdb] Start Tempesta DB Apr 26 01:48:39 192.168.122.209 [35069.987639] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:48:41 192.168.122.209 [35071.687055] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35071.687055] Maybe that's fine, but it's worth checking the [35071.687055] config - if there is no relations between the [35071.687055] names, then host name confusion attack is possible. Apr 26 01:48:41 192.168.122.209 [35071.777359] [tempesta fw] Configuration processing is completed. Apr 26 01:48:41 192.168.122.209 [35071.846636] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:48:42 192.168.122.209 [35072.494350] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:48:42 192.168.122.209 [35072.535315] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:48:42 192.168.122.209 [35072.579337] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:48:42 192.168.122.209 [35072.625356] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:48:42 192.168.122.209 [35072.627184] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:48:42 192.168.122.209 [35072.665254] [tempesta fw] Tempesta FW is ready Apr 26 01:48:43 192.168.122.209 [35073.434924] [tdb] Close table 'client0.tdb' Apr 26 01:48:43 192.168.122.209 [35073.628951] [tdb] Close table 'sessions0.tdb' Apr 26 01:48:46 192.168.122.209 [35076.935269] [tdb] Close table 'cache0.tdb' Apr 26 01:48:46 192.168.122.209 [35077.194771] [tdb] Close table 'filter0.tdb' Apr 26 01:48:46 192.168.122.209 [35077.195237] [tempesta fw] modules are stopped Apr 26 01:48:47 192.168.122.209 [35077.482159] [tempesta fw] exiting... Apr 26 01:48:47 192.168.122.209 [35077.620942] [tdb] Shutdown Tempesta DB Apr 26 01:48:47 192.168.122.209 [35077.886270] End test: cache.test_cache.TestCacheDublicateHeadersH2.test_regular Apr 26 01:48:47 192.168.122.209 [35077.903745] Start test: cache.test_cache.TestCacheDublicateHeadersHttp.test_raw Apr 26 01:48:49 192.168.122.209 [35079.478569] [tdb] Start Tempesta DB Apr 26 01:48:49 192.168.122.209 [35079.676920] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:48:50 192.168.122.209 [35081.222780] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35081.222780] Maybe that's fine, but it's worth checking the [35081.222780] config - if there is no relations between the [35081.222780] names, then host name confusion attack is possible. Apr 26 01:48:51 192.168.122.209 [35081.317478] [tempesta fw] Configuration processing is completed. Apr 26 01:48:51 192.168.122.209 [35081.378242] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:48:51 192.168.122.209 [35081.885428] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:48:51 192.168.122.209 [35081.914845] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:48:51 192.168.122.209 [35081.944184] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:48:51 192.168.122.209 [35081.989423] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:48:51 192.168.122.209 [35081.991203] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:48:51 192.168.122.209 [35082.029404] [tempesta fw] Tempesta FW is ready Apr 26 01:48:52 192.168.122.209 [35082.716532] [tdb] Close table 'client0.tdb' Apr 26 01:48:52 192.168.122.209 [35082.918863] [tdb] Close table 'sessions0.tdb' Apr 26 01:48:55 192.168.122.209 [35086.128896] [tdb] Close table 'cache0.tdb' Apr 26 01:48:56 192.168.122.209 [35086.363226] [tdb] Close table 'filter0.tdb' Apr 26 01:48:56 192.168.122.209 [35086.363682] [tempesta fw] modules are stopped Apr 26 01:48:56 192.168.122.209 [35086.606590] [tempesta fw] exiting... Apr 26 01:48:56 192.168.122.209 [35086.776958] [tdb] Shutdown Tempesta DB Apr 26 01:48:56 192.168.122.209 [35087.038534] End test: cache.test_cache.TestCacheDublicateHeadersHttp.test_raw Apr 26 01:48:56 192.168.122.209 [35087.056017] Start test: cache.test_cache.TestCacheDublicateHeadersHttp.test_regular Apr 26 01:48:58 192.168.122.209 [35088.547418] [tdb] Start Tempesta DB Apr 26 01:48:58 192.168.122.209 [35088.711262] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:49:00 192.168.122.209 [35090.342869] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35090.342869] Maybe that's fine, but it's worth checking the [35090.342869] config - if there is no relations between the [35090.342869] names, then host name confusion attack is possible. Apr 26 01:49:00 192.168.122.209 [35090.425574] [tempesta fw] Configuration processing is completed. Apr 26 01:49:00 192.168.122.209 [35090.486363] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:49:00 192.168.122.209 [35091.044054] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:49:00 192.168.122.209 [35091.078211] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:49:00 192.168.122.209 [35091.128315] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:49:00 192.168.122.209 [35091.177534] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:49:00 192.168.122.209 [35091.179280] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:49:00 192.168.122.209 [35091.217486] [tempesta fw] Tempesta FW is ready Apr 26 01:49:01 192.168.122.209 [35091.884503] [tdb] Close table 'client0.tdb' Apr 26 01:49:01 192.168.122.209 [35092.090728] [tdb] Close table 'sessions0.tdb' Apr 26 01:49:05 192.168.122.209 [35095.365084] [tdb] Close table 'cache0.tdb' Apr 26 01:49:05 192.168.122.209 [35095.615001] [tdb] Close table 'filter0.tdb' Apr 26 01:49:05 192.168.122.209 [35095.615450] [tempesta fw] modules are stopped Apr 26 01:49:05 192.168.122.209 [35095.778984] [tempesta fw] exiting... Apr 26 01:49:05 192.168.122.209 [35095.947628] [tdb] Shutdown Tempesta DB Apr 26 01:49:05 192.168.122.209 [35096.207641] End test: cache.test_cache.TestCacheDublicateHeadersHttp.test_regular Apr 26 01:49:05 192.168.122.209 [35096.224850] Start test: cache.test_cache.TestCacheH2.test_cache_date Apr 26 01:49:07 192.168.122.209 [35097.783642] [tdb] Start Tempesta DB Apr 26 01:49:07 192.168.122.209 [35097.942807] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:49:09 192.168.122.209 [35099.554993] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35099.554993] Maybe that's fine, but it's worth checking the [35099.554993] config - if there is no relations between the [35099.554993] names, then host name confusion attack is possible. Apr 26 01:49:09 192.168.122.209 [35099.721695] [tempesta fw] Configuration processing is completed. Apr 26 01:49:09 192.168.122.209 [35099.791384] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:49:10 192.168.122.209 [35100.271247] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:49:10 192.168.122.209 [35100.301530] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:49:10 192.168.122.209 [35100.331188] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:49:10 192.168.122.209 [35100.369664] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:49:10 192.168.122.209 [35100.371464] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:49:10 192.168.122.209 [35100.413508] [tempesta fw] Tempesta FW is ready Apr 26 01:49:11 192.168.122.209 [35101.273789] [tdb] Close table 'client0.tdb' Apr 26 01:49:11 192.168.122.209 [35101.478828] [tdb] Close table 'sessions0.tdb' Apr 26 01:49:14 192.168.122.209 [35104.714030] [tdb] Close table 'cache0.tdb' Apr 26 01:49:14 192.168.122.209 [35104.961381] [tdb] Close table 'filter0.tdb' Apr 26 01:49:14 192.168.122.209 [35104.961846] [tempesta fw] modules are stopped Apr 26 01:49:14 192.168.122.209 [35105.178971] [tempesta fw] exiting... Apr 26 01:49:15 192.168.122.209 [35105.347826] [tdb] Shutdown Tempesta DB Apr 26 01:49:15 192.168.122.209 [35105.622034] End test: cache.test_cache.TestCacheH2.test_cache_date Apr 26 01:49:15 192.168.122.209 [35105.644105] Start test: cache.test_cache.TestCacheH2.test_disabled_cache_bypass_all Apr 26 01:49:16 192.168.122.209 [35107.197465] [tdb] Start Tempesta DB Apr 26 01:49:17 192.168.122.209 [35107.357769] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:49:18 192.168.122.209 [35108.819069] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35108.819069] Maybe that's fine, but it's worth checking the [35108.819069] config - if there is no relations between the [35108.819069] names, then host name confusion attack is possible. Apr 26 01:49:18 192.168.122.209 [35108.937805] [tempesta fw] Configuration processing is completed. Apr 26 01:49:18 192.168.122.209 [35109.036616] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:49:18 192.168.122.209 [35109.069808] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:49:18 192.168.122.209 [35109.102357] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:49:18 192.168.122.209 [35109.161771] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:49:18 192.168.122.209 [35109.163533] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:49:18 192.168.122.209 [35109.197735] [tempesta fw] Tempesta FW is ready Apr 26 01:49:19 192.168.122.209 [35110.094616] [tdb] Close table 'client0.tdb' Apr 26 01:49:20 192.168.122.209 [35110.295850] [tdb] Close table 'sessions0.tdb' Apr 26 01:49:20 192.168.122.209 [35110.543038] [tdb] Close table 'filter0.tdb' Apr 26 01:49:20 192.168.122.209 [35110.543467] [tempesta fw] modules are stopped Apr 26 01:49:20 192.168.122.209 [35110.726522] [tempesta fw] exiting... Apr 26 01:49:20 192.168.122.209 [35110.877459] [tdb] Shutdown Tempesta DB Apr 26 01:49:20 192.168.122.209 [35111.131988] End test: cache.test_cache.TestCacheH2.test_disabled_cache_bypass_all Apr 26 01:49:20 192.168.122.209 [35111.157706] Start test: cache.test_cache.TestCacheH2.test_disabled_cache_bypass_prefix Apr 26 01:49:22 192.168.122.209 [35112.639744] [tdb] Start Tempesta DB Apr 26 01:49:22 192.168.122.209 [35112.785271] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:49:23 192.168.122.209 [35113.663943] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35113.663943] Maybe that's fine, but it's worth checking the [35113.663943] config - if there is no relations between the [35113.663943] names, then host name confusion attack is possible. Apr 26 01:49:23 192.168.122.209 [35113.837874] [tempesta fw] Configuration processing is completed. Apr 26 01:49:23 192.168.122.209 [35113.900636] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:49:23 192.168.122.209 [35113.934717] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:49:23 192.168.122.209 [35113.969118] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:49:23 192.168.122.209 [35114.013867] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:49:23 192.168.122.209 [35114.015633] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:49:23 192.168.122.209 [35114.065782] [tempesta fw] Tempesta FW is ready Apr 26 01:49:24 192.168.122.209 [35114.893515] [tdb] Close table 'client0.tdb' Apr 26 01:49:24 192.168.122.209 [35115.118240] [tdb] Close table 'sessions0.tdb' Apr 26 01:49:25 192.168.122.209 [35115.341607] [tdb] Close table 'filter0.tdb' Apr 26 01:49:25 192.168.122.209 [35115.342048] [tempesta fw] modules are stopped Apr 26 01:49:25 192.168.122.209 [35115.604205] [tempesta fw] exiting... Apr 26 01:49:25 192.168.122.209 [35115.799823] [tdb] Shutdown Tempesta DB Apr 26 01:49:25 192.168.122.209 [35116.116796] End test: cache.test_cache.TestCacheH2.test_disabled_cache_bypass_prefix Apr 26 01:49:25 192.168.122.209 [35116.135046] Start test: cache.test_cache.TestCacheH2.test_disabled_cache_bypass_suffix Apr 26 01:49:27 192.168.122.209 [35117.431788] [tdb] Start Tempesta DB Apr 26 01:49:27 192.168.122.209 [35117.585337] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:49:28 192.168.122.209 [35118.407175] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35118.407175] Maybe that's fine, but it's worth checking the [35118.407175] config - if there is no relations between the [35118.407175] names, then host name confusion attack is possible. Apr 26 01:49:28 192.168.122.209 [35118.589973] [tempesta fw] Configuration processing is completed. Apr 26 01:49:28 192.168.122.209 [35118.670883] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:49:28 192.168.122.209 [35118.706656] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:49:28 192.168.122.209 [35118.737938] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:49:28 192.168.122.209 [35118.785891] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:49:28 192.168.122.209 [35118.787624] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:49:28 192.168.122.209 [35118.829833] [tempesta fw] Tempesta FW is ready Apr 26 01:49:29 192.168.122.209 [35119.660405] [tdb] Close table 'client0.tdb' Apr 26 01:49:29 192.168.122.209 [35119.861073] [tdb] Close table 'sessions0.tdb' Apr 26 01:49:29 192.168.122.209 [35120.109352] [tdb] Close table 'filter0.tdb' Apr 26 01:49:29 192.168.122.209 [35120.109781] [tempesta fw] modules are stopped Apr 26 01:49:30 192.168.122.209 [35120.289129] [tempesta fw] exiting... Apr 26 01:49:30 192.168.122.209 [35120.474016] [tdb] Shutdown Tempesta DB Apr 26 01:49:30 192.168.122.209 [35120.745881] End test: cache.test_cache.TestCacheH2.test_disabled_cache_bypass_suffix Apr 26 01:49:30 192.168.122.209 [35120.771165] Start test: cache.test_cache.TestCacheH2.test_disabled_cache_fulfill_all Apr 26 01:49:31 192.168.122.209 [35122.194203] [tdb] Start Tempesta DB Apr 26 01:49:32 192.168.122.209 [35122.361022] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:49:32 192.168.122.209 [35123.051290] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35123.051290] Maybe that's fine, but it's worth checking the [35123.051290] config - if there is no relations between the [35123.051290] names, then host name confusion attack is possible. Apr 26 01:49:32 192.168.122.209 [35123.165975] [tempesta fw] Configuration processing is completed. Apr 26 01:49:32 192.168.122.209 [35123.225859] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:49:33 192.168.122.209 [35123.265958] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:49:33 192.168.122.209 [35123.304587] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:49:33 192.168.122.209 [35123.389988] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:49:33 192.168.122.209 [35123.391763] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:49:33 192.168.122.209 [35123.429904] [tempesta fw] Tempesta FW is ready Apr 26 01:49:34 192.168.122.209 [35124.265379] [tdb] Close table 'client0.tdb' Apr 26 01:49:34 192.168.122.209 [35124.471228] [tdb] Close table 'sessions0.tdb' Apr 26 01:49:34 192.168.122.209 [35124.705720] [tdb] Close table 'filter0.tdb' Apr 26 01:49:34 192.168.122.209 [35124.706202] [tempesta fw] modules are stopped Apr 26 01:49:34 192.168.122.209 [35124.923001] [tempesta fw] exiting... Apr 26 01:49:34 192.168.122.209 [35125.116745] [tdb] Shutdown Tempesta DB Apr 26 01:49:35 192.168.122.209 [35125.359760] End test: cache.test_cache.TestCacheH2.test_disabled_cache_fulfill_all Apr 26 01:49:35 192.168.122.209 [35125.389817] Start test: cache.test_cache.TestCacheH2.test_disabled_cache_fulfill_prefix Apr 26 01:49:36 192.168.122.209 [35126.829090] [tdb] Start Tempesta DB Apr 26 01:49:36 192.168.122.209 [35127.009758] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:49:37 192.168.122.209 [35127.811319] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35127.811319] Maybe that's fine, but it's worth checking the [35127.811319] config - if there is no relations between the [35127.811319] names, then host name confusion attack is possible. Apr 26 01:49:37 192.168.122.209 [35127.974071] [tempesta fw] Configuration processing is completed. Apr 26 01:49:37 192.168.122.209 [35128.035263] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:49:37 192.168.122.209 [35128.069345] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:49:37 192.168.122.209 [35128.104238] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:49:37 192.168.122.209 [35128.142010] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:49:37 192.168.122.209 [35128.143747] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:49:37 192.168.122.209 [35128.193893] [tempesta fw] Tempesta FW is ready Apr 26 01:49:38 192.168.122.209 [35129.000858] [tdb] Close table 'client0.tdb' Apr 26 01:49:38 192.168.122.209 [35129.197188] [tdb] Close table 'sessions0.tdb' Apr 26 01:49:39 192.168.122.209 [35129.440275] [tdb] Close table 'filter0.tdb' Apr 26 01:49:39 192.168.122.209 [35129.440747] [tempesta fw] modules are stopped Apr 26 01:49:39 192.168.122.209 [35129.663151] [tempesta fw] exiting... Apr 26 01:49:39 192.168.122.209 [35129.855909] [tdb] Shutdown Tempesta DB Apr 26 01:49:39 192.168.122.209 [35130.156373] End test: cache.test_cache.TestCacheH2.test_disabled_cache_fulfill_prefix Apr 26 01:49:39 192.168.122.209 [35130.174321] Start test: cache.test_cache.TestCacheH2.test_disabled_cache_fulfill_suffix Apr 26 01:49:41 192.168.122.209 [35131.576239] [tdb] Start Tempesta DB Apr 26 01:49:41 192.168.122.209 [35131.731913] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:49:42 192.168.122.209 [35132.471449] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35132.471449] Maybe that's fine, but it's worth checking the [35132.471449] config - if there is no relations between the [35132.471449] names, then host name confusion attack is possible. Apr 26 01:49:42 192.168.122.209 [35132.634109] [tempesta fw] Configuration processing is completed. Apr 26 01:49:42 192.168.122.209 [35132.696648] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:49:42 192.168.122.209 [35132.730117] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:49:42 192.168.122.209 [35132.765430] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:49:42 192.168.122.209 [35132.810069] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:49:42 192.168.122.209 [35132.811833] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:49:42 192.168.122.209 [35132.849987] [tempesta fw] Tempesta FW is ready Apr 26 01:49:43 192.168.122.209 [35133.680923] [tdb] Close table 'client0.tdb' Apr 26 01:49:43 192.168.122.209 [35133.867448] [tdb] Close table 'sessions0.tdb' Apr 26 01:49:43 192.168.122.209 [35134.109911] [tdb] Close table 'filter0.tdb' Apr 26 01:49:43 192.168.122.209 [35134.110352] [tempesta fw] modules are stopped Apr 26 01:49:45 192.168.122.209 [35135.607570] [tempesta fw] exiting... Apr 26 01:49:45 192.168.122.209 [35136.215721] [tdb] Shutdown Tempesta DB Apr 26 01:49:46 192.168.122.209 [35136.483152] End test: cache.test_cache.TestCacheH2.test_disabled_cache_fulfill_suffix Apr 26 01:49:46 192.168.122.209 [35136.505429] Start test: cache.test_cache.TestCacheH2.test_disabled_cache_fulfill_suffix2 Apr 26 01:49:47 192.168.122.209 [35138.080943] [tdb] Start Tempesta DB Apr 26 01:49:48 192.168.122.209 [35138.294850] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:49:49 192.168.122.209 [35139.351715] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35139.351715] Maybe that's fine, but it's worth checking the [35139.351715] config - if there is no relations between the [35139.351715] names, then host name confusion attack is possible. Apr 26 01:49:50 192.168.122.209 [35140.350244] [tempesta fw] Configuration processing is completed. Apr 26 01:49:50 192.168.122.209 [35140.549722] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:49:50 192.168.122.209 [35140.586502] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:49:50 192.168.122.209 [35140.624446] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:49:50 192.168.122.209 [35140.778170] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:49:50 192.168.122.209 [35140.779939] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:49:50 192.168.122.209 [35140.818132] [tempesta fw] Tempesta FW is ready Apr 26 01:49:51 192.168.122.209 [35141.642979] [tdb] Close table 'client0.tdb' Apr 26 01:49:51 192.168.122.209 [35141.839213] [tdb] Close table 'sessions0.tdb' Apr 26 01:49:51 192.168.122.209 [35142.107358] [tdb] Close table 'filter0.tdb' Apr 26 01:49:51 192.168.122.209 [35142.107820] [tempesta fw] modules are stopped Apr 26 01:49:52 192.168.122.209 [35142.303797] [tempesta fw] exiting... Apr 26 01:49:52 192.168.122.209 [35142.462274] [tdb] Shutdown Tempesta DB Apr 26 01:49:52 192.168.122.209 [35142.733862] End test: cache.test_cache.TestCacheH2.test_disabled_cache_fulfill_suffix2 Apr 26 01:49:52 192.168.122.209 [35142.750329] Start test: cache.test_cache.TestCacheH2.test_replicated_cache_bypass_all Apr 26 01:49:53 192.168.122.209 [35144.200077] [tdb] Start Tempesta DB Apr 26 01:49:54 192.168.122.209 [35144.356045] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:49:54 192.168.122.209 [35144.987586] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35144.987586] Maybe that's fine, but it's worth checking the [35144.987586] config - if there is no relations between the [35144.987586] names, then host name confusion attack is possible. Apr 26 01:49:54 192.168.122.209 [35145.110275] [tempesta fw] Configuration processing is completed. Apr 26 01:49:54 192.168.122.209 [35145.166178] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:49:55 192.168.122.209 [35145.594344] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:49:55 192.168.122.209 [35145.623318] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:49:55 192.168.122.209 [35145.717530] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:49:55 192.168.122.209 [35145.762229] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:49:55 192.168.122.209 [35145.763987] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:49:55 192.168.122.209 [35145.802202] [tempesta fw] Tempesta FW is ready Apr 26 01:49:56 192.168.122.209 [35146.636001] [tdb] Close table 'client0.tdb' Apr 26 01:49:56 192.168.122.209 [35146.836793] [tdb] Close table 'sessions0.tdb' Apr 26 01:49:59 192.168.122.209 [35150.106640] [tdb] Close table 'cache0.tdb' Apr 26 01:50:00 192.168.122.209 [35150.363530] [tdb] Close table 'filter0.tdb' Apr 26 01:50:00 192.168.122.209 [35150.363985] [tempesta fw] modules are stopped Apr 26 01:50:00 192.168.122.209 [35150.572102] [tempesta fw] exiting... Apr 26 01:50:00 192.168.122.209 [35150.709972] [tdb] Shutdown Tempesta DB Apr 26 01:50:00 192.168.122.209 [35151.006513] End test: cache.test_cache.TestCacheH2.test_replicated_cache_bypass_all Apr 26 01:50:00 192.168.122.209 [35151.039501] Start test: cache.test_cache.TestCacheH2.test_replicated_cache_bypass_prefix Apr 26 01:50:02 192.168.122.209 [35152.454342] [tdb] Start Tempesta DB Apr 26 01:50:02 192.168.122.209 [35152.617139] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:50:04 192.168.122.209 [35154.243682] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35154.243682] Maybe that's fine, but it's worth checking the [35154.243682] config - if there is no relations between the [35154.243682] names, then host name confusion attack is possible. Apr 26 01:50:04 192.168.122.209 [35154.426377] [tempesta fw] Configuration processing is completed. Apr 26 01:50:04 192.168.122.209 [35154.487143] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:50:04 192.168.122.209 [35154.990986] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:50:04 192.168.122.209 [35155.022581] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:50:04 192.168.122.209 [35155.053867] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:50:04 192.168.122.209 [35155.102408] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:50:04 192.168.122.209 [35155.104148] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:50:04 192.168.122.209 [35155.142278] [tempesta fw] Tempesta FW is ready Apr 26 01:50:05 192.168.122.209 [35155.995868] [tdb] Close table 'client0.tdb' Apr 26 01:50:05 192.168.122.209 [35156.188604] [tdb] Close table 'sessions0.tdb' Apr 26 01:50:09 192.168.122.209 [35159.481396] [tdb] Close table 'cache0.tdb' Apr 26 01:50:09 192.168.122.209 [35159.732286] [tdb] Close table 'filter0.tdb' Apr 26 01:50:09 192.168.122.209 [35159.732733] [tempesta fw] modules are stopped Apr 26 01:50:09 192.168.122.209 [35159.904069] [tempesta fw] exiting... Apr 26 01:50:09 192.168.122.209 [35160.088300] [tdb] Shutdown Tempesta DB Apr 26 01:50:10 192.168.122.209 [35160.338384] End test: cache.test_cache.TestCacheH2.test_replicated_cache_bypass_prefix Apr 26 01:50:10 192.168.122.209 [35160.369868] Start test: cache.test_cache.TestCacheH2.test_replicated_cache_bypass_suffix Apr 26 01:50:11 192.168.122.209 [35161.801927] [tdb] Start Tempesta DB Apr 26 01:50:11 192.168.122.209 [35161.954443] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:50:13 192.168.122.209 [35163.555805] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35163.555805] Maybe that's fine, but it's worth checking the [35163.555805] config - if there is no relations between the [35163.555805] names, then host name confusion attack is possible. Apr 26 01:50:13 192.168.122.209 [35163.730552] [tempesta fw] Configuration processing is completed. Apr 26 01:50:13 192.168.122.209 [35163.791710] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:50:14 192.168.122.209 [35164.268849] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:50:14 192.168.122.209 [35164.307693] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:50:14 192.168.122.209 [35164.369760] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:50:14 192.168.122.209 [35164.410481] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:50:14 192.168.122.209 [35164.412206] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:50:14 192.168.122.209 [35164.450433] [tempesta fw] Tempesta FW is ready Apr 26 01:50:15 192.168.122.209 [35165.291000] [tdb] Close table 'client0.tdb' Apr 26 01:50:15 192.168.122.209 [35165.521330] [tdb] Close table 'sessions0.tdb' Apr 26 01:50:18 192.168.122.209 [35168.819168] [tdb] Close table 'cache0.tdb' Apr 26 01:50:18 192.168.122.209 [35169.107345] [tdb] Close table 'filter0.tdb' Apr 26 01:50:18 192.168.122.209 [35169.107845] [tempesta fw] modules are stopped Apr 26 01:50:19 192.168.122.209 [35169.295000] [tempesta fw] exiting... Apr 26 01:50:19 192.168.122.209 [35169.503288] [tdb] Shutdown Tempesta DB Apr 26 01:50:19 192.168.122.209 [35169.782660] End test: cache.test_cache.TestCacheH2.test_replicated_cache_bypass_suffix Apr 26 01:50:19 192.168.122.209 [35169.802521] Start test: cache.test_cache.TestCacheH2.test_replicated_cache_fulfill_all Apr 26 01:50:21 192.168.122.209 [35171.420212] [tdb] Start Tempesta DB Apr 26 01:50:21 192.168.122.209 [35171.624365] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:50:22 192.168.122.209 [35173.119944] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35173.119944] Maybe that's fine, but it's worth checking the [35173.119944] config - if there is no relations between the [35173.119944] names, then host name confusion attack is possible. Apr 26 01:50:22 192.168.122.209 [35173.234620] [tempesta fw] Configuration processing is completed. Apr 26 01:50:23 192.168.122.209 [35173.315038] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:50:23 192.168.122.209 [35173.858803] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:50:23 192.168.122.209 [35173.894166] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:50:23 192.168.122.209 [35173.932205] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:50:23 192.168.122.209 [35174.026649] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:50:23 192.168.122.209 [35174.028430] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:50:23 192.168.122.209 [35174.066498] [tempesta fw] Tempesta FW is ready Apr 26 01:50:24 192.168.122.209 [35174.930599] [tdb] Close table 'client0.tdb' Apr 26 01:50:24 192.168.122.209 [35175.143712] [tdb] Close table 'sessions0.tdb' Apr 26 01:50:28 192.168.122.209 [35178.641689] [tdb] Close table 'cache0.tdb' Apr 26 01:50:28 192.168.122.209 [35178.909349] [tdb] Close table 'filter0.tdb' Apr 26 01:50:28 192.168.122.209 [35178.909816] [tempesta fw] modules are stopped Apr 26 01:50:28 192.168.122.209 [35179.101744] [tempesta fw] exiting... Apr 26 01:50:29 192.168.122.209 [35179.312540] [tdb] Shutdown Tempesta DB Apr 26 01:50:29 192.168.122.209 [35179.568795] End test: cache.test_cache.TestCacheH2.test_replicated_cache_fulfill_all Apr 26 01:50:29 192.168.122.209 [35179.588364] Start test: cache.test_cache.TestCacheH2.test_replicated_cache_fulfill_prefix Apr 26 01:50:30 192.168.122.209 [35181.123190] [tdb] Start Tempesta DB Apr 26 01:50:31 192.168.122.209 [35181.301945] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:50:32 192.168.122.209 [35183.042258] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35183.042258] Maybe that's fine, but it's worth checking the [35183.042258] config - if there is no relations between the [35183.042258] names, then host name confusion attack is possible. Apr 26 01:50:32 192.168.122.209 [35183.206745] [tempesta fw] Configuration processing is completed. Apr 26 01:50:33 192.168.122.209 [35183.259181] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:50:33 192.168.122.209 [35183.707610] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:50:33 192.168.122.209 [35183.735212] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:50:33 192.168.122.209 [35183.798222] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:50:33 192.168.122.209 [35183.882735] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:50:33 192.168.122.209 [35183.884553] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:50:33 192.168.122.209 [35183.934670] [tempesta fw] Tempesta FW is ready Apr 26 01:50:34 192.168.122.209 [35184.820867] [tdb] Close table 'client0.tdb' Apr 26 01:50:34 192.168.122.209 [35185.028039] [tdb] Close table 'sessions0.tdb' Apr 26 01:50:38 192.168.122.209 [35188.314181] [tdb] Close table 'cache0.tdb' Apr 26 01:50:38 192.168.122.209 [35188.546603] [tdb] Close table 'filter0.tdb' Apr 26 01:50:38 192.168.122.209 [35188.547043] [tempesta fw] modules are stopped Apr 26 01:50:38 192.168.122.209 [35188.781243] [tempesta fw] exiting... Apr 26 01:50:38 192.168.122.209 [35188.934065] [tdb] Shutdown Tempesta DB Apr 26 01:50:38 192.168.122.209 [35189.151438] End test: cache.test_cache.TestCacheH2.test_replicated_cache_fulfill_prefix Apr 26 01:50:38 192.168.122.209 [35189.161616] Start test: cache.test_cache.TestCacheH2.test_replicated_cache_fulfill_suffix Apr 26 01:50:40 192.168.122.209 [35190.688401] [tdb] Start Tempesta DB Apr 26 01:50:40 192.168.122.209 [35190.887328] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:50:42 192.168.122.209 [35192.528199] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35192.528199] Maybe that's fine, but it's worth checking the [35192.528199] config - if there is no relations between the [35192.528199] names, then host name confusion attack is possible. Apr 26 01:50:42 192.168.122.209 [35192.702894] [tempesta fw] Configuration processing is completed. Apr 26 01:50:42 192.168.122.209 [35192.768372] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:50:43 192.168.122.209 [35193.317634] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:50:43 192.168.122.209 [35193.352193] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:50:43 192.168.122.209 [35193.386642] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:50:43 192.168.122.209 [35193.426839] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:50:43 192.168.122.209 [35193.428134] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:50:43 192.168.122.209 [35193.466793] [tempesta fw] Tempesta FW is ready Apr 26 01:50:44 192.168.122.209 [35194.340487] [tdb] Close table 'client0.tdb' Apr 26 01:50:44 192.168.122.209 [35194.545538] [tdb] Close table 'sessions0.tdb' Apr 26 01:50:47 192.168.122.209 [35197.813430] [tdb] Close table 'cache0.tdb' Apr 26 01:50:47 192.168.122.209 [35198.090053] [tdb] Close table 'filter0.tdb' Apr 26 01:50:47 192.168.122.209 [35198.090499] [tempesta fw] modules are stopped Apr 26 01:50:48 192.168.122.209 [35198.309864] [tempesta fw] exiting... Apr 26 01:50:48 192.168.122.209 [35198.469478] [tdb] Shutdown Tempesta DB Apr 26 01:50:48 192.168.122.209 [35198.718017] End test: cache.test_cache.TestCacheH2.test_replicated_cache_fulfill_suffix Apr 26 01:50:48 192.168.122.209 [35198.759286] Start test: cache.test_cache.TestCacheH2.test_replicated_cache_fulfill_suffix2 Apr 26 01:50:50 192.168.122.209 [35200.322481] [tdb] Start Tempesta DB Apr 26 01:50:50 192.168.122.209 [35200.497744] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:50:51 192.168.122.209 [35202.124234] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35202.124234] Maybe that's fine, but it's worth checking the [35202.124234] config - if there is no relations between the [35202.124234] names, then host name confusion attack is possible. Apr 26 01:50:52 192.168.122.209 [35202.310978] [tempesta fw] Configuration processing is completed. Apr 26 01:50:52 192.168.122.209 [35202.369163] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:50:52 192.168.122.209 [35202.803300] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:50:52 192.168.122.209 [35202.830758] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:50:52 192.168.122.209 [35202.857110] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:50:52 192.168.122.209 [35202.906873] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:50:52 192.168.122.209 [35202.908603] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:50:52 192.168.122.209 [35202.954909] [tempesta fw] Tempesta FW is ready Apr 26 01:50:53 192.168.122.209 [35203.817576] [tdb] Close table 'client0.tdb' Apr 26 01:50:53 192.168.122.209 [35204.018455] [tdb] Close table 'sessions0.tdb' Apr 26 01:50:57 192.168.122.209 [35207.291419] [tdb] Close table 'cache0.tdb' Apr 26 01:50:57 192.168.122.209 [35207.525901] [tdb] Close table 'filter0.tdb' Apr 26 01:50:57 192.168.122.209 [35207.526330] [tempesta fw] modules are stopped Apr 26 01:50:57 192.168.122.209 [35207.727628] [tempesta fw] exiting... Apr 26 01:50:57 192.168.122.209 [35207.891789] [tdb] Shutdown Tempesta DB Apr 26 01:50:57 192.168.122.209 [35208.127324] End test: cache.test_cache.TestCacheH2.test_replicated_cache_fulfill_suffix2 Apr 26 01:50:57 192.168.122.209 [35208.144333] Start test: cache.test_cache.TestCacheH2.test_sharding_cache_bypass_all Apr 26 01:50:59 192.168.122.209 [35209.711557] [tdb] Start Tempesta DB Apr 26 01:50:59 192.168.122.209 [35209.883780] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:51:01 192.168.122.209 [35211.408435] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35211.408435] Maybe that's fine, but it's worth checking the [35211.408435] config - if there is no relations between the [35211.408435] names, then host name confusion attack is possible. Apr 26 01:51:01 192.168.122.209 [35211.543432] [tempesta fw] Configuration processing is completed. Apr 26 01:51:01 192.168.122.209 [35211.647191] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:51:01 192.168.122.209 [35212.199269] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:51:01 192.168.122.209 [35212.232559] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:51:02 192.168.122.209 [35212.266859] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:51:02 192.168.122.209 [35212.319107] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:51:02 192.168.122.209 [35212.320850] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:51:02 192.168.122.209 [35212.375043] [tempesta fw] Tempesta FW is ready Apr 26 01:51:02 192.168.122.209 [35213.202897] [tdb] Close table 'client0.tdb' Apr 26 01:51:03 192.168.122.209 [35213.397757] [tdb] Close table 'sessions0.tdb' Apr 26 01:51:06 192.168.122.209 [35216.663629] [tdb] Close table 'cache0.tdb' Apr 26 01:51:06 192.168.122.209 [35216.896834] [tdb] Close table 'filter0.tdb' Apr 26 01:51:06 192.168.122.209 [35216.897274] [tempesta fw] modules are stopped Apr 26 01:51:06 192.168.122.209 [35217.165414] [tempesta fw] exiting... Apr 26 01:51:07 192.168.122.209 [35217.343897] [tdb] Shutdown Tempesta DB Apr 26 01:51:07 192.168.122.209 [35217.570130] End test: cache.test_cache.TestCacheH2.test_sharding_cache_bypass_all Apr 26 01:51:07 192.168.122.209 [35217.589021] Start test: cache.test_cache.TestCacheH2.test_sharding_cache_bypass_prefix Apr 26 01:51:08 192.168.122.209 [35219.124064] [tdb] Start Tempesta DB Apr 26 01:51:09 192.168.122.209 [35219.283855] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:51:10 192.168.122.209 [35220.848010] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35220.848010] Maybe that's fine, but it's worth checking the [35220.848010] config - if there is no relations between the [35220.848010] names, then host name confusion attack is possible. Apr 26 01:51:10 192.168.122.209 [35221.015169] [tempesta fw] Configuration processing is completed. Apr 26 01:51:10 192.168.122.209 [35221.072358] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:51:11 192.168.122.209 [35221.614568] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:51:11 192.168.122.209 [35221.653216] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:51:11 192.168.122.209 [35221.679945] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:51:11 192.168.122.209 [35221.715110] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:51:11 192.168.122.209 [35221.715894] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:51:11 192.168.122.209 [35221.767174] [tempesta fw] Tempesta FW is ready Apr 26 01:51:12 192.168.122.209 [35222.678544] [tdb] Close table 'client0.tdb' Apr 26 01:51:12 192.168.122.209 [35222.860342] [tdb] Close table 'sessions0.tdb' Apr 26 01:51:15 192.168.122.209 [35226.107815] [tdb] Close table 'cache0.tdb' Apr 26 01:51:16 192.168.122.209 [35226.362189] [tdb] Close table 'filter0.tdb' Apr 26 01:51:16 192.168.122.209 [35226.362659] [tempesta fw] modules are stopped Apr 26 01:51:16 192.168.122.209 [35226.584441] [tempesta fw] exiting... Apr 26 01:51:16 192.168.122.209 [35226.752306] [tdb] Shutdown Tempesta DB Apr 26 01:51:16 192.168.122.209 [35227.007453] End test: cache.test_cache.TestCacheH2.test_sharding_cache_bypass_prefix Apr 26 01:51:16 192.168.122.209 [35227.031587] Start test: cache.test_cache.TestCacheH2.test_sharding_cache_bypass_suffix Apr 26 01:51:18 192.168.122.209 [35228.484648] [tdb] Start Tempesta DB Apr 26 01:51:18 192.168.122.209 [35228.664961] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:51:20 192.168.122.209 [35230.324651] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35230.324651] Maybe that's fine, but it's worth checking the [35230.324651] config - if there is no relations between the [35230.324651] names, then host name confusion attack is possible. Apr 26 01:51:20 192.168.122.209 [35230.515409] [tempesta fw] Configuration processing is completed. Apr 26 01:51:20 192.168.122.209 [35230.579477] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:51:20 192.168.122.209 [35231.142632] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:51:20 192.168.122.209 [35231.185521] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:51:20 192.168.122.209 [35231.222364] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:51:21 192.168.122.209 [35231.303289] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:51:21 192.168.122.209 [35231.305049] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:51:21 192.168.122.209 [35231.351280] [tempesta fw] Tempesta FW is ready Apr 26 01:51:21 192.168.122.209 [35232.201053] [tdb] Close table 'client0.tdb' Apr 26 01:51:22 192.168.122.209 [35232.385497] [tdb] Close table 'sessions0.tdb' Apr 26 01:51:25 192.168.122.209 [35235.684857] [tdb] Close table 'cache0.tdb' Apr 26 01:51:25 192.168.122.209 [35235.937361] [tdb] Close table 'filter0.tdb' Apr 26 01:51:25 192.168.122.209 [35235.937814] [tempesta fw] modules are stopped Apr 26 01:51:25 192.168.122.209 [35236.138077] [tempesta fw] exiting... Apr 26 01:51:26 192.168.122.209 [35236.307770] [tdb] Shutdown Tempesta DB Apr 26 01:51:26 192.168.122.209 [35236.592196] End test: cache.test_cache.TestCacheH2.test_sharding_cache_bypass_suffix Apr 26 01:51:26 192.168.122.209 [35236.610586] Start test: cache.test_cache.TestCacheH2.test_sharding_cache_fulfill_all Apr 26 01:51:27 192.168.122.209 [35238.153350] [tdb] Start Tempesta DB Apr 26 01:51:28 192.168.122.209 [35238.342084] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:51:29 192.168.122.209 [35239.804757] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35239.804757] Maybe that's fine, but it's worth checking the [35239.804757] config - if there is no relations between the [35239.804757] names, then host name confusion attack is possible. Apr 26 01:51:29 192.168.122.209 [35239.931428] [tempesta fw] Configuration processing is completed. Apr 26 01:51:29 192.168.122.209 [35239.999577] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:51:30 192.168.122.209 [35240.562214] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:51:30 192.168.122.209 [35240.629468] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:51:30 192.168.122.209 [35240.673283] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:51:30 192.168.122.209 [35240.723414] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:51:30 192.168.122.209 [35240.725184] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:51:30 192.168.122.209 [35240.763416] [tempesta fw] Tempesta FW is ready Apr 26 01:51:31 192.168.122.209 [35241.640636] [tdb] Close table 'client0.tdb' Apr 26 01:51:31 192.168.122.209 [35241.845478] [tdb] Close table 'sessions0.tdb' Apr 26 01:51:34 192.168.122.209 [35245.122176] [tdb] Close table 'cache0.tdb' Apr 26 01:51:35 192.168.122.209 [35245.383022] [tdb] Close table 'filter0.tdb' Apr 26 01:51:35 192.168.122.209 [35245.383484] [tempesta fw] modules are stopped Apr 26 01:51:35 192.168.122.209 [35245.577214] [tempesta fw] exiting... Apr 26 01:51:35 192.168.122.209 [35245.756210] [tdb] Shutdown Tempesta DB Apr 26 01:51:35 192.168.122.209 [35246.059899] End test: cache.test_cache.TestCacheH2.test_sharding_cache_fulfill_all Apr 26 01:51:35 192.168.122.209 [35246.092518] Start test: cache.test_cache.TestCacheH2.test_sharding_cache_fulfill_prefix Apr 26 01:51:37 192.168.122.209 [35247.557784] [tdb] Start Tempesta DB Apr 26 01:51:37 192.168.122.209 [35247.718741] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:51:39 192.168.122.209 [35249.296870] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35249.296870] Maybe that's fine, but it's worth checking the [35249.296870] config - if there is no relations between the [35249.296870] names, then host name confusion attack is possible. Apr 26 01:51:39 192.168.122.209 [35249.475899] [tempesta fw] Configuration processing is completed. Apr 26 01:51:39 192.168.122.209 [35249.534047] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:51:39 192.168.122.209 [35249.973064] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:51:39 192.168.122.209 [35249.999454] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:51:39 192.168.122.209 [35250.026133] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:51:39 192.168.122.209 [35250.063563] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:51:39 192.168.122.209 [35250.065314] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:51:39 192.168.122.209 [35250.103505] [tempesta fw] Tempesta FW is ready Apr 26 01:51:40 192.168.122.209 [35250.978443] [tdb] Close table 'client0.tdb' Apr 26 01:51:40 192.168.122.209 [35251.195084] [tdb] Close table 'sessions0.tdb' Apr 26 01:51:44 192.168.122.209 [35254.474532] [tdb] Close table 'cache0.tdb' Apr 26 01:51:44 192.168.122.209 [35254.723667] [tdb] Close table 'filter0.tdb' Apr 26 01:51:44 192.168.122.209 [35254.724112] [tempesta fw] modules are stopped Apr 26 01:51:44 192.168.122.209 [35254.920833] [tempesta fw] exiting... Apr 26 01:51:44 192.168.122.209 [35255.112863] [tdb] Shutdown Tempesta DB Apr 26 01:51:45 192.168.122.209 [35255.357511] End test: cache.test_cache.TestCacheH2.test_sharding_cache_fulfill_prefix Apr 26 01:51:45 192.168.122.209 [35255.381707] Start test: cache.test_cache.TestCacheH2.test_sharding_cache_fulfill_suffix Apr 26 01:51:46 192.168.122.209 [35256.889957] [tdb] Start Tempesta DB Apr 26 01:51:46 192.168.122.209 [35257.049459] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:51:48 192.168.122.209 [35258.524654] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35258.524654] Maybe that's fine, but it's worth checking the [35258.524654] config - if there is no relations between the [35258.524654] names, then host name confusion attack is possible. Apr 26 01:51:48 192.168.122.209 [35258.699741] [tempesta fw] Configuration processing is completed. Apr 26 01:51:48 192.168.122.209 [35258.759202] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:51:48 192.168.122.209 [35259.202115] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:51:48 192.168.122.209 [35259.229290] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:51:49 192.168.122.209 [35259.276494] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:51:49 192.168.122.209 [35259.319683] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:51:49 192.168.122.209 [35259.321416] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:51:49 192.168.122.209 [35259.359633] [tempesta fw] Tempesta FW is ready Apr 26 01:51:49 192.168.122.209 [35260.162388] [tdb] Close table 'client0.tdb' Apr 26 01:51:50 192.168.122.209 [35260.360566] [tdb] Close table 'sessions0.tdb' Apr 26 01:51:53 192.168.122.209 [35263.582462] [tdb] Close table 'cache0.tdb' Apr 26 01:51:53 192.168.122.209 [35263.823520] [tdb] Close table 'filter0.tdb' Apr 26 01:51:53 192.168.122.209 [35263.823982] [tempesta fw] modules are stopped Apr 26 01:51:53 192.168.122.209 [35264.008074] [tempesta fw] exiting... Apr 26 01:51:53 192.168.122.209 [35264.186525] [tdb] Shutdown Tempesta DB Apr 26 01:51:54 192.168.122.209 [35264.441909] End test: cache.test_cache.TestCacheH2.test_sharding_cache_fulfill_suffix Apr 26 01:51:54 192.168.122.209 [35264.466296] Start test: cache.test_cache.TestCacheH2.test_sharding_cache_fulfill_suffix2 Apr 26 01:51:55 192.168.122.209 [35265.986682] [tdb] Start Tempesta DB Apr 26 01:51:55 192.168.122.209 [35266.175655] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:51:57 192.168.122.209 [35267.777634] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35267.777634] Maybe that's fine, but it's worth checking the [35267.777634] config - if there is no relations between the [35267.777634] names, then host name confusion attack is possible. Apr 26 01:51:57 192.168.122.209 [35267.936146] [tempesta fw] Configuration processing is completed. Apr 26 01:51:57 192.168.122.209 [35268.030312] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:51:58 192.168.122.209 [35268.595851] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:51:58 192.168.122.209 [35268.634167] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:51:58 192.168.122.209 [35268.659810] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:51:58 192.168.122.209 [35268.711812] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:51:58 192.168.122.209 [35268.713573] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:51:58 192.168.122.209 [35268.751782] [tempesta fw] Tempesta FW is ready Apr 26 01:51:59 192.168.122.209 [35269.620651] [tdb] Close table 'client0.tdb' Apr 26 01:51:59 192.168.122.209 [35269.811757] [tdb] Close table 'sessions0.tdb' Apr 26 01:52:02 192.168.122.209 [35273.053114] [tdb] Close table 'cache0.tdb' Apr 26 01:52:03 192.168.122.209 [35273.305242] [tdb] Close table 'filter0.tdb' Apr 26 01:52:03 192.168.122.209 [35273.305691] [tempesta fw] modules are stopped Apr 26 01:52:03 192.168.122.209 [35273.630893] [tempesta fw] exiting... Apr 26 01:52:03 192.168.122.209 [35273.806581] [tdb] Shutdown Tempesta DB Apr 26 01:52:03 192.168.122.209 [35274.050084] End test: cache.test_cache.TestCacheH2.test_sharding_cache_fulfill_suffix2 Apr 26 01:52:03 192.168.122.209 [35274.083104] Start test: cache.test_cache.TestCacheHttp.test_cache_date Apr 26 01:52:05 192.168.122.209 [35275.569257] [tdb] Start Tempesta DB Apr 26 01:52:05 192.168.122.209 [35275.732726] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:52:07 192.168.122.209 [35277.348881] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35277.348881] Maybe that's fine, but it's worth checking the [35277.348881] config - if there is no relations between the [35277.348881] names, then host name confusion attack is possible. Apr 26 01:52:07 192.168.122.209 [35277.515951] [tempesta fw] Configuration processing is completed. Apr 26 01:52:07 192.168.122.209 [35277.573663] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:52:07 192.168.122.209 [35278.009396] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:52:07 192.168.122.209 [35278.036262] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:52:07 192.168.122.209 [35278.063111] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:52:07 192.168.122.209 [35278.135961] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:52:07 192.168.122.209 [35278.137723] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:52:07 192.168.122.209 [35278.175830] [tempesta fw] Tempesta FW is ready Apr 26 01:52:08 192.168.122.209 [35278.925412] [tdb] Close table 'client0.tdb' Apr 26 01:52:08 192.168.122.209 [35279.108647] [tdb] Close table 'sessions0.tdb' Apr 26 01:52:12 192.168.122.209 [35282.444940] [tdb] Close table 'cache0.tdb' Apr 26 01:52:12 192.168.122.209 [35282.693805] [tdb] Close table 'filter0.tdb' Apr 26 01:52:12 192.168.122.209 [35282.694252] [tempesta fw] modules are stopped Apr 26 01:52:12 192.168.122.209 [35282.872996] [tempesta fw] exiting... Apr 26 01:52:12 192.168.122.209 [35283.036430] [tdb] Shutdown Tempesta DB Apr 26 01:52:12 192.168.122.209 [35283.240582] End test: cache.test_cache.TestCacheHttp.test_cache_date Apr 26 01:52:13 192.168.122.209 [35283.257523] Start test: cache.test_cache.TestCacheHttp.test_disabled_cache_bypass_all Apr 26 01:52:14 192.168.122.209 [35284.769433] [tdb] Start Tempesta DB Apr 26 01:52:14 192.168.122.209 [35284.928205] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:52:16 192.168.122.209 [35286.425428] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35286.425428] Maybe that's fine, but it's worth checking the [35286.425428] config - if there is no relations between the [35286.425428] names, then host name confusion attack is possible. Apr 26 01:52:16 192.168.122.209 [35286.544095] [tempesta fw] Configuration processing is completed. Apr 26 01:52:16 192.168.122.209 [35286.615708] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:52:16 192.168.122.209 [35286.655074] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:52:16 192.168.122.209 [35286.694936] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:52:16 192.168.122.209 [35286.756051] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:52:16 192.168.122.209 [35286.757792] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:52:16 192.168.122.209 [35286.800006] [tempesta fw] Tempesta FW is ready Apr 26 01:52:17 192.168.122.209 [35287.558305] [tdb] Close table 'client0.tdb' Apr 26 01:52:17 192.168.122.209 [35287.751549] [tdb] Close table 'sessions0.tdb' Apr 26 01:52:17 192.168.122.209 [35288.011342] [tdb] Close table 'filter0.tdb' Apr 26 01:52:17 192.168.122.209 [35288.011798] [tempesta fw] modules are stopped Apr 26 01:52:17 192.168.122.209 [35288.224745] [tempesta fw] exiting... Apr 26 01:52:18 192.168.122.209 [35288.400580] [tdb] Shutdown Tempesta DB Apr 26 01:52:18 192.168.122.209 [35288.640863] End test: cache.test_cache.TestCacheHttp.test_disabled_cache_bypass_all Apr 26 01:52:18 192.168.122.209 [35288.660994] Start test: cache.test_cache.TestCacheHttp.test_disabled_cache_bypass_prefix Apr 26 01:52:19 192.168.122.209 [35290.130518] [tdb] Start Tempesta DB Apr 26 01:52:20 192.168.122.209 [35290.285763] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:52:20 192.168.122.209 [35291.001404] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35291.001404] Maybe that's fine, but it's worth checking the [35291.001404] config - if there is no relations between the [35291.001404] names, then host name confusion attack is possible. Apr 26 01:52:20 192.168.122.209 [35291.180128] [tempesta fw] Configuration processing is completed. Apr 26 01:52:20 192.168.122.209 [35291.238278] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:52:21 192.168.122.209 [35291.269161] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:52:21 192.168.122.209 [35291.302016] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:52:21 192.168.122.209 [35291.344120] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:52:21 192.168.122.209 [35291.345897] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:52:21 192.168.122.209 [35291.384068] [tempesta fw] Tempesta FW is ready Apr 26 01:52:21 192.168.122.209 [35292.108320] [tdb] Close table 'client0.tdb' Apr 26 01:52:22 192.168.122.209 [35292.297823] [tdb] Close table 'sessions0.tdb' Apr 26 01:52:22 192.168.122.209 [35292.543168] [tdb] Close table 'filter0.tdb' Apr 26 01:52:22 192.168.122.209 [35292.543607] [tempesta fw] modules are stopped Apr 26 01:52:22 192.168.122.209 [35292.735726] [tempesta fw] exiting... Apr 26 01:52:22 192.168.122.209 [35292.917725] [tdb] Shutdown Tempesta DB Apr 26 01:52:22 192.168.122.209 [35293.175326] End test: cache.test_cache.TestCacheHttp.test_disabled_cache_bypass_prefix Apr 26 01:52:22 192.168.122.209 [35293.199631] Start test: cache.test_cache.TestCacheHttp.test_disabled_cache_bypass_suffix Apr 26 01:52:24 192.168.122.209 [35294.618640] [tdb] Start Tempesta DB Apr 26 01:52:24 192.168.122.209 [35294.787295] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:52:25 192.168.122.209 [35295.513496] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35295.513496] Maybe that's fine, but it's worth checking the [35295.513496] config - if there is no relations between the [35295.513496] names, then host name confusion attack is possible. Apr 26 01:52:25 192.168.122.209 [35295.680185] [tempesta fw] Configuration processing is completed. Apr 26 01:52:25 192.168.122.209 [35295.739474] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:52:25 192.168.122.209 [35295.765415] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:52:25 192.168.122.209 [35295.795084] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:52:25 192.168.122.209 [35295.848176] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:52:25 192.168.122.209 [35295.849909] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:52:25 192.168.122.209 [35295.888113] [tempesta fw] Tempesta FW is ready Apr 26 01:52:26 192.168.122.209 [35296.593539] [tdb] Close table 'client0.tdb' Apr 26 01:52:26 192.168.122.209 [35296.793771] [tdb] Close table 'sessions0.tdb' Apr 26 01:52:26 192.168.122.209 [35297.006950] [tdb] Close table 'filter0.tdb' Apr 26 01:52:26 192.168.122.209 [35297.007401] [tempesta fw] modules are stopped Apr 26 01:52:26 192.168.122.209 [35297.241810] [tempesta fw] exiting... Apr 26 01:52:27 192.168.122.209 [35297.400528] [tdb] Shutdown Tempesta DB Apr 26 01:52:27 192.168.122.209 [35297.651101] End test: cache.test_cache.TestCacheHttp.test_disabled_cache_bypass_suffix Apr 26 01:52:27 192.168.122.209 [35297.663992] Start test: cache.test_cache.TestCacheHttp.test_disabled_cache_fulfill_all Apr 26 01:52:28 192.168.122.209 [35299.056736] [tdb] Start Tempesta DB Apr 26 01:52:28 192.168.122.209 [35299.218212] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:52:29 192.168.122.209 [35299.941547] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35299.941547] Maybe that's fine, but it's worth checking the [35299.941547] config - if there is no relations between the [35299.941547] names, then host name confusion attack is possible. Apr 26 01:52:29 192.168.122.209 [35300.056250] [tempesta fw] Configuration processing is completed. Apr 26 01:52:29 192.168.122.209 [35300.122028] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:52:29 192.168.122.209 [35300.162331] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:52:29 192.168.122.209 [35300.200087] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:52:30 192.168.122.209 [35300.256207] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:52:30 192.168.122.209 [35300.257986] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:52:30 192.168.122.209 [35300.296169] [tempesta fw] Tempesta FW is ready Apr 26 01:52:30 192.168.122.209 [35301.014123] [tdb] Close table 'client0.tdb' Apr 26 01:52:30 192.168.122.209 [35301.199729] [tdb] Close table 'sessions0.tdb' Apr 26 01:52:31 192.168.122.209 [35301.435309] [tdb] Close table 'filter0.tdb' Apr 26 01:52:31 192.168.122.209 [35301.435761] [tempesta fw] modules are stopped Apr 26 01:52:31 192.168.122.209 [35301.657778] [tempesta fw] exiting... Apr 26 01:52:31 192.168.122.209 [35301.822625] [tdb] Shutdown Tempesta DB Apr 26 01:52:31 192.168.122.209 [35302.058681] End test: cache.test_cache.TestCacheHttp.test_disabled_cache_fulfill_all Apr 26 01:52:31 192.168.122.209 [35302.081325] Start test: cache.test_cache.TestCacheHttp.test_disabled_cache_fulfill_prefix Apr 26 01:52:33 192.168.122.209 [35303.573018] [tdb] Start Tempesta DB Apr 26 01:52:33 192.168.122.209 [35303.722949] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:52:34 192.168.122.209 [35304.545584] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35304.545584] Maybe that's fine, but it's worth checking the [35304.545584] config - if there is no relations between the [35304.545584] names, then host name confusion attack is possible. Apr 26 01:52:34 192.168.122.209 [35304.740307] [tempesta fw] Configuration processing is completed. Apr 26 01:52:34 192.168.122.209 [35304.798456] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:52:34 192.168.122.209 [35304.828146] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:52:34 192.168.122.209 [35304.858188] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:52:34 192.168.122.209 [35304.904265] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:52:34 192.168.122.209 [35304.906017] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:52:34 192.168.122.209 [35304.944227] [tempesta fw] Tempesta FW is ready Apr 26 01:52:35 192.168.122.209 [35305.671830] [tdb] Close table 'client0.tdb' Apr 26 01:52:35 192.168.122.209 [35305.871400] [tdb] Close table 'sessions0.tdb' Apr 26 01:52:35 192.168.122.209 [35306.111051] [tdb] Close table 'filter0.tdb' Apr 26 01:52:35 192.168.122.209 [35306.111485] [tempesta fw] modules are stopped Apr 26 01:52:36 192.168.122.209 [35306.289215] [tempesta fw] exiting... Apr 26 01:52:36 192.168.122.209 [35306.438850] [tdb] Shutdown Tempesta DB Apr 26 01:52:36 192.168.122.209 [35306.665808] End test: cache.test_cache.TestCacheHttp.test_disabled_cache_fulfill_prefix Apr 26 01:52:36 192.168.122.209 [35306.695952] Start test: cache.test_cache.TestCacheHttp.test_disabled_cache_fulfill_suffix Apr 26 01:52:37 192.168.122.209 [35308.188921] [tdb] Start Tempesta DB Apr 26 01:52:38 192.168.122.209 [35308.356534] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:52:38 192.168.122.209 [35309.141719] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35309.141719] Maybe that's fine, but it's worth checking the [35309.141719] config - if there is no relations between the [35309.141719] names, then host name confusion attack is possible. Apr 26 01:52:39 192.168.122.209 [35309.316578] [tempesta fw] Configuration processing is completed. Apr 26 01:52:39 192.168.122.209 [35309.380933] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:52:39 192.168.122.209 [35309.421629] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:52:39 192.168.122.209 [35309.459501] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:52:39 192.168.122.209 [35309.508330] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:52:39 192.168.122.209 [35309.510126] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:52:39 192.168.122.209 [35309.548291] [tempesta fw] Tempesta FW is ready Apr 26 01:52:40 192.168.122.209 [35310.285387] [tdb] Close table 'client0.tdb' Apr 26 01:52:40 192.168.122.209 [35310.473831] [tdb] Close table 'sessions0.tdb' Apr 26 01:52:40 192.168.122.209 [35310.718738] [tdb] Close table 'filter0.tdb' Apr 26 01:52:40 192.168.122.209 [35310.719177] [tempesta fw] modules are stopped Apr 26 01:52:40 192.168.122.209 [35310.924682] [tempesta fw] exiting... Apr 26 01:52:40 192.168.122.209 [35311.080391] [tdb] Shutdown Tempesta DB Apr 26 01:52:41 192.168.122.209 [35311.349131] End test: cache.test_cache.TestCacheHttp.test_disabled_cache_fulfill_suffix Apr 26 01:52:41 192.168.122.209 [35311.372811] Start test: cache.test_cache.TestCacheHttp.test_disabled_cache_fulfill_suffix2 Apr 26 01:52:42 192.168.122.209 [35312.826434] [tdb] Start Tempesta DB Apr 26 01:52:42 192.168.122.209 [35312.963406] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:52:43 192.168.122.209 [35313.713731] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35313.713731] Maybe that's fine, but it's worth checking the [35313.713731] config - if there is no relations between the [35313.713731] names, then host name confusion attack is possible. Apr 26 01:52:43 192.168.122.209 [35313.884417] [tempesta fw] Configuration processing is completed. Apr 26 01:52:43 192.168.122.209 [35313.948747] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:52:43 192.168.122.209 [35313.987625] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 01:52:43 192.168.122.209 [35314.025790] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 01:52:43 192.168.122.209 [35314.072411] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:52:43 192.168.122.209 [35314.074153] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:52:43 192.168.122.209 [35314.112348] [tempesta fw] Tempesta FW is ready Apr 26 01:52:44 192.168.122.209 [35314.829328] [tdb] Close table 'client0.tdb' Apr 26 01:52:44 192.168.122.209 [35315.017449] [tdb] Close table 'sessions0.tdb' Apr 26 01:52:45 192.168.122.209 [35315.292163] [tdb] Close table 'filter0.tdb' Apr 26 01:52:45 192.168.122.209 [35315.292629] [tempesta fw] modules are stopped Apr 26 01:52:45 192.168.122.209 [35315.475989] [tempesta fw] exiting... Apr 26 01:52:45 192.168.122.209 [35315.628176] [tdb] Shutdown Tempesta DB Apr 26 01:52:45 192.168.122.209 [35315.866941] End test: cache.test_cache.TestCacheHttp.test_disabled_cache_fulfill_suffix2 Apr 26 01:52:45 192.168.122.209 [35315.885808] Start test: cache.test_cache.TestCacheHttp.test_replicated_cache_bypass_all Apr 26 01:52:47 192.168.122.209 [35317.316554] [tdb] Start Tempesta DB Apr 26 01:52:47 192.168.122.209 [35317.485708] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:52:47 192.168.122.209 [35318.189748] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35318.189748] Maybe that's fine, but it's worth checking the [35318.189748] config - if there is no relations between the [35318.189748] names, then host name confusion attack is possible. Apr 26 01:52:48 192.168.122.209 [35318.316534] [tempesta fw] Configuration processing is completed. Apr 26 01:52:48 192.168.122.209 [35318.375671] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:52:48 192.168.122.209 [35318.823636] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:52:48 192.168.122.209 [35318.881735] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:52:48 192.168.122.209 [35318.909031] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:52:48 192.168.122.209 [35318.972476] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:52:48 192.168.122.209 [35318.974229] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:52:48 192.168.122.209 [35319.012407] [tempesta fw] Tempesta FW is ready Apr 26 01:52:49 192.168.122.209 [35319.708492] [tdb] Close table 'client0.tdb' Apr 26 01:52:49 192.168.122.209 [35319.881504] [tdb] Close table 'sessions0.tdb' Apr 26 01:52:52 192.168.122.209 [35323.177957] [tdb] Close table 'cache0.tdb' Apr 26 01:52:53 192.168.122.209 [35323.435518] [tdb] Close table 'filter0.tdb' Apr 26 01:52:53 192.168.122.209 [35323.435961] [tempesta fw] modules are stopped Apr 26 01:52:53 192.168.122.209 [35323.638632] [tempesta fw] exiting... Apr 26 01:52:53 192.168.122.209 [35323.772817] [tdb] Shutdown Tempesta DB Apr 26 01:52:53 192.168.122.209 [35324.014566] End test: cache.test_cache.TestCacheHttp.test_replicated_cache_bypass_all Apr 26 01:52:53 192.168.122.209 [35324.042289] Start test: cache.test_cache.TestCacheHttp.test_replicated_cache_bypass_prefix Apr 26 01:52:55 192.168.122.209 [35325.603995] [tdb] Start Tempesta DB Apr 26 01:52:55 192.168.122.209 [35325.780652] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:52:57 192.168.122.209 [35327.393922] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35327.393922] Maybe that's fine, but it's worth checking the [35327.393922] config - if there is no relations between the [35327.393922] names, then host name confusion attack is possible. Apr 26 01:52:57 192.168.122.209 [35327.572902] [tempesta fw] Configuration processing is completed. Apr 26 01:52:57 192.168.122.209 [35327.635982] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:52:57 192.168.122.209 [35328.188964] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:52:57 192.168.122.209 [35328.224035] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:52:58 192.168.122.209 [35328.258705] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:52:58 192.168.122.209 [35328.304569] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:52:58 192.168.122.209 [35328.306299] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:52:58 192.168.122.209 [35328.352545] [tempesta fw] Tempesta FW is ready Apr 26 01:52:58 192.168.122.209 [35329.111652] [tdb] Close table 'client0.tdb' Apr 26 01:52:59 192.168.122.209 [35329.303907] [tdb] Close table 'sessions0.tdb' Apr 26 01:53:02 192.168.122.209 [35332.584745] [tdb] Close table 'cache0.tdb' Apr 26 01:53:02 192.168.122.209 [35332.839019] [tdb] Close table 'filter0.tdb' Apr 26 01:53:02 192.168.122.209 [35332.839483] [tempesta fw] modules are stopped Apr 26 01:53:02 192.168.122.209 [35333.010758] [tempesta fw] exiting... Apr 26 01:53:02 192.168.122.209 [35333.162004] [tdb] Shutdown Tempesta DB Apr 26 01:53:03 192.168.122.209 [35333.438993] End test: cache.test_cache.TestCacheHttp.test_replicated_cache_bypass_prefix Apr 26 01:53:03 192.168.122.209 [35333.459621] Start test: cache.test_cache.TestCacheHttp.test_replicated_cache_bypass_suffix Apr 26 01:53:04 192.168.122.209 [35334.807288] [tdb] Start Tempesta DB Apr 26 01:53:04 192.168.122.209 [35334.971947] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:53:06 192.168.122.209 [35336.577915] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35336.577915] Maybe that's fine, but it's worth checking the [35336.577915] config - if there is no relations between the [35336.577915] names, then host name confusion attack is possible. Apr 26 01:53:06 192.168.122.209 [35336.760714] [tempesta fw] Configuration processing is completed. Apr 26 01:53:06 192.168.122.209 [35336.812663] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:53:06 192.168.122.209 [35337.248235] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:53:07 192.168.122.209 [35337.275955] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:53:07 192.168.122.209 [35337.302483] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:53:07 192.168.122.209 [35337.368701] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:53:07 192.168.122.209 [35337.370442] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:53:07 192.168.122.209 [35337.408643] [tempesta fw] Tempesta FW is ready Apr 26 01:53:07 192.168.122.209 [35338.156114] [tdb] Close table 'client0.tdb' Apr 26 01:53:08 192.168.122.209 [35338.350663] [tdb] Close table 'sessions0.tdb' Apr 26 01:53:11 192.168.122.209 [35341.494496] [tdb] Close table 'cache0.tdb' Apr 26 01:53:11 192.168.122.209 [35341.758362] [tdb] Close table 'filter0.tdb' Apr 26 01:53:11 192.168.122.209 [35341.758803] [tempesta fw] modules are stopped Apr 26 01:53:11 192.168.122.209 [35341.953598] [tempesta fw] exiting... Apr 26 01:53:11 192.168.122.209 [35342.108708] [tdb] Shutdown Tempesta DB Apr 26 01:53:12 192.168.122.209 [35342.359206] End test: cache.test_cache.TestCacheHttp.test_replicated_cache_bypass_suffix Apr 26 01:53:12 192.168.122.209 [35342.377841] Start test: cache.test_cache.TestCacheHttp.test_replicated_cache_fulfill_all Apr 26 01:53:13 192.168.122.209 [35343.842376] [tdb] Start Tempesta DB Apr 26 01:53:13 192.168.122.209 [35343.999639] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:53:15 192.168.122.209 [35345.505843] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35345.505843] Maybe that's fine, but it's worth checking the [35345.505843] config - if there is no relations between the [35345.505843] names, then host name confusion attack is possible. Apr 26 01:53:15 192.168.122.209 [35345.620813] [tempesta fw] Configuration processing is completed. Apr 26 01:53:15 192.168.122.209 [35345.685318] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:53:15 192.168.122.209 [35346.224097] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:53:16 192.168.122.209 [35346.264418] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:53:16 192.168.122.209 [35346.300796] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:53:16 192.168.122.209 [35346.344812] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:53:16 192.168.122.209 [35346.346549] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:53:16 192.168.122.209 [35346.396755] [tempesta fw] Tempesta FW is ready Apr 26 01:53:16 192.168.122.209 [35347.197951] [tdb] Close table 'client0.tdb' Apr 26 01:53:17 192.168.122.209 [35347.393800] [tdb] Close table 'sessions0.tdb' Apr 26 01:53:20 192.168.122.209 [35350.633840] [tdb] Close table 'cache0.tdb' Apr 26 01:53:20 192.168.122.209 [35350.877822] [tdb] Close table 'filter0.tdb' Apr 26 01:53:20 192.168.122.209 [35350.878264] [tempesta fw] modules are stopped Apr 26 01:53:20 192.168.122.209 [35351.081962] [tempesta fw] exiting... Apr 26 01:53:20 192.168.122.209 [35351.247038] [tdb] Shutdown Tempesta DB Apr 26 01:53:21 192.168.122.209 [35351.504583] End test: cache.test_cache.TestCacheHttp.test_replicated_cache_fulfill_all Apr 26 01:53:21 192.168.122.209 [35351.523382] Start test: cache.test_cache.TestCacheHttp.test_replicated_cache_fulfill_prefix Apr 26 01:53:22 192.168.122.209 [35352.750788] [tdb] Start Tempesta DB Apr 26 01:53:22 192.168.122.209 [35352.927220] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:53:24 192.168.122.209 [35354.358263] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35354.358263] Maybe that's fine, but it's worth checking the [35354.358263] config - if there is no relations between the [35354.358263] names, then host name confusion attack is possible. Apr 26 01:53:24 192.168.122.209 [35354.528938] [tempesta fw] Configuration processing is completed. Apr 26 01:53:24 192.168.122.209 [35354.580427] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:53:24 192.168.122.209 [35355.034903] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:53:24 192.168.122.209 [35355.065018] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:53:24 192.168.122.209 [35355.093366] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:53:24 192.168.122.209 [35355.156910] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:53:24 192.168.122.209 [35355.158620] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:53:24 192.168.122.209 [35355.196858] [tempesta fw] Tempesta FW is ready Apr 26 01:53:25 192.168.122.209 [35355.898348] [tdb] Close table 'client0.tdb' Apr 26 01:53:25 192.168.122.209 [35356.114712] [tdb] Close table 'sessions0.tdb' Apr 26 01:53:29 192.168.122.209 [35359.351500] [tdb] Close table 'cache0.tdb' Apr 26 01:53:29 192.168.122.209 [35359.590578] [tdb] Close table 'filter0.tdb' Apr 26 01:53:29 192.168.122.209 [35359.591033] [tempesta fw] modules are stopped Apr 26 01:53:29 192.168.122.209 [35359.792235] [tempesta fw] exiting... Apr 26 01:53:29 192.168.122.209 [35359.919741] [tdb] Shutdown Tempesta DB Apr 26 01:53:29 192.168.122.209 [35360.142916] End test: cache.test_cache.TestCacheHttp.test_replicated_cache_fulfill_prefix Apr 26 01:53:29 192.168.122.209 [35360.169050] Start test: cache.test_cache.TestCacheHttp.test_replicated_cache_fulfill_suffix Apr 26 01:53:31 192.168.122.209 [35361.367016] [tdb] Start Tempesta DB Apr 26 01:53:31 192.168.122.209 [35361.527973] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:53:32 192.168.122.209 [35363.074203] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35363.074203] Maybe that's fine, but it's worth checking the [35363.074203] config - if there is no relations between the [35363.074203] names, then host name confusion attack is possible. Apr 26 01:53:33 192.168.122.209 [35363.249041] [tempesta fw] Configuration processing is completed. Apr 26 01:53:33 192.168.122.209 [35363.322104] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:53:33 192.168.122.209 [35363.763895] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:53:33 192.168.122.209 [35363.791003] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:53:33 192.168.122.209 [35363.818238] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:53:33 192.168.122.209 [35363.860963] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:53:33 192.168.122.209 [35363.862163] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:53:33 192.168.122.209 [35363.908979] [tempesta fw] Tempesta FW is ready Apr 26 01:53:34 192.168.122.209 [35364.619208] [tdb] Close table 'client0.tdb' Apr 26 01:53:34 192.168.122.209 [35364.815418] [tdb] Close table 'sessions0.tdb' Apr 26 01:53:37 192.168.122.209 [35368.136517] [tdb] Close table 'cache0.tdb' Apr 26 01:53:38 192.168.122.209 [35368.400586] [tdb] Close table 'filter0.tdb' Apr 26 01:53:38 192.168.122.209 [35368.401091] [tempesta fw] modules are stopped Apr 26 01:53:38 192.168.122.209 [35368.578683] [tempesta fw] exiting... Apr 26 01:53:38 192.168.122.209 [35368.735691] [tdb] Shutdown Tempesta DB Apr 26 01:53:38 192.168.122.209 [35368.980126] End test: cache.test_cache.TestCacheHttp.test_replicated_cache_fulfill_suffix Apr 26 01:53:38 192.168.122.209 [35369.004037] Start test: cache.test_cache.TestCacheHttp.test_replicated_cache_fulfill_suffix2 Apr 26 01:53:39 192.168.122.209 [35370.229412] [tdb] Start Tempesta DB Apr 26 01:53:40 192.168.122.209 [35370.397853] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:53:41 192.168.122.209 [35371.858420] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35371.858420] Maybe that's fine, but it's worth checking the [35371.858420] config - if there is no relations between the [35371.858420] names, then host name confusion attack is possible. Apr 26 01:53:41 192.168.122.209 [35372.045154] [tempesta fw] Configuration processing is completed. Apr 26 01:53:41 192.168.122.209 [35372.104743] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:53:42 192.168.122.209 [35372.597197] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:53:42 192.168.122.209 [35372.634375] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:53:42 192.168.122.209 [35372.662445] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:53:42 192.168.122.209 [35372.725156] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:53:42 192.168.122.209 [35372.726901] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:53:42 192.168.122.209 [35372.769092] [tempesta fw] Tempesta FW is ready Apr 26 01:53:43 192.168.122.209 [35373.480232] [tdb] Close table 'client0.tdb' Apr 26 01:53:43 192.168.122.209 [35373.676687] [tdb] Close table 'sessions0.tdb' Apr 26 01:53:46 192.168.122.209 [35376.960229] [tdb] Close table 'cache0.tdb' Apr 26 01:53:46 192.168.122.209 [35377.247185] [tdb] Close table 'filter0.tdb' Apr 26 01:53:46 192.168.122.209 [35377.247627] [tempesta fw] modules are stopped Apr 26 01:53:47 192.168.122.209 [35377.448713] [tempesta fw] exiting... Apr 26 01:53:47 192.168.122.209 [35377.620321] [tdb] Shutdown Tempesta DB Apr 26 01:53:47 192.168.122.209 [35377.879380] End test: cache.test_cache.TestCacheHttp.test_replicated_cache_fulfill_suffix2 Apr 26 01:53:47 192.168.122.209 [35377.903350] Start test: cache.test_cache.TestCacheHttp.test_sharding_cache_bypass_all Apr 26 01:53:48 192.168.122.209 [35379.097392] [tdb] Start Tempesta DB Apr 26 01:53:49 192.168.122.209 [35379.261166] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:53:50 192.168.122.209 [35380.690542] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35380.690542] Maybe that's fine, but it's worth checking the [35380.690542] config - if there is no relations between the [35380.690542] names, then host name confusion attack is possible. Apr 26 01:53:50 192.168.122.209 [35380.821273] [tempesta fw] Configuration processing is completed. Apr 26 01:53:50 192.168.122.209 [35380.914378] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:53:51 192.168.122.209 [35381.357372] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:53:51 192.168.122.209 [35381.385059] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:53:51 192.168.122.209 [35381.414751] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:53:51 192.168.122.209 [35381.457207] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:53:51 192.168.122.209 [35381.458563] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:53:51 192.168.122.209 [35381.497189] [tempesta fw] Tempesta FW is ready Apr 26 01:53:51 192.168.122.209 [35382.226723] [tdb] Close table 'client0.tdb' Apr 26 01:53:52 192.168.122.209 [35382.430676] [tdb] Close table 'sessions0.tdb' Apr 26 01:53:55 192.168.122.209 [35385.644846] [tdb] Close table 'cache0.tdb' Apr 26 01:53:55 192.168.122.209 [35385.964747] [tdb] Close table 'filter0.tdb' Apr 26 01:53:55 192.168.122.209 [35385.965972] [tempesta fw] modules are stopped Apr 26 01:53:55 192.168.122.209 [35386.212289] [tempesta fw] exiting... Apr 26 01:53:56 192.168.122.209 [35386.358648] [tdb] Shutdown Tempesta DB Apr 26 01:53:56 192.168.122.209 [35386.597009] End test: cache.test_cache.TestCacheHttp.test_sharding_cache_bypass_all Apr 26 01:53:56 192.168.122.209 [35386.615859] Start test: cache.test_cache.TestCacheHttp.test_sharding_cache_bypass_prefix Apr 26 01:53:57 192.168.122.209 [35387.833533] [tdb] Start Tempesta DB Apr 26 01:53:57 192.168.122.209 [35387.996126] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:53:59 192.168.122.209 [35389.498905] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35389.498905] Maybe that's fine, but it's worth checking the [35389.498905] config - if there is no relations between the [35389.498905] names, then host name confusion attack is possible. Apr 26 01:53:59 192.168.122.209 [35389.665413] [tempesta fw] Configuration processing is completed. Apr 26 01:53:59 192.168.122.209 [35389.717930] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:53:59 192.168.122.209 [35390.168144] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:53:59 192.168.122.209 [35390.199392] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:53:59 192.168.122.209 [35390.233126] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:54:00 192.168.122.209 [35390.273302] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:54:00 192.168.122.209 [35390.274204] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:54:00 192.168.122.209 [35390.317310] [tempesta fw] Tempesta FW is ready Apr 26 01:54:00 192.168.122.209 [35391.068519] [tdb] Close table 'client0.tdb' Apr 26 01:54:01 192.168.122.209 [35391.277128] [tdb] Close table 'sessions0.tdb' Apr 26 01:54:04 192.168.122.209 [35394.494327] [tdb] Close table 'cache0.tdb' Apr 26 01:54:04 192.168.122.209 [35394.746918] [tdb] Close table 'filter0.tdb' Apr 26 01:54:04 192.168.122.209 [35394.747363] [tempesta fw] modules are stopped Apr 26 01:54:04 192.168.122.209 [35394.941618] [tempesta fw] exiting... Apr 26 01:54:04 192.168.122.209 [35395.107772] [tdb] Shutdown Tempesta DB Apr 26 01:54:05 192.168.122.209 [35395.347413] End test: cache.test_cache.TestCacheHttp.test_sharding_cache_bypass_prefix Apr 26 01:54:05 192.168.122.209 [35395.365510] Start test: cache.test_cache.TestCacheHttp.test_sharding_cache_bypass_suffix Apr 26 01:54:06 192.168.122.209 [35396.571770] [tdb] Start Tempesta DB Apr 26 01:54:06 192.168.122.209 [35396.736631] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:54:07 192.168.122.209 [35398.146725] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35398.146725] Maybe that's fine, but it's worth checking the [35398.146725] config - if there is no relations between the [35398.146725] names, then host name confusion attack is possible. Apr 26 01:54:08 192.168.122.209 [35398.305728] [tempesta fw] Configuration processing is completed. Apr 26 01:54:08 192.168.122.209 [35398.366081] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:54:08 192.168.122.209 [35398.796936] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:54:08 192.168.122.209 [35398.823738] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:54:08 192.168.122.209 [35398.850249] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:54:08 192.168.122.209 [35398.893435] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:54:08 192.168.122.209 [35398.894519] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:54:08 192.168.122.209 [35398.937430] [tempesta fw] Tempesta FW is ready Apr 26 01:54:09 192.168.122.209 [35399.662959] [tdb] Close table 'client0.tdb' Apr 26 01:54:09 192.168.122.209 [35399.868060] [tdb] Close table 'sessions0.tdb' Apr 26 01:54:12 192.168.122.209 [35403.121501] [tdb] Close table 'cache0.tdb' Apr 26 01:54:13 192.168.122.209 [35403.393692] [tdb] Close table 'filter0.tdb' Apr 26 01:54:13 192.168.122.209 [35403.394139] [tempesta fw] modules are stopped Apr 26 01:54:13 192.168.122.209 [35403.631735] [tempesta fw] exiting... Apr 26 01:54:13 192.168.122.209 [35403.774468] [tdb] Shutdown Tempesta DB Apr 26 01:54:13 192.168.122.209 [35403.992562] End test: cache.test_cache.TestCacheHttp.test_sharding_cache_bypass_suffix Apr 26 01:54:13 192.168.122.209 [35404.010276] Start test: cache.test_cache.TestCacheHttp.test_sharding_cache_fulfill_all Apr 26 01:54:14 192.168.122.209 [35405.185982] [tdb] Start Tempesta DB Apr 26 01:54:15 192.168.122.209 [35405.328111] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:54:16 192.168.122.209 [35406.779074] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35406.779074] Maybe that's fine, but it's worth checking the [35406.779074] config - if there is no relations between the [35406.779074] names, then host name confusion attack is possible. Apr 26 01:54:16 192.168.122.209 [35406.885642] [tempesta fw] Configuration processing is completed. Apr 26 01:54:16 192.168.122.209 [35406.944774] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:54:17 192.168.122.209 [35407.412117] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:54:17 192.168.122.209 [35407.440174] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:54:17 192.168.122.209 [35407.469167] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:54:17 192.168.122.209 [35407.521578] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:54:17 192.168.122.209 [35407.523062] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:54:17 192.168.122.209 [35407.561534] [tempesta fw] Tempesta FW is ready Apr 26 01:54:18 192.168.122.209 [35408.306480] [tdb] Close table 'client0.tdb' Apr 26 01:54:18 192.168.122.209 [35408.520571] [tdb] Close table 'sessions0.tdb' Apr 26 01:54:21 192.168.122.209 [35411.692874] [tdb] Close table 'cache0.tdb' Apr 26 01:54:21 192.168.122.209 [35411.925702] [tdb] Close table 'filter0.tdb' Apr 26 01:54:21 192.168.122.209 [35411.926148] [tempesta fw] modules are stopped Apr 26 01:54:21 192.168.122.209 [35412.145510] [tempesta fw] exiting... Apr 26 01:54:22 192.168.122.209 [35412.330115] [tdb] Shutdown Tempesta DB Apr 26 01:54:22 192.168.122.209 [35412.541589] End test: cache.test_cache.TestCacheHttp.test_sharding_cache_fulfill_all Apr 26 01:54:22 192.168.122.209 [35412.552349] Start test: cache.test_cache.TestCacheHttp.test_sharding_cache_fulfill_prefix Apr 26 01:54:23 192.168.122.209 [35413.774217] [tdb] Start Tempesta DB Apr 26 01:54:23 192.168.122.209 [35413.933698] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:54:25 192.168.122.209 [35415.402496] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35415.402496] Maybe that's fine, but it's worth checking the [35415.402496] config - if there is no relations between the [35415.402496] names, then host name confusion attack is possible. Apr 26 01:54:25 192.168.122.209 [35415.597721] [tempesta fw] Configuration processing is completed. Apr 26 01:54:25 192.168.122.209 [35415.650134] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:54:25 192.168.122.209 [35416.071378] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:54:25 192.168.122.209 [35416.097268] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:54:25 192.168.122.209 [35416.122951] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:54:25 192.168.122.209 [35416.173705] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:54:25 192.168.122.209 [35416.175461] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:54:25 192.168.122.209 [35416.217652] [tempesta fw] Tempesta FW is ready Apr 26 01:54:26 192.168.122.209 [35416.905677] [tdb] Close table 'client0.tdb' Apr 26 01:54:26 192.168.122.209 [35417.117772] [tdb] Close table 'sessions0.tdb' Apr 26 01:54:30 192.168.122.209 [35420.310632] [tdb] Close table 'cache0.tdb' Apr 26 01:54:30 192.168.122.209 [35420.529883] [tdb] Close table 'filter0.tdb' Apr 26 01:54:30 192.168.122.209 [35420.530319] [tempesta fw] modules are stopped Apr 26 01:54:30 192.168.122.209 [35420.752852] [tempesta fw] exiting... Apr 26 01:54:30 192.168.122.209 [35420.896182] [tdb] Shutdown Tempesta DB Apr 26 01:54:30 192.168.122.209 [35421.126122] End test: cache.test_cache.TestCacheHttp.test_sharding_cache_fulfill_prefix Apr 26 01:54:30 192.168.122.209 [35421.150132] Start test: cache.test_cache.TestCacheHttp.test_sharding_cache_fulfill_suffix Apr 26 01:54:32 192.168.122.209 [35422.338133] [tdb] Start Tempesta DB Apr 26 01:54:32 192.168.122.209 [35422.490680] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:54:33 192.168.122.209 [35423.935042] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35423.935042] Maybe that's fine, but it's worth checking the [35423.935042] config - if there is no relations between the [35423.935042] names, then host name confusion attack is possible. Apr 26 01:54:33 192.168.122.209 [35424.097813] [tempesta fw] Configuration processing is completed. Apr 26 01:54:33 192.168.122.209 [35424.148622] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:54:34 192.168.122.209 [35424.577514] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:54:34 192.168.122.209 [35424.611264] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:54:34 192.168.122.209 [35424.662226] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:54:34 192.168.122.209 [35424.709680] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:54:34 192.168.122.209 [35424.710581] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:54:34 192.168.122.209 [35424.757747] [tempesta fw] Tempesta FW is ready Apr 26 01:54:35 192.168.122.209 [35425.516529] [tdb] Close table 'client0.tdb' Apr 26 01:54:35 192.168.122.209 [35425.707774] [tdb] Close table 'sessions0.tdb' Apr 26 01:54:38 192.168.122.209 [35428.923618] [tdb] Close table 'cache0.tdb' Apr 26 01:54:38 192.168.122.209 [35429.182762] [tdb] Close table 'filter0.tdb' Apr 26 01:54:38 192.168.122.209 [35429.183211] [tempesta fw] modules are stopped Apr 26 01:54:39 192.168.122.209 [35429.374271] [tempesta fw] exiting... Apr 26 01:54:39 192.168.122.209 [35429.566132] [tdb] Shutdown Tempesta DB Apr 26 01:54:39 192.168.122.209 [35429.788248] End test: cache.test_cache.TestCacheHttp.test_sharding_cache_fulfill_suffix Apr 26 01:54:39 192.168.122.209 [35429.809987] Start test: cache.test_cache.TestCacheHttp.test_sharding_cache_fulfill_suffix2 Apr 26 01:54:40 192.168.122.209 [35431.007144] [tdb] Start Tempesta DB Apr 26 01:54:40 192.168.122.209 [35431.159360] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:54:42 192.168.122.209 [35432.642913] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35432.642913] Maybe that's fine, but it's worth checking the [35432.642913] config - if there is no relations between the [35432.642913] names, then host name confusion attack is possible. Apr 26 01:54:42 192.168.122.209 [35432.821926] [tempesta fw] Configuration processing is completed. Apr 26 01:54:42 192.168.122.209 [35432.873150] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:54:43 192.168.122.209 [35433.295469] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:54:43 192.168.122.209 [35433.321605] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:54:43 192.168.122.209 [35433.349593] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:54:43 192.168.122.209 [35433.397866] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:54:43 192.168.122.209 [35433.399307] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:54:43 192.168.122.209 [35433.449863] [tempesta fw] Tempesta FW is ready Apr 26 01:54:43 192.168.122.209 [35434.216662] [tdb] Close table 'client0.tdb' Apr 26 01:54:44 192.168.122.209 [35434.407487] [tdb] Close table 'sessions0.tdb' Apr 26 01:54:47 192.168.122.209 [35437.568477] [tdb] Close table 'cache0.tdb' Apr 26 01:54:47 192.168.122.209 [35437.815707] [tdb] Close table 'filter0.tdb' Apr 26 01:54:47 192.168.122.209 [35437.816139] [tempesta fw] modules are stopped Apr 26 01:54:47 192.168.122.209 [35438.009071] [tempesta fw] exiting... Apr 26 01:54:47 192.168.122.209 [35438.173926] [tdb] Shutdown Tempesta DB Apr 26 01:54:48 192.168.122.209 [35438.427212] End test: cache.test_cache.TestCacheHttp.test_sharding_cache_fulfill_suffix2 Apr 26 01:54:48 192.168.122.209 [35438.439767] Start test: cache.test_cache.TestCacheLocationH2.test_prefix_bypassed Apr 26 01:54:49 192.168.122.209 [35439.608553] [tdb] Start Tempesta DB Apr 26 01:54:49 192.168.122.209 [35439.758633] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:54:51 192.168.122.209 [35441.687500] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35441.687500] Maybe that's fine, but it's worth checking the [35441.687500] config - if there is no relations between the [35441.687500] names, then host name confusion attack is possible. Apr 26 01:54:51 192.168.122.209 [35441.798002] [tempesta fw] Configuration processing is completed. Apr 26 01:54:51 192.168.122.209 [35441.879720] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:54:52 192.168.122.209 [35442.301472] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:54:52 192.168.122.209 [35442.327696] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:54:52 192.168.122.209 [35442.356208] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:54:52 192.168.122.209 [35442.406038] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:54:52 192.168.122.209 [35442.407713] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:54:52 192.168.122.209 [35442.445980] [tempesta fw] Tempesta FW is ready Apr 26 01:54:52 192.168.122.209 [35443.032356] [tdb] Close table 'client0.tdb' Apr 26 01:54:52 192.168.122.209 [35443.228000] [tdb] Close table 'sessions0.tdb' Apr 26 01:54:56 192.168.122.209 [35446.433242] [tdb] Close table 'cache0.tdb' Apr 26 01:54:56 192.168.122.209 [35446.668337] [tdb] Close table 'filter0.tdb' Apr 26 01:54:56 192.168.122.209 [35446.668770] [tempesta fw] modules are stopped Apr 26 01:54:56 192.168.122.209 [35446.952929] [tempesta fw] exiting... Apr 26 01:54:56 192.168.122.209 [35447.090731] [tdb] Shutdown Tempesta DB Apr 26 01:54:57 192.168.122.209 [35447.317623] End test: cache.test_cache.TestCacheLocationH2.test_prefix_bypassed Apr 26 01:54:57 192.168.122.209 [35447.353469] Start test: cache.test_cache.TestCacheLocationH2.test_suffix_cached Apr 26 01:54:58 192.168.122.209 [35448.562253] [tdb] Start Tempesta DB Apr 26 01:54:58 192.168.122.209 [35448.729588] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:55:00 192.168.122.209 [35450.555348] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35450.555348] Maybe that's fine, but it's worth checking the [35450.555348] config - if there is no relations between the [35450.555348] names, then host name confusion attack is possible. Apr 26 01:55:00 192.168.122.209 [35450.658505] [tempesta fw] Configuration processing is completed. Apr 26 01:55:00 192.168.122.209 [35450.709344] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:55:00 192.168.122.209 [35451.122932] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:55:00 192.168.122.209 [35451.148543] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:55:00 192.168.122.209 [35451.174748] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:55:00 192.168.122.209 [35451.222117] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:55:00 192.168.122.209 [35451.223513] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:55:01 192.168.122.209 [35451.274189] [tempesta fw] Tempesta FW is ready Apr 26 01:55:01 192.168.122.209 [35451.893552] [tdb] Close table 'client0.tdb' Apr 26 01:55:01 192.168.122.209 [35452.092555] [tdb] Close table 'sessions0.tdb' Apr 26 01:55:05 192.168.122.209 [35455.300407] [tdb] Close table 'cache0.tdb' Apr 26 01:55:05 192.168.122.209 [35455.524893] [tdb] Close table 'filter0.tdb' Apr 26 01:55:05 192.168.122.209 [35455.525330] [tempesta fw] modules are stopped Apr 26 01:55:05 192.168.122.209 [35455.739539] [tempesta fw] exiting... Apr 26 01:55:05 192.168.122.209 [35455.893972] [tdb] Shutdown Tempesta DB Apr 26 01:55:05 192.168.122.209 [35456.138429] End test: cache.test_cache.TestCacheLocationH2.test_suffix_cached Apr 26 01:55:05 192.168.122.209 [35456.153653] Start test: cache.test_cache.TestCacheLocationH2.test_suffix_cached_and_prefix_bypassed Apr 26 01:55:07 192.168.122.209 [35457.309805] [tdb] Start Tempesta DB Apr 26 01:55:07 192.168.122.209 [35457.480511] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:55:09 192.168.122.209 [35459.447506] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35459.447506] Maybe that's fine, but it's worth checking the [35459.447506] config - if there is no relations between the [35459.447506] names, then host name confusion attack is possible. Apr 26 01:55:09 192.168.122.209 [35459.546233] [tempesta fw] Configuration processing is completed. Apr 26 01:55:09 192.168.122.209 [35459.597316] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:55:09 192.168.122.209 [35460.008949] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:55:09 192.168.122.209 [35460.034763] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:55:09 192.168.122.209 [35460.060822] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:55:09 192.168.122.209 [35460.102195] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:55:09 192.168.122.209 [35460.103258] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:55:09 192.168.122.209 [35460.142219] [tempesta fw] Tempesta FW is ready Apr 26 01:55:10 192.168.122.209 [35460.732540] [tdb] Close table 'client0.tdb' Apr 26 01:55:10 192.168.122.209 [35460.923534] [tdb] Close table 'sessions0.tdb' Apr 26 01:55:13 192.168.122.209 [35464.115013] [tdb] Close table 'cache0.tdb' Apr 26 01:55:14 192.168.122.209 [35464.353330] [tdb] Close table 'filter0.tdb' Apr 26 01:55:14 192.168.122.209 [35464.353765] [tempesta fw] modules are stopped Apr 26 01:55:14 192.168.122.209 [35464.530023] [tempesta fw] exiting... Apr 26 01:55:14 192.168.122.209 [35464.669294] [tdb] Shutdown Tempesta DB Apr 26 01:55:14 192.168.122.209 [35464.894667] End test: cache.test_cache.TestCacheLocationH2.test_suffix_cached_and_prefix_bypassed Apr 26 01:55:14 192.168.122.209 [35464.933360] Start test: cache.test_cache.TestCacheLocationHttp.test_prefix_bypassed Apr 26 01:55:15 192.168.122.209 [35466.137433] [tdb] Start Tempesta DB Apr 26 01:55:16 192.168.122.209 [35466.284784] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:55:18 192.168.122.209 [35468.263673] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35468.263673] Maybe that's fine, but it's worth checking the [35468.263673] config - if there is no relations between the [35468.263673] names, then host name confusion attack is possible. Apr 26 01:55:18 192.168.122.209 [35468.378334] [tempesta fw] Configuration processing is completed. Apr 26 01:55:18 192.168.122.209 [35468.438154] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:55:18 192.168.122.209 [35468.856672] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:55:18 192.168.122.209 [35468.882408] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:55:18 192.168.122.209 [35468.908153] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:55:18 192.168.122.209 [35468.958372] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:55:18 192.168.122.209 [35468.959978] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:55:18 192.168.122.209 [35469.010330] [tempesta fw] Tempesta FW is ready Apr 26 01:55:19 192.168.122.209 [35469.642068] [tdb] Close table 'client0.tdb' Apr 26 01:55:19 192.168.122.209 [35469.831225] [tdb] Close table 'sessions0.tdb' Apr 26 01:55:22 192.168.122.209 [35472.987197] [tdb] Close table 'cache0.tdb' Apr 26 01:55:22 192.168.122.209 [35473.208883] [tdb] Close table 'filter0.tdb' Apr 26 01:55:22 192.168.122.209 [35473.209326] [tempesta fw] modules are stopped Apr 26 01:55:23 192.168.122.209 [35473.417805] [tempesta fw] exiting... Apr 26 01:55:23 192.168.122.209 [35473.577674] [tdb] Shutdown Tempesta DB Apr 26 01:55:23 192.168.122.209 [35473.792931] End test: cache.test_cache.TestCacheLocationHttp.test_prefix_bypassed Apr 26 01:55:23 192.168.122.209 [35473.815422] Start test: cache.test_cache.TestCacheLocationHttp.test_suffix_cached Apr 26 01:55:24 192.168.122.209 [35475.051811] [tdb] Start Tempesta DB Apr 26 01:55:24 192.168.122.209 [35475.202306] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:55:26 192.168.122.209 [35477.135743] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35477.135743] Maybe that's fine, but it's worth checking the [35477.135743] config - if there is no relations between the [35477.135743] names, then host name confusion attack is possible. Apr 26 01:55:26 192.168.122.209 [35477.234489] [tempesta fw] Configuration processing is completed. Apr 26 01:55:27 192.168.122.209 [35477.329219] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:55:27 192.168.122.209 [35477.756021] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:55:27 192.168.122.209 [35477.782389] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:55:27 192.168.122.209 [35477.809053] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:55:27 192.168.122.209 [35477.854508] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:55:27 192.168.122.209 [35477.856246] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:55:27 192.168.122.209 [35477.902438] [tempesta fw] Tempesta FW is ready Apr 26 01:55:28 192.168.122.209 [35478.526857] [tdb] Close table 'client0.tdb' Apr 26 01:55:28 192.168.122.209 [35478.715551] [tdb] Close table 'sessions0.tdb' Apr 26 01:55:31 192.168.122.209 [35481.901612] [tdb] Close table 'cache0.tdb' Apr 26 01:55:31 192.168.122.209 [35482.137761] [tdb] Close table 'filter0.tdb' Apr 26 01:55:31 192.168.122.209 [35482.138221] [tempesta fw] modules are stopped Apr 26 01:55:32 192.168.122.209 [35482.463432] [tempesta fw] exiting... Apr 26 01:55:32 192.168.122.209 [35482.592991] [tdb] Shutdown Tempesta DB Apr 26 01:55:32 192.168.122.209 [35482.803705] End test: cache.test_cache.TestCacheLocationHttp.test_suffix_cached Apr 26 01:55:32 192.168.122.209 [35482.818937] Start test: cache.test_cache.TestCacheLocationHttp.test_suffix_cached_and_prefix_bypassed Apr 26 01:55:33 192.168.122.209 [35483.996216] [tdb] Start Tempesta DB Apr 26 01:55:33 192.168.122.209 [35484.141530] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:55:35 192.168.122.209 [35486.111890] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35486.111890] Maybe that's fine, but it's worth checking the [35486.111890] config - if there is no relations between the [35486.111890] names, then host name confusion attack is possible. Apr 26 01:55:35 192.168.122.209 [35486.198903] [tempesta fw] Configuration processing is completed. Apr 26 01:55:35 192.168.122.209 [35486.249693] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:55:36 192.168.122.209 [35486.662885] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:55:36 192.168.122.209 [35486.688320] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:55:36 192.168.122.209 [35486.713641] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:55:36 192.168.122.209 [35486.766616] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:55:36 192.168.122.209 [35486.768337] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:55:36 192.168.122.209 [35486.810574] [tempesta fw] Tempesta FW is ready Apr 26 01:55:37 192.168.122.209 [35487.483808] [tdb] Close table 'client0.tdb' Apr 26 01:55:37 192.168.122.209 [35487.674277] [tdb] Close table 'sessions0.tdb' Apr 26 01:55:40 192.168.122.209 [35490.830404] [tdb] Close table 'cache0.tdb' Apr 26 01:55:40 192.168.122.209 [35491.074887] [tdb] Close table 'filter0.tdb' Apr 26 01:55:40 192.168.122.209 [35491.075330] [tempesta fw] modules are stopped Apr 26 01:55:41 192.168.122.209 [35491.299616] [tempesta fw] exiting... Apr 26 01:55:41 192.168.122.209 [35491.447192] [tdb] Shutdown Tempesta DB Apr 26 01:55:41 192.168.122.209 [35491.679979] End test: cache.test_cache.TestCacheLocationHttp.test_suffix_cached_and_prefix_bypassed Apr 26 01:55:41 192.168.122.209 [35491.701837] Start test: cache.test_cache.TestCacheMultipleMethodsH2.test_GET_after_GET Apr 26 01:55:42 192.168.122.209 [35492.866215] [tdb] Start Tempesta DB Apr 26 01:55:42 192.168.122.209 [35493.031036] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:55:44 192.168.122.209 [35494.559995] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35494.559995] Maybe that's fine, but it's worth checking the [35494.559995] config - if there is no relations between the [35494.559995] names, then host name confusion attack is possible. Apr 26 01:55:44 192.168.122.209 [35494.630668] [tempesta fw] Configuration processing is completed. Apr 26 01:55:44 192.168.122.209 [35494.688705] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:55:44 192.168.122.209 [35495.118831] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:55:44 192.168.122.209 [35495.145100] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:55:44 192.168.122.209 [35495.171229] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:55:44 192.168.122.209 [35495.214713] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:55:44 192.168.122.209 [35495.216445] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:55:45 192.168.122.209 [35495.254673] [tempesta fw] Tempesta FW is ready Apr 26 01:55:45 192.168.122.209 [35495.885043] [tdb] Close table 'client0.tdb' Apr 26 01:55:45 192.168.122.209 [35496.070320] [tdb] Close table 'sessions0.tdb' Apr 26 01:55:48 192.168.122.209 [35499.236708] [tdb] Close table 'cache0.tdb' Apr 26 01:55:49 192.168.122.209 [35499.484240] [tdb] Close table 'filter0.tdb' Apr 26 01:55:49 192.168.122.209 [35499.484655] [tempesta fw] modules are stopped Apr 26 01:55:49 192.168.122.209 [35499.668612] [tempesta fw] exiting... Apr 26 01:55:49 192.168.122.209 [35499.821647] [tdb] Shutdown Tempesta DB Apr 26 01:55:49 192.168.122.209 [35500.047285] End test: cache.test_cache.TestCacheMultipleMethodsH2.test_GET_after_GET Apr 26 01:55:49 192.168.122.209 [35500.064815] Start test: cache.test_cache.TestCacheMultipleMethodsH2.test_GET_after_HEAD Apr 26 01:55:51 192.168.122.209 [35501.325081] [tdb] Start Tempesta DB Apr 26 01:55:51 192.168.122.209 [35501.489485] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:55:52 192.168.122.209 [35503.060002] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35503.060002] Maybe that's fine, but it's worth checking the [35503.060002] config - if there is no relations between the [35503.060002] names, then host name confusion attack is possible. Apr 26 01:55:52 192.168.122.209 [35503.143231] [tempesta fw] Configuration processing is completed. Apr 26 01:55:52 192.168.122.209 [35503.234030] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:55:53 192.168.122.209 [35503.668724] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:55:53 192.168.122.209 [35503.695529] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:55:53 192.168.122.209 [35503.722428] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:55:53 192.168.122.209 [35503.766837] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:55:53 192.168.122.209 [35503.768583] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:55:53 192.168.122.209 [35503.810768] [tempesta fw] Tempesta FW is ready Apr 26 01:55:54 192.168.122.209 [35504.427700] [tdb] Close table 'client0.tdb' Apr 26 01:55:54 192.168.122.209 [35504.619899] [tdb] Close table 'sessions0.tdb' Apr 26 01:55:57 192.168.122.209 [35507.760649] [tdb] Close table 'cache0.tdb' Apr 26 01:55:57 192.168.122.209 [35508.011073] [tdb] Close table 'filter0.tdb' Apr 26 01:55:57 192.168.122.209 [35508.011504] [tempesta fw] modules are stopped Apr 26 01:55:57 192.168.122.209 [35508.251841] [tempesta fw] exiting... Apr 26 01:55:58 192.168.122.209 [35508.431134] [tdb] Shutdown Tempesta DB Apr 26 01:55:58 192.168.122.209 [35508.623371] End test: cache.test_cache.TestCacheMultipleMethodsH2.test_GET_after_HEAD Apr 26 01:55:58 192.168.122.209 [35508.649654] Start test: cache.test_cache.TestCacheMultipleMethodsH2.test_HEAD_after_GET Apr 26 01:55:59 192.168.122.209 [35509.705555] [tdb] Start Tempesta DB Apr 26 01:55:59 192.168.122.209 [35509.856807] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:56:01 192.168.122.209 [35511.372158] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35511.372158] Maybe that's fine, but it's worth checking the [35511.372158] config - if there is no relations between the [35511.372158] names, then host name confusion attack is possible. Apr 26 01:56:01 192.168.122.209 [35511.438917] [tempesta fw] Configuration processing is completed. Apr 26 01:56:01 192.168.122.209 [35511.492204] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:56:01 192.168.122.209 [35511.921470] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:56:01 192.168.122.209 [35511.947963] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:56:01 192.168.122.209 [35511.974047] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:56:01 192.168.122.209 [35512.022898] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:56:01 192.168.122.209 [35512.024291] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:56:01 192.168.122.209 [35512.082869] [tempesta fw] Tempesta FW is ready Apr 26 01:56:02 192.168.122.209 [35512.695127] [tdb] Close table 'client0.tdb' Apr 26 01:56:02 192.168.122.209 [35512.896979] [tdb] Close table 'sessions0.tdb' Apr 26 01:56:05 192.168.122.209 [35516.058068] [tdb] Close table 'cache0.tdb' Apr 26 01:56:06 192.168.122.209 [35516.290907] [tdb] Close table 'filter0.tdb' Apr 26 01:56:06 192.168.122.209 [35516.291342] [tempesta fw] modules are stopped Apr 26 01:56:06 192.168.122.209 [35516.514882] [tempesta fw] exiting... Apr 26 01:56:06 192.168.122.209 [35516.676120] [tdb] Shutdown Tempesta DB Apr 26 01:56:06 192.168.122.209 [35516.894144] End test: cache.test_cache.TestCacheMultipleMethodsH2.test_HEAD_after_GET Apr 26 01:56:06 192.168.122.209 [35516.909360] Start test: cache.test_cache.TestCacheMultipleMethodsH2.test_HEAD_after_HEAD Apr 26 01:56:07 192.168.122.209 [35518.009313] [tdb] Start Tempesta DB Apr 26 01:56:07 192.168.122.209 [35518.159359] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:56:09 192.168.122.209 [35519.736262] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35519.736262] Maybe that's fine, but it's worth checking the [35519.736262] config - if there is no relations between the [35519.736262] names, then host name confusion attack is possible. Apr 26 01:56:09 192.168.122.209 [35519.811021] [tempesta fw] Configuration processing is completed. Apr 26 01:56:09 192.168.122.209 [35519.863306] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:56:10 192.168.122.209 [35520.295758] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:56:10 192.168.122.209 [35520.321957] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:56:10 192.168.122.209 [35520.348229] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:56:10 192.168.122.209 [35520.403048] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:56:10 192.168.122.209 [35520.404778] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:56:10 192.168.122.209 [35520.458981] [tempesta fw] Tempesta FW is ready Apr 26 01:56:10 192.168.122.209 [35521.027255] [tdb] Close table 'client0.tdb' Apr 26 01:56:11 192.168.122.209 [35521.255035] [tdb] Close table 'sessions0.tdb' Apr 26 01:56:14 192.168.122.209 [35524.492942] [tdb] Close table 'cache0.tdb' Apr 26 01:56:14 192.168.122.209 [35524.767419] [tdb] Close table 'filter0.tdb' Apr 26 01:56:14 192.168.122.209 [35524.767862] [tempesta fw] modules are stopped Apr 26 01:56:14 192.168.122.209 [35524.965115] [tempesta fw] exiting... Apr 26 01:56:14 192.168.122.209 [35525.152794] [tdb] Shutdown Tempesta DB Apr 26 01:56:15 192.168.122.209 [35525.414658] End test: cache.test_cache.TestCacheMultipleMethodsH2.test_HEAD_after_HEAD Apr 26 01:56:15 192.168.122.209 [35525.430622] Start test: cache.test_cache.TestCacheMultipleMethodsH2.test_POST_after_GET Apr 26 01:56:16 192.168.122.209 [35526.702713] [tdb] Start Tempesta DB Apr 26 01:56:16 192.168.122.209 [35526.853982] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:56:18 192.168.122.209 [35528.392508] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35528.392508] Maybe that's fine, but it's worth checking the [35528.392508] config - if there is no relations between the [35528.392508] names, then host name confusion attack is possible. Apr 26 01:56:18 192.168.122.209 [35528.459158] [tempesta fw] Configuration processing is completed. Apr 26 01:56:18 192.168.122.209 [35528.553469] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:56:18 192.168.122.209 [35528.991985] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:56:18 192.168.122.209 [35529.018907] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:56:18 192.168.122.209 [35529.046330] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:56:18 192.168.122.209 [35529.099166] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:56:18 192.168.122.209 [35529.100793] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:56:18 192.168.122.209 [35529.143095] [tempesta fw] Tempesta FW is ready Apr 26 01:56:19 192.168.122.209 [35529.785237] [tdb] Close table 'client0.tdb' Apr 26 01:56:19 192.168.122.209 [35529.974313] [tdb] Close table 'sessions0.tdb' Apr 26 01:56:22 192.168.122.209 [35533.158734] [tdb] Close table 'cache0.tdb' Apr 26 01:56:23 192.168.122.209 [35533.409853] [tdb] Close table 'filter0.tdb' Apr 26 01:56:23 192.168.122.209 [35533.410291] [tempesta fw] modules are stopped Apr 26 01:56:23 192.168.122.209 [35533.724884] [tempesta fw] exiting... Apr 26 01:56:23 192.168.122.209 [35533.845686] [tdb] Shutdown Tempesta DB Apr 26 01:56:23 192.168.122.209 [35534.053384] End test: cache.test_cache.TestCacheMultipleMethodsH2.test_POST_after_GET Apr 26 01:56:23 192.168.122.209 [35534.075896] Start test: cache.test_cache.TestCacheMultipleMethodsH2.test_POST_after_HEAD Apr 26 01:56:24 192.168.122.209 [35535.209909] [tdb] Start Tempesta DB Apr 26 01:56:25 192.168.122.209 [35535.360159] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:56:26 192.168.122.209 [35536.892490] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35536.892490] Maybe that's fine, but it's worth checking the [35536.892490] config - if there is no relations between the [35536.892490] names, then host name confusion attack is possible. Apr 26 01:56:26 192.168.122.209 [35536.963274] [tempesta fw] Configuration processing is completed. Apr 26 01:56:26 192.168.122.209 [35537.013560] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:56:27 192.168.122.209 [35537.440765] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:56:27 192.168.122.209 [35537.477412] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:56:27 192.168.122.209 [35537.503229] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:56:27 192.168.122.209 [35537.543201] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:56:27 192.168.122.209 [35537.544351] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:56:27 192.168.122.209 [35537.599215] [tempesta fw] Tempesta FW is ready Apr 26 01:56:27 192.168.122.209 [35538.204288] [tdb] Close table 'client0.tdb' Apr 26 01:56:28 192.168.122.209 [35538.412104] [tdb] Close table 'sessions0.tdb' Apr 26 01:56:31 192.168.122.209 [35541.682118] [tdb] Close table 'cache0.tdb' Apr 26 01:56:31 192.168.122.209 [35541.922973] [tdb] Close table 'filter0.tdb' Apr 26 01:56:31 192.168.122.209 [35541.923442] [tempesta fw] modules are stopped Apr 26 01:56:31 192.168.122.209 [35542.155847] [tempesta fw] exiting... Apr 26 01:56:32 192.168.122.209 [35542.326245] [tdb] Shutdown Tempesta DB Apr 26 01:56:32 192.168.122.209 [35542.545300] End test: cache.test_cache.TestCacheMultipleMethodsH2.test_POST_after_HEAD Apr 26 01:56:32 192.168.122.209 [35542.574191] Start test: cache.test_cache.TestCacheMultipleMethodsH2.test_cache_POST_request_not_cached_no_cache_control Apr 26 01:56:33 192.168.122.209 [35543.757684] [tdb] Start Tempesta DB Apr 26 01:56:33 192.168.122.209 [35543.891629] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:56:35 192.168.122.209 [35545.409234] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35545.409234] Maybe that's fine, but it's worth checking the [35545.409234] config - if there is no relations between the [35545.409234] names, then host name confusion attack is possible. Apr 26 01:56:35 192.168.122.209 [35545.499914] [tempesta fw] Configuration processing is completed. Apr 26 01:56:35 192.168.122.209 [35545.566781] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:56:35 192.168.122.209 [35545.978980] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:56:35 192.168.122.209 [35546.005790] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:56:35 192.168.122.209 [35546.043929] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:56:35 192.168.122.209 [35546.103378] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:56:35 192.168.122.209 [35546.105144] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:56:35 192.168.122.209 [35546.147325] [tempesta fw] Tempesta FW is ready Apr 26 01:56:36 192.168.122.209 [35546.776727] [tdb] Close table 'client0.tdb' Apr 26 01:56:36 192.168.122.209 [35547.054902] [tdb] Close table 'sessions0.tdb' Apr 26 01:56:39 192.168.122.209 [35550.221608] [tdb] Close table 'cache0.tdb' Apr 26 01:56:40 192.168.122.209 [35550.458391] [tdb] Close table 'filter0.tdb' Apr 26 01:56:40 192.168.122.209 [35550.458861] [tempesta fw] modules are stopped Apr 26 01:56:40 192.168.122.209 [35550.675399] [tempesta fw] exiting... Apr 26 01:56:40 192.168.122.209 [35550.847205] [tdb] Shutdown Tempesta DB Apr 26 01:56:40 192.168.122.209 [35551.090540] End test: cache.test_cache.TestCacheMultipleMethodsH2.test_cache_POST_request_not_cached_no_cache_control Apr 26 01:56:40 192.168.122.209 [35551.115829] Start test: cache.test_cache.TestCacheMultipleMethodsH2.test_cache_POST_request_not_cached_not_same_location Apr 26 01:56:42 192.168.122.209 [35552.294737] [tdb] Start Tempesta DB Apr 26 01:56:42 192.168.122.209 [35552.434599] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:56:43 192.168.122.209 [35553.948796] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35553.948796] Maybe that's fine, but it's worth checking the [35553.948796] config - if there is no relations between the [35553.948796] names, then host name confusion attack is possible. Apr 26 01:56:43 192.168.122.209 [35554.023502] [tempesta fw] Configuration processing is completed. Apr 26 01:56:43 192.168.122.209 [35554.111739] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:56:44 192.168.122.209 [35554.539817] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:56:44 192.168.122.209 [35554.566658] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:56:44 192.168.122.209 [35554.593823] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:56:44 192.168.122.209 [35554.639494] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:56:44 192.168.122.209 [35554.641204] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:56:44 192.168.122.209 [35554.679435] [tempesta fw] Tempesta FW is ready Apr 26 01:56:45 192.168.122.209 [35555.298994] [tdb] Close table 'client0.tdb' Apr 26 01:56:45 192.168.122.209 [35555.488535] [tdb] Close table 'sessions0.tdb' Apr 26 01:56:48 192.168.122.209 [35558.673209] [tdb] Close table 'cache0.tdb' Apr 26 01:56:48 192.168.122.209 [35558.932896] [tdb] Close table 'filter0.tdb' Apr 26 01:56:48 192.168.122.209 [35558.933659] [tempesta fw] modules are stopped Apr 26 01:56:48 192.168.122.209 [35559.129060] [tempesta fw] exiting... Apr 26 01:56:49 192.168.122.209 [35559.307523] [tdb] Shutdown Tempesta DB Apr 26 01:56:49 192.168.122.209 [35559.524788] End test: cache.test_cache.TestCacheMultipleMethodsH2.test_cache_POST_request_not_cached_not_same_location Apr 26 01:56:49 192.168.122.209 [35559.546890] Start test: cache.test_cache.TestCacheMultipleMethodsH2.test_cache_POST_request_with_location_GET Apr 26 01:56:50 192.168.122.209 [35560.715916] [tdb] Start Tempesta DB Apr 26 01:56:50 192.168.122.209 [35560.869989] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:56:52 192.168.122.209 [35562.348837] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35562.348837] Maybe that's fine, but it's worth checking the [35562.348837] config - if there is no relations between the [35562.348837] names, then host name confusion attack is possible. Apr 26 01:56:52 192.168.122.209 [35562.423905] [tempesta fw] Configuration processing is completed. Apr 26 01:56:52 192.168.122.209 [35562.481518] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:56:52 192.168.122.209 [35562.897102] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:56:52 192.168.122.209 [35562.931470] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:56:52 192.168.122.209 [35562.956528] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:56:52 192.168.122.209 [35562.999581] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:56:52 192.168.122.209 [35563.001325] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:56:52 192.168.122.209 [35563.039528] [tempesta fw] Tempesta FW is ready Apr 26 01:56:53 192.168.122.209 [35563.673116] [tdb] Close table 'client0.tdb' Apr 26 01:56:53 192.168.122.209 [35563.869965] [tdb] Close table 'sessions0.tdb' Apr 26 01:56:56 192.168.122.209 [35566.998067] [tdb] Close table 'cache0.tdb' Apr 26 01:56:56 192.168.122.209 [35567.250654] [tdb] Close table 'filter0.tdb' Apr 26 01:56:56 192.168.122.209 [35567.251080] [tempesta fw] modules are stopped Apr 26 01:56:57 192.168.122.209 [35567.448370] [tempesta fw] exiting... Apr 26 01:56:57 192.168.122.209 [35567.614729] [tdb] Shutdown Tempesta DB Apr 26 01:56:57 192.168.122.209 [35567.857535] End test: cache.test_cache.TestCacheMultipleMethodsH2.test_cache_POST_request_with_location_GET Apr 26 01:56:57 192.168.122.209 [35567.880337] Start test: cache.test_cache.TestCacheMultipleMethodsH2.test_cache_POST_request_with_location_HEAD Apr 26 01:56:58 192.168.122.209 [35569.086051] [tdb] Start Tempesta DB Apr 26 01:56:58 192.168.122.209 [35569.228991] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:57:00 192.168.122.209 [35570.740956] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35570.740956] Maybe that's fine, but it's worth checking the [35570.740956] config - if there is no relations between the [35570.740956] names, then host name confusion attack is possible. Apr 26 01:57:00 192.168.122.209 [35570.811737] [tempesta fw] Configuration processing is completed. Apr 26 01:57:00 192.168.122.209 [35570.861708] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:57:01 192.168.122.209 [35571.285862] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:57:01 192.168.122.209 [35571.312079] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:57:01 192.168.122.209 [35571.338243] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:57:01 192.168.122.209 [35571.387662] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:57:01 192.168.122.209 [35571.389039] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:57:01 192.168.122.209 [35571.427643] [tempesta fw] Tempesta FW is ready Apr 26 01:57:01 192.168.122.209 [35572.071562] [tdb] Close table 'client0.tdb' Apr 26 01:57:01 192.168.122.209 [35572.252295] [tdb] Close table 'sessions0.tdb' Apr 26 01:57:05 192.168.122.209 [35575.427399] [tdb] Close table 'cache0.tdb' Apr 26 01:57:05 192.168.122.209 [35575.688525] [tdb] Close table 'filter0.tdb' Apr 26 01:57:05 192.168.122.209 [35575.688965] [tempesta fw] modules are stopped Apr 26 01:57:05 192.168.122.209 [35575.900212] [tempesta fw] exiting... Apr 26 01:57:05 192.168.122.209 [35576.081931] [tdb] Shutdown Tempesta DB Apr 26 01:57:06 192.168.122.209 [35576.328579] End test: cache.test_cache.TestCacheMultipleMethodsH2.test_cache_POST_request_with_location_HEAD Apr 26 01:57:06 192.168.122.209 [35576.345104] Start test: cache.test_cache.TestCacheMultipleMethodsH2.test_cache_POST_request_with_location_POST Apr 26 01:57:07 192.168.122.209 [35577.515266] [tdb] Start Tempesta DB Apr 26 01:57:07 192.168.122.209 [35577.664947] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:57:08 192.168.122.209 [35579.148513] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35579.148513] Maybe that's fine, but it's worth checking the [35579.148513] config - if there is no relations between the [35579.148513] names, then host name confusion attack is possible. Apr 26 01:57:08 192.168.122.209 [35579.211757] [tempesta fw] Configuration processing is completed. Apr 26 01:57:09 192.168.122.209 [35579.298669] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:57:09 192.168.122.209 [35579.728611] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:57:09 192.168.122.209 [35579.766458] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:57:09 192.168.122.209 [35579.793375] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:57:09 192.168.122.209 [35579.835803] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:57:09 192.168.122.209 [35579.837187] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:57:09 192.168.122.209 [35579.879748] [tempesta fw] Tempesta FW is ready Apr 26 01:57:10 192.168.122.209 [35580.500900] [tdb] Close table 'client0.tdb' Apr 26 01:57:10 192.168.122.209 [35580.711277] [tdb] Close table 'sessions0.tdb' Apr 26 01:57:13 192.168.122.209 [35583.869545] [tdb] Close table 'cache0.tdb' Apr 26 01:57:13 192.168.122.209 [35584.116398] [tdb] Close table 'filter0.tdb' Apr 26 01:57:13 192.168.122.209 [35584.117030] [tempesta fw] modules are stopped Apr 26 01:57:14 192.168.122.209 [35584.308577] [tempesta fw] exiting... Apr 26 01:57:14 192.168.122.209 [35584.427826] [tdb] Shutdown Tempesta DB Apr 26 01:57:14 192.168.122.209 [35584.653732] End test: cache.test_cache.TestCacheMultipleMethodsH2.test_cache_POST_request_with_location_POST Apr 26 01:57:14 192.168.122.209 [35584.663889] Start test: cache.test_cache.TestCacheMultipleMethodsH2.test_several_entries_GET_GET Apr 26 01:57:15 192.168.122.209 [35585.895130] [tdb] Start Tempesta DB Apr 26 01:57:15 192.168.122.209 [35586.060057] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:57:17 192.168.122.209 [35587.677138] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35587.677138] Maybe that's fine, but it's worth checking the [35587.677138] config - if there is no relations between the [35587.677138] names, then host name confusion attack is possible. Apr 26 01:57:17 192.168.122.209 [35587.747922] [tempesta fw] Configuration processing is completed. Apr 26 01:57:17 192.168.122.209 [35587.797763] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:57:17 192.168.122.209 [35588.229596] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:57:18 192.168.122.209 [35588.256433] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:57:18 192.168.122.209 [35588.282633] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:57:18 192.168.122.209 [35588.331837] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:57:18 192.168.122.209 [35588.332619] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:57:18 192.168.122.209 [35588.375862] [tempesta fw] Tempesta FW is ready Apr 26 01:57:20 192.168.122.209 [35591.035166] [tdb] Close table 'client0.tdb' Apr 26 01:57:20 192.168.122.209 [35591.225826] [tdb] Close table 'sessions0.tdb' Apr 26 01:57:24 192.168.122.209 [35594.387537] [tdb] Close table 'cache0.tdb' Apr 26 01:57:24 192.168.122.209 [35594.651002] [tdb] Close table 'filter0.tdb' Apr 26 01:57:24 192.168.122.209 [35594.651406] [tempesta fw] modules are stopped Apr 26 01:57:24 192.168.122.209 [35594.839648] [tempesta fw] exiting... Apr 26 01:57:24 192.168.122.209 [35594.993225] [tdb] Shutdown Tempesta DB Apr 26 01:57:24 192.168.122.209 [35595.222339] End test: cache.test_cache.TestCacheMultipleMethodsH2.test_several_entries_GET_GET Apr 26 01:57:24 192.168.122.209 [35595.240242] Start test: cache.test_cache.TestCacheMultipleMethodsH2.test_several_entries_GET_HEAD Apr 26 01:57:26 192.168.122.209 [35596.441341] [tdb] Start Tempesta DB Apr 26 01:57:26 192.168.122.209 [35596.589019] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:57:27 192.168.122.209 [35598.193321] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35598.193321] Maybe that's fine, but it's worth checking the [35598.193321] config - if there is no relations between the [35598.193321] names, then host name confusion attack is possible. Apr 26 01:57:28 192.168.122.209 [35598.276367] [tempesta fw] Configuration processing is completed. Apr 26 01:57:28 192.168.122.209 [35598.329956] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:57:28 192.168.122.209 [35598.766421] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:57:28 192.168.122.209 [35598.792605] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:57:28 192.168.122.209 [35598.819210] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:57:28 192.168.122.209 [35598.872089] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:57:28 192.168.122.209 [35598.873823] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:57:28 192.168.122.209 [35598.911998] [tempesta fw] Tempesta FW is ready Apr 26 01:57:31 192.168.122.209 [35601.504661] [tdb] Close table 'client0.tdb' Apr 26 01:57:31 192.168.122.209 [35601.724367] [tdb] Close table 'sessions0.tdb' Apr 26 01:57:34 192.168.122.209 [35604.941438] [tdb] Close table 'cache0.tdb' Apr 26 01:57:34 192.168.122.209 [35605.203569] [tdb] Close table 'filter0.tdb' Apr 26 01:57:34 192.168.122.209 [35605.204018] [tempesta fw] modules are stopped Apr 26 01:57:35 192.168.122.209 [35605.383787] [tempesta fw] exiting... Apr 26 01:57:35 192.168.122.209 [35605.553886] [tdb] Shutdown Tempesta DB Apr 26 01:57:35 192.168.122.209 [35605.805989] End test: cache.test_cache.TestCacheMultipleMethodsH2.test_several_entries_GET_HEAD Apr 26 01:57:35 192.168.122.209 [35605.828219] Start test: cache.test_cache.TestCacheMultipleMethodsH2.test_several_entries_GET_POST Apr 26 01:57:36 192.168.122.209 [35607.034599] [tdb] Start Tempesta DB Apr 26 01:57:36 192.168.122.209 [35607.188648] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:57:38 192.168.122.209 [35608.705439] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35608.705439] Maybe that's fine, but it's worth checking the [35608.705439] config - if there is no relations between the [35608.705439] names, then host name confusion attack is possible. Apr 26 01:57:38 192.168.122.209 [35608.813332] [tempesta fw] Configuration processing is completed. Apr 26 01:57:38 192.168.122.209 [35608.869986] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:57:39 192.168.122.209 [35609.288488] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:57:39 192.168.122.209 [35609.314518] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:57:39 192.168.122.209 [35609.341035] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:57:39 192.168.122.209 [35609.388193] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:57:39 192.168.122.209 [35609.389925] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:57:39 192.168.122.209 [35609.432160] [tempesta fw] Tempesta FW is ready Apr 26 01:57:39 192.168.122.209 [35610.101461] [tdb] Close table 'client0.tdb' Apr 26 01:57:40 192.168.122.209 [35610.299061] [tdb] Close table 'sessions0.tdb' Apr 26 01:57:43 192.168.122.209 [35613.485201] [tdb] Close table 'cache0.tdb' Apr 26 01:57:43 192.168.122.209 [35613.730284] [tdb] Close table 'filter0.tdb' Apr 26 01:57:43 192.168.122.209 [35613.730707] [tempesta fw] modules are stopped Apr 26 01:57:43 192.168.122.209 [35613.899905] [tempesta fw] exiting... Apr 26 01:57:43 192.168.122.209 [35614.033377] [tdb] Shutdown Tempesta DB Apr 26 01:57:44 192.168.122.209 [35614.272936] End test: cache.test_cache.TestCacheMultipleMethodsH2.test_several_entries_GET_POST Apr 26 01:57:44 192.168.122.209 [35614.300628] Start test: cache.test_cache.TestCacheMultipleMethodsH2.test_several_entries_POST_GET Apr 26 01:57:45 192.168.122.209 [35615.510278] [tdb] Start Tempesta DB Apr 26 01:57:45 192.168.122.209 [35615.659777] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:57:46 192.168.122.209 [35617.137621] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35617.137621] Maybe that's fine, but it's worth checking the [35617.137621] config - if there is no relations between the [35617.137621] names, then host name confusion attack is possible. Apr 26 01:57:46 192.168.122.209 [35617.212641] [tempesta fw] Configuration processing is completed. Apr 26 01:57:47 192.168.122.209 [35617.263424] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:57:47 192.168.122.209 [35617.682301] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:57:47 192.168.122.209 [35617.708256] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:57:47 192.168.122.209 [35617.733994] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:57:47 192.168.122.209 [35617.776306] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:57:47 192.168.122.209 [35617.778136] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:57:47 192.168.122.209 [35617.828311] [tempesta fw] Tempesta FW is ready Apr 26 01:57:50 192.168.122.209 [35620.450778] [tdb] Close table 'client0.tdb' Apr 26 01:57:50 192.168.122.209 [35620.641807] [tdb] Close table 'sessions0.tdb' Apr 26 01:57:53 192.168.122.209 [35623.819166] [tdb] Close table 'cache0.tdb' Apr 26 01:57:53 192.168.122.209 [35624.063782] [tdb] Close table 'filter0.tdb' Apr 26 01:57:53 192.168.122.209 [35624.064241] [tempesta fw] modules are stopped Apr 26 01:57:53 192.168.122.209 [35624.244393] [tempesta fw] exiting... Apr 26 01:57:54 192.168.122.209 [35624.395307] [tdb] Shutdown Tempesta DB Apr 26 01:57:54 192.168.122.209 [35624.656508] End test: cache.test_cache.TestCacheMultipleMethodsH2.test_several_entries_POST_GET Apr 26 01:57:54 192.168.122.209 [35624.673979] Start test: cache.test_cache.TestCacheMultipleMethodsH2.test_several_entries_POST_HEAD Apr 26 01:57:55 192.168.122.209 [35625.908849] [tdb] Start Tempesta DB Apr 26 01:57:55 192.168.122.209 [35626.058212] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:57:57 192.168.122.209 [35627.573682] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35627.573682] Maybe that's fine, but it's worth checking the [35627.573682] config - if there is no relations between the [35627.573682] names, then host name confusion attack is possible. Apr 26 01:57:57 192.168.122.209 [35627.644441] [tempesta fw] Configuration processing is completed. Apr 26 01:57:57 192.168.122.209 [35627.702965] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:57:57 192.168.122.209 [35628.125306] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:57:57 192.168.122.209 [35628.151650] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:57:57 192.168.122.209 [35628.177555] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:57:57 192.168.122.209 [35628.220403] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:57:57 192.168.122.209 [35628.221816] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:57:58 192.168.122.209 [35628.272372] [tempesta fw] Tempesta FW is ready Apr 26 01:58:00 192.168.122.209 [35630.891164] [tdb] Close table 'client0.tdb' Apr 26 01:58:00 192.168.122.209 [35631.071932] [tdb] Close table 'sessions0.tdb' Apr 26 01:58:04 192.168.122.209 [35634.290692] [tdb] Close table 'cache0.tdb' Apr 26 01:58:04 192.168.122.209 [35634.560993] [tdb] Close table 'filter0.tdb' Apr 26 01:58:04 192.168.122.209 [35634.561440] [tempesta fw] modules are stopped Apr 26 01:58:04 192.168.122.209 [35634.752047] [tempesta fw] exiting... Apr 26 01:58:04 192.168.122.209 [35634.897456] [tdb] Shutdown Tempesta DB Apr 26 01:58:04 192.168.122.209 [35635.103516] End test: cache.test_cache.TestCacheMultipleMethodsH2.test_several_entries_POST_HEAD Apr 26 01:58:04 192.168.122.209 [35635.125387] Start test: cache.test_cache.TestCacheMultipleMethodsH2.test_several_entries_POST_POST Apr 26 01:58:06 192.168.122.209 [35636.329657] [tdb] Start Tempesta DB Apr 26 01:58:06 192.168.122.209 [35636.469630] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:58:07 192.168.122.209 [35638.041852] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35638.041852] Maybe that's fine, but it's worth checking the [35638.041852] config - if there is no relations between the [35638.041852] names, then host name confusion attack is possible. Apr 26 01:58:07 192.168.122.209 [35638.116610] [tempesta fw] Configuration processing is completed. Apr 26 01:58:07 192.168.122.209 [35638.174592] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:58:08 192.168.122.209 [35638.591557] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:58:08 192.168.122.209 [35638.626489] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:58:08 192.168.122.209 [35638.652126] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:58:08 192.168.122.209 [35638.744561] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:58:08 192.168.122.209 [35638.746289] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:58:08 192.168.122.209 [35638.792511] [tempesta fw] Tempesta FW is ready Apr 26 01:58:09 192.168.122.209 [35639.433017] [tdb] Close table 'client0.tdb' Apr 26 01:58:09 192.168.122.209 [35639.643528] [tdb] Close table 'sessions0.tdb' Apr 26 01:58:12 192.168.122.209 [35642.824825] [tdb] Close table 'cache0.tdb' Apr 26 01:58:12 192.168.122.209 [35643.073654] [tdb] Close table 'filter0.tdb' Apr 26 01:58:12 192.168.122.209 [35643.074088] [tempesta fw] modules are stopped Apr 26 01:58:12 192.168.122.209 [35643.247214] [tempesta fw] exiting... Apr 26 01:58:13 192.168.122.209 [35643.392187] [tdb] Shutdown Tempesta DB Apr 26 01:58:13 192.168.122.209 [35643.618972] End test: cache.test_cache.TestCacheMultipleMethodsH2.test_several_entries_POST_POST Apr 26 01:58:13 192.168.122.209 [35643.635668] Start test: cache.test_cache.TestCacheMultipleMethodsH2.test_update_cache_via_DELETE_request Apr 26 01:58:14 192.168.122.209 [35644.859341] [tdb] Start Tempesta DB Apr 26 01:58:14 192.168.122.209 [35645.005566] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:58:16 192.168.122.209 [35646.545944] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35646.545944] Maybe that's fine, but it's worth checking the [35646.545944] config - if there is no relations between the [35646.545944] names, then host name confusion attack is possible. Apr 26 01:58:16 192.168.122.209 [35646.616696] [tempesta fw] Configuration processing is completed. Apr 26 01:58:16 192.168.122.209 [35646.678937] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:58:16 192.168.122.209 [35647.100297] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:58:16 192.168.122.209 [35647.126752] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:58:16 192.168.122.209 [35647.152712] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:58:16 192.168.122.209 [35647.196674] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:58:16 192.168.122.209 [35647.198402] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:58:16 192.168.122.209 [35647.236684] [tempesta fw] Tempesta FW is ready Apr 26 01:58:17 192.168.122.209 [35647.825711] [tdb] Close table 'client0.tdb' Apr 26 01:58:17 192.168.122.209 [35648.018375] [tdb] Close table 'sessions0.tdb' Apr 26 01:58:20 192.168.122.209 [35651.225193] [tdb] Close table 'cache0.tdb' Apr 26 01:58:21 192.168.122.209 [35651.474091] [tdb] Close table 'filter0.tdb' Apr 26 01:58:21 192.168.122.209 [35651.474520] [tempesta fw] modules are stopped Apr 26 01:58:21 192.168.122.209 [35651.688162] [tempesta fw] exiting... Apr 26 01:58:21 192.168.122.209 [35651.828167] [tdb] Shutdown Tempesta DB Apr 26 01:58:21 192.168.122.209 [35652.073587] End test: cache.test_cache.TestCacheMultipleMethodsH2.test_update_cache_via_DELETE_request Apr 26 01:58:21 192.168.122.209 [35652.098936] Start test: cache.test_cache.TestCacheMultipleMethodsH2.test_update_cache_via_PUT_request Apr 26 01:58:23 192.168.122.209 [35653.320940] [tdb] Start Tempesta DB Apr 26 01:58:23 192.168.122.209 [35653.474424] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:58:24 192.168.122.209 [35655.002008] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35655.002008] Maybe that's fine, but it's worth checking the [35655.002008] config - if there is no relations between the [35655.002008] names, then host name confusion attack is possible. Apr 26 01:58:24 192.168.122.209 [35655.068783] [tempesta fw] Configuration processing is completed. Apr 26 01:58:24 192.168.122.209 [35655.151285] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:58:25 192.168.122.209 [35655.586740] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:58:25 192.168.122.209 [35655.613517] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:58:25 192.168.122.209 [35655.640349] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:58:25 192.168.122.209 [35655.696792] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:58:25 192.168.122.209 [35655.698520] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:58:25 192.168.122.209 [35655.740748] [tempesta fw] Tempesta FW is ready Apr 26 01:58:26 192.168.122.209 [35656.449712] [tdb] Close table 'client0.tdb' Apr 26 01:58:26 192.168.122.209 [35656.646084] [tdb] Close table 'sessions0.tdb' Apr 26 01:58:29 192.168.122.209 [35659.782656] [tdb] Close table 'cache0.tdb' Apr 26 01:58:29 192.168.122.209 [35660.034222] [tdb] Close table 'filter0.tdb' Apr 26 01:58:29 192.168.122.209 [35660.034670] [tempesta fw] modules are stopped Apr 26 01:58:30 192.168.122.209 [35660.280804] [tempesta fw] exiting... Apr 26 01:58:30 192.168.122.209 [35660.435786] [tdb] Shutdown Tempesta DB Apr 26 01:58:30 192.168.122.209 [35660.678426] End test: cache.test_cache.TestCacheMultipleMethodsH2.test_update_cache_via_PUT_request Apr 26 01:58:30 192.168.122.209 [35660.689337] Start test: cache.test_cache.TestCacheMultipleMethodsHttp.test_GET_after_GET Apr 26 01:58:31 192.168.122.209 [35661.894232] [tdb] Start Tempesta DB Apr 26 01:58:31 192.168.122.209 [35662.047258] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:58:33 192.168.122.209 [35663.598157] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35663.598157] Maybe that's fine, but it's worth checking the [35663.598157] config - if there is no relations between the [35663.598157] names, then host name confusion attack is possible. Apr 26 01:58:33 192.168.122.209 [35663.668896] [tempesta fw] Configuration processing is completed. Apr 26 01:58:33 192.168.122.209 [35663.719360] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:58:33 192.168.122.209 [35664.140281] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:58:33 192.168.122.209 [35664.166538] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:58:33 192.168.122.209 [35664.192252] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:58:33 192.168.122.209 [35664.236909] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:58:33 192.168.122.209 [35664.238610] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:58:34 192.168.122.209 [35664.276853] [tempesta fw] Tempesta FW is ready Apr 26 01:58:34 192.168.122.209 [35664.934058] [tdb] Close table 'client0.tdb' Apr 26 01:58:34 192.168.122.209 [35665.125962] [tdb] Close table 'sessions0.tdb' Apr 26 01:58:38 192.168.122.209 [35668.298765] [tdb] Close table 'cache0.tdb' Apr 26 01:58:38 192.168.122.209 [35668.531734] [tdb] Close table 'filter0.tdb' Apr 26 01:58:38 192.168.122.209 [35668.532173] [tempesta fw] modules are stopped Apr 26 01:58:38 192.168.122.209 [35668.752533] [tempesta fw] exiting... Apr 26 01:58:38 192.168.122.209 [35668.893272] [tdb] Shutdown Tempesta DB Apr 26 01:58:38 192.168.122.209 [35669.109507] End test: cache.test_cache.TestCacheMultipleMethodsHttp.test_GET_after_GET Apr 26 01:58:38 192.168.122.209 [35669.119262] Start test: cache.test_cache.TestCacheMultipleMethodsHttp.test_GET_after_HEAD Apr 26 01:58:40 192.168.122.209 [35670.292232] [tdb] Start Tempesta DB Apr 26 01:58:40 192.168.122.209 [35670.438692] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:58:41 192.168.122.209 [35671.942274] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35671.942274] Maybe that's fine, but it's worth checking the [35671.942274] config - if there is no relations between the [35671.942274] names, then host name confusion attack is possible. Apr 26 01:58:41 192.168.122.209 [35672.008984] [tempesta fw] Configuration processing is completed. Apr 26 01:58:41 192.168.122.209 [35672.060106] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:58:42 192.168.122.209 [35672.480289] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:58:42 192.168.122.209 [35672.506400] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:58:42 192.168.122.209 [35672.532056] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:58:42 192.168.122.209 [35672.572998] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:58:42 192.168.122.209 [35672.574726] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:58:42 192.168.122.209 [35672.612985] [tempesta fw] Tempesta FW is ready Apr 26 01:58:42 192.168.122.209 [35673.209621] [tdb] Close table 'client0.tdb' Apr 26 01:58:43 192.168.122.209 [35673.437834] [tdb] Close table 'sessions0.tdb' Apr 26 01:58:46 192.168.122.209 [35676.666004] [tdb] Close table 'cache0.tdb' Apr 26 01:58:46 192.168.122.209 [35676.885931] [tdb] Close table 'filter0.tdb' Apr 26 01:58:46 192.168.122.209 [35676.886360] [tempesta fw] modules are stopped Apr 26 01:58:46 192.168.122.209 [35677.136397] [tempesta fw] exiting... Apr 26 01:58:47 192.168.122.209 [35677.261441] [tdb] Shutdown Tempesta DB Apr 26 01:58:47 192.168.122.209 [35677.481447] End test: cache.test_cache.TestCacheMultipleMethodsHttp.test_GET_after_HEAD Apr 26 01:58:47 192.168.122.209 [35677.514826] Start test: cache.test_cache.TestCacheMultipleMethodsHttp.test_HEAD_after_GET Apr 26 01:58:48 192.168.122.209 [35678.740297] [tdb] Start Tempesta DB Apr 26 01:58:48 192.168.122.209 [35678.899957] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:58:50 192.168.122.209 [35680.446298] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35680.446298] Maybe that's fine, but it's worth checking the [35680.446298] config - if there is no relations between the [35680.446298] names, then host name confusion attack is possible. Apr 26 01:58:50 192.168.122.209 [35680.525070] [tempesta fw] Configuration processing is completed. Apr 26 01:58:50 192.168.122.209 [35680.606785] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:58:50 192.168.122.209 [35681.033863] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:58:50 192.168.122.209 [35681.060775] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:58:50 192.168.122.209 [35681.087770] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:58:50 192.168.122.209 [35681.137119] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:58:50 192.168.122.209 [35681.138861] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:58:50 192.168.122.209 [35681.185066] [tempesta fw] Tempesta FW is ready Apr 26 01:58:51 192.168.122.209 [35681.783433] [tdb] Close table 'client0.tdb' Apr 26 01:58:51 192.168.122.209 [35681.984741] [tdb] Close table 'sessions0.tdb' Apr 26 01:58:54 192.168.122.209 [35685.227482] [tdb] Close table 'cache0.tdb' Apr 26 01:58:55 192.168.122.209 [35685.478665] [tdb] Close table 'filter0.tdb' Apr 26 01:58:55 192.168.122.209 [35685.479102] [tempesta fw] modules are stopped Apr 26 01:58:55 192.168.122.209 [35685.672910] [tempesta fw] exiting... Apr 26 01:58:55 192.168.122.209 [35685.815532] [tdb] Shutdown Tempesta DB Apr 26 01:58:55 192.168.122.209 [35686.052770] End test: cache.test_cache.TestCacheMultipleMethodsHttp.test_HEAD_after_GET Apr 26 01:58:55 192.168.122.209 [35686.071678] Start test: cache.test_cache.TestCacheMultipleMethodsHttp.test_HEAD_after_HEAD Apr 26 01:58:57 192.168.122.209 [35687.318683] [tdb] Start Tempesta DB Apr 26 01:58:57 192.168.122.209 [35687.470479] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:58:58 192.168.122.209 [35689.006494] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35689.006494] Maybe that's fine, but it's worth checking the [35689.006494] config - if there is no relations between the [35689.006494] names, then host name confusion attack is possible. Apr 26 01:58:58 192.168.122.209 [35689.069240] [tempesta fw] Configuration processing is completed. Apr 26 01:58:58 192.168.122.209 [35689.123766] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:58:59 192.168.122.209 [35689.547256] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:58:59 192.168.122.209 [35689.573440] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:58:59 192.168.122.209 [35689.598942] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:58:59 192.168.122.209 [35689.637192] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:58:59 192.168.122.209 [35689.638885] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:58:59 192.168.122.209 [35689.689168] [tempesta fw] Tempesta FW is ready Apr 26 01:59:00 192.168.122.209 [35690.294901] [tdb] Close table 'client0.tdb' Apr 26 01:59:00 192.168.122.209 [35690.479307] [tdb] Close table 'sessions0.tdb' Apr 26 01:59:03 192.168.122.209 [35693.639768] [tdb] Close table 'cache0.tdb' Apr 26 01:59:03 192.168.122.209 [35693.879487] [tdb] Close table 'filter0.tdb' Apr 26 01:59:03 192.168.122.209 [35693.879943] [tempesta fw] modules are stopped Apr 26 01:59:03 192.168.122.209 [35694.056269] [tempesta fw] exiting... Apr 26 01:59:03 192.168.122.209 [35694.216840] [tdb] Shutdown Tempesta DB Apr 26 01:59:04 192.168.122.209 [35694.438492] End test: cache.test_cache.TestCacheMultipleMethodsHttp.test_HEAD_after_HEAD Apr 26 01:59:04 192.168.122.209 [35694.456782] Start test: cache.test_cache.TestCacheMultipleMethodsHttp.test_POST_after_GET Apr 26 01:59:05 192.168.122.209 [35695.681021] [tdb] Start Tempesta DB Apr 26 01:59:05 192.168.122.209 [35695.826345] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:59:07 192.168.122.209 [35697.418279] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35697.418279] Maybe that's fine, but it's worth checking the [35697.418279] config - if there is no relations between the [35697.418279] names, then host name confusion attack is possible. Apr 26 01:59:07 192.168.122.209 [35697.485651] [tempesta fw] Configuration processing is completed. Apr 26 01:59:07 192.168.122.209 [35697.544074] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:59:07 192.168.122.209 [35697.963709] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:59:07 192.168.122.209 [35697.989905] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:59:07 192.168.122.209 [35698.015743] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:59:07 192.168.122.209 [35698.061278] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:59:07 192.168.122.209 [35698.062702] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:59:07 192.168.122.209 [35698.101275] [tempesta fw] Tempesta FW is ready Apr 26 01:59:08 192.168.122.209 [35698.709750] [tdb] Close table 'client0.tdb' Apr 26 01:59:08 192.168.122.209 [35698.899197] [tdb] Close table 'sessions0.tdb' Apr 26 01:59:11 192.168.122.209 [35702.129288] [tdb] Close table 'cache0.tdb' Apr 26 01:59:12 192.168.122.209 [35702.374866] [tdb] Close table 'filter0.tdb' Apr 26 01:59:12 192.168.122.209 [35702.375298] [tempesta fw] modules are stopped Apr 26 01:59:12 192.168.122.209 [35702.570214] [tempesta fw] exiting... Apr 26 01:59:12 192.168.122.209 [35702.733654] [tdb] Shutdown Tempesta DB Apr 26 01:59:12 192.168.122.209 [35702.948232] End test: cache.test_cache.TestCacheMultipleMethodsHttp.test_POST_after_GET Apr 26 01:59:12 192.168.122.209 [35702.966710] Start test: cache.test_cache.TestCacheMultipleMethodsHttp.test_POST_after_HEAD Apr 26 01:59:13 192.168.122.209 [35704.168032] [tdb] Start Tempesta DB Apr 26 01:59:14 192.168.122.209 [35704.305906] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:59:15 192.168.122.209 [35705.826682] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35705.826682] Maybe that's fine, but it's worth checking the [35705.826682] config - if there is no relations between the [35705.826682] names, then host name confusion attack is possible. Apr 26 01:59:15 192.168.122.209 [35705.893477] [tempesta fw] Configuration processing is completed. Apr 26 01:59:15 192.168.122.209 [35705.985414] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:59:16 192.168.122.209 [35706.421504] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:59:16 192.168.122.209 [35706.447900] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:59:16 192.168.122.209 [35706.477362] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:59:16 192.168.122.209 [35706.525441] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:59:16 192.168.122.209 [35706.527174] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:59:16 192.168.122.209 [35706.581392] [tempesta fw] Tempesta FW is ready Apr 26 01:59:16 192.168.122.209 [35707.189352] [tdb] Close table 'client0.tdb' Apr 26 01:59:17 192.168.122.209 [35707.401841] [tdb] Close table 'sessions0.tdb' Apr 26 01:59:20 192.168.122.209 [35710.573042] [tdb] Close table 'cache0.tdb' Apr 26 01:59:20 192.168.122.209 [35710.836121] [tdb] Close table 'filter0.tdb' Apr 26 01:59:20 192.168.122.209 [35710.836561] [tempesta fw] modules are stopped Apr 26 01:59:20 192.168.122.209 [35711.013719] [tempesta fw] exiting... Apr 26 01:59:20 192.168.122.209 [35711.163580] [tdb] Shutdown Tempesta DB Apr 26 01:59:21 192.168.122.209 [35711.379466] End test: cache.test_cache.TestCacheMultipleMethodsHttp.test_POST_after_HEAD Apr 26 01:59:21 192.168.122.209 [35711.390097] Start test: cache.test_cache.TestCacheMultipleMethodsHttp.test_cache_POST_request_not_cached_no_cache_control Apr 26 01:59:22 192.168.122.209 [35712.599305] [tdb] Start Tempesta DB Apr 26 01:59:22 192.168.122.209 [35712.752122] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:59:23 192.168.122.209 [35714.242803] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35714.242803] Maybe that's fine, but it's worth checking the [35714.242803] config - if there is no relations between the [35714.242803] names, then host name confusion attack is possible. Apr 26 01:59:24 192.168.122.209 [35714.313542] [tempesta fw] Configuration processing is completed. Apr 26 01:59:24 192.168.122.209 [35714.364055] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:59:24 192.168.122.209 [35714.789677] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:59:24 192.168.122.209 [35714.815633] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:59:24 192.168.122.209 [35714.841047] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:59:24 192.168.122.209 [35714.889547] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:59:24 192.168.122.209 [35714.891261] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:59:24 192.168.122.209 [35714.933504] [tempesta fw] Tempesta FW is ready Apr 26 01:59:25 192.168.122.209 [35715.525636] [tdb] Close table 'client0.tdb' Apr 26 01:59:25 192.168.122.209 [35715.753304] [tdb] Close table 'sessions0.tdb' Apr 26 01:59:28 192.168.122.209 [35718.971889] [tdb] Close table 'cache0.tdb' Apr 26 01:59:28 192.168.122.209 [35719.212669] [tdb] Close table 'filter0.tdb' Apr 26 01:59:28 192.168.122.209 [35719.213106] [tempesta fw] modules are stopped Apr 26 01:59:29 192.168.122.209 [35719.406002] [tempesta fw] exiting... Apr 26 01:59:29 192.168.122.209 [35719.538480] [tdb] Shutdown Tempesta DB Apr 26 01:59:29 192.168.122.209 [35719.754954] End test: cache.test_cache.TestCacheMultipleMethodsHttp.test_cache_POST_request_not_cached_no_cache_control Apr 26 01:59:29 192.168.122.209 [35719.774256] Start test: cache.test_cache.TestCacheMultipleMethodsHttp.test_cache_POST_request_not_cached_not_same_location Apr 26 01:59:30 192.168.122.209 [35720.977755] [tdb] Start Tempesta DB Apr 26 01:59:30 192.168.122.209 [35721.138989] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:59:32 192.168.122.209 [35722.642890] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35722.642890] Maybe that's fine, but it's worth checking the [35722.642890] config - if there is no relations between the [35722.642890] names, then host name confusion attack is possible. Apr 26 01:59:32 192.168.122.209 [35722.709671] [tempesta fw] Configuration processing is completed. Apr 26 01:59:32 192.168.122.209 [35722.768562] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:59:32 192.168.122.209 [35723.236006] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:59:33 192.168.122.209 [35723.262516] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:59:33 192.168.122.209 [35723.288982] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:59:33 192.168.122.209 [35723.329617] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:59:33 192.168.122.209 [35723.330810] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:59:33 192.168.122.209 [35723.377644] [tempesta fw] Tempesta FW is ready Apr 26 01:59:33 192.168.122.209 [35724.004488] [tdb] Close table 'client0.tdb' Apr 26 01:59:33 192.168.122.209 [35724.192939] [tdb] Close table 'sessions0.tdb' Apr 26 01:59:37 192.168.122.209 [35727.436250] [tdb] Close table 'cache0.tdb' Apr 26 01:59:37 192.168.122.209 [35727.683379] [tdb] Close table 'filter0.tdb' Apr 26 01:59:37 192.168.122.209 [35727.683863] [tempesta fw] modules are stopped Apr 26 01:59:37 192.168.122.209 [35727.886119] [tempesta fw] exiting... Apr 26 01:59:37 192.168.122.209 [35728.035061] [tdb] Shutdown Tempesta DB Apr 26 01:59:38 192.168.122.209 [35728.282945] End test: cache.test_cache.TestCacheMultipleMethodsHttp.test_cache_POST_request_not_cached_not_same_location Apr 26 01:59:38 192.168.122.209 [35728.301839] Start test: cache.test_cache.TestCacheMultipleMethodsHttp.test_cache_POST_request_with_location_GET Apr 26 01:59:39 192.168.122.209 [35729.496316] [tdb] Start Tempesta DB Apr 26 01:59:39 192.168.122.209 [35729.661746] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:59:40 192.168.122.209 [35731.219085] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35731.219085] Maybe that's fine, but it's worth checking the [35731.219085] config - if there is no relations between the [35731.219085] names, then host name confusion attack is possible. Apr 26 01:59:41 192.168.122.209 [35731.285780] [tempesta fw] Configuration processing is completed. Apr 26 01:59:41 192.168.122.209 [35731.338244] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:59:41 192.168.122.209 [35731.793647] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:59:41 192.168.122.209 [35731.822736] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:59:41 192.168.122.209 [35731.852520] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:59:41 192.168.122.209 [35731.901707] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:59:41 192.168.122.209 [35731.903662] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:59:41 192.168.122.209 [35731.941733] [tempesta fw] Tempesta FW is ready Apr 26 01:59:42 192.168.122.209 [35732.562832] [tdb] Close table 'client0.tdb' Apr 26 01:59:42 192.168.122.209 [35732.753764] [tdb] Close table 'sessions0.tdb' Apr 26 01:59:45 192.168.122.209 [35735.985311] [tdb] Close table 'cache0.tdb' Apr 26 01:59:45 192.168.122.209 [35736.243823] [tdb] Close table 'filter0.tdb' Apr 26 01:59:45 192.168.122.209 [35736.244271] [tempesta fw] modules are stopped Apr 26 01:59:46 192.168.122.209 [35736.427582] [tempesta fw] exiting... Apr 26 01:59:46 192.168.122.209 [35736.582775] [tdb] Shutdown Tempesta DB Apr 26 01:59:46 192.168.122.209 [35736.816335] End test: cache.test_cache.TestCacheMultipleMethodsHttp.test_cache_POST_request_with_location_GET Apr 26 01:59:46 192.168.122.209 [35736.852789] Start test: cache.test_cache.TestCacheMultipleMethodsHttp.test_cache_POST_request_with_location_HEAD Apr 26 01:59:47 192.168.122.209 [35738.087780] [tdb] Start Tempesta DB Apr 26 01:59:47 192.168.122.209 [35738.241371] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:59:49 192.168.122.209 [35739.847127] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35739.847127] Maybe that's fine, but it's worth checking the [35739.847127] config - if there is no relations between the [35739.847127] names, then host name confusion attack is possible. Apr 26 01:59:49 192.168.122.209 [35739.925889] [tempesta fw] Configuration processing is completed. Apr 26 01:59:49 192.168.122.209 [35739.975476] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:59:50 192.168.122.209 [35740.397567] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:59:50 192.168.122.209 [35740.424657] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:59:50 192.168.122.209 [35740.451706] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:59:50 192.168.122.209 [35740.513840] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:59:50 192.168.122.209 [35740.515577] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:59:50 192.168.122.209 [35740.565823] [tempesta fw] Tempesta FW is ready Apr 26 01:59:50 192.168.122.209 [35741.166994] [tdb] Close table 'client0.tdb' Apr 26 01:59:51 192.168.122.209 [35741.357976] [tdb] Close table 'sessions0.tdb' Apr 26 01:59:54 192.168.122.209 [35744.578875] [tdb] Close table 'cache0.tdb' Apr 26 01:59:54 192.168.122.209 [35744.831864] [tdb] Close table 'filter0.tdb' Apr 26 01:59:54 192.168.122.209 [35744.832313] [tempesta fw] modules are stopped Apr 26 01:59:54 192.168.122.209 [35745.010794] [tempesta fw] exiting... Apr 26 01:59:54 192.168.122.209 [35745.174074] [tdb] Shutdown Tempesta DB Apr 26 01:59:55 192.168.122.209 [35745.404190] End test: cache.test_cache.TestCacheMultipleMethodsHttp.test_cache_POST_request_with_location_HEAD Apr 26 01:59:55 192.168.122.209 [35745.430140] Start test: cache.test_cache.TestCacheMultipleMethodsHttp.test_cache_POST_request_with_location_POST Apr 26 01:59:56 192.168.122.209 [35746.637261] [tdb] Start Tempesta DB Apr 26 01:59:56 192.168.122.209 [35746.801107] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 01:59:58 192.168.122.209 [35748.423274] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35748.423274] Maybe that's fine, but it's worth checking the [35748.423274] config - if there is no relations between the [35748.423274] names, then host name confusion attack is possible. Apr 26 01:59:58 192.168.122.209 [35748.505988] [tempesta fw] Configuration processing is completed. Apr 26 01:59:58 192.168.122.209 [35748.555830] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 01:59:58 192.168.122.209 [35749.022156] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 01:59:58 192.168.122.209 [35749.051079] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 01:59:58 192.168.122.209 [35749.080430] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 01:59:58 192.168.122.209 [35749.125969] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 01:59:58 192.168.122.209 [35749.127702] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 01:59:58 192.168.122.209 [35749.161964] [tempesta fw] Tempesta FW is ready Apr 26 01:59:59 192.168.122.209 [35749.765171] [tdb] Close table 'client0.tdb' Apr 26 01:59:59 192.168.122.209 [35749.957368] [tdb] Close table 'sessions0.tdb' Apr 26 02:00:02 192.168.122.209 [35753.155516] [tdb] Close table 'cache0.tdb' Apr 26 02:00:03 192.168.122.209 [35753.405019] [tdb] Close table 'filter0.tdb' Apr 26 02:00:03 192.168.122.209 [35753.405468] [tempesta fw] modules are stopped Apr 26 02:00:03 192.168.122.209 [35753.571200] [tempesta fw] exiting... Apr 26 02:00:03 192.168.122.209 [35753.725282] [tdb] Shutdown Tempesta DB Apr 26 02:00:03 192.168.122.209 [35754.013358] End test: cache.test_cache.TestCacheMultipleMethodsHttp.test_cache_POST_request_with_location_POST Apr 26 02:00:03 192.168.122.209 [35754.025252] Start test: cache.test_cache.TestCacheMultipleMethodsHttp.test_several_entries_GET_GET Apr 26 02:00:05 192.168.122.209 [35755.320961] [tdb] Start Tempesta DB Apr 26 02:00:05 192.168.122.209 [35755.473278] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:00:07 192.168.122.209 [35758.015552] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35758.015552] Maybe that's fine, but it's worth checking the [35758.015552] config - if there is no relations between the [35758.015552] names, then host name confusion attack is possible. Apr 26 02:00:08 192.168.122.209 [35758.515797] [tempesta fw] Configuration processing is completed. Apr 26 02:00:08 192.168.122.209 [35758.749129] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:00:08 192.168.122.209 [35759.208070] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:00:08 192.168.122.209 [35759.237055] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:00:09 192.168.122.209 [35759.264755] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:00:09 192.168.122.209 [35759.818125] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:00:09 192.168.122.209 [35759.819876] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:00:10 192.168.122.209 [35760.270111] [tempesta fw] Tempesta FW is ready Apr 26 02:00:13 192.168.122.209 [35763.282771] [tdb] Close table 'client0.tdb' Apr 26 02:00:13 192.168.122.209 [35763.504526] [tdb] Close table 'sessions0.tdb' Apr 26 02:00:16 192.168.122.209 [35766.720346] [tdb] Close table 'cache0.tdb' Apr 26 02:00:16 192.168.122.209 [35766.940846] [tdb] Close table 'filter0.tdb' Apr 26 02:00:16 192.168.122.209 [35766.941283] [tempesta fw] modules are stopped Apr 26 02:00:16 192.168.122.209 [35767.145102] [tempesta fw] exiting... Apr 26 02:00:17 192.168.122.209 [35767.312377] [tdb] Shutdown Tempesta DB Apr 26 02:00:17 192.168.122.209 [35767.544203] End test: cache.test_cache.TestCacheMultipleMethodsHttp.test_several_entries_GET_GET Apr 26 02:00:17 192.168.122.209 [35767.565266] Start test: cache.test_cache.TestCacheMultipleMethodsHttp.test_several_entries_GET_HEAD Apr 26 02:00:18 192.168.122.209 [35768.767490] [tdb] Start Tempesta DB Apr 26 02:00:18 192.168.122.209 [35768.926998] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:00:20 192.168.122.209 [35770.431557] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35770.431557] Maybe that's fine, but it's worth checking the [35770.431557] config - if there is no relations between the [35770.431557] names, then host name confusion attack is possible. Apr 26 02:00:20 192.168.122.209 [35770.510582] [tempesta fw] Configuration processing is completed. Apr 26 02:00:20 192.168.122.209 [35770.596987] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:00:20 192.168.122.209 [35771.026581] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:00:20 192.168.122.209 [35771.056657] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:00:20 192.168.122.209 [35771.083964] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:00:20 192.168.122.209 [35771.126292] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:00:20 192.168.122.209 [35771.128043] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:00:20 192.168.122.209 [35771.166241] [tempesta fw] Tempesta FW is ready Apr 26 02:00:23 192.168.122.209 [35773.792536] [tdb] Close table 'client0.tdb' Apr 26 02:00:23 192.168.122.209 [35773.978735] [tdb] Close table 'sessions0.tdb' Apr 26 02:00:26 192.168.122.209 [35777.249278] [tdb] Close table 'cache0.tdb' Apr 26 02:00:27 192.168.122.209 [35777.497889] [tdb] Close table 'filter0.tdb' Apr 26 02:00:27 192.168.122.209 [35777.498344] [tempesta fw] modules are stopped Apr 26 02:00:27 192.168.122.209 [35777.703067] [tempesta fw] exiting... Apr 26 02:00:27 192.168.122.209 [35777.882948] [tdb] Shutdown Tempesta DB Apr 26 02:00:27 192.168.122.209 [35778.117245] End test: cache.test_cache.TestCacheMultipleMethodsHttp.test_several_entries_GET_HEAD Apr 26 02:00:27 192.168.122.209 [35778.136338] Start test: cache.test_cache.TestCacheMultipleMethodsHttp.test_several_entries_GET_POST Apr 26 02:00:29 192.168.122.209 [35779.316620] [tdb] Start Tempesta DB Apr 26 02:00:29 192.168.122.209 [35779.467939] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:00:30 192.168.122.209 [35780.963649] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35780.963649] Maybe that's fine, but it's worth checking the [35780.963649] config - if there is no relations between the [35780.963649] names, then host name confusion attack is possible. Apr 26 02:00:30 192.168.122.209 [35781.038408] [tempesta fw] Configuration processing is completed. Apr 26 02:00:30 192.168.122.209 [35781.101723] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:00:31 192.168.122.209 [35781.524167] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:00:31 192.168.122.209 [35781.550095] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:00:31 192.168.122.209 [35781.575719] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:00:31 192.168.122.209 [35781.630431] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:00:31 192.168.122.209 [35781.632165] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:00:31 192.168.122.209 [35781.674384] [tempesta fw] Tempesta FW is ready Apr 26 02:00:32 192.168.122.209 [35782.308933] [tdb] Close table 'client0.tdb' Apr 26 02:00:32 192.168.122.209 [35782.504790] [tdb] Close table 'sessions0.tdb' Apr 26 02:00:35 192.168.122.209 [35785.685906] [tdb] Close table 'cache0.tdb' Apr 26 02:00:35 192.168.122.209 [35785.983245] [tdb] Close table 'filter0.tdb' Apr 26 02:00:35 192.168.122.209 [35785.983719] [tempesta fw] modules are stopped Apr 26 02:00:35 192.168.122.209 [35786.162813] [tempesta fw] exiting... Apr 26 02:00:36 192.168.122.209 [35786.293069] [tdb] Shutdown Tempesta DB Apr 26 02:00:36 192.168.122.209 [35786.526426] End test: cache.test_cache.TestCacheMultipleMethodsHttp.test_several_entries_GET_POST Apr 26 02:00:36 192.168.122.209 [35786.542115] Start test: cache.test_cache.TestCacheMultipleMethodsHttp.test_several_entries_POST_GET Apr 26 02:00:37 192.168.122.209 [35787.711467] [tdb] Start Tempesta DB Apr 26 02:00:37 192.168.122.209 [35787.866041] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:00:39 192.168.122.209 [35789.419761] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35789.419761] Maybe that's fine, but it's worth checking the [35789.419761] config - if there is no relations between the [35789.419761] names, then host name confusion attack is possible. Apr 26 02:00:39 192.168.122.209 [35789.498515] [tempesta fw] Configuration processing is completed. Apr 26 02:00:39 192.168.122.209 [35789.552481] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:00:39 192.168.122.209 [35789.993519] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:00:39 192.168.122.209 [35790.034862] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:00:39 192.168.122.209 [35790.066420] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:00:39 192.168.122.209 [35790.110519] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:00:39 192.168.122.209 [35790.112271] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:00:39 192.168.122.209 [35790.150472] [tempesta fw] Tempesta FW is ready Apr 26 02:00:42 192.168.122.209 [35792.765800] [tdb] Close table 'client0.tdb' Apr 26 02:00:42 192.168.122.209 [35792.961757] [tdb] Close table 'sessions0.tdb' Apr 26 02:00:45 192.168.122.209 [35796.214597] [tdb] Close table 'cache0.tdb' Apr 26 02:00:46 192.168.122.209 [35796.457164] [tdb] Close table 'filter0.tdb' Apr 26 02:00:46 192.168.122.209 [35796.457615] [tempesta fw] modules are stopped Apr 26 02:00:46 192.168.122.209 [35796.676794] [tempesta fw] exiting... Apr 26 02:00:46 192.168.122.209 [35796.836001] [tdb] Shutdown Tempesta DB Apr 26 02:00:46 192.168.122.209 [35797.080607] End test: cache.test_cache.TestCacheMultipleMethodsHttp.test_several_entries_POST_GET Apr 26 02:00:46 192.168.122.209 [35797.106442] Start test: cache.test_cache.TestCacheMultipleMethodsHttp.test_several_entries_POST_HEAD Apr 26 02:00:48 192.168.122.209 [35798.290777] [tdb] Start Tempesta DB Apr 26 02:00:48 192.168.122.209 [35798.435210] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:00:49 192.168.122.209 [35799.991920] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35799.991920] Maybe that's fine, but it's worth checking the [35799.991920] config - if there is no relations between the [35799.991920] names, then host name confusion attack is possible. Apr 26 02:00:49 192.168.122.209 [35800.070656] [tempesta fw] Configuration processing is completed. Apr 26 02:00:49 192.168.122.209 [35800.121410] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:00:50 192.168.122.209 [35800.565033] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:00:50 192.168.122.209 [35800.599524] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:00:50 192.168.122.209 [35800.625337] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:00:50 192.168.122.209 [35800.674657] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:00:50 192.168.122.209 [35800.675966] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:00:50 192.168.122.209 [35800.718624] [tempesta fw] Tempesta FW is ready Apr 26 02:00:53 192.168.122.209 [35803.355034] [tdb] Close table 'client0.tdb' Apr 26 02:00:53 192.168.122.209 [35803.543274] [tdb] Close table 'sessions0.tdb' Apr 26 02:00:56 192.168.122.209 [35806.757609] [tdb] Close table 'cache0.tdb' Apr 26 02:00:56 192.168.122.209 [35807.028060] [tdb] Close table 'filter0.tdb' Apr 26 02:00:56 192.168.122.209 [35807.028530] [tempesta fw] modules are stopped Apr 26 02:00:56 192.168.122.209 [35807.233144] [tempesta fw] exiting... Apr 26 02:00:57 192.168.122.209 [35807.370035] [tdb] Shutdown Tempesta DB Apr 26 02:00:57 192.168.122.209 [35807.610457] End test: cache.test_cache.TestCacheMultipleMethodsHttp.test_several_entries_POST_HEAD Apr 26 02:00:57 192.168.122.209 [35807.622088] Start test: cache.test_cache.TestCacheMultipleMethodsHttp.test_several_entries_POST_POST Apr 26 02:00:58 192.168.122.209 [35808.809695] [tdb] Start Tempesta DB Apr 26 02:00:58 192.168.122.209 [35808.963500] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:01:00 192.168.122.209 [35810.480151] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35810.480151] Maybe that's fine, but it's worth checking the [35810.480151] config - if there is no relations between the [35810.480151] names, then host name confusion attack is possible. Apr 26 02:01:00 192.168.122.209 [35810.554794] [tempesta fw] Configuration processing is completed. Apr 26 02:01:00 192.168.122.209 [35810.608360] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:01:00 192.168.122.209 [35811.030173] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:01:00 192.168.122.209 [35811.056615] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:01:00 192.168.122.209 [35811.083110] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:01:00 192.168.122.209 [35811.154806] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:01:00 192.168.122.209 [35811.156610] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:01:00 192.168.122.209 [35811.202791] [tempesta fw] Tempesta FW is ready Apr 26 02:01:01 192.168.122.209 [35811.847387] [tdb] Close table 'client0.tdb' Apr 26 02:01:01 192.168.122.209 [35812.045052] [tdb] Close table 'sessions0.tdb' Apr 26 02:01:04 192.168.122.209 [35815.207046] [tdb] Close table 'cache0.tdb' Apr 26 02:01:05 192.168.122.209 [35815.451413] [tdb] Close table 'filter0.tdb' Apr 26 02:01:05 192.168.122.209 [35815.451861] [tempesta fw] modules are stopped Apr 26 02:01:05 192.168.122.209 [35815.660291] [tempesta fw] exiting... Apr 26 02:01:05 192.168.122.209 [35815.830206] [tdb] Shutdown Tempesta DB Apr 26 02:01:05 192.168.122.209 [35816.065610] End test: cache.test_cache.TestCacheMultipleMethodsHttp.test_several_entries_POST_POST Apr 26 02:01:05 192.168.122.209 [35816.077312] Start test: cache.test_cache.TestCacheMultipleMethodsHttp.test_update_cache_via_DELETE_request Apr 26 02:01:06 192.168.122.209 [35817.233181] [tdb] Start Tempesta DB Apr 26 02:01:07 192.168.122.209 [35817.377180] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:01:08 192.168.122.209 [35818.880145] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35818.880145] Maybe that's fine, but it's worth checking the [35818.880145] config - if there is no relations between the [35818.880145] names, then host name confusion attack is possible. Apr 26 02:01:08 192.168.122.209 [35818.951241] [tempesta fw] Configuration processing is completed. Apr 26 02:01:08 192.168.122.209 [35819.048714] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:01:09 192.168.122.209 [35819.478545] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:01:09 192.168.122.209 [35819.505591] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:01:09 192.168.122.209 [35819.533543] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:01:09 192.168.122.209 [35819.602918] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:01:09 192.168.122.209 [35819.604655] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:01:09 192.168.122.209 [35819.646855] [tempesta fw] Tempesta FW is ready Apr 26 02:01:10 192.168.122.209 [35820.279775] [tdb] Close table 'client0.tdb' Apr 26 02:01:10 192.168.122.209 [35820.477138] [tdb] Close table 'sessions0.tdb' Apr 26 02:01:13 192.168.122.209 [35823.643070] [tdb] Close table 'cache0.tdb' Apr 26 02:01:13 192.168.122.209 [35823.899914] [tdb] Close table 'filter0.tdb' Apr 26 02:01:13 192.168.122.209 [35823.900349] [tempesta fw] modules are stopped Apr 26 02:01:13 192.168.122.209 [35824.091346] [tempesta fw] exiting... Apr 26 02:01:14 192.168.122.209 [35824.263793] [tdb] Shutdown Tempesta DB Apr 26 02:01:14 192.168.122.209 [35824.492685] End test: cache.test_cache.TestCacheMultipleMethodsHttp.test_update_cache_via_DELETE_request Apr 26 02:01:14 192.168.122.209 [35824.513731] Start test: cache.test_cache.TestCacheMultipleMethodsHttp.test_update_cache_via_PUT_request Apr 26 02:01:15 192.168.122.209 [35825.644883] [tdb] Start Tempesta DB Apr 26 02:01:15 192.168.122.209 [35825.800554] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:01:17 192.168.122.209 [35827.380372] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35827.380372] Maybe that's fine, but it's worth checking the [35827.380372] config - if there is no relations between the [35827.380372] names, then host name confusion attack is possible. Apr 26 02:01:17 192.168.122.209 [35827.459020] [tempesta fw] Configuration processing is completed. Apr 26 02:01:17 192.168.122.209 [35827.508459] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:01:17 192.168.122.209 [35827.927057] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:01:17 192.168.122.209 [35827.953540] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:01:17 192.168.122.209 [35827.980135] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:01:17 192.168.122.209 [35828.031038] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:01:17 192.168.122.209 [35828.032760] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:01:17 192.168.122.209 [35828.078971] [tempesta fw] Tempesta FW is ready Apr 26 02:01:18 192.168.122.209 [35828.651224] [tdb] Close table 'client0.tdb' Apr 26 02:01:18 192.168.122.209 [35828.844190] [tdb] Close table 'sessions0.tdb' Apr 26 02:01:21 192.168.122.209 [35832.036486] [tdb] Close table 'cache0.tdb' Apr 26 02:01:22 192.168.122.209 [35832.265811] [tdb] Close table 'filter0.tdb' Apr 26 02:01:22 192.168.122.209 [35832.266250] [tempesta fw] modules are stopped Apr 26 02:01:22 192.168.122.209 [35832.484316] [tempesta fw] exiting... Apr 26 02:01:22 192.168.122.209 [35832.631623] [tdb] Shutdown Tempesta DB Apr 26 02:01:22 192.168.122.209 [35832.864596] End test: cache.test_cache.TestCacheMultipleMethodsHttp.test_update_cache_via_PUT_request Apr 26 02:01:22 192.168.122.209 [35832.877216] Start test: cache.test_cache.TestCacheOverriddenHostH2.test Apr 26 02:01:23 192.168.122.209 [35834.093454] [tdb] Start Tempesta DB Apr 26 02:01:23 192.168.122.209 [35834.224065] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:01:25 192.168.122.209 [35835.860358] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35835.860358] Maybe that's fine, but it's worth checking the [35835.860358] config - if there is no relations between the [35835.860358] names, then host name confusion attack is possible. Apr 26 02:01:25 192.168.122.209 [35835.963133] [tempesta fw] Configuration processing is completed. Apr 26 02:01:25 192.168.122.209 [35836.014980] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:01:26 192.168.122.209 [35836.434907] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:01:26 192.168.122.209 [35836.461604] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:01:26 192.168.122.209 [35836.487443] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:01:26 192.168.122.209 [35836.547130] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:01:26 192.168.122.209 [35836.548981] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:01:26 192.168.122.209 [35836.591086] [tempesta fw] Tempesta FW is ready Apr 26 02:01:26 192.168.122.209 [35837.224385] [tdb] Close table 'client0.tdb' Apr 26 02:01:27 192.168.122.209 [35837.405299] [tdb] Close table 'sessions0.tdb' Apr 26 02:01:30 192.168.122.209 [35840.631284] [tdb] Close table 'cache0.tdb' Apr 26 02:01:30 192.168.122.209 [35840.884901] [tdb] Close table 'filter0.tdb' Apr 26 02:01:30 192.168.122.209 [35840.885321] [tempesta fw] modules are stopped Apr 26 02:01:30 192.168.122.209 [35841.068378] [tempesta fw] exiting... Apr 26 02:01:30 192.168.122.209 [35841.215085] [tdb] Shutdown Tempesta DB Apr 26 02:01:31 192.168.122.209 [35841.426587] End test: cache.test_cache.TestCacheOverriddenHostH2.test Apr 26 02:01:31 192.168.122.209 [35841.445390] Start test: cache.test_cache.TestCacheOverriddenHostHttp.test Apr 26 02:01:32 192.168.122.209 [35842.697112] [tdb] Start Tempesta DB Apr 26 02:01:32 192.168.122.209 [35842.835640] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:01:34 192.168.122.209 [35844.352476] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35844.352476] Maybe that's fine, but it's worth checking the [35844.352476] config - if there is no relations between the [35844.352476] names, then host name confusion attack is possible. Apr 26 02:01:34 192.168.122.209 [35844.451283] [tempesta fw] Configuration processing is completed. Apr 26 02:01:34 192.168.122.209 [35844.541143] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:01:34 192.168.122.209 [35844.976304] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:01:34 192.168.122.209 [35845.003147] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:01:34 192.168.122.209 [35845.030399] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:01:34 192.168.122.209 [35845.079257] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:01:34 192.168.122.209 [35845.080986] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:01:34 192.168.122.209 [35845.131141] [tempesta fw] Tempesta FW is ready Apr 26 02:01:35 192.168.122.209 [35845.760865] [tdb] Close table 'client0.tdb' Apr 26 02:01:35 192.168.122.209 [35845.953881] [tdb] Close table 'sessions0.tdb' Apr 26 02:01:38 192.168.122.209 [35849.180220] [tdb] Close table 'cache0.tdb' Apr 26 02:01:39 192.168.122.209 [35849.408211] [tdb] Close table 'filter0.tdb' Apr 26 02:01:39 192.168.122.209 [35849.408680] [tempesta fw] modules are stopped Apr 26 02:01:39 192.168.122.209 [35849.616878] [tempesta fw] exiting... Apr 26 02:01:39 192.168.122.209 [35849.772681] [tdb] Shutdown Tempesta DB Apr 26 02:01:39 192.168.122.209 [35849.973788] End test: cache.test_cache.TestCacheOverriddenHostHttp.test Apr 26 02:01:39 192.168.122.209 [35849.988043] Start test: cache.test_cache.TestCacheResponseWithCacheDifferentClients.test_GET_deproxy_deproxy_h2 Apr 26 02:01:40 192.168.122.209 [35851.171498] [tdb] Start Tempesta DB Apr 26 02:01:41 192.168.122.209 [35851.340441] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:01:42 192.168.122.209 [35852.957127] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35852.957127] Maybe that's fine, but it's worth checking the [35852.957127] config - if there is no relations between the [35852.957127] names, then host name confusion attack is possible. Apr 26 02:01:42 192.168.122.209 [35853.007323] [tempesta fw] Configuration processing is completed. Apr 26 02:01:42 192.168.122.209 [35853.078745] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:01:43 192.168.122.209 [35853.496509] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:01:43 192.168.122.209 [35853.522863] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:01:43 192.168.122.209 [35853.548809] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:01:43 192.168.122.209 [35853.595344] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:01:43 192.168.122.209 [35853.597063] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:01:43 192.168.122.209 [35853.639289] [tempesta fw] Tempesta FW is ready Apr 26 02:01:44 192.168.122.209 [35854.278385] [tdb] Close table 'client0.tdb' Apr 26 02:01:44 192.168.122.209 [35854.476261] [tdb] Close table 'sessions0.tdb' Apr 26 02:01:47 192.168.122.209 [35857.685490] [tdb] Close table 'cache0.tdb' Apr 26 02:01:47 192.168.122.209 [35857.929614] [tdb] Close table 'filter0.tdb' Apr 26 02:01:47 192.168.122.209 [35857.930045] [tempesta fw] modules are stopped Apr 26 02:01:47 192.168.122.209 [35858.134187] [tempesta fw] exiting... Apr 26 02:01:48 192.168.122.209 [35858.279345] [tdb] Shutdown Tempesta DB Apr 26 02:01:48 192.168.122.209 [35858.502744] End test: cache.test_cache.TestCacheResponseWithCacheDifferentClients.test_GET_deproxy_deproxy_h2 Apr 26 02:01:48 192.168.122.209 [35858.520200] Start test: cache.test_cache.TestCacheResponseWithCacheDifferentClients.test_GET_deproxy_h2_deproxy Apr 26 02:01:49 192.168.122.209 [35859.735402] [tdb] Start Tempesta DB Apr 26 02:01:49 192.168.122.209 [35859.891285] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:01:51 192.168.122.209 [35861.441098] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35861.441098] Maybe that's fine, but it's worth checking the [35861.441098] config - if there is no relations between the [35861.441098] names, then host name confusion attack is possible. Apr 26 02:01:51 192.168.122.209 [35861.491811] [tempesta fw] Configuration processing is completed. Apr 26 02:01:51 192.168.122.209 [35861.542701] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:01:51 192.168.122.209 [35861.968134] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:01:51 192.168.122.209 [35861.994148] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:01:51 192.168.122.209 [35862.019930] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:01:51 192.168.122.209 [35862.075455] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:01:51 192.168.122.209 [35862.077164] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:01:51 192.168.122.209 [35862.119404] [tempesta fw] Tempesta FW is ready Apr 26 02:01:52 192.168.122.209 [35862.722034] [tdb] Close table 'client0.tdb' Apr 26 02:01:52 192.168.122.209 [35862.912649] [tdb] Close table 'sessions0.tdb' Apr 26 02:01:55 192.168.122.209 [35866.125408] [tdb] Close table 'cache0.tdb' Apr 26 02:01:56 192.168.122.209 [35866.342739] [tdb] Close table 'filter0.tdb' Apr 26 02:01:56 192.168.122.209 [35866.343171] [tempesta fw] modules are stopped Apr 26 02:01:56 192.168.122.209 [35866.557234] [tempesta fw] exiting... Apr 26 02:01:56 192.168.122.209 [35866.688367] [tdb] Shutdown Tempesta DB Apr 26 02:01:56 192.168.122.209 [35866.914565] End test: cache.test_cache.TestCacheResponseWithCacheDifferentClients.test_GET_deproxy_h2_deproxy Apr 26 02:01:56 192.168.122.209 [35866.925441] Start test: cache.test_cache.TestCacheResponseWithCacheDifferentClients.test_HEAD_deproxy_deproxy_h2 Apr 26 02:01:57 192.168.122.209 [35868.113235] [tdb] Start Tempesta DB Apr 26 02:01:58 192.168.122.209 [35868.264483] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:01:59 192.168.122.209 [35869.805200] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35869.805200] Maybe that's fine, but it's worth checking the [35869.805200] config - if there is no relations between the [35869.805200] names, then host name confusion attack is possible. Apr 26 02:01:59 192.168.122.209 [35869.859512] [tempesta fw] Configuration processing is completed. Apr 26 02:01:59 192.168.122.209 [35869.946653] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:02:00 192.168.122.209 [35870.379430] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:02:00 192.168.122.209 [35870.406368] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:02:00 192.168.122.209 [35870.433349] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:02:00 192.168.122.209 [35870.483574] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:02:00 192.168.122.209 [35870.485168] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:02:00 192.168.122.209 [35870.527519] [tempesta fw] Tempesta FW is ready Apr 26 02:02:00 192.168.122.209 [35871.155728] [tdb] Close table 'client0.tdb' Apr 26 02:02:01 192.168.122.209 [35871.390216] [tdb] Close table 'sessions0.tdb' Apr 26 02:02:04 192.168.122.209 [35874.582541] [tdb] Close table 'cache0.tdb' Apr 26 02:02:04 192.168.122.209 [35874.816476] [tdb] Close table 'filter0.tdb' Apr 26 02:02:04 192.168.122.209 [35874.816939] [tempesta fw] modules are stopped Apr 26 02:02:04 192.168.122.209 [35875.000712] [tempesta fw] exiting... Apr 26 02:02:04 192.168.122.209 [35875.149627] [tdb] Shutdown Tempesta DB Apr 26 02:02:05 192.168.122.209 [35875.376244] End test: cache.test_cache.TestCacheResponseWithCacheDifferentClients.test_HEAD_deproxy_deproxy_h2 Apr 26 02:02:05 192.168.122.209 [35875.394204] Start test: cache.test_cache.TestCacheResponseWithCacheDifferentClients.test_HEAD_deproxy_h2_deproxy Apr 26 02:02:06 192.168.122.209 [35876.640662] [tdb] Start Tempesta DB Apr 26 02:02:06 192.168.122.209 [35876.788482] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:02:08 192.168.122.209 [35878.393353] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35878.393353] Maybe that's fine, but it's worth checking the [35878.393353] config - if there is no relations between the [35878.393353] names, then host name confusion attack is possible. Apr 26 02:02:08 192.168.122.209 [35878.443939] [tempesta fw] Configuration processing is completed. Apr 26 02:02:08 192.168.122.209 [35878.493259] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:02:08 192.168.122.209 [35878.910435] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:02:08 192.168.122.209 [35878.936368] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:02:08 192.168.122.209 [35878.962111] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:02:08 192.168.122.209 [35879.003683] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:02:08 192.168.122.209 [35879.005409] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:02:08 192.168.122.209 [35879.043629] [tempesta fw] Tempesta FW is ready Apr 26 02:02:09 192.168.122.209 [35879.660386] [tdb] Close table 'client0.tdb' Apr 26 02:02:09 192.168.122.209 [35879.850402] [tdb] Close table 'sessions0.tdb' Apr 26 02:02:12 192.168.122.209 [35883.074783] [tdb] Close table 'cache0.tdb' Apr 26 02:02:13 192.168.122.209 [35883.308958] [tdb] Close table 'filter0.tdb' Apr 26 02:02:13 192.168.122.209 [35883.309379] [tempesta fw] modules are stopped Apr 26 02:02:13 192.168.122.209 [35883.484432] [tempesta fw] exiting... Apr 26 02:02:13 192.168.122.209 [35883.633650] [tdb] Shutdown Tempesta DB Apr 26 02:02:13 192.168.122.209 [35883.873732] End test: cache.test_cache.TestCacheResponseWithCacheDifferentClients.test_HEAD_deproxy_h2_deproxy Apr 26 02:02:13 192.168.122.209 [35883.897610] Start test: cache.test_cache.TestCacheResponseWithTrailersH2.test_GET_GET Apr 26 02:02:14 192.168.122.209 [35885.062189] [tdb] Start Tempesta DB Apr 26 02:02:14 192.168.122.209 [35885.213435] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:02:16 192.168.122.209 [35886.793570] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35886.793570] Maybe that's fine, but it's worth checking the [35886.793570] config - if there is no relations between the [35886.793570] names, then host name confusion attack is possible. Apr 26 02:02:16 192.168.122.209 [35886.851752] [tempesta fw] Configuration processing is completed. Apr 26 02:02:16 192.168.122.209 [35886.911724] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:02:17 192.168.122.209 [35887.328266] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:02:17 192.168.122.209 [35887.354361] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:02:17 192.168.122.209 [35887.380476] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:02:17 192.168.122.209 [35887.435819] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:02:17 192.168.122.209 [35887.437551] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:02:17 192.168.122.209 [35887.475740] [tempesta fw] Tempesta FW is ready Apr 26 02:02:17 192.168.122.209 [35888.096631] [tdb] Close table 'client0.tdb' Apr 26 02:02:18 192.168.122.209 [35888.309563] [tdb] Close table 'sessions0.tdb' Apr 26 02:02:21 192.168.122.209 [35891.502443] [tdb] Close table 'cache0.tdb' Apr 26 02:02:21 192.168.122.209 [35891.750834] [tdb] Close table 'filter0.tdb' Apr 26 02:02:21 192.168.122.209 [35891.751260] [tempesta fw] modules are stopped Apr 26 02:02:21 192.168.122.209 [35891.924585] [tempesta fw] exiting... Apr 26 02:02:21 192.168.122.209 [35892.066927] [tdb] Shutdown Tempesta DB Apr 26 02:02:22 192.168.122.209 [35892.296674] End test: cache.test_cache.TestCacheResponseWithTrailersH2.test_GET_GET Apr 26 02:02:22 192.168.122.209 [35892.322253] Start test: cache.test_cache.TestCacheResponseWithTrailersH2.test_GET_HEAD Apr 26 02:02:23 192.168.122.209 [35893.499090] [tdb] Start Tempesta DB Apr 26 02:02:23 192.168.122.209 [35893.635886] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:02:24 192.168.122.209 [35895.233506] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35895.233506] Maybe that's fine, but it's worth checking the [35895.233506] config - if there is no relations between the [35895.233506] names, then host name confusion attack is possible. Apr 26 02:02:25 192.168.122.209 [35895.276162] [tempesta fw] Configuration processing is completed. Apr 26 02:02:25 192.168.122.209 [35895.367560] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:02:25 192.168.122.209 [35895.796100] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:02:25 192.168.122.209 [35895.822971] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:02:25 192.168.122.209 [35895.849601] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:02:25 192.168.122.209 [35895.895904] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:02:25 192.168.122.209 [35895.897628] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:02:25 192.168.122.209 [35895.939839] [tempesta fw] Tempesta FW is ready Apr 26 02:02:26 192.168.122.209 [35896.596241] [tdb] Close table 'client0.tdb' Apr 26 02:02:26 192.168.122.209 [35896.776880] [tdb] Close table 'sessions0.tdb' Apr 26 02:02:29 192.168.122.209 [35899.979704] [tdb] Close table 'cache0.tdb' Apr 26 02:02:29 192.168.122.209 [35900.217503] [tdb] Close table 'filter0.tdb' Apr 26 02:02:29 192.168.122.209 [35900.218152] [tempesta fw] modules are stopped Apr 26 02:02:30 192.168.122.209 [35900.410488] [tempesta fw] exiting... Apr 26 02:02:30 192.168.122.209 [35900.543637] [tdb] Shutdown Tempesta DB Apr 26 02:02:30 192.168.122.209 [35900.765109] End test: cache.test_cache.TestCacheResponseWithTrailersH2.test_GET_HEAD Apr 26 02:02:30 192.168.122.209 [35900.798314] Start test: cache.test_cache.TestCacheResponseWithTrailersH2.test_HEAD_GET Apr 26 02:02:31 192.168.122.209 [35901.991841] [tdb] Start Tempesta DB Apr 26 02:02:31 192.168.122.209 [35902.159090] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:02:33 192.168.122.209 [35903.821629] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35903.821629] Maybe that's fine, but it's worth checking the [35903.821629] config - if there is no relations between the [35903.821629] names, then host name confusion attack is possible. Apr 26 02:02:33 192.168.122.209 [35903.864280] [tempesta fw] Configuration processing is completed. Apr 26 02:02:33 192.168.122.209 [35903.915552] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:02:34 192.168.122.209 [35904.347396] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:02:34 192.168.122.209 [35904.373704] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:02:34 192.168.122.209 [35904.399616] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:02:34 192.168.122.209 [35904.440019] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:02:34 192.168.122.209 [35904.441744] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:02:34 192.168.122.209 [35904.487960] [tempesta fw] Tempesta FW is ready Apr 26 02:02:34 192.168.122.209 [35905.129712] [tdb] Close table 'client0.tdb' Apr 26 02:02:35 192.168.122.209 [35905.301139] [tdb] Close table 'sessions0.tdb' Apr 26 02:02:38 192.168.122.209 [35908.500924] [tdb] Close table 'cache0.tdb' Apr 26 02:02:38 192.168.122.209 [35908.729521] [tdb] Close table 'filter0.tdb' Apr 26 02:02:38 192.168.122.209 [35908.729954] [tempesta fw] modules are stopped Apr 26 02:02:38 192.168.122.209 [35908.924191] [tempesta fw] exiting... Apr 26 02:02:38 192.168.122.209 [35909.083839] [tdb] Shutdown Tempesta DB Apr 26 02:02:39 192.168.122.209 [35909.278320] End test: cache.test_cache.TestCacheResponseWithTrailersH2.test_HEAD_GET Apr 26 02:02:39 192.168.122.209 [35909.288740] Start test: cache.test_cache.TestCacheResponseWithTrailersH2.test_HEAD_HEAD Apr 26 02:02:40 192.168.122.209 [35910.463484] [tdb] Start Tempesta DB Apr 26 02:02:40 192.168.122.209 [35910.628633] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:02:42 192.168.122.209 [35912.265747] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35912.265747] Maybe that's fine, but it's worth checking the [35912.265747] config - if there is no relations between the [35912.265747] names, then host name confusion attack is possible. Apr 26 02:02:42 192.168.122.209 [35912.324151] [tempesta fw] Configuration processing is completed. Apr 26 02:02:42 192.168.122.209 [35912.379168] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:02:42 192.168.122.209 [35912.797436] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:02:42 192.168.122.209 [35912.823367] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:02:42 192.168.122.209 [35912.849133] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:02:42 192.168.122.209 [35912.908125] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:02:42 192.168.122.209 [35912.909850] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:02:42 192.168.122.209 [35912.952041] [tempesta fw] Tempesta FW is ready Apr 26 02:02:43 192.168.122.209 [35913.564705] [tdb] Close table 'client0.tdb' Apr 26 02:02:43 192.168.122.209 [35913.766835] [tdb] Close table 'sessions0.tdb' Apr 26 02:02:46 192.168.122.209 [35916.991730] [tdb] Close table 'cache0.tdb' Apr 26 02:02:46 192.168.122.209 [35917.243101] [tdb] Close table 'filter0.tdb' Apr 26 02:02:46 192.168.122.209 [35917.243519] [tempesta fw] modules are stopped Apr 26 02:02:47 192.168.122.209 [35917.424012] [tempesta fw] exiting... Apr 26 02:02:47 192.168.122.209 [35917.604846] [tdb] Shutdown Tempesta DB Apr 26 02:02:47 192.168.122.209 [35917.797467] End test: cache.test_cache.TestCacheResponseWithTrailersH2.test_HEAD_HEAD Apr 26 02:02:47 192.168.122.209 [35917.821492] Start test: cache.test_cache.TestCacheResponseWithTrailersH2.test_empty_body_head_to_get Apr 26 02:02:48 192.168.122.209 [35919.029143] [tdb] Start Tempesta DB Apr 26 02:02:48 192.168.122.209 [35919.163867] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:02:50 192.168.122.209 [35920.805949] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35920.805949] Maybe that's fine, but it's worth checking the [35920.805949] config - if there is no relations between the [35920.805949] names, then host name confusion attack is possible. Apr 26 02:02:50 192.168.122.209 [35920.844509] [tempesta fw] Configuration processing is completed. Apr 26 02:02:50 192.168.122.209 [35920.928409] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:02:51 192.168.122.209 [35921.362895] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:02:51 192.168.122.209 [35921.389444] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:02:51 192.168.122.209 [35921.416014] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:02:51 192.168.122.209 [35921.456171] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:02:51 192.168.122.209 [35921.457159] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:02:51 192.168.122.209 [35921.512181] [tempesta fw] Tempesta FW is ready Apr 26 02:02:51 192.168.122.209 [35922.154195] [tdb] Close table 'client0.tdb' Apr 26 02:02:52 192.168.122.209 [35922.346367] [tdb] Close table 'sessions0.tdb' Apr 26 02:02:55 192.168.122.209 [35925.538592] [tdb] Close table 'cache0.tdb' Apr 26 02:02:55 192.168.122.209 [35925.802744] [tdb] Close table 'filter0.tdb' Apr 26 02:02:55 192.168.122.209 [35925.803190] [tempesta fw] modules are stopped Apr 26 02:02:55 192.168.122.209 [35926.013080] [tempesta fw] exiting... Apr 26 02:02:55 192.168.122.209 [35926.148492] [tdb] Shutdown Tempesta DB Apr 26 02:02:56 192.168.122.209 [35926.368283] End test: cache.test_cache.TestCacheResponseWithTrailersH2.test_empty_body_head_to_get Apr 26 02:02:56 192.168.122.209 [35926.396230] Start test: cache.test_cache.TestCacheResponseWithTrailersH2.test_hbh_headers_hbp_GET Apr 26 02:02:57 192.168.122.209 [35927.623369] [tdb] Start Tempesta DB Apr 26 02:02:57 192.168.122.209 [35927.773298] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:02:59 192.168.122.209 [35929.325980] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35929.325980] Maybe that's fine, but it's worth checking the [35929.325980] config - if there is no relations between the [35929.325980] names, then host name confusion attack is possible. Apr 26 02:02:59 192.168.122.209 [35929.376289] [tempesta fw] Configuration processing is completed. Apr 26 02:02:59 192.168.122.209 [35929.426216] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:02:59 192.168.122.209 [35929.852536] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:02:59 192.168.122.209 [35929.878838] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:02:59 192.168.122.209 [35929.904930] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:02:59 192.168.122.209 [35929.952346] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:02:59 192.168.122.209 [35929.954066] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:02:59 192.168.122.209 [35929.992318] [tempesta fw] Tempesta FW is ready Apr 26 02:02:59 192.168.122.209 [35930.161300] [tempesta fw] Warning: Parser error: state=Resp_HdrConnectionV input(-8)=0x6b('ection: keep-alive [35930.161300] Keep-Alive: timeout=5, max=1') data_len=347 off=301 Apr 26 02:02:59 192.168.122.209 [35930.165663] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 02:03:00 192.168.122.209 [35930.637014] [tdb] Close table 'client0.tdb' Apr 26 02:03:00 192.168.122.209 [35930.835327] [tdb] Close table 'sessions0.tdb' Apr 26 02:03:03 192.168.122.209 [35934.007494] [tdb] Close table 'cache0.tdb' Apr 26 02:03:03 192.168.122.209 [35934.248846] [tdb] Close table 'filter0.tdb' Apr 26 02:03:03 192.168.122.209 [35934.249286] [tempesta fw] modules are stopped Apr 26 02:03:04 192.168.122.209 [35934.425012] [tempesta fw] exiting... Apr 26 02:03:04 192.168.122.209 [35934.570327] [tdb] Shutdown Tempesta DB Apr 26 02:03:04 192.168.122.209 [35934.800111] End test: cache.test_cache.TestCacheResponseWithTrailersH2.test_hbh_headers_hbp_GET Apr 26 02:03:04 192.168.122.209 [35934.821922] Start test: cache.test_cache.TestCacheResponseWithTrailersH2.test_hbh_headers_hbp_HEAD Apr 26 02:03:05 192.168.122.209 [35935.981391] [tdb] Start Tempesta DB Apr 26 02:03:05 192.168.122.209 [35936.130405] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:03:07 192.168.122.209 [35937.650110] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35937.650110] Maybe that's fine, but it's worth checking the [35937.650110] config - if there is no relations between the [35937.650110] names, then host name confusion attack is possible. Apr 26 02:03:07 192.168.122.209 [35937.696749] [tempesta fw] Configuration processing is completed. Apr 26 02:03:07 192.168.122.209 [35937.747602] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:03:07 192.168.122.209 [35938.167904] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:03:07 192.168.122.209 [35938.194198] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:03:07 192.168.122.209 [35938.220146] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:03:08 192.168.122.209 [35938.272463] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:03:08 192.168.122.209 [35938.274225] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:03:08 192.168.122.209 [35938.320423] [tempesta fw] Tempesta FW is ready Apr 26 02:03:08 192.168.122.209 [35938.469745] [tempesta fw] Warning: Parser error: state=Resp_HdrConnectionV input(-8)=0x6b('ection: keep-alive [35938.469745] Keep-Alive: timeout=5, max=1') data_len=347 off=301 Apr 26 02:03:08 192.168.122.209 [35938.471790] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 02:03:08 192.168.122.209 [35938.915467] [tdb] Close table 'client0.tdb' Apr 26 02:03:08 192.168.122.209 [35939.110196] [tdb] Close table 'sessions0.tdb' Apr 26 02:03:12 192.168.122.209 [35942.266080] [tdb] Close table 'cache0.tdb' Apr 26 02:03:12 192.168.122.209 [35942.503370] [tdb] Close table 'filter0.tdb' Apr 26 02:03:12 192.168.122.209 [35942.503814] [tempesta fw] modules are stopped Apr 26 02:03:12 192.168.122.209 [35942.712343] [tempesta fw] exiting... Apr 26 02:03:12 192.168.122.209 [35942.884939] [tdb] Shutdown Tempesta DB Apr 26 02:03:12 192.168.122.209 [35943.148795] End test: cache.test_cache.TestCacheResponseWithTrailersH2.test_hbh_headers_hbp_HEAD Apr 26 02:03:12 192.168.122.209 [35943.169371] Start test: cache.test_cache.TestCacheResponseWithTrailersH2.test_hbh_headers_mix_GET Apr 26 02:03:14 192.168.122.209 [35944.373266] [tdb] Start Tempesta DB Apr 26 02:03:14 192.168.122.209 [35944.524356] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:03:15 192.168.122.209 [35946.166180] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35946.166180] Maybe that's fine, but it's worth checking the [35946.166180] config - if there is no relations between the [35946.166180] names, then host name confusion attack is possible. Apr 26 02:03:15 192.168.122.209 [35946.208819] [tempesta fw] Configuration processing is completed. Apr 26 02:03:16 192.168.122.209 [35946.297759] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:03:16 192.168.122.209 [35946.730609] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:03:16 192.168.122.209 [35946.757340] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:03:16 192.168.122.209 [35946.784009] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:03:16 192.168.122.209 [35946.828577] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:03:16 192.168.122.209 [35946.830296] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:03:16 192.168.122.209 [35946.889809] [tempesta fw] Tempesta FW is ready Apr 26 02:03:16 192.168.122.209 [35947.044205] [tempesta fw] Warning: Parser error: state=Resp_HdrConnectionV input(-8)=0x6b('ection: keep-alive [35947.044205] X-Token1: value1 [35947.044205] [35947.044205] ') data_len=331 off=299 Apr 26 02:03:16 192.168.122.209 [35947.046469] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 02:03:17 192.168.122.209 [35947.463911] [tdb] Close table 'client0.tdb' Apr 26 02:03:17 192.168.122.209 [35947.719859] [tdb] Close table 'sessions0.tdb' Apr 26 02:03:20 192.168.122.209 [35950.970246] [tdb] Close table 'cache0.tdb' Apr 26 02:03:20 192.168.122.209 [35951.219211] [tdb] Close table 'filter0.tdb' Apr 26 02:03:20 192.168.122.209 [35951.219647] [tempesta fw] modules are stopped Apr 26 02:03:21 192.168.122.209 [35951.426038] [tempesta fw] exiting... Apr 26 02:03:21 192.168.122.209 [35951.563602] [tdb] Shutdown Tempesta DB Apr 26 02:03:21 192.168.122.209 [35951.803377] End test: cache.test_cache.TestCacheResponseWithTrailersH2.test_hbh_headers_mix_GET Apr 26 02:03:21 192.168.122.209 [35951.814962] Start test: cache.test_cache.TestCacheResponseWithTrailersH2.test_hbh_headers_mix_HEAD Apr 26 02:03:22 192.168.122.209 [35953.007726] [tdb] Start Tempesta DB Apr 26 02:03:22 192.168.122.209 [35953.155463] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:03:24 192.168.122.209 [35954.745111] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35954.745111] Maybe that's fine, but it's worth checking the [35954.745111] config - if there is no relations between the [35954.745111] names, then host name confusion attack is possible. Apr 26 02:03:24 192.168.122.209 [35954.776822] [tempesta fw] Configuration processing is completed. Apr 26 02:03:24 192.168.122.209 [35954.827310] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:03:24 192.168.122.209 [35955.245502] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:03:25 192.168.122.209 [35955.271448] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:03:25 192.168.122.209 [35955.297044] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:03:25 192.168.122.209 [35955.348687] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:03:25 192.168.122.209 [35955.350407] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:03:25 192.168.122.209 [35955.388615] [tempesta fw] Tempesta FW is ready Apr 26 02:03:25 192.168.122.209 [35955.557232] [tempesta fw] Warning: Parser error: state=Resp_HdrConnectionV input(-8)=0x6b('ection: keep-alive [35955.557232] X-Token1: value1 [35955.557232] [35955.557232] ') data_len=331 off=299 Apr 26 02:03:25 192.168.122.209 [35955.559692] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 02:03:25 192.168.122.209 [35956.025306] [tdb] Close table 'client0.tdb' Apr 26 02:03:25 192.168.122.209 [35956.207862] [tdb] Close table 'sessions0.tdb' Apr 26 02:03:29 192.168.122.209 [35959.426120] [tdb] Close table 'cache0.tdb' Apr 26 02:03:29 192.168.122.209 [35959.666500] [tdb] Close table 'filter0.tdb' Apr 26 02:03:29 192.168.122.209 [35959.666941] [tempesta fw] modules are stopped Apr 26 02:03:29 192.168.122.209 [35959.866091] [tempesta fw] exiting... Apr 26 02:03:29 192.168.122.209 [35960.030525] [tdb] Shutdown Tempesta DB Apr 26 02:03:30 192.168.122.209 [35960.286016] End test: cache.test_cache.TestCacheResponseWithTrailersH2.test_hbh_headers_mix_HEAD Apr 26 02:03:30 192.168.122.209 [35960.296038] Start test: cache.test_cache.TestCacheResponseWithTrailersH2.test_same_hdr_and_trailer_head_to_get Apr 26 02:03:31 192.168.122.209 [35961.443495] [tdb] Start Tempesta DB Apr 26 02:03:31 192.168.122.209 [35961.593763] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:03:32 192.168.122.209 [35963.218425] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35963.218425] Maybe that's fine, but it's worth checking the [35963.218425] config - if there is no relations between the [35963.218425] names, then host name confusion attack is possible. Apr 26 02:03:33 192.168.122.209 [35963.268743] [tempesta fw] Configuration processing is completed. Apr 26 02:03:33 192.168.122.209 [35963.323449] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:03:33 192.168.122.209 [35963.752230] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:03:33 192.168.122.209 [35963.778561] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:03:33 192.168.122.209 [35963.806535] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:03:33 192.168.122.209 [35963.860789] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:03:33 192.168.122.209 [35963.862511] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:03:33 192.168.122.209 [35963.920724] [tempesta fw] Tempesta FW is ready Apr 26 02:03:34 192.168.122.209 [35964.562436] [tdb] Close table 'client0.tdb' Apr 26 02:03:34 192.168.122.209 [35964.752455] [tdb] Close table 'sessions0.tdb' Apr 26 02:03:37 192.168.122.209 [35967.962344] [tdb] Close table 'cache0.tdb' Apr 26 02:03:37 192.168.122.209 [35968.187341] [tdb] Close table 'filter0.tdb' Apr 26 02:03:37 192.168.122.209 [35968.187776] [tempesta fw] modules are stopped Apr 26 02:03:38 192.168.122.209 [35968.404021] [tempesta fw] exiting... Apr 26 02:03:38 192.168.122.209 [35968.551263] [tdb] Shutdown Tempesta DB Apr 26 02:03:38 192.168.122.209 [35968.766131] End test: cache.test_cache.TestCacheResponseWithTrailersH2.test_same_hdr_and_trailer_head_to_get Apr 26 02:03:38 192.168.122.209 [35968.784580] Start test: cache.test_cache.TestCacheResponseWithTrailersH2.test_same_hdr_and_trailer_head_to_get_multiple_1 Apr 26 02:03:39 192.168.122.209 [35969.991743] [tdb] Start Tempesta DB Apr 26 02:03:39 192.168.122.209 [35970.142381] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:03:41 192.168.122.209 [35971.766505] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35971.766505] Maybe that's fine, but it's worth checking the [35971.766505] config - if there is no relations between the [35971.766505] names, then host name confusion attack is possible. Apr 26 02:03:41 192.168.122.209 [35971.829259] [tempesta fw] Configuration processing is completed. Apr 26 02:03:41 192.168.122.209 [35971.885514] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:03:42 192.168.122.209 [35972.309488] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:03:42 192.168.122.209 [35972.345273] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:03:42 192.168.122.209 [35972.372011] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:03:42 192.168.122.209 [35972.424895] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:03:42 192.168.122.209 [35972.426492] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:03:42 192.168.122.209 [35972.472844] [tempesta fw] Tempesta FW is ready Apr 26 02:03:42 192.168.122.209 [35973.066542] [tdb] Close table 'client0.tdb' Apr 26 02:03:43 192.168.122.209 [35973.258927] [tdb] Close table 'sessions0.tdb' Apr 26 02:03:46 192.168.122.209 [35976.457854] [tdb] Close table 'cache0.tdb' Apr 26 02:03:46 192.168.122.209 [35976.699651] [tdb] Close table 'filter0.tdb' Apr 26 02:03:46 192.168.122.209 [35976.700090] [tempesta fw] modules are stopped Apr 26 02:03:46 192.168.122.209 [35976.881958] [tempesta fw] exiting... Apr 26 02:03:46 192.168.122.209 [35977.028850] [tdb] Shutdown Tempesta DB Apr 26 02:03:46 192.168.122.209 [35977.251112] End test: cache.test_cache.TestCacheResponseWithTrailersH2.test_same_hdr_and_trailer_head_to_get_multiple_1 Apr 26 02:03:47 192.168.122.209 [35977.270801] Start test: cache.test_cache.TestCacheResponseWithTrailersH2.test_same_hdr_and_trailer_head_to_get_multiple_2 Apr 26 02:03:48 192.168.122.209 [35978.428444] [tdb] Start Tempesta DB Apr 26 02:03:48 192.168.122.209 [35978.589648] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:03:49 192.168.122.209 [35980.134744] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35980.134744] Maybe that's fine, but it's worth checking the [35980.134744] config - if there is no relations between the [35980.134744] names, then host name confusion attack is possible. Apr 26 02:03:49 192.168.122.209 [35980.181257] [tempesta fw] Configuration processing is completed. Apr 26 02:03:49 192.168.122.209 [35980.241085] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:03:50 192.168.122.209 [35980.674389] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:03:50 192.168.122.209 [35980.701439] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:03:50 192.168.122.209 [35980.729661] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:03:50 192.168.122.209 [35980.781017] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:03:50 192.168.122.209 [35980.782758] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:03:50 192.168.122.209 [35980.836958] [tempesta fw] Tempesta FW is ready Apr 26 02:03:51 192.168.122.209 [35981.443127] [tdb] Close table 'client0.tdb' Apr 26 02:03:51 192.168.122.209 [35981.651949] [tdb] Close table 'sessions0.tdb' Apr 26 02:03:54 192.168.122.209 [35984.848404] [tdb] Close table 'cache0.tdb' Apr 26 02:03:54 192.168.122.209 [35985.084886] [tdb] Close table 'filter0.tdb' Apr 26 02:03:54 192.168.122.209 [35985.085319] [tempesta fw] modules are stopped Apr 26 02:03:55 192.168.122.209 [35985.297193] [tempesta fw] exiting... Apr 26 02:03:55 192.168.122.209 [35985.462262] [tdb] Shutdown Tempesta DB Apr 26 02:03:55 192.168.122.209 [35985.700917] End test: cache.test_cache.TestCacheResponseWithTrailersH2.test_same_hdr_and_trailer_head_to_get_multiple_2 Apr 26 02:03:55 192.168.122.209 [35985.718591] Start test: cache.test_cache.TestCacheResponseWithTrailersH2.test_same_trailer_head_to_get Apr 26 02:03:56 192.168.122.209 [35986.904206] [tdb] Start Tempesta DB Apr 26 02:03:56 192.168.122.209 [35987.045471] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:03:58 192.168.122.209 [35988.674757] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35988.674757] Maybe that's fine, but it's worth checking the [35988.674757] config - if there is no relations between the [35988.674757] names, then host name confusion attack is possible. Apr 26 02:03:58 192.168.122.209 [35988.737072] [tempesta fw] Configuration processing is completed. Apr 26 02:03:58 192.168.122.209 [35988.792302] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:03:58 192.168.122.209 [35989.210127] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:03:59 192.168.122.209 [35989.267237] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:03:59 192.168.122.209 [35989.293689] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:03:59 192.168.122.209 [35989.349105] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:03:59 192.168.122.209 [35989.350852] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:03:59 192.168.122.209 [35989.397087] [tempesta fw] Tempesta FW is ready Apr 26 02:03:59 192.168.122.209 [35990.029117] [tdb] Close table 'client0.tdb' Apr 26 02:03:59 192.168.122.209 [35990.218276] [tdb] Close table 'sessions0.tdb' Apr 26 02:04:03 192.168.122.209 [35993.388016] [tdb] Close table 'cache0.tdb' Apr 26 02:04:03 192.168.122.209 [35993.627464] [tdb] Close table 'filter0.tdb' Apr 26 02:04:03 192.168.122.209 [35993.627901] [tempesta fw] modules are stopped Apr 26 02:04:03 192.168.122.209 [35993.837334] [tempesta fw] exiting... Apr 26 02:04:03 192.168.122.209 [35994.002587] [tdb] Shutdown Tempesta DB Apr 26 02:04:04 192.168.122.209 [35994.268322] End test: cache.test_cache.TestCacheResponseWithTrailersH2.test_same_trailer_head_to_get Apr 26 02:04:04 192.168.122.209 [35994.281993] Start test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_GET_GET Apr 26 02:04:05 192.168.122.209 [35995.525634] [tdb] Start Tempesta DB Apr 26 02:04:05 192.168.122.209 [35995.666539] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:04:07 192.168.122.209 [35997.270860] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [35997.270860] Maybe that's fine, but it's worth checking the [35997.270860] config - if there is no relations between the [35997.270860] names, then host name confusion attack is possible. Apr 26 02:04:07 192.168.122.209 [35997.321487] [tempesta fw] Configuration processing is completed. Apr 26 02:04:07 192.168.122.209 [35997.371879] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:04:07 192.168.122.209 [35997.795504] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:04:07 192.168.122.209 [35997.822765] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:04:07 192.168.122.209 [35997.848805] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:04:07 192.168.122.209 [35997.929258] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:04:07 192.168.122.209 [35997.930981] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:04:07 192.168.122.209 [35997.969169] [tempesta fw] Tempesta FW is ready Apr 26 02:04:08 192.168.122.209 [35998.566159] [tdb] Close table 'client0.tdb' Apr 26 02:04:08 192.168.122.209 [35998.758936] [tdb] Close table 'sessions0.tdb' Apr 26 02:04:11 192.168.122.209 [36001.922961] [tdb] Close table 'cache0.tdb' Apr 26 02:04:11 192.168.122.209 [36002.182613] [tdb] Close table 'filter0.tdb' Apr 26 02:04:11 192.168.122.209 [36002.183055] [tempesta fw] modules are stopped Apr 26 02:04:12 192.168.122.209 [36002.374899] [tempesta fw] exiting... Apr 26 02:04:12 192.168.122.209 [36002.563559] [tdb] Shutdown Tempesta DB Apr 26 02:04:12 192.168.122.209 [36002.806836] End test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_GET_GET Apr 26 02:04:12 192.168.122.209 [36002.830527] Start test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_GET_HEAD Apr 26 02:04:13 192.168.122.209 [36004.041549] [tdb] Start Tempesta DB Apr 26 02:04:13 192.168.122.209 [36004.184734] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:04:15 192.168.122.209 [36005.802965] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36005.802965] Maybe that's fine, but it's worth checking the [36005.802965] config - if there is no relations between the [36005.802965] names, then host name confusion attack is possible. Apr 26 02:04:15 192.168.122.209 [36005.849688] [tempesta fw] Configuration processing is completed. Apr 26 02:04:15 192.168.122.209 [36005.939514] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:04:16 192.168.122.209 [36006.370229] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:04:16 192.168.122.209 [36006.397314] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:04:16 192.168.122.209 [36006.425711] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:04:16 192.168.122.209 [36006.473330] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:04:16 192.168.122.209 [36006.474534] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:04:16 192.168.122.209 [36006.521282] [tempesta fw] Tempesta FW is ready Apr 26 02:04:16 192.168.122.209 [36007.165133] [tdb] Close table 'client0.tdb' Apr 26 02:04:17 192.168.122.209 [36007.363955] [tdb] Close table 'sessions0.tdb' Apr 26 02:04:20 192.168.122.209 [36010.579681] [tdb] Close table 'cache0.tdb' Apr 26 02:04:20 192.168.122.209 [36010.801649] [tdb] Close table 'filter0.tdb' Apr 26 02:04:20 192.168.122.209 [36010.802089] [tempesta fw] modules are stopped Apr 26 02:04:20 192.168.122.209 [36010.998080] [tempesta fw] exiting... Apr 26 02:04:20 192.168.122.209 [36011.167326] [tdb] Shutdown Tempesta DB Apr 26 02:04:21 192.168.122.209 [36011.405577] End test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_GET_HEAD Apr 26 02:04:21 192.168.122.209 [36011.423506] Start test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_HEAD_GET Apr 26 02:04:22 192.168.122.209 [36012.630253] [tdb] Start Tempesta DB Apr 26 02:04:22 192.168.122.209 [36012.763483] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:04:24 192.168.122.209 [36014.295086] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36014.295086] Maybe that's fine, but it's worth checking the [36014.295086] config - if there is no relations between the [36014.295086] names, then host name confusion attack is possible. Apr 26 02:04:24 192.168.122.209 [36014.337723] [tempesta fw] Configuration processing is completed. Apr 26 02:04:24 192.168.122.209 [36014.412173] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:04:24 192.168.122.209 [36014.841432] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:04:24 192.168.122.209 [36014.867834] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:04:24 192.168.122.209 [36014.893873] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:04:24 192.168.122.209 [36014.949460] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:04:24 192.168.122.209 [36014.951185] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:04:24 192.168.122.209 [36014.997402] [tempesta fw] Tempesta FW is ready Apr 26 02:04:25 192.168.122.209 [36015.638969] [tdb] Close table 'client0.tdb' Apr 26 02:04:25 192.168.122.209 [36015.833561] [tdb] Close table 'sessions0.tdb' Apr 26 02:04:28 192.168.122.209 [36019.041006] [tdb] Close table 'cache0.tdb' Apr 26 02:04:29 192.168.122.209 [36019.258701] [tdb] Close table 'filter0.tdb' Apr 26 02:04:29 192.168.122.209 [36019.259137] [tempesta fw] modules are stopped Apr 26 02:04:29 192.168.122.209 [36019.465028] [tempesta fw] exiting... Apr 26 02:04:29 192.168.122.209 [36019.620263] [tdb] Shutdown Tempesta DB Apr 26 02:04:29 192.168.122.209 [36019.839025] End test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_HEAD_GET Apr 26 02:04:29 192.168.122.209 [36019.855497] Start test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_HEAD_HEAD Apr 26 02:04:30 192.168.122.209 [36021.081350] [tdb] Start Tempesta DB Apr 26 02:04:30 192.168.122.209 [36021.211333] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:04:32 192.168.122.209 [36022.827173] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36022.827173] Maybe that's fine, but it's worth checking the [36022.827173] config - if there is no relations between the [36022.827173] names, then host name confusion attack is possible. Apr 26 02:04:32 192.168.122.209 [36022.885515] [tempesta fw] Configuration processing is completed. Apr 26 02:04:32 192.168.122.209 [36022.936242] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:04:33 192.168.122.209 [36023.360954] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:04:33 192.168.122.209 [36023.387418] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:04:33 192.168.122.209 [36023.413463] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:04:33 192.168.122.209 [36023.465595] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:04:33 192.168.122.209 [36023.467348] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:04:33 192.168.122.209 [36023.517467] [tempesta fw] Tempesta FW is ready Apr 26 02:04:33 192.168.122.209 [36024.146035] [tdb] Close table 'client0.tdb' Apr 26 02:04:34 192.168.122.209 [36024.353149] [tdb] Close table 'sessions0.tdb' Apr 26 02:04:37 192.168.122.209 [36027.557842] [tdb] Close table 'cache0.tdb' Apr 26 02:04:37 192.168.122.209 [36027.800942] [tdb] Close table 'filter0.tdb' Apr 26 02:04:37 192.168.122.209 [36027.801378] [tempesta fw] modules are stopped Apr 26 02:04:37 192.168.122.209 [36027.986746] [tempesta fw] exiting... Apr 26 02:04:37 192.168.122.209 [36028.135498] [tdb] Shutdown Tempesta DB Apr 26 02:04:38 192.168.122.209 [36028.343219] End test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_HEAD_HEAD Apr 26 02:04:38 192.168.122.209 [36028.353976] Start test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_empty_body_head_to_get Apr 26 02:04:39 192.168.122.209 [36029.522857] [tdb] Start Tempesta DB Apr 26 02:04:39 192.168.122.209 [36029.678199] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:04:41 192.168.122.209 [36031.291350] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36031.291350] Maybe that's fine, but it's worth checking the [36031.291350] config - if there is no relations between the [36031.291350] names, then host name confusion attack is possible. Apr 26 02:04:41 192.168.122.209 [36031.357643] [tempesta fw] Configuration processing is completed. Apr 26 02:04:41 192.168.122.209 [36031.448422] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:04:41 192.168.122.209 [36031.886783] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:04:41 192.168.122.209 [36031.913525] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:04:41 192.168.122.209 [36031.940465] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:04:41 192.168.122.209 [36032.009749] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:04:41 192.168.122.209 [36032.011459] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:04:41 192.168.122.209 [36032.053601] [tempesta fw] Tempesta FW is ready Apr 26 02:04:42 192.168.122.209 [36032.690223] [tdb] Close table 'client0.tdb' Apr 26 02:04:42 192.168.122.209 [36032.880484] [tdb] Close table 'sessions0.tdb' Apr 26 02:04:45 192.168.122.209 [36036.146866] [tdb] Close table 'cache0.tdb' Apr 26 02:04:46 192.168.122.209 [36036.380052] [tdb] Close table 'filter0.tdb' Apr 26 02:04:46 192.168.122.209 [36036.380474] [tempesta fw] modules are stopped Apr 26 02:04:46 192.168.122.209 [36036.599094] [tempesta fw] exiting... Apr 26 02:04:46 192.168.122.209 [36036.729363] [tdb] Shutdown Tempesta DB Apr 26 02:04:46 192.168.122.209 [36036.983212] End test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_empty_body_head_to_get Apr 26 02:04:46 192.168.122.209 [36037.004531] Start test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_hbh_headers_hbp_GET Apr 26 02:04:47 192.168.122.209 [36038.157439] [tdb] Start Tempesta DB Apr 26 02:04:48 192.168.122.209 [36038.294120] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:04:49 192.168.122.209 [36039.871410] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36039.871410] Maybe that's fine, but it's worth checking the [36039.871410] config - if there is no relations between the [36039.871410] names, then host name confusion attack is possible. Apr 26 02:04:49 192.168.122.209 [36039.929737] [tempesta fw] Configuration processing is completed. Apr 26 02:04:49 192.168.122.209 [36039.981633] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:04:50 192.168.122.209 [36040.443298] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:04:50 192.168.122.209 [36040.471350] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:04:50 192.168.122.209 [36040.499019] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:04:50 192.168.122.209 [36040.589770] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:04:50 192.168.122.209 [36040.591534] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:04:50 192.168.122.209 [36040.637726] [tempesta fw] Tempesta FW is ready Apr 26 02:04:50 192.168.122.209 [36040.793402] [tempesta fw] Warning: Parser error: state=Resp_HdrConnectionV input(-8)=0x6b('ection: keep-alive [36040.793402] Keep-Alive: timeout=5, max=1') data_len=347 off=301 Apr 26 02:04:50 192.168.122.209 [36040.795155] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 02:04:51 192.168.122.209 [36041.278946] [tdb] Close table 'client0.tdb' Apr 26 02:04:51 192.168.122.209 [36041.490832] [tdb] Close table 'sessions0.tdb' Apr 26 02:04:54 192.168.122.209 [36044.676807] [tdb] Close table 'cache0.tdb' Apr 26 02:04:54 192.168.122.209 [36044.915881] [tdb] Close table 'filter0.tdb' Apr 26 02:04:54 192.168.122.209 [36044.916313] [tempesta fw] modules are stopped Apr 26 02:04:54 192.168.122.209 [36045.088735] [tempesta fw] exiting... Apr 26 02:04:54 192.168.122.209 [36045.224445] [tdb] Shutdown Tempesta DB Apr 26 02:04:55 192.168.122.209 [36045.464143] End test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_hbh_headers_hbp_GET Apr 26 02:04:55 192.168.122.209 [36045.486225] Start test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_hbh_headers_hbp_HEAD Apr 26 02:04:56 192.168.122.209 [36046.727009] [tdb] Start Tempesta DB Apr 26 02:04:56 192.168.122.209 [36046.866849] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:04:58 192.168.122.209 [36048.439510] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36048.439510] Maybe that's fine, but it's worth checking the [36048.439510] config - if there is no relations between the [36048.439510] names, then host name confusion attack is possible. Apr 26 02:04:58 192.168.122.209 [36048.494145] [tempesta fw] Configuration processing is completed. Apr 26 02:04:58 192.168.122.209 [36048.552070] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:04:58 192.168.122.209 [36048.972183] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:04:58 192.168.122.209 [36049.007914] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:04:58 192.168.122.209 [36049.033534] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:04:58 192.168.122.209 [36049.081928] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:04:58 192.168.122.209 [36049.083672] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:04:58 192.168.122.209 [36049.129829] [tempesta fw] Tempesta FW is ready Apr 26 02:04:59 192.168.122.209 [36049.285885] [tempesta fw] Warning: Parser error: state=Resp_HdrConnectionV input(-8)=0x6b('ection: keep-alive [36049.285885] Keep-Alive: timeout=5, max=1') data_len=347 off=301 Apr 26 02:04:59 192.168.122.209 [36049.287805] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 02:04:59 192.168.122.209 [36049.778820] [tdb] Close table 'client0.tdb' Apr 26 02:04:59 192.168.122.209 [36049.961593] [tdb] Close table 'sessions0.tdb' Apr 26 02:05:02 192.168.122.209 [36053.243460] [tdb] Close table 'cache0.tdb' Apr 26 02:05:03 192.168.122.209 [36053.501574] [tdb] Close table 'filter0.tdb' Apr 26 02:05:03 192.168.122.209 [36053.502067] [tempesta fw] modules are stopped Apr 26 02:05:03 192.168.122.209 [36053.695033] [tempesta fw] exiting... Apr 26 02:05:03 192.168.122.209 [36053.843683] [tdb] Shutdown Tempesta DB Apr 26 02:05:03 192.168.122.209 [36054.095241] End test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_hbh_headers_hbp_HEAD Apr 26 02:05:03 192.168.122.209 [36054.116239] Start test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_hbh_headers_mix_GET Apr 26 02:05:05 192.168.122.209 [36055.288230] [tdb] Start Tempesta DB Apr 26 02:05:05 192.168.122.209 [36055.437778] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:05:06 192.168.122.209 [36057.075620] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36057.075620] Maybe that's fine, but it's worth checking the [36057.075620] config - if there is no relations between the [36057.075620] names, then host name confusion attack is possible. Apr 26 02:05:06 192.168.122.209 [36057.126271] [tempesta fw] Configuration processing is completed. Apr 26 02:05:06 192.168.122.209 [36057.216303] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:05:07 192.168.122.209 [36057.646496] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:05:07 192.168.122.209 [36057.672916] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:05:07 192.168.122.209 [36057.700765] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:05:07 192.168.122.209 [36057.749992] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:05:07 192.168.122.209 [36057.751716] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:05:07 192.168.122.209 [36057.789954] [tempesta fw] Tempesta FW is ready Apr 26 02:05:07 192.168.122.209 [36057.941069] [tempesta fw] Warning: Parser error: state=Resp_HdrConnectionV input(-8)=0x6b('ection: keep-alive [36057.941069] X-Token1: value1 [36057.941069] [36057.941069] ') data_len=331 off=299 Apr 26 02:05:07 192.168.122.209 [36057.945913] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 02:05:08 192.168.122.209 [36058.395837] [tdb] Close table 'client0.tdb' Apr 26 02:05:08 192.168.122.209 [36058.588673] [tdb] Close table 'sessions0.tdb' Apr 26 02:05:11 192.168.122.209 [36061.742724] [tdb] Close table 'cache0.tdb' Apr 26 02:05:11 192.168.122.209 [36061.985223] [tdb] Close table 'filter0.tdb' Apr 26 02:05:11 192.168.122.209 [36061.985683] [tempesta fw] modules are stopped Apr 26 02:05:11 192.168.122.209 [36062.202352] [tempesta fw] exiting... Apr 26 02:05:12 192.168.122.209 [36062.384802] [tdb] Shutdown Tempesta DB Apr 26 02:05:12 192.168.122.209 [36062.624308] End test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_hbh_headers_mix_GET Apr 26 02:05:12 192.168.122.209 [36062.641858] Start test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_hbh_headers_mix_HEAD Apr 26 02:05:13 192.168.122.209 [36063.850766] [tdb] Start Tempesta DB Apr 26 02:05:13 192.168.122.209 [36064.015213] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:05:15 192.168.122.209 [36065.579788] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36065.579788] Maybe that's fine, but it's worth checking the [36065.579788] config - if there is no relations between the [36065.579788] names, then host name confusion attack is possible. Apr 26 02:05:15 192.168.122.209 [36065.638160] [tempesta fw] Configuration processing is completed. Apr 26 02:05:15 192.168.122.209 [36065.692254] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:05:15 192.168.122.209 [36066.156749] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:05:15 192.168.122.209 [36066.185334] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:05:15 192.168.122.209 [36066.213435] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:05:15 192.168.122.209 [36066.258120] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:05:16 192.168.122.209 [36066.259882] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:05:16 192.168.122.209 [36066.314048] [tempesta fw] Tempesta FW is ready Apr 26 02:05:16 192.168.122.209 [36066.451893] [tempesta fw] Warning: Parser error: state=Resp_HdrConnectionV input(-8)=0x6b('ection: keep-alive [36066.451893] X-Token1: value1 [36066.451893] [36066.451893] ') data_len=331 off=299 Apr 26 02:05:16 192.168.122.209 [36066.453540] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 02:05:16 192.168.122.209 [36066.917599] [tdb] Close table 'client0.tdb' Apr 26 02:05:16 192.168.122.209 [36067.129432] [tdb] Close table 'sessions0.tdb' Apr 26 02:05:20 192.168.122.209 [36070.373108] [tdb] Close table 'cache0.tdb' Apr 26 02:05:20 192.168.122.209 [36070.605758] [tdb] Close table 'filter0.tdb' Apr 26 02:05:20 192.168.122.209 [36070.606614] [tempesta fw] modules are stopped Apr 26 02:05:20 192.168.122.209 [36070.802201] [tempesta fw] exiting... Apr 26 02:05:20 192.168.122.209 [36070.949508] [tdb] Shutdown Tempesta DB Apr 26 02:05:20 192.168.122.209 [36071.167357] End test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_hbh_headers_mix_HEAD Apr 26 02:05:20 192.168.122.209 [36071.180850] Start test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_same_hdr_and_trailer_head_to_get Apr 26 02:05:22 192.168.122.209 [36072.457416] [tdb] Start Tempesta DB Apr 26 02:05:22 192.168.122.209 [36072.623060] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:05:23 192.168.122.209 [36074.235962] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36074.235962] Maybe that's fine, but it's worth checking the [36074.235962] config - if there is no relations between the [36074.235962] names, then host name confusion attack is possible. Apr 26 02:05:24 192.168.122.209 [36074.286567] [tempesta fw] Configuration processing is completed. Apr 26 02:05:24 192.168.122.209 [36074.347398] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:05:24 192.168.122.209 [36074.816858] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:05:24 192.168.122.209 [36074.846753] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:05:24 192.168.122.209 [36074.877488] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:05:24 192.168.122.209 [36074.926229] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:05:24 192.168.122.209 [36074.927492] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:05:24 192.168.122.209 [36074.962113] [tempesta fw] Tempesta FW is ready Apr 26 02:05:25 192.168.122.209 [36075.605301] [tdb] Close table 'client0.tdb' Apr 26 02:05:25 192.168.122.209 [36075.801214] [tdb] Close table 'sessions0.tdb' Apr 26 02:05:28 192.168.122.209 [36078.958933] [tdb] Close table 'cache0.tdb' Apr 26 02:05:28 192.168.122.209 [36079.187333] [tdb] Close table 'filter0.tdb' Apr 26 02:05:28 192.168.122.209 [36079.187777] [tempesta fw] modules are stopped Apr 26 02:05:29 192.168.122.209 [36079.375805] [tempesta fw] exiting... Apr 26 02:05:29 192.168.122.209 [36079.523866] [tdb] Shutdown Tempesta DB Apr 26 02:05:29 192.168.122.209 [36079.740761] End test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_same_hdr_and_trailer_head_to_get Apr 26 02:05:29 192.168.122.209 [36079.771184] Start test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_same_hdr_and_trailer_head_to_get_multiple_1 Apr 26 02:05:30 192.168.122.209 [36080.939000] [tdb] Start Tempesta DB Apr 26 02:05:30 192.168.122.209 [36081.090677] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:05:32 192.168.122.209 [36082.724189] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36082.724189] Maybe that's fine, but it's worth checking the [36082.724189] config - if there is no relations between the [36082.724189] names, then host name confusion attack is possible. Apr 26 02:05:32 192.168.122.209 [36082.770708] [tempesta fw] Configuration processing is completed. Apr 26 02:05:32 192.168.122.209 [36082.821160] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:05:33 192.168.122.209 [36083.274437] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:05:33 192.168.122.209 [36083.305082] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:05:33 192.168.122.209 [36083.337113] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:05:33 192.168.122.209 [36083.386343] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:05:33 192.168.122.209 [36083.388084] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:05:33 192.168.122.209 [36083.426288] [tempesta fw] Tempesta FW is ready Apr 26 02:05:33 192.168.122.209 [36084.007289] [tdb] Close table 'client0.tdb' Apr 26 02:05:33 192.168.122.209 [36084.228148] [tdb] Close table 'sessions0.tdb' Apr 26 02:05:37 192.168.122.209 [36087.434345] [tdb] Close table 'cache0.tdb' Apr 26 02:05:37 192.168.122.209 [36087.679576] [tdb] Close table 'filter0.tdb' Apr 26 02:05:37 192.168.122.209 [36087.680016] [tempesta fw] modules are stopped Apr 26 02:05:37 192.168.122.209 [36087.903374] [tempesta fw] exiting... Apr 26 02:05:37 192.168.122.209 [36088.039141] [tdb] Shutdown Tempesta DB Apr 26 02:05:38 192.168.122.209 [36088.275916] End test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_same_hdr_and_trailer_head_to_get_multiple_1 Apr 26 02:05:38 192.168.122.209 [36088.300224] Start test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_same_hdr_and_trailer_head_to_get_multiple_2 Apr 26 02:05:39 192.168.122.209 [36089.448282] [tdb] Start Tempesta DB Apr 26 02:05:39 192.168.122.209 [36089.612914] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:05:40 192.168.122.209 [36091.232044] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36091.232044] Maybe that's fine, but it's worth checking the [36091.232044] config - if there is no relations between the [36091.232044] names, then host name confusion attack is possible. Apr 26 02:05:41 192.168.122.209 [36091.274711] [tempesta fw] Configuration processing is completed. Apr 26 02:05:41 192.168.122.209 [36091.356109] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:05:41 192.168.122.209 [36091.784798] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:05:41 192.168.122.209 [36091.811536] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:05:41 192.168.122.209 [36091.838726] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:05:41 192.168.122.209 [36091.890454] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:05:41 192.168.122.209 [36091.892187] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:05:41 192.168.122.209 [36091.958398] [tempesta fw] Tempesta FW is ready Apr 26 02:05:42 192.168.122.209 [36092.540640] [tdb] Close table 'client0.tdb' Apr 26 02:05:42 192.168.122.209 [36092.742120] [tdb] Close table 'sessions0.tdb' Apr 26 02:05:45 192.168.122.209 [36095.960102] [tdb] Close table 'cache0.tdb' Apr 26 02:05:45 192.168.122.209 [36096.204232] [tdb] Close table 'filter0.tdb' Apr 26 02:05:45 192.168.122.209 [36096.204673] [tempesta fw] modules are stopped Apr 26 02:05:46 192.168.122.209 [36096.397648] [tempesta fw] exiting... Apr 26 02:05:46 192.168.122.209 [36096.543485] [tdb] Shutdown Tempesta DB Apr 26 02:05:46 192.168.122.209 [36096.765247] End test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_same_hdr_and_trailer_head_to_get_multiple_2 Apr 26 02:05:46 192.168.122.209 [36096.783238] Start test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_same_trailer_head_to_get Apr 26 02:05:47 192.168.122.209 [36098.005724] [tdb] Start Tempesta DB Apr 26 02:05:47 192.168.122.209 [36098.148296] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:05:49 192.168.122.209 [36099.788177] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36099.788177] Maybe that's fine, but it's worth checking the [36099.788177] config - if there is no relations between the [36099.788177] names, then host name confusion attack is possible. Apr 26 02:05:49 192.168.122.209 [36099.854688] [tempesta fw] Configuration processing is completed. Apr 26 02:05:49 192.168.122.209 [36099.911362] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:05:50 192.168.122.209 [36100.354448] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:05:50 192.168.122.209 [36100.382131] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:05:50 192.168.122.209 [36100.409276] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:05:50 192.168.122.209 [36100.462532] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:05:50 192.168.122.209 [36100.464189] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:05:50 192.168.122.209 [36100.506515] [tempesta fw] Tempesta FW is ready Apr 26 02:05:50 192.168.122.209 [36101.115346] [tdb] Close table 'client0.tdb' Apr 26 02:05:51 192.168.122.209 [36101.347091] [tdb] Close table 'sessions0.tdb' Apr 26 02:05:54 192.168.122.209 [36104.559104] [tdb] Close table 'cache0.tdb' Apr 26 02:05:54 192.168.122.209 [36104.791086] [tdb] Close table 'filter0.tdb' Apr 26 02:05:54 192.168.122.209 [36104.791517] [tempesta fw] modules are stopped Apr 26 02:05:54 192.168.122.209 [36104.966878] [tempesta fw] exiting... Apr 26 02:05:54 192.168.122.209 [36105.100065] [tdb] Shutdown Tempesta DB Apr 26 02:05:55 192.168.122.209 [36105.328966] End test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_same_trailer_head_to_get Apr 26 02:05:55 192.168.122.209 [36105.343022] Start test: cache.test_cache.TestCacheUseStaleCfg.test_cache_use_stale_config_dupl Apr 26 02:05:56 192.168.122.209 [36106.565278] [tdb] Start Tempesta DB Apr 26 02:05:56 192.168.122.209 [36106.717026] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:05:57 192.168.122.209 [36108.164311] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36108.164311] Maybe that's fine, but it's worth checking the [36108.164311] config - if there is no relations between the [36108.164311] names, then host name confusion attack is possible. Apr 26 02:05:57 192.168.122.209 [36108.238712] [tempesta fw] ERROR: duplicate entry: 'cache_use_stale', only one such entry is allowed. Apr 26 02:05:57 192.168.122.209 [36108.241248] [tempesta fw] ERROR: configuration parsing error: [36108.241248] 15: cache_use_stale 5*;cache_use_stale 4*; [36108.241248] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 02:05:57 192.168.122.209 [36108.245770] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 02:05:58 192.168.122.209 [36108.454690] [tempesta fw] exiting... Apr 26 02:05:58 192.168.122.209 [36108.583841] [tdb] Shutdown Tempesta DB Apr 26 02:05:58 192.168.122.209 [36109.195684] End test: cache.test_cache.TestCacheUseStaleCfg.test_cache_use_stale_config_dupl Apr 26 02:05:58 192.168.122.209 [36109.214955] Start test: cache.test_cache.TestCacheUseStaleCfg.test_cache_use_stale_config_wrong_code Apr 26 02:06:00 192.168.122.209 [36110.322461] [tdb] Start Tempesta DB Apr 26 02:06:00 192.168.122.209 [36110.488861] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:06:00 192.168.122.209 [36111.008393] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36111.008393] Maybe that's fine, but it's worth checking the [36111.008393] config - if there is no relations between the [36111.008393] names, then host name confusion attack is possible. Apr 26 02:06:00 192.168.122.209 [36111.078866] [tempesta fw] ERROR: Please specify status code above than 399. Apr 26 02:06:00 192.168.122.209 [36111.078878] [tempesta fw] ERROR: configuration parsing error: [36111.078878] 15: cache_use_stale 200; [36111.078878] ^^^^^^^^^^^^^^^^^^^^ Apr 26 02:06:00 192.168.122.209 [36111.084548] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 02:06:01 192.168.122.209 [36111.278286] [tempesta fw] exiting... Apr 26 02:06:01 192.168.122.209 [36111.392806] [tdb] Shutdown Tempesta DB Apr 26 02:06:01 192.168.122.209 [36111.906200] End test: cache.test_cache.TestCacheUseStaleCfg.test_cache_use_stale_config_wrong_code Apr 26 02:06:01 192.168.122.209 [36111.925464] Start test: cache.test_cache.TestCacheUseStaleCfg.test_cache_use_stale_config_wrong_mask Apr 26 02:06:02 192.168.122.209 [36113.001667] [tdb] Start Tempesta DB Apr 26 02:06:02 192.168.122.209 [36113.156524] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:06:03 192.168.122.209 [36113.740438] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36113.740438] Maybe that's fine, but it's worth checking the [36113.740438] config - if there is no relations between the [36113.740438] names, then host name confusion attack is possible. Apr 26 02:06:03 192.168.122.209 [36113.804148] [tempesta fw] ERROR: cache_use_stale Unsupported argument "3*" Apr 26 02:06:03 192.168.122.209 [36113.804159] [tempesta fw] ERROR: configuration parsing error: [36113.804159] 15: cache_use_stale 3*; [36113.804159] ^^^^^^^^^^^^^^^^^^^ Apr 26 02:06:03 192.168.122.209 [36113.809654] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 02:06:03 192.168.122.209 [36113.980221] [tempesta fw] exiting... Apr 26 02:06:03 192.168.122.209 [36114.109081] [tdb] Shutdown Tempesta DB Apr 26 02:06:04 192.168.122.209 [36114.603800] End test: cache.test_cache.TestCacheUseStaleCfg.test_cache_use_stale_config_wrong_mask Apr 26 02:06:04 192.168.122.209 [36114.625879] Start test: cache.test_cache.TestCacheVhost.test_h2 Apr 26 02:06:05 192.168.122.209 [36115.682650] [tdb] Start Tempesta DB Apr 26 02:06:05 192.168.122.209 [36115.825244] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:06:06 192.168.122.209 [36116.584777] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [36116.584777] Maybe that's fine, but it's worth checking the [36116.584777] config - if there is no relations between the [36116.584777] names, then host name confusion attack is possible. Apr 26 02:06:06 192.168.122.209 [36116.702827] [tempesta fw] Configuration processing is completed. Apr 26 02:06:06 192.168.122.209 [36116.755051] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:06:06 192.168.122.209 [36117.173068] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:06:06 192.168.122.209 [36117.199163] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:06:06 192.168.122.209 [36117.229704] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:06:07 192.168.122.209 [36117.302867] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:06:07 192.168.122.209 [36117.342722] [tempesta fw] Tempesta FW is ready Apr 26 02:06:08 192.168.122.209 [36118.371693] [tdb] Close table 'client0.tdb' Apr 26 02:06:08 192.168.122.209 [36118.572223] [tdb] Close table 'sessions0.tdb' Apr 26 02:06:11 192.168.122.209 [36121.714735] [tdb] Close table 'cache0.tdb' Apr 26 02:06:11 192.168.122.209 [36121.946419] [tdb] Close table 'filter0.tdb' Apr 26 02:06:11 192.168.122.209 [36121.946868] [tempesta fw] modules are stopped Apr 26 02:06:11 192.168.122.209 [36122.234287] [tempesta fw] exiting... Apr 26 02:06:12 192.168.122.209 [36122.406570] [tdb] Shutdown Tempesta DB Apr 26 02:06:12 192.168.122.209 [36122.620502] End test: cache.test_cache.TestCacheVhost.test_h2 Apr 26 02:06:12 192.168.122.209 [36122.643684] Start test: cache.test_cache.TestCacheVhost.test_https Apr 26 02:06:13 192.168.122.209 [36123.865550] [tdb] Start Tempesta DB Apr 26 02:06:13 192.168.122.209 [36124.014311] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:06:15 192.168.122.209 [36125.858069] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [36125.858069] Maybe that's fine, but it's worth checking the [36125.858069] config - if there is no relations between the [36125.858069] names, then host name confusion attack is possible. Apr 26 02:06:15 192.168.122.209 [36125.978939] [tempesta fw] Configuration processing is completed. Apr 26 02:06:15 192.168.122.209 [36126.060848] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:06:16 192.168.122.209 [36126.480750] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:06:16 192.168.122.209 [36126.506867] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:06:16 192.168.122.209 [36126.532929] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:06:16 192.168.122.209 [36126.598886] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:06:16 192.168.122.209 [36126.638836] [tempesta fw] Tempesta FW is ready Apr 26 02:06:17 192.168.122.209 [36127.692174] [tdb] Close table 'client0.tdb' Apr 26 02:06:17 192.168.122.209 [36127.885561] [tdb] Close table 'sessions0.tdb' Apr 26 02:06:20 192.168.122.209 [36131.038900] [tdb] Close table 'cache0.tdb' Apr 26 02:06:21 192.168.122.209 [36131.296092] [tdb] Close table 'filter0.tdb' Apr 26 02:06:21 192.168.122.209 [36131.296537] [tempesta fw] modules are stopped Apr 26 02:06:21 192.168.122.209 [36131.590653] [tempesta fw] exiting... Apr 26 02:06:21 192.168.122.209 [36131.733591] [tdb] Shutdown Tempesta DB Apr 26 02:06:21 192.168.122.209 [36132.027585] End test: cache.test_cache.TestCacheVhost.test_https Apr 26 02:06:21 192.168.122.209 [36132.048176] Start test: cache.test_cache.TestChunkedResponse.test_cached_data_equal_to_original Apr 26 02:06:23 192.168.122.209 [36133.274054] [tdb] Start Tempesta DB Apr 26 02:06:23 192.168.122.209 [36133.430446] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:06:24 192.168.122.209 [36134.812262] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36134.812262] Maybe that's fine, but it's worth checking the [36134.812262] config - if there is no relations between the [36134.812262] names, then host name confusion attack is possible. Apr 26 02:06:24 192.168.122.209 [36134.959000] [tempesta fw] Configuration processing is completed. Apr 26 02:06:24 192.168.122.209 [36135.020788] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:06:25 192.168.122.209 [36135.437649] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:06:25 192.168.122.209 [36135.464251] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:06:25 192.168.122.209 [36135.489857] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:06:25 192.168.122.209 [36135.535001] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:06:25 192.168.122.209 [36135.536786] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:06:25 192.168.122.209 [36135.586949] [tempesta fw] Tempesta FW is ready Apr 26 02:06:26 192.168.122.209 [36136.326300] [tdb] Close table 'client0.tdb' Apr 26 02:06:26 192.168.122.209 [36136.509304] [tdb] Close table 'sessions0.tdb' Apr 26 02:06:29 192.168.122.209 [36139.713227] [tdb] Close table 'cache0.tdb' Apr 26 02:06:29 192.168.122.209 [36139.964124] [tdb] Close table 'filter0.tdb' Apr 26 02:06:29 192.168.122.209 [36139.964572] [tempesta fw] modules are stopped Apr 26 02:06:29 192.168.122.209 [36140.180917] [tempesta fw] exiting... Apr 26 02:06:30 192.168.122.209 [36140.334303] [tdb] Shutdown Tempesta DB Apr 26 02:06:30 192.168.122.209 [36140.567724] End test: cache.test_cache.TestChunkedResponse.test_cached_data_equal_to_original Apr 26 02:06:30 192.168.122.209 [36140.587653] Start test: cache.test_cache.TestChunkedResponse.test_h2_cached_data_equal_to_original Apr 26 02:06:31 192.168.122.209 [36141.832665] [tdb] Start Tempesta DB Apr 26 02:06:31 192.168.122.209 [36141.984910] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:06:33 192.168.122.209 [36143.344532] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36143.344532] Maybe that's fine, but it's worth checking the [36143.344532] config - if there is no relations between the [36143.344532] names, then host name confusion attack is possible. Apr 26 02:06:33 192.168.122.209 [36143.479095] [tempesta fw] Configuration processing is completed. Apr 26 02:06:33 192.168.122.209 [36143.536162] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:06:33 192.168.122.209 [36144.020884] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:06:33 192.168.122.209 [36144.055063] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:06:33 192.168.122.209 [36144.084601] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:06:33 192.168.122.209 [36144.123119] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:06:33 192.168.122.209 [36144.124905] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:06:33 192.168.122.209 [36144.171064] [tempesta fw] Tempesta FW is ready Apr 26 02:06:34 192.168.122.209 [36144.905432] [tdb] Close table 'client0.tdb' Apr 26 02:06:34 192.168.122.209 [36145.106363] [tdb] Close table 'sessions0.tdb' Apr 26 02:06:38 192.168.122.209 [36148.357063] [tdb] Close table 'cache0.tdb' Apr 26 02:06:38 192.168.122.209 [36148.612740] [tdb] Close table 'filter0.tdb' Apr 26 02:06:38 192.168.122.209 [36148.613208] [tempesta fw] modules are stopped Apr 26 02:06:38 192.168.122.209 [36148.795549] [tempesta fw] exiting... Apr 26 02:06:38 192.168.122.209 [36148.938037] [tdb] Shutdown Tempesta DB Apr 26 02:06:38 192.168.122.209 [36149.158820] End test: cache.test_cache.TestChunkedResponse.test_h2_cached_data_equal_to_original Apr 26 02:06:38 192.168.122.209 [36149.179499] Start test: cache.test_cache.TestH2CacheDisable.test_cache_disable Apr 26 02:06:40 192.168.122.209 [36150.349525] [tdb] Start Tempesta DB Apr 26 02:06:40 192.168.122.209 [36150.504925] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:06:42 192.168.122.209 [36152.276512] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36152.276512] Maybe that's fine, but it's worth checking the [36152.276512] config - if there is no relations between the [36152.276512] names, then host name confusion attack is possible. Apr 26 02:06:42 192.168.122.209 [36152.463233] [tempesta fw] Configuration processing is completed. Apr 26 02:06:42 192.168.122.209 [36152.519772] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:06:42 192.168.122.209 [36152.974366] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:06:42 192.168.122.209 [36153.002978] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:06:42 192.168.122.209 [36153.032798] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:06:42 192.168.122.209 [36153.079247] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:06:42 192.168.122.209 [36153.080614] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:06:42 192.168.122.209 [36153.119209] [tempesta fw] Tempesta FW is ready Apr 26 02:06:43 192.168.122.209 [36153.749852] [tdb] Close table 'client0.tdb' Apr 26 02:06:43 192.168.122.209 [36153.943302] [tdb] Close table 'sessions0.tdb' Apr 26 02:06:46 192.168.122.209 [36157.167557] [tdb] Close table 'cache0.tdb' Apr 26 02:06:47 192.168.122.209 [36157.419304] [tdb] Close table 'filter0.tdb' Apr 26 02:06:47 192.168.122.209 [36157.419740] [tempesta fw] modules are stopped Apr 26 02:06:47 192.168.122.209 [36157.612908] [tempesta fw] exiting... Apr 26 02:06:47 192.168.122.209 [36157.765943] [tdb] Shutdown Tempesta DB Apr 26 02:06:47 192.168.122.209 [36157.974388] End test: cache.test_cache.TestH2CacheDisable.test_cache_disable Apr 26 02:06:47 192.168.122.209 [36157.993781] Start test: cache.test_cache.TestH2CacheDisable.test_cache_disable_0 Apr 26 02:06:48 192.168.122.209 [36159.193361] [tdb] Start Tempesta DB Apr 26 02:06:49 192.168.122.209 [36159.339975] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:06:50 192.168.122.209 [36161.064567] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36161.064567] Maybe that's fine, but it's worth checking the [36161.064567] config - if there is no relations between the [36161.064567] names, then host name confusion attack is possible. Apr 26 02:06:50 192.168.122.209 [36161.235368] [tempesta fw] Configuration processing is completed. Apr 26 02:06:51 192.168.122.209 [36161.289957] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:06:51 192.168.122.209 [36161.719680] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:06:51 192.168.122.209 [36161.745583] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:06:51 192.168.122.209 [36161.771911] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:06:51 192.168.122.209 [36161.811338] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:06:51 192.168.122.209 [36161.813079] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:06:51 192.168.122.209 [36161.851291] [tempesta fw] Tempesta FW is ready Apr 26 02:06:52 192.168.122.209 [36162.480142] [tdb] Close table 'client0.tdb' Apr 26 02:06:52 192.168.122.209 [36162.674525] [tdb] Close table 'sessions0.tdb' Apr 26 02:06:55 192.168.122.209 [36165.866052] [tdb] Close table 'cache0.tdb' Apr 26 02:06:55 192.168.122.209 [36166.105487] [tdb] Close table 'filter0.tdb' Apr 26 02:06:55 192.168.122.209 [36166.105925] [tempesta fw] modules are stopped Apr 26 02:06:56 192.168.122.209 [36166.320705] [tempesta fw] exiting... Apr 26 02:06:56 192.168.122.209 [36166.482279] [tdb] Shutdown Tempesta DB Apr 26 02:06:56 192.168.122.209 [36166.729144] End test: cache.test_cache.TestH2CacheDisable.test_cache_disable_0 Apr 26 02:06:56 192.168.122.209 [36166.746523] Start test: cache.test_cache.TestH2CacheDisable.test_cache_disable_1 Apr 26 02:06:57 192.168.122.209 [36167.939322] [tdb] Start Tempesta DB Apr 26 02:06:57 192.168.122.209 [36168.082324] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:06:59 192.168.122.209 [36169.752713] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36169.752713] Maybe that's fine, but it's worth checking the [36169.752713] config - if there is no relations between the [36169.752713] names, then host name confusion attack is possible. Apr 26 02:06:59 192.168.122.209 [36169.919488] [tempesta fw] Configuration processing is completed. Apr 26 02:06:59 192.168.122.209 [36169.968301] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:07:00 192.168.122.209 [36170.383112] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:07:00 192.168.122.209 [36170.408133] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:07:00 192.168.122.209 [36170.433596] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:07:00 192.168.122.209 [36170.503466] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:07:00 192.168.122.209 [36170.505245] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:07:00 192.168.122.209 [36170.543402] [tempesta fw] Tempesta FW is ready Apr 26 02:07:00 192.168.122.209 [36171.117339] [tdb] Close table 'client0.tdb' Apr 26 02:07:01 192.168.122.209 [36171.318804] [tdb] Close table 'sessions0.tdb' Apr 26 02:07:04 192.168.122.209 [36174.603722] [tdb] Close table 'cache0.tdb' Apr 26 02:07:04 192.168.122.209 [36174.866188] [tdb] Close table 'filter0.tdb' Apr 26 02:07:04 192.168.122.209 [36174.866630] [tempesta fw] modules are stopped Apr 26 02:07:04 192.168.122.209 [36175.071803] [tempesta fw] exiting... Apr 26 02:07:04 192.168.122.209 [36175.225069] [tdb] Shutdown Tempesta DB Apr 26 02:07:05 192.168.122.209 [36175.471101] End test: cache.test_cache.TestH2CacheDisable.test_cache_disable_1 Apr 26 02:07:05 192.168.122.209 [36175.496555] Start test: cache.test_cache.TestH2CacheDisable.test_cache_disable_with_override_http_chain Apr 26 02:07:06 192.168.122.209 [36176.748049] [tdb] Start Tempesta DB Apr 26 02:07:06 192.168.122.209 [36176.893976] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:07:08 192.168.122.209 [36178.620804] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36178.620804] Maybe that's fine, but it's worth checking the [36178.620804] config - if there is no relations between the [36178.620804] names, then host name confusion attack is possible. Apr 26 02:07:08 192.168.122.209 [36178.787593] [tempesta fw] Configuration processing is completed. Apr 26 02:07:08 192.168.122.209 [36178.873275] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:07:09 192.168.122.209 [36179.302607] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:07:09 192.168.122.209 [36179.329064] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:07:09 192.168.122.209 [36179.355606] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:07:09 192.168.122.209 [36179.411548] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:07:09 192.168.122.209 [36179.413246] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:07:09 192.168.122.209 [36179.459538] [tempesta fw] Tempesta FW is ready Apr 26 02:07:09 192.168.122.209 [36180.065549] [tdb] Close table 'client0.tdb' Apr 26 02:07:09 192.168.122.209 [36180.246132] [tdb] Close table 'sessions0.tdb' Apr 26 02:07:13 192.168.122.209 [36183.434567] [tdb] Close table 'cache0.tdb' Apr 26 02:07:13 192.168.122.209 [36183.674890] [tdb] Close table 'filter0.tdb' Apr 26 02:07:13 192.168.122.209 [36183.675319] [tempesta fw] modules are stopped Apr 26 02:07:13 192.168.122.209 [36183.940980] [tempesta fw] exiting... Apr 26 02:07:13 192.168.122.209 [36184.106132] [tdb] Shutdown Tempesta DB Apr 26 02:07:14 192.168.122.209 [36184.341035] End test: cache.test_cache.TestH2CacheDisable.test_cache_disable_with_override_http_chain Apr 26 02:07:14 192.168.122.209 [36184.357545] Start test: cache.test_cache.TestH2CacheHdrDel.test_cache_bypass Apr 26 02:07:15 192.168.122.209 [36185.539326] [tdb] Start Tempesta DB Apr 26 02:07:15 192.168.122.209 [36185.679948] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:07:16 192.168.122.209 [36187.097005] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36187.097005] Maybe that's fine, but it's worth checking the [36187.097005] config - if there is no relations between the [36187.097005] names, then host name confusion attack is possible. Apr 26 02:07:16 192.168.122.209 [36187.199682] [tempesta fw] Configuration processing is completed. Apr 26 02:07:16 192.168.122.209 [36187.249507] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:07:17 192.168.122.209 [36187.671767] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:07:17 192.168.122.209 [36187.697798] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:07:17 192.168.122.209 [36187.724684] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:07:17 192.168.122.209 [36187.771643] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:07:17 192.168.122.209 [36187.773404] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:07:17 192.168.122.209 [36187.819630] [tempesta fw] Tempesta FW is ready Apr 26 02:07:18 192.168.122.209 [36188.438923] [tdb] Close table 'client0.tdb' Apr 26 02:07:18 192.168.122.209 [36188.644534] [tdb] Close table 'sessions0.tdb' Apr 26 02:07:21 192.168.122.209 [36191.853565] [tdb] Close table 'cache0.tdb' Apr 26 02:07:21 192.168.122.209 [36192.078738] [tdb] Close table 'filter0.tdb' Apr 26 02:07:21 192.168.122.209 [36192.079169] [tempesta fw] modules are stopped Apr 26 02:07:22 192.168.122.209 [36192.280476] [tempesta fw] exiting... Apr 26 02:07:22 192.168.122.209 [36192.419701] [tdb] Shutdown Tempesta DB Apr 26 02:07:22 192.168.122.209 [36192.638080] End test: cache.test_cache.TestH2CacheHdrDel.test_cache_bypass Apr 26 02:07:22 192.168.122.209 [36192.662044] Start test: cache.test_cache.TestH2CacheHdrDel.test_cache_bypass_and_hdr_del Apr 26 02:07:23 192.168.122.209 [36193.821516] [tdb] Start Tempesta DB Apr 26 02:07:23 192.168.122.209 [36193.965139] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:07:25 192.168.122.209 [36195.356566] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36195.356566] Maybe that's fine, but it's worth checking the [36195.356566] config - if there is no relations between the [36195.356566] names, then host name confusion attack is possible. Apr 26 02:07:25 192.168.122.209 [36195.471811] [tempesta fw] Configuration processing is completed. Apr 26 02:07:25 192.168.122.209 [36195.521973] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:07:25 192.168.122.209 [36195.952812] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:07:25 192.168.122.209 [36195.978835] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:07:25 192.168.122.209 [36196.004964] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:07:25 192.168.122.209 [36196.051812] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:07:25 192.168.122.209 [36196.053536] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:07:25 192.168.122.209 [36196.099741] [tempesta fw] Tempesta FW is ready Apr 26 02:07:26 192.168.122.209 [36196.734293] [tdb] Close table 'client0.tdb' Apr 26 02:07:26 192.168.122.209 [36196.920602] [tdb] Close table 'sessions0.tdb' Apr 26 02:07:29 192.168.122.209 [36200.167824] [tdb] Close table 'cache0.tdb' Apr 26 02:07:30 192.168.122.209 [36200.405976] [tdb] Close table 'filter0.tdb' Apr 26 02:07:30 192.168.122.209 [36200.406410] [tempesta fw] modules are stopped Apr 26 02:07:30 192.168.122.209 [36200.604399] [tempesta fw] exiting... Apr 26 02:07:30 192.168.122.209 [36200.764207] [tdb] Shutdown Tempesta DB Apr 26 02:07:30 192.168.122.209 [36201.017365] End test: cache.test_cache.TestH2CacheHdrDel.test_cache_bypass_and_hdr_del Apr 26 02:07:30 192.168.122.209 [36201.028853] Start test: cache.test_cache.TestH2CacheHdrDel.test_cache_bypass_no_cache_with_arg Apr 26 02:07:31 192.168.122.209 [36202.222694] [tdb] Start Tempesta DB Apr 26 02:07:32 192.168.122.209 [36202.371373] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:07:33 192.168.122.209 [36203.785192] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36203.785192] Maybe that's fine, but it's worth checking the [36203.785192] config - if there is no relations between the [36203.785192] names, then host name confusion attack is possible. Apr 26 02:07:33 192.168.122.209 [36203.891909] [tempesta fw] Configuration processing is completed. Apr 26 02:07:33 192.168.122.209 [36203.949096] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:07:34 192.168.122.209 [36204.373694] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:07:34 192.168.122.209 [36204.399900] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:07:34 192.168.122.209 [36204.427245] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:07:34 192.168.122.209 [36204.475925] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:07:34 192.168.122.209 [36204.477664] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:07:34 192.168.122.209 [36204.519844] [tempesta fw] Tempesta FW is ready Apr 26 02:07:34 192.168.122.209 [36205.124264] [tdb] Close table 'client0.tdb' Apr 26 02:07:35 192.168.122.209 [36205.316560] [tdb] Close table 'sessions0.tdb' Apr 26 02:07:38 192.168.122.209 [36208.541589] [tdb] Close table 'cache0.tdb' Apr 26 02:07:38 192.168.122.209 [36208.791864] [tdb] Close table 'filter0.tdb' Apr 26 02:07:38 192.168.122.209 [36208.792295] [tempesta fw] modules are stopped Apr 26 02:07:38 192.168.122.209 [36208.978793] [tempesta fw] exiting... Apr 26 02:07:38 192.168.122.209 [36209.161524] [tdb] Shutdown Tempesta DB Apr 26 02:07:39 192.168.122.209 [36209.395124] End test: cache.test_cache.TestH2CacheHdrDel.test_cache_bypass_no_cache_with_arg Apr 26 02:07:39 192.168.122.209 [36209.414421] Start test: cache.test_cache.TestH2CacheHdrDel.test_cache_bypass_private_with_arg Apr 26 02:07:40 192.168.122.209 [36210.625413] [tdb] Start Tempesta DB Apr 26 02:07:40 192.168.122.209 [36210.781308] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:07:41 192.168.122.209 [36212.213260] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36212.213260] Maybe that's fine, but it's worth checking the [36212.213260] config - if there is no relations between the [36212.213260] names, then host name confusion attack is possible. Apr 26 02:07:42 192.168.122.209 [36212.320024] [tempesta fw] Configuration processing is completed. Apr 26 02:07:42 192.168.122.209 [36212.372942] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:07:42 192.168.122.209 [36212.802141] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:07:42 192.168.122.209 [36212.837527] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:07:42 192.168.122.209 [36212.864145] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:07:42 192.168.122.209 [36212.936008] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:07:42 192.168.122.209 [36212.937726] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:07:42 192.168.122.209 [36212.979963] [tempesta fw] Tempesta FW is ready Apr 26 02:07:43 192.168.122.209 [36213.610215] [tdb] Close table 'client0.tdb' Apr 26 02:07:43 192.168.122.209 [36213.826991] [tdb] Close table 'sessions0.tdb' Apr 26 02:07:46 192.168.122.209 [36217.006067] [tdb] Close table 'cache0.tdb' Apr 26 02:07:46 192.168.122.209 [36217.235074] [tdb] Close table 'filter0.tdb' Apr 26 02:07:46 192.168.122.209 [36217.235522] [tempesta fw] modules are stopped Apr 26 02:07:47 192.168.122.209 [36217.428301] [tempesta fw] exiting... Apr 26 02:07:47 192.168.122.209 [36217.628212] [tdb] Shutdown Tempesta DB Apr 26 02:07:47 192.168.122.209 [36217.884180] End test: cache.test_cache.TestH2CacheHdrDel.test_cache_bypass_private_with_arg Apr 26 02:07:47 192.168.122.209 [36217.900997] Start test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfill Apr 26 02:07:48 192.168.122.209 [36219.129354] [tdb] Start Tempesta DB Apr 26 02:07:49 192.168.122.209 [36219.277330] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:07:50 192.168.122.209 [36220.677367] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36220.677367] Maybe that's fine, but it's worth checking the [36220.677367] config - if there is no relations between the [36220.677367] names, then host name confusion attack is possible. Apr 26 02:07:50 192.168.122.209 [36220.780174] [tempesta fw] Configuration processing is completed. Apr 26 02:07:50 192.168.122.209 [36220.830080] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:07:50 192.168.122.209 [36221.249844] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:07:51 192.168.122.209 [36221.276830] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:07:51 192.168.122.209 [36221.302669] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:07:51 192.168.122.209 [36221.408119] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:07:51 192.168.122.209 [36221.409845] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:07:51 192.168.122.209 [36221.456061] [tempesta fw] Tempesta FW is ready Apr 26 02:07:51 192.168.122.209 [36222.061199] [tdb] Close table 'client0.tdb' Apr 26 02:07:51 192.168.122.209 [36222.250899] [tdb] Close table 'sessions0.tdb' Apr 26 02:07:55 192.168.122.209 [36225.433352] [tdb] Close table 'cache0.tdb' Apr 26 02:07:55 192.168.122.209 [36225.692227] [tdb] Close table 'filter0.tdb' Apr 26 02:07:55 192.168.122.209 [36225.692669] [tempesta fw] modules are stopped Apr 26 02:07:55 192.168.122.209 [36225.882528] [tempesta fw] exiting... Apr 26 02:07:55 192.168.122.209 [36226.022511] [tdb] Shutdown Tempesta DB Apr 26 02:07:55 192.168.122.209 [36226.243781] End test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfill Apr 26 02:07:55 192.168.122.209 [36226.254973] Start test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfill_and_hdr_del Apr 26 02:07:57 192.168.122.209 [36227.435774] [tdb] Start Tempesta DB Apr 26 02:07:57 192.168.122.209 [36227.585934] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:07:58 192.168.122.209 [36229.033447] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36229.033447] Maybe that's fine, but it's worth checking the [36229.033447] config - if there is no relations between the [36229.033447] names, then host name confusion attack is possible. Apr 26 02:07:58 192.168.122.209 [36229.152179] [tempesta fw] Configuration processing is completed. Apr 26 02:07:58 192.168.122.209 [36229.202145] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:07:59 192.168.122.209 [36229.629759] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:07:59 192.168.122.209 [36229.656364] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:07:59 192.168.122.209 [36229.683956] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:07:59 192.168.122.209 [36229.736870] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:07:59 192.168.122.209 [36229.738601] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:07:59 192.168.122.209 [36229.784166] [tempesta fw] Tempesta FW is ready Apr 26 02:08:00 192.168.122.209 [36230.373069] [tdb] Close table 'client0.tdb' Apr 26 02:08:00 192.168.122.209 [36230.558026] [tdb] Close table 'sessions0.tdb' Apr 26 02:08:03 192.168.122.209 [36233.727896] [tdb] Close table 'cache0.tdb' Apr 26 02:08:03 192.168.122.209 [36233.985176] [tdb] Close table 'filter0.tdb' Apr 26 02:08:03 192.168.122.209 [36233.985615] [tempesta fw] modules are stopped Apr 26 02:08:03 192.168.122.209 [36234.183829] [tempesta fw] exiting... Apr 26 02:08:04 192.168.122.209 [36234.360754] [tdb] Shutdown Tempesta DB Apr 26 02:08:04 192.168.122.209 [36234.579022] End test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfill_and_hdr_del Apr 26 02:08:04 192.168.122.209 [36234.589559] Start test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfilll_multi_cache_control Apr 26 02:08:05 192.168.122.209 [36235.817945] [tdb] Start Tempesta DB Apr 26 02:08:05 192.168.122.209 [36235.974503] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:08:07 192.168.122.209 [36237.393594] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36237.393594] Maybe that's fine, but it's worth checking the [36237.393594] config - if there is no relations between the [36237.393594] names, then host name confusion attack is possible. Apr 26 02:08:07 192.168.122.209 [36237.512337] [tempesta fw] Configuration processing is completed. Apr 26 02:08:07 192.168.122.209 [36237.561373] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:08:07 192.168.122.209 [36237.975499] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:08:07 192.168.122.209 [36238.001355] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:08:07 192.168.122.209 [36238.026887] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:08:07 192.168.122.209 [36238.092332] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:08:07 192.168.122.209 [36238.094049] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:08:07 192.168.122.209 [36238.140277] [tempesta fw] Tempesta FW is ready Apr 26 02:08:08 192.168.122.209 [36238.752405] [tdb] Close table 'client0.tdb' Apr 26 02:08:08 192.168.122.209 [36238.940766] [tdb] Close table 'sessions0.tdb' Apr 26 02:08:11 192.168.122.209 [36242.128933] [tdb] Close table 'cache0.tdb' Apr 26 02:08:12 192.168.122.209 [36242.349447] [tdb] Close table 'filter0.tdb' Apr 26 02:08:12 192.168.122.209 [36242.349887] [tempesta fw] modules are stopped Apr 26 02:08:12 192.168.122.209 [36242.539863] [tempesta fw] exiting... Apr 26 02:08:12 192.168.122.209 [36242.673353] [tdb] Shutdown Tempesta DB Apr 26 02:08:12 192.168.122.209 [36242.909126] End test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfilll_multi_cache_control Apr 26 02:08:12 192.168.122.209 [36242.928879] Start test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfilll_multi_cache_control_2 Apr 26 02:08:13 192.168.122.209 [36244.134323] [tdb] Start Tempesta DB Apr 26 02:08:14 192.168.122.209 [36244.286993] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:08:15 192.168.122.209 [36245.721655] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36245.721655] Maybe that's fine, but it's worth checking the [36245.721655] config - if there is no relations between the [36245.721655] names, then host name confusion attack is possible. Apr 26 02:08:15 192.168.122.209 [36245.828774] [tempesta fw] Configuration processing is completed. Apr 26 02:08:15 192.168.122.209 [36245.919545] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:08:16 192.168.122.209 [36246.349118] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:08:16 192.168.122.209 [36246.375529] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:08:16 192.168.122.209 [36246.402931] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:08:16 192.168.122.209 [36246.456516] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:08:16 192.168.122.209 [36246.458261] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:08:16 192.168.122.209 [36246.508382] [tempesta fw] Tempesta FW is ready Apr 26 02:08:16 192.168.122.209 [36247.162208] [tdb] Close table 'client0.tdb' Apr 26 02:08:17 192.168.122.209 [36247.355892] [tdb] Close table 'sessions0.tdb' Apr 26 02:08:20 192.168.122.209 [36250.535787] [tdb] Close table 'cache0.tdb' Apr 26 02:08:20 192.168.122.209 [36250.786981] [tdb] Close table 'filter0.tdb' Apr 26 02:08:20 192.168.122.209 [36250.787429] [tempesta fw] modules are stopped Apr 26 02:08:20 192.168.122.209 [36250.976248] [tempesta fw] exiting... Apr 26 02:08:20 192.168.122.209 [36251.129021] [tdb] Shutdown Tempesta DB Apr 26 02:08:21 192.168.122.209 [36251.359503] End test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfilll_multi_cache_control_2 Apr 26 02:08:21 192.168.122.209 [36251.374981] Start test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfilll_no_cache_with_arg Apr 26 02:08:22 192.168.122.209 [36252.588329] [tdb] Start Tempesta DB Apr 26 02:08:22 192.168.122.209 [36252.741558] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:08:23 192.168.122.209 [36254.185780] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36254.185780] Maybe that's fine, but it's worth checking the [36254.185780] config - if there is no relations between the [36254.185780] names, then host name confusion attack is possible. Apr 26 02:08:24 192.168.122.209 [36254.288580] [tempesta fw] Configuration processing is completed. Apr 26 02:08:24 192.168.122.209 [36254.343164] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:08:24 192.168.122.209 [36254.761204] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:08:24 192.168.122.209 [36254.787159] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:08:24 192.168.122.209 [36254.818156] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:08:24 192.168.122.209 [36254.868574] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:08:24 192.168.122.209 [36254.870310] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:08:24 192.168.122.209 [36254.908510] [tempesta fw] Tempesta FW is ready Apr 26 02:08:25 192.168.122.209 [36255.568600] [tdb] Close table 'client0.tdb' Apr 26 02:08:25 192.168.122.209 [36255.760040] [tdb] Close table 'sessions0.tdb' Apr 26 02:08:28 192.168.122.209 [36258.974387] [tdb] Close table 'cache0.tdb' Apr 26 02:08:28 192.168.122.209 [36259.211536] [tdb] Close table 'filter0.tdb' Apr 26 02:08:28 192.168.122.209 [36259.211997] [tempesta fw] modules are stopped Apr 26 02:08:29 192.168.122.209 [36259.410996] [tempesta fw] exiting... Apr 26 02:08:29 192.168.122.209 [36259.532550] [tdb] Shutdown Tempesta DB Apr 26 02:08:29 192.168.122.209 [36259.752080] End test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfilll_no_cache_with_arg Apr 26 02:08:29 192.168.122.209 [36259.773927] Start test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfilll_no_cache_with_arg_2 Apr 26 02:08:30 192.168.122.209 [36260.993842] [tdb] Start Tempesta DB Apr 26 02:08:30 192.168.122.209 [36261.144911] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:08:32 192.168.122.209 [36262.557878] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36262.557878] Maybe that's fine, but it's worth checking the [36262.557878] config - if there is no relations between the [36262.557878] names, then host name confusion attack is possible. Apr 26 02:08:32 192.168.122.209 [36262.668666] [tempesta fw] Configuration processing is completed. Apr 26 02:08:32 192.168.122.209 [36262.718372] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:08:32 192.168.122.209 [36263.149739] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:08:32 192.168.122.209 [36263.175368] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:08:32 192.168.122.209 [36263.201347] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:08:32 192.168.122.209 [36263.244654] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:08:32 192.168.122.209 [36263.246405] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:08:33 192.168.122.209 [36263.296621] [tempesta fw] Tempesta FW is ready Apr 26 02:08:33 192.168.122.209 [36263.924951] [tdb] Close table 'client0.tdb' Apr 26 02:08:33 192.168.122.209 [36264.114576] [tdb] Close table 'sessions0.tdb' Apr 26 02:08:37 192.168.122.209 [36267.327778] [tdb] Close table 'cache0.tdb' Apr 26 02:08:37 192.168.122.209 [36267.566796] [tdb] Close table 'filter0.tdb' Apr 26 02:08:37 192.168.122.209 [36267.567228] [tempesta fw] modules are stopped Apr 26 02:08:37 192.168.122.209 [36267.762341] [tempesta fw] exiting... Apr 26 02:08:37 192.168.122.209 [36267.918814] [tdb] Shutdown Tempesta DB Apr 26 02:08:37 192.168.122.209 [36268.158477] End test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfilll_no_cache_with_arg_2 Apr 26 02:08:37 192.168.122.209 [36268.182872] Start test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfilll_no_cache_with_args Apr 26 02:08:39 192.168.122.209 [36269.442270] [tdb] Start Tempesta DB Apr 26 02:08:39 192.168.122.209 [36269.582576] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:08:40 192.168.122.209 [36270.966012] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36270.966012] Maybe that's fine, but it's worth checking the [36270.966012] config - if there is no relations between the [36270.966012] names, then host name confusion attack is possible. Apr 26 02:08:40 192.168.122.209 [36271.072795] [tempesta fw] Configuration processing is completed. Apr 26 02:08:40 192.168.122.209 [36271.124208] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:08:41 192.168.122.209 [36271.550064] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:08:41 192.168.122.209 [36271.576679] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:08:41 192.168.122.209 [36271.603867] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:08:41 192.168.122.209 [36271.644772] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:08:41 192.168.122.209 [36271.646478] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:08:41 192.168.122.209 [36271.692716] [tempesta fw] Tempesta FW is ready Apr 26 02:08:42 192.168.122.209 [36272.345387] [tdb] Close table 'client0.tdb' Apr 26 02:08:42 192.168.122.209 [36272.542864] [tdb] Close table 'sessions0.tdb' Apr 26 02:08:45 192.168.122.209 [36275.716766] [tdb] Close table 'cache0.tdb' Apr 26 02:08:45 192.168.122.209 [36275.965392] [tdb] Close table 'filter0.tdb' Apr 26 02:08:45 192.168.122.209 [36275.965830] [tempesta fw] modules are stopped Apr 26 02:08:45 192.168.122.209 [36276.130196] [tempesta fw] exiting... Apr 26 02:08:46 192.168.122.209 [36276.297291] [tdb] Shutdown Tempesta DB Apr 26 02:08:46 192.168.122.209 [36276.532462] End test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfilll_no_cache_with_args Apr 26 02:08:46 192.168.122.209 [36276.557601] Start test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfilll_private_with_arg Apr 26 02:08:47 192.168.122.209 [36277.734995] [tdb] Start Tempesta DB Apr 26 02:08:47 192.168.122.209 [36277.881085] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:08:49 192.168.122.209 [36279.286116] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36279.286116] Maybe that's fine, but it's worth checking the [36279.286116] config - if there is no relations between the [36279.286116] names, then host name confusion attack is possible. Apr 26 02:08:49 192.168.122.209 [36279.388908] [tempesta fw] Configuration processing is completed. Apr 26 02:08:49 192.168.122.209 [36279.440370] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:08:49 192.168.122.209 [36279.872216] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:08:49 192.168.122.209 [36279.899144] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:08:49 192.168.122.209 [36279.926220] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:08:49 192.168.122.209 [36279.968880] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:08:49 192.168.122.209 [36279.970599] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:08:49 192.168.122.209 [36280.012769] [tempesta fw] Tempesta FW is ready Apr 26 02:08:50 192.168.122.209 [36280.637123] [tdb] Close table 'client0.tdb' Apr 26 02:08:50 192.168.122.209 [36280.803695] [tdb] Close table 'sessions0.tdb' Apr 26 02:08:53 192.168.122.209 [36283.999183] [tdb] Close table 'cache0.tdb' Apr 26 02:08:53 192.168.122.209 [36284.243725] [tdb] Close table 'filter0.tdb' Apr 26 02:08:53 192.168.122.209 [36284.244161] [tempesta fw] modules are stopped Apr 26 02:08:54 192.168.122.209 [36284.427637] [tempesta fw] exiting... Apr 26 02:08:54 192.168.122.209 [36284.616733] [tdb] Shutdown Tempesta DB Apr 26 02:08:54 192.168.122.209 [36284.850056] End test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfilll_private_with_arg Apr 26 02:08:54 192.168.122.209 [36284.862552] Start test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfilll_private_with_arg_2 Apr 26 02:08:55 192.168.122.209 [36286.095734] [tdb] Start Tempesta DB Apr 26 02:08:55 192.168.122.209 [36286.245328] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:08:57 192.168.122.209 [36287.594220] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36287.594220] Maybe that's fine, but it's worth checking the [36287.594220] config - if there is no relations between the [36287.594220] names, then host name confusion attack is possible. Apr 26 02:08:57 192.168.122.209 [36287.700991] [tempesta fw] Configuration processing is completed. Apr 26 02:08:57 192.168.122.209 [36287.751873] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:08:57 192.168.122.209 [36288.184603] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:08:57 192.168.122.209 [36288.211641] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:08:57 192.168.122.209 [36288.238449] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:08:58 192.168.122.209 [36288.332985] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:08:58 192.168.122.209 [36288.334710] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:08:58 192.168.122.209 [36288.392947] [tempesta fw] Tempesta FW is ready Apr 26 02:08:58 192.168.122.209 [36288.986027] [tdb] Close table 'client0.tdb' Apr 26 02:08:58 192.168.122.209 [36289.211887] [tdb] Close table 'sessions0.tdb' Apr 26 02:09:02 192.168.122.209 [36292.369236] [tdb] Close table 'cache0.tdb' Apr 26 02:09:02 192.168.122.209 [36292.608619] [tdb] Close table 'filter0.tdb' Apr 26 02:09:02 192.168.122.209 [36292.609091] [tempesta fw] modules are stopped Apr 26 02:09:02 192.168.122.209 [36292.799253] [tempesta fw] exiting... Apr 26 02:09:02 192.168.122.209 [36292.964765] [tdb] Shutdown Tempesta DB Apr 26 02:09:02 192.168.122.209 [36293.192081] End test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfilll_private_with_arg_2 Apr 26 02:09:02 192.168.122.209 [36293.211594] Start test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfilll_private_with_args Apr 26 02:09:04 192.168.122.209 [36294.434061] [tdb] Start Tempesta DB Apr 26 02:09:04 192.168.122.209 [36294.575444] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:09:05 192.168.122.209 [36295.998353] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36295.998353] Maybe that's fine, but it's worth checking the [36295.998353] config - if there is no relations between the [36295.998353] names, then host name confusion attack is possible. Apr 26 02:09:05 192.168.122.209 [36296.105115] [tempesta fw] Configuration processing is completed. Apr 26 02:09:05 192.168.122.209 [36296.154501] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:09:06 192.168.122.209 [36296.592203] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:09:06 192.168.122.209 [36296.628946] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:09:06 192.168.122.209 [36296.665887] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:09:06 192.168.122.209 [36296.709095] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:09:06 192.168.122.209 [36296.710854] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:09:06 192.168.122.209 [36296.749073] [tempesta fw] Tempesta FW is ready Apr 26 02:09:07 192.168.122.209 [36297.335365] [tdb] Close table 'client0.tdb' Apr 26 02:09:07 192.168.122.209 [36297.538185] [tdb] Close table 'sessions0.tdb' Apr 26 02:09:10 192.168.122.209 [36300.697755] [tdb] Close table 'cache0.tdb' Apr 26 02:09:10 192.168.122.209 [36300.952388] [tdb] Close table 'filter0.tdb' Apr 26 02:09:10 192.168.122.209 [36300.952812] [tempesta fw] modules are stopped Apr 26 02:09:10 192.168.122.209 [36301.130495] [tempesta fw] exiting... Apr 26 02:09:11 192.168.122.209 [36301.281312] [tdb] Shutdown Tempesta DB Apr 26 02:09:11 192.168.122.209 [36301.496499] End test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfilll_private_with_args Apr 26 02:09:11 192.168.122.209 [36301.515259] Start test: cache.test_cache.TestH2CacheTtl.test_global_cache_ttl_3_sleep_0 Apr 26 02:09:12 192.168.122.209 [36302.700804] [tdb] Start Tempesta DB Apr 26 02:09:12 192.168.122.209 [36302.857291] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:09:14 192.168.122.209 [36304.478357] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36304.478357] Maybe that's fine, but it's worth checking the [36304.478357] config - if there is no relations between the [36304.478357] names, then host name confusion attack is possible. Apr 26 02:09:14 192.168.122.209 [36304.669213] [tempesta fw] Configuration processing is completed. Apr 26 02:09:14 192.168.122.209 [36304.727165] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:09:14 192.168.122.209 [36305.133395] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:09:14 192.168.122.209 [36305.158497] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:09:14 192.168.122.209 [36305.183315] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:09:14 192.168.122.209 [36305.241228] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:09:14 192.168.122.209 [36305.242977] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:09:15 192.168.122.209 [36305.293173] [tempesta fw] Tempesta FW is ready Apr 26 02:09:15 192.168.122.209 [36305.890288] [tdb] Close table 'client0.tdb' Apr 26 02:09:15 192.168.122.209 [36306.101904] [tdb] Close table 'sessions0.tdb' Apr 26 02:09:19 192.168.122.209 [36309.306344] [tdb] Close table 'cache0.tdb' Apr 26 02:09:19 192.168.122.209 [36309.536772] [tdb] Close table 'filter0.tdb' Apr 26 02:09:19 192.168.122.209 [36309.537246] [tempesta fw] modules are stopped Apr 26 02:09:19 192.168.122.209 [36309.748550] [tempesta fw] exiting... Apr 26 02:09:19 192.168.122.209 [36309.904656] [tdb] Shutdown Tempesta DB Apr 26 02:09:19 192.168.122.209 [36310.135210] End test: cache.test_cache.TestH2CacheTtl.test_global_cache_ttl_3_sleep_0 Apr 26 02:09:19 192.168.122.209 [36310.153901] Start test: cache.test_cache.TestH2CacheTtl.test_global_cache_ttl_3_sleep_2_max_age_1 Apr 26 02:09:21 192.168.122.209 [36311.365434] [tdb] Start Tempesta DB Apr 26 02:09:21 192.168.122.209 [36311.511945] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:09:22 192.168.122.209 [36313.110551] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36313.110551] Maybe that's fine, but it's worth checking the [36313.110551] config - if there is no relations between the [36313.110551] names, then host name confusion attack is possible. Apr 26 02:09:23 192.168.122.209 [36313.305381] [tempesta fw] Configuration processing is completed. Apr 26 02:09:23 192.168.122.209 [36313.358685] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:09:23 192.168.122.209 [36313.781647] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:09:23 192.168.122.209 [36313.808012] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:09:23 192.168.122.209 [36313.834407] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:09:23 192.168.122.209 [36313.881321] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:09:23 192.168.122.209 [36313.883063] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:09:23 192.168.122.209 [36313.921277] [tempesta fw] Tempesta FW is ready Apr 26 02:09:26 192.168.122.209 [36316.533766] [tdb] Close table 'client0.tdb' Apr 26 02:09:26 192.168.122.209 [36316.721627] [tdb] Close table 'sessions0.tdb' Apr 26 02:09:29 192.168.122.209 [36319.912858] [tdb] Close table 'cache0.tdb' Apr 26 02:09:29 192.168.122.209 [36320.156333] [tdb] Close table 'filter0.tdb' Apr 26 02:09:29 192.168.122.209 [36320.156757] [tempesta fw] modules are stopped Apr 26 02:09:30 192.168.122.209 [36320.397693] [tempesta fw] exiting... Apr 26 02:09:30 192.168.122.209 [36320.555039] [tdb] Shutdown Tempesta DB Apr 26 02:09:30 192.168.122.209 [36320.757025] End test: cache.test_cache.TestH2CacheTtl.test_global_cache_ttl_3_sleep_2_max_age_1 Apr 26 02:09:30 192.168.122.209 [36320.780386] Start test: cache.test_cache.TestH2CacheTtl.test_global_cache_ttl_3_sleep_2_s_maxage_1 Apr 26 02:09:31 192.168.122.209 [36321.983410] [tdb] Start Tempesta DB Apr 26 02:09:31 192.168.122.209 [36322.136112] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:09:33 192.168.122.209 [36323.818563] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36323.818563] Maybe that's fine, but it's worth checking the [36323.818563] config - if there is no relations between the [36323.818563] names, then host name confusion attack is possible. Apr 26 02:09:33 192.168.122.209 [36324.013452] [tempesta fw] Configuration processing is completed. Apr 26 02:09:33 192.168.122.209 [36324.064299] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:09:34 192.168.122.209 [36324.485777] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:09:34 192.168.122.209 [36324.512168] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:09:34 192.168.122.209 [36324.538481] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:09:34 192.168.122.209 [36324.625466] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:09:34 192.168.122.209 [36324.627217] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:09:34 192.168.122.209 [36324.665420] [tempesta fw] Tempesta FW is ready Apr 26 02:09:36 192.168.122.209 [36327.259187] [tdb] Close table 'client0.tdb' Apr 26 02:09:37 192.168.122.209 [36327.448260] [tdb] Close table 'sessions0.tdb' Apr 26 02:09:40 192.168.122.209 [36330.608179] [tdb] Close table 'cache0.tdb' Apr 26 02:09:40 192.168.122.209 [36330.848716] [tdb] Close table 'filter0.tdb' Apr 26 02:09:40 192.168.122.209 [36330.849118] [tempesta fw] modules are stopped Apr 26 02:09:40 192.168.122.209 [36331.062745] [tempesta fw] exiting... Apr 26 02:09:40 192.168.122.209 [36331.187510] [tdb] Shutdown Tempesta DB Apr 26 02:09:41 192.168.122.209 [36331.430815] End test: cache.test_cache.TestH2CacheTtl.test_global_cache_ttl_3_sleep_2_s_maxage_1 Apr 26 02:09:41 192.168.122.209 [36331.446019] Start test: cache.test_cache.TestH2CacheTtl.test_global_cache_ttl_3_sleep_4 Apr 26 02:09:42 192.168.122.209 [36332.619623] [tdb] Start Tempesta DB Apr 26 02:09:42 192.168.122.209 [36332.767568] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:09:44 192.168.122.209 [36334.366919] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36334.366919] Maybe that's fine, but it's worth checking the [36334.366919] config - if there is no relations between the [36334.366919] names, then host name confusion attack is possible. Apr 26 02:09:44 192.168.122.209 [36334.545690] [tempesta fw] Configuration processing is completed. Apr 26 02:09:44 192.168.122.209 [36334.594990] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:09:44 192.168.122.209 [36335.014206] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:09:44 192.168.122.209 [36335.039478] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:09:44 192.168.122.209 [36335.064816] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:09:44 192.168.122.209 [36335.117604] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:09:44 192.168.122.209 [36335.119356] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:09:44 192.168.122.209 [36335.165552] [tempesta fw] Tempesta FW is ready Apr 26 02:09:49 192.168.122.209 [36339.791479] [tdb] Close table 'client0.tdb' Apr 26 02:09:49 192.168.122.209 [36339.983597] [tdb] Close table 'sessions0.tdb' Apr 26 02:09:52 192.168.122.209 [36343.161672] [tdb] Close table 'cache0.tdb' Apr 26 02:09:53 192.168.122.209 [36343.418833] [tdb] Close table 'filter0.tdb' Apr 26 02:09:53 192.168.122.209 [36343.419246] [tempesta fw] modules are stopped Apr 26 02:09:53 192.168.122.209 [36343.666069] [tempesta fw] exiting... Apr 26 02:09:53 192.168.122.209 [36343.816961] [tdb] Shutdown Tempesta DB Apr 26 02:09:53 192.168.122.209 [36344.048142] End test: cache.test_cache.TestH2CacheTtl.test_global_cache_ttl_3_sleep_4 Apr 26 02:09:53 192.168.122.209 [36344.062101] Start test: cache.test_cache.TestH2CacheTtl.test_global_cache_ttl_3_sleep_4_max_age_10 Apr 26 02:09:54 192.168.122.209 [36345.243160] [tdb] Start Tempesta DB Apr 26 02:09:55 192.168.122.209 [36345.379967] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:09:56 192.168.122.209 [36347.099007] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36347.099007] Maybe that's fine, but it's worth checking the [36347.099007] config - if there is no relations between the [36347.099007] names, then host name confusion attack is possible. Apr 26 02:09:57 192.168.122.209 [36347.293814] [tempesta fw] Configuration processing is completed. Apr 26 02:09:57 192.168.122.209 [36347.378454] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:09:57 192.168.122.209 [36347.817208] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:09:57 192.168.122.209 [36347.844134] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:09:57 192.168.122.209 [36347.871084] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:09:57 192.168.122.209 [36347.913824] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:09:57 192.168.122.209 [36347.915541] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:09:57 192.168.122.209 [36347.957714] [tempesta fw] Tempesta FW is ready Apr 26 02:10:02 192.168.122.209 [36352.545840] [tdb] Close table 'client0.tdb' Apr 26 02:10:02 192.168.122.209 [36352.738549] [tdb] Close table 'sessions0.tdb' Apr 26 02:10:05 192.168.122.209 [36355.966525] [tdb] Close table 'cache0.tdb' Apr 26 02:10:05 192.168.122.209 [36356.181730] [tdb] Close table 'filter0.tdb' Apr 26 02:10:05 192.168.122.209 [36356.182163] [tempesta fw] modules are stopped Apr 26 02:10:06 192.168.122.209 [36356.458001] [tempesta fw] exiting... Apr 26 02:10:06 192.168.122.209 [36356.620380] [tdb] Shutdown Tempesta DB Apr 26 02:10:06 192.168.122.209 [36356.834815] End test: cache.test_cache.TestH2CacheTtl.test_global_cache_ttl_3_sleep_4_max_age_10 Apr 26 02:10:06 192.168.122.209 [36356.847980] Start test: cache.test_cache.TestH2CacheTtl.test_priority_for_cache_control_header_no_cache Apr 26 02:10:07 192.168.122.209 [36357.892994] [tdb] Start Tempesta DB Apr 26 02:10:07 192.168.122.209 [36358.033773] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:10:09 192.168.122.209 [36359.643188] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36359.643188] Maybe that's fine, but it's worth checking the [36359.643188] config - if there is no relations between the [36359.643188] names, then host name confusion attack is possible. Apr 26 02:10:09 192.168.122.209 [36359.841933] [tempesta fw] Configuration processing is completed. Apr 26 02:10:09 192.168.122.209 [36359.892712] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:10:10 192.168.122.209 [36360.302432] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:10:10 192.168.122.209 [36360.328001] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:10:10 192.168.122.209 [36360.353288] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:10:10 192.168.122.209 [36360.409939] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:10:10 192.168.122.209 [36360.411673] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:10:10 192.168.122.209 [36360.457826] [tempesta fw] Tempesta FW is ready Apr 26 02:10:10 192.168.122.209 [36361.085164] [tdb] Close table 'client0.tdb' Apr 26 02:10:11 192.168.122.209 [36361.278144] [tdb] Close table 'sessions0.tdb' Apr 26 02:10:14 192.168.122.209 [36364.515388] [tdb] Close table 'cache0.tdb' Apr 26 02:10:14 192.168.122.209 [36364.770666] [tdb] Close table 'filter0.tdb' Apr 26 02:10:14 192.168.122.209 [36364.771095] [tempesta fw] modules are stopped Apr 26 02:10:14 192.168.122.209 [36364.977899] [tempesta fw] exiting... Apr 26 02:10:14 192.168.122.209 [36365.126808] [tdb] Shutdown Tempesta DB Apr 26 02:10:15 192.168.122.209 [36365.351388] End test: cache.test_cache.TestH2CacheTtl.test_priority_for_cache_control_header_no_cache Apr 26 02:10:15 192.168.122.209 [36365.371674] Start test: cache.test_cache.TestH2CacheTtl.test_priority_for_cache_control_header_no_store Apr 26 02:10:16 192.168.122.209 [36366.441517] [tdb] Start Tempesta DB Apr 26 02:10:16 192.168.122.209 [36366.587740] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:10:18 192.168.122.209 [36368.323304] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36368.323304] Maybe that's fine, but it's worth checking the [36368.323304] config - if there is no relations between the [36368.323304] names, then host name confusion attack is possible. Apr 26 02:10:18 192.168.122.209 [36368.514084] [tempesta fw] Configuration processing is completed. Apr 26 02:10:18 192.168.122.209 [36368.567112] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:10:18 192.168.122.209 [36368.993591] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:10:18 192.168.122.209 [36369.019906] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:10:18 192.168.122.209 [36369.046010] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:10:18 192.168.122.209 [36369.098056] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:10:18 192.168.122.209 [36369.099790] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:10:18 192.168.122.209 [36369.137980] [tempesta fw] Tempesta FW is ready Apr 26 02:10:19 192.168.122.209 [36369.742091] [tdb] Close table 'client0.tdb' Apr 26 02:10:19 192.168.122.209 [36369.931692] [tdb] Close table 'sessions0.tdb' Apr 26 02:10:22 192.168.122.209 [36373.099708] [tdb] Close table 'cache0.tdb' Apr 26 02:10:23 192.168.122.209 [36373.349348] [tdb] Close table 'filter0.tdb' Apr 26 02:10:23 192.168.122.209 [36373.349774] [tempesta fw] modules are stopped Apr 26 02:10:23 192.168.122.209 [36373.583603] [tempesta fw] exiting... Apr 26 02:10:23 192.168.122.209 [36373.736323] [tdb] Shutdown Tempesta DB Apr 26 02:10:23 192.168.122.209 [36373.971595] End test: cache.test_cache.TestH2CacheTtl.test_priority_for_cache_control_header_no_store Apr 26 02:10:23 192.168.122.209 [36373.992184] Start test: cache.test_cache.TestH2CacheTtl.test_priority_for_cache_control_header_private Apr 26 02:10:24 192.168.122.209 [36375.219093] [tdb] Start Tempesta DB Apr 26 02:10:25 192.168.122.209 [36375.364736] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:10:26 192.168.122.209 [36377.083416] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36377.083416] Maybe that's fine, but it's worth checking the [36377.083416] config - if there is no relations between the [36377.083416] names, then host name confusion attack is possible. Apr 26 02:10:26 192.168.122.209 [36377.258158] [tempesta fw] Configuration processing is completed. Apr 26 02:10:27 192.168.122.209 [36377.309371] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:10:27 192.168.122.209 [36377.725857] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:10:27 192.168.122.209 [36377.751751] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:10:27 192.168.122.209 [36377.777397] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:10:27 192.168.122.209 [36377.830170] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:10:27 192.168.122.209 [36377.831899] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:10:27 192.168.122.209 [36377.878110] [tempesta fw] Tempesta FW is ready Apr 26 02:10:28 192.168.122.209 [36378.523762] [tdb] Close table 'client0.tdb' Apr 26 02:10:28 192.168.122.209 [36378.712287] [tdb] Close table 'sessions0.tdb' Apr 26 02:10:32 192.168.122.209 [36383.103796] [tdb] Close table 'cache0.tdb' Apr 26 02:10:33 192.168.122.209 [36383.649169] [tdb] Close table 'filter0.tdb' Apr 26 02:10:33 192.168.122.209 [36383.649611] [tempesta fw] modules are stopped Apr 26 02:10:34 192.168.122.209 [36384.936665] [tempesta fw] exiting... Apr 26 02:10:35 192.168.122.209 [36385.435570] [tdb] Shutdown Tempesta DB Apr 26 02:10:35 192.168.122.209 [36385.796535] End test: cache.test_cache.TestH2CacheTtl.test_priority_for_cache_control_header_private Apr 26 02:10:35 192.168.122.209 [36385.815787] Start test: cache.test_cache.TestH2CacheTtl.test_vhost_cache_ttl_1_sleep_2 Apr 26 02:10:36 192.168.122.209 [36387.004244] [tdb] Start Tempesta DB Apr 26 02:10:36 192.168.122.209 [36387.154750] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:10:38 192.168.122.209 [36388.803545] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36388.803545] Maybe that's fine, but it's worth checking the [36388.803545] config - if there is no relations between the [36388.803545] names, then host name confusion attack is possible. Apr 26 02:10:38 192.168.122.209 [36388.998318] [tempesta fw] Configuration processing is completed. Apr 26 02:10:38 192.168.122.209 [36389.085597] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:10:39 192.168.122.209 [36389.503949] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:10:39 192.168.122.209 [36389.529916] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:10:39 192.168.122.209 [36389.556098] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:10:39 192.168.122.209 [36389.594301] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:10:39 192.168.122.209 [36389.595382] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:10:39 192.168.122.209 [36389.638245] [tempesta fw] Tempesta FW is ready Apr 26 02:10:41 192.168.122.209 [36392.259913] [tdb] Close table 'client0.tdb' Apr 26 02:10:42 192.168.122.209 [36392.444574] [tdb] Close table 'sessions0.tdb' Apr 26 02:10:45 192.168.122.209 [36395.619676] [tdb] Close table 'cache0.tdb' Apr 26 02:10:45 192.168.122.209 [36395.853601] [tdb] Close table 'filter0.tdb' Apr 26 02:10:45 192.168.122.209 [36395.854033] [tempesta fw] modules are stopped Apr 26 02:10:45 192.168.122.209 [36396.069302] [tempesta fw] exiting... Apr 26 02:10:45 192.168.122.209 [36396.226800] [tdb] Shutdown Tempesta DB Apr 26 02:10:46 192.168.122.209 [36396.478513] End test: cache.test_cache.TestH2CacheTtl.test_vhost_cache_ttl_1_sleep_2 Apr 26 02:10:46 192.168.122.209 [36396.491697] Start test: cache.test_cache.TestH2CacheTtl.test_vhost_cache_ttl_1_sleep_4 Apr 26 02:10:47 192.168.122.209 [36397.661511] [tdb] Start Tempesta DB Apr 26 02:10:47 192.168.122.209 [36397.819016] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:10:49 192.168.122.209 [36399.427667] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36399.427667] Maybe that's fine, but it's worth checking the [36399.427667] config - if there is no relations between the [36399.427667] names, then host name confusion attack is possible. Apr 26 02:10:49 192.168.122.209 [36399.618441] [tempesta fw] Configuration processing is completed. Apr 26 02:10:49 192.168.122.209 [36399.680394] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:10:49 192.168.122.209 [36400.102877] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:10:49 192.168.122.209 [36400.129136] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:10:49 192.168.122.209 [36400.154907] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:10:49 192.168.122.209 [36400.214436] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:10:49 192.168.122.209 [36400.216204] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:10:49 192.168.122.209 [36400.254385] [tempesta fw] Tempesta FW is ready Apr 26 02:10:54 192.168.122.209 [36404.837462] [tdb] Close table 'client0.tdb' Apr 26 02:10:54 192.168.122.209 [36405.048948] [tdb] Close table 'sessions0.tdb' Apr 26 02:10:57 192.168.122.209 [36408.211895] [tdb] Close table 'cache0.tdb' Apr 26 02:10:58 192.168.122.209 [36408.436156] [tdb] Close table 'filter0.tdb' Apr 26 02:10:58 192.168.122.209 [36408.436585] [tempesta fw] modules are stopped Apr 26 02:10:58 192.168.122.209 [36408.686751] [tempesta fw] exiting... Apr 26 02:10:58 192.168.122.209 [36408.813303] [tdb] Shutdown Tempesta DB Apr 26 02:10:58 192.168.122.209 [36409.054399] End test: cache.test_cache.TestH2CacheTtl.test_vhost_cache_ttl_1_sleep_4 Apr 26 02:10:58 192.168.122.209 [36409.067686] Start test: cache.test_cache.TestQueryparamsAndRedirectH2.test_query_param_different_key Apr 26 02:11:00 192.168.122.209 [36410.277827] [tdb] Start Tempesta DB Apr 26 02:11:00 192.168.122.209 [36410.438342] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:11:01 192.168.122.209 [36411.959849] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36411.959849] Maybe that's fine, but it's worth checking the [36411.959849] config - if there is no relations between the [36411.959849] names, then host name confusion attack is possible. Apr 26 02:11:01 192.168.122.209 [36412.054894] [tempesta fw] Configuration processing is completed. Apr 26 02:11:01 192.168.122.209 [36412.104949] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:11:02 192.168.122.209 [36412.534903] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:11:02 192.168.122.209 [36412.560818] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:11:02 192.168.122.209 [36412.586873] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:11:02 192.168.122.209 [36412.630601] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:11:02 192.168.122.209 [36412.632331] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:11:02 192.168.122.209 [36412.682545] [tempesta fw] Tempesta FW is ready Apr 26 02:11:02 192.168.122.209 [36413.254128] [tdb] Close table 'client0.tdb' Apr 26 02:11:03 192.168.122.209 [36413.478337] [tdb] Close table 'sessions0.tdb' Apr 26 02:11:06 192.168.122.209 [36416.655647] [tdb] Close table 'cache0.tdb' Apr 26 02:11:06 192.168.122.209 [36416.895020] [tdb] Close table 'filter0.tdb' Apr 26 02:11:06 192.168.122.209 [36416.895501] [tempesta fw] modules are stopped Apr 26 02:11:06 192.168.122.209 [36417.089084] [tempesta fw] exiting... Apr 26 02:11:06 192.168.122.209 [36417.259356] [tdb] Shutdown Tempesta DB Apr 26 02:11:07 192.168.122.209 [36417.509486] End test: cache.test_cache.TestQueryparamsAndRedirectH2.test_query_param_different_key Apr 26 02:11:07 192.168.122.209 [36417.526443] Start test: cache.test_cache.TestQueryparamsAndRedirectH2.test_query_param_different_value Apr 26 02:11:08 192.168.122.209 [36418.764543] [tdb] Start Tempesta DB Apr 26 02:11:08 192.168.122.209 [36418.914202] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:11:10 192.168.122.209 [36420.304046] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36420.304046] Maybe that's fine, but it's worth checking the [36420.304046] config - if there is no relations between the [36420.304046] names, then host name confusion attack is possible. Apr 26 02:11:10 192.168.122.209 [36420.398720] [tempesta fw] Configuration processing is completed. Apr 26 02:11:10 192.168.122.209 [36420.448457] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:11:10 192.168.122.209 [36420.869729] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:11:10 192.168.122.209 [36420.896084] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:11:10 192.168.122.209 [36420.922546] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:11:10 192.168.122.209 [36420.978728] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:11:10 192.168.122.209 [36420.980461] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:11:10 192.168.122.209 [36421.034668] [tempesta fw] Tempesta FW is ready Apr 26 02:11:11 192.168.122.209 [36421.681370] [tdb] Close table 'client0.tdb' Apr 26 02:11:11 192.168.122.209 [36421.880775] [tdb] Close table 'sessions0.tdb' Apr 26 02:11:14 192.168.122.209 [36425.030835] [tdb] Close table 'cache0.tdb' Apr 26 02:11:15 192.168.122.209 [36425.286414] [tdb] Close table 'filter0.tdb' Apr 26 02:11:15 192.168.122.209 [36425.286893] [tempesta fw] modules are stopped Apr 26 02:11:15 192.168.122.209 [36425.490343] [tempesta fw] exiting... Apr 26 02:11:15 192.168.122.209 [36425.642028] [tdb] Shutdown Tempesta DB Apr 26 02:11:15 192.168.122.209 [36425.887921] End test: cache.test_cache.TestQueryparamsAndRedirectH2.test_query_param_different_value Apr 26 02:11:15 192.168.122.209 [36425.900465] Start test: cache.test_cache.TestQueryparamsAndRedirectH2.test_query_param_same_params Apr 26 02:11:16 192.168.122.209 [36427.090192] [tdb] Start Tempesta DB Apr 26 02:11:16 192.168.122.209 [36427.241086] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:11:18 192.168.122.209 [36428.740083] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36428.740083] Maybe that's fine, but it's worth checking the [36428.740083] config - if there is no relations between the [36428.740083] names, then host name confusion attack is possible. Apr 26 02:11:18 192.168.122.209 [36428.850839] [tempesta fw] Configuration processing is completed. Apr 26 02:11:18 192.168.122.209 [36428.937813] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:11:19 192.168.122.209 [36429.363950] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:11:19 192.168.122.209 [36429.390806] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:11:19 192.168.122.209 [36429.417635] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:11:19 192.168.122.209 [36429.462840] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:11:19 192.168.122.209 [36429.464578] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:11:19 192.168.122.209 [36429.502776] [tempesta fw] Tempesta FW is ready Apr 26 02:11:19 192.168.122.209 [36430.153445] [tdb] Close table 'client0.tdb' Apr 26 02:11:20 192.168.122.209 [36430.348294] [tdb] Close table 'sessions0.tdb' Apr 26 02:11:23 192.168.122.209 [36433.482237] [tdb] Close table 'cache0.tdb' Apr 26 02:11:23 192.168.122.209 [36433.742509] [tdb] Close table 'filter0.tdb' Apr 26 02:11:23 192.168.122.209 [36433.742954] [tempesta fw] modules are stopped Apr 26 02:11:23 192.168.122.209 [36433.987860] [tempesta fw] exiting... Apr 26 02:11:23 192.168.122.209 [36434.124750] [tdb] Shutdown Tempesta DB Apr 26 02:11:24 192.168.122.209 [36434.357001] End test: cache.test_cache.TestQueryparamsAndRedirectH2.test_query_param_same_params Apr 26 02:11:24 192.168.122.209 [36434.379029] Start test: cache.test_cache.TestQueryparamsAndRedirectH2.test_query_param_with_new_param Apr 26 02:11:25 192.168.122.209 [36435.670158] [tdb] Start Tempesta DB Apr 26 02:11:25 192.168.122.209 [36435.805654] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:11:27 192.168.122.209 [36437.328277] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36437.328277] Maybe that's fine, but it's worth checking the [36437.328277] config - if there is no relations between the [36437.328277] names, then host name confusion attack is possible. Apr 26 02:11:27 192.168.122.209 [36437.414943] [tempesta fw] Configuration processing is completed. Apr 26 02:11:27 192.168.122.209 [36437.474885] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:11:27 192.168.122.209 [36438.029524] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:11:27 192.168.122.209 [36438.064118] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:11:27 192.168.122.209 [36438.097672] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:11:27 192.168.122.209 [36438.142904] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:11:27 192.168.122.209 [36438.144015] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:11:27 192.168.122.209 [36438.182896] [tempesta fw] Tempesta FW is ready Apr 26 02:11:28 192.168.122.209 [36438.886563] [tdb] Close table 'client0.tdb' Apr 26 02:11:28 192.168.122.209 [36439.085308] [tdb] Close table 'sessions0.tdb' Apr 26 02:11:31 192.168.122.209 [36442.234732] [tdb] Close table 'cache0.tdb' Apr 26 02:11:32 192.168.122.209 [36442.494957] [tdb] Close table 'filter0.tdb' Apr 26 02:11:32 192.168.122.209 [36442.495401] [tempesta fw] modules are stopped Apr 26 02:11:32 192.168.122.209 [36442.695259] [tempesta fw] exiting... Apr 26 02:11:32 192.168.122.209 [36442.844293] [tdb] Shutdown Tempesta DB Apr 26 02:11:32 192.168.122.209 [36443.053775] End test: cache.test_cache.TestQueryparamsAndRedirectH2.test_query_param_with_new_param Apr 26 02:11:32 192.168.122.209 [36443.071985] Start test: cache.test_cache.TestQueryparamsAndRedirectH2.test_redirect_300_multiple_choices Apr 26 02:11:34 192.168.122.209 [36444.382717] [tdb] Start Tempesta DB Apr 26 02:11:34 192.168.122.209 [36444.545858] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:11:35 192.168.122.209 [36446.060311] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36446.060311] Maybe that's fine, but it's worth checking the [36446.060311] config - if there is no relations between the [36446.060311] names, then host name confusion attack is possible. Apr 26 02:11:35 192.168.122.209 [36446.147103] [tempesta fw] Configuration processing is completed. Apr 26 02:11:35 192.168.122.209 [36446.209195] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:11:36 192.168.122.209 [36446.629008] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:11:36 192.168.122.209 [36446.655524] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:11:36 192.168.122.209 [36446.681842] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:11:36 192.168.122.209 [36446.727046] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:11:36 192.168.122.209 [36446.728797] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:11:36 192.168.122.209 [36446.762989] [tempesta fw] Tempesta FW is ready Apr 26 02:11:37 192.168.122.209 [36447.413349] [tdb] Close table 'client0.tdb' Apr 26 02:11:37 192.168.122.209 [36447.607925] [tdb] Close table 'sessions0.tdb' Apr 26 02:11:40 192.168.122.209 [36450.889209] [tdb] Close table 'cache0.tdb' Apr 26 02:11:40 192.168.122.209 [36451.147538] [tdb] Close table 'filter0.tdb' Apr 26 02:11:40 192.168.122.209 [36451.148020] [tempesta fw] modules are stopped Apr 26 02:11:41 192.168.122.209 [36451.357196] [tempesta fw] exiting... Apr 26 02:11:41 192.168.122.209 [36451.497802] [tdb] Shutdown Tempesta DB Apr 26 02:11:41 192.168.122.209 [36451.712055] End test: cache.test_cache.TestQueryparamsAndRedirectH2.test_redirect_300_multiple_choices Apr 26 02:11:41 192.168.122.209 [36451.730480] Start test: cache.test_cache.TestQueryparamsAndRedirectH2.test_redirect_301_moved_permanently Apr 26 02:11:42 192.168.122.209 [36453.051368] [tdb] Start Tempesta DB Apr 26 02:11:42 192.168.122.209 [36453.201075] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:11:44 192.168.122.209 [36454.700424] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36454.700424] Maybe that's fine, but it's worth checking the [36454.700424] config - if there is no relations between the [36454.700424] names, then host name confusion attack is possible. Apr 26 02:11:44 192.168.122.209 [36454.787166] [tempesta fw] Configuration processing is completed. Apr 26 02:11:44 192.168.122.209 [36454.869630] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:11:45 192.168.122.209 [36455.307265] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:11:45 192.168.122.209 [36455.342708] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:11:45 192.168.122.209 [36455.378290] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:11:45 192.168.122.209 [36455.447171] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:11:45 192.168.122.209 [36455.448909] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:11:45 192.168.122.209 [36455.495101] [tempesta fw] Tempesta FW is ready Apr 26 02:11:45 192.168.122.209 [36456.132272] [tdb] Close table 'client0.tdb' Apr 26 02:11:46 192.168.122.209 [36456.336152] [tdb] Close table 'sessions0.tdb' Apr 26 02:11:49 192.168.122.209 [36459.557605] [tdb] Close table 'cache0.tdb' Apr 26 02:11:49 192.168.122.209 [36459.806021] [tdb] Close table 'filter0.tdb' Apr 26 02:11:49 192.168.122.209 [36459.806469] [tempesta fw] modules are stopped Apr 26 02:11:49 192.168.122.209 [36460.045319] [tempesta fw] exiting... Apr 26 02:11:49 192.168.122.209 [36460.196590] [tdb] Shutdown Tempesta DB Apr 26 02:11:50 192.168.122.209 [36460.424700] End test: cache.test_cache.TestQueryparamsAndRedirectH2.test_redirect_301_moved_permanently Apr 26 02:11:50 192.168.122.209 [36460.452429] Start test: cache.test_cache.TestQueryparamsAndRedirectH2.test_redirect_302_found Apr 26 02:11:51 192.168.122.209 [36461.772792] [tdb] Start Tempesta DB Apr 26 02:11:51 192.168.122.209 [36461.940568] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:11:53 192.168.122.209 [36463.444508] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36463.444508] Maybe that's fine, but it's worth checking the [36463.444508] config - if there is no relations between the [36463.444508] names, then host name confusion attack is possible. Apr 26 02:11:53 192.168.122.209 [36463.539371] [tempesta fw] Configuration processing is completed. Apr 26 02:11:53 192.168.122.209 [36463.589073] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:11:53 192.168.122.209 [36464.011445] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:11:53 192.168.122.209 [36464.037543] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:11:53 192.168.122.209 [36464.063357] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:11:53 192.168.122.209 [36464.111286] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:11:53 192.168.122.209 [36464.113004] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:11:53 192.168.122.209 [36464.159230] [tempesta fw] Tempesta FW is ready Apr 26 02:11:54 192.168.122.209 [36464.794638] [tdb] Close table 'client0.tdb' Apr 26 02:11:54 192.168.122.209 [36465.015411] [tdb] Close table 'sessions0.tdb' Apr 26 02:11:57 192.168.122.209 [36468.167052] [tdb] Close table 'cache0.tdb' Apr 26 02:11:58 192.168.122.209 [36468.383888] [tdb] Close table 'filter0.tdb' Apr 26 02:11:58 192.168.122.209 [36468.384323] [tempesta fw] modules are stopped Apr 26 02:11:58 192.168.122.209 [36468.626576] [tempesta fw] exiting... Apr 26 02:11:58 192.168.122.209 [36468.791626] [tdb] Shutdown Tempesta DB Apr 26 02:11:58 192.168.122.209 [36469.036378] End test: cache.test_cache.TestQueryparamsAndRedirectH2.test_redirect_302_found Apr 26 02:11:58 192.168.122.209 [36469.054243] Start test: cache.test_cache.TestQueryparamsAndRedirectH2.test_redirect_303_see_other Apr 26 02:12:00 192.168.122.209 [36470.373746] [tdb] Start Tempesta DB Apr 26 02:12:00 192.168.122.209 [36470.515573] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:12:01 192.168.122.209 [36471.956654] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36471.956654] Maybe that's fine, but it's worth checking the [36471.956654] config - if there is no relations between the [36471.956654] names, then host name confusion attack is possible. Apr 26 02:12:01 192.168.122.209 [36472.051392] [tempesta fw] Configuration processing is completed. Apr 26 02:12:01 192.168.122.209 [36472.101319] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:12:02 192.168.122.209 [36472.521110] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:12:02 192.168.122.209 [36472.548015] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:12:02 192.168.122.209 [36472.574139] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:12:02 192.168.122.209 [36472.635353] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:12:02 192.168.122.209 [36472.636878] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:12:02 192.168.122.209 [36472.675342] [tempesta fw] Tempesta FW is ready Apr 26 02:12:03 192.168.122.209 [36473.328240] [tdb] Close table 'client0.tdb' Apr 26 02:12:03 192.168.122.209 [36473.545889] [tdb] Close table 'sessions0.tdb' Apr 26 02:12:06 192.168.122.209 [36476.784870] [tdb] Close table 'cache0.tdb' Apr 26 02:12:06 192.168.122.209 [36477.043602] [tdb] Close table 'filter0.tdb' Apr 26 02:12:06 192.168.122.209 [36477.044039] [tempesta fw] modules are stopped Apr 26 02:12:06 192.168.122.209 [36477.230059] [tempesta fw] exiting... Apr 26 02:12:07 192.168.122.209 [36477.414796] [tdb] Shutdown Tempesta DB Apr 26 02:12:07 192.168.122.209 [36477.670561] End test: cache.test_cache.TestQueryparamsAndRedirectH2.test_redirect_303_see_other Apr 26 02:12:07 192.168.122.209 [36477.680528] Start test: cache.test_cache.TestQueryparamsAndRedirectH2.test_redirect_304_not_modified Apr 26 02:12:08 192.168.122.209 [36479.001924] [tdb] Start Tempesta DB Apr 26 02:12:08 192.168.122.209 [36479.166324] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:12:10 192.168.122.209 [36480.652727] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36480.652727] Maybe that's fine, but it's worth checking the [36480.652727] config - if there is no relations between the [36480.652727] names, then host name confusion attack is possible. Apr 26 02:12:10 192.168.122.209 [36480.743410] [tempesta fw] Configuration processing is completed. Apr 26 02:12:10 192.168.122.209 [36480.800256] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:12:11 192.168.122.209 [36481.371503] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:12:11 192.168.122.209 [36481.405745] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:12:11 192.168.122.209 [36481.432554] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:12:11 192.168.122.209 [36481.471558] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:12:11 192.168.122.209 [36481.473314] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:12:11 192.168.122.209 [36481.511452] [tempesta fw] Tempesta FW is ready Apr 26 02:12:11 192.168.122.209 [36482.168804] [tdb] Close table 'client0.tdb' Apr 26 02:12:12 192.168.122.209 [36482.373480] [tdb] Close table 'sessions0.tdb' Apr 26 02:12:15 192.168.122.209 [36485.523791] [tdb] Close table 'cache0.tdb' Apr 26 02:12:15 192.168.122.209 [36485.763513] [tdb] Close table 'filter0.tdb' Apr 26 02:12:15 192.168.122.209 [36485.763952] [tempesta fw] modules are stopped Apr 26 02:12:15 192.168.122.209 [36486.016477] [tempesta fw] exiting... Apr 26 02:12:15 192.168.122.209 [36486.172540] [tdb] Shutdown Tempesta DB Apr 26 02:12:16 192.168.122.209 [36486.435071] End test: cache.test_cache.TestQueryparamsAndRedirectH2.test_redirect_304_not_modified Apr 26 02:12:16 192.168.122.209 [36486.453678] Start test: cache.test_cache.TestQueryparamsAndRedirectH2.test_redirect_305_user_proxy Apr 26 02:12:17 192.168.122.209 [36487.722110] [tdb] Start Tempesta DB Apr 26 02:12:17 192.168.122.209 [36487.875090] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:12:19 192.168.122.209 [36489.368827] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36489.368827] Maybe that's fine, but it's worth checking the [36489.368827] config - if there is no relations between the [36489.368827] names, then host name confusion attack is possible. Apr 26 02:12:19 192.168.122.209 [36489.455627] [tempesta fw] Configuration processing is completed. Apr 26 02:12:19 192.168.122.209 [36489.515446] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:12:19 192.168.122.209 [36490.070255] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:12:19 192.168.122.209 [36490.104046] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:12:19 192.168.122.209 [36490.137913] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:12:19 192.168.122.209 [36490.179513] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:12:19 192.168.122.209 [36490.180553] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:12:19 192.168.122.209 [36490.219507] [tempesta fw] Tempesta FW is ready Apr 26 02:12:20 192.168.122.209 [36490.887902] [tdb] Close table 'client0.tdb' Apr 26 02:12:20 192.168.122.209 [36491.078941] [tdb] Close table 'sessions0.tdb' Apr 26 02:12:24 192.168.122.209 [36494.390965] [tdb] Close table 'cache0.tdb' Apr 26 02:12:24 192.168.122.209 [36494.661342] [tdb] Close table 'filter0.tdb' Apr 26 02:12:24 192.168.122.209 [36494.661793] [tempesta fw] modules are stopped Apr 26 02:12:24 192.168.122.209 [36494.881443] [tempesta fw] exiting... Apr 26 02:12:24 192.168.122.209 [36495.044189] [tdb] Shutdown Tempesta DB Apr 26 02:12:25 192.168.122.209 [36495.291332] End test: cache.test_cache.TestQueryparamsAndRedirectH2.test_redirect_305_user_proxy Apr 26 02:12:25 192.168.122.209 [36495.305559] Start test: cache.test_cache.TestQueryparamsAndRedirectH2.test_redirect_307_temporary_redirect Apr 26 02:12:26 192.168.122.209 [36496.610150] [tdb] Start Tempesta DB Apr 26 02:12:26 192.168.122.209 [36496.747572] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:12:27 192.168.122.209 [36498.240973] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36498.240973] Maybe that's fine, but it's worth checking the [36498.240973] config - if there is no relations between the [36498.240973] names, then host name confusion attack is possible. Apr 26 02:12:28 192.168.122.209 [36498.331749] [tempesta fw] Configuration processing is completed. Apr 26 02:12:28 192.168.122.209 [36498.385689] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:12:28 192.168.122.209 [36498.820485] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:12:28 192.168.122.209 [36498.846814] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:12:28 192.168.122.209 [36498.880636] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:12:28 192.168.122.209 [36498.947766] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:12:28 192.168.122.209 [36498.949529] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:12:28 192.168.122.209 [36499.003689] [tempesta fw] Tempesta FW is ready Apr 26 02:12:29 192.168.122.209 [36499.664451] [tdb] Close table 'client0.tdb' Apr 26 02:12:29 192.168.122.209 [36499.866028] [tdb] Close table 'sessions0.tdb' Apr 26 02:12:32 192.168.122.209 [36503.063163] [tdb] Close table 'cache0.tdb' Apr 26 02:12:33 192.168.122.209 [36503.305706] [tdb] Close table 'filter0.tdb' Apr 26 02:12:33 192.168.122.209 [36503.306163] [tempesta fw] modules are stopped Apr 26 02:12:33 192.168.122.209 [36503.483657] [tempesta fw] exiting... Apr 26 02:12:33 192.168.122.209 [36503.614439] [tdb] Shutdown Tempesta DB Apr 26 02:12:33 192.168.122.209 [36503.836311] End test: cache.test_cache.TestQueryparamsAndRedirectH2.test_redirect_307_temporary_redirect Apr 26 02:12:33 192.168.122.209 [36503.856570] Start test: cache.test_cache.TestQueryparamsAndRedirectH2.test_redirect_308_permanent_redirect Apr 26 02:12:34 192.168.122.209 [36505.081533] [tdb] Start Tempesta DB Apr 26 02:12:34 192.168.122.209 [36505.232042] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:12:36 192.168.122.209 [36506.685123] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36506.685123] Maybe that's fine, but it's worth checking the [36506.685123] config - if there is no relations between the [36506.685123] names, then host name confusion attack is possible. Apr 26 02:12:36 192.168.122.209 [36506.783843] [tempesta fw] Configuration processing is completed. Apr 26 02:12:36 192.168.122.209 [36506.837444] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:12:37 192.168.122.209 [36507.291348] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:12:37 192.168.122.209 [36507.318778] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:12:37 192.168.122.209 [36507.347101] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:12:37 192.168.122.209 [36507.391841] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:12:37 192.168.122.209 [36507.393574] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:12:37 192.168.122.209 [36507.439726] [tempesta fw] Tempesta FW is ready Apr 26 02:12:37 192.168.122.209 [36508.090394] [tdb] Close table 'client0.tdb' Apr 26 02:12:38 192.168.122.209 [36508.288551] [tdb] Close table 'sessions0.tdb' Apr 26 02:12:41 192.168.122.209 [36511.529368] [tdb] Close table 'cache0.tdb' Apr 26 02:12:41 192.168.122.209 [36511.761667] [tdb] Close table 'filter0.tdb' Apr 26 02:12:41 192.168.122.209 [36511.762096] [tempesta fw] modules are stopped Apr 26 02:12:41 192.168.122.209 [36511.970039] [tempesta fw] exiting... Apr 26 02:12:41 192.168.122.209 [36512.126573] [tdb] Shutdown Tempesta DB Apr 26 02:12:42 192.168.122.209 [36512.351257] End test: cache.test_cache.TestQueryparamsAndRedirectH2.test_redirect_308_permanent_redirect Apr 26 02:12:42 192.168.122.209 [36512.371520] Start test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_query_param_different_key Apr 26 02:12:43 192.168.122.209 [36513.565539] [tdb] Start Tempesta DB Apr 26 02:12:43 192.168.122.209 [36513.720431] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:12:44 192.168.122.209 [36515.209213] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36515.209213] Maybe that's fine, but it's worth checking the [36515.209213] config - if there is no relations between the [36515.209213] names, then host name confusion attack is possible. Apr 26 02:12:45 192.168.122.209 [36515.291950] [tempesta fw] Configuration processing is completed. Apr 26 02:12:45 192.168.122.209 [36515.379507] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:12:45 192.168.122.209 [36515.816521] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:12:45 192.168.122.209 [36515.843042] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:12:45 192.168.122.209 [36515.869915] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:12:45 192.168.122.209 [36515.915980] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:12:45 192.168.122.209 [36515.917722] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:12:45 192.168.122.209 [36515.963889] [tempesta fw] Tempesta FW is ready Apr 26 02:12:46 192.168.122.209 [36516.630339] [tdb] Close table 'client0.tdb' Apr 26 02:12:46 192.168.122.209 [36516.824670] [tdb] Close table 'sessions0.tdb' Apr 26 02:12:49 192.168.122.209 [36520.034964] [tdb] Close table 'cache0.tdb' Apr 26 02:12:49 192.168.122.209 [36520.264647] [tdb] Close table 'filter0.tdb' Apr 26 02:12:49 192.168.122.209 [36520.265077] [tempesta fw] modules are stopped Apr 26 02:12:50 192.168.122.209 [36520.530923] [tempesta fw] exiting... Apr 26 02:12:50 192.168.122.209 [36520.701683] [tdb] Shutdown Tempesta DB Apr 26 02:12:50 192.168.122.209 [36520.933910] End test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_query_param_different_key Apr 26 02:12:50 192.168.122.209 [36520.952932] Start test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_query_param_different_value Apr 26 02:12:51 192.168.122.209 [36522.171543] [tdb] Start Tempesta DB Apr 26 02:12:52 192.168.122.209 [36522.319483] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:12:53 192.168.122.209 [36523.769372] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36523.769372] Maybe that's fine, but it's worth checking the [36523.769372] config - if there is no relations between the [36523.769372] names, then host name confusion attack is possible. Apr 26 02:12:53 192.168.122.209 [36523.864989] [tempesta fw] Configuration processing is completed. Apr 26 02:12:53 192.168.122.209 [36523.922131] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:12:54 192.168.122.209 [36524.362384] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:12:54 192.168.122.209 [36524.403621] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:12:54 192.168.122.209 [36524.430530] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:12:54 192.168.122.209 [36524.472089] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:12:54 192.168.122.209 [36524.473845] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:12:54 192.168.122.209 [36524.519971] [tempesta fw] Tempesta FW is ready Apr 26 02:12:54 192.168.122.209 [36525.180870] [tdb] Close table 'client0.tdb' Apr 26 02:12:55 192.168.122.209 [36525.391431] [tdb] Close table 'sessions0.tdb' Apr 26 02:12:58 192.168.122.209 [36528.563654] [tdb] Close table 'cache0.tdb' Apr 26 02:12:58 192.168.122.209 [36528.826733] [tdb] Close table 'filter0.tdb' Apr 26 02:12:58 192.168.122.209 [36528.827170] [tempesta fw] modules are stopped Apr 26 02:12:58 192.168.122.209 [36529.009101] [tempesta fw] exiting... Apr 26 02:12:58 192.168.122.209 [36529.168683] [tdb] Shutdown Tempesta DB Apr 26 02:12:59 192.168.122.209 [36529.426068] End test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_query_param_different_value Apr 26 02:12:59 192.168.122.209 [36529.445754] Start test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_query_param_same_params Apr 26 02:13:00 192.168.122.209 [36530.640315] [tdb] Start Tempesta DB Apr 26 02:13:00 192.168.122.209 [36530.796833] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:13:01 192.168.122.209 [36532.225462] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36532.225462] Maybe that's fine, but it's worth checking the [36532.225462] config - if there is no relations between the [36532.225462] names, then host name confusion attack is possible. Apr 26 02:13:02 192.168.122.209 [36532.316138] [tempesta fw] Configuration processing is completed. Apr 26 02:13:02 192.168.122.209 [36532.377072] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:13:02 192.168.122.209 [36532.833123] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:13:02 192.168.122.209 [36532.860981] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:13:02 192.168.122.209 [36532.888592] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:13:02 192.168.122.209 [36532.988177] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:13:02 192.168.122.209 [36532.989890] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:13:02 192.168.122.209 [36533.032110] [tempesta fw] Tempesta FW is ready Apr 26 02:13:03 192.168.122.209 [36533.642750] [tdb] Close table 'client0.tdb' Apr 26 02:13:03 192.168.122.209 [36533.849656] [tdb] Close table 'sessions0.tdb' Apr 26 02:13:06 192.168.122.209 [36537.068666] [tdb] Close table 'cache0.tdb' Apr 26 02:13:07 192.168.122.209 [36537.386828] [tdb] Close table 'filter0.tdb' Apr 26 02:13:07 192.168.122.209 [36537.387482] [tempesta fw] modules are stopped Apr 26 02:13:07 192.168.122.209 [36537.580357] [tempesta fw] exiting... Apr 26 02:13:07 192.168.122.209 [36537.725972] [tdb] Shutdown Tempesta DB Apr 26 02:13:07 192.168.122.209 [36537.933688] End test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_query_param_same_params Apr 26 02:13:07 192.168.122.209 [36537.957644] Start test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_query_param_with_new_param Apr 26 02:13:08 192.168.122.209 [36539.131388] [tdb] Start Tempesta DB Apr 26 02:13:09 192.168.122.209 [36539.284726] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:13:10 192.168.122.209 [36540.829519] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36540.829519] Maybe that's fine, but it's worth checking the [36540.829519] config - if there is no relations between the [36540.829519] names, then host name confusion attack is possible. Apr 26 02:13:10 192.168.122.209 [36540.916285] [tempesta fw] Configuration processing is completed. Apr 26 02:13:10 192.168.122.209 [36541.003562] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:13:11 192.168.122.209 [36541.443245] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:13:11 192.168.122.209 [36541.470602] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:13:11 192.168.122.209 [36541.498609] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:13:11 192.168.122.209 [36541.548300] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:13:11 192.168.122.209 [36541.550005] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:13:11 192.168.122.209 [36541.596242] [tempesta fw] Tempesta FW is ready Apr 26 02:13:11 192.168.122.209 [36542.223384] [tdb] Close table 'client0.tdb' Apr 26 02:13:12 192.168.122.209 [36542.419385] [tdb] Close table 'sessions0.tdb' Apr 26 02:13:15 192.168.122.209 [36545.603251] [tdb] Close table 'cache0.tdb' Apr 26 02:13:15 192.168.122.209 [36545.865332] [tdb] Close table 'filter0.tdb' Apr 26 02:13:15 192.168.122.209 [36545.865795] [tempesta fw] modules are stopped Apr 26 02:13:15 192.168.122.209 [36546.099100] [tempesta fw] exiting... Apr 26 02:13:15 192.168.122.209 [36546.259281] [tdb] Shutdown Tempesta DB Apr 26 02:13:16 192.168.122.209 [36546.496526] End test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_query_param_with_new_param Apr 26 02:13:16 192.168.122.209 [36546.509514] Start test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_redirect_300_multiple_choices Apr 26 02:13:17 192.168.122.209 [36547.686154] [tdb] Start Tempesta DB Apr 26 02:13:17 192.168.122.209 [36547.831808] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:13:18 192.168.122.209 [36549.245834] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36549.245834] Maybe that's fine, but it's worth checking the [36549.245834] config - if there is no relations between the [36549.245834] names, then host name confusion attack is possible. Apr 26 02:13:19 192.168.122.209 [36549.328428] [tempesta fw] Configuration processing is completed. Apr 26 02:13:19 192.168.122.209 [36549.384439] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:13:19 192.168.122.209 [36549.835734] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:13:19 192.168.122.209 [36549.871010] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:13:19 192.168.122.209 [36549.897506] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:13:19 192.168.122.209 [36549.948345] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:13:19 192.168.122.209 [36549.950452] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:13:19 192.168.122.209 [36549.988335] [tempesta fw] Tempesta FW is ready Apr 26 02:13:20 192.168.122.209 [36550.640118] [tdb] Close table 'client0.tdb' Apr 26 02:13:20 192.168.122.209 [36550.835494] [tdb] Close table 'sessions0.tdb' Apr 26 02:13:23 192.168.122.209 [36554.015892] [tdb] Close table 'cache0.tdb' Apr 26 02:13:24 192.168.122.209 [36554.296157] [tdb] Close table 'filter0.tdb' Apr 26 02:13:24 192.168.122.209 [36554.296605] [tempesta fw] modules are stopped Apr 26 02:13:24 192.168.122.209 [36554.518954] [tempesta fw] exiting... Apr 26 02:13:24 192.168.122.209 [36554.654221] [tdb] Shutdown Tempesta DB Apr 26 02:13:24 192.168.122.209 [36554.862863] End test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_redirect_300_multiple_choices Apr 26 02:13:24 192.168.122.209 [36554.880433] Start test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_redirect_301_moved_permanently Apr 26 02:13:25 192.168.122.209 [36556.090628] [tdb] Start Tempesta DB Apr 26 02:13:25 192.168.122.209 [36556.244062] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:13:27 192.168.122.209 [36557.665755] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36557.665755] Maybe that's fine, but it's worth checking the [36557.665755] config - if there is no relations between the [36557.665755] names, then host name confusion attack is possible. Apr 26 02:13:27 192.168.122.209 [36557.756523] [tempesta fw] Configuration processing is completed. Apr 26 02:13:27 192.168.122.209 [36557.813372] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:13:27 192.168.122.209 [36558.229175] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:13:27 192.168.122.209 [36558.255057] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:13:28 192.168.122.209 [36558.281191] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:13:28 192.168.122.209 [36558.320488] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:13:28 192.168.122.209 [36558.322236] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:13:28 192.168.122.209 [36558.360441] [tempesta fw] Tempesta FW is ready Apr 26 02:13:28 192.168.122.209 [36558.987929] [tdb] Close table 'client0.tdb' Apr 26 02:13:28 192.168.122.209 [36559.208033] [tdb] Close table 'sessions0.tdb' Apr 26 02:13:32 192.168.122.209 [36562.394639] [tdb] Close table 'cache0.tdb' Apr 26 02:13:32 192.168.122.209 [36562.643983] [tdb] Close table 'filter0.tdb' Apr 26 02:13:32 192.168.122.209 [36562.644440] [tempesta fw] modules are stopped Apr 26 02:13:32 192.168.122.209 [36562.835449] [tempesta fw] exiting... Apr 26 02:13:32 192.168.122.209 [36562.998910] [tdb] Shutdown Tempesta DB Apr 26 02:13:32 192.168.122.209 [36563.244439] End test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_redirect_301_moved_permanently Apr 26 02:13:33 192.168.122.209 [36563.271396] Start test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_redirect_302_found Apr 26 02:13:34 192.168.122.209 [36564.496834] [tdb] Start Tempesta DB Apr 26 02:13:34 192.168.122.209 [36564.660565] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:13:35 192.168.122.209 [36566.169848] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36566.169848] Maybe that's fine, but it's worth checking the [36566.169848] config - if there is no relations between the [36566.169848] names, then host name confusion attack is possible. Apr 26 02:13:35 192.168.122.209 [36566.260624] [tempesta fw] Configuration processing is completed. Apr 26 02:13:36 192.168.122.209 [36566.353332] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:13:36 192.168.122.209 [36566.782807] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:13:36 192.168.122.209 [36566.809642] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:13:36 192.168.122.209 [36566.844582] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:13:36 192.168.122.209 [36566.904607] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:13:36 192.168.122.209 [36566.906334] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:13:36 192.168.122.209 [36566.948594] [tempesta fw] Tempesta FW is ready Apr 26 02:13:37 192.168.122.209 [36567.574254] [tdb] Close table 'client0.tdb' Apr 26 02:13:37 192.168.122.209 [36567.790085] [tdb] Close table 'sessions0.tdb' Apr 26 02:13:40 192.168.122.209 [36570.959946] [tdb] Close table 'cache0.tdb' Apr 26 02:13:40 192.168.122.209 [36571.190015] [tdb] Close table 'filter0.tdb' Apr 26 02:13:40 192.168.122.209 [36571.190456] [tempesta fw] modules are stopped Apr 26 02:13:41 192.168.122.209 [36571.426578] [tempesta fw] exiting... Apr 26 02:13:41 192.168.122.209 [36571.565215] [tdb] Shutdown Tempesta DB Apr 26 02:13:41 192.168.122.209 [36571.777568] End test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_redirect_302_found Apr 26 02:13:41 192.168.122.209 [36571.804102] Start test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_redirect_303_see_other Apr 26 02:13:42 192.168.122.209 [36573.039178] [tdb] Start Tempesta DB Apr 26 02:13:42 192.168.122.209 [36573.184013] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:13:44 192.168.122.209 [36574.637963] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36574.637963] Maybe that's fine, but it's worth checking the [36574.637963] config - if there is no relations between the [36574.637963] names, then host name confusion attack is possible. Apr 26 02:13:44 192.168.122.209 [36574.720726] [tempesta fw] Configuration processing is completed. Apr 26 02:13:44 192.168.122.209 [36574.770152] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:13:44 192.168.122.209 [36575.194839] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:13:44 192.168.122.209 [36575.221478] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:13:44 192.168.122.209 [36575.247661] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:13:45 192.168.122.209 [36575.292732] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:13:45 192.168.122.209 [36575.294464] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:13:45 192.168.122.209 [36575.332677] [tempesta fw] Tempesta FW is ready Apr 26 02:13:45 192.168.122.209 [36575.967815] [tdb] Close table 'client0.tdb' Apr 26 02:13:45 192.168.122.209 [36576.159041] [tdb] Close table 'sessions0.tdb' Apr 26 02:13:49 192.168.122.209 [36579.335249] [tdb] Close table 'cache0.tdb' Apr 26 02:13:49 192.168.122.209 [36579.594782] [tdb] Close table 'filter0.tdb' Apr 26 02:13:49 192.168.122.209 [36579.595236] [tempesta fw] modules are stopped Apr 26 02:13:49 192.168.122.209 [36579.791082] [tempesta fw] exiting... Apr 26 02:13:49 192.168.122.209 [36579.942470] [tdb] Shutdown Tempesta DB Apr 26 02:13:49 192.168.122.209 [36580.146705] End test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_redirect_303_see_other Apr 26 02:13:49 192.168.122.209 [36580.160919] Start test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_redirect_304_not_modified Apr 26 02:13:51 192.168.122.209 [36581.339891] [tdb] Start Tempesta DB Apr 26 02:13:51 192.168.122.209 [36581.473056] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:13:52 192.168.122.209 [36582.874068] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36582.874068] Maybe that's fine, but it's worth checking the [36582.874068] config - if there is no relations between the [36582.874068] names, then host name confusion attack is possible. Apr 26 02:13:52 192.168.122.209 [36582.952839] [tempesta fw] Configuration processing is completed. Apr 26 02:13:52 192.168.122.209 [36583.003240] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:13:53 192.168.122.209 [36583.449331] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:13:53 192.168.122.209 [36583.480506] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:13:53 192.168.122.209 [36583.512420] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:13:53 192.168.122.209 [36583.556839] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:13:53 192.168.122.209 [36583.558567] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:13:53 192.168.122.209 [36583.596803] [tempesta fw] Tempesta FW is ready Apr 26 02:13:53 192.168.122.209 [36584.250420] [tdb] Close table 'client0.tdb' Apr 26 02:13:54 192.168.122.209 [36584.438711] [tdb] Close table 'sessions0.tdb' Apr 26 02:13:57 192.168.122.209 [36587.607520] [tdb] Close table 'cache0.tdb' Apr 26 02:13:57 192.168.122.209 [36587.843199] [tdb] Close table 'filter0.tdb' Apr 26 02:13:57 192.168.122.209 [36587.843630] [tempesta fw] modules are stopped Apr 26 02:13:57 192.168.122.209 [36588.043127] [tempesta fw] exiting... Apr 26 02:13:57 192.168.122.209 [36588.171139] [tdb] Shutdown Tempesta DB Apr 26 02:13:58 192.168.122.209 [36588.397810] End test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_redirect_304_not_modified Apr 26 02:13:58 192.168.122.209 [36588.422286] Start test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_redirect_305_user_proxy Apr 26 02:13:59 192.168.122.209 [36589.614330] [tdb] Start Tempesta DB Apr 26 02:13:59 192.168.122.209 [36589.781736] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:14:00 192.168.122.209 [36591.170166] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36591.170166] Maybe that's fine, but it's worth checking the [36591.170166] config - if there is no relations between the [36591.170166] names, then host name confusion attack is possible. Apr 26 02:14:00 192.168.122.209 [36591.256944] [tempesta fw] Configuration processing is completed. Apr 26 02:14:01 192.168.122.209 [36591.307822] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:14:01 192.168.122.209 [36591.727598] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:14:01 192.168.122.209 [36591.754161] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:14:01 192.168.122.209 [36591.781624] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:14:01 192.168.122.209 [36591.820894] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:14:01 192.168.122.209 [36591.822619] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:14:01 192.168.122.209 [36591.864803] [tempesta fw] Tempesta FW is ready Apr 26 02:14:02 192.168.122.209 [36592.485856] [tdb] Close table 'client0.tdb' Apr 26 02:14:02 192.168.122.209 [36592.670909] [tdb] Close table 'sessions0.tdb' Apr 26 02:14:05 192.168.122.209 [36595.892358] [tdb] Close table 'cache0.tdb' Apr 26 02:14:05 192.168.122.209 [36596.163830] [tdb] Close table 'filter0.tdb' Apr 26 02:14:05 192.168.122.209 [36596.164265] [tempesta fw] modules are stopped Apr 26 02:14:06 192.168.122.209 [36596.390220] [tempesta fw] exiting... Apr 26 02:14:06 192.168.122.209 [36596.522522] [tdb] Shutdown Tempesta DB Apr 26 02:14:06 192.168.122.209 [36596.727690] End test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_redirect_305_user_proxy Apr 26 02:14:06 192.168.122.209 [36596.748635] Start test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_redirect_307_temporary_redirect Apr 26 02:14:07 192.168.122.209 [36597.911640] [tdb] Start Tempesta DB Apr 26 02:14:07 192.168.122.209 [36598.058629] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:14:09 192.168.122.209 [36599.570379] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36599.570379] Maybe that's fine, but it's worth checking the [36599.570379] config - if there is no relations between the [36599.570379] names, then host name confusion attack is possible. Apr 26 02:14:09 192.168.122.209 [36599.661058] [tempesta fw] Configuration processing is completed. Apr 26 02:14:09 192.168.122.209 [36599.715163] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:14:09 192.168.122.209 [36600.158340] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:14:09 192.168.122.209 [36600.186087] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:14:09 192.168.122.209 [36600.214399] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:14:10 192.168.122.209 [36600.281027] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:14:10 192.168.122.209 [36600.282385] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:14:10 192.168.122.209 [36600.320986] [tempesta fw] Tempesta FW is ready Apr 26 02:14:10 192.168.122.209 [36600.908022] [tdb] Close table 'client0.tdb' Apr 26 02:14:10 192.168.122.209 [36601.113218] [tdb] Close table 'sessions0.tdb' Apr 26 02:14:14 192.168.122.209 [36604.268788] [tdb] Close table 'cache0.tdb' Apr 26 02:14:14 192.168.122.209 [36604.547628] [tdb] Close table 'filter0.tdb' Apr 26 02:14:14 192.168.122.209 [36604.548064] [tempesta fw] modules are stopped Apr 26 02:14:14 192.168.122.209 [36604.734589] [tempesta fw] exiting... Apr 26 02:14:14 192.168.122.209 [36604.893299] [tdb] Shutdown Tempesta DB Apr 26 02:14:14 192.168.122.209 [36605.109947] End test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_redirect_307_temporary_redirect Apr 26 02:14:14 192.168.122.209 [36605.130899] Start test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_redirect_308_permanent_redirect Apr 26 02:14:15 192.168.122.209 [36606.226409] [tdb] Start Tempesta DB Apr 26 02:14:16 192.168.122.209 [36606.374908] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:14:17 192.168.122.209 [36607.790485] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [36607.790485] Maybe that's fine, but it's worth checking the [36607.790485] config - if there is no relations between the [36607.790485] names, then host name confusion attack is possible. Apr 26 02:14:17 192.168.122.209 [36607.873173] [tempesta fw] Configuration processing is completed. Apr 26 02:14:17 192.168.122.209 [36607.932114] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:14:18 192.168.122.209 [36608.354823] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:14:18 192.168.122.209 [36608.381471] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:14:18 192.168.122.209 [36608.408296] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:14:18 192.168.122.209 [36608.477182] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:14:18 192.168.122.209 [36608.478951] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:14:18 192.168.122.209 [36608.529111] [tempesta fw] Tempesta FW is ready Apr 26 02:14:18 192.168.122.209 [36609.106888] [tdb] Close table 'client0.tdb' Apr 26 02:14:19 192.168.122.209 [36609.308600] [tdb] Close table 'sessions0.tdb' Apr 26 02:14:22 192.168.122.209 [36612.660952] [tdb] Close table 'cache0.tdb' Apr 26 02:14:22 192.168.122.209 [36612.877526] [tdb] Close table 'filter0.tdb' Apr 26 02:14:22 192.168.122.209 [36612.877984] [tempesta fw] modules are stopped Apr 26 02:14:22 192.168.122.209 [36613.085781] [tempesta fw] exiting... Apr 26 02:14:22 192.168.122.209 [36613.228355] [tdb] Shutdown Tempesta DB Apr 26 02:14:23 192.168.122.209 [36613.502879] End test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_redirect_308_permanent_redirect Apr 26 02:14:23 192.168.122.209 [36613.523132] Start test: cache.test_cache_control.CCArgBothNoCacheCached.test Apr 26 02:14:24 192.168.122.209 [36614.696147] [tdb] Start Tempesta DB Apr 26 02:14:24 192.168.122.209 [36614.836362] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:14:26 192.168.122.209 [36616.313227] [tempesta fw] Configuration processing is completed. Apr 26 02:14:26 192.168.122.209 [36616.364696] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:14:26 192.168.122.209 [36616.797378] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:14:26 192.168.122.209 [36616.825317] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:14:26 192.168.122.209 [36616.852395] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:14:26 192.168.122.209 [36616.905294] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:14:26 192.168.122.209 [36616.945222] [tempesta fw] Tempesta FW is ready Apr 26 02:14:27 192.168.122.209 [36617.567267] [tdb] Close table 'client0.tdb' Apr 26 02:14:27 192.168.122.209 [36617.760201] [tdb] Close table 'sessions0.tdb' Apr 26 02:14:30 192.168.122.209 [36620.939888] [tdb] Close table 'cache0.tdb' Apr 26 02:14:30 192.168.122.209 [36621.170943] [tdb] Close table 'filter0.tdb' Apr 26 02:14:30 192.168.122.209 [36621.171369] [tempesta fw] modules are stopped Apr 26 02:14:31 192.168.122.209 [36621.367337] [tempesta fw] exiting... Apr 26 02:14:31 192.168.122.209 [36621.519350] [tdb] Shutdown Tempesta DB Apr 26 02:14:31 192.168.122.209 [36621.744733] End test: cache.test_cache_control.CCArgBothNoCacheCached.test Apr 26 02:14:31 192.168.122.209 [36621.761490] Start test: cache.test_cache_control.CCArgNoCacheBypass.test Apr 26 02:14:32 192.168.122.209 [36622.932892] [tdb] Start Tempesta DB Apr 26 02:14:32 192.168.122.209 [36623.084575] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:14:34 192.168.122.209 [36624.569411] [tempesta fw] Configuration processing is completed. Apr 26 02:14:34 192.168.122.209 [36624.620228] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:14:34 192.168.122.209 [36625.039869] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:14:34 192.168.122.209 [36625.066081] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:14:34 192.168.122.209 [36625.092162] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:14:34 192.168.122.209 [36625.133329] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:14:34 192.168.122.209 [36625.189321] [tempesta fw] Tempesta FW is ready Apr 26 02:14:35 192.168.122.209 [36625.791118] [tdb] Close table 'client0.tdb' Apr 26 02:14:35 192.168.122.209 [36625.985468] [tdb] Close table 'sessions0.tdb' Apr 26 02:14:38 192.168.122.209 [36629.156947] [tdb] Close table 'cache0.tdb' Apr 26 02:14:39 192.168.122.209 [36629.390011] [tdb] Close table 'filter0.tdb' Apr 26 02:14:39 192.168.122.209 [36629.390445] [tempesta fw] modules are stopped Apr 26 02:14:39 192.168.122.209 [36629.608473] [tempesta fw] exiting... Apr 26 02:14:39 192.168.122.209 [36629.771106] [tdb] Shutdown Tempesta DB Apr 26 02:14:39 192.168.122.209 [36629.991491] End test: cache.test_cache_control.CCArgNoCacheBypass.test Apr 26 02:14:39 192.168.122.209 [36630.002950] Start test: cache.test_cache_control.CCArgNoCacheCached.test Apr 26 02:14:40 192.168.122.209 [36631.170569] [tdb] Start Tempesta DB Apr 26 02:14:41 192.168.122.209 [36631.321693] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:14:42 192.168.122.209 [36632.845533] [tempesta fw] Configuration processing is completed. Apr 26 02:14:42 192.168.122.209 [36632.929981] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:14:43 192.168.122.209 [36633.363891] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:14:43 192.168.122.209 [36633.391284] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:14:43 192.168.122.209 [36633.418545] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:14:43 192.168.122.209 [36633.473500] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:14:43 192.168.122.209 [36633.521459] [tempesta fw] Tempesta FW is ready Apr 26 02:14:43 192.168.122.209 [36634.154163] [tdb] Close table 'client0.tdb' Apr 26 02:14:44 192.168.122.209 [36634.366283] [tdb] Close table 'sessions0.tdb' Apr 26 02:14:47 192.168.122.209 [36637.515394] [tdb] Close table 'cache0.tdb' Apr 26 02:14:47 192.168.122.209 [36637.777209] [tdb] Close table 'filter0.tdb' Apr 26 02:14:47 192.168.122.209 [36637.777661] [tempesta fw] modules are stopped Apr 26 02:14:47 192.168.122.209 [36637.986197] [tempesta fw] exiting... Apr 26 02:14:47 192.168.122.209 [36638.125071] [tdb] Shutdown Tempesta DB Apr 26 02:14:48 192.168.122.209 [36638.355278] End test: cache.test_cache_control.CCArgNoCacheCached.test Apr 26 02:14:48 192.168.122.209 [36638.381579] Start test: cache.test_cache_control.CCArgNoCacheCached2.test Apr 26 02:14:49 192.168.122.209 [36639.564545] [tdb] Start Tempesta DB Apr 26 02:14:49 192.168.122.209 [36639.702053] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:14:50 192.168.122.209 [36641.233623] [tempesta fw] Configuration processing is completed. Apr 26 02:14:51 192.168.122.209 [36641.282927] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:14:51 192.168.122.209 [36641.701429] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:14:51 192.168.122.209 [36641.727852] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:14:51 192.168.122.209 [36641.753804] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:14:51 192.168.122.209 [36641.809594] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:14:51 192.168.122.209 [36641.861527] [tempesta fw] Tempesta FW is ready Apr 26 02:14:52 192.168.122.209 [36642.488734] [tdb] Close table 'client0.tdb' Apr 26 02:14:52 192.168.122.209 [36642.680446] [tdb] Close table 'sessions0.tdb' Apr 26 02:14:55 192.168.122.209 [36645.916414] [tdb] Close table 'cache0.tdb' Apr 26 02:14:55 192.168.122.209 [36646.159965] [tdb] Close table 'filter0.tdb' Apr 26 02:14:55 192.168.122.209 [36646.160418] [tempesta fw] modules are stopped Apr 26 02:14:56 192.168.122.209 [36646.345246] [tempesta fw] exiting... Apr 26 02:14:56 192.168.122.209 [36646.487882] [tdb] Shutdown Tempesta DB Apr 26 02:14:56 192.168.122.209 [36646.710918] End test: cache.test_cache_control.CCArgNoCacheCached2.test Apr 26 02:14:56 192.168.122.209 [36646.722088] Start test: cache.test_cache_control.CCArgNoCacheCached3.test Apr 26 02:14:57 192.168.122.209 [36647.934590] [tdb] Start Tempesta DB Apr 26 02:14:57 192.168.122.209 [36648.080150] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:14:59 192.168.122.209 [36649.610404] [tempesta fw] Configuration processing is completed. Apr 26 02:14:59 192.168.122.209 [36649.663640] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:14:59 192.168.122.209 [36650.114532] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:14:59 192.168.122.209 [36650.140810] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:14:59 192.168.122.209 [36650.166682] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:14:59 192.168.122.209 [36650.205702] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:14:59 192.168.122.209 [36650.245654] [tempesta fw] Tempesta FW is ready Apr 26 02:15:00 192.168.122.209 [36650.861020] [tdb] Close table 'client0.tdb' Apr 26 02:15:00 192.168.122.209 [36651.036524] [tdb] Close table 'sessions0.tdb' Apr 26 02:15:04 192.168.122.209 [36654.379854] [tdb] Close table 'cache0.tdb' Apr 26 02:15:04 192.168.122.209 [36654.619229] [tdb] Close table 'filter0.tdb' Apr 26 02:15:04 192.168.122.209 [36654.619669] [tempesta fw] modules are stopped Apr 26 02:15:04 192.168.122.209 [36654.826445] [tempesta fw] exiting... Apr 26 02:15:04 192.168.122.209 [36654.979727] [tdb] Shutdown Tempesta DB Apr 26 02:15:04 192.168.122.209 [36655.182898] End test: cache.test_cache_control.CCArgNoCacheCached3.test Apr 26 02:15:04 192.168.122.209 [36655.193412] Start test: cache.test_cache_control.CCArgPrivateBypass.test Apr 26 02:15:06 192.168.122.209 [36656.351654] [tdb] Start Tempesta DB Apr 26 02:15:06 192.168.122.209 [36656.494661] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:15:07 192.168.122.209 [36658.033954] [tempesta fw] Configuration processing is completed. Apr 26 02:15:07 192.168.122.209 [36658.084492] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:15:08 192.168.122.209 [36658.512377] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:15:08 192.168.122.209 [36658.538116] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:15:08 192.168.122.209 [36658.564632] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:15:08 192.168.122.209 [36658.621812] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:15:08 192.168.122.209 [36658.661750] [tempesta fw] Tempesta FW is ready Apr 26 02:15:08 192.168.122.209 [36659.262346] [tdb] Close table 'client0.tdb' Apr 26 02:15:09 192.168.122.209 [36659.446871] [tdb] Close table 'sessions0.tdb' Apr 26 02:15:12 192.168.122.209 [36662.654486] [tdb] Close table 'cache0.tdb' Apr 26 02:15:12 192.168.122.209 [36662.913806] [tdb] Close table 'filter0.tdb' Apr 26 02:15:12 192.168.122.209 [36662.914252] [tempesta fw] modules are stopped Apr 26 02:15:12 192.168.122.209 [36663.088076] [tempesta fw] exiting... Apr 26 02:15:12 192.168.122.209 [36663.228822] [tdb] Shutdown Tempesta DB Apr 26 02:15:13 192.168.122.209 [36663.436250] End test: cache.test_cache_control.CCArgPrivateBypass.test Apr 26 02:15:13 192.168.122.209 [36663.468543] Start test: cache.test_cache_control.CCArgPrivateCached.test Apr 26 02:15:14 192.168.122.209 [36664.619755] [tdb] Start Tempesta DB Apr 26 02:15:14 192.168.122.209 [36664.756709] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:15:15 192.168.122.209 [36666.237974] [tempesta fw] Configuration processing is completed. Apr 26 02:15:16 192.168.122.209 [36666.288741] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:15:16 192.168.122.209 [36666.721994] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:15:16 192.168.122.209 [36666.757340] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:15:16 192.168.122.209 [36666.784112] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:15:16 192.168.122.209 [36666.833902] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:15:16 192.168.122.209 [36666.877852] [tempesta fw] Tempesta FW is ready Apr 26 02:15:17 192.168.122.209 [36667.474853] [tdb] Close table 'client0.tdb' Apr 26 02:15:17 192.168.122.209 [36667.694657] [tdb] Close table 'sessions0.tdb' Apr 26 02:15:20 192.168.122.209 [36670.893590] [tdb] Close table 'cache0.tdb' Apr 26 02:15:20 192.168.122.209 [36671.126341] [tdb] Close table 'filter0.tdb' Apr 26 02:15:20 192.168.122.209 [36671.126781] [tempesta fw] modules are stopped Apr 26 02:15:21 192.168.122.209 [36671.310204] [tempesta fw] exiting... Apr 26 02:15:21 192.168.122.209 [36671.448589] [tdb] Shutdown Tempesta DB Apr 26 02:15:21 192.168.122.209 [36671.708394] End test: cache.test_cache_control.CCArgPrivateCached.test Apr 26 02:15:21 192.168.122.209 [36671.729020] Start test: cache.test_cache_control.CCArgPrivateCached2.test Apr 26 02:15:22 192.168.122.209 [36672.985422] [tdb] Start Tempesta DB Apr 26 02:15:22 192.168.122.209 [36673.122907] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:15:24 192.168.122.209 [36674.666059] [tempesta fw] Configuration processing is completed. Apr 26 02:15:24 192.168.122.209 [36674.725993] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:15:24 192.168.122.209 [36675.153383] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:15:24 192.168.122.209 [36675.179941] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:15:24 192.168.122.209 [36675.206109] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:15:24 192.168.122.209 [36675.254027] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:15:25 192.168.122.209 [36675.293998] [tempesta fw] Tempesta FW is ready Apr 26 02:15:25 192.168.122.209 [36675.920792] [tdb] Close table 'client0.tdb' Apr 26 02:15:25 192.168.122.209 [36676.112132] [tdb] Close table 'sessions0.tdb' Apr 26 02:15:29 192.168.122.209 [36679.270875] [tdb] Close table 'cache0.tdb' Apr 26 02:15:29 192.168.122.209 [36679.539373] [tdb] Close table 'filter0.tdb' Apr 26 02:15:29 192.168.122.209 [36679.539798] [tempesta fw] modules are stopped Apr 26 02:15:29 192.168.122.209 [36679.730300] [tempesta fw] exiting... Apr 26 02:15:29 192.168.122.209 [36679.861812] [tdb] Shutdown Tempesta DB Apr 26 02:15:29 192.168.122.209 [36680.085032] End test: cache.test_cache_control.CCArgPrivateCached2.test Apr 26 02:15:29 192.168.122.209 [36680.097700] Start test: cache.test_cache_control.CacheHdrDelBypass.test Apr 26 02:15:31 192.168.122.209 [36681.304307] [tdb] Start Tempesta DB Apr 26 02:15:31 192.168.122.209 [36681.447962] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:15:32 192.168.122.209 [36682.974158] [tempesta fw] Configuration processing is completed. Apr 26 02:15:32 192.168.122.209 [36683.023168] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:15:33 192.168.122.209 [36683.462501] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:15:33 192.168.122.209 [36683.496066] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:15:33 192.168.122.209 [36683.522756] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:15:33 192.168.122.209 [36683.590125] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:15:33 192.168.122.209 [36683.630105] [tempesta fw] Tempesta FW is ready Apr 26 02:15:33 192.168.122.209 [36684.209562] [tdb] Close table 'client0.tdb' Apr 26 02:15:34 192.168.122.209 [36684.408377] [tdb] Close table 'sessions0.tdb' Apr 26 02:15:37 192.168.122.209 [36687.572429] [tdb] Close table 'cache0.tdb' Apr 26 02:15:37 192.168.122.209 [36687.812545] [tdb] Close table 'filter0.tdb' Apr 26 02:15:37 192.168.122.209 [36687.812978] [tempesta fw] modules are stopped Apr 26 02:15:37 192.168.122.209 [36688.035236] [tempesta fw] exiting... Apr 26 02:15:37 192.168.122.209 [36688.205409] [tdb] Shutdown Tempesta DB Apr 26 02:15:38 192.168.122.209 [36688.425889] End test: cache.test_cache_control.CacheHdrDelBypass.test Apr 26 02:15:38 192.168.122.209 [36688.438689] Start test: cache.test_cache_control.CacheHdrDelCached.test Apr 26 02:15:39 192.168.122.209 [36689.614352] [tdb] Start Tempesta DB Apr 26 02:15:39 192.168.122.209 [36689.753132] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:15:41 192.168.122.209 [36691.282279] [tempesta fw] Configuration processing is completed. Apr 26 02:15:41 192.168.122.209 [36691.332874] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:15:41 192.168.122.209 [36691.758021] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:15:41 192.168.122.209 [36691.792851] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:15:41 192.168.122.209 [36691.818949] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:15:41 192.168.122.209 [36691.874241] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:15:41 192.168.122.209 [36691.922187] [tempesta fw] Tempesta FW is ready Apr 26 02:15:42 192.168.122.209 [36692.522649] [tdb] Close table 'client0.tdb' Apr 26 02:15:42 192.168.122.209 [36692.720434] [tdb] Close table 'sessions0.tdb' Apr 26 02:15:45 192.168.122.209 [36695.973650] [tdb] Close table 'cache0.tdb' Apr 26 02:15:45 192.168.122.209 [36696.234946] [tdb] Close table 'filter0.tdb' Apr 26 02:15:45 192.168.122.209 [36696.235381] [tempesta fw] modules are stopped Apr 26 02:15:46 192.168.122.209 [36696.435530] [tempesta fw] exiting... Apr 26 02:15:46 192.168.122.209 [36696.559291] [tdb] Shutdown Tempesta DB Apr 26 02:15:46 192.168.122.209 [36696.778251] End test: cache.test_cache_control.CacheHdrDelCached.test Apr 26 02:15:46 192.168.122.209 [36696.796564] Start test: cache.test_cache_control.CacheHdrDelCached2.test Apr 26 02:15:47 192.168.122.209 [36697.973859] [tdb] Start Tempesta DB Apr 26 02:15:47 192.168.122.209 [36698.118885] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:15:49 192.168.122.209 [36699.658429] [tempesta fw] Configuration processing is completed. Apr 26 02:15:49 192.168.122.209 [36699.708330] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:15:49 192.168.122.209 [36700.138020] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:15:49 192.168.122.209 [36700.174402] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:15:49 192.168.122.209 [36700.201616] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:15:49 192.168.122.209 [36700.238276] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:15:50 192.168.122.209 [36700.278228] [tempesta fw] Tempesta FW is ready Apr 26 02:15:50 192.168.122.209 [36700.887854] [tdb] Close table 'client0.tdb' Apr 26 02:15:50 192.168.122.209 [36701.088114] [tdb] Close table 'sessions0.tdb' Apr 26 02:15:54 192.168.122.209 [36704.267479] [tdb] Close table 'cache0.tdb' Apr 26 02:15:54 192.168.122.209 [36704.495812] [tdb] Close table 'filter0.tdb' Apr 26 02:15:54 192.168.122.209 [36704.496265] [tempesta fw] modules are stopped Apr 26 02:15:54 192.168.122.209 [36704.708994] [tempesta fw] exiting... Apr 26 02:15:54 192.168.122.209 [36704.877720] [tdb] Shutdown Tempesta DB Apr 26 02:15:54 192.168.122.209 [36705.097853] End test: cache.test_cache_control.CacheHdrDelCached2.test Apr 26 02:15:54 192.168.122.209 [36705.124335] Start test: cache.test_cache_control.CacheTtlGlobalApplied.test Apr 26 02:15:56 192.168.122.209 [36706.268763] [tdb] Start Tempesta DB Apr 26 02:15:56 192.168.122.209 [36706.414083] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:15:57 192.168.122.209 [36707.982541] [tempesta fw] Configuration processing is completed. Apr 26 02:15:57 192.168.122.209 [36708.037407] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:15:58 192.168.122.209 [36708.466144] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:15:58 192.168.122.209 [36708.492456] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:15:58 192.168.122.209 [36708.519156] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:15:58 192.168.122.209 [36708.570410] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:15:58 192.168.122.209 [36708.610404] [tempesta fw] Tempesta FW is ready Apr 26 02:16:00 192.168.122.209 [36711.199722] [tdb] Close table 'client0.tdb' Apr 26 02:16:01 192.168.122.209 [36711.379063] [tdb] Close table 'sessions0.tdb' Apr 26 02:16:04 192.168.122.209 [36714.610584] [tdb] Close table 'cache0.tdb' Apr 26 02:16:04 192.168.122.209 [36714.872428] [tdb] Close table 'filter0.tdb' Apr 26 02:16:04 192.168.122.209 [36714.872855] [tempesta fw] modules are stopped Apr 26 02:16:04 192.168.122.209 [36715.071227] [tempesta fw] exiting... Apr 26 02:16:04 192.168.122.209 [36715.244013] [tdb] Shutdown Tempesta DB Apr 26 02:16:05 192.168.122.209 [36715.479944] End test: cache.test_cache_control.CacheTtlGlobalApplied.test Apr 26 02:16:05 192.168.122.209 [36715.493089] Start test: cache.test_cache_control.CacheTtlGlobalApplied2.test Apr 26 02:16:06 192.168.122.209 [36716.684349] [tdb] Start Tempesta DB Apr 26 02:16:06 192.168.122.209 [36716.847321] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:16:08 192.168.122.209 [36718.390624] [tempesta fw] Configuration processing is completed. Apr 26 02:16:08 192.168.122.209 [36718.441793] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:16:08 192.168.122.209 [36718.877963] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:16:08 192.168.122.209 [36718.904060] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:16:08 192.168.122.209 [36718.930922] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:16:08 192.168.122.209 [36718.978595] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:16:08 192.168.122.209 [36719.022536] [tempesta fw] Tempesta FW is ready Apr 26 02:16:12 192.168.122.209 [36722.654707] [tdb] Close table 'client0.tdb' Apr 26 02:16:12 192.168.122.209 [36722.831258] [tdb] Close table 'sessions0.tdb' Apr 26 02:16:15 192.168.122.209 [36726.064390] [tdb] Close table 'cache0.tdb' Apr 26 02:16:16 192.168.122.209 [36726.294621] [tdb] Close table 'filter0.tdb' Apr 26 02:16:16 192.168.122.209 [36726.295071] [tempesta fw] modules are stopped Apr 26 02:16:16 192.168.122.209 [36726.496057] [tempesta fw] exiting... Apr 26 02:16:16 192.168.122.209 [36726.643584] [tdb] Shutdown Tempesta DB Apr 26 02:16:16 192.168.122.209 [36726.850661] End test: cache.test_cache_control.CacheTtlGlobalApplied2.test Apr 26 02:16:16 192.168.122.209 [36726.870605] Start test: cache.test_cache_control.CacheTtlGlobalHonourMaxAge.test Apr 26 02:16:17 192.168.122.209 [36728.050210] [tdb] Start Tempesta DB Apr 26 02:16:17 192.168.122.209 [36728.196993] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:16:19 192.168.122.209 [36729.694778] [tempesta fw] Configuration processing is completed. Apr 26 02:16:19 192.168.122.209 [36729.752723] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:16:19 192.168.122.209 [36730.170423] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:16:19 192.168.122.209 [36730.201045] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:16:19 192.168.122.209 [36730.227243] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:16:20 192.168.122.209 [36730.270734] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:16:20 192.168.122.209 [36730.318677] [tempesta fw] Tempesta FW is ready Apr 26 02:16:23 192.168.122.209 [36733.937012] [tdb] Close table 'client0.tdb' Apr 26 02:16:23 192.168.122.209 [36734.133295] [tdb] Close table 'sessions0.tdb' Apr 26 02:16:27 192.168.122.209 [36737.278028] [tdb] Close table 'cache0.tdb' Apr 26 02:16:27 192.168.122.209 [36737.532422] [tdb] Close table 'filter0.tdb' Apr 26 02:16:27 192.168.122.209 [36737.532887] [tempesta fw] modules are stopped Apr 26 02:16:27 192.168.122.209 [36737.731603] [tempesta fw] exiting... Apr 26 02:16:27 192.168.122.209 [36737.860404] [tdb] Shutdown Tempesta DB Apr 26 02:16:27 192.168.122.209 [36738.059446] End test: cache.test_cache_control.CacheTtlGlobalHonourMaxAge.test Apr 26 02:16:27 192.168.122.209 [36738.069634] Start test: cache.test_cache_control.CacheTtlGlobalHonourMaxAge2.test Apr 26 02:16:29 192.168.122.209 [36739.307440] [tdb] Start Tempesta DB Apr 26 02:16:29 192.168.122.209 [36739.473972] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:16:30 192.168.122.209 [36741.086902] [tempesta fw] Configuration processing is completed. Apr 26 02:16:30 192.168.122.209 [36741.138031] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:16:31 192.168.122.209 [36741.583583] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:16:31 192.168.122.209 [36741.610275] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:16:31 192.168.122.209 [36741.637229] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:16:31 192.168.122.209 [36741.682877] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:16:31 192.168.122.209 [36741.718831] [tempesta fw] Tempesta FW is ready Apr 26 02:16:35 192.168.122.209 [36745.330133] [tdb] Close table 'client0.tdb' Apr 26 02:16:35 192.168.122.209 [36745.525912] [tdb] Close table 'sessions0.tdb' Apr 26 02:16:38 192.168.122.209 [36748.734863] [tdb] Close table 'cache0.tdb' Apr 26 02:16:38 192.168.122.209 [36748.986816] [tdb] Close table 'filter0.tdb' Apr 26 02:16:38 192.168.122.209 [36748.987237] [tempesta fw] modules are stopped Apr 26 02:16:38 192.168.122.209 [36749.162732] [tempesta fw] exiting... Apr 26 02:16:39 192.168.122.209 [36749.298695] [tdb] Shutdown Tempesta DB Apr 26 02:16:39 192.168.122.209 [36749.539247] End test: cache.test_cache_control.CacheTtlGlobalHonourMaxAge2.test Apr 26 02:16:39 192.168.122.209 [36749.555834] Start test: cache.test_cache_control.CacheTtlHonourNoCache.test Apr 26 02:16:40 192.168.122.209 [36750.755913] [tdb] Start Tempesta DB Apr 26 02:16:40 192.168.122.209 [36750.912681] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:16:42 192.168.122.209 [36752.523061] [tempesta fw] Configuration processing is completed. Apr 26 02:16:42 192.168.122.209 [36752.575734] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:16:42 192.168.122.209 [36753.029795] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:16:42 192.168.122.209 [36753.058291] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:16:42 192.168.122.209 [36753.086556] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:16:42 192.168.122.209 [36753.142986] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:16:42 192.168.122.209 [36753.182916] [tempesta fw] Tempesta FW is ready Apr 26 02:16:45 192.168.122.209 [36755.839166] [tdb] Close table 'client0.tdb' Apr 26 02:16:45 192.168.122.209 [36756.024748] [tdb] Close table 'sessions0.tdb' Apr 26 02:16:48 192.168.122.209 [36759.195947] [tdb] Close table 'cache0.tdb' Apr 26 02:16:49 192.168.122.209 [36759.439025] [tdb] Close table 'filter0.tdb' Apr 26 02:16:49 192.168.122.209 [36759.439483] [tempesta fw] modules are stopped Apr 26 02:16:49 192.168.122.209 [36759.636462] [tempesta fw] exiting... Apr 26 02:16:49 192.168.122.209 [36759.813704] [tdb] Shutdown Tempesta DB Apr 26 02:16:49 192.168.122.209 [36760.004435] End test: cache.test_cache_control.CacheTtlHonourNoCache.test Apr 26 02:16:49 192.168.122.209 [36760.021886] Start test: cache.test_cache_control.CacheTtlHttpChainHonourMaxAge.test Apr 26 02:16:50 192.168.122.209 [36761.210317] [tdb] Start Tempesta DB Apr 26 02:16:51 192.168.122.209 [36761.368126] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:16:52 192.168.122.209 [36762.995202] [tempesta fw] Configuration processing is completed. Apr 26 02:16:52 192.168.122.209 [36763.049879] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:16:53 192.168.122.209 [36763.487660] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:16:53 192.168.122.209 [36763.514772] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:16:53 192.168.122.209 [36763.547037] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:16:53 192.168.122.209 [36763.587163] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:16:53 192.168.122.209 [36763.627109] [tempesta fw] Tempesta FW is ready Apr 26 02:16:58 192.168.122.209 [36768.270375] [tdb] Close table 'client0.tdb' Apr 26 02:16:58 192.168.122.209 [36768.455816] [tdb] Close table 'sessions0.tdb' Apr 26 02:17:01 192.168.122.209 [36771.650413] [tdb] Close table 'cache0.tdb' Apr 26 02:17:01 192.168.122.209 [36771.875847] [tdb] Close table 'filter0.tdb' Apr 26 02:17:01 192.168.122.209 [36771.876291] [tempesta fw] modules are stopped Apr 26 02:17:01 192.168.122.209 [36772.115419] [tempesta fw] exiting... Apr 26 02:17:01 192.168.122.209 [36772.257969] [tdb] Shutdown Tempesta DB Apr 26 02:17:02 192.168.122.209 [36772.484581] End test: cache.test_cache_control.CacheTtlHttpChainHonourMaxAge.test Apr 26 02:17:02 192.168.122.209 [36772.515226] Start test: cache.test_cache_control.CacheTtlHttpChainOverride.test Apr 26 02:17:03 192.168.122.209 [36773.683657] [tdb] Start Tempesta DB Apr 26 02:17:03 192.168.122.209 [36773.841793] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:17:05 192.168.122.209 [36775.547406] [tempesta fw] Configuration processing is completed. Apr 26 02:17:05 192.168.122.209 [36775.598670] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:17:05 192.168.122.209 [36776.025487] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:17:05 192.168.122.209 [36776.060496] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:17:05 192.168.122.209 [36776.089393] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:17:05 192.168.122.209 [36776.127358] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:17:05 192.168.122.209 [36776.171232] [tempesta fw] Tempesta FW is ready Apr 26 02:17:08 192.168.122.209 [36778.765136] [tdb] Close table 'client0.tdb' Apr 26 02:17:08 192.168.122.209 [36778.929920] [tdb] Close table 'sessions0.tdb' Apr 26 02:17:11 192.168.122.209 [36782.141973] [tdb] Close table 'cache0.tdb' Apr 26 02:17:12 192.168.122.209 [36782.403901] [tdb] Close table 'filter0.tdb' Apr 26 02:17:12 192.168.122.209 [36782.404353] [tempesta fw] modules are stopped Apr 26 02:17:12 192.168.122.209 [36782.632784] [tempesta fw] exiting... Apr 26 02:17:12 192.168.122.209 [36782.766301] [tdb] Shutdown Tempesta DB Apr 26 02:17:12 192.168.122.209 [36783.007775] End test: cache.test_cache_control.CacheTtlHttpChainOverride.test Apr 26 02:17:12 192.168.122.209 [36783.025564] Start test: cache.test_cache_control.HttpChainCacheActionBypass.test Apr 26 02:17:13 192.168.122.209 [36784.190102] [tdb] Start Tempesta DB Apr 26 02:17:14 192.168.122.209 [36784.336375] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:17:15 192.168.122.209 [36785.963478] [tempesta fw] Configuration processing is completed. Apr 26 02:17:15 192.168.122.209 [36786.017355] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:17:16 192.168.122.209 [36786.450667] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:17:16 192.168.122.209 [36786.478617] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:17:16 192.168.122.209 [36786.505206] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:17:16 192.168.122.209 [36786.579576] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:17:16 192.168.122.209 [36786.635421] [tempesta fw] Tempesta FW is ready Apr 26 02:17:16 192.168.122.209 [36787.236460] [tdb] Close table 'client0.tdb' Apr 26 02:17:17 192.168.122.209 [36787.484952] [tdb] Close table 'sessions0.tdb' Apr 26 02:17:20 192.168.122.209 [36790.698806] [tdb] Close table 'cache0.tdb' Apr 26 02:17:20 192.168.122.209 [36790.951377] [tdb] Close table 'filter0.tdb' Apr 26 02:17:20 192.168.122.209 [36790.951811] [tempesta fw] modules are stopped Apr 26 02:17:20 192.168.122.209 [36791.153129] [tempesta fw] exiting... Apr 26 02:17:21 192.168.122.209 [36791.283489] [tdb] Shutdown Tempesta DB Apr 26 02:17:21 192.168.122.209 [36791.510174] End test: cache.test_cache_control.HttpChainCacheActionBypass.test Apr 26 02:17:21 192.168.122.209 [36791.530378] Start test: cache.test_cache_control.HttpChainCacheActionCached.test Apr 26 02:17:22 192.168.122.209 [36792.751111] [tdb] Start Tempesta DB Apr 26 02:17:22 192.168.122.209 [36792.899405] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:17:24 192.168.122.209 [36794.567661] [tempesta fw] Configuration processing is completed. Apr 26 02:17:24 192.168.122.209 [36794.619102] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:17:24 192.168.122.209 [36795.042098] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:17:24 192.168.122.209 [36795.068324] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:17:24 192.168.122.209 [36795.099518] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:17:24 192.168.122.209 [36795.143579] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:17:24 192.168.122.209 [36795.183539] [tempesta fw] Tempesta FW is ready Apr 26 02:17:25 192.168.122.209 [36795.778928] [tdb] Close table 'client0.tdb' Apr 26 02:17:25 192.168.122.209 [36795.992270] [tdb] Close table 'sessions0.tdb' Apr 26 02:17:28 192.168.122.209 [36799.169229] [tdb] Close table 'cache0.tdb' Apr 26 02:17:29 192.168.122.209 [36799.384458] [tdb] Close table 'filter0.tdb' Apr 26 02:17:29 192.168.122.209 [36799.384897] [tempesta fw] modules are stopped Apr 26 02:17:29 192.168.122.209 [36799.585713] [tempesta fw] exiting... Apr 26 02:17:29 192.168.122.209 [36799.738177] [tdb] Shutdown Tempesta DB Apr 26 02:17:29 192.168.122.209 [36799.981216] End test: cache.test_cache_control.HttpChainCacheActionCached.test Apr 26 02:17:29 192.168.122.209 [36799.998634] Start test: cache.test_cache_control.HttpChainCacheActionOverrideBypass.test Apr 26 02:17:30 192.168.122.209 [36801.182332] [tdb] Start Tempesta DB Apr 26 02:17:31 192.168.122.209 [36801.344063] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:17:32 192.168.122.209 [36803.091682] [tempesta fw] Configuration processing is completed. Apr 26 02:17:32 192.168.122.209 [36803.145090] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:17:33 192.168.122.209 [36803.555146] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:17:33 192.168.122.209 [36803.583082] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:17:33 192.168.122.209 [36803.608392] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:17:33 192.168.122.209 [36803.667636] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:17:33 192.168.122.209 [36803.707632] [tempesta fw] Tempesta FW is ready Apr 26 02:17:34 192.168.122.209 [36804.338487] [tdb] Close table 'client0.tdb' Apr 26 02:17:34 192.168.122.209 [36804.542264] [tdb] Close table 'sessions0.tdb' Apr 26 02:17:37 192.168.122.209 [36807.761155] [tdb] Close table 'cache0.tdb' Apr 26 02:17:37 192.168.122.209 [36808.026411] [tdb] Close table 'filter0.tdb' Apr 26 02:17:37 192.168.122.209 [36808.026842] [tempesta fw] modules are stopped Apr 26 02:17:37 192.168.122.209 [36808.243413] [tempesta fw] exiting... Apr 26 02:17:38 192.168.122.209 [36808.406672] [tdb] Shutdown Tempesta DB Apr 26 02:17:38 192.168.122.209 [36808.675859] End test: cache.test_cache_control.HttpChainCacheActionOverrideBypass.test Apr 26 02:17:38 192.168.122.209 [36808.699520] Start test: cache.test_cache_control.HttpChainCacheActionOverrideCached.test Apr 26 02:17:39 192.168.122.209 [36809.924049] [tdb] Start Tempesta DB Apr 26 02:17:39 192.168.122.209 [36810.073205] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:17:41 192.168.122.209 [36811.799860] [tempesta fw] Configuration processing is completed. Apr 26 02:17:41 192.168.122.209 [36811.881579] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:17:42 192.168.122.209 [36812.301641] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:17:42 192.168.122.209 [36812.327661] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:17:42 192.168.122.209 [36812.354764] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:17:42 192.168.122.209 [36812.399762] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:17:42 192.168.122.209 [36812.443747] [tempesta fw] Tempesta FW is ready Apr 26 02:17:42 192.168.122.209 [36813.039660] [tdb] Close table 'client0.tdb' Apr 26 02:17:42 192.168.122.209 [36813.238791] [tdb] Close table 'sessions0.tdb' Apr 26 02:17:46 192.168.122.209 [36816.465715] [tdb] Close table 'cache0.tdb' Apr 26 02:17:46 192.168.122.209 [36816.706969] [tdb] Close table 'filter0.tdb' Apr 26 02:17:46 192.168.122.209 [36816.707401] [tempesta fw] modules are stopped Apr 26 02:17:46 192.168.122.209 [36816.977540] [tempesta fw] exiting... Apr 26 02:17:46 192.168.122.209 [36817.130099] [tdb] Shutdown Tempesta DB Apr 26 02:17:47 192.168.122.209 [36817.367348] End test: cache.test_cache_control.HttpChainCacheActionOverrideCached.test Apr 26 02:17:47 192.168.122.209 [36817.377892] Start test: cache.test_cache_control.RequestMaxAge0NoCache.test Apr 26 02:17:48 192.168.122.209 [36818.504274] [tdb] Start Tempesta DB Apr 26 02:17:48 192.168.122.209 [36818.664779] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:17:49 192.168.122.209 [36820.203940] [tempesta fw] Configuration processing is completed. Apr 26 02:17:49 192.168.122.209 [36820.253204] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:17:50 192.168.122.209 [36820.702801] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:17:50 192.168.122.209 [36820.730860] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:17:50 192.168.122.209 [36820.758434] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:17:50 192.168.122.209 [36820.815907] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:17:50 192.168.122.209 [36820.859859] [tempesta fw] Tempesta FW is ready Apr 26 02:17:51 192.168.122.209 [36821.498949] [tdb] Close table 'client0.tdb' Apr 26 02:17:51 192.168.122.209 [36821.705039] [tdb] Close table 'sessions0.tdb' Apr 26 02:17:54 192.168.122.209 [36824.970953] [tdb] Close table 'cache0.tdb' Apr 26 02:17:54 192.168.122.209 [36825.201761] [tdb] Close table 'filter0.tdb' Apr 26 02:17:54 192.168.122.209 [36825.202185] [tempesta fw] modules are stopped Apr 26 02:17:55 192.168.122.209 [36825.410465] [tempesta fw] exiting... Apr 26 02:17:55 192.168.122.209 [36825.584704] [tdb] Shutdown Tempesta DB Apr 26 02:17:55 192.168.122.209 [36825.833387] End test: cache.test_cache_control.RequestMaxAge0NoCache.test Apr 26 02:17:55 192.168.122.209 [36825.851271] Start test: cache.test_cache_control.RequestMaxAge0NoCache2.test Apr 26 02:17:56 192.168.122.209 [36827.072756] [tdb] Start Tempesta DB Apr 26 02:17:56 192.168.122.209 [36827.235061] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:17:58 192.168.122.209 [36828.800338] [tempesta fw] Configuration processing is completed. Apr 26 02:17:58 192.168.122.209 [36828.851279] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:17:59 192.168.122.209 [36829.298662] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:17:59 192.168.122.209 [36829.325915] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:17:59 192.168.122.209 [36829.352817] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:17:59 192.168.122.209 [36829.400052] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:17:59 192.168.122.209 [36829.447967] [tempesta fw] Tempesta FW is ready Apr 26 02:17:59 192.168.122.209 [36830.069709] [tdb] Close table 'client0.tdb' Apr 26 02:17:59 192.168.122.209 [36830.268097] [tdb] Close table 'sessions0.tdb' Apr 26 02:18:03 192.168.122.209 [36833.509033] [tdb] Close table 'cache0.tdb' Apr 26 02:18:03 192.168.122.209 [36833.757321] [tdb] Close table 'filter0.tdb' Apr 26 02:18:03 192.168.122.209 [36833.757772] [tempesta fw] modules are stopped Apr 26 02:18:03 192.168.122.209 [36833.983323] [tempesta fw] exiting... Apr 26 02:18:03 192.168.122.209 [36834.130847] [tdb] Shutdown Tempesta DB Apr 26 02:18:04 192.168.122.209 [36834.354118] End test: cache.test_cache_control.RequestMaxAge0NoCache2.test Apr 26 02:18:04 192.168.122.209 [36834.381980] Start test: cache.test_cache_control.RequestMaxAgeCached.test Apr 26 02:18:05 192.168.122.209 [36835.578919] [tdb] Start Tempesta DB Apr 26 02:18:05 192.168.122.209 [36835.721651] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:18:06 192.168.122.209 [36837.204191] [tempesta fw] Configuration processing is completed. Apr 26 02:18:06 192.168.122.209 [36837.260924] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:18:07 192.168.122.209 [36837.716733] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:18:07 192.168.122.209 [36837.747317] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:18:07 192.168.122.209 [36837.778593] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:18:07 192.168.122.209 [36837.832146] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:18:07 192.168.122.209 [36837.868081] [tempesta fw] Tempesta FW is ready Apr 26 02:18:08 192.168.122.209 [36838.504480] [tdb] Close table 'client0.tdb' Apr 26 02:18:08 192.168.122.209 [36838.714407] [tdb] Close table 'sessions0.tdb' Apr 26 02:18:11 192.168.122.209 [36841.963652] [tdb] Close table 'cache0.tdb' Apr 26 02:18:11 192.168.122.209 [36842.215468] [tdb] Close table 'filter0.tdb' Apr 26 02:18:11 192.168.122.209 [36842.215911] [tempesta fw] modules are stopped Apr 26 02:18:12 192.168.122.209 [36842.393308] [tempesta fw] exiting... Apr 26 02:18:12 192.168.122.209 [36842.555448] [tdb] Shutdown Tempesta DB Apr 26 02:18:12 192.168.122.209 [36842.781897] End test: cache.test_cache_control.RequestMaxAgeCached.test Apr 26 02:18:12 192.168.122.209 [36842.810302] Start test: cache.test_cache_control.RequestMaxAgeMaxStaleCached.test Apr 26 02:18:13 192.168.122.209 [36843.983348] [tdb] Start Tempesta DB Apr 26 02:18:13 192.168.122.209 [36844.124202] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:18:15 192.168.122.209 [36845.528289] [tempesta fw] Configuration processing is completed. Apr 26 02:18:15 192.168.122.209 [36845.578103] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:18:15 192.168.122.209 [36846.032762] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:18:15 192.168.122.209 [36846.060322] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:18:15 192.168.122.209 [36846.088111] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:18:15 192.168.122.209 [36846.140253] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:18:15 192.168.122.209 [36846.180183] [tempesta fw] Tempesta FW is ready Apr 26 02:18:18 192.168.122.209 [36848.286875] [tdb] Close table 'client0.tdb' Apr 26 02:18:18 192.168.122.209 [36848.481022] [tdb] Close table 'sessions0.tdb' Apr 26 02:18:21 192.168.122.209 [36851.707411] [tdb] Close table 'cache0.tdb' Apr 26 02:18:21 192.168.122.209 [36851.918202] [tdb] Close table 'filter0.tdb' Apr 26 02:18:21 192.168.122.209 [36851.918650] [tempesta fw] modules are stopped Apr 26 02:18:21 192.168.122.209 [36852.132951] [tempesta fw] exiting... Apr 26 02:18:22 192.168.122.209 [36852.317793] [tdb] Shutdown Tempesta DB Apr 26 02:18:22 192.168.122.209 [36852.549466] End test: cache.test_cache_control.RequestMaxAgeMaxStaleCached.test Apr 26 02:18:22 192.168.122.209 [36852.560396] Start test: cache.test_cache_control.RequestMaxAgeMaxStaleNotCached.test Apr 26 02:18:23 192.168.122.209 [36853.732685] [tdb] Start Tempesta DB Apr 26 02:18:23 192.168.122.209 [36853.871633] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:18:25 192.168.122.209 [36855.380420] [tempesta fw] Configuration processing is completed. Apr 26 02:18:25 192.168.122.209 [36855.430980] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:18:25 192.168.122.209 [36855.845610] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:18:25 192.168.122.209 [36855.871516] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:18:25 192.168.122.209 [36855.897060] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:18:25 192.168.122.209 [36855.948387] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:18:25 192.168.122.209 [36855.992343] [tempesta fw] Tempesta FW is ready Apr 26 02:18:29 192.168.122.209 [36859.598052] [tdb] Close table 'client0.tdb' Apr 26 02:18:29 192.168.122.209 [36859.797014] [tdb] Close table 'sessions0.tdb' Apr 26 02:18:32 192.168.122.209 [36863.162921] [tdb] Close table 'cache0.tdb' Apr 26 02:18:33 192.168.122.209 [36863.415272] [tdb] Close table 'filter0.tdb' Apr 26 02:18:33 192.168.122.209 [36863.415707] [tempesta fw] modules are stopped Apr 26 02:18:33 192.168.122.209 [36863.612351] [tempesta fw] exiting... Apr 26 02:18:33 192.168.122.209 [36863.750077] [tdb] Shutdown Tempesta DB Apr 26 02:18:33 192.168.122.209 [36863.979867] End test: cache.test_cache_control.RequestMaxAgeMaxStaleNotCached.test Apr 26 02:18:33 192.168.122.209 [36863.997499] Start test: cache.test_cache_control.RequestMaxAgeNoCached.test Apr 26 02:18:34 192.168.122.209 [36865.081317] [tdb] Start Tempesta DB Apr 26 02:18:34 192.168.122.209 [36865.224697] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:18:36 192.168.122.209 [36866.696546] [tempesta fw] Configuration processing is completed. Apr 26 02:18:36 192.168.122.209 [36866.754139] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:18:36 192.168.122.209 [36867.186596] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:18:36 192.168.122.209 [36867.213001] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:18:36 192.168.122.209 [36867.240363] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:18:37 192.168.122.209 [36867.292546] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:18:37 192.168.122.209 [36867.340477] [tempesta fw] Tempesta FW is ready Apr 26 02:18:39 192.168.122.209 [36869.973283] [tdb] Close table 'client0.tdb' Apr 26 02:18:39 192.168.122.209 [36870.177667] [tdb] Close table 'sessions0.tdb' Apr 26 02:18:43 192.168.122.209 [36873.420179] [tdb] Close table 'cache0.tdb' Apr 26 02:18:43 192.168.122.209 [36873.660239] [tdb] Close table 'filter0.tdb' Apr 26 02:18:43 192.168.122.209 [36873.660698] [tempesta fw] modules are stopped Apr 26 02:18:43 192.168.122.209 [36873.882762] [tempesta fw] exiting... Apr 26 02:18:43 192.168.122.209 [36874.050245] [tdb] Shutdown Tempesta DB Apr 26 02:18:43 192.168.122.209 [36874.265515] End test: cache.test_cache_control.RequestMaxAgeNoCached.test Apr 26 02:18:44 192.168.122.209 [36874.280060] Start test: cache.test_cache_control.RequestMaxStaleCached.test Apr 26 02:18:45 192.168.122.209 [36875.474211] [tdb] Start Tempesta DB Apr 26 02:18:45 192.168.122.209 [36875.612125] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:18:46 192.168.122.209 [36877.085682] [tempesta fw] Configuration processing is completed. Apr 26 02:18:46 192.168.122.209 [36877.143598] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:18:47 192.168.122.209 [36877.579956] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:18:47 192.168.122.209 [36877.615195] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:18:47 192.168.122.209 [36877.641473] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:18:47 192.168.122.209 [36877.680645] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:18:47 192.168.122.209 [36877.724614] [tempesta fw] Tempesta FW is ready Apr 26 02:18:49 192.168.122.209 [36879.850277] [tdb] Close table 'client0.tdb' Apr 26 02:18:49 192.168.122.209 [36880.035040] [tdb] Close table 'sessions0.tdb' Apr 26 02:18:52 192.168.122.209 [36883.209701] [tdb] Close table 'cache0.tdb' Apr 26 02:18:53 192.168.122.209 [36883.446114] [tdb] Close table 'filter0.tdb' Apr 26 02:18:53 192.168.122.209 [36883.446562] [tempesta fw] modules are stopped Apr 26 02:18:53 192.168.122.209 [36883.629149] [tempesta fw] exiting... Apr 26 02:18:53 192.168.122.209 [36883.769656] [tdb] Shutdown Tempesta DB Apr 26 02:18:53 192.168.122.209 [36883.952422] End test: cache.test_cache_control.RequestMaxStaleCached.test Apr 26 02:18:53 192.168.122.209 [36883.970642] Start test: cache.test_cache_control.RequestMinFreshCached.test Apr 26 02:18:54 192.168.122.209 [36885.141066] [tdb] Start Tempesta DB Apr 26 02:18:55 192.168.122.209 [36885.286469] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:18:56 192.168.122.209 [36886.832823] [tempesta fw] Configuration processing is completed. Apr 26 02:18:56 192.168.122.209 [36886.883757] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:18:57 192.168.122.209 [36887.303711] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:18:57 192.168.122.209 [36887.329759] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:18:57 192.168.122.209 [36887.355801] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:18:57 192.168.122.209 [36887.408784] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:18:57 192.168.122.209 [36887.448720] [tempesta fw] Tempesta FW is ready Apr 26 02:18:57 192.168.122.209 [36887.982450] [tdb] Close table 'client0.tdb' Apr 26 02:18:57 192.168.122.209 [36888.197561] [tdb] Close table 'sessions0.tdb' Apr 26 02:19:01 192.168.122.209 [36891.390858] [tdb] Close table 'cache0.tdb' Apr 26 02:19:01 192.168.122.209 [36891.654262] [tdb] Close table 'filter0.tdb' Apr 26 02:19:01 192.168.122.209 [36891.654704] [tempesta fw] modules are stopped Apr 26 02:19:01 192.168.122.209 [36891.826510] [tempesta fw] exiting... Apr 26 02:19:01 192.168.122.209 [36891.999763] [tdb] Shutdown Tempesta DB Apr 26 02:19:01 192.168.122.209 [36892.192901] End test: cache.test_cache_control.RequestMinFreshCached.test Apr 26 02:19:01 192.168.122.209 [36892.203015] Start test: cache.test_cache_control.RequestMinFreshNotCached.test Apr 26 02:19:03 192.168.122.209 [36893.407751] [tdb] Start Tempesta DB Apr 26 02:19:03 192.168.122.209 [36893.549908] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:19:04 192.168.122.209 [36895.028944] [tempesta fw] Configuration processing is completed. Apr 26 02:19:04 192.168.122.209 [36895.080396] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:19:05 192.168.122.209 [36895.517687] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:19:05 192.168.122.209 [36895.544177] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:19:05 192.168.122.209 [36895.570142] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:19:05 192.168.122.209 [36895.628881] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:19:05 192.168.122.209 [36895.672847] [tempesta fw] Tempesta FW is ready Apr 26 02:19:08 192.168.122.209 [36898.280591] [tdb] Close table 'client0.tdb' Apr 26 02:19:08 192.168.122.209 [36898.471925] [tdb] Close table 'sessions0.tdb' Apr 26 02:19:11 192.168.122.209 [36901.673753] [tdb] Close table 'cache0.tdb' Apr 26 02:19:11 192.168.122.209 [36901.925701] [tdb] Close table 'filter0.tdb' Apr 26 02:19:11 192.168.122.209 [36901.926163] [tempesta fw] modules are stopped Apr 26 02:19:11 192.168.122.209 [36902.125121] [tempesta fw] exiting... Apr 26 02:19:12 192.168.122.209 [36902.293471] [tdb] Shutdown Tempesta DB Apr 26 02:19:12 192.168.122.209 [36902.522233] End test: cache.test_cache_control.RequestMinFreshNotCached.test Apr 26 02:19:12 192.168.122.209 [36902.553009] Start test: cache.test_cache_control.RequestNoChacheNotCached.test Apr 26 02:19:13 192.168.122.209 [36903.720575] [tdb] Start Tempesta DB Apr 26 02:19:13 192.168.122.209 [36903.860933] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:19:15 192.168.122.209 [36905.417055] [tempesta fw] Configuration processing is completed. Apr 26 02:19:15 192.168.122.209 [36905.467071] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:19:15 192.168.122.209 [36905.885908] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:19:15 192.168.122.209 [36905.911801] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:19:15 192.168.122.209 [36905.937534] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:19:15 192.168.122.209 [36906.021017] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:19:15 192.168.122.209 [36906.064980] [tempesta fw] Tempesta FW is ready Apr 26 02:19:16 192.168.122.209 [36906.680325] [tdb] Close table 'client0.tdb' Apr 26 02:19:16 192.168.122.209 [36906.876627] [tdb] Close table 'sessions0.tdb' Apr 26 02:19:19 192.168.122.209 [36910.123173] [tdb] Close table 'cache0.tdb' Apr 26 02:19:20 192.168.122.209 [36910.339702] [tdb] Close table 'filter0.tdb' Apr 26 02:19:20 192.168.122.209 [36910.340136] [tempesta fw] modules are stopped Apr 26 02:19:20 192.168.122.209 [36910.547909] [tempesta fw] exiting... Apr 26 02:19:20 192.168.122.209 [36910.690047] [tdb] Shutdown Tempesta DB Apr 26 02:19:20 192.168.122.209 [36910.900778] End test: cache.test_cache_control.RequestNoChacheNotCached.test Apr 26 02:19:20 192.168.122.209 [36910.927391] Start test: cache.test_cache_control.RequestNoStoreNotCached.test Apr 26 02:19:21 192.168.122.209 [36912.105933] [tdb] Start Tempesta DB Apr 26 02:19:21 192.168.122.209 [36912.255379] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:19:23 192.168.122.209 [36913.821155] [tempesta fw] Configuration processing is completed. Apr 26 02:19:23 192.168.122.209 [36913.911900] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:19:24 192.168.122.209 [36914.338422] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:19:24 192.168.122.209 [36914.365466] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:19:24 192.168.122.209 [36914.400257] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:19:24 192.168.122.209 [36914.437127] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:19:24 192.168.122.209 [36914.485079] [tempesta fw] Tempesta FW is ready Apr 26 02:19:24 192.168.122.209 [36915.099217] [tdb] Close table 'client0.tdb' Apr 26 02:19:25 192.168.122.209 [36915.300122] [tdb] Close table 'sessions0.tdb' Apr 26 02:19:28 192.168.122.209 [36918.489472] [tdb] Close table 'cache0.tdb' Apr 26 02:19:28 192.168.122.209 [36918.728184] [tdb] Close table 'filter0.tdb' Apr 26 02:19:28 192.168.122.209 [36918.728617] [tempesta fw] modules are stopped Apr 26 02:19:28 192.168.122.209 [36918.937411] [tempesta fw] exiting... Apr 26 02:19:28 192.168.122.209 [36919.073490] [tdb] Shutdown Tempesta DB Apr 26 02:19:29 192.168.122.209 [36919.305319] End test: cache.test_cache_control.RequestNoStoreNotCached.test Apr 26 02:19:29 192.168.122.209 [36919.334247] Start test: cache.test_cache_control.RequestOnlyIfCached504.test Apr 26 02:19:30 192.168.122.209 [36920.537963] [tdb] Start Tempesta DB Apr 26 02:19:30 192.168.122.209 [36920.687721] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:19:31 192.168.122.209 [36922.237304] [tempesta fw] Configuration processing is completed. Apr 26 02:19:32 192.168.122.209 [36922.290870] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:19:32 192.168.122.209 [36922.713738] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:19:32 192.168.122.209 [36922.739731] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:19:32 192.168.122.209 [36922.765431] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:19:32 192.168.122.209 [36922.813232] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:19:32 192.168.122.209 [36922.857206] [tempesta fw] Tempesta FW is ready Apr 26 02:19:35 192.168.122.209 [36925.537890] [tempesta fw] Warning: resource not cached, status 504: 127.0.0.2 Apr 26 02:19:35 192.168.122.209 [36925.984268] [tdb] Close table 'client0.tdb' Apr 26 02:19:35 192.168.122.209 [36926.172105] [tdb] Close table 'sessions0.tdb' Apr 26 02:19:39 192.168.122.209 [36929.394008] [tdb] Close table 'cache0.tdb' Apr 26 02:19:39 192.168.122.209 [36929.648015] [tdb] Close table 'filter0.tdb' Apr 26 02:19:39 192.168.122.209 [36929.648451] [tempesta fw] modules are stopped Apr 26 02:19:39 192.168.122.209 [36929.813248] [tempesta fw] exiting... Apr 26 02:19:39 192.168.122.209 [36929.951614] [tdb] Shutdown Tempesta DB Apr 26 02:19:39 192.168.122.209 [36930.155100] End test: cache.test_cache_control.RequestOnlyIfCached504.test Apr 26 02:19:39 192.168.122.209 [36930.179656] Start test: cache.test_cache_control.RequestOnlyIfCachedCached.test Apr 26 02:19:41 192.168.122.209 [36931.398104] [tdb] Start Tempesta DB Apr 26 02:19:41 192.168.122.209 [36931.557749] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:19:42 192.168.122.209 [36933.081352] [tempesta fw] Configuration processing is completed. Apr 26 02:19:42 192.168.122.209 [36933.139092] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:19:43 192.168.122.209 [36933.570760] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:19:43 192.168.122.209 [36933.596951] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:19:43 192.168.122.209 [36933.623455] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:19:43 192.168.122.209 [36933.673379] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:19:43 192.168.122.209 [36933.717270] [tempesta fw] Tempesta FW is ready Apr 26 02:19:44 192.168.122.209 [36934.330210] [tdb] Close table 'client0.tdb' Apr 26 02:19:44 192.168.122.209 [36934.525524] [tdb] Close table 'sessions0.tdb' Apr 26 02:19:47 192.168.122.209 [36937.708423] [tdb] Close table 'cache0.tdb' Apr 26 02:19:47 192.168.122.209 [36937.951981] [tdb] Close table 'filter0.tdb' Apr 26 02:19:47 192.168.122.209 [36937.952422] [tempesta fw] modules are stopped Apr 26 02:19:47 192.168.122.209 [36938.117232] [tempesta fw] exiting... Apr 26 02:19:47 192.168.122.209 [36938.263519] [tdb] Shutdown Tempesta DB Apr 26 02:19:48 192.168.122.209 [36938.469040] End test: cache.test_cache_control.RequestOnlyIfCachedCached.test Apr 26 02:19:48 192.168.122.209 [36938.499968] Start test: cache.test_cache_control.ResponseForAuthorizationUserMustRevalidateNotCached.test Apr 26 02:19:49 192.168.122.209 [36939.657512] [tdb] Start Tempesta DB Apr 26 02:19:49 192.168.122.209 [36939.819717] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:19:50 192.168.122.209 [36941.257511] [tempesta fw] Configuration processing is completed. Apr 26 02:19:51 192.168.122.209 [36941.313187] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:19:51 192.168.122.209 [36941.736783] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:19:51 192.168.122.209 [36941.762839] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:19:51 192.168.122.209 [36941.788831] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:19:51 192.168.122.209 [36941.857502] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:19:51 192.168.122.209 [36941.909438] [tempesta fw] Tempesta FW is ready Apr 26 02:19:54 192.168.122.209 [36944.530650] [tdb] Close table 'client0.tdb' Apr 26 02:19:54 192.168.122.209 [36944.717433] [tdb] Close table 'sessions0.tdb' Apr 26 02:19:57 192.168.122.209 [36947.871484] [tdb] Close table 'cache0.tdb' Apr 26 02:19:57 192.168.122.209 [36948.113345] [tdb] Close table 'filter0.tdb' Apr 26 02:19:57 192.168.122.209 [36948.113782] [tempesta fw] modules are stopped Apr 26 02:19:58 192.168.122.209 [36948.326862] [tempesta fw] exiting... Apr 26 02:19:58 192.168.122.209 [36948.475835] [tdb] Shutdown Tempesta DB Apr 26 02:19:58 192.168.122.209 [36948.708063] End test: cache.test_cache_control.ResponseForAuthorizationUserMustRevalidateNotCached.test Apr 26 02:19:58 192.168.122.209 [36948.721648] Start test: cache.test_cache_control.ResponseMaxAgeCached.test Apr 26 02:19:59 192.168.122.209 [36949.940881] [tdb] Start Tempesta DB Apr 26 02:19:59 192.168.122.209 [36950.086519] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:20:01 192.168.122.209 [36951.557659] [tempesta fw] Configuration processing is completed. Apr 26 02:20:01 192.168.122.209 [36951.611389] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:20:01 192.168.122.209 [36952.033251] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:20:01 192.168.122.209 [36952.059397] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:20:01 192.168.122.209 [36952.085412] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:20:01 192.168.122.209 [36952.137603] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:20:01 192.168.122.209 [36952.189550] [tempesta fw] Tempesta FW is ready Apr 26 02:20:02 192.168.122.209 [36952.819307] [tdb] Close table 'client0.tdb' Apr 26 02:20:02 192.168.122.209 [36953.027154] [tdb] Close table 'sessions0.tdb' Apr 26 02:20:05 192.168.122.209 [36956.258072] [tdb] Close table 'cache0.tdb' Apr 26 02:20:06 192.168.122.209 [36956.510423] [tdb] Close table 'filter0.tdb' Apr 26 02:20:06 192.168.122.209 [36956.510880] [tempesta fw] modules are stopped Apr 26 02:20:06 192.168.122.209 [36956.744850] [tempesta fw] exiting... Apr 26 02:20:06 192.168.122.209 [36956.890711] [tdb] Shutdown Tempesta DB Apr 26 02:20:06 192.168.122.209 [36957.126947] End test: cache.test_cache_control.ResponseMaxAgeCached.test Apr 26 02:20:06 192.168.122.209 [36957.163394] Start test: cache.test_cache_control.ResponseMaxAgeCached2.test Apr 26 02:20:08 192.168.122.209 [36958.415803] [tdb] Start Tempesta DB Apr 26 02:20:08 192.168.122.209 [36958.561718] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:20:09 192.168.122.209 [36960.005755] [tempesta fw] Configuration processing is completed. Apr 26 02:20:09 192.168.122.209 [36960.094480] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:20:10 192.168.122.209 [36960.532876] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:20:10 192.168.122.209 [36960.559824] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:20:10 192.168.122.209 [36960.586550] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:20:10 192.168.122.209 [36960.645698] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:20:10 192.168.122.209 [36960.689673] [tempesta fw] Tempesta FW is ready Apr 26 02:20:11 192.168.122.209 [36961.310282] [tdb] Close table 'client0.tdb' Apr 26 02:20:11 192.168.122.209 [36961.511788] [tdb] Close table 'sessions0.tdb' Apr 26 02:20:14 192.168.122.209 [36964.719167] [tdb] Close table 'cache0.tdb' Apr 26 02:20:14 192.168.122.209 [36964.976842] [tdb] Close table 'filter0.tdb' Apr 26 02:20:14 192.168.122.209 [36964.977284] [tempesta fw] modules are stopped Apr 26 02:20:14 192.168.122.209 [36965.198657] [tempesta fw] exiting... Apr 26 02:20:15 192.168.122.209 [36965.357909] [tdb] Shutdown Tempesta DB Apr 26 02:20:15 192.168.122.209 [36965.580283] End test: cache.test_cache_control.ResponseMaxAgeCached2.test Apr 26 02:20:15 192.168.122.209 [36965.597791] Start test: cache.test_cache_control.ResponseMaxAgeIgnore.test Apr 26 02:20:16 192.168.122.209 [36966.818010] [tdb] Start Tempesta DB Apr 26 02:20:16 192.168.122.209 [36966.969161] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:20:18 192.168.122.209 [36968.529869] [tempesta fw] Configuration processing is completed. Apr 26 02:20:18 192.168.122.209 [36968.584276] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:20:18 192.168.122.209 [36969.019000] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:20:18 192.168.122.209 [36969.046668] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:20:18 192.168.122.209 [36969.073354] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:20:18 192.168.122.209 [36969.121782] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:20:18 192.168.122.209 [36969.173777] [tempesta fw] Tempesta FW is ready Apr 26 02:20:21 192.168.122.209 [36971.315625] [tdb] Close table 'client0.tdb' Apr 26 02:20:21 192.168.122.209 [36971.508744] [tdb] Close table 'sessions0.tdb' Apr 26 02:20:24 192.168.122.209 [36974.763097] [tdb] Close table 'cache0.tdb' Apr 26 02:20:24 192.168.122.209 [36975.011783] [tdb] Close table 'filter0.tdb' Apr 26 02:20:24 192.168.122.209 [36975.012204] [tempesta fw] modules are stopped Apr 26 02:20:24 192.168.122.209 [36975.196458] [tempesta fw] exiting... Apr 26 02:20:25 192.168.122.209 [36975.347753] [tdb] Shutdown Tempesta DB Apr 26 02:20:25 192.168.122.209 [36975.567303] End test: cache.test_cache_control.ResponseMaxAgeIgnore.test Apr 26 02:20:25 192.168.122.209 [36975.580470] Start test: cache.test_cache_control.ResponseMaxAgeNotCached.test Apr 26 02:20:26 192.168.122.209 [36976.791806] [tdb] Start Tempesta DB Apr 26 02:20:26 192.168.122.209 [36976.941066] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:20:28 192.168.122.209 [36978.450006] [tempesta fw] Configuration processing is completed. Apr 26 02:20:28 192.168.122.209 [36978.512083] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:20:28 192.168.122.209 [36978.933786] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:20:28 192.168.122.209 [36978.959418] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:20:28 192.168.122.209 [36978.985126] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:20:28 192.168.122.209 [36979.025923] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:20:28 192.168.122.209 [36979.069820] [tempesta fw] Tempesta FW is ready Apr 26 02:20:31 192.168.122.209 [36981.657821] [tdb] Close table 'client0.tdb' Apr 26 02:20:31 192.168.122.209 [36981.862786] [tdb] Close table 'sessions0.tdb' Apr 26 02:20:34 192.168.122.209 [36985.070095] [tdb] Close table 'cache0.tdb' Apr 26 02:20:35 192.168.122.209 [36985.319906] [tdb] Close table 'filter0.tdb' Apr 26 02:20:35 192.168.122.209 [36985.320331] [tempesta fw] modules are stopped Apr 26 02:20:35 192.168.122.209 [36985.515018] [tempesta fw] exiting... Apr 26 02:20:35 192.168.122.209 [36985.679654] [tdb] Shutdown Tempesta DB Apr 26 02:20:35 192.168.122.209 [36985.914439] End test: cache.test_cache_control.ResponseMaxAgeNotCached.test Apr 26 02:20:35 192.168.122.209 [36985.940144] Start test: cache.test_cache_control.ResponseMaxAgeNotCached2.test Apr 26 02:20:36 192.168.122.209 [36987.100267] [tdb] Start Tempesta DB Apr 26 02:20:36 192.168.122.209 [36987.248357] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:20:38 192.168.122.209 [36988.686409] [tempesta fw] Configuration processing is completed. Apr 26 02:20:38 192.168.122.209 [36988.735703] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:20:38 192.168.122.209 [36989.161997] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:20:38 192.168.122.209 [36989.188431] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:20:38 192.168.122.209 [36989.215711] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:20:39 192.168.122.209 [36989.270095] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:20:39 192.168.122.209 [36989.310010] [tempesta fw] Tempesta FW is ready Apr 26 02:20:39 192.168.122.209 [36989.927754] [tdb] Close table 'client0.tdb' Apr 26 02:20:39 192.168.122.209 [36990.125656] [tdb] Close table 'sessions0.tdb' Apr 26 02:20:43 192.168.122.209 [36993.407247] [tdb] Close table 'cache0.tdb' Apr 26 02:20:43 192.168.122.209 [36993.657316] [tdb] Close table 'filter0.tdb' Apr 26 02:20:43 192.168.122.209 [36993.657729] [tempesta fw] modules are stopped Apr 26 02:20:43 192.168.122.209 [36993.822044] [tempesta fw] exiting... Apr 26 02:20:43 192.168.122.209 [36993.960833] [tdb] Shutdown Tempesta DB Apr 26 02:20:43 192.168.122.209 [36994.170432] End test: cache.test_cache_control.ResponseMaxAgeNotCached2.test Apr 26 02:20:43 192.168.122.209 [36994.190212] Start test: cache.test_cache_control.ResponseMultipleNoCacheIgnore.test Apr 26 02:20:45 192.168.122.209 [36995.439447] [tdb] Start Tempesta DB Apr 26 02:20:45 192.168.122.209 [36995.595799] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:20:46 192.168.122.209 [36997.142196] [tempesta fw] Configuration processing is completed. Apr 26 02:20:46 192.168.122.209 [36997.194396] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:20:47 192.168.122.209 [36997.622453] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:20:47 192.168.122.209 [36997.648463] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:20:47 192.168.122.209 [36997.675050] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:20:47 192.168.122.209 [36997.718182] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:20:47 192.168.122.209 [36997.762096] [tempesta fw] Tempesta FW is ready Apr 26 02:20:48 192.168.122.209 [36998.386834] [tdb] Close table 'client0.tdb' Apr 26 02:20:48 192.168.122.209 [36998.579085] [tdb] Close table 'sessions0.tdb' Apr 26 02:20:51 192.168.122.209 [37001.748547] [tdb] Close table 'cache0.tdb' Apr 26 02:20:51 192.168.122.209 [37001.975688] [tdb] Close table 'filter0.tdb' Apr 26 02:20:51 192.168.122.209 [37001.976118] [tempesta fw] modules are stopped Apr 26 02:20:51 192.168.122.209 [37002.206730] [tempesta fw] exiting... Apr 26 02:20:52 192.168.122.209 [37002.606703] [tdb] Shutdown Tempesta DB Apr 26 02:20:53 192.168.122.209 [37003.355969] End test: cache.test_cache_control.ResponseMultipleNoCacheIgnore.test Apr 26 02:20:53 192.168.122.209 [37003.370033] Start test: cache.test_cache_control.ResponseMustRevalidateCached.test Apr 26 02:20:54 192.168.122.209 [37004.684549] [tdb] Start Tempesta DB Apr 26 02:20:54 192.168.122.209 [37004.871233] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:20:57 192.168.122.209 [37007.610753] [tempesta fw] Configuration processing is completed. Apr 26 02:20:57 192.168.122.209 [37007.779416] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:20:57 192.168.122.209 [37008.227000] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:20:57 192.168.122.209 [37008.254098] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:20:58 192.168.122.209 [37008.285701] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:20:58 192.168.122.209 [37008.754789] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:20:58 192.168.122.209 [37008.954238] [tempesta fw] Tempesta FW is ready Apr 26 02:20:59 192.168.122.209 [37009.529269] [tdb] Close table 'client0.tdb' Apr 26 02:20:59 192.168.122.209 [37009.731884] [tdb] Close table 'sessions0.tdb' Apr 26 02:21:02 192.168.122.209 [37012.964675] [tdb] Close table 'cache0.tdb' Apr 26 02:21:02 192.168.122.209 [37013.217390] [tdb] Close table 'filter0.tdb' Apr 26 02:21:02 192.168.122.209 [37013.217835] [tempesta fw] modules are stopped Apr 26 02:21:03 192.168.122.209 [37013.401178] [tempesta fw] exiting... Apr 26 02:21:03 192.168.122.209 [37013.541049] [tdb] Shutdown Tempesta DB Apr 26 02:21:03 192.168.122.209 [37013.759099] End test: cache.test_cache_control.ResponseMustRevalidateCached.test Apr 26 02:21:03 192.168.122.209 [37013.771505] Start test: cache.test_cache_control.ResponseMustRevalidateHalfIgnore.test Apr 26 02:21:04 192.168.122.209 [37014.962260] [tdb] Start Tempesta DB Apr 26 02:21:04 192.168.122.209 [37015.113190] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:21:06 192.168.122.209 [37016.638437] [tempesta fw] Configuration processing is completed. Apr 26 02:21:06 192.168.122.209 [37016.728751] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:21:06 192.168.122.209 [37017.159291] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:21:06 192.168.122.209 [37017.186324] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:21:06 192.168.122.209 [37017.213378] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:21:07 192.168.122.209 [37017.314403] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:21:07 192.168.122.209 [37017.362338] [tempesta fw] Tempesta FW is ready Apr 26 02:21:09 192.168.122.209 [37019.495087] [tdb] Close table 'client0.tdb' Apr 26 02:21:09 192.168.122.209 [37019.674934] [tdb] Close table 'sessions0.tdb' Apr 26 02:21:12 192.168.122.209 [37022.832089] [tdb] Close table 'cache0.tdb' Apr 26 02:21:12 192.168.122.209 [37023.055935] [tdb] Close table 'filter0.tdb' Apr 26 02:21:12 192.168.122.209 [37023.056371] [tempesta fw] modules are stopped Apr 26 02:21:12 192.168.122.209 [37023.246448] [tempesta fw] exiting... Apr 26 02:21:13 192.168.122.209 [37023.405524] [tdb] Shutdown Tempesta DB Apr 26 02:21:13 192.168.122.209 [37023.618442] End test: cache.test_cache_control.ResponseMustRevalidateHalfIgnore.test Apr 26 02:21:13 192.168.122.209 [37023.637686] Start test: cache.test_cache_control.ResponseMustRevalidateIgnore.test Apr 26 02:21:14 192.168.122.209 [37024.831956] [tdb] Start Tempesta DB Apr 26 02:21:14 192.168.122.209 [37024.979480] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:21:16 192.168.122.209 [37026.550563] [tempesta fw] Configuration processing is completed. Apr 26 02:21:16 192.168.122.209 [37026.609462] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:21:16 192.168.122.209 [37027.033369] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:21:16 192.168.122.209 [37027.060495] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:21:16 192.168.122.209 [37027.086782] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:21:16 192.168.122.209 [37027.142529] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:21:16 192.168.122.209 [37027.182471] [tempesta fw] Tempesta FW is ready Apr 26 02:21:19 192.168.122.209 [37029.785501] [tdb] Close table 'client0.tdb' Apr 26 02:21:19 192.168.122.209 [37029.973737] [tdb] Close table 'sessions0.tdb' Apr 26 02:21:22 192.168.122.209 [37033.163111] [tdb] Close table 'cache0.tdb' Apr 26 02:21:23 192.168.122.209 [37033.413862] [tdb] Close table 'filter0.tdb' Apr 26 02:21:23 192.168.122.209 [37033.414310] [tempesta fw] modules are stopped Apr 26 02:21:23 192.168.122.209 [37033.605774] [tempesta fw] exiting... Apr 26 02:21:23 192.168.122.209 [37033.736132] [tdb] Shutdown Tempesta DB Apr 26 02:21:23 192.168.122.209 [37033.920400] End test: cache.test_cache_control.ResponseMustRevalidateIgnore.test Apr 26 02:21:23 192.168.122.209 [37033.946155] Start test: cache.test_cache_control.ResponseMustRevalidateMultiIgnore.test Apr 26 02:21:24 192.168.122.209 [37035.111374] [tdb] Start Tempesta DB Apr 26 02:21:24 192.168.122.209 [37035.248352] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:21:26 192.168.122.209 [37036.734700] [tempesta fw] Configuration processing is completed. Apr 26 02:21:26 192.168.122.209 [37036.788051] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:21:26 192.168.122.209 [37037.214353] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:21:26 192.168.122.209 [37037.240051] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:21:26 192.168.122.209 [37037.266351] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:21:27 192.168.122.209 [37037.334629] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:21:27 192.168.122.209 [37037.386603] [tempesta fw] Tempesta FW is ready Apr 26 02:21:29 192.168.122.209 [37039.491045] [tdb] Close table 'client0.tdb' Apr 26 02:21:29 192.168.122.209 [37039.691319] [tdb] Close table 'sessions0.tdb' Apr 26 02:21:32 192.168.122.209 [37042.911861] [tdb] Close table 'cache0.tdb' Apr 26 02:21:32 192.168.122.209 [37043.124106] [tdb] Close table 'filter0.tdb' Apr 26 02:21:32 192.168.122.209 [37043.124539] [tempesta fw] modules are stopped Apr 26 02:21:33 192.168.122.209 [37043.338789] [tempesta fw] exiting... Apr 26 02:21:33 192.168.122.209 [37043.488218] [tdb] Shutdown Tempesta DB Apr 26 02:21:33 192.168.122.209 [37043.710852] End test: cache.test_cache_control.ResponseMustRevalidateMultiIgnore.test Apr 26 02:21:33 192.168.122.209 [37043.744911] Start test: cache.test_cache_control.ResponseMustRevalidateNotCached.test Apr 26 02:21:34 192.168.122.209 [37044.946171] [tdb] Start Tempesta DB Apr 26 02:21:34 192.168.122.209 [37045.103055] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:21:36 192.168.122.209 [37046.570810] [tempesta fw] Configuration processing is completed. Apr 26 02:21:36 192.168.122.209 [37046.624035] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:21:36 192.168.122.209 [37047.039617] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:21:36 192.168.122.209 [37047.065546] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:21:36 192.168.122.209 [37047.092318] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:21:36 192.168.122.209 [37047.146761] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:21:36 192.168.122.209 [37047.186706] [tempesta fw] Tempesta FW is ready Apr 26 02:21:39 192.168.122.209 [37049.826292] [tdb] Close table 'client0.tdb' Apr 26 02:21:39 192.168.122.209 [37050.011136] [tdb] Close table 'sessions0.tdb' Apr 26 02:21:42 192.168.122.209 [37053.204742] [tdb] Close table 'cache0.tdb' Apr 26 02:21:43 192.168.122.209 [37053.436055] [tdb] Close table 'filter0.tdb' Apr 26 02:21:43 192.168.122.209 [37053.436485] [tempesta fw] modules are stopped Apr 26 02:21:43 192.168.122.209 [37053.637391] [tempesta fw] exiting... Apr 26 02:21:43 192.168.122.209 [37053.814597] [tdb] Shutdown Tempesta DB Apr 26 02:21:43 192.168.122.209 [37054.058347] End test: cache.test_cache_control.ResponseMustRevalidateNotCached.test Apr 26 02:21:43 192.168.122.209 [37054.069760] Start test: cache.test_cache_control.ResponseMustRevalidateStaleCached.test Apr 26 02:21:45 192.168.122.209 [37055.290635] [tdb] Start Tempesta DB Apr 26 02:21:45 192.168.122.209 [37055.427968] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:21:46 192.168.122.209 [37056.918851] [tempesta fw] Configuration processing is completed. Apr 26 02:21:46 192.168.122.209 [37056.975858] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:21:47 192.168.122.209 [37057.397765] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:21:47 192.168.122.209 [37057.424217] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:21:47 192.168.122.209 [37057.451114] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:21:47 192.168.122.209 [37057.498868] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:21:47 192.168.122.209 [37057.566833] [tempesta fw] Tempesta FW is ready Apr 26 02:21:47 192.168.122.209 [37058.159820] [tdb] Close table 'client0.tdb' Apr 26 02:21:48 192.168.122.209 [37058.407930] [tdb] Close table 'sessions0.tdb' Apr 26 02:21:51 192.168.122.209 [37061.571498] [tdb] Close table 'cache0.tdb' Apr 26 02:21:51 192.168.122.209 [37061.808504] [tdb] Close table 'filter0.tdb' Apr 26 02:21:51 192.168.122.209 [37061.808964] [tempesta fw] modules are stopped Apr 26 02:21:51 192.168.122.209 [37062.023280] [tempesta fw] exiting... Apr 26 02:21:51 192.168.122.209 [37062.199493] [tdb] Shutdown Tempesta DB Apr 26 02:21:52 192.168.122.209 [37062.461893] End test: cache.test_cache_control.ResponseMustRevalidateStaleCached.test Apr 26 02:21:52 192.168.122.209 [37062.478666] Start test: cache.test_cache_control.ResponseMustRevalidateStaleIgnore.test Apr 26 02:21:53 192.168.122.209 [37063.671526] [tdb] Start Tempesta DB Apr 26 02:21:53 192.168.122.209 [37063.813350] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:21:55 192.168.122.209 [37065.419073] [tempesta fw] Configuration processing is completed. Apr 26 02:21:55 192.168.122.209 [37065.475126] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:21:55 192.168.122.209 [37065.905978] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:21:55 192.168.122.209 [37065.932358] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:21:55 192.168.122.209 [37065.960165] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:21:55 192.168.122.209 [37066.002945] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:21:55 192.168.122.209 [37066.046967] [tempesta fw] Tempesta FW is ready Apr 26 02:21:57 192.168.122.209 [37068.176906] [tdb] Close table 'client0.tdb' Apr 26 02:21:58 192.168.122.209 [37068.362080] [tdb] Close table 'sessions0.tdb' Apr 26 02:22:01 192.168.122.209 [37071.616284] [tdb] Close table 'cache0.tdb' Apr 26 02:22:01 192.168.122.209 [37071.854450] [tdb] Close table 'filter0.tdb' Apr 26 02:22:01 192.168.122.209 [37071.854936] [tempesta fw] modules are stopped Apr 26 02:22:01 192.168.122.209 [37072.076241] [tempesta fw] exiting... Apr 26 02:22:01 192.168.122.209 [37072.232185] [tdb] Shutdown Tempesta DB Apr 26 02:22:02 192.168.122.209 [37072.464400] End test: cache.test_cache_control.ResponseMustRevalidateStaleIgnore.test Apr 26 02:22:02 192.168.122.209 [37072.489804] Start test: cache.test_cache_control.ResponseMustRevalidateStaleNotCached.test Apr 26 02:22:03 192.168.122.209 [37073.680177] [tdb] Start Tempesta DB Apr 26 02:22:03 192.168.122.209 [37073.830169] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:22:05 192.168.122.209 [37075.379417] [tempesta fw] Configuration processing is completed. Apr 26 02:22:05 192.168.122.209 [37075.465813] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:22:05 192.168.122.209 [37075.909795] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:22:05 192.168.122.209 [37075.937611] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:22:05 192.168.122.209 [37075.964357] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:22:05 192.168.122.209 [37076.019155] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:22:05 192.168.122.209 [37076.071064] [tempesta fw] Tempesta FW is ready Apr 26 02:22:08 192.168.122.209 [37078.704766] [tdb] Close table 'client0.tdb' Apr 26 02:22:08 192.168.122.209 [37078.888815] [tdb] Close table 'sessions0.tdb' Apr 26 02:22:11 192.168.122.209 [37082.165953] [tdb] Close table 'cache0.tdb' Apr 26 02:22:12 192.168.122.209 [37082.416786] [tdb] Close table 'filter0.tdb' Apr 26 02:22:12 192.168.122.209 [37082.417233] [tempesta fw] modules are stopped Apr 26 02:22:12 192.168.122.209 [37082.630740] [tempesta fw] exiting... Apr 26 02:22:12 192.168.122.209 [37082.760855] [tdb] Shutdown Tempesta DB Apr 26 02:22:12 192.168.122.209 [37082.997515] End test: cache.test_cache_control.ResponseMustRevalidateStaleNotCached.test Apr 26 02:22:12 192.168.122.209 [37083.019201] Start test: cache.test_cache_control.ResponseNoCache.test Apr 26 02:22:13 192.168.122.209 [37084.215586] [tdb] Start Tempesta DB Apr 26 02:22:14 192.168.122.209 [37084.368379] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:22:15 192.168.122.209 [37085.887438] [tempesta fw] Configuration processing is completed. Apr 26 02:22:15 192.168.122.209 [37085.946285] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:22:16 192.168.122.209 [37086.396492] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:22:16 192.168.122.209 [37086.425021] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:22:16 192.168.122.209 [37086.452646] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:22:16 192.168.122.209 [37086.491267] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:22:16 192.168.122.209 [37086.535192] [tempesta fw] Tempesta FW is ready Apr 26 02:22:16 192.168.122.209 [37087.152168] [tdb] Close table 'client0.tdb' Apr 26 02:22:17 192.168.122.209 [37087.350112] [tdb] Close table 'sessions0.tdb' Apr 26 02:22:20 192.168.122.209 [37090.467928] [tdb] Close table 'cache0.tdb' Apr 26 02:22:20 192.168.122.209 [37090.715010] [tdb] Close table 'filter0.tdb' Apr 26 02:22:20 192.168.122.209 [37090.715831] [tempesta fw] modules are stopped Apr 26 02:22:20 192.168.122.209 [37090.930970] [tempesta fw] exiting... Apr 26 02:22:20 192.168.122.209 [37091.071781] [tdb] Shutdown Tempesta DB Apr 26 02:22:21 192.168.122.209 [37091.297118] End test: cache.test_cache_control.ResponseNoCache.test Apr 26 02:22:21 192.168.122.209 [37091.310511] Start test: cache.test_cache_control.ResponseNoCacheIgnore.test Apr 26 02:22:22 192.168.122.209 [37092.513853] [tdb] Start Tempesta DB Apr 26 02:22:22 192.168.122.209 [37092.662502] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:22:23 192.168.122.209 [37094.251389] [tempesta fw] Configuration processing is completed. Apr 26 02:22:24 192.168.122.209 [37094.333621] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:22:24 192.168.122.209 [37094.782333] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:22:24 192.168.122.209 [37094.820760] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:22:24 192.168.122.209 [37094.850428] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:22:24 192.168.122.209 [37094.903412] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:22:24 192.168.122.209 [37094.943336] [tempesta fw] Tempesta FW is ready Apr 26 02:22:25 192.168.122.209 [37095.562801] [tdb] Close table 'client0.tdb' Apr 26 02:22:25 192.168.122.209 [37095.760068] [tdb] Close table 'sessions0.tdb' Apr 26 02:22:28 192.168.122.209 [37098.950990] [tdb] Close table 'cache0.tdb' Apr 26 02:22:28 192.168.122.209 [37099.193181] [tdb] Close table 'filter0.tdb' Apr 26 02:22:28 192.168.122.209 [37099.193625] [tempesta fw] modules are stopped Apr 26 02:22:29 192.168.122.209 [37099.388985] [tempesta fw] exiting... Apr 26 02:22:29 192.168.122.209 [37099.538004] [tdb] Shutdown Tempesta DB Apr 26 02:22:29 192.168.122.209 [37099.802124] End test: cache.test_cache_control.ResponseNoCacheIgnore.test Apr 26 02:22:29 192.168.122.209 [37099.811562] Start test: cache.test_cache_control.ResponseNoCacheIgnoreMulti.test Apr 26 02:22:30 192.168.122.209 [37100.995236] [tdb] Start Tempesta DB Apr 26 02:22:30 192.168.122.209 [37101.171136] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:22:32 192.168.122.209 [37102.727490] [tempesta fw] Configuration processing is completed. Apr 26 02:22:32 192.168.122.209 [37102.776930] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:22:32 192.168.122.209 [37103.213973] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:22:32 192.168.122.209 [37103.250590] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:22:33 192.168.122.209 [37103.277426] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:22:33 192.168.122.209 [37103.315451] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:22:33 192.168.122.209 [37103.355410] [tempesta fw] Tempesta FW is ready Apr 26 02:22:33 192.168.122.209 [37103.919934] [tdb] Close table 'client0.tdb' Apr 26 02:22:33 192.168.122.209 [37104.110257] [tdb] Close table 'sessions0.tdb' Apr 26 02:22:37 192.168.122.209 [37107.361573] [tdb] Close table 'cache0.tdb' Apr 26 02:22:37 192.168.122.209 [37107.613368] [tdb] Close table 'filter0.tdb' Apr 26 02:22:37 192.168.122.209 [37107.613803] [tempesta fw] modules are stopped Apr 26 02:22:37 192.168.122.209 [37107.806629] [tempesta fw] exiting... Apr 26 02:22:37 192.168.122.209 [37108.009175] [tdb] Shutdown Tempesta DB Apr 26 02:22:37 192.168.122.209 [37108.265257] End test: cache.test_cache_control.ResponseNoCacheIgnoreMulti.test Apr 26 02:22:38 192.168.122.209 [37108.275834] Start test: cache.test_cache_control.ResponseNoStore.test Apr 26 02:22:39 192.168.122.209 [37109.469763] [tdb] Start Tempesta DB Apr 26 02:22:39 192.168.122.209 [37109.629282] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:22:40 192.168.122.209 [37111.115621] [tempesta fw] Configuration processing is completed. Apr 26 02:22:40 192.168.122.209 [37111.168349] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:22:41 192.168.122.209 [37111.598852] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:22:41 192.168.122.209 [37111.634454] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:22:41 192.168.122.209 [37111.660424] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:22:41 192.168.122.209 [37111.711561] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:22:41 192.168.122.209 [37111.751514] [tempesta fw] Tempesta FW is ready Apr 26 02:22:42 192.168.122.209 [37112.348648] [tdb] Close table 'client0.tdb' Apr 26 02:22:42 192.168.122.209 [37112.538789] [tdb] Close table 'sessions0.tdb' Apr 26 02:22:45 192.168.122.209 [37115.743287] [tdb] Close table 'cache0.tdb' Apr 26 02:22:45 192.168.122.209 [37116.003767] [tdb] Close table 'filter0.tdb' Apr 26 02:22:45 192.168.122.209 [37116.004225] [tempesta fw] modules are stopped Apr 26 02:22:45 192.168.122.209 [37116.207988] [tempesta fw] exiting... Apr 26 02:22:46 192.168.122.209 [37116.363951] [tdb] Shutdown Tempesta DB Apr 26 02:22:46 192.168.122.209 [37116.601276] End test: cache.test_cache_control.ResponseNoStore.test Apr 26 02:22:46 192.168.122.209 [37116.620285] Start test: cache.test_cache_control.ResponsePrivate.test Apr 26 02:22:47 192.168.122.209 [37117.757860] [tdb] Start Tempesta DB Apr 26 02:22:47 192.168.122.209 [37117.921004] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:22:49 192.168.122.209 [37119.403699] [tempesta fw] Configuration processing is completed. Apr 26 02:22:49 192.168.122.209 [37119.454651] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:22:49 192.168.122.209 [37119.886423] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:22:49 192.168.122.209 [37119.917058] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:22:49 192.168.122.209 [37119.948552] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:22:49 192.168.122.209 [37119.995674] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:22:49 192.168.122.209 [37120.039607] [tempesta fw] Tempesta FW is ready Apr 26 02:22:50 192.168.122.209 [37120.638536] [tdb] Close table 'client0.tdb' Apr 26 02:22:50 192.168.122.209 [37120.831677] [tdb] Close table 'sessions0.tdb' Apr 26 02:22:53 192.168.122.209 [37123.987142] [tdb] Close table 'cache0.tdb' Apr 26 02:22:53 192.168.122.209 [37124.245602] [tdb] Close table 'filter0.tdb' Apr 26 02:22:53 192.168.122.209 [37124.246032] [tempesta fw] modules are stopped Apr 26 02:22:54 192.168.122.209 [37124.432091] [tempesta fw] exiting... Apr 26 02:22:54 192.168.122.209 [37124.602374] [tdb] Shutdown Tempesta DB Apr 26 02:22:54 192.168.122.209 [37124.815146] End test: cache.test_cache_control.ResponsePrivate.test Apr 26 02:22:54 192.168.122.209 [37124.834604] Start test: cache.test_cache_control.ResponseProxyRevalidateIgnore.test Apr 26 02:22:55 192.168.122.209 [37126.015266] [tdb] Start Tempesta DB Apr 26 02:22:55 192.168.122.209 [37126.155185] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:22:57 192.168.122.209 [37127.755812] [tempesta fw] Configuration processing is completed. Apr 26 02:22:57 192.168.122.209 [37127.804915] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:22:57 192.168.122.209 [37128.250203] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:22:58 192.168.122.209 [37128.276903] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:22:58 192.168.122.209 [37128.303960] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:22:58 192.168.122.209 [37128.347763] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:22:58 192.168.122.209 [37128.387741] [tempesta fw] Tempesta FW is ready Apr 26 02:23:00 192.168.122.209 [37130.952205] [tdb] Close table 'client0.tdb' Apr 26 02:23:00 192.168.122.209 [37131.158618] [tdb] Close table 'sessions0.tdb' Apr 26 02:23:04 192.168.122.209 [37134.388177] [tdb] Close table 'cache0.tdb' Apr 26 02:23:04 192.168.122.209 [37134.629417] [tdb] Close table 'filter0.tdb' Apr 26 02:23:04 192.168.122.209 [37134.629857] [tempesta fw] modules are stopped Apr 26 02:23:04 192.168.122.209 [37134.812022] [tempesta fw] exiting... Apr 26 02:23:04 192.168.122.209 [37134.938642] [tdb] Shutdown Tempesta DB Apr 26 02:23:04 192.168.122.209 [37135.210279] End test: cache.test_cache_control.ResponseProxyRevalidateIgnore.test Apr 26 02:23:04 192.168.122.209 [37135.226987] Start test: cache.test_cache_control.ResponseProxyRevalidateNotCached.test Apr 26 02:23:06 192.168.122.209 [37136.393301] [tdb] Start Tempesta DB Apr 26 02:23:06 192.168.122.209 [37136.548384] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:23:07 192.168.122.209 [37138.047880] [tempesta fw] Configuration processing is completed. Apr 26 02:23:07 192.168.122.209 [37138.100349] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:23:08 192.168.122.209 [37138.529575] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:23:08 192.168.122.209 [37138.557100] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:23:08 192.168.122.209 [37138.584696] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:23:08 192.168.122.209 [37138.631913] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:23:08 192.168.122.209 [37138.679871] [tempesta fw] Tempesta FW is ready Apr 26 02:23:11 192.168.122.209 [37141.290223] [tdb] Close table 'client0.tdb' Apr 26 02:23:11 192.168.122.209 [37141.492561] [tdb] Close table 'sessions0.tdb' Apr 26 02:23:14 192.168.122.209 [37144.739619] [tdb] Close table 'cache0.tdb' Apr 26 02:23:14 192.168.122.209 [37144.980296] [tdb] Close table 'filter0.tdb' Apr 26 02:23:14 192.168.122.209 [37144.980732] [tempesta fw] modules are stopped Apr 26 02:23:14 192.168.122.209 [37145.161690] [tempesta fw] exiting... Apr 26 02:23:15 192.168.122.209 [37145.298854] [tdb] Shutdown Tempesta DB Apr 26 02:23:15 192.168.122.209 [37145.504168] End test: cache.test_cache_control.ResponseProxyRevalidateNotCached.test Apr 26 02:23:15 192.168.122.209 [37145.518343] Start test: cache.test_cache_control.ResponseProxyRevalidateStaleIgnore.test Apr 26 02:23:16 192.168.122.209 [37146.649541] [tdb] Start Tempesta DB Apr 26 02:23:16 192.168.122.209 [37146.806315] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:23:18 192.168.122.209 [37148.296099] [tempesta fw] Configuration processing is completed. Apr 26 02:23:18 192.168.122.209 [37148.357077] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:23:18 192.168.122.209 [37148.775933] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:23:18 192.168.122.209 [37148.801786] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:23:18 192.168.122.209 [37148.827651] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:23:18 192.168.122.209 [37148.880000] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:23:18 192.168.122.209 [37148.927985] [tempesta fw] Tempesta FW is ready Apr 26 02:23:21 192.168.122.209 [37151.509530] [tdb] Close table 'client0.tdb' Apr 26 02:23:21 192.168.122.209 [37151.695166] [tdb] Close table 'sessions0.tdb' Apr 26 02:23:24 192.168.122.209 [37154.892191] [tdb] Close table 'cache0.tdb' Apr 26 02:23:24 192.168.122.209 [37155.120886] [tdb] Close table 'filter0.tdb' Apr 26 02:23:24 192.168.122.209 [37155.121326] [tempesta fw] modules are stopped Apr 26 02:23:25 192.168.122.209 [37155.327000] [tempesta fw] exiting... Apr 26 02:23:25 192.168.122.209 [37155.504415] [tdb] Shutdown Tempesta DB Apr 26 02:23:25 192.168.122.209 [37155.725427] End test: cache.test_cache_control.ResponseProxyRevalidateStaleIgnore.test Apr 26 02:23:25 192.168.122.209 [37155.741500] Start test: cache.test_cache_control.ResponseProxyRevalidateStaleNotCached.test Apr 26 02:23:26 192.168.122.209 [37156.850432] [tdb] Start Tempesta DB Apr 26 02:23:26 192.168.122.209 [37157.004776] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:23:28 192.168.122.209 [37158.492214] [tempesta fw] Configuration processing is completed. Apr 26 02:23:28 192.168.122.209 [37158.541901] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:23:28 192.168.122.209 [37158.963798] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:23:28 192.168.122.209 [37158.989816] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:23:28 192.168.122.209 [37159.015547] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:23:28 192.168.122.209 [37159.060161] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:23:28 192.168.122.209 [37159.108109] [tempesta fw] Tempesta FW is ready Apr 26 02:23:31 192.168.122.209 [37161.752734] [tdb] Close table 'client0.tdb' Apr 26 02:23:31 192.168.122.209 [37161.938158] [tdb] Close table 'sessions0.tdb' Apr 26 02:23:34 192.168.122.209 [37165.107611] [tdb] Close table 'cache0.tdb' Apr 26 02:23:35 192.168.122.209 [37165.347684] [tdb] Close table 'filter0.tdb' Apr 26 02:23:35 192.168.122.209 [37165.348123] [tempesta fw] modules are stopped Apr 26 02:23:35 192.168.122.209 [37165.585571] [tempesta fw] exiting... Apr 26 02:23:35 192.168.122.209 [37165.717579] [tdb] Shutdown Tempesta DB Apr 26 02:23:35 192.168.122.209 [37165.977921] End test: cache.test_cache_control.ResponseProxyRevalidateStaleNotCached.test Apr 26 02:23:35 192.168.122.209 [37166.001198] Start test: cache.test_cache_control.ResponsePublicCached.test Apr 26 02:23:36 192.168.122.209 [37167.200190] [tdb] Start Tempesta DB Apr 26 02:23:37 192.168.122.209 [37167.347673] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:23:38 192.168.122.209 [37168.876335] [tempesta fw] Configuration processing is completed. Apr 26 02:23:38 192.168.122.209 [37168.930946] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:23:39 192.168.122.209 [37169.355434] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:23:39 192.168.122.209 [37169.381453] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:23:39 192.168.122.209 [37169.406936] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:23:39 192.168.122.209 [37169.496233] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:23:39 192.168.122.209 [37169.536247] [tempesta fw] Tempesta FW is ready Apr 26 02:23:39 192.168.122.209 [37170.169874] [tdb] Close table 'client0.tdb' Apr 26 02:23:40 192.168.122.209 [37170.334424] [tdb] Close table 'sessions0.tdb' Apr 26 02:23:43 192.168.122.209 [37173.478375] [tdb] Close table 'cache0.tdb' Apr 26 02:23:43 192.168.122.209 [37173.727510] [tdb] Close table 'filter0.tdb' Apr 26 02:23:43 192.168.122.209 [37173.727950] [tempesta fw] modules are stopped Apr 26 02:23:43 192.168.122.209 [37174.026984] [tempesta fw] exiting... Apr 26 02:23:43 192.168.122.209 [37174.209052] [tdb] Shutdown Tempesta DB Apr 26 02:23:44 192.168.122.209 [37174.428562] End test: cache.test_cache_control.ResponsePublicCached.test Apr 26 02:23:44 192.168.122.209 [37174.441510] Start test: cache.test_cache_control.ResponsePublicCached2.test Apr 26 02:23:45 192.168.122.209 [37175.658043] [tdb] Start Tempesta DB Apr 26 02:23:45 192.168.122.209 [37175.821230] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:23:47 192.168.122.209 [37177.348755] [tempesta fw] Configuration processing is completed. Apr 26 02:23:47 192.168.122.209 [37177.442342] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:23:47 192.168.122.209 [37177.870157] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:23:47 192.168.122.209 [37177.896974] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:23:47 192.168.122.209 [37177.923978] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:23:47 192.168.122.209 [37178.004338] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:23:47 192.168.122.209 [37178.044370] [tempesta fw] Tempesta FW is ready Apr 26 02:23:48 192.168.122.209 [37178.657303] [tdb] Close table 'client0.tdb' Apr 26 02:23:48 192.168.122.209 [37178.854146] [tdb] Close table 'sessions0.tdb' Apr 26 02:23:51 192.168.122.209 [37182.051549] [tdb] Close table 'cache0.tdb' Apr 26 02:23:51 192.168.122.209 [37182.262356] [tdb] Close table 'filter0.tdb' Apr 26 02:23:51 192.168.122.209 [37182.262784] [tempesta fw] modules are stopped Apr 26 02:23:52 192.168.122.209 [37182.480616] [tempesta fw] exiting... Apr 26 02:23:52 192.168.122.209 [37182.616892] [tdb] Shutdown Tempesta DB Apr 26 02:23:52 192.168.122.209 [37182.841016] End test: cache.test_cache_control.ResponsePublicCached2.test Apr 26 02:23:52 192.168.122.209 [37182.871406] Start test: cache.test_cache_control.ResponsePublicIgnore.test Apr 26 02:23:53 192.168.122.209 [37184.090990] [tdb] Start Tempesta DB Apr 26 02:23:53 192.168.122.209 [37184.252910] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:23:55 192.168.122.209 [37185.800510] [tempesta fw] Configuration processing is completed. Apr 26 02:23:55 192.168.122.209 [37185.849856] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:23:55 192.168.122.209 [37186.267410] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:23:56 192.168.122.209 [37186.293562] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:23:56 192.168.122.209 [37186.319242] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:23:56 192.168.122.209 [37186.372500] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:23:56 192.168.122.209 [37186.412440] [tempesta fw] Tempesta FW is ready Apr 26 02:23:56 192.168.122.209 [37187.051271] [tdb] Close table 'client0.tdb' Apr 26 02:23:56 192.168.122.209 [37187.253106] [tdb] Close table 'sessions0.tdb' Apr 26 02:24:00 192.168.122.209 [37190.397012] [tdb] Close table 'cache0.tdb' Apr 26 02:24:00 192.168.122.209 [37190.634041] [tdb] Close table 'filter0.tdb' Apr 26 02:24:00 192.168.122.209 [37190.634475] [tempesta fw] modules are stopped Apr 26 02:24:00 192.168.122.209 [37190.796477] [tempesta fw] exiting... Apr 26 02:24:00 192.168.122.209 [37190.951258] [tdb] Shutdown Tempesta DB Apr 26 02:24:00 192.168.122.209 [37191.179735] End test: cache.test_cache_control.ResponsePublicIgnore.test Apr 26 02:24:00 192.168.122.209 [37191.193538] Start test: cache.test_cache_control.ResponsePublicIgnore2.test Apr 26 02:24:02 192.168.122.209 [37192.367188] [tdb] Start Tempesta DB Apr 26 02:24:02 192.168.122.209 [37192.510784] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:24:03 192.168.122.209 [37194.081064] [tempesta fw] Configuration processing is completed. Apr 26 02:24:03 192.168.122.209 [37194.148210] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:24:04 192.168.122.209 [37194.566408] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:24:04 192.168.122.209 [37194.593836] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:24:04 192.168.122.209 [37194.624323] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:24:04 192.168.122.209 [37194.672633] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:24:04 192.168.122.209 [37194.712547] [tempesta fw] Tempesta FW is ready Apr 26 02:24:05 192.168.122.209 [37195.347659] [tdb] Close table 'client0.tdb' Apr 26 02:24:05 192.168.122.209 [37195.542037] [tdb] Close table 'sessions0.tdb' Apr 26 02:24:08 192.168.122.209 [37198.719171] [tdb] Close table 'cache0.tdb' Apr 26 02:24:08 192.168.122.209 [37198.975637] [tdb] Close table 'filter0.tdb' Apr 26 02:24:08 192.168.122.209 [37198.976076] [tempesta fw] modules are stopped Apr 26 02:24:08 192.168.122.209 [37199.176724] [tempesta fw] exiting... Apr 26 02:24:09 192.168.122.209 [37199.341578] [tdb] Shutdown Tempesta DB Apr 26 02:24:09 192.168.122.209 [37199.553923] End test: cache.test_cache_control.ResponsePublicIgnore2.test Apr 26 02:24:09 192.168.122.209 [37199.566592] Start test: cache.test_cache_control.ResponsePublicNotCached.test Apr 26 02:24:10 192.168.122.209 [37200.678473] [tdb] Start Tempesta DB Apr 26 02:24:10 192.168.122.209 [37200.823822] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:24:12 192.168.122.209 [37202.328674] [tempesta fw] Configuration processing is completed. Apr 26 02:24:12 192.168.122.209 [37202.378502] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:24:12 192.168.122.209 [37202.804082] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:24:12 192.168.122.209 [37202.830758] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:24:12 192.168.122.209 [37202.857366] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:24:12 192.168.122.209 [37202.900700] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:24:12 192.168.122.209 [37202.940658] [tempesta fw] Tempesta FW is ready Apr 26 02:24:13 192.168.122.209 [37203.534291] [tdb] Close table 'client0.tdb' Apr 26 02:24:13 192.168.122.209 [37203.727189] [tdb] Close table 'sessions0.tdb' Apr 26 02:24:16 192.168.122.209 [37206.927530] [tdb] Close table 'cache0.tdb' Apr 26 02:24:16 192.168.122.209 [37207.170985] [tdb] Close table 'filter0.tdb' Apr 26 02:24:16 192.168.122.209 [37207.171432] [tempesta fw] modules are stopped Apr 26 02:24:17 192.168.122.209 [37207.348838] [tempesta fw] exiting... Apr 26 02:24:17 192.168.122.209 [37207.475763] [tdb] Shutdown Tempesta DB Apr 26 02:24:17 192.168.122.209 [37207.672005] End test: cache.test_cache_control.ResponsePublicNotCached.test Apr 26 02:24:17 192.168.122.209 [37207.691547] Start test: cache.test_cache_control.ResponseSMaxageCached.test Apr 26 02:24:18 192.168.122.209 [37208.897701] [tdb] Start Tempesta DB Apr 26 02:24:18 192.168.122.209 [37209.041678] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:24:20 192.168.122.209 [37210.588785] [tempesta fw] Configuration processing is completed. Apr 26 02:24:20 192.168.122.209 [37210.643013] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:24:20 192.168.122.209 [37211.056308] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:24:20 192.168.122.209 [37211.123910] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:24:20 192.168.122.209 [37211.158609] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:24:20 192.168.122.209 [37211.196741] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:24:20 192.168.122.209 [37211.240749] [tempesta fw] Tempesta FW is ready Apr 26 02:24:21 192.168.122.209 [37211.877314] [tdb] Close table 'client0.tdb' Apr 26 02:24:21 192.168.122.209 [37212.077031] [tdb] Close table 'sessions0.tdb' Apr 26 02:24:24 192.168.122.209 [37215.263422] [tdb] Close table 'cache0.tdb' Apr 26 02:24:25 192.168.122.209 [37215.500523] [tdb] Close table 'filter0.tdb' Apr 26 02:24:25 192.168.122.209 [37215.500990] [tempesta fw] modules are stopped Apr 26 02:24:25 192.168.122.209 [37215.676440] [tempesta fw] exiting... Apr 26 02:24:25 192.168.122.209 [37215.834553] [tdb] Shutdown Tempesta DB Apr 26 02:24:25 192.168.122.209 [37216.062126] End test: cache.test_cache_control.ResponseSMaxageCached.test Apr 26 02:24:25 192.168.122.209 [37216.072752] Start test: cache.test_cache_control.ResponseSMaxageIgnore.test Apr 26 02:24:27 192.168.122.209 [37217.307522] [tdb] Start Tempesta DB Apr 26 02:24:27 192.168.122.209 [37217.460658] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:24:28 192.168.122.209 [37219.032955] [tempesta fw] Configuration processing is completed. Apr 26 02:24:28 192.168.122.209 [37219.094187] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:24:29 192.168.122.209 [37219.545470] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:24:29 192.168.122.209 [37219.571663] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:24:29 192.168.122.209 [37219.597922] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:24:29 192.168.122.209 [37219.644924] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:24:29 192.168.122.209 [37219.688868] [tempesta fw] Tempesta FW is ready Apr 26 02:24:31 192.168.122.209 [37221.811151] [tdb] Close table 'client0.tdb' Apr 26 02:24:31 192.168.122.209 [37222.007694] [tdb] Close table 'sessions0.tdb' Apr 26 02:24:34 192.168.122.209 [37225.127067] [tdb] Close table 'cache0.tdb' Apr 26 02:24:35 192.168.122.209 [37225.384478] [tdb] Close table 'filter0.tdb' Apr 26 02:24:35 192.168.122.209 [37225.385310] [tempesta fw] modules are stopped Apr 26 02:24:35 192.168.122.209 [37225.577008] [tempesta fw] exiting... Apr 26 02:24:35 192.168.122.209 [37225.717124] [tdb] Shutdown Tempesta DB Apr 26 02:24:35 192.168.122.209 [37225.946903] End test: cache.test_cache_control.ResponseSMaxageIgnore.test Apr 26 02:24:35 192.168.122.209 [37225.957932] Start test: cache.test_cache_control.ResponseSMaxageMaxAgeIgnore.test Apr 26 02:24:36 192.168.122.209 [37227.151075] [tdb] Start Tempesta DB Apr 26 02:24:37 192.168.122.209 [37227.310772] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:24:38 192.168.122.209 [37228.933118] [tempesta fw] Configuration processing is completed. Apr 26 02:24:38 192.168.122.209 [37228.982770] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:24:39 192.168.122.209 [37229.416144] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:24:39 192.168.122.209 [37229.442660] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:24:39 192.168.122.209 [37229.468512] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:24:39 192.168.122.209 [37229.508973] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:24:39 192.168.122.209 [37229.560991] [tempesta fw] Tempesta FW is ready Apr 26 02:24:41 192.168.122.209 [37231.651066] [tdb] Close table 'client0.tdb' Apr 26 02:24:41 192.168.122.209 [37231.838253] [tdb] Close table 'sessions0.tdb' Apr 26 02:24:44 192.168.122.209 [37235.005853] [tdb] Close table 'cache0.tdb' Apr 26 02:24:44 192.168.122.209 [37235.235334] [tdb] Close table 'filter0.tdb' Apr 26 02:24:44 192.168.122.209 [37235.235763] [tempesta fw] modules are stopped Apr 26 02:24:45 192.168.122.209 [37235.434521] [tempesta fw] exiting... Apr 26 02:24:45 192.168.122.209 [37235.623168] [tdb] Shutdown Tempesta DB Apr 26 02:24:45 192.168.122.209 [37235.848151] End test: cache.test_cache_control.ResponseSMaxageMaxAgeIgnore.test Apr 26 02:24:45 192.168.122.209 [37235.878133] Start test: cache.test_cache_control.ResponseSMaxageMaxAgeNotCached.test Apr 26 02:24:46 192.168.122.209 [37237.079510] [tdb] Start Tempesta DB Apr 26 02:24:46 192.168.122.209 [37237.222563] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:24:48 192.168.122.209 [37238.729192] [tempesta fw] Configuration processing is completed. Apr 26 02:24:48 192.168.122.209 [37238.778102] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:24:48 192.168.122.209 [37239.204064] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:24:48 192.168.122.209 [37239.235692] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:24:48 192.168.122.209 [37239.262775] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:24:49 192.168.122.209 [37239.313172] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:24:49 192.168.122.209 [37239.357254] [tempesta fw] Tempesta FW is ready Apr 26 02:24:51 192.168.122.209 [37241.963463] [tdb] Close table 'client0.tdb' Apr 26 02:24:51 192.168.122.209 [37242.150935] [tdb] Close table 'sessions0.tdb' Apr 26 02:24:55 192.168.122.209 [37245.320544] [tdb] Close table 'cache0.tdb' Apr 26 02:24:55 192.168.122.209 [37245.560044] [tdb] Close table 'filter0.tdb' Apr 26 02:24:55 192.168.122.209 [37245.560475] [tempesta fw] modules are stopped Apr 26 02:24:55 192.168.122.209 [37245.736190] [tempesta fw] exiting... Apr 26 02:24:55 192.168.122.209 [37245.878107] [tdb] Shutdown Tempesta DB Apr 26 02:24:55 192.168.122.209 [37246.062745] End test: cache.test_cache_control.ResponseSMaxageMaxAgeNotCached.test Apr 26 02:24:55 192.168.122.209 [37246.077378] Start test: cache.test_cache_control.ResponseSMaxageNotCached.test Apr 26 02:24:57 192.168.122.209 [37247.315127] [tdb] Start Tempesta DB Apr 26 02:24:57 192.168.122.209 [37247.458622] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:24:58 192.168.122.209 [37248.925631] [tempesta fw] Configuration processing is completed. Apr 26 02:24:58 192.168.122.209 [37248.975255] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:24:59 192.168.122.209 [37249.389860] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:24:59 192.168.122.209 [37249.415922] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:24:59 192.168.122.209 [37249.442520] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:24:59 192.168.122.209 [37249.501279] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:24:59 192.168.122.209 [37249.541226] [tempesta fw] Tempesta FW is ready Apr 26 02:25:01 192.168.122.209 [37252.119053] [tdb] Close table 'client0.tdb' Apr 26 02:25:02 192.168.122.209 [37252.325553] [tdb] Close table 'sessions0.tdb' Apr 26 02:25:05 192.168.122.209 [37255.434113] [tdb] Close table 'cache0.tdb' Apr 26 02:25:05 192.168.122.209 [37255.681082] [tdb] Close table 'filter0.tdb' Apr 26 02:25:05 192.168.122.209 [37255.681542] [tempesta fw] modules are stopped Apr 26 02:25:05 192.168.122.209 [37255.869951] [tempesta fw] exiting... Apr 26 02:25:05 192.168.122.209 [37256.051941] [tdb] Shutdown Tempesta DB Apr 26 02:25:06 192.168.122.209 [37256.333817] End test: cache.test_cache_control.ResponseSMaxageNotCached.test Apr 26 02:25:06 192.168.122.209 [37256.345345] Start test: cache.test_cache_control.ResponseSMaxageNotCached2.test Apr 26 02:25:07 192.168.122.209 [37257.558506] [tdb] Start Tempesta DB Apr 26 02:25:07 192.168.122.209 [37257.703374] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:25:08 192.168.122.209 [37259.165448] [tempesta fw] Configuration processing is completed. Apr 26 02:25:08 192.168.122.209 [37259.214749] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:25:09 192.168.122.209 [37259.632785] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:25:09 192.168.122.209 [37259.658979] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:25:09 192.168.122.209 [37259.685651] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:25:09 192.168.122.209 [37259.725411] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:25:09 192.168.122.209 [37259.765357] [tempesta fw] Tempesta FW is ready Apr 26 02:25:12 192.168.122.209 [37262.351695] [tdb] Close table 'client0.tdb' Apr 26 02:25:12 192.168.122.209 [37262.559690] [tdb] Close table 'sessions0.tdb' Apr 26 02:25:15 192.168.122.209 [37265.658290] [tdb] Close table 'cache0.tdb' Apr 26 02:25:15 192.168.122.209 [37265.898026] [tdb] Close table 'filter0.tdb' Apr 26 02:25:15 192.168.122.209 [37265.898459] [tempesta fw] modules are stopped Apr 26 02:25:15 192.168.122.209 [37266.101204] [tempesta fw] exiting... Apr 26 02:25:15 192.168.122.209 [37266.264471] [tdb] Shutdown Tempesta DB Apr 26 02:25:16 192.168.122.209 [37266.494300] End test: cache.test_cache_control.ResponseSMaxageNotCached2.test Apr 26 02:25:16 192.168.122.209 [37266.518510] Start test: cache.test_cache_control.ResponseStaleCached.test Apr 26 02:25:17 192.168.122.209 [37267.742331] [tdb] Start Tempesta DB Apr 26 02:25:17 192.168.122.209 [37267.888750] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:25:19 192.168.122.209 [37269.313578] [tempesta fw] Configuration processing is completed. Apr 26 02:25:19 192.168.122.209 [37269.364233] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:25:19 192.168.122.209 [37269.778888] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:25:19 192.168.122.209 [37269.804378] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:25:19 192.168.122.209 [37269.829393] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:25:19 192.168.122.209 [37269.877553] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:25:19 192.168.122.209 [37269.921487] [tempesta fw] Tempesta FW is ready Apr 26 02:25:21 192.168.122.209 [37272.062516] [tdb] Close table 'client0.tdb' Apr 26 02:25:21 192.168.122.209 [37272.251060] [tdb] Close table 'sessions0.tdb' Apr 26 02:25:25 192.168.122.209 [37275.414452] [tdb] Close table 'cache0.tdb' Apr 26 02:25:25 192.168.122.209 [37275.652590] [tdb] Close table 'filter0.tdb' Apr 26 02:25:25 192.168.122.209 [37275.653004] [tempesta fw] modules are stopped Apr 26 02:25:25 192.168.122.209 [37275.869340] [tempesta fw] exiting... Apr 26 02:25:25 192.168.122.209 [37276.022720] [tdb] Shutdown Tempesta DB Apr 26 02:25:25 192.168.122.209 [37276.213256] End test: cache.test_cache_control.ResponseStaleCached.test Apr 26 02:25:25 192.168.122.209 [37276.241997] Start test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsDefaultCache.test Apr 26 02:25:27 192.168.122.209 [37277.389306] [tdb] Start Tempesta DB Apr 26 02:25:27 192.168.122.209 [37277.530227] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:25:28 192.168.122.209 [37278.982002] [tempesta fw] Configuration processing is completed. Apr 26 02:25:28 192.168.122.209 [37279.032370] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:25:29 192.168.122.209 [37279.444267] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:25:29 192.168.122.209 [37279.469790] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:25:29 192.168.122.209 [37279.502146] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:25:29 192.168.122.209 [37279.549654] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:25:29 192.168.122.209 [37279.593524] [tempesta fw] Tempesta FW is ready Apr 26 02:25:29 192.168.122.209 [37280.199886] [tdb] Close table 'client0.tdb' Apr 26 02:25:30 192.168.122.209 [37280.410227] [tdb] Close table 'sessions0.tdb' Apr 26 02:25:33 192.168.122.209 [37283.590831] [tdb] Close table 'cache0.tdb' Apr 26 02:25:33 192.168.122.209 [37283.821888] [tdb] Close table 'filter0.tdb' Apr 26 02:25:33 192.168.122.209 [37283.822343] [tempesta fw] modules are stopped Apr 26 02:25:33 192.168.122.209 [37284.014038] [tempesta fw] exiting... Apr 26 02:25:33 192.168.122.209 [37284.157772] [tdb] Shutdown Tempesta DB Apr 26 02:25:34 192.168.122.209 [37284.431432] End test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsDefaultCache.test Apr 26 02:25:34 192.168.122.209 [37284.450717] Start test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsMaxAgeCache.test Apr 26 02:25:35 192.168.122.209 [37285.664378] [tdb] Start Tempesta DB Apr 26 02:25:35 192.168.122.209 [37285.812015] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:25:37 192.168.122.209 [37287.294112] [tempesta fw] Configuration processing is completed. Apr 26 02:25:37 192.168.122.209 [37287.344138] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:25:37 192.168.122.209 [37287.773117] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:25:37 192.168.122.209 [37287.799405] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:25:37 192.168.122.209 [37287.825705] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:25:37 192.168.122.209 [37287.877763] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:25:37 192.168.122.209 [37287.917709] [tempesta fw] Tempesta FW is ready Apr 26 02:25:38 192.168.122.209 [37288.501445] [tdb] Close table 'client0.tdb' Apr 26 02:25:38 192.168.122.209 [37288.697223] [tdb] Close table 'sessions0.tdb' Apr 26 02:25:41 192.168.122.209 [37291.904975] [tdb] Close table 'cache0.tdb' Apr 26 02:25:41 192.168.122.209 [37292.128993] [tdb] Close table 'filter0.tdb' Apr 26 02:25:41 192.168.122.209 [37292.129435] [tempesta fw] modules are stopped Apr 26 02:25:42 192.168.122.209 [37292.329942] [tempesta fw] exiting... Apr 26 02:25:42 192.168.122.209 [37292.490328] [tdb] Shutdown Tempesta DB Apr 26 02:25:42 192.168.122.209 [37292.713151] End test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsMaxAgeCache.test Apr 26 02:25:42 192.168.122.209 [37292.737008] Start test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsMustRevalidateCache2.test Apr 26 02:25:43 192.168.122.209 [37293.945381] [tdb] Start Tempesta DB Apr 26 02:25:43 192.168.122.209 [37294.090563] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:25:45 192.168.122.209 [37295.581922] [tempesta fw] Configuration processing is completed. Apr 26 02:25:45 192.168.122.209 [37295.633219] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:25:45 192.168.122.209 [37296.063157] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:25:45 192.168.122.209 [37296.089721] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:25:45 192.168.122.209 [37296.117375] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:25:45 192.168.122.209 [37296.161885] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:25:45 192.168.122.209 [37296.201825] [tempesta fw] Tempesta FW is ready Apr 26 02:25:46 192.168.122.209 [37296.857167] [tdb] Close table 'client0.tdb' Apr 26 02:25:46 192.168.122.209 [37297.039404] [tdb] Close table 'sessions0.tdb' Apr 26 02:25:49 192.168.122.209 [37300.234585] [tdb] Close table 'cache0.tdb' Apr 26 02:25:50 192.168.122.209 [37300.490823] [tdb] Close table 'filter0.tdb' Apr 26 02:25:50 192.168.122.209 [37300.491251] [tempesta fw] modules are stopped Apr 26 02:25:50 192.168.122.209 [37300.710699] [tempesta fw] exiting... Apr 26 02:25:50 192.168.122.209 [37300.869496] [tdb] Shutdown Tempesta DB Apr 26 02:25:50 192.168.122.209 [37301.096347] End test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsMustRevalidateCache2.test Apr 26 02:25:50 192.168.122.209 [37301.107514] Start test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsNoCacheCache.test Apr 26 02:25:52 192.168.122.209 [37302.308078] [tdb] Start Tempesta DB Apr 26 02:25:52 192.168.122.209 [37302.451590] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:25:53 192.168.122.209 [37303.958018] [tempesta fw] Configuration processing is completed. Apr 26 02:25:53 192.168.122.209 [37304.011882] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:25:54 192.168.122.209 [37304.430857] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:25:54 192.168.122.209 [37304.457242] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:25:54 192.168.122.209 [37304.483501] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:25:54 192.168.122.209 [37304.533995] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:25:54 192.168.122.209 [37304.577932] [tempesta fw] Tempesta FW is ready Apr 26 02:25:54 192.168.122.209 [37305.219074] [tdb] Close table 'client0.tdb' Apr 26 02:25:55 192.168.122.209 [37305.415012] [tdb] Close table 'sessions0.tdb' Apr 26 02:25:58 192.168.122.209 [37308.608850] [tdb] Close table 'cache0.tdb' Apr 26 02:25:58 192.168.122.209 [37308.831691] [tdb] Close table 'filter0.tdb' Apr 26 02:25:58 192.168.122.209 [37308.832133] [tempesta fw] modules are stopped Apr 26 02:25:58 192.168.122.209 [37309.079429] [tempesta fw] exiting... Apr 26 02:25:58 192.168.122.209 [37309.206192] [tdb] Shutdown Tempesta DB Apr 26 02:25:59 192.168.122.209 [37309.425353] End test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsNoCacheCache.test Apr 26 02:25:59 192.168.122.209 [37309.445907] Start test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsNoStoreCache.test Apr 26 02:26:00 192.168.122.209 [37310.620720] [tdb] Start Tempesta DB Apr 26 02:26:00 192.168.122.209 [37310.772818] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:26:01 192.168.122.209 [37312.230065] [tempesta fw] Configuration processing is completed. Apr 26 02:26:02 192.168.122.209 [37312.321091] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:26:02 192.168.122.209 [37312.820348] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:26:02 192.168.122.209 [37312.846371] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:26:02 192.168.122.209 [37312.872946] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:26:02 192.168.122.209 [37312.926093] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:26:02 192.168.122.209 [37312.970024] [tempesta fw] Tempesta FW is ready Apr 26 02:26:03 192.168.122.209 [37313.601467] [tdb] Close table 'client0.tdb' Apr 26 02:26:03 192.168.122.209 [37313.782617] [tdb] Close table 'sessions0.tdb' Apr 26 02:26:06 192.168.122.209 [37316.970527] [tdb] Close table 'cache0.tdb' Apr 26 02:26:06 192.168.122.209 [37317.192768] [tdb] Close table 'filter0.tdb' Apr 26 02:26:06 192.168.122.209 [37317.193206] [tempesta fw] modules are stopped Apr 26 02:26:07 192.168.122.209 [37317.367553] [tempesta fw] exiting... Apr 26 02:26:07 192.168.122.209 [37317.501853] [tdb] Shutdown Tempesta DB Apr 26 02:26:07 192.168.122.209 [37317.741602] End test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsNoStoreCache.test Apr 26 02:26:07 192.168.122.209 [37317.754799] Start test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsNoTransformCache.test Apr 26 02:26:08 192.168.122.209 [37318.957232] [tdb] Start Tempesta DB Apr 26 02:26:08 192.168.122.209 [37319.090804] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:26:10 192.168.122.209 [37320.626218] [tempesta fw] Configuration processing is completed. Apr 26 02:26:10 192.168.122.209 [37320.675925] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:26:10 192.168.122.209 [37321.095022] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:26:10 192.168.122.209 [37321.121104] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:26:10 192.168.122.209 [37321.146997] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:26:10 192.168.122.209 [37321.202204] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:26:10 192.168.122.209 [37321.242127] [tempesta fw] Tempesta FW is ready Apr 26 02:26:11 192.168.122.209 [37321.868908] [tdb] Close table 'client0.tdb' Apr 26 02:26:11 192.168.122.209 [37322.079114] [tdb] Close table 'sessions0.tdb' Apr 26 02:26:15 192.168.122.209 [37325.281655] [tdb] Close table 'cache0.tdb' Apr 26 02:26:15 192.168.122.209 [37325.489833] [tdb] Close table 'filter0.tdb' Apr 26 02:26:15 192.168.122.209 [37325.490301] [tempesta fw] modules are stopped Apr 26 02:26:15 192.168.122.209 [37325.677781] [tempesta fw] exiting... Apr 26 02:26:15 192.168.122.209 [37325.808418] [tdb] Shutdown Tempesta DB Apr 26 02:26:15 192.168.122.209 [37326.046120] End test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsNoTransformCache.test Apr 26 02:26:15 192.168.122.209 [37326.056750] Start test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsPrivateCache.test Apr 26 02:26:16 192.168.122.209 [37327.209734] [tdb] Start Tempesta DB Apr 26 02:26:17 192.168.122.209 [37327.357310] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:26:18 192.168.122.209 [37328.854367] [tempesta fw] Configuration processing is completed. Apr 26 02:26:18 192.168.122.209 [37328.903703] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:26:19 192.168.122.209 [37329.318860] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:26:19 192.168.122.209 [37329.345477] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:26:19 192.168.122.209 [37329.371870] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:26:19 192.168.122.209 [37329.414240] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:26:19 192.168.122.209 [37329.478259] [tempesta fw] Tempesta FW is ready Apr 26 02:26:19 192.168.122.209 [37330.075372] [tdb] Close table 'client0.tdb' Apr 26 02:26:20 192.168.122.209 [37330.300699] [tdb] Close table 'sessions0.tdb' Apr 26 02:26:23 192.168.122.209 [37333.446850] [tdb] Close table 'cache0.tdb' Apr 26 02:26:23 192.168.122.209 [37333.688459] [tdb] Close table 'filter0.tdb' Apr 26 02:26:23 192.168.122.209 [37333.688905] [tempesta fw] modules are stopped Apr 26 02:26:23 192.168.122.209 [37333.878377] [tempesta fw] exiting... Apr 26 02:26:23 192.168.122.209 [37334.031157] [tdb] Shutdown Tempesta DB Apr 26 02:26:23 192.168.122.209 [37334.269263] End test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsPrivateCache.test Apr 26 02:26:24 192.168.122.209 [37334.294664] Start test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsProxyRevalidateCache.test Apr 26 02:26:25 192.168.122.209 [37335.548920] [tdb] Start Tempesta DB Apr 26 02:26:25 192.168.122.209 [37335.684939] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:26:26 192.168.122.209 [37337.218448] [tempesta fw] Configuration processing is completed. Apr 26 02:26:27 192.168.122.209 [37337.307525] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:26:27 192.168.122.209 [37337.734555] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:26:27 192.168.122.209 [37337.761060] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:26:27 192.168.122.209 [37337.787970] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:26:27 192.168.122.209 [37337.830340] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:26:27 192.168.122.209 [37337.870336] [tempesta fw] Tempesta FW is ready Apr 26 02:26:28 192.168.122.209 [37338.485854] [tdb] Close table 'client0.tdb' Apr 26 02:26:28 192.168.122.209 [37338.694697] [tdb] Close table 'sessions0.tdb' Apr 26 02:26:31 192.168.122.209 [37341.869112] [tdb] Close table 'cache0.tdb' Apr 26 02:26:31 192.168.122.209 [37342.110070] [tdb] Close table 'filter0.tdb' Apr 26 02:26:31 192.168.122.209 [37342.110508] [tempesta fw] modules are stopped Apr 26 02:26:32 192.168.122.209 [37342.349164] [tempesta fw] exiting... Apr 26 02:26:32 192.168.122.209 [37342.495787] [tdb] Shutdown Tempesta DB Apr 26 02:26:32 192.168.122.209 [37342.719225] End test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsProxyRevalidateCache.test Apr 26 02:26:32 192.168.122.209 [37342.730591] Start test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsPublicCache.test Apr 26 02:26:33 192.168.122.209 [37343.935216] [tdb] Start Tempesta DB Apr 26 02:26:33 192.168.122.209 [37344.080997] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:26:35 192.168.122.209 [37345.530478] [tempesta fw] Configuration processing is completed. Apr 26 02:26:35 192.168.122.209 [37345.580869] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:26:35 192.168.122.209 [37345.997852] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:26:35 192.168.122.209 [37346.024120] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:26:35 192.168.122.209 [37346.049904] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:26:35 192.168.122.209 [37346.098410] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:26:35 192.168.122.209 [37346.142453] [tempesta fw] Tempesta FW is ready Apr 26 02:26:36 192.168.122.209 [37346.773366] [tdb] Close table 'client0.tdb' Apr 26 02:26:36 192.168.122.209 [37346.970225] [tdb] Close table 'sessions0.tdb' Apr 26 02:26:39 192.168.122.209 [37350.217727] [tdb] Close table 'cache0.tdb' Apr 26 02:26:40 192.168.122.209 [37350.474164] [tdb] Close table 'filter0.tdb' Apr 26 02:26:40 192.168.122.209 [37350.474628] [tempesta fw] modules are stopped Apr 26 02:26:40 192.168.122.209 [37350.664730] [tempesta fw] exiting... Apr 26 02:26:40 192.168.122.209 [37350.827379] [tdb] Shutdown Tempesta DB Apr 26 02:26:40 192.168.122.209 [37351.048425] End test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsPublicCache.test Apr 26 02:26:40 192.168.122.209 [37351.065467] Start test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsSMaxAgeCache.test Apr 26 02:26:41 192.168.122.209 [37352.240737] [tdb] Start Tempesta DB Apr 26 02:26:42 192.168.122.209 [37352.395427] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:26:43 192.168.122.209 [37353.910645] [tempesta fw] Configuration processing is completed. Apr 26 02:26:43 192.168.122.209 [37353.964354] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:26:44 192.168.122.209 [37354.393622] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:26:44 192.168.122.209 [37354.424740] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:26:44 192.168.122.209 [37354.450271] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:26:44 192.168.122.209 [37354.502613] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:26:44 192.168.122.209 [37354.558559] [tempesta fw] Tempesta FW is ready Apr 26 02:26:44 192.168.122.209 [37355.159537] [tdb] Close table 'client0.tdb' Apr 26 02:26:45 192.168.122.209 [37355.354156] [tdb] Close table 'sessions0.tdb' Apr 26 02:26:48 192.168.122.209 [37358.579967] [tdb] Close table 'cache0.tdb' Apr 26 02:26:48 192.168.122.209 [37358.834900] [tdb] Close table 'filter0.tdb' Apr 26 02:26:48 192.168.122.209 [37358.835334] [tempesta fw] modules are stopped Apr 26 02:26:48 192.168.122.209 [37359.023784] [tempesta fw] exiting... Apr 26 02:26:48 192.168.122.209 [37359.181364] [tdb] Shutdown Tempesta DB Apr 26 02:26:49 192.168.122.209 [37359.417073] End test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsSMaxAgeCache.test Apr 26 02:26:49 192.168.122.209 [37359.439357] Start test: cache.test_cache_control.StoringResponsesWithSetCookieHeaderDefaultCache.test Apr 26 02:26:50 192.168.122.209 [37360.705711] [tdb] Start Tempesta DB Apr 26 02:26:50 192.168.122.209 [37360.862951] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:26:52 192.168.122.209 [37362.394929] [tempesta fw] Configuration processing is completed. Apr 26 02:26:52 192.168.122.209 [37362.449368] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:26:52 192.168.122.209 [37362.894775] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:26:52 192.168.122.209 [37362.920964] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:26:52 192.168.122.209 [37362.947485] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:26:52 192.168.122.209 [37363.006707] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:26:52 192.168.122.209 [37363.058655] [tempesta fw] Tempesta FW is ready Apr 26 02:26:53 192.168.122.209 [37363.677993] [tdb] Close table 'client0.tdb' Apr 26 02:26:53 192.168.122.209 [37363.874381] [tdb] Close table 'sessions0.tdb' Apr 26 02:26:56 192.168.122.209 [37367.039652] [tdb] Close table 'cache0.tdb' Apr 26 02:26:56 192.168.122.209 [37367.270858] [tdb] Close table 'filter0.tdb' Apr 26 02:26:56 192.168.122.209 [37367.271316] [tempesta fw] modules are stopped Apr 26 02:26:57 192.168.122.209 [37367.464031] [tempesta fw] exiting... Apr 26 02:26:57 192.168.122.209 [37367.605419] [tdb] Shutdown Tempesta DB Apr 26 02:26:57 192.168.122.209 [37367.832559] End test: cache.test_cache_control.StoringResponsesWithSetCookieHeaderDefaultCache.test Apr 26 02:26:57 192.168.122.209 [37367.844809] Start test: cache.test_cache_control.TestCache.test Apr 26 02:26:58 192.168.122.209 [37368.997277] [tdb] Start Tempesta DB Apr 26 02:26:58 192.168.122.209 [37369.141138] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:27:00 192.168.122.209 [37370.730849] [tempesta fw] Configuration processing is completed. Apr 26 02:27:00 192.168.122.209 [37370.779664] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:27:00 192.168.122.209 [37371.202121] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:27:00 192.168.122.209 [37371.229186] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:27:00 192.168.122.209 [37371.256066] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:27:01 192.168.122.209 [37371.302821] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:27:01 192.168.122.209 [37371.342768] [tempesta fw] Tempesta FW is ready Apr 26 02:27:01 192.168.122.209 [37371.941713] [tdb] Close table 'client0.tdb' Apr 26 02:27:01 192.168.122.209 [37372.169787] [tdb] Close table 'sessions0.tdb' Apr 26 02:27:05 192.168.122.209 [37375.351473] [tdb] Close table 'cache0.tdb' Apr 26 02:27:05 192.168.122.209 [37375.610216] [tdb] Close table 'filter0.tdb' Apr 26 02:27:05 192.168.122.209 [37375.610792] [tempesta fw] modules are stopped Apr 26 02:27:05 192.168.122.209 [37375.783629] [tempesta fw] exiting... Apr 26 02:27:05 192.168.122.209 [37375.955526] [tdb] Shutdown Tempesta DB Apr 26 02:27:05 192.168.122.209 [37376.186501] End test: cache.test_cache_control.TestCache.test Apr 26 02:27:05 192.168.122.209 [37376.203238] Start test: cache.test_cache_control.TestCache2.test Apr 26 02:27:07 192.168.122.209 [37377.420088] [tdb] Start Tempesta DB Apr 26 02:27:07 192.168.122.209 [37377.590195] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:27:08 192.168.122.209 [37379.090963] [tempesta fw] Configuration processing is completed. Apr 26 02:27:08 192.168.122.209 [37379.150355] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:27:09 192.168.122.209 [37379.568178] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:27:09 192.168.122.209 [37379.608214] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:27:09 192.168.122.209 [37379.637466] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:27:09 192.168.122.209 [37379.690934] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:27:09 192.168.122.209 [37379.734889] [tempesta fw] Tempesta FW is ready Apr 26 02:27:10 192.168.122.209 [37380.306349] [tdb] Close table 'client0.tdb' Apr 26 02:27:10 192.168.122.209 [37380.501197] [tdb] Close table 'sessions0.tdb' Apr 26 02:27:13 192.168.122.209 [37383.699387] [tdb] Close table 'cache0.tdb' Apr 26 02:27:13 192.168.122.209 [37383.921268] [tdb] Close table 'filter0.tdb' Apr 26 02:27:13 192.168.122.209 [37383.921720] [tempesta fw] modules are stopped Apr 26 02:27:13 192.168.122.209 [37384.100139] [tempesta fw] exiting... Apr 26 02:27:13 192.168.122.209 [37384.257551] [tdb] Shutdown Tempesta DB Apr 26 02:27:14 192.168.122.209 [37384.501313] End test: cache.test_cache_control.TestCache2.test Apr 26 02:27:14 192.168.122.209 [37384.523726] Start test: cache.test_cache_control.TestCacheBypass.test Apr 26 02:27:15 192.168.122.209 [37385.725617] [tdb] Start Tempesta DB Apr 26 02:27:15 192.168.122.209 [37385.870634] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:27:17 192.168.122.209 [37387.367073] [tempesta fw] Configuration processing is completed. Apr 26 02:27:17 192.168.122.209 [37387.416559] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:27:17 192.168.122.209 [37387.841021] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:27:17 192.168.122.209 [37387.867578] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:27:17 192.168.122.209 [37387.894306] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:27:17 192.168.122.209 [37387.935033] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:27:17 192.168.122.209 [37387.974982] [tempesta fw] Tempesta FW is ready Apr 26 02:27:18 192.168.122.209 [37388.580846] [tdb] Close table 'client0.tdb' Apr 26 02:27:18 192.168.122.209 [37388.794046] [tdb] Close table 'sessions0.tdb' Apr 26 02:27:21 192.168.122.209 [37391.946469] [tdb] Close table 'cache0.tdb' Apr 26 02:27:21 192.168.122.209 [37392.165066] [tdb] Close table 'filter0.tdb' Apr 26 02:27:21 192.168.122.209 [37392.165497] [tempesta fw] modules are stopped Apr 26 02:27:22 192.168.122.209 [37392.360669] [tempesta fw] exiting... Apr 26 02:27:22 192.168.122.209 [37392.527967] [tdb] Shutdown Tempesta DB Apr 26 02:27:22 192.168.122.209 [37392.767234] End test: cache.test_cache_control.TestCacheBypass.test Apr 26 02:27:22 192.168.122.209 [37392.802723] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_no_cache_in_request_and_cache_lvl_1 Apr 26 02:27:23 192.168.122.209 [37393.912737] [tdb] Start Tempesta DB Apr 26 02:27:23 192.168.122.209 [37394.062102] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:27:25 192.168.122.209 [37395.404402] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37395.404402] Maybe that's fine, but it's worth checking the [37395.404402] config - if there is no relations between the [37395.404402] names, then host name confusion attack is possible. Apr 26 02:27:25 192.168.122.209 [37395.491146] [tempesta fw] Configuration processing is completed. Apr 26 02:27:25 192.168.122.209 [37395.543252] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:27:25 192.168.122.209 [37395.963731] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:27:25 192.168.122.209 [37395.990357] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:27:25 192.168.122.209 [37396.021768] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:27:25 192.168.122.209 [37396.087125] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:27:25 192.168.122.209 [37396.088880] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:27:25 192.168.122.209 [37396.127080] [tempesta fw] Tempesta FW is ready Apr 26 02:27:26 192.168.122.209 [37396.751746] [tdb] Close table 'client0.tdb' Apr 26 02:27:26 192.168.122.209 [37396.938516] [tdb] Close table 'sessions0.tdb' Apr 26 02:27:29 192.168.122.209 [37400.082260] [tdb] Close table 'cache0.tdb' Apr 26 02:27:30 192.168.122.209 [37400.301061] [tdb] Close table 'filter0.tdb' Apr 26 02:27:30 192.168.122.209 [37400.301513] [tempesta fw] modules are stopped Apr 26 02:27:30 192.168.122.209 [37400.535231] [tempesta fw] exiting... Apr 26 02:27:30 192.168.122.209 [37400.688200] [tdb] Shutdown Tempesta DB Apr 26 02:27:30 192.168.122.209 [37400.906244] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_no_cache_in_request_and_cache_lvl_1 Apr 26 02:27:30 192.168.122.209 [37400.920675] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_no_cache_in_request_and_cache_lvl_2 Apr 26 02:27:31 192.168.122.209 [37402.095187] [tdb] Start Tempesta DB Apr 26 02:27:31 192.168.122.209 [37402.261015] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:27:33 192.168.122.209 [37403.672466] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37403.672466] Maybe that's fine, but it's worth checking the [37403.672466] config - if there is no relations between the [37403.672466] names, then host name confusion attack is possible. Apr 26 02:27:33 192.168.122.209 [37403.763270] [tempesta fw] Configuration processing is completed. Apr 26 02:27:33 192.168.122.209 [37403.818127] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:27:33 192.168.122.209 [37404.242854] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:27:33 192.168.122.209 [37404.269536] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:27:34 192.168.122.209 [37404.296236] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:27:34 192.168.122.209 [37404.355232] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:27:34 192.168.122.209 [37404.356995] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:27:34 192.168.122.209 [37404.399180] [tempesta fw] Tempesta FW is ready Apr 26 02:27:34 192.168.122.209 [37405.040396] [tdb] Close table 'client0.tdb' Apr 26 02:27:34 192.168.122.209 [37405.264986] [tdb] Close table 'sessions0.tdb' Apr 26 02:27:38 192.168.122.209 [37408.439346] [tdb] Close table 'cache0.tdb' Apr 26 02:27:38 192.168.122.209 [37408.687502] [tdb] Close table 'filter0.tdb' Apr 26 02:27:38 192.168.122.209 [37408.687931] [tempesta fw] modules are stopped Apr 26 02:27:38 192.168.122.209 [37408.914812] [tempesta fw] exiting... Apr 26 02:27:38 192.168.122.209 [37409.107355] [tdb] Shutdown Tempesta DB Apr 26 02:27:39 192.168.122.209 [37409.332879] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_no_cache_in_request_and_cache_lvl_2 Apr 26 02:27:39 192.168.122.209 [37409.353102] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_no_cache_in_response_and_cache_lvl_1 Apr 26 02:27:40 192.168.122.209 [37410.529278] [tdb] Start Tempesta DB Apr 26 02:27:40 192.168.122.209 [37410.670909] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:27:41 192.168.122.209 [37412.044577] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37412.044577] Maybe that's fine, but it's worth checking the [37412.044577] config - if there is no relations between the [37412.044577] names, then host name confusion attack is possible. Apr 26 02:27:41 192.168.122.209 [37412.136089] [tempesta fw] Configuration processing is completed. Apr 26 02:27:41 192.168.122.209 [37412.198529] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:27:42 192.168.122.209 [37412.619811] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:27:42 192.168.122.209 [37412.646147] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:27:42 192.168.122.209 [37412.672032] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:27:42 192.168.122.209 [37412.727333] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:27:42 192.168.122.209 [37412.729077] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:27:42 192.168.122.209 [37412.767284] [tempesta fw] Tempesta FW is ready Apr 26 02:27:43 192.168.122.209 [37413.406079] [tdb] Close table 'client0.tdb' Apr 26 02:27:43 192.168.122.209 [37413.599725] [tdb] Close table 'sessions0.tdb' Apr 26 02:27:46 192.168.122.209 [37416.789559] [tdb] Close table 'cache0.tdb' Apr 26 02:27:46 192.168.122.209 [37416.999039] [tdb] Close table 'filter0.tdb' Apr 26 02:27:46 192.168.122.209 [37416.999502] [tempesta fw] modules are stopped Apr 26 02:27:46 192.168.122.209 [37417.211540] [tempesta fw] exiting... Apr 26 02:27:47 192.168.122.209 [37417.354871] [tdb] Shutdown Tempesta DB Apr 26 02:27:47 192.168.122.209 [37417.584910] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_no_cache_in_response_and_cache_lvl_1 Apr 26 02:27:47 192.168.122.209 [37417.615655] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_no_cache_in_response_and_cache_lvl_2 Apr 26 02:27:48 192.168.122.209 [37418.811336] [tdb] Start Tempesta DB Apr 26 02:27:48 192.168.122.209 [37418.967797] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:27:50 192.168.122.209 [37420.380726] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37420.380726] Maybe that's fine, but it's worth checking the [37420.380726] config - if there is no relations between the [37420.380726] names, then host name confusion attack is possible. Apr 26 02:27:50 192.168.122.209 [37420.467768] [tempesta fw] Configuration processing is completed. Apr 26 02:27:50 192.168.122.209 [37420.549781] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:27:50 192.168.122.209 [37421.002804] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:27:50 192.168.122.209 [37421.030876] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:27:50 192.168.122.209 [37421.059127] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:27:50 192.168.122.209 [37421.099452] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:27:50 192.168.122.209 [37421.101176] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:27:50 192.168.122.209 [37421.151382] [tempesta fw] Tempesta FW is ready Apr 26 02:27:51 192.168.122.209 [37421.756614] [tdb] Close table 'client0.tdb' Apr 26 02:27:51 192.168.122.209 [37421.938698] [tdb] Close table 'sessions0.tdb' Apr 26 02:27:54 192.168.122.209 [37425.146246] [tdb] Close table 'cache0.tdb' Apr 26 02:27:55 192.168.122.209 [37425.379047] [tdb] Close table 'filter0.tdb' Apr 26 02:27:55 192.168.122.209 [37425.379515] [tempesta fw] modules are stopped Apr 26 02:27:55 192.168.122.209 [37425.579675] [tempesta fw] exiting... Apr 26 02:27:55 192.168.122.209 [37425.737323] [tdb] Shutdown Tempesta DB Apr 26 02:27:55 192.168.122.209 [37425.941239] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_no_cache_in_response_and_cache_lvl_2 Apr 26 02:27:55 192.168.122.209 [37425.956150] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_no_store_in_request_and_cache_lvl_1 Apr 26 02:27:56 192.168.122.209 [37427.118427] [tdb] Start Tempesta DB Apr 26 02:27:57 192.168.122.209 [37427.284687] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:27:58 192.168.122.209 [37428.728828] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37428.728828] Maybe that's fine, but it's worth checking the [37428.728828] config - if there is no relations between the [37428.728828] names, then host name confusion attack is possible. Apr 26 02:27:58 192.168.122.209 [37428.819650] [tempesta fw] Configuration processing is completed. Apr 26 02:27:58 192.168.122.209 [37428.870483] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:27:59 192.168.122.209 [37429.308670] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:27:59 192.168.122.209 [37429.336080] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:27:59 192.168.122.209 [37429.363734] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:27:59 192.168.122.209 [37429.415561] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:27:59 192.168.122.209 [37429.417301] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:27:59 192.168.122.209 [37429.459505] [tempesta fw] Tempesta FW is ready Apr 26 02:27:59 192.168.122.209 [37430.080348] [tdb] Close table 'client0.tdb' Apr 26 02:27:59 192.168.122.209 [37430.271596] [tdb] Close table 'sessions0.tdb' Apr 26 02:28:03 192.168.122.209 [37433.416812] [tdb] Close table 'cache0.tdb' Apr 26 02:28:03 192.168.122.209 [37433.668841] [tdb] Close table 'filter0.tdb' Apr 26 02:28:03 192.168.122.209 [37433.669273] [tempesta fw] modules are stopped Apr 26 02:28:03 192.168.122.209 [37433.869413] [tempesta fw] exiting... Apr 26 02:28:03 192.168.122.209 [37434.010019] [tdb] Shutdown Tempesta DB Apr 26 02:28:03 192.168.122.209 [37434.257210] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_no_store_in_request_and_cache_lvl_1 Apr 26 02:28:04 192.168.122.209 [37434.280009] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_no_store_in_request_and_cache_lvl_2 Apr 26 02:28:05 192.168.122.209 [37435.474559] [tdb] Start Tempesta DB Apr 26 02:28:05 192.168.122.209 [37435.637459] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:28:06 192.168.122.209 [37437.048892] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37437.048892] Maybe that's fine, but it's worth checking the [37437.048892] config - if there is no relations between the [37437.048892] names, then host name confusion attack is possible. Apr 26 02:28:06 192.168.122.209 [37437.135679] [tempesta fw] Configuration processing is completed. Apr 26 02:28:06 192.168.122.209 [37437.188459] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:28:07 192.168.122.209 [37437.615937] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:28:07 192.168.122.209 [37437.652895] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:28:07 192.168.122.209 [37437.679184] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:28:07 192.168.122.209 [37437.719654] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:28:07 192.168.122.209 [37437.721402] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:28:07 192.168.122.209 [37437.759595] [tempesta fw] Tempesta FW is ready Apr 26 02:28:08 192.168.122.209 [37438.347960] [tdb] Close table 'client0.tdb' Apr 26 02:28:08 192.168.122.209 [37438.557107] [tdb] Close table 'sessions0.tdb' Apr 26 02:28:11 192.168.122.209 [37441.732803] [tdb] Close table 'cache0.tdb' Apr 26 02:28:11 192.168.122.209 [37441.973910] [tdb] Close table 'filter0.tdb' Apr 26 02:28:11 192.168.122.209 [37441.974349] [tempesta fw] modules are stopped Apr 26 02:28:11 192.168.122.209 [37442.193352] [tempesta fw] exiting... Apr 26 02:28:12 192.168.122.209 [37442.375638] [tdb] Shutdown Tempesta DB Apr 26 02:28:12 192.168.122.209 [37442.609877] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_no_store_in_request_and_cache_lvl_2 Apr 26 02:28:12 192.168.122.209 [37442.625867] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_no_store_in_response_and_cache_lvl_1 Apr 26 02:28:13 192.168.122.209 [37443.838688] [tdb] Start Tempesta DB Apr 26 02:28:13 192.168.122.209 [37443.995808] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:28:15 192.168.122.209 [37445.385101] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37445.385101] Maybe that's fine, but it's worth checking the [37445.385101] config - if there is no relations between the [37445.385101] names, then host name confusion attack is possible. Apr 26 02:28:15 192.168.122.209 [37445.475795] [tempesta fw] Configuration processing is completed. Apr 26 02:28:15 192.168.122.209 [37445.526374] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:28:15 192.168.122.209 [37445.965803] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:28:15 192.168.122.209 [37445.993444] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:28:15 192.168.122.209 [37446.021176] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:28:15 192.168.122.209 [37446.083754] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:28:15 192.168.122.209 [37446.085488] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:28:15 192.168.122.209 [37446.123727] [tempesta fw] Tempesta FW is ready Apr 26 02:28:16 192.168.122.209 [37446.713297] [tdb] Close table 'client0.tdb' Apr 26 02:28:16 192.168.122.209 [37446.930371] [tdb] Close table 'sessions0.tdb' Apr 26 02:28:19 192.168.122.209 [37450.105819] [tdb] Close table 'cache0.tdb' Apr 26 02:28:20 192.168.122.209 [37450.350775] [tdb] Close table 'filter0.tdb' Apr 26 02:28:20 192.168.122.209 [37450.351218] [tempesta fw] modules are stopped Apr 26 02:28:20 192.168.122.209 [37450.545525] [tempesta fw] exiting... Apr 26 02:28:20 192.168.122.209 [37450.670209] [tdb] Shutdown Tempesta DB Apr 26 02:28:20 192.168.122.209 [37450.873132] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_no_store_in_response_and_cache_lvl_1 Apr 26 02:28:20 192.168.122.209 [37450.887915] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_no_store_in_response_and_cache_lvl_2 Apr 26 02:28:21 192.168.122.209 [37452.076618] [tdb] Start Tempesta DB Apr 26 02:28:21 192.168.122.209 [37452.230202] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:28:23 192.168.122.209 [37453.613117] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37453.613117] Maybe that's fine, but it's worth checking the [37453.613117] config - if there is no relations between the [37453.613117] names, then host name confusion attack is possible. Apr 26 02:28:23 192.168.122.209 [37453.699889] [tempesta fw] Configuration processing is completed. Apr 26 02:28:23 192.168.122.209 [37453.750889] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:28:23 192.168.122.209 [37454.170114] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:28:23 192.168.122.209 [37454.198101] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:28:23 192.168.122.209 [37454.224743] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:28:24 192.168.122.209 [37454.279956] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:28:24 192.168.122.209 [37454.281678] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:28:24 192.168.122.209 [37454.339812] [tempesta fw] Tempesta FW is ready Apr 26 02:28:24 192.168.122.209 [37455.023678] [tdb] Close table 'client0.tdb' Apr 26 02:28:24 192.168.122.209 [37455.237887] [tdb] Close table 'sessions0.tdb' Apr 26 02:28:28 192.168.122.209 [37458.477100] [tdb] Close table 'cache0.tdb' Apr 26 02:28:28 192.168.122.209 [37458.691440] [tdb] Close table 'filter0.tdb' Apr 26 02:28:28 192.168.122.209 [37458.691882] [tempesta fw] modules are stopped Apr 26 02:28:28 192.168.122.209 [37458.881050] [tempesta fw] exiting... Apr 26 02:28:28 192.168.122.209 [37459.041503] [tdb] Shutdown Tempesta DB Apr 26 02:28:28 192.168.122.209 [37459.270953] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_no_store_in_response_and_cache_lvl_2 Apr 26 02:28:29 192.168.122.209 [37459.291225] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_private_in_response_and_cache_lvl_1 Apr 26 02:28:30 192.168.122.209 [37460.489690] [tdb] Start Tempesta DB Apr 26 02:28:30 192.168.122.209 [37460.644556] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:28:31 192.168.122.209 [37462.057210] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37462.057210] Maybe that's fine, but it's worth checking the [37462.057210] config - if there is no relations between the [37462.057210] names, then host name confusion attack is possible. Apr 26 02:28:31 192.168.122.209 [37462.140006] [tempesta fw] Configuration processing is completed. Apr 26 02:28:31 192.168.122.209 [37462.191110] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:28:32 192.168.122.209 [37462.623996] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:28:32 192.168.122.209 [37462.662599] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:28:32 192.168.122.209 [37462.689317] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:28:32 192.168.122.209 [37462.735984] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:28:32 192.168.122.209 [37462.737738] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:28:32 192.168.122.209 [37462.795965] [tempesta fw] Tempesta FW is ready Apr 26 02:28:33 192.168.122.209 [37463.408323] [tdb] Close table 'client0.tdb' Apr 26 02:28:33 192.168.122.209 [37463.635805] [tdb] Close table 'sessions0.tdb' Apr 26 02:28:36 192.168.122.209 [37466.876102] [tdb] Close table 'cache0.tdb' Apr 26 02:28:36 192.168.122.209 [37467.122859] [tdb] Close table 'filter0.tdb' Apr 26 02:28:36 192.168.122.209 [37467.123257] [tempesta fw] modules are stopped Apr 26 02:28:37 192.168.122.209 [37467.333008] [tempesta fw] exiting... Apr 26 02:28:37 192.168.122.209 [37467.468055] [tdb] Shutdown Tempesta DB Apr 26 02:28:37 192.168.122.209 [37467.679808] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_private_in_response_and_cache_lvl_1 Apr 26 02:28:37 192.168.122.209 [37467.714876] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_private_in_response_and_cache_lvl_2 Apr 26 02:28:38 192.168.122.209 [37468.915001] [tdb] Start Tempesta DB Apr 26 02:28:38 192.168.122.209 [37469.072082] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:28:40 192.168.122.209 [37470.477327] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37470.477327] Maybe that's fine, but it's worth checking the [37470.477327] config - if there is no relations between the [37470.477327] names, then host name confusion attack is possible. Apr 26 02:28:40 192.168.122.209 [37470.568463] [tempesta fw] Configuration processing is completed. Apr 26 02:28:40 192.168.122.209 [37470.618010] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:28:40 192.168.122.209 [37471.042390] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:28:40 192.168.122.209 [37471.069278] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:28:40 192.168.122.209 [37471.095751] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:28:40 192.168.122.209 [37471.136010] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:28:40 192.168.122.209 [37471.137009] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:28:40 192.168.122.209 [37471.184036] [tempesta fw] Tempesta FW is ready Apr 26 02:28:41 192.168.122.209 [37471.820192] [tdb] Close table 'client0.tdb' Apr 26 02:28:41 192.168.122.209 [37472.003017] [tdb] Close table 'sessions0.tdb' Apr 26 02:28:44 192.168.122.209 [37475.154354] [tdb] Close table 'cache0.tdb' Apr 26 02:28:45 192.168.122.209 [37475.415181] [tdb] Close table 'filter0.tdb' Apr 26 02:28:45 192.168.122.209 [37475.415619] [tempesta fw] modules are stopped Apr 26 02:28:45 192.168.122.209 [37475.616815] [tempesta fw] exiting... Apr 26 02:28:45 192.168.122.209 [37475.800119] [tdb] Shutdown Tempesta DB Apr 26 02:28:45 192.168.122.209 [37476.028699] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_private_in_response_and_cache_lvl_2 Apr 26 02:28:45 192.168.122.209 [37476.049762] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_pragma_no_cache_in_request_and_cache_lvl_1 Apr 26 02:28:46 192.168.122.209 [37477.207190] [tdb] Start Tempesta DB Apr 26 02:28:47 192.168.122.209 [37477.365711] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:28:48 192.168.122.209 [37478.713438] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37478.713438] Maybe that's fine, but it's worth checking the [37478.713438] config - if there is no relations between the [37478.713438] names, then host name confusion attack is possible. Apr 26 02:28:48 192.168.122.209 [37478.804225] [tempesta fw] Configuration processing is completed. Apr 26 02:28:48 192.168.122.209 [37478.902160] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:28:49 192.168.122.209 [37479.343055] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:28:49 192.168.122.209 [37479.369903] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:28:49 192.168.122.209 [37479.396908] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:28:49 192.168.122.209 [37479.468177] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:28:49 192.168.122.209 [37479.469906] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:28:49 192.168.122.209 [37479.520149] [tempesta fw] Tempesta FW is ready Apr 26 02:28:49 192.168.122.209 [37480.122978] [tdb] Close table 'client0.tdb' Apr 26 02:28:50 192.168.122.209 [37480.335098] [tdb] Close table 'sessions0.tdb' Apr 26 02:28:53 192.168.122.209 [37483.506581] [tdb] Close table 'cache0.tdb' Apr 26 02:28:53 192.168.122.209 [37483.734929] [tdb] Close table 'filter0.tdb' Apr 26 02:28:53 192.168.122.209 [37483.735360] [tempesta fw] modules are stopped Apr 26 02:28:53 192.168.122.209 [37483.926302] [tempesta fw] exiting... Apr 26 02:28:53 192.168.122.209 [37484.069778] [tdb] Shutdown Tempesta DB Apr 26 02:28:54 192.168.122.209 [37484.294658] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_pragma_no_cache_in_request_and_cache_lvl_1 Apr 26 02:28:54 192.168.122.209 [37484.314372] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_pragma_no_cache_in_request_and_cache_lvl_2 Apr 26 02:28:55 192.168.122.209 [37485.498881] [tdb] Start Tempesta DB Apr 26 02:28:55 192.168.122.209 [37485.650452] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:28:56 192.168.122.209 [37487.053598] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37487.053598] Maybe that's fine, but it's worth checking the [37487.053598] config - if there is no relations between the [37487.053598] names, then host name confusion attack is possible. Apr 26 02:28:56 192.168.122.209 [37487.140278] [tempesta fw] Configuration processing is completed. Apr 26 02:28:56 192.168.122.209 [37487.189863] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:28:57 192.168.122.209 [37487.616955] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:28:57 192.168.122.209 [37487.642674] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:28:57 192.168.122.209 [37487.668513] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:28:57 192.168.122.209 [37487.716237] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:28:57 192.168.122.209 [37487.717955] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:28:57 192.168.122.209 [37487.764230] [tempesta fw] Tempesta FW is ready Apr 26 02:28:58 192.168.122.209 [37488.397546] [tdb] Close table 'client0.tdb' Apr 26 02:28:58 192.168.122.209 [37488.604600] [tdb] Close table 'sessions0.tdb' Apr 26 02:29:01 192.168.122.209 [37491.806125] [tdb] Close table 'cache0.tdb' Apr 26 02:29:01 192.168.122.209 [37492.037260] [tdb] Close table 'filter0.tdb' Apr 26 02:29:01 192.168.122.209 [37492.037701] [tempesta fw] modules are stopped Apr 26 02:29:01 192.168.122.209 [37492.218066] [tempesta fw] exiting... Apr 26 02:29:02 192.168.122.209 [37492.353871] [tdb] Shutdown Tempesta DB Apr 26 02:29:02 192.168.122.209 [37492.565298] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_pragma_no_cache_in_request_and_cache_lvl_2 Apr 26 02:29:02 192.168.122.209 [37492.579823] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_pragma_no_cache_in_response_and_cache_lvl_1 Apr 26 02:29:03 192.168.122.209 [37493.776161] [tdb] Start Tempesta DB Apr 26 02:29:03 192.168.122.209 [37493.914448] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:29:05 192.168.122.209 [37495.321608] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37495.321608] Maybe that's fine, but it's worth checking the [37495.321608] config - if there is no relations between the [37495.321608] names, then host name confusion attack is possible. Apr 26 02:29:05 192.168.122.209 [37495.404430] [tempesta fw] Configuration processing is completed. Apr 26 02:29:05 192.168.122.209 [37495.486503] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:29:05 192.168.122.209 [37495.950045] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:29:05 192.168.122.209 [37495.981378] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:29:05 192.168.122.209 [37496.012564] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:29:05 192.168.122.209 [37496.088394] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:29:05 192.168.122.209 [37496.090135] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:29:05 192.168.122.209 [37496.128347] [tempesta fw] Tempesta FW is ready Apr 26 02:29:06 192.168.122.209 [37496.750092] [tdb] Close table 'client0.tdb' Apr 26 02:29:06 192.168.122.209 [37496.951166] [tdb] Close table 'sessions0.tdb' Apr 26 02:29:09 192.168.122.209 [37500.115182] [tdb] Close table 'cache0.tdb' Apr 26 02:29:10 192.168.122.209 [37500.344834] [tdb] Close table 'filter0.tdb' Apr 26 02:29:10 192.168.122.209 [37500.345272] [tempesta fw] modules are stopped Apr 26 02:29:10 192.168.122.209 [37500.535262] [tempesta fw] exiting... Apr 26 02:29:10 192.168.122.209 [37500.709720] [tdb] Shutdown Tempesta DB Apr 26 02:29:10 192.168.122.209 [37500.964594] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_pragma_no_cache_in_response_and_cache_lvl_1 Apr 26 02:29:10 192.168.122.209 [37500.987821] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_pragma_no_cache_in_response_and_cache_lvl_2 Apr 26 02:29:11 192.168.122.209 [37502.207291] [tdb] Start Tempesta DB Apr 26 02:29:12 192.168.122.209 [37502.364669] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:29:13 192.168.122.209 [37503.741788] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37503.741788] Maybe that's fine, but it's worth checking the [37503.741788] config - if there is no relations between the [37503.741788] names, then host name confusion attack is possible. Apr 26 02:29:13 192.168.122.209 [37503.828565] [tempesta fw] Configuration processing is completed. Apr 26 02:29:13 192.168.122.209 [37503.878804] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:29:14 192.168.122.209 [37504.307564] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:29:14 192.168.122.209 [37504.334268] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:29:14 192.168.122.209 [37504.360556] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:29:14 192.168.122.209 [37504.420492] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:29:14 192.168.122.209 [37504.422215] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:29:14 192.168.122.209 [37504.460460] [tempesta fw] Tempesta FW is ready Apr 26 02:29:14 192.168.122.209 [37505.037114] [tdb] Close table 'client0.tdb' Apr 26 02:29:14 192.168.122.209 [37505.261017] [tdb] Close table 'sessions0.tdb' Apr 26 02:29:18 192.168.122.209 [37508.544162] [tdb] Close table 'cache0.tdb' Apr 26 02:29:18 192.168.122.209 [37508.799488] [tdb] Close table 'filter0.tdb' Apr 26 02:29:18 192.168.122.209 [37508.799939] [tempesta fw] modules are stopped Apr 26 02:29:18 192.168.122.209 [37509.002929] [tempesta fw] exiting... Apr 26 02:29:18 192.168.122.209 [37509.145853] [tdb] Shutdown Tempesta DB Apr 26 02:29:19 192.168.122.209 [37509.373402] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_pragma_no_cache_in_response_and_cache_lvl_2 Apr 26 02:29:19 192.168.122.209 [37509.402938] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_no_cache_in_request_and_cache_lvl_1 Apr 26 02:29:20 192.168.122.209 [37510.618279] [tdb] Start Tempesta DB Apr 26 02:29:20 192.168.122.209 [37510.764047] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:29:21 192.168.122.209 [37512.141894] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37512.141894] Maybe that's fine, but it's worth checking the [37512.141894] config - if there is no relations between the [37512.141894] names, then host name confusion attack is possible. Apr 26 02:29:21 192.168.122.209 [37512.224635] [tempesta fw] Configuration processing is completed. Apr 26 02:29:21 192.168.122.209 [37512.273555] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:29:22 192.168.122.209 [37512.717920] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:29:22 192.168.122.209 [37512.745795] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:29:22 192.168.122.209 [37512.774560] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:29:22 192.168.122.209 [37512.852634] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:29:22 192.168.122.209 [37512.854410] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:29:22 192.168.122.209 [37512.900558] [tempesta fw] Tempesta FW is ready Apr 26 02:29:23 192.168.122.209 [37513.509951] [tdb] Close table 'client0.tdb' Apr 26 02:29:23 192.168.122.209 [37513.706803] [tdb] Close table 'sessions0.tdb' Apr 26 02:29:26 192.168.122.209 [37516.885297] [tdb] Close table 'cache0.tdb' Apr 26 02:29:26 192.168.122.209 [37517.134312] [tdb] Close table 'filter0.tdb' Apr 26 02:29:26 192.168.122.209 [37517.134734] [tempesta fw] modules are stopped Apr 26 02:29:27 192.168.122.209 [37517.329689] [tempesta fw] exiting... Apr 26 02:29:27 192.168.122.209 [37517.457544] [tdb] Shutdown Tempesta DB Apr 26 02:29:27 192.168.122.209 [37517.674328] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_no_cache_in_request_and_cache_lvl_1 Apr 26 02:29:27 192.168.122.209 [37517.689205] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_no_cache_in_request_and_cache_lvl_2 Apr 26 02:29:28 192.168.122.209 [37518.908414] [tdb] Start Tempesta DB Apr 26 02:29:28 192.168.122.209 [37519.057008] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:29:30 192.168.122.209 [37520.457940] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37520.457940] Maybe that's fine, but it's worth checking the [37520.457940] config - if there is no relations between the [37520.457940] names, then host name confusion attack is possible. Apr 26 02:29:30 192.168.122.209 [37520.540756] [tempesta fw] Configuration processing is completed. Apr 26 02:29:30 192.168.122.209 [37520.595130] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:29:30 192.168.122.209 [37521.017158] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:29:30 192.168.122.209 [37521.073510] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:29:30 192.168.122.209 [37521.099585] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:29:30 192.168.122.209 [37521.148728] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:29:30 192.168.122.209 [37521.150442] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:29:30 192.168.122.209 [37521.188672] [tempesta fw] Tempesta FW is ready Apr 26 02:29:31 192.168.122.209 [37521.791787] [tdb] Close table 'client0.tdb' Apr 26 02:29:31 192.168.122.209 [37522.016708] [tdb] Close table 'sessions0.tdb' Apr 26 02:29:34 192.168.122.209 [37525.162603] [tdb] Close table 'cache0.tdb' Apr 26 02:29:35 192.168.122.209 [37525.409055] [tdb] Close table 'filter0.tdb' Apr 26 02:29:35 192.168.122.209 [37525.409501] [tempesta fw] modules are stopped Apr 26 02:29:35 192.168.122.209 [37525.593662] [tempesta fw] exiting... Apr 26 02:29:35 192.168.122.209 [37525.779516] [tdb] Shutdown Tempesta DB Apr 26 02:29:35 192.168.122.209 [37526.000516] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_no_cache_in_request_and_cache_lvl_2 Apr 26 02:29:35 192.168.122.209 [37526.028308] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_no_cache_in_response_and_cache_lvl_1 Apr 26 02:29:36 192.168.122.209 [37527.207268] [tdb] Start Tempesta DB Apr 26 02:29:37 192.168.122.209 [37527.349729] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:29:38 192.168.122.209 [37528.750094] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37528.750094] Maybe that's fine, but it's worth checking the [37528.750094] config - if there is no relations between the [37528.750094] names, then host name confusion attack is possible. Apr 26 02:29:38 192.168.122.209 [37528.840855] [tempesta fw] Configuration processing is completed. Apr 26 02:29:38 192.168.122.209 [37528.895641] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:29:39 192.168.122.209 [37529.331494] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:29:39 192.168.122.209 [37529.372274] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:29:39 192.168.122.209 [37529.398790] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:29:39 192.168.122.209 [37529.440827] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:29:39 192.168.122.209 [37529.442549] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:29:39 192.168.122.209 [37529.488778] [tempesta fw] Tempesta FW is ready Apr 26 02:29:39 192.168.122.209 [37530.124177] [tdb] Close table 'client0.tdb' Apr 26 02:29:40 192.168.122.209 [37530.319773] [tdb] Close table 'sessions0.tdb' Apr 26 02:29:43 192.168.122.209 [37533.486414] [tdb] Close table 'cache0.tdb' Apr 26 02:29:43 192.168.122.209 [37533.721065] [tdb] Close table 'filter0.tdb' Apr 26 02:29:43 192.168.122.209 [37533.721506] [tempesta fw] modules are stopped Apr 26 02:29:43 192.168.122.209 [37533.925418] [tempesta fw] exiting... Apr 26 02:29:43 192.168.122.209 [37534.100722] [tdb] Shutdown Tempesta DB Apr 26 02:29:44 192.168.122.209 [37534.347870] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_no_cache_in_response_and_cache_lvl_1 Apr 26 02:29:44 192.168.122.209 [37534.359873] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_no_cache_in_response_and_cache_lvl_2 Apr 26 02:29:45 192.168.122.209 [37535.567622] [tdb] Start Tempesta DB Apr 26 02:29:45 192.168.122.209 [37535.715843] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:29:46 192.168.122.209 [37537.086175] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37537.086175] Maybe that's fine, but it's worth checking the [37537.086175] config - if there is no relations between the [37537.086175] names, then host name confusion attack is possible. Apr 26 02:29:46 192.168.122.209 [37537.176959] [tempesta fw] Configuration processing is completed. Apr 26 02:29:46 192.168.122.209 [37537.228245] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:29:47 192.168.122.209 [37537.648368] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:29:47 192.168.122.209 [37537.681910] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:29:47 192.168.122.209 [37537.707552] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:29:47 192.168.122.209 [37537.764916] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:29:47 192.168.122.209 [37537.766657] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:29:47 192.168.122.209 [37537.804857] [tempesta fw] Tempesta FW is ready Apr 26 02:29:48 192.168.122.209 [37538.424953] [tdb] Close table 'client0.tdb' Apr 26 02:29:48 192.168.122.209 [37538.607820] [tdb] Close table 'sessions0.tdb' Apr 26 02:29:51 192.168.122.209 [37541.735927] [tdb] Close table 'cache0.tdb' Apr 26 02:29:51 192.168.122.209 [37541.980040] [tdb] Close table 'filter0.tdb' Apr 26 02:29:51 192.168.122.209 [37541.980480] [tempesta fw] modules are stopped Apr 26 02:29:51 192.168.122.209 [37542.165122] [tempesta fw] exiting... Apr 26 02:29:52 192.168.122.209 [37542.325628] [tdb] Shutdown Tempesta DB Apr 26 02:29:52 192.168.122.209 [37542.558986] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_no_cache_in_response_and_cache_lvl_2 Apr 26 02:29:52 192.168.122.209 [37542.574555] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_no_store_in_request_and_cache_lvl_1 Apr 26 02:29:53 192.168.122.209 [37543.691960] [tdb] Start Tempesta DB Apr 26 02:29:53 192.168.122.209 [37543.830320] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:29:54 192.168.122.209 [37545.202325] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37545.202325] Maybe that's fine, but it's worth checking the [37545.202325] config - if there is no relations between the [37545.202325] names, then host name confusion attack is possible. Apr 26 02:29:55 192.168.122.209 [37545.297080] [tempesta fw] Configuration processing is completed. Apr 26 02:29:55 192.168.122.209 [37545.360688] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:29:55 192.168.122.209 [37545.806811] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:29:55 192.168.122.209 [37545.833409] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:29:55 192.168.122.209 [37545.860537] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:29:55 192.168.122.209 [37545.909025] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:29:55 192.168.122.209 [37545.910787] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:29:55 192.168.122.209 [37545.948989] [tempesta fw] Tempesta FW is ready Apr 26 02:29:56 192.168.122.209 [37546.575620] [tdb] Close table 'client0.tdb' Apr 26 02:29:56 192.168.122.209 [37546.788652] [tdb] Close table 'sessions0.tdb' Apr 26 02:29:59 192.168.122.209 [37549.947833] [tdb] Close table 'cache0.tdb' Apr 26 02:29:59 192.168.122.209 [37550.179743] [tdb] Close table 'filter0.tdb' Apr 26 02:29:59 192.168.122.209 [37550.180217] [tempesta fw] modules are stopped Apr 26 02:30:00 192.168.122.209 [37550.390313] [tempesta fw] exiting... Apr 26 02:30:00 192.168.122.209 [37550.551301] [tdb] Shutdown Tempesta DB Apr 26 02:30:00 192.168.122.209 [37550.838104] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_no_store_in_request_and_cache_lvl_1 Apr 26 02:30:00 192.168.122.209 [37550.849025] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_no_store_in_request_and_cache_lvl_2 Apr 26 02:30:01 192.168.122.209 [37551.997264] [tdb] Start Tempesta DB Apr 26 02:30:01 192.168.122.209 [37552.138285] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:30:03 192.168.122.209 [37553.514377] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37553.514377] Maybe that's fine, but it's worth checking the [37553.514377] config - if there is no relations between the [37553.514377] names, then host name confusion attack is possible. Apr 26 02:30:03 192.168.122.209 [37553.597202] [tempesta fw] Configuration processing is completed. Apr 26 02:30:03 192.168.122.209 [37553.646168] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:30:03 192.168.122.209 [37554.062935] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:30:03 192.168.122.209 [37554.119438] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:30:03 192.168.122.209 [37554.145726] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:30:03 192.168.122.209 [37554.209130] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:30:03 192.168.122.209 [37554.210880] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:30:03 192.168.122.209 [37554.253078] [tempesta fw] Tempesta FW is ready Apr 26 02:30:04 192.168.122.209 [37554.852556] [tdb] Close table 'client0.tdb' Apr 26 02:30:04 192.168.122.209 [37555.051412] [tdb] Close table 'sessions0.tdb' Apr 26 02:30:07 192.168.122.209 [37558.241212] [tdb] Close table 'cache0.tdb' Apr 26 02:30:08 192.168.122.209 [37558.475061] [tdb] Close table 'filter0.tdb' Apr 26 02:30:08 192.168.122.209 [37558.475494] [tempesta fw] modules are stopped Apr 26 02:30:08 192.168.122.209 [37558.677582] [tempesta fw] exiting... Apr 26 02:30:08 192.168.122.209 [37558.839585] [tdb] Shutdown Tempesta DB Apr 26 02:30:08 192.168.122.209 [37559.047858] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_no_store_in_request_and_cache_lvl_2 Apr 26 02:30:08 192.168.122.209 [37559.067495] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_no_store_in_response_and_cache_lvl_1 Apr 26 02:30:10 192.168.122.209 [37560.300653] [tdb] Start Tempesta DB Apr 26 02:30:10 192.168.122.209 [37560.440946] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:30:11 192.168.122.209 [37561.818481] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37561.818481] Maybe that's fine, but it's worth checking the [37561.818481] config - if there is no relations between the [37561.818481] names, then host name confusion attack is possible. Apr 26 02:30:11 192.168.122.209 [37561.913287] [tempesta fw] Configuration processing is completed. Apr 26 02:30:11 192.168.122.209 [37561.971680] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:30:12 192.168.122.209 [37562.407196] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:30:12 192.168.122.209 [37562.434469] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:30:12 192.168.122.209 [37562.471208] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:30:12 192.168.122.209 [37562.529238] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:30:12 192.168.122.209 [37562.531007] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:30:12 192.168.122.209 [37562.573200] [tempesta fw] Tempesta FW is ready Apr 26 02:30:12 192.168.122.209 [37563.205822] [tdb] Close table 'client0.tdb' Apr 26 02:30:13 192.168.122.209 [37563.426243] [tdb] Close table 'sessions0.tdb' Apr 26 02:30:16 192.168.122.209 [37566.576925] [tdb] Close table 'cache0.tdb' Apr 26 02:30:16 192.168.122.209 [37566.818409] [tdb] Close table 'filter0.tdb' Apr 26 02:30:16 192.168.122.209 [37566.818848] [tempesta fw] modules are stopped Apr 26 02:30:16 192.168.122.209 [37566.989377] [tempesta fw] exiting... Apr 26 02:30:16 192.168.122.209 [37567.152756] [tdb] Shutdown Tempesta DB Apr 26 02:30:17 192.168.122.209 [37567.448678] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_no_store_in_response_and_cache_lvl_1 Apr 26 02:30:17 192.168.122.209 [37567.464141] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_no_store_in_response_and_cache_lvl_2 Apr 26 02:30:18 192.168.122.209 [37568.637939] [tdb] Start Tempesta DB Apr 26 02:30:18 192.168.122.209 [37568.804579] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:30:19 192.168.122.209 [37570.142597] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37570.142597] Maybe that's fine, but it's worth checking the [37570.142597] config - if there is no relations between the [37570.142597] names, then host name confusion attack is possible. Apr 26 02:30:19 192.168.122.209 [37570.233386] [tempesta fw] Configuration processing is completed. Apr 26 02:30:20 192.168.122.209 [37570.300346] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:30:20 192.168.122.209 [37570.723845] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:30:20 192.168.122.209 [37570.780438] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:30:20 192.168.122.209 [37570.806582] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:30:20 192.168.122.209 [37570.881341] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:30:20 192.168.122.209 [37570.883091] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:30:20 192.168.122.209 [37570.929292] [tempesta fw] Tempesta FW is ready Apr 26 02:30:21 192.168.122.209 [37571.523548] [tdb] Close table 'client0.tdb' Apr 26 02:30:21 192.168.122.209 [37571.717744] [tdb] Close table 'sessions0.tdb' Apr 26 02:30:24 192.168.122.209 [37574.879004] [tdb] Close table 'cache0.tdb' Apr 26 02:30:24 192.168.122.209 [37575.108808] [tdb] Close table 'filter0.tdb' Apr 26 02:30:24 192.168.122.209 [37575.109532] [tempesta fw] modules are stopped Apr 26 02:30:25 192.168.122.209 [37575.310483] [tempesta fw] exiting... Apr 26 02:30:25 192.168.122.209 [37575.467162] [tdb] Shutdown Tempesta DB Apr 26 02:30:25 192.168.122.209 [37575.724563] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_no_store_in_response_and_cache_lvl_2 Apr 26 02:30:25 192.168.122.209 [37575.750354] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_private_in_response_and_cache_lvl_1 Apr 26 02:30:26 192.168.122.209 [37576.884919] [tdb] Start Tempesta DB Apr 26 02:30:26 192.168.122.209 [37577.037809] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:30:28 192.168.122.209 [37578.454709] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37578.454709] Maybe that's fine, but it's worth checking the [37578.454709] config - if there is no relations between the [37578.454709] names, then host name confusion attack is possible. Apr 26 02:30:28 192.168.122.209 [37578.541480] [tempesta fw] Configuration processing is completed. Apr 26 02:30:28 192.168.122.209 [37578.592168] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:30:28 192.168.122.209 [37579.020846] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:30:28 192.168.122.209 [37579.047726] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:30:28 192.168.122.209 [37579.074796] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:30:28 192.168.122.209 [37579.121456] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:30:28 192.168.122.209 [37579.123194] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:30:28 192.168.122.209 [37579.161405] [tempesta fw] Tempesta FW is ready Apr 26 02:30:29 192.168.122.209 [37579.800945] [tdb] Close table 'client0.tdb' Apr 26 02:30:29 192.168.122.209 [37580.019947] [tdb] Close table 'sessions0.tdb' Apr 26 02:30:32 192.168.122.209 [37583.224083] [tdb] Close table 'cache0.tdb' Apr 26 02:30:33 192.168.122.209 [37583.449909] [tdb] Close table 'filter0.tdb' Apr 26 02:30:33 192.168.122.209 [37583.450344] [tempesta fw] modules are stopped Apr 26 02:30:33 192.168.122.209 [37583.697742] [tempesta fw] exiting... Apr 26 02:30:33 192.168.122.209 [37583.860758] [tdb] Shutdown Tempesta DB Apr 26 02:30:33 192.168.122.209 [37584.132388] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_private_in_response_and_cache_lvl_1 Apr 26 02:30:33 192.168.122.209 [37584.151027] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_private_in_response_and_cache_lvl_2 Apr 26 02:30:35 192.168.122.209 [37585.375309] [tdb] Start Tempesta DB Apr 26 02:30:35 192.168.122.209 [37585.522313] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:30:36 192.168.122.209 [37586.898821] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37586.898821] Maybe that's fine, but it's worth checking the [37586.898821] config - if there is no relations between the [37586.898821] names, then host name confusion attack is possible. Apr 26 02:30:36 192.168.122.209 [37586.993621] [tempesta fw] Configuration processing is completed. Apr 26 02:30:36 192.168.122.209 [37587.047977] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:30:37 192.168.122.209 [37587.474139] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:30:37 192.168.122.209 [37587.537284] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:30:37 192.168.122.209 [37587.563852] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:30:37 192.168.122.209 [37587.625556] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:30:37 192.168.122.209 [37587.627287] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:30:37 192.168.122.209 [37587.673503] [tempesta fw] Tempesta FW is ready Apr 26 02:30:38 192.168.122.209 [37588.293961] [tdb] Close table 'client0.tdb' Apr 26 02:30:38 192.168.122.209 [37588.502916] [tdb] Close table 'sessions0.tdb' Apr 26 02:30:41 192.168.122.209 [37591.720652] [tdb] Close table 'cache0.tdb' Apr 26 02:30:41 192.168.122.209 [37591.970561] [tdb] Close table 'filter0.tdb' Apr 26 02:30:41 192.168.122.209 [37591.970999] [tempesta fw] modules are stopped Apr 26 02:30:41 192.168.122.209 [37592.195199] [tempesta fw] exiting... Apr 26 02:30:42 192.168.122.209 [37592.368174] [tdb] Shutdown Tempesta DB Apr 26 02:30:42 192.168.122.209 [37592.584788] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_private_in_response_and_cache_lvl_2 Apr 26 02:30:42 192.168.122.209 [37592.607004] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_pragma_no_cache_in_request_and_cache_lvl_1 Apr 26 02:30:43 192.168.122.209 [37593.812280] [tdb] Start Tempesta DB Apr 26 02:30:43 192.168.122.209 [37593.960167] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:30:45 192.168.122.209 [37595.364086] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37595.364086] Maybe that's fine, but it's worth checking the [37595.364086] config - if there is no relations between the [37595.364086] names, then host name confusion attack is possible. Apr 26 02:30:45 192.168.122.209 [37595.449689] [tempesta fw] Configuration processing is completed. Apr 26 02:30:45 192.168.122.209 [37595.505822] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:30:45 192.168.122.209 [37595.961817] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:30:45 192.168.122.209 [37595.988493] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:30:45 192.168.122.209 [37596.015713] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:30:45 192.168.122.209 [37596.065683] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:30:45 192.168.122.209 [37596.067438] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:30:45 192.168.122.209 [37596.109608] [tempesta fw] Tempesta FW is ready Apr 26 02:30:46 192.168.122.209 [37596.701532] [tdb] Close table 'client0.tdb' Apr 26 02:30:46 192.168.122.209 [37596.898975] [tdb] Close table 'sessions0.tdb' Apr 26 02:30:49 192.168.122.209 [37600.062061] [tdb] Close table 'cache0.tdb' Apr 26 02:30:50 192.168.122.209 [37600.303555] [tdb] Close table 'filter0.tdb' Apr 26 02:30:50 192.168.122.209 [37600.303996] [tempesta fw] modules are stopped Apr 26 02:30:50 192.168.122.209 [37600.486477] [tempesta fw] exiting... Apr 26 02:30:50 192.168.122.209 [37600.640595] [tdb] Shutdown Tempesta DB Apr 26 02:30:50 192.168.122.209 [37600.861066] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_pragma_no_cache_in_request_and_cache_lvl_1 Apr 26 02:30:50 192.168.122.209 [37600.874604] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_pragma_no_cache_in_request_and_cache_lvl_2 Apr 26 02:30:51 192.168.122.209 [37602.077970] [tdb] Start Tempesta DB Apr 26 02:30:51 192.168.122.209 [37602.202803] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:30:53 192.168.122.209 [37603.559019] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37603.559019] Maybe that's fine, but it's worth checking the [37603.559019] config - if there is no relations between the [37603.559019] names, then host name confusion attack is possible. Apr 26 02:30:53 192.168.122.209 [37603.641805] [tempesta fw] Configuration processing is completed. Apr 26 02:30:53 192.168.122.209 [37603.701008] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:30:53 192.168.122.209 [37604.129734] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:30:53 192.168.122.209 [37604.155850] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:30:53 192.168.122.209 [37604.182522] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:30:53 192.168.122.209 [37604.221780] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:30:53 192.168.122.209 [37604.223531] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:30:53 192.168.122.209 [37604.261719] [tempesta fw] Tempesta FW is ready Apr 26 02:30:54 192.168.122.209 [37604.875352] [tdb] Close table 'client0.tdb' Apr 26 02:30:54 192.168.122.209 [37605.061095] [tdb] Close table 'sessions0.tdb' Apr 26 02:30:57 192.168.122.209 [37608.266312] [tdb] Close table 'cache0.tdb' Apr 26 02:30:58 192.168.122.209 [37608.487761] [tdb] Close table 'filter0.tdb' Apr 26 02:30:58 192.168.122.209 [37608.488195] [tempesta fw] modules are stopped Apr 26 02:30:58 192.168.122.209 [37608.679548] [tempesta fw] exiting... Apr 26 02:30:58 192.168.122.209 [37608.832565] [tdb] Shutdown Tempesta DB Apr 26 02:30:58 192.168.122.209 [37609.099779] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_pragma_no_cache_in_request_and_cache_lvl_2 Apr 26 02:30:58 192.168.122.209 [37609.116661] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_pragma_no_cache_in_response_and_cache_lvl_1 Apr 26 02:30:59 192.168.122.209 [37610.229226] [tdb] Start Tempesta DB Apr 26 02:31:00 192.168.122.209 [37610.375272] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:31:01 192.168.122.209 [37611.755122] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37611.755122] Maybe that's fine, but it's worth checking the [37611.755122] config - if there is no relations between the [37611.755122] names, then host name confusion attack is possible. Apr 26 02:31:01 192.168.122.209 [37611.849893] [tempesta fw] Configuration processing is completed. Apr 26 02:31:01 192.168.122.209 [37611.934942] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:31:02 192.168.122.209 [37612.360441] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:31:02 192.168.122.209 [37612.387565] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:31:02 192.168.122.209 [37612.414968] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:31:02 192.168.122.209 [37612.477801] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:31:02 192.168.122.209 [37612.478568] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:31:02 192.168.122.209 [37612.525807] [tempesta fw] Tempesta FW is ready Apr 26 02:31:02 192.168.122.209 [37613.160267] [tdb] Close table 'client0.tdb' Apr 26 02:31:03 192.168.122.209 [37613.351283] [tdb] Close table 'sessions0.tdb' Apr 26 02:31:06 192.168.122.209 [37616.507889] [tdb] Close table 'cache0.tdb' Apr 26 02:31:06 192.168.122.209 [37616.741678] [tdb] Close table 'filter0.tdb' Apr 26 02:31:06 192.168.122.209 [37616.742925] [tempesta fw] modules are stopped Apr 26 02:31:06 192.168.122.209 [37616.963568] [tempesta fw] exiting... Apr 26 02:31:06 192.168.122.209 [37617.121204] [tdb] Shutdown Tempesta DB Apr 26 02:31:07 192.168.122.209 [37617.359959] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_pragma_no_cache_in_response_and_cache_lvl_1 Apr 26 02:31:07 192.168.122.209 [37617.373354] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_pragma_no_cache_in_response_and_cache_lvl_2 Apr 26 02:31:08 192.168.122.209 [37618.586024] [tdb] Start Tempesta DB Apr 26 02:31:08 192.168.122.209 [37618.742069] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:31:09 192.168.122.209 [37620.143201] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37620.143201] Maybe that's fine, but it's worth checking the [37620.143201] config - if there is no relations between the [37620.143201] names, then host name confusion attack is possible. Apr 26 02:31:09 192.168.122.209 [37620.229996] [tempesta fw] Configuration processing is completed. Apr 26 02:31:10 192.168.122.209 [37620.281468] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:31:10 192.168.122.209 [37620.699649] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:31:10 192.168.122.209 [37620.725451] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:31:10 192.168.122.209 [37620.753233] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:31:10 192.168.122.209 [37620.801952] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:31:10 192.168.122.209 [37620.803249] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:31:10 192.168.122.209 [37620.841936] [tempesta fw] Tempesta FW is ready Apr 26 02:31:11 192.168.122.209 [37621.485432] [tdb] Close table 'client0.tdb' Apr 26 02:31:11 192.168.122.209 [37621.672449] [tdb] Close table 'sessions0.tdb' Apr 26 02:31:14 192.168.122.209 [37624.849386] [tdb] Close table 'cache0.tdb' Apr 26 02:31:15 192.168.122.209 [37625.338528] [tdb] Close table 'filter0.tdb' Apr 26 02:31:15 192.168.122.209 [37625.338997] [tempesta fw] modules are stopped Apr 26 02:31:16 192.168.122.209 [37626.664160] [tempesta fw] exiting... Apr 26 02:31:16 192.168.122.209 [37627.237225] [tdb] Shutdown Tempesta DB Apr 26 02:31:17 192.168.122.209 [37627.821099] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_pragma_no_cache_in_response_and_cache_lvl_2 Apr 26 02:31:17 192.168.122.209 [37627.841201] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_max_stale Apr 26 02:31:18 192.168.122.209 [37629.222748] [tdb] Start Tempesta DB Apr 26 02:31:19 192.168.122.209 [37629.412710] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:31:21 192.168.122.209 [37631.444009] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37631.444009] Maybe that's fine, but it's worth checking the [37631.444009] config - if there is no relations between the [37631.444009] names, then host name confusion attack is possible. Apr 26 02:31:21 192.168.122.209 [37631.534382] [tempesta fw] Configuration processing is completed. Apr 26 02:31:21 192.168.122.209 [37631.584973] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:31:21 192.168.122.209 [37632.019980] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:31:21 192.168.122.209 [37632.046667] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:31:21 192.168.122.209 [37632.073054] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:31:21 192.168.122.209 [37632.122120] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:31:21 192.168.122.209 [37632.162079] [tempesta fw] Tempesta FW is ready Apr 26 02:31:33 192.168.122.209 [37643.786363] [tdb] Close table 'client0.tdb' Apr 26 02:31:33 192.168.122.209 [37643.965886] [tdb] Close table 'sessions0.tdb' Apr 26 02:31:36 192.168.122.209 [37647.138158] [tdb] Close table 'cache0.tdb' Apr 26 02:31:37 192.168.122.209 [37647.378034] [tdb] Close table 'filter0.tdb' Apr 26 02:31:37 192.168.122.209 [37647.378491] [tempesta fw] modules are stopped Apr 26 02:31:37 192.168.122.209 [37647.562297] [tempesta fw] exiting... Apr 26 02:31:37 192.168.122.209 [37647.703276] [tdb] Shutdown Tempesta DB Apr 26 02:31:37 192.168.122.209 [37647.924190] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_max_stale Apr 26 02:31:37 192.168.122.209 [37647.961671] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_stale_if_error_not_use_304 Apr 26 02:31:38 192.168.122.209 [37649.179269] [tdb] Start Tempesta DB Apr 26 02:31:39 192.168.122.209 [37649.327712] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:31:40 192.168.122.209 [37650.812038] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37650.812038] Maybe that's fine, but it's worth checking the [37650.812038] config - if there is no relations between the [37650.812038] names, then host name confusion attack is possible. Apr 26 02:31:40 192.168.122.209 [37650.890657] [tempesta fw] Configuration processing is completed. Apr 26 02:31:40 192.168.122.209 [37650.941266] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:31:41 192.168.122.209 [37651.368368] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:31:41 192.168.122.209 [37651.394398] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:31:41 192.168.122.209 [37651.420189] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:31:41 192.168.122.209 [37651.462256] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:31:41 192.168.122.209 [37651.506322] [tempesta fw] Tempesta FW is ready Apr 26 02:31:43 192.168.122.209 [37654.116001] [tdb] Close table 'client0.tdb' Apr 26 02:31:44 192.168.122.209 [37654.324193] [tdb] Close table 'sessions0.tdb' Apr 26 02:31:47 192.168.122.209 [37657.469381] [tdb] Close table 'cache0.tdb' Apr 26 02:31:47 192.168.122.209 [37657.719154] [tdb] Close table 'filter0.tdb' Apr 26 02:31:47 192.168.122.209 [37657.719619] [tempesta fw] modules are stopped Apr 26 02:31:47 192.168.122.209 [37657.895525] [tempesta fw] exiting... Apr 26 02:31:47 192.168.122.209 [37658.061830] [tdb] Shutdown Tempesta DB Apr 26 02:31:48 192.168.122.209 [37658.292450] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_stale_if_error_not_use_304 Apr 26 02:31:48 192.168.122.209 [37658.308684] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_fresh_200 Apr 26 02:31:49 192.168.122.209 [37659.545765] [tdb] Start Tempesta DB Apr 26 02:31:49 192.168.122.209 [37659.699366] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:31:50 192.168.122.209 [37661.184202] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37661.184202] Maybe that's fine, but it's worth checking the [37661.184202] config - if there is no relations between the [37661.184202] names, then host name confusion attack is possible. Apr 26 02:31:51 192.168.122.209 [37661.298483] [tempesta fw] Configuration processing is completed. Apr 26 02:31:51 192.168.122.209 [37661.353241] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:31:51 192.168.122.209 [37661.780481] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:31:51 192.168.122.209 [37661.806911] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:31:51 192.168.122.209 [37661.832926] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:31:51 192.168.122.209 [37661.882496] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:31:51 192.168.122.209 [37661.930455] [tempesta fw] Tempesta FW is ready Apr 26 02:31:55 192.168.122.209 [37665.552392] [tdb] Close table 'client0.tdb' Apr 26 02:31:55 192.168.122.209 [37665.758636] [tdb] Close table 'sessions0.tdb' Apr 26 02:31:58 192.168.122.209 [37668.891968] [tdb] Close table 'cache0.tdb' Apr 26 02:31:58 192.168.122.209 [37669.152349] [tdb] Close table 'filter0.tdb' Apr 26 02:31:58 192.168.122.209 [37669.152784] [tempesta fw] modules are stopped Apr 26 02:31:59 192.168.122.209 [37669.339504] [tempesta fw] exiting... Apr 26 02:31:59 192.168.122.209 [37669.498339] [tdb] Shutdown Tempesta DB Apr 26 02:31:59 192.168.122.209 [37669.716538] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_fresh_200 Apr 26 02:31:59 192.168.122.209 [37669.740632] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_fresh_403 Apr 26 02:32:00 192.168.122.209 [37670.970541] [tdb] Start Tempesta DB Apr 26 02:32:00 192.168.122.209 [37671.127629] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:32:02 192.168.122.209 [37672.668345] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37672.668345] Maybe that's fine, but it's worth checking the [37672.668345] config - if there is no relations between the [37672.668345] names, then host name confusion attack is possible. Apr 26 02:32:02 192.168.122.209 [37672.758947] [tempesta fw] Configuration processing is completed. Apr 26 02:32:02 192.168.122.209 [37672.845132] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:32:03 192.168.122.209 [37673.288955] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:32:03 192.168.122.209 [37673.326565] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:32:03 192.168.122.209 [37673.354853] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:32:03 192.168.122.209 [37673.402566] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:32:03 192.168.122.209 [37673.442594] [tempesta fw] Tempesta FW is ready Apr 26 02:32:06 192.168.122.209 [37677.043115] [tdb] Close table 'client0.tdb' Apr 26 02:32:06 192.168.122.209 [37677.221812] [tdb] Close table 'sessions0.tdb' Apr 26 02:32:10 192.168.122.209 [37680.473511] [tdb] Close table 'cache0.tdb' Apr 26 02:32:10 192.168.122.209 [37680.717321] [tdb] Close table 'filter0.tdb' Apr 26 02:32:10 192.168.122.209 [37680.717768] [tempesta fw] modules are stopped Apr 26 02:32:10 192.168.122.209 [37680.895171] [tempesta fw] exiting... Apr 26 02:32:10 192.168.122.209 [37681.051463] [tdb] Shutdown Tempesta DB Apr 26 02:32:11 192.168.122.209 [37681.282506] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_fresh_403 Apr 26 02:32:11 192.168.122.209 [37681.302112] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_fresh_on_error_must_revalidate Apr 26 02:32:12 192.168.122.209 [37682.515644] [tdb] Start Tempesta DB Apr 26 02:32:12 192.168.122.209 [37682.665954] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:32:13 192.168.122.209 [37684.056425] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37684.056425] Maybe that's fine, but it's worth checking the [37684.056425] config - if there is no relations between the [37684.056425] names, then host name confusion attack is possible. Apr 26 02:32:13 192.168.122.209 [37684.159090] [tempesta fw] Configuration processing is completed. Apr 26 02:32:13 192.168.122.209 [37684.208452] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:32:14 192.168.122.209 [37684.637220] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:32:14 192.168.122.209 [37684.663547] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:32:14 192.168.122.209 [37684.689623] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:32:14 192.168.122.209 [37684.746735] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:32:14 192.168.122.209 [37684.786754] [tempesta fw] Tempesta FW is ready Apr 26 02:32:18 192.168.122.209 [37688.365002] [tdb] Close table 'client0.tdb' Apr 26 02:32:18 192.168.122.209 [37688.555766] [tdb] Close table 'sessions0.tdb' Apr 26 02:32:21 192.168.122.209 [37691.762259] [tdb] Close table 'cache0.tdb' Apr 26 02:32:21 192.168.122.209 [37692.004462] [tdb] Close table 'filter0.tdb' Apr 26 02:32:21 192.168.122.209 [37692.004904] [tempesta fw] modules are stopped Apr 26 02:32:21 192.168.122.209 [37692.197765] [tempesta fw] exiting... Apr 26 02:32:22 192.168.122.209 [37692.348498] [tdb] Shutdown Tempesta DB Apr 26 02:32:22 192.168.122.209 [37692.576579] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_fresh_on_error_must_revalidate Apr 26 02:32:22 192.168.122.209 [37692.593933] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_fresh_on_error_proxy_revalidate Apr 26 02:32:23 192.168.122.209 [37693.685357] [tdb] Start Tempesta DB Apr 26 02:32:23 192.168.122.209 [37693.843523] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:32:25 192.168.122.209 [37695.352681] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37695.352681] Maybe that's fine, but it's worth checking the [37695.352681] config - if there is no relations between the [37695.352681] names, then host name confusion attack is possible. Apr 26 02:32:25 192.168.122.209 [37695.482931] [tempesta fw] Configuration processing is completed. Apr 26 02:32:25 192.168.122.209 [37695.533128] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:32:25 192.168.122.209 [37695.979646] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:32:25 192.168.122.209 [37696.006243] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:32:25 192.168.122.209 [37696.033231] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:32:25 192.168.122.209 [37696.094933] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:32:25 192.168.122.209 [37696.146821] [tempesta fw] Tempesta FW is ready Apr 26 02:32:29 192.168.122.209 [37699.760323] [tdb] Close table 'client0.tdb' Apr 26 02:32:29 192.168.122.209 [37699.948754] [tdb] Close table 'sessions0.tdb' Apr 26 02:32:32 192.168.122.209 [37703.204994] [tdb] Close table 'cache0.tdb' Apr 26 02:32:33 192.168.122.209 [37703.438877] [tdb] Close table 'filter0.tdb' Apr 26 02:32:33 192.168.122.209 [37703.439310] [tempesta fw] modules are stopped Apr 26 02:32:33 192.168.122.209 [37703.678984] [tempesta fw] exiting... Apr 26 02:32:33 192.168.122.209 [37703.827931] [tdb] Shutdown Tempesta DB Apr 26 02:32:33 192.168.122.209 [37704.056023] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_fresh_on_error_proxy_revalidate Apr 26 02:32:33 192.168.122.209 [37704.087927] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_fresh_on_error_s_maxage Apr 26 02:32:34 192.168.122.209 [37705.275685] [tdb] Start Tempesta DB Apr 26 02:32:35 192.168.122.209 [37705.439692] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:32:36 192.168.122.209 [37706.932812] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37706.932812] Maybe that's fine, but it's worth checking the [37706.932812] config - if there is no relations between the [37706.932812] names, then host name confusion attack is possible. Apr 26 02:32:36 192.168.122.209 [37707.027370] [tempesta fw] Configuration processing is completed. Apr 26 02:32:36 192.168.122.209 [37707.083498] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:32:37 192.168.122.209 [37707.511008] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:32:37 192.168.122.209 [37707.537639] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:32:37 192.168.122.209 [37707.564521] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:32:37 192.168.122.209 [37707.615104] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:32:37 192.168.122.209 [37707.659059] [tempesta fw] Tempesta FW is ready Apr 26 02:32:41 192.168.122.209 [37711.292991] [tdb] Close table 'client0.tdb' Apr 26 02:32:41 192.168.122.209 [37711.480152] [tdb] Close table 'sessions0.tdb' Apr 26 02:32:44 192.168.122.209 [37714.611011] [tdb] Close table 'cache0.tdb' Apr 26 02:32:44 192.168.122.209 [37714.861416] [tdb] Close table 'filter0.tdb' Apr 26 02:32:44 192.168.122.209 [37714.861858] [tempesta fw] modules are stopped Apr 26 02:32:44 192.168.122.209 [37715.043525] [tempesta fw] exiting... Apr 26 02:32:44 192.168.122.209 [37715.206270] [tdb] Shutdown Tempesta DB Apr 26 02:32:45 192.168.122.209 [37715.434257] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_fresh_on_error_s_maxage Apr 26 02:32:45 192.168.122.209 [37715.456368] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_400 Apr 26 02:32:46 192.168.122.209 [37716.652205] [tdb] Start Tempesta DB Apr 26 02:32:46 192.168.122.209 [37716.796156] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:32:47 192.168.122.209 [37718.248893] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37718.248893] Maybe that's fine, but it's worth checking the [37718.248893] config - if there is no relations between the [37718.248893] names, then host name confusion attack is possible. Apr 26 02:32:48 192.168.122.209 [37718.343519] [tempesta fw] Configuration processing is completed. Apr 26 02:32:48 192.168.122.209 [37718.394303] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:32:48 192.168.122.209 [37718.832265] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:32:48 192.168.122.209 [37718.859043] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:32:48 192.168.122.209 [37718.886368] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:32:48 192.168.122.209 [37718.931249] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:32:48 192.168.122.209 [37718.975180] [tempesta fw] Tempesta FW is ready Apr 26 02:32:52 192.168.122.209 [37722.581743] [tdb] Close table 'client0.tdb' Apr 26 02:32:52 192.168.122.209 [37722.758153] [tdb] Close table 'sessions0.tdb' Apr 26 02:32:55 192.168.122.209 [37725.953825] [tdb] Close table 'cache0.tdb' Apr 26 02:32:55 192.168.122.209 [37726.204909] [tdb] Close table 'filter0.tdb' Apr 26 02:32:55 192.168.122.209 [37726.205336] [tempesta fw] modules are stopped Apr 26 02:32:56 192.168.122.209 [37726.384444] [tempesta fw] exiting... Apr 26 02:32:56 192.168.122.209 [37726.513045] [tdb] Shutdown Tempesta DB Apr 26 02:32:56 192.168.122.209 [37726.734685] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_400 Apr 26 02:32:56 192.168.122.209 [37726.762771] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_4xx_400 Apr 26 02:32:57 192.168.122.209 [37727.951961] [tdb] Start Tempesta DB Apr 26 02:32:57 192.168.122.209 [37728.109471] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:32:59 192.168.122.209 [37729.645233] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37729.645233] Maybe that's fine, but it's worth checking the [37729.645233] config - if there is no relations between the [37729.645233] names, then host name confusion attack is possible. Apr 26 02:32:59 192.168.122.209 [37729.735661] [tempesta fw] Configuration processing is completed. Apr 26 02:32:59 192.168.122.209 [37729.785079] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:32:59 192.168.122.209 [37730.204453] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:32:59 192.168.122.209 [37730.230896] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:32:59 192.168.122.209 [37730.257302] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:33:00 192.168.122.209 [37730.299344] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:33:00 192.168.122.209 [37730.331332] [tempesta fw] Tempesta FW is ready Apr 26 02:33:03 192.168.122.209 [37733.885768] [tdb] Close table 'client0.tdb' Apr 26 02:33:03 192.168.122.209 [37734.091338] [tdb] Close table 'sessions0.tdb' Apr 26 02:33:06 192.168.122.209 [37737.211914] [tdb] Close table 'cache0.tdb' Apr 26 02:33:07 192.168.122.209 [37737.474906] [tdb] Close table 'filter0.tdb' Apr 26 02:33:07 192.168.122.209 [37737.475380] [tempesta fw] modules are stopped Apr 26 02:33:07 192.168.122.209 [37737.675214] [tempesta fw] exiting... Apr 26 02:33:07 192.168.122.209 [37737.842638] [tdb] Shutdown Tempesta DB Apr 26 02:33:07 192.168.122.209 [37738.087210] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_4xx_400 Apr 26 02:33:07 192.168.122.209 [37738.124174] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_4xx_403 Apr 26 02:33:09 192.168.122.209 [37739.289220] [tdb] Start Tempesta DB Apr 26 02:33:09 192.168.122.209 [37739.423869] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:33:10 192.168.122.209 [37740.886920] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37740.886920] Maybe that's fine, but it's worth checking the [37740.886920] config - if there is no relations between the [37740.886920] names, then host name confusion attack is possible. Apr 26 02:33:10 192.168.122.209 [37740.975836] [tempesta fw] Configuration processing is completed. Apr 26 02:33:10 192.168.122.209 [37741.026862] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:33:11 192.168.122.209 [37741.465663] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:33:11 192.168.122.209 [37741.491854] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:33:11 192.168.122.209 [37741.518002] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:33:11 192.168.122.209 [37741.579530] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:33:11 192.168.122.209 [37741.619465] [tempesta fw] Tempesta FW is ready Apr 26 02:33:14 192.168.122.209 [37745.231936] [tdb] Close table 'client0.tdb' Apr 26 02:33:15 192.168.122.209 [37745.422948] [tdb] Close table 'sessions0.tdb' Apr 26 02:33:18 192.168.122.209 [37748.584996] [tdb] Close table 'cache0.tdb' Apr 26 02:33:18 192.168.122.209 [37748.818024] [tdb] Close table 'filter0.tdb' Apr 26 02:33:18 192.168.122.209 [37748.818463] [tempesta fw] modules are stopped Apr 26 02:33:18 192.168.122.209 [37748.991980] [tempesta fw] exiting... Apr 26 02:33:18 192.168.122.209 [37749.156051] [tdb] Shutdown Tempesta DB Apr 26 02:33:19 192.168.122.209 [37749.378942] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_4xx_403 Apr 26 02:33:19 192.168.122.209 [37749.396784] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_4xx_5xx Apr 26 02:33:20 192.168.122.209 [37750.535964] [tdb] Start Tempesta DB Apr 26 02:33:20 192.168.122.209 [37750.692470] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:33:21 192.168.122.209 [37752.145311] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37752.145311] Maybe that's fine, but it's worth checking the [37752.145311] config - if there is no relations between the [37752.145311] names, then host name confusion attack is possible. Apr 26 02:33:21 192.168.122.209 [37752.247669] [tempesta fw] Configuration processing is completed. Apr 26 02:33:22 192.168.122.209 [37752.310782] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:33:22 192.168.122.209 [37752.738610] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:33:22 192.168.122.209 [37752.764957] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:33:22 192.168.122.209 [37752.791009] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:33:22 192.168.122.209 [37752.875675] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:33:22 192.168.122.209 [37752.927627] [tempesta fw] Tempesta FW is ready Apr 26 02:33:26 192.168.122.209 [37756.538444] [tdb] Close table 'client0.tdb' Apr 26 02:33:26 192.168.122.209 [37756.731235] [tdb] Close table 'sessions0.tdb' Apr 26 02:33:29 192.168.122.209 [37759.897872] [tdb] Close table 'cache0.tdb' Apr 26 02:33:29 192.168.122.209 [37760.164146] [tdb] Close table 'filter0.tdb' Apr 26 02:33:29 192.168.122.209 [37760.164594] [tempesta fw] modules are stopped Apr 26 02:33:30 192.168.122.209 [37760.339534] [tempesta fw] exiting... Apr 26 02:33:30 192.168.122.209 [37760.524610] [tdb] Shutdown Tempesta DB Apr 26 02:33:30 192.168.122.209 [37760.785294] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_4xx_5xx Apr 26 02:33:30 192.168.122.209 [37760.809078] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_500 Apr 26 02:33:31 192.168.122.209 [37762.028117] [tdb] Start Tempesta DB Apr 26 02:33:31 192.168.122.209 [37762.182870] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:33:33 192.168.122.209 [37763.637484] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37763.637484] Maybe that's fine, but it's worth checking the [37763.637484] config - if there is no relations between the [37763.637484] names, then host name confusion attack is possible. Apr 26 02:33:33 192.168.122.209 [37763.728205] [tempesta fw] Configuration processing is completed. Apr 26 02:33:33 192.168.122.209 [37763.793237] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:33:33 192.168.122.209 [37764.230748] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:33:33 192.168.122.209 [37764.257778] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:33:34 192.168.122.209 [37764.285404] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:33:34 192.168.122.209 [37764.343748] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:33:34 192.168.122.209 [37764.391780] [tempesta fw] Tempesta FW is ready Apr 26 02:33:37 192.168.122.209 [37768.045435] [tdb] Close table 'client0.tdb' Apr 26 02:33:37 192.168.122.209 [37768.232727] [tdb] Close table 'sessions0.tdb' Apr 26 02:33:41 192.168.122.209 [37771.381365] [tdb] Close table 'cache0.tdb' Apr 26 02:33:41 192.168.122.209 [37771.609054] [tdb] Close table 'filter0.tdb' Apr 26 02:33:41 192.168.122.209 [37771.609493] [tempesta fw] modules are stopped Apr 26 02:33:41 192.168.122.209 [37771.821420] [tempesta fw] exiting... Apr 26 02:33:41 192.168.122.209 [37772.000415] [tdb] Shutdown Tempesta DB Apr 26 02:33:41 192.168.122.209 [37772.228458] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_500 Apr 26 02:33:41 192.168.122.209 [37772.253215] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_5xx_500 Apr 26 02:33:43 192.168.122.209 [37773.443330] [tdb] Start Tempesta DB Apr 26 02:33:43 192.168.122.209 [37773.587372] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:33:44 192.168.122.209 [37775.081599] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37775.081599] Maybe that's fine, but it's worth checking the [37775.081599] config - if there is no relations between the [37775.081599] names, then host name confusion attack is possible. Apr 26 02:33:44 192.168.122.209 [37775.191922] [tempesta fw] Configuration processing is completed. Apr 26 02:33:44 192.168.122.209 [37775.240530] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:33:45 192.168.122.209 [37775.663243] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:33:45 192.168.122.209 [37775.689100] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:33:45 192.168.122.209 [37775.714889] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:33:45 192.168.122.209 [37775.755951] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:33:45 192.168.122.209 [37775.795911] [tempesta fw] Tempesta FW is ready Apr 26 02:33:49 192.168.122.209 [37779.404610] [tdb] Close table 'client0.tdb' Apr 26 02:33:49 192.168.122.209 [37779.574343] [tdb] Close table 'sessions0.tdb' Apr 26 02:33:52 192.168.122.209 [37782.825211] [tdb] Close table 'cache0.tdb' Apr 26 02:33:52 192.168.122.209 [37783.078622] [tdb] Close table 'filter0.tdb' Apr 26 02:33:52 192.168.122.209 [37783.079079] [tempesta fw] modules are stopped Apr 26 02:33:52 192.168.122.209 [37783.243682] [tempesta fw] exiting... Apr 26 02:33:53 192.168.122.209 [37783.392925] [tdb] Shutdown Tempesta DB Apr 26 02:33:53 192.168.122.209 [37783.622656] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_5xx_500 Apr 26 02:33:53 192.168.122.209 [37783.638318] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_5xx_502 Apr 26 02:33:54 192.168.122.209 [37784.852265] [tdb] Start Tempesta DB Apr 26 02:33:54 192.168.122.209 [37784.996864] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:33:56 192.168.122.209 [37786.457473] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37786.457473] Maybe that's fine, but it's worth checking the [37786.457473] config - if there is no relations between the [37786.457473] names, then host name confusion attack is possible. Apr 26 02:33:56 192.168.122.209 [37786.552338] [tempesta fw] Configuration processing is completed. Apr 26 02:33:56 192.168.122.209 [37786.603155] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:33:56 192.168.122.209 [37787.040904] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:33:56 192.168.122.209 [37787.067982] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:33:56 192.168.122.209 [37787.095089] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:33:56 192.168.122.209 [37787.144079] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:33:56 192.168.122.209 [37787.183967] [tempesta fw] Tempesta FW is ready Apr 26 02:34:00 192.168.122.209 [37790.786484] [tdb] Close table 'client0.tdb' Apr 26 02:34:00 192.168.122.209 [37790.973430] [tdb] Close table 'sessions0.tdb' Apr 26 02:34:03 192.168.122.209 [37794.115710] [tdb] Close table 'cache0.tdb' Apr 26 02:34:04 192.168.122.209 [37794.351409] [tdb] Close table 'filter0.tdb' Apr 26 02:34:04 192.168.122.209 [37794.351854] [tempesta fw] modules are stopped Apr 26 02:34:04 192.168.122.209 [37794.538942] [tempesta fw] exiting... Apr 26 02:34:04 192.168.122.209 [37794.660090] [tdb] Shutdown Tempesta DB Apr 26 02:34:04 192.168.122.209 [37794.895814] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_5xx_502 Apr 26 02:34:04 192.168.122.209 [37794.916884] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_if_error_duplicated_req Apr 26 02:34:05 192.168.122.209 [37795.979094] [tdb] Start Tempesta DB Apr 26 02:34:05 192.168.122.209 [37796.120384] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:34:07 192.168.122.209 [37797.589928] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37797.589928] Maybe that's fine, but it's worth checking the [37797.589928] config - if there is no relations between the [37797.589928] names, then host name confusion attack is possible. Apr 26 02:34:07 192.168.122.209 [37797.688525] [tempesta fw] Configuration processing is completed. Apr 26 02:34:07 192.168.122.209 [37797.736945] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:34:07 192.168.122.209 [37798.156765] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:34:07 192.168.122.209 [37798.182916] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:34:07 192.168.122.209 [37798.208640] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:34:08 192.168.122.209 [37798.284279] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:34:08 192.168.122.209 [37798.328196] [tempesta fw] Tempesta FW is ready Apr 26 02:34:08 192.168.122.209 [37798.906072] [tdb] Close table 'client0.tdb' Apr 26 02:34:08 192.168.122.209 [37799.120033] [tdb] Close table 'sessions0.tdb' Apr 26 02:34:12 192.168.122.209 [37802.306222] [tdb] Close table 'cache0.tdb' Apr 26 02:34:12 192.168.122.209 [37802.548447] [tdb] Close table 'filter0.tdb' Apr 26 02:34:12 192.168.122.209 [37802.548885] [tempesta fw] modules are stopped Apr 26 02:34:12 192.168.122.209 [37802.752535] [tempesta fw] exiting... Apr 26 02:34:12 192.168.122.209 [37802.892061] [tdb] Shutdown Tempesta DB Apr 26 02:34:12 192.168.122.209 [37803.144279] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_if_error_duplicated_req Apr 26 02:34:12 192.168.122.209 [37803.155646] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_if_error_duplicated_resp Apr 26 02:34:14 192.168.122.209 [37804.415259] [tdb] Start Tempesta DB Apr 26 02:34:14 192.168.122.209 [37804.554764] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:34:15 192.168.122.209 [37806.017986] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37806.017986] Maybe that's fine, but it's worth checking the [37806.017986] config - if there is no relations between the [37806.017986] names, then host name confusion attack is possible. Apr 26 02:34:15 192.168.122.209 [37806.116342] [tempesta fw] Configuration processing is completed. Apr 26 02:34:15 192.168.122.209 [37806.170015] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:34:16 192.168.122.209 [37806.592625] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:34:16 192.168.122.209 [37806.619279] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:34:16 192.168.122.209 [37806.645481] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:34:16 192.168.122.209 [37806.696358] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:34:16 192.168.122.209 [37806.744301] [tempesta fw] Tempesta FW is ready Apr 26 02:34:16 192.168.122.209 [37806.901210] [tempesta fw] Warning: Parser error: state=Resp_HdrCache_CtrlV input(-8)=0x73('ontrol: stale-if-error=20, stale-if-error=19 [37806.901210] da') data_len=128 off=51 Apr 26 02:34:16 192.168.122.209 [37806.902634] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 02:34:17 192.168.122.209 [37807.347672] [tdb] Close table 'client0.tdb' Apr 26 02:34:17 192.168.122.209 [37807.571062] [tdb] Close table 'sessions0.tdb' Apr 26 02:34:20 192.168.122.209 [37810.790497] [tdb] Close table 'cache0.tdb' Apr 26 02:34:20 192.168.122.209 [37811.009205] [tdb] Close table 'filter0.tdb' Apr 26 02:34:20 192.168.122.209 [37811.009658] [tempesta fw] modules are stopped Apr 26 02:34:20 192.168.122.209 [37811.230417] [tempesta fw] exiting... Apr 26 02:34:21 192.168.122.209 [37811.405726] [tdb] Shutdown Tempesta DB Apr 26 02:34:21 192.168.122.209 [37811.648948] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_if_error_duplicated_resp Apr 26 02:34:21 192.168.122.209 [37811.666384] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_if_error_param_req Apr 26 02:34:22 192.168.122.209 [37812.868716] [tdb] Start Tempesta DB Apr 26 02:34:22 192.168.122.209 [37813.032615] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:34:24 192.168.122.209 [37814.473716] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37814.473716] Maybe that's fine, but it's worth checking the [37814.473716] config - if there is no relations between the [37814.473716] names, then host name confusion attack is possible. Apr 26 02:34:24 192.168.122.209 [37814.544753] [tempesta fw] Configuration processing is completed. Apr 26 02:34:24 192.168.122.209 [37814.594206] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:34:24 192.168.122.209 [37815.032817] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:34:24 192.168.122.209 [37815.059451] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:34:24 192.168.122.209 [37815.086160] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:34:24 192.168.122.209 [37815.144417] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:34:24 192.168.122.209 [37815.192414] [tempesta fw] Tempesta FW is ready Apr 26 02:34:28 192.168.122.209 [37818.813441] [tdb] Close table 'client0.tdb' Apr 26 02:34:28 192.168.122.209 [37819.006798] [tdb] Close table 'sessions0.tdb' Apr 26 02:34:31 192.168.122.209 [37822.142049] [tdb] Close table 'cache0.tdb' Apr 26 02:34:32 192.168.122.209 [37822.381544] [tdb] Close table 'filter0.tdb' Apr 26 02:34:32 192.168.122.209 [37822.381984] [tempesta fw] modules are stopped Apr 26 02:34:32 192.168.122.209 [37822.609550] [tempesta fw] exiting... Apr 26 02:34:32 192.168.122.209 [37822.768533] [tdb] Shutdown Tempesta DB Apr 26 02:34:32 192.168.122.209 [37822.995601] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_if_error_param_req Apr 26 02:34:32 192.168.122.209 [37823.013912] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_if_error_param_resp Apr 26 02:34:33 192.168.122.209 [37824.258220] [tdb] Start Tempesta DB Apr 26 02:34:34 192.168.122.209 [37824.405425] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:34:35 192.168.122.209 [37825.862239] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37825.862239] Maybe that's fine, but it's worth checking the [37825.862239] config - if there is no relations between the [37825.862239] names, then host name confusion attack is possible. Apr 26 02:34:35 192.168.122.209 [37825.940894] [tempesta fw] Configuration processing is completed. Apr 26 02:34:35 192.168.122.209 [37825.992742] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:34:36 192.168.122.209 [37826.412984] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:34:36 192.168.122.209 [37826.438302] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:34:36 192.168.122.209 [37826.463375] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:34:36 192.168.122.209 [37826.512585] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:34:36 192.168.122.209 [37826.552554] [tempesta fw] Tempesta FW is ready Apr 26 02:34:39 192.168.122.209 [37830.194757] [tdb] Close table 'client0.tdb' Apr 26 02:34:40 192.168.122.209 [37830.384094] [tdb] Close table 'sessions0.tdb' Apr 26 02:34:43 192.168.122.209 [37833.582004] [tdb] Close table 'cache0.tdb' Apr 26 02:34:43 192.168.122.209 [37833.818468] [tdb] Close table 'filter0.tdb' Apr 26 02:34:43 192.168.122.209 [37833.818910] [tempesta fw] modules are stopped Apr 26 02:34:43 192.168.122.209 [37834.011261] [tempesta fw] exiting... Apr 26 02:34:43 192.168.122.209 [37834.157225] [tdb] Shutdown Tempesta DB Apr 26 02:34:44 192.168.122.209 [37834.388062] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_if_error_param_resp Apr 26 02:34:44 192.168.122.209 [37834.406700] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_invalid_response Apr 26 02:34:45 192.168.122.209 [37835.637017] [tdb] Start Tempesta DB Apr 26 02:34:45 192.168.122.209 [37835.779210] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:34:46 192.168.122.209 [37837.214490] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37837.214490] Maybe that's fine, but it's worth checking the [37837.214490] config - if there is no relations between the [37837.214490] names, then host name confusion attack is possible. Apr 26 02:34:47 192.168.122.209 [37837.352755] [tempesta fw] Configuration processing is completed. Apr 26 02:34:47 192.168.122.209 [37837.447678] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:34:47 192.168.122.209 [37837.888287] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:34:47 192.168.122.209 [37837.915964] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:34:47 192.168.122.209 [37837.944159] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:34:47 192.168.122.209 [37837.992759] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:34:47 192.168.122.209 [37838.028694] [tempesta fw] Tempesta FW is ready Apr 26 02:34:50 192.168.122.209 [37841.204177] [tempesta fw] Warning: Parser error: state=RGen_HdrOtherN input(-8)=0x68('gth: 0 [37841.204177] hd>r: v [37841.204177] date: Sat, 26 Apr 2025 02:34:50') data_len=91 off=43 Apr 26 02:34:51 192.168.122.209 [37841.644967] [tdb] Close table 'client0.tdb' Apr 26 02:34:51 192.168.122.209 [37841.819962] [tdb] Close table 'sessions0.tdb' Apr 26 02:34:54 192.168.122.209 [37844.978956] [tdb] Close table 'cache0.tdb' Apr 26 02:34:54 192.168.122.209 [37845.224522] [tdb] Close table 'filter0.tdb' Apr 26 02:34:54 192.168.122.209 [37845.224985] [tempesta fw] modules are stopped Apr 26 02:34:55 192.168.122.209 [37845.486590] [tempesta fw] exiting... Apr 26 02:34:55 192.168.122.209 [37845.619923] [tdb] Shutdown Tempesta DB Apr 26 02:34:55 192.168.122.209 [37845.836341] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_invalid_response Apr 26 02:34:55 192.168.122.209 [37845.856356] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_then_fresh_req Apr 26 02:34:56 192.168.122.209 [37847.015067] [tdb] Start Tempesta DB Apr 26 02:34:56 192.168.122.209 [37847.152902] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:34:58 192.168.122.209 [37848.630624] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37848.630624] Maybe that's fine, but it's worth checking the [37848.630624] config - if there is no relations between the [37848.630624] names, then host name confusion attack is possible. Apr 26 02:34:58 192.168.122.209 [37848.720851] [tempesta fw] Configuration processing is completed. Apr 26 02:34:58 192.168.122.209 [37848.769726] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:34:58 192.168.122.209 [37849.186948] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:34:58 192.168.122.209 [37849.212531] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:34:58 192.168.122.209 [37849.237616] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:34:58 192.168.122.209 [37849.280847] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:34:59 192.168.122.209 [37849.324908] [tempesta fw] Tempesta FW is ready Apr 26 02:35:05 192.168.122.209 [37855.960510] [tdb] Close table 'client0.tdb' Apr 26 02:35:05 192.168.122.209 [37856.140079] [tdb] Close table 'sessions0.tdb' Apr 26 02:35:09 192.168.122.209 [37859.313103] [tdb] Close table 'cache0.tdb' Apr 26 02:35:09 192.168.122.209 [37859.547979] [tdb] Close table 'filter0.tdb' Apr 26 02:35:09 192.168.122.209 [37859.548435] [tempesta fw] modules are stopped Apr 26 02:35:09 192.168.122.209 [37859.749311] [tempesta fw] exiting... Apr 26 02:35:09 192.168.122.209 [37859.879382] [tdb] Shutdown Tempesta DB Apr 26 02:35:09 192.168.122.209 [37860.121351] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_then_fresh_req Apr 26 02:35:09 192.168.122.209 [37860.131541] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_then_fresh_resp Apr 26 02:35:11 192.168.122.209 [37861.292724] [tdb] Start Tempesta DB Apr 26 02:35:11 192.168.122.209 [37861.431459] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:35:12 192.168.122.209 [37862.950736] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37862.950736] Maybe that's fine, but it's worth checking the [37862.950736] config - if there is no relations between the [37862.950736] names, then host name confusion attack is possible. Apr 26 02:35:12 192.168.122.209 [37863.033457] [tempesta fw] Configuration processing is completed. Apr 26 02:35:12 192.168.122.209 [37863.083981] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:35:13 192.168.122.209 [37863.507048] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:35:13 192.168.122.209 [37863.533297] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:35:13 192.168.122.209 [37863.559557] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:35:13 192.168.122.209 [37863.605049] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:35:13 192.168.122.209 [37863.645064] [tempesta fw] Tempesta FW is ready Apr 26 02:35:19 192.168.122.209 [37870.214252] [tdb] Close table 'client0.tdb' Apr 26 02:35:20 192.168.122.209 [37870.411687] [tdb] Close table 'sessions0.tdb' Apr 26 02:35:23 192.168.122.209 [37873.565260] [tdb] Close table 'cache0.tdb' Apr 26 02:35:23 192.168.122.209 [37873.803847] [tdb] Close table 'filter0.tdb' Apr 26 02:35:23 192.168.122.209 [37873.804260] [tempesta fw] modules are stopped Apr 26 02:35:23 192.168.122.209 [37873.969456] [tempesta fw] exiting... Apr 26 02:35:23 192.168.122.209 [37874.109924] [tdb] Shutdown Tempesta DB Apr 26 02:35:24 192.168.122.209 [37874.321893] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_then_fresh_resp Apr 26 02:35:24 192.168.122.209 [37874.340447] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_max_stale Apr 26 02:35:25 192.168.122.209 [37875.563451] [tdb] Start Tempesta DB Apr 26 02:35:25 192.168.122.209 [37875.717109] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:35:26 192.168.122.209 [37877.211049] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37877.211049] Maybe that's fine, but it's worth checking the [37877.211049] config - if there is no relations between the [37877.211049] names, then host name confusion attack is possible. Apr 26 02:35:27 192.168.122.209 [37877.317222] [tempesta fw] Configuration processing is completed. Apr 26 02:35:27 192.168.122.209 [37877.366972] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:35:27 192.168.122.209 [37877.806448] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:35:27 192.168.122.209 [37877.832919] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:35:27 192.168.122.209 [37877.859648] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:35:27 192.168.122.209 [37877.921313] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:35:27 192.168.122.209 [37877.961218] [tempesta fw] Tempesta FW is ready Apr 26 02:35:39 192.168.122.209 [37889.592235] [tdb] Close table 'client0.tdb' Apr 26 02:35:39 192.168.122.209 [37889.783953] [tdb] Close table 'sessions0.tdb' Apr 26 02:35:42 192.168.122.209 [37892.913984] [tdb] Close table 'cache0.tdb' Apr 26 02:35:42 192.168.122.209 [37893.173826] [tdb] Close table 'filter0.tdb' Apr 26 02:35:42 192.168.122.209 [37893.174337] [tempesta fw] modules are stopped Apr 26 02:35:43 192.168.122.209 [37893.388834] [tempesta fw] exiting... Apr 26 02:35:43 192.168.122.209 [37893.560962] [tdb] Shutdown Tempesta DB Apr 26 02:35:43 192.168.122.209 [37893.802077] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_max_stale Apr 26 02:35:43 192.168.122.209 [37893.813380] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_stale_if_error_not_use_304 Apr 26 02:35:44 192.168.122.209 [37895.048795] [tdb] Start Tempesta DB Apr 26 02:35:44 192.168.122.209 [37895.209157] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:35:46 192.168.122.209 [37896.783144] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37896.783144] Maybe that's fine, but it's worth checking the [37896.783144] config - if there is no relations between the [37896.783144] names, then host name confusion attack is possible. Apr 26 02:35:46 192.168.122.209 [37896.869802] [tempesta fw] Configuration processing is completed. Apr 26 02:35:46 192.168.122.209 [37896.923960] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:35:47 192.168.122.209 [37897.354239] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:35:47 192.168.122.209 [37897.380723] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:35:47 192.168.122.209 [37897.407227] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:35:47 192.168.122.209 [37897.461525] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:35:47 192.168.122.209 [37897.521461] [tempesta fw] Tempesta FW is ready Apr 26 02:35:49 192.168.122.209 [37900.127935] [tdb] Close table 'client0.tdb' Apr 26 02:35:50 192.168.122.209 [37900.321231] [tdb] Close table 'sessions0.tdb' Apr 26 02:35:53 192.168.122.209 [37903.606132] [tdb] Close table 'cache0.tdb' Apr 26 02:35:53 192.168.122.209 [37903.839944] [tdb] Close table 'filter0.tdb' Apr 26 02:35:53 192.168.122.209 [37903.840388] [tempesta fw] modules are stopped Apr 26 02:35:53 192.168.122.209 [37904.027882] [tempesta fw] exiting... Apr 26 02:35:53 192.168.122.209 [37904.167277] [tdb] Shutdown Tempesta DB Apr 26 02:35:54 192.168.122.209 [37904.424844] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_stale_if_error_not_use_304 Apr 26 02:35:54 192.168.122.209 [37904.438291] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_fresh_200 Apr 26 02:35:55 192.168.122.209 [37905.662379] [tdb] Start Tempesta DB Apr 26 02:35:55 192.168.122.209 [37905.807908] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:35:57 192.168.122.209 [37907.295057] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37907.295057] Maybe that's fine, but it's worth checking the [37907.295057] config - if there is no relations between the [37907.295057] names, then host name confusion attack is possible. Apr 26 02:35:57 192.168.122.209 [37907.401616] [tempesta fw] Configuration processing is completed. Apr 26 02:35:57 192.168.122.209 [37907.450472] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:35:57 192.168.122.209 [37907.924766] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:35:57 192.168.122.209 [37907.953698] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:35:57 192.168.122.209 [37907.982405] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:35:57 192.168.122.209 [37908.049608] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:35:57 192.168.122.209 [37908.093609] [tempesta fw] Tempesta FW is ready Apr 26 02:36:01 192.168.122.209 [37911.711278] [tdb] Close table 'client0.tdb' Apr 26 02:36:01 192.168.122.209 [37911.909835] [tdb] Close table 'sessions0.tdb' Apr 26 02:36:04 192.168.122.209 [37915.227852] [tdb] Close table 'cache0.tdb' Apr 26 02:36:05 192.168.122.209 [37915.483018] [tdb] Close table 'filter0.tdb' Apr 26 02:36:05 192.168.122.209 [37915.483468] [tempesta fw] modules are stopped Apr 26 02:36:05 192.168.122.209 [37915.670810] [tempesta fw] exiting... Apr 26 02:36:05 192.168.122.209 [37915.824129] [tdb] Shutdown Tempesta DB Apr 26 02:36:05 192.168.122.209 [37916.074900] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_fresh_200 Apr 26 02:36:05 192.168.122.209 [37916.098522] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_fresh_403 Apr 26 02:36:07 192.168.122.209 [37917.396024] [tdb] Start Tempesta DB Apr 26 02:36:07 192.168.122.209 [37917.565476] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:36:08 192.168.122.209 [37919.215511] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37919.215511] Maybe that's fine, but it's worth checking the [37919.215511] config - if there is no relations between the [37919.215511] names, then host name confusion attack is possible. Apr 26 02:36:09 192.168.122.209 [37919.317786] [tempesta fw] Configuration processing is completed. Apr 26 02:36:09 192.168.122.209 [37919.380434] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:36:09 192.168.122.209 [37919.821842] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:36:09 192.168.122.209 [37919.851400] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:36:09 192.168.122.209 [37919.878795] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:36:09 192.168.122.209 [37919.921827] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:36:09 192.168.122.209 [37919.961765] [tempesta fw] Tempesta FW is ready Apr 26 02:36:13 192.168.122.209 [37923.537052] [tdb] Close table 'client0.tdb' Apr 26 02:36:13 192.168.122.209 [37923.723593] [tdb] Close table 'sessions0.tdb' Apr 26 02:36:16 192.168.122.209 [37926.888637] [tdb] Close table 'cache0.tdb' Apr 26 02:36:16 192.168.122.209 [37927.139979] [tdb] Close table 'filter0.tdb' Apr 26 02:36:16 192.168.122.209 [37927.140422] [tempesta fw] modules are stopped Apr 26 02:36:17 192.168.122.209 [37927.323745] [tempesta fw] exiting... Apr 26 02:36:17 192.168.122.209 [37927.480542] [tdb] Shutdown Tempesta DB Apr 26 02:36:17 192.168.122.209 [37927.727857] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_fresh_403 Apr 26 02:36:17 192.168.122.209 [37927.745577] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_fresh_on_error_must_revalidate Apr 26 02:36:18 192.168.122.209 [37929.018534] [tdb] Start Tempesta DB Apr 26 02:36:18 192.168.122.209 [37929.158380] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:36:20 192.168.122.209 [37930.631661] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37930.631661] Maybe that's fine, but it's worth checking the [37930.631661] config - if there is no relations between the [37930.631661] names, then host name confusion attack is possible. Apr 26 02:36:20 192.168.122.209 [37930.734239] [tempesta fw] Configuration processing is completed. Apr 26 02:36:20 192.168.122.209 [37930.783498] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:36:20 192.168.122.209 [37931.242396] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:36:20 192.168.122.209 [37931.273126] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:36:21 192.168.122.209 [37931.305067] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:36:21 192.168.122.209 [37931.353942] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:36:21 192.168.122.209 [37931.397898] [tempesta fw] Tempesta FW is ready Apr 26 02:36:24 192.168.122.209 [37935.027637] [tdb] Close table 'client0.tdb' Apr 26 02:36:24 192.168.122.209 [37935.223393] [tdb] Close table 'sessions0.tdb' Apr 26 02:36:28 192.168.122.209 [37938.495788] [tdb] Close table 'cache0.tdb' Apr 26 02:36:28 192.168.122.209 [37938.716322] [tdb] Close table 'filter0.tdb' Apr 26 02:36:28 192.168.122.209 [37938.716803] [tempesta fw] modules are stopped Apr 26 02:36:28 192.168.122.209 [37938.922902] [tempesta fw] exiting... Apr 26 02:36:28 192.168.122.209 [37939.049683] [tdb] Shutdown Tempesta DB Apr 26 02:36:29 192.168.122.209 [37939.307266] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_fresh_on_error_must_revalidate Apr 26 02:36:29 192.168.122.209 [37939.325489] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_fresh_on_error_proxy_revalidate Apr 26 02:36:30 192.168.122.209 [37940.494965] [tdb] Start Tempesta DB Apr 26 02:36:30 192.168.122.209 [37940.650520] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:36:31 192.168.122.209 [37942.211843] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37942.211843] Maybe that's fine, but it's worth checking the [37942.211843] config - if there is no relations between the [37942.211843] names, then host name confusion attack is possible. Apr 26 02:36:32 192.168.122.209 [37942.334069] [tempesta fw] Configuration processing is completed. Apr 26 02:36:32 192.168.122.209 [37942.388151] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:36:32 192.168.122.209 [37942.811122] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:36:32 192.168.122.209 [37942.838030] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:36:32 192.168.122.209 [37942.864178] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:36:32 192.168.122.209 [37942.918104] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:36:32 192.168.122.209 [37942.966501] [tempesta fw] Tempesta FW is ready Apr 26 02:36:36 192.168.122.209 [37946.587161] [tdb] Close table 'client0.tdb' Apr 26 02:36:36 192.168.122.209 [37946.763789] [tdb] Close table 'sessions0.tdb' Apr 26 02:36:39 192.168.122.209 [37949.979659] [tdb] Close table 'cache0.tdb' Apr 26 02:36:39 192.168.122.209 [37950.216997] [tdb] Close table 'filter0.tdb' Apr 26 02:36:39 192.168.122.209 [37950.217418] [tempesta fw] modules are stopped Apr 26 02:36:40 192.168.122.209 [37950.406621] [tempesta fw] exiting... Apr 26 02:36:40 192.168.122.209 [37950.564544] [tdb] Shutdown Tempesta DB Apr 26 02:36:40 192.168.122.209 [37950.772752] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_fresh_on_error_proxy_revalidate Apr 26 02:36:40 192.168.122.209 [37950.790646] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_fresh_on_error_s_maxage Apr 26 02:36:41 192.168.122.209 [37951.983588] [tdb] Start Tempesta DB Apr 26 02:36:41 192.168.122.209 [37952.127352] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:36:43 192.168.122.209 [37953.655901] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37953.655901] Maybe that's fine, but it's worth checking the [37953.655901] config - if there is no relations between the [37953.655901] names, then host name confusion attack is possible. Apr 26 02:36:43 192.168.122.209 [37953.762597] [tempesta fw] Configuration processing is completed. Apr 26 02:36:43 192.168.122.209 [37953.812002] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:36:43 192.168.122.209 [37954.241912] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:36:43 192.168.122.209 [37954.268260] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:36:44 192.168.122.209 [37954.295198] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:36:44 192.168.122.209 [37954.338282] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:36:44 192.168.122.209 [37954.378189] [tempesta fw] Tempesta FW is ready Apr 26 02:36:47 192.168.122.209 [37958.041379] [tdb] Close table 'client0.tdb' Apr 26 02:36:47 192.168.122.209 [37958.230872] [tdb] Close table 'sessions0.tdb' Apr 26 02:36:51 192.168.122.209 [37961.403851] [tdb] Close table 'cache0.tdb' Apr 26 02:36:51 192.168.122.209 [37961.649692] [tdb] Close table 'filter0.tdb' Apr 26 02:36:51 192.168.122.209 [37961.650159] [tempesta fw] modules are stopped Apr 26 02:36:51 192.168.122.209 [37961.828257] [tempesta fw] exiting... Apr 26 02:36:51 192.168.122.209 [37961.992800] [tdb] Shutdown Tempesta DB Apr 26 02:36:51 192.168.122.209 [37962.227256] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_fresh_on_error_s_maxage Apr 26 02:36:51 192.168.122.209 [37962.243847] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_400 Apr 26 02:36:53 192.168.122.209 [37963.427724] [tdb] Start Tempesta DB Apr 26 02:36:53 192.168.122.209 [37963.569852] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:36:54 192.168.122.209 [37965.064027] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37965.064027] Maybe that's fine, but it's worth checking the [37965.064027] config - if there is no relations between the [37965.064027] names, then host name confusion attack is possible. Apr 26 02:36:54 192.168.122.209 [37965.170681] [tempesta fw] Configuration processing is completed. Apr 26 02:36:54 192.168.122.209 [37965.225099] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:36:55 192.168.122.209 [37965.653119] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:36:55 192.168.122.209 [37965.678819] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:36:55 192.168.122.209 [37965.704829] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:36:55 192.168.122.209 [37965.778399] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:36:55 192.168.122.209 [37965.818350] [tempesta fw] Tempesta FW is ready Apr 26 02:36:59 192.168.122.209 [37969.406540] [tdb] Close table 'client0.tdb' Apr 26 02:36:59 192.168.122.209 [37969.594727] [tdb] Close table 'sessions0.tdb' Apr 26 02:37:02 192.168.122.209 [37972.790516] [tdb] Close table 'cache0.tdb' Apr 26 02:37:02 192.168.122.209 [37973.035339] [tdb] Close table 'filter0.tdb' Apr 26 02:37:02 192.168.122.209 [37973.035771] [tempesta fw] modules are stopped Apr 26 02:37:02 192.168.122.209 [37973.207249] [tempesta fw] exiting... Apr 26 02:37:03 192.168.122.209 [37973.354532] [tdb] Shutdown Tempesta DB Apr 26 02:37:03 192.168.122.209 [37973.582476] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_400 Apr 26 02:37:03 192.168.122.209 [37973.612866] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_4xx_400 Apr 26 02:37:04 192.168.122.209 [37974.717897] [tdb] Start Tempesta DB Apr 26 02:37:04 192.168.122.209 [37974.860746] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:37:06 192.168.122.209 [37976.343504] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37976.343504] Maybe that's fine, but it's worth checking the [37976.343504] config - if there is no relations between the [37976.343504] names, then host name confusion attack is possible. Apr 26 02:37:06 192.168.122.209 [37976.442527] [tempesta fw] Configuration processing is completed. Apr 26 02:37:06 192.168.122.209 [37976.488155] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:37:06 192.168.122.209 [37976.916337] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:37:06 192.168.122.209 [37976.942061] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:37:06 192.168.122.209 [37976.973978] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:37:06 192.168.122.209 [37977.022549] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:37:06 192.168.122.209 [37977.062492] [tempesta fw] Tempesta FW is ready Apr 26 02:37:10 192.168.122.209 [37980.684936] [tdb] Close table 'client0.tdb' Apr 26 02:37:10 192.168.122.209 [37980.877927] [tdb] Close table 'sessions0.tdb' Apr 26 02:37:13 192.168.122.209 [37984.041744] [tdb] Close table 'cache0.tdb' Apr 26 02:37:13 192.168.122.209 [37984.282634] [tdb] Close table 'filter0.tdb' Apr 26 02:37:13 192.168.122.209 [37984.283055] [tempesta fw] modules are stopped Apr 26 02:37:14 192.168.122.209 [37984.451212] [tempesta fw] exiting... Apr 26 02:37:14 192.168.122.209 [37984.603546] [tdb] Shutdown Tempesta DB Apr 26 02:37:14 192.168.122.209 [37984.849642] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_4xx_400 Apr 26 02:37:14 192.168.122.209 [37984.874503] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_4xx_403 Apr 26 02:37:15 192.168.122.209 [37986.064448] [tdb] Start Tempesta DB Apr 26 02:37:15 192.168.122.209 [37986.211107] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:37:17 192.168.122.209 [37987.656326] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37987.656326] Maybe that's fine, but it's worth checking the [37987.656326] config - if there is no relations between the [37987.656326] names, then host name confusion attack is possible. Apr 26 02:37:17 192.168.122.209 [37987.743055] [tempesta fw] Configuration processing is completed. Apr 26 02:37:17 192.168.122.209 [37987.795969] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:37:17 192.168.122.209 [37988.211184] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:37:17 192.168.122.209 [37988.242352] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:37:17 192.168.122.209 [37988.268333] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:37:18 192.168.122.209 [37988.354646] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:37:18 192.168.122.209 [37988.390628] [tempesta fw] Tempesta FW is ready Apr 26 02:37:21 192.168.122.209 [37991.982496] [tdb] Close table 'client0.tdb' Apr 26 02:37:21 192.168.122.209 [37992.155776] [tdb] Close table 'sessions0.tdb' Apr 26 02:37:25 192.168.122.209 [37995.362837] [tdb] Close table 'cache0.tdb' Apr 26 02:37:25 192.168.122.209 [37995.611421] [tdb] Close table 'filter0.tdb' Apr 26 02:37:25 192.168.122.209 [37995.611855] [tempesta fw] modules are stopped Apr 26 02:37:25 192.168.122.209 [37995.839148] [tempesta fw] exiting... Apr 26 02:37:25 192.168.122.209 [37995.985262] [tdb] Shutdown Tempesta DB Apr 26 02:37:25 192.168.122.209 [37996.189160] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_4xx_403 Apr 26 02:37:25 192.168.122.209 [37996.214170] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_4xx_5xx Apr 26 02:37:27 192.168.122.209 [37997.333454] [tdb] Start Tempesta DB Apr 26 02:37:27 192.168.122.209 [37997.485941] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:37:28 192.168.122.209 [37998.924493] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [37998.924493] Maybe that's fine, but it's worth checking the [37998.924493] config - if there is no relations between the [37998.924493] names, then host name confusion attack is possible. Apr 26 02:37:28 192.168.122.209 [37999.023189] [tempesta fw] Configuration processing is completed. Apr 26 02:37:28 192.168.122.209 [37999.072651] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:37:29 192.168.122.209 [37999.499903] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:37:29 192.168.122.209 [37999.526511] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:37:29 192.168.122.209 [37999.553303] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:37:29 192.168.122.209 [37999.598836] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:37:29 192.168.122.209 [37999.646769] [tempesta fw] Tempesta FW is ready Apr 26 02:37:32 192.168.122.209 [38003.196889] [tdb] Close table 'client0.tdb' Apr 26 02:37:33 192.168.122.209 [38003.406700] [tdb] Close table 'sessions0.tdb' Apr 26 02:37:36 192.168.122.209 [38006.568537] [tdb] Close table 'cache0.tdb' Apr 26 02:37:36 192.168.122.209 [38006.794093] [tdb] Close table 'filter0.tdb' Apr 26 02:37:36 192.168.122.209 [38006.794505] [tempesta fw] modules are stopped Apr 26 02:37:36 192.168.122.209 [38006.995217] [tempesta fw] exiting... Apr 26 02:37:36 192.168.122.209 [38007.136213] [tdb] Shutdown Tempesta DB Apr 26 02:37:37 192.168.122.209 [38007.363406] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_4xx_5xx Apr 26 02:37:37 192.168.122.209 [38007.387076] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_500 Apr 26 02:37:38 192.168.122.209 [38008.560247] [tdb] Start Tempesta DB Apr 26 02:37:38 192.168.122.209 [38008.703024] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:37:39 192.168.122.209 [38010.212646] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38010.212646] Maybe that's fine, but it's worth checking the [38010.212646] config - if there is no relations between the [38010.212646] names, then host name confusion attack is possible. Apr 26 02:37:40 192.168.122.209 [38010.315348] [tempesta fw] Configuration processing is completed. Apr 26 02:37:40 192.168.122.209 [38010.366139] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:37:40 192.168.122.209 [38010.783974] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:37:40 192.168.122.209 [38010.810848] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:37:40 192.168.122.209 [38010.837878] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:37:40 192.168.122.209 [38010.882980] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:37:40 192.168.122.209 [38010.922946] [tempesta fw] Tempesta FW is ready Apr 26 02:37:44 192.168.122.209 [38014.483855] [tdb] Close table 'client0.tdb' Apr 26 02:37:44 192.168.122.209 [38014.691405] [tdb] Close table 'sessions0.tdb' Apr 26 02:37:47 192.168.122.209 [38017.872847] [tdb] Close table 'cache0.tdb' Apr 26 02:37:47 192.168.122.209 [38018.093773] [tdb] Close table 'filter0.tdb' Apr 26 02:37:47 192.168.122.209 [38018.094218] [tempesta fw] modules are stopped Apr 26 02:37:48 192.168.122.209 [38018.291032] [tempesta fw] exiting... Apr 26 02:37:48 192.168.122.209 [38018.447805] [tdb] Shutdown Tempesta DB Apr 26 02:37:48 192.168.122.209 [38018.670088] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_500 Apr 26 02:37:48 192.168.122.209 [38018.705047] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_5xx_500 Apr 26 02:37:49 192.168.122.209 [38019.915641] [tdb] Start Tempesta DB Apr 26 02:37:49 192.168.122.209 [38020.063243] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:37:51 192.168.122.209 [38021.532804] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38021.532804] Maybe that's fine, but it's worth checking the [38021.532804] config - if there is no relations between the [38021.532804] names, then host name confusion attack is possible. Apr 26 02:37:51 192.168.122.209 [38021.627427] [tempesta fw] Configuration processing is completed. Apr 26 02:37:51 192.168.122.209 [38021.677241] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:37:51 192.168.122.209 [38022.096843] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:37:51 192.168.122.209 [38022.122541] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:37:51 192.168.122.209 [38022.148497] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:37:51 192.168.122.209 [38022.207122] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:37:51 192.168.122.209 [38022.255059] [tempesta fw] Tempesta FW is ready Apr 26 02:37:55 192.168.122.209 [38025.835577] [tdb] Close table 'client0.tdb' Apr 26 02:37:55 192.168.122.209 [38026.020492] [tdb] Close table 'sessions0.tdb' Apr 26 02:37:58 192.168.122.209 [38029.172990] [tdb] Close table 'cache0.tdb' Apr 26 02:37:59 192.168.122.209 [38029.416193] [tdb] Close table 'filter0.tdb' Apr 26 02:37:59 192.168.122.209 [38029.416643] [tempesta fw] modules are stopped Apr 26 02:37:59 192.168.122.209 [38029.607663] [tempesta fw] exiting... Apr 26 02:37:59 192.168.122.209 [38029.731368] [tdb] Shutdown Tempesta DB Apr 26 02:37:59 192.168.122.209 [38029.933479] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_5xx_500 Apr 26 02:37:59 192.168.122.209 [38029.960530] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_5xx_502 Apr 26 02:38:00 192.168.122.209 [38031.111590] [tdb] Start Tempesta DB Apr 26 02:38:00 192.168.122.209 [38031.270221] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:38:02 192.168.122.209 [38032.797010] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38032.797010] Maybe that's fine, but it's worth checking the [38032.797010] config - if there is no relations between the [38032.797010] names, then host name confusion attack is possible. Apr 26 02:38:02 192.168.122.209 [38032.891535] [tempesta fw] Configuration processing is completed. Apr 26 02:38:02 192.168.122.209 [38032.943552] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:38:03 192.168.122.209 [38033.367862] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:38:03 192.168.122.209 [38033.394216] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:38:03 192.168.122.209 [38033.421000] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:38:03 192.168.122.209 [38033.459257] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:38:03 192.168.122.209 [38033.519229] [tempesta fw] Tempesta FW is ready Apr 26 02:38:06 192.168.122.209 [38037.091665] [tdb] Close table 'client0.tdb' Apr 26 02:38:06 192.168.122.209 [38037.277678] [tdb] Close table 'sessions0.tdb' Apr 26 02:38:10 192.168.122.209 [38040.378491] [tdb] Close table 'cache0.tdb' Apr 26 02:38:10 192.168.122.209 [38040.632889] [tdb] Close table 'filter0.tdb' Apr 26 02:38:10 192.168.122.209 [38040.633321] [tempesta fw] modules are stopped Apr 26 02:38:10 192.168.122.209 [38040.813473] [tempesta fw] exiting... Apr 26 02:38:10 192.168.122.209 [38040.952579] [tdb] Shutdown Tempesta DB Apr 26 02:38:10 192.168.122.209 [38041.174346] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_5xx_502 Apr 26 02:38:10 192.168.122.209 [38041.190868] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_if_error_duplicated_req Apr 26 02:38:12 192.168.122.209 [38042.363495] [tdb] Start Tempesta DB Apr 26 02:38:12 192.168.122.209 [38042.508954] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:38:13 192.168.122.209 [38043.933082] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38043.933082] Maybe that's fine, but it's worth checking the [38043.933082] config - if there is no relations between the [38043.933082] names, then host name confusion attack is possible. Apr 26 02:38:13 192.168.122.209 [38044.011381] [tempesta fw] Configuration processing is completed. Apr 26 02:38:13 192.168.122.209 [38044.076843] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:38:14 192.168.122.209 [38044.501090] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:38:14 192.168.122.209 [38044.526642] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:38:14 192.168.122.209 [38044.552336] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:38:14 192.168.122.209 [38044.591403] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:38:14 192.168.122.209 [38044.639294] [tempesta fw] Tempesta FW is ready Apr 26 02:38:14 192.168.122.209 [38045.255108] [tdb] Close table 'client0.tdb' Apr 26 02:38:15 192.168.122.209 [38045.444173] [tdb] Close table 'sessions0.tdb' Apr 26 02:38:18 192.168.122.209 [38048.611140] [tdb] Close table 'cache0.tdb' Apr 26 02:38:18 192.168.122.209 [38048.874027] [tdb] Close table 'filter0.tdb' Apr 26 02:38:18 192.168.122.209 [38048.874453] [tempesta fw] modules are stopped Apr 26 02:38:18 192.168.122.209 [38049.056807] [tempesta fw] exiting... Apr 26 02:38:18 192.168.122.209 [38049.211150] [tdb] Shutdown Tempesta DB Apr 26 02:38:19 192.168.122.209 [38049.452380] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_if_error_duplicated_req Apr 26 02:38:19 192.168.122.209 [38049.464959] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_if_error_duplicated_resp Apr 26 02:38:20 192.168.122.209 [38050.675991] [tdb] Start Tempesta DB Apr 26 02:38:20 192.168.122.209 [38050.826763] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:38:22 192.168.122.209 [38052.285139] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38052.285139] Maybe that's fine, but it's worth checking the [38052.285139] config - if there is no relations between the [38052.285139] names, then host name confusion attack is possible. Apr 26 02:38:22 192.168.122.209 [38052.355796] [tempesta fw] Configuration processing is completed. Apr 26 02:38:22 192.168.122.209 [38052.406920] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:38:22 192.168.122.209 [38052.816842] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:38:22 192.168.122.209 [38052.842675] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:38:22 192.168.122.209 [38052.868998] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:38:22 192.168.122.209 [38052.907463] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:38:22 192.168.122.209 [38052.947417] [tempesta fw] Tempesta FW is ready Apr 26 02:38:22 192.168.122.209 [38053.084786] [tempesta fw] Warning: Parser error: state=Resp_HdrCache_CtrlV input(-8)=0x73('ontrol: stale-if-error=20, stale-if-error=19 [38053.084786] da') data_len=128 off=51 Apr 26 02:38:22 192.168.122.209 [38053.086142] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 02:38:23 192.168.122.209 [38053.525687] [tdb] Close table 'client0.tdb' Apr 26 02:38:23 192.168.122.209 [38053.728240] [tdb] Close table 'sessions0.tdb' Apr 26 02:38:26 192.168.122.209 [38056.859918] [tdb] Close table 'cache0.tdb' Apr 26 02:38:26 192.168.122.209 [38057.112436] [tdb] Close table 'filter0.tdb' Apr 26 02:38:26 192.168.122.209 [38057.112872] [tempesta fw] modules are stopped Apr 26 02:38:26 192.168.122.209 [38057.280236] [tempesta fw] exiting... Apr 26 02:38:27 192.168.122.209 [38057.417344] [tdb] Shutdown Tempesta DB Apr 26 02:38:27 192.168.122.209 [38057.630858] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_if_error_duplicated_resp Apr 26 02:38:27 192.168.122.209 [38057.653946] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_if_error_param_req Apr 26 02:38:28 192.168.122.209 [38058.792646] [tdb] Start Tempesta DB Apr 26 02:38:28 192.168.122.209 [38058.936806] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:38:30 192.168.122.209 [38060.361306] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38060.361306] Maybe that's fine, but it's worth checking the [38060.361306] config - if there is no relations between the [38060.361306] names, then host name confusion attack is possible. Apr 26 02:38:30 192.168.122.209 [38060.443919] [tempesta fw] Configuration processing is completed. Apr 26 02:38:30 192.168.122.209 [38060.492536] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:38:30 192.168.122.209 [38060.920404] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:38:30 192.168.122.209 [38060.947055] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:38:30 192.168.122.209 [38060.973929] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:38:30 192.168.122.209 [38061.019618] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:38:30 192.168.122.209 [38061.059593] [tempesta fw] Tempesta FW is ready Apr 26 02:38:34 192.168.122.209 [38064.709255] [tdb] Close table 'client0.tdb' Apr 26 02:38:34 192.168.122.209 [38064.897915] [tdb] Close table 'sessions0.tdb' Apr 26 02:38:37 192.168.122.209 [38068.041465] [tdb] Close table 'cache0.tdb' Apr 26 02:38:37 192.168.122.209 [38068.281580] [tdb] Close table 'filter0.tdb' Apr 26 02:38:37 192.168.122.209 [38068.282002] [tempesta fw] modules are stopped Apr 26 02:38:38 192.168.122.209 [38068.463362] [tempesta fw] exiting... Apr 26 02:38:38 192.168.122.209 [38068.627142] [tdb] Shutdown Tempesta DB Apr 26 02:38:38 192.168.122.209 [38068.866893] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_if_error_param_req Apr 26 02:38:38 192.168.122.209 [38068.882134] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_if_error_param_resp Apr 26 02:38:39 192.168.122.209 [38070.047050] [tdb] Start Tempesta DB Apr 26 02:38:39 192.168.122.209 [38070.195997] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:38:41 192.168.122.209 [38071.661424] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38071.661424] Maybe that's fine, but it's worth checking the [38071.661424] config - if there is no relations between the [38071.661424] names, then host name confusion attack is possible. Apr 26 02:38:41 192.168.122.209 [38071.736130] [tempesta fw] Configuration processing is completed. Apr 26 02:38:41 192.168.122.209 [38071.792819] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:38:41 192.168.122.209 [38072.208953] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:38:41 192.168.122.209 [38072.234404] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:38:41 192.168.122.209 [38072.260316] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:38:42 192.168.122.209 [38072.299759] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:38:42 192.168.122.209 [38072.347732] [tempesta fw] Tempesta FW is ready Apr 26 02:38:45 192.168.122.209 [38076.026850] [tdb] Close table 'client0.tdb' Apr 26 02:38:45 192.168.122.209 [38076.213467] [tdb] Close table 'sessions0.tdb' Apr 26 02:38:49 192.168.122.209 [38079.389065] [tdb] Close table 'cache0.tdb' Apr 26 02:38:49 192.168.122.209 [38079.639329] [tdb] Close table 'filter0.tdb' Apr 26 02:38:49 192.168.122.209 [38079.639797] [tempesta fw] modules are stopped Apr 26 02:38:49 192.168.122.209 [38079.814970] [tempesta fw] exiting... Apr 26 02:38:49 192.168.122.209 [38079.962764] [tdb] Shutdown Tempesta DB Apr 26 02:38:49 192.168.122.209 [38080.239266] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_if_error_param_resp Apr 26 02:38:49 192.168.122.209 [38080.259170] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_invalid_response Apr 26 02:38:51 192.168.122.209 [38081.561210] [tdb] Start Tempesta DB Apr 26 02:38:51 192.168.122.209 [38081.703408] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:38:52 192.168.122.209 [38083.153538] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38083.153538] Maybe that's fine, but it's worth checking the [38083.153538] config - if there is no relations between the [38083.153538] names, then host name confusion attack is possible. Apr 26 02:38:52 192.168.122.209 [38083.263877] [tempesta fw] Configuration processing is completed. Apr 26 02:38:53 192.168.122.209 [38083.313669] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:38:53 192.168.122.209 [38083.748950] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:38:53 192.168.122.209 [38083.775767] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:38:53 192.168.122.209 [38083.801946] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:38:53 192.168.122.209 [38083.843925] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:38:53 192.168.122.209 [38083.891790] [tempesta fw] Tempesta FW is ready Apr 26 02:38:56 192.168.122.209 [38087.052834] [tempesta fw] Warning: Parser error: state=RGen_HdrOtherN input(-8)=0x68('gth: 0 [38087.052834] hd>r: v [38087.052834] date: Sat, 26 Apr 2025 02:38:56') data_len=91 off=43 Apr 26 02:38:57 192.168.122.209 [38087.496827] [tdb] Close table 'client0.tdb' Apr 26 02:38:57 192.168.122.209 [38087.681404] [tdb] Close table 'sessions0.tdb' Apr 26 02:39:00 192.168.122.209 [38090.839130] [tdb] Close table 'cache0.tdb' Apr 26 02:39:00 192.168.122.209 [38091.049707] [tdb] Close table 'filter0.tdb' Apr 26 02:39:00 192.168.122.209 [38091.050155] [tempesta fw] modules are stopped Apr 26 02:39:01 192.168.122.209 [38091.305836] [tempesta fw] exiting... Apr 26 02:39:01 192.168.122.209 [38091.445164] [tdb] Shutdown Tempesta DB Apr 26 02:39:01 192.168.122.209 [38091.661863] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_invalid_response Apr 26 02:39:01 192.168.122.209 [38091.703714] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_then_fresh_req Apr 26 02:39:02 192.168.122.209 [38092.867443] [tdb] Start Tempesta DB Apr 26 02:39:02 192.168.122.209 [38093.027760] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:39:04 192.168.122.209 [38094.441700] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38094.441700] Maybe that's fine, but it's worth checking the [38094.441700] config - if there is no relations between the [38094.441700] names, then host name confusion attack is possible. Apr 26 02:39:04 192.168.122.209 [38094.524337] [tempesta fw] Configuration processing is completed. Apr 26 02:39:04 192.168.122.209 [38094.574743] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:39:04 192.168.122.209 [38094.986178] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:39:04 192.168.122.209 [38095.020714] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:39:04 192.168.122.209 [38095.046610] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:39:04 192.168.122.209 [38095.096046] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:39:04 192.168.122.209 [38095.152005] [tempesta fw] Tempesta FW is ready Apr 26 02:39:11 192.168.122.209 [38101.761353] [tdb] Close table 'client0.tdb' Apr 26 02:39:11 192.168.122.209 [38101.941569] [tdb] Close table 'sessions0.tdb' Apr 26 02:39:14 192.168.122.209 [38105.145018] [tdb] Close table 'cache0.tdb' Apr 26 02:39:15 192.168.122.209 [38105.380684] [tdb] Close table 'filter0.tdb' Apr 26 02:39:15 192.168.122.209 [38105.381137] [tempesta fw] modules are stopped Apr 26 02:39:15 192.168.122.209 [38105.605690] [tempesta fw] exiting... Apr 26 02:39:15 192.168.122.209 [38105.786324] [tdb] Shutdown Tempesta DB Apr 26 02:39:15 192.168.122.209 [38105.997554] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_then_fresh_req Apr 26 02:39:15 192.168.122.209 [38106.016190] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_then_fresh_resp Apr 26 02:39:16 192.168.122.209 [38107.201466] [tdb] Start Tempesta DB Apr 26 02:39:17 192.168.122.209 [38107.347602] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:39:18 192.168.122.209 [38108.865859] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38108.865859] Maybe that's fine, but it's worth checking the [38108.865859] config - if there is no relations between the [38108.865859] names, then host name confusion attack is possible. Apr 26 02:39:18 192.168.122.209 [38108.972403] [tempesta fw] Configuration processing is completed. Apr 26 02:39:18 192.168.122.209 [38109.025885] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:39:19 192.168.122.209 [38109.439684] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:39:19 192.168.122.209 [38109.465127] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:39:19 192.168.122.209 [38109.490357] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:39:19 192.168.122.209 [38109.556244] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:39:19 192.168.122.209 [38109.604224] [tempesta fw] Tempesta FW is ready Apr 26 02:39:25 192.168.122.209 [38116.217361] [tdb] Close table 'client0.tdb' Apr 26 02:39:26 192.168.122.209 [38116.411921] [tdb] Close table 'sessions0.tdb' Apr 26 02:39:29 192.168.122.209 [38119.590536] [tdb] Close table 'cache0.tdb' Apr 26 02:39:29 192.168.122.209 [38119.856021] [tdb] Close table 'filter0.tdb' Apr 26 02:39:29 192.168.122.209 [38119.856455] [tempesta fw] modules are stopped Apr 26 02:39:29 192.168.122.209 [38120.024129] [tempesta fw] exiting... Apr 26 02:39:29 192.168.122.209 [38120.163619] [tdb] Shutdown Tempesta DB Apr 26 02:39:30 192.168.122.209 [38120.412723] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_then_fresh_resp Apr 26 02:39:30 192.168.122.209 [38120.430426] Start test: cache.test_cache_stale.TestCacheUseStaleTimeoutH2.test_timeout_no_stale Apr 26 02:39:31 192.168.122.209 [38121.664593] [tdb] Start Tempesta DB Apr 26 02:39:31 192.168.122.209 [38121.815674] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:39:33 192.168.122.209 [38123.322051] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38123.322051] Maybe that's fine, but it's worth checking the [38123.322051] config - if there is no relations between the [38123.322051] names, then host name confusion attack is possible. Apr 26 02:39:33 192.168.122.209 [38123.416700] [tempesta fw] Configuration processing is completed. Apr 26 02:39:33 192.168.122.209 [38123.466398] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:39:33 192.168.122.209 [38123.879359] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:39:33 192.168.122.209 [38123.905150] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:39:33 192.168.122.209 [38123.931291] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:39:33 192.168.122.209 [38123.980345] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:39:33 192.168.122.209 [38124.024365] [tempesta fw] Tempesta FW is ready Apr 26 02:39:36 192.168.122.209 [38127.232568] [tempesta fw] Warning: request evicted: the number of retries exceeded, status 504: 127.0.0.2 Apr 26 02:39:37 192.168.122.209 [38127.660527] [tdb] Close table 'client0.tdb' Apr 26 02:39:37 192.168.122.209 [38127.863154] [tdb] Close table 'sessions0.tdb' Apr 26 02:39:40 192.168.122.209 [38131.085377] [tdb] Close table 'cache0.tdb' Apr 26 02:39:41 192.168.122.209 [38131.331741] [tdb] Close table 'filter0.tdb' Apr 26 02:39:41 192.168.122.209 [38131.332197] [tempesta fw] modules are stopped Apr 26 02:39:41 192.168.122.209 [38131.503131] [tempesta fw] exiting... Apr 26 02:39:41 192.168.122.209 [38131.691249] [tdb] Shutdown Tempesta DB Apr 26 02:39:41 192.168.122.209 [38131.918077] End test: cache.test_cache_stale.TestCacheUseStaleTimeoutH2.test_timeout_no_stale Apr 26 02:39:41 192.168.122.209 [38131.931753] Start test: cache.test_cache_stale.TestCacheUseStaleTimeoutH2.test_use_stale_timeout Apr 26 02:39:42 192.168.122.209 [38133.087827] [tdb] Start Tempesta DB Apr 26 02:39:42 192.168.122.209 [38133.240279] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:39:44 192.168.122.209 [38134.762241] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38134.762241] Maybe that's fine, but it's worth checking the [38134.762241] config - if there is no relations between the [38134.762241] names, then host name confusion attack is possible. Apr 26 02:39:44 192.168.122.209 [38134.868861] [tempesta fw] Configuration processing is completed. Apr 26 02:39:44 192.168.122.209 [38134.929285] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:39:45 192.168.122.209 [38135.348970] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:39:45 192.168.122.209 [38135.375159] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:39:45 192.168.122.209 [38135.401231] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:39:45 192.168.122.209 [38135.452581] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:39:45 192.168.122.209 [38135.504553] [tempesta fw] Tempesta FW is ready Apr 26 02:39:48 192.168.122.209 [38138.725020] [tempesta fw] Warning: request evicted: the number of retries exceeded, status 504: 127.0.0.2 Apr 26 02:39:48 192.168.122.209 [38139.168936] [tdb] Close table 'client0.tdb' Apr 26 02:39:49 192.168.122.209 [38139.354721] [tdb] Close table 'sessions0.tdb' Apr 26 02:39:52 192.168.122.209 [38142.527166] [tdb] Close table 'cache0.tdb' Apr 26 02:39:52 192.168.122.209 [38142.757770] [tdb] Close table 'filter0.tdb' Apr 26 02:39:52 192.168.122.209 [38142.758242] [tempesta fw] modules are stopped Apr 26 02:39:52 192.168.122.209 [38142.941714] [tempesta fw] exiting... Apr 26 02:39:52 192.168.122.209 [38143.078331] [tdb] Shutdown Tempesta DB Apr 26 02:39:53 192.168.122.209 [38143.338573] End test: cache.test_cache_stale.TestCacheUseStaleTimeoutH2.test_use_stale_timeout Apr 26 02:39:53 192.168.122.209 [38143.349670] Start test: cache.test_cache_stale.TestCacheUseStaleTimeoutHttp.test_timeout_no_stale Apr 26 02:39:54 192.168.122.209 [38144.543698] [tdb] Start Tempesta DB Apr 26 02:39:54 192.168.122.209 [38144.683722] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:39:55 192.168.122.209 [38146.110293] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38146.110293] Maybe that's fine, but it's worth checking the [38146.110293] config - if there is no relations between the [38146.110293] names, then host name confusion attack is possible. Apr 26 02:39:55 192.168.122.209 [38146.209010] [tempesta fw] Configuration processing is completed. Apr 26 02:39:55 192.168.122.209 [38146.262229] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:39:56 192.168.122.209 [38146.683305] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:39:56 192.168.122.209 [38146.709009] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:39:56 192.168.122.209 [38146.735040] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:39:56 192.168.122.209 [38146.784713] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:39:56 192.168.122.209 [38146.832675] [tempesta fw] Tempesta FW is ready Apr 26 02:39:59 192.168.122.209 [38150.044894] [tempesta fw] Warning: request evicted: the number of retries exceeded, status 504: 127.0.0.2 Apr 26 02:40:00 192.168.122.209 [38150.437994] [tdb] Close table 'client0.tdb' Apr 26 02:40:00 192.168.122.209 [38150.650420] [tdb] Close table 'sessions0.tdb' Apr 26 02:40:03 192.168.122.209 [38153.823434] [tdb] Close table 'cache0.tdb' Apr 26 02:40:03 192.168.122.209 [38154.083784] [tdb] Close table 'filter0.tdb' Apr 26 02:40:03 192.168.122.209 [38154.084211] [tempesta fw] modules are stopped Apr 26 02:40:04 192.168.122.209 [38154.324908] [tempesta fw] exiting... Apr 26 02:40:04 192.168.122.209 [38154.476021] [tdb] Shutdown Tempesta DB Apr 26 02:40:04 192.168.122.209 [38154.716642] End test: cache.test_cache_stale.TestCacheUseStaleTimeoutHttp.test_timeout_no_stale Apr 26 02:40:04 192.168.122.209 [38154.748160] Start test: cache.test_cache_stale.TestCacheUseStaleTimeoutHttp.test_use_stale_timeout Apr 26 02:40:05 192.168.122.209 [38155.913523] [tdb] Start Tempesta DB Apr 26 02:40:05 192.168.122.209 [38156.054001] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:40:07 192.168.122.209 [38157.598502] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38157.598502] Maybe that's fine, but it's worth checking the [38157.598502] config - if there is no relations between the [38157.598502] names, then host name confusion attack is possible. Apr 26 02:40:07 192.168.122.209 [38157.693233] [tempesta fw] Configuration processing is completed. Apr 26 02:40:07 192.168.122.209 [38157.746452] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:40:07 192.168.122.209 [38158.171359] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:40:07 192.168.122.209 [38158.197739] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:40:07 192.168.122.209 [38158.224095] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:40:08 192.168.122.209 [38158.288862] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:40:08 192.168.122.209 [38158.332814] [tempesta fw] Tempesta FW is ready Apr 26 02:40:11 192.168.122.209 [38161.544997] [tempesta fw] Warning: request evicted: the number of retries exceeded, status 504: 127.0.0.2 Apr 26 02:40:11 192.168.122.209 [38161.966905] [tdb] Close table 'client0.tdb' Apr 26 02:40:11 192.168.122.209 [38162.156216] [tdb] Close table 'sessions0.tdb' Apr 26 02:40:15 192.168.122.209 [38165.422128] [tdb] Close table 'cache0.tdb' Apr 26 02:40:15 192.168.122.209 [38165.677666] [tdb] Close table 'filter0.tdb' Apr 26 02:40:15 192.168.122.209 [38165.678102] [tempesta fw] modules are stopped Apr 26 02:40:15 192.168.122.209 [38165.864184] [tempesta fw] exiting... Apr 26 02:40:15 192.168.122.209 [38166.001908] [tdb] Shutdown Tempesta DB Apr 26 02:40:15 192.168.122.209 [38166.216613] End test: cache.test_cache_stale.TestCacheUseStaleTimeoutHttp.test_use_stale_timeout Apr 26 02:40:15 192.168.122.209 [38166.234281] Start test: cache.test_conditional.TestConditionalH2.test_correct_none_match_and_modified_since Apr 26 02:40:17 192.168.122.209 [38167.406102] [tdb] Start Tempesta DB Apr 26 02:40:17 192.168.122.209 [38167.550105] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:40:18 192.168.122.209 [38168.998287] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38168.998287] Maybe that's fine, but it's worth checking the [38168.998287] config - if there is no relations between the [38168.998287] names, then host name confusion attack is possible. Apr 26 02:40:18 192.168.122.209 [38169.129042] [tempesta fw] Configuration processing is completed. Apr 26 02:40:18 192.168.122.209 [38169.182313] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:40:19 192.168.122.209 [38169.602244] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:40:19 192.168.122.209 [38169.628532] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:40:19 192.168.122.209 [38169.654763] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:40:19 192.168.122.209 [38169.693012] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:40:19 192.168.122.209 [38169.694636] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:40:19 192.168.122.209 [38169.732957] [tempesta fw] Tempesta FW is ready Apr 26 02:40:20 192.168.122.209 [38170.361667] [tdb] Close table 'client0.tdb' Apr 26 02:40:20 192.168.122.209 [38170.580033] [tdb] Close table 'sessions0.tdb' Apr 26 02:40:23 192.168.122.209 [38173.740617] [tdb] Close table 'cache0.tdb' Apr 26 02:40:23 192.168.122.209 [38173.992577] [tdb] Close table 'filter0.tdb' Apr 26 02:40:23 192.168.122.209 [38173.993042] [tempesta fw] modules are stopped Apr 26 02:40:23 192.168.122.209 [38174.182477] [tempesta fw] exiting... Apr 26 02:40:24 192.168.122.209 [38174.328181] [tdb] Shutdown Tempesta DB Apr 26 02:40:24 192.168.122.209 [38174.560418] End test: cache.test_conditional.TestConditionalH2.test_correct_none_match_and_modified_since Apr 26 02:40:24 192.168.122.209 [38174.571193] Start test: cache.test_conditional.TestConditionalH2.test_incorrect_none_match_and_correct_modified_since Apr 26 02:40:25 192.168.122.209 [38175.790723] [tdb] Start Tempesta DB Apr 26 02:40:25 192.168.122.209 [38175.920470] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:40:27 192.168.122.209 [38177.378012] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38177.378012] Maybe that's fine, but it's worth checking the [38177.378012] config - if there is no relations between the [38177.378012] names, then host name confusion attack is possible. Apr 26 02:40:27 192.168.122.209 [38177.509404] [tempesta fw] Configuration processing is completed. Apr 26 02:40:27 192.168.122.209 [38177.568127] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:40:27 192.168.122.209 [38177.979302] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:40:27 192.168.122.209 [38178.005863] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:40:27 192.168.122.209 [38178.032134] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:40:27 192.168.122.209 [38178.081127] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:40:27 192.168.122.209 [38178.082860] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:40:27 192.168.122.209 [38178.121089] [tempesta fw] Tempesta FW is ready Apr 26 02:40:28 192.168.122.209 [38178.748740] [tdb] Close table 'client0.tdb' Apr 26 02:40:28 192.168.122.209 [38178.929972] [tdb] Close table 'sessions0.tdb' Apr 26 02:40:31 192.168.122.209 [38182.085892] [tdb] Close table 'cache0.tdb' Apr 26 02:40:32 192.168.122.209 [38182.318423] [tdb] Close table 'filter0.tdb' Apr 26 02:40:32 192.168.122.209 [38182.318859] [tempesta fw] modules are stopped Apr 26 02:40:32 192.168.122.209 [38182.509519] [tempesta fw] exiting... Apr 26 02:40:32 192.168.122.209 [38182.668746] [tdb] Shutdown Tempesta DB Apr 26 02:40:32 192.168.122.209 [38182.912456] End test: cache.test_conditional.TestConditionalH2.test_incorrect_none_match_and_correct_modified_since Apr 26 02:40:32 192.168.122.209 [38182.935382] Start test: cache.test_conditional.TestConditionalH2.test_mod_since Apr 26 02:40:33 192.168.122.209 [38184.166745] [tdb] Start Tempesta DB Apr 26 02:40:34 192.168.122.209 [38184.312782] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:40:35 192.168.122.209 [38185.754475] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38185.754475] Maybe that's fine, but it's worth checking the [38185.754475] config - if there is no relations between the [38185.754475] names, then host name confusion attack is possible. Apr 26 02:40:35 192.168.122.209 [38185.893216] [tempesta fw] Configuration processing is completed. Apr 26 02:40:35 192.168.122.209 [38185.975061] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:40:36 192.168.122.209 [38186.401347] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:40:36 192.168.122.209 [38186.427734] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:40:36 192.168.122.209 [38186.455311] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:40:36 192.168.122.209 [38186.513235] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:40:36 192.168.122.209 [38186.514973] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:40:36 192.168.122.209 [38186.553171] [tempesta fw] Tempesta FW is ready Apr 26 02:40:36 192.168.122.209 [38187.195270] [tdb] Close table 'client0.tdb' Apr 26 02:40:37 192.168.122.209 [38187.387441] [tdb] Close table 'sessions0.tdb' Apr 26 02:40:40 192.168.122.209 [38190.546771] [tdb] Close table 'cache0.tdb' Apr 26 02:40:40 192.168.122.209 [38190.782464] [tdb] Close table 'filter0.tdb' Apr 26 02:40:40 192.168.122.209 [38190.782899] [tempesta fw] modules are stopped Apr 26 02:40:40 192.168.122.209 [38191.032187] [tempesta fw] exiting... Apr 26 02:40:40 192.168.122.209 [38191.179637] [tdb] Shutdown Tempesta DB Apr 26 02:40:41 192.168.122.209 [38191.414297] End test: cache.test_conditional.TestConditionalH2.test_mod_since Apr 26 02:40:41 192.168.122.209 [38191.437245] Start test: cache.test_conditional.TestConditionalH2.test_mod_since_nc Apr 26 02:40:42 192.168.122.209 [38192.722909] [tdb] Start Tempesta DB Apr 26 02:40:42 192.168.122.209 [38192.875730] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:40:44 192.168.122.209 [38194.310567] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38194.310567] Maybe that's fine, but it's worth checking the [38194.310567] config - if there is no relations between the [38194.310567] names, then host name confusion attack is possible. Apr 26 02:40:44 192.168.122.209 [38194.449284] [tempesta fw] Configuration processing is completed. Apr 26 02:40:44 192.168.122.209 [38194.502905] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:40:44 192.168.122.209 [38194.936009] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:40:44 192.168.122.209 [38194.971033] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:40:44 192.168.122.209 [38194.997853] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:40:44 192.168.122.209 [38195.041336] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:40:44 192.168.122.209 [38195.043052] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:40:44 192.168.122.209 [38195.081295] [tempesta fw] Tempesta FW is ready Apr 26 02:40:45 192.168.122.209 [38195.709828] [tdb] Close table 'client0.tdb' Apr 26 02:40:45 192.168.122.209 [38195.911483] [tdb] Close table 'sessions0.tdb' Apr 26 02:40:48 192.168.122.209 [38199.081754] [tdb] Close table 'cache0.tdb' Apr 26 02:40:49 192.168.122.209 [38199.324263] [tdb] Close table 'filter0.tdb' Apr 26 02:40:49 192.168.122.209 [38199.324699] [tempesta fw] modules are stopped Apr 26 02:40:49 192.168.122.209 [38199.526377] [tempesta fw] exiting... Apr 26 02:40:49 192.168.122.209 [38199.676199] [tdb] Shutdown Tempesta DB Apr 26 02:40:49 192.168.122.209 [38199.924648] End test: cache.test_conditional.TestConditionalH2.test_mod_since_nc Apr 26 02:40:49 192.168.122.209 [38199.942740] Start test: cache.test_conditional.TestConditionalH2.test_mod_since_nc_with_invalid_date Apr 26 02:40:50 192.168.122.209 [38201.117019] [tdb] Start Tempesta DB Apr 26 02:40:50 192.168.122.209 [38201.264356] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:40:52 192.168.122.209 [38202.742840] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38202.742840] Maybe that's fine, but it's worth checking the [38202.742840] config - if there is no relations between the [38202.742840] names, then host name confusion attack is possible. Apr 26 02:40:52 192.168.122.209 [38202.873470] [tempesta fw] Configuration processing is completed. Apr 26 02:40:52 192.168.122.209 [38202.926396] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:40:53 192.168.122.209 [38203.400563] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:40:53 192.168.122.209 [38203.429797] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:40:53 192.168.122.209 [38203.458709] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:40:53 192.168.122.209 [38203.505478] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:40:53 192.168.122.209 [38203.507183] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:40:53 192.168.122.209 [38203.549410] [tempesta fw] Tempesta FW is ready Apr 26 02:40:53 192.168.122.209 [38204.159748] [tdb] Close table 'client0.tdb' Apr 26 02:40:54 192.168.122.209 [38204.363203] [tdb] Close table 'sessions0.tdb' Apr 26 02:40:57 192.168.122.209 [38207.563869] [tdb] Close table 'cache0.tdb' Apr 26 02:40:57 192.168.122.209 [38207.794035] [tdb] Close table 'filter0.tdb' Apr 26 02:40:57 192.168.122.209 [38207.794479] [tempesta fw] modules are stopped Apr 26 02:40:57 192.168.122.209 [38207.989658] [tempesta fw] exiting... Apr 26 02:40:57 192.168.122.209 [38208.157998] [tdb] Shutdown Tempesta DB Apr 26 02:40:58 192.168.122.209 [38208.403396] End test: cache.test_conditional.TestConditionalH2.test_mod_since_nc_with_invalid_date Apr 26 02:40:58 192.168.122.209 [38208.414886] Start test: cache.test_conditional.TestConditionalH2.test_none_match Apr 26 02:40:59 192.168.122.209 [38209.579484] [tdb] Start Tempesta DB Apr 26 02:40:59 192.168.122.209 [38209.734706] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:41:00 192.168.122.209 [38211.134790] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38211.134790] Maybe that's fine, but it's worth checking the [38211.134790] config - if there is no relations between the [38211.134790] names, then host name confusion attack is possible. Apr 26 02:41:00 192.168.122.209 [38211.265584] [tempesta fw] Configuration processing is completed. Apr 26 02:41:01 192.168.122.209 [38211.347200] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:41:01 192.168.122.209 [38211.781380] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:41:01 192.168.122.209 [38211.808538] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:41:01 192.168.122.209 [38211.836013] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:41:01 192.168.122.209 [38211.881548] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:41:01 192.168.122.209 [38211.883281] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:41:01 192.168.122.209 [38211.925500] [tempesta fw] Tempesta FW is ready Apr 26 02:41:02 192.168.122.209 [38212.522161] [tdb] Close table 'client0.tdb' Apr 26 02:41:02 192.168.122.209 [38212.723358] [tdb] Close table 'sessions0.tdb' Apr 26 02:41:05 192.168.122.209 [38215.961629] [tdb] Close table 'cache0.tdb' Apr 26 02:41:05 192.168.122.209 [38216.204657] [tdb] Close table 'filter0.tdb' Apr 26 02:41:05 192.168.122.209 [38216.205197] [tempesta fw] modules are stopped Apr 26 02:41:06 192.168.122.209 [38216.468056] [tempesta fw] exiting... Apr 26 02:41:06 192.168.122.209 [38216.631425] [tdb] Shutdown Tempesta DB Apr 26 02:41:06 192.168.122.209 [38216.827198] End test: cache.test_conditional.TestConditionalH2.test_none_match Apr 26 02:41:06 192.168.122.209 [38216.846302] Start test: cache.test_conditional.TestConditionalH2.test_none_match_HEAD Apr 26 02:41:07 192.168.122.209 [38218.097064] [tdb] Start Tempesta DB Apr 26 02:41:07 192.168.122.209 [38218.270371] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:41:09 192.168.122.209 [38219.746932] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38219.746932] Maybe that's fine, but it's worth checking the [38219.746932] config - if there is no relations between the [38219.746932] names, then host name confusion attack is possible. Apr 26 02:41:09 192.168.122.209 [38219.885688] [tempesta fw] Configuration processing is completed. Apr 26 02:41:09 192.168.122.209 [38219.936901] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:41:10 192.168.122.209 [38220.398307] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:41:10 192.168.122.209 [38220.436834] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:41:10 192.168.122.209 [38220.465713] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:41:10 192.168.122.209 [38220.513680] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:41:10 192.168.122.209 [38220.515426] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:41:10 192.168.122.209 [38220.557603] [tempesta fw] Tempesta FW is ready Apr 26 02:41:10 192.168.122.209 [38221.212335] [tdb] Close table 'client0.tdb' Apr 26 02:41:11 192.168.122.209 [38221.402808] [tdb] Close table 'sessions0.tdb' Apr 26 02:41:14 192.168.122.209 [38224.629462] [tdb] Close table 'cache0.tdb' Apr 26 02:41:14 192.168.122.209 [38224.859416] [tdb] Close table 'filter0.tdb' Apr 26 02:41:14 192.168.122.209 [38224.859867] [tempesta fw] modules are stopped Apr 26 02:41:14 192.168.122.209 [38225.064862] [tempesta fw] exiting... Apr 26 02:41:14 192.168.122.209 [38225.227763] [tdb] Shutdown Tempesta DB Apr 26 02:41:15 192.168.122.209 [38225.481625] End test: cache.test_conditional.TestConditionalH2.test_none_match_HEAD Apr 26 02:41:15 192.168.122.209 [38225.501884] Start test: cache.test_conditional.TestConditionalH2.test_none_match_any Apr 26 02:41:16 192.168.122.209 [38226.780495] [tdb] Start Tempesta DB Apr 26 02:41:16 192.168.122.209 [38226.943287] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:41:18 192.168.122.209 [38228.410964] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38228.410964] Maybe that's fine, but it's worth checking the [38228.410964] config - if there is no relations between the [38228.410964] names, then host name confusion attack is possible. Apr 26 02:41:18 192.168.122.209 [38228.557771] [tempesta fw] Configuration processing is completed. Apr 26 02:41:18 192.168.122.209 [38228.608309] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:41:18 192.168.122.209 [38229.026018] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:41:18 192.168.122.209 [38229.054523] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:41:18 192.168.122.209 [38229.082281] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:41:18 192.168.122.209 [38229.129790] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:41:18 192.168.122.209 [38229.131533] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:41:18 192.168.122.209 [38229.169669] [tempesta fw] Tempesta FW is ready Apr 26 02:41:19 192.168.122.209 [38229.790504] [tdb] Close table 'client0.tdb' Apr 26 02:41:19 192.168.122.209 [38229.986846] [tdb] Close table 'sessions0.tdb' Apr 26 02:41:22 192.168.122.209 [38233.236240] [tdb] Close table 'cache0.tdb' Apr 26 02:41:23 192.168.122.209 [38233.502166] [tdb] Close table 'filter0.tdb' Apr 26 02:41:23 192.168.122.209 [38233.502608] [tempesta fw] modules are stopped Apr 26 02:41:23 192.168.122.209 [38233.689398] [tempesta fw] exiting... Apr 26 02:41:23 192.168.122.209 [38233.862884] [tdb] Shutdown Tempesta DB Apr 26 02:41:23 192.168.122.209 [38234.106607] End test: cache.test_conditional.TestConditionalH2.test_none_match_any Apr 26 02:41:23 192.168.122.209 [38234.131481] Start test: cache.test_conditional.TestConditionalH2.test_none_match_list Apr 26 02:41:25 192.168.122.209 [38235.348439] [tdb] Start Tempesta DB Apr 26 02:41:25 192.168.122.209 [38235.493043] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:41:26 192.168.122.209 [38236.963123] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38236.963123] Maybe that's fine, but it's worth checking the [38236.963123] config - if there is no relations between the [38236.963123] names, then host name confusion attack is possible. Apr 26 02:41:26 192.168.122.209 [38237.109868] [tempesta fw] Configuration processing is completed. Apr 26 02:41:26 192.168.122.209 [38237.201508] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:41:27 192.168.122.209 [38237.629918] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:41:27 192.168.122.209 [38237.660397] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:41:27 192.168.122.209 [38237.693352] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:41:27 192.168.122.209 [38237.745912] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:41:27 192.168.122.209 [38237.747666] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:41:27 192.168.122.209 [38237.785887] [tempesta fw] Tempesta FW is ready Apr 26 02:41:28 192.168.122.209 [38238.401573] [tdb] Close table 'client0.tdb' Apr 26 02:41:28 192.168.122.209 [38238.611362] [tdb] Close table 'sessions0.tdb' Apr 26 02:41:31 192.168.122.209 [38241.796749] [tdb] Close table 'cache0.tdb' Apr 26 02:41:31 192.168.122.209 [38242.046828] [tdb] Close table 'filter0.tdb' Apr 26 02:41:31 192.168.122.209 [38242.047259] [tempesta fw] modules are stopped Apr 26 02:41:31 192.168.122.209 [38242.245337] [tempesta fw] exiting... Apr 26 02:41:32 192.168.122.209 [38242.391876] [tdb] Shutdown Tempesta DB Apr 26 02:41:32 192.168.122.209 [38242.627896] End test: cache.test_conditional.TestConditionalH2.test_none_match_list Apr 26 02:41:32 192.168.122.209 [38242.657628] Start test: cache.test_conditional.TestConditionalH2.test_none_match_nc_GET Apr 26 02:41:33 192.168.122.209 [38243.852421] [tdb] Start Tempesta DB Apr 26 02:41:33 192.168.122.209 [38243.996057] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:41:35 192.168.122.209 [38245.415319] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38245.415319] Maybe that's fine, but it's worth checking the [38245.415319] config - if there is no relations between the [38245.415319] names, then host name confusion attack is possible. Apr 26 02:41:35 192.168.122.209 [38245.546013] [tempesta fw] Configuration processing is completed. Apr 26 02:41:35 192.168.122.209 [38245.600652] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:41:35 192.168.122.209 [38246.036649] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:41:35 192.168.122.209 [38246.063153] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:41:35 192.168.122.209 [38246.089997] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:41:35 192.168.122.209 [38246.129991] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:41:35 192.168.122.209 [38246.131774] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:41:35 192.168.122.209 [38246.169999] [tempesta fw] Tempesta FW is ready Apr 26 02:41:36 192.168.122.209 [38246.776351] [tdb] Close table 'client0.tdb' Apr 26 02:41:36 192.168.122.209 [38246.965265] [tdb] Close table 'sessions0.tdb' Apr 26 02:41:41 192.168.122.209 [38251.670670] [tdb] Close table 'cache0.tdb' Apr 26 02:41:42 192.168.122.209 [38252.369325] [tdb] Close table 'filter0.tdb' Apr 26 02:41:42 192.168.122.209 [38252.369785] [tempesta fw] modules are stopped Apr 26 02:41:43 192.168.122.209 [38253.933988] [tempesta fw] exiting... Apr 26 02:41:43 192.168.122.209 [38254.074563] [tdb] Shutdown Tempesta DB Apr 26 02:41:44 192.168.122.209 [38254.331254] End test: cache.test_conditional.TestConditionalH2.test_none_match_nc_GET Apr 26 02:41:44 192.168.122.209 [38254.347329] Start test: cache.test_conditional.TestConditionalH2.test_none_match_nc_HEAD Apr 26 02:41:45 192.168.122.209 [38255.472171] [tdb] Start Tempesta DB Apr 26 02:41:45 192.168.122.209 [38255.613271] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:41:46 192.168.122.209 [38257.003365] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38257.003365] Maybe that's fine, but it's worth checking the [38257.003365] config - if there is no relations between the [38257.003365] names, then host name confusion attack is possible. Apr 26 02:41:46 192.168.122.209 [38257.162757] [tempesta fw] Configuration processing is completed. Apr 26 02:41:46 192.168.122.209 [38257.212348] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:41:47 192.168.122.209 [38257.638095] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:41:47 192.168.122.209 [38257.663937] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:41:47 192.168.122.209 [38257.690098] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:41:47 192.168.122.209 [38257.762151] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:41:47 192.168.122.209 [38257.763927] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:41:47 192.168.122.209 [38257.806114] [tempesta fw] Tempesta FW is ready Apr 26 02:41:48 192.168.122.209 [38258.417400] [tdb] Close table 'client0.tdb' Apr 26 02:41:48 192.168.122.209 [38258.607828] [tdb] Close table 'sessions0.tdb' Apr 26 02:41:51 192.168.122.209 [38261.758232] [tdb] Close table 'cache0.tdb' Apr 26 02:41:51 192.168.122.209 [38262.004421] [tdb] Close table 'filter0.tdb' Apr 26 02:41:51 192.168.122.209 [38262.004867] [tempesta fw] modules are stopped Apr 26 02:41:51 192.168.122.209 [38262.211258] [tempesta fw] exiting... Apr 26 02:41:52 192.168.122.209 [38262.346399] [tdb] Shutdown Tempesta DB Apr 26 02:41:52 192.168.122.209 [38262.548229] End test: cache.test_conditional.TestConditionalH2.test_none_match_nc_HEAD Apr 26 02:41:52 192.168.122.209 [38262.563469] Start test: cache.test_conditional.TestConditionalH2.test_none_match_no_quotes_etag Apr 26 02:41:53 192.168.122.209 [38263.650761] [tdb] Start Tempesta DB Apr 26 02:41:53 192.168.122.209 [38263.779864] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:41:54 192.168.122.209 [38265.179516] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38265.179516] Maybe that's fine, but it's worth checking the [38265.179516] config - if there is no relations between the [38265.179516] names, then host name confusion attack is possible. Apr 26 02:41:55 192.168.122.209 [38265.338260] [tempesta fw] Configuration processing is completed. Apr 26 02:41:55 192.168.122.209 [38265.389017] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:41:55 192.168.122.209 [38265.806541] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:41:55 192.168.122.209 [38265.832692] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:41:55 192.168.122.209 [38265.859670] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:41:55 192.168.122.209 [38265.898282] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:41:55 192.168.122.209 [38265.899813] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:41:55 192.168.122.209 [38265.938192] [tempesta fw] Tempesta FW is ready Apr 26 02:41:56 192.168.122.209 [38266.488500] [tdb] Close table 'client0.tdb' Apr 26 02:41:56 192.168.122.209 [38266.697695] [tdb] Close table 'sessions0.tdb' Apr 26 02:41:59 192.168.122.209 [38269.826359] [tdb] Close table 'cache0.tdb' Apr 26 02:41:59 192.168.122.209 [38270.101703] [tdb] Close table 'filter0.tdb' Apr 26 02:41:59 192.168.122.209 [38270.102362] [tempesta fw] modules are stopped Apr 26 02:42:00 192.168.122.209 [38270.304198] [tempesta fw] exiting... Apr 26 02:42:00 192.168.122.209 [38270.476662] [tdb] Shutdown Tempesta DB Apr 26 02:42:00 192.168.122.209 [38270.715291] End test: cache.test_conditional.TestConditionalH2.test_none_match_no_quotes_etag Apr 26 02:42:00 192.168.122.209 [38270.726534] Start test: cache.test_conditional.TestConditionalH2.test_none_match_no_quotes_etag_with_extra_spaces Apr 26 02:42:01 192.168.122.209 [38271.940491] [tdb] Start Tempesta DB Apr 26 02:42:01 192.168.122.209 [38272.074950] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:42:03 192.168.122.209 [38273.499581] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38273.499581] Maybe that's fine, but it's worth checking the [38273.499581] config - if there is no relations between the [38273.499581] names, then host name confusion attack is possible. Apr 26 02:42:03 192.168.122.209 [38273.646382] [tempesta fw] Configuration processing is completed. Apr 26 02:42:03 192.168.122.209 [38273.695858] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:42:03 192.168.122.209 [38274.122219] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:42:03 192.168.122.209 [38274.160736] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:42:03 192.168.122.209 [38274.186180] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:42:03 192.168.122.209 [38274.238366] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:42:03 192.168.122.209 [38274.240078] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:42:03 192.168.122.209 [38274.278307] [tempesta fw] Tempesta FW is ready Apr 26 02:42:04 192.168.122.209 [38274.906456] [tdb] Close table 'client0.tdb' Apr 26 02:42:04 192.168.122.209 [38275.080814] [tdb] Close table 'sessions0.tdb' Apr 26 02:42:07 192.168.122.209 [38278.218036] [tdb] Close table 'cache0.tdb' Apr 26 02:42:08 192.168.122.209 [38278.453794] [tdb] Close table 'filter0.tdb' Apr 26 02:42:08 192.168.122.209 [38278.454256] [tempesta fw] modules are stopped Apr 26 02:42:08 192.168.122.209 [38278.655436] [tempesta fw] exiting... Apr 26 02:42:08 192.168.122.209 [38278.817806] [tdb] Shutdown Tempesta DB Apr 26 02:42:08 192.168.122.209 [38279.033552] End test: cache.test_conditional.TestConditionalH2.test_none_match_no_quotes_etag_with_extra_spaces Apr 26 02:42:08 192.168.122.209 [38279.051550] Start test: cache.test_conditional.TestConditionalH2.test_none_match_weak_all Apr 26 02:42:09 192.168.122.209 [38280.225067] [tdb] Start Tempesta DB Apr 26 02:42:10 192.168.122.209 [38280.374437] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:42:11 192.168.122.209 [38281.787702] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38281.787702] Maybe that's fine, but it's worth checking the [38281.787702] config - if there is no relations between the [38281.787702] names, then host name confusion attack is possible. Apr 26 02:42:11 192.168.122.209 [38281.918477] [tempesta fw] Configuration processing is completed. Apr 26 02:42:11 192.168.122.209 [38281.974864] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:42:12 192.168.122.209 [38282.379406] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:42:12 192.168.122.209 [38282.404986] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:42:12 192.168.122.209 [38282.430681] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:42:12 192.168.122.209 [38282.474449] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:42:12 192.168.122.209 [38282.475875] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:42:12 192.168.122.209 [38282.518424] [tempesta fw] Tempesta FW is ready Apr 26 02:42:12 192.168.122.209 [38283.140407] [tdb] Close table 'client0.tdb' Apr 26 02:42:13 192.168.122.209 [38283.337203] [tdb] Close table 'sessions0.tdb' Apr 26 02:42:16 192.168.122.209 [38286.473459] [tdb] Close table 'cache0.tdb' Apr 26 02:42:16 192.168.122.209 [38286.717543] [tdb] Close table 'filter0.tdb' Apr 26 02:42:16 192.168.122.209 [38286.717966] [tempesta fw] modules are stopped Apr 26 02:42:16 192.168.122.209 [38286.943842] [tempesta fw] exiting... Apr 26 02:42:16 192.168.122.209 [38287.068507] [tdb] Shutdown Tempesta DB Apr 26 02:42:17 192.168.122.209 [38287.321354] End test: cache.test_conditional.TestConditionalH2.test_none_match_weak_all Apr 26 02:42:17 192.168.122.209 [38287.339087] Start test: cache.test_conditional.TestConditionalH2.test_none_match_weak_clnt Apr 26 02:42:18 192.168.122.209 [38288.535009] [tdb] Start Tempesta DB Apr 26 02:42:18 192.168.122.209 [38288.682899] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:42:19 192.168.122.209 [38290.143572] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38290.143572] Maybe that's fine, but it's worth checking the [38290.143572] config - if there is no relations between the [38290.143572] names, then host name confusion attack is possible. Apr 26 02:42:19 192.168.122.209 [38290.287025] [tempesta fw] Configuration processing is completed. Apr 26 02:42:20 192.168.122.209 [38290.341383] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:42:20 192.168.122.209 [38290.746164] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:42:20 192.168.122.209 [38290.771715] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:42:20 192.168.122.209 [38290.827409] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:42:20 192.168.122.209 [38290.898508] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:42:20 192.168.122.209 [38290.899538] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:42:20 192.168.122.209 [38290.938535] [tempesta fw] Tempesta FW is ready Apr 26 02:42:21 192.168.122.209 [38291.549622] [tdb] Close table 'client0.tdb' Apr 26 02:42:21 192.168.122.209 [38291.747550] [tdb] Close table 'sessions0.tdb' Apr 26 02:42:24 192.168.122.209 [38294.919693] [tdb] Close table 'cache0.tdb' Apr 26 02:42:24 192.168.122.209 [38295.171125] [tdb] Close table 'filter0.tdb' Apr 26 02:42:24 192.168.122.209 [38295.171546] [tempesta fw] modules are stopped Apr 26 02:42:25 192.168.122.209 [38295.374279] [tempesta fw] exiting... Apr 26 02:42:25 192.168.122.209 [38295.551871] [tdb] Shutdown Tempesta DB Apr 26 02:42:25 192.168.122.209 [38295.780578] End test: cache.test_conditional.TestConditionalH2.test_none_match_weak_clnt Apr 26 02:42:25 192.168.122.209 [38295.805628] Start test: cache.test_conditional.TestConditionalH2.test_none_match_weak_srv Apr 26 02:42:26 192.168.122.209 [38296.994352] [tdb] Start Tempesta DB Apr 26 02:42:26 192.168.122.209 [38297.140104] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:42:28 192.168.122.209 [38298.527921] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38298.527921] Maybe that's fine, but it's worth checking the [38298.527921] config - if there is no relations between the [38298.527921] names, then host name confusion attack is possible. Apr 26 02:42:28 192.168.122.209 [38298.671574] [tempesta fw] Configuration processing is completed. Apr 26 02:42:28 192.168.122.209 [38298.720640] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:42:28 192.168.122.209 [38299.142940] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:42:28 192.168.122.209 [38299.169326] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:42:28 192.168.122.209 [38299.195467] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:42:28 192.168.122.209 [38299.238685] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:42:28 192.168.122.209 [38299.240449] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:42:28 192.168.122.209 [38299.278627] [tempesta fw] Tempesta FW is ready Apr 26 02:42:29 192.168.122.209 [38300.001633] [tdb] Close table 'client0.tdb' Apr 26 02:42:29 192.168.122.209 [38300.207871] [tdb] Close table 'sessions0.tdb' Apr 26 02:42:33 192.168.122.209 [38303.344846] [tdb] Close table 'cache0.tdb' Apr 26 02:42:33 192.168.122.209 [38303.574010] [tdb] Close table 'filter0.tdb' Apr 26 02:42:33 192.168.122.209 [38303.574438] [tempesta fw] modules are stopped Apr 26 02:42:33 192.168.122.209 [38303.763297] [tempesta fw] exiting... Apr 26 02:42:33 192.168.122.209 [38303.899632] [tdb] Shutdown Tempesta DB Apr 26 02:42:33 192.168.122.209 [38304.124871] End test: cache.test_conditional.TestConditionalH2.test_none_match_weak_srv Apr 26 02:42:33 192.168.122.209 [38304.140764] Start test: cache.test_conditional.TestConditionalH2.test_response_without_last_modified Apr 26 02:42:34 192.168.122.209 [38305.272543] [tdb] Start Tempesta DB Apr 26 02:42:35 192.168.122.209 [38305.428759] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:42:36 192.168.122.209 [38306.904026] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38306.904026] Maybe that's fine, but it's worth checking the [38306.904026] config - if there is no relations between the [38306.904026] names, then host name confusion attack is possible. Apr 26 02:42:36 192.168.122.209 [38307.042778] [tempesta fw] Configuration processing is completed. Apr 26 02:42:36 192.168.122.209 [38307.095791] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:42:37 192.168.122.209 [38307.513424] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:42:37 192.168.122.209 [38307.548570] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:42:37 192.168.122.209 [38307.613545] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:42:37 192.168.122.209 [38307.662784] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:42:37 192.168.122.209 [38307.664526] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:42:37 192.168.122.209 [38307.702747] [tempesta fw] Tempesta FW is ready Apr 26 02:42:38 192.168.122.209 [38308.327727] [tdb] Close table 'client0.tdb' Apr 26 02:42:38 192.168.122.209 [38308.512458] [tdb] Close table 'sessions0.tdb' Apr 26 02:42:41 192.168.122.209 [38311.739827] [tdb] Close table 'cache0.tdb' Apr 26 02:42:41 192.168.122.209 [38311.981215] [tdb] Close table 'filter0.tdb' Apr 26 02:42:41 192.168.122.209 [38311.981644] [tempesta fw] modules are stopped Apr 26 02:42:41 192.168.122.209 [38312.151602] [tempesta fw] exiting... Apr 26 02:42:42 192.168.122.209 [38312.301123] [tdb] Shutdown Tempesta DB Apr 26 02:42:42 192.168.122.209 [38312.534199] End test: cache.test_conditional.TestConditionalH2.test_response_without_last_modified Apr 26 02:42:42 192.168.122.209 [38312.554813] Start test: cache.test_conditional.TestConditionalH2.test_response_without_last_modified_and_date Apr 26 02:42:43 192.168.122.209 [38313.798152] [tdb] Start Tempesta DB Apr 26 02:42:43 192.168.122.209 [38313.953481] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:42:45 192.168.122.209 [38315.360073] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38315.360073] Maybe that's fine, but it's worth checking the [38315.360073] config - if there is no relations between the [38315.360073] names, then host name confusion attack is possible. Apr 26 02:42:45 192.168.122.209 [38315.546904] [tempesta fw] Configuration processing is completed. Apr 26 02:42:45 192.168.122.209 [38315.601325] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:42:45 192.168.122.209 [38316.024029] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:42:45 192.168.122.209 [38316.049990] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:42:45 192.168.122.209 [38316.075961] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:42:45 192.168.122.209 [38316.114896] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:42:45 192.168.122.209 [38316.116625] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:42:45 192.168.122.209 [38316.166839] [tempesta fw] Tempesta FW is ready Apr 26 02:42:46 192.168.122.209 [38316.834487] [tdb] Close table 'client0.tdb' Apr 26 02:42:46 192.168.122.209 [38317.014671] [tdb] Close table 'sessions0.tdb' Apr 26 02:42:49 192.168.122.209 [38320.188364] [tdb] Close table 'cache0.tdb' Apr 26 02:42:50 192.168.122.209 [38320.421665] [tdb] Close table 'filter0.tdb' Apr 26 02:42:50 192.168.122.209 [38320.422115] [tempesta fw] modules are stopped Apr 26 02:42:50 192.168.122.209 [38320.631262] [tempesta fw] exiting... Apr 26 02:42:50 192.168.122.209 [38320.773272] [tdb] Shutdown Tempesta DB Apr 26 02:42:50 192.168.122.209 [38320.991866] End test: cache.test_conditional.TestConditionalH2.test_response_without_last_modified_and_date Apr 26 02:42:50 192.168.122.209 [38321.004619] Start test: cache.test_conditional.TestConditionalH2.test_response_without_last_modified_and_date_nc Apr 26 02:42:51 192.168.122.209 [38322.216555] [tdb] Start Tempesta DB Apr 26 02:42:52 192.168.122.209 [38322.371966] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:42:53 192.168.122.209 [38323.860250] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38323.860250] Maybe that's fine, but it's worth checking the [38323.860250] config - if there is no relations between the [38323.860250] names, then host name confusion attack is possible. Apr 26 02:42:53 192.168.122.209 [38324.007023] [tempesta fw] Configuration processing is completed. Apr 26 02:42:53 192.168.122.209 [38324.095069] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:42:54 192.168.122.209 [38324.523083] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:42:54 192.168.122.209 [38324.549644] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:42:54 192.168.122.209 [38324.576957] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:42:54 192.168.122.209 [38324.623020] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:42:54 192.168.122.209 [38324.624822] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:42:54 192.168.122.209 [38324.670967] [tempesta fw] Tempesta FW is ready Apr 26 02:42:54 192.168.122.209 [38325.279322] [tdb] Close table 'client0.tdb' Apr 26 02:42:55 192.168.122.209 [38325.480739] [tdb] Close table 'sessions0.tdb' Apr 26 02:42:58 192.168.122.209 [38328.616106] [tdb] Close table 'cache0.tdb' Apr 26 02:42:58 192.168.122.209 [38328.870118] [tdb] Close table 'filter0.tdb' Apr 26 02:42:58 192.168.122.209 [38328.870560] [tempesta fw] modules are stopped Apr 26 02:42:58 192.168.122.209 [38329.035248] [tempesta fw] exiting... Apr 26 02:42:58 192.168.122.209 [38329.184706] [tdb] Shutdown Tempesta DB Apr 26 02:42:59 192.168.122.209 [38329.435928] End test: cache.test_conditional.TestConditionalH2.test_response_without_last_modified_and_date_nc Apr 26 02:42:59 192.168.122.209 [38329.469612] Start test: cache.test_conditional.TestConditionalH2.test_response_without_last_modified_nc Apr 26 02:43:00 192.168.122.209 [38330.610113] [tdb] Start Tempesta DB Apr 26 02:43:00 192.168.122.209 [38330.761867] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:43:01 192.168.122.209 [38332.160351] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38332.160351] Maybe that's fine, but it's worth checking the [38332.160351] config - if there is no relations between the [38332.160351] names, then host name confusion attack is possible. Apr 26 02:43:02 192.168.122.209 [38332.312371] [tempesta fw] Configuration processing is completed. Apr 26 02:43:02 192.168.122.209 [38332.365322] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:43:02 192.168.122.209 [38332.783239] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:43:02 192.168.122.209 [38332.809571] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:43:02 192.168.122.209 [38332.835728] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:43:02 192.168.122.209 [38332.875070] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:43:02 192.168.122.209 [38332.876239] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:43:02 192.168.122.209 [38332.919064] [tempesta fw] Tempesta FW is ready Apr 26 02:43:03 192.168.122.209 [38333.548393] [tdb] Close table 'client0.tdb' Apr 26 02:43:03 192.168.122.209 [38333.730595] [tdb] Close table 'sessions0.tdb' Apr 26 02:43:06 192.168.122.209 [38336.881991] [tdb] Close table 'cache0.tdb' Apr 26 02:43:06 192.168.122.209 [38337.108908] [tdb] Close table 'filter0.tdb' Apr 26 02:43:06 192.168.122.209 [38337.109340] [tempesta fw] modules are stopped Apr 26 02:43:07 192.168.122.209 [38337.292973] [tempesta fw] exiting... Apr 26 02:43:07 192.168.122.209 [38337.463454] [tdb] Shutdown Tempesta DB Apr 26 02:43:07 192.168.122.209 [38337.714003] End test: cache.test_conditional.TestConditionalH2.test_response_without_last_modified_nc Apr 26 02:43:07 192.168.122.209 [38337.738669] Start test: cache.test_conditional.TestConditionalHttp.test_correct_none_match_and_modified_since Apr 26 02:43:08 192.168.122.209 [38338.970764] [tdb] Start Tempesta DB Apr 26 02:43:08 192.168.122.209 [38339.121918] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:43:10 192.168.122.209 [38340.628500] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38340.628500] Maybe that's fine, but it's worth checking the [38340.628500] config - if there is no relations between the [38340.628500] names, then host name confusion attack is possible. Apr 26 02:43:10 192.168.122.209 [38340.763215] [tempesta fw] Configuration processing is completed. Apr 26 02:43:10 192.168.122.209 [38340.812143] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:43:10 192.168.122.209 [38341.223950] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:43:10 192.168.122.209 [38341.249080] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:43:10 192.168.122.209 [38341.276659] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:43:11 192.168.122.209 [38341.319160] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:43:11 192.168.122.209 [38341.320212] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:43:11 192.168.122.209 [38341.367166] [tempesta fw] Tempesta FW is ready Apr 26 02:43:11 192.168.122.209 [38341.993727] [tdb] Close table 'client0.tdb' Apr 26 02:43:11 192.168.122.209 [38342.195826] [tdb] Close table 'sessions0.tdb' Apr 26 02:43:15 192.168.122.209 [38345.343575] [tdb] Close table 'cache0.tdb' Apr 26 02:43:15 192.168.122.209 [38345.565533] [tdb] Close table 'filter0.tdb' Apr 26 02:43:15 192.168.122.209 [38345.565966] [tempesta fw] modules are stopped Apr 26 02:43:15 192.168.122.209 [38345.799516] [tempesta fw] exiting... Apr 26 02:43:15 192.168.122.209 [38345.954556] [tdb] Shutdown Tempesta DB Apr 26 02:43:15 192.168.122.209 [38346.184622] End test: cache.test_conditional.TestConditionalHttp.test_correct_none_match_and_modified_since Apr 26 02:43:15 192.168.122.209 [38346.201076] Start test: cache.test_conditional.TestConditionalHttp.test_incorrect_none_match_and_correct_modified_since Apr 26 02:43:17 192.168.122.209 [38347.360243] [tdb] Start Tempesta DB Apr 26 02:43:17 192.168.122.209 [38347.526021] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:43:18 192.168.122.209 [38348.964556] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38348.964556] Maybe that's fine, but it's worth checking the [38348.964556] config - if there is no relations between the [38348.964556] names, then host name confusion attack is possible. Apr 26 02:43:18 192.168.122.209 [38349.099400] [tempesta fw] Configuration processing is completed. Apr 26 02:43:18 192.168.122.209 [38349.184244] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:43:19 192.168.122.209 [38349.608401] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:43:19 192.168.122.209 [38349.635110] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:43:19 192.168.122.209 [38349.662513] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:43:19 192.168.122.209 [38349.711325] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:43:19 192.168.122.209 [38349.713058] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:43:19 192.168.122.209 [38349.751267] [tempesta fw] Tempesta FW is ready Apr 26 02:43:20 192.168.122.209 [38350.358211] [tdb] Close table 'client0.tdb' Apr 26 02:43:20 192.168.122.209 [38350.560994] [tdb] Close table 'sessions0.tdb' Apr 26 02:43:23 192.168.122.209 [38353.711484] [tdb] Close table 'cache0.tdb' Apr 26 02:43:23 192.168.122.209 [38353.946845] [tdb] Close table 'filter0.tdb' Apr 26 02:43:23 192.168.122.209 [38353.947293] [tempesta fw] modules are stopped Apr 26 02:43:23 192.168.122.209 [38354.192175] [tempesta fw] exiting... Apr 26 02:43:24 192.168.122.209 [38354.332740] [tdb] Shutdown Tempesta DB Apr 26 02:43:24 192.168.122.209 [38354.550636] End test: cache.test_conditional.TestConditionalHttp.test_incorrect_none_match_and_correct_modified_since Apr 26 02:43:24 192.168.122.209 [38354.580793] Start test: cache.test_conditional.TestConditionalHttp.test_mod_since Apr 26 02:43:25 192.168.122.209 [38355.763925] [tdb] Start Tempesta DB Apr 26 02:43:25 192.168.122.209 [38355.899868] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:43:26 192.168.122.209 [38357.276611] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38357.276611] Maybe that's fine, but it's worth checking the [38357.276611] config - if there is no relations between the [38357.276611] names, then host name confusion attack is possible. Apr 26 02:43:27 192.168.122.209 [38357.415429] [tempesta fw] Configuration processing is completed. Apr 26 02:43:27 192.168.122.209 [38357.463067] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:43:27 192.168.122.209 [38357.881519] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:43:27 192.168.122.209 [38357.907813] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:43:27 192.168.122.209 [38357.933789] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:43:27 192.168.122.209 [38357.975444] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:43:27 192.168.122.209 [38357.977182] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:43:27 192.168.122.209 [38358.015395] [tempesta fw] Tempesta FW is ready Apr 26 02:43:28 192.168.122.209 [38358.626361] [tdb] Close table 'client0.tdb' Apr 26 02:43:28 192.168.122.209 [38358.841078] [tdb] Close table 'sessions0.tdb' Apr 26 02:43:31 192.168.122.209 [38361.978190] [tdb] Close table 'cache0.tdb' Apr 26 02:43:31 192.168.122.209 [38362.239057] [tdb] Close table 'filter0.tdb' Apr 26 02:43:31 192.168.122.209 [38362.239518] [tempesta fw] modules are stopped Apr 26 02:43:32 192.168.122.209 [38362.438130] [tempesta fw] exiting... Apr 26 02:43:32 192.168.122.209 [38362.582944] [tdb] Shutdown Tempesta DB Apr 26 02:43:32 192.168.122.209 [38362.776336] End test: cache.test_conditional.TestConditionalHttp.test_mod_since Apr 26 02:43:32 192.168.122.209 [38362.799474] Start test: cache.test_conditional.TestConditionalHttp.test_mod_since_nc Apr 26 02:43:33 192.168.122.209 [38363.993935] [tdb] Start Tempesta DB Apr 26 02:43:33 192.168.122.209 [38364.151031] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:43:35 192.168.122.209 [38365.620824] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38365.620824] Maybe that's fine, but it's worth checking the [38365.620824] config - if there is no relations between the [38365.620824] names, then host name confusion attack is possible. Apr 26 02:43:35 192.168.122.209 [38365.771560] [tempesta fw] Configuration processing is completed. Apr 26 02:43:35 192.168.122.209 [38365.821132] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:43:35 192.168.122.209 [38366.240235] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:43:35 192.168.122.209 [38366.266008] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:43:36 192.168.122.209 [38366.292206] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:43:36 192.168.122.209 [38366.339549] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:43:36 192.168.122.209 [38366.341295] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:43:36 192.168.122.209 [38366.379499] [tempesta fw] Tempesta FW is ready Apr 26 02:43:36 192.168.122.209 [38366.949029] [tdb] Close table 'client0.tdb' Apr 26 02:43:36 192.168.122.209 [38367.174819] [tdb] Close table 'sessions0.tdb' Apr 26 02:43:40 192.168.122.209 [38370.342552] [tdb] Close table 'cache0.tdb' Apr 26 02:43:40 192.168.122.209 [38370.583215] [tdb] Close table 'filter0.tdb' Apr 26 02:43:40 192.168.122.209 [38370.584016] [tempesta fw] modules are stopped Apr 26 02:43:40 192.168.122.209 [38370.793533] [tempesta fw] exiting... Apr 26 02:43:40 192.168.122.209 [38370.944157] [tdb] Shutdown Tempesta DB Apr 26 02:43:40 192.168.122.209 [38371.149755] End test: cache.test_conditional.TestConditionalHttp.test_mod_since_nc Apr 26 02:43:40 192.168.122.209 [38371.161402] Start test: cache.test_conditional.TestConditionalHttp.test_mod_since_nc_with_invalid_date Apr 26 02:43:41 192.168.122.209 [38372.270984] [tdb] Start Tempesta DB Apr 26 02:43:42 192.168.122.209 [38372.420247] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:43:43 192.168.122.209 [38373.860899] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38373.860899] Maybe that's fine, but it's worth checking the [38373.860899] config - if there is no relations between the [38373.860899] names, then host name confusion attack is possible. Apr 26 02:43:43 192.168.122.209 [38373.991685] [tempesta fw] Configuration processing is completed. Apr 26 02:43:43 192.168.122.209 [38374.040459] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:43:44 192.168.122.209 [38374.455639] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:43:44 192.168.122.209 [38374.486395] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:43:44 192.168.122.209 [38374.512242] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:43:44 192.168.122.209 [38374.551645] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:43:44 192.168.122.209 [38374.553370] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:43:44 192.168.122.209 [38374.591593] [tempesta fw] Tempesta FW is ready Apr 26 02:43:44 192.168.122.209 [38375.226112] [tdb] Close table 'client0.tdb' Apr 26 02:43:45 192.168.122.209 [38375.416069] [tdb] Close table 'sessions0.tdb' Apr 26 02:43:48 192.168.122.209 [38378.565373] [tdb] Close table 'cache0.tdb' Apr 26 02:43:48 192.168.122.209 [38378.812731] [tdb] Close table 'filter0.tdb' Apr 26 02:43:48 192.168.122.209 [38378.813177] [tempesta fw] modules are stopped Apr 26 02:43:48 192.168.122.209 [38379.035983] [tempesta fw] exiting... Apr 26 02:43:48 192.168.122.209 [38379.203126] [tdb] Shutdown Tempesta DB Apr 26 02:43:49 192.168.122.209 [38379.420792] End test: cache.test_conditional.TestConditionalHttp.test_mod_since_nc_with_invalid_date Apr 26 02:43:49 192.168.122.209 [38379.444675] Start test: cache.test_conditional.TestConditionalHttp.test_none_match Apr 26 02:43:50 192.168.122.209 [38380.597688] [tdb] Start Tempesta DB Apr 26 02:43:50 192.168.122.209 [38380.730467] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:43:51 192.168.122.209 [38382.149029] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38382.149029] Maybe that's fine, but it's worth checking the [38382.149029] config - if there is no relations between the [38382.149029] names, then host name confusion attack is possible. Apr 26 02:43:52 192.168.122.209 [38382.291771] [tempesta fw] Configuration processing is completed. Apr 26 02:43:52 192.168.122.209 [38382.382503] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:43:52 192.168.122.209 [38382.811347] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:43:52 192.168.122.209 [38382.838834] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:43:52 192.168.122.209 [38382.866800] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:43:52 192.168.122.209 [38382.907761] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:43:52 192.168.122.209 [38382.909484] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:43:52 192.168.122.209 [38382.947714] [tempesta fw] Tempesta FW is ready Apr 26 02:43:53 192.168.122.209 [38383.564024] [tdb] Close table 'client0.tdb' Apr 26 02:43:53 192.168.122.209 [38383.760277] [tdb] Close table 'sessions0.tdb' Apr 26 02:43:56 192.168.122.209 [38386.992664] [tdb] Close table 'cache0.tdb' Apr 26 02:43:56 192.168.122.209 [38387.224508] [tdb] Close table 'filter0.tdb' Apr 26 02:43:56 192.168.122.209 [38387.225487] [tempesta fw] modules are stopped Apr 26 02:43:57 192.168.122.209 [38387.463827] [tempesta fw] exiting... Apr 26 02:43:57 192.168.122.209 [38387.607416] [tdb] Shutdown Tempesta DB Apr 26 02:43:57 192.168.122.209 [38387.835070] End test: cache.test_conditional.TestConditionalHttp.test_none_match Apr 26 02:43:57 192.168.122.209 [38387.851985] Start test: cache.test_conditional.TestConditionalHttp.test_none_match_HEAD Apr 26 02:43:58 192.168.122.209 [38389.031613] [tdb] Start Tempesta DB Apr 26 02:43:58 192.168.122.209 [38389.170305] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:44:00 192.168.122.209 [38390.561166] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38390.561166] Maybe that's fine, but it's worth checking the [38390.561166] config - if there is no relations between the [38390.561166] names, then host name confusion attack is possible. Apr 26 02:44:00 192.168.122.209 [38390.687872] [tempesta fw] Configuration processing is completed. Apr 26 02:44:00 192.168.122.209 [38390.736828] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:44:00 192.168.122.209 [38391.151583] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:44:00 192.168.122.209 [38391.193713] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:44:00 192.168.122.209 [38391.219414] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:44:00 192.168.122.209 [38391.263887] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:44:00 192.168.122.209 [38391.265639] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:44:01 192.168.122.209 [38391.303824] [tempesta fw] Tempesta FW is ready Apr 26 02:44:01 192.168.122.209 [38391.899311] [tdb] Close table 'client0.tdb' Apr 26 02:44:01 192.168.122.209 [38392.101666] [tdb] Close table 'sessions0.tdb' Apr 26 02:44:04 192.168.122.209 [38395.285323] [tdb] Close table 'cache0.tdb' Apr 26 02:44:05 192.168.122.209 [38395.543197] [tdb] Close table 'filter0.tdb' Apr 26 02:44:05 192.168.122.209 [38395.543626] [tempesta fw] modules are stopped Apr 26 02:44:05 192.168.122.209 [38395.733318] [tempesta fw] exiting... Apr 26 02:44:05 192.168.122.209 [38395.949043] [tdb] Shutdown Tempesta DB Apr 26 02:44:05 192.168.122.209 [38396.208933] End test: cache.test_conditional.TestConditionalHttp.test_none_match_HEAD Apr 26 02:44:05 192.168.122.209 [38396.222727] Start test: cache.test_conditional.TestConditionalHttp.test_none_match_any Apr 26 02:44:07 192.168.122.209 [38397.416215] [tdb] Start Tempesta DB Apr 26 02:44:07 192.168.122.209 [38397.570799] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:44:08 192.168.122.209 [38399.029218] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38399.029218] Maybe that's fine, but it's worth checking the [38399.029218] config - if there is no relations between the [38399.029218] names, then host name confusion attack is possible. Apr 26 02:44:08 192.168.122.209 [38399.159985] [tempesta fw] Configuration processing is completed. Apr 26 02:44:08 192.168.122.209 [38399.213802] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:44:09 192.168.122.209 [38399.635915] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:44:09 192.168.122.209 [38399.669412] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:44:09 192.168.122.209 [38399.703474] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:44:09 192.168.122.209 [38399.763969] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:44:09 192.168.122.209 [38399.765702] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:44:09 192.168.122.209 [38399.811916] [tempesta fw] Tempesta FW is ready Apr 26 02:44:10 192.168.122.209 [38400.455940] [tdb] Close table 'client0.tdb' Apr 26 02:44:10 192.168.122.209 [38400.656322] [tdb] Close table 'sessions0.tdb' Apr 26 02:44:13 192.168.122.209 [38403.826875] [tdb] Close table 'cache0.tdb' Apr 26 02:44:13 192.168.122.209 [38404.061758] [tdb] Close table 'filter0.tdb' Apr 26 02:44:13 192.168.122.209 [38404.062198] [tempesta fw] modules are stopped Apr 26 02:44:13 192.168.122.209 [38404.267392] [tempesta fw] exiting... Apr 26 02:44:14 192.168.122.209 [38404.428259] [tdb] Shutdown Tempesta DB Apr 26 02:44:14 192.168.122.209 [38404.634819] End test: cache.test_conditional.TestConditionalHttp.test_none_match_any Apr 26 02:44:14 192.168.122.209 [38404.653967] Start test: cache.test_conditional.TestConditionalHttp.test_none_match_empty_etag Apr 26 02:44:15 192.168.122.209 [38405.868257] [tdb] Start Tempesta DB Apr 26 02:44:15 192.168.122.209 [38406.014401] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:44:17 192.168.122.209 [38407.437309] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38407.437309] Maybe that's fine, but it's worth checking the [38407.437309] config - if there is no relations between the [38407.437309] names, then host name confusion attack is possible. Apr 26 02:44:17 192.168.122.209 [38407.564105] [tempesta fw] Configuration processing is completed. Apr 26 02:44:17 192.168.122.209 [38407.616117] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:44:17 192.168.122.209 [38408.048579] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:44:17 192.168.122.209 [38408.074299] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:44:17 192.168.122.209 [38408.100939] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:44:17 192.168.122.209 [38408.164096] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:44:17 192.168.122.209 [38408.165835] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:44:17 192.168.122.209 [38408.203996] [tempesta fw] Tempesta FW is ready Apr 26 02:44:18 192.168.122.209 [38408.830308] [tdb] Close table 'client0.tdb' Apr 26 02:44:18 192.168.122.209 [38409.021908] [tdb] Close table 'sessions0.tdb' Apr 26 02:44:21 192.168.122.209 [38412.152087] [tdb] Close table 'cache0.tdb' Apr 26 02:44:22 192.168.122.209 [38412.401525] [tdb] Close table 'filter0.tdb' Apr 26 02:44:22 192.168.122.209 [38412.401959] [tempesta fw] modules are stopped Apr 26 02:44:22 192.168.122.209 [38412.619737] [tempesta fw] exiting... Apr 26 02:44:22 192.168.122.209 [38412.754887] [tdb] Shutdown Tempesta DB Apr 26 02:44:22 192.168.122.209 [38412.965036] End test: cache.test_conditional.TestConditionalHttp.test_none_match_empty_etag Apr 26 02:44:22 192.168.122.209 [38412.982936] Start test: cache.test_conditional.TestConditionalHttp.test_none_match_list Apr 26 02:44:23 192.168.122.209 [38414.204931] [tdb] Start Tempesta DB Apr 26 02:44:24 192.168.122.209 [38414.345622] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:44:25 192.168.122.209 [38415.725415] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38415.725415] Maybe that's fine, but it's worth checking the [38415.725415] config - if there is no relations between the [38415.725415] names, then host name confusion attack is possible. Apr 26 02:44:25 192.168.122.209 [38415.864179] [tempesta fw] Configuration processing is completed. Apr 26 02:44:25 192.168.122.209 [38415.912707] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:44:26 192.168.122.209 [38416.323255] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:44:26 192.168.122.209 [38416.349016] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:44:26 192.168.122.209 [38416.375747] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:44:26 192.168.122.209 [38416.416189] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:44:26 192.168.122.209 [38416.417909] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:44:26 192.168.122.209 [38416.456142] [tempesta fw] Tempesta FW is ready Apr 26 02:44:26 192.168.122.209 [38417.093461] [tdb] Close table 'client0.tdb' Apr 26 02:44:26 192.168.122.209 [38417.274705] [tdb] Close table 'sessions0.tdb' Apr 26 02:44:30 192.168.122.209 [38420.441189] [tdb] Close table 'cache0.tdb' Apr 26 02:44:30 192.168.122.209 [38420.708342] [tdb] Close table 'filter0.tdb' Apr 26 02:44:30 192.168.122.209 [38420.708793] [tempesta fw] modules are stopped Apr 26 02:44:30 192.168.122.209 [38420.905559] [tempesta fw] exiting... Apr 26 02:44:30 192.168.122.209 [38421.065258] [tdb] Shutdown Tempesta DB Apr 26 02:44:30 192.168.122.209 [38421.286644] End test: cache.test_conditional.TestConditionalHttp.test_none_match_list Apr 26 02:44:31 192.168.122.209 [38421.317593] Start test: cache.test_conditional.TestConditionalHttp.test_none_match_nc_GET Apr 26 02:44:32 192.168.122.209 [38422.553357] [tdb] Start Tempesta DB Apr 26 02:44:32 192.168.122.209 [38422.701990] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:44:33 192.168.122.209 [38424.089435] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38424.089435] Maybe that's fine, but it's worth checking the [38424.089435] config - if there is no relations between the [38424.089435] names, then host name confusion attack is possible. Apr 26 02:44:33 192.168.122.209 [38424.216292] [tempesta fw] Configuration processing is completed. Apr 26 02:44:33 192.168.122.209 [38424.267846] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:44:34 192.168.122.209 [38424.687246] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:44:34 192.168.122.209 [38424.713459] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:44:34 192.168.122.209 [38424.750037] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:44:34 192.168.122.209 [38424.788290] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:44:34 192.168.122.209 [38424.790031] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:44:34 192.168.122.209 [38424.840236] [tempesta fw] Tempesta FW is ready Apr 26 02:44:35 192.168.122.209 [38425.435676] [tdb] Close table 'client0.tdb' Apr 26 02:44:35 192.168.122.209 [38425.646355] [tdb] Close table 'sessions0.tdb' Apr 26 02:44:38 192.168.122.209 [38428.757211] [tdb] Close table 'cache0.tdb' Apr 26 02:44:38 192.168.122.209 [38429.011986] [tdb] Close table 'filter0.tdb' Apr 26 02:44:38 192.168.122.209 [38429.012678] [tempesta fw] modules are stopped Apr 26 02:44:38 192.168.122.209 [38429.233721] [tempesta fw] exiting... Apr 26 02:44:39 192.168.122.209 [38429.395852] [tdb] Shutdown Tempesta DB Apr 26 02:44:39 192.168.122.209 [38429.607271] End test: cache.test_conditional.TestConditionalHttp.test_none_match_nc_GET Apr 26 02:44:39 192.168.122.209 [38429.626086] Start test: cache.test_conditional.TestConditionalHttp.test_none_match_nc_HEAD Apr 26 02:44:40 192.168.122.209 [38430.806251] [tdb] Start Tempesta DB Apr 26 02:44:40 192.168.122.209 [38430.947042] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:44:42 192.168.122.209 [38432.341662] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38432.341662] Maybe that's fine, but it's worth checking the [38432.341662] config - if there is no relations between the [38432.341662] names, then host name confusion attack is possible. Apr 26 02:44:42 192.168.122.209 [38432.492409] [tempesta fw] Configuration processing is completed. Apr 26 02:44:42 192.168.122.209 [38432.541406] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:44:42 192.168.122.209 [38432.956067] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:44:42 192.168.122.209 [38432.981810] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:44:42 192.168.122.209 [38433.008423] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:44:42 192.168.122.209 [38433.048395] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:44:42 192.168.122.209 [38433.050115] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:44:42 192.168.122.209 [38433.092345] [tempesta fw] Tempesta FW is ready Apr 26 02:44:43 192.168.122.209 [38433.685892] [tdb] Close table 'client0.tdb' Apr 26 02:44:43 192.168.122.209 [38433.900422] [tdb] Close table 'sessions0.tdb' Apr 26 02:44:46 192.168.122.209 [38437.063803] [tdb] Close table 'cache0.tdb' Apr 26 02:44:47 192.168.122.209 [38437.307512] [tdb] Close table 'filter0.tdb' Apr 26 02:44:47 192.168.122.209 [38437.307959] [tempesta fw] modules are stopped Apr 26 02:44:47 192.168.122.209 [38437.540635] [tempesta fw] exiting... Apr 26 02:44:47 192.168.122.209 [38437.684962] [tdb] Shutdown Tempesta DB Apr 26 02:44:47 192.168.122.209 [38437.896128] End test: cache.test_conditional.TestConditionalHttp.test_none_match_nc_HEAD Apr 26 02:44:47 192.168.122.209 [38437.911981] Start test: cache.test_conditional.TestConditionalHttp.test_none_match_no_quotes_empty_etag Apr 26 02:44:48 192.168.122.209 [38439.180898] [tdb] Start Tempesta DB Apr 26 02:44:49 192.168.122.209 [38439.331641] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:44:50 192.168.122.209 [38440.809732] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38440.809732] Maybe that's fine, but it's worth checking the [38440.809732] config - if there is no relations between the [38440.809732] names, then host name confusion attack is possible. Apr 26 02:44:50 192.168.122.209 [38440.956519] [tempesta fw] Configuration processing is completed. Apr 26 02:44:50 192.168.122.209 [38441.005560] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:44:51 192.168.122.209 [38441.411254] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:44:51 192.168.122.209 [38441.445488] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:44:51 192.168.122.209 [38441.471005] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:44:51 192.168.122.209 [38441.540510] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:44:51 192.168.122.209 [38441.542243] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:44:51 192.168.122.209 [38441.580466] [tempesta fw] Tempesta FW is ready Apr 26 02:44:51 192.168.122.209 [38442.187023] [tdb] Close table 'client0.tdb' Apr 26 02:44:52 192.168.122.209 [38442.398795] [tdb] Close table 'sessions0.tdb' Apr 26 02:44:55 192.168.122.209 [38445.578260] [tdb] Close table 'cache0.tdb' Apr 26 02:44:55 192.168.122.209 [38445.807066] [tdb] Close table 'filter0.tdb' Apr 26 02:44:55 192.168.122.209 [38445.807502] [tempesta fw] modules are stopped Apr 26 02:44:55 192.168.122.209 [38446.044146] [tempesta fw] exiting... Apr 26 02:44:55 192.168.122.209 [38446.172000] [tdb] Shutdown Tempesta DB Apr 26 02:44:56 192.168.122.209 [38446.421872] End test: cache.test_conditional.TestConditionalHttp.test_none_match_no_quotes_empty_etag Apr 26 02:44:56 192.168.122.209 [38446.439111] Start test: cache.test_conditional.TestConditionalHttp.test_none_match_no_quotes_empty_etag_with_extra_spaces Apr 26 02:44:57 192.168.122.209 [38447.566882] [tdb] Start Tempesta DB Apr 26 02:44:57 192.168.122.209 [38447.713163] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:44:58 192.168.122.209 [38449.169846] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38449.169846] Maybe that's fine, but it's worth checking the [38449.169846] config - if there is no relations between the [38449.169846] names, then host name confusion attack is possible. Apr 26 02:44:59 192.168.122.209 [38449.320657] [tempesta fw] Configuration processing is completed. Apr 26 02:44:59 192.168.122.209 [38449.405692] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:44:59 192.168.122.209 [38449.834572] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:44:59 192.168.122.209 [38449.861744] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:44:59 192.168.122.209 [38449.889601] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:44:59 192.168.122.209 [38449.928632] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:44:59 192.168.122.209 [38449.930446] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:44:59 192.168.122.209 [38449.968572] [tempesta fw] Tempesta FW is ready Apr 26 02:45:00 192.168.122.209 [38450.560275] [tdb] Close table 'client0.tdb' Apr 26 02:45:00 192.168.122.209 [38450.768190] [tdb] Close table 'sessions0.tdb' Apr 26 02:45:03 192.168.122.209 [38454.000434] [tdb] Close table 'cache0.tdb' Apr 26 02:45:03 192.168.122.209 [38454.251709] [tdb] Close table 'filter0.tdb' Apr 26 02:45:03 192.168.122.209 [38454.252137] [tempesta fw] modules are stopped Apr 26 02:45:04 192.168.122.209 [38454.451835] [tempesta fw] exiting... Apr 26 02:45:04 192.168.122.209 [38454.574277] [tdb] Shutdown Tempesta DB Apr 26 02:45:04 192.168.122.209 [38454.829667] End test: cache.test_conditional.TestConditionalHttp.test_none_match_no_quotes_empty_etag_with_extra_spaces Apr 26 02:45:04 192.168.122.209 [38454.854505] Start test: cache.test_conditional.TestConditionalHttp.test_none_match_no_quotes_etag Apr 26 02:45:05 192.168.122.209 [38456.026559] [tdb] Start Tempesta DB Apr 26 02:45:05 192.168.122.209 [38456.170502] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:45:07 192.168.122.209 [38457.637997] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38457.637997] Maybe that's fine, but it's worth checking the [38457.637997] config - if there is no relations between the [38457.637997] names, then host name confusion attack is possible. Apr 26 02:45:07 192.168.122.209 [38457.776722] [tempesta fw] Configuration processing is completed. Apr 26 02:45:07 192.168.122.209 [38457.833897] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:45:07 192.168.122.209 [38458.234664] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:45:07 192.168.122.209 [38458.269420] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:45:08 192.168.122.209 [38458.294301] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:45:08 192.168.122.209 [38458.336720] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:45:08 192.168.122.209 [38458.338443] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:45:08 192.168.122.209 [38458.376629] [tempesta fw] Tempesta FW is ready Apr 26 02:45:08 192.168.122.209 [38458.961784] [tdb] Close table 'client0.tdb' Apr 26 02:45:08 192.168.122.209 [38459.163707] [tdb] Close table 'sessions0.tdb' Apr 26 02:45:12 192.168.122.209 [38462.331155] [tdb] Close table 'cache0.tdb' Apr 26 02:45:12 192.168.122.209 [38462.577449] [tdb] Close table 'filter0.tdb' Apr 26 02:45:12 192.168.122.209 [38462.577899] [tempesta fw] modules are stopped Apr 26 02:45:12 192.168.122.209 [38462.805587] [tempesta fw] exiting... Apr 26 02:45:12 192.168.122.209 [38462.950537] [tdb] Shutdown Tempesta DB Apr 26 02:45:12 192.168.122.209 [38463.194419] End test: cache.test_conditional.TestConditionalHttp.test_none_match_no_quotes_etag Apr 26 02:45:12 192.168.122.209 [38463.208118] Start test: cache.test_conditional.TestConditionalHttp.test_none_match_no_quotes_etag_with_extra_spaces Apr 26 02:45:14 192.168.122.209 [38464.383329] [tdb] Start Tempesta DB Apr 26 02:45:14 192.168.122.209 [38464.548036] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:45:15 192.168.122.209 [38466.021583] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38466.021583] Maybe that's fine, but it's worth checking the [38466.021583] config - if there is no relations between the [38466.021583] names, then host name confusion attack is possible. Apr 26 02:45:15 192.168.122.209 [38466.160838] [tempesta fw] Configuration processing is completed. Apr 26 02:45:15 192.168.122.209 [38466.217500] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:45:16 192.168.122.209 [38466.639878] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:45:16 192.168.122.209 [38466.665688] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:45:16 192.168.122.209 [38466.691276] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:45:16 192.168.122.209 [38466.732855] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:45:16 192.168.122.209 [38466.734588] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:45:16 192.168.122.209 [38466.784821] [tempesta fw] Tempesta FW is ready Apr 26 02:45:17 192.168.122.209 [38467.452474] [tdb] Close table 'client0.tdb' Apr 26 02:45:17 192.168.122.209 [38467.639934] [tdb] Close table 'sessions0.tdb' Apr 26 02:45:20 192.168.122.209 [38470.764642] [tdb] Close table 'cache0.tdb' Apr 26 02:45:20 192.168.122.209 [38471.007194] [tdb] Close table 'filter0.tdb' Apr 26 02:45:20 192.168.122.209 [38471.007638] [tempesta fw] modules are stopped Apr 26 02:45:20 192.168.122.209 [38471.188032] [tempesta fw] exiting... Apr 26 02:45:21 192.168.122.209 [38471.330071] [tdb] Shutdown Tempesta DB Apr 26 02:45:21 192.168.122.209 [38471.574002] End test: cache.test_conditional.TestConditionalHttp.test_none_match_no_quotes_etag_with_extra_spaces Apr 26 02:45:21 192.168.122.209 [38471.585804] Start test: cache.test_conditional.TestConditionalHttp.test_none_match_weak_all Apr 26 02:45:22 192.168.122.209 [38472.791554] [tdb] Start Tempesta DB Apr 26 02:45:22 192.168.122.209 [38472.938539] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:45:24 192.168.122.209 [38474.322196] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38474.322196] Maybe that's fine, but it's worth checking the [38474.322196] config - if there is no relations between the [38474.322196] names, then host name confusion attack is possible. Apr 26 02:45:24 192.168.122.209 [38474.485013] [tempesta fw] Configuration processing is completed. Apr 26 02:45:24 192.168.122.209 [38474.574596] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:45:24 192.168.122.209 [38474.987099] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:45:24 192.168.122.209 [38475.013455] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:45:24 192.168.122.209 [38475.040347] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:45:24 192.168.122.209 [38475.092972] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:45:24 192.168.122.209 [38475.094693] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:45:24 192.168.122.209 [38475.132903] [tempesta fw] Tempesta FW is ready Apr 26 02:45:25 192.168.122.209 [38475.723170] [tdb] Close table 'client0.tdb' Apr 26 02:45:25 192.168.122.209 [38475.917876] [tdb] Close table 'sessions0.tdb' Apr 26 02:45:28 192.168.122.209 [38479.089415] [tdb] Close table 'cache0.tdb' Apr 26 02:45:29 192.168.122.209 [38479.338075] [tdb] Close table 'filter0.tdb' Apr 26 02:45:29 192.168.122.209 [38479.338525] [tempesta fw] modules are stopped Apr 26 02:45:29 192.168.122.209 [38479.568532] [tempesta fw] exiting... Apr 26 02:45:29 192.168.122.209 [38479.718108] [tdb] Shutdown Tempesta DB Apr 26 02:45:29 192.168.122.209 [38479.936277] End test: cache.test_conditional.TestConditionalHttp.test_none_match_weak_all Apr 26 02:45:29 192.168.122.209 [38479.950546] Start test: cache.test_conditional.TestConditionalHttp.test_none_match_weak_clnt Apr 26 02:45:30 192.168.122.209 [38481.173981] [tdb] Start Tempesta DB Apr 26 02:45:31 192.168.122.209 [38481.332373] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:45:32 192.168.122.209 [38482.750368] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38482.750368] Maybe that's fine, but it's worth checking the [38482.750368] config - if there is no relations between the [38482.750368] names, then host name confusion attack is possible. Apr 26 02:45:32 192.168.122.209 [38482.885136] [tempesta fw] Configuration processing is completed. Apr 26 02:45:32 192.168.122.209 [38482.934580] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:45:33 192.168.122.209 [38483.392328] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:45:33 192.168.122.209 [38483.421158] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:45:33 192.168.122.209 [38483.454710] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:45:33 192.168.122.209 [38483.537065] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:45:33 192.168.122.209 [38483.538810] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:45:33 192.168.122.209 [38483.577017] [tempesta fw] Tempesta FW is ready Apr 26 02:45:33 192.168.122.209 [38484.185702] [tdb] Close table 'client0.tdb' Apr 26 02:45:34 192.168.122.209 [38484.402898] [tdb] Close table 'sessions0.tdb' Apr 26 02:45:37 192.168.122.209 [38487.618851] [tdb] Close table 'cache0.tdb' Apr 26 02:45:37 192.168.122.209 [38487.863966] [tdb] Close table 'filter0.tdb' Apr 26 02:45:37 192.168.122.209 [38487.864412] [tempesta fw] modules are stopped Apr 26 02:45:37 192.168.122.209 [38488.052223] [tempesta fw] exiting... Apr 26 02:45:37 192.168.122.209 [38488.200728] [tdb] Shutdown Tempesta DB Apr 26 02:45:38 192.168.122.209 [38488.419951] End test: cache.test_conditional.TestConditionalHttp.test_none_match_weak_clnt Apr 26 02:45:38 192.168.122.209 [38488.432278] Start test: cache.test_conditional.TestConditionalHttp.test_none_match_weak_srv Apr 26 02:45:39 192.168.122.209 [38489.636869] [tdb] Start Tempesta DB Apr 26 02:45:39 192.168.122.209 [38489.798161] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:45:40 192.168.122.209 [38491.206485] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38491.206485] Maybe that's fine, but it's worth checking the [38491.206485] config - if there is no relations between the [38491.206485] names, then host name confusion attack is possible. Apr 26 02:45:41 192.168.122.209 [38491.353255] [tempesta fw] Configuration processing is completed. Apr 26 02:45:41 192.168.122.209 [38491.413028] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:45:41 192.168.122.209 [38491.828983] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:45:41 192.168.122.209 [38491.856238] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:45:41 192.168.122.209 [38491.883530] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:45:41 192.168.122.209 [38491.937173] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:45:41 192.168.122.209 [38491.938936] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:45:41 192.168.122.209 [38491.981103] [tempesta fw] Tempesta FW is ready Apr 26 02:45:42 192.168.122.209 [38492.579832] [tdb] Close table 'client0.tdb' Apr 26 02:45:42 192.168.122.209 [38492.785703] [tdb] Close table 'sessions0.tdb' Apr 26 02:45:45 192.168.122.209 [38495.975316] [tdb] Close table 'cache0.tdb' Apr 26 02:45:45 192.168.122.209 [38496.227086] [tdb] Close table 'filter0.tdb' Apr 26 02:45:45 192.168.122.209 [38496.227505] [tempesta fw] modules are stopped Apr 26 02:45:46 192.168.122.209 [38496.403081] [tempesta fw] exiting... Apr 26 02:45:46 192.168.122.209 [38496.542945] [tdb] Shutdown Tempesta DB Apr 26 02:45:46 192.168.122.209 [38496.778409] End test: cache.test_conditional.TestConditionalHttp.test_none_match_weak_srv Apr 26 02:45:46 192.168.122.209 [38496.792649] Start test: cache.test_conditional.TestConditionalHttp.test_response_without_last_modified Apr 26 02:45:47 192.168.122.209 [38498.003717] [tdb] Start Tempesta DB Apr 26 02:45:47 192.168.122.209 [38498.169920] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:45:49 192.168.122.209 [38499.526605] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38499.526605] Maybe that's fine, but it's worth checking the [38499.526605] config - if there is no relations between the [38499.526605] names, then host name confusion attack is possible. Apr 26 02:45:49 192.168.122.209 [38499.661276] [tempesta fw] Configuration processing is completed. Apr 26 02:45:49 192.168.122.209 [38499.713797] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:45:49 192.168.122.209 [38500.154354] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:45:49 192.168.122.209 [38500.183670] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:45:49 192.168.122.209 [38500.216995] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:45:49 192.168.122.209 [38500.261304] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:45:49 192.168.122.209 [38500.263037] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:45:50 192.168.122.209 [38500.309221] [tempesta fw] Tempesta FW is ready Apr 26 02:45:50 192.168.122.209 [38500.924152] [tdb] Close table 'client0.tdb' Apr 26 02:45:50 192.168.122.209 [38501.120687] [tdb] Close table 'sessions0.tdb' Apr 26 02:45:53 192.168.122.209 [38504.287073] [tdb] Close table 'cache0.tdb' Apr 26 02:45:54 192.168.122.209 [38504.517097] [tdb] Close table 'filter0.tdb' Apr 26 02:45:54 192.168.122.209 [38504.517551] [tempesta fw] modules are stopped Apr 26 02:45:54 192.168.122.209 [38504.784689] [tempesta fw] exiting... Apr 26 02:45:54 192.168.122.209 [38504.913391] [tdb] Shutdown Tempesta DB Apr 26 02:45:54 192.168.122.209 [38505.127412] End test: cache.test_conditional.TestConditionalHttp.test_response_without_last_modified Apr 26 02:45:54 192.168.122.209 [38505.166190] Start test: cache.test_conditional.TestConditionalHttp.test_response_without_last_modified_and_date Apr 26 02:45:56 192.168.122.209 [38506.336683] [tdb] Start Tempesta DB Apr 26 02:45:56 192.168.122.209 [38506.504944] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:45:57 192.168.122.209 [38507.922630] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38507.922630] Maybe that's fine, but it's worth checking the [38507.922630] config - if there is no relations between the [38507.922630] names, then host name confusion attack is possible. Apr 26 02:45:57 192.168.122.209 [38508.061324] [tempesta fw] Configuration processing is completed. Apr 26 02:45:57 192.168.122.209 [38508.111613] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:45:58 192.168.122.209 [38508.543495] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:45:58 192.168.122.209 [38508.574401] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:45:58 192.168.122.209 [38508.606230] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:45:58 192.168.122.209 [38508.665398] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:45:58 192.168.122.209 [38508.667308] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:45:58 192.168.122.209 [38508.701336] [tempesta fw] Tempesta FW is ready Apr 26 02:45:58 192.168.122.209 [38509.283561] [tdb] Close table 'client0.tdb' Apr 26 02:45:59 192.168.122.209 [38509.549941] [tdb] Close table 'sessions0.tdb' Apr 26 02:46:02 192.168.122.209 [38512.769368] [tdb] Close table 'cache0.tdb' Apr 26 02:46:02 192.168.122.209 [38513.035080] [tdb] Close table 'filter0.tdb' Apr 26 02:46:02 192.168.122.209 [38513.035531] [tempesta fw] modules are stopped Apr 26 02:46:02 192.168.122.209 [38513.208039] [tempesta fw] exiting... Apr 26 02:46:03 192.168.122.209 [38513.397986] [tdb] Shutdown Tempesta DB Apr 26 02:46:03 192.168.122.209 [38513.625772] End test: cache.test_conditional.TestConditionalHttp.test_response_without_last_modified_and_date Apr 26 02:46:03 192.168.122.209 [38513.653766] Start test: cache.test_conditional.TestConditionalHttp.test_response_without_last_modified_and_date_nc Apr 26 02:46:04 192.168.122.209 [38514.871497] [tdb] Start Tempesta DB Apr 26 02:46:04 192.168.122.209 [38515.023097] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:46:06 192.168.122.209 [38516.442758] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38516.442758] Maybe that's fine, but it's worth checking the [38516.442758] config - if there is no relations between the [38516.442758] names, then host name confusion attack is possible. Apr 26 02:46:06 192.168.122.209 [38516.593528] [tempesta fw] Configuration processing is completed. Apr 26 02:46:06 192.168.122.209 [38516.663327] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:46:06 192.168.122.209 [38517.076228] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:46:06 192.168.122.209 [38517.101662] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:46:06 192.168.122.209 [38517.127364] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:46:06 192.168.122.209 [38517.173501] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:46:06 192.168.122.209 [38517.175257] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:46:06 192.168.122.209 [38517.217431] [tempesta fw] Tempesta FW is ready Apr 26 02:46:07 192.168.122.209 [38517.842334] [tdb] Close table 'client0.tdb' Apr 26 02:46:07 192.168.122.209 [38518.035130] [tdb] Close table 'sessions0.tdb' Apr 26 02:46:10 192.168.122.209 [38521.240649] [tdb] Close table 'cache0.tdb' Apr 26 02:46:11 192.168.122.209 [38521.480994] [tdb] Close table 'filter0.tdb' Apr 26 02:46:11 192.168.122.209 [38521.481481] [tempesta fw] modules are stopped Apr 26 02:46:11 192.168.122.209 [38521.701934] [tempesta fw] exiting... Apr 26 02:46:11 192.168.122.209 [38521.845163] [tdb] Shutdown Tempesta DB Apr 26 02:46:11 192.168.122.209 [38522.085940] End test: cache.test_conditional.TestConditionalHttp.test_response_without_last_modified_and_date_nc Apr 26 02:46:11 192.168.122.209 [38522.097641] Start test: cache.test_conditional.TestConditionalHttp.test_response_without_last_modified_nc Apr 26 02:46:13 192.168.122.209 [38523.310425] [tdb] Start Tempesta DB Apr 26 02:46:13 192.168.122.209 [38523.448533] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:46:14 192.168.122.209 [38524.898834] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38524.898834] Maybe that's fine, but it's worth checking the [38524.898834] config - if there is no relations between the [38524.898834] names, then host name confusion attack is possible. Apr 26 02:46:14 192.168.122.209 [38525.037614] [tempesta fw] Configuration processing is completed. Apr 26 02:46:14 192.168.122.209 [38525.086900] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:46:15 192.168.122.209 [38525.497883] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:46:15 192.168.122.209 [38525.528330] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:46:15 192.168.122.209 [38525.560431] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:46:15 192.168.122.209 [38525.605607] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:46:15 192.168.122.209 [38525.607345] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:46:15 192.168.122.209 [38525.645534] [tempesta fw] Tempesta FW is ready Apr 26 02:46:15 192.168.122.209 [38526.260652] [tdb] Close table 'client0.tdb' Apr 26 02:46:16 192.168.122.209 [38526.459547] [tdb] Close table 'sessions0.tdb' Apr 26 02:46:19 192.168.122.209 [38529.586239] [tdb] Close table 'cache0.tdb' Apr 26 02:46:19 192.168.122.209 [38529.814516] [tdb] Close table 'filter0.tdb' Apr 26 02:46:19 192.168.122.209 [38529.814945] [tempesta fw] modules are stopped Apr 26 02:46:19 192.168.122.209 [38530.011322] [tempesta fw] exiting... Apr 26 02:46:19 192.168.122.209 [38530.183333] [tdb] Shutdown Tempesta DB Apr 26 02:46:20 192.168.122.209 [38530.407805] End test: cache.test_conditional.TestConditionalHttp.test_response_without_last_modified_nc Apr 26 02:46:20 192.168.122.209 [38530.423034] Start test: cache.test_conditional.TestNotModifiedResponseHeadersH2.test_cachable_headers_cache_control Apr 26 02:46:21 192.168.122.209 [38531.563282] [tdb] Start Tempesta DB Apr 26 02:46:21 192.168.122.209 [38531.707976] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:46:22 192.168.122.209 [38533.134985] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38533.134985] Maybe that's fine, but it's worth checking the [38533.134985] config - if there is no relations between the [38533.134985] names, then host name confusion attack is possible. Apr 26 02:46:22 192.168.122.209 [38533.277697] [tempesta fw] Configuration processing is completed. Apr 26 02:46:23 192.168.122.209 [38533.340239] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:46:23 192.168.122.209 [38533.766669] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:46:23 192.168.122.209 [38533.793149] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:46:23 192.168.122.209 [38533.819463] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:46:23 192.168.122.209 [38533.865734] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:46:23 192.168.122.209 [38533.867478] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:46:23 192.168.122.209 [38533.917644] [tempesta fw] Tempesta FW is ready Apr 26 02:46:24 192.168.122.209 [38534.511360] [tdb] Close table 'client0.tdb' Apr 26 02:46:24 192.168.122.209 [38534.712820] [tdb] Close table 'sessions0.tdb' Apr 26 02:46:27 192.168.122.209 [38537.848631] [tdb] Close table 'cache0.tdb' Apr 26 02:46:27 192.168.122.209 [38538.127899] [tdb] Close table 'filter0.tdb' Apr 26 02:46:27 192.168.122.209 [38538.128336] [tempesta fw] modules are stopped Apr 26 02:46:28 192.168.122.209 [38538.327639] [tempesta fw] exiting... Apr 26 02:46:28 192.168.122.209 [38538.464888] [tdb] Shutdown Tempesta DB Apr 26 02:46:28 192.168.122.209 [38538.689900] End test: cache.test_conditional.TestNotModifiedResponseHeadersH2.test_cachable_headers_cache_control Apr 26 02:46:28 192.168.122.209 [38538.705007] Start test: cache.test_conditional.TestNotModifiedResponseHeadersH2.test_cachable_headers_content_location Apr 26 02:46:29 192.168.122.209 [38539.935081] [tdb] Start Tempesta DB Apr 26 02:46:29 192.168.122.209 [38540.086221] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:46:31 192.168.122.209 [38541.527051] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38541.527051] Maybe that's fine, but it's worth checking the [38541.527051] config - if there is no relations between the [38541.527051] names, then host name confusion attack is possible. Apr 26 02:46:31 192.168.122.209 [38541.681714] [tempesta fw] Configuration processing is completed. Apr 26 02:46:31 192.168.122.209 [38541.732171] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:46:31 192.168.122.209 [38542.164841] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:46:31 192.168.122.209 [38542.190731] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:46:31 192.168.122.209 [38542.216782] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:46:31 192.168.122.209 [38542.273815] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:46:31 192.168.122.209 [38542.275539] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:46:32 192.168.122.209 [38542.313791] [tempesta fw] Tempesta FW is ready Apr 26 02:46:32 192.168.122.209 [38542.930503] [tdb] Close table 'client0.tdb' Apr 26 02:46:32 192.168.122.209 [38543.134931] [tdb] Close table 'sessions0.tdb' Apr 26 02:46:36 192.168.122.209 [38546.324090] [tdb] Close table 'cache0.tdb' Apr 26 02:46:36 192.168.122.209 [38546.560239] [tdb] Close table 'filter0.tdb' Apr 26 02:46:36 192.168.122.209 [38546.560675] [tempesta fw] modules are stopped Apr 26 02:46:36 192.168.122.209 [38546.745311] [tempesta fw] exiting... Apr 26 02:46:36 192.168.122.209 [38546.898083] [tdb] Shutdown Tempesta DB Apr 26 02:46:36 192.168.122.209 [38547.135908] End test: cache.test_conditional.TestNotModifiedResponseHeadersH2.test_cachable_headers_content_location Apr 26 02:46:36 192.168.122.209 [38547.146976] Start test: cache.test_conditional.TestNotModifiedResponseHeadersH2.test_cachable_headers_etag Apr 26 02:46:38 192.168.122.209 [38548.350823] [tdb] Start Tempesta DB Apr 26 02:46:38 192.168.122.209 [38548.496965] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:46:39 192.168.122.209 [38549.971132] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38549.971132] Maybe that's fine, but it's worth checking the [38549.971132] config - if there is no relations between the [38549.971132] names, then host name confusion attack is possible. Apr 26 02:46:39 192.168.122.209 [38550.109911] [tempesta fw] Configuration processing is completed. Apr 26 02:46:39 192.168.122.209 [38550.159953] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:46:40 192.168.122.209 [38550.574059] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:46:40 192.168.122.209 [38550.600099] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:46:40 192.168.122.209 [38550.626462] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:46:40 192.168.122.209 [38550.681914] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:46:40 192.168.122.209 [38550.683665] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:46:40 192.168.122.209 [38550.721864] [tempesta fw] Tempesta FW is ready Apr 26 02:46:41 192.168.122.209 [38551.349998] [tdb] Close table 'client0.tdb' Apr 26 02:46:41 192.168.122.209 [38551.556830] [tdb] Close table 'sessions0.tdb' Apr 26 02:46:44 192.168.122.209 [38554.728664] [tdb] Close table 'cache0.tdb' Apr 26 02:46:44 192.168.122.209 [38554.959544] [tdb] Close table 'filter0.tdb' Apr 26 02:46:44 192.168.122.209 [38554.959979] [tempesta fw] modules are stopped Apr 26 02:46:44 192.168.122.209 [38555.157965] [tempesta fw] exiting... Apr 26 02:46:45 192.168.122.209 [38555.314225] [tdb] Shutdown Tempesta DB Apr 26 02:46:45 192.168.122.209 [38555.557943] End test: cache.test_conditional.TestNotModifiedResponseHeadersH2.test_cachable_headers_etag Apr 26 02:46:45 192.168.122.209 [38555.575287] Start test: cache.test_conditional.TestNotModifiedResponseHeadersH2.test_cachable_headers_expires Apr 26 02:46:46 192.168.122.209 [38556.753826] [tdb] Start Tempesta DB Apr 26 02:46:46 192.168.122.209 [38556.897872] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:46:48 192.168.122.209 [38558.327294] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38558.327294] Maybe that's fine, but it's worth checking the [38558.327294] config - if there is no relations between the [38558.327294] names, then host name confusion attack is possible. Apr 26 02:46:48 192.168.122.209 [38558.462050] [tempesta fw] Configuration processing is completed. Apr 26 02:46:48 192.168.122.209 [38558.513359] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:46:48 192.168.122.209 [38558.955300] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:46:48 192.168.122.209 [38558.981167] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:46:48 192.168.122.209 [38559.007626] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:46:48 192.168.122.209 [38559.086053] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:46:48 192.168.122.209 [38559.087806] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:46:48 192.168.122.209 [38559.129972] [tempesta fw] Tempesta FW is ready Apr 26 02:46:49 192.168.122.209 [38559.750130] [tdb] Close table 'client0.tdb' Apr 26 02:46:49 192.168.122.209 [38559.940091] [tdb] Close table 'sessions0.tdb' Apr 26 02:46:52 192.168.122.209 [38563.148245] [tdb] Close table 'cache0.tdb' Apr 26 02:46:53 192.168.122.209 [38563.431336] [tdb] Close table 'filter0.tdb' Apr 26 02:46:53 192.168.122.209 [38563.431821] [tempesta fw] modules are stopped Apr 26 02:46:53 192.168.122.209 [38563.616021] [tempesta fw] exiting... Apr 26 02:46:53 192.168.122.209 [38563.801348] [tdb] Shutdown Tempesta DB Apr 26 02:46:53 192.168.122.209 [38564.002863] End test: cache.test_conditional.TestNotModifiedResponseHeadersH2.test_cachable_headers_expires Apr 26 02:46:53 192.168.122.209 [38564.024432] Start test: cache.test_conditional.TestNotModifiedResponseHeadersH2.test_cachable_headers_vary Apr 26 02:46:54 192.168.122.209 [38565.135982] [tdb] Start Tempesta DB Apr 26 02:46:54 192.168.122.209 [38565.281247] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:46:56 192.168.122.209 [38566.727575] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38566.727575] Maybe that's fine, but it's worth checking the [38566.727575] config - if there is no relations between the [38566.727575] names, then host name confusion attack is possible. Apr 26 02:46:56 192.168.122.209 [38566.882155] [tempesta fw] Configuration processing is completed. Apr 26 02:46:56 192.168.122.209 [38566.932380] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:46:57 192.168.122.209 [38567.365753] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:46:57 192.168.122.209 [38567.392986] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:46:57 192.168.122.209 [38567.420180] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:46:57 192.168.122.209 [38567.482172] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:46:57 192.168.122.209 [38567.483946] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:46:57 192.168.122.209 [38567.526106] [tempesta fw] Tempesta FW is ready Apr 26 02:46:57 192.168.122.209 [38568.134420] [tdb] Close table 'client0.tdb' Apr 26 02:46:58 192.168.122.209 [38568.324833] [tdb] Close table 'sessions0.tdb' Apr 26 02:47:01 192.168.122.209 [38571.497339] [tdb] Close table 'cache0.tdb' Apr 26 02:47:01 192.168.122.209 [38571.713209] [tdb] Close table 'filter0.tdb' Apr 26 02:47:01 192.168.122.209 [38571.713650] [tempesta fw] modules are stopped Apr 26 02:47:01 192.168.122.209 [38571.893928] [tempesta fw] exiting... Apr 26 02:47:01 192.168.122.209 [38572.038264] [tdb] Shutdown Tempesta DB Apr 26 02:47:01 192.168.122.209 [38572.272174] End test: cache.test_conditional.TestNotModifiedResponseHeadersH2.test_cachable_headers_vary Apr 26 02:47:02 192.168.122.209 [38572.315537] Start test: cache.test_conditional.TestNotModifiedResponseHeadersH2.test_non_cachable_header Apr 26 02:47:03 192.168.122.209 [38573.543487] [tdb] Start Tempesta DB Apr 26 02:47:03 192.168.122.209 [38573.710881] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:47:04 192.168.122.209 [38575.171592] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38575.171592] Maybe that's fine, but it's worth checking the [38575.171592] config - if there is no relations between the [38575.171592] names, then host name confusion attack is possible. Apr 26 02:47:05 192.168.122.209 [38575.310344] [tempesta fw] Configuration processing is completed. Apr 26 02:47:05 192.168.122.209 [38575.393947] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:47:05 192.168.122.209 [38575.823748] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:47:05 192.168.122.209 [38575.850610] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:47:05 192.168.122.209 [38575.877992] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:47:05 192.168.122.209 [38575.942245] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:47:05 192.168.122.209 [38575.943975] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:47:05 192.168.122.209 [38575.994182] [tempesta fw] Tempesta FW is ready Apr 26 02:47:06 192.168.122.209 [38576.637079] [tdb] Close table 'client0.tdb' Apr 26 02:47:06 192.168.122.209 [38576.827366] [tdb] Close table 'sessions0.tdb' Apr 26 02:47:09 192.168.122.209 [38580.018930] [tdb] Close table 'cache0.tdb' Apr 26 02:47:09 192.168.122.209 [38580.258179] [tdb] Close table 'filter0.tdb' Apr 26 02:47:09 192.168.122.209 [38580.258633] [tempesta fw] modules are stopped Apr 26 02:47:10 192.168.122.209 [38580.521325] [tempesta fw] exiting... Apr 26 02:47:10 192.168.122.209 [38580.676525] [tdb] Shutdown Tempesta DB Apr 26 02:47:10 192.168.122.209 [38580.918390] End test: cache.test_conditional.TestNotModifiedResponseHeadersH2.test_non_cachable_header Apr 26 02:47:10 192.168.122.209 [38580.937962] Start test: cache.test_conditional.TestNotModifiedResponseHeadersHttp.test_cachable_headers_cache_control Apr 26 02:47:11 192.168.122.209 [38582.152961] [tdb] Start Tempesta DB Apr 26 02:47:12 192.168.122.209 [38582.296694] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:47:13 192.168.122.209 [38583.691613] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38583.691613] Maybe that's fine, but it's worth checking the [38583.691613] config - if there is no relations between the [38583.691613] names, then host name confusion attack is possible. Apr 26 02:47:13 192.168.122.209 [38583.838394] [tempesta fw] Configuration processing is completed. Apr 26 02:47:13 192.168.122.209 [38583.889254] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:47:14 192.168.122.209 [38584.298204] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:47:14 192.168.122.209 [38584.323864] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:47:14 192.168.122.209 [38584.348816] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:47:14 192.168.122.209 [38584.398351] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:47:14 192.168.122.209 [38584.400103] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:47:14 192.168.122.209 [38584.446300] [tempesta fw] Tempesta FW is ready Apr 26 02:47:14 192.168.122.209 [38585.053489] [tdb] Close table 'client0.tdb' Apr 26 02:47:14 192.168.122.209 [38585.242916] [tdb] Close table 'sessions0.tdb' Apr 26 02:47:18 192.168.122.209 [38588.412118] [tdb] Close table 'cache0.tdb' Apr 26 02:47:18 192.168.122.209 [38588.662935] [tdb] Close table 'filter0.tdb' Apr 26 02:47:18 192.168.122.209 [38588.663368] [tempesta fw] modules are stopped Apr 26 02:47:18 192.168.122.209 [38588.883259] [tempesta fw] exiting... Apr 26 02:47:18 192.168.122.209 [38589.009287] [tdb] Shutdown Tempesta DB Apr 26 02:47:18 192.168.122.209 [38589.218973] End test: cache.test_conditional.TestNotModifiedResponseHeadersHttp.test_cachable_headers_cache_control Apr 26 02:47:18 192.168.122.209 [38589.235160] Start test: cache.test_conditional.TestNotModifiedResponseHeadersHttp.test_cachable_headers_content_location Apr 26 02:47:20 192.168.122.209 [38590.396282] [tdb] Start Tempesta DB Apr 26 02:47:20 192.168.122.209 [38590.541264] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:47:21 192.168.122.209 [38591.987713] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38591.987713] Maybe that's fine, but it's worth checking the [38591.987713] config - if there is no relations between the [38591.987713] names, then host name confusion attack is possible. Apr 26 02:47:21 192.168.122.209 [38592.134561] [tempesta fw] Configuration processing is completed. Apr 26 02:47:21 192.168.122.209 [38592.183811] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:47:22 192.168.122.209 [38592.618040] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:47:22 192.168.122.209 [38592.643069] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:47:22 192.168.122.209 [38592.675140] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:47:22 192.168.122.209 [38592.730462] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:47:22 192.168.122.209 [38592.732220] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:47:22 192.168.122.209 [38592.778412] [tempesta fw] Tempesta FW is ready Apr 26 02:47:23 192.168.122.209 [38593.399222] [tdb] Close table 'client0.tdb' Apr 26 02:47:23 192.168.122.209 [38593.593538] [tdb] Close table 'sessions0.tdb' Apr 26 02:47:26 192.168.122.209 [38596.767997] [tdb] Close table 'cache0.tdb' Apr 26 02:47:26 192.168.122.209 [38596.997381] [tdb] Close table 'filter0.tdb' Apr 26 02:47:26 192.168.122.209 [38596.997803] [tempesta fw] modules are stopped Apr 26 02:47:26 192.168.122.209 [38597.189808] [tempesta fw] exiting... Apr 26 02:47:27 192.168.122.209 [38597.338097] [tdb] Shutdown Tempesta DB Apr 26 02:47:27 192.168.122.209 [38597.572395] End test: cache.test_conditional.TestNotModifiedResponseHeadersHttp.test_cachable_headers_content_location Apr 26 02:47:27 192.168.122.209 [38597.589878] Start test: cache.test_conditional.TestNotModifiedResponseHeadersHttp.test_cachable_headers_etag Apr 26 02:47:28 192.168.122.209 [38598.745141] [tdb] Start Tempesta DB Apr 26 02:47:28 192.168.122.209 [38598.896285] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:47:30 192.168.122.209 [38600.375841] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38600.375841] Maybe that's fine, but it's worth checking the [38600.375841] config - if there is no relations between the [38600.375841] names, then host name confusion attack is possible. Apr 26 02:47:30 192.168.122.209 [38600.510630] [tempesta fw] Configuration processing is completed. Apr 26 02:47:30 192.168.122.209 [38600.563764] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:47:30 192.168.122.209 [38600.977502] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:47:30 192.168.122.209 [38601.002987] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:47:30 192.168.122.209 [38601.028535] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:47:30 192.168.122.209 [38601.070566] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:47:30 192.168.122.209 [38601.072304] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:47:30 192.168.122.209 [38601.110512] [tempesta fw] Tempesta FW is ready Apr 26 02:47:31 192.168.122.209 [38601.751105] [tdb] Close table 'client0.tdb' Apr 26 02:47:31 192.168.122.209 [38601.947252] [tdb] Close table 'sessions0.tdb' Apr 26 02:47:34 192.168.122.209 [38605.054217] [tdb] Close table 'cache0.tdb' Apr 26 02:47:35 192.168.122.209 [38605.309353] [tdb] Close table 'filter0.tdb' Apr 26 02:47:35 192.168.122.209 [38605.309791] [tempesta fw] modules are stopped Apr 26 02:47:35 192.168.122.209 [38605.514563] [tempesta fw] exiting... Apr 26 02:47:35 192.168.122.209 [38605.658203] [tdb] Shutdown Tempesta DB Apr 26 02:47:35 192.168.122.209 [38605.913505] End test: cache.test_conditional.TestNotModifiedResponseHeadersHttp.test_cachable_headers_etag Apr 26 02:47:35 192.168.122.209 [38605.932209] Start test: cache.test_conditional.TestNotModifiedResponseHeadersHttp.test_cachable_headers_expires Apr 26 02:47:36 192.168.122.209 [38607.111004] [tdb] Start Tempesta DB Apr 26 02:47:36 192.168.122.209 [38607.250925] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:47:38 192.168.122.209 [38608.691972] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38608.691972] Maybe that's fine, but it's worth checking the [38608.691972] config - if there is no relations between the [38608.691972] names, then host name confusion attack is possible. Apr 26 02:47:38 192.168.122.209 [38608.830693] [tempesta fw] Configuration processing is completed. Apr 26 02:47:38 192.168.122.209 [38608.883455] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:47:39 192.168.122.209 [38609.313795] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:47:39 192.168.122.209 [38609.340305] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:47:39 192.168.122.209 [38609.367483] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:47:39 192.168.122.209 [38609.406675] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:47:39 192.168.122.209 [38609.408425] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:47:39 192.168.122.209 [38609.446618] [tempesta fw] Tempesta FW is ready Apr 26 02:47:39 192.168.122.209 [38610.072095] [tdb] Close table 'client0.tdb' Apr 26 02:47:39 192.168.122.209 [38610.275735] [tdb] Close table 'sessions0.tdb' Apr 26 02:47:43 192.168.122.209 [38613.446493] [tdb] Close table 'cache0.tdb' Apr 26 02:47:43 192.168.122.209 [38613.690769] [tdb] Close table 'filter0.tdb' Apr 26 02:47:43 192.168.122.209 [38613.691203] [tempesta fw] modules are stopped Apr 26 02:47:43 192.168.122.209 [38613.926503] [tempesta fw] exiting... Apr 26 02:47:43 192.168.122.209 [38614.102067] [tdb] Shutdown Tempesta DB Apr 26 02:47:44 192.168.122.209 [38614.330195] End test: cache.test_conditional.TestNotModifiedResponseHeadersHttp.test_cachable_headers_expires Apr 26 02:47:44 192.168.122.209 [38614.356259] Start test: cache.test_conditional.TestNotModifiedResponseHeadersHttp.test_cachable_headers_vary Apr 26 02:47:45 192.168.122.209 [38615.545002] [tdb] Start Tempesta DB Apr 26 02:47:45 192.168.122.209 [38615.702712] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:47:46 192.168.122.209 [38617.160038] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38617.160038] Maybe that's fine, but it's worth checking the [38617.160038] config - if there is no relations between the [38617.160038] names, then host name confusion attack is possible. Apr 26 02:47:47 192.168.122.209 [38617.295136] [tempesta fw] Configuration processing is completed. Apr 26 02:47:47 192.168.122.209 [38617.347152] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:47:47 192.168.122.209 [38617.762914] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:47:47 192.168.122.209 [38617.799852] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:47:47 192.168.122.209 [38617.825550] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:47:47 192.168.122.209 [38617.866815] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:47:47 192.168.122.209 [38617.868539] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:47:47 192.168.122.209 [38617.910742] [tempesta fw] Tempesta FW is ready Apr 26 02:47:48 192.168.122.209 [38618.530645] [tdb] Close table 'client0.tdb' Apr 26 02:47:48 192.168.122.209 [38618.730193] [tdb] Close table 'sessions0.tdb' Apr 26 02:47:51 192.168.122.209 [38621.912954] [tdb] Close table 'cache0.tdb' Apr 26 02:47:51 192.168.122.209 [38622.157514] [tdb] Close table 'filter0.tdb' Apr 26 02:47:51 192.168.122.209 [38622.157923] [tempesta fw] modules are stopped Apr 26 02:47:52 192.168.122.209 [38622.342795] [tempesta fw] exiting... Apr 26 02:47:52 192.168.122.209 [38622.505291] [tdb] Shutdown Tempesta DB Apr 26 02:47:52 192.168.122.209 [38622.685252] End test: cache.test_conditional.TestNotModifiedResponseHeadersHttp.test_cachable_headers_vary Apr 26 02:47:52 192.168.122.209 [38622.714779] Start test: cache.test_conditional.TestNotModifiedResponseHeadersHttp.test_non_cachable_header Apr 26 02:47:53 192.168.122.209 [38623.925225] [tdb] Start Tempesta DB Apr 26 02:47:53 192.168.122.209 [38624.087014] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:47:55 192.168.122.209 [38625.600138] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38625.600138] Maybe that's fine, but it's worth checking the [38625.600138] config - if there is no relations between the [38625.600138] names, then host name confusion attack is possible. Apr 26 02:47:55 192.168.122.209 [38625.738829] [tempesta fw] Configuration processing is completed. Apr 26 02:47:55 192.168.122.209 [38625.789626] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:47:55 192.168.122.209 [38626.223698] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:47:55 192.168.122.209 [38626.250156] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:47:55 192.168.122.209 [38626.277332] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:47:56 192.168.122.209 [38626.322900] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:47:56 192.168.122.209 [38626.324462] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:47:56 192.168.122.209 [38626.362834] [tempesta fw] Tempesta FW is ready Apr 26 02:47:56 192.168.122.209 [38626.945306] [tdb] Close table 'client0.tdb' Apr 26 02:47:56 192.168.122.209 [38627.171424] [tdb] Close table 'sessions0.tdb' Apr 26 02:48:00 192.168.122.209 [38630.335101] [tdb] Close table 'cache0.tdb' Apr 26 02:48:00 192.168.122.209 [38630.568923] [tdb] Close table 'filter0.tdb' Apr 26 02:48:00 192.168.122.209 [38630.569373] [tempesta fw] modules are stopped Apr 26 02:48:00 192.168.122.209 [38630.772082] [tempesta fw] exiting... Apr 26 02:48:00 192.168.122.209 [38630.938822] [tdb] Shutdown Tempesta DB Apr 26 02:48:00 192.168.122.209 [38631.167274] End test: cache.test_conditional.TestNotModifiedResponseHeadersHttp.test_non_cachable_header Apr 26 02:48:00 192.168.122.209 [38631.186447] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_authorization_in_first_request_must_revalidate_in_response Apr 26 02:48:02 192.168.122.209 [38632.402777] [tdb] Start Tempesta DB Apr 26 02:48:02 192.168.122.209 [38632.554161] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:48:03 192.168.122.209 [38633.984179] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38633.984179] Maybe that's fine, but it's worth checking the [38633.984179] config - if there is no relations between the [38633.984179] names, then host name confusion attack is possible. Apr 26 02:48:03 192.168.122.209 [38634.118997] [tempesta fw] Configuration processing is completed. Apr 26 02:48:03 192.168.122.209 [38634.167699] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:48:04 192.168.122.209 [38634.583180] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:48:04 192.168.122.209 [38634.610309] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:48:04 192.168.122.209 [38634.638300] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:48:04 192.168.122.209 [38634.703001] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:48:04 192.168.122.209 [38634.704748] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:48:04 192.168.122.209 [38634.742964] [tempesta fw] Tempesta FW is ready Apr 26 02:48:05 192.168.122.209 [38635.365432] [tdb] Close table 'client0.tdb' Apr 26 02:48:05 192.168.122.209 [38635.570762] [tdb] Close table 'sessions0.tdb' Apr 26 02:48:08 192.168.122.209 [38638.744876] [tdb] Close table 'cache0.tdb' Apr 26 02:48:08 192.168.122.209 [38638.969393] [tdb] Close table 'filter0.tdb' Apr 26 02:48:08 192.168.122.209 [38638.969856] [tempesta fw] modules are stopped Apr 26 02:48:08 192.168.122.209 [38639.151573] [tempesta fw] exiting... Apr 26 02:48:09 192.168.122.209 [38639.315853] [tdb] Shutdown Tempesta DB Apr 26 02:48:09 192.168.122.209 [38639.549574] End test: cache.test_h2_cache_control.TestH2CacheControl.test_authorization_in_first_request_must_revalidate_in_response Apr 26 02:48:09 192.168.122.209 [38639.559886] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_authorization_in_first_request_proxy_revalidate_in_response Apr 26 02:48:10 192.168.122.209 [38640.779123] [tdb] Start Tempesta DB Apr 26 02:48:10 192.168.122.209 [38640.917767] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:48:12 192.168.122.209 [38642.356317] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38642.356317] Maybe that's fine, but it's worth checking the [38642.356317] config - if there is no relations between the [38642.356317] names, then host name confusion attack is possible. Apr 26 02:48:12 192.168.122.209 [38642.483130] [tempesta fw] Configuration processing is completed. Apr 26 02:48:12 192.168.122.209 [38642.534549] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:48:12 192.168.122.209 [38642.970848] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:48:12 192.168.122.209 [38642.996699] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:48:12 192.168.122.209 [38643.023105] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:48:12 192.168.122.209 [38643.063133] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:48:12 192.168.122.209 [38643.064862] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:48:12 192.168.122.209 [38643.111070] [tempesta fw] Tempesta FW is ready Apr 26 02:48:13 192.168.122.209 [38643.690248] [tdb] Close table 'client0.tdb' Apr 26 02:48:13 192.168.122.209 [38643.889584] [tdb] Close table 'sessions0.tdb' Apr 26 02:48:16 192.168.122.209 [38647.104528] [tdb] Close table 'cache0.tdb' Apr 26 02:48:17 192.168.122.209 [38647.362290] [tdb] Close table 'filter0.tdb' Apr 26 02:48:17 192.168.122.209 [38647.362720] [tempesta fw] modules are stopped Apr 26 02:48:17 192.168.122.209 [38647.571596] [tempesta fw] exiting... Apr 26 02:48:17 192.168.122.209 [38647.754898] [tdb] Shutdown Tempesta DB Apr 26 02:48:17 192.168.122.209 [38647.971264] End test: cache.test_h2_cache_control.TestH2CacheControl.test_authorization_in_first_request_proxy_revalidate_in_response Apr 26 02:48:17 192.168.122.209 [38648.009265] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_authorization_in_first_request_public_in_response Apr 26 02:48:18 192.168.122.209 [38649.233010] [tdb] Start Tempesta DB Apr 26 02:48:19 192.168.122.209 [38649.383096] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:48:20 192.168.122.209 [38650.796569] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38650.796569] Maybe that's fine, but it's worth checking the [38650.796569] config - if there is no relations between the [38650.796569] names, then host name confusion attack is possible. Apr 26 02:48:20 192.168.122.209 [38650.919235] [tempesta fw] Configuration processing is completed. Apr 26 02:48:20 192.168.122.209 [38650.968451] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:48:21 192.168.122.209 [38651.402447] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:48:21 192.168.122.209 [38651.430024] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:48:21 192.168.122.209 [38651.457259] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:48:21 192.168.122.209 [38651.491209] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:48:21 192.168.122.209 [38651.492942] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:48:21 192.168.122.209 [38651.531158] [tempesta fw] Tempesta FW is ready Apr 26 02:48:21 192.168.122.209 [38652.127460] [tdb] Close table 'client0.tdb' Apr 26 02:48:22 192.168.122.209 [38652.330655] [tdb] Close table 'sessions0.tdb' Apr 26 02:48:25 192.168.122.209 [38655.475376] [tdb] Close table 'cache0.tdb' Apr 26 02:48:25 192.168.122.209 [38655.706764] [tdb] Close table 'filter0.tdb' Apr 26 02:48:25 192.168.122.209 [38655.707234] [tempesta fw] modules are stopped Apr 26 02:48:25 192.168.122.209 [38655.950885] [tempesta fw] exiting... Apr 26 02:48:25 192.168.122.209 [38656.077616] [tdb] Shutdown Tempesta DB Apr 26 02:48:26 192.168.122.209 [38656.312172] End test: cache.test_h2_cache_control.TestH2CacheControl.test_authorization_in_first_request_public_in_response Apr 26 02:48:26 192.168.122.209 [38656.326205] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_authorization_in_first_request_s_maxage_in_response Apr 26 02:48:27 192.168.122.209 [38657.532399] [tdb] Start Tempesta DB Apr 26 02:48:27 192.168.122.209 [38657.668402] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:48:28 192.168.122.209 [38659.104606] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38659.104606] Maybe that's fine, but it's worth checking the [38659.104606] config - if there is no relations between the [38659.104606] names, then host name confusion attack is possible. Apr 26 02:48:28 192.168.122.209 [38659.219349] [tempesta fw] Configuration processing is completed. Apr 26 02:48:28 192.168.122.209 [38659.269178] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:48:29 192.168.122.209 [38659.689374] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:48:29 192.168.122.209 [38659.715730] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:48:29 192.168.122.209 [38659.742214] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:48:29 192.168.122.209 [38659.795334] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:48:29 192.168.122.209 [38659.797057] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:48:29 192.168.122.209 [38659.835208] [tempesta fw] Tempesta FW is ready Apr 26 02:48:30 192.168.122.209 [38660.449989] [tdb] Close table 'client0.tdb' Apr 26 02:48:30 192.168.122.209 [38660.694651] [tdb] Close table 'sessions0.tdb' Apr 26 02:48:33 192.168.122.209 [38663.870321] [tdb] Close table 'cache0.tdb' Apr 26 02:48:33 192.168.122.209 [38664.125536] [tdb] Close table 'filter0.tdb' Apr 26 02:48:33 192.168.122.209 [38664.125980] [tempesta fw] modules are stopped Apr 26 02:48:34 192.168.122.209 [38664.359303] [tempesta fw] exiting... Apr 26 02:48:34 192.168.122.209 [38664.535693] [tdb] Shutdown Tempesta DB Apr 26 02:48:34 192.168.122.209 [38664.792087] End test: cache.test_h2_cache_control.TestH2CacheControl.test_authorization_in_first_request_s_maxage_in_response Apr 26 02:48:34 192.168.122.209 [38664.814003] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_authorization_in_second_request Apr 26 02:48:35 192.168.122.209 [38666.028478] [tdb] Start Tempesta DB Apr 26 02:48:35 192.168.122.209 [38666.177739] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:48:37 192.168.122.209 [38667.556709] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38667.556709] Maybe that's fine, but it's worth checking the [38667.556709] config - if there is no relations between the [38667.556709] names, then host name confusion attack is possible. Apr 26 02:48:37 192.168.122.209 [38667.683436] [tempesta fw] Configuration processing is completed. Apr 26 02:48:37 192.168.122.209 [38667.734211] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:48:37 192.168.122.209 [38668.217482] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:48:37 192.168.122.209 [38668.249723] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:48:37 192.168.122.209 [38668.280521] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:48:38 192.168.122.209 [38668.327459] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:48:38 192.168.122.209 [38668.329185] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:48:38 192.168.122.209 [38668.371404] [tempesta fw] Tempesta FW is ready Apr 26 02:48:38 192.168.122.209 [38668.986680] [tdb] Close table 'client0.tdb' Apr 26 02:48:38 192.168.122.209 [38669.188226] [tdb] Close table 'sessions0.tdb' Apr 26 02:48:42 192.168.122.209 [38672.446351] [tdb] Close table 'cache0.tdb' Apr 26 02:48:42 192.168.122.209 [38672.725060] [tdb] Close table 'filter0.tdb' Apr 26 02:48:42 192.168.122.209 [38672.725522] [tempesta fw] modules are stopped Apr 26 02:48:42 192.168.122.209 [38672.899861] [tempesta fw] exiting... Apr 26 02:48:42 192.168.122.209 [38673.057092] [tdb] Shutdown Tempesta DB Apr 26 02:48:42 192.168.122.209 [38673.285420] End test: cache.test_h2_cache_control.TestH2CacheControl.test_authorization_in_second_request Apr 26 02:48:43 192.168.122.209 [38673.309685] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_max_age_0_in_request Apr 26 02:48:44 192.168.122.209 [38674.483181] [tdb] Start Tempesta DB Apr 26 02:48:44 192.168.122.209 [38674.640753] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:48:45 192.168.122.209 [38676.080512] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38676.080512] Maybe that's fine, but it's worth checking the [38676.080512] config - if there is no relations between the [38676.080512] names, then host name confusion attack is possible. Apr 26 02:48:45 192.168.122.209 [38676.196789] [tempesta fw] Configuration processing is completed. Apr 26 02:48:45 192.168.122.209 [38676.252579] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:48:46 192.168.122.209 [38676.668333] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:48:46 192.168.122.209 [38676.695222] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:48:46 192.168.122.209 [38676.721881] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:48:46 192.168.122.209 [38676.787545] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:48:46 192.168.122.209 [38676.789310] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:48:46 192.168.122.209 [38676.855523] [tempesta fw] Tempesta FW is ready Apr 26 02:48:47 192.168.122.209 [38677.510608] [tdb] Close table 'client0.tdb' Apr 26 02:48:47 192.168.122.209 [38677.705320] [tdb] Close table 'sessions0.tdb' Apr 26 02:48:50 192.168.122.209 [38680.847687] [tdb] Close table 'cache0.tdb' Apr 26 02:48:50 192.168.122.209 [38681.078746] [tdb] Close table 'filter0.tdb' Apr 26 02:48:50 192.168.122.209 [38681.079182] [tempesta fw] modules are stopped Apr 26 02:48:51 192.168.122.209 [38681.307780] [tempesta fw] exiting... Apr 26 02:48:51 192.168.122.209 [38681.455165] [tdb] Shutdown Tempesta DB Apr 26 02:48:51 192.168.122.209 [38681.691964] End test: cache.test_h2_cache_control.TestH2CacheControl.test_max_age_0_in_request Apr 26 02:48:51 192.168.122.209 [38681.706982] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_max_age_0_in_response Apr 26 02:48:52 192.168.122.209 [38682.897868] [tdb] Start Tempesta DB Apr 26 02:48:52 192.168.122.209 [38683.029568] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:48:54 192.168.122.209 [38684.424884] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38684.424884] Maybe that's fine, but it's worth checking the [38684.424884] config - if there is no relations between the [38684.424884] names, then host name confusion attack is possible. Apr 26 02:48:54 192.168.122.209 [38684.547669] [tempesta fw] Configuration processing is completed. Apr 26 02:48:54 192.168.122.209 [38684.633362] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:48:54 192.168.122.209 [38685.048500] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:48:54 192.168.122.209 [38685.075831] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:48:54 192.168.122.209 [38685.102564] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:48:54 192.168.122.209 [38685.151669] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:48:54 192.168.122.209 [38685.153412] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:48:54 192.168.122.209 [38685.191596] [tempesta fw] Tempesta FW is ready Apr 26 02:48:55 192.168.122.209 [38685.798980] [tdb] Close table 'client0.tdb' Apr 26 02:48:55 192.168.122.209 [38685.991650] [tdb] Close table 'sessions0.tdb' Apr 26 02:48:58 192.168.122.209 [38689.202546] [tdb] Close table 'cache0.tdb' Apr 26 02:48:59 192.168.122.209 [38689.469363] [tdb] Close table 'filter0.tdb' Apr 26 02:48:59 192.168.122.209 [38689.469817] [tempesta fw] modules are stopped Apr 26 02:48:59 192.168.122.209 [38689.691121] [tempesta fw] exiting... Apr 26 02:48:59 192.168.122.209 [38689.833308] [tdb] Shutdown Tempesta DB Apr 26 02:48:59 192.168.122.209 [38690.057170] End test: cache.test_h2_cache_control.TestH2CacheControl.test_max_age_0_in_response Apr 26 02:48:59 192.168.122.209 [38690.068420] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_max_age_1_in_request_sleep_2 Apr 26 02:49:00 192.168.122.209 [38691.260348] [tdb] Start Tempesta DB Apr 26 02:49:01 192.168.122.209 [38691.407963] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:49:02 192.168.122.209 [38692.825649] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38692.825649] Maybe that's fine, but it's worth checking the [38692.825649] config - if there is no relations between the [38692.825649] names, then host name confusion attack is possible. Apr 26 02:49:02 192.168.122.209 [38692.943902] [tempesta fw] Configuration processing is completed. Apr 26 02:49:02 192.168.122.209 [38693.001305] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:49:03 192.168.122.209 [38693.486334] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:49:03 192.168.122.209 [38693.518497] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:49:03 192.168.122.209 [38693.551057] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:49:03 192.168.122.209 [38693.611828] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:49:03 192.168.122.209 [38693.613629] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:49:03 192.168.122.209 [38693.659728] [tempesta fw] Tempesta FW is ready Apr 26 02:49:06 192.168.122.209 [38696.292444] [tdb] Close table 'client0.tdb' Apr 26 02:49:06 192.168.122.209 [38696.496604] [tdb] Close table 'sessions0.tdb' Apr 26 02:49:09 192.168.122.209 [38699.667177] [tdb] Close table 'cache0.tdb' Apr 26 02:49:09 192.168.122.209 [38699.885831] [tdb] Close table 'filter0.tdb' Apr 26 02:49:09 192.168.122.209 [38699.886285] [tempesta fw] modules are stopped Apr 26 02:49:09 192.168.122.209 [38700.064076] [tempesta fw] exiting... Apr 26 02:49:09 192.168.122.209 [38700.229225] [tdb] Shutdown Tempesta DB Apr 26 02:49:10 192.168.122.209 [38700.464399] End test: cache.test_h2_cache_control.TestH2CacheControl.test_max_age_1_in_request_sleep_2 Apr 26 02:49:10 192.168.122.209 [38700.491666] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_max_age_1_in_request_sleep_2_from_hpack_dynamic_table Apr 26 02:49:11 192.168.122.209 [38701.709943] [tdb] Start Tempesta DB Apr 26 02:49:11 192.168.122.209 [38701.860156] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:49:13 192.168.122.209 [38703.329206] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38703.329206] Maybe that's fine, but it's worth checking the [38703.329206] config - if there is no relations between the [38703.329206] names, then host name confusion attack is possible. Apr 26 02:49:13 192.168.122.209 [38703.443908] [tempesta fw] Configuration processing is completed. Apr 26 02:49:13 192.168.122.209 [38703.497214] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:49:13 192.168.122.209 [38703.936288] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:49:13 192.168.122.209 [38703.962185] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:49:13 192.168.122.209 [38703.996502] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:49:13 192.168.122.209 [38704.043868] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:49:13 192.168.122.209 [38704.045282] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:49:13 192.168.122.209 [38704.099847] [tempesta fw] Tempesta FW is ready Apr 26 02:49:16 192.168.122.209 [38706.712232] [tdb] Close table 'client0.tdb' Apr 26 02:49:16 192.168.122.209 [38706.906692] [tdb] Close table 'sessions0.tdb' Apr 26 02:49:19 192.168.122.209 [38710.078887] [tdb] Close table 'cache0.tdb' Apr 26 02:49:20 192.168.122.209 [38710.324191] [tdb] Close table 'filter0.tdb' Apr 26 02:49:20 192.168.122.209 [38710.324645] [tempesta fw] modules are stopped Apr 26 02:49:20 192.168.122.209 [38710.510525] [tempesta fw] exiting... Apr 26 02:49:20 192.168.122.209 [38710.639968] [tdb] Shutdown Tempesta DB Apr 26 02:49:20 192.168.122.209 [38710.852036] End test: cache.test_h2_cache_control.TestH2CacheControl.test_max_age_1_in_request_sleep_2_from_hpack_dynamic_table Apr 26 02:49:20 192.168.122.209 [38710.892889] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_max_age_1_in_response_sleep_2 Apr 26 02:49:21 192.168.122.209 [38712.083965] [tdb] Start Tempesta DB Apr 26 02:49:21 192.168.122.209 [38712.242243] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:49:23 192.168.122.209 [38713.589293] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38713.589293] Maybe that's fine, but it's worth checking the [38713.589293] config - if there is no relations between the [38713.589293] names, then host name confusion attack is possible. Apr 26 02:49:23 192.168.122.209 [38713.712035] [tempesta fw] Configuration processing is completed. Apr 26 02:49:23 192.168.122.209 [38713.760991] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:49:23 192.168.122.209 [38714.166377] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:49:23 192.168.122.209 [38714.191972] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:49:23 192.168.122.209 [38714.218982] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:49:23 192.168.122.209 [38714.267912] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:49:23 192.168.122.209 [38714.268857] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:49:24 192.168.122.209 [38714.315887] [tempesta fw] Tempesta FW is ready Apr 26 02:49:26 192.168.122.209 [38716.918318] [tdb] Close table 'client0.tdb' Apr 26 02:49:26 192.168.122.209 [38717.120920] [tdb] Close table 'sessions0.tdb' Apr 26 02:49:30 192.168.122.209 [38720.406386] [tdb] Close table 'cache0.tdb' Apr 26 02:49:30 192.168.122.209 [38720.654952] [tdb] Close table 'filter0.tdb' Apr 26 02:49:30 192.168.122.209 [38720.655421] [tempesta fw] modules are stopped Apr 26 02:49:30 192.168.122.209 [38720.868029] [tempesta fw] exiting... Apr 26 02:49:30 192.168.122.209 [38721.012913] [tdb] Shutdown Tempesta DB Apr 26 02:49:30 192.168.122.209 [38721.281266] End test: cache.test_h2_cache_control.TestH2CacheControl.test_max_age_1_in_response_sleep_2 Apr 26 02:49:31 192.168.122.209 [38721.306996] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_max_age_2_in_request_sleep_0 Apr 26 02:49:32 192.168.122.209 [38722.550175] [tdb] Start Tempesta DB Apr 26 02:49:32 192.168.122.209 [38722.717149] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:49:33 192.168.122.209 [38724.161427] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38724.161427] Maybe that's fine, but it's worth checking the [38724.161427] config - if there is no relations between the [38724.161427] names, then host name confusion attack is possible. Apr 26 02:49:34 192.168.122.209 [38724.296485] [tempesta fw] Configuration processing is completed. Apr 26 02:49:34 192.168.122.209 [38724.368511] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:49:34 192.168.122.209 [38724.848673] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:49:34 192.168.122.209 [38724.876245] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:49:34 192.168.122.209 [38724.903892] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:49:34 192.168.122.209 [38724.948162] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:49:34 192.168.122.209 [38724.949922] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:49:34 192.168.122.209 [38724.988128] [tempesta fw] Tempesta FW is ready Apr 26 02:49:35 192.168.122.209 [38725.599125] [tdb] Close table 'client0.tdb' Apr 26 02:49:35 192.168.122.209 [38725.789603] [tdb] Close table 'sessions0.tdb' Apr 26 02:49:38 192.168.122.209 [38729.029035] [tdb] Close table 'cache0.tdb' Apr 26 02:49:38 192.168.122.209 [38729.272302] [tdb] Close table 'filter0.tdb' Apr 26 02:49:38 192.168.122.209 [38729.272761] [tempesta fw] modules are stopped Apr 26 02:49:39 192.168.122.209 [38729.463427] [tempesta fw] exiting... Apr 26 02:49:39 192.168.122.209 [38729.633767] [tdb] Shutdown Tempesta DB Apr 26 02:49:39 192.168.122.209 [38729.863471] End test: cache.test_h2_cache_control.TestH2CacheControl.test_max_age_2_in_request_sleep_0 Apr 26 02:49:39 192.168.122.209 [38729.878749] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_max_age_2_in_response_sleep_0 Apr 26 02:49:40 192.168.122.209 [38731.026315] [tdb] Start Tempesta DB Apr 26 02:49:40 192.168.122.209 [38731.177777] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:49:42 192.168.122.209 [38732.565588] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38732.565588] Maybe that's fine, but it's worth checking the [38732.565588] config - if there is no relations between the [38732.565588] names, then host name confusion attack is possible. Apr 26 02:49:42 192.168.122.209 [38732.680330] [tempesta fw] Configuration processing is completed. Apr 26 02:49:42 192.168.122.209 [38732.728872] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:49:42 192.168.122.209 [38733.173946] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:49:42 192.168.122.209 [38733.201807] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:49:42 192.168.122.209 [38733.230193] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:49:42 192.168.122.209 [38733.280345] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:49:42 192.168.122.209 [38733.282068] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:49:43 192.168.122.209 [38733.328230] [tempesta fw] Tempesta FW is ready Apr 26 02:49:43 192.168.122.209 [38733.997741] [tdb] Close table 'client0.tdb' Apr 26 02:49:43 192.168.122.209 [38734.175807] [tdb] Close table 'sessions0.tdb' Apr 26 02:49:47 192.168.122.209 [38737.412827] [tdb] Close table 'cache0.tdb' Apr 26 02:49:47 192.168.122.209 [38737.671517] [tdb] Close table 'filter0.tdb' Apr 26 02:49:47 192.168.122.209 [38737.671945] [tempesta fw] modules are stopped Apr 26 02:49:47 192.168.122.209 [38737.857835] [tempesta fw] exiting... Apr 26 02:49:47 192.168.122.209 [38738.020019] [tdb] Shutdown Tempesta DB Apr 26 02:49:47 192.168.122.209 [38738.242500] End test: cache.test_h2_cache_control.TestH2CacheControl.test_max_age_2_in_response_sleep_0 Apr 26 02:49:47 192.168.122.209 [38738.270827] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_max_stale_1_in_request_sleep_3 Apr 26 02:49:49 192.168.122.209 [38739.465280] [tdb] Start Tempesta DB Apr 26 02:49:49 192.168.122.209 [38739.617605] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:49:50 192.168.122.209 [38741.005646] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38741.005646] Maybe that's fine, but it's worth checking the [38741.005646] config - if there is no relations between the [38741.005646] names, then host name confusion attack is possible. Apr 26 02:49:50 192.168.122.209 [38741.120355] [tempesta fw] Configuration processing is completed. Apr 26 02:49:50 192.168.122.209 [38741.211149] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:49:51 192.168.122.209 [38741.668712] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:49:51 192.168.122.209 [38741.698603] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:49:51 192.168.122.209 [38741.728954] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:49:51 192.168.122.209 [38741.788347] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:49:51 192.168.122.209 [38741.790114] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:49:51 192.168.122.209 [38741.832349] [tempesta fw] Tempesta FW is ready Apr 26 02:49:55 192.168.122.209 [38745.482328] [tdb] Close table 'client0.tdb' Apr 26 02:49:55 192.168.122.209 [38745.669931] [tdb] Close table 'sessions0.tdb' Apr 26 02:49:58 192.168.122.209 [38748.926433] [tdb] Close table 'cache0.tdb' Apr 26 02:49:58 192.168.122.209 [38749.159493] [tdb] Close table 'filter0.tdb' Apr 26 02:49:58 192.168.122.209 [38749.159951] [tempesta fw] modules are stopped Apr 26 02:49:59 192.168.122.209 [38749.412639] [tempesta fw] exiting... Apr 26 02:49:59 192.168.122.209 [38749.599689] [tdb] Shutdown Tempesta DB Apr 26 02:49:59 192.168.122.209 [38749.857129] End test: cache.test_h2_cache_control.TestH2CacheControl.test_max_stale_1_in_request_sleep_3 Apr 26 02:49:59 192.168.122.209 [38749.872143] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_max_stale_5_in_request_sleep_2 Apr 26 02:50:00 192.168.122.209 [38751.095065] [tdb] Start Tempesta DB Apr 26 02:50:00 192.168.122.209 [38751.255704] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:50:02 192.168.122.209 [38752.709891] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38752.709891] Maybe that's fine, but it's worth checking the [38752.709891] config - if there is no relations between the [38752.709891] names, then host name confusion attack is possible. Apr 26 02:50:02 192.168.122.209 [38752.828611] [tempesta fw] Configuration processing is completed. Apr 26 02:50:02 192.168.122.209 [38752.881437] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:50:03 192.168.122.209 [38753.303440] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:50:03 192.168.122.209 [38753.332977] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:50:03 192.168.122.209 [38753.361501] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:50:03 192.168.122.209 [38753.412597] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:50:03 192.168.122.209 [38753.414346] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:50:03 192.168.122.209 [38753.468405] [tempesta fw] Tempesta FW is ready Apr 26 02:50:05 192.168.122.209 [38756.131214] [tdb] Close table 'client0.tdb' Apr 26 02:50:06 192.168.122.209 [38756.322859] [tdb] Close table 'sessions0.tdb' Apr 26 02:50:09 192.168.122.209 [38759.479822] [tdb] Close table 'cache0.tdb' Apr 26 02:50:09 192.168.122.209 [38759.734723] [tdb] Close table 'filter0.tdb' Apr 26 02:50:09 192.168.122.209 [38759.735167] [tempesta fw] modules are stopped Apr 26 02:50:09 192.168.122.209 [38759.929431] [tempesta fw] exiting... Apr 26 02:50:09 192.168.122.209 [38760.088229] [tdb] Shutdown Tempesta DB Apr 26 02:50:10 192.168.122.209 [38760.338345] End test: cache.test_h2_cache_control.TestH2CacheControl.test_max_stale_5_in_request_sleep_2 Apr 26 02:50:10 192.168.122.209 [38760.363203] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_max_stale_5_in_request_sleep_2_from_dynamic_table Apr 26 02:50:11 192.168.122.209 [38761.585800] [tdb] Start Tempesta DB Apr 26 02:50:11 192.168.122.209 [38761.741148] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:50:12 192.168.122.209 [38763.205906] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38763.205906] Maybe that's fine, but it's worth checking the [38763.205906] config - if there is no relations between the [38763.205906] names, then host name confusion attack is possible. Apr 26 02:50:13 192.168.122.209 [38763.332661] [tempesta fw] Configuration processing is completed. Apr 26 02:50:13 192.168.122.209 [38763.388899] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:50:13 192.168.122.209 [38763.901179] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:50:13 192.168.122.209 [38763.943509] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:50:13 192.168.122.209 [38763.974953] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:50:13 192.168.122.209 [38764.024683] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:50:13 192.168.122.209 [38764.026401] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:50:13 192.168.122.209 [38764.064607] [tempesta fw] Tempesta FW is ready Apr 26 02:50:16 192.168.122.209 [38766.694654] [tdb] Close table 'client0.tdb' Apr 26 02:50:16 192.168.122.209 [38766.891944] [tdb] Close table 'sessions0.tdb' Apr 26 02:50:19 192.168.122.209 [38770.129798] [tdb] Close table 'cache0.tdb' Apr 26 02:50:20 192.168.122.209 [38770.390179] [tdb] Close table 'filter0.tdb' Apr 26 02:50:20 192.168.122.209 [38770.390643] [tempesta fw] modules are stopped Apr 26 02:50:20 192.168.122.209 [38770.618487] [tempesta fw] exiting... Apr 26 02:50:20 192.168.122.209 [38770.793096] [tdb] Shutdown Tempesta DB Apr 26 02:50:20 192.168.122.209 [38771.019738] End test: cache.test_h2_cache_control.TestH2CacheControl.test_max_stale_5_in_request_sleep_2_from_dynamic_table Apr 26 02:50:20 192.168.122.209 [38771.042556] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_max_stale_in_request_sleep_2 Apr 26 02:50:21 192.168.122.209 [38772.271772] [tdb] Start Tempesta DB Apr 26 02:50:22 192.168.122.209 [38772.421598] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:50:23 192.168.122.209 [38773.854100] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38773.854100] Maybe that's fine, but it's worth checking the [38773.854100] config - if there is no relations between the [38773.854100] names, then host name confusion attack is possible. Apr 26 02:50:23 192.168.122.209 [38773.972827] [tempesta fw] Configuration processing is completed. Apr 26 02:50:23 192.168.122.209 [38774.021267] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:50:24 192.168.122.209 [38774.444931] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:50:24 192.168.122.209 [38774.471089] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:50:24 192.168.122.209 [38774.497701] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:50:24 192.168.122.209 [38774.540753] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:50:24 192.168.122.209 [38774.541837] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:50:24 192.168.122.209 [38774.584745] [tempesta fw] Tempesta FW is ready Apr 26 02:50:26 192.168.122.209 [38777.202515] [tdb] Close table 'client0.tdb' Apr 26 02:50:27 192.168.122.209 [38777.391826] [tdb] Close table 'sessions0.tdb' Apr 26 02:50:30 192.168.122.209 [38780.547983] [tdb] Close table 'cache0.tdb' Apr 26 02:50:30 192.168.122.209 [38780.803806] [tdb] Close table 'filter0.tdb' Apr 26 02:50:30 192.168.122.209 [38780.804232] [tempesta fw] modules are stopped Apr 26 02:50:30 192.168.122.209 [38780.978986] [tempesta fw] exiting... Apr 26 02:50:30 192.168.122.209 [38781.098794] [tdb] Shutdown Tempesta DB Apr 26 02:50:31 192.168.122.209 [38781.381929] End test: cache.test_h2_cache_control.TestH2CacheControl.test_max_stale_in_request_sleep_2 Apr 26 02:50:31 192.168.122.209 [38781.410155] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_min_fresh_1_in_request_sleep_0 Apr 26 02:50:32 192.168.122.209 [38782.620743] [tdb] Start Tempesta DB Apr 26 02:50:32 192.168.122.209 [38782.767916] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:50:33 192.168.122.209 [38784.218212] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38784.218212] Maybe that's fine, but it's worth checking the [38784.218212] config - if there is no relations between the [38784.218212] names, then host name confusion attack is possible. Apr 26 02:50:34 192.168.122.209 [38784.348947] [tempesta fw] Configuration processing is completed. Apr 26 02:50:34 192.168.122.209 [38784.398713] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:50:34 192.168.122.209 [38784.811476] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:50:34 192.168.122.209 [38784.837228] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:50:34 192.168.122.209 [38784.863077] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:50:34 192.168.122.209 [38784.904935] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:50:34 192.168.122.209 [38784.906660] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:50:34 192.168.122.209 [38784.948903] [tempesta fw] Tempesta FW is ready Apr 26 02:50:35 192.168.122.209 [38785.573690] [tdb] Close table 'client0.tdb' Apr 26 02:50:35 192.168.122.209 [38785.747947] [tdb] Close table 'sessions0.tdb' Apr 26 02:50:38 192.168.122.209 [38788.932163] [tdb] Close table 'cache0.tdb' Apr 26 02:50:38 192.168.122.209 [38789.193718] [tdb] Close table 'filter0.tdb' Apr 26 02:50:38 192.168.122.209 [38789.194158] [tempesta fw] modules are stopped Apr 26 02:50:39 192.168.122.209 [38789.380687] [tempesta fw] exiting... Apr 26 02:50:39 192.168.122.209 [38789.523307] [tdb] Shutdown Tempesta DB Apr 26 02:50:39 192.168.122.209 [38789.773337] End test: cache.test_h2_cache_control.TestH2CacheControl.test_min_fresh_1_in_request_sleep_0 Apr 26 02:50:39 192.168.122.209 [38789.798598] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_min_fresh_1_in_request_sleep_0_from_dynamic_table Apr 26 02:50:40 192.168.122.209 [38790.997134] [tdb] Start Tempesta DB Apr 26 02:50:40 192.168.122.209 [38791.143345] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:50:42 192.168.122.209 [38792.534359] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38792.534359] Maybe that's fine, but it's worth checking the [38792.534359] config - if there is no relations between the [38792.534359] names, then host name confusion attack is possible. Apr 26 02:50:42 192.168.122.209 [38792.657189] [tempesta fw] Configuration processing is completed. Apr 26 02:50:42 192.168.122.209 [38792.738634] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:50:42 192.168.122.209 [38793.170782] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:50:42 192.168.122.209 [38793.197927] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:50:42 192.168.122.209 [38793.225627] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:50:42 192.168.122.209 [38793.273059] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:50:42 192.168.122.209 [38793.274804] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:50:43 192.168.122.209 [38793.313009] [tempesta fw] Tempesta FW is ready Apr 26 02:50:43 192.168.122.209 [38793.983932] [tdb] Close table 'client0.tdb' Apr 26 02:50:43 192.168.122.209 [38794.187964] [tdb] Close table 'sessions0.tdb' Apr 26 02:50:47 192.168.122.209 [38797.408201] [tdb] Close table 'cache0.tdb' Apr 26 02:50:47 192.168.122.209 [38797.638626] [tdb] Close table 'filter0.tdb' Apr 26 02:50:47 192.168.122.209 [38797.639070] [tempesta fw] modules are stopped Apr 26 02:50:47 192.168.122.209 [38797.856432] [tempesta fw] exiting... Apr 26 02:50:47 192.168.122.209 [38798.006824] [tdb] Shutdown Tempesta DB Apr 26 02:50:47 192.168.122.209 [38798.255646] End test: cache.test_h2_cache_control.TestH2CacheControl.test_min_fresh_1_in_request_sleep_0_from_dynamic_table Apr 26 02:50:47 192.168.122.209 [38798.280962] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_min_fresh_2_in_request_sleep_2 Apr 26 02:50:49 192.168.122.209 [38799.517672] [tdb] Start Tempesta DB Apr 26 02:50:49 192.168.122.209 [38799.669111] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:50:50 192.168.122.209 [38801.078437] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38801.078437] Maybe that's fine, but it's worth checking the [38801.078437] config - if there is no relations between the [38801.078437] names, then host name confusion attack is possible. Apr 26 02:50:50 192.168.122.209 [38801.197178] [tempesta fw] Configuration processing is completed. Apr 26 02:50:50 192.168.122.209 [38801.253923] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:50:51 192.168.122.209 [38801.672722] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:50:51 192.168.122.209 [38801.698211] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:50:51 192.168.122.209 [38801.723446] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:50:51 192.168.122.209 [38801.773170] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:50:51 192.168.122.209 [38801.774989] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:50:51 192.168.122.209 [38801.813103] [tempesta fw] Tempesta FW is ready Apr 26 02:50:54 192.168.122.209 [38804.446899] [tdb] Close table 'client0.tdb' Apr 26 02:50:54 192.168.122.209 [38804.636459] [tdb] Close table 'sessions0.tdb' Apr 26 02:50:57 192.168.122.209 [38807.807865] [tdb] Close table 'cache0.tdb' Apr 26 02:50:57 192.168.122.209 [38808.037043] [tdb] Close table 'filter0.tdb' Apr 26 02:50:57 192.168.122.209 [38808.037505] [tempesta fw] modules are stopped Apr 26 02:50:57 192.168.122.209 [38808.261095] [tempesta fw] exiting... Apr 26 02:50:58 192.168.122.209 [38808.419304] [tdb] Shutdown Tempesta DB Apr 26 02:50:58 192.168.122.209 [38808.644732] End test: cache.test_h2_cache_control.TestH2CacheControl.test_min_fresh_2_in_request_sleep_2 Apr 26 02:50:58 192.168.122.209 [38808.663089] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_must_revalidate_in_response_from_cache Apr 26 02:50:59 192.168.122.209 [38809.858098] [tdb] Start Tempesta DB Apr 26 02:50:59 192.168.122.209 [38809.983342] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:51:01 192.168.122.209 [38811.450535] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38811.450535] Maybe that's fine, but it's worth checking the [38811.450535] config - if there is no relations between the [38811.450535] names, then host name confusion attack is possible. Apr 26 02:51:01 192.168.122.209 [38811.585307] [tempesta fw] Configuration processing is completed. Apr 26 02:51:01 192.168.122.209 [38811.634610] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:51:01 192.168.122.209 [38812.047658] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:51:01 192.168.122.209 [38812.073122] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:51:01 192.168.122.209 [38812.098837] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:51:01 192.168.122.209 [38812.153302] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:51:01 192.168.122.209 [38812.155030] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:51:01 192.168.122.209 [38812.201262] [tempesta fw] Tempesta FW is ready Apr 26 02:51:02 192.168.122.209 [38812.810816] [tdb] Close table 'client0.tdb' Apr 26 02:51:02 192.168.122.209 [38813.001110] [tdb] Close table 'sessions0.tdb' Apr 26 02:51:05 192.168.122.209 [38816.190688] [tdb] Close table 'cache0.tdb' Apr 26 02:51:06 192.168.122.209 [38816.426501] [tdb] Close table 'filter0.tdb' Apr 26 02:51:06 192.168.122.209 [38816.426945] [tempesta fw] modules are stopped Apr 26 02:51:06 192.168.122.209 [38816.616719] [tempesta fw] exiting... Apr 26 02:51:06 192.168.122.209 [38816.772785] [tdb] Shutdown Tempesta DB Apr 26 02:51:06 192.168.122.209 [38816.999150] End test: cache.test_h2_cache_control.TestH2CacheControl.test_must_revalidate_in_response_from_cache Apr 26 02:51:06 192.168.122.209 [38817.021714] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_must_revalidate_in_response_max_stale_in_request_from_cache Apr 26 02:51:07 192.168.122.209 [38818.288505] [tdb] Start Tempesta DB Apr 26 02:51:08 192.168.122.209 [38818.446224] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:51:09 192.168.122.209 [38819.810634] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38819.810634] Maybe that's fine, but it's worth checking the [38819.810634] config - if there is no relations between the [38819.810634] names, then host name confusion attack is possible. Apr 26 02:51:09 192.168.122.209 [38819.921727] [tempesta fw] Configuration processing is completed. Apr 26 02:51:09 192.168.122.209 [38819.974141] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:51:10 192.168.122.209 [38820.412549] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:51:10 192.168.122.209 [38820.438901] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:51:10 192.168.122.209 [38820.465000] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:51:10 192.168.122.209 [38820.521415] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:51:10 192.168.122.209 [38820.523151] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:51:10 192.168.122.209 [38820.561350] [tempesta fw] Tempesta FW is ready Apr 26 02:51:11 192.168.122.209 [38821.299953] [tdb] Close table 'client0.tdb' Apr 26 02:51:11 192.168.122.209 [38821.513288] [tdb] Close table 'sessions0.tdb' Apr 26 02:51:14 192.168.122.209 [38824.699234] [tdb] Close table 'cache0.tdb' Apr 26 02:51:14 192.168.122.209 [38824.950623] [tdb] Close table 'filter0.tdb' Apr 26 02:51:14 192.168.122.209 [38824.951075] [tempesta fw] modules are stopped Apr 26 02:51:14 192.168.122.209 [38825.174960] [tempesta fw] exiting... Apr 26 02:51:15 192.168.122.209 [38825.357335] [tdb] Shutdown Tempesta DB Apr 26 02:51:15 192.168.122.209 [38825.617404] End test: cache.test_h2_cache_control.TestH2CacheControl.test_must_revalidate_in_response_max_stale_in_request_from_cache Apr 26 02:51:15 192.168.122.209 [38825.633729] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_must_revalidate_in_response_max_stale_in_request_not_from_cache Apr 26 02:51:16 192.168.122.209 [38826.758511] [tdb] Start Tempesta DB Apr 26 02:51:16 192.168.122.209 [38826.908649] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:51:18 192.168.122.209 [38828.292340] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38828.292340] Maybe that's fine, but it's worth checking the [38828.292340] config - if there is no relations between the [38828.292340] names, then host name confusion attack is possible. Apr 26 02:51:18 192.168.122.209 [38828.413565] [tempesta fw] Configuration processing is completed. Apr 26 02:51:18 192.168.122.209 [38828.505417] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:51:18 192.168.122.209 [38828.933269] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:51:18 192.168.122.209 [38828.960239] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:51:18 192.168.122.209 [38828.987958] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:51:18 192.168.122.209 [38829.033546] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:51:18 192.168.122.209 [38829.035316] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:51:18 192.168.122.209 [38829.069460] [tempesta fw] Tempesta FW is ready Apr 26 02:51:21 192.168.122.209 [38831.743447] [tdb] Close table 'client0.tdb' Apr 26 02:51:21 192.168.122.209 [38831.931449] [tdb] Close table 'sessions0.tdb' Apr 26 02:51:24 192.168.122.209 [38835.122297] [tdb] Close table 'cache0.tdb' Apr 26 02:51:25 192.168.122.209 [38835.373929] [tdb] Close table 'filter0.tdb' Apr 26 02:51:25 192.168.122.209 [38835.374399] [tempesta fw] modules are stopped Apr 26 02:51:25 192.168.122.209 [38835.575084] [tempesta fw] exiting... Apr 26 02:51:25 192.168.122.209 [38835.769703] [tdb] Shutdown Tempesta DB Apr 26 02:51:25 192.168.122.209 [38836.031503] End test: cache.test_h2_cache_control.TestH2CacheControl.test_must_revalidate_in_response_max_stale_in_request_not_from_cache Apr 26 02:51:25 192.168.122.209 [38836.051662] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_must_revalidate_in_response_not_from_cache Apr 26 02:51:27 192.168.122.209 [38837.392259] [tdb] Start Tempesta DB Apr 26 02:51:27 192.168.122.209 [38837.557998] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:51:28 192.168.122.209 [38839.118665] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38839.118665] Maybe that's fine, but it's worth checking the [38839.118665] config - if there is no relations between the [38839.118665] names, then host name confusion attack is possible. Apr 26 02:51:28 192.168.122.209 [38839.241654] [tempesta fw] Configuration processing is completed. Apr 26 02:51:28 192.168.122.209 [38839.291258] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:51:29 192.168.122.209 [38839.702062] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:51:29 192.168.122.209 [38839.727800] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:51:29 192.168.122.209 [38839.753192] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:51:29 192.168.122.209 [38839.809644] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:51:29 192.168.122.209 [38839.811363] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:51:29 192.168.122.209 [38839.849610] [tempesta fw] Tempesta FW is ready Apr 26 02:51:32 192.168.122.209 [38842.474348] [tdb] Close table 'client0.tdb' Apr 26 02:51:32 192.168.122.209 [38842.669528] [tdb] Close table 'sessions0.tdb' Apr 26 02:51:35 192.168.122.209 [38845.810592] [tdb] Close table 'cache0.tdb' Apr 26 02:51:35 192.168.122.209 [38846.047054] [tdb] Close table 'filter0.tdb' Apr 26 02:51:35 192.168.122.209 [38846.047463] [tempesta fw] modules are stopped Apr 26 02:51:35 192.168.122.209 [38846.261740] [tempesta fw] exiting... Apr 26 02:51:36 192.168.122.209 [38846.434986] [tdb] Shutdown Tempesta DB Apr 26 02:51:36 192.168.122.209 [38846.634170] End test: cache.test_h2_cache_control.TestH2CacheControl.test_must_revalidate_in_response_not_from_cache Apr 26 02:51:36 192.168.122.209 [38846.650878] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_no_cache_in_first_request Apr 26 02:51:37 192.168.122.209 [38847.786042] [tdb] Start Tempesta DB Apr 26 02:51:37 192.168.122.209 [38847.933706] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:51:38 192.168.122.209 [38849.262631] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38849.262631] Maybe that's fine, but it's worth checking the [38849.262631] config - if there is no relations between the [38849.262631] names, then host name confusion attack is possible. Apr 26 02:51:39 192.168.122.209 [38849.394839] [tempesta fw] Configuration processing is completed. Apr 26 02:51:39 192.168.122.209 [38849.443617] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:51:39 192.168.122.209 [38849.859037] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:51:39 192.168.122.209 [38849.884092] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:51:39 192.168.122.209 [38849.909688] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:51:39 192.168.122.209 [38849.961796] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:51:39 192.168.122.209 [38849.963534] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:51:39 192.168.122.209 [38850.005730] [tempesta fw] Tempesta FW is ready Apr 26 02:51:40 192.168.122.209 [38850.603868] [tdb] Close table 'client0.tdb' Apr 26 02:51:40 192.168.122.209 [38850.804118] [tdb] Close table 'sessions0.tdb' Apr 26 02:51:43 192.168.122.209 [38854.019991] [tdb] Close table 'cache0.tdb' Apr 26 02:51:43 192.168.122.209 [38854.289500] [tdb] Close table 'filter0.tdb' Apr 26 02:51:43 192.168.122.209 [38854.290138] [tempesta fw] modules are stopped Apr 26 02:51:44 192.168.122.209 [38854.465668] [tempesta fw] exiting... Apr 26 02:51:44 192.168.122.209 [38854.601061] [tdb] Shutdown Tempesta DB Apr 26 02:51:44 192.168.122.209 [38854.804632] End test: cache.test_h2_cache_control.TestH2CacheControl.test_no_cache_in_first_request Apr 26 02:51:44 192.168.122.209 [38854.824282] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_no_cache_in_response Apr 26 02:51:45 192.168.122.209 [38856.006747] [tdb] Start Tempesta DB Apr 26 02:51:45 192.168.122.209 [38856.142419] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:51:47 192.168.122.209 [38857.571119] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38857.571119] Maybe that's fine, but it's worth checking the [38857.571119] config - if there is no relations between the [38857.571119] names, then host name confusion attack is possible. Apr 26 02:51:47 192.168.122.209 [38857.693893] [tempesta fw] Configuration processing is completed. Apr 26 02:51:47 192.168.122.209 [38857.743296] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:51:47 192.168.122.209 [38858.155026] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:51:47 192.168.122.209 [38858.180660] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:51:47 192.168.122.209 [38858.207625] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:51:47 192.168.122.209 [38858.249830] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:51:47 192.168.122.209 [38858.250940] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:51:48 192.168.122.209 [38858.293863] [tempesta fw] Tempesta FW is ready Apr 26 02:51:48 192.168.122.209 [38858.911448] [tdb] Close table 'client0.tdb' Apr 26 02:51:48 192.168.122.209 [38859.086093] [tdb] Close table 'sessions0.tdb' Apr 26 02:51:51 192.168.122.209 [38862.270512] [tdb] Close table 'cache0.tdb' Apr 26 02:51:52 192.168.122.209 [38862.508500] [tdb] Close table 'filter0.tdb' Apr 26 02:51:52 192.168.122.209 [38862.508937] [tempesta fw] modules are stopped Apr 26 02:51:52 192.168.122.209 [38862.701646] [tempesta fw] exiting... Apr 26 02:51:52 192.168.122.209 [38862.850929] [tdb] Shutdown Tempesta DB Apr 26 02:51:52 192.168.122.209 [38863.061518] End test: cache.test_h2_cache_control.TestH2CacheControl.test_no_cache_in_response Apr 26 02:51:52 192.168.122.209 [38863.078681] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_no_cache_in_second_request Apr 26 02:51:54 192.168.122.209 [38864.303353] [tdb] Start Tempesta DB Apr 26 02:51:54 192.168.122.209 [38864.438731] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:51:55 192.168.122.209 [38865.864172] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38865.864172] Maybe that's fine, but it's worth checking the [38865.864172] config - if there is no relations between the [38865.864172] names, then host name confusion attack is possible. Apr 26 02:51:55 192.168.122.209 [38865.978002] [tempesta fw] Configuration processing is completed. Apr 26 02:51:55 192.168.122.209 [38866.031710] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:51:56 192.168.122.209 [38866.452989] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:51:56 192.168.122.209 [38866.487203] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:51:56 192.168.122.209 [38866.513582] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:51:56 192.168.122.209 [38866.570020] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:51:56 192.168.122.209 [38866.571733] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:51:56 192.168.122.209 [38866.609947] [tempesta fw] Tempesta FW is ready Apr 26 02:51:56 192.168.122.209 [38867.236644] [tdb] Close table 'client0.tdb' Apr 26 02:51:57 192.168.122.209 [38867.420936] [tdb] Close table 'sessions0.tdb' Apr 26 02:52:00 192.168.122.209 [38870.977600] [tdb] Close table 'cache0.tdb' Apr 26 02:52:01 192.168.122.209 [38871.618585] [tdb] Close table 'filter0.tdb' Apr 26 02:52:01 192.168.122.209 [38871.619021] [tempesta fw] modules are stopped Apr 26 02:52:03 192.168.122.209 [38873.648525] [tempesta fw] exiting... Apr 26 02:52:04 192.168.122.209 [38874.449850] [tdb] Shutdown Tempesta DB Apr 26 02:52:04 192.168.122.209 [38874.901468] End test: cache.test_h2_cache_control.TestH2CacheControl.test_no_cache_in_second_request Apr 26 02:52:04 192.168.122.209 [38874.933163] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_no_store_in_first_and_second_request_from_dynamic_table Apr 26 02:52:05 192.168.122.209 [38876.237982] [tdb] Start Tempesta DB Apr 26 02:52:06 192.168.122.209 [38876.402214] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:52:07 192.168.122.209 [38877.799380] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38877.799380] Maybe that's fine, but it's worth checking the [38877.799380] config - if there is no relations between the [38877.799380] names, then host name confusion attack is possible. Apr 26 02:52:07 192.168.122.209 [38877.922184] [tempesta fw] Configuration processing is completed. Apr 26 02:52:07 192.168.122.209 [38877.982927] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:52:08 192.168.122.209 [38878.400162] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:52:08 192.168.122.209 [38878.426228] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:52:08 192.168.122.209 [38878.451658] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:52:08 192.168.122.209 [38878.522162] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:52:08 192.168.122.209 [38878.523901] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:52:08 192.168.122.209 [38878.562098] [tempesta fw] Tempesta FW is ready Apr 26 02:52:08 192.168.122.209 [38879.192039] [tdb] Close table 'client0.tdb' Apr 26 02:52:09 192.168.122.209 [38879.375555] [tdb] Close table 'sessions0.tdb' Apr 26 02:52:12 192.168.122.209 [38882.571253] [tdb] Close table 'cache0.tdb' Apr 26 02:52:12 192.168.122.209 [38882.779153] [tdb] Close table 'filter0.tdb' Apr 26 02:52:12 192.168.122.209 [38882.779630] [tempesta fw] modules are stopped Apr 26 02:52:12 192.168.122.209 [38882.958105] [tempesta fw] exiting... Apr 26 02:52:12 192.168.122.209 [38883.111081] [tdb] Shutdown Tempesta DB Apr 26 02:52:13 192.168.122.209 [38883.363238] End test: cache.test_h2_cache_control.TestH2CacheControl.test_no_store_in_first_and_second_request_from_dynamic_table Apr 26 02:52:13 192.168.122.209 [38883.398062] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_no_store_in_first_request Apr 26 02:52:14 192.168.122.209 [38884.566859] [tdb] Start Tempesta DB Apr 26 02:52:14 192.168.122.209 [38884.710995] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:52:15 192.168.122.209 [38886.179475] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38886.179475] Maybe that's fine, but it's worth checking the [38886.179475] config - if there is no relations between the [38886.179475] names, then host name confusion attack is possible. Apr 26 02:52:16 192.168.122.209 [38886.294264] [tempesta fw] Configuration processing is completed. Apr 26 02:52:16 192.168.122.209 [38886.348262] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:52:16 192.168.122.209 [38886.771648] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:52:16 192.168.122.209 [38886.797190] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:52:16 192.168.122.209 [38886.823020] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:52:16 192.168.122.209 [38886.866269] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:52:16 192.168.122.209 [38886.866390] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:52:16 192.168.122.209 [38886.922195] [tempesta fw] Tempesta FW is ready Apr 26 02:52:17 192.168.122.209 [38887.529064] [tdb] Close table 'client0.tdb' Apr 26 02:52:17 192.168.122.209 [38887.734537] [tdb] Close table 'sessions0.tdb' Apr 26 02:52:20 192.168.122.209 [38890.953078] [tdb] Close table 'cache0.tdb' Apr 26 02:52:20 192.168.122.209 [38891.191914] [tdb] Close table 'filter0.tdb' Apr 26 02:52:20 192.168.122.209 [38891.192339] [tempesta fw] modules are stopped Apr 26 02:52:21 192.168.122.209 [38891.427043] [tempesta fw] exiting... Apr 26 02:52:21 192.168.122.209 [38891.591114] [tdb] Shutdown Tempesta DB Apr 26 02:52:21 192.168.122.209 [38891.832759] End test: cache.test_h2_cache_control.TestH2CacheControl.test_no_store_in_first_request Apr 26 02:52:21 192.168.122.209 [38891.849687] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_no_store_in_response Apr 26 02:52:22 192.168.122.209 [38893.061859] [tdb] Start Tempesta DB Apr 26 02:52:22 192.168.122.209 [38893.200477] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:52:24 192.168.122.209 [38894.587579] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38894.587579] Maybe that's fine, but it's worth checking the [38894.587579] config - if there is no relations between the [38894.587579] names, then host name confusion attack is possible. Apr 26 02:52:24 192.168.122.209 [38894.706377] [tempesta fw] Configuration processing is completed. Apr 26 02:52:24 192.168.122.209 [38894.756552] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:52:24 192.168.122.209 [38895.159665] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:52:24 192.168.122.209 [38895.185192] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:52:24 192.168.122.209 [38895.210828] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:52:24 192.168.122.209 [38895.258377] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:52:24 192.168.122.209 [38895.260097] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:52:25 192.168.122.209 [38895.314354] [tempesta fw] Tempesta FW is ready Apr 26 02:52:25 192.168.122.209 [38895.891806] [tdb] Close table 'client0.tdb' Apr 26 02:52:25 192.168.122.209 [38896.095662] [tdb] Close table 'sessions0.tdb' Apr 26 02:52:29 192.168.122.209 [38899.346309] [tdb] Close table 'cache0.tdb' Apr 26 02:52:29 192.168.122.209 [38899.559614] [tdb] Close table 'filter0.tdb' Apr 26 02:52:29 192.168.122.209 [38899.560073] [tempesta fw] modules are stopped Apr 26 02:52:29 192.168.122.209 [38899.754705] [tempesta fw] exiting... Apr 26 02:52:29 192.168.122.209 [38899.941844] [tdb] Shutdown Tempesta DB Apr 26 02:52:29 192.168.122.209 [38900.176105] End test: cache.test_h2_cache_control.TestH2CacheControl.test_no_store_in_response Apr 26 02:52:29 192.168.122.209 [38900.197223] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_no_store_in_second_request Apr 26 02:52:31 192.168.122.209 [38901.414028] [tdb] Start Tempesta DB Apr 26 02:52:31 192.168.122.209 [38901.566763] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:52:32 192.168.122.209 [38902.983734] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38902.983734] Maybe that's fine, but it's worth checking the [38902.983734] config - if there is no relations between the [38902.983734] names, then host name confusion attack is possible. Apr 26 02:52:32 192.168.122.209 [38903.106482] [tempesta fw] Configuration processing is completed. Apr 26 02:52:32 192.168.122.209 [38903.155596] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:52:33 192.168.122.209 [38903.580521] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:52:33 192.168.122.209 [38903.607049] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:52:33 192.168.122.209 [38903.633689] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:52:33 192.168.122.209 [38903.678474] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:52:33 192.168.122.209 [38903.680216] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:52:33 192.168.122.209 [38903.718435] [tempesta fw] Tempesta FW is ready Apr 26 02:52:34 192.168.122.209 [38904.306141] [tdb] Close table 'client0.tdb' Apr 26 02:52:34 192.168.122.209 [38904.513785] [tdb] Close table 'sessions0.tdb' Apr 26 02:52:37 192.168.122.209 [38907.674236] [tdb] Close table 'cache0.tdb' Apr 26 02:52:37 192.168.122.209 [38907.896379] [tdb] Close table 'filter0.tdb' Apr 26 02:52:37 192.168.122.209 [38907.896817] [tempesta fw] modules are stopped Apr 26 02:52:37 192.168.122.209 [38908.105868] [tempesta fw] exiting... Apr 26 02:52:37 192.168.122.209 [38908.241625] [tdb] Shutdown Tempesta DB Apr 26 02:52:38 192.168.122.209 [38908.459731] End test: cache.test_h2_cache_control.TestH2CacheControl.test_no_store_in_second_request Apr 26 02:52:38 192.168.122.209 [38908.477855] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_only_if_cached_in_request_from_cache Apr 26 02:52:39 192.168.122.209 [38909.650624] [tdb] Start Tempesta DB Apr 26 02:52:39 192.168.122.209 [38909.800418] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:52:40 192.168.122.209 [38911.215625] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38911.215625] Maybe that's fine, but it's worth checking the [38911.215625] config - if there is no relations between the [38911.215625] names, then host name confusion attack is possible. Apr 26 02:52:41 192.168.122.209 [38911.318601] [tempesta fw] Configuration processing is completed. Apr 26 02:52:41 192.168.122.209 [38911.371243] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:52:41 192.168.122.209 [38911.783935] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:52:41 192.168.122.209 [38911.818123] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:52:41 192.168.122.209 [38911.843948] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:52:41 192.168.122.209 [38911.890587] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:52:41 192.168.122.209 [38911.892290] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:52:41 192.168.122.209 [38911.930554] [tempesta fw] Tempesta FW is ready Apr 26 02:52:42 192.168.122.209 [38912.560324] [tdb] Close table 'client0.tdb' Apr 26 02:52:42 192.168.122.209 [38912.747569] [tdb] Close table 'sessions0.tdb' Apr 26 02:52:45 192.168.122.209 [38915.919328] [tdb] Close table 'cache0.tdb' Apr 26 02:52:45 192.168.122.209 [38916.151079] [tdb] Close table 'filter0.tdb' Apr 26 02:52:45 192.168.122.209 [38916.151512] [tempesta fw] modules are stopped Apr 26 02:52:46 192.168.122.209 [38916.379013] [tempesta fw] exiting... Apr 26 02:52:46 192.168.122.209 [38916.537395] [tdb] Shutdown Tempesta DB Apr 26 02:52:46 192.168.122.209 [38916.804960] End test: cache.test_h2_cache_control.TestH2CacheControl.test_only_if_cached_in_request_from_cache Apr 26 02:52:46 192.168.122.209 [38916.829515] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_only_if_cached_in_request_from_cache_from_dynamic_table Apr 26 02:52:47 192.168.122.209 [38918.019949] [tdb] Start Tempesta DB Apr 26 02:52:47 192.168.122.209 [38918.162739] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:52:49 192.168.122.209 [38919.515918] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38919.515918] Maybe that's fine, but it's worth checking the [38919.515918] config - if there is no relations between the [38919.515918] names, then host name confusion attack is possible. Apr 26 02:52:49 192.168.122.209 [38919.646695] [tempesta fw] Configuration processing is completed. Apr 26 02:52:49 192.168.122.209 [38919.699396] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:52:49 192.168.122.209 [38920.108546] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:52:49 192.168.122.209 [38920.134209] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:52:49 192.168.122.209 [38920.160914] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:52:49 192.168.122.209 [38920.206685] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:52:49 192.168.122.209 [38920.208411] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:52:49 192.168.122.209 [38920.254577] [tempesta fw] Tempesta FW is ready Apr 26 02:52:50 192.168.122.209 [38920.894051] [tdb] Close table 'client0.tdb' Apr 26 02:52:50 192.168.122.209 [38921.092602] [tdb] Close table 'sessions0.tdb' Apr 26 02:52:53 192.168.122.209 [38924.230416] [tdb] Close table 'cache0.tdb' Apr 26 02:52:54 192.168.122.209 [38924.500507] [tdb] Close table 'filter0.tdb' Apr 26 02:52:54 192.168.122.209 [38924.500934] [tempesta fw] modules are stopped Apr 26 02:52:54 192.168.122.209 [38924.708113] [tempesta fw] exiting... Apr 26 02:52:54 192.168.122.209 [38924.849027] [tdb] Shutdown Tempesta DB Apr 26 02:52:54 192.168.122.209 [38925.081499] End test: cache.test_h2_cache_control.TestH2CacheControl.test_only_if_cached_in_request_from_cache_from_dynamic_table Apr 26 02:52:54 192.168.122.209 [38925.104074] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_only_if_cached_in_request_not_from_cache Apr 26 02:52:55 192.168.122.209 [38926.222676] [tdb] Start Tempesta DB Apr 26 02:52:56 192.168.122.209 [38926.375485] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:52:57 192.168.122.209 [38927.812020] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38927.812020] Maybe that's fine, but it's worth checking the [38927.812020] config - if there is no relations between the [38927.812020] names, then host name confusion attack is possible. Apr 26 02:52:57 192.168.122.209 [38927.934840] [tempesta fw] Configuration processing is completed. Apr 26 02:52:57 192.168.122.209 [38927.983616] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:52:58 192.168.122.209 [38928.385656] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:52:58 192.168.122.209 [38928.419522] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:52:58 192.168.122.209 [38928.444829] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:52:58 192.168.122.209 [38928.486727] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:52:58 192.168.122.209 [38928.487778] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:52:58 192.168.122.209 [38928.530748] [tempesta fw] Tempesta FW is ready Apr 26 02:53:00 192.168.122.209 [38930.683839] [tempesta fw] Warning: resource not cached, status 504: 127.0.0.2 Apr 26 02:53:00 192.168.122.209 [38931.114657] [tdb] Close table 'client0.tdb' Apr 26 02:53:01 192.168.122.209 [38931.304164] [tdb] Close table 'sessions0.tdb' Apr 26 02:53:04 192.168.122.209 [38934.436956] [tdb] Close table 'cache0.tdb' Apr 26 02:53:04 192.168.122.209 [38934.676504] [tdb] Close table 'filter0.tdb' Apr 26 02:53:04 192.168.122.209 [38934.677031] [tempesta fw] modules are stopped Apr 26 02:53:04 192.168.122.209 [38934.867476] [tempesta fw] exiting... Apr 26 02:53:04 192.168.122.209 [38935.040040] [tdb] Shutdown Tempesta DB Apr 26 02:53:04 192.168.122.209 [38935.241776] End test: cache.test_h2_cache_control.TestH2CacheControl.test_only_if_cached_in_request_not_from_cache Apr 26 02:53:04 192.168.122.209 [38935.272671] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_private_in_response Apr 26 02:53:06 192.168.122.209 [38936.469522] [tdb] Start Tempesta DB Apr 26 02:53:06 192.168.122.209 [38936.616716] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:53:07 192.168.122.209 [38938.000183] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38938.000183] Maybe that's fine, but it's worth checking the [38938.000183] config - if there is no relations between the [38938.000183] names, then host name confusion attack is possible. Apr 26 02:53:07 192.168.122.209 [38938.130941] [tempesta fw] Configuration processing is completed. Apr 26 02:53:07 192.168.122.209 [38938.179517] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:53:08 192.168.122.209 [38938.583277] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:53:08 192.168.122.209 [38938.608640] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:53:08 192.168.122.209 [38938.633916] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:53:08 192.168.122.209 [38938.682928] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:53:08 192.168.122.209 [38938.684683] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:53:08 192.168.122.209 [38938.726867] [tempesta fw] Tempesta FW is ready Apr 26 02:53:09 192.168.122.209 [38939.327554] [tdb] Close table 'client0.tdb' Apr 26 02:53:09 192.168.122.209 [38939.546489] [tdb] Close table 'sessions0.tdb' Apr 26 02:53:12 192.168.122.209 [38942.736672] [tdb] Close table 'cache0.tdb' Apr 26 02:53:12 192.168.122.209 [38942.987300] [tdb] Close table 'filter0.tdb' Apr 26 02:53:12 192.168.122.209 [38942.987756] [tempesta fw] modules are stopped Apr 26 02:53:12 192.168.122.209 [38943.200430] [tempesta fw] exiting... Apr 26 02:53:13 192.168.122.209 [38943.342357] [tdb] Shutdown Tempesta DB Apr 26 02:53:13 192.168.122.209 [38943.562903] End test: cache.test_h2_cache_control.TestH2CacheControl.test_private_in_response Apr 26 02:53:13 192.168.122.209 [38943.578431] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_proxy_revalidate_in_response_from_cache Apr 26 02:53:14 192.168.122.209 [38944.811621] [tdb] Start Tempesta DB Apr 26 02:53:14 192.168.122.209 [38944.959888] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:53:16 192.168.122.209 [38946.384304] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38946.384304] Maybe that's fine, but it's worth checking the [38946.384304] config - if there is no relations between the [38946.384304] names, then host name confusion attack is possible. Apr 26 02:53:16 192.168.122.209 [38946.503077] [tempesta fw] Configuration processing is completed. Apr 26 02:53:16 192.168.122.209 [38946.596541] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:53:16 192.168.122.209 [38947.013679] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:53:16 192.168.122.209 [38947.039890] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:53:16 192.168.122.209 [38947.066874] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:53:16 192.168.122.209 [38947.107046] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:53:16 192.168.122.209 [38947.108766] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:53:16 192.168.122.209 [38947.146980] [tempesta fw] Tempesta FW is ready Apr 26 02:53:17 192.168.122.209 [38947.795337] [tdb] Close table 'client0.tdb' Apr 26 02:53:17 192.168.122.209 [38947.997668] [tdb] Close table 'sessions0.tdb' Apr 26 02:53:20 192.168.122.209 [38951.155349] [tdb] Close table 'cache0.tdb' Apr 26 02:53:21 192.168.122.209 [38951.418297] [tdb] Close table 'filter0.tdb' Apr 26 02:53:21 192.168.122.209 [38951.418720] [tempesta fw] modules are stopped Apr 26 02:53:21 192.168.122.209 [38951.639950] [tempesta fw] exiting... Apr 26 02:53:21 192.168.122.209 [38951.782221] [tdb] Shutdown Tempesta DB Apr 26 02:53:21 192.168.122.209 [38952.008231] End test: cache.test_h2_cache_control.TestH2CacheControl.test_proxy_revalidate_in_response_from_cache Apr 26 02:53:21 192.168.122.209 [38952.033925] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_proxy_revalidate_in_response_max_stale_in_request_from_cache Apr 26 02:53:22 192.168.122.209 [38953.236307] [tdb] Start Tempesta DB Apr 26 02:53:23 192.168.122.209 [38953.394406] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:53:24 192.168.122.209 [38954.784395] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38954.784395] Maybe that's fine, but it's worth checking the [38954.784395] config - if there is no relations between the [38954.784395] names, then host name confusion attack is possible. Apr 26 02:53:24 192.168.122.209 [38954.903162] [tempesta fw] Configuration processing is completed. Apr 26 02:53:24 192.168.122.209 [38954.957206] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:53:25 192.168.122.209 [38955.360999] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:53:25 192.168.122.209 [38955.386146] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:53:25 192.168.122.209 [38955.411437] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:53:25 192.168.122.209 [38955.455066] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:53:25 192.168.122.209 [38955.456838] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:53:25 192.168.122.209 [38955.503084] [tempesta fw] Tempesta FW is ready Apr 26 02:53:25 192.168.122.209 [38956.111097] [tdb] Close table 'client0.tdb' Apr 26 02:53:26 192.168.122.209 [38956.328155] [tdb] Close table 'sessions0.tdb' Apr 26 02:53:29 192.168.122.209 [38959.535142] [tdb] Close table 'cache0.tdb' Apr 26 02:53:29 192.168.122.209 [38959.755735] [tdb] Close table 'filter0.tdb' Apr 26 02:53:29 192.168.122.209 [38959.756172] [tempesta fw] modules are stopped Apr 26 02:53:29 192.168.122.209 [38959.991160] [tempesta fw] exiting... Apr 26 02:53:29 192.168.122.209 [38960.141331] [tdb] Shutdown Tempesta DB Apr 26 02:53:30 192.168.122.209 [38960.372684] End test: cache.test_h2_cache_control.TestH2CacheControl.test_proxy_revalidate_in_response_max_stale_in_request_from_cache Apr 26 02:53:30 192.168.122.209 [38960.394663] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_proxy_revalidate_in_response_max_stale_in_request_not_from_cache Apr 26 02:53:31 192.168.122.209 [38961.585325] [tdb] Start Tempesta DB Apr 26 02:53:31 192.168.122.209 [38961.722585] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:53:32 192.168.122.209 [38963.096474] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38963.096474] Maybe that's fine, but it's worth checking the [38963.096474] config - if there is no relations between the [38963.096474] names, then host name confusion attack is possible. Apr 26 02:53:32 192.168.122.209 [38963.215261] [tempesta fw] Configuration processing is completed. Apr 26 02:53:32 192.168.122.209 [38963.265413] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:53:33 192.168.122.209 [38963.681575] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:53:33 192.168.122.209 [38963.707278] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:53:33 192.168.122.209 [38963.732858] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:53:33 192.168.122.209 [38963.815291] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:53:33 192.168.122.209 [38963.817042] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:53:33 192.168.122.209 [38963.855118] [tempesta fw] Tempesta FW is ready Apr 26 02:53:36 192.168.122.209 [38966.471296] [tdb] Close table 'client0.tdb' Apr 26 02:53:36 192.168.122.209 [38966.661699] [tdb] Close table 'sessions0.tdb' Apr 26 02:53:39 192.168.122.209 [38969.840556] [tdb] Close table 'cache0.tdb' Apr 26 02:53:39 192.168.122.209 [38970.085506] [tdb] Close table 'filter0.tdb' Apr 26 02:53:39 192.168.122.209 [38970.085959] [tempesta fw] modules are stopped Apr 26 02:53:39 192.168.122.209 [38970.266358] [tempesta fw] exiting... Apr 26 02:53:40 192.168.122.209 [38970.461247] [tdb] Shutdown Tempesta DB Apr 26 02:53:40 192.168.122.209 [38970.693747] End test: cache.test_h2_cache_control.TestH2CacheControl.test_proxy_revalidate_in_response_max_stale_in_request_not_from_cache Apr 26 02:53:40 192.168.122.209 [38970.715832] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_proxy_revalidate_in_response_not_from_cache Apr 26 02:53:41 192.168.122.209 [38971.909899] [tdb] Start Tempesta DB Apr 26 02:53:41 192.168.122.209 [38972.052855] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:53:43 192.168.122.209 [38973.544800] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38973.544800] Maybe that's fine, but it's worth checking the [38973.544800] config - if there is no relations between the [38973.544800] names, then host name confusion attack is possible. Apr 26 02:53:43 192.168.122.209 [38973.667416] [tempesta fw] Configuration processing is completed. Apr 26 02:53:43 192.168.122.209 [38973.721938] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:53:43 192.168.122.209 [38974.142339] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:53:43 192.168.122.209 [38974.168147] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:53:43 192.168.122.209 [38974.195119] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:53:43 192.168.122.209 [38974.247401] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:53:43 192.168.122.209 [38974.249140] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:53:43 192.168.122.209 [38974.287359] [tempesta fw] Tempesta FW is ready Apr 26 02:53:46 192.168.122.209 [38976.898674] [tdb] Close table 'client0.tdb' Apr 26 02:53:46 192.168.122.209 [38977.102697] [tdb] Close table 'sessions0.tdb' Apr 26 02:53:49 192.168.122.209 [38980.262044] [tdb] Close table 'cache0.tdb' Apr 26 02:53:50 192.168.122.209 [38980.500094] [tdb] Close table 'filter0.tdb' Apr 26 02:53:50 192.168.122.209 [38980.500508] [tempesta fw] modules are stopped Apr 26 02:53:50 192.168.122.209 [38980.680925] [tempesta fw] exiting... Apr 26 02:53:50 192.168.122.209 [38980.819090] [tdb] Shutdown Tempesta DB Apr 26 02:53:50 192.168.122.209 [38981.051973] End test: cache.test_h2_cache_control.TestH2CacheControl.test_proxy_revalidate_in_response_not_from_cache Apr 26 02:53:50 192.168.122.209 [38981.080754] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_s_maxage_0_in_response Apr 26 02:53:51 192.168.122.209 [38982.260631] [tdb] Start Tempesta DB Apr 26 02:53:52 192.168.122.209 [38982.403469] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:53:53 192.168.122.209 [38983.784723] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38983.784723] Maybe that's fine, but it's worth checking the [38983.784723] config - if there is no relations between the [38983.784723] names, then host name confusion attack is possible. Apr 26 02:53:53 192.168.122.209 [38983.911514] [tempesta fw] Configuration processing is completed. Apr 26 02:53:53 192.168.122.209 [38983.965152] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:53:54 192.168.122.209 [38984.373646] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:53:54 192.168.122.209 [38984.399575] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:53:54 192.168.122.209 [38984.426247] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:53:54 192.168.122.209 [38984.479502] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:53:54 192.168.122.209 [38984.481250] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:53:54 192.168.122.209 [38984.539453] [tempesta fw] Tempesta FW is ready Apr 26 02:53:54 192.168.122.209 [38985.174556] [tdb] Close table 'client0.tdb' Apr 26 02:53:55 192.168.122.209 [38985.373785] [tdb] Close table 'sessions0.tdb' Apr 26 02:53:58 192.168.122.209 [38988.542360] [tdb] Close table 'cache0.tdb' Apr 26 02:53:58 192.168.122.209 [38988.781812] [tdb] Close table 'filter0.tdb' Apr 26 02:53:58 192.168.122.209 [38988.782242] [tempesta fw] modules are stopped Apr 26 02:53:58 192.168.122.209 [38988.967786] [tempesta fw] exiting... Apr 26 02:53:58 192.168.122.209 [38989.108912] [tdb] Shutdown Tempesta DB Apr 26 02:53:59 192.168.122.209 [38989.319744] End test: cache.test_h2_cache_control.TestH2CacheControl.test_s_maxage_0_in_response Apr 26 02:53:59 192.168.122.209 [38989.332842] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_s_maxage_1_in_response_sleep_2 Apr 26 02:54:00 192.168.122.209 [38990.514560] [tdb] Start Tempesta DB Apr 26 02:54:00 192.168.122.209 [38990.651031] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:54:01 192.168.122.209 [38991.973460] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [38991.973460] Maybe that's fine, but it's worth checking the [38991.973460] config - if there is no relations between the [38991.973460] names, then host name confusion attack is possible. Apr 26 02:54:01 192.168.122.209 [38992.091611] [tempesta fw] Configuration processing is completed. Apr 26 02:54:01 192.168.122.209 [38992.139074] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:54:02 192.168.122.209 [38992.556073] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:54:02 192.168.122.209 [38992.582373] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:54:02 192.168.122.209 [38992.608857] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:54:02 192.168.122.209 [38992.655523] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:54:02 192.168.122.209 [38992.657269] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:54:02 192.168.122.209 [38992.707552] [tempesta fw] Tempesta FW is ready Apr 26 02:54:05 192.168.122.209 [38995.301826] [tdb] Close table 'client0.tdb' Apr 26 02:54:05 192.168.122.209 [38995.501323] [tdb] Close table 'sessions0.tdb' Apr 26 02:54:08 192.168.122.209 [38998.742343] [tdb] Close table 'cache0.tdb' Apr 26 02:54:08 192.168.122.209 [38998.949694] [tdb] Close table 'filter0.tdb' Apr 26 02:54:08 192.168.122.209 [38998.950131] [tempesta fw] modules are stopped Apr 26 02:54:08 192.168.122.209 [38999.153853] [tempesta fw] exiting... Apr 26 02:54:09 192.168.122.209 [38999.343805] [tdb] Shutdown Tempesta DB Apr 26 02:54:09 192.168.122.209 [38999.565138] End test: cache.test_h2_cache_control.TestH2CacheControl.test_s_maxage_1_in_response_sleep_2 Apr 26 02:54:09 192.168.122.209 [38999.587328] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_s_maxage_1_max_age_5_in_response_sleep_2 Apr 26 02:54:10 192.168.122.209 [39000.694353] [tdb] Start Tempesta DB Apr 26 02:54:10 192.168.122.209 [39000.839668] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:54:11 192.168.122.209 [39002.252974] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39002.252974] Maybe that's fine, but it's worth checking the [39002.252974] config - if there is no relations between the [39002.252974] names, then host name confusion attack is possible. Apr 26 02:54:12 192.168.122.209 [39002.367778] [tempesta fw] Configuration processing is completed. Apr 26 02:54:12 192.168.122.209 [39002.420652] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:54:12 192.168.122.209 [39002.832852] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:54:12 192.168.122.209 [39002.858195] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:54:12 192.168.122.209 [39002.883161] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:54:12 192.168.122.209 [39002.927663] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:54:12 192.168.122.209 [39002.928951] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:54:12 192.168.122.209 [39002.979676] [tempesta fw] Tempesta FW is ready Apr 26 02:54:15 192.168.122.209 [39005.608589] [tdb] Close table 'client0.tdb' Apr 26 02:54:15 192.168.122.209 [39005.792148] [tdb] Close table 'sessions0.tdb' Apr 26 02:54:18 192.168.122.209 [39009.025147] [tdb] Close table 'cache0.tdb' Apr 26 02:54:18 192.168.122.209 [39009.287434] [tdb] Close table 'filter0.tdb' Apr 26 02:54:18 192.168.122.209 [39009.288278] [tempesta fw] modules are stopped Apr 26 02:54:19 192.168.122.209 [39009.497199] [tempesta fw] exiting... Apr 26 02:54:19 192.168.122.209 [39009.658037] [tdb] Shutdown Tempesta DB Apr 26 02:54:19 192.168.122.209 [39009.916802] End test: cache.test_h2_cache_control.TestH2CacheControl.test_s_maxage_1_max_age_5_in_response_sleep_2 Apr 26 02:54:19 192.168.122.209 [39009.929182] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_s_maxage_2_in_response_sleep_0 Apr 26 02:54:20 192.168.122.209 [39011.199324] [tdb] Start Tempesta DB Apr 26 02:54:21 192.168.122.209 [39011.373246] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:54:22 192.168.122.209 [39012.828651] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39012.828651] Maybe that's fine, but it's worth checking the [39012.828651] config - if there is no relations between the [39012.828651] names, then host name confusion attack is possible. Apr 26 02:54:22 192.168.122.209 [39012.955923] [tempesta fw] Configuration processing is completed. Apr 26 02:54:22 192.168.122.209 [39013.045429] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:54:23 192.168.122.209 [39013.503136] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:54:23 192.168.122.209 [39013.533552] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:54:23 192.168.122.209 [39013.564104] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:54:23 192.168.122.209 [39013.611870] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:54:23 192.168.122.209 [39013.613671] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:54:23 192.168.122.209 [39013.655760] [tempesta fw] Tempesta FW is ready Apr 26 02:54:23 192.168.122.209 [39014.284875] [tdb] Close table 'client0.tdb' Apr 26 02:54:24 192.168.122.209 [39014.507945] [tdb] Close table 'sessions0.tdb' Apr 26 02:54:27 192.168.122.209 [39017.649489] [tdb] Close table 'cache0.tdb' Apr 26 02:54:27 192.168.122.209 [39017.880038] [tdb] Close table 'filter0.tdb' Apr 26 02:54:27 192.168.122.209 [39017.880485] [tempesta fw] modules are stopped Apr 26 02:54:27 192.168.122.209 [39018.064858] [tempesta fw] exiting... Apr 26 02:54:27 192.168.122.209 [39018.245612] [tdb] Shutdown Tempesta DB Apr 26 02:54:28 192.168.122.209 [39018.494645] End test: cache.test_h2_cache_control.TestH2CacheControl.test_s_maxage_2_in_response_sleep_0 Apr 26 02:54:28 192.168.122.209 [39018.507282] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_s_maxage_in_request Apr 26 02:54:29 192.168.122.209 [39019.712330] [tdb] Start Tempesta DB Apr 26 02:54:29 192.168.122.209 [39019.876851] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:54:30 192.168.122.209 [39021.268750] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39021.268750] Maybe that's fine, but it's worth checking the [39021.268750] config - if there is no relations between the [39021.268750] names, then host name confusion attack is possible. Apr 26 02:54:31 192.168.122.209 [39021.392006] [tempesta fw] Configuration processing is completed. Apr 26 02:54:31 192.168.122.209 [39021.442552] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:54:31 192.168.122.209 [39021.900608] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:54:31 192.168.122.209 [39021.928507] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:54:31 192.168.122.209 [39021.959522] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:54:31 192.168.122.209 [39022.003974] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:54:31 192.168.122.209 [39022.005705] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:54:31 192.168.122.209 [39022.043922] [tempesta fw] Tempesta FW is ready Apr 26 02:54:32 192.168.122.209 [39022.672956] [tdb] Close table 'client0.tdb' Apr 26 02:54:32 192.168.122.209 [39022.881401] [tdb] Close table 'sessions0.tdb' Apr 26 02:54:35 192.168.122.209 [39026.069977] [tdb] Close table 'cache0.tdb' Apr 26 02:54:36 192.168.122.209 [39026.310513] [tdb] Close table 'filter0.tdb' Apr 26 02:54:36 192.168.122.209 [39026.310979] [tempesta fw] modules are stopped Apr 26 02:54:36 192.168.122.209 [39026.520393] [tempesta fw] exiting... Apr 26 02:54:36 192.168.122.209 [39026.673517] [tdb] Shutdown Tempesta DB Apr 26 02:54:36 192.168.122.209 [39026.940435] End test: cache.test_h2_cache_control.TestH2CacheControl.test_s_maxage_in_request Apr 26 02:54:36 192.168.122.209 [39026.962906] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_s_maxage_in_response_and_max_stale_in_request Apr 26 02:54:37 192.168.122.209 [39028.231799] [tdb] Start Tempesta DB Apr 26 02:54:38 192.168.122.209 [39028.400724] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:54:39 192.168.122.209 [39029.857407] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39029.857407] Maybe that's fine, but it's worth checking the [39029.857407] config - if there is no relations between the [39029.857407] names, then host name confusion attack is possible. Apr 26 02:54:39 192.168.122.209 [39029.988095] [tempesta fw] Configuration processing is completed. Apr 26 02:54:39 192.168.122.209 [39030.053505] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:54:40 192.168.122.209 [39030.519057] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:54:40 192.168.122.209 [39030.559263] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:54:40 192.168.122.209 [39030.590318] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:54:40 192.168.122.209 [39030.648095] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:54:40 192.168.122.209 [39030.649841] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:54:40 192.168.122.209 [39030.687959] [tempesta fw] Tempesta FW is ready Apr 26 02:54:43 192.168.122.209 [39033.328165] [tdb] Close table 'client0.tdb' Apr 26 02:54:43 192.168.122.209 [39033.520799] [tdb] Close table 'sessions0.tdb' Apr 26 02:54:46 192.168.122.209 [39036.690196] [tdb] Close table 'cache0.tdb' Apr 26 02:54:46 192.168.122.209 [39036.950146] [tdb] Close table 'filter0.tdb' Apr 26 02:54:46 192.168.122.209 [39036.950592] [tempesta fw] modules are stopped Apr 26 02:54:46 192.168.122.209 [39037.143737] [tempesta fw] exiting... Apr 26 02:54:47 192.168.122.209 [39037.310680] [tdb] Shutdown Tempesta DB Apr 26 02:54:47 192.168.122.209 [39037.560415] End test: cache.test_h2_cache_control.TestH2CacheControl.test_s_maxage_in_response_and_max_stale_in_request Apr 26 02:54:47 192.168.122.209 [39037.575723] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_same_authorization_in_requests Apr 26 02:54:48 192.168.122.209 [39038.766719] [tdb] Start Tempesta DB Apr 26 02:54:48 192.168.122.209 [39038.896326] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:54:50 192.168.122.209 [39040.293498] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39040.293498] Maybe that's fine, but it's worth checking the [39040.293498] config - if there is no relations between the [39040.293498] names, then host name confusion attack is possible. Apr 26 02:54:50 192.168.122.209 [39040.424226] [tempesta fw] Configuration processing is completed. Apr 26 02:54:50 192.168.122.209 [39040.477822] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:54:50 192.168.122.209 [39040.902789] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:54:50 192.168.122.209 [39040.932865] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:54:50 192.168.122.209 [39040.964821] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:54:50 192.168.122.209 [39041.028202] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:54:50 192.168.122.209 [39041.029938] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:54:50 192.168.122.209 [39041.068150] [tempesta fw] Tempesta FW is ready Apr 26 02:54:51 192.168.122.209 [39041.707642] [tdb] Close table 'client0.tdb' Apr 26 02:54:51 192.168.122.209 [39041.910105] [tdb] Close table 'sessions0.tdb' Apr 26 02:54:54 192.168.122.209 [39045.103132] [tdb] Close table 'cache0.tdb' Apr 26 02:54:55 192.168.122.209 [39045.344989] [tdb] Close table 'filter0.tdb' Apr 26 02:54:55 192.168.122.209 [39045.345454] [tempesta fw] modules are stopped Apr 26 02:54:55 192.168.122.209 [39045.568665] [tempesta fw] exiting... Apr 26 02:54:55 192.168.122.209 [39045.740329] [tdb] Shutdown Tempesta DB Apr 26 02:54:55 192.168.122.209 [39045.966658] End test: cache.test_h2_cache_control.TestH2CacheControl.test_same_authorization_in_requests Apr 26 02:54:55 192.168.122.209 [39045.983509] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_same_authorization_in_requests_from_dynamic_table Apr 26 02:54:56 192.168.122.209 [39047.176939] [tdb] Start Tempesta DB Apr 26 02:54:57 192.168.122.209 [39047.325091] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:54:58 192.168.122.209 [39048.733560] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39048.733560] Maybe that's fine, but it's worth checking the [39048.733560] config - if there is no relations between the [39048.733560] names, then host name confusion attack is possible. Apr 26 02:54:58 192.168.122.209 [39048.864402] [tempesta fw] Configuration processing is completed. Apr 26 02:54:58 192.168.122.209 [39048.921260] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:54:59 192.168.122.209 [39049.400993] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:54:59 192.168.122.209 [39049.429463] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:54:59 192.168.122.209 [39049.457327] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:54:59 192.168.122.209 [39049.512381] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:54:59 192.168.122.209 [39049.514204] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:54:59 192.168.122.209 [39049.552251] [tempesta fw] Tempesta FW is ready Apr 26 02:54:59 192.168.122.209 [39050.193273] [tdb] Close table 'client0.tdb' Apr 26 02:55:00 192.168.122.209 [39050.374432] [tdb] Close table 'sessions0.tdb' Apr 26 02:55:03 192.168.122.209 [39053.617551] [tdb] Close table 'cache0.tdb' Apr 26 02:55:03 192.168.122.209 [39053.882910] [tdb] Close table 'filter0.tdb' Apr 26 02:55:03 192.168.122.209 [39053.883360] [tempesta fw] modules are stopped Apr 26 02:55:03 192.168.122.209 [39054.050395] [tempesta fw] exiting... Apr 26 02:55:03 192.168.122.209 [39054.171624] [tdb] Shutdown Tempesta DB Apr 26 02:55:04 192.168.122.209 [39054.446369] End test: cache.test_h2_cache_control.TestH2CacheControl.test_same_authorization_in_requests_from_dynamic_table Apr 26 02:55:04 192.168.122.209 [39054.456442] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_same_authorization_in_requests_max_age_in_response Apr 26 02:55:05 192.168.122.209 [39055.647835] [tdb] Start Tempesta DB Apr 26 02:55:05 192.168.122.209 [39055.808742] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:55:06 192.168.122.209 [39057.241674] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39057.241674] Maybe that's fine, but it's worth checking the [39057.241674] config - if there is no relations between the [39057.241674] names, then host name confusion attack is possible. Apr 26 02:55:07 192.168.122.209 [39057.360473] [tempesta fw] Configuration processing is completed. Apr 26 02:55:07 192.168.122.209 [39057.441684] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:55:07 192.168.122.209 [39057.873673] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:55:07 192.168.122.209 [39057.908886] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:55:07 192.168.122.209 [39057.936109] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:55:07 192.168.122.209 [39057.992367] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:55:07 192.168.122.209 [39057.994093] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:55:07 192.168.122.209 [39058.032365] [tempesta fw] Tempesta FW is ready Apr 26 02:55:08 192.168.122.209 [39058.685187] [tdb] Close table 'client0.tdb' Apr 26 02:55:08 192.168.122.209 [39058.890151] [tdb] Close table 'sessions0.tdb' Apr 26 02:55:11 192.168.122.209 [39062.054938] [tdb] Close table 'cache0.tdb' Apr 26 02:55:11 192.168.122.209 [39062.286598] [tdb] Close table 'filter0.tdb' Apr 26 02:55:11 192.168.122.209 [39062.287029] [tempesta fw] modules are stopped Apr 26 02:55:12 192.168.122.209 [39062.466574] [tempesta fw] exiting... Apr 26 02:55:12 192.168.122.209 [39062.612321] [tdb] Shutdown Tempesta DB Apr 26 02:55:12 192.168.122.209 [39062.834115] End test: cache.test_h2_cache_control.TestH2CacheControl.test_same_authorization_in_requests_max_age_in_response Apr 26 02:55:12 192.168.122.209 [39062.845226] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_same_authorization_in_requests_no_transform_in_response Apr 26 02:55:13 192.168.122.209 [39064.118982] [tdb] Start Tempesta DB Apr 26 02:55:13 192.168.122.209 [39064.252479] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:55:15 192.168.122.209 [39065.709772] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39065.709772] Maybe that's fine, but it's worth checking the [39065.709772] config - if there is no relations between the [39065.709772] names, then host name confusion attack is possible. Apr 26 02:55:15 192.168.122.209 [39065.824541] [tempesta fw] Configuration processing is completed. Apr 26 02:55:15 192.168.122.209 [39065.880902] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:55:15 192.168.122.209 [39066.290984] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:55:16 192.168.122.209 [39066.317172] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:55:16 192.168.122.209 [39066.342859] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:55:16 192.168.122.209 [39066.412539] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:55:16 192.168.122.209 [39066.414294] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:55:16 192.168.122.209 [39066.472382] [tempesta fw] Tempesta FW is ready Apr 26 02:55:16 192.168.122.209 [39067.098332] [tdb] Close table 'client0.tdb' Apr 26 02:55:16 192.168.122.209 [39067.296852] [tdb] Close table 'sessions0.tdb' Apr 26 02:55:20 192.168.122.209 [39070.484131] [tdb] Close table 'cache0.tdb' Apr 26 02:55:20 192.168.122.209 [39070.716596] [tdb] Close table 'filter0.tdb' Apr 26 02:55:20 192.168.122.209 [39070.717043] [tempesta fw] modules are stopped Apr 26 02:55:20 192.168.122.209 [39070.938460] [tempesta fw] exiting... Apr 26 02:55:20 192.168.122.209 [39071.122095] [tdb] Shutdown Tempesta DB Apr 26 02:55:21 192.168.122.209 [39071.341346] End test: cache.test_h2_cache_control.TestH2CacheControl.test_same_authorization_in_requests_no_transform_in_response Apr 26 02:55:21 192.168.122.209 [39071.354799] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_set_cookie_no_cached Apr 26 02:55:22 192.168.122.209 [39072.488231] [tdb] Start Tempesta DB Apr 26 02:55:22 192.168.122.209 [39072.647405] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:55:23 192.168.122.209 [39074.037872] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39074.037872] Maybe that's fine, but it's worth checking the [39074.037872] config - if there is no relations between the [39074.037872] names, then host name confusion attack is possible. Apr 26 02:55:23 192.168.122.209 [39074.152620] [tempesta fw] Configuration processing is completed. Apr 26 02:55:23 192.168.122.209 [39074.202863] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:55:24 192.168.122.209 [39074.607063] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:55:24 192.168.122.209 [39074.632121] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:55:24 192.168.122.209 [39074.657717] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:55:24 192.168.122.209 [39074.740608] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:55:24 192.168.122.209 [39074.742347] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:55:24 192.168.122.209 [39074.784562] [tempesta fw] Tempesta FW is ready Apr 26 02:55:25 192.168.122.209 [39075.408263] [tdb] Close table 'client0.tdb' Apr 26 02:55:25 192.168.122.209 [39075.606412] [tdb] Close table 'sessions0.tdb' Apr 26 02:55:28 192.168.122.209 [39078.787826] [tdb] Close table 'cache0.tdb' Apr 26 02:55:28 192.168.122.209 [39079.010301] [tdb] Close table 'filter0.tdb' Apr 26 02:55:28 192.168.122.209 [39079.010739] [tempesta fw] modules are stopped Apr 26 02:55:28 192.168.122.209 [39079.202778] [tempesta fw] exiting... Apr 26 02:55:29 192.168.122.209 [39079.378340] [tdb] Shutdown Tempesta DB Apr 26 02:55:29 192.168.122.209 [39079.619931] End test: cache.test_h2_cache_control.TestH2CacheControl.test_set_cookie_no_cached Apr 26 02:55:29 192.168.122.209 [39079.640045] Start test: cache.test_h2_cache_control.TestH2CacheControlIgnore.test_ignore_max_age_not_ignore_s_maxage Apr 26 02:55:30 192.168.122.209 [39080.861204] [tdb] Start Tempesta DB Apr 26 02:55:30 192.168.122.209 [39081.007605] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:55:32 192.168.122.209 [39082.425527] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39082.425527] Maybe that's fine, but it's worth checking the [39082.425527] config - if there is no relations between the [39082.425527] names, then host name confusion attack is possible. Apr 26 02:55:32 192.168.122.209 [39082.584733] [tempesta fw] Configuration processing is completed. Apr 26 02:55:32 192.168.122.209 [39082.634564] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:55:32 192.168.122.209 [39083.048938] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:55:32 192.168.122.209 [39083.074471] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:55:32 192.168.122.209 [39083.100350] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:55:32 192.168.122.209 [39083.148723] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:55:32 192.168.122.209 [39083.150450] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:55:32 192.168.122.209 [39083.200605] [tempesta fw] Tempesta FW is ready Apr 26 02:55:35 192.168.122.209 [39085.837590] [tdb] Close table 'client0.tdb' Apr 26 02:55:35 192.168.122.209 [39086.023222] [tdb] Close table 'sessions0.tdb' Apr 26 02:55:38 192.168.122.209 [39089.135440] [tdb] Close table 'cache0.tdb' Apr 26 02:55:39 192.168.122.209 [39089.349453] [tdb] Close table 'filter0.tdb' Apr 26 02:55:39 192.168.122.209 [39089.349885] [tempesta fw] modules are stopped Apr 26 02:55:39 192.168.122.209 [39089.555174] [tempesta fw] exiting... Apr 26 02:55:39 192.168.122.209 [39089.724647] [tdb] Shutdown Tempesta DB Apr 26 02:55:39 192.168.122.209 [39089.948662] End test: cache.test_h2_cache_control.TestH2CacheControlIgnore.test_ignore_max_age_not_ignore_s_maxage Apr 26 02:55:39 192.168.122.209 [39089.959243] Start test: cache.test_h2_cache_control.TestH2CacheControlIgnore.test_ignore_max_age_s_maxage Apr 26 02:55:40 192.168.122.209 [39091.098807] [tdb] Start Tempesta DB Apr 26 02:55:40 192.168.122.209 [39091.244249] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:55:42 192.168.122.209 [39092.646079] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39092.646079] Maybe that's fine, but it's worth checking the [39092.646079] config - if there is no relations between the [39092.646079] names, then host name confusion attack is possible. Apr 26 02:55:42 192.168.122.209 [39092.784854] [tempesta fw] Configuration processing is completed. Apr 26 02:55:42 192.168.122.209 [39092.833497] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:55:42 192.168.122.209 [39093.248995] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:55:42 192.168.122.209 [39093.275143] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:55:43 192.168.122.209 [39093.302430] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:55:43 192.168.122.209 [39093.364856] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:55:43 192.168.122.209 [39093.366602] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:55:43 192.168.122.209 [39093.408841] [tempesta fw] Tempesta FW is ready Apr 26 02:55:45 192.168.122.209 [39096.020326] [tdb] Close table 'client0.tdb' Apr 26 02:55:45 192.168.122.209 [39096.214942] [tdb] Close table 'sessions0.tdb' Apr 26 02:55:49 192.168.122.209 [39099.373654] [tdb] Close table 'cache0.tdb' Apr 26 02:55:49 192.168.122.209 [39099.620876] [tdb] Close table 'filter0.tdb' Apr 26 02:55:49 192.168.122.209 [39099.621345] [tempesta fw] modules are stopped Apr 26 02:55:49 192.168.122.209 [39099.866733] [tempesta fw] exiting... Apr 26 02:55:49 192.168.122.209 [39100.015699] [tdb] Shutdown Tempesta DB Apr 26 02:55:49 192.168.122.209 [39100.252021] End test: cache.test_h2_cache_control.TestH2CacheControlIgnore.test_ignore_max_age_s_maxage Apr 26 02:55:49 192.168.122.209 [39100.265799] Start test: cache.test_h2_cache_control.TestH2CacheControlIgnore.test_ignore_max_stale_in_request Apr 26 02:55:51 192.168.122.209 [39101.503673] [tdb] Start Tempesta DB Apr 26 02:55:51 192.168.122.209 [39101.657492] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:55:52 192.168.122.209 [39103.034308] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39103.034308] Maybe that's fine, but it's worth checking the [39103.034308] config - if there is no relations between the [39103.034308] names, then host name confusion attack is possible. Apr 26 02:55:52 192.168.122.209 [39103.169008] [tempesta fw] Configuration processing is completed. Apr 26 02:55:52 192.168.122.209 [39103.222509] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:55:53 192.168.122.209 [39103.687757] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:55:53 192.168.122.209 [39103.717095] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:55:53 192.168.122.209 [39103.746125] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:55:53 192.168.122.209 [39103.784918] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:55:53 192.168.122.209 [39103.785980] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:55:53 192.168.122.209 [39103.824931] [tempesta fw] Tempesta FW is ready Apr 26 02:55:56 192.168.122.209 [39106.456113] [tdb] Close table 'client0.tdb' Apr 26 02:55:56 192.168.122.209 [39106.647186] [tdb] Close table 'sessions0.tdb' Apr 26 02:55:59 192.168.122.209 [39109.812319] [tdb] Close table 'cache0.tdb' Apr 26 02:55:59 192.168.122.209 [39110.055329] [tdb] Close table 'filter0.tdb' Apr 26 02:55:59 192.168.122.209 [39110.056050] [tempesta fw] modules are stopped Apr 26 02:55:59 192.168.122.209 [39110.248046] [tempesta fw] exiting... Apr 26 02:56:00 192.168.122.209 [39110.415040] [tdb] Shutdown Tempesta DB Apr 26 02:56:00 192.168.122.209 [39110.642656] End test: cache.test_h2_cache_control.TestH2CacheControlIgnore.test_ignore_max_stale_in_request Apr 26 02:56:00 192.168.122.209 [39110.657642] Start test: cache.test_h2_cache_control.TestH2CacheControlIgnore.test_ignore_must_revalidate Apr 26 02:56:01 192.168.122.209 [39111.847803] [tdb] Start Tempesta DB Apr 26 02:56:01 192.168.122.209 [39112.000399] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:56:03 192.168.122.209 [39113.358393] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39113.358393] Maybe that's fine, but it's worth checking the [39113.358393] config - if there is no relations between the [39113.358393] names, then host name confusion attack is possible. Apr 26 02:56:03 192.168.122.209 [39113.497112] [tempesta fw] Configuration processing is completed. Apr 26 02:56:03 192.168.122.209 [39113.546530] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:56:03 192.168.122.209 [39113.962943] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:56:03 192.168.122.209 [39113.990204] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:56:03 192.168.122.209 [39114.018257] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:56:03 192.168.122.209 [39114.069039] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:56:03 192.168.122.209 [39114.070754] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:56:03 192.168.122.209 [39114.117065] [tempesta fw] Tempesta FW is ready Apr 26 02:56:06 192.168.122.209 [39116.714199] [tdb] Close table 'client0.tdb' Apr 26 02:56:06 192.168.122.209 [39116.900413] [tdb] Close table 'sessions0.tdb' Apr 26 02:56:09 192.168.122.209 [39120.015760] [tdb] Close table 'cache0.tdb' Apr 26 02:56:09 192.168.122.209 [39120.246737] [tdb] Close table 'filter0.tdb' Apr 26 02:56:09 192.168.122.209 [39120.247170] [tempesta fw] modules are stopped Apr 26 02:56:10 192.168.122.209 [39120.448878] [tempesta fw] exiting... Apr 26 02:56:10 192.168.122.209 [39120.632243] [tdb] Shutdown Tempesta DB Apr 26 02:56:10 192.168.122.209 [39120.861762] End test: cache.test_h2_cache_control.TestH2CacheControlIgnore.test_ignore_must_revalidate Apr 26 02:56:10 192.168.122.209 [39120.876225] Start test: cache.test_h2_cache_control.TestH2CacheControlIgnore.test_ignore_public_with_authorization Apr 26 02:56:11 192.168.122.209 [39122.064355] [tdb] Start Tempesta DB Apr 26 02:56:11 192.168.122.209 [39122.212934] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:56:13 192.168.122.209 [39123.666263] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39123.666263] Maybe that's fine, but it's worth checking the [39123.666263] config - if there is no relations between the [39123.666263] names, then host name confusion attack is possible. Apr 26 02:56:13 192.168.122.209 [39123.809253] [tempesta fw] Configuration processing is completed. Apr 26 02:56:13 192.168.122.209 [39123.871935] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:56:14 192.168.122.209 [39124.299063] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:56:14 192.168.122.209 [39124.324897] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:56:14 192.168.122.209 [39124.351185] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:56:14 192.168.122.209 [39124.409234] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:56:14 192.168.122.209 [39124.410911] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:56:14 192.168.122.209 [39124.461177] [tempesta fw] Tempesta FW is ready Apr 26 02:56:14 192.168.122.209 [39125.031438] [tdb] Close table 'client0.tdb' Apr 26 02:56:14 192.168.122.209 [39125.252908] [tdb] Close table 'sessions0.tdb' Apr 26 02:56:18 192.168.122.209 [39128.395744] [tdb] Close table 'cache0.tdb' Apr 26 02:56:18 192.168.122.209 [39128.612207] [tdb] Close table 'filter0.tdb' Apr 26 02:56:18 192.168.122.209 [39128.612645] [tempesta fw] modules are stopped Apr 26 02:56:18 192.168.122.209 [39128.804301] [tempesta fw] exiting... Apr 26 02:56:18 192.168.122.209 [39128.943107] [tdb] Shutdown Tempesta DB Apr 26 02:56:18 192.168.122.209 [39129.166383] End test: cache.test_h2_cache_control.TestH2CacheControlIgnore.test_ignore_public_with_authorization Apr 26 02:56:18 192.168.122.209 [39129.176591] Start test: cache.test_h2_cache_control.TestH2CacheControlIgnore.test_multi_ignore_private_no_cache_no_store Apr 26 02:56:20 192.168.122.209 [39130.336616] [tdb] Start Tempesta DB Apr 26 02:56:20 192.168.122.209 [39130.476781] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:56:21 192.168.122.209 [39131.895594] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39131.895594] Maybe that's fine, but it's worth checking the [39131.895594] config - if there is no relations between the [39131.895594] names, then host name confusion attack is possible. Apr 26 02:56:21 192.168.122.209 [39132.025341] [tempesta fw] Configuration processing is completed. Apr 26 02:56:21 192.168.122.209 [39132.074293] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:56:22 192.168.122.209 [39132.510750] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:56:22 192.168.122.209 [39132.537020] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:56:22 192.168.122.209 [39132.562967] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:56:22 192.168.122.209 [39132.601270] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:56:22 192.168.122.209 [39132.602346] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:56:22 192.168.122.209 [39132.641275] [tempesta fw] Tempesta FW is ready Apr 26 02:56:22 192.168.122.209 [39133.267068] [tdb] Close table 'client0.tdb' Apr 26 02:56:23 192.168.122.209 [39133.484082] [tdb] Close table 'sessions0.tdb' Apr 26 02:56:26 192.168.122.209 [39136.692646] [tdb] Close table 'cache0.tdb' Apr 26 02:56:26 192.168.122.209 [39136.918058] [tdb] Close table 'filter0.tdb' Apr 26 02:56:26 192.168.122.209 [39136.918494] [tempesta fw] modules are stopped Apr 26 02:56:26 192.168.122.209 [39137.129390] [tempesta fw] exiting... Apr 26 02:56:26 192.168.122.209 [39137.295348] [tdb] Shutdown Tempesta DB Apr 26 02:56:27 192.168.122.209 [39137.550877] End test: cache.test_h2_cache_control.TestH2CacheControlIgnore.test_multi_ignore_private_no_cache_no_store Apr 26 02:56:27 192.168.122.209 [39137.560895] Start test: cache.test_h2_cache_control.TestH2CacheType.test_cache_is_shared Apr 26 02:56:28 192.168.122.209 [39138.740599] [tdb] Start Tempesta DB Apr 26 02:56:28 192.168.122.209 [39138.893430] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:56:29 192.168.122.209 [39140.250667] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39140.250667] Maybe that's fine, but it's worth checking the [39140.250667] config - if there is no relations between the [39140.250667] names, then host name confusion attack is possible. Apr 26 02:56:30 192.168.122.209 [39140.373401] [tempesta fw] Configuration processing is completed. Apr 26 02:56:30 192.168.122.209 [39140.424582] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:56:30 192.168.122.209 [39140.834857] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:56:30 192.168.122.209 [39140.860318] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:56:30 192.168.122.209 [39140.885671] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:56:30 192.168.122.209 [39140.925444] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 02:56:30 192.168.122.209 [39140.927154] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:56:30 192.168.122.209 [39140.965379] [tempesta fw] Tempesta FW is ready Apr 26 02:56:33 192.168.122.209 [39143.608212] [tdb] Close table 'client0.tdb' Apr 26 02:56:33 192.168.122.209 [39143.798942] [tdb] Close table 'sessions0.tdb' Apr 26 02:56:36 192.168.122.209 [39146.984902] [tdb] Close table 'cache0.tdb' Apr 26 02:56:36 192.168.122.209 [39147.241798] [tdb] Close table 'filter0.tdb' Apr 26 02:56:36 192.168.122.209 [39147.242241] [tempesta fw] modules are stopped Apr 26 02:56:37 192.168.122.209 [39147.460285] [tempesta fw] exiting... Apr 26 02:56:37 192.168.122.209 [39147.636969] [tdb] Shutdown Tempesta DB Apr 26 02:56:37 192.168.122.209 [39147.853857] End test: cache.test_h2_cache_control.TestH2CacheType.test_cache_is_shared Apr 26 02:56:37 192.168.122.209 [39147.865524] Start test: cache.test_purge.TestPurgeAcl.test_purge_acl_fail Apr 26 02:56:38 192.168.122.209 [39149.048749] [tdb] Start Tempesta DB Apr 26 02:56:38 192.168.122.209 [39149.198245] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:56:40 192.168.122.209 [39150.749600] [tempesta fw] Configuration processing is completed. Apr 26 02:56:40 192.168.122.209 [39150.805097] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:56:40 192.168.122.209 [39151.218262] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:56:40 192.168.122.209 [39151.243992] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:56:40 192.168.122.209 [39151.269513] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:56:41 192.168.122.209 [39151.321570] [tempesta fw] Open listen socket on: ::1 Apr 26 02:56:41 192.168.122.209 [39151.323180] [tempesta fw] Open listen socket on: 127.0.0.1 Apr 26 02:56:41 192.168.122.209 [39151.373529] [tempesta fw] Tempesta FW is ready Apr 26 02:56:41 192.168.122.209 [39151.535620] [tempesta fw] Warning: purge: ACL violation, status 403: 127.0.0.2 Apr 26 02:56:41 192.168.122.209 [39151.986485] [tdb] Close table 'client0.tdb' Apr 26 02:56:41 192.168.122.209 [39152.178105] [tdb] Close table 'sessions0.tdb' Apr 26 02:56:45 192.168.122.209 [39155.364833] [tdb] Close table 'cache0.tdb' Apr 26 02:56:45 192.168.122.209 [39155.608044] [tdb] Close table 'filter0.tdb' Apr 26 02:56:45 192.168.122.209 [39155.608483] [tempesta fw] modules are stopped Apr 26 02:56:45 192.168.122.209 [39155.789604] [tempesta fw] exiting... Apr 26 02:56:45 192.168.122.209 [39155.933729] [tdb] Shutdown Tempesta DB Apr 26 02:56:45 192.168.122.209 [39156.172969] End test: cache.test_purge.TestPurgeAcl.test_purge_acl_fail Apr 26 02:56:45 192.168.122.209 [39156.189192] Start test: cache.test_purge.TestPurgeAcl.test_purge_acl_ipv4 Apr 26 02:56:47 192.168.122.209 [39157.347842] [tdb] Start Tempesta DB Apr 26 02:56:47 192.168.122.209 [39157.496413] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:56:48 192.168.122.209 [39159.049617] [tempesta fw] Configuration processing is completed. Apr 26 02:56:48 192.168.122.209 [39159.102116] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:56:49 192.168.122.209 [39159.525025] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:56:49 192.168.122.209 [39159.551963] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:56:49 192.168.122.209 [39159.585663] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:56:49 192.168.122.209 [39159.633662] [tempesta fw] Open listen socket on: ::1 Apr 26 02:56:49 192.168.122.209 [39159.634890] [tempesta fw] Open listen socket on: 127.0.0.1 Apr 26 02:56:49 192.168.122.209 [39159.677625] [tempesta fw] Tempesta FW is ready Apr 26 02:56:49 192.168.122.209 [39159.843026] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 02:56:49 192.168.122.209 [39160.292614] [tdb] Close table 'client0.tdb' Apr 26 02:56:50 192.168.122.209 [39160.498754] [tdb] Close table 'sessions0.tdb' Apr 26 02:56:53 192.168.122.209 [39163.728358] [tdb] Close table 'cache0.tdb' Apr 26 02:56:53 192.168.122.209 [39163.963491] [tdb] Close table 'filter0.tdb' Apr 26 02:56:53 192.168.122.209 [39163.963949] [tempesta fw] modules are stopped Apr 26 02:56:53 192.168.122.209 [39164.124749] [tempesta fw] exiting... Apr 26 02:56:53 192.168.122.209 [39164.287856] [tdb] Shutdown Tempesta DB Apr 26 02:56:54 192.168.122.209 [39164.495773] End test: cache.test_purge.TestPurgeAcl.test_purge_acl_ipv4 Apr 26 02:56:54 192.168.122.209 [39164.513680] Start test: cache.test_purge.TestPurgeAcl.test_purge_acl_ipv4_and_ipv6 Apr 26 02:56:55 192.168.122.209 [39165.674858] [tdb] Start Tempesta DB Apr 26 02:56:55 192.168.122.209 [39165.829686] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:56:57 192.168.122.209 [39167.305792] [tempesta fw] Configuration processing is completed. Apr 26 02:56:57 192.168.122.209 [39167.355162] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:56:57 192.168.122.209 [39167.763505] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:56:57 192.168.122.209 [39167.801277] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:56:57 192.168.122.209 [39167.837225] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:56:57 192.168.122.209 [39167.877633] [tempesta fw] Open listen socket on: ::1 Apr 26 02:56:57 192.168.122.209 [39167.878404] [tempesta fw] Open listen socket on: 127.0.0.1 Apr 26 02:56:57 192.168.122.209 [39167.917603] [tempesta fw] Tempesta FW is ready Apr 26 02:56:57 192.168.122.209 [39168.064598] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 02:56:58 192.168.122.209 [39168.541957] [tdb] Close table 'client0.tdb' Apr 26 02:56:58 192.168.122.209 [39168.771295] [tdb] Close table 'sessions0.tdb' Apr 26 02:57:01 192.168.122.209 [39171.932042] [tdb] Close table 'cache0.tdb' Apr 26 02:57:01 192.168.122.209 [39172.150647] [tdb] Close table 'filter0.tdb' Apr 26 02:57:01 192.168.122.209 [39172.151086] [tempesta fw] modules are stopped Apr 26 02:57:02 192.168.122.209 [39172.335211] [tempesta fw] exiting... Apr 26 02:57:02 192.168.122.209 [39172.463602] [tdb] Shutdown Tempesta DB Apr 26 02:57:02 192.168.122.209 [39172.709156] End test: cache.test_purge.TestPurgeAcl.test_purge_acl_ipv4_and_ipv6 Apr 26 02:57:02 192.168.122.209 [39172.722971] Start test: cache.test_purge.TestPurgeAcl.test_purge_acl_ipv4_with_mask Apr 26 02:57:03 192.168.122.209 [39173.919099] [tdb] Start Tempesta DB Apr 26 02:57:03 192.168.122.209 [39174.053169] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:57:05 192.168.122.209 [39175.617829] [tempesta fw] Configuration processing is completed. Apr 26 02:57:05 192.168.122.209 [39175.675647] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:57:05 192.168.122.209 [39176.089041] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:57:05 192.168.122.209 [39176.114779] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:57:05 192.168.122.209 [39176.140247] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:57:05 192.168.122.209 [39176.185893] [tempesta fw] Open listen socket on: ::1 Apr 26 02:57:05 192.168.122.209 [39176.187433] [tempesta fw] Open listen socket on: 127.0.0.1 Apr 26 02:57:05 192.168.122.209 [39176.225826] [tempesta fw] Tempesta FW is ready Apr 26 02:57:06 192.168.122.209 [39176.420307] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 02:57:06 192.168.122.209 [39176.904177] [tdb] Close table 'client0.tdb' Apr 26 02:57:06 192.168.122.209 [39177.111162] [tdb] Close table 'sessions0.tdb' Apr 26 02:57:09 192.168.122.209 [39180.231202] [tdb] Close table 'cache0.tdb' Apr 26 02:57:10 192.168.122.209 [39180.490187] [tdb] Close table 'filter0.tdb' Apr 26 02:57:10 192.168.122.209 [39180.490621] [tempesta fw] modules are stopped Apr 26 02:57:10 192.168.122.209 [39180.676017] [tempesta fw] exiting... Apr 26 02:57:10 192.168.122.209 [39180.843063] [tdb] Shutdown Tempesta DB Apr 26 02:57:10 192.168.122.209 [39181.068764] End test: cache.test_purge.TestPurgeAcl.test_purge_acl_ipv4_with_mask Apr 26 02:57:10 192.168.122.209 [39181.083190] Start test: cache.test_purge.TestPurgeAcl.test_purge_acl_ipv6 Apr 26 02:57:11 192.168.122.209 [39182.264726] [tdb] Start Tempesta DB Apr 26 02:57:12 192.168.122.209 [39182.400380] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:57:13 192.168.122.209 [39183.953983] [tempesta fw] Configuration processing is completed. Apr 26 02:57:13 192.168.122.209 [39184.003017] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:57:14 192.168.122.209 [39184.411235] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:57:14 192.168.122.209 [39184.437312] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:57:14 192.168.122.209 [39184.463325] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:57:14 192.168.122.209 [39184.509917] [tempesta fw] Open listen socket on: ::1 Apr 26 02:57:14 192.168.122.209 [39184.511438] [tempesta fw] Open listen socket on: 127.0.0.1 Apr 26 02:57:14 192.168.122.209 [39184.557927] [tempesta fw] Tempesta FW is ready Apr 26 02:57:14 192.168.122.209 [39184.741633] [tempesta fw] Warning: purge: success, status 200: ::1 Apr 26 02:57:14 192.168.122.209 [39185.217904] [tdb] Close table 'client0.tdb' Apr 26 02:57:15 192.168.122.209 [39185.411391] [tdb] Close table 'sessions0.tdb' Apr 26 02:57:18 192.168.122.209 [39188.603150] [tdb] Close table 'cache0.tdb' Apr 26 02:57:18 192.168.122.209 [39188.849182] [tdb] Close table 'filter0.tdb' Apr 26 02:57:18 192.168.122.209 [39188.849614] [tempesta fw] modules are stopped Apr 26 02:57:18 192.168.122.209 [39189.014269] [tempesta fw] exiting... Apr 26 02:57:18 192.168.122.209 [39189.170331] [tdb] Shutdown Tempesta DB Apr 26 02:57:19 192.168.122.209 [39189.361496] End test: cache.test_purge.TestPurgeAcl.test_purge_acl_ipv6 Apr 26 02:57:19 192.168.122.209 [39189.380001] Start test: cache.test_purge.TestPurgeAcl.test_purge_acl_ipv6_with_mask Apr 26 02:57:20 192.168.122.209 [39190.530995] [tdb] Start Tempesta DB Apr 26 02:57:20 192.168.122.209 [39190.680753] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:57:21 192.168.122.209 [39192.254082] [tempesta fw] Configuration processing is completed. Apr 26 02:57:22 192.168.122.209 [39192.312087] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:57:22 192.168.122.209 [39192.723947] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:57:22 192.168.122.209 [39192.749577] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:57:22 192.168.122.209 [39192.775524] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:57:22 192.168.122.209 [39192.822089] [tempesta fw] Open listen socket on: ::1 Apr 26 02:57:22 192.168.122.209 [39192.823640] [tempesta fw] Open listen socket on: 127.0.0.1 Apr 26 02:57:22 192.168.122.209 [39192.866024] [tempesta fw] Tempesta FW is ready Apr 26 02:57:22 192.168.122.209 [39193.040795] [tempesta fw] Warning: purge: success, status 200: ::1 Apr 26 02:57:23 192.168.122.209 [39193.508552] [tdb] Close table 'client0.tdb' Apr 26 02:57:23 192.168.122.209 [39193.706134] [tdb] Close table 'sessions0.tdb' Apr 26 02:57:26 192.168.122.209 [39196.850109] [tdb] Close table 'cache0.tdb' Apr 26 02:57:26 192.168.122.209 [39197.106712] [tdb] Close table 'filter0.tdb' Apr 26 02:57:26 192.168.122.209 [39197.107146] [tempesta fw] modules are stopped Apr 26 02:57:26 192.168.122.209 [39197.276323] [tempesta fw] exiting... Apr 26 02:57:27 192.168.122.209 [39197.410850] [tdb] Shutdown Tempesta DB Apr 26 02:57:27 192.168.122.209 [39197.635367] End test: cache.test_purge.TestPurgeAcl.test_purge_acl_ipv6_with_mask Apr 26 02:57:27 192.168.122.209 [39197.660532] Start test: cache.test_purge.TestPurgeAcl.test_purge_fail Apr 26 02:57:28 192.168.122.209 [39198.747541] [tdb] Start Tempesta DB Apr 26 02:57:28 192.168.122.209 [39198.890308] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:57:30 192.168.122.209 [39200.322238] [tempesta fw] Configuration processing is completed. Apr 26 02:57:30 192.168.122.209 [39200.371332] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:57:30 192.168.122.209 [39200.789247] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:57:30 192.168.122.209 [39200.823256] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:57:30 192.168.122.209 [39200.848726] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:57:30 192.168.122.209 [39200.898180] [tempesta fw] Open listen socket on: ::1 Apr 26 02:57:30 192.168.122.209 [39200.899727] [tempesta fw] Open listen socket on: 127.0.0.1 Apr 26 02:57:30 192.168.122.209 [39200.958083] [tempesta fw] Tempesta FW is ready Apr 26 02:57:30 192.168.122.209 [39201.125466] [tempesta fw] Warning: purge: not configured, status 403: 127.0.0.2 Apr 26 02:57:31 192.168.122.209 [39201.579301] [tdb] Close table 'client0.tdb' Apr 26 02:57:31 192.168.122.209 [39201.775185] [tdb] Close table 'sessions0.tdb' Apr 26 02:57:34 192.168.122.209 [39204.945659] [tdb] Close table 'cache0.tdb' Apr 26 02:57:34 192.168.122.209 [39205.183669] [tdb] Close table 'filter0.tdb' Apr 26 02:57:34 192.168.122.209 [39205.184104] [tempesta fw] modules are stopped Apr 26 02:57:35 192.168.122.209 [39205.453939] [tempesta fw] exiting... Apr 26 02:57:35 192.168.122.209 [39205.620450] [tdb] Shutdown Tempesta DB Apr 26 02:57:35 192.168.122.209 [39205.838335] End test: cache.test_purge.TestPurgeAcl.test_purge_fail Apr 26 02:57:35 192.168.122.209 [39205.855690] Start test: cache.test_purge.TestPurgeImmediate.test_purge Apr 26 02:57:36 192.168.122.209 [39206.997534] [tdb] Start Tempesta DB Apr 26 02:57:36 192.168.122.209 [39207.145766] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:57:38 192.168.122.209 [39208.898291] [tempesta fw] Configuration processing is completed. Apr 26 02:57:38 192.168.122.209 [39208.949647] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:57:39 192.168.122.209 [39209.359384] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:57:39 192.168.122.209 [39209.384480] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:57:39 192.168.122.209 [39209.417540] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:57:39 192.168.122.209 [39209.458320] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:57:39 192.168.122.209 [39209.498190] [tempesta fw] Tempesta FW is ready Apr 26 02:57:39 192.168.122.209 [39209.687245] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 02:57:39 192.168.122.209 [39210.189548] [tdb] Close table 'client0.tdb' Apr 26 02:57:40 192.168.122.209 [39210.379412] [tdb] Close table 'sessions0.tdb' Apr 26 02:57:43 192.168.122.209 [39213.521422] [tdb] Close table 'cache0.tdb' Apr 26 02:57:43 192.168.122.209 [39213.768962] [tdb] Close table 'filter0.tdb' Apr 26 02:57:43 192.168.122.209 [39213.769397] [tempesta fw] modules are stopped Apr 26 02:57:43 192.168.122.209 [39213.934346] [tempesta fw] exiting... Apr 26 02:57:43 192.168.122.209 [39214.089935] [tdb] Shutdown Tempesta DB Apr 26 02:57:44 192.168.122.209 [39214.319557] End test: cache.test_purge.TestPurgeImmediate.test_purge Apr 26 02:57:44 192.168.122.209 [39214.335899] Start test: cache.test_purge.TestPurgeImmediate.test_purge_get_basic Apr 26 02:57:45 192.168.122.209 [39215.485149] [tdb] Start Tempesta DB Apr 26 02:57:45 192.168.122.209 [39215.641679] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:57:47 192.168.122.209 [39217.418373] [tempesta fw] Configuration processing is completed. Apr 26 02:57:47 192.168.122.209 [39217.468507] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:57:47 192.168.122.209 [39217.877792] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:57:47 192.168.122.209 [39217.903621] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:57:47 192.168.122.209 [39217.931548] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:57:47 192.168.122.209 [39217.970392] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:57:47 192.168.122.209 [39218.014338] [tempesta fw] Tempesta FW is ready Apr 26 02:57:48 192.168.122.209 [39218.689594] [tdb] Close table 'client0.tdb' Apr 26 02:57:48 192.168.122.209 [39218.910917] [tdb] Close table 'sessions0.tdb' Apr 26 02:57:51 192.168.122.209 [39222.081225] [tdb] Close table 'cache0.tdb' Apr 26 02:57:52 192.168.122.209 [39222.322032] [tdb] Close table 'filter0.tdb' Apr 26 02:57:52 192.168.122.209 [39222.322845] [tempesta fw] modules are stopped Apr 26 02:57:52 192.168.122.209 [39222.491886] [tempesta fw] exiting... Apr 26 02:57:52 192.168.122.209 [39222.614099] [tdb] Shutdown Tempesta DB Apr 26 02:57:52 192.168.122.209 [39222.840365] End test: cache.test_purge.TestPurgeImmediate.test_purge_get_basic Apr 26 02:57:52 192.168.122.209 [39222.860600] Start test: cache.test_purge.TestPurgeImmediate.test_purge_get_garbage Apr 26 02:57:53 192.168.122.209 [39224.035635] [tdb] Start Tempesta DB Apr 26 02:57:53 192.168.122.209 [39224.192543] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:57:55 192.168.122.209 [39226.010481] [tempesta fw] Configuration processing is completed. Apr 26 02:57:55 192.168.122.209 [39226.061075] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:57:56 192.168.122.209 [39226.483956] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:57:56 192.168.122.209 [39226.509527] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:57:56 192.168.122.209 [39226.535660] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:57:56 192.168.122.209 [39226.578431] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:57:56 192.168.122.209 [39226.618437] [tempesta fw] Tempesta FW is ready Apr 26 02:57:56 192.168.122.209 [39226.790323] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 02:57:56 192.168.122.209 [39226.822309] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 02:57:57 192.168.122.209 [39227.353553] [tdb] Close table 'client0.tdb' Apr 26 02:57:57 192.168.122.209 [39227.558085] [tdb] Close table 'sessions0.tdb' Apr 26 02:58:00 192.168.122.209 [39230.709364] [tdb] Close table 'cache0.tdb' Apr 26 02:58:00 192.168.122.209 [39230.945404] [tdb] Close table 'filter0.tdb' Apr 26 02:58:00 192.168.122.209 [39230.945806] [tempesta fw] modules are stopped Apr 26 02:58:00 192.168.122.209 [39231.110362] [tempesta fw] exiting... Apr 26 02:58:00 192.168.122.209 [39231.233461] [tdb] Shutdown Tempesta DB Apr 26 02:58:01 192.168.122.209 [39231.458403] End test: cache.test_purge.TestPurgeImmediate.test_purge_get_garbage Apr 26 02:58:01 192.168.122.209 [39231.476807] Start test: cache.test_purge.TestPurgeImmediate.test_purge_get_uncacheable Apr 26 02:58:02 192.168.122.209 [39232.696837] [tdb] Start Tempesta DB Apr 26 02:58:02 192.168.122.209 [39232.845011] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:58:04 192.168.122.209 [39234.618578] [tempesta fw] Configuration processing is completed. Apr 26 02:58:04 192.168.122.209 [39234.670835] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:58:04 192.168.122.209 [39235.072678] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:58:04 192.168.122.209 [39235.098062] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:58:04 192.168.122.209 [39235.128472] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:58:04 192.168.122.209 [39235.174631] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:58:04 192.168.122.209 [39235.230561] [tempesta fw] Tempesta FW is ready Apr 26 02:58:05 192.168.122.209 [39235.867631] [tdb] Close table 'client0.tdb' Apr 26 02:58:05 192.168.122.209 [39236.059533] [tdb] Close table 'sessions0.tdb' Apr 26 02:58:08 192.168.122.209 [39239.189719] [tdb] Close table 'cache0.tdb' Apr 26 02:58:09 192.168.122.209 [39239.404197] [tdb] Close table 'filter0.tdb' Apr 26 02:58:09 192.168.122.209 [39239.404628] [tempesta fw] modules are stopped Apr 26 02:58:09 192.168.122.209 [39239.582549] [tempesta fw] exiting... Apr 26 02:58:09 192.168.122.209 [39239.724880] [tdb] Shutdown Tempesta DB Apr 26 02:58:09 192.168.122.209 [39239.939233] End test: cache.test_purge.TestPurgeImmediate.test_purge_get_uncacheable Apr 26 02:58:09 192.168.122.209 [39239.951499] Start test: cache.test_purge.TestPurgeImmediate.test_purge_get_uncached Apr 26 02:58:10 192.168.122.209 [39241.197851] [tdb] Start Tempesta DB Apr 26 02:58:11 192.168.122.209 [39241.353272] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:58:12 192.168.122.209 [39243.238726] [tempesta fw] Configuration processing is completed. Apr 26 02:58:12 192.168.122.209 [39243.298111] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:58:13 192.168.122.209 [39243.752712] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:58:13 192.168.122.209 [39243.782035] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:58:13 192.168.122.209 [39243.810972] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:58:13 192.168.122.209 [39243.854694] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:58:13 192.168.122.209 [39243.906650] [tempesta fw] Tempesta FW is ready Apr 26 02:58:14 192.168.122.209 [39244.545375] [tdb] Close table 'client0.tdb' Apr 26 02:58:14 192.168.122.209 [39244.763991] [tdb] Close table 'sessions0.tdb' Apr 26 02:58:17 192.168.122.209 [39247.957248] [tdb] Close table 'cache0.tdb' Apr 26 02:58:17 192.168.122.209 [39248.190446] [tdb] Close table 'filter0.tdb' Apr 26 02:58:17 192.168.122.209 [39248.190888] [tempesta fw] modules are stopped Apr 26 02:58:18 192.168.122.209 [39248.362355] [tempesta fw] exiting... Apr 26 02:58:18 192.168.122.209 [39248.504433] [tdb] Shutdown Tempesta DB Apr 26 02:58:18 192.168.122.209 [39248.734965] End test: cache.test_purge.TestPurgeImmediate.test_purge_get_uncached Apr 26 02:58:18 192.168.122.209 [39248.747451] Start test: cache.test_purge.TestPurgeImmediate.test_purge_get_update Apr 26 02:58:19 192.168.122.209 [39249.905370] [tdb] Start Tempesta DB Apr 26 02:58:19 192.168.122.209 [39250.072038] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:58:21 192.168.122.209 [39251.810834] [tempesta fw] Configuration processing is completed. Apr 26 02:58:21 192.168.122.209 [39251.861016] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:58:21 192.168.122.209 [39252.269762] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:58:21 192.168.122.209 [39252.296686] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:58:22 192.168.122.209 [39252.324494] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:58:22 192.168.122.209 [39252.362761] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:58:22 192.168.122.209 [39252.402847] [tempesta fw] Tempesta FW is ready Apr 26 02:58:22 192.168.122.209 [39253.067448] [tdb] Close table 'client0.tdb' Apr 26 02:58:22 192.168.122.209 [39253.281596] [tdb] Close table 'sessions0.tdb' Apr 26 02:58:26 192.168.122.209 [39256.435208] [tdb] Close table 'cache0.tdb' Apr 26 02:58:26 192.168.122.209 [39256.683600] [tdb] Close table 'filter0.tdb' Apr 26 02:58:26 192.168.122.209 [39256.684018] [tempesta fw] modules are stopped Apr 26 02:58:26 192.168.122.209 [39256.854819] [tempesta fw] exiting... Apr 26 02:58:26 192.168.122.209 [39257.005208] [tdb] Shutdown Tempesta DB Apr 26 02:58:26 192.168.122.209 [39257.197356] End test: cache.test_purge.TestPurgeImmediate.test_purge_get_update Apr 26 02:58:26 192.168.122.209 [39257.212064] Start test: cache.test_purge.TestPurgeImmediate.test_purge_get_update_cc Apr 26 02:58:27 192.168.122.209 [39258.251321] [tdb] Start Tempesta DB Apr 26 02:58:28 192.168.122.209 [39258.393416] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:58:29 192.168.122.209 [39260.158942] [tempesta fw] Configuration processing is completed. Apr 26 02:58:29 192.168.122.209 [39260.215436] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:58:30 192.168.122.209 [39260.665393] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:58:30 192.168.122.209 [39260.694422] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:58:30 192.168.122.209 [39260.723707] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:58:30 192.168.122.209 [39260.766934] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:58:30 192.168.122.209 [39260.806902] [tempesta fw] Tempesta FW is ready Apr 26 02:58:31 192.168.122.209 [39261.502583] [tdb] Close table 'client0.tdb' Apr 26 02:58:31 192.168.122.209 [39261.704688] [tdb] Close table 'sessions0.tdb' Apr 26 02:58:34 192.168.122.209 [39264.832343] [tdb] Close table 'cache0.tdb' Apr 26 02:58:34 192.168.122.209 [39265.049921] [tdb] Close table 'filter0.tdb' Apr 26 02:58:34 192.168.122.209 [39265.050351] [tempesta fw] modules are stopped Apr 26 02:58:34 192.168.122.209 [39265.241266] [tempesta fw] exiting... Apr 26 02:58:35 192.168.122.209 [39265.383192] [tdb] Shutdown Tempesta DB Apr 26 02:58:35 192.168.122.209 [39265.605725] End test: cache.test_purge.TestPurgeImmediate.test_purge_get_update_cc Apr 26 02:58:35 192.168.122.209 [39265.625291] Start test: cache.test_purge.TestPurgeImmediate.test_purge_get_update_hdr_del Apr 26 02:58:36 192.168.122.209 [39266.818413] [tdb] Start Tempesta DB Apr 26 02:58:36 192.168.122.209 [39266.986106] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:58:38 192.168.122.209 [39268.863040] [tempesta fw] Configuration processing is completed. Apr 26 02:58:38 192.168.122.209 [39268.912508] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:58:39 192.168.122.209 [39269.329389] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:58:39 192.168.122.209 [39269.355624] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:58:39 192.168.122.209 [39269.382393] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:58:39 192.168.122.209 [39269.427038] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:58:39 192.168.122.209 [39269.466997] [tempesta fw] Tempesta FW is ready Apr 26 02:58:39 192.168.122.209 [39270.117632] [tdb] Close table 'client0.tdb' Apr 26 02:58:40 192.168.122.209 [39270.317530] [tdb] Close table 'sessions0.tdb' Apr 26 02:58:43 192.168.122.209 [39273.451914] [tdb] Close table 'cache0.tdb' Apr 26 02:58:43 192.168.122.209 [39273.689994] [tdb] Close table 'filter0.tdb' Apr 26 02:58:43 192.168.122.209 [39273.690440] [tempesta fw] modules are stopped Apr 26 02:58:43 192.168.122.209 [39273.846982] [tempesta fw] exiting... Apr 26 02:58:43 192.168.122.209 [39274.021271] [tdb] Shutdown Tempesta DB Apr 26 02:58:43 192.168.122.209 [39274.241896] End test: cache.test_purge.TestPurgeImmediate.test_purge_get_update_hdr_del Apr 26 02:58:43 192.168.122.209 [39274.258790] Start test: cache.test_purge.TestPurgeImmediate.test_useless_x_tempesta_cache Apr 26 02:58:45 192.168.122.209 [39275.484464] [tdb] Start Tempesta DB Apr 26 02:58:45 192.168.122.209 [39275.622056] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:58:47 192.168.122.209 [39277.411422] [tempesta fw] Configuration processing is completed. Apr 26 02:58:47 192.168.122.209 [39277.456594] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:58:47 192.168.122.209 [39277.860135] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:58:47 192.168.122.209 [39277.892634] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:58:47 192.168.122.209 [39277.918210] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:58:47 192.168.122.209 [39277.963152] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:58:47 192.168.122.209 [39277.999086] [tempesta fw] Tempesta FW is ready Apr 26 02:58:48 192.168.122.209 [39278.616999] [tdb] Close table 'client0.tdb' Apr 26 02:58:48 192.168.122.209 [39278.786636] [tdb] Close table 'sessions0.tdb' Apr 26 02:58:51 192.168.122.209 [39281.962654] [tdb] Close table 'cache0.tdb' Apr 26 02:58:51 192.168.122.209 [39282.215826] [tdb] Close table 'filter0.tdb' Apr 26 02:58:51 192.168.122.209 [39282.216272] [tempesta fw] modules are stopped Apr 26 02:58:52 192.168.122.209 [39282.431938] [tempesta fw] exiting... Apr 26 02:58:52 192.168.122.209 [39282.610466] [tdb] Shutdown Tempesta DB Apr 26 02:58:52 192.168.122.209 [39282.863261] End test: cache.test_purge.TestPurgeImmediate.test_useless_x_tempesta_cache Apr 26 02:58:52 192.168.122.209 [39282.892967] Start test: cache.test_purge.TestPurgeInvalidConfig.test_wrong_config_cache_0_purge Apr 26 02:58:53 192.168.122.209 [39284.096371] [tdb] Start Tempesta DB Apr 26 02:58:53 192.168.122.209 [39284.262254] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:58:55 192.168.122.209 [39286.115250] [tempesta fw] ERROR: syntax error Apr 26 02:58:55 192.168.122.209 [39286.116529] [tempesta fw] ERROR: configuration parsing error: [39286.116529] 22: cache_purge_acl 127.0.0.1 [39286.116529] ^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 02:58:55 192.168.122.209 [39286.120446] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 02:58:55 192.168.122.209 [39286.285178] [tempesta fw] exiting... Apr 26 02:58:56 192.168.122.209 [39286.414556] [tdb] Shutdown Tempesta DB Apr 26 02:58:56 192.168.122.209 [39286.899361] End test: cache.test_purge.TestPurgeInvalidConfig.test_wrong_config_cache_0_purge Apr 26 02:58:56 192.168.122.209 [39286.924770] Start test: cache.test_purge.TestPurgeInvalidConfig.test_wrong_config_cache_purge_acl_no_purge Apr 26 02:58:57 192.168.122.209 [39288.065181] [tdb] Start Tempesta DB Apr 26 02:58:57 192.168.122.209 [39288.233684] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:58:58 192.168.122.209 [39288.943756] [tempesta fw] ERROR: more than one value specified Apr 26 02:58:58 192.168.122.209 [39288.945466] [tempesta fw] ERROR: can't parse integer Apr 26 02:58:58 192.168.122.209 [39288.945475] [tempesta fw] ERROR: configuration parsing error: [39288.945475] 20: cache 2 [39288.945475] ^^^^^^^ Apr 26 02:58:58 192.168.122.209 [39288.950116] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 02:58:58 192.168.122.209 [39289.101500] [tempesta fw] exiting... Apr 26 02:58:58 192.168.122.209 [39289.219861] [tdb] Shutdown Tempesta DB Apr 26 02:58:59 192.168.122.209 [39289.664956] End test: cache.test_purge.TestPurgeInvalidConfig.test_wrong_config_cache_purge_acl_no_purge Apr 26 02:58:59 192.168.122.209 [39289.676297] Start test: cache.test_purge.TestPurgeInvalidConfig.test_wrong_config_cache_purge_no_purge_acl Apr 26 02:59:00 192.168.122.209 [39290.789468] [tdb] Start Tempesta DB Apr 26 02:59:00 192.168.122.209 [39290.948885] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:59:01 192.168.122.209 [39291.747835] [tempesta fw] ERROR: Directives mismatching: 'cache_purge' directive requires 'cache_purge_acl', but it wasn't provided. Apr 26 02:59:01 192.168.122.209 [39291.750877] [tempesta fw] ERROR: Unable to complete the configuration of module 'vhost': -22 Apr 26 02:59:01 192.168.122.209 [39291.753047] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 02:59:01 192.168.122.209 [39291.985142] [tempesta fw] exiting... Apr 26 02:59:01 192.168.122.209 [39292.110910] [tdb] Shutdown Tempesta DB Apr 26 02:59:02 192.168.122.209 [39292.570406] End test: cache.test_purge.TestPurgeInvalidConfig.test_wrong_config_cache_purge_no_purge_acl Apr 26 02:59:02 192.168.122.209 [39292.583316] Start test: cache.test_purge.TestPurgeInvalidConfig.test_wrong_config_purge_cache_0 Apr 26 02:59:03 192.168.122.209 [39293.601404] [tdb] Start Tempesta DB Apr 26 02:59:03 192.168.122.209 [39293.763651] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:59:04 192.168.122.209 [39294.551411] [tempesta fw] ERROR: Directives mismatching: 'cache_purge' directive requires 'cache' be not zero Apr 26 02:59:04 192.168.122.209 [39294.554179] [tempesta fw] ERROR: configuration parsing error: [39294.554179] 21: cache 0; [39294.554179] ^^^^^^^^ Apr 26 02:59:04 192.168.122.209 [39294.557267] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 02:59:04 192.168.122.209 [39294.718569] [tempesta fw] exiting... Apr 26 02:59:04 192.168.122.209 [39294.828029] [tdb] Shutdown Tempesta DB Apr 26 02:59:04 192.168.122.209 [39295.275984] End test: cache.test_purge.TestPurgeInvalidConfig.test_wrong_config_purge_cache_0 Apr 26 02:59:04 192.168.122.209 [39295.288107] Start test: cache.test_purge.TestPurgeInvalidConfig.test_wrong_config_purge_no_cache Apr 26 02:59:06 192.168.122.209 [39296.449813] [tdb] Start Tempesta DB Apr 26 02:59:06 192.168.122.209 [39296.605566] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:59:07 192.168.122.209 [39297.339392] [tempesta fw] ERROR: syntax error Apr 26 02:59:07 192.168.122.209 [39297.340697] [tempesta fw] ERROR: configuration parsing error: [39297.340697] 20: cache_purge;ncache_purge_acl 127.0.0.1 [39297.340697] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 02:59:07 192.168.122.209 [39297.345247] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 02:59:07 192.168.122.209 [39297.509158] [tempesta fw] exiting... Apr 26 02:59:07 192.168.122.209 [39297.620246] [tdb] Shutdown Tempesta DB Apr 26 02:59:07 192.168.122.209 [39298.030609] End test: cache.test_purge.TestPurgeInvalidConfig.test_wrong_config_purge_no_cache Apr 26 02:59:07 192.168.122.209 [39298.050070] Start test: cache.test_purge.TestPurgeInvalidate.test_purge Apr 26 02:59:08 192.168.122.209 [39299.172068] [tdb] Start Tempesta DB Apr 26 02:59:09 192.168.122.209 [39299.333345] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:59:09 192.168.122.209 [39300.211468] [tempesta fw] Configuration processing is completed. Apr 26 02:59:09 192.168.122.209 [39300.272647] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:59:10 192.168.122.209 [39300.777330] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:59:10 192.168.122.209 [39300.809807] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:59:10 192.168.122.209 [39300.842287] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:59:10 192.168.122.209 [39300.895462] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:59:10 192.168.122.209 [39300.935421] [tempesta fw] Tempesta FW is ready Apr 26 02:59:10 192.168.122.209 [39301.105782] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 02:59:11 192.168.122.209 [39301.559000] [tdb] Close table 'client0.tdb' Apr 26 02:59:11 192.168.122.209 [39301.745526] [tdb] Close table 'sessions0.tdb' Apr 26 02:59:14 192.168.122.209 [39304.897767] [tdb] Close table 'cache0.tdb' Apr 26 02:59:14 192.168.122.209 [39305.131644] [tdb] Close table 'filter0.tdb' Apr 26 02:59:14 192.168.122.209 [39305.132079] [tempesta fw] modules are stopped Apr 26 02:59:15 192.168.122.209 [39305.304682] [tempesta fw] exiting... Apr 26 02:59:15 192.168.122.209 [39305.468405] [tdb] Shutdown Tempesta DB Apr 26 02:59:15 192.168.122.209 [39305.704523] End test: cache.test_purge.TestPurgeInvalidate.test_purge Apr 26 02:59:15 192.168.122.209 [39305.737927] Start test: cache.test_purge.TestPurgeInvalidate.test_purge_get_basic Apr 26 02:59:16 192.168.122.209 [39306.940983] [tdb] Start Tempesta DB Apr 26 02:59:16 192.168.122.209 [39307.083513] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:59:18 192.168.122.209 [39308.915552] [tempesta fw] Configuration processing is completed. Apr 26 02:59:18 192.168.122.209 [39309.006090] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:59:19 192.168.122.209 [39309.419531] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:59:19 192.168.122.209 [39309.449510] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:59:19 192.168.122.209 [39309.480838] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:59:19 192.168.122.209 [39309.527485] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:59:19 192.168.122.209 [39309.571527] [tempesta fw] Tempesta FW is ready Apr 26 02:59:19 192.168.122.209 [39310.246660] [tdb] Close table 'client0.tdb' Apr 26 02:59:20 192.168.122.209 [39310.456385] [tdb] Close table 'sessions0.tdb' Apr 26 02:59:23 192.168.122.209 [39313.656410] [tdb] Close table 'cache0.tdb' Apr 26 02:59:23 192.168.122.209 [39313.900343] [tdb] Close table 'filter0.tdb' Apr 26 02:59:23 192.168.122.209 [39313.900790] [tempesta fw] modules are stopped Apr 26 02:59:23 192.168.122.209 [39314.102255] [tempesta fw] exiting... Apr 26 02:59:23 192.168.122.209 [39314.227804] [tdb] Shutdown Tempesta DB Apr 26 02:59:24 192.168.122.209 [39314.449301] End test: cache.test_purge.TestPurgeInvalidate.test_purge_get_basic Apr 26 02:59:24 192.168.122.209 [39314.460881] Start test: cache.test_purge.TestPurgeInvalidate.test_purge_get_garbage Apr 26 02:59:25 192.168.122.209 [39315.621214] [tdb] Start Tempesta DB Apr 26 02:59:25 192.168.122.209 [39315.744139] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:59:27 192.168.122.209 [39317.488087] [tempesta fw] Configuration processing is completed. Apr 26 02:59:27 192.168.122.209 [39317.541408] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:59:27 192.168.122.209 [39317.972079] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:59:27 192.168.122.209 [39318.000448] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:59:27 192.168.122.209 [39318.029123] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:59:27 192.168.122.209 [39318.067582] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:59:27 192.168.122.209 [39318.107613] [tempesta fw] Tempesta FW is ready Apr 26 02:59:27 192.168.122.209 [39318.289465] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 02:59:28 192.168.122.209 [39318.321508] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 02:59:28 192.168.122.209 [39318.826737] [tdb] Close table 'client0.tdb' Apr 26 02:59:28 192.168.122.209 [39319.021245] [tdb] Close table 'sessions0.tdb' Apr 26 02:59:31 192.168.122.209 [39322.211377] [tdb] Close table 'cache0.tdb' Apr 26 02:59:32 192.168.122.209 [39322.441749] [tdb] Close table 'filter0.tdb' Apr 26 02:59:32 192.168.122.209 [39322.442190] [tempesta fw] modules are stopped Apr 26 02:59:32 192.168.122.209 [39322.620624] [tempesta fw] exiting... Apr 26 02:59:32 192.168.122.209 [39322.743955] [tdb] Shutdown Tempesta DB Apr 26 02:59:32 192.168.122.209 [39322.956369] End test: cache.test_purge.TestPurgeInvalidate.test_purge_get_garbage Apr 26 02:59:32 192.168.122.209 [39322.971134] Start test: cache.test_purge.TestPurgeInvalidate.test_purge_get_uncacheable Apr 26 02:59:33 192.168.122.209 [39324.113370] [tdb] Start Tempesta DB Apr 26 02:59:33 192.168.122.209 [39324.264220] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:59:35 192.168.122.209 [39326.059755] [tempesta fw] Configuration processing is completed. Apr 26 02:59:35 192.168.122.209 [39326.112521] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:59:36 192.168.122.209 [39326.519002] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:59:36 192.168.122.209 [39326.544006] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:59:36 192.168.122.209 [39326.569335] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:59:36 192.168.122.209 [39326.639757] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:59:36 192.168.122.209 [39326.679715] [tempesta fw] Tempesta FW is ready Apr 26 02:59:37 192.168.122.209 [39327.335421] [tdb] Close table 'client0.tdb' Apr 26 02:59:37 192.168.122.209 [39327.557432] [tdb] Close table 'sessions0.tdb' Apr 26 02:59:40 192.168.122.209 [39330.796800] [tdb] Close table 'cache0.tdb' Apr 26 02:59:40 192.168.122.209 [39331.022702] [tdb] Close table 'filter0.tdb' Apr 26 02:59:40 192.168.122.209 [39331.023124] [tempesta fw] modules are stopped Apr 26 02:59:40 192.168.122.209 [39331.188279] [tempesta fw] exiting... Apr 26 02:59:41 192.168.122.209 [39331.345145] [tdb] Shutdown Tempesta DB Apr 26 02:59:41 192.168.122.209 [39331.546827] End test: cache.test_purge.TestPurgeInvalidate.test_purge_get_uncacheable Apr 26 02:59:41 192.168.122.209 [39331.565468] Start test: cache.test_purge.TestPurgeInvalidate.test_purge_get_uncached Apr 26 02:59:42 192.168.122.209 [39332.757116] [tdb] Start Tempesta DB Apr 26 02:59:42 192.168.122.209 [39332.914560] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:59:44 192.168.122.209 [39334.759851] [tempesta fw] Configuration processing is completed. Apr 26 02:59:44 192.168.122.209 [39334.808842] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:59:44 192.168.122.209 [39335.220980] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:59:44 192.168.122.209 [39335.246628] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:59:44 192.168.122.209 [39335.272809] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:59:45 192.168.122.209 [39335.315888] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:59:45 192.168.122.209 [39335.359803] [tempesta fw] Tempesta FW is ready Apr 26 02:59:45 192.168.122.209 [39336.007455] [tdb] Close table 'client0.tdb' Apr 26 02:59:45 192.168.122.209 [39336.210614] [tdb] Close table 'sessions0.tdb' Apr 26 02:59:49 192.168.122.209 [39339.375969] [tdb] Close table 'cache0.tdb' Apr 26 02:59:49 192.168.122.209 [39339.638685] [tdb] Close table 'filter0.tdb' Apr 26 02:59:49 192.168.122.209 [39339.639119] [tempesta fw] modules are stopped Apr 26 02:59:49 192.168.122.209 [39339.828617] [tempesta fw] exiting... Apr 26 02:59:49 192.168.122.209 [39339.995429] [tdb] Shutdown Tempesta DB Apr 26 02:59:49 192.168.122.209 [39340.238605] End test: cache.test_purge.TestPurgeInvalidate.test_purge_get_uncached Apr 26 02:59:49 192.168.122.209 [39340.265073] Start test: cache.test_purge.TestPurgeInvalidate.test_purge_get_update Apr 26 02:59:51 192.168.122.209 [39341.480871] [tdb] Start Tempesta DB Apr 26 02:59:51 192.168.122.209 [39341.625601] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 02:59:53 192.168.122.209 [39343.479950] [tempesta fw] Configuration processing is completed. Apr 26 02:59:53 192.168.122.209 [39343.531131] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 02:59:53 192.168.122.209 [39343.932263] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 02:59:53 192.168.122.209 [39343.957543] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 02:59:53 192.168.122.209 [39343.982449] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 02:59:53 192.168.122.209 [39344.059964] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 02:59:53 192.168.122.209 [39344.107967] [tempesta fw] Tempesta FW is ready Apr 26 02:59:54 192.168.122.209 [39344.760109] [tdb] Close table 'client0.tdb' Apr 26 02:59:54 192.168.122.209 [39344.942564] [tdb] Close table 'sessions0.tdb' Apr 26 02:59:57 192.168.122.209 [39348.112677] [tdb] Close table 'cache0.tdb' Apr 26 02:59:58 192.168.122.209 [39348.364821] [tdb] Close table 'filter0.tdb' Apr 26 02:59:58 192.168.122.209 [39348.365251] [tempesta fw] modules are stopped Apr 26 02:59:58 192.168.122.209 [39348.556995] [tempesta fw] exiting... Apr 26 02:59:58 192.168.122.209 [39348.704169] [tdb] Shutdown Tempesta DB Apr 26 02:59:58 192.168.122.209 [39348.932131] End test: cache.test_purge.TestPurgeInvalidate.test_purge_get_update Apr 26 02:59:58 192.168.122.209 [39348.952360] Start test: cache.test_purge.TestPurgeInvalidate.test_purge_get_update_cc Apr 26 02:59:59 192.168.122.209 [39350.187381] [tdb] Start Tempesta DB Apr 26 03:00:00 192.168.122.209 [39350.334647] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:00:01 192.168.122.209 [39352.204085] [tempesta fw] Configuration processing is completed. Apr 26 03:00:01 192.168.122.209 [39352.286895] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:00:02 192.168.122.209 [39352.712047] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:00:02 192.168.122.209 [39352.739301] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:00:02 192.168.122.209 [39352.767258] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:00:02 192.168.122.209 [39352.816079] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:00:02 192.168.122.209 [39352.856043] [tempesta fw] Tempesta FW is ready Apr 26 03:00:03 192.168.122.209 [39353.516805] [tdb] Close table 'client0.tdb' Apr 26 03:00:03 192.168.122.209 [39353.720791] [tdb] Close table 'sessions0.tdb' Apr 26 03:00:06 192.168.122.209 [39356.863242] [tdb] Close table 'cache0.tdb' Apr 26 03:00:06 192.168.122.209 [39357.095711] [tdb] Close table 'filter0.tdb' Apr 26 03:00:06 192.168.122.209 [39357.096261] [tempesta fw] modules are stopped Apr 26 03:00:06 192.168.122.209 [39357.268938] [tempesta fw] exiting... Apr 26 03:00:07 192.168.122.209 [39357.407194] [tdb] Shutdown Tempesta DB Apr 26 03:00:07 192.168.122.209 [39357.626616] End test: cache.test_purge.TestPurgeInvalidate.test_purge_get_update_cc Apr 26 03:00:07 192.168.122.209 [39357.645207] Start test: cache.test_purge.TestPurgeInvalidate.test_purge_get_update_hdr_del Apr 26 03:00:08 192.168.122.209 [39358.814604] [tdb] Start Tempesta DB Apr 26 03:00:08 192.168.122.209 [39358.979505] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:00:10 192.168.122.209 [39360.884170] [tempesta fw] Configuration processing is completed. Apr 26 03:00:10 192.168.122.209 [39360.933730] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:00:11 192.168.122.209 [39361.336017] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:00:11 192.168.122.209 [39361.361563] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:00:11 192.168.122.209 [39361.386614] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:00:11 192.168.122.209 [39361.432185] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:00:11 192.168.122.209 [39361.472134] [tempesta fw] Tempesta FW is ready Apr 26 03:00:11 192.168.122.209 [39362.148146] [tdb] Close table 'client0.tdb' Apr 26 03:00:12 192.168.122.209 [39362.348033] [tdb] Close table 'sessions0.tdb' Apr 26 03:00:15 192.168.122.209 [39365.499059] [tdb] Close table 'cache0.tdb' Apr 26 03:00:15 192.168.122.209 [39365.720292] [tdb] Close table 'filter0.tdb' Apr 26 03:00:15 192.168.122.209 [39365.720724] [tempesta fw] modules are stopped Apr 26 03:00:15 192.168.122.209 [39365.893510] [tempesta fw] exiting... Apr 26 03:00:15 192.168.122.209 [39366.020337] [tdb] Shutdown Tempesta DB Apr 26 03:00:15 192.168.122.209 [39366.235442] End test: cache.test_purge.TestPurgeInvalidate.test_purge_get_update_hdr_del Apr 26 03:00:15 192.168.122.209 [39366.252347] Start test: cache.test_purge.TestPurgeInvalidate.test_useless_x_tempesta_cache Apr 26 03:00:17 192.168.122.209 [39367.470174] [tdb] Start Tempesta DB Apr 26 03:00:17 192.168.122.209 [39367.620211] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:00:19 192.168.122.209 [39369.468377] [tempesta fw] Configuration processing is completed. Apr 26 03:00:19 192.168.122.209 [39369.518423] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:00:19 192.168.122.209 [39369.928334] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:00:19 192.168.122.209 [39369.953986] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:00:19 192.168.122.209 [39369.979250] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:00:19 192.168.122.209 [39370.024241] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:00:19 192.168.122.209 [39370.072243] [tempesta fw] Tempesta FW is ready Apr 26 03:00:20 192.168.122.209 [39370.699616] [tdb] Close table 'client0.tdb' Apr 26 03:00:20 192.168.122.209 [39370.882600] [tdb] Close table 'sessions0.tdb' Apr 26 03:00:23 192.168.122.209 [39374.034019] [tdb] Close table 'cache0.tdb' Apr 26 03:00:23 192.168.122.209 [39374.278341] [tdb] Close table 'filter0.tdb' Apr 26 03:00:23 192.168.122.209 [39374.278777] [tempesta fw] modules are stopped Apr 26 03:00:24 192.168.122.209 [39374.509801] [tempesta fw] exiting... Apr 26 03:00:24 192.168.122.209 [39374.648243] [tdb] Shutdown Tempesta DB Apr 26 03:00:24 192.168.122.209 [39374.886810] End test: cache.test_purge.TestPurgeInvalidate.test_useless_x_tempesta_cache Apr 26 03:00:24 192.168.122.209 [39374.907389] Start test: cache.test_purge_hch.HeavyChunkedPurgeTest.test_0_purge_non_hch Apr 26 03:00:25 192.168.122.209 [39376.115879] [tdb] Start Tempesta DB Apr 26 03:00:25 192.168.122.209 [39376.262615] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:00:27 192.168.122.209 [39377.696462] [tempesta fw] Configuration processing is completed. Apr 26 03:00:27 192.168.122.209 [39377.788991] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:00:27 192.168.122.209 [39378.200849] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:00:27 192.168.122.209 [39378.227650] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:00:27 192.168.122.209 [39378.254252] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:00:28 192.168.122.209 [39378.300397] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:00:28 192.168.122.209 [39378.344357] [tempesta fw] Tempesta FW is ready Apr 26 03:00:28 192.168.122.209 [39378.930177] [tdb] Close table 'client0.tdb' Apr 26 03:00:28 192.168.122.209 [39379.150683] [tdb] Close table 'sessions0.tdb' Apr 26 03:00:32 192.168.122.209 [39382.315692] [tdb] Close table 'cache0.tdb' Apr 26 03:00:32 192.168.122.209 [39382.557851] [tdb] Close table 'filter0.tdb' Apr 26 03:00:32 192.168.122.209 [39382.558285] [tempesta fw] modules are stopped Apr 26 03:00:32 192.168.122.209 [39382.771720] [tempesta fw] exiting... Apr 26 03:00:32 192.168.122.209 [39382.955694] [tdb] Shutdown Tempesta DB Apr 26 03:00:32 192.168.122.209 [39383.140459] End test: cache.test_purge_hch.HeavyChunkedPurgeTest.test_0_purge_non_hch Apr 26 03:00:32 192.168.122.209 [39383.179560] Start test: cache.test_purge_hch.HeavyChunkedPurgeTest.test_1_purge_hch Apr 26 03:00:34 192.168.122.209 [39384.402792] [tdb] Start Tempesta DB Apr 26 03:00:34 192.168.122.209 [39384.557917] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:00:35 192.168.122.209 [39386.012559] [tempesta fw] Configuration processing is completed. Apr 26 03:00:35 192.168.122.209 [39386.064535] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:00:36 192.168.122.209 [39386.485594] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:00:36 192.168.122.209 [39386.511978] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:00:36 192.168.122.209 [39386.537990] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:00:36 192.168.122.209 [39386.580515] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:00:36 192.168.122.209 [39386.620490] [tempesta fw] Tempesta FW is ready Apr 26 03:00:36 192.168.122.209 [39387.210363] [tdb] Close table 'client0.tdb' Apr 26 03:00:37 192.168.122.209 [39387.411633] [tdb] Close table 'sessions0.tdb' Apr 26 03:00:40 192.168.122.209 [39390.594894] [tdb] Close table 'cache0.tdb' Apr 26 03:00:40 192.168.122.209 [39390.835672] [tdb] Close table 'filter0.tdb' Apr 26 03:00:40 192.168.122.209 [39390.836092] [tempesta fw] modules are stopped Apr 26 03:00:40 192.168.122.209 [39391.035549] [tempesta fw] exiting... Apr 26 03:00:40 192.168.122.209 [39391.182802] [tdb] Shutdown Tempesta DB Apr 26 03:00:41 192.168.122.209 [39391.405745] End test: cache.test_purge_hch.HeavyChunkedPurgeTest.test_1_purge_hch Apr 26 03:00:41 192.168.122.209 [39391.424561] Start test: cache.test_purge_resp_hch.HeavyChunkedPurgeRespTest.test_0_purge_resp_non_hch Apr 26 03:00:42 192.168.122.209 [39392.654995] [tdb] Start Tempesta DB Apr 26 03:00:42 192.168.122.209 [39392.808776] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:00:44 192.168.122.209 [39394.304653] [tempesta fw] Configuration processing is completed. Apr 26 03:00:44 192.168.122.209 [39394.357544] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:00:44 192.168.122.209 [39394.791454] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:00:44 192.168.122.209 [39394.817462] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:00:44 192.168.122.209 [39394.843817] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:00:44 192.168.122.209 [39394.896662] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:00:44 192.168.122.209 [39394.940562] [tempesta fw] Tempesta FW is ready Apr 26 03:00:45 192.168.122.209 [39395.570626] [tdb] Close table 'client0.tdb' Apr 26 03:00:45 192.168.122.209 [39395.767581] [tdb] Close table 'sessions0.tdb' Apr 26 03:00:48 192.168.122.209 [39398.957934] [tdb] Close table 'cache0.tdb' Apr 26 03:00:48 192.168.122.209 [39399.219910] [tdb] Close table 'filter0.tdb' Apr 26 03:00:48 192.168.122.209 [39399.220371] [tempesta fw] modules are stopped Apr 26 03:00:49 192.168.122.209 [39399.426823] [tempesta fw] exiting... Apr 26 03:00:49 192.168.122.209 [39399.609687] [tdb] Shutdown Tempesta DB Apr 26 03:00:49 192.168.122.209 [39399.874433] End test: cache.test_purge_resp_hch.HeavyChunkedPurgeRespTest.test_0_purge_resp_non_hch Apr 26 03:00:49 192.168.122.209 [39399.893354] Start test: encoding.test_encoding.TestH1BothTEAndCE.test Apr 26 03:00:50 192.168.122.209 [39401.071564] [tdb] Start Tempesta DB Apr 26 03:00:50 192.168.122.209 [39401.223611] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:00:52 192.168.122.209 [39402.381046] [tempesta fw] Configuration processing is completed. Apr 26 03:00:52 192.168.122.209 [39402.430586] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:00:52 192.168.122.209 [39402.846122] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:00:52 192.168.122.209 [39402.872441] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:00:52 192.168.122.209 [39402.899285] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:00:52 192.168.122.209 [39402.944710] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:00:52 192.168.122.209 [39402.984676] [tempesta fw] Tempesta FW is ready Apr 26 03:00:52 192.168.122.209 [39403.123188] [tempesta fw] Warning: Content-Encoding and Transfer-Encoding other than chunked not allowed to be in same response. Apr 26 03:00:52 192.168.122.209 [39403.124473] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 03:00:53 192.168.122.209 [39403.592651] [tdb] Close table 'client0.tdb' Apr 26 03:00:53 192.168.122.209 [39403.809638] [tdb] Close table 'sessions0.tdb' Apr 26 03:00:56 192.168.122.209 [39407.033606] [tdb] Close table 'cache0.tdb' Apr 26 03:00:56 192.168.122.209 [39407.271715] [tdb] Close table 'filter0.tdb' Apr 26 03:00:56 192.168.122.209 [39407.272181] [tempesta fw] modules are stopped Apr 26 03:00:57 192.168.122.209 [39407.482101] [tempesta fw] exiting... Apr 26 03:00:57 192.168.122.209 [39407.629485] [tdb] Shutdown Tempesta DB Apr 26 03:00:57 192.168.122.209 [39407.876244] End test: encoding.test_encoding.TestH1BothTEAndCE.test Apr 26 03:00:57 192.168.122.209 [39407.896090] Start test: encoding.test_encoding.TestH1ChunkedNonCacheable.test Apr 26 03:00:58 192.168.122.209 [39409.117995] [tdb] Start Tempesta DB Apr 26 03:00:58 192.168.122.209 [39409.265547] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:01:00 192.168.122.209 [39410.448776] [tempesta fw] Configuration processing is completed. Apr 26 03:01:00 192.168.122.209 [39410.518464] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:01:00 192.168.122.209 [39410.546457] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:01:00 192.168.122.209 [39410.575255] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:01:00 192.168.122.209 [39410.616809] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:01:00 192.168.122.209 [39410.660751] [tempesta fw] Tempesta FW is ready Apr 26 03:01:00 192.168.122.209 [39411.285809] [tdb] Close table 'client0.tdb' Apr 26 03:01:01 192.168.122.209 [39411.485076] [tdb] Close table 'sessions0.tdb' Apr 26 03:01:01 192.168.122.209 [39411.740299] [tdb] Close table 'filter0.tdb' Apr 26 03:01:01 192.168.122.209 [39411.740756] [tempesta fw] modules are stopped Apr 26 03:01:01 192.168.122.209 [39411.903764] [tempesta fw] exiting... Apr 26 03:01:01 192.168.122.209 [39412.039394] [tdb] Shutdown Tempesta DB Apr 26 03:01:01 192.168.122.209 [39412.256554] End test: encoding.test_encoding.TestH1ChunkedNonCacheable.test Apr 26 03:01:01 192.168.122.209 [39412.281636] Start test: encoding.test_encoding.TestH1ChunkedWithLongBodyAndTrailer.test Apr 26 03:01:03 192.168.122.209 [39413.475331] [tdb] Start Tempesta DB Apr 26 03:01:03 192.168.122.209 [39413.657529] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:01:03 192.168.122.209 [39414.282157] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39414.282157] Maybe that's fine, but it's worth checking the [39414.282157] config - if there is no relations between the [39414.282157] names, then host name confusion attack is possible. Apr 26 03:01:04 192.168.122.209 [39414.372872] [tempesta fw] Configuration processing is completed. Apr 26 03:01:04 192.168.122.209 [39414.423255] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:01:04 192.168.122.209 [39414.840556] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:01:04 192.168.122.209 [39414.900709] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:01:04 192.168.122.209 [39414.926917] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:01:04 192.168.122.209 [39414.976879] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:01:04 192.168.122.209 [39414.978639] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:01:04 192.168.122.209 [39415.020812] [tempesta fw] Tempesta FW is ready Apr 26 03:01:05 192.168.122.209 [39415.679661] [tdb] Close table 'client0.tdb' Apr 26 03:01:05 192.168.122.209 [39415.864033] [tdb] Close table 'sessions0.tdb' Apr 26 03:01:08 192.168.122.209 [39419.006416] [tdb] Close table 'cache0.tdb' Apr 26 03:01:08 192.168.122.209 [39419.255405] [tdb] Close table 'filter0.tdb' Apr 26 03:01:08 192.168.122.209 [39419.255839] [tempesta fw] modules are stopped Apr 26 03:01:09 192.168.122.209 [39419.512126] [tempesta fw] exiting... Apr 26 03:01:09 192.168.122.209 [39419.668334] [tdb] Shutdown Tempesta DB Apr 26 03:01:09 192.168.122.209 [39419.892697] End test: encoding.test_encoding.TestH1ChunkedWithLongBodyAndTrailer.test Apr 26 03:01:09 192.168.122.209 [39419.917230] Start test: encoding.test_encoding.TestH1ChunkedWithTrailer.test Apr 26 03:01:10 192.168.122.209 [39421.124090] [tdb] Start Tempesta DB Apr 26 03:01:10 192.168.122.209 [39421.272530] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:01:12 192.168.122.209 [39422.670241] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39422.670241] Maybe that's fine, but it's worth checking the [39422.670241] config - if there is no relations between the [39422.670241] names, then host name confusion attack is possible. Apr 26 03:01:12 192.168.122.209 [39422.768995] [tempesta fw] Configuration processing is completed. Apr 26 03:01:12 192.168.122.209 [39422.819055] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:01:12 192.168.122.209 [39423.246806] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:01:12 192.168.122.209 [39423.272400] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:01:12 192.168.122.209 [39423.297787] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:01:13 192.168.122.209 [39423.344974] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:01:13 192.168.122.209 [39423.346737] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:01:13 192.168.122.209 [39423.388923] [tempesta fw] Tempesta FW is ready Apr 26 03:01:13 192.168.122.209 [39423.993491] [tdb] Close table 'client0.tdb' Apr 26 03:01:13 192.168.122.209 [39424.189663] [tdb] Close table 'sessions0.tdb' Apr 26 03:01:17 192.168.122.209 [39427.356601] [tdb] Close table 'cache0.tdb' Apr 26 03:01:17 192.168.122.209 [39427.603509] [tdb] Close table 'filter0.tdb' Apr 26 03:01:17 192.168.122.209 [39427.603937] [tempesta fw] modules are stopped Apr 26 03:01:17 192.168.122.209 [39427.812501] [tempesta fw] exiting... Apr 26 03:01:17 192.168.122.209 [39427.950776] [tdb] Shutdown Tempesta DB Apr 26 03:01:17 192.168.122.209 [39428.171029] End test: encoding.test_encoding.TestH1ChunkedWithTrailer.test Apr 26 03:01:17 192.168.122.209 [39428.198044] Start test: encoding.test_encoding.TestH2BodyDechunking.test Apr 26 03:01:19 192.168.122.209 [39429.405130] [tdb] Start Tempesta DB Apr 26 03:01:19 192.168.122.209 [39429.549771] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:01:20 192.168.122.209 [39430.946356] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39430.946356] Maybe that's fine, but it's worth checking the [39430.946356] config - if there is no relations between the [39430.946356] names, then host name confusion attack is possible. Apr 26 03:01:20 192.168.122.209 [39431.033082] [tempesta fw] Configuration processing is completed. Apr 26 03:01:20 192.168.122.209 [39431.085388] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:01:21 192.168.122.209 [39431.502926] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:01:21 192.168.122.209 [39431.528923] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:01:21 192.168.122.209 [39431.554991] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:01:21 192.168.122.209 [39431.633133] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:01:21 192.168.122.209 [39431.677018] [tempesta fw] Tempesta FW is ready Apr 26 03:01:21 192.168.122.209 [39432.296056] [tdb] Close table 'client0.tdb' Apr 26 03:01:22 192.168.122.209 [39432.502365] [tdb] Close table 'sessions0.tdb' Apr 26 03:01:25 192.168.122.209 [39435.718852] [tdb] Close table 'cache0.tdb' Apr 26 03:01:25 192.168.122.209 [39435.941619] [tdb] Close table 'filter0.tdb' Apr 26 03:01:25 192.168.122.209 [39435.942074] [tempesta fw] modules are stopped Apr 26 03:01:25 192.168.122.209 [39436.143329] [tempesta fw] exiting... Apr 26 03:01:26 192.168.122.209 [39436.316412] [tdb] Shutdown Tempesta DB Apr 26 03:01:26 192.168.122.209 [39436.580441] End test: encoding.test_encoding.TestH2BodyDechunking.test Apr 26 03:01:26 192.168.122.209 [39436.595507] Start test: encoding.test_encoding.TestH2ChunkedExtensionRemoved.test Apr 26 03:01:27 192.168.122.209 [39437.651524] [tdb] Start Tempesta DB Apr 26 03:01:27 192.168.122.209 [39437.793072] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:01:28 192.168.122.209 [39439.022606] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39439.022606] Maybe that's fine, but it's worth checking the [39439.022606] config - if there is no relations between the [39439.022606] names, then host name confusion attack is possible. Apr 26 03:01:28 192.168.122.209 [39439.109232] [tempesta fw] Configuration processing is completed. Apr 26 03:01:28 192.168.122.209 [39439.195201] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:01:29 192.168.122.209 [39439.620832] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:01:29 192.168.122.209 [39439.648158] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:01:29 192.168.122.209 [39439.677532] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:01:29 192.168.122.209 [39439.717173] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:01:29 192.168.122.209 [39439.757049] [tempesta fw] Tempesta FW is ready Apr 26 03:01:30 192.168.122.209 [39440.465438] [tdb] Close table 'client0.tdb' Apr 26 03:01:30 192.168.122.209 [39440.712088] [tdb] Close table 'sessions0.tdb' Apr 26 03:01:33 192.168.122.209 [39443.882042] [tdb] Close table 'cache0.tdb' Apr 26 03:01:33 192.168.122.209 [39444.130114] [tdb] Close table 'filter0.tdb' Apr 26 03:01:33 192.168.122.209 [39444.130542] [tempesta fw] modules are stopped Apr 26 03:01:34 192.168.122.209 [39444.332221] [tempesta fw] exiting... Apr 26 03:01:34 192.168.122.209 [39444.476792] [tdb] Shutdown Tempesta DB Apr 26 03:01:34 192.168.122.209 [39444.720973] End test: encoding.test_encoding.TestH2ChunkedExtensionRemoved.test Apr 26 03:01:34 192.168.122.209 [39444.742802] Start test: encoding.test_encoding.TestH2ChunkedIsNotLast.test Apr 26 03:01:35 192.168.122.209 [39445.903349] [tdb] Start Tempesta DB Apr 26 03:01:35 192.168.122.209 [39446.037769] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:01:37 192.168.122.209 [39447.379776] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39447.379776] Maybe that's fine, but it's worth checking the [39447.379776] config - if there is no relations between the [39447.379776] names, then host name confusion attack is possible. Apr 26 03:01:37 192.168.122.209 [39447.461292] [tempesta fw] Configuration processing is completed. Apr 26 03:01:37 192.168.122.209 [39447.509870] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:01:37 192.168.122.209 [39447.927745] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:01:37 192.168.122.209 [39447.953975] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:01:37 192.168.122.209 [39447.979736] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:01:37 192.168.122.209 [39448.029277] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:01:37 192.168.122.209 [39448.073255] [tempesta fw] Tempesta FW is ready Apr 26 03:01:37 192.168.122.209 [39448.219236] [tempesta fw] Warning: Parser error: state=Resp_HdrTransfer_EncodingV input(-8)=0x63('coding: chunked, gzip [39448.219236] [39448.219236] 3 [39448.219236] 123 [39448.219236] 0 [39448.219236] [39448.219236] ') data_len=198 off=168 Apr 26 03:01:37 192.168.122.209 [39448.221988] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 03:01:38 192.168.122.209 [39448.681823] [tdb] Close table 'client0.tdb' Apr 26 03:01:38 192.168.122.209 [39448.877911] [tdb] Close table 'sessions0.tdb' Apr 26 03:01:41 192.168.122.209 [39452.069912] [tdb] Close table 'cache0.tdb' Apr 26 03:01:41 192.168.122.209 [39452.294500] [tdb] Close table 'filter0.tdb' Apr 26 03:01:41 192.168.122.209 [39452.294931] [tempesta fw] modules are stopped Apr 26 03:01:42 192.168.122.209 [39452.494561] [tempesta fw] exiting... Apr 26 03:01:42 192.168.122.209 [39452.650445] [tdb] Shutdown Tempesta DB Apr 26 03:01:42 192.168.122.209 [39452.833818] End test: encoding.test_encoding.TestH2ChunkedIsNotLast.test Apr 26 03:01:42 192.168.122.209 [39452.844563] Start test: encoding.test_encoding.TestH2ChunkedWithLongBodyAndTrailer.test Apr 26 03:01:43 192.168.122.209 [39453.979341] [tdb] Start Tempesta DB Apr 26 03:01:43 192.168.122.209 [39454.122702] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:01:45 192.168.122.209 [39455.486672] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39455.486672] Maybe that's fine, but it's worth checking the [39455.486672] config - if there is no relations between the [39455.486672] names, then host name confusion attack is possible. Apr 26 03:01:45 192.168.122.209 [39455.577409] [tempesta fw] Configuration processing is completed. Apr 26 03:01:45 192.168.122.209 [39455.627836] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:01:45 192.168.122.209 [39456.078947] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:01:45 192.168.122.209 [39456.105743] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:01:45 192.168.122.209 [39456.132274] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:01:45 192.168.122.209 [39456.177409] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:01:45 192.168.122.209 [39456.179162] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:01:45 192.168.122.209 [39456.217340] [tempesta fw] Tempesta FW is ready Apr 26 03:01:47 192.168.122.209 [39457.444595] [tdb] Close table 'client0.tdb' Apr 26 03:01:47 192.168.122.209 [39457.647339] [tdb] Close table 'sessions0.tdb' Apr 26 03:01:50 192.168.122.209 [39460.770483] [tdb] Close table 'cache0.tdb' Apr 26 03:01:50 192.168.122.209 [39461.016253] [tdb] Close table 'filter0.tdb' Apr 26 03:01:50 192.168.122.209 [39461.016679] [tempesta fw] modules are stopped Apr 26 03:01:50 192.168.122.209 [39461.199200] [tempesta fw] exiting... Apr 26 03:01:51 192.168.122.209 [39461.332848] [tdb] Shutdown Tempesta DB Apr 26 03:01:51 192.168.122.209 [39461.567280] End test: encoding.test_encoding.TestH2ChunkedWithLongBodyAndTrailer.test Apr 26 03:01:51 192.168.122.209 [39461.581223] Start test: encoding.test_encoding.TestH2ChunkedWithTrailer.test Apr 26 03:01:52 192.168.122.209 [39462.770066] [tdb] Start Tempesta DB Apr 26 03:01:52 192.168.122.209 [39462.912676] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:01:54 192.168.122.209 [39464.322782] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39464.322782] Maybe that's fine, but it's worth checking the [39464.322782] config - if there is no relations between the [39464.322782] names, then host name confusion attack is possible. Apr 26 03:01:54 192.168.122.209 [39464.413462] [tempesta fw] Configuration processing is completed. Apr 26 03:01:54 192.168.122.209 [39464.462821] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:01:54 192.168.122.209 [39464.872052] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:01:54 192.168.122.209 [39464.905799] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:01:54 192.168.122.209 [39464.932034] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:01:54 192.168.122.209 [39464.985516] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:01:54 192.168.122.209 [39464.987242] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:01:54 192.168.122.209 [39465.033387] [tempesta fw] Tempesta FW is ready Apr 26 03:01:55 192.168.122.209 [39465.587393] [tdb] Close table 'client0.tdb' Apr 26 03:01:55 192.168.122.209 [39465.831033] [tdb] Close table 'sessions0.tdb' Apr 26 03:01:58 192.168.122.209 [39468.928810] [tdb] Close table 'cache0.tdb' Apr 26 03:01:58 192.168.122.209 [39469.149999] [tdb] Close table 'filter0.tdb' Apr 26 03:01:58 192.168.122.209 [39469.150439] [tempesta fw] modules are stopped Apr 26 03:01:59 192.168.122.209 [39469.320158] [tempesta fw] exiting... Apr 26 03:01:59 192.168.122.209 [39469.457957] [tdb] Shutdown Tempesta DB Apr 26 03:01:59 192.168.122.209 [39469.689969] End test: encoding.test_encoding.TestH2ChunkedWithTrailer.test Apr 26 03:01:59 192.168.122.209 [39469.709710] Start test: encoding.test_encoding.TestH2EmptyResponseBodyDechunking.test Apr 26 03:02:00 192.168.122.209 [39470.885152] [tdb] Start Tempesta DB Apr 26 03:02:00 192.168.122.209 [39471.048387] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:02:02 192.168.122.209 [39472.406817] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39472.406817] Maybe that's fine, but it's worth checking the [39472.406817] config - if there is no relations between the [39472.406817] names, then host name confusion attack is possible. Apr 26 03:02:02 192.168.122.209 [39472.493627] [tempesta fw] Configuration processing is completed. Apr 26 03:02:02 192.168.122.209 [39472.544113] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:02:02 192.168.122.209 [39472.964845] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:02:02 192.168.122.209 [39472.991642] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:02:02 192.168.122.209 [39473.018944] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:02:02 192.168.122.209 [39473.073612] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:02:02 192.168.122.209 [39473.113586] [tempesta fw] Tempesta FW is ready Apr 26 03:02:03 192.168.122.209 [39473.718709] [tdb] Close table 'client0.tdb' Apr 26 03:02:03 192.168.122.209 [39473.909178] [tdb] Close table 'sessions0.tdb' Apr 26 03:02:06 192.168.122.209 [39477.099738] [tdb] Close table 'cache0.tdb' Apr 26 03:02:07 192.168.122.209 [39477.334001] [tdb] Close table 'filter0.tdb' Apr 26 03:02:07 192.168.122.209 [39477.334439] [tempesta fw] modules are stopped Apr 26 03:02:07 192.168.122.209 [39477.524722] [tempesta fw] exiting... Apr 26 03:02:07 192.168.122.209 [39477.677163] [tdb] Shutdown Tempesta DB Apr 26 03:02:07 192.168.122.209 [39477.881281] End test: encoding.test_encoding.TestH2EmptyResponseBodyDechunking.test Apr 26 03:02:07 192.168.122.209 [39477.894866] Start test: encoding.test_encoding.TestH2EmptyResponseBodyDechunkingHead.test Apr 26 03:02:08 192.168.122.209 [39479.047242] [tdb] Start Tempesta DB Apr 26 03:02:08 192.168.122.209 [39479.194457] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:02:10 192.168.122.209 [39480.554940] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39480.554940] Maybe that's fine, but it's worth checking the [39480.554940] config - if there is no relations between the [39480.554940] names, then host name confusion attack is possible. Apr 26 03:02:10 192.168.122.209 [39480.645726] [tempesta fw] Configuration processing is completed. Apr 26 03:02:10 192.168.122.209 [39480.705701] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:02:10 192.168.122.209 [39481.140759] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:02:10 192.168.122.209 [39481.166986] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:02:10 192.168.122.209 [39481.193574] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:02:10 192.168.122.209 [39481.233720] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:02:10 192.168.122.209 [39481.281586] [tempesta fw] Tempesta FW is ready Apr 26 03:02:11 192.168.122.209 [39481.883305] [tdb] Close table 'client0.tdb' Apr 26 03:02:11 192.168.122.209 [39482.079548] [tdb] Close table 'sessions0.tdb' Apr 26 03:02:14 192.168.122.209 [39485.212507] [tdb] Close table 'cache0.tdb' Apr 26 03:02:15 192.168.122.209 [39485.448285] [tdb] Close table 'filter0.tdb' Apr 26 03:02:15 192.168.122.209 [39485.448737] [tempesta fw] modules are stopped Apr 26 03:02:15 192.168.122.209 [39485.638616] [tempesta fw] exiting... Apr 26 03:02:15 192.168.122.209 [39485.794218] [tdb] Shutdown Tempesta DB Apr 26 03:02:15 192.168.122.209 [39486.017023] End test: encoding.test_encoding.TestH2EmptyResponseBodyDechunkingHead.test Apr 26 03:02:15 192.168.122.209 [39486.030335] Start test: encoding.test_encoding.TestH2LargeResponseBodyDechunking.test Apr 26 03:02:16 192.168.122.209 [39487.134906] [tdb] Start Tempesta DB Apr 26 03:02:16 192.168.122.209 [39487.288349] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:02:18 192.168.122.209 [39488.603098] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39488.603098] Maybe that's fine, but it's worth checking the [39488.603098] config - if there is no relations between the [39488.603098] names, then host name confusion attack is possible. Apr 26 03:02:18 192.168.122.209 [39488.697826] [tempesta fw] Configuration processing is completed. Apr 26 03:02:18 192.168.122.209 [39488.757211] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:02:18 192.168.122.209 [39489.171638] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:02:18 192.168.122.209 [39489.196831] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:02:18 192.168.122.209 [39489.222261] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:02:18 192.168.122.209 [39489.273828] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:02:19 192.168.122.209 [39489.321780] [tempesta fw] Tempesta FW is ready Apr 26 03:02:19 192.168.122.209 [39489.955889] [tdb] Close table 'client0.tdb' Apr 26 03:02:19 192.168.122.209 [39490.137209] [tdb] Close table 'sessions0.tdb' Apr 26 03:02:23 192.168.122.209 [39493.739631] [tdb] Close table 'cache0.tdb' Apr 26 03:02:24 192.168.122.209 [39494.332804] [tdb] Close table 'filter0.tdb' Apr 26 03:02:24 192.168.122.209 [39494.333243] [tempesta fw] modules are stopped Apr 26 03:02:26 192.168.122.209 [39496.382575] [tempesta fw] exiting... Apr 26 03:02:26 192.168.122.209 [39497.232662] [tdb] Shutdown Tempesta DB Apr 26 03:02:27 192.168.122.209 [39497.976797] End test: encoding.test_encoding.TestH2LargeResponseBodyDechunking.test Apr 26 03:02:27 192.168.122.209 [39497.988663] Start test: encoding.test_encoding.TestH2LargeResponseBodyDechunking2.test Apr 26 03:02:28 192.168.122.209 [39499.126628] [tdb] Start Tempesta DB Apr 26 03:02:28 192.168.122.209 [39499.278344] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:02:30 192.168.122.209 [39500.611195] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39500.611195] Maybe that's fine, but it's worth checking the [39500.611195] config - if there is no relations between the [39500.611195] names, then host name confusion attack is possible. Apr 26 03:02:30 192.168.122.209 [39500.697958] [tempesta fw] Configuration processing is completed. Apr 26 03:02:30 192.168.122.209 [39500.747341] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:02:30 192.168.122.209 [39501.165447] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:02:30 192.168.122.209 [39501.198964] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:02:30 192.168.122.209 [39501.224698] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:02:30 192.168.122.209 [39501.289949] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:02:31 192.168.122.209 [39501.341942] [tempesta fw] Tempesta FW is ready Apr 26 03:02:32 192.168.122.209 [39503.063759] [tdb] Close table 'client0.tdb' Apr 26 03:02:32 192.168.122.209 [39503.243502] [tdb] Close table 'sessions0.tdb' Apr 26 03:02:36 192.168.122.209 [39506.345541] [tdb] Close table 'cache0.tdb' Apr 26 03:02:36 192.168.122.209 [39506.583840] [tdb] Close table 'filter0.tdb' Apr 26 03:02:36 192.168.122.209 [39506.584262] [tempesta fw] modules are stopped Apr 26 03:02:36 192.168.122.209 [39506.821593] [tempesta fw] exiting... Apr 26 03:02:36 192.168.122.209 [39506.950149] [tdb] Shutdown Tempesta DB Apr 26 03:02:36 192.168.122.209 [39507.161392] End test: encoding.test_encoding.TestH2LargeResponseBodyDechunking2.test Apr 26 03:02:36 192.168.122.209 [39507.178530] Start test: encoding.test_encoding.TestH2TEMovedToCE.test Apr 26 03:02:38 192.168.122.209 [39508.311082] [tdb] Start Tempesta DB Apr 26 03:02:38 192.168.122.209 [39508.466652] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:02:39 192.168.122.209 [39509.743357] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39509.743357] Maybe that's fine, but it's worth checking the [39509.743357] config - if there is no relations between the [39509.743357] names, then host name confusion attack is possible. Apr 26 03:02:39 192.168.122.209 [39509.834080] [tempesta fw] Configuration processing is completed. Apr 26 03:02:39 192.168.122.209 [39509.884588] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:02:39 192.168.122.209 [39510.289926] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:02:40 192.168.122.209 [39510.315657] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:02:40 192.168.122.209 [39510.341774] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:02:40 192.168.122.209 [39510.398050] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:02:40 192.168.122.209 [39510.446029] [tempesta fw] Tempesta FW is ready Apr 26 03:02:40 192.168.122.209 [39511.015987] [tdb] Close table 'client0.tdb' Apr 26 03:02:40 192.168.122.209 [39511.231956] [tdb] Close table 'sessions0.tdb' Apr 26 03:02:44 192.168.122.209 [39514.371153] [tdb] Close table 'cache0.tdb' Apr 26 03:02:44 192.168.122.209 [39514.594262] [tdb] Close table 'filter0.tdb' Apr 26 03:02:44 192.168.122.209 [39514.594707] [tempesta fw] modules are stopped Apr 26 03:02:44 192.168.122.209 [39514.809743] [tempesta fw] exiting... Apr 26 03:02:44 192.168.122.209 [39514.966448] [tdb] Shutdown Tempesta DB Apr 26 03:02:44 192.168.122.209 [39515.177154] End test: encoding.test_encoding.TestH2TEMovedToCE.test Apr 26 03:02:44 192.168.122.209 [39515.198411] Start test: encoding.test_encoding.TestRequestChunkedNotLast.test Apr 26 03:02:46 192.168.122.209 [39516.348289] [tdb] Start Tempesta DB Apr 26 03:02:46 192.168.122.209 [39516.498141] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:02:47 192.168.122.209 [39517.602229] [tempesta fw] Configuration processing is completed. Apr 26 03:02:47 192.168.122.209 [39517.651531] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:02:47 192.168.122.209 [39518.093705] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:02:47 192.168.122.209 [39518.121027] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:02:47 192.168.122.209 [39518.148440] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:02:47 192.168.122.209 [39518.190163] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:02:47 192.168.122.209 [39518.230115] [tempesta fw] Tempesta FW is ready Apr 26 03:02:48 192.168.122.209 [39518.392268] [tempesta fw] Warning: Parser error: state=Req_HdrTransfer_EncodingV input(-8)=0x63('coding: chunked, gzip [39518.392268] [39518.392268] the body does not actua') data_len=102 off=52 Apr 26 03:02:48 192.168.122.209 [39518.841182] [tdb] Close table 'client0.tdb' Apr 26 03:02:48 192.168.122.209 [39519.035429] [tdb] Close table 'sessions0.tdb' Apr 26 03:02:51 192.168.122.209 [39522.271775] [tdb] Close table 'cache0.tdb' Apr 26 03:02:52 192.168.122.209 [39522.518414] [tdb] Close table 'filter0.tdb' Apr 26 03:02:52 192.168.122.209 [39522.518848] [tempesta fw] modules are stopped Apr 26 03:02:52 192.168.122.209 [39522.702762] [tempesta fw] exiting... Apr 26 03:02:52 192.168.122.209 [39522.861330] [tdb] Shutdown Tempesta DB Apr 26 03:02:52 192.168.122.209 [39523.066895] End test: encoding.test_encoding.TestRequestChunkedNotLast.test Apr 26 03:02:52 192.168.122.209 [39523.077438] Start test: encoding.test_encoding.TestRequestTEAndCL.test Apr 26 03:02:53 192.168.122.209 [39524.297151] [tdb] Start Tempesta DB Apr 26 03:02:54 192.168.122.209 [39524.445162] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:02:55 192.168.122.209 [39525.510356] [tempesta fw] Configuration processing is completed. Apr 26 03:02:55 192.168.122.209 [39525.560818] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:02:55 192.168.122.209 [39525.996231] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:02:55 192.168.122.209 [39526.024216] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:02:55 192.168.122.209 [39526.052139] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:02:55 192.168.122.209 [39526.090274] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:02:55 192.168.122.209 [39526.130222] [tempesta fw] Tempesta FW is ready Apr 26 03:02:55 192.168.122.209 [39526.269504] [tempesta fw] Warning: Transfer-Encoding chunked and Content-Length in same request considered as attempt to Request smuggling attack. Apr 26 03:02:56 192.168.122.209 [39526.733902] [tdb] Close table 'client0.tdb' Apr 26 03:02:56 192.168.122.209 [39526.933677] [tdb] Close table 'sessions0.tdb' Apr 26 03:02:59 192.168.122.209 [39530.065364] [tdb] Close table 'cache0.tdb' Apr 26 03:02:59 192.168.122.209 [39530.288897] [tdb] Close table 'filter0.tdb' Apr 26 03:02:59 192.168.122.209 [39530.289358] [tempesta fw] modules are stopped Apr 26 03:03:00 192.168.122.209 [39530.464216] [tempesta fw] exiting... Apr 26 03:03:00 192.168.122.209 [39530.636451] [tdb] Shutdown Tempesta DB Apr 26 03:03:00 192.168.122.209 [39530.864274] End test: encoding.test_encoding.TestRequestTEAndCL.test Apr 26 03:03:00 192.168.122.209 [39530.880500] Start test: forwarding.test_forwarded_hdr.TestForwardedBase.test_run Apr 26 03:03:00 192.168.122.209 [39530.892268] End test: forwarding.test_forwarded_hdr.TestForwardedBase.test_run Apr 26 03:03:00 192.168.122.209 [39530.905489] Start test: forwarding.test_forwarded_hdr.TestForwardedBaseAllowed.test_run Apr 26 03:03:01 192.168.122.209 [39532.029625] [tdb] Start Tempesta DB Apr 26 03:03:01 192.168.122.209 [39532.163797] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:03:03 192.168.122.209 [39533.554425] [tempesta fw] Configuration processing is completed. Apr 26 03:03:03 192.168.122.209 [39533.606819] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:03:03 192.168.122.209 [39534.033354] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:03:03 192.168.122.209 [39534.059914] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:03:03 192.168.122.209 [39534.086612] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:03:03 192.168.122.209 [39534.126365] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:03:03 192.168.122.209 [39534.166315] [tempesta fw] Tempesta FW is ready Apr 26 03:03:04 192.168.122.209 [39534.904352] [tdb] Close table 'client0.tdb' Apr 26 03:03:04 192.168.122.209 [39535.104887] [tdb] Close table 'sessions0.tdb' Apr 26 03:03:07 192.168.122.209 [39538.252235] [tdb] Close table 'cache0.tdb' Apr 26 03:03:08 192.168.122.209 [39538.520189] [tdb] Close table 'filter0.tdb' Apr 26 03:03:08 192.168.122.209 [39538.520618] [tempesta fw] modules are stopped Apr 26 03:03:08 192.168.122.209 [39538.716855] [tempesta fw] exiting... Apr 26 03:03:08 192.168.122.209 [39538.877921] [tdb] Shutdown Tempesta DB Apr 26 03:03:08 192.168.122.209 [39539.067529] End test: forwarding.test_forwarded_hdr.TestForwardedBaseAllowed.test_run Apr 26 03:03:08 192.168.122.209 [39539.086260] Start test: forwarding.test_forwarded_hdr.TestForwardedBaseDisallowed.test_run Apr 26 03:03:09 192.168.122.209 [39540.297245] [tdb] Start Tempesta DB Apr 26 03:03:10 192.168.122.209 [39540.455219] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:03:11 192.168.122.209 [39541.794529] [tempesta fw] Configuration processing is completed. Apr 26 03:03:11 192.168.122.209 [39541.851102] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:03:11 192.168.122.209 [39542.250432] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:03:11 192.168.122.209 [39542.275680] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:03:11 192.168.122.209 [39542.301227] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:03:12 192.168.122.209 [39542.354480] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:03:12 192.168.122.209 [39542.394424] [tempesta fw] Tempesta FW is ready Apr 26 03:03:12 192.168.122.209 [39542.525629] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-8)=0x68('warded: host=example.com:0 [39542.525629] [39542.525629] ') data_len=66 off=44 Apr 26 03:03:12 192.168.122.209 [39542.536899] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-8)=0x68('warded: host=example.com:65536 [39542.536899] [39542.536899] ') data_len=70 off=44 Apr 26 03:03:12 192.168.122.209 [39542.548499] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-8)=0x68('warded: host=example.com:8080; [39542.548499] [39542.548499] ') data_len=70 off=44 Apr 26 03:03:12 192.168.122.209 [39542.559536] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-8)=0x68('warded: host=example.com: [39542.559536] [39542.559536] ') data_len=65 off=44 Apr 26 03:03:12 192.168.122.209 [39542.570849] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-8)=0x68('warded: host=[1:2:3] [39542.570849] [39542.570849] ') data_len=60 off=44 Apr 26 03:03:12 192.168.122.209 [39542.582135] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-8)=0x68('warded: host="[1:2:3]:" [39542.582135] [39542.582135] ') data_len=63 off=44 Apr 26 03:03:12 192.168.122.209 [39543.244997] [tdb] Close table 'client0.tdb' Apr 26 03:03:13 192.168.122.209 [39543.445640] [tdb] Close table 'sessions0.tdb' Apr 26 03:03:16 192.168.122.209 [39546.568209] [tdb] Close table 'cache0.tdb' Apr 26 03:03:16 192.168.122.209 [39546.816502] [tdb] Close table 'filter0.tdb' Apr 26 03:03:16 192.168.122.209 [39546.816949] net_ratelimit: 16 callbacks suppressed Apr 26 03:03:16 192.168.122.209 [39546.816950] [tempesta fw] modules are stopped Apr 26 03:03:16 192.168.122.209 [39547.002216] [tempesta fw] exiting... Apr 26 03:03:16 192.168.122.209 [39547.152918] [tdb] Shutdown Tempesta DB Apr 26 03:03:17 192.168.122.209 [39547.365709] End test: forwarding.test_forwarded_hdr.TestForwardedBaseDisallowed.test_run Apr 26 03:03:17 192.168.122.209 [39547.374921] Start test: forwarding.test_forwarded_hdr.TestForwardedBaseMalicious.test_malicious Apr 26 03:03:18 192.168.122.209 [39548.544800] [tdb] Start Tempesta DB Apr 26 03:03:18 192.168.122.209 [39548.700156] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:03:19 192.168.122.209 [39550.066678] [tempesta fw] Configuration processing is completed. Apr 26 03:03:19 192.168.122.209 [39550.132082] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:03:20 192.168.122.209 [39550.550874] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:03:20 192.168.122.209 [39550.577211] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:03:20 192.168.122.209 [39550.603725] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:03:20 192.168.122.209 [39550.650575] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:03:20 192.168.122.209 [39550.694466] [tempesta fw] Tempesta FW is ready Apr 26 03:03:20 192.168.122.209 [39550.826691] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-8)=0x66('warded: for= [39550.826691] [39550.826691] ') data_len=57 off=44 Apr 26 03:03:20 192.168.122.209 [39550.837722] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-8)=0x66('warded: for="> [39550.837722] [39550.837722] ') data_len=59 off=44 Apr 26 03:03:20 192.168.122.209 [39550.851391] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-8)=0x66('warded: for=" onlick=alert(1) [39550.851391] [39550.851391] ') data_len=69 off=44 Apr 26 03:03:20 192.168.122.209 [39550.862638] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-8)=0x66('warded: for=' sqlinj [39550.862638] [39550.862638] ') data_len=60 off=44 Apr 26 03:03:20 192.168.122.209 [39550.873966] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-8)=0x68('warded: host= [39550.873966] [39550.873966] ') data_len=58 off=44 Apr 26 03:03:20 192.168.122.209 [39550.885357] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-8)=0x68('warded: host="> [39550.885357] [39550.885357] ') data_len=60 off=44 Apr 26 03:03:21 192.168.122.209 [39551.645751] [tdb] Close table 'client0.tdb' Apr 26 03:03:21 192.168.122.209 [39551.840440] [tdb] Close table 'sessions0.tdb' Apr 26 03:03:24 192.168.122.209 [39555.010971] [tdb] Close table 'cache0.tdb' Apr 26 03:03:24 192.168.122.209 [39555.255939] [tdb] Close table 'filter0.tdb' Apr 26 03:03:24 192.168.122.209 [39555.256391] net_ratelimit: 26 callbacks suppressed Apr 26 03:03:24 192.168.122.209 [39555.256392] [tempesta fw] modules are stopped Apr 26 03:03:25 192.168.122.209 [39555.506561] [tempesta fw] exiting... Apr 26 03:03:25 192.168.122.209 [39555.648103] [tdb] Shutdown Tempesta DB Apr 26 03:03:25 192.168.122.209 [39555.850076] End test: forwarding.test_forwarded_hdr.TestForwardedBaseMalicious.test_malicious Apr 26 03:03:25 192.168.122.209 [39555.860034] Start test: forwarding.test_forwarded_hdr.TestForwardedBaseMalicious.test_run Apr 26 03:03:26 192.168.122.209 [39557.018409] [tdb] Start Tempesta DB Apr 26 03:03:26 192.168.122.209 [39557.174231] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:03:28 192.168.122.209 [39558.554793] [tempesta fw] Configuration processing is completed. Apr 26 03:03:28 192.168.122.209 [39558.623485] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:03:28 192.168.122.209 [39559.039486] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:03:28 192.168.122.209 [39559.065672] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:03:28 192.168.122.209 [39559.091208] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:03:28 192.168.122.209 [39559.130690] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:03:28 192.168.122.209 [39559.170630] [tempesta fw] Tempesta FW is ready Apr 26 03:03:29 192.168.122.209 [39559.308758] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-8)=0x66('warded: for=%s [39559.308758] [39559.308758] ') data_len=54 off=44 Apr 26 03:03:29 192.168.122.209 [39559.340471] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-8)=0x68('warded: host=%s [39559.340471] [39559.340471] ') data_len=55 off=44 Apr 26 03:03:29 192.168.122.209 [39559.350940] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-8)=0x62('warded: by=%s [39559.350940] [39559.350940] ') data_len=53 off=44 Apr 26 03:03:29 192.168.122.209 [39559.361660] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-8)=0x70('warded: proto=%s [39559.361660] [39559.361660] ') data_len=56 off=44 Apr 26 03:03:29 192.168.122.209 [39559.372585] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-8)=0x68('warded: host=%s;for=1.1.1.1;by=2.2.2.2;proto=htt') data_len=89 off=44 Apr 26 03:03:29 192.168.122.209 [39559.383800] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-8)=0x68('warded: host=example.com;for=%s;by=2.2.2.2;proto') data_len=93 off=44 Apr 26 03:03:29 192.168.122.209 [39559.853297] [tdb] Close table 'client0.tdb' Apr 26 03:03:29 192.168.122.209 [39560.046655] [tdb] Close table 'sessions0.tdb' Apr 26 03:03:32 192.168.122.209 [39563.234393] [tdb] Close table 'cache0.tdb' Apr 26 03:03:33 192.168.122.209 [39563.473503] [tdb] Close table 'filter0.tdb' Apr 26 03:03:33 192.168.122.209 [39563.473956] net_ratelimit: 2 callbacks suppressed Apr 26 03:03:33 192.168.122.209 [39563.473957] [tempesta fw] modules are stopped Apr 26 03:03:33 192.168.122.209 [39563.704723] [tempesta fw] exiting... Apr 26 03:03:33 192.168.122.209 [39563.863977] [tdb] Shutdown Tempesta DB Apr 26 03:03:33 192.168.122.209 [39564.072861] End test: forwarding.test_forwarded_hdr.TestForwardedBaseMalicious.test_run Apr 26 03:03:33 192.168.122.209 [39564.083814] Start test: forwarding.test_match_host_forwarded.TestMatchHost.test_1 Apr 26 03:03:34 192.168.122.209 [39565.274809] [tdb] Start Tempesta DB Apr 26 03:03:35 192.168.122.209 [39565.441861] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:03:37 192.168.122.209 [39567.498951] [tempesta fw] Configuration processing is completed. Apr 26 03:03:37 192.168.122.209 [39567.552586] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:03:37 192.168.122.209 [39568.020981] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:03:37 192.168.122.209 [39568.050794] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:03:37 192.168.122.209 [39568.081198] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:03:37 192.168.122.209 [39568.170811] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:03:37 192.168.122.209 [39568.210762] [tempesta fw] Tempesta FW is ready Apr 26 03:03:38 192.168.122.209 [39568.971776] [tdb] Close table 'client0.tdb' Apr 26 03:03:38 192.168.122.209 [39569.172798] [tdb] Close table 'sessions0.tdb' Apr 26 03:03:42 192.168.122.209 [39572.332269] [tdb] Close table 'cache0.tdb' Apr 26 03:03:42 192.168.122.209 [39572.547873] [tdb] Close table 'filter0.tdb' Apr 26 03:03:42 192.168.122.209 [39572.548400] [tempesta fw] modules are stopped Apr 26 03:03:42 192.168.122.209 [39572.773906] [tempesta fw] exiting... Apr 26 03:03:42 192.168.122.209 [39572.915064] [tdb] Shutdown Tempesta DB Apr 26 03:03:42 192.168.122.209 [39573.113816] End test: forwarding.test_match_host_forwarded.TestMatchHost.test_1 Apr 26 03:03:42 192.168.122.209 [39573.129138] Start test: forwarding.test_match_host_forwarded.TestMatchHost.test_2 Apr 26 03:03:43 192.168.122.209 [39574.265578] [tdb] Start Tempesta DB Apr 26 03:03:44 192.168.122.209 [39574.418116] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:03:46 192.168.122.209 [39576.530913] [tempesta fw] Configuration processing is completed. Apr 26 03:03:46 192.168.122.209 [39576.632820] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:03:46 192.168.122.209 [39577.067599] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:03:46 192.168.122.209 [39577.096128] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:03:46 192.168.122.209 [39577.125155] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:03:46 192.168.122.209 [39577.226941] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:03:46 192.168.122.209 [39577.286867] [tempesta fw] Tempesta FW is ready Apr 26 03:03:47 192.168.122.209 [39577.995325] [tdb] Close table 'client0.tdb' Apr 26 03:03:47 192.168.122.209 [39578.197728] [tdb] Close table 'sessions0.tdb' Apr 26 03:03:51 192.168.122.209 [39581.344876] [tdb] Close table 'cache0.tdb' Apr 26 03:03:51 192.168.122.209 [39581.619279] [tdb] Close table 'filter0.tdb' Apr 26 03:03:51 192.168.122.209 [39581.619730] [tempesta fw] modules are stopped Apr 26 03:03:51 192.168.122.209 [39581.853059] [tempesta fw] exiting... Apr 26 03:03:51 192.168.122.209 [39582.020258] [tdb] Shutdown Tempesta DB Apr 26 03:03:51 192.168.122.209 [39582.221416] End test: forwarding.test_match_host_forwarded.TestMatchHost.test_2 Apr 26 03:03:51 192.168.122.209 [39582.233420] Start test: forwarding.test_match_host_forwarded.TestMatchHost.test_3 Apr 26 03:03:53 192.168.122.209 [39583.389879] [tdb] Start Tempesta DB Apr 26 03:03:53 192.168.122.209 [39583.542882] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:03:55 192.168.122.209 [39585.775243] [tempesta fw] Configuration processing is completed. Apr 26 03:03:55 192.168.122.209 [39585.834635] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:03:55 192.168.122.209 [39586.254419] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:03:55 192.168.122.209 [39586.280940] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:03:56 192.168.122.209 [39586.312048] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:03:56 192.168.122.209 [39586.419040] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:03:56 192.168.122.209 [39586.466974] [tempesta fw] Tempesta FW is ready Apr 26 03:03:57 192.168.122.209 [39587.322291] [tdb] Close table 'client0.tdb' Apr 26 03:03:57 192.168.122.209 [39587.516767] [tdb] Close table 'sessions0.tdb' Apr 26 03:04:00 192.168.122.209 [39590.562042] [tdb] Close table 'cache0.tdb' Apr 26 03:04:00 192.168.122.209 [39590.806175] [tdb] Close table 'filter0.tdb' Apr 26 03:04:00 192.168.122.209 [39590.806607] [tempesta fw] modules are stopped Apr 26 03:04:00 192.168.122.209 [39591.052882] [tempesta fw] exiting... Apr 26 03:04:00 192.168.122.209 [39591.225783] [tdb] Shutdown Tempesta DB Apr 26 03:04:01 192.168.122.209 [39591.467389] End test: forwarding.test_match_host_forwarded.TestMatchHost.test_3 Apr 26 03:04:01 192.168.122.209 [39591.481711] Start test: forwarding.test_match_host_forwarded.TestMatchHost.test_4 Apr 26 03:04:02 192.168.122.209 [39592.647575] [tdb] Start Tempesta DB Apr 26 03:04:02 192.168.122.209 [39592.798219] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:04:04 192.168.122.209 [39594.779312] [tempesta fw] Configuration processing is completed. Apr 26 03:04:04 192.168.122.209 [39594.833681] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:04:04 192.168.122.209 [39595.282481] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:04:05 192.168.122.209 [39595.312742] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:04:05 192.168.122.209 [39595.344158] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:04:05 192.168.122.209 [39595.455212] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:04:05 192.168.122.209 [39595.499034] [tempesta fw] Tempesta FW is ready Apr 26 03:04:05 192.168.122.209 [39596.273053] [tdb] Close table 'client0.tdb' Apr 26 03:04:06 192.168.122.209 [39596.472218] [tdb] Close table 'sessions0.tdb' Apr 26 03:04:09 192.168.122.209 [39599.633532] [tdb] Close table 'cache0.tdb' Apr 26 03:04:09 192.168.122.209 [39599.886884] [tdb] Close table 'filter0.tdb' Apr 26 03:04:09 192.168.122.209 [39599.887932] [tempesta fw] modules are stopped Apr 26 03:04:09 192.168.122.209 [39600.109202] [tempesta fw] exiting... Apr 26 03:04:09 192.168.122.209 [39600.244409] [tdb] Shutdown Tempesta DB Apr 26 03:04:10 192.168.122.209 [39600.438939] End test: forwarding.test_match_host_forwarded.TestMatchHost.test_4 Apr 26 03:04:10 192.168.122.209 [39600.447432] Start test: forwarding.test_match_host_forwarded.TestMatchHost.test_5 Apr 26 03:04:11 192.168.122.209 [39601.661995] [tdb] Start Tempesta DB Apr 26 03:04:11 192.168.122.209 [39601.807038] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:04:13 192.168.122.209 [39603.907396] [tempesta fw] Configuration processing is completed. Apr 26 03:04:13 192.168.122.209 [39603.957257] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:04:14 192.168.122.209 [39604.359100] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:04:14 192.168.122.209 [39604.384337] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:04:14 192.168.122.209 [39604.409516] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:04:14 192.168.122.209 [39604.531313] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:04:14 192.168.122.209 [39604.567157] [tempesta fw] Tempesta FW is ready Apr 26 03:04:15 192.168.122.209 [39605.338559] [tdb] Close table 'client0.tdb' Apr 26 03:04:15 192.168.122.209 [39605.534676] [tdb] Close table 'sessions0.tdb' Apr 26 03:04:18 192.168.122.209 [39608.759913] [tdb] Close table 'cache0.tdb' Apr 26 03:04:18 192.168.122.209 [39609.009317] [tdb] Close table 'filter0.tdb' Apr 26 03:04:18 192.168.122.209 [39609.009760] [tempesta fw] modules are stopped Apr 26 03:04:18 192.168.122.209 [39609.231329] [tempesta fw] exiting... Apr 26 03:04:19 192.168.122.209 [39609.392354] [tdb] Shutdown Tempesta DB Apr 26 03:04:19 192.168.122.209 [39609.594658] End test: forwarding.test_match_host_forwarded.TestMatchHost.test_5 Apr 26 03:04:19 192.168.122.209 [39609.604856] Start test: forwarding.test_match_host_forwarded.TestMatchHost.test_6 Apr 26 03:04:20 192.168.122.209 [39610.758904] [tdb] Start Tempesta DB Apr 26 03:04:20 192.168.122.209 [39610.935285] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:04:22 192.168.122.209 [39613.047525] [tempesta fw] Configuration processing is completed. Apr 26 03:04:22 192.168.122.209 [39613.098896] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:04:23 192.168.122.209 [39613.506657] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:04:23 192.168.122.209 [39613.533521] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:04:23 192.168.122.209 [39613.559839] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:04:23 192.168.122.209 [39613.663385] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:04:23 192.168.122.209 [39613.703325] [tempesta fw] Tempesta FW is ready Apr 26 03:04:24 192.168.122.209 [39614.476341] [tdb] Close table 'client0.tdb' Apr 26 03:04:24 192.168.122.209 [39614.671820] [tdb] Close table 'sessions0.tdb' Apr 26 03:04:27 192.168.122.209 [39617.814535] [tdb] Close table 'cache0.tdb' Apr 26 03:04:27 192.168.122.209 [39618.057252] [tdb] Close table 'filter0.tdb' Apr 26 03:04:27 192.168.122.209 [39618.057689] [tempesta fw] modules are stopped Apr 26 03:04:28 192.168.122.209 [39618.323819] [tempesta fw] exiting... Apr 26 03:04:28 192.168.122.209 [39618.480123] [tdb] Shutdown Tempesta DB Apr 26 03:04:28 192.168.122.209 [39618.711057] End test: forwarding.test_match_host_forwarded.TestMatchHost.test_6 Apr 26 03:04:28 192.168.122.209 [39618.734692] Start test: forwarding.test_match_host_forwarded.TestMatchHost.test_7 Apr 26 03:04:29 192.168.122.209 [39619.904695] [tdb] Start Tempesta DB Apr 26 03:04:29 192.168.122.209 [39620.051833] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:04:31 192.168.122.209 [39622.059556] [tempesta fw] Configuration processing is completed. Apr 26 03:04:31 192.168.122.209 [39622.142694] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:04:32 192.168.122.209 [39622.552050] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:04:32 192.168.122.209 [39622.578294] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:04:32 192.168.122.209 [39622.612262] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:04:32 192.168.122.209 [39622.707482] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:04:32 192.168.122.209 [39622.751434] [tempesta fw] Tempesta FW is ready Apr 26 03:04:33 192.168.122.209 [39623.524223] [tdb] Close table 'client0.tdb' Apr 26 03:04:33 192.168.122.209 [39623.714347] [tdb] Close table 'sessions0.tdb' Apr 26 03:04:36 192.168.122.209 [39626.830991] [tdb] Close table 'cache0.tdb' Apr 26 03:04:36 192.168.122.209 [39627.065997] [tdb] Close table 'filter0.tdb' Apr 26 03:04:36 192.168.122.209 [39627.066438] [tempesta fw] modules are stopped Apr 26 03:04:37 192.168.122.209 [39627.368525] [tempesta fw] exiting... Apr 26 03:04:37 192.168.122.209 [39627.515647] [tdb] Shutdown Tempesta DB Apr 26 03:04:37 192.168.122.209 [39627.757743] End test: forwarding.test_match_host_forwarded.TestMatchHost.test_7 Apr 26 03:04:37 192.168.122.209 [39627.782351] Start test: forwarding.test_match_host_forwarded.TestMatchHost.test_8 Apr 26 03:04:38 192.168.122.209 [39628.874469] [tdb] Start Tempesta DB Apr 26 03:04:38 192.168.122.209 [39629.035545] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:04:40 192.168.122.209 [39631.167714] [tempesta fw] Configuration processing is completed. Apr 26 03:04:40 192.168.122.209 [39631.221521] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:04:41 192.168.122.209 [39631.636205] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:04:41 192.168.122.209 [39631.670943] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:04:41 192.168.122.209 [39631.696025] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:04:41 192.168.122.209 [39631.791614] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:04:41 192.168.122.209 [39631.839545] [tempesta fw] Tempesta FW is ready Apr 26 03:04:41 192.168.122.209 [39631.974922] [tempesta fw] Warning: request has been filtered out via http table: 127.0.0.2 Apr 26 03:04:42 192.168.122.209 [39632.598489] [tdb] Close table 'client0.tdb' Apr 26 03:04:42 192.168.122.209 [39632.820047] [tdb] Close table 'sessions0.tdb' Apr 26 03:04:45 192.168.122.209 [39635.967748] [tdb] Close table 'cache0.tdb' Apr 26 03:04:45 192.168.122.209 [39636.222269] [tdb] Close table 'filter0.tdb' Apr 26 03:04:45 192.168.122.209 [39636.222698] [tempesta fw] modules are stopped Apr 26 03:04:46 192.168.122.209 [39636.493054] [tempesta fw] exiting... Apr 26 03:04:46 192.168.122.209 [39636.663441] [tdb] Shutdown Tempesta DB Apr 26 03:04:46 192.168.122.209 [39636.877297] End test: forwarding.test_match_host_forwarded.TestMatchHost.test_8 Apr 26 03:04:46 192.168.122.209 [39636.895638] Start test: forwarding.test_match_host_forwarded.TestMatchHost.test_9 Apr 26 03:04:47 192.168.122.209 [39638.026722] [tdb] Start Tempesta DB Apr 26 03:04:47 192.168.122.209 [39638.169860] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:04:49 192.168.122.209 [39640.135822] [tempesta fw] Configuration processing is completed. Apr 26 03:04:49 192.168.122.209 [39640.187952] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:04:50 192.168.122.209 [39640.589357] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:04:50 192.168.122.209 [39640.628510] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:04:50 192.168.122.209 [39640.653467] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:04:50 192.168.122.209 [39640.751731] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:04:50 192.168.122.209 [39640.791680] [tempesta fw] Tempesta FW is ready Apr 26 03:04:50 192.168.122.209 [39640.938109] [tempesta fw] Warning: request has been filtered out via http table: 127.0.0.2 Apr 26 03:04:51 192.168.122.209 [39641.567340] [tdb] Close table 'client0.tdb' Apr 26 03:04:51 192.168.122.209 [39641.758189] [tdb] Close table 'sessions0.tdb' Apr 26 03:04:54 192.168.122.209 [39644.889951] [tdb] Close table 'cache0.tdb' Apr 26 03:04:54 192.168.122.209 [39645.120627] [tdb] Close table 'filter0.tdb' Apr 26 03:04:54 192.168.122.209 [39645.121063] [tempesta fw] modules are stopped Apr 26 03:04:55 192.168.122.209 [39645.367910] [tempesta fw] exiting... Apr 26 03:04:55 192.168.122.209 [39645.510193] [tdb] Shutdown Tempesta DB Apr 26 03:04:55 192.168.122.209 [39645.706055] End test: forwarding.test_match_host_forwarded.TestMatchHost.test_9 Apr 26 03:04:55 192.168.122.209 [39645.738440] Start test: http2_general.test_flow_control_window.TestFlowControl.test_not_blocked_continuation_frame Apr 26 03:04:56 192.168.122.209 [39646.930407] [tdb] Start Tempesta DB Apr 26 03:04:56 192.168.122.209 [39647.084985] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:04:58 192.168.122.209 [39648.741275] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39648.741275] Maybe that's fine, but it's worth checking the [39648.741275] config - if there is no relations between the [39648.741275] names, then host name confusion attack is possible. Apr 26 03:04:58 192.168.122.209 [39648.903827] [tempesta fw] Configuration processing is completed. Apr 26 03:04:58 192.168.122.209 [39648.958488] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:04:59 192.168.122.209 [39649.407003] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:04:59 192.168.122.209 [39649.432175] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:04:59 192.168.122.209 [39649.457737] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:04:59 192.168.122.209 [39649.499827] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:04:59 192.168.122.209 [39649.539773] [tempesta fw] Tempesta FW is ready Apr 26 03:04:59 192.168.122.209 [39650.176030] [tdb] Close table 'client0.tdb' Apr 26 03:05:00 192.168.122.209 [39650.358419] [tdb] Close table 'sessions0.tdb' Apr 26 03:05:03 192.168.122.209 [39653.488833] [tdb] Close table 'cache0.tdb' Apr 26 03:05:03 192.168.122.209 [39653.744075] [tdb] Close table 'filter0.tdb' Apr 26 03:05:03 192.168.122.209 [39653.744510] [tempesta fw] modules are stopped Apr 26 03:05:03 192.168.122.209 [39653.972034] [tempesta fw] exiting... Apr 26 03:05:03 192.168.122.209 [39654.163101] [tdb] Shutdown Tempesta DB Apr 26 03:05:04 192.168.122.209 [39654.382870] End test: http2_general.test_flow_control_window.TestFlowControl.test_not_blocked_continuation_frame Apr 26 03:05:04 192.168.122.209 [39654.393909] Start test: http2_general.test_flow_control_window.TestFlowControl.test_not_blocked_rst_frame Apr 26 03:05:05 192.168.122.209 [39655.559940] [tdb] Start Tempesta DB Apr 26 03:05:05 192.168.122.209 [39655.708767] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:05:06 192.168.122.209 [39657.273398] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39657.273398] Maybe that's fine, but it's worth checking the [39657.273398] config - if there is no relations between the [39657.273398] names, then host name confusion attack is possible. Apr 26 03:05:07 192.168.122.209 [39657.432406] [tempesta fw] Configuration processing is completed. Apr 26 03:05:07 192.168.122.209 [39657.495803] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:05:07 192.168.122.209 [39657.901557] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:05:07 192.168.122.209 [39657.927499] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:05:07 192.168.122.209 [39657.953408] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:05:07 192.168.122.209 [39658.015933] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:05:07 192.168.122.209 [39658.055892] [tempesta fw] Tempesta FW is ready Apr 26 03:05:08 192.168.122.209 [39658.640809] [tdb] Close table 'client0.tdb' Apr 26 03:05:08 192.168.122.209 [39658.827028] [tdb] Close table 'sessions0.tdb' Apr 26 03:05:11 192.168.122.209 [39662.024638] [tdb] Close table 'cache0.tdb' Apr 26 03:05:11 192.168.122.209 [39662.264289] [tdb] Close table 'filter0.tdb' Apr 26 03:05:11 192.168.122.209 [39662.264734] [tempesta fw] modules are stopped Apr 26 03:05:12 192.168.122.209 [39662.509505] [tempesta fw] exiting... Apr 26 03:05:12 192.168.122.209 [39662.651933] [tdb] Shutdown Tempesta DB Apr 26 03:05:12 192.168.122.209 [39662.853361] End test: http2_general.test_flow_control_window.TestFlowControl.test_not_blocked_rst_frame Apr 26 03:05:12 192.168.122.209 [39662.865181] Start test: http2_general.test_flow_control_window.TestFlowControl.test_not_blocked_settings_frame Apr 26 03:05:13 192.168.122.209 [39664.004084] [tdb] Start Tempesta DB Apr 26 03:05:13 192.168.122.209 [39664.142489] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:05:15 192.168.122.209 [39665.897609] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39665.897609] Maybe that's fine, but it's worth checking the [39665.897609] config - if there is no relations between the [39665.897609] names, then host name confusion attack is possible. Apr 26 03:05:15 192.168.122.209 [39666.064058] [tempesta fw] Configuration processing is completed. Apr 26 03:05:15 192.168.122.209 [39666.116904] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:05:16 192.168.122.209 [39666.535475] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:05:16 192.168.122.209 [39666.560862] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:05:16 192.168.122.209 [39666.586327] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:05:16 192.168.122.209 [39666.628059] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:05:16 192.168.122.209 [39666.667995] [tempesta fw] Tempesta FW is ready Apr 26 03:05:16 192.168.122.209 [39667.258392] [tdb] Close table 'client0.tdb' Apr 26 03:05:17 192.168.122.209 [39667.461440] [tdb] Close table 'sessions0.tdb' Apr 26 03:05:20 192.168.122.209 [39670.601332] [tdb] Close table 'cache0.tdb' Apr 26 03:05:20 192.168.122.209 [39670.849078] [tdb] Close table 'filter0.tdb' Apr 26 03:05:20 192.168.122.209 [39670.849534] [tempesta fw] modules are stopped Apr 26 03:05:20 192.168.122.209 [39671.072113] [tempesta fw] exiting... Apr 26 03:05:20 192.168.122.209 [39671.224607] [tdb] Shutdown Tempesta DB Apr 26 03:05:21 192.168.122.209 [39671.413068] End test: http2_general.test_flow_control_window.TestFlowControl.test_not_blocked_settings_frame Apr 26 03:05:21 192.168.122.209 [39671.425469] Start test: http2_general.test_flow_control_window.TestFlowControl.test_request_body_greater_than_initial_window_size Apr 26 03:05:22 192.168.122.209 [39672.632317] [tdb] Start Tempesta DB Apr 26 03:05:22 192.168.122.209 [39672.782535] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:05:24 192.168.122.209 [39674.421567] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39674.421567] Maybe that's fine, but it's worth checking the [39674.421567] config - if there is no relations between the [39674.421567] names, then host name confusion attack is possible. Apr 26 03:05:24 192.168.122.209 [39674.580171] [tempesta fw] Configuration processing is completed. Apr 26 03:05:24 192.168.122.209 [39674.641628] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:05:24 192.168.122.209 [39675.088529] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:05:24 192.168.122.209 [39675.116612] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:05:24 192.168.122.209 [39675.144432] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:05:24 192.168.122.209 [39675.196176] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:05:24 192.168.122.209 [39675.240112] [tempesta fw] Tempesta FW is ready Apr 26 03:05:25 192.168.122.209 [39675.907820] [tdb] Close table 'client0.tdb' Apr 26 03:05:25 192.168.122.209 [39676.101523] [tdb] Close table 'sessions0.tdb' Apr 26 03:05:28 192.168.122.209 [39679.237472] [tdb] Close table 'cache0.tdb' Apr 26 03:05:29 192.168.122.209 [39679.496158] [tdb] Close table 'filter0.tdb' Apr 26 03:05:29 192.168.122.209 [39679.496613] [tempesta fw] modules are stopped Apr 26 03:05:29 192.168.122.209 [39679.710957] [tempesta fw] exiting... Apr 26 03:05:29 192.168.122.209 [39679.850578] [tdb] Shutdown Tempesta DB Apr 26 03:05:29 192.168.122.209 [39680.052122] End test: http2_general.test_flow_control_window.TestFlowControl.test_request_body_greater_than_initial_window_size Apr 26 03:05:29 192.168.122.209 [39680.072086] Start test: http2_general.test_flow_control_window.TestFlowControl.test_several_stream Apr 26 03:05:30 192.168.122.209 [39681.227264] [tdb] Start Tempesta DB Apr 26 03:05:31 192.168.122.209 [39681.358920] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:05:32 192.168.122.209 [39682.989716] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39682.989716] Maybe that's fine, but it's worth checking the [39682.989716] config - if there is no relations between the [39682.989716] names, then host name confusion attack is possible. Apr 26 03:05:32 192.168.122.209 [39683.144268] [tempesta fw] Configuration processing is completed. Apr 26 03:05:32 192.168.122.209 [39683.241757] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:05:33 192.168.122.209 [39683.657351] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:05:33 192.168.122.209 [39683.692946] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:05:33 192.168.122.209 [39683.720335] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:05:33 192.168.122.209 [39683.780262] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:05:33 192.168.122.209 [39683.824218] [tempesta fw] Tempesta FW is ready Apr 26 03:05:34 192.168.122.209 [39684.461319] [tdb] Close table 'client0.tdb' Apr 26 03:05:34 192.168.122.209 [39684.652119] [tdb] Close table 'sessions0.tdb' Apr 26 03:05:37 192.168.122.209 [39687.830244] [tdb] Close table 'cache0.tdb' Apr 26 03:05:37 192.168.122.209 [39688.059510] [tdb] Close table 'filter0.tdb' Apr 26 03:05:37 192.168.122.209 [39688.059955] [tempesta fw] modules are stopped Apr 26 03:05:38 192.168.122.209 [39688.345628] [tempesta fw] exiting... Apr 26 03:05:38 192.168.122.209 [39688.483538] [tdb] Shutdown Tempesta DB Apr 26 03:05:38 192.168.122.209 [39688.699394] End test: http2_general.test_flow_control_window.TestFlowControl.test_several_stream Apr 26 03:05:38 192.168.122.209 [39688.715143] Start test: http2_general.test_flow_control_window.TestFlowControl.test_single_stream_no_trailer_in_response Apr 26 03:05:39 192.168.122.209 [39689.852472] [tdb] Start Tempesta DB Apr 26 03:05:39 192.168.122.209 [39689.997289] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:05:41 192.168.122.209 [39691.625824] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39691.625824] Maybe that's fine, but it's worth checking the [39691.625824] config - if there is no relations between the [39691.625824] names, then host name confusion attack is possible. Apr 26 03:05:41 192.168.122.209 [39691.772393] [tempesta fw] Configuration processing is completed. Apr 26 03:05:41 192.168.122.209 [39691.828304] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:05:41 192.168.122.209 [39692.242805] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:05:41 192.168.122.209 [39692.268742] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:05:41 192.168.122.209 [39692.294197] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:05:42 192.168.122.209 [39692.356381] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:05:42 192.168.122.209 [39692.400333] [tempesta fw] Tempesta FW is ready Apr 26 03:05:42 192.168.122.209 [39693.021264] [tdb] Close table 'client0.tdb' Apr 26 03:05:42 192.168.122.209 [39693.220088] [tdb] Close table 'sessions0.tdb' Apr 26 03:05:46 192.168.122.209 [39696.486296] [tdb] Close table 'cache0.tdb' Apr 26 03:05:46 192.168.122.209 [39696.746224] [tdb] Close table 'filter0.tdb' Apr 26 03:05:46 192.168.122.209 [39696.746668] [tempesta fw] modules are stopped Apr 26 03:05:46 192.168.122.209 [39696.953125] [tempesta fw] exiting... Apr 26 03:05:46 192.168.122.209 [39697.110059] [tdb] Shutdown Tempesta DB Apr 26 03:05:47 192.168.122.209 [39697.330422] End test: http2_general.test_flow_control_window.TestFlowControl.test_single_stream_no_trailer_in_response Apr 26 03:05:47 192.168.122.209 [39697.346450] Start test: http2_general.test_flow_control_window.TestFlowControl.test_single_stream_trailer_in_response Apr 26 03:05:48 192.168.122.209 [39698.513466] [tdb] Start Tempesta DB Apr 26 03:05:48 192.168.122.209 [39698.661286] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:05:49 192.168.122.209 [39700.281922] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39700.281922] Maybe that's fine, but it's worth checking the [39700.281922] config - if there is no relations between the [39700.281922] names, then host name confusion attack is possible. Apr 26 03:05:50 192.168.122.209 [39700.428497] [tempesta fw] Configuration processing is completed. Apr 26 03:05:50 192.168.122.209 [39700.518313] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:05:50 192.168.122.209 [39700.934049] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:05:50 192.168.122.209 [39700.960799] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:05:50 192.168.122.209 [39700.988069] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:05:50 192.168.122.209 [39701.032491] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:05:50 192.168.122.209 [39701.076438] [tempesta fw] Tempesta FW is ready Apr 26 03:05:51 192.168.122.209 [39701.722146] [tdb] Close table 'client0.tdb' Apr 26 03:05:51 192.168.122.209 [39701.933840] [tdb] Close table 'sessions0.tdb' Apr 26 03:05:54 192.168.122.209 [39705.102271] [tdb] Close table 'cache0.tdb' Apr 26 03:05:55 192.168.122.209 [39705.328142] [tdb] Close table 'filter0.tdb' Apr 26 03:05:55 192.168.122.209 [39705.328591] [tempesta fw] modules are stopped Apr 26 03:05:55 192.168.122.209 [39705.577923] [tempesta fw] exiting... Apr 26 03:05:55 192.168.122.209 [39705.737794] [tdb] Shutdown Tempesta DB Apr 26 03:05:55 192.168.122.209 [39705.978023] End test: http2_general.test_flow_control_window.TestFlowControl.test_single_stream_trailer_in_response Apr 26 03:05:55 192.168.122.209 [39706.000730] Start test: http2_general.test_h2_frame.TestH2Frame.test_continuation_frame Apr 26 03:05:56 192.168.122.209 [39707.161724] [tdb] Start Tempesta DB Apr 26 03:05:56 192.168.122.209 [39707.294940] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:05:58 192.168.122.209 [39708.878001] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39708.878001] Maybe that's fine, but it's worth checking the [39708.878001] config - if there is no relations between the [39708.878001] names, then host name confusion attack is possible. Apr 26 03:05:58 192.168.122.209 [39709.040619] [tempesta fw] Configuration processing is completed. Apr 26 03:05:58 192.168.122.209 [39709.090327] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:05:59 192.168.122.209 [39709.496747] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:05:59 192.168.122.209 [39709.522369] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:05:59 192.168.122.209 [39709.547626] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:05:59 192.168.122.209 [39709.588602] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:05:59 192.168.122.209 [39709.636549] [tempesta fw] Tempesta FW is ready Apr 26 03:05:59 192.168.122.209 [39710.263707] [tdb] Close table 'client0.tdb' Apr 26 03:06:00 192.168.122.209 [39710.466293] [tdb] Close table 'sessions0.tdb' Apr 26 03:06:03 192.168.122.209 [39713.631768] [tdb] Close table 'cache0.tdb' Apr 26 03:06:03 192.168.122.209 [39713.876337] [tdb] Close table 'filter0.tdb' Apr 26 03:06:03 192.168.122.209 [39713.876798] [tempesta fw] modules are stopped Apr 26 03:06:03 192.168.122.209 [39714.123075] [tempesta fw] exiting... Apr 26 03:06:03 192.168.122.209 [39714.270552] [tdb] Shutdown Tempesta DB Apr 26 03:06:04 192.168.122.209 [39714.476259] End test: http2_general.test_h2_frame.TestH2Frame.test_continuation_frame Apr 26 03:06:04 192.168.122.209 [39714.496798] Start test: http2_general.test_h2_frame.TestH2Frame.test_data_framing Apr 26 03:06:05 192.168.122.209 [39715.719882] [tdb] Start Tempesta DB Apr 26 03:06:05 192.168.122.209 [39715.864158] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:06:07 192.168.122.209 [39717.458132] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39717.458132] Maybe that's fine, but it's worth checking the [39717.458132] config - if there is no relations between the [39717.458132] names, then host name confusion attack is possible. Apr 26 03:06:07 192.168.122.209 [39717.612726] [tempesta fw] Configuration processing is completed. Apr 26 03:06:07 192.168.122.209 [39717.662922] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:06:07 192.168.122.209 [39718.067684] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:06:07 192.168.122.209 [39718.092871] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:06:07 192.168.122.209 [39718.117905] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:06:07 192.168.122.209 [39718.160713] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:06:07 192.168.122.209 [39718.204782] [tempesta fw] Tempesta FW is ready Apr 26 03:06:08 192.168.122.209 [39718.848722] [tdb] Close table 'client0.tdb' Apr 26 03:06:08 192.168.122.209 [39719.076239] [tdb] Close table 'sessions0.tdb' Apr 26 03:06:11 192.168.122.209 [39722.223648] [tdb] Close table 'cache0.tdb' Apr 26 03:06:12 192.168.122.209 [39722.443594] [tdb] Close table 'filter0.tdb' Apr 26 03:06:12 192.168.122.209 [39722.444040] [tempesta fw] modules are stopped Apr 26 03:06:12 192.168.122.209 [39722.672293] [tempesta fw] exiting... Apr 26 03:06:12 192.168.122.209 [39722.822679] [tdb] Shutdown Tempesta DB Apr 26 03:06:12 192.168.122.209 [39723.039440] End test: http2_general.test_h2_frame.TestH2Frame.test_data_framing Apr 26 03:06:12 192.168.122.209 [39723.051817] Start test: http2_general.test_h2_frame.TestH2Frame.test_empty_continuation_end_headers Apr 26 03:06:13 192.168.122.209 [39724.256373] [tdb] Start Tempesta DB Apr 26 03:06:14 192.168.122.209 [39724.415020] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:06:15 192.168.122.209 [39725.990226] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39725.990226] Maybe that's fine, but it's worth checking the [39725.990226] config - if there is no relations between the [39725.990226] names, then host name confusion attack is possible. Apr 26 03:06:15 192.168.122.209 [39726.144821] [tempesta fw] Configuration processing is completed. Apr 26 03:06:15 192.168.122.209 [39726.240279] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:06:16 192.168.122.209 [39726.699481] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:06:16 192.168.122.209 [39726.728636] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:06:16 192.168.122.209 [39726.758259] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:06:16 192.168.122.209 [39726.796827] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:06:16 192.168.122.209 [39726.836749] [tempesta fw] Tempesta FW is ready Apr 26 03:06:17 192.168.122.209 [39727.455731] [tdb] Close table 'client0.tdb' Apr 26 03:06:17 192.168.122.209 [39727.652859] [tdb] Close table 'sessions0.tdb' Apr 26 03:06:20 192.168.122.209 [39730.799501] [tdb] Close table 'cache0.tdb' Apr 26 03:06:20 192.168.122.209 [39731.033287] [tdb] Close table 'filter0.tdb' Apr 26 03:06:20 192.168.122.209 [39731.033726] [tempesta fw] modules are stopped Apr 26 03:06:21 192.168.122.209 [39731.334223] [tempesta fw] exiting... Apr 26 03:06:21 192.168.122.209 [39731.454253] [tdb] Shutdown Tempesta DB Apr 26 03:06:21 192.168.122.209 [39731.650302] End test: http2_general.test_h2_frame.TestH2Frame.test_empty_continuation_end_headers Apr 26 03:06:21 192.168.122.209 [39731.670911] Start test: http2_general.test_h2_frame.TestH2Frame.test_empty_continuation_frame Apr 26 03:06:22 192.168.122.209 [39732.798979] [tdb] Start Tempesta DB Apr 26 03:06:22 192.168.122.209 [39732.937040] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:06:24 192.168.122.209 [39734.598332] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39734.598332] Maybe that's fine, but it's worth checking the [39734.598332] config - if there is no relations between the [39734.598332] names, then host name confusion attack is possible. Apr 26 03:06:24 192.168.122.209 [39734.744951] [tempesta fw] Configuration processing is completed. Apr 26 03:06:24 192.168.122.209 [39734.794058] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:06:24 192.168.122.209 [39735.194883] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:06:24 192.168.122.209 [39735.220036] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:06:24 192.168.122.209 [39735.245059] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:06:24 192.168.122.209 [39735.292932] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:06:25 192.168.122.209 [39735.332896] [tempesta fw] Tempesta FW is ready Apr 26 03:06:25 192.168.122.209 [39735.477025] [tempesta fw] Empty CONTINUATION frame without END_HEADERS Apr 26 03:06:25 192.168.122.209 [39735.877536] [tdb] Close table 'client0.tdb' Apr 26 03:06:25 192.168.122.209 [39736.093501] [tdb] Close table 'sessions0.tdb' Apr 26 03:06:28 192.168.122.209 [39739.270058] [tdb] Close table 'cache0.tdb' Apr 26 03:06:29 192.168.122.209 [39739.514262] [tdb] Close table 'filter0.tdb' Apr 26 03:06:29 192.168.122.209 [39739.514661] [tempesta fw] modules are stopped Apr 26 03:06:29 192.168.122.209 [39739.774839] [tempesta fw] exiting... Apr 26 03:06:29 192.168.122.209 [39739.950298] [tdb] Shutdown Tempesta DB Apr 26 03:06:29 192.168.122.209 [39740.166248] End test: http2_general.test_h2_frame.TestH2Frame.test_empty_continuation_frame Apr 26 03:06:29 192.168.122.209 [39740.177885] Start test: http2_general.test_h2_frame.TestH2Frame.test_empty_data_frame Apr 26 03:06:31 192.168.122.209 [39741.355873] [tdb] Start Tempesta DB Apr 26 03:06:31 192.168.122.209 [39741.520728] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:06:32 192.168.122.209 [39743.102486] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39743.102486] Maybe that's fine, but it's worth checking the [39743.102486] config - if there is no relations between the [39743.102486] names, then host name confusion attack is possible. Apr 26 03:06:32 192.168.122.209 [39743.257152] [tempesta fw] Configuration processing is completed. Apr 26 03:06:33 192.168.122.209 [39743.306489] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:06:33 192.168.122.209 [39743.718538] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:06:33 192.168.122.209 [39743.743717] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:06:33 192.168.122.209 [39743.769020] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:06:33 192.168.122.209 [39743.813031] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:06:33 192.168.122.209 [39743.864982] [tempesta fw] Tempesta FW is ready Apr 26 03:06:34 192.168.122.209 [39744.002523] [tempesta fw] Empty DATA frame without END_STREAM Apr 26 03:06:34 192.168.122.209 [39744.478237] [tdb] Close table 'client0.tdb' Apr 26 03:06:34 192.168.122.209 [39744.688934] [tdb] Close table 'sessions0.tdb' Apr 26 03:06:37 192.168.122.209 [39747.856618] [tdb] Close table 'cache0.tdb' Apr 26 03:06:37 192.168.122.209 [39748.110589] [tdb] Close table 'filter0.tdb' Apr 26 03:06:37 192.168.122.209 [39748.111011] [tempesta fw] modules are stopped Apr 26 03:06:38 192.168.122.209 [39748.318651] [tempesta fw] exiting... Apr 26 03:06:38 192.168.122.209 [39748.469907] [tdb] Shutdown Tempesta DB Apr 26 03:06:38 192.168.122.209 [39748.679408] End test: http2_general.test_h2_frame.TestH2Frame.test_empty_data_frame Apr 26 03:06:38 192.168.122.209 [39748.696891] Start test: http2_general.test_h2_frame.TestH2Frame.test_empty_data_frame_mixed Apr 26 03:06:39 192.168.122.209 [39749.840697] [tdb] Start Tempesta DB Apr 26 03:06:39 192.168.122.209 [39749.973080] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:06:41 192.168.122.209 [39751.554269] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39751.554269] Maybe that's fine, but it's worth checking the [39751.554269] config - if there is no relations between the [39751.554269] names, then host name confusion attack is possible. Apr 26 03:06:41 192.168.122.209 [39751.709171] [tempesta fw] Configuration processing is completed. Apr 26 03:06:41 192.168.122.209 [39751.791994] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:06:41 192.168.122.209 [39752.203594] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:06:41 192.168.122.209 [39752.229681] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:06:41 192.168.122.209 [39752.256317] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:06:41 192.168.122.209 [39752.301134] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:06:42 192.168.122.209 [39752.341081] [tempesta fw] Tempesta FW is ready Apr 26 03:06:42 192.168.122.209 [39752.491161] [tempesta fw] Empty DATA frame without END_STREAM Apr 26 03:06:42 192.168.122.209 [39752.928748] [tdb] Close table 'client0.tdb' Apr 26 03:06:42 192.168.122.209 [39753.144342] [tdb] Close table 'sessions0.tdb' Apr 26 03:06:45 192.168.122.209 [39756.296489] [tdb] Close table 'cache0.tdb' Apr 26 03:06:46 192.168.122.209 [39756.526269] [tdb] Close table 'filter0.tdb' Apr 26 03:06:46 192.168.122.209 [39756.526885] [tempesta fw] modules are stopped Apr 26 03:06:46 192.168.122.209 [39756.776784] [tempesta fw] exiting... Apr 26 03:06:46 192.168.122.209 [39756.920117] [tdb] Shutdown Tempesta DB Apr 26 03:06:46 192.168.122.209 [39757.172177] End test: http2_general.test_h2_frame.TestH2Frame.test_empty_data_frame_mixed Apr 26 03:06:46 192.168.122.209 [39757.188914] Start test: http2_general.test_h2_frame.TestH2Frame.test_empty_headers_empty_continuation_multiple Apr 26 03:06:48 192.168.122.209 [39758.346393] [tdb] Start Tempesta DB Apr 26 03:06:48 192.168.122.209 [39758.485876] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:06:49 192.168.122.209 [39760.130717] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39760.130717] Maybe that's fine, but it's worth checking the [39760.130717] config - if there is no relations between the [39760.130717] names, then host name confusion attack is possible. Apr 26 03:06:49 192.168.122.209 [39760.281283] [tempesta fw] Configuration processing is completed. Apr 26 03:06:50 192.168.122.209 [39760.330691] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:06:50 192.168.122.209 [39760.732004] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:06:50 192.168.122.209 [39760.757679] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:06:50 192.168.122.209 [39760.782793] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:06:50 192.168.122.209 [39760.833246] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:06:50 192.168.122.209 [39760.881144] [tempesta fw] Tempesta FW is ready Apr 26 03:06:51 192.168.122.209 [39761.466673] [tdb] Close table 'client0.tdb' Apr 26 03:06:51 192.168.122.209 [39761.656242] [tdb] Close table 'sessions0.tdb' Apr 26 03:06:54 192.168.122.209 [39764.830854] [tdb] Close table 'cache0.tdb' Apr 26 03:06:54 192.168.122.209 [39765.084348] [tdb] Close table 'filter0.tdb' Apr 26 03:06:54 192.168.122.209 [39765.084779] [tempesta fw] modules are stopped Apr 26 03:06:54 192.168.122.209 [39765.294566] [tempesta fw] exiting... Apr 26 03:06:55 192.168.122.209 [39765.425614] [tdb] Shutdown Tempesta DB Apr 26 03:06:55 192.168.122.209 [39765.644724] End test: http2_general.test_h2_frame.TestH2Frame.test_empty_headers_empty_continuation_multiple Apr 26 03:06:55 192.168.122.209 [39765.669709] Start test: http2_general.test_h2_frame.TestH2Frame.test_empty_headers_frame_end_headers Apr 26 03:06:56 192.168.122.209 [39766.794277] [tdb] Start Tempesta DB Apr 26 03:06:56 192.168.122.209 [39766.940389] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:06:58 192.168.122.209 [39768.570779] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39768.570779] Maybe that's fine, but it's worth checking the [39768.570779] config - if there is no relations between the [39768.570779] names, then host name confusion attack is possible. Apr 26 03:06:58 192.168.122.209 [39768.717359] [tempesta fw] Configuration processing is completed. Apr 26 03:06:58 192.168.122.209 [39768.766815] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:06:58 192.168.122.209 [39769.171486] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:06:58 192.168.122.209 [39769.197172] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:06:58 192.168.122.209 [39769.222620] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:06:58 192.168.122.209 [39769.269371] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:06:59 192.168.122.209 [39769.313305] [tempesta fw] Tempesta FW is ready Apr 26 03:06:59 192.168.122.209 [39769.919504] [tdb] Close table 'client0.tdb' Apr 26 03:06:59 192.168.122.209 [39770.119565] [tdb] Close table 'sessions0.tdb' Apr 26 03:07:02 192.168.122.209 [39773.262499] [tdb] Close table 'cache0.tdb' Apr 26 03:07:03 192.168.122.209 [39773.509171] [tdb] Close table 'filter0.tdb' Apr 26 03:07:03 192.168.122.209 [39773.509607] [tempesta fw] modules are stopped Apr 26 03:07:03 192.168.122.209 [39773.709484] [tempesta fw] exiting... Apr 26 03:07:03 192.168.122.209 [39773.876754] [tdb] Shutdown Tempesta DB Apr 26 03:07:03 192.168.122.209 [39774.091655] End test: http2_general.test_h2_frame.TestH2Frame.test_empty_headers_frame_end_headers Apr 26 03:07:03 192.168.122.209 [39774.101937] Start test: http2_general.test_h2_frame.TestH2Frame.test_empty_headers_frame_no_end_headers Apr 26 03:07:04 192.168.122.209 [39775.290482] [tdb] Start Tempesta DB Apr 26 03:07:05 192.168.122.209 [39775.438313] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:07:06 192.168.122.209 [39777.078863] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39777.078863] Maybe that's fine, but it's worth checking the [39777.078863] config - if there is no relations between the [39777.078863] names, then host name confusion attack is possible. Apr 26 03:07:06 192.168.122.209 [39777.241821] [tempesta fw] Configuration processing is completed. Apr 26 03:07:07 192.168.122.209 [39777.322826] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:07:07 192.168.122.209 [39777.729333] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:07:07 192.168.122.209 [39777.755691] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:07:07 192.168.122.209 [39777.782409] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:07:07 192.168.122.209 [39777.845494] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:07:07 192.168.122.209 [39777.897423] [tempesta fw] Tempesta FW is ready Apr 26 03:07:08 192.168.122.209 [39778.484663] [tdb] Close table 'client0.tdb' Apr 26 03:07:08 192.168.122.209 [39778.683673] [tdb] Close table 'sessions0.tdb' Apr 26 03:07:11 192.168.122.209 [39781.813252] [tdb] Close table 'cache0.tdb' Apr 26 03:07:11 192.168.122.209 [39782.077506] [tdb] Close table 'filter0.tdb' Apr 26 03:07:11 192.168.122.209 [39782.077940] [tempesta fw] modules are stopped Apr 26 03:07:12 192.168.122.209 [39782.323543] [tempesta fw] exiting... Apr 26 03:07:12 192.168.122.209 [39782.488699] [tdb] Shutdown Tempesta DB Apr 26 03:07:12 192.168.122.209 [39782.740838] End test: http2_general.test_h2_frame.TestH2Frame.test_empty_headers_frame_no_end_headers Apr 26 03:07:12 192.168.122.209 [39782.751954] Start test: http2_general.test_h2_frame.TestH2Frame.test_empty_last_data_frame Apr 26 03:07:13 192.168.122.209 [39783.905413] [tdb] Start Tempesta DB Apr 26 03:07:13 192.168.122.209 [39784.063203] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:07:15 192.168.122.209 [39785.586388] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39785.586388] Maybe that's fine, but it's worth checking the [39785.586388] config - if there is no relations between the [39785.586388] names, then host name confusion attack is possible. Apr 26 03:07:15 192.168.122.209 [39785.733603] [tempesta fw] Configuration processing is completed. Apr 26 03:07:15 192.168.122.209 [39785.782733] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:07:15 192.168.122.209 [39786.188498] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:07:15 192.168.122.209 [39786.214400] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:07:15 192.168.122.209 [39786.239648] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:07:15 192.168.122.209 [39786.297538] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:07:16 192.168.122.209 [39786.337579] [tempesta fw] Tempesta FW is ready Apr 26 03:07:16 192.168.122.209 [39786.978531] [tdb] Close table 'client0.tdb' Apr 26 03:07:16 192.168.122.209 [39787.185113] [tdb] Close table 'sessions0.tdb' Apr 26 03:07:20 192.168.122.209 [39790.339859] [tdb] Close table 'cache0.tdb' Apr 26 03:07:20 192.168.122.209 [39790.575208] [tdb] Close table 'filter0.tdb' Apr 26 03:07:20 192.168.122.209 [39790.575643] [tempesta fw] modules are stopped Apr 26 03:07:20 192.168.122.209 [39790.825726] [tempesta fw] exiting... Apr 26 03:07:20 192.168.122.209 [39790.991569] [tdb] Shutdown Tempesta DB Apr 26 03:07:20 192.168.122.209 [39791.196235] End test: http2_general.test_h2_frame.TestH2Frame.test_empty_last_data_frame Apr 26 03:07:20 192.168.122.209 [39791.212508] Start test: http2_general.test_h2_frame.TestH2Frame.test_goaway_frame_in_request Apr 26 03:07:22 192.168.122.209 [39792.430134] [tdb] Start Tempesta DB Apr 26 03:07:22 192.168.122.209 [39792.567797] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:07:23 192.168.122.209 [39794.155017] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39794.155017] Maybe that's fine, but it's worth checking the [39794.155017] config - if there is no relations between the [39794.155017] names, then host name confusion attack is possible. Apr 26 03:07:24 192.168.122.209 [39794.317684] [tempesta fw] Configuration processing is completed. Apr 26 03:07:24 192.168.122.209 [39794.375150] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:07:24 192.168.122.209 [39794.779743] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:07:24 192.168.122.209 [39794.805220] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:07:24 192.168.122.209 [39794.830337] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:07:24 192.168.122.209 [39794.885676] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:07:24 192.168.122.209 [39794.933628] [tempesta fw] Tempesta FW is ready Apr 26 03:07:24 192.168.122.209 [39795.088720] [tempesta fw] HTTP/2 connection is closed by client with error code: 1, ID of last processed stream: 4 Apr 26 03:07:25 192.168.122.209 [39795.522130] [tdb] Close table 'client0.tdb' Apr 26 03:07:25 192.168.122.209 [39795.739555] [tdb] Close table 'sessions0.tdb' Apr 26 03:07:28 192.168.122.209 [39798.868111] [tdb] Close table 'cache0.tdb' Apr 26 03:07:28 192.168.122.209 [39799.111052] [tdb] Close table 'filter0.tdb' Apr 26 03:07:28 192.168.122.209 [39799.111495] [tempesta fw] modules are stopped Apr 26 03:07:29 192.168.122.209 [39799.374479] [tempesta fw] exiting... Apr 26 03:07:29 192.168.122.209 [39799.534342] [tdb] Shutdown Tempesta DB Apr 26 03:07:29 192.168.122.209 [39799.751479] End test: http2_general.test_h2_frame.TestH2Frame.test_goaway_frame_in_request Apr 26 03:07:29 192.168.122.209 [39799.762553] Start test: http2_general.test_h2_frame.TestH2Frame.test_goaway_frame_in_response Apr 26 03:07:30 192.168.122.209 [39800.948211] [tdb] Start Tempesta DB Apr 26 03:07:30 192.168.122.209 [39801.100462] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:07:32 192.168.122.209 [39802.707245] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39802.707245] Maybe that's fine, but it's worth checking the [39802.707245] config - if there is no relations between the [39802.707245] names, then host name confusion attack is possible. Apr 26 03:07:32 192.168.122.209 [39802.865834] [tempesta fw] Configuration processing is completed. Apr 26 03:07:32 192.168.122.209 [39802.949376] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:07:33 192.168.122.209 [39803.374399] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:07:33 192.168.122.209 [39803.400974] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:07:33 192.168.122.209 [39803.428013] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:07:33 192.168.122.209 [39803.469757] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:07:33 192.168.122.209 [39803.509745] [tempesta fw] Tempesta FW is ready Apr 26 03:07:33 192.168.122.209 [39804.120077] [tdb] Close table 'client0.tdb' Apr 26 03:07:34 192.168.122.209 [39804.314226] [tdb] Close table 'sessions0.tdb' Apr 26 03:07:37 192.168.122.209 [39807.449085] [tdb] Close table 'cache0.tdb' Apr 26 03:07:37 192.168.122.209 [39807.689273] [tdb] Close table 'filter0.tdb' Apr 26 03:07:37 192.168.122.209 [39807.689716] [tempesta fw] modules are stopped Apr 26 03:07:37 192.168.122.209 [39807.970536] [tempesta fw] exiting... Apr 26 03:07:37 192.168.122.209 [39808.092029] [tdb] Shutdown Tempesta DB Apr 26 03:07:38 192.168.122.209 [39808.320191] End test: http2_general.test_h2_frame.TestH2Frame.test_goaway_frame_in_response Apr 26 03:07:38 192.168.122.209 [39808.328129] Start test: http2_general.test_h2_frame.TestH2Frame.test_multiple_empty_headers_frames Apr 26 03:07:39 192.168.122.209 [39809.512412] [tdb] Start Tempesta DB Apr 26 03:07:39 192.168.122.209 [39809.663014] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:07:40 192.168.122.209 [39811.227303] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39811.227303] Maybe that's fine, but it's worth checking the [39811.227303] config - if there is no relations between the [39811.227303] names, then host name confusion attack is possible. Apr 26 03:07:41 192.168.122.209 [39811.373902] [tempesta fw] Configuration processing is completed. Apr 26 03:07:41 192.168.122.209 [39811.423550] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:07:41 192.168.122.209 [39811.831605] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:07:41 192.168.122.209 [39811.858156] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:07:41 192.168.122.209 [39811.883169] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:07:41 192.168.122.209 [39811.929899] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:07:41 192.168.122.209 [39811.969850] [tempesta fw] Tempesta FW is ready Apr 26 03:07:42 192.168.122.209 [39812.554983] [tdb] Close table 'client0.tdb' Apr 26 03:07:42 192.168.122.209 [39812.739541] [tdb] Close table 'sessions0.tdb' Apr 26 03:07:45 192.168.122.209 [39815.921602] [tdb] Close table 'cache0.tdb' Apr 26 03:07:45 192.168.122.209 [39816.176651] [tdb] Close table 'filter0.tdb' Apr 26 03:07:45 192.168.122.209 [39816.177083] [tempesta fw] modules are stopped Apr 26 03:07:46 192.168.122.209 [39816.397881] [tempesta fw] exiting... Apr 26 03:07:46 192.168.122.209 [39816.555400] [tdb] Shutdown Tempesta DB Apr 26 03:07:46 192.168.122.209 [39816.747018] End test: http2_general.test_h2_frame.TestH2Frame.test_multiple_empty_headers_frames Apr 26 03:07:46 192.168.122.209 [39816.768263] Start test: http2_general.test_h2_frame.TestH2Frame.test_opening_same_stream_after_invalid Apr 26 03:07:47 192.168.122.209 [39817.911524] [tdb] Start Tempesta DB Apr 26 03:07:47 192.168.122.209 [39818.053753] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:07:49 192.168.122.209 [39819.763343] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39819.763343] Maybe that's fine, but it's worth checking the [39819.763343] config - if there is no relations between the [39819.763343] names, then host name confusion attack is possible. Apr 26 03:07:49 192.168.122.209 [39819.910046] [tempesta fw] Configuration processing is completed. Apr 26 03:07:49 192.168.122.209 [39819.960165] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:07:50 192.168.122.209 [39820.371627] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:07:50 192.168.122.209 [39820.398347] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:07:50 192.168.122.209 [39820.433302] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:07:50 192.168.122.209 [39820.482016] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:07:50 192.168.122.209 [39820.525977] [tempesta fw] Tempesta FW is ready Apr 26 03:07:50 192.168.122.209 [39821.108866] [tdb] Close table 'client0.tdb' Apr 26 03:07:50 192.168.122.209 [39821.300110] [tdb] Close table 'sessions0.tdb' Apr 26 03:07:54 192.168.122.209 [39824.447044] [tdb] Close table 'cache0.tdb' Apr 26 03:07:54 192.168.122.209 [39824.692479] [tdb] Close table 'filter0.tdb' Apr 26 03:07:54 192.168.122.209 [39824.692933] [tempesta fw] modules are stopped Apr 26 03:07:54 192.168.122.209 [39824.914837] [tempesta fw] exiting... Apr 26 03:07:54 192.168.122.209 [39825.105511] [tdb] Shutdown Tempesta DB Apr 26 03:07:54 192.168.122.209 [39825.299900] End test: http2_general.test_h2_frame.TestH2Frame.test_opening_same_stream_after_invalid Apr 26 03:07:55 192.168.122.209 [39825.309656] Start test: http2_general.test_h2_frame.TestH2Frame.test_rst_frame_in_request Apr 26 03:07:56 192.168.122.209 [39826.432143] [tdb] Start Tempesta DB Apr 26 03:07:56 192.168.122.209 [39826.603394] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:07:57 192.168.122.209 [39828.180332] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39828.180332] Maybe that's fine, but it's worth checking the [39828.180332] config - if there is no relations between the [39828.180332] names, then host name confusion attack is possible. Apr 26 03:07:58 192.168.122.209 [39828.318135] [tempesta fw] Configuration processing is completed. Apr 26 03:07:58 192.168.122.209 [39828.399984] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:07:58 192.168.122.209 [39828.825373] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:07:58 192.168.122.209 [39828.851810] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:07:58 192.168.122.209 [39828.879104] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:07:58 192.168.122.209 [39828.922111] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:07:58 192.168.122.209 [39828.962070] [tempesta fw] Tempesta FW is ready Apr 26 03:07:59 192.168.122.209 [39829.566611] [tdb] Close table 'client0.tdb' Apr 26 03:07:59 192.168.122.209 [39829.772465] [tdb] Close table 'sessions0.tdb' Apr 26 03:08:02 192.168.122.209 [39832.956609] [tdb] Close table 'cache0.tdb' Apr 26 03:08:02 192.168.122.209 [39833.241996] [tdb] Close table 'filter0.tdb' Apr 26 03:08:02 192.168.122.209 [39833.242438] [tempesta fw] modules are stopped Apr 26 03:08:03 192.168.122.209 [39833.513979] [tempesta fw] exiting... Apr 26 03:08:03 192.168.122.209 [39833.653626] [tdb] Shutdown Tempesta DB Apr 26 03:08:03 192.168.122.209 [39833.885535] End test: http2_general.test_h2_frame.TestH2Frame.test_rst_frame_in_request Apr 26 03:08:03 192.168.122.209 [39833.898267] Start test: http2_general.test_h2_frame.TestH2Frame.test_rst_frame_in_response Apr 26 03:08:04 192.168.122.209 [39835.077355] [tdb] Start Tempesta DB Apr 26 03:08:04 192.168.122.209 [39835.219098] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:08:06 192.168.122.209 [39836.831666] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39836.831666] Maybe that's fine, but it's worth checking the [39836.831666] config - if there is no relations between the [39836.831666] names, then host name confusion attack is possible. Apr 26 03:08:06 192.168.122.209 [39836.986538] [tempesta fw] Configuration processing is completed. Apr 26 03:08:06 192.168.122.209 [39837.036412] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:08:07 192.168.122.209 [39837.440450] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:08:07 192.168.122.209 [39837.465681] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:08:07 192.168.122.209 [39837.490659] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:08:07 192.168.122.209 [39837.530214] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:08:07 192.168.122.209 [39837.578176] [tempesta fw] Tempesta FW is ready Apr 26 03:08:07 192.168.122.209 [39837.721455] [tempesta fw] Warning: request dropped: incorrect X-Forwarded-For header: 127.0.0.2 Apr 26 03:08:07 192.168.122.209 [39838.201957] [tdb] Close table 'client0.tdb' Apr 26 03:08:08 192.168.122.209 [39838.381966] [tdb] Close table 'sessions0.tdb' Apr 26 03:08:11 192.168.122.209 [39841.533302] [tdb] Close table 'cache0.tdb' Apr 26 03:08:11 192.168.122.209 [39841.772531] [tdb] Close table 'filter0.tdb' Apr 26 03:08:11 192.168.122.209 [39841.772982] [tempesta fw] modules are stopped Apr 26 03:08:11 192.168.122.209 [39842.066795] [tempesta fw] exiting... Apr 26 03:08:11 192.168.122.209 [39842.257932] [tdb] Shutdown Tempesta DB Apr 26 03:08:12 192.168.122.209 [39842.450758] End test: http2_general.test_h2_frame.TestH2Frame.test_rst_frame_in_response Apr 26 03:08:12 192.168.122.209 [39842.462317] Start test: http2_general.test_h2_frame.TestH2Frame.test_rst_stream_with_id_0 Apr 26 03:08:13 192.168.122.209 [39843.610156] [tdb] Start Tempesta DB Apr 26 03:08:13 192.168.122.209 [39843.762366] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:08:15 192.168.122.209 [39845.323747] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39845.323747] Maybe that's fine, but it's worth checking the [39845.323747] config - if there is no relations between the [39845.323747] names, then host name confusion attack is possible. Apr 26 03:08:15 192.168.122.209 [39845.486330] [tempesta fw] Configuration processing is completed. Apr 26 03:08:15 192.168.122.209 [39845.535922] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:08:15 192.168.122.209 [39845.947689] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:08:15 192.168.122.209 [39845.972812] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:08:15 192.168.122.209 [39845.998156] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:08:15 192.168.122.209 [39846.038323] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:08:15 192.168.122.209 [39846.078284] [tempesta fw] Tempesta FW is ready Apr 26 03:08:16 192.168.122.209 [39846.656163] [tdb] Close table 'client0.tdb' Apr 26 03:08:16 192.168.122.209 [39846.847729] [tdb] Close table 'sessions0.tdb' Apr 26 03:08:19 192.168.122.209 [39850.041237] [tdb] Close table 'cache0.tdb' Apr 26 03:08:19 192.168.122.209 [39850.285169] [tdb] Close table 'filter0.tdb' Apr 26 03:08:19 192.168.122.209 [39850.285603] [tempesta fw] modules are stopped Apr 26 03:08:20 192.168.122.209 [39850.551062] [tempesta fw] exiting... Apr 26 03:08:20 192.168.122.209 [39850.722854] [tdb] Shutdown Tempesta DB Apr 26 03:08:20 192.168.122.209 [39850.945472] End test: http2_general.test_h2_frame.TestH2Frame.test_rst_stream_with_id_0 Apr 26 03:08:20 192.168.122.209 [39850.955097] Start test: http2_general.test_h2_frame.TestH2Frame.test_settings_frame Apr 26 03:08:21 192.168.122.209 [39852.141102] [tdb] Start Tempesta DB Apr 26 03:08:21 192.168.122.209 [39852.292324] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:08:23 192.168.122.209 [39853.891902] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39853.891902] Maybe that's fine, but it's worth checking the [39853.891902] config - if there is no relations between the [39853.891902] names, then host name confusion attack is possible. Apr 26 03:08:23 192.168.122.209 [39854.066443] [tempesta fw] Configuration processing is completed. Apr 26 03:08:23 192.168.122.209 [39854.152469] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:08:24 192.168.122.209 [39854.590585] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:08:24 192.168.122.209 [39854.628860] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:08:24 192.168.122.209 [39854.656662] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:08:24 192.168.122.209 [39854.698443] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:08:24 192.168.122.209 [39854.746400] [tempesta fw] Tempesta FW is ready Apr 26 03:08:25 192.168.122.209 [39855.330720] [tdb] Close table 'client0.tdb' Apr 26 03:08:25 192.168.122.209 [39855.527455] [tdb] Close table 'sessions0.tdb' Apr 26 03:08:28 192.168.122.209 [39858.672167] [tdb] Close table 'cache0.tdb' Apr 26 03:08:28 192.168.122.209 [39858.919613] [tdb] Close table 'filter0.tdb' Apr 26 03:08:28 192.168.122.209 [39858.920044] [tempesta fw] modules are stopped Apr 26 03:08:28 192.168.122.209 [39859.179536] [tempesta fw] exiting... Apr 26 03:08:29 192.168.122.209 [39859.356522] [tdb] Shutdown Tempesta DB Apr 26 03:08:29 192.168.122.209 [39859.572292] End test: http2_general.test_h2_frame.TestH2Frame.test_settings_frame Apr 26 03:08:29 192.168.122.209 [39859.583418] Start test: http2_general.test_h2_frame.TestH2Frame.test_trailer_header_frame_without_end_stream Apr 26 03:08:30 192.168.122.209 [39860.778801] [tdb] Start Tempesta DB Apr 26 03:08:30 192.168.122.209 [39860.949302] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:08:32 192.168.122.209 [39862.551958] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39862.551958] Maybe that's fine, but it's worth checking the [39862.551958] config - if there is no relations between the [39862.551958] names, then host name confusion attack is possible. Apr 26 03:08:32 192.168.122.209 [39862.702572] [tempesta fw] Configuration processing is completed. Apr 26 03:08:32 192.168.122.209 [39862.751972] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:08:32 192.168.122.209 [39863.187782] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:08:32 192.168.122.209 [39863.215854] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:08:32 192.168.122.209 [39863.243830] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:08:33 192.168.122.209 [39863.310590] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:08:33 192.168.122.209 [39863.358533] [tempesta fw] Tempesta FW is ready Apr 26 03:08:33 192.168.122.209 [39863.950760] [tdb] Close table 'client0.tdb' Apr 26 03:08:33 192.168.122.209 [39864.169319] [tdb] Close table 'sessions0.tdb' Apr 26 03:08:37 192.168.122.209 [39867.364519] [tdb] Close table 'cache0.tdb' Apr 26 03:08:37 192.168.122.209 [39867.627793] [tdb] Close table 'filter0.tdb' Apr 26 03:08:37 192.168.122.209 [39867.628255] [tempesta fw] modules are stopped Apr 26 03:08:37 192.168.122.209 [39867.834848] [tempesta fw] exiting... Apr 26 03:08:37 192.168.122.209 [39868.020964] [tdb] Shutdown Tempesta DB Apr 26 03:08:37 192.168.122.209 [39868.231743] End test: http2_general.test_h2_frame.TestH2Frame.test_trailer_header_frame_without_end_stream Apr 26 03:08:37 192.168.122.209 [39868.254357] Start test: http2_general.test_h2_frame.TestH2Frame.test_window_update_frame Apr 26 03:08:39 192.168.122.209 [39869.439440] [tdb] Start Tempesta DB Apr 26 03:08:39 192.168.122.209 [39869.584930] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:08:40 192.168.122.209 [39871.200061] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39871.200061] Maybe that's fine, but it's worth checking the [39871.200061] config - if there is no relations between the [39871.200061] names, then host name confusion attack is possible. Apr 26 03:08:41 192.168.122.209 [39871.350650] [tempesta fw] Configuration processing is completed. Apr 26 03:08:41 192.168.122.209 [39871.407379] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:08:41 192.168.122.209 [39871.832585] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:08:41 192.168.122.209 [39871.858803] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:08:41 192.168.122.209 [39871.885698] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:08:41 192.168.122.209 [39871.934676] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:08:41 192.168.122.209 [39871.982637] [tempesta fw] Tempesta FW is ready Apr 26 03:08:42 192.168.122.209 [39872.623448] [tdb] Close table 'client0.tdb' Apr 26 03:08:42 192.168.122.209 [39872.819360] [tdb] Close table 'sessions0.tdb' Apr 26 03:08:45 192.168.122.209 [39876.047461] [tdb] Close table 'cache0.tdb' Apr 26 03:08:45 192.168.122.209 [39876.279984] [tdb] Close table 'filter0.tdb' Apr 26 03:08:45 192.168.122.209 [39876.280445] [tempesta fw] modules are stopped Apr 26 03:08:46 192.168.122.209 [39876.571220] [tempesta fw] exiting... Apr 26 03:08:46 192.168.122.209 [39876.712217] [tdb] Shutdown Tempesta DB Apr 26 03:08:46 192.168.122.209 [39876.964029] End test: http2_general.test_h2_frame.TestH2Frame.test_window_update_frame Apr 26 03:08:46 192.168.122.209 [39876.973119] Start test: http2_general.test_h2_frame.TestH2FrameEnabledDisabledTsoGroGso.test_data_frame Apr 26 03:08:47 192.168.122.209 [39878.115089] [tdb] Start Tempesta DB Apr 26 03:08:47 192.168.122.209 [39878.256731] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:08:49 192.168.122.209 [39879.844272] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39879.844272] Maybe that's fine, but it's worth checking the [39879.844272] config - if there is no relations between the [39879.844272] names, then host name confusion attack is possible. Apr 26 03:08:49 192.168.122.209 [39880.006806] [tempesta fw] Configuration processing is completed. Apr 26 03:08:49 192.168.122.209 [39880.061802] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:08:50 192.168.122.209 [39880.514990] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:08:50 192.168.122.209 [39880.544139] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:08:50 192.168.122.209 [39880.574593] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:08:50 192.168.122.209 [39880.618786] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:08:50 192.168.122.209 [39880.658714] [tempesta fw] Tempesta FW is ready Apr 26 03:08:51 192.168.122.209 [39881.825637] [tdb] Close table 'client0.tdb' Apr 26 03:08:51 192.168.122.209 [39882.017655] [tdb] Close table 'sessions0.tdb' Apr 26 03:08:54 192.168.122.209 [39885.260976] [tdb] Close table 'cache0.tdb' Apr 26 03:08:55 192.168.122.209 [39885.498715] [tdb] Close table 'filter0.tdb' Apr 26 03:08:55 192.168.122.209 [39885.499145] [tempesta fw] modules are stopped Apr 26 03:08:55 192.168.122.209 [39885.719332] [tempesta fw] exiting... Apr 26 03:08:55 192.168.122.209 [39885.873495] [tdb] Shutdown Tempesta DB Apr 26 03:08:55 192.168.122.209 [39886.092199] End test: http2_general.test_h2_frame.TestH2FrameEnabledDisabledTsoGroGso.test_data_frame Apr 26 03:08:55 192.168.122.209 [39886.100084] Start test: http2_general.test_h2_frame.TestH2FrameEnabledDisabledTsoGroGso.test_headers_frame_for_local_resp_invalid_req_d Apr 26 03:08:56 192.168.122.209 [39887.260441] [tdb] Start Tempesta DB Apr 26 03:08:57 192.168.122.209 [39887.426633] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:08:58 192.168.122.209 [39889.116336] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39889.116336] Maybe that's fine, but it's worth checking the [39889.116336] config - if there is no relations between the [39889.116336] names, then host name confusion attack is possible. Apr 26 03:08:58 192.168.122.209 [39889.282889] [tempesta fw] Configuration processing is completed. Apr 26 03:08:59 192.168.122.209 [39889.384840] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:08:59 192.168.122.209 [39889.812265] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:08:59 192.168.122.209 [39889.838277] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:08:59 192.168.122.209 [39889.864194] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:08:59 192.168.122.209 [39889.910900] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:08:59 192.168.122.209 [39889.950842] [tempesta fw] Tempesta FW is ready Apr 26 03:08:59 192.168.122.209 [39890.301756] [tempesta fw] Warning: request has been filtered out via http table: 127.0.0.2 Apr 26 03:09:00 192.168.122.209 [39890.858618] [tdb] Close table 'client0.tdb' Apr 26 03:09:00 192.168.122.209 [39891.075029] [tdb] Close table 'sessions0.tdb' Apr 26 03:09:03 192.168.122.209 [39894.252524] [tdb] Close table 'cache0.tdb' Apr 26 03:09:04 192.168.122.209 [39894.489536] [tdb] Close table 'filter0.tdb' Apr 26 03:09:04 192.168.122.209 [39894.489971] [tempesta fw] modules are stopped Apr 26 03:09:04 192.168.122.209 [39894.758358] [tempesta fw] exiting... Apr 26 03:09:04 192.168.122.209 [39894.899603] [tdb] Shutdown Tempesta DB Apr 26 03:09:04 192.168.122.209 [39895.131215] End test: http2_general.test_h2_frame.TestH2FrameEnabledDisabledTsoGroGso.test_headers_frame_for_local_resp_invalid_req_d Apr 26 03:09:04 192.168.122.209 [39895.143468] Start test: http2_general.test_h2_frame.TestH2FrameEnabledDisabledTsoGroGso.test_headers_frame_for_local_resp_invalid_req_e Apr 26 03:09:06 192.168.122.209 [39896.331174] [tdb] Start Tempesta DB Apr 26 03:09:06 192.168.122.209 [39896.476484] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:09:07 192.168.122.209 [39898.128439] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39898.128439] Maybe that's fine, but it's worth checking the [39898.128439] config - if there is no relations between the [39898.128439] names, then host name confusion attack is possible. Apr 26 03:09:07 192.168.122.209 [39898.287040] [tempesta fw] Configuration processing is completed. Apr 26 03:09:08 192.168.122.209 [39898.338059] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:09:08 192.168.122.209 [39898.783364] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:09:08 192.168.122.209 [39898.814540] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:09:08 192.168.122.209 [39898.840249] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:09:08 192.168.122.209 [39898.899006] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:09:08 192.168.122.209 [39898.942961] [tempesta fw] Tempesta FW is ready Apr 26 03:09:08 192.168.122.209 [39899.249277] [tempesta fw] Warning: request has been filtered out via http table: 127.0.0.2 Apr 26 03:09:09 192.168.122.209 [39899.777300] [tdb] Close table 'client0.tdb' Apr 26 03:09:09 192.168.122.209 [39899.964538] [tdb] Close table 'sessions0.tdb' Apr 26 03:09:12 192.168.122.209 [39903.163220] [tdb] Close table 'cache0.tdb' Apr 26 03:09:13 192.168.122.209 [39903.426499] [tdb] Close table 'filter0.tdb' Apr 26 03:09:13 192.168.122.209 [39903.427004] [tempesta fw] modules are stopped Apr 26 03:09:13 192.168.122.209 [39903.654653] [tempesta fw] exiting... Apr 26 03:09:13 192.168.122.209 [39903.813197] [tdb] Shutdown Tempesta DB Apr 26 03:09:13 192.168.122.209 [39904.014978] End test: http2_general.test_h2_frame.TestH2FrameEnabledDisabledTsoGroGso.test_headers_frame_for_local_resp_invalid_req_e Apr 26 03:09:13 192.168.122.209 [39904.031864] Start test: http2_general.test_h2_frame.TestH2FrameEnabledDisabledTsoGroGso.test_headers_frame_with_continuation Apr 26 03:09:14 192.168.122.209 [39905.218709] [tdb] Start Tempesta DB Apr 26 03:09:15 192.168.122.209 [39905.390219] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:09:16 192.168.122.209 [39906.984584] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39906.984584] Maybe that's fine, but it's worth checking the [39906.984584] config - if there is no relations between the [39906.984584] names, then host name confusion attack is possible. Apr 26 03:09:16 192.168.122.209 [39907.135133] [tempesta fw] Configuration processing is completed. Apr 26 03:09:16 192.168.122.209 [39907.187425] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:09:17 192.168.122.209 [39907.607586] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:09:17 192.168.122.209 [39907.635520] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:09:17 192.168.122.209 [39907.664361] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:09:17 192.168.122.209 [39907.711111] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:09:17 192.168.122.209 [39907.755057] [tempesta fw] Tempesta FW is ready Apr 26 03:09:18 192.168.122.209 [39908.805865] [tdb] Close table 'client0.tdb' Apr 26 03:09:18 192.168.122.209 [39909.012115] [tdb] Close table 'sessions0.tdb' Apr 26 03:09:21 192.168.122.209 [39912.157645] [tdb] Close table 'cache0.tdb' Apr 26 03:09:22 192.168.122.209 [39912.395846] [tdb] Close table 'filter0.tdb' Apr 26 03:09:22 192.168.122.209 [39912.396275] [tempesta fw] modules are stopped Apr 26 03:09:22 192.168.122.209 [39912.648906] [tempesta fw] exiting... Apr 26 03:09:22 192.168.122.209 [39912.804288] [tdb] Shutdown Tempesta DB Apr 26 03:09:22 192.168.122.209 [39913.046454] End test: http2_general.test_h2_frame.TestH2FrameEnabledDisabledTsoGroGso.test_headers_frame_with_continuation Apr 26 03:09:22 192.168.122.209 [39913.056395] Start test: http2_general.test_h2_frame.TestH2FrameEnabledDisabledTsoGroGso.test_headers_frame_without_continuation Apr 26 03:09:23 192.168.122.209 [39914.222320] [tdb] Start Tempesta DB Apr 26 03:09:24 192.168.122.209 [39914.368124] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:09:25 192.168.122.209 [39916.016640] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39916.016640] Maybe that's fine, but it's worth checking the [39916.016640] config - if there is no relations between the [39916.016640] names, then host name confusion attack is possible. Apr 26 03:09:25 192.168.122.209 [39916.171234] [tempesta fw] Configuration processing is completed. Apr 26 03:09:25 192.168.122.209 [39916.228318] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:09:26 192.168.122.209 [39916.642338] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:09:26 192.168.122.209 [39916.667931] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:09:26 192.168.122.209 [39916.693263] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:09:26 192.168.122.209 [39916.727164] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:09:26 192.168.122.209 [39916.763187] [tempesta fw] Tempesta FW is ready Apr 26 03:09:27 192.168.122.209 [39917.865669] [tdb] Close table 'client0.tdb' Apr 26 03:09:27 192.168.122.209 [39918.043700] [tdb] Close table 'sessions0.tdb' Apr 26 03:09:30 192.168.122.209 [39921.238035] [tdb] Close table 'cache0.tdb' Apr 26 03:09:31 192.168.122.209 [39921.490452] [tdb] Close table 'filter0.tdb' Apr 26 03:09:31 192.168.122.209 [39921.490882] [tempesta fw] modules are stopped Apr 26 03:09:31 192.168.122.209 [39921.733835] [tempesta fw] exiting... Apr 26 03:09:31 192.168.122.209 [39921.886656] [tdb] Shutdown Tempesta DB Apr 26 03:09:31 192.168.122.209 [39922.083599] End test: http2_general.test_h2_frame.TestH2FrameEnabledDisabledTsoGroGso.test_headers_frame_without_continuation Apr 26 03:09:31 192.168.122.209 [39922.090522] Start test: http2_general.test_h2_frame.TestH2FrameEnabledDisabledTsoGroGso.test_mixed_frames_long_headers_disabled Apr 26 03:09:32 192.168.122.209 [39923.259291] [tdb] Start Tempesta DB Apr 26 03:09:33 192.168.122.209 [39923.412030] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:09:34 192.168.122.209 [39925.040745] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39925.040745] Maybe that's fine, but it's worth checking the [39925.040745] config - if there is no relations between the [39925.040745] names, then host name confusion attack is possible. Apr 26 03:09:34 192.168.122.209 [39925.195655] [tempesta fw] Configuration processing is completed. Apr 26 03:09:34 192.168.122.209 [39925.283851] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:09:35 192.168.122.209 [39925.702486] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:09:35 192.168.122.209 [39925.728307] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:09:35 192.168.122.209 [39925.754051] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:09:35 192.168.122.209 [39925.815346] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:09:35 192.168.122.209 [39925.859295] [tempesta fw] Tempesta FW is ready Apr 26 03:09:36 192.168.122.209 [39926.692219] [tdb] Close table 'client0.tdb' Apr 26 03:09:36 192.168.122.209 [39926.880792] [tdb] Close table 'sessions0.tdb' Apr 26 03:09:39 192.168.122.209 [39929.996299] [tdb] Close table 'cache0.tdb' Apr 26 03:09:39 192.168.122.209 [39930.268789] [tdb] Close table 'filter0.tdb' Apr 26 03:09:39 192.168.122.209 [39930.269219] [tempesta fw] modules are stopped Apr 26 03:09:40 192.168.122.209 [39930.471088] [tempesta fw] exiting... Apr 26 03:09:40 192.168.122.209 [39930.627231] [tdb] Shutdown Tempesta DB Apr 26 03:09:40 192.168.122.209 [39930.862586] End test: http2_general.test_h2_frame.TestH2FrameEnabledDisabledTsoGroGso.test_mixed_frames_long_headers_disabled Apr 26 03:09:40 192.168.122.209 [39930.874573] Start test: http2_general.test_h2_frame.TestH2FrameEnabledDisabledTsoGroGso.test_mixed_frames_long_headers_enabled Apr 26 03:09:41 192.168.122.209 [39932.037117] [tdb] Start Tempesta DB Apr 26 03:09:41 192.168.122.209 [39932.183563] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:09:43 192.168.122.209 [39933.788881] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39933.788881] Maybe that's fine, but it's worth checking the [39933.788881] config - if there is no relations between the [39933.788881] names, then host name confusion attack is possible. Apr 26 03:09:43 192.168.122.209 [39933.939493] [tempesta fw] Configuration processing is completed. Apr 26 03:09:43 192.168.122.209 [39933.989480] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:09:44 192.168.122.209 [39934.401867] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:09:44 192.168.122.209 [39934.427204] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:09:44 192.168.122.209 [39934.452387] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:09:44 192.168.122.209 [39934.499463] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:09:44 192.168.122.209 [39934.547398] [tempesta fw] Tempesta FW is ready Apr 26 03:09:45 192.168.122.209 [39935.422975] [tdb] Close table 'client0.tdb' Apr 26 03:09:45 192.168.122.209 [39935.626733] [tdb] Close table 'sessions0.tdb' Apr 26 03:09:48 192.168.122.209 [39938.755125] [tdb] Close table 'cache0.tdb' Apr 26 03:09:48 192.168.122.209 [39939.007227] [tdb] Close table 'filter0.tdb' Apr 26 03:09:48 192.168.122.209 [39939.007681] [tempesta fw] modules are stopped Apr 26 03:09:48 192.168.122.209 [39939.224609] [tempesta fw] exiting... Apr 26 03:09:49 192.168.122.209 [39939.369650] [tdb] Shutdown Tempesta DB Apr 26 03:09:49 192.168.122.209 [39939.574512] End test: http2_general.test_h2_frame.TestH2FrameEnabledDisabledTsoGroGso.test_mixed_frames_long_headers_enabled Apr 26 03:09:49 192.168.122.209 [39939.586533] Start test: http2_general.test_h2_frame.TestH2FrameEnabledDisabledTsoGroGsoCache.test_headers_frame_for_local_resp_cache_200_long Apr 26 03:09:50 192.168.122.209 [39940.731383] [tdb] Start Tempesta DB Apr 26 03:09:50 192.168.122.209 [39940.878427] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:09:52 192.168.122.209 [39942.544981] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39942.544981] Maybe that's fine, but it's worth checking the [39942.544981] config - if there is no relations between the [39942.544981] names, then host name confusion attack is possible. Apr 26 03:09:52 192.168.122.209 [39942.739563] [tempesta fw] Configuration processing is completed. Apr 26 03:09:52 192.168.122.209 [39942.790165] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:09:52 192.168.122.209 [39943.196676] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:09:52 192.168.122.209 [39943.223322] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:09:52 192.168.122.209 [39943.250762] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:09:52 192.168.122.209 [39943.295578] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:09:53 192.168.122.209 [39943.335534] [tempesta fw] Tempesta FW is ready Apr 26 03:09:54 192.168.122.209 [39944.554556] [tdb] Close table 'client0.tdb' Apr 26 03:09:54 192.168.122.209 [39944.740648] [tdb] Close table 'sessions0.tdb' Apr 26 03:09:57 192.168.122.209 [39947.931464] [tdb] Close table 'cache0.tdb' Apr 26 03:09:57 192.168.122.209 [39948.177714] [tdb] Close table 'filter0.tdb' Apr 26 03:09:57 192.168.122.209 [39948.178149] [tempesta fw] modules are stopped Apr 26 03:09:58 192.168.122.209 [39948.363876] [tempesta fw] exiting... Apr 26 03:09:58 192.168.122.209 [39948.499046] [tdb] Shutdown Tempesta DB Apr 26 03:09:58 192.168.122.209 [39948.723537] End test: http2_general.test_h2_frame.TestH2FrameEnabledDisabledTsoGroGsoCache.test_headers_frame_for_local_resp_cache_200_long Apr 26 03:09:58 192.168.122.209 [39948.735781] Start test: http2_general.test_h2_frame.TestH2FrameEnabledDisabledTsoGroGsoCache.test_headers_frame_for_local_resp_cache_200_short Apr 26 03:09:59 192.168.122.209 [39949.850543] [tdb] Start Tempesta DB Apr 26 03:09:59 192.168.122.209 [39950.002232] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:10:01 192.168.122.209 [39951.645132] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39951.645132] Maybe that's fine, but it's worth checking the [39951.645132] config - if there is no relations between the [39951.645132] names, then host name confusion attack is possible. Apr 26 03:10:01 192.168.122.209 [39951.827720] [tempesta fw] Configuration processing is completed. Apr 26 03:10:01 192.168.122.209 [39951.885427] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:10:01 192.168.122.209 [39952.290070] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:10:02 192.168.122.209 [39952.315501] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:10:02 192.168.122.209 [39952.341539] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:10:02 192.168.122.209 [39952.391705] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:10:02 192.168.122.209 [39952.439595] [tempesta fw] Tempesta FW is ready Apr 26 03:10:03 192.168.122.209 [39953.591739] [tdb] Close table 'client0.tdb' Apr 26 03:10:03 192.168.122.209 [39953.787467] [tdb] Close table 'sessions0.tdb' Apr 26 03:10:06 192.168.122.209 [39956.948557] [tdb] Close table 'cache0.tdb' Apr 26 03:10:06 192.168.122.209 [39957.200474] [tdb] Close table 'filter0.tdb' Apr 26 03:10:06 192.168.122.209 [39957.200912] [tempesta fw] modules are stopped Apr 26 03:10:07 192.168.122.209 [39957.409047] [tempesta fw] exiting... Apr 26 03:10:07 192.168.122.209 [39957.572037] [tdb] Shutdown Tempesta DB Apr 26 03:10:07 192.168.122.209 [39957.771875] End test: http2_general.test_h2_frame.TestH2FrameEnabledDisabledTsoGroGsoCache.test_headers_frame_for_local_resp_cache_200_short Apr 26 03:10:07 192.168.122.209 [39957.783885] Start test: http2_general.test_h2_frame.TestH2FrameEnabledDisabledTsoGroGsoCache.test_headers_frame_for_local_resp_cache_304_long Apr 26 03:10:08 192.168.122.209 [39958.954416] [tdb] Start Tempesta DB Apr 26 03:10:08 192.168.122.209 [39959.096373] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:10:10 192.168.122.209 [39960.765333] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39960.765333] Maybe that's fine, but it's worth checking the [39960.765333] config - if there is no relations between the [39960.765333] names, then host name confusion attack is possible. Apr 26 03:10:10 192.168.122.209 [39960.963804] [tempesta fw] Configuration processing is completed. Apr 26 03:10:10 192.168.122.209 [39961.013502] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:10:11 192.168.122.209 [39961.415449] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:10:11 192.168.122.209 [39961.440549] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:10:11 192.168.122.209 [39961.465716] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:10:11 192.168.122.209 [39961.503748] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:10:11 192.168.122.209 [39961.539752] [tempesta fw] Tempesta FW is ready Apr 26 03:10:12 192.168.122.209 [39962.746911] [tdb] Close table 'client0.tdb' Apr 26 03:10:12 192.168.122.209 [39962.953881] [tdb] Close table 'sessions0.tdb' Apr 26 03:10:15 192.168.122.209 [39966.098927] [tdb] Close table 'cache0.tdb' Apr 26 03:10:16 192.168.122.209 [39966.339928] [tdb] Close table 'filter0.tdb' Apr 26 03:10:16 192.168.122.209 [39966.340383] [tempesta fw] modules are stopped Apr 26 03:10:16 192.168.122.209 [39966.550898] [tempesta fw] exiting... Apr 26 03:10:16 192.168.122.209 [39966.688667] [tdb] Shutdown Tempesta DB Apr 26 03:10:16 192.168.122.209 [39966.893357] End test: http2_general.test_h2_frame.TestH2FrameEnabledDisabledTsoGroGsoCache.test_headers_frame_for_local_resp_cache_304_long Apr 26 03:10:16 192.168.122.209 [39966.916087] Start test: http2_general.test_h2_frame.TestH2FrameEnabledDisabledTsoGroGsoCache.test_headers_frame_for_local_resp_cache_304_short Apr 26 03:10:17 192.168.122.209 [39968.106541] [tdb] Start Tempesta DB Apr 26 03:10:17 192.168.122.209 [39968.262334] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:10:19 192.168.122.209 [39969.901318] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39969.901318] Maybe that's fine, but it's worth checking the [39969.901318] config - if there is no relations between the [39969.901318] names, then host name confusion attack is possible. Apr 26 03:10:19 192.168.122.209 [39970.083911] [tempesta fw] Configuration processing is completed. Apr 26 03:10:19 192.168.122.209 [39970.175558] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:10:20 192.168.122.209 [39970.587703] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:10:20 192.168.122.209 [39970.614248] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:10:20 192.168.122.209 [39970.641061] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:10:20 192.168.122.209 [39970.695925] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:10:20 192.168.122.209 [39970.735835] [tempesta fw] Tempesta FW is ready Apr 26 03:10:21 192.168.122.209 [39971.899185] [tdb] Close table 'client0.tdb' Apr 26 03:10:21 192.168.122.209 [39972.078555] [tdb] Close table 'sessions0.tdb' Apr 26 03:10:24 192.168.122.209 [39975.255445] [tdb] Close table 'cache0.tdb' Apr 26 03:10:25 192.168.122.209 [39975.521601] [tdb] Close table 'filter0.tdb' Apr 26 03:10:25 192.168.122.209 [39975.522043] [tempesta fw] modules are stopped Apr 26 03:10:25 192.168.122.209 [39975.765262] [tempesta fw] exiting... Apr 26 03:10:25 192.168.122.209 [39975.941711] [tdb] Shutdown Tempesta DB Apr 26 03:10:25 192.168.122.209 [39976.156683] End test: http2_general.test_h2_frame.TestH2FrameEnabledDisabledTsoGroGsoCache.test_headers_frame_for_local_resp_cache_304_short Apr 26 03:10:25 192.168.122.209 [39976.168056] Start test: http2_general.test_h2_frame.TestH2FrameEnabledDisabledTsoGroGsoStickyCookie.test_headers_frame_for_local_resp_sticky_cookie_long Apr 26 03:10:27 192.168.122.209 [39977.324020] [tdb] Start Tempesta DB Apr 26 03:10:27 192.168.122.209 [39977.457351] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:10:28 192.168.122.209 [39979.285524] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39979.285524] Maybe that's fine, but it's worth checking the [39979.285524] config - if there is no relations between the [39979.285524] names, then host name confusion attack is possible. Apr 26 03:10:29 192.168.122.209 [39979.464055] [tempesta fw] Configuration processing is completed. Apr 26 03:10:29 192.168.122.209 [39979.513246] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:10:29 192.168.122.209 [39979.925158] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:10:29 192.168.122.209 [39979.950918] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:10:29 192.168.122.209 [39979.978570] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:10:29 192.168.122.209 [39980.020057] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:10:29 192.168.122.209 [39980.059978] [tempesta fw] Tempesta FW is ready Apr 26 03:10:30 192.168.122.209 [39981.205575] [tdb] Close table 'client0.tdb' Apr 26 03:10:31 192.168.122.209 [39981.407302] [tdb] Close table 'sessions0.tdb' Apr 26 03:10:34 192.168.122.209 [39984.559701] [tdb] Close table 'cache0.tdb' Apr 26 03:10:34 192.168.122.209 [39984.807221] [tdb] Close table 'filter0.tdb' Apr 26 03:10:34 192.168.122.209 [39984.807652] [tempesta fw] modules are stopped Apr 26 03:10:34 192.168.122.209 [39985.008004] [tempesta fw] exiting... Apr 26 03:10:34 192.168.122.209 [39985.161058] [tdb] Shutdown Tempesta DB Apr 26 03:10:35 192.168.122.209 [39985.364079] End test: http2_general.test_h2_frame.TestH2FrameEnabledDisabledTsoGroGsoStickyCookie.test_headers_frame_for_local_resp_sticky_cookie_long Apr 26 03:10:35 192.168.122.209 [39985.376475] Start test: http2_general.test_h2_frame.TestH2FrameEnabledDisabledTsoGroGsoStickyCookie.test_headers_frame_for_local_resp_sticky_cookie_short Apr 26 03:10:36 192.168.122.209 [39986.542864] [tdb] Start Tempesta DB Apr 26 03:10:36 192.168.122.209 [39986.701629] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:10:38 192.168.122.209 [39988.517417] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39988.517417] Maybe that's fine, but it's worth checking the [39988.517417] config - if there is no relations between the [39988.517417] names, then host name confusion attack is possible. Apr 26 03:10:38 192.168.122.209 [39988.688162] [tempesta fw] Configuration processing is completed. Apr 26 03:10:38 192.168.122.209 [39988.746093] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:10:38 192.168.122.209 [39989.166232] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:10:38 192.168.122.209 [39989.192223] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:10:38 192.168.122.209 [39989.218398] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:10:38 192.168.122.209 [39989.284102] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:10:39 192.168.122.209 [39989.324139] [tempesta fw] Tempesta FW is ready Apr 26 03:10:40 192.168.122.209 [39990.414131] [tdb] Close table 'client0.tdb' Apr 26 03:10:40 192.168.122.209 [39990.608739] [tdb] Close table 'sessions0.tdb' Apr 26 03:10:43 192.168.122.209 [39993.846737] [tdb] Close table 'cache0.tdb' Apr 26 03:10:43 192.168.122.209 [39994.083797] [tdb] Close table 'filter0.tdb' Apr 26 03:10:43 192.168.122.209 [39994.084258] [tempesta fw] modules are stopped Apr 26 03:10:43 192.168.122.209 [39994.284684] [tempesta fw] exiting... Apr 26 03:10:44 192.168.122.209 [39994.431050] [tdb] Shutdown Tempesta DB Apr 26 03:10:44 192.168.122.209 [39994.678405] End test: http2_general.test_h2_frame.TestH2FrameEnabledDisabledTsoGroGsoStickyCookie.test_headers_frame_for_local_resp_sticky_cookie_short Apr 26 03:10:44 192.168.122.209 [39994.690399] Start test: http2_general.test_h2_frame.TestPostponedFrames.test_headers Apr 26 03:10:45 192.168.122.209 [39995.950942] [tdb] Start Tempesta DB Apr 26 03:10:45 192.168.122.209 [39996.105695] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:10:47 192.168.122.209 [39997.709695] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [39997.709695] Maybe that's fine, but it's worth checking the [39997.709695] config - if there is no relations between the [39997.709695] names, then host name confusion attack is possible. Apr 26 03:10:47 192.168.122.209 [39997.888278] [tempesta fw] Configuration processing is completed. Apr 26 03:10:47 192.168.122.209 [39997.937467] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:10:48 192.168.122.209 [39998.345576] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:10:48 192.168.122.209 [39998.371139] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:10:48 192.168.122.209 [39998.397267] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:10:48 192.168.122.209 [39998.436244] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:10:48 192.168.122.209 [39998.476217] [tempesta fw] Tempesta FW is ready Apr 26 03:10:49 192.168.122.209 [39999.734157] [tdb] Close table 'client0.tdb' Apr 26 03:10:49 192.168.122.209 [39999.925469] [tdb] Close table 'sessions0.tdb' Apr 26 03:10:52 192.168.122.209 [40003.049293] [tdb] Close table 'cache0.tdb' Apr 26 03:10:53 192.168.122.209 [40003.316841] [tdb] Close table 'filter0.tdb' Apr 26 03:10:53 192.168.122.209 [40003.317275] [tempesta fw] modules are stopped Apr 26 03:10:53 192.168.122.209 [40003.575800] [tempesta fw] exiting... Apr 26 03:10:53 192.168.122.209 [40003.755694] [tdb] Shutdown Tempesta DB Apr 26 03:10:53 192.168.122.209 [40003.987777] End test: http2_general.test_h2_frame.TestPostponedFrames.test_headers Apr 26 03:10:53 192.168.122.209 [40004.008579] Start test: http2_general.test_h2_frame.TestPostponedFrames.test_trailers Apr 26 03:10:54 192.168.122.209 [40005.182295] [tdb] Start Tempesta DB Apr 26 03:10:55 192.168.122.209 [40005.319883] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:10:56 192.168.122.209 [40006.997581] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40006.997581] Maybe that's fine, but it's worth checking the [40006.997581] config - if there is no relations between the [40006.997581] names, then host name confusion attack is possible. Apr 26 03:10:56 192.168.122.209 [40007.152393] [tempesta fw] Configuration processing is completed. Apr 26 03:10:56 192.168.122.209 [40007.202428] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:10:57 192.168.122.209 [40007.604231] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:10:57 192.168.122.209 [40007.629600] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:10:57 192.168.122.209 [40007.654636] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:10:57 192.168.122.209 [40007.704363] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:10:57 192.168.122.209 [40007.744332] [tempesta fw] Tempesta FW is ready Apr 26 03:10:58 192.168.122.209 [40009.061210] [tdb] Close table 'client0.tdb' Apr 26 03:10:58 192.168.122.209 [40009.251310] [tdb] Close table 'sessions0.tdb' Apr 26 03:11:02 192.168.122.209 [40012.391818] [tdb] Close table 'cache0.tdb' Apr 26 03:11:02 192.168.122.209 [40012.658066] [tdb] Close table 'filter0.tdb' Apr 26 03:11:02 192.168.122.209 [40012.658511] [tempesta fw] modules are stopped Apr 26 03:11:02 192.168.122.209 [40012.862962] [tempesta fw] exiting... Apr 26 03:11:02 192.168.122.209 [40013.025862] [tdb] Shutdown Tempesta DB Apr 26 03:11:02 192.168.122.209 [40013.209839] End test: http2_general.test_h2_frame.TestPostponedFrames.test_trailers Apr 26 03:11:02 192.168.122.209 [40013.220071] Start test: http2_general.test_h2_headers.AddBackendLongHeaders.test Apr 26 03:11:04 192.168.122.209 [40014.461829] [tdb] Start Tempesta DB Apr 26 03:11:04 192.168.122.209 [40014.610131] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:11:05 192.168.122.209 [40015.994146] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40015.994146] Maybe that's fine, but it's worth checking the [40015.994146] config - if there is no relations between the [40015.994146] names, then host name confusion attack is possible. Apr 26 03:11:05 192.168.122.209 [40016.052502] [tempesta fw] Configuration processing is completed. Apr 26 03:11:05 192.168.122.209 [40016.144095] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:11:06 192.168.122.209 [40016.556875] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:11:06 192.168.122.209 [40016.583410] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:11:06 192.168.122.209 [40016.610315] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:11:06 192.168.122.209 [40016.680499] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:11:06 192.168.122.209 [40016.720461] [tempesta fw] Tempesta FW is ready Apr 26 03:11:07 192.168.122.209 [40017.509339] [tdb] Close table 'client0.tdb' Apr 26 03:11:07 192.168.122.209 [40017.703790] [tdb] Close table 'sessions0.tdb' Apr 26 03:11:10 192.168.122.209 [40020.845789] [tdb] Close table 'cache0.tdb' Apr 26 03:11:10 192.168.122.209 [40021.100837] [tdb] Close table 'filter0.tdb' Apr 26 03:11:10 192.168.122.209 [40021.101296] [tempesta fw] modules are stopped Apr 26 03:11:11 192.168.122.209 [40021.312544] [tempesta fw] exiting... Apr 26 03:11:11 192.168.122.209 [40021.469900] [tdb] Shutdown Tempesta DB Apr 26 03:11:11 192.168.122.209 [40021.709758] End test: http2_general.test_h2_headers.AddBackendLongHeaders.test Apr 26 03:11:11 192.168.122.209 [40021.716247] Start test: http2_general.test_h2_headers.AddBackendLongHeadersCache.test Apr 26 03:11:12 192.168.122.209 [40023.018733] [tdb] Start Tempesta DB Apr 26 03:11:12 192.168.122.209 [40023.161856] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:11:14 192.168.122.209 [40024.606235] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40024.606235] Maybe that's fine, but it's worth checking the [40024.606235] config - if there is no relations between the [40024.606235] names, then host name confusion attack is possible. Apr 26 03:11:14 192.168.122.209 [40024.676610] [tempesta fw] Configuration processing is completed. Apr 26 03:11:14 192.168.122.209 [40024.725635] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:11:14 192.168.122.209 [40025.132111] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:11:14 192.168.122.209 [40025.158044] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:11:14 192.168.122.209 [40025.183304] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:11:14 192.168.122.209 [40025.260621] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:11:14 192.168.122.209 [40025.300559] [tempesta fw] Tempesta FW is ready Apr 26 03:11:15 192.168.122.209 [40026.033594] [tdb] Close table 'client0.tdb' Apr 26 03:11:15 192.168.122.209 [40026.258788] [tdb] Close table 'sessions0.tdb' Apr 26 03:11:19 192.168.122.209 [40029.433314] [tdb] Close table 'cache0.tdb' Apr 26 03:11:19 192.168.122.209 [40029.704274] [tdb] Close table 'filter0.tdb' Apr 26 03:11:19 192.168.122.209 [40029.704726] [tempesta fw] modules are stopped Apr 26 03:11:19 192.168.122.209 [40029.884532] [tempesta fw] exiting... Apr 26 03:11:19 192.168.122.209 [40030.058099] [tdb] Shutdown Tempesta DB Apr 26 03:11:20 192.168.122.209 [40030.325127] End test: http2_general.test_h2_headers.AddBackendLongHeadersCache.test Apr 26 03:11:20 192.168.122.209 [40030.339832] Start test: http2_general.test_h2_headers.AddBackendShortHeaders.test Apr 26 03:11:21 192.168.122.209 [40031.645639] [tdb] Start Tempesta DB Apr 26 03:11:21 192.168.122.209 [40031.781416] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:11:22 192.168.122.209 [40033.190226] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40033.190226] Maybe that's fine, but it's worth checking the [40033.190226] config - if there is no relations between the [40033.190226] names, then host name confusion attack is possible. Apr 26 03:11:22 192.168.122.209 [40033.240773] [tempesta fw] Configuration processing is completed. Apr 26 03:11:22 192.168.122.209 [40033.290678] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:11:23 192.168.122.209 [40033.707414] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:11:23 192.168.122.209 [40033.733214] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:11:23 192.168.122.209 [40033.759018] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:11:23 192.168.122.209 [40033.832782] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:11:23 192.168.122.209 [40033.872692] [tempesta fw] Tempesta FW is ready Apr 26 03:11:24 192.168.122.209 [40034.638178] [tdb] Close table 'client0.tdb' Apr 26 03:11:24 192.168.122.209 [40034.864252] [tdb] Close table 'sessions0.tdb' Apr 26 03:11:27 192.168.122.209 [40038.067548] [tdb] Close table 'cache0.tdb' Apr 26 03:11:28 192.168.122.209 [40038.354426] [tdb] Close table 'filter0.tdb' Apr 26 03:11:28 192.168.122.209 [40038.354852] [tempesta fw] modules are stopped Apr 26 03:11:28 192.168.122.209 [40038.546079] [tempesta fw] exiting... Apr 26 03:11:28 192.168.122.209 [40038.699902] [tdb] Shutdown Tempesta DB Apr 26 03:11:28 192.168.122.209 [40038.941759] End test: http2_general.test_h2_headers.AddBackendShortHeaders.test Apr 26 03:11:28 192.168.122.209 [40038.959412] Start test: http2_general.test_h2_headers.AddBackendShortHeadersCache.test Apr 26 03:11:29 192.168.122.209 [40040.234864] [tdb] Start Tempesta DB Apr 26 03:11:30 192.168.122.209 [40040.393486] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:11:31 192.168.122.209 [40041.762472] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40041.762472] Maybe that's fine, but it's worth checking the [40041.762472] config - if there is no relations between the [40041.762472] names, then host name confusion attack is possible. Apr 26 03:11:31 192.168.122.209 [40041.840840] [tempesta fw] Configuration processing is completed. Apr 26 03:11:31 192.168.122.209 [40041.892764] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:11:32 192.168.122.209 [40042.311681] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:11:32 192.168.122.209 [40042.337374] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:11:32 192.168.122.209 [40042.362425] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:11:32 192.168.122.209 [40042.448897] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:11:32 192.168.122.209 [40042.488776] [tempesta fw] Tempesta FW is ready Apr 26 03:11:32 192.168.122.209 [40043.291219] [tdb] Close table 'client0.tdb' Apr 26 03:11:33 192.168.122.209 [40043.490460] [tdb] Close table 'sessions0.tdb' Apr 26 03:11:36 192.168.122.209 [40046.690093] [tdb] Close table 'cache0.tdb' Apr 26 03:11:36 192.168.122.209 [40046.927209] [tdb] Close table 'filter0.tdb' Apr 26 03:11:36 192.168.122.209 [40046.927666] [tempesta fw] modules are stopped Apr 26 03:11:36 192.168.122.209 [40047.130159] [tempesta fw] exiting... Apr 26 03:11:36 192.168.122.209 [40047.277918] [tdb] Shutdown Tempesta DB Apr 26 03:11:37 192.168.122.209 [40047.513527] End test: http2_general.test_h2_headers.AddBackendShortHeadersCache.test Apr 26 03:11:37 192.168.122.209 [40047.537121] Start test: http2_general.test_h2_headers.BackendSetCoookieH2.test Apr 26 03:11:38 192.168.122.209 [40048.841667] [tdb] Start Tempesta DB Apr 26 03:11:38 192.168.122.209 [40048.986344] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:11:40 192.168.122.209 [40050.398528] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40050.398528] Maybe that's fine, but it's worth checking the [40050.398528] config - if there is no relations between the [40050.398528] names, then host name confusion attack is possible. Apr 26 03:11:40 192.168.122.209 [40050.481290] [tempesta fw] Configuration processing is completed. Apr 26 03:11:40 192.168.122.209 [40050.568542] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:11:40 192.168.122.209 [40050.997932] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:11:40 192.168.122.209 [40051.024813] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:11:40 192.168.122.209 [40051.057650] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:11:40 192.168.122.209 [40051.132964] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:11:40 192.168.122.209 [40051.172902] [tempesta fw] Tempesta FW is ready Apr 26 03:11:41 192.168.122.209 [40052.004300] [tdb] Close table 'client0.tdb' Apr 26 03:11:41 192.168.122.209 [40052.196338] [tdb] Close table 'sessions0.tdb' Apr 26 03:11:45 192.168.122.209 [40055.358652] [tdb] Close table 'cache0.tdb' Apr 26 03:11:45 192.168.122.209 [40055.601230] [tdb] Close table 'filter0.tdb' Apr 26 03:11:45 192.168.122.209 [40055.601660] [tempesta fw] modules are stopped Apr 26 03:11:45 192.168.122.209 [40055.857116] [tempesta fw] exiting... Apr 26 03:11:45 192.168.122.209 [40056.015546] [tdb] Shutdown Tempesta DB Apr 26 03:11:45 192.168.122.209 [40056.267801] End test: http2_general.test_h2_headers.BackendSetCoookieH2.test Apr 26 03:11:45 192.168.122.209 [40056.284460] Start test: http2_general.test_h2_headers.CookieParsingH2.test_duplicate_cookie Apr 26 03:11:47 192.168.122.209 [40057.478980] [tdb] Start Tempesta DB Apr 26 03:11:47 192.168.122.209 [40057.619429] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:11:48 192.168.122.209 [40059.082338] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40059.082338] Maybe that's fine, but it's worth checking the [40059.082338] config - if there is no relations between the [40059.082338] names, then host name confusion attack is possible. Apr 26 03:11:48 192.168.122.209 [40059.217087] [tempesta fw] Configuration processing is completed. Apr 26 03:11:48 192.168.122.209 [40059.268303] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:11:49 192.168.122.209 [40059.677098] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:11:49 192.168.122.209 [40059.702429] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:11:49 192.168.122.209 [40059.727540] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:11:49 192.168.122.209 [40059.805098] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:11:49 192.168.122.209 [40059.806789] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:11:49 192.168.122.209 [40059.853000] [tempesta fw] Tempesta FW is ready Apr 26 03:11:49 192.168.122.209 [40060.017011] [tempesta fw] Warning: Multiple Tempesta sticky cookies found in request: 2 Apr 26 03:11:49 192.168.122.209 [40060.018776] [tempesta fw] Warning: request dropped: internal error in Sticky module: 127.0.0.2 Apr 26 03:11:50 192.168.122.209 [40060.468809] [tdb] Close table 'client0.tdb' Apr 26 03:11:50 192.168.122.209 [40060.663363] [tdb] Close table 'sessions0.tdb' Apr 26 03:11:53 192.168.122.209 [40063.852788] [tdb] Close table 'cache0.tdb' Apr 26 03:11:53 192.168.122.209 [40064.115422] [tdb] Close table 'filter0.tdb' Apr 26 03:11:53 192.168.122.209 [40064.115860] [tempesta fw] modules are stopped Apr 26 03:11:53 192.168.122.209 [40064.282304] [tempesta fw] exiting... Apr 26 03:11:54 192.168.122.209 [40064.430752] [tdb] Shutdown Tempesta DB Apr 26 03:11:54 192.168.122.209 [40064.681598] End test: http2_general.test_h2_headers.CookieParsingH2.test_duplicate_cookie Apr 26 03:11:54 192.168.122.209 [40064.697218] Start test: http2_general.test_h2_headers.CookieParsingH2.test_many_cookie_and_name_as_substring_other_name_1 Apr 26 03:11:55 192.168.122.209 [40065.831568] [tdb] Start Tempesta DB Apr 26 03:11:55 192.168.122.209 [40065.979832] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:11:57 192.168.122.209 [40067.538066] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40067.538066] Maybe that's fine, but it's worth checking the [40067.538066] config - if there is no relations between the [40067.538066] names, then host name confusion attack is possible. Apr 26 03:11:57 192.168.122.209 [40067.685206] [tempesta fw] Configuration processing is completed. Apr 26 03:11:57 192.168.122.209 [40067.734646] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:11:57 192.168.122.209 [40068.137763] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:11:57 192.168.122.209 [40068.163007] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:11:57 192.168.122.209 [40068.188064] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:11:57 192.168.122.209 [40068.245189] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:11:57 192.168.122.209 [40068.246877] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:11:57 192.168.122.209 [40068.289121] [tempesta fw] Tempesta FW is ready Apr 26 03:11:58 192.168.122.209 [40068.900295] [tdb] Close table 'client0.tdb' Apr 26 03:11:58 192.168.122.209 [40069.096096] [tdb] Close table 'sessions0.tdb' Apr 26 03:12:01 192.168.122.209 [40072.239808] [tdb] Close table 'cache0.tdb' Apr 26 03:12:02 192.168.122.209 [40072.480926] [tdb] Close table 'filter0.tdb' Apr 26 03:12:02 192.168.122.209 [40072.481363] [tempesta fw] modules are stopped Apr 26 03:12:02 192.168.122.209 [40072.706527] [tempesta fw] exiting... Apr 26 03:12:02 192.168.122.209 [40072.889841] [tdb] Shutdown Tempesta DB Apr 26 03:12:02 192.168.122.209 [40073.088958] End test: http2_general.test_h2_headers.CookieParsingH2.test_many_cookie_and_name_as_substring_other_name_1 Apr 26 03:12:02 192.168.122.209 [40073.096559] Start test: http2_general.test_h2_headers.CookieParsingH2.test_many_cookie_and_name_as_substring_other_name_2 Apr 26 03:12:03 192.168.122.209 [40074.260529] [tdb] Start Tempesta DB Apr 26 03:12:04 192.168.122.209 [40074.406177] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:12:05 192.168.122.209 [40075.930958] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40075.930958] Maybe that's fine, but it's worth checking the [40075.930958] config - if there is no relations between the [40075.930958] names, then host name confusion attack is possible. Apr 26 03:12:05 192.168.122.209 [40076.065314] [tempesta fw] Configuration processing is completed. Apr 26 03:12:05 192.168.122.209 [40076.155112] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:12:06 192.168.122.209 [40076.570830] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:12:06 192.168.122.209 [40076.597253] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:12:06 192.168.122.209 [40076.632517] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:12:06 192.168.122.209 [40076.677279] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:12:06 192.168.122.209 [40076.678947] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:12:06 192.168.122.209 [40076.725215] [tempesta fw] Tempesta FW is ready Apr 26 03:12:06 192.168.122.209 [40077.305355] [tdb] Close table 'client0.tdb' Apr 26 03:12:07 192.168.122.209 [40077.521039] [tdb] Close table 'sessions0.tdb' Apr 26 03:12:10 192.168.122.209 [40080.697362] [tdb] Close table 'cache0.tdb' Apr 26 03:12:10 192.168.122.209 [40080.951429] [tdb] Close table 'filter0.tdb' Apr 26 03:12:10 192.168.122.209 [40080.951862] [tempesta fw] modules are stopped Apr 26 03:12:10 192.168.122.209 [40081.178627] [tempesta fw] exiting... Apr 26 03:12:11 192.168.122.209 [40081.323038] [tdb] Shutdown Tempesta DB Apr 26 03:12:11 192.168.122.209 [40081.529410] End test: http2_general.test_h2_headers.CookieParsingH2.test_many_cookie_and_name_as_substring_other_name_2 Apr 26 03:12:11 192.168.122.209 [40081.543417] Start test: http2_general.test_h2_headers.CookieParsingH2.test_many_cookie_and_name_as_substring_other_value_1 Apr 26 03:12:12 192.168.122.209 [40082.767673] [tdb] Start Tempesta DB Apr 26 03:12:12 192.168.122.209 [40082.915986] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:12:14 192.168.122.209 [40084.462685] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40084.462685] Maybe that's fine, but it's worth checking the [40084.462685] config - if there is no relations between the [40084.462685] names, then host name confusion attack is possible. Apr 26 03:12:14 192.168.122.209 [40084.617327] [tempesta fw] Configuration processing is completed. Apr 26 03:12:14 192.168.122.209 [40084.667064] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:12:14 192.168.122.209 [40085.071737] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:12:14 192.168.122.209 [40085.097291] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:12:14 192.168.122.209 [40085.122275] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:12:14 192.168.122.209 [40085.173400] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:12:14 192.168.122.209 [40085.175080] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:12:14 192.168.122.209 [40085.217335] [tempesta fw] Tempesta FW is ready Apr 26 03:12:15 192.168.122.209 [40085.833297] [tdb] Close table 'client0.tdb' Apr 26 03:12:15 192.168.122.209 [40086.043073] [tdb] Close table 'sessions0.tdb' Apr 26 03:12:18 192.168.122.209 [40089.207966] [tdb] Close table 'cache0.tdb' Apr 26 03:12:19 192.168.122.209 [40089.461285] [tdb] Close table 'filter0.tdb' Apr 26 03:12:19 192.168.122.209 [40089.461721] [tempesta fw] modules are stopped Apr 26 03:12:19 192.168.122.209 [40089.708277] [tempesta fw] exiting... Apr 26 03:12:19 192.168.122.209 [40089.855981] [tdb] Shutdown Tempesta DB Apr 26 03:12:19 192.168.122.209 [40090.047355] End test: http2_general.test_h2_headers.CookieParsingH2.test_many_cookie_and_name_as_substring_other_value_1 Apr 26 03:12:19 192.168.122.209 [40090.060841] Start test: http2_general.test_h2_headers.CookieParsingH2.test_many_cookie_and_name_as_substring_other_value_2 Apr 26 03:12:20 192.168.122.209 [40091.171294] [tdb] Start Tempesta DB Apr 26 03:12:21 192.168.122.209 [40091.310503] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:12:22 192.168.122.209 [40092.811133] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40092.811133] Maybe that's fine, but it's worth checking the [40092.811133] config - if there is no relations between the [40092.811133] names, then host name confusion attack is possible. Apr 26 03:12:22 192.168.122.209 [40092.953529] [tempesta fw] Configuration processing is completed. Apr 26 03:12:22 192.168.122.209 [40093.003161] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:12:23 192.168.122.209 [40093.409807] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:12:23 192.168.122.209 [40093.436792] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:12:23 192.168.122.209 [40093.462077] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:12:23 192.168.122.209 [40093.533511] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:12:23 192.168.122.209 [40093.535184] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:12:23 192.168.122.209 [40093.589431] [tempesta fw] Tempesta FW is ready Apr 26 03:12:23 192.168.122.209 [40094.188294] [tdb] Close table 'client0.tdb' Apr 26 03:12:24 192.168.122.209 [40094.389561] [tdb] Close table 'sessions0.tdb' Apr 26 03:12:27 192.168.122.209 [40097.520055] [tdb] Close table 'cache0.tdb' Apr 26 03:12:27 192.168.122.209 [40097.771825] [tdb] Close table 'filter0.tdb' Apr 26 03:12:27 192.168.122.209 [40097.772277] [tempesta fw] modules are stopped Apr 26 03:12:27 192.168.122.209 [40097.962954] [tempesta fw] exiting... Apr 26 03:12:27 192.168.122.209 [40098.121321] [tdb] Shutdown Tempesta DB Apr 26 03:12:28 192.168.122.209 [40098.325706] End test: http2_general.test_h2_headers.CookieParsingH2.test_many_cookie_and_name_as_substring_other_value_2 Apr 26 03:12:28 192.168.122.209 [40098.351079] Start test: http2_general.test_h2_headers.CookieParsingH2.test_many_cookie_between Apr 26 03:12:29 192.168.122.209 [40099.523926] [tdb] Start Tempesta DB Apr 26 03:12:29 192.168.122.209 [40099.677592] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:12:30 192.168.122.209 [40101.134869] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40101.134869] Maybe that's fine, but it's worth checking the [40101.134869] config - if there is no relations between the [40101.134869] names, then host name confusion attack is possible. Apr 26 03:12:30 192.168.122.209 [40101.262868] [tempesta fw] Configuration processing is completed. Apr 26 03:12:31 192.168.122.209 [40101.350337] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:12:31 192.168.122.209 [40101.768499] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:12:31 192.168.122.209 [40101.795349] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:12:31 192.168.122.209 [40101.822955] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:12:31 192.168.122.209 [40101.874890] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:12:31 192.168.122.209 [40101.876560] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:12:31 192.168.122.209 [40101.913541] [tempesta fw] Tempesta FW is ready Apr 26 03:12:32 192.168.122.209 [40102.553085] [tdb] Close table 'client0.tdb' Apr 26 03:12:32 192.168.122.209 [40102.748653] [tdb] Close table 'sessions0.tdb' Apr 26 03:12:35 192.168.122.209 [40105.895335] [tdb] Close table 'cache0.tdb' Apr 26 03:12:35 192.168.122.209 [40106.134016] [tdb] Close table 'filter0.tdb' Apr 26 03:12:35 192.168.122.209 [40106.134461] [tempesta fw] modules are stopped Apr 26 03:12:36 192.168.122.209 [40106.368482] [tempesta fw] exiting... Apr 26 03:12:36 192.168.122.209 [40106.528523] [tdb] Shutdown Tempesta DB Apr 26 03:12:36 192.168.122.209 [40106.742498] End test: http2_general.test_h2_headers.CookieParsingH2.test_many_cookie_between Apr 26 03:12:36 192.168.122.209 [40106.766890] Start test: http2_general.test_h2_headers.CookieParsingH2.test_many_cookie_first Apr 26 03:12:37 192.168.122.209 [40107.919554] [tdb] Start Tempesta DB Apr 26 03:12:37 192.168.122.209 [40108.073065] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:12:39 192.168.122.209 [40109.594998] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40109.594998] Maybe that's fine, but it's worth checking the [40109.594998] config - if there is no relations between the [40109.594998] names, then host name confusion attack is possible. Apr 26 03:12:39 192.168.122.209 [40109.753720] [tempesta fw] Configuration processing is completed. Apr 26 03:12:39 192.168.122.209 [40109.807123] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:12:39 192.168.122.209 [40110.218425] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:12:39 192.168.122.209 [40110.243736] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:12:39 192.168.122.209 [40110.268604] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:12:40 192.168.122.209 [40110.321713] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:12:40 192.168.122.209 [40110.323426] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:12:40 192.168.122.209 [40110.361671] [tempesta fw] Tempesta FW is ready Apr 26 03:12:40 192.168.122.209 [40110.970105] [tdb] Close table 'client0.tdb' Apr 26 03:12:40 192.168.122.209 [40111.170007] [tdb] Close table 'sessions0.tdb' Apr 26 03:12:44 192.168.122.209 [40114.336333] [tdb] Close table 'cache0.tdb' Apr 26 03:12:44 192.168.122.209 [40114.602620] [tdb] Close table 'filter0.tdb' Apr 26 03:12:44 192.168.122.209 [40114.603055] [tempesta fw] modules are stopped Apr 26 03:12:44 192.168.122.209 [40114.798578] [tempesta fw] exiting... Apr 26 03:12:44 192.168.122.209 [40114.959930] [tdb] Shutdown Tempesta DB Apr 26 03:12:45 192.168.122.209 [40115.469260] End test: http2_general.test_h2_headers.CookieParsingH2.test_many_cookie_first Apr 26 03:12:45 192.168.122.209 [40115.482154] Start test: http2_general.test_h2_headers.CookieParsingH2.test_many_cookie_last Apr 26 03:12:46 192.168.122.209 [40117.039903] [tdb] Start Tempesta DB Apr 26 03:12:46 192.168.122.209 [40117.212319] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:12:49 192.168.122.209 [40119.399869] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40119.399869] Maybe that's fine, but it's worth checking the [40119.399869] config - if there is no relations between the [40119.399869] names, then host name confusion attack is possible. Apr 26 03:12:50 192.168.122.209 [40120.639801] [tempesta fw] Configuration processing is completed. Apr 26 03:12:50 192.168.122.209 [40120.826653] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:12:51 192.168.122.209 [40121.559437] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:12:51 192.168.122.209 [40121.594813] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:12:51 192.168.122.209 [40121.621609] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:12:51 192.168.122.209 [40121.925850] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:12:51 192.168.122.209 [40121.927621] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:12:51 192.168.122.209 [40121.965801] [tempesta fw] Tempesta FW is ready Apr 26 03:12:52 192.168.122.209 [40122.544157] [tdb] Close table 'client0.tdb' Apr 26 03:12:52 192.168.122.209 [40122.748634] [tdb] Close table 'sessions0.tdb' Apr 26 03:12:55 192.168.122.209 [40125.946222] [tdb] Close table 'cache0.tdb' Apr 26 03:12:55 192.168.122.209 [40126.184737] [tdb] Close table 'filter0.tdb' Apr 26 03:12:55 192.168.122.209 [40126.185176] [tempesta fw] modules are stopped Apr 26 03:12:56 192.168.122.209 [40126.376449] [tempesta fw] exiting... Apr 26 03:12:56 192.168.122.209 [40126.537409] [tdb] Shutdown Tempesta DB Apr 26 03:12:56 192.168.122.209 [40126.727001] End test: http2_general.test_h2_headers.CookieParsingH2.test_many_cookie_last Apr 26 03:12:56 192.168.122.209 [40126.738084] Start test: http2_general.test_h2_headers.CookieParsingH2.test_single_cookie Apr 26 03:12:57 192.168.122.209 [40127.892723] [tdb] Start Tempesta DB Apr 26 03:12:57 192.168.122.209 [40128.044082] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:12:59 192.168.122.209 [40129.506682] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40129.506682] Maybe that's fine, but it's worth checking the [40129.506682] config - if there is no relations between the [40129.506682] names, then host name confusion attack is possible. Apr 26 03:12:59 192.168.122.209 [40129.641905] [tempesta fw] Configuration processing is completed. Apr 26 03:12:59 192.168.122.209 [40129.687075] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:12:59 192.168.122.209 [40130.105650] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:12:59 192.168.122.209 [40130.131637] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:12:59 192.168.122.209 [40130.157289] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:12:59 192.168.122.209 [40130.201902] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:12:59 192.168.122.209 [40130.203106] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:12:59 192.168.122.209 [40130.241939] [tempesta fw] Tempesta FW is ready Apr 26 03:13:00 192.168.122.209 [40130.894746] [tdb] Close table 'client0.tdb' Apr 26 03:13:00 192.168.122.209 [40131.081595] [tdb] Close table 'sessions0.tdb' Apr 26 03:13:03 192.168.122.209 [40134.244806] [tdb] Close table 'cache0.tdb' Apr 26 03:13:04 192.168.122.209 [40134.468330] [tdb] Close table 'filter0.tdb' Apr 26 03:13:04 192.168.122.209 [40134.468762] [tempesta fw] modules are stopped Apr 26 03:13:04 192.168.122.209 [40134.648382] [tempesta fw] exiting... Apr 26 03:13:04 192.168.122.209 [40134.799978] [tdb] Shutdown Tempesta DB Apr 26 03:13:04 192.168.122.209 [40134.996312] End test: http2_general.test_h2_headers.CookieParsingH2.test_single_cookie Apr 26 03:13:04 192.168.122.209 [40135.004131] Start test: http2_general.test_h2_headers.CookieParsingHttp.test_duplicate_cookie Apr 26 03:13:05 192.168.122.209 [40136.145875] [tdb] Start Tempesta DB Apr 26 03:13:05 192.168.122.209 [40136.293017] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:13:07 192.168.122.209 [40137.762689] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40137.762689] Maybe that's fine, but it's worth checking the [40137.762689] config - if there is no relations between the [40137.762689] names, then host name confusion attack is possible. Apr 26 03:13:07 192.168.122.209 [40137.886289] [tempesta fw] Configuration processing is completed. Apr 26 03:13:07 192.168.122.209 [40137.937951] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:13:08 192.168.122.209 [40138.339609] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:13:08 192.168.122.209 [40138.365205] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:13:08 192.168.122.209 [40138.390163] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:13:08 192.168.122.209 [40138.437974] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:13:08 192.168.122.209 [40138.439362] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:13:08 192.168.122.209 [40138.482003] [tempesta fw] Tempesta FW is ready Apr 26 03:13:08 192.168.122.209 [40138.648484] [tempesta fw] Warning: Multiple Tempesta sticky cookies found in request: 2 Apr 26 03:13:08 192.168.122.209 [40138.650743] [tempesta fw] Warning: request dropped: internal error in Sticky module: 127.0.0.2 Apr 26 03:13:08 192.168.122.209 [40139.093633] [tdb] Close table 'client0.tdb' Apr 26 03:13:08 192.168.122.209 [40139.304546] [tdb] Close table 'sessions0.tdb' Apr 26 03:13:12 192.168.122.209 [40142.463374] [tdb] Close table 'cache0.tdb' Apr 26 03:13:12 192.168.122.209 [40142.698705] [tdb] Close table 'filter0.tdb' Apr 26 03:13:12 192.168.122.209 [40142.699146] [tempesta fw] modules are stopped Apr 26 03:13:12 192.168.122.209 [40142.908666] [tempesta fw] exiting... Apr 26 03:13:12 192.168.122.209 [40143.060758] [tdb] Shutdown Tempesta DB Apr 26 03:13:12 192.168.122.209 [40143.274126] End test: http2_general.test_h2_headers.CookieParsingHttp.test_duplicate_cookie Apr 26 03:13:12 192.168.122.209 [40143.295665] Start test: http2_general.test_h2_headers.CookieParsingHttp.test_many_cookie_and_name_as_substring_other_name_1 Apr 26 03:13:14 192.168.122.209 [40144.458727] [tdb] Start Tempesta DB Apr 26 03:13:14 192.168.122.209 [40144.599116] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:13:15 192.168.122.209 [40146.153386] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40146.153386] Maybe that's fine, but it's worth checking the [40146.153386] config - if there is no relations between the [40146.153386] names, then host name confusion attack is possible. Apr 26 03:13:15 192.168.122.209 [40146.278229] [tempesta fw] Configuration processing is completed. Apr 26 03:13:16 192.168.122.209 [40146.329267] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:13:16 192.168.122.209 [40146.754260] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:13:16 192.168.122.209 [40146.780706] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:13:16 192.168.122.209 [40146.806823] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:13:16 192.168.122.209 [40146.854162] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:13:16 192.168.122.209 [40146.855648] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:13:16 192.168.122.209 [40146.898112] [tempesta fw] Tempesta FW is ready Apr 26 03:13:17 192.168.122.209 [40147.528572] [tdb] Close table 'client0.tdb' Apr 26 03:13:17 192.168.122.209 [40147.730164] [tdb] Close table 'sessions0.tdb' Apr 26 03:13:20 192.168.122.209 [40150.892871] [tdb] Close table 'cache0.tdb' Apr 26 03:13:20 192.168.122.209 [40151.141382] [tdb] Close table 'filter0.tdb' Apr 26 03:13:20 192.168.122.209 [40151.141838] [tempesta fw] modules are stopped Apr 26 03:13:21 192.168.122.209 [40151.362844] [tempesta fw] exiting... Apr 26 03:13:21 192.168.122.209 [40151.520804] [tdb] Shutdown Tempesta DB Apr 26 03:13:21 192.168.122.209 [40151.732634] End test: http2_general.test_h2_headers.CookieParsingHttp.test_many_cookie_and_name_as_substring_other_name_1 Apr 26 03:13:21 192.168.122.209 [40151.751267] Start test: http2_general.test_h2_headers.CookieParsingHttp.test_many_cookie_and_name_as_substring_other_name_2 Apr 26 03:13:22 192.168.122.209 [40152.907526] [tdb] Start Tempesta DB Apr 26 03:13:22 192.168.122.209 [40153.043343] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:13:24 192.168.122.209 [40154.583549] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40154.583549] Maybe that's fine, but it's worth checking the [40154.583549] config - if there is no relations between the [40154.583549] names, then host name confusion attack is possible. Apr 26 03:13:24 192.168.122.209 [40154.722286] [tempesta fw] Configuration processing is completed. Apr 26 03:13:24 192.168.122.209 [40154.772732] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:13:24 192.168.122.209 [40155.173888] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:13:24 192.168.122.209 [40155.207673] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:13:24 192.168.122.209 [40155.232590] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:13:24 192.168.122.209 [40155.290267] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:13:24 192.168.122.209 [40155.291990] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:13:25 192.168.122.209 [40155.338239] [tempesta fw] Tempesta FW is ready Apr 26 03:13:25 192.168.122.209 [40155.947429] [tdb] Close table 'client0.tdb' Apr 26 03:13:25 192.168.122.209 [40156.124193] [tdb] Close table 'sessions0.tdb' Apr 26 03:13:29 192.168.122.209 [40159.329594] [tdb] Close table 'cache0.tdb' Apr 26 03:13:29 192.168.122.209 [40159.571143] [tdb] Close table 'filter0.tdb' Apr 26 03:13:29 192.168.122.209 [40159.571575] [tempesta fw] modules are stopped Apr 26 03:13:29 192.168.122.209 [40159.760608] [tempesta fw] exiting... Apr 26 03:13:29 192.168.122.209 [40159.915947] [tdb] Shutdown Tempesta DB Apr 26 03:13:29 192.168.122.209 [40160.116222] End test: http2_general.test_h2_headers.CookieParsingHttp.test_many_cookie_and_name_as_substring_other_name_2 Apr 26 03:13:29 192.168.122.209 [40160.128982] Start test: http2_general.test_h2_headers.CookieParsingHttp.test_many_cookie_and_name_as_substring_other_value_1 Apr 26 03:13:30 192.168.122.209 [40161.267623] [tdb] Start Tempesta DB Apr 26 03:13:31 192.168.122.209 [40161.436150] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:13:32 192.168.122.209 [40162.867661] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40162.867661] Maybe that's fine, but it's worth checking the [40162.867661] config - if there is no relations between the [40162.867661] names, then host name confusion attack is possible. Apr 26 03:13:32 192.168.122.209 [40163.006369] [tempesta fw] Configuration processing is completed. Apr 26 03:13:32 192.168.122.209 [40163.096307] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:13:33 192.168.122.209 [40163.545468] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:13:33 192.168.122.209 [40163.573731] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:13:33 192.168.122.209 [40163.603066] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:13:33 192.168.122.209 [40163.642339] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:13:33 192.168.122.209 [40163.644044] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:13:33 192.168.122.209 [40163.698375] [tempesta fw] Tempesta FW is ready Apr 26 03:13:33 192.168.122.209 [40164.308148] [tdb] Close table 'client0.tdb' Apr 26 03:13:34 192.168.122.209 [40164.516958] [tdb] Close table 'sessions0.tdb' Apr 26 03:13:37 192.168.122.209 [40167.739993] [tdb] Close table 'cache0.tdb' Apr 26 03:13:37 192.168.122.209 [40167.987351] [tdb] Close table 'filter0.tdb' Apr 26 03:13:37 192.168.122.209 [40167.988334] [tempesta fw] modules are stopped Apr 26 03:13:37 192.168.122.209 [40168.235416] [tempesta fw] exiting... Apr 26 03:13:38 192.168.122.209 [40168.395316] [tdb] Shutdown Tempesta DB Apr 26 03:13:38 192.168.122.209 [40168.619550] End test: http2_general.test_h2_headers.CookieParsingHttp.test_many_cookie_and_name_as_substring_other_value_1 Apr 26 03:13:38 192.168.122.209 [40168.629896] Start test: http2_general.test_h2_headers.CookieParsingHttp.test_many_cookie_and_name_as_substring_other_value_2 Apr 26 03:13:39 192.168.122.209 [40169.834761] [tdb] Start Tempesta DB Apr 26 03:13:39 192.168.122.209 [40169.997142] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:13:41 192.168.122.209 [40171.451722] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40171.451722] Maybe that's fine, but it's worth checking the [40171.451722] config - if there is no relations between the [40171.451722] names, then host name confusion attack is possible. Apr 26 03:13:41 192.168.122.209 [40171.622501] [tempesta fw] Configuration processing is completed. Apr 26 03:13:41 192.168.122.209 [40171.672001] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:13:41 192.168.122.209 [40172.092796] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:13:41 192.168.122.209 [40172.119083] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:13:41 192.168.122.209 [40172.144947] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:13:41 192.168.122.209 [40172.198421] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:13:41 192.168.122.209 [40172.200121] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:13:41 192.168.122.209 [40172.238456] [tempesta fw] Tempesta FW is ready Apr 26 03:13:42 192.168.122.209 [40172.842125] [tdb] Close table 'client0.tdb' Apr 26 03:13:42 192.168.122.209 [40173.029939] [tdb] Close table 'sessions0.tdb' Apr 26 03:13:45 192.168.122.209 [40176.205240] [tdb] Close table 'cache0.tdb' Apr 26 03:13:46 192.168.122.209 [40176.459107] [tdb] Close table 'filter0.tdb' Apr 26 03:13:46 192.168.122.209 [40176.459557] [tempesta fw] modules are stopped Apr 26 03:13:46 192.168.122.209 [40176.649129] [tempesta fw] exiting... Apr 26 03:13:46 192.168.122.209 [40176.774252] [tdb] Shutdown Tempesta DB Apr 26 03:13:46 192.168.122.209 [40176.979919] End test: http2_general.test_h2_headers.CookieParsingHttp.test_many_cookie_and_name_as_substring_other_value_2 Apr 26 03:13:46 192.168.122.209 [40176.993395] Start test: http2_general.test_h2_headers.CookieParsingHttp.test_many_cookie_between Apr 26 03:13:47 192.168.122.209 [40178.195682] [tdb] Start Tempesta DB Apr 26 03:13:48 192.168.122.209 [40178.342921] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:13:49 192.168.122.209 [40179.915991] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40179.915991] Maybe that's fine, but it's worth checking the [40179.915991] config - if there is no relations between the [40179.915991] names, then host name confusion attack is possible. Apr 26 03:13:49 192.168.122.209 [40180.054657] [tempesta fw] Configuration processing is completed. Apr 26 03:13:49 192.168.122.209 [40180.106732] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:13:50 192.168.122.209 [40180.566196] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:13:50 192.168.122.209 [40180.594629] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:13:50 192.168.122.209 [40180.623562] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:13:50 192.168.122.209 [40180.678596] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:13:50 192.168.122.209 [40180.680312] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:13:50 192.168.122.209 [40180.718563] [tempesta fw] Tempesta FW is ready Apr 26 03:13:51 192.168.122.209 [40181.316634] [tdb] Close table 'client0.tdb' Apr 26 03:13:51 192.168.122.209 [40181.526017] [tdb] Close table 'sessions0.tdb' Apr 26 03:13:54 192.168.122.209 [40184.813571] [tdb] Close table 'cache0.tdb' Apr 26 03:13:54 192.168.122.209 [40185.059390] [tdb] Close table 'filter0.tdb' Apr 26 03:13:54 192.168.122.209 [40185.059832] [tempesta fw] modules are stopped Apr 26 03:13:54 192.168.122.209 [40185.229936] [tempesta fw] exiting... Apr 26 03:13:55 192.168.122.209 [40185.431891] [tdb] Shutdown Tempesta DB Apr 26 03:13:55 192.168.122.209 [40185.643901] End test: http2_general.test_h2_headers.CookieParsingHttp.test_many_cookie_between Apr 26 03:13:55 192.168.122.209 [40185.653316] Start test: http2_general.test_h2_headers.CookieParsingHttp.test_many_cookie_first Apr 26 03:13:56 192.168.122.209 [40186.867752] [tdb] Start Tempesta DB Apr 26 03:13:56 192.168.122.209 [40187.028532] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:13:58 192.168.122.209 [40188.519888] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40188.519888] Maybe that's fine, but it's worth checking the [40188.519888] config - if there is no relations between the [40188.519888] names, then host name confusion attack is possible. Apr 26 03:13:58 192.168.122.209 [40188.654801] [tempesta fw] Configuration processing is completed. Apr 26 03:13:58 192.168.122.209 [40188.740901] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:13:58 192.168.122.209 [40189.199075] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:13:58 192.168.122.209 [40189.230406] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:13:58 192.168.122.209 [40189.265783] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:13:59 192.168.122.209 [40189.338728] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:13:59 192.168.122.209 [40189.340472] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:13:59 192.168.122.209 [40189.378655] [tempesta fw] Tempesta FW is ready Apr 26 03:13:59 192.168.122.209 [40189.934531] [tdb] Close table 'client0.tdb' Apr 26 03:13:59 192.168.122.209 [40190.153014] [tdb] Close table 'sessions0.tdb' Apr 26 03:14:03 192.168.122.209 [40193.385708] [tdb] Close table 'cache0.tdb' Apr 26 03:14:03 192.168.122.209 [40193.618097] [tdb] Close table 'filter0.tdb' Apr 26 03:14:03 192.168.122.209 [40193.618532] [tempesta fw] modules are stopped Apr 26 03:14:03 192.168.122.209 [40193.908680] [tempesta fw] exiting... Apr 26 03:14:03 192.168.122.209 [40194.032797] [tdb] Shutdown Tempesta DB Apr 26 03:14:03 192.168.122.209 [40194.248645] End test: http2_general.test_h2_headers.CookieParsingHttp.test_many_cookie_first Apr 26 03:14:03 192.168.122.209 [40194.255890] Start test: http2_general.test_h2_headers.CookieParsingHttp.test_many_cookie_last Apr 26 03:14:05 192.168.122.209 [40195.412675] [tdb] Start Tempesta DB Apr 26 03:14:05 192.168.122.209 [40195.563853] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:14:06 192.168.122.209 [40197.056082] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40197.056082] Maybe that's fine, but it's worth checking the [40197.056082] config - if there is no relations between the [40197.056082] names, then host name confusion attack is possible. Apr 26 03:14:06 192.168.122.209 [40197.190858] [tempesta fw] Configuration processing is completed. Apr 26 03:14:06 192.168.122.209 [40197.240625] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:14:07 192.168.122.209 [40197.662827] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:14:07 192.168.122.209 [40197.698247] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:14:07 192.168.122.209 [40197.724567] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:14:07 192.168.122.209 [40197.778830] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:14:07 192.168.122.209 [40197.780558] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:14:07 192.168.122.209 [40197.822764] [tempesta fw] Tempesta FW is ready Apr 26 03:14:08 192.168.122.209 [40198.473179] [tdb] Close table 'client0.tdb' Apr 26 03:14:08 192.168.122.209 [40198.680429] [tdb] Close table 'sessions0.tdb' Apr 26 03:14:11 192.168.122.209 [40201.826025] [tdb] Close table 'cache0.tdb' Apr 26 03:14:11 192.168.122.209 [40202.080339] [tdb] Close table 'filter0.tdb' Apr 26 03:14:11 192.168.122.209 [40202.080788] [tempesta fw] modules are stopped Apr 26 03:14:11 192.168.122.209 [40202.280833] [tempesta fw] exiting... Apr 26 03:14:12 192.168.122.209 [40202.446800] [tdb] Shutdown Tempesta DB Apr 26 03:14:12 192.168.122.209 [40202.675603] End test: http2_general.test_h2_headers.CookieParsingHttp.test_many_cookie_last Apr 26 03:14:12 192.168.122.209 [40202.684948] Start test: http2_general.test_h2_headers.CookieParsingHttp.test_single_cookie Apr 26 03:14:13 192.168.122.209 [40203.822367] [tdb] Start Tempesta DB Apr 26 03:14:13 192.168.122.209 [40203.972674] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:14:15 192.168.122.209 [40205.496293] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40205.496293] Maybe that's fine, but it's worth checking the [40205.496293] config - if there is no relations between the [40205.496293] names, then host name confusion attack is possible. Apr 26 03:14:15 192.168.122.209 [40205.638993] [tempesta fw] Configuration processing is completed. Apr 26 03:14:15 192.168.122.209 [40205.690511] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:14:15 192.168.122.209 [40206.099608] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:14:15 192.168.122.209 [40206.125663] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:14:15 192.168.122.209 [40206.151625] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:14:15 192.168.122.209 [40206.194983] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:14:15 192.168.122.209 [40206.196710] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:14:15 192.168.122.209 [40206.238872] [tempesta fw] Tempesta FW is ready Apr 26 03:14:16 192.168.122.209 [40206.850437] [tdb] Close table 'client0.tdb' Apr 26 03:14:16 192.168.122.209 [40207.044157] [tdb] Close table 'sessions0.tdb' Apr 26 03:14:19 192.168.122.209 [40210.196946] [tdb] Close table 'cache0.tdb' Apr 26 03:14:20 192.168.122.209 [40210.452484] [tdb] Close table 'filter0.tdb' Apr 26 03:14:20 192.168.122.209 [40210.452923] [tempesta fw] modules are stopped Apr 26 03:14:20 192.168.122.209 [40210.662883] [tempesta fw] exiting... Apr 26 03:14:20 192.168.122.209 [40210.792210] [tdb] Shutdown Tempesta DB Apr 26 03:14:20 192.168.122.209 [40210.976826] End test: http2_general.test_h2_headers.CookieParsingHttp.test_single_cookie Apr 26 03:14:20 192.168.122.209 [40210.994016] Start test: http2_general.test_h2_headers.DuplicateSingularHeader.test_header_as_string_value Apr 26 03:14:21 192.168.122.209 [40212.190368] [tdb] Start Tempesta DB Apr 26 03:14:22 192.168.122.209 [40212.349389] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:14:23 192.168.122.209 [40214.004498] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40214.004498] Maybe that's fine, but it's worth checking the [40214.004498] config - if there is no relations between the [40214.004498] names, then host name confusion attack is possible. Apr 26 03:14:23 192.168.122.209 [40214.175036] [tempesta fw] Configuration processing is completed. Apr 26 03:14:23 192.168.122.209 [40214.269843] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:14:24 192.168.122.209 [40214.725519] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:14:24 192.168.122.209 [40214.758127] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:14:24 192.168.122.209 [40214.788793] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:14:24 192.168.122.209 [40214.847029] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:14:24 192.168.122.209 [40214.886945] [tempesta fw] Tempesta FW is ready Apr 26 03:14:24 192.168.122.209 [40215.063445] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrRefererV input=0x74('test1'), len=5, off=0 Apr 26 03:14:25 192.168.122.209 [40215.534540] [tdb] Close table 'client0.tdb' Apr 26 03:14:25 192.168.122.209 [40215.738565] [tdb] Close table 'sessions0.tdb' Apr 26 03:14:28 192.168.122.209 [40218.966765] [tdb] Close table 'cache0.tdb' Apr 26 03:14:28 192.168.122.209 [40219.201308] [tdb] Close table 'filter0.tdb' Apr 26 03:14:28 192.168.122.209 [40219.201743] [tempesta fw] modules are stopped Apr 26 03:14:29 192.168.122.209 [40219.495279] [tempesta fw] exiting... Apr 26 03:14:29 192.168.122.209 [40219.667228] [tdb] Shutdown Tempesta DB Apr 26 03:14:29 192.168.122.209 [40219.861619] End test: http2_general.test_h2_headers.DuplicateSingularHeader.test_header_as_string_value Apr 26 03:14:29 192.168.122.209 [40219.871664] Start test: http2_general.test_h2_headers.DuplicateSingularHeader.test_header_from_static_table_and_dynamic_table Apr 26 03:14:30 192.168.122.209 [40221.031210] [tdb] Start Tempesta DB Apr 26 03:14:30 192.168.122.209 [40221.177805] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:14:32 192.168.122.209 [40222.776579] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40222.776579] Maybe that's fine, but it's worth checking the [40222.776579] config - if there is no relations between the [40222.776579] names, then host name confusion attack is possible. Apr 26 03:14:32 192.168.122.209 [40222.931155] [tempesta fw] Configuration processing is completed. Apr 26 03:14:32 192.168.122.209 [40222.981222] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:14:33 192.168.122.209 [40223.385383] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:14:33 192.168.122.209 [40223.411383] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:14:33 192.168.122.209 [40223.446169] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:14:33 192.168.122.209 [40223.499160] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:14:33 192.168.122.209 [40223.539132] [tempesta fw] Tempesta FW is ready Apr 26 03:14:33 192.168.122.209 [40224.146452] [tdb] Close table 'client0.tdb' Apr 26 03:14:34 192.168.122.209 [40224.318822] [tdb] Close table 'sessions0.tdb' Apr 26 03:14:37 192.168.122.209 [40227.484235] [tdb] Close table 'cache0.tdb' Apr 26 03:14:37 192.168.122.209 [40227.715977] [tdb] Close table 'filter0.tdb' Apr 26 03:14:37 192.168.122.209 [40227.716411] [tempesta fw] modules are stopped Apr 26 03:14:37 192.168.122.209 [40227.933994] [tempesta fw] exiting... Apr 26 03:14:37 192.168.122.209 [40228.058743] [tdb] Shutdown Tempesta DB Apr 26 03:14:37 192.168.122.209 [40228.282505] End test: http2_general.test_h2_headers.DuplicateSingularHeader.test_header_from_static_table_and_dynamic_table Apr 26 03:14:37 192.168.122.209 [40228.307886] Start test: http2_general.test_h2_headers.DuplicateSingularHeader.test_two_header_as_bytes_from_dynamic_table Apr 26 03:14:39 192.168.122.209 [40229.469053] [tdb] Start Tempesta DB Apr 26 03:14:39 192.168.122.209 [40229.611737] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:14:40 192.168.122.209 [40231.172955] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40231.172955] Maybe that's fine, but it's worth checking the [40231.172955] config - if there is no relations between the [40231.172955] names, then host name confusion attack is possible. Apr 26 03:14:41 192.168.122.209 [40231.339327] [tempesta fw] Configuration processing is completed. Apr 26 03:14:41 192.168.122.209 [40231.389206] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:14:41 192.168.122.209 [40231.794408] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:14:41 192.168.122.209 [40231.820042] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:14:41 192.168.122.209 [40231.845272] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:14:41 192.168.122.209 [40231.891229] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:14:41 192.168.122.209 [40231.935236] [tempesta fw] Tempesta FW is ready Apr 26 03:14:42 192.168.122.209 [40232.516025] [tdb] Close table 'client0.tdb' Apr 26 03:14:42 192.168.122.209 [40232.706601] [tdb] Close table 'sessions0.tdb' Apr 26 03:14:45 192.168.122.209 [40235.849461] [tdb] Close table 'cache0.tdb' Apr 26 03:14:45 192.168.122.209 [40236.100743] [tdb] Close table 'filter0.tdb' Apr 26 03:14:45 192.168.122.209 [40236.101179] [tempesta fw] modules are stopped Apr 26 03:14:46 192.168.122.209 [40236.326728] [tempesta fw] exiting... Apr 26 03:14:46 192.168.122.209 [40236.482230] [tdb] Shutdown Tempesta DB Apr 26 03:14:46 192.168.122.209 [40236.708736] End test: http2_general.test_h2_headers.DuplicateSingularHeader.test_two_header_as_bytes_from_dynamic_table Apr 26 03:14:46 192.168.122.209 [40236.718032] Start test: http2_general.test_h2_headers.HeadersEmptyCache.test Apr 26 03:14:47 192.168.122.209 [40237.853525] [tdb] Start Tempesta DB Apr 26 03:14:47 192.168.122.209 [40237.994417] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:14:49 192.168.122.209 [40239.504965] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40239.504965] Maybe that's fine, but it's worth checking the [40239.504965] config - if there is no relations between the [40239.504965] names, then host name confusion attack is possible. Apr 26 03:14:49 192.168.122.209 [40239.571352] [tempesta fw] Configuration processing is completed. Apr 26 03:14:49 192.168.122.209 [40239.659486] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:14:49 192.168.122.209 [40240.070133] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:14:49 192.168.122.209 [40240.096432] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:14:49 192.168.122.209 [40240.123208] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:14:49 192.168.122.209 [40240.179372] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:14:49 192.168.122.209 [40240.223307] [tempesta fw] Tempesta FW is ready Apr 26 03:14:50 192.168.122.209 [40240.884643] [tdb] Close table 'client0.tdb' Apr 26 03:14:50 192.168.122.209 [40241.104622] [tdb] Close table 'sessions0.tdb' Apr 26 03:14:53 192.168.122.209 [40244.237690] [tdb] Close table 'cache0.tdb' Apr 26 03:14:54 192.168.122.209 [40244.477445] [tdb] Close table 'filter0.tdb' Apr 26 03:14:54 192.168.122.209 [40244.477880] [tempesta fw] modules are stopped Apr 26 03:14:54 192.168.122.209 [40244.723368] [tempesta fw] exiting... Apr 26 03:14:54 192.168.122.209 [40244.869604] [tdb] Shutdown Tempesta DB Apr 26 03:14:54 192.168.122.209 [40245.052905] End test: http2_general.test_h2_headers.HeadersEmptyCache.test Apr 26 03:14:54 192.168.122.209 [40245.064486] Start test: http2_general.test_h2_headers.HeadersParsing.test_long_header_name_in_request Apr 26 03:14:55 192.168.122.209 [40246.206112] [tdb] Start Tempesta DB Apr 26 03:14:56 192.168.122.209 [40246.352390] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:14:57 192.168.122.209 [40247.984933] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40247.984933] Maybe that's fine, but it's worth checking the [40247.984933] config - if there is no relations between the [40247.984933] names, then host name confusion attack is possible. Apr 26 03:14:57 192.168.122.209 [40248.143480] [tempesta fw] Configuration processing is completed. Apr 26 03:14:57 192.168.122.209 [40248.193931] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:14:58 192.168.122.209 [40248.602025] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:14:58 192.168.122.209 [40248.627561] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:14:58 192.168.122.209 [40248.652991] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:14:58 192.168.122.209 [40248.695425] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:14:58 192.168.122.209 [40248.731440] [tempesta fw] Tempesta FW is ready Apr 26 03:15:08 192.168.122.209 [40258.018616] [tempesta fw] Warning: Max header name length 1024 exceeded. Apr 26 03:15:08 192.168.122.209 [40258.436167] [tdb] Close table 'client0.tdb' Apr 26 03:15:08 192.168.122.209 [40258.621743] [tdb] Close table 'sessions0.tdb' Apr 26 03:15:11 192.168.122.209 [40261.738496] [tdb] Close table 'cache0.tdb' Apr 26 03:15:11 192.168.122.209 [40261.990746] [tdb] Close table 'filter0.tdb' Apr 26 03:15:11 192.168.122.209 [40261.991169] [tempesta fw] modules are stopped Apr 26 03:15:11 192.168.122.209 [40262.223770] [tempesta fw] exiting... Apr 26 03:15:12 192.168.122.209 [40262.405941] [tdb] Shutdown Tempesta DB Apr 26 03:15:12 192.168.122.209 [40262.616364] End test: http2_general.test_h2_headers.HeadersParsing.test_long_header_name_in_request Apr 26 03:15:12 192.168.122.209 [40262.629257] Start test: http2_general.test_h2_headers.HeadersParsing.test_long_header_name_in_response Apr 26 03:15:13 192.168.122.209 [40263.839320] [tdb] Start Tempesta DB Apr 26 03:15:13 192.168.122.209 [40263.975787] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:15:15 192.168.122.209 [40265.629145] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40265.629145] Maybe that's fine, but it's worth checking the [40265.629145] config - if there is no relations between the [40265.629145] names, then host name confusion attack is possible. Apr 26 03:15:15 192.168.122.209 [40265.775709] [tempesta fw] Configuration processing is completed. Apr 26 03:15:15 192.168.122.209 [40265.825870] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:15:15 192.168.122.209 [40266.236196] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:15:15 192.168.122.209 [40266.261602] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:15:15 192.168.122.209 [40266.287018] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:15:16 192.168.122.209 [40266.339707] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:15:16 192.168.122.209 [40266.379663] [tempesta fw] Tempesta FW is ready Apr 26 03:15:25 192.168.122.209 [40275.611414] [tempesta fw] Warning: Max header name length 1024 exceeded. Apr 26 03:15:25 192.168.122.209 [40275.611432] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 03:15:25 192.168.122.209 [40276.030586] [tdb] Close table 'client0.tdb' Apr 26 03:15:25 192.168.122.209 [40276.217178] [tdb] Close table 'sessions0.tdb' Apr 26 03:15:29 192.168.122.209 [40279.314914] [tdb] Close table 'cache0.tdb' Apr 26 03:15:29 192.168.122.209 [40279.539479] [tdb] Close table 'filter0.tdb' Apr 26 03:15:29 192.168.122.209 [40279.539946] [tempesta fw] modules are stopped Apr 26 03:15:29 192.168.122.209 [40279.830624] [tempesta fw] exiting... Apr 26 03:15:29 192.168.122.209 [40279.965410] [tdb] Shutdown Tempesta DB Apr 26 03:15:29 192.168.122.209 [40280.162547] End test: http2_general.test_h2_headers.HeadersParsing.test_long_header_name_in_response Apr 26 03:15:29 192.168.122.209 [40280.180541] Start test: http2_general.test_h2_headers.HeadersParsing.test_small_header_in_request Apr 26 03:15:31 192.168.122.209 [40281.316820] [tdb] Start Tempesta DB Apr 26 03:15:31 192.168.122.209 [40281.465296] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:15:32 192.168.122.209 [40283.069325] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40283.069325] Maybe that's fine, but it's worth checking the [40283.069325] config - if there is no relations between the [40283.069325] names, then host name confusion attack is possible. Apr 26 03:15:32 192.168.122.209 [40283.228251] [tempesta fw] Configuration processing is completed. Apr 26 03:15:32 192.168.122.209 [40283.277573] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:15:33 192.168.122.209 [40283.691656] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:15:33 192.168.122.209 [40283.717694] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:15:33 192.168.122.209 [40283.744265] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:15:33 192.168.122.209 [40283.783950] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:15:33 192.168.122.209 [40283.827895] [tempesta fw] Tempesta FW is ready Apr 26 03:15:34 192.168.122.209 [40284.486330] [tdb] Close table 'client0.tdb' Apr 26 03:15:34 192.168.122.209 [40284.682152] [tdb] Close table 'sessions0.tdb' Apr 26 03:15:37 192.168.122.209 [40287.874369] [tdb] Close table 'cache0.tdb' Apr 26 03:15:37 192.168.122.209 [40288.127471] [tdb] Close table 'filter0.tdb' Apr 26 03:15:37 192.168.122.209 [40288.127924] [tempesta fw] modules are stopped Apr 26 03:15:38 192.168.122.209 [40288.368034] [tempesta fw] exiting... Apr 26 03:15:38 192.168.122.209 [40288.521053] [tdb] Shutdown Tempesta DB Apr 26 03:15:38 192.168.122.209 [40288.730071] End test: http2_general.test_h2_headers.HeadersParsing.test_small_header_in_request Apr 26 03:15:38 192.168.122.209 [40288.750348] Start test: http2_general.test_h2_headers.HeadersParsing.test_transfer_encoding_header_in_request Apr 26 03:15:39 192.168.122.209 [40289.940724] [tdb] Start Tempesta DB Apr 26 03:15:39 192.168.122.209 [40290.085062] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:15:41 192.168.122.209 [40291.721669] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40291.721669] Maybe that's fine, but it's worth checking the [40291.721669] config - if there is no relations between the [40291.721669] names, then host name confusion attack is possible. Apr 26 03:15:41 192.168.122.209 [40291.900036] [tempesta fw] Configuration processing is completed. Apr 26 03:15:41 192.168.122.209 [40291.950093] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:15:42 192.168.122.209 [40292.351587] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:15:42 192.168.122.209 [40292.377016] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:15:42 192.168.122.209 [40292.402343] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:15:42 192.168.122.209 [40292.448050] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:15:42 192.168.122.209 [40292.491992] [tempesta fw] Tempesta FW is ready Apr 26 03:15:42 192.168.122.209 [40292.628054] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrTeV input=0x63('chunked'), len=7, off=0 Apr 26 03:15:42 192.168.122.209 [40293.109221] [tdb] Close table 'client0.tdb' Apr 26 03:15:42 192.168.122.209 [40293.290725] [tdb] Close table 'sessions0.tdb' Apr 26 03:15:46 192.168.122.209 [40296.421725] [tdb] Close table 'cache0.tdb' Apr 26 03:15:46 192.168.122.209 [40296.671527] [tdb] Close table 'filter0.tdb' Apr 26 03:15:46 192.168.122.209 [40296.671991] [tempesta fw] modules are stopped Apr 26 03:15:46 192.168.122.209 [40296.891455] [tempesta fw] exiting... Apr 26 03:15:46 192.168.122.209 [40297.073138] [tdb] Shutdown Tempesta DB Apr 26 03:15:46 192.168.122.209 [40297.270939] End test: http2_general.test_h2_headers.HeadersParsing.test_transfer_encoding_header_in_request Apr 26 03:15:46 192.168.122.209 [40297.279349] Start test: http2_general.test_h2_headers.HeadersSpacedCache.test Apr 26 03:15:48 192.168.122.209 [40298.402009] [tdb] Start Tempesta DB Apr 26 03:15:48 192.168.122.209 [40298.541410] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:15:49 192.168.122.209 [40299.909700] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40299.909700] Maybe that's fine, but it's worth checking the [40299.909700] config - if there is no relations between the [40299.909700] names, then host name confusion attack is possible. Apr 26 03:15:49 192.168.122.209 [40299.992131] [tempesta fw] Configuration processing is completed. Apr 26 03:15:49 192.168.122.209 [40300.079325] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:15:50 192.168.122.209 [40300.495711] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:15:50 192.168.122.209 [40300.522372] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:15:50 192.168.122.209 [40300.549409] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:15:50 192.168.122.209 [40300.608132] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:15:50 192.168.122.209 [40300.660085] [tempesta fw] Tempesta FW is ready Apr 26 03:15:51 192.168.122.209 [40301.373834] [tdb] Close table 'client0.tdb' Apr 26 03:15:51 192.168.122.209 [40301.570156] [tdb] Close table 'sessions0.tdb' Apr 26 03:15:54 192.168.122.209 [40304.728314] [tdb] Close table 'cache0.tdb' Apr 26 03:15:54 192.168.122.209 [40304.957334] [tdb] Close table 'filter0.tdb' Apr 26 03:15:54 192.168.122.209 [40304.957755] [tempesta fw] modules are stopped Apr 26 03:15:54 192.168.122.209 [40305.252391] [tempesta fw] exiting... Apr 26 03:15:55 192.168.122.209 [40305.408673] [tdb] Shutdown Tempesta DB Apr 26 03:15:55 192.168.122.209 [40305.613651] End test: http2_general.test_h2_headers.HeadersSpacedCache.test Apr 26 03:15:55 192.168.122.209 [40305.631558] Start test: http2_general.test_h2_headers.LowercaseAddBackendHeaders.test Apr 26 03:15:56 192.168.122.209 [40306.871692] [tdb] Start Tempesta DB Apr 26 03:15:56 192.168.122.209 [40307.022769] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:15:58 192.168.122.209 [40308.425767] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40308.425767] Maybe that's fine, but it's worth checking the [40308.425767] config - if there is no relations between the [40308.425767] names, then host name confusion attack is possible. Apr 26 03:15:58 192.168.122.209 [40308.476240] [tempesta fw] Configuration processing is completed. Apr 26 03:15:58 192.168.122.209 [40308.526214] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:15:58 192.168.122.209 [40308.928037] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:15:58 192.168.122.209 [40308.953346] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:15:58 192.168.122.209 [40308.978620] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:15:58 192.168.122.209 [40309.052254] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:15:58 192.168.122.209 [40309.100151] [tempesta fw] Tempesta FW is ready Apr 26 03:15:59 192.168.122.209 [40309.852243] [tdb] Close table 'client0.tdb' Apr 26 03:15:59 192.168.122.209 [40310.054389] [tdb] Close table 'sessions0.tdb' Apr 26 03:16:02 192.168.122.209 [40313.237004] [tdb] Close table 'cache0.tdb' Apr 26 03:16:03 192.168.122.209 [40313.500117] [tdb] Close table 'filter0.tdb' Apr 26 03:16:03 192.168.122.209 [40313.500568] [tempesta fw] modules are stopped Apr 26 03:16:03 192.168.122.209 [40313.700457] [tempesta fw] exiting... Apr 26 03:16:03 192.168.122.209 [40313.879062] [tdb] Shutdown Tempesta DB Apr 26 03:16:03 192.168.122.209 [40314.141303] End test: http2_general.test_h2_headers.LowercaseAddBackendHeaders.test Apr 26 03:16:03 192.168.122.209 [40314.153098] Start test: http2_general.test_h2_headers.LowercaseAddBackendHeadersCache.test Apr 26 03:16:05 192.168.122.209 [40315.382302] [tdb] Start Tempesta DB Apr 26 03:16:05 192.168.122.209 [40315.529143] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:16:06 192.168.122.209 [40316.849897] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40316.849897] Maybe that's fine, but it's worth checking the [40316.849897] config - if there is no relations between the [40316.849897] names, then host name confusion attack is possible. Apr 26 03:16:06 192.168.122.209 [40316.940523] [tempesta fw] Configuration processing is completed. Apr 26 03:16:06 192.168.122.209 [40316.996209] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:16:07 192.168.122.209 [40317.413418] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:16:07 192.168.122.209 [40317.439375] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:16:07 192.168.122.209 [40317.464976] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:16:07 192.168.122.209 [40317.536344] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:16:07 192.168.122.209 [40317.580297] [tempesta fw] Tempesta FW is ready Apr 26 03:16:08 192.168.122.209 [40318.401301] [tdb] Close table 'client0.tdb' Apr 26 03:16:08 192.168.122.209 [40318.610629] [tdb] Close table 'sessions0.tdb' Apr 26 03:16:11 192.168.122.209 [40321.797224] [tdb] Close table 'cache0.tdb' Apr 26 03:16:11 192.168.122.209 [40322.078067] [tdb] Close table 'filter0.tdb' Apr 26 03:16:11 192.168.122.209 [40322.078494] [tempesta fw] modules are stopped Apr 26 03:16:11 192.168.122.209 [40322.252254] [tempesta fw] exiting... Apr 26 03:16:12 192.168.122.209 [40322.410670] [tdb] Shutdown Tempesta DB Apr 26 03:16:12 192.168.122.209 [40322.644385] End test: http2_general.test_h2_headers.LowercaseAddBackendHeadersCache.test Apr 26 03:16:12 192.168.122.209 [40322.660110] Start test: http2_general.test_h2_headers.MissingDateServerWithBodyTest.test Apr 26 03:16:13 192.168.122.209 [40323.877027] [tdb] Start Tempesta DB Apr 26 03:16:13 192.168.122.209 [40324.029456] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:16:15 192.168.122.209 [40325.399586] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40325.399586] Maybe that's fine, but it's worth checking the [40325.399586] config - if there is no relations between the [40325.399586] names, then host name confusion attack is possible. Apr 26 03:16:15 192.168.122.209 [40325.488824] [tempesta fw] Configuration processing is completed. Apr 26 03:16:15 192.168.122.209 [40325.545897] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:16:15 192.168.122.209 [40326.002334] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:16:15 192.168.122.209 [40326.039950] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:16:15 192.168.122.209 [40326.065677] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:16:15 192.168.122.209 [40326.112465] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:16:15 192.168.122.209 [40326.152416] [tempesta fw] Tempesta FW is ready Apr 26 03:16:16 192.168.122.209 [40326.773422] [tdb] Close table 'client0.tdb' Apr 26 03:16:16 192.168.122.209 [40326.967982] [tdb] Close table 'sessions0.tdb' Apr 26 03:16:19 192.168.122.209 [40330.135518] [tdb] Close table 'cache0.tdb' Apr 26 03:16:20 192.168.122.209 [40330.405437] [tdb] Close table 'filter0.tdb' Apr 26 03:16:20 192.168.122.209 [40330.405879] [tempesta fw] modules are stopped Apr 26 03:16:20 192.168.122.209 [40330.576809] [tempesta fw] exiting... Apr 26 03:16:20 192.168.122.209 [40330.738938] [tdb] Shutdown Tempesta DB Apr 26 03:16:20 192.168.122.209 [40330.963985] End test: http2_general.test_h2_headers.MissingDateServerWithBodyTest.test Apr 26 03:16:20 192.168.122.209 [40330.975014] Start test: http2_general.test_h2_headers.MissingDateServerWithLargeBodyTest.test Apr 26 03:16:21 192.168.122.209 [40332.135770] [tdb] Start Tempesta DB Apr 26 03:16:21 192.168.122.209 [40332.298025] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:16:23 192.168.122.209 [40333.578002] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40333.578002] Maybe that's fine, but it's worth checking the [40333.578002] config - if there is no relations between the [40333.578002] names, then host name confusion attack is possible. Apr 26 03:16:23 192.168.122.209 [40333.672446] [tempesta fw] Configuration processing is completed. Apr 26 03:16:23 192.168.122.209 [40333.720628] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:16:23 192.168.122.209 [40334.120764] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:16:23 192.168.122.209 [40334.147108] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:16:23 192.168.122.209 [40334.174075] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:16:23 192.168.122.209 [40334.232573] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:16:23 192.168.122.209 [40334.272523] [tempesta fw] Tempesta FW is ready Apr 26 03:16:24 192.168.122.209 [40334.869283] [tdb] Close table 'client0.tdb' Apr 26 03:16:24 192.168.122.209 [40335.071654] [tdb] Close table 'sessions0.tdb' Apr 26 03:16:27 192.168.122.209 [40338.281339] [tdb] Close table 'cache0.tdb' Apr 26 03:16:28 192.168.122.209 [40338.545605] [tdb] Close table 'filter0.tdb' Apr 26 03:16:28 192.168.122.209 [40338.546031] [tempesta fw] modules are stopped Apr 26 03:16:28 192.168.122.209 [40338.725440] [tempesta fw] exiting... Apr 26 03:16:28 192.168.122.209 [40338.923549] [tdb] Shutdown Tempesta DB Apr 26 03:16:28 192.168.122.209 [40339.145871] End test: http2_general.test_h2_headers.MissingDateServerWithLargeBodyTest.test Apr 26 03:16:28 192.168.122.209 [40339.155303] Start test: http2_general.test_h2_headers.TestConnectionHeaders.test_TE_header_in_request Apr 26 03:16:29 192.168.122.209 [40340.264972] [tdb] Start Tempesta DB Apr 26 03:16:30 192.168.122.209 [40340.402261] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:16:31 192.168.122.209 [40342.026153] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40342.026153] Maybe that's fine, but it's worth checking the [40342.026153] config - if there is no relations between the [40342.026153] names, then host name confusion attack is possible. Apr 26 03:16:31 192.168.122.209 [40342.176717] [tempesta fw] Configuration processing is completed. Apr 26 03:16:31 192.168.122.209 [40342.229870] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:16:32 192.168.122.209 [40342.671094] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:16:32 192.168.122.209 [40342.706352] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:16:32 192.168.122.209 [40342.731184] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:16:32 192.168.122.209 [40342.772670] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:16:32 192.168.122.209 [40342.812619] [tempesta fw] Tempesta FW is ready Apr 26 03:16:32 192.168.122.209 [40342.948134] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrTeV input=0x67('gzip'), len=4, off=0 Apr 26 03:16:33 192.168.122.209 [40343.418518] [tdb] Close table 'client0.tdb' Apr 26 03:16:33 192.168.122.209 [40343.617983] [tdb] Close table 'sessions0.tdb' Apr 26 03:16:36 192.168.122.209 [40346.783967] [tdb] Close table 'cache0.tdb' Apr 26 03:16:36 192.168.122.209 [40347.026530] [tdb] Close table 'filter0.tdb' Apr 26 03:16:36 192.168.122.209 [40347.026963] [tempesta fw] modules are stopped Apr 26 03:16:36 192.168.122.209 [40347.260219] [tempesta fw] exiting... Apr 26 03:16:37 192.168.122.209 [40347.413710] [tdb] Shutdown Tempesta DB Apr 26 03:16:37 192.168.122.209 [40347.631865] End test: http2_general.test_h2_headers.TestConnectionHeaders.test_TE_header_in_request Apr 26 03:16:37 192.168.122.209 [40347.641129] Start test: http2_general.test_h2_headers.TestConnectionHeaders.test_connection_header_in_request Apr 26 03:16:38 192.168.122.209 [40348.859272] [tdb] Start Tempesta DB Apr 26 03:16:38 192.168.122.209 [40348.982238] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:16:40 192.168.122.209 [40350.534217] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40350.534217] Maybe that's fine, but it's worth checking the [40350.534217] config - if there is no relations between the [40350.534217] names, then host name confusion attack is possible. Apr 26 03:16:40 192.168.122.209 [40350.696809] [tempesta fw] Configuration processing is completed. Apr 26 03:16:40 192.168.122.209 [40350.781333] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:16:40 192.168.122.209 [40351.199930] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:16:40 192.168.122.209 [40351.236462] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:16:40 192.168.122.209 [40351.263301] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:16:40 192.168.122.209 [40351.304733] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:16:41 192.168.122.209 [40351.348683] [tempesta fw] Tempesta FW is ready Apr 26 03:16:41 192.168.122.209 [40351.482398] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrConnection input=0x63('connection'), len=10, off=0 Apr 26 03:16:41 192.168.122.209 [40351.921746] [tdb] Close table 'client0.tdb' Apr 26 03:16:41 192.168.122.209 [40352.126713] [tdb] Close table 'sessions0.tdb' Apr 26 03:16:45 192.168.122.209 [40355.319196] [tdb] Close table 'cache0.tdb' Apr 26 03:16:45 192.168.122.209 [40355.568360] [tdb] Close table 'filter0.tdb' Apr 26 03:16:45 192.168.122.209 [40355.568807] [tempesta fw] modules are stopped Apr 26 03:16:45 192.168.122.209 [40355.854430] [tempesta fw] exiting... Apr 26 03:16:45 192.168.122.209 [40355.995334] [tdb] Shutdown Tempesta DB Apr 26 03:16:45 192.168.122.209 [40356.227488] End test: http2_general.test_h2_headers.TestConnectionHeaders.test_connection_header_in_request Apr 26 03:16:45 192.168.122.209 [40356.238107] Start test: http2_general.test_h2_headers.TestConnectionHeaders.test_connection_header_in_response Apr 26 03:16:47 192.168.122.209 [40357.375780] [tdb] Start Tempesta DB Apr 26 03:16:47 192.168.122.209 [40357.506209] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:16:48 192.168.122.209 [40359.114648] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40359.114648] Maybe that's fine, but it's worth checking the [40359.114648] config - if there is no relations between the [40359.114648] names, then host name confusion attack is possible. Apr 26 03:16:48 192.168.122.209 [40359.264911] [tempesta fw] Configuration processing is completed. Apr 26 03:16:49 192.168.122.209 [40359.315842] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:16:49 192.168.122.209 [40359.720447] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:16:49 192.168.122.209 [40359.745811] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:16:49 192.168.122.209 [40359.770719] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:16:49 192.168.122.209 [40359.816851] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:16:49 192.168.122.209 [40359.856846] [tempesta fw] Tempesta FW is ready Apr 26 03:16:50 192.168.122.209 [40360.446549] [tdb] Close table 'client0.tdb' Apr 26 03:16:50 192.168.122.209 [40360.648957] [tdb] Close table 'sessions0.tdb' Apr 26 03:16:53 192.168.122.209 [40363.996047] [tdb] Close table 'cache0.tdb' Apr 26 03:16:53 192.168.122.209 [40364.228025] [tdb] Close table 'filter0.tdb' Apr 26 03:16:53 192.168.122.209 [40364.228449] [tempesta fw] modules are stopped Apr 26 03:16:54 192.168.122.209 [40364.520847] [tempesta fw] exiting... Apr 26 03:16:54 192.168.122.209 [40364.662385] [tdb] Shutdown Tempesta DB Apr 26 03:16:54 192.168.122.209 [40364.868876] End test: http2_general.test_h2_headers.TestConnectionHeaders.test_connection_header_in_response Apr 26 03:16:54 192.168.122.209 [40364.877970] Start test: http2_general.test_h2_headers.TestConnectionHeaders.test_keep_alive_header_in_request Apr 26 03:16:55 192.168.122.209 [40366.067111] [tdb] Start Tempesta DB Apr 26 03:16:55 192.168.122.209 [40366.221551] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:16:57 192.168.122.209 [40367.774428] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40367.774428] Maybe that's fine, but it's worth checking the [40367.774428] config - if there is no relations between the [40367.774428] names, then host name confusion attack is possible. Apr 26 03:16:57 192.168.122.209 [40367.925328] [tempesta fw] Configuration processing is completed. Apr 26 03:16:57 192.168.122.209 [40367.975713] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:16:58 192.168.122.209 [40368.381518] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:16:58 192.168.122.209 [40368.407121] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:16:58 192.168.122.209 [40368.432430] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:16:58 192.168.122.209 [40368.480981] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:16:58 192.168.122.209 [40368.520951] [tempesta fw] Tempesta FW is ready Apr 26 03:16:58 192.168.122.209 [40368.656629] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrKeep_Alive input=0x6b('keep-alive'), len=10, off=0 Apr 26 03:16:58 192.168.122.209 [40369.076892] [tdb] Close table 'client0.tdb' Apr 26 03:16:58 192.168.122.209 [40369.296424] [tdb] Close table 'sessions0.tdb' Apr 26 03:17:02 192.168.122.209 [40372.504057] [tdb] Close table 'cache0.tdb' Apr 26 03:17:02 192.168.122.209 [40372.746113] [tdb] Close table 'filter0.tdb' Apr 26 03:17:02 192.168.122.209 [40372.746542] [tempesta fw] modules are stopped Apr 26 03:17:02 192.168.122.209 [40372.953319] [tempesta fw] exiting... Apr 26 03:17:02 192.168.122.209 [40373.103371] [tdb] Shutdown Tempesta DB Apr 26 03:17:03 192.168.122.209 [40373.334345] End test: http2_general.test_h2_headers.TestConnectionHeaders.test_keep_alive_header_in_request Apr 26 03:17:03 192.168.122.209 [40373.347425] Start test: http2_general.test_h2_headers.TestConnectionHeaders.test_keep_alive_header_in_response Apr 26 03:17:04 192.168.122.209 [40374.491329] [tdb] Start Tempesta DB Apr 26 03:17:04 192.168.122.209 [40374.629828] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:17:05 192.168.122.209 [40376.253876] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40376.253876] Maybe that's fine, but it's worth checking the [40376.253876] config - if there is no relations between the [40376.253876] names, then host name confusion attack is possible. Apr 26 03:17:06 192.168.122.209 [40376.397181] [tempesta fw] Configuration processing is completed. Apr 26 03:17:06 192.168.122.209 [40376.488218] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:17:06 192.168.122.209 [40376.903915] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:17:06 192.168.122.209 [40376.935554] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:17:06 192.168.122.209 [40376.962599] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:17:06 192.168.122.209 [40377.005118] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:17:06 192.168.122.209 [40377.045073] [tempesta fw] Tempesta FW is ready Apr 26 03:17:07 192.168.122.209 [40377.652704] [tdb] Close table 'client0.tdb' Apr 26 03:17:07 192.168.122.209 [40377.847483] [tdb] Close table 'sessions0.tdb' Apr 26 03:17:10 192.168.122.209 [40380.983097] [tdb] Close table 'cache0.tdb' Apr 26 03:17:10 192.168.122.209 [40381.215588] [tdb] Close table 'filter0.tdb' Apr 26 03:17:10 192.168.122.209 [40381.216024] [tempesta fw] modules are stopped Apr 26 03:17:11 192.168.122.209 [40381.499531] [tempesta fw] exiting... Apr 26 03:17:11 192.168.122.209 [40381.660744] [tdb] Shutdown Tempesta DB Apr 26 03:17:11 192.168.122.209 [40381.874276] End test: http2_general.test_h2_headers.TestConnectionHeaders.test_keep_alive_header_in_response Apr 26 03:17:11 192.168.122.209 [40381.885956] Start test: http2_general.test_h2_headers.TestConnectionHeaders.test_proxy_connection_header_in_request Apr 26 03:17:12 192.168.122.209 [40383.056374] [tdb] Start Tempesta DB Apr 26 03:17:12 192.168.122.209 [40383.205714] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:17:14 192.168.122.209 [40384.822668] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40384.822668] Maybe that's fine, but it's worth checking the [40384.822668] config - if there is no relations between the [40384.822668] names, then host name confusion attack is possible. Apr 26 03:17:14 192.168.122.209 [40384.973242] [tempesta fw] Configuration processing is completed. Apr 26 03:17:14 192.168.122.209 [40385.028515] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:17:15 192.168.122.209 [40385.453492] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:17:15 192.168.122.209 [40385.482716] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:17:15 192.168.122.209 [40385.508801] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:17:15 192.168.122.209 [40385.561241] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:17:15 192.168.122.209 [40385.613193] [tempesta fw] Tempesta FW is ready Apr 26 03:17:15 192.168.122.209 [40385.758439] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrProxyConnection input=0x70('proxy-connection'), len=16, off=0 Apr 26 03:17:15 192.168.122.209 [40386.212037] [tdb] Close table 'client0.tdb' Apr 26 03:17:16 192.168.122.209 [40386.414599] [tdb] Close table 'sessions0.tdb' Apr 26 03:17:19 192.168.122.209 [40389.547103] [tdb] Close table 'cache0.tdb' Apr 26 03:17:19 192.168.122.209 [40389.777237] [tdb] Close table 'filter0.tdb' Apr 26 03:17:19 192.168.122.209 [40389.777655] [tempesta fw] modules are stopped Apr 26 03:17:19 192.168.122.209 [40390.020995] [tempesta fw] exiting... Apr 26 03:17:19 192.168.122.209 [40390.184418] [tdb] Shutdown Tempesta DB Apr 26 03:17:20 192.168.122.209 [40390.388395] End test: http2_general.test_h2_headers.TestConnectionHeaders.test_proxy_connection_header_in_request Apr 26 03:17:20 192.168.122.209 [40390.406623] Start test: http2_general.test_h2_headers.TestConnectionHeaders.test_proxy_connection_header_in_response Apr 26 03:17:21 192.168.122.209 [40391.460151] [tdb] Start Tempesta DB Apr 26 03:17:21 192.168.122.209 [40391.621012] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:17:22 192.168.122.209 [40393.122827] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40393.122827] Maybe that's fine, but it's worth checking the [40393.122827] config - if there is no relations between the [40393.122827] names, then host name confusion attack is possible. Apr 26 03:17:23 192.168.122.209 [40393.313336] [tempesta fw] Configuration processing is completed. Apr 26 03:17:23 192.168.122.209 [40393.370081] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:17:23 192.168.122.209 [40393.808698] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:17:23 192.168.122.209 [40393.836469] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:17:23 192.168.122.209 [40393.863617] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:17:23 192.168.122.209 [40393.909339] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:17:23 192.168.122.209 [40393.949294] [tempesta fw] Tempesta FW is ready Apr 26 03:17:24 192.168.122.209 [40394.519097] [tdb] Close table 'client0.tdb' Apr 26 03:17:24 192.168.122.209 [40394.720665] [tdb] Close table 'sessions0.tdb' Apr 26 03:17:27 192.168.122.209 [40397.868061] [tdb] Close table 'cache0.tdb' Apr 26 03:17:27 192.168.122.209 [40398.099306] [tdb] Close table 'filter0.tdb' Apr 26 03:17:27 192.168.122.209 [40398.099736] [tempesta fw] modules are stopped Apr 26 03:17:28 192.168.122.209 [40398.317448] [tempesta fw] exiting... Apr 26 03:17:28 192.168.122.209 [40398.454897] [tdb] Shutdown Tempesta DB Apr 26 03:17:28 192.168.122.209 [40398.671776] End test: http2_general.test_h2_headers.TestConnectionHeaders.test_proxy_connection_header_in_response Apr 26 03:17:28 192.168.122.209 [40398.688402] Start test: http2_general.test_h2_headers.TestConnectionHeaders.test_upgrade_header_in_request Apr 26 03:17:29 192.168.122.209 [40399.830279] [tdb] Start Tempesta DB Apr 26 03:17:29 192.168.122.209 [40399.992503] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:17:31 192.168.122.209 [40401.440071] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40401.440071] Maybe that's fine, but it's worth checking the [40401.440071] config - if there is no relations between the [40401.440071] names, then host name confusion attack is possible. Apr 26 03:17:31 192.168.122.209 [40401.585427] [tempesta fw] Configuration processing is completed. Apr 26 03:17:31 192.168.122.209 [40401.678164] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:17:31 192.168.122.209 [40402.098189] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:17:31 192.168.122.209 [40402.124773] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:17:31 192.168.122.209 [40402.152207] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:17:31 192.168.122.209 [40402.201433] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:17:31 192.168.122.209 [40402.241380] [tempesta fw] Tempesta FW is ready Apr 26 03:17:32 192.168.122.209 [40402.366910] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrUpgrade input=0x75('upgrade'), len=7, off=0 Apr 26 03:17:32 192.168.122.209 [40402.793594] [tdb] Close table 'client0.tdb' Apr 26 03:17:32 192.168.122.209 [40402.983178] [tdb] Close table 'sessions0.tdb' Apr 26 03:17:35 192.168.122.209 [40406.174355] [tdb] Close table 'cache0.tdb' Apr 26 03:17:36 192.168.122.209 [40406.412344] [tdb] Close table 'filter0.tdb' Apr 26 03:17:36 192.168.122.209 [40406.412785] [tempesta fw] modules are stopped Apr 26 03:17:36 192.168.122.209 [40406.662967] [tempesta fw] exiting... Apr 26 03:17:36 192.168.122.209 [40406.805817] [tdb] Shutdown Tempesta DB Apr 26 03:17:36 192.168.122.209 [40407.046622] End test: http2_general.test_h2_headers.TestConnectionHeaders.test_upgrade_header_in_request Apr 26 03:17:36 192.168.122.209 [40407.058687] Start test: http2_general.test_h2_headers.TestConnectionHeaders.test_upgrade_header_in_response Apr 26 03:17:37 192.168.122.209 [40408.117827] [tdb] Start Tempesta DB Apr 26 03:17:37 192.168.122.209 [40408.266472] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:17:39 192.168.122.209 [40409.863902] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40409.863902] Maybe that's fine, but it's worth checking the [40409.863902] config - if there is no relations between the [40409.863902] names, then host name confusion attack is possible. Apr 26 03:17:39 192.168.122.209 [40410.026485] [tempesta fw] Configuration processing is completed. Apr 26 03:17:39 192.168.122.209 [40410.080766] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:17:40 192.168.122.209 [40410.516216] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:17:40 192.168.122.209 [40410.544204] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:17:40 192.168.122.209 [40410.572405] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:17:40 192.168.122.209 [40410.621542] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:17:40 192.168.122.209 [40410.669487] [tempesta fw] Tempesta FW is ready Apr 26 03:17:40 192.168.122.209 [40411.228470] [tdb] Close table 'client0.tdb' Apr 26 03:17:41 192.168.122.209 [40411.449851] [tdb] Close table 'sessions0.tdb' Apr 26 03:17:44 192.168.122.209 [40414.626094] [tdb] Close table 'cache0.tdb' Apr 26 03:17:44 192.168.122.209 [40414.869009] [tdb] Close table 'filter0.tdb' Apr 26 03:17:44 192.168.122.209 [40414.869504] [tempesta fw] modules are stopped Apr 26 03:17:44 192.168.122.209 [40415.095132] [tempesta fw] exiting... Apr 26 03:17:44 192.168.122.209 [40415.251568] [tdb] Shutdown Tempesta DB Apr 26 03:17:45 192.168.122.209 [40415.465010] End test: http2_general.test_h2_headers.TestConnectionHeaders.test_upgrade_header_in_response Apr 26 03:17:45 192.168.122.209 [40415.475207] Start test: http2_general.test_h2_headers.TestContentTypeWithEmptyBodyDELETE.test_request_success Apr 26 03:17:46 192.168.122.209 [40416.682250] [tdb] Start Tempesta DB Apr 26 03:17:46 192.168.122.209 [40416.842440] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:17:48 192.168.122.209 [40418.314938] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40418.314938] Maybe that's fine, but it's worth checking the [40418.314938] config - if there is no relations between the [40418.314938] names, then host name confusion attack is possible. Apr 26 03:17:48 192.168.122.209 [40418.449706] [tempesta fw] Configuration processing is completed. Apr 26 03:17:48 192.168.122.209 [40418.510017] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:17:48 192.168.122.209 [40418.951444] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:17:48 192.168.122.209 [40418.978751] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:17:48 192.168.122.209 [40419.008289] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:17:48 192.168.122.209 [40419.077693] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:17:48 192.168.122.209 [40419.117616] [tempesta fw] Tempesta FW is ready Apr 26 03:17:48 192.168.122.209 [40419.265618] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 03:17:48 192.168.122.209 [40419.266389] [tempesta fw] Warning: Can't create pipelined response: 127.0.0.3 Apr 26 03:17:48 192.168.122.209 [40419.267031] [tempesta fw] 127.0.0.2 "default" "DELETE / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800880200" Apr 26 03:17:49 192.168.122.209 [40419.743276] [tdb] Close table 'client0.tdb' Apr 26 03:17:49 192.168.122.209 [40419.951375] [tdb] Close table 'sessions0.tdb' Apr 26 03:17:52 192.168.122.209 [40423.130551] [tdb] Close table 'cache0.tdb' Apr 26 03:17:53 192.168.122.209 [40423.366911] [tdb] Close table 'filter0.tdb' Apr 26 03:17:53 192.168.122.209 [40423.367386] [tempesta fw] modules are stopped Apr 26 03:17:53 192.168.122.209 [40423.578680] [tempesta fw] exiting... Apr 26 03:17:53 192.168.122.209 [40423.731921] [tdb] Shutdown Tempesta DB Apr 26 03:17:53 192.168.122.209 [40423.933858] End test: http2_general.test_h2_headers.TestContentTypeWithEmptyBodyDELETE.test_request_success Apr 26 03:17:53 192.168.122.209 [40423.943725] Start test: http2_general.test_h2_headers.TestContentTypeWithEmptyBodyPATCH.test_request_success Apr 26 03:17:54 192.168.122.209 [40425.117283] [tdb] Start Tempesta DB Apr 26 03:17:54 192.168.122.209 [40425.267120] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:17:56 192.168.122.209 [40426.539050] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40426.539050] Maybe that's fine, but it's worth checking the [40426.539050] config - if there is no relations between the [40426.539050] names, then host name confusion attack is possible. Apr 26 03:17:56 192.168.122.209 [40426.677823] [tempesta fw] Configuration processing is completed. Apr 26 03:17:56 192.168.122.209 [40426.736282] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:17:56 192.168.122.209 [40427.199778] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:17:56 192.168.122.209 [40427.239401] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:17:56 192.168.122.209 [40427.271258] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:17:57 192.168.122.209 [40427.317740] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:17:57 192.168.122.209 [40427.361709] [tempesta fw] Tempesta FW is ready Apr 26 03:17:57 192.168.122.209 [40427.493387] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 03:17:57 192.168.122.209 [40427.494403] [tempesta fw] Warning: Can't create pipelined response: 127.0.0.3 Apr 26 03:17:57 192.168.122.209 [40427.495064] [tempesta fw] 127.0.0.2 "default" "PATCH / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800a40200" Apr 26 03:17:57 192.168.122.209 [40427.970833] [tdb] Close table 'client0.tdb' Apr 26 03:17:57 192.168.122.209 [40428.167492] [tdb] Close table 'sessions0.tdb' Apr 26 03:18:01 192.168.122.209 [40431.352201] [tdb] Close table 'cache0.tdb' Apr 26 03:18:01 192.168.122.209 [40431.595022] [tdb] Close table 'filter0.tdb' Apr 26 03:18:01 192.168.122.209 [40431.595455] [tempesta fw] modules are stopped Apr 26 03:18:01 192.168.122.209 [40431.759029] [tempesta fw] exiting... Apr 26 03:18:01 192.168.122.209 [40431.899832] [tdb] Shutdown Tempesta DB Apr 26 03:18:01 192.168.122.209 [40432.125046] End test: http2_general.test_h2_headers.TestContentTypeWithEmptyBodyPATCH.test_request_success Apr 26 03:18:01 192.168.122.209 [40432.134629] Start test: http2_general.test_h2_headers.TestContentTypeWithEmptyBodyPOST.test_request_success Apr 26 03:18:03 192.168.122.209 [40433.345656] [tdb] Start Tempesta DB Apr 26 03:18:03 192.168.122.209 [40433.498180] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:18:04 192.168.122.209 [40434.790671] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40434.790671] Maybe that's fine, but it's worth checking the [40434.790671] config - if there is no relations between the [40434.790671] names, then host name confusion attack is possible. Apr 26 03:18:04 192.168.122.209 [40434.913982] [tempesta fw] Configuration processing is completed. Apr 26 03:18:04 192.168.122.209 [40434.963055] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:18:05 192.168.122.209 [40435.369701] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:18:05 192.168.122.209 [40435.396823] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:18:05 192.168.122.209 [40435.424995] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:18:05 192.168.122.209 [40435.509864] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:18:05 192.168.122.209 [40435.553806] [tempesta fw] Tempesta FW is ready Apr 26 03:18:05 192.168.122.209 [40435.689946] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 03:18:05 192.168.122.209 [40435.692239] [tempesta fw] Warning: Can't create pipelined response: 127.0.0.3 Apr 26 03:18:05 192.168.122.209 [40435.694267] [tempesta fw] 127.0.0.2 "default" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800a80200" Apr 26 03:18:05 192.168.122.209 [40436.135123] [tdb] Close table 'client0.tdb' Apr 26 03:18:06 192.168.122.209 [40436.409128] [tdb] Close table 'sessions0.tdb' Apr 26 03:18:09 192.168.122.209 [40439.594705] [tdb] Close table 'cache0.tdb' Apr 26 03:18:09 192.168.122.209 [40439.829682] [tdb] Close table 'filter0.tdb' Apr 26 03:18:09 192.168.122.209 [40439.830146] [tempesta fw] modules are stopped Apr 26 03:18:09 192.168.122.209 [40440.060534] [tempesta fw] exiting... Apr 26 03:18:09 192.168.122.209 [40440.181950] [tdb] Shutdown Tempesta DB Apr 26 03:18:10 192.168.122.209 [40440.432971] End test: http2_general.test_h2_headers.TestContentTypeWithEmptyBodyPOST.test_request_success Apr 26 03:18:10 192.168.122.209 [40440.449268] Start test: http2_general.test_h2_headers.TestContentTypeWithEmptyBodyPUT.test_request_success Apr 26 03:18:11 192.168.122.209 [40441.640125] [tdb] Start Tempesta DB Apr 26 03:18:11 192.168.122.209 [40441.781505] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:18:12 192.168.122.209 [40443.147415] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40443.147415] Maybe that's fine, but it's worth checking the [40443.147415] config - if there is no relations between the [40443.147415] names, then host name confusion attack is possible. Apr 26 03:18:12 192.168.122.209 [40443.278034] [tempesta fw] Configuration processing is completed. Apr 26 03:18:13 192.168.122.209 [40443.332091] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:18:13 192.168.122.209 [40443.750391] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:18:13 192.168.122.209 [40443.776964] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:18:13 192.168.122.209 [40443.802508] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:18:13 192.168.122.209 [40443.845994] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:18:13 192.168.122.209 [40443.885933] [tempesta fw] Tempesta FW is ready Apr 26 03:18:13 192.168.122.209 [40444.017171] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 03:18:13 192.168.122.209 [40444.018082] [tempesta fw] Warning: Can't create pipelined response: 127.0.0.3 Apr 26 03:18:13 192.168.122.209 [40444.018728] [tempesta fw] 127.0.0.2 "default" "PUT / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800b40200" Apr 26 03:18:14 192.168.122.209 [40444.468417] [tdb] Close table 'client0.tdb' Apr 26 03:18:14 192.168.122.209 [40444.670899] [tdb] Close table 'sessions0.tdb' Apr 26 03:18:17 192.168.122.209 [40447.848401] [tdb] Close table 'cache0.tdb' Apr 26 03:18:17 192.168.122.209 [40448.072635] [tdb] Close table 'filter0.tdb' Apr 26 03:18:17 192.168.122.209 [40448.073064] [tempesta fw] modules are stopped Apr 26 03:18:17 192.168.122.209 [40448.285212] [tempesta fw] exiting... Apr 26 03:18:18 192.168.122.209 [40448.443260] [tdb] Shutdown Tempesta DB Apr 26 03:18:18 192.168.122.209 [40448.697248] End test: http2_general.test_h2_headers.TestContentTypeWithEmptyBodyPUT.test_request_success Apr 26 03:18:18 192.168.122.209 [40448.708358] Start test: http2_general.test_h2_headers.TestH2Host.test_different_host_and_authority_headers Apr 26 03:18:19 192.168.122.209 [40449.816066] [tdb] Start Tempesta DB Apr 26 03:18:19 192.168.122.209 [40449.963228] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:18:21 192.168.122.209 [40451.547502] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40451.547502] Maybe that's fine, but it's worth checking the [40451.547502] config - if there is no relations between the [40451.547502] names, then host name confusion attack is possible. Apr 26 03:18:21 192.168.122.209 [40451.714140] [tempesta fw] Configuration processing is completed. Apr 26 03:18:21 192.168.122.209 [40451.769033] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:18:21 192.168.122.209 [40452.168394] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:18:21 192.168.122.209 [40452.193602] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:18:21 192.168.122.209 [40452.218981] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:18:21 192.168.122.209 [40452.266086] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:18:21 192.168.122.209 [40452.310024] [tempesta fw] Tempesta FW is ready Apr 26 03:18:22 192.168.122.209 [40452.925977] [tdb] Close table 'client0.tdb' Apr 26 03:18:22 192.168.122.209 [40453.089763] [tdb] Close table 'sessions0.tdb' Apr 26 03:18:25 192.168.122.209 [40456.235115] [tdb] Close table 'cache0.tdb' Apr 26 03:18:26 192.168.122.209 [40456.472409] [tdb] Close table 'filter0.tdb' Apr 26 03:18:26 192.168.122.209 [40456.472849] [tempesta fw] modules are stopped Apr 26 03:18:26 192.168.122.209 [40456.722054] [tempesta fw] exiting... Apr 26 03:18:26 192.168.122.209 [40456.878241] [tdb] Shutdown Tempesta DB Apr 26 03:18:26 192.168.122.209 [40457.088900] End test: http2_general.test_h2_headers.TestH2Host.test_different_host_and_authority_headers Apr 26 03:18:26 192.168.122.209 [40457.101080] Start test: http2_general.test_h2_headers.TestH2Host.test_empty_authority_header Apr 26 03:18:27 192.168.122.209 [40458.237382] [tdb] Start Tempesta DB Apr 26 03:18:28 192.168.122.209 [40458.399588] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:18:29 192.168.122.209 [40459.988440] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40459.988440] Maybe that's fine, but it's worth checking the [40459.988440] config - if there is no relations between the [40459.988440] names, then host name confusion attack is possible. Apr 26 03:18:29 192.168.122.209 [40460.130507] [tempesta fw] Configuration processing is completed. Apr 26 03:18:29 192.168.122.209 [40460.180109] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:18:30 192.168.122.209 [40460.582734] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:18:30 192.168.122.209 [40460.608096] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:18:30 192.168.122.209 [40460.633317] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:18:30 192.168.122.209 [40460.682180] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:18:30 192.168.122.209 [40460.726143] [tempesta fw] Tempesta FW is ready Apr 26 03:18:30 192.168.122.209 [40461.279343] [tdb] Close table 'client0.tdb' Apr 26 03:18:31 192.168.122.209 [40461.487948] [tdb] Close table 'sessions0.tdb' Apr 26 03:18:34 192.168.122.209 [40464.672510] [tdb] Close table 'cache0.tdb' Apr 26 03:18:34 192.168.122.209 [40464.924863] [tdb] Close table 'filter0.tdb' Apr 26 03:18:34 192.168.122.209 [40464.925323] [tempesta fw] modules are stopped Apr 26 03:18:34 192.168.122.209 [40465.155780] [tempesta fw] exiting... Apr 26 03:18:35 192.168.122.209 [40465.320937] [tdb] Shutdown Tempesta DB Apr 26 03:18:35 192.168.122.209 [40465.532674] End test: http2_general.test_h2_headers.TestH2Host.test_empty_authority_header Apr 26 03:18:35 192.168.122.209 [40465.544233] Start test: http2_general.test_h2_headers.TestH2Host.test_empty_host_header Apr 26 03:18:36 192.168.122.209 [40466.753089] [tdb] Start Tempesta DB Apr 26 03:18:36 192.168.122.209 [40466.914382] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:18:38 192.168.122.209 [40468.475702] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40468.475702] Maybe that's fine, but it's worth checking the [40468.475702] config - if there is no relations between the [40468.475702] names, then host name confusion attack is possible. Apr 26 03:18:38 192.168.122.209 [40468.634317] [tempesta fw] Configuration processing is completed. Apr 26 03:18:38 192.168.122.209 [40468.716544] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:18:38 192.168.122.209 [40469.141449] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:18:38 192.168.122.209 [40469.168046] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:18:38 192.168.122.209 [40469.196198] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:18:38 192.168.122.209 [40469.242291] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:18:38 192.168.122.209 [40469.290261] [tempesta fw] Tempesta FW is ready Apr 26 03:18:39 192.168.122.209 [40469.898051] [tdb] Close table 'client0.tdb' Apr 26 03:18:39 192.168.122.209 [40470.085197] [tdb] Close table 'sessions0.tdb' Apr 26 03:18:42 192.168.122.209 [40473.253196] [tdb] Close table 'cache0.tdb' Apr 26 03:18:43 192.168.122.209 [40473.510703] [tdb] Close table 'filter0.tdb' Apr 26 03:18:43 192.168.122.209 [40473.511147] [tempesta fw] modules are stopped Apr 26 03:18:43 192.168.122.209 [40473.754266] [tempesta fw] exiting... Apr 26 03:18:43 192.168.122.209 [40473.923303] [tdb] Shutdown Tempesta DB Apr 26 03:18:43 192.168.122.209 [40474.161236] End test: http2_general.test_h2_headers.TestH2Host.test_empty_host_header Apr 26 03:18:43 192.168.122.209 [40474.173253] Start test: http2_general.test_h2_headers.TestH2Host.test_forwarded_and_empty_host_header Apr 26 03:18:45 192.168.122.209 [40475.345101] [tdb] Start Tempesta DB Apr 26 03:18:45 192.168.122.209 [40475.513270] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:18:46 192.168.122.209 [40477.019847] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40477.019847] Maybe that's fine, but it's worth checking the [40477.019847] config - if there is no relations between the [40477.019847] names, then host name confusion attack is possible. Apr 26 03:18:46 192.168.122.209 [40477.174408] [tempesta fw] Configuration processing is completed. Apr 26 03:18:46 192.168.122.209 [40477.225420] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:18:47 192.168.122.209 [40477.631696] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:18:47 192.168.122.209 [40477.657135] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:18:47 192.168.122.209 [40477.682381] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:18:47 192.168.122.209 [40477.730404] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:18:47 192.168.122.209 [40477.770362] [tempesta fw] Tempesta FW is ready Apr 26 03:18:48 192.168.122.209 [40478.377380] [tdb] Close table 'client0.tdb' Apr 26 03:18:48 192.168.122.209 [40478.559704] [tdb] Close table 'sessions0.tdb' Apr 26 03:18:51 192.168.122.209 [40481.743229] [tdb] Close table 'cache0.tdb' Apr 26 03:18:51 192.168.122.209 [40481.992176] [tdb] Close table 'filter0.tdb' Apr 26 03:18:51 192.168.122.209 [40481.992769] [tempesta fw] modules are stopped Apr 26 03:18:51 192.168.122.209 [40482.194823] [tempesta fw] exiting... Apr 26 03:18:52 192.168.122.209 [40482.350153] [tdb] Shutdown Tempesta DB Apr 26 03:18:52 192.168.122.209 [40482.561653] End test: http2_general.test_h2_headers.TestH2Host.test_forwarded_and_empty_host_header Apr 26 03:18:52 192.168.122.209 [40482.577250] Start test: http2_general.test_h2_headers.TestH2Host.test_host_authority_ok Apr 26 03:18:53 192.168.122.209 [40483.723206] [tdb] Start Tempesta DB Apr 26 03:18:53 192.168.122.209 [40483.892463] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:18:55 192.168.122.209 [40485.412496] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40485.412496] Maybe that's fine, but it's worth checking the [40485.412496] config - if there is no relations between the [40485.412496] names, then host name confusion attack is possible. Apr 26 03:18:55 192.168.122.209 [40485.570560] [tempesta fw] Configuration processing is completed. Apr 26 03:18:55 192.168.122.209 [40485.621716] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:18:55 192.168.122.209 [40486.030791] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:18:55 192.168.122.209 [40486.056533] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:18:55 192.168.122.209 [40486.082497] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:18:55 192.168.122.209 [40486.134528] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:18:55 192.168.122.209 [40486.182475] [tempesta fw] Tempesta FW is ready Apr 26 03:18:56 192.168.122.209 [40486.772746] [tdb] Close table 'client0.tdb' Apr 26 03:18:56 192.168.122.209 [40486.972515] [tdb] Close table 'sessions0.tdb' Apr 26 03:18:59 192.168.122.209 [40490.135400] [tdb] Close table 'cache0.tdb' Apr 26 03:19:00 192.168.122.209 [40490.369681] [tdb] Close table 'filter0.tdb' Apr 26 03:19:00 192.168.122.209 [40490.370114] [tempesta fw] modules are stopped Apr 26 03:19:00 192.168.122.209 [40490.650616] [tempesta fw] exiting... Apr 26 03:19:00 192.168.122.209 [40490.802916] [tdb] Shutdown Tempesta DB Apr 26 03:19:00 192.168.122.209 [40491.035004] End test: http2_general.test_h2_headers.TestH2Host.test_host_authority_ok Apr 26 03:19:00 192.168.122.209 [40491.049479] Start test: http2_general.test_h2_headers.TestH2Host.test_host_header_ok Apr 26 03:19:01 192.168.122.209 [40492.189675] [tdb] Start Tempesta DB Apr 26 03:19:02 192.168.122.209 [40492.332847] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:19:03 192.168.122.209 [40493.895192] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40493.895192] Maybe that's fine, but it's worth checking the [40493.895192] config - if there is no relations between the [40493.895192] names, then host name confusion attack is possible. Apr 26 03:19:03 192.168.122.209 [40494.050658] [tempesta fw] Configuration processing is completed. Apr 26 03:19:03 192.168.122.209 [40494.147700] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:19:04 192.168.122.209 [40494.563328] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:19:04 192.168.122.209 [40494.590097] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:19:04 192.168.122.209 [40494.617485] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:19:04 192.168.122.209 [40494.662622] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:19:04 192.168.122.209 [40494.710570] [tempesta fw] Tempesta FW is ready Apr 26 03:19:05 192.168.122.209 [40495.321048] [tdb] Close table 'client0.tdb' Apr 26 03:19:05 192.168.122.209 [40495.511424] [tdb] Close table 'sessions0.tdb' Apr 26 03:19:08 192.168.122.209 [40498.697020] [tdb] Close table 'cache0.tdb' Apr 26 03:19:08 192.168.122.209 [40498.937642] [tdb] Close table 'filter0.tdb' Apr 26 03:19:08 192.168.122.209 [40498.938306] [tempesta fw] modules are stopped Apr 26 03:19:08 192.168.122.209 [40499.164656] [tempesta fw] exiting... Apr 26 03:19:08 192.168.122.209 [40499.310214] [tdb] Shutdown Tempesta DB Apr 26 03:19:09 192.168.122.209 [40499.538161] End test: http2_general.test_h2_headers.TestH2Host.test_host_header_ok Apr 26 03:19:09 192.168.122.209 [40499.547543] Start test: http2_general.test_h2_headers.TestH2Host.test_host_missing Apr 26 03:19:10 192.168.122.209 [40500.698148] [tdb] Start Tempesta DB Apr 26 03:19:10 192.168.122.209 [40500.857246] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:19:12 192.168.122.209 [40502.456191] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40502.456191] Maybe that's fine, but it's worth checking the [40502.456191] config - if there is no relations between the [40502.456191] names, then host name confusion attack is possible. Apr 26 03:19:12 192.168.122.209 [40502.614761] [tempesta fw] Configuration processing is completed. Apr 26 03:19:12 192.168.122.209 [40502.664564] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:19:12 192.168.122.209 [40503.080960] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:19:12 192.168.122.209 [40503.106499] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:19:12 192.168.122.209 [40503.131634] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:19:12 192.168.122.209 [40503.178725] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:19:12 192.168.122.209 [40503.218679] [tempesta fw] Tempesta FW is ready Apr 26 03:19:13 192.168.122.209 [40503.376121] [tempesta fw] Warning: Invalid authority: 127.0.0.2 Apr 26 03:19:13 192.168.122.209 [40503.800703] [tdb] Close table 'client0.tdb' Apr 26 03:19:13 192.168.122.209 [40503.984066] [tdb] Close table 'sessions0.tdb' Apr 26 03:19:16 192.168.122.209 [40507.244405] [tdb] Close table 'cache0.tdb' Apr 26 03:19:17 192.168.122.209 [40507.493075] [tdb] Close table 'filter0.tdb' Apr 26 03:19:17 192.168.122.209 [40507.493545] [tempesta fw] modules are stopped Apr 26 03:19:17 192.168.122.209 [40507.765962] [tempesta fw] exiting... Apr 26 03:19:17 192.168.122.209 [40507.934305] [tdb] Shutdown Tempesta DB Apr 26 03:19:17 192.168.122.209 [40508.129524] End test: http2_general.test_h2_headers.TestH2Host.test_host_missing Apr 26 03:19:17 192.168.122.209 [40508.141176] Start test: http2_general.test_h2_headers.TestHeadersBlockedByMaxHeaderListSize.test_blocked_by_max_headers_count_huffman Apr 26 03:19:19 192.168.122.209 [40509.342866] [tdb] Start Tempesta DB Apr 26 03:19:19 192.168.122.209 [40509.510888] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:19:20 192.168.122.209 [40511.020206] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40511.020206] Maybe that's fine, but it's worth checking the [40511.020206] config - if there is no relations between the [40511.020206] names, then host name confusion attack is possible. Apr 26 03:19:20 192.168.122.209 [40511.102878] [tempesta fw] Configuration processing is completed. Apr 26 03:19:20 192.168.122.209 [40511.157551] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:19:21 192.168.122.209 [40511.663226] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:19:21 192.168.122.209 [40511.702447] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:19:21 192.168.122.209 [40511.734226] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:19:21 192.168.122.209 [40511.778862] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:19:21 192.168.122.209 [40511.830783] [tempesta fw] Tempesta FW is ready Apr 26 03:19:21 192.168.122.209 [40511.983095] [tempesta fw] Warning: frang: HTTP header list size exceeded for 127.0.0.2: 251 (lim=250) Apr 26 03:19:22 192.168.122.209 [40512.428506] [tdb] Close table 'client0.tdb' Apr 26 03:19:22 192.168.122.209 [40512.629332] [tdb] Close table 'sessions0.tdb' Apr 26 03:19:25 192.168.122.209 [40515.832527] [tdb] Close table 'cache0.tdb' Apr 26 03:19:25 192.168.122.209 [40516.078662] [tdb] Close table 'filter0.tdb' Apr 26 03:19:25 192.168.122.209 [40516.079109] [tempesta fw] modules are stopped Apr 26 03:19:25 192.168.122.209 [40516.284470] [tempesta fw] exiting... Apr 26 03:19:26 192.168.122.209 [40516.452374] [tdb] Shutdown Tempesta DB Apr 26 03:19:26 192.168.122.209 [40516.668995] End test: http2_general.test_h2_headers.TestHeadersBlockedByMaxHeaderListSize.test_blocked_by_max_headers_count_huffman Apr 26 03:19:26 192.168.122.209 [40516.678559] Start test: http2_general.test_h2_headers.TestHeadersBlockedByMaxHeaderListSize.test_blocked_by_max_headers_count_no_huffman Apr 26 03:19:27 192.168.122.209 [40517.928094] [tdb] Start Tempesta DB Apr 26 03:19:27 192.168.122.209 [40518.073312] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:19:29 192.168.122.209 [40519.608337] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40519.608337] Maybe that's fine, but it's worth checking the [40519.608337] config - if there is no relations between the [40519.608337] names, then host name confusion attack is possible. Apr 26 03:19:29 192.168.122.209 [40519.687006] [tempesta fw] Configuration processing is completed. Apr 26 03:19:29 192.168.122.209 [40519.777766] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:19:29 192.168.122.209 [40520.213513] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:19:29 192.168.122.209 [40520.240554] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:19:29 192.168.122.209 [40520.270292] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:19:30 192.168.122.209 [40520.322990] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:19:30 192.168.122.209 [40520.362907] [tempesta fw] Tempesta FW is ready Apr 26 03:19:30 192.168.122.209 [40520.522022] [tempesta fw] Warning: frang: HTTP header list size exceeded for 127.0.0.2: 251 (lim=250) Apr 26 03:19:30 192.168.122.209 [40521.001827] [tdb] Close table 'client0.tdb' Apr 26 03:19:30 192.168.122.209 [40521.196615] [tdb] Close table 'sessions0.tdb' Apr 26 03:19:34 192.168.122.209 [40524.421809] [tdb] Close table 'cache0.tdb' Apr 26 03:19:34 192.168.122.209 [40524.651633] [tdb] Close table 'filter0.tdb' Apr 26 03:19:34 192.168.122.209 [40524.652070] [tempesta fw] modules are stopped Apr 26 03:19:34 192.168.122.209 [40524.884909] [tempesta fw] exiting... Apr 26 03:19:34 192.168.122.209 [40525.042025] [tdb] Shutdown Tempesta DB Apr 26 03:19:34 192.168.122.209 [40525.252383] End test: http2_general.test_h2_headers.TestHeadersBlockedByMaxHeaderListSize.test_blocked_by_max_headers_count_no_huffman Apr 26 03:19:34 192.168.122.209 [40525.264199] Start test: http2_general.test_h2_headers.TestHeadersBlockedByMaxHeaderListSize.test_not_blocked_by_max_headers_count_huffman Apr 26 03:19:36 192.168.122.209 [40526.444219] [tdb] Start Tempesta DB Apr 26 03:19:36 192.168.122.209 [40526.591801] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:19:37 192.168.122.209 [40528.020221] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40528.020221] Maybe that's fine, but it's worth checking the [40528.020221] config - if there is no relations between the [40528.020221] names, then host name confusion attack is possible. Apr 26 03:19:37 192.168.122.209 [40528.127073] [tempesta fw] Configuration processing is completed. Apr 26 03:19:37 192.168.122.209 [40528.181545] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:19:38 192.168.122.209 [40528.599904] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:19:38 192.168.122.209 [40528.630431] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:19:38 192.168.122.209 [40528.661923] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:19:38 192.168.122.209 [40528.727025] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:19:38 192.168.122.209 [40528.767024] [tempesta fw] Tempesta FW is ready Apr 26 03:19:39 192.168.122.209 [40529.353371] [tdb] Close table 'client0.tdb' Apr 26 03:19:39 192.168.122.209 [40529.542857] [tdb] Close table 'sessions0.tdb' Apr 26 03:19:42 192.168.122.209 [40532.826319] [tdb] Close table 'cache0.tdb' Apr 26 03:19:42 192.168.122.209 [40533.073247] [tdb] Close table 'filter0.tdb' Apr 26 03:19:42 192.168.122.209 [40533.073699] [tempesta fw] modules are stopped Apr 26 03:19:42 192.168.122.209 [40533.285358] [tempesta fw] exiting... Apr 26 03:19:43 192.168.122.209 [40533.417065] [tdb] Shutdown Tempesta DB Apr 26 03:19:43 192.168.122.209 [40533.656797] End test: http2_general.test_h2_headers.TestHeadersBlockedByMaxHeaderListSize.test_not_blocked_by_max_headers_count_huffman Apr 26 03:19:43 192.168.122.209 [40533.670515] Start test: http2_general.test_h2_headers.TestHeadersBlockedByMaxHeaderListSize.test_not_blocked_by_max_headers_count_no_huffman Apr 26 03:19:44 192.168.122.209 [40534.874433] [tdb] Start Tempesta DB Apr 26 03:19:44 192.168.122.209 [40535.036001] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:19:46 192.168.122.209 [40536.528517] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40536.528517] Maybe that's fine, but it's worth checking the [40536.528517] config - if there is no relations between the [40536.528517] names, then host name confusion attack is possible. Apr 26 03:19:46 192.168.122.209 [40536.623222] [tempesta fw] Configuration processing is completed. Apr 26 03:19:46 192.168.122.209 [40536.674299] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:19:46 192.168.122.209 [40537.094494] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:19:46 192.168.122.209 [40537.122424] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:19:46 192.168.122.209 [40537.148825] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:19:46 192.168.122.209 [40537.191112] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:19:46 192.168.122.209 [40537.231132] [tempesta fw] Tempesta FW is ready Apr 26 03:19:47 192.168.122.209 [40537.800386] [tdb] Close table 'client0.tdb' Apr 26 03:19:47 192.168.122.209 [40537.986405] [tdb] Close table 'sessions0.tdb' Apr 26 03:19:50 192.168.122.209 [40541.138639] [tdb] Close table 'cache0.tdb' Apr 26 03:19:51 192.168.122.209 [40541.394646] [tdb] Close table 'filter0.tdb' Apr 26 03:19:51 192.168.122.209 [40541.395117] [tempesta fw] modules are stopped Apr 26 03:19:51 192.168.122.209 [40541.619704] [tempesta fw] exiting... Apr 26 03:19:51 192.168.122.209 [40541.757666] [tdb] Shutdown Tempesta DB Apr 26 03:19:51 192.168.122.209 [40541.967781] End test: http2_general.test_h2_headers.TestHeadersBlockedByMaxHeaderListSize.test_not_blocked_by_max_headers_count_no_huffman Apr 26 03:19:51 192.168.122.209 [40541.979868] Start test: http2_general.test_h2_headers.TestNoContentLengthInMethodMethodDELETE.test_request_success Apr 26 03:19:52 192.168.122.209 [40543.109772] [tdb] Start Tempesta DB Apr 26 03:19:52 192.168.122.209 [40543.262608] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:19:54 192.168.122.209 [40544.632483] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40544.632483] Maybe that's fine, but it's worth checking the [40544.632483] config - if there is no relations between the [40544.632483] names, then host name confusion attack is possible. Apr 26 03:19:54 192.168.122.209 [40544.759349] [tempesta fw] Configuration processing is completed. Apr 26 03:19:54 192.168.122.209 [40544.842602] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:19:54 192.168.122.209 [40545.276479] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:19:54 192.168.122.209 [40545.303233] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:19:55 192.168.122.209 [40545.330768] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:19:55 192.168.122.209 [40545.371235] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:19:55 192.168.122.209 [40545.419218] [tempesta fw] Tempesta FW is ready Apr 26 03:19:55 192.168.122.209 [40545.574985] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 03:19:55 192.168.122.209 [40545.576075] [tempesta fw] Warning: Can't create pipelined response: 127.0.0.3 Apr 26 03:19:55 192.168.122.209 [40545.576985] [tempesta fw] 127.0.0.2 "default" "DELETE / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800880200" Apr 26 03:19:55 192.168.122.209 [40545.589953] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 03:19:55 192.168.122.209 [40545.592252] [tempesta fw] Warning: Can't create pipelined response: 127.0.0.3 Apr 26 03:19:55 192.168.122.209 [40545.594223] [tempesta fw] 127.0.0.2 "default" "DELETE / HTTP/2.0" 201 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800880200" Apr 26 03:19:55 192.168.122.209 [40545.600524] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 03:19:55 192.168.122.209 [40545.602832] [tempesta fw] 127.0.0.2 "default" "DELETE / HTTP/2.0" 302 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800880200" Apr 26 03:19:55 192.168.122.209 [40545.611972] [tempesta fw] 127.0.0.2 "default" "DELETE / HTTP/2.0" 304 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800880200" Apr 26 03:19:55 192.168.122.209 [40545.620906] [tempesta fw] 127.0.0.2 "default" "DELETE / HTTP/2.0" 400 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800880200" Apr 26 03:19:55 192.168.122.209 [40545.631654] [tempesta fw] 127.0.0.2 "default" "DELETE / HTTP/2.0" 401 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800880200" Apr 26 03:19:55 192.168.122.209 [40545.641763] [tempesta fw] 127.0.0.2 "default" "DELETE / HTTP/2.0" 404 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800880200" Apr 26 03:19:55 192.168.122.209 [40545.652437] [tempesta fw] 127.0.0.2 "default" "DELETE / HTTP/2.0" 500 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800880200" Apr 26 03:19:55 192.168.122.209 [40546.093998] [tdb] Close table 'client0.tdb' Apr 26 03:19:55 192.168.122.209 [40546.286930] [tdb] Close table 'sessions0.tdb' Apr 26 03:19:59 192.168.122.209 [40549.495083] [tdb] Close table 'cache0.tdb' Apr 26 03:19:59 192.168.122.209 [40549.719698] [tdb] Close table 'filter0.tdb' Apr 26 03:19:59 192.168.122.209 [40549.720146] net_ratelimit: 11 callbacks suppressed Apr 26 03:19:59 192.168.122.209 [40549.720147] [tempesta fw] modules are stopped Apr 26 03:19:59 192.168.122.209 [40549.979412] [tempesta fw] exiting... Apr 26 03:19:59 192.168.122.209 [40550.123830] [tdb] Shutdown Tempesta DB Apr 26 03:20:00 192.168.122.209 [40550.316786] End test: http2_general.test_h2_headers.TestNoContentLengthInMethodMethodDELETE.test_request_success Apr 26 03:20:00 192.168.122.209 [40550.336011] Start test: http2_general.test_h2_headers.TestNoContentLengthInMethodMethodGET.test_request_success Apr 26 03:20:01 192.168.122.209 [40551.470599] [tdb] Start Tempesta DB Apr 26 03:20:01 192.168.122.209 [40551.633276] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:20:02 192.168.122.209 [40553.004614] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40553.004614] Maybe that's fine, but it's worth checking the [40553.004614] config - if there is no relations between the [40553.004614] names, then host name confusion attack is possible. Apr 26 03:20:02 192.168.122.209 [40553.131457] [tempesta fw] Configuration processing is completed. Apr 26 03:20:02 192.168.122.209 [40553.193304] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:20:03 192.168.122.209 [40553.596956] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:20:03 192.168.122.209 [40553.622467] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:20:03 192.168.122.209 [40553.647441] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:20:03 192.168.122.209 [40553.695366] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:20:03 192.168.122.209 [40553.743326] [tempesta fw] Tempesta FW is ready Apr 26 03:20:03 192.168.122.209 [40553.901972] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 03:20:03 192.168.122.209 [40553.903451] [tempesta fw] Warning: Can't create pipelined response: 127.0.0.3 Apr 26 03:20:03 192.168.122.209 [40553.904713] [tempesta fw] 127.0.0.2 "default" "GET / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=178008c0200" Apr 26 03:20:03 192.168.122.209 [40553.913091] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 03:20:03 192.168.122.209 [40553.915041] [tempesta fw] Warning: Can't create pipelined response: 127.0.0.3 Apr 26 03:20:03 192.168.122.209 [40553.916760] [tempesta fw] 127.0.0.2 "default" "GET / HTTP/2.0" 302 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=178008c0200" Apr 26 03:20:03 192.168.122.209 [40553.923299] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 03:20:03 192.168.122.209 [40553.924412] [tempesta fw] 127.0.0.2 "default" "GET / HTTP/2.0" 304 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=178008c0200" Apr 26 03:20:03 192.168.122.209 [40553.933804] [tempesta fw] 127.0.0.2 "default" "GET / HTTP/2.0" 400 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=178008c0200" Apr 26 03:20:03 192.168.122.209 [40553.944796] [tempesta fw] 127.0.0.2 "default" "GET / HTTP/2.0" 401 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=178008c0200" Apr 26 03:20:03 192.168.122.209 [40553.955771] [tempesta fw] 127.0.0.2 "default" "GET / HTTP/2.0" 404 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=178008c0200" Apr 26 03:20:03 192.168.122.209 [40553.966275] [tempesta fw] 127.0.0.2 "default" "GET / HTTP/2.0" 500 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=178008c0200" Apr 26 03:20:04 192.168.122.209 [40554.444002] [tdb] Close table 'client0.tdb' Apr 26 03:20:04 192.168.122.209 [40554.633208] [tdb] Close table 'sessions0.tdb' Apr 26 03:20:07 192.168.122.209 [40557.737369] [tdb] Close table 'cache0.tdb' Apr 26 03:20:07 192.168.122.209 [40557.981209] [tdb] Close table 'filter0.tdb' Apr 26 03:20:07 192.168.122.209 [40557.981639] net_ratelimit: 9 callbacks suppressed Apr 26 03:20:07 192.168.122.209 [40557.981641] [tempesta fw] modules are stopped Apr 26 03:20:07 192.168.122.209 [40558.162283] [tempesta fw] exiting... Apr 26 03:20:07 192.168.122.209 [40558.312751] [tdb] Shutdown Tempesta DB Apr 26 03:20:08 192.168.122.209 [40558.522738] End test: http2_general.test_h2_headers.TestNoContentLengthInMethodMethodGET.test_request_success Apr 26 03:20:08 192.168.122.209 [40558.538533] Start test: http2_general.test_h2_headers.TestNoContentLengthInMethodMethodHEAD.test_request_success Apr 26 03:20:09 192.168.122.209 [40559.669395] [tdb] Start Tempesta DB Apr 26 03:20:09 192.168.122.209 [40559.811036] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:20:10 192.168.122.209 [40561.128707] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40561.128707] Maybe that's fine, but it's worth checking the [40561.128707] config - if there is no relations between the [40561.128707] names, then host name confusion attack is possible. Apr 26 03:20:10 192.168.122.209 [40561.259507] [tempesta fw] Configuration processing is completed. Apr 26 03:20:10 192.168.122.209 [40561.309444] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:20:11 192.168.122.209 [40561.738905] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:20:11 192.168.122.209 [40561.764955] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:20:11 192.168.122.209 [40561.790596] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:20:11 192.168.122.209 [40561.835486] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:20:11 192.168.122.209 [40561.891432] [tempesta fw] Tempesta FW is ready Apr 26 03:20:11 192.168.122.209 [40562.032273] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 03:20:11 192.168.122.209 [40562.034599] [tempesta fw] Warning: Can't create pipelined response: 127.0.0.3 Apr 26 03:20:11 192.168.122.209 [40562.036645] [tempesta fw] 127.0.0.2 "default" "HEAD / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800900200" Apr 26 03:20:12 192.168.122.209 [40562.489546] [tdb] Close table 'client0.tdb' Apr 26 03:20:12 192.168.122.209 [40562.686364] [tdb] Close table 'sessions0.tdb' Apr 26 03:20:15 192.168.122.209 [40565.890559] [tdb] Close table 'cache0.tdb' Apr 26 03:20:15 192.168.122.209 [40566.114744] [tdb] Close table 'filter0.tdb' Apr 26 03:20:15 192.168.122.209 [40566.115187] [tempesta fw] modules are stopped Apr 26 03:20:15 192.168.122.209 [40566.291887] [tempesta fw] exiting... Apr 26 03:20:16 192.168.122.209 [40566.453911] [tdb] Shutdown Tempesta DB Apr 26 03:20:16 192.168.122.209 [40566.701885] End test: http2_general.test_h2_headers.TestNoContentLengthInMethodMethodHEAD.test_request_success Apr 26 03:20:16 192.168.122.209 [40566.714687] Start test: http2_general.test_h2_headers.TestNoContentLengthInMethodMethodPATCH.test_request_success Apr 26 03:20:17 192.168.122.209 [40567.831167] [tdb] Start Tempesta DB Apr 26 03:20:17 192.168.122.209 [40567.974484] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:20:18 192.168.122.209 [40569.244858] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40569.244858] Maybe that's fine, but it's worth checking the [40569.244858] config - if there is no relations between the [40569.244858] names, then host name confusion attack is possible. Apr 26 03:20:19 192.168.122.209 [40569.367645] [tempesta fw] Configuration processing is completed. Apr 26 03:20:19 192.168.122.209 [40569.417889] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:20:19 192.168.122.209 [40569.831739] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:20:19 192.168.122.209 [40569.857305] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:20:19 192.168.122.209 [40569.883100] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:20:19 192.168.122.209 [40569.931594] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:20:19 192.168.122.209 [40569.971551] [tempesta fw] Tempesta FW is ready Apr 26 03:20:19 192.168.122.209 [40570.118793] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 03:20:19 192.168.122.209 [40570.121152] [tempesta fw] Warning: Can't create pipelined response: 127.0.0.3 Apr 26 03:20:19 192.168.122.209 [40570.123173] [tempesta fw] 127.0.0.2 "default" "PATCH / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800a40200" Apr 26 03:20:19 192.168.122.209 [40570.129019] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 03:20:19 192.168.122.209 [40570.131307] [tempesta fw] Warning: Can't create pipelined response: 127.0.0.3 Apr 26 03:20:19 192.168.122.209 [40570.133309] [tempesta fw] 127.0.0.2 "default" "PATCH / HTTP/2.0" 201 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800a40200" Apr 26 03:20:19 192.168.122.209 [40570.152008] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 03:20:19 192.168.122.209 [40570.154336] [tempesta fw] 127.0.0.2 "default" "PATCH / HTTP/2.0" 302 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800a40200" Apr 26 03:20:19 192.168.122.209 [40570.159838] [tempesta fw] 127.0.0.2 "default" "PATCH / HTTP/2.0" 304 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800a40200" Apr 26 03:20:19 192.168.122.209 [40570.170579] [tempesta fw] 127.0.0.2 "default" "PATCH / HTTP/2.0" 400 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800a40200" Apr 26 03:20:19 192.168.122.209 [40570.181549] [tempesta fw] 127.0.0.2 "default" "PATCH / HTTP/2.0" 401 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800a40200" Apr 26 03:20:19 192.168.122.209 [40570.192061] [tempesta fw] 127.0.0.2 "default" "PATCH / HTTP/2.0" 404 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800a40200" Apr 26 03:20:19 192.168.122.209 [40570.202728] [tempesta fw] 127.0.0.2 "default" "PATCH / HTTP/2.0" 500 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800a40200" Apr 26 03:20:20 192.168.122.209 [40570.653359] [tdb] Close table 'client0.tdb' Apr 26 03:20:20 192.168.122.209 [40570.862525] [tdb] Close table 'sessions0.tdb' Apr 26 03:20:23 192.168.122.209 [40574.046586] [tdb] Close table 'cache0.tdb' Apr 26 03:20:23 192.168.122.209 [40574.302299] [tdb] Close table 'filter0.tdb' Apr 26 03:20:23 192.168.122.209 [40574.302737] net_ratelimit: 11 callbacks suppressed Apr 26 03:20:23 192.168.122.209 [40574.302738] [tempesta fw] modules are stopped Apr 26 03:20:24 192.168.122.209 [40574.477562] [tempesta fw] exiting... Apr 26 03:20:24 192.168.122.209 [40574.649169] [tdb] Shutdown Tempesta DB Apr 26 03:20:24 192.168.122.209 [40574.857111] End test: http2_general.test_h2_headers.TestNoContentLengthInMethodMethodPATCH.test_request_success Apr 26 03:20:24 192.168.122.209 [40574.864398] Start test: http2_general.test_h2_headers.TestNoContentLengthInMethodMethodPOST.test_request_success Apr 26 03:20:25 192.168.122.209 [40576.041665] [tdb] Start Tempesta DB Apr 26 03:20:25 192.168.122.209 [40576.192171] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:20:27 192.168.122.209 [40577.488925] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40577.488925] Maybe that's fine, but it's worth checking the [40577.488925] config - if there is no relations between the [40577.488925] names, then host name confusion attack is possible. Apr 26 03:20:27 192.168.122.209 [40577.627706] [tempesta fw] Configuration processing is completed. Apr 26 03:20:27 192.168.122.209 [40577.677120] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:20:27 192.168.122.209 [40578.083381] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:20:27 192.168.122.209 [40578.140576] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:20:27 192.168.122.209 [40578.167387] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:20:27 192.168.122.209 [40578.207629] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:20:27 192.168.122.209 [40578.259636] [tempesta fw] Tempesta FW is ready Apr 26 03:20:28 192.168.122.209 [40578.396582] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 03:20:28 192.168.122.209 [40578.399294] [tempesta fw] Warning: Can't create pipelined response: 127.0.0.3 Apr 26 03:20:28 192.168.122.209 [40578.401358] [tempesta fw] 127.0.0.2 "default" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800a80200" Apr 26 03:20:28 192.168.122.209 [40578.406519] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 03:20:28 192.168.122.209 [40578.407902] [tempesta fw] Warning: Can't create pipelined response: 127.0.0.3 Apr 26 03:20:28 192.168.122.209 [40578.409107] [tempesta fw] 127.0.0.2 "default" "POST / HTTP/2.0" 201 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800a80200" Apr 26 03:20:28 192.168.122.209 [40578.427080] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 03:20:28 192.168.122.209 [40578.429409] [tempesta fw] 127.0.0.2 "default" "POST / HTTP/2.0" 302 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800a80200" Apr 26 03:20:28 192.168.122.209 [40578.437564] [tempesta fw] 127.0.0.2 "default" "POST / HTTP/2.0" 304 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800a80200" Apr 26 03:20:28 192.168.122.209 [40578.448004] [tempesta fw] 127.0.0.2 "default" "POST / HTTP/2.0" 400 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800a80200" Apr 26 03:20:28 192.168.122.209 [40578.461515] [tempesta fw] 127.0.0.2 "default" "POST / HTTP/2.0" 401 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800a80200" Apr 26 03:20:28 192.168.122.209 [40578.472415] [tempesta fw] 127.0.0.2 "default" "POST / HTTP/2.0" 404 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800a80200" Apr 26 03:20:28 192.168.122.209 [40578.482766] [tempesta fw] 127.0.0.2 "default" "POST / HTTP/2.0" 500 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800a80200" Apr 26 03:20:28 192.168.122.209 [40578.927315] [tdb] Close table 'client0.tdb' Apr 26 03:20:28 192.168.122.209 [40579.138410] [tdb] Close table 'sessions0.tdb' Apr 26 03:20:31 192.168.122.209 [40582.305015] [tdb] Close table 'cache0.tdb' Apr 26 03:20:32 192.168.122.209 [40582.548799] [tdb] Close table 'filter0.tdb' Apr 26 03:20:32 192.168.122.209 [40582.549251] net_ratelimit: 11 callbacks suppressed Apr 26 03:20:32 192.168.122.209 [40582.549253] [tempesta fw] modules are stopped Apr 26 03:20:32 192.168.122.209 [40582.739720] [tempesta fw] exiting... Apr 26 03:20:32 192.168.122.209 [40582.897061] [tdb] Shutdown Tempesta DB Apr 26 03:20:32 192.168.122.209 [40583.114296] End test: http2_general.test_h2_headers.TestNoContentLengthInMethodMethodPOST.test_request_success Apr 26 03:20:32 192.168.122.209 [40583.132127] Start test: http2_general.test_h2_headers.TestNoContentLengthInMethodMethodPUT.test_request_success Apr 26 03:20:34 192.168.122.209 [40584.327715] [tdb] Start Tempesta DB Apr 26 03:20:34 192.168.122.209 [40584.480769] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:20:35 192.168.122.209 [40585.837074] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40585.837074] Maybe that's fine, but it's worth checking the [40585.837074] config - if there is no relations between the [40585.837074] names, then host name confusion attack is possible. Apr 26 03:20:35 192.168.122.209 [40585.955848] [tempesta fw] Configuration processing is completed. Apr 26 03:20:35 192.168.122.209 [40586.006345] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:20:36 192.168.122.209 [40586.418766] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:20:36 192.168.122.209 [40586.445469] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:20:36 192.168.122.209 [40586.472689] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:20:36 192.168.122.209 [40586.515806] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:20:36 192.168.122.209 [40586.563758] [tempesta fw] Tempesta FW is ready Apr 26 03:20:36 192.168.122.209 [40586.709684] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 03:20:36 192.168.122.209 [40586.710685] [tempesta fw] Warning: Can't create pipelined response: 127.0.0.3 Apr 26 03:20:36 192.168.122.209 [40586.711532] [tempesta fw] 127.0.0.2 "default" "PUT / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800b40200" Apr 26 03:20:36 192.168.122.209 [40586.715115] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 03:20:36 192.168.122.209 [40586.716180] [tempesta fw] Warning: Can't create pipelined response: 127.0.0.3 Apr 26 03:20:36 192.168.122.209 [40586.717108] [tempesta fw] 127.0.0.2 "default" "PUT / HTTP/2.0" 201 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800b40200" Apr 26 03:20:36 192.168.122.209 [40586.725451] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 03:20:36 192.168.122.209 [40586.726574] [tempesta fw] 127.0.0.2 "default" "PUT / HTTP/2.0" 302 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800b40200" Apr 26 03:20:36 192.168.122.209 [40586.736561] [tempesta fw] 127.0.0.2 "default" "PUT / HTTP/2.0" 304 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800b40200" Apr 26 03:20:36 192.168.122.209 [40586.746538] [tempesta fw] 127.0.0.2 "default" "PUT / HTTP/2.0" 400 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800b40200" Apr 26 03:20:36 192.168.122.209 [40586.757327] [tempesta fw] 127.0.0.2 "default" "PUT / HTTP/2.0" 401 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800b40200" Apr 26 03:20:36 192.168.122.209 [40586.770200] [tempesta fw] 127.0.0.2 "default" "PUT / HTTP/2.0" 404 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800b40200" Apr 26 03:20:36 192.168.122.209 [40586.778696] [tempesta fw] 127.0.0.2 "default" "PUT / HTTP/2.0" 500 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800b40200" Apr 26 03:20:36 192.168.122.209 [40587.234644] [tdb] Close table 'client0.tdb' Apr 26 03:20:37 192.168.122.209 [40587.422158] [tdb] Close table 'sessions0.tdb' Apr 26 03:20:40 192.168.122.209 [40590.621553] [tdb] Close table 'cache0.tdb' Apr 26 03:20:40 192.168.122.209 [40590.860548] [tdb] Close table 'filter0.tdb' Apr 26 03:20:40 192.168.122.209 [40590.860997] net_ratelimit: 11 callbacks suppressed Apr 26 03:20:40 192.168.122.209 [40590.860998] [tempesta fw] modules are stopped Apr 26 03:20:40 192.168.122.209 [40591.083718] [tempesta fw] exiting... Apr 26 03:20:40 192.168.122.209 [40591.224838] [tdb] Shutdown Tempesta DB Apr 26 03:20:41 192.168.122.209 [40591.427325] End test: http2_general.test_h2_headers.TestNoContentLengthInMethodMethodPUT.test_request_success Apr 26 03:20:41 192.168.122.209 [40591.436889] Start test: http2_general.test_h2_headers.TestPseudoHeaders.test_authority_with_scheme_and_path Apr 26 03:20:42 192.168.122.209 [40592.584585] [tdb] Start Tempesta DB Apr 26 03:20:42 192.168.122.209 [40592.730284] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:20:44 192.168.122.209 [40594.404737] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40594.404737] Maybe that's fine, but it's worth checking the [40594.404737] config - if there is no relations between the [40594.404737] names, then host name confusion attack is possible. Apr 26 03:20:44 192.168.122.209 [40594.567917] [tempesta fw] Configuration processing is completed. Apr 26 03:20:44 192.168.122.209 [40594.617564] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:20:44 192.168.122.209 [40595.023271] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:20:44 192.168.122.209 [40595.080027] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:20:44 192.168.122.209 [40595.106747] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:20:44 192.168.122.209 [40595.187879] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:20:44 192.168.122.209 [40595.227869] [tempesta fw] Tempesta FW is ready Apr 26 03:20:45 192.168.122.209 [40595.376559] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrPsAuthorityV input=0x68('https://example.'), len=30, off=0 Apr 26 03:20:45 192.168.122.209 [40595.814024] [tdb] Close table 'client0.tdb' Apr 26 03:20:45 192.168.122.209 [40596.000995] [tdb] Close table 'sessions0.tdb' Apr 26 03:20:48 192.168.122.209 [40599.201550] [tdb] Close table 'cache0.tdb' Apr 26 03:20:49 192.168.122.209 [40599.435538] [tdb] Close table 'filter0.tdb' Apr 26 03:20:49 192.168.122.209 [40599.436362] [tempesta fw] modules are stopped Apr 26 03:20:49 192.168.122.209 [40599.697539] [tempesta fw] exiting... Apr 26 03:20:49 192.168.122.209 [40599.841406] [tdb] Shutdown Tempesta DB Apr 26 03:20:49 192.168.122.209 [40600.041333] End test: http2_general.test_h2_headers.TestPseudoHeaders.test_authority_with_scheme_and_path Apr 26 03:20:49 192.168.122.209 [40600.068009] Start test: http2_general.test_h2_headers.TestPseudoHeaders.test_duplicate_pseudo_header Apr 26 03:20:50 192.168.122.209 [40601.194154] [tdb] Start Tempesta DB Apr 26 03:20:51 192.168.122.209 [40601.342547] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:20:52 192.168.122.209 [40602.941826] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40602.941826] Maybe that's fine, but it's worth checking the [40602.941826] config - if there is no relations between the [40602.941826] names, then host name confusion attack is possible. Apr 26 03:20:52 192.168.122.209 [40603.116060] [tempesta fw] Configuration processing is completed. Apr 26 03:20:52 192.168.122.209 [40603.175410] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:20:53 192.168.122.209 [40603.632307] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:20:53 192.168.122.209 [40603.666558] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:20:53 192.168.122.209 [40603.691873] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:20:53 192.168.122.209 [40603.735965] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:20:53 192.168.122.209 [40603.791968] [tempesta fw] Tempesta FW is ready Apr 26 03:20:54 192.168.122.209 [40604.429532] [tdb] Close table 'client0.tdb' Apr 26 03:20:54 192.168.122.209 [40604.624393] [tdb] Close table 'sessions0.tdb' Apr 26 03:20:57 192.168.122.209 [40607.813584] [tdb] Close table 'cache0.tdb' Apr 26 03:20:57 192.168.122.209 [40608.050711] [tdb] Close table 'filter0.tdb' Apr 26 03:20:57 192.168.122.209 [40608.052006] [tempesta fw] modules are stopped Apr 26 03:20:57 192.168.122.209 [40608.274513] [tempesta fw] exiting... Apr 26 03:20:58 192.168.122.209 [40608.416833] [tdb] Shutdown Tempesta DB Apr 26 03:20:58 192.168.122.209 [40608.618011] End test: http2_general.test_h2_headers.TestPseudoHeaders.test_duplicate_pseudo_header Apr 26 03:20:58 192.168.122.209 [40608.640282] Start test: http2_general.test_h2_headers.TestPseudoHeaders.test_invalid_pseudo_header Apr 26 03:20:59 192.168.122.209 [40609.771309] [tdb] Start Tempesta DB Apr 26 03:20:59 192.168.122.209 [40609.922735] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:21:01 192.168.122.209 [40611.501628] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40611.501628] Maybe that's fine, but it's worth checking the [40611.501628] config - if there is no relations between the [40611.501628] names, then host name confusion attack is possible. Apr 26 03:21:01 192.168.122.209 [40611.660180] [tempesta fw] Configuration processing is completed. Apr 26 03:21:01 192.168.122.209 [40611.751381] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:21:01 192.168.122.209 [40612.171242] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:21:01 192.168.122.209 [40612.206430] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:21:01 192.168.122.209 [40612.233701] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:21:01 192.168.122.209 [40612.280142] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:21:02 192.168.122.209 [40612.324087] [tempesta fw] Tempesta FW is ready Apr 26 03:21:02 192.168.122.209 [40612.470658] [tempesta fw] Warning: HTTP/2 request dropped: state=RGen_HdrOtherN input=0x3a(':content-length'), len=15, off=0 Apr 26 03:21:02 192.168.122.209 [40612.906082] [tdb] Close table 'client0.tdb' Apr 26 03:21:02 192.168.122.209 [40613.083562] [tdb] Close table 'sessions0.tdb' Apr 26 03:21:05 192.168.122.209 [40616.254917] [tdb] Close table 'cache0.tdb' Apr 26 03:21:06 192.168.122.209 [40616.498524] [tdb] Close table 'filter0.tdb' Apr 26 03:21:06 192.168.122.209 [40616.498969] [tempesta fw] modules are stopped Apr 26 03:21:06 192.168.122.209 [40616.795556] [tempesta fw] exiting... Apr 26 03:21:06 192.168.122.209 [40616.953088] [tdb] Shutdown Tempesta DB Apr 26 03:21:06 192.168.122.209 [40617.175342] End test: http2_general.test_h2_headers.TestPseudoHeaders.test_invalid_pseudo_header Apr 26 03:21:06 192.168.122.209 [40617.191566] Start test: http2_general.test_h2_headers.TestPseudoHeaders.test_regular_header_before_pseudo_header Apr 26 03:21:08 192.168.122.209 [40618.324849] [tdb] Start Tempesta DB Apr 26 03:21:08 192.168.122.209 [40618.472236] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:21:09 192.168.122.209 [40620.073692] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40620.073692] Maybe that's fine, but it's worth checking the [40620.073692] config - if there is no relations between the [40620.073692] names, then host name confusion attack is possible. Apr 26 03:21:09 192.168.122.209 [40620.232247] [tempesta fw] Configuration processing is completed. Apr 26 03:21:09 192.168.122.209 [40620.282448] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:21:10 192.168.122.209 [40620.695224] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:21:10 192.168.122.209 [40620.721170] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:21:10 192.168.122.209 [40620.747390] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:21:10 192.168.122.209 [40620.796285] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:21:10 192.168.122.209 [40620.840189] [tempesta fw] Tempesta FW is ready Apr 26 03:21:10 192.168.122.209 [40620.982879] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrContent_LengthV input=0x30('0'), len=1, off=0 Apr 26 03:21:11 192.168.122.209 [40621.396767] [tdb] Close table 'client0.tdb' Apr 26 03:21:11 192.168.122.209 [40621.615244] [tdb] Close table 'sessions0.tdb' Apr 26 03:21:14 192.168.122.209 [40624.814110] [tdb] Close table 'cache0.tdb' Apr 26 03:21:14 192.168.122.209 [40625.062138] [tdb] Close table 'filter0.tdb' Apr 26 03:21:14 192.168.122.209 [40625.062592] [tempesta fw] modules are stopped Apr 26 03:21:14 192.168.122.209 [40625.257557] [tempesta fw] exiting... Apr 26 03:21:15 192.168.122.209 [40625.402171] [tdb] Shutdown Tempesta DB Apr 26 03:21:15 192.168.122.209 [40625.606081] End test: http2_general.test_h2_headers.TestPseudoHeaders.test_regular_header_before_pseudo_header Apr 26 03:21:15 192.168.122.209 [40625.633404] Start test: http2_general.test_h2_headers.TestPseudoHeaders.test_status_header_in_request Apr 26 03:21:16 192.168.122.209 [40626.741889] [tdb] Start Tempesta DB Apr 26 03:21:16 192.168.122.209 [40626.886781] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:21:18 192.168.122.209 [40628.489793] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40628.489793] Maybe that's fine, but it's worth checking the [40628.489793] config - if there is no relations between the [40628.489793] names, then host name confusion attack is possible. Apr 26 03:21:18 192.168.122.209 [40628.684369] [tempesta fw] Configuration processing is completed. Apr 26 03:21:18 192.168.122.209 [40628.734432] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:21:18 192.168.122.209 [40629.138000] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:21:18 192.168.122.209 [40629.163202] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:21:18 192.168.122.209 [40629.188924] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:21:18 192.168.122.209 [40629.244363] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:21:18 192.168.122.209 [40629.288318] [tempesta fw] Tempesta FW is ready Apr 26 03:21:19 192.168.122.209 [40629.916184] [tdb] Close table 'client0.tdb' Apr 26 03:21:19 192.168.122.209 [40630.120786] [tdb] Close table 'sessions0.tdb' Apr 26 03:21:22 192.168.122.209 [40633.281521] [tdb] Close table 'cache0.tdb' Apr 26 03:21:23 192.168.122.209 [40633.519385] [tdb] Close table 'filter0.tdb' Apr 26 03:21:23 192.168.122.209 [40633.519810] [tempesta fw] modules are stopped Apr 26 03:21:23 192.168.122.209 [40633.755935] [tempesta fw] exiting... Apr 26 03:21:23 192.168.122.209 [40633.914574] [tdb] Shutdown Tempesta DB Apr 26 03:21:23 192.168.122.209 [40634.131818] End test: http2_general.test_h2_headers.TestPseudoHeaders.test_status_header_in_request Apr 26 03:21:23 192.168.122.209 [40634.152666] Start test: http2_general.test_h2_headers.TestSplitCookies.test_split_cookies Apr 26 03:21:24 192.168.122.209 [40635.281172] [tdb] Start Tempesta DB Apr 26 03:21:25 192.168.122.209 [40635.418661] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:21:26 192.168.122.209 [40637.029556] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40637.029556] Maybe that's fine, but it's worth checking the [40637.029556] config - if there is no relations between the [40637.029556] names, then host name confusion attack is possible. Apr 26 03:21:26 192.168.122.209 [40637.172506] [tempesta fw] Configuration processing is completed. Apr 26 03:21:26 192.168.122.209 [40637.263049] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:21:27 192.168.122.209 [40637.687247] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:21:27 192.168.122.209 [40637.714093] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:21:27 192.168.122.209 [40637.740869] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:21:27 192.168.122.209 [40637.784424] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:21:27 192.168.122.209 [40637.824404] [tempesta fw] Tempesta FW is ready Apr 26 03:21:28 192.168.122.209 [40638.433314] [tdb] Close table 'client0.tdb' Apr 26 03:21:28 192.168.122.209 [40638.642550] [tdb] Close table 'sessions0.tdb' Apr 26 03:21:31 192.168.122.209 [40641.771247] [tdb] Close table 'cache0.tdb' Apr 26 03:21:31 192.168.122.209 [40642.019892] [tdb] Close table 'filter0.tdb' Apr 26 03:21:31 192.168.122.209 [40642.020344] [tempesta fw] modules are stopped Apr 26 03:21:31 192.168.122.209 [40642.309662] [tempesta fw] exiting... Apr 26 03:21:32 192.168.122.209 [40642.475644] [tdb] Shutdown Tempesta DB Apr 26 03:21:32 192.168.122.209 [40642.674927] End test: http2_general.test_h2_headers.TestSplitCookies.test_split_cookies Apr 26 03:21:32 192.168.122.209 [40642.686184] Start test: http2_general.test_h2_headers.TestTrailers.test_trailers_in_request_trailer Apr 26 03:21:33 192.168.122.209 [40643.908148] [tdb] Start Tempesta DB Apr 26 03:21:33 192.168.122.209 [40644.065318] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:21:35 192.168.122.209 [40645.666070] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40645.666070] Maybe that's fine, but it's worth checking the [40645.666070] config - if there is no relations between the [40645.666070] names, then host name confusion attack is possible. Apr 26 03:21:35 192.168.122.209 [40645.820587] [tempesta fw] Configuration processing is completed. Apr 26 03:21:35 192.168.122.209 [40645.870949] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:21:35 192.168.122.209 [40646.276605] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:21:35 192.168.122.209 [40646.302484] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:21:36 192.168.122.209 [40646.327759] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:21:36 192.168.122.209 [40646.392588] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:21:36 192.168.122.209 [40646.436520] [tempesta fw] Tempesta FW is ready Apr 26 03:21:36 192.168.122.209 [40647.045281] [tdb] Close table 'client0.tdb' Apr 26 03:21:36 192.168.122.209 [40647.245423] [tdb] Close table 'sessions0.tdb' Apr 26 03:21:40 192.168.122.209 [40650.367452] [tdb] Close table 'cache0.tdb' Apr 26 03:21:40 192.168.122.209 [40650.616520] [tdb] Close table 'filter0.tdb' Apr 26 03:21:40 192.168.122.209 [40650.616956] [tempesta fw] modules are stopped Apr 26 03:21:40 192.168.122.209 [40650.849214] [tempesta fw] exiting... Apr 26 03:21:40 192.168.122.209 [40650.998382] [tdb] Shutdown Tempesta DB Apr 26 03:21:40 192.168.122.209 [40651.210135] End test: http2_general.test_h2_headers.TestTrailers.test_trailers_in_request_trailer Apr 26 03:21:40 192.168.122.209 [40651.231238] Start test: http2_general.test_h2_headers.TestTrailers.test_trailers_in_request_trailer_mix_1 Apr 26 03:21:42 192.168.122.209 [40652.398640] [tdb] Start Tempesta DB Apr 26 03:21:42 192.168.122.209 [40652.552771] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:21:43 192.168.122.209 [40654.138120] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40654.138120] Maybe that's fine, but it's worth checking the [40654.138120] config - if there is no relations between the [40654.138120] names, then host name confusion attack is possible. Apr 26 03:21:43 192.168.122.209 [40654.284683] [tempesta fw] Configuration processing is completed. Apr 26 03:21:44 192.168.122.209 [40654.343830] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:21:44 192.168.122.209 [40654.750589] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:21:44 192.168.122.209 [40654.776056] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:21:44 192.168.122.209 [40654.803840] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:21:44 192.168.122.209 [40654.848627] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:21:44 192.168.122.209 [40654.888650] [tempesta fw] Tempesta FW is ready Apr 26 03:21:44 192.168.122.209 [40655.088961] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrConnection input=0x63('connection'), len=10, off=0 Apr 26 03:21:45 192.168.122.209 [40655.538641] [tdb] Close table 'client0.tdb' Apr 26 03:21:45 192.168.122.209 [40655.727889] [tdb] Close table 'sessions0.tdb' Apr 26 03:21:48 192.168.122.209 [40658.934961] [tdb] Close table 'cache0.tdb' Apr 26 03:21:48 192.168.122.209 [40659.153551] [tdb] Close table 'filter0.tdb' Apr 26 03:21:48 192.168.122.209 [40659.153984] [tempesta fw] modules are stopped Apr 26 03:21:49 192.168.122.209 [40659.367968] [tempesta fw] exiting... Apr 26 03:21:49 192.168.122.209 [40659.515242] [tdb] Shutdown Tempesta DB Apr 26 03:21:49 192.168.122.209 [40659.738501] End test: http2_general.test_h2_headers.TestTrailers.test_trailers_in_request_trailer_mix_1 Apr 26 03:21:49 192.168.122.209 [40659.766018] Start test: http2_general.test_h2_headers.TestTrailers.test_trailers_in_request_trailer_mix_2 Apr 26 03:21:50 192.168.122.209 [40660.853897] [tdb] Start Tempesta DB Apr 26 03:21:50 192.168.122.209 [40661.018432] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:21:52 192.168.122.209 [40662.590204] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40662.590204] Maybe that's fine, but it's worth checking the [40662.590204] config - if there is no relations between the [40662.590204] names, then host name confusion attack is possible. Apr 26 03:21:52 192.168.122.209 [40662.736806] [tempesta fw] Configuration processing is completed. Apr 26 03:21:52 192.168.122.209 [40662.821154] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:21:52 192.168.122.209 [40663.231245] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:21:52 192.168.122.209 [40663.257778] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:21:52 192.168.122.209 [40663.284970] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:21:53 192.168.122.209 [40663.328725] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:21:53 192.168.122.209 [40663.377196] [tempesta fw] Tempesta FW is ready Apr 26 03:21:53 192.168.122.209 [40663.527626] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrKeep_Alive input=0x6b('keep-alive'), len=10, off=0 Apr 26 03:21:53 192.168.122.209 [40663.943571] [tdb] Close table 'client0.tdb' Apr 26 03:21:53 192.168.122.209 [40664.157363] [tdb] Close table 'sessions0.tdb' Apr 26 03:21:57 192.168.122.209 [40667.338604] [tdb] Close table 'cache0.tdb' Apr 26 03:21:57 192.168.122.209 [40667.575208] [tdb] Close table 'filter0.tdb' Apr 26 03:21:57 192.168.122.209 [40667.575646] [tempesta fw] modules are stopped Apr 26 03:21:57 192.168.122.209 [40667.900416] [tempesta fw] exiting... Apr 26 03:21:57 192.168.122.209 [40668.064554] [tdb] Shutdown Tempesta DB Apr 26 03:21:57 192.168.122.209 [40668.284357] End test: http2_general.test_h2_headers.TestTrailers.test_trailers_in_request_trailer_mix_2 Apr 26 03:21:57 192.168.122.209 [40668.304527] Start test: http2_general.test_h2_headers.TestTrailers.test_trailers_in_request_trailer_mix_3 Apr 26 03:21:59 192.168.122.209 [40669.455865] [tdb] Start Tempesta DB Apr 26 03:21:59 192.168.122.209 [40669.602427] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:22:00 192.168.122.209 [40671.194328] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40671.194328] Maybe that's fine, but it's worth checking the [40671.194328] config - if there is no relations between the [40671.194328] names, then host name confusion attack is possible. Apr 26 03:22:01 192.168.122.209 [40671.376907] [tempesta fw] Configuration processing is completed. Apr 26 03:22:01 192.168.122.209 [40671.426933] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:22:01 192.168.122.209 [40671.829683] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:22:01 192.168.122.209 [40671.863808] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:22:01 192.168.122.209 [40671.888544] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:22:01 192.168.122.209 [40671.952891] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:22:01 192.168.122.209 [40671.992793] [tempesta fw] Tempesta FW is ready Apr 26 03:22:01 192.168.122.209 [40672.146396] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrUpgrade input=0x75('upgrade'), len=7, off=0 Apr 26 03:22:02 192.168.122.209 [40672.641375] [tdb] Close table 'client0.tdb' Apr 26 03:22:02 192.168.122.209 [40672.831931] [tdb] Close table 'sessions0.tdb' Apr 26 03:22:05 192.168.122.209 [40675.995174] [tdb] Close table 'cache0.tdb' Apr 26 03:22:05 192.168.122.209 [40676.224233] [tdb] Close table 'filter0.tdb' Apr 26 03:22:05 192.168.122.209 [40676.224661] [tempesta fw] modules are stopped Apr 26 03:22:06 192.168.122.209 [40676.447873] [tempesta fw] exiting... Apr 26 03:22:06 192.168.122.209 [40676.608434] [tdb] Shutdown Tempesta DB Apr 26 03:22:06 192.168.122.209 [40676.808116] End test: http2_general.test_h2_headers.TestTrailers.test_trailers_in_request_trailer_mix_3 Apr 26 03:22:06 192.168.122.209 [40676.822203] Start test: http2_general.test_h2_headers.TestTrailers.test_trailers_in_request_trailer_mix_4 Apr 26 03:22:07 192.168.122.209 [40678.032467] [tdb] Start Tempesta DB Apr 26 03:22:07 192.168.122.209 [40678.191376] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:22:09 192.168.122.209 [40679.762469] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40679.762469] Maybe that's fine, but it's worth checking the [40679.762469] config - if there is no relations between the [40679.762469] names, then host name confusion attack is possible. Apr 26 03:22:09 192.168.122.209 [40679.925013] [tempesta fw] Configuration processing is completed. Apr 26 03:22:09 192.168.122.209 [40679.975208] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:22:10 192.168.122.209 [40680.382785] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:22:10 192.168.122.209 [40680.408631] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:22:10 192.168.122.209 [40680.434131] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:22:10 192.168.122.209 [40680.480989] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:22:10 192.168.122.209 [40680.524951] [tempesta fw] Tempesta FW is ready Apr 26 03:22:10 192.168.122.209 [40680.667198] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrTeV input=0x63('chunked'), len=7, off=0 Apr 26 03:22:10 192.168.122.209 [40681.175710] [tdb] Close table 'client0.tdb' Apr 26 03:22:11 192.168.122.209 [40681.367586] [tdb] Close table 'sessions0.tdb' Apr 26 03:22:14 192.168.122.209 [40684.530196] [tdb] Close table 'cache0.tdb' Apr 26 03:22:14 192.168.122.209 [40684.760097] [tdb] Close table 'filter0.tdb' Apr 26 03:22:14 192.168.122.209 [40684.760520] [tempesta fw] modules are stopped Apr 26 03:22:14 192.168.122.209 [40684.988627] [tempesta fw] exiting... Apr 26 03:22:14 192.168.122.209 [40685.182891] [tdb] Shutdown Tempesta DB Apr 26 03:22:15 192.168.122.209 [40685.406934] End test: http2_general.test_h2_headers.TestTrailers.test_trailers_in_request_trailer_mix_4 Apr 26 03:22:15 192.168.122.209 [40685.420255] Start test: http2_general.test_h2_headers.TestTrailers.test_trailers_in_request_trailer_with_hbp Apr 26 03:22:16 192.168.122.209 [40686.635446] [tdb] Start Tempesta DB Apr 26 03:22:16 192.168.122.209 [40686.773672] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:22:17 192.168.122.209 [40688.214518] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40688.214518] Maybe that's fine, but it's worth checking the [40688.214518] config - if there is no relations between the [40688.214518] names, then host name confusion attack is possible. Apr 26 03:22:18 192.168.122.209 [40688.361119] [tempesta fw] Configuration processing is completed. Apr 26 03:22:18 192.168.122.209 [40688.449481] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:22:18 192.168.122.209 [40688.861402] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:22:18 192.168.122.209 [40688.888071] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:22:18 192.168.122.209 [40688.914779] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:22:18 192.168.122.209 [40688.957113] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:22:18 192.168.122.209 [40688.997056] [tempesta fw] Tempesta FW is ready Apr 26 03:22:18 192.168.122.209 [40689.162450] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrConnection input=0x63('connection'), len=10, off=0 Apr 26 03:22:19 192.168.122.209 [40689.603951] [tdb] Close table 'client0.tdb' Apr 26 03:22:19 192.168.122.209 [40689.801231] [tdb] Close table 'sessions0.tdb' Apr 26 03:22:22 192.168.122.209 [40692.960146] [tdb] Close table 'cache0.tdb' Apr 26 03:22:22 192.168.122.209 [40693.199679] [tdb] Close table 'filter0.tdb' Apr 26 03:22:22 192.168.122.209 [40693.200111] [tempesta fw] modules are stopped Apr 26 03:22:23 192.168.122.209 [40693.421348] [tempesta fw] exiting... Apr 26 03:22:23 192.168.122.209 [40693.575859] [tdb] Shutdown Tempesta DB Apr 26 03:22:23 192.168.122.209 [40693.772478] End test: http2_general.test_h2_headers.TestTrailers.test_trailers_in_request_trailer_with_hbp Apr 26 03:22:23 192.168.122.209 [40693.791618] Start test: http2_general.test_h2_headers.TestTrailers.test_trailers_in_response_empty_body Apr 26 03:22:24 192.168.122.209 [40695.017115] [tdb] Start Tempesta DB Apr 26 03:22:24 192.168.122.209 [40695.167806] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:22:26 192.168.122.209 [40696.774710] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40696.774710] Maybe that's fine, but it's worth checking the [40696.774710] config - if there is no relations between the [40696.774710] names, then host name confusion attack is possible. Apr 26 03:22:26 192.168.122.209 [40696.921263] [tempesta fw] Configuration processing is completed. Apr 26 03:22:26 192.168.122.209 [40696.971258] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:22:27 192.168.122.209 [40697.377266] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:22:27 192.168.122.209 [40697.402897] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:22:27 192.168.122.209 [40697.428059] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:22:27 192.168.122.209 [40697.501220] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:22:27 192.168.122.209 [40697.541167] [tempesta fw] Tempesta FW is ready Apr 26 03:22:27 192.168.122.209 [40698.126275] [tdb] Close table 'client0.tdb' Apr 26 03:22:28 192.168.122.209 [40698.326658] [tdb] Close table 'sessions0.tdb' Apr 26 03:22:31 192.168.122.209 [40701.525419] [tdb] Close table 'cache0.tdb' Apr 26 03:22:31 192.168.122.209 [40701.774473] [tdb] Close table 'filter0.tdb' Apr 26 03:22:31 192.168.122.209 [40701.774909] [tempesta fw] modules are stopped Apr 26 03:22:31 192.168.122.209 [40701.968978] [tempesta fw] exiting... Apr 26 03:22:31 192.168.122.209 [40702.130025] [tdb] Shutdown Tempesta DB Apr 26 03:22:32 192.168.122.209 [40702.335547] End test: http2_general.test_h2_headers.TestTrailers.test_trailers_in_response_empty_body Apr 26 03:22:32 192.168.122.209 [40702.348003] Start test: http2_general.test_h2_headers.TestTrailers.test_trailers_in_response_not_empty_body Apr 26 03:22:33 192.168.122.209 [40703.546778] [tdb] Start Tempesta DB Apr 26 03:22:33 192.168.122.209 [40703.690081] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:22:35 192.168.122.209 [40705.326799] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40705.326799] Maybe that's fine, but it's worth checking the [40705.326799] config - if there is no relations between the [40705.326799] names, then host name confusion attack is possible. Apr 26 03:22:35 192.168.122.209 [40705.489382] [tempesta fw] Configuration processing is completed. Apr 26 03:22:35 192.168.122.209 [40705.539795] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:22:35 192.168.122.209 [40705.952720] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:22:35 192.168.122.209 [40705.978438] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:22:35 192.168.122.209 [40706.003750] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:22:35 192.168.122.209 [40706.065364] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:22:35 192.168.122.209 [40706.105305] [tempesta fw] Tempesta FW is ready Apr 26 03:22:36 192.168.122.209 [40706.760631] [tdb] Close table 'client0.tdb' Apr 26 03:22:36 192.168.122.209 [40706.953763] [tdb] Close table 'sessions0.tdb' Apr 26 03:22:39 192.168.122.209 [40710.104324] [tdb] Close table 'cache0.tdb' Apr 26 03:22:40 192.168.122.209 [40710.340739] [tdb] Close table 'filter0.tdb' Apr 26 03:22:40 192.168.122.209 [40710.341197] [tempesta fw] modules are stopped Apr 26 03:22:40 192.168.122.209 [40710.532504] [tempesta fw] exiting... Apr 26 03:22:40 192.168.122.209 [40710.697102] [tdb] Shutdown Tempesta DB Apr 26 03:22:40 192.168.122.209 [40710.876610] End test: http2_general.test_h2_headers.TestTrailers.test_trailers_in_response_not_empty_body Apr 26 03:22:40 192.168.122.209 [40710.899226] Start test: http2_general.test_h2_headers.TestTrailers.test_trailers_invalid_header_in_request Apr 26 03:22:41 192.168.122.209 [40712.034250] [tdb] Start Tempesta DB Apr 26 03:22:41 192.168.122.209 [40712.167283] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:22:43 192.168.122.209 [40713.810283] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40713.810283] Maybe that's fine, but it's worth checking the [40713.810283] config - if there is no relations between the [40713.810283] names, then host name confusion attack is possible. Apr 26 03:22:43 192.168.122.209 [40713.961474] [tempesta fw] Configuration processing is completed. Apr 26 03:22:43 192.168.122.209 [40714.046582] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:22:44 192.168.122.209 [40714.466130] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:22:44 192.168.122.209 [40714.493338] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:22:44 192.168.122.209 [40714.520891] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:22:44 192.168.122.209 [40714.561477] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:22:44 192.168.122.209 [40714.609403] [tempesta fw] Tempesta FW is ready Apr 26 03:22:45 192.168.122.209 [40715.457127] [tdb] Close table 'client0.tdb' Apr 26 03:22:45 192.168.122.209 [40715.669351] [tdb] Close table 'sessions0.tdb' Apr 26 03:22:48 192.168.122.209 [40718.815428] [tdb] Close table 'cache0.tdb' Apr 26 03:22:48 192.168.122.209 [40719.036999] [tdb] Close table 'filter0.tdb' Apr 26 03:22:48 192.168.122.209 [40719.037450] [tempesta fw] modules are stopped Apr 26 03:22:48 192.168.122.209 [40719.292053] [tempesta fw] exiting... Apr 26 03:22:49 192.168.122.209 [40719.431771] [tdb] Shutdown Tempesta DB Apr 26 03:22:49 192.168.122.209 [40719.653759] End test: http2_general.test_h2_headers.TestTrailers.test_trailers_invalid_header_in_request Apr 26 03:22:49 192.168.122.209 [40719.667668] Start test: http2_general.test_h2_headers.TestTrailers.test_trailers_with_continuation_frame_in_request Apr 26 03:22:50 192.168.122.209 [40720.848289] [tdb] Start Tempesta DB Apr 26 03:22:50 192.168.122.209 [40720.998662] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:22:52 192.168.122.209 [40722.594365] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40722.594365] Maybe that's fine, but it's worth checking the [40722.594365] config - if there is no relations between the [40722.594365] names, then host name confusion attack is possible. Apr 26 03:22:52 192.168.122.209 [40722.733648] [tempesta fw] Configuration processing is completed. Apr 26 03:22:52 192.168.122.209 [40722.786045] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:22:52 192.168.122.209 [40723.231656] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:22:52 192.168.122.209 [40723.257152] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:22:52 192.168.122.209 [40723.282525] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:22:53 192.168.122.209 [40723.325551] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:22:53 192.168.122.209 [40723.365527] [tempesta fw] Tempesta FW is ready Apr 26 03:22:53 192.168.122.209 [40723.995240] [tdb] Close table 'client0.tdb' Apr 26 03:22:53 192.168.122.209 [40724.170958] [tdb] Close table 'sessions0.tdb' Apr 26 03:22:57 192.168.122.209 [40727.349265] [tdb] Close table 'cache0.tdb' Apr 26 03:22:57 192.168.122.209 [40727.583892] [tdb] Close table 'filter0.tdb' Apr 26 03:22:57 192.168.122.209 [40727.584339] [tempesta fw] modules are stopped Apr 26 03:22:57 192.168.122.209 [40727.808558] [tempesta fw] exiting... Apr 26 03:22:57 192.168.122.209 [40727.948184] [tdb] Shutdown Tempesta DB Apr 26 03:22:57 192.168.122.209 [40728.148851] End test: http2_general.test_h2_headers.TestTrailers.test_trailers_with_continuation_frame_in_request Apr 26 03:22:57 192.168.122.209 [40728.161774] Start test: http2_general.test_h2_headers.TestTrailers.test_trailers_with_empty_continuation_frame_in_request_end_headers Apr 26 03:22:58 192.168.122.209 [40729.294376] [tdb] Start Tempesta DB Apr 26 03:22:59 192.168.122.209 [40729.447492] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:23:00 192.168.122.209 [40731.047218] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40731.047218] Maybe that's fine, but it's worth checking the [40731.047218] config - if there is no relations between the [40731.047218] names, then host name confusion attack is possible. Apr 26 03:23:00 192.168.122.209 [40731.193666] [tempesta fw] Configuration processing is completed. Apr 26 03:23:00 192.168.122.209 [40731.243841] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:23:01 192.168.122.209 [40731.650404] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:23:01 192.168.122.209 [40731.686594] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:23:01 192.168.122.209 [40731.712160] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:23:01 192.168.122.209 [40731.769661] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:23:01 192.168.122.209 [40731.821623] [tempesta fw] Tempesta FW is ready Apr 26 03:23:02 192.168.122.209 [40732.443095] [tdb] Close table 'client0.tdb' Apr 26 03:23:02 192.168.122.209 [40732.644398] [tdb] Close table 'sessions0.tdb' Apr 26 03:23:05 192.168.122.209 [40735.816240] [tdb] Close table 'cache0.tdb' Apr 26 03:23:05 192.168.122.209 [40736.068746] [tdb] Close table 'filter0.tdb' Apr 26 03:23:05 192.168.122.209 [40736.069154] [tempesta fw] modules are stopped Apr 26 03:23:05 192.168.122.209 [40736.273928] [tempesta fw] exiting... Apr 26 03:23:06 192.168.122.209 [40736.423804] [tdb] Shutdown Tempesta DB Apr 26 03:23:06 192.168.122.209 [40736.661262] End test: http2_general.test_h2_headers.TestTrailers.test_trailers_with_empty_continuation_frame_in_request_end_headers Apr 26 03:23:06 192.168.122.209 [40736.676620] Start test: http2_general.test_h2_headers.TestTrailers.test_trailers_with_empty_continuation_frame_in_request_no_end_headers Apr 26 03:23:07 192.168.122.209 [40737.868415] [tdb] Start Tempesta DB Apr 26 03:23:07 192.168.122.209 [40738.034338] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:23:10 192.168.122.209 [40740.331358] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40740.331358] Maybe that's fine, but it's worth checking the [40740.331358] config - if there is no relations between the [40740.331358] names, then host name confusion attack is possible. Apr 26 03:23:10 192.168.122.209 [40741.257869] [tempesta fw] Configuration processing is completed. Apr 26 03:23:11 192.168.122.209 [40741.409374] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:23:11 192.168.122.209 [40741.860238] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:23:11 192.168.122.209 [40741.886731] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:23:11 192.168.122.209 [40741.912680] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:23:12 192.168.122.209 [40742.605938] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:23:12 192.168.122.209 [40743.117876] [tempesta fw] Tempesta FW is ready Apr 26 03:23:14 192.168.122.209 [40743.313413] [tempesta fw] Empty CONTINUATION frame without END_HEADERS Apr 26 03:23:14 192.168.122.209 [40744.656484] [tdb] Close table 'client0.tdb' Apr 26 03:23:14 192.168.122.209 [40744.854652] [tdb] Close table 'sessions0.tdb' Apr 26 03:23:17 192.168.122.209 [40748.073049] [tdb] Close table 'cache0.tdb' Apr 26 03:23:18 192.168.122.209 [40748.324641] [tdb] Close table 'filter0.tdb' Apr 26 03:23:18 192.168.122.209 [40748.325083] [tempesta fw] modules are stopped Apr 26 03:23:18 192.168.122.209 [40748.559271] [tempesta fw] exiting... Apr 26 03:23:18 192.168.122.209 [40748.723306] [tdb] Shutdown Tempesta DB Apr 26 03:23:18 192.168.122.209 [40748.955007] End test: http2_general.test_h2_headers.TestTrailers.test_trailers_with_empty_continuation_frame_in_request_no_end_headers Apr 26 03:23:18 192.168.122.209 [40748.970346] Start test: http2_general.test_h2_headers.TestTrailers.test_trailers_with_pseudo_headers_in_request Apr 26 03:23:19 192.168.122.209 [40750.167339] [tdb] Start Tempesta DB Apr 26 03:23:19 192.168.122.209 [40750.312164] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:23:21 192.168.122.209 [40751.911404] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40751.911404] Maybe that's fine, but it's worth checking the [40751.911404] config - if there is no relations between the [40751.911404] names, then host name confusion attack is possible. Apr 26 03:23:21 192.168.122.209 [40752.054361] [tempesta fw] Configuration processing is completed. Apr 26 03:23:21 192.168.122.209 [40752.104357] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:23:22 192.168.122.209 [40752.508059] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:23:22 192.168.122.209 [40752.533656] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:23:22 192.168.122.209 [40752.559106] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:23:22 192.168.122.209 [40752.605967] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:23:22 192.168.122.209 [40752.645875] [tempesta fw] Tempesta FW is ready Apr 26 03:23:22 192.168.122.209 [40753.212212] [tdb] Close table 'client0.tdb' Apr 26 03:23:23 192.168.122.209 [40753.445480] [tdb] Close table 'sessions0.tdb' Apr 26 03:23:26 192.168.122.209 [40756.585723] [tdb] Close table 'cache0.tdb' Apr 26 03:23:26 192.168.122.209 [40756.821262] [tdb] Close table 'filter0.tdb' Apr 26 03:23:26 192.168.122.209 [40756.821702] [tempesta fw] modules are stopped Apr 26 03:23:26 192.168.122.209 [40757.061797] [tempesta fw] exiting... Apr 26 03:23:26 192.168.122.209 [40757.206402] [tdb] Shutdown Tempesta DB Apr 26 03:23:27 192.168.122.209 [40757.418870] End test: http2_general.test_h2_headers.TestTrailers.test_trailers_with_pseudo_headers_in_request Apr 26 03:23:27 192.168.122.209 [40757.438975] Start test: http2_general.test_h2_headers.TestTrailers.test_trailers_without_end_stream_in_request Apr 26 03:23:28 192.168.122.209 [40758.772177] [tdb] Start Tempesta DB Apr 26 03:23:28 192.168.122.209 [40758.936427] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:23:30 192.168.122.209 [40760.551517] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40760.551517] Maybe that's fine, but it's worth checking the [40760.551517] config - if there is no relations between the [40760.551517] names, then host name confusion attack is possible. Apr 26 03:23:30 192.168.122.209 [40760.734101] [tempesta fw] Configuration processing is completed. Apr 26 03:23:30 192.168.122.209 [40760.784442] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:23:30 192.168.122.209 [40761.189472] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:23:30 192.168.122.209 [40761.215371] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:23:30 192.168.122.209 [40761.241310] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:23:30 192.168.122.209 [40761.290044] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:23:31 192.168.122.209 [40761.329946] [tempesta fw] Tempesta FW is ready Apr 26 03:23:31 192.168.122.209 [40761.949155] [tdb] Close table 'client0.tdb' Apr 26 03:23:31 192.168.122.209 [40762.153910] [tdb] Close table 'sessions0.tdb' Apr 26 03:23:34 192.168.122.209 [40765.282210] [tdb] Close table 'cache0.tdb' Apr 26 03:23:35 192.168.122.209 [40765.518157] [tdb] Close table 'filter0.tdb' Apr 26 03:23:35 192.168.122.209 [40765.518596] [tempesta fw] modules are stopped Apr 26 03:23:35 192.168.122.209 [40765.790324] [tempesta fw] exiting... Apr 26 03:23:35 192.168.122.209 [40765.939985] [tdb] Shutdown Tempesta DB Apr 26 03:23:35 192.168.122.209 [40766.133698] End test: http2_general.test_h2_headers.TestTrailers.test_trailers_without_end_stream_in_request Apr 26 03:23:35 192.168.122.209 [40766.143609] Start test: http2_general.test_h2_hpack.TestFramePayloadLength.test_invalid_data Apr 26 03:23:36 192.168.122.209 [40767.308939] [tdb] Start Tempesta DB Apr 26 03:23:37 192.168.122.209 [40767.450539] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:23:38 192.168.122.209 [40769.027609] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40769.027609] Maybe that's fine, but it's worth checking the [40769.027609] config - if there is no relations between the [40769.027609] names, then host name confusion attack is possible. Apr 26 03:23:38 192.168.122.209 [40769.194214] [tempesta fw] Configuration processing is completed. Apr 26 03:23:38 192.168.122.209 [40769.275258] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:23:39 192.168.122.209 [40769.695924] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:23:39 192.168.122.209 [40769.722673] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:23:39 192.168.122.209 [40769.749606] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:23:39 192.168.122.209 [40769.794209] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:23:39 192.168.122.209 [40769.842102] [tempesta fw] Tempesta FW is ready Apr 26 03:23:40 192.168.122.209 [40770.435962] [tdb] Close table 'client0.tdb' Apr 26 03:23:40 192.168.122.209 [40770.643366] [tdb] Close table 'sessions0.tdb' Apr 26 03:23:43 192.168.122.209 [40773.800956] [tdb] Close table 'cache0.tdb' Apr 26 03:23:43 192.168.122.209 [40774.064149] [tdb] Close table 'filter0.tdb' Apr 26 03:23:43 192.168.122.209 [40774.064622] [tempesta fw] modules are stopped Apr 26 03:23:44 192.168.122.209 [40774.320423] [tempesta fw] exiting... Apr 26 03:23:44 192.168.122.209 [40774.458440] [tdb] Shutdown Tempesta DB Apr 26 03:23:44 192.168.122.209 [40774.653245] End test: http2_general.test_h2_hpack.TestFramePayloadLength.test_invalid_data Apr 26 03:23:44 192.168.122.209 [40774.664356] Start test: http2_general.test_h2_hpack.TestFramePayloadLength.test_large_frame_payload_length Apr 26 03:23:45 192.168.122.209 [40775.773420] [tdb] Start Tempesta DB Apr 26 03:23:45 192.168.122.209 [40775.916268] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:23:47 192.168.122.209 [40777.548747] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40777.548747] Maybe that's fine, but it's worth checking the [40777.548747] config - if there is no relations between the [40777.548747] names, then host name confusion attack is possible. Apr 26 03:23:47 192.168.122.209 [40777.710424] [tempesta fw] Configuration processing is completed. Apr 26 03:23:47 192.168.122.209 [40777.779173] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:23:47 192.168.122.209 [40778.190241] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:23:47 192.168.122.209 [40778.216608] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:23:47 192.168.122.209 [40778.241867] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:23:48 192.168.122.209 [40778.318260] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:23:48 192.168.122.209 [40778.366226] [tempesta fw] Tempesta FW is ready Apr 26 03:23:48 192.168.122.209 [40778.931935] [tdb] Close table 'client0.tdb' Apr 26 03:23:48 192.168.122.209 [40779.129616] [tdb] Close table 'sessions0.tdb' Apr 26 03:23:51 192.168.122.209 [40782.266150] [tdb] Close table 'cache0.tdb' Apr 26 03:23:52 192.168.122.209 [40782.497246] [tdb] Close table 'filter0.tdb' Apr 26 03:23:52 192.168.122.209 [40782.497691] [tempesta fw] modules are stopped Apr 26 03:23:52 192.168.122.209 [40782.762658] [tempesta fw] exiting... Apr 26 03:23:52 192.168.122.209 [40782.907442] [tdb] Shutdown Tempesta DB Apr 26 03:23:52 192.168.122.209 [40783.142122] End test: http2_general.test_h2_hpack.TestFramePayloadLength.test_large_frame_payload_length Apr 26 03:23:52 192.168.122.209 [40783.153629] Start test: http2_general.test_h2_hpack.TestFramePayloadLength.test_small_frame_payload_length Apr 26 03:23:54 192.168.122.209 [40784.353251] [tdb] Start Tempesta DB Apr 26 03:23:54 192.168.122.209 [40784.490911] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:23:55 192.168.122.209 [40786.075804] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40786.075804] Maybe that's fine, but it's worth checking the [40786.075804] config - if there is no relations between the [40786.075804] names, then host name confusion attack is possible. Apr 26 03:23:55 192.168.122.209 [40786.222382] [tempesta fw] Configuration processing is completed. Apr 26 03:23:55 192.168.122.209 [40786.276387] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:23:56 192.168.122.209 [40786.684599] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:23:56 192.168.122.209 [40786.710289] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:23:56 192.168.122.209 [40786.735687] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:23:56 192.168.122.209 [40786.778314] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:23:56 192.168.122.209 [40786.822369] [tempesta fw] Tempesta FW is ready Apr 26 03:23:57 192.168.122.209 [40787.441606] [tdb] Close table 'client0.tdb' Apr 26 03:23:57 192.168.122.209 [40787.638306] [tdb] Close table 'sessions0.tdb' Apr 26 03:24:00 192.168.122.209 [40790.752948] [tdb] Close table 'cache0.tdb' Apr 26 03:24:00 192.168.122.209 [40790.985796] [tdb] Close table 'filter0.tdb' Apr 26 03:24:00 192.168.122.209 [40790.986261] [tempesta fw] modules are stopped Apr 26 03:24:00 192.168.122.209 [40791.219256] [tempesta fw] exiting... Apr 26 03:24:01 192.168.122.209 [40791.391841] [tdb] Shutdown Tempesta DB Apr 26 03:24:01 192.168.122.209 [40791.622844] End test: http2_general.test_h2_hpack.TestFramePayloadLength.test_small_frame_payload_length Apr 26 03:24:01 192.168.122.209 [40791.634794] Start test: http2_general.test_h2_hpack.TestHpack.test_big_header_after_setting_header_table_size Apr 26 03:24:02 192.168.122.209 [40792.828388] [tdb] Start Tempesta DB Apr 26 03:24:02 192.168.122.209 [40792.978094] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:24:04 192.168.122.209 [40794.515517] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40794.515517] Maybe that's fine, but it's worth checking the [40794.515517] config - if there is no relations between the [40794.515517] names, then host name confusion attack is possible. Apr 26 03:24:04 192.168.122.209 [40794.662429] [tempesta fw] Configuration processing is completed. Apr 26 03:24:04 192.168.122.209 [40794.759003] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:24:04 192.168.122.209 [40795.172962] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:24:04 192.168.122.209 [40795.199518] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:24:04 192.168.122.209 [40795.226502] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:24:04 192.168.122.209 [40795.274378] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:24:05 192.168.122.209 [40795.326427] [tempesta fw] Tempesta FW is ready Apr 26 03:24:05 192.168.122.209 [40795.908834] [tdb] Close table 'client0.tdb' Apr 26 03:24:05 192.168.122.209 [40796.087575] [tdb] Close table 'sessions0.tdb' Apr 26 03:24:08 192.168.122.209 [40799.281570] [tdb] Close table 'cache0.tdb' Apr 26 03:24:09 192.168.122.209 [40799.515998] [tdb] Close table 'filter0.tdb' Apr 26 03:24:09 192.168.122.209 [40799.516434] [tempesta fw] modules are stopped Apr 26 03:24:09 192.168.122.209 [40799.770032] [tempesta fw] exiting... Apr 26 03:24:09 192.168.122.209 [40799.941616] [tdb] Shutdown Tempesta DB Apr 26 03:24:09 192.168.122.209 [40800.148065] End test: http2_general.test_h2_hpack.TestHpack.test_big_header_after_setting_header_table_size Apr 26 03:24:09 192.168.122.209 [40800.163843] Start test: http2_general.test_h2_hpack.TestHpack.test_big_header_and_body_in_response Apr 26 03:24:11 192.168.122.209 [40801.363244] [tdb] Start Tempesta DB Apr 26 03:24:11 192.168.122.209 [40801.505870] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:24:12 192.168.122.209 [40803.155998] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40803.155998] Maybe that's fine, but it's worth checking the [40803.155998] config - if there is no relations between the [40803.155998] names, then host name confusion attack is possible. Apr 26 03:24:12 192.168.122.209 [40803.314620] [tempesta fw] Configuration processing is completed. Apr 26 03:24:13 192.168.122.209 [40803.365141] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:24:13 192.168.122.209 [40803.777895] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:24:13 192.168.122.209 [40803.803916] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:24:13 192.168.122.209 [40803.829200] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:24:13 192.168.122.209 [40803.870606] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:24:13 192.168.122.209 [40803.914534] [tempesta fw] Tempesta FW is ready Apr 26 03:24:14 192.168.122.209 [40804.579946] [tdb] Close table 'client0.tdb' Apr 26 03:24:14 192.168.122.209 [40804.774058] [tdb] Close table 'sessions0.tdb' Apr 26 03:24:17 192.168.122.209 [40807.942113] [tdb] Close table 'cache0.tdb' Apr 26 03:24:17 192.168.122.209 [40808.171692] [tdb] Close table 'filter0.tdb' Apr 26 03:24:17 192.168.122.209 [40808.172135] [tempesta fw] modules are stopped Apr 26 03:24:18 192.168.122.209 [40808.379022] [tempesta fw] exiting... Apr 26 03:24:18 192.168.122.209 [40808.508574] [tdb] Shutdown Tempesta DB Apr 26 03:24:18 192.168.122.209 [40808.703750] End test: http2_general.test_h2_hpack.TestHpack.test_big_header_and_body_in_response Apr 26 03:24:18 192.168.122.209 [40808.713014] Start test: http2_general.test_h2_hpack.TestHpack.test_big_header_in_response Apr 26 03:24:19 192.168.122.209 [40809.890975] [tdb] Start Tempesta DB Apr 26 03:24:19 192.168.122.209 [40810.030027] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:24:21 192.168.122.209 [40811.564047] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40811.564047] Maybe that's fine, but it's worth checking the [40811.564047] config - if there is no relations between the [40811.564047] names, then host name confusion attack is possible. Apr 26 03:24:21 192.168.122.209 [40811.710724] [tempesta fw] Configuration processing is completed. Apr 26 03:24:21 192.168.122.209 [40811.761649] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:24:21 192.168.122.209 [40812.165880] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:24:21 192.168.122.209 [40812.191171] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:24:21 192.168.122.209 [40812.218242] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:24:21 192.168.122.209 [40812.258631] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:24:21 192.168.122.209 [40812.302639] [tempesta fw] Tempesta FW is ready Apr 26 03:24:22 192.168.122.209 [40812.923978] [tdb] Close table 'client0.tdb' Apr 26 03:24:22 192.168.122.209 [40813.111779] [tdb] Close table 'sessions0.tdb' Apr 26 03:24:25 192.168.122.209 [40816.251256] [tdb] Close table 'cache0.tdb' Apr 26 03:24:26 192.168.122.209 [40816.493861] [tdb] Close table 'filter0.tdb' Apr 26 03:24:26 192.168.122.209 [40816.494286] [tempesta fw] modules are stopped Apr 26 03:24:26 192.168.122.209 [40816.755091] [tempesta fw] exiting... Apr 26 03:24:26 192.168.122.209 [40816.938035] [tdb] Shutdown Tempesta DB Apr 26 03:24:26 192.168.122.209 [40817.200586] End test: http2_general.test_h2_hpack.TestHpack.test_big_header_in_response Apr 26 03:24:26 192.168.122.209 [40817.212391] Start test: http2_general.test_h2_hpack.TestHpack.test_bytes_of_table_size_in_header_frame_1 Apr 26 03:24:28 192.168.122.209 [40818.322784] [tdb] Start Tempesta DB Apr 26 03:24:28 192.168.122.209 [40818.477717] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:24:29 192.168.122.209 [40820.160327] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40820.160327] Maybe that's fine, but it's worth checking the [40820.160327] config - if there is no relations between the [40820.160327] names, then host name confusion attack is possible. Apr 26 03:24:30 192.168.122.209 [40820.326772] [tempesta fw] Configuration processing is completed. Apr 26 03:24:30 192.168.122.209 [40820.405719] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:24:30 192.168.122.209 [40820.829830] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:24:30 192.168.122.209 [40820.856902] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:24:30 192.168.122.209 [40820.884290] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:24:30 192.168.122.209 [40820.950823] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:24:30 192.168.122.209 [40820.994755] [tempesta fw] Tempesta FW is ready Apr 26 03:24:31 192.168.122.209 [40821.610349] [tdb] Close table 'client0.tdb' Apr 26 03:24:31 192.168.122.209 [40821.805558] [tdb] Close table 'sessions0.tdb' Apr 26 03:24:34 192.168.122.209 [40824.980613] [tdb] Close table 'cache0.tdb' Apr 26 03:24:34 192.168.122.209 [40825.245125] [tdb] Close table 'filter0.tdb' Apr 26 03:24:34 192.168.122.209 [40825.245850] [tempesta fw] modules are stopped Apr 26 03:24:35 192.168.122.209 [40825.448209] [tempesta fw] exiting... Apr 26 03:24:35 192.168.122.209 [40825.606698] [tdb] Shutdown Tempesta DB Apr 26 03:24:35 192.168.122.209 [40825.779397] End test: http2_general.test_h2_hpack.TestHpack.test_bytes_of_table_size_in_header_frame_1 Apr 26 03:24:35 192.168.122.209 [40825.801587] Start test: http2_general.test_h2_hpack.TestHpack.test_bytes_of_table_size_in_header_frame_2 Apr 26 03:24:36 192.168.122.209 [40826.961341] [tdb] Start Tempesta DB Apr 26 03:24:36 192.168.122.209 [40827.112218] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:24:38 192.168.122.209 [40828.716341] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40828.716341] Maybe that's fine, but it's worth checking the [40828.716341] config - if there is no relations between the [40828.716341] names, then host name confusion attack is possible. Apr 26 03:24:38 192.168.122.209 [40828.862948] [tempesta fw] Configuration processing is completed. Apr 26 03:24:38 192.168.122.209 [40828.912979] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:24:39 192.168.122.209 [40829.323505] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:24:39 192.168.122.209 [40829.349304] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:24:39 192.168.122.209 [40829.374362] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:24:39 192.168.122.209 [40829.446944] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:24:39 192.168.122.209 [40829.486874] [tempesta fw] Tempesta FW is ready Apr 26 03:24:39 192.168.122.209 [40830.079527] [tdb] Close table 'client0.tdb' Apr 26 03:24:39 192.168.122.209 [40830.259573] [tdb] Close table 'sessions0.tdb' Apr 26 03:24:43 192.168.122.209 [40833.416699] [tdb] Close table 'cache0.tdb' Apr 26 03:24:43 192.168.122.209 [40833.676020] [tdb] Close table 'filter0.tdb' Apr 26 03:24:43 192.168.122.209 [40833.676454] [tempesta fw] modules are stopped Apr 26 03:24:43 192.168.122.209 [40833.904582] [tempesta fw] exiting... Apr 26 03:24:43 192.168.122.209 [40834.071194] [tdb] Shutdown Tempesta DB Apr 26 03:24:43 192.168.122.209 [40834.301524] End test: http2_general.test_h2_hpack.TestHpack.test_bytes_of_table_size_in_header_frame_2 Apr 26 03:24:43 192.168.122.209 [40834.309253] Start test: http2_general.test_h2_hpack.TestHpack.test_clearing_dynamic_table Apr 26 03:24:45 192.168.122.209 [40835.474017] [tdb] Start Tempesta DB Apr 26 03:24:45 192.168.122.209 [40835.629709] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:24:46 192.168.122.209 [40837.284463] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40837.284463] Maybe that's fine, but it's worth checking the [40837.284463] config - if there is no relations between the [40837.284463] names, then host name confusion attack is possible. Apr 26 03:24:47 192.168.122.209 [40837.447779] [tempesta fw] Configuration processing is completed. Apr 26 03:24:47 192.168.122.209 [40837.496759] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:24:47 192.168.122.209 [40837.912875] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:24:47 192.168.122.209 [40837.938694] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:24:47 192.168.122.209 [40837.964285] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:24:47 192.168.122.209 [40838.026953] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:24:47 192.168.122.209 [40838.071004] [tempesta fw] Tempesta FW is ready Apr 26 03:24:48 192.168.122.209 [40838.694673] [tdb] Close table 'client0.tdb' Apr 26 03:24:48 192.168.122.209 [40838.898584] [tdb] Close table 'sessions0.tdb' Apr 26 03:24:51 192.168.122.209 [40842.079587] [tdb] Close table 'cache0.tdb' Apr 26 03:24:52 192.168.122.209 [40842.340791] [tdb] Close table 'filter0.tdb' Apr 26 03:24:52 192.168.122.209 [40842.341221] [tempesta fw] modules are stopped Apr 26 03:24:52 192.168.122.209 [40842.539796] [tempesta fw] exiting... Apr 26 03:24:52 192.168.122.209 [40842.694448] [tdb] Shutdown Tempesta DB Apr 26 03:24:52 192.168.122.209 [40842.919739] End test: http2_general.test_h2_hpack.TestHpack.test_clearing_dynamic_table Apr 26 03:24:52 192.168.122.209 [40842.931404] Start test: http2_general.test_h2_hpack.TestHpack.test_clearing_dynamic_table_with_settings_frame Apr 26 03:24:53 192.168.122.209 [40844.137441] [tdb] Start Tempesta DB Apr 26 03:24:53 192.168.122.209 [40844.264529] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:24:55 192.168.122.209 [40845.828543] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40845.828543] Maybe that's fine, but it's worth checking the [40845.828543] config - if there is no relations between the [40845.828543] names, then host name confusion attack is possible. Apr 26 03:24:55 192.168.122.209 [40845.991133] [tempesta fw] Configuration processing is completed. Apr 26 03:24:55 192.168.122.209 [40846.085663] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:24:56 192.168.122.209 [40846.503662] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:24:56 192.168.122.209 [40846.530176] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:24:56 192.168.122.209 [40846.557658] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:24:56 192.168.122.209 [40846.611160] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:24:56 192.168.122.209 [40846.679121] [tempesta fw] Tempesta FW is ready Apr 26 03:24:57 192.168.122.209 [40847.341063] [tdb] Close table 'client0.tdb' Apr 26 03:24:57 192.168.122.209 [40847.555747] [tdb] Close table 'sessions0.tdb' Apr 26 03:25:00 192.168.122.209 [40850.769508] [tdb] Close table 'cache0.tdb' Apr 26 03:25:00 192.168.122.209 [40851.011954] [tdb] Close table 'filter0.tdb' Apr 26 03:25:00 192.168.122.209 [40851.012405] [tempesta fw] modules are stopped Apr 26 03:25:00 192.168.122.209 [40851.276288] [tempesta fw] exiting... Apr 26 03:25:01 192.168.122.209 [40851.413620] [tdb] Shutdown Tempesta DB Apr 26 03:25:01 192.168.122.209 [40851.650433] End test: http2_general.test_h2_hpack.TestHpack.test_clearing_dynamic_table_with_settings_frame Apr 26 03:25:01 192.168.122.209 [40851.661810] Start test: http2_general.test_h2_hpack.TestHpack.test_disable_huffman Apr 26 03:25:02 192.168.122.209 [40852.869749] [tdb] Start Tempesta DB Apr 26 03:25:02 192.168.122.209 [40853.026259] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:25:04 192.168.122.209 [40854.592726] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40854.592726] Maybe that's fine, but it's worth checking the [40854.592726] config - if there is no relations between the [40854.592726] names, then host name confusion attack is possible. Apr 26 03:25:04 192.168.122.209 [40854.735280] [tempesta fw] Configuration processing is completed. Apr 26 03:25:04 192.168.122.209 [40854.785865] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:25:04 192.168.122.209 [40855.218366] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:25:04 192.168.122.209 [40855.245443] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:25:04 192.168.122.209 [40855.273401] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:25:05 192.168.122.209 [40855.331247] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:25:05 192.168.122.209 [40855.371208] [tempesta fw] Tempesta FW is ready Apr 26 03:25:05 192.168.122.209 [40855.959219] [tdb] Close table 'client0.tdb' Apr 26 03:25:05 192.168.122.209 [40856.162033] [tdb] Close table 'sessions0.tdb' Apr 26 03:25:08 192.168.122.209 [40859.271027] [tdb] Close table 'cache0.tdb' Apr 26 03:25:09 192.168.122.209 [40859.501792] [tdb] Close table 'filter0.tdb' Apr 26 03:25:09 192.168.122.209 [40859.502213] [tempesta fw] modules are stopped Apr 26 03:25:09 192.168.122.209 [40859.731213] [tempesta fw] exiting... Apr 26 03:25:09 192.168.122.209 [40859.875390] [tdb] Shutdown Tempesta DB Apr 26 03:25:09 192.168.122.209 [40860.060808] End test: http2_general.test_h2_hpack.TestHpack.test_disable_huffman Apr 26 03:25:09 192.168.122.209 [40860.071647] Start test: http2_general.test_h2_hpack.TestHpack.test_get_method_as_string Apr 26 03:25:10 192.168.122.209 [40861.220547] [tdb] Start Tempesta DB Apr 26 03:25:11 192.168.122.209 [40861.365462] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:25:12 192.168.122.209 [40863.017809] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40863.017809] Maybe that's fine, but it's worth checking the [40863.017809] config - if there is no relations between the [40863.017809] names, then host name confusion attack is possible. Apr 26 03:25:12 192.168.122.209 [40863.179368] [tempesta fw] Configuration processing is completed. Apr 26 03:25:12 192.168.122.209 [40863.233412] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:25:13 192.168.122.209 [40863.676061] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:25:13 192.168.122.209 [40863.712191] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:25:13 192.168.122.209 [40863.739357] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:25:13 192.168.122.209 [40863.787368] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:25:13 192.168.122.209 [40863.831339] [tempesta fw] Tempesta FW is ready Apr 26 03:25:14 192.168.122.209 [40864.433664] [tdb] Close table 'client0.tdb' Apr 26 03:25:14 192.168.122.209 [40864.665303] [tdb] Close table 'sessions0.tdb' Apr 26 03:25:17 192.168.122.209 [40867.852931] [tdb] Close table 'cache0.tdb' Apr 26 03:25:17 192.168.122.209 [40868.096812] [tdb] Close table 'filter0.tdb' Apr 26 03:25:17 192.168.122.209 [40868.097247] [tempesta fw] modules are stopped Apr 26 03:25:18 192.168.122.209 [40868.356093] [tempesta fw] exiting... Apr 26 03:25:18 192.168.122.209 [40868.532691] [tdb] Shutdown Tempesta DB Apr 26 03:25:18 192.168.122.209 [40868.749591] End test: http2_general.test_h2_hpack.TestHpack.test_get_method_as_string Apr 26 03:25:18 192.168.122.209 [40868.762243] Start test: http2_general.test_h2_hpack.TestHpack.test_http_headers_code_charater_is_invalid_in_header Apr 26 03:25:19 192.168.122.209 [40869.916925] [tdb] Start Tempesta DB Apr 26 03:25:19 192.168.122.209 [40870.064324] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:25:21 192.168.122.209 [40871.716394] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40871.716394] Maybe that's fine, but it's worth checking the [40871.716394] config - if there is no relations between the [40871.716394] names, then host name confusion attack is possible. Apr 26 03:25:21 192.168.122.209 [40871.895907] [tempesta fw] Configuration processing is completed. Apr 26 03:25:21 192.168.122.209 [40871.955677] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:25:22 192.168.122.209 [40872.425375] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:25:22 192.168.122.209 [40872.454094] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:25:22 192.168.122.209 [40872.488493] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:25:22 192.168.122.209 [40872.535491] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:25:22 192.168.122.209 [40872.575418] [tempesta fw] Tempesta FW is ready Apr 26 03:25:22 192.168.122.209 [40872.734342] [tempesta fw] Warning: Parser error: state=RGen_HdrOtherV input(-8)=0x1('qwerty: ') data_len=201 off=78 Apr 26 03:25:22 192.168.122.209 [40872.738190] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 03:25:22 192.168.122.209 [40873.176339] [tdb] Close table 'client0.tdb' Apr 26 03:25:23 192.168.122.209 [40873.372663] [tdb] Close table 'sessions0.tdb' Apr 26 03:25:26 192.168.122.209 [40876.489140] [tdb] Close table 'cache0.tdb' Apr 26 03:25:26 192.168.122.209 [40876.724258] [tdb] Close table 'filter0.tdb' Apr 26 03:25:26 192.168.122.209 [40876.724679] [tempesta fw] modules are stopped Apr 26 03:25:26 192.168.122.209 [40876.935052] [tempesta fw] exiting... Apr 26 03:25:26 192.168.122.209 [40877.074781] [tdb] Shutdown Tempesta DB Apr 26 03:25:26 192.168.122.209 [40877.290364] End test: http2_general.test_h2_hpack.TestHpack.test_http_headers_code_charater_is_invalid_in_header Apr 26 03:25:26 192.168.122.209 [40877.300740] Start test: http2_general.test_h2_hpack.TestHpack.test_never_indexed Apr 26 03:25:28 192.168.122.209 [40878.462381] [tdb] Start Tempesta DB Apr 26 03:25:28 192.168.122.209 [40878.605291] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:25:29 192.168.122.209 [40880.164994] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40880.164994] Maybe that's fine, but it's worth checking the [40880.164994] config - if there is no relations between the [40880.164994] names, then host name confusion attack is possible. Apr 26 03:25:29 192.168.122.209 [40880.315595] [tempesta fw] Configuration processing is completed. Apr 26 03:25:30 192.168.122.209 [40880.405710] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:25:30 192.168.122.209 [40880.826333] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:25:30 192.168.122.209 [40880.853504] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:25:30 192.168.122.209 [40880.881075] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:25:30 192.168.122.209 [40880.979613] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:25:30 192.168.122.209 [40881.023523] [tempesta fw] Tempesta FW is ready Apr 26 03:25:31 192.168.122.209 [40881.653047] [tdb] Close table 'client0.tdb' Apr 26 03:25:31 192.168.122.209 [40881.879273] [tdb] Close table 'sessions0.tdb' Apr 26 03:25:34 192.168.122.209 [40885.090669] [tdb] Close table 'cache0.tdb' Apr 26 03:25:35 192.168.122.209 [40885.326615] [tdb] Close table 'filter0.tdb' Apr 26 03:25:35 192.168.122.209 [40885.327057] [tempesta fw] modules are stopped Apr 26 03:25:35 192.168.122.209 [40885.572878] [tempesta fw] exiting... Apr 26 03:25:35 192.168.122.209 [40885.727954] [tdb] Shutdown Tempesta DB Apr 26 03:25:35 192.168.122.209 [40885.974466] End test: http2_general.test_h2_hpack.TestHpack.test_never_indexed Apr 26 03:25:35 192.168.122.209 [40885.985764] Start test: http2_general.test_h2_hpack.TestHpack.test_relloc_hpack_table Apr 26 03:25:36 192.168.122.209 [40887.191906] [tdb] Start Tempesta DB Apr 26 03:25:37 192.168.122.209 [40887.333849] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:25:38 192.168.122.209 [40888.985013] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40888.985013] Maybe that's fine, but it's worth checking the [40888.985013] config - if there is no relations between the [40888.985013] names, then host name confusion attack is possible. Apr 26 03:25:38 192.168.122.209 [40889.147736] [tempesta fw] Configuration processing is completed. Apr 26 03:25:38 192.168.122.209 [40889.199641] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:25:39 192.168.122.209 [40889.607971] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:25:39 192.168.122.209 [40889.633926] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:25:39 192.168.122.209 [40889.660939] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:25:39 192.168.122.209 [40889.707700] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:25:39 192.168.122.209 [40889.747645] [tempesta fw] Tempesta FW is ready Apr 26 03:26:15 192.168.122.209 [40926.207254] [tdb] Close table 'client0.tdb' Apr 26 03:26:16 192.168.122.209 [40926.416256] [tdb] Close table 'sessions0.tdb' Apr 26 03:26:19 192.168.122.209 [40929.619270] [tdb] Close table 'cache0.tdb' Apr 26 03:26:19 192.168.122.209 [40929.857842] [tdb] Close table 'filter0.tdb' Apr 26 03:26:19 192.168.122.209 [40929.858284] [tempesta fw] modules are stopped Apr 26 03:26:19 192.168.122.209 [40930.073846] [tempesta fw] exiting... Apr 26 03:26:19 192.168.122.209 [40930.214369] [tdb] Shutdown Tempesta DB Apr 26 03:26:20 192.168.122.209 [40930.427560] End test: http2_general.test_h2_hpack.TestHpack.test_relloc_hpack_table Apr 26 03:26:20 192.168.122.209 [40930.443533] Start test: http2_general.test_h2_hpack.TestHpack.test_rewrite_dynamic_table_for_request Apr 26 03:26:21 192.168.122.209 [40931.653060] [tdb] Start Tempesta DB Apr 26 03:26:21 192.168.122.209 [40931.785580] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:26:23 192.168.122.209 [40933.341767] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40933.341767] Maybe that's fine, but it's worth checking the [40933.341767] config - if there is no relations between the [40933.341767] names, then host name confusion attack is possible. Apr 26 03:26:23 192.168.122.209 [40933.492297] [tempesta fw] Configuration processing is completed. Apr 26 03:26:23 192.168.122.209 [40933.542507] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:26:23 192.168.122.209 [40933.948262] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:26:23 192.168.122.209 [40933.973810] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:26:23 192.168.122.209 [40934.000174] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:26:23 192.168.122.209 [40934.056265] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:26:23 192.168.122.209 [40934.100206] [tempesta fw] Tempesta FW is ready Apr 26 03:26:24 192.168.122.209 [40934.697712] [tdb] Close table 'client0.tdb' Apr 26 03:26:24 192.168.122.209 [40934.891750] [tdb] Close table 'sessions0.tdb' Apr 26 03:26:27 192.168.122.209 [40938.149415] [tdb] Close table 'cache0.tdb' Apr 26 03:26:28 192.168.122.209 [40938.428362] [tdb] Close table 'filter0.tdb' Apr 26 03:26:28 192.168.122.209 [40938.428835] [tempesta fw] modules are stopped Apr 26 03:26:28 192.168.122.209 [40938.678996] [tempesta fw] exiting... Apr 26 03:26:28 192.168.122.209 [40938.826849] [tdb] Shutdown Tempesta DB Apr 26 03:26:28 192.168.122.209 [40939.033003] End test: http2_general.test_h2_hpack.TestHpack.test_rewrite_dynamic_table_for_request Apr 26 03:26:28 192.168.122.209 [40939.044663] Start test: http2_general.test_h2_hpack.TestHpack.test_rewrite_dynamic_table_for_response Apr 26 03:26:29 192.168.122.209 [40940.165142] [tdb] Start Tempesta DB Apr 26 03:26:29 192.168.122.209 [40940.318789] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:26:31 192.168.122.209 [40941.981856] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40941.981856] Maybe that's fine, but it's worth checking the [40941.981856] config - if there is no relations between the [40941.981856] names, then host name confusion attack is possible. Apr 26 03:26:31 192.168.122.209 [40942.136379] [tempesta fw] Configuration processing is completed. Apr 26 03:26:31 192.168.122.209 [40942.221792] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:26:32 192.168.122.209 [40942.647803] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:26:32 192.168.122.209 [40942.676414] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:26:32 192.168.122.209 [40942.705885] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:26:32 192.168.122.209 [40942.840333] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:26:32 192.168.122.209 [40942.880324] [tempesta fw] Tempesta FW is ready Apr 26 03:26:33 192.168.122.209 [40943.483919] [tdb] Close table 'client0.tdb' Apr 26 03:26:33 192.168.122.209 [40943.692612] [tdb] Close table 'sessions0.tdb' Apr 26 03:26:36 192.168.122.209 [40946.831097] [tdb] Close table 'cache0.tdb' Apr 26 03:26:36 192.168.122.209 [40947.073692] [tdb] Close table 'filter0.tdb' Apr 26 03:26:36 192.168.122.209 [40947.074869] [tempesta fw] modules are stopped Apr 26 03:26:37 192.168.122.209 [40947.350371] [tempesta fw] exiting... Apr 26 03:26:37 192.168.122.209 [40947.494363] [tdb] Shutdown Tempesta DB Apr 26 03:26:37 192.168.122.209 [40947.707990] End test: http2_general.test_h2_hpack.TestHpack.test_rewrite_dynamic_table_for_response Apr 26 03:26:37 192.168.122.209 [40947.717943] Start test: http2_general.test_h2_hpack.TestHpack.test_send_invalid_request_after_setting_header_table_size Apr 26 03:26:38 192.168.122.209 [40948.917703] [tdb] Start Tempesta DB Apr 26 03:26:38 192.168.122.209 [40949.074318] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:26:40 192.168.122.209 [40950.629927] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40950.629927] Maybe that's fine, but it's worth checking the [40950.629927] config - if there is no relations between the [40950.629927] names, then host name confusion attack is possible. Apr 26 03:26:40 192.168.122.209 [40950.780483] [tempesta fw] Configuration processing is completed. Apr 26 03:26:40 192.168.122.209 [40950.830826] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:26:40 192.168.122.209 [40951.254944] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:26:40 192.168.122.209 [40951.281173] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:26:40 192.168.122.209 [40951.306922] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:26:41 192.168.122.209 [40951.368480] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:26:41 192.168.122.209 [40951.404427] [tempesta fw] Tempesta FW is ready Apr 26 03:26:41 192.168.122.209 [40951.556259] [tempesta fw] Warning: request has been filtered out via http table: 127.0.0.2 Apr 26 03:26:41 192.168.122.209 [40951.959884] [tdb] Close table 'client0.tdb' Apr 26 03:26:41 192.168.122.209 [40952.187295] [tdb] Close table 'sessions0.tdb' Apr 26 03:26:45 192.168.122.209 [40955.430224] [tdb] Close table 'cache0.tdb' Apr 26 03:26:45 192.168.122.209 [40955.654445] [tdb] Close table 'filter0.tdb' Apr 26 03:26:45 192.168.122.209 [40955.654882] [tempesta fw] modules are stopped Apr 26 03:26:45 192.168.122.209 [40955.872237] [tempesta fw] exiting... Apr 26 03:26:45 192.168.122.209 [40956.034031] [tdb] Shutdown Tempesta DB Apr 26 03:26:45 192.168.122.209 [40956.221875] End test: http2_general.test_h2_hpack.TestHpack.test_send_invalid_request_after_setting_header_table_size Apr 26 03:26:45 192.168.122.209 [40956.235520] Start test: http2_general.test_h2_hpack.TestHpack.test_settings_header_table_size Apr 26 03:26:47 192.168.122.209 [40957.445831] [tdb] Start Tempesta DB Apr 26 03:26:47 192.168.122.209 [40957.599330] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:26:48 192.168.122.209 [40959.210001] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40959.210001] Maybe that's fine, but it's worth checking the [40959.210001] config - if there is no relations between the [40959.210001] names, then host name confusion attack is possible. Apr 26 03:26:49 192.168.122.209 [40959.360808] [tempesta fw] Configuration processing is completed. Apr 26 03:26:49 192.168.122.209 [40959.416750] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:26:49 192.168.122.209 [40959.823116] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:26:49 192.168.122.209 [40959.848754] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:26:49 192.168.122.209 [40959.874515] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:26:49 192.168.122.209 [40959.916918] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:26:49 192.168.122.209 [40959.960530] [tempesta fw] Tempesta FW is ready Apr 26 03:26:50 192.168.122.209 [40960.587956] [tdb] Close table 'client0.tdb' Apr 26 03:26:50 192.168.122.209 [40960.779990] [tdb] Close table 'sessions0.tdb' Apr 26 03:26:53 192.168.122.209 [40963.911213] [tdb] Close table 'cache0.tdb' Apr 26 03:26:53 192.168.122.209 [40964.159230] [tdb] Close table 'filter0.tdb' Apr 26 03:26:53 192.168.122.209 [40964.159670] [tempesta fw] modules are stopped Apr 26 03:26:54 192.168.122.209 [40964.408887] [tempesta fw] exiting... Apr 26 03:26:54 192.168.122.209 [40964.583903] [tdb] Shutdown Tempesta DB Apr 26 03:26:54 192.168.122.209 [40964.790153] End test: http2_general.test_h2_hpack.TestHpack.test_settings_header_table_size Apr 26 03:26:54 192.168.122.209 [40964.801097] Start test: http2_general.test_h2_hpack.TestHpack.test_settings_header_table_stress Apr 26 03:26:55 192.168.122.209 [40966.012496] [tdb] Start Tempesta DB Apr 26 03:26:55 192.168.122.209 [40966.166189] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:26:57 192.168.122.209 [40967.810185] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40967.810185] Maybe that's fine, but it's worth checking the [40967.810185] config - if there is no relations between the [40967.810185] names, then host name confusion attack is possible. Apr 26 03:26:57 192.168.122.209 [40967.964686] [tempesta fw] Configuration processing is completed. Apr 26 03:26:57 192.168.122.209 [40968.047320] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:26:58 192.168.122.209 [40968.463393] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:26:58 192.168.122.209 [40968.490343] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:26:58 192.168.122.209 [40968.517041] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:26:58 192.168.122.209 [40968.608711] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:26:58 192.168.122.209 [40968.652649] [tempesta fw] Tempesta FW is ready Apr 26 03:27:07 192.168.122.209 [40977.412862] [tdb] Close table 'client0.tdb' Apr 26 03:27:07 192.168.122.209 [40977.600716] [tdb] Close table 'sessions0.tdb' Apr 26 03:27:10 192.168.122.209 [40980.760475] [tdb] Close table 'cache0.tdb' Apr 26 03:27:10 192.168.122.209 [40980.994687] [tdb] Close table 'filter0.tdb' Apr 26 03:27:10 192.168.122.209 [40980.995132] [tempesta fw] modules are stopped Apr 26 03:27:10 192.168.122.209 [40981.208169] [tempesta fw] exiting... Apr 26 03:27:11 192.168.122.209 [40981.364664] [tdb] Shutdown Tempesta DB Apr 26 03:27:11 192.168.122.209 [40981.613901] End test: http2_general.test_h2_hpack.TestHpack.test_settings_header_table_stress Apr 26 03:27:11 192.168.122.209 [40981.633128] Start test: http2_general.test_h2_hpack.TestHpack.test_static_table Apr 26 03:27:12 192.168.122.209 [40982.784740] [tdb] Start Tempesta DB Apr 26 03:27:12 192.168.122.209 [40982.939443] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:27:14 192.168.122.209 [40984.598017] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40984.598017] Maybe that's fine, but it's worth checking the [40984.598017] config - if there is no relations between the [40984.598017] names, then host name confusion attack is possible. Apr 26 03:27:14 192.168.122.209 [40984.769004] [tempesta fw] Configuration processing is completed. Apr 26 03:27:14 192.168.122.209 [40984.829426] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:27:14 192.168.122.209 [40985.248764] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:27:14 192.168.122.209 [40985.275850] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:27:14 192.168.122.209 [40985.301424] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:27:15 192.168.122.209 [40985.344872] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:27:15 192.168.122.209 [40985.384866] [tempesta fw] Tempesta FW is ready Apr 26 03:27:15 192.168.122.209 [40985.972771] [tdb] Close table 'client0.tdb' Apr 26 03:27:15 192.168.122.209 [40986.188992] [tdb] Close table 'sessions0.tdb' Apr 26 03:27:18 192.168.122.209 [40989.249192] [tdb] Close table 'cache0.tdb' Apr 26 03:27:19 192.168.122.209 [40989.473162] [tdb] Close table 'filter0.tdb' Apr 26 03:27:19 192.168.122.209 [40989.473604] [tempesta fw] modules are stopped Apr 26 03:27:19 192.168.122.209 [40989.755182] [tempesta fw] exiting... Apr 26 03:27:19 192.168.122.209 [40989.906830] [tdb] Shutdown Tempesta DB Apr 26 03:27:19 192.168.122.209 [40990.113267] End test: http2_general.test_h2_hpack.TestHpack.test_static_table Apr 26 03:27:19 192.168.122.209 [40990.131668] Start test: http2_general.test_h2_hpack.TestHpackBomb.test_hpack_bomb_huffman Apr 26 03:27:20 192.168.122.209 [40991.307272] [tdb] Start Tempesta DB Apr 26 03:27:21 192.168.122.209 [40991.465239] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:27:22 192.168.122.209 [40993.022663] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [40993.022663] Maybe that's fine, but it's worth checking the [40993.022663] config - if there is no relations between the [40993.022663] names, then host name confusion attack is possible. Apr 26 03:27:22 192.168.122.209 [40993.173045] [tempesta fw] Configuration processing is completed. Apr 26 03:27:22 192.168.122.209 [40993.222942] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:27:23 192.168.122.209 [40993.627524] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:27:23 192.168.122.209 [40993.653090] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:27:23 192.168.122.209 [40993.678314] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:27:23 192.168.122.209 [40993.732979] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:27:23 192.168.122.209 [40993.776973] [tempesta fw] Tempesta FW is ready Apr 26 03:27:24 192.168.122.209 [40994.406552] [tempesta fw] Warning: frang: HTTP header list size exceeded for 127.0.0.2: 69632 (lim=65536) Apr 26 03:27:24 192.168.122.209 [40994.927905] [tempesta fw] Warning: frang: HTTP header list size exceeded for 127.0.0.2: 69632 (lim=65536) Apr 26 03:27:25 192.168.122.209 [40995.379008] [tdb] Close table 'client0.tdb' Apr 26 03:27:25 192.168.122.209 [40995.580577] [tdb] Close table 'sessions0.tdb' Apr 26 03:27:28 192.168.122.209 [40998.749982] [tdb] Close table 'cache0.tdb' Apr 26 03:27:28 192.168.122.209 [40998.995254] [tdb] Close table 'filter0.tdb' Apr 26 03:27:28 192.168.122.209 [40998.995681] [tempesta fw] modules are stopped Apr 26 03:27:28 192.168.122.209 [40999.195106] [tempesta fw] exiting... Apr 26 03:27:29 192.168.122.209 [40999.370165] [tdb] Shutdown Tempesta DB Apr 26 03:27:29 192.168.122.209 [40999.582364] End test: http2_general.test_h2_hpack.TestHpackBomb.test_hpack_bomb_huffman Apr 26 03:27:29 192.168.122.209 [40999.603309] Start test: http2_general.test_h2_hpack.TestHpackBomb.test_hpack_bomb_no_huffman Apr 26 03:27:30 192.168.122.209 [41000.713938] [tdb] Start Tempesta DB Apr 26 03:27:30 192.168.122.209 [41000.865103] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:27:32 192.168.122.209 [41002.514547] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41002.514547] Maybe that's fine, but it's worth checking the [41002.514547] config - if there is no relations between the [41002.514547] names, then host name confusion attack is possible. Apr 26 03:27:32 192.168.122.209 [41002.677160] [tempesta fw] Configuration processing is completed. Apr 26 03:27:32 192.168.122.209 [41002.778473] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:27:32 192.168.122.209 [41003.191320] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:27:32 192.168.122.209 [41003.218009] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:27:32 192.168.122.209 [41003.242822] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:27:32 192.168.122.209 [41003.313147] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:27:33 192.168.122.209 [41003.357133] [tempesta fw] Tempesta FW is ready Apr 26 03:27:33 192.168.122.209 [41003.995129] [tempesta fw] Warning: frang: HTTP header list size exceeded for 127.0.0.2: 69632 (lim=65536) Apr 26 03:27:34 192.168.122.209 [41004.506591] [tempesta fw] Warning: frang: HTTP header list size exceeded for 127.0.0.2: 69632 (lim=65536) Apr 26 03:27:34 192.168.122.209 [41004.967004] [tdb] Close table 'client0.tdb' Apr 26 03:27:34 192.168.122.209 [41005.164468] [tdb] Close table 'sessions0.tdb' Apr 26 03:27:37 192.168.122.209 [41008.308599] [tdb] Close table 'cache0.tdb' Apr 26 03:27:38 192.168.122.209 [41008.557847] [tdb] Close table 'filter0.tdb' Apr 26 03:27:38 192.168.122.209 [41008.558334] [tempesta fw] modules are stopped Apr 26 03:27:38 192.168.122.209 [41008.801101] [tempesta fw] exiting... Apr 26 03:27:38 192.168.122.209 [41008.978259] [tdb] Shutdown Tempesta DB Apr 26 03:27:38 192.168.122.209 [41009.187408] End test: http2_general.test_h2_hpack.TestHpackBomb.test_hpack_bomb_no_huffman Apr 26 03:27:38 192.168.122.209 [41009.202247] Start test: http2_general.test_h2_hpack.TestHpackCache.test_h2_cache_200_after_setting_header_table_size Apr 26 03:27:40 192.168.122.209 [41010.349099] [tdb] Start Tempesta DB Apr 26 03:27:40 192.168.122.209 [41010.484775] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:27:41 192.168.122.209 [41012.070696] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41012.070696] Maybe that's fine, but it's worth checking the [41012.070696] config - if there is no relations between the [41012.070696] names, then host name confusion attack is possible. Apr 26 03:27:41 192.168.122.209 [41012.257291] [tempesta fw] Configuration processing is completed. Apr 26 03:27:41 192.168.122.209 [41012.309189] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:27:42 192.168.122.209 [41012.714737] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:27:42 192.168.122.209 [41012.748626] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:27:42 192.168.122.209 [41012.773569] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:27:42 192.168.122.209 [41012.821269] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:27:42 192.168.122.209 [41012.865176] [tempesta fw] Tempesta FW is ready Apr 26 03:27:43 192.168.122.209 [41013.451529] [tdb] Close table 'client0.tdb' Apr 26 03:27:43 192.168.122.209 [41013.668412] [tdb] Close table 'sessions0.tdb' Apr 26 03:27:46 192.168.122.209 [41016.816436] [tdb] Close table 'cache0.tdb' Apr 26 03:27:46 192.168.122.209 [41017.045000] [tdb] Close table 'filter0.tdb' Apr 26 03:27:46 192.168.122.209 [41017.045444] [tempesta fw] modules are stopped Apr 26 03:27:46 192.168.122.209 [41017.301038] [tempesta fw] exiting... Apr 26 03:27:47 192.168.122.209 [41017.474052] [tdb] Shutdown Tempesta DB Apr 26 03:27:47 192.168.122.209 [41017.717005] End test: http2_general.test_h2_hpack.TestHpackCache.test_h2_cache_200_after_setting_header_table_size Apr 26 03:27:47 192.168.122.209 [41017.729387] Start test: http2_general.test_h2_hpack.TestHpackCache.test_h2_cache_304_after_setting_header_table_size Apr 26 03:27:48 192.168.122.209 [41018.843263] [tdb] Start Tempesta DB Apr 26 03:27:48 192.168.122.209 [41018.997499] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:27:50 192.168.122.209 [41020.610814] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41020.610814] Maybe that's fine, but it's worth checking the [41020.610814] config - if there is no relations between the [41020.610814] names, then host name confusion attack is possible. Apr 26 03:27:50 192.168.122.209 [41020.797377] [tempesta fw] Configuration processing is completed. Apr 26 03:27:50 192.168.122.209 [41020.847766] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:27:50 192.168.122.209 [41021.266913] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:27:50 192.168.122.209 [41021.292876] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:27:50 192.168.122.209 [41021.319166] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:27:51 192.168.122.209 [41021.421397] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:27:51 192.168.122.209 [41021.461343] [tempesta fw] Tempesta FW is ready Apr 26 03:27:51 192.168.122.209 [41022.046744] [tdb] Close table 'client0.tdb' Apr 26 03:27:51 192.168.122.209 [41022.222288] [tdb] Close table 'sessions0.tdb' Apr 26 03:27:55 192.168.122.209 [41025.367505] [tdb] Close table 'cache0.tdb' Apr 26 03:27:55 192.168.122.209 [41025.607245] [tdb] Close table 'filter0.tdb' Apr 26 03:27:55 192.168.122.209 [41025.607682] [tempesta fw] modules are stopped Apr 26 03:27:55 192.168.122.209 [41025.826006] [tempesta fw] exiting... Apr 26 03:27:55 192.168.122.209 [41025.957825] [tdb] Shutdown Tempesta DB Apr 26 03:27:55 192.168.122.209 [41026.157044] End test: http2_general.test_h2_hpack.TestHpackCache.test_h2_cache_304_after_setting_header_table_size Apr 26 03:27:55 192.168.122.209 [41026.166572] Start test: http2_general.test_h2_hpack.TestHpackStickyCookie.test_h2_cookie_after_setting_header_table_size Apr 26 03:27:57 192.168.122.209 [41027.354293] [tdb] Start Tempesta DB Apr 26 03:27:57 192.168.122.209 [41027.509393] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:27:58 192.168.122.209 [41029.278865] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41029.278865] Maybe that's fine, but it's worth checking the [41029.278865] config - if there is no relations between the [41029.278865] names, then host name confusion attack is possible. Apr 26 03:27:59 192.168.122.209 [41029.441561] [tempesta fw] Configuration processing is completed. Apr 26 03:27:59 192.168.122.209 [41029.499978] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:27:59 192.168.122.209 [41029.911995] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:27:59 192.168.122.209 [41029.937600] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:27:59 192.168.122.209 [41029.967564] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:27:59 192.168.122.209 [41030.025477] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:27:59 192.168.122.209 [41030.069433] [tempesta fw] Tempesta FW is ready Apr 26 03:28:00 192.168.122.209 [41030.687066] [tdb] Close table 'client0.tdb' Apr 26 03:28:00 192.168.122.209 [41030.888643] [tdb] Close table 'sessions0.tdb' Apr 26 03:28:03 192.168.122.209 [41034.034125] [tdb] Close table 'cache0.tdb' Apr 26 03:28:03 192.168.122.209 [41034.295342] [tdb] Close table 'filter0.tdb' Apr 26 03:28:03 192.168.122.209 [41034.295793] [tempesta fw] modules are stopped Apr 26 03:28:04 192.168.122.209 [41034.531391] [tempesta fw] exiting... Apr 26 03:28:04 192.168.122.209 [41034.730037] [tdb] Shutdown Tempesta DB Apr 26 03:28:04 192.168.122.209 [41034.935955] End test: http2_general.test_h2_hpack.TestHpackStickyCookie.test_h2_cookie_after_setting_header_table_size Apr 26 03:28:04 192.168.122.209 [41034.954178] Start test: http2_general.test_h2_hpack.TestHpackTableSizeEncodedInInvalidPlace.test_begin Apr 26 03:28:05 192.168.122.209 [41036.125558] [tdb] Start Tempesta DB Apr 26 03:28:05 192.168.122.209 [41036.277370] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:28:07 192.168.122.209 [41037.930402] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41037.930402] Maybe that's fine, but it's worth checking the [41037.930402] config - if there is no relations between the [41037.930402] names, then host name confusion attack is possible. Apr 26 03:28:07 192.168.122.209 [41038.105595] [tempesta fw] Configuration processing is completed. Apr 26 03:28:07 192.168.122.209 [41038.199903] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:28:08 192.168.122.209 [41038.618581] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:28:08 192.168.122.209 [41038.645401] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:28:08 192.168.122.209 [41038.672313] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:28:08 192.168.122.209 [41038.725626] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:28:08 192.168.122.209 [41038.765547] [tempesta fw] Tempesta FW is ready Apr 26 03:28:09 192.168.122.209 [41039.367092] [tdb] Close table 'client0.tdb' Apr 26 03:28:09 192.168.122.209 [41039.571693] [tdb] Close table 'sessions0.tdb' Apr 26 03:28:12 192.168.122.209 [41042.761953] [tdb] Close table 'cache0.tdb' Apr 26 03:28:12 192.168.122.209 [41043.017585] [tdb] Close table 'filter0.tdb' Apr 26 03:28:12 192.168.122.209 [41043.018241] [tempesta fw] modules are stopped Apr 26 03:28:12 192.168.122.209 [41043.245312] [tempesta fw] exiting... Apr 26 03:28:13 192.168.122.209 [41043.398566] [tdb] Shutdown Tempesta DB Apr 26 03:28:13 192.168.122.209 [41043.610971] End test: http2_general.test_h2_hpack.TestHpackTableSizeEncodedInInvalidPlace.test_begin Apr 26 03:28:13 192.168.122.209 [41043.619915] Start test: http2_general.test_h2_hpack.TestHpackTableSizeEncodedInInvalidPlace.test_end Apr 26 03:28:14 192.168.122.209 [41044.645785] [tdb] Start Tempesta DB Apr 26 03:28:14 192.168.122.209 [41044.781159] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:28:15 192.168.122.209 [41046.299127] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41046.299127] Maybe that's fine, but it's worth checking the [41046.299127] config - if there is no relations between the [41046.299127] names, then host name confusion attack is possible. Apr 26 03:28:16 192.168.122.209 [41046.461713] [tempesta fw] Configuration processing is completed. Apr 26 03:28:16 192.168.122.209 [41046.526331] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:28:16 192.168.122.209 [41046.950806] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:28:16 192.168.122.209 [41046.988962] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:28:16 192.168.122.209 [41047.013970] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:28:16 192.168.122.209 [41047.073675] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:28:16 192.168.122.209 [41047.121631] [tempesta fw] Tempesta FW is ready Apr 26 03:28:17 192.168.122.209 [41047.731105] [tdb] Close table 'client0.tdb' Apr 26 03:28:17 192.168.122.209 [41047.913292] [tdb] Close table 'sessions0.tdb' Apr 26 03:28:20 192.168.122.209 [41051.187199] [tdb] Close table 'cache0.tdb' Apr 26 03:28:21 192.168.122.209 [41051.418997] [tdb] Close table 'filter0.tdb' Apr 26 03:28:21 192.168.122.209 [41051.419433] [tempesta fw] modules are stopped Apr 26 03:28:21 192.168.122.209 [41051.635371] [tempesta fw] exiting... Apr 26 03:28:21 192.168.122.209 [41051.811882] [tdb] Shutdown Tempesta DB Apr 26 03:28:21 192.168.122.209 [41052.045712] End test: http2_general.test_h2_hpack.TestHpackTableSizeEncodedInInvalidPlace.test_end Apr 26 03:28:21 192.168.122.209 [41052.060307] Start test: http2_general.test_h2_hpack.TestHpackTableSizeEncodedInInvalidPlace.test_middle Apr 26 03:28:22 192.168.122.209 [41053.219978] [tdb] Start Tempesta DB Apr 26 03:28:23 192.168.122.209 [41053.367171] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:28:24 192.168.122.209 [41055.019041] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41055.019041] Maybe that's fine, but it's worth checking the [41055.019041] config - if there is no relations between the [41055.019041] names, then host name confusion attack is possible. Apr 26 03:28:24 192.168.122.209 [41055.165806] [tempesta fw] Configuration processing is completed. Apr 26 03:28:24 192.168.122.209 [41055.226841] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:28:25 192.168.122.209 [41055.644771] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:28:25 192.168.122.209 [41055.679230] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:28:25 192.168.122.209 [41055.704763] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:28:25 192.168.122.209 [41055.761780] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:28:25 192.168.122.209 [41055.801731] [tempesta fw] Tempesta FW is ready Apr 26 03:28:26 192.168.122.209 [41056.371939] [tdb] Close table 'client0.tdb' Apr 26 03:28:26 192.168.122.209 [41056.592661] [tdb] Close table 'sessions0.tdb' Apr 26 03:28:29 192.168.122.209 [41059.727241] [tdb] Close table 'cache0.tdb' Apr 26 03:28:29 192.168.122.209 [41059.969546] [tdb] Close table 'filter0.tdb' Apr 26 03:28:29 192.168.122.209 [41059.969990] [tempesta fw] modules are stopped Apr 26 03:28:29 192.168.122.209 [41060.181776] [tempesta fw] exiting... Apr 26 03:28:29 192.168.122.209 [41060.314991] [tdb] Shutdown Tempesta DB Apr 26 03:28:30 192.168.122.209 [41060.531207] End test: http2_general.test_h2_hpack.TestHpackTableSizeEncodedInInvalidPlace.test_middle Apr 26 03:28:30 192.168.122.209 [41060.545165] Start test: http2_general.test_h2_hpack.TestHpackUnknownMethod.test_unknown_method_dynamic_table Apr 26 03:28:31 192.168.122.209 [41061.633487] [tdb] Start Tempesta DB Apr 26 03:28:31 192.168.122.209 [41061.784103] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:28:32 192.168.122.209 [41063.163415] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41063.163415] Maybe that's fine, but it's worth checking the [41063.163415] config - if there is no relations between the [41063.163415] names, then host name confusion attack is possible. Apr 26 03:28:32 192.168.122.209 [41063.282213] [tempesta fw] Configuration processing is completed. Apr 26 03:28:33 192.168.122.209 [41063.374092] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:28:33 192.168.122.209 [41063.785431] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:28:33 192.168.122.209 [41063.820307] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:28:33 192.168.122.209 [41063.847083] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:28:33 192.168.122.209 [41063.901897] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:28:33 192.168.122.209 [41063.949829] [tempesta fw] Tempesta FW is ready Apr 26 03:28:34 192.168.122.209 [41064.519415] [tdb] Close table 'client0.tdb' Apr 26 03:28:34 192.168.122.209 [41064.707283] [tdb] Close table 'sessions0.tdb' Apr 26 03:28:37 192.168.122.209 [41067.841112] [tdb] Close table 'cache0.tdb' Apr 26 03:28:37 192.168.122.209 [41068.127742] [tdb] Close table 'filter0.tdb' Apr 26 03:28:37 192.168.122.209 [41068.128163] [tempesta fw] modules are stopped Apr 26 03:28:38 192.168.122.209 [41068.366890] [tempesta fw] exiting... Apr 26 03:28:38 192.168.122.209 [41068.532145] [tdb] Shutdown Tempesta DB Apr 26 03:28:38 192.168.122.209 [41068.754573] End test: http2_general.test_h2_hpack.TestHpackUnknownMethod.test_unknown_method_dynamic_table Apr 26 03:28:38 192.168.122.209 [41068.764369] Start test: http2_general.test_h2_hpack.TestLoadingHeadersFromHpackDynamicTable.test_content_length_field_from_hpack_table Apr 26 03:28:39 192.168.122.209 [41069.770239] [tdb] Start Tempesta DB Apr 26 03:28:39 192.168.122.209 [41069.928898] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:28:41 192.168.122.209 [41071.587430] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41071.587430] Maybe that's fine, but it's worth checking the [41071.587430] config - if there is no relations between the [41071.587430] names, then host name confusion attack is possible. Apr 26 03:28:41 192.168.122.209 [41071.725952] [tempesta fw] Configuration processing is completed. Apr 26 03:28:41 192.168.122.209 [41071.776703] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:28:41 192.168.122.209 [41072.183794] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:28:41 192.168.122.209 [41072.209545] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:28:41 192.168.122.209 [41072.244889] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:28:41 192.168.122.209 [41072.297988] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:28:42 192.168.122.209 [41072.337922] [tempesta fw] Tempesta FW is ready Apr 26 03:28:42 192.168.122.209 [41072.467638] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102d00a80280" Apr 26 03:28:42 192.168.122.209 [41072.477590] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102d00a80280" Apr 26 03:28:42 192.168.122.209 [41072.904652] [tdb] Close table 'client0.tdb' Apr 26 03:28:42 192.168.122.209 [41073.128107] [tdb] Close table 'sessions0.tdb' Apr 26 03:28:45 192.168.122.209 [41076.292318] [tdb] Close table 'cache0.tdb' Apr 26 03:28:46 192.168.122.209 [41076.521512] [tdb] Close table 'filter0.tdb' Apr 26 03:28:46 192.168.122.209 [41076.521966] [tempesta fw] modules are stopped Apr 26 03:28:46 192.168.122.209 [41076.789252] [tempesta fw] exiting... Apr 26 03:28:46 192.168.122.209 [41076.963056] [tdb] Shutdown Tempesta DB Apr 26 03:28:46 192.168.122.209 [41077.161111] End test: http2_general.test_h2_hpack.TestLoadingHeadersFromHpackDynamicTable.test_content_length_field_from_hpack_table Apr 26 03:28:46 192.168.122.209 [41077.178772] Start test: http2_general.test_h2_hpack.TestLoadingHeadersFromHpackDynamicTable.test_content_type_from_hpack_table Apr 26 03:28:47 192.168.122.209 [41078.289202] [tdb] Start Tempesta DB Apr 26 03:28:48 192.168.122.209 [41078.423820] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:28:49 192.168.122.209 [41080.191498] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41080.191498] Maybe that's fine, but it's worth checking the [41080.191498] config - if there is no relations between the [41080.191498] names, then host name confusion attack is possible. Apr 26 03:28:50 192.168.122.209 [41080.346099] [tempesta fw] Configuration processing is completed. Apr 26 03:28:50 192.168.122.209 [41080.432723] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:28:50 192.168.122.209 [41080.850624] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:28:50 192.168.122.209 [41080.877324] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:28:50 192.168.122.209 [41080.904736] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:28:50 192.168.122.209 [41080.950081] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:28:50 192.168.122.209 [41080.990026] [tempesta fw] Tempesta FW is ready Apr 26 03:28:50 192.168.122.209 [41081.126880] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:50 192.168.122.209 [41081.132745] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:50 192.168.122.209 [41081.145850] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:50 192.168.122.209 [41081.155290] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:50 192.168.122.209 [41081.166312] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:50 192.168.122.209 [41081.176878] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:50 192.168.122.209 [41081.187617] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:50 192.168.122.209 [41081.198444] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:50 192.168.122.209 [41081.209264] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:50 192.168.122.209 [41081.219798] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:50 192.168.122.209 [41081.230714] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:50 192.168.122.209 [41081.241289] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:50 192.168.122.209 [41081.252136] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:50 192.168.122.209 [41081.262669] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:50 192.168.122.209 [41081.273527] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:50 192.168.122.209 [41081.284157] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:50 192.168.122.209 [41081.296166] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:50 192.168.122.209 [41081.305723] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:50 192.168.122.209 [41081.316422] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.327263] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.338013] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.348685] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.360536] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.370577] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.381184] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.391838] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.402922] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.413814] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.424698] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.435342] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.446342] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.457082] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.467795] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.478603] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.489579] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.500129] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.511261] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.521713] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.532304] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.543135] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.554134] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.564789] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.575588] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.586720] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.597512] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.608036] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.618999] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.629974] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.640844] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.651572] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.662459] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.673159] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.684210] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.695133] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.706369] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.717272] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.728290] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.739388] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.750491] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.761426] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.772726] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.783400] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.794573] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.808231] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.816544] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.827462] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.838951] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.849290] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.860467] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.871261] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.882398] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.893485] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.904651] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.915402] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.926728] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.937730] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.951355] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.961582] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.972139] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.982567] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41081.993043] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41082.003501] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41082.013929] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41082.024168] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41082.034903] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41082.045269] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41082.055646] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41082.066077] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41082.076525] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41082.087088] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41082.097616] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41082.108096] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41082.119035] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41082.128897] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41082.139379] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41082.149765] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41082.160289] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41082.170825] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41082.181675] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41082.191814] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41082.205068] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41082.212775] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41082.223292] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41082.234291] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41082.244425] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41082.254805] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41082.265299] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41082.275698] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41082.288271] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41082.299013] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41082.310381] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:51 192.168.122.209 [41082.321497] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.332600] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.343953] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.354948] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.365915] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.377153] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.388296] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.402396] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.410494] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.421769] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.432916] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.448405] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.459672] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.469617] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.480233] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.491303] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.502379] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.513673] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.524907] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.536445] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.547245] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.558766] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.569774] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.580875] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.592183] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.603670] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.614748] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.625936] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.637196] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.648471] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.659425] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.670948] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.682110] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.693527] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.705242] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.716099] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.727103] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.738852] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.750390] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.761462] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.772693] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.784107] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.795267] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.806825] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.818242] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.829584] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.840422] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.851780] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.863105] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.874541] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.889314] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.897441] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.908472] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.920304] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.931041] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.942703] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.953979] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.965420] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.976543] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.988159] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41082.999216] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41083.010655] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41083.022160] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41083.033750] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41083.044863] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41083.056585] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41083.067871] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41083.079398] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41083.090670] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41083.102195] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41083.113513] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41083.124850] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41083.136236] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41083.147605] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41083.158995] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41083.170605] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41083.182088] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41083.193613] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41083.204616] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41083.216151] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41083.227599] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41083.239160] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41083.250550] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41083.262185] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41083.272547] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41083.284158] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41083.295425] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41083.307177] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:52 192.168.122.209 [41083.318800] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:53 192.168.122.209 [41083.330082] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:53 192.168.122.209 [41083.341118] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:53 192.168.122.209 [41083.352750] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:53 192.168.122.209 [41083.367812] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:53 192.168.122.209 [41083.375924] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:53 192.168.122.209 [41083.388088] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:53 192.168.122.209 [41083.398080] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:53 192.168.122.209 [41083.412125] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:53 192.168.122.209 [41083.423133] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:53 192.168.122.209 [41083.434466] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:53 192.168.122.209 [41083.444809] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:53 192.168.122.209 [41083.455808] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:53 192.168.122.209 [41083.467096] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:53 192.168.122.209 [41083.480313] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:53 192.168.122.209 [41083.492098] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:53 192.168.122.209 [41083.503130] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:53 192.168.122.209 [41083.514945] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:53 192.168.122.209 [41083.526042] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:53 192.168.122.209 [41083.537296] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:53 192.168.122.209 [41083.548419] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:53 192.168.122.209 [41083.560137] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:53 192.168.122.209 [41083.571622] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:53 192.168.122.209 [41083.583244] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:53 192.168.122.209 [41083.594389] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:53 192.168.122.209 [41083.605440] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:53 192.168.122.209 [41083.616472] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:53 192.168.122.209 [41083.627871] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:53 192.168.122.209 [41083.639564] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:53 192.168.122.209 [41083.651271] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:53 192.168.122.209 [41083.662996] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:53 192.168.122.209 [41083.674643] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:53 192.168.122.209 [41083.686271] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:53 192.168.122.209 [41083.697761] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:53 192.168.122.209 [41083.710499] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:53 192.168.122.209 [41083.721000] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:53 192.168.122.209 [41083.732437] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:53 192.168.122.209 [41083.744376] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:53 192.168.122.209 [41083.755816] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:53 192.168.122.209 [41083.767349] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:53 192.168.122.209 [41083.779051] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:53 192.168.122.209 [41083.790546] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:53 192.168.122.209 [41083.801937] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:53 192.168.122.209 [41083.813589] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:53 192.168.122.209 [41083.825139] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:53 192.168.122.209 [41083.836951] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:53 192.168.122.209 [41083.848243] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:53 192.168.122.209 [41083.862828] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:53 192.168.122.209 [41083.871650] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:53 192.168.122.209 [41083.883471] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:53 192.168.122.209 [41083.894976] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 03:28:54 192.168.122.209 [41084.331759] [tdb] Close table 'client0.tdb' Apr 26 03:28:54 192.168.122.209 [41084.521636] [tdb] Close table 'sessions0.tdb' Apr 26 03:28:57 192.168.122.209 [41087.636666] [tdb] Close table 'cache0.tdb' Apr 26 03:28:57 192.168.122.209 [41087.875825] [tdb] Close table 'filter0.tdb' Apr 26 03:28:57 192.168.122.209 [41087.876287] [tempesta fw] modules are stopped Apr 26 03:28:57 192.168.122.209 [41088.098280] [tempesta fw] exiting... Apr 26 03:28:57 192.168.122.209 [41088.268969] [tdb] Shutdown Tempesta DB Apr 26 03:28:58 192.168.122.209 [41088.503767] End test: http2_general.test_h2_hpack.TestLoadingHeadersFromHpackDynamicTable.test_content_type_from_hpack_table Apr 26 03:28:58 192.168.122.209 [41088.521434] Start test: http2_general.test_h2_hpack.TestLoadingHeadersFromHpackDynamicTable.test_cookie_from_hpack_table_huffman_1 Apr 26 03:28:59 192.168.122.209 [41089.718923] [tdb] Start Tempesta DB Apr 26 03:28:59 192.168.122.209 [41089.872973] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:29:01 192.168.122.209 [41091.679714] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41091.679714] Maybe that's fine, but it's worth checking the [41091.679714] config - if there is no relations between the [41091.679714] names, then host name confusion attack is possible. Apr 26 03:29:01 192.168.122.209 [41091.834267] [tempesta fw] Configuration processing is completed. Apr 26 03:29:01 192.168.122.209 [41091.891046] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:29:01 192.168.122.209 [41092.305749] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:29:02 192.168.122.209 [41092.331580] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:29:02 192.168.122.209 [41092.358441] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:29:02 192.168.122.209 [41092.402213] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:29:02 192.168.122.209 [41092.450176] [tempesta fw] Tempesta FW is ready Apr 26 03:29:02 192.168.122.209 [41092.594538] [tempesta fw] 127.0.0.2 "good" "GET / HTTP/2.0" 200 0 "http://tempesta-tech.com:8080" "-" "ja5t=66cb8f00d4250002" "ja5h=2a67f7f008cc440" Apr 26 03:29:02 192.168.122.209 [41092.679973] [tempesta fw] 127.0.0.2 "good" "GET / HTTP/2.0" 200 0 "http://tempesta-tech.com:8080" "-" "ja5t=66cb8f00d4250002" "ja5h=3dae7f008c83c0" Apr 26 03:29:03 192.168.122.209 [41093.425097] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 03:29:03 192.168.122.209 [41093.539457] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41093.539457] Maybe that's fine, but it's worth checking the [41093.539457] config - if there is no relations between the [41093.539457] names, then host name confusion attack is possible. Apr 26 03:29:03 192.168.122.209 [41093.774244] [tempesta fw] Configuration processing is completed. Apr 26 03:29:03 192.168.122.209 [41094.017449] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000004da5e5e5 Apr 26 03:29:03 192.168.122.209 [41094.226336] [tempesta fw] Tempesta FW is ready Apr 26 03:29:03 192.168.122.209 [41094.281212] [tempesta fw] Warning: parsed request exceeded ja5h limit: 127.0.0.2 Apr 26 03:29:03 192.168.122.209 [41094.282443] [tempesta fw] 127.0.0.2 "-" "GET / HTTP/2.0" 403 0 "http://tempesta-tech.com:8080" "-" "ja5t=66cb8f00d4250002" "ja5h=2a67f7f008cc440" Apr 26 03:29:03 192.168.122.209 [41094.302783] [tempesta fw] Warning: parsed request exceeded ja5h limit: 127.0.0.2 Apr 26 03:29:03 192.168.122.209 [41094.303924] [tempesta fw] 127.0.0.2 "-" "GET / HTTP/2.0" 403 0 "http://tempesta-tech.com:8080" "-" "ja5t=66cb8f00d4250002" "ja5h=2a67f7f008cc440" Apr 26 03:29:04 192.168.122.209 [41094.720252] [tdb] Close table 'client0.tdb' Apr 26 03:29:04 192.168.122.209 [41094.925204] [tdb] Close table 'sessions0.tdb' Apr 26 03:29:07 192.168.122.209 [41098.112448] [tdb] Close table 'cache0.tdb' Apr 26 03:29:08 192.168.122.209 [41098.407321] [tdb] Close table 'filter0.tdb' Apr 26 03:29:08 192.168.122.209 [41099.084483] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 03:29:08 192.168.122.209 [41099.084944] [tempesta fw] modules are stopped Apr 26 03:29:09 192.168.122.209 [41099.324272] [tempesta fw] exiting... Apr 26 03:29:09 192.168.122.209 [41099.466635] [tdb] Shutdown Tempesta DB Apr 26 03:29:09 192.168.122.209 [41099.678914] End test: http2_general.test_h2_hpack.TestLoadingHeadersFromHpackDynamicTable.test_cookie_from_hpack_table_huffman_1 Apr 26 03:29:09 192.168.122.209 [41099.686884] Start test: http2_general.test_h2_hpack.TestLoadingHeadersFromHpackDynamicTable.test_cookie_from_hpack_table_huffman_2 Apr 26 03:29:10 192.168.122.209 [41100.801446] [tdb] Start Tempesta DB Apr 26 03:29:10 192.168.122.209 [41100.940706] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:29:12 192.168.122.209 [41102.759886] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41102.759886] Maybe that's fine, but it's worth checking the [41102.759886] config - if there is no relations between the [41102.759886] names, then host name confusion attack is possible. Apr 26 03:29:12 192.168.122.209 [41102.890404] [tempesta fw] Configuration processing is completed. Apr 26 03:29:12 192.168.122.209 [41102.947126] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:29:13 192.168.122.209 [41103.360387] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:29:13 192.168.122.209 [41103.395363] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:29:13 192.168.122.209 [41103.421421] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:29:13 192.168.122.209 [41103.474251] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:29:13 192.168.122.209 [41103.514306] [tempesta fw] Tempesta FW is ready Apr 26 03:29:13 192.168.122.209 [41103.641636] [tempesta fw] 127.0.0.2 "good" "GET / HTTP/2.0" 200 0 "http://tempesta-tech.com:8080" "-" "ja5t=66cb8f00d4250002" "ja5h=62f91f7f008fec40" Apr 26 03:29:13 192.168.122.209 [41103.713285] [tempesta fw] 127.0.0.2 "good" "GET / HTTP/2.0" 200 0 "http://tempesta-tech.com:8080" "-" "ja5t=66cb8f00d4250002" "ja5h=3dae7f008c83c0" Apr 26 03:29:14 192.168.122.209 [41104.456656] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 03:29:14 192.168.122.209 [41104.571559] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41104.571559] Maybe that's fine, but it's worth checking the [41104.571559] config - if there is no relations between the [41104.571559] names, then host name confusion attack is possible. Apr 26 03:29:14 192.168.122.209 [41104.790751] [tempesta fw] Configuration processing is completed. Apr 26 03:29:14 192.168.122.209 [41104.956543] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000004da5e5e5 Apr 26 03:29:14 192.168.122.209 [41105.158399] [tempesta fw] Tempesta FW is ready Apr 26 03:29:14 192.168.122.209 [41105.200678] [tempesta fw] Warning: parsed request exceeded ja5h limit: 127.0.0.2 Apr 26 03:29:14 192.168.122.209 [41105.202365] [tempesta fw] 127.0.0.2 "-" "GET / HTTP/2.0" 403 0 "http://tempesta-tech.com:8080" "-" "ja5t=66cb8f00d4250002" "ja5h=62f91f7f008fec40" Apr 26 03:29:14 192.168.122.209 [41105.223022] [tempesta fw] Warning: parsed request exceeded ja5h limit: 127.0.0.2 Apr 26 03:29:14 192.168.122.209 [41105.225111] [tempesta fw] 127.0.0.2 "-" "GET / HTTP/2.0" 403 0 "http://tempesta-tech.com:8080" "-" "ja5t=66cb8f00d4250002" "ja5h=62f91f7f008fec40" Apr 26 03:29:15 192.168.122.209 [41105.647837] [tdb] Close table 'client0.tdb' Apr 26 03:29:15 192.168.122.209 [41105.839660] [tdb] Close table 'sessions0.tdb' Apr 26 03:29:18 192.168.122.209 [41108.956614] [tdb] Close table 'cache0.tdb' Apr 26 03:29:18 192.168.122.209 [41109.220865] [tdb] Close table 'filter0.tdb' Apr 26 03:29:19 192.168.122.209 [41109.873184] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 03:29:19 192.168.122.209 [41109.873643] [tempesta fw] modules are stopped Apr 26 03:29:19 192.168.122.209 [41110.112406] [tempesta fw] exiting... Apr 26 03:29:19 192.168.122.209 [41110.272929] [tdb] Shutdown Tempesta DB Apr 26 03:29:20 192.168.122.209 [41110.471147] End test: http2_general.test_h2_hpack.TestLoadingHeadersFromHpackDynamicTable.test_cookie_from_hpack_table_huffman_2 Apr 26 03:29:20 192.168.122.209 [41110.503124] Start test: http2_general.test_h2_hpack.TestLoadingHeadersFromHpackDynamicTable.test_cookie_from_hpack_table_no_huffman_1 Apr 26 03:29:21 192.168.122.209 [41111.686410] [tdb] Start Tempesta DB Apr 26 03:29:21 192.168.122.209 [41111.833761] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:29:23 192.168.122.209 [41113.719946] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41113.719946] Maybe that's fine, but it's worth checking the [41113.719946] config - if there is no relations between the [41113.719946] names, then host name confusion attack is possible. Apr 26 03:29:23 192.168.122.209 [41113.850531] [tempesta fw] Configuration processing is completed. Apr 26 03:29:23 192.168.122.209 [41113.912065] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:29:24 192.168.122.209 [41114.329475] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:29:24 192.168.122.209 [41114.355669] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:29:24 192.168.122.209 [41114.382778] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:29:24 192.168.122.209 [41114.438492] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:29:24 192.168.122.209 [41114.482448] [tempesta fw] Tempesta FW is ready Apr 26 03:29:24 192.168.122.209 [41114.621898] [tempesta fw] 127.0.0.2 "good" "GET / HTTP/2.0" 200 0 "http://tempesta-tech.com:8080" "-" "ja5t=66cb8f00d4250002" "ja5h=2a67f7f008cc440" Apr 26 03:29:24 192.168.122.209 [41114.706309] [tempesta fw] 127.0.0.2 "good" "GET / HTTP/2.0" 200 0 "http://tempesta-tech.com:8080" "-" "ja5t=66cb8f00d4250002" "ja5h=3dae7f008c83c0" Apr 26 03:29:25 192.168.122.209 [41115.423170] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 03:29:25 192.168.122.209 [41115.539689] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41115.539689] Maybe that's fine, but it's worth checking the [41115.539689] config - if there is no relations between the [41115.539689] names, then host name confusion attack is possible. Apr 26 03:29:25 192.168.122.209 [41115.746530] [tempesta fw] Configuration processing is completed. Apr 26 03:29:25 192.168.122.209 [41115.919948] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000004da5e5e5 Apr 26 03:29:25 192.168.122.209 [41116.122523] [tempesta fw] Tempesta FW is ready Apr 26 03:29:25 192.168.122.209 [41116.180601] [tempesta fw] Warning: parsed request exceeded ja5h limit: 127.0.0.2 Apr 26 03:29:25 192.168.122.209 [41116.181285] [tempesta fw] 127.0.0.2 "-" "GET / HTTP/2.0" 403 0 "http://tempesta-tech.com:8080" "-" "ja5t=66cb8f00d4250002" "ja5h=2a67f7f008cc440" Apr 26 03:29:25 192.168.122.209 [41116.204063] [tempesta fw] Warning: parsed request exceeded ja5h limit: 127.0.0.2 Apr 26 03:29:25 192.168.122.209 [41116.204783] [tempesta fw] 127.0.0.2 "-" "GET / HTTP/2.0" 403 0 "http://tempesta-tech.com:8080" "-" "ja5t=66cb8f00d4250002" "ja5h=2a67f7f008cc440" Apr 26 03:29:26 192.168.122.209 [41116.672886] [tdb] Close table 'client0.tdb' Apr 26 03:29:26 192.168.122.209 [41116.865895] [tdb] Close table 'sessions0.tdb' Apr 26 03:29:29 192.168.122.209 [41119.942881] [tdb] Close table 'cache0.tdb' Apr 26 03:29:29 192.168.122.209 [41120.217195] [tdb] Close table 'filter0.tdb' Apr 26 03:29:30 192.168.122.209 [41120.861353] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 03:29:30 192.168.122.209 [41120.861811] [tempesta fw] modules are stopped Apr 26 03:29:30 192.168.122.209 [41121.085190] [tempesta fw] exiting... Apr 26 03:29:30 192.168.122.209 [41121.216426] [tdb] Shutdown Tempesta DB Apr 26 03:29:31 192.168.122.209 [41121.422579] End test: http2_general.test_h2_hpack.TestLoadingHeadersFromHpackDynamicTable.test_cookie_from_hpack_table_no_huffman_1 Apr 26 03:29:31 192.168.122.209 [41121.434201] Start test: http2_general.test_h2_hpack.TestLoadingHeadersFromHpackDynamicTable.test_cookie_from_hpack_table_no_huffman_2 Apr 26 03:29:32 192.168.122.209 [41122.635873] [tdb] Start Tempesta DB Apr 26 03:29:32 192.168.122.209 [41122.793660] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:29:34 192.168.122.209 [41124.740091] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41124.740091] Maybe that's fine, but it's worth checking the [41124.740091] config - if there is no relations between the [41124.740091] names, then host name confusion attack is possible. Apr 26 03:29:34 192.168.122.209 [41124.878672] [tempesta fw] Configuration processing is completed. Apr 26 03:29:34 192.168.122.209 [41124.929514] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:29:35 192.168.122.209 [41125.330769] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:29:35 192.168.122.209 [41125.356163] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:29:35 192.168.122.209 [41125.382749] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:29:35 192.168.122.209 [41125.430626] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:29:35 192.168.122.209 [41125.486583] [tempesta fw] Tempesta FW is ready Apr 26 03:29:35 192.168.122.209 [41125.665679] [tempesta fw] 127.0.0.2 "good" "GET / HTTP/2.0" 200 0 "http://tempesta-tech.com:8080" "-" "ja5t=66cb8f00d4250002" "ja5h=62f91f7f008fec40" Apr 26 03:29:35 192.168.122.209 [41125.739110] [tempesta fw] 127.0.0.2 "good" "GET / HTTP/2.0" 200 0 "http://tempesta-tech.com:8080" "-" "ja5t=66cb8f00d4250002" "ja5h=3dae7f008c83c0" Apr 26 03:29:36 192.168.122.209 [41126.474149] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 03:29:36 192.168.122.209 [41126.595836] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41126.595836] Maybe that's fine, but it's worth checking the [41126.595836] config - if there is no relations between the [41126.595836] names, then host name confusion attack is possible. Apr 26 03:29:36 192.168.122.209 [41126.810667] [tempesta fw] Configuration processing is completed. Apr 26 03:29:36 192.168.122.209 [41126.984519] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000004da5e5e5 Apr 26 03:29:36 192.168.122.209 [41127.190663] [tempesta fw] Tempesta FW is ready Apr 26 03:29:36 192.168.122.209 [41127.233272] [tempesta fw] Warning: parsed request exceeded ja5h limit: 127.0.0.2 Apr 26 03:29:36 192.168.122.209 [41127.235324] [tempesta fw] 127.0.0.2 "-" "GET / HTTP/2.0" 403 0 "http://tempesta-tech.com:8080" "-" "ja5t=66cb8f00d4250002" "ja5h=62f91f7f008fec40" Apr 26 03:29:36 192.168.122.209 [41127.255386] [tempesta fw] Warning: parsed request exceeded ja5h limit: 127.0.0.2 Apr 26 03:29:36 192.168.122.209 [41127.256432] [tempesta fw] 127.0.0.2 "-" "GET / HTTP/2.0" 403 0 "http://tempesta-tech.com:8080" "-" "ja5t=66cb8f00d4250002" "ja5h=62f91f7f008fec40" Apr 26 03:29:37 192.168.122.209 [41127.686368] [tdb] Close table 'client0.tdb' Apr 26 03:29:37 192.168.122.209 [41127.876945] [tdb] Close table 'sessions0.tdb' Apr 26 03:29:40 192.168.122.209 [41131.027477] [tdb] Close table 'cache0.tdb' Apr 26 03:29:40 192.168.122.209 [41131.270150] [tdb] Close table 'filter0.tdb' Apr 26 03:29:41 192.168.122.209 [41131.921371] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 03:29:41 192.168.122.209 [41131.921806] [tempesta fw] modules are stopped Apr 26 03:29:41 192.168.122.209 [41132.214425] [tempesta fw] exiting... Apr 26 03:29:42 192.168.122.209 [41132.395092] [tdb] Shutdown Tempesta DB Apr 26 03:29:42 192.168.122.209 [41132.590487] End test: http2_general.test_h2_hpack.TestLoadingHeadersFromHpackDynamicTable.test_cookie_from_hpack_table_no_huffman_2 Apr 26 03:29:42 192.168.122.209 [41132.605250] Start test: http2_general.test_h2_hpack.TestLoadingHeadersFromHpackDynamicTable.test_method_override_from_hpack_table Apr 26 03:29:43 192.168.122.209 [41133.796371] [tdb] Start Tempesta DB Apr 26 03:29:43 192.168.122.209 [41133.947405] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:29:45 192.168.122.209 [41135.904254] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41135.904254] Maybe that's fine, but it's worth checking the [41135.904254] config - if there is no relations between the [41135.904254] names, then host name confusion attack is possible. Apr 26 03:29:45 192.168.122.209 [41136.038800] [tempesta fw] Configuration processing is completed. Apr 26 03:29:45 192.168.122.209 [41136.090160] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:29:46 192.168.122.209 [41136.511108] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:29:46 192.168.122.209 [41136.537994] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:29:46 192.168.122.209 [41136.564176] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:29:46 192.168.122.209 [41136.610764] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:29:46 192.168.122.209 [41136.650692] [tempesta fw] Tempesta FW is ready Apr 26 03:29:47 192.168.122.209 [41137.463812] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 03:29:47 192.168.122.209 [41137.583927] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41137.583927] Maybe that's fine, but it's worth checking the [41137.583927] config - if there is no relations between the [41137.583927] names, then host name confusion attack is possible. Apr 26 03:29:47 192.168.122.209 [41137.758831] [tempesta fw] Configuration processing is completed. Apr 26 03:29:47 192.168.122.209 [41138.051193] [tempesta fw] Tempesta FW is ready Apr 26 03:29:47 192.168.122.209 [41138.096187] [tempesta fw] 127.0.0.2 "good" "GET / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=74683da0008c0280" Apr 26 03:29:48 192.168.122.209 [41138.734687] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 03:29:48 192.168.122.209 [41138.840202] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41138.840202] Maybe that's fine, but it's worth checking the [41138.840202] config - if there is no relations between the [41138.840202] names, then host name confusion attack is possible. Apr 26 03:29:48 192.168.122.209 [41139.006796] [tempesta fw] Configuration processing is completed. Apr 26 03:29:48 192.168.122.209 [41139.314805] [tempesta fw] Tempesta FW is ready Apr 26 03:29:49 192.168.122.209 [41139.363145] [tempesta fw] Warning: frang: restricted overridden HTTP method for 127.0.0.2: 4 (0x10u) Apr 26 03:29:49 192.168.122.209 [41139.363979] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 03:29:49 192.168.122.209 [41139.364698] [tempesta fw] 127.0.0.2 "good" "GET / HTTP/2.0" 403 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=74683da0008c0280" Apr 26 03:29:49 192.168.122.209 [41139.809745] [tdb] Close table 'client0.tdb' Apr 26 03:29:49 192.168.122.209 [41139.983713] [tdb] Close table 'sessions0.tdb' Apr 26 03:29:52 192.168.122.209 [41143.107979] [tdb] Close table 'cache0.tdb' Apr 26 03:29:53 192.168.122.209 [41143.354117] [tdb] Close table 'filter0.tdb' Apr 26 03:29:53 192.168.122.209 [41143.354590] [tempesta fw] modules are stopped Apr 26 03:29:53 192.168.122.209 [41143.564155] [tempesta fw] exiting... Apr 26 03:29:53 192.168.122.209 [41143.727311] [tdb] Shutdown Tempesta DB Apr 26 03:29:53 192.168.122.209 [41143.943820] End test: http2_general.test_h2_hpack.TestLoadingHeadersFromHpackDynamicTable.test_method_override_from_hpack_table Apr 26 03:29:53 192.168.122.209 [41143.950523] Start test: http2_general.test_h2_hpack.TestLoadingHeadersFromHpackDynamicTable.test_pragma_from_hpack_table Apr 26 03:29:54 192.168.122.209 [41145.183167] [tdb] Start Tempesta DB Apr 26 03:29:55 192.168.122.209 [41145.333526] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:29:56 192.168.122.209 [41147.060351] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41147.060351] Maybe that's fine, but it's worth checking the [41147.060351] config - if there is no relations between the [41147.060351] names, then host name confusion attack is possible. Apr 26 03:29:56 192.168.122.209 [41147.194947] [tempesta fw] Configuration processing is completed. Apr 26 03:29:56 192.168.122.209 [41147.245358] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:29:57 192.168.122.209 [41147.650499] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:29:57 192.168.122.209 [41147.684863] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:29:57 192.168.122.209 [41147.710412] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:29:57 192.168.122.209 [41147.766892] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:29:57 192.168.122.209 [41147.818839] [tempesta fw] Tempesta FW is ready Apr 26 03:29:58 192.168.122.209 [41148.628792] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 03:29:58 192.168.122.209 [41148.788052] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41148.788052] Maybe that's fine, but it's worth checking the [41148.788052] config - if there is no relations between the [41148.788052] names, then host name confusion attack is possible. Apr 26 03:29:58 192.168.122.209 [41148.954927] [tempesta fw] Configuration processing is completed. Apr 26 03:29:58 192.168.122.209 [41149.247357] [tempesta fw] Tempesta FW is ready Apr 26 03:29:58 192.168.122.209 [41149.295375] [tempesta fw] 127.0.0.2 "good" "GET / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=67618298008c0280" Apr 26 03:29:58 192.168.122.209 [41149.301397] [tempesta fw] 127.0.0.2 "good" "GET / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=67618298008c0280" Apr 26 03:29:58 192.168.122.209 [41149.311901] [tempesta fw] 127.0.0.2 "good" "GET / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=178008c0200" Apr 26 03:29:58 192.168.122.209 [41149.322111] [tempesta fw] 127.0.0.2 "good" "GET / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=178008c0200" Apr 26 03:29:59 192.168.122.209 [41149.767807] [tdb] Close table 'client0.tdb' Apr 26 03:29:59 192.168.122.209 [41149.957010] [tdb] Close table 'sessions0.tdb' Apr 26 03:30:02 192.168.122.209 [41153.120725] [tdb] Close table 'cache0.tdb' Apr 26 03:30:03 192.168.122.209 [41153.354668] [tdb] Close table 'filter0.tdb' Apr 26 03:30:03 192.168.122.209 [41153.355103] [tempesta fw] modules are stopped Apr 26 03:30:03 192.168.122.209 [41153.630323] [tempesta fw] exiting... Apr 26 03:30:03 192.168.122.209 [41153.763636] [tdb] Shutdown Tempesta DB Apr 26 03:30:03 192.168.122.209 [41154.005883] End test: http2_general.test_h2_hpack.TestLoadingHeadersFromHpackDynamicTable.test_pragma_from_hpack_table Apr 26 03:30:03 192.168.122.209 [41154.018619] Start test: http2_general.test_h2_hpack.TestLoadingHeadersFromHpackDynamicTable.test_referer_from_hpack_table Apr 26 03:30:04 192.168.122.209 [41155.163907] [tdb] Start Tempesta DB Apr 26 03:30:04 192.168.122.209 [41155.312957] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:30:06 192.168.122.209 [41157.060472] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41157.060472] Maybe that's fine, but it's worth checking the [41157.060472] config - if there is no relations between the [41157.060472] names, then host name confusion attack is possible. Apr 26 03:30:06 192.168.122.209 [41157.199046] [tempesta fw] Configuration processing is completed. Apr 26 03:30:06 192.168.122.209 [41157.249976] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:30:07 192.168.122.209 [41157.668147] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:30:07 192.168.122.209 [41157.703674] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:30:07 192.168.122.209 [41157.730632] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:30:07 192.168.122.209 [41157.779012] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:30:07 192.168.122.209 [41157.838958] [tempesta fw] Tempesta FW is ready Apr 26 03:30:07 192.168.122.209 [41157.976287] [tempesta fw] 127.0.0.2 "good" "GET / HTTP/2.0" 200 0 "http://tempesta-tech.com:8080" "-" "ja5t=66cb8f00d4250002" "ja5h=1033008c02c0" Apr 26 03:30:08 192.168.122.209 [41158.806277] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 03:30:08 192.168.122.209 [41158.920410] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41158.920410] Maybe that's fine, but it's worth checking the [41158.920410] config - if there is no relations between the [41158.920410] names, then host name confusion attack is possible. Apr 26 03:30:08 192.168.122.209 [41159.107084] [tempesta fw] Configuration processing is completed. Apr 26 03:30:08 192.168.122.209 [41159.268404] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000004da5e5e5 Apr 26 03:30:09 192.168.122.209 [41159.467065] [tempesta fw] Tempesta FW is ready Apr 26 03:30:09 192.168.122.209 [41159.512774] [tempesta fw] 127.0.0.2 "good" "GET / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=178008c0200" Apr 26 03:30:09 192.168.122.209 [41159.523028] [tempesta fw] Warning: parsed request exceeded ja5h limit: 127.0.0.2 Apr 26 03:30:09 192.168.122.209 [41159.524286] [tempesta fw] 127.0.0.2 "-" "GET / HTTP/2.0" 403 0 "http://tempesta-tech.com:8080" "-" "ja5t=66cb8f00d4250002" "ja5h=1033008c02c0" Apr 26 03:30:09 192.168.122.209 [41159.946461] [tdb] Close table 'client0.tdb' Apr 26 03:30:09 192.168.122.209 [41160.132037] [tdb] Close table 'sessions0.tdb' Apr 26 03:30:12 192.168.122.209 [41163.274558] [tdb] Close table 'cache0.tdb' Apr 26 03:30:13 192.168.122.209 [41163.511123] [tdb] Close table 'filter0.tdb' Apr 26 03:30:13 192.168.122.209 [41164.152585] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 03:30:13 192.168.122.209 [41164.153048] [tempesta fw] modules are stopped Apr 26 03:30:14 192.168.122.209 [41164.423119] [tempesta fw] exiting... Apr 26 03:30:14 192.168.122.209 [41164.593045] [tdb] Shutdown Tempesta DB Apr 26 03:30:14 192.168.122.209 [41164.839400] End test: http2_general.test_h2_hpack.TestLoadingHeadersFromHpackDynamicTable.test_referer_from_hpack_table Apr 26 03:30:14 192.168.122.209 [41164.851657] Start test: http2_general.test_h2_max_frame_size.TestMaxFrameSize.test_data_frame_is_large_than_max_frame_size Apr 26 03:30:15 192.168.122.209 [41166.026732] [tdb] Start Tempesta DB Apr 26 03:30:15 192.168.122.209 [41166.182710] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:30:17 192.168.122.209 [41168.004520] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41168.004520] Maybe that's fine, but it's worth checking the [41168.004520] config - if there is no relations between the [41168.004520] names, then host name confusion attack is possible. Apr 26 03:30:17 192.168.122.209 [41168.151178] [tempesta fw] Configuration processing is completed. Apr 26 03:30:17 192.168.122.209 [41168.208235] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:30:18 192.168.122.209 [41168.629966] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:30:18 192.168.122.209 [41168.656004] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:30:18 192.168.122.209 [41168.682459] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:30:18 192.168.122.209 [41168.723148] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:30:18 192.168.122.209 [41168.763113] [tempesta fw] Tempesta FW is ready Apr 26 03:30:18 192.168.122.209 [41169.291880] [tdb] Close table 'client0.tdb' Apr 26 03:30:19 192.168.122.209 [41169.515964] [tdb] Close table 'sessions0.tdb' Apr 26 03:30:22 192.168.122.209 [41172.681358] [tdb] Close table 'cache0.tdb' Apr 26 03:30:22 192.168.122.209 [41172.908715] [tdb] Close table 'filter0.tdb' Apr 26 03:30:22 192.168.122.209 [41172.909155] [tempesta fw] modules are stopped Apr 26 03:30:22 192.168.122.209 [41173.192578] [tempesta fw] exiting... Apr 26 03:30:23 192.168.122.209 [41173.354788] [tdb] Shutdown Tempesta DB Apr 26 03:30:23 192.168.122.209 [41173.571921] End test: http2_general.test_h2_max_frame_size.TestMaxFrameSize.test_data_frame_is_large_than_max_frame_size Apr 26 03:30:23 192.168.122.209 [41173.592687] Start test: http2_general.test_h2_max_frame_size.TestMaxFrameSize.test_headers_frame_is_large_than_max_frame_size Apr 26 03:30:24 192.168.122.209 [41174.794712] [tdb] Start Tempesta DB Apr 26 03:30:24 192.168.122.209 [41174.937573] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:30:26 192.168.122.209 [41176.532714] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41176.532714] Maybe that's fine, but it's worth checking the [41176.532714] config - if there is no relations between the [41176.532714] names, then host name confusion attack is possible. Apr 26 03:30:26 192.168.122.209 [41176.695263] [tempesta fw] Configuration processing is completed. Apr 26 03:30:26 192.168.122.209 [41176.783375] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:30:26 192.168.122.209 [41177.207431] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:30:26 192.168.122.209 [41177.233985] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:30:26 192.168.122.209 [41177.261059] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:30:26 192.168.122.209 [41177.299200] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:30:27 192.168.122.209 [41177.355215] [tempesta fw] Tempesta FW is ready Apr 26 03:30:27 192.168.122.209 [41177.974418] [tdb] Close table 'client0.tdb' Apr 26 03:30:27 192.168.122.209 [41178.155801] [tdb] Close table 'sessions0.tdb' Apr 26 03:30:31 192.168.122.209 [41181.342952] [tdb] Close table 'cache0.tdb' Apr 26 03:30:31 192.168.122.209 [41181.572664] [tdb] Close table 'filter0.tdb' Apr 26 03:30:31 192.168.122.209 [41181.573091] [tempesta fw] modules are stopped Apr 26 03:30:31 192.168.122.209 [41181.793596] [tempesta fw] exiting... Apr 26 03:30:31 192.168.122.209 [41181.959094] [tdb] Shutdown Tempesta DB Apr 26 03:30:31 192.168.122.209 [41182.165965] End test: http2_general.test_h2_max_frame_size.TestMaxFrameSize.test_headers_frame_is_large_than_max_frame_size Apr 26 03:30:31 192.168.122.209 [41182.182271] Start test: http2_general.test_h2_max_frame_size.TestMaxFrameSize.test_large_data_frame_in_response Apr 26 03:30:33 192.168.122.209 [41183.375187] [tdb] Start Tempesta DB Apr 26 03:30:33 192.168.122.209 [41183.522066] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:30:34 192.168.122.209 [41185.136781] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41185.136781] Maybe that's fine, but it's worth checking the [41185.136781] config - if there is no relations between the [41185.136781] names, then host name confusion attack is possible. Apr 26 03:30:34 192.168.122.209 [41185.299360] [tempesta fw] Configuration processing is completed. Apr 26 03:30:35 192.168.122.209 [41185.359108] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:30:35 192.168.122.209 [41185.768741] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:30:35 192.168.122.209 [41185.794533] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:30:35 192.168.122.209 [41185.820305] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:30:35 192.168.122.209 [41185.891317] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:30:35 192.168.122.209 [41185.939284] [tempesta fw] Tempesta FW is ready Apr 26 03:30:36 192.168.122.209 [41186.508658] [tdb] Close table 'client0.tdb' Apr 26 03:30:36 192.168.122.209 [41186.706716] [tdb] Close table 'sessions0.tdb' Apr 26 03:30:39 192.168.122.209 [41189.871524] [tdb] Close table 'cache0.tdb' Apr 26 03:30:39 192.168.122.209 [41190.104091] [tdb] Close table 'filter0.tdb' Apr 26 03:30:39 192.168.122.209 [41190.104523] [tempesta fw] modules are stopped Apr 26 03:30:40 192.168.122.209 [41190.328831] [tempesta fw] exiting... Apr 26 03:30:40 192.168.122.209 [41190.462735] [tdb] Shutdown Tempesta DB Apr 26 03:30:40 192.168.122.209 [41190.682171] End test: http2_general.test_h2_max_frame_size.TestMaxFrameSize.test_large_data_frame_in_response Apr 26 03:30:40 192.168.122.209 [41190.693121] Start test: http2_general.test_h2_max_frame_size.TestMaxFrameSize.test_large_headers_frame_in_response Apr 26 03:30:41 192.168.122.209 [41191.901960] [tdb] Start Tempesta DB Apr 26 03:30:41 192.168.122.209 [41192.057987] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:30:43 192.168.122.209 [41193.680941] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41193.680941] Maybe that's fine, but it's worth checking the [41193.680941] config - if there is no relations between the [41193.680941] names, then host name confusion attack is possible. Apr 26 03:30:43 192.168.122.209 [41193.831793] [tempesta fw] Configuration processing is completed. Apr 26 03:30:43 192.168.122.209 [41193.900046] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:30:43 192.168.122.209 [41194.313638] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:30:44 192.168.122.209 [41194.345254] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:30:44 192.168.122.209 [41194.371146] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:30:44 192.168.122.209 [41194.419437] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:30:44 192.168.122.209 [41194.483335] [tempesta fw] Tempesta FW is ready Apr 26 03:30:44 192.168.122.209 [41195.073174] [tdb] Close table 'client0.tdb' Apr 26 03:30:44 192.168.122.209 [41195.293368] [tdb] Close table 'sessions0.tdb' Apr 26 03:30:48 192.168.122.209 [41198.434575] [tdb] Close table 'cache0.tdb' Apr 26 03:30:48 192.168.122.209 [41198.678792] [tdb] Close table 'filter0.tdb' Apr 26 03:30:48 192.168.122.209 [41198.679218] [tempesta fw] modules are stopped Apr 26 03:30:48 192.168.122.209 [41198.909255] [tempesta fw] exiting... Apr 26 03:30:48 192.168.122.209 [41199.048361] [tdb] Shutdown Tempesta DB Apr 26 03:30:48 192.168.122.209 [41199.271835] End test: http2_general.test_h2_max_frame_size.TestMaxFrameSize.test_large_headers_frame_in_response Apr 26 03:30:48 192.168.122.209 [41199.284571] Start test: http2_general.test_h2_perf.TLSPerf.test Apr 26 03:30:50 192.168.122.209 [41200.672896] [tdb] Start Tempesta DB Apr 26 03:30:50 192.168.122.209 [41200.841799] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:30:51 192.168.122.209 [41202.204919] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41202.204919] Maybe that's fine, but it's worth checking the [41202.204919] config - if there is no relations between the [41202.204919] names, then host name confusion attack is possible. Apr 26 03:30:51 192.168.122.209 [41202.295588] [tempesta fw] Configuration processing is completed. Apr 26 03:30:52 192.168.122.209 [41202.381455] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:30:52 192.168.122.209 [41202.804870] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:30:52 192.168.122.209 [41202.840452] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:30:52 192.168.122.209 [41202.867820] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:30:52 192.168.122.209 [41202.931540] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:30:52 192.168.122.209 [41202.983486] [tempesta fw] Tempesta FW is ready Apr 26 03:31:03 192.168.122.209 [41213.630048] [tdb] Close table 'client0.tdb' Apr 26 03:31:03 192.168.122.209 [41213.822282] [tdb] Close table 'sessions0.tdb' Apr 26 03:31:06 192.168.122.209 [41217.084199] [tdb] Close table 'cache0.tdb' Apr 26 03:31:07 192.168.122.209 [41217.340662] [tdb] Close table 'filter0.tdb' Apr 26 03:31:07 192.168.122.209 [41217.341127] [tempesta fw] modules are stopped Apr 26 03:31:07 192.168.122.209 [41217.578656] [tempesta fw] exiting... Apr 26 03:31:07 192.168.122.209 [41217.752236] [tdb] Shutdown Tempesta DB Apr 26 03:31:07 192.168.122.209 [41218.042902] End test: http2_general.test_h2_perf.TLSPerf.test Apr 26 03:31:07 192.168.122.209 [41218.059355] Start test: http2_general.test_h2_ping.TestH2Ping.test Apr 26 03:31:08 192.168.122.209 [41219.269569] [tdb] Start Tempesta DB Apr 26 03:31:09 192.168.122.209 [41219.432816] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:31:10 192.168.122.209 [41220.913082] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [41220.913082] Maybe that's fine, but it's worth checking the [41220.913082] config - if there is no relations between the [41220.913082] names, then host name confusion attack is possible. Apr 26 03:31:10 192.168.122.209 [41220.960181] [tempesta fw] Configuration processing is completed. Apr 26 03:31:10 192.168.122.209 [41221.024877] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:31:11 192.168.122.209 [41221.481643] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:31:11 192.168.122.209 [41221.511371] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:31:11 192.168.122.209 [41221.546968] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:31:11 192.168.122.209 [41221.603801] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:31:11 192.168.122.209 [41221.651761] [tempesta fw] Tempesta FW is ready Apr 26 03:31:11 192.168.122.209 [41222.313705] [tdb] Close table 'client0.tdb' Apr 26 03:31:12 192.168.122.209 [41222.517926] [tdb] Close table 'sessions0.tdb' Apr 26 03:31:15 192.168.122.209 [41225.620549] [tdb] Close table 'cache0.tdb' Apr 26 03:31:15 192.168.122.209 [41225.870501] [tdb] Close table 'filter0.tdb' Apr 26 03:31:15 192.168.122.209 [41225.870935] [tempesta fw] modules are stopped Apr 26 03:31:15 192.168.122.209 [41226.067976] [tempesta fw] exiting... Apr 26 03:31:15 192.168.122.209 [41226.175450] [tdb] Shutdown Tempesta DB Apr 26 03:31:16 192.168.122.209 [41226.405169] End test: http2_general.test_h2_ping.TestH2Ping.test Apr 26 03:31:16 192.168.122.209 [41226.417957] Start test: http2_general.test_h2_responses.TestH2Responses.test_h2_bad_forwarded_for_ip Apr 26 03:31:17 192.168.122.209 [41227.619689] [tdb] Start Tempesta DB Apr 26 03:31:17 192.168.122.209 [41227.786495] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:31:19 192.168.122.209 [41229.533268] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41229.533268] Maybe that's fine, but it's worth checking the [41229.533268] config - if there is no relations between the [41229.533268] names, then host name confusion attack is possible. Apr 26 03:31:19 192.168.122.209 [41229.695889] [tempesta fw] Configuration processing is completed. Apr 26 03:31:19 192.168.122.209 [41229.761301] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:31:19 192.168.122.209 [41229.794335] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:31:19 192.168.122.209 [41229.825974] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:31:19 192.168.122.209 [41229.911887] [tempesta fw] Open listen socket on: 127.0.0.1:8765 Apr 26 03:31:19 192.168.122.209 [41229.963815] [tempesta fw] Tempesta FW is ready Apr 26 03:31:19 192.168.122.209 [41230.156791] [tempesta fw] Warning: request dropped: incorrect X-Forwarded-For header: 127.0.0.2 Apr 26 03:31:20 192.168.122.209 [41230.661857] [tdb] Close table 'client0.tdb' Apr 26 03:31:20 192.168.122.209 [41230.853049] [tdb] Close table 'sessions0.tdb' Apr 26 03:31:20 192.168.122.209 [41231.117139] [tdb] Close table 'filter0.tdb' Apr 26 03:31:20 192.168.122.209 [41231.117572] [tempesta fw] modules are stopped Apr 26 03:31:21 192.168.122.209 [41231.356483] [tempesta fw] exiting... Apr 26 03:31:21 192.168.122.209 [41231.540277] [tdb] Shutdown Tempesta DB Apr 26 03:31:21 192.168.122.209 [41231.812298] End test: http2_general.test_h2_responses.TestH2Responses.test_h2_bad_forwarded_for_ip Apr 26 03:31:21 192.168.122.209 [41231.833096] Start test: http2_general.test_h2_responses.TestH2Responses.test_h2_bad_header Apr 26 03:31:22 192.168.122.209 [41233.057012] [tdb] Start Tempesta DB Apr 26 03:31:22 192.168.122.209 [41233.219204] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:31:23 192.168.122.209 [41233.969151] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41233.969151] Maybe that's fine, but it's worth checking the [41233.969151] config - if there is no relations between the [41233.969151] names, then host name confusion attack is possible. Apr 26 03:31:23 192.168.122.209 [41234.119993] [tempesta fw] Configuration processing is completed. Apr 26 03:31:23 192.168.122.209 [41234.181420] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:31:23 192.168.122.209 [41234.218461] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:31:23 192.168.122.209 [41234.248874] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:31:24 192.168.122.209 [41234.327972] [tempesta fw] Open listen socket on: 127.0.0.1:8765 Apr 26 03:31:24 192.168.122.209 [41234.375904] [tempesta fw] Tempesta FW is ready Apr 26 03:31:24 192.168.122.209 [41234.610976] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrCookieV input=0x41('AAAAAA//dfsdf'), len=13, off=0 Apr 26 03:31:24 192.168.122.209 [41235.058790] [tdb] Close table 'client0.tdb' Apr 26 03:31:24 192.168.122.209 [41235.262497] [tdb] Close table 'sessions0.tdb' Apr 26 03:31:25 192.168.122.209 [41235.484903] [tdb] Close table 'filter0.tdb' Apr 26 03:31:25 192.168.122.209 [41235.485335] [tempesta fw] modules are stopped Apr 26 03:31:25 192.168.122.209 [41235.704604] [tempesta fw] exiting... Apr 26 03:31:25 192.168.122.209 [41235.861894] [tdb] Shutdown Tempesta DB Apr 26 03:31:25 192.168.122.209 [41236.082372] End test: http2_general.test_h2_responses.TestH2Responses.test_h2_bad_header Apr 26 03:31:25 192.168.122.209 [41236.093661] Start test: http2_general.test_h2_responses.TestH2Responses.test_h2_bad_host Apr 26 03:31:26 192.168.122.209 [41237.238664] [tdb] Start Tempesta DB Apr 26 03:31:27 192.168.122.209 [41237.392078] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:31:27 192.168.122.209 [41238.281241] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41238.281241] Maybe that's fine, but it's worth checking the [41238.281241] config - if there is no relations between the [41238.281241] names, then host name confusion attack is possible. Apr 26 03:31:28 192.168.122.209 [41238.428006] [tempesta fw] Configuration processing is completed. Apr 26 03:31:28 192.168.122.209 [41238.478984] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:31:28 192.168.122.209 [41238.506901] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:31:28 192.168.122.209 [41238.534981] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:31:28 192.168.122.209 [41238.607972] [tempesta fw] Open listen socket on: 127.0.0.1:8765 Apr 26 03:31:28 192.168.122.209 [41238.647954] [tempesta fw] Tempesta FW is ready Apr 26 03:31:28 192.168.122.209 [41238.817350] [tempesta fw] Warning: request has been filtered out via http table: 127.0.0.2 Apr 26 03:31:28 192.168.122.209 [41239.265058] [tdb] Close table 'client0.tdb' Apr 26 03:31:29 192.168.122.209 [41239.457973] [tdb] Close table 'sessions0.tdb' Apr 26 03:31:29 192.168.122.209 [41239.695950] [tdb] Close table 'filter0.tdb' Apr 26 03:31:29 192.168.122.209 [41239.696380] [tempesta fw] modules are stopped Apr 26 03:31:29 192.168.122.209 [41239.922930] [tempesta fw] exiting... Apr 26 03:31:29 192.168.122.209 [41240.081880] [tdb] Shutdown Tempesta DB Apr 26 03:31:30 192.168.122.209 [41240.330807] End test: http2_general.test_h2_responses.TestH2Responses.test_h2_bad_host Apr 26 03:31:30 192.168.122.209 [41240.342927] Start test: http2_general.test_h2_responses.TestH2ResponsesPipelined.test_bad_pipelined_first_fail Apr 26 03:31:31 192.168.122.209 [41241.484089] [tdb] Start Tempesta DB Apr 26 03:31:31 192.168.122.209 [41241.635907] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:31:32 192.168.122.209 [41242.425496] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41242.425496] Maybe that's fine, but it's worth checking the [41242.425496] config - if there is no relations between the [41242.425496] names, then host name confusion attack is possible. Apr 26 03:31:32 192.168.122.209 [41242.556175] [tempesta fw] Configuration processing is completed. Apr 26 03:31:32 192.168.122.209 [41242.608771] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:31:32 192.168.122.209 [41243.129181] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:31:32 192.168.122.209 [41243.205420] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:31:32 192.168.122.209 [41243.238110] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:31:32 192.168.122.209 [41243.276064] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:31:32 192.168.122.209 [41243.315969] [tempesta fw] Tempesta FW is ready Apr 26 03:31:33 192.168.122.209 [41243.471863] [tempesta fw] Warning: Parser error: state=RGen_HdrOtherN input(-8)=0x20('ebian [41243.471863] C ontent-Length: 0 [41243.471863] [41243.471863] HTTP/1.1 200 OK [41243.471863] Da') data_len=274 off=71 Apr 26 03:31:33 192.168.122.209 [41243.475413] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 03:31:33 192.168.122.209 [41243.916938] [tdb] Close table 'client0.tdb' Apr 26 03:31:33 192.168.122.209 [41244.104121] [tdb] Close table 'sessions0.tdb' Apr 26 03:31:37 192.168.122.209 [41247.326262] [tdb] Close table 'cache0.tdb' Apr 26 03:31:37 192.168.122.209 [41247.566597] [tdb] Close table 'filter0.tdb' Apr 26 03:31:37 192.168.122.209 [41247.567037] [tempesta fw] modules are stopped Apr 26 03:31:37 192.168.122.209 [41247.803155] [tempesta fw] exiting... Apr 26 03:31:37 192.168.122.209 [41247.967653] [tdb] Shutdown Tempesta DB Apr 26 03:31:37 192.168.122.209 [41248.183432] End test: http2_general.test_h2_responses.TestH2ResponsesPipelined.test_bad_pipelined_first_fail Apr 26 03:31:37 192.168.122.209 [41248.190932] Start test: http2_general.test_h2_responses.TestH2ResponsesPipelined.test_bad_pipelined_second_fail Apr 26 03:31:39 192.168.122.209 [41249.330999] [tdb] Start Tempesta DB Apr 26 03:31:39 192.168.122.209 [41249.462671] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:31:40 192.168.122.209 [41251.109616] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41251.109616] Maybe that's fine, but it's worth checking the [41251.109616] config - if there is no relations between the [41251.109616] names, then host name confusion attack is possible. Apr 26 03:31:40 192.168.122.209 [41251.240502] [tempesta fw] Configuration processing is completed. Apr 26 03:31:40 192.168.122.209 [41251.295642] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:31:41 192.168.122.209 [41251.714820] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:31:41 192.168.122.209 [41251.741777] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:31:41 192.168.122.209 [41251.768967] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:31:41 192.168.122.209 [41251.816147] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:31:41 192.168.122.209 [41251.860082] [tempesta fw] Tempesta FW is ready Apr 26 03:31:41 192.168.122.209 [41252.025155] [tempesta fw] Warning: Parser error: state=RGen_HdrOtherN input(-8)=0x20('ebian [41252.025155] C ontent-Length: 0 [41252.025155] [41252.025155] HTTP/1.1 200 OK [41252.025155] Da') data_len=183 off=71 Apr 26 03:31:41 192.168.122.209 [41252.026848] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 03:31:42 192.168.122.209 [41252.450417] [tdb] Close table 'client0.tdb' Apr 26 03:31:42 192.168.122.209 [41252.656228] [tdb] Close table 'sessions0.tdb' Apr 26 03:31:45 192.168.122.209 [41255.796676] [tdb] Close table 'cache0.tdb' Apr 26 03:31:45 192.168.122.209 [41256.035759] [tdb] Close table 'filter0.tdb' Apr 26 03:31:45 192.168.122.209 [41256.036205] [tempesta fw] modules are stopped Apr 26 03:31:45 192.168.122.209 [41256.259242] [tempesta fw] exiting... Apr 26 03:31:46 192.168.122.209 [41256.434383] [tdb] Shutdown Tempesta DB Apr 26 03:31:46 192.168.122.209 [41256.606383] End test: http2_general.test_h2_responses.TestH2ResponsesPipelined.test_bad_pipelined_second_fail Apr 26 03:31:46 192.168.122.209 [41256.630826] Start test: http2_general.test_h2_responses.TestH2ResponsesPipelined.test_bad_pipelined_third_fail Apr 26 03:31:47 192.168.122.209 [41257.784840] [tdb] Start Tempesta DB Apr 26 03:31:47 192.168.122.209 [41257.923905] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:31:49 192.168.122.209 [41259.509658] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41259.509658] Maybe that's fine, but it's worth checking the [41259.509658] config - if there is no relations between the [41259.509658] names, then host name confusion attack is possible. Apr 26 03:31:49 192.168.122.209 [41259.636278] [tempesta fw] Configuration processing is completed. Apr 26 03:31:49 192.168.122.209 [41259.687857] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:31:49 192.168.122.209 [41260.095259] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:31:49 192.168.122.209 [41260.120583] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:31:49 192.168.122.209 [41260.146092] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:31:49 192.168.122.209 [41260.184244] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:31:49 192.168.122.209 [41260.228089] [tempesta fw] Tempesta FW is ready Apr 26 03:31:50 192.168.122.209 [41260.383052] [tempesta fw] Warning: Parser error: state=RGen_HdrOtherN input(-8)=0x20('ebian [41260.383052] C ontent-Length: 0 [41260.383052] [41260.383052] ') data_len=92 off=71 Apr 26 03:31:50 192.168.122.209 [41260.386635] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 03:31:50 192.168.122.209 [41260.849276] [tdb] Close table 'client0.tdb' Apr 26 03:31:50 192.168.122.209 [41261.043396] [tdb] Close table 'sessions0.tdb' Apr 26 03:31:53 192.168.122.209 [41264.185450] [tdb] Close table 'cache0.tdb' Apr 26 03:31:54 192.168.122.209 [41264.415907] [tdb] Close table 'filter0.tdb' Apr 26 03:31:54 192.168.122.209 [41264.416365] [tempesta fw] modules are stopped Apr 26 03:31:54 192.168.122.209 [41264.687329] [tempesta fw] exiting... Apr 26 03:31:54 192.168.122.209 [41264.825896] [tdb] Shutdown Tempesta DB Apr 26 03:31:54 192.168.122.209 [41265.032827] End test: http2_general.test_h2_responses.TestH2ResponsesPipelined.test_bad_pipelined_third_fail Apr 26 03:31:54 192.168.122.209 [41265.046892] Start test: http2_general.test_h2_responses.TestH2ResponsesPipelined.test_success_pipelined Apr 26 03:31:55 192.168.122.209 [41266.214827] [tdb] Start Tempesta DB Apr 26 03:31:56 192.168.122.209 [41266.364974] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:31:57 192.168.122.209 [41267.957821] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41267.957821] Maybe that's fine, but it's worth checking the [41267.957821] config - if there is no relations between the [41267.957821] names, then host name confusion attack is possible. Apr 26 03:31:57 192.168.122.209 [41268.100376] [tempesta fw] Configuration processing is completed. Apr 26 03:31:57 192.168.122.209 [41268.166730] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:31:58 192.168.122.209 [41268.614250] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:31:58 192.168.122.209 [41268.645314] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:31:58 192.168.122.209 [41268.676956] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:31:58 192.168.122.209 [41268.724347] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:31:58 192.168.122.209 [41268.772274] [tempesta fw] Tempesta FW is ready Apr 26 03:31:59 192.168.122.209 [41269.387295] [tdb] Close table 'client0.tdb' Apr 26 03:31:59 192.168.122.209 [41269.589342] [tdb] Close table 'sessions0.tdb' Apr 26 03:32:02 192.168.122.209 [41272.933933] [tdb] Close table 'cache0.tdb' Apr 26 03:32:02 192.168.122.209 [41273.191537] [tdb] Close table 'filter0.tdb' Apr 26 03:32:02 192.168.122.209 [41273.191998] [tempesta fw] modules are stopped Apr 26 03:32:03 192.168.122.209 [41273.458368] [tempesta fw] exiting... Apr 26 03:32:03 192.168.122.209 [41273.614166] [tdb] Shutdown Tempesta DB Apr 26 03:32:03 192.168.122.209 [41273.869334] End test: http2_general.test_h2_responses.TestH2ResponsesPipelined.test_success_pipelined Apr 26 03:32:03 192.168.122.209 [41273.884118] Start test: http2_general.test_h2_sticky_cookie.H2StickyCookieBaseTestCase.test_h2_cookie_default Apr 26 03:32:04 192.168.122.209 [41275.185292] [tdb] Start Tempesta DB Apr 26 03:32:05 192.168.122.209 [41275.346486] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:32:06 192.168.122.209 [41277.049790] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41277.049790] Maybe that's fine, but it's worth checking the [41277.049790] config - if there is no relations between the [41277.049790] names, then host name confusion attack is possible. Apr 26 03:32:06 192.168.122.209 [41277.172474] [tempesta fw] Configuration processing is completed. Apr 26 03:32:06 192.168.122.209 [41277.226810] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:32:06 192.168.122.209 [41277.254344] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:32:06 192.168.122.209 [41277.282134] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:32:07 192.168.122.209 [41277.360444] [tempesta fw] Open listen socket on: 127.0.0.1:8765 Apr 26 03:32:07 192.168.122.209 [41277.408385] [tempesta fw] Tempesta FW is ready Apr 26 03:32:07 192.168.122.209 [41278.087566] [tdb] Close table 'client0.tdb' Apr 26 03:32:07 192.168.122.209 [41278.288822] [tdb] Close table 'sessions0.tdb' Apr 26 03:32:08 192.168.122.209 [41278.527573] [tdb] Close table 'filter0.tdb' Apr 26 03:32:08 192.168.122.209 [41278.528021] [tempesta fw] modules are stopped Apr 26 03:32:08 192.168.122.209 [41278.741757] [tempesta fw] exiting... Apr 26 03:32:08 192.168.122.209 [41278.910333] [tdb] Shutdown Tempesta DB Apr 26 03:32:08 192.168.122.209 [41279.155665] End test: http2_general.test_h2_sticky_cookie.H2StickyCookieBaseTestCase.test_h2_cookie_default Apr 26 03:32:08 192.168.122.209 [41279.176282] Start test: http2_general.test_h2_sticky_cookie.H2StickyCookieTestCase.test_h2_many_cookie_enforce Apr 26 03:32:10 192.168.122.209 [41280.366664] [tdb] Start Tempesta DB Apr 26 03:32:10 192.168.122.209 [41280.527423] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:32:11 192.168.122.209 [41281.369756] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41281.369756] Maybe that's fine, but it's worth checking the [41281.369756] config - if there is no relations between the [41281.369756] names, then host name confusion attack is possible. Apr 26 03:32:11 192.168.122.209 [41281.492536] [tempesta fw] Configuration processing is completed. Apr 26 03:32:11 192.168.122.209 [41281.543043] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:32:11 192.168.122.209 [41281.573663] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:32:11 192.168.122.209 [41281.602595] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:32:11 192.168.122.209 [41281.684508] [tempesta fw] Open listen socket on: 127.0.0.1:8765 Apr 26 03:32:11 192.168.122.209 [41281.720450] [tempesta fw] Tempesta FW is ready Apr 26 03:32:12 192.168.122.209 [41282.363169] [tdb] Close table 'client0.tdb' Apr 26 03:32:12 192.168.122.209 [41282.552810] [tdb] Close table 'sessions0.tdb' Apr 26 03:32:12 192.168.122.209 [41282.787503] [tdb] Close table 'filter0.tdb' Apr 26 03:32:12 192.168.122.209 [41282.787930] [tempesta fw] modules are stopped Apr 26 03:32:12 192.168.122.209 [41283.025334] [tempesta fw] exiting... Apr 26 03:32:12 192.168.122.209 [41283.148388] [tdb] Shutdown Tempesta DB Apr 26 03:32:13 192.168.122.209 [41283.413048] End test: http2_general.test_h2_sticky_cookie.H2StickyCookieTestCase.test_h2_many_cookie_enforce Apr 26 03:32:13 192.168.122.209 [41283.435607] Start test: http2_general.test_h2_sticky_cookie.H2StickyCookieTestCase.test_h2_no_cookie_enforce Apr 26 03:32:14 192.168.122.209 [41284.662394] [tdb] Start Tempesta DB Apr 26 03:32:14 192.168.122.209 [41284.808551] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:32:15 192.168.122.209 [41285.633821] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41285.633821] Maybe that's fine, but it's worth checking the [41285.633821] config - if there is no relations between the [41285.633821] names, then host name confusion attack is possible. Apr 26 03:32:15 192.168.122.209 [41285.760578] [tempesta fw] Configuration processing is completed. Apr 26 03:32:15 192.168.122.209 [41285.811039] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:32:15 192.168.122.209 [41285.838685] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:32:15 192.168.122.209 [41285.866665] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:32:15 192.168.122.209 [41285.968565] [tempesta fw] Open listen socket on: 127.0.0.1:8765 Apr 26 03:32:15 192.168.122.209 [41286.008494] [tempesta fw] Tempesta FW is ready Apr 26 03:32:16 192.168.122.209 [41286.635260] [tdb] Close table 'client0.tdb' Apr 26 03:32:16 192.168.122.209 [41286.833027] [tdb] Close table 'sessions0.tdb' Apr 26 03:32:16 192.168.122.209 [41287.076537] [tdb] Close table 'filter0.tdb' Apr 26 03:32:16 192.168.122.209 [41287.076949] [tempesta fw] modules are stopped Apr 26 03:32:16 192.168.122.209 [41287.311211] [tempesta fw] exiting... Apr 26 03:32:17 192.168.122.209 [41287.445012] [tdb] Shutdown Tempesta DB Apr 26 03:32:17 192.168.122.209 [41287.682346] End test: http2_general.test_h2_sticky_cookie.H2StickyCookieTestCase.test_h2_no_cookie_enforce Apr 26 03:32:17 192.168.122.209 [41287.696709] Start test: http2_general.test_h2_stream_priority.TestMaxConcurrentStreams.test_max_concurent_stream_exceed_by_priority_frame Apr 26 03:32:18 192.168.122.209 [41288.784505] [tdb] Start Tempesta DB Apr 26 03:32:18 192.168.122.209 [41288.945377] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:32:19 192.168.122.209 [41289.898040] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41289.898040] Maybe that's fine, but it's worth checking the [41289.898040] config - if there is no relations between the [41289.898040] names, then host name confusion attack is possible. Apr 26 03:32:19 192.168.122.209 [41290.052590] [tempesta fw] Configuration processing is completed. Apr 26 03:32:19 192.168.122.209 [41290.104303] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:32:20 192.168.122.209 [41290.506260] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:32:20 192.168.122.209 [41290.532312] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:32:20 192.168.122.209 [41290.558491] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:32:20 192.168.122.209 [41290.612605] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:32:20 192.168.122.209 [41290.652553] [tempesta fw] Tempesta FW is ready Apr 26 03:32:20 192.168.122.209 [41290.798835] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 03:32:20 192.168.122.209 [41290.799944] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.2 Apr 26 03:32:20 192.168.122.209 [41290.799955] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 03:32:20 192.168.122.209 [41290.803134] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 03:32:20 192.168.122.209 [41290.803141] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.2 Apr 26 03:32:20 192.168.122.209 [41290.805661] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.2 Apr 26 03:32:20 192.168.122.209 [41290.805666] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 03:32:20 192.168.122.209 [41291.216319] [tdb] Close table 'client0.tdb' Apr 26 03:32:21 192.168.122.209 [41291.392146] [tdb] Close table 'sessions0.tdb' Apr 26 03:32:24 192.168.122.209 [41294.548158] [tdb] Close table 'cache0.tdb' Apr 26 03:32:24 192.168.122.209 [41294.797331] [tdb] Close table 'filter0.tdb' Apr 26 03:32:24 192.168.122.209 [41295.045209] [tempesta fw] exiting... Apr 26 03:32:24 192.168.122.209 [41295.183608] [tdb] Shutdown Tempesta DB Apr 26 03:32:25 192.168.122.209 [41295.387541] End test: http2_general.test_h2_stream_priority.TestMaxConcurrentStreams.test_max_concurent_stream_exceed_by_priority_frame Apr 26 03:32:25 192.168.122.209 [41295.411722] Start test: http2_general.test_h2_stream_priority.TestMaxConcurrentStreams.test_max_concurent_stream_exceed_by_stream Apr 26 03:32:26 192.168.122.209 [41296.563425] [tdb] Start Tempesta DB Apr 26 03:32:26 192.168.122.209 [41296.707883] net_ratelimit: 6 callbacks suppressed Apr 26 03:32:26 192.168.122.209 [41296.707886] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:32:28 192.168.122.209 [41298.462121] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41298.462121] Maybe that's fine, but it's worth checking the [41298.462121] config - if there is no relations between the [41298.462121] names, then host name confusion attack is possible. Apr 26 03:32:28 192.168.122.209 [41298.612671] [tempesta fw] Configuration processing is completed. Apr 26 03:32:28 192.168.122.209 [41298.670812] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:32:28 192.168.122.209 [41299.080974] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:32:28 192.168.122.209 [41299.106227] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:32:28 192.168.122.209 [41299.131339] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:32:28 192.168.122.209 [41299.184711] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:32:28 192.168.122.209 [41299.224648] [tempesta fw] Tempesta FW is ready Apr 26 03:32:29 192.168.122.209 [41299.939659] [tdb] Close table 'client0.tdb' Apr 26 03:32:29 192.168.122.209 [41300.142621] [tdb] Close table 'sessions0.tdb' Apr 26 03:32:32 192.168.122.209 [41303.287453] [tdb] Close table 'cache0.tdb' Apr 26 03:32:33 192.168.122.209 [41303.544846] [tdb] Close table 'filter0.tdb' Apr 26 03:32:33 192.168.122.209 [41303.545304] [tempesta fw] modules are stopped Apr 26 03:32:33 192.168.122.209 [41303.780619] [tempesta fw] exiting... Apr 26 03:32:33 192.168.122.209 [41303.945993] [tdb] Shutdown Tempesta DB Apr 26 03:32:33 192.168.122.209 [41304.136817] End test: http2_general.test_h2_stream_priority.TestMaxConcurrentStreams.test_max_concurent_stream_exceed_by_stream Apr 26 03:32:33 192.168.122.209 [41304.151462] Start test: http2_general.test_h2_stream_priority.TestMaxConcurrentStreams.test_opening_created_idle_streams_after_exceed_max_concurrent_streams_limit Apr 26 03:32:35 192.168.122.209 [41305.341512] [tdb] Start Tempesta DB Apr 26 03:32:35 192.168.122.209 [41305.500732] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:32:36 192.168.122.209 [41307.282999] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41307.282999] Maybe that's fine, but it's worth checking the [41307.282999] config - if there is no relations between the [41307.282999] names, then host name confusion attack is possible. Apr 26 03:32:37 192.168.122.209 [41307.432828] [tempesta fw] Configuration processing is completed. Apr 26 03:32:37 192.168.122.209 [41307.486214] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:32:37 192.168.122.209 [41307.890586] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:32:37 192.168.122.209 [41307.946549] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:32:37 192.168.122.209 [41307.973279] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:32:37 192.168.122.209 [41308.016807] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:32:37 192.168.122.209 [41308.060754] [tempesta fw] Tempesta FW is ready Apr 26 03:32:38 192.168.122.209 [41308.864860] [tdb] Close table 'client0.tdb' Apr 26 03:32:38 192.168.122.209 [41309.060018] [tdb] Close table 'sessions0.tdb' Apr 26 03:32:41 192.168.122.209 [41312.206419] [tdb] Close table 'cache0.tdb' Apr 26 03:32:42 192.168.122.209 [41312.458851] [tdb] Close table 'filter0.tdb' Apr 26 03:32:42 192.168.122.209 [41312.459281] [tempesta fw] modules are stopped Apr 26 03:32:42 192.168.122.209 [41312.690091] [tempesta fw] exiting... Apr 26 03:32:42 192.168.122.209 [41312.854456] [tdb] Shutdown Tempesta DB Apr 26 03:32:42 192.168.122.209 [41313.032499] End test: http2_general.test_h2_stream_priority.TestMaxConcurrentStreams.test_opening_created_idle_streams_after_exceed_max_concurrent_streams_limit Apr 26 03:32:42 192.168.122.209 [41313.047899] Start test: http2_general.test_h2_stream_priority.TestMaxConcurrentStreams.test_opening_not_created_idle_streams_after_exceed_max_concurrent_streams_limit Apr 26 03:32:43 192.168.122.209 [41314.192472] [tdb] Start Tempesta DB Apr 26 03:32:44 192.168.122.209 [41314.356106] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:32:45 192.168.122.209 [41316.022371] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41316.022371] Maybe that's fine, but it's worth checking the [41316.022371] config - if there is no relations between the [41316.022371] names, then host name confusion attack is possible. Apr 26 03:32:45 192.168.122.209 [41316.168944] [tempesta fw] Configuration processing is completed. Apr 26 03:32:45 192.168.122.209 [41316.221926] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:32:46 192.168.122.209 [41316.628693] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:32:46 192.168.122.209 [41316.654275] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:32:46 192.168.122.209 [41316.679738] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:32:46 192.168.122.209 [41316.720925] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:32:46 192.168.122.209 [41316.760865] [tempesta fw] Tempesta FW is ready Apr 26 03:32:47 192.168.122.209 [41317.490705] [tdb] Close table 'client0.tdb' Apr 26 03:32:47 192.168.122.209 [41317.710781] [tdb] Close table 'sessions0.tdb' Apr 26 03:32:50 192.168.122.209 [41320.915742] [tdb] Close table 'cache0.tdb' Apr 26 03:32:50 192.168.122.209 [41321.132605] [tdb] Close table 'filter0.tdb' Apr 26 03:32:50 192.168.122.209 [41321.133074] [tempesta fw] modules are stopped Apr 26 03:32:51 192.168.122.209 [41321.335309] [tempesta fw] exiting... Apr 26 03:32:51 192.168.122.209 [41321.487436] [tdb] Shutdown Tempesta DB Apr 26 03:32:51 192.168.122.209 [41321.693192] End test: http2_general.test_h2_stream_priority.TestMaxConcurrentStreams.test_opening_not_created_idle_streams_after_exceed_max_concurrent_streams_limit Apr 26 03:32:51 192.168.122.209 [41321.726257] Start test: http2_general.test_h2_stream_priority.TestStreamPriorityInHeaders.test_stream_priority_from_existing_stream Apr 26 03:32:52 192.168.122.209 [41322.912745] [tdb] Start Tempesta DB Apr 26 03:32:52 192.168.122.209 [41323.055720] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:32:54 192.168.122.209 [41324.882493] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41324.882493] Maybe that's fine, but it's worth checking the [41324.882493] config - if there is no relations between the [41324.882493] names, then host name confusion attack is possible. Apr 26 03:32:54 192.168.122.209 [41325.033041] [tempesta fw] Configuration processing is completed. Apr 26 03:32:54 192.168.122.209 [41325.124212] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:32:55 192.168.122.209 [41325.537206] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:32:55 192.168.122.209 [41325.563795] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:32:55 192.168.122.209 [41325.591107] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:32:55 192.168.122.209 [41325.641033] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:32:55 192.168.122.209 [41325.680974] [tempesta fw] Tempesta FW is ready Apr 26 03:32:56 192.168.122.209 [41326.630855] [tdb] Close table 'client0.tdb' Apr 26 03:32:56 192.168.122.209 [41326.811430] [tdb] Close table 'sessions0.tdb' Apr 26 03:32:59 192.168.122.209 [41329.978457] [tdb] Close table 'cache0.tdb' Apr 26 03:32:59 192.168.122.209 [41330.243288] [tdb] Close table 'filter0.tdb' Apr 26 03:32:59 192.168.122.209 [41330.243726] [tempesta fw] modules are stopped Apr 26 03:33:00 192.168.122.209 [41330.485774] [tempesta fw] exiting... Apr 26 03:33:00 192.168.122.209 [41330.658915] [tdb] Shutdown Tempesta DB Apr 26 03:33:00 192.168.122.209 [41330.855192] End test: http2_general.test_h2_stream_priority.TestStreamPriorityInHeaders.test_stream_priority_from_existing_stream Apr 26 03:33:00 192.168.122.209 [41330.873702] Start test: http2_general.test_h2_stream_priority.TestStreamPriorityInHeaders.test_stream_priority_from_existing_stream_complex Apr 26 03:33:01 192.168.122.209 [41332.055877] [tdb] Start Tempesta DB Apr 26 03:33:01 192.168.122.209 [41332.207285] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:33:03 192.168.122.209 [41333.842561] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41333.842561] Maybe that's fine, but it's worth checking the [41333.842561] config - if there is no relations between the [41333.842561] names, then host name confusion attack is possible. Apr 26 03:33:03 192.168.122.209 [41334.017151] [tempesta fw] Configuration processing is completed. Apr 26 03:33:03 192.168.122.209 [41334.068226] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:33:04 192.168.122.209 [41334.483071] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:33:04 192.168.122.209 [41334.509144] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:33:04 192.168.122.209 [41334.534282] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:33:04 192.168.122.209 [41334.597143] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:33:04 192.168.122.209 [41334.641077] [tempesta fw] Tempesta FW is ready Apr 26 03:33:05 192.168.122.209 [41335.678126] [tdb] Close table 'client0.tdb' Apr 26 03:33:05 192.168.122.209 [41335.866045] [tdb] Close table 'sessions0.tdb' Apr 26 03:33:08 192.168.122.209 [41338.984344] [tdb] Close table 'cache0.tdb' Apr 26 03:33:08 192.168.122.209 [41339.229706] [tdb] Close table 'filter0.tdb' Apr 26 03:33:08 192.168.122.209 [41339.230127] [tempesta fw] modules are stopped Apr 26 03:33:09 192.168.122.209 [41339.502939] [tempesta fw] exiting... Apr 26 03:33:09 192.168.122.209 [41339.660709] [tdb] Shutdown Tempesta DB Apr 26 03:33:09 192.168.122.209 [41339.887783] End test: http2_general.test_h2_stream_priority.TestStreamPriorityInHeaders.test_stream_priority_from_existing_stream_complex Apr 26 03:33:09 192.168.122.209 [41339.897097] Start test: http2_general.test_h2_stream_priority.TestStreamPriorityInHeaders.test_stream_priority_from_existing_stream_complex_exclusive Apr 26 03:33:10 192.168.122.209 [41341.061299] [tdb] Start Tempesta DB Apr 26 03:33:10 192.168.122.209 [41341.216759] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:33:12 192.168.122.209 [41342.930705] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41342.930705] Maybe that's fine, but it's worth checking the [41342.930705] config - if there is no relations between the [41342.930705] names, then host name confusion attack is possible. Apr 26 03:33:12 192.168.122.209 [41343.093245] [tempesta fw] Configuration processing is completed. Apr 26 03:33:12 192.168.122.209 [41343.143378] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:33:13 192.168.122.209 [41343.572845] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:33:13 192.168.122.209 [41343.598890] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:33:13 192.168.122.209 [41343.624735] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:33:13 192.168.122.209 [41343.673246] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:33:13 192.168.122.209 [41343.713192] [tempesta fw] Tempesta FW is ready Apr 26 03:33:14 192.168.122.209 [41344.823633] [tdb] Close table 'client0.tdb' Apr 26 03:33:14 192.168.122.209 [41345.028555] [tdb] Close table 'sessions0.tdb' Apr 26 03:33:17 192.168.122.209 [41348.129821] [tdb] Close table 'cache0.tdb' Apr 26 03:33:18 192.168.122.209 [41348.355302] [tdb] Close table 'filter0.tdb' Apr 26 03:33:18 192.168.122.209 [41348.355745] [tempesta fw] modules are stopped Apr 26 03:33:18 192.168.122.209 [41348.566736] [tempesta fw] exiting... Apr 26 03:33:18 192.168.122.209 [41348.712073] [tdb] Shutdown Tempesta DB Apr 26 03:33:18 192.168.122.209 [41348.928161] End test: http2_general.test_h2_stream_priority.TestStreamPriorityInHeaders.test_stream_priority_from_existing_stream_complex_exclusive Apr 26 03:33:18 192.168.122.209 [41348.947743] Start test: http2_general.test_h2_stream_priority.TestStreamPriorityInHeaders.test_stream_priority_from_existing_stream_with_removal Apr 26 03:33:19 192.168.122.209 [41350.094021] [tdb] Start Tempesta DB Apr 26 03:33:19 192.168.122.209 [41350.230355] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:33:21 192.168.122.209 [41351.958781] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41351.958781] Maybe that's fine, but it's worth checking the [41351.958781] config - if there is no relations between the [41351.958781] names, then host name confusion attack is possible. Apr 26 03:33:21 192.168.122.209 [41352.117377] [tempesta fw] Configuration processing is completed. Apr 26 03:33:21 192.168.122.209 [41352.176353] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:33:22 192.168.122.209 [41352.577837] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:33:22 192.168.122.209 [41352.604013] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:33:22 192.168.122.209 [41352.629278] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:33:22 192.168.122.209 [41352.681365] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:33:22 192.168.122.209 [41352.733349] [tempesta fw] Tempesta FW is ready Apr 26 03:33:23 192.168.122.209 [41353.754596] [tdb] Close table 'client0.tdb' Apr 26 03:33:23 192.168.122.209 [41353.944854] [tdb] Close table 'sessions0.tdb' Apr 26 03:33:26 192.168.122.209 [41357.108291] [tdb] Close table 'cache0.tdb' Apr 26 03:33:27 192.168.122.209 [41357.358072] [tdb] Close table 'filter0.tdb' Apr 26 03:33:27 192.168.122.209 [41357.358507] [tempesta fw] modules are stopped Apr 26 03:33:27 192.168.122.209 [41357.633023] [tempesta fw] exiting... Apr 26 03:33:27 192.168.122.209 [41357.778096] [tdb] Shutdown Tempesta DB Apr 26 03:33:27 192.168.122.209 [41357.981438] End test: http2_general.test_h2_stream_priority.TestStreamPriorityInHeaders.test_stream_priority_from_existing_stream_with_removal Apr 26 03:33:27 192.168.122.209 [41357.996002] Start test: http2_general.test_h2_stream_priority.TestStreamPriorityInHeaders.test_stream_priority_from_non_existing_stream Apr 26 03:33:28 192.168.122.209 [41359.101138] [tdb] Start Tempesta DB Apr 26 03:33:28 192.168.122.209 [41359.258824] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:33:31 192.168.122.209 [41361.543007] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41361.543007] Maybe that's fine, but it's worth checking the [41361.543007] config - if there is no relations between the [41361.543007] names, then host name confusion attack is possible. Apr 26 03:33:32 192.168.122.209 [41362.449858] [tempesta fw] Configuration processing is completed. Apr 26 03:33:32 192.168.122.209 [41362.579092] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:33:32 192.168.122.209 [41362.996640] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:33:32 192.168.122.209 [41363.023503] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:33:32 192.168.122.209 [41363.050211] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:33:33 192.168.122.209 [41363.461499] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:33:33 192.168.122.209 [41363.737462] [tempesta fw] Tempesta FW is ready Apr 26 03:33:34 192.168.122.209 [41365.241829] [tdb] Close table 'client0.tdb' Apr 26 03:33:35 192.168.122.209 [41365.616505] [tdb] Close table 'sessions0.tdb' Apr 26 03:33:38 192.168.122.209 [41368.983580] [tdb] Close table 'cache0.tdb' Apr 26 03:33:38 192.168.122.209 [41369.200477] [tdb] Close table 'filter0.tdb' Apr 26 03:33:38 192.168.122.209 [41369.200901] [tempesta fw] modules are stopped Apr 26 03:33:39 192.168.122.209 [41369.435062] [tempesta fw] exiting... Apr 26 03:33:39 192.168.122.209 [41369.610641] [tdb] Shutdown Tempesta DB Apr 26 03:33:39 192.168.122.209 [41369.833307] End test: http2_general.test_h2_stream_priority.TestStreamPriorityInHeaders.test_stream_priority_from_non_existing_stream Apr 26 03:33:39 192.168.122.209 [41369.841511] Start test: http2_general.test_h2_stream_priority.TestStreamPriorityInPriorityFrames.test_stream_priority_from_existing_stream Apr 26 03:33:40 192.168.122.209 [41371.095721] [tdb] Start Tempesta DB Apr 26 03:33:40 192.168.122.209 [41371.256715] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:33:42 192.168.122.209 [41372.955080] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41372.955080] Maybe that's fine, but it's worth checking the [41372.955080] config - if there is no relations between the [41372.955080] names, then host name confusion attack is possible. Apr 26 03:33:42 192.168.122.209 [41373.101579] [tempesta fw] Configuration processing is completed. Apr 26 03:33:42 192.168.122.209 [41373.151823] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:33:43 192.168.122.209 [41373.572013] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:33:43 192.168.122.209 [41373.598304] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:33:43 192.168.122.209 [41373.624292] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:33:43 192.168.122.209 [41373.673608] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:33:43 192.168.122.209 [41373.721574] [tempesta fw] Tempesta FW is ready Apr 26 03:33:44 192.168.122.209 [41374.665410] [tdb] Close table 'client0.tdb' Apr 26 03:33:44 192.168.122.209 [41374.849681] [tdb] Close table 'sessions0.tdb' Apr 26 03:33:47 192.168.122.209 [41377.955257] [tdb] Close table 'cache0.tdb' Apr 26 03:33:47 192.168.122.209 [41378.202628] [tdb] Close table 'filter0.tdb' Apr 26 03:33:47 192.168.122.209 [41378.203073] [tempesta fw] modules are stopped Apr 26 03:33:48 192.168.122.209 [41378.433977] [tempesta fw] exiting... Apr 26 03:33:48 192.168.122.209 [41378.599161] [tdb] Shutdown Tempesta DB Apr 26 03:33:48 192.168.122.209 [41378.797629] End test: http2_general.test_h2_stream_priority.TestStreamPriorityInPriorityFrames.test_stream_priority_from_existing_stream Apr 26 03:33:48 192.168.122.209 [41378.825429] Start test: http2_general.test_h2_stream_priority.TestStreamPriorityInPriorityFrames.test_stream_priority_from_existing_stream_complex Apr 26 03:33:49 192.168.122.209 [41379.950653] [tdb] Start Tempesta DB Apr 26 03:33:49 192.168.122.209 [41380.107167] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:33:51 192.168.122.209 [41381.807210] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41381.807210] Maybe that's fine, but it's worth checking the [41381.807210] config - if there is no relations between the [41381.807210] names, then host name confusion attack is possible. Apr 26 03:33:51 192.168.122.209 [41381.981749] [tempesta fw] Configuration processing is completed. Apr 26 03:33:51 192.168.122.209 [41382.069135] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:33:52 192.168.122.209 [41382.491201] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:33:52 192.168.122.209 [41382.518565] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:33:52 192.168.122.209 [41382.546552] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:33:52 192.168.122.209 [41382.601744] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:33:52 192.168.122.209 [41382.641741] [tempesta fw] Tempesta FW is ready Apr 26 03:33:53 192.168.122.209 [41383.657807] [tdb] Close table 'client0.tdb' Apr 26 03:33:53 192.168.122.209 [41383.844761] [tdb] Close table 'sessions0.tdb' Apr 26 03:33:56 192.168.122.209 [41386.999937] [tdb] Close table 'cache0.tdb' Apr 26 03:33:56 192.168.122.209 [41387.218818] [tdb] Close table 'filter0.tdb' Apr 26 03:33:56 192.168.122.209 [41387.219437] [tempesta fw] modules are stopped Apr 26 03:33:57 192.168.122.209 [41387.543457] [tempesta fw] exiting... Apr 26 03:33:57 192.168.122.209 [41387.702319] [tdb] Shutdown Tempesta DB Apr 26 03:33:57 192.168.122.209 [41387.899644] End test: http2_general.test_h2_stream_priority.TestStreamPriorityInPriorityFrames.test_stream_priority_from_existing_stream_complex Apr 26 03:33:57 192.168.122.209 [41387.908774] Start test: http2_general.test_h2_stream_priority.TestStreamPriorityInPriorityFrames.test_stream_priority_from_non_existing_stream Apr 26 03:33:58 192.168.122.209 [41389.096009] [tdb] Start Tempesta DB Apr 26 03:33:58 192.168.122.209 [41389.245820] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:34:00 192.168.122.209 [41390.983276] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41390.983276] Maybe that's fine, but it's worth checking the [41390.983276] config - if there is no relations between the [41390.983276] names, then host name confusion attack is possible. Apr 26 03:34:00 192.168.122.209 [41391.141853] [tempesta fw] Configuration processing is completed. Apr 26 03:34:00 192.168.122.209 [41391.191802] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:34:01 192.168.122.209 [41391.597431] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:34:01 192.168.122.209 [41391.622646] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:34:01 192.168.122.209 [41391.647668] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:34:01 192.168.122.209 [41391.693857] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:34:01 192.168.122.209 [41391.737788] [tempesta fw] Tempesta FW is ready Apr 26 03:34:02 192.168.122.209 [41392.753438] [tdb] Close table 'client0.tdb' Apr 26 03:34:02 192.168.122.209 [41392.943565] [tdb] Close table 'sessions0.tdb' Apr 26 03:34:05 192.168.122.209 [41396.097984] [tdb] Close table 'cache0.tdb' Apr 26 03:34:06 192.168.122.209 [41396.332399] [tdb] Close table 'filter0.tdb' Apr 26 03:34:06 192.168.122.209 [41396.332829] [tempesta fw] modules are stopped Apr 26 03:34:06 192.168.122.209 [41396.552182] [tempesta fw] exiting... Apr 26 03:34:06 192.168.122.209 [41396.694136] [tdb] Shutdown Tempesta DB Apr 26 03:34:06 192.168.122.209 [41396.904398] End test: http2_general.test_h2_stream_priority.TestStreamPriorityInPriorityFrames.test_stream_priority_from_non_existing_stream Apr 26 03:34:06 192.168.122.209 [41396.923964] Start test: http2_general.test_h2_stream_priority.TestStreamPriorityTreeRebuild.test_stream_change_parent_stream_exlusive Apr 26 03:34:07 192.168.122.209 [41398.111560] [tdb] Start Tempesta DB Apr 26 03:34:07 192.168.122.209 [41398.285472] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:34:09 192.168.122.209 [41399.966776] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41399.966776] Maybe that's fine, but it's worth checking the [41399.966776] config - if there is no relations between the [41399.966776] names, then host name confusion attack is possible. Apr 26 03:34:09 192.168.122.209 [41400.133983] [tempesta fw] Configuration processing is completed. Apr 26 03:34:09 192.168.122.209 [41400.184699] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:34:10 192.168.122.209 [41400.593581] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:34:10 192.168.122.209 [41400.619336] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:34:10 192.168.122.209 [41400.644606] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:34:10 192.168.122.209 [41400.689841] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:34:10 192.168.122.209 [41400.745889] [tempesta fw] Tempesta FW is ready Apr 26 03:34:11 192.168.122.209 [41401.758849] [tdb] Close table 'client0.tdb' Apr 26 03:34:11 192.168.122.209 [41401.957090] [tdb] Close table 'sessions0.tdb' Apr 26 03:34:14 192.168.122.209 [41405.121186] [tdb] Close table 'cache0.tdb' Apr 26 03:34:15 192.168.122.209 [41405.378400] [tdb] Close table 'filter0.tdb' Apr 26 03:34:15 192.168.122.209 [41405.378829] [tempesta fw] modules are stopped Apr 26 03:34:15 192.168.122.209 [41405.635007] [tempesta fw] exiting... Apr 26 03:34:15 192.168.122.209 [41405.784972] [tdb] Shutdown Tempesta DB Apr 26 03:34:15 192.168.122.209 [41405.990850] End test: http2_general.test_h2_stream_priority.TestStreamPriorityTreeRebuild.test_stream_change_parent_stream_exlusive Apr 26 03:34:15 192.168.122.209 [41406.005603] Start test: http2_general.test_h2_stream_priority.TestStreamPriorityTreeRebuild.test_stream_change_parent_stream_exlusive_with_rebuild Apr 26 03:34:16 192.168.122.209 [41407.171997] [tdb] Start Tempesta DB Apr 26 03:34:16 192.168.122.209 [41407.324892] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:34:18 192.168.122.209 [41409.071579] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41409.071579] Maybe that's fine, but it's worth checking the [41409.071579] config - if there is no relations between the [41409.071579] names, then host name confusion attack is possible. Apr 26 03:34:18 192.168.122.209 [41409.246078] [tempesta fw] Configuration processing is completed. Apr 26 03:34:19 192.168.122.209 [41409.328923] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:34:19 192.168.122.209 [41409.734977] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:34:19 192.168.122.209 [41409.760557] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:34:19 192.168.122.209 [41409.786566] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:34:19 192.168.122.209 [41409.826056] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:34:19 192.168.122.209 [41409.877999] [tempesta fw] Tempesta FW is ready Apr 26 03:34:20 192.168.122.209 [41410.904575] [tdb] Close table 'client0.tdb' Apr 26 03:34:20 192.168.122.209 [41411.095488] [tdb] Close table 'sessions0.tdb' Apr 26 03:34:23 192.168.122.209 [41414.233388] [tdb] Close table 'cache0.tdb' Apr 26 03:34:24 192.168.122.209 [41414.466831] [tdb] Close table 'filter0.tdb' Apr 26 03:34:24 192.168.122.209 [41414.467258] [tempesta fw] modules are stopped Apr 26 03:34:24 192.168.122.209 [41414.707203] [tempesta fw] exiting... Apr 26 03:34:24 192.168.122.209 [41414.857634] [tdb] Shutdown Tempesta DB Apr 26 03:34:24 192.168.122.209 [41415.080237] End test: http2_general.test_h2_stream_priority.TestStreamPriorityTreeRebuild.test_stream_change_parent_stream_exlusive_with_rebuild Apr 26 03:34:24 192.168.122.209 [41415.091939] Start test: http2_general.test_h2_stream_priority.TestStreamPriorityTreeRebuild.test_stream_change_parent_stream_not_exlusive Apr 26 03:34:25 192.168.122.209 [41416.244307] [tdb] Start Tempesta DB Apr 26 03:34:26 192.168.122.209 [41416.385790] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:34:27 192.168.122.209 [41418.115616] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41418.115616] Maybe that's fine, but it's worth checking the [41418.115616] config - if there is no relations between the [41418.115616] names, then host name confusion attack is possible. Apr 26 03:34:27 192.168.122.209 [41418.274195] [tempesta fw] Configuration processing is completed. Apr 26 03:34:28 192.168.122.209 [41418.329169] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:34:28 192.168.122.209 [41418.744726] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:34:28 192.168.122.209 [41418.770669] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:34:28 192.168.122.209 [41418.797456] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:34:28 192.168.122.209 [41418.838183] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:34:28 192.168.122.209 [41418.878119] [tempesta fw] Tempesta FW is ready Apr 26 03:34:29 192.168.122.209 [41419.900655] [tdb] Close table 'client0.tdb' Apr 26 03:34:29 192.168.122.209 [41420.090865] [tdb] Close table 'sessions0.tdb' Apr 26 03:34:32 192.168.122.209 [41423.228349] [tdb] Close table 'cache0.tdb' Apr 26 03:34:33 192.168.122.209 [41423.482951] [tdb] Close table 'filter0.tdb' Apr 26 03:34:33 192.168.122.209 [41423.483383] [tempesta fw] modules are stopped Apr 26 03:34:33 192.168.122.209 [41423.691828] [tempesta fw] exiting... Apr 26 03:34:33 192.168.122.209 [41423.859617] [tdb] Shutdown Tempesta DB Apr 26 03:34:33 192.168.122.209 [41424.071955] End test: http2_general.test_h2_stream_priority.TestStreamPriorityTreeRebuild.test_stream_change_parent_stream_not_exlusive Apr 26 03:34:33 192.168.122.209 [41424.087763] Start test: http2_general.test_h2_stream_priority.TestStreamPriorityTreeRebuild.test_stream_change_parent_stream_not_exlusive_with_rebuild Apr 26 03:34:34 192.168.122.209 [41425.241441] [tdb] Start Tempesta DB Apr 26 03:34:35 192.168.122.209 [41425.393406] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:34:36 192.168.122.209 [41427.091784] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41427.091784] Maybe that's fine, but it's worth checking the [41427.091784] config - if there is no relations between the [41427.091784] names, then host name confusion attack is possible. Apr 26 03:34:36 192.168.122.209 [41427.250309] [tempesta fw] Configuration processing is completed. Apr 26 03:34:36 192.168.122.209 [41427.301280] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:34:37 192.168.122.209 [41427.713740] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:34:37 192.168.122.209 [41427.739680] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:34:37 192.168.122.209 [41427.765410] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:34:37 192.168.122.209 [41427.822326] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:34:37 192.168.122.209 [41427.862221] [tempesta fw] Tempesta FW is ready Apr 26 03:34:38 192.168.122.209 [41428.872360] [tdb] Close table 'client0.tdb' Apr 26 03:34:38 192.168.122.209 [41429.058428] [tdb] Close table 'sessions0.tdb' Apr 26 03:34:41 192.168.122.209 [41432.178780] [tdb] Close table 'cache0.tdb' Apr 26 03:34:42 192.168.122.209 [41432.444771] [tdb] Close table 'filter0.tdb' Apr 26 03:34:42 192.168.122.209 [41432.445204] [tempesta fw] modules are stopped Apr 26 03:34:42 192.168.122.209 [41432.663539] [tempesta fw] exiting... Apr 26 03:34:42 192.168.122.209 [41432.838897] [tdb] Shutdown Tempesta DB Apr 26 03:34:42 192.168.122.209 [41433.061988] End test: http2_general.test_h2_stream_priority.TestStreamPriorityTreeRebuild.test_stream_change_parent_stream_not_exlusive_with_rebuild Apr 26 03:34:42 192.168.122.209 [41433.086950] Start test: http2_general.test_h2_stream_states.TestClosedStreamState.test_priority_frame_in_closed_state Apr 26 03:34:43 192.168.122.209 [41434.297678] [tdb] Start Tempesta DB Apr 26 03:34:44 192.168.122.209 [41434.446238] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:34:45 192.168.122.209 [41436.015860] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41436.015860] Maybe that's fine, but it's worth checking the [41436.015860] config - if there is no relations between the [41436.015860] names, then host name confusion attack is possible. Apr 26 03:34:45 192.168.122.209 [41436.186375] [tempesta fw] Configuration processing is completed. Apr 26 03:34:45 192.168.122.209 [41436.240582] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:34:46 192.168.122.209 [41436.657514] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:34:46 192.168.122.209 [41436.683331] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:34:46 192.168.122.209 [41436.709139] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:34:46 192.168.122.209 [41436.758378] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:34:46 192.168.122.209 [41436.838335] [tempesta fw] Tempesta FW is ready Apr 26 03:34:46 192.168.122.209 [41436.984815] [tempesta fw] Warning: tfw_h2_stream_fsm, stream fully closed: stream->id=1, type=2, flags=0x0 Apr 26 03:34:47 192.168.122.209 [41437.402757] [tdb] Close table 'client0.tdb' Apr 26 03:34:47 192.168.122.209 [41437.629627] [tdb] Close table 'sessions0.tdb' Apr 26 03:34:50 192.168.122.209 [41440.741696] [tdb] Close table 'cache0.tdb' Apr 26 03:34:50 192.168.122.209 [41440.996536] [tdb] Close table 'filter0.tdb' Apr 26 03:34:50 192.168.122.209 [41440.996976] [tempesta fw] modules are stopped Apr 26 03:34:50 192.168.122.209 [41441.203694] [tempesta fw] exiting... Apr 26 03:34:51 192.168.122.209 [41441.365251] [tdb] Shutdown Tempesta DB Apr 26 03:34:51 192.168.122.209 [41441.589718] End test: http2_general.test_h2_stream_states.TestClosedStreamState.test_priority_frame_in_closed_state Apr 26 03:34:51 192.168.122.209 [41441.597513] Start test: http2_general.test_h2_stream_states.TestClosedStreamState.test_rst_stream_frame_in_closed_state Apr 26 03:34:52 192.168.122.209 [41442.788950] [tdb] Start Tempesta DB Apr 26 03:34:52 192.168.122.209 [41442.952877] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:34:54 192.168.122.209 [41444.583930] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41444.583930] Maybe that's fine, but it's worth checking the [41444.583930] config - if there is no relations between the [41444.583930] names, then host name confusion attack is possible. Apr 26 03:34:54 192.168.122.209 [41444.734492] [tempesta fw] Configuration processing is completed. Apr 26 03:34:54 192.168.122.209 [41444.785594] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:34:54 192.168.122.209 [41445.210701] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:34:54 192.168.122.209 [41445.236715] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:34:54 192.168.122.209 [41445.263317] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:34:55 192.168.122.209 [41445.338505] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:34:55 192.168.122.209 [41445.378436] [tempesta fw] Tempesta FW is ready Apr 26 03:34:55 192.168.122.209 [41445.973151] [tdb] Close table 'client0.tdb' Apr 26 03:34:55 192.168.122.209 [41446.171274] [tdb] Close table 'sessions0.tdb' Apr 26 03:34:58 192.168.122.209 [41449.284210] [tdb] Close table 'cache0.tdb' Apr 26 03:34:59 192.168.122.209 [41449.524119] [tdb] Close table 'filter0.tdb' Apr 26 03:34:59 192.168.122.209 [41449.524568] [tempesta fw] modules are stopped Apr 26 03:34:59 192.168.122.209 [41449.723545] [tempesta fw] exiting... Apr 26 03:34:59 192.168.122.209 [41449.888268] [tdb] Shutdown Tempesta DB Apr 26 03:34:59 192.168.122.209 [41450.087560] End test: http2_general.test_h2_stream_states.TestClosedStreamState.test_rst_stream_frame_in_closed_state Apr 26 03:34:59 192.168.122.209 [41450.103008] Start test: http2_general.test_h2_stream_states.TestClosedStreamState.test_window_update_frame_in_closed_state Apr 26 03:35:01 192.168.122.209 [41451.340740] [tdb] Start Tempesta DB Apr 26 03:35:01 192.168.122.209 [41451.486565] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:35:02 192.168.122.209 [41453.101179] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41453.101179] Maybe that's fine, but it's worth checking the [41453.101179] config - if there is no relations between the [41453.101179] names, then host name confusion attack is possible. Apr 26 03:35:02 192.168.122.209 [41453.274668] [tempesta fw] Configuration processing is completed. Apr 26 03:35:03 192.168.122.209 [41453.331581] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:35:03 192.168.122.209 [41453.738670] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:35:03 192.168.122.209 [41453.764485] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:35:03 192.168.122.209 [41453.789771] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:35:03 192.168.122.209 [41453.834611] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:35:03 192.168.122.209 [41453.882580] [tempesta fw] Tempesta FW is ready Apr 26 03:35:04 192.168.122.209 [41454.440650] [tdb] Close table 'client0.tdb' Apr 26 03:35:04 192.168.122.209 [41454.650909] [tdb] Close table 'sessions0.tdb' Apr 26 03:35:07 192.168.122.209 [41457.803472] [tdb] Close table 'cache0.tdb' Apr 26 03:35:07 192.168.122.209 [41458.063635] [tdb] Close table 'filter0.tdb' Apr 26 03:35:07 192.168.122.209 [41458.064068] [tempesta fw] modules are stopped Apr 26 03:35:07 192.168.122.209 [41458.287643] [tempesta fw] exiting... Apr 26 03:35:08 192.168.122.209 [41458.440532] [tdb] Shutdown Tempesta DB Apr 26 03:35:08 192.168.122.209 [41458.692584] End test: http2_general.test_h2_stream_states.TestClosedStreamState.test_window_update_frame_in_closed_state Apr 26 03:35:08 192.168.122.209 [41458.701814] Start test: http2_general.test_h2_stream_states.TestHalfClosedStreamStateUnexpectedFrames.test_priority_frame_in_half_closed_state Apr 26 03:35:09 192.168.122.209 [41459.914818] [tdb] Start Tempesta DB Apr 26 03:35:09 192.168.122.209 [41460.062683] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:35:11 192.168.122.209 [41461.644247] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41461.644247] Maybe that's fine, but it's worth checking the [41461.644247] config - if there is no relations between the [41461.644247] names, then host name confusion attack is possible. Apr 26 03:35:11 192.168.122.209 [41461.790741] [tempesta fw] Configuration processing is completed. Apr 26 03:35:11 192.168.122.209 [41461.841269] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:35:11 192.168.122.209 [41462.248618] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:35:11 192.168.122.209 [41462.274626] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:35:11 192.168.122.209 [41462.300376] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:35:12 192.168.122.209 [41462.358699] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:35:12 192.168.122.209 [41462.406648] [tempesta fw] Tempesta FW is ready Apr 26 03:35:12 192.168.122.209 [41462.555987] [tempesta fw] Warning: tfw_h2_stream_fsm, stream fully closed: stream->id=1, type=2, flags=0x0 Apr 26 03:35:12 192.168.122.209 [41463.027322] [tdb] Close table 'client0.tdb' Apr 26 03:35:12 192.168.122.209 [41463.213108] [tdb] Close table 'sessions0.tdb' Apr 26 03:35:16 192.168.122.209 [41466.408000] [tdb] Close table 'cache0.tdb' Apr 26 03:35:16 192.168.122.209 [41466.649504] [tdb] Close table 'filter0.tdb' Apr 26 03:35:16 192.168.122.209 [41466.649941] [tempesta fw] modules are stopped Apr 26 03:35:16 192.168.122.209 [41466.884021] [tempesta fw] exiting... Apr 26 03:35:16 192.168.122.209 [41467.083237] [tdb] Shutdown Tempesta DB Apr 26 03:35:17 192.168.122.209 [41467.325726] End test: http2_general.test_h2_stream_states.TestHalfClosedStreamStateUnexpectedFrames.test_priority_frame_in_half_closed_state Apr 26 03:35:17 192.168.122.209 [41467.336126] Start test: http2_general.test_h2_stream_states.TestHalfClosedStreamStateUnexpectedFrames.test_reset_frame_in_half_closed_state Apr 26 03:35:18 192.168.122.209 [41468.493868] [tdb] Start Tempesta DB Apr 26 03:35:18 192.168.122.209 [41468.643297] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:35:19 192.168.122.209 [41470.224255] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41470.224255] Maybe that's fine, but it's worth checking the [41470.224255] config - if there is no relations between the [41470.224255] names, then host name confusion attack is possible. Apr 26 03:35:20 192.168.122.209 [41470.382833] [tempesta fw] Configuration processing is completed. Apr 26 03:35:20 192.168.122.209 [41470.434157] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:35:20 192.168.122.209 [41470.849013] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:35:20 192.168.122.209 [41470.874970] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:35:20 192.168.122.209 [41470.901080] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:35:20 192.168.122.209 [41470.954831] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:35:20 192.168.122.209 [41470.994792] [tempesta fw] Tempesta FW is ready Apr 26 03:35:21 192.168.122.209 [41471.582527] [tdb] Close table 'client0.tdb' Apr 26 03:35:21 192.168.122.209 [41471.771710] [tdb] Close table 'sessions0.tdb' Apr 26 03:35:24 192.168.122.209 [41474.912068] [tdb] Close table 'cache0.tdb' Apr 26 03:35:24 192.168.122.209 [41475.138601] [tdb] Close table 'filter0.tdb' Apr 26 03:35:24 192.168.122.209 [41475.139035] [tempesta fw] modules are stopped Apr 26 03:35:25 192.168.122.209 [41475.383206] [tempesta fw] exiting... Apr 26 03:35:25 192.168.122.209 [41475.517639] [tdb] Shutdown Tempesta DB Apr 26 03:35:25 192.168.122.209 [41475.711750] End test: http2_general.test_h2_stream_states.TestHalfClosedStreamStateUnexpectedFrames.test_reset_frame_in_half_closed_state Apr 26 03:35:25 192.168.122.209 [41475.727157] Start test: http2_general.test_h2_stream_states.TestHalfClosedStreamStateUnexpectedFrames.test_window_update_frame_in_half_closed_state Apr 26 03:35:26 192.168.122.209 [41476.912737] [tdb] Start Tempesta DB Apr 26 03:35:26 192.168.122.209 [41477.063713] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:35:28 192.168.122.209 [41478.640798] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41478.640798] Maybe that's fine, but it's worth checking the [41478.640798] config - if there is no relations between the [41478.640798] names, then host name confusion attack is possible. Apr 26 03:35:28 192.168.122.209 [41478.810952] [tempesta fw] Configuration processing is completed. Apr 26 03:35:28 192.168.122.209 [41478.862454] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:35:28 192.168.122.209 [41479.288064] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:35:28 192.168.122.209 [41479.313675] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:35:29 192.168.122.209 [41479.339419] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:35:29 192.168.122.209 [41479.406886] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:35:29 192.168.122.209 [41479.462868] [tempesta fw] Tempesta FW is ready Apr 26 03:35:29 192.168.122.209 [41480.087463] [tdb] Close table 'client0.tdb' Apr 26 03:35:29 192.168.122.209 [41480.290708] [tdb] Close table 'sessions0.tdb' Apr 26 03:35:33 192.168.122.209 [41483.433001] [tdb] Close table 'cache0.tdb' Apr 26 03:35:33 192.168.122.209 [41483.673802] [tdb] Close table 'filter0.tdb' Apr 26 03:35:33 192.168.122.209 [41483.674231] [tempesta fw] modules are stopped Apr 26 03:35:33 192.168.122.209 [41483.918592] [tempesta fw] exiting... Apr 26 03:35:33 192.168.122.209 [41484.068758] [tdb] Shutdown Tempesta DB Apr 26 03:35:33 192.168.122.209 [41484.278570] End test: http2_general.test_h2_stream_states.TestHalfClosedStreamStateUnexpectedFrames.test_window_update_frame_in_half_closed_state Apr 26 03:35:33 192.168.122.209 [41484.305175] Start test: http2_general.test_h2_stream_states.TestHalfClosedStreamStateWindowUpdate.test_window_update_frame_in_half_closed_state Apr 26 03:35:35 192.168.122.209 [41485.434155] [tdb] Start Tempesta DB Apr 26 03:35:35 192.168.122.209 [41485.580352] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:35:36 192.168.122.209 [41487.200482] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41487.200482] Maybe that's fine, but it's worth checking the [41487.200482] config - if there is no relations between the [41487.200482] names, then host name confusion attack is possible. Apr 26 03:35:37 192.168.122.209 [41487.351025] [tempesta fw] Configuration processing is completed. Apr 26 03:35:37 192.168.122.209 [41487.400243] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:35:37 192.168.122.209 [41487.806681] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:35:37 192.168.122.209 [41487.831888] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:35:37 192.168.122.209 [41487.856968] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:35:37 192.168.122.209 [41487.895014] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:35:37 192.168.122.209 [41487.934975] [tempesta fw] Tempesta FW is ready Apr 26 03:35:40 192.168.122.209 [41490.517613] [tdb] Close table 'client0.tdb' Apr 26 03:35:40 192.168.122.209 [41490.703583] [tdb] Close table 'sessions0.tdb' Apr 26 03:35:43 192.168.122.209 [41493.894718] [tdb] Close table 'cache0.tdb' Apr 26 03:35:43 192.168.122.209 [41494.123726] [tdb] Close table 'filter0.tdb' Apr 26 03:35:43 192.168.122.209 [41494.124161] [tempesta fw] modules are stopped Apr 26 03:35:44 192.168.122.209 [41494.328406] [tempesta fw] exiting... Apr 26 03:35:44 192.168.122.209 [41494.442993] [tdb] Shutdown Tempesta DB Apr 26 03:35:44 192.168.122.209 [41494.683147] End test: http2_general.test_h2_stream_states.TestHalfClosedStreamStateWindowUpdate.test_window_update_frame_in_half_closed_state Apr 26 03:35:44 192.168.122.209 [41494.701409] Start test: http2_general.test_h2_stream_states.TestIdleState.test_closing_idle_stream Apr 26 03:35:45 192.168.122.209 [41495.837816] [tdb] Start Tempesta DB Apr 26 03:35:45 192.168.122.209 [41495.982136] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:35:47 192.168.122.209 [41497.592573] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41497.592573] Maybe that's fine, but it's worth checking the [41497.592573] config - if there is no relations between the [41497.592573] names, then host name confusion attack is possible. Apr 26 03:35:47 192.168.122.209 [41497.747146] [tempesta fw] Configuration processing is completed. Apr 26 03:35:47 192.168.122.209 [41497.796261] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:35:47 192.168.122.209 [41498.210562] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:35:47 192.168.122.209 [41498.236029] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:35:47 192.168.122.209 [41498.261442] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:35:47 192.168.122.209 [41498.315113] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:35:48 192.168.122.209 [41498.363112] [tempesta fw] Tempesta FW is ready Apr 26 03:35:48 192.168.122.209 [41498.982703] [tdb] Close table 'client0.tdb' Apr 26 03:35:48 192.168.122.209 [41499.173207] [tdb] Close table 'sessions0.tdb' Apr 26 03:35:52 192.168.122.209 [41502.345811] [tdb] Close table 'cache0.tdb' Apr 26 03:35:52 192.168.122.209 [41502.602664] [tdb] Close table 'filter0.tdb' Apr 26 03:35:52 192.168.122.209 [41502.603112] [tempesta fw] modules are stopped Apr 26 03:35:52 192.168.122.209 [41502.842924] [tempesta fw] exiting... Apr 26 03:35:52 192.168.122.209 [41502.996542] [tdb] Shutdown Tempesta DB Apr 26 03:35:52 192.168.122.209 [41503.225938] End test: http2_general.test_h2_stream_states.TestIdleState.test_closing_idle_stream Apr 26 03:35:52 192.168.122.209 [41503.247773] Start test: http2_general.test_h2_stream_states.TestIdleState.test_not_closing_idle_stream Apr 26 03:35:54 192.168.122.209 [41504.461090] [tdb] Start Tempesta DB Apr 26 03:35:54 192.168.122.209 [41504.596936] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:35:55 192.168.122.209 [41506.220685] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41506.220685] Maybe that's fine, but it's worth checking the [41506.220685] config - if there is no relations between the [41506.220685] names, then host name confusion attack is possible. Apr 26 03:35:56 192.168.122.209 [41506.383556] [tempesta fw] Configuration processing is completed. Apr 26 03:35:56 192.168.122.209 [41506.465371] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:35:56 192.168.122.209 [41506.877354] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:35:56 192.168.122.209 [41506.904285] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:35:56 192.168.122.209 [41506.932072] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:35:56 192.168.122.209 [41506.983259] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:35:56 192.168.122.209 [41507.027195] [tempesta fw] Tempesta FW is ready Apr 26 03:35:57 192.168.122.209 [41507.689250] [tdb] Close table 'client0.tdb' Apr 26 03:35:57 192.168.122.209 [41507.868613] [tdb] Close table 'sessions0.tdb' Apr 26 03:36:00 192.168.122.209 [41511.043760] [tdb] Close table 'cache0.tdb' Apr 26 03:36:00 192.168.122.209 [41511.278953] [tdb] Close table 'filter0.tdb' Apr 26 03:36:00 192.168.122.209 [41511.279418] [tempesta fw] modules are stopped Apr 26 03:36:01 192.168.122.209 [41511.538939] [tempesta fw] exiting... Apr 26 03:36:01 192.168.122.209 [41511.689831] [tdb] Shutdown Tempesta DB Apr 26 03:36:01 192.168.122.209 [41511.907086] End test: http2_general.test_h2_stream_states.TestIdleState.test_not_closing_idle_stream Apr 26 03:36:01 192.168.122.209 [41511.932606] Start test: http2_general.test_h2_stream_states.TestIdleState.test_priority_frame_in_idle_state Apr 26 03:36:02 192.168.122.209 [41513.080892] [tdb] Start Tempesta DB Apr 26 03:36:02 192.168.122.209 [41513.227878] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:36:04 192.168.122.209 [41514.836794] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41514.836794] Maybe that's fine, but it's worth checking the [41514.836794] config - if there is no relations between the [41514.836794] names, then host name confusion attack is possible. Apr 26 03:36:04 192.168.122.209 [41514.995376] [tempesta fw] Configuration processing is completed. Apr 26 03:36:04 192.168.122.209 [41515.046263] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:36:05 192.168.122.209 [41515.457880] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:36:05 192.168.122.209 [41515.493112] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:36:05 192.168.122.209 [41515.518947] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:36:05 192.168.122.209 [41515.571376] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:36:05 192.168.122.209 [41515.619300] [tempesta fw] Tempesta FW is ready Apr 26 03:36:05 192.168.122.209 [41516.226421] [tdb] Close table 'client0.tdb' Apr 26 03:36:06 192.168.122.209 [41516.431249] [tdb] Close table 'sessions0.tdb' Apr 26 03:36:09 192.168.122.209 [41519.552257] [tdb] Close table 'cache0.tdb' Apr 26 03:36:09 192.168.122.209 [41519.792815] [tdb] Close table 'filter0.tdb' Apr 26 03:36:09 192.168.122.209 [41519.793241] [tempesta fw] modules are stopped Apr 26 03:36:09 192.168.122.209 [41520.044362] [tempesta fw] exiting... Apr 26 03:36:09 192.168.122.209 [41520.202175] [tdb] Shutdown Tempesta DB Apr 26 03:36:10 192.168.122.209 [41520.402248] End test: http2_general.test_h2_stream_states.TestIdleState.test_priority_frame_in_idle_state Apr 26 03:36:10 192.168.122.209 [41520.410795] Start test: http2_general.test_h2_stream_states.TestIdleState.test_rst_frame_for_idle_stream Apr 26 03:36:11 192.168.122.209 [41521.585292] [tdb] Start Tempesta DB Apr 26 03:36:11 192.168.122.209 [41521.741489] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:36:13 192.168.122.209 [41523.400936] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41523.400936] Maybe that's fine, but it's worth checking the [41523.400936] config - if there is no relations between the [41523.400936] names, then host name confusion attack is possible. Apr 26 03:36:13 192.168.122.209 [41523.555486] [tempesta fw] Configuration processing is completed. Apr 26 03:36:13 192.168.122.209 [41523.613967] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:36:13 192.168.122.209 [41524.027639] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:36:13 192.168.122.209 [41524.053349] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:36:13 192.168.122.209 [41524.079507] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:36:13 192.168.122.209 [41524.123468] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:36:13 192.168.122.209 [41524.163368] [tempesta fw] Tempesta FW is ready Apr 26 03:36:19 192.168.122.209 [41529.763770] [tdb] Close table 'client0.tdb' Apr 26 03:36:19 192.168.122.209 [41529.953996] [tdb] Close table 'sessions0.tdb' Apr 26 03:36:22 192.168.122.209 [41533.066932] [tdb] Close table 'cache0.tdb' Apr 26 03:36:22 192.168.122.209 [41533.295181] [tdb] Close table 'filter0.tdb' Apr 26 03:36:22 192.168.122.209 [41533.295638] [tempesta fw] modules are stopped Apr 26 03:36:23 192.168.122.209 [41533.545339] [tempesta fw] exiting... Apr 26 03:36:23 192.168.122.209 [41533.707165] [tdb] Shutdown Tempesta DB Apr 26 03:36:23 192.168.122.209 [41533.918863] End test: http2_general.test_h2_stream_states.TestIdleState.test_rst_frame_for_idle_stream Apr 26 03:36:23 192.168.122.209 [41533.926827] Start test: http2_general.test_h2_stream_states.TestLocHalfClosedStreamState.test_headers Apr 26 03:36:24 192.168.122.209 [41535.199475] [tdb] Start Tempesta DB Apr 26 03:36:25 192.168.122.209 [41535.351242] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:36:26 192.168.122.209 [41536.930749] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41536.930749] Maybe that's fine, but it's worth checking the [41536.930749] config - if there is no relations between the [41536.930749] names, then host name confusion attack is possible. Apr 26 03:36:26 192.168.122.209 [41537.075650] [tempesta fw] Configuration processing is completed. Apr 26 03:36:26 192.168.122.209 [41537.160105] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:36:27 192.168.122.209 [41537.577308] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:36:27 192.168.122.209 [41537.603989] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:36:27 192.168.122.209 [41537.631242] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:36:27 192.168.122.209 [41537.683645] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:36:27 192.168.122.209 [41537.723575] [tempesta fw] Tempesta FW is ready Apr 26 03:36:30 192.168.122.209 [41540.622451] [tdb] Close table 'client0.tdb' Apr 26 03:36:30 192.168.122.209 [41540.819536] [tdb] Close table 'sessions0.tdb' Apr 26 03:36:33 192.168.122.209 [41543.993637] [tdb] Close table 'cache0.tdb' Apr 26 03:36:33 192.168.122.209 [41544.212770] [tdb] Close table 'filter0.tdb' Apr 26 03:36:33 192.168.122.209 [41544.213201] [tempesta fw] modules are stopped Apr 26 03:36:34 192.168.122.209 [41544.476665] [tempesta fw] exiting... Apr 26 03:36:34 192.168.122.209 [41544.633026] [tdb] Shutdown Tempesta DB Apr 26 03:36:34 192.168.122.209 [41544.842740] End test: http2_general.test_h2_stream_states.TestLocHalfClosedStreamState.test_headers Apr 26 03:36:34 192.168.122.209 [41544.852402] Start test: http2_general.test_h2_stream_states.TestStreamStateCont.test_any_frame_between_header_blocks Apr 26 03:36:35 192.168.122.209 [41545.997436] [tdb] Start Tempesta DB Apr 26 03:36:35 192.168.122.209 [41546.140342] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:36:37 192.168.122.209 [41547.690194] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41547.690194] Maybe that's fine, but it's worth checking the [41547.690194] config - if there is no relations between the [41547.690194] names, then host name confusion attack is possible. Apr 26 03:36:37 192.168.122.209 [41547.851761] [tempesta fw] Configuration processing is completed. Apr 26 03:36:37 192.168.122.209 [41547.906838] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:36:37 192.168.122.209 [41548.314459] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:36:38 192.168.122.209 [41548.340480] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:36:38 192.168.122.209 [41548.365906] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:36:38 192.168.122.209 [41548.411811] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:36:38 192.168.122.209 [41548.451671] [tempesta fw] Tempesta FW is ready Apr 26 03:36:38 192.168.122.209 [41549.017719] [tdb] Close table 'client0.tdb' Apr 26 03:36:38 192.168.122.209 [41549.219492] [tdb] Close table 'sessions0.tdb' Apr 26 03:36:42 192.168.122.209 [41552.351663] [tdb] Close table 'cache0.tdb' Apr 26 03:36:42 192.168.122.209 [41552.602717] [tdb] Close table 'filter0.tdb' Apr 26 03:36:42 192.168.122.209 [41552.603151] [tempesta fw] modules are stopped Apr 26 03:36:42 192.168.122.209 [41552.799580] [tempesta fw] exiting... Apr 26 03:36:42 192.168.122.209 [41552.938648] [tdb] Shutdown Tempesta DB Apr 26 03:36:42 192.168.122.209 [41553.171274] End test: http2_general.test_h2_stream_states.TestStreamStateCont.test_any_frame_between_header_blocks Apr 26 03:36:42 192.168.122.209 [41553.191576] Start test: http2_general.test_h2_stream_states.TestStreamStateCont.test_error_request_between_header_blocks Apr 26 03:36:44 192.168.122.209 [41554.386169] [tdb] Start Tempesta DB Apr 26 03:36:44 192.168.122.209 [41554.551929] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:36:45 192.168.122.209 [41556.125287] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41556.125287] Maybe that's fine, but it's worth checking the [41556.125287] config - if there is no relations between the [41556.125287] names, then host name confusion attack is possible. Apr 26 03:36:45 192.168.122.209 [41556.287881] [tempesta fw] Configuration processing is completed. Apr 26 03:36:46 192.168.122.209 [41556.339171] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:36:46 192.168.122.209 [41556.764305] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:36:46 192.168.122.209 [41556.789777] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:36:46 192.168.122.209 [41556.815242] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:36:46 192.168.122.209 [41556.859866] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:36:46 192.168.122.209 [41556.899917] [tempesta fw] Tempesta FW is ready Apr 26 03:36:46 192.168.122.209 [41557.056698] [tempesta fw] Warning: HTTP/2 request dropped: state=RGen_HdrOtherN input=0x42('BAD'), len=3, off=0 Apr 26 03:36:47 192.168.122.209 [41557.530867] [tdb] Close table 'client0.tdb' Apr 26 03:36:47 192.168.122.209 [41557.742790] [tdb] Close table 'sessions0.tdb' Apr 26 03:36:50 192.168.122.209 [41560.848877] [tdb] Close table 'cache0.tdb' Apr 26 03:36:50 192.168.122.209 [41561.089778] [tdb] Close table 'filter0.tdb' Apr 26 03:36:50 192.168.122.209 [41561.090210] [tempesta fw] modules are stopped Apr 26 03:36:50 192.168.122.209 [41561.291502] [tempesta fw] exiting... Apr 26 03:36:51 192.168.122.209 [41561.436306] [tdb] Shutdown Tempesta DB Apr 26 03:36:51 192.168.122.209 [41561.639304] End test: http2_general.test_h2_stream_states.TestStreamStateCont.test_error_request_between_header_blocks Apr 26 03:36:51 192.168.122.209 [41561.651152] Start test: http2_general.test_h2_stream_states.TestStreamStateCont.test_headers_frame_for_other_stream_after_rst Apr 26 03:36:52 192.168.122.209 [41562.846547] [tdb] Start Tempesta DB Apr 26 03:36:52 192.168.122.209 [41562.991074] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:36:54 192.168.122.209 [41564.645171] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41564.645171] Maybe that's fine, but it's worth checking the [41564.645171] config - if there is no relations between the [41564.645171] names, then host name confusion attack is possible. Apr 26 03:36:54 192.168.122.209 [41564.800004] [tempesta fw] Configuration processing is completed. Apr 26 03:36:54 192.168.122.209 [41564.896189] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:36:54 192.168.122.209 [41565.314950] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:36:55 192.168.122.209 [41565.341783] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:36:55 192.168.122.209 [41565.367483] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:36:55 192.168.122.209 [41565.427973] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:36:55 192.168.122.209 [41565.467934] [tempesta fw] Tempesta FW is ready Apr 26 03:36:55 192.168.122.209 [41566.077500] [tdb] Close table 'client0.tdb' Apr 26 03:36:55 192.168.122.209 [41566.268151] [tdb] Close table 'sessions0.tdb' Apr 26 03:36:59 192.168.122.209 [41569.418812] [tdb] Close table 'cache0.tdb' Apr 26 03:36:59 192.168.122.209 [41569.676617] [tdb] Close table 'filter0.tdb' Apr 26 03:36:59 192.168.122.209 [41569.677047] [tempesta fw] modules are stopped Apr 26 03:36:59 192.168.122.209 [41569.995535] [tempesta fw] exiting... Apr 26 03:36:59 192.168.122.209 [41570.161401] [tdb] Shutdown Tempesta DB Apr 26 03:37:00 192.168.122.209 [41570.394681] End test: http2_general.test_h2_stream_states.TestStreamStateCont.test_headers_frame_for_other_stream_after_rst Apr 26 03:37:00 192.168.122.209 [41570.405424] Start test: http2_general.test_h2_stream_states.TestStreamStateCont.test_headers_frame_for_other_stream_between_header_blocks Apr 26 03:37:01 192.168.122.209 [41571.592031] [tdb] Start Tempesta DB Apr 26 03:37:01 192.168.122.209 [41571.738541] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:37:03 192.168.122.209 [41573.349542] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41573.349542] Maybe that's fine, but it's worth checking the [41573.349542] config - if there is no relations between the [41573.349542] names, then host name confusion attack is possible. Apr 26 03:37:03 192.168.122.209 [41573.496101] [tempesta fw] Configuration processing is completed. Apr 26 03:37:03 192.168.122.209 [41573.547723] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:37:03 192.168.122.209 [41573.952648] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:37:03 192.168.122.209 [41573.978149] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:37:03 192.168.122.209 [41574.003201] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:37:03 192.168.122.209 [41574.060077] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:37:03 192.168.122.209 [41574.112028] [tempesta fw] Tempesta FW is ready Apr 26 03:37:04 192.168.122.209 [41574.734859] [tdb] Close table 'client0.tdb' Apr 26 03:37:04 192.168.122.209 [41574.935344] [tdb] Close table 'sessions0.tdb' Apr 26 03:37:07 192.168.122.209 [41578.076698] [tdb] Close table 'cache0.tdb' Apr 26 03:37:08 192.168.122.209 [41578.331816] [tdb] Close table 'filter0.tdb' Apr 26 03:37:08 192.168.122.209 [41578.332265] [tempesta fw] modules are stopped Apr 26 03:37:08 192.168.122.209 [41578.587727] [tempesta fw] exiting... Apr 26 03:37:08 192.168.122.209 [41578.761272] [tdb] Shutdown Tempesta DB Apr 26 03:37:08 192.168.122.209 [41578.986815] End test: http2_general.test_h2_stream_states.TestStreamStateCont.test_headers_frame_for_other_stream_between_header_blocks Apr 26 03:37:08 192.168.122.209 [41579.000587] Start test: http2_general.test_h2_stream_states.TestStreamStateContClosed.test_any_frame_between_header_blocks Apr 26 03:37:09 192.168.122.209 [41580.168083] [tdb] Start Tempesta DB Apr 26 03:37:09 192.168.122.209 [41580.309855] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:37:11 192.168.122.209 [41581.893609] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41581.893609] Maybe that's fine, but it's worth checking the [41581.893609] config - if there is no relations between the [41581.893609] names, then host name confusion attack is possible. Apr 26 03:37:11 192.168.122.209 [41582.052219] [tempesta fw] Configuration processing is completed. Apr 26 03:37:11 192.168.122.209 [41582.103143] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:37:12 192.168.122.209 [41582.510390] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:37:12 192.168.122.209 [41582.536163] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:37:12 192.168.122.209 [41582.561998] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:37:12 192.168.122.209 [41582.612194] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:37:12 192.168.122.209 [41582.660130] [tempesta fw] Tempesta FW is ready Apr 26 03:37:12 192.168.122.209 [41583.309043] [tdb] Close table 'client0.tdb' Apr 26 03:37:13 192.168.122.209 [41583.509698] [tdb] Close table 'sessions0.tdb' Apr 26 03:37:16 192.168.122.209 [41586.619317] [tdb] Close table 'cache0.tdb' Apr 26 03:37:16 192.168.122.209 [41586.879667] [tdb] Close table 'filter0.tdb' Apr 26 03:37:16 192.168.122.209 [41586.880118] [tempesta fw] modules are stopped Apr 26 03:37:16 192.168.122.209 [41587.139404] [tempesta fw] exiting... Apr 26 03:37:16 192.168.122.209 [41587.301916] [tdb] Shutdown Tempesta DB Apr 26 03:37:17 192.168.122.209 [41587.530494] End test: http2_general.test_h2_stream_states.TestStreamStateContClosed.test_any_frame_between_header_blocks Apr 26 03:37:17 192.168.122.209 [41587.544088] Start test: http2_general.test_h2_stream_states.TestStreamStateContClosed.test_error_request_between_header_blocks Apr 26 03:37:18 192.168.122.209 [41588.727742] [tdb] Start Tempesta DB Apr 26 03:37:18 192.168.122.209 [41588.872611] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:37:20 192.168.122.209 [41590.517704] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41590.517704] Maybe that's fine, but it's worth checking the [41590.517704] config - if there is no relations between the [41590.517704] names, then host name confusion attack is possible. Apr 26 03:37:20 192.168.122.209 [41590.684310] [tempesta fw] Configuration processing is completed. Apr 26 03:37:20 192.168.122.209 [41590.735683] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:37:20 192.168.122.209 [41591.157932] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:37:20 192.168.122.209 [41591.187781] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:37:20 192.168.122.209 [41591.217558] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:37:20 192.168.122.209 [41591.268303] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:37:20 192.168.122.209 [41591.308259] [tempesta fw] Tempesta FW is ready Apr 26 03:37:21 192.168.122.209 [41591.468512] [tempesta fw] Warning: HTTP/2 request dropped: state=RGen_HdrOtherN input=0x42('BAD'), len=3, off=0 Apr 26 03:37:21 192.168.122.209 [41591.906003] [tdb] Close table 'client0.tdb' Apr 26 03:37:21 192.168.122.209 [41592.119322] [tdb] Close table 'sessions0.tdb' Apr 26 03:37:24 192.168.122.209 [41595.324009] [tdb] Close table 'cache0.tdb' Apr 26 03:37:25 192.168.122.209 [41595.588100] [tdb] Close table 'filter0.tdb' Apr 26 03:37:25 192.168.122.209 [41595.588557] [tempesta fw] modules are stopped Apr 26 03:37:25 192.168.122.209 [41595.808830] [tempesta fw] exiting... Apr 26 03:37:25 192.168.122.209 [41595.942147] [tdb] Shutdown Tempesta DB Apr 26 03:37:25 192.168.122.209 [41596.133428] End test: http2_general.test_h2_stream_states.TestStreamStateContClosed.test_error_request_between_header_blocks Apr 26 03:37:25 192.168.122.209 [41596.144074] Start test: http2_general.test_h2_stream_states.TestStreamStateContClosed.test_headers_frame_for_other_stream_after_rst Apr 26 03:37:27 192.168.122.209 [41597.344691] [tdb] Start Tempesta DB Apr 26 03:37:27 192.168.122.209 [41597.487145] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:37:28 192.168.122.209 [41599.109821] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41599.109821] Maybe that's fine, but it's worth checking the [41599.109821] config - if there is no relations between the [41599.109821] names, then host name confusion attack is possible. Apr 26 03:37:28 192.168.122.209 [41599.272428] [tempesta fw] Configuration processing is completed. Apr 26 03:37:28 192.168.122.209 [41599.327081] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:37:29 192.168.122.209 [41599.740689] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:37:29 192.168.122.209 [41599.766990] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:37:29 192.168.122.209 [41599.793583] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:37:29 192.168.122.209 [41599.840402] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:37:29 192.168.122.209 [41599.880357] [tempesta fw] Tempesta FW is ready Apr 26 03:37:30 192.168.122.209 [41600.502447] [tdb] Close table 'client0.tdb' Apr 26 03:37:30 192.168.122.209 [41600.713880] [tdb] Close table 'sessions0.tdb' Apr 26 03:37:33 192.168.122.209 [41603.961584] [tdb] Close table 'cache0.tdb' Apr 26 03:37:33 192.168.122.209 [41604.207271] [tdb] Close table 'filter0.tdb' Apr 26 03:37:33 192.168.122.209 [41604.207741] [tempesta fw] modules are stopped Apr 26 03:37:34 192.168.122.209 [41604.442192] [tempesta fw] exiting... Apr 26 03:37:34 192.168.122.209 [41604.610111] [tdb] Shutdown Tempesta DB Apr 26 03:37:34 192.168.122.209 [41604.823795] End test: http2_general.test_h2_stream_states.TestStreamStateContClosed.test_headers_frame_for_other_stream_after_rst Apr 26 03:37:34 192.168.122.209 [41604.835990] Start test: http2_general.test_h2_stream_states.TestStreamStateContClosed.test_headers_frame_for_other_stream_between_header_blocks Apr 26 03:37:35 192.168.122.209 [41605.981231] [tdb] Start Tempesta DB Apr 26 03:37:35 192.168.122.209 [41606.139305] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:37:37 192.168.122.209 [41607.814172] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41607.814172] Maybe that's fine, but it's worth checking the [41607.814172] config - if there is no relations between the [41607.814172] names, then host name confusion attack is possible. Apr 26 03:37:37 192.168.122.209 [41607.964578] [tempesta fw] Configuration processing is completed. Apr 26 03:37:37 192.168.122.209 [41608.025753] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:37:38 192.168.122.209 [41608.491022] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:37:38 192.168.122.209 [41608.520251] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:37:38 192.168.122.209 [41608.559882] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:37:38 192.168.122.209 [41608.636506] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:37:38 192.168.122.209 [41608.684476] [tempesta fw] Tempesta FW is ready Apr 26 03:37:38 192.168.122.209 [41609.274948] [tdb] Close table 'client0.tdb' Apr 26 03:37:39 192.168.122.209 [41609.470918] [tdb] Close table 'sessions0.tdb' Apr 26 03:37:42 192.168.122.209 [41612.623076] [tdb] Close table 'cache0.tdb' Apr 26 03:37:42 192.168.122.209 [41612.883023] [tdb] Close table 'filter0.tdb' Apr 26 03:37:42 192.168.122.209 [41612.883481] [tempesta fw] modules are stopped Apr 26 03:37:42 192.168.122.209 [41613.111222] [tempesta fw] exiting... Apr 26 03:37:42 192.168.122.209 [41613.287288] [tdb] Shutdown Tempesta DB Apr 26 03:37:43 192.168.122.209 [41613.508162] End test: http2_general.test_h2_stream_states.TestStreamStateContClosed.test_headers_frame_for_other_stream_between_header_blocks Apr 26 03:37:43 192.168.122.209 [41613.524899] Start test: http2_general.test_h2_stream_states.TestTwoHeadersFramesFirstWithoutEndStream.test Apr 26 03:37:44 192.168.122.209 [41614.711083] [tdb] Start Tempesta DB Apr 26 03:37:44 192.168.122.209 [41614.862912] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:37:46 192.168.122.209 [41616.434118] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41616.434118] Maybe that's fine, but it's worth checking the [41616.434118] config - if there is no relations between the [41616.434118] names, then host name confusion attack is possible. Apr 26 03:37:46 192.168.122.209 [41616.596946] [tempesta fw] Configuration processing is completed. Apr 26 03:37:46 192.168.122.209 [41616.648377] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:37:46 192.168.122.209 [41617.070616] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:37:46 192.168.122.209 [41617.096935] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:37:46 192.168.122.209 [41617.123242] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:37:46 192.168.122.209 [41617.168642] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:37:46 192.168.122.209 [41617.208556] [tempesta fw] Tempesta FW is ready Apr 26 03:37:47 192.168.122.209 [41617.832006] [tdb] Close table 'client0.tdb' Apr 26 03:37:47 192.168.122.209 [41618.031907] [tdb] Close table 'sessions0.tdb' Apr 26 03:37:50 192.168.122.209 [41621.221400] [tdb] Close table 'cache0.tdb' Apr 26 03:37:51 192.168.122.209 [41621.451286] [tdb] Close table 'filter0.tdb' Apr 26 03:37:51 192.168.122.209 [41621.451715] [tempesta fw] modules are stopped Apr 26 03:37:51 192.168.122.209 [41621.672390] [tempesta fw] exiting... Apr 26 03:37:51 192.168.122.209 [41621.857066] [tdb] Shutdown Tempesta DB Apr 26 03:37:51 192.168.122.209 [41622.086629] End test: http2_general.test_h2_stream_states.TestTwoHeadersFramesFirstWithoutEndStream.test Apr 26 03:37:51 192.168.122.209 [41622.098624] Start test: http2_general.test_h2_streams.TestH2Stream.test_headers_frame_with_zero_stream_id Apr 26 03:37:52 192.168.122.209 [41623.295619] [tdb] Start Tempesta DB Apr 26 03:37:53 192.168.122.209 [41623.446182] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:37:54 192.168.122.209 [41625.062168] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41625.062168] Maybe that's fine, but it's worth checking the [41625.062168] config - if there is no relations between the [41625.062168] names, then host name confusion attack is possible. Apr 26 03:37:54 192.168.122.209 [41625.224730] [tempesta fw] Configuration processing is completed. Apr 26 03:37:54 192.168.122.209 [41625.309620] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:37:55 192.168.122.209 [41625.803257] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:37:55 192.168.122.209 [41625.833116] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:37:55 192.168.122.209 [41625.865177] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:37:55 192.168.122.209 [41625.916757] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:37:55 192.168.122.209 [41625.956678] [tempesta fw] Tempesta FW is ready Apr 26 03:37:56 192.168.122.209 [41626.552222] [tdb] Close table 'client0.tdb' Apr 26 03:37:56 192.168.122.209 [41626.758756] [tdb] Close table 'sessions0.tdb' Apr 26 03:37:59 192.168.122.209 [41629.901791] [tdb] Close table 'cache0.tdb' Apr 26 03:37:59 192.168.122.209 [41630.154864] [tdb] Close table 'filter0.tdb' Apr 26 03:37:59 192.168.122.209 [41630.155297] [tempesta fw] modules are stopped Apr 26 03:38:00 192.168.122.209 [41630.409983] [tempesta fw] exiting... Apr 26 03:38:00 192.168.122.209 [41630.540542] [tdb] Shutdown Tempesta DB Apr 26 03:38:00 192.168.122.209 [41630.739656] End test: http2_general.test_h2_streams.TestH2Stream.test_headers_frame_with_zero_stream_id Apr 26 03:38:00 192.168.122.209 [41630.760101] Start test: http2_general.test_h2_streams.TestH2Stream.test_max_concurrent_stream Apr 26 03:38:01 192.168.122.209 [41631.966859] [tdb] Start Tempesta DB Apr 26 03:38:01 192.168.122.209 [41632.118319] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:38:03 192.168.122.209 [41633.706271] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41633.706271] Maybe that's fine, but it's worth checking the [41633.706271] config - if there is no relations between the [41633.706271] names, then host name confusion attack is possible. Apr 26 03:38:03 192.168.122.209 [41633.872838] [tempesta fw] Configuration processing is completed. Apr 26 03:38:03 192.168.122.209 [41633.933567] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:38:04 192.168.122.209 [41634.344239] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:38:04 192.168.122.209 [41634.369805] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:38:04 192.168.122.209 [41634.396760] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:38:04 192.168.122.209 [41634.436845] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:38:04 192.168.122.209 [41634.476789] [tempesta fw] Tempesta FW is ready Apr 26 03:38:04 192.168.122.209 [41635.053922] [tdb] Close table 'client0.tdb' Apr 26 03:38:04 192.168.122.209 [41635.240901] [tdb] Close table 'sessions0.tdb' Apr 26 03:38:08 192.168.122.209 [41638.380591] [tdb] Close table 'cache0.tdb' Apr 26 03:38:08 192.168.122.209 [41638.617877] [tdb] Close table 'filter0.tdb' Apr 26 03:38:08 192.168.122.209 [41638.618325] [tempesta fw] modules are stopped Apr 26 03:38:08 192.168.122.209 [41638.867872] [tempesta fw] exiting... Apr 26 03:38:08 192.168.122.209 [41639.015579] [tdb] Shutdown Tempesta DB Apr 26 03:38:08 192.168.122.209 [41639.250555] End test: http2_general.test_h2_streams.TestH2Stream.test_max_concurrent_stream Apr 26 03:38:08 192.168.122.209 [41639.266920] Start test: http2_general.test_h2_streams.TestH2Stream.test_max_concurrent_stream_not_exceeded Apr 26 03:38:10 192.168.122.209 [41640.411397] [tdb] Start Tempesta DB Apr 26 03:38:10 192.168.122.209 [41640.555691] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:38:11 192.168.122.209 [41642.158383] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41642.158383] Maybe that's fine, but it's worth checking the [41642.158383] config - if there is no relations between the [41642.158383] names, then host name confusion attack is possible. Apr 26 03:38:11 192.168.122.209 [41642.320961] [tempesta fw] Configuration processing is completed. Apr 26 03:38:12 192.168.122.209 [41642.379895] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:38:12 192.168.122.209 [41642.792761] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:38:12 192.168.122.209 [41642.818144] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:38:12 192.168.122.209 [41642.843215] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:38:12 192.168.122.209 [41642.892934] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:38:12 192.168.122.209 [41642.936872] [tempesta fw] Tempesta FW is ready Apr 26 03:38:13 192.168.122.209 [41643.576057] [tdb] Close table 'client0.tdb' Apr 26 03:38:13 192.168.122.209 [41643.777809] [tdb] Close table 'sessions0.tdb' Apr 26 03:38:16 192.168.122.209 [41646.968107] [tdb] Close table 'cache0.tdb' Apr 26 03:38:16 192.168.122.209 [41647.238824] [tdb] Close table 'filter0.tdb' Apr 26 03:38:16 192.168.122.209 [41647.239279] [tempesta fw] modules are stopped Apr 26 03:38:17 192.168.122.209 [41647.507589] [tempesta fw] exiting... Apr 26 03:38:17 192.168.122.209 [41647.666864] [tdb] Shutdown Tempesta DB Apr 26 03:38:17 192.168.122.209 [41647.916096] End test: http2_general.test_h2_streams.TestH2Stream.test_max_concurrent_stream_not_exceeded Apr 26 03:38:17 192.168.122.209 [41647.930561] Start test: http2_general.test_h2_streams.TestH2Stream.test_request_with_even_numbered_stream_id Apr 26 03:38:18 192.168.122.209 [41649.108163] [tdb] Start Tempesta DB Apr 26 03:38:18 192.168.122.209 [41649.263394] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:38:20 192.168.122.209 [41650.806498] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41650.806498] Maybe that's fine, but it's worth checking the [41650.806498] config - if there is no relations between the [41650.806498] names, then host name confusion attack is possible. Apr 26 03:38:20 192.168.122.209 [41650.965063] [tempesta fw] Configuration processing is completed. Apr 26 03:38:20 192.168.122.209 [41651.048076] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:38:21 192.168.122.209 [41651.475696] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:38:21 192.168.122.209 [41651.501610] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:38:21 192.168.122.209 [41651.527676] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:38:21 192.168.122.209 [41651.585035] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:38:21 192.168.122.209 [41651.629001] [tempesta fw] Tempesta FW is ready Apr 26 03:38:21 192.168.122.209 [41652.215824] [tdb] Close table 'client0.tdb' Apr 26 03:38:22 192.168.122.209 [41652.411194] [tdb] Close table 'sessions0.tdb' Apr 26 03:38:25 192.168.122.209 [41655.545705] [tdb] Close table 'cache0.tdb' Apr 26 03:38:25 192.168.122.209 [41655.797588] [tdb] Close table 'filter0.tdb' Apr 26 03:38:25 192.168.122.209 [41655.798043] [tempesta fw] modules are stopped Apr 26 03:38:25 192.168.122.209 [41656.057669] [tempesta fw] exiting... Apr 26 03:38:25 192.168.122.209 [41656.221426] [tdb] Shutdown Tempesta DB Apr 26 03:38:26 192.168.122.209 [41656.442013] End test: http2_general.test_h2_streams.TestH2Stream.test_request_with_even_numbered_stream_id Apr 26 03:38:26 192.168.122.209 [41656.462516] Start test: http2_general.test_h2_streams.TestH2Stream.test_request_with_large_stream_id Apr 26 03:38:27 192.168.122.209 [41657.642401] [tdb] Start Tempesta DB Apr 26 03:38:27 192.168.122.209 [41657.792569] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:38:29 192.168.122.209 [41659.410572] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41659.410572] Maybe that's fine, but it's worth checking the [41659.410572] config - if there is no relations between the [41659.410572] names, then host name confusion attack is possible. Apr 26 03:38:29 192.168.122.209 [41659.605178] [tempesta fw] Configuration processing is completed. Apr 26 03:38:29 192.168.122.209 [41659.663441] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:38:29 192.168.122.209 [41660.148024] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:38:29 192.168.122.209 [41660.180559] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:38:29 192.168.122.209 [41660.213033] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:38:29 192.168.122.209 [41660.253172] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:38:29 192.168.122.209 [41660.293091] [tempesta fw] Tempesta FW is ready Apr 26 03:38:30 192.168.122.209 [41660.898148] [tdb] Close table 'client0.tdb' Apr 26 03:38:30 192.168.122.209 [41661.110712] [tdb] Close table 'sessions0.tdb' Apr 26 03:38:33 192.168.122.209 [41664.286033] [tdb] Close table 'cache0.tdb' Apr 26 03:38:34 192.168.122.209 [41664.543426] [tdb] Close table 'filter0.tdb' Apr 26 03:38:34 192.168.122.209 [41664.543871] [tempesta fw] modules are stopped Apr 26 03:38:34 192.168.122.209 [41664.779810] [tempesta fw] exiting... Apr 26 03:38:34 192.168.122.209 [41664.964626] [tdb] Shutdown Tempesta DB Apr 26 03:38:34 192.168.122.209 [41665.179223] End test: http2_general.test_h2_streams.TestH2Stream.test_request_with_large_stream_id Apr 26 03:38:34 192.168.122.209 [41665.196478] Start test: http2_general.test_h2_streams.TestH2Stream.test_reuse_stream_id Apr 26 03:38:36 192.168.122.209 [41666.403352] [tdb] Start Tempesta DB Apr 26 03:38:36 192.168.122.209 [41666.545841] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:38:37 192.168.122.209 [41668.166711] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41668.166711] Maybe that's fine, but it's worth checking the [41668.166711] config - if there is no relations between the [41668.166711] names, then host name confusion attack is possible. Apr 26 03:38:37 192.168.122.209 [41668.313261] [tempesta fw] Configuration processing is completed. Apr 26 03:38:38 192.168.122.209 [41668.373764] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:38:38 192.168.122.209 [41668.790724] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:38:38 192.168.122.209 [41668.816672] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:38:38 192.168.122.209 [41668.842999] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:38:38 192.168.122.209 [41668.897263] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:38:38 192.168.122.209 [41668.953221] [tempesta fw] Tempesta FW is ready Apr 26 03:38:39 192.168.122.209 [41669.540820] [tdb] Close table 'client0.tdb' Apr 26 03:38:39 192.168.122.209 [41669.740739] [tdb] Close table 'sessions0.tdb' Apr 26 03:38:42 192.168.122.209 [41672.881518] [tdb] Close table 'cache0.tdb' Apr 26 03:38:42 192.168.122.209 [41673.123696] [tdb] Close table 'filter0.tdb' Apr 26 03:38:42 192.168.122.209 [41673.124142] [tempesta fw] modules are stopped Apr 26 03:38:43 192.168.122.209 [41673.374471] [tempesta fw] exiting... Apr 26 03:38:43 192.168.122.209 [41673.532229] [tdb] Shutdown Tempesta DB Apr 26 03:38:43 192.168.122.209 [41673.728078] End test: http2_general.test_h2_streams.TestH2Stream.test_reuse_stream_id Apr 26 03:38:43 192.168.122.209 [41673.751938] Start test: http2_general.test_h2_streams.TestMultiplexing.test_base_multiplexing Apr 26 03:38:44 192.168.122.209 [41674.914299] [tdb] Start Tempesta DB Apr 26 03:38:44 192.168.122.209 [41675.060198] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:38:46 192.168.122.209 [41677.138736] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41677.138736] Maybe that's fine, but it's worth checking the [41677.138736] config - if there is no relations between the [41677.138736] names, then host name confusion attack is possible. Apr 26 03:38:46 192.168.122.209 [41677.309427] [tempesta fw] Configuration processing is completed. Apr 26 03:38:47 192.168.122.209 [41677.360721] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:38:47 192.168.122.209 [41677.776411] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:38:47 192.168.122.209 [41677.802326] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:38:47 192.168.122.209 [41677.829562] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:38:47 192.168.122.209 [41677.957403] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:38:47 192.168.122.209 [41677.997327] [tempesta fw] Tempesta FW is ready Apr 26 03:38:49 192.168.122.209 [41679.432497] [tdb] Close table 'client0.tdb' Apr 26 03:38:49 192.168.122.209 [41679.628575] [tdb] Close table 'sessions0.tdb' Apr 26 03:38:52 192.168.122.209 [41682.750505] [tdb] Close table 'cache0.tdb' Apr 26 03:38:52 192.168.122.209 [41682.991283] [tdb] Close table 'filter0.tdb' Apr 26 03:38:52 192.168.122.209 [41682.991740] [tempesta fw] modules are stopped Apr 26 03:38:52 192.168.122.209 [41683.281305] [tempesta fw] exiting... Apr 26 03:38:53 192.168.122.209 [41683.413181] [tdb] Shutdown Tempesta DB Apr 26 03:38:53 192.168.122.209 [41683.650615] End test: http2_general.test_h2_streams.TestMultiplexing.test_base_multiplexing Apr 26 03:38:53 192.168.122.209 [41683.670937] Start test: http_general.test_expect_100_continue.TestExpect100ContinueBehavior.test_regular_behaviour Apr 26 03:38:54 192.168.122.209 [41684.893419] [tdb] Start Tempesta DB Apr 26 03:38:54 192.168.122.209 [41685.047022] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:38:55 192.168.122.209 [41686.273514] [tempesta fw] Configuration processing is completed. Apr 26 03:38:55 192.168.122.209 [41686.325785] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:38:56 192.168.122.209 [41686.744230] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:38:56 192.168.122.209 [41686.769241] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:38:56 192.168.122.209 [41686.795157] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:38:56 192.168.122.209 [41686.853434] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:38:56 192.168.122.209 [41686.901434] [tempesta fw] Tempesta FW is ready Apr 26 03:38:56 192.168.122.209 [41687.073040] [tempesta fw] 127.0.0.2 "default" "PUT /test_100 HTTP/1.1" 200 0 "-" "-" "ja5t=0" "ja5h=18d200340200" Apr 26 03:38:57 192.168.122.209 [41687.488883] [tdb] Close table 'client0.tdb' Apr 26 03:38:57 192.168.122.209 [41687.679604] [tdb] Close table 'sessions0.tdb' Apr 26 03:39:00 192.168.122.209 [41690.838635] [tdb] Close table 'cache0.tdb' Apr 26 03:39:00 192.168.122.209 [41691.076742] [tdb] Close table 'filter0.tdb' Apr 26 03:39:00 192.168.122.209 [41691.077190] [tempesta fw] modules are stopped Apr 26 03:39:00 192.168.122.209 [41691.225621] [tempesta fw] exiting... Apr 26 03:39:01 192.168.122.209 [41691.358944] [tdb] Shutdown Tempesta DB Apr 26 03:39:01 192.168.122.209 [41691.600173] End test: http_general.test_expect_100_continue.TestExpect100ContinueBehavior.test_regular_behaviour Apr 26 03:39:01 192.168.122.209 [41691.614529] Start test: http_general.test_expect_100_continue.TestExpect100ContinueBehavior.test_request_pipeline_3_all_100 Apr 26 03:39:02 192.168.122.209 [41692.834532] [tdb] Start Tempesta DB Apr 26 03:39:02 192.168.122.209 [41692.998381] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:39:03 192.168.122.209 [41694.245678] [tempesta fw] Configuration processing is completed. Apr 26 03:39:03 192.168.122.209 [41694.295715] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:39:04 192.168.122.209 [41694.700093] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:39:04 192.168.122.209 [41694.734126] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:39:04 192.168.122.209 [41694.760018] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:39:04 192.168.122.209 [41694.805581] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:39:04 192.168.122.209 [41694.845544] [tempesta fw] Tempesta FW is ready Apr 26 03:39:04 192.168.122.209 [41694.988608] [tempesta fw] 127.0.0.2 "default" "PUT /expect HTTP/1.1" 200 0 "-" "-" "ja5t=0" "ja5h=18d200340200" Apr 26 03:39:04 192.168.122.209 [41694.988753] [tempesta fw] 127.0.0.2 "default" "PUT /expect HTTP/1.1" 200 0 "-" "-" "ja5t=0" "ja5h=18d200340200" Apr 26 03:39:04 192.168.122.209 [41694.991537] [tempesta fw] 127.0.0.2 "default" "PUT /expect HTTP/1.1" 200 0 "-" "-" "ja5t=0" "ja5h=18d200340200" Apr 26 03:39:05 192.168.122.209 [41695.446541] [tdb] Close table 'client0.tdb' Apr 26 03:39:05 192.168.122.209 [41695.634640] [tdb] Close table 'sessions0.tdb' Apr 26 03:39:08 192.168.122.209 [41698.774936] [tdb] Close table 'cache0.tdb' Apr 26 03:39:08 192.168.122.209 [41698.999604] [tdb] Close table 'filter0.tdb' Apr 26 03:39:08 192.168.122.209 [41699.000044] [tempesta fw] modules are stopped Apr 26 03:39:08 192.168.122.209 [41699.165844] [tempesta fw] exiting... Apr 26 03:39:08 192.168.122.209 [41699.315882] [tdb] Shutdown Tempesta DB Apr 26 03:39:09 192.168.122.209 [41699.548230] End test: http_general.test_expect_100_continue.TestExpect100ContinueBehavior.test_request_pipeline_3_all_100 Apr 26 03:39:09 192.168.122.209 [41699.559659] Start test: http_general.test_expect_100_continue.TestExpect100ContinueBehavior.test_request_pipeline_3_requests_empty_body Apr 26 03:39:10 192.168.122.209 [41700.787697] [tdb] Start Tempesta DB Apr 26 03:39:10 192.168.122.209 [41700.931263] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:39:11 192.168.122.209 [41702.197715] [tempesta fw] Configuration processing is completed. Apr 26 03:39:11 192.168.122.209 [41702.252272] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:39:12 192.168.122.209 [41702.669028] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:39:12 192.168.122.209 [41702.707620] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:39:12 192.168.122.209 [41702.732618] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:39:12 192.168.122.209 [41702.785719] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:39:12 192.168.122.209 [41702.845619] [tempesta fw] Tempesta FW is ready Apr 26 03:39:14 192.168.122.209 [41704.974203] [tempesta fw] 127.0.0.2 "default" "PUT /test HTTP/1.1" 200 0 "-" "-" "ja5t=0" "ja5h=22200340180" Apr 26 03:39:14 192.168.122.209 [41704.974288] [tempesta fw] 127.0.0.2 "default" "GET /test HTTP/1.1" 200 0 "-" "-" "ja5t=0" "ja5h=4000c0080" Apr 26 03:39:14 192.168.122.209 [41704.977943] [tempesta fw] 127.0.0.2 "default" "PUT /expect HTTP/1.1" 200 0 "-" "-" "ja5t=0" "ja5h=18d200340200" Apr 26 03:39:15 192.168.122.209 [41705.442324] [tdb] Close table 'client0.tdb' Apr 26 03:39:15 192.168.122.209 [41705.634201] [tdb] Close table 'sessions0.tdb' Apr 26 03:39:18 192.168.122.209 [41708.778137] [tdb] Close table 'cache0.tdb' Apr 26 03:39:18 192.168.122.209 [41709.011010] [tdb] Close table 'filter0.tdb' Apr 26 03:39:18 192.168.122.209 [41709.011441] [tempesta fw] modules are stopped Apr 26 03:39:18 192.168.122.209 [41709.175445] [tempesta fw] exiting... Apr 26 03:39:18 192.168.122.209 [41709.322234] [tdb] Shutdown Tempesta DB Apr 26 03:39:19 192.168.122.209 [41709.567615] End test: http_general.test_expect_100_continue.TestExpect100ContinueBehavior.test_request_pipeline_3_requests_empty_body Apr 26 03:39:19 192.168.122.209 [41709.581420] Start test: http_general.test_expect_100_continue.TestExpect100ContinueBehavior.test_request_pipeline_3_requests_encoding_chunked Apr 26 03:39:20 192.168.122.209 [41710.813452] [tdb] Start Tempesta DB Apr 26 03:39:20 192.168.122.209 [41710.952013] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:39:21 192.168.122.209 [41712.149857] [tempesta fw] Configuration processing is completed. Apr 26 03:39:21 192.168.122.209 [41712.200080] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:39:22 192.168.122.209 [41712.607358] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:39:22 192.168.122.209 [41712.633427] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:39:22 192.168.122.209 [41712.660525] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:39:22 192.168.122.209 [41712.713820] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:39:22 192.168.122.209 [41712.765748] [tempesta fw] Tempesta FW is ready Apr 26 03:39:22 192.168.122.209 [41712.905091] [tempesta fw] 127.0.0.2 "default" "PUT /test HTTP/1.1" 200 0 "-" "-" "ja5t=0" "ja5h=22200340180" Apr 26 03:39:22 192.168.122.209 [41712.905126] [tempesta fw] 127.0.0.2 "default" "PUT /expect HTTP/1.1" 200 0 "-" "-" "ja5t=0" "ja5h=18f500340200" Apr 26 03:39:22 192.168.122.209 [41712.906133] [tempesta fw] 127.0.0.2 "default" "GET /test HTTP/1.1" 200 0 "-" "-" "ja5t=0" "ja5h=4000c0080" Apr 26 03:39:23 192.168.122.209 [41713.359726] [tdb] Close table 'client0.tdb' Apr 26 03:39:23 192.168.122.209 [41713.549468] [tdb] Close table 'sessions0.tdb' Apr 26 03:39:26 192.168.122.209 [41716.750030] [tdb] Close table 'cache0.tdb' Apr 26 03:39:26 192.168.122.209 [41716.985768] [tdb] Close table 'filter0.tdb' Apr 26 03:39:26 192.168.122.209 [41716.986203] [tempesta fw] modules are stopped Apr 26 03:39:26 192.168.122.209 [41717.157051] [tempesta fw] exiting... Apr 26 03:39:26 192.168.122.209 [41717.283980] [tdb] Shutdown Tempesta DB Apr 26 03:39:27 192.168.122.209 [41717.496369] End test: http_general.test_expect_100_continue.TestExpect100ContinueBehavior.test_request_pipeline_3_requests_encoding_chunked Apr 26 03:39:27 192.168.122.209 [41717.507613] Start test: http_general.test_expect_100_continue.TestExpect100ContinueBehavior.test_request_pipeline_delay Apr 26 03:39:28 192.168.122.209 [41718.709668] [tdb] Start Tempesta DB Apr 26 03:39:28 192.168.122.209 [41718.857073] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:39:29 192.168.122.209 [41720.137882] [tempesta fw] Configuration processing is completed. Apr 26 03:39:29 192.168.122.209 [41720.187982] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:39:30 192.168.122.209 [41720.604146] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:39:30 192.168.122.209 [41720.629505] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:39:30 192.168.122.209 [41720.655670] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:39:30 192.168.122.209 [41720.693910] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:39:30 192.168.122.209 [41720.733848] [tempesta fw] Tempesta FW is ready Apr 26 03:39:32 192.168.122.209 [41722.858383] [tempesta fw] 127.0.0.2 "default" "PUT /test HTTP/1.1" 200 0 "-" "-" "ja5t=0" "ja5h=22200340180" Apr 26 03:39:34 192.168.122.209 [41724.864233] [tempesta fw] 127.0.0.2 "default" "PUT /expect HTTP/1.1" 200 0 "-" "-" "ja5t=0" "ja5h=18d200340200" Apr 26 03:39:34 192.168.122.209 [41725.270784] [tdb] Close table 'client0.tdb' Apr 26 03:39:35 192.168.122.209 [41725.463154] [tdb] Close table 'sessions0.tdb' Apr 26 03:39:38 192.168.122.209 [41728.659012] [tdb] Close table 'cache0.tdb' Apr 26 03:39:38 192.168.122.209 [41728.901798] [tdb] Close table 'filter0.tdb' Apr 26 03:39:38 192.168.122.209 [41728.902227] [tempesta fw] modules are stopped Apr 26 03:39:38 192.168.122.209 [41729.097993] [tempesta fw] exiting... Apr 26 03:39:38 192.168.122.209 [41729.282342] [tdb] Shutdown Tempesta DB Apr 26 03:39:39 192.168.122.209 [41729.526108] End test: http_general.test_expect_100_continue.TestExpect100ContinueBehavior.test_request_pipeline_delay Apr 26 03:39:39 192.168.122.209 [41729.538980] Start test: http_general.test_expect_100_continue.TestExpect100ContinueBehavior.test_request_pipeline_delay_3_requests Apr 26 03:39:40 192.168.122.209 [41730.774901] [tdb] Start Tempesta DB Apr 26 03:39:40 192.168.122.209 [41730.925044] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:39:41 192.168.122.209 [41732.162084] [tempesta fw] Configuration processing is completed. Apr 26 03:39:41 192.168.122.209 [41732.212850] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:39:42 192.168.122.209 [41732.619353] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:39:42 192.168.122.209 [41732.644896] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:39:42 192.168.122.209 [41732.671519] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:39:42 192.168.122.209 [41732.710132] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:39:42 192.168.122.209 [41732.750018] [tempesta fw] Tempesta FW is ready Apr 26 03:39:44 192.168.122.209 [41734.893443] [tempesta fw] 127.0.0.2 "default" "PUT /test HTTP/1.1" 200 0 "-" "-" "ja5t=0" "ja5h=22200340180" Apr 26 03:39:46 192.168.122.209 [41736.907729] [tempesta fw] 127.0.0.2 "default" "PUT /expect HTTP/1.1" 200 0 "-" "-" "ja5t=0" "ja5h=18d200340200" Apr 26 03:39:46 192.168.122.209 [41736.907796] [tempesta fw] 127.0.0.2 "default" "GET /test HTTP/1.1" 200 0 "-" "-" "ja5t=0" "ja5h=4000c0080" Apr 26 03:39:47 192.168.122.209 [41737.346394] [tdb] Close table 'client0.tdb' Apr 26 03:39:47 192.168.122.209 [41737.524469] [tdb] Close table 'sessions0.tdb' Apr 26 03:39:50 192.168.122.209 [41740.655149] [tdb] Close table 'cache0.tdb' Apr 26 03:39:50 192.168.122.209 [41740.921324] [tdb] Close table 'filter0.tdb' Apr 26 03:39:50 192.168.122.209 [41740.921759] [tempesta fw] modules are stopped Apr 26 03:39:50 192.168.122.209 [41741.130709] [tempesta fw] exiting... Apr 26 03:39:50 192.168.122.209 [41741.279341] [tdb] Shutdown Tempesta DB Apr 26 03:39:51 192.168.122.209 [41741.492322] End test: http_general.test_expect_100_continue.TestExpect100ContinueBehavior.test_request_pipeline_delay_3_requests Apr 26 03:39:51 192.168.122.209 [41741.511969] Start test: http_general.test_expect_100_continue.TestExpect100ContinueBehavior.test_request_pipeline_delay_no_wait Apr 26 03:39:52 192.168.122.209 [41742.741114] [tdb] Start Tempesta DB Apr 26 03:39:52 192.168.122.209 [41742.893938] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:39:53 192.168.122.209 [41744.146257] [tempesta fw] Configuration processing is completed. Apr 26 03:39:53 192.168.122.209 [41744.196576] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:39:54 192.168.122.209 [41744.660339] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:39:54 192.168.122.209 [41744.694690] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:39:54 192.168.122.209 [41744.729561] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:39:54 192.168.122.209 [41744.786115] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:39:54 192.168.122.209 [41744.826072] [tempesta fw] Tempesta FW is ready Apr 26 03:39:56 192.168.122.209 [41746.984707] [tempesta fw] 127.0.0.2 "default" "PUT /test HTTP/1.1" 200 0 "-" "-" "ja5t=0" "ja5h=22200340180" Apr 26 03:39:56 192.168.122.209 [41747.176811] [tempesta fw] 127.0.0.2 "default" "PUT /expect HTTP/1.1" 200 0 "-" "-" "ja5t=0" "ja5h=18d200340200" Apr 26 03:39:57 192.168.122.209 [41747.608653] [tdb] Close table 'client0.tdb' Apr 26 03:39:57 192.168.122.209 [41747.797298] [tdb] Close table 'sessions0.tdb' Apr 26 03:40:00 192.168.122.209 [41750.928268] [tdb] Close table 'cache0.tdb' Apr 26 03:40:00 192.168.122.209 [41751.172177] [tdb] Close table 'filter0.tdb' Apr 26 03:40:00 192.168.122.209 [41751.172602] [tempesta fw] modules are stopped Apr 26 03:40:01 192.168.122.209 [41751.342479] [tempesta fw] exiting... Apr 26 03:40:01 192.168.122.209 [41751.481782] [tdb] Shutdown Tempesta DB Apr 26 03:40:01 192.168.122.209 [41751.729824] End test: http_general.test_expect_100_continue.TestExpect100ContinueBehavior.test_request_pipeline_delay_no_wait Apr 26 03:40:01 192.168.122.209 [41751.745714] Start test: http_general.test_expect_100_continue.TestExpect100ContinueBehavior.test_send_full_request Apr 26 03:40:02 192.168.122.209 [41752.925914] [tdb] Start Tempesta DB Apr 26 03:40:02 192.168.122.209 [41753.079011] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:40:03 192.168.122.209 [41754.302347] [tempesta fw] Configuration processing is completed. Apr 26 03:40:04 192.168.122.209 [41754.352022] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:40:04 192.168.122.209 [41754.759080] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:40:04 192.168.122.209 [41754.785068] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:40:04 192.168.122.209 [41754.811600] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:40:04 192.168.122.209 [41754.870327] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:40:04 192.168.122.209 [41754.910316] [tempesta fw] Tempesta FW is ready Apr 26 03:40:04 192.168.122.209 [41755.039456] [tempesta fw] 127.0.0.2 "default" "PUT /test_100 HTTP/1.1" 200 0 "-" "-" "ja5t=0" "ja5h=18d200340200" Apr 26 03:40:05 192.168.122.209 [41755.482999] [tdb] Close table 'client0.tdb' Apr 26 03:40:05 192.168.122.209 [41755.710399] [tdb] Close table 'sessions0.tdb' Apr 26 03:40:08 192.168.122.209 [41758.879795] [tdb] Close table 'cache0.tdb' Apr 26 03:40:08 192.168.122.209 [41759.113400] [tdb] Close table 'filter0.tdb' Apr 26 03:40:08 192.168.122.209 [41759.113839] [tempesta fw] modules are stopped Apr 26 03:40:09 192.168.122.209 [41759.355693] [tempesta fw] exiting... Apr 26 03:40:09 192.168.122.209 [41759.509132] [tdb] Shutdown Tempesta DB Apr 26 03:40:09 192.168.122.209 [41759.742156] End test: http_general.test_expect_100_continue.TestExpect100ContinueBehavior.test_send_full_request Apr 26 03:40:09 192.168.122.209 [41759.766833] Start test: http_general.test_headers.BackendSetCoookie.test_request_success Apr 26 03:40:10 192.168.122.209 [41760.926344] [tdb] Start Tempesta DB Apr 26 03:40:10 192.168.122.209 [41761.075970] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:40:12 192.168.122.209 [41762.634532] [tempesta fw] Configuration processing is completed. Apr 26 03:40:12 192.168.122.209 [41762.698356] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:40:12 192.168.122.209 [41763.117998] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:40:12 192.168.122.209 [41763.143431] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:40:12 192.168.122.209 [41763.169584] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:40:12 192.168.122.209 [41763.262431] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:40:12 192.168.122.209 [41763.322382] [tempesta fw] Tempesta FW is ready Apr 26 03:40:13 192.168.122.209 [41764.059606] [tdb] Close table 'client0.tdb' Apr 26 03:40:13 192.168.122.209 [41764.241219] [tdb] Close table 'sessions0.tdb' Apr 26 03:40:17 192.168.122.209 [41767.384441] [tdb] Close table 'cache0.tdb' Apr 26 03:40:17 192.168.122.209 [41767.615666] [tdb] Close table 'filter0.tdb' Apr 26 03:40:17 192.168.122.209 [41767.616106] [tempesta fw] modules are stopped Apr 26 03:40:17 192.168.122.209 [41767.826603] [tempesta fw] exiting... Apr 26 03:40:17 192.168.122.209 [41767.964174] [tdb] Shutdown Tempesta DB Apr 26 03:40:17 192.168.122.209 [41768.181415] End test: http_general.test_headers.BackendSetCoookie.test_request_success Apr 26 03:40:17 192.168.122.209 [41768.192955] Start test: http_general.test_headers.RepeatedHeaderCache.test_request_cache_del_dup_success Apr 26 03:40:19 192.168.122.209 [41769.393090] [tdb] Start Tempesta DB Apr 26 03:40:19 192.168.122.209 [41769.535135] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:40:20 192.168.122.209 [41770.902555] [tempesta fw] Configuration processing is completed. Apr 26 03:40:20 192.168.122.209 [41770.958731] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:40:21 192.168.122.209 [41771.369596] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:40:21 192.168.122.209 [41771.395592] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:40:21 192.168.122.209 [41771.421980] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:40:21 192.168.122.209 [41771.474577] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:40:21 192.168.122.209 [41771.522448] [tempesta fw] Tempesta FW is ready Apr 26 03:40:21 192.168.122.209 [41772.093368] [tdb] Close table 'client0.tdb' Apr 26 03:40:21 192.168.122.209 [41772.285444] [tdb] Close table 'sessions0.tdb' Apr 26 03:40:25 192.168.122.209 [41775.507756] [tdb] Close table 'cache0.tdb' Apr 26 03:40:25 192.168.122.209 [41775.752582] [tdb] Close table 'filter0.tdb' Apr 26 03:40:25 192.168.122.209 [41775.753030] [tempesta fw] modules are stopped Apr 26 03:40:25 192.168.122.209 [41775.937267] [tempesta fw] exiting... Apr 26 03:40:25 192.168.122.209 [41776.072856] [tdb] Shutdown Tempesta DB Apr 26 03:40:25 192.168.122.209 [41776.268935] End test: http_general.test_headers.RepeatedHeaderCache.test_request_cache_del_dup_success Apr 26 03:40:25 192.168.122.209 [41776.290989] Start test: http_general.test_headers.TestContentTypeWithEmptyBodyDELETE.test_request_success Apr 26 03:40:27 192.168.122.209 [41777.456546] [tdb] Start Tempesta DB Apr 26 03:40:27 192.168.122.209 [41777.602580] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:40:28 192.168.122.209 [41778.936015] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41778.936015] Maybe that's fine, but it's worth checking the [41778.936015] config - if there is no relations between the [41778.936015] names, then host name confusion attack is possible. Apr 26 03:40:28 192.168.122.209 [41779.050678] [tempesta fw] Configuration processing is completed. Apr 26 03:40:28 192.168.122.209 [41779.100697] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:40:29 192.168.122.209 [41779.502609] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:40:29 192.168.122.209 [41779.537092] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:40:29 192.168.122.209 [41779.602859] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:40:29 192.168.122.209 [41779.658667] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:40:29 192.168.122.209 [41779.710626] [tempesta fw] Tempesta FW is ready Apr 26 03:40:29 192.168.122.209 [41779.855433] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 03:40:29 192.168.122.209 [41779.856212] [tempesta fw] Warning: Can't create pipelined response: 127.0.0.3 Apr 26 03:40:29 192.168.122.209 [41779.856856] [tempesta fw] 127.0.0.2 "default" "DELETE / HTTP/1.1" 200 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400080080" Apr 26 03:40:30 192.168.122.209 [41780.361003] [tdb] Close table 'client0.tdb' Apr 26 03:40:30 192.168.122.209 [41780.566547] [tdb] Close table 'sessions0.tdb' Apr 26 03:40:33 192.168.122.209 [41783.777714] [tdb] Close table 'cache0.tdb' Apr 26 03:40:33 192.168.122.209 [41784.023283] [tdb] Close table 'filter0.tdb' Apr 26 03:40:33 192.168.122.209 [41784.023720] [tempesta fw] modules are stopped Apr 26 03:40:33 192.168.122.209 [41784.219048] [tempesta fw] exiting... Apr 26 03:40:34 192.168.122.209 [41784.358763] [tdb] Shutdown Tempesta DB Apr 26 03:40:34 192.168.122.209 [41784.561974] End test: http_general.test_headers.TestContentTypeWithEmptyBodyDELETE.test_request_success Apr 26 03:40:34 192.168.122.209 [41784.576645] Start test: http_general.test_headers.TestContentTypeWithEmptyBodyPATCH.test_request_success Apr 26 03:40:35 192.168.122.209 [41785.785510] [tdb] Start Tempesta DB Apr 26 03:40:35 192.168.122.209 [41785.931780] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:40:36 192.168.122.209 [41787.235911] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41787.235911] Maybe that's fine, but it's worth checking the [41787.235911] config - if there is no relations between the [41787.235911] names, then host name confusion attack is possible. Apr 26 03:40:37 192.168.122.209 [41787.366788] [tempesta fw] Configuration processing is completed. Apr 26 03:40:37 192.168.122.209 [41787.418016] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:40:37 192.168.122.209 [41787.833903] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:40:37 192.168.122.209 [41787.867094] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:40:37 192.168.122.209 [41787.893529] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:40:37 192.168.122.209 [41787.938745] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:40:37 192.168.122.209 [41787.978679] [tempesta fw] Tempesta FW is ready Apr 26 03:40:37 192.168.122.209 [41788.121201] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 03:40:37 192.168.122.209 [41788.123508] [tempesta fw] Warning: Can't create pipelined response: 127.0.0.3 Apr 26 03:40:37 192.168.122.209 [41788.125498] [tempesta fw] 127.0.0.2 "default" "PATCH / HTTP/1.1" 200 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400240080" Apr 26 03:40:38 192.168.122.209 [41788.542863] [tdb] Close table 'client0.tdb' Apr 26 03:40:38 192.168.122.209 [41788.751016] [tdb] Close table 'sessions0.tdb' Apr 26 03:40:41 192.168.122.209 [41791.908117] [tdb] Close table 'cache0.tdb' Apr 26 03:40:41 192.168.122.209 [41792.149511] [tdb] Close table 'filter0.tdb' Apr 26 03:40:41 192.168.122.209 [41792.149952] [tempesta fw] modules are stopped Apr 26 03:40:42 192.168.122.209 [41792.383138] [tempesta fw] exiting... Apr 26 03:40:42 192.168.122.209 [41792.509816] [tdb] Shutdown Tempesta DB Apr 26 03:40:42 192.168.122.209 [41792.714300] End test: http_general.test_headers.TestContentTypeWithEmptyBodyPATCH.test_request_success Apr 26 03:40:42 192.168.122.209 [41792.734280] Start test: http_general.test_headers.TestContentTypeWithEmptyBodyPOST.test_request_success Apr 26 03:40:43 192.168.122.209 [41793.876853] [tdb] Start Tempesta DB Apr 26 03:40:43 192.168.122.209 [41794.038425] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:40:45 192.168.122.209 [41795.364101] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41795.364101] Maybe that's fine, but it's worth checking the [41795.364101] config - if there is no relations between the [41795.364101] names, then host name confusion attack is possible. Apr 26 03:40:45 192.168.122.209 [41795.482865] [tempesta fw] Configuration processing is completed. Apr 26 03:40:45 192.168.122.209 [41795.533198] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:40:45 192.168.122.209 [41795.941769] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:40:45 192.168.122.209 [41795.977879] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:40:45 192.168.122.209 [41796.042153] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:40:45 192.168.122.209 [41796.094849] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:40:45 192.168.122.209 [41796.142822] [tempesta fw] Tempesta FW is ready Apr 26 03:40:45 192.168.122.209 [41796.298473] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 03:40:45 192.168.122.209 [41796.299576] [tempesta fw] Warning: Can't create pipelined response: 127.0.0.3 Apr 26 03:40:45 192.168.122.209 [41796.300823] [tempesta fw] 127.0.0.2 "default" "POST / HTTP/1.1" 200 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400280080" Apr 26 03:40:46 192.168.122.209 [41796.806788] [tdb] Close table 'client0.tdb' Apr 26 03:40:46 192.168.122.209 [41797.004117] [tdb] Close table 'sessions0.tdb' Apr 26 03:40:49 192.168.122.209 [41800.177602] [tdb] Close table 'cache0.tdb' Apr 26 03:40:50 192.168.122.209 [41800.388764] [tdb] Close table 'filter0.tdb' Apr 26 03:40:50 192.168.122.209 [41800.389201] [tempesta fw] modules are stopped Apr 26 03:40:50 192.168.122.209 [41800.608154] [tempesta fw] exiting... Apr 26 03:40:50 192.168.122.209 [41800.758669] [tdb] Shutdown Tempesta DB Apr 26 03:40:50 192.168.122.209 [41801.010651] End test: http_general.test_headers.TestContentTypeWithEmptyBodyPOST.test_request_success Apr 26 03:40:50 192.168.122.209 [41801.022665] Start test: http_general.test_headers.TestContentTypeWithEmptyBodyPUT.test_request_success Apr 26 03:40:51 192.168.122.209 [41802.206555] [tdb] Start Tempesta DB Apr 26 03:40:52 192.168.122.209 [41802.356717] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:40:53 192.168.122.209 [41803.700189] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [41803.700189] Maybe that's fine, but it's worth checking the [41803.700189] config - if there is no relations between the [41803.700189] names, then host name confusion attack is possible. Apr 26 03:40:53 192.168.122.209 [41803.830972] [tempesta fw] Configuration processing is completed. Apr 26 03:40:53 192.168.122.209 [41803.881990] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:40:53 192.168.122.209 [41804.303278] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:40:53 192.168.122.209 [41804.328442] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:40:54 192.168.122.209 [41804.354022] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:40:54 192.168.122.209 [41804.426943] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:40:54 192.168.122.209 [41804.466925] [tempesta fw] Tempesta FW is ready Apr 26 03:40:54 192.168.122.209 [41804.608507] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 03:40:54 192.168.122.209 [41804.610859] [tempesta fw] Warning: Can't create pipelined response: 127.0.0.3 Apr 26 03:40:54 192.168.122.209 [41804.612872] [tempesta fw] 127.0.0.2 "default" "PUT / HTTP/1.1" 200 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400340080" Apr 26 03:40:54 192.168.122.209 [41805.081231] [tdb] Close table 'client0.tdb' Apr 26 03:40:54 192.168.122.209 [41805.296408] [tdb] Close table 'sessions0.tdb' Apr 26 03:40:58 192.168.122.209 [41808.516736] [tdb] Close table 'cache0.tdb' Apr 26 03:40:58 192.168.122.209 [41808.743184] [tdb] Close table 'filter0.tdb' Apr 26 03:40:58 192.168.122.209 [41808.743636] [tempesta fw] modules are stopped Apr 26 03:40:58 192.168.122.209 [41808.991558] [tempesta fw] exiting... Apr 26 03:40:58 192.168.122.209 [41809.191885] [tdb] Shutdown Tempesta DB Apr 26 03:40:59 192.168.122.209 [41809.450507] End test: http_general.test_headers.TestContentTypeWithEmptyBodyPUT.test_request_success Apr 26 03:40:59 192.168.122.209 [41809.472224] Start test: http_general.test_headers.TestHeadersBlockedByMaxHeaderListSize.test_blocked_by_max_headers_count Apr 26 03:41:00 192.168.122.209 [41810.586530] [tdb] Start Tempesta DB Apr 26 03:41:00 192.168.122.209 [41810.741053] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:41:01 192.168.122.209 [41812.019066] [tempesta fw] Configuration processing is completed. Apr 26 03:41:01 192.168.122.209 [41812.073610] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:41:02 192.168.122.209 [41812.478172] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:41:02 192.168.122.209 [41812.534531] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:41:02 192.168.122.209 [41812.560568] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:41:02 192.168.122.209 [41812.638990] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:41:02 192.168.122.209 [41812.691000] [tempesta fw] Tempesta FW is ready Apr 26 03:41:02 192.168.122.209 [41812.842285] [tempesta fw] Warning: frang: HTTP header list size exceeded for 127.0.0.2: 24 (lim=23) Apr 26 03:41:02 192.168.122.209 [41813.264980] [tdb] Close table 'client0.tdb' Apr 26 03:41:03 192.168.122.209 [41813.492549] [tdb] Close table 'sessions0.tdb' Apr 26 03:41:06 192.168.122.209 [41816.647516] [tdb] Close table 'cache0.tdb' Apr 26 03:41:06 192.168.122.209 [41816.921754] [tdb] Close table 'filter0.tdb' Apr 26 03:41:06 192.168.122.209 [41816.922187] [tempesta fw] modules are stopped Apr 26 03:41:06 192.168.122.209 [41817.100740] [tempesta fw] exiting... Apr 26 03:41:06 192.168.122.209 [41817.262313] [tdb] Shutdown Tempesta DB Apr 26 03:41:07 192.168.122.209 [41817.459825] End test: http_general.test_headers.TestHeadersBlockedByMaxHeaderListSize.test_blocked_by_max_headers_count Apr 26 03:41:07 192.168.122.209 [41817.474481] Start test: http_general.test_headers.TestHeadersBlockedByMaxHeaderListSize.test_not_blocked_by_max_headers_count Apr 26 03:41:08 192.168.122.209 [41818.629832] [tdb] Start Tempesta DB Apr 26 03:41:08 192.168.122.209 [41818.788478] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:41:09 192.168.122.209 [41820.147206] [tempesta fw] Configuration processing is completed. Apr 26 03:41:09 192.168.122.209 [41820.197305] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:41:10 192.168.122.209 [41820.602573] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:41:10 192.168.122.209 [41820.628135] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:41:10 192.168.122.209 [41820.653537] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:41:10 192.168.122.209 [41820.699163] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:41:10 192.168.122.209 [41820.743096] [tempesta fw] Tempesta FW is ready Apr 26 03:41:10 192.168.122.209 [41821.298777] [tdb] Close table 'client0.tdb' Apr 26 03:41:11 192.168.122.209 [41821.505343] [tdb] Close table 'sessions0.tdb' Apr 26 03:41:14 192.168.122.209 [41824.717565] [tdb] Close table 'cache0.tdb' Apr 26 03:41:14 192.168.122.209 [41824.971694] [tdb] Close table 'filter0.tdb' Apr 26 03:41:14 192.168.122.209 [41824.972151] [tempesta fw] modules are stopped Apr 26 03:41:14 192.168.122.209 [41825.137975] [tempesta fw] exiting... Apr 26 03:41:14 192.168.122.209 [41825.267933] [tdb] Shutdown Tempesta DB Apr 26 03:41:15 192.168.122.209 [41825.474467] End test: http_general.test_headers.TestHeadersBlockedByMaxHeaderListSize.test_not_blocked_by_max_headers_count Apr 26 03:41:15 192.168.122.209 [41825.483908] Start test: http_general.test_headers.TestHeadersParsing.test_invalid_trailers_in_request Apr 26 03:41:16 192.168.122.209 [41826.656776] [tdb] Start Tempesta DB Apr 26 03:41:16 192.168.122.209 [41826.807459] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:41:17 192.168.122.209 [41828.135310] [tempesta fw] Configuration processing is completed. Apr 26 03:41:17 192.168.122.209 [41828.231716] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:41:17 192.168.122.209 [41828.261515] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:41:17 192.168.122.209 [41828.296337] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:41:18 192.168.122.209 [41828.339271] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:41:18 192.168.122.209 [41828.387243] [tempesta fw] Tempesta FW is ready Apr 26 03:41:18 192.168.122.209 [41828.518869] [tempesta fw] Warning: Parser error: state=Req_HdrCache_ControlV input(-8)=0x6e('ontrol: no-cache [41828.518869] X-Token2: value2 [41828.518869] [41828.518869] ') data_len=254 off=224 Apr 26 03:41:18 192.168.122.209 [41828.989268] [tdb] Close table 'client0.tdb' Apr 26 03:41:18 192.168.122.209 [41829.179815] [tdb] Close table 'sessions0.tdb' Apr 26 03:41:19 192.168.122.209 [41829.403043] [tdb] Close table 'filter0.tdb' Apr 26 03:41:19 192.168.122.209 [41829.403491] [tempesta fw] modules are stopped Apr 26 03:41:19 192.168.122.209 [41829.610274] [tempesta fw] exiting... Apr 26 03:41:19 192.168.122.209 [41829.760614] [tdb] Shutdown Tempesta DB Apr 26 03:41:19 192.168.122.209 [41829.987629] End test: http_general.test_headers.TestHeadersParsing.test_invalid_trailers_in_request Apr 26 03:41:19 192.168.122.209 [41829.994857] Start test: http_general.test_headers.TestHeadersParsing.test_invalid_trailers_in_response_cache_control Apr 26 03:41:20 192.168.122.209 [41831.103532] [tdb] Start Tempesta DB Apr 26 03:41:20 192.168.122.209 [41831.250822] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:41:21 192.168.122.209 [41831.799425] [tempesta fw] Configuration processing is completed. Apr 26 03:41:21 192.168.122.209 [41831.850788] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:41:21 192.168.122.209 [41831.879761] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:41:21 192.168.122.209 [41831.907577] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:41:21 192.168.122.209 [41831.951297] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:41:21 192.168.122.209 [41831.991273] [tempesta fw] Tempesta FW is ready Apr 26 03:41:21 192.168.122.209 [41832.129326] [tempesta fw] Warning: Parser error: state=Resp_HdrCache_CtrlV input(-8)=0x6e('ontrol: no-cache [41832.129326] [41832.129326] ') data_len=123 off=111 Apr 26 03:41:21 192.168.122.209 [41832.133476] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 03:41:22 192.168.122.209 [41832.574402] [tdb] Close table 'client0.tdb' Apr 26 03:41:22 192.168.122.209 [41832.755654] [tdb] Close table 'sessions0.tdb' Apr 26 03:41:22 192.168.122.209 [41833.000652] [tdb] Close table 'filter0.tdb' Apr 26 03:41:22 192.168.122.209 [41833.001089] [tempesta fw] modules are stopped Apr 26 03:41:22 192.168.122.209 [41833.181088] [tempesta fw] exiting... Apr 26 03:41:22 192.168.122.209 [41833.328516] [tdb] Shutdown Tempesta DB Apr 26 03:41:23 192.168.122.209 [41833.551716] End test: http_general.test_headers.TestHeadersParsing.test_invalid_trailers_in_response_cache_control Apr 26 03:41:23 192.168.122.209 [41833.564113] Start test: http_general.test_headers.TestHeadersParsing.test_invalid_trailers_in_response_date Apr 26 03:41:24 192.168.122.209 [41834.689541] [tdb] Start Tempesta DB Apr 26 03:41:24 192.168.122.209 [41834.832813] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:41:25 192.168.122.209 [41835.395388] [tempesta fw] Configuration processing is completed. Apr 26 03:41:25 192.168.122.209 [41835.448111] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:41:25 192.168.122.209 [41835.478252] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:41:25 192.168.122.209 [41835.506567] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:41:25 192.168.122.209 [41835.547346] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:41:25 192.168.122.209 [41835.587287] [tempesta fw] Tempesta FW is ready Apr 26 03:41:25 192.168.122.209 [41835.701701] [tempesta fw] Warning: Parser error: state=Resp_HdrDateV input(-8)=0x4d(' [41835.701701] date: Mon, 12 Dec 2016 13:59:39 GMT [41835.701701] [41835.701701] ') data_len=126 off=93 Apr 26 03:41:25 192.168.122.209 [41836.122176] [tdb] Close table 'client0.tdb' Apr 26 03:41:25 192.168.122.209 [41836.305977] [tdb] Close table 'sessions0.tdb' Apr 26 03:41:26 192.168.122.209 [41836.505567] [tdb] Close table 'filter0.tdb' Apr 26 03:41:26 192.168.122.209 [41836.506030] net_ratelimit: 1 callbacks suppressed Apr 26 03:41:26 192.168.122.209 [41836.506032] [tempesta fw] modules are stopped Apr 26 03:41:26 192.168.122.209 [41836.691567] [tempesta fw] exiting... Apr 26 03:41:26 192.168.122.209 [41836.842841] [tdb] Shutdown Tempesta DB Apr 26 03:41:26 192.168.122.209 [41837.051422] End test: http_general.test_headers.TestHeadersParsing.test_invalid_trailers_in_response_date Apr 26 03:41:26 192.168.122.209 [41837.078766] Start test: http_general.test_headers.TestHeadersParsing.test_invalid_trailers_in_response_expires Apr 26 03:41:27 192.168.122.209 [41838.166391] [tdb] Start Tempesta DB Apr 26 03:41:27 192.168.122.209 [41838.321012] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:41:28 192.168.122.209 [41838.899860] [tempesta fw] Configuration processing is completed. Apr 26 03:41:28 192.168.122.209 [41838.953817] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:41:28 192.168.122.209 [41838.983656] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:41:28 192.168.122.209 [41839.012348] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:41:28 192.168.122.209 [41839.059381] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:41:28 192.168.122.209 [41839.107335] [tempesta fw] Tempesta FW is ready Apr 26 03:41:28 192.168.122.209 [41839.237170] [tempesta fw] Warning: Parser error: state=Resp_HdrExpiresV input(-8)=0x54('xpires: Thu, 01 Dec 2102 16:00:00 GMT [41839.237170] [41839.237170] ') data_len=132 off=99 Apr 26 03:41:28 192.168.122.209 [41839.239529] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 03:41:29 192.168.122.209 [41839.652040] [tdb] Close table 'client0.tdb' Apr 26 03:41:29 192.168.122.209 [41839.838658] [tdb] Close table 'sessions0.tdb' Apr 26 03:41:29 192.168.122.209 [41840.071776] [tdb] Close table 'filter0.tdb' Apr 26 03:41:29 192.168.122.209 [41840.072222] [tempesta fw] modules are stopped Apr 26 03:41:29 192.168.122.209 [41840.259297] [tempesta fw] exiting... Apr 26 03:41:30 192.168.122.209 [41840.389061] [tdb] Shutdown Tempesta DB Apr 26 03:41:30 192.168.122.209 [41840.604967] End test: http_general.test_headers.TestHeadersParsing.test_invalid_trailers_in_response_expires Apr 26 03:41:30 192.168.122.209 [41840.615717] Start test: http_general.test_headers.TestHeadersParsing.test_invalid_trailers_in_response_last_modified Apr 26 03:41:31 192.168.122.209 [41841.750446] [tdb] Start Tempesta DB Apr 26 03:41:31 192.168.122.209 [41841.905378] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:41:32 192.168.122.209 [41842.435457] [tempesta fw] Configuration processing is completed. Apr 26 03:41:32 192.168.122.209 [41842.492084] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:41:32 192.168.122.209 [41842.521525] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:41:32 192.168.122.209 [41842.549120] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:41:32 192.168.122.209 [41842.595415] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:41:32 192.168.122.209 [41842.639379] [tempesta fw] Tempesta FW is ready Apr 26 03:41:32 192.168.122.209 [41842.766752] [tempesta fw] Warning: Parser error: state=Resp_HdrLast_ModifiedV input(-8)=0x4d('dified: Mon, 12 Dec 2016 13:59:39 GMT [41842.766752] [41842.766752] ') data_len=144 off=111 Apr 26 03:41:32 192.168.122.209 [41842.771362] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 03:41:32 192.168.122.209 [41843.176386] [tdb] Close table 'client0.tdb' Apr 26 03:41:33 192.168.122.209 [41843.357999] [tdb] Close table 'sessions0.tdb' Apr 26 03:41:33 192.168.122.209 [41843.574531] [tdb] Close table 'filter0.tdb' Apr 26 03:41:33 192.168.122.209 [41843.574963] [tempesta fw] modules are stopped Apr 26 03:41:33 192.168.122.209 [41843.810066] [tempesta fw] exiting... Apr 26 03:41:33 192.168.122.209 [41843.950893] [tdb] Shutdown Tempesta DB Apr 26 03:41:33 192.168.122.209 [41844.159991] End test: http_general.test_headers.TestHeadersParsing.test_invalid_trailers_in_response_last_modified Apr 26 03:41:33 192.168.122.209 [41844.184536] Start test: http_general.test_headers.TestHeadersParsing.test_invalid_trailers_in_response_vary Apr 26 03:41:34 192.168.122.209 [41845.281981] [tdb] Start Tempesta DB Apr 26 03:41:35 192.168.122.209 [41845.437543] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:41:35 192.168.122.209 [41845.991450] [tempesta fw] Configuration processing is completed. Apr 26 03:41:35 192.168.122.209 [41846.043324] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:41:35 192.168.122.209 [41846.073063] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:41:35 192.168.122.209 [41846.100981] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:41:35 192.168.122.209 [41846.139472] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:41:35 192.168.122.209 [41846.179428] [tempesta fw] Tempesta FW is ready Apr 26 03:41:35 192.168.122.209 [41846.314154] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 03:41:36 192.168.122.209 [41846.740655] [tdb] Close table 'client0.tdb' Apr 26 03:41:36 192.168.122.209 [41846.915231] [tdb] Close table 'sessions0.tdb' Apr 26 03:41:36 192.168.122.209 [41847.141243] [tdb] Close table 'filter0.tdb' Apr 26 03:41:36 192.168.122.209 [41847.141680] [tempesta fw] modules are stopped Apr 26 03:41:37 192.168.122.209 [41847.351706] [tempesta fw] exiting... Apr 26 03:41:37 192.168.122.209 [41847.502623] [tdb] Shutdown Tempesta DB Apr 26 03:41:37 192.168.122.209 [41847.696263] End test: http_general.test_headers.TestHeadersParsing.test_invalid_trailers_in_response_vary Apr 26 03:41:37 192.168.122.209 [41847.716416] Start test: http_general.test_headers.TestHeadersParsing.test_long_header_name_in_request Apr 26 03:41:38 192.168.122.209 [41848.835664] [tdb] Start Tempesta DB Apr 26 03:41:38 192.168.122.209 [41848.990088] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:41:39 192.168.122.209 [41849.575539] [tempesta fw] Configuration processing is completed. Apr 26 03:41:39 192.168.122.209 [41849.626649] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:41:39 192.168.122.209 [41849.659889] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:41:39 192.168.122.209 [41849.690304] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:41:39 192.168.122.209 [41849.775511] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:41:39 192.168.122.209 [41849.815458] [tempesta fw] Tempesta FW is ready Apr 26 03:41:49 192.168.122.209 [41859.139337] [tempesta fw] Warning: Max header name length 1024 exceeded. Apr 26 03:41:49 192.168.122.209 [41859.581815] [tdb] Close table 'client0.tdb' Apr 26 03:41:49 192.168.122.209 [41859.779373] [tdb] Close table 'sessions0.tdb' Apr 26 03:41:49 192.168.122.209 [41860.015940] [tdb] Close table 'filter0.tdb' Apr 26 03:41:49 192.168.122.209 [41860.016400] [tempesta fw] modules are stopped Apr 26 03:41:49 192.168.122.209 [41860.217698] [tempesta fw] exiting... Apr 26 03:41:50 192.168.122.209 [41860.365226] [tdb] Shutdown Tempesta DB Apr 26 03:41:50 192.168.122.209 [41860.574685] End test: http_general.test_headers.TestHeadersParsing.test_long_header_name_in_request Apr 26 03:41:50 192.168.122.209 [41860.595319] Start test: http_general.test_headers.TestHeadersParsing.test_long_header_name_in_response Apr 26 03:41:51 192.168.122.209 [41861.693125] [tdb] Start Tempesta DB Apr 26 03:41:51 192.168.122.209 [41861.860944] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:41:52 192.168.122.209 [41862.439757] [tempesta fw] Configuration processing is completed. Apr 26 03:41:52 192.168.122.209 [41862.489967] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:41:52 192.168.122.209 [41862.517637] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:41:52 192.168.122.209 [41862.545392] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:41:52 192.168.122.209 [41862.591708] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:41:52 192.168.122.209 [41862.627623] [tempesta fw] Tempesta FW is ready Apr 26 03:42:01 192.168.122.209 [41871.839447] [tempesta fw] Warning: Max header name length 1024 exceeded. Apr 26 03:42:01 192.168.122.209 [41871.839463] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 03:42:01 192.168.122.209 [41872.306171] [tdb] Close table 'client0.tdb' Apr 26 03:42:02 192.168.122.209 [41872.512386] [tdb] Close table 'sessions0.tdb' Apr 26 03:42:02 192.168.122.209 [41872.747027] [tdb] Close table 'filter0.tdb' Apr 26 03:42:02 192.168.122.209 [41872.747466] [tempesta fw] modules are stopped Apr 26 03:42:02 192.168.122.209 [41872.946385] [tempesta fw] exiting... Apr 26 03:42:02 192.168.122.209 [41873.109486] [tdb] Shutdown Tempesta DB Apr 26 03:42:02 192.168.122.209 [41873.296570] End test: http_general.test_headers.TestHeadersParsing.test_long_header_name_in_response Apr 26 03:42:02 192.168.122.209 [41873.306954] Start test: http_general.test_headers.TestHeadersParsing.test_server_in_trailers_response_empty_body Apr 26 03:42:04 192.168.122.209 [41874.441336] [tdb] Start Tempesta DB Apr 26 03:42:04 192.168.122.209 [41874.578163] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:42:04 192.168.122.209 [41875.143882] [tempesta fw] Configuration processing is completed. Apr 26 03:42:04 192.168.122.209 [41875.197930] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:42:04 192.168.122.209 [41875.230601] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:42:04 192.168.122.209 [41875.261694] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:42:04 192.168.122.209 [41875.303797] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:42:05 192.168.122.209 [41875.343812] [tempesta fw] Tempesta FW is ready Apr 26 03:42:05 192.168.122.209 [41875.468388] [tempesta fw] Warning: There is a hop-by-hop header in trailers, drop response Apr 26 03:42:05 192.168.122.209 [41875.468395] [tempesta fw] Warning: Parser error: state=Resp_HdrServerV input(-8)=0x64('Server: deproxy [41875.468395] X-Token: value [41875.468395] [41875.468395] ') data_len=101 off=74 Apr 26 03:42:05 192.168.122.209 [41875.471551] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 03:42:05 192.168.122.209 [41875.853176] [tdb] Close table 'client0.tdb' Apr 26 03:42:05 192.168.122.209 [41876.039091] [tdb] Close table 'sessions0.tdb' Apr 26 03:42:05 192.168.122.209 [41876.266257] [tdb] Close table 'filter0.tdb' Apr 26 03:42:05 192.168.122.209 [41876.266711] [tempesta fw] modules are stopped Apr 26 03:42:06 192.168.122.209 [41876.472566] [tempesta fw] exiting... Apr 26 03:42:06 192.168.122.209 [41876.625446] [tdb] Shutdown Tempesta DB Apr 26 03:42:06 192.168.122.209 [41876.847055] End test: http_general.test_headers.TestHeadersParsing.test_server_in_trailers_response_empty_body Apr 26 03:42:06 192.168.122.209 [41876.872100] Start test: http_general.test_headers.TestHeadersParsing.test_server_in_trailers_response_not_empty_body Apr 26 03:42:07 192.168.122.209 [41877.977822] [tdb] Start Tempesta DB Apr 26 03:42:07 192.168.122.209 [41878.131178] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:42:08 192.168.122.209 [41878.707908] [tempesta fw] Configuration processing is completed. Apr 26 03:42:08 192.168.122.209 [41878.760647] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:42:08 192.168.122.209 [41878.790999] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:42:08 192.168.122.209 [41878.821437] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:42:08 192.168.122.209 [41878.871834] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:42:08 192.168.122.209 [41878.911813] [tempesta fw] Tempesta FW is ready Apr 26 03:42:08 192.168.122.209 [41879.025352] [tempesta fw] Warning: There is a hop-by-hop header in trailers, drop response Apr 26 03:42:08 192.168.122.209 [41879.025359] [tempesta fw] Warning: Parser error: state=Resp_HdrServerV input(-8)=0x64('Server: deproxy [41879.025359] X-Token: value [41879.025359] [41879.025359] ') data_len=123 off=96 Apr 26 03:42:08 192.168.122.209 [41879.029220] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 03:42:09 192.168.122.209 [41879.460980] [tdb] Close table 'client0.tdb' Apr 26 03:42:09 192.168.122.209 [41879.644740] [tdb] Close table 'sessions0.tdb' Apr 26 03:42:09 192.168.122.209 [41879.867406] [tdb] Close table 'filter0.tdb' Apr 26 03:42:09 192.168.122.209 [41879.867868] [tempesta fw] modules are stopped Apr 26 03:42:09 192.168.122.209 [41880.043932] [tempesta fw] exiting... Apr 26 03:42:09 192.168.122.209 [41880.213281] [tdb] Shutdown Tempesta DB Apr 26 03:42:10 192.168.122.209 [41880.463196] End test: http_general.test_headers.TestHeadersParsing.test_server_in_trailers_response_not_empty_body Apr 26 03:42:10 192.168.122.209 [41880.474109] Start test: http_general.test_headers.TestHeadersParsing.test_trailers_in_request_trailer_GET Apr 26 03:42:11 192.168.122.209 [41881.586941] [tdb] Start Tempesta DB Apr 26 03:42:11 192.168.122.209 [41881.746870] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:42:11 192.168.122.209 [41882.311902] [tempesta fw] Configuration processing is completed. Apr 26 03:42:12 192.168.122.209 [41882.363417] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:42:12 192.168.122.209 [41882.391177] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:42:12 192.168.122.209 [41882.419206] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:42:12 192.168.122.209 [41882.467919] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:42:12 192.168.122.209 [41882.507879] [tempesta fw] Tempesta FW is ready Apr 26 03:42:12 192.168.122.209 [41883.051232] [tdb] Close table 'client0.tdb' Apr 26 03:42:12 192.168.122.209 [41883.236240] [tdb] Close table 'sessions0.tdb' Apr 26 03:42:13 192.168.122.209 [41883.453100] [tdb] Close table 'filter0.tdb' Apr 26 03:42:13 192.168.122.209 [41883.453538] net_ratelimit: 2 callbacks suppressed Apr 26 03:42:13 192.168.122.209 [41883.453540] [tempesta fw] modules are stopped Apr 26 03:42:13 192.168.122.209 [41883.656276] [tempesta fw] exiting... Apr 26 03:42:13 192.168.122.209 [41883.800353] [tdb] Shutdown Tempesta DB Apr 26 03:42:13 192.168.122.209 [41884.006146] End test: http_general.test_headers.TestHeadersParsing.test_trailers_in_request_trailer_GET Apr 26 03:42:13 192.168.122.209 [41884.021415] Start test: http_general.test_headers.TestHeadersParsing.test_trailers_in_request_trailer_HEAD Apr 26 03:42:14 192.168.122.209 [41885.115417] [tdb] Start Tempesta DB Apr 26 03:42:14 192.168.122.209 [41885.289611] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:42:15 192.168.122.209 [41885.924014] [tempesta fw] Configuration processing is completed. Apr 26 03:42:15 192.168.122.209 [41885.974533] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:42:15 192.168.122.209 [41886.002483] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:42:15 192.168.122.209 [41886.030273] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:42:15 192.168.122.209 [41886.071959] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:42:15 192.168.122.209 [41886.123918] [tempesta fw] Tempesta FW is ready Apr 26 03:42:15 192.168.122.209 [41886.258462] [tempesta fw] Warning: Content-Length or Content-Type not allowed to be used with such (overridden) method Apr 26 03:42:15 192.168.122.209 [41886.260242] [tempesta fw] Warning: Parser error: state=RGen_BodyParse input(-8)=0x31('ken2 [41886.260242] [41886.260242] 10 [41886.260242] abcdefghijklmnop [41886.260242] 0 [41886.260242] X-Token1: value') data_len=215 off=152 Apr 26 03:42:16 192.168.122.209 [41886.664371] [tdb] Close table 'client0.tdb' Apr 26 03:42:16 192.168.122.209 [41886.851197] [tdb] Close table 'sessions0.tdb' Apr 26 03:42:16 192.168.122.209 [41887.072002] [tdb] Close table 'filter0.tdb' Apr 26 03:42:16 192.168.122.209 [41887.072426] [tempesta fw] modules are stopped Apr 26 03:42:16 192.168.122.209 [41887.281798] [tempesta fw] exiting... Apr 26 03:42:17 192.168.122.209 [41887.423644] [tdb] Shutdown Tempesta DB Apr 26 03:42:17 192.168.122.209 [41887.673000] End test: http_general.test_headers.TestHeadersParsing.test_trailers_in_request_trailer_HEAD Apr 26 03:42:17 192.168.122.209 [41887.683191] Start test: http_general.test_headers.TestHeadersParsing.test_trailers_in_request_trailer_POST Apr 26 03:42:18 192.168.122.209 [41888.793310] [tdb] Start Tempesta DB Apr 26 03:42:18 192.168.122.209 [41888.938611] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:42:19 192.168.122.209 [41889.508070] [tempesta fw] Configuration processing is completed. Apr 26 03:42:19 192.168.122.209 [41889.561260] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:42:19 192.168.122.209 [41889.591729] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:42:19 192.168.122.209 [41889.622365] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:42:19 192.168.122.209 [41889.668011] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:42:19 192.168.122.209 [41889.707968] [tempesta fw] Tempesta FW is ready Apr 26 03:42:19 192.168.122.209 [41890.226073] [tdb] Close table 'client0.tdb' Apr 26 03:42:20 192.168.122.209 [41890.422457] [tdb] Close table 'sessions0.tdb' Apr 26 03:42:20 192.168.122.209 [41890.637496] [tdb] Close table 'filter0.tdb' Apr 26 03:42:20 192.168.122.209 [41890.637929] [tempesta fw] modules are stopped Apr 26 03:42:20 192.168.122.209 [41890.803010] [tempesta fw] exiting... Apr 26 03:42:20 192.168.122.209 [41890.941818] [tdb] Shutdown Tempesta DB Apr 26 03:42:20 192.168.122.209 [41891.147116] End test: http_general.test_headers.TestHeadersParsing.test_trailers_in_request_trailer_POST Apr 26 03:42:20 192.168.122.209 [41891.159758] Start test: http_general.test_headers.TestHeadersParsing.test_trailers_in_request_trailer_hbp_from_connection_POST Apr 26 03:42:21 192.168.122.209 [41892.240676] [tdb] Start Tempesta DB Apr 26 03:42:22 192.168.122.209 [41892.404440] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:42:22 192.168.122.209 [41892.952096] [tempesta fw] Configuration processing is completed. Apr 26 03:42:22 192.168.122.209 [41893.003052] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:42:22 192.168.122.209 [41893.030867] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:42:22 192.168.122.209 [41893.058603] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:42:22 192.168.122.209 [41893.104049] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:42:22 192.168.122.209 [41893.152027] [tempesta fw] Tempesta FW is ready Apr 26 03:42:22 192.168.122.209 [41893.289575] [tempesta fw] Warning: There is a hop-by-hop header in trailers, drop request Apr 26 03:42:22 192.168.122.209 [41893.289588] [tempesta fw] Warning: Parser error: state=st_curr input(-8)=0x76('eader1: value1 [41893.289588] HbpHeader2: value2 [41893.289588] [41893.289588] ') data_len=223 off=193 Apr 26 03:42:23 192.168.122.209 [41893.695337] [tdb] Close table 'client0.tdb' Apr 26 03:42:23 192.168.122.209 [41893.884090] [tdb] Close table 'sessions0.tdb' Apr 26 03:42:23 192.168.122.209 [41894.118852] [tdb] Close table 'filter0.tdb' Apr 26 03:42:23 192.168.122.209 [41894.119275] [tempesta fw] modules are stopped Apr 26 03:42:23 192.168.122.209 [41894.299232] [tempesta fw] exiting... Apr 26 03:42:24 192.168.122.209 [41894.452323] [tdb] Shutdown Tempesta DB Apr 26 03:42:24 192.168.122.209 [41894.635087] End test: http_general.test_headers.TestHeadersParsing.test_trailers_in_request_trailer_hbp_from_connection_POST Apr 26 03:42:24 192.168.122.209 [41894.655213] Start test: http_general.test_headers.TestHeadersParsing.test_trailers_in_request_trailer_mix_POST_keep_alive Apr 26 03:42:25 192.168.122.209 [41895.735133] [tdb] Start Tempesta DB Apr 26 03:42:25 192.168.122.209 [41895.876274] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:42:26 192.168.122.209 [41896.440121] [tempesta fw] Configuration processing is completed. Apr 26 03:42:26 192.168.122.209 [41896.501622] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:42:26 192.168.122.209 [41896.529096] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:42:26 192.168.122.209 [41896.557113] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:42:26 192.168.122.209 [41896.596092] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:42:26 192.168.122.209 [41896.640039] [tempesta fw] Tempesta FW is ready Apr 26 03:42:26 192.168.122.209 [41896.773150] [tempesta fw] Warning: There is a hop-by-hop header in trailers, drop request Apr 26 03:42:26 192.168.122.209 [41896.773158] [tempesta fw] Warning: Parser error: state=Req_HdrKeep_AliveV input(-8)=0x74('-Alive: timeout=5, max=20 [41896.773158] [41896.773158] ') data_len=230 off=209 Apr 26 03:42:26 192.168.122.209 [41897.204793] [tdb] Close table 'client0.tdb' Apr 26 03:42:27 192.168.122.209 [41897.395088] [tdb] Close table 'sessions0.tdb' Apr 26 03:42:27 192.168.122.209 [41897.619708] [tdb] Close table 'filter0.tdb' Apr 26 03:42:27 192.168.122.209 [41897.620490] [tempesta fw] modules are stopped Apr 26 03:42:27 192.168.122.209 [41897.794306] [tempesta fw] exiting... Apr 26 03:42:27 192.168.122.209 [41897.930969] [tdb] Shutdown Tempesta DB Apr 26 03:42:27 192.168.122.209 [41898.160792] End test: http_general.test_headers.TestHeadersParsing.test_trailers_in_request_trailer_mix_POST_keep_alive Apr 26 03:42:27 192.168.122.209 [41898.181532] Start test: http_general.test_headers.TestHeadersParsing.test_trailers_in_request_trailer_mix_POST_transfer_encoding Apr 26 03:42:28 192.168.122.209 [41899.220856] [tdb] Start Tempesta DB Apr 26 03:42:29 192.168.122.209 [41899.361450] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:42:29 192.168.122.209 [41899.968191] [tempesta fw] Configuration processing is completed. Apr 26 03:42:29 192.168.122.209 [41900.018098] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:42:29 192.168.122.209 [41900.045731] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:42:29 192.168.122.209 [41900.073401] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:42:29 192.168.122.209 [41900.124173] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:42:29 192.168.122.209 [41900.164092] [tempesta fw] Tempesta FW is ready Apr 26 03:42:29 192.168.122.209 [41900.312466] [tempesta fw] Warning: Parser error: state=Req_HdrTransfer_EncodingV input(-8)=0x63('coding: chunked [41900.312466] [41900.312466] ') data_len=234 off=223 Apr 26 03:42:30 192.168.122.209 [41900.711900] [tdb] Close table 'client0.tdb' Apr 26 03:42:30 192.168.122.209 [41900.901242] [tdb] Close table 'sessions0.tdb' Apr 26 03:42:30 192.168.122.209 [41901.133326] [tdb] Close table 'filter0.tdb' Apr 26 03:42:30 192.168.122.209 [41901.133783] [tempesta fw] modules are stopped Apr 26 03:42:30 192.168.122.209 [41901.329171] [tempesta fw] exiting... Apr 26 03:42:31 192.168.122.209 [41901.467911] [tdb] Shutdown Tempesta DB Apr 26 03:42:31 192.168.122.209 [41901.690185] End test: http_general.test_headers.TestHeadersParsing.test_trailers_in_request_trailer_mix_POST_transfer_encoding Apr 26 03:42:31 192.168.122.209 [41901.699104] Start test: http_general.test_headers.TestHeadersParsing.test_trailers_in_request_trailer_mix_POST_upgrade Apr 26 03:42:32 192.168.122.209 [41902.790687] [tdb] Start Tempesta DB Apr 26 03:42:32 192.168.122.209 [41902.931979] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:42:33 192.168.122.209 [41903.488249] [tempesta fw] Configuration processing is completed. Apr 26 03:42:33 192.168.122.209 [41903.538152] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:42:33 192.168.122.209 [41903.568011] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:42:33 192.168.122.209 [41903.595834] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:42:33 192.168.122.209 [41903.636224] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:42:33 192.168.122.209 [41903.684142] [tempesta fw] Tempesta FW is ready Apr 26 03:42:33 192.168.122.209 [41903.812188] [tempesta fw] Warning: Parser error: state=Req_HdrUpgradeV input(-8)=0x77('pgrade: websocket [41903.812188] [41903.812188] ') data_len=216 off=203 Apr 26 03:42:33 192.168.122.209 [41904.216066] [tdb] Close table 'client0.tdb' Apr 26 03:42:34 192.168.122.209 [41904.398700] [tdb] Close table 'sessions0.tdb' Apr 26 03:42:34 192.168.122.209 [41904.628462] [tdb] Close table 'filter0.tdb' Apr 26 03:42:34 192.168.122.209 [41904.628890] [tempesta fw] modules are stopped Apr 26 03:42:34 192.168.122.209 [41904.792759] [tempesta fw] exiting... Apr 26 03:42:34 192.168.122.209 [41904.922499] [tdb] Shutdown Tempesta DB Apr 26 03:42:34 192.168.122.209 [41905.140600] End test: http_general.test_headers.TestHeadersParsing.test_trailers_in_request_trailer_mix_POST_upgrade Apr 26 03:42:34 192.168.122.209 [41905.147499] Start test: http_general.test_headers.TestHeadersParsing.test_trailers_in_response_get_hbp_GET Apr 26 03:42:35 192.168.122.209 [41906.244580] [tdb] Start Tempesta DB Apr 26 03:42:36 192.168.122.209 [41906.398163] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:42:36 192.168.122.209 [41906.980382] [tempesta fw] Configuration processing is completed. Apr 26 03:42:36 192.168.122.209 [41907.029776] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:42:36 192.168.122.209 [41907.057559] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:42:36 192.168.122.209 [41907.085970] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:42:36 192.168.122.209 [41907.132230] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:42:36 192.168.122.209 [41907.176170] [tempesta fw] Tempesta FW is ready Apr 26 03:42:36 192.168.122.209 [41907.305159] [tempesta fw] Warning: Parser error: state=Resp_HdrConnectionV input(-8)=0x6b('ection: keep-alive [41907.305159] Keep-Alive: timeout=5, max=1') data_len=329 off=283 Apr 26 03:42:36 192.168.122.209 [41907.306632] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 03:42:37 192.168.122.209 [41907.719621] [tdb] Close table 'client0.tdb' Apr 26 03:42:37 192.168.122.209 [41907.914553] [tdb] Close table 'sessions0.tdb' Apr 26 03:42:37 192.168.122.209 [41908.151652] [tdb] Close table 'filter0.tdb' Apr 26 03:42:37 192.168.122.209 [41908.152458] [tempesta fw] modules are stopped Apr 26 03:42:38 192.168.122.209 [41908.334410] [tempesta fw] exiting... Apr 26 03:42:38 192.168.122.209 [41908.468996] [tdb] Shutdown Tempesta DB Apr 26 03:42:38 192.168.122.209 [41908.669125] End test: http_general.test_headers.TestHeadersParsing.test_trailers_in_response_get_hbp_GET Apr 26 03:42:38 192.168.122.209 [41908.680754] Start test: http_general.test_headers.TestHeadersParsing.test_trailers_in_response_get_hbp_from_connection_GET Apr 26 03:42:39 192.168.122.209 [41909.766598] [tdb] Start Tempesta DB Apr 26 03:42:39 192.168.122.209 [41909.914431] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:42:40 192.168.122.209 [41910.460300] [tempesta fw] Configuration processing is completed. Apr 26 03:42:40 192.168.122.209 [41910.510467] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:42:40 192.168.122.209 [41910.537757] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:42:40 192.168.122.209 [41910.565232] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:42:40 192.168.122.209 [41910.624278] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:42:40 192.168.122.209 [41910.668223] [tempesta fw] Tempesta FW is ready Apr 26 03:42:40 192.168.122.209 [41910.789120] [tempesta fw] Warning: There is a hop-by-hop header in trailers, drop response Apr 26 03:42:40 192.168.122.209 [41910.789133] [tempesta fw] Warning: Parser error: state=st_curr input(-8)=0x76('eader1: value1 [41910.789133] HbpHeader2: value2 [41910.789133] [41910.789133] ') data_len=313 off=283 Apr 26 03:42:40 192.168.122.209 [41910.795460] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 03:42:40 192.168.122.209 [41911.223281] [tdb] Close table 'client0.tdb' Apr 26 03:42:41 192.168.122.209 [41911.412824] [tdb] Close table 'sessions0.tdb' Apr 26 03:42:41 192.168.122.209 [41911.651416] [tdb] Close table 'filter0.tdb' Apr 26 03:42:41 192.168.122.209 [41911.651867] [tempesta fw] modules are stopped Apr 26 03:42:41 192.168.122.209 [41911.816808] [tempesta fw] exiting... Apr 26 03:42:41 192.168.122.209 [41911.963521] [tdb] Shutdown Tempesta DB Apr 26 03:42:41 192.168.122.209 [41912.201952] End test: http_general.test_headers.TestHeadersParsing.test_trailers_in_response_get_hbp_from_connection_GET Apr 26 03:42:41 192.168.122.209 [41912.213034] Start test: http_general.test_headers.TestHeadersParsing.test_trailers_in_response_get_mix_GET_keep_alive Apr 26 03:42:42 192.168.122.209 [41913.310733] [tdb] Start Tempesta DB Apr 26 03:42:43 192.168.122.209 [41913.459987] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:42:43 192.168.122.209 [41914.052360] [tempesta fw] Configuration processing is completed. Apr 26 03:42:43 192.168.122.209 [41914.103831] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:42:43 192.168.122.209 [41914.133974] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:42:43 192.168.122.209 [41914.162862] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:42:43 192.168.122.209 [41914.200322] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:42:43 192.168.122.209 [41914.244259] [tempesta fw] Tempesta FW is ready Apr 26 03:42:44 192.168.122.209 [41914.757935] [tdb] Close table 'client0.tdb' Apr 26 03:42:44 192.168.122.209 [41914.946374] [tdb] Close table 'sessions0.tdb' Apr 26 03:42:44 192.168.122.209 [41915.168530] [tdb] Close table 'filter0.tdb' Apr 26 03:42:44 192.168.122.209 [41915.168984] net_ratelimit: 2 callbacks suppressed Apr 26 03:42:44 192.168.122.209 [41915.168985] [tempesta fw] modules are stopped Apr 26 03:42:45 192.168.122.209 [41915.350373] [tempesta fw] exiting... Apr 26 03:42:45 192.168.122.209 [41915.497783] [tdb] Shutdown Tempesta DB Apr 26 03:42:45 192.168.122.209 [41915.682150] End test: http_general.test_headers.TestHeadersParsing.test_trailers_in_response_get_mix_GET_keep_alive Apr 26 03:42:45 192.168.122.209 [41915.696097] Start test: http_general.test_headers.TestHeadersParsing.test_trailers_in_response_get_mix_GET_proxy_connection Apr 26 03:42:46 192.168.122.209 [41916.746358] [tdb] Start Tempesta DB Apr 26 03:42:46 192.168.122.209 [41916.887909] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:42:47 192.168.122.209 [41917.428562] [tempesta fw] Configuration processing is completed. Apr 26 03:42:47 192.168.122.209 [41917.490845] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:42:47 192.168.122.209 [41917.518651] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:42:47 192.168.122.209 [41917.546332] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:42:47 192.168.122.209 [41917.584370] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:42:47 192.168.122.209 [41917.636311] [tempesta fw] Tempesta FW is ready Apr 26 03:42:47 192.168.122.209 [41917.744774] [tempesta fw] Warning: There is a hop-by-hop header in trailers, drop response Apr 26 03:42:47 192.168.122.209 [41917.744788] [tempesta fw] Warning: Parser error: state=st_curr input(-8)=0x6b('ection: keep-alive [41917.744788] [41917.744788] ') data_len=325 off=311 Apr 26 03:42:47 192.168.122.209 [41917.750860] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 03:42:47 192.168.122.209 [41918.126530] [tdb] Close table 'client0.tdb' Apr 26 03:42:47 192.168.122.209 [41918.327167] [tdb] Close table 'sessions0.tdb' Apr 26 03:42:48 192.168.122.209 [41918.536615] [tdb] Close table 'filter0.tdb' Apr 26 03:42:48 192.168.122.209 [41918.537047] [tempesta fw] modules are stopped Apr 26 03:42:48 192.168.122.209 [41918.735814] [tempesta fw] exiting... Apr 26 03:42:48 192.168.122.209 [41918.896339] [tdb] Shutdown Tempesta DB Apr 26 03:42:48 192.168.122.209 [41919.111148] End test: http_general.test_headers.TestHeadersParsing.test_trailers_in_response_get_mix_GET_proxy_connection Apr 26 03:42:48 192.168.122.209 [41919.126221] Start test: http_general.test_headers.TestHeadersParsing.test_trailers_in_response_get_mix_GET_transfer_encoding Apr 26 03:42:49 192.168.122.209 [41920.195695] [tdb] Start Tempesta DB Apr 26 03:42:49 192.168.122.209 [41920.330650] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:42:50 192.168.122.209 [41920.936467] [tempesta fw] Configuration processing is completed. Apr 26 03:42:50 192.168.122.209 [41920.990225] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:42:50 192.168.122.209 [41921.017584] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:42:50 192.168.122.209 [41921.045207] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:42:50 192.168.122.209 [41921.092406] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:42:50 192.168.122.209 [41921.152377] [tempesta fw] Tempesta FW is ready Apr 26 03:42:50 192.168.122.209 [41921.271774] [tempesta fw] Warning: Parser error: state=Resp_HdrTransfer_EncodingV input(-8)=0x63('coding: chunked [41921.271774] [41921.271774] ') data_len=324 off=313 Apr 26 03:42:50 192.168.122.209 [41921.273602] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 03:42:51 192.168.122.209 [41921.674114] [tdb] Close table 'client0.tdb' Apr 26 03:42:51 192.168.122.209 [41921.858432] [tdb] Close table 'sessions0.tdb' Apr 26 03:42:51 192.168.122.209 [41922.095414] [tdb] Close table 'filter0.tdb' Apr 26 03:42:51 192.168.122.209 [41922.095848] [tempesta fw] modules are stopped Apr 26 03:42:51 192.168.122.209 [41922.281925] [tempesta fw] exiting... Apr 26 03:42:52 192.168.122.209 [41922.434662] [tdb] Shutdown Tempesta DB Apr 26 03:42:52 192.168.122.209 [41922.630126] End test: http_general.test_headers.TestHeadersParsing.test_trailers_in_response_get_mix_GET_transfer_encoding Apr 26 03:42:52 192.168.122.209 [41922.639717] Start test: http_general.test_headers.TestHeadersParsing.test_trailers_in_response_get_mix_GET_upgrade Apr 26 03:42:53 192.168.122.209 [41923.724513] [tdb] Start Tempesta DB Apr 26 03:42:53 192.168.122.209 [41923.869686] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:42:54 192.168.122.209 [41924.424524] [tempesta fw] Configuration processing is completed. Apr 26 03:42:54 192.168.122.209 [41924.476072] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:42:54 192.168.122.209 [41924.506322] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:42:54 192.168.122.209 [41924.533940] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:42:54 192.168.122.209 [41924.608444] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:42:54 192.168.122.209 [41924.668390] [tempesta fw] Tempesta FW is ready Apr 26 03:42:54 192.168.122.209 [41924.800162] [tempesta fw] Warning: Parser error: state=Resp_HdrUpgradeV input(-8)=0x77('pgrade: websocket [41924.800162] [41924.800162] ') data_len=306 off=293 Apr 26 03:42:54 192.168.122.209 [41925.255324] [tdb] Close table 'client0.tdb' Apr 26 03:42:55 192.168.122.209 [41925.438861] [tdb] Close table 'sessions0.tdb' Apr 26 03:42:55 192.168.122.209 [41925.678831] [tdb] Close table 'filter0.tdb' Apr 26 03:42:55 192.168.122.209 [41925.679268] net_ratelimit: 1 callbacks suppressed Apr 26 03:42:55 192.168.122.209 [41925.679269] [tempesta fw] modules are stopped Apr 26 03:42:55 192.168.122.209 [41925.876216] [tempesta fw] exiting... Apr 26 03:42:55 192.168.122.209 [41926.008562] [tdb] Shutdown Tempesta DB Apr 26 03:42:55 192.168.122.209 [41926.229636] End test: http_general.test_headers.TestHeadersParsing.test_trailers_in_response_get_mix_GET_upgrade Apr 26 03:42:55 192.168.122.209 [41926.244403] Start test: http_general.test_headers.TestHeadersParsing.test_trailers_in_response_get_no_hbp_GET Apr 26 03:42:57 192.168.122.209 [41927.378161] [tdb] Start Tempesta DB Apr 26 03:42:57 192.168.122.209 [41927.522155] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:42:57 192.168.122.209 [41928.120528] [tempesta fw] Configuration processing is completed. Apr 26 03:42:57 192.168.122.209 [41928.170965] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:42:57 192.168.122.209 [41928.198542] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:42:57 192.168.122.209 [41928.226074] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:42:57 192.168.122.209 [41928.276506] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:42:57 192.168.122.209 [41928.320435] [tempesta fw] Tempesta FW is ready Apr 26 03:42:58 192.168.122.209 [41928.881567] [tdb] Close table 'client0.tdb' Apr 26 03:42:58 192.168.122.209 [41929.070345] [tdb] Close table 'sessions0.tdb' Apr 26 03:42:58 192.168.122.209 [41929.300984] [tdb] Close table 'filter0.tdb' Apr 26 03:42:58 192.168.122.209 [41929.301436] [tempesta fw] modules are stopped Apr 26 03:42:59 192.168.122.209 [41929.462197] [tempesta fw] exiting... Apr 26 03:42:59 192.168.122.209 [41929.571767] [tdb] Shutdown Tempesta DB Apr 26 03:42:59 192.168.122.209 [41929.775270] End test: http_general.test_headers.TestHeadersParsing.test_trailers_in_response_get_no_hbp_GET Apr 26 03:42:59 192.168.122.209 [41929.790065] Start test: http_general.test_headers.TestHeadersParsing.test_trailers_in_response_head_hbp_HEAD Apr 26 03:43:00 192.168.122.209 [41930.920750] [tdb] Start Tempesta DB Apr 26 03:43:00 192.168.122.209 [41931.064877] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:43:01 192.168.122.209 [41931.624606] [tempesta fw] Configuration processing is completed. Apr 26 03:43:01 192.168.122.209 [41931.674177] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:43:01 192.168.122.209 [41931.701654] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:43:01 192.168.122.209 [41931.729058] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:43:01 192.168.122.209 [41931.780562] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:43:01 192.168.122.209 [41931.820494] [tempesta fw] Tempesta FW is ready Apr 26 03:43:02 192.168.122.209 [41932.343071] [tdb] Close table 'client0.tdb' Apr 26 03:43:02 192.168.122.209 [41932.532620] [tdb] Close table 'sessions0.tdb' Apr 26 03:43:02 192.168.122.209 [41932.765372] [tdb] Close table 'filter0.tdb' Apr 26 03:43:02 192.168.122.209 [41932.765805] [tempesta fw] modules are stopped Apr 26 03:43:02 192.168.122.209 [41932.937641] [tempesta fw] exiting... Apr 26 03:43:02 192.168.122.209 [41933.072531] [tdb] Shutdown Tempesta DB Apr 26 03:43:02 192.168.122.209 [41933.273777] End test: http_general.test_headers.TestHeadersParsing.test_trailers_in_response_head_hbp_HEAD Apr 26 03:43:02 192.168.122.209 [41933.282077] Start test: http_general.test_headers.TestHeadersParsing.test_trailers_in_response_head_hbp_from_connection_HEAD Apr 26 03:43:04 192.168.122.209 [41934.378816] [tdb] Start Tempesta DB Apr 26 03:43:04 192.168.122.209 [41934.532589] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:43:04 192.168.122.209 [41935.076637] [tempesta fw] Configuration processing is completed. Apr 26 03:43:04 192.168.122.209 [41935.136535] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:43:04 192.168.122.209 [41935.169218] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:43:04 192.168.122.209 [41935.198323] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:43:04 192.168.122.209 [41935.240584] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:43:04 192.168.122.209 [41935.284527] [tempesta fw] Tempesta FW is ready Apr 26 03:43:05 192.168.122.209 [41935.839134] [tdb] Close table 'client0.tdb' Apr 26 03:43:05 192.168.122.209 [41936.025392] [tdb] Close table 'sessions0.tdb' Apr 26 03:43:05 192.168.122.209 [41936.235684] [tdb] Close table 'filter0.tdb' Apr 26 03:43:05 192.168.122.209 [41936.236137] [tempesta fw] modules are stopped Apr 26 03:43:06 192.168.122.209 [41936.419735] [tempesta fw] exiting... Apr 26 03:43:06 192.168.122.209 [41936.579184] [tdb] Shutdown Tempesta DB Apr 26 03:43:06 192.168.122.209 [41936.801602] End test: http_general.test_headers.TestHeadersParsing.test_trailers_in_response_head_hbp_from_connection_HEAD Apr 26 03:43:06 192.168.122.209 [41936.813066] Start test: http_general.test_headers.TestHeadersParsing.test_trailers_in_response_head_mix_HEAD Apr 26 03:43:07 192.168.122.209 [41937.944294] [tdb] Start Tempesta DB Apr 26 03:43:07 192.168.122.209 [41938.095781] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:43:08 192.168.122.209 [41938.656667] [tempesta fw] Configuration processing is completed. Apr 26 03:43:08 192.168.122.209 [41938.710246] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:43:08 192.168.122.209 [41938.738053] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:43:08 192.168.122.209 [41938.765318] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:43:08 192.168.122.209 [41938.816642] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:43:08 192.168.122.209 [41938.856567] [tempesta fw] Tempesta FW is ready Apr 26 03:43:09 192.168.122.209 [41939.379104] [tdb] Close table 'client0.tdb' Apr 26 03:43:09 192.168.122.209 [41939.563015] [tdb] Close table 'sessions0.tdb' Apr 26 03:43:09 192.168.122.209 [41939.790777] [tdb] Close table 'filter0.tdb' Apr 26 03:43:09 192.168.122.209 [41939.791226] [tempesta fw] modules are stopped Apr 26 03:43:09 192.168.122.209 [41939.977395] [tempesta fw] exiting... Apr 26 03:43:09 192.168.122.209 [41940.130894] [tdb] Shutdown Tempesta DB Apr 26 03:43:10 192.168.122.209 [41940.371923] End test: http_general.test_headers.TestHeadersParsing.test_trailers_in_response_head_mix_HEAD Apr 26 03:43:10 192.168.122.209 [41940.387562] Start test: http_general.test_headers.TestHeadersParsing.test_trailers_in_response_head_no_hbp_HEAD Apr 26 03:43:11 192.168.122.209 [41941.395886] [tdb] Start Tempesta DB Apr 26 03:43:11 192.168.122.209 [41941.536529] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:43:11 192.168.122.209 [41942.140690] [tempesta fw] Configuration processing is completed. Apr 26 03:43:11 192.168.122.209 [41942.194580] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:43:11 192.168.122.209 [41942.222475] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:43:11 192.168.122.209 [41942.250133] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:43:11 192.168.122.209 [41942.304680] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:43:12 192.168.122.209 [41942.368626] [tempesta fw] Tempesta FW is ready Apr 26 03:43:12 192.168.122.209 [41942.933264] [tdb] Close table 'client0.tdb' Apr 26 03:43:12 192.168.122.209 [41943.121498] [tdb] Close table 'sessions0.tdb' Apr 26 03:43:13 192.168.122.209 [41943.361645] [tdb] Close table 'filter0.tdb' Apr 26 03:43:13 192.168.122.209 [41943.362086] [tempesta fw] modules are stopped Apr 26 03:43:13 192.168.122.209 [41943.564868] [tempesta fw] exiting... Apr 26 03:43:13 192.168.122.209 [41943.719168] [tdb] Shutdown Tempesta DB Apr 26 03:43:13 192.168.122.209 [41943.929830] End test: http_general.test_headers.TestHeadersParsing.test_trailers_in_response_head_no_hbp_HEAD Apr 26 03:43:13 192.168.122.209 [41943.940878] Start test: http_general.test_headers.TestHeadersParsing.test_trailers_in_response_simple_empty_body Apr 26 03:43:14 192.168.122.209 [41945.014762] [tdb] Start Tempesta DB Apr 26 03:43:14 192.168.122.209 [41945.186029] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:43:15 192.168.122.209 [41945.752745] [tempesta fw] Configuration processing is completed. Apr 26 03:43:15 192.168.122.209 [41945.803137] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:43:15 192.168.122.209 [41945.832414] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:43:15 192.168.122.209 [41945.859955] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:43:15 192.168.122.209 [41945.912716] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:43:15 192.168.122.209 [41945.956656] [tempesta fw] Tempesta FW is ready Apr 26 03:43:16 192.168.122.209 [41946.502282] [tdb] Close table 'client0.tdb' Apr 26 03:43:16 192.168.122.209 [41946.688195] [tdb] Close table 'sessions0.tdb' Apr 26 03:43:16 192.168.122.209 [41946.918522] [tdb] Close table 'filter0.tdb' Apr 26 03:43:16 192.168.122.209 [41946.918951] [tempesta fw] modules are stopped Apr 26 03:43:16 192.168.122.209 [41947.091695] [tempesta fw] exiting... Apr 26 03:43:16 192.168.122.209 [41947.226602] [tdb] Shutdown Tempesta DB Apr 26 03:43:17 192.168.122.209 [41947.440978] End test: http_general.test_headers.TestHeadersParsing.test_trailers_in_response_simple_empty_body Apr 26 03:43:17 192.168.122.209 [41947.456241] Start test: http_general.test_headers.TestHeadersParsing.test_trailers_in_response_simple_not_empty_body Apr 26 03:43:18 192.168.122.209 [41948.597083] [tdb] Start Tempesta DB Apr 26 03:43:18 192.168.122.209 [41948.752674] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:43:18 192.168.122.209 [41949.308783] [tempesta fw] Configuration processing is completed. Apr 26 03:43:19 192.168.122.209 [41949.360173] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:43:19 192.168.122.209 [41949.388070] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:43:19 192.168.122.209 [41949.415972] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:43:19 192.168.122.209 [41949.484755] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:43:19 192.168.122.209 [41949.524664] [tempesta fw] Tempesta FW is ready Apr 26 03:43:19 192.168.122.209 [41950.097952] [tdb] Close table 'client0.tdb' Apr 26 03:43:19 192.168.122.209 [41950.278478] [tdb] Close table 'sessions0.tdb' Apr 26 03:43:20 192.168.122.209 [41950.507613] [tdb] Close table 'filter0.tdb' Apr 26 03:43:20 192.168.122.209 [41950.508043] [tempesta fw] modules are stopped Apr 26 03:43:20 192.168.122.209 [41950.724753] [tempesta fw] exiting... Apr 26 03:43:20 192.168.122.209 [41950.864658] [tdb] Shutdown Tempesta DB Apr 26 03:43:20 192.168.122.209 [41951.083076] End test: http_general.test_headers.TestHeadersParsing.test_trailers_in_response_simple_not_empty_body Apr 26 03:43:20 192.168.122.209 [41951.093226] Start test: http_general.test_headers.TestHeadersParsing.test_without_trailers_in_request Apr 26 03:43:21 192.168.122.209 [41952.147869] [tdb] Start Tempesta DB Apr 26 03:43:21 192.168.122.209 [41952.303233] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:43:22 192.168.122.209 [41952.872747] [tempesta fw] Configuration processing is completed. Apr 26 03:43:22 192.168.122.209 [41952.922772] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:43:22 192.168.122.209 [41952.950426] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:43:22 192.168.122.209 [41952.978234] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:43:22 192.168.122.209 [41953.040796] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:43:22 192.168.122.209 [41953.084747] [tempesta fw] Tempesta FW is ready Apr 26 03:43:23 192.168.122.209 [41953.654631] [tdb] Close table 'client0.tdb' Apr 26 03:43:23 192.168.122.209 [41953.847197] [tdb] Close table 'sessions0.tdb' Apr 26 03:43:23 192.168.122.209 [41954.060402] [tdb] Close table 'filter0.tdb' Apr 26 03:43:23 192.168.122.209 [41954.061202] [tempesta fw] modules are stopped Apr 26 03:43:23 192.168.122.209 [41954.221444] [tempesta fw] exiting... Apr 26 03:43:24 192.168.122.209 [41954.378187] [tdb] Shutdown Tempesta DB Apr 26 03:43:24 192.168.122.209 [41954.596127] End test: http_general.test_headers.TestHeadersParsing.test_without_trailers_in_request Apr 26 03:43:24 192.168.122.209 [41954.605989] Start test: http_general.test_headers.TestHost.test_forward_absolute_uri_default_path Apr 26 03:43:25 192.168.122.209 [41955.648802] [tdb] Start Tempesta DB Apr 26 03:43:25 192.168.122.209 [41955.796500] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:43:25 192.168.122.209 [41956.312904] [tempesta fw] Configuration processing is completed. Apr 26 03:43:26 192.168.122.209 [41956.379253] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:43:26 192.168.122.209 [41956.991738] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:43:26 192.168.122.209 [41957.065193] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:43:26 192.168.122.209 [41957.108505] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:43:26 192.168.122.209 [41957.152863] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:43:26 192.168.122.209 [41957.208796] [tempesta fw] Tempesta FW is ready Apr 26 03:43:27 192.168.122.209 [41957.757260] [tdb] Close table 'client0.tdb' Apr 26 03:43:27 192.168.122.209 [41957.941708] [tdb] Close table 'sessions0.tdb' Apr 26 03:43:30 192.168.122.209 [41961.089927] [tdb] Close table 'cache0.tdb' Apr 26 03:43:30 192.168.122.209 [41961.330226] [tdb] Close table 'filter0.tdb' Apr 26 03:43:30 192.168.122.209 [41961.330652] [tempesta fw] modules are stopped Apr 26 03:43:31 192.168.122.209 [41961.552506] [tempesta fw] exiting... Apr 26 03:43:31 192.168.122.209 [41961.685156] [tdb] Shutdown Tempesta DB Apr 26 03:43:31 192.168.122.209 [41961.886005] End test: http_general.test_headers.TestHost.test_forward_absolute_uri_default_path Apr 26 03:43:31 192.168.122.209 [41961.894661] Start test: http_general.test_headers.TestHost.test_forward_absolute_uri_empty_path Apr 26 03:43:32 192.168.122.209 [41963.022552] [tdb] Start Tempesta DB Apr 26 03:43:32 192.168.122.209 [41963.165426] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:43:34 192.168.122.209 [41964.544929] [tempesta fw] Configuration processing is completed. Apr 26 03:43:34 192.168.122.209 [41964.599498] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:43:34 192.168.122.209 [41965.011922] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:43:34 192.168.122.209 [41965.037979] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:43:34 192.168.122.209 [41965.064956] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:43:34 192.168.122.209 [41965.128950] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:43:34 192.168.122.209 [41965.172915] [tempesta fw] Tempesta FW is ready Apr 26 03:43:35 192.168.122.209 [41965.771790] [tdb] Close table 'client0.tdb' Apr 26 03:43:35 192.168.122.209 [41965.962552] [tdb] Close table 'sessions0.tdb' Apr 26 03:43:38 192.168.122.209 [41969.105730] [tdb] Close table 'cache0.tdb' Apr 26 03:43:39 192.168.122.209 [41969.334988] [tdb] Close table 'filter0.tdb' Apr 26 03:43:39 192.168.122.209 [41969.335428] [tempesta fw] modules are stopped Apr 26 03:43:39 192.168.122.209 [41969.504871] [tempesta fw] exiting... Apr 26 03:43:39 192.168.122.209 [41969.672248] [tdb] Shutdown Tempesta DB Apr 26 03:43:39 192.168.122.209 [41969.895943] End test: http_general.test_headers.TestHost.test_forward_absolute_uri_empty_path Apr 26 03:43:39 192.168.122.209 [41969.905409] Start test: http_general.test_headers.TestHost.test_forward_absolute_uri_full_path Apr 26 03:43:40 192.168.122.209 [41971.065905] [tdb] Start Tempesta DB Apr 26 03:43:40 192.168.122.209 [41971.216660] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:43:42 192.168.122.209 [41972.541441] [tempesta fw] Configuration processing is completed. Apr 26 03:43:42 192.168.122.209 [41972.633121] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:43:42 192.168.122.209 [41973.051834] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:43:42 192.168.122.209 [41973.077803] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:43:42 192.168.122.209 [41973.104886] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:43:42 192.168.122.209 [41973.149071] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:43:42 192.168.122.209 [41973.201038] [tempesta fw] Tempesta FW is ready Apr 26 03:43:43 192.168.122.209 [41973.791432] [tdb] Close table 'client0.tdb' Apr 26 03:43:43 192.168.122.209 [41973.982647] [tdb] Close table 'sessions0.tdb' Apr 26 03:43:46 192.168.122.209 [41977.167763] [tdb] Close table 'cache0.tdb' Apr 26 03:43:47 192.168.122.209 [41977.418256] [tdb] Close table 'filter0.tdb' Apr 26 03:43:47 192.168.122.209 [41977.418704] [tempesta fw] modules are stopped Apr 26 03:43:47 192.168.122.209 [41977.579330] [tempesta fw] exiting... Apr 26 03:43:47 192.168.122.209 [41977.734205] [tdb] Shutdown Tempesta DB Apr 26 03:43:47 192.168.122.209 [41977.934223] End test: http_general.test_headers.TestHost.test_forward_absolute_uri_full_path Apr 26 03:43:47 192.168.122.209 [41977.954263] Start test: http_general.test_headers.TestHost.test_forwarded_and_empty_host_header Apr 26 03:43:48 192.168.122.209 [41979.089260] [tdb] Start Tempesta DB Apr 26 03:43:48 192.168.122.209 [41979.230120] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:43:50 192.168.122.209 [41980.581497] [tempesta fw] Configuration processing is completed. Apr 26 03:43:50 192.168.122.209 [41980.631573] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:43:50 192.168.122.209 [41981.040218] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:43:50 192.168.122.209 [41981.066350] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:43:50 192.168.122.209 [41981.091516] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:43:50 192.168.122.209 [41981.137158] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:43:50 192.168.122.209 [41981.181105] [tempesta fw] Tempesta FW is ready Apr 26 03:43:50 192.168.122.209 [41981.297685] [tempesta fw] Warning: Invalid authority: 127.0.0.2 Apr 26 03:43:51 192.168.122.209 [41981.779709] [tdb] Close table 'client0.tdb' Apr 26 03:43:51 192.168.122.209 [41981.972670] [tdb] Close table 'sessions0.tdb' Apr 26 03:43:55 192.168.122.209 [41986.163252] [tdb] Close table 'cache0.tdb' Apr 26 03:43:56 192.168.122.209 [41986.967400] [tdb] Close table 'filter0.tdb' Apr 26 03:43:56 192.168.122.209 [41986.967840] [tempesta fw] modules are stopped Apr 26 03:43:57 192.168.122.209 [41988.332760] [tempesta fw] exiting... Apr 26 03:43:58 192.168.122.209 [41988.778037] [tdb] Shutdown Tempesta DB Apr 26 03:43:59 192.168.122.209 [41989.449866] kmemleak: 27 new suspected memory leaks (see /sys/kernel/debug/kmemleak) Apr 26 03:43:59 192.168.122.209 [41989.586902] End test: http_general.test_headers.TestHost.test_forwarded_and_empty_host_header Apr 26 03:43:59 192.168.122.209 [41989.600699] Start test: http_general.test_headers.TestHost.test_host_header_empty Apr 26 03:44:00 192.168.122.209 [41990.760551] [tdb] Start Tempesta DB Apr 26 03:44:00 192.168.122.209 [41990.908643] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:44:01 192.168.122.209 [41992.273339] [tempesta fw] Configuration processing is completed. Apr 26 03:44:02 192.168.122.209 [41992.335701] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:44:02 192.168.122.209 [41992.758517] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:44:02 192.168.122.209 [41992.793759] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:44:02 192.168.122.209 [41992.820487] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:44:02 192.168.122.209 [41992.869298] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:44:02 192.168.122.209 [41992.913244] [tempesta fw] Tempesta FW is ready Apr 26 03:44:02 192.168.122.209 [41993.054653] [tempesta fw] Warning: Invalid authority: 127.0.0.2 Apr 26 03:44:03 192.168.122.209 [41993.506780] [tdb] Close table 'client0.tdb' Apr 26 03:44:03 192.168.122.209 [41993.712815] [tdb] Close table 'sessions0.tdb' Apr 26 03:44:06 192.168.122.209 [41996.835356] [tdb] Close table 'cache0.tdb' Apr 26 03:44:06 192.168.122.209 [41997.057019] [tdb] Close table 'filter0.tdb' Apr 26 03:44:06 192.168.122.209 [41997.057471] [tempesta fw] modules are stopped Apr 26 03:44:06 192.168.122.209 [41997.250750] [tempesta fw] exiting... Apr 26 03:44:07 192.168.122.209 [41997.415002] [tdb] Shutdown Tempesta DB Apr 26 03:44:07 192.168.122.209 [41997.620203] End test: http_general.test_headers.TestHost.test_host_header_empty Apr 26 03:44:07 192.168.122.209 [41997.634080] Start test: http_general.test_headers.TestHost.test_host_header_ok Apr 26 03:44:08 192.168.122.209 [41998.812028] [tdb] Start Tempesta DB Apr 26 03:44:08 192.168.122.209 [41998.958296] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:44:09 192.168.122.209 [42000.309484] [tempesta fw] Configuration processing is completed. Apr 26 03:44:10 192.168.122.209 [42000.363497] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:44:10 192.168.122.209 [42000.767072] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:44:10 192.168.122.209 [42000.792413] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:44:10 192.168.122.209 [42000.817510] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:44:10 192.168.122.209 [42000.857400] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:44:10 192.168.122.209 [42000.901344] [tempesta fw] Tempesta FW is ready Apr 26 03:44:11 192.168.122.209 [42001.525251] [tdb] Close table 'client0.tdb' Apr 26 03:44:11 192.168.122.209 [42001.726936] [tdb] Close table 'sessions0.tdb' Apr 26 03:44:14 192.168.122.209 [42004.886137] [tdb] Close table 'cache0.tdb' Apr 26 03:44:14 192.168.122.209 [42005.105458] [tdb] Close table 'filter0.tdb' Apr 26 03:44:14 192.168.122.209 [42005.105893] [tempesta fw] modules are stopped Apr 26 03:44:14 192.168.122.209 [42005.310458] [tempesta fw] exiting... Apr 26 03:44:15 192.168.122.209 [42005.447712] [tdb] Shutdown Tempesta DB Apr 26 03:44:15 192.168.122.209 [42005.681887] End test: http_general.test_headers.TestHost.test_host_header_ok Apr 26 03:44:15 192.168.122.209 [42005.697079] Start test: http_general.test_headers.TestHost.test_host_in_uri_without_host_header Apr 26 03:44:16 192.168.122.209 [42006.893445] [tdb] Start Tempesta DB Apr 26 03:44:16 192.168.122.209 [42007.055816] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:44:18 192.168.122.209 [42008.365567] [tempesta fw] Configuration processing is completed. Apr 26 03:44:18 192.168.122.209 [42008.452888] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:44:18 192.168.122.209 [42008.868583] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:44:18 192.168.122.209 [42008.894401] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:44:18 192.168.122.209 [42008.920824] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:44:18 192.168.122.209 [42008.961461] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:44:18 192.168.122.209 [42009.013446] [tempesta fw] Tempesta FW is ready Apr 26 03:44:18 192.168.122.209 [42009.149802] [tempesta fw] Warning: Parser error: state=Req_UriAuthority input(-8)=0x40('p://user@tempesta-tech.com/ HTTP/1.1 [42009.149802] [42009.149802] ') data_len=47 off=15 Apr 26 03:44:19 192.168.122.209 [42009.599206] [tdb] Close table 'client0.tdb' Apr 26 03:44:19 192.168.122.209 [42009.804404] [tdb] Close table 'sessions0.tdb' Apr 26 03:44:22 192.168.122.209 [42012.998266] [tdb] Close table 'cache0.tdb' Apr 26 03:44:22 192.168.122.209 [42013.247313] [tdb] Close table 'filter0.tdb' Apr 26 03:44:22 192.168.122.209 [42013.247731] [tempesta fw] modules are stopped Apr 26 03:44:23 192.168.122.209 [42013.433088] [tempesta fw] exiting... Apr 26 03:44:23 192.168.122.209 [42013.562422] [tdb] Shutdown Tempesta DB Apr 26 03:44:23 192.168.122.209 [42013.761653] End test: http_general.test_headers.TestHost.test_host_in_uri_without_host_header Apr 26 03:44:23 192.168.122.209 [42013.772901] Start test: http_general.test_headers.TestHost.test_host_missing Apr 26 03:44:24 192.168.122.209 [42014.910847] [tdb] Start Tempesta DB Apr 26 03:44:24 192.168.122.209 [42015.069732] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:44:26 192.168.122.209 [42016.385628] [tempesta fw] Configuration processing is completed. Apr 26 03:44:26 192.168.122.209 [42016.436159] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:44:26 192.168.122.209 [42016.846515] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:44:26 192.168.122.209 [42016.877091] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:44:26 192.168.122.209 [42016.902443] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:44:26 192.168.122.209 [42016.953623] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:44:26 192.168.122.209 [42016.997555] [tempesta fw] Tempesta FW is ready Apr 26 03:44:26 192.168.122.209 [42017.125050] [tempesta fw] Warning: Invalid authority: 127.0.0.2 Apr 26 03:44:27 192.168.122.209 [42017.582775] [tdb] Close table 'client0.tdb' Apr 26 03:44:27 192.168.122.209 [42017.791345] [tdb] Close table 'sessions0.tdb' Apr 26 03:44:30 192.168.122.209 [42020.937845] [tdb] Close table 'cache0.tdb' Apr 26 03:44:30 192.168.122.209 [42021.181849] [tdb] Close table 'filter0.tdb' Apr 26 03:44:30 192.168.122.209 [42021.182281] [tempesta fw] modules are stopped Apr 26 03:44:31 192.168.122.209 [42021.343913] [tempesta fw] exiting... Apr 26 03:44:31 192.168.122.209 [42021.457105] [tdb] Shutdown Tempesta DB Apr 26 03:44:31 192.168.122.209 [42021.675864] End test: http_general.test_headers.TestHost.test_host_missing Apr 26 03:44:31 192.168.122.209 [42021.686769] Start test: http_general.test_headers.TestHostWithCache.test_different_host_in_uri_and_headers_1 Apr 26 03:44:32 192.168.122.209 [42022.828414] [tdb] Start Tempesta DB Apr 26 03:44:32 192.168.122.209 [42022.976810] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:44:34 192.168.122.209 [42024.713726] [tempesta fw] Configuration processing is completed. Apr 26 03:44:34 192.168.122.209 [42024.763558] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:44:34 192.168.122.209 [42025.179675] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:44:34 192.168.122.209 [42025.205385] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:44:34 192.168.122.209 [42025.233450] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:44:34 192.168.122.209 [42025.289649] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:44:35 192.168.122.209 [42025.345651] [tempesta fw] Tempesta FW is ready Apr 26 03:44:35 192.168.122.209 [42025.487168] [tempesta fw] Warning: Parser error: state=Req_UriAuthority input(-8)=0x40('p://user@tempesta-tech.com/ HTTP/1.1 [42025.487168] Host: loca') data_len=64 off=15 Apr 26 03:44:35 192.168.122.209 [42025.915252] [tdb] Close table 'client0.tdb' Apr 26 03:44:35 192.168.122.209 [42026.109668] [tdb] Close table 'sessions0.tdb' Apr 26 03:44:38 192.168.122.209 [42029.292234] [tdb] Close table 'cache0.tdb' Apr 26 03:44:39 192.168.122.209 [42029.531521] [tdb] Close table 'filter0.tdb' Apr 26 03:44:39 192.168.122.209 [42029.531942] [tempesta fw] modules are stopped Apr 26 03:44:39 192.168.122.209 [42029.731998] [tempesta fw] exiting... Apr 26 03:44:39 192.168.122.209 [42029.876763] [tdb] Shutdown Tempesta DB Apr 26 03:44:39 192.168.122.209 [42030.105005] End test: http_general.test_headers.TestHostWithCache.test_different_host_in_uri_and_headers_1 Apr 26 03:44:39 192.168.122.209 [42030.119869] Start test: http_general.test_headers.TestHostWithCache.test_different_host_in_uri_and_headers_10 Apr 26 03:44:40 192.168.122.209 [42031.293783] [tdb] Start Tempesta DB Apr 26 03:44:41 192.168.122.209 [42031.439482] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:44:42 192.168.122.209 [42033.241876] [tempesta fw] Configuration processing is completed. Apr 26 03:44:42 192.168.122.209 [42033.292537] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:44:43 192.168.122.209 [42033.699510] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:44:43 192.168.122.209 [42033.725014] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:44:43 192.168.122.209 [42033.751547] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:44:43 192.168.122.209 [42033.837831] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:44:43 192.168.122.209 [42033.889762] [tempesta fw] Tempesta FW is ready Apr 26 03:44:43 192.168.122.209 [42034.015369] [tempesta fw] Warning: Parser error: state=Req_UriAuthorityStart input(-8)=0x2f(' http:///path HTTP/1.1 [42034.015369] Host: localhost [42034.015369] [42034.015369] ') data_len=46 off=11 Apr 26 03:44:44 192.168.122.209 [42034.469905] [tdb] Close table 'client0.tdb' Apr 26 03:44:44 192.168.122.209 [42034.683889] [tdb] Close table 'sessions0.tdb' Apr 26 03:44:47 192.168.122.209 [42037.796041] [tdb] Close table 'cache0.tdb' Apr 26 03:44:47 192.168.122.209 [42038.068241] [tdb] Close table 'filter0.tdb' Apr 26 03:44:47 192.168.122.209 [42038.068674] [tempesta fw] modules are stopped Apr 26 03:44:47 192.168.122.209 [42038.312760] [tempesta fw] exiting... Apr 26 03:44:48 192.168.122.209 [42038.462025] [tdb] Shutdown Tempesta DB Apr 26 03:44:48 192.168.122.209 [42038.682197] End test: http_general.test_headers.TestHostWithCache.test_different_host_in_uri_and_headers_10 Apr 26 03:44:48 192.168.122.209 [42038.695342] Start test: http_general.test_headers.TestHostWithCache.test_different_host_in_uri_and_headers_11 Apr 26 03:44:49 192.168.122.209 [42039.851139] [tdb] Start Tempesta DB Apr 26 03:44:49 192.168.122.209 [42040.000967] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:44:51 192.168.122.209 [42041.797943] [tempesta fw] Configuration processing is completed. Apr 26 03:44:51 192.168.122.209 [42041.857187] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:44:51 192.168.122.209 [42042.266203] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:44:51 192.168.122.209 [42042.291954] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:44:51 192.168.122.209 [42042.317415] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:44:52 192.168.122.209 [42042.365925] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:44:52 192.168.122.209 [42042.405881] [tempesta fw] Tempesta FW is ready Apr 26 03:44:52 192.168.122.209 [42042.532346] [tempesta fw] Warning: Parser error: state=Req_UriAuthority input(-8)=0x40('p://user@/path HTTP/1.1 [42042.532346] Host: localhost [42042.532346] [42042.532346] ') data_len=51 off=15 Apr 26 03:44:52 192.168.122.209 [42042.980050] [tdb] Close table 'client0.tdb' Apr 26 03:44:52 192.168.122.209 [42043.170197] [tdb] Close table 'sessions0.tdb' Apr 26 03:44:55 192.168.122.209 [42046.321939] [tdb] Close table 'cache0.tdb' Apr 26 03:44:56 192.168.122.209 [42046.541287] [tdb] Close table 'filter0.tdb' Apr 26 03:44:56 192.168.122.209 [42046.541723] [tempesta fw] modules are stopped Apr 26 03:44:56 192.168.122.209 [42046.784720] [tempesta fw] exiting... Apr 26 03:44:56 192.168.122.209 [42046.917216] [tdb] Shutdown Tempesta DB Apr 26 03:44:56 192.168.122.209 [42047.106193] End test: http_general.test_headers.TestHostWithCache.test_different_host_in_uri_and_headers_11 Apr 26 03:44:56 192.168.122.209 [42047.113407] Start test: http_general.test_headers.TestHostWithCache.test_different_host_in_uri_and_headers_12 Apr 26 03:44:57 192.168.122.209 [42048.296564] [tdb] Start Tempesta DB Apr 26 03:44:58 192.168.122.209 [42048.446698] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:44:59 192.168.122.209 [42050.266046] [tempesta fw] Configuration processing is completed. Apr 26 03:45:00 192.168.122.209 [42050.354148] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:45:00 192.168.122.209 [42050.787183] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:45:00 192.168.122.209 [42050.812402] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:45:00 192.168.122.209 [42050.837884] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:45:00 192.168.122.209 [42050.886025] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:45:00 192.168.122.209 [42050.926005] [tempesta fw] Tempesta FW is ready Apr 26 03:45:00 192.168.122.209 [42051.065048] [tempesta fw] Warning: Parser error: state=Req_UriAuthorityStart input(-8)=0x3a(' http://:443 HTTP/1.1 [42051.065048] Host: localhost [42051.065048] [42051.065048] ') data_len=45 off=11 Apr 26 03:45:01 192.168.122.209 [42051.504492] [tdb] Close table 'client0.tdb' Apr 26 03:45:01 192.168.122.209 [42051.685498] [tdb] Close table 'sessions0.tdb' Apr 26 03:45:04 192.168.122.209 [42054.793166] [tdb] Close table 'cache0.tdb' Apr 26 03:45:04 192.168.122.209 [42055.040844] [tdb] Close table 'filter0.tdb' Apr 26 03:45:04 192.168.122.209 [42055.041275] [tempesta fw] modules are stopped Apr 26 03:45:04 192.168.122.209 [42055.277250] [tempesta fw] exiting... Apr 26 03:45:05 192.168.122.209 [42055.435908] [tdb] Shutdown Tempesta DB Apr 26 03:45:05 192.168.122.209 [42055.653095] End test: http_general.test_headers.TestHostWithCache.test_different_host_in_uri_and_headers_12 Apr 26 03:45:05 192.168.122.209 [42055.666259] Start test: http_general.test_headers.TestHostWithCache.test_different_host_in_uri_and_headers_13 Apr 26 03:45:06 192.168.122.209 [42056.814337] [tdb] Start Tempesta DB Apr 26 03:45:06 192.168.122.209 [42056.962374] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:45:08 192.168.122.209 [42058.830164] [tempesta fw] Configuration processing is completed. Apr 26 03:45:08 192.168.122.209 [42058.881349] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:45:08 192.168.122.209 [42059.284524] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:45:08 192.168.122.209 [42059.309918] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:45:09 192.168.122.209 [42059.340378] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:45:09 192.168.122.209 [42059.386150] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:45:09 192.168.122.209 [42059.426099] [tempesta fw] Tempesta FW is ready Apr 26 03:45:09 192.168.122.209 [42059.546960] [tempesta fw] Warning: Parser error: state=Req_UriAuthorityStart input(-8)=0x2f(' http:///path HTTP/1.1 [42059.546960] Host: [42059.546960] [42059.546960] ') data_len=37 off=11 Apr 26 03:45:09 192.168.122.209 [42059.953554] [tdb] Close table 'client0.tdb' Apr 26 03:45:09 192.168.122.209 [42060.181245] [tdb] Close table 'sessions0.tdb' Apr 26 03:45:12 192.168.122.209 [42063.304694] [tdb] Close table 'cache0.tdb' Apr 26 03:45:13 192.168.122.209 [42063.562931] [tdb] Close table 'filter0.tdb' Apr 26 03:45:13 192.168.122.209 [42063.563362] [tempesta fw] modules are stopped Apr 26 03:45:13 192.168.122.209 [42063.782254] [tempesta fw] exiting... Apr 26 03:45:13 192.168.122.209 [42063.918736] [tdb] Shutdown Tempesta DB Apr 26 03:45:13 192.168.122.209 [42064.112758] End test: http_general.test_headers.TestHostWithCache.test_different_host_in_uri_and_headers_13 Apr 26 03:45:13 192.168.122.209 [42064.131621] Start test: http_general.test_headers.TestHostWithCache.test_different_host_in_uri_and_headers_2 Apr 26 03:45:14 192.168.122.209 [42065.295291] [tdb] Start Tempesta DB Apr 26 03:45:15 192.168.122.209 [42065.433099] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:45:16 192.168.122.209 [42067.186281] [tempesta fw] Configuration processing is completed. Apr 26 03:45:16 192.168.122.209 [42067.235725] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:45:17 192.168.122.209 [42067.641077] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:45:17 192.168.122.209 [42067.671117] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:45:17 192.168.122.209 [42067.696379] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:45:17 192.168.122.209 [42067.742159] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:45:17 192.168.122.209 [42067.782205] [tempesta fw] Tempesta FW is ready Apr 26 03:45:17 192.168.122.209 [42067.932368] [tempesta fw] Warning: Parser error: state=Req_UriAuthority input(-8)=0x40('p://user@-x/ HTTP/1.1 [42067.932368] Host: localhost [42067.932368] [42067.932368] ') data_len=49 off=15 Apr 26 03:45:18 192.168.122.209 [42068.378152] [tdb] Close table 'client0.tdb' Apr 26 03:45:18 192.168.122.209 [42068.583024] [tdb] Close table 'sessions0.tdb' Apr 26 03:45:21 192.168.122.209 [42071.737938] [tdb] Close table 'cache0.tdb' Apr 26 03:45:21 192.168.122.209 [42071.985804] [tdb] Close table 'filter0.tdb' Apr 26 03:45:21 192.168.122.209 [42071.986613] [tempesta fw] modules are stopped Apr 26 03:45:21 192.168.122.209 [42072.197129] [tempesta fw] exiting... Apr 26 03:45:22 192.168.122.209 [42072.358262] [tdb] Shutdown Tempesta DB Apr 26 03:45:22 192.168.122.209 [42072.570004] End test: http_general.test_headers.TestHostWithCache.test_different_host_in_uri_and_headers_2 Apr 26 03:45:22 192.168.122.209 [42072.579856] Start test: http_general.test_headers.TestHostWithCache.test_different_host_in_uri_and_headers_3 Apr 26 03:45:23 192.168.122.209 [42073.788142] [tdb] Start Tempesta DB Apr 26 03:45:23 192.168.122.209 [42073.940158] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:45:25 192.168.122.209 [42075.742369] [tempesta fw] Configuration processing is completed. Apr 26 03:45:25 192.168.122.209 [42075.823865] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:45:25 192.168.122.209 [42076.237944] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:45:25 192.168.122.209 [42076.263506] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:45:25 192.168.122.209 [42076.288939] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:45:26 192.168.122.209 [42076.334364] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:45:26 192.168.122.209 [42076.378297] [tempesta fw] Tempesta FW is ready Apr 26 03:45:26 192.168.122.209 [42076.518981] [tempesta fw] Warning: Parser error: state=Req_UriAuthority input(-8)=0x40('p://user@/ HTTP/1.1 [42076.518981] Host: localhost [42076.518981] [42076.518981] ') data_len=47 off=15 Apr 26 03:45:26 192.168.122.209 [42076.972628] [tdb] Close table 'client0.tdb' Apr 26 03:45:26 192.168.122.209 [42077.190101] [tdb] Close table 'sessions0.tdb' Apr 26 03:45:30 192.168.122.209 [42080.362365] [tdb] Close table 'cache0.tdb' Apr 26 03:45:30 192.168.122.209 [42080.605905] [tdb] Close table 'filter0.tdb' Apr 26 03:45:30 192.168.122.209 [42080.606363] [tempesta fw] modules are stopped Apr 26 03:45:30 192.168.122.209 [42080.785210] [tempesta fw] exiting... Apr 26 03:45:30 192.168.122.209 [42080.905856] [tdb] Shutdown Tempesta DB Apr 26 03:45:30 192.168.122.209 [42081.090463] End test: http_general.test_headers.TestHostWithCache.test_different_host_in_uri_and_headers_3 Apr 26 03:45:30 192.168.122.209 [42081.113958] Start test: http_general.test_headers.TestHostWithCache.test_different_host_in_uri_and_headers_4 Apr 26 03:45:31 192.168.122.209 [42082.208076] [tdb] Start Tempesta DB Apr 26 03:45:32 192.168.122.209 [42082.352514] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:45:33 192.168.122.209 [42084.198439] [tempesta fw] Configuration processing is completed. Apr 26 03:45:33 192.168.122.209 [42084.255885] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:45:34 192.168.122.209 [42084.656255] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:45:34 192.168.122.209 [42084.694431] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:45:34 192.168.122.209 [42084.719351] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:45:34 192.168.122.209 [42084.778452] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:45:34 192.168.122.209 [42084.818399] [tempesta fw] Tempesta FW is ready Apr 26 03:45:35 192.168.122.209 [42085.388123] [tdb] Close table 'client0.tdb' Apr 26 03:45:35 192.168.122.209 [42085.585350] [tdb] Close table 'sessions0.tdb' Apr 26 03:45:38 192.168.122.209 [42088.740957] [tdb] Close table 'cache0.tdb' Apr 26 03:45:38 192.168.122.209 [42088.976123] [tdb] Close table 'filter0.tdb' Apr 26 03:45:38 192.168.122.209 [42088.976558] [tempesta fw] modules are stopped Apr 26 03:45:38 192.168.122.209 [42089.170112] [tempesta fw] exiting... Apr 26 03:45:38 192.168.122.209 [42089.302896] [tdb] Shutdown Tempesta DB Apr 26 03:45:39 192.168.122.209 [42089.502790] End test: http_general.test_headers.TestHostWithCache.test_different_host_in_uri_and_headers_4 Apr 26 03:45:39 192.168.122.209 [42089.526256] Start test: http_general.test_headers.TestHostWithCache.test_different_host_in_uri_and_headers_5 Apr 26 03:45:40 192.168.122.209 [42090.722356] [tdb] Start Tempesta DB Apr 26 03:45:40 192.168.122.209 [42090.862605] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:45:42 192.168.122.209 [42092.678620] [tempesta fw] Configuration processing is completed. Apr 26 03:45:42 192.168.122.209 [42092.732865] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:45:42 192.168.122.209 [42093.145222] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:45:42 192.168.122.209 [42093.170961] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:45:42 192.168.122.209 [42093.196388] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:45:42 192.168.122.209 [42093.246582] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:45:42 192.168.122.209 [42093.294553] [tempesta fw] Tempesta FW is ready Apr 26 03:45:43 192.168.122.209 [42093.414502] [tempesta fw] Warning: Parser error: state=Req_UriAuthority input(-8)=0x40('p://user@:333/ HTTP/1.1 [42093.414502] Host: localhost [42093.414502] [42093.414502] ') data_len=51 off=15 Apr 26 03:45:43 192.168.122.209 [42093.845483] [tdb] Close table 'client0.tdb' Apr 26 03:45:43 192.168.122.209 [42094.043562] [tdb] Close table 'sessions0.tdb' Apr 26 03:45:46 192.168.122.209 [42097.160308] [tdb] Close table 'cache0.tdb' Apr 26 03:45:47 192.168.122.209 [42097.380715] [tdb] Close table 'filter0.tdb' Apr 26 03:45:47 192.168.122.209 [42097.381162] [tempesta fw] modules are stopped Apr 26 03:45:47 192.168.122.209 [42097.622960] [tempesta fw] exiting... Apr 26 03:45:47 192.168.122.209 [42097.798143] [tdb] Shutdown Tempesta DB Apr 26 03:45:47 192.168.122.209 [42097.996499] End test: http_general.test_headers.TestHostWithCache.test_different_host_in_uri_and_headers_5 Apr 26 03:45:47 192.168.122.209 [42098.019365] Start test: http_general.test_headers.TestHostWithCache.test_different_host_in_uri_and_headers_6 Apr 26 03:45:48 192.168.122.209 [42099.241842] [tdb] Start Tempesta DB Apr 26 03:45:49 192.168.122.209 [42099.409880] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:45:50 192.168.122.209 [42101.118701] [tempesta fw] Configuration processing is completed. Apr 26 03:45:50 192.168.122.209 [42101.218569] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:45:51 192.168.122.209 [42101.635186] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:45:51 192.168.122.209 [42101.660832] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:45:51 192.168.122.209 [42101.696454] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:45:51 192.168.122.209 [42101.746676] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:45:51 192.168.122.209 [42101.786626] [tempesta fw] Tempesta FW is ready Apr 26 03:45:51 192.168.122.209 [42101.908791] [tempesta fw] Warning: Parser error: state=Req_UriAuthority input(-8)=0x40('p://user@:/url/ HTTP/1.1 [42101.908791] Host: localhost [42101.908791] [42101.908791] ') data_len=52 off=15 Apr 26 03:45:52 192.168.122.209 [42102.361739] [tdb] Close table 'client0.tdb' Apr 26 03:45:52 192.168.122.209 [42102.572920] [tdb] Close table 'sessions0.tdb' Apr 26 03:45:55 192.168.122.209 [42105.645463] [tdb] Close table 'cache0.tdb' Apr 26 03:45:55 192.168.122.209 [42105.904485] [tdb] Close table 'filter0.tdb' Apr 26 03:45:55 192.168.122.209 [42105.904922] [tempesta fw] modules are stopped Apr 26 03:45:55 192.168.122.209 [42106.158904] [tempesta fw] exiting... Apr 26 03:45:55 192.168.122.209 [42106.304173] [tdb] Shutdown Tempesta DB Apr 26 03:45:56 192.168.122.209 [42106.508554] End test: http_general.test_headers.TestHostWithCache.test_different_host_in_uri_and_headers_6 Apr 26 03:45:56 192.168.122.209 [42106.517639] Start test: http_general.test_headers.TestHostWithCache.test_different_host_in_uri_and_headers_7 Apr 26 03:45:57 192.168.122.209 [42107.705043] [tdb] Start Tempesta DB Apr 26 03:45:57 192.168.122.209 [42107.857060] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:45:59 192.168.122.209 [42109.630805] [tempesta fw] Configuration processing is completed. Apr 26 03:45:59 192.168.122.209 [42109.681340] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:45:59 192.168.122.209 [42110.099503] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:45:59 192.168.122.209 [42110.125704] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:45:59 192.168.122.209 [42110.151238] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:45:59 192.168.122.209 [42110.190813] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:45:59 192.168.122.209 [42110.246737] [tempesta fw] Tempesta FW is ready Apr 26 03:46:00 192.168.122.209 [42110.389742] [tempesta fw] Warning: Parser error: state=Req_UriAuthority input(-8)=0x40('p://user@: HTTP/1.1 [42110.389742] Host: localhost [42110.389742] [42110.389742] ') data_len=47 off=15 Apr 26 03:46:00 192.168.122.209 [42110.818093] [tdb] Close table 'client0.tdb' Apr 26 03:46:00 192.168.122.209 [42111.008772] [tdb] Close table 'sessions0.tdb' Apr 26 03:46:03 192.168.122.209 [42114.208403] [tdb] Close table 'cache0.tdb' Apr 26 03:46:04 192.168.122.209 [42114.460343] [tdb] Close table 'filter0.tdb' Apr 26 03:46:04 192.168.122.209 [42114.460760] [tempesta fw] modules are stopped Apr 26 03:46:04 192.168.122.209 [42114.660910] [tempesta fw] exiting... Apr 26 03:46:04 192.168.122.209 [42114.805732] [tdb] Shutdown Tempesta DB Apr 26 03:46:04 192.168.122.209 [42115.020638] End test: http_general.test_headers.TestHostWithCache.test_different_host_in_uri_and_headers_7 Apr 26 03:46:04 192.168.122.209 [42115.029984] Start test: http_general.test_headers.TestHostWithCache.test_different_host_in_uri_and_headers_8 Apr 26 03:46:05 192.168.122.209 [42116.173992] [tdb] Start Tempesta DB Apr 26 03:46:05 192.168.122.209 [42116.318720] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:46:07 192.168.122.209 [42118.266942] [tempesta fw] Configuration processing is completed. Apr 26 03:46:07 192.168.122.209 [42118.325072] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:46:08 192.168.122.209 [42118.737484] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:46:08 192.168.122.209 [42118.763190] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:46:08 192.168.122.209 [42118.788582] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:46:08 192.168.122.209 [42118.866886] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:46:08 192.168.122.209 [42118.906843] [tempesta fw] Tempesta FW is ready Apr 26 03:46:08 192.168.122.209 [42119.022253] [tempesta fw] Warning: Parser error: state=Req_UriPort input(-8)=0x20('ech.com: HTTP/1.1 [42119.022253] Host: localhost [42119.022253] [42119.022253] ') data_len=59 off=29 Apr 26 03:46:09 192.168.122.209 [42119.423101] [tdb] Close table 'client0.tdb' Apr 26 03:46:09 192.168.122.209 [42119.632860] [tdb] Close table 'sessions0.tdb' Apr 26 03:46:12 192.168.122.209 [42122.779066] [tdb] Close table 'cache0.tdb' Apr 26 03:46:12 192.168.122.209 [42123.029630] [tdb] Close table 'filter0.tdb' Apr 26 03:46:12 192.168.122.209 [42123.030069] [tempesta fw] modules are stopped Apr 26 03:46:12 192.168.122.209 [42123.212492] [tempesta fw] exiting... Apr 26 03:46:13 192.168.122.209 [42123.369244] [tdb] Shutdown Tempesta DB Apr 26 03:46:13 192.168.122.209 [42123.572618] End test: http_general.test_headers.TestHostWithCache.test_different_host_in_uri_and_headers_8 Apr 26 03:46:13 192.168.122.209 [42123.581516] Start test: http_general.test_headers.TestHostWithCache.test_different_host_in_uri_and_headers_9 Apr 26 03:46:14 192.168.122.209 [42124.743712] [tdb] Start Tempesta DB Apr 26 03:46:14 192.168.122.209 [42124.892294] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:46:16 192.168.122.209 [42126.695002] [tempesta fw] Configuration processing is completed. Apr 26 03:46:16 192.168.122.209 [42126.780729] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:46:16 192.168.122.209 [42127.227354] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:46:16 192.168.122.209 [42127.263435] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:46:16 192.168.122.209 [42127.292348] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:46:17 192.168.122.209 [42127.354930] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:46:17 192.168.122.209 [42127.414939] [tempesta fw] Tempesta FW is ready Apr 26 03:46:17 192.168.122.209 [42127.577730] [tempesta fw] Warning: Parser error: state=Req_UriPort input(-8)=0x2f('ech.com:/ HTTP/1.1 [42127.577730] Host: localhost [42127.577730] [42127.577730] ') data_len=60 off=29 Apr 26 03:46:17 192.168.122.209 [42128.042151] [tdb] Close table 'client0.tdb' Apr 26 03:46:17 192.168.122.209 [42128.233660] [tdb] Close table 'sessions0.tdb' Apr 26 03:46:21 192.168.122.209 [42131.426979] [tdb] Close table 'cache0.tdb' Apr 26 03:46:21 192.168.122.209 [42131.697853] [tdb] Close table 'filter0.tdb' Apr 26 03:46:21 192.168.122.209 [42131.698288] [tempesta fw] modules are stopped Apr 26 03:46:21 192.168.122.209 [42131.889598] [tempesta fw] exiting... Apr 26 03:46:21 192.168.122.209 [42132.035416] [tdb] Shutdown Tempesta DB Apr 26 03:46:21 192.168.122.209 [42132.218051] End test: http_general.test_headers.TestHostWithCache.test_different_host_in_uri_and_headers_9 Apr 26 03:46:21 192.168.122.209 [42132.228508] Start test: http_general.test_headers.TestMethods.test_known_methods Apr 26 03:46:23 192.168.122.209 [42133.347663] [tdb] Start Tempesta DB Apr 26 03:46:23 192.168.122.209 [42133.513707] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:46:24 192.168.122.209 [42134.883172] [tempesta fw] Configuration processing is completed. Apr 26 03:46:24 192.168.122.209 [42134.935113] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:46:25 192.168.122.209 [42135.361246] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:46:25 192.168.122.209 [42135.387512] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:46:25 192.168.122.209 [42135.414124] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:46:25 192.168.122.209 [42135.475140] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:46:25 192.168.122.209 [42135.535053] [tempesta fw] Tempesta FW is ready Apr 26 03:46:25 192.168.122.209 [42136.247889] [tdb] Close table 'client0.tdb' Apr 26 03:46:26 192.168.122.209 [42136.459568] [tdb] Close table 'sessions0.tdb' Apr 26 03:46:29 192.168.122.209 [42139.652035] [tdb] Close table 'cache0.tdb' Apr 26 03:46:29 192.168.122.209 [42139.892979] [tdb] Close table 'filter0.tdb' Apr 26 03:46:29 192.168.122.209 [42139.893457] [tempesta fw] modules are stopped Apr 26 03:46:29 192.168.122.209 [42140.083658] [tempesta fw] exiting... Apr 26 03:46:29 192.168.122.209 [42140.238234] [tdb] Shutdown Tempesta DB Apr 26 03:46:30 192.168.122.209 [42140.463972] End test: http_general.test_headers.TestMethods.test_known_methods Apr 26 03:46:30 192.168.122.209 [42140.473723] Start test: http_general.test_headers.TestMethods.test_known_methods_leading_crlf Apr 26 03:46:31 192.168.122.209 [42141.582177] [tdb] Start Tempesta DB Apr 26 03:46:31 192.168.122.209 [42141.734748] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:46:32 192.168.122.209 [42143.047242] [tempesta fw] Configuration processing is completed. Apr 26 03:46:32 192.168.122.209 [42143.097235] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:46:33 192.168.122.209 [42143.535400] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:46:33 192.168.122.209 [42143.562078] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:46:33 192.168.122.209 [42143.589442] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:46:33 192.168.122.209 [42143.631190] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:46:33 192.168.122.209 [42143.671161] [tempesta fw] Tempesta FW is ready Apr 26 03:46:34 192.168.122.209 [42144.415618] [tdb] Close table 'client0.tdb' Apr 26 03:46:34 192.168.122.209 [42144.628898] [tdb] Close table 'sessions0.tdb' Apr 26 03:46:37 192.168.122.209 [42147.802524] [tdb] Close table 'cache0.tdb' Apr 26 03:46:37 192.168.122.209 [42148.060894] [tdb] Close table 'filter0.tdb' Apr 26 03:46:37 192.168.122.209 [42148.061340] [tempesta fw] modules are stopped Apr 26 03:46:37 192.168.122.209 [42148.233727] [tempesta fw] exiting... Apr 26 03:46:38 192.168.122.209 [42148.361413] [tdb] Shutdown Tempesta DB Apr 26 03:46:38 192.168.122.209 [42148.607535] End test: http_general.test_headers.TestMethods.test_known_methods_leading_crlf Apr 26 03:46:38 192.168.122.209 [42148.622401] Start test: http_general.test_headers.TestMethods.test_unknown_methods Apr 26 03:46:39 192.168.122.209 [42149.761698] [tdb] Start Tempesta DB Apr 26 03:46:39 192.168.122.209 [42149.928354] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:46:40 192.168.122.209 [42151.327384] [tempesta fw] Configuration processing is completed. Apr 26 03:46:41 192.168.122.209 [42151.379137] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:46:41 192.168.122.209 [42151.858410] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:46:41 192.168.122.209 [42151.890193] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:46:41 192.168.122.209 [42151.920483] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:46:41 192.168.122.209 [42151.971353] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:46:41 192.168.122.209 [42152.015248] [tempesta fw] Tempesta FW is ready Apr 26 03:46:42 192.168.122.209 [42152.653950] [tdb] Close table 'client0.tdb' Apr 26 03:46:42 192.168.122.209 [42152.851076] [tdb] Close table 'sessions0.tdb' Apr 26 03:46:45 192.168.122.209 [42156.061702] [tdb] Close table 'cache0.tdb' Apr 26 03:46:45 192.168.122.209 [42156.281440] [tdb] Close table 'filter0.tdb' Apr 26 03:46:45 192.168.122.209 [42156.281874] [tempesta fw] modules are stopped Apr 26 03:46:46 192.168.122.209 [42156.442503] [tempesta fw] exiting... Apr 26 03:46:46 192.168.122.209 [42156.594614] [tdb] Shutdown Tempesta DB Apr 26 03:46:46 192.168.122.209 [42156.819834] End test: http_general.test_headers.TestMethods.test_unknown_methods Apr 26 03:46:46 192.168.122.209 [42156.831438] Start test: http_general.test_headers.TestMethods.test_unknown_methods_leading_crlf Apr 26 03:46:47 192.168.122.209 [42158.025535] [tdb] Start Tempesta DB Apr 26 03:46:47 192.168.122.209 [42158.178382] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:46:49 192.168.122.209 [42159.483482] [tempesta fw] Configuration processing is completed. Apr 26 03:46:49 192.168.122.209 [42159.534592] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:46:49 192.168.122.209 [42159.943014] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:46:49 192.168.122.209 [42160.005771] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:46:49 192.168.122.209 [42160.031839] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:46:49 192.168.122.209 [42160.071404] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:46:49 192.168.122.209 [42160.115351] [tempesta fw] Tempesta FW is ready Apr 26 03:46:50 192.168.122.209 [42160.713897] [tdb] Close table 'client0.tdb' Apr 26 03:46:50 192.168.122.209 [42160.910888] [tdb] Close table 'sessions0.tdb' Apr 26 03:46:53 192.168.122.209 [42164.057619] [tdb] Close table 'cache0.tdb' Apr 26 03:46:53 192.168.122.209 [42164.306766] [tdb] Close table 'filter0.tdb' Apr 26 03:46:53 192.168.122.209 [42164.307230] [tempesta fw] modules are stopped Apr 26 03:46:54 192.168.122.209 [42164.491692] [tempesta fw] exiting... Apr 26 03:46:54 192.168.122.209 [42164.673599] [tdb] Shutdown Tempesta DB Apr 26 03:46:54 192.168.122.209 [42164.872868] End test: http_general.test_headers.TestMethods.test_unknown_methods_leading_crlf Apr 26 03:46:54 192.168.122.209 [42164.885544] Start test: http_general.test_headers.TestNoContentLengthInMethodMethodDELETE.test_request_success Apr 26 03:46:55 192.168.122.209 [42166.020975] [tdb] Start Tempesta DB Apr 26 03:46:55 192.168.122.209 [42166.164546] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:46:57 192.168.122.209 [42167.424699] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [42167.424699] Maybe that's fine, but it's worth checking the [42167.424699] config - if there is no relations between the [42167.424699] names, then host name confusion attack is possible. Apr 26 03:46:57 192.168.122.209 [42167.551521] [tempesta fw] Configuration processing is completed. Apr 26 03:46:57 192.168.122.209 [42167.601774] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:46:57 192.168.122.209 [42168.015932] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:46:57 192.168.122.209 [42168.041861] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:46:57 192.168.122.209 [42168.068867] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:46:57 192.168.122.209 [42168.111500] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:46:57 192.168.122.209 [42168.159451] [tempesta fw] Tempesta FW is ready Apr 26 03:46:57 192.168.122.209 [42168.316865] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 03:46:57 192.168.122.209 [42168.319148] [tempesta fw] Warning: Can't create pipelined response: 127.0.0.3 Apr 26 03:46:57 192.168.122.209 [42168.321154] [tempesta fw] 127.0.0.2 "default" "DELETE / HTTP/1.1" 200 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400080080" Apr 26 03:46:57 192.168.122.209 [42168.331931] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 03:46:57 192.168.122.209 [42168.333195] [tempesta fw] Warning: Can't create pipelined response: 127.0.0.3 Apr 26 03:46:57 192.168.122.209 [42168.334290] [tempesta fw] 127.0.0.2 "default" "DELETE / HTTP/1.1" 201 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400080080" Apr 26 03:46:58 192.168.122.209 [42168.341532] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 03:46:58 192.168.122.209 [42168.343862] [tempesta fw] 127.0.0.2 "default" "DELETE / HTTP/1.1" 302 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400080080" Apr 26 03:46:58 192.168.122.209 [42168.352099] [tempesta fw] 127.0.0.2 "default" "DELETE / HTTP/1.1" 304 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400080080" Apr 26 03:46:58 192.168.122.209 [42168.362408] [tempesta fw] 127.0.0.2 "default" "DELETE / HTTP/1.1" 400 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400080080" Apr 26 03:46:58 192.168.122.209 [42168.372590] [tempesta fw] 127.0.0.2 "default" "DELETE / HTTP/1.1" 401 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400080080" Apr 26 03:46:58 192.168.122.209 [42168.384111] [tempesta fw] 127.0.0.2 "default" "DELETE / HTTP/1.1" 404 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400080080" Apr 26 03:46:58 192.168.122.209 [42168.393767] [tempesta fw] 127.0.0.2 "default" "DELETE / HTTP/1.1" 500 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400080080" Apr 26 03:46:58 192.168.122.209 [42168.841419] [tdb] Close table 'client0.tdb' Apr 26 03:46:58 192.168.122.209 [42169.057243] [tdb] Close table 'sessions0.tdb' Apr 26 03:47:01 192.168.122.209 [42172.222422] [tdb] Close table 'cache0.tdb' Apr 26 03:47:02 192.168.122.209 [42172.478722] [tdb] Close table 'filter0.tdb' Apr 26 03:47:02 192.168.122.209 [42172.479159] net_ratelimit: 11 callbacks suppressed Apr 26 03:47:02 192.168.122.209 [42172.479161] [tempesta fw] modules are stopped Apr 26 03:47:02 192.168.122.209 [42172.731289] [tempesta fw] exiting... Apr 26 03:47:02 192.168.122.209 [42172.879805] [tdb] Shutdown Tempesta DB Apr 26 03:47:02 192.168.122.209 [42173.124796] End test: http_general.test_headers.TestNoContentLengthInMethodMethodDELETE.test_request_success Apr 26 03:47:02 192.168.122.209 [42173.149185] Start test: http_general.test_headers.TestNoContentLengthInMethodMethodGET.test_request_success Apr 26 03:47:03 192.168.122.209 [42174.299979] [tdb] Start Tempesta DB Apr 26 03:47:04 192.168.122.209 [42174.455437] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:47:05 192.168.122.209 [42175.840871] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [42175.840871] Maybe that's fine, but it's worth checking the [42175.840871] config - if there is no relations between the [42175.840871] names, then host name confusion attack is possible. Apr 26 03:47:05 192.168.122.209 [42175.967941] [tempesta fw] Configuration processing is completed. Apr 26 03:47:05 192.168.122.209 [42176.019521] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:47:06 192.168.122.209 [42176.427265] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:47:06 192.168.122.209 [42176.483968] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:47:06 192.168.122.209 [42176.518938] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:47:06 192.168.122.209 [42176.563635] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:47:06 192.168.122.209 [42176.599552] [tempesta fw] Tempesta FW is ready Apr 26 03:47:06 192.168.122.209 [42176.754413] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 03:47:06 192.168.122.209 [42176.756725] [tempesta fw] Warning: Can't create pipelined response: 127.0.0.3 Apr 26 03:47:06 192.168.122.209 [42176.758716] [tempesta fw] 127.0.0.2 "default" "GET / HTTP/1.1" 200 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=4000c0080" Apr 26 03:47:06 192.168.122.209 [42176.771412] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 03:47:06 192.168.122.209 [42176.773044] [tempesta fw] Warning: Can't create pipelined response: 127.0.0.3 Apr 26 03:47:06 192.168.122.209 [42176.774447] [tempesta fw] 127.0.0.2 "default" "GET / HTTP/1.1" 302 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=4000c0080" Apr 26 03:47:06 192.168.122.209 [42176.781423] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 03:47:06 192.168.122.209 [42176.782188] [tempesta fw] 127.0.0.2 "default" "GET / HTTP/1.1" 304 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=4000c0080" Apr 26 03:47:06 192.168.122.209 [42176.792176] [tempesta fw] 127.0.0.2 "default" "GET / HTTP/1.1" 400 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=4000c0080" Apr 26 03:47:06 192.168.122.209 [42176.802007] [tempesta fw] 127.0.0.2 "default" "GET / HTTP/1.1" 401 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=4000c0080" Apr 26 03:47:06 192.168.122.209 [42176.812202] [tempesta fw] 127.0.0.2 "default" "GET / HTTP/1.1" 404 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=4000c0080" Apr 26 03:47:06 192.168.122.209 [42176.822252] [tempesta fw] 127.0.0.2 "default" "GET / HTTP/1.1" 500 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=4000c0080" Apr 26 03:47:06 192.168.122.209 [42177.246545] [tdb] Close table 'client0.tdb' Apr 26 03:47:07 192.168.122.209 [42177.450638] [tdb] Close table 'sessions0.tdb' Apr 26 03:47:10 192.168.122.209 [42180.573800] [tdb] Close table 'cache0.tdb' Apr 26 03:47:10 192.168.122.209 [42180.827349] [tdb] Close table 'filter0.tdb' Apr 26 03:47:10 192.168.122.209 [42180.827790] net_ratelimit: 9 callbacks suppressed Apr 26 03:47:10 192.168.122.209 [42180.827792] [tempesta fw] modules are stopped Apr 26 03:47:10 192.168.122.209 [42181.044415] [tempesta fw] exiting... Apr 26 03:47:10 192.168.122.209 [42181.183817] [tdb] Shutdown Tempesta DB Apr 26 03:47:11 192.168.122.209 [42181.378112] End test: http_general.test_headers.TestNoContentLengthInMethodMethodGET.test_request_success Apr 26 03:47:11 192.168.122.209 [42181.388862] Start test: http_general.test_headers.TestNoContentLengthInMethodMethodHEAD.test_request_success Apr 26 03:47:12 192.168.122.209 [42182.587962] [tdb] Start Tempesta DB Apr 26 03:47:12 192.168.122.209 [42182.743280] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:47:13 192.168.122.209 [42184.077006] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [42184.077006] Maybe that's fine, but it's worth checking the [42184.077006] config - if there is no relations between the [42184.077006] names, then host name confusion attack is possible. Apr 26 03:47:13 192.168.122.209 [42184.227760] [tempesta fw] Configuration processing is completed. Apr 26 03:47:13 192.168.122.209 [42184.279532] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:47:14 192.168.122.209 [42184.718650] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:47:14 192.168.122.209 [42184.748490] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:47:14 192.168.122.209 [42184.779578] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:47:14 192.168.122.209 [42184.839727] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:47:14 192.168.122.209 [42184.879671] [tempesta fw] Tempesta FW is ready Apr 26 03:47:14 192.168.122.209 [42185.017631] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 03:47:14 192.168.122.209 [42185.019961] [tempesta fw] Warning: Can't create pipelined response: 127.0.0.3 Apr 26 03:47:14 192.168.122.209 [42185.021943] [tempesta fw] 127.0.0.2 "default" "HEAD / HTTP/1.1" 200 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400100080" Apr 26 03:47:15 192.168.122.209 [42185.430952] [tdb] Close table 'client0.tdb' Apr 26 03:47:15 192.168.122.209 [42185.663002] [tdb] Close table 'sessions0.tdb' Apr 26 03:47:18 192.168.122.209 [42188.956380] [tdb] Close table 'cache0.tdb' Apr 26 03:47:18 192.168.122.209 [42189.206580] [tdb] Close table 'filter0.tdb' Apr 26 03:47:18 192.168.122.209 [42189.207035] [tempesta fw] modules are stopped Apr 26 03:47:19 192.168.122.209 [42189.407531] [tempesta fw] exiting... Apr 26 03:47:19 192.168.122.209 [42189.557476] [tdb] Shutdown Tempesta DB Apr 26 03:47:19 192.168.122.209 [42189.781003] End test: http_general.test_headers.TestNoContentLengthInMethodMethodHEAD.test_request_success Apr 26 03:47:19 192.168.122.209 [42189.802648] Start test: http_general.test_headers.TestNoContentLengthInMethodMethodPATCH.test_request_success Apr 26 03:47:20 192.168.122.209 [42190.968949] [tdb] Start Tempesta DB Apr 26 03:47:20 192.168.122.209 [42191.142956] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:47:22 192.168.122.209 [42192.525164] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [42192.525164] Maybe that's fine, but it's worth checking the [42192.525164] config - if there is no relations between the [42192.525164] names, then host name confusion attack is possible. Apr 26 03:47:22 192.168.122.209 [42192.647865] [tempesta fw] Configuration processing is completed. Apr 26 03:47:22 192.168.122.209 [42192.704254] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:47:22 192.168.122.209 [42193.119419] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:47:22 192.168.122.209 [42193.191690] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:47:22 192.168.122.209 [42193.218673] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:47:22 192.168.122.209 [42193.259873] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:47:22 192.168.122.209 [42193.303718] [tempesta fw] Tempesta FW is ready Apr 26 03:47:23 192.168.122.209 [42193.437135] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 03:47:23 192.168.122.209 [42193.439437] [tempesta fw] Warning: Can't create pipelined response: 127.0.0.3 Apr 26 03:47:23 192.168.122.209 [42193.441459] [tempesta fw] 127.0.0.2 "default" "PATCH / HTTP/1.1" 200 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400240080" Apr 26 03:47:23 192.168.122.209 [42193.457416] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 03:47:23 192.168.122.209 [42193.459715] [tempesta fw] Warning: Can't create pipelined response: 127.0.0.3 Apr 26 03:47:23 192.168.122.209 [42193.461699] [tempesta fw] 127.0.0.2 "default" "PATCH / HTTP/1.1" 201 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400240080" Apr 26 03:47:23 192.168.122.209 [42193.476320] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 03:47:23 192.168.122.209 [42193.477074] [tempesta fw] 127.0.0.2 "default" "PATCH / HTTP/1.1" 302 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400240080" Apr 26 03:47:23 192.168.122.209 [42193.488720] [tempesta fw] 127.0.0.2 "default" "PATCH / HTTP/1.1" 304 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400240080" Apr 26 03:47:23 192.168.122.209 [42193.499453] [tempesta fw] 127.0.0.2 "default" "PATCH / HTTP/1.1" 400 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400240080" Apr 26 03:47:23 192.168.122.209 [42193.509762] [tempesta fw] 127.0.0.2 "default" "PATCH / HTTP/1.1" 401 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400240080" Apr 26 03:47:23 192.168.122.209 [42193.521433] [tempesta fw] 127.0.0.2 "default" "PATCH / HTTP/1.1" 404 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400240080" Apr 26 03:47:23 192.168.122.209 [42193.530708] [tempesta fw] 127.0.0.2 "default" "PATCH / HTTP/1.1" 500 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400240080" Apr 26 03:47:23 192.168.122.209 [42193.969627] [tdb] Close table 'client0.tdb' Apr 26 03:47:23 192.168.122.209 [42194.165122] [tdb] Close table 'sessions0.tdb' Apr 26 03:47:26 192.168.122.209 [42197.311807] [tdb] Close table 'cache0.tdb' Apr 26 03:47:27 192.168.122.209 [42197.566814] [tdb] Close table 'filter0.tdb' Apr 26 03:47:27 192.168.122.209 [42197.567270] net_ratelimit: 11 callbacks suppressed Apr 26 03:47:27 192.168.122.209 [42197.567272] [tempesta fw] modules are stopped Apr 26 03:47:27 192.168.122.209 [42197.771581] [tempesta fw] exiting... Apr 26 03:47:27 192.168.122.209 [42197.938023] [tdb] Shutdown Tempesta DB Apr 26 03:47:27 192.168.122.209 [42198.165242] End test: http_general.test_headers.TestNoContentLengthInMethodMethodPATCH.test_request_success Apr 26 03:47:27 192.168.122.209 [42198.174671] Start test: http_general.test_headers.TestNoContentLengthInMethodMethodPOST.test_request_success Apr 26 03:47:29 192.168.122.209 [42199.351466] [tdb] Start Tempesta DB Apr 26 03:47:29 192.168.122.209 [42199.493421] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:47:30 192.168.122.209 [42200.753342] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [42200.753342] Maybe that's fine, but it's worth checking the [42200.753342] config - if there is no relations between the [42200.753342] names, then host name confusion attack is possible. Apr 26 03:47:30 192.168.122.209 [42200.871860] [tempesta fw] Configuration processing is completed. Apr 26 03:47:30 192.168.122.209 [42200.937862] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:47:31 192.168.122.209 [42201.371577] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:47:31 192.168.122.209 [42201.397309] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:47:31 192.168.122.209 [42201.422798] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:47:31 192.168.122.209 [42201.467874] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:47:31 192.168.122.209 [42201.515876] [tempesta fw] Tempesta FW is ready Apr 26 03:47:31 192.168.122.209 [42201.674962] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 03:47:31 192.168.122.209 [42201.677299] [tempesta fw] Warning: Can't create pipelined response: 127.0.0.3 Apr 26 03:47:31 192.168.122.209 [42201.679268] [tempesta fw] 127.0.0.2 "default" "POST / HTTP/1.1" 200 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400280080" Apr 26 03:47:31 192.168.122.209 [42201.693690] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 03:47:31 192.168.122.209 [42201.694783] [tempesta fw] Warning: Can't create pipelined response: 127.0.0.3 Apr 26 03:47:31 192.168.122.209 [42201.695940] [tempesta fw] 127.0.0.2 "default" "POST / HTTP/1.1" 201 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400280080" Apr 26 03:47:31 192.168.122.209 [42201.704499] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 03:47:31 192.168.122.209 [42201.706808] [tempesta fw] 127.0.0.2 "default" "POST / HTTP/1.1" 302 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400280080" Apr 26 03:47:31 192.168.122.209 [42201.714475] [tempesta fw] 127.0.0.2 "default" "POST / HTTP/1.1" 304 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400280080" Apr 26 03:47:31 192.168.122.209 [42201.724906] [tempesta fw] 127.0.0.2 "default" "POST / HTTP/1.1" 400 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400280080" Apr 26 03:47:31 192.168.122.209 [42201.735507] [tempesta fw] 127.0.0.2 "default" "POST / HTTP/1.1" 401 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400280080" Apr 26 03:47:31 192.168.122.209 [42201.745767] [tempesta fw] 127.0.0.2 "default" "POST / HTTP/1.1" 404 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400280080" Apr 26 03:47:31 192.168.122.209 [42201.756609] [tempesta fw] 127.0.0.2 "default" "POST / HTTP/1.1" 500 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400280080" Apr 26 03:47:31 192.168.122.209 [42202.235781] [tdb] Close table 'client0.tdb' Apr 26 03:47:32 192.168.122.209 [42202.424915] [tdb] Close table 'sessions0.tdb' Apr 26 03:47:35 192.168.122.209 [42205.629810] [tdb] Close table 'cache0.tdb' Apr 26 03:47:35 192.168.122.209 [42205.867191] [tdb] Close table 'filter0.tdb' Apr 26 03:47:35 192.168.122.209 [42205.867640] net_ratelimit: 11 callbacks suppressed Apr 26 03:47:35 192.168.122.209 [42205.867642] [tempesta fw] modules are stopped Apr 26 03:47:35 192.168.122.209 [42206.058496] [tempesta fw] exiting... Apr 26 03:47:35 192.168.122.209 [42206.216571] [tdb] Shutdown Tempesta DB Apr 26 03:47:36 192.168.122.209 [42206.420684] End test: http_general.test_headers.TestNoContentLengthInMethodMethodPOST.test_request_success Apr 26 03:47:36 192.168.122.209 [42206.433333] Start test: http_general.test_headers.TestNoContentLengthInMethodMethodPUT.test_request_success Apr 26 03:47:37 192.168.122.209 [42207.547761] [tdb] Start Tempesta DB Apr 26 03:47:37 192.168.122.209 [42207.698359] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:47:38 192.168.122.209 [42209.057366] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [42209.057366] Maybe that's fine, but it's worth checking the [42209.057366] config - if there is no relations between the [42209.057366] names, then host name confusion attack is possible. Apr 26 03:47:38 192.168.122.209 [42209.216073] [tempesta fw] Configuration processing is completed. Apr 26 03:47:38 192.168.122.209 [42209.267308] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:47:39 192.168.122.209 [42209.673958] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:47:39 192.168.122.209 [42209.713880] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:47:39 192.168.122.209 [42209.739231] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:47:39 192.168.122.209 [42209.780070] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:47:39 192.168.122.209 [42209.819972] [tempesta fw] Tempesta FW is ready Apr 26 03:47:39 192.168.122.209 [42209.979217] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 03:47:39 192.168.122.209 [42209.981137] [tempesta fw] Warning: Can't create pipelined response: 127.0.0.3 Apr 26 03:47:39 192.168.122.209 [42209.982841] [tempesta fw] 127.0.0.2 "default" "PUT / HTTP/1.1" 200 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400340080" Apr 26 03:47:39 192.168.122.209 [42209.991982] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 03:47:39 192.168.122.209 [42209.993826] [tempesta fw] Warning: Can't create pipelined response: 127.0.0.3 Apr 26 03:47:39 192.168.122.209 [42209.995415] [tempesta fw] 127.0.0.2 "default" "PUT / HTTP/1.1" 201 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400340080" Apr 26 03:47:39 192.168.122.209 [42210.002226] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 03:47:39 192.168.122.209 [42210.003004] [tempesta fw] 127.0.0.2 "default" "PUT / HTTP/1.1" 302 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400340080" Apr 26 03:47:39 192.168.122.209 [42210.013031] [tempesta fw] 127.0.0.2 "default" "PUT / HTTP/1.1" 304 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400340080" Apr 26 03:47:39 192.168.122.209 [42210.023013] [tempesta fw] 127.0.0.2 "default" "PUT / HTTP/1.1" 400 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400340080" Apr 26 03:47:39 192.168.122.209 [42210.033660] [tempesta fw] 127.0.0.2 "default" "PUT / HTTP/1.1" 401 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400340080" Apr 26 03:47:39 192.168.122.209 [42210.044751] [tempesta fw] 127.0.0.2 "default" "PUT / HTTP/1.1" 404 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400340080" Apr 26 03:47:39 192.168.122.209 [42210.055156] [tempesta fw] 127.0.0.2 "default" "PUT / HTTP/1.1" 500 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400340080" Apr 26 03:47:40 192.168.122.209 [42210.515980] [tdb] Close table 'client0.tdb' Apr 26 03:47:40 192.168.122.209 [42210.712546] [tdb] Close table 'sessions0.tdb' Apr 26 03:47:43 192.168.122.209 [42213.866539] [tdb] Close table 'cache0.tdb' Apr 26 03:47:43 192.168.122.209 [42214.115662] [tdb] Close table 'filter0.tdb' Apr 26 03:47:43 192.168.122.209 [42214.116466] net_ratelimit: 11 callbacks suppressed Apr 26 03:47:43 192.168.122.209 [42214.116467] [tempesta fw] modules are stopped Apr 26 03:47:44 192.168.122.209 [42214.367247] [tempesta fw] exiting... Apr 26 03:47:44 192.168.122.209 [42214.510255] [tdb] Shutdown Tempesta DB Apr 26 03:47:44 192.168.122.209 [42214.706900] End test: http_general.test_headers.TestNoContentLengthInMethodMethodPUT.test_request_success Apr 26 03:47:44 192.168.122.209 [42214.720742] Start test: http_general.test_headers.TestSmallHeader.test_small_header_name_accepted Apr 26 03:47:45 192.168.122.209 [42215.890082] [tdb] Start Tempesta DB Apr 26 03:47:45 192.168.122.209 [42216.029769] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:47:46 192.168.122.209 [42217.308170] [tempesta fw] Configuration processing is completed. Apr 26 03:47:47 192.168.122.209 [42217.358750] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:47:47 192.168.122.209 [42217.386768] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:47:47 192.168.122.209 [42217.415366] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:47:47 192.168.122.209 [42217.460131] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:47:47 192.168.122.209 [42217.500031] [tempesta fw] Tempesta FW is ready Apr 26 03:47:47 192.168.122.209 [42218.155893] [tdb] Close table 'client0.tdb' Apr 26 03:47:48 192.168.122.209 [42218.351898] [tdb] Close table 'sessions0.tdb' Apr 26 03:47:48 192.168.122.209 [42218.576730] [tdb] Close table 'filter0.tdb' Apr 26 03:47:48 192.168.122.209 [42218.577158] [tempesta fw] modules are stopped Apr 26 03:47:48 192.168.122.209 [42218.753973] [tempesta fw] exiting... Apr 26 03:47:48 192.168.122.209 [42218.921149] [tdb] Shutdown Tempesta DB Apr 26 03:47:48 192.168.122.209 [42219.150887] End test: http_general.test_headers.TestSmallHeader.test_small_header_name_accepted Apr 26 03:47:48 192.168.122.209 [42219.163021] Start test: mixed_requests.test_mixed.MixedRequests.test_connect Apr 26 03:47:53 192.168.122.209 [42223.371257] [tdb] Start Tempesta DB Apr 26 03:47:53 192.168.122.209 [42223.509220] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:47:53 192.168.122.209 [42224.036258] [tempesta fw] Configuration processing is completed. Apr 26 03:47:53 192.168.122.209 [42224.091877] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:47:53 192.168.122.209 [42224.123002] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:47:53 192.168.122.209 [42224.152212] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:47:53 192.168.122.209 [42224.236205] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:47:53 192.168.122.209 [42224.288155] [tempesta fw] Tempesta FW is ready Apr 26 03:47:54 192.168.122.209 [42224.512922] [tempesta fw] Warning: request dropped: non-idempotent requests aren't re-forwarded or re-scheduled, status 504: 127.0.0.1 Apr 26 03:47:54 192.168.122.209 [42224.520481] [tempesta fw] Warning: request dropped: non-idempotent requests aren't re-forwarded or re-scheduled, status 504: 127.0.0.1 Apr 26 03:47:54 192.168.122.209 [42224.568276] [tempesta fw] Warning: request dropped: non-idempotent requests aren't re-forwarded or re-scheduled, status 504: 127.0.0.1 Apr 26 03:47:54 192.168.122.209 [42224.588848] [tempesta fw] Warning: request dropped: non-idempotent requests aren't re-forwarded or re-scheduled, status 504: 127.0.0.1 Apr 26 03:47:54 192.168.122.209 [42224.632803] [tempesta fw] Warning: request dropped: non-idempotent requests aren't re-forwarded or re-scheduled, status 504: 127.0.0.1 Apr 26 03:47:54 192.168.122.209 [42224.640590] [tempesta fw] Warning: request dropped: non-idempotent requests aren't re-forwarded or re-scheduled, status 504: 127.0.0.1 Apr 26 03:47:54 192.168.122.209 [42224.724902] [tempesta fw] Warning: request dropped: non-idempotent requests aren't re-forwarded or re-scheduled, status 504: 127.0.0.1 Apr 26 03:47:59 192.168.122.209 [42229.869175] net_ratelimit: 19 callbacks suppressed Apr 26 03:47:59 192.168.122.209 [42229.869179] [tempesta fw] Warning: request dropped: non-idempotent requests aren't re-forwarded or re-scheduled, status 504: 127.0.0.1 Apr 26 03:48:00 192.168.122.209 [42230.665419] [tempesta fw] Warning: request dropped: non-idempotent requests aren't re-forwarded or re-scheduled, status 504: 127.0.0.1 Apr 26 03:48:04 192.168.122.209 [42234.986265] [tdb] Close table 'client0.tdb' Apr 26 03:48:04 192.168.122.209 [42235.175393] [tdb] Close table 'sessions0.tdb' Apr 26 03:48:05 192.168.122.209 [42235.429732] [tdb] Close table 'filter0.tdb' Apr 26 03:48:05 192.168.122.209 [42235.430196] [tempesta fw] modules are stopped Apr 26 03:48:05 192.168.122.209 [42235.606788] [tempesta fw] exiting... Apr 26 03:48:05 192.168.122.209 [42235.740468] [tdb] Shutdown Tempesta DB Apr 26 03:48:05 192.168.122.209 [42235.974172] End test: mixed_requests.test_mixed.MixedRequests.test_connect Apr 26 03:48:05 192.168.122.209 [42235.985749] Start test: mixed_requests.test_mixed.MixedRequests.test_get_post Apr 26 03:48:10 192.168.122.209 [42240.340530] [tdb] Start Tempesta DB Apr 26 03:48:10 192.168.122.209 [42240.504759] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:48:10 192.168.122.209 [42241.068473] [tempesta fw] Configuration processing is completed. Apr 26 03:48:10 192.168.122.209 [42241.118997] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:48:10 192.168.122.209 [42241.146231] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:48:10 192.168.122.209 [42241.173258] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:48:10 192.168.122.209 [42241.252476] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:48:10 192.168.122.209 [42241.300376] [tempesta fw] Tempesta FW is ready Apr 26 03:48:11 192.168.122.209 [42241.476953] [tempesta fw] Warning: Invalid authority: 127.0.0.1 Apr 26 03:48:11 192.168.122.209 [42241.477713] [tempesta fw] Warning: Invalid authority: 127.0.0.1 Apr 26 03:48:11 192.168.122.209 [42241.479184] [tempesta fw] Warning: Invalid authority: 127.0.0.1 Apr 26 03:48:11 192.168.122.209 [42241.480654] [tempesta fw] Warning: Invalid authority: 127.0.0.1 Apr 26 03:48:11 192.168.122.209 [42241.480909] [tempesta fw] Warning: Invalid authority: 127.0.0.1 Apr 26 03:48:11 192.168.122.209 [42241.482055] [tempesta fw] Warning: Invalid authority: 127.0.0.1 Apr 26 03:48:11 192.168.122.209 [42241.484231] [tempesta fw] Warning: Invalid authority: 127.0.0.1 Apr 26 03:48:15 192.168.122.209 [42245.508340] net_ratelimit: 12515 callbacks suppressed Apr 26 03:48:15 192.168.122.209 [42245.508354] [tempesta fw] Warning: Invalid authority: 127.0.0.1 Apr 26 03:48:15 192.168.122.209 [42245.508537] [tempesta fw] Warning: Invalid authority: 127.0.0.1 Apr 26 03:48:15 192.168.122.209 [42245.510127] [tempesta fw] Warning: Invalid authority: 127.0.0.1 Apr 26 03:48:15 192.168.122.209 [42245.511091] [tempesta fw] Warning: Invalid authority: 127.0.0.1 Apr 26 03:48:15 192.168.122.209 [42245.511117] [tempesta fw] Warning: Invalid authority: 127.0.0.1 Apr 26 03:48:15 192.168.122.209 [42245.515109] [tempesta fw] Warning: Invalid authority: 127.0.0.1 Apr 26 03:48:15 192.168.122.209 [42245.517491] [tempesta fw] Warning: Invalid authority: 127.0.0.1 Apr 26 03:48:15 192.168.122.209 [42245.518254] [tempesta fw] Warning: Invalid authority: 127.0.0.1 Apr 26 03:48:15 192.168.122.209 [42245.518773] [tempesta fw] Warning: Invalid authority: 127.0.0.1 Apr 26 03:48:15 192.168.122.209 [42245.519780] [tempesta fw] Warning: Invalid authority: 127.0.0.1 Apr 26 03:48:20 192.168.122.209 [42250.512426] net_ratelimit: 14332 callbacks suppressed Apr 26 03:48:20 192.168.122.209 [42250.512435] [tempesta fw] Warning: Invalid authority: 127.0.0.1 Apr 26 03:48:20 192.168.122.209 [42250.513690] [tempesta fw] Warning: Invalid authority: 127.0.0.1 Apr 26 03:48:20 192.168.122.209 [42250.514544] [tempesta fw] Warning: Invalid authority: 127.0.0.1 Apr 26 03:48:20 192.168.122.209 [42250.515421] [tempesta fw] Warning: Invalid authority: 127.0.0.1 Apr 26 03:48:20 192.168.122.209 [42250.516103] [tempesta fw] Warning: Invalid authority: 127.0.0.1 Apr 26 03:48:20 192.168.122.209 [42250.517150] [tempesta fw] Warning: Invalid authority: 127.0.0.1 Apr 26 03:48:20 192.168.122.209 [42250.517870] [tempesta fw] Warning: Invalid authority: 127.0.0.1 Apr 26 03:48:20 192.168.122.209 [42250.518848] [tempesta fw] Warning: Invalid authority: 127.0.0.1 Apr 26 03:48:20 192.168.122.209 [42250.518857] [tempesta fw] Warning: Invalid authority: 127.0.0.1 Apr 26 03:48:20 192.168.122.209 [42250.520385] [tempesta fw] Warning: Invalid authority: 127.0.0.1 Apr 26 03:48:21 192.168.122.209 [42251.965197] [tdb] Close table 'client0.tdb' Apr 26 03:48:21 192.168.122.209 [42252.202791] [tdb] Close table 'sessions0.tdb' Apr 26 03:48:22 192.168.122.209 [42252.479351] [tdb] Close table 'filter0.tdb' Apr 26 03:48:22 192.168.122.209 [42252.647416] [tempesta fw] exiting... Apr 26 03:48:22 192.168.122.209 [42252.783127] [tdb] Shutdown Tempesta DB Apr 26 03:48:22 192.168.122.209 [42253.041648] End test: mixed_requests.test_mixed.MixedRequests.test_get_post Apr 26 03:48:22 192.168.122.209 [42253.057859] Start test: mixed_requests.test_mixed.MixedRequests.test_head_get Apr 26 03:48:27 192.168.122.209 [42257.390315] [tdb] Start Tempesta DB Apr 26 03:48:27 192.168.122.209 [42257.581913] net_ratelimit: 2935 callbacks suppressed Apr 26 03:48:27 192.168.122.209 [42257.581918] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:48:27 192.168.122.209 [42258.140714] [tempesta fw] Configuration processing is completed. Apr 26 03:48:27 192.168.122.209 [42258.201661] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:48:27 192.168.122.209 [42258.231341] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:48:27 192.168.122.209 [42258.262385] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:48:27 192.168.122.209 [42258.332645] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:48:28 192.168.122.209 [42258.372587] [tempesta fw] Tempesta FW is ready Apr 26 03:48:38 192.168.122.209 [42269.049175] [tdb] Close table 'client0.tdb' Apr 26 03:48:38 192.168.122.209 [42269.272795] [tdb] Close table 'sessions0.tdb' Apr 26 03:48:39 192.168.122.209 [42269.520520] [tdb] Close table 'filter0.tdb' Apr 26 03:48:39 192.168.122.209 [42269.521004] [tempesta fw] modules are stopped Apr 26 03:48:39 192.168.122.209 [42269.677484] [tempesta fw] exiting... Apr 26 03:48:39 192.168.122.209 [42269.829448] [tdb] Shutdown Tempesta DB Apr 26 03:48:39 192.168.122.209 [42270.139438] End test: mixed_requests.test_mixed.MixedRequests.test_head_get Apr 26 03:48:39 192.168.122.209 [42270.150368] Start test: mixed_requests.test_mixed.MixedRequests.test_mixed Apr 26 03:48:44 192.168.122.209 [42274.404678] [tdb] Start Tempesta DB Apr 26 03:48:44 192.168.122.209 [42274.558274] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:48:44 192.168.122.209 [42275.108939] [tempesta fw] Configuration processing is completed. Apr 26 03:48:44 192.168.122.209 [42275.155711] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:48:44 192.168.122.209 [42275.183879] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:48:44 192.168.122.209 [42275.211756] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:48:44 192.168.122.209 [42275.300860] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:48:45 192.168.122.209 [42275.340835] [tempesta fw] Tempesta FW is ready Apr 26 03:48:45 192.168.122.209 [42275.705117] [tempesta fw] Warning: request dropped: non-idempotent requests aren't re-forwarded or re-scheduled, status 504: 127.0.0.1 Apr 26 03:48:45 192.168.122.209 [42275.857005] [tempesta fw] Warning: request dropped: non-idempotent requests aren't re-forwarded or re-scheduled, status 504: 127.0.0.1 Apr 26 03:48:46 192.168.122.209 [42276.413160] [tempesta fw] Warning: request dropped: non-idempotent requests aren't re-forwarded or re-scheduled, status 504: 127.0.0.1 Apr 26 03:48:55 192.168.122.209 [42286.064275] [tdb] Close table 'client0.tdb' Apr 26 03:48:55 192.168.122.209 [42286.254488] [tdb] Close table 'sessions0.tdb' Apr 26 03:48:56 192.168.122.209 [42286.515104] [tdb] Close table 'filter0.tdb' Apr 26 03:48:56 192.168.122.209 [42286.515500] [tempesta fw] modules are stopped Apr 26 03:48:56 192.168.122.209 [42286.677086] [tempesta fw] exiting... Apr 26 03:48:56 192.168.122.209 [42286.809824] [tdb] Shutdown Tempesta DB Apr 26 03:48:56 192.168.122.209 [42287.053389] End test: mixed_requests.test_mixed.MixedRequests.test_mixed Apr 26 03:48:56 192.168.122.209 [42287.060611] Start test: mixed_requests.test_mixed.MixedRequests.test_pipeline Apr 26 03:49:00 192.168.122.209 [42291.255327] [tdb] Start Tempesta DB Apr 26 03:49:01 192.168.122.209 [42291.404263] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:49:01 192.168.122.209 [42291.873127] [tempesta fw] Configuration processing is completed. Apr 26 03:49:01 192.168.122.209 [42291.932470] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:49:01 192.168.122.209 [42291.962116] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:49:01 192.168.122.209 [42291.989790] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:49:01 192.168.122.209 [42292.061086] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:49:01 192.168.122.209 [42292.101017] [tempesta fw] Tempesta FW is ready Apr 26 03:49:12 192.168.122.209 [42302.774264] [tdb] Close table 'client0.tdb' Apr 26 03:49:12 192.168.122.209 [42302.985020] [tdb] Close table 'sessions0.tdb' Apr 26 03:49:12 192.168.122.209 [42303.231422] [tdb] Close table 'filter0.tdb' Apr 26 03:49:12 192.168.122.209 [42303.231876] [tempesta fw] modules are stopped Apr 26 03:49:13 192.168.122.209 [42303.413620] [tempesta fw] exiting... Apr 26 03:49:13 192.168.122.209 [42303.547230] [tdb] Shutdown Tempesta DB Apr 26 03:49:13 192.168.122.209 [42303.779286] End test: mixed_requests.test_mixed.MixedRequests.test_pipeline Apr 26 03:49:13 192.168.122.209 [42303.797965] Start test: mixed_requests.test_mixed.MixedRequests.test_post_big Apr 26 03:49:17 192.168.122.209 [42308.137534] [tdb] Start Tempesta DB Apr 26 03:49:17 192.168.122.209 [42308.278365] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:49:18 192.168.122.209 [42308.813339] [tempesta fw] Configuration processing is completed. Apr 26 03:49:18 192.168.122.209 [42308.863046] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:49:18 192.168.122.209 [42308.890723] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:49:18 192.168.122.209 [42308.918578] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:49:18 192.168.122.209 [42308.969301] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:49:18 192.168.122.209 [42309.017241] [tempesta fw] Tempesta FW is ready Apr 26 03:49:29 192.168.122.209 [42319.699830] [tdb] Close table 'client0.tdb' Apr 26 03:49:29 192.168.122.209 [42319.889796] [tdb] Close table 'sessions0.tdb' Apr 26 03:49:29 192.168.122.209 [42320.123995] [tdb] Close table 'filter0.tdb' Apr 26 03:49:29 192.168.122.209 [42320.124445] [tempesta fw] modules are stopped Apr 26 03:49:29 192.168.122.209 [42320.325807] [tempesta fw] exiting... Apr 26 03:49:30 192.168.122.209 [42320.476056] [tdb] Shutdown Tempesta DB Apr 26 03:49:30 192.168.122.209 [42320.696594] End test: mixed_requests.test_mixed.MixedRequests.test_post_big Apr 26 03:49:30 192.168.122.209 [42320.718132] Start test: mixed_requests.test_mixed.MixedRequests.test_post_empty Apr 26 03:49:34 192.168.122.209 [42325.077382] [tdb] Start Tempesta DB Apr 26 03:49:34 192.168.122.209 [42325.230072] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:49:35 192.168.122.209 [42325.737529] [tempesta fw] Configuration processing is completed. Apr 26 03:49:35 192.168.122.209 [42325.789045] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:49:35 192.168.122.209 [42325.818493] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:49:35 192.168.122.209 [42325.845988] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:49:35 192.168.122.209 [42325.909488] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:49:35 192.168.122.209 [42325.949454] [tempesta fw] Tempesta FW is ready Apr 26 03:49:46 192.168.122.209 [42336.625775] [tdb] Close table 'client0.tdb' Apr 26 03:49:46 192.168.122.209 [42336.837242] [tdb] Close table 'sessions0.tdb' Apr 26 03:49:46 192.168.122.209 [42337.092619] [tdb] Close table 'filter0.tdb' Apr 26 03:49:46 192.168.122.209 [42337.093056] [tempesta fw] modules are stopped Apr 26 03:49:46 192.168.122.209 [42337.265517] [tempesta fw] exiting... Apr 26 03:49:47 192.168.122.209 [42337.426501] [tdb] Shutdown Tempesta DB Apr 26 03:49:47 192.168.122.209 [42337.667065] End test: mixed_requests.test_mixed.MixedRequests.test_post_empty Apr 26 03:49:47 192.168.122.209 [42337.694106] Start test: mixed_requests.test_mixed.MixedRequests.test_post_small Apr 26 03:49:51 192.168.122.209 [42341.956317] [tdb] Start Tempesta DB Apr 26 03:49:51 192.168.122.209 [42342.099328] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:49:52 192.168.122.209 [42342.625786] [tempesta fw] Configuration processing is completed. Apr 26 03:49:52 192.168.122.209 [42342.677071] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:49:52 192.168.122.209 [42342.704515] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:49:52 192.168.122.209 [42342.733175] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:49:52 192.168.122.209 [42342.801719] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:49:52 192.168.122.209 [42342.841534] [tempesta fw] Tempesta FW is ready Apr 26 03:49:53 192.168.122.209 [42343.413856] [tempesta fw] Warning: request dropped: non-idempotent requests aren't re-forwarded or re-scheduled, status 504: 127.0.0.1 Apr 26 03:49:53 192.168.122.209 [42343.417733] [tempesta fw] Warning: request dropped: non-idempotent requests aren't re-forwarded or re-scheduled, status 504: 127.0.0.1 Apr 26 03:50:03 192.168.122.209 [42353.602930] [tdb] Close table 'client0.tdb' Apr 26 03:50:03 192.168.122.209 [42353.803702] [tdb] Close table 'sessions0.tdb' Apr 26 03:50:03 192.168.122.209 [42354.060807] [tdb] Close table 'filter0.tdb' Apr 26 03:50:03 192.168.122.209 [42354.061243] [tempesta fw] modules are stopped Apr 26 03:50:03 192.168.122.209 [42354.317718] [tempesta fw] exiting... Apr 26 03:50:04 192.168.122.209 [42354.463541] [tdb] Shutdown Tempesta DB Apr 26 03:50:04 192.168.122.209 [42354.754858] End test: mixed_requests.test_mixed.MixedRequests.test_post_small Apr 26 03:50:04 192.168.122.209 [42354.773453] Start test: mixed_requests.test_mixed.MixedRequests.test_real Apr 26 03:50:08 192.168.122.209 [42359.090878] [tdb] Start Tempesta DB Apr 26 03:50:08 192.168.122.209 [42359.234584] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:50:09 192.168.122.209 [42359.786390] [tempesta fw] Configuration processing is completed. Apr 26 03:50:09 192.168.122.209 [42359.836715] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:50:09 192.168.122.209 [42359.866087] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:50:09 192.168.122.209 [42359.893428] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:50:09 192.168.122.209 [42359.973953] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:50:09 192.168.122.209 [42360.017869] [tempesta fw] Tempesta FW is ready Apr 26 03:50:09 192.168.122.209 [42360.176992] [tempesta fw] Warning: Invalid authority: 127.0.0.1 Apr 26 03:50:09 192.168.122.209 [42360.178616] [tempesta fw] Warning: Invalid authority: 127.0.0.1 Apr 26 03:50:09 192.168.122.209 [42360.178636] [tempesta fw] Warning: Invalid authority: 127.0.0.1 Apr 26 03:50:09 192.168.122.209 [42360.179350] [tempesta fw] Warning: Invalid authority: 127.0.0.1 Apr 26 03:50:09 192.168.122.209 [42360.182474] [tempesta fw] Warning: Invalid authority: 127.0.0.1 Apr 26 03:50:09 192.168.122.209 [42360.183772] [tempesta fw] Warning: Invalid authority: 127.0.0.1 Apr 26 03:50:09 192.168.122.209 [42360.184844] [tempesta fw] Warning: Invalid authority: 127.0.0.1 Apr 26 03:50:13 192.168.122.209 [42364.238130] net_ratelimit: 14469 callbacks suppressed Apr 26 03:50:13 192.168.122.209 [42364.238132] [tempesta fw] Warning: Invalid authority: 127.0.0.1 Apr 26 03:50:13 192.168.122.209 [42364.238551] [tempesta fw] Warning: Invalid authority: 127.0.0.1 Apr 26 03:50:13 192.168.122.209 [42364.239794] [tempesta fw] Warning: Invalid authority: 127.0.0.1 Apr 26 03:50:13 192.168.122.209 [42364.240992] [tempesta fw] Warning: Invalid authority: 127.0.0.1 Apr 26 03:50:13 192.168.122.209 [42364.241127] [tempesta fw] Warning: Invalid authority: 127.0.0.1 Apr 26 03:50:13 192.168.122.209 [42364.242183] [tempesta fw] Warning: Invalid authority: 127.0.0.1 Apr 26 03:50:13 192.168.122.209 [42364.243287] [tempesta fw] Warning: Invalid authority: 127.0.0.1 Apr 26 03:50:13 192.168.122.209 [42364.244238] [tempesta fw] Warning: Invalid authority: 127.0.0.1 Apr 26 03:50:13 192.168.122.209 [42364.244386] [tempesta fw] Warning: Invalid authority: 127.0.0.1 Apr 26 03:50:13 192.168.122.209 [42364.245401] [tempesta fw] Warning: Invalid authority: 127.0.0.1 Apr 26 03:50:18 192.168.122.209 [42369.242462] net_ratelimit: 15252 callbacks suppressed Apr 26 03:50:18 192.168.122.209 [42369.242464] [tempesta fw] Warning: Invalid authority: 127.0.0.1 Apr 26 03:50:18 192.168.122.209 [42369.243588] [tempesta fw] Warning: Invalid authority: 127.0.0.1 Apr 26 03:50:18 192.168.122.209 [42369.244801] [tempesta fw] Warning: Invalid authority: 127.0.0.1 Apr 26 03:50:18 192.168.122.209 [42369.245409] [tempesta fw] Warning: Invalid authority: 127.0.0.1 Apr 26 03:50:18 192.168.122.209 [42369.247547] [tempesta fw] Warning: Invalid authority: 127.0.0.1 Apr 26 03:50:18 192.168.122.209 [42369.248239] [tempesta fw] Warning: Invalid authority: 127.0.0.1 Apr 26 03:50:18 192.168.122.209 [42369.249360] [tempesta fw] Warning: Invalid authority: 127.0.0.1 Apr 26 03:50:18 192.168.122.209 [42369.250078] [tempesta fw] Warning: Invalid authority: 127.0.0.1 Apr 26 03:50:18 192.168.122.209 [42369.251160] [tempesta fw] Warning: Invalid authority: 127.0.0.1 Apr 26 03:50:18 192.168.122.209 [42369.252086] [tempesta fw] Warning: Invalid authority: 127.0.0.1 Apr 26 03:50:20 192.168.122.209 [42370.715532] [tdb] Close table 'client0.tdb' Apr 26 03:50:20 192.168.122.209 [42370.906728] [tdb] Close table 'sessions0.tdb' Apr 26 03:50:20 192.168.122.209 [42371.137631] [tdb] Close table 'filter0.tdb' Apr 26 03:50:20 192.168.122.209 [42371.304347] [tempesta fw] exiting... Apr 26 03:50:21 192.168.122.209 [42371.456396] [tdb] Shutdown Tempesta DB Apr 26 03:50:21 192.168.122.209 [42371.707254] End test: mixed_requests.test_mixed.MixedRequests.test_real Apr 26 03:50:21 192.168.122.209 [42371.716105] Start test: mixed_requests.test_mixed.MixedRequests.test_real2 Apr 26 03:50:25 192.168.122.209 [42375.951384] [tdb] Start Tempesta DB Apr 26 03:50:25 192.168.122.209 [42376.085567] net_ratelimit: 2830 callbacks suppressed Apr 26 03:50:25 192.168.122.209 [42376.085569] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:50:26 192.168.122.209 [42376.602202] [tempesta fw] Configuration processing is completed. Apr 26 03:50:26 192.168.122.209 [42376.652778] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:50:26 192.168.122.209 [42376.680713] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:50:26 192.168.122.209 [42376.708908] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:50:26 192.168.122.209 [42376.782168] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:50:26 192.168.122.209 [42376.826084] [tempesta fw] Tempesta FW is ready Apr 26 03:50:37 192.168.122.209 [42387.543878] [tdb] Close table 'client0.tdb' Apr 26 03:50:37 192.168.122.209 [42387.737958] [tdb] Close table 'sessions0.tdb' Apr 26 03:50:37 192.168.122.209 [42387.955723] [tdb] Close table 'filter0.tdb' Apr 26 03:50:37 192.168.122.209 [42387.956155] [tempesta fw] modules are stopped Apr 26 03:50:37 192.168.122.209 [42388.144408] [tempesta fw] exiting... Apr 26 03:50:37 192.168.122.209 [42388.275874] [tdb] Shutdown Tempesta DB Apr 26 03:50:38 192.168.122.209 [42388.547265] End test: mixed_requests.test_mixed.MixedRequests.test_real2 Apr 26 03:50:38 192.168.122.209 [42388.564605] Start test: mixed_requests.test_mixed.MixedRequests.test_real_pipelined Apr 26 03:50:42 192.168.122.209 [42392.899529] [tdb] Start Tempesta DB Apr 26 03:50:42 192.168.122.209 [42393.041163] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:50:43 192.168.122.209 [42393.602428] [tempesta fw] Configuration processing is completed. Apr 26 03:50:43 192.168.122.209 [42393.654386] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:50:43 192.168.122.209 [42393.690739] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:50:43 192.168.122.209 [42393.717546] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:50:43 192.168.122.209 [42393.782344] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:50:43 192.168.122.209 [42393.822274] [tempesta fw] Tempesta FW is ready Apr 26 03:50:54 192.168.122.209 [42404.493776] [tdb] Close table 'client0.tdb' Apr 26 03:50:54 192.168.122.209 [42404.698572] [tdb] Close table 'sessions0.tdb' Apr 26 03:50:54 192.168.122.209 [42404.931860] [tdb] Close table 'filter0.tdb' Apr 26 03:50:54 192.168.122.209 [42404.932281] [tempesta fw] modules are stopped Apr 26 03:50:54 192.168.122.209 [42405.155740] [tempesta fw] exiting... Apr 26 03:50:54 192.168.122.209 [42405.318673] [tdb] Shutdown Tempesta DB Apr 26 03:50:55 192.168.122.209 [42405.543574] End test: mixed_requests.test_mixed.MixedRequests.test_real_pipelined Apr 26 03:50:55 192.168.122.209 [42405.562113] Start test: msg_sequence.test_pairing.PairingTestH2.test_disconnect_client Apr 26 03:50:56 192.168.122.209 [42406.786185] [tdb] Start Tempesta DB Apr 26 03:50:56 192.168.122.209 [42406.948167] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:50:57 192.168.122.209 [42407.499788] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [42407.499788] Maybe that's fine, but it's worth checking the [42407.499788] config - if there is no relations between the [42407.499788] names, then host name confusion attack is possible. Apr 26 03:50:57 192.168.122.209 [42407.594542] [tempesta fw] Configuration processing is completed. Apr 26 03:50:57 192.168.122.209 [42407.648738] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:50:57 192.168.122.209 [42408.248388] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:50:57 192.168.122.209 [42408.321271] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:50:58 192.168.122.209 [42408.368398] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:50:58 192.168.122.209 [42408.414565] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:50:58 192.168.122.209 [42408.416318] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:50:58 192.168.122.209 [42408.470502] [tempesta fw] Tempesta FW is ready Apr 26 03:50:58 192.168.122.209 [42409.110815] [tdb] Close table 'client0.tdb' Apr 26 03:50:58 192.168.122.209 [42409.293088] [tdb] Close table 'sessions0.tdb' Apr 26 03:51:02 192.168.122.209 [42412.452943] [tdb] Close table 'cache0.tdb' Apr 26 03:51:02 192.168.122.209 [42412.691003] [tdb] Close table 'filter0.tdb' Apr 26 03:51:02 192.168.122.209 [42412.691432] [tempesta fw] modules are stopped Apr 26 03:51:02 192.168.122.209 [42412.946520] [tempesta fw] exiting... Apr 26 03:51:02 192.168.122.209 [42413.079057] [tdb] Shutdown Tempesta DB Apr 26 03:51:02 192.168.122.209 [42413.258464] End test: msg_sequence.test_pairing.PairingTestH2.test_disconnect_client Apr 26 03:51:02 192.168.122.209 [42413.281796] Start test: msg_sequence.test_pairing.PairingTestHttp.test_disconnect_client Apr 26 03:51:04 192.168.122.209 [42414.464936] [tdb] Start Tempesta DB Apr 26 03:51:04 192.168.122.209 [42414.624015] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:51:05 192.168.122.209 [42415.975890] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [42415.975890] Maybe that's fine, but it's worth checking the [42415.975890] config - if there is no relations between the [42415.975890] names, then host name confusion attack is possible. Apr 26 03:51:05 192.168.122.209 [42416.070673] [tempesta fw] Configuration processing is completed. Apr 26 03:51:05 192.168.122.209 [42416.126289] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:51:06 192.168.122.209 [42416.540298] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:51:06 192.168.122.209 [42416.565835] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:51:06 192.168.122.209 [42416.592199] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:51:06 192.168.122.209 [42416.646636] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:51:06 192.168.122.209 [42416.648479] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:51:06 192.168.122.209 [42416.698576] [tempesta fw] Tempesta FW is ready Apr 26 03:51:07 192.168.122.209 [42417.372024] [tdb] Close table 'client0.tdb' Apr 26 03:51:07 192.168.122.209 [42417.580598] [tdb] Close table 'sessions0.tdb' Apr 26 03:51:10 192.168.122.209 [42420.717000] [tdb] Close table 'cache0.tdb' Apr 26 03:51:10 192.168.122.209 [42420.978241] [tdb] Close table 'filter0.tdb' Apr 26 03:51:10 192.168.122.209 [42420.979700] [tempesta fw] modules are stopped Apr 26 03:51:10 192.168.122.209 [42421.218753] [tempesta fw] exiting... Apr 26 03:51:11 192.168.122.209 [42421.361899] [tdb] Shutdown Tempesta DB Apr 26 03:51:11 192.168.122.209 [42421.565078] End test: msg_sequence.test_pairing.PairingTestHttp.test_disconnect_client Apr 26 03:51:11 192.168.122.209 [42421.589867] Start test: multiple_listeners.test_mixed.TestMixedListeners.test_h2_https_success Apr 26 03:51:12 192.168.122.209 [42422.976544] [tdb] Start Tempesta DB Apr 26 03:51:12 192.168.122.209 [42423.129517] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:51:14 192.168.122.209 [42424.879998] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [42424.879998] Maybe that's fine, but it's worth checking the [42424.879998] config - if there is no relations between the [42424.879998] names, then host name confusion attack is possible. Apr 26 03:51:14 192.168.122.209 [42424.998746] [tempesta fw] Configuration processing is completed. Apr 26 03:51:14 192.168.122.209 [42425.064350] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:51:14 192.168.122.209 [42425.094896] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:51:14 192.168.122.209 [42425.126342] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:51:14 192.168.122.209 [42425.203176] [tempesta fw] Open listen socket on: 127.0.0.1:4444 Apr 26 03:51:14 192.168.122.209 [42425.204854] [tempesta fw] Open listen socket on: 127.0.0.1:4433 Apr 26 03:51:14 192.168.122.209 [42425.206716] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 03:51:14 192.168.122.209 [42425.254687] [tempesta fw] Tempesta FW is ready Apr 26 03:51:15 192.168.122.209 [42426.041211] [tdb] Close table 'client0.tdb' Apr 26 03:51:15 192.168.122.209 [42426.219906] [tdb] Close table 'sessions0.tdb' Apr 26 03:51:16 192.168.122.209 [42426.474383] [tdb] Close table 'filter0.tdb' Apr 26 03:51:16 192.168.122.209 [42426.474868] [tempesta fw] modules are stopped Apr 26 03:51:16 192.168.122.209 [42426.704371] [tempesta fw] exiting... Apr 26 03:51:16 192.168.122.209 [42426.849399] [tdb] Shutdown Tempesta DB Apr 26 03:51:16 192.168.122.209 [42427.123628] End test: multiple_listeners.test_mixed.TestMixedListeners.test_h2_https_success Apr 26 03:51:16 192.168.122.209 [42427.137445] Start test: multiple_listeners.test_mixed.TestMixedListeners.test_mixed_h2_success Apr 26 03:51:18 192.168.122.209 [42428.370029] [tdb] Start Tempesta DB Apr 26 03:51:18 192.168.122.209 [42428.528209] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:51:19 192.168.122.209 [42429.416034] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [42429.416034] Maybe that's fine, but it's worth checking the [42429.416034] config - if there is no relations between the [42429.416034] names, then host name confusion attack is possible. Apr 26 03:51:19 192.168.122.209 [42429.550797] [tempesta fw] Configuration processing is completed. Apr 26 03:51:19 192.168.122.209 [42429.607468] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:51:19 192.168.122.209 [42429.637077] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:51:19 192.168.122.209 [42429.664749] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:51:19 192.168.122.209 [42429.742818] [tempesta fw] Open listen socket on: 127.0.0.1:4444 Apr 26 03:51:19 192.168.122.209 [42429.744690] [tempesta fw] Open listen socket on: 127.0.0.1:4433 Apr 26 03:51:19 192.168.122.209 [42429.746453] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 03:51:19 192.168.122.209 [42429.790742] [tempesta fw] Tempesta FW is ready Apr 26 03:51:19 192.168.122.209 [42430.036725] [tempesta tls] Warning: [::ffff:127.0.0.1] ClientHello: cannot find matching ALPN for h2 Apr 26 03:51:20 192.168.122.209 [42430.491760] [tdb] Close table 'client0.tdb' Apr 26 03:51:20 192.168.122.209 [42430.685527] [tdb] Close table 'sessions0.tdb' Apr 26 03:51:20 192.168.122.209 [42430.932071] [tdb] Close table 'filter0.tdb' Apr 26 03:51:20 192.168.122.209 [42430.932510] [tempesta fw] modules are stopped Apr 26 03:51:20 192.168.122.209 [42431.151304] [tempesta fw] exiting... Apr 26 03:51:20 192.168.122.209 [42431.287068] [tdb] Shutdown Tempesta DB Apr 26 03:51:21 192.168.122.209 [42431.573367] End test: multiple_listeners.test_mixed.TestMixedListeners.test_mixed_h2_success Apr 26 03:51:21 192.168.122.209 [42431.594181] Start test: multiple_listeners.test_mixed.TestMixedListeners.test_mixed_https_success Apr 26 03:51:22 192.168.122.209 [42432.762534] [tdb] Start Tempesta DB Apr 26 03:51:22 192.168.122.209 [42432.909229] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:51:23 192.168.122.209 [42433.864204] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [42433.864204] Maybe that's fine, but it's worth checking the [42433.864204] config - if there is no relations between the [42433.864204] names, then host name confusion attack is possible. Apr 26 03:51:23 192.168.122.209 [42433.982899] [tempesta fw] Configuration processing is completed. Apr 26 03:51:23 192.168.122.209 [42434.039331] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:51:23 192.168.122.209 [42434.068538] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:51:23 192.168.122.209 [42434.097285] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:51:23 192.168.122.209 [42434.162878] [tempesta fw] Open listen socket on: 127.0.0.1:4444 Apr 26 03:51:23 192.168.122.209 [42434.164758] [tempesta fw] Open listen socket on: 127.0.0.1:4433 Apr 26 03:51:23 192.168.122.209 [42434.166463] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 03:51:23 192.168.122.209 [42434.206814] [tempesta fw] Tempesta FW is ready Apr 26 03:51:24 192.168.122.209 [42434.472502] [tempesta tls] Warning: [::ffff:127.0.0.1] ClientHello: cannot find matching ALPN for http/1.1 Apr 26 03:51:24 192.168.122.209 [42434.960638] [tdb] Close table 'client0.tdb' Apr 26 03:51:24 192.168.122.209 [42435.167983] [tdb] Close table 'sessions0.tdb' Apr 26 03:51:25 192.168.122.209 [42435.393202] [tdb] Close table 'filter0.tdb' Apr 26 03:51:25 192.168.122.209 [42435.393632] [tempesta fw] modules are stopped Apr 26 03:51:25 192.168.122.209 [42435.628570] [tempesta fw] exiting... Apr 26 03:51:25 192.168.122.209 [42435.768479] [tdb] Shutdown Tempesta DB Apr 26 03:51:25 192.168.122.209 [42435.981855] End test: multiple_listeners.test_mixed.TestMixedListeners.test_mixed_https_success Apr 26 03:51:25 192.168.122.209 [42436.014283] Start test: multiple_listeners.test_multiple_listening.TestMultipleListening.test_multiple_listeners_success Apr 26 03:51:27 192.168.122.209 [42437.569054] [tdb] Start Tempesta DB Apr 26 03:51:27 192.168.122.209 [42437.734182] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:51:32 192.168.122.209 [42442.796300] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [42442.796300] Maybe that's fine, but it's worth checking the [42442.796300] config - if there is no relations between the [42442.796300] names, then host name confusion attack is possible. Apr 26 03:51:32 192.168.122.209 [42442.918990] [tempesta fw] Configuration processing is completed. Apr 26 03:51:32 192.168.122.209 [42442.987225] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:51:32 192.168.122.209 [42443.020108] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:51:32 192.168.122.209 [42443.055740] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:51:32 192.168.122.209 [42443.135030] [tempesta fw] Open listen socket on: 127.0.2.5:8086 Apr 26 03:51:32 192.168.122.209 [42443.136823] [tempesta fw] Open listen socket on: 127.0.2.7:8097 Apr 26 03:51:32 192.168.122.209 [42443.138562] [tempesta fw] Open listen socket on: 127.0.2.5:8088 Apr 26 03:51:32 192.168.122.209 [42443.140908] [tempesta fw] Open listen socket on: 127.0.2.7:8099 Apr 26 03:51:32 192.168.122.209 [42443.142666] [tempesta fw] Open listen socket on: [::1]:6604 Apr 26 03:51:32 192.168.122.209 [42443.144343] [tempesta fw] Open listen socket on: 127.0.1.4:8084 Apr 26 03:51:32 192.168.122.209 [42443.146048] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:51:32 192.168.122.209 [42443.147696] [tempesta fw] Open listen socket on: [::1]:8082 Apr 26 03:51:32 192.168.122.209 [42443.190963] [tempesta fw] Tempesta FW is ready Apr 26 03:51:38 192.168.122.209 [42449.333301] [tdb] Close table 'client0.tdb' Apr 26 03:51:39 192.168.122.209 [42449.538169] [tdb] Close table 'sessions0.tdb' Apr 26 03:51:39 192.168.122.209 [42449.765917] [tdb] Close table 'filter0.tdb' Apr 26 03:51:39 192.168.122.209 [42449.766355] net_ratelimit: 98 callbacks suppressed Apr 26 03:51:39 192.168.122.209 [42449.766357] [tempesta fw] modules are stopped Apr 26 03:51:39 192.168.122.209 [42449.972617] [tempesta fw] exiting... Apr 26 03:51:39 192.168.122.209 [42450.120865] [tdb] Shutdown Tempesta DB Apr 26 03:51:40 192.168.122.209 [42450.429478] End test: multiple_listeners.test_multiple_listening.TestMultipleListening.test_multiple_listeners_success Apr 26 03:51:40 192.168.122.209 [42450.455408] Start test: nonidempotent.test_nonidempotent.NonIdempotentH1SchedTest.test Apr 26 03:51:41 192.168.122.209 [42451.898329] [tdb] Start Tempesta DB Apr 26 03:51:41 192.168.122.209 [42452.043806] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:51:42 192.168.122.209 [42452.655438] [tempesta fw] Configuration processing is completed. Apr 26 03:51:42 192.168.122.209 [42452.706931] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:51:42 192.168.122.209 [42452.735009] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:51:42 192.168.122.209 [42452.762672] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:51:42 192.168.122.209 [42452.851088] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:51:42 192.168.122.209 [42452.895036] [tempesta fw] Tempesta FW is ready Apr 26 03:51:46 192.168.122.209 [42456.509015] [tdb] Close table 'client0.tdb' Apr 26 03:51:46 192.168.122.209 [42456.712499] [tdb] Close table 'sessions0.tdb' Apr 26 03:51:46 192.168.122.209 [42456.932346] [tdb] Close table 'filter0.tdb' Apr 26 03:51:46 192.168.122.209 [42456.932799] [tempesta fw] modules are stopped Apr 26 03:51:46 192.168.122.209 [42457.115050] [tempesta fw] exiting... Apr 26 03:51:46 192.168.122.209 [42457.241695] [tdb] Shutdown Tempesta DB Apr 26 03:51:47 192.168.122.209 [42457.520614] End test: nonidempotent.test_nonidempotent.NonIdempotentH1SchedTest.test Apr 26 03:51:47 192.168.122.209 [42457.551950] Start test: nonidempotent.test_nonidempotent.NonIdempotentH2SchedTest.test Apr 26 03:51:48 192.168.122.209 [42458.930446] [tdb] Start Tempesta DB Apr 26 03:51:48 192.168.122.209 [42459.084755] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:51:49 192.168.122.209 [42459.732580] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [42459.732580] Maybe that's fine, but it's worth checking the [42459.732580] config - if there is no relations between the [42459.732580] names, then host name confusion attack is possible. Apr 26 03:51:49 192.168.122.209 [42459.863191] [tempesta fw] Configuration processing is completed. Apr 26 03:51:49 192.168.122.209 [42459.915879] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:51:49 192.168.122.209 [42459.948540] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:51:49 192.168.122.209 [42459.976448] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:51:49 192.168.122.209 [42460.051204] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:51:49 192.168.122.209 [42460.091171] [tempesta fw] Tempesta FW is ready Apr 26 03:51:53 192.168.122.209 [42463.733213] [tdb] Close table 'client0.tdb' Apr 26 03:51:53 192.168.122.209 [42463.935136] [tdb] Close table 'sessions0.tdb' Apr 26 03:51:53 192.168.122.209 [42464.169483] [tdb] Close table 'filter0.tdb' Apr 26 03:51:53 192.168.122.209 [42464.169912] [tempesta fw] modules are stopped Apr 26 03:51:54 192.168.122.209 [42464.372071] [tempesta fw] exiting... Apr 26 03:51:54 192.168.122.209 [42464.506687] [tdb] Shutdown Tempesta DB Apr 26 03:51:54 192.168.122.209 [42464.745158] End test: nonidempotent.test_nonidempotent.NonIdempotentH2SchedTest.test Apr 26 03:51:54 192.168.122.209 [42464.766161] Start test: nonidempotent.test_nonidempotent.NotRetryNonIdempotentH1Test.test Apr 26 03:51:55 192.168.122.209 [42465.807913] [tdb] Start Tempesta DB Apr 26 03:51:55 192.168.122.209 [42465.958048] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:51:56 192.168.122.209 [42466.407297] [tempesta fw] Configuration processing is completed. Apr 26 03:51:56 192.168.122.209 [42466.460563] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:51:56 192.168.122.209 [42466.488353] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:51:56 192.168.122.209 [42466.516886] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:51:56 192.168.122.209 [42466.571265] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:51:56 192.168.122.209 [42466.611208] [tempesta fw] Tempesta FW is ready Apr 26 03:51:56 192.168.122.209 [42466.771403] [tempesta fw] Warning: request dropped: non-idempotent requests aren't re-forwarded or re-scheduled, status 504: 127.0.0.2 Apr 26 03:51:56 192.168.122.209 [42467.212461] [tdb] Close table 'client0.tdb' Apr 26 03:51:57 192.168.122.209 [42467.402759] [tdb] Close table 'sessions0.tdb' Apr 26 03:51:57 192.168.122.209 [42467.698831] [tdb] Close table 'filter0.tdb' Apr 26 03:51:57 192.168.122.209 [42467.699292] [tempesta fw] modules are stopped Apr 26 03:51:57 192.168.122.209 [42467.871260] [tempesta fw] exiting... Apr 26 03:51:57 192.168.122.209 [42467.996133] [tdb] Shutdown Tempesta DB Apr 26 03:51:57 192.168.122.209 [42468.206429] End test: nonidempotent.test_nonidempotent.NotRetryNonIdempotentH1Test.test Apr 26 03:51:57 192.168.122.209 [42468.238959] Start test: nonidempotent.test_nonidempotent.NotRetryNonIdempotentH2Test.test Apr 26 03:51:59 192.168.122.209 [42469.354643] [tdb] Start Tempesta DB Apr 26 03:51:59 192.168.122.209 [42469.512424] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:51:59 192.168.122.209 [42469.996588] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [42469.996588] Maybe that's fine, but it's worth checking the [42469.996588] config - if there is no relations between the [42469.996588] names, then host name confusion attack is possible. Apr 26 03:51:59 192.168.122.209 [42470.111361] [tempesta fw] Configuration processing is completed. Apr 26 03:51:59 192.168.122.209 [42470.162569] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:51:59 192.168.122.209 [42470.193090] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:51:59 192.168.122.209 [42470.221510] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:51:59 192.168.122.209 [42470.291271] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:51:59 192.168.122.209 [42470.339276] [tempesta fw] Tempesta FW is ready Apr 26 03:52:00 192.168.122.209 [42470.503385] [tempesta fw] Warning: request dropped: non-idempotent requests aren't re-forwarded or re-scheduled, status 504: 127.0.0.2 Apr 26 03:52:00 192.168.122.209 [42471.014880] [tdb] Close table 'client0.tdb' Apr 26 03:52:00 192.168.122.209 [42471.206787] [tdb] Close table 'sessions0.tdb' Apr 26 03:52:01 192.168.122.209 [42471.436901] [tdb] Close table 'filter0.tdb' Apr 26 03:52:01 192.168.122.209 [42471.437322] [tempesta fw] modules are stopped Apr 26 03:52:01 192.168.122.209 [42471.676831] [tempesta fw] exiting... Apr 26 03:52:01 192.168.122.209 [42471.811663] [tdb] Shutdown Tempesta DB Apr 26 03:52:01 192.168.122.209 [42472.078878] End test: nonidempotent.test_nonidempotent.NotRetryNonIdempotentH2Test.test Apr 26 03:52:01 192.168.122.209 [42472.096596] Start test: nonidempotent.test_nonidempotent.NotRetryNonIdempotentPostH2Test.test Apr 26 03:52:02 192.168.122.209 [42473.336463] [tdb] Start Tempesta DB Apr 26 03:52:03 192.168.122.209 [42473.477920] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:52:03 192.168.122.209 [42474.052627] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [42474.052627] Maybe that's fine, but it's worth checking the [42474.052627] config - if there is no relations between the [42474.052627] names, then host name confusion attack is possible. Apr 26 03:52:03 192.168.122.209 [42474.179645] [tempesta fw] Configuration processing is completed. Apr 26 03:52:03 192.168.122.209 [42474.226084] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:52:03 192.168.122.209 [42474.253573] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:52:03 192.168.122.209 [42474.280967] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:52:03 192.168.122.209 [42474.327417] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:52:04 192.168.122.209 [42474.371328] [tempesta fw] Tempesta FW is ready Apr 26 03:52:04 192.168.122.209 [42474.519762] [tempesta fw] Warning: request dropped: non-idempotent requests aren't re-forwarded or re-scheduled, status 504: 127.0.0.2 Apr 26 03:52:04 192.168.122.209 [42474.957846] [tdb] Close table 'client0.tdb' Apr 26 03:52:04 192.168.122.209 [42475.134500] [tdb] Close table 'sessions0.tdb' Apr 26 03:52:05 192.168.122.209 [42475.399554] [tdb] Close table 'filter0.tdb' Apr 26 03:52:05 192.168.122.209 [42475.399989] [tempesta fw] modules are stopped Apr 26 03:52:05 192.168.122.209 [42475.615400] [tempesta fw] exiting... Apr 26 03:52:05 192.168.122.209 [42475.758558] [tdb] Shutdown Tempesta DB Apr 26 03:52:05 192.168.122.209 [42476.004747] End test: nonidempotent.test_nonidempotent.NotRetryNonIdempotentPostH2Test.test Apr 26 03:52:05 192.168.122.209 [42476.034674] Start test: nonidempotent.test_nonidempotent.RetryNonIdempotenRevOrderH1Test.test Apr 26 03:52:06 192.168.122.209 [42477.175950] [tdb] Start Tempesta DB Apr 26 03:52:06 192.168.122.209 [42477.320910] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:52:07 192.168.122.209 [42477.867470] [tempesta fw] Configuration processing is completed. Apr 26 03:52:07 192.168.122.209 [42477.923605] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:52:07 192.168.122.209 [42477.953299] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:52:07 192.168.122.209 [42477.983009] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:52:07 192.168.122.209 [42478.047411] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:52:07 192.168.122.209 [42478.087377] [tempesta fw] Tempesta FW is ready Apr 26 03:52:08 192.168.122.209 [42478.672407] [tdb] Close table 'client0.tdb' Apr 26 03:52:08 192.168.122.209 [42478.904877] [tdb] Close table 'sessions0.tdb' Apr 26 03:52:08 192.168.122.209 [42479.143313] [tdb] Close table 'filter0.tdb' Apr 26 03:52:08 192.168.122.209 [42479.143764] [tempesta fw] modules are stopped Apr 26 03:52:08 192.168.122.209 [42479.339626] [tempesta fw] exiting... Apr 26 03:52:09 192.168.122.209 [42479.465039] [tdb] Shutdown Tempesta DB Apr 26 03:52:09 192.168.122.209 [42479.722342] End test: nonidempotent.test_nonidempotent.RetryNonIdempotenRevOrderH1Test.test Apr 26 03:52:09 192.168.122.209 [42479.748322] Start test: nonidempotent.test_nonidempotent.RetryNonIdempotentH1Test.test Apr 26 03:52:10 192.168.122.209 [42480.997491] [tdb] Start Tempesta DB Apr 26 03:52:10 192.168.122.209 [42481.168542] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:52:11 192.168.122.209 [42481.684360] [tempesta fw] Configuration processing is completed. Apr 26 03:52:11 192.168.122.209 [42481.743645] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:52:11 192.168.122.209 [42481.772035] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:52:11 192.168.122.209 [42481.801511] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:52:11 192.168.122.209 [42481.863498] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:52:11 192.168.122.209 [42481.915419] [tempesta fw] Tempesta FW is ready Apr 26 03:52:12 192.168.122.209 [42482.462868] [tdb] Close table 'client0.tdb' Apr 26 03:52:12 192.168.122.209 [42482.654579] [tdb] Close table 'sessions0.tdb' Apr 26 03:52:12 192.168.122.209 [42482.909664] [tdb] Close table 'filter0.tdb' Apr 26 03:52:12 192.168.122.209 [42482.910108] [tempesta fw] modules are stopped Apr 26 03:52:12 192.168.122.209 [42483.081007] [tempesta fw] exiting... Apr 26 03:52:12 192.168.122.209 [42483.225517] [tdb] Shutdown Tempesta DB Apr 26 03:52:13 192.168.122.209 [42483.482336] End test: nonidempotent.test_nonidempotent.RetryNonIdempotentH1Test.test Apr 26 03:52:13 192.168.122.209 [42483.509007] Start test: nonidempotent.test_nonidempotent.RetryNonIdempotentH2Test.test Apr 26 03:52:14 192.168.122.209 [42484.717448] [tdb] Start Tempesta DB Apr 26 03:52:14 192.168.122.209 [42484.861174] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:52:15 192.168.122.209 [42485.452816] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [42485.452816] Maybe that's fine, but it's worth checking the [42485.452816] config - if there is no relations between the [42485.452816] names, then host name confusion attack is possible. Apr 26 03:52:15 192.168.122.209 [42485.591514] [tempesta fw] Configuration processing is completed. Apr 26 03:52:15 192.168.122.209 [42485.642538] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:52:15 192.168.122.209 [42485.680594] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:52:15 192.168.122.209 [42485.707920] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:52:15 192.168.122.209 [42485.751505] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:52:15 192.168.122.209 [42485.799469] [tempesta fw] Tempesta FW is ready Apr 26 03:52:16 192.168.122.209 [42486.415666] [tdb] Close table 'client0.tdb' Apr 26 03:52:16 192.168.122.209 [42486.616120] [tdb] Close table 'sessions0.tdb' Apr 26 03:52:16 192.168.122.209 [42486.850755] [tdb] Close table 'filter0.tdb' Apr 26 03:52:16 192.168.122.209 [42486.851200] [tempesta fw] modules are stopped Apr 26 03:52:16 192.168.122.209 [42487.056142] [tempesta fw] exiting... Apr 26 03:52:16 192.168.122.209 [42487.205946] [tdb] Shutdown Tempesta DB Apr 26 03:52:17 192.168.122.209 [42487.450851] End test: nonidempotent.test_nonidempotent.RetryNonIdempotentH2Test.test Apr 26 03:52:17 192.168.122.209 [42487.481165] Start test: nonidempotent.test_nonidempotent.RetryNonIdempotentPostH1Test.test Apr 26 03:52:18 192.168.122.209 [42488.673163] [tdb] Start Tempesta DB Apr 26 03:52:18 192.168.122.209 [42488.822485] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:52:19 192.168.122.209 [42489.359579] [tempesta fw] Configuration processing is completed. Apr 26 03:52:19 192.168.122.209 [42489.426451] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:52:19 192.168.122.209 [42489.455138] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:52:19 192.168.122.209 [42489.483260] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:52:19 192.168.122.209 [42489.539600] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:52:19 192.168.122.209 [42489.595520] [tempesta fw] Tempesta FW is ready Apr 26 03:52:19 192.168.122.209 [42490.220295] [tdb] Close table 'client0.tdb' Apr 26 03:52:20 192.168.122.209 [42490.408866] [tdb] Close table 'sessions0.tdb' Apr 26 03:52:20 192.168.122.209 [42490.628467] [tdb] Close table 'filter0.tdb' Apr 26 03:52:20 192.168.122.209 [42490.628901] [tempesta fw] modules are stopped Apr 26 03:52:20 192.168.122.209 [42490.844776] [tempesta fw] exiting... Apr 26 03:52:20 192.168.122.209 [42490.987260] [tdb] Shutdown Tempesta DB Apr 26 03:52:20 192.168.122.209 [42491.243589] End test: nonidempotent.test_nonidempotent.RetryNonIdempotentPostH1Test.test Apr 26 03:52:20 192.168.122.209 [42491.270187] Start test: nonidempotent.test_nonidempotent.RetryNonIdempotentPostH2Test.test Apr 26 03:52:22 192.168.122.209 [42492.460136] [tdb] Start Tempesta DB Apr 26 03:52:22 192.168.122.209 [42492.596953] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:52:22 192.168.122.209 [42493.180900] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [42493.180900] Maybe that's fine, but it's worth checking the [42493.180900] config - if there is no relations between the [42493.180900] names, then host name confusion attack is possible. Apr 26 03:52:22 192.168.122.209 [42493.299956] [tempesta fw] Configuration processing is completed. Apr 26 03:52:23 192.168.122.209 [42493.350114] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:52:23 192.168.122.209 [42493.377587] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 03:52:23 192.168.122.209 [42493.405163] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 03:52:23 192.168.122.209 [42493.463618] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:52:23 192.168.122.209 [42493.503547] [tempesta fw] Tempesta FW is ready Apr 26 03:52:23 192.168.122.209 [42494.129311] [tdb] Close table 'client0.tdb' Apr 26 03:52:23 192.168.122.209 [42494.325515] [tdb] Close table 'sessions0.tdb' Apr 26 03:52:24 192.168.122.209 [42494.576614] [tdb] Close table 'filter0.tdb' Apr 26 03:52:24 192.168.122.209 [42494.577053] [tempesta fw] modules are stopped Apr 26 03:52:24 192.168.122.209 [42494.760214] [tempesta fw] exiting... Apr 26 03:52:24 192.168.122.209 [42494.903161] [tdb] Shutdown Tempesta DB Apr 26 03:52:24 192.168.122.209 [42495.166316] End test: nonidempotent.test_nonidempotent.RetryNonIdempotentPostH2Test.test Apr 26 03:52:24 192.168.122.209 [42495.201759] Start test: normalization.test_http_multipart.ConfigParameterAbsent.test Apr 26 03:52:26 192.168.122.209 [42496.351297] [tdb] Start Tempesta DB Apr 26 03:52:26 192.168.122.209 [42496.507551] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:52:26 192.168.122.209 [42497.119676] [tempesta fw] Configuration processing is completed. Apr 26 03:52:26 192.168.122.209 [42497.184420] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:52:27 192.168.122.209 [42497.798740] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:52:27 192.168.122.209 [42497.877817] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:52:27 192.168.122.209 [42497.921117] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:52:27 192.168.122.209 [42497.979666] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:52:27 192.168.122.209 [42498.027633] [tempesta fw] Tempesta FW is ready Apr 26 03:52:28 192.168.122.209 [42498.592768] [tdb] Close table 'client0.tdb' Apr 26 03:52:28 192.168.122.209 [42498.799382] [tdb] Close table 'sessions0.tdb' Apr 26 03:52:31 192.168.122.209 [42501.910422] [tdb] Close table 'cache0.tdb' Apr 26 03:52:31 192.168.122.209 [42502.127544] [tdb] Close table 'filter0.tdb' Apr 26 03:52:31 192.168.122.209 [42502.127996] [tempesta fw] modules are stopped Apr 26 03:52:31 192.168.122.209 [42502.333820] [tempesta fw] exiting... Apr 26 03:52:32 192.168.122.209 [42502.487609] [tdb] Shutdown Tempesta DB Apr 26 03:52:32 192.168.122.209 [42502.764077] End test: normalization.test_http_multipart.ConfigParameterAbsent.test Apr 26 03:52:32 192.168.122.209 [42502.785589] Start test: normalization.test_http_multipart.ConfigParameterAtLocation.test Apr 26 03:52:33 192.168.122.209 [42504.052091] [tdb] Start Tempesta DB Apr 26 03:52:33 192.168.122.209 [42504.200930] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:52:35 192.168.122.209 [42505.640084] [tempesta fw] Configuration processing is completed. Apr 26 03:52:35 192.168.122.209 [42505.690461] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:52:35 192.168.122.209 [42506.097106] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:52:35 192.168.122.209 [42506.122610] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:52:35 192.168.122.209 [42506.148141] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:52:35 192.168.122.209 [42506.187765] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:52:35 192.168.122.209 [42506.247738] [tempesta fw] Tempesta FW is ready Apr 26 03:52:36 192.168.122.209 [42506.900645] [tdb] Close table 'client0.tdb' Apr 26 03:52:36 192.168.122.209 [42507.141519] [tdb] Close table 'sessions0.tdb' Apr 26 03:52:39 192.168.122.209 [42510.317535] [tdb] Close table 'cache0.tdb' Apr 26 03:52:40 192.168.122.209 [42510.555908] [tdb] Close table 'filter0.tdb' Apr 26 03:52:40 192.168.122.209 [42510.556340] [tempesta fw] modules are stopped Apr 26 03:52:40 192.168.122.209 [42510.756073] [tempesta fw] exiting... Apr 26 03:52:40 192.168.122.209 [42510.895077] [tdb] Shutdown Tempesta DB Apr 26 03:52:40 192.168.122.209 [42511.136140] End test: normalization.test_http_multipart.ConfigParameterAtLocation.test Apr 26 03:52:40 192.168.122.209 [42511.156636] Start test: normalization.test_http_multipart.ConfigParameterAtTopLevel.test Apr 26 03:52:42 192.168.122.209 [42512.366113] [tdb] Start Tempesta DB Apr 26 03:52:42 192.168.122.209 [42512.512117] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:52:43 192.168.122.209 [42513.919970] [tempesta fw] Configuration processing is completed. Apr 26 03:52:43 192.168.122.209 [42513.973689] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:52:44 192.168.122.209 [42514.402491] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:52:44 192.168.122.209 [42514.428877] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:52:44 192.168.122.209 [42514.456153] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:52:44 192.168.122.209 [42514.495881] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:52:44 192.168.122.209 [42514.535844] [tempesta fw] Tempesta FW is ready Apr 26 03:52:44 192.168.122.209 [42515.148261] [tdb] Close table 'client0.tdb' Apr 26 03:52:44 192.168.122.209 [42515.337503] [tdb] Close table 'sessions0.tdb' Apr 26 03:52:48 192.168.122.209 [42518.533903] [tdb] Close table 'cache0.tdb' Apr 26 03:52:48 192.168.122.209 [42518.784734] [tdb] Close table 'filter0.tdb' Apr 26 03:52:48 192.168.122.209 [42518.785179] [tempesta fw] modules are stopped Apr 26 03:52:48 192.168.122.209 [42518.996163] [tempesta fw] exiting... Apr 26 03:52:48 192.168.122.209 [42519.127848] [tdb] Shutdown Tempesta DB Apr 26 03:52:48 192.168.122.209 [42519.332231] End test: normalization.test_http_multipart.ConfigParameterAtTopLevel.test Apr 26 03:52:49 192.168.122.209 [42519.345226] Start test: normalization.test_http_multipart.ConfigParameterAtVhost.test Apr 26 03:52:50 192.168.122.209 [42520.506636] [tdb] Start Tempesta DB Apr 26 03:52:50 192.168.122.209 [42520.643521] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:52:51 192.168.122.209 [42522.020304] [tempesta fw] Configuration processing is completed. Apr 26 03:52:51 192.168.122.209 [42522.086854] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:52:52 192.168.122.209 [42522.502986] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:52:52 192.168.122.209 [42522.528791] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:52:52 192.168.122.209 [42522.555412] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:52:52 192.168.122.209 [42522.599926] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:52:52 192.168.122.209 [42522.639941] [tempesta fw] Tempesta FW is ready Apr 26 03:52:52 192.168.122.209 [42523.234810] [tdb] Close table 'client0.tdb' Apr 26 03:52:53 192.168.122.209 [42523.431232] [tdb] Close table 'sessions0.tdb' Apr 26 03:52:56 192.168.122.209 [42526.567016] [tdb] Close table 'cache0.tdb' Apr 26 03:52:56 192.168.122.209 [42526.826633] [tdb] Close table 'filter0.tdb' Apr 26 03:52:56 192.168.122.209 [42526.827066] [tempesta fw] modules are stopped Apr 26 03:52:56 192.168.122.209 [42527.027340] [tempesta fw] exiting... Apr 26 03:52:56 192.168.122.209 [42527.174725] [tdb] Shutdown Tempesta DB Apr 26 03:52:57 192.168.122.209 [42527.412299] End test: normalization.test_http_multipart.ConfigParameterAtVhost.test Apr 26 03:52:57 192.168.122.209 [42527.438063] Start test: normalization.test_http_multipart.ContentTypeHeaderReconstructTest.test_replacement_escaped Apr 26 03:52:58 192.168.122.209 [42528.603255] [tdb] Start Tempesta DB Apr 26 03:52:58 192.168.122.209 [42528.748116] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:52:59 192.168.122.209 [42530.224073] [tempesta fw] Configuration processing is completed. Apr 26 03:52:59 192.168.122.209 [42530.281839] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:53:00 192.168.122.209 [42530.700785] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:53:00 192.168.122.209 [42530.734796] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:53:00 192.168.122.209 [42530.760715] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:53:00 192.168.122.209 [42530.804092] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:53:00 192.168.122.209 [42530.852039] [tempesta fw] Tempesta FW is ready Apr 26 03:53:01 192.168.122.209 [42531.458144] [tdb] Close table 'client0.tdb' Apr 26 03:53:01 192.168.122.209 [42531.667343] [tdb] Close table 'sessions0.tdb' Apr 26 03:53:04 192.168.122.209 [42534.772994] [tdb] Close table 'cache0.tdb' Apr 26 03:53:04 192.168.122.209 [42535.021182] [tdb] Close table 'filter0.tdb' Apr 26 03:53:04 192.168.122.209 [42535.021613] [tempesta fw] modules are stopped Apr 26 03:53:04 192.168.122.209 [42535.283943] [tempesta fw] exiting... Apr 26 03:53:05 192.168.122.209 [42535.448728] [tdb] Shutdown Tempesta DB Apr 26 03:53:05 192.168.122.209 [42535.667305] End test: normalization.test_http_multipart.ContentTypeHeaderReconstructTest.test_replacement_escaped Apr 26 03:53:05 192.168.122.209 [42535.695505] Start test: normalization.test_http_multipart.ContentTypeHeaderReconstructTest.test_replacement_quoted Apr 26 03:53:06 192.168.122.209 [42536.874853] [tdb] Start Tempesta DB Apr 26 03:53:06 192.168.122.209 [42537.023090] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:53:08 192.168.122.209 [42538.448200] [tempesta fw] Configuration processing is completed. Apr 26 03:53:08 192.168.122.209 [42538.498869] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:53:08 192.168.122.209 [42538.904987] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:53:08 192.168.122.209 [42538.930730] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:53:08 192.168.122.209 [42538.972370] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:53:08 192.168.122.209 [42539.052186] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:53:08 192.168.122.209 [42539.100131] [tempesta fw] Tempesta FW is ready Apr 26 03:53:10 192.168.122.209 [42540.995231] [tdb] Close table 'client0.tdb' Apr 26 03:53:10 192.168.122.209 [42541.182709] [tdb] Close table 'sessions0.tdb' Apr 26 03:53:14 192.168.122.209 [42544.343012] [tdb] Close table 'cache0.tdb' Apr 26 03:53:14 192.168.122.209 [42544.601936] [tdb] Close table 'filter0.tdb' Apr 26 03:53:14 192.168.122.209 [42544.602375] [tempesta fw] modules are stopped Apr 26 03:53:14 192.168.122.209 [42544.779962] [tempesta fw] exiting... Apr 26 03:53:14 192.168.122.209 [42544.932201] [tdb] Shutdown Tempesta DB Apr 26 03:53:14 192.168.122.209 [42545.191205] End test: normalization.test_http_multipart.ContentTypeHeaderReconstructTest.test_replacement_quoted Apr 26 03:53:14 192.168.122.209 [42545.236439] Start test: normalization.test_http_multipart.ContentTypeHeaderReconstructTest.test_replacement_unquoted_1 Apr 26 03:53:16 192.168.122.209 [42546.475498] [tdb] Start Tempesta DB Apr 26 03:53:16 192.168.122.209 [42546.616898] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:53:17 192.168.122.209 [42548.060305] [tempesta fw] Configuration processing is completed. Apr 26 03:53:17 192.168.122.209 [42548.110731] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:53:18 192.168.122.209 [42548.531143] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:53:18 192.168.122.209 [42548.577406] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:53:18 192.168.122.209 [42548.603387] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:53:18 192.168.122.209 [42548.664311] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:53:18 192.168.122.209 [42548.708281] [tempesta fw] Tempesta FW is ready Apr 26 03:53:20 192.168.122.209 [42550.610909] [tdb] Close table 'client0.tdb' Apr 26 03:53:20 192.168.122.209 [42550.802924] [tdb] Close table 'sessions0.tdb' Apr 26 03:53:23 192.168.122.209 [42553.954899] [tdb] Close table 'cache0.tdb' Apr 26 03:53:23 192.168.122.209 [42554.186943] [tdb] Close table 'filter0.tdb' Apr 26 03:53:23 192.168.122.209 [42554.187376] [tempesta fw] modules are stopped Apr 26 03:53:24 192.168.122.209 [42554.353939] [tempesta fw] exiting... Apr 26 03:53:24 192.168.122.209 [42554.488287] [tdb] Shutdown Tempesta DB Apr 26 03:53:24 192.168.122.209 [42554.736866] End test: normalization.test_http_multipart.ContentTypeHeaderReconstructTest.test_replacement_unquoted_1 Apr 26 03:53:24 192.168.122.209 [42554.749430] Start test: normalization.test_http_multipart.ContentTypeHeaderReconstructTest.test_replacement_unquoted_2 Apr 26 03:53:25 192.168.122.209 [42555.981462] [tdb] Start Tempesta DB Apr 26 03:53:25 192.168.122.209 [42556.139987] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:53:27 192.168.122.209 [42557.580419] [tempesta fw] Configuration processing is completed. Apr 26 03:53:27 192.168.122.209 [42557.632616] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:53:27 192.168.122.209 [42558.050027] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:53:27 192.168.122.209 [42558.076037] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:53:27 192.168.122.209 [42558.101930] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:53:27 192.168.122.209 [42558.148507] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:53:27 192.168.122.209 [42558.188379] [tempesta fw] Tempesta FW is ready Apr 26 03:53:29 192.168.122.209 [42560.207968] [tdb] Close table 'client0.tdb' Apr 26 03:53:30 192.168.122.209 [42560.402425] [tdb] Close table 'sessions0.tdb' Apr 26 03:53:33 192.168.122.209 [42563.591059] [tdb] Close table 'cache0.tdb' Apr 26 03:53:33 192.168.122.209 [42563.845401] [tdb] Close table 'filter0.tdb' Apr 26 03:53:33 192.168.122.209 [42563.845824] [tempesta fw] modules are stopped Apr 26 03:53:33 192.168.122.209 [42564.014411] [tempesta fw] exiting... Apr 26 03:53:33 192.168.122.209 [42564.146114] [tdb] Shutdown Tempesta DB Apr 26 03:53:34 192.168.122.209 [42564.359939] End test: normalization.test_http_multipart.ContentTypeHeaderReconstructTest.test_replacement_unquoted_2 Apr 26 03:53:34 192.168.122.209 [42564.372303] Start test: sessions.test_cookies.CookieLifetime.test_cookie Apr 26 03:53:35 192.168.122.209 [42565.497080] [tdb] Start Tempesta DB Apr 26 03:53:35 192.168.122.209 [42565.641826] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:53:36 192.168.122.209 [42567.132625] [tempesta fw] Configuration processing is completed. Apr 26 03:53:36 192.168.122.209 [42567.192155] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:53:37 192.168.122.209 [42567.596241] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:53:37 192.168.122.209 [42567.622250] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:53:37 192.168.122.209 [42567.647852] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:53:37 192.168.122.209 [42567.696467] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:53:37 192.168.122.209 [42567.744506] [tempesta fw] Tempesta FW is ready Apr 26 03:53:42 192.168.122.209 [42572.901537] [tempesta fw] Warning: http_sess: sticky cookie value expired for 127.0.0.2 (issued=4305533801 lifetime=500 now=4305535058) Apr 26 03:53:43 192.168.122.209 [42573.402208] [tdb] Close table 'client0.tdb' Apr 26 03:53:43 192.168.122.209 [42573.581487] [tdb] Close table 'sessions0.tdb' Apr 26 03:53:46 192.168.122.209 [42576.636370] [tdb] Close table 'cache0.tdb' Apr 26 03:53:46 192.168.122.209 [42576.875988] [tdb] Close table 'filter0.tdb' Apr 26 03:53:46 192.168.122.209 [42576.876432] [tempesta fw] modules are stopped Apr 26 03:53:46 192.168.122.209 [42577.035134] [tempesta fw] exiting... Apr 26 03:53:46 192.168.122.209 [42577.188735] [tdb] Shutdown Tempesta DB Apr 26 03:53:47 192.168.122.209 [42577.378074] End test: sessions.test_cookies.CookieLifetime.test_cookie Apr 26 03:53:47 192.168.122.209 [42577.386086] Start test: sessions.test_cookies.CookiesEnabled.test_cookie Apr 26 03:53:48 192.168.122.209 [42578.582461] [tdb] Start Tempesta DB Apr 26 03:53:48 192.168.122.209 [42578.722366] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:53:49 192.168.122.209 [42580.112783] [tempesta fw] Configuration processing is completed. Apr 26 03:53:49 192.168.122.209 [42580.199966] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:53:50 192.168.122.209 [42580.618402] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:53:50 192.168.122.209 [42580.644352] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:53:50 192.168.122.209 [42580.670241] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:53:50 192.168.122.209 [42580.728706] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:53:50 192.168.122.209 [42580.796648] [tempesta fw] Tempesta FW is ready Apr 26 03:53:51 192.168.122.209 [42581.501290] [tdb] Close table 'client0.tdb' Apr 26 03:53:51 192.168.122.209 [42581.703623] [tdb] Close table 'sessions0.tdb' Apr 26 03:53:54 192.168.122.209 [42584.841950] [tdb] Close table 'cache0.tdb' Apr 26 03:53:54 192.168.122.209 [42585.099469] [tdb] Close table 'filter0.tdb' Apr 26 03:53:54 192.168.122.209 [42585.099894] [tempesta fw] modules are stopped Apr 26 03:53:54 192.168.122.209 [42585.292399] [tempesta fw] exiting... Apr 26 03:53:55 192.168.122.209 [42585.408870] [tdb] Shutdown Tempesta DB Apr 26 03:53:55 192.168.122.209 [42585.616755] End test: sessions.test_cookies.CookiesEnabled.test_cookie Apr 26 03:53:55 192.168.122.209 [42585.628139] Start test: sessions.test_cookies.CookiesEnforced.test_cookie Apr 26 03:53:56 192.168.122.209 [42586.776806] [tdb] Start Tempesta DB Apr 26 03:53:56 192.168.122.209 [42586.927333] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:53:58 192.168.122.209 [42588.348903] [tempesta fw] Configuration processing is completed. Apr 26 03:53:58 192.168.122.209 [42588.399966] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:53:58 192.168.122.209 [42588.810662] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:53:58 192.168.122.209 [42588.836965] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:53:58 192.168.122.209 [42588.862420] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:53:58 192.168.122.209 [42588.920676] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:53:58 192.168.122.209 [42588.964773] [tempesta fw] Tempesta FW is ready Apr 26 03:53:59 192.168.122.209 [42589.614964] [tdb] Close table 'client0.tdb' Apr 26 03:53:59 192.168.122.209 [42589.838404] [tdb] Close table 'sessions0.tdb' Apr 26 03:54:02 192.168.122.209 [42592.969614] [tdb] Close table 'cache0.tdb' Apr 26 03:54:02 192.168.122.209 [42593.244258] [tdb] Close table 'filter0.tdb' Apr 26 03:54:02 192.168.122.209 [42593.244707] [tempesta fw] modules are stopped Apr 26 03:54:03 192.168.122.209 [42593.405419] [tempesta fw] exiting... Apr 26 03:54:03 192.168.122.209 [42593.526567] [tdb] Shutdown Tempesta DB Apr 26 03:54:03 192.168.122.209 [42593.721202] End test: sessions.test_cookies.CookiesEnforced.test_cookie Apr 26 03:54:03 192.168.122.209 [42593.733614] Start test: sessions.test_cookies.CookiesInherit.test_cookie Apr 26 03:54:04 192.168.122.209 [42594.920881] [tdb] Start Tempesta DB Apr 26 03:54:04 192.168.122.209 [42595.050529] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:54:07 192.168.122.209 [42597.569043] [tempesta fw] Configuration processing is completed. Apr 26 03:54:07 192.168.122.209 [42597.658501] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:54:07 192.168.122.209 [42598.077149] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:54:07 192.168.122.209 [42598.103190] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:54:07 192.168.122.209 [42598.129335] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:54:07 192.168.122.209 [42598.225007] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:54:07 192.168.122.209 [42598.288881] [tempesta fw] Tempesta FW is ready Apr 26 03:54:08 192.168.122.209 [42599.212902] [tdb] Close table 'client0.tdb' Apr 26 03:54:09 192.168.122.209 [42599.406362] [tdb] Close table 'sessions0.tdb' Apr 26 03:54:12 192.168.122.209 [42602.554812] [tdb] Close table 'cache0.tdb' Apr 26 03:54:12 192.168.122.209 [42602.793982] [tdb] Close table 'filter0.tdb' Apr 26 03:54:12 192.168.122.209 [42602.794416] [tempesta fw] modules are stopped Apr 26 03:54:12 192.168.122.209 [42603.038181] [tempesta fw] exiting... Apr 26 03:54:12 192.168.122.209 [42603.164036] [tdb] Shutdown Tempesta DB Apr 26 03:54:13 192.168.122.209 [42603.376627] End test: sessions.test_cookies.CookiesInherit.test_cookie Apr 26 03:54:13 192.168.122.209 [42603.404701] Start test: sessions.test_cookies.CookiesMaxMisses.test_max_misses__no_cookie Apr 26 03:54:14 192.168.122.209 [42604.538484] [tdb] Start Tempesta DB Apr 26 03:54:14 192.168.122.209 [42604.693673] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:54:16 192.168.122.209 [42606.801186] [tempesta fw] Configuration processing is completed. Apr 26 03:54:16 192.168.122.209 [42606.963218] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:54:17 192.168.122.209 [42607.452713] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:54:17 192.168.122.209 [42607.482930] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:54:17 192.168.122.209 [42607.511845] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:54:17 192.168.122.209 [42607.805101] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:54:17 192.168.122.209 [42608.149052] [tempesta fw] Tempesta FW is ready Apr 26 03:54:17 192.168.122.209 [42608.326657] [tempesta fw] Warning: frang: max rmisses exceeded for 127.0.0.2: 3 (lim=2) Apr 26 03:54:19 192.168.122.209 [42609.345031] [tdb] Close table 'client0.tdb' Apr 26 03:54:19 192.168.122.209 [42609.654056] [tdb] Close table 'sessions0.tdb' Apr 26 03:54:23 192.168.122.209 [42613.508641] [tdb] Close table 'cache0.tdb' Apr 26 03:54:23 192.168.122.209 [42613.763470] [tdb] Close table 'filter0.tdb' Apr 26 03:54:23 192.168.122.209 [42613.763916] [tempesta fw] modules are stopped Apr 26 03:54:23 192.168.122.209 [42613.930131] [tempesta fw] exiting... Apr 26 03:54:23 192.168.122.209 [42614.060326] [tdb] Shutdown Tempesta DB Apr 26 03:54:23 192.168.122.209 [42614.248811] End test: sessions.test_cookies.CookiesMaxMisses.test_max_misses__no_cookie Apr 26 03:54:23 192.168.122.209 [42614.269537] Start test: sessions.test_cookies.CookiesMaxMisses.test_max_misses__with_invalid_cookie Apr 26 03:54:25 192.168.122.209 [42615.474883] [tdb] Start Tempesta DB Apr 26 03:54:25 192.168.122.209 [42615.650754] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:54:26 192.168.122.209 [42617.081273] [tempesta fw] Configuration processing is completed. Apr 26 03:54:26 192.168.122.209 [42617.134557] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:54:27 192.168.122.209 [42617.637232] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:54:27 192.168.122.209 [42617.668551] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:54:27 192.168.122.209 [42617.701549] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:54:27 192.168.122.209 [42617.769165] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:54:27 192.168.122.209 [42617.809142] [tempesta fw] Tempesta FW is ready Apr 26 03:54:27 192.168.122.209 [42617.945128] [tempesta fw] Warning: http_sess: bad sticky cookie length for 127.0.0.2 22(56) Apr 26 03:54:27 192.168.122.209 [42617.955618] [tempesta fw] Warning: http_sess: bad sticky cookie length for 127.0.0.2 22(56) Apr 26 03:54:27 192.168.122.209 [42617.966102] [tempesta fw] Warning: http_sess: bad sticky cookie length for 127.0.0.2 22(56) Apr 26 03:54:27 192.168.122.209 [42617.968437] [tempesta fw] Warning: frang: max rmisses exceeded for 127.0.0.2: 3 (lim=2) Apr 26 03:54:28 192.168.122.209 [42618.398363] [tdb] Close table 'client0.tdb' Apr 26 03:54:28 192.168.122.209 [42618.598331] [tdb] Close table 'sessions0.tdb' Apr 26 03:54:31 192.168.122.209 [42621.856544] [tdb] Close table 'cache0.tdb' Apr 26 03:54:31 192.168.122.209 [42622.093665] [tdb] Close table 'filter0.tdb' Apr 26 03:54:31 192.168.122.209 [42622.094098] [tempesta fw] modules are stopped Apr 26 03:54:31 192.168.122.209 [42622.312226] [tempesta fw] exiting... Apr 26 03:54:32 192.168.122.209 [42622.463789] [tdb] Shutdown Tempesta DB Apr 26 03:54:32 192.168.122.209 [42622.668358] End test: sessions.test_cookies.CookiesMaxMisses.test_max_misses__with_invalid_cookie Apr 26 03:54:32 192.168.122.209 [42622.691372] Start test: sessions.test_cookies.CookiesNotEnabled.test_cookie Apr 26 03:54:33 192.168.122.209 [42623.891275] [tdb] Start Tempesta DB Apr 26 03:54:33 192.168.122.209 [42624.040725] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:54:35 192.168.122.209 [42625.361342] [tempesta fw] Configuration processing is completed. Apr 26 03:54:35 192.168.122.209 [42625.413766] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:54:35 192.168.122.209 [42625.823790] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:54:35 192.168.122.209 [42625.849425] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:54:35 192.168.122.209 [42625.882180] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:54:35 192.168.122.209 [42625.953273] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:54:35 192.168.122.209 [42625.993220] [tempesta fw] Tempesta FW is ready Apr 26 03:54:36 192.168.122.209 [42626.744242] [tdb] Close table 'client0.tdb' Apr 26 03:54:36 192.168.122.209 [42626.922984] [tdb] Close table 'sessions0.tdb' Apr 26 03:54:39 192.168.122.209 [42630.197270] [tdb] Close table 'cache0.tdb' Apr 26 03:54:40 192.168.122.209 [42630.419230] [tdb] Close table 'filter0.tdb' Apr 26 03:54:40 192.168.122.209 [42630.419651] [tempesta fw] modules are stopped Apr 26 03:54:40 192.168.122.209 [42630.641071] [tempesta fw] exiting... Apr 26 03:54:40 192.168.122.209 [42630.816085] [tdb] Shutdown Tempesta DB Apr 26 03:54:40 192.168.122.209 [42631.014688] End test: sessions.test_cookies.CookiesNotEnabled.test_cookie Apr 26 03:54:40 192.168.122.209 [42631.023428] Start test: sessions.test_cookies.StickyCookieConfigGlobal.test_cookie_options_no_cookie Apr 26 03:54:41 192.168.122.209 [42632.204355] [tdb] Start Tempesta DB Apr 26 03:54:42 192.168.122.209 [42632.355294] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:54:43 192.168.122.209 [42633.522267] [tempesta fw] ERROR: http_sess: cookie options requires sticky cookies enabled and explicitly defined in the same section Apr 26 03:54:43 192.168.122.209 [42633.524560] [tempesta fw] ERROR: configuration parsing error Apr 26 03:54:43 192.168.122.209 [42633.525816] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 03:54:43 192.168.122.209 [42633.672992] [tempesta fw] exiting... Apr 26 03:54:43 192.168.122.209 [42633.821679] [tdb] Shutdown Tempesta DB Apr 26 03:54:44 192.168.122.209 [42634.380628] End test: sessions.test_cookies.StickyCookieConfigGlobal.test_cookie_options_no_cookie Apr 26 03:54:44 192.168.122.209 [42634.396859] Start test: sessions.test_cookies.StickyCookieConfigGlobal.test_cookie_options_with_cookie Apr 26 03:54:45 192.168.122.209 [42635.501362] [tdb] Start Tempesta DB Apr 26 03:54:45 192.168.122.209 [42635.640089] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:54:45 192.168.122.209 [42635.955414] [tempesta fw] Configuration processing is completed. Apr 26 03:54:45 192.168.122.209 [42636.027933] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:54:46 192.168.122.209 [42636.460869] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:54:46 192.168.122.209 [42636.492257] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:54:46 192.168.122.209 [42636.523609] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:54:46 192.168.122.209 [42636.524687] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:54:46 192.168.122.209 [42636.553411] [tempesta fw] Tempesta FW is ready Apr 26 03:54:46 192.168.122.209 [42636.986726] [tdb] Close table 'client0.tdb' Apr 26 03:54:46 192.168.122.209 [42637.168776] [tdb] Close table 'sessions0.tdb' Apr 26 03:54:50 192.168.122.209 [42640.389979] [tdb] Close table 'cache0.tdb' Apr 26 03:54:50 192.168.122.209 [42640.643546] [tdb] Close table 'filter0.tdb' Apr 26 03:54:50 192.168.122.209 [42640.643980] [tempesta fw] modules are stopped Apr 26 03:54:50 192.168.122.209 [42640.808458] [tempesta fw] exiting... Apr 26 03:54:50 192.168.122.209 [42640.942122] [tdb] Shutdown Tempesta DB Apr 26 03:54:50 192.168.122.209 [42641.159706] End test: sessions.test_cookies.StickyCookieConfigGlobal.test_cookie_options_with_cookie Apr 26 03:54:50 192.168.122.209 [42641.170748] Start test: sessions.test_cookies.StickyCookieConfigGlobal.test_dublicate_delay_min Apr 26 03:54:52 192.168.122.209 [42642.386871] [tdb] Start Tempesta DB Apr 26 03:54:52 192.168.122.209 [42642.532160] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:54:53 192.168.122.209 [42644.018734] [tempesta fw] ERROR: Duplicate argument: 'delay_min' Apr 26 03:54:53 192.168.122.209 [42644.020482] [tempesta fw] ERROR: configuration parsing error: [42644.020482] 3: js_challenge resp_code=503 delay_min=1000 delay_min=2000 delay_range=3000 /t [42644.020482] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 03:54:53 192.168.122.209 [42644.025038] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 03:54:53 192.168.122.209 [42644.170837] [tempesta fw] exiting... Apr 26 03:54:53 192.168.122.209 [42644.300737] [tdb] Shutdown Tempesta DB Apr 26 03:54:54 192.168.122.209 [42644.824826] End test: sessions.test_cookies.StickyCookieConfigGlobal.test_dublicate_delay_min Apr 26 03:54:54 192.168.122.209 [42644.836649] Start test: sessions.test_cookies.StickyCookieConfigGlobal.test_dublicate_delay_range Apr 26 03:54:55 192.168.122.209 [42646.066569] [tdb] Start Tempesta DB Apr 26 03:54:55 192.168.122.209 [42646.214473] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:54:56 192.168.122.209 [42646.699602] [tempesta fw] ERROR: Duplicate argument: 'delay_range' Apr 26 03:54:56 192.168.122.209 [42646.700199] [tempesta fw] ERROR: configuration parsing error: [42646.700199] 3: js_challenge resp_code=503 delay_min=1000 delay_range=2000 delay_range=3000 [42646.700199] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 03:54:56 192.168.122.209 [42646.702361] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 03:54:56 192.168.122.209 [42646.832210] [tempesta fw] exiting... Apr 26 03:54:56 192.168.122.209 [42646.931666] [tdb] Shutdown Tempesta DB Apr 26 03:54:57 192.168.122.209 [42647.445760] End test: sessions.test_cookies.StickyCookieConfigGlobal.test_dublicate_delay_range Apr 26 03:54:57 192.168.122.209 [42647.462875] Start test: sessions.test_cookies.StickyCookieConfigGlobal.test_dublicate_max_misses Apr 26 03:54:58 192.168.122.209 [42648.540972] [tdb] Start Tempesta DB Apr 26 03:54:58 192.168.122.209 [42648.692108] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:54:58 192.168.122.209 [42648.879016] [tempesta fw] ERROR: Duplicate argument: 'max_misses' Apr 26 03:54:58 192.168.122.209 [42648.879808] [tempesta fw] ERROR: configuration parsing error: [42648.879808] 3: cookie max_misses=3 max_misses=4 enforce; [42648.879808] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 03:54:58 192.168.122.209 [42648.881738] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 03:54:58 192.168.122.209 [42649.016834] [tempesta fw] exiting... Apr 26 03:54:58 192.168.122.209 [42649.128278] [tdb] Shutdown Tempesta DB Apr 26 03:54:59 192.168.122.209 [42649.553942] End test: sessions.test_cookies.StickyCookieConfigGlobal.test_dublicate_max_misses Apr 26 03:54:59 192.168.122.209 [42649.563355] Start test: sessions.test_cookies.StickyCookieConfigGlobal.test_dublicate_name Apr 26 03:55:00 192.168.122.209 [42650.568311] [tdb] Start Tempesta DB Apr 26 03:55:00 192.168.122.209 [42650.703501] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:55:00 192.168.122.209 [42650.915700] [tempesta fw] ERROR: Duplicate argument: 'name' Apr 26 03:55:00 192.168.122.209 [42650.917286] [tempesta fw] ERROR: configuration parsing error: [42650.917286] 3: cookie name=A name=B enforce; [42650.917286] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 03:55:00 192.168.122.209 [42650.921799] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 03:55:00 192.168.122.209 [42651.057658] [tempesta fw] exiting... Apr 26 03:55:00 192.168.122.209 [42651.167430] [tdb] Shutdown Tempesta DB Apr 26 03:55:01 192.168.122.209 [42651.612370] End test: sessions.test_cookies.StickyCookieConfigGlobal.test_dublicate_name Apr 26 03:55:01 192.168.122.209 [42651.619246] Start test: sessions.test_cookies.StickyCookieConfigGlobal.test_dublicate_resp_code Apr 26 03:55:02 192.168.122.209 [42652.633377] [tdb] Start Tempesta DB Apr 26 03:55:02 192.168.122.209 [42652.782057] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:55:02 192.168.122.209 [42653.195359] [tempesta fw] ERROR: Duplicate argument: 'resp_code' Apr 26 03:55:02 192.168.122.209 [42653.196649] [tempesta fw] ERROR: configuration parsing error: [42653.196649] 3: js_challenge resp_code=503 resp_code=502 delay_min=2000 delay_range=3000 /tm [42653.196649] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 03:55:02 192.168.122.209 [42653.201694] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 03:55:03 192.168.122.209 [42653.358302] [tempesta fw] exiting... Apr 26 03:55:03 192.168.122.209 [42653.497364] [tdb] Shutdown Tempesta DB Apr 26 03:55:03 192.168.122.209 [42653.938809] End test: sessions.test_cookies.StickyCookieConfigGlobal.test_dublicate_resp_code Apr 26 03:55:03 192.168.122.209 [42653.948510] Start test: sessions.test_cookies.StickyCookieConfigGlobal.test_empty_js_challenge Apr 26 03:55:04 192.168.122.209 [42655.051837] [tdb] Start Tempesta DB Apr 26 03:55:04 192.168.122.209 [42655.191434] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:55:05 192.168.122.209 [42655.419242] [tempesta fw] ERROR: js_challenge: required argument 'delay_min' not set. Apr 26 03:55:05 192.168.122.209 [42655.419993] [tempesta fw] ERROR: configuration parsing error: [42655.419993] 3: js_challenge; [42655.419993] ^^^^^^^^^^^^^^^^^ Apr 26 03:55:05 192.168.122.209 [42655.421138] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 03:55:05 192.168.122.209 [42655.561735] [tempesta fw] exiting... Apr 26 03:55:05 192.168.122.209 [42655.687943] [tdb] Shutdown Tempesta DB Apr 26 03:55:05 192.168.122.209 [42656.122149] End test: sessions.test_cookies.StickyCookieConfigGlobal.test_empty_js_challenge Apr 26 03:55:05 192.168.122.209 [42656.132657] Start test: sessions.test_cookies.StickyCookieConfigGlobal.test_js_challenge_no_cookie Apr 26 03:55:06 192.168.122.209 [42657.129576] [tdb] Start Tempesta DB Apr 26 03:55:06 192.168.122.209 [42657.267370] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:55:07 192.168.122.209 [42657.656413] [tempesta fw] ERROR: http_sess: JavaScript challenge requires sticky cookies enabled and explicitly defined in the same section Apr 26 03:55:07 192.168.122.209 [42657.658481] [tempesta fw] ERROR: configuration parsing error Apr 26 03:55:07 192.168.122.209 [42657.659326] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 03:55:07 192.168.122.209 [42657.780481] [tempesta fw] exiting... Apr 26 03:55:07 192.168.122.209 [42657.885867] [tdb] Shutdown Tempesta DB Apr 26 03:55:07 192.168.122.209 [42658.338968] End test: sessions.test_cookies.StickyCookieConfigGlobal.test_js_challenge_no_cookie Apr 26 03:55:08 192.168.122.209 [42658.356835] Start test: sessions.test_cookies.StickyCookieConfigGlobal.test_js_challenge_with_cookie Apr 26 03:55:08 192.168.122.209 [42659.325902] [tdb] Start Tempesta DB Apr 26 03:55:09 192.168.122.209 [42659.482157] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:55:09 192.168.122.209 [42659.897060] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 03:55:09 192.168.122.209 [42659.927889] [tempesta fw] Configuration processing is completed. Apr 26 03:55:09 192.168.122.209 [42659.985288] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:55:10 192.168.122.209 [42660.396836] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:55:10 192.168.122.209 [42660.423823] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:55:10 192.168.122.209 [42660.450872] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:55:10 192.168.122.209 [42660.451912] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:55:10 192.168.122.209 [42660.473797] [tempesta fw] Tempesta FW is ready Apr 26 03:55:10 192.168.122.209 [42660.870906] [tdb] Close table 'client0.tdb' Apr 26 03:55:10 192.168.122.209 [42661.070773] [tdb] Close table 'sessions0.tdb' Apr 26 03:55:13 192.168.122.209 [42664.212810] [tdb] Close table 'cache0.tdb' Apr 26 03:55:14 192.168.122.209 [42664.455217] [tdb] Close table 'filter0.tdb' Apr 26 03:55:14 192.168.122.209 [42664.455639] [tempesta fw] modules are stopped Apr 26 03:55:14 192.168.122.209 [42664.677761] [tempesta fw] exiting... Apr 26 03:55:14 192.168.122.209 [42664.816564] [tdb] Shutdown Tempesta DB Apr 26 03:55:14 192.168.122.209 [42664.999299] End test: sessions.test_cookies.StickyCookieConfigGlobal.test_js_challenge_with_cookie Apr 26 03:55:14 192.168.122.209 [42665.008800] Start test: sessions.test_cookies.StickyCookieConfigVhost.test_cookie_options_no_cookie Apr 26 03:55:15 192.168.122.209 [42666.153684] [tdb] Start Tempesta DB Apr 26 03:55:15 192.168.122.209 [42666.308060] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:55:17 192.168.122.209 [42667.747209] [tempesta fw] ERROR: http_sess: cookie options requires sticky cookies enabled and explicitly defined in the same section Apr 26 03:55:17 192.168.122.209 [42667.750568] [tempesta fw] ERROR: configuration parsing error Apr 26 03:55:17 192.168.122.209 [42667.752130] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 03:55:17 192.168.122.209 [42667.933844] [tempesta fw] exiting... Apr 26 03:55:17 192.168.122.209 [42668.081323] [tdb] Shutdown Tempesta DB Apr 26 03:55:18 192.168.122.209 [42668.617571] End test: sessions.test_cookies.StickyCookieConfigVhost.test_cookie_options_no_cookie Apr 26 03:55:18 192.168.122.209 [42668.629121] Start test: sessions.test_cookies.StickyCookieConfigVhost.test_cookie_options_with_cookie Apr 26 03:55:19 192.168.122.209 [42669.749718] [tdb] Start Tempesta DB Apr 26 03:55:19 192.168.122.209 [42669.905443] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:55:20 192.168.122.209 [42670.401832] [tempesta fw] Configuration processing is completed. Apr 26 03:55:20 192.168.122.209 [42670.489088] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:55:20 192.168.122.209 [42670.968452] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:55:20 192.168.122.209 [42670.998421] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:55:20 192.168.122.209 [42671.027885] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:55:20 192.168.122.209 [42671.105851] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:55:20 192.168.122.209 [42671.175221] [tempesta fw] Tempesta FW is ready Apr 26 03:55:21 192.168.122.209 [42671.673008] [tdb] Close table 'client0.tdb' Apr 26 03:55:21 192.168.122.209 [42671.856440] [tdb] Close table 'sessions0.tdb' Apr 26 03:55:24 192.168.122.209 [42675.031564] [tdb] Close table 'cache0.tdb' Apr 26 03:55:24 192.168.122.209 [42675.285370] [tdb] Close table 'filter0.tdb' Apr 26 03:55:24 192.168.122.209 [42675.285861] [tempesta fw] modules are stopped Apr 26 03:55:25 192.168.122.209 [42675.478711] [tempesta fw] exiting... Apr 26 03:55:25 192.168.122.209 [42675.604299] [tdb] Shutdown Tempesta DB Apr 26 03:55:25 192.168.122.209 [42675.827204] End test: sessions.test_cookies.StickyCookieConfigVhost.test_cookie_options_with_cookie Apr 26 03:55:25 192.168.122.209 [42675.834601] Start test: sessions.test_cookies.StickyCookieConfigVhost.test_dublicate_delay_min Apr 26 03:55:26 192.168.122.209 [42677.122133] [tdb] Start Tempesta DB Apr 26 03:55:26 192.168.122.209 [42677.283326] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:55:28 192.168.122.209 [42679.007081] [tempesta fw] ERROR: Duplicate argument: 'delay_min' Apr 26 03:55:28 192.168.122.209 [42679.008827] [tempesta fw] ERROR: configuration parsing error: [42679.008827] 8: js_challenge resp_code=503 delay_min=1000 delay_min=2000 delay_range=300 [42679.008827] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 03:55:28 192.168.122.209 [42679.015358] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 03:55:28 192.168.122.209 [42679.195982] [tempesta fw] exiting... Apr 26 03:55:29 192.168.122.209 [42679.349099] [tdb] Shutdown Tempesta DB Apr 26 03:55:29 192.168.122.209 [42679.861346] End test: sessions.test_cookies.StickyCookieConfigVhost.test_dublicate_delay_min Apr 26 03:55:29 192.168.122.209 [42679.880161] Start test: sessions.test_cookies.StickyCookieConfigVhost.test_dublicate_delay_range Apr 26 03:55:30 192.168.122.209 [42680.980381] [tdb] Start Tempesta DB Apr 26 03:55:30 192.168.122.209 [42681.130603] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:55:31 192.168.122.209 [42681.827089] [tempesta fw] ERROR: Duplicate argument: 'delay_range' Apr 26 03:55:31 192.168.122.209 [42681.828875] [tempesta fw] ERROR: configuration parsing error: [42681.828875] 8: js_challenge resp_code=503 delay_min=1000 delay_range=2000 delay_range=3 [42681.828875] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 03:55:31 192.168.122.209 [42681.834667] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 03:55:31 192.168.122.209 [42682.002614] [tempesta fw] exiting... Apr 26 03:55:31 192.168.122.209 [42682.150373] [tdb] Shutdown Tempesta DB Apr 26 03:55:32 192.168.122.209 [42682.638561] End test: sessions.test_cookies.StickyCookieConfigVhost.test_dublicate_delay_range Apr 26 03:55:32 192.168.122.209 [42682.663370] Start test: sessions.test_cookies.StickyCookieConfigVhost.test_dublicate_max_misses Apr 26 03:55:33 192.168.122.209 [42683.786469] [tdb] Start Tempesta DB Apr 26 03:55:33 192.168.122.209 [42683.925817] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:55:33 192.168.122.209 [42684.330828] [tempesta fw] ERROR: Duplicate argument: 'max_misses' Apr 26 03:55:33 192.168.122.209 [42684.332539] [tempesta fw] ERROR: configuration parsing error: [42684.332539] 8: cookie max_misses=3 max_misses=4 enforce; [42684.332539] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 03:55:33 192.168.122.209 [42684.337592] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 03:55:34 192.168.122.209 [42684.511128] [tempesta fw] exiting... Apr 26 03:55:34 192.168.122.209 [42684.637121] [tdb] Shutdown Tempesta DB Apr 26 03:55:34 192.168.122.209 [42685.097724] End test: sessions.test_cookies.StickyCookieConfigVhost.test_dublicate_max_misses Apr 26 03:55:34 192.168.122.209 [42685.118335] Start test: sessions.test_cookies.StickyCookieConfigVhost.test_dublicate_name Apr 26 03:55:35 192.168.122.209 [42686.226034] [tdb] Start Tempesta DB Apr 26 03:55:36 192.168.122.209 [42686.381545] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:55:36 192.168.122.209 [42686.839886] [tempesta fw] ERROR: Duplicate argument: 'name' Apr 26 03:55:36 192.168.122.209 [42686.841099] [tempesta fw] ERROR: configuration parsing error: [42686.841099] 8: cookie name=A name=B enforce; [42686.841099] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 03:55:36 192.168.122.209 [42686.842902] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 03:55:36 192.168.122.209 [42687.003113] [tempesta fw] exiting... Apr 26 03:55:36 192.168.122.209 [42687.139804] [tdb] Shutdown Tempesta DB Apr 26 03:55:37 192.168.122.209 [42687.608799] End test: sessions.test_cookies.StickyCookieConfigVhost.test_dublicate_name Apr 26 03:55:37 192.168.122.209 [42687.623317] Start test: sessions.test_cookies.StickyCookieConfigVhost.test_dublicate_resp_code Apr 26 03:55:38 192.168.122.209 [42688.754238] [tdb] Start Tempesta DB Apr 26 03:55:38 192.168.122.209 [42688.902751] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:55:39 192.168.122.209 [42689.559315] [tempesta fw] ERROR: Duplicate argument: 'resp_code' Apr 26 03:55:39 192.168.122.209 [42689.561031] [tempesta fw] ERROR: configuration parsing error: [42689.561031] 8: js_challenge resp_code=503 resp_code=502 delay_min=2000 delay_range=3000 [42689.561031] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 03:55:39 192.168.122.209 [42689.567584] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 03:55:39 192.168.122.209 [42689.726522] [tempesta fw] exiting... Apr 26 03:55:39 192.168.122.209 [42689.830327] [tdb] Shutdown Tempesta DB Apr 26 03:55:39 192.168.122.209 [42690.332731] End test: sessions.test_cookies.StickyCookieConfigVhost.test_dublicate_resp_code Apr 26 03:55:40 192.168.122.209 [42690.345761] Start test: sessions.test_cookies.StickyCookieConfigVhost.test_empty_js_challenge Apr 26 03:55:41 192.168.122.209 [42691.442164] [tdb] Start Tempesta DB Apr 26 03:55:41 192.168.122.209 [42691.592979] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:55:41 192.168.122.209 [42692.023260] [tempesta fw] ERROR: js_challenge: required argument 'delay_min' not set. Apr 26 03:55:41 192.168.122.209 [42692.025467] [tempesta fw] ERROR: configuration parsing error: [42692.025467] 8: js_challenge; [42692.025467] ^^^^^^^^^^^^^^^^^^^^^ Apr 26 03:55:41 192.168.122.209 [42692.029185] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 03:55:41 192.168.122.209 [42692.214748] [tempesta fw] exiting... Apr 26 03:55:41 192.168.122.209 [42692.340864] [tdb] Shutdown Tempesta DB Apr 26 03:55:42 192.168.122.209 [42692.860662] End test: sessions.test_cookies.StickyCookieConfigVhost.test_empty_js_challenge Apr 26 03:55:42 192.168.122.209 [42692.873714] Start test: sessions.test_cookies.StickyCookieConfigVhost.test_js_challenge_no_cookie Apr 26 03:55:43 192.168.122.209 [42694.044159] [tdb] Start Tempesta DB Apr 26 03:55:43 192.168.122.209 [42694.194468] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:55:44 192.168.122.209 [42694.800567] [tempesta fw] ERROR: http_sess: JavaScript challenge requires sticky cookies enabled and explicitly defined in the same section Apr 26 03:55:44 192.168.122.209 [42694.804022] [tempesta fw] ERROR: configuration parsing error Apr 26 03:55:44 192.168.122.209 [42694.805592] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 03:55:44 192.168.122.209 [42695.001964] [tempesta fw] exiting... Apr 26 03:55:44 192.168.122.209 [42695.118560] [tdb] Shutdown Tempesta DB Apr 26 03:55:45 192.168.122.209 [42695.630828] End test: sessions.test_cookies.StickyCookieConfigVhost.test_js_challenge_no_cookie Apr 26 03:55:45 192.168.122.209 [42695.643671] Start test: sessions.test_cookies.StickyCookieConfigVhost.test_js_challenge_with_cookie Apr 26 03:55:46 192.168.122.209 [42696.744209] [tdb] Start Tempesta DB Apr 26 03:55:46 192.168.122.209 [42696.904784] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:55:47 192.168.122.209 [42697.593117] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 03:55:47 192.168.122.209 [42697.642302] [tempesta fw] Configuration processing is completed. Apr 26 03:55:47 192.168.122.209 [42697.694127] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:55:47 192.168.122.209 [42698.202703] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:55:47 192.168.122.209 [42698.235089] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:55:47 192.168.122.209 [42698.266998] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:55:48 192.168.122.209 [42698.346240] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:55:48 192.168.122.209 [42698.394138] [tempesta fw] Tempesta FW is ready Apr 26 03:55:48 192.168.122.209 [42698.946977] [tdb] Close table 'client0.tdb' Apr 26 03:55:48 192.168.122.209 [42699.133050] [tdb] Close table 'sessions0.tdb' Apr 26 03:55:51 192.168.122.209 [42702.309821] [tdb] Close table 'cache0.tdb' Apr 26 03:55:52 192.168.122.209 [42702.552409] [tdb] Close table 'filter0.tdb' Apr 26 03:55:52 192.168.122.209 [42702.552846] [tempesta fw] modules are stopped Apr 26 03:55:52 192.168.122.209 [42702.760846] [tempesta fw] exiting... Apr 26 03:55:52 192.168.122.209 [42702.922562] [tdb] Shutdown Tempesta DB Apr 26 03:55:52 192.168.122.209 [42703.122725] End test: sessions.test_cookies.StickyCookieConfigVhost.test_js_challenge_with_cookie Apr 26 03:55:52 192.168.122.209 [42703.136915] Start test: sessions.test_cookies.StickyCookieOptions.test_cookie_options_all_in_one Apr 26 03:55:53 192.168.122.209 [42704.314285] [tdb] Start Tempesta DB Apr 26 03:55:54 192.168.122.209 [42704.469562] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:55:56 192.168.122.209 [42706.462344] [tempesta fw] Configuration processing is completed. Apr 26 03:55:56 192.168.122.209 [42706.546912] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:55:56 192.168.122.209 [42706.997483] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:55:56 192.168.122.209 [42707.028960] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:55:56 192.168.122.209 [42707.060517] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:55:56 192.168.122.209 [42707.158309] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:55:56 192.168.122.209 [42707.230452] [tempesta fw] Tempesta FW is ready Apr 26 03:55:57 192.168.122.209 [42707.886246] [tdb] Close table 'client0.tdb' Apr 26 03:55:57 192.168.122.209 [42708.082813] [tdb] Close table 'sessions0.tdb' Apr 26 03:56:00 192.168.122.209 [42711.286909] [tdb] Close table 'cache0.tdb' Apr 26 03:56:01 192.168.122.209 [42711.546338] [tdb] Close table 'filter0.tdb' Apr 26 03:56:01 192.168.122.209 [42711.546781] [tempesta fw] modules are stopped Apr 26 03:56:01 192.168.122.209 [42711.770338] [tempesta fw] exiting... Apr 26 03:56:01 192.168.122.209 [42711.919751] [tdb] Shutdown Tempesta DB Apr 26 03:56:01 192.168.122.209 [42712.113813] End test: sessions.test_cookies.StickyCookieOptions.test_cookie_options_all_in_one Apr 26 03:56:01 192.168.122.209 [42712.125303] Start test: sessions.test_cookies.StickyCookieOptions.test_dublicate_expires Apr 26 03:56:02 192.168.122.209 [42713.317198] [tdb] Start Tempesta DB Apr 26 03:56:03 192.168.122.209 [42713.472463] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:56:05 192.168.122.209 [42715.406778] [tempesta fw] ERROR: Duplicate argument: 'Expires' Apr 26 03:56:05 192.168.122.209 [42715.407795] [tempesta fw] ERROR: configuration parsing error: [42715.407795] 11: cookie_options Expires=3 Expires=5; [42715.407795] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 03:56:05 192.168.122.209 [42715.410619] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 03:56:05 192.168.122.209 [42715.607278] [tempesta fw] exiting... Apr 26 03:56:05 192.168.122.209 [42715.733709] [tdb] Shutdown Tempesta DB Apr 26 03:56:05 192.168.122.209 [42716.270327] End test: sessions.test_cookies.StickyCookieOptions.test_dublicate_expires Apr 26 03:56:05 192.168.122.209 [42716.283818] Start test: sessions.test_cookies.StickyCookieOptions.test_dublicate_max_age Apr 26 03:56:07 192.168.122.209 [42717.422500] [tdb] Start Tempesta DB Apr 26 03:56:07 192.168.122.209 [42717.578803] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:56:08 192.168.122.209 [42718.439178] [tempesta fw] ERROR: Duplicate argument: 'Max-Age' Apr 26 03:56:08 192.168.122.209 [42718.440837] [tempesta fw] ERROR: configuration parsing error: [42718.440837] 11: cookie_options Max-Age=3 Max-Age=5; [42718.440837] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 03:56:08 192.168.122.209 [42718.445796] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 03:56:08 192.168.122.209 [42718.614877] [tempesta fw] exiting... Apr 26 03:56:08 192.168.122.209 [42718.738563] [tdb] Shutdown Tempesta DB Apr 26 03:56:08 192.168.122.209 [42719.219029] End test: sessions.test_cookies.StickyCookieOptions.test_dublicate_max_age Apr 26 03:56:08 192.168.122.209 [42719.236332] Start test: sessions.test_cookies.StickyCookieOptions.test_dublicate_path Apr 26 03:56:10 192.168.122.209 [42720.349565] [tdb] Start Tempesta DB Apr 26 03:56:10 192.168.122.209 [42720.497494] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:56:11 192.168.122.209 [42721.379268] [tempesta fw] ERROR: Duplicate argument: 'Path' Apr 26 03:56:11 192.168.122.209 [42721.380869] [tempesta fw] ERROR: configuration parsing error: [42721.380869] 11: cookie_options Path=/ Path=/etc; [42721.380869] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 03:56:11 192.168.122.209 [42721.385408] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 03:56:11 192.168.122.209 [42721.572989] [tempesta fw] exiting... Apr 26 03:56:11 192.168.122.209 [42721.690696] [tdb] Shutdown Tempesta DB Apr 26 03:56:11 192.168.122.209 [42722.187400] End test: sessions.test_cookies.StickyCookieOptions.test_dublicate_path Apr 26 03:56:11 192.168.122.209 [42722.199823] Start test: sessions.test_cookies.StickyCookieOptions.test_empty_options Apr 26 03:56:12 192.168.122.209 [42723.224475] [tdb] Start Tempesta DB Apr 26 03:56:13 192.168.122.209 [42723.379942] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:56:14 192.168.122.209 [42724.370576] [tempesta fw] Configuration processing is completed. Apr 26 03:56:14 192.168.122.209 [42724.430077] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:56:14 192.168.122.209 [42724.841644] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:56:14 192.168.122.209 [42724.868238] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:56:14 192.168.122.209 [42724.894514] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:56:14 192.168.122.209 [42725.010530] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:56:14 192.168.122.209 [42725.090477] [tempesta fw] Tempesta FW is ready Apr 26 03:56:15 192.168.122.209 [42725.690008] [tdb] Close table 'client0.tdb' Apr 26 03:56:15 192.168.122.209 [42725.875174] [tdb] Close table 'sessions0.tdb' Apr 26 03:56:18 192.168.122.209 [42728.993897] [tdb] Close table 'cache0.tdb' Apr 26 03:56:18 192.168.122.209 [42729.223746] [tdb] Close table 'filter0.tdb' Apr 26 03:56:18 192.168.122.209 [42729.224176] [tempesta fw] modules are stopped Apr 26 03:56:19 192.168.122.209 [42729.415396] [tempesta fw] exiting... Apr 26 03:56:19 192.168.122.209 [42729.533617] [tdb] Shutdown Tempesta DB Apr 26 03:56:19 192.168.122.209 [42729.726935] End test: sessions.test_cookies.StickyCookieOptions.test_empty_options Apr 26 03:56:19 192.168.122.209 [42729.745255] Start test: sessions.test_cookies.StickyCookieOptions.test_empty_options_1 Apr 26 03:56:20 192.168.122.209 [42730.882882] [tdb] Start Tempesta DB Apr 26 03:56:20 192.168.122.209 [42731.045005] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:56:22 192.168.122.209 [42733.038972] [tempesta fw] Configuration processing is completed. Apr 26 03:56:22 192.168.122.209 [42733.121370] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:56:23 192.168.122.209 [42733.556202] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:56:23 192.168.122.209 [42733.581995] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:56:23 192.168.122.209 [42733.608452] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:56:23 192.168.122.209 [42733.686641] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:56:23 192.168.122.209 [42733.726602] [tempesta fw] Tempesta FW is ready Apr 26 03:56:24 192.168.122.209 [42734.357933] [tdb] Close table 'client0.tdb' Apr 26 03:56:24 192.168.122.209 [42734.559695] [tdb] Close table 'sessions0.tdb' Apr 26 03:56:27 192.168.122.209 [42737.664774] [tdb] Close table 'cache0.tdb' Apr 26 03:56:27 192.168.122.209 [42737.931921] [tdb] Close table 'filter0.tdb' Apr 26 03:56:27 192.168.122.209 [42737.932438] [tempesta fw] modules are stopped Apr 26 03:56:27 192.168.122.209 [42738.151490] [tempesta fw] exiting... Apr 26 03:56:27 192.168.122.209 [42738.276021] [tdb] Shutdown Tempesta DB Apr 26 03:56:28 192.168.122.209 [42738.470956] End test: sessions.test_cookies.StickyCookieOptions.test_empty_options_1 Apr 26 03:56:28 192.168.122.209 [42738.486142] Start test: sessions.test_cookies.StickyCookieOptions.test_empty_vhost_global_expires_and_sess_lifetime_are_set Apr 26 03:56:29 192.168.122.209 [42739.624443] [tdb] Start Tempesta DB Apr 26 03:56:29 192.168.122.209 [42739.761137] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:56:31 192.168.122.209 [42741.762762] [tempesta fw] Configuration processing is completed. Apr 26 03:56:31 192.168.122.209 [42741.813842] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:56:31 192.168.122.209 [42742.216913] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:56:31 192.168.122.209 [42742.242326] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:56:31 192.168.122.209 [42742.268169] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:56:32 192.168.122.209 [42742.354754] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:56:32 192.168.122.209 [42742.398715] [tempesta fw] Tempesta FW is ready Apr 26 03:56:32 192.168.122.209 [42743.071877] [tdb] Close table 'client0.tdb' Apr 26 03:56:32 192.168.122.209 [42743.273491] [tdb] Close table 'sessions0.tdb' Apr 26 03:56:36 192.168.122.209 [42746.413390] [tdb] Close table 'cache0.tdb' Apr 26 03:56:36 192.168.122.209 [42746.674799] [tdb] Close table 'filter0.tdb' Apr 26 03:56:36 192.168.122.209 [42746.675255] [tempesta fw] modules are stopped Apr 26 03:56:36 192.168.122.209 [42746.894581] [tempesta fw] exiting... Apr 26 03:56:36 192.168.122.209 [42747.022211] [tdb] Shutdown Tempesta DB Apr 26 03:56:36 192.168.122.209 [42747.213578] End test: sessions.test_cookies.StickyCookieOptions.test_empty_vhost_global_expires_and_sess_lifetime_are_set Apr 26 03:56:36 192.168.122.209 [42747.224928] Start test: sessions.test_cookies.StickyCookieOptions.test_empty_vhost_global_sess_lifetime_is_set Apr 26 03:56:37 192.168.122.209 [42748.326655] [tdb] Start Tempesta DB Apr 26 03:56:38 192.168.122.209 [42748.463988] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:56:40 192.168.122.209 [42750.446877] [tempesta fw] Configuration processing is completed. Apr 26 03:56:40 192.168.122.209 [42750.497345] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:56:40 192.168.122.209 [42750.911572] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:56:40 192.168.122.209 [42750.937865] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:56:40 192.168.122.209 [42750.964489] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:56:40 192.168.122.209 [42751.050893] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:56:40 192.168.122.209 [42751.106828] [tempesta fw] Tempesta FW is ready Apr 26 03:56:41 192.168.122.209 [42751.755562] [tdb] Close table 'client0.tdb' Apr 26 03:56:41 192.168.122.209 [42751.950724] [tdb] Close table 'sessions0.tdb' Apr 26 03:56:44 192.168.122.209 [42755.102826] [tdb] Close table 'cache0.tdb' Apr 26 03:56:45 192.168.122.209 [42755.368741] [tdb] Close table 'filter0.tdb' Apr 26 03:56:45 192.168.122.209 [42755.369193] [tempesta fw] modules are stopped Apr 26 03:56:45 192.168.122.209 [42755.569057] [tempesta fw] exiting... Apr 26 03:56:45 192.168.122.209 [42755.708163] [tdb] Shutdown Tempesta DB Apr 26 03:56:45 192.168.122.209 [42755.928328] End test: sessions.test_cookies.StickyCookieOptions.test_empty_vhost_global_sess_lifetime_is_set Apr 26 03:56:45 192.168.122.209 [42755.937266] Start test: sessions.test_cookies.StickyCookieOptions.test_vhost_and_global_options_other Apr 26 03:56:46 192.168.122.209 [42757.068595] [tdb] Start Tempesta DB Apr 26 03:56:46 192.168.122.209 [42757.219889] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:56:48 192.168.122.209 [42759.239006] [tempesta fw] Configuration processing is completed. Apr 26 03:56:48 192.168.122.209 [42759.290601] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:56:49 192.168.122.209 [42759.696580] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:56:49 192.168.122.209 [42759.730258] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:56:49 192.168.122.209 [42759.763361] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:56:49 192.168.122.209 [42759.842991] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:56:49 192.168.122.209 [42759.946830] [tempesta fw] Tempesta FW is ready Apr 26 03:56:50 192.168.122.209 [42760.568380] [tdb] Close table 'client0.tdb' Apr 26 03:56:50 192.168.122.209 [42760.754504] [tdb] Close table 'sessions0.tdb' Apr 26 03:56:53 192.168.122.209 [42764.006826] [tdb] Close table 'cache0.tdb' Apr 26 03:56:53 192.168.122.209 [42764.264024] [tdb] Close table 'filter0.tdb' Apr 26 03:56:53 192.168.122.209 [42764.264442] [tempesta fw] modules are stopped Apr 26 03:56:54 192.168.122.209 [42764.505739] [tempesta fw] exiting... Apr 26 03:56:54 192.168.122.209 [42764.660530] [tdb] Shutdown Tempesta DB Apr 26 03:56:54 192.168.122.209 [42764.848875] End test: sessions.test_cookies.StickyCookieOptions.test_vhost_and_global_options_other Apr 26 03:56:54 192.168.122.209 [42764.863064] Start test: sessions.test_cookies.StickyCookieOptions.test_vhost_expires_is_set Apr 26 03:56:55 192.168.122.209 [42766.004797] [tdb] Start Tempesta DB Apr 26 03:56:55 192.168.122.209 [42766.146402] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:56:57 192.168.122.209 [42768.099047] [tempesta fw] Configuration processing is completed. Apr 26 03:56:57 192.168.122.209 [42768.190748] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:56:58 192.168.122.209 [42768.610303] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:56:58 192.168.122.209 [42768.636226] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:56:58 192.168.122.209 [42768.661902] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:56:58 192.168.122.209 [42768.759110] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:56:58 192.168.122.209 [42768.811063] [tempesta fw] Tempesta FW is ready Apr 26 03:56:59 192.168.122.209 [42769.479502] [tdb] Close table 'client0.tdb' Apr 26 03:56:59 192.168.122.209 [42769.668005] [tdb] Close table 'sessions0.tdb' Apr 26 03:57:02 192.168.122.209 [42772.867665] [tdb] Close table 'cache0.tdb' Apr 26 03:57:02 192.168.122.209 [42773.124727] [tdb] Close table 'filter0.tdb' Apr 26 03:57:02 192.168.122.209 [42773.125151] [tempesta fw] modules are stopped Apr 26 03:57:03 192.168.122.209 [42773.368112] [tempesta fw] exiting... Apr 26 03:57:03 192.168.122.209 [42773.512017] [tdb] Shutdown Tempesta DB Apr 26 03:57:03 192.168.122.209 [42773.728004] End test: sessions.test_cookies.StickyCookieOptions.test_vhost_expires_is_set Apr 26 03:57:03 192.168.122.209 [42773.741357] Start test: sessions.test_cookies.StickyCookieOptions.test_vhost_max_age_is_set Apr 26 03:57:04 192.168.122.209 [42774.882485] [tdb] Start Tempesta DB Apr 26 03:57:04 192.168.122.209 [42775.033451] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:57:06 192.168.122.209 [42777.035187] [tempesta fw] Configuration processing is completed. Apr 26 03:57:06 192.168.122.209 [42777.089684] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:57:07 192.168.122.209 [42777.503550] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:57:07 192.168.122.209 [42777.540034] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:57:07 192.168.122.209 [42777.565519] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:57:07 192.168.122.209 [42777.663205] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:57:07 192.168.122.209 [42777.703141] [tempesta fw] Tempesta FW is ready Apr 26 03:57:07 192.168.122.209 [42778.331566] [tdb] Close table 'client0.tdb' Apr 26 03:57:08 192.168.122.209 [42778.537160] [tdb] Close table 'sessions0.tdb' Apr 26 03:57:11 192.168.122.209 [42781.721351] [tdb] Close table 'cache0.tdb' Apr 26 03:57:11 192.168.122.209 [42781.951249] [tdb] Close table 'filter0.tdb' Apr 26 03:57:11 192.168.122.209 [42781.951702] [tempesta fw] modules are stopped Apr 26 03:57:11 192.168.122.209 [42782.171610] [tempesta fw] exiting... Apr 26 03:57:11 192.168.122.209 [42782.337999] [tdb] Shutdown Tempesta DB Apr 26 03:57:12 192.168.122.209 [42782.560043] End test: sessions.test_cookies.StickyCookieOptions.test_vhost_max_age_is_set Apr 26 03:57:12 192.168.122.209 [42782.582353] Start test: sessions.test_cookies.StickyCookieOptions.test_vhost_sess_lifetime_and_global_sess_lifetime_and_max_age_are_set Apr 26 03:57:13 192.168.122.209 [42783.746636] [tdb] Start Tempesta DB Apr 26 03:57:13 192.168.122.209 [42783.896241] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:57:15 192.168.122.209 [42785.811306] [tempesta fw] Configuration processing is completed. Apr 26 03:57:15 192.168.122.209 [42785.861275] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:57:15 192.168.122.209 [42786.264104] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:57:15 192.168.122.209 [42786.289525] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:57:15 192.168.122.209 [42786.314780] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:57:16 192.168.122.209 [42786.415338] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:57:16 192.168.122.209 [42786.459267] [tempesta fw] Tempesta FW is ready Apr 26 03:57:16 192.168.122.209 [42787.057772] [tdb] Close table 'client0.tdb' Apr 26 03:57:16 192.168.122.209 [42787.260411] [tdb] Close table 'sessions0.tdb' Apr 26 03:57:20 192.168.122.209 [42790.430787] [tdb] Close table 'cache0.tdb' Apr 26 03:57:20 192.168.122.209 [42790.684982] [tdb] Close table 'filter0.tdb' Apr 26 03:57:20 192.168.122.209 [42790.685410] [tempesta fw] modules are stopped Apr 26 03:57:20 192.168.122.209 [42790.882467] [tempesta fw] exiting... Apr 26 03:57:20 192.168.122.209 [42791.045374] [tdb] Shutdown Tempesta DB Apr 26 03:57:20 192.168.122.209 [42791.268897] End test: sessions.test_cookies.StickyCookieOptions.test_vhost_sess_lifetime_and_global_sess_lifetime_and_max_age_are_set Apr 26 03:57:20 192.168.122.209 [42791.290390] Start test: sessions.test_cookies.TestCookieDockerH2.test Apr 26 03:57:23 192.168.122.209 [42793.455364] docker0: port 1(vethae40c4d) entered blocking state Apr 26 03:57:23 192.168.122.209 [42793.456449] docker0: port 1(vethae40c4d) entered disabled state Apr 26 03:57:23 192.168.122.209 [42793.460020] device vethae40c4d entered promiscuous mode Apr 26 03:57:23 192.168.122.209 [42794.085254] eth0: renamed from vethde3152d Apr 26 03:57:23 192.168.122.209 [42794.105721] IPv6: ADDRCONF(NETDEV_CHANGE): vethae40c4d: link becomes ready Apr 26 03:57:23 192.168.122.209 [42794.107129] docker0: port 1(vethae40c4d) entered blocking state Apr 26 03:57:23 192.168.122.209 [42794.107938] docker0: port 1(vethae40c4d) entered forwarding state Apr 26 03:57:24 192.168.122.209 [42795.153812] [tdb] Start Tempesta DB Apr 26 03:57:24 192.168.122.209 [42795.296522] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:57:26 192.168.122.209 [42796.857519] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [42796.857519] Maybe that's fine, but it's worth checking the [42796.857519] config - if there is no relations between the [42796.857519] names, then host name confusion attack is possible. Apr 26 03:57:26 192.168.122.209 [42797.011686] [tempesta fw] Configuration processing is completed. Apr 26 03:57:26 192.168.122.209 [42797.061616] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:57:27 192.168.122.209 [42797.467471] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:57:27 192.168.122.209 [42797.493257] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:57:27 192.168.122.209 [42797.528084] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:57:27 192.168.122.209 [42797.611668] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:57:27 192.168.122.209 [42797.613453] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:57:27 192.168.122.209 [42797.671748] [tempesta fw] Tempesta FW is ready Apr 26 03:57:28 192.168.122.209 [42798.428007] [tdb] Close table 'client0.tdb' Apr 26 03:57:28 192.168.122.209 [42798.630694] [tdb] Close table 'sessions0.tdb' Apr 26 03:57:31 192.168.122.209 [42801.835073] [tdb] Close table 'cache0.tdb' Apr 26 03:57:31 192.168.122.209 [42802.103512] [tdb] Close table 'filter0.tdb' Apr 26 03:57:31 192.168.122.209 [42802.103938] [tempesta fw] modules are stopped Apr 26 03:57:31 192.168.122.209 [42802.332735] [tempesta fw] exiting... Apr 26 03:57:32 192.168.122.209 [42802.504467] [tdb] Shutdown Tempesta DB Apr 26 03:57:32 192.168.122.209 [42802.975709] docker0: port 1(vethae40c4d) entered disabled state Apr 26 03:57:32 192.168.122.209 [42802.976401] vethde3152d: renamed from eth0 Apr 26 03:57:32 192.168.122.209 [42803.039808] docker0: port 1(vethae40c4d) entered disabled state Apr 26 03:57:32 192.168.122.209 [42803.047748] device vethae40c4d left promiscuous mode Apr 26 03:57:32 192.168.122.209 [42803.048591] docker0: port 1(vethae40c4d) entered disabled state Apr 26 03:57:32 192.168.122.209 [42803.303128] End test: sessions.test_cookies.TestCookieDockerH2.test Apr 26 03:57:32 192.168.122.209 [42803.311230] Start test: sessions.test_cookies.TestCookieDockerHttp.test Apr 26 03:57:34 192.168.122.209 [42804.684221] docker0: port 1(vethccd1389) entered blocking state Apr 26 03:57:34 192.168.122.209 [42804.684836] docker0: port 1(vethccd1389) entered disabled state Apr 26 03:57:34 192.168.122.209 [42804.686801] device vethccd1389 entered promiscuous mode Apr 26 03:57:34 192.168.122.209 [42804.689364] docker0: port 1(vethccd1389) entered blocking state Apr 26 03:57:34 192.168.122.209 [42804.689959] docker0: port 1(vethccd1389) entered forwarding state Apr 26 03:57:34 192.168.122.209 [42804.690940] docker0: port 1(vethccd1389) entered disabled state Apr 26 03:57:34 192.168.122.209 [42805.202237] eth0: renamed from vethcc95c66 Apr 26 03:57:34 192.168.122.209 [42805.244034] IPv6: ADDRCONF(NETDEV_CHANGE): vethccd1389: link becomes ready Apr 26 03:57:34 192.168.122.209 [42805.245095] docker0: port 1(vethccd1389) entered blocking state Apr 26 03:57:34 192.168.122.209 [42805.245672] docker0: port 1(vethccd1389) entered forwarding state Apr 26 03:57:36 192.168.122.209 [42806.358004] [tdb] Start Tempesta DB Apr 26 03:57:36 192.168.122.209 [42806.495194] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:57:37 192.168.122.209 [42807.997743] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [42807.997743] Maybe that's fine, but it's worth checking the [42807.997743] config - if there is no relations between the [42807.997743] names, then host name confusion attack is possible. Apr 26 03:57:37 192.168.122.209 [42808.187629] [tempesta fw] Configuration processing is completed. Apr 26 03:57:37 192.168.122.209 [42808.237765] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:57:38 192.168.122.209 [42808.638567] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:57:38 192.168.122.209 [42808.663912] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:57:38 192.168.122.209 [42808.689269] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:57:38 192.168.122.209 [42808.776440] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:57:38 192.168.122.209 [42808.778194] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:57:38 192.168.122.209 [42808.823551] [tempesta fw] Tempesta FW is ready Apr 26 03:57:39 192.168.122.209 [42809.582749] [tdb] Close table 'client0.tdb' Apr 26 03:57:39 192.168.122.209 [42809.771498] [tdb] Close table 'sessions0.tdb' Apr 26 03:57:42 192.168.122.209 [42812.928433] [tdb] Close table 'cache0.tdb' Apr 26 03:57:42 192.168.122.209 [42813.203757] [tdb] Close table 'filter0.tdb' Apr 26 03:57:42 192.168.122.209 [42813.204192] [tempesta fw] modules are stopped Apr 26 03:57:43 192.168.122.209 [42813.451319] [tempesta fw] exiting... Apr 26 03:57:43 192.168.122.209 [42813.579197] [tdb] Shutdown Tempesta DB Apr 26 03:57:43 192.168.122.209 [42814.121710] docker0: port 1(vethccd1389) entered disabled state Apr 26 03:57:43 192.168.122.209 [42814.122411] vethcc95c66: renamed from eth0 Apr 26 03:57:43 192.168.122.209 [42814.189688] docker0: port 1(vethccd1389) entered disabled state Apr 26 03:57:43 192.168.122.209 [42814.201049] device vethccd1389 left promiscuous mode Apr 26 03:57:43 192.168.122.209 [42814.201548] docker0: port 1(vethccd1389) entered disabled state Apr 26 03:57:44 192.168.122.209 [42814.367045] End test: sessions.test_cookies.TestCookieDockerHttp.test Apr 26 03:57:44 192.168.122.209 [42814.376683] Start test: sessions.test_cookies.TestCookieDockerHttps.test Apr 26 03:57:45 192.168.122.209 [42815.843006] docker0: port 1(vethe30a54d) entered blocking state Apr 26 03:57:45 192.168.122.209 [42815.843838] docker0: port 1(vethe30a54d) entered disabled state Apr 26 03:57:45 192.168.122.209 [42815.846064] device vethe30a54d entered promiscuous mode Apr 26 03:57:45 192.168.122.209 [42815.847898] docker0: port 1(vethe30a54d) entered blocking state Apr 26 03:57:45 192.168.122.209 [42815.848488] docker0: port 1(vethe30a54d) entered forwarding state Apr 26 03:57:45 192.168.122.209 [42815.849759] docker0: port 1(vethe30a54d) entered disabled state Apr 26 03:57:45 192.168.122.209 [42816.331034] eth0: renamed from veth658537b Apr 26 03:57:46 192.168.122.209 [42816.356758] IPv6: ADDRCONF(NETDEV_CHANGE): vethe30a54d: link becomes ready Apr 26 03:57:46 192.168.122.209 [42816.358065] docker0: port 1(vethe30a54d) entered blocking state Apr 26 03:57:46 192.168.122.209 [42816.358806] docker0: port 1(vethe30a54d) entered forwarding state Apr 26 03:57:47 192.168.122.209 [42817.444313] [tdb] Start Tempesta DB Apr 26 03:57:47 192.168.122.209 [42817.585705] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:57:48 192.168.122.209 [42819.088755] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [42819.088755] Maybe that's fine, but it's worth checking the [42819.088755] config - if there is no relations between the [42819.088755] names, then host name confusion attack is possible. Apr 26 03:57:48 192.168.122.209 [42819.251763] [tempesta fw] Configuration processing is completed. Apr 26 03:57:48 192.168.122.209 [42819.301523] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:57:49 192.168.122.209 [42819.704135] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:57:49 192.168.122.209 [42819.735243] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:57:49 192.168.122.209 [42819.760276] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:57:49 192.168.122.209 [42819.857220] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:57:49 192.168.122.209 [42819.858176] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:57:49 192.168.122.209 [42819.923675] [tempesta fw] Tempesta FW is ready Apr 26 03:57:50 192.168.122.209 [42820.662353] [tdb] Close table 'client0.tdb' Apr 26 03:57:50 192.168.122.209 [42820.859501] [tdb] Close table 'sessions0.tdb' Apr 26 03:57:53 192.168.122.209 [42823.993528] [tdb] Close table 'cache0.tdb' Apr 26 03:57:53 192.168.122.209 [42824.267093] [tdb] Close table 'filter0.tdb' Apr 26 03:57:53 192.168.122.209 [42824.267528] [tempesta fw] modules are stopped Apr 26 03:57:54 192.168.122.209 [42824.615188] [tempesta fw] exiting... Apr 26 03:57:54 192.168.122.209 [42824.743860] [tdb] Shutdown Tempesta DB Apr 26 03:57:54 192.168.122.209 [42825.178351] docker0: port 1(vethe30a54d) entered disabled state Apr 26 03:57:54 192.168.122.209 [42825.179055] veth658537b: renamed from eth0 Apr 26 03:57:54 192.168.122.209 [42825.245324] docker0: port 1(vethe30a54d) entered disabled state Apr 26 03:57:54 192.168.122.209 [42825.251969] device vethe30a54d left promiscuous mode Apr 26 03:57:54 192.168.122.209 [42825.252486] docker0: port 1(vethe30a54d) entered disabled state Apr 26 03:57:55 192.168.122.209 [42825.499506] End test: sessions.test_cookies.TestCookieDockerHttps.test Apr 26 03:57:55 192.168.122.209 [42825.517782] Start test: sessions.test_cookies.VhostCookies.test_cookie Apr 26 03:57:56 192.168.122.209 [42826.510200] [tdb] Start Tempesta DB Apr 26 03:57:56 192.168.122.209 [42826.668116] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:57:58 192.168.122.209 [42828.995917] [tempesta fw] Configuration processing is completed. Apr 26 03:57:58 192.168.122.209 [42829.047223] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:57:59 192.168.122.209 [42829.460448] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:57:59 192.168.122.209 [42829.486377] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:57:59 192.168.122.209 [42829.512633] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:57:59 192.168.122.209 [42829.643855] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:57:59 192.168.122.209 [42829.683814] [tempesta fw] Tempesta FW is ready Apr 26 03:58:00 192.168.122.209 [42830.651553] [tdb] Close table 'client0.tdb' Apr 26 03:58:00 192.168.122.209 [42830.847194] [tdb] Close table 'sessions0.tdb' Apr 26 03:58:03 192.168.122.209 [42833.959410] [tdb] Close table 'cache0.tdb' Apr 26 03:58:03 192.168.122.209 [42834.199214] [tdb] Close table 'filter0.tdb' Apr 26 03:58:03 192.168.122.209 [42834.199661] [tempesta fw] modules are stopped Apr 26 03:58:04 192.168.122.209 [42834.433157] [tempesta fw] exiting... Apr 26 03:58:04 192.168.122.209 [42834.564769] [tdb] Shutdown Tempesta DB Apr 26 03:58:04 192.168.122.209 [42834.776517] End test: sessions.test_cookies.VhostCookies.test_cookie Apr 26 03:58:04 192.168.122.209 [42834.785624] Start test: sessions.test_h2_sticky_scheduler.H2StickySchedulerTestCase.test_h2_cookie_scheduler Apr 26 03:58:05 192.168.122.209 [42836.173937] [tdb] Start Tempesta DB Apr 26 03:58:05 192.168.122.209 [42836.334793] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:58:07 192.168.122.209 [42838.189241] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [42838.189241] Maybe that's fine, but it's worth checking the [42838.189241] config - if there is no relations between the [42838.189241] names, then host name confusion attack is possible. Apr 26 03:58:07 192.168.122.209 [42838.324015] [tempesta fw] Configuration processing is completed. Apr 26 03:58:08 192.168.122.209 [42838.374682] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:58:08 192.168.122.209 [42838.809352] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:58:08 192.168.122.209 [42838.836984] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:58:08 192.168.122.209 [42838.865363] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:58:08 192.168.122.209 [42838.939974] [tempesta fw] Open listen socket on: 127.0.0.1:8765 Apr 26 03:58:08 192.168.122.209 [42838.979962] [tempesta fw] Tempesta FW is ready Apr 26 03:58:09 192.168.122.209 [42839.350495] [tempesta fw] Warning: request has been filtered out via http table: 127.0.0.2 Apr 26 03:58:09 192.168.122.209 [42839.901436] [tdb] Close table 'client0.tdb' Apr 26 03:58:09 192.168.122.209 [42840.105677] [tdb] Close table 'sessions0.tdb' Apr 26 03:58:12 192.168.122.209 [42843.307766] [tdb] Close table 'cache0.tdb' Apr 26 03:58:13 192.168.122.209 [42843.558246] [tdb] Close table 'filter0.tdb' Apr 26 03:58:13 192.168.122.209 [42843.558670] [tempesta fw] modules are stopped Apr 26 03:58:13 192.168.122.209 [42843.809761] [tempesta fw] exiting... Apr 26 03:58:13 192.168.122.209 [42843.931621] [tdb] Shutdown Tempesta DB Apr 26 03:58:13 192.168.122.209 [42844.194094] End test: sessions.test_h2_sticky_scheduler.H2StickySchedulerTestCase.test_h2_cookie_scheduler Apr 26 03:58:13 192.168.122.209 [42844.245978] Start test: sessions.test_js_challenge.JSChallengeCookieExpiresAndMethodOverrideH2.test_cookie_expires Apr 26 03:58:15 192.168.122.209 [42845.435728] [tdb] Start Tempesta DB Apr 26 03:58:15 192.168.122.209 [42845.597759] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:58:17 192.168.122.209 [42847.529372] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [42847.529372] Maybe that's fine, but it's worth checking the [42847.529372] config - if there is no relations between the [42847.529372] names, then host name confusion attack is possible. Apr 26 03:58:17 192.168.122.209 [42847.662099] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 03:58:17 192.168.122.209 [42847.700509] [tempesta fw] Configuration processing is completed. Apr 26 03:58:17 192.168.122.209 [42847.750524] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:58:17 192.168.122.209 [42848.164266] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:58:17 192.168.122.209 [42848.199841] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:58:17 192.168.122.209 [42848.226825] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:58:17 192.168.122.209 [42848.272101] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:58:17 192.168.122.209 [42848.273837] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:58:17 192.168.122.209 [42848.312040] [tempesta fw] Tempesta FW is ready Apr 26 03:58:21 192.168.122.209 [42851.553273] [tempesta fw] Warning: http_sess: sticky cookie value expired for 127.0.0.2 (issued=4305603943 lifetime=750 now=4305604720) Apr 26 03:58:21 192.168.122.209 [42852.075573] [tdb] Close table 'client0.tdb' Apr 26 03:58:21 192.168.122.209 [42852.282776] [tdb] Close table 'sessions0.tdb' Apr 26 03:58:25 192.168.122.209 [42855.397407] [tdb] Close table 'cache0.tdb' Apr 26 03:58:25 192.168.122.209 [42855.626459] [tdb] Close table 'filter0.tdb' Apr 26 03:58:25 192.168.122.209 [42855.626896] [tempesta fw] modules are stopped Apr 26 03:58:25 192.168.122.209 [42855.809503] [tempesta fw] exiting... Apr 26 03:58:25 192.168.122.209 [42855.957696] [tdb] Shutdown Tempesta DB Apr 26 03:58:25 192.168.122.209 [42856.154068] End test: sessions.test_js_challenge.JSChallengeCookieExpiresAndMethodOverrideH2.test_cookie_expires Apr 26 03:58:25 192.168.122.209 [42856.209962] Start test: sessions.test_js_challenge.JSChallengeCookieExpiresAndMethodOverrideHttp.test_cookie_expires Apr 26 03:58:27 192.168.122.209 [42857.450171] [tdb] Start Tempesta DB Apr 26 03:58:27 192.168.122.209 [42857.600695] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:58:29 192.168.122.209 [42859.509512] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [42859.509512] Maybe that's fine, but it's worth checking the [42859.509512] config - if there is no relations between the [42859.509512] names, then host name confusion attack is possible. Apr 26 03:58:29 192.168.122.209 [42859.645258] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 03:58:29 192.168.122.209 [42859.688250] [tempesta fw] Configuration processing is completed. Apr 26 03:58:29 192.168.122.209 [42859.739653] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:58:29 192.168.122.209 [42860.186758] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:58:29 192.168.122.209 [42860.215837] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:58:29 192.168.122.209 [42860.243777] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:58:29 192.168.122.209 [42860.312255] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:58:29 192.168.122.209 [42860.313991] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:58:30 192.168.122.209 [42860.352205] [tempesta fw] Tempesta FW is ready Apr 26 03:58:33 192.168.122.209 [42863.608564] [tempesta fw] Warning: http_sess: sticky cookie value expired for 127.0.0.2 (issued=4305606957 lifetime=750 now=4305607734) Apr 26 03:58:33 192.168.122.209 [42864.102600] [tdb] Close table 'client0.tdb' Apr 26 03:58:33 192.168.122.209 [42864.292800] [tdb] Close table 'sessions0.tdb' Apr 26 03:58:37 192.168.122.209 [42867.477323] [tdb] Close table 'cache0.tdb' Apr 26 03:58:37 192.168.122.209 [42867.716007] [tdb] Close table 'filter0.tdb' Apr 26 03:58:37 192.168.122.209 [42867.716502] [tempesta fw] modules are stopped Apr 26 03:58:37 192.168.122.209 [42867.902430] [tempesta fw] exiting... Apr 26 03:58:37 192.168.122.209 [42868.027177] [tdb] Shutdown Tempesta DB Apr 26 03:58:37 192.168.122.209 [42868.234987] End test: sessions.test_js_challenge.JSChallengeCookieExpiresAndMethodOverrideHttp.test_cookie_expires Apr 26 03:58:37 192.168.122.209 [42868.297112] Start test: sessions.test_js_challenge.JSChallengeH2.test_cookies_in_request_multiple_in_one Apr 26 03:58:39 192.168.122.209 [42869.445537] [tdb] Start Tempesta DB Apr 26 03:58:39 192.168.122.209 [42869.595880] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:58:41 192.168.122.209 [42871.649264] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [42871.649264] Maybe that's fine, but it's worth checking the [42871.649264] config - if there is no relations between the [42871.649264] names, then host name confusion attack is possible. Apr 26 03:58:41 192.168.122.209 [42871.818477] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 03:58:41 192.168.122.209 [42871.856412] [tempesta fw] Configuration processing is completed. Apr 26 03:58:41 192.168.122.209 [42871.908085] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:58:42 192.168.122.209 [42872.353375] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:58:42 192.168.122.209 [42872.381490] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:58:42 192.168.122.209 [42872.409688] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:58:42 192.168.122.209 [42872.452408] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:58:42 192.168.122.209 [42872.454141] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:58:42 192.168.122.209 [42872.496357] [tempesta fw] Tempesta FW is ready Apr 26 03:58:46 192.168.122.209 [42877.145825] [tempesta fw] Warning: Multiple Tempesta sticky cookies found in request: 2 Apr 26 03:58:46 192.168.122.209 [42877.148098] [tempesta fw] Warning: request dropped: internal error in Sticky module: 127.0.0.2 Apr 26 03:58:47 192.168.122.209 [42877.601211] [tdb] Close table 'client0.tdb' Apr 26 03:58:47 192.168.122.209 [42877.798937] [tdb] Close table 'sessions0.tdb' Apr 26 03:58:50 192.168.122.209 [42881.040876] [tdb] Close table 'cache0.tdb' Apr 26 03:58:50 192.168.122.209 [42881.275288] [tdb] Close table 'filter0.tdb' Apr 26 03:58:50 192.168.122.209 [42881.275714] [tempesta fw] modules are stopped Apr 26 03:58:51 192.168.122.209 [42881.464150] [tempesta fw] exiting... Apr 26 03:58:51 192.168.122.209 [42881.629888] [tdb] Shutdown Tempesta DB Apr 26 03:58:51 192.168.122.209 [42881.892639] End test: sessions.test_js_challenge.JSChallengeH2.test_cookies_in_request_multiple_in_one Apr 26 03:58:51 192.168.122.209 [42881.903684] Start test: sessions.test_js_challenge.JSChallengeH2.test_cookies_in_request_multiple_in_two Apr 26 03:58:52 192.168.122.209 [42883.088912] [tdb] Start Tempesta DB Apr 26 03:58:52 192.168.122.209 [42883.229437] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:58:54 192.168.122.209 [42885.305865] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [42885.305865] Maybe that's fine, but it's worth checking the [42885.305865] config - if there is no relations between the [42885.305865] names, then host name confusion attack is possible. Apr 26 03:58:55 192.168.122.209 [42885.466654] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 03:58:55 192.168.122.209 [42885.508590] [tempesta fw] Configuration processing is completed. Apr 26 03:58:55 192.168.122.209 [42885.560128] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:58:55 192.168.122.209 [42885.980591] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:58:55 192.168.122.209 [42886.006756] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:58:55 192.168.122.209 [42886.041766] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:58:55 192.168.122.209 [42886.100615] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:58:55 192.168.122.209 [42886.102323] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:58:55 192.168.122.209 [42886.152521] [tempesta fw] Tempesta FW is ready Apr 26 03:58:59 192.168.122.209 [42890.232436] [tempesta fw] Warning: Multiple Tempesta sticky cookies found in request: 2 Apr 26 03:58:59 192.168.122.209 [42890.233185] [tempesta fw] Warning: request dropped: internal error in Sticky module: 127.0.0.2 Apr 26 03:59:00 192.168.122.209 [42890.679981] [tdb] Close table 'client0.tdb' Apr 26 03:59:00 192.168.122.209 [42890.859889] [tdb] Close table 'sessions0.tdb' Apr 26 03:59:03 192.168.122.209 [42894.135536] [tdb] Close table 'cache0.tdb' Apr 26 03:59:04 192.168.122.209 [42894.381825] [tdb] Close table 'filter0.tdb' Apr 26 03:59:04 192.168.122.209 [42894.382282] [tempesta fw] modules are stopped Apr 26 03:59:04 192.168.122.209 [42894.599263] [tempesta fw] exiting... Apr 26 03:59:04 192.168.122.209 [42894.766888] [tdb] Shutdown Tempesta DB Apr 26 03:59:04 192.168.122.209 [42895.012919] End test: sessions.test_js_challenge.JSChallengeH2.test_cookies_in_request_multiple_in_two Apr 26 03:59:04 192.168.122.209 [42895.023454] Start test: sessions.test_js_challenge.JSChallengeH2.test_delay_pass Apr 26 03:59:05 192.168.122.209 [42896.165857] [tdb] Start Tempesta DB Apr 26 03:59:05 192.168.122.209 [42896.311696] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:59:07 192.168.122.209 [42898.330135] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [42898.330135] Maybe that's fine, but it's worth checking the [42898.330135] config - if there is no relations between the [42898.330135] names, then host name confusion attack is possible. Apr 26 03:59:08 192.168.122.209 [42898.494884] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 03:59:08 192.168.122.209 [42898.548799] [tempesta fw] Configuration processing is completed. Apr 26 03:59:08 192.168.122.209 [42898.604478] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:59:08 192.168.122.209 [42899.014874] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:59:08 192.168.122.209 [42899.042486] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:59:08 192.168.122.209 [42899.070419] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:59:08 192.168.122.209 [42899.112733] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:59:08 192.168.122.209 [42899.114471] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:59:08 192.168.122.209 [42899.152685] [tempesta fw] Tempesta FW is ready Apr 26 03:59:10 192.168.122.209 [42900.902019] [tdb] Close table 'client0.tdb' Apr 26 03:59:10 192.168.122.209 [42901.087868] [tdb] Close table 'sessions0.tdb' Apr 26 03:59:13 192.168.122.209 [42904.214662] [tdb] Close table 'cache0.tdb' Apr 26 03:59:14 192.168.122.209 [42904.465805] [tdb] Close table 'filter0.tdb' Apr 26 03:59:14 192.168.122.209 [42904.466248] [tempesta fw] modules are stopped Apr 26 03:59:14 192.168.122.209 [42904.660922] [tempesta fw] exiting... Apr 26 03:59:14 192.168.122.209 [42904.786249] [tdb] Shutdown Tempesta DB Apr 26 03:59:14 192.168.122.209 [42904.989618] End test: sessions.test_js_challenge.JSChallengeH2.test_delay_pass Apr 26 03:59:14 192.168.122.209 [42905.014178] Start test: sessions.test_js_challenge.JSChallengeH2.test_delay_pipelined_pass Apr 26 03:59:15 192.168.122.209 [42906.172701] [tdb] Start Tempesta DB Apr 26 03:59:15 192.168.122.209 [42906.337068] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:59:18 192.168.122.209 [42908.394116] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [42908.394116] Maybe that's fine, but it's worth checking the [42908.394116] config - if there is no relations between the [42908.394116] names, then host name confusion attack is possible. Apr 26 03:59:18 192.168.122.209 [42908.554933] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 03:59:18 192.168.122.209 [42908.596828] [tempesta fw] Configuration processing is completed. Apr 26 03:59:18 192.168.122.209 [42908.647256] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:59:18 192.168.122.209 [42909.070511] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:59:18 192.168.122.209 [42909.107775] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:59:18 192.168.122.209 [42909.135025] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:59:18 192.168.122.209 [42909.180863] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:59:18 192.168.122.209 [42909.182650] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:59:18 192.168.122.209 [42909.228822] [tempesta fw] Tempesta FW is ready Apr 26 03:59:21 192.168.122.209 [42912.023315] [tdb] Close table 'client0.tdb' Apr 26 03:59:21 192.168.122.209 [42912.219396] [tdb] Close table 'sessions0.tdb' Apr 26 03:59:25 192.168.122.209 [42915.433049] [tdb] Close table 'cache0.tdb' Apr 26 03:59:25 192.168.122.209 [42915.682752] [tdb] Close table 'filter0.tdb' Apr 26 03:59:25 192.168.122.209 [42915.683202] [tempesta fw] modules are stopped Apr 26 03:59:25 192.168.122.209 [42915.885747] [tempesta fw] exiting... Apr 26 03:59:25 192.168.122.209 [42916.065167] [tdb] Shutdown Tempesta DB Apr 26 03:59:25 192.168.122.209 [42916.275060] End test: sessions.test_js_challenge.JSChallengeH2.test_delay_pipelined_pass Apr 26 03:59:25 192.168.122.209 [42916.294193] Start test: sessions.test_js_challenge.JSChallengeH2.test_delay_pipelined_too_early Apr 26 03:59:27 192.168.122.209 [42917.538465] [tdb] Start Tempesta DB Apr 26 03:59:27 192.168.122.209 [42917.710307] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:59:29 192.168.122.209 [42919.802254] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [42919.802254] Maybe that's fine, but it's worth checking the [42919.802254] config - if there is no relations between the [42919.802254] names, then host name confusion attack is possible. Apr 26 03:59:29 192.168.122.209 [42919.991072] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 03:59:29 192.168.122.209 [42920.033026] [tempesta fw] Configuration processing is completed. Apr 26 03:59:29 192.168.122.209 [42920.089958] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:59:30 192.168.122.209 [42920.540651] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:59:30 192.168.122.209 [42920.568275] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:59:30 192.168.122.209 [42920.595616] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:59:30 192.168.122.209 [42920.641017] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:59:30 192.168.122.209 [42920.642727] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:59:30 192.168.122.209 [42920.688970] [tempesta fw] Tempesta FW is ready Apr 26 03:59:30 192.168.122.209 [42920.851496] [tempesta fw] Warning: http_sess: jsch redirect received too early for 127.0.0.2 (4305622044 is not after 4305622554) Apr 26 03:59:30 192.168.122.209 [42920.853653] [tempesta fw] Warning: frang: max rmisses exceeded for 127.0.0.2: 3 (lim=2) Apr 26 03:59:30 192.168.122.209 [42921.285850] [tdb] Close table 'client0.tdb' Apr 26 03:59:31 192.168.122.209 [42921.480192] [tdb] Close table 'sessions0.tdb' Apr 26 03:59:34 192.168.122.209 [42924.683818] [tdb] Close table 'cache0.tdb' Apr 26 03:59:34 192.168.122.209 [42924.964479] [tdb] Close table 'filter0.tdb' Apr 26 03:59:34 192.168.122.209 [42924.964942] [tempesta fw] modules are stopped Apr 26 03:59:34 192.168.122.209 [42925.148366] [tempesta fw] exiting... Apr 26 03:59:34 192.168.122.209 [42925.288249] [tdb] Shutdown Tempesta DB Apr 26 03:59:35 192.168.122.209 [42925.518969] End test: sessions.test_js_challenge.JSChallengeH2.test_delay_pipelined_too_early Apr 26 03:59:35 192.168.122.209 [42925.531639] Start test: sessions.test_js_challenge.JSChallengeH2.test_delay_too_small Apr 26 03:59:36 192.168.122.209 [42926.794165] [tdb] Start Tempesta DB Apr 26 03:59:36 192.168.122.209 [42926.957486] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:59:38 192.168.122.209 [42929.016849] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [42929.016849] Maybe that's fine, but it's worth checking the [42929.016849] config - if there is no relations between the [42929.016849] names, then host name confusion attack is possible. Apr 26 03:59:38 192.168.122.209 [42929.167217] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 03:59:38 192.168.122.209 [42929.217046] [tempesta fw] Configuration processing is completed. Apr 26 03:59:38 192.168.122.209 [42929.278081] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:59:39 192.168.122.209 [42929.782694] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:59:39 192.168.122.209 [42929.812607] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:59:39 192.168.122.209 [42929.841753] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:59:39 192.168.122.209 [42929.913179] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:59:39 192.168.122.209 [42929.914916] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:59:39 192.168.122.209 [42929.957102] [tempesta fw] Tempesta FW is ready Apr 26 03:59:39 192.168.122.209 [42930.110657] [tempesta fw] Warning: http_sess: jsch redirect received too early for 127.0.0.2 (4305624359 is not after 4305624698) Apr 26 03:59:40 192.168.122.209 [42930.550376] [tdb] Close table 'client0.tdb' Apr 26 03:59:40 192.168.122.209 [42930.754981] [tdb] Close table 'sessions0.tdb' Apr 26 03:59:43 192.168.122.209 [42933.946417] [tdb] Close table 'cache0.tdb' Apr 26 03:59:43 192.168.122.209 [42934.192859] [tdb] Close table 'filter0.tdb' Apr 26 03:59:43 192.168.122.209 [42934.193321] [tempesta fw] modules are stopped Apr 26 03:59:44 192.168.122.209 [42934.375705] [tempesta fw] exiting... Apr 26 03:59:44 192.168.122.209 [42934.511473] [tdb] Shutdown Tempesta DB Apr 26 03:59:44 192.168.122.209 [42934.730846] End test: sessions.test_js_challenge.JSChallengeH2.test_delay_too_small Apr 26 03:59:44 192.168.122.209 [42934.743012] Start test: sessions.test_js_challenge.JSChallengeH2.test_disable_challenge_on_reload Apr 26 03:59:45 192.168.122.209 [42935.919305] [tdb] Start Tempesta DB Apr 26 03:59:45 192.168.122.209 [42936.078738] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:59:47 192.168.122.209 [42938.162695] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [42938.162695] Maybe that's fine, but it's worth checking the [42938.162695] config - if there is no relations between the [42938.162695] names, then host name confusion attack is possible. Apr 26 03:59:48 192.168.122.209 [42938.354622] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 03:59:48 192.168.122.209 [42938.389565] [tempesta fw] Configuration processing is completed. Apr 26 03:59:48 192.168.122.209 [42938.443750] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:59:48 192.168.122.209 [42938.911590] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:59:48 192.168.122.209 [42938.943986] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:59:48 192.168.122.209 [42938.977369] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:59:48 192.168.122.209 [42939.021191] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:59:48 192.168.122.209 [42939.022963] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:59:48 192.168.122.209 [42939.069208] [tempesta fw] Tempesta FW is ready Apr 26 03:59:49 192.168.122.209 [42939.789029] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 03:59:49 192.168.122.209 [42939.850610] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [42939.850610] Maybe that's fine, but it's worth checking the [42939.850610] config - if there is no relations between the [42939.850610] names, then host name confusion attack is possible. Apr 26 03:59:49 192.168.122.209 [42940.105270] [tempesta fw] Configuration processing is completed. Apr 26 03:59:50 192.168.122.209 [42940.381828] [tempesta fw] Tempesta FW is ready Apr 26 03:59:50 192.168.122.209 [42940.871123] [tdb] Close table 'client0.tdb' Apr 26 03:59:50 192.168.122.209 [42941.075586] [tdb] Close table 'sessions0.tdb' Apr 26 03:59:53 192.168.122.209 [42944.218787] [tdb] Close table 'cache0.tdb' Apr 26 03:59:54 192.168.122.209 [42944.461871] [tdb] Close table 'filter0.tdb' Apr 26 03:59:54 192.168.122.209 [42944.462312] [tempesta fw] modules are stopped Apr 26 03:59:54 192.168.122.209 [42944.676652] [tempesta fw] exiting... Apr 26 03:59:54 192.168.122.209 [42944.852293] [tdb] Shutdown Tempesta DB Apr 26 03:59:54 192.168.122.209 [42945.092173] End test: sessions.test_js_challenge.JSChallengeH2.test_disable_challenge_on_reload Apr 26 03:59:54 192.168.122.209 [42945.112380] Start test: sessions.test_js_challenge.JSChallengeH2.test_enable_challenge_on_reload Apr 26 03:59:55 192.168.122.209 [42946.150524] [tdb] Start Tempesta DB Apr 26 03:59:55 192.168.122.209 [42946.312923] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 03:59:57 192.168.122.209 [42948.046553] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [42948.046553] Maybe that's fine, but it's worth checking the [42948.046553] config - if there is no relations between the [42948.046553] names, then host name confusion attack is possible. Apr 26 03:59:57 192.168.122.209 [42948.249376] [tempesta fw] Configuration processing is completed. Apr 26 03:59:57 192.168.122.209 [42948.302731] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 03:59:58 192.168.122.209 [42948.716351] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 03:59:58 192.168.122.209 [42948.741653] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 03:59:58 192.168.122.209 [42948.766972] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 03:59:58 192.168.122.209 [42948.813365] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 03:59:58 192.168.122.209 [42948.815124] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 03:59:58 192.168.122.209 [42948.853318] [tempesta fw] Tempesta FW is ready Apr 26 03:59:59 192.168.122.209 [42949.834586] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 03:59:59 192.168.122.209 [42949.922977] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [42949.922977] Maybe that's fine, but it's worth checking the [42949.922977] config - if there is no relations between the [42949.922977] names, then host name confusion attack is possible. Apr 26 03:59:59 192.168.122.209 [42950.147284] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 03:59:59 192.168.122.209 [42950.205403] [tempesta fw] Configuration processing is completed. Apr 26 04:00:00 192.168.122.209 [42950.485881] [tempesta fw] Tempesta FW is ready Apr 26 04:00:02 192.168.122.209 [42952.903262] [tdb] Close table 'client0.tdb' Apr 26 04:00:02 192.168.122.209 [42953.099662] [tdb] Close table 'sessions0.tdb' Apr 26 04:00:05 192.168.122.209 [42956.310303] [tdb] Close table 'cache0.tdb' Apr 26 04:00:06 192.168.122.209 [42956.547922] [tdb] Close table 'filter0.tdb' Apr 26 04:00:06 192.168.122.209 [42956.548368] [tempesta fw] modules are stopped Apr 26 04:00:06 192.168.122.209 [42956.732994] [tempesta fw] exiting... Apr 26 04:00:06 192.168.122.209 [42956.875700] [tdb] Shutdown Tempesta DB Apr 26 04:00:06 192.168.122.209 [42957.058298] End test: sessions.test_js_challenge.JSChallengeH2.test_enable_challenge_on_reload Apr 26 04:00:06 192.168.122.209 [42957.067423] Start test: sessions.test_js_challenge.JSChallengeH2.test_first_post_request_pipelined Apr 26 04:00:07 192.168.122.209 [42958.174178] [tdb] Start Tempesta DB Apr 26 04:00:07 192.168.122.209 [42958.328447] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:00:09 192.168.122.209 [42960.302761] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [42960.302761] Maybe that's fine, but it's worth checking the [42960.302761] config - if there is no relations between the [42960.302761] names, then host name confusion attack is possible. Apr 26 04:00:10 192.168.122.209 [42960.499531] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:00:10 192.168.122.209 [42960.553518] [tempesta fw] Configuration processing is completed. Apr 26 04:00:10 192.168.122.209 [42960.608252] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:00:10 192.168.122.209 [42961.026119] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:00:10 192.168.122.209 [42961.052619] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:00:10 192.168.122.209 [42961.079149] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:00:10 192.168.122.209 [42961.117578] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:00:10 192.168.122.209 [42961.119365] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:00:10 192.168.122.209 [42961.165522] [tempesta fw] Tempesta FW is ready Apr 26 04:00:13 192.168.122.209 [42963.390494] [tdb] Close table 'client0.tdb' Apr 26 04:00:13 192.168.122.209 [42963.598176] [tdb] Close table 'sessions0.tdb' Apr 26 04:00:16 192.168.122.209 [42966.781630] [tdb] Close table 'cache0.tdb' Apr 26 04:00:16 192.168.122.209 [42967.008245] [tdb] Close table 'filter0.tdb' Apr 26 04:00:16 192.168.122.209 [42967.008693] [tempesta fw] modules are stopped Apr 26 04:00:16 192.168.122.209 [42967.211541] [tempesta fw] exiting... Apr 26 04:00:17 192.168.122.209 [42967.358426] [tdb] Shutdown Tempesta DB Apr 26 04:00:17 192.168.122.209 [42967.580231] End test: sessions.test_js_challenge.JSChallengeH2.test_first_post_request_pipelined Apr 26 04:00:17 192.168.122.209 [42967.589148] Start test: sessions.test_js_challenge.JSChallengeH2.test_first_request_GET_and_accept_all Apr 26 04:00:18 192.168.122.209 [42968.800552] [tdb] Start Tempesta DB Apr 26 04:00:18 192.168.122.209 [42968.957336] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:00:20 192.168.122.209 [42971.030639] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [42971.030639] Maybe that's fine, but it's worth checking the [42971.030639] config - if there is no relations between the [42971.030639] names, then host name confusion attack is possible. Apr 26 04:00:20 192.168.122.209 [42971.207693] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:00:20 192.168.122.209 [42971.241835] [tempesta fw] Configuration processing is completed. Apr 26 04:00:20 192.168.122.209 [42971.292190] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:00:21 192.168.122.209 [42971.730650] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:00:21 192.168.122.209 [42971.758747] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:00:21 192.168.122.209 [42971.787006] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:00:21 192.168.122.209 [42971.833683] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:00:21 192.168.122.209 [42971.835221] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:00:21 192.168.122.209 [42971.885600] [tempesta fw] Tempesta FW is ready Apr 26 04:00:22 192.168.122.209 [42972.503361] [tdb] Close table 'client0.tdb' Apr 26 04:00:22 192.168.122.209 [42972.692940] [tdb] Close table 'sessions0.tdb' Apr 26 04:00:25 192.168.122.209 [42975.799317] [tdb] Close table 'cache0.tdb' Apr 26 04:00:25 192.168.122.209 [42976.052948] [tdb] Close table 'filter0.tdb' Apr 26 04:00:25 192.168.122.209 [42976.053371] [tempesta fw] modules are stopped Apr 26 04:00:25 192.168.122.209 [42976.303089] [tempesta fw] exiting... Apr 26 04:00:26 192.168.122.209 [42976.455631] [tdb] Shutdown Tempesta DB Apr 26 04:00:26 192.168.122.209 [42976.646277] End test: sessions.test_js_challenge.JSChallengeH2.test_first_request_GET_and_accept_all Apr 26 04:00:26 192.168.122.209 [42976.667039] Start test: sessions.test_js_challenge.JSChallengeH2.test_first_request_GET_and_accept_html Apr 26 04:00:27 192.168.122.209 [42977.812750] [tdb] Start Tempesta DB Apr 26 04:00:27 192.168.122.209 [42977.962649] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:00:29 192.168.122.209 [42980.083127] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [42980.083127] Maybe that's fine, but it's worth checking the [42980.083127] config - if there is no relations between the [42980.083127] names, then host name confusion attack is possible. Apr 26 04:00:29 192.168.122.209 [42980.239863] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:00:29 192.168.122.209 [42980.285804] [tempesta fw] Configuration processing is completed. Apr 26 04:00:29 192.168.122.209 [42980.340866] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:00:30 192.168.122.209 [42980.770725] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:00:30 192.168.122.209 [42980.797240] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:00:30 192.168.122.209 [42980.824113] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:00:30 192.168.122.209 [42980.869774] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:00:30 192.168.122.209 [42980.871513] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:00:30 192.168.122.209 [42980.925712] [tempesta fw] Tempesta FW is ready Apr 26 04:00:31 192.168.122.209 [42981.481235] [tdb] Close table 'client0.tdb' Apr 26 04:00:31 192.168.122.209 [42981.665474] [tdb] Close table 'sessions0.tdb' Apr 26 04:00:34 192.168.122.209 [42984.834704] [tdb] Close table 'cache0.tdb' Apr 26 04:00:34 192.168.122.209 [42985.082528] [tdb] Close table 'filter0.tdb' Apr 26 04:00:34 192.168.122.209 [42985.082972] [tempesta fw] modules are stopped Apr 26 04:00:34 192.168.122.209 [42985.298305] [tempesta fw] exiting... Apr 26 04:00:35 192.168.122.209 [42985.483916] [tdb] Shutdown Tempesta DB Apr 26 04:00:35 192.168.122.209 [42985.701469] End test: sessions.test_js_challenge.JSChallengeH2.test_first_request_GET_and_accept_html Apr 26 04:00:35 192.168.122.209 [42985.718299] Start test: sessions.test_js_challenge.JSChallengeH2.test_first_request_GET_and_accept_image Apr 26 04:00:36 192.168.122.209 [42986.942431] [tdb] Start Tempesta DB Apr 26 04:00:36 192.168.122.209 [42987.099243] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:00:38 192.168.122.209 [42989.171166] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [42989.171166] Maybe that's fine, but it's worth checking the [42989.171166] config - if there is no relations between the [42989.171166] names, then host name confusion attack is possible. Apr 26 04:00:38 192.168.122.209 [42989.335855] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:00:39 192.168.122.209 [42989.385885] [tempesta fw] Configuration processing is completed. Apr 26 04:00:39 192.168.122.209 [42989.436830] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:00:39 192.168.122.209 [42989.880295] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:00:39 192.168.122.209 [42989.907397] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:00:39 192.168.122.209 [42989.934430] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:00:39 192.168.122.209 [42989.985870] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:00:39 192.168.122.209 [42989.987582] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:00:39 192.168.122.209 [42990.025845] [tempesta fw] Tempesta FW is ready Apr 26 04:00:40 192.168.122.209 [42990.628668] [tdb] Close table 'client0.tdb' Apr 26 04:00:40 192.168.122.209 [42990.808218] [tdb] Close table 'sessions0.tdb' Apr 26 04:00:43 192.168.122.209 [42994.012312] [tdb] Close table 'cache0.tdb' Apr 26 04:00:43 192.168.122.209 [42994.234638] [tdb] Close table 'filter0.tdb' Apr 26 04:00:43 192.168.122.209 [42994.235083] [tempesta fw] modules are stopped Apr 26 04:00:44 192.168.122.209 [42994.432444] [tempesta fw] exiting... Apr 26 04:00:44 192.168.122.209 [42994.626767] [tdb] Shutdown Tempesta DB Apr 26 04:00:44 192.168.122.209 [42994.844694] End test: sessions.test_js_challenge.JSChallengeH2.test_first_request_GET_and_accept_image Apr 26 04:00:44 192.168.122.209 [42994.859091] Start test: sessions.test_js_challenge.JSChallengeH2.test_first_request_GET_and_accept_plain Apr 26 04:00:45 192.168.122.209 [42996.073391] [tdb] Start Tempesta DB Apr 26 04:00:45 192.168.122.209 [42996.232969] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:00:47 192.168.122.209 [42998.239253] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [42998.239253] Maybe that's fine, but it's worth checking the [42998.239253] config - if there is no relations between the [42998.239253] names, then host name confusion attack is possible. Apr 26 04:00:48 192.168.122.209 [42998.400075] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:00:48 192.168.122.209 [42998.449999] [tempesta fw] Configuration processing is completed. Apr 26 04:00:48 192.168.122.209 [42998.501019] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:00:48 192.168.122.209 [42998.964602] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:00:48 192.168.122.209 [42998.992746] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:00:48 192.168.122.209 [42999.022100] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:00:48 192.168.122.209 [42999.090046] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:00:48 192.168.122.209 [42999.091780] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:00:48 192.168.122.209 [42999.141989] [tempesta fw] Tempesta FW is ready Apr 26 04:00:49 192.168.122.209 [42999.774950] [tdb] Close table 'client0.tdb' Apr 26 04:00:49 192.168.122.209 [42999.963286] [tdb] Close table 'sessions0.tdb' Apr 26 04:00:52 192.168.122.209 [43003.199386] [tdb] Close table 'cache0.tdb' Apr 26 04:00:53 192.168.122.209 [43003.459899] [tdb] Close table 'filter0.tdb' Apr 26 04:00:53 192.168.122.209 [43003.460336] [tempesta fw] modules are stopped Apr 26 04:00:53 192.168.122.209 [43003.647981] [tempesta fw] exiting... Apr 26 04:00:53 192.168.122.209 [43003.776485] [tdb] Shutdown Tempesta DB Apr 26 04:00:53 192.168.122.209 [43003.980815] End test: sessions.test_js_challenge.JSChallengeH2.test_first_request_GET_and_accept_plain Apr 26 04:00:53 192.168.122.209 [43003.993497] Start test: sessions.test_js_challenge.JSChallengeH2.test_first_request_GET_and_accept_text_all Apr 26 04:00:54 192.168.122.209 [43005.170499] [tdb] Start Tempesta DB Apr 26 04:00:54 192.168.122.209 [43005.334095] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:00:57 192.168.122.209 [43007.387363] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43007.387363] Maybe that's fine, but it's worth checking the [43007.387363] config - if there is no relations between the [43007.387363] names, then host name confusion attack is possible. Apr 26 04:00:57 192.168.122.209 [43007.572493] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:00:57 192.168.122.209 [43007.614120] [tempesta fw] Configuration processing is completed. Apr 26 04:00:57 192.168.122.209 [43007.664525] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:00:57 192.168.122.209 [43008.071185] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:00:57 192.168.122.209 [43008.099183] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:00:57 192.168.122.209 [43008.137102] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:00:57 192.168.122.209 [43008.186065] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:00:57 192.168.122.209 [43008.187256] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:00:57 192.168.122.209 [43008.230062] [tempesta fw] Tempesta FW is ready Apr 26 04:00:58 192.168.122.209 [43008.787401] [tdb] Close table 'client0.tdb' Apr 26 04:00:58 192.168.122.209 [43008.980529] [tdb] Close table 'sessions0.tdb' Apr 26 04:01:01 192.168.122.209 [43012.160408] [tdb] Close table 'cache0.tdb' Apr 26 04:01:02 192.168.122.209 [43012.410563] [tdb] Close table 'filter0.tdb' Apr 26 04:01:02 192.168.122.209 [43012.410995] [tempesta fw] modules are stopped Apr 26 04:01:02 192.168.122.209 [43012.606706] [tempesta fw] exiting... Apr 26 04:01:02 192.168.122.209 [43012.742661] [tdb] Shutdown Tempesta DB Apr 26 04:01:02 192.168.122.209 [43012.963062] End test: sessions.test_js_challenge.JSChallengeH2.test_first_request_GET_and_accept_text_all Apr 26 04:01:02 192.168.122.209 [43012.978018] Start test: sessions.test_js_challenge.JSChallengeH2.test_first_request_POST Apr 26 04:01:03 192.168.122.209 [43014.151207] [tdb] Start Tempesta DB Apr 26 04:01:03 192.168.122.209 [43014.307332] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:01:05 192.168.122.209 [43016.307573] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43016.307573] Maybe that's fine, but it's worth checking the [43016.307573] config - if there is no relations between the [43016.307573] names, then host name confusion attack is possible. Apr 26 04:01:06 192.168.122.209 [43016.472461] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:01:06 192.168.122.209 [43016.514317] [tempesta fw] Configuration processing is completed. Apr 26 04:01:06 192.168.122.209 [43016.593036] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:01:06 192.168.122.209 [43017.057931] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:01:06 192.168.122.209 [43017.087111] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:01:06 192.168.122.209 [43017.116751] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:01:06 192.168.122.209 [43017.154188] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:01:06 192.168.122.209 [43017.156130] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:01:06 192.168.122.209 [43017.194131] [tempesta fw] Tempesta FW is ready Apr 26 04:01:07 192.168.122.209 [43017.794439] [tdb] Close table 'client0.tdb' Apr 26 04:01:07 192.168.122.209 [43017.993620] [tdb] Close table 'sessions0.tdb' Apr 26 04:01:10 192.168.122.209 [43021.169073] [tdb] Close table 'cache0.tdb' Apr 26 04:01:11 192.168.122.209 [43021.389198] [tdb] Close table 'filter0.tdb' Apr 26 04:01:11 192.168.122.209 [43021.389635] [tempesta fw] modules are stopped Apr 26 04:01:11 192.168.122.209 [43021.608999] [tempesta fw] exiting... Apr 26 04:01:11 192.168.122.209 [43021.767525] [tdb] Shutdown Tempesta DB Apr 26 04:01:11 192.168.122.209 [43021.988290] End test: sessions.test_js_challenge.JSChallengeH2.test_first_request_POST Apr 26 04:01:11 192.168.122.209 [43022.008053] Start test: sessions.test_js_challenge.JSChallengeH2.test_method_override_GET_HEAD Apr 26 04:01:12 192.168.122.209 [43023.209507] [tdb] Start Tempesta DB Apr 26 04:01:13 192.168.122.209 [43023.355438] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:01:15 192.168.122.209 [43025.375580] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43025.375580] Maybe that's fine, but it's worth checking the [43025.375580] config - if there is no relations between the [43025.375580] names, then host name confusion attack is possible. Apr 26 04:01:15 192.168.122.209 [43025.532403] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:01:15 192.168.122.209 [43025.562666] [tempesta fw] Configuration processing is completed. Apr 26 04:01:15 192.168.122.209 [43025.613793] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:01:15 192.168.122.209 [43026.021702] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:01:15 192.168.122.209 [43026.047587] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:01:15 192.168.122.209 [43026.073597] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:01:15 192.168.122.209 [43026.122366] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:01:15 192.168.122.209 [43026.124123] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:01:15 192.168.122.209 [43026.162315] [tempesta fw] Tempesta FW is ready Apr 26 04:01:16 192.168.122.209 [43026.721464] [tdb] Close table 'client0.tdb' Apr 26 04:01:16 192.168.122.209 [43026.920946] [tdb] Close table 'sessions0.tdb' Apr 26 04:01:19 192.168.122.209 [43030.085971] [tdb] Close table 'cache0.tdb' Apr 26 04:01:19 192.168.122.209 [43030.319675] [tdb] Close table 'filter0.tdb' Apr 26 04:01:19 192.168.122.209 [43030.320105] [tempesta fw] modules are stopped Apr 26 04:01:20 192.168.122.209 [43030.509426] [tempesta fw] exiting... Apr 26 04:01:20 192.168.122.209 [43030.668960] [tdb] Shutdown Tempesta DB Apr 26 04:01:20 192.168.122.209 [43030.905117] End test: sessions.test_js_challenge.JSChallengeH2.test_method_override_GET_HEAD Apr 26 04:01:20 192.168.122.209 [43030.925030] Start test: sessions.test_js_challenge.JSChallengeH2.test_method_override_GET_POST Apr 26 04:01:21 192.168.122.209 [43032.045766] [tdb] Start Tempesta DB Apr 26 04:01:21 192.168.122.209 [43032.197967] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:01:23 192.168.122.209 [43034.255761] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43034.255761] Maybe that's fine, but it's worth checking the [43034.255761] config - if there is no relations between the [43034.255761] names, then host name confusion attack is possible. Apr 26 04:01:24 192.168.122.209 [43034.413068] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:01:24 192.168.122.209 [43034.462479] [tempesta fw] Configuration processing is completed. Apr 26 04:01:24 192.168.122.209 [43034.512569] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:01:24 192.168.122.209 [43034.919115] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:01:24 192.168.122.209 [43034.953036] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:01:24 192.168.122.209 [43035.008804] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:01:24 192.168.122.209 [43035.090461] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:01:24 192.168.122.209 [43035.092227] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:01:24 192.168.122.209 [43035.130416] [tempesta fw] Tempesta FW is ready Apr 26 04:01:24 192.168.122.209 [43035.260063] [tempesta fw] Warning: request dropped: unsafe method override: 127.0.0.2 Apr 26 04:01:25 192.168.122.209 [43035.679773] [tdb] Close table 'client0.tdb' Apr 26 04:01:25 192.168.122.209 [43035.858356] [tdb] Close table 'sessions0.tdb' Apr 26 04:01:28 192.168.122.209 [43038.960938] [tdb] Close table 'cache0.tdb' Apr 26 04:01:28 192.168.122.209 [43039.183706] [tdb] Close table 'filter0.tdb' Apr 26 04:01:28 192.168.122.209 [43039.184138] [tempesta fw] modules are stopped Apr 26 04:01:29 192.168.122.209 [43039.378927] [tempesta fw] exiting... Apr 26 04:01:29 192.168.122.209 [43039.526030] [tdb] Shutdown Tempesta DB Apr 26 04:01:29 192.168.122.209 [43039.761346] End test: sessions.test_js_challenge.JSChallengeH2.test_method_override_GET_POST Apr 26 04:01:29 192.168.122.209 [43039.772384] Start test: sessions.test_js_challenge.JSChallengeH2.test_method_override_HEAD_POST Apr 26 04:01:30 192.168.122.209 [43040.886469] [tdb] Start Tempesta DB Apr 26 04:01:30 192.168.122.209 [43041.036936] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:01:32 192.168.122.209 [43043.092386] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43043.092386] Maybe that's fine, but it's worth checking the [43043.092386] config - if there is no relations between the [43043.092386] names, then host name confusion attack is possible. Apr 26 04:01:32 192.168.122.209 [43043.248616] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:01:32 192.168.122.209 [43043.290503] [tempesta fw] Configuration processing is completed. Apr 26 04:01:32 192.168.122.209 [43043.341528] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:01:33 192.168.122.209 [43043.755967] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:01:33 192.168.122.209 [43043.781784] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:01:33 192.168.122.209 [43043.807756] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:01:33 192.168.122.209 [43043.846576] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:01:33 192.168.122.209 [43043.848243] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:01:33 192.168.122.209 [43043.886525] [tempesta fw] Tempesta FW is ready Apr 26 04:01:33 192.168.122.209 [43044.040800] [tempesta fw] Warning: request dropped: unsafe method override: 127.0.0.2 Apr 26 04:01:34 192.168.122.209 [43044.502864] [tdb] Close table 'client0.tdb' Apr 26 04:01:34 192.168.122.209 [43044.689347] [tdb] Close table 'sessions0.tdb' Apr 26 04:01:37 192.168.122.209 [43047.801456] [tdb] Close table 'cache0.tdb' Apr 26 04:01:37 192.168.122.209 [43048.040447] [tdb] Close table 'filter0.tdb' Apr 26 04:01:37 192.168.122.209 [43048.040885] [tempesta fw] modules are stopped Apr 26 04:01:37 192.168.122.209 [43048.242733] [tempesta fw] exiting... Apr 26 04:01:38 192.168.122.209 [43048.373882] [tdb] Shutdown Tempesta DB Apr 26 04:01:38 192.168.122.209 [43048.602169] End test: sessions.test_js_challenge.JSChallengeH2.test_method_override_HEAD_POST Apr 26 04:01:38 192.168.122.209 [43048.614922] Start test: sessions.test_js_challenge.JSChallengeH2.test_method_override_POST_GET Apr 26 04:01:39 192.168.122.209 [43049.787050] [tdb] Start Tempesta DB Apr 26 04:01:39 192.168.122.209 [43049.942660] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:01:41 192.168.122.209 [43051.935954] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43051.935954] Maybe that's fine, but it's worth checking the [43051.935954] config - if there is no relations between the [43051.935954] names, then host name confusion attack is possible. Apr 26 04:01:41 192.168.122.209 [43052.096651] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:01:41 192.168.122.209 [43052.146716] [tempesta fw] Configuration processing is completed. Apr 26 04:01:41 192.168.122.209 [43052.198878] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:01:42 192.168.122.209 [43052.635773] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:01:42 192.168.122.209 [43052.666195] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:01:42 192.168.122.209 [43052.727751] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:01:42 192.168.122.209 [43052.766681] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:01:42 192.168.122.209 [43052.768352] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:01:42 192.168.122.209 [43052.810624] [tempesta fw] Tempesta FW is ready Apr 26 04:01:43 192.168.122.209 [43053.378054] [tdb] Close table 'client0.tdb' Apr 26 04:01:43 192.168.122.209 [43053.563282] [tdb] Close table 'sessions0.tdb' Apr 26 04:01:46 192.168.122.209 [43056.742914] [tdb] Close table 'cache0.tdb' Apr 26 04:01:46 192.168.122.209 [43057.030670] [tdb] Close table 'filter0.tdb' Apr 26 04:01:46 192.168.122.209 [43057.031135] [tempesta fw] modules are stopped Apr 26 04:01:46 192.168.122.209 [43057.325201] [tempesta fw] exiting... Apr 26 04:01:47 192.168.122.209 [43057.496306] [tdb] Shutdown Tempesta DB Apr 26 04:01:47 192.168.122.209 [43057.702147] End test: sessions.test_js_challenge.JSChallengeH2.test_method_override_POST_GET Apr 26 04:01:47 192.168.122.209 [43057.716146] Start test: sessions.test_js_challenge.JSChallengeH2.test_method_override_POST_HEAD Apr 26 04:01:48 192.168.122.209 [43058.898704] [tdb] Start Tempesta DB Apr 26 04:01:48 192.168.122.209 [43059.047074] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:01:50 192.168.122.209 [43061.132083] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43061.132083] Maybe that's fine, but it's worth checking the [43061.132083] config - if there is no relations between the [43061.132083] names, then host name confusion attack is possible. Apr 26 04:01:50 192.168.122.209 [43061.284845] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:01:50 192.168.122.209 [43061.330809] [tempesta fw] Configuration processing is completed. Apr 26 04:01:51 192.168.122.209 [43061.381416] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:01:51 192.168.122.209 [43061.804158] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:01:51 192.168.122.209 [43061.831162] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:01:51 192.168.122.209 [43061.858410] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:01:51 192.168.122.209 [43061.914842] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:01:51 192.168.122.209 [43061.916560] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:01:51 192.168.122.209 [43061.950759] [tempesta fw] Tempesta FW is ready Apr 26 04:01:52 192.168.122.209 [43062.537602] [tdb] Close table 'client0.tdb' Apr 26 04:01:52 192.168.122.209 [43062.733203] [tdb] Close table 'sessions0.tdb' Apr 26 04:01:55 192.168.122.209 [43065.929638] [tdb] Close table 'cache0.tdb' Apr 26 04:01:55 192.168.122.209 [43066.187753] [tdb] Close table 'filter0.tdb' Apr 26 04:01:55 192.168.122.209 [43066.188316] [tempesta fw] modules are stopped Apr 26 04:01:56 192.168.122.209 [43066.375629] [tempesta fw] exiting... Apr 26 04:01:56 192.168.122.209 [43066.537930] [tdb] Shutdown Tempesta DB Apr 26 04:01:56 192.168.122.209 [43066.740026] End test: sessions.test_js_challenge.JSChallengeH2.test_method_override_POST_HEAD Apr 26 04:01:56 192.168.122.209 [43066.748757] Start test: sessions.test_js_challenge.JSChallengeH2.test_method_override_with_cache_GET_HEAD Apr 26 04:01:57 192.168.122.209 [43067.905413] [tdb] Start Tempesta DB Apr 26 04:01:57 192.168.122.209 [43068.058771] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:01:59 192.168.122.209 [43070.084187] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43070.084187] Maybe that's fine, but it's worth checking the [43070.084187] config - if there is no relations between the [43070.084187] names, then host name confusion attack is possible. Apr 26 04:01:59 192.168.122.209 [43070.240979] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:01:59 192.168.122.209 [43070.294964] [tempesta fw] Configuration processing is completed. Apr 26 04:02:00 192.168.122.209 [43070.349871] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:02:00 192.168.122.209 [43070.760518] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:02:00 192.168.122.209 [43070.786104] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:02:00 192.168.122.209 [43070.842452] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:02:00 192.168.122.209 [43070.894931] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:02:00 192.168.122.209 [43070.896597] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:02:00 192.168.122.209 [43070.934866] [tempesta fw] Tempesta FW is ready Apr 26 04:02:03 192.168.122.209 [43073.619346] [tdb] Close table 'client0.tdb' Apr 26 04:02:03 192.168.122.209 [43073.807389] [tdb] Close table 'sessions0.tdb' Apr 26 04:02:06 192.168.122.209 [43076.946104] [tdb] Close table 'cache0.tdb' Apr 26 04:02:06 192.168.122.209 [43077.189800] [tdb] Close table 'filter0.tdb' Apr 26 04:02:06 192.168.122.209 [43077.190244] [tempesta fw] modules are stopped Apr 26 04:02:07 192.168.122.209 [43077.416538] [tempesta fw] exiting... Apr 26 04:02:07 192.168.122.209 [43077.567770] [tdb] Shutdown Tempesta DB Apr 26 04:02:07 192.168.122.209 [43077.773251] End test: sessions.test_js_challenge.JSChallengeH2.test_method_override_with_cache_GET_HEAD Apr 26 04:02:07 192.168.122.209 [43077.792529] Start test: sessions.test_js_challenge.JSChallengeH2.test_method_override_with_cache_GET_POST Apr 26 04:02:08 192.168.122.209 [43078.895981] [tdb] Start Tempesta DB Apr 26 04:02:08 192.168.122.209 [43079.051650] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:02:10 192.168.122.209 [43081.052403] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43081.052403] Maybe that's fine, but it's worth checking the [43081.052403] config - if there is no relations between the [43081.052403] names, then host name confusion attack is possible. Apr 26 04:02:10 192.168.122.209 [43081.245625] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:02:10 192.168.122.209 [43081.287106] [tempesta fw] Configuration processing is completed. Apr 26 04:02:11 192.168.122.209 [43081.351512] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:02:11 192.168.122.209 [43081.759224] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:02:11 192.168.122.209 [43081.790940] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:02:11 192.168.122.209 [43081.847255] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:02:11 192.168.122.209 [43081.903083] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:02:11 192.168.122.209 [43081.904756] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:02:11 192.168.122.209 [43081.943015] [tempesta fw] Tempesta FW is ready Apr 26 04:02:13 192.168.122.209 [43083.955981] [tempesta fw] Warning: request dropped: unsafe method override: 127.0.0.2 Apr 26 04:02:14 192.168.122.209 [43084.382776] [tdb] Close table 'client0.tdb' Apr 26 04:02:14 192.168.122.209 [43084.568272] [tdb] Close table 'sessions0.tdb' Apr 26 04:02:17 192.168.122.209 [43087.740821] [tdb] Close table 'cache0.tdb' Apr 26 04:02:17 192.168.122.209 [43087.964680] [tdb] Close table 'filter0.tdb' Apr 26 04:02:17 192.168.122.209 [43087.965131] [tempesta fw] modules are stopped Apr 26 04:02:17 192.168.122.209 [43088.174779] [tempesta fw] exiting... Apr 26 04:02:17 192.168.122.209 [43088.331083] [tdb] Shutdown Tempesta DB Apr 26 04:02:18 192.168.122.209 [43088.549237] End test: sessions.test_js_challenge.JSChallengeH2.test_method_override_with_cache_GET_POST Apr 26 04:02:18 192.168.122.209 [43088.571237] Start test: sessions.test_js_challenge.JSChallengeH2.test_method_override_with_cache_HEAD_GET Apr 26 04:02:19 192.168.122.209 [43089.742622] [tdb] Start Tempesta DB Apr 26 04:02:19 192.168.122.209 [43089.900650] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:02:21 192.168.122.209 [43091.964423] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43091.964423] Maybe that's fine, but it's worth checking the [43091.964423] config - if there is no relations between the [43091.964423] names, then host name confusion attack is possible. Apr 26 04:02:21 192.168.122.209 [43092.165224] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:02:21 192.168.122.209 [43092.199494] [tempesta fw] Configuration processing is completed. Apr 26 04:02:21 192.168.122.209 [43092.250528] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:02:22 192.168.122.209 [43092.661590] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:02:22 192.168.122.209 [43092.687387] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:02:22 192.168.122.209 [43092.713113] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:02:22 192.168.122.209 [43092.767184] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:02:22 192.168.122.209 [43092.768872] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:02:22 192.168.122.209 [43092.807143] [tempesta fw] Tempesta FW is ready Apr 26 04:02:24 192.168.122.209 [43094.938790] [tdb] Close table 'client0.tdb' Apr 26 04:02:24 192.168.122.209 [43095.129017] [tdb] Close table 'sessions0.tdb' Apr 26 04:02:27 192.168.122.209 [43098.240893] [tdb] Close table 'cache0.tdb' Apr 26 04:02:28 192.168.122.209 [43098.491846] [tdb] Close table 'filter0.tdb' Apr 26 04:02:28 192.168.122.209 [43098.492307] [tempesta fw] modules are stopped Apr 26 04:02:28 192.168.122.209 [43098.677672] [tempesta fw] exiting... Apr 26 04:02:28 192.168.122.209 [43098.811728] [tdb] Shutdown Tempesta DB Apr 26 04:02:28 192.168.122.209 [43099.036793] End test: sessions.test_js_challenge.JSChallengeH2.test_method_override_with_cache_HEAD_GET Apr 26 04:02:28 192.168.122.209 [43099.063411] Start test: sessions.test_js_challenge.JSChallengeH2.test_method_override_with_cache_HEAD_POST Apr 26 04:02:29 192.168.122.209 [43100.198425] [tdb] Start Tempesta DB Apr 26 04:02:29 192.168.122.209 [43100.338925] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:02:32 192.168.122.209 [43102.376710] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43102.376710] Maybe that's fine, but it's worth checking the [43102.376710] config - if there is no relations between the [43102.376710] names, then host name confusion attack is possible. Apr 26 04:02:32 192.168.122.209 [43102.556913] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:02:32 192.168.122.209 [43102.595550] [tempesta fw] Configuration processing is completed. Apr 26 04:02:32 192.168.122.209 [43102.646794] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:02:32 192.168.122.209 [43103.052643] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:02:32 192.168.122.209 [43103.078610] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:02:32 192.168.122.209 [43103.134954] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:02:32 192.168.122.209 [43103.183275] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:02:32 192.168.122.209 [43103.184404] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:02:32 192.168.122.209 [43103.223267] [tempesta fw] Tempesta FW is ready Apr 26 04:02:34 192.168.122.209 [43104.575128] [tempesta fw] Warning: request dropped: unsafe method override: 127.0.0.2 Apr 26 04:02:34 192.168.122.209 [43104.988958] [tdb] Close table 'client0.tdb' Apr 26 04:02:34 192.168.122.209 [43105.186682] [tdb] Close table 'sessions0.tdb' Apr 26 04:02:38 192.168.122.209 [43108.384810] [tdb] Close table 'cache0.tdb' Apr 26 04:02:38 192.168.122.209 [43108.624994] [tdb] Close table 'filter0.tdb' Apr 26 04:02:38 192.168.122.209 [43108.625431] [tempesta fw] modules are stopped Apr 26 04:02:38 192.168.122.209 [43108.813703] [tempesta fw] exiting... Apr 26 04:02:38 192.168.122.209 [43108.979251] [tdb] Shutdown Tempesta DB Apr 26 04:02:38 192.168.122.209 [43109.212214] End test: sessions.test_js_challenge.JSChallengeH2.test_method_override_with_cache_HEAD_POST Apr 26 04:02:38 192.168.122.209 [43109.233790] Start test: sessions.test_js_challenge.JSChallengeH2.test_method_override_with_cache_POST_GET Apr 26 04:02:40 192.168.122.209 [43110.400563] [tdb] Start Tempesta DB Apr 26 04:02:40 192.168.122.209 [43110.548949] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:02:42 192.168.122.209 [43112.616734] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43112.616734] Maybe that's fine, but it's worth checking the [43112.616734] config - if there is no relations between the [43112.616734] names, then host name confusion attack is possible. Apr 26 04:02:42 192.168.122.209 [43112.773558] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:02:42 192.168.122.209 [43112.807799] [tempesta fw] Configuration processing is completed. Apr 26 04:02:42 192.168.122.209 [43112.858040] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:02:42 192.168.122.209 [43113.267281] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:02:42 192.168.122.209 [43113.293039] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:02:42 192.168.122.209 [43113.318968] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:02:43 192.168.122.209 [43113.391450] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:02:43 192.168.122.209 [43113.393244] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:02:43 192.168.122.209 [43113.439409] [tempesta fw] Tempesta FW is ready Apr 26 04:02:45 192.168.122.209 [43116.275469] [tdb] Close table 'client0.tdb' Apr 26 04:02:46 192.168.122.209 [43116.460565] [tdb] Close table 'sessions0.tdb' Apr 26 04:02:49 192.168.122.209 [43119.592629] [tdb] Close table 'cache0.tdb' Apr 26 04:02:49 192.168.122.209 [43119.829134] [tdb] Close table 'filter0.tdb' Apr 26 04:02:49 192.168.122.209 [43119.829579] [tempesta fw] modules are stopped Apr 26 04:02:49 192.168.122.209 [43120.069144] [tempesta fw] exiting... Apr 26 04:02:49 192.168.122.209 [43120.228009] [tdb] Shutdown Tempesta DB Apr 26 04:02:50 192.168.122.209 [43120.425301] End test: sessions.test_js_challenge.JSChallengeH2.test_method_override_with_cache_POST_GET Apr 26 04:02:50 192.168.122.209 [43120.446717] Start test: sessions.test_js_challenge.JSChallengeH2.test_method_override_with_cache_POST_HEAD Apr 26 04:02:51 192.168.122.209 [43121.638613] [tdb] Start Tempesta DB Apr 26 04:02:51 192.168.122.209 [43121.793337] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:02:53 192.168.122.209 [43123.888838] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43123.888838] Maybe that's fine, but it's worth checking the [43123.888838] config - if there is no relations between the [43123.888838] names, then host name confusion attack is possible. Apr 26 04:02:53 192.168.122.209 [43124.053616] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:02:53 192.168.122.209 [43124.091618] [tempesta fw] Configuration processing is completed. Apr 26 04:02:53 192.168.122.209 [43124.144682] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:02:54 192.168.122.209 [43124.562280] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:02:54 192.168.122.209 [43124.590745] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:02:54 192.168.122.209 [43124.616937] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:02:54 192.168.122.209 [43124.667521] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:02:54 192.168.122.209 [43124.669185] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:02:54 192.168.122.209 [43124.711541] [tempesta fw] Tempesta FW is ready Apr 26 04:02:56 192.168.122.209 [43127.320132] [tdb] Close table 'client0.tdb' Apr 26 04:02:57 192.168.122.209 [43127.514855] [tdb] Close table 'sessions0.tdb' Apr 26 04:03:00 192.168.122.209 [43130.655324] [tdb] Close table 'cache0.tdb' Apr 26 04:03:00 192.168.122.209 [43130.902177] [tdb] Close table 'filter0.tdb' Apr 26 04:03:00 192.168.122.209 [43130.902578] [tempesta fw] modules are stopped Apr 26 04:03:00 192.168.122.209 [43131.115797] [tempesta fw] exiting... Apr 26 04:03:00 192.168.122.209 [43131.276221] [tdb] Shutdown Tempesta DB Apr 26 04:03:01 192.168.122.209 [43131.470264] End test: sessions.test_js_challenge.JSChallengeH2.test_method_override_with_cache_POST_HEAD Apr 26 04:03:01 192.168.122.209 [43131.499084] Start test: sessions.test_js_challenge.JSChallengeH2.test_new_client_session_with_exist_cookie Apr 26 04:03:02 192.168.122.209 [43132.688729] [tdb] Start Tempesta DB Apr 26 04:03:02 192.168.122.209 [43132.839385] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:03:04 192.168.122.209 [43134.901021] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43134.901021] Maybe that's fine, but it's worth checking the [43134.901021] config - if there is no relations between the [43134.901021] names, then host name confusion attack is possible. Apr 26 04:03:04 192.168.122.209 [43135.061798] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:03:04 192.168.122.209 [43135.100076] [tempesta fw] Configuration processing is completed. Apr 26 04:03:04 192.168.122.209 [43135.151153] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:03:05 192.168.122.209 [43135.564905] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:03:05 192.168.122.209 [43135.590987] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:03:05 192.168.122.209 [43135.616641] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:03:05 192.168.122.209 [43135.679730] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:03:05 192.168.122.209 [43135.681425] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:03:05 192.168.122.209 [43135.727680] [tempesta fw] Tempesta FW is ready Apr 26 04:03:07 192.168.122.209 [43138.143405] [tdb] Close table 'client0.tdb' Apr 26 04:03:07 192.168.122.209 [43138.328871] [tdb] Close table 'sessions0.tdb' Apr 26 04:03:11 192.168.122.209 [43141.477839] [tdb] Close table 'cache0.tdb' Apr 26 04:03:11 192.168.122.209 [43141.721940] [tdb] Close table 'filter0.tdb' Apr 26 04:03:11 192.168.122.209 [43141.722405] [tempesta fw] modules are stopped Apr 26 04:03:11 192.168.122.209 [43141.929181] [tempesta fw] exiting... Apr 26 04:03:11 192.168.122.209 [43142.103719] [tdb] Shutdown Tempesta DB Apr 26 04:03:11 192.168.122.209 [43142.322003] End test: sessions.test_js_challenge.JSChallengeH2.test_new_client_session_with_exist_cookie Apr 26 04:03:11 192.168.122.209 [43142.333414] Start test: sessions.test_js_challenge.JSChallengeH2.test_not_block_after_tempesta_restart Apr 26 04:03:13 192.168.122.209 [43143.468792] [tdb] Start Tempesta DB Apr 26 04:03:13 192.168.122.209 [43143.626457] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:03:15 192.168.122.209 [43145.613218] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43145.613218] Maybe that's fine, but it's worth checking the [43145.613218] config - if there is no relations between the [43145.613218] names, then host name confusion attack is possible. Apr 26 04:03:15 192.168.122.209 [43145.793920] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:03:15 192.168.122.209 [43145.839885] [tempesta fw] Configuration processing is completed. Apr 26 04:03:15 192.168.122.209 [43145.891234] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:03:15 192.168.122.209 [43146.311838] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:03:15 192.168.122.209 [43146.338198] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:03:16 192.168.122.209 [43146.364936] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:03:16 192.168.122.209 [43146.411868] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:03:16 192.168.122.209 [43146.413554] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:03:16 192.168.122.209 [43146.451822] [tempesta fw] Tempesta FW is ready Apr 26 04:03:18 192.168.122.209 [43148.498332] [tdb] Close table 'client0.tdb' Apr 26 04:03:18 192.168.122.209 [43148.686906] [tdb] Close table 'sessions0.tdb' Apr 26 04:03:21 192.168.122.209 [43151.823687] [tdb] Close table 'cache0.tdb' Apr 26 04:03:21 192.168.122.209 [43152.078916] [tdb] Close table 'filter0.tdb' Apr 26 04:03:21 192.168.122.209 [43152.079397] [tempesta fw] modules are stopped Apr 26 04:03:21 192.168.122.209 [43152.256439] [tempesta fw] exiting... Apr 26 04:03:22 192.168.122.209 [43152.425001] [tdb] Shutdown Tempesta DB Apr 26 04:03:23 192.168.122.209 [43153.585674] [tdb] Start Tempesta DB Apr 26 04:03:23 192.168.122.209 [43153.731221] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:03:25 192.168.122.209 [43155.649154] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43155.649154] Maybe that's fine, but it's worth checking the [43155.649154] config - if there is no relations between the [43155.649154] names, then host name confusion attack is possible. Apr 26 04:03:25 192.168.122.209 [43155.826056] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:03:25 192.168.122.209 [43155.888040] [tempesta fw] Configuration processing is completed. Apr 26 04:03:25 192.168.122.209 [43155.939759] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:03:25 192.168.122.209 [43156.348715] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:03:26 192.168.122.209 [43156.374662] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:03:26 192.168.122.209 [43156.400404] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:03:26 192.168.122.209 [43156.480163] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:03:26 192.168.122.209 [43156.481857] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:03:26 192.168.122.209 [43156.551957] [tempesta fw] Tempesta FW is ready Apr 26 04:03:26 192.168.122.209 [43156.609692] [tempesta fw] Warning: http_sess: bad received HMAC value for 127.0.0.2 f(pos=0), ts=0x100a3708d orig_hmac=[abea588ce20cf7a63b1a4e5bd591ae41fd73ae22] Apr 26 04:03:29 192.168.122.209 [43159.540149] [tdb] Close table 'client0.tdb' Apr 26 04:03:29 192.168.122.209 [43159.736996] [tdb] Close table 'sessions0.tdb' Apr 26 04:03:32 192.168.122.209 [43162.844794] [tdb] Close table 'cache0.tdb' Apr 26 04:03:32 192.168.122.209 [43163.092130] [tdb] Close table 'filter0.tdb' Apr 26 04:03:32 192.168.122.209 [43163.092563] [tempesta fw] modules are stopped Apr 26 04:03:32 192.168.122.209 [43163.320302] [tempesta fw] exiting... Apr 26 04:03:33 192.168.122.209 [43163.458567] [tdb] Shutdown Tempesta DB Apr 26 04:03:33 192.168.122.209 [43163.664255] End test: sessions.test_js_challenge.JSChallengeH2.test_not_block_after_tempesta_restart Apr 26 04:03:33 192.168.122.209 [43163.680642] Start test: sessions.test_js_challenge.JSChallengeH2.test_number_of_requests_is_greater_than_max_misses Apr 26 04:03:34 192.168.122.209 [43164.818827] [tdb] Start Tempesta DB Apr 26 04:03:34 192.168.122.209 [43164.963011] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:03:36 192.168.122.209 [43166.965418] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43166.965418] Maybe that's fine, but it's worth checking the [43166.965418] config - if there is no relations between the [43166.965418] names, then host name confusion attack is possible. Apr 26 04:03:36 192.168.122.209 [43167.122095] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:03:36 192.168.122.209 [43167.164470] [tempesta fw] Configuration processing is completed. Apr 26 04:03:36 192.168.122.209 [43167.210988] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:03:37 192.168.122.209 [43167.633864] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:03:37 192.168.122.209 [43167.671615] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:03:37 192.168.122.209 [43167.698324] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:03:37 192.168.122.209 [43167.752153] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:03:37 192.168.122.209 [43167.753883] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:03:37 192.168.122.209 [43167.812094] [tempesta fw] Tempesta FW is ready Apr 26 04:03:37 192.168.122.209 [43167.977479] [tempesta fw] Warning: frang: max rmisses exceeded for 127.0.0.2: 3 (lim=2) Apr 26 04:03:38 192.168.122.209 [43168.418445] [tdb] Close table 'client0.tdb' Apr 26 04:03:38 192.168.122.209 [43168.620594] [tdb] Close table 'sessions0.tdb' Apr 26 04:03:41 192.168.122.209 [43171.880351] [tdb] Close table 'cache0.tdb' Apr 26 04:03:41 192.168.122.209 [43172.113197] [tdb] Close table 'filter0.tdb' Apr 26 04:03:41 192.168.122.209 [43172.113644] [tempesta fw] modules are stopped Apr 26 04:03:41 192.168.122.209 [43172.320081] [tempesta fw] exiting... Apr 26 04:03:42 192.168.122.209 [43172.448700] [tdb] Shutdown Tempesta DB Apr 26 04:03:42 192.168.122.209 [43172.668630] End test: sessions.test_js_challenge.JSChallengeH2.test_number_of_requests_is_greater_than_max_misses Apr 26 04:03:42 192.168.122.209 [43172.679768] Start test: sessions.test_js_challenge.JSChallengeH2.test_resp_code_302 Apr 26 04:03:43 192.168.122.209 [43173.861223] [tdb] Start Tempesta DB Apr 26 04:03:43 192.168.122.209 [43174.011756] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:03:45 192.168.122.209 [43175.993591] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43175.993591] Maybe that's fine, but it's worth checking the [43175.993591] config - if there is no relations between the [43175.993591] names, then host name confusion attack is possible. Apr 26 04:03:45 192.168.122.209 [43176.174267] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:03:45 192.168.122.209 [43176.220259] [tempesta fw] Configuration processing is completed. Apr 26 04:03:45 192.168.122.209 [43176.270459] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:03:46 192.168.122.209 [43176.684993] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:03:46 192.168.122.209 [43176.721210] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:03:46 192.168.122.209 [43176.747120] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:03:46 192.168.122.209 [43176.804173] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:03:46 192.168.122.209 [43176.806014] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:03:46 192.168.122.209 [43176.848203] [tempesta fw] Tempesta FW is ready Apr 26 04:03:47 192.168.122.209 [43177.409170] [tdb] Close table 'client0.tdb' Apr 26 04:03:47 192.168.122.209 [43177.613887] [tdb] Close table 'sessions0.tdb' Apr 26 04:03:50 192.168.122.209 [43180.729013] [tdb] Close table 'cache0.tdb' Apr 26 04:03:50 192.168.122.209 [43180.963141] [tdb] Close table 'filter0.tdb' Apr 26 04:03:50 192.168.122.209 [43180.963575] [tempesta fw] modules are stopped Apr 26 04:03:50 192.168.122.209 [43181.163344] [tempesta fw] exiting... Apr 26 04:03:50 192.168.122.209 [43181.317533] [tdb] Shutdown Tempesta DB Apr 26 04:03:51 192.168.122.209 [43181.519682] End test: sessions.test_js_challenge.JSChallengeH2.test_resp_code_302 Apr 26 04:03:51 192.168.122.209 [43181.538694] Start test: sessions.test_js_challenge.JSChallengeH2.test_resp_code_403 Apr 26 04:03:52 192.168.122.209 [43182.754536] [tdb] Start Tempesta DB Apr 26 04:03:52 192.168.122.209 [43182.905819] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:03:54 192.168.122.209 [43184.965266] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43184.965266] Maybe that's fine, but it's worth checking the [43184.965266] config - if there is no relations between the [43184.965266] names, then host name confusion attack is possible. Apr 26 04:03:54 192.168.122.209 [43185.134399] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:03:54 192.168.122.209 [43185.176300] [tempesta fw] Configuration processing is completed. Apr 26 04:03:54 192.168.122.209 [43185.228503] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:03:55 192.168.122.209 [43185.688677] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:03:55 192.168.122.209 [43185.725972] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:03:55 192.168.122.209 [43185.752440] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:03:55 192.168.122.209 [43185.792314] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:03:55 192.168.122.209 [43185.793397] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:03:55 192.168.122.209 [43185.844267] [tempesta fw] Tempesta FW is ready Apr 26 04:03:56 192.168.122.209 [43186.441633] [tdb] Close table 'client0.tdb' Apr 26 04:03:56 192.168.122.209 [43186.637509] [tdb] Close table 'sessions0.tdb' Apr 26 04:03:59 192.168.122.209 [43189.791072] [tdb] Close table 'cache0.tdb' Apr 26 04:03:59 192.168.122.209 [43190.035441] [tdb] Close table 'filter0.tdb' Apr 26 04:03:59 192.168.122.209 [43190.035883] [tempesta fw] modules are stopped Apr 26 04:03:59 192.168.122.209 [43190.208343] [tempesta fw] exiting... Apr 26 04:03:59 192.168.122.209 [43190.337753] [tdb] Shutdown Tempesta DB Apr 26 04:04:00 192.168.122.209 [43190.553932] End test: sessions.test_js_challenge.JSChallengeH2.test_resp_code_403 Apr 26 04:04:00 192.168.122.209 [43190.563443] Start test: sessions.test_js_challenge.JSChallengeH2.test_resp_code_default Apr 26 04:04:01 192.168.122.209 [43191.733783] [tdb] Start Tempesta DB Apr 26 04:04:01 192.168.122.209 [43191.880436] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:04:03 192.168.122.209 [43193.961719] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43193.961719] Maybe that's fine, but it's worth checking the [43193.961719] config - if there is no relations between the [43193.961719] names, then host name confusion attack is possible. Apr 26 04:04:03 192.168.122.209 [43194.126359] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:04:03 192.168.122.209 [43194.156795] [tempesta fw] Configuration processing is completed. Apr 26 04:04:03 192.168.122.209 [43194.210340] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:04:04 192.168.122.209 [43194.613188] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:04:04 192.168.122.209 [43194.638962] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:04:04 192.168.122.209 [43194.695470] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:04:04 192.168.122.209 [43194.740370] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:04:04 192.168.122.209 [43194.741402] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:04:04 192.168.122.209 [43194.780458] [tempesta fw] Tempesta FW is ready Apr 26 04:04:05 192.168.122.209 [43195.369407] [tdb] Close table 'client0.tdb' Apr 26 04:04:05 192.168.122.209 [43195.586206] [tdb] Close table 'sessions0.tdb' Apr 26 04:04:08 192.168.122.209 [43198.774921] [tdb] Close table 'cache0.tdb' Apr 26 04:04:08 192.168.122.209 [43199.014439] [tdb] Close table 'filter0.tdb' Apr 26 04:04:08 192.168.122.209 [43199.014881] [tempesta fw] modules are stopped Apr 26 04:04:08 192.168.122.209 [43199.209003] [tempesta fw] exiting... Apr 26 04:04:09 192.168.122.209 [43199.386641] [tdb] Shutdown Tempesta DB Apr 26 04:04:09 192.168.122.209 [43199.620244] End test: sessions.test_js_challenge.JSChallengeH2.test_resp_code_default Apr 26 04:04:09 192.168.122.209 [43199.630138] Start test: sessions.test_js_challenge.JSChallengeH2.test_restart_js_challenge Apr 26 04:04:10 192.168.122.209 [43200.820960] [tdb] Start Tempesta DB Apr 26 04:04:10 192.168.122.209 [43200.974497] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:04:12 192.168.122.209 [43203.073478] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43203.073478] Maybe that's fine, but it's worth checking the [43203.073478] config - if there is no relations between the [43203.073478] names, then host name confusion attack is possible. Apr 26 04:04:12 192.168.122.209 [43203.246650] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:04:12 192.168.122.209 [43203.276915] [tempesta fw] Configuration processing is completed. Apr 26 04:04:12 192.168.122.209 [43203.327450] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:04:13 192.168.122.209 [43203.764603] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:04:13 192.168.122.209 [43203.791029] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:04:13 192.168.122.209 [43203.852888] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:04:13 192.168.122.209 [43203.888606] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:04:13 192.168.122.209 [43203.890284] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:04:13 192.168.122.209 [43203.936547] [tempesta fw] Tempesta FW is ready Apr 26 04:04:13 192.168.122.209 [43204.086467] [tempesta fw] Warning: http_sess: bad received HMAC value for 127.0.0.2 f(pos=0), ts=0x100116a72 orig_hmac=[22bd3751bcc55b4212ecd27e46c964e327239b66] Apr 26 04:04:16 192.168.122.209 [43206.877110] [tdb] Close table 'client0.tdb' Apr 26 04:04:16 192.168.122.209 [43207.061665] [tdb] Close table 'sessions0.tdb' Apr 26 04:04:19 192.168.122.209 [43210.177851] [tdb] Close table 'cache0.tdb' Apr 26 04:04:20 192.168.122.209 [43210.424939] [tdb] Close table 'filter0.tdb' Apr 26 04:04:20 192.168.122.209 [43210.425376] [tempesta fw] modules are stopped Apr 26 04:04:20 192.168.122.209 [43210.605726] [tempesta fw] exiting... Apr 26 04:04:20 192.168.122.209 [43210.744835] [tdb] Shutdown Tempesta DB Apr 26 04:04:20 192.168.122.209 [43210.943761] End test: sessions.test_js_challenge.JSChallengeH2.test_restart_js_challenge Apr 26 04:04:20 192.168.122.209 [43210.954711] Start test: sessions.test_js_challenge.JSChallengeH2.test_second_request_GET_and_accept_all Apr 26 04:04:21 192.168.122.209 [43212.131911] [tdb] Start Tempesta DB Apr 26 04:04:21 192.168.122.209 [43212.301520] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:04:23 192.168.122.209 [43214.325990] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43214.325990] Maybe that's fine, but it's worth checking the [43214.325990] config - if there is no relations between the [43214.325990] names, then host name confusion attack is possible. Apr 26 04:04:24 192.168.122.209 [43214.494709] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:04:24 192.168.122.209 [43214.540733] [tempesta fw] Configuration processing is completed. Apr 26 04:04:24 192.168.122.209 [43214.591710] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:04:24 192.168.122.209 [43215.001818] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:04:24 192.168.122.209 [43215.027569] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:04:24 192.168.122.209 [43215.062714] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:04:24 192.168.122.209 [43215.112780] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:04:24 192.168.122.209 [43215.114158] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:04:24 192.168.122.209 [43215.156677] [tempesta fw] Tempesta FW is ready Apr 26 04:04:27 192.168.122.209 [43217.870923] [tdb] Close table 'client0.tdb' Apr 26 04:04:27 192.168.122.209 [43218.086108] [tdb] Close table 'sessions0.tdb' Apr 26 04:04:31 192.168.122.209 [43221.485253] [tdb] Close table 'cache0.tdb' Apr 26 04:04:31 192.168.122.209 [43221.757773] [tdb] Close table 'filter0.tdb' Apr 26 04:04:31 192.168.122.209 [43221.758226] [tempesta fw] modules are stopped Apr 26 04:04:31 192.168.122.209 [43221.954976] [tempesta fw] exiting... Apr 26 04:04:31 192.168.122.209 [43222.099013] [tdb] Shutdown Tempesta DB Apr 26 04:04:31 192.168.122.209 [43222.298426] End test: sessions.test_js_challenge.JSChallengeH2.test_second_request_GET_and_accept_all Apr 26 04:04:31 192.168.122.209 [43222.312179] Start test: sessions.test_js_challenge.JSChallengeH2.test_second_request_POST Apr 26 04:04:33 192.168.122.209 [43223.531227] [tdb] Start Tempesta DB Apr 26 04:04:33 192.168.122.209 [43223.727572] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:04:35 192.168.122.209 [43225.842821] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43225.842821] Maybe that's fine, but it's worth checking the [43225.842821] config - if there is no relations between the [43225.842821] names, then host name confusion attack is possible. Apr 26 04:04:35 192.168.122.209 [43226.003066] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:04:35 192.168.122.209 [43226.044982] [tempesta fw] Configuration processing is completed. Apr 26 04:04:35 192.168.122.209 [43226.107935] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:04:36 192.168.122.209 [43226.599617] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:04:36 192.168.122.209 [43226.629631] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:04:36 192.168.122.209 [43226.656587] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:04:36 192.168.122.209 [43226.708936] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:04:36 192.168.122.209 [43226.710649] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:04:36 192.168.122.209 [43226.748838] [tempesta fw] Tempesta FW is ready Apr 26 04:04:39 192.168.122.209 [43230.139284] [tdb] Close table 'client0.tdb' Apr 26 04:04:40 192.168.122.209 [43230.421096] [tdb] Close table 'sessions0.tdb' Apr 26 04:04:44 192.168.122.209 [43234.884650] [tdb] Close table 'cache0.tdb' Apr 26 04:04:44 192.168.122.209 [43235.169974] [tdb] Close table 'filter0.tdb' Apr 26 04:04:44 192.168.122.209 [43235.170450] [tempesta fw] modules are stopped Apr 26 04:04:45 192.168.122.209 [43235.367381] [tempesta fw] exiting... Apr 26 04:04:45 192.168.122.209 [43235.524914] [tdb] Shutdown Tempesta DB Apr 26 04:04:45 192.168.122.209 [43235.743902] End test: sessions.test_js_challenge.JSChallengeH2.test_second_request_POST Apr 26 04:04:45 192.168.122.209 [43235.759102] Start test: sessions.test_js_challenge.JSChallengeH2.test_servicing_non_challengeble_request_from_cache_GET Apr 26 04:04:46 192.168.122.209 [43236.924377] [tdb] Start Tempesta DB Apr 26 04:04:46 192.168.122.209 [43237.087217] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:04:48 192.168.122.209 [43239.138406] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43239.138406] Maybe that's fine, but it's worth checking the [43239.138406] config - if there is no relations between the [43239.138406] names, then host name confusion attack is possible. Apr 26 04:04:48 192.168.122.209 [43239.295194] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:04:48 192.168.122.209 [43239.333113] [tempesta fw] Configuration processing is completed. Apr 26 04:04:49 192.168.122.209 [43239.384672] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:04:49 192.168.122.209 [43239.798804] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:04:49 192.168.122.209 [43239.825615] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:04:49 192.168.122.209 [43239.852990] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:04:49 192.168.122.209 [43239.905072] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:04:49 192.168.122.209 [43239.906848] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:04:49 192.168.122.209 [43239.961003] [tempesta fw] Tempesta FW is ready Apr 26 04:04:52 192.168.122.209 [43242.927889] [tdb] Close table 'client0.tdb' Apr 26 04:04:52 192.168.122.209 [43243.110949] [tdb] Close table 'sessions0.tdb' Apr 26 04:04:55 192.168.122.209 [43246.256045] [tdb] Close table 'cache0.tdb' Apr 26 04:04:56 192.168.122.209 [43246.513655] [tdb] Close table 'filter0.tdb' Apr 26 04:04:56 192.168.122.209 [43246.514114] [tempesta fw] modules are stopped Apr 26 04:04:56 192.168.122.209 [43246.706496] [tempesta fw] exiting... Apr 26 04:04:56 192.168.122.209 [43246.888558] [tdb] Shutdown Tempesta DB Apr 26 04:04:56 192.168.122.209 [43247.096838] End test: sessions.test_js_challenge.JSChallengeH2.test_servicing_non_challengeble_request_from_cache_GET Apr 26 04:04:56 192.168.122.209 [43247.111492] Start test: sessions.test_js_challenge.JSChallengeH2.test_servicing_non_challengeble_request_from_cache_HEAD Apr 26 04:04:57 192.168.122.209 [43248.276656] [tdb] Start Tempesta DB Apr 26 04:04:58 192.168.122.209 [43248.434548] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:05:00 192.168.122.209 [43250.506461] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43250.506461] Maybe that's fine, but it's worth checking the [43250.506461] config - if there is no relations between the [43250.506461] names, then host name confusion attack is possible. Apr 26 04:05:00 192.168.122.209 [43250.671224] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:05:00 192.168.122.209 [43250.713216] [tempesta fw] Configuration processing is completed. Apr 26 04:05:00 192.168.122.209 [43250.762830] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:05:00 192.168.122.209 [43251.168950] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:05:00 192.168.122.209 [43251.194449] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:05:00 192.168.122.209 [43251.258899] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:05:00 192.168.122.209 [43251.301202] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:05:00 192.168.122.209 [43251.302932] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:05:00 192.168.122.209 [43251.341148] [tempesta fw] Tempesta FW is ready Apr 26 04:05:03 192.168.122.209 [43254.145829] [tdb] Close table 'client0.tdb' Apr 26 04:05:03 192.168.122.209 [43254.336321] [tdb] Close table 'sessions0.tdb' Apr 26 04:05:07 192.168.122.209 [43257.488805] [tdb] Close table 'cache0.tdb' Apr 26 04:05:07 192.168.122.209 [43257.728363] [tdb] Close table 'filter0.tdb' Apr 26 04:05:07 192.168.122.209 [43257.728792] [tempesta fw] modules are stopped Apr 26 04:05:07 192.168.122.209 [43257.914188] [tempesta fw] exiting... Apr 26 04:05:07 192.168.122.209 [43258.077465] [tdb] Shutdown Tempesta DB Apr 26 04:05:07 192.168.122.209 [43258.292374] End test: sessions.test_js_challenge.JSChallengeH2.test_servicing_non_challengeble_request_from_cache_HEAD Apr 26 04:05:07 192.168.122.209 [43258.306556] Start test: sessions.test_js_challenge.JSChallengeH2.test_servicing_non_challengeble_request_from_cache_POST Apr 26 04:05:09 192.168.122.209 [43259.459072] [tdb] Start Tempesta DB Apr 26 04:05:09 192.168.122.209 [43259.602821] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:05:11 192.168.122.209 [43261.650690] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43261.650690] Maybe that's fine, but it's worth checking the [43261.650690] config - if there is no relations between the [43261.650690] names, then host name confusion attack is possible. Apr 26 04:05:11 192.168.122.209 [43261.831385] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:05:11 192.168.122.209 [43261.861769] [tempesta fw] Configuration processing is completed. Apr 26 04:05:11 192.168.122.209 [43261.940801] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:05:12 192.168.122.209 [43262.357984] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:05:12 192.168.122.209 [43262.383999] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:05:12 192.168.122.209 [43262.409987] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:05:12 192.168.122.209 [43262.465363] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:05:12 192.168.122.209 [43262.467093] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:05:12 192.168.122.209 [43262.513311] [tempesta fw] Tempesta FW is ready Apr 26 04:05:14 192.168.122.209 [43265.136123] [tdb] Close table 'client0.tdb' Apr 26 04:05:14 192.168.122.209 [43265.334067] [tdb] Close table 'sessions0.tdb' Apr 26 04:05:18 192.168.122.209 [43268.482580] [tdb] Close table 'cache0.tdb' Apr 26 04:05:18 192.168.122.209 [43268.711421] [tdb] Close table 'filter0.tdb' Apr 26 04:05:18 192.168.122.209 [43268.711861] [tempesta fw] modules are stopped Apr 26 04:05:18 192.168.122.209 [43268.926689] [tempesta fw] exiting... Apr 26 04:05:18 192.168.122.209 [43269.057488] [tdb] Shutdown Tempesta DB Apr 26 04:05:18 192.168.122.209 [43269.260811] End test: sessions.test_js_challenge.JSChallengeH2.test_servicing_non_challengeble_request_from_cache_POST Apr 26 04:05:18 192.168.122.209 [43269.320214] Start test: sessions.test_js_challenge.JSChallengeHttp.test_cookies_in_request_multiple_in_one Apr 26 04:05:20 192.168.122.209 [43270.438054] [tdb] Start Tempesta DB Apr 26 04:05:20 192.168.122.209 [43270.585493] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:05:22 192.168.122.209 [43272.606771] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43272.606771] Maybe that's fine, but it's worth checking the [43272.606771] config - if there is no relations between the [43272.606771] names, then host name confusion attack is possible. Apr 26 04:05:22 192.168.122.209 [43272.775525] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:05:22 192.168.122.209 [43272.821489] [tempesta fw] Configuration processing is completed. Apr 26 04:05:22 192.168.122.209 [43272.877456] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:05:22 192.168.122.209 [43273.300032] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:05:22 192.168.122.209 [43273.328661] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:05:23 192.168.122.209 [43273.355322] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:05:23 192.168.122.209 [43273.405498] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:05:23 192.168.122.209 [43273.407213] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:05:23 192.168.122.209 [43273.461446] [tempesta fw] Tempesta FW is ready Apr 26 04:05:27 192.168.122.209 [43277.544715] [tempesta fw] Warning: Multiple Tempesta sticky cookies found in request: 2 Apr 26 04:05:27 192.168.122.209 [43277.546956] [tempesta fw] Warning: request dropped: internal error in Sticky module: 127.0.0.2 Apr 26 04:05:27 192.168.122.209 [43278.000860] [tdb] Close table 'client0.tdb' Apr 26 04:05:27 192.168.122.209 [43278.190900] [tdb] Close table 'sessions0.tdb' Apr 26 04:05:31 192.168.122.209 [43281.353907] [tdb] Close table 'cache0.tdb' Apr 26 04:05:31 192.168.122.209 [43281.602385] [tdb] Close table 'filter0.tdb' Apr 26 04:05:31 192.168.122.209 [43281.602812] [tempesta fw] modules are stopped Apr 26 04:05:31 192.168.122.209 [43281.785931] [tempesta fw] exiting... Apr 26 04:05:31 192.168.122.209 [43281.921269] [tdb] Shutdown Tempesta DB Apr 26 04:05:31 192.168.122.209 [43282.142529] End test: sessions.test_js_challenge.JSChallengeHttp.test_cookies_in_request_multiple_in_one Apr 26 04:05:31 192.168.122.209 [43282.152015] Start test: sessions.test_js_challenge.JSChallengeHttp.test_cookies_in_request_multiple_in_two Apr 26 04:05:31 192.168.122.209 [43282.256350] End test: sessions.test_js_challenge.JSChallengeHttp.test_cookies_in_request_multiple_in_two Apr 26 04:05:31 192.168.122.209 [43282.283299] Start test: sessions.test_js_challenge.JSChallengeHttp.test_delay_pass Apr 26 04:05:33 192.168.122.209 [43283.381299] [tdb] Start Tempesta DB Apr 26 04:05:33 192.168.122.209 [43283.533689] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:05:35 192.168.122.209 [43285.610903] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43285.610903] Maybe that's fine, but it's worth checking the [43285.610903] config - if there is no relations between the [43285.610903] names, then host name confusion attack is possible. Apr 26 04:05:35 192.168.122.209 [43285.783721] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:05:35 192.168.122.209 [43285.829667] [tempesta fw] Configuration processing is completed. Apr 26 04:05:35 192.168.122.209 [43285.884540] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:05:35 192.168.122.209 [43286.289312] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:05:35 192.168.122.209 [43286.315539] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:05:35 192.168.122.209 [43286.340684] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:05:36 192.168.122.209 [43286.385650] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:05:36 192.168.122.209 [43286.387384] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:05:36 192.168.122.209 [43286.445642] [tempesta fw] Tempesta FW is ready Apr 26 04:05:38 192.168.122.209 [43289.019353] [tdb] Close table 'client0.tdb' Apr 26 04:05:38 192.168.122.209 [43289.216909] [tdb] Close table 'sessions0.tdb' Apr 26 04:05:41 192.168.122.209 [43292.350720] [tdb] Close table 'cache0.tdb' Apr 26 04:05:42 192.168.122.209 [43292.595892] [tdb] Close table 'filter0.tdb' Apr 26 04:05:42 192.168.122.209 [43292.596324] [tempesta fw] modules are stopped Apr 26 04:05:42 192.168.122.209 [43292.820537] [tempesta fw] exiting... Apr 26 04:05:42 192.168.122.209 [43292.934876] [tdb] Shutdown Tempesta DB Apr 26 04:05:42 192.168.122.209 [43293.160111] End test: sessions.test_js_challenge.JSChallengeHttp.test_delay_pass Apr 26 04:05:42 192.168.122.209 [43293.180788] Start test: sessions.test_js_challenge.JSChallengeHttp.test_delay_pipelined_pass Apr 26 04:05:43 192.168.122.209 [43294.316307] [tdb] Start Tempesta DB Apr 26 04:05:44 192.168.122.209 [43294.465632] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:05:46 192.168.122.209 [43296.447052] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43296.447052] Maybe that's fine, but it's worth checking the [43296.447052] config - if there is no relations between the [43296.447052] names, then host name confusion attack is possible. Apr 26 04:05:46 192.168.122.209 [43296.615835] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:05:46 192.168.122.209 [43296.657736] [tempesta fw] Configuration processing is completed. Apr 26 04:05:46 192.168.122.209 [43296.708169] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:05:46 192.168.122.209 [43297.130653] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:05:46 192.168.122.209 [43297.157003] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:05:46 192.168.122.209 [43297.183849] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:05:46 192.168.122.209 [43297.237815] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:05:46 192.168.122.209 [43297.239573] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:05:46 192.168.122.209 [43297.281738] [tempesta fw] Tempesta FW is ready Apr 26 04:05:49 192.168.122.209 [43299.543891] [tdb] Close table 'client0.tdb' Apr 26 04:05:49 192.168.122.209 [43299.742038] [tdb] Close table 'sessions0.tdb' Apr 26 04:05:52 192.168.122.209 [43302.936791] [tdb] Close table 'cache0.tdb' Apr 26 04:05:52 192.168.122.209 [43303.168996] [tdb] Close table 'filter0.tdb' Apr 26 04:05:52 192.168.122.209 [43303.169435] [tempesta fw] modules are stopped Apr 26 04:05:53 192.168.122.209 [43303.353686] [tempesta fw] exiting... Apr 26 04:05:53 192.168.122.209 [43303.519670] [tdb] Shutdown Tempesta DB Apr 26 04:05:53 192.168.122.209 [43303.724455] End test: sessions.test_js_challenge.JSChallengeHttp.test_delay_pipelined_pass Apr 26 04:05:53 192.168.122.209 [43303.735897] Start test: sessions.test_js_challenge.JSChallengeHttp.test_delay_pipelined_too_early Apr 26 04:05:54 192.168.122.209 [43304.908314] [tdb] Start Tempesta DB Apr 26 04:05:54 192.168.122.209 [43305.046719] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:05:56 192.168.122.209 [43307.071198] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43307.071198] Maybe that's fine, but it's worth checking the [43307.071198] config - if there is no relations between the [43307.071198] names, then host name confusion attack is possible. Apr 26 04:05:56 192.168.122.209 [43307.251981] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:05:56 192.168.122.209 [43307.282339] [tempesta fw] Configuration processing is completed. Apr 26 04:05:56 192.168.122.209 [43307.332582] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:05:57 192.168.122.209 [43307.741756] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:05:57 192.168.122.209 [43307.767852] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:05:57 192.168.122.209 [43307.793827] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:05:57 192.168.122.209 [43307.845961] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:05:57 192.168.122.209 [43307.847676] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:05:57 192.168.122.209 [43307.885940] [tempesta fw] Tempesta FW is ready Apr 26 04:05:57 192.168.122.209 [43308.031191] [tempesta fw] Warning: http_sess: jsch redirect received too early for 127.0.0.2 (4305718838 is not after 4305719169) Apr 26 04:05:57 192.168.122.209 [43308.034438] [tempesta fw] Warning: frang: max rmisses exceeded for 127.0.0.2: 3 (lim=2) Apr 26 04:05:58 192.168.122.209 [43308.461365] [tdb] Close table 'client0.tdb' Apr 26 04:05:58 192.168.122.209 [43308.650666] [tdb] Close table 'sessions0.tdb' Apr 26 04:06:01 192.168.122.209 [43311.813810] [tdb] Close table 'cache0.tdb' Apr 26 04:06:01 192.168.122.209 [43312.058208] [tdb] Close table 'filter0.tdb' Apr 26 04:06:01 192.168.122.209 [43312.058646] [tempesta fw] modules are stopped Apr 26 04:06:01 192.168.122.209 [43312.224162] [tempesta fw] exiting... Apr 26 04:06:01 192.168.122.209 [43312.344168] [tdb] Shutdown Tempesta DB Apr 26 04:06:02 192.168.122.209 [43312.570864] End test: sessions.test_js_challenge.JSChallengeHttp.test_delay_pipelined_too_early Apr 26 04:06:02 192.168.122.209 [43312.582535] Start test: sessions.test_js_challenge.JSChallengeHttp.test_delay_too_small Apr 26 04:06:03 192.168.122.209 [43313.760196] [tdb] Start Tempesta DB Apr 26 04:06:03 192.168.122.209 [43313.923431] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:06:05 192.168.122.209 [43315.987287] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43315.987287] Maybe that's fine, but it's worth checking the [43315.987287] config - if there is no relations between the [43315.987287] names, then host name confusion attack is possible. Apr 26 04:06:05 192.168.122.209 [43316.144048] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:06:05 192.168.122.209 [43316.182047] [tempesta fw] Configuration processing is completed. Apr 26 04:06:05 192.168.122.209 [43316.243886] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:06:06 192.168.122.209 [43316.661000] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:06:06 192.168.122.209 [43316.687120] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:06:06 192.168.122.209 [43316.743088] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:06:06 192.168.122.209 [43316.798052] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:06:06 192.168.122.209 [43316.799776] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:06:06 192.168.122.209 [43316.837993] [tempesta fw] Tempesta FW is ready Apr 26 04:06:06 192.168.122.209 [43316.994792] [tempesta fw] Warning: http_sess: jsch redirect received too early for 127.0.0.2 (4305721079 is not after 4305721595) Apr 26 04:06:07 192.168.122.209 [43317.423374] [tdb] Close table 'client0.tdb' Apr 26 04:06:07 192.168.122.209 [43317.603074] [tdb] Close table 'sessions0.tdb' Apr 26 04:06:10 192.168.122.209 [43320.721827] [tdb] Close table 'cache0.tdb' Apr 26 04:06:10 192.168.122.209 [43320.969336] [tdb] Close table 'filter0.tdb' Apr 26 04:06:10 192.168.122.209 [43320.969762] [tempesta fw] modules are stopped Apr 26 04:06:10 192.168.122.209 [43321.155137] [tempesta fw] exiting... Apr 26 04:06:10 192.168.122.209 [43321.285033] [tdb] Shutdown Tempesta DB Apr 26 04:06:11 192.168.122.209 [43321.456302] End test: sessions.test_js_challenge.JSChallengeHttp.test_delay_too_small Apr 26 04:06:11 192.168.122.209 [43321.467915] Start test: sessions.test_js_challenge.JSChallengeHttp.test_disable_challenge_on_reload Apr 26 04:06:12 192.168.122.209 [43322.608907] [tdb] Start Tempesta DB Apr 26 04:06:12 192.168.122.209 [43322.777061] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:06:14 192.168.122.209 [43324.851394] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43324.851394] Maybe that's fine, but it's worth checking the [43324.851394] config - if there is no relations between the [43324.851394] names, then host name confusion attack is possible. Apr 26 04:06:14 192.168.122.209 [43325.020185] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:06:14 192.168.122.209 [43325.058157] [tempesta fw] Configuration processing is completed. Apr 26 04:06:14 192.168.122.209 [43325.115532] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:06:15 192.168.122.209 [43325.537621] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:06:15 192.168.122.209 [43325.563304] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:06:15 192.168.122.209 [43325.589330] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:06:15 192.168.122.209 [43325.638149] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:06:15 192.168.122.209 [43325.639773] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:06:15 192.168.122.209 [43325.698094] [tempesta fw] Tempesta FW is ready Apr 26 04:06:16 192.168.122.209 [43326.471515] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 04:06:16 192.168.122.209 [43326.556873] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43326.556873] Maybe that's fine, but it's worth checking the [43326.556873] config - if there is no relations between the [43326.556873] names, then host name confusion attack is possible. Apr 26 04:06:16 192.168.122.209 [43326.842190] [tempesta fw] Configuration processing is completed. Apr 26 04:06:16 192.168.122.209 [43327.114385] [tempesta fw] Tempesta FW is ready Apr 26 04:06:17 192.168.122.209 [43327.546995] [tdb] Close table 'client0.tdb' Apr 26 04:06:17 192.168.122.209 [43327.735973] [tdb] Close table 'sessions0.tdb' Apr 26 04:06:20 192.168.122.209 [43330.873609] [tdb] Close table 'cache0.tdb' Apr 26 04:06:20 192.168.122.209 [43331.108852] [tdb] Close table 'filter0.tdb' Apr 26 04:06:20 192.168.122.209 [43331.109287] [tempesta fw] modules are stopped Apr 26 04:06:20 192.168.122.209 [43331.314640] [tempesta fw] exiting... Apr 26 04:06:21 192.168.122.209 [43331.460818] [tdb] Shutdown Tempesta DB Apr 26 04:06:21 192.168.122.209 [43331.643099] End test: sessions.test_js_challenge.JSChallengeHttp.test_disable_challenge_on_reload Apr 26 04:06:21 192.168.122.209 [43331.666617] Start test: sessions.test_js_challenge.JSChallengeHttp.test_enable_challenge_on_reload Apr 26 04:06:22 192.168.122.209 [43332.817589] [tdb] Start Tempesta DB Apr 26 04:06:22 192.168.122.209 [43332.955626] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:06:24 192.168.122.209 [43334.747523] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43334.747523] Maybe that's fine, but it's worth checking the [43334.747523] config - if there is no relations between the [43334.747523] names, then host name confusion attack is possible. Apr 26 04:06:24 192.168.122.209 [43334.934228] [tempesta fw] Configuration processing is completed. Apr 26 04:06:24 192.168.122.209 [43334.986322] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:06:25 192.168.122.209 [43335.413171] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:06:25 192.168.122.209 [43335.447924] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:06:25 192.168.122.209 [43335.503750] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:06:25 192.168.122.209 [43335.550302] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:06:25 192.168.122.209 [43335.552010] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:06:25 192.168.122.209 [43335.598223] [tempesta fw] Tempesta FW is ready Apr 26 04:06:26 192.168.122.209 [43336.599620] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 04:06:26 192.168.122.209 [43336.679668] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43336.679668] Maybe that's fine, but it's worth checking the [43336.679668] config - if there is no relations between the [43336.679668] names, then host name confusion attack is possible. Apr 26 04:06:26 192.168.122.209 [43336.900422] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:06:26 192.168.122.209 [43336.946296] [tempesta fw] Configuration processing is completed. Apr 26 04:06:26 192.168.122.209 [43337.230395] [tempesta fw] Tempesta FW is ready Apr 26 04:06:28 192.168.122.209 [43338.858380] [tdb] Close table 'client0.tdb' Apr 26 04:06:28 192.168.122.209 [43339.057117] [tdb] Close table 'sessions0.tdb' Apr 26 04:06:31 192.168.122.209 [43342.282999] [tdb] Close table 'cache0.tdb' Apr 26 04:06:32 192.168.122.209 [43342.538372] [tdb] Close table 'filter0.tdb' Apr 26 04:06:32 192.168.122.209 [43342.538827] [tempesta fw] modules are stopped Apr 26 04:06:32 192.168.122.209 [43342.740531] [tempesta fw] exiting... Apr 26 04:06:32 192.168.122.209 [43342.850404] [tdb] Shutdown Tempesta DB Apr 26 04:06:32 192.168.122.209 [43343.065535] End test: sessions.test_js_challenge.JSChallengeHttp.test_enable_challenge_on_reload Apr 26 04:06:32 192.168.122.209 [43343.078493] Start test: sessions.test_js_challenge.JSChallengeHttp.test_first_post_request_pipelined Apr 26 04:06:33 192.168.122.209 [43344.257568] [tdb] Start Tempesta DB Apr 26 04:06:34 192.168.122.209 [43344.436770] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:06:36 192.168.122.209 [43346.511416] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43346.511416] Maybe that's fine, but it's worth checking the [43346.511416] config - if there is no relations between the [43346.511416] names, then host name confusion attack is possible. Apr 26 04:06:36 192.168.122.209 [43346.680546] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:06:36 192.168.122.209 [43346.722438] [tempesta fw] Configuration processing is completed. Apr 26 04:06:36 192.168.122.209 [43346.774207] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:06:36 192.168.122.209 [43347.218583] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:06:36 192.168.122.209 [43347.258703] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:06:36 192.168.122.209 [43347.319675] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:06:37 192.168.122.209 [43347.354367] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:06:37 192.168.122.209 [43347.355326] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:06:37 192.168.122.209 [43347.394403] [tempesta fw] Tempesta FW is ready Apr 26 04:06:39 192.168.122.209 [43350.160062] [tdb] Close table 'client0.tdb' Apr 26 04:06:40 192.168.122.209 [43350.368628] [tdb] Close table 'sessions0.tdb' Apr 26 04:06:43 192.168.122.209 [43353.562826] [tdb] Close table 'cache0.tdb' Apr 26 04:06:43 192.168.122.209 [43353.826969] [tdb] Close table 'filter0.tdb' Apr 26 04:06:43 192.168.122.209 [43353.827456] [tempesta fw] modules are stopped Apr 26 04:06:43 192.168.122.209 [43354.049615] [tempesta fw] exiting... Apr 26 04:06:43 192.168.122.209 [43354.216956] [tdb] Shutdown Tempesta DB Apr 26 04:06:44 192.168.122.209 [43354.447085] End test: sessions.test_js_challenge.JSChallengeHttp.test_first_post_request_pipelined Apr 26 04:06:44 192.168.122.209 [43354.461978] Start test: sessions.test_js_challenge.JSChallengeHttp.test_first_request_GET_and_accept_all Apr 26 04:06:45 192.168.122.209 [43355.690444] [tdb] Start Tempesta DB Apr 26 04:06:45 192.168.122.209 [43355.882345] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:06:47 192.168.122.209 [43357.908000] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43357.908000] Maybe that's fine, but it's worth checking the [43357.908000] config - if there is no relations between the [43357.908000] names, then host name confusion attack is possible. Apr 26 04:06:47 192.168.122.209 [43358.107097] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:06:47 192.168.122.209 [43358.146670] [tempesta fw] Configuration processing is completed. Apr 26 04:06:47 192.168.122.209 [43358.197368] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:06:48 192.168.122.209 [43358.626149] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:06:48 192.168.122.209 [43358.652932] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:06:48 192.168.122.209 [43358.679096] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:06:48 192.168.122.209 [43358.738594] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:06:48 192.168.122.209 [43358.740322] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:06:48 192.168.122.209 [43358.778528] [tempesta fw] Tempesta FW is ready Apr 26 04:06:48 192.168.122.209 [43359.342594] [tdb] Close table 'client0.tdb' Apr 26 04:06:49 192.168.122.209 [43359.539844] [tdb] Close table 'sessions0.tdb' Apr 26 04:06:52 192.168.122.209 [43362.706706] [tdb] Close table 'cache0.tdb' Apr 26 04:06:52 192.168.122.209 [43362.936391] [tdb] Close table 'filter0.tdb' Apr 26 04:06:52 192.168.122.209 [43362.936820] [tempesta fw] modules are stopped Apr 26 04:06:52 192.168.122.209 [43363.116061] [tempesta fw] exiting... Apr 26 04:06:52 192.168.122.209 [43363.261764] [tdb] Shutdown Tempesta DB Apr 26 04:06:53 192.168.122.209 [43363.464191] End test: sessions.test_js_challenge.JSChallengeHttp.test_first_request_GET_and_accept_all Apr 26 04:06:53 192.168.122.209 [43363.475586] Start test: sessions.test_js_challenge.JSChallengeHttp.test_first_request_GET_and_accept_html Apr 26 04:06:54 192.168.122.209 [43364.644897] [tdb] Start Tempesta DB Apr 26 04:06:54 192.168.122.209 [43364.806678] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:06:56 192.168.122.209 [43366.739983] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43366.739983] Maybe that's fine, but it's worth checking the [43366.739983] config - if there is no relations between the [43366.739983] names, then host name confusion attack is possible. Apr 26 04:06:56 192.168.122.209 [43366.896829] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:06:56 192.168.122.209 [43366.938996] [tempesta fw] Configuration processing is completed. Apr 26 04:06:56 192.168.122.209 [43366.990236] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:06:57 192.168.122.209 [43367.406993] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:06:57 192.168.122.209 [43367.432993] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:06:57 192.168.122.209 [43367.489539] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:06:57 192.168.122.209 [43367.570684] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:06:57 192.168.122.209 [43367.572426] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:06:57 192.168.122.209 [43367.618644] [tempesta fw] Tempesta FW is ready Apr 26 04:06:57 192.168.122.209 [43368.179176] [tdb] Close table 'client0.tdb' Apr 26 04:06:58 192.168.122.209 [43368.381897] [tdb] Close table 'sessions0.tdb' Apr 26 04:07:01 192.168.122.209 [43371.591957] [tdb] Close table 'cache0.tdb' Apr 26 04:07:01 192.168.122.209 [43371.826850] [tdb] Close table 'filter0.tdb' Apr 26 04:07:01 192.168.122.209 [43371.827293] [tempesta fw] modules are stopped Apr 26 04:07:01 192.168.122.209 [43372.023876] [tempesta fw] exiting... Apr 26 04:07:01 192.168.122.209 [43372.166145] [tdb] Shutdown Tempesta DB Apr 26 04:07:02 192.168.122.209 [43372.357002] End test: sessions.test_js_challenge.JSChallengeHttp.test_first_request_GET_and_accept_html Apr 26 04:07:02 192.168.122.209 [43372.371370] Start test: sessions.test_js_challenge.JSChallengeHttp.test_first_request_GET_and_accept_image Apr 26 04:07:03 192.168.122.209 [43373.451472] [tdb] Start Tempesta DB Apr 26 04:07:03 192.168.122.209 [43373.626876] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:07:05 192.168.122.209 [43375.549016] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43375.549016] Maybe that's fine, but it's worth checking the [43375.549016] config - if there is no relations between the [43375.549016] names, then host name confusion attack is possible. Apr 26 04:07:05 192.168.122.209 [43375.708844] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:07:05 192.168.122.209 [43375.750891] [tempesta fw] Configuration processing is completed. Apr 26 04:07:05 192.168.122.209 [43375.802744] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:07:05 192.168.122.209 [43376.232000] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:07:05 192.168.122.209 [43376.257619] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:07:05 192.168.122.209 [43376.283313] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:07:05 192.168.122.209 [43376.346793] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:07:05 192.168.122.209 [43376.348521] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:07:06 192.168.122.209 [43376.390767] [tempesta fw] Tempesta FW is ready Apr 26 04:07:06 192.168.122.209 [43376.920894] [tdb] Close table 'client0.tdb' Apr 26 04:07:06 192.168.122.209 [43377.110359] [tdb] Close table 'sessions0.tdb' Apr 26 04:07:09 192.168.122.209 [43380.341419] [tdb] Close table 'cache0.tdb' Apr 26 04:07:10 192.168.122.209 [43380.587958] [tdb] Close table 'filter0.tdb' Apr 26 04:07:10 192.168.122.209 [43380.588404] [tempesta fw] modules are stopped Apr 26 04:07:10 192.168.122.209 [43380.763770] [tempesta fw] exiting... Apr 26 04:07:10 192.168.122.209 [43380.888064] [tdb] Shutdown Tempesta DB Apr 26 04:07:10 192.168.122.209 [43381.100938] End test: sessions.test_js_challenge.JSChallengeHttp.test_first_request_GET_and_accept_image Apr 26 04:07:10 192.168.122.209 [43381.123357] Start test: sessions.test_js_challenge.JSChallengeHttp.test_first_request_GET_and_accept_plain Apr 26 04:07:11 192.168.122.209 [43382.272957] [tdb] Start Tempesta DB Apr 26 04:07:12 192.168.122.209 [43382.425490] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:07:14 192.168.122.209 [43384.384243] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43384.384243] Maybe that's fine, but it's worth checking the [43384.384243] config - if there is no relations between the [43384.384243] names, then host name confusion attack is possible. Apr 26 04:07:14 192.168.122.209 [43384.556966] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:07:14 192.168.122.209 [43384.594884] [tempesta fw] Configuration processing is completed. Apr 26 04:07:14 192.168.122.209 [43384.660868] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:07:14 192.168.122.209 [43385.070060] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:07:14 192.168.122.209 [43385.096963] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:07:14 192.168.122.209 [43385.154465] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:07:14 192.168.122.209 [43385.202906] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:07:14 192.168.122.209 [43385.203931] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:07:14 192.168.122.209 [43385.246856] [tempesta fw] Tempesta FW is ready Apr 26 04:07:15 192.168.122.209 [43385.768842] [tdb] Close table 'client0.tdb' Apr 26 04:07:15 192.168.122.209 [43385.974694] [tdb] Close table 'sessions0.tdb' Apr 26 04:07:18 192.168.122.209 [43389.135545] [tdb] Close table 'cache0.tdb' Apr 26 04:07:19 192.168.122.209 [43389.378982] [tdb] Close table 'filter0.tdb' Apr 26 04:07:19 192.168.122.209 [43389.379418] [tempesta fw] modules are stopped Apr 26 04:07:19 192.168.122.209 [43389.589505] [tempesta fw] exiting... Apr 26 04:07:19 192.168.122.209 [43389.711630] [tdb] Shutdown Tempesta DB Apr 26 04:07:19 192.168.122.209 [43389.945519] End test: sessions.test_js_challenge.JSChallengeHttp.test_first_request_GET_and_accept_plain Apr 26 04:07:19 192.168.122.209 [43389.958753] Start test: sessions.test_js_challenge.JSChallengeHttp.test_first_request_GET_and_accept_text_all Apr 26 04:07:20 192.168.122.209 [43391.173684] [tdb] Start Tempesta DB Apr 26 04:07:20 192.168.122.209 [43391.320805] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:07:22 192.168.122.209 [43393.292298] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43393.292298] Maybe that's fine, but it's worth checking the [43393.292298] config - if there is no relations between the [43393.292298] names, then host name confusion attack is possible. Apr 26 04:07:23 192.168.122.209 [43393.465054] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:07:23 192.168.122.209 [43393.503096] [tempesta fw] Configuration processing is completed. Apr 26 04:07:23 192.168.122.209 [43393.554239] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:07:23 192.168.122.209 [43393.966366] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:07:23 192.168.122.209 [43393.992591] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:07:23 192.168.122.209 [43394.018635] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:07:23 192.168.122.209 [43394.063028] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:07:23 192.168.122.209 [43394.064755] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:07:23 192.168.122.209 [43394.102973] [tempesta fw] Tempesta FW is ready Apr 26 04:07:24 192.168.122.209 [43394.639870] [tdb] Close table 'client0.tdb' Apr 26 04:07:24 192.168.122.209 [43394.856127] [tdb] Close table 'sessions0.tdb' Apr 26 04:07:27 192.168.122.209 [43397.959611] [tdb] Close table 'cache0.tdb' Apr 26 04:07:27 192.168.122.209 [43398.183974] [tdb] Close table 'filter0.tdb' Apr 26 04:07:27 192.168.122.209 [43398.184403] [tempesta fw] modules are stopped Apr 26 04:07:28 192.168.122.209 [43398.425046] [tempesta fw] exiting... Apr 26 04:07:28 192.168.122.209 [43398.570729] [tdb] Shutdown Tempesta DB Apr 26 04:07:28 192.168.122.209 [43398.768068] End test: sessions.test_js_challenge.JSChallengeHttp.test_first_request_GET_and_accept_text_all Apr 26 04:07:28 192.168.122.209 [43398.777344] Start test: sessions.test_js_challenge.JSChallengeHttp.test_first_request_POST Apr 26 04:07:29 192.168.122.209 [43399.944219] [tdb] Start Tempesta DB Apr 26 04:07:29 192.168.122.209 [43400.096513] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:07:31 192.168.122.209 [43402.124510] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43402.124510] Maybe that's fine, but it's worth checking the [43402.124510] config - if there is no relations between the [43402.124510] names, then host name confusion attack is possible. Apr 26 04:07:31 192.168.122.209 [43402.289108] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:07:31 192.168.122.209 [43402.343151] [tempesta fw] Configuration processing is completed. Apr 26 04:07:32 192.168.122.209 [43402.393309] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:07:32 192.168.122.209 [43402.821713] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:07:32 192.168.122.209 [43402.847106] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:07:32 192.168.122.209 [43402.908456] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:07:32 192.168.122.209 [43402.963129] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:07:32 192.168.122.209 [43402.964323] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:07:32 192.168.122.209 [43403.015076] [tempesta fw] Tempesta FW is ready Apr 26 04:07:33 192.168.122.209 [43403.558939] [tdb] Close table 'client0.tdb' Apr 26 04:07:33 192.168.122.209 [43403.745951] [tdb] Close table 'sessions0.tdb' Apr 26 04:07:36 192.168.122.209 [43406.893209] [tdb] Close table 'cache0.tdb' Apr 26 04:07:36 192.168.122.209 [43407.163553] [tdb] Close table 'filter0.tdb' Apr 26 04:07:36 192.168.122.209 [43407.163994] [tempesta fw] modules are stopped Apr 26 04:07:37 192.168.122.209 [43407.395101] [tempesta fw] exiting... Apr 26 04:07:37 192.168.122.209 [43407.564244] [tdb] Shutdown Tempesta DB Apr 26 04:07:37 192.168.122.209 [43407.768446] End test: sessions.test_js_challenge.JSChallengeHttp.test_first_request_POST Apr 26 04:07:37 192.168.122.209 [43407.775946] Start test: sessions.test_js_challenge.JSChallengeHttp.test_method_override_GET_HEAD Apr 26 04:07:38 192.168.122.209 [43408.900371] [tdb] Start Tempesta DB Apr 26 04:07:38 192.168.122.209 [43409.036649] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:07:40 192.168.122.209 [43410.996514] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43410.996514] Maybe that's fine, but it's worth checking the [43410.996514] config - if there is no relations between the [43410.996514] names, then host name confusion attack is possible. Apr 26 04:07:40 192.168.122.209 [43411.153279] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:07:40 192.168.122.209 [43411.195292] [tempesta fw] Configuration processing is completed. Apr 26 04:07:40 192.168.122.209 [43411.245396] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:07:41 192.168.122.209 [43411.687229] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:07:41 192.168.122.209 [43411.713649] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:07:41 192.168.122.209 [43411.739989] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:07:41 192.168.122.209 [43411.779266] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:07:41 192.168.122.209 [43411.780976] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:07:41 192.168.122.209 [43411.819223] [tempesta fw] Tempesta FW is ready Apr 26 04:07:42 192.168.122.209 [43412.398632] [tdb] Close table 'client0.tdb' Apr 26 04:07:42 192.168.122.209 [43412.584458] [tdb] Close table 'sessions0.tdb' Apr 26 04:07:45 192.168.122.209 [43415.699766] [tdb] Close table 'cache0.tdb' Apr 26 04:07:45 192.168.122.209 [43415.940730] [tdb] Close table 'filter0.tdb' Apr 26 04:07:45 192.168.122.209 [43415.941168] [tempesta fw] modules are stopped Apr 26 04:07:45 192.168.122.209 [43416.125617] [tempesta fw] exiting... Apr 26 04:07:45 192.168.122.209 [43416.267185] [tdb] Shutdown Tempesta DB Apr 26 04:07:46 192.168.122.209 [43416.467157] End test: sessions.test_js_challenge.JSChallengeHttp.test_method_override_GET_HEAD Apr 26 04:07:46 192.168.122.209 [43416.478715] Start test: sessions.test_js_challenge.JSChallengeHttp.test_method_override_GET_POST Apr 26 04:07:47 192.168.122.209 [43417.670819] [tdb] Start Tempesta DB Apr 26 04:07:47 192.168.122.209 [43417.829970] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:07:49 192.168.122.209 [43419.848667] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43419.848667] Maybe that's fine, but it's worth checking the [43419.848667] config - if there is no relations between the [43419.848667] names, then host name confusion attack is possible. Apr 26 04:07:49 192.168.122.209 [43420.005382] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:07:49 192.168.122.209 [43420.043390] [tempesta fw] Configuration processing is completed. Apr 26 04:07:49 192.168.122.209 [43420.101694] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:07:50 192.168.122.209 [43420.527941] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:07:50 192.168.122.209 [43420.553340] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:07:50 192.168.122.209 [43420.613938] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:07:50 192.168.122.209 [43420.663367] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:07:50 192.168.122.209 [43420.665094] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:07:50 192.168.122.209 [43420.703305] [tempesta fw] Tempesta FW is ready Apr 26 04:07:50 192.168.122.209 [43420.832763] [tempesta fw] Warning: request dropped: unsafe method override: 127.0.0.2 Apr 26 04:07:50 192.168.122.209 [43421.279663] [tdb] Close table 'client0.tdb' Apr 26 04:07:51 192.168.122.209 [43421.467060] [tdb] Close table 'sessions0.tdb' Apr 26 04:07:54 192.168.122.209 [43424.628589] [tdb] Close table 'cache0.tdb' Apr 26 04:07:54 192.168.122.209 [43424.862029] [tdb] Close table 'filter0.tdb' Apr 26 04:07:54 192.168.122.209 [43424.862463] [tempesta fw] modules are stopped Apr 26 04:07:54 192.168.122.209 [43425.055785] [tempesta fw] exiting... Apr 26 04:07:54 192.168.122.209 [43425.238698] [tdb] Shutdown Tempesta DB Apr 26 04:07:55 192.168.122.209 [43425.435024] End test: sessions.test_js_challenge.JSChallengeHttp.test_method_override_GET_POST Apr 26 04:07:55 192.168.122.209 [43425.446448] Start test: sessions.test_js_challenge.JSChallengeHttp.test_method_override_HEAD_POST Apr 26 04:07:56 192.168.122.209 [43426.557684] [tdb] Start Tempesta DB Apr 26 04:07:56 192.168.122.209 [43426.705399] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:07:58 192.168.122.209 [43428.724821] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43428.724821] Maybe that's fine, but it's worth checking the [43428.724821] config - if there is no relations between the [43428.724821] names, then host name confusion attack is possible. Apr 26 04:07:58 192.168.122.209 [43428.881504] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:07:58 192.168.122.209 [43428.911879] [tempesta fw] Configuration processing is completed. Apr 26 04:07:58 192.168.122.209 [43428.965648] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:07:59 192.168.122.209 [43429.375964] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:07:59 192.168.122.209 [43429.401715] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:07:59 192.168.122.209 [43429.458143] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:07:59 192.168.122.209 [43429.515395] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:07:59 192.168.122.209 [43429.516356] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:07:59 192.168.122.209 [43429.555415] [tempesta fw] Tempesta FW is ready Apr 26 04:07:59 192.168.122.209 [43429.685084] [tempesta fw] Warning: request dropped: unsafe method override: 127.0.0.2 Apr 26 04:07:59 192.168.122.209 [43430.131541] [tdb] Close table 'client0.tdb' Apr 26 04:07:59 192.168.122.209 [43430.326362] [tdb] Close table 'sessions0.tdb' Apr 26 04:08:03 192.168.122.209 [43433.465658] [tdb] Close table 'cache0.tdb' Apr 26 04:08:03 192.168.122.209 [43433.711252] [tdb] Close table 'filter0.tdb' Apr 26 04:08:03 192.168.122.209 [43433.711683] [tempesta fw] modules are stopped Apr 26 04:08:03 192.168.122.209 [43433.895785] [tempesta fw] exiting... Apr 26 04:08:03 192.168.122.209 [43434.033544] [tdb] Shutdown Tempesta DB Apr 26 04:08:03 192.168.122.209 [43434.234091] End test: sessions.test_js_challenge.JSChallengeHttp.test_method_override_HEAD_POST Apr 26 04:08:03 192.168.122.209 [43434.260400] Start test: sessions.test_js_challenge.JSChallengeHttp.test_method_override_POST_GET Apr 26 04:08:05 192.168.122.209 [43435.418386] [tdb] Start Tempesta DB Apr 26 04:08:05 192.168.122.209 [43435.563777] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:08:07 192.168.122.209 [43437.572874] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43437.572874] Maybe that's fine, but it's worth checking the [43437.572874] config - if there is no relations between the [43437.572874] names, then host name confusion attack is possible. Apr 26 04:08:07 192.168.122.209 [43437.733705] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:08:07 192.168.122.209 [43437.779562] [tempesta fw] Configuration processing is completed. Apr 26 04:08:07 192.168.122.209 [43437.838435] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:08:07 192.168.122.209 [43438.256618] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:08:07 192.168.122.209 [43438.292958] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:08:07 192.168.122.209 [43438.323816] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:08:08 192.168.122.209 [43438.371594] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:08:08 192.168.122.209 [43438.373314] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:08:08 192.168.122.209 [43438.419528] [tempesta fw] Tempesta FW is ready Apr 26 04:08:08 192.168.122.209 [43439.003876] [tdb] Close table 'client0.tdb' Apr 26 04:08:08 192.168.122.209 [43439.192171] [tdb] Close table 'sessions0.tdb' Apr 26 04:08:11 192.168.122.209 [43442.314900] [tdb] Close table 'cache0.tdb' Apr 26 04:08:12 192.168.122.209 [43442.540969] [tdb] Close table 'filter0.tdb' Apr 26 04:08:12 192.168.122.209 [43442.541394] [tempesta fw] modules are stopped Apr 26 04:08:12 192.168.122.209 [43442.756585] [tempesta fw] exiting... Apr 26 04:08:12 192.168.122.209 [43442.895248] [tdb] Shutdown Tempesta DB Apr 26 04:08:12 192.168.122.209 [43443.129567] End test: sessions.test_js_challenge.JSChallengeHttp.test_method_override_POST_GET Apr 26 04:08:12 192.168.122.209 [43443.141434] Start test: sessions.test_js_challenge.JSChallengeHttp.test_method_override_POST_HEAD Apr 26 04:08:13 192.168.122.209 [43444.280704] [tdb] Start Tempesta DB Apr 26 04:08:14 192.168.122.209 [43444.435976] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:08:16 192.168.122.209 [43446.521002] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43446.521002] Maybe that's fine, but it's worth checking the [43446.521002] config - if there is no relations between the [43446.521002] names, then host name confusion attack is possible. Apr 26 04:08:16 192.168.122.209 [43446.685829] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:08:16 192.168.122.209 [43446.728029] [tempesta fw] Configuration processing is completed. Apr 26 04:08:16 192.168.122.209 [43446.783755] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:08:16 192.168.122.209 [43447.203099] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:08:16 192.168.122.209 [43447.236940] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:08:16 192.168.122.209 [43447.293255] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:08:16 192.168.122.209 [43447.345393] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:08:16 192.168.122.209 [43447.347129] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:08:17 192.168.122.209 [43447.383662] [tempesta fw] Tempesta FW is ready Apr 26 04:08:17 192.168.122.209 [43447.927538] [tdb] Close table 'client0.tdb' Apr 26 04:08:17 192.168.122.209 [43448.120550] [tdb] Close table 'sessions0.tdb' Apr 26 04:08:20 192.168.122.209 [43451.239203] [tdb] Close table 'cache0.tdb' Apr 26 04:08:21 192.168.122.209 [43451.491378] [tdb] Close table 'filter0.tdb' Apr 26 04:08:21 192.168.122.209 [43451.491836] [tempesta fw] modules are stopped Apr 26 04:08:21 192.168.122.209 [43451.670175] [tempesta fw] exiting... Apr 26 04:08:21 192.168.122.209 [43451.803917] [tdb] Shutdown Tempesta DB Apr 26 04:08:21 192.168.122.209 [43451.982241] End test: sessions.test_js_challenge.JSChallengeHttp.test_method_override_POST_HEAD Apr 26 04:08:21 192.168.122.209 [43451.993733] Start test: sessions.test_js_challenge.JSChallengeHttp.test_method_override_with_cache_GET_HEAD Apr 26 04:08:22 192.168.122.209 [43453.139278] [tdb] Start Tempesta DB Apr 26 04:08:22 192.168.122.209 [43453.299466] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:08:24 192.168.122.209 [43455.237059] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43455.237059] Maybe that's fine, but it's worth checking the [43455.237059] config - if there is no relations between the [43455.237059] names, then host name confusion attack is possible. Apr 26 04:08:25 192.168.122.209 [43455.401846] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:08:25 192.168.122.209 [43455.443806] [tempesta fw] Configuration processing is completed. Apr 26 04:08:25 192.168.122.209 [43455.503880] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:08:25 192.168.122.209 [43455.924934] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:08:25 192.168.122.209 [43455.950799] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:08:25 192.168.122.209 [43455.976790] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:08:25 192.168.122.209 [43456.023817] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:08:25 192.168.122.209 [43456.025538] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:08:25 192.168.122.209 [43456.063769] [tempesta fw] Tempesta FW is ready Apr 26 04:08:28 192.168.122.209 [43459.051262] [tdb] Close table 'client0.tdb' Apr 26 04:08:28 192.168.122.209 [43459.242017] [tdb] Close table 'sessions0.tdb' Apr 26 04:08:32 192.168.122.209 [43462.373331] [tdb] Close table 'cache0.tdb' Apr 26 04:08:32 192.168.122.209 [43462.609724] [tdb] Close table 'filter0.tdb' Apr 26 04:08:32 192.168.122.209 [43462.610182] [tempesta fw] modules are stopped Apr 26 04:08:32 192.168.122.209 [43462.804860] [tempesta fw] exiting... Apr 26 04:08:32 192.168.122.209 [43462.916018] [tdb] Shutdown Tempesta DB Apr 26 04:08:32 192.168.122.209 [43463.125309] End test: sessions.test_js_challenge.JSChallengeHttp.test_method_override_with_cache_GET_HEAD Apr 26 04:08:32 192.168.122.209 [43463.140041] Start test: sessions.test_js_challenge.JSChallengeHttp.test_method_override_with_cache_GET_POST Apr 26 04:08:33 192.168.122.209 [43464.292566] [tdb] Start Tempesta DB Apr 26 04:08:34 192.168.122.209 [43464.449542] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:08:36 192.168.122.209 [43466.457214] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43466.457214] Maybe that's fine, but it's worth checking the [43466.457214] config - if there is no relations between the [43466.457214] names, then host name confusion attack is possible. Apr 26 04:08:36 192.168.122.209 [43466.621983] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:08:36 192.168.122.209 [43466.668012] [tempesta fw] Configuration processing is completed. Apr 26 04:08:36 192.168.122.209 [43466.725457] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:08:36 192.168.122.209 [43467.134922] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:08:36 192.168.122.209 [43467.160625] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:08:36 192.168.122.209 [43467.227061] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:08:36 192.168.122.209 [43467.279910] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:08:36 192.168.122.209 [43467.281686] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:08:36 192.168.122.209 [43467.335922] [tempesta fw] Tempesta FW is ready Apr 26 04:08:39 192.168.122.209 [43469.685294] [tempesta fw] Warning: request dropped: unsafe method override: 127.0.0.2 Apr 26 04:08:39 192.168.122.209 [43470.114961] [tdb] Close table 'client0.tdb' Apr 26 04:08:39 192.168.122.209 [43470.319475] [tdb] Close table 'sessions0.tdb' Apr 26 04:08:43 192.168.122.209 [43473.483242] [tdb] Close table 'cache0.tdb' Apr 26 04:08:43 192.168.122.209 [43473.742585] [tdb] Close table 'filter0.tdb' Apr 26 04:08:43 192.168.122.209 [43473.743048] [tempesta fw] modules are stopped Apr 26 04:08:43 192.168.122.209 [43473.943936] [tempesta fw] exiting... Apr 26 04:08:43 192.168.122.209 [43474.101016] [tdb] Shutdown Tempesta DB Apr 26 04:08:43 192.168.122.209 [43474.297150] End test: sessions.test_js_challenge.JSChallengeHttp.test_method_override_with_cache_GET_POST Apr 26 04:08:43 192.168.122.209 [43474.310183] Start test: sessions.test_js_challenge.JSChallengeHttp.test_method_override_with_cache_HEAD_GET Apr 26 04:08:45 192.168.122.209 [43475.440268] [tdb] Start Tempesta DB Apr 26 04:08:45 192.168.122.209 [43475.585521] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:08:47 192.168.122.209 [43477.609336] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43477.609336] Maybe that's fine, but it's worth checking the [43477.609336] config - if there is no relations between the [43477.609336] names, then host name confusion attack is possible. Apr 26 04:08:47 192.168.122.209 [43477.794123] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:08:47 192.168.122.209 [43477.836101] [tempesta fw] Configuration processing is completed. Apr 26 04:08:47 192.168.122.209 [43477.888556] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:08:47 192.168.122.209 [43478.301243] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:08:47 192.168.122.209 [43478.337326] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:08:48 192.168.122.209 [43478.399222] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:08:48 192.168.122.209 [43478.444098] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:08:48 192.168.122.209 [43478.445808] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:08:48 192.168.122.209 [43478.492050] [tempesta fw] Tempesta FW is ready Apr 26 04:08:50 192.168.122.209 [43481.049181] [tdb] Close table 'client0.tdb' Apr 26 04:08:50 192.168.122.209 [43481.244000] [tdb] Close table 'sessions0.tdb' Apr 26 04:08:54 192.168.122.209 [43484.369785] [tdb] Close table 'cache0.tdb' Apr 26 04:08:54 192.168.122.209 [43484.631273] [tdb] Close table 'filter0.tdb' Apr 26 04:08:54 192.168.122.209 [43484.631710] [tempesta fw] modules are stopped Apr 26 04:08:54 192.168.122.209 [43484.832144] [tempesta fw] exiting... Apr 26 04:08:54 192.168.122.209 [43484.968980] [tdb] Shutdown Tempesta DB Apr 26 04:08:54 192.168.122.209 [43485.218566] End test: sessions.test_js_challenge.JSChallengeHttp.test_method_override_with_cache_HEAD_GET Apr 26 04:08:54 192.168.122.209 [43485.229843] Start test: sessions.test_js_challenge.JSChallengeHttp.test_method_override_with_cache_HEAD_POST Apr 26 04:08:56 192.168.122.209 [43486.416806] [tdb] Start Tempesta DB Apr 26 04:08:56 192.168.122.209 [43486.571146] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:08:58 192.168.122.209 [43488.553535] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43488.553535] Maybe that's fine, but it's worth checking the [43488.553535] config - if there is no relations between the [43488.553535] names, then host name confusion attack is possible. Apr 26 04:08:58 192.168.122.209 [43488.738249] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:08:58 192.168.122.209 [43488.780243] [tempesta fw] Configuration processing is completed. Apr 26 04:08:58 192.168.122.209 [43488.831412] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:08:58 192.168.122.209 [43489.237964] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:08:58 192.168.122.209 [43489.263601] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:08:58 192.168.122.209 [43489.319321] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:08:59 192.168.122.209 [43489.368227] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:08:59 192.168.122.209 [43489.369820] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:08:59 192.168.122.209 [43489.424219] [tempesta fw] Tempesta FW is ready Apr 26 04:09:00 192.168.122.209 [43491.283093] [tempesta fw] Warning: request dropped: unsafe method override: 127.0.0.2 Apr 26 04:09:01 192.168.122.209 [43491.711408] [tdb] Close table 'client0.tdb' Apr 26 04:09:01 192.168.122.209 [43491.891288] [tdb] Close table 'sessions0.tdb' Apr 26 04:09:04 192.168.122.209 [43495.070218] [tdb] Close table 'cache0.tdb' Apr 26 04:09:04 192.168.122.209 [43495.304654] [tdb] Close table 'filter0.tdb' Apr 26 04:09:04 192.168.122.209 [43495.305076] [tempesta fw] modules are stopped Apr 26 04:09:05 192.168.122.209 [43495.495940] [tempesta fw] exiting... Apr 26 04:09:05 192.168.122.209 [43495.685281] [tdb] Shutdown Tempesta DB Apr 26 04:09:05 192.168.122.209 [43495.919665] End test: sessions.test_js_challenge.JSChallengeHttp.test_method_override_with_cache_HEAD_POST Apr 26 04:09:05 192.168.122.209 [43495.931408] Start test: sessions.test_js_challenge.JSChallengeHttp.test_method_override_with_cache_POST_GET Apr 26 04:09:06 192.168.122.209 [43497.075958] [tdb] Start Tempesta DB Apr 26 04:09:06 192.168.122.209 [43497.233288] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:09:08 192.168.122.209 [43499.273620] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43499.273620] Maybe that's fine, but it's worth checking the [43499.273620] config - if there is no relations between the [43499.273620] names, then host name confusion attack is possible. Apr 26 04:09:09 192.168.122.209 [43499.430381] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:09:09 192.168.122.209 [43499.476380] [tempesta fw] Configuration processing is completed. Apr 26 04:09:09 192.168.122.209 [43499.525932] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:09:09 192.168.122.209 [43499.928885] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:09:09 192.168.122.209 [43499.954316] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:09:09 192.168.122.209 [43500.026994] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:09:09 192.168.122.209 [43500.084386] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:09:09 192.168.122.209 [43500.086094] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:09:09 192.168.122.209 [43500.128345] [tempesta fw] Tempesta FW is ready Apr 26 04:09:11 192.168.122.209 [43502.091787] [tdb] Close table 'client0.tdb' Apr 26 04:09:11 192.168.122.209 [43502.280383] [tdb] Close table 'sessions0.tdb' Apr 26 04:09:15 192.168.122.209 [43505.412704] [tdb] Close table 'cache0.tdb' Apr 26 04:09:15 192.168.122.209 [43505.636388] [tdb] Close table 'filter0.tdb' Apr 26 04:09:15 192.168.122.209 [43505.636807] [tempesta fw] modules are stopped Apr 26 04:09:15 192.168.122.209 [43505.819662] [tempesta fw] exiting... Apr 26 04:09:15 192.168.122.209 [43505.978521] [tdb] Shutdown Tempesta DB Apr 26 04:09:15 192.168.122.209 [43506.192081] End test: sessions.test_js_challenge.JSChallengeHttp.test_method_override_with_cache_POST_GET Apr 26 04:09:15 192.168.122.209 [43506.206753] Start test: sessions.test_js_challenge.JSChallengeHttp.test_method_override_with_cache_POST_HEAD Apr 26 04:09:16 192.168.122.209 [43507.350190] [tdb] Start Tempesta DB Apr 26 04:09:17 192.168.122.209 [43507.502685] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:09:19 192.168.122.209 [43509.533761] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43509.533761] Maybe that's fine, but it's worth checking the [43509.533761] config - if there is no relations between the [43509.533761] names, then host name confusion attack is possible. Apr 26 04:09:19 192.168.122.209 [43509.702547] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:09:19 192.168.122.209 [43509.748529] [tempesta fw] Configuration processing is completed. Apr 26 04:09:19 192.168.122.209 [43509.799574] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:09:19 192.168.122.209 [43510.214100] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:09:19 192.168.122.209 [43510.239759] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:09:19 192.168.122.209 [43510.294967] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:09:19 192.168.122.209 [43510.340513] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:09:19 192.168.122.209 [43510.342236] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:09:20 192.168.122.209 [43510.380443] [tempesta fw] Tempesta FW is ready Apr 26 04:09:23 192.168.122.209 [43513.416022] [tdb] Close table 'client0.tdb' Apr 26 04:09:23 192.168.122.209 [43513.602918] [tdb] Close table 'sessions0.tdb' Apr 26 04:09:26 192.168.122.209 [43516.732608] [tdb] Close table 'cache0.tdb' Apr 26 04:09:26 192.168.122.209 [43516.947364] [tdb] Close table 'filter0.tdb' Apr 26 04:09:26 192.168.122.209 [43516.947786] [tempesta fw] modules are stopped Apr 26 04:09:26 192.168.122.209 [43517.179125] [tempesta fw] exiting... Apr 26 04:09:26 192.168.122.209 [43517.310822] [tdb] Shutdown Tempesta DB Apr 26 04:09:27 192.168.122.209 [43517.533087] End test: sessions.test_js_challenge.JSChallengeHttp.test_method_override_with_cache_POST_HEAD Apr 26 04:09:27 192.168.122.209 [43517.542471] Start test: sessions.test_js_challenge.JSChallengeHttp.test_new_client_session_with_exist_cookie Apr 26 04:09:28 192.168.122.209 [43518.727978] [tdb] Start Tempesta DB Apr 26 04:09:28 192.168.122.209 [43518.861199] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:09:30 192.168.122.209 [43520.837889] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43520.837889] Maybe that's fine, but it's worth checking the [43520.837889] config - if there is no relations between the [43520.837889] names, then host name confusion attack is possible. Apr 26 04:09:30 192.168.122.209 [43521.014742] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:09:30 192.168.122.209 [43521.056640] [tempesta fw] Configuration processing is completed. Apr 26 04:09:30 192.168.122.209 [43521.110051] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:09:31 192.168.122.209 [43521.527941] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:09:31 192.168.122.209 [43521.553853] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:09:31 192.168.122.209 [43521.579692] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:09:31 192.168.122.209 [43521.652645] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:09:31 192.168.122.209 [43521.654354] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:09:31 192.168.122.209 [43521.696608] [tempesta fw] Tempesta FW is ready Apr 26 04:09:34 192.168.122.209 [43524.551446] [tdb] Close table 'client0.tdb' Apr 26 04:09:34 192.168.122.209 [43524.737775] [tdb] Close table 'sessions0.tdb' Apr 26 04:09:37 192.168.122.209 [43527.850486] [tdb] Close table 'cache0.tdb' Apr 26 04:09:37 192.168.122.209 [43528.077284] [tdb] Close table 'filter0.tdb' Apr 26 04:09:37 192.168.122.209 [43528.077711] [tempesta fw] modules are stopped Apr 26 04:09:37 192.168.122.209 [43528.274803] [tempesta fw] exiting... Apr 26 04:09:38 192.168.122.209 [43528.441718] [tdb] Shutdown Tempesta DB Apr 26 04:09:38 192.168.122.209 [43528.666512] End test: sessions.test_js_challenge.JSChallengeHttp.test_new_client_session_with_exist_cookie Apr 26 04:09:38 192.168.122.209 [43528.676456] Start test: sessions.test_js_challenge.JSChallengeHttp.test_not_block_after_tempesta_restart Apr 26 04:09:39 192.168.122.209 [43529.858816] [tdb] Start Tempesta DB Apr 26 04:09:39 192.168.122.209 [43529.998715] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:09:41 192.168.122.209 [43531.981984] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43531.981984] Maybe that's fine, but it's worth checking the [43531.981984] config - if there is no relations between the [43531.981984] names, then host name confusion attack is possible. Apr 26 04:09:41 192.168.122.209 [43532.146866] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:09:41 192.168.122.209 [43532.192785] [tempesta fw] Configuration processing is completed. Apr 26 04:09:41 192.168.122.209 [43532.248783] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:09:42 192.168.122.209 [43532.657721] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:09:42 192.168.122.209 [43532.683852] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:09:42 192.168.122.209 [43532.740023] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:09:42 192.168.122.209 [43532.804786] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:09:42 192.168.122.209 [43532.806550] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:09:42 192.168.122.209 [43532.852732] [tempesta fw] Tempesta FW is ready Apr 26 04:09:45 192.168.122.209 [43535.493543] [tdb] Close table 'client0.tdb' Apr 26 04:09:45 192.168.122.209 [43535.692112] [tdb] Close table 'sessions0.tdb' Apr 26 04:09:48 192.168.122.209 [43538.822619] [tdb] Close table 'cache0.tdb' Apr 26 04:09:48 192.168.122.209 [43539.058937] [tdb] Close table 'filter0.tdb' Apr 26 04:09:48 192.168.122.209 [43539.059345] [tempesta fw] modules are stopped Apr 26 04:09:48 192.168.122.209 [43539.258075] [tempesta fw] exiting... Apr 26 04:09:49 192.168.122.209 [43539.411148] [tdb] Shutdown Tempesta DB Apr 26 04:09:50 192.168.122.209 [43540.469205] [tdb] Start Tempesta DB Apr 26 04:09:50 192.168.122.209 [43540.606895] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:09:52 192.168.122.209 [43542.526133] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43542.526133] Maybe that's fine, but it's worth checking the [43542.526133] config - if there is no relations between the [43542.526133] names, then host name confusion attack is possible. Apr 26 04:09:52 192.168.122.209 [43542.690877] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:09:52 192.168.122.209 [43542.721252] [tempesta fw] Configuration processing is completed. Apr 26 04:09:52 192.168.122.209 [43542.772459] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:09:52 192.168.122.209 [43543.214892] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:09:52 192.168.122.209 [43543.242438] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:09:52 192.168.122.209 [43543.269751] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:09:52 192.168.122.209 [43543.344955] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:09:52 192.168.122.209 [43543.346724] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:09:53 192.168.122.209 [43543.420862] [tempesta fw] Tempesta FW is ready Apr 26 04:09:53 192.168.122.209 [43543.466404] [tempesta fw] Warning: http_sess: bad received HMAC value for 127.0.0.2 d(pos=0), ts=0x100a4e9e5 orig_hmac=[73fe0a96b7b7a8a23a940a315d9bd32e247b56c3] Apr 26 04:09:55 192.168.122.209 [43545.594565] [tdb] Close table 'client0.tdb' Apr 26 04:09:55 192.168.122.209 [43545.775050] [tdb] Close table 'sessions0.tdb' Apr 26 04:09:58 192.168.122.209 [43548.897024] [tdb] Close table 'cache0.tdb' Apr 26 04:09:58 192.168.122.209 [43549.123559] [tdb] Close table 'filter0.tdb' Apr 26 04:09:58 192.168.122.209 [43549.123983] [tempesta fw] modules are stopped Apr 26 04:09:59 192.168.122.209 [43549.361067] [tempesta fw] exiting... Apr 26 04:09:59 192.168.122.209 [43549.508011] [tdb] Shutdown Tempesta DB Apr 26 04:09:59 192.168.122.209 [43549.714382] End test: sessions.test_js_challenge.JSChallengeHttp.test_not_block_after_tempesta_restart Apr 26 04:09:59 192.168.122.209 [43549.725658] Start test: sessions.test_js_challenge.JSChallengeHttp.test_number_of_requests_is_greater_than_max_misses Apr 26 04:10:00 192.168.122.209 [43550.852608] [tdb] Start Tempesta DB Apr 26 04:10:00 192.168.122.209 [43551.013087] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:10:02 192.168.122.209 [43552.958404] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43552.958404] Maybe that's fine, but it's worth checking the [43552.958404] config - if there is no relations between the [43552.958404] names, then host name confusion attack is possible. Apr 26 04:10:02 192.168.122.209 [43553.135153] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:10:02 192.168.122.209 [43553.173096] [tempesta fw] Configuration processing is completed. Apr 26 04:10:02 192.168.122.209 [43553.225189] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:10:03 192.168.122.209 [43553.638900] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:10:03 192.168.122.209 [43553.664554] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:10:03 192.168.122.209 [43553.720708] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:10:03 192.168.122.209 [43553.785052] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:10:03 192.168.122.209 [43553.786767] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:10:03 192.168.122.209 [43553.825016] [tempesta fw] Tempesta FW is ready Apr 26 04:10:03 192.168.122.209 [43553.980245] [tempesta fw] Warning: frang: max rmisses exceeded for 127.0.0.2: 3 (lim=2) Apr 26 04:10:04 192.168.122.209 [43554.471111] [tdb] Close table 'client0.tdb' Apr 26 04:10:04 192.168.122.209 [43554.672247] [tdb] Close table 'sessions0.tdb' Apr 26 04:10:07 192.168.122.209 [43557.925126] [tdb] Close table 'cache0.tdb' Apr 26 04:10:07 192.168.122.209 [43558.172652] [tdb] Close table 'filter0.tdb' Apr 26 04:10:07 192.168.122.209 [43558.173119] [tempesta fw] modules are stopped Apr 26 04:10:08 192.168.122.209 [43558.423586] [tempesta fw] exiting... Apr 26 04:10:08 192.168.122.209 [43558.579244] [tdb] Shutdown Tempesta DB Apr 26 04:10:08 192.168.122.209 [43558.783735] End test: sessions.test_js_challenge.JSChallengeHttp.test_number_of_requests_is_greater_than_max_misses Apr 26 04:10:08 192.168.122.209 [43558.796536] Start test: sessions.test_js_challenge.JSChallengeHttp.test_resp_code_302 Apr 26 04:10:09 192.168.122.209 [43559.988570] [tdb] Start Tempesta DB Apr 26 04:10:09 192.168.122.209 [43560.163155] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:10:11 192.168.122.209 [43562.122407] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43562.122407] Maybe that's fine, but it's worth checking the [43562.122407] config - if there is no relations between the [43562.122407] names, then host name confusion attack is possible. Apr 26 04:10:11 192.168.122.209 [43562.299309] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:10:11 192.168.122.209 [43562.345161] [tempesta fw] Configuration processing is completed. Apr 26 04:10:12 192.168.122.209 [43562.402766] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:10:12 192.168.122.209 [43562.895107] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:10:12 192.168.122.209 [43562.926108] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:10:12 192.168.122.209 [43562.955742] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:10:12 192.168.122.209 [43563.001192] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:10:12 192.168.122.209 [43563.002928] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:10:12 192.168.122.209 [43563.045151] [tempesta fw] Tempesta FW is ready Apr 26 04:10:13 192.168.122.209 [43563.650377] [tdb] Close table 'client0.tdb' Apr 26 04:10:13 192.168.122.209 [43563.836881] [tdb] Close table 'sessions0.tdb' Apr 26 04:10:16 192.168.122.209 [43566.926938] [tdb] Close table 'cache0.tdb' Apr 26 04:10:16 192.168.122.209 [43567.161934] [tdb] Close table 'filter0.tdb' Apr 26 04:10:16 192.168.122.209 [43567.162363] [tempesta fw] modules are stopped Apr 26 04:10:17 192.168.122.209 [43567.362794] [tempesta fw] exiting... Apr 26 04:10:17 192.168.122.209 [43567.514874] [tdb] Shutdown Tempesta DB Apr 26 04:10:17 192.168.122.209 [43567.699889] End test: sessions.test_js_challenge.JSChallengeHttp.test_resp_code_302 Apr 26 04:10:17 192.168.122.209 [43567.708161] Start test: sessions.test_js_challenge.JSChallengeHttp.test_resp_code_403 Apr 26 04:10:18 192.168.122.209 [43568.775404] [tdb] Start Tempesta DB Apr 26 04:10:18 192.168.122.209 [43568.919829] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:10:20 192.168.122.209 [43570.822611] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43570.822611] Maybe that's fine, but it's worth checking the [43570.822611] config - if there is no relations between the [43570.822611] names, then host name confusion attack is possible. Apr 26 04:10:20 192.168.122.209 [43570.986044] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:10:20 192.168.122.209 [43571.033279] [tempesta fw] Configuration processing is completed. Apr 26 04:10:20 192.168.122.209 [43571.083311] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:10:21 192.168.122.209 [43571.486198] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:10:21 192.168.122.209 [43571.511519] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:10:21 192.168.122.209 [43571.573251] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:10:21 192.168.122.209 [43571.637292] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:10:21 192.168.122.209 [43571.639022] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:10:21 192.168.122.209 [43571.677227] [tempesta fw] Tempesta FW is ready Apr 26 04:10:21 192.168.122.209 [43572.202366] [tdb] Close table 'client0.tdb' Apr 26 04:10:22 192.168.122.209 [43572.391818] [tdb] Close table 'sessions0.tdb' Apr 26 04:10:25 192.168.122.209 [43575.611763] [tdb] Close table 'cache0.tdb' Apr 26 04:10:25 192.168.122.209 [43575.864384] [tdb] Close table 'filter0.tdb' Apr 26 04:10:25 192.168.122.209 [43575.864830] [tempesta fw] modules are stopped Apr 26 04:10:25 192.168.122.209 [43576.079818] [tempesta fw] exiting... Apr 26 04:10:25 192.168.122.209 [43576.266379] [tdb] Shutdown Tempesta DB Apr 26 04:10:26 192.168.122.209 [43576.480034] End test: sessions.test_js_challenge.JSChallengeHttp.test_resp_code_403 Apr 26 04:10:26 192.168.122.209 [43576.502809] Start test: sessions.test_js_challenge.JSChallengeHttp.test_resp_code_default Apr 26 04:10:27 192.168.122.209 [43577.697573] [tdb] Start Tempesta DB Apr 26 04:10:27 192.168.122.209 [43577.855711] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:10:29 192.168.122.209 [43579.882848] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43579.882848] Maybe that's fine, but it's worth checking the [43579.882848] config - if there is no relations between the [43579.882848] names, then host name confusion attack is possible. Apr 26 04:10:29 192.168.122.209 [43580.051397] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:10:29 192.168.122.209 [43580.089375] [tempesta fw] Configuration processing is completed. Apr 26 04:10:29 192.168.122.209 [43580.141393] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:10:30 192.168.122.209 [43580.604548] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:10:30 192.168.122.209 [43580.635827] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:10:30 192.168.122.209 [43580.667782] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:10:30 192.168.122.209 [43580.709393] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:10:30 192.168.122.209 [43580.711149] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:10:30 192.168.122.209 [43580.761340] [tempesta fw] Tempesta FW is ready Apr 26 04:10:30 192.168.122.209 [43581.346086] [tdb] Close table 'client0.tdb' Apr 26 04:10:31 192.168.122.209 [43581.536207] [tdb] Close table 'sessions0.tdb' Apr 26 04:10:34 192.168.122.209 [43584.718751] [tdb] Close table 'cache0.tdb' Apr 26 04:10:34 192.168.122.209 [43584.990528] [tdb] Close table 'filter0.tdb' Apr 26 04:10:34 192.168.122.209 [43584.990964] [tempesta fw] modules are stopped Apr 26 04:10:34 192.168.122.209 [43585.195326] [tempesta fw] exiting... Apr 26 04:10:34 192.168.122.209 [43585.313076] [tdb] Shutdown Tempesta DB Apr 26 04:10:35 192.168.122.209 [43585.527601] End test: sessions.test_js_challenge.JSChallengeHttp.test_resp_code_default Apr 26 04:10:35 192.168.122.209 [43585.552389] Start test: sessions.test_js_challenge.JSChallengeHttp.test_restart_js_challenge Apr 26 04:10:36 192.168.122.209 [43586.754846] [tdb] Start Tempesta DB Apr 26 04:10:36 192.168.122.209 [43586.901866] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:10:38 192.168.122.209 [43588.922808] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43588.922808] Maybe that's fine, but it's worth checking the [43588.922808] config - if there is no relations between the [43588.922808] names, then host name confusion attack is possible. Apr 26 04:10:38 192.168.122.209 [43589.083592] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:10:38 192.168.122.209 [43589.125561] [tempesta fw] Configuration processing is completed. Apr 26 04:10:38 192.168.122.209 [43589.176234] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:10:39 192.168.122.209 [43589.598229] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:10:39 192.168.122.209 [43589.624976] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:10:39 192.168.122.209 [43589.688255] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:10:39 192.168.122.209 [43589.733503] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:10:39 192.168.122.209 [43589.735257] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:10:39 192.168.122.209 [43589.773444] [tempesta fw] Tempesta FW is ready Apr 26 04:10:39 192.168.122.209 [43589.896506] [tempesta fw] Warning: http_sess: bad received HMAC value for 127.0.0.2 f(pos=0), ts=0x100116a72 orig_hmac=[dcd1a7be007d9b9ed7e259ffb8a858cb7d76cfd2] Apr 26 04:10:41 192.168.122.209 [43591.637219] [tdb] Close table 'client0.tdb' Apr 26 04:10:41 192.168.122.209 [43591.823002] [tdb] Close table 'sessions0.tdb' Apr 26 04:10:44 192.168.122.209 [43594.955790] [tdb] Close table 'cache0.tdb' Apr 26 04:10:44 192.168.122.209 [43595.189936] [tdb] Close table 'filter0.tdb' Apr 26 04:10:44 192.168.122.209 [43595.190363] [tempesta fw] modules are stopped Apr 26 04:10:45 192.168.122.209 [43595.369541] [tempesta fw] exiting... Apr 26 04:10:45 192.168.122.209 [43595.506698] [tdb] Shutdown Tempesta DB Apr 26 04:10:45 192.168.122.209 [43595.721809] End test: sessions.test_js_challenge.JSChallengeHttp.test_restart_js_challenge Apr 26 04:10:45 192.168.122.209 [43595.731266] Start test: sessions.test_js_challenge.JSChallengeHttp.test_second_request_GET_and_accept_all Apr 26 04:10:46 192.168.122.209 [43596.909930] [tdb] Start Tempesta DB Apr 26 04:10:46 192.168.122.209 [43597.057470] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:10:48 192.168.122.209 [43599.098885] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43599.098885] Maybe that's fine, but it's worth checking the [43599.098885] config - if there is no relations between the [43599.098885] names, then host name confusion attack is possible. Apr 26 04:10:48 192.168.122.209 [43599.279667] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:10:48 192.168.122.209 [43599.317643] [tempesta fw] Configuration processing is completed. Apr 26 04:10:49 192.168.122.209 [43599.367978] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:10:49 192.168.122.209 [43599.796704] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:10:49 192.168.122.209 [43599.830857] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:10:49 192.168.122.209 [43599.856802] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:10:49 192.168.122.209 [43599.905634] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:10:49 192.168.122.209 [43599.907458] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:10:49 192.168.122.209 [43599.953581] [tempesta fw] Tempesta FW is ready Apr 26 04:10:52 192.168.122.209 [43602.871231] [tdb] Close table 'client0.tdb' Apr 26 04:10:52 192.168.122.209 [43603.058791] [tdb] Close table 'sessions0.tdb' Apr 26 04:10:55 192.168.122.209 [43606.216617] [tdb] Close table 'cache0.tdb' Apr 26 04:10:56 192.168.122.209 [43606.457352] [tdb] Close table 'filter0.tdb' Apr 26 04:10:56 192.168.122.209 [43606.457810] [tempesta fw] modules are stopped Apr 26 04:10:56 192.168.122.209 [43606.649335] [tempesta fw] exiting... Apr 26 04:10:56 192.168.122.209 [43606.780372] [tdb] Shutdown Tempesta DB Apr 26 04:10:56 192.168.122.209 [43607.001195] End test: sessions.test_js_challenge.JSChallengeHttp.test_second_request_GET_and_accept_all Apr 26 04:10:56 192.168.122.209 [43607.013551] Start test: sessions.test_js_challenge.JSChallengeHttp.test_second_request_POST Apr 26 04:10:57 192.168.122.209 [43608.151841] [tdb] Start Tempesta DB Apr 26 04:10:57 192.168.122.209 [43608.300364] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:10:59 192.168.122.209 [43610.315030] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43610.315030] Maybe that's fine, but it's worth checking the [43610.315030] config - if there is no relations between the [43610.315030] names, then host name confusion attack is possible. Apr 26 04:11:00 192.168.122.209 [43610.475827] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:11:00 192.168.122.209 [43610.506041] [tempesta fw] Configuration processing is completed. Apr 26 04:11:00 192.168.122.209 [43610.555823] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:11:00 192.168.122.209 [43610.969377] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:11:00 192.168.122.209 [43610.996000] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:11:00 192.168.122.209 [43611.057699] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:11:00 192.168.122.209 [43611.097794] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:11:00 192.168.122.209 [43611.099545] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:11:00 192.168.122.209 [43611.145741] [tempesta fw] Tempesta FW is ready Apr 26 04:11:03 192.168.122.209 [43613.896293] [tdb] Close table 'client0.tdb' Apr 26 04:11:03 192.168.122.209 [43614.077019] [tdb] Close table 'sessions0.tdb' Apr 26 04:11:06 192.168.122.209 [43617.200124] [tdb] Close table 'cache0.tdb' Apr 26 04:11:07 192.168.122.209 [43617.440339] [tdb] Close table 'filter0.tdb' Apr 26 04:11:07 192.168.122.209 [43617.440771] [tempesta fw] modules are stopped Apr 26 04:11:07 192.168.122.209 [43617.643222] [tempesta fw] exiting... Apr 26 04:11:07 192.168.122.209 [43617.803981] [tdb] Shutdown Tempesta DB Apr 26 04:11:07 192.168.122.209 [43618.032029] End test: sessions.test_js_challenge.JSChallengeHttp.test_second_request_POST Apr 26 04:11:07 192.168.122.209 [43618.043291] Start test: sessions.test_js_challenge.JSChallengeHttp.test_servicing_non_challengeble_request_from_cache_GET Apr 26 04:11:08 192.168.122.209 [43619.214414] [tdb] Start Tempesta DB Apr 26 04:11:09 192.168.122.209 [43619.364024] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:11:11 192.168.122.209 [43621.367185] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43621.367185] Maybe that's fine, but it's worth checking the [43621.367185] config - if there is no relations between the [43621.367185] names, then host name confusion attack is possible. Apr 26 04:11:11 192.168.122.209 [43621.539946] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:11:11 192.168.122.209 [43621.581962] [tempesta fw] Configuration processing is completed. Apr 26 04:11:11 192.168.122.209 [43621.631853] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:11:11 192.168.122.209 [43622.059947] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:11:11 192.168.122.209 [43622.085629] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:11:11 192.168.122.209 [43622.111545] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:11:11 192.168.122.209 [43622.153948] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:11:11 192.168.122.209 [43622.155698] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:11:11 192.168.122.209 [43622.193870] [tempesta fw] Tempesta FW is ready Apr 26 04:11:14 192.168.122.209 [43624.719172] [tdb] Close table 'client0.tdb' Apr 26 04:11:14 192.168.122.209 [43624.900642] [tdb] Close table 'sessions0.tdb' Apr 26 04:11:17 192.168.122.209 [43628.037248] [tdb] Close table 'cache0.tdb' Apr 26 04:11:17 192.168.122.209 [43628.295612] [tdb] Close table 'filter0.tdb' Apr 26 04:11:17 192.168.122.209 [43628.296039] [tempesta fw] modules are stopped Apr 26 04:11:18 192.168.122.209 [43628.498245] [tempesta fw] exiting... Apr 26 04:11:18 192.168.122.209 [43628.648758] [tdb] Shutdown Tempesta DB Apr 26 04:11:18 192.168.122.209 [43628.875541] End test: sessions.test_js_challenge.JSChallengeHttp.test_servicing_non_challengeble_request_from_cache_GET Apr 26 04:11:18 192.168.122.209 [43628.883083] Start test: sessions.test_js_challenge.JSChallengeHttp.test_servicing_non_challengeble_request_from_cache_HEAD Apr 26 04:11:19 192.168.122.209 [43630.064660] [tdb] Start Tempesta DB Apr 26 04:11:19 192.168.122.209 [43630.224101] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:11:21 192.168.122.209 [43632.199344] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43632.199344] Maybe that's fine, but it's worth checking the [43632.199344] config - if there is no relations between the [43632.199344] names, then host name confusion attack is possible. Apr 26 04:11:22 192.168.122.209 [43632.364089] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:11:22 192.168.122.209 [43632.402075] [tempesta fw] Configuration processing is completed. Apr 26 04:11:22 192.168.122.209 [43632.456289] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:11:22 192.168.122.209 [43632.880704] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:11:22 192.168.122.209 [43632.906342] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:11:22 192.168.122.209 [43632.963471] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:11:22 192.168.122.209 [43633.010068] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:11:22 192.168.122.209 [43633.011796] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:11:22 192.168.122.209 [43633.050001] [tempesta fw] Tempesta FW is ready Apr 26 04:11:24 192.168.122.209 [43635.309704] [tdb] Close table 'client0.tdb' Apr 26 04:11:25 192.168.122.209 [43635.491184] [tdb] Close table 'sessions0.tdb' Apr 26 04:11:28 192.168.122.209 [43638.635259] [tdb] Close table 'cache0.tdb' Apr 26 04:11:28 192.168.122.209 [43638.860786] [tdb] Close table 'filter0.tdb' Apr 26 04:11:28 192.168.122.209 [43638.861226] [tempesta fw] modules are stopped Apr 26 04:11:28 192.168.122.209 [43639.066336] [tempesta fw] exiting... Apr 26 04:11:28 192.168.122.209 [43639.227528] [tdb] Shutdown Tempesta DB Apr 26 04:11:29 192.168.122.209 [43639.454288] End test: sessions.test_js_challenge.JSChallengeHttp.test_servicing_non_challengeble_request_from_cache_HEAD Apr 26 04:11:29 192.168.122.209 [43639.465157] Start test: sessions.test_js_challenge.JSChallengeHttp.test_servicing_non_challengeble_request_from_cache_POST Apr 26 04:11:30 192.168.122.209 [43640.639001] [tdb] Start Tempesta DB Apr 26 04:11:30 192.168.122.209 [43640.806638] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:11:32 192.168.122.209 [43642.791476] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43642.791476] Maybe that's fine, but it's worth checking the [43642.791476] config - if there is no relations between the [43642.791476] names, then host name confusion attack is possible. Apr 26 04:11:32 192.168.122.209 [43642.960244] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:11:32 192.168.122.209 [43642.998201] [tempesta fw] Configuration processing is completed. Apr 26 04:11:32 192.168.122.209 [43643.048056] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:11:33 192.168.122.209 [43643.463641] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:11:33 192.168.122.209 [43643.489434] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:11:33 192.168.122.209 [43643.515441] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:11:33 192.168.122.209 [43643.554192] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:11:33 192.168.122.209 [43643.555908] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:11:33 192.168.122.209 [43643.614136] [tempesta fw] Tempesta FW is ready Apr 26 04:11:35 192.168.122.209 [43645.485635] [tdb] Close table 'client0.tdb' Apr 26 04:11:35 192.168.122.209 [43645.685322] [tdb] Close table 'sessions0.tdb' Apr 26 04:11:38 192.168.122.209 [43648.819263] [tdb] Close table 'cache0.tdb' Apr 26 04:11:38 192.168.122.209 [43649.062362] [tdb] Close table 'filter0.tdb' Apr 26 04:11:38 192.168.122.209 [43649.062791] [tempesta fw] modules are stopped Apr 26 04:11:38 192.168.122.209 [43649.293809] [tempesta fw] exiting... Apr 26 04:11:39 192.168.122.209 [43649.431929] [tdb] Shutdown Tempesta DB Apr 26 04:11:39 192.168.122.209 [43649.638274] End test: sessions.test_js_challenge.JSChallengeHttp.test_servicing_non_challengeble_request_from_cache_POST Apr 26 04:11:39 192.168.122.209 [43649.653071] Start test: sessions.test_learn.LearnSessions.test_backend_fail Apr 26 04:11:40 192.168.122.209 [43650.804481] [tdb] Start Tempesta DB Apr 26 04:11:40 192.168.122.209 [43650.956747] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:11:42 192.168.122.209 [43652.358313] [tempesta fw] Configuration processing is completed. Apr 26 04:11:42 192.168.122.209 [43652.409440] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:11:42 192.168.122.209 [43652.828586] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:11:42 192.168.122.209 [43652.857597] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:11:42 192.168.122.209 [43652.913529] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:11:42 192.168.122.209 [43653.010321] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:11:42 192.168.122.209 [43653.078256] [tempesta fw] Tempesta FW is ready Apr 26 04:11:43 192.168.122.209 [43654.251399] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 04:11:43 192.168.122.209 [43654.254738] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 04:11:43 192.168.122.209 [43654.257385] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 04:11:43 192.168.122.209 [43654.260026] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 04:11:43 192.168.122.209 [43654.262659] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 04:11:43 192.168.122.209 [43654.265233] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 04:11:43 192.168.122.209 [43654.266371] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 04:11:43 192.168.122.209 [43654.267490] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 04:11:43 192.168.122.209 [43654.268612] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 04:11:43 192.168.122.209 [43654.269728] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 04:11:46 192.168.122.209 [43656.369712] [tdb] Close table 'client0.tdb' Apr 26 04:11:46 192.168.122.209 [43656.558060] [tdb] Close table 'sessions0.tdb' Apr 26 04:11:49 192.168.122.209 [43659.643043] [tdb] Close table 'cache0.tdb' Apr 26 04:11:49 192.168.122.209 [43659.863847] [tdb] Close table 'filter0.tdb' Apr 26 04:11:49 192.168.122.209 [43659.864286] net_ratelimit: 54 callbacks suppressed Apr 26 04:11:49 192.168.122.209 [43659.864287] [tempesta fw] modules are stopped Apr 26 04:11:49 192.168.122.209 [43660.051882] [tempesta fw] exiting... Apr 26 04:11:49 192.168.122.209 [43660.196983] [tdb] Shutdown Tempesta DB Apr 26 04:11:50 192.168.122.209 [43660.414877] End test: sessions.test_learn.LearnSessions.test_backend_fail Apr 26 04:11:50 192.168.122.209 [43660.426052] Start test: sessions.test_learn.LearnSessions.test_sessions Apr 26 04:11:51 192.168.122.209 [43661.569921] [tdb] Start Tempesta DB Apr 26 04:11:51 192.168.122.209 [43661.724013] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:11:52 192.168.122.209 [43663.118576] [tempesta fw] Configuration processing is completed. Apr 26 04:11:52 192.168.122.209 [43663.171638] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:11:53 192.168.122.209 [43663.612529] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:11:53 192.168.122.209 [43663.639221] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:11:53 192.168.122.209 [43663.665881] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:11:53 192.168.122.209 [43663.718369] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:11:53 192.168.122.209 [43663.806390] [tempesta fw] Tempesta FW is ready Apr 26 04:11:54 192.168.122.209 [43665.194202] [tdb] Close table 'client0.tdb' Apr 26 04:11:55 192.168.122.209 [43665.381306] [tdb] Close table 'sessions0.tdb' Apr 26 04:11:58 192.168.122.209 [43668.496286] [tdb] Close table 'cache0.tdb' Apr 26 04:11:58 192.168.122.209 [43668.719340] [tdb] Close table 'filter0.tdb' Apr 26 04:11:58 192.168.122.209 [43668.719777] [tempesta fw] modules are stopped Apr 26 04:11:58 192.168.122.209 [43668.910740] [tempesta fw] exiting... Apr 26 04:11:58 192.168.122.209 [43669.045086] [tdb] Shutdown Tempesta DB Apr 26 04:11:58 192.168.122.209 [43669.304045] End test: sessions.test_learn.LearnSessions.test_sessions Apr 26 04:11:58 192.168.122.209 [43669.312509] Start test: sessions.test_learn.LearnSessionsMultipleDiffSetCookie.test_backend_fail Apr 26 04:12:00 192.168.122.209 [43670.485916] [tdb] Start Tempesta DB Apr 26 04:12:00 192.168.122.209 [43670.626053] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:12:01 192.168.122.209 [43671.990624] [tempesta fw] Configuration processing is completed. Apr 26 04:12:01 192.168.122.209 [43672.047983] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:12:02 192.168.122.209 [43672.468737] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:12:02 192.168.122.209 [43672.494264] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:12:02 192.168.122.209 [43672.555305] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:12:02 192.168.122.209 [43672.642603] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:12:02 192.168.122.209 [43672.694505] [tempesta fw] Tempesta FW is ready Apr 26 04:12:03 192.168.122.209 [43673.849082] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 04:12:03 192.168.122.209 [43673.858279] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 04:12:03 192.168.122.209 [43673.861079] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 04:12:03 192.168.122.209 [43673.863755] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 04:12:03 192.168.122.209 [43673.865890] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 04:12:03 192.168.122.209 [43673.867973] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 04:12:03 192.168.122.209 [43673.870080] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 04:12:03 192.168.122.209 [43673.872169] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 04:12:03 192.168.122.209 [43673.873945] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 04:12:03 192.168.122.209 [43673.874816] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 04:12:05 192.168.122.209 [43675.931506] [tdb] Close table 'client0.tdb' Apr 26 04:12:05 192.168.122.209 [43676.113214] [tdb] Close table 'sessions0.tdb' Apr 26 04:12:08 192.168.122.209 [43679.220757] [tdb] Close table 'cache0.tdb' Apr 26 04:12:09 192.168.122.209 [43679.453146] [tdb] Close table 'filter0.tdb' Apr 26 04:12:09 192.168.122.209 [43679.453601] net_ratelimit: 54 callbacks suppressed Apr 26 04:12:09 192.168.122.209 [43679.453602] [tempesta fw] modules are stopped Apr 26 04:12:09 192.168.122.209 [43679.617635] [tempesta fw] exiting... Apr 26 04:12:09 192.168.122.209 [43679.739550] [tdb] Shutdown Tempesta DB Apr 26 04:12:09 192.168.122.209 [43679.973743] End test: sessions.test_learn.LearnSessionsMultipleDiffSetCookie.test_backend_fail Apr 26 04:12:09 192.168.122.209 [43679.984849] Start test: sessions.test_learn.LearnSessionsMultipleDiffSetCookie.test_sessions Apr 26 04:12:10 192.168.122.209 [43681.136950] [tdb] Start Tempesta DB Apr 26 04:12:10 192.168.122.209 [43681.283185] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:12:12 192.168.122.209 [43682.618754] [tempesta fw] Configuration processing is completed. Apr 26 04:12:12 192.168.122.209 [43682.671348] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:12:12 192.168.122.209 [43683.107062] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:12:12 192.168.122.209 [43683.134080] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:12:12 192.168.122.209 [43683.161080] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:12:12 192.168.122.209 [43683.222701] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:12:12 192.168.122.209 [43683.266673] [tempesta fw] Tempesta FW is ready Apr 26 04:12:14 192.168.122.209 [43684.669685] [tdb] Close table 'client0.tdb' Apr 26 04:12:14 192.168.122.209 [43684.860431] [tdb] Close table 'sessions0.tdb' Apr 26 04:12:17 192.168.122.209 [43687.952389] [tdb] Close table 'cache0.tdb' Apr 26 04:12:17 192.168.122.209 [43688.203091] [tdb] Close table 'filter0.tdb' Apr 26 04:12:17 192.168.122.209 [43688.203515] [tempesta fw] modules are stopped Apr 26 04:12:18 192.168.122.209 [43688.425790] [tempesta fw] exiting... Apr 26 04:12:18 192.168.122.209 [43688.556741] [tdb] Shutdown Tempesta DB Apr 26 04:12:18 192.168.122.209 [43688.757456] End test: sessions.test_learn.LearnSessionsMultipleDiffSetCookie.test_sessions Apr 26 04:12:18 192.168.122.209 [43688.769717] Start test: sessions.test_learn.LearnSessionsMultipleSameSetCookie.test Apr 26 04:12:19 192.168.122.209 [43690.032942] [tdb] Start Tempesta DB Apr 26 04:12:19 192.168.122.209 [43690.181659] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:12:21 192.168.122.209 [43691.510869] [tempesta fw] Configuration processing is completed. Apr 26 04:12:21 192.168.122.209 [43691.559538] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:12:21 192.168.122.209 [43691.975806] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:12:21 192.168.122.209 [43692.002146] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:12:21 192.168.122.209 [43692.064151] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:12:21 192.168.122.209 [43692.106838] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:12:21 192.168.122.209 [43692.146779] [tempesta fw] Tempesta FW is ready Apr 26 04:12:21 192.168.122.209 [43692.284198] [tempesta fw] Warning: Multiple sticky cookies found in response: 2 Apr 26 04:12:22 192.168.122.209 [43692.812615] [tdb] Close table 'client0.tdb' Apr 26 04:12:22 192.168.122.209 [43693.008234] [tdb] Close table 'sessions0.tdb' Apr 26 04:12:26 192.168.122.209 [43696.393461] [tdb] Close table 'cache0.tdb' Apr 26 04:12:26 192.168.122.209 [43696.622234] [tdb] Close table 'filter0.tdb' Apr 26 04:12:26 192.168.122.209 [43696.623436] [tempesta fw] modules are stopped Apr 26 04:12:26 192.168.122.209 [43696.797841] [tempesta fw] exiting... Apr 26 04:12:26 192.168.122.209 [43696.911365] [tdb] Shutdown Tempesta DB Apr 26 04:12:26 192.168.122.209 [43697.124504] End test: sessions.test_learn.LearnSessionsMultipleSameSetCookie.test Apr 26 04:12:26 192.168.122.209 [43697.140019] Start test: sessions.test_learn.LearnSessionsVhost.test_backend_fail Apr 26 04:12:27 192.168.122.209 [43698.341563] [tdb] Start Tempesta DB Apr 26 04:12:28 192.168.122.209 [43698.496987] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:12:30 192.168.122.209 [43700.491014] [tempesta fw] Configuration processing is completed. Apr 26 04:12:30 192.168.122.209 [43700.541724] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:12:30 192.168.122.209 [43700.972495] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:12:30 192.168.122.209 [43700.998207] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:12:30 192.168.122.209 [43701.024040] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:12:30 192.168.122.209 [43701.074870] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:12:30 192.168.122.209 [43701.114927] [tempesta fw] Tempesta FW is ready Apr 26 04:12:31 192.168.122.209 [43702.292928] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 04:12:31 192.168.122.209 [43702.304935] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 04:12:31 192.168.122.209 [43702.306386] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 04:12:31 192.168.122.209 [43702.307404] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 04:12:31 192.168.122.209 [43702.308354] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 04:12:31 192.168.122.209 [43702.309293] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 04:12:31 192.168.122.209 [43702.310244] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 04:12:31 192.168.122.209 [43702.311199] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 04:12:31 192.168.122.209 [43702.312138] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 04:12:31 192.168.122.209 [43702.313077] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 04:12:34 192.168.122.209 [43704.409852] [tdb] Close table 'client0.tdb' Apr 26 04:12:34 192.168.122.209 [43704.592360] [tdb] Close table 'sessions0.tdb' Apr 26 04:12:37 192.168.122.209 [43707.651284] [tdb] Close table 'cache0.tdb' Apr 26 04:12:37 192.168.122.209 [43707.866516] [tdb] Close table 'filter0.tdb' Apr 26 04:12:37 192.168.122.209 [43707.866978] net_ratelimit: 54 callbacks suppressed Apr 26 04:12:37 192.168.122.209 [43707.866979] [tempesta fw] modules are stopped Apr 26 04:12:37 192.168.122.209 [43708.077101] [tempesta fw] exiting... Apr 26 04:12:37 192.168.122.209 [43708.246656] [tdb] Shutdown Tempesta DB Apr 26 04:12:38 192.168.122.209 [43708.474257] End test: sessions.test_learn.LearnSessionsVhost.test_backend_fail Apr 26 04:12:38 192.168.122.209 [43708.483201] Start test: sessions.test_learn.LearnSessionsVhost.test_sessions Apr 26 04:12:39 192.168.122.209 [43709.621530] [tdb] Start Tempesta DB Apr 26 04:12:39 192.168.122.209 [43709.772501] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:12:41 192.168.122.209 [43711.615136] [tempesta fw] Configuration processing is completed. Apr 26 04:12:41 192.168.122.209 [43711.669324] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:12:41 192.168.122.209 [43712.081131] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:12:41 192.168.122.209 [43712.107225] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:12:41 192.168.122.209 [43712.164755] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:12:41 192.168.122.209 [43712.215008] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:12:41 192.168.122.209 [43712.259015] [tempesta fw] Tempesta FW is ready Apr 26 04:12:43 192.168.122.209 [43713.584479] [tdb] Close table 'client0.tdb' Apr 26 04:12:43 192.168.122.209 [43713.771984] [tdb] Close table 'sessions0.tdb' Apr 26 04:12:46 192.168.122.209 [43716.839137] [tdb] Close table 'cache0.tdb' Apr 26 04:12:46 192.168.122.209 [43717.097321] [tdb] Close table 'filter0.tdb' Apr 26 04:12:46 192.168.122.209 [43717.097757] [tempesta fw] modules are stopped Apr 26 04:12:46 192.168.122.209 [43717.327343] [tempesta fw] exiting... Apr 26 04:12:47 192.168.122.209 [43717.463284] [tdb] Shutdown Tempesta DB Apr 26 04:12:47 192.168.122.209 [43717.687832] End test: sessions.test_learn.LearnSessionsVhost.test_sessions Apr 26 04:12:47 192.168.122.209 [43717.697116] Start test: sessions.test_sessions.StickySessions.test_sessions Apr 26 04:12:48 192.168.122.209 [43718.877883] [tdb] Start Tempesta DB Apr 26 04:12:48 192.168.122.209 [43719.016473] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:12:50 192.168.122.209 [43720.479235] [tempesta fw] Configuration processing is completed. Apr 26 04:12:50 192.168.122.209 [43720.542252] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:12:50 192.168.122.209 [43720.962953] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:12:50 192.168.122.209 [43720.988360] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:12:50 192.168.122.209 [43721.013894] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:12:50 192.168.122.209 [43721.071438] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:12:50 192.168.122.209 [43721.115132] [tempesta fw] Tempesta FW is ready Apr 26 04:12:52 192.168.122.209 [43722.476370] [tdb] Close table 'client0.tdb' Apr 26 04:12:52 192.168.122.209 [43722.662903] [tdb] Close table 'sessions0.tdb' Apr 26 04:12:55 192.168.122.209 [43725.777460] [tdb] Close table 'cache0.tdb' Apr 26 04:12:55 192.168.122.209 [43726.006284] [tdb] Close table 'filter0.tdb' Apr 26 04:12:55 192.168.122.209 [43726.006710] [tempesta fw] modules are stopped Apr 26 04:12:55 192.168.122.209 [43726.178186] [tempesta fw] exiting... Apr 26 04:12:55 192.168.122.209 [43726.307802] [tdb] Shutdown Tempesta DB Apr 26 04:12:56 192.168.122.209 [43726.521285] End test: sessions.test_sessions.StickySessions.test_sessions Apr 26 04:12:56 192.168.122.209 [43726.539781] Start test: sessions.test_sessions.StickySessionsFailover.test_sessions Apr 26 04:12:57 192.168.122.209 [43727.670348] [tdb] Start Tempesta DB Apr 26 04:12:57 192.168.122.209 [43727.835282] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:12:59 192.168.122.209 [43729.627391] [tempesta fw] Configuration processing is completed. Apr 26 04:12:59 192.168.122.209 [43729.680010] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:12:59 192.168.122.209 [43730.100509] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:12:59 192.168.122.209 [43730.126890] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:12:59 192.168.122.209 [43730.184273] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:12:59 192.168.122.209 [43730.295266] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:12:59 192.168.122.209 [43730.335986] [tempesta fw] Tempesta FW is ready Apr 26 04:13:01 192.168.122.209 [43731.490900] [tempesta fw] sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down, try find other server Apr 26 04:13:03 192.168.122.209 [43733.640657] [tdb] Close table 'client0.tdb' Apr 26 04:13:03 192.168.122.209 [43733.822550] [tdb] Close table 'sessions0.tdb' Apr 26 04:13:06 192.168.122.209 [43736.940171] [tdb] Close table 'cache0.tdb' Apr 26 04:13:06 192.168.122.209 [43737.169535] [tdb] Close table 'filter0.tdb' Apr 26 04:13:06 192.168.122.209 [43737.169966] [tempesta fw] modules are stopped Apr 26 04:13:07 192.168.122.209 [43737.401215] [tempesta fw] exiting... Apr 26 04:13:07 192.168.122.209 [43737.525060] [tdb] Shutdown Tempesta DB Apr 26 04:13:07 192.168.122.209 [43737.739314] End test: sessions.test_sessions.StickySessionsFailover.test_sessions Apr 26 04:13:07 192.168.122.209 [43737.750289] Start test: sessions.test_sessions.StickySessionsFailover.test_sessions_reserved_server Apr 26 04:13:08 192.168.122.209 [43738.873461] [tdb] Start Tempesta DB Apr 26 04:13:08 192.168.122.209 [43739.030082] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:13:10 192.168.122.209 [43740.695526] [tempesta fw] Configuration processing is completed. Apr 26 04:13:10 192.168.122.209 [43740.754353] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:13:10 192.168.122.209 [43741.174718] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:13:10 192.168.122.209 [43741.200824] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:13:10 192.168.122.209 [43741.226928] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:13:10 192.168.122.209 [43741.299439] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:13:10 192.168.122.209 [43741.339391] [tempesta fw] Tempesta FW is ready Apr 26 04:13:12 192.168.122.209 [43742.521894] [tempesta fw] sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down, try find other server Apr 26 04:13:14 192.168.122.209 [43744.708950] [tdb] Close table 'client0.tdb' Apr 26 04:13:14 192.168.122.209 [43744.892335] [tdb] Close table 'sessions0.tdb' Apr 26 04:13:17 192.168.122.209 [43747.971527] [tdb] Close table 'cache0.tdb' Apr 26 04:13:17 192.168.122.209 [43748.209517] [tdb] Close table 'filter0.tdb' Apr 26 04:13:17 192.168.122.209 [43748.209977] [tempesta fw] modules are stopped Apr 26 04:13:18 192.168.122.209 [43748.430817] [tempesta fw] exiting... Apr 26 04:13:18 192.168.122.209 [43748.557067] [tdb] Shutdown Tempesta DB Apr 26 04:13:18 192.168.122.209 [43748.745109] End test: sessions.test_sessions.StickySessionsFailover.test_sessions_reserved_server Apr 26 04:13:18 192.168.122.209 [43748.766702] Start test: sessions.test_sessions.StickySessionsFailoverVhost.test_sessions Apr 26 04:13:19 192.168.122.209 [43749.948115] [tdb] Start Tempesta DB Apr 26 04:13:19 192.168.122.209 [43750.089737] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:13:21 192.168.122.209 [43752.055640] [tempesta fw] Configuration processing is completed. Apr 26 04:13:21 192.168.122.209 [43752.107527] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:13:22 192.168.122.209 [43752.551271] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:13:22 192.168.122.209 [43752.579171] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:13:22 192.168.122.209 [43752.637684] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:13:22 192.168.122.209 [43752.719586] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:13:22 192.168.122.209 [43752.763547] [tempesta fw] Tempesta FW is ready Apr 26 04:13:23 192.168.122.209 [43753.930278] [tempesta fw] sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down, try find other server Apr 26 04:13:25 192.168.122.209 [43756.151530] [tdb] Close table 'client0.tdb' Apr 26 04:13:25 192.168.122.209 [43756.336795] [tdb] Close table 'sessions0.tdb' Apr 26 04:13:29 192.168.122.209 [43759.449259] [tdb] Close table 'cache0.tdb' Apr 26 04:13:29 192.168.122.209 [43759.703022] [tdb] Close table 'filter0.tdb' Apr 26 04:13:29 192.168.122.209 [43759.703499] [tempesta fw] modules are stopped Apr 26 04:13:29 192.168.122.209 [43759.922671] [tempesta fw] exiting... Apr 26 04:13:29 192.168.122.209 [43760.051666] [tdb] Shutdown Tempesta DB Apr 26 04:13:29 192.168.122.209 [43760.266868] End test: sessions.test_sessions.StickySessionsFailoverVhost.test_sessions Apr 26 04:13:29 192.168.122.209 [43760.273380] Start test: sessions.test_sessions.StickySessionsFailoverVhost.test_sessions_reserved_server Apr 26 04:13:31 192.168.122.209 [43761.366457] [tdb] Start Tempesta DB Apr 26 04:13:31 192.168.122.209 [43761.541549] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:13:33 192.168.122.209 [43763.507831] [tempesta fw] Configuration processing is completed. Apr 26 04:13:33 192.168.122.209 [43763.562260] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:13:33 192.168.122.209 [43764.060529] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:13:33 192.168.122.209 [43764.091176] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:13:33 192.168.122.209 [43764.122394] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:13:33 192.168.122.209 [43764.195773] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:13:33 192.168.122.209 [43764.243677] [tempesta fw] Tempesta FW is ready Apr 26 04:13:35 192.168.122.209 [43765.412877] [tempesta fw] sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down, try find other server Apr 26 04:13:37 192.168.122.209 [43767.652630] [tdb] Close table 'client0.tdb' Apr 26 04:13:37 192.168.122.209 [43767.862643] [tdb] Close table 'sessions0.tdb' Apr 26 04:13:40 192.168.122.209 [43770.986184] [tdb] Close table 'cache0.tdb' Apr 26 04:13:40 192.168.122.209 [43771.230597] [tdb] Close table 'filter0.tdb' Apr 26 04:13:40 192.168.122.209 [43771.231033] [tempesta fw] modules are stopped Apr 26 04:13:41 192.168.122.209 [43771.460090] [tempesta fw] exiting... Apr 26 04:13:41 192.168.122.209 [43771.633645] [tdb] Shutdown Tempesta DB Apr 26 04:13:41 192.168.122.209 [43771.851598] End test: sessions.test_sessions.StickySessionsFailoverVhost.test_sessions_reserved_server Apr 26 04:13:41 192.168.122.209 [43771.862963] Start test: sessions.test_sessions.StickySessionsPersistense.test_sessions Apr 26 04:13:42 192.168.122.209 [43772.973571] [tdb] Start Tempesta DB Apr 26 04:13:42 192.168.122.209 [43773.131724] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:13:44 192.168.122.209 [43774.975877] [tempesta fw] Configuration processing is completed. Apr 26 04:13:44 192.168.122.209 [43775.026366] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:13:45 192.168.122.209 [43775.436663] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:13:45 192.168.122.209 [43775.462654] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:13:45 192.168.122.209 [43775.519295] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:13:45 192.168.122.209 [43775.615911] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:13:45 192.168.122.209 [43775.663818] [tempesta fw] Tempesta FW is ready Apr 26 04:13:46 192.168.122.209 [43776.832114] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 04:13:46 192.168.122.209 [43776.842581] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 04:13:46 192.168.122.209 [43776.853199] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 04:13:46 192.168.122.209 [43776.863895] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 04:13:46 192.168.122.209 [43776.874575] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 04:13:46 192.168.122.209 [43776.885243] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 04:13:46 192.168.122.209 [43776.895927] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 04:13:46 192.168.122.209 [43776.906483] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 04:13:46 192.168.122.209 [43776.917102] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 04:13:46 192.168.122.209 [43776.927751] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 04:13:48 192.168.122.209 [43778.988887] [tdb] Close table 'client0.tdb' Apr 26 04:13:48 192.168.122.209 [43779.195138] [tdb] Close table 'sessions0.tdb' Apr 26 04:13:51 192.168.122.209 [43782.345782] [tdb] Close table 'cache0.tdb' Apr 26 04:13:52 192.168.122.209 [43782.584342] [tdb] Close table 'filter0.tdb' Apr 26 04:13:52 192.168.122.209 [43782.584771] net_ratelimit: 54 callbacks suppressed Apr 26 04:13:52 192.168.122.209 [43782.584772] [tempesta fw] modules are stopped Apr 26 04:13:52 192.168.122.209 [43782.790628] [tempesta fw] exiting... Apr 26 04:13:52 192.168.122.209 [43782.925409] [tdb] Shutdown Tempesta DB Apr 26 04:13:52 192.168.122.209 [43783.128581] End test: sessions.test_sessions.StickySessionsPersistense.test_sessions Apr 26 04:13:52 192.168.122.209 [43783.139319] Start test: sessions.test_sessions.StickySessionsPersistenseVhost.test_sessions Apr 26 04:13:53 192.168.122.209 [43784.308645] [tdb] Start Tempesta DB Apr 26 04:13:54 192.168.122.209 [43784.461713] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:13:56 192.168.122.209 [43786.460105] [tempesta fw] Configuration processing is completed. Apr 26 04:13:56 192.168.122.209 [43786.520868] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:13:56 192.168.122.209 [43786.955702] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:13:56 192.168.122.209 [43786.986786] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:13:56 192.168.122.209 [43787.023087] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:13:56 192.168.122.209 [43787.156034] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:13:56 192.168.122.209 [43787.223978] [tempesta fw] Tempesta FW is ready Apr 26 04:13:58 192.168.122.209 [43788.380780] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 04:13:58 192.168.122.209 [43788.391290] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 04:13:58 192.168.122.209 [43788.401980] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 04:13:58 192.168.122.209 [43788.412565] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 04:13:58 192.168.122.209 [43788.423338] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 04:13:58 192.168.122.209 [43788.433946] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 04:13:58 192.168.122.209 [43788.444553] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 04:13:58 192.168.122.209 [43788.455377] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 04:13:58 192.168.122.209 [43788.466674] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 04:13:58 192.168.122.209 [43788.476718] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 04:14:00 192.168.122.209 [43790.551665] [tdb] Close table 'client0.tdb' Apr 26 04:14:00 192.168.122.209 [43790.733597] [tdb] Close table 'sessions0.tdb' Apr 26 04:14:03 192.168.122.209 [43793.890950] [tdb] Close table 'cache0.tdb' Apr 26 04:14:03 192.168.122.209 [43794.131935] [tdb] Close table 'filter0.tdb' Apr 26 04:14:03 192.168.122.209 [43794.132388] net_ratelimit: 54 callbacks suppressed Apr 26 04:14:03 192.168.122.209 [43794.132390] [tempesta fw] modules are stopped Apr 26 04:14:04 192.168.122.209 [43794.363459] [tempesta fw] exiting... Apr 26 04:14:04 192.168.122.209 [43794.505033] [tdb] Shutdown Tempesta DB Apr 26 04:14:04 192.168.122.209 [43794.699064] End test: sessions.test_sessions.StickySessionsPersistenseVhost.test_sessions Apr 26 04:14:04 192.168.122.209 [43794.709723] Start test: sessions.test_sessions.StickySessionsVhost.test_sessions Apr 26 04:14:05 192.168.122.209 [43795.851956] [tdb] Start Tempesta DB Apr 26 04:14:05 192.168.122.209 [43796.013091] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:14:07 192.168.122.209 [43797.820225] [tempesta fw] Configuration processing is completed. Apr 26 04:14:07 192.168.122.209 [43797.874224] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:14:07 192.168.122.209 [43798.309498] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:14:07 192.168.122.209 [43798.336567] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:14:08 192.168.122.209 [43798.400329] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:14:08 192.168.122.209 [43798.452038] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:14:08 192.168.122.209 [43798.496104] [tempesta fw] Tempesta FW is ready Apr 26 04:14:09 192.168.122.209 [43799.838667] [tdb] Close table 'client0.tdb' Apr 26 04:14:09 192.168.122.209 [43800.031774] [tdb] Close table 'sessions0.tdb' Apr 26 04:14:12 192.168.122.209 [43803.191552] [tdb] Close table 'cache0.tdb' Apr 26 04:14:13 192.168.122.209 [43803.428399] [tdb] Close table 'filter0.tdb' Apr 26 04:14:13 192.168.122.209 [43803.428836] [tempesta fw] modules are stopped Apr 26 04:14:13 192.168.122.209 [43803.666003] [tempesta fw] exiting... Apr 26 04:14:13 192.168.122.209 [43803.791197] [tdb] Shutdown Tempesta DB Apr 26 04:14:13 192.168.122.209 [43804.038976] End test: sessions.test_sessions.StickySessionsVhost.test_sessions Apr 26 04:14:13 192.168.122.209 [43804.050393] Start test: sessions.test_sticky_sess_stress.LotOfClients.test Apr 26 04:14:15 192.168.122.209 [43806.196639] [tdb] Start Tempesta DB Apr 26 04:14:15 192.168.122.209 [43806.351664] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:14:18 192.168.122.209 [43809.224384] [tempesta fw] Configuration processing is completed. Apr 26 04:14:18 192.168.122.209 [43809.283518] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:14:18 192.168.122.209 [43809.314656] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:14:18 192.168.122.209 [43809.345153] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:14:19 192.168.122.209 [43810.084303] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:14:19 192.168.122.209 [43810.132267] [tempesta fw] Tempesta FW is ready Apr 26 04:14:31 192.168.122.209 [43822.021712] [tdb] Close table 'client0.tdb' Apr 26 04:14:31 192.168.122.209 [43822.247508] [tdb] Close table 'sessions0.tdb' Apr 26 04:14:32 192.168.122.209 [43822.494058] [tdb] Close table 'filter0.tdb' Apr 26 04:14:32 192.168.122.209 [43822.494508] [tempesta fw] modules are stopped Apr 26 04:14:32 192.168.122.209 [43822.649751] [tempesta fw] exiting... Apr 26 04:14:32 192.168.122.209 [43822.777031] [tdb] Shutdown Tempesta DB Apr 26 04:14:33 192.168.122.209 [43823.852538] End test: sessions.test_sticky_sess_stress.LotOfClients.test Apr 26 04:14:33 192.168.122.209 [43823.865391] Start test: sessions.test_sticky_sess_stress.OneClient.test Apr 26 04:14:35 192.168.122.209 [43826.175572] [tdb] Start Tempesta DB Apr 26 04:14:35 192.168.122.209 [43826.315325] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:14:37 192.168.122.209 [43828.340664] [tempesta fw] Configuration processing is completed. Apr 26 04:14:38 192.168.122.209 [43828.396805] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:14:38 192.168.122.209 [43828.425685] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:14:38 192.168.122.209 [43828.454398] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:14:38 192.168.122.209 [43829.016571] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:14:38 192.168.122.209 [43829.052504] [tempesta fw] Tempesta FW is ready Apr 26 04:14:51 192.168.122.209 [43841.635842] [tdb] Close table 'client0.tdb' Apr 26 04:14:51 192.168.122.209 [43841.826450] [tdb] Close table 'sessions0.tdb' Apr 26 04:14:51 192.168.122.209 [43842.071734] [tdb] Close table 'filter0.tdb' Apr 26 04:14:51 192.168.122.209 [43842.072176] [tempesta fw] modules are stopped Apr 26 04:14:51 192.168.122.209 [43842.253228] [tempesta fw] exiting... Apr 26 04:14:52 192.168.122.209 [43842.405321] [tdb] Shutdown Tempesta DB Apr 26 04:14:53 192.168.122.209 [43843.566337] End test: sessions.test_sticky_sess_stress.OneClient.test Apr 26 04:14:53 192.168.122.209 [43843.572718] Start test: t_access_log.test_access_log.AccessLogFrang.test_frang Apr 26 04:14:54 192.168.122.209 [43844.755822] [tdb] Start Tempesta DB Apr 26 04:14:54 192.168.122.209 [43844.903514] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:14:55 192.168.122.209 [43845.564791] [tempesta fw] Configuration processing is completed. Apr 26 04:14:55 192.168.122.209 [43845.618590] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:14:55 192.168.122.209 [43845.648967] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:14:55 192.168.122.209 [43845.677249] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:14:55 192.168.122.209 [43845.728721] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:14:55 192.168.122.209 [43845.768670] [tempesta fw] Tempesta FW is ready Apr 26 04:14:55 192.168.122.209 [43845.957219] [tempesta fw] Warning: frang: HTTP URI length exceeded for 127.0.0.2: 27 (lim=10) Apr 26 04:14:55 192.168.122.209 [43845.958191] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:14:55 192.168.122.209 [43845.959027] [tempesta fw] 127.0.0.2 "default" "GET /longer-than-10-symbols-uri HTTP/1.1" 403 0 "referer" "user-agent" "ja5t=0" "ja5h=252000c01c0" Apr 26 04:14:56 192.168.122.209 [43846.465696] [tdb] Close table 'client0.tdb' Apr 26 04:14:56 192.168.122.209 [43846.662436] [tdb] Close table 'sessions0.tdb' Apr 26 04:14:56 192.168.122.209 [43846.885734] [tdb] Close table 'filter0.tdb' Apr 26 04:14:56 192.168.122.209 [43846.886156] [tempesta fw] modules are stopped Apr 26 04:14:56 192.168.122.209 [43847.069223] [tempesta fw] exiting... Apr 26 04:14:56 192.168.122.209 [43847.219158] [tdb] Shutdown Tempesta DB Apr 26 04:14:57 192.168.122.209 [43847.379424] End test: t_access_log.test_access_log.AccessLogFrang.test_frang Apr 26 04:14:57 192.168.122.209 [43847.401917] Start test: t_access_log.test_access_log.AccessLogTest.test_success_path_http1x Apr 26 04:14:58 192.168.122.209 [43848.592533] [tdb] Start Tempesta DB Apr 26 04:14:58 192.168.122.209 [43848.747133] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:14:59 192.168.122.209 [43849.592836] [tempesta fw] Configuration processing is completed. Apr 26 04:14:59 192.168.122.209 [43849.653512] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:14:59 192.168.122.209 [43849.681695] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:14:59 192.168.122.209 [43849.709404] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:14:59 192.168.122.209 [43849.752829] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:14:59 192.168.122.209 [43849.800764] [tempesta fw] Tempesta FW is ready Apr 26 04:14:59 192.168.122.209 [43849.967409] [tempesta fw] 127.0.0.2 "localhost" "GET /expect-status-200 HTTP/1.1" 200 12 "referer-code-string-200" "ua-code-string-200" "ja5t=0" "ja5h=266000c01c0" Apr 26 04:14:59 192.168.122.209 [43850.044925] [tempesta fw] 127.0.0.2 "localhost" "GET /expect-status-204 HTTP/1.1" 204 0 "referer-code-string-204" "ua-code-string-204" "ja5t=0" "ja5h=266000c01c0" Apr 26 04:14:59 192.168.122.209 [43850.118100] [tempesta fw] 127.0.0.2 "localhost" "GET /expect-status-302 HTTP/1.1" 302 13 "referer-code-string-302" "ua-code-string-302" "ja5t=0" "ja5h=266000c01c0" Apr 26 04:14:59 192.168.122.209 [43850.181171] [tempesta fw] 127.0.0.2 "localhost" "GET /expect-status-404 HTTP/1.1" 404 14 "referer-code-string-404" "ua-code-string-404" "ja5t=0" "ja5h=266000c01c0" Apr 26 04:14:59 192.168.122.209 [43850.274241] [tempesta fw] 127.0.0.2 "localhost" "GET /expect-status-500 HTTP/1.1" 500 26 "referer-code-string-500" "ua-code-string-500" "ja5t=0" "ja5h=266000c01c0" Apr 26 04:15:00 192.168.122.209 [43850.948405] [tdb] Close table 'client0.tdb' Apr 26 04:15:00 192.168.122.209 [43851.170650] [tdb] Close table 'sessions0.tdb' Apr 26 04:15:01 192.168.122.209 [43851.845247] [tdb] Close table 'filter0.tdb' Apr 26 04:15:01 192.168.122.209 [43851.845715] [tempesta fw] modules are stopped Apr 26 04:15:03 192.168.122.209 [43853.564486] [tempesta fw] exiting... Apr 26 04:15:03 192.168.122.209 [43853.891266] [tdb] Shutdown Tempesta DB Apr 26 04:15:04 192.168.122.209 [43854.360535] End test: t_access_log.test_access_log.AccessLogTest.test_success_path_http1x Apr 26 04:15:04 192.168.122.209 [43854.381263] Start test: t_access_log.test_access_log.AccessLogTest.test_uri_truncate Apr 26 04:15:05 192.168.122.209 [43855.618631] [tdb] Start Tempesta DB Apr 26 04:15:05 192.168.122.209 [43855.791349] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:15:06 192.168.122.209 [43857.237125] [tempesta fw] Configuration processing is completed. Apr 26 04:15:06 192.168.122.209 [43857.302592] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:15:06 192.168.122.209 [43857.340851] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:15:07 192.168.122.209 [43857.380526] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:15:07 192.168.122.209 [43857.420850] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:15:07 192.168.122.209 [43857.464857] [tempesta fw] Tempesta FW is ready Apr 26 04:15:07 192.168.122.209 [43857.640689] [tempesta fw] 127.0.0.2 "localhost" "GET /too-long-uri_111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111... HTTP/1.1" 200 0 "referer" "user-agent" "ja5t=0" "ja5h=252000c01c0" Apr 26 04:15:07 192.168.122.209 [43858.188231] [tdb] Close table 'client0.tdb' Apr 26 04:15:08 192.168.122.209 [43858.389722] [tdb] Close table 'sessions0.tdb' Apr 26 04:15:08 192.168.122.209 [43858.620922] [tdb] Close table 'filter0.tdb' Apr 26 04:15:08 192.168.122.209 [43858.621379] [tempesta fw] modules are stopped Apr 26 04:15:08 192.168.122.209 [43858.820959] [tempesta fw] exiting... Apr 26 04:15:08 192.168.122.209 [43858.965046] [tdb] Shutdown Tempesta DB Apr 26 04:15:08 192.168.122.209 [43859.174872] End test: t_access_log.test_access_log.AccessLogTest.test_uri_truncate Apr 26 04:15:08 192.168.122.209 [43859.186556] Start test: t_access_log.test_access_log_h2.FrangTest.test_tempesta Apr 26 04:15:10 192.168.122.209 [43860.519376] [tdb] Start Tempesta DB Apr 26 04:15:10 192.168.122.209 [43860.677006] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:15:11 192.168.122.209 [43861.414233] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43861.414233] Maybe that's fine, but it's worth checking the [43861.414233] config - if there is no relations between the [43861.414233] names, then host name confusion attack is possible. Apr 26 04:15:11 192.168.122.209 [43861.481021] [tempesta fw] Configuration processing is completed. Apr 26 04:15:11 192.168.122.209 [43861.533171] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:15:11 192.168.122.209 [43861.940542] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:15:11 192.168.122.209 [43862.000498] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:15:11 192.168.122.209 [43862.026117] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:15:11 192.168.122.209 [43862.108965] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:15:11 192.168.122.209 [43862.148938] [tempesta fw] Tempesta FW is ready Apr 26 04:15:11 192.168.122.209 [43862.320095] [tempesta fw] Warning: frang: HTTP URI length exceeded for 127.0.0.1: 32 (lim=10) Apr 26 04:15:11 192.168.122.209 [43862.321994] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.1 Apr 26 04:15:11 192.168.122.209 [43862.323499] [tempesta fw] 127.0.0.1 "default" "GET /some-uri-longer-than-10-symbols HTTP/2.0" 403 0 "http2-referer-403" "http2-user-agent-403" "ja5t=66cbf8ccef17001a" "ja5h=5b4cec5f008c03c0" Apr 26 04:15:12 192.168.122.209 [43862.927052] [tdb] Close table 'client0.tdb' Apr 26 04:15:12 192.168.122.209 [43863.126056] [tdb] Close table 'sessions0.tdb' Apr 26 04:15:15 192.168.122.209 [43866.345774] [tdb] Close table 'cache0.tdb' Apr 26 04:15:16 192.168.122.209 [43866.596692] [tdb] Close table 'filter0.tdb' Apr 26 04:15:16 192.168.122.209 [43866.597139] [tempesta fw] modules are stopped Apr 26 04:15:16 192.168.122.209 [43866.785876] [tempesta fw] exiting... Apr 26 04:15:16 192.168.122.209 [43866.935725] [tdb] Shutdown Tempesta DB Apr 26 04:15:16 192.168.122.209 [43867.239854] End test: t_access_log.test_access_log_h2.FrangTest.test_tempesta Apr 26 04:15:16 192.168.122.209 [43867.248393] Start test: t_access_log.test_access_log_h2.Response200Test.test_tempesta Apr 26 04:15:18 192.168.122.209 [43868.619730] [tdb] Start Tempesta DB Apr 26 04:15:18 192.168.122.209 [43868.781192] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:15:19 192.168.122.209 [43870.061797] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43870.061797] Maybe that's fine, but it's worth checking the [43870.061797] config - if there is no relations between the [43870.061797] names, then host name confusion attack is possible. Apr 26 04:15:19 192.168.122.209 [43870.133149] [tempesta fw] Configuration processing is completed. Apr 26 04:15:19 192.168.122.209 [43870.201027] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:15:20 192.168.122.209 [43870.766071] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:15:20 192.168.122.209 [43870.806198] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:15:20 192.168.122.209 [43870.840459] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:15:20 192.168.122.209 [43870.901077] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:15:20 192.168.122.209 [43870.957061] [tempesta fw] Tempesta FW is ready Apr 26 04:15:20 192.168.122.209 [43871.147030] [tempesta fw] 127.0.0.1 "default" "GET / HTTP/2.0" 200 0 "http2-referer-200" "http2-user-agent-200" "ja5t=66cbf8ccef17001a" "ja5h=5b4cec5f008c03c0" Apr 26 04:15:21 192.168.122.209 [43871.760452] [tdb] Close table 'client0.tdb' Apr 26 04:15:21 192.168.122.209 [43871.939020] [tdb] Close table 'sessions0.tdb' Apr 26 04:15:24 192.168.122.209 [43875.183362] [tdb] Close table 'cache0.tdb' Apr 26 04:15:25 192.168.122.209 [43875.448746] [tdb] Close table 'filter0.tdb' Apr 26 04:15:25 192.168.122.209 [43875.449555] [tempesta fw] modules are stopped Apr 26 04:15:25 192.168.122.209 [43875.630862] [tempesta fw] exiting... Apr 26 04:15:25 192.168.122.209 [43875.790372] [tdb] Shutdown Tempesta DB Apr 26 04:15:25 192.168.122.209 [43876.055587] End test: t_access_log.test_access_log_h2.Response200Test.test_tempesta Apr 26 04:15:25 192.168.122.209 [43876.073052] Start test: t_access_log.test_access_log_h2.Response204Test.test_tempesta Apr 26 04:15:27 192.168.122.209 [43877.541543] [tdb] Start Tempesta DB Apr 26 04:15:27 192.168.122.209 [43877.691650] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:15:28 192.168.122.209 [43879.050448] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43879.050448] Maybe that's fine, but it's worth checking the [43879.050448] config - if there is no relations between the [43879.050448] names, then host name confusion attack is possible. Apr 26 04:15:28 192.168.122.209 [43879.121265] [tempesta fw] Configuration processing is completed. Apr 26 04:15:28 192.168.122.209 [43879.182271] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:15:29 192.168.122.209 [43879.591155] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:15:29 192.168.122.209 [43879.617061] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:15:29 192.168.122.209 [43879.656940] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:15:29 192.168.122.209 [43879.745217] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:15:29 192.168.122.209 [43879.789143] [tempesta fw] Tempesta FW is ready Apr 26 04:15:29 192.168.122.209 [43879.986690] [tempesta fw] 127.0.0.1 "default" "GET / HTTP/2.0" 204 0 "http2-referer-204" "http2-user-agent-204" "ja5t=66cbf8ccef17001a" "ja5h=5b4cec5f008c03c0" Apr 26 04:15:30 192.168.122.209 [43880.613402] [tdb] Close table 'client0.tdb' Apr 26 04:15:30 192.168.122.209 [43880.828831] [tdb] Close table 'sessions0.tdb' Apr 26 04:15:33 192.168.122.209 [43883.979913] [tdb] Close table 'cache0.tdb' Apr 26 04:15:33 192.168.122.209 [43884.250934] [tdb] Close table 'filter0.tdb' Apr 26 04:15:33 192.168.122.209 [43884.251337] [tempesta fw] modules are stopped Apr 26 04:15:34 192.168.122.209 [43884.477509] [tempesta fw] exiting... Apr 26 04:15:34 192.168.122.209 [43884.626881] [tdb] Shutdown Tempesta DB Apr 26 04:15:34 192.168.122.209 [43884.868115] End test: t_access_log.test_access_log_h2.Response204Test.test_tempesta Apr 26 04:15:34 192.168.122.209 [43884.887022] Start test: t_access_log.test_access_log_h2.Response302Test.test_tempesta Apr 26 04:15:35 192.168.122.209 [43886.297024] [tdb] Start Tempesta DB Apr 26 04:15:36 192.168.122.209 [43886.461328] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:15:37 192.168.122.209 [43887.822545] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43887.822545] Maybe that's fine, but it's worth checking the [43887.822545] config - if there is no relations between the [43887.822545] names, then host name confusion attack is possible. Apr 26 04:15:37 192.168.122.209 [43887.893417] [tempesta fw] Configuration processing is completed. Apr 26 04:15:37 192.168.122.209 [43887.951981] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:15:38 192.168.122.209 [43888.376314] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:15:38 192.168.122.209 [43888.411510] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:15:38 192.168.122.209 [43888.437607] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:15:38 192.168.122.209 [43888.505313] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:15:38 192.168.122.209 [43888.553247] [tempesta fw] Tempesta FW is ready Apr 26 04:15:38 192.168.122.209 [43888.762534] [tempesta fw] 127.0.0.1 "default" "GET / HTTP/2.0" 302 154 "http2-referer-302" "http2-user-agent-302" "ja5t=66cbf8ccef17001a" "ja5h=5b4cec5f008c03c0" Apr 26 04:15:39 192.168.122.209 [43889.437546] [tdb] Close table 'client0.tdb' Apr 26 04:15:39 192.168.122.209 [43889.628922] [tdb] Close table 'sessions0.tdb' Apr 26 04:15:42 192.168.122.209 [43892.869611] [tdb] Close table 'cache0.tdb' Apr 26 04:15:42 192.168.122.209 [43893.127551] [tdb] Close table 'filter0.tdb' Apr 26 04:15:42 192.168.122.209 [43893.128009] [tempesta fw] modules are stopped Apr 26 04:15:42 192.168.122.209 [43893.314370] [tempesta fw] exiting... Apr 26 04:15:43 192.168.122.209 [43893.460837] [tdb] Shutdown Tempesta DB Apr 26 04:15:43 192.168.122.209 [43893.712191] End test: t_access_log.test_access_log_h2.Response302Test.test_tempesta Apr 26 04:15:43 192.168.122.209 [43893.720854] Start test: t_access_log.test_access_log_h2.Response404Test.test_tempesta Apr 26 04:15:44 192.168.122.209 [43895.151578] [tdb] Start Tempesta DB Apr 26 04:15:44 192.168.122.209 [43895.302685] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:15:46 192.168.122.209 [43896.726747] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43896.726747] Maybe that's fine, but it's worth checking the [43896.726747] config - if there is no relations between the [43896.726747] names, then host name confusion attack is possible. Apr 26 04:15:46 192.168.122.209 [43896.801483] [tempesta fw] Configuration processing is completed. Apr 26 04:15:46 192.168.122.209 [43896.861258] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:15:46 192.168.122.209 [43897.282912] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:15:46 192.168.122.209 [43897.309866] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:15:46 192.168.122.209 [43897.336699] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:15:47 192.168.122.209 [43897.405425] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:15:47 192.168.122.209 [43897.445368] [tempesta fw] Tempesta FW is ready Apr 26 04:15:47 192.168.122.209 [43897.625659] [tempesta fw] 127.0.0.1 "default" "GET / HTTP/2.0" 404 162 "http2-referer-404" "http2-user-agent-404" "ja5t=66cbf8ccef17001a" "ja5h=5b4cec5f008c03c0" Apr 26 04:15:47 192.168.122.209 [43898.281336] [tdb] Close table 'client0.tdb' Apr 26 04:15:48 192.168.122.209 [43898.482497] [tdb] Close table 'sessions0.tdb' Apr 26 04:15:51 192.168.122.209 [43901.639476] [tdb] Close table 'cache0.tdb' Apr 26 04:15:51 192.168.122.209 [43901.901263] [tdb] Close table 'filter0.tdb' Apr 26 04:15:51 192.168.122.209 [43901.902129] [tempesta fw] modules are stopped Apr 26 04:15:51 192.168.122.209 [43902.083682] [tempesta fw] exiting... Apr 26 04:15:51 192.168.122.209 [43902.257601] [tdb] Shutdown Tempesta DB Apr 26 04:15:52 192.168.122.209 [43902.498865] End test: t_access_log.test_access_log_h2.Response404Test.test_tempesta Apr 26 04:15:52 192.168.122.209 [43902.522406] Start test: t_access_log.test_access_log_h2.Response500Test.test_tempesta Apr 26 04:15:53 192.168.122.209 [43903.923506] [tdb] Start Tempesta DB Apr 26 04:15:53 192.168.122.209 [43904.083483] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:15:55 192.168.122.209 [43905.406790] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43905.406790] Maybe that's fine, but it's worth checking the [43905.406790] config - if there is no relations between the [43905.406790] names, then host name confusion attack is possible. Apr 26 04:15:55 192.168.122.209 [43905.477980] [tempesta fw] Configuration processing is completed. Apr 26 04:15:55 192.168.122.209 [43905.537572] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:15:55 192.168.122.209 [43906.110828] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:15:55 192.168.122.209 [43906.145756] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:15:55 192.168.122.209 [43906.180751] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:15:55 192.168.122.209 [43906.265557] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:15:55 192.168.122.209 [43906.313502] [tempesta fw] Tempesta FW is ready Apr 26 04:15:56 192.168.122.209 [43906.487296] [tempesta fw] 127.0.0.1 "default" "GET / HTTP/2.0" 500 186 "http2-referer-500" "http2-user-agent-500" "ja5t=66cbf8ccef17001a" "ja5h=5b4cec5f008c03c0" Apr 26 04:15:56 192.168.122.209 [43907.154687] [tdb] Close table 'client0.tdb' Apr 26 04:15:56 192.168.122.209 [43907.345693] [tdb] Close table 'sessions0.tdb' Apr 26 04:16:00 192.168.122.209 [43910.526134] [tdb] Close table 'cache0.tdb' Apr 26 04:16:00 192.168.122.209 [43910.766049] [tdb] Close table 'filter0.tdb' Apr 26 04:16:00 192.168.122.209 [43910.766499] [tempesta fw] modules are stopped Apr 26 04:16:00 192.168.122.209 [43910.969710] [tempesta fw] exiting... Apr 26 04:16:00 192.168.122.209 [43911.138174] [tdb] Shutdown Tempesta DB Apr 26 04:16:01 192.168.122.209 [43911.398654] End test: t_access_log.test_access_log_h2.Response500Test.test_tempesta Apr 26 04:16:01 192.168.122.209 [43911.408240] Start test: t_access_log.test_access_log_h2.TruncateUriTest.test_tempesta Apr 26 04:16:02 192.168.122.209 [43912.830321] [tdb] Start Tempesta DB Apr 26 04:16:02 192.168.122.209 [43912.995164] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:16:04 192.168.122.209 [43914.390926] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43914.390926] Maybe that's fine, but it's worth checking the [43914.390926] config - if there is no relations between the [43914.390926] names, then host name confusion attack is possible. Apr 26 04:16:04 192.168.122.209 [43914.461673] [tempesta fw] Configuration processing is completed. Apr 26 04:16:04 192.168.122.209 [43914.521806] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:16:04 192.168.122.209 [43915.072601] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:16:04 192.168.122.209 [43915.112827] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:16:04 192.168.122.209 [43915.139863] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:16:04 192.168.122.209 [43915.213635] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:16:04 192.168.122.209 [43915.257602] [tempesta fw] Tempesta FW is ready Apr 26 04:16:05 192.168.122.209 [43915.447246] [tempesta fw] 127.0.0.1 "default" "GET /truncated-uri_____________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________... HTTP/2.0" 200 0 "http2-referer-200" "http2-user-agent-200" "ja5t=66cbf8ccef17001a" "ja5h=5b4cec5f008c03c0" Apr 26 04:16:05 192.168.122.209 [43916.060503] [tdb] Close table 'client0.tdb' Apr 26 04:16:05 192.168.122.209 [43916.257911] [tdb] Close table 'sessions0.tdb' Apr 26 04:16:09 192.168.122.209 [43919.486972] [tdb] Close table 'cache0.tdb' Apr 26 04:16:09 192.168.122.209 [43919.755389] [tdb] Close table 'filter0.tdb' Apr 26 04:16:09 192.168.122.209 [43919.755839] [tempesta fw] modules are stopped Apr 26 04:16:09 192.168.122.209 [43919.931936] [tempesta fw] exiting... Apr 26 04:16:09 192.168.122.209 [43920.093817] [tdb] Shutdown Tempesta DB Apr 26 04:16:10 192.168.122.209 [43920.379121] End test: t_access_log.test_access_log_h2.TruncateUriTest.test_tempesta Apr 26 04:16:10 192.168.122.209 [43920.403217] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_boundary_values_0x40_from_0x41_to_0x7e Apr 26 04:16:11 192.168.122.209 [43921.741777] [tdb] Start Tempesta DB Apr 26 04:16:11 192.168.122.209 [43921.922701] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:16:12 192.168.122.209 [43923.339184] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43923.339184] Maybe that's fine, but it's worth checking the [43923.339184] config - if there is no relations between the [43923.339184] names, then host name confusion attack is possible. Apr 26 04:16:13 192.168.122.209 [43923.437763] [tempesta fw] Configuration processing is completed. Apr 26 04:16:13 192.168.122.209 [43923.488748] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:16:13 192.168.122.209 [43923.920163] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:16:13 192.168.122.209 [43923.947024] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:16:13 192.168.122.209 [43923.973759] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:16:13 192.168.122.209 [43924.041771] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:16:13 192.168.122.209 [43924.043489] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:16:13 192.168.122.209 [43924.081698] [tempesta fw] Tempesta FW is ready Apr 26 04:16:13 192.168.122.209 [43924.236918] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_Path input=0x65('example@'), len=9, off=1 Apr 26 04:16:14 192.168.122.209 [43924.724161] [tdb] Close table 'client0.tdb' Apr 26 04:16:14 192.168.122.209 [43924.928939] [tdb] Close table 'sessions0.tdb' Apr 26 04:16:17 192.168.122.209 [43928.077085] [tdb] Close table 'cache0.tdb' Apr 26 04:16:17 192.168.122.209 [43928.333595] [tdb] Close table 'filter0.tdb' Apr 26 04:16:17 192.168.122.209 [43928.334046] [tempesta fw] modules are stopped Apr 26 04:16:18 192.168.122.209 [43928.530291] [tempesta fw] exiting... Apr 26 04:16:18 192.168.122.209 [43928.715696] [tdb] Shutdown Tempesta DB Apr 26 04:16:18 192.168.122.209 [43928.923917] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_boundary_values_0x40_from_0x41_to_0x7e Apr 26 04:16:18 192.168.122.209 [43928.935216] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_boundary_values_0x41_from_0x41_to_0x7e Apr 26 04:16:19 192.168.122.209 [43930.140188] [tdb] Start Tempesta DB Apr 26 04:16:19 192.168.122.209 [43930.302593] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:16:21 192.168.122.209 [43931.655180] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43931.655180] Maybe that's fine, but it's worth checking the [43931.655180] config - if there is no relations between the [43931.655180] names, then host name confusion attack is possible. Apr 26 04:16:21 192.168.122.209 [43931.769909] [tempesta fw] Configuration processing is completed. Apr 26 04:16:21 192.168.122.209 [43931.822093] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:16:21 192.168.122.209 [43932.266600] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:16:21 192.168.122.209 [43932.293564] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:16:21 192.168.122.209 [43932.320593] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:16:22 192.168.122.209 [43932.377867] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:16:22 192.168.122.209 [43932.379583] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:16:22 192.168.122.209 [43932.425813] [tempesta fw] Tempesta FW is ready Apr 26 04:16:22 192.168.122.209 [43933.041225] [tdb] Close table 'client0.tdb' Apr 26 04:16:22 192.168.122.209 [43933.239330] [tdb] Close table 'sessions0.tdb' Apr 26 04:16:25 192.168.122.209 [43936.350612] [tdb] Close table 'cache0.tdb' Apr 26 04:16:26 192.168.122.209 [43936.575063] [tdb] Close table 'filter0.tdb' Apr 26 04:16:26 192.168.122.209 [43936.575494] [tempesta fw] modules are stopped Apr 26 04:16:26 192.168.122.209 [43936.747729] [tempesta fw] exiting... Apr 26 04:16:26 192.168.122.209 [43936.910716] [tdb] Shutdown Tempesta DB Apr 26 04:16:26 192.168.122.209 [43937.106561] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_boundary_values_0x41_from_0x41_to_0x7e Apr 26 04:16:26 192.168.122.209 [43937.131435] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_boundary_values_0x7e_from_0x41_to_0x7e Apr 26 04:16:27 192.168.122.209 [43938.235853] [tdb] Start Tempesta DB Apr 26 04:16:28 192.168.122.209 [43938.382541] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:16:29 192.168.122.209 [43939.735150] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43939.735150] Maybe that's fine, but it's worth checking the [43939.735150] config - if there is no relations between the [43939.735150] names, then host name confusion attack is possible. Apr 26 04:16:29 192.168.122.209 [43939.842001] [tempesta fw] Configuration processing is completed. Apr 26 04:16:29 192.168.122.209 [43939.899803] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:16:30 192.168.122.209 [43940.359574] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:16:30 192.168.122.209 [43940.387880] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:16:30 192.168.122.209 [43940.415901] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:16:30 192.168.122.209 [43940.473983] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:16:30 192.168.122.209 [43940.475656] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:16:30 192.168.122.209 [43940.521859] [tempesta fw] Tempesta FW is ready Apr 26 04:16:30 192.168.122.209 [43941.105345] [tdb] Close table 'client0.tdb' Apr 26 04:16:30 192.168.122.209 [43941.308282] [tdb] Close table 'sessions0.tdb' Apr 26 04:16:34 192.168.122.209 [43944.550462] [tdb] Close table 'cache0.tdb' Apr 26 04:16:34 192.168.122.209 [43944.797448] [tdb] Close table 'filter0.tdb' Apr 26 04:16:34 192.168.122.209 [43944.797906] [tempesta fw] modules are stopped Apr 26 04:16:34 192.168.122.209 [43945.007250] [tempesta fw] exiting... Apr 26 04:16:34 192.168.122.209 [43945.166912] [tdb] Shutdown Tempesta DB Apr 26 04:16:35 192.168.122.209 [43945.365299] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_boundary_values_0x7e_from_0x41_to_0x7e Apr 26 04:16:35 192.168.122.209 [43945.392294] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_boundary_values_0x7f_from_0x41_to_0x7e Apr 26 04:16:36 192.168.122.209 [43946.577647] [tdb] Start Tempesta DB Apr 26 04:16:36 192.168.122.209 [43946.728873] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:16:37 192.168.122.209 [43948.071336] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43948.071336] Maybe that's fine, but it's worth checking the [43948.071336] config - if there is no relations between the [43948.071336] names, then host name confusion attack is possible. Apr 26 04:16:37 192.168.122.209 [43948.187068] [tempesta fw] Configuration processing is completed. Apr 26 04:16:37 192.168.122.209 [43948.239371] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:16:38 192.168.122.209 [43948.718722] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:16:38 192.168.122.209 [43948.747479] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:16:38 192.168.122.209 [43948.776557] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:16:38 192.168.122.209 [43948.822082] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:16:38 192.168.122.209 [43948.823796] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:16:38 192.168.122.209 [43948.869994] [tempesta fw] Tempesta FW is ready Apr 26 04:16:38 192.168.122.209 [43949.008818] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_Path input=0x65('example'), len=10, off=1 Apr 26 04:16:39 192.168.122.209 [43949.442382] [tdb] Close table 'client0.tdb' Apr 26 04:16:39 192.168.122.209 [43949.664628] [tdb] Close table 'sessions0.tdb' Apr 26 04:16:42 192.168.122.209 [43952.935512] [tdb] Close table 'cache0.tdb' Apr 26 04:16:42 192.168.122.209 [43953.181602] [tdb] Close table 'filter0.tdb' Apr 26 04:16:42 192.168.122.209 [43953.182432] [tempesta fw] modules are stopped Apr 26 04:16:43 192.168.122.209 [43953.379367] [tempesta fw] exiting... Apr 26 04:16:43 192.168.122.209 [43953.509314] [tdb] Shutdown Tempesta DB Apr 26 04:16:43 192.168.122.209 [43953.717802] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_boundary_values_0x7f_from_0x41_to_0x7e Apr 26 04:16:43 192.168.122.209 [43953.726314] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_boundary_values_disallowed_0x5f Apr 26 04:16:44 192.168.122.209 [43954.884839] [tdb] Start Tempesta DB Apr 26 04:16:44 192.168.122.209 [43955.050936] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:16:46 192.168.122.209 [43956.475447] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43956.475447] Maybe that's fine, but it's worth checking the [43956.475447] config - if there is no relations between the [43956.475447] names, then host name confusion attack is possible. Apr 26 04:16:46 192.168.122.209 [43956.590187] [tempesta fw] Configuration processing is completed. Apr 26 04:16:46 192.168.122.209 [43956.651570] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:16:46 192.168.122.209 [43957.127733] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:16:46 192.168.122.209 [43957.156880] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:16:46 192.168.122.209 [43957.184072] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:16:46 192.168.122.209 [43957.234211] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:16:46 192.168.122.209 [43957.235876] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:16:46 192.168.122.209 [43957.274131] [tempesta fw] Tempesta FW is ready Apr 26 04:16:47 192.168.122.209 [43957.424945] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_Path input=0x65('example_'), len=9, off=1 Apr 26 04:16:47 192.168.122.209 [43957.891982] [tdb] Close table 'client0.tdb' Apr 26 04:16:47 192.168.122.209 [43958.105353] [tdb] Close table 'sessions0.tdb' Apr 26 04:16:51 192.168.122.209 [43961.383167] [tdb] Close table 'cache0.tdb' Apr 26 04:16:51 192.168.122.209 [43961.638388] [tdb] Close table 'filter0.tdb' Apr 26 04:16:51 192.168.122.209 [43961.638806] [tempesta fw] modules are stopped Apr 26 04:16:51 192.168.122.209 [43961.950124] [tempesta fw] exiting... Apr 26 04:16:51 192.168.122.209 [43962.104735] [tdb] Shutdown Tempesta DB Apr 26 04:16:51 192.168.122.209 [43962.331589] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_boundary_values_disallowed_0x5f Apr 26 04:16:51 192.168.122.209 [43962.347061] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_cookie_brange_allow_many_cookie Apr 26 04:16:53 192.168.122.209 [43963.573675] [tdb] Start Tempesta DB Apr 26 04:16:53 192.168.122.209 [43963.731460] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:16:54 192.168.122.209 [43965.107519] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43965.107519] Maybe that's fine, but it's worth checking the [43965.107519] config - if there is no relations between the [43965.107519] names, then host name confusion attack is possible. Apr 26 04:16:54 192.168.122.209 [43965.202258] [tempesta fw] Configuration processing is completed. Apr 26 04:16:54 192.168.122.209 [43965.254747] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:16:55 192.168.122.209 [43965.682186] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:16:55 192.168.122.209 [43965.708422] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:16:55 192.168.122.209 [43965.742972] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:16:55 192.168.122.209 [43965.782276] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:16:55 192.168.122.209 [43965.783966] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:16:55 192.168.122.209 [43965.834233] [tempesta fw] Tempesta FW is ready Apr 26 04:16:56 192.168.122.209 [43966.372725] [tdb] Close table 'client0.tdb' Apr 26 04:16:56 192.168.122.209 [43966.584289] [tdb] Close table 'sessions0.tdb' Apr 26 04:16:59 192.168.122.209 [43969.818992] [tdb] Close table 'cache0.tdb' Apr 26 04:16:59 192.168.122.209 [43970.080229] [tdb] Close table 'filter0.tdb' Apr 26 04:16:59 192.168.122.209 [43970.080680] [tempesta fw] modules are stopped Apr 26 04:16:59 192.168.122.209 [43970.290303] [tempesta fw] exiting... Apr 26 04:17:00 192.168.122.209 [43970.470490] [tdb] Shutdown Tempesta DB Apr 26 04:17:00 192.168.122.209 [43970.691085] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_cookie_brange_allow_many_cookie Apr 26 04:17:00 192.168.122.209 [43970.710741] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_cookie_brange_check_value Apr 26 04:17:01 192.168.122.209 [43971.930028] [tdb] Start Tempesta DB Apr 26 04:17:01 192.168.122.209 [43972.067893] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:17:03 192.168.122.209 [43973.519671] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43973.519671] Maybe that's fine, but it's worth checking the [43973.519671] config - if there is no relations between the [43973.519671] names, then host name confusion attack is possible. Apr 26 04:17:03 192.168.122.209 [43973.626507] [tempesta fw] Configuration processing is completed. Apr 26 04:17:03 192.168.122.209 [43973.676421] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:17:03 192.168.122.209 [43974.078979] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:17:03 192.168.122.209 [43974.135761] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:17:03 192.168.122.209 [43974.161551] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:17:03 192.168.122.209 [43974.250401] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:17:03 192.168.122.209 [43974.252145] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:17:03 192.168.122.209 [43974.290332] [tempesta fw] Tempesta FW is ready Apr 26 04:17:04 192.168.122.209 [43974.448852] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrCookieV input=0x69('id=QWErty'), len=9, off=0 Apr 26 04:17:04 192.168.122.209 [43974.896007] [tdb] Close table 'client0.tdb' Apr 26 04:17:04 192.168.122.209 [43975.101320] [tdb] Close table 'sessions0.tdb' Apr 26 04:17:07 192.168.122.209 [43978.231616] [tdb] Close table 'cache0.tdb' Apr 26 04:17:08 192.168.122.209 [43978.478975] [tdb] Close table 'filter0.tdb' Apr 26 04:17:08 192.168.122.209 [43978.479412] [tempesta fw] modules are stopped Apr 26 04:17:08 192.168.122.209 [43978.675220] [tempesta fw] exiting... Apr 26 04:17:08 192.168.122.209 [43978.841071] [tdb] Shutdown Tempesta DB Apr 26 04:17:08 192.168.122.209 [43979.058950] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_cookie_brange_check_value Apr 26 04:17:08 192.168.122.209 [43979.082766] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_cookie_brange_not_check_name Apr 26 04:17:09 192.168.122.209 [43980.286664] [tdb] Start Tempesta DB Apr 26 04:17:10 192.168.122.209 [43980.436904] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:17:11 192.168.122.209 [43981.799410] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43981.799410] Maybe that's fine, but it's worth checking the [43981.799410] config - if there is no relations between the [43981.799410] names, then host name confusion attack is possible. Apr 26 04:17:11 192.168.122.209 [43981.902497] [tempesta fw] Configuration processing is completed. Apr 26 04:17:11 192.168.122.209 [43981.953441] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:17:12 192.168.122.209 [43982.377176] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:17:12 192.168.122.209 [43982.404663] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:17:12 192.168.122.209 [43982.431748] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:17:12 192.168.122.209 [43982.474513] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:17:12 192.168.122.209 [43982.476211] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:17:12 192.168.122.209 [43982.518453] [tempesta fw] Tempesta FW is ready Apr 26 04:17:12 192.168.122.209 [43983.137124] [tdb] Close table 'client0.tdb' Apr 26 04:17:12 192.168.122.209 [43983.341446] [tdb] Close table 'sessions0.tdb' Apr 26 04:17:16 192.168.122.209 [43986.504897] [tdb] Close table 'cache0.tdb' Apr 26 04:17:16 192.168.122.209 [43986.733069] [tdb] Close table 'filter0.tdb' Apr 26 04:17:16 192.168.122.209 [43986.733497] [tempesta fw] modules are stopped Apr 26 04:17:16 192.168.122.209 [43986.914640] [tempesta fw] exiting... Apr 26 04:17:16 192.168.122.209 [43987.057446] [tdb] Shutdown Tempesta DB Apr 26 04:17:16 192.168.122.209 [43987.269031] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_cookie_brange_not_check_name Apr 26 04:17:16 192.168.122.209 [43987.281710] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_ctext_vchar_brange_allow Apr 26 04:17:18 192.168.122.209 [43988.453292] [tdb] Start Tempesta DB Apr 26 04:17:18 192.168.122.209 [43988.628349] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:17:19 192.168.122.209 [43989.939867] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43989.939867] Maybe that's fine, but it's worth checking the [43989.939867] config - if there is no relations between the [43989.939867] names, then host name confusion attack is possible. Apr 26 04:17:19 192.168.122.209 [43990.050642] [tempesta fw] Configuration processing is completed. Apr 26 04:17:19 192.168.122.209 [43990.102671] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:17:20 192.168.122.209 [43990.553186] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:17:20 192.168.122.209 [43990.620646] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:17:20 192.168.122.209 [43990.652356] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:17:20 192.168.122.209 [43990.698607] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:17:20 192.168.122.209 [43990.700273] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:17:20 192.168.122.209 [43990.754545] [tempesta fw] Tempesta FW is ready Apr 26 04:17:20 192.168.122.209 [43991.349803] [tdb] Close table 'client0.tdb' Apr 26 04:17:21 192.168.122.209 [43991.543809] [tdb] Close table 'sessions0.tdb' Apr 26 04:17:24 192.168.122.209 [43994.697439] [tdb] Close table 'cache0.tdb' Apr 26 04:17:24 192.168.122.209 [43994.937909] [tdb] Close table 'filter0.tdb' Apr 26 04:17:24 192.168.122.209 [43994.938334] [tempesta fw] modules are stopped Apr 26 04:17:24 192.168.122.209 [43995.139370] [tempesta fw] exiting... Apr 26 04:17:24 192.168.122.209 [43995.280084] [tdb] Shutdown Tempesta DB Apr 26 04:17:25 192.168.122.209 [43995.483977] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_ctext_vchar_brange_allow Apr 26 04:17:25 192.168.122.209 [43995.493447] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_ctext_vchar_brange_disallow Apr 26 04:17:26 192.168.122.209 [43996.665830] [tdb] Start Tempesta DB Apr 26 04:17:26 192.168.122.209 [43996.824404] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:17:27 192.168.122.209 [43998.272195] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [43998.272195] Maybe that's fine, but it's worth checking the [43998.272195] config - if there is no relations between the [43998.272195] names, then host name confusion attack is possible. Apr 26 04:17:28 192.168.122.209 [43998.370729] [tempesta fw] Configuration processing is completed. Apr 26 04:17:28 192.168.122.209 [43998.426953] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:17:28 192.168.122.209 [43998.860605] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:17:28 192.168.122.209 [43998.890871] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:17:28 192.168.122.209 [43998.918118] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:17:28 192.168.122.209 [43998.982709] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:17:28 192.168.122.209 [43998.984396] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:17:28 192.168.122.209 [43999.030648] [tempesta fw] Tempesta FW is ready Apr 26 04:17:28 192.168.122.209 [43999.169816] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrUser_AgentV input=0x4d('Mozilla/5.0 %'), len=13, off=0 Apr 26 04:17:29 192.168.122.209 [43999.597195] [tdb] Close table 'client0.tdb' Apr 26 04:17:29 192.168.122.209 [43999.824781] [tdb] Close table 'sessions0.tdb' Apr 26 04:17:32 192.168.122.209 [44002.930653] [tdb] Close table 'cache0.tdb' Apr 26 04:17:32 192.168.122.209 [44003.178541] [tdb] Close table 'filter0.tdb' Apr 26 04:17:32 192.168.122.209 [44003.179026] [tempesta fw] modules are stopped Apr 26 04:17:33 192.168.122.209 [44003.379955] [tempesta fw] exiting... Apr 26 04:17:33 192.168.122.209 [44003.548656] [tdb] Shutdown Tempesta DB Apr 26 04:17:33 192.168.122.209 [44003.780710] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_ctext_vchar_brange_disallow Apr 26 04:17:33 192.168.122.209 [44003.812602] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_etag_brange_if_none_match_allow Apr 26 04:17:34 192.168.122.209 [44004.997073] [tdb] Start Tempesta DB Apr 26 04:17:34 192.168.122.209 [44005.150425] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:17:36 192.168.122.209 [44006.628212] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44006.628212] Maybe that's fine, but it's worth checking the [44006.628212] config - if there is no relations between the [44006.628212] names, then host name confusion attack is possible. Apr 26 04:17:36 192.168.122.209 [44006.734863] [tempesta fw] Configuration processing is completed. Apr 26 04:17:36 192.168.122.209 [44006.794283] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:17:36 192.168.122.209 [44007.237300] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:17:36 192.168.122.209 [44007.265058] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:17:36 192.168.122.209 [44007.292649] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:17:36 192.168.122.209 [44007.338885] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:17:36 192.168.122.209 [44007.340596] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:17:37 192.168.122.209 [44007.374779] [tempesta fw] Tempesta FW is ready Apr 26 04:17:37 192.168.122.209 [44007.931331] [tdb] Close table 'client0.tdb' Apr 26 04:17:37 192.168.122.209 [44008.141436] [tdb] Close table 'sessions0.tdb' Apr 26 04:17:40 192.168.122.209 [44011.314768] [tdb] Close table 'cache0.tdb' Apr 26 04:17:41 192.168.122.209 [44011.543998] [tdb] Close table 'filter0.tdb' Apr 26 04:17:41 192.168.122.209 [44011.544443] [tempesta fw] modules are stopped Apr 26 04:17:41 192.168.122.209 [44011.755190] [tempesta fw] exiting... Apr 26 04:17:41 192.168.122.209 [44011.901310] [tdb] Shutdown Tempesta DB Apr 26 04:17:41 192.168.122.209 [44012.112591] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_etag_brange_if_none_match_allow Apr 26 04:17:41 192.168.122.209 [44012.127013] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_etag_brange_if_none_match_allow_all Apr 26 04:17:42 192.168.122.209 [44013.265720] [tdb] Start Tempesta DB Apr 26 04:17:43 192.168.122.209 [44013.425482] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:17:44 192.168.122.209 [44014.784211] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44014.784211] Maybe that's fine, but it's worth checking the [44014.784211] config - if there is no relations between the [44014.784211] names, then host name confusion attack is possible. Apr 26 04:17:44 192.168.122.209 [44014.886962] [tempesta fw] Configuration processing is completed. Apr 26 04:17:44 192.168.122.209 [44014.970750] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:17:45 192.168.122.209 [44015.436432] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:17:45 192.168.122.209 [44015.502576] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:17:45 192.168.122.209 [44015.530244] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:17:45 192.168.122.209 [44015.570929] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:17:45 192.168.122.209 [44015.572613] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:17:45 192.168.122.209 [44015.618885] [tempesta fw] Tempesta FW is ready Apr 26 04:17:45 192.168.122.209 [44016.210075] [tdb] Close table 'client0.tdb' Apr 26 04:17:46 192.168.122.209 [44016.377846] [tdb] Close table 'sessions0.tdb' Apr 26 04:17:49 192.168.122.209 [44019.568606] [tdb] Close table 'cache0.tdb' Apr 26 04:17:49 192.168.122.209 [44019.837316] [tdb] Close table 'filter0.tdb' Apr 26 04:17:49 192.168.122.209 [44019.837768] [tempesta fw] modules are stopped Apr 26 04:17:49 192.168.122.209 [44020.033641] [tempesta fw] exiting... Apr 26 04:17:49 192.168.122.209 [44020.176349] [tdb] Shutdown Tempesta DB Apr 26 04:17:50 192.168.122.209 [44020.396281] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_etag_brange_if_none_match_allow_all Apr 26 04:17:50 192.168.122.209 [44020.404778] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_etag_brange_if_none_match_allow_weak Apr 26 04:17:51 192.168.122.209 [44021.608753] [tdb] Start Tempesta DB Apr 26 04:17:51 192.168.122.209 [44021.771170] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:17:52 192.168.122.209 [44023.220262] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44023.220262] Maybe that's fine, but it's worth checking the [44023.220262] config - if there is no relations between the [44023.220262] names, then host name confusion attack is possible. Apr 26 04:17:52 192.168.122.209 [44023.319038] [tempesta fw] Configuration processing is completed. Apr 26 04:17:53 192.168.122.209 [44023.372319] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:17:53 192.168.122.209 [44023.834995] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:17:53 192.168.122.209 [44023.863539] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:17:53 192.168.122.209 [44023.891224] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:17:53 192.168.122.209 [44023.939035] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:17:53 192.168.122.209 [44023.940729] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:17:53 192.168.122.209 [44023.994968] [tempesta fw] Tempesta FW is ready Apr 26 04:17:54 192.168.122.209 [44024.606352] [tdb] Close table 'client0.tdb' Apr 26 04:17:54 192.168.122.209 [44024.806021] [tdb] Close table 'sessions0.tdb' Apr 26 04:17:57 192.168.122.209 [44028.022225] [tdb] Close table 'cache0.tdb' Apr 26 04:17:57 192.168.122.209 [44028.274031] [tdb] Close table 'filter0.tdb' Apr 26 04:17:57 192.168.122.209 [44028.274494] [tempesta fw] modules are stopped Apr 26 04:17:58 192.168.122.209 [44028.455384] [tempesta fw] exiting... Apr 26 04:17:58 192.168.122.209 [44028.636479] [tdb] Shutdown Tempesta DB Apr 26 04:17:58 192.168.122.209 [44028.861611] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_etag_brange_if_none_match_allow_weak Apr 26 04:17:58 192.168.122.209 [44028.877763] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_etag_brange_if_none_match_disallow Apr 26 04:17:59 192.168.122.209 [44030.149788] [tdb] Start Tempesta DB Apr 26 04:17:59 192.168.122.209 [44030.296216] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:18:01 192.168.122.209 [44031.696520] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44031.696520] Maybe that's fine, but it's worth checking the [44031.696520] config - if there is no relations between the [44031.696520] names, then host name confusion attack is possible. Apr 26 04:18:01 192.168.122.209 [44031.799190] [tempesta fw] Configuration processing is completed. Apr 26 04:18:01 192.168.122.209 [44031.851825] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:18:01 192.168.122.209 [44032.314201] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:18:02 192.168.122.209 [44032.391065] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:18:02 192.168.122.209 [44032.421800] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:18:02 192.168.122.209 [44032.519161] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:18:02 192.168.122.209 [44032.520863] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:18:02 192.168.122.209 [44032.559092] [tempesta fw] Tempesta FW is ready Apr 26 04:18:02 192.168.122.209 [44032.709849] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrIf_None_MatchV input=0x22('"asdfQWErty"'), len=12, off=0 Apr 26 04:18:02 192.168.122.209 [44033.269638] [tdb] Close table 'client0.tdb' Apr 26 04:18:03 192.168.122.209 [44033.461082] [tdb] Close table 'sessions0.tdb' Apr 26 04:18:06 192.168.122.209 [44036.579373] [tdb] Close table 'cache0.tdb' Apr 26 04:18:06 192.168.122.209 [44036.832596] [tdb] Close table 'filter0.tdb' Apr 26 04:18:06 192.168.122.209 [44036.833043] [tempesta fw] modules are stopped Apr 26 04:18:06 192.168.122.209 [44037.081007] [tempesta fw] exiting... Apr 26 04:18:06 192.168.122.209 [44037.217134] [tdb] Shutdown Tempesta DB Apr 26 04:18:07 192.168.122.209 [44037.458926] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_etag_brange_if_none_match_disallow Apr 26 04:18:07 192.168.122.209 [44037.482186] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_etag_brange_if_none_match_many_values Apr 26 04:18:08 192.168.122.209 [44038.695587] [tdb] Start Tempesta DB Apr 26 04:18:08 192.168.122.209 [44038.827437] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:18:09 192.168.122.209 [44040.204547] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44040.204547] Maybe that's fine, but it's worth checking the [44040.204547] config - if there is no relations between the [44040.204547] names, then host name confusion attack is possible. Apr 26 04:18:09 192.168.122.209 [44040.319264] [tempesta fw] Configuration processing is completed. Apr 26 04:18:10 192.168.122.209 [44040.371362] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:18:10 192.168.122.209 [44040.829272] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:18:10 192.168.122.209 [44040.856728] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:18:10 192.168.122.209 [44040.915237] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:18:10 192.168.122.209 [44040.955187] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:18:10 192.168.122.209 [44040.955958] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:18:10 192.168.122.209 [44040.999142] [tempesta fw] Tempesta FW is ready Apr 26 04:18:11 192.168.122.209 [44041.604379] [tdb] Close table 'client0.tdb' Apr 26 04:18:11 192.168.122.209 [44041.819534] [tdb] Close table 'sessions0.tdb' Apr 26 04:18:14 192.168.122.209 [44045.028347] [tdb] Close table 'cache0.tdb' Apr 26 04:18:14 192.168.122.209 [44045.286422] [tdb] Close table 'filter0.tdb' Apr 26 04:18:14 192.168.122.209 [44045.286860] [tempesta fw] modules are stopped Apr 26 04:18:15 192.168.122.209 [44045.461285] [tempesta fw] exiting... Apr 26 04:18:15 192.168.122.209 [44045.617715] [tdb] Shutdown Tempesta DB Apr 26 04:18:15 192.168.122.209 [44045.842519] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_etag_brange_if_none_match_many_values Apr 26 04:18:15 192.168.122.209 [44045.851058] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_nctl_brange_request_negative Apr 26 04:18:16 192.168.122.209 [44047.045212] [tdb] Start Tempesta DB Apr 26 04:18:16 192.168.122.209 [44047.199252] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:18:18 192.168.122.209 [44048.640655] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44048.640655] Maybe that's fine, but it's worth checking the [44048.640655] config - if there is no relations between the [44048.640655] names, then host name confusion attack is possible. Apr 26 04:18:18 192.168.122.209 [44048.727381] [tempesta fw] Configuration processing is completed. Apr 26 04:18:18 192.168.122.209 [44048.777551] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:18:18 192.168.122.209 [44049.193143] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:18:18 192.168.122.209 [44049.219013] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:18:18 192.168.122.209 [44049.245188] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:18:18 192.168.122.209 [44049.287344] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:18:18 192.168.122.209 [44049.289050] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:18:18 192.168.122.209 [44049.327307] [tempesta fw] Tempesta FW is ready Apr 26 04:18:19 192.168.122.209 [44049.478363] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrIf_Modified_SinceV input=0x4d('Mon, 12 Dec 2016'), len=30, off=0 Apr 26 04:18:19 192.168.122.209 [44049.946598] [tdb] Close table 'client0.tdb' Apr 26 04:18:19 192.168.122.209 [44050.137023] [tdb] Close table 'sessions0.tdb' Apr 26 04:18:22 192.168.122.209 [44053.305494] [tdb] Close table 'cache0.tdb' Apr 26 04:18:23 192.168.122.209 [44053.551932] [tdb] Close table 'filter0.tdb' Apr 26 04:18:23 192.168.122.209 [44053.552376] [tempesta fw] modules are stopped Apr 26 04:18:23 192.168.122.209 [44053.787976] [tempesta fw] exiting... Apr 26 04:18:23 192.168.122.209 [44053.932854] [tdb] Shutdown Tempesta DB Apr 26 04:18:23 192.168.122.209 [44054.132026] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_nctl_brange_request_negative Apr 26 04:18:23 192.168.122.209 [44054.154516] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_nctl_brange_request_positive Apr 26 04:18:24 192.168.122.209 [44055.281391] [tdb] Start Tempesta DB Apr 26 04:18:25 192.168.122.209 [44055.432270] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:18:26 192.168.122.209 [44056.792769] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44056.792769] Maybe that's fine, but it's worth checking the [44056.792769] config - if there is no relations between the [44056.792769] names, then host name confusion attack is possible. Apr 26 04:18:26 192.168.122.209 [44056.899517] [tempesta fw] Configuration processing is completed. Apr 26 04:18:26 192.168.122.209 [44056.951365] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:18:27 192.168.122.209 [44057.371456] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:18:27 192.168.122.209 [44057.404810] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:18:27 192.168.122.209 [44057.460641] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:18:27 192.168.122.209 [44057.503438] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:18:27 192.168.122.209 [44057.505097] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:18:27 192.168.122.209 [44057.543405] [tempesta fw] Tempesta FW is ready Apr 26 04:18:27 192.168.122.209 [44058.126276] [tdb] Close table 'client0.tdb' Apr 26 04:18:27 192.168.122.209 [44058.331020] [tdb] Close table 'sessions0.tdb' Apr 26 04:18:31 192.168.122.209 [44061.494208] [tdb] Close table 'cache0.tdb' Apr 26 04:18:31 192.168.122.209 [44061.738197] [tdb] Close table 'filter0.tdb' Apr 26 04:18:31 192.168.122.209 [44061.738640] [tempesta fw] modules are stopped Apr 26 04:18:31 192.168.122.209 [44061.955883] [tempesta fw] exiting... Apr 26 04:18:31 192.168.122.209 [44062.127238] [tdb] Shutdown Tempesta DB Apr 26 04:18:31 192.168.122.209 [44062.355438] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_nctl_brange_request_positive Apr 26 04:18:32 192.168.122.209 [44062.368709] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_nctl_brange_response_negative Apr 26 04:18:33 192.168.122.209 [44063.569777] [tdb] Start Tempesta DB Apr 26 04:18:33 192.168.122.209 [44063.720042] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:18:34 192.168.122.209 [44065.084850] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44065.084850] Maybe that's fine, but it's worth checking the [44065.084850] config - if there is no relations between the [44065.084850] names, then host name confusion attack is possible. Apr 26 04:18:34 192.168.122.209 [44065.187622] [tempesta fw] Configuration processing is completed. Apr 26 04:18:34 192.168.122.209 [44065.241971] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:18:35 192.168.122.209 [44065.660625] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:18:35 192.168.122.209 [44065.686097] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:18:35 192.168.122.209 [44065.712292] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:18:35 192.168.122.209 [44065.767547] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:18:35 192.168.122.209 [44065.769243] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:18:35 192.168.122.209 [44065.827523] [tempesta fw] Tempesta FW is ready Apr 26 04:18:35 192.168.122.209 [44065.985087] [tempesta fw] Warning: Parser error: state=Resp_HdrDateV input(-8)=0x4d(' [44065.985087] date: Mon, 12 Dec 2016% 13:59:39 GMT [44065.985087] content-') data_len=76 off=23 Apr 26 04:18:35 192.168.122.209 [44065.987665] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 04:18:35 192.168.122.209 [44066.002981] [tempesta fw] Warning: Parser error: state=Resp_HdrExpiresV input(-8)=0x4d('xpires: Mon, 12 Dec 2016% 13:59:39 GMT [44066.002981] content-') data_len=79 off=26 Apr 26 04:18:35 192.168.122.209 [44066.007213] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 04:18:35 192.168.122.209 [44066.021407] [tempesta fw] Warning: Parser error: state=Resp_HdrLast_ModifiedV input(-8)=0x4d('dified: Mon, 12 Dec 2016% 13:59:39 GMT [44066.021407] content-') data_len=85 off=32 Apr 26 04:18:35 192.168.122.209 [44066.024899] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 04:18:36 192.168.122.209 [44066.472563] [tdb] Close table 'client0.tdb' Apr 26 04:18:36 192.168.122.209 [44066.665963] [tdb] Close table 'sessions0.tdb' Apr 26 04:18:39 192.168.122.209 [44069.803863] [tdb] Close table 'cache0.tdb' Apr 26 04:18:39 192.168.122.209 [44070.042987] [tdb] Close table 'filter0.tdb' Apr 26 04:18:39 192.168.122.209 [44070.043428] [tempesta fw] modules are stopped Apr 26 04:18:39 192.168.122.209 [44070.264467] [tempesta fw] exiting... Apr 26 04:18:40 192.168.122.209 [44070.455030] [tdb] Shutdown Tempesta DB Apr 26 04:18:40 192.168.122.209 [44070.668532] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_nctl_brange_response_negative Apr 26 04:18:40 192.168.122.209 [44070.681277] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_nctl_brange_response_positive Apr 26 04:18:41 192.168.122.209 [44071.894101] [tdb] Start Tempesta DB Apr 26 04:18:41 192.168.122.209 [44072.046795] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:18:43 192.168.122.209 [44073.416896] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44073.416896] Maybe that's fine, but it's worth checking the [44073.416896] config - if there is no relations between the [44073.416896] names, then host name confusion attack is possible. Apr 26 04:18:43 192.168.122.209 [44073.523678] [tempesta fw] Configuration processing is completed. Apr 26 04:18:43 192.168.122.209 [44073.573818] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:18:43 192.168.122.209 [44073.978848] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:18:43 192.168.122.209 [44074.035607] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:18:43 192.168.122.209 [44074.061069] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:18:43 192.168.122.209 [44074.139655] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:18:43 192.168.122.209 [44074.141340] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:18:43 192.168.122.209 [44074.187619] [tempesta fw] Tempesta FW is ready Apr 26 04:18:44 192.168.122.209 [44074.798879] [tdb] Close table 'client0.tdb' Apr 26 04:18:44 192.168.122.209 [44074.996698] [tdb] Close table 'sessions0.tdb' Apr 26 04:18:47 192.168.122.209 [44078.179144] [tdb] Close table 'cache0.tdb' Apr 26 04:18:48 192.168.122.209 [44078.423151] [tdb] Close table 'filter0.tdb' Apr 26 04:18:48 192.168.122.209 [44078.423595] [tempesta fw] modules are stopped Apr 26 04:18:48 192.168.122.209 [44078.606730] [tempesta fw] exiting... Apr 26 04:18:48 192.168.122.209 [44078.728385] [tdb] Shutdown Tempesta DB Apr 26 04:18:48 192.168.122.209 [44078.939003] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_nctl_brange_response_positive Apr 26 04:18:48 192.168.122.209 [44078.950658] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_qetoken_brange_disallow_equal Apr 26 04:18:49 192.168.122.209 [44080.108036] [tdb] Start Tempesta DB Apr 26 04:18:49 192.168.122.209 [44080.261744] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:18:51 192.168.122.209 [44081.681045] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44081.681045] Maybe that's fine, but it's worth checking the [44081.681045] config - if there is no relations between the [44081.681045] names, then host name confusion attack is possible. Apr 26 04:18:51 192.168.122.209 [44081.775781] [tempesta fw] Configuration processing is completed. Apr 26 04:18:51 192.168.122.209 [44081.831406] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:18:51 192.168.122.209 [44082.264177] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:18:51 192.168.122.209 [44082.290819] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:18:51 192.168.122.209 [44082.317782] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:18:52 192.168.122.209 [44082.371774] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:18:52 192.168.122.209 [44082.373462] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:18:52 192.168.122.209 [44082.415650] [tempesta fw] Tempesta FW is ready Apr 26 04:18:52 192.168.122.209 [44082.560316] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrCache_ControlV input=0x75('unknown=value'), len=13, off=0 Apr 26 04:18:52 192.168.122.209 [44083.015801] [tdb] Close table 'client0.tdb' Apr 26 04:18:52 192.168.122.209 [44083.186008] [tdb] Close table 'sessions0.tdb' Apr 26 04:18:56 192.168.122.209 [44086.407808] [tdb] Close table 'cache0.tdb' Apr 26 04:18:56 192.168.122.209 [44086.655121] [tdb] Close table 'filter0.tdb' Apr 26 04:18:56 192.168.122.209 [44086.655558] [tempesta fw] modules are stopped Apr 26 04:18:56 192.168.122.209 [44086.880161] [tempesta fw] exiting... Apr 26 04:18:56 192.168.122.209 [44087.038256] [tdb] Shutdown Tempesta DB Apr 26 04:18:56 192.168.122.209 [44087.242880] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_qetoken_brange_disallow_equal Apr 26 04:18:56 192.168.122.209 [44087.252217] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_qetoken_brange_negative Apr 26 04:18:58 192.168.122.209 [44088.402932] [tdb] Start Tempesta DB Apr 26 04:18:58 192.168.122.209 [44088.554209] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:18:59 192.168.122.209 [44089.977187] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44089.977187] Maybe that's fine, but it's worth checking the [44089.977187] config - if there is no relations between the [44089.977187] names, then host name confusion attack is possible. Apr 26 04:18:59 192.168.122.209 [44090.075918] [tempesta fw] Configuration processing is completed. Apr 26 04:18:59 192.168.122.209 [44090.130071] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:19:00 192.168.122.209 [44090.547274] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:19:00 192.168.122.209 [44090.573005] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:19:00 192.168.122.209 [44090.598611] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:19:00 192.168.122.209 [44090.643893] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:19:00 192.168.122.209 [44090.645325] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:19:00 192.168.122.209 [44090.683820] [tempesta fw] Tempesta FW is ready Apr 26 04:19:00 192.168.122.209 [44090.828940] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrCache_ControlV input=0x75('unkno%wn=value%'), len=15, off=0 Apr 26 04:19:00 192.168.122.209 [44091.216589] [tdb] Close table 'client0.tdb' Apr 26 04:19:01 192.168.122.209 [44091.435419] [tdb] Close table 'sessions0.tdb' Apr 26 04:19:04 192.168.122.209 [44094.579340] [tdb] Close table 'cache0.tdb' Apr 26 04:19:04 192.168.122.209 [44094.828574] [tdb] Close table 'filter0.tdb' Apr 26 04:19:04 192.168.122.209 [44094.829017] [tempesta fw] modules are stopped Apr 26 04:19:04 192.168.122.209 [44095.040568] [tempesta fw] exiting... Apr 26 04:19:04 192.168.122.209 [44095.188902] [tdb] Shutdown Tempesta DB Apr 26 04:19:05 192.168.122.209 [44095.406593] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_qetoken_brange_negative Apr 26 04:19:05 192.168.122.209 [44095.417693] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_qetoken_brange_positive Apr 26 04:19:06 192.168.122.209 [44096.524027] [tdb] Start Tempesta DB Apr 26 04:19:06 192.168.122.209 [44096.672270] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:19:07 192.168.122.209 [44098.073214] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44098.073214] Maybe that's fine, but it's worth checking the [44098.073214] config - if there is no relations between the [44098.073214] names, then host name confusion attack is possible. Apr 26 04:19:07 192.168.122.209 [44098.175995] [tempesta fw] Configuration processing is completed. Apr 26 04:19:07 192.168.122.209 [44098.227350] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:19:08 192.168.122.209 [44098.655353] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:19:08 192.168.122.209 [44098.680959] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:19:08 192.168.122.209 [44098.706775] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:19:08 192.168.122.209 [44098.747979] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:19:08 192.168.122.209 [44098.749670] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:19:08 192.168.122.209 [44098.795927] [tempesta fw] Tempesta FW is ready Apr 26 04:19:08 192.168.122.209 [44099.361755] [tdb] Close table 'client0.tdb' Apr 26 04:19:09 192.168.122.209 [44099.572947] [tdb] Close table 'sessions0.tdb' Apr 26 04:19:12 192.168.122.209 [44102.717429] [tdb] Close table 'cache0.tdb' Apr 26 04:19:12 192.168.122.209 [44102.946469] [tdb] Close table 'filter0.tdb' Apr 26 04:19:12 192.168.122.209 [44102.946898] [tempesta fw] modules are stopped Apr 26 04:19:12 192.168.122.209 [44103.153485] [tempesta fw] exiting... Apr 26 04:19:12 192.168.122.209 [44103.342348] [tdb] Shutdown Tempesta DB Apr 26 04:19:13 192.168.122.209 [44103.531122] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_qetoken_brange_positive Apr 26 04:19:13 192.168.122.209 [44103.542430] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_token_brange_negative Apr 26 04:19:14 192.168.122.209 [44104.736221] [tdb] Start Tempesta DB Apr 26 04:19:14 192.168.122.209 [44104.884678] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:19:15 192.168.122.209 [44106.317352] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44106.317352] Maybe that's fine, but it's worth checking the [44106.317352] config - if there is no relations between the [44106.317352] names, then host name confusion attack is possible. Apr 26 04:19:16 192.168.122.209 [44106.428097] [tempesta fw] Configuration processing is completed. Apr 26 04:19:16 192.168.122.209 [44106.484888] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:19:16 192.168.122.209 [44106.900201] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:19:16 192.168.122.209 [44106.956027] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:19:16 192.168.122.209 [44106.981701] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:19:16 192.168.122.209 [44107.024099] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:19:16 192.168.122.209 [44107.025780] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:19:16 192.168.122.209 [44107.068030] [tempesta fw] Tempesta FW is ready Apr 26 04:19:16 192.168.122.209 [44107.213059] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrCookieV input=0x75('unknown%=value'), len=14, off=0 Apr 26 04:19:17 192.168.122.209 [44107.660227] [tdb] Close table 'client0.tdb' Apr 26 04:19:17 192.168.122.209 [44107.857796] [tdb] Close table 'sessions0.tdb' Apr 26 04:19:20 192.168.122.209 [44111.039403] [tdb] Close table 'cache0.tdb' Apr 26 04:19:20 192.168.122.209 [44111.279812] [tdb] Close table 'filter0.tdb' Apr 26 04:19:20 192.168.122.209 [44111.280272] [tempesta fw] modules are stopped Apr 26 04:19:21 192.168.122.209 [44111.476019] [tempesta fw] exiting... Apr 26 04:19:21 192.168.122.209 [44111.630521] [tdb] Shutdown Tempesta DB Apr 26 04:19:21 192.168.122.209 [44111.825381] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_token_brange_negative Apr 26 04:19:21 192.168.122.209 [44111.838791] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_token_brange_positive Apr 26 04:19:22 192.168.122.209 [44112.960611] [tdb] Start Tempesta DB Apr 26 04:19:22 192.168.122.209 [44113.091193] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:19:24 192.168.122.209 [44114.489433] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44114.489433] Maybe that's fine, but it's worth checking the [44114.489433] config - if there is no relations between the [44114.489433] names, then host name confusion attack is possible. Apr 26 04:19:24 192.168.122.209 [44114.588207] [tempesta fw] Configuration processing is completed. Apr 26 04:19:24 192.168.122.209 [44114.639293] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:19:24 192.168.122.209 [44115.063516] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:19:24 192.168.122.209 [44115.089929] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:19:24 192.168.122.209 [44115.115954] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:19:24 192.168.122.209 [44115.164201] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:19:24 192.168.122.209 [44115.165890] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:19:24 192.168.122.209 [44115.208125] [tempesta fw] Tempesta FW is ready Apr 26 04:19:25 192.168.122.209 [44115.762433] [tdb] Close table 'client0.tdb' Apr 26 04:19:25 192.168.122.209 [44115.995922] [tdb] Close table 'sessions0.tdb' Apr 26 04:19:28 192.168.122.209 [44119.131097] [tdb] Close table 'cache0.tdb' Apr 26 04:19:29 192.168.122.209 [44119.383413] [tdb] Close table 'filter0.tdb' Apr 26 04:19:29 192.168.122.209 [44119.383849] [tempesta fw] modules are stopped Apr 26 04:19:29 192.168.122.209 [44119.582672] [tempesta fw] exiting... Apr 26 04:19:29 192.168.122.209 [44119.763304] [tdb] Shutdown Tempesta DB Apr 26 04:19:29 192.168.122.209 [44119.973237] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_token_brange_positive Apr 26 04:19:29 192.168.122.209 [44119.980098] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_uri_brange_blocked_percent Apr 26 04:19:30 192.168.122.209 [44121.210643] [tdb] Start Tempesta DB Apr 26 04:19:30 192.168.122.209 [44121.352983] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:19:32 192.168.122.209 [44122.761277] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44122.761277] Maybe that's fine, but it's worth checking the [44122.761277] config - if there is no relations between the [44122.761277] names, then host name confusion attack is possible. Apr 26 04:19:32 192.168.122.209 [44122.860311] [tempesta fw] Configuration processing is completed. Apr 26 04:19:32 192.168.122.209 [44122.911785] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:19:32 192.168.122.209 [44123.316771] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:19:33 192.168.122.209 [44123.372694] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:19:33 192.168.122.209 [44123.398319] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:19:33 192.168.122.209 [44123.472323] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:19:33 192.168.122.209 [44123.474003] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:19:33 192.168.122.209 [44123.528242] [tempesta fw] Tempesta FW is ready Apr 26 04:19:33 192.168.122.209 [44123.656108] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrPsPathV input=0x6a('js%a'), len=4, off=0 Apr 26 04:19:33 192.168.122.209 [44124.110564] [tdb] Close table 'client0.tdb' Apr 26 04:19:33 192.168.122.209 [44124.313003] [tdb] Close table 'sessions0.tdb' Apr 26 04:19:37 192.168.122.209 [44127.519929] [tdb] Close table 'cache0.tdb' Apr 26 04:19:37 192.168.122.209 [44127.767802] [tdb] Close table 'filter0.tdb' Apr 26 04:19:37 192.168.122.209 [44127.768258] [tempesta fw] modules are stopped Apr 26 04:19:37 192.168.122.209 [44127.932885] [tempesta fw] exiting... Apr 26 04:19:37 192.168.122.209 [44128.104920] [tdb] Shutdown Tempesta DB Apr 26 04:19:37 192.168.122.209 [44128.319050] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_uri_brange_blocked_percent Apr 26 04:19:37 192.168.122.209 [44128.335444] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_uri_brange_issue_2030 Apr 26 04:19:39 192.168.122.209 [44129.468538] [tdb] Start Tempesta DB Apr 26 04:19:39 192.168.122.209 [44129.618920] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:19:40 192.168.122.209 [44130.965769] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44130.965769] Maybe that's fine, but it's worth checking the [44130.965769] config - if there is no relations between the [44130.965769] names, then host name confusion attack is possible. Apr 26 04:19:40 192.168.122.209 [44131.060790] [tempesta fw] Configuration processing is completed. Apr 26 04:19:40 192.168.122.209 [44131.119502] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:19:41 192.168.122.209 [44131.538468] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:19:41 192.168.122.209 [44131.565672] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:19:41 192.168.122.209 [44131.630904] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:19:41 192.168.122.209 [44131.685677] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:19:41 192.168.122.209 [44131.688376] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:19:41 192.168.122.209 [44131.732330] [tempesta fw] Tempesta FW is ready Apr 26 04:19:41 192.168.122.209 [44132.341382] [tdb] Close table 'client0.tdb' Apr 26 04:19:42 192.168.122.209 [44132.530015] [tdb] Close table 'sessions0.tdb' Apr 26 04:19:45 192.168.122.209 [44135.779622] [tdb] Close table 'cache0.tdb' Apr 26 04:19:45 192.168.122.209 [44136.023860] [tdb] Close table 'filter0.tdb' Apr 26 04:19:45 192.168.122.209 [44136.024311] [tempesta fw] modules are stopped Apr 26 04:19:45 192.168.122.209 [44136.217615] [tempesta fw] exiting... Apr 26 04:19:45 192.168.122.209 [44136.360208] [tdb] Shutdown Tempesta DB Apr 26 04:19:46 192.168.122.209 [44136.602280] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_uri_brange_issue_2030 Apr 26 04:19:46 192.168.122.209 [44136.622045] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_uri_brange_not_blocked_percent Apr 26 04:19:47 192.168.122.209 [44137.856245] [tdb] Start Tempesta DB Apr 26 04:19:47 192.168.122.209 [44138.008455] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:19:49 192.168.122.209 [44139.417734] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44139.417734] Maybe that's fine, but it's worth checking the [44139.417734] config - if there is no relations between the [44139.417734] names, then host name confusion attack is possible. Apr 26 04:19:49 192.168.122.209 [44139.520521] [tempesta fw] Configuration processing is completed. Apr 26 04:19:49 192.168.122.209 [44139.571820] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:19:49 192.168.122.209 [44139.999857] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:19:49 192.168.122.209 [44140.032457] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:19:49 192.168.122.209 [44140.058586] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:19:49 192.168.122.209 [44140.100492] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:19:49 192.168.122.209 [44140.102187] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:19:49 192.168.122.209 [44140.140466] [tempesta fw] Tempesta FW is ready Apr 26 04:19:50 192.168.122.209 [44140.702355] [tdb] Close table 'client0.tdb' Apr 26 04:19:50 192.168.122.209 [44140.902574] [tdb] Close table 'sessions0.tdb' Apr 26 04:19:53 192.168.122.209 [44144.048998] [tdb] Close table 'cache0.tdb' Apr 26 04:19:53 192.168.122.209 [44144.289653] [tdb] Close table 'filter0.tdb' Apr 26 04:19:53 192.168.122.209 [44144.290085] [tempesta fw] modules are stopped Apr 26 04:19:54 192.168.122.209 [44144.530527] [tempesta fw] exiting... Apr 26 04:19:54 192.168.122.209 [44144.699854] [tdb] Shutdown Tempesta DB Apr 26 04:19:54 192.168.122.209 [44144.901875] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_uri_brange_not_blocked_percent Apr 26 04:19:54 192.168.122.209 [44144.922866] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_uri_brange_referer_header_allowed_character Apr 26 04:19:55 192.168.122.209 [44146.078063] [tdb] Start Tempesta DB Apr 26 04:19:55 192.168.122.209 [44146.227761] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:19:57 192.168.122.209 [44147.603084] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44147.603084] Maybe that's fine, but it's worth checking the [44147.603084] config - if there is no relations between the [44147.603084] names, then host name confusion attack is possible. Apr 26 04:19:57 192.168.122.209 [44147.721195] [tempesta fw] Configuration processing is completed. Apr 26 04:19:57 192.168.122.209 [44147.769040] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:19:57 192.168.122.209 [44148.186063] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:19:57 192.168.122.209 [44148.211399] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:19:57 192.168.122.209 [44148.275172] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:19:57 192.168.122.209 [44148.316641] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:19:57 192.168.122.209 [44148.318312] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:19:57 192.168.122.209 [44148.356544] [tempesta fw] Tempesta FW is ready Apr 26 04:19:58 192.168.122.209 [44148.938408] [tdb] Close table 'client0.tdb' Apr 26 04:19:58 192.168.122.209 [44149.134378] [tdb] Close table 'sessions0.tdb' Apr 26 04:20:01 192.168.122.209 [44152.325950] [tdb] Close table 'cache0.tdb' Apr 26 04:20:02 192.168.122.209 [44152.575734] [tdb] Close table 'filter0.tdb' Apr 26 04:20:02 192.168.122.209 [44152.576167] [tempesta fw] modules are stopped Apr 26 04:20:02 192.168.122.209 [44152.778243] [tempesta fw] exiting... Apr 26 04:20:02 192.168.122.209 [44152.922778] [tdb] Shutdown Tempesta DB Apr 26 04:20:02 192.168.122.209 [44153.186122] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_uri_brange_referer_header_allowed_character Apr 26 04:20:02 192.168.122.209 [44153.200075] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_uri_brange_referer_header_disallowed_character Apr 26 04:20:03 192.168.122.209 [44154.295407] [tdb] Start Tempesta DB Apr 26 04:20:04 192.168.122.209 [44154.433676] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:20:05 192.168.122.209 [44155.810012] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44155.810012] Maybe that's fine, but it's worth checking the [44155.810012] config - if there is no relations between the [44155.810012] names, then host name confusion attack is possible. Apr 26 04:20:05 192.168.122.209 [44155.912741] [tempesta fw] Configuration processing is completed. Apr 26 04:20:05 192.168.122.209 [44155.967348] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:20:06 192.168.122.209 [44156.404350] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:20:06 192.168.122.209 [44156.430684] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:20:06 192.168.122.209 [44156.457166] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:20:06 192.168.122.209 [44156.492704] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:20:06 192.168.122.209 [44156.494382] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:20:06 192.168.122.209 [44156.532663] [tempesta fw] Tempesta FW is ready Apr 26 04:20:06 192.168.122.209 [44156.666656] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrRefererV input=0x2f('/example+'), len=9, off=0 Apr 26 04:20:06 192.168.122.209 [44157.147490] [tdb] Close table 'client0.tdb' Apr 26 04:20:06 192.168.122.209 [44157.328906] [tdb] Close table 'sessions0.tdb' Apr 26 04:20:10 192.168.122.209 [44160.483767] [tdb] Close table 'cache0.tdb' Apr 26 04:20:10 192.168.122.209 [44160.724847] [tdb] Close table 'filter0.tdb' Apr 26 04:20:10 192.168.122.209 [44160.725312] [tempesta fw] modules are stopped Apr 26 04:20:10 192.168.122.209 [44160.893569] [tempesta fw] exiting... Apr 26 04:20:10 192.168.122.209 [44161.028537] [tdb] Shutdown Tempesta DB Apr 26 04:20:10 192.168.122.209 [44161.272389] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_uri_brange_referer_header_disallowed_character Apr 26 04:20:10 192.168.122.209 [44161.297241] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_xff_brange_allow_ipv4 Apr 26 04:20:12 192.168.122.209 [44162.418738] [tdb] Start Tempesta DB Apr 26 04:20:12 192.168.122.209 [44162.575052] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:20:13 192.168.122.209 [44163.942045] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44163.942045] Maybe that's fine, but it's worth checking the [44163.942045] config - if there is no relations between the [44163.942045] names, then host name confusion attack is possible. Apr 26 04:20:13 192.168.122.209 [44164.052832] [tempesta fw] Configuration processing is completed. Apr 26 04:20:13 192.168.122.209 [44164.111098] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:20:14 192.168.122.209 [44164.531042] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:20:14 192.168.122.209 [44164.588303] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:20:14 192.168.122.209 [44164.621187] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:20:14 192.168.122.209 [44164.664750] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:20:14 192.168.122.209 [44164.666030] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:20:14 192.168.122.209 [44164.704754] [tempesta fw] Tempesta FW is ready Apr 26 04:20:14 192.168.122.209 [44165.279203] [tdb] Close table 'client0.tdb' Apr 26 04:20:15 192.168.122.209 [44165.474272] [tdb] Close table 'sessions0.tdb' Apr 26 04:20:18 192.168.122.209 [44168.622328] [tdb] Close table 'cache0.tdb' Apr 26 04:20:18 192.168.122.209 [44168.866197] [tdb] Close table 'filter0.tdb' Apr 26 04:20:18 192.168.122.209 [44168.866617] [tempesta fw] modules are stopped Apr 26 04:20:18 192.168.122.209 [44169.108793] [tempesta fw] exiting... Apr 26 04:20:18 192.168.122.209 [44169.241482] [tdb] Shutdown Tempesta DB Apr 26 04:20:19 192.168.122.209 [44169.499181] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_xff_brange_allow_ipv4 Apr 26 04:20:19 192.168.122.209 [44169.512256] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_xff_brange_allow_ipv6 Apr 26 04:20:20 192.168.122.209 [44170.648478] [tdb] Start Tempesta DB Apr 26 04:20:20 192.168.122.209 [44170.800394] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:20:21 192.168.122.209 [44172.226148] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44172.226148] Maybe that's fine, but it's worth checking the [44172.226148] config - if there is no relations between the [44172.226148] names, then host name confusion attack is possible. Apr 26 04:20:21 192.168.122.209 [44172.348920] [tempesta fw] Configuration processing is completed. Apr 26 04:20:22 192.168.122.209 [44172.407989] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:20:22 192.168.122.209 [44172.838500] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:20:22 192.168.122.209 [44172.864759] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:20:22 192.168.122.209 [44172.891473] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:20:22 192.168.122.209 [44172.936944] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:20:22 192.168.122.209 [44172.938627] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:20:22 192.168.122.209 [44172.992861] [tempesta fw] Tempesta FW is ready Apr 26 04:20:23 192.168.122.209 [44173.584035] [tdb] Close table 'client0.tdb' Apr 26 04:20:23 192.168.122.209 [44173.780767] [tdb] Close table 'sessions0.tdb' Apr 26 04:20:26 192.168.122.209 [44176.950032] [tdb] Close table 'cache0.tdb' Apr 26 04:20:26 192.168.122.209 [44177.186851] [tdb] Close table 'filter0.tdb' Apr 26 04:20:26 192.168.122.209 [44177.187299] [tempesta fw] modules are stopped Apr 26 04:20:27 192.168.122.209 [44177.500119] [tempesta fw] exiting... Apr 26 04:20:27 192.168.122.209 [44177.673492] [tdb] Shutdown Tempesta DB Apr 26 04:20:27 192.168.122.209 [44177.908707] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_xff_brange_allow_ipv6 Apr 26 04:20:27 192.168.122.209 [44177.917529] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_xff_brange_allow_many_ip Apr 26 04:20:28 192.168.122.209 [44179.024145] [tdb] Start Tempesta DB Apr 26 04:20:28 192.168.122.209 [44179.175984] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:20:30 192.168.122.209 [44180.558314] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44180.558314] Maybe that's fine, but it's worth checking the [44180.558314] config - if there is no relations between the [44180.558314] names, then host name confusion attack is possible. Apr 26 04:20:30 192.168.122.209 [44180.665042] [tempesta fw] Configuration processing is completed. Apr 26 04:20:30 192.168.122.209 [44180.719593] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:20:30 192.168.122.209 [44181.170569] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:20:30 192.168.122.209 [44181.199004] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:20:30 192.168.122.209 [44181.227196] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:20:30 192.168.122.209 [44181.269026] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:20:30 192.168.122.209 [44181.270674] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:20:30 192.168.122.209 [44181.312969] [tempesta fw] Tempesta FW is ready Apr 26 04:20:31 192.168.122.209 [44181.860703] [tdb] Close table 'client0.tdb' Apr 26 04:20:31 192.168.122.209 [44182.065903] [tdb] Close table 'sessions0.tdb' Apr 26 04:20:34 192.168.122.209 [44185.233574] [tdb] Close table 'cache0.tdb' Apr 26 04:20:35 192.168.122.209 [44185.488724] [tdb] Close table 'filter0.tdb' Apr 26 04:20:35 192.168.122.209 [44185.489586] [tempesta fw] modules are stopped Apr 26 04:20:35 192.168.122.209 [44185.711315] [tempesta fw] exiting... Apr 26 04:20:35 192.168.122.209 [44185.858255] [tdb] Shutdown Tempesta DB Apr 26 04:20:35 192.168.122.209 [44186.097934] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_xff_brange_allow_many_ip Apr 26 04:20:35 192.168.122.209 [44186.113763] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_xff_brange_disallow_ipv4 Apr 26 04:20:36 192.168.122.209 [44187.275990] [tdb] Start Tempesta DB Apr 26 04:20:37 192.168.122.209 [44187.438118] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:20:38 192.168.122.209 [44188.878463] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44188.878463] Maybe that's fine, but it's worth checking the [44188.878463] config - if there is no relations between the [44188.878463] names, then host name confusion attack is possible. Apr 26 04:20:38 192.168.122.209 [44188.989847] [tempesta fw] Configuration processing is completed. Apr 26 04:20:38 192.168.122.209 [44189.047441] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:20:39 192.168.122.209 [44189.542008] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:20:39 192.168.122.209 [44189.573141] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:20:39 192.168.122.209 [44189.602816] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:20:39 192.168.122.209 [44189.645139] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:20:39 192.168.122.209 [44189.646841] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:20:39 192.168.122.209 [44189.685066] [tempesta fw] Tempesta FW is ready Apr 26 04:20:39 192.168.122.209 [44189.834142] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrX_Forwarded_ForV input=0x35('5.10.50.6'), len=9, off=0 Apr 26 04:20:39 192.168.122.209 [44190.282201] [tdb] Close table 'client0.tdb' Apr 26 04:20:40 192.168.122.209 [44190.499785] [tdb] Close table 'sessions0.tdb' Apr 26 04:20:43 192.168.122.209 [44193.661876] [tdb] Close table 'cache0.tdb' Apr 26 04:20:43 192.168.122.209 [44193.941840] [tdb] Close table 'filter0.tdb' Apr 26 04:20:43 192.168.122.209 [44193.942356] [tempesta fw] modules are stopped Apr 26 04:20:43 192.168.122.209 [44194.157600] [tempesta fw] exiting... Apr 26 04:20:43 192.168.122.209 [44194.332897] [tdb] Shutdown Tempesta DB Apr 26 04:20:44 192.168.122.209 [44194.564972] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_xff_brange_disallow_ipv4 Apr 26 04:20:44 192.168.122.209 [44194.590688] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_xff_brange_disallow_ipv6 Apr 26 04:20:45 192.168.122.209 [44195.897142] [tdb] Start Tempesta DB Apr 26 04:20:45 192.168.122.209 [44196.040923] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:20:47 192.168.122.209 [44197.474587] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44197.474587] Maybe that's fine, but it's worth checking the [44197.474587] config - if there is no relations between the [44197.474587] names, then host name confusion attack is possible. Apr 26 04:20:47 192.168.122.209 [44197.573199] [tempesta fw] Configuration processing is completed. Apr 26 04:20:47 192.168.122.209 [44197.626318] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:20:47 192.168.122.209 [44198.091497] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:20:47 192.168.122.209 [44198.123392] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:20:47 192.168.122.209 [44198.185705] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:20:47 192.168.122.209 [44198.233260] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:20:47 192.168.122.209 [44198.234969] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:20:47 192.168.122.209 [44198.273190] [tempesta fw] Tempesta FW is ready Apr 26 04:20:48 192.168.122.209 [44198.434991] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrX_Forwarded_ForV input=0x32('2001:db8:85a3:8d'), len=36, off=0 Apr 26 04:20:48 192.168.122.209 [44198.899896] [tdb] Close table 'client0.tdb' Apr 26 04:20:48 192.168.122.209 [44199.095540] [tdb] Close table 'sessions0.tdb' Apr 26 04:20:51 192.168.122.209 [44202.211415] [tdb] Close table 'cache0.tdb' Apr 26 04:20:52 192.168.122.209 [44202.472197] [tdb] Close table 'filter0.tdb' Apr 26 04:20:52 192.168.122.209 [44202.472628] [tempesta fw] modules are stopped Apr 26 04:20:52 192.168.122.209 [44202.677647] [tempesta fw] exiting... Apr 26 04:20:52 192.168.122.209 [44202.811580] [tdb] Shutdown Tempesta DB Apr 26 04:20:52 192.168.122.209 [44203.039235] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_xff_brange_disallow_ipv6 Apr 26 04:20:52 192.168.122.209 [44203.048774] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_boundary_values_0x40_from_0x41_to_0x7e Apr 26 04:20:53 192.168.122.209 [44204.175861] [tdb] Start Tempesta DB Apr 26 04:20:53 192.168.122.209 [44204.332356] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:20:55 192.168.122.209 [44205.794692] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44205.794692] Maybe that's fine, but it's worth checking the [44205.794692] config - if there is no relations between the [44205.794692] names, then host name confusion attack is possible. Apr 26 04:20:55 192.168.122.209 [44205.901389] [tempesta fw] Configuration processing is completed. Apr 26 04:20:55 192.168.122.209 [44205.961167] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:20:56 192.168.122.209 [44206.414152] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:20:56 192.168.122.209 [44206.442189] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:20:56 192.168.122.209 [44206.469600] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:20:56 192.168.122.209 [44206.513387] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:20:56 192.168.122.209 [44206.515108] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:20:56 192.168.122.209 [44206.549300] [tempesta fw] Tempesta FW is ready Apr 26 04:20:56 192.168.122.209 [44206.674340] [tempesta fw] Warning: Parser error: state=Req_UriAbsPath input(-5)=0x65('GET /example@ HTTP/1.1 [44206.674340] Host: localhost [44206.674340] [44206.674340] ') data_len=43 off=5 Apr 26 04:20:56 192.168.122.209 [44207.108071] [tdb] Close table 'client0.tdb' Apr 26 04:20:56 192.168.122.209 [44207.319472] [tdb] Close table 'sessions0.tdb' Apr 26 04:21:00 192.168.122.209 [44210.456056] [tdb] Close table 'cache0.tdb' Apr 26 04:21:00 192.168.122.209 [44210.703318] [tdb] Close table 'filter0.tdb' Apr 26 04:21:00 192.168.122.209 [44210.703758] [tempesta fw] modules are stopped Apr 26 04:21:00 192.168.122.209 [44210.922325] [tempesta fw] exiting... Apr 26 04:21:00 192.168.122.209 [44211.075120] [tdb] Shutdown Tempesta DB Apr 26 04:21:00 192.168.122.209 [44211.297515] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_boundary_values_0x40_from_0x41_to_0x7e Apr 26 04:21:00 192.168.122.209 [44211.312410] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_boundary_values_0x41_from_0x41_to_0x7e Apr 26 04:21:02 192.168.122.209 [44212.497878] [tdb] Start Tempesta DB Apr 26 04:21:02 192.168.122.209 [44212.650845] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:21:03 192.168.122.209 [44214.054693] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44214.054693] Maybe that's fine, but it's worth checking the [44214.054693] config - if there is no relations between the [44214.054693] names, then host name confusion attack is possible. Apr 26 04:21:03 192.168.122.209 [44214.173451] [tempesta fw] Configuration processing is completed. Apr 26 04:21:03 192.168.122.209 [44214.223041] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:21:04 192.168.122.209 [44214.632815] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:21:04 192.168.122.209 [44214.659002] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:21:04 192.168.122.209 [44214.719985] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:21:04 192.168.122.209 [44214.769488] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:21:04 192.168.122.209 [44214.771157] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:21:04 192.168.122.209 [44214.809391] [tempesta fw] Tempesta FW is ready Apr 26 04:21:05 192.168.122.209 [44215.392869] [tdb] Close table 'client0.tdb' Apr 26 04:21:05 192.168.122.209 [44215.600401] [tdb] Close table 'sessions0.tdb' Apr 26 04:21:08 192.168.122.209 [44218.741078] [tdb] Close table 'cache0.tdb' Apr 26 04:21:08 192.168.122.209 [44218.962759] [tdb] Close table 'filter0.tdb' Apr 26 04:21:08 192.168.122.209 [44218.963201] [tempesta fw] modules are stopped Apr 26 04:21:08 192.168.122.209 [44219.144552] [tempesta fw] exiting... Apr 26 04:21:08 192.168.122.209 [44219.336883] [tdb] Shutdown Tempesta DB Apr 26 04:21:09 192.168.122.209 [44219.530657] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_boundary_values_0x41_from_0x41_to_0x7e Apr 26 04:21:09 192.168.122.209 [44219.543930] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_boundary_values_0x7e_from_0x41_to_0x7e Apr 26 04:21:10 192.168.122.209 [44220.688797] [tdb] Start Tempesta DB Apr 26 04:21:10 192.168.122.209 [44220.841509] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:21:11 192.168.122.209 [44222.270809] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44222.270809] Maybe that's fine, but it's worth checking the [44222.270809] config - if there is no relations between the [44222.270809] names, then host name confusion attack is possible. Apr 26 04:21:12 192.168.122.209 [44222.381565] [tempesta fw] Configuration processing is completed. Apr 26 04:21:12 192.168.122.209 [44222.431250] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:21:12 192.168.122.209 [44222.858427] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:21:12 192.168.122.209 [44222.883798] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:21:12 192.168.122.209 [44222.909791] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:21:12 192.168.122.209 [44222.957569] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:21:12 192.168.122.209 [44222.959254] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:21:12 192.168.122.209 [44222.997505] [tempesta fw] Tempesta FW is ready Apr 26 04:21:13 192.168.122.209 [44223.557674] [tdb] Close table 'client0.tdb' Apr 26 04:21:13 192.168.122.209 [44223.742265] [tdb] Close table 'sessions0.tdb' Apr 26 04:21:16 192.168.122.209 [44226.955252] [tdb] Close table 'cache0.tdb' Apr 26 04:21:16 192.168.122.209 [44227.190357] [tdb] Close table 'filter0.tdb' Apr 26 04:21:16 192.168.122.209 [44227.190817] [tempesta fw] modules are stopped Apr 26 04:21:17 192.168.122.209 [44227.397641] [tempesta fw] exiting... Apr 26 04:21:17 192.168.122.209 [44227.580469] [tdb] Shutdown Tempesta DB Apr 26 04:21:17 192.168.122.209 [44227.786664] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_boundary_values_0x7e_from_0x41_to_0x7e Apr 26 04:21:17 192.168.122.209 [44227.801262] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_boundary_values_0x7f_from_0x41_to_0x7e Apr 26 04:21:18 192.168.122.209 [44228.997204] [tdb] Start Tempesta DB Apr 26 04:21:18 192.168.122.209 [44229.152625] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:21:20 192.168.122.209 [44230.570927] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44230.570927] Maybe that's fine, but it's worth checking the [44230.570927] config - if there is no relations between the [44230.570927] names, then host name confusion attack is possible. Apr 26 04:21:20 192.168.122.209 [44230.673713] [tempesta fw] Configuration processing is completed. Apr 26 04:21:20 192.168.122.209 [44230.726066] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:21:20 192.168.122.209 [44231.146766] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:21:20 192.168.122.209 [44231.173239] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:21:20 192.168.122.209 [44231.199526] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:21:20 192.168.122.209 [44231.253645] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:21:20 192.168.122.209 [44231.255307] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:21:20 192.168.122.209 [44231.301601] [tempesta fw] Tempesta FW is ready Apr 26 04:21:21 192.168.122.209 [44231.446754] [tempesta fw] Warning: Parser error: state=Req_UriAbsPath input(-5)=0x65('GET /example HTTP/1.1 [44231.446754] Host: localhost [44231.446754] [44231.446754] ') data_len=43 off=5 Apr 26 04:21:21 192.168.122.209 [44231.900154] [tdb] Close table 'client0.tdb' Apr 26 04:21:21 192.168.122.209 [44232.085456] [tdb] Close table 'sessions0.tdb' Apr 26 04:21:24 192.168.122.209 [44235.215469] [tdb] Close table 'cache0.tdb' Apr 26 04:21:25 192.168.122.209 [44235.459561] [tdb] Close table 'filter0.tdb' Apr 26 04:21:25 192.168.122.209 [44235.460001] [tempesta fw] modules are stopped Apr 26 04:21:25 192.168.122.209 [44235.693315] [tempesta fw] exiting... Apr 26 04:21:25 192.168.122.209 [44235.830458] [tdb] Shutdown Tempesta DB Apr 26 04:21:25 192.168.122.209 [44236.039100] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_boundary_values_0x7f_from_0x41_to_0x7e Apr 26 04:21:25 192.168.122.209 [44236.054095] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_boundary_values_disallowed_0x5f Apr 26 04:21:26 192.168.122.209 [44237.184689] [tdb] Start Tempesta DB Apr 26 04:21:26 192.168.122.209 [44237.333953] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:21:28 192.168.122.209 [44238.787019] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44238.787019] Maybe that's fine, but it's worth checking the [44238.787019] config - if there is no relations between the [44238.787019] names, then host name confusion attack is possible. Apr 26 04:21:28 192.168.122.209 [44238.897844] [tempesta fw] Configuration processing is completed. Apr 26 04:21:28 192.168.122.209 [44238.949343] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:21:29 192.168.122.209 [44239.370542] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:21:29 192.168.122.209 [44239.397028] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:21:29 192.168.122.209 [44239.423458] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:21:29 192.168.122.209 [44239.469717] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:21:29 192.168.122.209 [44239.471384] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:21:29 192.168.122.209 [44239.533738] [tempesta fw] Tempesta FW is ready Apr 26 04:21:29 192.168.122.209 [44239.677289] [tempesta fw] Warning: Parser error: state=Req_UriAbsPath input(-5)=0x65('GET /example_ HTTP/1.1 [44239.677289] Host: localhost [44239.677289] [44239.677289] ') data_len=43 off=5 Apr 26 04:21:29 192.168.122.209 [44240.174303] [tdb] Close table 'client0.tdb' Apr 26 04:21:30 192.168.122.209 [44240.363732] [tdb] Close table 'sessions0.tdb' Apr 26 04:21:33 192.168.122.209 [44243.559275] [tdb] Close table 'cache0.tdb' Apr 26 04:21:33 192.168.122.209 [44243.812741] [tdb] Close table 'filter0.tdb' Apr 26 04:21:33 192.168.122.209 [44243.813203] [tempesta fw] modules are stopped Apr 26 04:21:33 192.168.122.209 [44244.008414] [tempesta fw] exiting... Apr 26 04:21:33 192.168.122.209 [44244.163511] [tdb] Shutdown Tempesta DB Apr 26 04:21:33 192.168.122.209 [44244.349395] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_boundary_values_disallowed_0x5f Apr 26 04:21:34 192.168.122.209 [44244.367437] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_cookie_brange_allow_many_cookie Apr 26 04:21:35 192.168.122.209 [44245.434659] [tdb] Start Tempesta DB Apr 26 04:21:35 192.168.122.209 [44245.592678] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:21:36 192.168.122.209 [44246.939180] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44246.939180] Maybe that's fine, but it's worth checking the [44246.939180] config - if there is no relations between the [44246.939180] names, then host name confusion attack is possible. Apr 26 04:21:36 192.168.122.209 [44247.037879] [tempesta fw] Configuration processing is completed. Apr 26 04:21:36 192.168.122.209 [44247.091063] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:21:37 192.168.122.209 [44247.522453] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:21:37 192.168.122.209 [44247.548236] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:21:37 192.168.122.209 [44247.573883] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:21:37 192.168.122.209 [44247.629868] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:21:37 192.168.122.209 [44247.631564] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:21:37 192.168.122.209 [44247.681805] [tempesta fw] Tempesta FW is ready Apr 26 04:21:37 192.168.122.209 [44248.264132] [tdb] Close table 'client0.tdb' Apr 26 04:21:38 192.168.122.209 [44248.455334] [tdb] Close table 'sessions0.tdb' Apr 26 04:21:41 192.168.122.209 [44251.563087] [tdb] Close table 'cache0.tdb' Apr 26 04:21:41 192.168.122.209 [44251.798679] [tdb] Close table 'filter0.tdb' Apr 26 04:21:41 192.168.122.209 [44251.799112] [tempesta fw] modules are stopped Apr 26 04:21:41 192.168.122.209 [44251.989030] [tempesta fw] exiting... Apr 26 04:21:41 192.168.122.209 [44252.109430] [tdb] Shutdown Tempesta DB Apr 26 04:21:41 192.168.122.209 [44252.303279] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_cookie_brange_allow_many_cookie Apr 26 04:21:41 192.168.122.209 [44252.315386] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_cookie_brange_check_value Apr 26 04:21:43 192.168.122.209 [44253.463252] [tdb] Start Tempesta DB Apr 26 04:21:43 192.168.122.209 [44253.615311] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:21:44 192.168.122.209 [44255.007249] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44255.007249] Maybe that's fine, but it's worth checking the [44255.007249] config - if there is no relations between the [44255.007249] names, then host name confusion attack is possible. Apr 26 04:21:44 192.168.122.209 [44255.110010] [tempesta fw] Configuration processing is completed. Apr 26 04:21:44 192.168.122.209 [44255.162866] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:21:45 192.168.122.209 [44255.588500] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:21:45 192.168.122.209 [44255.614787] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:21:45 192.168.122.209 [44255.641803] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:21:45 192.168.122.209 [44255.693967] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:21:45 192.168.122.209 [44255.695665] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:21:45 192.168.122.209 [44255.733906] [tempesta fw] Tempesta FW is ready Apr 26 04:21:45 192.168.122.209 [44255.866471] [tempesta fw] Warning: Parser error: state=Req_HdrCookieV input(-8)=0x69('cookie: id=QWErty [44255.866471] [44255.866471] ') data_len=54 off=41 Apr 26 04:21:45 192.168.122.209 [44256.318646] [tdb] Close table 'client0.tdb' Apr 26 04:21:46 192.168.122.209 [44256.510028] [tdb] Close table 'sessions0.tdb' Apr 26 04:21:49 192.168.122.209 [44259.665982] [tdb] Close table 'cache0.tdb' Apr 26 04:21:49 192.168.122.209 [44259.924263] [tdb] Close table 'filter0.tdb' Apr 26 04:21:49 192.168.122.209 [44259.924690] [tempesta fw] modules are stopped Apr 26 04:21:49 192.168.122.209 [44260.118886] [tempesta fw] exiting... Apr 26 04:21:49 192.168.122.209 [44260.267977] [tdb] Shutdown Tempesta DB Apr 26 04:21:50 192.168.122.209 [44260.473522] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_cookie_brange_check_value Apr 26 04:21:50 192.168.122.209 [44260.482803] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_cookie_brange_not_check_name Apr 26 04:21:51 192.168.122.209 [44261.620145] [tdb] Start Tempesta DB Apr 26 04:21:51 192.168.122.209 [44261.764111] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:21:52 192.168.122.209 [44263.139354] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44263.139354] Maybe that's fine, but it's worth checking the [44263.139354] config - if there is no relations between the [44263.139354] names, then host name confusion attack is possible. Apr 26 04:21:52 192.168.122.209 [44263.242072] [tempesta fw] Configuration processing is completed. Apr 26 04:21:52 192.168.122.209 [44263.294160] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:21:53 192.168.122.209 [44263.712980] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:21:53 192.168.122.209 [44263.739053] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:21:53 192.168.122.209 [44263.765695] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:21:53 192.168.122.209 [44263.806071] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:21:53 192.168.122.209 [44263.807803] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:21:53 192.168.122.209 [44263.846030] [tempesta fw] Tempesta FW is ready Apr 26 04:21:54 192.168.122.209 [44264.399733] [tdb] Close table 'client0.tdb' Apr 26 04:21:54 192.168.122.209 [44264.597498] [tdb] Close table 'sessions0.tdb' Apr 26 04:21:57 192.168.122.209 [44267.752546] [tdb] Close table 'cache0.tdb' Apr 26 04:21:57 192.168.122.209 [44267.984243] [tdb] Close table 'filter0.tdb' Apr 26 04:21:57 192.168.122.209 [44267.984696] [tempesta fw] modules are stopped Apr 26 04:21:57 192.168.122.209 [44268.174918] [tempesta fw] exiting... Apr 26 04:21:57 192.168.122.209 [44268.329846] [tdb] Shutdown Tempesta DB Apr 26 04:21:58 192.168.122.209 [44268.554374] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_cookie_brange_not_check_name Apr 26 04:21:58 192.168.122.209 [44268.563164] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_ctext_vchar_brange_allow Apr 26 04:21:59 192.168.122.209 [44269.740995] [tdb] Start Tempesta DB Apr 26 04:21:59 192.168.122.209 [44269.877339] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:22:00 192.168.122.209 [44271.226788] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44271.226788] Maybe that's fine, but it's worth checking the [44271.226788] config - if there is no relations between the [44271.226788] names, then host name confusion attack is possible. Apr 26 04:22:00 192.168.122.209 [44271.326211] [tempesta fw] Configuration processing is completed. Apr 26 04:22:01 192.168.122.209 [44271.379407] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:22:01 192.168.122.209 [44271.792963] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:22:01 192.168.122.209 [44271.818678] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:22:01 192.168.122.209 [44271.843952] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:22:01 192.168.122.209 [44271.886085] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:22:01 192.168.122.209 [44271.887205] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:22:01 192.168.122.209 [44271.926114] [tempesta fw] Tempesta FW is ready Apr 26 04:22:02 192.168.122.209 [44272.517129] [tdb] Close table 'client0.tdb' Apr 26 04:22:02 192.168.122.209 [44272.733104] [tdb] Close table 'sessions0.tdb' Apr 26 04:22:05 192.168.122.209 [44275.894167] [tdb] Close table 'cache0.tdb' Apr 26 04:22:05 192.168.122.209 [44276.144784] [tdb] Close table 'filter0.tdb' Apr 26 04:22:05 192.168.122.209 [44276.145226] [tempesta fw] modules are stopped Apr 26 04:22:05 192.168.122.209 [44276.352851] [tempesta fw] exiting... Apr 26 04:22:06 192.168.122.209 [44276.508996] [tdb] Shutdown Tempesta DB Apr 26 04:22:06 192.168.122.209 [44276.701673] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_ctext_vchar_brange_allow Apr 26 04:22:06 192.168.122.209 [44276.710717] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_ctext_vchar_brange_disallow Apr 26 04:22:07 192.168.122.209 [44277.904111] [tdb] Start Tempesta DB Apr 26 04:22:07 192.168.122.209 [44278.034694] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:22:09 192.168.122.209 [44279.363512] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44279.363512] Maybe that's fine, but it's worth checking the [44279.363512] config - if there is no relations between the [44279.363512] names, then host name confusion attack is possible. Apr 26 04:22:09 192.168.122.209 [44279.462240] [tempesta fw] Configuration processing is completed. Apr 26 04:22:09 192.168.122.209 [44279.526576] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:22:09 192.168.122.209 [44279.937350] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:22:09 192.168.122.209 [44279.999533] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:22:09 192.168.122.209 [44280.026399] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:22:09 192.168.122.209 [44280.082329] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:22:09 192.168.122.209 [44280.084065] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:22:09 192.168.122.209 [44280.134230] [tempesta fw] Tempesta FW is ready Apr 26 04:22:09 192.168.122.209 [44280.272864] [tempesta fw] Warning: Parser error: state=Req_HdrUser_AgentV input(-8)=0x4d('-agent: Mozilla/5.0 % [44280.272864] [44280.272864] ') data_len=62 off=45 Apr 26 04:22:10 192.168.122.209 [44280.747098] [tdb] Close table 'client0.tdb' Apr 26 04:22:10 192.168.122.209 [44280.948894] [tdb] Close table 'sessions0.tdb' Apr 26 04:22:13 192.168.122.209 [44284.060533] [tdb] Close table 'cache0.tdb' Apr 26 04:22:13 192.168.122.209 [44284.305928] [tdb] Close table 'filter0.tdb' Apr 26 04:22:13 192.168.122.209 [44284.306384] [tempesta fw] modules are stopped Apr 26 04:22:14 192.168.122.209 [44284.517071] [tempesta fw] exiting... Apr 26 04:22:14 192.168.122.209 [44284.653326] [tdb] Shutdown Tempesta DB Apr 26 04:22:14 192.168.122.209 [44284.853318] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_ctext_vchar_brange_disallow Apr 26 04:22:14 192.168.122.209 [44284.865121] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_etag_brange_if_none_match_allow Apr 26 04:22:15 192.168.122.209 [44286.058568] [tdb] Start Tempesta DB Apr 26 04:22:15 192.168.122.209 [44286.182576] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:22:17 192.168.122.209 [44287.563679] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44287.563679] Maybe that's fine, but it's worth checking the [44287.563679] config - if there is no relations between the [44287.563679] names, then host name confusion attack is possible. Apr 26 04:22:17 192.168.122.209 [44287.670519] [tempesta fw] Configuration processing is completed. Apr 26 04:22:17 192.168.122.209 [44287.734549] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:22:17 192.168.122.209 [44288.172085] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:22:17 192.168.122.209 [44288.197783] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:22:17 192.168.122.209 [44288.223531] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:22:17 192.168.122.209 [44288.262374] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:22:17 192.168.122.209 [44288.264107] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:22:17 192.168.122.209 [44288.306299] [tempesta fw] Tempesta FW is ready Apr 26 04:22:18 192.168.122.209 [44288.885892] [tdb] Close table 'client0.tdb' Apr 26 04:22:18 192.168.122.209 [44289.089752] [tdb] Close table 'sessions0.tdb' Apr 26 04:22:21 192.168.122.209 [44292.267197] [tdb] Close table 'cache0.tdb' Apr 26 04:22:22 192.168.122.209 [44292.494467] [tdb] Close table 'filter0.tdb' Apr 26 04:22:22 192.168.122.209 [44292.494901] [tempesta fw] modules are stopped Apr 26 04:22:22 192.168.122.209 [44292.676402] [tempesta fw] exiting... Apr 26 04:22:22 192.168.122.209 [44292.832122] [tdb] Shutdown Tempesta DB Apr 26 04:22:22 192.168.122.209 [44293.055360] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_etag_brange_if_none_match_allow Apr 26 04:22:22 192.168.122.209 [44293.067656] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_etag_brange_if_none_match_allow_all Apr 26 04:22:23 192.168.122.209 [44294.259184] [tdb] Start Tempesta DB Apr 26 04:22:24 192.168.122.209 [44294.418794] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:22:25 192.168.122.209 [44295.755742] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44295.755742] Maybe that's fine, but it's worth checking the [44295.755742] config - if there is no relations between the [44295.755742] names, then host name confusion attack is possible. Apr 26 04:22:25 192.168.122.209 [44295.870535] [tempesta fw] Configuration processing is completed. Apr 26 04:22:25 192.168.122.209 [44295.925554] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:22:25 192.168.122.209 [44296.330226] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:22:26 192.168.122.209 [44296.386166] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:22:26 192.168.122.209 [44296.411338] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:22:26 192.168.122.209 [44296.478491] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:22:26 192.168.122.209 [44296.480255] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:22:26 192.168.122.209 [44296.526424] [tempesta fw] Tempesta FW is ready Apr 26 04:22:26 192.168.122.209 [44297.133045] [tdb] Close table 'client0.tdb' Apr 26 04:22:26 192.168.122.209 [44297.332386] [tdb] Close table 'sessions0.tdb' Apr 26 04:22:30 192.168.122.209 [44300.451223] [tdb] Close table 'cache0.tdb' Apr 26 04:22:30 192.168.122.209 [44300.761777] [tdb] Close table 'filter0.tdb' Apr 26 04:22:30 192.168.122.209 [44300.762208] [tempesta fw] modules are stopped Apr 26 04:22:30 192.168.122.209 [44300.937825] [tempesta fw] exiting... Apr 26 04:22:30 192.168.122.209 [44301.070021] [tdb] Shutdown Tempesta DB Apr 26 04:22:30 192.168.122.209 [44301.294082] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_etag_brange_if_none_match_allow_all Apr 26 04:22:30 192.168.122.209 [44301.311364] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_etag_brange_if_none_match_allow_weak Apr 26 04:22:32 192.168.122.209 [44302.381389] [tdb] Start Tempesta DB Apr 26 04:22:32 192.168.122.209 [44302.524141] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:22:33 192.168.122.209 [44303.891861] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44303.891861] Maybe that's fine, but it's worth checking the [44303.891861] config - if there is no relations between the [44303.891861] names, then host name confusion attack is possible. Apr 26 04:22:33 192.168.122.209 [44303.998607] [tempesta fw] Configuration processing is completed. Apr 26 04:22:33 192.168.122.209 [44304.050898] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:22:34 192.168.122.209 [44304.474879] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:22:34 192.168.122.209 [44304.515850] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:22:34 192.168.122.209 [44304.541156] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:22:34 192.168.122.209 [44304.590592] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:22:34 192.168.122.209 [44304.592312] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:22:34 192.168.122.209 [44304.626536] [tempesta fw] Tempesta FW is ready Apr 26 04:22:34 192.168.122.209 [44305.183966] [tdb] Close table 'client0.tdb' Apr 26 04:22:35 192.168.122.209 [44305.370288] [tdb] Close table 'sessions0.tdb' Apr 26 04:22:38 192.168.122.209 [44308.498216] [tdb] Close table 'cache0.tdb' Apr 26 04:22:38 192.168.122.209 [44308.766192] [tdb] Close table 'filter0.tdb' Apr 26 04:22:38 192.168.122.209 [44308.766677] [tempesta fw] modules are stopped Apr 26 04:22:38 192.168.122.209 [44308.984962] [tempesta fw] exiting... Apr 26 04:22:38 192.168.122.209 [44309.111657] [tdb] Shutdown Tempesta DB Apr 26 04:22:38 192.168.122.209 [44309.305059] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_etag_brange_if_none_match_allow_weak Apr 26 04:22:38 192.168.122.209 [44309.322579] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_etag_brange_if_none_match_disallow Apr 26 04:22:40 192.168.122.209 [44310.399040] [tdb] Start Tempesta DB Apr 26 04:22:40 192.168.122.209 [44310.546143] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:22:41 192.168.122.209 [44311.903951] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44311.903951] Maybe that's fine, but it's worth checking the [44311.903951] config - if there is no relations between the [44311.903951] names, then host name confusion attack is possible. Apr 26 04:22:41 192.168.122.209 [44312.002723] [tempesta fw] Configuration processing is completed. Apr 26 04:22:41 192.168.122.209 [44312.053619] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:22:42 192.168.122.209 [44312.457295] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:22:42 192.168.122.209 [44312.514039] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:22:42 192.168.122.209 [44312.539581] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:22:42 192.168.122.209 [44312.582691] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:22:42 192.168.122.209 [44312.584419] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:22:42 192.168.122.209 [44312.626637] [tempesta fw] Tempesta FW is ready Apr 26 04:22:42 192.168.122.209 [44312.771186] [tempesta fw] Warning: Parser error: state=Req_HdrIf_None_MatchV input(-8)=0x22('-match: "asdfQWErty" [44312.771186] [44312.771186] ') data_len=64 off=48 Apr 26 04:22:42 192.168.122.209 [44313.214435] [tdb] Close table 'client0.tdb' Apr 26 04:22:43 192.168.122.209 [44313.426281] [tdb] Close table 'sessions0.tdb' Apr 26 04:22:46 192.168.122.209 [44316.605950] [tdb] Close table 'cache0.tdb' Apr 26 04:22:46 192.168.122.209 [44316.838619] [tdb] Close table 'filter0.tdb' Apr 26 04:22:46 192.168.122.209 [44316.839068] [tempesta fw] modules are stopped Apr 26 04:22:46 192.168.122.209 [44317.044376] [tempesta fw] exiting... Apr 26 04:22:46 192.168.122.209 [44317.167970] [tdb] Shutdown Tempesta DB Apr 26 04:22:47 192.168.122.209 [44317.386080] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_etag_brange_if_none_match_disallow Apr 26 04:22:47 192.168.122.209 [44317.398639] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_etag_brange_if_none_match_many_values Apr 26 04:22:48 192.168.122.209 [44318.473774] [tdb] Start Tempesta DB Apr 26 04:22:48 192.168.122.209 [44318.632657] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:22:49 192.168.122.209 [44320.036048] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44320.036048] Maybe that's fine, but it's worth checking the [44320.036048] config - if there is no relations between the [44320.036048] names, then host name confusion attack is possible. Apr 26 04:22:49 192.168.122.209 [44320.142801] [tempesta fw] Configuration processing is completed. Apr 26 04:22:49 192.168.122.209 [44320.193075] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:22:50 192.168.122.209 [44320.616258] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:22:50 192.168.122.209 [44320.642725] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:22:50 192.168.122.209 [44320.669177] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:22:50 192.168.122.209 [44320.714803] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:22:50 192.168.122.209 [44320.716528] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:22:50 192.168.122.209 [44320.754743] [tempesta fw] Tempesta FW is ready Apr 26 04:22:50 192.168.122.209 [44321.283731] [tdb] Close table 'client0.tdb' Apr 26 04:22:51 192.168.122.209 [44321.480431] [tdb] Close table 'sessions0.tdb' Apr 26 04:22:54 192.168.122.209 [44324.649821] [tdb] Close table 'cache0.tdb' Apr 26 04:22:54 192.168.122.209 [44324.882094] [tdb] Close table 'filter0.tdb' Apr 26 04:22:54 192.168.122.209 [44324.882525] [tempesta fw] modules are stopped Apr 26 04:22:54 192.168.122.209 [44325.087377] [tempesta fw] exiting... Apr 26 04:22:54 192.168.122.209 [44325.224485] [tdb] Shutdown Tempesta DB Apr 26 04:22:55 192.168.122.209 [44325.451719] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_etag_brange_if_none_match_many_values Apr 26 04:22:55 192.168.122.209 [44325.462727] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_nctl_brange_request_negative Apr 26 04:22:56 192.168.122.209 [44326.616110] [tdb] Start Tempesta DB Apr 26 04:22:56 192.168.122.209 [44326.786115] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:22:57 192.168.122.209 [44328.240419] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44328.240419] Maybe that's fine, but it's worth checking the [44328.240419] config - if there is no relations between the [44328.240419] names, then host name confusion attack is possible. Apr 26 04:22:57 192.168.122.209 [44328.334916] [tempesta fw] Configuration processing is completed. Apr 26 04:22:58 192.168.122.209 [44328.386010] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:22:58 192.168.122.209 [44328.807280] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:22:58 192.168.122.209 [44328.832944] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:22:58 192.168.122.209 [44328.858646] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:22:58 192.168.122.209 [44328.902894] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:22:58 192.168.122.209 [44328.904375] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:22:58 192.168.122.209 [44328.942851] [tempesta fw] Tempesta FW is ready Apr 26 04:22:58 192.168.122.209 [44329.057706] [tempesta fw] Warning: Parser error: state=Req_HdrIf_Modified_SinceV input(-8)=0x4d('-since: Mon, 12 Dec 2016% 13:59:39 GMT [44329.057706] [44329.057706] ') data_len=86 off=52 Apr 26 04:22:59 192.168.122.209 [44329.524506] [tdb] Close table 'client0.tdb' Apr 26 04:22:59 192.168.122.209 [44329.718205] [tdb] Close table 'sessions0.tdb' Apr 26 04:23:02 192.168.122.209 [44332.815118] [tdb] Close table 'cache0.tdb' Apr 26 04:23:02 192.168.122.209 [44333.036074] [tdb] Close table 'filter0.tdb' Apr 26 04:23:02 192.168.122.209 [44333.036521] [tempesta fw] modules are stopped Apr 26 04:23:02 192.168.122.209 [44333.240443] [tempesta fw] exiting... Apr 26 04:23:03 192.168.122.209 [44333.375591] [tdb] Shutdown Tempesta DB Apr 26 04:23:03 192.168.122.209 [44333.584532] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_nctl_brange_request_negative Apr 26 04:23:03 192.168.122.209 [44333.604931] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_nctl_brange_request_positive Apr 26 04:23:04 192.168.122.209 [44334.743291] [tdb] Start Tempesta DB Apr 26 04:23:04 192.168.122.209 [44334.882468] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:23:05 192.168.122.209 [44336.220243] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44336.220243] Maybe that's fine, but it's worth checking the [44336.220243] config - if there is no relations between the [44336.220243] names, then host name confusion attack is possible. Apr 26 04:23:05 192.168.122.209 [44336.323014] [tempesta fw] Configuration processing is completed. Apr 26 04:23:06 192.168.122.209 [44336.375904] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:23:06 192.168.122.209 [44336.778969] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:23:06 192.168.122.209 [44336.841513] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:23:06 192.168.122.209 [44336.868896] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:23:06 192.168.122.209 [44336.922945] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:23:06 192.168.122.209 [44336.924697] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:23:06 192.168.122.209 [44336.962950] [tempesta fw] Tempesta FW is ready Apr 26 04:23:07 192.168.122.209 [44337.522573] [tdb] Close table 'client0.tdb' Apr 26 04:23:07 192.168.122.209 [44337.720981] [tdb] Close table 'sessions0.tdb' Apr 26 04:23:10 192.168.122.209 [44340.843935] [tdb] Close table 'cache0.tdb' Apr 26 04:23:10 192.168.122.209 [44341.087145] [tdb] Close table 'filter0.tdb' Apr 26 04:23:10 192.168.122.209 [44341.087564] [tempesta fw] modules are stopped Apr 26 04:23:10 192.168.122.209 [44341.299162] [tempesta fw] exiting... Apr 26 04:23:11 192.168.122.209 [44341.415181] [tdb] Shutdown Tempesta DB Apr 26 04:23:11 192.168.122.209 [44341.635286] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_nctl_brange_request_positive Apr 26 04:23:11 192.168.122.209 [44341.645620] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_nctl_brange_response_negative Apr 26 04:23:12 192.168.122.209 [44342.838007] [tdb] Start Tempesta DB Apr 26 04:23:12 192.168.122.209 [44342.989440] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:23:13 192.168.122.209 [44344.336355] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44344.336355] Maybe that's fine, but it's worth checking the [44344.336355] config - if there is no relations between the [44344.336355] names, then host name confusion attack is possible. Apr 26 04:23:14 192.168.122.209 [44344.447116] [tempesta fw] Configuration processing is completed. Apr 26 04:23:14 192.168.122.209 [44344.498770] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:23:14 192.168.122.209 [44344.942258] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:23:14 192.168.122.209 [44344.968197] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:23:14 192.168.122.209 [44344.994769] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:23:14 192.168.122.209 [44345.035112] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:23:14 192.168.122.209 [44345.036819] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:23:14 192.168.122.209 [44345.079039] [tempesta fw] Tempesta FW is ready Apr 26 04:23:14 192.168.122.209 [44345.214582] [tempesta fw] Warning: Parser error: state=Resp_HdrDateV input(-8)=0x4d(' [44345.214582] date: Mon, 12 Dec 2016% 13:59:39 GMT [44345.214582] content-') data_len=76 off=23 Apr 26 04:23:14 192.168.122.209 [44345.216553] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 04:23:14 192.168.122.209 [44345.225561] [tempesta fw] Warning: Parser error: state=Resp_HdrExpiresV input(-8)=0x4d('xpires: Mon, 12 Dec 2016% 13:59:39 GMT [44345.225561] content-') data_len=79 off=26 Apr 26 04:23:14 192.168.122.209 [44345.227522] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 04:23:14 192.168.122.209 [44345.238065] [tempesta fw] Warning: Parser error: state=Resp_HdrLast_ModifiedV input(-8)=0x4d('dified: Mon, 12 Dec 2016% 13:59:39 GMT [44345.238065] content-') data_len=85 off=32 Apr 26 04:23:14 192.168.122.209 [44345.242382] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 04:23:15 192.168.122.209 [44345.714206] [tdb] Close table 'client0.tdb' Apr 26 04:23:15 192.168.122.209 [44345.927474] [tdb] Close table 'sessions0.tdb' Apr 26 04:23:18 192.168.122.209 [44349.066593] [tdb] Close table 'cache0.tdb' Apr 26 04:23:18 192.168.122.209 [44349.337457] [tdb] Close table 'filter0.tdb' Apr 26 04:23:18 192.168.122.209 [44349.337878] [tempesta fw] modules are stopped Apr 26 04:23:19 192.168.122.209 [44349.537818] [tempesta fw] exiting... Apr 26 04:23:19 192.168.122.209 [44349.646578] [tdb] Shutdown Tempesta DB Apr 26 04:23:19 192.168.122.209 [44349.847257] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_nctl_brange_response_negative Apr 26 04:23:19 192.168.122.209 [44349.865802] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_nctl_brange_response_positive Apr 26 04:23:20 192.168.122.209 [44351.099317] [tdb] Start Tempesta DB Apr 26 04:23:20 192.168.122.209 [44351.264505] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:23:22 192.168.122.209 [44352.700467] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44352.700467] Maybe that's fine, but it's worth checking the [44352.700467] config - if there is no relations between the [44352.700467] names, then host name confusion attack is possible. Apr 26 04:23:22 192.168.122.209 [44352.815889] [tempesta fw] Configuration processing is completed. Apr 26 04:23:22 192.168.122.209 [44352.874378] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:23:22 192.168.122.209 [44353.291125] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:23:22 192.168.122.209 [44353.353037] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:23:23 192.168.122.209 [44353.392801] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:23:23 192.168.122.209 [44353.463179] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:23:23 192.168.122.209 [44353.464896] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:23:23 192.168.122.209 [44353.503112] [tempesta fw] Tempesta FW is ready Apr 26 04:23:23 192.168.122.209 [44354.120150] [tdb] Close table 'client0.tdb' Apr 26 04:23:23 192.168.122.209 [44354.314192] [tdb] Close table 'sessions0.tdb' Apr 26 04:23:27 192.168.122.209 [44357.459806] [tdb] Close table 'cache0.tdb' Apr 26 04:23:27 192.168.122.209 [44357.704210] [tdb] Close table 'filter0.tdb' Apr 26 04:23:27 192.168.122.209 [44357.704704] [tempesta fw] modules are stopped Apr 26 04:23:27 192.168.122.209 [44357.890140] [tempesta fw] exiting... Apr 26 04:23:27 192.168.122.209 [44357.997956] [tdb] Shutdown Tempesta DB Apr 26 04:23:27 192.168.122.209 [44358.221241] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_nctl_brange_response_positive Apr 26 04:23:27 192.168.122.209 [44358.234756] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_qetoken_brange_disallow_equal Apr 26 04:23:29 192.168.122.209 [44359.373518] [tdb] Start Tempesta DB Apr 26 04:23:29 192.168.122.209 [44359.528592] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:23:30 192.168.122.209 [44360.948600] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44360.948600] Maybe that's fine, but it's worth checking the [44360.948600] config - if there is no relations between the [44360.948600] names, then host name confusion attack is possible. Apr 26 04:23:30 192.168.122.209 [44361.055347] [tempesta fw] Configuration processing is completed. Apr 26 04:23:30 192.168.122.209 [44361.114414] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:23:31 192.168.122.209 [44361.587517] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:23:31 192.168.122.209 [44361.616469] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:23:31 192.168.122.209 [44361.645186] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:23:31 192.168.122.209 [44361.707315] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:23:31 192.168.122.209 [44361.709069] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:23:31 192.168.122.209 [44361.747295] [tempesta fw] Tempesta FW is ready Apr 26 04:23:31 192.168.122.209 [44361.898669] [tempesta fw] Warning: Parser error: state=Req_HdrCache_ControlV input(-8)=0x75('ontrol: unknown=value [44361.898669] [44361.898669] ') data_len=65 off=48 Apr 26 04:23:31 192.168.122.209 [44362.347120] [tdb] Close table 'client0.tdb' Apr 26 04:23:32 192.168.122.209 [44362.521943] [tdb] Close table 'sessions0.tdb' Apr 26 04:23:35 192.168.122.209 [44365.688676] [tdb] Close table 'cache0.tdb' Apr 26 04:23:35 192.168.122.209 [44365.946773] [tdb] Close table 'filter0.tdb' Apr 26 04:23:35 192.168.122.209 [44365.947254] [tempesta fw] modules are stopped Apr 26 04:23:35 192.168.122.209 [44366.146986] [tempesta fw] exiting... Apr 26 04:23:35 192.168.122.209 [44366.271658] [tdb] Shutdown Tempesta DB Apr 26 04:23:36 192.168.122.209 [44366.476580] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_qetoken_brange_disallow_equal Apr 26 04:23:36 192.168.122.209 [44366.488224] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_qetoken_brange_negative Apr 26 04:23:37 192.168.122.209 [44367.658929] [tdb] Start Tempesta DB Apr 26 04:23:37 192.168.122.209 [44367.821163] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:23:38 192.168.122.209 [44369.252645] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44369.252645] Maybe that's fine, but it's worth checking the [44369.252645] config - if there is no relations between the [44369.252645] names, then host name confusion attack is possible. Apr 26 04:23:39 192.168.122.209 [44369.379422] [tempesta fw] Configuration processing is completed. Apr 26 04:23:39 192.168.122.209 [44369.432586] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:23:39 192.168.122.209 [44369.905111] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:23:39 192.168.122.209 [44369.933706] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:23:39 192.168.122.209 [44369.961038] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:23:39 192.168.122.209 [44370.003431] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:23:39 192.168.122.209 [44370.005161] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:23:39 192.168.122.209 [44370.059373] [tempesta fw] Tempesta FW is ready Apr 26 04:23:39 192.168.122.209 [44370.191756] [tempesta fw] Warning: Parser error: state=Req_HdrCache_ControlV input(-8)=0x75('ontrol: unkno%wn=value% [44370.191756] [44370.191756] ') data_len=67 off=48 Apr 26 04:23:40 192.168.122.209 [44370.621587] [tdb] Close table 'client0.tdb' Apr 26 04:23:40 192.168.122.209 [44370.831965] [tdb] Close table 'sessions0.tdb' Apr 26 04:23:43 192.168.122.209 [44374.031408] [tdb] Close table 'cache0.tdb' Apr 26 04:23:43 192.168.122.209 [44374.289147] [tdb] Close table 'filter0.tdb' Apr 26 04:23:43 192.168.122.209 [44374.289582] [tempesta fw] modules are stopped Apr 26 04:23:44 192.168.122.209 [44374.468426] [tempesta fw] exiting... Apr 26 04:23:44 192.168.122.209 [44374.613987] [tdb] Shutdown Tempesta DB Apr 26 04:23:44 192.168.122.209 [44374.817326] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_qetoken_brange_negative Apr 26 04:23:44 192.168.122.209 [44374.829377] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_qetoken_brange_positive Apr 26 04:23:45 192.168.122.209 [44375.947300] [tdb] Start Tempesta DB Apr 26 04:23:45 192.168.122.209 [44376.122506] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:23:47 192.168.122.209 [44377.524808] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44377.524808] Maybe that's fine, but it's worth checking the [44377.524808] config - if there is no relations between the [44377.524808] names, then host name confusion attack is possible. Apr 26 04:23:47 192.168.122.209 [44377.639565] [tempesta fw] Configuration processing is completed. Apr 26 04:23:47 192.168.122.209 [44377.690772] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:23:47 192.168.122.209 [44378.148745] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:23:47 192.168.122.209 [44378.179180] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:23:47 192.168.122.209 [44378.206149] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:23:47 192.168.122.209 [44378.243555] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:23:47 192.168.122.209 [44378.245296] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:23:47 192.168.122.209 [44378.287463] [tempesta fw] Tempesta FW is ready Apr 26 04:23:48 192.168.122.209 [44378.894541] [tdb] Close table 'client0.tdb' Apr 26 04:23:48 192.168.122.209 [44379.073529] [tdb] Close table 'sessions0.tdb' Apr 26 04:23:51 192.168.122.209 [44382.284415] [tdb] Close table 'cache0.tdb' Apr 26 04:23:52 192.168.122.209 [44382.509837] [tdb] Close table 'filter0.tdb' Apr 26 04:23:52 192.168.122.209 [44382.510269] [tempesta fw] modules are stopped Apr 26 04:23:52 192.168.122.209 [44382.743120] [tempesta fw] exiting... Apr 26 04:23:52 192.168.122.209 [44382.932722] [tdb] Shutdown Tempesta DB Apr 26 04:23:52 192.168.122.209 [44383.146893] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_qetoken_brange_positive Apr 26 04:23:52 192.168.122.209 [44383.169475] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_token_brange_negative Apr 26 04:23:54 192.168.122.209 [44384.375217] [tdb] Start Tempesta DB Apr 26 04:23:54 192.168.122.209 [44384.528638] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:23:55 192.168.122.209 [44385.924895] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44385.924895] Maybe that's fine, but it's worth checking the [44385.924895] config - if there is no relations between the [44385.924895] names, then host name confusion attack is possible. Apr 26 04:23:55 192.168.122.209 [44386.027647] [tempesta fw] Configuration processing is completed. Apr 26 04:23:55 192.168.122.209 [44386.079965] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:23:56 192.168.122.209 [44386.519783] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:23:56 192.168.122.209 [44386.551776] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:23:56 192.168.122.209 [44386.583610] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:23:56 192.168.122.209 [44386.631631] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:23:56 192.168.122.209 [44386.633365] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:23:56 192.168.122.209 [44386.687595] [tempesta fw] Tempesta FW is ready Apr 26 04:23:56 192.168.122.209 [44386.825263] [tempesta fw] Warning: Parser error: state=Req_HdrCookieV input(-8)=0x75('cookie: unknown%=value [44386.825263] [44386.825263] ') data_len=59 off=41 Apr 26 04:23:56 192.168.122.209 [44387.228707] [tdb] Close table 'client0.tdb' Apr 26 04:23:57 192.168.122.209 [44387.453395] [tdb] Close table 'sessions0.tdb' Apr 26 04:24:00 192.168.122.209 [44390.657624] [tdb] Close table 'cache0.tdb' Apr 26 04:24:00 192.168.122.209 [44390.920921] [tdb] Close table 'filter0.tdb' Apr 26 04:24:00 192.168.122.209 [44390.921377] [tempesta fw] modules are stopped Apr 26 04:24:00 192.168.122.209 [44391.120326] [tempesta fw] exiting... Apr 26 04:24:00 192.168.122.209 [44391.254725] [tdb] Shutdown Tempesta DB Apr 26 04:24:01 192.168.122.209 [44391.462946] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_token_brange_negative Apr 26 04:24:01 192.168.122.209 [44391.476629] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_token_brange_positive Apr 26 04:24:02 192.168.122.209 [44392.671844] [tdb] Start Tempesta DB Apr 26 04:24:02 192.168.122.209 [44392.838860] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:24:03 192.168.122.209 [44394.261041] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44394.261041] Maybe that's fine, but it's worth checking the [44394.261041] config - if there is no relations between the [44394.261041] names, then host name confusion attack is possible. Apr 26 04:24:04 192.168.122.209 [44394.371751] [tempesta fw] Configuration processing is completed. Apr 26 04:24:04 192.168.122.209 [44394.428395] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:24:04 192.168.122.209 [44394.839329] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:24:04 192.168.122.209 [44394.864862] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:24:04 192.168.122.209 [44394.890493] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:24:04 192.168.122.209 [44394.935683] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:24:04 192.168.122.209 [44394.937412] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:24:04 192.168.122.209 [44394.983674] [tempesta fw] Tempesta FW is ready Apr 26 04:24:05 192.168.122.209 [44395.545236] [tdb] Close table 'client0.tdb' Apr 26 04:24:05 192.168.122.209 [44395.763209] [tdb] Close table 'sessions0.tdb' Apr 26 04:24:08 192.168.122.209 [44398.940999] [tdb] Close table 'cache0.tdb' Apr 26 04:24:08 192.168.122.209 [44399.177831] [tdb] Close table 'filter0.tdb' Apr 26 04:24:08 192.168.122.209 [44399.178257] [tempesta fw] modules are stopped Apr 26 04:24:09 192.168.122.209 [44399.371277] [tempesta fw] exiting... Apr 26 04:24:09 192.168.122.209 [44399.507661] [tdb] Shutdown Tempesta DB Apr 26 04:24:09 192.168.122.209 [44399.719246] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_token_brange_positive Apr 26 04:24:09 192.168.122.209 [44399.731977] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_uri_brange_blocked_percent Apr 26 04:24:10 192.168.122.209 [44400.919049] [tdb] Start Tempesta DB Apr 26 04:24:10 192.168.122.209 [44401.071822] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:24:12 192.168.122.209 [44402.433104] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44402.433104] Maybe that's fine, but it's worth checking the [44402.433104] config - if there is no relations between the [44402.433104] names, then host name confusion attack is possible. Apr 26 04:24:12 192.168.122.209 [44402.535855] [tempesta fw] Configuration processing is completed. Apr 26 04:24:12 192.168.122.209 [44402.588215] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:24:12 192.168.122.209 [44403.021072] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:24:12 192.168.122.209 [44403.046694] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:24:12 192.168.122.209 [44403.072770] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:24:12 192.168.122.209 [44403.127833] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:24:12 192.168.122.209 [44403.129550] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:24:12 192.168.122.209 [44403.167809] [tempesta fw] Tempesta FW is ready Apr 26 04:24:12 192.168.122.209 [44403.293466] [tempesta fw] Warning: Parser error: state=Req_UriAbsoluteForm input(-4)=0x6a('GET js%a HTTP/1.1 [44403.293466] Host: localhost [44403.293466] [44403.293466] ') data_len=38 off=4 Apr 26 04:24:13 192.168.122.209 [44403.758937] [tdb] Close table 'client0.tdb' Apr 26 04:24:13 192.168.122.209 [44403.953373] [tdb] Close table 'sessions0.tdb' Apr 26 04:24:16 192.168.122.209 [44407.068912] [tdb] Close table 'cache0.tdb' Apr 26 04:24:16 192.168.122.209 [44407.287134] [tdb] Close table 'filter0.tdb' Apr 26 04:24:16 192.168.122.209 [44407.287575] [tempesta fw] modules are stopped Apr 26 04:24:17 192.168.122.209 [44407.516209] [tempesta fw] exiting... Apr 26 04:24:17 192.168.122.209 [44407.661306] [tdb] Shutdown Tempesta DB Apr 26 04:24:17 192.168.122.209 [44407.876854] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_uri_brange_blocked_percent Apr 26 04:24:17 192.168.122.209 [44407.888948] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_uri_brange_issue_2030 Apr 26 04:24:18 192.168.122.209 [44409.024044] [tdb] Start Tempesta DB Apr 26 04:24:18 192.168.122.209 [44409.149485] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:24:20 192.168.122.209 [44410.557188] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44410.557188] Maybe that's fine, but it's worth checking the [44410.557188] config - if there is no relations between the [44410.557188] names, then host name confusion attack is possible. Apr 26 04:24:20 192.168.122.209 [44410.659985] [tempesta fw] Configuration processing is completed. Apr 26 04:24:20 192.168.122.209 [44410.710836] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:24:20 192.168.122.209 [44411.126737] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:24:20 192.168.122.209 [44411.152701] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:24:20 192.168.122.209 [44411.178840] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:24:20 192.168.122.209 [44411.231951] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:24:20 192.168.122.209 [44411.233669] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:24:20 192.168.122.209 [44411.275929] [tempesta fw] Tempesta FW is ready Apr 26 04:24:21 192.168.122.209 [44411.854507] [tdb] Close table 'client0.tdb' Apr 26 04:24:21 192.168.122.209 [44412.057237] [tdb] Close table 'sessions0.tdb' Apr 26 04:24:24 192.168.122.209 [44415.126885] [tdb] Close table 'cache0.tdb' Apr 26 04:24:25 192.168.122.209 [44415.384499] [tdb] Close table 'filter0.tdb' Apr 26 04:24:25 192.168.122.209 [44415.384939] [tempesta fw] modules are stopped Apr 26 04:24:25 192.168.122.209 [44415.583870] [tempesta fw] exiting... Apr 26 04:24:25 192.168.122.209 [44415.700460] [tdb] Shutdown Tempesta DB Apr 26 04:24:25 192.168.122.209 [44415.897310] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_uri_brange_issue_2030 Apr 26 04:24:25 192.168.122.209 [44415.909719] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_uri_brange_not_blocked_percent Apr 26 04:24:26 192.168.122.209 [44417.023500] [tdb] Start Tempesta DB Apr 26 04:24:26 192.168.122.209 [44417.172967] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:24:28 192.168.122.209 [44418.573320] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44418.573320] Maybe that's fine, but it's worth checking the [44418.573320] config - if there is no relations between the [44418.573320] names, then host name confusion attack is possible. Apr 26 04:24:28 192.168.122.209 [44418.676135] [tempesta fw] Configuration processing is completed. Apr 26 04:24:28 192.168.122.209 [44418.728013] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:24:28 192.168.122.209 [44419.166449] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:24:28 192.168.122.209 [44419.192432] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:24:28 192.168.122.209 [44419.218372] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:24:28 192.168.122.209 [44419.272081] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:24:28 192.168.122.209 [44419.273793] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:24:28 192.168.122.209 [44419.307990] [tempesta fw] Tempesta FW is ready Apr 26 04:24:29 192.168.122.209 [44419.934854] [tdb] Close table 'client0.tdb' Apr 26 04:24:29 192.168.122.209 [44420.128086] [tdb] Close table 'sessions0.tdb' Apr 26 04:24:32 192.168.122.209 [44423.292572] [tdb] Close table 'cache0.tdb' Apr 26 04:24:33 192.168.122.209 [44423.558217] [tdb] Close table 'filter0.tdb' Apr 26 04:24:33 192.168.122.209 [44423.558673] [tempesta fw] modules are stopped Apr 26 04:24:33 192.168.122.209 [44423.777025] [tempesta fw] exiting... Apr 26 04:24:33 192.168.122.209 [44423.938238] [tdb] Shutdown Tempesta DB Apr 26 04:24:33 192.168.122.209 [44424.134245] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_uri_brange_not_blocked_percent Apr 26 04:24:33 192.168.122.209 [44424.156963] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_uri_brange_referer_header_allowed_character Apr 26 04:24:34 192.168.122.209 [44425.274820] [tdb] Start Tempesta DB Apr 26 04:24:35 192.168.122.209 [44425.429004] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:24:36 192.168.122.209 [44426.781463] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44426.781463] Maybe that's fine, but it's worth checking the [44426.781463] config - if there is no relations between the [44426.781463] names, then host name confusion attack is possible. Apr 26 04:24:36 192.168.122.209 [44426.884187] [tempesta fw] Configuration processing is completed. Apr 26 04:24:36 192.168.122.209 [44426.949650] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:24:37 192.168.122.209 [44427.381616] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:24:37 192.168.122.209 [44427.407636] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:24:37 192.168.122.209 [44427.434825] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:24:37 192.168.122.209 [44427.488158] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:24:37 192.168.122.209 [44427.489907] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:24:37 192.168.122.209 [44427.532129] [tempesta fw] Tempesta FW is ready Apr 26 04:24:37 192.168.122.209 [44428.095316] [tdb] Close table 'client0.tdb' Apr 26 04:24:37 192.168.122.209 [44428.275042] [tdb] Close table 'sessions0.tdb' Apr 26 04:24:41 192.168.122.209 [44431.472675] [tdb] Close table 'cache0.tdb' Apr 26 04:24:41 192.168.122.209 [44431.728219] [tdb] Close table 'filter0.tdb' Apr 26 04:24:41 192.168.122.209 [44431.728656] [tempesta fw] modules are stopped Apr 26 04:24:41 192.168.122.209 [44431.941989] [tempesta fw] exiting... Apr 26 04:24:41 192.168.122.209 [44432.129953] [tdb] Shutdown Tempesta DB Apr 26 04:24:41 192.168.122.209 [44432.297405] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_uri_brange_referer_header_allowed_character Apr 26 04:24:41 192.168.122.209 [44432.309653] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_uri_brange_referer_header_disallowed_character Apr 26 04:24:43 192.168.122.209 [44433.503981] [tdb] Start Tempesta DB Apr 26 04:24:43 192.168.122.209 [44433.650793] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:24:44 192.168.122.209 [44435.081503] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44435.081503] Maybe that's fine, but it's worth checking the [44435.081503] config - if there is no relations between the [44435.081503] names, then host name confusion attack is possible. Apr 26 04:24:44 192.168.122.209 [44435.176296] [tempesta fw] Configuration processing is completed. Apr 26 04:24:44 192.168.122.209 [44435.231042] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:24:45 192.168.122.209 [44435.637907] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:24:45 192.168.122.209 [44435.701693] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:24:45 192.168.122.209 [44435.726891] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:24:45 192.168.122.209 [44435.772246] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:24:45 192.168.122.209 [44435.773961] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:24:45 192.168.122.209 [44435.812191] [tempesta fw] Tempesta FW is ready Apr 26 04:24:45 192.168.122.209 [44435.962649] [tempesta fw] Warning: Parser error: state=Req_HdrRefererV input(-8)=0x2f('eferer: /example+ [44435.962649] [44435.962649] ') data_len=55 off=42 Apr 26 04:24:46 192.168.122.209 [44436.396744] [tdb] Close table 'client0.tdb' Apr 26 04:24:46 192.168.122.209 [44436.623260] [tdb] Close table 'sessions0.tdb' Apr 26 04:24:49 192.168.122.209 [44439.756028] [tdb] Close table 'cache0.tdb' Apr 26 04:24:49 192.168.122.209 [44440.014327] [tdb] Close table 'filter0.tdb' Apr 26 04:24:49 192.168.122.209 [44440.014763] [tempesta fw] modules are stopped Apr 26 04:24:49 192.168.122.209 [44440.223925] [tempesta fw] exiting... Apr 26 04:24:50 192.168.122.209 [44440.371401] [tdb] Shutdown Tempesta DB Apr 26 04:24:50 192.168.122.209 [44440.574063] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_uri_brange_referer_header_disallowed_character Apr 26 04:24:50 192.168.122.209 [44440.595090] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_xff_brange_allow_ipv4 Apr 26 04:24:51 192.168.122.209 [44441.706586] [tdb] Start Tempesta DB Apr 26 04:24:51 192.168.122.209 [44441.856800] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:24:52 192.168.122.209 [44443.265565] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44443.265565] Maybe that's fine, but it's worth checking the [44443.265565] config - if there is no relations between the [44443.265565] names, then host name confusion attack is possible. Apr 26 04:24:53 192.168.122.209 [44443.368390] [tempesta fw] Configuration processing is completed. Apr 26 04:24:53 192.168.122.209 [44443.432676] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:24:53 192.168.122.209 [44443.869069] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:24:53 192.168.122.209 [44443.896088] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:24:53 192.168.122.209 [44443.922735] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:24:53 192.168.122.209 [44443.972354] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:24:53 192.168.122.209 [44443.974162] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:24:53 192.168.122.209 [44444.016293] [tempesta fw] Tempesta FW is ready Apr 26 04:24:54 192.168.122.209 [44444.632765] [tdb] Close table 'client0.tdb' Apr 26 04:24:54 192.168.122.209 [44444.823992] [tdb] Close table 'sessions0.tdb' Apr 26 04:24:57 192.168.122.209 [44447.953923] [tdb] Close table 'cache0.tdb' Apr 26 04:24:57 192.168.122.209 [44448.182587] [tdb] Close table 'filter0.tdb' Apr 26 04:24:57 192.168.122.209 [44448.183024] [tempesta fw] modules are stopped Apr 26 04:24:57 192.168.122.209 [44448.363436] [tempesta fw] exiting... Apr 26 04:24:58 192.168.122.209 [44448.510485] [tdb] Shutdown Tempesta DB Apr 26 04:24:58 192.168.122.209 [44448.695389] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_xff_brange_allow_ipv4 Apr 26 04:24:58 192.168.122.209 [44448.715846] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_xff_brange_allow_ipv6 Apr 26 04:24:59 192.168.122.209 [44449.854422] [tdb] Start Tempesta DB Apr 26 04:24:59 192.168.122.209 [44450.000199] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:25:01 192.168.122.209 [44451.401704] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44451.401704] Maybe that's fine, but it's worth checking the [44451.401704] config - if there is no relations between the [44451.401704] names, then host name confusion attack is possible. Apr 26 04:25:01 192.168.122.209 [44451.520495] [tempesta fw] Configuration processing is completed. Apr 26 04:25:01 192.168.122.209 [44451.572953] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:25:01 192.168.122.209 [44451.994040] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:25:01 192.168.122.209 [44452.050142] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:25:01 192.168.122.209 [44452.075739] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:25:01 192.168.122.209 [44452.124376] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:25:01 192.168.122.209 [44452.125148] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:25:01 192.168.122.209 [44452.176403] [tempesta fw] Tempesta FW is ready Apr 26 04:25:02 192.168.122.209 [44452.723515] [tdb] Close table 'client0.tdb' Apr 26 04:25:02 192.168.122.209 [44452.920466] [tdb] Close table 'sessions0.tdb' Apr 26 04:25:05 192.168.122.209 [44456.061792] [tdb] Close table 'cache0.tdb' Apr 26 04:25:05 192.168.122.209 [44456.293225] [tdb] Close table 'filter0.tdb' Apr 26 04:25:05 192.168.122.209 [44456.293685] [tempesta fw] modules are stopped Apr 26 04:25:06 192.168.122.209 [44456.482642] [tempesta fw] exiting... Apr 26 04:25:06 192.168.122.209 [44456.588638] [tdb] Shutdown Tempesta DB Apr 26 04:25:06 192.168.122.209 [44456.761810] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_xff_brange_allow_ipv6 Apr 26 04:25:06 192.168.122.209 [44456.774223] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_xff_brange_allow_many_ip Apr 26 04:25:07 192.168.122.209 [44457.961588] [tdb] Start Tempesta DB Apr 26 04:25:07 192.168.122.209 [44458.105133] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:25:09 192.168.122.209 [44459.533817] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44459.533817] Maybe that's fine, but it's worth checking the [44459.533817] config - if there is no relations between the [44459.533817] names, then host name confusion attack is possible. Apr 26 04:25:09 192.168.122.209 [44459.640589] [tempesta fw] Configuration processing is completed. Apr 26 04:25:09 192.168.122.209 [44459.693556] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:25:09 192.168.122.209 [44460.160535] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:25:09 192.168.122.209 [44460.186068] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:25:09 192.168.122.209 [44460.212196] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:25:09 192.168.122.209 [44460.256557] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:25:09 192.168.122.209 [44460.258295] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:25:09 192.168.122.209 [44460.328546] [tempesta fw] Tempesta FW is ready Apr 26 04:25:10 192.168.122.209 [44460.939369] [tdb] Close table 'client0.tdb' Apr 26 04:25:10 192.168.122.209 [44461.140636] [tdb] Close table 'sessions0.tdb' Apr 26 04:25:13 192.168.122.209 [44464.239780] [tdb] Close table 'cache0.tdb' Apr 26 04:25:14 192.168.122.209 [44464.464181] [tdb] Close table 'filter0.tdb' Apr 26 04:25:14 192.168.122.209 [44464.464627] [tempesta fw] modules are stopped Apr 26 04:25:14 192.168.122.209 [44464.670897] [tempesta fw] exiting... Apr 26 04:25:14 192.168.122.209 [44464.815252] [tdb] Shutdown Tempesta DB Apr 26 04:25:14 192.168.122.209 [44465.030272] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_xff_brange_allow_many_ip Apr 26 04:25:14 192.168.122.209 [44465.044286] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_xff_brange_disallow_ipv4 Apr 26 04:25:15 192.168.122.209 [44466.278881] [tdb] Start Tempesta DB Apr 26 04:25:16 192.168.122.209 [44466.422975] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:25:17 192.168.122.209 [44467.825921] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44467.825921] Maybe that's fine, but it's worth checking the [44467.825921] config - if there is no relations between the [44467.825921] names, then host name confusion attack is possible. Apr 26 04:25:17 192.168.122.209 [44467.944748] [tempesta fw] Configuration processing is completed. Apr 26 04:25:17 192.168.122.209 [44467.999560] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:25:18 192.168.122.209 [44468.413622] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:25:18 192.168.122.209 [44468.440197] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:25:18 192.168.122.209 [44468.466224] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:25:18 192.168.122.209 [44468.516676] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:25:18 192.168.122.209 [44468.518435] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:25:18 192.168.122.209 [44468.568577] [tempesta fw] Tempesta FW is ready Apr 26 04:25:18 192.168.122.209 [44468.713612] [tempesta fw] Warning: Parser error: state=Req_HdrX_Forwarded_ForV input(-8)=0x35('ed-for: 5.10.50.6 [44468.713612] [44468.713612] ') data_len=63 off=50 Apr 26 04:25:18 192.168.122.209 [44469.137258] [tdb] Close table 'client0.tdb' Apr 26 04:25:18 192.168.122.209 [44469.344467] [tdb] Close table 'sessions0.tdb' Apr 26 04:25:22 192.168.122.209 [44472.555514] [tdb] Close table 'cache0.tdb' Apr 26 04:25:22 192.168.122.209 [44472.812874] [tdb] Close table 'filter0.tdb' Apr 26 04:25:22 192.168.122.209 [44472.813312] [tempesta fw] modules are stopped Apr 26 04:25:22 192.168.122.209 [44473.002170] [tempesta fw] exiting... Apr 26 04:25:22 192.168.122.209 [44473.118098] [tdb] Shutdown Tempesta DB Apr 26 04:25:23 192.168.122.209 [44473.410159] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_xff_brange_disallow_ipv4 Apr 26 04:25:23 192.168.122.209 [44473.422576] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_xff_brange_disallow_ipv6 Apr 26 04:25:24 192.168.122.209 [44474.918534] [tdb] Start Tempesta DB Apr 26 04:25:24 192.168.122.209 [44475.100799] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:25:26 192.168.122.209 [44476.910160] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44476.910160] Maybe that's fine, but it's worth checking the [44476.910160] config - if there is no relations between the [44476.910160] names, then host name confusion attack is possible. Apr 26 04:25:27 192.168.122.209 [44477.609136] [tempesta fw] Configuration processing is completed. Apr 26 04:25:27 192.168.122.209 [44477.696869] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:25:27 192.168.122.209 [44478.171965] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:25:27 192.168.122.209 [44478.199241] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:25:27 192.168.122.209 [44478.226309] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:25:28 192.168.122.209 [44478.768837] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:25:28 192.168.122.209 [44478.770654] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:25:28 192.168.122.209 [44479.052737] [tempesta fw] Tempesta FW is ready Apr 26 04:25:29 192.168.122.209 [44479.396303] [tempesta fw] Warning: Parser error: state=Req_HdrX_Forwarded_ForV input(-8)=0x32('ed-for: 2001:db8:85a3:8d3:1319:8a2e:370:7348 [44479.396303] [44479.396303] ') data_len=90 off=50 Apr 26 04:25:29 192.168.122.209 [44479.890605] [tdb] Close table 'client0.tdb' Apr 26 04:25:29 192.168.122.209 [44480.105843] [tdb] Close table 'sessions0.tdb' Apr 26 04:25:32 192.168.122.209 [44483.284545] [tdb] Close table 'cache0.tdb' Apr 26 04:25:33 192.168.122.209 [44483.517415] [tdb] Close table 'filter0.tdb' Apr 26 04:25:33 192.168.122.209 [44483.517844] [tempesta fw] modules are stopped Apr 26 04:25:33 192.168.122.209 [44483.729522] [tempesta fw] exiting... Apr 26 04:25:33 192.168.122.209 [44483.867413] [tdb] Shutdown Tempesta DB Apr 26 04:25:33 192.168.122.209 [44484.066619] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_xff_brange_disallow_ipv6 Apr 26 04:25:33 192.168.122.209 [44484.090037] Start test: t_fault_injection.test_fault_injection_base.TestFailFunction.test_crypto_alloc_aead_atomic_h2 Apr 26 04:25:34 192.168.122.209 [44485.250879] [tdb] Start Tempesta DB Apr 26 04:25:35 192.168.122.209 [44485.403985] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:25:36 192.168.122.209 [44486.802171] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44486.802171] Maybe that's fine, but it's worth checking the [44486.802171] config - if there is no relations between the [44486.802171] names, then host name confusion attack is possible. Apr 26 04:25:36 192.168.122.209 [44486.920955] [tempesta fw] Configuration processing is completed. Apr 26 04:25:36 192.168.122.209 [44486.972205] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:25:37 192.168.122.209 [44487.383333] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:25:37 192.168.122.209 [44487.409447] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:25:37 192.168.122.209 [44487.436132] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:25:37 192.168.122.209 [44487.488915] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:25:37 192.168.122.209 [44487.490626] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:25:37 192.168.122.209 [44487.528870] [tempesta fw] Tempesta FW is ready Apr 26 04:25:37 192.168.122.209 [44487.734883] FAULT_INJECTION: forcing a failure. [44487.734883] name fail_function, interval 0, probability 100, space 0, times 1 Apr 26 04:25:37 192.168.122.209 [44487.736741] CPU: 2 PID: 302879 Comm: python3.10 Tainted: G OE 5.10.35.tfw-39c65d3-debug #1 Apr 26 04:25:37 192.168.122.209 [44487.738214] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 Apr 26 04:25:37 192.168.122.209 [44487.739649] Call Trace: Apr 26 04:25:37 192.168.122.209 [44487.740062] Apr 26 04:25:37 192.168.122.209 [44487.740433] dump_stack+0x96/0xc4 Apr 26 04:25:37 192.168.122.209 [44487.740979] should_fail.cold+0x5/0xa Apr 26 04:25:37 192.168.122.209 [44487.741578] fei_kprobe_handler+0x23/0x60 Apr 26 04:25:37 192.168.122.209 [44487.742233] ? crypto_alloc_aead_atomic+0x1/0x30 Apr 26 04:25:37 192.168.122.209 [44487.742999] kprobe_ftrace_handler+0xbe/0x150 Apr 26 04:25:37 192.168.122.209 [44487.743701] ? crypto_alloc_aead_atomic+0x5/0x30 Apr 26 04:25:37 192.168.122.209 [44487.744465] ? ttls_cipher_setup+0x4e/0xe0 [tempesta_tls] Apr 26 04:25:37 192.168.122.209 [44487.745020] ftrace_ops_assist_func+0xef/0x1b0 Apr 26 04:25:37 192.168.122.209 [44487.745422] ? aead_register_instance+0xd0/0xd0 Apr 26 04:25:37 192.168.122.209 [44487.745842] 0xffffffffc16e00e3 Apr 26 04:25:37 192.168.122.209 [44487.746138] RIP: 0010:crypto_alloc_aead_atomic+0x1/0x30 Apr 26 04:25:37 192.168.122.209 [44487.746591] Code: c3 48 8d 7b 6c e8 7f 9e c2 ff 8b 43 6c 89 43 40 eb ad 0f 0b b8 ea ff ff ff 5b 41 5c 41 5d 5d c3 b8 ea ff ff ff eb d3 66 90 e8 <4b> 4c e7 0b 55 48 89 e5 e8 42 a7 ff ff 48 85 c0 74 16 48 89 c7 ba Apr 26 04:25:37 192.168.122.209 [44487.748248] RSP: 0018:ffff888147f08b40 EFLAGS: 00000246 ORIG_RAX: 0000000000000000 Apr 26 04:25:37 192.168.122.209 [44487.748919] RAX: 0000000000000000 RBX: ffff888147f08d00 RCX: ffffffffc19578d5 Apr 26 04:25:37 192.168.122.209 [44487.749539] RDX: dffffc0000000000 RSI: 0000000000000000 RDI: ffff88811c0b2c48 Apr 26 04:25:37 192.168.122.209 [44487.750180] RBP: ffff888147f08b70 R08: ffffffffc196ff90 R09: ffff888147f08328 Apr 26 04:25:37 192.168.122.209 [44487.750809] R10: ffffed1028fe1070 R11: 0000000000000001 R12: ffff888076c42a10 Apr 26 04:25:37 192.168.122.209 [44487.751455] R13: ffffffffc1991bc0 R14: ffff888076c42a18 R15: 0000000000000010 Apr 26 04:25:37 192.168.122.209 [44487.752096] ? ttls_derive_keys+0x4c0/0xab0 [tempesta_tls] Apr 26 04:25:37 192.168.122.209 [44487.752596] ? ttls_cipher_setup+0x45/0xe0 [tempesta_tls] Apr 26 04:25:37 192.168.122.209 [44487.753097] ? crypto_alloc_aead_atomic+0x5/0x30 Apr 26 04:25:37 192.168.122.209 [44487.753544] ? ttls_cipher_setup+0x4e/0xe0 [tempesta_tls] Apr 26 04:25:37 192.168.122.209 [44487.754032] ? crypto_alloc_aead_atomic+0x5/0x30 Apr 26 04:25:37 192.168.122.209 [44487.754484] ? ttls_cipher_setup+0x4e/0xe0 [tempesta_tls] Apr 26 04:25:37 192.168.122.209 [44487.754988] ttls_derive_keys+0x517/0xab0 [tempesta_tls] Apr 26 04:25:37 192.168.122.209 [44487.755477] ? ttls_update_checksum+0x220/0x220 [tempesta_tls] Apr 26 04:25:37 192.168.122.209 [44487.756011] ? sha256_avx2_update+0x15/0x20 [sha256_ssse3] Apr 26 04:25:37 192.168.122.209 [44487.756514] ttls_handshake_server_step+0xb07/0x3950 [tempesta_tls] Apr 26 04:25:37 192.168.122.209 [44487.757121] ? ttls_handshake_server_step+0xb07/0x3950 [tempesta_tls] Apr 26 04:25:37 192.168.122.209 [44487.757708] ? loopback_xmit+0x15e/0x1b0 Apr 26 04:25:37 192.168.122.209 [44487.758077] ? ttls_parse_client_hello+0x2c60/0x2c60 [tempesta_tls] Apr 26 04:25:37 192.168.122.209 [44487.758649] ? netdev_core_pick_tx+0x120/0x120 Apr 26 04:25:37 192.168.122.209 [44487.759068] ? __kasan_check_write+0x14/0x20 Apr 26 04:25:37 192.168.122.209 [44487.759502] ? nf_conntrack_in+0x7c0/0x9b0 [nf_conntrack] Apr 26 04:25:37 192.168.122.209 [44487.759987] ? dev_queue_xmit+0x10/0x20 Apr 26 04:25:37 192.168.122.209 [44487.760346] ? ip_finish_output2+0x351/0xa80 Apr 26 04:25:37 192.168.122.209 [44487.760738] ? __ip_flush_pending_frames.constprop.0+0x130/0x130 Apr 26 04:25:37 192.168.122.209 [44487.761279] ? cgroup_bpf_release+0x400/0x400 Apr 26 04:25:37 192.168.122.209 [44487.761670] ? __ip_finish_output+0x16b/0x340 Apr 26 04:25:37 192.168.122.209 [44487.762067] ? ip_finish_output+0x2d/0xe0 Apr 26 04:25:37 192.168.122.209 [44487.762434] ? ip_output+0x133/0x210 Apr 26 04:25:37 192.168.122.209 [44487.762777] ? ip_mc_output+0x4e0/0x4e0 Apr 26 04:25:37 192.168.122.209 [44487.763147] ? __ip_finish_output+0x340/0x340 Apr 26 04:25:37 192.168.122.209 [44487.763540] ? ipv4_dst_check+0x6d/0xa0 Apr 26 04:25:37 192.168.122.209 [44487.763892] ? __ip_queue_xmit+0x35e/0x7d0 Apr 26 04:25:37 192.168.122.209 [44487.764271] ttls_recv+0x53d/0xbc0 [tempesta_tls] Apr 26 04:25:37 192.168.122.209 [44487.764698] ? ttls_handle_alert+0x50/0x50 [tempesta_tls] Apr 26 04:25:37 192.168.122.209 [44487.765219] ss_skb_process+0x270/0x2f0 [tempesta_fw] Apr 26 04:25:37 192.168.122.209 [44487.765680] ? ttls_handle_alert+0x50/0x50 [tempesta_tls] Apr 26 04:25:37 192.168.122.209 [44487.766196] ? tfw_sock_srv_exit+0x30/0x30 [tempesta_fw] Apr 26 04:25:37 192.168.122.209 [44487.766686] ? _raw_write_lock_irqsave+0xe0/0xe0 Apr 26 04:25:37 192.168.122.209 [44487.767147] tfw_tls_connection_recv+0x14e/0x730 [tempesta_fw] Apr 26 04:25:37 192.168.122.209 [44487.767667] ? __kasan_check_write+0x14/0x20 Apr 26 04:25:37 192.168.122.209 [44487.768088] ? tfw_tls_connection_lost+0x40/0x40 [tempesta_fw] Apr 26 04:25:37 192.168.122.209 [44487.768633] ? ss_skb_unroll+0x3d6/0x540 [tempesta_fw] Apr 26 04:25:37 192.168.122.209 [44487.769159] ss_tcp_process_data+0x436/0x8b0 [tempesta_fw] Apr 26 04:25:37 192.168.122.209 [44487.769675] ? __sk_close_locked+0x100/0x100 [tempesta_fw] Apr 26 04:25:37 192.168.122.209 [44487.770204] ss_tcp_data_ready+0x7b/0x150 [tempesta_fw] Apr 26 04:25:37 192.168.122.209 [44487.770660] tcp_data_ready+0x73/0x210 Apr 26 04:25:37 192.168.122.209 [44487.770981] tcp_data_queue+0x1085/0x1d80 Apr 26 04:25:37 192.168.122.209 [44487.771320] ? tcp_validate_incoming+0x1fa/0xa30 Apr 26 04:25:37 192.168.122.209 [44487.771710] ? tcp_data_ready+0x210/0x210 Apr 26 04:25:37 192.168.122.209 [44487.772049] ? tcp_enter_cwr+0x1c0/0x1c0 Apr 26 04:25:37 192.168.122.209 [44487.772376] ? kvm_clock_get_cycles+0x11/0x20 Apr 26 04:25:37 192.168.122.209 [44487.772767] ? ktime_get+0x4f/0xb0 Apr 26 04:25:37 192.168.122.209 [44487.773075] tcp_rcv_established+0x422/0xb40 Apr 26 04:25:37 192.168.122.209 [44487.773477] ? tcp_parse_md5sig_option+0x20/0xb0 Apr 26 04:25:37 192.168.122.209 [44487.773899] ? tcp_data_queue+0x1d80/0x1d80 Apr 26 04:25:37 192.168.122.209 [44487.774279] ? __kasan_check_read+0x11/0x20 Apr 26 04:25:37 192.168.122.209 [44487.774651] tcp_v4_do_rcv+0x25f/0x360 Apr 26 04:25:37 192.168.122.209 [44487.774987] tcp_v4_rcv+0x1600/0x1770 Apr 26 04:25:37 192.168.122.209 [44487.775313] ? tcp_v4_early_demux+0x2f0/0x2f0 Apr 26 04:25:37 192.168.122.209 [44487.775695] ip_protocol_deliver_rcu+0x46/0x2e0 Apr 26 04:25:37 192.168.122.209 [44487.776100] ip_local_deliver_finish+0xc6/0xe0 Apr 26 04:25:37 192.168.122.209 [44487.776488] ip_local_deliver+0x1f5/0x210 Apr 26 04:25:37 192.168.122.209 [44487.776865] ? ip_local_deliver_finish+0xe0/0xe0 Apr 26 04:25:37 192.168.122.209 [44487.777291] ? nf_nat_inet_fn+0x2b3/0x440 [nf_nat] Apr 26 04:25:37 192.168.122.209 [44487.777720] ? ip_protocol_deliver_rcu+0x2e0/0x2e0 Apr 26 04:25:37 192.168.122.209 [44487.778154] ? ip_rcv_finish_core.constprop.0+0x17c/0x890 Apr 26 04:25:37 192.168.122.209 [44487.778631] ip_rcv_finish+0xcf/0xf0 Apr 26 04:25:37 192.168.122.209 [44487.778961] ip_rcv+0x16d/0x180 Apr 26 04:25:37 192.168.122.209 [44487.779286] ? ip_local_deliver+0x210/0x210 Apr 26 04:25:37 192.168.122.209 [44487.779656] ? ip_rcv_finish_core.constprop.0+0x890/0x890 Apr 26 04:25:37 192.168.122.209 [44487.780129] ? __kasan_check_read+0x11/0x20 Apr 26 04:25:37 192.168.122.209 [44487.780506] ? ip_local_deliver+0x210/0x210 Apr 26 04:25:37 192.168.122.209 [44487.780889] __netif_receive_skb_one_core+0x132/0x140 Apr 26 04:25:37 192.168.122.209 [44487.781325] ? napi_gro_receive+0x260/0x260 Apr 26 04:25:37 192.168.122.209 [44487.781691] ? __kasan_check_write+0x14/0x20 Apr 26 04:25:37 192.168.122.209 [44487.782110] ? _raw_spin_lock+0x7b/0xd0 Apr 26 04:25:37 192.168.122.209 [44487.782452] __netif_receive_skb+0x26/0xb0 Apr 26 04:25:37 192.168.122.209 [44487.782817] process_backlog+0xfe/0x290 Apr 26 04:25:37 192.168.122.209 [44487.783157] net_rx_action+0x287/0x6b0 Apr 26 04:25:37 192.168.122.209 [44487.783497] ? napi_complete_done+0x2c0/0x2c0 Apr 26 04:25:37 192.168.122.209 [44487.783910] ? switch_fpu_return+0x120/0x120 Apr 26 04:25:37 192.168.122.209 [44487.784294] __do_softirq+0xfe/0x383 Apr 26 04:25:37 192.168.122.209 [44487.784631] asm_call_irq_on_stack+0xf/0x20 Apr 26 04:25:37 192.168.122.209 [44487.785028] Apr 26 04:25:37 192.168.122.209 [44487.785237] do_softirq_own_stack+0x3d/0x50 Apr 26 04:25:37 192.168.122.209 [44487.785620] do_softirq+0x72/0x90 Apr 26 04:25:37 192.168.122.209 [44487.785926] __local_bh_enable_ip+0x50/0x60 Apr 26 04:25:37 192.168.122.209 [44487.786301] ip_finish_output2+0x351/0xa80 Apr 26 04:25:37 192.168.122.209 [44487.786678] ? __ip_flush_pending_frames.constprop.0+0x130/0x130 Apr 26 04:25:37 192.168.122.209 [44487.787213] ? cgroup_bpf_release+0x400/0x400 Apr 26 04:25:37 192.168.122.209 [44487.787610] __ip_finish_output+0x16b/0x340 Apr 26 04:25:37 192.168.122.209 [44487.787996] ip_finish_output+0x2d/0xe0 Apr 26 04:25:37 192.168.122.209 [44487.788349] ip_output+0x133/0x210 Apr 26 04:25:37 192.168.122.209 [44487.788659] ? ip_mc_output+0x4e0/0x4e0 Apr 26 04:25:37 192.168.122.209 [44487.789012] ? __ip_finish_output+0x340/0x340 Apr 26 04:25:37 192.168.122.209 [44487.789403] ? ipv4_dst_check+0x6d/0xa0 Apr 26 04:25:37 192.168.122.209 [44487.789755] __ip_queue_xmit+0x356/0x7d0 Apr 26 04:25:37 192.168.122.209 [44487.790110] ip_queue_xmit+0x3b/0x50 Apr 26 04:25:37 192.168.122.209 [44487.790437] __tcp_transmit_skb+0x152f/0x1730 Apr 26 04:25:37 192.168.122.209 [44487.790841] ? __tcp_select_window+0x370/0x370 Apr 26 04:25:37 192.168.122.209 [44487.791236] ? pvclock_clocksource_read+0xe1/0x1a0 Apr 26 04:25:37 192.168.122.209 [44487.791652] ? __kasan_check_read+0x11/0x20 Apr 26 04:25:37 192.168.122.209 [44487.792023] tcp_write_xmit+0x796/0x2a50 Apr 26 04:25:37 192.168.122.209 [44487.792377] ? iov_iter_advance+0x12b/0x5f0 Apr 26 04:25:37 192.168.122.209 [44487.792770] __tcp_push_pending_frames+0x5f/0x1a0 Apr 26 04:25:37 192.168.122.209 [44487.793190] tcp_push+0x209/0x2b0 Apr 26 04:25:37 192.168.122.209 [44487.793493] tcp_sendmsg_locked+0x13fa/0x15f0 Apr 26 04:25:37 192.168.122.209 [44487.793893] ? skb_do_copy_data_nocache+0x1b0/0x1b0 Apr 26 04:25:37 192.168.122.209 [44487.794330] ? __kasan_check_write+0x14/0x20 Apr 26 04:25:37 192.168.122.209 [44487.794714] ? _raw_spin_lock_bh+0x86/0xe0 Apr 26 04:25:37 192.168.122.209 [44487.795095] ? inet_recvmsg+0x105/0x270 Apr 26 04:25:37 192.168.122.209 [44487.795441] ? tcp_release_cb+0x46/0x1f0 Apr 26 04:25:37 192.168.122.209 [44487.795805] tcp_sendmsg+0x2d/0x50 Apr 26 04:25:37 192.168.122.209 [44487.796115] inet_sendmsg+0x64/0xa0 Apr 26 04:25:37 192.168.122.209 [44487.796430] ? inet_send_prepare+0x120/0x120 Apr 26 04:25:37 192.168.122.209 [44487.796822] sock_sendmsg+0x97/0xa0 Apr 26 04:25:37 192.168.122.209 [44487.797146] sock_write_iter+0x14c/0x200 Apr 26 04:25:37 192.168.122.209 [44487.797502] ? sock_sendmsg+0xa0/0xa0 Apr 26 04:25:37 192.168.122.209 [44487.797844] ? fsnotify+0x81c/0x890 Apr 26 04:25:37 192.168.122.209 [44487.798165] new_sync_write+0x3aa/0x3c0 Apr 26 04:25:37 192.168.122.209 [44487.798515] ? new_sync_read+0x3c0/0x3c0 Apr 26 04:25:37 192.168.122.209 [44487.798874] ? rw_verify_area+0x7c/0x150 Apr 26 04:25:37 192.168.122.209 [44487.799226] vfs_write+0x311/0x3d0 Apr 26 04:25:37 192.168.122.209 [44487.799535] ksys_write+0x138/0x170 Apr 26 04:25:37 192.168.122.209 [44487.799861] ? __ia32_sys_read+0x50/0x50 Apr 26 04:25:37 192.168.122.209 [44487.800216] ? __kasan_check_read+0x11/0x20 Apr 26 04:25:37 192.168.122.209 [44487.800603] ? fpregs_assert_state_consistent+0x5a/0x70 Apr 26 04:25:37 192.168.122.209 [44487.801091] __x64_sys_write+0x42/0x50 Apr 26 04:25:37 192.168.122.209 [44487.801443] do_syscall_64+0x38/0x90 Apr 26 04:25:37 192.168.122.209 [44487.801772] entry_SYSCALL_64_after_hwframe+0x44/0xa9 Apr 26 04:25:37 192.168.122.209 [44487.802222] RIP: 0033:0x7f88f225b5ad Apr 26 04:25:37 192.168.122.209 [44487.802545] Code: e5 48 83 ec 20 48 89 55 e8 48 89 75 f0 89 7d f8 e8 b8 bf f7 ff 48 8b 55 e8 48 8b 75 f0 41 89 c0 8b 7d f8 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 33 44 89 c7 48 89 45 f8 e8 0f c0 f7 ff 48 8b Apr 26 04:25:37 192.168.122.209 [44487.804215] RSP: 002b:00007f88ed97c400 EFLAGS: 00000293 ORIG_RAX: 0000000000000001 Apr 26 04:25:37 192.168.122.209 [44487.804905] RAX: ffffffffffffffda RBX: 00007f88e83e9ac0 RCX: 00007f88f225b5ad Apr 26 04:25:37 192.168.122.209 [44487.805535] RDX: 000000000000007e RSI: 00007f88e807c430 RDI: 0000000000000006 Apr 26 04:25:37 192.168.122.209 [44487.806180] RBP: 00007f88ed97c420 R08: 0000000000000000 R09: 0000000000000000 Apr 26 04:25:37 192.168.122.209 [44487.806829] R10: 0000000000000000 R11: 0000000000000293 R12: 000000000000007e Apr 26 04:25:37 192.168.122.209 [44487.807452] R13: 00007f88e807c430 R14: 00007f88ed97c540 R15: 00007f88ed97c4f0 Apr 26 04:25:37 192.168.122.209 [44487.808108] [tempesta tls] Warning: cannot setup encryption cipher, -12 Apr 26 04:25:37 192.168.122.209 [44487.808713] [tempesta tls] Warning: [::ffff:127.0.0.2] KeyExchange: cannot derive keys, crypto error -12 Apr 26 04:25:37 192.168.122.209 [44488.304366] [tdb] Close table 'client0.tdb' Apr 26 04:25:38 192.168.122.209 [44488.508835] [tdb] Close table 'sessions0.tdb' Apr 26 04:25:41 192.168.122.209 [44491.593380] [tdb] Close table 'cache0.tdb' Apr 26 04:25:41 192.168.122.209 [44491.849213] [tdb] Close table 'filter0.tdb' Apr 26 04:25:41 192.168.122.209 [44491.849652] [tempesta fw] modules are stopped Apr 26 04:25:41 192.168.122.209 [44492.043984] [tempesta fw] exiting... Apr 26 04:25:41 192.168.122.209 [44492.186425] [tdb] Shutdown Tempesta DB Apr 26 04:25:42 192.168.122.209 [44492.405417] End test: t_fault_injection.test_fault_injection_base.TestFailFunction.test_crypto_alloc_aead_atomic_h2 Apr 26 04:25:42 192.168.122.209 [44492.414880] Start test: t_fault_injection.test_fault_injection_base.TestFailFunction.test_crypto_alloc_aead_atomic_ssl Apr 26 04:25:43 192.168.122.209 [44493.566141] [tdb] Start Tempesta DB Apr 26 04:25:43 192.168.122.209 [44493.711015] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:25:44 192.168.122.209 [44495.069751] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44495.069751] Maybe that's fine, but it's worth checking the [44495.069751] config - if there is no relations between the [44495.069751] names, then host name confusion attack is possible. Apr 26 04:25:44 192.168.122.209 [44495.185352] [tempesta fw] Configuration processing is completed. Apr 26 04:25:44 192.168.122.209 [44495.235309] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:25:45 192.168.122.209 [44495.659570] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:25:45 192.168.122.209 [44495.686504] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:25:45 192.168.122.209 [44495.713321] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:25:45 192.168.122.209 [44495.765015] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:25:45 192.168.122.209 [44495.766739] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:25:45 192.168.122.209 [44495.804959] [tempesta fw] Tempesta FW is ready Apr 26 04:25:45 192.168.122.209 [44495.997041] FAULT_INJECTION: forcing a failure. [44495.997041] name fail_function, interval 0, probability 100, space 0, times 1 Apr 26 04:25:45 192.168.122.209 [44496.000223] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G OE 5.10.35.tfw-39c65d3-debug #1 Apr 26 04:25:45 192.168.122.209 [44496.002558] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 Apr 26 04:25:45 192.168.122.209 [44496.004924] Call Trace: Apr 26 04:25:45 192.168.122.209 [44496.005295] Apr 26 04:25:45 192.168.122.209 [44496.005580] dump_stack+0x96/0xc4 Apr 26 04:25:45 192.168.122.209 [44496.006035] should_fail.cold+0x5/0xa Apr 26 04:25:45 192.168.122.209 [44496.006541] fei_kprobe_handler+0x23/0x60 Apr 26 04:25:45 192.168.122.209 [44496.007080] ? crypto_alloc_aead_atomic+0x1/0x30 Apr 26 04:25:45 192.168.122.209 [44496.007693] kprobe_ftrace_handler+0xbe/0x150 Apr 26 04:25:45 192.168.122.209 [44496.008274] ? crypto_alloc_aead_atomic+0x5/0x30 Apr 26 04:25:45 192.168.122.209 [44496.008899] ? ttls_cipher_setup+0x4e/0xe0 [tempesta_tls] Apr 26 04:25:45 192.168.122.209 [44496.009604] ftrace_ops_assist_func+0xef/0x1b0 Apr 26 04:25:45 192.168.122.209 [44496.010193] ? aead_register_instance+0xd0/0xd0 Apr 26 04:25:45 192.168.122.209 [44496.010793] 0xffffffffc16e00e3 Apr 26 04:25:45 192.168.122.209 [44496.011220] RIP: 0010:crypto_alloc_aead_atomic+0x1/0x30 Apr 26 04:25:45 192.168.122.209 [44496.011903] Code: c3 48 8d 7b 6c e8 7f 9e c2 ff 8b 43 6c 89 43 40 eb ad 0f 0b b8 ea ff ff ff 5b 41 5c 41 5d 5d c3 b8 ea ff ff ff eb d3 66 90 e8 <4b> 4c e7 0b 55 48 89 e5 e8 42 a7 ff ff 48 85 c0 74 16 48 89 c7 ba Apr 26 04:25:45 192.168.122.209 [44496.014293] RSP: 0018:ffff888147e08b40 EFLAGS: 00000246 ORIG_RAX: 0000000000000000 Apr 26 04:25:45 192.168.122.209 [44496.015075] RAX: 0000000000000000 RBX: ffff888147e08d00 RCX: ffffffffc19578d5 Apr 26 04:25:45 192.168.122.209 [44496.015700] RDX: dffffc0000000000 RSI: 0000000000000000 RDI: ffff88811c0b2c48 Apr 26 04:25:45 192.168.122.209 [44496.016331] RBP: ffff888147e08b70 R08: ffffffffc196ff90 R09: ffff888147e08328 Apr 26 04:25:45 192.168.122.209 [44496.016977] R10: ffffed1028fc1070 R11: 0000000000000001 R12: ffff88805879cc78 Apr 26 04:25:45 192.168.122.209 [44496.017609] R13: ffffffffc1991bc0 R14: ffff88805879cc80 R15: 0000000000000010 Apr 26 04:25:45 192.168.122.209 [44496.018248] ? ttls_derive_keys+0x4c0/0xab0 [tempesta_tls] Apr 26 04:25:45 192.168.122.209 [44496.018737] ? ttls_cipher_setup+0x45/0xe0 [tempesta_tls] Apr 26 04:25:45 192.168.122.209 [44496.019221] ? crypto_alloc_aead_atomic+0x5/0x30 Apr 26 04:25:45 192.168.122.209 [44496.019642] ? ttls_cipher_setup+0x4e/0xe0 [tempesta_tls] Apr 26 04:25:45 192.168.122.209 [44496.020124] ? crypto_alloc_aead_atomic+0x5/0x30 Apr 26 04:25:45 192.168.122.209 [44496.020541] ? ttls_cipher_setup+0x4e/0xe0 [tempesta_tls] Apr 26 04:25:45 192.168.122.209 [44496.021030] ttls_derive_keys+0x517/0xab0 [tempesta_tls] Apr 26 04:25:45 192.168.122.209 [44496.021512] ? ttls_update_checksum+0x220/0x220 [tempesta_tls] Apr 26 04:25:45 192.168.122.209 [44496.022040] ? sha256_avx2_update+0x15/0x20 [sha256_ssse3] Apr 26 04:25:45 192.168.122.209 [44496.022534] ttls_handshake_server_step+0xb07/0x3950 [tempesta_tls] Apr 26 04:25:45 192.168.122.209 [44496.023098] ? ttls_handshake_server_step+0xb07/0x3950 [tempesta_tls] Apr 26 04:25:45 192.168.122.209 [44496.023670] ? loopback_xmit+0x15e/0x1b0 Apr 26 04:25:45 192.168.122.209 [44496.024034] ? ttls_parse_client_hello+0x2c60/0x2c60 [tempesta_tls] Apr 26 04:25:45 192.168.122.209 [44496.024667] ? netdev_core_pick_tx+0x120/0x120 Apr 26 04:25:45 192.168.122.209 [44496.025071] ? __kasan_check_write+0x14/0x20 Apr 26 04:25:45 192.168.122.209 [44496.025475] ? nf_conntrack_in+0x7c0/0x9b0 [nf_conntrack] Apr 26 04:25:45 192.168.122.209 [44496.025957] ? dev_queue_xmit+0x10/0x20 Apr 26 04:25:45 192.168.122.209 [44496.026306] ? ip_finish_output2+0x351/0xa80 Apr 26 04:25:45 192.168.122.209 [44496.026704] ? __ip_flush_pending_frames.constprop.0+0x130/0x130 Apr 26 04:25:45 192.168.122.209 [44496.027252] ? cgroup_bpf_release+0x400/0x400 Apr 26 04:25:45 192.168.122.209 [44496.027659] ? __ip_finish_output+0x16b/0x340 Apr 26 04:25:45 192.168.122.209 [44496.028051] ? ip_finish_output+0x2d/0xe0 Apr 26 04:25:45 192.168.122.209 [44496.028411] ? ip_output+0x133/0x210 Apr 26 04:25:45 192.168.122.209 [44496.028739] ? static_protections+0x98/0x2b0 Apr 26 04:25:45 192.168.122.209 [44496.029122] ? ip_mc_output+0x4e0/0x4e0 Apr 26 04:25:45 192.168.122.209 [44496.029467] ? kasan_save_stack+0x23/0x50 Apr 26 04:25:45 192.168.122.209 [44496.029830] ? lookup_address+0xb0/0xb0 Apr 26 04:25:45 192.168.122.209 [44496.030188] ? __ip_finish_output+0x340/0x340 Apr 26 04:25:45 192.168.122.209 [44496.030593] ? ipv4_dst_check+0x6d/0xa0 Apr 26 04:25:45 192.168.122.209 [44496.030943] ? lookup_address_in_pgd.part.0.constprop.0+0x215/0x280 Apr 26 04:25:45 192.168.122.209 [44496.031490] ? __change_page_attr_set_clr+0xb8d/0x14b0 Apr 26 04:25:45 192.168.122.209 [44496.031960] ttls_recv+0x53d/0xbc0 [tempesta_tls] Apr 26 04:25:45 192.168.122.209 [44496.032395] ? ttls_handle_alert+0x50/0x50 [tempesta_tls] Apr 26 04:25:45 192.168.122.209 [44496.032911] ss_skb_process+0x270/0x2f0 [tempesta_fw] Apr 26 04:25:45 192.168.122.209 [44496.033368] ? ttls_handle_alert+0x50/0x50 [tempesta_tls] Apr 26 04:25:45 192.168.122.209 [44496.033884] ? tfw_sock_srv_exit+0x30/0x30 [tempesta_fw] Apr 26 04:25:45 192.168.122.209 [44496.034354] ? _raw_write_lock_irqsave+0xe0/0xe0 Apr 26 04:25:45 192.168.122.209 [44496.034792] tfw_tls_connection_recv+0x14e/0x730 [tempesta_fw] Apr 26 04:25:45 192.168.122.209 [44496.035310] ? __kasan_check_write+0x14/0x20 Apr 26 04:25:45 192.168.122.209 [44496.035723] ? tfw_tls_connection_lost+0x40/0x40 [tempesta_fw] Apr 26 04:25:45 192.168.122.209 [44496.036279] ? ss_skb_unroll+0x3d6/0x540 [tempesta_fw] Apr 26 04:25:45 192.168.122.209 [44496.036760] ss_tcp_process_data+0x436/0x8b0 [tempesta_fw] Apr 26 04:25:45 192.168.122.209 [44496.037276] ? __sk_close_locked+0x100/0x100 [tempesta_fw] Apr 26 04:25:45 192.168.122.209 [44496.037791] ss_tcp_data_ready+0x7b/0x150 [tempesta_fw] Apr 26 04:25:45 192.168.122.209 [44496.038258] tcp_data_ready+0x73/0x210 Apr 26 04:25:45 192.168.122.209 [44496.038597] tcp_data_queue+0x1085/0x1d80 Apr 26 04:25:45 192.168.122.209 [44496.038960] ? tcp_validate_incoming+0x1fa/0xa30 Apr 26 04:25:45 192.168.122.209 [44496.039374] ? tcp_data_ready+0x210/0x210 Apr 26 04:25:45 192.168.122.209 [44496.039731] ? tcp_enter_cwr+0x1c0/0x1c0 Apr 26 04:25:45 192.168.122.209 [44496.040086] ? kvm_clock_get_cycles+0x11/0x20 Apr 26 04:25:45 192.168.122.209 [44496.040498] ? ktime_get+0x4f/0xb0 Apr 26 04:25:45 192.168.122.209 [44496.040809] tcp_rcv_established+0x422/0xb40 Apr 26 04:25:45 192.168.122.209 [44496.041196] ? tcp_parse_md5sig_option+0x20/0xb0 Apr 26 04:25:45 192.168.122.209 [44496.041606] ? tcp_data_queue+0x1d80/0x1d80 Apr 26 04:25:45 192.168.122.209 [44496.041982] ? __kasan_check_read+0x11/0x20 Apr 26 04:25:45 192.168.122.209 [44496.042364] tcp_v4_do_rcv+0x25f/0x360 Apr 26 04:25:45 192.168.122.209 [44496.042701] tcp_v4_rcv+0x1600/0x1770 Apr 26 04:25:45 192.168.122.209 [44496.043036] ? tcp_v4_early_demux+0x2f0/0x2f0 Apr 26 04:25:45 192.168.122.209 [44496.043427] ip_protocol_deliver_rcu+0x46/0x2e0 Apr 26 04:25:45 192.168.122.209 [44496.043838] ip_local_deliver_finish+0xc6/0xe0 Apr 26 04:25:45 192.168.122.209 [44496.044235] ip_local_deliver+0x1f5/0x210 Apr 26 04:25:45 192.168.122.209 [44496.044595] ? ip_local_deliver_finish+0xe0/0xe0 Apr 26 04:25:45 192.168.122.209 [44496.045041] ? nf_nat_inet_fn+0x2b3/0x440 [nf_nat] Apr 26 04:25:45 192.168.122.209 [44496.045472] ? ip_protocol_deliver_rcu+0x2e0/0x2e0 Apr 26 04:25:45 192.168.122.209 [44496.045900] ? ip_rcv_finish_core.constprop.0+0x17c/0x890 Apr 26 04:25:45 192.168.122.209 [44496.046376] ip_rcv_finish+0xcf/0xf0 Apr 26 04:25:45 192.168.122.209 [44496.046699] ip_rcv+0x16d/0x180 Apr 26 04:25:45 192.168.122.209 [44496.046992] ? ip_local_deliver+0x210/0x210 Apr 26 04:25:45 192.168.122.209 [44496.047367] ? ip_rcv_finish_core.constprop.0+0x890/0x890 Apr 26 04:25:45 192.168.122.209 [44496.047848] ? ip_local_deliver+0x210/0x210 Apr 26 04:25:45 192.168.122.209 [44496.048222] __netif_receive_skb_one_core+0x132/0x140 Apr 26 04:25:45 192.168.122.209 [44496.048674] ? napi_gro_receive+0x260/0x260 Apr 26 04:25:45 192.168.122.209 [44496.049051] ? find_next_bit+0x14/0x20 Apr 26 04:25:45 192.168.122.209 [44496.049399] ? cpumask_next+0x2c/0x40 Apr 26 04:25:45 192.168.122.209 [44496.049728] ? __kasan_check_write+0x14/0x20 Apr 26 04:25:45 192.168.122.209 [44496.050124] ? _raw_spin_lock+0x7b/0xd0 Apr 26 04:25:45 192.168.122.209 [44496.050495] __netif_receive_skb+0x26/0xb0 Apr 26 04:25:45 192.168.122.209 [44496.050867] ? generic_exec_single+0xb1/0x170 Apr 26 04:25:45 192.168.122.209 [44496.051255] process_backlog+0xfe/0x290 Apr 26 04:25:45 192.168.122.209 [44496.051605] net_rx_action+0x287/0x6b0 Apr 26 04:25:45 192.168.122.209 [44496.051947] ? napi_complete_done+0x2c0/0x2c0 Apr 26 04:25:45 192.168.122.209 [44496.052342] ? switch_fpu_return+0x120/0x120 Apr 26 04:25:45 192.168.122.209 [44496.052729] __do_softirq+0xfe/0x383 Apr 26 04:25:45 192.168.122.209 [44496.053065] asm_call_irq_on_stack+0xf/0x20 Apr 26 04:25:45 192.168.122.209 [44496.053443] Apr 26 04:25:45 192.168.122.209 [44496.053643] do_softirq_own_stack+0x3d/0x50 Apr 26 04:25:45 192.168.122.209 [44496.054022] irq_exit_rcu+0xc7/0x120 Apr 26 04:25:45 192.168.122.209 [44496.054355] sysvec_call_function_single+0x3a/0x90 Apr 26 04:25:45 192.168.122.209 [44496.054781] asm_sysvec_call_function_single+0x12/0x20 Apr 26 04:25:45 192.168.122.209 [44496.055241] RIP: 0010:native_safe_halt+0xe/0x10 Apr 26 04:25:45 192.168.122.209 [44496.055639] Code: 49 8b 04 24 a8 08 0f 85 71 ff ff ff e9 0f ff ff ff cc cc cc cc cc cc cc cc cc cc cc e9 07 00 00 00 0f 00 2d d4 62 51 00 fb f4 90 e9 07 00 00 00 0f 00 2d c4 62 51 00 f4 c3 cc cc 0f 1f 44 00 Apr 26 04:25:45 192.168.122.209 [44496.057258] RSP: 0018:ffffffffb7207dc8 EFLAGS: 00000202 Apr 26 04:25:45 192.168.122.209 [44496.057718] RAX: ffffffffb63426a0 RBX: ffffffffb721b100 RCX: ffffffffb632c475 Apr 26 04:25:45 192.168.122.209 [44496.058346] RDX: 000000000aabeb52 RSI: 0000000000000004 RDI: ffff888147e35040 Apr 26 04:25:45 192.168.122.209 [44496.058976] RBP: ffffffffb7207dd0 R08: 0000000000000001 R09: ffff888147e35043 Apr 26 04:25:45 192.168.122.209 [44496.059602] R10: ffffed1028fc6a08 R11: 0000000000000001 R12: 0000000000000000 Apr 26 04:25:45 192.168.122.209 [44496.060226] R13: ffffffffb7ae9360 R14: 0000000000000000 R15: 0000000000000000 Apr 26 04:25:45 192.168.122.209 [44496.060852] ? __cpuidle_text_start+0x8/0x8 Apr 26 04:25:45 192.168.122.209 [44496.061227] ? rcu_eqs_enter.constprop.0+0x85/0xa0 Apr 26 04:25:45 192.168.122.209 [44496.061656] ? default_idle+0xe/0x20 Apr 26 04:25:45 192.168.122.209 [44496.061981] arch_cpu_idle+0x15/0x20 Apr 26 04:25:45 192.168.122.209 [44496.062334] default_idle_call+0x66/0x160 Apr 26 04:25:45 192.168.122.209 [44496.062698] do_idle+0x36f/0x430 Apr 26 04:25:45 192.168.122.209 [44496.063001] ? arch_cpu_idle_exit+0x40/0x40 Apr 26 04:25:45 192.168.122.209 [44496.063376] cpu_startup_entry+0x20/0x30 Apr 26 04:25:45 192.168.122.209 [44496.063738] rest_init+0xc8/0xce Apr 26 04:25:45 192.168.122.209 [44496.064072] arch_call_rest_init+0xe/0x1b Apr 26 04:25:45 192.168.122.209 [44496.064436] start_kernel+0x380/0x39d Apr 26 04:25:45 192.168.122.209 [44496.064767] x86_64_start_reservations+0x24/0x26 Apr 26 04:25:45 192.168.122.209 [44496.065183] x86_64_start_kernel+0x7a/0x7e Apr 26 04:25:45 192.168.122.209 [44496.065550] secondary_startup_64_no_verify+0xb0/0xbb Apr 26 04:25:45 192.168.122.209 [44496.066023] [tempesta tls] Warning: cannot setup encryption cipher, -12 Apr 26 04:25:45 192.168.122.209 [44496.066628] [tempesta tls] Warning: [::ffff:127.0.0.2] KeyExchange: cannot derive keys, crypto error -12 Apr 26 04:25:46 192.168.122.209 [44496.576332] [tdb] Close table 'client0.tdb' Apr 26 04:25:46 192.168.122.209 [44496.781325] [tdb] Close table 'sessions0.tdb' Apr 26 04:25:49 192.168.122.209 [44499.918711] [tdb] Close table 'cache0.tdb' Apr 26 04:25:49 192.168.122.209 [44500.153973] [tdb] Close table 'filter0.tdb' Apr 26 04:25:49 192.168.122.209 [44500.154403] [tempesta fw] modules are stopped Apr 26 04:25:49 192.168.122.209 [44500.349626] [tempesta fw] exiting... Apr 26 04:25:50 192.168.122.209 [44500.480438] [tdb] Shutdown Tempesta DB Apr 26 04:25:50 192.168.122.209 [44500.693669] End test: t_fault_injection.test_fault_injection_base.TestFailFunction.test_crypto_alloc_aead_atomic_ssl Apr 26 04:25:50 192.168.122.209 [44500.705021] Start test: t_fault_injection.test_fault_injection_base.TestFailFunction.test_crypto_alloc_shash_atomic_h2 Apr 26 04:25:51 192.168.122.209 [44501.858366] [tdb] Start Tempesta DB Apr 26 04:25:51 192.168.122.209 [44502.003991] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:25:53 192.168.122.209 [44503.411604] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44503.411604] Maybe that's fine, but it's worth checking the [44503.411604] config - if there is no relations between the [44503.411604] names, then host name confusion attack is possible. Apr 26 04:25:53 192.168.122.209 [44503.553148] [tempesta fw] Configuration processing is completed. Apr 26 04:25:53 192.168.122.209 [44503.601209] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:25:53 192.168.122.209 [44504.013738] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:25:53 192.168.122.209 [44504.039416] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:25:53 192.168.122.209 [44504.065141] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:25:53 192.168.122.209 [44504.109140] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:25:53 192.168.122.209 [44504.110823] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:25:53 192.168.122.209 [44504.149089] [tempesta fw] Tempesta FW is ready Apr 26 04:25:53 192.168.122.209 [44504.334058] FAULT_INJECTION: forcing a failure. [44504.334058] name fail_function, interval 0, probability 100, space 0, times 1 Apr 26 04:25:53 192.168.122.209 [44504.335595] CPU: 1 PID: 1293 Comm: VM Periodic Tas Tainted: G OE 5.10.35.tfw-39c65d3-debug #1 Apr 26 04:25:53 192.168.122.209 [44504.336750] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 Apr 26 04:25:53 192.168.122.209 [44504.337621] Call Trace: Apr 26 04:25:53 192.168.122.209 [44504.337860] Apr 26 04:25:53 192.168.122.209 [44504.338071] dump_stack+0x96/0xc4 Apr 26 04:25:53 192.168.122.209 [44504.338394] should_fail.cold+0x5/0xa Apr 26 04:25:53 192.168.122.209 [44504.338748] fei_kprobe_handler+0x23/0x60 Apr 26 04:25:53 192.168.122.209 [44504.339135] ? crypto_alloc_shash_atomic+0x1/0x30 Apr 26 04:25:53 192.168.122.209 [44504.339579] kprobe_ftrace_handler+0xbe/0x150 Apr 26 04:25:53 192.168.122.209 [44504.340004] ? crypto_alloc_shash_atomic+0x5/0x30 Apr 26 04:25:53 192.168.122.209 [44504.340456] ? ttls_sha256_init_start+0x1b/0xa0 [tempesta_tls] Apr 26 04:25:53 192.168.122.209 [44504.341006] ftrace_ops_assist_func+0xef/0x1b0 Apr 26 04:25:53 192.168.122.209 [44504.341426] ? shash_free_singlespawn_instance+0x30/0x30 Apr 26 04:25:53 192.168.122.209 [44504.341937] 0xffffffffc16e00e3 Apr 26 04:25:53 192.168.122.209 [44504.342240] RIP: 0010:crypto_alloc_shash_atomic+0x1/0x30 Apr 26 04:25:53 192.168.122.209 [44504.342734] Code: 89 e5 41 54 49 89 fc 48 8d bf 38 02 00 00 e8 66 6c ff ff 4c 89 e7 e8 fe ce c1 ff 4c 8b 65 f8 c9 c3 0f 1f 84 00 00 00 00 00 e8 ef e6 0b 55 48 89 e5 e8 d2 4a ff ff 48 85 c0 74 16 48 89 c7 ba Apr 26 04:25:53 192.168.122.209 [44504.344439] RSP: 0018:ffff888147e88dc0 EFLAGS: 00000297 ORIG_RAX: 0000000000000000 Apr 26 04:25:53 192.168.122.209 [44504.345144] RAX: ffff8880298bcbe0 RBX: ffff888024dc9bb0 RCX: ffffffffc196f93d Apr 26 04:25:53 192.168.122.209 [44504.345801] RDX: 000000000000000c RSI: ffff88802d218005 RDI: ffffffffc16ed4c0 Apr 26 04:25:53 192.168.122.209 [44504.346461] RBP: ffff888147e88dd8 R08: ffffffffc196f929 R09: ffff88802a368057 Apr 26 04:25:53 192.168.122.209 [44504.347138] R10: ffffed100546d00a R11: 0000000000000001 R12: ffff8880298bcbe0 Apr 26 04:25:53 192.168.122.209 [44504.347766] R13: ffff8880298bcba8 R14: ffff888024dc9bd0 R15: 0000000000000001 Apr 26 04:25:53 192.168.122.209 [44504.348406] ? ttls_update_checksum+0x79/0x220 [tempesta_tls] Apr 26 04:25:53 192.168.122.209 [44504.348921] ? ttls_update_checksum+0x8d/0x220 [tempesta_tls] Apr 26 04:25:53 192.168.122.209 [44504.349438] ? crypto_alloc_shash_atomic+0x5/0x30 Apr 26 04:25:53 192.168.122.209 [44504.349870] ? ttls_sha256_init_start+0x1b/0xa0 [tempesta_tls] Apr 26 04:25:53 192.168.122.209 [44504.350396] ? crypto_alloc_shash_atomic+0x5/0x30 Apr 26 04:25:53 192.168.122.209 [44504.350826] ? ttls_sha256_init_start+0x1b/0xa0 [tempesta_tls] Apr 26 04:25:53 192.168.122.209 [44504.351359] ttls_update_checksum+0x1ee/0x220 [tempesta_tls] Apr 26 04:25:53 192.168.122.209 [44504.351878] ttls_parse_client_hello+0x636/0x2c60 [tempesta_tls] Apr 26 04:25:53 192.168.122.209 [44504.352421] ttls_handshake_server_step+0x7a7/0x3950 [tempesta_tls] Apr 26 04:25:53 192.168.122.209 [44504.352986] ? ttls_parse_client_hello+0x2c60/0x2c60 [tempesta_tls] Apr 26 04:25:53 192.168.122.209 [44504.353539] ? __cpa_process_fault+0x800/0x800 Apr 26 04:25:53 192.168.122.209 [44504.353944] ? flush_tlb_one_user+0x20/0x20 Apr 26 04:25:53 192.168.122.209 [44504.354322] ? ftrace_graph_ret_addr+0x2a/0xb0 Apr 26 04:25:53 192.168.122.209 [44504.354719] ? stack_trace_save+0x94/0xc0 Apr 26 04:25:53 192.168.122.209 [44504.355086] ? get_stack_info_noinstr+0x17/0xf0 Apr 26 04:25:53 192.168.122.209 [44504.355495] ? ftrace_graph_ret_addr+0x2a/0xb0 Apr 26 04:25:53 192.168.122.209 [44504.355882] ? secondary_startup_64_no_verify+0xb0/0xbb Apr 26 04:25:53 192.168.122.209 [44504.356339] ? update_stack_state+0x1d2/0x280 Apr 26 04:25:53 192.168.122.209 [44504.356717] ? unwind_next_frame.part.0+0x1d9/0x360 Apr 26 04:25:53 192.168.122.209 [44504.357170] ? create_prof_cpu_mask+0x30/0x30 Apr 26 04:25:53 192.168.122.209 [44504.357559] ? unwind_next_frame+0x23/0x40 Apr 26 04:25:53 192.168.122.209 [44504.357927] ? arch_stack_walk+0x88/0xf0 Apr 26 04:25:53 192.168.122.209 [44504.358311] ? secondary_startup_64_no_verify+0xb0/0xbb Apr 26 04:25:53 192.168.122.209 [44504.358781] ? static_protections+0x98/0x2b0 Apr 26 04:25:53 192.168.122.209 [44504.359166] ? lookup_address+0xb0/0xb0 Apr 26 04:25:53 192.168.122.209 [44504.359512] ? lookup_address_in_pgd.part.0.constprop.0+0x215/0x280 Apr 26 04:25:53 192.168.122.209 [44504.360074] ? __change_page_attr_set_clr+0xb8d/0x14b0 Apr 26 04:25:53 192.168.122.209 [44504.360538] ? update_stack_state+0x1d2/0x280 Apr 26 04:25:53 192.168.122.209 [44504.360928] ? __cpa_process_fault+0x800/0x800 Apr 26 04:25:53 192.168.122.209 [44504.361335] ttls_recv+0x53d/0xbc0 [tempesta_tls] Apr 26 04:25:53 192.168.122.209 [44504.361761] ? ttls_handle_alert+0x50/0x50 [tempesta_tls] Apr 26 04:25:53 192.168.122.209 [44504.362282] ss_skb_process+0x270/0x2f0 [tempesta_fw] Apr 26 04:25:53 192.168.122.209 [44504.362740] ? ttls_handle_alert+0x50/0x50 [tempesta_tls] Apr 26 04:25:53 192.168.122.209 [44504.363251] ? tfw_sock_srv_exit+0x30/0x30 [tempesta_fw] Apr 26 04:25:53 192.168.122.209 [44504.363724] ? _raw_write_lock_irqsave+0xe0/0xe0 Apr 26 04:25:53 192.168.122.209 [44504.364174] tfw_tls_connection_recv+0x14e/0x730 [tempesta_fw] Apr 26 04:25:53 192.168.122.209 [44504.364691] ? __kasan_check_write+0x14/0x20 Apr 26 04:25:53 192.168.122.209 [44504.365106] ? tfw_tls_connection_lost+0x40/0x40 [tempesta_fw] Apr 26 04:25:53 192.168.122.209 [44504.365650] ? ss_skb_unroll+0x3d6/0x540 [tempesta_fw] Apr 26 04:25:53 192.168.122.209 [44504.366143] ss_tcp_process_data+0x436/0x8b0 [tempesta_fw] Apr 26 04:25:53 192.168.122.209 [44504.366656] ? __sk_close_locked+0x100/0x100 [tempesta_fw] Apr 26 04:25:54 192.168.122.209 [44504.367149] ? tcp_grow_window+0xce/0x330 Apr 26 04:25:54 192.168.122.209 [44504.367536] ss_tcp_data_ready+0x7b/0x150 [tempesta_fw] Apr 26 04:25:54 192.168.122.209 [44504.368010] tcp_data_ready+0x73/0x210 Apr 26 04:25:54 192.168.122.209 [44504.368350] tcp_data_queue+0x1085/0x1d80 Apr 26 04:25:54 192.168.122.209 [44504.368712] ? tcp_data_ready+0x210/0x210 Apr 26 04:25:54 192.168.122.209 [44504.369078] ? tcp_enter_cwr+0x1c0/0x1c0 Apr 26 04:25:54 192.168.122.209 [44504.369436] ? kvm_clock_get_cycles+0x11/0x20 Apr 26 04:25:54 192.168.122.209 [44504.369825] ? ktime_get+0x4f/0xb0 Apr 26 04:25:54 192.168.122.209 [44504.370139] tcp_rcv_established+0x422/0xb40 Apr 26 04:25:54 192.168.122.209 [44504.370530] ? tcp_data_queue+0x1d80/0x1d80 Apr 26 04:25:54 192.168.122.209 [44504.370913] ? __kasan_check_read+0x11/0x20 Apr 26 04:25:54 192.168.122.209 [44504.371294] tcp_v4_do_rcv+0x25f/0x360 Apr 26 04:25:54 192.168.122.209 [44504.371632] tcp_v4_rcv+0x1600/0x1770 Apr 26 04:25:54 192.168.122.209 [44504.371972] ? tcp_v4_early_demux+0x2f0/0x2f0 Apr 26 04:25:54 192.168.122.209 [44504.372368] ip_protocol_deliver_rcu+0x46/0x2e0 Apr 26 04:25:54 192.168.122.209 [44504.372771] ip_local_deliver_finish+0xc6/0xe0 Apr 26 04:25:54 192.168.122.209 [44504.373175] ip_local_deliver+0x1f5/0x210 Apr 26 04:25:54 192.168.122.209 [44504.373533] ? ip_local_deliver_finish+0xe0/0xe0 Apr 26 04:25:54 192.168.122.209 [44504.373957] ? nf_nat_inet_fn+0x2b3/0x440 [nf_nat] Apr 26 04:25:54 192.168.122.209 [44504.374382] ? ip_protocol_deliver_rcu+0x2e0/0x2e0 Apr 26 04:25:54 192.168.122.209 [44504.374809] ? ip_rcv_finish_core.constprop.0+0x17c/0x890 Apr 26 04:25:54 192.168.122.209 [44504.375298] ip_rcv_finish+0xcf/0xf0 Apr 26 04:25:54 192.168.122.209 [44504.375626] ip_rcv+0x16d/0x180 Apr 26 04:25:54 192.168.122.209 [44504.375912] ? ip_local_deliver+0x210/0x210 Apr 26 04:25:54 192.168.122.209 [44504.376294] ? ip_rcv_finish_core.constprop.0+0x890/0x890 Apr 26 04:25:54 192.168.122.209 [44504.376774] ? ttwu_do_activate+0xa4/0x170 Apr 26 04:25:54 192.168.122.209 [44504.377150] ? ip_local_deliver+0x210/0x210 Apr 26 04:25:54 192.168.122.209 [44504.377526] __netif_receive_skb_one_core+0x132/0x140 Apr 26 04:25:54 192.168.122.209 [44504.377979] ? napi_gro_receive+0x260/0x260 Apr 26 04:25:54 192.168.122.209 [44504.378355] ? __kasan_check_write+0x14/0x20 Apr 26 04:25:54 192.168.122.209 [44504.378746] ? _raw_spin_lock+0x7b/0xd0 Apr 26 04:25:54 192.168.122.209 [44504.379097] __netif_receive_skb+0x26/0xb0 Apr 26 04:25:54 192.168.122.209 [44504.379465] process_backlog+0xfe/0x290 Apr 26 04:25:54 192.168.122.209 [44504.379812] net_rx_action+0x287/0x6b0 Apr 26 04:25:54 192.168.122.209 [44504.380157] ? napi_complete_done+0x2c0/0x2c0 Apr 26 04:25:54 192.168.122.209 [44504.380558] ? switch_fpu_return+0x120/0x120 Apr 26 04:25:54 192.168.122.209 [44504.380949] __do_softirq+0xfe/0x383 Apr 26 04:25:54 192.168.122.209 [44504.381279] asm_call_irq_on_stack+0xf/0x20 Apr 26 04:25:54 192.168.122.209 [44504.381658] Apr 26 04:25:54 192.168.122.209 [44504.381857] do_softirq_own_stack+0x3d/0x50 Apr 26 04:25:54 192.168.122.209 [44504.382237] irq_exit_rcu+0xc7/0x120 Apr 26 04:25:54 192.168.122.209 [44504.382561] sysvec_call_function_single+0x3a/0x90 Apr 26 04:25:54 192.168.122.209 [44504.382997] asm_sysvec_call_function_single+0x12/0x20 Apr 26 04:25:54 192.168.122.209 [44504.383454] RIP: 0010:finish_task_switch+0xa9/0x370 Apr 26 04:25:54 192.168.122.209 [44504.383887] Code: 44 00 00 0f 1f 44 00 00 49 8d 7d 2c e8 00 17 34 00 41 c7 45 2c 00 00 00 00 4c 89 e7 e8 c4 e6 04 00 66 90 fb 66 0f 1f 44 00 00 <65> 48 8b 1c 25 c0 fb 01 00 0f 1f 44 00 00 4d 85 f6 74 3b 65 48 8b Apr 26 04:25:54 192.168.122.209 [44504.385511] RSP: 0018:ffff88811848f8c0 EFLAGS: 00000246 Apr 26 04:25:54 192.168.122.209 [44504.385984] RAX: 0000000000000001 RBX: ffff88810b74a080 RCX: dffffc0000000000 Apr 26 04:25:54 192.168.122.209 [44504.386614] RDX: 0000000000000007 RSI: 0000000000000004 RDI: ffff888147eb41c0 Apr 26 04:25:54 192.168.122.209 [44504.387247] RBP: ffff88811848f900 R08: ffffffffb5153b90 R09: ffff88810b74bf03 Apr 26 04:25:54 192.168.122.209 [44504.387873] R10: ffffed10216e97e0 R11: 0000000000000001 R12: ffff888147eb41c0 Apr 26 04:25:54 192.168.122.209 [44504.388511] R13: ffff888100f2c0c0 R14: ffff888101ae39c0 R15: 0000000000000000 Apr 26 04:25:54 192.168.122.209 [44504.389170] ? finish_task_switch+0x90/0x370 Apr 26 04:25:54 192.168.122.209 [44504.389559] __schedule+0x529/0xd80 Apr 26 04:25:54 192.168.122.209 [44504.389878] ? io_schedule_timeout+0xc0/0xc0 Apr 26 04:25:54 192.168.122.209 [44504.390277] schedule+0x7b/0x130 Apr 26 04:25:54 192.168.122.209 [44504.390572] futex_wait_queue_me+0x170/0x220 Apr 26 04:25:54 192.168.122.209 [44504.390963] ? futex_wait_setup+0x160/0x160 Apr 26 04:25:54 192.168.122.209 [44504.391339] futex_wait+0x197/0x3b0 Apr 26 04:25:54 192.168.122.209 [44504.391660] ? exit_robust_list+0x140/0x140 Apr 26 04:25:54 192.168.122.209 [44504.392040] ? update_cfs_group+0x120/0x160 Apr 26 04:25:54 192.168.122.209 [44504.392444] ? __hrtimer_init+0x100/0x100 Apr 26 04:25:54 192.168.122.209 [44504.392806] ? futex_wake+0x117/0x2d0 Apr 26 04:25:54 192.168.122.209 [44504.393152] ? ttwu_do_wakeup+0xbe/0x240 Apr 26 04:25:54 192.168.122.209 [44504.393504] do_futex+0x23a/0xfa0 Apr 26 04:25:54 192.168.122.209 [44504.393804] ? try_to_wake_up+0x41e/0xa70 Apr 26 04:25:54 192.168.122.209 [44504.394173] ? futex_exit_release+0x110/0x110 Apr 26 04:25:54 192.168.122.209 [44504.394565] ? _raw_read_lock_bh+0x50/0x50 Apr 26 04:25:54 192.168.122.209 [44504.394938] ? __hrtimer_init+0x100/0x100 Apr 26 04:25:54 192.168.122.209 [44504.395300] ? __kasan_check_write+0x14/0x20 Apr 26 04:25:54 192.168.122.209 [44504.395682] ? _copy_from_user+0x41/0x80 Apr 26 04:25:54 192.168.122.209 [44504.396044] ? get_timespec64+0xdd/0x130 Apr 26 04:25:54 192.168.122.209 [44504.396396] ? __ia32_compat_sys_gettimeofday+0x130/0x130 Apr 26 04:25:54 192.168.122.209 [44504.396873] ? ktime_get+0x4f/0xb0 Apr 26 04:25:54 192.168.122.209 [44504.397187] __x64_sys_futex+0x130/0x320 Apr 26 04:25:54 192.168.122.209 [44504.397551] ? __ia32_sys_futex_time32+0x360/0x360 Apr 26 04:25:54 192.168.122.209 [44504.397983] ? __kasan_check_read+0x11/0x20 Apr 26 04:25:54 192.168.122.209 [44504.398370] ? exit_to_user_mode_prepare+0x35/0x150 Apr 26 04:25:54 192.168.122.209 [44504.398797] do_syscall_64+0x38/0x90 Apr 26 04:25:54 192.168.122.209 [44504.399146] entry_SYSCALL_64_after_hwframe+0x44/0xa9 Apr 26 04:25:54 192.168.122.209 [44504.399595] RIP: 0033:0x7fe752eb8d71 Apr 26 04:25:54 192.168.122.209 [44504.399918] Code: 48 89 4d c8 e8 00 f8 ff ff 4c 8b 55 c8 8b 75 dc 45 31 c0 41 89 c5 48 8b 7d d0 41 b9 ff ff ff ff 44 89 e2 b8 ca 00 00 00 0f 05 <44> 89 ef 48 89 c3 e8 54 f8 ff ff e9 65 ff ff ff 0f 1f 80 00 00 00 Apr 26 04:25:54 192.168.122.209 [44504.401567] RSP: 002b:00007fe73410dbf0 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca Apr 26 04:25:54 192.168.122.209 [44504.402241] RAX: ffffffffffffffda RBX: 00007fe752deac28 RCX: 00007fe752eb8d71 Apr 26 04:25:54 192.168.122.209 [44504.402866] RDX: 0000000000000000 RSI: 0000000000000089 RDI: 00007fe752deac54 Apr 26 04:25:54 192.168.122.209 [44504.403497] RBP: 00007fe73410dc30 R08: 0000000000000000 R09: 00000000ffffffff Apr 26 04:25:54 192.168.122.209 [44504.404129] R10: 00007fe73410dd20 R11: 0000000000000246 R12: 0000000000000000 Apr 26 04:25:54 192.168.122.209 [44504.404757] R13: 0000000000000000 R14: 00007fe752deac00 R15: 00007fe752deac54 Apr 26 04:25:54 192.168.122.209 [44504.405416] [tempesta tls] Warning: Cannot setup hash ctx, -12 Apr 26 04:25:54 192.168.122.209 [44504.948207] [tdb] Close table 'client0.tdb' Apr 26 04:25:54 192.168.122.209 [44505.146083] [tdb] Close table 'sessions0.tdb' Apr 26 04:25:57 192.168.122.209 [44508.284398] [tdb] Close table 'cache0.tdb' Apr 26 04:25:58 192.168.122.209 [44508.525236] [tdb] Close table 'filter0.tdb' Apr 26 04:25:58 192.168.122.209 [44508.525668] [tempesta fw] modules are stopped Apr 26 04:25:58 192.168.122.209 [44508.702252] [tempesta fw] exiting... Apr 26 04:25:58 192.168.122.209 [44508.876335] [tdb] Shutdown Tempesta DB Apr 26 04:25:58 192.168.122.209 [44509.111654] End test: t_fault_injection.test_fault_injection_base.TestFailFunction.test_crypto_alloc_shash_atomic_h2 Apr 26 04:25:58 192.168.122.209 [44509.125791] Start test: t_fault_injection.test_fault_injection_base.TestFailFunction.test_crypto_alloc_shash_atomic_ssl Apr 26 04:25:59 192.168.122.209 [44510.328101] [tdb] Start Tempesta DB Apr 26 04:26:00 192.168.122.209 [44510.481225] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:26:01 192.168.122.209 [44511.911632] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44511.911632] Maybe that's fine, but it's worth checking the [44511.911632] config - if there is no relations between the [44511.911632] names, then host name confusion attack is possible. Apr 26 04:26:01 192.168.122.209 [44512.033314] [tempesta fw] Configuration processing is completed. Apr 26 04:26:01 192.168.122.209 [44512.086399] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:26:02 192.168.122.209 [44512.544619] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:26:02 192.168.122.209 [44512.572059] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:26:02 192.168.122.209 [44512.599602] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:26:02 192.168.122.209 [44512.673234] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:26:02 192.168.122.209 [44512.674973] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:26:02 192.168.122.209 [44512.721190] [tempesta fw] Tempesta FW is ready Apr 26 04:26:02 192.168.122.209 [44512.910474] FAULT_INJECTION: forcing a failure. [44512.910474] name fail_function, interval 0, probability 100, space 0, times 1 Apr 26 04:26:02 192.168.122.209 [44512.911963] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G OE 5.10.35.tfw-39c65d3-debug #1 Apr 26 04:26:02 192.168.122.209 [44512.913108] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 Apr 26 04:26:02 192.168.122.209 [44512.914282] Call Trace: Apr 26 04:26:02 192.168.122.209 [44512.914611] Apr 26 04:26:02 192.168.122.209 [44512.914908] dump_stack+0x96/0xc4 Apr 26 04:26:02 192.168.122.209 [44512.915380] should_fail.cold+0x5/0xa Apr 26 04:26:02 192.168.122.209 [44512.915902] fei_kprobe_handler+0x23/0x60 Apr 26 04:26:02 192.168.122.209 [44512.916462] ? crypto_alloc_shash_atomic+0x1/0x30 Apr 26 04:26:02 192.168.122.209 [44512.917115] kprobe_ftrace_handler+0xbe/0x150 Apr 26 04:26:02 192.168.122.209 [44512.917715] ? crypto_alloc_shash_atomic+0x5/0x30 Apr 26 04:26:02 192.168.122.209 [44512.918385] ? ttls_sha256_init_start+0x1b/0xa0 [tempesta_tls] Apr 26 04:26:02 192.168.122.209 [44512.919188] ftrace_ops_assist_func+0xef/0x1b0 Apr 26 04:26:02 192.168.122.209 [44512.919801] ? shash_free_singlespawn_instance+0x30/0x30 Apr 26 04:26:02 192.168.122.209 [44512.920533] 0xffffffffc16e00e3 Apr 26 04:26:02 192.168.122.209 [44512.920981] RIP: 0010:crypto_alloc_shash_atomic+0x1/0x30 Apr 26 04:26:02 192.168.122.209 [44512.921713] Code: 89 e5 41 54 49 89 fc 48 8d bf 38 02 00 00 e8 66 6c ff ff 4c 89 e7 e8 fe ce c1 ff 4c 8b 65 f8 c9 c3 0f 1f 84 00 00 00 00 00 e8 ef e6 0b 55 48 89 e5 e8 d2 4a ff ff 48 85 c0 74 16 48 89 c7 ba Apr 26 04:26:02 192.168.122.209 [44512.924228] RSP: 0018:ffff888147e88dc0 EFLAGS: 00000297 ORIG_RAX: 0000000000000000 Apr 26 04:26:02 192.168.122.209 [44512.925145] RAX: ffff888110f66290 RBX: ffff88810c63b2a0 RCX: ffffffffc196f93d Apr 26 04:26:02 192.168.122.209 [44512.925779] RDX: 000000000000000c RSI: ffff8881036e8005 RDI: ffffffffc16ed4c0 Apr 26 04:26:02 192.168.122.209 [44512.926411] RBP: ffff888147e88dd8 R08: ffffffffc196f929 R09: ffff88803b258057 Apr 26 04:26:02 192.168.122.209 [44512.927036] R10: ffffed100764b00a R11: 0000000000000001 R12: ffff888110f66290 Apr 26 04:26:02 192.168.122.209 [44512.927663] R13: ffff888110f66258 R14: ffff88810c63b2c0 R15: 0000000000000001 Apr 26 04:26:02 192.168.122.209 [44512.928303] ? ttls_update_checksum+0x79/0x220 [tempesta_tls] Apr 26 04:26:02 192.168.122.209 [44512.928821] ? ttls_update_checksum+0x8d/0x220 [tempesta_tls] Apr 26 04:26:02 192.168.122.209 [44512.929338] ? crypto_alloc_shash_atomic+0x5/0x30 Apr 26 04:26:02 192.168.122.209 [44512.929764] ? ttls_sha256_init_start+0x1b/0xa0 [tempesta_tls] Apr 26 04:26:02 192.168.122.209 [44512.930285] ? crypto_alloc_shash_atomic+0x5/0x30 Apr 26 04:26:02 192.168.122.209 [44512.930709] ? ttls_sha256_init_start+0x1b/0xa0 [tempesta_tls] Apr 26 04:26:02 192.168.122.209 [44512.931246] ttls_update_checksum+0x1ee/0x220 [tempesta_tls] Apr 26 04:26:02 192.168.122.209 [44512.931757] ttls_parse_client_hello+0x636/0x2c60 [tempesta_tls] Apr 26 04:26:02 192.168.122.209 [44512.932295] ? lookup_address_in_pgd.part.0.constprop.0+0x215/0x280 Apr 26 04:26:02 192.168.122.209 [44512.932859] ttls_handshake_server_step+0x7a7/0x3950 [tempesta_tls] Apr 26 04:26:02 192.168.122.209 [44512.933427] ? ttls_parse_client_hello+0x2c60/0x2c60 [tempesta_tls] Apr 26 04:26:02 192.168.122.209 [44512.933981] ? __cpa_process_fault+0x800/0x800 Apr 26 04:26:02 192.168.122.209 [44512.934389] ? flush_tlb_one_user+0x20/0x20 Apr 26 04:26:02 192.168.122.209 [44512.934765] ? ftrace_graph_ret_addr+0x2a/0xb0 Apr 26 04:26:02 192.168.122.209 [44512.935171] ? stack_trace_save+0x94/0xc0 Apr 26 04:26:02 192.168.122.209 [44512.935535] ? get_stack_info_noinstr+0x17/0xf0 Apr 26 04:26:02 192.168.122.209 [44512.935946] ? ftrace_graph_ret_addr+0x2a/0xb0 Apr 26 04:26:02 192.168.122.209 [44512.936351] ? secondary_startup_64_no_verify+0xb0/0xbb Apr 26 04:26:02 192.168.122.209 [44512.936816] ? update_stack_state+0x1d2/0x280 Apr 26 04:26:02 192.168.122.209 [44512.937213] ? unwind_next_frame.part.0+0x1d9/0x360 Apr 26 04:26:02 192.168.122.209 [44512.937654] ? create_prof_cpu_mask+0x30/0x30 Apr 26 04:26:02 192.168.122.209 [44512.938049] ? unwind_next_frame+0x23/0x40 Apr 26 04:26:02 192.168.122.209 [44512.938421] ? arch_stack_walk+0x88/0xf0 Apr 26 04:26:02 192.168.122.209 [44512.938778] ? secondary_startup_64_no_verify+0xb0/0xbb Apr 26 04:26:02 192.168.122.209 [44512.939253] ? stack_trace_save+0x94/0xc0 Apr 26 04:26:02 192.168.122.209 [44512.939620] ? stack_trace_consume_entry+0x90/0x90 Apr 26 04:26:02 192.168.122.209 [44512.940061] ? kasan_save_stack+0x42/0x50 Apr 26 04:26:02 192.168.122.209 [44512.940425] ? kasan_save_stack+0x23/0x50 Apr 26 04:26:02 192.168.122.209 [44512.940793] ? __kasan_kmalloc.constprop.0+0xcf/0xe0 Apr 26 04:26:02 192.168.122.209 [44512.941241] ? kasan_slab_alloc+0xe/0x10 Apr 26 04:26:02 192.168.122.209 [44512.941595] ? kmem_cache_alloc+0xf7/0x290 Apr 26 04:26:02 192.168.122.209 [44512.941966] ? create_object.isra.0+0x43/0x4e0 Apr 26 04:26:02 192.168.122.209 [44512.942373] ? kmemleak_alloc+0x4b/0x80 Apr 26 04:26:02 192.168.122.209 [44512.942720] ? kmem_cache_alloc+0x118/0x290 Apr 26 04:26:02 192.168.122.209 [44512.943111] ? ttls_ctx_init+0x50/0xa0 [tempesta_tls] Apr 26 04:26:02 192.168.122.209 [44512.943562] ? ftrace_graph_ret_addr+0x2a/0xb0 Apr 26 04:26:02 192.168.122.209 [44512.943966] ? stack_trace_save+0x94/0xc0 Apr 26 04:26:02 192.168.122.209 [44512.944335] ? ftrace_graph_ret_addr+0x2a/0xb0 Apr 26 04:26:02 192.168.122.209 [44512.944739] ? __netif_receive_skb+0x26/0xb0 Apr 26 04:26:02 192.168.122.209 [44512.945130] ? update_stack_state+0x1d2/0x280 Apr 26 04:26:02 192.168.122.209 [44512.945538] ttls_recv+0x53d/0xbc0 [tempesta_tls] Apr 26 04:26:02 192.168.122.209 [44512.945966] ? ttls_handle_alert+0x50/0x50 [tempesta_tls] Apr 26 04:26:02 192.168.122.209 [44512.946486] ss_skb_process+0x270/0x2f0 [tempesta_fw] Apr 26 04:26:02 192.168.122.209 [44512.946945] ? ttls_handle_alert+0x50/0x50 [tempesta_tls] Apr 26 04:26:02 192.168.122.209 [44512.947464] ? tfw_sock_srv_exit+0x30/0x30 [tempesta_fw] Apr 26 04:26:02 192.168.122.209 [44512.947939] ? _raw_write_lock_irqsave+0xe0/0xe0 Apr 26 04:26:02 192.168.122.209 [44512.948385] tfw_tls_connection_recv+0x14e/0x730 [tempesta_fw] Apr 26 04:26:02 192.168.122.209 [44512.948906] ? __kasan_check_write+0x14/0x20 Apr 26 04:26:02 192.168.122.209 [44512.949326] ? tfw_tls_connection_lost+0x40/0x40 [tempesta_fw] Apr 26 04:26:02 192.168.122.209 [44512.949870] ? ss_skb_unroll+0x3d6/0x540 [tempesta_fw] Apr 26 04:26:02 192.168.122.209 [44512.950361] ss_tcp_process_data+0x436/0x8b0 [tempesta_fw] Apr 26 04:26:02 192.168.122.209 [44512.950877] ? __sk_close_locked+0x100/0x100 [tempesta_fw] Apr 26 04:26:02 192.168.122.209 [44512.951375] ? tcp_grow_window+0xce/0x330 Apr 26 04:26:02 192.168.122.209 [44512.951764] ss_tcp_data_ready+0x7b/0x150 [tempesta_fw] Apr 26 04:26:02 192.168.122.209 [44512.952236] tcp_data_ready+0x73/0x210 Apr 26 04:26:02 192.168.122.209 [44512.952578] tcp_data_queue+0x1085/0x1d80 Apr 26 04:26:02 192.168.122.209 [44512.952945] ? tcp_data_ready+0x210/0x210 Apr 26 04:26:02 192.168.122.209 [44512.953311] ? tcp_enter_cwr+0x1c0/0x1c0 Apr 26 04:26:02 192.168.122.209 [44512.953665] ? kvm_clock_get_cycles+0x11/0x20 Apr 26 04:26:02 192.168.122.209 [44512.954060] ? ktime_get+0x4f/0xb0 Apr 26 04:26:02 192.168.122.209 [44512.954375] tcp_rcv_established+0x422/0xb40 Apr 26 04:26:02 192.168.122.209 [44512.954760] ? tcp_data_queue+0x1d80/0x1d80 Apr 26 04:26:02 192.168.122.209 [44512.955140] ? __kasan_check_read+0x11/0x20 Apr 26 04:26:02 192.168.122.209 [44512.955520] tcp_v4_do_rcv+0x25f/0x360 Apr 26 04:26:02 192.168.122.209 [44512.955862] tcp_v4_rcv+0x1600/0x1770 Apr 26 04:26:02 192.168.122.209 [44512.956202] ? tcp_v4_early_demux+0x2f0/0x2f0 Apr 26 04:26:02 192.168.122.209 [44512.956596] ip_protocol_deliver_rcu+0x46/0x2e0 Apr 26 04:26:02 192.168.122.209 [44512.957002] ip_local_deliver_finish+0xc6/0xe0 Apr 26 04:26:02 192.168.122.209 [44512.957409] ip_local_deliver+0x1f5/0x210 Apr 26 04:26:02 192.168.122.209 [44512.957771] ? ip_local_deliver_finish+0xe0/0xe0 Apr 26 04:26:02 192.168.122.209 [44512.958191] ? nf_nat_inet_fn+0x2b3/0x440 [nf_nat] Apr 26 04:26:02 192.168.122.209 [44512.958619] ? ip_protocol_deliver_rcu+0x2e0/0x2e0 Apr 26 04:26:02 192.168.122.209 [44512.959054] ? ip_rcv_finish_core.constprop.0+0x17c/0x890 Apr 26 04:26:02 192.168.122.209 [44512.959535] ip_rcv_finish+0xcf/0xf0 Apr 26 04:26:02 192.168.122.209 [44512.959860] ip_rcv+0x16d/0x180 Apr 26 04:26:02 192.168.122.209 [44512.960151] ? ip_local_deliver+0x210/0x210 Apr 26 04:26:02 192.168.122.209 [44512.960532] ? ip_rcv_finish_core.constprop.0+0x890/0x890 Apr 26 04:26:02 192.168.122.209 [44512.961013] ? ip_local_deliver+0x210/0x210 Apr 26 04:26:02 192.168.122.209 [44512.961392] __netif_receive_skb_one_core+0x132/0x140 Apr 26 04:26:02 192.168.122.209 [44512.961844] ? napi_gro_receive+0x260/0x260 Apr 26 04:26:02 192.168.122.209 [44512.962233] ? __kasan_check_write+0x14/0x20 Apr 26 04:26:02 192.168.122.209 [44512.962616] ? _raw_spin_lock+0x7b/0xd0 Apr 26 04:26:02 192.168.122.209 [44512.962962] __netif_receive_skb+0x26/0xb0 Apr 26 04:26:02 192.168.122.209 [44512.963335] process_backlog+0xfe/0x290 Apr 26 04:26:02 192.168.122.209 [44512.963684] net_rx_action+0x287/0x6b0 Apr 26 04:26:02 192.168.122.209 [44512.964024] ? napi_complete_done+0x2c0/0x2c0 Apr 26 04:26:02 192.168.122.209 [44512.964418] ? switch_fpu_return+0x120/0x120 Apr 26 04:26:02 192.168.122.209 [44512.964803] __do_softirq+0xfe/0x383 Apr 26 04:26:02 192.168.122.209 [44512.965139] asm_call_irq_on_stack+0xf/0x20 Apr 26 04:26:02 192.168.122.209 [44512.965513] Apr 26 04:26:02 192.168.122.209 [44512.965713] do_softirq_own_stack+0x3d/0x50 Apr 26 04:26:02 192.168.122.209 [44512.966094] irq_exit_rcu+0xc7/0x120 Apr 26 04:26:02 192.168.122.209 [44512.966425] sysvec_call_function_single+0x3a/0x90 Apr 26 04:26:02 192.168.122.209 [44512.966854] asm_sysvec_call_function_single+0x12/0x20 Apr 26 04:26:02 192.168.122.209 [44512.967316] RIP: 0010:native_safe_halt+0xe/0x10 Apr 26 04:26:02 192.168.122.209 [44512.967723] Code: 49 8b 04 24 a8 08 0f 85 71 ff ff ff e9 0f ff ff ff cc cc cc cc cc cc cc cc cc cc cc e9 07 00 00 00 0f 00 2d d4 62 51 00 fb f4 90 e9 07 00 00 00 0f 00 2d c4 62 51 00 f4 c3 cc cc 0f 1f 44 00 Apr 26 04:26:02 192.168.122.209 [44512.969378] RSP: 0018:ffff888100f37db8 EFLAGS: 00000212 Apr 26 04:26:02 192.168.122.209 [44512.969843] RAX: ffffffffb63426a0 RBX: ffff888100f2c0c0 RCX: ffffffffb632c475 Apr 26 04:26:02 192.168.122.209 [44512.970477] RDX: 000000000a99700e RSI: 0000000000000004 RDI: ffff888147eb5040 Apr 26 04:26:02 192.168.122.209 [44512.971113] RBP: ffff888100f37dc0 R08: 0000000000000001 R09: ffff888147eb5043 Apr 26 04:26:02 192.168.122.209 [44512.971742] R10: ffffed1028fd6a08 R11: 0000000000000001 R12: 0000000000000001 Apr 26 04:26:02 192.168.122.209 [44512.972373] R13: ffffffffb7ae9360 R14: 0000000000000000 R15: 0000000000000000 Apr 26 04:26:02 192.168.122.209 [44512.973000] ? __cpuidle_text_start+0x8/0x8 Apr 26 04:26:02 192.168.122.209 [44512.973378] ? rcu_eqs_enter.constprop.0+0x85/0xa0 Apr 26 04:26:02 192.168.122.209 [44512.973808] ? default_idle+0xe/0x20 Apr 26 04:26:02 192.168.122.209 [44512.974136] arch_cpu_idle+0x15/0x20 Apr 26 04:26:02 192.168.122.209 [44512.974460] default_idle_call+0x66/0x160 Apr 26 04:26:02 192.168.122.209 [44512.974823] do_idle+0x36f/0x430 Apr 26 04:26:02 192.168.122.209 [44512.975127] ? arch_cpu_idle_exit+0x40/0x40 Apr 26 04:26:02 192.168.122.209 [44512.975504] cpu_startup_entry+0x20/0x30 Apr 26 04:26:02 192.168.122.209 [44512.975860] start_secondary+0x1c1/0x210 Apr 26 04:26:02 192.168.122.209 [44512.976220] ? set_cpu_sibling_map+0xd70/0xd70 Apr 26 04:26:02 192.168.122.209 [44512.976624] ? set_bringup_idt_handler.constprop.0+0x84/0x90 Apr 26 04:26:02 192.168.122.209 [44512.977130] ? start_cpu0+0xc/0xc Apr 26 04:26:02 192.168.122.209 [44512.977434] secondary_startup_64_no_verify+0xb0/0xbb Apr 26 04:26:02 192.168.122.209 [44512.977907] [tempesta tls] Warning: Cannot setup hash ctx, -12 Apr 26 04:26:03 192.168.122.209 [44513.504833] [tdb] Close table 'client0.tdb' Apr 26 04:26:03 192.168.122.209 [44513.730876] [tdb] Close table 'sessions0.tdb' Apr 26 04:26:06 192.168.122.209 [44516.895956] [tdb] Close table 'cache0.tdb' Apr 26 04:26:06 192.168.122.209 [44517.142789] [tdb] Close table 'filter0.tdb' Apr 26 04:26:06 192.168.122.209 [44517.143241] [tempesta fw] modules are stopped Apr 26 04:26:06 192.168.122.209 [44517.318261] [tempesta fw] exiting... Apr 26 04:26:07 192.168.122.209 [44517.490809] [tdb] Shutdown Tempesta DB Apr 26 04:26:07 192.168.122.209 [44517.727223] End test: t_fault_injection.test_fault_injection_base.TestFailFunction.test_crypto_alloc_shash_atomic_ssl Apr 26 04:26:07 192.168.122.209 [44517.742521] Start test: t_fault_injection.test_fault_injection_base.TestFailFunction.test_ss_skb_expand_head_tail Apr 26 04:26:08 192.168.122.209 [44518.924910] [tdb] Start Tempesta DB Apr 26 04:26:08 192.168.122.209 [44519.088903] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:26:10 192.168.122.209 [44520.470602] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44520.470602] Maybe that's fine, but it's worth checking the [44520.470602] config - if there is no relations between the [44520.470602] names, then host name confusion attack is possible. Apr 26 04:26:10 192.168.122.209 [44520.589390] [tempesta fw] Configuration processing is completed. Apr 26 04:26:10 192.168.122.209 [44520.646896] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:26:10 192.168.122.209 [44521.142006] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:26:10 192.168.122.209 [44521.172222] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:26:10 192.168.122.209 [44521.199586] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:26:10 192.168.122.209 [44521.237343] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:26:10 192.168.122.209 [44521.239063] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:26:10 192.168.122.209 [44521.297290] [tempesta fw] Tempesta FW is ready Apr 26 04:26:11 192.168.122.209 [44521.522797] FAULT_INJECTION: forcing a failure. [44521.522797] name fail_function, interval 0, probability 100, space 0, times 1 Apr 26 04:26:11 192.168.122.209 [44521.524732] CPU: 3 PID: 0 Comm: swapper/3 Tainted: G OE 5.10.35.tfw-39c65d3-debug #1 Apr 26 04:26:11 192.168.122.209 [44521.526225] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 Apr 26 04:26:11 192.168.122.209 [44521.527745] Call Trace: Apr 26 04:26:11 192.168.122.209 [44521.528169] Apr 26 04:26:11 192.168.122.209 [44521.528527] dump_stack+0x96/0xc4 Apr 26 04:26:11 192.168.122.209 [44521.528968] should_fail.cold+0x5/0xa Apr 26 04:26:11 192.168.122.209 [44521.529309] fei_kprobe_handler+0x23/0x60 Apr 26 04:26:11 192.168.122.209 [44521.529704] ? ss_skb_expand_head_tail+0x1/0x170 [tempesta_fw] Apr 26 04:26:11 192.168.122.209 [44521.530225] kprobe_ftrace_handler+0xbe/0x150 Apr 26 04:26:11 192.168.122.209 [44521.530645] ? ss_skb_expand_head_tail+0x5/0x170 [tempesta_fw] Apr 26 04:26:11 192.168.122.209 [44521.531192] ? tfw_tls_encrypt+0x757/0xce0 [tempesta_fw] Apr 26 04:26:11 192.168.122.209 [44521.531671] ftrace_ops_assist_func+0xef/0x1b0 Apr 26 04:26:11 192.168.122.209 [44521.532097] ? __new_pgfrag+0x2a0/0x2a0 [tempesta_fw] Apr 26 04:26:11 192.168.122.209 [44521.532551] 0xffffffffc16e00e3 Apr 26 04:26:11 192.168.122.209 [44521.532867] RIP: 0010:ss_skb_expand_head_tail+0x1/0x170 [tempesta_fw] Apr 26 04:26:11 192.168.122.209 [44521.533442] Code: 0f b6 d3 be ff ff ff ff 4c 89 ff e8 99 86 7d f3 eb 9f 4c 89 ff e8 6f 1b 6c f3 eb 99 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 e8 b2 9d ff 55 48 89 e5 41 57 41 56 41 55 49 89 d5 41 54 49 89 cc Apr 26 04:26:11 192.168.122.209 [44521.535049] RSP: 0018:ffff888147f897f0 EFLAGS: 00000212 ORIG_RAX: 0000000000000000 Apr 26 04:26:11 192.168.122.209 [44521.535733] RAX: 0000000000000000 RBX: ffff88803c691828 RCX: 0000000000000010 Apr 26 04:26:11 192.168.122.209 [44521.536371] RDX: 000000000000000d RSI: ffff88805b3da380 RDI: ffff88803c691828 Apr 26 04:26:11 192.168.122.209 [44521.536999] RBP: ffff888147f89bf8 R08: ffffffffc1d0f1b3 R09: ffff88803c69180f Apr 26 04:26:11 192.168.122.209 [44521.537627] R10: ffffed10078d2301 R11: 0000000000000001 R12: ffff888147f89bd0 Apr 26 04:26:11 192.168.122.209 [44521.538256] R13: ffff88803c691828 R14: ffff88805b3da380 R15: 0000000000000400 Apr 26 04:26:11 192.168.122.209 [44521.538910] ? tfw_tls_encrypt+0xb53/0xce0 [tempesta_fw] Apr 26 04:26:11 192.168.122.209 [44521.539419] ? ss_skb_expand_head_tail+0x5/0x170 [tempesta_fw] Apr 26 04:26:11 192.168.122.209 [44521.539960] ? tfw_tls_encrypt+0x757/0xce0 [tempesta_fw] Apr 26 04:26:11 192.168.122.209 [44521.540472] ? ss_skb_expand_head_tail+0x5/0x170 [tempesta_fw] Apr 26 04:26:11 192.168.122.209 [44521.541019] ? tfw_tls_encrypt+0x757/0xce0 [tempesta_fw] Apr 26 04:26:11 192.168.122.209 [44521.541524] ? tfw_tls_connection_recv+0x730/0x730 [tempesta_fw] Apr 26 04:26:11 192.168.122.209 [44521.542056] ? tcp_rcv_established+0x43f/0xb40 Apr 26 04:26:11 192.168.122.209 [44521.542460] ? tcp_parse_md5sig_option+0x20/0xb0 Apr 26 04:26:11 192.168.122.209 [44521.542878] ? tcp_data_queue+0x1d80/0x1d80 Apr 26 04:26:11 192.168.122.209 [44521.543259] ? __kasan_check_read+0x11/0x20 Apr 26 04:26:11 192.168.122.209 [44521.543635] ? __kasan_check_write+0x14/0x20 Apr 26 04:26:11 192.168.122.209 [44521.544018] ? sock_put+0x1f/0x60 Apr 26 04:26:11 192.168.122.209 [44521.544327] ? tcp_v4_rcv+0x1633/0x1770 Apr 26 04:26:11 192.168.122.209 [44521.544676] ? tcp_v4_early_demux+0x2f0/0x2f0 Apr 26 04:26:11 192.168.122.209 [44521.545068] ? ip_protocol_deliver_rcu+0x196/0x2e0 Apr 26 04:26:11 192.168.122.209 [44521.545504] ? ip_local_deliver_finish+0xcb/0xe0 Apr 26 04:26:11 192.168.122.209 [44521.545918] ? ip_local_deliver+0x1f5/0x210 Apr 26 04:26:11 192.168.122.209 [44521.546300] ? __asan_loadN+0xf/0x20 Apr 26 04:26:11 192.168.122.209 [44521.546624] ? pvclock_clocksource_read+0xe1/0x1a0 Apr 26 04:26:11 192.168.122.209 [44521.547054] tcp_tfw_sk_write_xmit+0x148/0x1d0 Apr 26 04:26:11 192.168.122.209 [44521.547487] ? tfw_tls_connection_recv+0x730/0x730 [tempesta_fw] Apr 26 04:26:11 192.168.122.209 [44521.548020] tcp_write_xmit+0x768/0x2a50 Apr 26 04:26:11 192.168.122.209 [44521.548377] ? bpf_skops_hdr_opt_len+0x210/0x210 Apr 26 04:26:11 192.168.122.209 [44521.548792] ? ip_rcv+0x16d/0x180 Apr 26 04:26:11 192.168.122.209 [44521.549097] ? ip_local_deliver+0x210/0x210 Apr 26 04:26:11 192.168.122.209 [44521.549480] __tcp_push_pending_frames+0x5f/0x1a0 Apr 26 04:26:11 192.168.122.209 [44521.549899] tcp_push+0x209/0x2b0 Apr 26 04:26:11 192.168.122.209 [44521.550233] ss_tx_action+0x946/0xc20 [tempesta_fw] Apr 26 04:26:11 192.168.122.209 [44521.550699] ? ss_skb_tcp_entail_list+0x1a0/0x1a0 [tempesta_fw] Apr 26 04:26:11 192.168.122.209 [44521.551228] ? net_rps_send_ipi+0x91/0xa0 Apr 26 04:26:11 192.168.122.209 [44521.551590] ? __kfree_skb_flush+0x27/0x60 Apr 26 04:26:11 192.168.122.209 [44521.551960] ? net_rx_action+0x438/0x6b0 Apr 26 04:26:11 192.168.122.209 [44521.552324] ? napi_complete_done+0x2c0/0x2c0 Apr 26 04:26:11 192.168.122.209 [44521.552716] net_tx_action+0xfa/0x3c0 Apr 26 04:26:11 192.168.122.209 [44521.553050] __do_softirq+0xfe/0x383 Apr 26 04:26:11 192.168.122.209 [44521.553386] asm_call_irq_on_stack+0xf/0x20 Apr 26 04:26:11 192.168.122.209 [44521.553765] Apr 26 04:26:11 192.168.122.209 [44521.553966] do_softirq_own_stack+0x3d/0x50 Apr 26 04:26:11 192.168.122.209 [44521.554346] irq_exit_rcu+0xc7/0x120 Apr 26 04:26:11 192.168.122.209 [44521.554673] sysvec_call_function_single+0x3a/0x90 Apr 26 04:26:11 192.168.122.209 [44521.555106] asm_sysvec_call_function_single+0x12/0x20 Apr 26 04:26:11 192.168.122.209 [44521.555570] RIP: 0010:native_safe_halt+0xe/0x10 Apr 26 04:26:11 192.168.122.209 [44521.555974] Code: 49 8b 04 24 a8 08 0f 85 71 ff ff ff e9 0f ff ff ff cc cc cc cc cc cc cc cc cc cc cc e9 07 00 00 00 0f 00 2d d4 62 51 00 fb f4 90 e9 07 00 00 00 0f 00 2d c4 62 51 00 f4 c3 cc cc 0f 1f 44 00 Apr 26 04:26:11 192.168.122.209 [44521.557615] RSP: 0018:ffff888100f47db8 EFLAGS: 00000216 Apr 26 04:26:11 192.168.122.209 [44521.558082] RAX: ffffffffb63426a0 RBX: ffff888100f28040 RCX: ffffffffb632c475 Apr 26 04:26:11 192.168.122.209 [44521.558713] RDX: 000000000b226f8e RSI: 0000000000000004 RDI: ffff888147fb5040 Apr 26 04:26:11 192.168.122.209 [44521.559343] RBP: ffff888100f47dc0 R08: 0000000000000001 R09: ffff888147fb5043 Apr 26 04:26:11 192.168.122.209 [44521.559967] R10: ffffed1028ff6a08 R11: 0000000000000001 R12: 0000000000000003 Apr 26 04:26:11 192.168.122.209 [44521.560600] R13: ffffffffb7ae9360 R14: 0000000000000000 R15: 0000000000000000 Apr 26 04:26:11 192.168.122.209 [44521.561230] ? __cpuidle_text_start+0x8/0x8 Apr 26 04:26:11 192.168.122.209 [44521.561606] ? rcu_eqs_enter.constprop.0+0x85/0xa0 Apr 26 04:26:11 192.168.122.209 [44521.562037] ? default_idle+0xe/0x20 Apr 26 04:26:11 192.168.122.209 [44521.562369] arch_cpu_idle+0x15/0x20 Apr 26 04:26:11 192.168.122.209 [44521.562696] default_idle_call+0x66/0x160 Apr 26 04:26:11 192.168.122.209 [44521.563057] do_idle+0x36f/0x430 Apr 26 04:26:11 192.168.122.209 [44521.563358] ? arch_cpu_idle_exit+0x40/0x40 Apr 26 04:26:11 192.168.122.209 [44521.563736] cpu_startup_entry+0x20/0x30 Apr 26 04:26:11 192.168.122.209 [44521.564093] start_secondary+0x1c1/0x210 Apr 26 04:26:11 192.168.122.209 [44521.564450] ? set_cpu_sibling_map+0xd70/0xd70 Apr 26 04:26:11 192.168.122.209 [44521.564849] ? set_bringup_idt_handler.constprop.0+0x84/0x90 Apr 26 04:26:11 192.168.122.209 [44521.565357] ? start_cpu0+0xc/0xc Apr 26 04:26:11 192.168.122.209 [44521.565662] secondary_startup_64_no_verify+0xb0/0xbb Apr 26 04:26:11 192.168.122.209 [44521.566156] [tempesta fw] Warning: tfw_tls_encrypt: cannot encrypt data (-12) Apr 26 04:26:11 192.168.122.209 [44522.160889] [tdb] Close table 'client0.tdb' Apr 26 04:26:11 192.168.122.209 [44522.358791] [tdb] Close table 'sessions0.tdb' Apr 26 04:26:15 192.168.122.209 [44525.557701] [tdb] Close table 'cache0.tdb' Apr 26 04:26:15 192.168.122.209 [44525.804773] [tdb] Close table 'filter0.tdb' Apr 26 04:26:15 192.168.122.209 [44525.805248] [tempesta fw] modules are stopped Apr 26 04:26:15 192.168.122.209 [44526.030122] [tempesta fw] exiting... Apr 26 04:26:15 192.168.122.209 [44526.182582] [tdb] Shutdown Tempesta DB Apr 26 04:26:16 192.168.122.209 [44526.448798] End test: t_fault_injection.test_fault_injection_base.TestFailFunction.test_ss_skb_expand_head_tail Apr 26 04:26:16 192.168.122.209 [44526.458786] Start test: t_fault_injection.test_fault_injection_base.TestFailFunction.test_ss_skb_to_sgvec_with_new_pages Apr 26 04:26:17 192.168.122.209 [44527.651129] [tdb] Start Tempesta DB Apr 26 04:26:17 192.168.122.209 [44527.827001] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:26:18 192.168.122.209 [44529.226764] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44529.226764] Maybe that's fine, but it's worth checking the [44529.226764] config - if there is no relations between the [44529.226764] names, then host name confusion attack is possible. Apr 26 04:26:18 192.168.122.209 [44529.349565] [tempesta fw] Configuration processing is completed. Apr 26 04:26:19 192.168.122.209 [44529.431426] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:26:19 192.168.122.209 [44529.916085] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:26:19 192.168.122.209 [44529.959535] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:26:19 192.168.122.209 [44529.986959] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:26:19 192.168.122.209 [44530.025461] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:26:19 192.168.122.209 [44530.027187] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:26:19 192.168.122.209 [44530.065396] [tempesta fw] Tempesta FW is ready Apr 26 04:26:19 192.168.122.209 [44530.314402] FAULT_INJECTION: forcing a failure. [44530.314402] name fail_function, interval 0, probability 100, space 0, times 1 Apr 26 04:26:19 192.168.122.209 [44530.315957] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G OE 5.10.35.tfw-39c65d3-debug #1 Apr 26 04:26:19 192.168.122.209 [44530.317126] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 Apr 26 04:26:19 192.168.122.209 [44530.318338] Call Trace: Apr 26 04:26:19 192.168.122.209 [44530.318672] Apr 26 04:26:19 192.168.122.209 [44530.318966] dump_stack+0x96/0xc4 Apr 26 04:26:19 192.168.122.209 [44530.319415] should_fail.cold+0x5/0xa Apr 26 04:26:19 192.168.122.209 [44530.319791] fei_kprobe_handler+0x23/0x60 Apr 26 04:26:19 192.168.122.209 [44530.320186] ? ss_skb_to_sgvec_with_new_pages+0x1/0x4c0 [tempesta_fw] Apr 26 04:26:19 192.168.122.209 [44530.320769] kprobe_ftrace_handler+0xbe/0x150 Apr 26 04:26:19 192.168.122.209 [44530.321186] ? ss_skb_to_sgvec_with_new_pages+0x5/0x4c0 [tempesta_fw] Apr 26 04:26:19 192.168.122.209 [44530.321787] ? tfw_tls_encrypt+0x688/0xce0 [tempesta_fw] Apr 26 04:26:19 192.168.122.209 [44530.322266] ftrace_ops_assist_func+0xef/0x1b0 Apr 26 04:26:19 192.168.122.209 [44530.322697] ? ss_skb_dump+0x420/0x420 [tempesta_fw] Apr 26 04:26:19 192.168.122.209 [44530.323149] 0xffffffffc16e00e3 Apr 26 04:26:19 192.168.122.209 [44530.323471] RIP: 0010:ss_skb_to_sgvec_with_new_pages+0x1/0x4c0 [tempesta_fw] Apr 26 04:26:19 192.168.122.209 [44530.324091] Code: b0 83 45 c8 01 8b 5d c8 e8 6c 14 79 f3 41 0f b6 46 02 5a 59 39 d8 0f 8f 99 fe ff ff 4c 8b 75 c0 e9 19 fe ff ff 0f 1f 40 00 e8 c3 9d ff 55 48 89 e5 41 57 49 89 ff 48 83 c7 70 41 56 41 55 41 Apr 26 04:26:19 192.168.122.209 [44530.325717] RSP: 0018:ffff888147e897f0 EFLAGS: 00000282 ORIG_RAX: 0000000000000000 Apr 26 04:26:19 192.168.122.209 [44530.326386] RAX: 0000000000000001 RBX: ffff888147e898d0 RCX: ffffffffb5f956c2 Apr 26 04:26:19 192.168.122.209 [44530.327013] RDX: ffff888147e89870 RSI: ffff888147e89a70 RDI: ffff8880666a2000 Apr 26 04:26:19 192.168.122.209 [44530.327641] RBP: ffff888147e89bf8 R08: ffffffffb5f9554b R09: ffff888147e89a70 Apr 26 04:26:19 192.168.122.209 [44530.328276] R10: ffffed1028fd1351 R11: 0000000000000001 R12: ffff888147e89bd0 Apr 26 04:26:19 192.168.122.209 [44530.328900] R13: 0000000000000001 R14: 0000000000000000 R15: ffff8880666a2000 Apr 26 04:26:19 192.168.122.209 [44530.329531] ? __skb_to_sgvec+0x30b/0x450 Apr 26 04:26:19 192.168.122.209 [44530.329892] ? skb_to_sgvec+0x32/0x50 Apr 26 04:26:19 192.168.122.209 [44530.330253] ? ss_skb_to_sgvec_with_new_pages+0x5/0x4c0 [tempesta_fw] Apr 26 04:26:19 192.168.122.209 [44530.330852] ? tfw_tls_encrypt+0x688/0xce0 [tempesta_fw] Apr 26 04:26:19 192.168.122.209 [44530.331355] ? ss_skb_to_sgvec_with_new_pages+0x5/0x4c0 [tempesta_fw] Apr 26 04:26:19 192.168.122.209 [44530.331948] ? tfw_tls_encrypt+0x688/0xce0 [tempesta_fw] Apr 26 04:26:19 192.168.122.209 [44530.332454] ? tfw_tls_connection_recv+0x730/0x730 [tempesta_fw] Apr 26 04:26:19 192.168.122.209 [44530.332982] ? tcp_rcv_established+0x9b0/0xb40 Apr 26 04:26:19 192.168.122.209 [44530.333384] ? tcp_data_queue+0x1d80/0x1d80 Apr 26 04:26:19 192.168.122.209 [44530.333759] ? __kasan_check_read+0x11/0x20 Apr 26 04:26:19 192.168.122.209 [44530.334146] ? __kasan_check_write+0x14/0x20 Apr 26 04:26:19 192.168.122.209 [44530.334532] ? sock_put+0x1f/0x60 Apr 26 04:26:19 192.168.122.209 [44530.334833] ? tcp_v4_rcv+0x1633/0x1770 Apr 26 04:26:19 192.168.122.209 [44530.335181] ? tcp_v4_early_demux+0x2f0/0x2f0 Apr 26 04:26:19 192.168.122.209 [44530.335583] ? ip_protocol_deliver_rcu+0x196/0x2e0 Apr 26 04:26:19 192.168.122.209 [44530.336014] ? ip_local_deliver_finish+0xcb/0xe0 Apr 26 04:26:19 192.168.122.209 [44530.336432] ? ip_local_deliver+0x1f5/0x210 Apr 26 04:26:19 192.168.122.209 [44530.336810] ? __asan_loadN+0xf/0x20 Apr 26 04:26:19 192.168.122.209 [44530.337141] ? pvclock_clocksource_read+0xe1/0x1a0 Apr 26 04:26:19 192.168.122.209 [44530.337573] tcp_tfw_sk_write_xmit+0x148/0x1d0 Apr 26 04:26:19 192.168.122.209 [44530.337997] ? tfw_tls_connection_recv+0x730/0x730 [tempesta_fw] Apr 26 04:26:19 192.168.122.209 [44530.338530] tcp_write_xmit+0x768/0x2a50 Apr 26 04:26:19 192.168.122.209 [44530.338887] ? bpf_skops_hdr_opt_len+0x210/0x210 Apr 26 04:26:19 192.168.122.209 [44530.339303] ? ip_rcv+0x16d/0x180 Apr 26 04:26:19 192.168.122.209 [44530.339606] ? ip_local_deliver+0x210/0x210 Apr 26 04:26:19 192.168.122.209 [44530.339983] __tcp_push_pending_frames+0x5f/0x1a0 Apr 26 04:26:19 192.168.122.209 [44530.340414] tcp_push+0x209/0x2b0 Apr 26 04:26:19 192.168.122.209 [44530.340744] ss_tx_action+0x946/0xc20 [tempesta_fw] Apr 26 04:26:19 192.168.122.209 [44530.341206] ? ss_skb_tcp_entail_list+0x1a0/0x1a0 [tempesta_fw] Apr 26 04:26:19 192.168.122.209 [44530.341736] ? __kfree_skb_flush+0x27/0x60 Apr 26 04:26:19 192.168.122.209 [44530.342109] ? net_rx_action+0x438/0x6b0 Apr 26 04:26:19 192.168.122.209 [44530.342466] ? napi_complete_done+0x2c0/0x2c0 Apr 26 04:26:19 192.168.122.209 [44530.342857] net_tx_action+0xfa/0x3c0 Apr 26 04:26:19 192.168.122.209 [44530.343189] __do_softirq+0xfe/0x383 Apr 26 04:26:19 192.168.122.209 [44530.343521] asm_call_irq_on_stack+0xf/0x20 Apr 26 04:26:19 192.168.122.209 [44530.343896] Apr 26 04:26:19 192.168.122.209 [44530.344096] do_softirq_own_stack+0x3d/0x50 Apr 26 04:26:19 192.168.122.209 [44530.344477] irq_exit_rcu+0xc7/0x120 Apr 26 04:26:19 192.168.122.209 [44530.344809] sysvec_call_function_single+0x3a/0x90 Apr 26 04:26:19 192.168.122.209 [44530.345235] asm_sysvec_call_function_single+0x12/0x20 Apr 26 04:26:19 192.168.122.209 [44530.345699] RIP: 0010:native_safe_halt+0xe/0x10 Apr 26 04:26:19 192.168.122.209 [44530.346105] Code: 49 8b 04 24 a8 08 0f 85 71 ff ff ff e9 0f ff ff ff cc cc cc cc cc cc cc cc cc cc cc e9 07 00 00 00 0f 00 2d d4 62 51 00 fb f4 90 e9 07 00 00 00 0f 00 2d c4 62 51 00 f4 c3 cc cc 0f 1f 44 00 Apr 26 04:26:19 192.168.122.209 [44530.347728] RSP: 0018:ffff888100f37db8 EFLAGS: 00000206 Apr 26 04:26:19 192.168.122.209 [44530.348205] RAX: ffffffffb63426a0 RBX: ffff888100f2c0c0 RCX: ffffffffb632c475 Apr 26 04:26:19 192.168.122.209 [44530.348833] RDX: 000000000a99f846 RSI: 0000000000000004 RDI: ffff888147eb5040 Apr 26 04:26:19 192.168.122.209 [44530.349463] RBP: ffff888100f37dc0 R08: 0000000000000001 R09: ffff888147eb5043 Apr 26 04:26:19 192.168.122.209 [44530.350086] R10: ffffed1028fd6a08 R11: 0000000000000001 R12: 0000000000000001 Apr 26 04:26:19 192.168.122.209 [44530.350713] R13: ffffffffb7ae9360 R14: 0000000000000000 R15: 0000000000000000 Apr 26 04:26:19 192.168.122.209 [44530.351343] ? __cpuidle_text_start+0x8/0x8 Apr 26 04:26:19 192.168.122.209 [44530.351717] ? rcu_eqs_enter.constprop.0+0x85/0xa0 Apr 26 04:26:19 192.168.122.209 [44530.352148] ? default_idle+0xe/0x20 Apr 26 04:26:19 192.168.122.209 [44530.352475] arch_cpu_idle+0x15/0x20 Apr 26 04:26:19 192.168.122.209 [44530.352799] default_idle_call+0x66/0x160 Apr 26 04:26:19 192.168.122.209 [44530.353161] do_idle+0x36f/0x430 Apr 26 04:26:19 192.168.122.209 [44530.353464] ? arch_cpu_idle_exit+0x40/0x40 Apr 26 04:26:19 192.168.122.209 [44530.353837] cpu_startup_entry+0x20/0x30 Apr 26 04:26:19 192.168.122.209 [44530.354191] start_secondary+0x1c1/0x210 Apr 26 04:26:19 192.168.122.209 [44530.354549] ? set_cpu_sibling_map+0xd70/0xd70 Apr 26 04:26:19 192.168.122.209 [44530.354956] ? set_bringup_idt_handler.constprop.0+0x84/0x90 Apr 26 04:26:19 192.168.122.209 [44530.355458] ? start_cpu0+0xc/0xc Apr 26 04:26:19 192.168.122.209 [44530.355759] secondary_startup_64_no_verify+0xb0/0xbb Apr 26 04:26:19 192.168.122.209 [44530.356229] [tempesta fw] Warning: tfw_tls_encrypt: cannot encrypt data (-12) Apr 26 04:26:20 192.168.122.209 [44530.942447] [tdb] Close table 'client0.tdb' Apr 26 04:26:20 192.168.122.209 [44531.169063] [tdb] Close table 'sessions0.tdb' Apr 26 04:26:24 192.168.122.209 [44534.380643] [tdb] Close table 'cache0.tdb' Apr 26 04:26:24 192.168.122.209 [44534.655738] [tdb] Close table 'filter0.tdb' Apr 26 04:26:24 192.168.122.209 [44534.656225] [tempesta fw] modules are stopped Apr 26 04:26:24 192.168.122.209 [44534.844109] [tempesta fw] exiting... Apr 26 04:26:24 192.168.122.209 [44534.998917] [tdb] Shutdown Tempesta DB Apr 26 04:26:24 192.168.122.209 [44535.228522] End test: t_fault_injection.test_fault_injection_base.TestFailFunction.test_ss_skb_to_sgvec_with_new_pages Apr 26 04:26:24 192.168.122.209 [44535.259957] Start test: t_fault_injection.test_fault_injection_base.TestFailFunction.test_tfw_cli_conn_alloc Apr 26 04:26:26 192.168.122.209 [44536.458703] [tdb] Start Tempesta DB Apr 26 04:26:26 192.168.122.209 [44536.636274] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:26:27 192.168.122.209 [44538.046878] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44538.046878] Maybe that's fine, but it's worth checking the [44538.046878] config - if there is no relations between the [44538.046878] names, then host name confusion attack is possible. Apr 26 04:26:27 192.168.122.209 [44538.165616] [tempesta fw] Configuration processing is completed. Apr 26 04:26:27 192.168.122.209 [44538.215727] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:26:28 192.168.122.209 [44538.657344] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:26:28 192.168.122.209 [44538.722392] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:26:28 192.168.122.209 [44538.754958] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:26:28 192.168.122.209 [44538.789549] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:26:28 192.168.122.209 [44538.791299] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:26:28 192.168.122.209 [44538.829513] [tempesta fw] Tempesta FW is ready Apr 26 04:26:28 192.168.122.209 [44539.091065] FAULT_INJECTION: forcing a failure. [44539.091065] name fail_function, interval 0, probability 100, space 0, times -1 Apr 26 04:26:28 192.168.122.209 [44539.092915] CPU: 2 PID: 7925 Comm: python3.10 Tainted: G OE 5.10.35.tfw-39c65d3-debug #1 Apr 26 04:26:28 192.168.122.209 [44539.094350] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 Apr 26 04:26:28 192.168.122.209 [44539.095800] Call Trace: Apr 26 04:26:28 192.168.122.209 [44539.096197] Apr 26 04:26:28 192.168.122.209 [44539.096579] dump_stack+0x96/0xc4 Apr 26 04:26:28 192.168.122.209 [44539.097116] should_fail.cold+0x5/0xa Apr 26 04:26:28 192.168.122.209 [44539.097661] fei_kprobe_handler+0x23/0x60 Apr 26 04:26:28 192.168.122.209 [44539.098055] ? tfw_cli_conn_alloc+0x1/0x140 [tempesta_fw] Apr 26 04:26:28 192.168.122.209 [44539.098564] kprobe_ftrace_handler+0xbe/0x150 Apr 26 04:26:28 192.168.122.209 [44539.098999] ? tfw_cli_conn_alloc+0x5/0x140 [tempesta_fw] Apr 26 04:26:28 192.168.122.209 [44539.099523] ? tfw_sock_clnt_new+0x1a6/0x460 [tempesta_fw] Apr 26 04:26:28 192.168.122.209 [44539.100020] ftrace_ops_assist_func+0xef/0x1b0 Apr 26 04:26:28 192.168.122.209 [44539.100459] ? tfw_cli_conn_abort_all+0x80/0x80 [tempesta_fw] Apr 26 04:26:28 192.168.122.209 [44539.100984] 0xffffffffc16e00e3 Apr 26 04:26:28 192.168.122.209 [44539.101305] RIP: 0010:tfw_cli_conn_alloc+0x1/0x140 [tempesta_fw] Apr 26 04:26:28 192.168.122.209 [44539.101854] Code: e8 14 76 79 f3 48 8b 43 30 48 8d 58 d0 4d 39 f5 75 dc 4c 89 ff e8 2f 55 64 f4 31 c0 5b 41 5c 41 5d 41 5e 41 5f 5d c3 66 90 e8 22 9e ff 55 89 f8 83 e0 0f 48 89 e5 41 54 53 83 f8 03 0f 84 10 Apr 26 04:26:28 192.168.122.209 [44539.103513] RSP: 0018:ffff888147f096d0 EFLAGS: 00000246 ORIG_RAX: 0000000000000000 Apr 26 04:26:28 192.168.122.209 [44539.104245] RAX: 0000000000000000 RBX: ffff88803c696580 RCX: dffffc0000000000 Apr 26 04:26:28 192.168.122.209 [44539.104875] RDX: 0000000000000003 RSI: 0000000000000004 RDI: 0000000000000100 Apr 26 04:26:28 192.168.122.209 [44539.105503] RBP: ffff888147f097a8 R08: ffffffffc1cfe00d R09: 0000000000000003 Apr 26 04:26:28 192.168.122.209 [44539.106130] R10: ffffed1028fe1266 R11: 0000000000000001 R12: ffffffffc1d44500 Apr 26 04:26:28 192.168.122.209 [44539.106760] R13: 1ffff11028fe12e0 R14: ffffffffc1d44430 R15: ffff88813480d010 Apr 26 04:26:28 192.168.122.209 [44539.107421] ? tfw_sock_clnt_new+0x19d/0x460 [tempesta_fw] Apr 26 04:26:28 192.168.122.209 [44539.107934] ? tfw_cli_conn_alloc+0x5/0x140 [tempesta_fw] Apr 26 04:26:28 192.168.122.209 [44539.108444] ? tfw_sock_clnt_new+0x1a6/0x460 [tempesta_fw] Apr 26 04:26:28 192.168.122.209 [44539.108959] ? tfw_cli_conn_alloc+0x5/0x140 [tempesta_fw] Apr 26 04:26:28 192.168.122.209 [44539.109469] ? tfw_sock_clnt_new+0x1a6/0x460 [tempesta_fw] Apr 26 04:26:28 192.168.122.209 [44539.110000] ? tfw_cli_conn_alloc+0x140/0x140 [tempesta_fw] Apr 26 04:26:28 192.168.122.209 [44539.110504] ? tcp_rbtree_insert+0xc0/0xc0 Apr 26 04:26:28 192.168.122.209 [44539.110903] ss_tcp_state_change+0x162/0x310 [tempesta_fw] Apr 26 04:26:28 192.168.122.209 [44539.111393] tcp_rcv_state_process+0x156b/0x1cb0 Apr 26 04:26:28 192.168.122.209 [44539.111803] ? reqsk_put+0x119/0x160 Apr 26 04:26:28 192.168.122.209 [44539.112127] ? tcp_finish_connect+0x1f0/0x1f0 Apr 26 04:26:28 192.168.122.209 [44539.112523] ? inet_csk_complete_hashdance+0x61/0xf0 Apr 26 04:26:28 192.168.122.209 [44539.112965] ? tcp_check_req+0x2f5/0x940 Apr 26 04:26:28 192.168.122.209 [44539.113317] ? tcp_child_process+0x2e0/0x2e0 Apr 26 04:26:28 192.168.122.209 [44539.113708] ? bpf_get_listener_sock+0x11/0x80 Apr 26 04:26:28 192.168.122.209 [44539.114110] tcp_child_process+0x15c/0x2e0 Apr 26 04:26:28 192.168.122.209 [44539.114483] tcp_v4_rcv+0x1179/0x1770 Apr 26 04:26:28 192.168.122.209 [44539.114820] ? tcp_v4_early_demux+0x2f0/0x2f0 Apr 26 04:26:28 192.168.122.209 [44539.115210] ip_protocol_deliver_rcu+0x46/0x2e0 Apr 26 04:26:28 192.168.122.209 [44539.115624] ip_local_deliver_finish+0xc6/0xe0 Apr 26 04:26:28 192.168.122.209 [44539.116025] ip_local_deliver+0x1f5/0x210 Apr 26 04:26:28 192.168.122.209 [44539.116391] ? ip_local_deliver_finish+0xe0/0xe0 Apr 26 04:26:28 192.168.122.209 [44539.116813] ? nf_nat_inet_fn+0x2b3/0x440 [nf_nat] Apr 26 04:26:28 192.168.122.209 [44539.117243] ? ip_protocol_deliver_rcu+0x2e0/0x2e0 Apr 26 04:26:28 192.168.122.209 [44539.117681] ? ip_rcv_finish_core.constprop.0+0x17c/0x890 Apr 26 04:26:28 192.168.122.209 [44539.118181] ip_rcv_finish+0xcf/0xf0 Apr 26 04:26:28 192.168.122.209 [44539.118518] ip_rcv+0x16d/0x180 Apr 26 04:26:28 192.168.122.209 [44539.118812] ? ip_local_deliver+0x210/0x210 Apr 26 04:26:28 192.168.122.209 [44539.119189] ? ip_rcv_finish_core.constprop.0+0x890/0x890 Apr 26 04:26:28 192.168.122.209 [44539.119696] ? update_load_avg+0x132/0xa70 Apr 26 04:26:28 192.168.122.209 [44539.120065] ? ip_local_deliver+0x210/0x210 Apr 26 04:26:28 192.168.122.209 [44539.120451] __netif_receive_skb_one_core+0x132/0x140 Apr 26 04:26:28 192.168.122.209 [44539.120900] ? napi_gro_receive+0x260/0x260 Apr 26 04:26:28 192.168.122.209 [44539.121284] ? __kasan_check_write+0x14/0x20 Apr 26 04:26:28 192.168.122.209 [44539.121686] ? _raw_spin_lock+0x7b/0xd0 Apr 26 04:26:28 192.168.122.209 [44539.122037] __netif_receive_skb+0x26/0xb0 Apr 26 04:26:28 192.168.122.209 [44539.122414] ? generic_exec_single+0xb1/0x170 Apr 26 04:26:28 192.168.122.209 [44539.122807] process_backlog+0xfe/0x290 Apr 26 04:26:28 192.168.122.209 [44539.123155] net_rx_action+0x287/0x6b0 Apr 26 04:26:28 192.168.122.209 [44539.123503] ? try_to_wake_up+0x41e/0xa70 Apr 26 04:26:28 192.168.122.209 [44539.123866] ? napi_complete_done+0x2c0/0x2c0 Apr 26 04:26:28 192.168.122.209 [44539.124258] ? switch_fpu_return+0x120/0x120 Apr 26 04:26:28 192.168.122.209 [44539.124650] __do_softirq+0xfe/0x383 Apr 26 04:26:28 192.168.122.209 [44539.124980] asm_call_irq_on_stack+0xf/0x20 Apr 26 04:26:28 192.168.122.209 [44539.125355] Apr 26 04:26:28 192.168.122.209 [44539.125563] do_softirq_own_stack+0x3d/0x50 Apr 26 04:26:28 192.168.122.209 [44539.125941] irq_exit_rcu+0xc7/0x120 Apr 26 04:26:28 192.168.122.209 [44539.126275] sysvec_call_function_single+0x3a/0x90 Apr 26 04:26:28 192.168.122.209 [44539.126708] ? asm_sysvec_call_function_single+0xa/0x20 Apr 26 04:26:28 192.168.122.209 [44539.127174] asm_sysvec_call_function_single+0x12/0x20 Apr 26 04:26:28 192.168.122.209 [44539.127636] RIP: 0033:0x505dda Apr 26 04:26:28 192.168.122.209 [44539.127923] Code: c0 01 48 89 05 cf 80 3f 00 48 89 43 18 eb 21 90 48 8b 05 c1 80 3f 00 48 83 c0 01 48 89 05 b6 80 3f 00 48 89 43 18 48 83 2f 01 <0f> 84 b0 00 00 00 49 83 2c 24 01 0f 85 88 fe ff ff e9 36 41 f2 ff Apr 26 04:26:28 192.168.122.209 [44539.129547] RSP: 002b:00007fff8107ad90 EFLAGS: 00000206 Apr 26 04:26:28 192.168.122.209 [44539.130016] RAX: 00000000186d3bc7 RBX: 00007f88e6eb6bc0 RCX: 00007fff8107ad98 Apr 26 04:26:28 192.168.122.209 [44539.130660] RDX: 000000000000001f RSI: 00007f88f1dc82b0 RDI: 00007f88f1d5c030 Apr 26 04:26:28 192.168.122.209 [44539.131293] RBP: 00007fff8107add0 R08: 0000000000000016 R09: 0000000002df1608 Apr 26 04:26:28 192.168.122.209 [44539.131922] R10: 0000000000000020 R11: 0000000000000000 R12: 00007f88f1dc82b0 Apr 26 04:26:28 192.168.122.209 [44539.132551] R13: 00007f88ec825170 R14: 0000000000000002 R15: cc8c939620f81df6 Apr 26 04:26:28 192.168.122.209 [44539.133200] [tempesta fw] ERROR: can't allocate a new client connection Apr 26 04:26:29 192.168.122.209 [44539.717226] [tdb] Close table 'client0.tdb' Apr 26 04:26:29 192.168.122.209 [44539.906369] [tdb] Close table 'sessions0.tdb' Apr 26 04:26:32 192.168.122.209 [44543.025212] [tdb] Close table 'cache0.tdb' Apr 26 04:26:32 192.168.122.209 [44543.265370] [tdb] Close table 'filter0.tdb' Apr 26 04:26:32 192.168.122.209 [44543.265835] [tempesta fw] modules are stopped Apr 26 04:26:33 192.168.122.209 [44543.469468] [tempesta fw] exiting... Apr 26 04:26:33 192.168.122.209 [44543.629186] [tdb] Shutdown Tempesta DB Apr 26 04:26:33 192.168.122.209 [44543.847930] End test: t_fault_injection.test_fault_injection_base.TestFailFunction.test_tfw_cli_conn_alloc Apr 26 04:26:33 192.168.122.209 [44543.857103] Start test: t_fault_injection.test_fault_injection_base.TestFailFunction.test_tfw_client_obtain Apr 26 04:26:34 192.168.122.209 [44545.044751] [tdb] Start Tempesta DB Apr 26 04:26:34 192.168.122.209 [44545.198059] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:26:36 192.168.122.209 [44546.646610] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44546.646610] Maybe that's fine, but it's worth checking the [44546.646610] config - if there is no relations between the [44546.646610] names, then host name confusion attack is possible. Apr 26 04:26:36 192.168.122.209 [44546.753645] [tempesta fw] Configuration processing is completed. Apr 26 04:26:36 192.168.122.209 [44546.804545] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:26:36 192.168.122.209 [44547.241261] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:26:36 192.168.122.209 [44547.301347] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:26:36 192.168.122.209 [44547.329937] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:26:37 192.168.122.209 [44547.369681] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:26:37 192.168.122.209 [44547.371434] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:26:37 192.168.122.209 [44547.409587] [tempesta fw] Tempesta FW is ready Apr 26 04:26:37 192.168.122.209 [44547.658921] FAULT_INJECTION: forcing a failure. [44547.658921] name fail_function, interval 0, probability 100, space 0, times -1 Apr 26 04:26:37 192.168.122.209 [44547.660524] CPU: 2 PID: 1094 Comm: sshd Tainted: G OE 5.10.35.tfw-39c65d3-debug #1 Apr 26 04:26:37 192.168.122.209 [44547.661498] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 Apr 26 04:26:37 192.168.122.209 [44547.662308] Call Trace: Apr 26 04:26:37 192.168.122.209 [44547.662540] Apr 26 04:26:37 192.168.122.209 [44547.662738] dump_stack+0x96/0xc4 Apr 26 04:26:37 192.168.122.209 [44547.663038] should_fail.cold+0x5/0xa Apr 26 04:26:37 192.168.122.209 [44547.663373] fei_kprobe_handler+0x23/0x60 Apr 26 04:26:37 192.168.122.209 [44547.663765] ? tfw_client_obtain+0x1/0x290 [tempesta_fw] Apr 26 04:26:37 192.168.122.209 [44547.664240] kprobe_ftrace_handler+0xbe/0x150 Apr 26 04:26:37 192.168.122.209 [44547.664655] ? tfw_client_obtain+0x5/0x290 [tempesta_fw] Apr 26 04:26:37 192.168.122.209 [44547.665152] ? tfw_classify_conn_estab+0x17c/0x410 [tempesta_fw] Apr 26 04:26:37 192.168.122.209 [44547.665686] ftrace_ops_assist_func+0xef/0x1b0 Apr 26 04:26:37 192.168.122.209 [44547.666111] ? tfw_client_stop+0x60/0x60 [tempesta_fw] Apr 26 04:26:37 192.168.122.209 [44547.666573] 0xffffffffc16e00e3 Apr 26 04:26:37 192.168.122.209 [44547.666882] RIP: 0010:tfw_client_obtain+0x1/0x290 [tempesta_fw] Apr 26 04:26:37 192.168.122.209 [44547.667406] Code: 40 48 c1 e7 03 e8 ff fb ff ff 48 8b 3d 58 05 16 00 89 c6 e8 01 67 81 f3 5d c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 e8 <7b> ad aa ff 48 b8 00 00 00 00 00 fc ff df 55 b9 08 00 00 00 48 89 Apr 26 04:26:37 192.168.122.209 [44547.669059] RSP: 0018:ffff888147f09508 EFLAGS: 00000282 ORIG_RAX: 0000000000000000 Apr 26 04:26:37 192.168.122.209 [44547.669748] RAX: 0000000000000000 RBX: 1ffff11028fe12ab RCX: dffffc0000000000 Apr 26 04:26:37 192.168.122.209 [44547.670378] RDX: ffffffffc1c5fee0 RSI: 0000000000000000 RDI: 0000000000000000 Apr 26 04:26:37 192.168.122.209 [44547.671019] RBP: ffff888147f09600 R08: ffffffffc1cf8371 R09: ffff888147f0958f Apr 26 04:26:37 192.168.122.209 [44547.671659] R10: ffffed1028fe12b1 R11: 0000000000000001 R12: ffff88803c692d40 Apr 26 04:26:37 192.168.122.209 [44547.672279] R13: ffff888025a8e480 R14: ffff888029b78000 R15: ffff88803c692dc8 Apr 26 04:26:37 192.168.122.209 [44547.672936] ? ss_getpeername+0x1b1/0x1e0 [tempesta_fw] Apr 26 04:26:37 192.168.122.209 [44547.673421] ? queued_spin_unlock+0x10/0x10 [tempesta_fw] Apr 26 04:26:37 192.168.122.209 [44547.673931] ? tfw_client_obtain+0x5/0x290 [tempesta_fw] Apr 26 04:26:37 192.168.122.209 [44547.674426] ? tfw_classify_conn_estab+0x17c/0x410 [tempesta_fw] Apr 26 04:26:37 192.168.122.209 [44547.674981] ? tfw_client_obtain+0x5/0x290 [tempesta_fw] Apr 26 04:26:37 192.168.122.209 [44547.675480] ? tfw_classify_conn_estab+0x17c/0x410 [tempesta_fw] Apr 26 04:26:37 192.168.122.209 [44547.676038] ? frang_conn_limit+0x3e0/0x3e0 [tempesta_fw] Apr 26 04:26:37 192.168.122.209 [44547.676518] ? memset+0x3c/0x50 Apr 26 04:26:37 192.168.122.209 [44547.676821] tempesta_new_clntsk+0x4d/0x80 Apr 26 04:26:37 192.168.122.209 [44547.677189] tcp_v4_syn_recv_sock+0x558/0x880 Apr 26 04:26:37 192.168.122.209 [44547.677582] ? tcp_add_backlog+0xa60/0xa60 Apr 26 04:26:37 192.168.122.209 [44547.677950] ? bpf_flow_dissect+0x190/0x190 Apr 26 04:26:37 192.168.122.209 [44547.678330] tcp_v6_syn_recv_sock+0xa57/0xed0 Apr 26 04:26:37 192.168.122.209 [44547.678754] ? nft_do_chain+0x6f7/0x860 [nf_tables] Apr 26 04:26:37 192.168.122.209 [44547.679191] ? tcp_v6_do_rcv+0x780/0x780 Apr 26 04:26:37 192.168.122.209 [44547.679548] ? __asan_storeN+0x12/0x20 Apr 26 04:26:37 192.168.122.209 [44547.679887] ? tcp_parse_options+0x444/0x650 Apr 26 04:26:37 192.168.122.209 [44547.680270] tcp_check_req+0x27b/0x940 Apr 26 04:26:37 192.168.122.209 [44547.680616] ? tcp_child_process+0x2e0/0x2e0 Apr 26 04:26:37 192.168.122.209 [44547.680998] ? bpf_get_listener_sock+0x80/0x80 Apr 26 04:26:37 192.168.122.209 [44547.681393] ? memmove+0x4e/0x60 Apr 26 04:26:37 192.168.122.209 [44547.681695] tcp_v4_rcv+0x113a/0x1770 Apr 26 04:26:37 192.168.122.209 [44547.682028] ? tcp_v4_early_demux+0x2f0/0x2f0 Apr 26 04:26:37 192.168.122.209 [44547.682418] ip_protocol_deliver_rcu+0x46/0x2e0 Apr 26 04:26:37 192.168.122.209 [44547.682828] ip_local_deliver_finish+0xc6/0xe0 Apr 26 04:26:37 192.168.122.209 [44547.683227] ip_local_deliver+0x1f5/0x210 Apr 26 04:26:37 192.168.122.209 [44547.683594] ? ip_local_deliver_finish+0xe0/0xe0 Apr 26 04:26:37 192.168.122.209 [44547.684007] ? nf_nat_inet_fn+0x2b3/0x440 [nf_nat] Apr 26 04:26:37 192.168.122.209 [44547.684433] ? ip_protocol_deliver_rcu+0x2e0/0x2e0 Apr 26 04:26:37 192.168.122.209 [44547.684863] ? ip_rcv_finish_core.constprop.0+0x17c/0x890 Apr 26 04:26:37 192.168.122.209 [44547.685346] ip_rcv_finish+0xcf/0xf0 Apr 26 04:26:37 192.168.122.209 [44547.685677] ip_rcv+0x16d/0x180 Apr 26 04:26:37 192.168.122.209 [44547.685965] ? ip_local_deliver+0x210/0x210 Apr 26 04:26:37 192.168.122.209 [44547.686346] ? ip_rcv_finish_core.constprop.0+0x890/0x890 Apr 26 04:26:37 192.168.122.209 [44547.686840] ? virtqueue_poll+0xbb/0xd0 Apr 26 04:26:37 192.168.122.209 [44547.687195] ? virtqueue_napi_complete+0x3f/0x80 [virtio_net] Apr 26 04:26:37 192.168.122.209 [44547.687707] ? ip_local_deliver+0x210/0x210 Apr 26 04:26:37 192.168.122.209 [44547.688085] __netif_receive_skb_one_core+0x132/0x140 Apr 26 04:26:37 192.168.122.209 [44547.688545] ? napi_gro_receive+0x260/0x260 Apr 26 04:26:37 192.168.122.209 [44547.688928] ? __kasan_check_write+0x14/0x20 Apr 26 04:26:37 192.168.122.209 [44547.689314] ? _raw_spin_lock+0x7b/0xd0 Apr 26 04:26:37 192.168.122.209 [44547.689667] __netif_receive_skb+0x26/0xb0 Apr 26 04:26:37 192.168.122.209 [44547.690041] process_backlog+0xfe/0x290 Apr 26 04:26:37 192.168.122.209 [44547.690387] net_rx_action+0x287/0x6b0 Apr 26 04:26:37 192.168.122.209 [44547.690730] ? napi_complete_done+0x2c0/0x2c0 Apr 26 04:26:37 192.168.122.209 [44547.691119] ? switch_fpu_return+0x120/0x120 Apr 26 04:26:37 192.168.122.209 [44547.691509] ? kvm_guest_apic_eoi_write+0x54/0x60 Apr 26 04:26:37 192.168.122.209 [44547.691933] __do_softirq+0xfe/0x383 Apr 26 04:26:37 192.168.122.209 [44547.692257] asm_call_irq_on_stack+0xf/0x20 Apr 26 04:26:37 192.168.122.209 [44547.692638] Apr 26 04:26:37 192.168.122.209 [44547.692840] do_softirq_own_stack+0x3d/0x50 Apr 26 04:26:37 192.168.122.209 [44547.693215] do_softirq+0x72/0x90 Apr 26 04:26:37 192.168.122.209 [44547.693520] __local_bh_enable_ip+0x50/0x60 Apr 26 04:26:37 192.168.122.209 [44547.693901] ip_finish_output2+0x351/0xa80 Apr 26 04:26:37 192.168.122.209 [44547.694272] ? __ip_flush_pending_frames.constprop.0+0x130/0x130 Apr 26 04:26:37 192.168.122.209 [44547.694809] __ip_finish_output+0x16b/0x340 Apr 26 04:26:37 192.168.122.209 [44547.695185] ip_finish_output+0x2d/0xe0 Apr 26 04:26:37 192.168.122.209 [44547.695535] ip_output+0x133/0x210 Apr 26 04:26:37 192.168.122.209 [44547.695847] ? ip_mc_output+0x4e0/0x4e0 Apr 26 04:26:37 192.168.122.209 [44547.696193] ? __ip_finish_output+0x340/0x340 Apr 26 04:26:37 192.168.122.209 [44547.696587] ? ipv4_dst_check+0x6d/0xa0 Apr 26 04:26:37 192.168.122.209 [44547.696931] __ip_queue_xmit+0x356/0x7d0 Apr 26 04:26:37 192.168.122.209 [44547.697287] ip_queue_xmit+0x3b/0x50 Apr 26 04:26:37 192.168.122.209 [44547.697617] __tcp_transmit_skb+0x152f/0x1730 Apr 26 04:26:37 192.168.122.209 [44547.698007] ? __tcp_select_window+0x370/0x370 Apr 26 04:26:37 192.168.122.209 [44547.698405] ? pvclock_clocksource_read+0xe1/0x1a0 Apr 26 04:26:37 192.168.122.209 [44547.698840] ? __kasan_check_read+0x11/0x20 Apr 26 04:26:37 192.168.122.209 [44547.699215] tcp_write_xmit+0x796/0x2a50 Apr 26 04:26:37 192.168.122.209 [44547.699572] __tcp_push_pending_frames+0x5f/0x1a0 Apr 26 04:26:37 192.168.122.209 [44547.699991] tcp_push+0x209/0x2b0 Apr 26 04:26:37 192.168.122.209 [44547.700294] tcp_sendmsg_locked+0x13fa/0x15f0 Apr 26 04:26:37 192.168.122.209 [44547.700687] ? skb_do_copy_data_nocache+0x1b0/0x1b0 Apr 26 04:26:37 192.168.122.209 [44547.701121] ? __kasan_check_write+0x14/0x20 Apr 26 04:26:37 192.168.122.209 [44547.701508] ? _raw_spin_lock_bh+0x86/0xe0 Apr 26 04:26:37 192.168.122.209 [44547.701880] tcp_sendmsg+0x2d/0x50 Apr 26 04:26:37 192.168.122.209 [44547.702187] inet6_sendmsg+0x64/0xa0 Apr 26 04:26:37 192.168.122.209 [44547.702540] ? inet6_ioctl+0x1b0/0x1b0 Apr 26 04:26:37 192.168.122.209 [44547.702877] sock_sendmsg+0x80/0xa0 Apr 26 04:26:37 192.168.122.209 [44547.703198] sock_write_iter+0x14c/0x200 Apr 26 04:26:37 192.168.122.209 [44547.703556] ? sock_sendmsg+0xa0/0xa0 Apr 26 04:26:37 192.168.122.209 [44547.703894] ? fsnotify+0x81c/0x890 Apr 26 04:26:37 192.168.122.209 [44547.704213] new_sync_write+0x3aa/0x3c0 Apr 26 04:26:37 192.168.122.209 [44547.704565] ? new_sync_read+0x3c0/0x3c0 Apr 26 04:26:37 192.168.122.209 [44547.704917] ? rw_verify_area+0x7c/0x150 Apr 26 04:26:37 192.168.122.209 [44547.705272] vfs_write+0x311/0x3d0 Apr 26 04:26:37 192.168.122.209 [44547.705583] ksys_write+0x138/0x170 Apr 26 04:26:37 192.168.122.209 [44547.705906] ? __ia32_sys_read+0x50/0x50 Apr 26 04:26:37 192.168.122.209 [44547.706260] ? __x32_compat_sys_rt_sigprocmask+0x1a0/0x1a0 Apr 26 04:26:37 192.168.122.209 [44547.706751] ? __kasan_check_read+0x11/0x20 Apr 26 04:26:37 192.168.122.209 [44547.707126] ? fpregs_assert_state_consistent+0x5a/0x70 Apr 26 04:26:37 192.168.122.209 [44547.707597] __x64_sys_write+0x42/0x50 Apr 26 04:26:37 192.168.122.209 [44547.707935] do_syscall_64+0x38/0x90 Apr 26 04:26:37 192.168.122.209 [44547.708256] entry_SYSCALL_64_after_hwframe+0x44/0xa9 Apr 26 04:26:37 192.168.122.209 [44547.708707] RIP: 0033:0x7fd0529dd574 Apr 26 04:26:37 192.168.122.209 [44547.709033] Code: c7 00 16 00 00 00 b8 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 80 3d d5 ea 0e 00 00 74 13 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 54 c3 0f 1f 00 55 48 89 e5 48 83 ec 20 48 89 Apr 26 04:26:37 192.168.122.209 [44547.710644] RSP: 002b:00007ffc32c42618 EFLAGS: 00000202 ORIG_RAX: 0000000000000001 Apr 26 04:26:37 192.168.122.209 [44547.711308] RAX: ffffffffffffffda RBX: 0000000000000bd0 RCX: 00007fd0529dd574 Apr 26 04:26:37 192.168.122.209 [44547.711941] RDX: 0000000000000bd0 RSI: 0000564828fe3730 RDI: 0000000000000004 Apr 26 04:26:37 192.168.122.209 [44547.712577] RBP: 00007ffc32c42630 R08: 0000000000000000 R09: 0000000000000000 Apr 26 04:26:37 192.168.122.209 [44547.713196] R10: 00007ffc32da2080 R11: 0000000000000202 R12: 0000564828fb0c10 Apr 26 04:26:37 192.168.122.209 [44547.713821] R13: 0000000000000000 R14: 000000000000000a R15: 0000000000000001 Apr 26 04:26:37 192.168.122.209 [44547.714481] [tempesta fw] ERROR: can't obtain a client for frang accounting Apr 26 04:26:37 192.168.122.209 [44548.311238] [tdb] Close table 'client0.tdb' Apr 26 04:26:38 192.168.122.209 [44548.508260] [tdb] Close table 'sessions0.tdb' Apr 26 04:26:41 192.168.122.209 [44551.636302] [tdb] Close table 'cache0.tdb' Apr 26 04:26:41 192.168.122.209 [44551.875912] [tdb] Close table 'filter0.tdb' Apr 26 04:26:41 192.168.122.209 [44551.876371] [tempesta fw] modules are stopped Apr 26 04:26:41 192.168.122.209 [44552.051471] [tempesta fw] exiting... Apr 26 04:26:41 192.168.122.209 [44552.185827] [tdb] Shutdown Tempesta DB Apr 26 04:26:42 192.168.122.209 [44552.428365] End test: t_fault_injection.test_fault_injection_base.TestFailFunction.test_tfw_client_obtain Apr 26 04:26:42 192.168.122.209 [44552.443562] Start test: t_fault_injection.test_fault_injection_base.TestFailFunction.test_tfw_h2_entail_stream_skb Apr 26 04:26:43 192.168.122.209 [44553.630716] [tdb] Start Tempesta DB Apr 26 04:26:43 192.168.122.209 [44553.776251] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:26:44 192.168.122.209 [44555.259437] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44555.259437] Maybe that's fine, but it's worth checking the [44555.259437] config - if there is no relations between the [44555.259437] names, then host name confusion attack is possible. Apr 26 04:26:45 192.168.122.209 [44555.381871] [tempesta fw] Configuration processing is completed. Apr 26 04:26:45 192.168.122.209 [44555.436777] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:26:45 192.168.122.209 [44555.912781] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:26:45 192.168.122.209 [44555.941797] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:26:45 192.168.122.209 [44555.970514] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:26:45 192.168.122.209 [44556.009780] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:26:45 192.168.122.209 [44556.011523] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:26:45 192.168.122.209 [44556.065724] [tempesta fw] Tempesta FW is ready Apr 26 04:26:45 192.168.122.209 [44556.317153] FAULT_INJECTION: forcing a failure. [44556.317153] name fail_function, interval 0, probability 100, space 0, times 1 Apr 26 04:26:45 192.168.122.209 [44556.318235] CPU: 2 PID: 0 Comm: swapper/2 Tainted: G OE 5.10.35.tfw-39c65d3-debug #1 Apr 26 04:26:45 192.168.122.209 [44556.319031] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 Apr 26 04:26:45 192.168.122.209 [44556.319847] Call Trace: Apr 26 04:26:45 192.168.122.209 [44556.320076] Apr 26 04:26:45 192.168.122.209 [44556.320273] dump_stack+0x96/0xc4 Apr 26 04:26:45 192.168.122.209 [44556.320579] should_fail.cold+0x5/0xa Apr 26 04:26:45 192.168.122.209 [44556.320921] fei_kprobe_handler+0x23/0x60 Apr 26 04:26:45 192.168.122.209 [44556.321312] ? tfw_h2_entail_stream_skb+0x1/0x5d0 [tempesta_fw] Apr 26 04:26:45 192.168.122.209 [44556.321843] kprobe_ftrace_handler+0xbe/0x150 Apr 26 04:26:45 192.168.122.209 [44556.322260] ? tfw_h2_entail_stream_skb+0x5/0x5d0 [tempesta_fw] Apr 26 04:26:45 192.168.122.209 [44556.322812] ? tfw_h2_make_frames+0x2d2/0xa50 [tempesta_fw] Apr 26 04:26:45 192.168.122.209 [44556.323309] ftrace_ops_assist_func+0xef/0x1b0 Apr 26 04:26:45 192.168.122.209 [44556.323757] ? tfw_h2_stream_xmit_prepare_resp+0x680/0x680 [tempesta_fw] Apr 26 04:26:45 192.168.122.209 [44556.324354] 0xffffffffc16e00e3 Apr 26 04:26:45 192.168.122.209 [44556.324673] RIP: 0010:tfw_h2_entail_stream_skb+0x1/0x5d0 [tempesta_fw] Apr 26 04:26:45 192.168.122.209 [44556.325249] Code: ff ff 48 8b 5d d0 4c 8b 7d a0 41 89 c5 4c 8b 65 98 e9 02 ff ff ff e8 1e ac 39 f4 85 c0 0f 84 b8 fb ff ff e9 be 3a 0c 00 90 e8 89 a8 ff 55 48 8d 82 a0 03 00 00 48 89 e5 41 57 41 56 41 55 49 Apr 26 04:26:45 192.168.122.209 [44556.326921] RSP: 0018:ffff888147f09c20 EFLAGS: 00000246 ORIG_RAX: 0000000000000000 Apr 26 04:26:45 192.168.122.209 [44556.327627] RAX: 0000000000000000 RBX: ffff888057679334 RCX: ffff888057679334 Apr 26 04:26:45 192.168.122.209 [44556.328253] RDX: ffff888057678f80 RSI: ffff888066736f80 RDI: ffff88803c6916c0 Apr 26 04:26:45 192.168.122.209 [44556.328882] RBP: ffff888147f09d30 R08: 0000000000000000 R09: 0000000000000003 Apr 26 04:26:45 192.168.122.209 [44556.329506] R10: ffffed1028fe1334 R11: 0000000000000001 R12: ffff888057678f80 Apr 26 04:26:45 192.168.122.209 [44556.330140] R13: ffff888066736f80 R14: ffff888057679338 R15: ffff888147f09d08 Apr 26 04:26:45 192.168.122.209 [44556.330797] ? tfw_h2_entail_stream_skb+0x5/0x5d0 [tempesta_fw] Apr 26 04:26:45 192.168.122.209 [44556.331347] ? tfw_h2_make_frames+0x2d2/0xa50 [tempesta_fw] Apr 26 04:26:45 192.168.122.209 [44556.331871] ? tfw_h2_entail_stream_skb+0x5/0x5d0 [tempesta_fw] Apr 26 04:26:45 192.168.122.209 [44556.332428] ? tfw_h2_make_frames+0x2d2/0xa50 [tempesta_fw] Apr 26 04:26:45 192.168.122.209 [44556.332950] ? tfw_h2_frame_process+0xf20/0xf20 [tempesta_fw] Apr 26 04:26:45 192.168.122.209 [44556.333487] tfw_sk_fill_write_queue+0x2c8/0x360 [tempesta_fw] Apr 26 04:26:45 192.168.122.209 [44556.334036] ? tfw_sock_clnt_start+0x640/0x640 [tempesta_fw] Apr 26 04:26:45 192.168.122.209 [44556.334566] ? tfw_h2_sched_activate_stream+0xc8/0x190 [tempesta_fw] Apr 26 04:26:45 192.168.122.209 [44556.335160] ? ss_skb_tcp_entail_list+0x25/0x1a0 [tempesta_fw] Apr 26 04:26:45 192.168.122.209 [44556.335734] ss_tx_action+0x6eb/0xc20 [tempesta_fw] Apr 26 04:26:45 192.168.122.209 [44556.336196] ? ss_skb_tcp_entail_list+0x1a0/0x1a0 [tempesta_fw] Apr 26 04:26:45 192.168.122.209 [44556.336729] ? __kfree_skb_flush+0x27/0x60 Apr 26 04:26:45 192.168.122.209 [44556.337126] ? net_rx_action+0x438/0x6b0 Apr 26 04:26:45 192.168.122.209 [44556.337482] ? __kernel_fpu_begin_mask+0x9a/0x150 Apr 26 04:26:45 192.168.122.209 [44556.337910] net_tx_action+0xfa/0x3c0 Apr 26 04:26:45 192.168.122.209 [44556.338247] __do_softirq+0xfe/0x383 Apr 26 04:26:45 192.168.122.209 [44556.338569] asm_call_irq_on_stack+0xf/0x20 Apr 26 04:26:45 192.168.122.209 [44556.338945] Apr 26 04:26:45 192.168.122.209 [44556.339142] do_softirq_own_stack+0x3d/0x50 Apr 26 04:26:45 192.168.122.209 [44556.339538] irq_exit_rcu+0xc7/0x120 Apr 26 04:26:45 192.168.122.209 [44556.339866] sysvec_call_function_single+0x3a/0x90 Apr 26 04:26:45 192.168.122.209 [44556.340290] asm_sysvec_call_function_single+0x12/0x20 Apr 26 04:26:45 192.168.122.209 [44556.340756] RIP: 0010:native_safe_halt+0xe/0x10 Apr 26 04:26:45 192.168.122.209 [44556.341166] Code: 49 8b 04 24 a8 08 0f 85 71 ff ff ff e9 0f ff ff ff cc cc cc cc cc cc cc cc cc cc cc e9 07 00 00 00 0f 00 2d d4 62 51 00 fb f4 90 e9 07 00 00 00 0f 00 2d c4 62 51 00 f4 c3 cc cc 0f 1f 44 00 Apr 26 04:26:45 192.168.122.209 [44556.342777] RSP: 0018:ffff888100f3fdb8 EFLAGS: 00000216 Apr 26 04:26:45 192.168.122.209 [44556.343240] RAX: ffffffffb63426a0 RBX: ffff888100f2a080 RCX: ffffffffb632c475 Apr 26 04:26:45 192.168.122.209 [44556.343867] RDX: 000000000b111cfe RSI: 0000000000000004 RDI: ffff888147f35040 Apr 26 04:26:45 192.168.122.209 [44556.344494] RBP: ffff888100f3fdc0 R08: 0000000000000001 R09: ffff888147f35043 Apr 26 04:26:45 192.168.122.209 [44556.345120] R10: ffffed1028fe6a08 R11: 0000000000000001 R12: 0000000000000002 Apr 26 04:26:45 192.168.122.209 [44556.345747] R13: ffffffffb7ae9360 R14: 0000000000000000 R15: 0000000000000000 Apr 26 04:26:45 192.168.122.209 [44556.346379] ? __cpuidle_text_start+0x8/0x8 Apr 26 04:26:45 192.168.122.209 [44556.346760] ? rcu_eqs_enter.constprop.0+0x85/0xa0 Apr 26 04:26:45 192.168.122.209 [44556.347185] ? default_idle+0xe/0x20 Apr 26 04:26:45 192.168.122.209 [44556.347513] arch_cpu_idle+0x15/0x20 Apr 26 04:26:45 192.168.122.209 [44556.347843] default_idle_call+0x66/0x160 Apr 26 04:26:45 192.168.122.209 [44556.348210] do_idle+0x36f/0x430 Apr 26 04:26:45 192.168.122.209 [44556.348502] ? asm_sysvec_apic_timer_interrupt+0x12/0x20 Apr 26 04:26:45 192.168.122.209 [44556.348991] ? arch_cpu_idle_exit+0x40/0x40 Apr 26 04:26:45 192.168.122.209 [44556.349365] cpu_startup_entry+0x20/0x30 Apr 26 04:26:45 192.168.122.209 [44556.349727] start_secondary+0x1c1/0x210 Apr 26 04:26:45 192.168.122.209 [44556.350080] ? set_cpu_sibling_map+0xd70/0xd70 Apr 26 04:26:45 192.168.122.209 [44556.350478] ? set_bringup_idt_handler.constprop.0+0x84/0x90 Apr 26 04:26:45 192.168.122.209 [44556.350985] ? start_cpu0+0xc/0xc Apr 26 04:26:45 192.168.122.209 [44556.351296] secondary_startup_64_no_verify+0xb0/0xbb Apr 26 04:26:46 192.168.122.209 [44556.351770] [tempesta fw] Warning: Failed to send frame -12 Apr 26 04:26:46 192.168.122.209 [44556.829515] [tdb] Close table 'client0.tdb' Apr 26 04:26:46 192.168.122.209 [44557.051056] [tdb] Close table 'sessions0.tdb' Apr 26 04:26:49 192.168.122.209 [44560.181377] [tdb] Close table 'cache0.tdb' Apr 26 04:26:50 192.168.122.209 [44560.453908] [tdb] Close table 'filter0.tdb' Apr 26 04:26:50 192.168.122.209 [44560.454336] [tempesta fw] modules are stopped Apr 26 04:26:50 192.168.122.209 [44560.638481] [tempesta fw] exiting... Apr 26 04:26:50 192.168.122.209 [44560.797237] [tdb] Shutdown Tempesta DB Apr 26 04:26:50 192.168.122.209 [44560.998299] End test: t_fault_injection.test_fault_injection_base.TestFailFunction.test_tfw_h2_entail_stream_skb Apr 26 04:26:50 192.168.122.209 [44561.014323] Start test: t_fault_injection.test_fault_injection_base.TestFailFunction.test_tfw_h2_stream_xmit_prepare_resp Apr 26 04:26:51 192.168.122.209 [44562.153284] [tdb] Start Tempesta DB Apr 26 04:26:51 192.168.122.209 [44562.309013] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:26:53 192.168.122.209 [44563.763136] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44563.763136] Maybe that's fine, but it's worth checking the [44563.763136] config - if there is no relations between the [44563.763136] names, then host name confusion attack is possible. Apr 26 04:26:53 192.168.122.209 [44563.905940] [tempesta fw] Configuration processing is completed. Apr 26 04:26:53 192.168.122.209 [44563.957735] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:26:54 192.168.122.209 [44564.369521] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:26:54 192.168.122.209 [44564.433117] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:26:54 192.168.122.209 [44564.460051] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:26:54 192.168.122.209 [44564.497880] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:26:54 192.168.122.209 [44564.499607] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:26:54 192.168.122.209 [44564.537824] [tempesta fw] Tempesta FW is ready Apr 26 04:26:54 192.168.122.209 [44564.779320] FAULT_INJECTION: forcing a failure. [44564.779320] name fail_function, interval 0, probability 100, space 0, times 1 Apr 26 04:26:54 192.168.122.209 [44564.780790] CPU: 3 PID: 0 Comm: swapper/3 Tainted: G OE 5.10.35.tfw-39c65d3-debug #1 Apr 26 04:26:54 192.168.122.209 [44564.781926] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 Apr 26 04:26:54 192.168.122.209 [44564.783058] Call Trace: Apr 26 04:26:54 192.168.122.209 [44564.783376] Apr 26 04:26:54 192.168.122.209 [44564.783647] dump_stack+0x96/0xc4 Apr 26 04:26:54 192.168.122.209 [44564.784078] should_fail.cold+0x5/0xa Apr 26 04:26:54 192.168.122.209 [44564.784547] fei_kprobe_handler+0x23/0x60 Apr 26 04:26:54 192.168.122.209 [44564.785128] ? tfw_h2_stream_xmit_prepare_resp+0x1/0x680 [tempesta_fw] Apr 26 04:26:54 192.168.122.209 [44564.785958] kprobe_ftrace_handler+0xbe/0x150 Apr 26 04:26:54 192.168.122.209 [44564.786459] ? tfw_h2_stream_xmit_prepare_resp+0x5/0x680 [tempesta_fw] Apr 26 04:26:54 192.168.122.209 [44564.787077] ? tfw_h2_make_frames+0x835/0xa50 [tempesta_fw] Apr 26 04:26:54 192.168.122.209 [44564.787585] ftrace_ops_assist_func+0xef/0x1b0 Apr 26 04:26:54 192.168.122.209 [44564.788034] ? tfw_http_exit+0x20/0x20 [tempesta_fw] Apr 26 04:26:54 192.168.122.209 [44564.788488] 0xffffffffc16e00e3 Apr 26 04:26:54 192.168.122.209 [44564.788813] RIP: 0010:tfw_h2_stream_xmit_prepare_resp+0x1/0x680 [tempesta_fw] Apr 26 04:26:54 192.168.122.209 [44564.789450] Code: 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 c7 c7 40 39 d6 c1 48 89 e5 e8 ab ba 09 00 31 ff e8 f4 ef fd ff 5d c3 66 90 e8 <2b> 90 a8 ff 55 48 89 e5 41 57 41 56 41 55 41 54 49 89 fc 48 81 c7 Apr 26 04:26:54 192.168.122.209 [44564.791138] RSP: 0018:ffff888147f89c20 EFLAGS: 00000246 ORIG_RAX: 0000000000000000 Apr 26 04:26:54 192.168.122.209 [44564.791817] RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffffc1c5f5de Apr 26 04:26:54 192.168.122.209 [44564.792453] RDX: dffffc0000000000 RSI: 0000000000000001 RDI: ffff888038d9e200 Apr 26 04:26:54 192.168.122.209 [44564.793117] RBP: ffff888147f89d30 R08: ffffffffc1cee3a6 R09: ffff88802d2a88af Apr 26 04:26:54 192.168.122.209 [44564.793769] R10: ffffed1005a55115 R11: 0000000000000001 R12: ffff888038d9e200 Apr 26 04:26:54 192.168.122.209 [44564.794407] R13: ffff88802d2a8848 R14: ffff888038d9e5b8 R15: ffff888147f89d08 Apr 26 04:26:54 192.168.122.209 [44564.795103] ? tfw_h2_stream_sched_remove+0x86/0x210 [tempesta_fw] Apr 26 04:26:54 192.168.122.209 [44564.795682] ? tfw_h2_make_frames+0x15e/0xa50 [tempesta_fw] Apr 26 04:26:54 192.168.122.209 [44564.796215] ? tfw_h2_stream_xmit_prepare_resp+0x5/0x680 [tempesta_fw] Apr 26 04:26:54 192.168.122.209 [44564.796829] ? tfw_h2_make_frames+0x835/0xa50 [tempesta_fw] Apr 26 04:26:54 192.168.122.209 [44564.797357] ? tfw_h2_stream_xmit_prepare_resp+0x5/0x680 [tempesta_fw] Apr 26 04:26:54 192.168.122.209 [44564.797992] ? tfw_h2_make_frames+0x835/0xa50 [tempesta_fw] Apr 26 04:26:54 192.168.122.209 [44564.798499] ? __asan_loadN+0xf/0x20 Apr 26 04:26:54 192.168.122.209 [44564.798865] ? tfw_h2_frame_process+0xf20/0xf20 [tempesta_fw] Apr 26 04:26:54 192.168.122.209 [44564.799411] tfw_sk_fill_write_queue+0x2c8/0x360 [tempesta_fw] Apr 26 04:26:54 192.168.122.209 [44564.799965] ? tfw_sock_clnt_start+0x640/0x640 [tempesta_fw] Apr 26 04:26:54 192.168.122.209 [44564.800500] ? tfw_h2_sched_activate_stream+0xc8/0x190 [tempesta_fw] Apr 26 04:26:54 192.168.122.209 [44564.801100] ? ss_skb_tcp_entail_list+0x25/0x1a0 [tempesta_fw] Apr 26 04:26:54 192.168.122.209 [44564.801654] ss_tx_action+0x6eb/0xc20 [tempesta_fw] Apr 26 04:26:54 192.168.122.209 [44564.802140] ? ss_skb_tcp_entail_list+0x1a0/0x1a0 [tempesta_fw] Apr 26 04:26:54 192.168.122.209 [44564.802672] ? net_rps_send_ipi+0x91/0xa0 Apr 26 04:26:54 192.168.122.209 [44564.803048] ? __kfree_skb_flush+0x27/0x60 Apr 26 04:26:54 192.168.122.209 [44564.803423] ? net_rx_action+0x438/0x6b0 Apr 26 04:26:54 192.168.122.209 [44564.803786] ? napi_complete_done+0x2c0/0x2c0 Apr 26 04:26:54 192.168.122.209 [44564.804184] net_tx_action+0xfa/0x3c0 Apr 26 04:26:54 192.168.122.209 [44564.804525] __do_softirq+0xfe/0x383 Apr 26 04:26:54 192.168.122.209 [44564.804863] asm_call_irq_on_stack+0xf/0x20 Apr 26 04:26:54 192.168.122.209 [44564.805264] Apr 26 04:26:54 192.168.122.209 [44564.805467] do_softirq_own_stack+0x3d/0x50 Apr 26 04:26:54 192.168.122.209 [44564.805882] irq_exit_rcu+0xc7/0x120 Apr 26 04:26:54 192.168.122.209 [44564.806214] sysvec_call_function_single+0x3a/0x90 Apr 26 04:26:54 192.168.122.209 [44564.806648] asm_sysvec_call_function_single+0x12/0x20 Apr 26 04:26:54 192.168.122.209 [44564.807118] RIP: 0010:native_safe_halt+0xe/0x10 Apr 26 04:26:54 192.168.122.209 [44564.807535] Code: 49 8b 04 24 a8 08 0f 85 71 ff ff ff e9 0f ff ff ff cc cc cc cc cc cc cc cc cc cc cc e9 07 00 00 00 0f 00 2d d4 62 51 00 fb f4 90 e9 07 00 00 00 0f 00 2d c4 62 51 00 f4 c3 cc cc 0f 1f 44 00 Apr 26 04:26:54 192.168.122.209 [44564.809203] RSP: 0018:ffff888100f47db8 EFLAGS: 00000206 Apr 26 04:26:54 192.168.122.209 [44564.809680] RAX: ffffffffb63426a0 RBX: ffff888100f28040 RCX: ffffffffb632c475 Apr 26 04:26:54 192.168.122.209 [44564.810322] RDX: 000000000b300e16 RSI: 0000000000000004 RDI: ffff888147fb5040 Apr 26 04:26:54 192.168.122.209 [44564.810971] RBP: ffff888100f47dc0 R08: 0000000000000001 R09: ffff888147fb5043 Apr 26 04:26:54 192.168.122.209 [44564.811611] R10: ffffed1028ff6a08 R11: 0000000000000001 R12: 0000000000000003 Apr 26 04:26:54 192.168.122.209 [44564.812247] R13: ffffffffb7ae9360 R14: 0000000000000000 R15: 0000000000000000 Apr 26 04:26:54 192.168.122.209 [44564.812887] ? __cpuidle_text_start+0x8/0x8 Apr 26 04:26:54 192.168.122.209 [44564.813282] ? rcu_eqs_enter.constprop.0+0x85/0xa0 Apr 26 04:26:54 192.168.122.209 [44564.813744] ? default_idle+0xe/0x20 Apr 26 04:26:54 192.168.122.209 [44564.814074] arch_cpu_idle+0x15/0x20 Apr 26 04:26:54 192.168.122.209 [44564.814403] default_idle_call+0x66/0x160 Apr 26 04:26:54 192.168.122.209 [44564.814778] do_idle+0x36f/0x430 Apr 26 04:26:54 192.168.122.209 [44564.815079] ? asm_common_interrupt+0x1e/0x40 Apr 26 04:26:54 192.168.122.209 [44564.815499] ? arch_cpu_idle_exit+0x40/0x40 Apr 26 04:26:54 192.168.122.209 [44564.815886] cpu_startup_entry+0x20/0x30 Apr 26 04:26:54 192.168.122.209 [44564.816252] start_secondary+0x1c1/0x210 Apr 26 04:26:54 192.168.122.209 [44564.816613] ? set_cpu_sibling_map+0xd70/0xd70 Apr 26 04:26:54 192.168.122.209 [44564.817022] ? set_bringup_idt_handler.constprop.0+0x84/0x90 Apr 26 04:26:54 192.168.122.209 [44564.817531] ? start_cpu0+0xc/0xc Apr 26 04:26:54 192.168.122.209 [44564.817858] secondary_startup_64_no_verify+0xb0/0xbb Apr 26 04:26:54 192.168.122.209 [44565.307903] [tdb] Close table 'client0.tdb' Apr 26 04:26:55 192.168.122.209 [44565.499854] [tdb] Close table 'sessions0.tdb' Apr 26 04:26:58 192.168.122.209 [44568.637391] [tdb] Close table 'cache0.tdb' Apr 26 04:26:58 192.168.122.209 [44568.889217] [tdb] Close table 'filter0.tdb' Apr 26 04:26:58 192.168.122.209 [44568.889675] [tempesta fw] modules are stopped Apr 26 04:26:58 192.168.122.209 [44569.062178] [tempesta fw] exiting... Apr 26 04:26:58 192.168.122.209 [44569.221400] [tdb] Shutdown Tempesta DB Apr 26 04:26:59 192.168.122.209 [44569.458532] End test: t_fault_injection.test_fault_injection_base.TestFailFunction.test_tfw_h2_stream_xmit_prepare_resp Apr 26 04:26:59 192.168.122.209 [44569.465103] Start test: t_fault_injection.test_fault_injection_base.TestFailFunction.test_tfw_hpack_init Apr 26 04:27:00 192.168.122.209 [44570.646753] [tdb] Start Tempesta DB Apr 26 04:27:00 192.168.122.209 [44570.800466] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:27:01 192.168.122.209 [44572.245059] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44572.245059] Maybe that's fine, but it's worth checking the [44572.245059] config - if there is no relations between the [44572.245059] names, then host name confusion attack is possible. Apr 26 04:27:01 192.168.122.209 [44572.350048] [tempesta fw] Configuration processing is completed. Apr 26 04:27:02 192.168.122.209 [44572.400912] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:27:02 192.168.122.209 [44572.819478] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:27:02 192.168.122.209 [44572.883738] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:27:02 192.168.122.209 [44572.910643] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:27:02 192.168.122.209 [44572.966011] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:27:02 192.168.122.209 [44572.967746] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:27:02 192.168.122.209 [44573.013923] [tempesta fw] Tempesta FW is ready Apr 26 04:27:02 192.168.122.209 [44573.265278] FAULT_INJECTION: forcing a failure. [44573.265278] name fail_function, interval 0, probability 100, space 0, times -1 Apr 26 04:27:02 192.168.122.209 [44573.267571] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G OE 5.10.35.tfw-39c65d3-debug #1 Apr 26 04:27:02 192.168.122.209 [44573.269022] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 Apr 26 04:27:02 192.168.122.209 [44573.270065] Call Trace: Apr 26 04:27:02 192.168.122.209 [44573.270356] Apr 26 04:27:02 192.168.122.209 [44573.270609] dump_stack+0x96/0xc4 Apr 26 04:27:02 192.168.122.209 [44573.271001] should_fail.cold+0x5/0xa Apr 26 04:27:02 192.168.122.209 [44573.271429] fei_kprobe_handler+0x23/0x60 Apr 26 04:27:02 192.168.122.209 [44573.271932] ? tfw_hpack_init+0x1/0x1c0 [tempesta_fw] Apr 26 04:27:02 192.168.122.209 [44573.272510] kprobe_ftrace_handler+0xbe/0x150 Apr 26 04:27:02 192.168.122.209 [44573.273043] ? tfw_hpack_init+0x5/0x1c0 [tempesta_fw] Apr 26 04:27:02 192.168.122.209 [44573.273651] ? tfw_h2_context_init+0x247/0x250 [tempesta_fw] Apr 26 04:27:02 192.168.122.209 [44573.274296] ftrace_ops_assist_func+0xef/0x1b0 Apr 26 04:27:02 192.168.122.209 [44573.274843] ? tfw_hpack_rbtree_find.constprop.0.isra.0+0x5d0/0x5d0 [tempesta_fw] Apr 26 04:27:02 192.168.122.209 [44573.275681] 0xffffffffc16e00e3 Apr 26 04:27:02 192.168.122.209 [44573.276083] RIP: 0010:tfw_hpack_init+0x1/0x1c0 [tempesta_fw] Apr 26 04:27:02 192.168.122.209 [44573.276723] Code: 0b 4c 8b 6d 88 4c 8b 75 80 48 8b 45 c8 45 85 e4 79 09 48 8d 58 0e e9 7d fd ff ff 48 8d 58 10 e9 74 fd ff ff 0f 1f 44 00 00 e8 83 aa ff 55 48 89 e5 41 57 41 56 41 55 41 54 41 89 f4 53 48 89 Apr 26 04:27:02 192.168.122.209 [44573.278816] RSP: 0018:ffff888147e88eb0 EFLAGS: 00000246 ORIG_RAX: 0000000000000000 Apr 26 04:27:02 192.168.122.209 [44573.279569] RAX: 0000000000000000 RBX: ffff88803f111f38 RCX: dffffc0000000000 Apr 26 04:27:02 192.168.122.209 [44573.280201] RDX: 0000000000000003 RSI: 0000000000001000 RDI: ffff88803f112000 Apr 26 04:27:02 192.168.122.209 [44573.280835] RBP: ffff888147e88ec8 R08: ffffffffc1c583df R09: ffff888147e88a68 Apr 26 04:27:02 192.168.122.209 [44573.281467] R10: ffffed1028fd1158 R11: 0000000000000001 R12: 0000000000004000 Apr 26 04:27:02 192.168.122.209 [44573.282097] R13: 0000000000000000 R14: ffff888007d5f532 R15: ffff88803f111bb0 Apr 26 04:27:02 192.168.122.209 [44573.282750] ? tfw_h2_context_init+0x22f/0x250 [tempesta_fw] Apr 26 04:27:02 192.168.122.209 [44573.283282] ? tfw_hpack_init+0x5/0x1c0 [tempesta_fw] Apr 26 04:27:02 192.168.122.209 [44573.283759] ? tfw_h2_context_init+0x247/0x250 [tempesta_fw] Apr 26 04:27:02 192.168.122.209 [44573.284287] ? tfw_hpack_init+0x5/0x1c0 [tempesta_fw] Apr 26 04:27:02 192.168.122.209 [44573.284761] ? tfw_h2_context_init+0x247/0x250 [tempesta_fw] Apr 26 04:27:02 192.168.122.209 [44573.285300] tfw_tls_over+0x76/0x90 [tempesta_fw] Apr 26 04:27:02 192.168.122.209 [44573.285735] ttls_handshake_server_step+0x6f4/0x3950 [tempesta_tls] Apr 26 04:27:02 192.168.122.209 [44573.286311] ? loopback_xmit+0x15e/0x1b0 Apr 26 04:27:02 192.168.122.209 [44573.286676] ? ttls_parse_client_hello+0x2c60/0x2c60 [tempesta_tls] Apr 26 04:27:02 192.168.122.209 [44573.287242] ? flush_tlb_one_user+0x20/0x20 Apr 26 04:27:02 192.168.122.209 [44573.287626] ? __kasan_check_read+0x11/0x20 Apr 26 04:27:02 192.168.122.209 [44573.288006] ? __flush_tlb_all+0x37/0x50 Apr 26 04:27:02 192.168.122.209 [44573.288360] ? __kernel_map_pages+0x108/0x180 Apr 26 04:27:02 192.168.122.209 [44573.288753] ? set_direct_map_default_noflush+0x130/0x130 Apr 26 04:27:02 192.168.122.209 [44573.289245] ? netdev_core_pick_tx+0x120/0x120 Apr 26 04:27:02 192.168.122.209 [44573.289643] ? flush_tlb_one_user+0x20/0x20 Apr 26 04:27:02 192.168.122.209 [44573.290025] ? __flush_tlb_all+0x37/0x50 Apr 26 04:27:02 192.168.122.209 [44573.290379] ? __kernel_map_pages+0x108/0x180 Apr 26 04:27:02 192.168.122.209 [44573.290773] ? set_direct_map_default_noflush+0x130/0x130 Apr 26 04:27:02 192.168.122.209 [44573.291257] ? __alloc_pages_slowpath.constprop.0+0x1390/0x1390 Apr 26 04:27:02 192.168.122.209 [44573.291789] ttls_recv+0x53d/0xbc0 [tempesta_tls] Apr 26 04:27:02 192.168.122.209 [44573.292222] ? ttls_handle_alert+0x50/0x50 [tempesta_tls] Apr 26 04:27:02 192.168.122.209 [44573.292732] ss_skb_process+0x270/0x2f0 [tempesta_fw] Apr 26 04:27:02 192.168.122.209 [44573.293195] ? ttls_handle_alert+0x50/0x50 [tempesta_tls] Apr 26 04:27:02 192.168.122.209 [44573.293703] ? tfw_sock_srv_exit+0x30/0x30 [tempesta_fw] Apr 26 04:27:02 192.168.122.209 [44573.294181] ? _raw_write_lock_irqsave+0xe0/0xe0 Apr 26 04:27:02 192.168.122.209 [44573.294599] ? kfree_skbmem+0x10b/0x220 Apr 26 04:27:02 192.168.122.209 [44573.294976] tfw_tls_connection_recv+0x14e/0x730 [tempesta_fw] Apr 26 04:27:02 192.168.122.209 [44573.295519] ? tfw_tls_connection_lost+0x40/0x40 [tempesta_fw] Apr 26 04:27:02 192.168.122.209 [44573.296067] ? ss_skb_unroll+0x3d6/0x540 [tempesta_fw] Apr 26 04:27:02 192.168.122.209 [44573.296556] ss_tcp_process_data+0x436/0x8b0 [tempesta_fw] Apr 26 04:27:02 192.168.122.209 [44573.297074] ? __sk_close_locked+0x100/0x100 [tempesta_fw] Apr 26 04:27:02 192.168.122.209 [44573.297589] ss_tcp_data_ready+0x7b/0x150 [tempesta_fw] Apr 26 04:27:02 192.168.122.209 [44573.298060] tcp_data_ready+0x73/0x210 Apr 26 04:27:02 192.168.122.209 [44573.298404] tcp_data_queue+0x1085/0x1d80 Apr 26 04:27:02 192.168.122.209 [44573.298765] ? tcp_validate_incoming+0x1fa/0xa30 Apr 26 04:27:02 192.168.122.209 [44573.299189] ? tcp_data_ready+0x210/0x210 Apr 26 04:27:02 192.168.122.209 [44573.299554] ? tcp_enter_cwr+0x1c0/0x1c0 Apr 26 04:27:02 192.168.122.209 [44573.299919] ? kvm_clock_get_cycles+0x11/0x20 Apr 26 04:27:02 192.168.122.209 [44573.300338] ? ktime_get+0x4f/0xb0 Apr 26 04:27:02 192.168.122.209 [44573.300656] tcp_rcv_established+0x422/0xb40 Apr 26 04:27:02 192.168.122.209 [44573.301057] ? tcp_parse_md5sig_option+0x20/0xb0 Apr 26 04:27:02 192.168.122.209 [44573.301491] ? tcp_data_queue+0x1d80/0x1d80 Apr 26 04:27:02 192.168.122.209 [44573.301871] ? __kasan_check_read+0x11/0x20 Apr 26 04:27:02 192.168.122.209 [44573.302246] tcp_v4_do_rcv+0x25f/0x360 Apr 26 04:27:02 192.168.122.209 [44573.302586] tcp_v4_rcv+0x1600/0x1770 Apr 26 04:27:02 192.168.122.209 [44573.302927] ? tcp_v4_early_demux+0x2f0/0x2f0 Apr 26 04:27:02 192.168.122.209 [44573.303318] ip_protocol_deliver_rcu+0x46/0x2e0 Apr 26 04:27:02 192.168.122.209 [44573.303723] ip_local_deliver_finish+0xc6/0xe0 Apr 26 04:27:02 192.168.122.209 [44573.304127] ip_local_deliver+0x1f5/0x210 Apr 26 04:27:02 192.168.122.209 [44573.304494] ? ip_local_deliver_finish+0xe0/0xe0 Apr 26 04:27:02 192.168.122.209 [44573.304912] ? nf_nat_inet_fn+0x2b3/0x440 [nf_nat] Apr 26 04:27:02 192.168.122.209 [44573.305340] ? ip_protocol_deliver_rcu+0x2e0/0x2e0 Apr 26 04:27:02 192.168.122.209 [44573.305766] ? ip_rcv_finish_core.constprop.0+0x17c/0x890 Apr 26 04:27:02 192.168.122.209 [44573.306253] ip_rcv_finish+0xcf/0xf0 Apr 26 04:27:02 192.168.122.209 [44573.306577] ip_rcv+0x16d/0x180 Apr 26 04:27:02 192.168.122.209 [44573.306865] ? ip_local_deliver+0x210/0x210 Apr 26 04:27:02 192.168.122.209 [44573.307243] ? ip_rcv_finish_core.constprop.0+0x890/0x890 Apr 26 04:27:02 192.168.122.209 [44573.307726] ? ip_local_deliver+0x210/0x210 Apr 26 04:27:02 192.168.122.209 [44573.308105] __netif_receive_skb_one_core+0x132/0x140 Apr 26 04:27:02 192.168.122.209 [44573.308555] ? napi_gro_receive+0x260/0x260 Apr 26 04:27:02 192.168.122.209 [44573.308942] ? find_next_bit+0x14/0x20 Apr 26 04:27:02 192.168.122.209 [44573.309285] ? cpumask_next+0x2c/0x40 Apr 26 04:27:02 192.168.122.209 [44573.309615] ? __kasan_check_write+0x14/0x20 Apr 26 04:27:02 192.168.122.209 [44573.310004] ? _raw_spin_lock+0x7b/0xd0 Apr 26 04:27:02 192.168.122.209 [44573.310350] __netif_receive_skb+0x26/0xb0 Apr 26 04:27:02 192.168.122.209 [44573.310722] process_backlog+0xfe/0x290 Apr 26 04:27:02 192.168.122.209 [44573.311072] net_rx_action+0x287/0x6b0 Apr 26 04:27:02 192.168.122.209 [44573.311409] ? napi_complete_done+0x2c0/0x2c0 Apr 26 04:27:02 192.168.122.209 [44573.311804] ? switch_fpu_return+0x120/0x120 Apr 26 04:27:02 192.168.122.209 [44573.312191] __do_softirq+0xfe/0x383 Apr 26 04:27:02 192.168.122.209 [44573.312520] asm_call_irq_on_stack+0xf/0x20 Apr 26 04:27:02 192.168.122.209 [44573.312899] Apr 26 04:27:02 192.168.122.209 [44573.313098] do_softirq_own_stack+0x3d/0x50 Apr 26 04:27:02 192.168.122.209 [44573.313481] irq_exit_rcu+0xc7/0x120 Apr 26 04:27:02 192.168.122.209 [44573.313816] sysvec_call_function_single+0x3a/0x90 Apr 26 04:27:02 192.168.122.209 [44573.314241] asm_sysvec_call_function_single+0x12/0x20 Apr 26 04:27:02 192.168.122.209 [44573.314698] RIP: 0010:native_safe_halt+0xe/0x10 Apr 26 04:27:02 192.168.122.209 [44573.315110] Code: 49 8b 04 24 a8 08 0f 85 71 ff ff ff e9 0f ff ff ff cc cc cc cc cc cc cc cc cc cc cc e9 07 00 00 00 0f 00 2d d4 62 51 00 fb f4 90 e9 07 00 00 00 0f 00 2d c4 62 51 00 f4 c3 cc cc 0f 1f 44 00 Apr 26 04:27:02 192.168.122.209 [44573.316724] RSP: 0018:ffff888100f37db8 EFLAGS: 00000216 Apr 26 04:27:02 192.168.122.209 [44573.317193] RAX: ffffffffb63426a0 RBX: ffff888100f2c0c0 RCX: ffffffffb632c475 Apr 26 04:27:02 192.168.122.209 [44573.317822] RDX: 000000000aa70a8e RSI: 0000000000000004 RDI: ffff888147eb5040 Apr 26 04:27:02 192.168.122.209 [44573.318451] RBP: ffff888100f37dc0 R08: 0000000000000001 R09: ffff888147eb5043 Apr 26 04:27:02 192.168.122.209 [44573.319077] R10: ffffed1028fd6a08 R11: 0000000000000001 R12: 0000000000000001 Apr 26 04:27:02 192.168.122.209 [44573.319701] R13: ffffffffb7ae9360 R14: 0000000000000000 R15: 0000000000000000 Apr 26 04:27:02 192.168.122.209 [44573.320332] ? __cpuidle_text_start+0x8/0x8 Apr 26 04:27:02 192.168.122.209 [44573.320710] ? rcu_eqs_enter.constprop.0+0x85/0xa0 Apr 26 04:27:02 192.168.122.209 [44573.321144] ? default_idle+0xe/0x20 Apr 26 04:27:02 192.168.122.209 [44573.321469] arch_cpu_idle+0x15/0x20 Apr 26 04:27:02 192.168.122.209 [44573.321793] default_idle_call+0x66/0x160 Apr 26 04:27:02 192.168.122.209 [44573.322163] do_idle+0x36f/0x430 Apr 26 04:27:02 192.168.122.209 [44573.322455] ? asm_sysvec_call_function_single+0x12/0x20 Apr 26 04:27:02 192.168.122.209 [44573.322931] ? arch_cpu_idle_exit+0x40/0x40 Apr 26 04:27:02 192.168.122.209 [44573.323308] cpu_startup_entry+0x20/0x30 Apr 26 04:27:02 192.168.122.209 [44573.323665] start_secondary+0x1c1/0x210 Apr 26 04:27:02 192.168.122.209 [44573.324021] ? set_cpu_sibling_map+0xd70/0xd70 Apr 26 04:27:02 192.168.122.209 [44573.324426] ? set_bringup_idt_handler.constprop.0+0x84/0x90 Apr 26 04:27:02 192.168.122.209 [44573.324932] ? start_cpu0+0xc/0xc Apr 26 04:27:02 192.168.122.209 [44573.325239] secondary_startup_64_no_verify+0xb0/0xbb Apr 26 04:27:02 192.168.122.209 [44573.325705] [tempesta fw] ERROR: cannot establish a new h2 connection Apr 26 04:27:03 192.168.122.209 [44573.872924] [tdb] Close table 'client0.tdb' Apr 26 04:27:03 192.168.122.209 [44574.081374] [tdb] Close table 'sessions0.tdb' Apr 26 04:27:06 192.168.122.209 [44577.191494] [tdb] Close table 'cache0.tdb' Apr 26 04:27:07 192.168.122.209 [44577.437779] [tdb] Close table 'filter0.tdb' Apr 26 04:27:07 192.168.122.209 [44577.438232] [tempesta fw] modules are stopped Apr 26 04:27:07 192.168.122.209 [44577.612363] [tempesta fw] exiting... Apr 26 04:27:07 192.168.122.209 [44577.767074] [tdb] Shutdown Tempesta DB Apr 26 04:27:07 192.168.122.209 [44577.986570] End test: t_fault_injection.test_fault_injection_base.TestFailFunction.test_tfw_hpack_init Apr 26 04:27:07 192.168.122.209 [44577.995825] Start test: t_fault_injection.test_fault_injection_base.TestFailFunction.test_with_mtu_ss_skb_expand_head_tail_long_resp Apr 26 04:27:08 192.168.122.209 [44579.267346] [tdb] Start Tempesta DB Apr 26 04:27:09 192.168.122.209 [44579.417031] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:27:10 192.168.122.209 [44580.827438] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44580.827438] Maybe that's fine, but it's worth checking the [44580.827438] config - if there is no relations between the [44580.827438] names, then host name confusion attack is possible. Apr 26 04:27:10 192.168.122.209 [44580.942173] [tempesta fw] Configuration processing is completed. Apr 26 04:27:10 192.168.122.209 [44580.996909] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:27:11 192.168.122.209 [44581.437353] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:27:11 192.168.122.209 [44581.463582] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:27:11 192.168.122.209 [44581.489653] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:27:11 192.168.122.209 [44581.554128] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:27:11 192.168.122.209 [44581.555851] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:27:11 192.168.122.209 [44581.606052] [tempesta fw] Tempesta FW is ready Apr 26 04:27:11 192.168.122.209 [44581.844793] FAULT_INJECTION: forcing a failure. [44581.844793] name fail_function, interval 0, probability 100, space 0, times 1 Apr 26 04:27:11 192.168.122.209 [44581.846207] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G OE 5.10.35.tfw-39c65d3-debug #1 Apr 26 04:27:11 192.168.122.209 [44581.847254] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 Apr 26 04:27:11 192.168.122.209 [44581.848317] Call Trace: Apr 26 04:27:11 192.168.122.209 [44581.848549] Apr 26 04:27:11 192.168.122.209 [44581.848748] dump_stack+0x96/0xc4 Apr 26 04:27:11 192.168.122.209 [44581.849057] should_fail.cold+0x5/0xa Apr 26 04:27:11 192.168.122.209 [44581.849399] fei_kprobe_handler+0x23/0x60 Apr 26 04:27:11 192.168.122.209 [44581.849792] ? ss_skb_to_sgvec_with_new_pages+0x1/0x4c0 [tempesta_fw] Apr 26 04:27:11 192.168.122.209 [44581.850368] kprobe_ftrace_handler+0xbe/0x150 Apr 26 04:27:11 192.168.122.209 [44581.850784] ? ss_skb_to_sgvec_with_new_pages+0x5/0x4c0 [tempesta_fw] Apr 26 04:27:11 192.168.122.209 [44581.851387] ? tfw_tls_encrypt+0x688/0xce0 [tempesta_fw] Apr 26 04:27:11 192.168.122.209 [44581.851861] ftrace_ops_assist_func+0xef/0x1b0 Apr 26 04:27:11 192.168.122.209 [44581.852289] ? ss_skb_dump+0x420/0x420 [tempesta_fw] Apr 26 04:27:11 192.168.122.209 [44581.852735] 0xffffffffc16e00e3 Apr 26 04:27:11 192.168.122.209 [44581.853058] RIP: 0010:ss_skb_to_sgvec_with_new_pages+0x1/0x4c0 [tempesta_fw] Apr 26 04:27:11 192.168.122.209 [44581.853675] Code: b0 83 45 c8 01 8b 5d c8 e8 6c 14 79 f3 41 0f b6 46 02 5a 59 39 d8 0f 8f 99 fe ff ff 4c 8b 75 c0 e9 19 fe ff ff 0f 1f 40 00 e8 c3 9d ff 55 48 89 e5 41 57 49 89 ff 48 83 c7 70 41 56 41 55 41 Apr 26 04:27:11 192.168.122.209 [44581.855323] RSP: 0018:ffff888147e897f0 EFLAGS: 00000282 ORIG_RAX: 0000000000000000 Apr 26 04:27:11 192.168.122.209 [44581.856011] RAX: 0000000000000001 RBX: ffff888147e898d0 RCX: ffffffffb5f956c2 Apr 26 04:27:11 192.168.122.209 [44581.856640] RDX: ffff888147e89870 RSI: ffff888147e89a70 RDI: ffff88800c508000 Apr 26 04:27:11 192.168.122.209 [44581.857266] RBP: ffff888147e89bf8 R08: ffffffffb5f9554b R09: ffff888147e89a70 Apr 26 04:27:11 192.168.122.209 [44581.857887] R10: ffffed1028fd1355 R11: 0000000000000001 R12: ffff888147e89bd0 Apr 26 04:27:11 192.168.122.209 [44581.858516] R13: 0000000000000001 R14: 0000000000000000 R15: ffff88800c508000 Apr 26 04:27:11 192.168.122.209 [44581.859153] ? __skb_to_sgvec+0x30b/0x450 Apr 26 04:27:11 192.168.122.209 [44581.859512] ? skb_to_sgvec+0x32/0x50 Apr 26 04:27:11 192.168.122.209 [44581.859871] ? ss_skb_to_sgvec_with_new_pages+0x5/0x4c0 [tempesta_fw] Apr 26 04:27:11 192.168.122.209 [44581.860469] ? tfw_tls_encrypt+0x688/0xce0 [tempesta_fw] Apr 26 04:27:11 192.168.122.209 [44581.860973] ? ss_skb_to_sgvec_with_new_pages+0x5/0x4c0 [tempesta_fw] Apr 26 04:27:11 192.168.122.209 [44581.861563] ? tfw_tls_encrypt+0x688/0xce0 [tempesta_fw] Apr 26 04:27:11 192.168.122.209 [44581.862064] ? tfw_tls_connection_recv+0x730/0x730 [tempesta_fw] Apr 26 04:27:11 192.168.122.209 [44581.862592] ? tcp_rcv_established+0x43f/0xb40 Apr 26 04:27:11 192.168.122.209 [44581.862996] ? sock_put+0x1f/0x60 Apr 26 04:27:11 192.168.122.209 [44581.863295] ? tcp_v4_rcv+0x1633/0x1770 Apr 26 04:27:11 192.168.122.209 [44581.863642] ? __alloc_pages_nodemask+0x2db/0x540 Apr 26 04:27:11 192.168.122.209 [44581.864065] ? __alloc_pages_slowpath.constprop.0+0x1390/0x1390 Apr 26 04:27:11 192.168.122.209 [44581.864592] ? __kasan_check_write+0x14/0x20 Apr 26 04:27:11 192.168.122.209 [44581.864978] ? pg_skb_alloc+0x60e/0x680 Apr 26 04:27:11 192.168.122.209 [44581.865322] ? skb_zerocopy_clone+0x63/0x280 Apr 26 04:27:11 192.168.122.209 [44581.865704] ? memcpy+0x4e/0x60 Apr 26 04:27:11 192.168.122.209 [44581.865998] ? skb_split+0x2c2/0x5f0 Apr 26 04:27:11 192.168.122.209 [44581.866322] ? tcp_fragment_tstamp+0x59/0x130 Apr 26 04:27:11 192.168.122.209 [44581.866713] tcp_tfw_sk_write_xmit+0x148/0x1d0 Apr 26 04:27:11 192.168.122.209 [44581.867145] ? tfw_tls_connection_recv+0x730/0x730 [tempesta_fw] Apr 26 04:27:11 192.168.122.209 [44581.867677] tcp_write_xmit+0x768/0x2a50 Apr 26 04:27:11 192.168.122.209 [44581.868033] ? bpf_skops_hdr_opt_len+0x210/0x210 Apr 26 04:27:11 192.168.122.209 [44581.868443] ? ip_rcv+0x16d/0x180 Apr 26 04:27:11 192.168.122.209 [44581.868744] ? ip_local_deliver+0x210/0x210 Apr 26 04:27:11 192.168.122.209 [44581.869127] __tcp_push_pending_frames+0x5f/0x1a0 Apr 26 04:27:11 192.168.122.209 [44581.869544] tcp_push+0x209/0x2b0 Apr 26 04:27:11 192.168.122.209 [44581.869871] ss_tx_action+0x946/0xc20 [tempesta_fw] Apr 26 04:27:11 192.168.122.209 [44581.870334] ? ss_skb_tcp_entail_list+0x1a0/0x1a0 [tempesta_fw] Apr 26 04:27:11 192.168.122.209 [44581.870860] ? net_rps_send_ipi+0x91/0xa0 Apr 26 04:27:11 192.168.122.209 [44581.871255] ? __kfree_skb_flush+0x27/0x60 Apr 26 04:27:11 192.168.122.209 [44581.871621] ? net_rx_action+0x438/0x6b0 Apr 26 04:27:11 192.168.122.209 [44581.871979] ? napi_complete_done+0x2c0/0x2c0 Apr 26 04:27:11 192.168.122.209 [44581.872373] net_tx_action+0xfa/0x3c0 Apr 26 04:27:11 192.168.122.209 [44581.872703] __do_softirq+0xfe/0x383 Apr 26 04:27:11 192.168.122.209 [44581.873031] asm_call_irq_on_stack+0xf/0x20 Apr 26 04:27:11 192.168.122.209 [44581.873407] Apr 26 04:27:11 192.168.122.209 [44581.873608] do_softirq_own_stack+0x3d/0x50 Apr 26 04:27:11 192.168.122.209 [44581.873989] irq_exit_rcu+0xc7/0x120 Apr 26 04:27:11 192.168.122.209 [44581.874311] sysvec_call_function_single+0x3a/0x90 Apr 26 04:27:11 192.168.122.209 [44581.874736] asm_sysvec_call_function_single+0x12/0x20 Apr 26 04:27:11 192.168.122.209 [44581.875200] RIP: 0010:native_safe_halt+0xe/0x10 Apr 26 04:27:11 192.168.122.209 [44581.875604] Code: 49 8b 04 24 a8 08 0f 85 71 ff ff ff e9 0f ff ff ff cc cc cc cc cc cc cc cc cc cc cc e9 07 00 00 00 0f 00 2d d4 62 51 00 fb f4 90 e9 07 00 00 00 0f 00 2d c4 62 51 00 f4 c3 cc cc 0f 1f 44 00 Apr 26 04:27:11 192.168.122.209 [44581.877213] RSP: 0018:ffff888100f37db8 EFLAGS: 00000206 Apr 26 04:27:11 192.168.122.209 [44581.877675] RAX: ffffffffb63426a0 RBX: ffff888100f2c0c0 RCX: ffffffffb632c475 Apr 26 04:27:11 192.168.122.209 [44581.878306] RDX: 000000000aaf5022 RSI: 0000000000000004 RDI: ffff888147eb5040 Apr 26 04:27:11 192.168.122.209 [44581.878936] RBP: ffff888100f37dc0 R08: 0000000000000001 R09: ffff888147eb5043 Apr 26 04:27:11 192.168.122.209 [44581.879563] R10: ffffed1028fd6a08 R11: 0000000000000001 R12: 0000000000000001 Apr 26 04:27:11 192.168.122.209 [44581.880190] R13: ffffffffb7ae9360 R14: 0000000000000000 R15: 0000000000000000 Apr 26 04:27:11 192.168.122.209 [44581.880819] ? __cpuidle_text_start+0x8/0x8 Apr 26 04:27:11 192.168.122.209 [44581.881196] ? rcu_eqs_enter.constprop.0+0x85/0xa0 Apr 26 04:27:11 192.168.122.209 [44581.881621] ? default_idle+0xe/0x20 Apr 26 04:27:11 192.168.122.209 [44581.881949] arch_cpu_idle+0x15/0x20 Apr 26 04:27:11 192.168.122.209 [44581.882274] default_idle_call+0x66/0x160 Apr 26 04:27:11 192.168.122.209 [44581.882634] do_idle+0x36f/0x430 Apr 26 04:27:11 192.168.122.209 [44581.882931] ? asm_sysvec_call_function_single+0x12/0x20 Apr 26 04:27:11 192.168.122.209 [44581.883401] ? arch_cpu_idle_exit+0x40/0x40 Apr 26 04:27:11 192.168.122.209 [44581.883780] cpu_startup_entry+0x20/0x30 Apr 26 04:27:11 192.168.122.209 [44581.884136] start_secondary+0x1c1/0x210 Apr 26 04:27:11 192.168.122.209 [44581.884485] ? set_cpu_sibling_map+0xd70/0xd70 Apr 26 04:27:11 192.168.122.209 [44581.884882] ? set_bringup_idt_handler.constprop.0+0x84/0x90 Apr 26 04:27:11 192.168.122.209 [44581.885388] ? start_cpu0+0xc/0xc Apr 26 04:27:11 192.168.122.209 [44581.885688] secondary_startup_64_no_verify+0xb0/0xbb Apr 26 04:27:11 192.168.122.209 [44581.886157] [tempesta fw] Warning: tfw_tls_encrypt: cannot encrypt data (-12) Apr 26 04:27:12 192.168.122.209 [44582.506201] [tdb] Close table 'client0.tdb' Apr 26 04:27:12 192.168.122.209 [44582.692893] [tdb] Close table 'sessions0.tdb' Apr 26 04:27:15 192.168.122.209 [44585.875753] [tdb] Close table 'cache0.tdb' Apr 26 04:27:15 192.168.122.209 [44586.113251] [tdb] Close table 'filter0.tdb' Apr 26 04:27:15 192.168.122.209 [44586.113704] [tempesta fw] modules are stopped Apr 26 04:27:15 192.168.122.209 [44586.289488] [tempesta fw] exiting... Apr 26 04:27:16 192.168.122.209 [44586.446117] [tdb] Shutdown Tempesta DB Apr 26 04:27:16 192.168.122.209 [44586.696745] End test: t_fault_injection.test_fault_injection_base.TestFailFunction.test_with_mtu_ss_skb_expand_head_tail_long_resp Apr 26 04:27:16 192.168.122.209 [44586.708725] Start test: t_fault_injection.test_fault_injection_base.TestFailFunction.test_with_mtu_ss_skb_to_sgvec_with_new_pages_long_resp Apr 26 04:27:17 192.168.122.209 [44587.942305] [tdb] Start Tempesta DB Apr 26 04:27:17 192.168.122.209 [44588.096042] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:27:19 192.168.122.209 [44589.515538] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44589.515538] Maybe that's fine, but it's worth checking the [44589.515538] config - if there is no relations between the [44589.515538] names, then host name confusion attack is possible. Apr 26 04:27:19 192.168.122.209 [44589.630259] [tempesta fw] Configuration processing is completed. Apr 26 04:27:19 192.168.122.209 [44589.686750] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:27:19 192.168.122.209 [44590.099271] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:27:19 192.168.122.209 [44590.161431] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:27:19 192.168.122.209 [44590.186910] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:27:19 192.168.122.209 [44590.246222] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:27:19 192.168.122.209 [44590.247949] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:27:19 192.168.122.209 [44590.290159] [tempesta fw] Tempesta FW is ready Apr 26 04:27:20 192.168.122.209 [44590.524519] FAULT_INJECTION: forcing a failure. [44590.524519] name fail_function, interval 0, probability 100, space 0, times 1 Apr 26 04:27:20 192.168.122.209 [44590.525533] CPU: 1 PID: 305762 Comm: python3.10 Tainted: G OE 5.10.35.tfw-39c65d3-debug #1 Apr 26 04:27:20 192.168.122.209 [44590.526376] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 Apr 26 04:27:20 192.168.122.209 [44590.527188] Call Trace: Apr 26 04:27:20 192.168.122.209 [44590.527415] Apr 26 04:27:20 192.168.122.209 [44590.527611] dump_stack+0x96/0xc4 Apr 26 04:27:20 192.168.122.209 [44590.527913] should_fail.cold+0x5/0xa Apr 26 04:27:20 192.168.122.209 [44590.528257] fei_kprobe_handler+0x23/0x60 Apr 26 04:27:20 192.168.122.209 [44590.528648] ? ss_skb_to_sgvec_with_new_pages+0x1/0x4c0 [tempesta_fw] Apr 26 04:27:20 192.168.122.209 [44590.529216] kprobe_ftrace_handler+0xbe/0x150 Apr 26 04:27:20 192.168.122.209 [44590.529640] ? ss_skb_to_sgvec_with_new_pages+0x5/0x4c0 [tempesta_fw] Apr 26 04:27:20 192.168.122.209 [44590.530240] ? tfw_tls_encrypt+0x688/0xce0 [tempesta_fw] Apr 26 04:27:20 192.168.122.209 [44590.530713] ftrace_ops_assist_func+0xef/0x1b0 Apr 26 04:27:20 192.168.122.209 [44590.531142] ? ss_skb_dump+0x420/0x420 [tempesta_fw] Apr 26 04:27:20 192.168.122.209 [44590.531586] 0xffffffffc16e00e3 Apr 26 04:27:20 192.168.122.209 [44590.531902] RIP: 0010:ss_skb_to_sgvec_with_new_pages+0x1/0x4c0 [tempesta_fw] Apr 26 04:27:20 192.168.122.209 [44590.532524] Code: b0 83 45 c8 01 8b 5d c8 e8 6c 14 79 f3 41 0f b6 46 02 5a 59 39 d8 0f 8f 99 fe ff ff 4c 8b 75 c0 e9 19 fe ff ff 0f 1f 40 00 e8 c3 9d ff 55 48 89 e5 41 57 49 89 ff 48 83 c7 70 41 56 41 55 41 Apr 26 04:27:20 192.168.122.209 [44590.534144] RSP: 0018:ffff888147e897f0 EFLAGS: 00000282 ORIG_RAX: 0000000000000000 Apr 26 04:27:20 192.168.122.209 [44590.534808] RAX: 0000000000000001 RBX: ffff888147e898d0 RCX: ffffffffb5f956c2 Apr 26 04:27:20 192.168.122.209 [44590.535447] RDX: ffff888147e89870 RSI: ffff888147e89a70 RDI: ffff888011620000 Apr 26 04:27:20 192.168.122.209 [44590.536075] RBP: ffff888147e89bf8 R08: ffffffffb5f9554b R09: ffff888147e89a70 Apr 26 04:27:20 192.168.122.209 [44590.536696] R10: ffffed1028fd1355 R11: 0000000000000001 R12: ffff888147e89bd0 Apr 26 04:27:20 192.168.122.209 [44590.537323] R13: 0000000000000001 R14: 0000000000000000 R15: ffff888011620000 Apr 26 04:27:20 192.168.122.209 [44590.537950] ? __skb_to_sgvec+0x30b/0x450 Apr 26 04:27:20 192.168.122.209 [44590.538311] ? skb_to_sgvec+0x32/0x50 Apr 26 04:27:20 192.168.122.209 [44590.538670] ? ss_skb_to_sgvec_with_new_pages+0x5/0x4c0 [tempesta_fw] Apr 26 04:27:20 192.168.122.209 [44590.539264] ? tfw_tls_encrypt+0x688/0xce0 [tempesta_fw] Apr 26 04:27:20 192.168.122.209 [44590.539763] ? ss_skb_to_sgvec_with_new_pages+0x5/0x4c0 [tempesta_fw] Apr 26 04:27:20 192.168.122.209 [44590.540359] ? tfw_tls_encrypt+0x688/0xce0 [tempesta_fw] Apr 26 04:27:20 192.168.122.209 [44590.540856] ? tfw_tls_connection_recv+0x730/0x730 [tempesta_fw] Apr 26 04:27:20 192.168.122.209 [44590.541391] ? __kasan_check_write+0x14/0x20 Apr 26 04:27:20 192.168.122.209 [44590.541777] ? _raw_write_lock_irqsave+0xe0/0xe0 Apr 26 04:27:20 192.168.122.209 [44590.542195] ? sock_put+0x1f/0x60 Apr 26 04:27:20 192.168.122.209 [44590.542496] ? tcp_v4_rcv+0x1633/0x1770 Apr 26 04:27:20 192.168.122.209 [44590.542843] ? __alloc_pages_nodemask+0x2db/0x540 Apr 26 04:27:20 192.168.122.209 [44590.543269] ? __alloc_pages_slowpath.constprop.0+0x1390/0x1390 Apr 26 04:27:20 192.168.122.209 [44590.543790] ? __kasan_check_write+0x14/0x20 Apr 26 04:27:20 192.168.122.209 [44590.544173] ? pg_skb_alloc+0x60e/0x680 Apr 26 04:27:20 192.168.122.209 [44590.544518] ? skb_zerocopy_clone+0x63/0x280 Apr 26 04:27:20 192.168.122.209 [44590.544902] ? memcpy+0x4e/0x60 Apr 26 04:27:20 192.168.122.209 [44590.545190] ? skb_split+0x2c2/0x5f0 Apr 26 04:27:20 192.168.122.209 [44590.545514] ? tcp_fragment_tstamp+0x59/0x130 Apr 26 04:27:20 192.168.122.209 [44590.545903] tcp_tfw_sk_write_xmit+0x148/0x1d0 Apr 26 04:27:20 192.168.122.209 [44590.546334] ? tfw_tls_connection_recv+0x730/0x730 [tempesta_fw] Apr 26 04:27:20 192.168.122.209 [44590.546860] tcp_write_xmit+0x768/0x2a50 Apr 26 04:27:20 192.168.122.209 [44590.547215] ? bpf_skops_hdr_opt_len+0x210/0x210 Apr 26 04:27:20 192.168.122.209 [44590.547626] ? ip_rcv+0x16d/0x180 Apr 26 04:27:20 192.168.122.209 [44590.547929] ? ip_local_deliver+0x210/0x210 Apr 26 04:27:20 192.168.122.209 [44590.548305] __tcp_push_pending_frames+0x5f/0x1a0 Apr 26 04:27:20 192.168.122.209 [44590.548728] tcp_push+0x209/0x2b0 Apr 26 04:27:20 192.168.122.209 [44590.549060] ss_tx_action+0x946/0xc20 [tempesta_fw] Apr 26 04:27:20 192.168.122.209 [44590.549523] ? ss_skb_tcp_entail_list+0x1a0/0x1a0 [tempesta_fw] Apr 26 04:27:20 192.168.122.209 [44590.550047] ? __kfree_skb_flush+0x27/0x60 Apr 26 04:27:20 192.168.122.209 [44590.550413] ? net_rx_action+0x438/0x6b0 Apr 26 04:27:20 192.168.122.209 [44590.550764] ? napi_complete_done+0x2c0/0x2c0 Apr 26 04:27:20 192.168.122.209 [44590.551160] net_tx_action+0xfa/0x3c0 Apr 26 04:27:20 192.168.122.209 [44590.551491] __do_softirq+0xfe/0x383 Apr 26 04:27:20 192.168.122.209 [44590.551813] asm_call_irq_on_stack+0xf/0x20 Apr 26 04:27:20 192.168.122.209 [44590.552193] Apr 26 04:27:20 192.168.122.209 [44590.552393] do_softirq_own_stack+0x3d/0x50 Apr 26 04:27:20 192.168.122.209 [44590.552766] do_softirq+0x72/0x90 Apr 26 04:27:20 192.168.122.209 [44590.553074] __local_bh_enable_ip+0x50/0x60 Apr 26 04:27:20 192.168.122.209 [44590.553446] ip_finish_output2+0x351/0xa80 Apr 26 04:27:20 192.168.122.209 [44590.553814] ? __ip_flush_pending_frames.constprop.0+0x130/0x130 Apr 26 04:27:20 192.168.122.209 [44590.554346] __ip_finish_output+0x16b/0x340 Apr 26 04:27:20 192.168.122.209 [44590.554719] ip_finish_output+0x2d/0xe0 Apr 26 04:27:20 192.168.122.209 [44590.555067] ip_output+0x133/0x210 Apr 26 04:27:20 192.168.122.209 [44590.555378] ? ip_mc_output+0x4e0/0x4e0 Apr 26 04:27:20 192.168.122.209 [44590.555724] ? stack_trace_save+0x94/0xc0 Apr 26 04:27:20 192.168.122.209 [44590.556088] ? __ip_finish_output+0x340/0x340 Apr 26 04:27:20 192.168.122.209 [44590.556478] ? ipv4_dst_check+0x6d/0xa0 Apr 26 04:27:20 192.168.122.209 [44590.556826] __ip_queue_xmit+0x356/0x7d0 Apr 26 04:27:20 192.168.122.209 [44590.557182] ip_queue_xmit+0x3b/0x50 Apr 26 04:27:20 192.168.122.209 [44590.557508] __tcp_transmit_skb+0x152f/0x1730 Apr 26 04:27:20 192.168.122.209 [44590.557896] ? __tcp_select_window+0x370/0x370 Apr 26 04:27:20 192.168.122.209 [44590.558299] ? pvclock_clocksource_read+0xe1/0x1a0 Apr 26 04:27:20 192.168.122.209 [44590.558722] ? __kasan_check_read+0x11/0x20 Apr 26 04:27:20 192.168.122.209 [44590.559100] tcp_write_xmit+0x796/0x2a50 Apr 26 04:27:20 192.168.122.209 [44590.559454] __tcp_push_pending_frames+0x5f/0x1a0 Apr 26 04:27:20 192.168.122.209 [44590.559874] tcp_push+0x209/0x2b0 Apr 26 04:27:20 192.168.122.209 [44590.560179] tcp_sendmsg_locked+0x13fa/0x15f0 Apr 26 04:27:20 192.168.122.209 [44590.560570] ? skb_do_copy_data_nocache+0x1b0/0x1b0 Apr 26 04:27:20 192.168.122.209 [44590.561003] ? __kasan_check_write+0x14/0x20 Apr 26 04:27:20 192.168.122.209 [44590.561392] ? _raw_spin_lock_bh+0x86/0xe0 Apr 26 04:27:20 192.168.122.209 [44590.561757] ? inet_recvmsg+0x105/0x270 Apr 26 04:27:20 192.168.122.209 [44590.562106] ? tcp_release_cb+0x46/0x1f0 Apr 26 04:27:20 192.168.122.209 [44590.562460] tcp_sendmsg+0x2d/0x50 Apr 26 04:27:20 192.168.122.209 [44590.562770] inet_sendmsg+0x64/0xa0 Apr 26 04:27:20 192.168.122.209 [44590.563088] ? inet_send_prepare+0x120/0x120 Apr 26 04:27:20 192.168.122.209 [44590.563472] sock_sendmsg+0x97/0xa0 Apr 26 04:27:20 192.168.122.209 [44590.563786] sock_write_iter+0x14c/0x200 Apr 26 04:27:20 192.168.122.209 [44590.564146] ? sock_sendmsg+0xa0/0xa0 Apr 26 04:27:20 192.168.122.209 [44590.564477] ? fsnotify+0x81c/0x890 Apr 26 04:27:20 192.168.122.209 [44590.564792] new_sync_write+0x3aa/0x3c0 Apr 26 04:27:20 192.168.122.209 [44590.565140] ? new_sync_read+0x3c0/0x3c0 Apr 26 04:27:20 192.168.122.209 [44590.565495] ? rw_verify_area+0x7c/0x150 Apr 26 04:27:20 192.168.122.209 [44590.565846] vfs_write+0x311/0x3d0 Apr 26 04:27:20 192.168.122.209 [44590.566158] ksys_write+0x138/0x170 Apr 26 04:27:20 192.168.122.209 [44590.566471] ? __ia32_sys_read+0x50/0x50 Apr 26 04:27:20 192.168.122.209 [44590.566826] ? __kasan_check_read+0x11/0x20 Apr 26 04:27:20 192.168.122.209 [44590.567204] ? fpregs_assert_state_consistent+0x5a/0x70 Apr 26 04:27:20 192.168.122.209 [44590.567664] __x64_sys_write+0x42/0x50 Apr 26 04:27:20 192.168.122.209 [44590.568006] do_syscall_64+0x38/0x90 Apr 26 04:27:20 192.168.122.209 [44590.568337] entry_SYSCALL_64_after_hwframe+0x44/0xa9 Apr 26 04:27:20 192.168.122.209 [44590.568782] RIP: 0033:0x7f88f225b5ad Apr 26 04:27:20 192.168.122.209 [44590.569108] Code: e5 48 83 ec 20 48 89 55 e8 48 89 75 f0 89 7d f8 e8 b8 bf f7 ff 48 8b 55 e8 48 8b 75 f0 41 89 c0 8b 7d f8 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 33 44 89 c7 48 89 45 f8 e8 0f c0 f7 ff 48 8b Apr 26 04:27:20 192.168.122.209 [44590.570720] RSP: 002b:00007f88ed97b350 EFLAGS: 00000293 ORIG_RAX: 0000000000000001 Apr 26 04:27:20 192.168.122.209 [44590.571386] RAX: ffffffffffffffda RBX: 00007f88e83eb1d0 RCX: 00007f88f225b5ad Apr 26 04:27:20 192.168.122.209 [44590.572006] RDX: 000000000000007c RSI: 00007f88e8093243 RDI: 0000000000000006 Apr 26 04:27:20 192.168.122.209 [44590.572633] RBP: 00007f88ed97b370 R08: 0000000000000000 R09: 0000000000000000 Apr 26 04:27:20 192.168.122.209 [44590.573263] R10: 00007f88e8091480 R11: 0000000000000293 R12: 000000000000007c Apr 26 04:27:20 192.168.122.209 [44590.573883] R13: 00007f88e8093243 R14: 00007f88ed97b490 R15: 00007f88ed97b440 Apr 26 04:27:20 192.168.122.209 [44590.574541] [tempesta fw] Warning: tfw_tls_encrypt: cannot encrypt data (-12) Apr 26 04:27:20 192.168.122.209 [44591.280534] [tdb] Close table 'client0.tdb' Apr 26 04:27:21 192.168.122.209 [44591.449766] [tdb] Close table 'sessions0.tdb' Apr 26 04:27:24 192.168.122.209 [44594.534753] [tdb] Close table 'cache0.tdb' Apr 26 04:27:24 192.168.122.209 [44594.788001] [tdb] Close table 'filter0.tdb' Apr 26 04:27:24 192.168.122.209 [44594.788441] [tempesta fw] modules are stopped Apr 26 04:27:24 192.168.122.209 [44594.999554] [tempesta fw] exiting... Apr 26 04:27:24 192.168.122.209 [44595.157834] [tdb] Shutdown Tempesta DB Apr 26 04:27:25 192.168.122.209 [44595.386314] End test: t_fault_injection.test_fault_injection_base.TestFailFunction.test_with_mtu_ss_skb_to_sgvec_with_new_pages_long_resp Apr 26 04:27:25 192.168.122.209 [44595.407979] Start test: t_fault_injection.test_fault_injection_base.TestFailFunctionPipelinedResponses.test_tfw_http_msg_create_sibling Apr 26 04:27:26 192.168.122.209 [44596.587177] [tdb] Start Tempesta DB Apr 26 04:27:26 192.168.122.209 [44596.738949] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:27:27 192.168.122.209 [44598.147659] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44598.147659] Maybe that's fine, but it's worth checking the [44598.147659] config - if there is no relations between the [44598.147659] names, then host name confusion attack is possible. Apr 26 04:27:27 192.168.122.209 [44598.254384] [tempesta fw] Configuration processing is completed. Apr 26 04:27:27 192.168.122.209 [44598.305976] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:27:28 192.168.122.209 [44598.728565] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:27:28 192.168.122.209 [44598.784666] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:27:28 192.168.122.209 [44598.810391] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:27:28 192.168.122.209 [44598.878321] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:27:28 192.168.122.209 [44598.880043] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:27:28 192.168.122.209 [44598.918278] [tempesta fw] Tempesta FW is ready Apr 26 04:27:28 192.168.122.209 [44599.188683] FAULT_INJECTION: forcing a failure. [44599.188683] name fail_function, interval 0, probability 100, space 0, times -1 Apr 26 04:27:28 192.168.122.209 [44599.191270] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G OE 5.10.35.tfw-39c65d3-debug #1 Apr 26 04:27:28 192.168.122.209 [44599.193212] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 Apr 26 04:27:28 192.168.122.209 [44599.195202] Call Trace: Apr 26 04:27:28 192.168.122.209 [44599.195759] Apr 26 04:27:28 192.168.122.209 [44599.196239] dump_stack+0x96/0xc4 Apr 26 04:27:28 192.168.122.209 [44599.196989] should_fail.cold+0x5/0xa Apr 26 04:27:28 192.168.122.209 [44599.197805] fei_kprobe_handler+0x23/0x60 Apr 26 04:27:28 192.168.122.209 [44599.198382] ? tfw_http_msg_create_sibling+0x1/0x100 [tempesta_fw] Apr 26 04:27:28 192.168.122.209 [44599.199029] kprobe_ftrace_handler+0xbe/0x150 Apr 26 04:27:28 192.168.122.209 [44599.199530] ? tfw_http_msg_create_sibling+0x5/0x100 [tempesta_fw] Apr 26 04:27:28 192.168.122.209 [44599.200213] ? tfw_http_msg_process_generic+0xab7/0xc70 [tempesta_fw] Apr 26 04:27:28 192.168.122.209 [44599.200888] ftrace_ops_assist_func+0xef/0x1b0 Apr 26 04:27:28 192.168.122.209 [44599.201396] ? tfw_http_conn_msg_alloc+0x3c0/0x3c0 [tempesta_fw] Apr 26 04:27:28 192.168.122.209 [44599.202037] 0xffffffffc16e00e3 Apr 26 04:27:28 192.168.122.209 [44599.202416] RIP: 0010:tfw_http_msg_create_sibling+0x1/0x100 [tempesta_fw] Apr 26 04:27:28 192.168.122.209 [44599.203133] Code: 00 00 4c 89 e7 e8 1f cd 0a 00 49 89 c6 e9 cc fe ff ff e8 32 ac 3a f4 85 c0 0f 84 43 ff ff ff e9 88 37 0d 00 0f 1f 44 00 00 e8 89 a9 ff 55 48 89 e5 41 56 41 55 41 54 49 89 fc 48 83 c7 40 53 Apr 26 04:27:28 192.168.122.209 [44599.205062] RSP: 0018:ffff888147e09328 EFLAGS: 00000246 ORIG_RAX: 0000000000000000 Apr 26 04:27:28 192.168.122.209 [44599.205857] RAX: 0000000000000000 RBX: ffff88803c124380 RCX: ffffffffc1c55ee4 Apr 26 04:27:28 192.168.122.209 [44599.206605] RDX: dffffc0000000000 RSI: ffff88803c124380 RDI: ffff8880396a0020 Apr 26 04:27:28 192.168.122.209 [44599.207357] RBP: ffff888147e09518 R08: 0000000000000000 R09: ffff8880396a00df Apr 26 04:27:28 192.168.122.209 [44599.208108] R10: ffffed10072d401b R11: 0000000000000001 R12: ffff8880396a0020 Apr 26 04:27:28 192.168.122.209 [44599.208745] R13: ffff888147e095a0 R14: ffff888147e094f0 R15: ffff888147e093d0 Apr 26 04:27:28 192.168.122.209 [44599.209398] ? tfw_http_msg_process_generic+0xaa4/0xc70 [tempesta_fw] Apr 26 04:27:28 192.168.122.209 [44599.209991] ? tfw_http_msg_create_sibling+0x5/0x100 [tempesta_fw] Apr 26 04:27:28 192.168.122.209 [44599.210566] ? tfw_http_msg_process_generic+0xab7/0xc70 [tempesta_fw] Apr 26 04:27:28 192.168.122.209 [44599.211173] ? tfw_http_msg_create_sibling+0x5/0x100 [tempesta_fw] Apr 26 04:27:28 192.168.122.209 [44599.211742] ? tfw_http_msg_process_generic+0xab7/0xc70 [tempesta_fw] Apr 26 04:27:28 192.168.122.209 [44599.212336] ? tfw_http_req_process+0x11a0/0x11a0 [tempesta_fw] Apr 26 04:27:28 192.168.122.209 [44599.212860] ? __kasan_check_write+0x14/0x20 Apr 26 04:27:28 192.168.122.209 [44599.213258] ? pg_skb_alloc+0x60e/0x680 Apr 26 04:27:28 192.168.122.209 [44599.213603] ? __kasan_check_write+0x14/0x20 Apr 26 04:27:28 192.168.122.209 [44599.213987] ? __alloc_skb+0x278/0x350 Apr 26 04:27:28 192.168.122.209 [44599.214332] ? __kasan_check_write+0x14/0x20 Apr 26 04:27:28 192.168.122.209 [44599.214745] ? __coalesce_frag+0x136/0x370 [tempesta_fw] Apr 26 04:27:28 192.168.122.209 [44599.215245] tfw_http_msg_process+0x80/0xc0 [tempesta_fw] Apr 26 04:27:28 192.168.122.209 [44599.215723] ? skb_release_data+0x8c/0x320 Apr 26 04:27:28 192.168.122.209 [44599.216113] tfw_connection_recv+0x12e/0x250 [tempesta_fw] Apr 26 04:27:28 192.168.122.209 [44599.216628] ? tfw_connection_send+0x70/0x70 [tempesta_fw] Apr 26 04:27:28 192.168.122.209 [44599.217144] ? ss_skb_unroll+0x3d6/0x540 [tempesta_fw] Apr 26 04:27:28 192.168.122.209 [44599.217628] ss_tcp_process_data+0x436/0x8b0 [tempesta_fw] Apr 26 04:27:28 192.168.122.209 [44599.218145] ? __sk_close_locked+0x100/0x100 [tempesta_fw] Apr 26 04:27:28 192.168.122.209 [44599.218659] ss_tcp_data_ready+0x7b/0x150 [tempesta_fw] Apr 26 04:27:28 192.168.122.209 [44599.219127] tcp_data_ready+0x73/0x210 Apr 26 04:27:28 192.168.122.209 [44599.219463] tcp_data_queue+0x1085/0x1d80 Apr 26 04:27:28 192.168.122.209 [44599.219821] ? tcp_validate_incoming+0x1fa/0xa30 Apr 26 04:27:28 192.168.122.209 [44599.220240] ? tcp_data_ready+0x210/0x210 Apr 26 04:27:28 192.168.122.209 [44599.220600] ? tcp_enter_cwr+0x1c0/0x1c0 Apr 26 04:27:28 192.168.122.209 [44599.220952] ? kvm_clock_get_cycles+0x11/0x20 Apr 26 04:27:28 192.168.122.209 [44599.221347] ? ktime_get+0x4f/0xb0 Apr 26 04:27:28 192.168.122.209 [44599.221659] tcp_rcv_established+0x422/0xb40 Apr 26 04:27:28 192.168.122.209 [44599.222041] ? tcp_parse_md5sig_option+0x20/0xb0 Apr 26 04:27:28 192.168.122.209 [44599.222457] ? tcp_data_queue+0x1d80/0x1d80 Apr 26 04:27:28 192.168.122.209 [44599.222834] ? __kasan_check_read+0x11/0x20 Apr 26 04:27:28 192.168.122.209 [44599.223214] tcp_v4_do_rcv+0x25f/0x360 Apr 26 04:27:28 192.168.122.209 [44599.223553] tcp_v4_rcv+0x1600/0x1770 Apr 26 04:27:28 192.168.122.209 [44599.223882] ? tcp_v4_early_demux+0x2f0/0x2f0 Apr 26 04:27:28 192.168.122.209 [44599.224279] ip_protocol_deliver_rcu+0x46/0x2e0 Apr 26 04:27:28 192.168.122.209 [44599.224688] ip_local_deliver_finish+0xc6/0xe0 Apr 26 04:27:28 192.168.122.209 [44599.225082] ip_local_deliver+0x1f5/0x210 Apr 26 04:27:28 192.168.122.209 [44599.225444] ? ip_local_deliver_finish+0xe0/0xe0 Apr 26 04:27:28 192.168.122.209 [44599.225855] ? nf_nat_inet_fn+0x2b3/0x440 [nf_nat] Apr 26 04:27:28 192.168.122.209 [44599.226289] ? ip_protocol_deliver_rcu+0x2e0/0x2e0 Apr 26 04:27:28 192.168.122.209 [44599.226713] ? ip_rcv_finish_core.constprop.0+0x17c/0x890 Apr 26 04:27:28 192.168.122.209 [44599.227193] ip_rcv_finish+0xcf/0xf0 Apr 26 04:27:28 192.168.122.209 [44599.227513] ip_rcv+0x16d/0x180 Apr 26 04:27:28 192.168.122.209 [44599.227803] ? ip_local_deliver+0x210/0x210 Apr 26 04:27:28 192.168.122.209 [44599.228184] ? ip_rcv_finish_core.constprop.0+0x890/0x890 Apr 26 04:27:28 192.168.122.209 [44599.228664] ? ip_local_deliver+0x210/0x210 Apr 26 04:27:28 192.168.122.209 [44599.229041] __netif_receive_skb_one_core+0x132/0x140 Apr 26 04:27:28 192.168.122.209 [44599.229497] ? napi_gro_receive+0x260/0x260 Apr 26 04:27:28 192.168.122.209 [44599.229872] ? find_next_bit+0x14/0x20 Apr 26 04:27:28 192.168.122.209 [44599.230214] ? cpumask_next+0x2c/0x40 Apr 26 04:27:28 192.168.122.209 [44599.230545] ? __kasan_check_write+0x14/0x20 Apr 26 04:27:28 192.168.122.209 [44599.230930] ? _raw_spin_lock+0x7b/0xd0 Apr 26 04:27:28 192.168.122.209 [44599.231281] __netif_receive_skb+0x26/0xb0 Apr 26 04:27:28 192.168.122.209 [44599.231647] process_backlog+0xfe/0x290 Apr 26 04:27:28 192.168.122.209 [44599.231993] net_rx_action+0x287/0x6b0 Apr 26 04:27:28 192.168.122.209 [44599.232343] ? napi_complete_done+0x2c0/0x2c0 Apr 26 04:27:28 192.168.122.209 [44599.232733] ? switch_fpu_return+0x120/0x120 Apr 26 04:27:28 192.168.122.209 [44599.233118] __do_softirq+0xfe/0x383 Apr 26 04:27:28 192.168.122.209 [44599.233447] asm_call_irq_on_stack+0xf/0x20 Apr 26 04:27:28 192.168.122.209 [44599.233826] Apr 26 04:27:28 192.168.122.209 [44599.234026] do_softirq_own_stack+0x3d/0x50 Apr 26 04:27:28 192.168.122.209 [44599.234407] irq_exit_rcu+0xc7/0x120 Apr 26 04:27:28 192.168.122.209 [44599.234733] sysvec_call_function_single+0x3a/0x90 Apr 26 04:27:28 192.168.122.209 [44599.235169] asm_sysvec_call_function_single+0x12/0x20 Apr 26 04:27:28 192.168.122.209 [44599.235625] RIP: 0010:native_safe_halt+0xe/0x10 Apr 26 04:27:28 192.168.122.209 [44599.236029] Code: 49 8b 04 24 a8 08 0f 85 71 ff ff ff e9 0f ff ff ff cc cc cc cc cc cc cc cc cc cc cc e9 07 00 00 00 0f 00 2d d4 62 51 00 fb f4 90 e9 07 00 00 00 0f 00 2d c4 62 51 00 f4 c3 cc cc 0f 1f 44 00 Apr 26 04:27:28 192.168.122.209 [44599.237645] RSP: 0018:ffffffffb7207dc8 EFLAGS: 00000202 Apr 26 04:27:28 192.168.122.209 [44599.238110] RAX: ffffffffb63426a0 RBX: ffffffffb721b100 RCX: ffffffffb632c475 Apr 26 04:27:28 192.168.122.209 [44599.238736] RDX: 000000000ac103ba RSI: 0000000000000004 RDI: ffff888147e35040 Apr 26 04:27:28 192.168.122.209 [44599.239366] RBP: ffffffffb7207dd0 R08: 0000000000000001 R09: ffff888147e35043 Apr 26 04:27:28 192.168.122.209 [44599.239989] R10: ffffed1028fc6a08 R11: 0000000000000001 R12: 0000000000000000 Apr 26 04:27:28 192.168.122.209 [44599.240622] R13: ffffffffb7ae9360 R14: 0000000000000000 R15: 0000000000000000 Apr 26 04:27:28 192.168.122.209 [44599.241253] ? __cpuidle_text_start+0x8/0x8 Apr 26 04:27:28 192.168.122.209 [44599.241628] ? rcu_eqs_enter.constprop.0+0x85/0xa0 Apr 26 04:27:28 192.168.122.209 [44599.242055] ? default_idle+0xe/0x20 Apr 26 04:27:28 192.168.122.209 [44599.242386] arch_cpu_idle+0x15/0x20 Apr 26 04:27:28 192.168.122.209 [44599.242710] default_idle_call+0x66/0x160 Apr 26 04:27:28 192.168.122.209 [44599.243071] do_idle+0x36f/0x430 Apr 26 04:27:28 192.168.122.209 [44599.243369] ? arch_cpu_idle_exit+0x40/0x40 Apr 26 04:27:28 192.168.122.209 [44599.243750] cpu_startup_entry+0x20/0x30 Apr 26 04:27:28 192.168.122.209 [44599.244103] rest_init+0xc8/0xce Apr 26 04:27:28 192.168.122.209 [44599.244432] arch_call_rest_init+0xe/0x1b Apr 26 04:27:28 192.168.122.209 [44599.244793] start_kernel+0x380/0x39d Apr 26 04:27:28 192.168.122.209 [44599.245135] x86_64_start_reservations+0x24/0x26 Apr 26 04:27:28 192.168.122.209 [44599.245547] x86_64_start_kernel+0x7a/0x7e Apr 26 04:27:28 192.168.122.209 [44599.245916] secondary_startup_64_no_verify+0xb0/0xbb Apr 26 04:27:28 192.168.122.209 [44599.246402] [tempesta fw] Warning: Can't create pipelined response: 127.0.0.3 Apr 26 04:27:31 192.168.122.209 [44601.845645] [tdb] Close table 'client0.tdb' Apr 26 04:27:31 192.168.122.209 [44602.049089] [tdb] Close table 'sessions0.tdb' Apr 26 04:27:34 192.168.122.209 [44605.281859] [tdb] Close table 'cache0.tdb' Apr 26 04:27:35 192.168.122.209 [44605.509023] [tdb] Close table 'filter0.tdb' Apr 26 04:27:35 192.168.122.209 [44605.509458] [tempesta fw] modules are stopped Apr 26 04:27:35 192.168.122.209 [44605.712016] [tempesta fw] exiting... Apr 26 04:27:35 192.168.122.209 [44605.850664] [tdb] Shutdown Tempesta DB Apr 26 04:27:35 192.168.122.209 [44606.100636] End test: t_fault_injection.test_fault_injection_base.TestFailFunctionPipelinedResponses.test_tfw_http_msg_create_sibling Apr 26 04:27:35 192.168.122.209 [44606.115045] Start test: t_fault_injection.test_fault_injection_base.TestFailFunctionPrepareResp.test_tfw_h2_prep_resp_for_error_response Apr 26 04:27:37 192.168.122.209 [44607.425957] [tdb] Start Tempesta DB Apr 26 04:27:37 192.168.122.209 [44607.585509] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:27:38 192.168.122.209 [44609.015863] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44609.015863] Maybe that's fine, but it's worth checking the [44609.015863] config - if there is no relations between the [44609.015863] names, then host name confusion attack is possible. Apr 26 04:27:38 192.168.122.209 [44609.150426] [tempesta fw] Configuration processing is completed. Apr 26 04:27:38 192.168.122.209 [44609.201728] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:27:39 192.168.122.209 [44609.623204] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:27:39 192.168.122.209 [44609.648885] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:27:39 192.168.122.209 [44609.674606] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:27:39 192.168.122.209 [44609.734454] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:27:39 192.168.122.209 [44609.736195] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:27:39 192.168.122.209 [44609.774396] [tempesta fw] Tempesta FW is ready Apr 26 04:27:39 192.168.122.209 [44610.025055] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrContent_TypeV input=0x21('!!!!'), len=5, off=0 Apr 26 04:27:39 192.168.122.209 [44610.026665] FAULT_INJECTION: forcing a failure. [44610.026665] name fail_function, interval 0, probability 100, space 0, times -1 Apr 26 04:27:39 192.168.122.209 [44610.028316] CPU: 3 PID: 0 Comm: swapper/3 Tainted: G OE 5.10.35.tfw-39c65d3-debug #1 Apr 26 04:27:39 192.168.122.209 [44610.029207] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 Apr 26 04:27:39 192.168.122.209 [44610.030031] Call Trace: Apr 26 04:27:39 192.168.122.209 [44610.030266] Apr 26 04:27:39 192.168.122.209 [44610.030462] dump_stack+0x96/0xc4 Apr 26 04:27:39 192.168.122.209 [44610.030764] should_fail.cold+0x5/0xa Apr 26 04:27:39 192.168.122.209 [44610.031105] fei_kprobe_handler+0x23/0x60 Apr 26 04:27:39 192.168.122.209 [44610.031504] ? tfw_h2_append_predefined_body+0x1/0x380 [tempesta_fw] Apr 26 04:27:39 192.168.122.209 [44610.032072] kprobe_ftrace_handler+0xbe/0x150 Apr 26 04:27:39 192.168.122.209 [44610.032497] ? tfw_h2_append_predefined_body+0x5/0x380 [tempesta_fw] Apr 26 04:27:39 192.168.122.209 [44610.033092] ? tfw_h2_prep_resp+0x4db/0x520 [tempesta_fw] Apr 26 04:27:39 192.168.122.209 [44610.033580] ftrace_ops_assist_func+0xef/0x1b0 Apr 26 04:27:39 192.168.122.209 [44610.034004] ? tfw_h2_msg_hdr_add.constprop.0+0x120/0x120 [tempesta_fw] Apr 26 04:27:39 192.168.122.209 [44610.034598] 0xffffffffc16e00e3 Apr 26 04:27:39 192.168.122.209 [44610.034914] RIP: 0010:tfw_h2_append_predefined_body+0x1/0x380 [tempesta_fw] Apr 26 04:27:39 192.168.122.209 [44610.035544] Code: 14 00 00 00 00 48 8b 55 f0 65 48 2b 14 25 28 00 00 00 75 06 48 8b 5d f8 c9 c3 e8 0a 8d 6e f4 66 2e 0f 1f 84 00 00 00 00 00 e8 <2b> ca a9 ff 48 85 f6 0f 84 4b 03 00 00 55 48 89 e5 41 57 41 56 49 Apr 26 04:27:39 192.168.122.209 [44610.037174] RSP: 0018:ffff888147f889f0 EFLAGS: 00000246 ORIG_RAX: 0000000000000000 Apr 26 04:27:39 192.168.122.209 [44610.037851] RAX: 0000000000000000 RBX: 0000000000000039 RCX: ffffffffc1c49864 Apr 26 04:27:39 192.168.122.209 [44610.038488] RDX: dffffc0000000000 RSI: ffff888147f88d78 RDI: ffff8880681c0020 Apr 26 04:27:39 192.168.122.209 [44610.039118] RBP: ffff888147f88b90 R08: 0000000000000000 R09: ffff8880681c00c3 Apr 26 04:27:39 192.168.122.209 [44610.039745] R10: ffffed100d038018 R11: 0000000000000001 R12: ffff888147f88d78 Apr 26 04:27:39 192.168.122.209 [44610.040376] R13: 0000000000000000 R14: 1ffff11028ff1145 R15: ffff8880681c0020 Apr 26 04:27:39 192.168.122.209 [44610.041031] ? tfw_h2_prep_resp+0x4c4/0x520 [tempesta_fw] Apr 26 04:27:39 192.168.122.209 [44610.041541] ? tfw_h2_append_predefined_body+0x5/0x380 [tempesta_fw] Apr 26 04:27:39 192.168.122.209 [44610.042124] ? tfw_h2_prep_resp+0x4db/0x520 [tempesta_fw] Apr 26 04:27:39 192.168.122.209 [44610.042632] ? tfw_h2_append_predefined_body+0x5/0x380 [tempesta_fw] Apr 26 04:27:39 192.168.122.209 [44610.043219] ? tfw_h2_prep_resp+0x4db/0x520 [tempesta_fw] Apr 26 04:27:39 192.168.122.209 [44610.043728] ? tfw_h2_resp_status_write+0x2d0/0x2d0 [tempesta_fw] Apr 26 04:27:39 192.168.122.209 [44610.044295] ? get_order+0x20/0x20 [tempesta_fw] Apr 26 04:27:39 192.168.122.209 [44610.044708] ? pvclock_clocksource_read+0xe1/0x1a0 Apr 26 04:27:39 192.168.122.209 [44610.045143] ? memset+0x3c/0x50 Apr 26 04:27:39 192.168.122.209 [44610.045463] ? __tfw_http_msg_alloc+0x219/0x3c0 [tempesta_fw] Apr 26 04:27:39 192.168.122.209 [44610.045995] tfw_h2_send_resp+0x55/0x190 [tempesta_fw] Apr 26 04:27:39 192.168.122.209 [44610.046483] tfw_h2_send_err_resp+0xf0/0x130 [tempesta_fw] Apr 26 04:27:39 192.168.122.209 [44610.046996] ? tfw_h2_send_resp+0x190/0x190 [tempesta_fw] Apr 26 04:27:39 192.168.122.209 [44610.047485] ? printk+0xb2/0xe3 Apr 26 04:27:39 192.168.122.209 [44610.047804] tfw_http_cli_error_resp_and_log+0x1a7/0x7f0 [tempesta_fw] Apr 26 04:27:39 192.168.122.209 [44610.048410] ? tfw_h1_send_err_resp+0x120/0x120 [tempesta_fw] Apr 26 04:27:39 192.168.122.209 [44610.048949] ? h2_set_hdr_x_method_override+0x50/0x50 [tempesta_fw] Apr 26 04:27:39 192.168.122.209 [44610.049539] ? tfw_sock_srv_exit+0x30/0x30 [tempesta_fw] Apr 26 04:27:39 192.168.122.209 [44610.050008] ? __kasan_check_write+0x14/0x20 Apr 26 04:27:39 192.168.122.209 [44610.050398] ? _raw_spin_lock_irqsave+0x8e/0xf0 Apr 26 04:27:39 192.168.122.209 [44610.050833] tfw_http_req_process+0x43d/0x11a0 [tempesta_fw] Apr 26 04:27:39 192.168.122.209 [44610.051339] ? eb_delete+0x27/0x210 [tempesta_lib] Apr 26 04:27:39 192.168.122.209 [44610.051792] ? tfw_http_extract_request_authority+0x110/0x110 [tempesta_fw] Apr 26 04:27:39 192.168.122.209 [44610.052410] ? __kasan_check_write+0x14/0x20 Apr 26 04:27:39 192.168.122.209 [44610.052795] ? _raw_spin_lock+0x7b/0xd0 Apr 26 04:27:39 192.168.122.209 [44610.053145] ? _raw_write_lock_irqsave+0xe0/0xe0 Apr 26 04:27:39 192.168.122.209 [44610.053590] ? tfw_h2_add_stream_dep+0x2f3/0x310 [tempesta_fw] Apr 26 04:27:39 192.168.122.209 [44610.054107] ? memset+0x3c/0x50 Apr 26 04:27:39 192.168.122.209 [44610.054401] ? bzero_fast+0xe/0x10 [tempesta_lib] Apr 26 04:27:39 192.168.122.209 [44610.054849] ? tfw_pool_alloc_pages+0x70/0xc0 [tempesta_fw] Apr 26 04:27:39 192.168.122.209 [44610.055347] ? __kasan_check_write+0x14/0x20 Apr 26 04:27:39 192.168.122.209 [44610.055756] ? tfw_http_conn_msg_alloc+0x37a/0x3c0 [tempesta_fw] Apr 26 04:27:39 192.168.122.209 [44610.056320] tfw_http_msg_process_generic+0x385/0xc70 [tempesta_fw] Apr 26 04:27:39 192.168.122.209 [44610.056901] ? __split_pgfrag_del_w_frag+0x356/0xbc0 [tempesta_fw] Apr 26 04:27:39 192.168.122.209 [44610.057476] ? tfw_http_req_process+0x11a0/0x11a0 [tempesta_fw] Apr 26 04:27:39 192.168.122.209 [44610.058026] ? ss_skb_chop_head_tail+0x1bb/0x380 [tempesta_fw] Apr 26 04:27:39 192.168.122.209 [44610.058579] ? ss_skb_get_room_w_frag+0xf0/0xf0 [tempesta_fw] Apr 26 04:27:39 192.168.122.209 [44610.059115] ? tfw_h2_send_rst_stream+0x150/0x150 [tempesta_fw] Apr 26 04:27:39 192.168.122.209 [44610.059667] tfw_h2_frame_process+0x9c6/0xf20 [tempesta_fw] Apr 26 04:27:39 192.168.122.209 [44610.060188] ? tfw_h2_frame_recv+0x3c30/0x3c30 [tempesta_fw] Apr 26 04:27:39 192.168.122.209 [44610.060721] ? ss_skb_chop_head_tail+0x2a8/0x380 [tempesta_fw] Apr 26 04:27:39 192.168.122.209 [44610.061270] tfw_http_msg_process+0x9d/0xc0 [tempesta_fw] Apr 26 04:27:39 192.168.122.209 [44610.061773] tfw_connection_recv+0x12e/0x250 [tempesta_fw] Apr 26 04:27:39 192.168.122.209 [44610.062288] ? tfw_connection_send+0x70/0x70 [tempesta_fw] Apr 26 04:27:39 192.168.122.209 [44610.062809] ? ss_skb_list_chop_head_tail+0x6e/0x1d0 [tempesta_fw] Apr 26 04:27:39 192.168.122.209 [44610.063385] tfw_tls_connection_recv+0x4f6/0x730 [tempesta_fw] Apr 26 04:27:39 192.168.122.209 [44610.063898] ? __kasan_check_write+0x14/0x20 Apr 26 04:27:39 192.168.122.209 [44610.064315] ? tfw_tls_connection_lost+0x40/0x40 [tempesta_fw] Apr 26 04:27:39 192.168.122.209 [44610.064859] ? ss_skb_unroll+0x3d6/0x540 [tempesta_fw] Apr 26 04:27:39 192.168.122.209 [44610.065348] ss_tcp_process_data+0x436/0x8b0 [tempesta_fw] Apr 26 04:27:39 192.168.122.209 [44610.065864] ? __sk_close_locked+0x100/0x100 [tempesta_fw] Apr 26 04:27:39 192.168.122.209 [44610.066385] ss_tcp_data_ready+0x7b/0x150 [tempesta_fw] Apr 26 04:27:39 192.168.122.209 [44610.066856] tcp_data_ready+0x73/0x210 Apr 26 04:27:39 192.168.122.209 [44610.067196] tcp_data_queue+0x1085/0x1d80 Apr 26 04:27:39 192.168.122.209 [44610.067562] ? tcp_data_ready+0x210/0x210 Apr 26 04:27:39 192.168.122.209 [44610.067933] ? tcp_enter_cwr+0x1c0/0x1c0 Apr 26 04:27:39 192.168.122.209 [44610.068295] ? kvm_clock_get_cycles+0x11/0x20 Apr 26 04:27:39 192.168.122.209 [44610.068688] ? ktime_get+0x4f/0xb0 Apr 26 04:27:39 192.168.122.209 [44610.068997] tcp_rcv_established+0x422/0xb40 Apr 26 04:27:39 192.168.122.209 [44610.069388] ? tcp_parse_md5sig_option+0x20/0xb0 Apr 26 04:27:39 192.168.122.209 [44610.069806] ? tcp_data_queue+0x1d80/0x1d80 Apr 26 04:27:39 192.168.122.209 [44610.070184] ? __kasan_check_read+0x11/0x20 Apr 26 04:27:39 192.168.122.209 [44610.070565] tcp_v4_do_rcv+0x25f/0x360 Apr 26 04:27:39 192.168.122.209 [44610.070906] tcp_v4_rcv+0x1600/0x1770 Apr 26 04:27:39 192.168.122.209 [44610.071243] ? tcp_v4_early_demux+0x2f0/0x2f0 Apr 26 04:27:39 192.168.122.209 [44610.071648] ip_protocol_deliver_rcu+0x46/0x2e0 Apr 26 04:27:39 192.168.122.209 [44610.072051] ip_local_deliver_finish+0xc6/0xe0 Apr 26 04:27:39 192.168.122.209 [44610.072452] ip_local_deliver+0x1f5/0x210 Apr 26 04:27:39 192.168.122.209 [44610.072817] ? ip_local_deliver_finish+0xe0/0xe0 Apr 26 04:27:39 192.168.122.209 [44610.073234] ? nf_nat_inet_fn+0x2b3/0x440 [nf_nat] Apr 26 04:27:39 192.168.122.209 [44610.073665] ? ip_protocol_deliver_rcu+0x2e0/0x2e0 Apr 26 04:27:39 192.168.122.209 [44610.074093] ? ip_rcv_finish_core.constprop.0+0x17c/0x890 Apr 26 04:27:39 192.168.122.209 [44610.074582] ip_rcv_finish+0xcf/0xf0 Apr 26 04:27:39 192.168.122.209 [44610.074909] ip_rcv+0x16d/0x180 Apr 26 04:27:39 192.168.122.209 [44610.075196] ? ip_local_deliver+0x210/0x210 Apr 26 04:27:39 192.168.122.209 [44610.075577] ? ip_rcv_finish_core.constprop.0+0x890/0x890 Apr 26 04:27:39 192.168.122.209 [44610.076059] ? update_load_avg+0x59d/0xa70 Apr 26 04:27:39 192.168.122.209 [44610.076434] ? sched_clock+0x9/0x10 Apr 26 04:27:39 192.168.122.209 [44610.076751] ? sched_clock_cpu+0x1b/0x110 Apr 26 04:27:39 192.168.122.209 [44610.077112] ? ip_local_deliver+0x210/0x210 Apr 26 04:27:39 192.168.122.209 [44610.077495] __netif_receive_skb_one_core+0x132/0x140 Apr 26 04:27:39 192.168.122.209 [44610.077947] ? napi_gro_receive+0x260/0x260 Apr 26 04:27:39 192.168.122.209 [44610.078325] ? __kasan_check_write+0x14/0x20 Apr 26 04:27:39 192.168.122.209 [44610.078713] ? _raw_spin_lock+0x7b/0xd0 Apr 26 04:27:39 192.168.122.209 [44610.079063] __netif_receive_skb+0x26/0xb0 Apr 26 04:27:39 192.168.122.209 [44610.079441] ? generic_exec_single+0xb1/0x170 Apr 26 04:27:39 192.168.122.209 [44610.079829] process_backlog+0xfe/0x290 Apr 26 04:27:39 192.168.122.209 [44610.080178] net_rx_action+0x287/0x6b0 Apr 26 04:27:39 192.168.122.209 [44610.080523] ? try_to_wake_up+0x41e/0xa70 Apr 26 04:27:39 192.168.122.209 [44610.080886] ? napi_complete_done+0x2c0/0x2c0 Apr 26 04:27:39 192.168.122.209 [44610.081277] ? switch_fpu_return+0x120/0x120 Apr 26 04:27:39 192.168.122.209 [44610.081663] __do_softirq+0xfe/0x383 Apr 26 04:27:39 192.168.122.209 [44610.081990] asm_call_irq_on_stack+0xf/0x20 Apr 26 04:27:39 192.168.122.209 [44610.082369] Apr 26 04:27:39 192.168.122.209 [44610.082569] do_softirq_own_stack+0x3d/0x50 Apr 26 04:27:39 192.168.122.209 [44610.082946] irq_exit_rcu+0xc7/0x120 Apr 26 04:27:39 192.168.122.209 [44610.083276] sysvec_call_function_single+0x3a/0x90 Apr 26 04:27:39 192.168.122.209 [44610.083705] asm_sysvec_call_function_single+0x12/0x20 Apr 26 04:27:39 192.168.122.209 [44610.084158] RIP: 0010:native_safe_halt+0xe/0x10 Apr 26 04:27:39 192.168.122.209 [44610.084572] Code: 49 8b 04 24 a8 08 0f 85 71 ff ff ff e9 0f ff ff ff cc cc cc cc cc cc cc cc cc cc cc e9 07 00 00 00 0f 00 2d d4 62 51 00 fb f4 90 e9 07 00 00 00 0f 00 2d c4 62 51 00 f4 c3 cc cc 0f 1f 44 00 Apr 26 04:27:39 192.168.122.209 [44610.086192] RSP: 0018:ffff888100f47db8 EFLAGS: 00000202 Apr 26 04:27:39 192.168.122.209 [44610.086680] RAX: ffffffffb63426a0 RBX: ffff888100f28040 RCX: ffffffffb632c475 Apr 26 04:27:39 192.168.122.209 [44610.087309] RDX: 000000000b3274c2 RSI: 0000000000000004 RDI: ffff888147fb5040 Apr 26 04:27:39 192.168.122.209 [44610.087932] RBP: ffff888100f47dc0 R08: 0000000000000001 R09: ffff888147fb5043 Apr 26 04:27:39 192.168.122.209 [44610.088564] R10: ffffed1028ff6a08 R11: 0000000000000001 R12: 0000000000000003 Apr 26 04:27:39 192.168.122.209 [44610.089196] R13: ffffffffb7ae9360 R14: 0000000000000000 R15: 0000000000000000 Apr 26 04:27:39 192.168.122.209 [44610.089825] ? __cpuidle_text_start+0x8/0x8 Apr 26 04:27:39 192.168.122.209 [44610.090200] ? rcu_eqs_enter.constprop.0+0x85/0xa0 Apr 26 04:27:39 192.168.122.209 [44610.090661] ? default_idle+0xe/0x20 Apr 26 04:27:39 192.168.122.209 [44610.090989] arch_cpu_idle+0x15/0x20 Apr 26 04:27:39 192.168.122.209 [44610.091317] default_idle_call+0x66/0x160 Apr 26 04:27:39 192.168.122.209 [44610.091680] do_idle+0x36f/0x430 Apr 26 04:27:39 192.168.122.209 [44610.091977] ? asm_common_interrupt+0x1e/0x40 Apr 26 04:27:39 192.168.122.209 [44610.092373] ? arch_cpu_idle_exit+0x40/0x40 Apr 26 04:27:39 192.168.122.209 [44610.092751] cpu_startup_entry+0x20/0x30 Apr 26 04:27:39 192.168.122.209 [44610.093107] start_secondary+0x1c1/0x210 Apr 26 04:27:39 192.168.122.209 [44610.093468] ? set_cpu_sibling_map+0xd70/0xd70 Apr 26 04:27:39 192.168.122.209 [44610.093869] ? set_bringup_idt_handler.constprop.0+0x84/0x90 Apr 26 04:27:39 192.168.122.209 [44610.094387] ? start_cpu0+0xc/0xc Apr 26 04:27:39 192.168.122.209 [44610.094691] secondary_startup_64_no_verify+0xb0/0xbb Apr 26 04:27:40 192.168.122.209 [44610.675920] [tdb] Close table 'client0.tdb' Apr 26 04:27:40 192.168.122.209 [44610.866335] [tdb] Close table 'sessions0.tdb' Apr 26 04:27:43 192.168.122.209 [44613.999837] [tdb] Close table 'cache0.tdb' Apr 26 04:27:43 192.168.122.209 [44614.231166] [tdb] Close table 'filter0.tdb' Apr 26 04:27:43 192.168.122.209 [44614.231623] [tempesta fw] modules are stopped Apr 26 04:27:44 192.168.122.209 [44614.416242] [tempesta fw] exiting... Apr 26 04:27:44 192.168.122.209 [44614.550188] [tdb] Shutdown Tempesta DB Apr 26 04:27:44 192.168.122.209 [44614.754185] End test: t_fault_injection.test_fault_injection_base.TestFailFunctionPrepareResp.test_tfw_h2_prep_resp_for_error_response Apr 26 04:27:44 192.168.122.209 [44614.778037] Start test: t_fault_injection.test_fault_injection_base.TestFailFunctionPrepareResp.test_tfw_h2_prep_resp_for_sticky_ccokie Apr 26 04:27:45 192.168.122.209 [44616.020848] [tdb] Start Tempesta DB Apr 26 04:27:45 192.168.122.209 [44616.151879] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:27:47 192.168.122.209 [44617.867814] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44617.867814] Maybe that's fine, but it's worth checking the [44617.867814] config - if there is no relations between the [44617.867814] names, then host name confusion attack is possible. Apr 26 04:27:47 192.168.122.209 [44617.960968] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:27:47 192.168.122.209 [44618.006605] [tempesta fw] Configuration processing is completed. Apr 26 04:27:47 192.168.122.209 [44618.057906] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:27:48 192.168.122.209 [44618.478888] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:27:48 192.168.122.209 [44618.504923] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:27:48 192.168.122.209 [44618.531807] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:27:48 192.168.122.209 [44618.602570] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:27:48 192.168.122.209 [44618.604294] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:27:48 192.168.122.209 [44618.642517] [tempesta fw] Tempesta FW is ready Apr 26 04:27:48 192.168.122.209 [44618.857467] FAULT_INJECTION: forcing a failure. [44618.857467] name fail_function, interval 0, probability 100, space 0, times 1 Apr 26 04:27:48 192.168.122.209 [44618.858934] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G OE 5.10.35.tfw-39c65d3-debug #1 Apr 26 04:27:48 192.168.122.209 [44618.859995] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 Apr 26 04:27:48 192.168.122.209 [44618.860985] Call Trace: Apr 26 04:27:48 192.168.122.209 [44618.861266] Apr 26 04:27:48 192.168.122.209 [44618.861514] dump_stack+0x96/0xc4 Apr 26 04:27:48 192.168.122.209 [44618.861885] should_fail.cold+0x5/0xa Apr 26 04:27:48 192.168.122.209 [44618.862293] fei_kprobe_handler+0x23/0x60 Apr 26 04:27:48 192.168.122.209 [44618.862791] ? tfw_h2_append_predefined_body+0x1/0x380 [tempesta_fw] Apr 26 04:27:48 192.168.122.209 [44618.863468] kprobe_ftrace_handler+0xbe/0x150 Apr 26 04:27:48 192.168.122.209 [44618.863987] ? tfw_h2_append_predefined_body+0x5/0x380 [tempesta_fw] Apr 26 04:27:48 192.168.122.209 [44618.864705] ? tfw_h2_prep_resp+0x4db/0x520 [tempesta_fw] Apr 26 04:27:48 192.168.122.209 [44618.865280] ftrace_ops_assist_func+0xef/0x1b0 Apr 26 04:27:48 192.168.122.209 [44618.865810] ? tfw_h2_msg_hdr_add.constprop.0+0x120/0x120 [tempesta_fw] Apr 26 04:27:48 192.168.122.209 [44618.866529] 0xffffffffc16e00e3 Apr 26 04:27:48 192.168.122.209 [44618.866921] RIP: 0010:tfw_h2_append_predefined_body+0x1/0x380 [tempesta_fw] Apr 26 04:27:48 192.168.122.209 [44618.867661] Code: 14 00 00 00 00 48 8b 55 f0 65 48 2b 14 25 28 00 00 00 75 06 48 8b 5d f8 c9 c3 e8 0a 8d 6e f4 66 2e 0f 1f 84 00 00 00 00 00 e8 <2b> ca a9 ff 48 85 f6 0f 84 4b 03 00 00 55 48 89 e5 41 57 41 56 49 Apr 26 04:27:48 192.168.122.209 [44618.869601] RSP: 0018:ffff888147e88558 EFLAGS: 00000246 ORIG_RAX: 0000000000000000 Apr 26 04:27:48 192.168.122.209 [44618.870416] RAX: 0000000000000000 RBX: 00000000000000b2 RCX: ffffffffc1c49864 Apr 26 04:27:48 192.168.122.209 [44618.871084] RDX: dffffc0000000000 RSI: ffff888147e88a80 RDI: ffff8880582d7020 Apr 26 04:27:48 192.168.122.209 [44618.871717] RBP: ffff888147e886f8 R08: 0000000000000000 R09: ffff8880582d70c3 Apr 26 04:27:48 192.168.122.209 [44618.872348] R10: ffffed100b05ae18 R11: 0000000000000001 R12: ffff888147e88a80 Apr 26 04:27:48 192.168.122.209 [44618.872988] R13: 0000000000000665 R14: 1ffff11028fd10b2 R15: ffff8880582d7020 Apr 26 04:27:48 192.168.122.209 [44618.873661] ? tfw_h2_prep_resp+0x4c4/0x520 [tempesta_fw] Apr 26 04:27:48 192.168.122.209 [44618.874176] ? tfw_h2_append_predefined_body+0x5/0x380 [tempesta_fw] Apr 26 04:27:48 192.168.122.209 [44618.874784] ? tfw_h2_prep_resp+0x4db/0x520 [tempesta_fw] Apr 26 04:27:48 192.168.122.209 [44618.875304] ? tfw_h2_append_predefined_body+0x5/0x380 [tempesta_fw] Apr 26 04:27:48 192.168.122.209 [44618.875905] ? tfw_h2_prep_resp+0x4db/0x520 [tempesta_fw] Apr 26 04:27:48 192.168.122.209 [44618.876426] ? tfw_h2_resp_status_write+0x2d0/0x2d0 [tempesta_fw] Apr 26 04:27:48 192.168.122.209 [44618.877001] ? tfw_http_prep_date_from+0x3e7/0x470 [tempesta_fw] Apr 26 04:27:48 192.168.122.209 [44618.877577] ? get_order+0x20/0x20 [tempesta_fw] Apr 26 04:27:48 192.168.122.209 [44618.878027] ? tfw_str_to_cstr+0xd5/0x110 [tempesta_fw] Apr 26 04:27:48 192.168.122.209 [44618.878545] tfw_http_prep_redir+0x592/0x730 [tempesta_fw] Apr 26 04:27:48 192.168.122.209 [44618.879068] ? tfw_h2_prep_resp+0x520/0x520 [tempesta_fw] Apr 26 04:27:48 192.168.122.209 [44618.879562] ? memcpy+0x4e/0x60 Apr 26 04:27:48 192.168.122.209 [44618.879863] ? memset+0x3c/0x50 Apr 26 04:27:48 192.168.122.209 [44618.880158] ? bin2hex+0x92/0xd0 Apr 26 04:27:48 192.168.122.209 [44618.880505] tfw_http_sticky_build_redirect.constprop.0+0x38a/0x440 [tempesta_fw] Apr 26 04:27:48 192.168.122.209 [44618.881203] ? tfw_http_sticky_verify+0x690/0x690 [tempesta_fw] Apr 26 04:27:48 192.168.122.209 [44618.881739] ? bzero_fast+0xe/0x10 [tempesta_lib] Apr 26 04:27:48 192.168.122.209 [44618.882203] ? __str_grow_tree+0xd8/0x210 [tempesta_fw] Apr 26 04:27:48 192.168.122.209 [44618.882719] ? frang_http_hdr_limit+0x4c0/0x4c0 [tempesta_fw] Apr 26 04:27:48 192.168.122.209 [44618.883235] ? __kasan_check_read+0x11/0x20 Apr 26 04:27:48 192.168.122.209 [44618.883654] ? frang_http_req_trailer_check+0xd3/0x3f0 [tempesta_fw] Apr 26 04:27:48 192.168.122.209 [44618.884254] tfw_http_sess_obtain+0x76f/0x870 [tempesta_fw] Apr 26 04:27:48 192.168.122.209 [44618.884793] ? tfw_http_sess_release_entry+0x20/0x20 [tempesta_fw] Apr 26 04:27:48 192.168.122.209 [44618.885346] ? __kasan_check_write+0x14/0x20 Apr 26 04:27:48 192.168.122.209 [44618.885775] ? frang_http_req_handler+0x30e/0x940 [tempesta_fw] Apr 26 04:27:48 192.168.122.209 [44618.886334] ? tfw_http_req_client_link.isra.0+0x108/0x1b0 [tempesta_fw] Apr 26 04:27:48 192.168.122.209 [44618.886977] tfw_http_req_process+0x700/0x11a0 [tempesta_fw] Apr 26 04:27:48 192.168.122.209 [44618.887525] ? tfw_http_extract_request_authority+0x110/0x110 [tempesta_fw] Apr 26 04:27:48 192.168.122.209 [44618.888143] ? alloc_pages_current+0x96/0x140 Apr 26 04:27:48 192.168.122.209 [44618.888582] ? tfw_pool_alloc_pages+0x9b/0xc0 [tempesta_fw] Apr 26 04:27:48 192.168.122.209 [44618.889080] ? __kasan_check_write+0x14/0x20 Apr 26 04:27:48 192.168.122.209 [44618.889513] ? tfw_http_conn_msg_alloc+0x37a/0x3c0 [tempesta_fw] Apr 26 04:27:48 192.168.122.209 [44618.890078] tfw_http_msg_process_generic+0x385/0xc70 [tempesta_fw] Apr 26 04:27:48 192.168.122.209 [44618.890682] ? __split_pgfrag_del_w_frag+0x356/0xbc0 [tempesta_fw] Apr 26 04:27:48 192.168.122.209 [44618.891268] ? tfw_http_req_process+0x11a0/0x11a0 [tempesta_fw] Apr 26 04:27:48 192.168.122.209 [44618.891836] ? ss_skb_chop_head_tail+0x1bb/0x380 [tempesta_fw] Apr 26 04:27:48 192.168.122.209 [44618.892395] ? ss_skb_get_room_w_frag+0xf0/0xf0 [tempesta_fw] Apr 26 04:27:48 192.168.122.209 [44618.892942] ? tfw_h2_send_rst_stream+0x150/0x150 [tempesta_fw] Apr 26 04:27:48 192.168.122.209 [44618.893474] ? __kasan_check_write+0x14/0x20 Apr 26 04:27:48 192.168.122.209 [44618.893870] ? kfree_skbmem+0xeb/0x220 Apr 26 04:27:48 192.168.122.209 [44618.894254] tfw_h2_frame_process+0x9c6/0xf20 [tempesta_fw] Apr 26 04:27:48 192.168.122.209 [44618.894802] ? tfw_h2_frame_recv+0x3c30/0x3c30 [tempesta_fw] Apr 26 04:27:48 192.168.122.209 [44618.895342] ? ss_skb_chop_head_tail+0x2a8/0x380 [tempesta_fw] Apr 26 04:27:48 192.168.122.209 [44618.895903] tfw_http_msg_process+0x9d/0xc0 [tempesta_fw] Apr 26 04:27:48 192.168.122.209 [44618.896421] tfw_connection_recv+0x12e/0x250 [tempesta_fw] Apr 26 04:27:48 192.168.122.209 [44618.896941] ? tfw_connection_send+0x70/0x70 [tempesta_fw] Apr 26 04:27:48 192.168.122.209 [44618.897474] ? ss_skb_list_chop_head_tail+0x6e/0x1d0 [tempesta_fw] Apr 26 04:27:48 192.168.122.209 [44618.898062] tfw_tls_connection_recv+0x4f6/0x730 [tempesta_fw] Apr 26 04:27:48 192.168.122.209 [44618.898592] ? __kasan_check_write+0x14/0x20 Apr 26 04:27:48 192.168.122.209 [44618.899015] ? tfw_tls_connection_lost+0x40/0x40 [tempesta_fw] Apr 26 04:27:48 192.168.122.209 [44618.899576] ? ss_skb_unroll+0x3d6/0x540 [tempesta_fw] Apr 26 04:27:48 192.168.122.209 [44618.900076] ss_tcp_process_data+0x436/0x8b0 [tempesta_fw] Apr 26 04:27:48 192.168.122.209 [44618.900606] ? __sk_close_locked+0x100/0x100 [tempesta_fw] Apr 26 04:27:48 192.168.122.209 [44618.901097] ? tcp_grow_window+0xce/0x330 Apr 26 04:27:48 192.168.122.209 [44618.901506] ss_tcp_data_ready+0x7b/0x150 [tempesta_fw] Apr 26 04:27:48 192.168.122.209 [44618.901978] tcp_data_ready+0x73/0x210 Apr 26 04:27:48 192.168.122.209 [44618.902323] tcp_data_queue+0x1085/0x1d80 Apr 26 04:27:48 192.168.122.209 [44618.902706] ? tcp_validate_incoming+0x1fa/0xa30 Apr 26 04:27:48 192.168.122.209 [44618.903127] ? tcp_data_ready+0x210/0x210 Apr 26 04:27:48 192.168.122.209 [44618.903504] ? tcp_enter_cwr+0x1c0/0x1c0 Apr 26 04:27:48 192.168.122.209 [44618.903868] ? kvm_clock_get_cycles+0x11/0x20 Apr 26 04:27:48 192.168.122.209 [44618.904264] ? ktime_get+0x4f/0xb0 Apr 26 04:27:48 192.168.122.209 [44618.904586] tcp_rcv_established+0x422/0xb40 Apr 26 04:27:48 192.168.122.209 [44618.904981] ? tcp_parse_md5sig_option+0x20/0xb0 Apr 26 04:27:48 192.168.122.209 [44618.905404] ? tcp_data_queue+0x1d80/0x1d80 Apr 26 04:27:48 192.168.122.209 [44618.905788] ? __kasan_check_read+0x11/0x20 Apr 26 04:27:48 192.168.122.209 [44618.906168] tcp_v4_do_rcv+0x25f/0x360 Apr 26 04:27:48 192.168.122.209 [44618.906531] tcp_v4_rcv+0x1600/0x1770 Apr 26 04:27:48 192.168.122.209 [44618.906877] ? tcp_v4_early_demux+0x2f0/0x2f0 Apr 26 04:27:48 192.168.122.209 [44618.907277] ip_protocol_deliver_rcu+0x46/0x2e0 Apr 26 04:27:48 192.168.122.209 [44618.907694] ip_local_deliver_finish+0xc6/0xe0 Apr 26 04:27:48 192.168.122.209 [44618.908103] ip_local_deliver+0x1f5/0x210 Apr 26 04:27:48 192.168.122.209 [44618.908476] ? ip_local_deliver_finish+0xe0/0xe0 Apr 26 04:27:48 192.168.122.209 [44618.908899] ? nf_nat_inet_fn+0x2b3/0x440 [nf_nat] Apr 26 04:27:48 192.168.122.209 [44618.909332] ? ip_protocol_deliver_rcu+0x2e0/0x2e0 Apr 26 04:27:48 192.168.122.209 [44618.909772] ? ip_rcv_finish_core.constprop.0+0x17c/0x890 Apr 26 04:27:48 192.168.122.209 [44618.910254] ip_rcv_finish+0xcf/0xf0 Apr 26 04:27:48 192.168.122.209 [44618.910599] ip_rcv+0x16d/0x180 Apr 26 04:27:48 192.168.122.209 [44618.910895] ? ip_local_deliver+0x210/0x210 Apr 26 04:27:48 192.168.122.209 [44618.911284] ? ip_rcv_finish_core.constprop.0+0x890/0x890 Apr 26 04:27:48 192.168.122.209 [44618.911777] ? ip_local_deliver+0x210/0x210 Apr 26 04:27:48 192.168.122.209 [44618.912158] __netif_receive_skb_one_core+0x132/0x140 Apr 26 04:27:48 192.168.122.209 [44618.912620] ? napi_gro_receive+0x260/0x260 Apr 26 04:27:48 192.168.122.209 [44618.913008] ? find_next_bit+0x14/0x20 Apr 26 04:27:48 192.168.122.209 [44618.913353] ? cpumask_next+0x2c/0x40 Apr 26 04:27:48 192.168.122.209 [44618.913695] ? __kasan_check_write+0x14/0x20 Apr 26 04:27:48 192.168.122.209 [44618.914087] ? _raw_spin_lock+0x7b/0xd0 Apr 26 04:27:48 192.168.122.209 [44618.914454] __netif_receive_skb+0x26/0xb0 Apr 26 04:27:48 192.168.122.209 [44618.914835] ? generic_exec_single+0xb1/0x170 Apr 26 04:27:48 192.168.122.209 [44618.915231] process_backlog+0xfe/0x290 Apr 26 04:27:48 192.168.122.209 [44618.915591] net_rx_action+0x287/0x6b0 Apr 26 04:27:48 192.168.122.209 [44618.915940] ? napi_complete_done+0x2c0/0x2c0 Apr 26 04:27:48 192.168.122.209 [44618.916344] ? switch_fpu_return+0x120/0x120 Apr 26 04:27:48 192.168.122.209 [44618.916740] __do_softirq+0xfe/0x383 Apr 26 04:27:48 192.168.122.209 [44618.917070] asm_call_irq_on_stack+0xf/0x20 Apr 26 04:27:48 192.168.122.209 [44618.917460] Apr 26 04:27:48 192.168.122.209 [44618.917668] do_softirq_own_stack+0x3d/0x50 Apr 26 04:27:48 192.168.122.209 [44618.918053] irq_exit_rcu+0xc7/0x120 Apr 26 04:27:48 192.168.122.209 [44618.918395] sysvec_call_function_single+0x3a/0x90 Apr 26 04:27:48 192.168.122.209 [44618.918838] asm_sysvec_call_function_single+0x12/0x20 Apr 26 04:27:48 192.168.122.209 [44618.919300] RIP: 0010:native_safe_halt+0xe/0x10 Apr 26 04:27:48 192.168.122.209 [44618.919720] Code: 49 8b 04 24 a8 08 0f 85 71 ff ff ff e9 0f ff ff ff cc cc cc cc cc cc cc cc cc cc cc e9 07 00 00 00 0f 00 2d d4 62 51 00 fb f4 90 e9 07 00 00 00 0f 00 2d c4 62 51 00 f4 c3 cc cc 0f 1f 44 00 Apr 26 04:27:48 192.168.122.209 [44618.921337] RSP: 0018:ffff888100f37db8 EFLAGS: 00000212 Apr 26 04:27:48 192.168.122.209 [44618.921833] RAX: ffffffffb63426a0 RBX: ffff888100f2c0c0 RCX: ffffffffb632c475 Apr 26 04:27:48 192.168.122.209 [44618.922477] RDX: 000000000ab50a6e RSI: 0000000000000004 RDI: ffff888147eb5040 Apr 26 04:27:48 192.168.122.209 [44618.923110] RBP: ffff888100f37dc0 R08: 0000000000000001 R09: ffff888147eb5043 Apr 26 04:27:48 192.168.122.209 [44618.923749] R10: ffffed1028fd6a08 R11: 0000000000000001 R12: 0000000000000001 Apr 26 04:27:48 192.168.122.209 [44618.924385] R13: ffffffffb7ae9360 R14: 0000000000000000 R15: 0000000000000000 Apr 26 04:27:48 192.168.122.209 [44618.925023] ? __cpuidle_text_start+0x8/0x8 Apr 26 04:27:48 192.168.122.209 [44618.925408] ? rcu_eqs_enter.constprop.0+0x85/0xa0 Apr 26 04:27:48 192.168.122.209 [44618.925843] ? default_idle+0xe/0x20 Apr 26 04:27:48 192.168.122.209 [44618.926178] arch_cpu_idle+0x15/0x20 Apr 26 04:27:48 192.168.122.209 [44618.926522] default_idle_call+0x66/0x160 Apr 26 04:27:48 192.168.122.209 [44618.926899] do_idle+0x36f/0x430 Apr 26 04:27:48 192.168.122.209 [44618.927199] ? asm_sysvec_call_function_single+0x12/0x20 Apr 26 04:27:48 192.168.122.209 [44618.927688] ? arch_cpu_idle_exit+0x40/0x40 Apr 26 04:27:48 192.168.122.209 [44618.928073] cpu_startup_entry+0x20/0x30 Apr 26 04:27:48 192.168.122.209 [44618.928440] start_secondary+0x1c1/0x210 Apr 26 04:27:48 192.168.122.209 [44618.928801] ? set_cpu_sibling_map+0xd70/0xd70 Apr 26 04:27:48 192.168.122.209 [44618.929204] ? set_bringup_idt_handler.constprop.0+0x84/0x90 Apr 26 04:27:48 192.168.122.209 [44618.929723] ? start_cpu0+0xc/0xc Apr 26 04:27:48 192.168.122.209 [44618.930030] secondary_startup_64_no_verify+0xb0/0xbb Apr 26 04:27:48 192.168.122.209 [44618.930521] [tempesta fw] Warning: request dropped: internal error in Sticky module: 127.0.0.2 Apr 26 04:27:49 192.168.122.209 [44619.428222] [tdb] Close table 'client0.tdb' Apr 26 04:27:49 192.168.122.209 [44619.622140] [tdb] Close table 'sessions0.tdb' Apr 26 04:27:52 192.168.122.209 [44622.720328] [tdb] Close table 'cache0.tdb' Apr 26 04:27:52 192.168.122.209 [44622.966559] [tdb] Close table 'filter0.tdb' Apr 26 04:27:52 192.168.122.209 [44622.966990] [tempesta fw] modules are stopped Apr 26 04:27:52 192.168.122.209 [44623.175357] [tempesta fw] exiting... Apr 26 04:27:52 192.168.122.209 [44623.335522] [tdb] Shutdown Tempesta DB Apr 26 04:27:53 192.168.122.209 [44623.542480] End test: t_fault_injection.test_fault_injection_base.TestFailFunctionPrepareResp.test_tfw_h2_prep_resp_for_sticky_ccokie Apr 26 04:27:53 192.168.122.209 [44623.559161] Start test: t_fault_injection.test_fault_injection_base.TestFailFunctionStaleFwd.test_tfw_http_resp_do_fwd_stale_h2 Apr 26 04:27:54 192.168.122.209 [44624.702600] [tdb] Start Tempesta DB Apr 26 04:27:54 192.168.122.209 [44624.843694] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:27:56 192.168.122.209 [44626.443991] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44626.443991] Maybe that's fine, but it's worth checking the [44626.443991] config - if there is no relations between the [44626.443991] names, then host name confusion attack is possible. Apr 26 04:27:56 192.168.122.209 [44626.622704] [tempesta fw] Configuration processing is completed. Apr 26 04:27:56 192.168.122.209 [44626.675460] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:27:56 192.168.122.209 [44627.104065] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:27:56 192.168.122.209 [44627.131125] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:27:56 192.168.122.209 [44627.158094] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:27:56 192.168.122.209 [44627.222636] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:27:56 192.168.122.209 [44627.224293] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:27:56 192.168.122.209 [44627.262643] [tempesta fw] Tempesta FW is ready Apr 26 04:28:00 192.168.122.209 [44630.541696] FAULT_INJECTION: forcing a failure. [44630.541696] name fail_function, interval 0, probability 100, space 0, times -1 Apr 26 04:28:00 192.168.122.209 [44630.544925] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G OE 5.10.35.tfw-39c65d3-debug #1 Apr 26 04:28:00 192.168.122.209 [44630.547350] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 Apr 26 04:28:00 192.168.122.209 [44630.549452] Call Trace: Apr 26 04:28:00 192.168.122.209 [44630.549832] Apr 26 04:28:00 192.168.122.209 [44630.550165] dump_stack+0x96/0xc4 Apr 26 04:28:00 192.168.122.209 [44630.550679] should_fail.cold+0x5/0xa Apr 26 04:28:00 192.168.122.209 [44630.551230] fei_kprobe_handler+0x23/0x60 Apr 26 04:28:00 192.168.122.209 [44630.551882] ? tfw_cache_build_resp_stale+0x1/0xb0 [tempesta_fw] Apr 26 04:28:00 192.168.122.209 [44630.552773] kprobe_ftrace_handler+0xbe/0x150 Apr 26 04:28:00 192.168.122.209 [44630.553470] ? tfw_cache_build_resp_stale+0x5/0xb0 [tempesta_fw] Apr 26 04:28:00 192.168.122.209 [44630.554404] ? __tfw_http_resp_fwd_stale+0x47/0x160 [tempesta_fw] Apr 26 04:28:00 192.168.122.209 [44630.555309] ftrace_ops_assist_func+0xef/0x1b0 Apr 26 04:28:00 192.168.122.209 [44630.556027] ? tfw_cache_build_resp+0xb30/0xb30 [tempesta_fw] Apr 26 04:28:00 192.168.122.209 [44630.556886] 0xffffffffc16e00e3 Apr 26 04:28:00 192.168.122.209 [44630.557400] RIP: 0010:tfw_cache_build_resp_stale+0x1/0xb0 [tempesta_fw] Apr 26 04:28:00 192.168.122.209 [44630.558383] Code: e8 94 9e 86 f3 44 3b 6b 24 0f 82 11 ff ff ff e9 9e fb ff ff e8 40 0f 70 f4 e9 a1 ee 0e 00 66 66 2e 0f 1f 84 00 00 00 00 00 e8 <5b> 4c ab ff 55 48 89 e5 41 57 41 56 41 55 41 54 53 48 89 fb 48 8d Apr 26 04:28:00 192.168.122.209 [44630.560383] RSP: 0018:ffff888147e092e8 EFLAGS: 00000246 ORIG_RAX: 0000000000000000 Apr 26 04:28:00 192.168.122.209 [44630.561113] RAX: 0000000000000000 RBX: ffff88800df82020 RCX: ffffffffc1c4c4d6 Apr 26 04:28:00 192.168.122.209 [44630.561736] RDX: dffffc0000000000 RSI: 0000000000000040 RDI: ffff8880372cf020 Apr 26 04:28:00 192.168.122.209 [44630.562357] RBP: ffff888147e09320 R08: ffffffffc1c36b00 R09: 0000000000000000 Apr 26 04:28:00 192.168.122.209 [44630.562997] R10: ffffed1006e59e1b R11: 0000000000000e00 R12: ffff8880372cf020 Apr 26 04:28:00 192.168.122.209 [44630.563633] R13: ffff8880372cf020 R14: ffff8880372cf058 R15: ffff88800df82058 Apr 26 04:28:00 192.168.122.209 [44630.564308] ? tfw_gfsm_move+0xc0/0x310 [tempesta_fw] Apr 26 04:28:00 192.168.122.209 [44630.564796] ? __tfw_http_resp_fwd_stale+0x36/0x160 [tempesta_fw] Apr 26 04:28:00 192.168.122.209 [44630.565358] ? tfw_cache_build_resp_stale+0x5/0xb0 [tempesta_fw] Apr 26 04:28:00 192.168.122.209 [44630.565923] ? __tfw_http_resp_fwd_stale+0x47/0x160 [tempesta_fw] Apr 26 04:28:00 192.168.122.209 [44630.566479] ? tfw_cache_build_resp_stale+0x5/0xb0 [tempesta_fw] Apr 26 04:28:00 192.168.122.209 [44630.567033] ? __tfw_http_resp_fwd_stale+0x47/0x160 [tempesta_fw] Apr 26 04:28:00 192.168.122.209 [44630.567599] tfw_http_msg_process_generic+0x7c8/0xc70 [tempesta_fw] Apr 26 04:28:00 192.168.122.209 [44630.568179] ? tfw_http_req_process+0x11a0/0x11a0 [tempesta_fw] Apr 26 04:28:00 192.168.122.209 [44630.568711] ? __kasan_check_write+0x14/0x20 Apr 26 04:28:00 192.168.122.209 [44630.569136] ? pg_skb_alloc+0x60e/0x680 Apr 26 04:28:00 192.168.122.209 [44630.569481] ? __kasan_check_write+0x14/0x20 Apr 26 04:28:00 192.168.122.209 [44630.569872] ? __alloc_skb+0x278/0x350 Apr 26 04:28:00 192.168.122.209 [44630.570208] ? __kasan_check_write+0x14/0x20 Apr 26 04:28:00 192.168.122.209 [44630.570623] ? __coalesce_frag+0x136/0x370 [tempesta_fw] Apr 26 04:28:00 192.168.122.209 [44630.571120] tfw_http_msg_process+0x80/0xc0 [tempesta_fw] Apr 26 04:28:00 192.168.122.209 [44630.571614] ? skb_release_data+0x8c/0x320 Apr 26 04:28:00 192.168.122.209 [44630.572003] tfw_connection_recv+0x12e/0x250 [tempesta_fw] Apr 26 04:28:00 192.168.122.209 [44630.572508] ? tfw_connection_send+0x70/0x70 [tempesta_fw] Apr 26 04:28:00 192.168.122.209 [44630.573022] ? ss_skb_unroll+0x3d6/0x540 [tempesta_fw] Apr 26 04:28:00 192.168.122.209 [44630.573507] ss_tcp_process_data+0x436/0x8b0 [tempesta_fw] Apr 26 04:28:00 192.168.122.209 [44630.574021] ? __sk_close_locked+0x100/0x100 [tempesta_fw] Apr 26 04:28:00 192.168.122.209 [44630.574542] ss_tcp_data_ready+0x7b/0x150 [tempesta_fw] Apr 26 04:28:00 192.168.122.209 [44630.575011] tcp_data_ready+0x73/0x210 Apr 26 04:28:00 192.168.122.209 [44630.575355] tcp_data_queue+0x1085/0x1d80 Apr 26 04:28:00 192.168.122.209 [44630.575716] ? tcp_validate_incoming+0x1fa/0xa30 Apr 26 04:28:00 192.168.122.209 [44630.576135] ? tcp_data_ready+0x210/0x210 Apr 26 04:28:00 192.168.122.209 [44630.576494] ? tcp_enter_cwr+0x1c0/0x1c0 Apr 26 04:28:00 192.168.122.209 [44630.576857] ? kvm_clock_get_cycles+0x11/0x20 Apr 26 04:28:00 192.168.122.209 [44630.577245] ? ktime_get+0x4f/0xb0 Apr 26 04:28:00 192.168.122.209 [44630.577557] tcp_rcv_established+0x422/0xb40 Apr 26 04:28:00 192.168.122.209 [44630.577936] ? tcp_parse_md5sig_option+0x20/0xb0 Apr 26 04:28:00 192.168.122.209 [44630.578349] ? tcp_data_queue+0x1d80/0x1d80 Apr 26 04:28:00 192.168.122.209 [44630.578726] ? __kasan_check_read+0x11/0x20 Apr 26 04:28:00 192.168.122.209 [44630.579101] tcp_v4_do_rcv+0x25f/0x360 Apr 26 04:28:00 192.168.122.209 [44630.579438] tcp_v4_rcv+0x1600/0x1770 Apr 26 04:28:00 192.168.122.209 [44630.579777] ? tcp_v4_early_demux+0x2f0/0x2f0 Apr 26 04:28:00 192.168.122.209 [44630.580168] ip_protocol_deliver_rcu+0x46/0x2e0 Apr 26 04:28:00 192.168.122.209 [44630.580573] ip_local_deliver_finish+0xc6/0xe0 Apr 26 04:28:00 192.168.122.209 [44630.580966] ip_local_deliver+0x1f5/0x210 Apr 26 04:28:00 192.168.122.209 [44630.581328] ? ip_local_deliver_finish+0xe0/0xe0 Apr 26 04:28:00 192.168.122.209 [44630.581746] ? nf_nat_inet_fn+0x2b3/0x440 [nf_nat] Apr 26 04:28:00 192.168.122.209 [44630.582171] ? ip_protocol_deliver_rcu+0x2e0/0x2e0 Apr 26 04:28:00 192.168.122.209 [44630.582603] ? ip_rcv_finish_core.constprop.0+0x17c/0x890 Apr 26 04:28:00 192.168.122.209 [44630.583085] ip_rcv_finish+0xcf/0xf0 Apr 26 04:28:00 192.168.122.209 [44630.583405] ip_rcv+0x16d/0x180 Apr 26 04:28:00 192.168.122.209 [44630.583696] ? ip_local_deliver+0x210/0x210 Apr 26 04:28:00 192.168.122.209 [44630.584070] ? ip_rcv_finish_core.constprop.0+0x890/0x890 Apr 26 04:28:00 192.168.122.209 [44630.584555] ? ip_local_deliver+0x210/0x210 Apr 26 04:28:00 192.168.122.209 [44630.584932] __netif_receive_skb_one_core+0x132/0x140 Apr 26 04:28:00 192.168.122.209 [44630.585381] ? napi_gro_receive+0x260/0x260 Apr 26 04:28:00 192.168.122.209 [44630.585763] ? find_next_bit+0x14/0x20 Apr 26 04:28:00 192.168.122.209 [44630.586105] ? cpumask_next+0x2c/0x40 Apr 26 04:28:00 192.168.122.209 [44630.586436] ? __kasan_check_write+0x14/0x20 Apr 26 04:28:00 192.168.122.209 [44630.586822] ? _raw_spin_lock+0x7b/0xd0 Apr 26 04:28:00 192.168.122.209 [44630.587167] __netif_receive_skb+0x26/0xb0 Apr 26 04:28:00 192.168.122.209 [44630.587540] ? generic_exec_single+0xb1/0x170 Apr 26 04:28:00 192.168.122.209 [44630.587930] process_backlog+0xfe/0x290 Apr 26 04:28:00 192.168.122.209 [44630.588274] net_rx_action+0x287/0x6b0 Apr 26 04:28:00 192.168.122.209 [44630.588614] ? napi_complete_done+0x2c0/0x2c0 Apr 26 04:28:00 192.168.122.209 [44630.589010] ? switch_fpu_return+0x120/0x120 Apr 26 04:28:00 192.168.122.209 [44630.589392] __do_softirq+0xfe/0x383 Apr 26 04:28:00 192.168.122.209 [44630.589720] asm_call_irq_on_stack+0xf/0x20 Apr 26 04:28:00 192.168.122.209 [44630.590093] Apr 26 04:28:00 192.168.122.209 [44630.590294] do_softirq_own_stack+0x3d/0x50 Apr 26 04:28:00 192.168.122.209 [44630.590673] irq_exit_rcu+0xc7/0x120 Apr 26 04:28:00 192.168.122.209 [44630.590997] sysvec_call_function_single+0x3a/0x90 Apr 26 04:28:00 192.168.122.209 [44630.591421] asm_sysvec_call_function_single+0x12/0x20 Apr 26 04:28:00 192.168.122.209 [44630.591884] RIP: 0010:native_safe_halt+0xe/0x10 Apr 26 04:28:00 192.168.122.209 [44630.592288] Code: 49 8b 04 24 a8 08 0f 85 71 ff ff ff e9 0f ff ff ff cc cc cc cc cc cc cc cc cc cc cc e9 07 00 00 00 0f 00 2d d4 62 51 00 fb f4 90 e9 07 00 00 00 0f 00 2d c4 62 51 00 f4 c3 cc cc 0f 1f 44 00 Apr 26 04:28:00 192.168.122.209 [44630.593900] RSP: 0018:ffffffffb7207dc8 EFLAGS: 00000212 Apr 26 04:28:00 192.168.122.209 [44630.594382] RAX: ffffffffb63426a0 RBX: ffffffffb721b100 RCX: ffffffffb632c475 Apr 26 04:28:00 192.168.122.209 [44630.595013] RDX: 000000000acaa5ae RSI: 0000000000000004 RDI: ffff888147e35040 Apr 26 04:28:00 192.168.122.209 [44630.595639] RBP: ffffffffb7207dd0 R08: 0000000000000001 R09: ffff888147e35043 Apr 26 04:28:00 192.168.122.209 [44630.596259] R10: ffffed1028fc6a08 R11: 0000000000000001 R12: 0000000000000000 Apr 26 04:28:00 192.168.122.209 [44630.596881] R13: ffffffffb7ae9360 R14: 0000000000000000 R15: 0000000000000000 Apr 26 04:28:00 192.168.122.209 [44630.597507] ? __cpuidle_text_start+0x8/0x8 Apr 26 04:28:00 192.168.122.209 [44630.597883] ? rcu_eqs_enter.constprop.0+0x85/0xa0 Apr 26 04:28:00 192.168.122.209 [44630.598306] ? default_idle+0xe/0x20 Apr 26 04:28:00 192.168.122.209 [44630.598633] arch_cpu_idle+0x15/0x20 Apr 26 04:28:00 192.168.122.209 [44630.598958] default_idle_call+0x66/0x160 Apr 26 04:28:00 192.168.122.209 [44630.599318] do_idle+0x36f/0x430 Apr 26 04:28:00 192.168.122.209 [44630.599615] ? arch_cpu_idle_exit+0x40/0x40 Apr 26 04:28:00 192.168.122.209 [44630.599989] cpu_startup_entry+0x20/0x30 Apr 26 04:28:00 192.168.122.209 [44630.600346] rest_init+0xc8/0xce Apr 26 04:28:00 192.168.122.209 [44630.600645] arch_call_rest_init+0xe/0x1b Apr 26 04:28:00 192.168.122.209 [44630.601006] start_kernel+0x380/0x39d Apr 26 04:28:00 192.168.122.209 [44630.601340] x86_64_start_reservations+0x24/0x26 Apr 26 04:28:00 192.168.122.209 [44630.601763] x86_64_start_kernel+0x7a/0x7e Apr 26 04:28:00 192.168.122.209 [44630.602130] secondary_startup_64_no_verify+0xb0/0xbb Apr 26 04:28:00 192.168.122.209 [44630.602616] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 04:28:00 192.168.122.209 [44631.086200] [tdb] Close table 'client0.tdb' Apr 26 04:28:00 192.168.122.209 [44631.269677] [tdb] Close table 'sessions0.tdb' Apr 26 04:28:04 192.168.122.209 [44634.470722] [tdb] Close table 'cache0.tdb' Apr 26 04:28:04 192.168.122.209 [44634.733848] [tdb] Close table 'filter0.tdb' Apr 26 04:28:04 192.168.122.209 [44634.734306] [tempesta fw] modules are stopped Apr 26 04:28:04 192.168.122.209 [44634.926798] [tempesta fw] exiting... Apr 26 04:28:04 192.168.122.209 [44635.064809] [tdb] Shutdown Tempesta DB Apr 26 04:28:04 192.168.122.209 [44635.283078] End test: t_fault_injection.test_fault_injection_base.TestFailFunctionStaleFwd.test_tfw_http_resp_do_fwd_stale_h2 Apr 26 04:28:04 192.168.122.209 [44635.303259] Start test: t_fault_injection.test_fault_injection_base.TestFailFunctionStaleFwd.test_tfw_http_resp_do_fwd_stale_http Apr 26 04:28:06 192.168.122.209 [44636.402324] [tdb] Start Tempesta DB Apr 26 04:28:06 192.168.122.209 [44636.560833] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:28:07 192.168.122.209 [44638.040139] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44638.040139] Maybe that's fine, but it's worth checking the [44638.040139] config - if there is no relations between the [44638.040139] names, then host name confusion attack is possible. Apr 26 04:28:07 192.168.122.209 [44638.190840] [tempesta fw] Configuration processing is completed. Apr 26 04:28:07 192.168.122.209 [44638.242911] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:28:08 192.168.122.209 [44638.699789] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:28:08 192.168.122.209 [44638.737772] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:28:08 192.168.122.209 [44638.764724] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:28:08 192.168.122.209 [44638.818842] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:28:08 192.168.122.209 [44638.820525] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:28:08 192.168.122.209 [44638.858792] [tempesta fw] Tempesta FW is ready Apr 26 04:28:11 192.168.122.209 [44642.146044] FAULT_INJECTION: forcing a failure. [44642.146044] name fail_function, interval 0, probability 100, space 0, times -1 Apr 26 04:28:11 192.168.122.209 [44642.149322] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G OE 5.10.35.tfw-39c65d3-debug #1 Apr 26 04:28:11 192.168.122.209 [44642.151748] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 Apr 26 04:28:11 192.168.122.209 [44642.154021] Call Trace: Apr 26 04:28:11 192.168.122.209 [44642.154461] Apr 26 04:28:11 192.168.122.209 [44642.154855] dump_stack+0x96/0xc4 Apr 26 04:28:11 192.168.122.209 [44642.155444] should_fail.cold+0x5/0xa Apr 26 04:28:11 192.168.122.209 [44642.156092] fei_kprobe_handler+0x23/0x60 Apr 26 04:28:11 192.168.122.209 [44642.156849] ? tfw_cache_build_resp_stale+0x1/0xb0 [tempesta_fw] Apr 26 04:28:11 192.168.122.209 [44642.157897] kprobe_ftrace_handler+0xbe/0x150 Apr 26 04:28:11 192.168.122.209 [44642.158699] ? tfw_cache_build_resp_stale+0x5/0xb0 [tempesta_fw] Apr 26 04:28:11 192.168.122.209 [44642.159779] ? __tfw_http_resp_fwd_stale+0x47/0x160 [tempesta_fw] Apr 26 04:28:11 192.168.122.209 [44642.160824] ftrace_ops_assist_func+0xef/0x1b0 Apr 26 04:28:11 192.168.122.209 [44642.161644] ? tfw_cache_build_resp+0xb30/0xb30 [tempesta_fw] Apr 26 04:28:11 192.168.122.209 [44642.162631] 0xffffffffc16e00e3 Apr 26 04:28:11 192.168.122.209 [44642.163324] RIP: 0010:tfw_cache_build_resp_stale+0x1/0xb0 [tempesta_fw] Apr 26 04:28:11 192.168.122.209 [44642.164074] Code: e8 94 9e 86 f3 44 3b 6b 24 0f 82 11 ff ff ff e9 9e fb ff ff e8 40 0f 70 f4 e9 a1 ee 0e 00 66 66 2e 0f 1f 84 00 00 00 00 00 e8 <5b> 4c ab ff 55 48 89 e5 41 57 41 56 41 55 41 54 53 48 89 fb 48 8d Apr 26 04:28:11 192.168.122.209 [44642.165704] RSP: 0018:ffff888147e092e8 EFLAGS: 00000246 ORIG_RAX: 0000000000000000 Apr 26 04:28:11 192.168.122.209 [44642.166364] RAX: 0000000000000000 RBX: ffff88803bb4d020 RCX: ffffffffc1c4c4d6 Apr 26 04:28:11 192.168.122.209 [44642.166993] RDX: dffffc0000000000 RSI: 0000000000000040 RDI: ffff88800e5b4020 Apr 26 04:28:11 192.168.122.209 [44642.167619] RBP: ffff888147e09320 R08: ffffffffc1c36b00 R09: 0000000000000000 Apr 26 04:28:11 192.168.122.209 [44642.168249] R10: ffffed1001cb681b R11: 0000000000000e00 R12: ffff88800e5b4020 Apr 26 04:28:11 192.168.122.209 [44642.168875] R13: ffff88800e5b4020 R14: ffff88800e5b4058 R15: ffff88803bb4d058 Apr 26 04:28:11 192.168.122.209 [44642.169523] ? tfw_gfsm_move+0xc0/0x310 [tempesta_fw] Apr 26 04:28:11 192.168.122.209 [44642.169997] ? __tfw_http_resp_fwd_stale+0x36/0x160 [tempesta_fw] Apr 26 04:28:11 192.168.122.209 [44642.170561] ? tfw_cache_build_resp_stale+0x5/0xb0 [tempesta_fw] Apr 26 04:28:11 192.168.122.209 [44642.171115] ? __tfw_http_resp_fwd_stale+0x47/0x160 [tempesta_fw] Apr 26 04:28:11 192.168.122.209 [44642.171678] ? tfw_cache_build_resp_stale+0x5/0xb0 [tempesta_fw] Apr 26 04:28:11 192.168.122.209 [44642.172229] ? __tfw_http_resp_fwd_stale+0x47/0x160 [tempesta_fw] Apr 26 04:28:11 192.168.122.209 [44642.172797] tfw_http_msg_process_generic+0x7c8/0xc70 [tempesta_fw] Apr 26 04:28:11 192.168.122.209 [44642.173381] ? tfw_http_req_process+0x11a0/0x11a0 [tempesta_fw] Apr 26 04:28:11 192.168.122.209 [44642.173909] ? pg_skb_alloc+0x60e/0x680 Apr 26 04:28:11 192.168.122.209 [44642.174257] ? __kasan_check_write+0x14/0x20 Apr 26 04:28:11 192.168.122.209 [44642.174646] ? __alloc_skb+0x278/0x350 Apr 26 04:28:11 192.168.122.209 [44642.174984] ? __kasan_check_write+0x14/0x20 Apr 26 04:28:11 192.168.122.209 [44642.175394] ? __coalesce_frag+0x136/0x370 [tempesta_fw] Apr 26 04:28:11 192.168.122.209 [44642.175891] tfw_http_msg_process+0x80/0xc0 [tempesta_fw] Apr 26 04:28:11 192.168.122.209 [44642.176370] ? skb_release_data+0x8c/0x320 Apr 26 04:28:11 192.168.122.209 [44642.176765] tfw_connection_recv+0x12e/0x250 [tempesta_fw] Apr 26 04:28:11 192.168.122.209 [44642.177273] ? tfw_connection_send+0x70/0x70 [tempesta_fw] Apr 26 04:28:11 192.168.122.209 [44642.177793] ? ss_skb_unroll+0x3d6/0x540 [tempesta_fw] Apr 26 04:28:11 192.168.122.209 [44642.178283] ss_tcp_process_data+0x436/0x8b0 [tempesta_fw] Apr 26 04:28:11 192.168.122.209 [44642.178803] ? __sk_close_locked+0x100/0x100 [tempesta_fw] Apr 26 04:28:11 192.168.122.209 [44642.179316] ss_tcp_data_ready+0x7b/0x150 [tempesta_fw] Apr 26 04:28:11 192.168.122.209 [44642.179785] tcp_data_ready+0x73/0x210 Apr 26 04:28:11 192.168.122.209 [44642.180128] tcp_data_queue+0x1085/0x1d80 Apr 26 04:28:11 192.168.122.209 [44642.180487] ? tcp_validate_incoming+0x1fa/0xa30 Apr 26 04:28:11 192.168.122.209 [44642.180902] ? tcp_data_ready+0x210/0x210 Apr 26 04:28:11 192.168.122.209 [44642.181262] ? tcp_enter_cwr+0x1c0/0x1c0 Apr 26 04:28:11 192.168.122.209 [44642.181619] ? kvm_clock_get_cycles+0x11/0x20 Apr 26 04:28:11 192.168.122.209 [44642.182012] ? ktime_get+0x4f/0xb0 Apr 26 04:28:11 192.168.122.209 [44642.182320] tcp_rcv_established+0x422/0xb40 Apr 26 04:28:11 192.168.122.209 [44642.182704] ? tcp_parse_md5sig_option+0x20/0xb0 Apr 26 04:28:11 192.168.122.209 [44642.183120] ? tcp_data_queue+0x1d80/0x1d80 Apr 26 04:28:11 192.168.122.209 [44642.183499] ? __kasan_check_read+0x11/0x20 Apr 26 04:28:11 192.168.122.209 [44642.183881] tcp_v4_do_rcv+0x25f/0x360 Apr 26 04:28:11 192.168.122.209 [44642.184220] tcp_v4_rcv+0x1600/0x1770 Apr 26 04:28:11 192.168.122.209 [44642.184557] ? tcp_v4_early_demux+0x2f0/0x2f0 Apr 26 04:28:11 192.168.122.209 [44642.184953] ip_protocol_deliver_rcu+0x46/0x2e0 Apr 26 04:28:11 192.168.122.209 [44642.185356] ip_local_deliver_finish+0xc6/0xe0 Apr 26 04:28:11 192.168.122.209 [44642.185757] ip_local_deliver+0x1f5/0x210 Apr 26 04:28:11 192.168.122.209 [44642.186122] ? ip_local_deliver_finish+0xe0/0xe0 Apr 26 04:28:11 192.168.122.209 [44642.186538] ? nf_nat_inet_fn+0x2b3/0x440 [nf_nat] Apr 26 04:28:11 192.168.122.209 [44642.186967] ? ip_protocol_deliver_rcu+0x2e0/0x2e0 Apr 26 04:28:11 192.168.122.209 [44642.187393] ? ip_rcv_finish_core.constprop.0+0x17c/0x890 Apr 26 04:28:11 192.168.122.209 [44642.187877] ip_rcv_finish+0xcf/0xf0 Apr 26 04:28:11 192.168.122.209 [44642.188201] ip_rcv+0x16d/0x180 Apr 26 04:28:11 192.168.122.209 [44642.188488] ? ip_local_deliver+0x210/0x210 Apr 26 04:28:11 192.168.122.209 [44642.188867] ? ip_rcv_finish_core.constprop.0+0x890/0x890 Apr 26 04:28:11 192.168.122.209 [44642.189357] ? ip_local_deliver+0x210/0x210 Apr 26 04:28:11 192.168.122.209 [44642.189737] __netif_receive_skb_one_core+0x132/0x140 Apr 26 04:28:11 192.168.122.209 [44642.190184] ? napi_gro_receive+0x260/0x260 Apr 26 04:28:11 192.168.122.209 [44642.190559] ? find_next_bit+0x14/0x20 Apr 26 04:28:11 192.168.122.209 [44642.190915] ? cpumask_next+0x2c/0x40 Apr 26 04:28:11 192.168.122.209 [44642.191251] ? __kasan_check_write+0x14/0x20 Apr 26 04:28:11 192.168.122.209 [44642.191634] ? _raw_spin_lock+0x7b/0xd0 Apr 26 04:28:11 192.168.122.209 [44642.191984] __netif_receive_skb+0x26/0xb0 Apr 26 04:28:11 192.168.122.209 [44642.192356] process_backlog+0xfe/0x290 Apr 26 04:28:11 192.168.122.209 [44642.192707] net_rx_action+0x287/0x6b0 Apr 26 04:28:11 192.168.122.209 [44642.193044] ? napi_complete_done+0x2c0/0x2c0 Apr 26 04:28:11 192.168.122.209 [44642.193438] ? switch_fpu_return+0x120/0x120 Apr 26 04:28:11 192.168.122.209 [44642.193832] __do_softirq+0xfe/0x383 Apr 26 04:28:11 192.168.122.209 [44642.194156] asm_call_irq_on_stack+0xf/0x20 Apr 26 04:28:11 192.168.122.209 [44642.194530] Apr 26 04:28:11 192.168.122.209 [44642.194736] do_softirq_own_stack+0x3d/0x50 Apr 26 04:28:11 192.168.122.209 [44642.195117] irq_exit_rcu+0xc7/0x120 Apr 26 04:28:11 192.168.122.209 [44642.195441] sysvec_call_function_single+0x3a/0x90 Apr 26 04:28:11 192.168.122.209 [44642.195871] asm_sysvec_call_function_single+0x12/0x20 Apr 26 04:28:11 192.168.122.209 [44642.196328] RIP: 0010:native_safe_halt+0xe/0x10 Apr 26 04:28:11 192.168.122.209 [44642.196746] Code: 49 8b 04 24 a8 08 0f 85 71 ff ff ff e9 0f ff ff ff cc cc cc cc cc cc cc cc cc cc cc e9 07 00 00 00 0f 00 2d d4 62 51 00 fb f4 90 e9 07 00 00 00 0f 00 2d c4 62 51 00 f4 c3 cc cc 0f 1f 44 00 Apr 26 04:28:11 192.168.122.209 [44642.198368] RSP: 0018:ffffffffb7207dc8 EFLAGS: 00000216 Apr 26 04:28:11 192.168.122.209 [44642.198834] RAX: ffffffffb63426a0 RBX: ffffffffb721b100 RCX: ffffffffb632c475 Apr 26 04:28:11 192.168.122.209 [44642.199462] RDX: 000000000acad64e RSI: 0000000000000004 RDI: ffff888147e35040 Apr 26 04:28:11 192.168.122.209 [44642.200096] RBP: ffffffffb7207dd0 R08: 0000000000000001 R09: ffff888147e35043 Apr 26 04:28:11 192.168.122.209 [44642.200720] R10: ffffed1028fc6a08 R11: 0000000000000001 R12: 0000000000000000 Apr 26 04:28:11 192.168.122.209 [44642.201340] R13: ffffffffb7ae9360 R14: 0000000000000000 R15: 0000000000000000 Apr 26 04:28:11 192.168.122.209 [44642.201966] ? __cpuidle_text_start+0x8/0x8 Apr 26 04:28:11 192.168.122.209 [44642.202344] ? rcu_eqs_enter.constprop.0+0x85/0xa0 Apr 26 04:28:11 192.168.122.209 [44642.202774] ? default_idle+0xe/0x20 Apr 26 04:28:11 192.168.122.209 [44642.203095] arch_cpu_idle+0x15/0x20 Apr 26 04:28:11 192.168.122.209 [44642.203424] default_idle_call+0x66/0x160 Apr 26 04:28:11 192.168.122.209 [44642.203796] do_idle+0x36f/0x430 Apr 26 04:28:11 192.168.122.209 [44642.204088] ? arch_cpu_idle_exit+0x40/0x40 Apr 26 04:28:11 192.168.122.209 [44642.204466] cpu_startup_entry+0x20/0x30 Apr 26 04:28:11 192.168.122.209 [44642.204824] rest_init+0xc8/0xce Apr 26 04:28:11 192.168.122.209 [44642.205129] arch_call_rest_init+0xe/0x1b Apr 26 04:28:11 192.168.122.209 [44642.205489] start_kernel+0x380/0x39d Apr 26 04:28:11 192.168.122.209 [44642.205823] x86_64_start_reservations+0x24/0x26 Apr 26 04:28:11 192.168.122.209 [44642.206236] x86_64_start_kernel+0x7a/0x7e Apr 26 04:28:11 192.168.122.209 [44642.206609] secondary_startup_64_no_verify+0xb0/0xbb Apr 26 04:28:11 192.168.122.209 [44642.207079] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 04:28:12 192.168.122.209 [44642.693394] [tdb] Close table 'client0.tdb' Apr 26 04:28:12 192.168.122.209 [44642.895168] [tdb] Close table 'sessions0.tdb' Apr 26 04:28:15 192.168.122.209 [44646.116905] [tdb] Close table 'cache0.tdb' Apr 26 04:28:16 192.168.122.209 [44646.369087] [tdb] Close table 'filter0.tdb' Apr 26 04:28:16 192.168.122.209 [44646.369522] [tempesta fw] modules are stopped Apr 26 04:28:16 192.168.122.209 [44646.558143] [tempesta fw] exiting... Apr 26 04:28:16 192.168.122.209 [44646.722045] [tdb] Shutdown Tempesta DB Apr 26 04:28:16 192.168.122.209 [44646.945861] End test: t_fault_injection.test_fault_injection_base.TestFailFunctionStaleFwd.test_tfw_http_resp_do_fwd_stale_http Apr 26 04:28:16 192.168.122.209 [44646.961208] Start test: t_fault_injection.test_fault_injection_base.TestFailFunctionStaleFwd.test_tfw_http_resp_do_fwd_stale_invalid_resp_h2 Apr 26 04:28:17 192.168.122.209 [44648.163301] [tdb] Start Tempesta DB Apr 26 04:28:17 192.168.122.209 [44648.321361] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:28:19 192.168.122.209 [44649.899616] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44649.899616] Maybe that's fine, but it's worth checking the [44649.899616] config - if there is no relations between the [44649.899616] names, then host name confusion attack is possible. Apr 26 04:28:19 192.168.122.209 [44650.059005] [tempesta fw] Configuration processing is completed. Apr 26 04:28:19 192.168.122.209 [44650.111701] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:28:20 192.168.122.209 [44650.560792] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:28:20 192.168.122.209 [44650.590451] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:28:20 192.168.122.209 [44650.618237] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:28:20 192.168.122.209 [44650.658977] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:28:20 192.168.122.209 [44650.660652] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:28:20 192.168.122.209 [44650.702922] [tempesta fw] Tempesta FW is ready Apr 26 04:28:23 192.168.122.209 [44653.969034] [tempesta fw] Warning: Parser error: state=RGen_HdrOtherN input(-8)=0x68('gth: 0 [44653.969034] hd>r: v [44653.969034] date: Sat, 26 Apr 2025 04:28:23') data_len=93 off=45 Apr 26 04:28:23 192.168.122.209 [44653.973650] FAULT_INJECTION: forcing a failure. [44653.973650] name fail_function, interval 0, probability 100, space 0, times -1 Apr 26 04:28:23 192.168.122.209 [44653.976838] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G OE 5.10.35.tfw-39c65d3-debug #1 Apr 26 04:28:23 192.168.122.209 [44653.979250] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 Apr 26 04:28:23 192.168.122.209 [44653.980616] Call Trace: Apr 26 04:28:23 192.168.122.209 [44653.980913] Apr 26 04:28:23 192.168.122.209 [44653.981152] dump_stack+0x96/0xc4 Apr 26 04:28:23 192.168.122.209 [44653.981524] should_fail.cold+0x5/0xa Apr 26 04:28:23 192.168.122.209 [44653.981940] fei_kprobe_handler+0x23/0x60 Apr 26 04:28:23 192.168.122.209 [44653.982448] ? tfw_cache_build_resp_stale+0x1/0xb0 [tempesta_fw] Apr 26 04:28:23 192.168.122.209 [44653.983107] kprobe_ftrace_handler+0xbe/0x150 Apr 26 04:28:23 192.168.122.209 [44653.983623] ? tfw_cache_build_resp_stale+0x5/0xb0 [tempesta_fw] Apr 26 04:28:23 192.168.122.209 [44653.984313] ? __tfw_http_resp_fwd_stale+0x47/0x160 [tempesta_fw] Apr 26 04:28:23 192.168.122.209 [44653.984990] ftrace_ops_assist_func+0xef/0x1b0 Apr 26 04:28:23 192.168.122.209 [44653.985506] ? tfw_cache_build_resp+0xb30/0xb30 [tempesta_fw] Apr 26 04:28:23 192.168.122.209 [44653.986143] 0xffffffffc16e00e3 Apr 26 04:28:23 192.168.122.209 [44653.986528] RIP: 0010:tfw_cache_build_resp_stale+0x1/0xb0 [tempesta_fw] Apr 26 04:28:23 192.168.122.209 [44653.987254] Code: e8 94 9e 86 f3 44 3b 6b 24 0f 82 11 ff ff ff e9 9e fb ff ff e8 40 0f 70 f4 e9 a1 ee 0e 00 66 66 2e 0f 1f 84 00 00 00 00 00 e8 <5b> 4c ab ff 55 48 89 e5 41 57 41 56 41 55 41 54 53 48 89 fb 48 8d Apr 26 04:28:23 192.168.122.209 [44653.989255] RSP: 0018:ffff888147e892e8 EFLAGS: 00000246 ORIG_RAX: 0000000000000000 Apr 26 04:28:23 192.168.122.209 [44653.990069] RAX: 0000000000000000 RBX: ffff88800c788020 RCX: ffffffffc1c4c4d6 Apr 26 04:28:23 192.168.122.209 [44653.990697] RDX: dffffc0000000000 RSI: 0000000000000008 RDI: ffff88803f1ec020 Apr 26 04:28:23 192.168.122.209 [44653.991369] RBP: ffff888147e89320 R08: 0000000000000000 R09: ffff88810d016fff Apr 26 04:28:23 192.168.122.209 [44653.991996] R10: ffffed1021a02dff R11: 0000000000000001 R12: ffff88803f1ec020 Apr 26 04:28:23 192.168.122.209 [44653.992623] R13: ffff88803f1ec0d8 R14: ffff88803f1ec058 R15: ffff88800c788058 Apr 26 04:28:23 192.168.122.209 [44653.993282] ? __tfw_http_resp_fwd_stale+0x36/0x160 [tempesta_fw] Apr 26 04:28:23 192.168.122.209 [44653.993852] ? tfw_cache_build_resp_stale+0x5/0xb0 [tempesta_fw] Apr 26 04:28:23 192.168.122.209 [44653.994410] ? __tfw_http_resp_fwd_stale+0x47/0x160 [tempesta_fw] Apr 26 04:28:23 192.168.122.209 [44653.994978] ? tfw_cache_build_resp_stale+0x5/0xb0 [tempesta_fw] Apr 26 04:28:23 192.168.122.209 [44653.995533] ? __tfw_http_resp_fwd_stale+0x47/0x160 [tempesta_fw] Apr 26 04:28:23 192.168.122.209 [44653.996106] tfw_http_msg_process_generic+0xb6b/0xc70 [tempesta_fw] Apr 26 04:28:23 192.168.122.209 [44653.996659] ? ftrace_graph_ret_addr+0x2a/0xb0 Apr 26 04:28:23 192.168.122.209 [44653.997062] ? stack_trace_save+0x94/0xc0 Apr 26 04:28:23 192.168.122.209 [44653.997424] ? get_stack_info_noinstr+0x17/0xf0 Apr 26 04:28:23 192.168.122.209 [44653.997866] ? tfw_http_req_process+0x11a0/0x11a0 [tempesta_fw] Apr 26 04:28:23 192.168.122.209 [44653.998393] ? pg_skb_alloc+0x60e/0x680 Apr 26 04:28:23 192.168.122.209 [44653.998746] ? __kasan_check_write+0x14/0x20 Apr 26 04:28:23 192.168.122.209 [44653.999133] ? __alloc_skb+0x278/0x350 Apr 26 04:28:23 192.168.122.209 [44653.999479] ? __kasan_check_write+0x14/0x20 Apr 26 04:28:23 192.168.122.209 [44653.999893] ? __coalesce_frag+0x136/0x370 [tempesta_fw] Apr 26 04:28:23 192.168.122.209 [44654.000391] tfw_http_msg_process+0x80/0xc0 [tempesta_fw] Apr 26 04:28:23 192.168.122.209 [44654.000873] ? skb_release_data+0x8c/0x320 Apr 26 04:28:23 192.168.122.209 [44654.001271] tfw_connection_recv+0x12e/0x250 [tempesta_fw] Apr 26 04:28:23 192.168.122.209 [44654.001809] ? tfw_connection_send+0x70/0x70 [tempesta_fw] Apr 26 04:28:23 192.168.122.209 [44654.002331] ? ss_skb_unroll+0x3d6/0x540 [tempesta_fw] Apr 26 04:28:23 192.168.122.209 [44654.002827] ss_tcp_process_data+0x436/0x8b0 [tempesta_fw] Apr 26 04:28:23 192.168.122.209 [44654.003364] ? __sk_close_locked+0x100/0x100 [tempesta_fw] Apr 26 04:28:23 192.168.122.209 [44654.003882] ss_tcp_data_ready+0x7b/0x150 [tempesta_fw] Apr 26 04:28:23 192.168.122.209 [44654.004349] tcp_data_ready+0x73/0x210 Apr 26 04:28:23 192.168.122.209 [44654.004689] tcp_data_queue+0x1085/0x1d80 Apr 26 04:28:23 192.168.122.209 [44654.005064] ? tcp_validate_incoming+0x1fa/0xa30 Apr 26 04:28:23 192.168.122.209 [44654.005478] ? tcp_data_ready+0x210/0x210 Apr 26 04:28:23 192.168.122.209 [44654.005843] ? tcp_enter_cwr+0x1c0/0x1c0 Apr 26 04:28:23 192.168.122.209 [44654.006197] ? kvm_clock_get_cycles+0x11/0x20 Apr 26 04:28:23 192.168.122.209 [44654.006593] ? ktime_get+0x4f/0xb0 Apr 26 04:28:23 192.168.122.209 [44654.006907] tcp_rcv_established+0x422/0xb40 Apr 26 04:28:23 192.168.122.209 [44654.007292] ? tcp_parse_md5sig_option+0x20/0xb0 Apr 26 04:28:23 192.168.122.209 [44654.007706] ? tcp_data_queue+0x1d80/0x1d80 Apr 26 04:28:23 192.168.122.209 [44654.008093] ? __kasan_check_read+0x11/0x20 Apr 26 04:28:23 192.168.122.209 [44654.008469] tcp_v4_do_rcv+0x25f/0x360 Apr 26 04:28:23 192.168.122.209 [44654.008807] tcp_v4_rcv+0x1600/0x1770 Apr 26 04:28:23 192.168.122.209 [44654.009145] ? tcp_v4_early_demux+0x2f0/0x2f0 Apr 26 04:28:23 192.168.122.209 [44654.009543] ip_protocol_deliver_rcu+0x46/0x2e0 Apr 26 04:28:23 192.168.122.209 [44654.009950] ip_local_deliver_finish+0xc6/0xe0 Apr 26 04:28:23 192.168.122.209 [44654.010349] ip_local_deliver+0x1f5/0x210 Apr 26 04:28:23 192.168.122.209 [44654.010712] ? ip_local_deliver_finish+0xe0/0xe0 Apr 26 04:28:23 192.168.122.209 [44654.011135] ? nf_nat_inet_fn+0x2b3/0x440 [nf_nat] Apr 26 04:28:23 192.168.122.209 [44654.011578] ? ip_protocol_deliver_rcu+0x2e0/0x2e0 Apr 26 04:28:23 192.168.122.209 [44654.012014] ? ip_rcv_finish_core.constprop.0+0x17c/0x890 Apr 26 04:28:23 192.168.122.209 [44654.012497] ip_rcv_finish+0xcf/0xf0 Apr 26 04:28:23 192.168.122.209 [44654.012833] ip_rcv+0x16d/0x180 Apr 26 04:28:23 192.168.122.209 [44654.013121] ? ip_local_deliver+0x210/0x210 Apr 26 04:28:23 192.168.122.209 [44654.013496] ? ip_rcv_finish_core.constprop.0+0x890/0x890 Apr 26 04:28:23 192.168.122.209 [44654.013978] ? ip_local_deliver+0x210/0x210 Apr 26 04:28:23 192.168.122.209 [44654.014362] __netif_receive_skb_one_core+0x132/0x140 Apr 26 04:28:23 192.168.122.209 [44654.014808] ? napi_gro_receive+0x260/0x260 Apr 26 04:28:23 192.168.122.209 [44654.015187] ? find_next_bit+0x14/0x20 Apr 26 04:28:23 192.168.122.209 [44654.015526] ? cpumask_next+0x2c/0x40 Apr 26 04:28:23 192.168.122.209 [44654.015866] ? __kasan_check_write+0x14/0x20 Apr 26 04:28:23 192.168.122.209 [44654.016250] ? _raw_spin_lock+0x7b/0xd0 Apr 26 04:28:23 192.168.122.209 [44654.016597] __netif_receive_skb+0x26/0xb0 Apr 26 04:28:23 192.168.122.209 [44654.016969] ? generic_exec_single+0xb1/0x170 Apr 26 04:28:23 192.168.122.209 [44654.017362] process_backlog+0xfe/0x290 Apr 26 04:28:23 192.168.122.209 [44654.017706] net_rx_action+0x287/0x6b0 Apr 26 04:28:23 192.168.122.209 [44654.018046] ? napi_complete_done+0x2c0/0x2c0 Apr 26 04:28:23 192.168.122.209 [44654.018441] ? switch_fpu_return+0x120/0x120 Apr 26 04:28:23 192.168.122.209 [44654.018830] __do_softirq+0xfe/0x383 Apr 26 04:28:23 192.168.122.209 [44654.019156] asm_call_irq_on_stack+0xf/0x20 Apr 26 04:28:23 192.168.122.209 [44654.019531] Apr 26 04:28:23 192.168.122.209 [44654.019731] do_softirq_own_stack+0x3d/0x50 Apr 26 04:28:23 192.168.122.209 [44654.020117] irq_exit_rcu+0xc7/0x120 Apr 26 04:28:23 192.168.122.209 [44654.020441] sysvec_call_function_single+0x3a/0x90 Apr 26 04:28:23 192.168.122.209 [44654.020874] asm_sysvec_call_function_single+0x12/0x20 Apr 26 04:28:23 192.168.122.209 [44654.021332] RIP: 0010:native_safe_halt+0xe/0x10 Apr 26 04:28:23 192.168.122.209 [44654.021742] Code: 49 8b 04 24 a8 08 0f 85 71 ff ff ff e9 0f ff ff ff cc cc cc cc cc cc cc cc cc cc cc e9 07 00 00 00 0f 00 2d d4 62 51 00 fb f4 90 e9 07 00 00 00 0f 00 2d c4 62 51 00 f4 c3 cc cc 0f 1f 44 00 Apr 26 04:28:23 192.168.122.209 [44654.023374] RSP: 0018:ffff888100f37db8 EFLAGS: 00000206 Apr 26 04:28:23 192.168.122.209 [44654.023847] RAX: ffffffffb63426a0 RBX: ffff888100f2c0c0 RCX: ffffffffb632c475 Apr 26 04:28:23 192.168.122.209 [44654.024473] RDX: 000000000ac3a95a RSI: 0000000000000004 RDI: ffff888147eb5040 Apr 26 04:28:23 192.168.122.209 [44654.025109] RBP: ffff888100f37dc0 R08: 0000000000000001 R09: ffff888147eb5043 Apr 26 04:28:23 192.168.122.209 [44654.025728] R10: ffffed1028fd6a08 R11: 0000000000000001 R12: 0000000000000001 Apr 26 04:28:23 192.168.122.209 [44654.026353] R13: ffffffffb7ae9360 R14: 0000000000000000 R15: 0000000000000000 Apr 26 04:28:23 192.168.122.209 [44654.026980] ? __cpuidle_text_start+0x8/0x8 Apr 26 04:28:23 192.168.122.209 [44654.027357] ? rcu_eqs_enter.constprop.0+0x85/0xa0 Apr 26 04:28:23 192.168.122.209 [44654.027785] ? default_idle+0xe/0x20 Apr 26 04:28:23 192.168.122.209 [44654.028113] arch_cpu_idle+0x15/0x20 Apr 26 04:28:23 192.168.122.209 [44654.028434] default_idle_call+0x66/0x160 Apr 26 04:28:23 192.168.122.209 [44654.028800] do_idle+0x36f/0x430 Apr 26 04:28:23 192.168.122.209 [44654.029097] ? asm_sysvec_apic_timer_interrupt+0x12/0x20 Apr 26 04:28:23 192.168.122.209 [44654.029579] ? arch_cpu_idle_exit+0x40/0x40 Apr 26 04:28:23 192.168.122.209 [44654.029959] cpu_startup_entry+0x20/0x30 Apr 26 04:28:23 192.168.122.209 [44654.030319] start_secondary+0x1c1/0x210 Apr 26 04:28:23 192.168.122.209 [44654.030671] ? set_cpu_sibling_map+0xd70/0xd70 Apr 26 04:28:23 192.168.122.209 [44654.031077] ? set_bringup_idt_handler.constprop.0+0x84/0x90 Apr 26 04:28:23 192.168.122.209 [44654.031576] ? start_cpu0+0xc/0xc Apr 26 04:28:23 192.168.122.209 [44654.031891] secondary_startup_64_no_verify+0xb0/0xbb Apr 26 04:28:23 192.168.122.209 [44654.032367] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 04:28:24 192.168.122.209 [44654.479761] [tdb] Close table 'client0.tdb' Apr 26 04:28:24 192.168.122.209 [44654.690935] [tdb] Close table 'sessions0.tdb' Apr 26 04:28:27 192.168.122.209 [44657.934784] [tdb] Close table 'cache0.tdb' Apr 26 04:28:27 192.168.122.209 [44658.185477] [tdb] Close table 'filter0.tdb' Apr 26 04:28:27 192.168.122.209 [44658.185944] [tempesta fw] modules are stopped Apr 26 04:28:28 192.168.122.209 [44658.368209] [tempesta fw] exiting... Apr 26 04:28:28 192.168.122.209 [44658.498664] [tdb] Shutdown Tempesta DB Apr 26 04:28:28 192.168.122.209 [44658.718737] End test: t_fault_injection.test_fault_injection_base.TestFailFunctionStaleFwd.test_tfw_http_resp_do_fwd_stale_invalid_resp_h2 Apr 26 04:28:28 192.168.122.209 [44658.731470] Start test: t_fault_injection.test_fault_injection_base.TestFailFunctionStaleFwd.test_tfw_http_resp_do_fwd_stale_invalid_resp_http Apr 26 04:28:29 192.168.122.209 [44659.899098] [tdb] Start Tempesta DB Apr 26 04:28:29 192.168.122.209 [44660.054834] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:28:31 192.168.122.209 [44661.572449] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44661.572449] Maybe that's fine, but it's worth checking the [44661.572449] config - if there is no relations between the [44661.572449] names, then host name confusion attack is possible. Apr 26 04:28:31 192.168.122.209 [44661.755183] [tempesta fw] Configuration processing is completed. Apr 26 04:28:31 192.168.122.209 [44661.810788] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:28:31 192.168.122.209 [44662.251653] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:28:31 192.168.122.209 [44662.280509] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:28:31 192.168.122.209 [44662.307837] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:28:31 192.168.122.209 [44662.359172] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:28:31 192.168.122.209 [44662.360865] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:28:32 192.168.122.209 [44662.399080] [tempesta fw] Tempesta FW is ready Apr 26 04:28:35 192.168.122.209 [44665.683711] [tempesta fw] Warning: Parser error: state=RGen_HdrOtherN input(-8)=0x68('gth: 0 [44665.683711] hd>r: v [44665.683711] date: Sat, 26 Apr 2025 04:28:35') data_len=93 off=45 Apr 26 04:28:35 192.168.122.209 [44665.685223] FAULT_INJECTION: forcing a failure. [44665.685223] name fail_function, interval 0, probability 100, space 0, times -1 Apr 26 04:28:35 192.168.122.209 [44665.686278] CPU: 0 PID: 307525 Comm: python3.10 Tainted: G OE 5.10.35.tfw-39c65d3-debug #1 Apr 26 04:28:35 192.168.122.209 [44665.687113] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 Apr 26 04:28:35 192.168.122.209 [44665.687931] Call Trace: Apr 26 04:28:35 192.168.122.209 [44665.688165] Apr 26 04:28:35 192.168.122.209 [44665.688364] dump_stack+0x96/0xc4 Apr 26 04:28:35 192.168.122.209 [44665.688667] should_fail.cold+0x5/0xa Apr 26 04:28:35 192.168.122.209 [44665.689007] fei_kprobe_handler+0x23/0x60 Apr 26 04:28:35 192.168.122.209 [44665.689402] ? tfw_cache_build_resp_stale+0x1/0xb0 [tempesta_fw] Apr 26 04:28:35 192.168.122.209 [44665.689938] kprobe_ftrace_handler+0xbe/0x150 Apr 26 04:28:35 192.168.122.209 [44665.690356] ? tfw_cache_build_resp_stale+0x5/0xb0 [tempesta_fw] Apr 26 04:28:35 192.168.122.209 [44665.690914] ? __tfw_http_resp_fwd_stale+0x47/0x160 [tempesta_fw] Apr 26 04:28:35 192.168.122.209 [44665.691459] ftrace_ops_assist_func+0xef/0x1b0 Apr 26 04:28:35 192.168.122.209 [44665.691884] ? tfw_cache_build_resp+0xb30/0xb30 [tempesta_fw] Apr 26 04:28:35 192.168.122.209 [44665.692412] 0xffffffffc16e00e3 Apr 26 04:28:35 192.168.122.209 [44665.692723] RIP: 0010:tfw_cache_build_resp_stale+0x1/0xb0 [tempesta_fw] Apr 26 04:28:35 192.168.122.209 [44665.693315] Code: e8 94 9e 86 f3 44 3b 6b 24 0f 82 11 ff ff ff e9 9e fb ff ff e8 40 0f 70 f4 e9 a1 ee 0e 00 66 66 2e 0f 1f 84 00 00 00 00 00 e8 <5b> 4c ab ff 55 48 89 e5 41 57 41 56 41 55 41 54 53 48 89 fb 48 8d Apr 26 04:28:35 192.168.122.209 [44665.694934] RSP: 0018:ffff888147e092e8 EFLAGS: 00000246 ORIG_RAX: 0000000000000000 Apr 26 04:28:35 192.168.122.209 [44665.695601] RAX: 0000000000000000 RBX: ffff88805e440020 RCX: ffffffffc1c4c4d6 Apr 26 04:28:35 192.168.122.209 [44665.696233] RDX: dffffc0000000000 RSI: 0000000000000008 RDI: ffff8880435ab020 Apr 26 04:28:35 192.168.122.209 [44665.696866] RBP: ffff888147e09320 R08: 0000000000000000 R09: ffff88810938d1bf Apr 26 04:28:35 192.168.122.209 [44665.697505] R10: ffffed1021271a37 R11: 0000000000000001 R12: ffff8880435ab020 Apr 26 04:28:35 192.168.122.209 [44665.698134] R13: ffff8880435ab0d8 R14: ffff8880435ab058 R15: ffff88805e440058 Apr 26 04:28:35 192.168.122.209 [44665.698786] ? __tfw_http_resp_fwd_stale+0x36/0x160 [tempesta_fw] Apr 26 04:28:35 192.168.122.209 [44665.699352] ? tfw_cache_build_resp_stale+0x5/0xb0 [tempesta_fw] Apr 26 04:28:35 192.168.122.209 [44665.699920] ? __tfw_http_resp_fwd_stale+0x47/0x160 [tempesta_fw] Apr 26 04:28:35 192.168.122.209 [44665.700491] ? tfw_cache_build_resp_stale+0x5/0xb0 [tempesta_fw] Apr 26 04:28:35 192.168.122.209 [44665.701048] ? __tfw_http_resp_fwd_stale+0x47/0x160 [tempesta_fw] Apr 26 04:28:35 192.168.122.209 [44665.701612] tfw_http_msg_process_generic+0xb6b/0xc70 [tempesta_fw] Apr 26 04:28:35 192.168.122.209 [44665.702200] ? tfw_http_req_process+0x11a0/0x11a0 [tempesta_fw] Apr 26 04:28:35 192.168.122.209 [44665.702727] ? __kasan_check_write+0x14/0x20 Apr 26 04:28:35 192.168.122.209 [44665.703119] ? pg_skb_alloc+0x60e/0x680 Apr 26 04:28:35 192.168.122.209 [44665.703464] ? __kasan_check_write+0x14/0x20 Apr 26 04:28:35 192.168.122.209 [44665.703851] ? __alloc_skb+0x278/0x350 Apr 26 04:28:35 192.168.122.209 [44665.704194] ? __kasan_check_write+0x14/0x20 Apr 26 04:28:35 192.168.122.209 [44665.704603] ? __coalesce_frag+0x136/0x370 [tempesta_fw] Apr 26 04:28:35 192.168.122.209 [44665.705104] tfw_http_msg_process+0x80/0xc0 [tempesta_fw] Apr 26 04:28:35 192.168.122.209 [44665.705586] ? skb_release_data+0x8c/0x320 Apr 26 04:28:35 192.168.122.209 [44665.705983] tfw_connection_recv+0x12e/0x250 [tempesta_fw] Apr 26 04:28:35 192.168.122.209 [44665.706493] ? tfw_connection_send+0x70/0x70 [tempesta_fw] Apr 26 04:28:35 192.168.122.209 [44665.707010] ? ss_skb_unroll+0x3d6/0x540 [tempesta_fw] Apr 26 04:28:35 192.168.122.209 [44665.707499] ss_tcp_process_data+0x436/0x8b0 [tempesta_fw] Apr 26 04:28:35 192.168.122.209 [44665.708017] ? __sk_close_locked+0x100/0x100 [tempesta_fw] Apr 26 04:28:35 192.168.122.209 [44665.708530] ss_tcp_data_ready+0x7b/0x150 [tempesta_fw] Apr 26 04:28:35 192.168.122.209 [44665.709003] tcp_data_ready+0x73/0x210 Apr 26 04:28:35 192.168.122.209 [44665.709344] tcp_data_queue+0x1085/0x1d80 Apr 26 04:28:35 192.168.122.209 [44665.709705] ? tcp_validate_incoming+0x1fa/0xa30 Apr 26 04:28:35 192.168.122.209 [44665.710123] ? tcp_data_ready+0x210/0x210 Apr 26 04:28:35 192.168.122.209 [44665.710483] ? tcp_enter_cwr+0x1c0/0x1c0 Apr 26 04:28:35 192.168.122.209 [44665.710844] ? kvm_clock_get_cycles+0x11/0x20 Apr 26 04:28:35 192.168.122.209 [44665.711245] ? ktime_get+0x4f/0xb0 Apr 26 04:28:35 192.168.122.209 [44665.711554] tcp_rcv_established+0x422/0xb40 Apr 26 04:28:35 192.168.122.209 [44665.711935] ? tcp_parse_md5sig_option+0x20/0xb0 Apr 26 04:28:35 192.168.122.209 [44665.712354] ? tcp_data_queue+0x1d80/0x1d80 Apr 26 04:28:35 192.168.122.209 [44665.712731] ? __kasan_check_read+0x11/0x20 Apr 26 04:28:35 192.168.122.209 [44665.713111] tcp_v4_do_rcv+0x25f/0x360 Apr 26 04:28:35 192.168.122.209 [44665.713450] tcp_v4_rcv+0x1600/0x1770 Apr 26 04:28:35 192.168.122.209 [44665.713784] ? tcp_v4_early_demux+0x2f0/0x2f0 Apr 26 04:28:35 192.168.122.209 [44665.714182] ip_protocol_deliver_rcu+0x46/0x2e0 Apr 26 04:28:35 192.168.122.209 [44665.714590] ip_local_deliver_finish+0xc6/0xe0 Apr 26 04:28:35 192.168.122.209 [44665.714989] ip_local_deliver+0x1f5/0x210 Apr 26 04:28:35 192.168.122.209 [44665.715352] ? ip_local_deliver_finish+0xe0/0xe0 Apr 26 04:28:35 192.168.122.209 [44665.715777] ? nf_nat_inet_fn+0x2b3/0x440 [nf_nat] Apr 26 04:28:35 192.168.122.209 [44665.716210] ? ip_protocol_deliver_rcu+0x2e0/0x2e0 Apr 26 04:28:35 192.168.122.209 [44665.716637] ? ip_rcv_finish_core.constprop.0+0x17c/0x890 Apr 26 04:28:35 192.168.122.209 [44665.717139] ip_rcv_finish+0xcf/0xf0 Apr 26 04:28:35 192.168.122.209 [44665.717463] ip_rcv+0x16d/0x180 Apr 26 04:28:35 192.168.122.209 [44665.717749] ? ip_local_deliver+0x210/0x210 Apr 26 04:28:35 192.168.122.209 [44665.718132] ? ip_rcv_finish_core.constprop.0+0x890/0x890 Apr 26 04:28:35 192.168.122.209 [44665.718615] ? ttwu_do_activate+0xa4/0x170 Apr 26 04:28:35 192.168.122.209 [44665.718987] ? ip_local_deliver+0x210/0x210 Apr 26 04:28:35 192.168.122.209 [44665.719363] __netif_receive_skb_one_core+0x132/0x140 Apr 26 04:28:35 192.168.122.209 [44665.719813] ? napi_gro_receive+0x260/0x260 Apr 26 04:28:35 192.168.122.209 [44665.720198] ? __kasan_check_write+0x14/0x20 Apr 26 04:28:35 192.168.122.209 [44665.720584] ? _raw_spin_lock+0x7b/0xd0 Apr 26 04:28:35 192.168.122.209 [44665.720932] __netif_receive_skb+0x26/0xb0 Apr 26 04:28:35 192.168.122.209 [44665.721306] process_backlog+0xfe/0x290 Apr 26 04:28:35 192.168.122.209 [44665.721657] net_rx_action+0x287/0x6b0 Apr 26 04:28:35 192.168.122.209 [44665.722002] ? napi_complete_done+0x2c0/0x2c0 Apr 26 04:28:35 192.168.122.209 [44665.722393] ? switch_fpu_return+0x120/0x120 Apr 26 04:28:35 192.168.122.209 [44665.722779] __do_softirq+0xfe/0x383 Apr 26 04:28:35 192.168.122.209 [44665.723111] asm_call_irq_on_stack+0xf/0x20 Apr 26 04:28:35 192.168.122.209 [44665.723488] Apr 26 04:28:35 192.168.122.209 [44665.723687] do_softirq_own_stack+0x3d/0x50 Apr 26 04:28:35 192.168.122.209 [44665.724068] do_softirq+0x72/0x90 Apr 26 04:28:35 192.168.122.209 [44665.724375] __local_bh_enable_ip+0x50/0x60 Apr 26 04:28:35 192.168.122.209 [44665.724752] ip_finish_output2+0x351/0xa80 Apr 26 04:28:35 192.168.122.209 [44665.725127] ? __ip_flush_pending_frames.constprop.0+0x130/0x130 Apr 26 04:28:35 192.168.122.209 [44665.725663] ? cgroup_bpf_release+0x400/0x400 Apr 26 04:28:35 192.168.122.209 [44665.726063] __ip_finish_output+0x16b/0x340 Apr 26 04:28:35 192.168.122.209 [44665.726462] ip_finish_output+0x2d/0xe0 Apr 26 04:28:35 192.168.122.209 [44665.726810] ip_output+0x133/0x210 Apr 26 04:28:35 192.168.122.209 [44665.727130] ? ip_mc_output+0x4e0/0x4e0 Apr 26 04:28:35 192.168.122.209 [44665.727500] ? __ip_finish_output+0x340/0x340 Apr 26 04:28:35 192.168.122.209 [44665.727892] ? ipv4_dst_check+0x6d/0xa0 Apr 26 04:28:35 192.168.122.209 [44665.728245] __ip_queue_xmit+0x356/0x7d0 Apr 26 04:28:35 192.168.122.209 [44665.728600] ip_queue_xmit+0x3b/0x50 Apr 26 04:28:35 192.168.122.209 [44665.728928] __tcp_transmit_skb+0x152f/0x1730 Apr 26 04:28:35 192.168.122.209 [44665.729325] ? __tcp_select_window+0x370/0x370 Apr 26 04:28:35 192.168.122.209 [44665.729724] ? pvclock_clocksource_read+0xe1/0x1a0 Apr 26 04:28:35 192.168.122.209 [44665.730155] ? __kasan_check_read+0x11/0x20 Apr 26 04:28:35 192.168.122.209 [44665.730533] tcp_write_xmit+0x796/0x2a50 Apr 26 04:28:35 192.168.122.209 [44665.730886] ? iov_iter_advance+0x12b/0x5f0 Apr 26 04:28:35 192.168.122.209 [44665.731265] __tcp_push_pending_frames+0x5f/0x1a0 Apr 26 04:28:35 192.168.122.209 [44665.731684] tcp_push+0x209/0x2b0 Apr 26 04:28:35 192.168.122.209 [44665.731993] tcp_sendmsg_locked+0x13fa/0x15f0 Apr 26 04:28:35 192.168.122.209 [44665.732384] ? skb_do_copy_data_nocache+0x1b0/0x1b0 Apr 26 04:28:35 192.168.122.209 [44665.732817] ? __kasan_check_write+0x14/0x20 Apr 26 04:28:35 192.168.122.209 [44665.733206] ? _raw_spin_lock_bh+0x86/0xe0 Apr 26 04:28:35 192.168.122.209 [44665.733578] ? __x64_sys_poll+0x250/0x250 Apr 26 04:28:35 192.168.122.209 [44665.733937] ? __kasan_check_write+0x14/0x20 Apr 26 04:28:35 192.168.122.209 [44665.734324] tcp_sendmsg+0x2d/0x50 Apr 26 04:28:35 192.168.122.209 [44665.734634] inet_sendmsg+0x64/0xa0 Apr 26 04:28:35 192.168.122.209 [44665.734957] ? inet_send_prepare+0x120/0x120 Apr 26 04:28:35 192.168.122.209 [44665.735342] sock_sendmsg+0x97/0xa0 Apr 26 04:28:35 192.168.122.209 [44665.735660] __sys_sendto+0x1ab/0x260 Apr 26 04:28:35 192.168.122.209 [44665.735994] ? __ia32_sys_getpeername+0x50/0x50 Apr 26 04:28:35 192.168.122.209 [44665.736415] ? clear_user+0x25/0x30 Apr 26 04:28:35 192.168.122.209 [44665.736732] ? __x64_sys_rseq+0x260/0x260 Apr 26 04:28:35 192.168.122.209 [44665.737096] ? mem_cgroup_handle_over_high+0x87/0x430 Apr 26 04:28:35 192.168.122.209 [44665.737545] ? __blkcg_punt_bio_submit+0xe0/0xe0 Apr 26 04:28:35 192.168.122.209 [44665.737966] __x64_sys_sendto+0x7f/0x90 Apr 26 04:28:35 192.168.122.209 [44665.738317] do_syscall_64+0x38/0x90 Apr 26 04:28:35 192.168.122.209 [44665.738640] entry_SYSCALL_64_after_hwframe+0x44/0xa9 Apr 26 04:28:35 192.168.122.209 [44665.739095] RIP: 0033:0x7f88f226aefa Apr 26 04:28:35 192.168.122.209 [44665.739423] Code: e0 89 7d e8 89 4d d4 e8 74 c6 f6 ff 44 8b 55 d4 48 8b 55 d8 45 31 c9 89 c3 48 8b 75 e0 8b 7d e8 45 31 c0 b8 2c 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 36 89 df 48 89 45 e8 e8 c3 c6 f6 ff 48 8b 45 Apr 26 04:28:35 192.168.122.209 [44665.741063] RSP: 002b:00007f88ed97cd80 EFLAGS: 00000246 ORIG_RAX: 000000000000002c Apr 26 04:28:35 192.168.122.209 [44665.741732] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f88f226aefa Apr 26 04:28:35 192.168.122.209 [44665.742361] RDX: 000000000000005d RSI: 00007f88ec8e4c50 RDI: 0000000000000027 Apr 26 04:28:35 192.168.122.209 [44665.742996] RBP: 00007f88ed97cdb0 R08: 0000000000000000 R09: 0000000000000000 Apr 26 04:28:35 192.168.122.209 [44665.743619] R10: 0000000000000000 R11: 0000000000000246 R12: 00007f88e6fe95a0 Apr 26 04:28:35 192.168.122.209 [44665.744243] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 Apr 26 04:28:35 192.168.122.209 [44665.744902] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 04:28:35 192.168.122.209 [44666.209350] [tdb] Close table 'client0.tdb' Apr 26 04:28:36 192.168.122.209 [44666.428054] [tdb] Close table 'sessions0.tdb' Apr 26 04:28:39 192.168.122.209 [44669.577101] [tdb] Close table 'cache0.tdb' Apr 26 04:28:39 192.168.122.209 [44669.828257] [tdb] Close table 'filter0.tdb' Apr 26 04:28:39 192.168.122.209 [44669.828685] [tempesta fw] modules are stopped Apr 26 04:28:39 192.168.122.209 [44670.013802] [tempesta fw] exiting... Apr 26 04:28:39 192.168.122.209 [44670.155056] [tdb] Shutdown Tempesta DB Apr 26 04:28:39 192.168.122.209 [44670.361355] End test: t_fault_injection.test_fault_injection_base.TestFailFunctionStaleFwd.test_tfw_http_resp_do_fwd_stale_invalid_resp_http Apr 26 04:28:40 192.168.122.209 [44670.381383] Start test: t_fault_injection.test_fault_injection_base.TestFailFunctionStaleFwd.test_tfw_http_resp_do_fwd_stale_noresp_h2 Apr 26 04:28:41 192.168.122.209 [44671.616143] [tdb] Start Tempesta DB Apr 26 04:28:41 192.168.122.209 [44671.755332] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:28:42 192.168.122.209 [44673.140533] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44673.140533] Maybe that's fine, but it's worth checking the [44673.140533] config - if there is no relations between the [44673.140533] names, then host name confusion attack is possible. Apr 26 04:28:42 192.168.122.209 [44673.315278] [tempesta fw] Configuration processing is completed. Apr 26 04:28:43 192.168.122.209 [44673.382034] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:28:43 192.168.122.209 [44673.839059] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:28:43 192.168.122.209 [44673.870030] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:28:43 192.168.122.209 [44673.905895] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:28:43 192.168.122.209 [44673.959614] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:28:43 192.168.122.209 [44673.961457] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:28:43 192.168.122.209 [44674.027226] [tempesta fw] Tempesta FW is ready Apr 26 04:28:46 192.168.122.209 [44677.339266] [tempesta fw] Warning: request evicted: the number of retries exceeded, status 504: 127.0.0.2 Apr 26 04:28:46 192.168.122.209 [44677.340156] FAULT_INJECTION: forcing a failure. [44677.340156] name fail_function, interval 0, probability 100, space 0, times -1 Apr 26 04:28:46 192.168.122.209 [44677.341186] CPU: 1 PID: 20 Comm: ksoftirqd/1 Tainted: G OE 5.10.35.tfw-39c65d3-debug #1 Apr 26 04:28:46 192.168.122.209 [44677.341998] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 Apr 26 04:28:46 192.168.122.209 [44677.342820] Call Trace: Apr 26 04:28:46 192.168.122.209 [44677.343067] dump_stack+0x96/0xc4 Apr 26 04:28:46 192.168.122.209 [44677.343379] should_fail.cold+0x5/0xa Apr 26 04:28:46 192.168.122.209 [44677.343723] fei_kprobe_handler+0x23/0x60 Apr 26 04:28:46 192.168.122.209 [44677.344118] ? tfw_cache_build_resp_stale+0x1/0xb0 [tempesta_fw] Apr 26 04:28:46 192.168.122.209 [44677.344653] kprobe_ftrace_handler+0xbe/0x150 Apr 26 04:28:46 192.168.122.209 [44677.345069] ? tfw_cache_build_resp_stale+0x5/0xb0 [tempesta_fw] Apr 26 04:28:46 192.168.122.209 [44677.345637] ? tfw_http_send_err_resp+0xa8/0x220 [tempesta_fw] Apr 26 04:28:46 192.168.122.209 [44677.346157] ftrace_ops_assist_func+0xef/0x1b0 Apr 26 04:28:46 192.168.122.209 [44677.346577] ? tfw_cache_build_resp+0xb30/0xb30 [tempesta_fw] Apr 26 04:28:46 192.168.122.209 [44677.347092] 0xffffffffc16e00e3 Apr 26 04:28:46 192.168.122.209 [44677.347412] RIP: 0010:tfw_cache_build_resp_stale+0x1/0xb0 [tempesta_fw] Apr 26 04:28:46 192.168.122.209 [44677.347993] Code: e8 94 9e 86 f3 44 3b 6b 24 0f 82 11 ff ff ff e9 9e fb ff ff e8 40 0f 70 f4 e9 a1 ee 0e 00 66 66 2e 0f 1f 84 00 00 00 00 00 e8 <5b> 4c ab ff 55 48 89 e5 41 57 41 56 41 55 41 54 53 48 89 fb 48 8d Apr 26 04:28:46 192.168.122.209 [44677.349671] RSP: 0018:ffff888100f8f2f0 EFLAGS: 00000202 ORIG_RAX: 0000000000000000 Apr 26 04:28:46 192.168.122.209 [44677.350354] RAX: 0000000000000001 RBX: ffff88800dafa020 RCX: ffffffffc1c44221 Apr 26 04:28:46 192.168.122.209 [44677.350988] RDX: ffffed1020d9b238 RSI: 0000000000000008 RDI: ffff88800dafa020 Apr 26 04:28:46 192.168.122.209 [44677.351613] RBP: ffff888100f8f3c0 R08: 0000000000000000 R09: ffff888106cd91bf Apr 26 04:28:46 192.168.122.209 [44677.352240] R10: ffffed1020d9b237 R11: 0000000000000001 R12: 1ffff110201f1e5f Apr 26 04:28:46 192.168.122.209 [44677.352862] R13: 00000000000001f8 R14: ffffffffc1d2e1a0 R15: ffff88805e44f9e8 Apr 26 04:28:46 192.168.122.209 [44677.353534] ? tfw_http_resp_should_fwd_stale+0x91/0xd0 [tempesta_fw] Apr 26 04:28:46 192.168.122.209 [44677.354129] ? tfw_cache_build_resp_stale+0x5/0xb0 [tempesta_fw] Apr 26 04:28:46 192.168.122.209 [44677.354682] ? tfw_http_send_err_resp+0xa8/0x220 [tempesta_fw] Apr 26 04:28:46 192.168.122.209 [44677.355221] ? tfw_cache_build_resp_stale+0x5/0xb0 [tempesta_fw] Apr 26 04:28:46 192.168.122.209 [44677.355777] ? tfw_http_send_err_resp+0xa8/0x220 [tempesta_fw] Apr 26 04:28:46 192.168.122.209 [44677.356325] ? tfw_http_cli_error_resp_and_log+0x7f0/0x7f0 [tempesta_fw] Apr 26 04:28:46 192.168.122.209 [44677.356921] ? __kasan_check_read+0x11/0x20 Apr 26 04:28:46 192.168.122.209 [44677.357326] tfw_http_req_zap_error+0x93/0x1b0 [tempesta_fw] Apr 26 04:28:46 192.168.122.209 [44677.357858] tfw_http_conn_repair+0x5d2/0x1700 [tempesta_fw] Apr 26 04:28:46 192.168.122.209 [44677.358364] ? tcp_metrics_nl_cmd_get+0x430/0x430 Apr 26 04:28:46 192.168.122.209 [44677.358824] ? tfw_http_conn_release+0x530/0x530 [tempesta_fw] Apr 26 04:28:46 192.168.122.209 [44677.359364] ? memset+0x3c/0x50 Apr 26 04:28:46 192.168.122.209 [44677.359679] ? tfw_gfsm_state_init+0x50/0x60 [tempesta_fw] Apr 26 04:28:46 192.168.122.209 [44677.360206] tfw_connection_repair+0x51/0x60 [tempesta_fw] Apr 26 04:28:46 192.168.122.209 [44677.360723] tfw_sock_srv_connect_complete+0x1fe/0x210 [tempesta_fw] Apr 26 04:28:46 192.168.122.209 [44677.361346] ? tfw_cfgop_out_sched+0x50/0x50 [tempesta_fw] Apr 26 04:28:46 192.168.122.209 [44677.361870] ss_tcp_state_change+0x162/0x310 [tempesta_fw] Apr 26 04:28:46 192.168.122.209 [44677.362365] tcp_rcv_state_process+0xbc3/0x1cb0 Apr 26 04:28:46 192.168.122.209 [44677.362800] ? tcp_finish_connect+0x1f0/0x1f0 Apr 26 04:28:46 192.168.122.209 [44677.363195] ? sk_filter_trim_cap+0x1fd/0x430 Apr 26 04:28:46 192.168.122.209 [44677.363599] ? tcp_parse_md5sig_option+0x79/0xb0 Apr 26 04:28:46 192.168.122.209 [44677.364027] ? __kasan_check_write+0x14/0x20 Apr 26 04:28:46 192.168.122.209 [44677.364438] ? _raw_spin_lock+0x7b/0xd0 Apr 26 04:28:46 192.168.122.209 [44677.364791] tcp_v4_do_rcv+0x164/0x360 Apr 26 04:28:46 192.168.122.209 [44677.365156] tcp_v4_rcv+0x1600/0x1770 Apr 26 04:28:46 192.168.122.209 [44677.365487] ? tcp_v4_early_demux+0x2f0/0x2f0 Apr 26 04:28:46 192.168.122.209 [44677.365881] ip_protocol_deliver_rcu+0x46/0x2e0 Apr 26 04:28:46 192.168.122.209 [44677.366290] ip_local_deliver_finish+0xc6/0xe0 Apr 26 04:28:46 192.168.122.209 [44677.366690] ip_local_deliver+0x1f5/0x210 Apr 26 04:28:46 192.168.122.209 [44677.367048] ? ip_local_deliver_finish+0xe0/0xe0 Apr 26 04:28:46 192.168.122.209 [44677.367468] ? nf_nat_inet_fn+0x2b3/0x440 [nf_nat] Apr 26 04:28:46 192.168.122.209 [44677.367896] ? ip_protocol_deliver_rcu+0x2e0/0x2e0 Apr 26 04:28:46 192.168.122.209 [44677.368332] ? ip_rcv_finish_core.constprop.0+0x17c/0x890 Apr 26 04:28:46 192.168.122.209 [44677.368810] ip_rcv_finish+0xcf/0xf0 Apr 26 04:28:46 192.168.122.209 [44677.369138] ip_rcv+0x16d/0x180 Apr 26 04:28:47 192.168.122.209 [44677.369425] ? ip_local_deliver+0x210/0x210 Apr 26 04:28:47 192.168.122.209 [44677.369802] ? __kasan_check_write+0x14/0x20 Apr 26 04:28:47 192.168.122.209 [44677.370191] ? _raw_spin_lock+0x7b/0xd0 Apr 26 04:28:47 192.168.122.209 [44677.370539] ? ip_rcv_finish_core.constprop.0+0x890/0x890 Apr 26 04:28:47 192.168.122.209 [44677.371021] ? __update_load_avg_cfs_rq+0x1dd/0x5f0 Apr 26 04:28:47 192.168.122.209 [44677.371466] ? __asan_loadN+0xf/0x20 Apr 26 04:28:47 192.168.122.209 [44677.371791] ? ip_local_deliver+0x210/0x210 Apr 26 04:28:47 192.168.122.209 [44677.372172] __netif_receive_skb_one_core+0x132/0x140 Apr 26 04:28:47 192.168.122.209 [44677.372624] ? napi_gro_receive+0x260/0x260 Apr 26 04:28:47 192.168.122.209 [44677.373005] ? __kasan_check_write+0x14/0x20 Apr 26 04:28:47 192.168.122.209 [44677.373393] ? _raw_spin_lock+0x7b/0xd0 Apr 26 04:28:47 192.168.122.209 [44677.373742] __netif_receive_skb+0x26/0xb0 Apr 26 04:28:47 192.168.122.209 [44677.374119] process_backlog+0xfe/0x290 Apr 26 04:28:47 192.168.122.209 [44677.374470] net_rx_action+0x287/0x6b0 Apr 26 04:28:47 192.168.122.209 [44677.374809] ? napi_complete_done+0x2c0/0x2c0 Apr 26 04:28:47 192.168.122.209 [44677.375204] ? switch_fpu_return+0x120/0x120 Apr 26 04:28:47 192.168.122.209 [44677.375590] ? io_schedule_timeout+0xc0/0xc0 Apr 26 04:28:47 192.168.122.209 [44677.375976] __do_softirq+0xfe/0x383 Apr 26 04:28:47 192.168.122.209 [44677.376306] ? tasklet_hi_action+0x30/0x30 Apr 26 04:28:47 192.168.122.209 [44677.376674] run_ksoftirqd+0x2b/0x40 Apr 26 04:28:47 192.168.122.209 [44677.376998] smpboot_thread_fn+0x1ba/0x2f0 Apr 26 04:28:47 192.168.122.209 [44677.377375] ? smpboot_register_percpu_thread+0x190/0x190 Apr 26 04:28:47 192.168.122.209 [44677.377853] ? __kasan_check_read+0x11/0x20 Apr 26 04:28:47 192.168.122.209 [44677.378234] ? __kthread_parkme+0x83/0xa0 Apr 26 04:28:47 192.168.122.209 [44677.378595] ? smpboot_register_percpu_thread+0x190/0x190 Apr 26 04:28:47 192.168.122.209 [44677.379077] kthread+0x1d9/0x200 Apr 26 04:28:47 192.168.122.209 [44677.379377] ? __kthread_bind_mask+0x70/0x70 Apr 26 04:28:47 192.168.122.209 [44677.379764] ret_from_fork+0x1f/0x30 Apr 26 04:28:47 192.168.122.209 [44677.849333] [tdb] Close table 'client0.tdb' Apr 26 04:28:47 192.168.122.209 [44678.050686] [tdb] Close table 'sessions0.tdb' Apr 26 04:28:50 192.168.122.209 [44681.312423] [tdb] Close table 'cache0.tdb' Apr 26 04:28:51 192.168.122.209 [44681.554745] [tdb] Close table 'filter0.tdb' Apr 26 04:28:51 192.168.122.209 [44681.555570] [tempesta fw] modules are stopped Apr 26 04:28:51 192.168.122.209 [44681.786637] [tempesta fw] exiting... Apr 26 04:28:51 192.168.122.209 [44681.920650] [tdb] Shutdown Tempesta DB Apr 26 04:28:51 192.168.122.209 [44682.140721] End test: t_fault_injection.test_fault_injection_base.TestFailFunctionStaleFwd.test_tfw_http_resp_do_fwd_stale_noresp_h2 Apr 26 04:28:51 192.168.122.209 [44682.155841] Start test: t_fault_injection.test_fault_injection_base.TestFailFunctionStaleFwd.test_tfw_http_resp_do_fwd_stale_noresp_http Apr 26 04:28:52 192.168.122.209 [44683.359274] [tdb] Start Tempesta DB Apr 26 04:28:53 192.168.122.209 [44683.519402] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:28:54 192.168.122.209 [44685.004773] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44685.004773] Maybe that's fine, but it's worth checking the [44685.004773] config - if there is no relations between the [44685.004773] names, then host name confusion attack is possible. Apr 26 04:28:54 192.168.122.209 [44685.175835] [tempesta fw] Configuration processing is completed. Apr 26 04:28:54 192.168.122.209 [44685.227640] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:28:55 192.168.122.209 [44685.656065] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:28:55 192.168.122.209 [44685.683390] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:28:55 192.168.122.209 [44685.715587] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:28:55 192.168.122.209 [44685.775418] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:28:55 192.168.122.209 [44685.777168] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:28:55 192.168.122.209 [44685.827366] [tempesta fw] Tempesta FW is ready Apr 26 04:28:58 192.168.122.209 [44689.155680] [tempesta fw] Warning: request evicted: the number of retries exceeded, status 504: 127.0.0.2 Apr 26 04:28:58 192.168.122.209 [44689.158365] FAULT_INJECTION: forcing a failure. [44689.158365] name fail_function, interval 0, probability 100, space 0, times -1 Apr 26 04:28:58 192.168.122.209 [44689.161634] CPU: 3 PID: 0 Comm: swapper/3 Tainted: G OE 5.10.35.tfw-39c65d3-debug #1 Apr 26 04:28:58 192.168.122.209 [44689.163567] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 Apr 26 04:28:58 192.168.122.209 [44689.165446] Call Trace: Apr 26 04:28:58 192.168.122.209 [44689.165966] Apr 26 04:28:58 192.168.122.209 [44689.166450] dump_stack+0x96/0xc4 Apr 26 04:28:58 192.168.122.209 [44689.167149] should_fail.cold+0x5/0xa Apr 26 04:28:58 192.168.122.209 [44689.167951] fei_kprobe_handler+0x23/0x60 Apr 26 04:28:58 192.168.122.209 [44689.168848] ? tfw_cache_build_resp_stale+0x1/0xb0 [tempesta_fw] Apr 26 04:28:58 192.168.122.209 [44689.170092] kprobe_ftrace_handler+0xbe/0x150 Apr 26 04:28:58 192.168.122.209 [44689.171058] ? tfw_cache_build_resp_stale+0x5/0xb0 [tempesta_fw] Apr 26 04:28:58 192.168.122.209 [44689.172135] ? tfw_http_send_err_resp+0xa8/0x220 [tempesta_fw] Apr 26 04:28:58 192.168.122.209 [44689.172655] ftrace_ops_assist_func+0xef/0x1b0 Apr 26 04:28:58 192.168.122.209 [44689.173075] ? tfw_cache_build_resp+0xb30/0xb30 [tempesta_fw] Apr 26 04:28:58 192.168.122.209 [44689.173593] 0xffffffffc16e00e3 Apr 26 04:28:58 192.168.122.209 [44689.173907] RIP: 0010:tfw_cache_build_resp_stale+0x1/0xb0 [tempesta_fw] Apr 26 04:28:58 192.168.122.209 [44689.174490] Code: e8 94 9e 86 f3 44 3b 6b 24 0f 82 11 ff ff ff e9 9e fb ff ff e8 40 0f 70 f4 e9 a1 ee 0e 00 66 66 2e 0f 1f 84 00 00 00 00 00 e8 <5b> 4c ab ff 55 48 89 e5 41 57 41 56 41 55 41 54 53 48 89 fb 48 8d Apr 26 04:28:58 192.168.122.209 [44689.176108] RSP: 0018:ffff888147f89470 EFLAGS: 00000202 ORIG_RAX: 0000000000000000 Apr 26 04:28:58 192.168.122.209 [44689.176805] RAX: 0000000000000001 RBX: ffff88804a985020 RCX: ffffffffc1c44221 Apr 26 04:28:58 192.168.122.209 [44689.177438] RDX: ffffed10213d93c0 RSI: 0000000000000008 RDI: ffff88804a985020 Apr 26 04:28:58 192.168.122.209 [44689.178058] RBP: ffff888147f89540 R08: 0000000000000000 R09: ffff888109ec9dff Apr 26 04:28:58 192.168.122.209 [44689.178685] R10: ffffed10213d93bf R11: 0000000000000001 R12: 1ffff11028ff128f Apr 26 04:28:58 192.168.122.209 [44689.179311] R13: 00000000000001f8 R14: ffffffffc1d2e1a0 R15: ffff88802f2c8008 Apr 26 04:28:58 192.168.122.209 [44689.179963] ? tfw_http_resp_should_fwd_stale+0x91/0xd0 [tempesta_fw] Apr 26 04:28:58 192.168.122.209 [44689.180557] ? tfw_cache_build_resp_stale+0x5/0xb0 [tempesta_fw] Apr 26 04:28:58 192.168.122.209 [44689.181112] ? tfw_http_send_err_resp+0xa8/0x220 [tempesta_fw] Apr 26 04:28:58 192.168.122.209 [44689.181658] ? tfw_cache_build_resp_stale+0x5/0xb0 [tempesta_fw] Apr 26 04:28:58 192.168.122.209 [44689.182212] ? tfw_http_send_err_resp+0xa8/0x220 [tempesta_fw] Apr 26 04:28:58 192.168.122.209 [44689.182756] ? tfw_http_cli_error_resp_and_log+0x7f0/0x7f0 [tempesta_fw] Apr 26 04:28:58 192.168.122.209 [44689.183360] ? __kasan_check_read+0x11/0x20 Apr 26 04:28:58 192.168.122.209 [44689.183788] tfw_http_req_zap_error+0x93/0x1b0 [tempesta_fw] Apr 26 04:28:58 192.168.122.209 [44689.184337] tfw_http_conn_repair+0x5d2/0x1700 [tempesta_fw] Apr 26 04:28:58 192.168.122.209 [44689.184866] ? tcp_metrics_nl_cmd_get+0x430/0x430 Apr 26 04:28:58 192.168.122.209 [44689.185318] ? tfw_http_conn_release+0x530/0x530 [tempesta_fw] Apr 26 04:28:58 192.168.122.209 [44689.185839] ? memset+0x3c/0x50 Apr 26 04:28:58 192.168.122.209 [44689.186152] ? tfw_gfsm_state_init+0x50/0x60 [tempesta_fw] Apr 26 04:28:58 192.168.122.209 [44689.186667] tfw_connection_repair+0x51/0x60 [tempesta_fw] Apr 26 04:28:58 192.168.122.209 [44689.187182] tfw_sock_srv_connect_complete+0x1fe/0x210 [tempesta_fw] Apr 26 04:28:58 192.168.122.209 [44689.187780] ? tfw_cfgop_out_sched+0x50/0x50 [tempesta_fw] Apr 26 04:28:58 192.168.122.209 [44689.188300] ss_tcp_state_change+0x162/0x310 [tempesta_fw] Apr 26 04:28:58 192.168.122.209 [44689.188788] tcp_rcv_state_process+0xbc3/0x1cb0 Apr 26 04:28:58 192.168.122.209 [44689.189193] ? inet_ehashfn+0x69/0x1a0 Apr 26 04:28:58 192.168.122.209 [44689.189539] ? tcp_finish_connect+0x1f0/0x1f0 Apr 26 04:28:58 192.168.122.209 [44689.189936] ? sk_filter_trim_cap+0x1fd/0x430 Apr 26 04:28:58 192.168.122.209 [44689.190330] ? tcp_parse_md5sig_option+0x79/0xb0 Apr 26 04:28:58 192.168.122.209 [44689.190742] ? __kasan_check_write+0x14/0x20 Apr 26 04:28:58 192.168.122.209 [44689.191141] ? _raw_spin_lock+0x7b/0xd0 Apr 26 04:28:58 192.168.122.209 [44689.191493] tcp_v4_do_rcv+0x164/0x360 Apr 26 04:28:58 192.168.122.209 [44689.191831] tcp_v4_rcv+0x1600/0x1770 Apr 26 04:28:58 192.168.122.209 [44689.192163] ? tcp_v4_early_demux+0x2f0/0x2f0 Apr 26 04:28:58 192.168.122.209 [44689.192560] ip_protocol_deliver_rcu+0x46/0x2e0 Apr 26 04:28:58 192.168.122.209 [44689.192966] ip_local_deliver_finish+0xc6/0xe0 Apr 26 04:28:58 192.168.122.209 [44689.193367] ip_local_deliver+0x1f5/0x210 Apr 26 04:28:58 192.168.122.209 [44689.193729] ? ip_local_deliver_finish+0xe0/0xe0 Apr 26 04:28:58 192.168.122.209 [44689.194144] ? nf_nat_inet_fn+0x2b3/0x440 [nf_nat] Apr 26 04:28:58 192.168.122.209 [44689.194590] ? ip_protocol_deliver_rcu+0x2e0/0x2e0 Apr 26 04:28:58 192.168.122.209 [44689.195015] ? ip_rcv_finish_core.constprop.0+0x17c/0x890 Apr 26 04:28:58 192.168.122.209 [44689.195497] ip_rcv_finish+0xcf/0xf0 Apr 26 04:28:58 192.168.122.209 [44689.195822] ip_rcv+0x16d/0x180 Apr 26 04:28:58 192.168.122.209 [44689.196109] ? ip_local_deliver+0x210/0x210 Apr 26 04:28:58 192.168.122.209 [44689.196487] ? ip_rcv_finish_core.constprop.0+0x890/0x890 Apr 26 04:28:58 192.168.122.209 [44689.196971] ? run_posix_cpu_timers+0x32e/0x3a0 Apr 26 04:28:58 192.168.122.209 [44689.197389] ? posix_cpu_timers_exit_group+0x110/0x110 Apr 26 04:28:58 192.168.122.209 [44689.197845] ? ip_local_deliver+0x210/0x210 Apr 26 04:28:58 192.168.122.209 [44689.198220] __netif_receive_skb_one_core+0x132/0x140 Apr 26 04:28:58 192.168.122.209 [44689.198670] ? napi_gro_receive+0x260/0x260 Apr 26 04:28:58 192.168.122.209 [44689.199045] ? __kasan_check_write+0x14/0x20 Apr 26 04:28:58 192.168.122.209 [44689.199432] ? _raw_spin_lock+0x7b/0xd0 Apr 26 04:28:58 192.168.122.209 [44689.199776] __netif_receive_skb+0x26/0xb0 Apr 26 04:28:58 192.168.122.209 [44689.200142] process_backlog+0xfe/0x290 Apr 26 04:28:58 192.168.122.209 [44689.200494] net_rx_action+0x287/0x6b0 Apr 26 04:28:58 192.168.122.209 [44689.200831] ? napi_complete_done+0x2c0/0x2c0 Apr 26 04:28:58 192.168.122.209 [44689.201221] ? switch_fpu_return+0x120/0x120 Apr 26 04:28:58 192.168.122.209 [44689.201608] __do_softirq+0xfe/0x383 Apr 26 04:28:58 192.168.122.209 [44689.201934] asm_call_irq_on_stack+0xf/0x20 Apr 26 04:28:58 192.168.122.209 [44689.202310] Apr 26 04:28:58 192.168.122.209 [44689.202513] do_softirq_own_stack+0x3d/0x50 Apr 26 04:28:58 192.168.122.209 [44689.202891] irq_exit_rcu+0xc7/0x120 Apr 26 04:28:58 192.168.122.209 [44689.203219] sysvec_call_function_single+0x3a/0x90 Apr 26 04:28:58 192.168.122.209 [44689.203653] asm_sysvec_call_function_single+0x12/0x20 Apr 26 04:28:58 192.168.122.209 [44689.204106] RIP: 0010:native_safe_halt+0xe/0x10 Apr 26 04:28:58 192.168.122.209 [44689.204515] Code: 49 8b 04 24 a8 08 0f 85 71 ff ff ff e9 0f ff ff ff cc cc cc cc cc cc cc cc cc cc cc e9 07 00 00 00 0f 00 2d d4 62 51 00 fb f4 90 e9 07 00 00 00 0f 00 2d c4 62 51 00 f4 c3 cc cc 0f 1f 44 00 Apr 26 04:28:58 192.168.122.209 [44689.206123] RSP: 0018:ffff888100f47db8 EFLAGS: 00000216 Apr 26 04:28:58 192.168.122.209 [44689.206595] RAX: ffffffffb63426a0 RBX: ffff888100f28040 RCX: ffffffffb632c475 Apr 26 04:28:58 192.168.122.209 [44689.207217] RDX: 000000000b3cd15e RSI: 0000000000000004 RDI: ffff888147fb5040 Apr 26 04:28:58 192.168.122.209 [44689.207842] RBP: ffff888100f47dc0 R08: 0000000000000001 R09: ffff888147fb5043 Apr 26 04:28:58 192.168.122.209 [44689.208469] R10: ffffed1028ff6a08 R11: 0000000000000001 R12: 0000000000000003 Apr 26 04:28:58 192.168.122.209 [44689.209108] R13: ffffffffb7ae9360 R14: 0000000000000000 R15: 0000000000000000 Apr 26 04:28:58 192.168.122.209 [44689.209738] ? __cpuidle_text_start+0x8/0x8 Apr 26 04:28:58 192.168.122.209 [44689.210113] ? rcu_eqs_enter.constprop.0+0x85/0xa0 Apr 26 04:28:58 192.168.122.209 [44689.210546] ? default_idle+0xe/0x20 Apr 26 04:28:58 192.168.122.209 [44689.210870] arch_cpu_idle+0x15/0x20 Apr 26 04:28:58 192.168.122.209 [44689.211193] default_idle_call+0x66/0x160 Apr 26 04:28:58 192.168.122.209 [44689.211559] do_idle+0x36f/0x430 Apr 26 04:28:58 192.168.122.209 [44689.211856] ? asm_sysvec_call_function_single+0x12/0x20 Apr 26 04:28:58 192.168.122.209 [44689.212331] ? arch_cpu_idle_exit+0x40/0x40 Apr 26 04:28:58 192.168.122.209 [44689.212793] cpu_startup_entry+0x20/0x30 Apr 26 04:28:58 192.168.122.209 [44689.213147] start_secondary+0x1c1/0x210 Apr 26 04:28:58 192.168.122.209 [44689.213511] ? set_cpu_sibling_map+0xd70/0xd70 Apr 26 04:28:58 192.168.122.209 [44689.213913] ? set_bringup_idt_handler.constprop.0+0x84/0x90 Apr 26 04:28:58 192.168.122.209 [44689.214416] ? start_cpu0+0xc/0xc Apr 26 04:28:58 192.168.122.209 [44689.214718] secondary_startup_64_no_verify+0xb0/0xbb Apr 26 04:28:59 192.168.122.209 [44689.671644] [tdb] Close table 'client0.tdb' Apr 26 04:28:59 192.168.122.209 [44689.860502] [tdb] Close table 'sessions0.tdb' Apr 26 04:29:02 192.168.122.209 [44693.031291] [tdb] Close table 'cache0.tdb' Apr 26 04:29:02 192.168.122.209 [44693.252165] [tdb] Close table 'filter0.tdb' Apr 26 04:29:02 192.168.122.209 [44693.252616] [tempesta fw] modules are stopped Apr 26 04:29:03 192.168.122.209 [44693.453269] [tempesta fw] exiting... Apr 26 04:29:03 192.168.122.209 [44693.608929] [tdb] Shutdown Tempesta DB Apr 26 04:29:03 192.168.122.209 [44693.817745] End test: t_fault_injection.test_fault_injection_base.TestFailFunctionStaleFwd.test_tfw_http_resp_do_fwd_stale_noresp_http Apr 26 04:29:03 192.168.122.209 [44693.831076] Start test: t_frang.test_client_body_and_header_timeout.ClientBodyTimeout.test_timeout_invalid Apr 26 04:29:04 192.168.122.209 [44695.041264] [tdb] Start Tempesta DB Apr 26 04:29:04 192.168.122.209 [44695.181605] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:29:06 192.168.122.209 [44696.740846] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44696.740846] Maybe that's fine, but it's worth checking the [44696.740846] config - if there is no relations between the [44696.740846] names, then host name confusion attack is possible. Apr 26 04:29:06 192.168.122.209 [44696.839593] [tempesta fw] Configuration processing is completed. Apr 26 04:29:06 192.168.122.209 [44696.898152] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:29:06 192.168.122.209 [44696.927658] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:29:06 192.168.122.209 [44696.965802] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:29:06 192.168.122.209 [44697.003568] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:29:06 192.168.122.209 [44697.005276] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:29:06 192.168.122.209 [44697.006907] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:29:06 192.168.122.209 [44697.043515] [tempesta fw] Tempesta FW is ready Apr 26 04:29:08 192.168.122.209 [44698.686538] [tempesta fw] Warning: frang: client body timeout exceeded for 127.0.0.2: 1500 (lim=1000) Apr 26 04:29:08 192.168.122.209 [44698.687401] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:29:08 192.168.122.209 [44699.222075] [tdb] Close table 'client0.tdb' Apr 26 04:29:09 192.168.122.209 [44699.420378] [tdb] Close table 'sessions0.tdb' Apr 26 04:29:09 192.168.122.209 [44699.654281] [tdb] Close table 'filter0.tdb' Apr 26 04:29:09 192.168.122.209 [44699.654736] [tempesta fw] modules are stopped Apr 26 04:29:09 192.168.122.209 [44699.891713] [tempesta fw] exiting... Apr 26 04:29:09 192.168.122.209 [44700.014988] [tdb] Shutdown Tempesta DB Apr 26 04:29:09 192.168.122.209 [44700.266490] End test: t_frang.test_client_body_and_header_timeout.ClientBodyTimeout.test_timeout_invalid Apr 26 04:29:09 192.168.122.209 [44700.286998] Start test: t_frang.test_client_body_and_header_timeout.ClientBodyTimeout.test_timeout_ok Apr 26 04:29:11 192.168.122.209 [44701.469243] [tdb] Start Tempesta DB Apr 26 04:29:11 192.168.122.209 [44701.624292] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:29:12 192.168.122.209 [44702.364870] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44702.364870] Maybe that's fine, but it's worth checking the [44702.364870] config - if there is no relations between the [44702.364870] names, then host name confusion attack is possible. Apr 26 04:29:12 192.168.122.209 [44702.475664] [tempesta fw] Configuration processing is completed. Apr 26 04:29:12 192.168.122.209 [44702.529089] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:29:12 192.168.122.209 [44702.559129] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:29:12 192.168.122.209 [44702.593708] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:29:12 192.168.122.209 [44702.651632] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:29:12 192.168.122.209 [44702.653353] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:29:12 192.168.122.209 [44702.655044] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:29:12 192.168.122.209 [44702.699574] [tempesta fw] Tempesta FW is ready Apr 26 04:29:13 192.168.122.209 [44703.846862] [tdb] Close table 'client0.tdb' Apr 26 04:29:13 192.168.122.209 [44704.036256] [tdb] Close table 'sessions0.tdb' Apr 26 04:29:13 192.168.122.209 [44704.285665] [tdb] Close table 'filter0.tdb' Apr 26 04:29:13 192.168.122.209 [44704.286115] [tempesta fw] modules are stopped Apr 26 04:29:14 192.168.122.209 [44704.501775] [tempesta fw] exiting... Apr 26 04:29:14 192.168.122.209 [44704.617145] [tdb] Shutdown Tempesta DB Apr 26 04:29:14 192.168.122.209 [44704.832573] End test: t_frang.test_client_body_and_header_timeout.ClientBodyTimeout.test_timeout_ok Apr 26 04:29:14 192.168.122.209 [44704.854377] Start test: t_frang.test_client_body_and_header_timeout.ClientBodyTimeoutH2.test_timeout_invalid Apr 26 04:29:15 192.168.122.209 [44705.988570] [tdb] Start Tempesta DB Apr 26 04:29:15 192.168.122.209 [44706.136834] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:29:16 192.168.122.209 [44706.916977] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44706.916977] Maybe that's fine, but it's worth checking the [44706.916977] config - if there is no relations between the [44706.916977] names, then host name confusion attack is possible. Apr 26 04:29:16 192.168.122.209 [44707.035727] [tempesta fw] Configuration processing is completed. Apr 26 04:29:16 192.168.122.209 [44707.088382] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:29:16 192.168.122.209 [44707.120819] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:29:16 192.168.122.209 [44707.150084] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:29:16 192.168.122.209 [44707.199707] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:29:16 192.168.122.209 [44707.201308] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:29:16 192.168.122.209 [44707.202603] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:29:16 192.168.122.209 [44707.251639] [tempesta fw] Tempesta FW is ready Apr 26 04:29:18 192.168.122.209 [44708.875401] [tempesta fw] Warning: frang: client body timeout exceeded for 127.0.0.2: 1492 (lim=1000) Apr 26 04:29:18 192.168.122.209 [44708.877968] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:29:19 192.168.122.209 [44709.389039] [tdb] Close table 'client0.tdb' Apr 26 04:29:19 192.168.122.209 [44709.591162] [tdb] Close table 'sessions0.tdb' Apr 26 04:29:19 192.168.122.209 [44709.831188] [tdb] Close table 'filter0.tdb' Apr 26 04:29:19 192.168.122.209 [44709.831638] [tempesta fw] modules are stopped Apr 26 04:29:19 192.168.122.209 [44710.045644] [tempesta fw] exiting... Apr 26 04:29:19 192.168.122.209 [44710.194781] [tdb] Shutdown Tempesta DB Apr 26 04:29:20 192.168.122.209 [44710.420573] End test: t_frang.test_client_body_and_header_timeout.ClientBodyTimeoutH2.test_timeout_invalid Apr 26 04:29:20 192.168.122.209 [44710.438195] Start test: t_frang.test_client_body_and_header_timeout.ClientBodyTimeoutH2.test_timeout_ok Apr 26 04:29:21 192.168.122.209 [44711.566417] [tdb] Start Tempesta DB Apr 26 04:29:21 192.168.122.209 [44711.716353] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:29:22 192.168.122.209 [44712.452980] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44712.452980] Maybe that's fine, but it's worth checking the [44712.452980] config - if there is no relations between the [44712.452980] names, then host name confusion attack is possible. Apr 26 04:29:22 192.168.122.209 [44712.552080] [tempesta fw] Configuration processing is completed. Apr 26 04:29:22 192.168.122.209 [44712.603054] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:29:22 192.168.122.209 [44712.631992] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:29:22 192.168.122.209 [44712.662446] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:29:22 192.168.122.209 [44712.703771] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:29:22 192.168.122.209 [44712.705455] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:29:22 192.168.122.209 [44712.707163] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:29:22 192.168.122.209 [44712.767725] [tempesta fw] Tempesta FW is ready Apr 26 04:29:23 192.168.122.209 [44713.941465] [tdb] Close table 'client0.tdb' Apr 26 04:29:23 192.168.122.209 [44714.140031] [tdb] Close table 'sessions0.tdb' Apr 26 04:29:24 192.168.122.209 [44714.371912] [tdb] Close table 'filter0.tdb' Apr 26 04:29:24 192.168.122.209 [44714.372348] [tempesta fw] modules are stopped Apr 26 04:29:24 192.168.122.209 [44714.549037] [tempesta fw] exiting... Apr 26 04:29:24 192.168.122.209 [44714.675415] [tdb] Shutdown Tempesta DB Apr 26 04:29:24 192.168.122.209 [44714.880072] End test: t_frang.test_client_body_and_header_timeout.ClientBodyTimeoutH2.test_timeout_ok Apr 26 04:29:24 192.168.122.209 [44714.897095] Start test: t_frang.test_client_body_and_header_timeout.ClientHeaderTimeout.test_timeout_invalid Apr 26 04:29:25 192.168.122.209 [44716.043531] [tdb] Start Tempesta DB Apr 26 04:29:25 192.168.122.209 [44716.193850] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:29:26 192.168.122.209 [44716.925056] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44716.925056] Maybe that's fine, but it's worth checking the [44716.925056] config - if there is no relations between the [44716.925056] names, then host name confusion attack is possible. Apr 26 04:29:26 192.168.122.209 [44717.023791] [tempesta fw] Configuration processing is completed. Apr 26 04:29:26 192.168.122.209 [44717.077999] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:29:26 192.168.122.209 [44717.108523] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:29:26 192.168.122.209 [44717.138814] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:29:26 192.168.122.209 [44717.175766] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:29:26 192.168.122.209 [44717.176670] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:29:26 192.168.122.209 [44717.177851] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:29:26 192.168.122.209 [44717.215774] [tempesta fw] Tempesta FW is ready Apr 26 04:29:28 192.168.122.209 [44718.834162] [tempesta fw] Warning: frang: client header timeout exceeded for 127.0.0.2: 1500 (lim=1000) Apr 26 04:29:28 192.168.122.209 [44718.835049] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:29:28 192.168.122.209 [44719.351608] [tdb] Close table 'client0.tdb' Apr 26 04:29:29 192.168.122.209 [44719.546642] [tdb] Close table 'sessions0.tdb' Apr 26 04:29:29 192.168.122.209 [44719.783517] [tdb] Close table 'filter0.tdb' Apr 26 04:29:29 192.168.122.209 [44719.784343] [tempesta fw] modules are stopped Apr 26 04:29:29 192.168.122.209 [44719.952360] [tempesta fw] exiting... Apr 26 04:29:29 192.168.122.209 [44720.086987] [tdb] Shutdown Tempesta DB Apr 26 04:29:29 192.168.122.209 [44720.322810] End test: t_frang.test_client_body_and_header_timeout.ClientHeaderTimeout.test_timeout_invalid Apr 26 04:29:29 192.168.122.209 [44720.334510] Start test: t_frang.test_client_body_and_header_timeout.ClientHeaderTimeout.test_timeout_ok Apr 26 04:29:31 192.168.122.209 [44721.563410] [tdb] Start Tempesta DB Apr 26 04:29:31 192.168.122.209 [44721.705998] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:29:32 192.168.122.209 [44722.477149] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44722.477149] Maybe that's fine, but it's worth checking the [44722.477149] config - if there is no relations between the [44722.477149] names, then host name confusion attack is possible. Apr 26 04:29:32 192.168.122.209 [44722.567930] [tempesta fw] Configuration processing is completed. Apr 26 04:29:32 192.168.122.209 [44722.618713] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:29:32 192.168.122.209 [44722.646530] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:29:32 192.168.122.209 [44722.675097] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:29:32 192.168.122.209 [44722.723892] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:29:32 192.168.122.209 [44722.725559] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:29:32 192.168.122.209 [44722.727248] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:29:32 192.168.122.209 [44722.763833] [tempesta fw] Tempesta FW is ready Apr 26 04:29:33 192.168.122.209 [44723.924101] [tdb] Close table 'client0.tdb' Apr 26 04:29:33 192.168.122.209 [44724.111719] [tdb] Close table 'sessions0.tdb' Apr 26 04:29:33 192.168.122.209 [44724.356868] [tdb] Close table 'filter0.tdb' Apr 26 04:29:33 192.168.122.209 [44724.357305] [tempesta fw] modules are stopped Apr 26 04:29:34 192.168.122.209 [44724.556543] [tempesta fw] exiting... Apr 26 04:29:34 192.168.122.209 [44724.685523] [tdb] Shutdown Tempesta DB Apr 26 04:29:34 192.168.122.209 [44724.861200] End test: t_frang.test_client_body_and_header_timeout.ClientHeaderTimeout.test_timeout_ok Apr 26 04:29:34 192.168.122.209 [44724.888251] Start test: t_frang.test_client_body_and_header_timeout.ClientHeaderTimeoutH2.test_starting_timeout_counter Apr 26 04:29:35 192.168.122.209 [44726.072988] [tdb] Start Tempesta DB Apr 26 04:29:35 192.168.122.209 [44726.221468] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:29:36 192.168.122.209 [44726.957200] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44726.957200] Maybe that's fine, but it's worth checking the [44726.957200] config - if there is no relations between the [44726.957200] names, then host name confusion attack is possible. Apr 26 04:29:36 192.168.122.209 [44727.063959] [tempesta fw] Configuration processing is completed. Apr 26 04:29:36 192.168.122.209 [44727.120613] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:29:36 192.168.122.209 [44727.150441] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:29:36 192.168.122.209 [44727.180563] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:29:36 192.168.122.209 [44727.231969] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:29:36 192.168.122.209 [44727.233650] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:29:36 192.168.122.209 [44727.235299] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:29:36 192.168.122.209 [44727.283913] [tempesta fw] Tempesta FW is ready Apr 26 04:29:40 192.168.122.209 [44730.443978] [tdb] Close table 'client0.tdb' Apr 26 04:29:40 192.168.122.209 [44730.641148] [tdb] Close table 'sessions0.tdb' Apr 26 04:29:40 192.168.122.209 [44730.881758] [tdb] Close table 'filter0.tdb' Apr 26 04:29:40 192.168.122.209 [44730.882183] [tempesta fw] modules are stopped Apr 26 04:29:40 192.168.122.209 [44731.079897] [tempesta fw] exiting... Apr 26 04:29:40 192.168.122.209 [44731.218136] [tdb] Shutdown Tempesta DB Apr 26 04:29:41 192.168.122.209 [44731.399422] End test: t_frang.test_client_body_and_header_timeout.ClientHeaderTimeoutH2.test_starting_timeout_counter Apr 26 04:29:41 192.168.122.209 [44731.411614] Start test: t_frang.test_client_body_and_header_timeout.ClientHeaderTimeoutH2.test_timeout_invalid Apr 26 04:29:42 192.168.122.209 [44732.536085] [tdb] Start Tempesta DB Apr 26 04:29:42 192.168.122.209 [44732.684654] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:29:43 192.168.122.209 [44733.421280] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44733.421280] Maybe that's fine, but it's worth checking the [44733.421280] config - if there is no relations between the [44733.421280] names, then host name confusion attack is possible. Apr 26 04:29:43 192.168.122.209 [44733.532040] [tempesta fw] Configuration processing is completed. Apr 26 04:29:43 192.168.122.209 [44733.582884] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:29:43 192.168.122.209 [44733.611561] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:29:43 192.168.122.209 [44733.641060] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:29:43 192.168.122.209 [44733.680022] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:29:43 192.168.122.209 [44733.681722] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:29:43 192.168.122.209 [44733.683373] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:29:43 192.168.122.209 [44733.720014] [tempesta fw] Tempesta FW is ready Apr 26 04:29:44 192.168.122.209 [44735.355637] [tempesta fw] Warning: frang: client header timeout exceeded for 127.0.0.2: 1500 (lim=1000) Apr 26 04:29:44 192.168.122.209 [44735.358255] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:29:45 192.168.122.209 [44735.839037] [tdb] Close table 'client0.tdb' Apr 26 04:29:45 192.168.122.209 [44736.043689] [tdb] Close table 'sessions0.tdb' Apr 26 04:29:45 192.168.122.209 [44736.285695] [tdb] Close table 'filter0.tdb' Apr 26 04:29:45 192.168.122.209 [44736.286122] [tempesta fw] modules are stopped Apr 26 04:29:46 192.168.122.209 [44736.500412] [tempesta fw] exiting... Apr 26 04:29:46 192.168.122.209 [44736.675508] [tdb] Shutdown Tempesta DB Apr 26 04:29:46 192.168.122.209 [44736.881278] End test: t_frang.test_client_body_and_header_timeout.ClientHeaderTimeoutH2.test_timeout_invalid Apr 26 04:29:46 192.168.122.209 [44736.892621] Start test: t_frang.test_client_body_and_header_timeout.ClientHeaderTimeoutH2.test_timeout_ok Apr 26 04:29:47 192.168.122.209 [44738.069502] [tdb] Start Tempesta DB Apr 26 04:29:47 192.168.122.209 [44738.227552] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:29:48 192.168.122.209 [44738.997326] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44738.997326] Maybe that's fine, but it's worth checking the [44738.997326] config - if there is no relations between the [44738.997326] names, then host name confusion attack is possible. Apr 26 04:29:48 192.168.122.209 [44739.104115] [tempesta fw] Configuration processing is completed. Apr 26 04:29:48 192.168.122.209 [44739.154035] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:29:48 192.168.122.209 [44739.184930] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:29:48 192.168.122.209 [44739.213875] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:29:48 192.168.122.209 [44739.272089] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:29:48 192.168.122.209 [44739.273865] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:29:48 192.168.122.209 [44739.275519] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:29:48 192.168.122.209 [44739.312057] [tempesta fw] Tempesta FW is ready Apr 26 04:29:50 192.168.122.209 [44740.498081] [tdb] Close table 'client0.tdb' Apr 26 04:29:50 192.168.122.209 [44740.701186] [tdb] Close table 'sessions0.tdb' Apr 26 04:29:50 192.168.122.209 [44740.942563] [tdb] Close table 'filter0.tdb' Apr 26 04:29:50 192.168.122.209 [44740.943032] [tempesta fw] modules are stopped Apr 26 04:29:50 192.168.122.209 [44741.148070] [tempesta fw] exiting... Apr 26 04:29:50 192.168.122.209 [44741.313129] [tdb] Shutdown Tempesta DB Apr 26 04:29:51 192.168.122.209 [44741.488088] End test: t_frang.test_client_body_and_header_timeout.ClientHeaderTimeoutH2.test_timeout_ok Apr 26 04:29:51 192.168.122.209 [44741.502836] Start test: t_frang.test_config.TestDefaultConfig.test_concurrent_tcp_connections Apr 26 04:29:52 192.168.122.209 [44742.636278] [tdb] Start Tempesta DB Apr 26 04:29:52 192.168.122.209 [44742.795108] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:29:52 192.168.122.209 [44743.325434] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44743.325434] Maybe that's fine, but it's worth checking the [44743.325434] config - if there is no relations between the [44743.325434] names, then host name confusion attack is possible. Apr 26 04:29:53 192.168.122.209 [44743.452241] [tempesta fw] Configuration processing is completed. Apr 26 04:29:53 192.168.122.209 [44743.503358] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:29:53 192.168.122.209 [44744.082910] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:29:53 192.168.122.209 [44744.120758] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:29:53 192.168.122.209 [44744.158282] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:29:53 192.168.122.209 [44744.204169] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:29:53 192.168.122.209 [44744.205854] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:29:53 192.168.122.209 [44744.260125] [tempesta fw] Tempesta FW is ready Apr 26 04:29:54 192.168.122.209 [44744.599464] [tempesta fw] Warning: frang: connections max num. exceeded for 127.0.0.1: 1001 (lim=1000) Apr 26 04:29:54 192.168.122.209 [44744.600784] [tempesta fw] Warning: frang: connections max num. exceeded for 127.0.0.1: 1001 (lim=1000) Apr 26 04:29:54 192.168.122.209 [44744.604971] [tempesta fw] Warning: frang: connections max num. exceeded for 127.0.0.1: 1001 (lim=1000) Apr 26 04:29:54 192.168.122.209 [44744.605807] [tempesta fw] Warning: frang: connections max num. exceeded for 127.0.0.1: 1002 (lim=1000) Apr 26 04:29:54 192.168.122.209 [44744.606744] [tempesta fw] Warning: frang: connections max num. exceeded for 127.0.0.1: 1001 (lim=1000) Apr 26 04:29:57 192.168.122.209 [44747.796071] net_ratelimit: 9105 callbacks suppressed Apr 26 04:29:57 192.168.122.209 [44747.796076] [tempesta fw] Warning: frang: connections max num. exceeded for 127.0.0.1: 1001 (lim=1000) Apr 26 04:29:57 192.168.122.209 [44747.798522] [tempesta fw] Warning: frang: connections max num. exceeded for 127.0.0.1: 1001 (lim=1000) Apr 26 04:29:57 192.168.122.209 [44747.803758] [tempesta fw] Warning: frang: connections max num. exceeded for 127.0.0.1: 1001 (lim=1000) Apr 26 04:29:57 192.168.122.209 [44747.804827] [tempesta fw] Warning: frang: connections max num. exceeded for 127.0.0.1: 1002 (lim=1000) Apr 26 04:29:57 192.168.122.209 [44747.805671] [tempesta fw] Warning: frang: connections max num. exceeded for 127.0.0.1: 1003 (lim=1000) Apr 26 04:29:57 192.168.122.209 [44747.807017] [tempesta fw] Warning: frang: connections max num. exceeded for 127.0.0.1: 1001 (lim=1000) Apr 26 04:29:57 192.168.122.209 [44747.808122] [tempesta fw] Warning: frang: connections max num. exceeded for 127.0.0.1: 1002 (lim=1000) Apr 26 04:29:57 192.168.122.209 [44747.808974] [tempesta fw] Warning: frang: connections max num. exceeded for 127.0.0.1: 1002 (lim=1000) Apr 26 04:29:57 192.168.122.209 [44747.810698] [tempesta fw] Warning: frang: connections max num. exceeded for 127.0.0.1: 1001 (lim=1000) Apr 26 04:29:57 192.168.122.209 [44747.811930] [tempesta fw] Warning: frang: connections max num. exceeded for 127.0.0.1: 1001 (lim=1000) Apr 26 04:30:02 192.168.122.209 [44752.800073] net_ratelimit: 16852 callbacks suppressed Apr 26 04:30:02 192.168.122.209 [44752.800077] [tempesta fw] Warning: frang: connections max num. exceeded for 127.0.0.1: 1001 (lim=1000) Apr 26 04:30:02 192.168.122.209 [44752.801425] [tempesta fw] Warning: frang: connections max num. exceeded for 127.0.0.1: 1002 (lim=1000) Apr 26 04:30:02 192.168.122.209 [44752.802282] [tempesta fw] Warning: frang: connections max num. exceeded for 127.0.0.1: 1003 (lim=1000) Apr 26 04:30:02 192.168.122.209 [44752.803244] [tempesta fw] Warning: frang: connections max num. exceeded for 127.0.0.1: 1001 (lim=1000) Apr 26 04:30:02 192.168.122.209 [44752.804095] [tempesta fw] Warning: frang: connections max num. exceeded for 127.0.0.1: 1002 (lim=1000) Apr 26 04:30:02 192.168.122.209 [44752.804924] [tempesta fw] Warning: frang: connections max num. exceeded for 127.0.0.1: 1003 (lim=1000) Apr 26 04:30:02 192.168.122.209 [44752.805822] [tempesta fw] Warning: frang: connections max num. exceeded for 127.0.0.1: 1001 (lim=1000) Apr 26 04:30:02 192.168.122.209 [44752.806657] [tempesta fw] Warning: frang: connections max num. exceeded for 127.0.0.1: 1002 (lim=1000) Apr 26 04:30:02 192.168.122.209 [44752.807493] [tempesta fw] Warning: frang: connections max num. exceeded for 127.0.0.1: 1003 (lim=1000) Apr 26 04:30:02 192.168.122.209 [44752.808483] [tempesta fw] Warning: frang: connections max num. exceeded for 127.0.0.1: 1001 (lim=1000) Apr 26 04:30:04 192.168.122.209 [44755.180501] [tdb] Close table 'client0.tdb' Apr 26 04:30:05 192.168.122.209 [44755.377398] [tdb] Close table 'sessions0.tdb' Apr 26 04:30:08 192.168.122.209 [44758.666399] [tdb] Close table 'cache0.tdb' Apr 26 04:30:08 192.168.122.209 [44758.926370] [tdb] Close table 'filter0.tdb' Apr 26 04:30:08 192.168.122.209 [44758.926806] net_ratelimit: 6307 callbacks suppressed Apr 26 04:30:08 192.168.122.209 [44758.926807] [tempesta fw] modules are stopped Apr 26 04:30:08 192.168.122.209 [44759.139294] [tempesta fw] exiting... Apr 26 04:30:08 192.168.122.209 [44759.282987] [tdb] Shutdown Tempesta DB Apr 26 04:30:09 192.168.122.209 [44759.508096] End test: t_frang.test_config.TestDefaultConfig.test_concurrent_tcp_connections Apr 26 04:30:09 192.168.122.209 [44759.516969] Start test: t_frang.test_config.TestDefaultConfig.test_http_ct_required Apr 26 04:30:10 192.168.122.209 [44760.740436] [tdb] Start Tempesta DB Apr 26 04:30:10 192.168.122.209 [44760.887237] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:30:11 192.168.122.209 [44762.313681] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44762.313681] Maybe that's fine, but it's worth checking the [44762.313681] config - if there is no relations between the [44762.313681] names, then host name confusion attack is possible. Apr 26 04:30:12 192.168.122.209 [44762.432667] [tempesta fw] Configuration processing is completed. Apr 26 04:30:12 192.168.122.209 [44762.489049] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:30:12 192.168.122.209 [44762.916404] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:30:12 192.168.122.209 [44762.948533] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:30:12 192.168.122.209 [44762.975435] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:30:12 192.168.122.209 [44763.096403] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:30:12 192.168.122.209 [44763.098182] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:30:12 192.168.122.209 [44763.144343] [tempesta fw] Tempesta FW is ready Apr 26 04:30:15 192.168.122.209 [44765.985793] [tdb] Close table 'client0.tdb' Apr 26 04:30:15 192.168.122.209 [44766.187945] [tdb] Close table 'sessions0.tdb' Apr 26 04:30:18 192.168.122.209 [44769.355995] [tdb] Close table 'cache0.tdb' Apr 26 04:30:19 192.168.122.209 [44769.632912] [tdb] Close table 'filter0.tdb' Apr 26 04:30:19 192.168.122.209 [44769.633588] [tempesta fw] modules are stopped Apr 26 04:30:19 192.168.122.209 [44769.833304] [tempesta fw] exiting... Apr 26 04:30:19 192.168.122.209 [44770.003858] [tdb] Shutdown Tempesta DB Apr 26 04:30:19 192.168.122.209 [44770.254574] End test: t_frang.test_config.TestDefaultConfig.test_http_ct_required Apr 26 04:30:19 192.168.122.209 [44770.267618] Start test: t_frang.test_config.TestDefaultConfig.test_http_header_cnt Apr 26 04:30:20 192.168.122.209 [44771.332870] [tdb] Start Tempesta DB Apr 26 04:30:21 192.168.122.209 [44771.467172] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:30:22 192.168.122.209 [44772.721919] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44772.721919] Maybe that's fine, but it's worth checking the [44772.721919] config - if there is no relations between the [44772.721919] names, then host name confusion attack is possible. Apr 26 04:30:22 192.168.122.209 [44772.844554] [tempesta fw] Configuration processing is completed. Apr 26 04:30:22 192.168.122.209 [44772.893989] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:30:22 192.168.122.209 [44773.303734] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:30:22 192.168.122.209 [44773.329873] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:30:22 192.168.122.209 [44773.355192] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:30:23 192.168.122.209 [44773.408551] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:30:23 192.168.122.209 [44773.410284] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:30:23 192.168.122.209 [44773.448487] [tempesta fw] Tempesta FW is ready Apr 26 04:30:23 192.168.122.209 [44773.572237] [tempesta fw] Warning: frang: HTTP headers count exceeded for 127.0.0.2: 51 (lim=50) Apr 26 04:30:23 192.168.122.209 [44774.069556] [tdb] Close table 'client0.tdb' Apr 26 04:30:23 192.168.122.209 [44774.280368] [tdb] Close table 'sessions0.tdb' Apr 26 04:30:27 192.168.122.209 [44777.453481] [tdb] Close table 'cache0.tdb' Apr 26 04:30:27 192.168.122.209 [44777.666583] [tdb] Close table 'filter0.tdb' Apr 26 04:30:27 192.168.122.209 [44777.667011] [tempesta fw] modules are stopped Apr 26 04:30:27 192.168.122.209 [44777.873034] [tempesta fw] exiting... Apr 26 04:30:27 192.168.122.209 [44778.030998] [tdb] Shutdown Tempesta DB Apr 26 04:30:27 192.168.122.209 [44778.243727] End test: t_frang.test_config.TestDefaultConfig.test_http_header_cnt Apr 26 04:30:27 192.168.122.209 [44778.255262] Start test: t_frang.test_config.TestDefaultConfig.test_http_methods Apr 26 04:30:29 192.168.122.209 [44779.516017] [tdb] Start Tempesta DB Apr 26 04:30:29 192.168.122.209 [44779.658296] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:30:30 192.168.122.209 [44780.993838] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44780.993838] Maybe that's fine, but it's worth checking the [44780.993838] config - if there is no relations between the [44780.993838] names, then host name confusion attack is possible. Apr 26 04:30:30 192.168.122.209 [44781.120591] [tempesta fw] Configuration processing is completed. Apr 26 04:30:30 192.168.122.209 [44781.175124] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:30:31 192.168.122.209 [44781.594410] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:30:31 192.168.122.209 [44781.619392] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:30:31 192.168.122.209 [44781.644857] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:30:31 192.168.122.209 [44781.692659] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:30:31 192.168.122.209 [44781.694472] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:30:31 192.168.122.209 [44781.736589] [tempesta fw] Tempesta FW is ready Apr 26 04:30:31 192.168.122.209 [44781.858802] [tempesta fw] Warning: frang: restricted HTTP method for 127.0.0.2: 13 (0x2000u) Apr 26 04:30:31 192.168.122.209 [44781.859589] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:30:31 192.168.122.209 [44782.368688] [tdb] Close table 'client0.tdb' Apr 26 04:30:32 192.168.122.209 [44782.559880] [tdb] Close table 'sessions0.tdb' Apr 26 04:30:35 192.168.122.209 [44785.672811] [tdb] Close table 'cache0.tdb' Apr 26 04:30:35 192.168.122.209 [44785.923871] [tdb] Close table 'filter0.tdb' Apr 26 04:30:35 192.168.122.209 [44785.924327] [tempesta fw] modules are stopped Apr 26 04:30:35 192.168.122.209 [44786.109915] [tempesta fw] exiting... Apr 26 04:30:35 192.168.122.209 [44786.259207] [tdb] Shutdown Tempesta DB Apr 26 04:30:36 192.168.122.209 [44786.462590] End test: t_frang.test_config.TestDefaultConfig.test_http_methods Apr 26 04:30:36 192.168.122.209 [44786.473716] Start test: t_frang.test_config.TestDefaultConfig.test_http_strict_host_checking Apr 26 04:30:37 192.168.122.209 [44787.641652] [tdb] Start Tempesta DB Apr 26 04:30:37 192.168.122.209 [44787.779480] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:30:38 192.168.122.209 [44789.045929] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44789.045929] Maybe that's fine, but it's worth checking the [44789.045929] config - if there is no relations between the [44789.045929] names, then host name confusion attack is possible. Apr 26 04:30:38 192.168.122.209 [44789.180712] [tempesta fw] Configuration processing is completed. Apr 26 04:30:38 192.168.122.209 [44789.231630] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:30:39 192.168.122.209 [44789.646807] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:30:39 192.168.122.209 [44789.672437] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:30:39 192.168.122.209 [44789.698188] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:30:39 192.168.122.209 [44789.748779] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:30:39 192.168.122.209 [44789.750522] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:30:39 192.168.122.209 [44789.788684] [tempesta fw] Tempesta FW is ready Apr 26 04:30:39 192.168.122.209 [44789.928885] [tempesta fw] Warning: frang: Request :authority differs from Host for 127.0.0.2 Apr 26 04:30:39 192.168.122.209 [44789.930812] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:30:40 192.168.122.209 [44790.455371] [tdb] Close table 'client0.tdb' Apr 26 04:30:40 192.168.122.209 [44790.661351] [tdb] Close table 'sessions0.tdb' Apr 26 04:30:43 192.168.122.209 [44793.793979] [tdb] Close table 'cache0.tdb' Apr 26 04:30:43 192.168.122.209 [44794.047639] [tdb] Close table 'filter0.tdb' Apr 26 04:30:43 192.168.122.209 [44794.048086] [tempesta fw] modules are stopped Apr 26 04:30:43 192.168.122.209 [44794.245334] [tempesta fw] exiting... Apr 26 04:30:44 192.168.122.209 [44794.413174] [tdb] Shutdown Tempesta DB Apr 26 04:30:44 192.168.122.209 [44794.595929] End test: t_frang.test_config.TestDefaultConfig.test_http_strict_host_checking Apr 26 04:30:44 192.168.122.209 [44794.606529] Start test: t_frang.test_config.TestDefaultConfig.test_http_trailer_split_allowed Apr 26 04:30:45 192.168.122.209 [44795.747606] [tdb] Start Tempesta DB Apr 26 04:30:45 192.168.122.209 [44795.902058] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:30:46 192.168.122.209 [44797.174202] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44797.174202] Maybe that's fine, but it's worth checking the [44797.174202] config - if there is no relations between the [44797.174202] names, then host name confusion attack is possible. Apr 26 04:30:46 192.168.122.209 [44797.296810] [tempesta fw] Configuration processing is completed. Apr 26 04:30:46 192.168.122.209 [44797.346482] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:30:47 192.168.122.209 [44797.759821] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:30:47 192.168.122.209 [44797.817724] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:30:47 192.168.122.209 [44797.844237] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:30:47 192.168.122.209 [44797.884854] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:30:47 192.168.122.209 [44797.886552] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:30:47 192.168.122.209 [44797.940806] [tempesta fw] Tempesta FW is ready Apr 26 04:30:47 192.168.122.209 [44798.081951] [tempesta fw] Warning: frang: HTTP field appear in header and trailer for client for 127.0.0.2 Apr 26 04:30:47 192.168.122.209 [44798.082842] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:30:48 192.168.122.209 [44798.636091] [tdb] Close table 'client0.tdb' Apr 26 04:30:48 192.168.122.209 [44798.825643] [tdb] Close table 'sessions0.tdb' Apr 26 04:30:51 192.168.122.209 [44801.987632] [tdb] Close table 'cache0.tdb' Apr 26 04:30:51 192.168.122.209 [44802.193854] [tdb] Close table 'filter0.tdb' Apr 26 04:30:51 192.168.122.209 [44802.194283] [tempesta fw] modules are stopped Apr 26 04:30:52 192.168.122.209 [44802.417951] [tempesta fw] exiting... Apr 26 04:30:52 192.168.122.209 [44802.583031] [tdb] Shutdown Tempesta DB Apr 26 04:30:52 192.168.122.209 [44802.789198] End test: t_frang.test_config.TestDefaultConfig.test_http_trailer_split_allowed Apr 26 04:30:52 192.168.122.209 [44802.809808] Start test: t_frang.test_config.TestDefaultConfig.test_ip_block Apr 26 04:30:53 192.168.122.209 [44804.015029] [tdb] Start Tempesta DB Apr 26 04:30:53 192.168.122.209 [44804.205398] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:30:55 192.168.122.209 [44805.530170] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44805.530170] Maybe that's fine, but it's worth checking the [44805.530170] config - if there is no relations between the [44805.530170] names, then host name confusion attack is possible. Apr 26 04:30:55 192.168.122.209 [44805.656968] [tempesta fw] Configuration processing is completed. Apr 26 04:30:55 192.168.122.209 [44805.707570] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:30:55 192.168.122.209 [44806.122246] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:30:55 192.168.122.209 [44806.148018] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:30:55 192.168.122.209 [44806.174303] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:30:55 192.168.122.209 [44806.216944] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:30:55 192.168.122.209 [44806.218622] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:30:55 192.168.122.209 [44806.256894] [tempesta fw] Tempesta FW is ready Apr 26 04:30:56 192.168.122.209 [44806.411877] [tempesta fw] Warning: frang: restricted HTTP method for 127.0.0.2: 13 (0x2000u) Apr 26 04:30:56 192.168.122.209 [44806.413763] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:30:56 192.168.122.209 [44806.943262] [tdb] Close table 'client0.tdb' Apr 26 04:30:56 192.168.122.209 [44807.132790] [tdb] Close table 'sessions0.tdb' Apr 26 04:30:59 192.168.122.209 [44810.241790] [tdb] Close table 'cache0.tdb' Apr 26 04:31:00 192.168.122.209 [44810.472542] [tdb] Close table 'filter0.tdb' Apr 26 04:31:00 192.168.122.209 [44810.472986] [tempesta fw] modules are stopped Apr 26 04:31:00 192.168.122.209 [44810.649748] [tempesta fw] exiting... Apr 26 04:31:00 192.168.122.209 [44810.799405] [tdb] Shutdown Tempesta DB Apr 26 04:31:00 192.168.122.209 [44810.996689] End test: t_frang.test_config.TestDefaultConfig.test_ip_block Apr 26 04:31:00 192.168.122.209 [44811.023131] Start test: t_frang.test_config.TestOverridingInheritance.test_connection_limit_in_location Apr 26 04:31:01 192.168.122.209 [44812.176116] [tdb] Start Tempesta DB Apr 26 04:31:01 192.168.122.209 [44812.317489] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:31:03 192.168.122.209 [44813.930276] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44813.930276] Maybe that's fine, but it's worth checking the [44813.930276] config - if there is no relations between the [44813.930276] names, then host name confusion attack is possible. Apr 26 04:31:03 192.168.122.209 [44814.034280] [tempesta fw] ERROR: Directive 'http_hdr_len' from 'frang_limits' group can be used only as top-level directive (outside of any 'vhost' directive). Apr 26 04:31:03 192.168.122.209 [44814.038149] [tempesta fw] ERROR: configuration parsing error: [44814.038149] 15: frang_limits {http_hdr_len 100;} [44814.038149] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 04:31:03 192.168.122.209 [44814.043816] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 04:31:03 192.168.122.209 [44814.247060] [tempesta fw] exiting... Apr 26 04:31:03 192.168.122.209 [44814.363945] [tdb] Shutdown Tempesta DB Apr 26 04:31:04 192.168.122.209 [44814.847154] End test: t_frang.test_config.TestOverridingInheritance.test_connection_limit_in_location Apr 26 04:31:04 192.168.122.209 [44814.862172] Start test: t_frang.test_config.TestOverridingInheritance.test_connection_limit_in_vhost Apr 26 04:31:05 192.168.122.209 [44815.929472] [tdb] Start Tempesta DB Apr 26 04:31:05 192.168.122.209 [44816.067732] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:31:06 192.168.122.209 [44816.566348] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44816.566348] Maybe that's fine, but it's worth checking the [44816.566348] config - if there is no relations between the [44816.566348] names, then host name confusion attack is possible. Apr 26 04:31:06 192.168.122.209 [44816.653637] [tempesta fw] ERROR: Directive 'http_hdr_len' from 'frang_limits' group can be used only as top-level directive (outside of any 'vhost' directive). Apr 26 04:31:06 192.168.122.209 [44816.657552] [tempesta fw] ERROR: configuration parsing error: [44816.657552] 12: vhost vhost_1 {frang_limits {http_hdr_len 100;} proxy_pass d [44816.657552] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 04:31:06 192.168.122.209 [44816.663412] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 04:31:06 192.168.122.209 [44816.861917] [tempesta fw] exiting... Apr 26 04:31:06 192.168.122.209 [44816.988272] [tdb] Shutdown Tempesta DB Apr 26 04:31:07 192.168.122.209 [44817.379328] End test: t_frang.test_config.TestOverridingInheritance.test_connection_limit_in_vhost Apr 26 04:31:07 192.168.122.209 [44817.393108] Start test: t_frang.test_config.TestOverridingInheritance.test_default_not_override_concurrent_tcp_connections Apr 26 04:31:08 192.168.122.209 [44818.498802] [tdb] Start Tempesta DB Apr 26 04:31:08 192.168.122.209 [44818.640240] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:31:08 192.168.122.209 [44819.098181] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44819.098181] Maybe that's fine, but it's worth checking the [44819.098181] config - if there is no relations between the [44819.098181] names, then host name confusion attack is possible. Apr 26 04:31:08 192.168.122.209 [44819.253510] [tempesta fw] Configuration processing is completed. Apr 26 04:31:08 192.168.122.209 [44819.302977] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:31:09 192.168.122.209 [44819.706398] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:31:09 192.168.122.209 [44819.762327] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:31:09 192.168.122.209 [44819.791625] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:31:09 192.168.122.209 [44819.829114] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:31:09 192.168.122.209 [44819.830800] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:31:09 192.168.122.209 [44819.881062] [tempesta fw] Tempesta FW is ready Apr 26 04:31:09 192.168.122.209 [44819.998693] [tempesta fw] Warning: frang: connections max num. exceeded for 127.0.0.2: 2 (lim=1) Apr 26 04:31:10 192.168.122.209 [44820.492528] [tdb] Close table 'client0.tdb' Apr 26 04:31:10 192.168.122.209 [44820.674563] [tdb] Close table 'sessions0.tdb' Apr 26 04:31:13 192.168.122.209 [44823.768269] [tdb] Close table 'cache0.tdb' Apr 26 04:31:13 192.168.122.209 [44823.999829] [tdb] Close table 'filter0.tdb' Apr 26 04:31:13 192.168.122.209 [44824.000270] [tempesta fw] modules are stopped Apr 26 04:31:13 192.168.122.209 [44824.225703] [tempesta fw] exiting... Apr 26 04:31:14 192.168.122.209 [44824.377077] [tdb] Shutdown Tempesta DB Apr 26 04:31:14 192.168.122.209 [44824.587879] End test: t_frang.test_config.TestOverridingInheritance.test_default_not_override_concurrent_tcp_connections Apr 26 04:31:14 192.168.122.209 [44824.609624] Start test: t_frang.test_config.TestOverridingInheritance.test_default_not_override_http_body_len_0 Apr 26 04:31:15 192.168.122.209 [44825.791795] [tdb] Start Tempesta DB Apr 26 04:31:15 192.168.122.209 [44825.928505] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:31:16 192.168.122.209 [44827.354495] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44827.354495] Maybe that's fine, but it's worth checking the [44827.354495] config - if there is no relations between the [44827.354495] names, then host name confusion attack is possible. Apr 26 04:31:17 192.168.122.209 [44827.533117] [tempesta fw] Configuration processing is completed. Apr 26 04:31:17 192.168.122.209 [44827.579436] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:31:17 192.168.122.209 [44827.983896] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:31:17 192.168.122.209 [44828.040094] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:31:17 192.168.122.209 [44828.065967] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:31:17 192.168.122.209 [44828.105244] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:31:17 192.168.122.209 [44828.106209] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:31:17 192.168.122.209 [44828.145180] [tempesta fw] Tempesta FW is ready Apr 26 04:31:20 192.168.122.209 [44831.010424] [tdb] Close table 'client0.tdb' Apr 26 04:31:20 192.168.122.209 [44831.200666] [tdb] Close table 'sessions0.tdb' Apr 26 04:31:23 192.168.122.209 [44834.295315] [tdb] Close table 'cache0.tdb' Apr 26 04:31:24 192.168.122.209 [44834.556458] [tdb] Close table 'filter0.tdb' Apr 26 04:31:24 192.168.122.209 [44834.556889] [tempesta fw] modules are stopped Apr 26 04:31:24 192.168.122.209 [44834.739656] [tempesta fw] exiting... Apr 26 04:31:24 192.168.122.209 [44834.866353] [tdb] Shutdown Tempesta DB Apr 26 04:31:24 192.168.122.209 [44835.079584] End test: t_frang.test_config.TestOverridingInheritance.test_default_not_override_http_body_len_0 Apr 26 04:31:24 192.168.122.209 [44835.093778] Start test: t_frang.test_config.TestOverridingInheritance.test_default_not_override_http_body_len_1 Apr 26 04:31:25 192.168.122.209 [44836.303285] [tdb] Start Tempesta DB Apr 26 04:31:26 192.168.122.209 [44836.448764] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:31:27 192.168.122.209 [44837.898607] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44837.898607] Maybe that's fine, but it's worth checking the [44837.898607] config - if there is no relations between the [44837.898607] names, then host name confusion attack is possible. Apr 26 04:31:27 192.168.122.209 [44838.061493] [tempesta fw] Configuration processing is completed. Apr 26 04:31:27 192.168.122.209 [44838.111886] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:31:28 192.168.122.209 [44838.524265] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:31:28 192.168.122.209 [44838.580489] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:31:28 192.168.122.209 [44838.612153] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:31:28 192.168.122.209 [44838.689374] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:31:28 192.168.122.209 [44838.691043] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:31:28 192.168.122.209 [44838.737315] [tempesta fw] Tempesta FW is ready Apr 26 04:31:28 192.168.122.209 [44838.876708] [tempesta fw] Warning: frang: HTTP body length exceeded for 127.0.0.2: 2 (lim=1) Apr 26 04:31:28 192.168.122.209 [44838.879095] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:31:29 192.168.122.209 [44839.375362] [tdb] Close table 'client0.tdb' Apr 26 04:31:29 192.168.122.209 [44839.594889] [tdb] Close table 'sessions0.tdb' Apr 26 04:31:32 192.168.122.209 [44842.747237] [tdb] Close table 'cache0.tdb' Apr 26 04:31:32 192.168.122.209 [44842.974125] [tdb] Close table 'filter0.tdb' Apr 26 04:31:32 192.168.122.209 [44842.974573] [tempesta fw] modules are stopped Apr 26 04:31:32 192.168.122.209 [44843.200582] [tempesta fw] exiting... Apr 26 04:31:32 192.168.122.209 [44843.318285] [tdb] Shutdown Tempesta DB Apr 26 04:31:33 192.168.122.209 [44843.502558] End test: t_frang.test_config.TestOverridingInheritance.test_default_not_override_http_body_len_1 Apr 26 04:31:33 192.168.122.209 [44843.516812] Start test: t_frang.test_config.TestOverridingInheritance.test_default_not_override_http_body_len_2 Apr 26 04:31:34 192.168.122.209 [44844.731047] [tdb] Start Tempesta DB Apr 26 04:31:34 192.168.122.209 [44844.857302] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:31:35 192.168.122.209 [44846.298757] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44846.298757] Maybe that's fine, but it's worth checking the [44846.298757] config - if there is no relations between the [44846.298757] names, then host name confusion attack is possible. Apr 26 04:31:36 192.168.122.209 [44846.469478] [tempesta fw] Configuration processing is completed. Apr 26 04:31:36 192.168.122.209 [44846.519429] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:31:36 192.168.122.209 [44846.956475] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:31:36 192.168.122.209 [44846.991104] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:31:36 192.168.122.209 [44847.016468] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:31:36 192.168.122.209 [44847.061514] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:31:36 192.168.122.209 [44847.063200] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:31:36 192.168.122.209 [44847.105408] [tempesta fw] Tempesta FW is ready Apr 26 04:31:39 192.168.122.209 [44849.980453] [tdb] Close table 'client0.tdb' Apr 26 04:31:39 192.168.122.209 [44850.173142] [tdb] Close table 'sessions0.tdb' Apr 26 04:31:42 192.168.122.209 [44853.299127] [tdb] Close table 'cache0.tdb' Apr 26 04:31:43 192.168.122.209 [44853.558855] [tdb] Close table 'filter0.tdb' Apr 26 04:31:43 192.168.122.209 [44853.559274] [tempesta fw] modules are stopped Apr 26 04:31:43 192.168.122.209 [44853.806785] [tempesta fw] exiting... Apr 26 04:31:43 192.168.122.209 [44853.948238] [tdb] Shutdown Tempesta DB Apr 26 04:31:43 192.168.122.209 [44854.182336] End test: t_frang.test_config.TestOverridingInheritance.test_default_not_override_http_body_len_2 Apr 26 04:31:43 192.168.122.209 [44854.194212] Start test: t_frang.test_config.TestOverridingInheritance.test_default_not_override_http_body_len_3 Apr 26 04:31:44 192.168.122.209 [44855.368788] [tdb] Start Tempesta DB Apr 26 04:31:45 192.168.122.209 [44855.517937] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:31:46 192.168.122.209 [44857.082834] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44857.082834] Maybe that's fine, but it's worth checking the [44857.082834] config - if there is no relations between the [44857.082834] names, then host name confusion attack is possible. Apr 26 04:31:46 192.168.122.209 [44857.257623] [tempesta fw] Configuration processing is completed. Apr 26 04:31:46 192.168.122.209 [44857.307484] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:31:47 192.168.122.209 [44857.710975] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:31:47 192.168.122.209 [44857.767061] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:31:47 192.168.122.209 [44857.792668] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:31:47 192.168.122.209 [44857.869604] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:31:47 192.168.122.209 [44857.871373] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:31:47 192.168.122.209 [44857.909555] [tempesta fw] Tempesta FW is ready Apr 26 04:31:47 192.168.122.209 [44858.042501] [tempesta fw] Warning: frang: HTTP body length exceeded for 127.0.0.2: 2 (lim=1) Apr 26 04:31:47 192.168.122.209 [44858.043560] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:31:48 192.168.122.209 [44858.599820] [tdb] Close table 'client0.tdb' Apr 26 04:31:48 192.168.122.209 [44858.788446] [tdb] Close table 'sessions0.tdb' Apr 26 04:31:51 192.168.122.209 [44861.894010] [tdb] Close table 'cache0.tdb' Apr 26 04:31:51 192.168.122.209 [44862.112296] [tdb] Close table 'filter0.tdb' Apr 26 04:31:51 192.168.122.209 [44862.112730] [tempesta fw] modules are stopped Apr 26 04:31:51 192.168.122.209 [44862.337832] [tempesta fw] exiting... Apr 26 04:31:52 192.168.122.209 [44862.461134] [tdb] Shutdown Tempesta DB Apr 26 04:31:52 192.168.122.209 [44862.676602] End test: t_frang.test_config.TestOverridingInheritance.test_default_not_override_http_body_len_3 Apr 26 04:31:52 192.168.122.209 [44862.686397] Start test: t_frang.test_config.TestOverridingInheritance.test_default_not_override_http_body_len_4 Apr 26 04:31:53 192.168.122.209 [44863.821895] [tdb] Start Tempesta DB Apr 26 04:31:53 192.168.122.209 [44863.965603] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:31:55 192.168.122.209 [44865.634954] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44865.634954] Maybe that's fine, but it's worth checking the [44865.634954] config - if there is no relations between the [44865.634954] names, then host name confusion attack is possible. Apr 26 04:31:55 192.168.122.209 [44865.817803] [tempesta fw] Configuration processing is completed. Apr 26 04:31:55 192.168.122.209 [44865.880846] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:31:55 192.168.122.209 [44866.314762] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:31:55 192.168.122.209 [44866.340429] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:31:55 192.168.122.209 [44866.366069] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:31:56 192.168.122.209 [44866.413710] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:31:56 192.168.122.209 [44866.415370] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:31:56 192.168.122.209 [44866.453666] [tempesta fw] Tempesta FW is ready Apr 26 04:31:56 192.168.122.209 [44866.595949] [tempesta fw] Warning: frang: HTTP body length exceeded for 127.0.0.2: 2 (lim=1) Apr 26 04:31:56 192.168.122.209 [44866.597189] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:31:56 192.168.122.209 [44867.114186] [tdb] Close table 'client0.tdb' Apr 26 04:31:56 192.168.122.209 [44867.324664] [tdb] Close table 'sessions0.tdb' Apr 26 04:32:00 192.168.122.209 [44870.438851] [tdb] Close table 'cache0.tdb' Apr 26 04:32:00 192.168.122.209 [44870.674747] [tdb] Close table 'filter0.tdb' Apr 26 04:32:00 192.168.122.209 [44870.675182] [tempesta fw] modules are stopped Apr 26 04:32:00 192.168.122.209 [44870.942726] [tempesta fw] exiting... Apr 26 04:32:00 192.168.122.209 [44871.057461] [tdb] Shutdown Tempesta DB Apr 26 04:32:00 192.168.122.209 [44871.240934] End test: t_frang.test_config.TestOverridingInheritance.test_default_not_override_http_body_len_4 Apr 26 04:32:00 192.168.122.209 [44871.269929] Start test: t_frang.test_config.TestOverridingInheritance.test_default_not_override_http_body_len_5 Apr 26 04:32:02 192.168.122.209 [44872.392190] [tdb] Start Tempesta DB Apr 26 04:32:02 192.168.122.209 [44872.537330] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:32:03 192.168.122.209 [44874.011061] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44874.011061] Maybe that's fine, but it's worth checking the [44874.011061] config - if there is no relations between the [44874.011061] names, then host name confusion attack is possible. Apr 26 04:32:03 192.168.122.209 [44874.153841] [tempesta fw] Configuration processing is completed. Apr 26 04:32:03 192.168.122.209 [44874.203325] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:32:04 192.168.122.209 [44874.608680] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:32:04 192.168.122.209 [44874.664604] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:32:04 192.168.122.209 [44874.690252] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:32:04 192.168.122.209 [44874.766015] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:32:04 192.168.122.209 [44874.767752] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:32:04 192.168.122.209 [44874.821769] [tempesta fw] Tempesta FW is ready Apr 26 04:32:07 192.168.122.209 [44877.628163] [tdb] Close table 'client0.tdb' Apr 26 04:32:07 192.168.122.209 [44877.847889] [tdb] Close table 'sessions0.tdb' Apr 26 04:32:10 192.168.122.209 [44881.019402] [tdb] Close table 'cache0.tdb' Apr 26 04:32:10 192.168.122.209 [44881.253998] [tdb] Close table 'filter0.tdb' Apr 26 04:32:10 192.168.122.209 [44881.254405] [tempesta fw] modules are stopped Apr 26 04:32:11 192.168.122.209 [44881.483735] [tempesta fw] exiting... Apr 26 04:32:11 192.168.122.209 [44881.598070] [tdb] Shutdown Tempesta DB Apr 26 04:32:11 192.168.122.209 [44881.820548] End test: t_frang.test_config.TestOverridingInheritance.test_default_not_override_http_body_len_5 Apr 26 04:32:11 192.168.122.209 [44881.841126] Start test: t_frang.test_config.TestOverridingInheritance.test_default_not_override_http_methods Apr 26 04:32:12 192.168.122.209 [44883.068568] [tdb] Start Tempesta DB Apr 26 04:32:12 192.168.122.209 [44883.221557] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:32:14 192.168.122.209 [44884.695134] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44884.695134] Maybe that's fine, but it's worth checking the [44884.695134] config - if there is no relations between the [44884.695134] names, then host name confusion attack is possible. Apr 26 04:32:14 192.168.122.209 [44884.861963] [tempesta fw] Configuration processing is completed. Apr 26 04:32:14 192.168.122.209 [44884.912712] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:32:14 192.168.122.209 [44885.325694] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:32:14 192.168.122.209 [44885.351368] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:32:15 192.168.122.209 [44885.377042] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:32:15 192.168.122.209 [44885.425949] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:32:15 192.168.122.209 [44885.427680] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:32:15 192.168.122.209 [44885.473956] [tempesta fw] Tempesta FW is ready Apr 26 04:32:15 192.168.122.209 [44885.626713] [tempesta fw] Warning: frang: restricted HTTP method for 127.0.0.2: 3 (0x8u) Apr 26 04:32:15 192.168.122.209 [44885.627628] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:32:15 192.168.122.209 [44886.145474] [tdb] Close table 'client0.tdb' Apr 26 04:32:15 192.168.122.209 [44886.331659] [tdb] Close table 'sessions0.tdb' Apr 26 04:32:19 192.168.122.209 [44889.520810] [tdb] Close table 'cache0.tdb' Apr 26 04:32:19 192.168.122.209 [44889.787408] [tdb] Close table 'filter0.tdb' Apr 26 04:32:19 192.168.122.209 [44889.788083] [tempesta fw] modules are stopped Apr 26 04:32:19 192.168.122.209 [44889.979622] [tempesta fw] exiting... Apr 26 04:32:19 192.168.122.209 [44890.154603] [tdb] Shutdown Tempesta DB Apr 26 04:32:19 192.168.122.209 [44890.366577] End test: t_frang.test_config.TestOverridingInheritance.test_default_not_override_http_methods Apr 26 04:32:20 192.168.122.209 [44890.372963] Start test: t_frang.test_config.TestOverridingInheritance.test_default_not_override_http_resp_code_block_1 Apr 26 04:32:21 192.168.122.209 [44891.453502] [tdb] Start Tempesta DB Apr 26 04:32:21 192.168.122.209 [44891.602235] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:32:22 192.168.122.209 [44892.979284] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44892.979284] Maybe that's fine, but it's worth checking the [44892.979284] config - if there is no relations between the [44892.979284] names, then host name confusion attack is possible. Apr 26 04:32:22 192.168.122.209 [44893.162115] [tempesta fw] Configuration processing is completed. Apr 26 04:32:22 192.168.122.209 [44893.217897] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:32:23 192.168.122.209 [44893.624600] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:32:23 192.168.122.209 [44893.650533] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:32:23 192.168.122.209 [44893.678187] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:32:23 192.168.122.209 [44893.722098] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:32:23 192.168.122.209 [44893.723776] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:32:23 192.168.122.209 [44893.761996] [tempesta fw] Tempesta FW is ready Apr 26 04:32:26 192.168.122.209 [44896.637122] [tdb] Close table 'client0.tdb' Apr 26 04:32:26 192.168.122.209 [44896.808591] [tdb] Close table 'sessions0.tdb' Apr 26 04:32:29 192.168.122.209 [44899.963740] [tdb] Close table 'cache0.tdb' Apr 26 04:32:29 192.168.122.209 [44900.218912] [tdb] Close table 'filter0.tdb' Apr 26 04:32:29 192.168.122.209 [44900.219363] [tempesta fw] modules are stopped Apr 26 04:32:30 192.168.122.209 [44900.412557] [tempesta fw] exiting... Apr 26 04:32:30 192.168.122.209 [44900.566795] [tdb] Shutdown Tempesta DB Apr 26 04:32:30 192.168.122.209 [44900.766344] End test: t_frang.test_config.TestOverridingInheritance.test_default_not_override_http_resp_code_block_1 Apr 26 04:32:30 192.168.122.209 [44900.780460] Start test: t_frang.test_config.TestOverridingInheritance.test_default_not_override_http_resp_code_block_2 Apr 26 04:32:31 192.168.122.209 [44901.961156] [tdb] Start Tempesta DB Apr 26 04:32:31 192.168.122.209 [44902.095903] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:32:33 192.168.122.209 [44903.603473] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44903.603473] Maybe that's fine, but it's worth checking the [44903.603473] config - if there is no relations between the [44903.603473] names, then host name confusion attack is possible. Apr 26 04:32:33 192.168.122.209 [44903.770265] [tempesta fw] Configuration processing is completed. Apr 26 04:32:33 192.168.122.209 [44903.820138] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:32:33 192.168.122.209 [44904.236923] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:32:33 192.168.122.209 [44904.262324] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:32:33 192.168.122.209 [44904.287753] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:32:33 192.168.122.209 [44904.330192] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:32:33 192.168.122.209 [44904.331867] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:32:34 192.168.122.209 [44904.374134] [tempesta fw] Tempesta FW is ready Apr 26 04:32:34 192.168.122.209 [44904.524172] [tempesta fw] Warning: frang: http_resp_code_block limit exceeded for 127.0.0.2: 2 (lim=1) Apr 26 04:32:34 192.168.122.209 [44904.525519] [tempesta fw] Warning: response blocked: filtered out: 127.0.0.2 Apr 26 04:32:34 192.168.122.209 [44905.036518] [tdb] Close table 'client0.tdb' Apr 26 04:32:34 192.168.122.209 [44905.223139] [tdb] Close table 'sessions0.tdb' Apr 26 04:32:37 192.168.122.209 [44908.359341] [tdb] Close table 'cache0.tdb' Apr 26 04:32:38 192.168.122.209 [44908.577248] [tdb] Close table 'filter0.tdb' Apr 26 04:32:38 192.168.122.209 [44908.577682] [tempesta fw] modules are stopped Apr 26 04:32:38 192.168.122.209 [44908.798591] [tempesta fw] exiting... Apr 26 04:32:38 192.168.122.209 [44908.940524] [tdb] Shutdown Tempesta DB Apr 26 04:32:38 192.168.122.209 [44909.203244] End test: t_frang.test_config.TestOverridingInheritance.test_default_not_override_http_resp_code_block_2 Apr 26 04:32:38 192.168.122.209 [44909.215456] Start test: t_frang.test_config.TestOverridingInheritance.test_default_not_override_http_resp_code_block_3 Apr 26 04:32:40 192.168.122.209 [44910.382437] [tdb] Start Tempesta DB Apr 26 04:32:40 192.168.122.209 [44910.536830] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:32:41 192.168.122.209 [44912.231536] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44912.231536] Maybe that's fine, but it's worth checking the [44912.231536] config - if there is no relations between the [44912.231536] names, then host name confusion attack is possible. Apr 26 04:32:42 192.168.122.209 [44912.386312] [tempesta fw] Configuration processing is completed. Apr 26 04:32:42 192.168.122.209 [44912.436822] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:32:42 192.168.122.209 [44912.847525] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:32:42 192.168.122.209 [44912.873564] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:32:42 192.168.122.209 [44912.899522] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:32:42 192.168.122.209 [44912.966302] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:32:42 192.168.122.209 [44912.967997] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:32:42 192.168.122.209 [44913.014285] [tempesta fw] Tempesta FW is ready Apr 26 04:32:42 192.168.122.209 [44913.155241] [tempesta fw] Warning: frang: http_resp_code_block limit exceeded for 127.0.0.2: 2 (lim=1) Apr 26 04:32:42 192.168.122.209 [44913.157819] [tempesta fw] Warning: response blocked: filtered out: 127.0.0.2 Apr 26 04:32:43 192.168.122.209 [44913.681226] [tdb] Close table 'client0.tdb' Apr 26 04:32:43 192.168.122.209 [44913.893185] [tdb] Close table 'sessions0.tdb' Apr 26 04:32:46 192.168.122.209 [44917.010819] [tdb] Close table 'cache0.tdb' Apr 26 04:32:46 192.168.122.209 [44917.251648] [tdb] Close table 'filter0.tdb' Apr 26 04:32:46 192.168.122.209 [44917.252092] [tempesta fw] modules are stopped Apr 26 04:32:47 192.168.122.209 [44917.486131] [tempesta fw] exiting... Apr 26 04:32:47 192.168.122.209 [44917.624834] [tdb] Shutdown Tempesta DB Apr 26 04:32:47 192.168.122.209 [44917.839037] End test: t_frang.test_config.TestOverridingInheritance.test_default_not_override_http_resp_code_block_3 Apr 26 04:32:47 192.168.122.209 [44917.851214] Start test: t_frang.test_config.TestOverridingInheritance.test_default_override_after_fail_reload_http_body_len Apr 26 04:32:48 192.168.122.209 [44918.966230] [tdb] Start Tempesta DB Apr 26 04:32:48 192.168.122.209 [44919.113054] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:32:50 192.168.122.209 [44920.539636] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44920.539636] Maybe that's fine, but it's worth checking the [44920.539636] config - if there is no relations between the [44920.539636] names, then host name confusion attack is possible. Apr 26 04:32:50 192.168.122.209 [44920.702456] [tempesta fw] Configuration processing is completed. Apr 26 04:32:50 192.168.122.209 [44920.753702] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:32:50 192.168.122.209 [44921.163822] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:32:50 192.168.122.209 [44921.220540] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:32:50 192.168.122.209 [44921.252315] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:32:50 192.168.122.209 [44921.294407] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:32:50 192.168.122.209 [44921.296074] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:32:50 192.168.122.209 [44921.334366] [tempesta fw] Tempesta FW is ready Apr 26 04:32:51 192.168.122.209 [44921.897605] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 04:32:51 192.168.122.209 [44921.995630] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44921.995630] Maybe that's fine, but it's worth checking the [44921.995630] config - if there is no relations between the [44921.995630] names, then host name confusion attack is possible. Apr 26 04:32:51 192.168.122.209 [44922.110527] [tempesta fw] ERROR: parser error Apr 26 04:32:51 192.168.122.209 [44922.111815] [tempesta fw] ERROR: configuration parsing error: [44922.111815] 12: frang_limits { "wrong_config" } [44922.111815] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 04:32:51 192.168.122.209 [44922.116505] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 04:32:52 192.168.122.209 [44922.901806] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 04:32:52 192.168.122.209 [44922.979609] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44922.979609] Maybe that's fine, but it's worth checking the [44922.979609] config - if there is no relations between the [44922.979609] names, then host name confusion attack is possible. Apr 26 04:32:52 192.168.122.209 [44923.178392] [tempesta fw] Configuration processing is completed. Apr 26 04:32:53 192.168.122.209 [44923.386454] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:32:53 192.168.122.209 [44923.388167] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:32:53 192.168.122.209 [44923.446810] [tempesta fw] Tempesta FW is ready Apr 26 04:32:55 192.168.122.209 [44926.183550] [tdb] Close table 'client0.tdb' Apr 26 04:32:55 192.168.122.209 [44926.357781] [tdb] Close table 'sessions0.tdb' Apr 26 04:32:59 192.168.122.209 [44929.536270] [tdb] Close table 'cache0.tdb' Apr 26 04:32:59 192.168.122.209 [44929.780210] [tdb] Close table 'filter0.tdb' Apr 26 04:32:59 192.168.122.209 [44929.780633] [tempesta fw] modules are stopped Apr 26 04:32:59 192.168.122.209 [44929.961819] [tempesta fw] exiting... Apr 26 04:32:59 192.168.122.209 [44930.117517] [tdb] Shutdown Tempesta DB Apr 26 04:32:59 192.168.122.209 [44930.332453] End test: t_frang.test_config.TestOverridingInheritance.test_default_override_after_fail_reload_http_body_len Apr 26 04:32:59 192.168.122.209 [44930.350471] Start test: t_frang.test_config.TestOverridingInheritance.test_default_override_after_fail_reload_http_body_len_1 Apr 26 04:33:01 192.168.122.209 [44931.649115] [tdb] Start Tempesta DB Apr 26 04:33:01 192.168.122.209 [44931.792045] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:33:03 192.168.122.209 [44933.527822] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44933.527822] Maybe that's fine, but it's worth checking the [44933.527822] config - if there is no relations between the [44933.527822] names, then host name confusion attack is possible. Apr 26 04:33:03 192.168.122.209 [44933.686587] [tempesta fw] Configuration processing is completed. Apr 26 04:33:03 192.168.122.209 [44933.750212] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:33:03 192.168.122.209 [44934.171467] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:33:03 192.168.122.209 [44934.197418] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:33:03 192.168.122.209 [44934.223417] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:33:03 192.168.122.209 [44934.278598] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:33:03 192.168.122.209 [44934.280363] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:33:03 192.168.122.209 [44934.338575] [tempesta fw] Tempesta FW is ready Apr 26 04:33:04 192.168.122.209 [44934.904734] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 04:33:04 192.168.122.209 [44934.991877] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44934.991877] Maybe that's fine, but it's worth checking the [44934.991877] config - if there is no relations between the [44934.991877] names, then host name confusion attack is possible. Apr 26 04:33:04 192.168.122.209 [44935.106697] [tempesta fw] ERROR: parser error Apr 26 04:33:04 192.168.122.209 [44935.107954] [tempesta fw] ERROR: configuration parsing error: [44935.107954] 12: frang_limits { "wrong_config" } [44935.107954] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 04:33:04 192.168.122.209 [44935.112695] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 04:33:05 192.168.122.209 [44935.961930] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 04:33:05 192.168.122.209 [44936.051815] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44936.051815] Maybe that's fine, but it's worth checking the [44936.051815] config - if there is no relations between the [44936.051815] names, then host name confusion attack is possible. Apr 26 04:33:05 192.168.122.209 [44936.246663] [tempesta fw] Configuration processing is completed. Apr 26 04:33:06 192.168.122.209 [44936.510574] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:33:06 192.168.122.209 [44936.511130] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:33:06 192.168.122.209 [44936.583084] [tempesta fw] Tempesta FW is ready Apr 26 04:33:08 192.168.122.209 [44939.349468] [tdb] Close table 'client0.tdb' Apr 26 04:33:09 192.168.122.209 [44939.542114] [tdb] Close table 'sessions0.tdb' Apr 26 04:33:12 192.168.122.209 [44942.635768] [tdb] Close table 'cache0.tdb' Apr 26 04:33:12 192.168.122.209 [44942.887386] [tdb] Close table 'filter0.tdb' Apr 26 04:33:12 192.168.122.209 [44942.887848] [tempesta fw] modules are stopped Apr 26 04:33:12 192.168.122.209 [44943.099308] [tempesta fw] exiting... Apr 26 04:33:12 192.168.122.209 [44943.230637] [tdb] Shutdown Tempesta DB Apr 26 04:33:13 192.168.122.209 [44943.433396] End test: t_frang.test_config.TestOverridingInheritance.test_default_override_after_fail_reload_http_body_len_1 Apr 26 04:33:13 192.168.122.209 [44943.446463] Start test: t_frang.test_config.TestOverridingInheritance.test_default_override_after_fail_reload_http_body_len_3 Apr 26 04:33:14 192.168.122.209 [44944.630363] [tdb] Start Tempesta DB Apr 26 04:33:14 192.168.122.209 [44944.778874] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:33:16 192.168.122.209 [44946.415965] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44946.415965] Maybe that's fine, but it's worth checking the [44946.415965] config - if there is no relations between the [44946.415965] names, then host name confusion attack is possible. Apr 26 04:33:16 192.168.122.209 [44946.566762] [tempesta fw] Configuration processing is completed. Apr 26 04:33:16 192.168.122.209 [44946.616808] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:33:16 192.168.122.209 [44947.020982] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:33:16 192.168.122.209 [44947.076681] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:33:16 192.168.122.209 [44947.102783] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:33:16 192.168.122.209 [44947.170768] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:33:16 192.168.122.209 [44947.172490] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:33:16 192.168.122.209 [44947.206634] [tempesta fw] Tempesta FW is ready Apr 26 04:33:17 192.168.122.209 [44947.760595] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 04:33:17 192.168.122.209 [44947.851906] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44947.851906] Maybe that's fine, but it's worth checking the [44947.851906] config - if there is no relations between the [44947.851906] names, then host name confusion attack is possible. Apr 26 04:33:17 192.168.122.209 [44947.978344] [tempesta fw] ERROR: parser error Apr 26 04:33:17 192.168.122.209 [44947.979660] [tempesta fw] ERROR: configuration parsing error: [44947.979660] 12: frang_limits { "wrong_config" } [44947.979660] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 04:33:17 192.168.122.209 [44947.982227] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 04:33:18 192.168.122.209 [44948.862412] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 04:33:18 192.168.122.209 [44948.947976] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44948.947976] Maybe that's fine, but it's worth checking the [44948.947976] config - if there is no relations between the [44948.947976] names, then host name confusion attack is possible. Apr 26 04:33:18 192.168.122.209 [44949.130769] [tempesta fw] Configuration processing is completed. Apr 26 04:33:19 192.168.122.209 [44949.382862] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:33:19 192.168.122.209 [44949.384623] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:33:19 192.168.122.209 [44949.443219] [tempesta fw] Tempesta FW is ready Apr 26 04:33:21 192.168.122.209 [44952.147859] [tdb] Close table 'client0.tdb' Apr 26 04:33:21 192.168.122.209 [44952.336049] [tdb] Close table 'sessions0.tdb' Apr 26 04:33:25 192.168.122.209 [44955.498515] [tdb] Close table 'cache0.tdb' Apr 26 04:33:25 192.168.122.209 [44955.735709] [tdb] Close table 'filter0.tdb' Apr 26 04:33:25 192.168.122.209 [44955.736142] [tempesta fw] modules are stopped Apr 26 04:33:25 192.168.122.209 [44955.943049] [tempesta fw] exiting... Apr 26 04:33:25 192.168.122.209 [44956.075052] [tdb] Shutdown Tempesta DB Apr 26 04:33:25 192.168.122.209 [44956.298031] End test: t_frang.test_config.TestOverridingInheritance.test_default_override_after_fail_reload_http_body_len_3 Apr 26 04:33:25 192.168.122.209 [44956.312875] Start test: t_frang.test_config.TestOverridingInheritance.test_default_override_after_fail_reload_http_ct_vals_1 Apr 26 04:33:27 192.168.122.209 [44957.400885] [tdb] Start Tempesta DB Apr 26 04:33:27 192.168.122.209 [44957.542893] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:33:29 192.168.122.209 [44959.384190] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44959.384190] Maybe that's fine, but it's worth checking the [44959.384190] config - if there is no relations between the [44959.384190] names, then host name confusion attack is possible. Apr 26 04:33:29 192.168.122.209 [44959.586987] [tempesta fw] Configuration processing is completed. Apr 26 04:33:29 192.168.122.209 [44959.643933] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:33:29 192.168.122.209 [44960.075545] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:33:29 192.168.122.209 [44960.100850] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:33:29 192.168.122.209 [44960.126526] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:33:29 192.168.122.209 [44960.182879] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:33:29 192.168.122.209 [44960.184045] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:33:29 192.168.122.209 [44960.226850] [tempesta fw] Tempesta FW is ready Apr 26 04:33:30 192.168.122.209 [44960.750100] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 04:33:30 192.168.122.209 [44960.840113] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44960.840113] Maybe that's fine, but it's worth checking the [44960.840113] config - if there is no relations between the [44960.840113] names, then host name confusion attack is possible. Apr 26 04:33:30 192.168.122.209 [44960.963015] [tempesta fw] ERROR: parser error Apr 26 04:33:30 192.168.122.209 [44960.964273] [tempesta fw] ERROR: configuration parsing error: [44960.964273] 12: frang_limits { "wrong_config" } [44960.964273] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 04:33:30 192.168.122.209 [44960.968957] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 04:33:31 192.168.122.209 [44962.109815] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 04:33:31 192.168.122.209 [44962.200064] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44962.200064] Maybe that's fine, but it's worth checking the [44962.200064] config - if there is no relations between the [44962.200064] names, then host name confusion attack is possible. Apr 26 04:33:32 192.168.122.209 [44962.455011] [tempesta fw] Configuration processing is completed. Apr 26 04:33:32 192.168.122.209 [44962.712151] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:33:32 192.168.122.209 [44962.713892] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:33:32 192.168.122.209 [44962.771641] [tempesta fw] Tempesta FW is ready Apr 26 04:33:34 192.168.122.209 [44965.094134] [tempesta fw] Warning: frang: restricted Content-Type for 127.0.0.2: text/ Apr 26 04:33:34 192.168.122.209 [44965.094925] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:33:35 192.168.122.209 [44965.581836] [tdb] Close table 'client0.tdb' Apr 26 04:33:35 192.168.122.209 [44965.781669] [tdb] Close table 'sessions0.tdb' Apr 26 04:33:38 192.168.122.209 [44968.894052] [tdb] Close table 'cache0.tdb' Apr 26 04:33:38 192.168.122.209 [44969.108035] [tdb] Close table 'filter0.tdb' Apr 26 04:33:38 192.168.122.209 [44969.108456] [tempesta fw] modules are stopped Apr 26 04:33:38 192.168.122.209 [44969.371926] [tempesta fw] exiting... Apr 26 04:33:39 192.168.122.209 [44969.517825] [tdb] Shutdown Tempesta DB Apr 26 04:33:39 192.168.122.209 [44969.749968] End test: t_frang.test_config.TestOverridingInheritance.test_default_override_after_fail_reload_http_ct_vals_1 Apr 26 04:33:39 192.168.122.209 [44969.767460] Start test: t_frang.test_config.TestOverridingInheritance.test_default_override_after_fail_reload_http_ct_vals_2 Apr 26 04:33:40 192.168.122.209 [44970.925684] [tdb] Start Tempesta DB Apr 26 04:33:40 192.168.122.209 [44971.066787] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:33:42 192.168.122.209 [44972.940335] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44972.940335] Maybe that's fine, but it's worth checking the [44972.940335] config - if there is no relations between the [44972.940335] names, then host name confusion attack is possible. Apr 26 04:33:42 192.168.122.209 [44973.159144] [tempesta fw] Configuration processing is completed. Apr 26 04:33:42 192.168.122.209 [44973.213602] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:33:43 192.168.122.209 [44973.622203] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:33:43 192.168.122.209 [44973.647734] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:33:43 192.168.122.209 [44973.673710] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:33:43 192.168.122.209 [44973.715074] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:33:43 192.168.122.209 [44973.716788] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:33:43 192.168.122.209 [44973.763033] [tempesta fw] Tempesta FW is ready Apr 26 04:33:43 192.168.122.209 [44974.298363] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 04:33:44 192.168.122.209 [44974.375821] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44974.375821] Maybe that's fine, but it's worth checking the [44974.375821] config - if there is no relations between the [44974.375821] names, then host name confusion attack is possible. Apr 26 04:33:44 192.168.122.209 [44974.467200] [tempesta fw] ERROR: parser error Apr 26 04:33:44 192.168.122.209 [44974.468460] [tempesta fw] ERROR: configuration parsing error: [44974.468460] 12: frang_limits { "wrong_config" } [44974.468460] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 04:33:44 192.168.122.209 [44974.473139] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 04:33:45 192.168.122.209 [44975.664759] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 04:33:45 192.168.122.209 [44975.756247] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44975.756247] Maybe that's fine, but it's worth checking the [44975.756247] config - if there is no relations between the [44975.756247] names, then host name confusion attack is possible. Apr 26 04:33:45 192.168.122.209 [44976.003170] [tempesta fw] Configuration processing is completed. Apr 26 04:33:45 192.168.122.209 [44976.275056] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:33:45 192.168.122.209 [44976.275635] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:33:45 192.168.122.209 [44976.347304] [tempesta fw] Tempesta FW is ready Apr 26 04:33:48 192.168.122.209 [44978.674280] [tempesta fw] Warning: frang: restricted Content-Type for 127.0.0.2: text/ Apr 26 04:33:48 192.168.122.209 [44978.676513] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:33:48 192.168.122.209 [44979.188685] [tdb] Close table 'client0.tdb' Apr 26 04:33:49 192.168.122.209 [44979.382311] [tdb] Close table 'sessions0.tdb' Apr 26 04:33:52 192.168.122.209 [44982.439242] [tdb] Close table 'cache0.tdb' Apr 26 04:33:52 192.168.122.209 [44982.685787] [tdb] Close table 'filter0.tdb' Apr 26 04:33:52 192.168.122.209 [44982.686205] [tempesta fw] modules are stopped Apr 26 04:33:52 192.168.122.209 [44982.910362] [tempesta fw] exiting... Apr 26 04:33:52 192.168.122.209 [44983.069347] [tdb] Shutdown Tempesta DB Apr 26 04:33:52 192.168.122.209 [44983.274190] End test: t_frang.test_config.TestOverridingInheritance.test_default_override_after_fail_reload_http_ct_vals_2 Apr 26 04:33:52 192.168.122.209 [44983.291181] Start test: t_frang.test_config.TestOverridingInheritance.test_default_override_after_fail_reload_http_ct_vals_3 Apr 26 04:33:54 192.168.122.209 [44984.464826] [tdb] Start Tempesta DB Apr 26 04:33:54 192.168.122.209 [44984.606759] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:33:56 192.168.122.209 [44986.552534] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44986.552534] Maybe that's fine, but it's worth checking the [44986.552534] config - if there is no relations between the [44986.552534] names, then host name confusion attack is possible. Apr 26 04:33:56 192.168.122.209 [44986.823314] [tempesta fw] Configuration processing is completed. Apr 26 04:33:56 192.168.122.209 [44986.879723] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:33:56 192.168.122.209 [44987.309602] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:33:56 192.168.122.209 [44987.335120] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:33:56 192.168.122.209 [44987.360294] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:33:57 192.168.122.209 [44987.403302] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:33:57 192.168.122.209 [44987.405048] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:33:57 192.168.122.209 [44987.451202] [tempesta fw] Tempesta FW is ready Apr 26 04:33:57 192.168.122.209 [44987.960226] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 04:33:57 192.168.122.209 [44988.056425] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44988.056425] Maybe that's fine, but it's worth checking the [44988.056425] config - if there is no relations between the [44988.056425] names, then host name confusion attack is possible. Apr 26 04:33:57 192.168.122.209 [44988.191364] [tempesta fw] ERROR: parser error Apr 26 04:33:57 192.168.122.209 [44988.192641] [tempesta fw] ERROR: configuration parsing error: [44988.192641] 12: frang_limits { "wrong_config" } [44988.192641] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 04:33:57 192.168.122.209 [44988.197331] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 04:33:58 192.168.122.209 [44989.239561] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 04:33:58 192.168.122.209 [44989.347314] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44989.347314] Maybe that's fine, but it's worth checking the [44989.347314] config - if there is no relations between the [44989.347314] names, then host name confusion attack is possible. Apr 26 04:33:59 192.168.122.209 [44989.603327] [tempesta fw] Configuration processing is completed. Apr 26 04:33:59 192.168.122.209 [44989.847359] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:33:59 192.168.122.209 [44989.849138] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:33:59 192.168.122.209 [44989.907952] [tempesta fw] Tempesta FW is ready Apr 26 04:34:01 192.168.122.209 [44992.228217] [tempesta fw] Warning: frang: restricted Content-Type for 127.0.0.2: text/ Apr 26 04:34:01 192.168.122.209 [44992.228958] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:34:02 192.168.122.209 [44992.739383] [tdb] Close table 'client0.tdb' Apr 26 04:34:02 192.168.122.209 [44992.912345] [tdb] Close table 'sessions0.tdb' Apr 26 04:34:05 192.168.122.209 [44996.021727] [tdb] Close table 'cache0.tdb' Apr 26 04:34:05 192.168.122.209 [44996.268417] [tdb] Close table 'filter0.tdb' Apr 26 04:34:05 192.168.122.209 [44996.268854] [tempesta fw] modules are stopped Apr 26 04:34:06 192.168.122.209 [44996.524371] [tempesta fw] exiting... Apr 26 04:34:06 192.168.122.209 [44996.669132] [tdb] Shutdown Tempesta DB Apr 26 04:34:06 192.168.122.209 [44996.887974] End test: t_frang.test_config.TestOverridingInheritance.test_default_override_after_fail_reload_http_ct_vals_3 Apr 26 04:34:06 192.168.122.209 [44996.901419] Start test: t_frang.test_config.TestOverridingInheritance.test_default_override_after_fail_reload_http_methods Apr 26 04:34:07 192.168.122.209 [44998.055970] [tdb] Start Tempesta DB Apr 26 04:34:07 192.168.122.209 [44998.198326] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:34:09 192.168.122.209 [44999.592639] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [44999.592639] Maybe that's fine, but it's worth checking the [44999.592639] config - if there is no relations between the [44999.592639] names, then host name confusion attack is possible. Apr 26 04:34:09 192.168.122.209 [44999.747440] [tempesta fw] Configuration processing is completed. Apr 26 04:34:09 192.168.122.209 [44999.798007] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:34:09 192.168.122.209 [45000.202644] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:34:09 192.168.122.209 [45000.227773] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:34:09 192.168.122.209 [45000.253265] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:34:09 192.168.122.209 [45000.299423] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:34:09 192.168.122.209 [45000.301163] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:34:09 192.168.122.209 [45000.359443] [tempesta fw] Tempesta FW is ready Apr 26 04:34:10 192.168.122.209 [45000.891573] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 04:34:10 192.168.122.209 [45000.980545] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45000.980545] Maybe that's fine, but it's worth checking the [45000.980545] config - if there is no relations between the [45000.980545] names, then host name confusion attack is possible. Apr 26 04:34:10 192.168.122.209 [45001.115539] [tempesta fw] ERROR: parser error Apr 26 04:34:10 192.168.122.209 [45001.116798] [tempesta fw] ERROR: configuration parsing error: [45001.116798] 12: frang_limits { "wrong_config" } [45001.116798] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 04:34:10 192.168.122.209 [45001.121540] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 04:34:11 192.168.122.209 [45001.845926] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 04:34:11 192.168.122.209 [45001.940671] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45001.940671] Maybe that's fine, but it's worth checking the [45001.940671] config - if there is no relations between the [45001.940671] names, then host name confusion attack is possible. Apr 26 04:34:11 192.168.122.209 [45002.115482] [tempesta fw] Configuration processing is completed. Apr 26 04:34:11 192.168.122.209 [45002.315415] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:34:11 192.168.122.209 [45002.317156] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:34:11 192.168.122.209 [45002.371720] [tempesta fw] Tempesta FW is ready Apr 26 04:34:14 192.168.122.209 [45005.146951] [tdb] Close table 'client0.tdb' Apr 26 04:34:14 192.168.122.209 [45005.331024] [tdb] Close table 'sessions0.tdb' Apr 26 04:34:18 192.168.122.209 [45008.434159] [tdb] Close table 'cache0.tdb' Apr 26 04:34:18 192.168.122.209 [45008.674543] [tdb] Close table 'filter0.tdb' Apr 26 04:34:18 192.168.122.209 [45008.674981] [tempesta fw] modules are stopped Apr 26 04:34:18 192.168.122.209 [45008.891561] [tempesta fw] exiting... Apr 26 04:34:18 192.168.122.209 [45009.038180] [tdb] Shutdown Tempesta DB Apr 26 04:34:18 192.168.122.209 [45009.248904] End test: t_frang.test_config.TestOverridingInheritance.test_default_override_after_fail_reload_http_methods Apr 26 04:34:18 192.168.122.209 [45009.271524] Start test: t_frang.test_config.TestOverridingInheritance.test_default_override_after_fail_reload_http_methods_1 Apr 26 04:34:20 192.168.122.209 [45010.420799] [tdb] Start Tempesta DB Apr 26 04:34:20 192.168.122.209 [45010.556556] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:34:21 192.168.122.209 [45012.232835] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45012.232835] Maybe that's fine, but it's worth checking the [45012.232835] config - if there is no relations between the [45012.232835] names, then host name confusion attack is possible. Apr 26 04:34:22 192.168.122.209 [45012.391599] [tempesta fw] Configuration processing is completed. Apr 26 04:34:22 192.168.122.209 [45012.442272] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:34:22 192.168.122.209 [45012.856491] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:34:22 192.168.122.209 [45012.882557] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:34:22 192.168.122.209 [45012.908774] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:34:22 192.168.122.209 [45012.951608] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:34:22 192.168.122.209 [45012.953356] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:34:22 192.168.122.209 [45012.991535] [tempesta fw] Tempesta FW is ready Apr 26 04:34:23 192.168.122.209 [45013.537880] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 04:34:23 192.168.122.209 [45013.632753] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45013.632753] Maybe that's fine, but it's worth checking the [45013.632753] config - if there is no relations between the [45013.632753] names, then host name confusion attack is possible. Apr 26 04:34:23 192.168.122.209 [45013.747809] [tempesta fw] ERROR: parser error Apr 26 04:34:23 192.168.122.209 [45013.749058] [tempesta fw] ERROR: configuration parsing error: [45013.749058] 12: frang_limits { "wrong_config" } [45013.749058] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 04:34:23 192.168.122.209 [45013.753770] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 04:34:24 192.168.122.209 [45014.722761] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 04:34:24 192.168.122.209 [45014.824734] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45014.824734] Maybe that's fine, but it's worth checking the [45014.824734] config - if there is no relations between the [45014.824734] names, then host name confusion attack is possible. Apr 26 04:34:24 192.168.122.209 [45015.047646] [tempesta fw] Configuration processing is completed. Apr 26 04:34:24 192.168.122.209 [45015.299777] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:34:24 192.168.122.209 [45015.301553] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:34:25 192.168.122.209 [45015.380054] [tempesta fw] Tempesta FW is ready Apr 26 04:34:27 192.168.122.209 [45018.106452] [tdb] Close table 'client0.tdb' Apr 26 04:34:27 192.168.122.209 [45018.294430] [tdb] Close table 'sessions0.tdb' Apr 26 04:34:31 192.168.122.209 [45021.417023] [tdb] Close table 'cache0.tdb' Apr 26 04:34:31 192.168.122.209 [45021.653482] [tdb] Close table 'filter0.tdb' Apr 26 04:34:31 192.168.122.209 [45021.653911] [tempesta fw] modules are stopped Apr 26 04:34:31 192.168.122.209 [45021.910672] [tempesta fw] exiting... Apr 26 04:34:31 192.168.122.209 [45022.046349] [tdb] Shutdown Tempesta DB Apr 26 04:34:31 192.168.122.209 [45022.232930] End test: t_frang.test_config.TestOverridingInheritance.test_default_override_after_fail_reload_http_methods_1 Apr 26 04:34:31 192.168.122.209 [45022.254638] Start test: t_frang.test_config.TestOverridingInheritance.test_default_override_after_reload_http_methods Apr 26 04:34:33 192.168.122.209 [45023.441360] [tdb] Start Tempesta DB Apr 26 04:34:33 192.168.122.209 [45023.590763] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:34:34 192.168.122.209 [45025.020991] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45025.020991] Maybe that's fine, but it's worth checking the [45025.020991] config - if there is no relations between the [45025.020991] names, then host name confusion attack is possible. Apr 26 04:34:34 192.168.122.209 [45025.175747] [tempesta fw] Configuration processing is completed. Apr 26 04:34:34 192.168.122.209 [45025.229523] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:34:35 192.168.122.209 [45025.671747] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:34:35 192.168.122.209 [45025.730750] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:34:35 192.168.122.209 [45025.757817] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:34:35 192.168.122.209 [45025.807763] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:34:35 192.168.122.209 [45025.809544] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:34:35 192.168.122.209 [45025.851695] [tempesta fw] Tempesta FW is ready Apr 26 04:34:36 192.168.122.209 [45026.403433] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 04:34:36 192.168.122.209 [45026.500994] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45026.500994] Maybe that's fine, but it's worth checking the [45026.500994] config - if there is no relations between the [45026.500994] names, then host name confusion attack is possible. Apr 26 04:34:36 192.168.122.209 [45026.655791] [tempesta fw] Configuration processing is completed. Apr 26 04:34:36 192.168.122.209 [45026.940103] [tempesta fw] Tempesta FW is ready Apr 26 04:34:39 192.168.122.209 [45029.689696] [tdb] Close table 'client0.tdb' Apr 26 04:34:39 192.168.122.209 [45029.877124] [tdb] Close table 'sessions0.tdb' Apr 26 04:34:42 192.168.122.209 [45033.092514] [tdb] Close table 'cache0.tdb' Apr 26 04:34:42 192.168.122.209 [45033.360341] [tdb] Close table 'filter0.tdb' Apr 26 04:34:42 192.168.122.209 [45033.360767] [tempesta fw] modules are stopped Apr 26 04:34:43 192.168.122.209 [45033.556642] [tempesta fw] exiting... Apr 26 04:34:43 192.168.122.209 [45033.696228] [tdb] Shutdown Tempesta DB Apr 26 04:34:43 192.168.122.209 [45033.911841] End test: t_frang.test_config.TestOverridingInheritance.test_default_override_after_reload_http_methods Apr 26 04:34:43 192.168.122.209 [45033.921451] Start test: t_frang.test_config.TestOverridingInheritance.test_inheritance_default_to_several_location_via_vhost Apr 26 04:34:44 192.168.122.209 [45035.061296] [tdb] Start Tempesta DB Apr 26 04:34:44 192.168.122.209 [45035.224929] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:34:46 192.168.122.209 [45036.793209] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45036.793209] Maybe that's fine, but it's worth checking the [45036.793209] config - if there is no relations between the [45036.793209] names, then host name confusion attack is possible. Apr 26 04:34:46 192.168.122.209 [45036.967903] [tempesta fw] Configuration processing is completed. Apr 26 04:34:46 192.168.122.209 [45037.020614] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:34:47 192.168.122.209 [45037.471132] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:34:47 192.168.122.209 [45037.500323] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:34:47 192.168.122.209 [45037.528768] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:34:47 192.168.122.209 [45037.571913] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:34:47 192.168.122.209 [45037.573681] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:34:47 192.168.122.209 [45037.615860] [tempesta fw] Tempesta FW is ready Apr 26 04:34:47 192.168.122.209 [45038.281395] [tdb] Close table 'client0.tdb' Apr 26 04:34:48 192.168.122.209 [45038.472692] [tdb] Close table 'sessions0.tdb' Apr 26 04:34:51 192.168.122.209 [45041.619926] [tdb] Close table 'cache0.tdb' Apr 26 04:34:51 192.168.122.209 [45041.879330] [tdb] Close table 'filter0.tdb' Apr 26 04:34:51 192.168.122.209 [45041.879808] [tempesta fw] modules are stopped Apr 26 04:34:51 192.168.122.209 [45042.106421] [tempesta fw] exiting... Apr 26 04:34:51 192.168.122.209 [45042.280104] [tdb] Shutdown Tempesta DB Apr 26 04:34:52 192.168.122.209 [45042.492351] End test: t_frang.test_config.TestOverridingInheritance.test_inheritance_default_to_several_location_via_vhost Apr 26 04:34:52 192.168.122.209 [45042.502681] Start test: t_frang.test_config.TestOverridingInheritance.test_inheritance_default_to_several_vhost Apr 26 04:34:53 192.168.122.209 [45043.715769] [tdb] Start Tempesta DB Apr 26 04:34:53 192.168.122.209 [45043.868372] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:34:55 192.168.122.209 [45045.381308] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45045.381308] Maybe that's fine, but it's worth checking the [45045.381308] config - if there is no relations between the [45045.381308] names, then host name confusion attack is possible. Apr 26 04:34:55 192.168.122.209 [45045.572033] [tempesta fw] Configuration processing is completed. Apr 26 04:34:55 192.168.122.209 [45045.628047] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:34:55 192.168.122.209 [45046.083348] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:34:55 192.168.122.209 [45046.142541] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:34:55 192.168.122.209 [45046.170933] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:34:55 192.168.122.209 [45046.248012] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:34:55 192.168.122.209 [45046.249694] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:34:55 192.168.122.209 [45046.291946] [tempesta fw] Tempesta FW is ready Apr 26 04:34:56 192.168.122.209 [45046.960065] [tdb] Close table 'client0.tdb' Apr 26 04:34:56 192.168.122.209 [45047.161640] [tdb] Close table 'sessions0.tdb' Apr 26 04:35:00 192.168.122.209 [45050.385016] [tdb] Close table 'cache0.tdb' Apr 26 04:35:00 192.168.122.209 [45050.651907] [tdb] Close table 'filter0.tdb' Apr 26 04:35:00 192.168.122.209 [45050.652331] [tempesta fw] modules are stopped Apr 26 04:35:00 192.168.122.209 [45050.938182] [tempesta fw] exiting... Apr 26 04:35:00 192.168.122.209 [45051.109637] [tdb] Shutdown Tempesta DB Apr 26 04:35:00 192.168.122.209 [45051.344085] End test: t_frang.test_config.TestOverridingInheritance.test_inheritance_default_to_several_vhost Apr 26 04:35:00 192.168.122.209 [45051.366325] Start test: t_frang.test_config.TestOverridingInheritance.test_inheritance_global_to_location Apr 26 04:35:02 192.168.122.209 [45052.508469] [tdb] Start Tempesta DB Apr 26 04:35:02 192.168.122.209 [45052.654433] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:35:03 192.168.122.209 [45054.141707] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45054.141707] Maybe that's fine, but it's worth checking the [45054.141707] config - if there is no relations between the [45054.141707] names, then host name confusion attack is possible. Apr 26 04:35:03 192.168.122.209 [45054.312133] [tempesta fw] Configuration processing is completed. Apr 26 04:35:03 192.168.122.209 [45054.364483] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:35:04 192.168.122.209 [45054.820885] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:35:04 192.168.122.209 [45054.852356] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:35:04 192.168.122.209 [45054.883364] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:35:04 192.168.122.209 [45054.944101] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:35:04 192.168.122.209 [45054.945854] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:35:04 192.168.122.209 [45054.984049] [tempesta fw] Tempesta FW is ready Apr 26 04:35:04 192.168.122.209 [45055.137719] [tempesta fw] Warning: frang: restricted HTTP method for 127.0.0.2: 3 (0x8u) Apr 26 04:35:04 192.168.122.209 [45055.138813] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:35:05 192.168.122.209 [45055.654468] [tdb] Close table 'client0.tdb' Apr 26 04:35:05 192.168.122.209 [45055.845292] [tdb] Close table 'sessions0.tdb' Apr 26 04:35:08 192.168.122.209 [45058.969747] [tdb] Close table 'cache0.tdb' Apr 26 04:35:08 192.168.122.209 [45059.183212] [tdb] Close table 'filter0.tdb' Apr 26 04:35:08 192.168.122.209 [45059.183643] [tempesta fw] modules are stopped Apr 26 04:35:09 192.168.122.209 [45059.427762] [tempesta fw] exiting... Apr 26 04:35:09 192.168.122.209 [45059.576671] [tdb] Shutdown Tempesta DB Apr 26 04:35:09 192.168.122.209 [45059.789228] End test: t_frang.test_config.TestOverridingInheritance.test_inheritance_global_to_location Apr 26 04:35:09 192.168.122.209 [45059.800990] Start test: t_frang.test_config.TestOverridingInheritance.test_inheritance_global_to_location_via_vhost Apr 26 04:35:10 192.168.122.209 [45060.960644] [tdb] Start Tempesta DB Apr 26 04:35:10 192.168.122.209 [45061.097807] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:35:12 192.168.122.209 [45062.649514] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45062.649514] Maybe that's fine, but it's worth checking the [45062.649514] config - if there is no relations between the [45062.649514] names, then host name confusion attack is possible. Apr 26 04:35:12 192.168.122.209 [45062.832231] [tempesta fw] Configuration processing is completed. Apr 26 04:35:12 192.168.122.209 [45062.890695] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:35:12 192.168.122.209 [45063.299032] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:35:12 192.168.122.209 [45063.355578] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:35:13 192.168.122.209 [45063.381179] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:35:13 192.168.122.209 [45063.424220] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:35:13 192.168.122.209 [45063.425883] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:35:13 192.168.122.209 [45063.476166] [tempesta fw] Tempesta FW is ready Apr 26 04:35:13 192.168.122.209 [45063.614464] [tempesta fw] Warning: frang: restricted HTTP method for 127.0.0.2: 3 (0x8u) Apr 26 04:35:13 192.168.122.209 [45063.616727] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:35:13 192.168.122.209 [45064.151474] [tdb] Close table 'client0.tdb' Apr 26 04:35:13 192.168.122.209 [45064.341480] [tdb] Close table 'sessions0.tdb' Apr 26 04:35:17 192.168.122.209 [45067.456425] [tdb] Close table 'cache0.tdb' Apr 26 04:35:17 192.168.122.209 [45067.698087] [tdb] Close table 'filter0.tdb' Apr 26 04:35:17 192.168.122.209 [45067.698520] [tempesta fw] modules are stopped Apr 26 04:35:17 192.168.122.209 [45067.935887] [tempesta fw] exiting... Apr 26 04:35:17 192.168.122.209 [45068.093917] [tdb] Shutdown Tempesta DB Apr 26 04:35:17 192.168.122.209 [45068.288822] End test: t_frang.test_config.TestOverridingInheritance.test_inheritance_global_to_location_via_vhost Apr 26 04:35:17 192.168.122.209 [45068.303036] Start test: t_frang.test_config.TestOverridingInheritance.test_inheritance_global_to_vhost Apr 26 04:35:19 192.168.122.209 [45069.482271] [tdb] Start Tempesta DB Apr 26 04:35:19 192.168.122.209 [45069.625708] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:35:20 192.168.122.209 [45071.137554] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45071.137554] Maybe that's fine, but it's worth checking the [45071.137554] config - if there is no relations between the [45071.137554] names, then host name confusion attack is possible. Apr 26 04:35:20 192.168.122.209 [45071.328352] [tempesta fw] Configuration processing is completed. Apr 26 04:35:21 192.168.122.209 [45071.379987] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:35:21 192.168.122.209 [45071.783588] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:35:21 192.168.122.209 [45071.839576] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:35:21 192.168.122.209 [45071.866152] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:35:21 192.168.122.209 [45071.908330] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:35:21 192.168.122.209 [45071.910058] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:35:21 192.168.122.209 [45071.976258] [tempesta fw] Tempesta FW is ready Apr 26 04:35:21 192.168.122.209 [45072.118272] [tempesta fw] Warning: frang: restricted HTTP method for 127.0.0.2: 3 (0x8u) Apr 26 04:35:21 192.168.122.209 [45072.120404] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:35:22 192.168.122.209 [45072.616973] [tdb] Close table 'client0.tdb' Apr 26 04:35:22 192.168.122.209 [45072.809170] [tdb] Close table 'sessions0.tdb' Apr 26 04:35:25 192.168.122.209 [45076.036711] [tdb] Close table 'cache0.tdb' Apr 26 04:35:25 192.168.122.209 [45076.290085] [tdb] Close table 'filter0.tdb' Apr 26 04:35:25 192.168.122.209 [45076.290518] [tempesta fw] modules are stopped Apr 26 04:35:26 192.168.122.209 [45076.539523] [tempesta fw] exiting... Apr 26 04:35:26 192.168.122.209 [45076.683035] [tdb] Shutdown Tempesta DB Apr 26 04:35:26 192.168.122.209 [45076.875078] End test: t_frang.test_config.TestOverridingInheritance.test_inheritance_global_to_vhost Apr 26 04:35:26 192.168.122.209 [45076.883050] Start test: t_frang.test_config.TestOverridingInheritance.test_inheritance_vhost_to_location Apr 26 04:35:27 192.168.122.209 [45078.041597] [tdb] Start Tempesta DB Apr 26 04:35:27 192.168.122.209 [45078.185199] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:35:29 192.168.122.209 [45079.809795] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45079.809795] Maybe that's fine, but it's worth checking the [45079.809795] config - if there is no relations between the [45079.809795] names, then host name confusion attack is possible. Apr 26 04:35:29 192.168.122.209 [45079.984505] [tempesta fw] Configuration processing is completed. Apr 26 04:35:29 192.168.122.209 [45080.050297] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:35:30 192.168.122.209 [45080.482161] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:35:30 192.168.122.209 [45080.509678] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:35:30 192.168.122.209 [45080.536947] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:35:30 192.168.122.209 [45080.588456] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:35:30 192.168.122.209 [45080.590168] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:35:30 192.168.122.209 [45080.636396] [tempesta fw] Tempesta FW is ready Apr 26 04:35:30 192.168.122.209 [45080.776401] [tempesta fw] Warning: frang: restricted HTTP method for 127.0.0.2: 3 (0x8u) Apr 26 04:35:30 192.168.122.209 [45080.777749] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:35:30 192.168.122.209 [45081.328424] [tdb] Close table 'client0.tdb' Apr 26 04:35:31 192.168.122.209 [45081.524432] [tdb] Close table 'sessions0.tdb' Apr 26 04:35:34 192.168.122.209 [45084.672816] [tdb] Close table 'cache0.tdb' Apr 26 04:35:34 192.168.122.209 [45084.927213] [tdb] Close table 'filter0.tdb' Apr 26 04:35:34 192.168.122.209 [45084.927664] [tempesta fw] modules are stopped Apr 26 04:35:34 192.168.122.209 [45085.149730] [tempesta fw] exiting... Apr 26 04:35:34 192.168.122.209 [45085.294959] [tdb] Shutdown Tempesta DB Apr 26 04:35:35 192.168.122.209 [45085.486360] End test: t_frang.test_config.TestOverridingInheritance.test_inheritance_vhost_to_location Apr 26 04:35:35 192.168.122.209 [45085.502323] Start test: t_frang.test_config.TestOverridingInheritance.test_inheritance_vhost_to_location_limits_after_location Apr 26 04:35:36 192.168.122.209 [45086.672332] [tdb] Start Tempesta DB Apr 26 04:35:36 192.168.122.209 [45086.820055] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:35:38 192.168.122.209 [45088.377828] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45088.377828] Maybe that's fine, but it's worth checking the [45088.377828] config - if there is no relations between the [45088.377828] names, then host name confusion attack is possible. Apr 26 04:35:38 192.168.122.209 [45088.544544] [tempesta fw] Configuration processing is completed. Apr 26 04:35:38 192.168.122.209 [45088.594361] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:35:38 192.168.122.209 [45088.995593] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:35:38 192.168.122.209 [45089.056080] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:35:38 192.168.122.209 [45089.081701] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:35:38 192.168.122.209 [45089.124536] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:35:38 192.168.122.209 [45089.126202] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:35:38 192.168.122.209 [45089.180486] [tempesta fw] Tempesta FW is ready Apr 26 04:35:39 192.168.122.209 [45089.399491] [tempesta fw] Warning: frang: restricted HTTP method for 127.0.0.2: 4 (0x10u) Apr 26 04:35:39 192.168.122.209 [45089.401756] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:35:39 192.168.122.209 [45089.880777] [tdb] Close table 'client0.tdb' Apr 26 04:35:39 192.168.122.209 [45090.087143] [tdb] Close table 'sessions0.tdb' Apr 26 04:35:42 192.168.122.209 [45093.181078] [tdb] Close table 'cache0.tdb' Apr 26 04:35:43 192.168.122.209 [45093.417910] [tdb] Close table 'filter0.tdb' Apr 26 04:35:43 192.168.122.209 [45093.418312] [tempesta fw] modules are stopped Apr 26 04:35:43 192.168.122.209 [45093.656889] [tempesta fw] exiting... Apr 26 04:35:43 192.168.122.209 [45093.768741] [tdb] Shutdown Tempesta DB Apr 26 04:35:43 192.168.122.209 [45093.988997] End test: t_frang.test_config.TestOverridingInheritance.test_inheritance_vhost_to_location_limits_after_location Apr 26 04:35:43 192.168.122.209 [45093.999907] Start test: t_frang.test_config.TestOverridingInheritance.test_overriding_global_to_location Apr 26 04:35:44 192.168.122.209 [45095.234918] [tdb] Start Tempesta DB Apr 26 04:35:45 192.168.122.209 [45095.387225] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:35:47 192.168.122.209 [45097.710109] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45097.710109] Maybe that's fine, but it's worth checking the [45097.710109] config - if there is no relations between the [45097.710109] names, then host name confusion attack is possible. Apr 26 04:35:48 192.168.122.209 [45098.716749] [tempesta fw] Configuration processing is completed. Apr 26 04:35:48 192.168.122.209 [45098.775459] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:35:48 192.168.122.209 [45099.186782] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:35:48 192.168.122.209 [45099.252125] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:35:48 192.168.122.209 [45099.278741] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:35:49 192.168.122.209 [45099.828715] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:35:49 192.168.122.209 [45099.830437] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:35:49 192.168.122.209 [45100.076632] [tempesta fw] Tempesta FW is ready Apr 26 04:35:49 192.168.122.209 [45100.210608] [tempesta fw] Warning: frang: restricted HTTP method for 127.0.0.2: 3 (0x8u) Apr 26 04:35:49 192.168.122.209 [45100.211375] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:35:50 192.168.122.209 [45101.355312] [tdb] Close table 'client0.tdb' Apr 26 04:35:51 192.168.122.209 [45101.665309] [tdb] Close table 'sessions0.tdb' Apr 26 04:35:54 192.168.122.209 [45104.897454] [tdb] Close table 'cache0.tdb' Apr 26 04:35:54 192.168.122.209 [45105.139931] [tdb] Close table 'filter0.tdb' Apr 26 04:35:54 192.168.122.209 [45105.140342] [tempesta fw] modules are stopped Apr 26 04:35:54 192.168.122.209 [45105.340343] [tempesta fw] exiting... Apr 26 04:35:55 192.168.122.209 [45105.487009] [tdb] Shutdown Tempesta DB Apr 26 04:35:55 192.168.122.209 [45105.667229] End test: t_frang.test_config.TestOverridingInheritance.test_overriding_global_to_location Apr 26 04:35:55 192.168.122.209 [45105.687696] Start test: t_frang.test_config.TestOverridingInheritance.test_overriding_global_to_location_via_vhost Apr 26 04:35:56 192.168.122.209 [45106.947041] [tdb] Start Tempesta DB Apr 26 04:35:56 192.168.122.209 [45107.084795] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:35:58 192.168.122.209 [45108.738030] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45108.738030] Maybe that's fine, but it's worth checking the [45108.738030] config - if there is no relations between the [45108.738030] names, then host name confusion attack is possible. Apr 26 04:35:58 192.168.122.209 [45108.921132] [tempesta fw] Configuration processing is completed. Apr 26 04:35:58 192.168.122.209 [45108.972302] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:35:59 192.168.122.209 [45109.395336] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:35:59 192.168.122.209 [45109.421336] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:35:59 192.168.122.209 [45109.447310] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:35:59 192.168.122.209 [45109.488812] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:35:59 192.168.122.209 [45109.490500] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:35:59 192.168.122.209 [45109.532775] [tempesta fw] Tempesta FW is ready Apr 26 04:35:59 192.168.122.209 [45109.695866] [tempesta fw] Warning: frang: restricted HTTP method for 127.0.0.2: 3 (0x8u) Apr 26 04:35:59 192.168.122.209 [45109.698131] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:35:59 192.168.122.209 [45110.221754] [tdb] Close table 'client0.tdb' Apr 26 04:36:00 192.168.122.209 [45110.409409] [tdb] Close table 'sessions0.tdb' Apr 26 04:36:03 192.168.122.209 [45113.535453] [tdb] Close table 'cache0.tdb' Apr 26 04:36:03 192.168.122.209 [45113.761264] [tdb] Close table 'filter0.tdb' Apr 26 04:36:03 192.168.122.209 [45113.761715] [tempesta fw] modules are stopped Apr 26 04:36:03 192.168.122.209 [45113.981245] [tempesta fw] exiting... Apr 26 04:36:03 192.168.122.209 [45114.130127] [tdb] Shutdown Tempesta DB Apr 26 04:36:03 192.168.122.209 [45114.348924] End test: t_frang.test_config.TestOverridingInheritance.test_overriding_global_to_location_via_vhost Apr 26 04:36:03 192.168.122.209 [45114.365803] Start test: t_frang.test_config.TestOverridingInheritance.test_overriding_global_to_vhost Apr 26 04:36:05 192.168.122.209 [45115.634632] [tdb] Start Tempesta DB Apr 26 04:36:05 192.168.122.209 [45115.768358] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:36:06 192.168.122.209 [45117.330172] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45117.330172] Maybe that's fine, but it's worth checking the [45117.330172] config - if there is no relations between the [45117.330172] names, then host name confusion attack is possible. Apr 26 04:36:07 192.168.122.209 [45117.492945] [tempesta fw] Configuration processing is completed. Apr 26 04:36:07 192.168.122.209 [45117.545930] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:36:07 192.168.122.209 [45117.954524] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:36:07 192.168.122.209 [45118.010973] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:36:07 192.168.122.209 [45118.036365] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:36:07 192.168.122.209 [45118.092850] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:36:07 192.168.122.209 [45118.094513] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:36:07 192.168.122.209 [45118.132856] [tempesta fw] Tempesta FW is ready Apr 26 04:36:07 192.168.122.209 [45118.272358] [tempesta fw] Warning: frang: restricted HTTP method for 127.0.0.2: 3 (0x8u) Apr 26 04:36:07 192.168.122.209 [45118.273120] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:36:08 192.168.122.209 [45118.770386] [tdb] Close table 'client0.tdb' Apr 26 04:36:08 192.168.122.209 [45118.978633] [tdb] Close table 'sessions0.tdb' Apr 26 04:36:11 192.168.122.209 [45122.092356] [tdb] Close table 'cache0.tdb' Apr 26 04:36:11 192.168.122.209 [45122.323317] [tdb] Close table 'filter0.tdb' Apr 26 04:36:11 192.168.122.209 [45122.323734] [tempesta fw] modules are stopped Apr 26 04:36:12 192.168.122.209 [45122.572832] [tempesta fw] exiting... Apr 26 04:36:12 192.168.122.209 [45122.720572] [tdb] Shutdown Tempesta DB Apr 26 04:36:12 192.168.122.209 [45122.940839] End test: t_frang.test_config.TestOverridingInheritance.test_overriding_global_to_vhost Apr 26 04:36:12 192.168.122.209 [45122.952173] Start test: t_frang.test_config.TestOverridingInheritance.test_overriding_vhost_to_location Apr 26 04:36:13 192.168.122.209 [45124.154474] [tdb] Start Tempesta DB Apr 26 04:36:13 192.168.122.209 [45124.302086] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:36:15 192.168.122.209 [45125.942737] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45125.942737] Maybe that's fine, but it's worth checking the [45125.942737] config - if there is no relations between the [45125.942737] names, then host name confusion attack is possible. Apr 26 04:36:15 192.168.122.209 [45126.117041] [tempesta fw] Configuration processing is completed. Apr 26 04:36:15 192.168.122.209 [45126.169501] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:36:16 192.168.122.209 [45126.597186] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:36:16 192.168.122.209 [45126.632841] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:36:16 192.168.122.209 [45126.658153] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:36:16 192.168.122.209 [45126.705012] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:36:16 192.168.122.209 [45126.706567] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:36:16 192.168.122.209 [45126.752973] [tempesta fw] Tempesta FW is ready Apr 26 04:36:16 192.168.122.209 [45126.889736] [tempesta fw] Warning: frang: restricted HTTP method for 127.0.0.2: 3 (0x8u) Apr 26 04:36:16 192.168.122.209 [45126.890519] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:36:17 192.168.122.209 [45127.403972] [tdb] Close table 'client0.tdb' Apr 26 04:36:17 192.168.122.209 [45127.594933] [tdb] Close table 'sessions0.tdb' Apr 26 04:36:20 192.168.122.209 [45130.680048] [tdb] Close table 'cache0.tdb' Apr 26 04:36:20 192.168.122.209 [45130.918677] [tdb] Close table 'filter0.tdb' Apr 26 04:36:20 192.168.122.209 [45130.919108] [tempesta fw] modules are stopped Apr 26 04:36:20 192.168.122.209 [45131.133839] [tempesta fw] exiting... Apr 26 04:36:20 192.168.122.209 [45131.285770] [tdb] Shutdown Tempesta DB Apr 26 04:36:21 192.168.122.209 [45131.498336] End test: t_frang.test_config.TestOverridingInheritance.test_overriding_vhost_to_location Apr 26 04:36:21 192.168.122.209 [45131.523795] Start test: t_frang.test_config.TestOverridingInheritance.test_two_connection_frang_limits_in_global_config Apr 26 04:36:22 192.168.122.209 [45132.742744] [tdb] Start Tempesta DB Apr 26 04:36:22 192.168.122.209 [45132.883604] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:36:24 192.168.122.209 [45134.410343] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45134.410343] Maybe that's fine, but it's worth checking the [45134.410343] config - if there is no relations between the [45134.410343] names, then host name confusion attack is possible. Apr 26 04:36:24 192.168.122.209 [45134.577407] [tempesta fw] Configuration processing is completed. Apr 26 04:36:24 192.168.122.209 [45134.626865] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:36:24 192.168.122.209 [45135.030129] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:36:24 192.168.122.209 [45135.085728] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:36:24 192.168.122.209 [45135.111281] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:36:24 192.168.122.209 [45135.161151] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:36:24 192.168.122.209 [45135.162842] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:36:24 192.168.122.209 [45135.205070] [tempesta fw] Tempesta FW is ready Apr 26 04:36:24 192.168.122.209 [45135.335837] [tempesta fw] Warning: frang: HTTP header length exceeded for 127.0.0.2: 190 (lim=100) Apr 26 04:36:25 192.168.122.209 [45135.803434] [tdb] Close table 'client0.tdb' Apr 26 04:36:25 192.168.122.209 [45136.034071] [tdb] Close table 'sessions0.tdb' Apr 26 04:36:28 192.168.122.209 [45139.164673] [tdb] Close table 'cache0.tdb' Apr 26 04:36:29 192.168.122.209 [45139.395330] [tdb] Close table 'filter0.tdb' Apr 26 04:36:29 192.168.122.209 [45139.395767] [tempesta fw] modules are stopped Apr 26 04:36:29 192.168.122.209 [45139.569504] [tempesta fw] exiting... Apr 26 04:36:29 192.168.122.209 [45139.721120] [tdb] Shutdown Tempesta DB Apr 26 04:36:29 192.168.122.209 [45139.948707] End test: t_frang.test_config.TestOverridingInheritance.test_two_connection_frang_limits_in_global_config Apr 26 04:36:29 192.168.122.209 [45139.961278] Start test: t_frang.test_config.TestOverridingInheritance.test_two_frang_limits_in_location Apr 26 04:36:30 192.168.122.209 [45141.085132] [tdb] Start Tempesta DB Apr 26 04:36:30 192.168.122.209 [45141.224942] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:36:32 192.168.122.209 [45142.874822] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45142.874822] Maybe that's fine, but it's worth checking the [45142.874822] config - if there is no relations between the [45142.874822] names, then host name confusion attack is possible. Apr 26 04:36:32 192.168.122.209 [45142.967648] [tempesta fw] ERROR: duplicate entry: 'frang_limits', only one such entry is allowed. Apr 26 04:36:32 192.168.122.209 [45142.970135] [tempesta fw] ERROR: configuration parsing error: [45142.970135] 16: frang_limits {http_methods post put;} [45142.970135] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 04:36:32 192.168.122.209 [45142.975897] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 04:36:32 192.168.122.209 [45143.180100] [tempesta fw] exiting... Apr 26 04:36:32 192.168.122.209 [45143.318237] [tdb] Shutdown Tempesta DB Apr 26 04:36:33 192.168.122.209 [45143.761660] End test: t_frang.test_config.TestOverridingInheritance.test_two_frang_limits_in_location Apr 26 04:36:33 192.168.122.209 [45143.772954] Start test: t_frang.test_config.TestOverridingInheritance.test_two_message_frang_limits_in_global_config Apr 26 04:36:34 192.168.122.209 [45144.892350] [tdb] Start Tempesta DB Apr 26 04:36:34 192.168.122.209 [45145.032919] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:36:35 192.168.122.209 [45145.494518] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45145.494518] Maybe that's fine, but it's worth checking the [45145.494518] config - if there is no relations between the [45145.494518] names, then host name confusion attack is possible. Apr 26 04:36:35 192.168.122.209 [45145.649348] [tempesta fw] Configuration processing is completed. Apr 26 04:36:35 192.168.122.209 [45145.701329] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:36:35 192.168.122.209 [45146.114668] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:36:35 192.168.122.209 [45146.171350] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:36:35 192.168.122.209 [45146.200513] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:36:35 192.168.122.209 [45146.265261] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:36:35 192.168.122.209 [45146.266957] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:36:35 192.168.122.209 [45146.305244] [tempesta fw] Tempesta FW is ready Apr 26 04:36:36 192.168.122.209 [45146.428152] [tempesta fw] Warning: frang: restricted HTTP method for 127.0.0.2: 3 (0x8u) Apr 26 04:36:36 192.168.122.209 [45146.429128] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:36:36 192.168.122.209 [45146.910207] [tdb] Close table 'client0.tdb' Apr 26 04:36:36 192.168.122.209 [45147.089294] [tdb] Close table 'sessions0.tdb' Apr 26 04:36:39 192.168.122.209 [45150.229059] [tdb] Close table 'cache0.tdb' Apr 26 04:36:40 192.168.122.209 [45150.463295] [tdb] Close table 'filter0.tdb' Apr 26 04:36:40 192.168.122.209 [45150.463702] [tempesta fw] modules are stopped Apr 26 04:36:40 192.168.122.209 [45150.667849] [tempesta fw] exiting... Apr 26 04:36:40 192.168.122.209 [45150.813394] [tdb] Shutdown Tempesta DB Apr 26 04:36:40 192.168.122.209 [45151.035069] End test: t_frang.test_config.TestOverridingInheritance.test_two_message_frang_limits_in_global_config Apr 26 04:36:40 192.168.122.209 [45151.046400] Start test: t_frang.test_config.TestOverridingInheritance.test_two_message_frang_limits_in_vhost Apr 26 04:36:41 192.168.122.209 [45152.202158] [tdb] Start Tempesta DB Apr 26 04:36:41 192.168.122.209 [45152.352396] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:36:43 192.168.122.209 [45153.878603] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45153.878603] Maybe that's fine, but it's worth checking the [45153.878603] config - if there is no relations between the [45153.878603] names, then host name confusion attack is possible. Apr 26 04:36:43 192.168.122.209 [45154.073418] [tempesta fw] Configuration processing is completed. Apr 26 04:36:43 192.168.122.209 [45154.125828] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:36:44 192.168.122.209 [45154.544593] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:36:44 192.168.122.209 [45154.570408] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:36:44 192.168.122.209 [45154.595900] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:36:44 192.168.122.209 [45154.641365] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:36:44 192.168.122.209 [45154.643035] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:36:44 192.168.122.209 [45154.693336] [tempesta fw] Tempesta FW is ready Apr 26 04:36:44 192.168.122.209 [45154.827796] [tempesta fw] Warning: frang: restricted HTTP method for 127.0.0.2: 3 (0x8u) Apr 26 04:36:44 192.168.122.209 [45154.829666] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:36:44 192.168.122.209 [45155.326586] [tdb] Close table 'client0.tdb' Apr 26 04:36:45 192.168.122.209 [45155.531481] [tdb] Close table 'sessions0.tdb' Apr 26 04:36:48 192.168.122.209 [45158.612447] [tdb] Close table 'cache0.tdb' Apr 26 04:36:48 192.168.122.209 [45158.835826] [tdb] Close table 'filter0.tdb' Apr 26 04:36:48 192.168.122.209 [45158.836283] [tempesta fw] modules are stopped Apr 26 04:36:48 192.168.122.209 [45159.065873] [tempesta fw] exiting... Apr 26 04:36:48 192.168.122.209 [45159.224837] [tdb] Shutdown Tempesta DB Apr 26 04:36:49 192.168.122.209 [45159.422503] End test: t_frang.test_config.TestOverridingInheritance.test_two_message_frang_limits_in_vhost Apr 26 04:36:49 192.168.122.209 [45159.435806] Start test: t_frang.test_connection_rate_burst.FrangTcpVsBoth.test_burst Apr 26 04:36:50 192.168.122.209 [45160.656819] [tdb] Start Tempesta DB Apr 26 04:36:50 192.168.122.209 [45160.817558] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:36:52 192.168.122.209 [45162.378721] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45162.378721] Maybe that's fine, but it's worth checking the [45162.378721] config - if there is no relations between the [45162.378721] names, then host name confusion attack is possible. Apr 26 04:36:52 192.168.122.209 [45162.481491] [tempesta fw] Configuration processing is completed. Apr 26 04:36:52 192.168.122.209 [45162.531124] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:36:52 192.168.122.209 [45162.566381] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:36:52 192.168.122.209 [45162.592929] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:36:52 192.168.122.209 [45162.641461] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:36:52 192.168.122.209 [45162.643132] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:36:52 192.168.122.209 [45162.685433] [tempesta fw] Tempesta FW is ready Apr 26 04:36:52 192.168.122.209 [45162.889474] [tempesta fw] Warning: frang: new connections burst exceeded for 127.0.0.1: 4 (lim=3) Apr 26 04:36:52 192.168.122.209 [45162.890379] [tempesta fw] Warning: frang: new connections burst exceeded for 127.0.0.1: 5 (lim=3) Apr 26 04:36:52 192.168.122.209 [45162.891276] [tempesta fw] Warning: frang: new connections burst exceeded for 127.0.0.1: 6 (lim=3) Apr 26 04:36:52 192.168.122.209 [45162.892599] [tempesta fw] Warning: frang: new connections burst exceeded for 127.0.0.1: 7 (lim=3) Apr 26 04:36:54 192.168.122.209 [45164.998259] [tempesta fw] Warning: frang: new connections burst exceeded for 127.0.0.1: 4 (lim=3) Apr 26 04:36:54 192.168.122.209 [45164.999224] [tempesta fw] Warning: frang: new connections burst exceeded for 127.0.0.1: 5 (lim=3) Apr 26 04:36:54 192.168.122.209 [45165.000040] [tempesta fw] Warning: frang: new connections burst exceeded for 127.0.0.1: 6 (lim=3) Apr 26 04:36:54 192.168.122.209 [45165.002973] [tempesta fw] Warning: frang: new connections burst exceeded for 127.0.0.1: 7 (lim=3) Apr 26 04:36:57 192.168.122.209 [45167.556943] [tdb] Close table 'client0.tdb' Apr 26 04:36:57 192.168.122.209 [45167.775569] [tdb] Close table 'sessions0.tdb' Apr 26 04:36:57 192.168.122.209 [45168.028818] [tdb] Close table 'filter0.tdb' Apr 26 04:36:57 192.168.122.209 [45168.029269] [tempesta fw] modules are stopped Apr 26 04:36:57 192.168.122.209 [45168.224695] [tempesta fw] exiting... Apr 26 04:36:57 192.168.122.209 [45168.362773] [tdb] Shutdown Tempesta DB Apr 26 04:36:58 192.168.122.209 [45168.582762] End test: t_frang.test_connection_rate_burst.FrangTcpVsBoth.test_burst Apr 26 04:36:58 192.168.122.209 [45168.591792] Start test: t_frang.test_connection_rate_burst.FrangTcpVsBoth.test_rate Apr 26 04:36:59 192.168.122.209 [45169.732902] [tdb] Start Tempesta DB Apr 26 04:36:59 192.168.122.209 [45169.874606] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:37:00 192.168.122.209 [45170.634815] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45170.634815] Maybe that's fine, but it's worth checking the [45170.634815] config - if there is no relations between the [45170.634815] names, then host name confusion attack is possible. Apr 26 04:37:00 192.168.122.209 [45170.745578] [tempesta fw] Configuration processing is completed. Apr 26 04:37:00 192.168.122.209 [45170.797099] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:37:00 192.168.122.209 [45170.825274] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:37:00 192.168.122.209 [45170.860282] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:37:00 192.168.122.209 [45170.909582] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:37:00 192.168.122.209 [45170.911250] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:37:00 192.168.122.209 [45170.949512] [tempesta fw] Tempesta FW is ready Apr 26 04:37:00 192.168.122.209 [45171.130999] [tempesta fw] Warning: frang: new connections rate exceeded for 127.0.0.1: 4 (lim=3) Apr 26 04:37:00 192.168.122.209 [45171.131828] [tempesta fw] Warning: frang: new connections rate exceeded for 127.0.0.1: 5 (lim=3) Apr 26 04:37:00 192.168.122.209 [45171.133929] [tempesta fw] Warning: frang: new connections rate exceeded for 127.0.0.1: 6 (lim=3) Apr 26 04:37:00 192.168.122.209 [45171.135115] [tempesta fw] Warning: frang: new connections rate exceeded for 127.0.0.1: 7 (lim=3) Apr 26 04:37:02 192.168.122.209 [45173.229807] [tempesta fw] Warning: frang: new connections rate exceeded for 127.0.0.1: 4 (lim=3) Apr 26 04:37:02 192.168.122.209 [45173.230929] [tempesta fw] Warning: frang: new connections rate exceeded for 127.0.0.1: 5 (lim=3) Apr 26 04:37:02 192.168.122.209 [45173.231842] [tempesta fw] Warning: frang: new connections rate exceeded for 127.0.0.1: 6 (lim=3) Apr 26 04:37:02 192.168.122.209 [45173.232785] [tempesta fw] Warning: frang: new connections rate exceeded for 127.0.0.1: 7 (lim=3) Apr 26 04:37:05 192.168.122.209 [45175.840996] [tdb] Close table 'client0.tdb' Apr 26 04:37:05 192.168.122.209 [45176.032143] [tdb] Close table 'sessions0.tdb' Apr 26 04:37:05 192.168.122.209 [45176.275385] [tdb] Close table 'filter0.tdb' Apr 26 04:37:05 192.168.122.209 [45176.275823] [tempesta fw] modules are stopped Apr 26 04:37:06 192.168.122.209 [45176.464833] [tempesta fw] exiting... Apr 26 04:37:06 192.168.122.209 [45176.620148] [tdb] Shutdown Tempesta DB Apr 26 04:37:06 192.168.122.209 [45176.831630] End test: t_frang.test_connection_rate_burst.FrangTcpVsBoth.test_rate Apr 26 04:37:06 192.168.122.209 [45176.841025] Start test: t_frang.test_connection_rate_burst.FrangTlsVsBoth.test_burst Apr 26 04:37:07 192.168.122.209 [45178.021959] [tdb] Start Tempesta DB Apr 26 04:37:07 192.168.122.209 [45178.167831] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:37:08 192.168.122.209 [45178.906916] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45178.906916] Maybe that's fine, but it's worth checking the [45178.906916] config - if there is no relations between the [45178.906916] names, then host name confusion attack is possible. Apr 26 04:37:08 192.168.122.209 [45179.009698] [tempesta fw] Configuration processing is completed. Apr 26 04:37:08 192.168.122.209 [45179.060919] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:37:08 192.168.122.209 [45179.088659] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:37:08 192.168.122.209 [45179.115295] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:37:08 192.168.122.209 [45179.165653] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:37:08 192.168.122.209 [45179.167325] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:37:08 192.168.122.209 [45179.205649] [tempesta fw] Tempesta FW is ready Apr 26 04:37:09 192.168.122.209 [45179.383356] [tempesta fw] Warning: frang: new TLS connections burst exceeded for 127.0.0.1: 4 (lim=3) Apr 26 04:37:09 192.168.122.209 [45179.385628] [tempesta fw] Warning: frang: new TLS connections burst exceeded for 127.0.0.1: 5 (lim=3) Apr 26 04:37:09 192.168.122.209 [45179.386469] [tempesta fw] Warning: frang: new TLS connections burst exceeded for 127.0.0.1: 6 (lim=3) Apr 26 04:37:09 192.168.122.209 [45179.387555] [tempesta fw] Warning: frang: new TLS connections burst exceeded for 127.0.0.1: 7 (lim=3) Apr 26 04:37:13 192.168.122.209 [45184.072042] [tdb] Close table 'client0.tdb' Apr 26 04:37:13 192.168.122.209 [45184.262975] [tdb] Close table 'sessions0.tdb' Apr 26 04:37:14 192.168.122.209 [45184.475058] [tdb] Close table 'filter0.tdb' Apr 26 04:37:14 192.168.122.209 [45184.475493] [tempesta fw] modules are stopped Apr 26 04:37:14 192.168.122.209 [45184.703203] [tempesta fw] exiting... Apr 26 04:37:14 192.168.122.209 [45184.850503] [tdb] Shutdown Tempesta DB Apr 26 04:37:14 192.168.122.209 [45185.044062] End test: t_frang.test_connection_rate_burst.FrangTlsVsBoth.test_burst Apr 26 04:37:14 192.168.122.209 [45185.058881] Start test: t_frang.test_connection_rate_burst.FrangTlsVsBoth.test_rate Apr 26 04:37:15 192.168.122.209 [45186.152499] [tdb] Start Tempesta DB Apr 26 04:37:15 192.168.122.209 [45186.310395] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:37:16 192.168.122.209 [45187.075037] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45187.075037] Maybe that's fine, but it's worth checking the [45187.075037] config - if there is no relations between the [45187.075037] names, then host name confusion attack is possible. Apr 26 04:37:16 192.168.122.209 [45187.193794] [tempesta fw] Configuration processing is completed. Apr 26 04:37:16 192.168.122.209 [45187.244426] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:37:16 192.168.122.209 [45187.272265] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:37:16 192.168.122.209 [45187.300637] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:37:16 192.168.122.209 [45187.337769] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:37:16 192.168.122.209 [45187.339500] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:37:17 192.168.122.209 [45187.389713] [tempesta fw] Tempesta FW is ready Apr 26 04:37:17 192.168.122.209 [45187.571385] [tempesta fw] Warning: frang: new TLS connections rate exceeded for 127.0.0.1: 4 (lim=3) Apr 26 04:37:17 192.168.122.209 [45187.572784] [tempesta fw] Warning: frang: new TLS connections rate exceeded for 127.0.0.1: 5 (lim=3) Apr 26 04:37:17 192.168.122.209 [45187.573633] [tempesta fw] Warning: frang: new TLS connections rate exceeded for 127.0.0.1: 6 (lim=3) Apr 26 04:37:17 192.168.122.209 [45187.576362] [tempesta fw] Warning: frang: new TLS connections rate exceeded for 127.0.0.1: 7 (lim=3) Apr 26 04:37:21 192.168.122.209 [45192.259960] [tdb] Close table 'client0.tdb' Apr 26 04:37:22 192.168.122.209 [45192.448430] [tdb] Close table 'sessions0.tdb' Apr 26 04:37:22 192.168.122.209 [45192.655302] [tdb] Close table 'filter0.tdb' Apr 26 04:37:22 192.168.122.209 [45192.655721] [tempesta fw] modules are stopped Apr 26 04:37:22 192.168.122.209 [45192.876492] [tempesta fw] exiting... Apr 26 04:37:22 192.168.122.209 [45193.013675] [tdb] Shutdown Tempesta DB Apr 26 04:37:22 192.168.122.209 [45193.253814] End test: t_frang.test_connection_rate_burst.FrangTlsVsBoth.test_rate Apr 26 04:37:22 192.168.122.209 [45193.263110] Start test: t_frang.test_connection_rate_burst.TestFrangTCP.test_connection_burst Apr 26 04:37:24 192.168.122.209 [45194.460444] [tdb] Start Tempesta DB Apr 26 04:37:24 192.168.122.209 [45194.614383] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:37:25 192.168.122.209 [45195.599164] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45195.599164] Maybe that's fine, but it's worth checking the [45195.599164] config - if there is no relations between the [45195.599164] names, then host name confusion attack is possible. Apr 26 04:37:25 192.168.122.209 [45195.729900] [tempesta fw] Configuration processing is completed. Apr 26 04:37:25 192.168.122.209 [45195.780010] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:37:25 192.168.122.209 [45195.807545] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:37:25 192.168.122.209 [45195.833970] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:37:25 192.168.122.209 [45195.881889] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:37:25 192.168.122.209 [45195.883562] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:37:25 192.168.122.209 [45195.921845] [tempesta fw] Tempesta FW is ready Apr 26 04:37:25 192.168.122.209 [45196.092360] [tempesta fw] Warning: frang: new connections burst exceeded for 127.0.0.1: 6 (lim=5) Apr 26 04:37:25 192.168.122.209 [45196.093480] [tempesta fw] Warning: frang: new connections burst exceeded for 127.0.0.1: 7 (lim=5) Apr 26 04:37:25 192.168.122.209 [45196.094624] [tempesta fw] Warning: frang: new connections burst exceeded for 127.0.0.1: 8 (lim=5) Apr 26 04:37:25 192.168.122.209 [45196.095778] [tempesta fw] Warning: frang: new connections burst exceeded for 127.0.0.1: 9 (lim=5) Apr 26 04:37:25 192.168.122.209 [45196.097028] [tempesta fw] Warning: frang: new connections burst exceeded for 127.0.0.1: 10 (lim=5) Apr 26 04:37:25 192.168.122.209 [45196.098288] [tempesta fw] Warning: frang: new connections burst exceeded for 127.0.0.1: 11 (lim=5) Apr 26 04:37:25 192.168.122.209 [45196.099709] [tempesta fw] Warning: frang: new connections burst exceeded for 127.0.0.1: 12 (lim=5) Apr 26 04:37:25 192.168.122.209 [45196.100738] [tempesta fw] Warning: frang: new connections burst exceeded for 127.0.0.1: 13 (lim=5) Apr 26 04:37:25 192.168.122.209 [45196.102226] [tempesta fw] Warning: frang: new connections burst exceeded for 127.0.0.1: 14 (lim=5) Apr 26 04:37:25 192.168.122.209 [45196.103028] [tempesta fw] Warning: frang: new connections burst exceeded for 127.0.0.1: 15 (lim=5) Apr 26 04:37:25 192.168.122.209 [45196.104554] [tempesta fw] Warning: frang: new connections burst exceeded for 127.0.0.1: 16 (lim=5) Apr 26 04:37:25 192.168.122.209 [45196.105367] [tempesta fw] Warning: frang: new connections burst exceeded for 127.0.0.1: 17 (lim=5) Apr 26 04:37:25 192.168.122.209 [45196.106939] [tempesta fw] Warning: frang: new connections burst exceeded for 127.0.0.1: 18 (lim=5) Apr 26 04:37:25 192.168.122.209 [45196.108380] [tempesta fw] Warning: frang: new connections burst exceeded for 127.0.0.1: 19 (lim=5) Apr 26 04:37:25 192.168.122.209 [45196.109279] [tempesta fw] Warning: frang: new connections burst exceeded for 127.0.0.1: 20 (lim=5) Apr 26 04:37:28 192.168.122.209 [45198.646656] [tdb] Close table 'client0.tdb' Apr 26 04:37:28 192.168.122.209 [45198.856113] [tdb] Close table 'sessions0.tdb' Apr 26 04:37:28 192.168.122.209 [45199.083139] [tdb] Close table 'filter0.tdb' Apr 26 04:37:28 192.168.122.209 [45199.083573] [tempesta fw] modules are stopped Apr 26 04:37:28 192.168.122.209 [45199.325548] [tempesta fw] exiting... Apr 26 04:37:29 192.168.122.209 [45199.455291] [tdb] Shutdown Tempesta DB Apr 26 04:37:29 192.168.122.209 [45199.666174] End test: t_frang.test_connection_rate_burst.TestFrangTCP.test_connection_burst Apr 26 04:37:29 192.168.122.209 [45199.677483] Start test: t_frang.test_connection_rate_burst.TestFrangTCP.test_connection_burst_on_the_limit Apr 26 04:37:30 192.168.122.209 [45200.830512] [tdb] Start Tempesta DB Apr 26 04:37:30 192.168.122.209 [45200.988211] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:37:31 192.168.122.209 [45202.043252] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45202.043252] Maybe that's fine, but it's worth checking the [45202.043252] config - if there is no relations between the [45202.043252] names, then host name confusion attack is possible. Apr 26 04:37:31 192.168.122.209 [45202.185979] [tempesta fw] Configuration processing is completed. Apr 26 04:37:31 192.168.122.209 [45202.240260] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:37:31 192.168.122.209 [45202.268165] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:37:31 192.168.122.209 [45202.296267] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:37:31 192.168.122.209 [45202.349975] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:37:31 192.168.122.209 [45202.351737] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:37:32 192.168.122.209 [45202.389908] [tempesta fw] Tempesta FW is ready Apr 26 04:37:34 192.168.122.209 [45205.172367] [tdb] Close table 'client0.tdb' Apr 26 04:37:34 192.168.122.209 [45205.359647] [tdb] Close table 'sessions0.tdb' Apr 26 04:37:35 192.168.122.209 [45205.580027] [tdb] Close table 'filter0.tdb' Apr 26 04:37:35 192.168.122.209 [45205.580477] [tempesta fw] modules are stopped Apr 26 04:37:35 192.168.122.209 [45205.858054] [tempesta fw] exiting... Apr 26 04:37:35 192.168.122.209 [45205.991064] [tdb] Shutdown Tempesta DB Apr 26 04:37:35 192.168.122.209 [45206.197262] End test: t_frang.test_connection_rate_burst.TestFrangTCP.test_connection_burst_on_the_limit Apr 26 04:37:35 192.168.122.209 [45206.216026] Start test: t_frang.test_connection_rate_burst.TestFrangTCP.test_connection_burst_without_reaching_the_limit Apr 26 04:37:36 192.168.122.209 [45207.369775] [tdb] Start Tempesta DB Apr 26 04:37:37 192.168.122.209 [45207.501881] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:37:38 192.168.122.209 [45208.499262] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45208.499262] Maybe that's fine, but it's worth checking the [45208.499262] config - if there is no relations between the [45208.499262] names, then host name confusion attack is possible. Apr 26 04:37:38 192.168.122.209 [45208.622359] [tempesta fw] Configuration processing is completed. Apr 26 04:37:38 192.168.122.209 [45208.673084] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:37:38 192.168.122.209 [45208.700734] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:37:38 192.168.122.209 [45208.727253] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:37:38 192.168.122.209 [45208.766001] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:37:38 192.168.122.209 [45208.767013] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:37:38 192.168.122.209 [45208.806003] [tempesta fw] Tempesta FW is ready Apr 26 04:37:41 192.168.122.209 [45211.574461] [tdb] Close table 'client0.tdb' Apr 26 04:37:41 192.168.122.209 [45211.784900] [tdb] Close table 'sessions0.tdb' Apr 26 04:37:41 192.168.122.209 [45212.023046] [tdb] Close table 'filter0.tdb' Apr 26 04:37:41 192.168.122.209 [45212.023492] [tempesta fw] modules are stopped Apr 26 04:37:41 192.168.122.209 [45212.249755] [tempesta fw] exiting... Apr 26 04:37:42 192.168.122.209 [45212.406054] [tdb] Shutdown Tempesta DB Apr 26 04:37:42 192.168.122.209 [45212.643611] End test: t_frang.test_connection_rate_burst.TestFrangTCP.test_connection_burst_without_reaching_the_limit Apr 26 04:37:42 192.168.122.209 [45212.660839] Start test: t_frang.test_connection_rate_burst.TestFrangTCP.test_connection_rate Apr 26 04:37:43 192.168.122.209 [45213.786764] [tdb] Start Tempesta DB Apr 26 04:37:43 192.168.122.209 [45213.923927] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:37:44 192.168.122.209 [45214.931382] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45214.931382] Maybe that's fine, but it's worth checking the [45214.931382] config - if there is no relations between the [45214.931382] names, then host name confusion attack is possible. Apr 26 04:37:44 192.168.122.209 [45215.058538] [tempesta fw] Configuration processing is completed. Apr 26 04:37:44 192.168.122.209 [45215.108142] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:37:44 192.168.122.209 [45215.136168] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:37:44 192.168.122.209 [45215.165961] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:37:44 192.168.122.209 [45215.206130] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:37:44 192.168.122.209 [45215.207797] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:37:44 192.168.122.209 [45215.250074] [tempesta fw] Tempesta FW is ready Apr 26 04:37:45 192.168.122.209 [45215.432444] [tempesta fw] Warning: frang: new connections rate exceeded for 127.0.0.1: 6 (lim=5) Apr 26 04:37:45 192.168.122.209 [45215.434202] [tempesta fw] Warning: frang: new connections rate exceeded for 127.0.0.1: 7 (lim=5) Apr 26 04:37:45 192.168.122.209 [45215.435389] [tempesta fw] Warning: frang: new connections rate exceeded for 127.0.0.1: 8 (lim=5) Apr 26 04:37:45 192.168.122.209 [45215.436655] [tempesta fw] Warning: frang: new connections rate exceeded for 127.0.0.1: 9 (lim=5) Apr 26 04:37:45 192.168.122.209 [45215.437822] [tempesta fw] Warning: frang: new connections rate exceeded for 127.0.0.1: 10 (lim=5) Apr 26 04:37:45 192.168.122.209 [45215.439556] [tempesta fw] Warning: frang: new connections rate exceeded for 127.0.0.1: 11 (lim=5) Apr 26 04:37:45 192.168.122.209 [45215.440460] [tempesta fw] Warning: frang: new connections rate exceeded for 127.0.0.1: 12 (lim=5) Apr 26 04:37:45 192.168.122.209 [45215.441722] [tempesta fw] Warning: frang: new connections rate exceeded for 127.0.0.1: 13 (lim=5) Apr 26 04:37:45 192.168.122.209 [45215.442587] [tempesta fw] Warning: frang: new connections rate exceeded for 127.0.0.1: 14 (lim=5) Apr 26 04:37:45 192.168.122.209 [45215.443403] [tempesta fw] Warning: frang: new connections rate exceeded for 127.0.0.1: 15 (lim=5) Apr 26 04:37:45 192.168.122.209 [45215.444278] [tempesta fw] Warning: frang: new connections rate exceeded for 127.0.0.1: 16 (lim=5) Apr 26 04:37:45 192.168.122.209 [45215.445096] [tempesta fw] Warning: frang: new connections rate exceeded for 127.0.0.1: 17 (lim=5) Apr 26 04:37:45 192.168.122.209 [45215.446226] [tempesta fw] Warning: frang: new connections rate exceeded for 127.0.0.1: 18 (lim=5) Apr 26 04:37:45 192.168.122.209 [45215.450090] [tempesta fw] Warning: frang: new connections rate exceeded for 127.0.0.1: 19 (lim=5) Apr 26 04:37:45 192.168.122.209 [45215.451018] [tempesta fw] Warning: frang: new connections rate exceeded for 127.0.0.1: 20 (lim=5) Apr 26 04:37:47 192.168.122.209 [45218.039985] [tdb] Close table 'client0.tdb' Apr 26 04:37:47 192.168.122.209 [45218.229846] [tdb] Close table 'sessions0.tdb' Apr 26 04:37:48 192.168.122.209 [45218.482612] [tdb] Close table 'filter0.tdb' Apr 26 04:37:48 192.168.122.209 [45218.483043] [tempesta fw] modules are stopped Apr 26 04:37:48 192.168.122.209 [45218.714245] [tempesta fw] exiting... Apr 26 04:37:48 192.168.122.209 [45218.864634] [tdb] Shutdown Tempesta DB Apr 26 04:37:48 192.168.122.209 [45219.074687] End test: t_frang.test_connection_rate_burst.TestFrangTCP.test_connection_rate Apr 26 04:37:48 192.168.122.209 [45219.083466] Start test: t_frang.test_connection_rate_burst.TestFrangTCP.test_connection_rate_on_the_limit Apr 26 04:37:49 192.168.122.209 [45220.256217] [tdb] Start Tempesta DB Apr 26 04:37:50 192.168.122.209 [45220.390720] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:37:50 192.168.122.209 [45221.359452] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45221.359452] Maybe that's fine, but it's worth checking the [45221.359452] config - if there is no relations between the [45221.359452] names, then host name confusion attack is possible. Apr 26 04:37:51 192.168.122.209 [45221.522221] [tempesta fw] Configuration processing is completed. Apr 26 04:37:51 192.168.122.209 [45221.572722] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:37:51 192.168.122.209 [45221.600335] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:37:51 192.168.122.209 [45221.626744] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:37:51 192.168.122.209 [45221.675115] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:37:51 192.168.122.209 [45221.676864] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:37:51 192.168.122.209 [45221.726170] [tempesta fw] Tempesta FW is ready Apr 26 04:37:54 192.168.122.209 [45224.485689] [tdb] Close table 'client0.tdb' Apr 26 04:37:54 192.168.122.209 [45224.677932] [tdb] Close table 'sessions0.tdb' Apr 26 04:37:54 192.168.122.209 [45224.904809] [tdb] Close table 'filter0.tdb' Apr 26 04:37:54 192.168.122.209 [45224.905246] [tempesta fw] modules are stopped Apr 26 04:37:54 192.168.122.209 [45225.129564] [tempesta fw] exiting... Apr 26 04:37:54 192.168.122.209 [45225.270406] [tdb] Shutdown Tempesta DB Apr 26 04:37:55 192.168.122.209 [45225.476619] End test: t_frang.test_connection_rate_burst.TestFrangTCP.test_connection_rate_on_the_limit Apr 26 04:37:55 192.168.122.209 [45225.489885] Start test: t_frang.test_connection_rate_burst.TestFrangTCP.test_connection_rate_without_reaching_the_limit Apr 26 04:37:56 192.168.122.209 [45226.709918] [tdb] Start Tempesta DB Apr 26 04:37:56 192.168.122.209 [45226.866116] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:37:57 192.168.122.209 [45227.895527] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45227.895527] Maybe that's fine, but it's worth checking the [45227.895527] config - if there is no relations between the [45227.895527] names, then host name confusion attack is possible. Apr 26 04:37:57 192.168.122.209 [45228.030201] [tempesta fw] Configuration processing is completed. Apr 26 04:37:57 192.168.122.209 [45228.080340] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:37:57 192.168.122.209 [45228.107646] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:37:57 192.168.122.209 [45228.133845] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:37:57 192.168.122.209 [45228.218296] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:37:57 192.168.122.209 [45228.220081] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:37:57 192.168.122.209 [45228.270244] [tempesta fw] Tempesta FW is ready Apr 26 04:38:00 192.168.122.209 [45231.061768] [tdb] Close table 'client0.tdb' Apr 26 04:38:00 192.168.122.209 [45231.253586] [tdb] Close table 'sessions0.tdb' Apr 26 04:38:01 192.168.122.209 [45231.496487] [tdb] Close table 'filter0.tdb' Apr 26 04:38:01 192.168.122.209 [45231.496923] [tempesta fw] modules are stopped Apr 26 04:38:01 192.168.122.209 [45231.743369] [tempesta fw] exiting... Apr 26 04:38:01 192.168.122.209 [45231.878063] [tdb] Shutdown Tempesta DB Apr 26 04:38:01 192.168.122.209 [45232.065168] End test: t_frang.test_connection_rate_burst.TestFrangTCP.test_connection_rate_without_reaching_the_limit Apr 26 04:38:01 192.168.122.209 [45232.083358] Start test: t_frang.test_connection_rate_burst.TestFrangTLS.test_connection_burst Apr 26 04:38:02 192.168.122.209 [45233.251662] [tdb] Start Tempesta DB Apr 26 04:38:03 192.168.122.209 [45233.391780] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:38:04 192.168.122.209 [45234.431777] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45234.431777] Maybe that's fine, but it's worth checking the [45234.431777] config - if there is no relations between the [45234.431777] names, then host name confusion attack is possible. Apr 26 04:38:04 192.168.122.209 [45234.562400] [tempesta fw] Configuration processing is completed. Apr 26 04:38:04 192.168.122.209 [45234.612871] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:38:04 192.168.122.209 [45234.642592] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:38:04 192.168.122.209 [45234.669432] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:38:04 192.168.122.209 [45234.718383] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:38:04 192.168.122.209 [45234.720123] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:38:04 192.168.122.209 [45234.758328] [tempesta fw] Tempesta FW is ready Apr 26 04:38:04 192.168.122.209 [45234.946265] [tempesta fw] Warning: frang: new TLS connections burst exceeded for 127.0.0.1: 6 (lim=5) Apr 26 04:38:04 192.168.122.209 [45234.947500] [tempesta fw] Warning: frang: new TLS connections burst exceeded for 127.0.0.1: 7 (lim=5) Apr 26 04:38:04 192.168.122.209 [45234.948343] [tempesta fw] Warning: frang: new TLS connections burst exceeded for 127.0.0.1: 8 (lim=5) Apr 26 04:38:04 192.168.122.209 [45234.949181] [tempesta fw] Warning: frang: new TLS connections burst exceeded for 127.0.0.1: 9 (lim=5) Apr 26 04:38:04 192.168.122.209 [45234.950015] [tempesta fw] Warning: frang: new TLS connections burst exceeded for 127.0.0.1: 10 (lim=5) Apr 26 04:38:04 192.168.122.209 [45234.950855] [tempesta fw] Warning: frang: new TLS connections burst exceeded for 127.0.0.1: 11 (lim=5) Apr 26 04:38:04 192.168.122.209 [45234.952313] [tempesta fw] Warning: frang: new TLS connections burst exceeded for 127.0.0.1: 12 (lim=5) Apr 26 04:38:04 192.168.122.209 [45234.953180] [tempesta fw] Warning: frang: new TLS connections burst exceeded for 127.0.0.1: 13 (lim=5) Apr 26 04:38:04 192.168.122.209 [45234.954022] [tempesta fw] Warning: frang: new TLS connections burst exceeded for 127.0.0.1: 14 (lim=5) Apr 26 04:38:04 192.168.122.209 [45234.957660] [tempesta fw] Warning: frang: new TLS connections burst exceeded for 127.0.0.1: 6 (lim=5) Apr 26 04:38:07 192.168.122.209 [45237.557909] [tdb] Close table 'client0.tdb' Apr 26 04:38:07 192.168.122.209 [45237.782079] [tdb] Close table 'sessions0.tdb' Apr 26 04:38:07 192.168.122.209 [45238.015347] [tdb] Close table 'filter0.tdb' Apr 26 04:38:07 192.168.122.209 [45238.016355] [tempesta fw] modules are stopped Apr 26 04:38:07 192.168.122.209 [45238.219408] [tempesta fw] exiting... Apr 26 04:38:07 192.168.122.209 [45238.350191] [tdb] Shutdown Tempesta DB Apr 26 04:38:08 192.168.122.209 [45238.571979] End test: t_frang.test_connection_rate_burst.TestFrangTLS.test_connection_burst Apr 26 04:38:08 192.168.122.209 [45238.591043] Start test: t_frang.test_connection_rate_burst.TestFrangTLS.test_connection_burst_on_the_limit Apr 26 04:38:09 192.168.122.209 [45239.800088] [tdb] Start Tempesta DB Apr 26 04:38:09 192.168.122.209 [45239.950205] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:38:10 192.168.122.209 [45240.935628] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45240.935628] Maybe that's fine, but it's worth checking the [45240.935628] config - if there is no relations between the [45240.935628] names, then host name confusion attack is possible. Apr 26 04:38:10 192.168.122.209 [45241.082482] [tempesta fw] Configuration processing is completed. Apr 26 04:38:10 192.168.122.209 [45241.132247] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:38:10 192.168.122.209 [45241.160678] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:38:10 192.168.122.209 [45241.187593] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:38:10 192.168.122.209 [45241.222451] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:38:10 192.168.122.209 [45241.223611] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:38:10 192.168.122.209 [45241.270421] [tempesta fw] Tempesta FW is ready Apr 26 04:38:13 192.168.122.209 [45244.061957] [tdb] Close table 'client0.tdb' Apr 26 04:38:13 192.168.122.209 [45244.255248] [tdb] Close table 'sessions0.tdb' Apr 26 04:38:14 192.168.122.209 [45244.466210] [tdb] Close table 'filter0.tdb' Apr 26 04:38:14 192.168.122.209 [45244.466654] [tempesta fw] modules are stopped Apr 26 04:38:14 192.168.122.209 [45244.694745] [tempesta fw] exiting... Apr 26 04:38:14 192.168.122.209 [45244.814888] [tdb] Shutdown Tempesta DB Apr 26 04:38:14 192.168.122.209 [45245.036952] End test: t_frang.test_connection_rate_burst.TestFrangTLS.test_connection_burst_on_the_limit Apr 26 04:38:14 192.168.122.209 [45245.050046] Start test: t_frang.test_connection_rate_burst.TestFrangTLS.test_connection_burst_without_reaching_the_limit Apr 26 04:38:15 192.168.122.209 [45246.227457] [tdb] Start Tempesta DB Apr 26 04:38:16 192.168.122.209 [45246.379987] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:38:17 192.168.122.209 [45247.375765] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45247.375765] Maybe that's fine, but it's worth checking the [45247.375765] config - if there is no relations between the [45247.375765] names, then host name confusion attack is possible. Apr 26 04:38:17 192.168.122.209 [45247.510593] [tempesta fw] Configuration processing is completed. Apr 26 04:38:17 192.168.122.209 [45247.563178] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:38:17 192.168.122.209 [45247.593441] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:38:17 192.168.122.209 [45247.619667] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:38:17 192.168.122.209 [45247.682527] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:38:17 192.168.122.209 [45247.684233] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:38:17 192.168.122.209 [45247.726478] [tempesta fw] Tempesta FW is ready Apr 26 04:38:20 192.168.122.209 [45250.533034] [tdb] Close table 'client0.tdb' Apr 26 04:38:20 192.168.122.209 [45250.719208] [tdb] Close table 'sessions0.tdb' Apr 26 04:38:20 192.168.122.209 [45250.970618] [tdb] Close table 'filter0.tdb' Apr 26 04:38:20 192.168.122.209 [45250.971092] [tempesta fw] modules are stopped Apr 26 04:38:20 192.168.122.209 [45251.210506] [tempesta fw] exiting... Apr 26 04:38:20 192.168.122.209 [45251.354431] [tdb] Shutdown Tempesta DB Apr 26 04:38:21 192.168.122.209 [45251.581567] End test: t_frang.test_connection_rate_burst.TestFrangTLS.test_connection_burst_without_reaching_the_limit Apr 26 04:38:21 192.168.122.209 [45251.593562] Start test: t_frang.test_connection_rate_burst.TestFrangTLS.test_connection_rate Apr 26 04:38:22 192.168.122.209 [45252.792930] [tdb] Start Tempesta DB Apr 26 04:38:22 192.168.122.209 [45252.949984] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:38:23 192.168.122.209 [45253.971852] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45253.971852] Maybe that's fine, but it's worth checking the [45253.971852] config - if there is no relations between the [45253.971852] names, then host name confusion attack is possible. Apr 26 04:38:23 192.168.122.209 [45254.102635] [tempesta fw] Configuration processing is completed. Apr 26 04:38:23 192.168.122.209 [45254.168789] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:38:23 192.168.122.209 [45254.196799] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:38:23 192.168.122.209 [45254.223616] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:38:23 192.168.122.209 [45254.270618] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:38:23 192.168.122.209 [45254.272338] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:38:23 192.168.122.209 [45254.322578] [tempesta fw] Tempesta FW is ready Apr 26 04:38:24 192.168.122.209 [45254.519135] [tempesta fw] Warning: frang: new TLS connections rate exceeded for 127.0.0.1: 6 (lim=5) Apr 26 04:38:24 192.168.122.209 [45254.520260] [tempesta fw] Warning: frang: new TLS connections rate exceeded for 127.0.0.1: 7 (lim=5) Apr 26 04:38:24 192.168.122.209 [45254.521460] [tempesta fw] Warning: frang: new TLS connections rate exceeded for 127.0.0.1: 8 (lim=5) Apr 26 04:38:24 192.168.122.209 [45254.522300] [tempesta fw] Warning: frang: new TLS connections rate exceeded for 127.0.0.1: 9 (lim=5) Apr 26 04:38:24 192.168.122.209 [45254.523142] [tempesta fw] Warning: frang: new TLS connections rate exceeded for 127.0.0.1: 10 (lim=5) Apr 26 04:38:24 192.168.122.209 [45254.523986] [tempesta fw] Warning: frang: new TLS connections rate exceeded for 127.0.0.1: 11 (lim=5) Apr 26 04:38:24 192.168.122.209 [45254.524877] [tempesta fw] Warning: frang: new TLS connections rate exceeded for 127.0.0.1: 12 (lim=5) Apr 26 04:38:24 192.168.122.209 [45254.526394] [tempesta fw] Warning: frang: new TLS connections rate exceeded for 127.0.0.1: 13 (lim=5) Apr 26 04:38:24 192.168.122.209 [45254.527228] [tempesta fw] Warning: frang: new TLS connections rate exceeded for 127.0.0.1: 14 (lim=5) Apr 26 04:38:24 192.168.122.209 [45254.528101] [tempesta fw] Warning: frang: new TLS connections rate exceeded for 127.0.0.1: 15 (lim=5) Apr 26 04:38:24 192.168.122.209 [45254.528936] [tempesta fw] Warning: frang: new TLS connections rate exceeded for 127.0.0.1: 16 (lim=5) Apr 26 04:38:24 192.168.122.209 [45254.529804] [tempesta fw] Warning: frang: new TLS connections rate exceeded for 127.0.0.1: 17 (lim=5) Apr 26 04:38:24 192.168.122.209 [45254.530634] [tempesta fw] Warning: frang: new TLS connections rate exceeded for 127.0.0.1: 18 (lim=5) Apr 26 04:38:24 192.168.122.209 [45254.531452] [tempesta fw] Warning: frang: new TLS connections rate exceeded for 127.0.0.1: 19 (lim=5) Apr 26 04:38:24 192.168.122.209 [45254.532933] [tempesta fw] Warning: frang: new TLS connections rate exceeded for 127.0.0.1: 20 (lim=5) Apr 26 04:38:26 192.168.122.209 [45257.153984] [tdb] Close table 'client0.tdb' Apr 26 04:38:26 192.168.122.209 [45257.349685] [tdb] Close table 'sessions0.tdb' Apr 26 04:38:27 192.168.122.209 [45257.592593] [tdb] Close table 'filter0.tdb' Apr 26 04:38:27 192.168.122.209 [45257.593015] [tempesta fw] modules are stopped Apr 26 04:38:27 192.168.122.209 [45257.815897] [tempesta fw] exiting... Apr 26 04:38:27 192.168.122.209 [45257.961915] [tdb] Shutdown Tempesta DB Apr 26 04:38:27 192.168.122.209 [45258.162406] End test: t_frang.test_connection_rate_burst.TestFrangTLS.test_connection_rate Apr 26 04:38:27 192.168.122.209 [45258.180845] Start test: t_frang.test_connection_rate_burst.TestFrangTLS.test_connection_rate_on_the_limit Apr 26 04:38:28 192.168.122.209 [45259.340148] [tdb] Start Tempesta DB Apr 26 04:38:29 192.168.122.209 [45259.490669] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:38:30 192.168.122.209 [45260.499936] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45260.499936] Maybe that's fine, but it's worth checking the [45260.499936] config - if there is no relations between the [45260.499936] names, then host name confusion attack is possible. Apr 26 04:38:30 192.168.122.209 [45260.634725] [tempesta fw] Configuration processing is completed. Apr 26 04:38:30 192.168.122.209 [45260.686113] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:38:30 192.168.122.209 [45260.714013] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:38:30 192.168.122.209 [45260.741090] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:38:30 192.168.122.209 [45260.783308] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:38:30 192.168.122.209 [45260.785028] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:38:30 192.168.122.209 [45260.822648] [tempesta fw] Tempesta FW is ready Apr 26 04:38:33 192.168.122.209 [45263.639690] [tdb] Close table 'client0.tdb' Apr 26 04:38:33 192.168.122.209 [45263.842444] [tdb] Close table 'sessions0.tdb' Apr 26 04:38:33 192.168.122.209 [45264.079026] [tdb] Close table 'filter0.tdb' Apr 26 04:38:33 192.168.122.209 [45264.079453] [tempesta fw] modules are stopped Apr 26 04:38:33 192.168.122.209 [45264.284197] [tempesta fw] exiting... Apr 26 04:38:34 192.168.122.209 [45264.415136] [tdb] Shutdown Tempesta DB Apr 26 04:38:34 192.168.122.209 [45264.643924] End test: t_frang.test_connection_rate_burst.TestFrangTLS.test_connection_rate_on_the_limit Apr 26 04:38:34 192.168.122.209 [45264.650194] Start test: t_frang.test_connection_rate_burst.TestFrangTLS.test_connection_rate_without_reaching_the_limit Apr 26 04:38:35 192.168.122.209 [45265.849316] [tdb] Start Tempesta DB Apr 26 04:38:35 192.168.122.209 [45266.000238] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:38:36 192.168.122.209 [45267.020043] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45267.020043] Maybe that's fine, but it's worth checking the [45267.020043] config - if there is no relations between the [45267.020043] names, then host name confusion attack is possible. Apr 26 04:38:36 192.168.122.209 [45267.158790] [tempesta fw] Configuration processing is completed. Apr 26 04:38:36 192.168.122.209 [45267.210545] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:38:36 192.168.122.209 [45267.240606] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:38:36 192.168.122.209 [45267.267463] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:38:36 192.168.122.209 [45267.306784] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:38:36 192.168.122.209 [45267.308552] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:38:36 192.168.122.209 [45267.354738] [tempesta fw] Tempesta FW is ready Apr 26 04:38:39 192.168.122.209 [45270.150997] [tdb] Close table 'client0.tdb' Apr 26 04:38:39 192.168.122.209 [45270.332281] [tdb] Close table 'sessions0.tdb' Apr 26 04:38:40 192.168.122.209 [45270.568503] [tdb] Close table 'filter0.tdb' Apr 26 04:38:40 192.168.122.209 [45270.568938] [tempesta fw] modules are stopped Apr 26 04:38:40 192.168.122.209 [45270.771059] [tempesta fw] exiting... Apr 26 04:38:40 192.168.122.209 [45270.937180] [tdb] Shutdown Tempesta DB Apr 26 04:38:40 192.168.122.209 [45271.128073] End test: t_frang.test_connection_rate_burst.TestFrangTLS.test_connection_rate_without_reaching_the_limit Apr 26 04:38:40 192.168.122.209 [45271.141702] Start test: t_frang.test_header_cnt.FrangHttpHeaderCountH2.test_default_http_header_cnt_huffman Apr 26 04:38:41 192.168.122.209 [45272.315881] [tdb] Start Tempesta DB Apr 26 04:38:42 192.168.122.209 [45272.462283] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:38:42 192.168.122.209 [45273.264102] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45273.264102] Maybe that's fine, but it's worth checking the [45273.264102] config - if there is no relations between the [45273.264102] names, then host name confusion attack is possible. Apr 26 04:38:43 192.168.122.209 [45273.386873] [tempesta fw] Configuration processing is completed. Apr 26 04:38:43 192.168.122.209 [45273.437250] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:38:43 192.168.122.209 [45273.465755] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:38:43 192.168.122.209 [45273.492382] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:38:43 192.168.122.209 [45273.546852] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:38:43 192.168.122.209 [45273.548637] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:38:43 192.168.122.209 [45273.550258] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:38:43 192.168.122.209 [45273.594809] [tempesta fw] Tempesta FW is ready Apr 26 04:38:43 192.168.122.209 [45274.196579] [tdb] Close table 'client0.tdb' Apr 26 04:38:44 192.168.122.209 [45274.390939] [tdb] Close table 'sessions0.tdb' Apr 26 04:38:44 192.168.122.209 [45274.629344] [tdb] Close table 'filter0.tdb' Apr 26 04:38:44 192.168.122.209 [45274.629825] [tempesta fw] modules are stopped Apr 26 04:38:44 192.168.122.209 [45274.863562] [tempesta fw] exiting... Apr 26 04:38:44 192.168.122.209 [45274.993068] [tdb] Shutdown Tempesta DB Apr 26 04:38:44 192.168.122.209 [45275.173611] End test: t_frang.test_header_cnt.FrangHttpHeaderCountH2.test_default_http_header_cnt_huffman Apr 26 04:38:44 192.168.122.209 [45275.193964] Start test: t_frang.test_header_cnt.FrangHttpHeaderCountH2.test_default_http_header_cnt_no_huffman Apr 26 04:38:45 192.168.122.209 [45276.348656] [tdb] Start Tempesta DB Apr 26 04:38:46 192.168.122.209 [45276.484492] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:38:46 192.168.122.209 [45277.264085] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45277.264085] Maybe that's fine, but it's worth checking the [45277.264085] config - if there is no relations between the [45277.264085] names, then host name confusion attack is possible. Apr 26 04:38:46 192.168.122.209 [45277.370941] [tempesta fw] Configuration processing is completed. Apr 26 04:38:47 192.168.122.209 [45277.422930] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:38:47 192.168.122.209 [45277.452788] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:38:47 192.168.122.209 [45277.479058] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:38:47 192.168.122.209 [45277.526907] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:38:47 192.168.122.209 [45277.528651] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:38:47 192.168.122.209 [45277.530279] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:38:47 192.168.122.209 [45277.574869] [tempesta fw] Tempesta FW is ready Apr 26 04:38:47 192.168.122.209 [45278.219035] [tdb] Close table 'client0.tdb' Apr 26 04:38:48 192.168.122.209 [45278.405265] [tdb] Close table 'sessions0.tdb' Apr 26 04:38:48 192.168.122.209 [45278.624766] [tdb] Close table 'filter0.tdb' Apr 26 04:38:48 192.168.122.209 [45278.625192] [tempesta fw] modules are stopped Apr 26 04:38:48 192.168.122.209 [45278.832217] [tempesta fw] exiting... Apr 26 04:38:48 192.168.122.209 [45278.964363] [tdb] Shutdown Tempesta DB Apr 26 04:38:48 192.168.122.209 [45279.149265] End test: t_frang.test_header_cnt.FrangHttpHeaderCountH2.test_default_http_header_cnt_no_huffman Apr 26 04:38:48 192.168.122.209 [45279.162912] Start test: t_frang.test_header_cnt.FrangHttpHeaderCountH2.test_hpack_bomb_huffman Apr 26 04:38:49 192.168.122.209 [45280.349341] [tdb] Start Tempesta DB Apr 26 04:38:50 192.168.122.209 [45280.486542] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:38:50 192.168.122.209 [45281.196240] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45281.196240] Maybe that's fine, but it's worth checking the [45281.196240] config - if there is no relations between the [45281.196240] names, then host name confusion attack is possible. Apr 26 04:38:50 192.168.122.209 [45281.298967] [tempesta fw] Configuration processing is completed. Apr 26 04:38:50 192.168.122.209 [45281.358015] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:38:51 192.168.122.209 [45281.390866] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:38:51 192.168.122.209 [45281.417073] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:38:51 192.168.122.209 [45281.466983] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:38:51 192.168.122.209 [45281.468720] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:38:51 192.168.122.209 [45281.470357] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:38:51 192.168.122.209 [45281.518924] [tempesta fw] Tempesta FW is ready Apr 26 04:38:51 192.168.122.209 [45282.251384] [tempesta fw] Warning: frang: HTTP headers count exceeded for 127.0.0.2: 7 (lim=6) Apr 26 04:38:54 192.168.122.209 [45284.664781] [tdb] Close table 'client0.tdb' Apr 26 04:38:54 192.168.122.209 [45284.864590] [tdb] Close table 'sessions0.tdb' Apr 26 04:38:54 192.168.122.209 [45285.094054] [tdb] Close table 'filter0.tdb' Apr 26 04:38:54 192.168.122.209 [45285.094481] [tempesta fw] modules are stopped Apr 26 04:38:54 192.168.122.209 [45285.329057] [tempesta fw] exiting... Apr 26 04:38:55 192.168.122.209 [45285.477031] [tdb] Shutdown Tempesta DB Apr 26 04:38:55 192.168.122.209 [45285.669983] End test: t_frang.test_header_cnt.FrangHttpHeaderCountH2.test_hpack_bomb_huffman Apr 26 04:38:55 192.168.122.209 [45285.683726] Start test: t_frang.test_header_cnt.FrangHttpHeaderCountH2.test_hpack_bomb_no_huffman Apr 26 04:38:56 192.168.122.209 [45286.848878] [tdb] Start Tempesta DB Apr 26 04:38:56 192.168.122.209 [45286.986361] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:38:57 192.168.122.209 [45287.724287] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45287.724287] Maybe that's fine, but it's worth checking the [45287.724287] config - if there is no relations between the [45287.724287] names, then host name confusion attack is possible. Apr 26 04:38:57 192.168.122.209 [45287.831063] [tempesta fw] Configuration processing is completed. Apr 26 04:38:57 192.168.122.209 [45287.887981] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:38:57 192.168.122.209 [45287.915852] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:38:57 192.168.122.209 [45287.942805] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:38:57 192.168.122.209 [45287.983041] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:38:57 192.168.122.209 [45287.984718] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:38:57 192.168.122.209 [45287.986375] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:38:57 192.168.122.209 [45288.022983] [tempesta fw] Tempesta FW is ready Apr 26 04:38:58 192.168.122.209 [45288.747781] [tempesta fw] Warning: frang: HTTP headers count exceeded for 127.0.0.2: 7 (lim=6) Apr 26 04:39:00 192.168.122.209 [45291.148245] [tdb] Close table 'client0.tdb' Apr 26 04:39:00 192.168.122.209 [45291.349158] [tdb] Close table 'sessions0.tdb' Apr 26 04:39:01 192.168.122.209 [45291.601458] [tdb] Close table 'filter0.tdb' Apr 26 04:39:01 192.168.122.209 [45291.601888] [tempesta fw] modules are stopped Apr 26 04:39:01 192.168.122.209 [45291.801138] [tempesta fw] exiting... Apr 26 04:39:01 192.168.122.209 [45291.952706] [tdb] Shutdown Tempesta DB Apr 26 04:39:01 192.168.122.209 [45292.159959] End test: t_frang.test_header_cnt.FrangHttpHeaderCountH2.test_hpack_bomb_no_huffman Apr 26 04:39:01 192.168.122.209 [45292.170382] Start test: t_frang.test_header_cnt.FrangHttpHeaderCountH2.test_not_reaching_limit_headers_as_bytes_huffman Apr 26 04:39:03 192.168.122.209 [45293.389439] [tdb] Start Tempesta DB Apr 26 04:39:03 192.168.122.209 [45293.533844] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:39:03 192.168.122.209 [45294.284446] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45294.284446] Maybe that's fine, but it's worth checking the [45294.284446] config - if there is no relations between the [45294.284446] names, then host name confusion attack is possible. Apr 26 04:39:04 192.168.122.209 [45294.387135] [tempesta fw] Configuration processing is completed. Apr 26 04:39:04 192.168.122.209 [45294.437558] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:39:04 192.168.122.209 [45294.465186] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:39:04 192.168.122.209 [45294.496622] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:39:04 192.168.122.209 [45294.583127] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:39:04 192.168.122.209 [45294.584809] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:39:04 192.168.122.209 [45294.586452] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:39:04 192.168.122.209 [45294.623122] [tempesta fw] Tempesta FW is ready Apr 26 04:39:04 192.168.122.209 [45295.242948] [tdb] Close table 'client0.tdb' Apr 26 04:39:05 192.168.122.209 [45295.436657] [tdb] Close table 'sessions0.tdb' Apr 26 04:39:05 192.168.122.209 [45295.660392] [tdb] Close table 'filter0.tdb' Apr 26 04:39:05 192.168.122.209 [45295.660813] [tempesta fw] modules are stopped Apr 26 04:39:05 192.168.122.209 [45295.864354] [tempesta fw] exiting... Apr 26 04:39:05 192.168.122.209 [45295.975423] [tdb] Shutdown Tempesta DB Apr 26 04:39:05 192.168.122.209 [45296.167265] End test: t_frang.test_header_cnt.FrangHttpHeaderCountH2.test_not_reaching_limit_headers_as_bytes_huffman Apr 26 04:39:05 192.168.122.209 [45296.188995] Start test: t_frang.test_header_cnt.FrangHttpHeaderCountH2.test_not_reaching_limit_headers_as_bytes_no_huffman Apr 26 04:39:07 192.168.122.209 [45297.429572] [tdb] Start Tempesta DB Apr 26 04:39:07 192.168.122.209 [45297.579744] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:39:07 192.168.122.209 [45298.344403] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45298.344403] Maybe that's fine, but it's worth checking the [45298.344403] config - if there is no relations between the [45298.344403] names, then host name confusion attack is possible. Apr 26 04:39:08 192.168.122.209 [45298.447175] [tempesta fw] Configuration processing is completed. Apr 26 04:39:08 192.168.122.209 [45298.498007] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:39:08 192.168.122.209 [45298.525817] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:39:08 192.168.122.209 [45298.553149] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:39:08 192.168.122.209 [45298.603205] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:39:08 192.168.122.209 [45298.604924] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:39:08 192.168.122.209 [45298.606580] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:39:08 192.168.122.209 [45298.651142] [tempesta fw] Tempesta FW is ready Apr 26 04:39:08 192.168.122.209 [45299.315052] [tdb] Close table 'client0.tdb' Apr 26 04:39:09 192.168.122.209 [45299.506947] [tdb] Close table 'sessions0.tdb' Apr 26 04:39:09 192.168.122.209 [45299.733084] [tdb] Close table 'filter0.tdb' Apr 26 04:39:09 192.168.122.209 [45299.733521] [tempesta fw] modules are stopped Apr 26 04:39:09 192.168.122.209 [45299.906835] [tempesta fw] exiting... Apr 26 04:39:09 192.168.122.209 [45300.016920] [tdb] Shutdown Tempesta DB Apr 26 04:39:09 192.168.122.209 [45300.212251] End test: t_frang.test_header_cnt.FrangHttpHeaderCountH2.test_not_reaching_limit_headers_as_bytes_no_huffman Apr 26 04:39:09 192.168.122.209 [45300.235396] Start test: t_frang.test_header_cnt.FrangHttpHeaderCountH2.test_not_reaching_the_limit Apr 26 04:39:11 192.168.122.209 [45301.391700] [tdb] Start Tempesta DB Apr 26 04:39:11 192.168.122.209 [45301.518195] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:39:11 192.168.122.209 [45302.260484] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45302.260484] Maybe that's fine, but it's worth checking the [45302.260484] config - if there is no relations between the [45302.260484] names, then host name confusion attack is possible. Apr 26 04:39:12 192.168.122.209 [45302.379213] [tempesta fw] Configuration processing is completed. Apr 26 04:39:12 192.168.122.209 [45302.428618] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:39:12 192.168.122.209 [45302.457286] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:39:12 192.168.122.209 [45302.484052] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:39:12 192.168.122.209 [45302.523160] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:39:12 192.168.122.209 [45302.524828] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:39:12 192.168.122.209 [45302.526477] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:39:12 192.168.122.209 [45302.563187] [tempesta fw] Tempesta FW is ready Apr 26 04:39:12 192.168.122.209 [45303.154659] [tdb] Close table 'client0.tdb' Apr 26 04:39:13 192.168.122.209 [45303.385652] [tdb] Close table 'sessions0.tdb' Apr 26 04:39:13 192.168.122.209 [45303.610701] [tdb] Close table 'filter0.tdb' Apr 26 04:39:13 192.168.122.209 [45303.611148] [tempesta fw] modules are stopped Apr 26 04:39:13 192.168.122.209 [45303.827337] [tempesta fw] exiting... Apr 26 04:39:13 192.168.122.209 [45303.978918] [tdb] Shutdown Tempesta DB Apr 26 04:39:13 192.168.122.209 [45304.199510] End test: t_frang.test_header_cnt.FrangHttpHeaderCountH2.test_not_reaching_the_limit Apr 26 04:39:13 192.168.122.209 [45304.209281] Start test: t_frang.test_header_cnt.FrangHttpHeaderCountH2.test_not_reaching_the_limit_2_huffman Apr 26 04:39:15 192.168.122.209 [45305.401764] [tdb] Start Tempesta DB Apr 26 04:39:15 192.168.122.209 [45305.535336] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:39:15 192.168.122.209 [45306.240619] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45306.240619] Maybe that's fine, but it's worth checking the [45306.240619] config - if there is no relations between the [45306.240619] names, then host name confusion attack is possible. Apr 26 04:39:15 192.168.122.209 [45306.343308] [tempesta fw] Configuration processing is completed. Apr 26 04:39:16 192.168.122.209 [45306.398110] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:39:16 192.168.122.209 [45306.428575] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:39:16 192.168.122.209 [45306.458186] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:39:16 192.168.122.209 [45306.503282] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:39:16 192.168.122.209 [45306.504981] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:39:16 192.168.122.209 [45306.506653] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:39:16 192.168.122.209 [45306.567213] [tempesta fw] Tempesta FW is ready Apr 26 04:39:16 192.168.122.209 [45307.295838] [tdb] Close table 'client0.tdb' Apr 26 04:39:17 192.168.122.209 [45307.479728] [tdb] Close table 'sessions0.tdb' Apr 26 04:39:17 192.168.122.209 [45307.709296] [tdb] Close table 'filter0.tdb' Apr 26 04:39:17 192.168.122.209 [45307.709723] [tempesta fw] modules are stopped Apr 26 04:39:17 192.168.122.209 [45307.876978] [tempesta fw] exiting... Apr 26 04:39:17 192.168.122.209 [45307.996135] [tdb] Shutdown Tempesta DB Apr 26 04:39:17 192.168.122.209 [45308.180821] End test: t_frang.test_header_cnt.FrangHttpHeaderCountH2.test_not_reaching_the_limit_2_huffman Apr 26 04:39:17 192.168.122.209 [45308.197443] Start test: t_frang.test_header_cnt.FrangHttpHeaderCountH2.test_not_reaching_the_limit_2_no_huffman Apr 26 04:39:18 192.168.122.209 [45309.298464] [tdb] Start Tempesta DB Apr 26 04:39:19 192.168.122.209 [45309.447645] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:39:19 192.168.122.209 [45310.224697] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45310.224697] Maybe that's fine, but it's worth checking the [45310.224697] config - if there is no relations between the [45310.224697] names, then host name confusion attack is possible. Apr 26 04:39:19 192.168.122.209 [45310.323384] [tempesta fw] Configuration processing is completed. Apr 26 04:39:19 192.168.122.209 [45310.374339] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:39:20 192.168.122.209 [45310.404535] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:39:20 192.168.122.209 [45310.431187] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:39:20 192.168.122.209 [45310.475338] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:39:20 192.168.122.209 [45310.477038] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:39:20 192.168.122.209 [45310.478711] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:39:20 192.168.122.209 [45310.515266] [tempesta fw] Tempesta FW is ready Apr 26 04:39:20 192.168.122.209 [45311.193033] [tdb] Close table 'client0.tdb' Apr 26 04:39:21 192.168.122.209 [45311.378340] [tdb] Close table 'sessions0.tdb' Apr 26 04:39:21 192.168.122.209 [45311.615760] [tdb] Close table 'filter0.tdb' Apr 26 04:39:21 192.168.122.209 [45311.616243] [tempesta fw] modules are stopped Apr 26 04:39:21 192.168.122.209 [45311.867226] [tempesta fw] exiting... Apr 26 04:39:21 192.168.122.209 [45311.993516] [tdb] Shutdown Tempesta DB Apr 26 04:39:21 192.168.122.209 [45312.206680] End test: t_frang.test_header_cnt.FrangHttpHeaderCountH2.test_not_reaching_the_limit_2_no_huffman Apr 26 04:39:21 192.168.122.209 [45312.220154] Start test: t_frang.test_header_cnt.FrangHttpHeaderCountH2.test_reaching_limit_headers_as_bytes_huffman Apr 26 04:39:22 192.168.122.209 [45313.349242] [tdb] Start Tempesta DB Apr 26 04:39:23 192.168.122.209 [45313.496843] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:39:23 192.168.122.209 [45314.249511] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45314.249511] Maybe that's fine, but it's worth checking the [45314.249511] config - if there is no relations between the [45314.249511] names, then host name confusion attack is possible. Apr 26 04:39:23 192.168.122.209 [45314.347408] [tempesta fw] Configuration processing is completed. Apr 26 04:39:24 192.168.122.209 [45314.397354] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:39:24 192.168.122.209 [45314.424762] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:39:24 192.168.122.209 [45314.452750] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:39:24 192.168.122.209 [45314.491376] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:39:24 192.168.122.209 [45314.493069] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:39:24 192.168.122.209 [45314.494854] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:39:24 192.168.122.209 [45314.539336] [tempesta fw] Tempesta FW is ready Apr 26 04:39:24 192.168.122.209 [45314.681376] [tempesta fw] Warning: frang: HTTP headers count exceeded for 127.0.0.2: 6 (lim=5) Apr 26 04:39:24 192.168.122.209 [45315.167374] [tdb] Close table 'client0.tdb' Apr 26 04:39:24 192.168.122.209 [45315.355936] [tdb] Close table 'sessions0.tdb' Apr 26 04:39:25 192.168.122.209 [45315.600670] [tdb] Close table 'filter0.tdb' Apr 26 04:39:25 192.168.122.209 [45315.601089] [tempesta fw] modules are stopped Apr 26 04:39:25 192.168.122.209 [45315.853170] [tempesta fw] exiting... Apr 26 04:39:25 192.168.122.209 [45315.982171] [tdb] Shutdown Tempesta DB Apr 26 04:39:25 192.168.122.209 [45316.168084] End test: t_frang.test_header_cnt.FrangHttpHeaderCountH2.test_reaching_limit_headers_as_bytes_huffman Apr 26 04:39:25 192.168.122.209 [45316.176836] Start test: t_frang.test_header_cnt.FrangHttpHeaderCountH2.test_reaching_limit_headers_as_bytes_no_huffman Apr 26 04:39:26 192.168.122.209 [45317.326543] [tdb] Start Tempesta DB Apr 26 04:39:27 192.168.122.209 [45317.477161] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:39:27 192.168.122.209 [45318.232651] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45318.232651] Maybe that's fine, but it's worth checking the [45318.232651] config - if there is no relations between the [45318.232651] names, then host name confusion attack is possible. Apr 26 04:39:27 192.168.122.209 [45318.343439] [tempesta fw] Configuration processing is completed. Apr 26 04:39:28 192.168.122.209 [45318.394343] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:39:28 192.168.122.209 [45318.424175] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:39:28 192.168.122.209 [45318.450369] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:39:28 192.168.122.209 [45318.491422] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:39:28 192.168.122.209 [45318.493093] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:39:28 192.168.122.209 [45318.494738] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:39:28 192.168.122.209 [45318.539377] [tempesta fw] Tempesta FW is ready Apr 26 04:39:28 192.168.122.209 [45318.676263] [tempesta fw] Warning: frang: HTTP headers count exceeded for 127.0.0.2: 6 (lim=5) Apr 26 04:39:28 192.168.122.209 [45319.192371] [tdb] Close table 'client0.tdb' Apr 26 04:39:29 192.168.122.209 [45319.385522] [tdb] Close table 'sessions0.tdb' Apr 26 04:39:29 192.168.122.209 [45319.629067] [tdb] Close table 'filter0.tdb' Apr 26 04:39:29 192.168.122.209 [45319.629534] [tempesta fw] modules are stopped Apr 26 04:39:29 192.168.122.209 [45319.827636] [tempesta fw] exiting... Apr 26 04:39:29 192.168.122.209 [45319.979998] [tdb] Shutdown Tempesta DB Apr 26 04:39:29 192.168.122.209 [45320.181733] End test: t_frang.test_header_cnt.FrangHttpHeaderCountH2.test_reaching_limit_headers_as_bytes_no_huffman Apr 26 04:39:29 192.168.122.209 [45320.196361] Start test: t_frang.test_header_cnt.FrangHttpHeaderCountH2.test_reaching_the_limit Apr 26 04:39:30 192.168.122.209 [45321.375563] [tdb] Start Tempesta DB Apr 26 04:39:31 192.168.122.209 [45321.521231] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:39:31 192.168.122.209 [45322.272761] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45322.272761] Maybe that's fine, but it's worth checking the [45322.272761] config - if there is no relations between the [45322.272761] names, then host name confusion attack is possible. Apr 26 04:39:31 192.168.122.209 [45322.371499] [tempesta fw] Configuration processing is completed. Apr 26 04:39:32 192.168.122.209 [45322.435379] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:39:32 192.168.122.209 [45322.465851] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:39:32 192.168.122.209 [45322.495586] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:39:32 192.168.122.209 [45322.543496] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:39:32 192.168.122.209 [45322.545219] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:39:32 192.168.122.209 [45322.546895] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:39:32 192.168.122.209 [45322.583375] [tempesta fw] Tempesta FW is ready Apr 26 04:39:32 192.168.122.209 [45322.707535] [tempesta fw] Warning: frang: HTTP headers count exceeded for 127.0.0.2: 3 (lim=2) Apr 26 04:39:32 192.168.122.209 [45323.206849] [tdb] Close table 'client0.tdb' Apr 26 04:39:33 192.168.122.209 [45323.397676] [tdb] Close table 'sessions0.tdb' Apr 26 04:39:33 192.168.122.209 [45323.626999] [tdb] Close table 'filter0.tdb' Apr 26 04:39:33 192.168.122.209 [45323.627812] [tempesta fw] modules are stopped Apr 26 04:39:33 192.168.122.209 [45323.824678] [tempesta fw] exiting... Apr 26 04:39:33 192.168.122.209 [45323.955069] [tdb] Shutdown Tempesta DB Apr 26 04:39:33 192.168.122.209 [45324.173450] End test: t_frang.test_header_cnt.FrangHttpHeaderCountH2.test_reaching_the_limit Apr 26 04:39:33 192.168.122.209 [45324.188120] Start test: t_frang.test_header_cnt.FrangHttpHeaderCountTestCase.test_default_http_header_cnt Apr 26 04:39:35 192.168.122.209 [45325.417382] [tdb] Start Tempesta DB Apr 26 04:39:35 192.168.122.209 [45325.573567] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:39:35 192.168.122.209 [45326.364804] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45326.364804] Maybe that's fine, but it's worth checking the [45326.364804] config - if there is no relations between the [45326.364804] names, then host name confusion attack is possible. Apr 26 04:39:36 192.168.122.209 [45326.475591] [tempesta fw] Configuration processing is completed. Apr 26 04:39:36 192.168.122.209 [45326.538220] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:39:36 192.168.122.209 [45326.566081] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:39:36 192.168.122.209 [45326.592579] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:39:36 192.168.122.209 [45326.647523] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:39:36 192.168.122.209 [45326.649221] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:39:36 192.168.122.209 [45326.650868] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:39:36 192.168.122.209 [45326.703473] [tempesta fw] Tempesta FW is ready Apr 26 04:39:36 192.168.122.209 [45327.360974] [tdb] Close table 'client0.tdb' Apr 26 04:39:37 192.168.122.209 [45327.555283] [tdb] Close table 'sessions0.tdb' Apr 26 04:39:37 192.168.122.209 [45327.785952] [tdb] Close table 'filter0.tdb' Apr 26 04:39:37 192.168.122.209 [45327.786388] [tempesta fw] modules are stopped Apr 26 04:39:37 192.168.122.209 [45328.004633] [tempesta fw] exiting... Apr 26 04:39:37 192.168.122.209 [45328.128833] [tdb] Shutdown Tempesta DB Apr 26 04:39:37 192.168.122.209 [45328.331704] End test: t_frang.test_header_cnt.FrangHttpHeaderCountTestCase.test_default_http_header_cnt Apr 26 04:39:37 192.168.122.209 [45328.348000] Start test: t_frang.test_header_cnt.FrangHttpHeaderCountTestCase.test_not_reaching_the_limit Apr 26 04:39:39 192.168.122.209 [45329.585992] [tdb] Start Tempesta DB Apr 26 04:39:39 192.168.122.209 [45329.733570] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:39:40 192.168.122.209 [45330.428831] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45330.428831] Maybe that's fine, but it's worth checking the [45330.428831] config - if there is no relations between the [45330.428831] names, then host name confusion attack is possible. Apr 26 04:39:40 192.168.122.209 [45330.539522] [tempesta fw] Configuration processing is completed. Apr 26 04:39:40 192.168.122.209 [45330.590484] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:39:40 192.168.122.209 [45330.620185] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:39:40 192.168.122.209 [45330.646560] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:39:40 192.168.122.209 [45330.687614] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:39:40 192.168.122.209 [45330.689293] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:39:40 192.168.122.209 [45330.691054] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:39:40 192.168.122.209 [45330.751540] [tempesta fw] Tempesta FW is ready Apr 26 04:39:41 192.168.122.209 [45331.389474] [tdb] Close table 'client0.tdb' Apr 26 04:39:41 192.168.122.209 [45331.584706] [tdb] Close table 'sessions0.tdb' Apr 26 04:39:41 192.168.122.209 [45331.846299] [tdb] Close table 'filter0.tdb' Apr 26 04:39:41 192.168.122.209 [45331.846714] [tempesta fw] modules are stopped Apr 26 04:39:41 192.168.122.209 [45332.068061] [tempesta fw] exiting... Apr 26 04:39:41 192.168.122.209 [45332.227987] [tdb] Shutdown Tempesta DB Apr 26 04:39:42 192.168.122.209 [45332.434261] End test: t_frang.test_header_cnt.FrangHttpHeaderCountTestCase.test_not_reaching_the_limit Apr 26 04:39:42 192.168.122.209 [45332.457521] Start test: t_frang.test_header_cnt.FrangHttpHeaderCountTestCase.test_not_reaching_the_limit_2 Apr 26 04:39:43 192.168.122.209 [45333.657231] [tdb] Start Tempesta DB Apr 26 04:39:43 192.168.122.209 [45333.794500] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:39:44 192.168.122.209 [45334.576809] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45334.576809] Maybe that's fine, but it's worth checking the [45334.576809] config - if there is no relations between the [45334.576809] names, then host name confusion attack is possible. Apr 26 04:39:44 192.168.122.209 [45334.684073] [tempesta fw] Configuration processing is completed. Apr 26 04:39:44 192.168.122.209 [45334.734134] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:39:44 192.168.122.209 [45334.761840] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:39:44 192.168.122.209 [45334.788573] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:39:44 192.168.122.209 [45334.835642] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:39:44 192.168.122.209 [45334.837318] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:39:44 192.168.122.209 [45334.838964] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:39:44 192.168.122.209 [45334.887572] [tempesta fw] Tempesta FW is ready Apr 26 04:39:45 192.168.122.209 [45335.526693] [tdb] Close table 'client0.tdb' Apr 26 04:39:45 192.168.122.209 [45335.713948] [tdb] Close table 'sessions0.tdb' Apr 26 04:39:45 192.168.122.209 [45335.938686] [tdb] Close table 'filter0.tdb' Apr 26 04:39:45 192.168.122.209 [45335.939149] [tempesta fw] modules are stopped Apr 26 04:39:45 192.168.122.209 [45336.139831] [tempesta fw] exiting... Apr 26 04:39:45 192.168.122.209 [45336.267535] [tdb] Shutdown Tempesta DB Apr 26 04:39:46 192.168.122.209 [45336.501563] End test: t_frang.test_header_cnt.FrangHttpHeaderCountTestCase.test_not_reaching_the_limit_2 Apr 26 04:39:46 192.168.122.209 [45336.513578] Start test: t_frang.test_header_cnt.FrangHttpHeaderCountTestCase.test_reaching_the_limit Apr 26 04:39:47 192.168.122.209 [45337.674717] [tdb] Start Tempesta DB Apr 26 04:39:47 192.168.122.209 [45337.811828] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:39:48 192.168.122.209 [45338.568915] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45338.568915] Maybe that's fine, but it's worth checking the [45338.568915] config - if there is no relations between the [45338.568915] names, then host name confusion attack is possible. Apr 26 04:39:48 192.168.122.209 [45338.667711] [tempesta fw] Configuration processing is completed. Apr 26 04:39:48 192.168.122.209 [45338.718599] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:39:48 192.168.122.209 [45338.748350] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:39:48 192.168.122.209 [45338.774959] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:39:48 192.168.122.209 [45338.823676] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:39:48 192.168.122.209 [45338.825360] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:39:48 192.168.122.209 [45338.826998] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:39:48 192.168.122.209 [45338.863620] [tempesta fw] Tempesta FW is ready Apr 26 04:39:48 192.168.122.209 [45338.980307] [tempesta fw] Warning: frang: HTTP headers count exceeded for 127.0.0.2: 3 (lim=2) Apr 26 04:39:49 192.168.122.209 [45339.495217] [tdb] Close table 'client0.tdb' Apr 26 04:39:49 192.168.122.209 [45339.686903] [tdb] Close table 'sessions0.tdb' Apr 26 04:39:49 192.168.122.209 [45339.962628] [tdb] Close table 'filter0.tdb' Apr 26 04:39:49 192.168.122.209 [45339.963062] [tempesta fw] modules are stopped Apr 26 04:39:49 192.168.122.209 [45340.156470] [tempesta fw] exiting... Apr 26 04:39:49 192.168.122.209 [45340.311098] [tdb] Shutdown Tempesta DB Apr 26 04:39:50 192.168.122.209 [45340.529187] End test: t_frang.test_header_cnt.FrangHttpHeaderCountTestCase.test_reaching_the_limit Apr 26 04:39:50 192.168.122.209 [45340.540977] Start test: t_frang.test_http_body_and_header_chunk_cnt.HttpBodyChunkCnt.test_chunk_cnt_invalid Apr 26 04:39:51 192.168.122.209 [45341.694624] [tdb] Start Tempesta DB Apr 26 04:39:51 192.168.122.209 [45341.844497] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:39:52 192.168.122.209 [45342.652963] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45342.652963] Maybe that's fine, but it's worth checking the [45342.652963] config - if there is no relations between the [45342.652963] names, then host name confusion attack is possible. Apr 26 04:39:52 192.168.122.209 [45342.759745] [tempesta fw] Configuration processing is completed. Apr 26 04:39:52 192.168.122.209 [45342.822092] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:39:52 192.168.122.209 [45342.849259] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:39:52 192.168.122.209 [45342.875673] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:39:52 192.168.122.209 [45342.927745] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:39:52 192.168.122.209 [45342.929420] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:39:52 192.168.122.209 [45342.931051] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:39:52 192.168.122.209 [45342.967675] [tempesta fw] Tempesta FW is ready Apr 26 04:39:53 192.168.122.209 [45343.481013] [tempesta fw] Warning: frang: HTTP body chunk count exceeded for 127.0.0.2: 4 (lim=3) Apr 26 04:39:53 192.168.122.209 [45343.483475] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:39:53 192.168.122.209 [45344.016964] [tdb] Close table 'client0.tdb' Apr 26 04:39:53 192.168.122.209 [45344.184609] [tdb] Close table 'sessions0.tdb' Apr 26 04:39:54 192.168.122.209 [45344.426344] [tdb] Close table 'filter0.tdb' Apr 26 04:39:54 192.168.122.209 [45344.426792] [tempesta fw] modules are stopped Apr 26 04:39:54 192.168.122.209 [45344.634643] [tempesta fw] exiting... Apr 26 04:39:54 192.168.122.209 [45344.770041] [tdb] Shutdown Tempesta DB Apr 26 04:39:54 192.168.122.209 [45344.963476] End test: t_frang.test_http_body_and_header_chunk_cnt.HttpBodyChunkCnt.test_chunk_cnt_invalid Apr 26 04:39:54 192.168.122.209 [45344.983527] Start test: t_frang.test_http_body_and_header_chunk_cnt.HttpBodyChunkCnt.test_chunk_cnt_ok Apr 26 04:39:55 192.168.122.209 [45346.134973] [tdb] Start Tempesta DB Apr 26 04:39:55 192.168.122.209 [45346.272793] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:39:56 192.168.122.209 [45347.100964] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45347.100964] Maybe that's fine, but it's worth checking the [45347.100964] config - if there is no relations between the [45347.100964] names, then host name confusion attack is possible. Apr 26 04:39:56 192.168.122.209 [45347.211815] [tempesta fw] Configuration processing is completed. Apr 26 04:39:56 192.168.122.209 [45347.269966] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:39:56 192.168.122.209 [45347.297082] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:39:56 192.168.122.209 [45347.323459] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:39:57 192.168.122.209 [45347.391829] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:39:57 192.168.122.209 [45347.393522] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:39:57 192.168.122.209 [45347.395174] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:39:57 192.168.122.209 [45347.431736] [tempesta fw] Tempesta FW is ready Apr 26 04:39:58 192.168.122.209 [45348.464444] [tdb] Close table 'client0.tdb' Apr 26 04:39:58 192.168.122.209 [45348.665791] [tdb] Close table 'sessions0.tdb' Apr 26 04:39:58 192.168.122.209 [45348.905263] [tdb] Close table 'filter0.tdb' Apr 26 04:39:58 192.168.122.209 [45348.905708] [tempesta fw] modules are stopped Apr 26 04:39:58 192.168.122.209 [45349.081193] [tempesta fw] exiting... Apr 26 04:39:58 192.168.122.209 [45349.194748] [tdb] Shutdown Tempesta DB Apr 26 04:39:59 192.168.122.209 [45349.384301] End test: t_frang.test_http_body_and_header_chunk_cnt.HttpBodyChunkCnt.test_chunk_cnt_ok Apr 26 04:39:59 192.168.122.209 [45349.399437] Start test: t_frang.test_http_body_and_header_chunk_cnt.HttpBodyChunkCnt.test_chunk_cnt_ok_2 Apr 26 04:40:00 192.168.122.209 [45350.654640] [tdb] Start Tempesta DB Apr 26 04:40:00 192.168.122.209 [45350.787652] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:40:01 192.168.122.209 [45351.497023] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45351.497023] Maybe that's fine, but it's worth checking the [45351.497023] config - if there is no relations between the [45351.497023] names, then host name confusion attack is possible. Apr 26 04:40:01 192.168.122.209 [45351.603825] [tempesta fw] Configuration processing is completed. Apr 26 04:40:01 192.168.122.209 [45351.660240] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:40:01 192.168.122.209 [45351.690683] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:40:01 192.168.122.209 [45351.717676] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:40:01 192.168.122.209 [45351.755794] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:40:01 192.168.122.209 [45351.756820] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:40:01 192.168.122.209 [45351.757799] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:40:01 192.168.122.209 [45351.799727] [tempesta fw] Tempesta FW is ready Apr 26 04:40:02 192.168.122.209 [45352.815796] [tdb] Close table 'client0.tdb' Apr 26 04:40:02 192.168.122.209 [45353.017247] [tdb] Close table 'sessions0.tdb' Apr 26 04:40:02 192.168.122.209 [45353.224684] [tdb] Close table 'filter0.tdb' Apr 26 04:40:02 192.168.122.209 [45353.225119] [tempesta fw] modules are stopped Apr 26 04:40:03 192.168.122.209 [45353.448631] [tempesta fw] exiting... Apr 26 04:40:03 192.168.122.209 [45353.587889] [tdb] Shutdown Tempesta DB Apr 26 04:40:03 192.168.122.209 [45353.835526] End test: t_frang.test_http_body_and_header_chunk_cnt.HttpBodyChunkCnt.test_chunk_cnt_ok_2 Apr 26 04:40:03 192.168.122.209 [45353.846958] Start test: t_frang.test_http_body_and_header_chunk_cnt.HttpBodyChunkCntH2.test_chunk_cnt_invalid Apr 26 04:40:04 192.168.122.209 [45355.053571] [tdb] Start Tempesta DB Apr 26 04:40:04 192.168.122.209 [45355.198497] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:40:05 192.168.122.209 [45355.957152] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45355.957152] Maybe that's fine, but it's worth checking the [45355.957152] config - if there is no relations between the [45355.957152] names, then host name confusion attack is possible. Apr 26 04:40:05 192.168.122.209 [45356.067927] [tempesta fw] Configuration processing is completed. Apr 26 04:40:05 192.168.122.209 [45356.118829] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:40:05 192.168.122.209 [45356.146435] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:40:05 192.168.122.209 [45356.172888] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:40:05 192.168.122.209 [45356.215916] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:40:05 192.168.122.209 [45356.217593] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:40:05 192.168.122.209 [45356.219221] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:40:05 192.168.122.209 [45356.267851] [tempesta fw] Tempesta FW is ready Apr 26 04:40:06 192.168.122.209 [45356.412596] [tempesta fw] Warning: frang: HTTP body chunk count exceeded for 127.0.0.2: 4 (lim=3) Apr 26 04:40:06 192.168.122.209 [45356.413415] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:40:06 192.168.122.209 [45356.929399] [tdb] Close table 'client0.tdb' Apr 26 04:40:06 192.168.122.209 [45357.132057] [tdb] Close table 'sessions0.tdb' Apr 26 04:40:06 192.168.122.209 [45357.357271] [tdb] Close table 'filter0.tdb' Apr 26 04:40:06 192.168.122.209 [45357.357703] [tempesta fw] modules are stopped Apr 26 04:40:07 192.168.122.209 [45357.553459] [tempesta fw] exiting... Apr 26 04:40:07 192.168.122.209 [45357.659900] [tdb] Shutdown Tempesta DB Apr 26 04:40:07 192.168.122.209 [45357.906862] End test: t_frang.test_http_body_and_header_chunk_cnt.HttpBodyChunkCntH2.test_chunk_cnt_invalid Apr 26 04:40:07 192.168.122.209 [45357.918767] Start test: t_frang.test_http_body_and_header_chunk_cnt.HttpBodyChunkCntH2.test_chunk_cnt_ok Apr 26 04:40:08 192.168.122.209 [45359.090645] [tdb] Start Tempesta DB Apr 26 04:40:08 192.168.122.209 [45359.233994] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:40:09 192.168.122.209 [45359.981257] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45359.981257] Maybe that's fine, but it's worth checking the [45359.981257] config - if there is no relations between the [45359.981257] names, then host name confusion attack is possible. Apr 26 04:40:09 192.168.122.209 [45360.095998] [tempesta fw] Configuration processing is completed. Apr 26 04:40:09 192.168.122.209 [45360.150692] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:40:09 192.168.122.209 [45360.183221] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:40:09 192.168.122.209 [45360.212479] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:40:09 192.168.122.209 [45360.255957] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:40:09 192.168.122.209 [45360.257704] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:40:09 192.168.122.209 [45360.259366] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:40:09 192.168.122.209 [45360.299910] [tempesta fw] Tempesta FW is ready Apr 26 04:40:10 192.168.122.209 [45360.936535] [tdb] Close table 'client0.tdb' Apr 26 04:40:10 192.168.122.209 [45361.127610] [tdb] Close table 'sessions0.tdb' Apr 26 04:40:11 192.168.122.209 [45361.386233] [tdb] Close table 'filter0.tdb' Apr 26 04:40:11 192.168.122.209 [45361.386672] [tempesta fw] modules are stopped Apr 26 04:40:11 192.168.122.209 [45361.611512] [tempesta fw] exiting... Apr 26 04:40:11 192.168.122.209 [45361.751245] [tdb] Shutdown Tempesta DB Apr 26 04:40:11 192.168.122.209 [45361.981225] End test: t_frang.test_http_body_and_header_chunk_cnt.HttpBodyChunkCntH2.test_chunk_cnt_ok Apr 26 04:40:11 192.168.122.209 [45361.991496] Start test: t_frang.test_http_body_and_header_chunk_cnt.HttpBodyChunkCntH2.test_chunk_cnt_ok_2 Apr 26 04:40:12 192.168.122.209 [45363.222145] [tdb] Start Tempesta DB Apr 26 04:40:12 192.168.122.209 [45363.351202] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:40:13 192.168.122.209 [45364.113277] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45364.113277] Maybe that's fine, but it's worth checking the [45364.113277] config - if there is no relations between the [45364.113277] names, then host name confusion attack is possible. Apr 26 04:40:13 192.168.122.209 [45364.216048] [tempesta fw] Configuration processing is completed. Apr 26 04:40:13 192.168.122.209 [45364.266070] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:40:13 192.168.122.209 [45364.293103] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:40:13 192.168.122.209 [45364.319302] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:40:13 192.168.122.209 [45364.360007] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:40:13 192.168.122.209 [45364.361697] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:40:13 192.168.122.209 [45364.363338] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:40:14 192.168.122.209 [45364.399954] [tempesta fw] Tempesta FW is ready Apr 26 04:40:14 192.168.122.209 [45365.061037] [tdb] Close table 'client0.tdb' Apr 26 04:40:14 192.168.122.209 [45365.262934] [tdb] Close table 'sessions0.tdb' Apr 26 04:40:15 192.168.122.209 [45365.481508] [tdb] Close table 'filter0.tdb' Apr 26 04:40:15 192.168.122.209 [45365.481942] [tempesta fw] modules are stopped Apr 26 04:40:15 192.168.122.209 [45365.655944] [tempesta fw] exiting... Apr 26 04:40:15 192.168.122.209 [45365.817958] [tdb] Shutdown Tempesta DB Apr 26 04:40:15 192.168.122.209 [45366.038881] End test: t_frang.test_http_body_and_header_chunk_cnt.HttpBodyChunkCntH2.test_chunk_cnt_ok_2 Apr 26 04:40:15 192.168.122.209 [45366.055365] Start test: t_frang.test_http_body_and_header_chunk_cnt.HttpHeaderChunkCnt.test_chunk_cnt_invalid Apr 26 04:40:16 192.168.122.209 [45367.206237] [tdb] Start Tempesta DB Apr 26 04:40:16 192.168.122.209 [45367.362876] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:40:17 192.168.122.209 [45368.194598] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45368.194598] Maybe that's fine, but it's worth checking the [45368.194598] config - if there is no relations between the [45368.194598] names, then host name confusion attack is possible. Apr 26 04:40:17 192.168.122.209 [45368.300101] [tempesta fw] Configuration processing is completed. Apr 26 04:40:17 192.168.122.209 [45368.353961] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:40:18 192.168.122.209 [45368.386078] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:40:18 192.168.122.209 [45368.415183] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:40:18 192.168.122.209 [45368.456067] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:40:18 192.168.122.209 [45368.457782] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:40:18 192.168.122.209 [45368.459451] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:40:18 192.168.122.209 [45368.512016] [tempesta fw] Tempesta FW is ready Apr 26 04:40:18 192.168.122.209 [45368.837957] [tempesta fw] Warning: frang: HTTP header chunk count exceeded for 127.0.0.2: 3 (lim=2) Apr 26 04:40:18 192.168.122.209 [45368.840513] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:40:19 192.168.122.209 [45369.384997] [tdb] Close table 'client0.tdb' Apr 26 04:40:19 192.168.122.209 [45369.578683] [tdb] Close table 'sessions0.tdb' Apr 26 04:40:19 192.168.122.209 [45369.818419] [tdb] Close table 'filter0.tdb' Apr 26 04:40:19 192.168.122.209 [45369.818858] [tempesta fw] modules are stopped Apr 26 04:40:19 192.168.122.209 [45370.056526] [tempesta fw] exiting... Apr 26 04:40:19 192.168.122.209 [45370.205408] [tdb] Shutdown Tempesta DB Apr 26 04:40:20 192.168.122.209 [45370.385600] End test: t_frang.test_http_body_and_header_chunk_cnt.HttpHeaderChunkCnt.test_chunk_cnt_invalid Apr 26 04:40:20 192.168.122.209 [45370.405965] Start test: t_frang.test_http_body_and_header_chunk_cnt.HttpHeaderChunkCnt.test_chunk_cnt_ok Apr 26 04:40:21 192.168.122.209 [45371.574449] [tdb] Start Tempesta DB Apr 26 04:40:21 192.168.122.209 [45371.717511] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:40:22 192.168.122.209 [45372.489431] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45372.489431] Maybe that's fine, but it's worth checking the [45372.489431] config - if there is no relations between the [45372.489431] names, then host name confusion attack is possible. Apr 26 04:40:22 192.168.122.209 [45372.592146] [tempesta fw] Configuration processing is completed. Apr 26 04:40:22 192.168.122.209 [45372.649727] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:40:22 192.168.122.209 [45372.680004] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:40:22 192.168.122.209 [45372.708859] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:40:22 192.168.122.209 [45372.764118] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:40:22 192.168.122.209 [45372.765817] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:40:22 192.168.122.209 [45372.767498] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:40:22 192.168.122.209 [45372.808059] [tempesta fw] Tempesta FW is ready Apr 26 04:40:23 192.168.122.209 [45373.662433] [tdb] Close table 'client0.tdb' Apr 26 04:40:23 192.168.122.209 [45373.842046] [tdb] Close table 'sessions0.tdb' Apr 26 04:40:23 192.168.122.209 [45374.077991] [tdb] Close table 'filter0.tdb' Apr 26 04:40:23 192.168.122.209 [45374.078443] [tempesta fw] modules are stopped Apr 26 04:40:23 192.168.122.209 [45374.313481] [tempesta fw] exiting... Apr 26 04:40:24 192.168.122.209 [45374.440764] [tdb] Shutdown Tempesta DB Apr 26 04:40:24 192.168.122.209 [45374.642899] End test: t_frang.test_http_body_and_header_chunk_cnt.HttpHeaderChunkCnt.test_chunk_cnt_ok Apr 26 04:40:24 192.168.122.209 [45374.661345] Start test: t_frang.test_http_body_and_header_chunk_cnt.HttpHeaderChunkCnt.test_chunk_cnt_ok_2 Apr 26 04:40:25 192.168.122.209 [45375.861495] [tdb] Start Tempesta DB Apr 26 04:40:25 192.168.122.209 [45376.002102] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:40:26 192.168.122.209 [45376.817448] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45376.817448] Maybe that's fine, but it's worth checking the [45376.817448] config - if there is no relations between the [45376.817448] names, then host name confusion attack is possible. Apr 26 04:40:26 192.168.122.209 [45376.916189] [tempesta fw] Configuration processing is completed. Apr 26 04:40:26 192.168.122.209 [45376.968673] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:40:26 192.168.122.209 [45376.998220] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:40:26 192.168.122.209 [45377.025294] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:40:26 192.168.122.209 [45377.072182] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:40:26 192.168.122.209 [45377.073872] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:40:26 192.168.122.209 [45377.075509] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:40:26 192.168.122.209 [45377.116128] [tempesta fw] Tempesta FW is ready Apr 26 04:40:27 192.168.122.209 [45377.945892] [tdb] Close table 'client0.tdb' Apr 26 04:40:27 192.168.122.209 [45378.143559] [tdb] Close table 'sessions0.tdb' Apr 26 04:40:28 192.168.122.209 [45378.389463] [tdb] Close table 'filter0.tdb' Apr 26 04:40:28 192.168.122.209 [45378.389920] [tempesta fw] modules are stopped Apr 26 04:40:28 192.168.122.209 [45378.592372] [tempesta fw] exiting... Apr 26 04:40:28 192.168.122.209 [45378.738477] [tdb] Shutdown Tempesta DB Apr 26 04:40:28 192.168.122.209 [45378.939348] End test: t_frang.test_http_body_and_header_chunk_cnt.HttpHeaderChunkCnt.test_chunk_cnt_ok_2 Apr 26 04:40:28 192.168.122.209 [45378.952544] Start test: t_frang.test_http_body_and_header_chunk_cnt.HttpHeaderChunkCntH2.test_chunk_cnt_invalid Apr 26 04:40:29 192.168.122.209 [45380.260204] [tdb] Start Tempesta DB Apr 26 04:40:30 192.168.122.209 [45380.409315] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:40:30 192.168.122.209 [45381.245468] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45381.245468] Maybe that's fine, but it's worth checking the [45381.245468] config - if there is no relations between the [45381.245468] names, then host name confusion attack is possible. Apr 26 04:40:30 192.168.122.209 [45381.368251] [tempesta fw] Configuration processing is completed. Apr 26 04:40:31 192.168.122.209 [45381.420642] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:40:31 192.168.122.209 [45381.448538] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:40:31 192.168.122.209 [45381.475447] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:40:31 192.168.122.209 [45381.532248] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:40:31 192.168.122.209 [45381.533947] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:40:31 192.168.122.209 [45381.535584] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:40:31 192.168.122.209 [45381.572179] [tempesta fw] Tempesta FW is ready Apr 26 04:40:31 192.168.122.209 [45381.705374] [tempesta fw] Warning: frang: HTTP header chunk count exceeded for 127.0.0.2: 3 (lim=2) Apr 26 04:40:31 192.168.122.209 [45381.706948] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:40:31 192.168.122.209 [45382.240422] [tdb] Close table 'client0.tdb' Apr 26 04:40:32 192.168.122.209 [45382.445985] [tdb] Close table 'sessions0.tdb' Apr 26 04:40:32 192.168.122.209 [45382.661552] [tdb] Close table 'filter0.tdb' Apr 26 04:40:32 192.168.122.209 [45382.661984] [tempesta fw] modules are stopped Apr 26 04:40:32 192.168.122.209 [45382.871940] [tempesta fw] exiting... Apr 26 04:40:32 192.168.122.209 [45383.012748] [tdb] Shutdown Tempesta DB Apr 26 04:40:32 192.168.122.209 [45383.219064] End test: t_frang.test_http_body_and_header_chunk_cnt.HttpHeaderChunkCntH2.test_chunk_cnt_invalid Apr 26 04:40:32 192.168.122.209 [45383.242757] Start test: t_frang.test_http_body_and_header_chunk_cnt.HttpHeaderChunkCntH2.test_chunk_cnt_ok Apr 26 04:40:34 192.168.122.209 [45384.575127] [tdb] Start Tempesta DB Apr 26 04:40:34 192.168.122.209 [45384.717303] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:40:35 192.168.122.209 [45385.533571] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45385.533571] Maybe that's fine, but it's worth checking the [45385.533571] config - if there is no relations between the [45385.533571] names, then host name confusion attack is possible. Apr 26 04:40:35 192.168.122.209 [45385.636294] [tempesta fw] Configuration processing is completed. Apr 26 04:40:35 192.168.122.209 [45385.687384] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:40:35 192.168.122.209 [45385.717896] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:40:35 192.168.122.209 [45385.745207] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:40:35 192.168.122.209 [45385.784283] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:40:35 192.168.122.209 [45385.785963] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:40:35 192.168.122.209 [45385.787599] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:40:35 192.168.122.209 [45385.824223] [tempesta fw] Tempesta FW is ready Apr 26 04:40:36 192.168.122.209 [45386.479360] [tdb] Close table 'client0.tdb' Apr 26 04:40:36 192.168.122.209 [45386.690057] [tdb] Close table 'sessions0.tdb' Apr 26 04:40:36 192.168.122.209 [45386.901642] [tdb] Close table 'filter0.tdb' Apr 26 04:40:36 192.168.122.209 [45386.902096] [tempesta fw] modules are stopped Apr 26 04:40:36 192.168.122.209 [45387.112725] [tempesta fw] exiting... Apr 26 04:40:36 192.168.122.209 [45387.265208] [tdb] Shutdown Tempesta DB Apr 26 04:40:37 192.168.122.209 [45387.498053] End test: t_frang.test_http_body_and_header_chunk_cnt.HttpHeaderChunkCntH2.test_chunk_cnt_ok Apr 26 04:40:37 192.168.122.209 [45387.518301] Start test: t_frang.test_http_body_and_header_chunk_cnt.HttpHeaderChunkCntH2.test_chunk_cnt_ok_2 Apr 26 04:40:38 192.168.122.209 [45388.758946] [tdb] Start Tempesta DB Apr 26 04:40:38 192.168.122.209 [45388.892911] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:40:39 192.168.122.209 [45389.657623] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45389.657623] Maybe that's fine, but it's worth checking the [45389.657623] config - if there is no relations between the [45389.657623] names, then host name confusion attack is possible. Apr 26 04:40:39 192.168.122.209 [45389.764338] [tempesta fw] Configuration processing is completed. Apr 26 04:40:39 192.168.122.209 [45389.824238] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:40:39 192.168.122.209 [45389.862196] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:40:39 192.168.122.209 [45389.898216] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:40:39 192.168.122.209 [45389.936273] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:40:39 192.168.122.209 [45389.937300] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:40:39 192.168.122.209 [45389.938302] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:40:39 192.168.122.209 [45389.976273] [tempesta fw] Tempesta FW is ready Apr 26 04:40:40 192.168.122.209 [45390.686572] [tdb] Close table 'client0.tdb' Apr 26 04:40:40 192.168.122.209 [45390.883237] [tdb] Close table 'sessions0.tdb' Apr 26 04:40:40 192.168.122.209 [45391.112040] [tdb] Close table 'filter0.tdb' Apr 26 04:40:40 192.168.122.209 [45391.112548] [tempesta fw] modules are stopped Apr 26 04:40:40 192.168.122.209 [45391.317462] [tempesta fw] exiting... Apr 26 04:40:41 192.168.122.209 [45391.458469] [tdb] Shutdown Tempesta DB Apr 26 04:40:41 192.168.122.209 [45391.649827] End test: t_frang.test_http_body_and_header_chunk_cnt.HttpHeaderChunkCntH2.test_chunk_cnt_ok_2 Apr 26 04:40:41 192.168.122.209 [45391.666632] Start test: t_frang.test_http_ct_required.FrangHttpCtRequiredH2.test_content_type_set_ok Apr 26 04:40:42 192.168.122.209 [45392.982260] [tdb] Start Tempesta DB Apr 26 04:40:42 192.168.122.209 [45393.135704] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:40:43 192.168.122.209 [45393.873654] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45393.873654] Maybe that's fine, but it's worth checking the [45393.873654] config - if there is no relations between the [45393.873654] names, then host name confusion attack is possible. Apr 26 04:40:43 192.168.122.209 [45393.980381] [tempesta fw] Configuration processing is completed. Apr 26 04:40:43 192.168.122.209 [45394.030830] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:40:43 192.168.122.209 [45394.059017] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:40:43 192.168.122.209 [45394.085703] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:40:43 192.168.122.209 [45394.136392] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:40:43 192.168.122.209 [45394.138071] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:40:43 192.168.122.209 [45394.139752] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:40:43 192.168.122.209 [45394.188341] [tempesta fw] Tempesta FW is ready Apr 26 04:40:44 192.168.122.209 [45394.833957] [tdb] Close table 'client0.tdb' Apr 26 04:40:44 192.168.122.209 [45395.022003] [tdb] Close table 'sessions0.tdb' Apr 26 04:40:44 192.168.122.209 [45395.257602] [tdb] Close table 'filter0.tdb' Apr 26 04:40:44 192.168.122.209 [45395.258051] [tempesta fw] modules are stopped Apr 26 04:40:45 192.168.122.209 [45395.430083] [tempesta fw] exiting... Apr 26 04:40:45 192.168.122.209 [45395.566236] [tdb] Shutdown Tempesta DB Apr 26 04:40:45 192.168.122.209 [45395.766030] End test: t_frang.test_http_ct_required.FrangHttpCtRequiredH2.test_content_type_set_ok Apr 26 04:40:45 192.168.122.209 [45395.786937] Start test: t_frang.test_http_ct_required.FrangHttpCtRequiredH2.test_default_http_ct_required Apr 26 04:40:46 192.168.122.209 [45396.944606] [tdb] Start Tempesta DB Apr 26 04:40:46 192.168.122.209 [45397.084814] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:40:47 192.168.122.209 [45397.845667] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45397.845667] Maybe that's fine, but it's worth checking the [45397.845667] config - if there is no relations between the [45397.845667] names, then host name confusion attack is possible. Apr 26 04:40:47 192.168.122.209 [45397.944468] [tempesta fw] Configuration processing is completed. Apr 26 04:40:47 192.168.122.209 [45397.999682] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:40:47 192.168.122.209 [45398.030280] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:40:47 192.168.122.209 [45398.057188] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:40:47 192.168.122.209 [45398.108436] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:40:47 192.168.122.209 [45398.110117] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:40:47 192.168.122.209 [45398.111774] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:40:47 192.168.122.209 [45398.148384] [tempesta fw] Tempesta FW is ready Apr 26 04:40:48 192.168.122.209 [45398.752975] [tdb] Close table 'client0.tdb' Apr 26 04:40:48 192.168.122.209 [45398.954798] [tdb] Close table 'sessions0.tdb' Apr 26 04:40:48 192.168.122.209 [45399.183298] [tdb] Close table 'filter0.tdb' Apr 26 04:40:48 192.168.122.209 [45399.183733] [tempesta fw] modules are stopped Apr 26 04:40:49 192.168.122.209 [45399.428219] [tempesta fw] exiting... Apr 26 04:40:49 192.168.122.209 [45399.561775] [tdb] Shutdown Tempesta DB Apr 26 04:40:49 192.168.122.209 [45399.781535] End test: t_frang.test_http_ct_required.FrangHttpCtRequiredH2.test_default_http_ct_required Apr 26 04:40:49 192.168.122.209 [45399.798412] Start test: t_frang.test_http_ct_required.FrangHttpCtRequiredH2.test_missing_content_type Apr 26 04:40:50 192.168.122.209 [45401.055787] [tdb] Start Tempesta DB Apr 26 04:40:50 192.168.122.209 [45401.214620] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:40:51 192.168.122.209 [45402.013701] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45402.013701] Maybe that's fine, but it's worth checking the [45402.013701] config - if there is no relations between the [45402.013701] names, then host name confusion attack is possible. Apr 26 04:40:51 192.168.122.209 [45402.116507] [tempesta fw] Configuration processing is completed. Apr 26 04:40:51 192.168.122.209 [45402.166531] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:40:51 192.168.122.209 [45402.194189] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:40:51 192.168.122.209 [45402.221176] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:40:51 192.168.122.209 [45402.268485] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:40:51 192.168.122.209 [45402.270160] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:40:51 192.168.122.209 [45402.271818] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:40:51 192.168.122.209 [45402.312434] [tempesta fw] Tempesta FW is ready Apr 26 04:40:52 192.168.122.209 [45402.444712] [tempesta fw] Warning: frang: Content-Type header field for 127.0.0.2 is missed Apr 26 04:40:52 192.168.122.209 [45402.446386] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:40:52 192.168.122.209 [45402.958865] [tdb] Close table 'client0.tdb' Apr 26 04:40:52 192.168.122.209 [45403.157937] [tdb] Close table 'sessions0.tdb' Apr 26 04:40:53 192.168.122.209 [45403.405412] [tdb] Close table 'filter0.tdb' Apr 26 04:40:53 192.168.122.209 [45403.405846] [tempesta fw] modules are stopped Apr 26 04:40:53 192.168.122.209 [45403.616981] [tempesta fw] exiting... Apr 26 04:40:53 192.168.122.209 [45403.740218] [tdb] Shutdown Tempesta DB Apr 26 04:40:53 192.168.122.209 [45403.962187] End test: t_frang.test_http_ct_required.FrangHttpCtRequiredH2.test_missing_content_type Apr 26 04:40:53 192.168.122.209 [45403.976466] Start test: t_frang.test_http_ct_required.FrangHttpCtRequiredTestCase.test_content_type_set_ok Apr 26 04:40:54 192.168.122.209 [45405.145622] [tdb] Start Tempesta DB Apr 26 04:40:54 192.168.122.209 [45405.284677] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:40:55 192.168.122.209 [45406.137797] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45406.137797] Maybe that's fine, but it's worth checking the [45406.137797] config - if there is no relations between the [45406.137797] names, then host name confusion attack is possible. Apr 26 04:40:55 192.168.122.209 [45406.240566] [tempesta fw] Configuration processing is completed. Apr 26 04:40:55 192.168.122.209 [45406.291424] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:40:55 192.168.122.209 [45406.320713] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:40:55 192.168.122.209 [45406.347178] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:40:56 192.168.122.209 [45406.392548] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:40:56 192.168.122.209 [45406.394229] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:40:56 192.168.122.209 [45406.395877] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:40:56 192.168.122.209 [45406.428511] [tempesta fw] Tempesta FW is ready Apr 26 04:40:56 192.168.122.209 [45407.087290] [tdb] Close table 'client0.tdb' Apr 26 04:40:56 192.168.122.209 [45407.294657] [tdb] Close table 'sessions0.tdb' Apr 26 04:40:57 192.168.122.209 [45407.544292] [tdb] Close table 'filter0.tdb' Apr 26 04:40:57 192.168.122.209 [45407.544791] [tempesta fw] modules are stopped Apr 26 04:40:57 192.168.122.209 [45407.722487] [tempesta fw] exiting... Apr 26 04:40:57 192.168.122.209 [45407.848890] [tdb] Shutdown Tempesta DB Apr 26 04:40:57 192.168.122.209 [45408.070138] End test: t_frang.test_http_ct_required.FrangHttpCtRequiredTestCase.test_content_type_set_ok Apr 26 04:40:57 192.168.122.209 [45408.082741] Start test: t_frang.test_http_ct_required.FrangHttpCtRequiredTestCase.test_default_http_ct_required Apr 26 04:40:59 192.168.122.209 [45409.463325] [tdb] Start Tempesta DB Apr 26 04:40:59 192.168.122.209 [45409.627615] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:41:00 192.168.122.209 [45410.445841] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45410.445841] Maybe that's fine, but it's worth checking the [45410.445841] config - if there is no relations between the [45410.445841] names, then host name confusion attack is possible. Apr 26 04:41:00 192.168.122.209 [45410.552556] [tempesta fw] Configuration processing is completed. Apr 26 04:41:00 192.168.122.209 [45410.603788] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:41:00 192.168.122.209 [45410.632571] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:41:00 192.168.122.209 [45410.659483] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:41:00 192.168.122.209 [45410.700584] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:41:00 192.168.122.209 [45410.702263] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:41:00 192.168.122.209 [45410.704052] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:41:00 192.168.122.209 [45410.740539] [tempesta fw] Tempesta FW is ready Apr 26 04:41:00 192.168.122.209 [45411.359242] [tdb] Close table 'client0.tdb' Apr 26 04:41:01 192.168.122.209 [45411.550084] [tdb] Close table 'sessions0.tdb' Apr 26 04:41:01 192.168.122.209 [45411.805267] [tdb] Close table 'filter0.tdb' Apr 26 04:41:01 192.168.122.209 [45411.805993] [tempesta fw] modules are stopped Apr 26 04:41:01 192.168.122.209 [45411.974178] [tempesta fw] exiting... Apr 26 04:41:01 192.168.122.209 [45412.106013] [tdb] Shutdown Tempesta DB Apr 26 04:41:01 192.168.122.209 [45412.320717] End test: t_frang.test_http_ct_required.FrangHttpCtRequiredTestCase.test_default_http_ct_required Apr 26 04:41:01 192.168.122.209 [45412.336828] Start test: t_frang.test_http_ct_required.FrangHttpCtRequiredTestCase.test_missing_content_type Apr 26 04:41:03 192.168.122.209 [45413.547679] [tdb] Start Tempesta DB Apr 26 04:41:03 192.168.122.209 [45413.675474] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:41:04 192.168.122.209 [45414.413870] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45414.413870] Maybe that's fine, but it's worth checking the [45414.413870] config - if there is no relations between the [45414.413870] names, then host name confusion attack is possible. Apr 26 04:41:04 192.168.122.209 [45414.520657] [tempesta fw] Configuration processing is completed. Apr 26 04:41:04 192.168.122.209 [45414.566205] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:41:04 192.168.122.209 [45414.593947] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:41:04 192.168.122.209 [45414.620669] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:41:04 192.168.122.209 [45414.680636] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:41:04 192.168.122.209 [45414.682301] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:41:04 192.168.122.209 [45414.683944] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:41:04 192.168.122.209 [45414.720627] [tempesta fw] Tempesta FW is ready Apr 26 04:41:04 192.168.122.209 [45414.849685] [tempesta fw] Warning: frang: Content-Type header field for 127.0.0.2 is missed Apr 26 04:41:04 192.168.122.209 [45414.851014] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:41:04 192.168.122.209 [45415.354407] [tdb] Close table 'client0.tdb' Apr 26 04:41:05 192.168.122.209 [45415.535573] [tdb] Close table 'sessions0.tdb' Apr 26 04:41:05 192.168.122.209 [45415.767339] [tdb] Close table 'filter0.tdb' Apr 26 04:41:05 192.168.122.209 [45415.767770] [tempesta fw] modules are stopped Apr 26 04:41:05 192.168.122.209 [45415.975926] [tempesta fw] exiting... Apr 26 04:41:05 192.168.122.209 [45416.105704] [tdb] Shutdown Tempesta DB Apr 26 04:41:05 192.168.122.209 [45416.287046] End test: t_frang.test_http_ct_required.FrangHttpCtRequiredTestCase.test_missing_content_type Apr 26 04:41:05 192.168.122.209 [45416.296538] Start test: t_frang.test_http_ct_vals.FrangHttpCtValsH2.test_content_vals_set_ok Apr 26 04:41:07 192.168.122.209 [45417.477274] [tdb] Start Tempesta DB Apr 26 04:41:07 192.168.122.209 [45417.614156] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:41:08 192.168.122.209 [45418.401944] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45418.401944] Maybe that's fine, but it's worth checking the [45418.401944] config - if there is no relations between the [45418.401944] names, then host name confusion attack is possible. Apr 26 04:41:08 192.168.122.209 [45418.500727] [tempesta fw] Configuration processing is completed. Apr 26 04:41:08 192.168.122.209 [45418.561019] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:41:08 192.168.122.209 [45418.590644] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:41:08 192.168.122.209 [45418.617122] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:41:08 192.168.122.209 [45418.672683] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:41:08 192.168.122.209 [45418.674379] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:41:08 192.168.122.209 [45418.676026] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:41:08 192.168.122.209 [45418.712650] [tempesta fw] Tempesta FW is ready Apr 26 04:41:09 192.168.122.209 [45419.389024] [tdb] Close table 'client0.tdb' Apr 26 04:41:09 192.168.122.209 [45419.583120] [tdb] Close table 'sessions0.tdb' Apr 26 04:41:09 192.168.122.209 [45419.811651] [tdb] Close table 'filter0.tdb' Apr 26 04:41:09 192.168.122.209 [45419.812095] [tempesta fw] modules are stopped Apr 26 04:41:09 192.168.122.209 [45420.053057] [tempesta fw] exiting... Apr 26 04:41:09 192.168.122.209 [45420.181941] [tdb] Shutdown Tempesta DB Apr 26 04:41:10 192.168.122.209 [45420.388448] End test: t_frang.test_http_ct_vals.FrangHttpCtValsH2.test_content_vals_set_ok Apr 26 04:41:10 192.168.122.209 [45420.399513] Start test: t_frang.test_http_ct_vals.FrangHttpCtValsH2.test_content_vals_set_ok_conf2 Apr 26 04:41:11 192.168.122.209 [45421.620338] [tdb] Start Tempesta DB Apr 26 04:41:11 192.168.122.209 [45421.763518] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:41:12 192.168.122.209 [45422.549993] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45422.549993] Maybe that's fine, but it's worth checking the [45422.549993] config - if there is no relations between the [45422.549993] names, then host name confusion attack is possible. Apr 26 04:41:12 192.168.122.209 [45422.669176] [tempesta fw] Configuration processing is completed. Apr 26 04:41:12 192.168.122.209 [45422.719829] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:41:12 192.168.122.209 [45422.747231] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:41:12 192.168.122.209 [45422.774061] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:41:12 192.168.122.209 [45422.824775] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:41:12 192.168.122.209 [45422.826461] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:41:12 192.168.122.209 [45422.828101] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:41:12 192.168.122.209 [45422.864680] [tempesta fw] Tempesta FW is ready Apr 26 04:41:13 192.168.122.209 [45423.561941] [tdb] Close table 'client0.tdb' Apr 26 04:41:13 192.168.122.209 [45423.753246] [tdb] Close table 'sessions0.tdb' Apr 26 04:41:13 192.168.122.209 [45423.991150] [tdb] Close table 'filter0.tdb' Apr 26 04:41:13 192.168.122.209 [45423.991594] [tempesta fw] modules are stopped Apr 26 04:41:13 192.168.122.209 [45424.156830] [tempesta fw] exiting... Apr 26 04:41:13 192.168.122.209 [45424.282943] [tdb] Shutdown Tempesta DB Apr 26 04:41:14 192.168.122.209 [45424.500478] End test: t_frang.test_http_ct_vals.FrangHttpCtValsH2.test_content_vals_set_ok_conf2 Apr 26 04:41:14 192.168.122.209 [45424.512486] Start test: t_frang.test_http_ct_vals.FrangHttpCtValsH2.test_default_http_ct_vals Apr 26 04:41:15 192.168.122.209 [45425.700653] [tdb] Start Tempesta DB Apr 26 04:41:15 192.168.122.209 [45425.857844] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:41:16 192.168.122.209 [45426.634027] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45426.634027] Maybe that's fine, but it's worth checking the [45426.634027] config - if there is no relations between the [45426.634027] names, then host name confusion attack is possible. Apr 26 04:41:16 192.168.122.209 [45426.744816] [tempesta fw] Configuration processing is completed. Apr 26 04:41:16 192.168.122.209 [45426.797627] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:41:16 192.168.122.209 [45426.828494] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:41:16 192.168.122.209 [45426.856406] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:41:16 192.168.122.209 [45426.924848] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:41:16 192.168.122.209 [45426.926543] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:41:16 192.168.122.209 [45426.928271] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:41:16 192.168.122.209 [45426.968753] [tempesta fw] Tempesta FW is ready Apr 26 04:41:17 192.168.122.209 [45427.613089] [tdb] Close table 'client0.tdb' Apr 26 04:41:17 192.168.122.209 [45427.806228] [tdb] Close table 'sessions0.tdb' Apr 26 04:41:17 192.168.122.209 [45428.067903] [tdb] Close table 'filter0.tdb' Apr 26 04:41:17 192.168.122.209 [45428.068333] [tempesta fw] modules are stopped Apr 26 04:41:17 192.168.122.209 [45428.250107] [tempesta fw] exiting... Apr 26 04:41:18 192.168.122.209 [45428.399174] [tdb] Shutdown Tempesta DB Apr 26 04:41:18 192.168.122.209 [45428.627508] End test: t_frang.test_http_ct_vals.FrangHttpCtValsH2.test_default_http_ct_vals Apr 26 04:41:18 192.168.122.209 [45428.639030] Start test: t_frang.test_http_ct_vals.FrangHttpCtValsH2.test_error_content_type Apr 26 04:41:19 192.168.122.209 [45429.863056] [tdb] Start Tempesta DB Apr 26 04:41:19 192.168.122.209 [45430.007721] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:41:20 192.168.122.209 [45430.718097] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45430.718097] Maybe that's fine, but it's worth checking the [45430.718097] config - if there is no relations between the [45430.718097] names, then host name confusion attack is possible. Apr 26 04:41:20 192.168.122.209 [45430.832854] [tempesta fw] Configuration processing is completed. Apr 26 04:41:20 192.168.122.209 [45430.896401] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:41:20 192.168.122.209 [45430.925615] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:41:20 192.168.122.209 [45430.953953] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:41:20 192.168.122.209 [45431.000862] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:41:20 192.168.122.209 [45431.002529] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:41:20 192.168.122.209 [45431.004164] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:41:20 192.168.122.209 [45431.040788] [tempesta fw] Tempesta FW is ready Apr 26 04:41:20 192.168.122.209 [45431.172933] [tempesta fw] Warning: frang: restricted Content-Type for 127.0.0.2: text/ Apr 26 04:41:20 192.168.122.209 [45431.174873] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:41:21 192.168.122.209 [45431.689554] [tdb] Close table 'client0.tdb' Apr 26 04:41:21 192.168.122.209 [45431.877715] [tdb] Close table 'sessions0.tdb' Apr 26 04:41:21 192.168.122.209 [45432.099366] [tdb] Close table 'filter0.tdb' Apr 26 04:41:21 192.168.122.209 [45432.099799] [tempesta fw] modules are stopped Apr 26 04:41:21 192.168.122.209 [45432.264576] [tempesta fw] exiting... Apr 26 04:41:22 192.168.122.209 [45432.413358] [tdb] Shutdown Tempesta DB Apr 26 04:41:22 192.168.122.209 [45432.631787] End test: t_frang.test_http_ct_vals.FrangHttpCtValsH2.test_error_content_type Apr 26 04:41:22 192.168.122.209 [45432.646524] Start test: t_frang.test_http_ct_vals.FrangHttpCtValsH2.test_error_content_type2 Apr 26 04:41:23 192.168.122.209 [45433.873641] [tdb] Start Tempesta DB Apr 26 04:41:23 192.168.122.209 [45434.020778] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:41:24 192.168.122.209 [45434.762415] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45434.762415] Maybe that's fine, but it's worth checking the [45434.762415] config - if there is no relations between the [45434.762415] names, then host name confusion attack is possible. Apr 26 04:41:24 192.168.122.209 [45434.868940] [tempesta fw] Configuration processing is completed. Apr 26 04:41:24 192.168.122.209 [45434.919201] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:41:24 192.168.122.209 [45434.949485] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:41:24 192.168.122.209 [45434.978884] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:41:24 192.168.122.209 [45435.032897] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:41:24 192.168.122.209 [45435.034641] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:41:24 192.168.122.209 [45435.036359] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:41:24 192.168.122.209 [45435.092871] [tempesta fw] Tempesta FW is ready Apr 26 04:41:24 192.168.122.209 [45435.226583] [tempesta fw] Warning: frang: restricted Content-Type for 127.0.0.2: text/ Apr 26 04:41:24 192.168.122.209 [45435.228175] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:41:25 192.168.122.209 [45435.769650] [tdb] Close table 'client0.tdb' Apr 26 04:41:25 192.168.122.209 [45435.973825] [tdb] Close table 'sessions0.tdb' Apr 26 04:41:25 192.168.122.209 [45436.199463] [tdb] Close table 'filter0.tdb' Apr 26 04:41:25 192.168.122.209 [45436.199893] [tempesta fw] modules are stopped Apr 26 04:41:26 192.168.122.209 [45436.417366] [tempesta fw] exiting... Apr 26 04:41:26 192.168.122.209 [45436.544531] [tdb] Shutdown Tempesta DB Apr 26 04:41:26 192.168.122.209 [45436.732616] End test: t_frang.test_http_ct_vals.FrangHttpCtValsH2.test_error_content_type2 Apr 26 04:41:26 192.168.122.209 [45436.747807] Start test: t_frang.test_http_ct_vals.FrangHttpCtValsH2.test_missing_content_type Apr 26 04:41:27 192.168.122.209 [45437.914672] [tdb] Start Tempesta DB Apr 26 04:41:27 192.168.122.209 [45438.044409] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:41:28 192.168.122.209 [45438.818191] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45438.818191] Maybe that's fine, but it's worth checking the [45438.818191] config - if there is no relations between the [45438.818191] names, then host name confusion attack is possible. Apr 26 04:41:28 192.168.122.209 [45438.917015] [tempesta fw] Configuration processing is completed. Apr 26 04:41:28 192.168.122.209 [45438.969050] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:41:28 192.168.122.209 [45438.999708] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:41:28 192.168.122.209 [45439.026457] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:41:28 192.168.122.209 [45439.068892] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:41:28 192.168.122.209 [45439.070555] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:41:28 192.168.122.209 [45439.072218] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:41:28 192.168.122.209 [45439.112893] [tempesta fw] Tempesta FW is ready Apr 26 04:41:28 192.168.122.209 [45439.247304] [tempesta fw] Warning: frang: Content-Type header field for 127.0.0.2 is missed Apr 26 04:41:28 192.168.122.209 [45439.248334] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:41:29 192.168.122.209 [45439.785959] [tdb] Close table 'client0.tdb' Apr 26 04:41:29 192.168.122.209 [45439.974764] [tdb] Close table 'sessions0.tdb' Apr 26 04:41:29 192.168.122.209 [45440.225268] [tdb] Close table 'filter0.tdb' Apr 26 04:41:29 192.168.122.209 [45440.225687] [tempesta fw] modules are stopped Apr 26 04:41:30 192.168.122.209 [45440.446261] [tempesta fw] exiting... Apr 26 04:41:30 192.168.122.209 [45440.605794] [tdb] Shutdown Tempesta DB Apr 26 04:41:30 192.168.122.209 [45440.813387] End test: t_frang.test_http_ct_vals.FrangHttpCtValsH2.test_missing_content_type Apr 26 04:41:30 192.168.122.209 [45440.824692] Start test: t_frang.test_http_ct_vals.FrangHttpCtValsTestCase.test_content_vals_set_ok Apr 26 04:41:31 192.168.122.209 [45442.034483] [tdb] Start Tempesta DB Apr 26 04:41:31 192.168.122.209 [45442.173133] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:41:32 192.168.122.209 [45442.942235] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45442.942235] Maybe that's fine, but it's worth checking the [45442.942235] config - if there is no relations between the [45442.942235] names, then host name confusion attack is possible. Apr 26 04:41:32 192.168.122.209 [45443.045016] [tempesta fw] Configuration processing is completed. Apr 26 04:41:32 192.168.122.209 [45443.098888] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:41:32 192.168.122.209 [45443.126327] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:41:32 192.168.122.209 [45443.153026] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:41:32 192.168.122.209 [45443.192996] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:41:32 192.168.122.209 [45443.194661] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:41:32 192.168.122.209 [45443.196384] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:41:32 192.168.122.209 [45443.236967] [tempesta fw] Tempesta FW is ready Apr 26 04:41:33 192.168.122.209 [45443.943306] [tdb] Close table 'client0.tdb' Apr 26 04:41:33 192.168.122.209 [45444.138742] [tdb] Close table 'sessions0.tdb' Apr 26 04:41:34 192.168.122.209 [45444.383724] [tdb] Close table 'filter0.tdb' Apr 26 04:41:34 192.168.122.209 [45444.384164] [tempesta fw] modules are stopped Apr 26 04:41:34 192.168.122.209 [45444.591836] [tempesta fw] exiting... Apr 26 04:41:34 192.168.122.209 [45444.720537] [tdb] Shutdown Tempesta DB Apr 26 04:41:34 192.168.122.209 [45444.926431] End test: t_frang.test_http_ct_vals.FrangHttpCtValsTestCase.test_content_vals_set_ok Apr 26 04:41:34 192.168.122.209 [45444.946197] Start test: t_frang.test_http_ct_vals.FrangHttpCtValsTestCase.test_content_vals_set_ok_conf2 Apr 26 04:41:35 192.168.122.209 [45446.209526] [tdb] Start Tempesta DB Apr 26 04:41:35 192.168.122.209 [45446.341093] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:41:36 192.168.122.209 [45447.174392] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45447.174392] Maybe that's fine, but it's worth checking the [45447.174392] config - if there is no relations between the [45447.174392] names, then host name confusion attack is possible. Apr 26 04:41:36 192.168.122.209 [45447.277076] [tempesta fw] Configuration processing is completed. Apr 26 04:41:36 192.168.122.209 [45447.328733] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:41:36 192.168.122.209 [45447.358975] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:41:37 192.168.122.209 [45447.387127] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:41:37 192.168.122.209 [45447.429062] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:41:37 192.168.122.209 [45447.430782] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:41:37 192.168.122.209 [45447.432435] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:41:37 192.168.122.209 [45447.477011] [tempesta fw] Tempesta FW is ready Apr 26 04:41:37 192.168.122.209 [45448.153275] [tdb] Close table 'client0.tdb' Apr 26 04:41:37 192.168.122.209 [45448.343139] [tdb] Close table 'sessions0.tdb' Apr 26 04:41:38 192.168.122.209 [45448.554059] [tdb] Close table 'filter0.tdb' Apr 26 04:41:38 192.168.122.209 [45448.554499] [tempesta fw] modules are stopped Apr 26 04:41:38 192.168.122.209 [45448.753956] [tempesta fw] exiting... Apr 26 04:41:38 192.168.122.209 [45448.880561] [tdb] Shutdown Tempesta DB Apr 26 04:41:38 192.168.122.209 [45449.090617] End test: t_frang.test_http_ct_vals.FrangHttpCtValsTestCase.test_content_vals_set_ok_conf2 Apr 26 04:41:38 192.168.122.209 [45449.097606] Start test: t_frang.test_http_ct_vals.FrangHttpCtValsTestCase.test_default_http_ct_vals Apr 26 04:41:39 192.168.122.209 [45450.253374] [tdb] Start Tempesta DB Apr 26 04:41:40 192.168.122.209 [45450.384796] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:41:40 192.168.122.209 [45451.110355] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45451.110355] Maybe that's fine, but it's worth checking the [45451.110355] config - if there is no relations between the [45451.110355] names, then host name confusion attack is possible. Apr 26 04:41:40 192.168.122.209 [45451.213113] [tempesta fw] Configuration processing is completed. Apr 26 04:41:40 192.168.122.209 [45451.269367] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:41:40 192.168.122.209 [45451.298783] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:41:40 192.168.122.209 [45451.327103] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:41:41 192.168.122.209 [45451.405110] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:41:41 192.168.122.209 [45451.406826] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:41:41 192.168.122.209 [45451.408489] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:41:41 192.168.122.209 [45451.445056] [tempesta fw] Tempesta FW is ready Apr 26 04:41:41 192.168.122.209 [45452.057522] [tdb] Close table 'client0.tdb' Apr 26 04:41:41 192.168.122.209 [45452.257713] [tdb] Close table 'sessions0.tdb' Apr 26 04:41:42 192.168.122.209 [45452.485685] [tdb] Close table 'filter0.tdb' Apr 26 04:41:42 192.168.122.209 [45452.486119] [tempesta fw] modules are stopped Apr 26 04:41:42 192.168.122.209 [45452.689975] [tempesta fw] exiting... Apr 26 04:41:42 192.168.122.209 [45452.830787] [tdb] Shutdown Tempesta DB Apr 26 04:41:42 192.168.122.209 [45453.030301] End test: t_frang.test_http_ct_vals.FrangHttpCtValsTestCase.test_default_http_ct_vals Apr 26 04:41:42 192.168.122.209 [45453.050260] Start test: t_frang.test_http_ct_vals.FrangHttpCtValsTestCase.test_error_content_type Apr 26 04:41:43 192.168.122.209 [45454.275987] [tdb] Start Tempesta DB Apr 26 04:41:44 192.168.122.209 [45454.405918] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:41:44 192.168.122.209 [45455.210396] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45455.210396] Maybe that's fine, but it's worth checking the [45455.210396] config - if there is no relations between the [45455.210396] names, then host name confusion attack is possible. Apr 26 04:41:44 192.168.122.209 [45455.317163] [tempesta fw] Configuration processing is completed. Apr 26 04:41:45 192.168.122.209 [45455.380219] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:41:45 192.168.122.209 [45455.410768] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:41:45 192.168.122.209 [45455.439664] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:41:45 192.168.122.209 [45455.497209] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:41:45 192.168.122.209 [45455.498903] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:41:45 192.168.122.209 [45455.500584] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:41:45 192.168.122.209 [45455.549109] [tempesta fw] Tempesta FW is ready Apr 26 04:41:45 192.168.122.209 [45455.683859] [tempesta fw] Warning: frang: restricted Content-Type for 127.0.0.2: text Apr 26 04:41:45 192.168.122.209 [45455.685135] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:41:45 192.168.122.209 [45456.228080] [tdb] Close table 'client0.tdb' Apr 26 04:41:46 192.168.122.209 [45456.425243] [tdb] Close table 'sessions0.tdb' Apr 26 04:41:46 192.168.122.209 [45456.668387] [tdb] Close table 'filter0.tdb' Apr 26 04:41:46 192.168.122.209 [45456.668846] [tempesta fw] modules are stopped Apr 26 04:41:46 192.168.122.209 [45456.926126] [tempesta fw] exiting... Apr 26 04:41:46 192.168.122.209 [45457.079853] [tdb] Shutdown Tempesta DB Apr 26 04:41:46 192.168.122.209 [45457.311970] End test: t_frang.test_http_ct_vals.FrangHttpCtValsTestCase.test_error_content_type Apr 26 04:41:46 192.168.122.209 [45457.323501] Start test: t_frang.test_http_ct_vals.FrangHttpCtValsTestCase.test_error_content_type2 Apr 26 04:41:48 192.168.122.209 [45458.510947] [tdb] Start Tempesta DB Apr 26 04:41:48 192.168.122.209 [45458.661268] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:41:49 192.168.122.209 [45459.482505] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45459.482505] Maybe that's fine, but it's worth checking the [45459.482505] config - if there is no relations between the [45459.482505] names, then host name confusion attack is possible. Apr 26 04:41:49 192.168.122.209 [45459.597251] [tempesta fw] Configuration processing is completed. Apr 26 04:41:49 192.168.122.209 [45459.648599] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:41:49 192.168.122.209 [45459.678955] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:41:49 192.168.122.209 [45459.708547] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:41:49 192.168.122.209 [45459.749190] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:41:49 192.168.122.209 [45459.750839] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:41:49 192.168.122.209 [45459.752522] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:41:49 192.168.122.209 [45459.809149] [tempesta fw] Tempesta FW is ready Apr 26 04:41:49 192.168.122.209 [45459.948205] [tempesta fw] Warning: frang: restricted Content-Type for 127.0.0.2: text Apr 26 04:41:49 192.168.122.209 [45459.949205] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:41:50 192.168.122.209 [45460.462237] [tdb] Close table 'client0.tdb' Apr 26 04:41:50 192.168.122.209 [45460.654380] [tdb] Close table 'sessions0.tdb' Apr 26 04:41:50 192.168.122.209 [45460.896833] [tdb] Close table 'filter0.tdb' Apr 26 04:41:50 192.168.122.209 [45460.897636] [tempesta fw] modules are stopped Apr 26 04:41:50 192.168.122.209 [45461.077226] [tempesta fw] exiting... Apr 26 04:41:50 192.168.122.209 [45461.217491] [tdb] Shutdown Tempesta DB Apr 26 04:41:51 192.168.122.209 [45461.390212] End test: t_frang.test_http_ct_vals.FrangHttpCtValsTestCase.test_error_content_type2 Apr 26 04:41:51 192.168.122.209 [45461.404774] Start test: t_frang.test_http_ct_vals.FrangHttpCtValsTestCase.test_missing_content_type Apr 26 04:41:52 192.168.122.209 [45462.650544] [tdb] Start Tempesta DB Apr 26 04:41:52 192.168.122.209 [45462.806373] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:41:53 192.168.122.209 [45463.582538] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45463.582538] Maybe that's fine, but it's worth checking the [45463.582538] config - if there is no relations between the [45463.582538] names, then host name confusion attack is possible. Apr 26 04:41:53 192.168.122.209 [45463.681294] [tempesta fw] Configuration processing is completed. Apr 26 04:41:53 192.168.122.209 [45463.732667] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:41:53 192.168.122.209 [45463.761589] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:41:53 192.168.122.209 [45463.788469] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:41:53 192.168.122.209 [45463.829263] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:41:53 192.168.122.209 [45463.830950] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:41:53 192.168.122.209 [45463.832612] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:41:53 192.168.122.209 [45463.873220] [tempesta fw] Tempesta FW is ready Apr 26 04:41:53 192.168.122.209 [45464.003372] [tempesta fw] Warning: frang: Content-Type header field for 127.0.0.2 is missed Apr 26 04:41:53 192.168.122.209 [45464.004650] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:41:54 192.168.122.209 [45464.535900] [tdb] Close table 'client0.tdb' Apr 26 04:41:54 192.168.122.209 [45464.729510] [tdb] Close table 'sessions0.tdb' Apr 26 04:41:54 192.168.122.209 [45464.948984] [tdb] Close table 'filter0.tdb' Apr 26 04:41:54 192.168.122.209 [45464.949426] [tempesta fw] modules are stopped Apr 26 04:41:54 192.168.122.209 [45465.159528] [tempesta fw] exiting... Apr 26 04:41:54 192.168.122.209 [45465.291374] [tdb] Shutdown Tempesta DB Apr 26 04:41:55 192.168.122.209 [45465.487393] End test: t_frang.test_http_ct_vals.FrangHttpCtValsTestCase.test_missing_content_type Apr 26 04:41:55 192.168.122.209 [45465.502687] Start test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideH2.test_accepted_request Apr 26 04:41:56 192.168.122.209 [45466.776970] [tdb] Start Tempesta DB Apr 26 04:41:56 192.168.122.209 [45466.918473] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:41:57 192.168.122.209 [45467.758681] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45467.758681] Maybe that's fine, but it's worth checking the [45467.758681] config - if there is no relations between the [45467.758681] names, then host name confusion attack is possible. Apr 26 04:41:57 192.168.122.209 [45467.857340] [tempesta fw] Configuration processing is completed. Apr 26 04:41:57 192.168.122.209 [45467.913927] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:41:57 192.168.122.209 [45467.945159] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:41:57 192.168.122.209 [45467.977171] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:41:57 192.168.122.209 [45468.021306] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:41:57 192.168.122.209 [45468.023015] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:41:57 192.168.122.209 [45468.024675] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:41:57 192.168.122.209 [45468.061252] [tempesta fw] Tempesta FW is ready Apr 26 04:41:58 192.168.122.209 [45468.737753] [tdb] Close table 'client0.tdb' Apr 26 04:41:58 192.168.122.209 [45468.949266] [tdb] Close table 'sessions0.tdb' Apr 26 04:41:58 192.168.122.209 [45469.190072] [tdb] Close table 'filter0.tdb' Apr 26 04:41:58 192.168.122.209 [45469.190576] [tempesta fw] modules are stopped Apr 26 04:41:58 192.168.122.209 [45469.362284] [tempesta fw] exiting... Apr 26 04:41:59 192.168.122.209 [45469.484474] [tdb] Shutdown Tempesta DB Apr 26 04:41:59 192.168.122.209 [45469.694405] End test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideH2.test_accepted_request Apr 26 04:41:59 192.168.122.209 [45469.707129] Start test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideH2.test_default_http_method_override_allowed Apr 26 04:42:00 192.168.122.209 [45470.933122] [tdb] Start Tempesta DB Apr 26 04:42:00 192.168.122.209 [45471.059950] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:42:01 192.168.122.209 [45471.890700] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45471.890700] Maybe that's fine, but it's worth checking the [45471.890700] config - if there is no relations between the [45471.890700] names, then host name confusion attack is possible. Apr 26 04:42:01 192.168.122.209 [45472.001390] [tempesta fw] Configuration processing is completed. Apr 26 04:42:01 192.168.122.209 [45472.051146] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:42:01 192.168.122.209 [45472.078603] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:42:01 192.168.122.209 [45472.105399] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:42:01 192.168.122.209 [45472.161360] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:42:01 192.168.122.209 [45472.163062] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:42:01 192.168.122.209 [45472.164693] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:42:01 192.168.122.209 [45472.201316] [tempesta fw] Tempesta FW is ready Apr 26 04:42:01 192.168.122.209 [45472.323773] [tempesta fw] Warning: frang: restricted overridden HTTP method for 127.0.0.2: 13 (0x2000u) Apr 26 04:42:01 192.168.122.209 [45472.325990] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:42:02 192.168.122.209 [45472.784709] [tdb] Close table 'client0.tdb' Apr 26 04:42:02 192.168.122.209 [45472.966283] [tdb] Close table 'sessions0.tdb' Apr 26 04:42:02 192.168.122.209 [45473.184876] [tdb] Close table 'filter0.tdb' Apr 26 04:42:02 192.168.122.209 [45473.185339] [tempesta fw] modules are stopped Apr 26 04:42:03 192.168.122.209 [45473.393998] [tempesta fw] exiting... Apr 26 04:42:03 192.168.122.209 [45473.528375] [tdb] Shutdown Tempesta DB Apr 26 04:42:03 192.168.122.209 [45473.761914] End test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideH2.test_default_http_method_override_allowed Apr 26 04:42:03 192.168.122.209 [45473.771777] Start test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideH2.test_not_accepted_request_x_http_method Apr 26 04:42:04 192.168.122.209 [45474.988500] [tdb] Start Tempesta DB Apr 26 04:42:04 192.168.122.209 [45475.118370] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:42:05 192.168.122.209 [45475.918713] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45475.918713] Maybe that's fine, but it's worth checking the [45475.918713] config - if there is no relations between the [45475.918713] names, then host name confusion attack is possible. Apr 26 04:42:05 192.168.122.209 [45476.025456] [tempesta fw] Configuration processing is completed. Apr 26 04:42:05 192.168.122.209 [45476.076776] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:42:05 192.168.122.209 [45476.104160] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:42:05 192.168.122.209 [45476.130493] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:42:05 192.168.122.209 [45476.185410] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:42:05 192.168.122.209 [45476.187083] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:42:05 192.168.122.209 [45476.188723] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:42:05 192.168.122.209 [45476.237371] [tempesta fw] Tempesta FW is ready Apr 26 04:42:05 192.168.122.209 [45476.366014] [tempesta fw] Warning: frang: restricted overridden HTTP method for 127.0.0.2: 8 (0x100u) Apr 26 04:42:05 192.168.122.209 [45476.367150] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:42:06 192.168.122.209 [45476.879257] [tdb] Close table 'client0.tdb' Apr 26 04:42:06 192.168.122.209 [45477.065813] [tdb] Close table 'sessions0.tdb' Apr 26 04:42:06 192.168.122.209 [45477.292658] [tdb] Close table 'filter0.tdb' Apr 26 04:42:06 192.168.122.209 [45477.293084] [tempesta fw] modules are stopped Apr 26 04:42:07 192.168.122.209 [45477.506864] [tempesta fw] exiting... Apr 26 04:42:07 192.168.122.209 [45477.635321] [tdb] Shutdown Tempesta DB Apr 26 04:42:07 192.168.122.209 [45477.813698] End test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideH2.test_not_accepted_request_x_http_method Apr 26 04:42:07 192.168.122.209 [45477.820305] Start test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideH2.test_not_accepted_request_x_http_method_override Apr 26 04:42:08 192.168.122.209 [45479.044378] [tdb] Start Tempesta DB Apr 26 04:42:08 192.168.122.209 [45479.194783] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:42:09 192.168.122.209 [45479.986715] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45479.986715] Maybe that's fine, but it's worth checking the [45479.986715] config - if there is no relations between the [45479.986715] names, then host name confusion attack is possible. Apr 26 04:42:09 192.168.122.209 [45480.093478] [tempesta fw] Configuration processing is completed. Apr 26 04:42:09 192.168.122.209 [45480.142770] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:42:09 192.168.122.209 [45480.173910] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:42:09 192.168.122.209 [45480.200763] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:42:09 192.168.122.209 [45480.253496] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:42:09 192.168.122.209 [45480.255180] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:42:09 192.168.122.209 [45480.256831] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:42:09 192.168.122.209 [45480.297438] [tempesta fw] Tempesta FW is ready Apr 26 04:42:10 192.168.122.209 [45480.436097] [tempesta fw] Warning: frang: restricted overridden HTTP method for 127.0.0.2: 8 (0x100u) Apr 26 04:42:10 192.168.122.209 [45480.437281] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:42:10 192.168.122.209 [45480.950774] [tdb] Close table 'client0.tdb' Apr 26 04:42:10 192.168.122.209 [45481.145948] [tdb] Close table 'sessions0.tdb' Apr 26 04:42:10 192.168.122.209 [45481.377295] [tdb] Close table 'filter0.tdb' Apr 26 04:42:10 192.168.122.209 [45481.377883] [tempesta fw] modules are stopped Apr 26 04:42:11 192.168.122.209 [45481.585707] [tempesta fw] exiting... Apr 26 04:42:11 192.168.122.209 [45481.726247] [tdb] Shutdown Tempesta DB Apr 26 04:42:11 192.168.122.209 [45481.918434] End test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideH2.test_not_accepted_request_x_http_method_override Apr 26 04:42:11 192.168.122.209 [45481.938817] Start test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideH2.test_not_accepted_request_x_method_override Apr 26 04:42:12 192.168.122.209 [45483.111271] [tdb] Start Tempesta DB Apr 26 04:42:12 192.168.122.209 [45483.240780] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:42:13 192.168.122.209 [45484.046752] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45484.046752] Maybe that's fine, but it's worth checking the [45484.046752] config - if there is no relations between the [45484.046752] names, then host name confusion attack is possible. Apr 26 04:42:13 192.168.122.209 [45484.149530] [tempesta fw] Configuration processing is completed. Apr 26 04:42:13 192.168.122.209 [45484.200421] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:42:13 192.168.122.209 [45484.228017] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:42:13 192.168.122.209 [45484.254289] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:42:13 192.168.122.209 [45484.305507] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:42:13 192.168.122.209 [45484.307173] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:42:13 192.168.122.209 [45484.308810] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:42:13 192.168.122.209 [45484.353418] [tempesta fw] Tempesta FW is ready Apr 26 04:42:14 192.168.122.209 [45484.487647] [tempesta fw] Warning: frang: restricted overridden HTTP method for 127.0.0.2: 8 (0x100u) Apr 26 04:42:14 192.168.122.209 [45484.489177] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:42:14 192.168.122.209 [45485.033797] [tdb] Close table 'client0.tdb' Apr 26 04:42:14 192.168.122.209 [45485.221476] [tdb] Close table 'sessions0.tdb' Apr 26 04:42:15 192.168.122.209 [45485.469939] [tdb] Close table 'filter0.tdb' Apr 26 04:42:15 192.168.122.209 [45485.470391] [tempesta fw] modules are stopped Apr 26 04:42:15 192.168.122.209 [45485.678240] [tempesta fw] exiting... Apr 26 04:42:15 192.168.122.209 [45485.827127] [tdb] Shutdown Tempesta DB Apr 26 04:42:15 192.168.122.209 [45486.032892] End test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideH2.test_not_accepted_request_x_method_override Apr 26 04:42:15 192.168.122.209 [45486.044589] Start test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideH2.test_unsafe_override_x_http_method Apr 26 04:42:16 192.168.122.209 [45487.264983] [tdb] Start Tempesta DB Apr 26 04:42:17 192.168.122.209 [45487.401727] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:42:17 192.168.122.209 [45488.182798] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45488.182798] Maybe that's fine, but it's worth checking the [45488.182798] config - if there is no relations between the [45488.182798] names, then host name confusion attack is possible. Apr 26 04:42:17 192.168.122.209 [45488.293595] [tempesta fw] Configuration processing is completed. Apr 26 04:42:17 192.168.122.209 [45488.346398] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:42:17 192.168.122.209 [45488.376522] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:42:18 192.168.122.209 [45488.402902] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:42:18 192.168.122.209 [45488.453539] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:42:18 192.168.122.209 [45488.455205] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:42:18 192.168.122.209 [45488.456861] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:42:18 192.168.122.209 [45488.505549] [tempesta fw] Tempesta FW is ready Apr 26 04:42:18 192.168.122.209 [45488.642619] [tempesta fw] Warning: request dropped: unsafe method override: 127.0.0.2 Apr 26 04:42:18 192.168.122.209 [45489.186873] [tdb] Close table 'client0.tdb' Apr 26 04:42:18 192.168.122.209 [45489.354761] [tdb] Close table 'sessions0.tdb' Apr 26 04:42:19 192.168.122.209 [45489.590994] [tdb] Close table 'filter0.tdb' Apr 26 04:42:19 192.168.122.209 [45489.591424] [tempesta fw] modules are stopped Apr 26 04:42:19 192.168.122.209 [45489.802574] [tempesta fw] exiting... Apr 26 04:42:19 192.168.122.209 [45489.944957] [tdb] Shutdown Tempesta DB Apr 26 04:42:19 192.168.122.209 [45490.155215] End test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideH2.test_unsafe_override_x_http_method Apr 26 04:42:19 192.168.122.209 [45490.173860] Start test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideH2.test_unsafe_override_x_http_method_override Apr 26 04:42:20 192.168.122.209 [45491.335794] [tdb] Start Tempesta DB Apr 26 04:42:21 192.168.122.209 [45491.476878] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:42:21 192.168.122.209 [45492.298858] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45492.298858] Maybe that's fine, but it's worth checking the [45492.298858] config - if there is no relations between the [45492.298858] names, then host name confusion attack is possible. Apr 26 04:42:22 192.168.122.209 [45492.405654] [tempesta fw] Configuration processing is completed. Apr 26 04:42:22 192.168.122.209 [45492.454862] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:42:22 192.168.122.209 [45492.482709] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:42:22 192.168.122.209 [45492.509537] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:42:22 192.168.122.209 [45492.557629] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:42:22 192.168.122.209 [45492.559291] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:42:22 192.168.122.209 [45492.560933] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:42:22 192.168.122.209 [45492.605587] [tempesta fw] Tempesta FW is ready Apr 26 04:42:22 192.168.122.209 [45492.729809] [tempesta fw] Warning: request dropped: unsafe method override: 127.0.0.2 Apr 26 04:42:22 192.168.122.209 [45493.235372] [tdb] Close table 'client0.tdb' Apr 26 04:42:23 192.168.122.209 [45493.435315] [tdb] Close table 'sessions0.tdb' Apr 26 04:42:23 192.168.122.209 [45493.640539] [tdb] Close table 'filter0.tdb' Apr 26 04:42:23 192.168.122.209 [45493.640967] [tempesta fw] modules are stopped Apr 26 04:42:23 192.168.122.209 [45493.837680] [tempesta fw] exiting... Apr 26 04:42:23 192.168.122.209 [45493.959057] [tdb] Shutdown Tempesta DB Apr 26 04:42:23 192.168.122.209 [45494.131278] End test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideH2.test_unsafe_override_x_http_method_override Apr 26 04:42:23 192.168.122.209 [45494.142693] Start test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideH2.test_unsafe_override_x_method_override Apr 26 04:42:24 192.168.122.209 [45495.304654] [tdb] Start Tempesta DB Apr 26 04:42:25 192.168.122.209 [45495.442751] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:42:25 192.168.122.209 [45496.234898] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45496.234898] Maybe that's fine, but it's worth checking the [45496.234898] config - if there is no relations between the [45496.234898] names, then host name confusion attack is possible. Apr 26 04:42:25 192.168.122.209 [45496.333705] [tempesta fw] Configuration processing is completed. Apr 26 04:42:26 192.168.122.209 [45496.383869] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:42:26 192.168.122.209 [45496.411304] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:42:26 192.168.122.209 [45496.437755] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:42:26 192.168.122.209 [45496.485683] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:42:26 192.168.122.209 [45496.487410] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:42:26 192.168.122.209 [45496.489047] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:42:26 192.168.122.209 [45496.525648] [tempesta fw] Tempesta FW is ready Apr 26 04:42:26 192.168.122.209 [45496.653085] [tempesta fw] Warning: request dropped: unsafe method override: 127.0.0.2 Apr 26 04:42:26 192.168.122.209 [45497.178995] [tdb] Close table 'client0.tdb' Apr 26 04:42:26 192.168.122.209 [45497.374158] [tdb] Close table 'sessions0.tdb' Apr 26 04:42:27 192.168.122.209 [45497.621595] [tdb] Close table 'filter0.tdb' Apr 26 04:42:27 192.168.122.209 [45497.622018] [tempesta fw] modules are stopped Apr 26 04:42:27 192.168.122.209 [45497.831210] [tempesta fw] exiting... Apr 26 04:42:27 192.168.122.209 [45497.958802] [tdb] Shutdown Tempesta DB Apr 26 04:42:27 192.168.122.209 [45498.189132] End test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideH2.test_unsafe_override_x_method_override Apr 26 04:42:27 192.168.122.209 [45498.211821] Start test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideTestCase.test_accepted_request Apr 26 04:42:29 192.168.122.209 [45499.391826] [tdb] Start Tempesta DB Apr 26 04:42:29 192.168.122.209 [45499.536458] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:42:29 192.168.122.209 [45500.370949] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45500.370949] Maybe that's fine, but it's worth checking the [45500.370949] config - if there is no relations between the [45500.370949] names, then host name confusion attack is possible. Apr 26 04:42:30 192.168.122.209 [45500.469737] [tempesta fw] Configuration processing is completed. Apr 26 04:42:30 192.168.122.209 [45500.520909] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:42:30 192.168.122.209 [45500.551124] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:42:30 192.168.122.209 [45500.577988] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:42:30 192.168.122.209 [45500.637716] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:42:30 192.168.122.209 [45500.639609] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:42:30 192.168.122.209 [45500.641239] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:42:30 192.168.122.209 [45500.689685] [tempesta fw] Tempesta FW is ready Apr 26 04:42:30 192.168.122.209 [45501.375698] [tdb] Close table 'client0.tdb' Apr 26 04:42:31 192.168.122.209 [45501.563078] [tdb] Close table 'sessions0.tdb' Apr 26 04:42:31 192.168.122.209 [45501.820474] [tdb] Close table 'filter0.tdb' Apr 26 04:42:31 192.168.122.209 [45501.820921] [tempesta fw] modules are stopped Apr 26 04:42:31 192.168.122.209 [45502.019144] [tempesta fw] exiting... Apr 26 04:42:31 192.168.122.209 [45502.140095] [tdb] Shutdown Tempesta DB Apr 26 04:42:31 192.168.122.209 [45502.355867] End test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideTestCase.test_accepted_request Apr 26 04:42:31 192.168.122.209 [45502.368768] Start test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideTestCase.test_default_http_method_override_allowed Apr 26 04:42:33 192.168.122.209 [45503.553604] [tdb] Start Tempesta DB Apr 26 04:42:33 192.168.122.209 [45503.684774] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:42:34 192.168.122.209 [45504.443025] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45504.443025] Maybe that's fine, but it's worth checking the [45504.443025] config - if there is no relations between the [45504.443025] names, then host name confusion attack is possible. Apr 26 04:42:34 192.168.122.209 [45504.557794] [tempesta fw] Configuration processing is completed. Apr 26 04:42:34 192.168.122.209 [45504.607627] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:42:34 192.168.122.209 [45504.634694] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:42:34 192.168.122.209 [45504.660937] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:42:34 192.168.122.209 [45504.717772] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:42:34 192.168.122.209 [45504.719445] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:42:34 192.168.122.209 [45504.721121] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:42:34 192.168.122.209 [45504.757719] [tempesta fw] Tempesta FW is ready Apr 26 04:42:34 192.168.122.209 [45504.882069] [tempesta fw] Warning: frang: restricted overridden HTTP method for 127.0.0.2: 13 (0x2000u) Apr 26 04:42:34 192.168.122.209 [45504.884655] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:42:35 192.168.122.209 [45505.410540] [tdb] Close table 'client0.tdb' Apr 26 04:42:35 192.168.122.209 [45505.592009] [tdb] Close table 'sessions0.tdb' Apr 26 04:42:35 192.168.122.209 [45505.805703] [tdb] Close table 'filter0.tdb' Apr 26 04:42:35 192.168.122.209 [45505.806128] [tempesta fw] modules are stopped Apr 26 04:42:35 192.168.122.209 [45506.061696] [tempesta fw] exiting... Apr 26 04:42:35 192.168.122.209 [45506.201405] [tdb] Shutdown Tempesta DB Apr 26 04:42:36 192.168.122.209 [45506.414300] End test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideTestCase.test_default_http_method_override_allowed Apr 26 04:42:36 192.168.122.209 [45506.424011] Start test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideTestCase.test_not_accepted_request_x_http_method Apr 26 04:42:37 192.168.122.209 [45507.693272] [tdb] Start Tempesta DB Apr 26 04:42:37 192.168.122.209 [45507.838493] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:42:38 192.168.122.209 [45508.593416] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45508.593416] Maybe that's fine, but it's worth checking the [45508.593416] config - if there is no relations between the [45508.593416] names, then host name confusion attack is possible. Apr 26 04:42:38 192.168.122.209 [45508.717864] [tempesta fw] Configuration processing is completed. Apr 26 04:42:38 192.168.122.209 [45508.769177] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:42:38 192.168.122.209 [45508.798943] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:42:38 192.168.122.209 [45508.825920] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:42:38 192.168.122.209 [45508.873839] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:42:38 192.168.122.209 [45508.875506] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:42:38 192.168.122.209 [45508.877180] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:42:38 192.168.122.209 [45508.917789] [tempesta fw] Tempesta FW is ready Apr 26 04:42:38 192.168.122.209 [45509.031416] [tempesta fw] Warning: frang: restricted overridden HTTP method for 127.0.0.2: 8 (0x100u) Apr 26 04:42:38 192.168.122.209 [45509.033037] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:42:39 192.168.122.209 [45509.530623] [tdb] Close table 'client0.tdb' Apr 26 04:42:39 192.168.122.209 [45509.748704] [tdb] Close table 'sessions0.tdb' Apr 26 04:42:39 192.168.122.209 [45509.980849] [tdb] Close table 'filter0.tdb' Apr 26 04:42:39 192.168.122.209 [45509.981272] [tempesta fw] modules are stopped Apr 26 04:42:39 192.168.122.209 [45510.235598] [tempesta fw] exiting... Apr 26 04:42:39 192.168.122.209 [45510.366356] [tdb] Shutdown Tempesta DB Apr 26 04:42:40 192.168.122.209 [45510.576570] End test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideTestCase.test_not_accepted_request_x_http_method Apr 26 04:42:40 192.168.122.209 [45510.590928] Start test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideTestCase.test_not_accepted_request_x_http_method_override Apr 26 04:42:41 192.168.122.209 [45511.831183] [tdb] Start Tempesta DB Apr 26 04:42:41 192.168.122.209 [45511.976115] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:42:42 192.168.122.209 [45512.755136] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45512.755136] Maybe that's fine, but it's worth checking the [45512.755136] config - if there is no relations between the [45512.755136] names, then host name confusion attack is possible. Apr 26 04:42:42 192.168.122.209 [45512.861889] [tempesta fw] Configuration processing is completed. Apr 26 04:42:42 192.168.122.209 [45512.912803] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:42:42 192.168.122.209 [45512.941009] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:42:42 192.168.122.209 [45512.969333] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:42:42 192.168.122.209 [45513.013827] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:42:42 192.168.122.209 [45513.015526] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:42:42 192.168.122.209 [45513.017165] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:42:42 192.168.122.209 [45513.053834] [tempesta fw] Tempesta FW is ready Apr 26 04:42:42 192.168.122.209 [45513.173011] [tempesta fw] Warning: frang: restricted overridden HTTP method for 127.0.0.2: 8 (0x100u) Apr 26 04:42:42 192.168.122.209 [45513.174761] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:42:43 192.168.122.209 [45513.697766] [tdb] Close table 'client0.tdb' Apr 26 04:42:43 192.168.122.209 [45513.891527] [tdb] Close table 'sessions0.tdb' Apr 26 04:42:43 192.168.122.209 [45514.144276] [tdb] Close table 'filter0.tdb' Apr 26 04:42:43 192.168.122.209 [45514.145509] [tempesta fw] modules are stopped Apr 26 04:42:43 192.168.122.209 [45514.353021] [tempesta fw] exiting... Apr 26 04:42:44 192.168.122.209 [45514.506272] [tdb] Shutdown Tempesta DB Apr 26 04:42:44 192.168.122.209 [45514.685624] End test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideTestCase.test_not_accepted_request_x_http_method_override Apr 26 04:42:44 192.168.122.209 [45514.696060] Start test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideTestCase.test_not_accepted_request_x_method_override Apr 26 04:42:45 192.168.122.209 [45515.879223] [tdb] Start Tempesta DB Apr 26 04:42:45 192.168.122.209 [45516.019046] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:42:46 192.168.122.209 [45516.799170] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45516.799170] Maybe that's fine, but it's worth checking the [45516.799170] config - if there is no relations between the [45516.799170] names, then host name confusion attack is possible. Apr 26 04:42:46 192.168.122.209 [45516.909947] [tempesta fw] Configuration processing is completed. Apr 26 04:42:46 192.168.122.209 [45516.966062] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:42:46 192.168.122.209 [45516.995159] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:42:46 192.168.122.209 [45517.023040] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:42:46 192.168.122.209 [45517.069938] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:42:46 192.168.122.209 [45517.071645] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:42:46 192.168.122.209 [45517.073296] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:42:46 192.168.122.209 [45517.109881] [tempesta fw] Tempesta FW is ready Apr 26 04:42:46 192.168.122.209 [45517.236749] [tempesta fw] Warning: frang: restricted overridden HTTP method for 127.0.0.2: 8 (0x100u) Apr 26 04:42:46 192.168.122.209 [45517.237596] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:42:47 192.168.122.209 [45517.742959] [tdb] Close table 'client0.tdb' Apr 26 04:42:47 192.168.122.209 [45517.934841] [tdb] Close table 'sessions0.tdb' Apr 26 04:42:47 192.168.122.209 [45518.152490] [tdb] Close table 'filter0.tdb' Apr 26 04:42:47 192.168.122.209 [45518.152890] [tempesta fw] modules are stopped Apr 26 04:42:47 192.168.122.209 [45518.344060] [tempesta fw] exiting... Apr 26 04:42:48 192.168.122.209 [45518.479004] [tdb] Shutdown Tempesta DB Apr 26 04:42:48 192.168.122.209 [45518.686242] End test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideTestCase.test_not_accepted_request_x_method_override Apr 26 04:42:48 192.168.122.209 [45518.706378] Start test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideTestCase.test_unsafe_override_x_http_method Apr 26 04:42:49 192.168.122.209 [45519.905010] [tdb] Start Tempesta DB Apr 26 04:42:49 192.168.122.209 [45520.048613] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:42:50 192.168.122.209 [45520.815261] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45520.815261] Maybe that's fine, but it's worth checking the [45520.815261] config - if there is no relations between the [45520.815261] names, then host name confusion attack is possible. Apr 26 04:42:50 192.168.122.209 [45520.918050] [tempesta fw] Configuration processing is completed. Apr 26 04:42:50 192.168.122.209 [45520.979027] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:42:50 192.168.122.209 [45521.009703] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:42:50 192.168.122.209 [45521.037395] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:42:50 192.168.122.209 [45521.081991] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:42:50 192.168.122.209 [45521.083687] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:42:50 192.168.122.209 [45521.085356] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:42:50 192.168.122.209 [45521.125925] [tempesta fw] Tempesta FW is ready Apr 26 04:42:50 192.168.122.209 [45521.256962] [tempesta fw] Warning: request dropped: unsafe method override: 127.0.0.2 Apr 26 04:42:51 192.168.122.209 [45521.790351] [tdb] Close table 'client0.tdb' Apr 26 04:42:51 192.168.122.209 [45521.990665] [tdb] Close table 'sessions0.tdb' Apr 26 04:42:51 192.168.122.209 [45522.258416] [tdb] Close table 'filter0.tdb' Apr 26 04:42:51 192.168.122.209 [45522.258850] [tempesta fw] modules are stopped Apr 26 04:42:52 192.168.122.209 [45522.447398] [tempesta fw] exiting... Apr 26 04:42:52 192.168.122.209 [45522.582742] [tdb] Shutdown Tempesta DB Apr 26 04:42:52 192.168.122.209 [45522.823367] End test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideTestCase.test_unsafe_override_x_http_method Apr 26 04:42:52 192.168.122.209 [45522.844112] Start test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideTestCase.test_unsafe_override_x_http_method_override Apr 26 04:42:53 192.168.122.209 [45524.045461] [tdb] Start Tempesta DB Apr 26 04:42:53 192.168.122.209 [45524.195372] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:42:54 192.168.122.209 [45525.035422] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45525.035422] Maybe that's fine, but it's worth checking the [45525.035422] config - if there is no relations between the [45525.035422] names, then host name confusion attack is possible. Apr 26 04:42:54 192.168.122.209 [45525.134066] [tempesta fw] Configuration processing is completed. Apr 26 04:42:54 192.168.122.209 [45525.192597] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:42:54 192.168.122.209 [45525.223394] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:42:54 192.168.122.209 [45525.254062] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:42:54 192.168.122.209 [45525.294204] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:42:54 192.168.122.209 [45525.295935] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:42:54 192.168.122.209 [45525.297605] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:42:54 192.168.122.209 [45525.341978] [tempesta fw] Tempesta FW is ready Apr 26 04:42:55 192.168.122.209 [45525.483310] [tempesta fw] Warning: request dropped: unsafe method override: 127.0.0.2 Apr 26 04:42:55 192.168.122.209 [45525.990328] [tdb] Close table 'client0.tdb' Apr 26 04:42:55 192.168.122.209 [45526.177445] [tdb] Close table 'sessions0.tdb' Apr 26 04:42:56 192.168.122.209 [45526.415126] [tdb] Close table 'filter0.tdb' Apr 26 04:42:56 192.168.122.209 [45526.415548] [tempesta fw] modules are stopped Apr 26 04:42:56 192.168.122.209 [45526.590333] [tempesta fw] exiting... Apr 26 04:42:56 192.168.122.209 [45526.701665] [tdb] Shutdown Tempesta DB Apr 26 04:42:56 192.168.122.209 [45526.913769] End test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideTestCase.test_unsafe_override_x_http_method_override Apr 26 04:42:56 192.168.122.209 [45526.928660] Start test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideTestCase.test_unsafe_override_x_method_override Apr 26 04:42:57 192.168.122.209 [45528.055910] [tdb] Start Tempesta DB Apr 26 04:42:57 192.168.122.209 [45528.217259] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:42:58 192.168.122.209 [45529.031368] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45529.031368] Maybe that's fine, but it's worth checking the [45529.031368] config - if there is no relations between the [45529.031368] names, then host name confusion attack is possible. Apr 26 04:42:58 192.168.122.209 [45529.134113] [tempesta fw] Configuration processing is completed. Apr 26 04:42:58 192.168.122.209 [45529.185433] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:42:58 192.168.122.209 [45529.215336] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:42:58 192.168.122.209 [45529.241654] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:42:58 192.168.122.209 [45529.286045] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:42:58 192.168.122.209 [45529.287269] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:42:58 192.168.122.209 [45529.288419] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:42:58 192.168.122.209 [45529.326026] [tempesta fw] Tempesta FW is ready Apr 26 04:42:59 192.168.122.209 [45529.444312] [tempesta fw] Warning: request dropped: unsafe method override: 127.0.0.2 Apr 26 04:42:59 192.168.122.209 [45529.983703] [tdb] Close table 'client0.tdb' Apr 26 04:42:59 192.168.122.209 [45530.171771] [tdb] Close table 'sessions0.tdb' Apr 26 04:43:00 192.168.122.209 [45530.403210] [tdb] Close table 'filter0.tdb' Apr 26 04:43:00 192.168.122.209 [45530.403640] [tempesta fw] modules are stopped Apr 26 04:43:00 192.168.122.209 [45530.628222] [tempesta fw] exiting... Apr 26 04:43:00 192.168.122.209 [45530.790958] [tdb] Shutdown Tempesta DB Apr 26 04:43:00 192.168.122.209 [45531.000123] End test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideTestCase.test_unsafe_override_x_method_override Apr 26 04:43:00 192.168.122.209 [45531.021665] Start test: t_frang.test_http_methods.FrangHttpMethodsH2.test_accepted_request Apr 26 04:43:01 192.168.122.209 [45532.190612] [tdb] Start Tempesta DB Apr 26 04:43:01 192.168.122.209 [45532.344463] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:43:02 192.168.122.209 [45533.115394] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45533.115394] Maybe that's fine, but it's worth checking the [45533.115394] config - if there is no relations between the [45533.115394] names, then host name confusion attack is possible. Apr 26 04:43:02 192.168.122.209 [45533.222174] [tempesta fw] Configuration processing is completed. Apr 26 04:43:02 192.168.122.209 [45533.273273] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:43:02 192.168.122.209 [45533.301007] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:43:02 192.168.122.209 [45533.327979] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:43:02 192.168.122.209 [45533.378196] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:43:03 192.168.122.209 [45533.379873] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:43:03 192.168.122.209 [45533.381546] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:43:03 192.168.122.209 [45533.418077] [tempesta fw] Tempesta FW is ready Apr 26 04:43:03 192.168.122.209 [45534.061180] [tdb] Close table 'client0.tdb' Apr 26 04:43:03 192.168.122.209 [45534.257651] [tdb] Close table 'sessions0.tdb' Apr 26 04:43:04 192.168.122.209 [45534.493459] [tdb] Close table 'filter0.tdb' Apr 26 04:43:04 192.168.122.209 [45534.493896] [tempesta fw] modules are stopped Apr 26 04:43:04 192.168.122.209 [45534.688249] [tempesta fw] exiting... Apr 26 04:43:04 192.168.122.209 [45534.818635] [tdb] Shutdown Tempesta DB Apr 26 04:43:04 192.168.122.209 [45535.006051] End test: t_frang.test_http_methods.FrangHttpMethodsH2.test_accepted_request Apr 26 04:43:04 192.168.122.209 [45535.017095] Start test: t_frang.test_http_methods.FrangHttpMethodsH2.test_accepted_request_shipping_cfg Apr 26 04:43:05 192.168.122.209 [45536.195351] [tdb] Start Tempesta DB Apr 26 04:43:05 192.168.122.209 [45536.351350] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:43:06 192.168.122.209 [45537.115475] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45537.115475] Maybe that's fine, but it's worth checking the [45537.115475] config - if there is no relations between the [45537.115475] names, then host name confusion attack is possible. Apr 26 04:43:06 192.168.122.209 [45537.230220] [tempesta fw] Configuration processing is completed. Apr 26 04:43:06 192.168.122.209 [45537.277870] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:43:06 192.168.122.209 [45537.305633] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:43:06 192.168.122.209 [45537.332375] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:43:07 192.168.122.209 [45537.394164] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:43:07 192.168.122.209 [45537.395814] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:43:07 192.168.122.209 [45537.397500] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:43:07 192.168.122.209 [45537.434079] [tempesta fw] Tempesta FW is ready Apr 26 04:43:07 192.168.122.209 [45538.166419] [tdb] Close table 'client0.tdb' Apr 26 04:43:07 192.168.122.209 [45538.355106] [tdb] Close table 'sessions0.tdb' Apr 26 04:43:08 192.168.122.209 [45538.570143] [tdb] Close table 'filter0.tdb' Apr 26 04:43:08 192.168.122.209 [45538.570571] [tempesta fw] modules are stopped Apr 26 04:43:08 192.168.122.209 [45538.808546] [tempesta fw] exiting... Apr 26 04:43:08 192.168.122.209 [45538.931882] [tdb] Shutdown Tempesta DB Apr 26 04:43:08 192.168.122.209 [45539.137459] End test: t_frang.test_http_methods.FrangHttpMethodsH2.test_accepted_request_shipping_cfg Apr 26 04:43:08 192.168.122.209 [45539.154353] Start test: t_frang.test_http_methods.FrangHttpMethodsH2.test_accepted_request_with_unknown_method Apr 26 04:43:10 192.168.122.209 [45540.408053] [tdb] Start Tempesta DB Apr 26 04:43:10 192.168.122.209 [45540.547719] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:43:10 192.168.122.209 [45541.371572] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45541.371572] Maybe that's fine, but it's worth checking the [45541.371572] config - if there is no relations between the [45541.371572] names, then host name confusion attack is possible. Apr 26 04:43:11 192.168.122.209 [45541.470563] [tempesta fw] Configuration processing is completed. Apr 26 04:43:11 192.168.122.209 [45541.521383] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:43:11 192.168.122.209 [45541.550938] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:43:11 192.168.122.209 [45541.577831] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:43:11 192.168.122.209 [45541.622167] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:43:11 192.168.122.209 [45541.623151] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:43:11 192.168.122.209 [45541.624184] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:43:11 192.168.122.209 [45541.662178] [tempesta fw] Tempesta FW is ready Apr 26 04:43:11 192.168.122.209 [45542.325802] [tdb] Close table 'client0.tdb' Apr 26 04:43:12 192.168.122.209 [45542.509172] [tdb] Close table 'sessions0.tdb' Apr 26 04:43:12 192.168.122.209 [45542.737091] [tdb] Close table 'filter0.tdb' Apr 26 04:43:12 192.168.122.209 [45542.737547] [tempesta fw] modules are stopped Apr 26 04:43:12 192.168.122.209 [45542.920877] [tempesta fw] exiting... Apr 26 04:43:12 192.168.122.209 [45543.052587] [tdb] Shutdown Tempesta DB Apr 26 04:43:12 192.168.122.209 [45543.231056] End test: t_frang.test_http_methods.FrangHttpMethodsH2.test_accepted_request_with_unknown_method Apr 26 04:43:12 192.168.122.209 [45543.252522] Start test: t_frang.test_http_methods.FrangHttpMethodsH2.test_not_accepted_request Apr 26 04:43:14 192.168.122.209 [45544.437009] [tdb] Start Tempesta DB Apr 26 04:43:14 192.168.122.209 [45544.572415] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:43:14 192.168.122.209 [45545.315638] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45545.315638] Maybe that's fine, but it's worth checking the [45545.315638] config - if there is no relations between the [45545.315638] names, then host name confusion attack is possible. Apr 26 04:43:15 192.168.122.209 [45545.418617] [tempesta fw] Configuration processing is completed. Apr 26 04:43:15 192.168.122.209 [45545.473241] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:43:15 192.168.122.209 [45545.505154] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:43:15 192.168.122.209 [45545.534688] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:43:15 192.168.122.209 [45545.578226] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:43:15 192.168.122.209 [45545.579271] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:43:15 192.168.122.209 [45545.580503] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:43:15 192.168.122.209 [45545.622249] [tempesta fw] Tempesta FW is ready Apr 26 04:43:15 192.168.122.209 [45545.757871] [tempesta fw] Warning: frang: restricted HTTP method for 127.0.0.2: 10 (0x400u) Apr 26 04:43:15 192.168.122.209 [45545.760203] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:43:15 192.168.122.209 [45546.288058] [tdb] Close table 'client0.tdb' Apr 26 04:43:16 192.168.122.209 [45546.494550] [tdb] Close table 'sessions0.tdb' Apr 26 04:43:16 192.168.122.209 [45546.750398] [tdb] Close table 'filter0.tdb' Apr 26 04:43:16 192.168.122.209 [45546.750835] [tempesta fw] modules are stopped Apr 26 04:43:16 192.168.122.209 [45546.962151] [tempesta fw] exiting... Apr 26 04:43:16 192.168.122.209 [45547.107649] [tdb] Shutdown Tempesta DB Apr 26 04:43:16 192.168.122.209 [45547.306578] End test: t_frang.test_http_methods.FrangHttpMethodsH2.test_not_accepted_request Apr 26 04:43:16 192.168.122.209 [45547.317600] Start test: t_frang.test_http_methods.FrangHttpMethodsH2.test_not_accepted_request_owerride Apr 26 04:43:18 192.168.122.209 [45548.493884] [tdb] Start Tempesta DB Apr 26 04:43:18 192.168.122.209 [45548.642461] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:43:19 192.168.122.209 [45549.471599] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45549.471599] Maybe that's fine, but it's worth checking the [45549.471599] config - if there is no relations between the [45549.471599] names, then host name confusion attack is possible. Apr 26 04:43:19 192.168.122.209 [45549.582344] [tempesta fw] Configuration processing is completed. Apr 26 04:43:19 192.168.122.209 [45549.634879] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:43:19 192.168.122.209 [45549.665608] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:43:19 192.168.122.209 [45549.693053] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:43:19 192.168.122.209 [45549.750313] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:43:19 192.168.122.209 [45549.752024] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:43:19 192.168.122.209 [45549.753680] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:43:19 192.168.122.209 [45549.790245] [tempesta fw] Tempesta FW is ready Apr 26 04:43:19 192.168.122.209 [45549.925884] [tempesta fw] Warning: frang: restricted HTTP method for 127.0.0.2: 17 (0x20000u) Apr 26 04:43:19 192.168.122.209 [45549.926943] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:43:20 192.168.122.209 [45550.512210] [tdb] Close table 'client0.tdb' Apr 26 04:43:20 192.168.122.209 [45550.709749] [tdb] Close table 'sessions0.tdb' Apr 26 04:43:20 192.168.122.209 [45550.941025] [tdb] Close table 'filter0.tdb' Apr 26 04:43:20 192.168.122.209 [45550.941471] [tempesta fw] modules are stopped Apr 26 04:43:20 192.168.122.209 [45551.138820] [tempesta fw] exiting... Apr 26 04:43:20 192.168.122.209 [45551.299558] [tdb] Shutdown Tempesta DB Apr 26 04:43:21 192.168.122.209 [45551.503770] End test: t_frang.test_http_methods.FrangHttpMethodsH2.test_not_accepted_request_owerride Apr 26 04:43:21 192.168.122.209 [45551.510937] Start test: t_frang.test_http_methods.FrangHttpMethodsH2.test_not_accepted_request_register Apr 26 04:43:22 192.168.122.209 [45552.713455] [tdb] Start Tempesta DB Apr 26 04:43:22 192.168.122.209 [45552.861684] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:43:23 192.168.122.209 [45553.659704] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45553.659704] Maybe that's fine, but it's worth checking the [45553.659704] config - if there is no relations between the [45553.659704] names, then host name confusion attack is possible. Apr 26 04:43:23 192.168.122.209 [45553.778623] [tempesta fw] Configuration processing is completed. Apr 26 04:43:23 192.168.122.209 [45553.829155] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:43:23 192.168.122.209 [45553.856977] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:43:23 192.168.122.209 [45553.883700] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:43:23 192.168.122.209 [45553.942349] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:43:23 192.168.122.209 [45553.944039] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:43:23 192.168.122.209 [45553.945686] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:43:23 192.168.122.209 [45553.982333] [tempesta fw] Tempesta FW is ready Apr 26 04:43:23 192.168.122.209 [45554.120397] [tempesta fw] Warning: frang: restricted HTTP method for 127.0.0.2: 17 (0x20000u) Apr 26 04:43:23 192.168.122.209 [45554.121597] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:43:24 192.168.122.209 [45554.642392] [tdb] Close table 'client0.tdb' Apr 26 04:43:24 192.168.122.209 [45554.841335] [tdb] Close table 'sessions0.tdb' Apr 26 04:43:24 192.168.122.209 [45555.076365] [tdb] Close table 'filter0.tdb' Apr 26 04:43:24 192.168.122.209 [45555.076798] [tempesta fw] modules are stopped Apr 26 04:43:24 192.168.122.209 [45555.275117] [tempesta fw] exiting... Apr 26 04:43:25 192.168.122.209 [45555.405727] [tdb] Shutdown Tempesta DB Apr 26 04:43:25 192.168.122.209 [45555.599193] End test: t_frang.test_http_methods.FrangHttpMethodsH2.test_not_accepted_request_register Apr 26 04:43:25 192.168.122.209 [45555.611024] Start test: t_frang.test_http_methods.FrangHttpMethodsH2.test_not_accepted_request_shipping_cfg_CONNECT Apr 26 04:43:26 192.168.122.209 [45556.739699] [tdb] Start Tempesta DB Apr 26 04:43:26 192.168.122.209 [45556.873790] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:43:27 192.168.122.209 [45557.711636] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45557.711636] Maybe that's fine, but it's worth checking the [45557.711636] config - if there is no relations between the [45557.711636] names, then host name confusion attack is possible. Apr 26 04:43:27 192.168.122.209 [45557.814514] [tempesta fw] Configuration processing is completed. Apr 26 04:43:27 192.168.122.209 [45557.868239] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:43:27 192.168.122.209 [45557.896136] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:43:27 192.168.122.209 [45557.923235] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:43:27 192.168.122.209 [45557.986460] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:43:27 192.168.122.209 [45557.988158] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:43:27 192.168.122.209 [45557.989825] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:43:27 192.168.122.209 [45558.026440] [tempesta fw] Tempesta FW is ready Apr 26 04:43:27 192.168.122.209 [45558.155542] [tempesta fw] Warning: frang: restricted HTTP method for 127.0.0.2: 17 (0x20000u) Apr 26 04:43:27 192.168.122.209 [45558.156521] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:43:28 192.168.122.209 [45558.692013] [tdb] Close table 'client0.tdb' Apr 26 04:43:28 192.168.122.209 [45558.883302] [tdb] Close table 'sessions0.tdb' Apr 26 04:43:28 192.168.122.209 [45559.107781] [tdb] Close table 'filter0.tdb' Apr 26 04:43:28 192.168.122.209 [45559.108239] [tempesta fw] modules are stopped Apr 26 04:43:28 192.168.122.209 [45559.296450] [tempesta fw] exiting... Apr 26 04:43:29 192.168.122.209 [45559.426796] [tdb] Shutdown Tempesta DB Apr 26 04:43:29 192.168.122.209 [45559.615619] End test: t_frang.test_http_methods.FrangHttpMethodsH2.test_not_accepted_request_shipping_cfg_CONNECT Apr 26 04:43:29 192.168.122.209 [45559.627294] Start test: t_frang.test_http_methods.FrangHttpMethodsH2.test_not_accepted_request_shipping_cfg_DELETE Apr 26 04:43:30 192.168.122.209 [45560.788082] [tdb] Start Tempesta DB Apr 26 04:43:30 192.168.122.209 [45560.915907] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:43:31 192.168.122.209 [45561.747755] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45561.747755] Maybe that's fine, but it's worth checking the [45561.747755] config - if there is no relations between the [45561.747755] names, then host name confusion attack is possible. Apr 26 04:43:31 192.168.122.209 [45561.846518] [tempesta fw] Configuration processing is completed. Apr 26 04:43:31 192.168.122.209 [45561.899278] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:43:31 192.168.122.209 [45561.930078] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:43:31 192.168.122.209 [45561.956954] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:43:31 192.168.122.209 [45562.014493] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:43:31 192.168.122.209 [45562.016191] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:43:31 192.168.122.209 [45562.017841] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:43:31 192.168.122.209 [45562.058438] [tempesta fw] Tempesta FW is ready Apr 26 04:43:31 192.168.122.209 [45562.195539] [tempesta fw] Warning: frang: restricted HTTP method for 127.0.0.2: 2 (0x4u) Apr 26 04:43:31 192.168.122.209 [45562.196460] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:43:32 192.168.122.209 [45562.723624] [tdb] Close table 'client0.tdb' Apr 26 04:43:32 192.168.122.209 [45562.924429] [tdb] Close table 'sessions0.tdb' Apr 26 04:43:32 192.168.122.209 [45563.176566] [tdb] Close table 'filter0.tdb' Apr 26 04:43:32 192.168.122.209 [45563.176988] [tempesta fw] modules are stopped Apr 26 04:43:32 192.168.122.209 [45563.355799] [tempesta fw] exiting... Apr 26 04:43:33 192.168.122.209 [45563.476509] [tdb] Shutdown Tempesta DB Apr 26 04:43:33 192.168.122.209 [45563.704115] End test: t_frang.test_http_methods.FrangHttpMethodsH2.test_not_accepted_request_shipping_cfg_DELETE Apr 26 04:43:33 192.168.122.209 [45563.717639] Start test: t_frang.test_http_methods.FrangHttpMethodsH2.test_not_accepted_request_shipping_cfg_OPTIONS Apr 26 04:43:34 192.168.122.209 [45564.833864] [tdb] Start Tempesta DB Apr 26 04:43:34 192.168.122.209 [45564.971035] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:43:35 192.168.122.209 [45565.743776] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45565.743776] Maybe that's fine, but it's worth checking the [45565.743776] config - if there is no relations between the [45565.743776] names, then host name confusion attack is possible. Apr 26 04:43:35 192.168.122.209 [45565.850562] [tempesta fw] Configuration processing is completed. Apr 26 04:43:35 192.168.122.209 [45565.899848] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:43:35 192.168.122.209 [45565.927292] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:43:35 192.168.122.209 [45565.953640] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:43:35 192.168.122.209 [45566.022590] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:43:35 192.168.122.209 [45566.024287] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:43:35 192.168.122.209 [45566.025907] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:43:35 192.168.122.209 [45566.062487] [tempesta fw] Tempesta FW is ready Apr 26 04:43:35 192.168.122.209 [45566.203426] [tempesta fw] Warning: frang: restricted HTTP method for 127.0.0.2: 8 (0x100u) Apr 26 04:43:35 192.168.122.209 [45566.205716] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:43:36 192.168.122.209 [45566.708144] [tdb] Close table 'client0.tdb' Apr 26 04:43:36 192.168.122.209 [45566.896505] [tdb] Close table 'sessions0.tdb' Apr 26 04:43:36 192.168.122.209 [45567.115372] [tdb] Close table 'filter0.tdb' Apr 26 04:43:36 192.168.122.209 [45567.115810] [tempesta fw] modules are stopped Apr 26 04:43:36 192.168.122.209 [45567.288347] [tempesta fw] exiting... Apr 26 04:43:37 192.168.122.209 [45567.409326] [tdb] Shutdown Tempesta DB Apr 26 04:43:37 192.168.122.209 [45567.614791] End test: t_frang.test_http_methods.FrangHttpMethodsH2.test_not_accepted_request_shipping_cfg_OPTIONS Apr 26 04:43:37 192.168.122.209 [45567.627395] Start test: t_frang.test_http_methods.FrangHttpMethodsH2.test_not_accepted_request_shipping_cfg_PATCH Apr 26 04:43:38 192.168.122.209 [45568.833784] [tdb] Start Tempesta DB Apr 26 04:43:38 192.168.122.209 [45568.960586] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:43:39 192.168.122.209 [45569.711856] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45569.711856] Maybe that's fine, but it's worth checking the [45569.711856] config - if there is no relations between the [45569.711856] names, then host name confusion attack is possible. Apr 26 04:43:39 192.168.122.209 [45569.818622] [tempesta fw] Configuration processing is completed. Apr 26 04:43:39 192.168.122.209 [45569.873651] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:43:39 192.168.122.209 [45569.903687] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:43:39 192.168.122.209 [45569.930672] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:43:39 192.168.122.209 [45569.986608] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:43:39 192.168.122.209 [45569.988297] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:43:39 192.168.122.209 [45569.990018] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:43:39 192.168.122.209 [45570.030580] [tempesta fw] Tempesta FW is ready Apr 26 04:43:39 192.168.122.209 [45570.157696] [tempesta fw] Warning: frang: restricted HTTP method for 127.0.0.2: 9 (0x200u) Apr 26 04:43:39 192.168.122.209 [45570.160018] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:43:40 192.168.122.209 [45570.673950] [tdb] Close table 'client0.tdb' Apr 26 04:43:40 192.168.122.209 [45570.859604] [tdb] Close table 'sessions0.tdb' Apr 26 04:43:40 192.168.122.209 [45571.097239] [tdb] Close table 'filter0.tdb' Apr 26 04:43:40 192.168.122.209 [45571.097682] [tempesta fw] modules are stopped Apr 26 04:43:40 192.168.122.209 [45571.274872] [tempesta fw] exiting... Apr 26 04:43:41 192.168.122.209 [45571.417585] [tdb] Shutdown Tempesta DB Apr 26 04:43:41 192.168.122.209 [45571.629759] End test: t_frang.test_http_methods.FrangHttpMethodsH2.test_not_accepted_request_shipping_cfg_PATCH Apr 26 04:43:41 192.168.122.209 [45571.640913] Start test: t_frang.test_http_methods.FrangHttpMethodsH2.test_not_accepted_request_shipping_cfg_PUT Apr 26 04:43:42 192.168.122.209 [45572.789831] [tdb] Start Tempesta DB Apr 26 04:43:42 192.168.122.209 [45572.931256] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:43:43 192.168.122.209 [45573.707905] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45573.707905] Maybe that's fine, but it's worth checking the [45573.707905] config - if there is no relations between the [45573.707905] names, then host name confusion attack is possible. Apr 26 04:43:43 192.168.122.209 [45573.810632] [tempesta fw] Configuration processing is completed. Apr 26 04:43:43 192.168.122.209 [45573.869405] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:43:43 192.168.122.209 [45573.896872] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:43:43 192.168.122.209 [45573.923367] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:43:43 192.168.122.209 [45573.966638] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:43:43 192.168.122.209 [45573.968307] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:43:43 192.168.122.209 [45573.969954] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:43:43 192.168.122.209 [45574.014589] [tempesta fw] Tempesta FW is ready Apr 26 04:43:43 192.168.122.209 [45574.136034] [tempesta fw] Warning: frang: restricted HTTP method for 127.0.0.2: 13 (0x2000u) Apr 26 04:43:43 192.168.122.209 [45574.137141] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:43:44 192.168.122.209 [45574.656518] [tdb] Close table 'client0.tdb' Apr 26 04:43:44 192.168.122.209 [45574.850630] [tdb] Close table 'sessions0.tdb' Apr 26 04:43:44 192.168.122.209 [45575.083371] [tdb] Close table 'filter0.tdb' Apr 26 04:43:44 192.168.122.209 [45575.083811] [tempesta fw] modules are stopped Apr 26 04:43:44 192.168.122.209 [45575.286429] [tempesta fw] exiting... Apr 26 04:43:45 192.168.122.209 [45575.430920] [tdb] Shutdown Tempesta DB Apr 26 04:43:45 192.168.122.209 [45575.638567] End test: t_frang.test_http_methods.FrangHttpMethodsH2.test_not_accepted_request_shipping_cfg_PUT Apr 26 04:43:45 192.168.122.209 [45575.650473] Start test: t_frang.test_http_methods.FrangHttpMethodsH2.test_not_accepted_request_shipping_cfg_TRACE Apr 26 04:43:46 192.168.122.209 [45576.780941] [tdb] Start Tempesta DB Apr 26 04:43:46 192.168.122.209 [45576.907743] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:43:47 192.168.122.209 [45577.715930] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45577.715930] Maybe that's fine, but it's worth checking the [45577.715930] config - if there is no relations between the [45577.715930] names, then host name confusion attack is possible. Apr 26 04:43:47 192.168.122.209 [45577.818709] [tempesta fw] Configuration processing is completed. Apr 26 04:43:47 192.168.122.209 [45577.866398] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:43:47 192.168.122.209 [45577.893491] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:43:47 192.168.122.209 [45577.919678] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:43:47 192.168.122.209 [45577.998727] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:43:47 192.168.122.209 [45578.000402] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:43:47 192.168.122.209 [45578.002046] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:43:47 192.168.122.209 [45578.046646] [tempesta fw] Tempesta FW is ready Apr 26 04:43:47 192.168.122.209 [45578.191929] [tempesta fw] Warning: frang: restricted HTTP method for 127.0.0.2: 14 (0x4000u) Apr 26 04:43:47 192.168.122.209 [45578.194258] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:43:48 192.168.122.209 [45578.702234] [tdb] Close table 'client0.tdb' Apr 26 04:43:48 192.168.122.209 [45578.895341] [tdb] Close table 'sessions0.tdb' Apr 26 04:43:48 192.168.122.209 [45579.148806] [tdb] Close table 'filter0.tdb' Apr 26 04:43:48 192.168.122.209 [45579.149252] [tempesta fw] modules are stopped Apr 26 04:43:49 192.168.122.209 [45579.381311] [tempesta fw] exiting... Apr 26 04:43:49 192.168.122.209 [45579.518231] [tdb] Shutdown Tempesta DB Apr 26 04:43:49 192.168.122.209 [45579.736566] End test: t_frang.test_http_methods.FrangHttpMethodsH2.test_not_accepted_request_shipping_cfg_TRACE Apr 26 04:43:49 192.168.122.209 [45579.750226] Start test: t_frang.test_http_methods.FrangHttpMethodsH2.test_not_accepted_request_with_unknown_method Apr 26 04:43:50 192.168.122.209 [45580.906440] [tdb] Start Tempesta DB Apr 26 04:43:50 192.168.122.209 [45581.030910] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:43:51 192.168.122.209 [45581.800008] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45581.800008] Maybe that's fine, but it's worth checking the [45581.800008] config - if there is no relations between the [45581.800008] names, then host name confusion attack is possible. Apr 26 04:43:51 192.168.122.209 [45581.914764] [tempesta fw] Configuration processing is completed. Apr 26 04:43:51 192.168.122.209 [45581.965485] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:43:51 192.168.122.209 [45581.994724] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:43:51 192.168.122.209 [45582.021275] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:43:51 192.168.122.209 [45582.070749] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:43:51 192.168.122.209 [45582.072093] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:43:51 192.168.122.209 [45582.073621] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:43:51 192.168.122.209 [45582.126720] [tempesta fw] Tempesta FW is ready Apr 26 04:43:51 192.168.122.209 [45582.253406] [tempesta fw] Warning: frang: restricted HTTP method for 127.0.0.2: 17 (0x20000u) Apr 26 04:43:51 192.168.122.209 [45582.254217] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:43:52 192.168.122.209 [45582.771810] [tdb] Close table 'client0.tdb' Apr 26 04:43:52 192.168.122.209 [45582.965329] [tdb] Close table 'sessions0.tdb' Apr 26 04:43:52 192.168.122.209 [45583.200513] [tdb] Close table 'filter0.tdb' Apr 26 04:43:52 192.168.122.209 [45583.201274] [tempesta fw] modules are stopped Apr 26 04:43:53 192.168.122.209 [45583.384131] [tempesta fw] exiting... Apr 26 04:43:53 192.168.122.209 [45583.507291] [tdb] Shutdown Tempesta DB Apr 26 04:43:53 192.168.122.209 [45583.691623] End test: t_frang.test_http_methods.FrangHttpMethodsH2.test_not_accepted_request_with_unknown_method Apr 26 04:43:53 192.168.122.209 [45583.708144] Start test: t_frang.test_http_methods.FrangHttpMethodsH2.test_not_accepted_request_zero_byte Apr 26 04:43:54 192.168.122.209 [45584.948827] [tdb] Start Tempesta DB Apr 26 04:43:54 192.168.122.209 [45585.064903] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:43:55 192.168.122.209 [45585.808042] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45585.808042] Maybe that's fine, but it's worth checking the [45585.808042] config - if there is no relations between the [45585.808042] names, then host name confusion attack is possible. Apr 26 04:43:55 192.168.122.209 [45585.906842] [tempesta fw] Configuration processing is completed. Apr 26 04:43:55 192.168.122.209 [45585.974656] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:43:55 192.168.122.209 [45586.002891] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:43:55 192.168.122.209 [45586.029557] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:43:55 192.168.122.209 [45586.086796] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:43:55 192.168.122.209 [45586.088487] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:43:55 192.168.122.209 [45586.090162] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:43:55 192.168.122.209 [45586.126738] [tempesta fw] Tempesta FW is ready Apr 26 04:43:55 192.168.122.209 [45586.259120] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_MethodUnknown input=0x0(''), len=2, off=0 Apr 26 04:43:56 192.168.122.209 [45586.780809] [tdb] Close table 'client0.tdb' Apr 26 04:43:56 192.168.122.209 [45586.971071] [tdb] Close table 'sessions0.tdb' Apr 26 04:43:56 192.168.122.209 [45587.212576] [tdb] Close table 'filter0.tdb' Apr 26 04:43:56 192.168.122.209 [45587.213016] [tempesta fw] modules are stopped Apr 26 04:43:57 192.168.122.209 [45587.427311] [tempesta fw] exiting... Apr 26 04:43:57 192.168.122.209 [45587.594091] [tdb] Shutdown Tempesta DB Apr 26 04:43:57 192.168.122.209 [45587.817223] End test: t_frang.test_http_methods.FrangHttpMethodsH2.test_not_accepted_request_zero_byte Apr 26 04:43:57 192.168.122.209 [45587.829863] Start test: t_frang.test_http_methods.FrangHttpMethodsTestCase.test_accepted_request Apr 26 04:43:58 192.168.122.209 [45588.954321] [tdb] Start Tempesta DB Apr 26 04:43:58 192.168.122.209 [45589.091849] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:43:59 192.168.122.209 [45589.844123] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45589.844123] Maybe that's fine, but it's worth checking the [45589.844123] config - if there is no relations between the [45589.844123] names, then host name confusion attack is possible. Apr 26 04:43:59 192.168.122.209 [45589.946895] [tempesta fw] Configuration processing is completed. Apr 26 04:43:59 192.168.122.209 [45590.011826] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:43:59 192.168.122.209 [45590.040471] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:43:59 192.168.122.209 [45590.066821] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:43:59 192.168.122.209 [45590.138834] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:43:59 192.168.122.209 [45590.140184] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:43:59 192.168.122.209 [45590.141771] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:43:59 192.168.122.209 [45590.178805] [tempesta fw] Tempesta FW is ready Apr 26 04:44:00 192.168.122.209 [45590.814074] [tdb] Close table 'client0.tdb' Apr 26 04:44:00 192.168.122.209 [45591.004630] [tdb] Close table 'sessions0.tdb' Apr 26 04:44:00 192.168.122.209 [45591.247488] [tdb] Close table 'filter0.tdb' Apr 26 04:44:00 192.168.122.209 [45591.247930] [tempesta fw] modules are stopped Apr 26 04:44:01 192.168.122.209 [45591.468971] [tempesta fw] exiting... Apr 26 04:44:01 192.168.122.209 [45591.615096] [tdb] Shutdown Tempesta DB Apr 26 04:44:01 192.168.122.209 [45591.825323] End test: t_frang.test_http_methods.FrangHttpMethodsTestCase.test_accepted_request Apr 26 04:44:01 192.168.122.209 [45591.837446] Start test: t_frang.test_http_methods.FrangHttpMethodsTestCase.test_accepted_request_shipping_cfg Apr 26 04:44:02 192.168.122.209 [45593.052871] [tdb] Start Tempesta DB Apr 26 04:44:02 192.168.122.209 [45593.191211] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:44:03 192.168.122.209 [45593.944170] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45593.944170] Maybe that's fine, but it's worth checking the [45593.944170] config - if there is no relations between the [45593.944170] names, then host name confusion attack is possible. Apr 26 04:44:03 192.168.122.209 [45594.042940] [tempesta fw] Configuration processing is completed. Apr 26 04:44:03 192.168.122.209 [45594.098440] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:44:03 192.168.122.209 [45594.125382] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:44:03 192.168.122.209 [45594.151275] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:44:03 192.168.122.209 [45594.206852] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:44:03 192.168.122.209 [45594.208526] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:44:03 192.168.122.209 [45594.210160] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:44:03 192.168.122.209 [45594.262848] [tempesta fw] Tempesta FW is ready Apr 26 04:44:04 192.168.122.209 [45594.924032] [tdb] Close table 'client0.tdb' Apr 26 04:44:04 192.168.122.209 [45595.117426] [tdb] Close table 'sessions0.tdb' Apr 26 04:44:04 192.168.122.209 [45595.339967] [tdb] Close table 'filter0.tdb' Apr 26 04:44:04 192.168.122.209 [45595.340395] [tempesta fw] modules are stopped Apr 26 04:44:05 192.168.122.209 [45595.524598] [tempesta fw] exiting... Apr 26 04:44:05 192.168.122.209 [45595.648894] [tdb] Shutdown Tempesta DB Apr 26 04:44:05 192.168.122.209 [45595.824896] End test: t_frang.test_http_methods.FrangHttpMethodsTestCase.test_accepted_request_shipping_cfg Apr 26 04:44:05 192.168.122.209 [45595.841572] Start test: t_frang.test_http_methods.FrangHttpMethodsTestCase.test_accepted_request_with_unknown_method Apr 26 04:44:06 192.168.122.209 [45597.041926] [tdb] Start Tempesta DB Apr 26 04:44:06 192.168.122.209 [45597.180696] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:44:07 192.168.122.209 [45597.976201] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45597.976201] Maybe that's fine, but it's worth checking the [45597.976201] config - if there is no relations between the [45597.976201] names, then host name confusion attack is possible. Apr 26 04:44:07 192.168.122.209 [45598.082966] [tempesta fw] Configuration processing is completed. Apr 26 04:44:07 192.168.122.209 [45598.133249] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:44:07 192.168.122.209 [45598.162478] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:44:07 192.168.122.209 [45598.188473] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:44:07 192.168.122.209 [45598.250947] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:44:07 192.168.122.209 [45598.252630] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:44:07 192.168.122.209 [45598.254284] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:44:07 192.168.122.209 [45598.302898] [tempesta fw] Tempesta FW is ready Apr 26 04:44:08 192.168.122.209 [45598.921827] [tdb] Close table 'client0.tdb' Apr 26 04:44:08 192.168.122.209 [45599.104886] [tdb] Close table 'sessions0.tdb' Apr 26 04:44:08 192.168.122.209 [45599.317243] [tdb] Close table 'filter0.tdb' Apr 26 04:44:08 192.168.122.209 [45599.317676] [tempesta fw] modules are stopped Apr 26 04:44:09 192.168.122.209 [45599.514044] [tempesta fw] exiting... Apr 26 04:44:09 192.168.122.209 [45599.655335] [tdb] Shutdown Tempesta DB Apr 26 04:44:09 192.168.122.209 [45599.844649] End test: t_frang.test_http_methods.FrangHttpMethodsTestCase.test_accepted_request_with_unknown_method Apr 26 04:44:09 192.168.122.209 [45599.857604] Start test: t_frang.test_http_methods.FrangHttpMethodsTestCase.test_not_accepted_request Apr 26 04:44:10 192.168.122.209 [45601.062345] [tdb] Start Tempesta DB Apr 26 04:44:10 192.168.122.209 [45601.207708] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:44:11 192.168.122.209 [45601.984264] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45601.984264] Maybe that's fine, but it's worth checking the [45601.984264] config - if there is no relations between the [45601.984264] names, then host name confusion attack is possible. Apr 26 04:44:11 192.168.122.209 [45602.090968] [tempesta fw] Configuration processing is completed. Apr 26 04:44:11 192.168.122.209 [45602.141146] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:44:11 192.168.122.209 [45602.169139] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:44:11 192.168.122.209 [45602.195902] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:44:11 192.168.122.209 [45602.251014] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:44:11 192.168.122.209 [45602.252694] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:44:11 192.168.122.209 [45602.254516] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:44:11 192.168.122.209 [45602.302903] [tempesta fw] Tempesta FW is ready Apr 26 04:44:12 192.168.122.209 [45602.437711] [tempesta fw] Warning: frang: restricted HTTP method for 127.0.0.2: 10 (0x400u) Apr 26 04:44:12 192.168.122.209 [45602.440047] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:44:12 192.168.122.209 [45602.961755] [tdb] Close table 'client0.tdb' Apr 26 04:44:12 192.168.122.209 [45603.148174] [tdb] Close table 'sessions0.tdb' Apr 26 04:44:13 192.168.122.209 [45603.393702] [tdb] Close table 'filter0.tdb' Apr 26 04:44:13 192.168.122.209 [45603.394200] [tempesta fw] modules are stopped Apr 26 04:44:13 192.168.122.209 [45603.619050] [tempesta fw] exiting... Apr 26 04:44:13 192.168.122.209 [45603.772688] [tdb] Shutdown Tempesta DB Apr 26 04:44:13 192.168.122.209 [45603.965616] End test: t_frang.test_http_methods.FrangHttpMethodsTestCase.test_not_accepted_request Apr 26 04:44:13 192.168.122.209 [45603.978391] Start test: t_frang.test_http_methods.FrangHttpMethodsTestCase.test_not_accepted_request_owerride Apr 26 04:44:14 192.168.122.209 [45605.157989] [tdb] Start Tempesta DB Apr 26 04:44:14 192.168.122.209 [45605.300871] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:44:15 192.168.122.209 [45606.096290] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45606.096290] Maybe that's fine, but it's worth checking the [45606.096290] config - if there is no relations between the [45606.096290] names, then host name confusion attack is possible. Apr 26 04:44:15 192.168.122.209 [45606.195074] [tempesta fw] Configuration processing is completed. Apr 26 04:44:15 192.168.122.209 [45606.244541] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:44:15 192.168.122.209 [45606.272703] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:44:15 192.168.122.209 [45606.299587] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:44:15 192.168.122.209 [45606.347032] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:44:15 192.168.122.209 [45606.348386] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:44:15 192.168.122.209 [45606.349761] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:44:16 192.168.122.209 [45606.394998] [tempesta fw] Tempesta FW is ready Apr 26 04:44:16 192.168.122.209 [45606.539592] [tempesta fw] Warning: frang: restricted HTTP method for 127.0.0.2: 17 (0x20000u) Apr 26 04:44:16 192.168.122.209 [45606.540407] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:44:16 192.168.122.209 [45607.028761] [tdb] Close table 'client0.tdb' Apr 26 04:44:16 192.168.122.209 [45607.229095] [tdb] Close table 'sessions0.tdb' Apr 26 04:44:17 192.168.122.209 [45607.457461] [tdb] Close table 'filter0.tdb' Apr 26 04:44:17 192.168.122.209 [45607.457900] [tempesta fw] modules are stopped Apr 26 04:44:17 192.168.122.209 [45607.644237] [tempesta fw] exiting... Apr 26 04:44:17 192.168.122.209 [45607.759155] [tdb] Shutdown Tempesta DB Apr 26 04:44:17 192.168.122.209 [45607.969988] End test: t_frang.test_http_methods.FrangHttpMethodsTestCase.test_not_accepted_request_owerride Apr 26 04:44:17 192.168.122.209 [45607.980650] Start test: t_frang.test_http_methods.FrangHttpMethodsTestCase.test_not_accepted_request_register Apr 26 04:44:18 192.168.122.209 [45609.262164] [tdb] Start Tempesta DB Apr 26 04:44:19 192.168.122.209 [45609.395887] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:44:19 192.168.122.209 [45610.132340] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45610.132340] Maybe that's fine, but it's worth checking the [45610.132340] config - if there is no relations between the [45610.132340] names, then host name confusion attack is possible. Apr 26 04:44:19 192.168.122.209 [45610.231153] [tempesta fw] Configuration processing is completed. Apr 26 04:44:19 192.168.122.209 [45610.285701] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:44:19 192.168.122.209 [45610.313306] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:44:19 192.168.122.209 [45610.342579] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:44:20 192.168.122.209 [45610.387072] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:44:20 192.168.122.209 [45610.388427] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:44:20 192.168.122.209 [45610.389726] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:44:20 192.168.122.209 [45610.435008] [tempesta fw] Tempesta FW is ready Apr 26 04:44:20 192.168.122.209 [45610.558362] [tempesta fw] Warning: frang: restricted HTTP method for 127.0.0.2: 17 (0x20000u) Apr 26 04:44:20 192.168.122.209 [45610.559400] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:44:20 192.168.122.209 [45611.088405] [tdb] Close table 'client0.tdb' Apr 26 04:44:20 192.168.122.209 [45611.269480] [tdb] Close table 'sessions0.tdb' Apr 26 04:44:21 192.168.122.209 [45611.508938] [tdb] Close table 'filter0.tdb' Apr 26 04:44:21 192.168.122.209 [45611.509370] [tempesta fw] modules are stopped Apr 26 04:44:21 192.168.122.209 [45611.715771] [tempesta fw] exiting... Apr 26 04:44:21 192.168.122.209 [45611.846762] [tdb] Shutdown Tempesta DB Apr 26 04:44:21 192.168.122.209 [45612.036242] End test: t_frang.test_http_methods.FrangHttpMethodsTestCase.test_not_accepted_request_register Apr 26 04:44:21 192.168.122.209 [45612.054080] Start test: t_frang.test_http_methods.FrangHttpMethodsTestCase.test_not_accepted_request_shipping_cfg_CONNECT Apr 26 04:44:22 192.168.122.209 [45613.265533] [tdb] Start Tempesta DB Apr 26 04:44:23 192.168.122.209 [45613.410882] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:44:23 192.168.122.209 [45614.224379] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45614.224379] Maybe that's fine, but it's worth checking the [45614.224379] config - if there is no relations between the [45614.224379] names, then host name confusion attack is possible. Apr 26 04:44:23 192.168.122.209 [45614.343182] [tempesta fw] Configuration processing is completed. Apr 26 04:44:24 192.168.122.209 [45614.393026] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:44:24 192.168.122.209 [45614.420425] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:44:24 192.168.122.209 [45614.446822] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:44:24 192.168.122.209 [45614.507163] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:44:24 192.168.122.209 [45614.508851] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:44:24 192.168.122.209 [45614.510485] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:44:24 192.168.122.209 [45614.547102] [tempesta fw] Tempesta FW is ready Apr 26 04:44:24 192.168.122.209 [45614.681880] [tempesta fw] Warning: frang: restricted HTTP method for 127.0.0.2: 17 (0x20000u) Apr 26 04:44:24 192.168.122.209 [45614.682871] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:44:24 192.168.122.209 [45615.197335] [tdb] Close table 'client0.tdb' Apr 26 04:44:25 192.168.122.209 [45615.385790] [tdb] Close table 'sessions0.tdb' Apr 26 04:44:25 192.168.122.209 [45615.610985] [tdb] Close table 'filter0.tdb' Apr 26 04:44:25 192.168.122.209 [45615.611414] [tempesta fw] modules are stopped Apr 26 04:44:25 192.168.122.209 [45615.830817] [tempesta fw] exiting... Apr 26 04:44:25 192.168.122.209 [45615.963418] [tdb] Shutdown Tempesta DB Apr 26 04:44:25 192.168.122.209 [45616.131342] End test: t_frang.test_http_methods.FrangHttpMethodsTestCase.test_not_accepted_request_shipping_cfg_CONNECT Apr 26 04:44:25 192.168.122.209 [45616.143662] Start test: t_frang.test_http_methods.FrangHttpMethodsTestCase.test_not_accepted_request_shipping_cfg_DELETE Apr 26 04:44:26 192.168.122.209 [45617.225353] [tdb] Start Tempesta DB Apr 26 04:44:26 192.168.122.209 [45617.367640] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:44:27 192.168.122.209 [45618.060389] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45618.060389] Maybe that's fine, but it's worth checking the [45618.060389] config - if there is no relations between the [45618.060389] names, then host name confusion attack is possible. Apr 26 04:44:27 192.168.122.209 [45618.167178] [tempesta fw] Configuration processing is completed. Apr 26 04:44:27 192.168.122.209 [45618.226642] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:44:27 192.168.122.209 [45618.254956] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:44:27 192.168.122.209 [45618.281601] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:44:27 192.168.122.209 [45618.335213] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:44:27 192.168.122.209 [45618.336904] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:44:27 192.168.122.209 [45618.338556] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:44:27 192.168.122.209 [45618.375154] [tempesta fw] Tempesta FW is ready Apr 26 04:44:28 192.168.122.209 [45618.491186] [tempesta fw] Warning: frang: restricted HTTP method for 127.0.0.2: 2 (0x4u) Apr 26 04:44:28 192.168.122.209 [45618.492161] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:44:28 192.168.122.209 [45618.986468] [tdb] Close table 'client0.tdb' Apr 26 04:44:28 192.168.122.209 [45619.176469] [tdb] Close table 'sessions0.tdb' Apr 26 04:44:29 192.168.122.209 [45619.394527] [tdb] Close table 'filter0.tdb' Apr 26 04:44:29 192.168.122.209 [45619.394959] [tempesta fw] modules are stopped Apr 26 04:44:29 192.168.122.209 [45619.596500] [tempesta fw] exiting... Apr 26 04:44:29 192.168.122.209 [45619.723086] [tdb] Shutdown Tempesta DB Apr 26 04:44:29 192.168.122.209 [45619.924430] End test: t_frang.test_http_methods.FrangHttpMethodsTestCase.test_not_accepted_request_shipping_cfg_DELETE Apr 26 04:44:29 192.168.122.209 [45619.938988] Start test: t_frang.test_http_methods.FrangHttpMethodsTestCase.test_not_accepted_request_shipping_cfg_OPTIONS Apr 26 04:44:30 192.168.122.209 [45621.015608] [tdb] Start Tempesta DB Apr 26 04:44:30 192.168.122.209 [45621.151489] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:44:31 192.168.122.209 [45621.844524] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45621.844524] Maybe that's fine, but it's worth checking the [45621.844524] config - if there is no relations between the [45621.844524] names, then host name confusion attack is possible. Apr 26 04:44:31 192.168.122.209 [45621.967273] [tempesta fw] Configuration processing is completed. Apr 26 04:44:31 192.168.122.209 [45622.017230] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:44:31 192.168.122.209 [45622.045020] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:44:31 192.168.122.209 [45622.072129] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:44:31 192.168.122.209 [45622.119252] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:44:31 192.168.122.209 [45622.120675] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:44:31 192.168.122.209 [45622.122103] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:44:31 192.168.122.209 [45622.159214] [tempesta fw] Tempesta FW is ready Apr 26 04:44:31 192.168.122.209 [45622.283330] [tempesta fw] Warning: frang: restricted HTTP method for 127.0.0.2: 8 (0x100u) Apr 26 04:44:31 192.168.122.209 [45622.284371] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:44:32 192.168.122.209 [45622.755326] [tdb] Close table 'client0.tdb' Apr 26 04:44:32 192.168.122.209 [45622.932950] [tdb] Close table 'sessions0.tdb' Apr 26 04:44:32 192.168.122.209 [45623.165954] [tdb] Close table 'filter0.tdb' Apr 26 04:44:32 192.168.122.209 [45623.166388] [tempesta fw] modules are stopped Apr 26 04:44:32 192.168.122.209 [45623.372013] [tempesta fw] exiting... Apr 26 04:44:33 192.168.122.209 [45623.518178] [tdb] Shutdown Tempesta DB Apr 26 04:44:33 192.168.122.209 [45623.736878] End test: t_frang.test_http_methods.FrangHttpMethodsTestCase.test_not_accepted_request_shipping_cfg_OPTIONS Apr 26 04:44:33 192.168.122.209 [45623.747052] Start test: t_frang.test_http_methods.FrangHttpMethodsTestCase.test_not_accepted_request_shipping_cfg_PATCH Apr 26 04:44:34 192.168.122.209 [45624.835698] [tdb] Start Tempesta DB Apr 26 04:44:34 192.168.122.209 [45624.981553] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:44:35 192.168.122.209 [45625.712538] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45625.712538] Maybe that's fine, but it's worth checking the [45625.712538] config - if there is no relations between the [45625.712538] names, then host name confusion attack is possible. Apr 26 04:44:35 192.168.122.209 [45625.815319] [tempesta fw] Configuration processing is completed. Apr 26 04:44:35 192.168.122.209 [45625.866307] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:44:35 192.168.122.209 [45625.895846] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:44:35 192.168.122.209 [45625.922025] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:44:35 192.168.122.209 [45625.971340] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:44:35 192.168.122.209 [45625.973025] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:44:35 192.168.122.209 [45625.974674] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:44:35 192.168.122.209 [45626.039262] [tempesta fw] Tempesta FW is ready Apr 26 04:44:35 192.168.122.209 [45626.160967] [tempesta fw] Warning: frang: restricted HTTP method for 127.0.0.2: 9 (0x200u) Apr 26 04:44:35 192.168.122.209 [45626.161724] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:44:36 192.168.122.209 [45626.660770] [tdb] Close table 'client0.tdb' Apr 26 04:44:36 192.168.122.209 [45626.848611] [tdb] Close table 'sessions0.tdb' Apr 26 04:44:36 192.168.122.209 [45627.103562] [tdb] Close table 'filter0.tdb' Apr 26 04:44:36 192.168.122.209 [45627.104002] [tempesta fw] modules are stopped Apr 26 04:44:36 192.168.122.209 [45627.324525] [tempesta fw] exiting... Apr 26 04:44:37 192.168.122.209 [45627.442175] [tdb] Shutdown Tempesta DB Apr 26 04:44:37 192.168.122.209 [45627.611451] End test: t_frang.test_http_methods.FrangHttpMethodsTestCase.test_not_accepted_request_shipping_cfg_PATCH Apr 26 04:44:37 192.168.122.209 [45627.629950] Start test: t_frang.test_http_methods.FrangHttpMethodsTestCase.test_not_accepted_request_shipping_cfg_PUT Apr 26 04:44:38 192.168.122.209 [45628.796824] [tdb] Start Tempesta DB Apr 26 04:44:38 192.168.122.209 [45628.933097] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:44:39 192.168.122.209 [45629.680553] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45629.680553] Maybe that's fine, but it's worth checking the [45629.680553] config - if there is no relations between the [45629.680553] names, then host name confusion attack is possible. Apr 26 04:44:39 192.168.122.209 [45629.787370] [tempesta fw] Configuration processing is completed. Apr 26 04:44:39 192.168.122.209 [45629.842001] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:44:39 192.168.122.209 [45629.869474] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:44:39 192.168.122.209 [45629.904331] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:44:39 192.168.122.209 [45629.947287] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:44:39 192.168.122.209 [45629.948304] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:44:39 192.168.122.209 [45629.949294] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:44:39 192.168.122.209 [45629.995299] [tempesta fw] Tempesta FW is ready Apr 26 04:44:39 192.168.122.209 [45630.134602] [tempesta fw] Warning: frang: restricted HTTP method for 127.0.0.2: 13 (0x2000u) Apr 26 04:44:39 192.168.122.209 [45630.135384] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:44:40 192.168.122.209 [45630.638434] [tdb] Close table 'client0.tdb' Apr 26 04:44:40 192.168.122.209 [45630.846928] [tdb] Close table 'sessions0.tdb' Apr 26 04:44:40 192.168.122.209 [45631.075561] [tdb] Close table 'filter0.tdb' Apr 26 04:44:40 192.168.122.209 [45631.075998] [tempesta fw] modules are stopped Apr 26 04:44:40 192.168.122.209 [45631.301748] [tempesta fw] exiting... Apr 26 04:44:41 192.168.122.209 [45631.435223] [tdb] Shutdown Tempesta DB Apr 26 04:44:41 192.168.122.209 [45631.637321] End test: t_frang.test_http_methods.FrangHttpMethodsTestCase.test_not_accepted_request_shipping_cfg_PUT Apr 26 04:44:41 192.168.122.209 [45631.648377] Start test: t_frang.test_http_methods.FrangHttpMethodsTestCase.test_not_accepted_request_shipping_cfg_TRACE Apr 26 04:44:42 192.168.122.209 [45632.746976] [tdb] Start Tempesta DB Apr 26 04:44:42 192.168.122.209 [45632.876080] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:44:43 192.168.122.209 [45633.552635] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45633.552635] Maybe that's fine, but it's worth checking the [45633.552635] config - if there is no relations between the [45633.552635] names, then host name confusion attack is possible. Apr 26 04:44:43 192.168.122.209 [45633.651423] [tempesta fw] Configuration processing is completed. Apr 26 04:44:43 192.168.122.209 [45633.701968] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:44:43 192.168.122.209 [45633.731842] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:44:43 192.168.122.209 [45633.759290] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:44:43 192.168.122.209 [45633.811409] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:44:43 192.168.122.209 [45633.813084] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:44:43 192.168.122.209 [45633.814737] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:44:43 192.168.122.209 [45633.851349] [tempesta fw] Tempesta FW is ready Apr 26 04:44:43 192.168.122.209 [45633.976488] [tempesta fw] Warning: frang: restricted HTTP method for 127.0.0.2: 14 (0x4000u) Apr 26 04:44:43 192.168.122.209 [45633.977964] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:44:44 192.168.122.209 [45634.431844] [tdb] Close table 'client0.tdb' Apr 26 04:44:44 192.168.122.209 [45634.629890] [tdb] Close table 'sessions0.tdb' Apr 26 04:44:44 192.168.122.209 [45634.854497] [tdb] Close table 'filter0.tdb' Apr 26 04:44:44 192.168.122.209 [45634.854930] [tempesta fw] modules are stopped Apr 26 04:44:44 192.168.122.209 [45635.052010] [tempesta fw] exiting... Apr 26 04:44:44 192.168.122.209 [45635.176053] [tdb] Shutdown Tempesta DB Apr 26 04:44:44 192.168.122.209 [45635.363770] End test: t_frang.test_http_methods.FrangHttpMethodsTestCase.test_not_accepted_request_shipping_cfg_TRACE Apr 26 04:44:45 192.168.122.209 [45635.390348] Start test: t_frang.test_http_methods.FrangHttpMethodsTestCase.test_not_accepted_request_with_unknown_method Apr 26 04:44:46 192.168.122.209 [45636.553963] [tdb] Start Tempesta DB Apr 26 04:44:46 192.168.122.209 [45636.684977] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:44:47 192.168.122.209 [45637.432697] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45637.432697] Maybe that's fine, but it's worth checking the [45637.432697] config - if there is no relations between the [45637.432697] names, then host name confusion attack is possible. Apr 26 04:44:47 192.168.122.209 [45637.539483] [tempesta fw] Configuration processing is completed. Apr 26 04:44:47 192.168.122.209 [45637.590706] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:44:47 192.168.122.209 [45637.618120] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:44:47 192.168.122.209 [45637.644483] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:44:47 192.168.122.209 [45637.691461] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:44:47 192.168.122.209 [45637.693143] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:44:47 192.168.122.209 [45637.694785] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:44:47 192.168.122.209 [45637.731434] [tempesta fw] Tempesta FW is ready Apr 26 04:44:47 192.168.122.209 [45637.871973] [tempesta fw] Warning: frang: restricted HTTP method for 127.0.0.2: 17 (0x20000u) Apr 26 04:44:47 192.168.122.209 [45637.874328] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:44:48 192.168.122.209 [45638.389150] [tdb] Close table 'client0.tdb' Apr 26 04:44:48 192.168.122.209 [45638.578731] [tdb] Close table 'sessions0.tdb' Apr 26 04:44:48 192.168.122.209 [45638.807023] [tdb] Close table 'filter0.tdb' Apr 26 04:44:48 192.168.122.209 [45638.807499] [tempesta fw] modules are stopped Apr 26 04:44:48 192.168.122.209 [45639.000682] [tempesta fw] exiting... Apr 26 04:44:48 192.168.122.209 [45639.117975] [tdb] Shutdown Tempesta DB Apr 26 04:44:48 192.168.122.209 [45639.327177] End test: t_frang.test_http_methods.FrangHttpMethodsTestCase.test_not_accepted_request_with_unknown_method Apr 26 04:44:48 192.168.122.209 [45639.343774] Start test: t_frang.test_http_resp_code_block.HttpRespCodeBlock.test_two_clients_one_ip Apr 26 04:44:50 192.168.122.209 [45640.771214] [tdb] Start Tempesta DB Apr 26 04:44:50 192.168.122.209 [45640.894718] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:44:51 192.168.122.209 [45641.463654] [tempesta fw] Configuration processing is completed. Apr 26 04:44:51 192.168.122.209 [45641.527569] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:44:51 192.168.122.209 [45642.158154] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:44:51 192.168.122.209 [45642.200701] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:44:51 192.168.122.209 [45642.244075] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:44:51 192.168.122.209 [45642.311522] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:44:51 192.168.122.209 [45642.351469] [tempesta fw] Tempesta FW is ready Apr 26 04:44:53 192.168.122.209 [45643.491138] [tempesta fw] Warning: frang: http_resp_code_block limit exceeded for 127.0.0.2: 6 (lim=5) Apr 26 04:44:53 192.168.122.209 [45643.493756] [tempesta fw] Warning: response blocked: filtered out: 127.0.0.2 Apr 26 04:44:53 192.168.122.209 [45643.495770] [tempesta fw] Warning: block client: 127.0.0.2 Apr 26 04:44:53 192.168.122.209 [45644.035386] [tdb] Close table 'client0.tdb' Apr 26 04:44:53 192.168.122.209 [45644.226695] [tdb] Close table 'sessions0.tdb' Apr 26 04:44:57 192.168.122.209 [45647.443117] [tdb] Close table 'cache0.tdb' Apr 26 04:44:57 192.168.122.209 [45647.678918] [tdb] Close table 'filter0.tdb' Apr 26 04:44:57 192.168.122.209 [45647.679397] [tempesta fw] modules are stopped Apr 26 04:44:57 192.168.122.209 [45647.858215] [tempesta fw] exiting... Apr 26 04:44:57 192.168.122.209 [45647.969693] [tdb] Shutdown Tempesta DB Apr 26 04:44:57 192.168.122.209 [45648.252245] End test: t_frang.test_http_resp_code_block.HttpRespCodeBlock.test_two_clients_one_ip Apr 26 04:44:57 192.168.122.209 [45648.264305] Start test: t_frang.test_http_resp_code_block.HttpRespCodeBlock.test_two_clients_two_ip Apr 26 04:44:59 192.168.122.209 [45649.554530] [tdb] Start Tempesta DB Apr 26 04:44:59 192.168.122.209 [45649.693088] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:45:00 192.168.122.209 [45650.959990] [tempesta fw] Configuration processing is completed. Apr 26 04:45:00 192.168.122.209 [45651.018873] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:45:01 192.168.122.209 [45651.463920] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:45:01 192.168.122.209 [45651.491669] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:45:01 192.168.122.209 [45651.519215] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:45:01 192.168.122.209 [45651.599654] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:45:01 192.168.122.209 [45651.643593] [tempesta fw] Tempesta FW is ready Apr 26 04:45:03 192.168.122.209 [45653.495815] [tempesta fw] Warning: frang: http_resp_code_block limit exceeded for 192.168.123.2: 6 (lim=5) Apr 26 04:45:03 192.168.122.209 [45653.496751] [tempesta fw] Warning: response blocked: filtered out: 192.168.123.2 Apr 26 04:45:03 192.168.122.209 [45653.497444] [tempesta fw] Warning: block client: 192.168.123.2 Apr 26 04:45:05 192.168.122.209 [45656.173756] [tdb] Close table 'client0.tdb' Apr 26 04:45:05 192.168.122.209 [45656.356050] [tdb] Close table 'sessions0.tdb' Apr 26 04:45:09 192.168.122.209 [45659.556684] [tdb] Close table 'cache0.tdb' Apr 26 04:45:09 192.168.122.209 [45659.813249] [tdb] Close table 'filter0.tdb' Apr 26 04:45:09 192.168.122.209 [45659.813693] [tempesta fw] modules are stopped Apr 26 04:45:09 192.168.122.209 [45659.984177] [tempesta fw] exiting... Apr 26 04:45:09 192.168.122.209 [45660.155821] [tdb] Shutdown Tempesta DB Apr 26 04:45:10 192.168.122.209 [45660.453505] End test: t_frang.test_http_resp_code_block.HttpRespCodeBlock.test_two_clients_two_ip Apr 26 04:45:10 192.168.122.209 [45660.464629] Start test: t_frang.test_http_resp_code_block.HttpRespCodeBlockH2.test_two_clients_one_ip Apr 26 04:45:11 192.168.122.209 [45661.835290] [tdb] Start Tempesta DB Apr 26 04:45:11 192.168.122.209 [45661.984843] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:45:13 192.168.122.209 [45663.377108] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45663.377108] Maybe that's fine, but it's worth checking the [45663.377108] config - if there is no relations between the [45663.377108] names, then host name confusion attack is possible. Apr 26 04:45:13 192.168.122.209 [45663.475807] [tempesta fw] Configuration processing is completed. Apr 26 04:45:13 192.168.122.209 [45663.527094] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:45:13 192.168.122.209 [45663.955055] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:45:13 192.168.122.209 [45664.021667] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:45:13 192.168.122.209 [45664.050707] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:45:13 192.168.122.209 [45664.143828] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:45:13 192.168.122.209 [45664.183756] [tempesta fw] Tempesta FW is ready Apr 26 04:45:14 192.168.122.209 [45665.349503] [tempesta fw] Warning: frang: http_resp_code_block limit exceeded for 127.0.0.2: 6 (lim=5) Apr 26 04:45:14 192.168.122.209 [45665.350359] [tempesta fw] Warning: response blocked: filtered out: 127.0.0.2 Apr 26 04:45:14 192.168.122.209 [45665.351016] [tempesta fw] Warning: block client: 127.0.0.2 Apr 26 04:45:15 192.168.122.209 [45665.872753] [tdb] Close table 'client0.tdb' Apr 26 04:45:15 192.168.122.209 [45666.074634] [tdb] Close table 'sessions0.tdb' Apr 26 04:45:18 192.168.122.209 [45669.357381] [tdb] Close table 'cache0.tdb' Apr 26 04:45:19 192.168.122.209 [45669.612699] [tdb] Close table 'filter0.tdb' Apr 26 04:45:19 192.168.122.209 [45669.613144] [tempesta fw] modules are stopped Apr 26 04:45:19 192.168.122.209 [45669.821873] [tempesta fw] exiting... Apr 26 04:45:19 192.168.122.209 [45669.953081] [tdb] Shutdown Tempesta DB Apr 26 04:45:19 192.168.122.209 [45670.247681] End test: t_frang.test_http_resp_code_block.HttpRespCodeBlockH2.test_two_clients_one_ip Apr 26 04:45:19 192.168.122.209 [45670.260189] Start test: t_frang.test_http_resp_code_block.HttpRespCodeBlockH2.test_two_clients_two_ip Apr 26 04:45:21 192.168.122.209 [45671.603361] [tdb] Start Tempesta DB Apr 26 04:45:21 192.168.122.209 [45671.773976] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:45:22 192.168.122.209 [45673.229248] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45673.229248] Maybe that's fine, but it's worth checking the [45673.229248] config - if there is no relations between the [45673.229248] names, then host name confusion attack is possible. Apr 26 04:45:22 192.168.122.209 [45673.327939] [tempesta fw] Configuration processing is completed. Apr 26 04:45:22 192.168.122.209 [45673.378482] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:45:23 192.168.122.209 [45673.818484] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:45:23 192.168.122.209 [45673.844122] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:45:23 192.168.122.209 [45673.870844] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:45:23 192.168.122.209 [45673.939942] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:45:23 192.168.122.209 [45673.979864] [tempesta fw] Tempesta FW is ready Apr 26 04:45:25 192.168.122.209 [45675.817247] [tempesta fw] Warning: frang: http_resp_code_block limit exceeded for 192.168.123.2: 6 (lim=5) Apr 26 04:45:25 192.168.122.209 [45675.819949] [tempesta fw] Warning: response blocked: filtered out: 192.168.123.2 Apr 26 04:45:25 192.168.122.209 [45675.821984] [tempesta fw] Warning: block client: 192.168.123.2 Apr 26 04:45:28 192.168.122.209 [45678.506130] [tdb] Close table 'client0.tdb' Apr 26 04:45:28 192.168.122.209 [45678.722825] [tdb] Close table 'sessions0.tdb' Apr 26 04:45:31 192.168.122.209 [45681.989332] [tdb] Close table 'cache0.tdb' Apr 26 04:45:31 192.168.122.209 [45682.230098] [tdb] Close table 'filter0.tdb' Apr 26 04:45:31 192.168.122.209 [45682.230520] [tempesta fw] modules are stopped Apr 26 04:45:32 192.168.122.209 [45682.435694] [tempesta fw] exiting... Apr 26 04:45:32 192.168.122.209 [45682.567865] [tdb] Shutdown Tempesta DB Apr 26 04:45:32 192.168.122.209 [45682.854197] End test: t_frang.test_http_resp_code_block.HttpRespCodeBlockH2.test_two_clients_two_ip Apr 26 04:45:32 192.168.122.209 [45682.867670] Start test: t_frang.test_http_resp_code_block.HttpRespCodeBlockOneClientH2.test_not_reaching_the_limit Apr 26 04:45:33 192.168.122.209 [45684.185366] [tdb] Start Tempesta DB Apr 26 04:45:33 192.168.122.209 [45684.334066] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:45:35 192.168.122.209 [45685.905438] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45685.905438] Maybe that's fine, but it's worth checking the [45685.905438] config - if there is no relations between the [45685.905438] names, then host name confusion attack is possible. Apr 26 04:45:35 192.168.122.209 [45686.004097] [tempesta fw] Configuration processing is completed. Apr 26 04:45:35 192.168.122.209 [45686.056583] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:45:35 192.168.122.209 [45686.085581] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:45:35 192.168.122.209 [45686.113236] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:45:35 192.168.122.209 [45686.180118] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:45:35 192.168.122.209 [45686.181890] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:45:35 192.168.122.209 [45686.183536] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:45:35 192.168.122.209 [45686.219998] [tempesta fw] Tempesta FW is ready Apr 26 04:45:38 192.168.122.209 [45689.179995] [tdb] Close table 'client0.tdb' Apr 26 04:45:39 192.168.122.209 [45689.393624] [tdb] Close table 'sessions0.tdb' Apr 26 04:45:39 192.168.122.209 [45689.628696] [tdb] Close table 'filter0.tdb' Apr 26 04:45:39 192.168.122.209 [45689.629139] [tempesta fw] modules are stopped Apr 26 04:45:39 192.168.122.209 [45689.880506] [tempesta fw] exiting... Apr 26 04:45:39 192.168.122.209 [45690.049579] [tdb] Shutdown Tempesta DB Apr 26 04:45:39 192.168.122.209 [45690.282223] End test: t_frang.test_http_resp_code_block.HttpRespCodeBlockOneClientH2.test_not_reaching_the_limit Apr 26 04:45:39 192.168.122.209 [45690.292714] Start test: t_frang.test_http_resp_code_block.HttpRespCodeBlockOneClientH2.test_reaching_the_limit Apr 26 04:45:41 192.168.122.209 [45691.625632] [tdb] Start Tempesta DB Apr 26 04:45:41 192.168.122.209 [45691.767624] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:45:42 192.168.122.209 [45692.541419] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45692.541419] Maybe that's fine, but it's worth checking the [45692.541419] config - if there is no relations between the [45692.541419] names, then host name confusion attack is possible. Apr 26 04:45:42 192.168.122.209 [45692.644163] [tempesta fw] Configuration processing is completed. Apr 26 04:45:42 192.168.122.209 [45692.695388] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:45:42 192.168.122.209 [45692.723421] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:45:42 192.168.122.209 [45692.752658] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:45:42 192.168.122.209 [45692.832146] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:45:42 192.168.122.209 [45692.833917] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:45:42 192.168.122.209 [45692.835579] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:45:42 192.168.122.209 [45692.884107] [tempesta fw] Tempesta FW is ready Apr 26 04:45:42 192.168.122.209 [45693.023213] [tempesta fw] Warning: frang: http_resp_code_block limit exceeded for 127.0.0.2: 7 (lim=6) Apr 26 04:45:42 192.168.122.209 [45693.025805] [tempesta fw] Warning: response blocked: filtered out: 127.0.0.2 Apr 26 04:45:43 192.168.122.209 [45693.515778] [tdb] Close table 'client0.tdb' Apr 26 04:45:43 192.168.122.209 [45693.729265] [tdb] Close table 'sessions0.tdb' Apr 26 04:45:43 192.168.122.209 [45693.956509] [tdb] Close table 'filter0.tdb' Apr 26 04:45:43 192.168.122.209 [45693.956948] [tempesta fw] modules are stopped Apr 26 04:45:43 192.168.122.209 [45694.170698] [tempesta fw] exiting... Apr 26 04:45:43 192.168.122.209 [45694.277966] [tdb] Shutdown Tempesta DB Apr 26 04:45:44 192.168.122.209 [45694.494523] End test: t_frang.test_http_resp_code_block.HttpRespCodeBlockOneClientH2.test_reaching_the_limit Apr 26 04:45:44 192.168.122.209 [45694.510105] Start test: t_frang.test_http_resp_code_block.HttpRespCodeBlockOneClientH2.test_reaching_the_limit_2 Apr 26 04:45:45 192.168.122.209 [45695.761779] [tdb] Start Tempesta DB Apr 26 04:45:45 192.168.122.209 [45695.901682] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:45:46 192.168.122.209 [45696.644928] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45696.644928] Maybe that's fine, but it's worth checking the [45696.644928] config - if there is no relations between the [45696.644928] names, then host name confusion attack is possible. Apr 26 04:45:46 192.168.122.209 [45696.752284] [tempesta fw] Configuration processing is completed. Apr 26 04:45:46 192.168.122.209 [45696.815426] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:45:46 192.168.122.209 [45696.845512] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:45:46 192.168.122.209 [45696.881657] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:45:46 192.168.122.209 [45696.964203] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:45:46 192.168.122.209 [45696.965878] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:45:46 192.168.122.209 [45696.967522] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:45:46 192.168.122.209 [45697.016165] [tempesta fw] Tempesta FW is ready Apr 26 04:45:46 192.168.122.209 [45697.173487] [tempesta fw] Warning: frang: http_resp_code_block limit exceeded for 127.0.0.2: 6 (lim=5) Apr 26 04:45:46 192.168.122.209 [45697.174352] [tempesta fw] Warning: response blocked: filtered out: 127.0.0.2 Apr 26 04:45:47 192.168.122.209 [45697.662323] [tdb] Close table 'client0.tdb' Apr 26 04:45:47 192.168.122.209 [45697.845193] [tdb] Close table 'sessions0.tdb' Apr 26 04:45:47 192.168.122.209 [45698.082099] [tdb] Close table 'filter0.tdb' Apr 26 04:45:47 192.168.122.209 [45698.082552] [tempesta fw] modules are stopped Apr 26 04:45:47 192.168.122.209 [45698.277683] [tempesta fw] exiting... Apr 26 04:45:48 192.168.122.209 [45698.388699] [tdb] Shutdown Tempesta DB Apr 26 04:45:48 192.168.122.209 [45698.617322] End test: t_frang.test_http_resp_code_block.HttpRespCodeBlockOneClientH2.test_reaching_the_limit_2 Apr 26 04:45:48 192.168.122.209 [45698.639965] Start test: t_frang.test_http_resp_code_block.HttpRespCodeBlockOneClientHttp.test_not_reaching_the_limit Apr 26 04:45:49 192.168.122.209 [45699.890986] [tdb] Start Tempesta DB Apr 26 04:45:49 192.168.122.209 [45700.026732] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:45:50 192.168.122.209 [45700.813567] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45700.813567] Maybe that's fine, but it's worth checking the [45700.813567] config - if there is no relations between the [45700.813567] names, then host name confusion attack is possible. Apr 26 04:45:50 192.168.122.209 [45700.912214] [tempesta fw] Configuration processing is completed. Apr 26 04:45:50 192.168.122.209 [45700.962853] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:45:50 192.168.122.209 [45700.990817] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:45:50 192.168.122.209 [45701.017827] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:45:50 192.168.122.209 [45701.092204] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:45:50 192.168.122.209 [45701.093897] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:45:50 192.168.122.209 [45701.095544] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:45:50 192.168.122.209 [45701.132208] [tempesta fw] Tempesta FW is ready Apr 26 04:45:53 192.168.122.209 [45703.997267] [tdb] Close table 'client0.tdb' Apr 26 04:45:53 192.168.122.209 [45704.207031] [tdb] Close table 'sessions0.tdb' Apr 26 04:45:54 192.168.122.209 [45704.436638] [tdb] Close table 'filter0.tdb' Apr 26 04:45:54 192.168.122.209 [45704.437072] [tempesta fw] modules are stopped Apr 26 04:45:54 192.168.122.209 [45704.633528] [tempesta fw] exiting... Apr 26 04:45:54 192.168.122.209 [45704.789090] [tdb] Shutdown Tempesta DB Apr 26 04:45:54 192.168.122.209 [45704.982448] End test: t_frang.test_http_resp_code_block.HttpRespCodeBlockOneClientHttp.test_not_reaching_the_limit Apr 26 04:45:54 192.168.122.209 [45704.996781] Start test: t_frang.test_http_resp_code_block.HttpRespCodeBlockOneClientHttp.test_reaching_the_limit Apr 26 04:45:55 192.168.122.209 [45706.283586] [tdb] Start Tempesta DB Apr 26 04:45:56 192.168.122.209 [45706.418365] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:45:56 192.168.122.209 [45707.149546] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45707.149546] Maybe that's fine, but it's worth checking the [45707.149546] config - if there is no relations between the [45707.149546] names, then host name confusion attack is possible. Apr 26 04:45:56 192.168.122.209 [45707.252356] [tempesta fw] Configuration processing is completed. Apr 26 04:45:56 192.168.122.209 [45707.304286] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:45:56 192.168.122.209 [45707.333601] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:45:56 192.168.122.209 [45707.359616] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:45:57 192.168.122.209 [45707.436332] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:45:57 192.168.122.209 [45707.438036] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:45:57 192.168.122.209 [45707.439737] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:45:57 192.168.122.209 [45707.480285] [tempesta fw] Tempesta FW is ready Apr 26 04:45:57 192.168.122.209 [45707.633779] [tempesta fw] Warning: frang: http_resp_code_block limit exceeded for 127.0.0.2: 7 (lim=6) Apr 26 04:45:57 192.168.122.209 [45707.634803] [tempesta fw] Warning: response blocked: filtered out: 127.0.0.2 Apr 26 04:45:57 192.168.122.209 [45708.199316] [tdb] Close table 'client0.tdb' Apr 26 04:45:58 192.168.122.209 [45708.394416] [tdb] Close table 'sessions0.tdb' Apr 26 04:45:58 192.168.122.209 [45708.617847] [tdb] Close table 'filter0.tdb' Apr 26 04:45:58 192.168.122.209 [45708.618298] [tempesta fw] modules are stopped Apr 26 04:45:58 192.168.122.209 [45708.807726] [tempesta fw] exiting... Apr 26 04:45:58 192.168.122.209 [45708.920665] [tdb] Shutdown Tempesta DB Apr 26 04:45:58 192.168.122.209 [45709.123429] End test: t_frang.test_http_resp_code_block.HttpRespCodeBlockOneClientHttp.test_reaching_the_limit Apr 26 04:45:58 192.168.122.209 [45709.135649] Start test: t_frang.test_http_resp_code_block.HttpRespCodeBlockOneClientHttp.test_reaching_the_limit_2 Apr 26 04:46:00 192.168.122.209 [45710.414827] [tdb] Start Tempesta DB Apr 26 04:46:00 192.168.122.209 [45710.559865] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:46:00 192.168.122.209 [45711.297680] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45711.297680] Maybe that's fine, but it's worth checking the [45711.297680] config - if there is no relations between the [45711.297680] names, then host name confusion attack is possible. Apr 26 04:46:01 192.168.122.209 [45711.404453] [tempesta fw] Configuration processing is completed. Apr 26 04:46:01 192.168.122.209 [45711.470997] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:46:01 192.168.122.209 [45711.499117] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:46:01 192.168.122.209 [45711.526152] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:46:01 192.168.122.209 [45711.604722] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:46:01 192.168.122.209 [45711.606410] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:46:01 192.168.122.209 [45711.608076] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:46:01 192.168.122.209 [45711.648328] [tempesta fw] Tempesta FW is ready Apr 26 04:46:01 192.168.122.209 [45711.805397] [tempesta fw] Warning: frang: http_resp_code_block limit exceeded for 127.0.0.2: 6 (lim=5) Apr 26 04:46:01 192.168.122.209 [45711.806256] [tempesta fw] Warning: response blocked: filtered out: 127.0.0.2 Apr 26 04:46:01 192.168.122.209 [45712.320149] [tdb] Close table 'client0.tdb' Apr 26 04:46:02 192.168.122.209 [45712.513298] [tdb] Close table 'sessions0.tdb' Apr 26 04:46:02 192.168.122.209 [45712.746387] [tdb] Close table 'filter0.tdb' Apr 26 04:46:02 192.168.122.209 [45712.746820] [tempesta fw] modules are stopped Apr 26 04:46:02 192.168.122.209 [45712.928284] [tempesta fw] exiting... Apr 26 04:46:02 192.168.122.209 [45713.047806] [tdb] Shutdown Tempesta DB Apr 26 04:46:02 192.168.122.209 [45713.265187] End test: t_frang.test_http_resp_code_block.HttpRespCodeBlockOneClientHttp.test_reaching_the_limit_2 Apr 26 04:46:02 192.168.122.209 [45713.285049] Start test: t_frang.test_http_strict_host_checking.FrangHostRequiredH2TestCase.test_auto_port_mismatch Apr 26 04:46:04 192.168.122.209 [45714.413671] [tdb] Start Tempesta DB Apr 26 04:46:04 192.168.122.209 [45714.553206] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:46:04 192.168.122.209 [45715.345679] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45715.345679] Maybe that's fine, but it's worth checking the [45715.345679] config - if there is no relations between the [45715.345679] names, then host name confusion attack is possible. Apr 26 04:46:05 192.168.122.209 [45715.488719] [tempesta fw] Configuration processing is completed. Apr 26 04:46:05 192.168.122.209 [45715.538860] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:46:05 192.168.122.209 [45715.566353] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:46:05 192.168.122.209 [45715.592687] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:46:05 192.168.122.209 [45715.644456] [tempesta fw] Open listen socket on: 0.0.0.0:444 Apr 26 04:46:05 192.168.122.209 [45715.646018] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:46:05 192.168.122.209 [45715.684408] [tempesta fw] Tempesta FW is ready Apr 26 04:46:05 192.168.122.209 [45715.815667] [tempesta fw] Warning: frang: port from host header doesn't match real port for 127.0.0.2: 443 (444) Apr 26 04:46:05 192.168.122.209 [45715.818196] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:46:05 192.168.122.209 [45716.334186] [tdb] Close table 'client0.tdb' Apr 26 04:46:06 192.168.122.209 [45716.523405] [tdb] Close table 'sessions0.tdb' Apr 26 04:46:06 192.168.122.209 [45716.762457] [tdb] Close table 'filter0.tdb' Apr 26 04:46:06 192.168.122.209 [45716.762898] [tempesta fw] modules are stopped Apr 26 04:46:06 192.168.122.209 [45716.985342] [tempesta fw] exiting... Apr 26 04:46:06 192.168.122.209 [45717.093744] [tdb] Shutdown Tempesta DB Apr 26 04:46:06 192.168.122.209 [45717.289662] End test: t_frang.test_http_strict_host_checking.FrangHostRequiredH2TestCase.test_auto_port_mismatch Apr 26 04:46:06 192.168.122.209 [45717.302471] Start test: t_frang.test_http_strict_host_checking.FrangHostRequiredH2TestCase.test_disabled_host_http_required Apr 26 04:46:08 192.168.122.209 [45718.456822] [tdb] Start Tempesta DB Apr 26 04:46:08 192.168.122.209 [45718.582172] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:46:09 192.168.122.209 [45719.834048] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45719.834048] Maybe that's fine, but it's worth checking the [45719.834048] config - if there is no relations between the [45719.834048] names, then host name confusion attack is possible. Apr 26 04:46:10 192.168.122.209 [45720.888514] [tempesta fw] Configuration processing is completed. Apr 26 04:46:10 192.168.122.209 [45721.031957] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:46:10 192.168.122.209 [45721.060192] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:46:10 192.168.122.209 [45721.086972] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:46:11 192.168.122.209 [45721.440605] [tempesta fw] Open listen socket on: 0.0.0.0:444 Apr 26 04:46:11 192.168.122.209 [45721.442311] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:46:11 192.168.122.209 [45721.740427] [tempesta fw] Tempesta FW is ready Apr 26 04:46:13 192.168.122.209 [45723.451052] [tdb] Close table 'client0.tdb' Apr 26 04:46:13 192.168.122.209 [45723.894111] [tdb] Close table 'sessions0.tdb' Apr 26 04:46:14 192.168.122.209 [45724.478601] [tdb] Close table 'filter0.tdb' Apr 26 04:46:14 192.168.122.209 [45724.479046] [tempesta fw] modules are stopped Apr 26 04:46:14 192.168.122.209 [45725.029123] [tempesta fw] exiting... Apr 26 04:46:14 192.168.122.209 [45725.169441] [tdb] Shutdown Tempesta DB Apr 26 04:46:15 192.168.122.209 [45725.387121] End test: t_frang.test_http_strict_host_checking.FrangHostRequiredH2TestCase.test_disabled_host_http_required Apr 26 04:46:15 192.168.122.209 [45725.401052] Start test: t_frang.test_http_strict_host_checking.FrangHostRequiredH2TestCase.test_h2_authority_header_as_ip Apr 26 04:46:16 192.168.122.209 [45726.593303] [tdb] Start Tempesta DB Apr 26 04:46:16 192.168.122.209 [45726.735667] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:46:17 192.168.122.209 [45727.501885] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45727.501885] Maybe that's fine, but it's worth checking the [45727.501885] config - if there is no relations between the [45727.501885] names, then host name confusion attack is possible. Apr 26 04:46:17 192.168.122.209 [45727.648554] [tempesta fw] Configuration processing is completed. Apr 26 04:46:17 192.168.122.209 [45727.704354] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:46:17 192.168.122.209 [45727.733790] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:46:17 192.168.122.209 [45727.760732] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:46:17 192.168.122.209 [45727.804560] [tempesta fw] Open listen socket on: 0.0.0.0:444 Apr 26 04:46:17 192.168.122.209 [45727.805930] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:46:17 192.168.122.209 [45727.844557] [tempesta fw] Tempesta FW is ready Apr 26 04:46:17 192.168.122.209 [45727.973270] [tempesta fw] Warning: frang: Host header field contains IP address for 127.0.0.2 Apr 26 04:46:17 192.168.122.209 [45727.974594] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:46:18 192.168.122.209 [45728.518759] [tdb] Close table 'client0.tdb' Apr 26 04:46:18 192.168.122.209 [45728.705269] [tdb] Close table 'sessions0.tdb' Apr 26 04:46:18 192.168.122.209 [45728.944878] [tdb] Close table 'filter0.tdb' Apr 26 04:46:18 192.168.122.209 [45728.945314] [tempesta fw] modules are stopped Apr 26 04:46:18 192.168.122.209 [45729.177888] [tempesta fw] exiting... Apr 26 04:46:18 192.168.122.209 [45729.289248] [tdb] Shutdown Tempesta DB Apr 26 04:46:19 192.168.122.209 [45729.482641] End test: t_frang.test_http_strict_host_checking.FrangHostRequiredH2TestCase.test_h2_authority_header_as_ip Apr 26 04:46:19 192.168.122.209 [45729.496780] Start test: t_frang.test_http_strict_host_checking.FrangHostRequiredH2TestCase.test_h2_authority_header_as_ipv6 Apr 26 04:46:20 192.168.122.209 [45730.693167] [tdb] Start Tempesta DB Apr 26 04:46:20 192.168.122.209 [45730.819641] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:46:21 192.168.122.209 [45731.605247] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45731.605247] Maybe that's fine, but it's worth checking the [45731.605247] config - if there is no relations between the [45731.605247] names, then host name confusion attack is possible. Apr 26 04:46:21 192.168.122.209 [45731.724607] [tempesta fw] Configuration processing is completed. Apr 26 04:46:21 192.168.122.209 [45731.771567] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:46:21 192.168.122.209 [45731.803322] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:46:21 192.168.122.209 [45731.833274] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:46:21 192.168.122.209 [45731.872655] [tempesta fw] Open listen socket on: 0.0.0.0:444 Apr 26 04:46:21 192.168.122.209 [45731.873733] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:46:21 192.168.122.209 [45731.912581] [tempesta fw] Tempesta FW is ready Apr 26 04:46:21 192.168.122.209 [45732.028318] [tempesta fw] Warning: frang: Host header field contains IP address for 127.0.0.2 Apr 26 04:46:21 192.168.122.209 [45732.029123] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:46:22 192.168.122.209 [45732.527889] [tdb] Close table 'client0.tdb' Apr 26 04:46:22 192.168.122.209 [45732.735269] [tdb] Close table 'sessions0.tdb' Apr 26 04:46:22 192.168.122.209 [45732.955088] [tdb] Close table 'filter0.tdb' Apr 26 04:46:22 192.168.122.209 [45732.955536] [tempesta fw] modules are stopped Apr 26 04:46:22 192.168.122.209 [45733.154216] [tempesta fw] exiting... Apr 26 04:46:22 192.168.122.209 [45733.305240] [tdb] Shutdown Tempesta DB Apr 26 04:46:23 192.168.122.209 [45733.507825] End test: t_frang.test_http_strict_host_checking.FrangHostRequiredH2TestCase.test_h2_authority_header_as_ipv6 Apr 26 04:46:23 192.168.122.209 [45733.519772] Start test: t_frang.test_http_strict_host_checking.FrangHostRequiredH2TestCase.test_h2_different_host_and_authority_header Apr 26 04:46:24 192.168.122.209 [45734.665170] [tdb] Start Tempesta DB Apr 26 04:46:24 192.168.122.209 [45734.797388] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:46:25 192.168.122.209 [45735.505933] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45735.505933] Maybe that's fine, but it's worth checking the [45735.505933] config - if there is no relations between the [45735.505933] names, then host name confusion attack is possible. Apr 26 04:46:25 192.168.122.209 [45735.640724] [tempesta fw] Configuration processing is completed. Apr 26 04:46:25 192.168.122.209 [45735.692162] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:46:25 192.168.122.209 [45735.721847] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:46:25 192.168.122.209 [45735.748478] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:46:25 192.168.122.209 [45735.788684] [tempesta fw] Open listen socket on: 0.0.0.0:444 Apr 26 04:46:25 192.168.122.209 [45735.790364] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:46:25 192.168.122.209 [45735.832633] [tempesta fw] Tempesta FW is ready Apr 26 04:46:25 192.168.122.209 [45735.971890] [tempesta fw] Warning: frang: Request :authority differs from Host for 127.0.0.2 Apr 26 04:46:25 192.168.122.209 [45735.972867] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:46:26 192.168.122.209 [45736.475237] [tdb] Close table 'client0.tdb' Apr 26 04:46:26 192.168.122.209 [45736.674416] [tdb] Close table 'sessions0.tdb' Apr 26 04:46:26 192.168.122.209 [45736.883234] [tdb] Close table 'filter0.tdb' Apr 26 04:46:26 192.168.122.209 [45736.883664] [tempesta fw] modules are stopped Apr 26 04:46:26 192.168.122.209 [45737.104585] [tempesta fw] exiting... Apr 26 04:46:26 192.168.122.209 [45737.253492] [tdb] Shutdown Tempesta DB Apr 26 04:46:27 192.168.122.209 [45737.431167] End test: t_frang.test_http_strict_host_checking.FrangHostRequiredH2TestCase.test_h2_different_host_and_authority_header Apr 26 04:46:27 192.168.122.209 [45737.444029] Start test: t_frang.test_http_strict_host_checking.FrangHostRequiredH2TestCase.test_h2_header_ok Apr 26 04:46:28 192.168.122.209 [45738.700027] [tdb] Start Tempesta DB Apr 26 04:46:28 192.168.122.209 [45738.830219] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:46:29 192.168.122.209 [45739.593959] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45739.593959] Maybe that's fine, but it's worth checking the [45739.593959] config - if there is no relations between the [45739.593959] names, then host name confusion attack is possible. Apr 26 04:46:29 192.168.122.209 [45739.748754] [tempesta fw] Configuration processing is completed. Apr 26 04:46:29 192.168.122.209 [45739.798546] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:46:29 192.168.122.209 [45739.825816] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:46:29 192.168.122.209 [45739.851984] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:46:29 192.168.122.209 [45739.884689] [tempesta fw] Open listen socket on: 0.0.0.0:444 Apr 26 04:46:29 192.168.122.209 [45739.885688] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:46:29 192.168.122.209 [45739.928724] [tempesta fw] Tempesta FW is ready Apr 26 04:46:30 192.168.122.209 [45740.655800] [tdb] Close table 'client0.tdb' Apr 26 04:46:30 192.168.122.209 [45740.848688] [tdb] Close table 'sessions0.tdb' Apr 26 04:46:30 192.168.122.209 [45741.090672] [tdb] Close table 'filter0.tdb' Apr 26 04:46:30 192.168.122.209 [45741.091142] [tempesta fw] modules are stopped Apr 26 04:46:30 192.168.122.209 [45741.265172] [tempesta fw] exiting... Apr 26 04:46:31 192.168.122.209 [45741.414822] [tdb] Shutdown Tempesta DB Apr 26 04:46:31 192.168.122.209 [45741.644860] End test: t_frang.test_http_strict_host_checking.FrangHostRequiredH2TestCase.test_h2_header_ok Apr 26 04:46:31 192.168.122.209 [45741.663555] Start test: t_frang.test_http_strict_host_checking.FrangHostRequiredH2TestCase.test_h2_host_header_as_ip Apr 26 04:46:32 192.168.122.209 [45742.896230] [tdb] Start Tempesta DB Apr 26 04:46:32 192.168.122.209 [45743.035170] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:46:33 192.168.122.209 [45743.790029] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45743.790029] Maybe that's fine, but it's worth checking the [45743.790029] config - if there is no relations between the [45743.790029] names, then host name confusion attack is possible. Apr 26 04:46:33 192.168.122.209 [45743.924772] [tempesta fw] Configuration processing is completed. Apr 26 04:46:33 192.168.122.209 [45743.975509] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:46:33 192.168.122.209 [45744.006163] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:46:33 192.168.122.209 [45744.032473] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:46:33 192.168.122.209 [45744.068801] [tempesta fw] Open listen socket on: 0.0.0.0:444 Apr 26 04:46:33 192.168.122.209 [45744.070493] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:46:33 192.168.122.209 [45744.112747] [tempesta fw] Tempesta FW is ready Apr 26 04:46:33 192.168.122.209 [45744.257650] [tempesta fw] Warning: frang: Host header field contains IP address for 127.0.0.2 Apr 26 04:46:33 192.168.122.209 [45744.259098] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:46:34 192.168.122.209 [45744.751338] [tdb] Close table 'client0.tdb' Apr 26 04:46:34 192.168.122.209 [45744.936820] [tdb] Close table 'sessions0.tdb' Apr 26 04:46:34 192.168.122.209 [45745.189056] [tdb] Close table 'filter0.tdb' Apr 26 04:46:34 192.168.122.209 [45745.189494] [tempesta fw] modules are stopped Apr 26 04:46:35 192.168.122.209 [45745.402395] [tempesta fw] exiting... Apr 26 04:46:35 192.168.122.209 [45745.539981] [tdb] Shutdown Tempesta DB Apr 26 04:46:35 192.168.122.209 [45745.762144] End test: t_frang.test_http_strict_host_checking.FrangHostRequiredH2TestCase.test_h2_host_header_as_ip Apr 26 04:46:35 192.168.122.209 [45745.775283] Start test: t_frang.test_http_strict_host_checking.FrangHostRequiredH2TestCase.test_h2_host_header_as_ipv6 Apr 26 04:46:36 192.168.122.209 [45747.019067] [tdb] Start Tempesta DB Apr 26 04:46:36 192.168.122.209 [45747.147799] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:46:37 192.168.122.209 [45747.938109] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45747.938109] Maybe that's fine, but it's worth checking the [45747.938109] config - if there is no relations between the [45747.938109] names, then host name confusion attack is possible. Apr 26 04:46:37 192.168.122.209 [45748.068878] [tempesta fw] Configuration processing is completed. Apr 26 04:46:37 192.168.122.209 [45748.121065] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:46:37 192.168.122.209 [45748.149281] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:46:37 192.168.122.209 [45748.176324] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:46:37 192.168.122.209 [45748.220825] [tempesta fw] Open listen socket on: 0.0.0.0:444 Apr 26 04:46:37 192.168.122.209 [45748.222126] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:46:37 192.168.122.209 [45748.260827] [tempesta fw] Tempesta FW is ready Apr 26 04:46:38 192.168.122.209 [45748.389339] [tempesta fw] Warning: frang: Host header field contains IP address for 127.0.0.2 Apr 26 04:46:38 192.168.122.209 [45748.391713] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:46:38 192.168.122.209 [45748.866254] [tdb] Close table 'client0.tdb' Apr 26 04:46:38 192.168.122.209 [45749.059660] [tdb] Close table 'sessions0.tdb' Apr 26 04:46:38 192.168.122.209 [45749.286771] [tdb] Close table 'filter0.tdb' Apr 26 04:46:38 192.168.122.209 [45749.287207] [tempesta fw] modules are stopped Apr 26 04:46:39 192.168.122.209 [45749.482787] [tempesta fw] exiting... Apr 26 04:46:39 192.168.122.209 [45749.636239] [tdb] Shutdown Tempesta DB Apr 26 04:46:39 192.168.122.209 [45749.833710] End test: t_frang.test_http_strict_host_checking.FrangHostRequiredH2TestCase.test_h2_host_header_as_ipv6 Apr 26 04:46:39 192.168.122.209 [45749.848984] Start test: t_frang.test_http_strict_host_checking.FrangHostRequiredTestCase.test_auto_port_mismatch Apr 26 04:46:40 192.168.122.209 [45751.072054] [tdb] Start Tempesta DB Apr 26 04:46:40 192.168.122.209 [45751.205593] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:46:41 192.168.122.209 [45751.962175] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45751.962175] Maybe that's fine, but it's worth checking the [45751.962175] config - if there is no relations between the [45751.962175] names, then host name confusion attack is possible. Apr 26 04:46:41 192.168.122.209 [45752.076953] [tempesta fw] Configuration processing is completed. Apr 26 04:46:41 192.168.122.209 [45752.130980] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:46:41 192.168.122.209 [45752.158521] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:46:41 192.168.122.209 [45752.185043] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:46:41 192.168.122.209 [45752.228828] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:46:41 192.168.122.209 [45752.230118] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:46:41 192.168.122.209 [45752.231432] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:46:41 192.168.122.209 [45752.276846] [tempesta fw] Tempesta FW is ready Apr 26 04:46:42 192.168.122.209 [45752.396478] [tempesta fw] Warning: frang: port from host header doesn't match real port for 127.0.0.2: 80 (81) Apr 26 04:46:42 192.168.122.209 [45752.398355] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:46:42 192.168.122.209 [45752.926330] [tdb] Close table 'client0.tdb' Apr 26 04:46:42 192.168.122.209 [45753.131456] [tdb] Close table 'sessions0.tdb' Apr 26 04:46:42 192.168.122.209 [45753.361564] [tdb] Close table 'filter0.tdb' Apr 26 04:46:42 192.168.122.209 [45753.362000] [tempesta fw] modules are stopped Apr 26 04:46:43 192.168.122.209 [45753.617107] [tempesta fw] exiting... Apr 26 04:46:43 192.168.122.209 [45753.742391] [tdb] Shutdown Tempesta DB Apr 26 04:46:43 192.168.122.209 [45753.932390] End test: t_frang.test_http_strict_host_checking.FrangHostRequiredTestCase.test_auto_port_mismatch Apr 26 04:46:43 192.168.122.209 [45753.947509] Start test: t_frang.test_http_strict_host_checking.FrangHostRequiredTestCase.test_auto_port_mismatch_uri Apr 26 04:46:44 192.168.122.209 [45755.131543] [tdb] Start Tempesta DB Apr 26 04:46:44 192.168.122.209 [45755.270109] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:46:45 192.168.122.209 [45756.018179] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45756.018179] Maybe that's fine, but it's worth checking the [45756.018179] config - if there is no relations between the [45756.018179] names, then host name confusion attack is possible. Apr 26 04:46:45 192.168.122.209 [45756.145362] [tempesta fw] Configuration processing is completed. Apr 26 04:46:45 192.168.122.209 [45756.196501] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:46:45 192.168.122.209 [45756.226405] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:46:45 192.168.122.209 [45756.253868] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:46:45 192.168.122.209 [45756.316989] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:46:45 192.168.122.209 [45756.319551] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:46:45 192.168.122.209 [45756.322183] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:46:45 192.168.122.209 [45756.352835] [tempesta fw] Tempesta FW is ready Apr 26 04:46:46 192.168.122.209 [45756.472673] [tempesta fw] Warning: frang: port from host header doesn't match real port for 127.0.0.2: 80 (81) Apr 26 04:46:46 192.168.122.209 [45756.474148] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:46:46 192.168.122.209 [45757.058940] [tdb] Close table 'client0.tdb' Apr 26 04:46:46 192.168.122.209 [45757.248707] [tdb] Close table 'sessions0.tdb' Apr 26 04:46:47 192.168.122.209 [45757.491112] [tdb] Close table 'filter0.tdb' Apr 26 04:46:47 192.168.122.209 [45757.491551] [tempesta fw] modules are stopped Apr 26 04:46:47 192.168.122.209 [45757.662697] [tempesta fw] exiting... Apr 26 04:46:47 192.168.122.209 [45757.774040] [tdb] Shutdown Tempesta DB Apr 26 04:46:47 192.168.122.209 [45757.985873] End test: t_frang.test_http_strict_host_checking.FrangHostRequiredTestCase.test_auto_port_mismatch_uri Apr 26 04:46:47 192.168.122.209 [45758.004345] Start test: t_frang.test_http_strict_host_checking.FrangHostRequiredTestCase.test_default_host_http_required Apr 26 04:46:48 192.168.122.209 [45759.145109] [tdb] Start Tempesta DB Apr 26 04:46:48 192.168.122.209 [45759.285277] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:46:49 192.168.122.209 [45760.034228] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45760.034228] Maybe that's fine, but it's worth checking the [45760.034228] config - if there is no relations between the [45760.034228] names, then host name confusion attack is possible. Apr 26 04:46:49 192.168.122.209 [45760.141013] [tempesta fw] Configuration processing is completed. Apr 26 04:46:49 192.168.122.209 [45760.191397] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:46:49 192.168.122.209 [45760.219967] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:46:49 192.168.122.209 [45760.246434] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:46:49 192.168.122.209 [45760.293011] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:46:49 192.168.122.209 [45760.294708] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:46:49 192.168.122.209 [45760.296354] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:46:49 192.168.122.209 [45760.336943] [tempesta fw] Tempesta FW is ready Apr 26 04:46:50 192.168.122.209 [45760.465723] [tempesta fw] Warning: frang: Host header field contains IP address for 127.0.0.2 Apr 26 04:46:50 192.168.122.209 [45760.468155] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:46:50 192.168.122.209 [45760.942716] [tdb] Close table 'client0.tdb' Apr 26 04:46:50 192.168.122.209 [45761.146687] [tdb] Close table 'sessions0.tdb' Apr 26 04:46:51 192.168.122.209 [45761.390766] [tdb] Close table 'filter0.tdb' Apr 26 04:46:51 192.168.122.209 [45761.391202] [tempesta fw] modules are stopped Apr 26 04:46:51 192.168.122.209 [45761.571296] [tempesta fw] exiting... Apr 26 04:46:51 192.168.122.209 [45761.699059] [tdb] Shutdown Tempesta DB Apr 26 04:46:51 192.168.122.209 [45761.922415] End test: t_frang.test_http_strict_host_checking.FrangHostRequiredTestCase.test_default_host_http_required Apr 26 04:46:51 192.168.122.209 [45761.933680] Start test: t_frang.test_http_strict_host_checking.FrangHostRequiredTestCase.test_disabled_host_http_required Apr 26 04:46:52 192.168.122.209 [45763.140281] [tdb] Start Tempesta DB Apr 26 04:46:52 192.168.122.209 [45763.280553] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:46:53 192.168.122.209 [45764.086317] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45764.086317] Maybe that's fine, but it's worth checking the [45764.086317] config - if there is no relations between the [45764.086317] names, then host name confusion attack is possible. Apr 26 04:46:53 192.168.122.209 [45764.189086] [tempesta fw] Configuration processing is completed. Apr 26 04:46:53 192.168.122.209 [45764.261206] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:46:53 192.168.122.209 [45764.291090] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:46:53 192.168.122.209 [45764.318559] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:46:53 192.168.122.209 [45764.361052] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:46:53 192.168.122.209 [45764.362746] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:46:53 192.168.122.209 [45764.364338] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:46:54 192.168.122.209 [45764.401004] [tempesta fw] Tempesta FW is ready Apr 26 04:46:54 192.168.122.209 [45765.035895] [tdb] Close table 'client0.tdb' Apr 26 04:46:54 192.168.122.209 [45765.234702] [tdb] Close table 'sessions0.tdb' Apr 26 04:46:55 192.168.122.209 [45765.466977] [tdb] Close table 'filter0.tdb' Apr 26 04:46:55 192.168.122.209 [45765.467410] [tempesta fw] modules are stopped Apr 26 04:46:55 192.168.122.209 [45765.644768] [tempesta fw] exiting... Apr 26 04:46:55 192.168.122.209 [45765.781919] [tdb] Shutdown Tempesta DB Apr 26 04:46:55 192.168.122.209 [45765.984764] End test: t_frang.test_http_strict_host_checking.FrangHostRequiredTestCase.test_disabled_host_http_required Apr 26 04:46:55 192.168.122.209 [45765.996675] Start test: t_frang.test_http_strict_host_checking.FrangHostRequiredTestCase.test_host_header_as_ip Apr 26 04:46:56 192.168.122.209 [45767.133061] [tdb] Start Tempesta DB Apr 26 04:46:56 192.168.122.209 [45767.257591] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:46:57 192.168.122.209 [45768.030348] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45768.030348] Maybe that's fine, but it's worth checking the [45768.030348] config - if there is no relations between the [45768.030348] names, then host name confusion attack is possible. Apr 26 04:46:57 192.168.122.209 [45768.153587] [tempesta fw] Configuration processing is completed. Apr 26 04:46:57 192.168.122.209 [45768.204911] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:46:57 192.168.122.209 [45768.231862] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:46:57 192.168.122.209 [45768.257733] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:46:57 192.168.122.209 [45768.309122] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:46:57 192.168.122.209 [45768.310820] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:46:57 192.168.122.209 [45768.312419] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:46:57 192.168.122.209 [45768.365043] [tempesta fw] Tempesta FW is ready Apr 26 04:46:58 192.168.122.209 [45768.482661] [tempesta fw] Warning: frang: Host header field contains IP address for 127.0.0.2 Apr 26 04:46:58 192.168.122.209 [45768.483795] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:46:58 192.168.122.209 [45769.030717] [tdb] Close table 'client0.tdb' Apr 26 04:46:58 192.168.122.209 [45769.214920] [tdb] Close table 'sessions0.tdb' Apr 26 04:46:59 192.168.122.209 [45769.454642] [tdb] Close table 'filter0.tdb' Apr 26 04:46:59 192.168.122.209 [45769.455070] [tempesta fw] modules are stopped Apr 26 04:46:59 192.168.122.209 [45769.666391] [tempesta fw] exiting... Apr 26 04:46:59 192.168.122.209 [45769.799364] [tdb] Shutdown Tempesta DB Apr 26 04:46:59 192.168.122.209 [45770.011838] End test: t_frang.test_http_strict_host_checking.FrangHostRequiredTestCase.test_host_header_as_ip Apr 26 04:46:59 192.168.122.209 [45770.023600] Start test: t_frang.test_http_strict_host_checking.FrangHostRequiredTestCase.test_host_header_as_ip6 Apr 26 04:47:00 192.168.122.209 [45771.176494] [tdb] Start Tempesta DB Apr 26 04:47:00 192.168.122.209 [45771.301549] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:47:01 192.168.122.209 [45772.030381] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45772.030381] Maybe that's fine, but it's worth checking the [45772.030381] config - if there is no relations between the [45772.030381] names, then host name confusion attack is possible. Apr 26 04:47:01 192.168.122.209 [45772.137185] [tempesta fw] Configuration processing is completed. Apr 26 04:47:01 192.168.122.209 [45772.188406] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:47:01 192.168.122.209 [45772.217744] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:47:01 192.168.122.209 [45772.243563] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:47:01 192.168.122.209 [45772.289123] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:47:01 192.168.122.209 [45772.290267] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:47:01 192.168.122.209 [45772.291532] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:47:01 192.168.122.209 [45772.333095] [tempesta fw] Tempesta FW is ready Apr 26 04:47:02 192.168.122.209 [45772.479439] [tempesta fw] Warning: frang: Host header field contains IP address for 127.0.0.2 Apr 26 04:47:02 192.168.122.209 [45772.480312] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:47:02 192.168.122.209 [45772.982695] [tdb] Close table 'client0.tdb' Apr 26 04:47:02 192.168.122.209 [45773.178611] [tdb] Close table 'sessions0.tdb' Apr 26 04:47:03 192.168.122.209 [45773.424189] [tdb] Close table 'filter0.tdb' Apr 26 04:47:03 192.168.122.209 [45773.424628] [tempesta fw] modules are stopped Apr 26 04:47:03 192.168.122.209 [45773.647433] [tempesta fw] exiting... Apr 26 04:47:03 192.168.122.209 [45773.764012] [tdb] Shutdown Tempesta DB Apr 26 04:47:03 192.168.122.209 [45773.976317] End test: t_frang.test_http_strict_host_checking.FrangHostRequiredTestCase.test_host_header_as_ip6 Apr 26 04:47:03 192.168.122.209 [45773.988580] Start test: t_frang.test_http_strict_host_checking.FrangHostRequiredTestCase.test_host_header_mismatch Apr 26 04:47:04 192.168.122.209 [45775.172380] [tdb] Start Tempesta DB Apr 26 04:47:04 192.168.122.209 [45775.322729] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:47:05 192.168.122.209 [45776.070451] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45776.070451] Maybe that's fine, but it's worth checking the [45776.070451] config - if there is no relations between the [45776.070451] names, then host name confusion attack is possible. Apr 26 04:47:05 192.168.122.209 [45776.189155] [tempesta fw] Configuration processing is completed. Apr 26 04:47:05 192.168.122.209 [45776.245883] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:47:05 192.168.122.209 [45776.276171] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:47:05 192.168.122.209 [45776.304984] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:47:05 192.168.122.209 [45776.349234] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:47:05 192.168.122.209 [45776.350956] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:47:05 192.168.122.209 [45776.352581] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:47:06 192.168.122.209 [45776.393153] [tempesta fw] Tempesta FW is ready Apr 26 04:47:06 192.168.122.209 [45776.502870] [tempesta fw] Warning: frang: Request host from absolute URI differs from Host header for 127.0.0.2 Apr 26 04:47:06 192.168.122.209 [45776.505704] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:47:06 192.168.122.209 [45776.972624] [tdb] Close table 'client0.tdb' Apr 26 04:47:06 192.168.122.209 [45777.165198] [tdb] Close table 'sessions0.tdb' Apr 26 04:47:07 192.168.122.209 [45777.389019] [tdb] Close table 'filter0.tdb' Apr 26 04:47:07 192.168.122.209 [45777.389471] [tempesta fw] modules are stopped Apr 26 04:47:07 192.168.122.209 [45777.569640] [tempesta fw] exiting... Apr 26 04:47:07 192.168.122.209 [45777.714927] [tdb] Shutdown Tempesta DB Apr 26 04:47:07 192.168.122.209 [45777.912636] End test: t_frang.test_http_strict_host_checking.FrangHostRequiredTestCase.test_host_header_mismatch Apr 26 04:47:07 192.168.122.209 [45777.920081] Start test: t_frang.test_http_strict_host_checking.FrangHostRequiredTestCase.test_host_header_mismatch_empty Apr 26 04:47:08 192.168.122.209 [45779.120911] [tdb] Start Tempesta DB Apr 26 04:47:08 192.168.122.209 [45779.261697] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:47:09 192.168.122.209 [45779.965914] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45779.965914] Maybe that's fine, but it's worth checking the [45779.965914] config - if there is no relations between the [45779.965914] names, then host name confusion attack is possible. Apr 26 04:47:09 192.168.122.209 [45780.061374] [tempesta fw] Configuration processing is completed. Apr 26 04:47:09 192.168.122.209 [45780.115606] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:47:09 192.168.122.209 [45780.163855] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:47:09 192.168.122.209 [45780.202873] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:47:09 192.168.122.209 [45780.269148] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:47:09 192.168.122.209 [45780.270014] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:47:09 192.168.122.209 [45780.270838] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:47:09 192.168.122.209 [45780.309107] [tempesta fw] Tempesta FW is ready Apr 26 04:47:10 192.168.122.209 [45780.474208] [tempesta fw] Warning: frang: Request host from absolute URI differs from Host header for 127.0.0.2 Apr 26 04:47:10 192.168.122.209 [45780.475601] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:47:10 192.168.122.209 [45780.974532] [tdb] Close table 'client0.tdb' Apr 26 04:47:10 192.168.122.209 [45781.162027] [tdb] Close table 'sessions0.tdb' Apr 26 04:47:11 192.168.122.209 [45781.404904] [tdb] Close table 'filter0.tdb' Apr 26 04:47:11 192.168.122.209 [45781.405719] [tempesta fw] modules are stopped Apr 26 04:47:11 192.168.122.209 [45781.621454] [tempesta fw] exiting... Apr 26 04:47:11 192.168.122.209 [45781.728568] [tdb] Shutdown Tempesta DB Apr 26 04:47:11 192.168.122.209 [45781.910487] End test: t_frang.test_http_strict_host_checking.FrangHostRequiredTestCase.test_host_header_mismatch_empty Apr 26 04:47:11 192.168.122.209 [45781.923830] Start test: t_frang.test_http_strict_host_checking.FrangHostRequiredTestCase.test_host_header_mismatch_port_in_host Apr 26 04:47:12 192.168.122.209 [45783.097495] [tdb] Start Tempesta DB Apr 26 04:47:12 192.168.122.209 [45783.247783] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:47:13 192.168.122.209 [45783.970586] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45783.970586] Maybe that's fine, but it's worth checking the [45783.970586] config - if there is no relations between the [45783.970586] names, then host name confusion attack is possible. Apr 26 04:47:13 192.168.122.209 [45784.069316] [tempesta fw] Configuration processing is completed. Apr 26 04:47:13 192.168.122.209 [45784.131907] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:47:13 192.168.122.209 [45784.159689] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:47:13 192.168.122.209 [45784.186147] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:47:13 192.168.122.209 [45784.229244] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:47:13 192.168.122.209 [45784.230273] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:47:13 192.168.122.209 [45784.231260] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:47:13 192.168.122.209 [45784.269249] [tempesta fw] Tempesta FW is ready Apr 26 04:47:14 192.168.122.209 [45784.389274] [tempesta fw] Warning: frang: port from host header doesn't match port from uri for 127.0.0.2: 80 (81) Apr 26 04:47:14 192.168.122.209 [45784.390586] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:47:14 192.168.122.209 [45784.914741] [tdb] Close table 'client0.tdb' Apr 26 04:47:14 192.168.122.209 [45785.103066] [tdb] Close table 'sessions0.tdb' Apr 26 04:47:14 192.168.122.209 [45785.342742] [tdb] Close table 'filter0.tdb' Apr 26 04:47:14 192.168.122.209 [45785.343190] [tempesta fw] modules are stopped Apr 26 04:47:15 192.168.122.209 [45785.516105] [tempesta fw] exiting... Apr 26 04:47:15 192.168.122.209 [45785.609450] [tdb] Shutdown Tempesta DB Apr 26 04:47:15 192.168.122.209 [45785.796590] End test: t_frang.test_http_strict_host_checking.FrangHostRequiredTestCase.test_host_header_mismatch_port_in_host Apr 26 04:47:15 192.168.122.209 [45785.816481] Start test: t_frang.test_http_strict_host_checking.FrangHostRequiredTestCase.test_host_header_no_port_in_host Apr 26 04:47:16 192.168.122.209 [45787.004489] [tdb] Start Tempesta DB Apr 26 04:47:16 192.168.122.209 [45787.159371] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:47:17 192.168.122.209 [45787.918660] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45787.918660] Maybe that's fine, but it's worth checking the [45787.918660] config - if there is no relations between the [45787.918660] names, then host name confusion attack is possible. Apr 26 04:47:17 192.168.122.209 [45788.029575] [tempesta fw] Configuration processing is completed. Apr 26 04:47:17 192.168.122.209 [45788.089142] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:47:17 192.168.122.209 [45788.122481] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:47:17 192.168.122.209 [45788.151783] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:47:17 192.168.122.209 [45788.205366] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:47:17 192.168.122.209 [45788.206998] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:47:17 192.168.122.209 [45788.208541] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:47:17 192.168.122.209 [45788.249322] [tempesta fw] Tempesta FW is ready Apr 26 04:47:18 192.168.122.209 [45788.844844] [tdb] Close table 'client0.tdb' Apr 26 04:47:18 192.168.122.209 [45789.039418] [tdb] Close table 'sessions0.tdb' Apr 26 04:47:18 192.168.122.209 [45789.268482] [tdb] Close table 'filter0.tdb' Apr 26 04:47:18 192.168.122.209 [45789.268928] [tempesta fw] modules are stopped Apr 26 04:47:19 192.168.122.209 [45789.443022] [tempesta fw] exiting... Apr 26 04:47:19 192.168.122.209 [45789.563425] [tdb] Shutdown Tempesta DB Apr 26 04:47:19 192.168.122.209 [45789.806300] End test: t_frang.test_http_strict_host_checking.FrangHostRequiredTestCase.test_host_header_no_port_in_host Apr 26 04:47:19 192.168.122.209 [45789.818156] Start test: t_frang.test_http_strict_host_checking.FrangHostRequiredTestCase.test_host_header_no_port_in_uri Apr 26 04:47:20 192.168.122.209 [45791.005031] [tdb] Start Tempesta DB Apr 26 04:47:20 192.168.122.209 [45791.154861] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:47:21 192.168.122.209 [45791.906736] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45791.906736] Maybe that's fine, but it's worth checking the [45791.906736] config - if there is no relations between the [45791.906736] names, then host name confusion attack is possible. Apr 26 04:47:21 192.168.122.209 [45792.009437] [tempesta fw] Configuration processing is completed. Apr 26 04:47:21 192.168.122.209 [45792.067497] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:47:21 192.168.122.209 [45792.097894] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:47:21 192.168.122.209 [45792.126912] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:47:21 192.168.122.209 [45792.173367] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:47:21 192.168.122.209 [45792.174606] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:47:21 192.168.122.209 [45792.176115] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:47:21 192.168.122.209 [45792.225446] [tempesta fw] Tempesta FW is ready Apr 26 04:47:22 192.168.122.209 [45792.887441] [tdb] Close table 'client0.tdb' Apr 26 04:47:22 192.168.122.209 [45793.078587] [tdb] Close table 'sessions0.tdb' Apr 26 04:47:22 192.168.122.209 [45793.305806] [tdb] Close table 'filter0.tdb' Apr 26 04:47:22 192.168.122.209 [45793.306282] [tempesta fw] modules are stopped Apr 26 04:47:23 192.168.122.209 [45793.496181] [tempesta fw] exiting... Apr 26 04:47:23 192.168.122.209 [45793.659153] [tdb] Shutdown Tempesta DB Apr 26 04:47:23 192.168.122.209 [45793.875554] End test: t_frang.test_http_strict_host_checking.FrangHostRequiredTestCase.test_host_header_no_port_in_uri Apr 26 04:47:23 192.168.122.209 [45793.883706] Start test: t_frang.test_http_strict_host_checking.FrangHostRequiredTestCase.test_host_header_set_ok Apr 26 04:47:24 192.168.122.209 [45795.045487] [tdb] Start Tempesta DB Apr 26 04:47:24 192.168.122.209 [45795.193168] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:47:25 192.168.122.209 [45795.950748] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45795.950748] Maybe that's fine, but it's worth checking the [45795.950748] config - if there is no relations between the [45795.950748] names, then host name confusion attack is possible. Apr 26 04:47:25 192.168.122.209 [45796.061484] [tempesta fw] Configuration processing is completed. Apr 26 04:47:25 192.168.122.209 [45796.113440] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:47:25 192.168.122.209 [45796.143136] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:47:25 192.168.122.209 [45796.169875] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:47:25 192.168.122.209 [45796.213435] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:47:25 192.168.122.209 [45796.214827] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:47:25 192.168.122.209 [45796.216106] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:47:25 192.168.122.209 [45796.261398] [tempesta fw] Tempesta FW is ready Apr 26 04:47:26 192.168.122.209 [45796.935022] [tdb] Close table 'client0.tdb' Apr 26 04:47:26 192.168.122.209 [45797.134220] [tdb] Close table 'sessions0.tdb' Apr 26 04:47:27 192.168.122.209 [45797.387071] [tdb] Close table 'filter0.tdb' Apr 26 04:47:27 192.168.122.209 [45797.387520] [tempesta fw] modules are stopped Apr 26 04:47:27 192.168.122.209 [45797.600784] [tempesta fw] exiting... Apr 26 04:47:27 192.168.122.209 [45797.730670] [tdb] Shutdown Tempesta DB Apr 26 04:47:27 192.168.122.209 [45797.942960] End test: t_frang.test_http_strict_host_checking.FrangHostRequiredTestCase.test_host_header_set_ok Apr 26 04:47:27 192.168.122.209 [45797.957736] Start test: t_frang.test_http_strict_host_checking.FrangHostRequiredTestCase.test_host_header_with_old_proto Apr 26 04:47:28 192.168.122.209 [45799.151521] [tdb] Start Tempesta DB Apr 26 04:47:28 192.168.122.209 [45799.292772] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:47:29 192.168.122.209 [45800.042824] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45800.042824] Maybe that's fine, but it's worth checking the [45800.042824] config - if there is no relations between the [45800.042824] names, then host name confusion attack is possible. Apr 26 04:47:29 192.168.122.209 [45800.153541] [tempesta fw] Configuration processing is completed. Apr 26 04:47:29 192.168.122.209 [45800.203757] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:47:29 192.168.122.209 [45800.231260] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:47:29 192.168.122.209 [45800.257344] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:47:29 192.168.122.209 [45800.337518] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:47:29 192.168.122.209 [45800.339235] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:47:29 192.168.122.209 [45800.340828] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:47:30 192.168.122.209 [45800.385435] [tempesta fw] Tempesta FW is ready Apr 26 04:47:30 192.168.122.209 [45800.529286] [tempesta fw] Warning: frang: Host header field in protocol prior to HTTP/1.1 for 127.0.0.2 Apr 26 04:47:30 192.168.122.209 [45800.531891] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:47:30 192.168.122.209 [45801.037976] [tdb] Close table 'client0.tdb' Apr 26 04:47:30 192.168.122.209 [45801.227967] [tdb] Close table 'sessions0.tdb' Apr 26 04:47:31 192.168.122.209 [45801.472104] [tdb] Close table 'filter0.tdb' Apr 26 04:47:31 192.168.122.209 [45801.472557] [tempesta fw] modules are stopped Apr 26 04:47:31 192.168.122.209 [45801.634063] [tempesta fw] exiting... Apr 26 04:47:31 192.168.122.209 [45801.776938] [tdb] Shutdown Tempesta DB Apr 26 04:47:31 192.168.122.209 [45801.986085] End test: t_frang.test_http_strict_host_checking.FrangHostRequiredTestCase.test_host_header_with_old_proto Apr 26 04:47:31 192.168.122.209 [45801.999277] Start test: t_frang.test_http_trailer_split_allowed.FrangHttpTrailerSplitLimitOnTestCase.test_accepted_request Apr 26 04:47:32 192.168.122.209 [45803.200179] [tdb] Start Tempesta DB Apr 26 04:47:32 192.168.122.209 [45803.346373] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:47:33 192.168.122.209 [45804.110886] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45804.110886] Maybe that's fine, but it's worth checking the [45804.110886] config - if there is no relations between the [45804.110886] names, then host name confusion attack is possible. Apr 26 04:47:33 192.168.122.209 [45804.213602] [tempesta fw] Configuration processing is completed. Apr 26 04:47:33 192.168.122.209 [45804.266033] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:47:33 192.168.122.209 [45804.296243] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:47:33 192.168.122.209 [45804.323320] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:47:34 192.168.122.209 [45804.389570] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:47:34 192.168.122.209 [45804.391287] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:47:34 192.168.122.209 [45804.392887] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:47:34 192.168.122.209 [45804.429521] [tempesta fw] Tempesta FW is ready Apr 26 04:47:34 192.168.122.209 [45805.129455] [tdb] Close table 'client0.tdb' Apr 26 04:47:34 192.168.122.209 [45805.343898] [tdb] Close table 'sessions0.tdb' Apr 26 04:47:35 192.168.122.209 [45805.594358] [tdb] Close table 'filter0.tdb' Apr 26 04:47:35 192.168.122.209 [45805.594810] [tempesta fw] modules are stopped Apr 26 04:47:35 192.168.122.209 [45805.799215] [tempesta fw] exiting... Apr 26 04:47:35 192.168.122.209 [45805.954258] [tdb] Shutdown Tempesta DB Apr 26 04:47:35 192.168.122.209 [45806.180916] End test: t_frang.test_http_trailer_split_allowed.FrangHttpTrailerSplitLimitOnTestCase.test_accepted_request Apr 26 04:47:35 192.168.122.209 [45806.191066] Start test: t_frang.test_http_trailer_split_allowed.FrangHttpTrailerSplitLimitOnTestCase.test_default_trailer_split_allowed Apr 26 04:47:37 192.168.122.209 [45807.404758] [tdb] Start Tempesta DB Apr 26 04:47:37 192.168.122.209 [45807.548528] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:47:37 192.168.122.209 [45808.306935] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45808.306935] Maybe that's fine, but it's worth checking the [45808.306935] config - if there is no relations between the [45808.306935] names, then host name confusion attack is possible. Apr 26 04:47:38 192.168.122.209 [45808.405667] [tempesta fw] Configuration processing is completed. Apr 26 04:47:38 192.168.122.209 [45808.460224] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:47:38 192.168.122.209 [45808.488691] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:47:38 192.168.122.209 [45808.516014] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:47:38 192.168.122.209 [45808.569651] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:47:38 192.168.122.209 [45808.571469] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:47:38 192.168.122.209 [45808.573140] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:47:38 192.168.122.209 [45808.613565] [tempesta fw] Tempesta FW is ready Apr 26 04:47:38 192.168.122.209 [45808.767548] [tempesta fw] Warning: frang: HTTP field appear in header and trailer for client for 127.0.0.2 Apr 26 04:47:38 192.168.122.209 [45808.769641] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:47:38 192.168.122.209 [45809.317695] [tdb] Close table 'client0.tdb' Apr 26 04:47:39 192.168.122.209 [45809.509828] [tdb] Close table 'sessions0.tdb' Apr 26 04:47:39 192.168.122.209 [45809.757554] [tdb] Close table 'filter0.tdb' Apr 26 04:47:39 192.168.122.209 [45809.758024] [tempesta fw] modules are stopped Apr 26 04:47:39 192.168.122.209 [45809.988891] [tempesta fw] exiting... Apr 26 04:47:39 192.168.122.209 [45810.166421] [tdb] Shutdown Tempesta DB Apr 26 04:47:39 192.168.122.209 [45810.354509] End test: t_frang.test_http_trailer_split_allowed.FrangHttpTrailerSplitLimitOnTestCase.test_default_trailer_split_allowed Apr 26 04:47:39 192.168.122.209 [45810.376911] Start test: t_frang.test_http_trailer_split_allowed.FrangHttpTrailerSplitLimitOnTestCase.test_disable_trailer_split_allowed Apr 26 04:47:41 192.168.122.209 [45811.542397] [tdb] Start Tempesta DB Apr 26 04:47:41 192.168.122.209 [45811.697371] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:47:42 192.168.122.209 [45812.470963] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45812.470963] Maybe that's fine, but it's worth checking the [45812.470963] config - if there is no relations between the [45812.470963] names, then host name confusion attack is possible. Apr 26 04:47:42 192.168.122.209 [45812.569684] [tempesta fw] Configuration processing is completed. Apr 26 04:47:42 192.168.122.209 [45812.621269] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:47:42 192.168.122.209 [45812.650901] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:47:42 192.168.122.209 [45812.677375] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:47:42 192.168.122.209 [45812.733667] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:47:42 192.168.122.209 [45812.735456] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:47:42 192.168.122.209 [45812.737059] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:47:42 192.168.122.209 [45812.785619] [tempesta fw] Tempesta FW is ready Apr 26 04:47:43 192.168.122.209 [45813.447101] [tdb] Close table 'client0.tdb' Apr 26 04:47:43 192.168.122.209 [45813.615881] [tdb] Close table 'sessions0.tdb' Apr 26 04:47:43 192.168.122.209 [45813.841563] [tdb] Close table 'filter0.tdb' Apr 26 04:47:43 192.168.122.209 [45813.842030] [tempesta fw] modules are stopped Apr 26 04:47:43 192.168.122.209 [45814.068657] [tempesta fw] exiting... Apr 26 04:47:43 192.168.122.209 [45814.175929] [tdb] Shutdown Tempesta DB Apr 26 04:47:43 192.168.122.209 [45814.378797] End test: t_frang.test_http_trailer_split_allowed.FrangHttpTrailerSplitLimitOnTestCase.test_disable_trailer_split_allowed Apr 26 04:47:44 192.168.122.209 [45814.392146] Start test: t_frang.test_http_trailer_split_allowed.TestFrangHttpTrailerSplitAllowedH2.test_accepted_request Apr 26 04:47:45 192.168.122.209 [45815.576649] [tdb] Start Tempesta DB Apr 26 04:47:45 192.168.122.209 [45815.716702] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:47:46 192.168.122.209 [45816.511029] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45816.511029] Maybe that's fine, but it's worth checking the [45816.511029] config - if there is no relations between the [45816.511029] names, then host name confusion attack is possible. Apr 26 04:47:46 192.168.122.209 [45816.613728] [tempesta fw] Configuration processing is completed. Apr 26 04:47:46 192.168.122.209 [45816.672664] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:47:46 192.168.122.209 [45816.710196] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:47:46 192.168.122.209 [45816.746003] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:47:46 192.168.122.209 [45816.785623] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:47:46 192.168.122.209 [45816.786693] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:47:46 192.168.122.209 [45816.787733] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:47:46 192.168.122.209 [45816.829628] [tempesta fw] Tempesta FW is ready Apr 26 04:47:47 192.168.122.209 [45817.497793] [tdb] Close table 'client0.tdb' Apr 26 04:47:47 192.168.122.209 [45817.685597] [tdb] Close table 'sessions0.tdb' Apr 26 04:47:47 192.168.122.209 [45817.929644] [tdb] Close table 'filter0.tdb' Apr 26 04:47:47 192.168.122.209 [45817.930083] [tempesta fw] modules are stopped Apr 26 04:47:47 192.168.122.209 [45818.125787] [tempesta fw] exiting... Apr 26 04:47:47 192.168.122.209 [45818.292144] [tdb] Shutdown Tempesta DB Apr 26 04:47:48 192.168.122.209 [45818.528774] End test: t_frang.test_http_trailer_split_allowed.TestFrangHttpTrailerSplitAllowedH2.test_accepted_request Apr 26 04:47:48 192.168.122.209 [45818.549650] Start test: t_frang.test_http_trailer_split_allowed.TestFrangHttpTrailerSplitAllowedH2.test_default_trailer_split_allowed Apr 26 04:47:49 192.168.122.209 [45819.821627] [tdb] Start Tempesta DB Apr 26 04:47:49 192.168.122.209 [45819.991956] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:47:50 192.168.122.209 [45820.787091] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45820.787091] Maybe that's fine, but it's worth checking the [45820.787091] config - if there is no relations between the [45820.787091] names, then host name confusion attack is possible. Apr 26 04:47:50 192.168.122.209 [45820.893807] [tempesta fw] Configuration processing is completed. Apr 26 04:47:50 192.168.122.209 [45820.944751] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:47:50 192.168.122.209 [45820.974680] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:47:50 192.168.122.209 [45821.002136] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:47:50 192.168.122.209 [45821.049759] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:47:50 192.168.122.209 [45821.051182] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:47:50 192.168.122.209 [45821.052489] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:47:50 192.168.122.209 [45821.105733] [tempesta fw] Tempesta FW is ready Apr 26 04:47:50 192.168.122.209 [45821.252306] [tempesta fw] Warning: frang: HTTP field appear in header and trailer for client for 127.0.0.2 Apr 26 04:47:50 192.168.122.209 [45821.253213] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:47:51 192.168.122.209 [45821.786872] [tdb] Close table 'client0.tdb' Apr 26 04:47:51 192.168.122.209 [45821.979345] [tdb] Close table 'sessions0.tdb' Apr 26 04:47:51 192.168.122.209 [45822.204505] [tdb] Close table 'filter0.tdb' Apr 26 04:47:51 192.168.122.209 [45822.204965] [tempesta fw] modules are stopped Apr 26 04:47:52 192.168.122.209 [45822.411676] [tempesta fw] exiting... Apr 26 04:47:52 192.168.122.209 [45822.546749] [tdb] Shutdown Tempesta DB Apr 26 04:47:52 192.168.122.209 [45822.753238] End test: t_frang.test_http_trailer_split_allowed.TestFrangHttpTrailerSplitAllowedH2.test_default_trailer_split_allowed Apr 26 04:47:52 192.168.122.209 [45822.763030] Start test: t_frang.test_http_trailer_split_allowed.TestFrangHttpTrailerSplitAllowedH2.test_disable_trailer_split_allowed Apr 26 04:47:53 192.168.122.209 [45823.908189] [tdb] Start Tempesta DB Apr 26 04:47:53 192.168.122.209 [45824.042574] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:47:54 192.168.122.209 [45824.815121] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45824.815121] Maybe that's fine, but it's worth checking the [45824.815121] config - if there is no relations between the [45824.815121] names, then host name confusion attack is possible. Apr 26 04:47:54 192.168.122.209 [45824.925820] [tempesta fw] Configuration processing is completed. Apr 26 04:47:54 192.168.122.209 [45824.976102] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:47:54 192.168.122.209 [45825.004207] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:47:54 192.168.122.209 [45825.031115] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:47:54 192.168.122.209 [45825.081830] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:47:54 192.168.122.209 [45825.083348] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:47:54 192.168.122.209 [45825.085063] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:47:54 192.168.122.209 [45825.125767] [tempesta fw] Tempesta FW is ready Apr 26 04:47:54 192.168.122.209 [45825.260120] [tempesta fw] Warning: frang: HTTP field appear in header and trailer for client for 127.0.0.2 Apr 26 04:47:54 192.168.122.209 [45825.262805] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:47:55 192.168.122.209 [45825.774905] [tdb] Close table 'client0.tdb' Apr 26 04:47:55 192.168.122.209 [45825.970780] [tdb] Close table 'sessions0.tdb' Apr 26 04:47:55 192.168.122.209 [45826.211953] [tdb] Close table 'filter0.tdb' Apr 26 04:47:55 192.168.122.209 [45826.212405] [tempesta fw] modules are stopped Apr 26 04:47:56 192.168.122.209 [45826.432262] [tempesta fw] exiting... Apr 26 04:47:56 192.168.122.209 [45826.558671] [tdb] Shutdown Tempesta DB Apr 26 04:47:56 192.168.122.209 [45826.745675] End test: t_frang.test_http_trailer_split_allowed.TestFrangHttpTrailerSplitAllowedH2.test_disable_trailer_split_allowed Apr 26 04:47:56 192.168.122.209 [45826.758097] Start test: t_frang.test_ip_block.FrangIpBlockConn.test_off Apr 26 04:47:58 192.168.122.209 [45828.407947] [tdb] Start Tempesta DB Apr 26 04:47:58 192.168.122.209 [45828.542773] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:47:58 192.168.122.209 [45829.085946] [tempesta fw] Configuration processing is completed. Apr 26 04:47:58 192.168.122.209 [45829.136350] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:47:59 192.168.122.209 [45829.602964] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:47:59 192.168.122.209 [45829.696105] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:47:59 192.168.122.209 [45829.742815] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:47:59 192.168.122.209 [45829.793879] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:47:59 192.168.122.209 [45829.833754] [tempesta fw] Tempesta FW is ready Apr 26 04:47:59 192.168.122.209 [45829.962145] [tempesta fw] Warning: frang: new connections rate exceeded for 127.0.0.2: 2 (lim=1) Apr 26 04:48:02 192.168.122.209 [45832.501429] [tdb] Close table 'client0.tdb' Apr 26 04:48:02 192.168.122.209 [45832.698548] [tdb] Close table 'sessions0.tdb' Apr 26 04:48:05 192.168.122.209 [45835.916821] [tdb] Close table 'cache0.tdb' Apr 26 04:48:05 192.168.122.209 [45836.161973] [tdb] Close table 'filter0.tdb' Apr 26 04:48:05 192.168.122.209 [45836.162425] [tempesta fw] modules are stopped Apr 26 04:48:05 192.168.122.209 [45836.375969] [tempesta fw] exiting... Apr 26 04:48:06 192.168.122.209 [45836.489248] [tdb] Shutdown Tempesta DB Apr 26 04:48:06 192.168.122.209 [45836.695359] End test: t_frang.test_ip_block.FrangIpBlockConn.test_off Apr 26 04:48:06 192.168.122.209 [45836.703709] Start test: t_frang.test_ip_block.FrangIpBlockConn.test_on Apr 26 04:48:07 192.168.122.209 [45837.955890] [tdb] Start Tempesta DB Apr 26 04:48:07 192.168.122.209 [45838.092301] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:48:09 192.168.122.209 [45839.450109] [tempesta fw] Configuration processing is completed. Apr 26 04:48:09 192.168.122.209 [45839.501779] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:48:09 192.168.122.209 [45839.991066] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:48:09 192.168.122.209 [45840.050057] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:48:09 192.168.122.209 [45840.077451] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:48:09 192.168.122.209 [45840.129996] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:48:09 192.168.122.209 [45840.169916] [tempesta fw] Tempesta FW is ready Apr 26 04:48:09 192.168.122.209 [45840.297546] [tempesta fw] Warning: frang: new connections rate exceeded for 127.0.0.2: 3 (lim=2) Apr 26 04:48:09 192.168.122.209 [45840.300041] [tempesta fw] Warning: block client: 127.0.0.2 Apr 26 04:48:12 192.168.122.209 [45842.494968] [tdb] Close table 'client0.tdb' Apr 26 04:48:12 192.168.122.209 [45842.690654] [tdb] Close table 'sessions0.tdb' Apr 26 04:48:15 192.168.122.209 [45845.939359] [tdb] Close table 'cache0.tdb' Apr 26 04:48:15 192.168.122.209 [45846.194853] [tdb] Close table 'filter0.tdb' Apr 26 04:48:15 192.168.122.209 [45846.195315] [tempesta fw] modules are stopped Apr 26 04:48:15 192.168.122.209 [45846.377412] [tempesta fw] exiting... Apr 26 04:48:16 192.168.122.209 [45846.516644] [tdb] Shutdown Tempesta DB Apr 26 04:48:16 192.168.122.209 [45846.762523] End test: t_frang.test_ip_block.FrangIpBlockConn.test_on Apr 26 04:48:16 192.168.122.209 [45846.773686] Start test: t_frang.test_ip_block.FrangIpBlockMsg.test_off Apr 26 04:48:17 192.168.122.209 [45848.073312] [tdb] Start Tempesta DB Apr 26 04:48:17 192.168.122.209 [45848.244519] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:48:19 192.168.122.209 [45849.642181] [tempesta fw] Configuration processing is completed. Apr 26 04:48:19 192.168.122.209 [45849.696441] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:48:19 192.168.122.209 [45850.198748] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:48:19 192.168.122.209 [45850.227685] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:48:19 192.168.122.209 [45850.257636] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:48:19 192.168.122.209 [45850.318170] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:48:19 192.168.122.209 [45850.366106] [tempesta fw] Tempesta FW is ready Apr 26 04:48:20 192.168.122.209 [45850.501927] [tempesta fw] Warning: frang: Host header field contains IP address for 127.0.0.2 Apr 26 04:48:20 192.168.122.209 [45850.504323] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:48:22 192.168.122.209 [45852.566107] [tdb] Close table 'client0.tdb' Apr 26 04:48:22 192.168.122.209 [45852.761758] [tdb] Close table 'sessions0.tdb' Apr 26 04:48:25 192.168.122.209 [45856.088789] [tdb] Close table 'cache0.tdb' Apr 26 04:48:25 192.168.122.209 [45856.344176] [tdb] Close table 'filter0.tdb' Apr 26 04:48:25 192.168.122.209 [45856.344636] [tempesta fw] modules are stopped Apr 26 04:48:26 192.168.122.209 [45856.504972] [tempesta fw] exiting... Apr 26 04:48:26 192.168.122.209 [45856.676765] [tdb] Shutdown Tempesta DB Apr 26 04:48:26 192.168.122.209 [45856.928658] End test: t_frang.test_ip_block.FrangIpBlockMsg.test_off Apr 26 04:48:26 192.168.122.209 [45856.939543] Start test: t_frang.test_ip_block.FrangIpBlockMsg.test_on Apr 26 04:48:27 192.168.122.209 [45858.148675] [tdb] Start Tempesta DB Apr 26 04:48:27 192.168.122.209 [45858.287757] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:48:29 192.168.122.209 [45859.702309] [tempesta fw] Configuration processing is completed. Apr 26 04:48:29 192.168.122.209 [45859.754268] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:48:29 192.168.122.209 [45860.240050] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:48:29 192.168.122.209 [45860.304988] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:48:29 192.168.122.209 [45860.339257] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:48:30 192.168.122.209 [45860.390268] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:48:30 192.168.122.209 [45860.450216] [tempesta fw] Tempesta FW is ready Apr 26 04:48:30 192.168.122.209 [45860.633564] [tempesta fw] Warning: frang: Host header field contains IP address for 127.0.0.2 Apr 26 04:48:30 192.168.122.209 [45860.636037] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:48:30 192.168.122.209 [45860.638178] [tempesta fw] Warning: block client: 127.0.0.2 Apr 26 04:48:32 192.168.122.209 [45862.703340] [tdb] Close table 'client0.tdb' Apr 26 04:48:32 192.168.122.209 [45862.903488] [tdb] Close table 'sessions0.tdb' Apr 26 04:48:35 192.168.122.209 [45866.223035] [tdb] Close table 'cache0.tdb' Apr 26 04:48:36 192.168.122.209 [45866.441993] [tdb] Close table 'filter0.tdb' Apr 26 04:48:36 192.168.122.209 [45866.442474] [tempesta fw] modules are stopped Apr 26 04:48:36 192.168.122.209 [45866.635527] [tempesta fw] exiting... Apr 26 04:48:36 192.168.122.209 [45866.765727] [tdb] Shutdown Tempesta DB Apr 26 04:48:36 192.168.122.209 [45866.978752] End test: t_frang.test_ip_block.FrangIpBlockMsg.test_on Apr 26 04:48:36 192.168.122.209 [45866.987496] Start test: t_frang.test_length.FrangLengthH2.test_body_len Apr 26 04:48:37 192.168.122.209 [45868.137397] [tdb] Start Tempesta DB Apr 26 04:48:37 192.168.122.209 [45868.288247] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:48:39 192.168.122.209 [45869.863711] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45869.863711] Maybe that's fine, but it's worth checking the [45869.863711] config - if there is no relations between the [45869.863711] names, then host name confusion attack is possible. Apr 26 04:48:39 192.168.122.209 [45869.974412] [tempesta fw] Configuration processing is completed. Apr 26 04:48:39 192.168.122.209 [45870.029156] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:48:39 192.168.122.209 [45870.057246] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:48:39 192.168.122.209 [45870.085864] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:48:39 192.168.122.209 [45870.134360] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:48:39 192.168.122.209 [45870.135768] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:48:39 192.168.122.209 [45870.137091] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:48:39 192.168.122.209 [45870.174372] [tempesta fw] Tempesta FW is ready Apr 26 04:48:39 192.168.122.209 [45870.320164] [tempesta fw] Warning: frang: HTTP body length exceeded for 127.0.0.2: 20 (lim=10) Apr 26 04:48:39 192.168.122.209 [45870.320961] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:48:40 192.168.122.209 [45870.861745] [tdb] Close table 'client0.tdb' Apr 26 04:48:40 192.168.122.209 [45871.048798] [tdb] Close table 'sessions0.tdb' Apr 26 04:48:40 192.168.122.209 [45871.264677] [tdb] Close table 'filter0.tdb' Apr 26 04:48:40 192.168.122.209 [45871.265121] [tempesta fw] modules are stopped Apr 26 04:48:41 192.168.122.209 [45871.487244] [tempesta fw] exiting... Apr 26 04:48:41 192.168.122.209 [45871.628027] [tdb] Shutdown Tempesta DB Apr 26 04:48:41 192.168.122.209 [45871.864528] End test: t_frang.test_length.FrangLengthH2.test_body_len Apr 26 04:48:41 192.168.122.209 [45871.874266] Start test: t_frang.test_length.FrangLengthH2.test_body_len_without_reaching_the_limit Apr 26 04:48:42 192.168.122.209 [45872.940016] [tdb] Start Tempesta DB Apr 26 04:48:42 192.168.122.209 [45873.076348] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:48:43 192.168.122.209 [45873.831669] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45873.831669] Maybe that's fine, but it's worth checking the [45873.831669] config - if there is no relations between the [45873.831669] names, then host name confusion attack is possible. Apr 26 04:48:43 192.168.122.209 [45873.934463] [tempesta fw] Configuration processing is completed. Apr 26 04:48:43 192.168.122.209 [45873.998805] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:48:43 192.168.122.209 [45874.032235] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:48:43 192.168.122.209 [45874.058699] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:48:43 192.168.122.209 [45874.110438] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:48:43 192.168.122.209 [45874.112067] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:48:43 192.168.122.209 [45874.113594] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:48:43 192.168.122.209 [45874.150346] [tempesta fw] Tempesta FW is ready Apr 26 04:48:44 192.168.122.209 [45874.781660] [tdb] Close table 'client0.tdb' Apr 26 04:48:44 192.168.122.209 [45874.959528] [tdb] Close table 'sessions0.tdb' Apr 26 04:48:44 192.168.122.209 [45875.208426] [tdb] Close table 'filter0.tdb' Apr 26 04:48:44 192.168.122.209 [45875.208855] [tempesta fw] modules are stopped Apr 26 04:48:45 192.168.122.209 [45875.433161] [tempesta fw] exiting... Apr 26 04:48:45 192.168.122.209 [45875.565685] [tdb] Shutdown Tempesta DB Apr 26 04:48:45 192.168.122.209 [45875.762819] End test: t_frang.test_length.FrangLengthH2.test_body_len_without_reaching_the_limit Apr 26 04:48:45 192.168.122.209 [45875.780330] Start test: t_frang.test_length.FrangLengthH2.test_body_len_without_reaching_the_limit_zero_len Apr 26 04:48:46 192.168.122.209 [45876.942675] [tdb] Start Tempesta DB Apr 26 04:48:46 192.168.122.209 [45877.075084] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:48:47 192.168.122.209 [45877.807729] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45877.807729] Maybe that's fine, but it's worth checking the [45877.807729] config - if there is no relations between the [45877.807729] names, then host name confusion attack is possible. Apr 26 04:48:47 192.168.122.209 [45877.902515] [tempesta fw] Configuration processing is completed. Apr 26 04:48:47 192.168.122.209 [45877.952664] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:48:47 192.168.122.209 [45877.980764] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:48:47 192.168.122.209 [45878.007754] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:48:47 192.168.122.209 [45878.054477] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:48:47 192.168.122.209 [45878.055837] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:48:47 192.168.122.209 [45878.057155] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:48:47 192.168.122.209 [45878.122377] [tempesta fw] Tempesta FW is ready Apr 26 04:48:48 192.168.122.209 [45878.769246] [tdb] Close table 'client0.tdb' Apr 26 04:48:48 192.168.122.209 [45878.958964] [tdb] Close table 'sessions0.tdb' Apr 26 04:48:48 192.168.122.209 [45879.196720] [tdb] Close table 'filter0.tdb' Apr 26 04:48:48 192.168.122.209 [45879.197142] [tempesta fw] modules are stopped Apr 26 04:48:48 192.168.122.209 [45879.363870] [tempesta fw] exiting... Apr 26 04:48:49 192.168.122.209 [45879.512479] [tdb] Shutdown Tempesta DB Apr 26 04:48:49 192.168.122.209 [45879.679256] End test: t_frang.test_length.FrangLengthH2.test_body_len_without_reaching_the_limit_zero_len Apr 26 04:48:49 192.168.122.209 [45879.699106] Start test: t_frang.test_length.FrangLengthH2.test_http_hdr_len_huffman Apr 26 04:48:50 192.168.122.209 [45880.870485] [tdb] Start Tempesta DB Apr 26 04:48:50 192.168.122.209 [45881.009105] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:48:51 192.168.122.209 [45881.743781] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45881.743781] Maybe that's fine, but it's worth checking the [45881.743781] config - if there is no relations between the [45881.743781] names, then host name confusion attack is possible. Apr 26 04:48:51 192.168.122.209 [45881.850555] [tempesta fw] Configuration processing is completed. Apr 26 04:48:51 192.168.122.209 [45881.901421] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:48:51 192.168.122.209 [45881.931518] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:48:51 192.168.122.209 [45881.958890] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:48:51 192.168.122.209 [45882.002507] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:48:51 192.168.122.209 [45882.003833] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:48:51 192.168.122.209 [45882.005153] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:48:51 192.168.122.209 [45882.042499] [tempesta fw] Tempesta FW is ready Apr 26 04:48:51 192.168.122.209 [45882.170127] [tempesta fw] Warning: frang: HTTP header length exceeded for 127.0.0.2: 358 (lim=300) Apr 26 04:48:52 192.168.122.209 [45882.705391] [tdb] Close table 'client0.tdb' Apr 26 04:48:52 192.168.122.209 [45882.890021] [tdb] Close table 'sessions0.tdb' Apr 26 04:48:52 192.168.122.209 [45883.154712] [tdb] Close table 'filter0.tdb' Apr 26 04:48:52 192.168.122.209 [45883.155228] [tempesta fw] modules are stopped Apr 26 04:48:52 192.168.122.209 [45883.379595] [tempesta fw] exiting... Apr 26 04:48:53 192.168.122.209 [45883.535717] [tdb] Shutdown Tempesta DB Apr 26 04:48:53 192.168.122.209 [45883.729877] End test: t_frang.test_length.FrangLengthH2.test_http_hdr_len_huffman Apr 26 04:48:53 192.168.122.209 [45883.742540] Start test: t_frang.test_length.FrangLengthH2.test_http_hdr_len_no_huffman Apr 26 04:48:54 192.168.122.209 [45884.836394] [tdb] Start Tempesta DB Apr 26 04:48:54 192.168.122.209 [45884.977168] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:48:55 192.168.122.209 [45885.644951] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45885.644951] Maybe that's fine, but it's worth checking the [45885.644951] config - if there is no relations between the [45885.644951] names, then host name confusion attack is possible. Apr 26 04:48:55 192.168.122.209 [45885.746624] [tempesta fw] Configuration processing is completed. Apr 26 04:48:55 192.168.122.209 [45885.797210] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:48:55 192.168.122.209 [45885.825689] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:48:55 192.168.122.209 [45885.852997] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:48:55 192.168.122.209 [45885.898557] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:48:55 192.168.122.209 [45885.900156] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:48:55 192.168.122.209 [45885.901774] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:48:55 192.168.122.209 [45885.938548] [tempesta fw] Tempesta FW is ready Apr 26 04:48:55 192.168.122.209 [45886.055404] [tempesta fw] Warning: frang: HTTP header length exceeded for 127.0.0.2: 358 (lim=300) Apr 26 04:48:56 192.168.122.209 [45886.559290] [tdb] Close table 'client0.tdb' Apr 26 04:48:56 192.168.122.209 [45886.799768] [tdb] Close table 'sessions0.tdb' Apr 26 04:48:56 192.168.122.209 [45887.012622] [tdb] Close table 'filter0.tdb' Apr 26 04:48:56 192.168.122.209 [45887.013046] [tempesta fw] modules are stopped Apr 26 04:48:56 192.168.122.209 [45887.213451] [tempesta fw] exiting... Apr 26 04:48:56 192.168.122.209 [45887.332115] [tdb] Shutdown Tempesta DB Apr 26 04:48:57 192.168.122.209 [45887.536771] End test: t_frang.test_length.FrangLengthH2.test_http_hdr_len_no_huffman Apr 26 04:48:57 192.168.122.209 [45887.548897] Start test: t_frang.test_length.FrangLengthH2.test_http_hdr_len_without_reaching_the_limit_2_huffman Apr 26 04:48:58 192.168.122.209 [45888.639539] [tdb] Start Tempesta DB Apr 26 04:48:58 192.168.122.209 [45888.770596] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:48:59 192.168.122.209 [45889.475869] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45889.475869] Maybe that's fine, but it's worth checking the [45889.475869] config - if there is no relations between the [45889.475869] names, then host name confusion attack is possible. Apr 26 04:48:59 192.168.122.209 [45889.582862] [tempesta fw] Configuration processing is completed. Apr 26 04:48:59 192.168.122.209 [45889.638206] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:48:59 192.168.122.209 [45889.665776] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:48:59 192.168.122.209 [45889.692304] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:48:59 192.168.122.209 [45889.738647] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:48:59 192.168.122.209 [45889.739999] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:48:59 192.168.122.209 [45889.741605] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:48:59 192.168.122.209 [45889.786599] [tempesta fw] Tempesta FW is ready Apr 26 04:49:00 192.168.122.209 [45890.421506] [tdb] Close table 'client0.tdb' Apr 26 04:49:00 192.168.122.209 [45890.609356] [tdb] Close table 'sessions0.tdb' Apr 26 04:49:00 192.168.122.209 [45890.832499] [tdb] Close table 'filter0.tdb' Apr 26 04:49:00 192.168.122.209 [45890.832932] [tempesta fw] modules are stopped Apr 26 04:49:00 192.168.122.209 [45891.064987] [tempesta fw] exiting... Apr 26 04:49:00 192.168.122.209 [45891.191078] [tdb] Shutdown Tempesta DB Apr 26 04:49:01 192.168.122.209 [45891.386341] End test: t_frang.test_length.FrangLengthH2.test_http_hdr_len_without_reaching_the_limit_2_huffman Apr 26 04:49:01 192.168.122.209 [45891.398448] Start test: t_frang.test_length.FrangLengthH2.test_http_hdr_len_without_reaching_the_limit_2_no_huffman Apr 26 04:49:02 192.168.122.209 [45892.594955] [tdb] Start Tempesta DB Apr 26 04:49:02 192.168.122.209 [45892.724630] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:49:03 192.168.122.209 [45893.503938] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45893.503938] Maybe that's fine, but it's worth checking the [45893.503938] config - if there is no relations between the [45893.503938] names, then host name confusion attack is possible. Apr 26 04:49:03 192.168.122.209 [45893.606700] [tempesta fw] Configuration processing is completed. Apr 26 04:49:03 192.168.122.209 [45893.656624] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:49:03 192.168.122.209 [45893.684375] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:49:03 192.168.122.209 [45893.714525] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:49:03 192.168.122.209 [45893.762597] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:49:03 192.168.122.209 [45893.763978] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:49:03 192.168.122.209 [45893.765604] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:49:03 192.168.122.209 [45893.818664] [tempesta fw] Tempesta FW is ready Apr 26 04:49:04 192.168.122.209 [45894.475363] [tdb] Close table 'client0.tdb' Apr 26 04:49:04 192.168.122.209 [45894.666516] [tdb] Close table 'sessions0.tdb' Apr 26 04:49:04 192.168.122.209 [45894.919192] [tdb] Close table 'filter0.tdb' Apr 26 04:49:04 192.168.122.209 [45894.919632] [tempesta fw] modules are stopped Apr 26 04:49:04 192.168.122.209 [45895.133319] [tempesta fw] exiting... Apr 26 04:49:04 192.168.122.209 [45895.275873] [tdb] Shutdown Tempesta DB Apr 26 04:49:05 192.168.122.209 [45895.471120] End test: t_frang.test_length.FrangLengthH2.test_http_hdr_len_without_reaching_the_limit_2_no_huffman Apr 26 04:49:05 192.168.122.209 [45895.485543] Start test: t_frang.test_length.FrangLengthH2.test_http_hdr_len_without_reaching_the_limit_huffman Apr 26 04:49:06 192.168.122.209 [45896.660092] [tdb] Start Tempesta DB Apr 26 04:49:06 192.168.122.209 [45896.800032] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:49:07 192.168.122.209 [45897.492038] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45897.492038] Maybe that's fine, but it's worth checking the [45897.492038] config - if there is no relations between the [45897.492038] names, then host name confusion attack is possible. Apr 26 04:49:07 192.168.122.209 [45897.606723] [tempesta fw] Configuration processing is completed. Apr 26 04:49:07 192.168.122.209 [45897.657132] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:49:07 192.168.122.209 [45897.686499] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:49:07 192.168.122.209 [45897.713173] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:49:07 192.168.122.209 [45897.806738] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:49:07 192.168.122.209 [45897.808435] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:49:07 192.168.122.209 [45897.810100] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:49:07 192.168.122.209 [45897.866688] [tempesta fw] Tempesta FW is ready Apr 26 04:49:08 192.168.122.209 [45898.477528] [tdb] Close table 'client0.tdb' Apr 26 04:49:08 192.168.122.209 [45898.665042] [tdb] Close table 'sessions0.tdb' Apr 26 04:49:08 192.168.122.209 [45898.908878] [tdb] Close table 'filter0.tdb' Apr 26 04:49:08 192.168.122.209 [45898.909307] [tempesta fw] modules are stopped Apr 26 04:49:08 192.168.122.209 [45899.123525] [tempesta fw] exiting... Apr 26 04:49:08 192.168.122.209 [45899.272363] [tdb] Shutdown Tempesta DB Apr 26 04:49:09 192.168.122.209 [45899.519915] End test: t_frang.test_length.FrangLengthH2.test_http_hdr_len_without_reaching_the_limit_huffman Apr 26 04:49:09 192.168.122.209 [45899.529038] Start test: t_frang.test_length.FrangLengthH2.test_http_hdr_len_without_reaching_the_limit_no_huffman Apr 26 04:49:10 192.168.122.209 [45900.664426] [tdb] Start Tempesta DB Apr 26 04:49:10 192.168.122.209 [45900.806770] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:49:11 192.168.122.209 [45901.532204] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45901.532204] Maybe that's fine, but it's worth checking the [45901.532204] config - if there is no relations between the [45901.532204] names, then host name confusion attack is possible. Apr 26 04:49:11 192.168.122.209 [45901.650820] [tempesta fw] Configuration processing is completed. Apr 26 04:49:11 192.168.122.209 [45901.702698] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:49:11 192.168.122.209 [45901.731136] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:49:11 192.168.122.209 [45901.758195] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:49:11 192.168.122.209 [45901.802727] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:49:11 192.168.122.209 [45901.803757] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:49:11 192.168.122.209 [45901.805044] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:49:11 192.168.122.209 [45901.850749] [tempesta fw] Tempesta FW is ready Apr 26 04:49:12 192.168.122.209 [45902.498191] [tdb] Close table 'client0.tdb' Apr 26 04:49:12 192.168.122.209 [45902.694033] [tdb] Close table 'sessions0.tdb' Apr 26 04:49:12 192.168.122.209 [45902.934420] [tdb] Close table 'filter0.tdb' Apr 26 04:49:12 192.168.122.209 [45902.934865] [tempesta fw] modules are stopped Apr 26 04:49:12 192.168.122.209 [45903.111384] [tempesta fw] exiting... Apr 26 04:49:12 192.168.122.209 [45903.263040] [tdb] Shutdown Tempesta DB Apr 26 04:49:13 192.168.122.209 [45903.456421] End test: t_frang.test_length.FrangLengthH2.test_http_hdr_len_without_reaching_the_limit_no_huffman Apr 26 04:49:13 192.168.122.209 [45903.480678] Start test: t_frang.test_length.FrangLengthH2.test_uri_len Apr 26 04:49:14 192.168.122.209 [45904.649197] [tdb] Start Tempesta DB Apr 26 04:49:14 192.168.122.209 [45904.782236] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:49:15 192.168.122.209 [45905.561340] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45905.561340] Maybe that's fine, but it's worth checking the [45905.561340] config - if there is no relations between the [45905.561340] names, then host name confusion attack is possible. Apr 26 04:49:15 192.168.122.209 [45905.658886] [tempesta fw] Configuration processing is completed. Apr 26 04:49:15 192.168.122.209 [45905.715948] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:49:15 192.168.122.209 [45905.744041] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:49:15 192.168.122.209 [45905.771823] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:49:15 192.168.122.209 [45905.818782] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:49:15 192.168.122.209 [45905.819925] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:49:15 192.168.122.209 [45905.821096] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:49:15 192.168.122.209 [45905.858747] [tempesta fw] Tempesta FW is ready Apr 26 04:49:15 192.168.122.209 [45905.996096] [tempesta fw] Warning: frang: HTTP URI length exceeded for 127.0.0.2: 10 (lim=5) Apr 26 04:49:15 192.168.122.209 [45905.998433] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:49:16 192.168.122.209 [45906.526929] [tdb] Close table 'client0.tdb' Apr 26 04:49:16 192.168.122.209 [45906.715583] [tdb] Close table 'sessions0.tdb' Apr 26 04:49:16 192.168.122.209 [45906.953449] [tdb] Close table 'filter0.tdb' Apr 26 04:49:16 192.168.122.209 [45906.953904] [tempesta fw] modules are stopped Apr 26 04:49:16 192.168.122.209 [45907.126286] [tempesta fw] exiting... Apr 26 04:49:16 192.168.122.209 [45907.287278] [tdb] Shutdown Tempesta DB Apr 26 04:49:17 192.168.122.209 [45907.459334] End test: t_frang.test_length.FrangLengthH2.test_uri_len Apr 26 04:49:17 192.168.122.209 [45907.470948] Start test: t_frang.test_length.FrangLengthH2.test_uri_len_on_the_limit Apr 26 04:49:18 192.168.122.209 [45908.625917] [tdb] Start Tempesta DB Apr 26 04:49:18 192.168.122.209 [45908.762875] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:49:19 192.168.122.209 [45909.544135] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45909.544135] Maybe that's fine, but it's worth checking the [45909.544135] config - if there is no relations between the [45909.544135] names, then host name confusion attack is possible. Apr 26 04:49:19 192.168.122.209 [45909.655020] [tempesta fw] Configuration processing is completed. Apr 26 04:49:19 192.168.122.209 [45909.706479] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:49:19 192.168.122.209 [45909.736218] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:49:19 192.168.122.209 [45909.763405] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:49:19 192.168.122.209 [45909.846887] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:49:19 192.168.122.209 [45909.848551] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:49:19 192.168.122.209 [45909.850188] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:49:19 192.168.122.209 [45909.886836] [tempesta fw] Tempesta FW is ready Apr 26 04:49:20 192.168.122.209 [45910.542073] [tdb] Close table 'client0.tdb' Apr 26 04:49:20 192.168.122.209 [45910.728842] [tdb] Close table 'sessions0.tdb' Apr 26 04:49:20 192.168.122.209 [45910.957516] [tdb] Close table 'filter0.tdb' Apr 26 04:49:20 192.168.122.209 [45910.957948] [tempesta fw] modules are stopped Apr 26 04:49:20 192.168.122.209 [45911.160045] [tempesta fw] exiting... Apr 26 04:49:20 192.168.122.209 [45911.320907] [tdb] Shutdown Tempesta DB Apr 26 04:49:21 192.168.122.209 [45911.509748] End test: t_frang.test_length.FrangLengthH2.test_uri_len_on_the_limit Apr 26 04:49:21 192.168.122.209 [45911.530020] Start test: t_frang.test_length.FrangLengthH2.test_uri_len_without_reaching_the_limit Apr 26 04:49:22 192.168.122.209 [45912.669309] [tdb] Start Tempesta DB Apr 26 04:49:22 192.168.122.209 [45912.802417] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:49:23 192.168.122.209 [45913.579235] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45913.579235] Maybe that's fine, but it's worth checking the [45913.579235] config - if there is no relations between the [45913.579235] names, then host name confusion attack is possible. Apr 26 04:49:23 192.168.122.209 [45913.667282] [tempesta fw] Configuration processing is completed. Apr 26 04:49:23 192.168.122.209 [45913.729100] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:49:23 192.168.122.209 [45913.756748] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:49:23 192.168.122.209 [45913.783670] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:49:23 192.168.122.209 [45913.822853] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:49:23 192.168.122.209 [45913.823896] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:49:23 192.168.122.209 [45913.824925] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:49:23 192.168.122.209 [45913.870860] [tempesta fw] Tempesta FW is ready Apr 26 04:49:24 192.168.122.209 [45914.524323] [tdb] Close table 'client0.tdb' Apr 26 04:49:24 192.168.122.209 [45914.718192] [tdb] Close table 'sessions0.tdb' Apr 26 04:49:24 192.168.122.209 [45914.933992] [tdb] Close table 'filter0.tdb' Apr 26 04:49:24 192.168.122.209 [45914.934434] [tempesta fw] modules are stopped Apr 26 04:49:24 192.168.122.209 [45915.119460] [tempesta fw] exiting... Apr 26 04:49:24 192.168.122.209 [45915.258926] [tdb] Shutdown Tempesta DB Apr 26 04:49:25 192.168.122.209 [45915.473448] End test: t_frang.test_length.FrangLengthH2.test_uri_len_without_reaching_the_limit Apr 26 04:49:25 192.168.122.209 [45915.484217] Start test: t_frang.test_length.FrangLengthTestCase.test_body_len Apr 26 04:49:26 192.168.122.209 [45916.705536] [tdb] Start Tempesta DB Apr 26 04:49:26 192.168.122.209 [45916.840605] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:49:27 192.168.122.209 [45917.588218] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45917.588218] Maybe that's fine, but it's worth checking the [45917.588218] config - if there is no relations between the [45917.588218] names, then host name confusion attack is possible. Apr 26 04:49:27 192.168.122.209 [45917.694997] [tempesta fw] Configuration processing is completed. Apr 26 04:49:27 192.168.122.209 [45917.744473] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:49:27 192.168.122.209 [45917.773232] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:49:27 192.168.122.209 [45917.802699] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:49:27 192.168.122.209 [45917.843001] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:49:27 192.168.122.209 [45917.844714] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:49:27 192.168.122.209 [45917.846368] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:49:27 192.168.122.209 [45917.886964] [tempesta fw] Tempesta FW is ready Apr 26 04:49:27 192.168.122.209 [45918.012667] [tempesta fw] Warning: frang: HTTP body length exceeded for 127.0.0.2: 20 (lim=10) Apr 26 04:49:27 192.168.122.209 [45918.014456] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:49:28 192.168.122.209 [45918.527585] [tdb] Close table 'client0.tdb' Apr 26 04:49:28 192.168.122.209 [45918.728404] [tdb] Close table 'sessions0.tdb' Apr 26 04:49:28 192.168.122.209 [45918.970717] [tdb] Close table 'filter0.tdb' Apr 26 04:49:28 192.168.122.209 [45918.971173] [tempesta fw] modules are stopped Apr 26 04:49:28 192.168.122.209 [45919.218988] [tempesta fw] exiting... Apr 26 04:49:28 192.168.122.209 [45919.338683] [tdb] Shutdown Tempesta DB Apr 26 04:49:29 192.168.122.209 [45919.534480] End test: t_frang.test_length.FrangLengthTestCase.test_body_len Apr 26 04:49:29 192.168.122.209 [45919.549567] Start test: t_frang.test_length.FrangLengthTestCase.test_body_len_without_reaching_the_limit Apr 26 04:49:30 192.168.122.209 [45920.814432] [tdb] Start Tempesta DB Apr 26 04:49:30 192.168.122.209 [45920.958133] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:49:31 192.168.122.209 [45921.676286] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45921.676286] Maybe that's fine, but it's worth checking the [45921.676286] config - if there is no relations between the [45921.676286] names, then host name confusion attack is possible. Apr 26 04:49:31 192.168.122.209 [45921.775057] [tempesta fw] Configuration processing is completed. Apr 26 04:49:31 192.168.122.209 [45921.825460] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:49:31 192.168.122.209 [45921.853670] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:49:31 192.168.122.209 [45921.880788] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:49:31 192.168.122.209 [45921.967043] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:49:31 192.168.122.209 [45921.968765] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:49:31 192.168.122.209 [45921.970404] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:49:31 192.168.122.209 [45922.006988] [tempesta fw] Tempesta FW is ready Apr 26 04:49:32 192.168.122.209 [45922.673232] [tdb] Close table 'client0.tdb' Apr 26 04:49:32 192.168.122.209 [45922.865542] [tdb] Close table 'sessions0.tdb' Apr 26 04:49:32 192.168.122.209 [45923.111900] [tdb] Close table 'filter0.tdb' Apr 26 04:49:32 192.168.122.209 [45923.112347] [tempesta fw] modules are stopped Apr 26 04:49:32 192.168.122.209 [45923.292156] [tempesta fw] exiting... Apr 26 04:49:33 192.168.122.209 [45923.418883] [tdb] Shutdown Tempesta DB Apr 26 04:49:33 192.168.122.209 [45923.614261] End test: t_frang.test_length.FrangLengthTestCase.test_body_len_without_reaching_the_limit Apr 26 04:49:33 192.168.122.209 [45923.624650] Start test: t_frang.test_length.FrangLengthTestCase.test_body_len_without_reaching_the_limit_zero_len Apr 26 04:49:34 192.168.122.209 [45924.852117] [tdb] Start Tempesta DB Apr 26 04:49:34 192.168.122.209 [45924.980013] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:49:35 192.168.122.209 [45925.796384] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45925.796384] Maybe that's fine, but it's worth checking the [45925.796384] config - if there is no relations between the [45925.796384] names, then host name confusion attack is possible. Apr 26 04:49:35 192.168.122.209 [45925.907136] [tempesta fw] Configuration processing is completed. Apr 26 04:49:35 192.168.122.209 [45925.967151] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:49:35 192.168.122.209 [45925.995024] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:49:35 192.168.122.209 [45926.022005] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:49:35 192.168.122.209 [45926.087098] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:49:35 192.168.122.209 [45926.088764] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:49:35 192.168.122.209 [45926.090416] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:49:35 192.168.122.209 [45926.131042] [tempesta fw] Tempesta FW is ready Apr 26 04:49:36 192.168.122.209 [45926.765193] [tdb] Close table 'client0.tdb' Apr 26 04:49:36 192.168.122.209 [45926.951173] [tdb] Close table 'sessions0.tdb' Apr 26 04:49:36 192.168.122.209 [45927.171961] [tdb] Close table 'filter0.tdb' Apr 26 04:49:36 192.168.122.209 [45927.172388] [tempesta fw] modules are stopped Apr 26 04:49:36 192.168.122.209 [45927.362328] [tempesta fw] exiting... Apr 26 04:49:37 192.168.122.209 [45927.511280] [tdb] Shutdown Tempesta DB Apr 26 04:49:37 192.168.122.209 [45927.720029] End test: t_frang.test_length.FrangLengthTestCase.test_body_len_without_reaching_the_limit_zero_len Apr 26 04:49:37 192.168.122.209 [45927.734453] Start test: t_frang.test_length.FrangLengthTestCase.test_http_hdr_len Apr 26 04:49:38 192.168.122.209 [45928.966365] [tdb] Start Tempesta DB Apr 26 04:49:38 192.168.122.209 [45929.108638] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:49:39 192.168.122.209 [45929.920434] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45929.920434] Maybe that's fine, but it's worth checking the [45929.920434] config - if there is no relations between the [45929.920434] names, then host name confusion attack is possible. Apr 26 04:49:39 192.168.122.209 [45930.023163] [tempesta fw] Configuration processing is completed. Apr 26 04:49:39 192.168.122.209 [45930.082831] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:49:39 192.168.122.209 [45930.113542] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:49:39 192.168.122.209 [45930.140491] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:49:39 192.168.122.209 [45930.183173] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:49:39 192.168.122.209 [45930.184844] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:49:39 192.168.122.209 [45930.186483] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:49:39 192.168.122.209 [45930.227102] [tempesta fw] Tempesta FW is ready Apr 26 04:49:39 192.168.122.209 [45930.361207] [tempesta fw] Warning: frang: HTTP header length exceeded for 127.0.0.2: 328 (lim=300) Apr 26 04:49:40 192.168.122.209 [45930.883570] [tdb] Close table 'client0.tdb' Apr 26 04:49:40 192.168.122.209 [45931.075073] [tdb] Close table 'sessions0.tdb' Apr 26 04:49:40 192.168.122.209 [45931.314568] [tdb] Close table 'filter0.tdb' Apr 26 04:49:40 192.168.122.209 [45931.315018] [tempesta fw] modules are stopped Apr 26 04:49:41 192.168.122.209 [45931.531046] [tempesta fw] exiting... Apr 26 04:49:41 192.168.122.209 [45931.653578] [tdb] Shutdown Tempesta DB Apr 26 04:49:41 192.168.122.209 [45931.844778] End test: t_frang.test_length.FrangLengthTestCase.test_http_hdr_len Apr 26 04:49:41 192.168.122.209 [45931.864440] Start test: t_frang.test_length.FrangLengthTestCase.test_http_hdr_len_without_reaching_the_limit Apr 26 04:49:42 192.168.122.209 [45933.050254] [tdb] Start Tempesta DB Apr 26 04:49:42 192.168.122.209 [45933.192302] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:49:43 192.168.122.209 [45933.956447] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45933.956447] Maybe that's fine, but it's worth checking the [45933.956447] config - if there is no relations between the [45933.956447] names, then host name confusion attack is possible. Apr 26 04:49:43 192.168.122.209 [45934.055422] [tempesta fw] Configuration processing is completed. Apr 26 04:49:43 192.168.122.209 [45934.109626] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:49:43 192.168.122.209 [45934.137897] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:49:43 192.168.122.209 [45934.165291] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:49:43 192.168.122.209 [45934.207199] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:49:43 192.168.122.209 [45934.208876] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:49:43 192.168.122.209 [45934.210540] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:49:43 192.168.122.209 [45934.247147] [tempesta fw] Tempesta FW is ready Apr 26 04:49:44 192.168.122.209 [45934.875331] [tdb] Close table 'client0.tdb' Apr 26 04:49:44 192.168.122.209 [45935.058752] [tdb] Close table 'sessions0.tdb' Apr 26 04:49:44 192.168.122.209 [45935.298796] [tdb] Close table 'filter0.tdb' Apr 26 04:49:44 192.168.122.209 [45935.299600] [tempesta fw] modules are stopped Apr 26 04:49:45 192.168.122.209 [45935.526325] [tempesta fw] exiting... Apr 26 04:49:45 192.168.122.209 [45935.647857] [tdb] Shutdown Tempesta DB Apr 26 04:49:45 192.168.122.209 [45935.853511] End test: t_frang.test_length.FrangLengthTestCase.test_http_hdr_len_without_reaching_the_limit Apr 26 04:49:45 192.168.122.209 [45935.863903] Start test: t_frang.test_length.FrangLengthTestCase.test_http_hdr_len_without_reaching_the_limit_2 Apr 26 04:49:46 192.168.122.209 [45937.089514] [tdb] Start Tempesta DB Apr 26 04:49:46 192.168.122.209 [45937.232506] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:49:47 192.168.122.209 [45937.984502] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45937.984502] Maybe that's fine, but it's worth checking the [45937.984502] config - if there is no relations between the [45937.984502] names, then host name confusion attack is possible. Apr 26 04:49:47 192.168.122.209 [45938.083266] [tempesta fw] Configuration processing is completed. Apr 26 04:49:47 192.168.122.209 [45938.138740] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:49:47 192.168.122.209 [45938.168749] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:49:47 192.168.122.209 [45938.204521] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:49:47 192.168.122.209 [45938.251245] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:49:47 192.168.122.209 [45938.252595] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:49:47 192.168.122.209 [45938.253966] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:49:47 192.168.122.209 [45938.291202] [tempesta fw] Tempesta FW is ready Apr 26 04:49:48 192.168.122.209 [45938.950589] [tdb] Close table 'client0.tdb' Apr 26 04:49:48 192.168.122.209 [45939.141319] [tdb] Close table 'sessions0.tdb' Apr 26 04:49:49 192.168.122.209 [45939.390140] [tdb] Close table 'filter0.tdb' Apr 26 04:49:49 192.168.122.209 [45939.390592] [tempesta fw] modules are stopped Apr 26 04:49:49 192.168.122.209 [45939.657049] [tempesta fw] exiting... Apr 26 04:49:49 192.168.122.209 [45939.788062] [tdb] Shutdown Tempesta DB Apr 26 04:49:49 192.168.122.209 [45939.981129] End test: t_frang.test_length.FrangLengthTestCase.test_http_hdr_len_without_reaching_the_limit_2 Apr 26 04:49:49 192.168.122.209 [45939.997637] Start test: t_frang.test_length.FrangLengthTestCase.test_uri_len Apr 26 04:49:50 192.168.122.209 [45941.149485] [tdb] Start Tempesta DB Apr 26 04:49:50 192.168.122.209 [45941.272492] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:49:51 192.168.122.209 [45942.032576] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45942.032576] Maybe that's fine, but it's worth checking the [45942.032576] config - if there is no relations between the [45942.032576] names, then host name confusion attack is possible. Apr 26 04:49:51 192.168.122.209 [45942.135330] [tempesta fw] Configuration processing is completed. Apr 26 04:49:51 192.168.122.209 [45942.186940] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:49:51 192.168.122.209 [45942.215240] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:49:51 192.168.122.209 [45942.253419] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:49:51 192.168.122.209 [45942.295238] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:49:51 192.168.122.209 [45942.296350] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:49:51 192.168.122.209 [45942.297651] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:49:51 192.168.122.209 [45942.339263] [tempesta fw] Tempesta FW is ready Apr 26 04:49:52 192.168.122.209 [45942.458993] [tempesta fw] Warning: frang: HTTP URI length exceeded for 127.0.0.2: 10 (lim=5) Apr 26 04:49:52 192.168.122.209 [45942.461371] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:49:52 192.168.122.209 [45943.005088] [tdb] Close table 'client0.tdb' Apr 26 04:49:52 192.168.122.209 [45943.190850] [tdb] Close table 'sessions0.tdb' Apr 26 04:49:53 192.168.122.209 [45943.434685] [tdb] Close table 'filter0.tdb' Apr 26 04:49:53 192.168.122.209 [45943.435137] [tempesta fw] modules are stopped Apr 26 04:49:53 192.168.122.209 [45943.638708] [tempesta fw] exiting... Apr 26 04:49:53 192.168.122.209 [45943.754776] [tdb] Shutdown Tempesta DB Apr 26 04:49:53 192.168.122.209 [45943.963456] End test: t_frang.test_length.FrangLengthTestCase.test_uri_len Apr 26 04:49:53 192.168.122.209 [45943.976676] Start test: t_frang.test_length.FrangLengthTestCase.test_uri_len_on_the_limit Apr 26 04:49:54 192.168.122.209 [45945.158951] [tdb] Start Tempesta DB Apr 26 04:49:54 192.168.122.209 [45945.299256] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:49:55 192.168.122.209 [45946.056623] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45946.056623] Maybe that's fine, but it's worth checking the [45946.056623] config - if there is no relations between the [45946.056623] names, then host name confusion attack is possible. Apr 26 04:49:55 192.168.122.209 [45946.163386] [tempesta fw] Configuration processing is completed. Apr 26 04:49:55 192.168.122.209 [45946.222693] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:49:55 192.168.122.209 [45946.258729] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:49:55 192.168.122.209 [45946.289512] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:49:55 192.168.122.209 [45946.331347] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:49:55 192.168.122.209 [45946.333034] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:49:55 192.168.122.209 [45946.334687] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:49:56 192.168.122.209 [45946.391293] [tempesta fw] Tempesta FW is ready Apr 26 04:49:56 192.168.122.209 [45947.081030] [tdb] Close table 'client0.tdb' Apr 26 04:49:56 192.168.122.209 [45947.270703] [tdb] Close table 'sessions0.tdb' Apr 26 04:49:57 192.168.122.209 [45947.522300] [tdb] Close table 'filter0.tdb' Apr 26 04:49:57 192.168.122.209 [45947.522745] [tempesta fw] modules are stopped Apr 26 04:49:57 192.168.122.209 [45947.711308] [tempesta fw] exiting... Apr 26 04:49:57 192.168.122.209 [45947.863758] [tdb] Shutdown Tempesta DB Apr 26 04:49:57 192.168.122.209 [45948.065075] End test: t_frang.test_length.FrangLengthTestCase.test_uri_len_on_the_limit Apr 26 04:49:57 192.168.122.209 [45948.077228] Start test: t_frang.test_length.FrangLengthTestCase.test_uri_len_without_reaching_the_limit Apr 26 04:49:58 192.168.122.209 [45949.237041] [tdb] Start Tempesta DB Apr 26 04:49:58 192.168.122.209 [45949.360827] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:49:59 192.168.122.209 [45950.107805] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45950.107805] Maybe that's fine, but it's worth checking the [45950.107805] config - if there is no relations between the [45950.107805] names, then host name confusion attack is possible. Apr 26 04:49:59 192.168.122.209 [45950.203422] [tempesta fw] Configuration processing is completed. Apr 26 04:49:59 192.168.122.209 [45950.255576] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:49:59 192.168.122.209 [45950.296722] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:49:59 192.168.122.209 [45950.323047] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:49:59 192.168.122.209 [45950.367373] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:49:59 192.168.122.209 [45950.368743] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:49:59 192.168.122.209 [45950.370051] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:50:00 192.168.122.209 [45950.407309] [tempesta fw] Tempesta FW is ready Apr 26 04:50:00 192.168.122.209 [45951.046527] [tdb] Close table 'client0.tdb' Apr 26 04:50:00 192.168.122.209 [45951.245640] [tdb] Close table 'sessions0.tdb' Apr 26 04:50:01 192.168.122.209 [45951.472266] [tdb] Close table 'filter0.tdb' Apr 26 04:50:01 192.168.122.209 [45951.472706] [tempesta fw] modules are stopped Apr 26 04:50:01 192.168.122.209 [45951.667628] [tempesta fw] exiting... Apr 26 04:50:01 192.168.122.209 [45951.821710] [tdb] Shutdown Tempesta DB Apr 26 04:50:01 192.168.122.209 [45952.058387] End test: t_frang.test_length.FrangLengthTestCase.test_uri_len_without_reaching_the_limit Apr 26 04:50:01 192.168.122.209 [45952.069322] Start test: t_frang.test_request_rate_burst.TestFrangRapidDDoSH2.test_request_burst_with_only_headers_frame Apr 26 04:50:02 192.168.122.209 [45953.218033] [tdb] Start Tempesta DB Apr 26 04:50:02 192.168.122.209 [45953.353766] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:50:03 192.168.122.209 [45954.120755] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45954.120755] Maybe that's fine, but it's worth checking the [45954.120755] config - if there is no relations between the [45954.120755] names, then host name confusion attack is possible. Apr 26 04:50:03 192.168.122.209 [45954.231570] [tempesta fw] Configuration processing is completed. Apr 26 04:50:03 192.168.122.209 [45954.289887] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:50:03 192.168.122.209 [45954.322927] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:50:03 192.168.122.209 [45954.350748] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:50:04 192.168.122.209 [45954.395413] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:50:04 192.168.122.209 [45954.396650] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:50:04 192.168.122.209 [45954.397823] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:50:04 192.168.122.209 [45954.435413] [tempesta fw] Tempesta FW is ready Apr 26 04:50:08 192.168.122.209 [45959.134395] [tempesta fw] Warning: frang: requests burst exceeded for 127.0.0.2: 6 (lim=5) Apr 26 04:50:08 192.168.122.209 [45959.135170] [tempesta fw] Warning: postponed request has been filtered out: 127.0.0.2 Apr 26 04:50:09 192.168.122.209 [45959.647342] [tdb] Close table 'client0.tdb' Apr 26 04:50:09 192.168.122.209 [45959.843689] [tdb] Close table 'sessions0.tdb' Apr 26 04:50:09 192.168.122.209 [45960.089695] [tdb] Close table 'filter0.tdb' Apr 26 04:50:09 192.168.122.209 [45960.090139] [tempesta fw] modules are stopped Apr 26 04:50:09 192.168.122.209 [45960.324740] [tempesta fw] exiting... Apr 26 04:50:10 192.168.122.209 [45960.458871] [tdb] Shutdown Tempesta DB Apr 26 04:50:10 192.168.122.209 [45960.681431] End test: t_frang.test_request_rate_burst.TestFrangRapidDDoSH2.test_request_burst_with_only_headers_frame Apr 26 04:50:10 192.168.122.209 [45960.701112] Start test: t_frang.test_request_rate_burst.TestFrangRapidDDoSH2.test_request_rate_with_only_headers_frame Apr 26 04:50:11 192.168.122.209 [45961.866489] [tdb] Start Tempesta DB Apr 26 04:50:11 192.168.122.209 [45961.999313] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:50:12 192.168.122.209 [45962.756828] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45962.756828] Maybe that's fine, but it's worth checking the [45962.756828] config - if there is no relations between the [45962.756828] names, then host name confusion attack is possible. Apr 26 04:50:12 192.168.122.209 [45962.855575] [tempesta fw] Configuration processing is completed. Apr 26 04:50:12 192.168.122.209 [45962.923884] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:50:12 192.168.122.209 [45962.953865] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:50:12 192.168.122.209 [45962.981116] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:50:12 192.168.122.209 [45963.035556] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:50:12 192.168.122.209 [45963.037244] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:50:12 192.168.122.209 [45963.038878] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:50:12 192.168.122.209 [45963.079535] [tempesta fw] Tempesta FW is ready Apr 26 04:50:17 192.168.122.209 [45967.778585] [tempesta fw] Warning: frang: request rate exceeded for 127.0.0.2: 6 (lim=5) Apr 26 04:50:17 192.168.122.209 [45967.779343] [tempesta fw] Warning: postponed request has been filtered out: 127.0.0.2 Apr 26 04:50:17 192.168.122.209 [45968.322411] [tdb] Close table 'client0.tdb' Apr 26 04:50:18 192.168.122.209 [45968.501612] [tdb] Close table 'sessions0.tdb' Apr 26 04:50:18 192.168.122.209 [45968.766920] [tdb] Close table 'filter0.tdb' Apr 26 04:50:18 192.168.122.209 [45968.767354] [tempesta fw] modules are stopped Apr 26 04:50:18 192.168.122.209 [45968.955385] [tempesta fw] exiting... Apr 26 04:50:18 192.168.122.209 [45969.085776] [tdb] Shutdown Tempesta DB Apr 26 04:50:18 192.168.122.209 [45969.300826] End test: t_frang.test_request_rate_burst.TestFrangRapidDDoSH2.test_request_rate_with_only_headers_frame Apr 26 04:50:18 192.168.122.209 [45969.312428] Start test: t_frang.test_request_rate_burst.TestFrangRequestBurstH2.test_two_clients_one_ip Apr 26 04:50:20 192.168.122.209 [45970.592511] [tdb] Start Tempesta DB Apr 26 04:50:20 192.168.122.209 [45970.734360] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:50:21 192.168.122.209 [45971.436962] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45971.436962] Maybe that's fine, but it's worth checking the [45971.436962] config - if there is no relations between the [45971.436962] names, then host name confusion attack is possible. Apr 26 04:50:21 192.168.122.209 [45971.503739] [tempesta fw] Configuration processing is completed. Apr 26 04:50:21 192.168.122.209 [45971.558723] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:50:21 192.168.122.209 [45972.167530] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:50:21 192.168.122.209 [45972.196013] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:50:21 192.168.122.209 [45972.227858] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:50:21 192.168.122.209 [45972.311883] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:50:21 192.168.122.209 [45972.313639] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:50:21 192.168.122.209 [45972.363627] [tempesta fw] Tempesta FW is ready Apr 26 04:50:26 192.168.122.209 [45977.046025] [tempesta fw] Warning: frang: requests burst exceeded for 127.0.0.2: 5 (lim=4) Apr 26 04:50:26 192.168.122.209 [45977.047196] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:50:26 192.168.122.209 [45977.047205] [tempesta fw] Warning: frang: requests burst exceeded for 127.0.0.2: 6 (lim=4) Apr 26 04:50:26 192.168.122.209 [45977.048306] [tempesta fw] Warning: block client: 127.0.0.2 Apr 26 04:50:26 192.168.122.209 [45977.049044] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:50:26 192.168.122.209 [45977.050500] [tempesta fw] Warning: block client: 127.0.0.2 Apr 26 04:50:32 192.168.122.209 [45983.195508] [tdb] Close table 'client0.tdb' Apr 26 04:50:33 192.168.122.209 [45983.395460] [tdb] Close table 'sessions0.tdb' Apr 26 04:50:36 192.168.122.209 [45986.680603] [tdb] Close table 'cache0.tdb' Apr 26 04:50:36 192.168.122.209 [45986.910615] [tdb] Close table 'filter0.tdb' Apr 26 04:50:36 192.168.122.209 [45986.911060] [tempesta fw] modules are stopped Apr 26 04:50:36 192.168.122.209 [45987.096984] [tempesta fw] exiting... Apr 26 04:50:36 192.168.122.209 [45987.255246] [tdb] Shutdown Tempesta DB Apr 26 04:50:37 192.168.122.209 [45987.529207] End test: t_frang.test_request_rate_burst.TestFrangRequestBurstH2.test_two_clients_one_ip Apr 26 04:50:37 192.168.122.209 [45987.544284] Start test: t_frang.test_request_rate_burst.TestFrangRequestBurstH2.test_two_clients_two_ip Apr 26 04:50:38 192.168.122.209 [45988.735381] [tdb] Start Tempesta DB Apr 26 04:50:38 192.168.122.209 [45988.887984] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:50:39 192.168.122.209 [45990.361182] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [45990.361182] Maybe that's fine, but it's worth checking the [45990.361182] config - if there is no relations between the [45990.361182] names, then host name confusion attack is possible. Apr 26 04:50:40 192.168.122.209 [45990.431938] [tempesta fw] Configuration processing is completed. Apr 26 04:50:40 192.168.122.209 [45990.482951] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:50:40 192.168.122.209 [45990.892452] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:50:40 192.168.122.209 [45990.918202] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:50:40 192.168.122.209 [45990.943430] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:50:40 192.168.122.209 [45990.995929] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:50:40 192.168.122.209 [45990.997448] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:50:40 192.168.122.209 [45991.035873] [tempesta fw] Tempesta FW is ready Apr 26 04:50:45 192.168.122.209 [45995.705223] [tempesta fw] Warning: frang: requests burst exceeded for 192.168.123.2: 5 (lim=4) Apr 26 04:50:45 192.168.122.209 [45995.706433] [tempesta fw] Warning: parsed request has been filtered out: 192.168.123.2 Apr 26 04:50:45 192.168.122.209 [45995.707526] [tempesta fw] Warning: block client: 192.168.123.2 Apr 26 04:50:51 192.168.122.209 [46001.958656] [tdb] Close table 'client0.tdb' Apr 26 04:50:51 192.168.122.209 [46002.170997] [tdb] Close table 'sessions0.tdb' Apr 26 04:50:54 192.168.122.209 [46005.380084] [tdb] Close table 'cache0.tdb' Apr 26 04:50:55 192.168.122.209 [46005.623785] [tdb] Close table 'filter0.tdb' Apr 26 04:50:55 192.168.122.209 [46005.624242] [tempesta fw] modules are stopped Apr 26 04:50:55 192.168.122.209 [46005.864521] [tempesta fw] exiting... Apr 26 04:50:55 192.168.122.209 [46006.010619] [tdb] Shutdown Tempesta DB Apr 26 04:50:55 192.168.122.209 [46006.227876] End test: t_frang.test_request_rate_burst.TestFrangRequestBurstH2.test_two_clients_two_ip Apr 26 04:50:55 192.168.122.209 [46006.235034] Start test: t_frang.test_request_rate_burst.TestFrangRequestBurstHttp.test_two_clients_one_ip Apr 26 04:50:57 192.168.122.209 [46007.483028] [tdb] Start Tempesta DB Apr 26 04:50:57 192.168.122.209 [46007.608543] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:50:58 192.168.122.209 [46009.145382] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46009.145382] Maybe that's fine, but it's worth checking the [46009.145382] config - if there is no relations between the [46009.145382] names, then host name confusion attack is possible. Apr 26 04:50:58 192.168.122.209 [46009.212220] [tempesta fw] Configuration processing is completed. Apr 26 04:50:58 192.168.122.209 [46009.266108] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:50:59 192.168.122.209 [46009.682038] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:50:59 192.168.122.209 [46009.707718] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:50:59 192.168.122.209 [46009.732929] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:50:59 192.168.122.209 [46009.792159] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:50:59 192.168.122.209 [46009.793874] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:50:59 192.168.122.209 [46009.832112] [tempesta fw] Tempesta FW is ready Apr 26 04:51:04 192.168.122.209 [46014.543261] [tempesta fw] Warning: frang: requests burst exceeded for 127.0.0.2: 5 (lim=4) Apr 26 04:51:04 192.168.122.209 [46014.544176] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:51:04 192.168.122.209 [46014.544857] [tempesta fw] Warning: block client: 127.0.0.2 Apr 26 04:51:10 192.168.122.209 [46020.599632] [tdb] Close table 'client0.tdb' Apr 26 04:51:10 192.168.122.209 [46020.923926] [tdb] Close table 'sessions0.tdb' Apr 26 04:51:13 192.168.122.209 [46024.253194] [tdb] Close table 'cache0.tdb' Apr 26 04:51:14 192.168.122.209 [46024.492115] [tdb] Close table 'filter0.tdb' Apr 26 04:51:14 192.168.122.209 [46024.492565] [tempesta fw] modules are stopped Apr 26 04:51:14 192.168.122.209 [46024.671304] [tempesta fw] exiting... Apr 26 04:51:14 192.168.122.209 [46024.812960] [tdb] Shutdown Tempesta DB Apr 26 04:51:14 192.168.122.209 [46025.043575] End test: t_frang.test_request_rate_burst.TestFrangRequestBurstHttp.test_two_clients_one_ip Apr 26 04:51:14 192.168.122.209 [46025.054917] Start test: t_frang.test_request_rate_burst.TestFrangRequestBurstHttp.test_two_clients_two_ip Apr 26 04:51:15 192.168.122.209 [46026.279659] [tdb] Start Tempesta DB Apr 26 04:51:16 192.168.122.209 [46026.413001] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:51:17 192.168.122.209 [46027.893621] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46027.893621] Maybe that's fine, but it's worth checking the [46027.893621] config - if there is no relations between the [46027.893621] names, then host name confusion attack is possible. Apr 26 04:51:17 192.168.122.209 [46027.964389] [tempesta fw] Configuration processing is completed. Apr 26 04:51:17 192.168.122.209 [46028.015347] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:51:18 192.168.122.209 [46028.429320] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:51:18 192.168.122.209 [46028.455496] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:51:18 192.168.122.209 [46028.480373] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:51:18 192.168.122.209 [46028.520321] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:51:18 192.168.122.209 [46028.521364] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:51:18 192.168.122.209 [46028.564338] [tempesta fw] Tempesta FW is ready Apr 26 04:51:22 192.168.122.209 [46033.237325] [tempesta fw] Warning: frang: requests burst exceeded for 192.168.123.2: 5 (lim=4) Apr 26 04:51:22 192.168.122.209 [46033.239725] [tempesta fw] Warning: parsed request has been filtered out: 192.168.123.2 Apr 26 04:51:22 192.168.122.209 [46033.241942] [tempesta fw] Warning: block client: 192.168.123.2 Apr 26 04:51:28 192.168.122.209 [46039.332541] [tdb] Close table 'client0.tdb' Apr 26 04:51:29 192.168.122.209 [46039.528495] [tdb] Close table 'sessions0.tdb' Apr 26 04:51:32 192.168.122.209 [46042.669782] [tdb] Close table 'cache0.tdb' Apr 26 04:51:32 192.168.122.209 [46042.895410] [tdb] Close table 'filter0.tdb' Apr 26 04:51:32 192.168.122.209 [46042.895855] [tempesta fw] modules are stopped Apr 26 04:51:32 192.168.122.209 [46043.100582] [tempesta fw] exiting... Apr 26 04:51:32 192.168.122.209 [46043.224535] [tdb] Shutdown Tempesta DB Apr 26 04:51:33 192.168.122.209 [46043.435830] End test: t_frang.test_request_rate_burst.TestFrangRequestBurstHttp.test_two_clients_two_ip Apr 26 04:51:33 192.168.122.209 [46043.450849] Start test: t_frang.test_request_rate_burst.TestFrangRequestRateBurstH2.test_request_burst_on_the_limit Apr 26 04:51:34 192.168.122.209 [46044.675032] [tdb] Start Tempesta DB Apr 26 04:51:34 192.168.122.209 [46044.809068] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:51:35 192.168.122.209 [46046.357847] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46046.357847] Maybe that's fine, but it's worth checking the [46046.357847] config - if there is no relations between the [46046.357847] names, then host name confusion attack is possible. Apr 26 04:51:36 192.168.122.209 [46046.460673] [tempesta fw] Configuration processing is completed. Apr 26 04:51:36 192.168.122.209 [46046.513634] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:51:36 192.168.122.209 [46046.540826] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:51:36 192.168.122.209 [46046.567526] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:51:36 192.168.122.209 [46046.620604] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:51:36 192.168.122.209 [46046.621975] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:51:36 192.168.122.209 [46046.623487] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:51:36 192.168.122.209 [46046.664601] [tempesta fw] Tempesta FW is ready Apr 26 04:51:41 192.168.122.209 [46051.902607] [tdb] Close table 'client0.tdb' Apr 26 04:51:41 192.168.122.209 [46052.092579] [tdb] Close table 'sessions0.tdb' Apr 26 04:51:41 192.168.122.209 [46052.317921] [tdb] Close table 'filter0.tdb' Apr 26 04:51:41 192.168.122.209 [46052.318352] [tempesta fw] modules are stopped Apr 26 04:51:42 192.168.122.209 [46052.550521] [tempesta fw] exiting... Apr 26 04:51:42 192.168.122.209 [46052.707122] [tdb] Shutdown Tempesta DB Apr 26 04:51:42 192.168.122.209 [46052.925606] End test: t_frang.test_request_rate_burst.TestFrangRequestRateBurstH2.test_request_burst_on_the_limit Apr 26 04:51:42 192.168.122.209 [46052.937220] Start test: t_frang.test_request_rate_burst.TestFrangRequestRateBurstH2.test_request_burst_reached Apr 26 04:51:43 192.168.122.209 [46054.091717] [tdb] Start Tempesta DB Apr 26 04:51:43 192.168.122.209 [46054.235316] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:51:44 192.168.122.209 [46054.989962] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46054.989962] Maybe that's fine, but it's worth checking the [46054.989962] config - if there is no relations between the [46054.989962] names, then host name confusion attack is possible. Apr 26 04:51:44 192.168.122.209 [46055.096744] [tempesta fw] Configuration processing is completed. Apr 26 04:51:44 192.168.122.209 [46055.150829] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:51:44 192.168.122.209 [46055.178568] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:51:44 192.168.122.209 [46055.213024] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:51:44 192.168.122.209 [46055.260685] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:51:44 192.168.122.209 [46055.262290] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:51:44 192.168.122.209 [46055.263821] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:51:44 192.168.122.209 [46055.308676] [tempesta fw] Tempesta FW is ready Apr 26 04:51:49 192.168.122.209 [46059.932697] [tempesta fw] Warning: frang: requests burst exceeded for 127.0.0.2: 6 (lim=5) Apr 26 04:51:49 192.168.122.209 [46059.934985] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:51:50 192.168.122.209 [46060.490538] [tdb] Close table 'client0.tdb' Apr 26 04:51:50 192.168.122.209 [46060.684405] [tdb] Close table 'sessions0.tdb' Apr 26 04:51:50 192.168.122.209 [46060.918037] [tdb] Close table 'filter0.tdb' Apr 26 04:51:50 192.168.122.209 [46060.918475] [tempesta fw] modules are stopped Apr 26 04:51:50 192.168.122.209 [46061.146196] [tempesta fw] exiting... Apr 26 04:51:50 192.168.122.209 [46061.302714] [tdb] Shutdown Tempesta DB Apr 26 04:51:51 192.168.122.209 [46061.511313] End test: t_frang.test_request_rate_burst.TestFrangRequestRateBurstH2.test_request_burst_reached Apr 26 04:51:51 192.168.122.209 [46061.532553] Start test: t_frang.test_request_rate_burst.TestFrangRequestRateBurstH2.test_request_burst_without_reaching_the_limit Apr 26 04:51:52 192.168.122.209 [46062.805908] [tdb] Start Tempesta DB Apr 26 04:51:52 192.168.122.209 [46062.954561] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:51:53 192.168.122.209 [46063.730076] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46063.730076] Maybe that's fine, but it's worth checking the [46063.730076] config - if there is no relations between the [46063.730076] names, then host name confusion attack is possible. Apr 26 04:51:53 192.168.122.209 [46063.840871] [tempesta fw] Configuration processing is completed. Apr 26 04:51:53 192.168.122.209 [46063.892356] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:51:53 192.168.122.209 [46063.921333] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:51:53 192.168.122.209 [46063.948519] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:51:53 192.168.122.209 [46063.988780] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:51:53 192.168.122.209 [46063.989822] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:51:53 192.168.122.209 [46063.990819] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:51:53 192.168.122.209 [46064.028797] [tempesta fw] Tempesta FW is ready Apr 26 04:51:58 192.168.122.209 [46069.170822] [tdb] Close table 'client0.tdb' Apr 26 04:51:58 192.168.122.209 [46069.363782] [tdb] Close table 'sessions0.tdb' Apr 26 04:51:59 192.168.122.209 [46069.595374] [tdb] Close table 'filter0.tdb' Apr 26 04:51:59 192.168.122.209 [46069.595817] [tempesta fw] modules are stopped Apr 26 04:51:59 192.168.122.209 [46069.837080] [tempesta fw] exiting... Apr 26 04:51:59 192.168.122.209 [46069.983642] [tdb] Shutdown Tempesta DB Apr 26 04:51:59 192.168.122.209 [46070.180688] End test: t_frang.test_request_rate_burst.TestFrangRequestRateBurstH2.test_request_burst_without_reaching_the_limit Apr 26 04:51:59 192.168.122.209 [46070.203298] Start test: t_frang.test_request_rate_burst.TestFrangRequestRateBurstH2.test_request_rate_on_the_limit Apr 26 04:52:01 192.168.122.209 [46071.437990] [tdb] Start Tempesta DB Apr 26 04:52:01 192.168.122.209 [46071.576822] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:52:02 192.168.122.209 [46072.406210] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46072.406210] Maybe that's fine, but it's worth checking the [46072.406210] config - if there is no relations between the [46072.406210] names, then host name confusion attack is possible. Apr 26 04:52:02 192.168.122.209 [46072.504964] [tempesta fw] Configuration processing is completed. Apr 26 04:52:02 192.168.122.209 [46072.556308] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:52:02 192.168.122.209 [46072.583982] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:52:02 192.168.122.209 [46072.610584] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:52:02 192.168.122.209 [46072.660937] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:52:02 192.168.122.209 [46072.662416] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:52:02 192.168.122.209 [46072.663826] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:52:02 192.168.122.209 [46072.716930] [tempesta fw] Tempesta FW is ready Apr 26 04:52:07 192.168.122.209 [46077.971750] [tdb] Close table 'client0.tdb' Apr 26 04:52:07 192.168.122.209 [46078.163330] [tdb] Close table 'sessions0.tdb' Apr 26 04:52:08 192.168.122.209 [46078.397237] [tdb] Close table 'filter0.tdb' Apr 26 04:52:08 192.168.122.209 [46078.397660] [tempesta fw] modules are stopped Apr 26 04:52:08 192.168.122.209 [46078.600781] [tempesta fw] exiting... Apr 26 04:52:08 192.168.122.209 [46078.749348] [tdb] Shutdown Tempesta DB Apr 26 04:52:08 192.168.122.209 [46078.971106] End test: t_frang.test_request_rate_burst.TestFrangRequestRateBurstH2.test_request_rate_on_the_limit Apr 26 04:52:08 192.168.122.209 [46078.996103] Start test: t_frang.test_request_rate_burst.TestFrangRequestRateBurstH2.test_request_rate_reached Apr 26 04:52:09 192.168.122.209 [46080.123817] [tdb] Start Tempesta DB Apr 26 04:52:09 192.168.122.209 [46080.264053] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:52:10 192.168.122.209 [46080.982324] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46080.982324] Maybe that's fine, but it's worth checking the [46080.982324] config - if there is no relations between the [46080.982324] names, then host name confusion attack is possible. Apr 26 04:52:10 192.168.122.209 [46081.085085] [tempesta fw] Configuration processing is completed. Apr 26 04:52:10 192.168.122.209 [46081.154047] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:52:10 192.168.122.209 [46081.184186] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:52:10 192.168.122.209 [46081.213301] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:52:10 192.168.122.209 [46081.265039] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:52:10 192.168.122.209 [46081.266475] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:52:10 192.168.122.209 [46081.267955] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:52:10 192.168.122.209 [46081.317045] [tempesta fw] Tempesta FW is ready Apr 26 04:52:15 192.168.122.209 [46085.913733] [tempesta fw] Warning: frang: request rate exceeded for 127.0.0.2: 6 (lim=5) Apr 26 04:52:15 192.168.122.209 [46085.914503] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:52:16 192.168.122.209 [46086.545163] [tdb] Close table 'client0.tdb' Apr 26 04:52:16 192.168.122.209 [46086.735873] [tdb] Close table 'sessions0.tdb' Apr 26 04:52:16 192.168.122.209 [46086.978130] [tdb] Close table 'filter0.tdb' Apr 26 04:52:16 192.168.122.209 [46086.978848] [tempesta fw] modules are stopped Apr 26 04:52:16 192.168.122.209 [46087.181200] [tempesta fw] exiting... Apr 26 04:52:16 192.168.122.209 [46087.341207] [tdb] Shutdown Tempesta DB Apr 26 04:52:17 192.168.122.209 [46087.570542] End test: t_frang.test_request_rate_burst.TestFrangRequestRateBurstH2.test_request_rate_reached Apr 26 04:52:17 192.168.122.209 [46087.589258] Start test: t_frang.test_request_rate_burst.TestFrangRequestRateBurstH2.test_request_rate_without_reaching_the_limit Apr 26 04:52:18 192.168.122.209 [46088.794483] [tdb] Start Tempesta DB Apr 26 04:52:18 192.168.122.209 [46088.938900] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:52:19 192.168.122.209 [46089.734452] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46089.734452] Maybe that's fine, but it's worth checking the [46089.734452] config - if there is no relations between the [46089.734452] names, then host name confusion attack is possible. Apr 26 04:52:19 192.168.122.209 [46089.845156] [tempesta fw] Configuration processing is completed. Apr 26 04:52:19 192.168.122.209 [46089.898571] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:52:19 192.168.122.209 [46089.929540] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:52:19 192.168.122.209 [46089.960701] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:52:19 192.168.122.209 [46090.009208] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:52:19 192.168.122.209 [46090.010546] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:52:19 192.168.122.209 [46090.011854] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:52:19 192.168.122.209 [46090.053149] [tempesta fw] Tempesta FW is ready Apr 26 04:52:24 192.168.122.209 [46095.298711] [tdb] Close table 'client0.tdb' Apr 26 04:52:25 192.168.122.209 [46095.502701] [tdb] Close table 'sessions0.tdb' Apr 26 04:52:25 192.168.122.209 [46095.721674] [tdb] Close table 'filter0.tdb' Apr 26 04:52:25 192.168.122.209 [46095.722115] [tempesta fw] modules are stopped Apr 26 04:52:25 192.168.122.209 [46095.930916] [tempesta fw] exiting... Apr 26 04:52:25 192.168.122.209 [46096.083822] [tdb] Shutdown Tempesta DB Apr 26 04:52:25 192.168.122.209 [46096.302441] End test: t_frang.test_request_rate_burst.TestFrangRequestRateBurstH2.test_request_rate_without_reaching_the_limit Apr 26 04:52:25 192.168.122.209 [46096.316137] Start test: t_frang.test_request_rate_burst.TestFrangRequestRateBurstHttp.test_request_burst_on_the_limit Apr 26 04:52:27 192.168.122.209 [46097.559897] [tdb] Start Tempesta DB Apr 26 04:52:27 192.168.122.209 [46097.700247] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:52:28 192.168.122.209 [46098.426572] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46098.426572] Maybe that's fine, but it's worth checking the [46098.426572] config - if there is no relations between the [46098.426572] names, then host name confusion attack is possible. Apr 26 04:52:28 192.168.122.209 [46098.525274] [tempesta fw] Configuration processing is completed. Apr 26 04:52:28 192.168.122.209 [46098.582198] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:52:28 192.168.122.209 [46098.612698] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:52:28 192.168.122.209 [46098.640238] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:52:28 192.168.122.209 [46098.705275] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:52:28 192.168.122.209 [46098.707021] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:52:28 192.168.122.209 [46098.708681] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:52:28 192.168.122.209 [46098.745246] [tempesta fw] Tempesta FW is ready Apr 26 04:52:33 192.168.122.209 [46104.004635] [tdb] Close table 'client0.tdb' Apr 26 04:52:33 192.168.122.209 [46104.217448] [tdb] Close table 'sessions0.tdb' Apr 26 04:52:34 192.168.122.209 [46104.461766] [tdb] Close table 'filter0.tdb' Apr 26 04:52:34 192.168.122.209 [46104.462195] [tempesta fw] modules are stopped Apr 26 04:52:34 192.168.122.209 [46104.661275] [tempesta fw] exiting... Apr 26 04:52:34 192.168.122.209 [46104.784916] [tdb] Shutdown Tempesta DB Apr 26 04:52:34 192.168.122.209 [46105.004169] End test: t_frang.test_request_rate_burst.TestFrangRequestRateBurstHttp.test_request_burst_on_the_limit Apr 26 04:52:34 192.168.122.209 [46105.013781] Start test: t_frang.test_request_rate_burst.TestFrangRequestRateBurstHttp.test_request_burst_reached Apr 26 04:52:35 192.168.122.209 [46106.305738] [tdb] Start Tempesta DB Apr 26 04:52:36 192.168.122.209 [46106.450828] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:52:36 192.168.122.209 [46107.242655] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46107.242655] Maybe that's fine, but it's worth checking the [46107.242655] config - if there is no relations between the [46107.242655] names, then host name confusion attack is possible. Apr 26 04:52:36 192.168.122.209 [46107.341421] [tempesta fw] Configuration processing is completed. Apr 26 04:52:37 192.168.122.209 [46107.396868] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:52:37 192.168.122.209 [46107.425262] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:52:37 192.168.122.209 [46107.453081] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:52:37 192.168.122.209 [46107.505388] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:52:37 192.168.122.209 [46107.507064] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:52:37 192.168.122.209 [46107.508699] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:52:37 192.168.122.209 [46107.553336] [tempesta fw] Tempesta FW is ready Apr 26 04:52:41 192.168.122.209 [46112.207920] [tempesta fw] Warning: frang: requests burst exceeded for 127.0.0.2: 6 (lim=5) Apr 26 04:52:41 192.168.122.209 [46112.208725] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:52:42 192.168.122.209 [46112.783048] [tdb] Close table 'client0.tdb' Apr 26 04:52:42 192.168.122.209 [46112.984453] [tdb] Close table 'sessions0.tdb' Apr 26 04:52:42 192.168.122.209 [46113.233360] [tdb] Close table 'filter0.tdb' Apr 26 04:52:42 192.168.122.209 [46113.233798] [tempesta fw] modules are stopped Apr 26 04:52:43 192.168.122.209 [46113.429452] [tempesta fw] exiting... Apr 26 04:52:43 192.168.122.209 [46113.575354] [tdb] Shutdown Tempesta DB Apr 26 04:52:43 192.168.122.209 [46113.792684] End test: t_frang.test_request_rate_burst.TestFrangRequestRateBurstHttp.test_request_burst_reached Apr 26 04:52:43 192.168.122.209 [46113.804302] Start test: t_frang.test_request_rate_burst.TestFrangRequestRateBurstHttp.test_request_burst_without_reaching_the_limit Apr 26 04:52:44 192.168.122.209 [46114.958530] [tdb] Start Tempesta DB Apr 26 04:52:44 192.168.122.209 [46115.091391] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:52:45 192.168.122.209 [46115.898942] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46115.898942] Maybe that's fine, but it's worth checking the [46115.898942] config - if there is no relations between the [46115.898942] names, then host name confusion attack is possible. Apr 26 04:52:45 192.168.122.209 [46116.005553] [tempesta fw] Configuration processing is completed. Apr 26 04:52:45 192.168.122.209 [46116.056952] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:52:45 192.168.122.209 [46116.087662] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:52:45 192.168.122.209 [46116.115113] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:52:45 192.168.122.209 [46116.165511] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:52:45 192.168.122.209 [46116.167238] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:52:45 192.168.122.209 [46116.168883] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:52:45 192.168.122.209 [46116.205374] [tempesta fw] Tempesta FW is ready Apr 26 04:52:51 192.168.122.209 [46121.414300] [tdb] Close table 'client0.tdb' Apr 26 04:52:51 192.168.122.209 [46121.607513] [tdb] Close table 'sessions0.tdb' Apr 26 04:52:51 192.168.122.209 [46121.848852] [tdb] Close table 'filter0.tdb' Apr 26 04:52:51 192.168.122.209 [46121.849278] [tempesta fw] modules are stopped Apr 26 04:52:51 192.168.122.209 [46122.045088] [tempesta fw] exiting... Apr 26 04:52:51 192.168.122.209 [46122.164329] [tdb] Shutdown Tempesta DB Apr 26 04:52:51 192.168.122.209 [46122.365224] End test: t_frang.test_request_rate_burst.TestFrangRequestRateBurstHttp.test_request_burst_without_reaching_the_limit Apr 26 04:52:51 192.168.122.209 [46122.382111] Start test: t_frang.test_request_rate_burst.TestFrangRequestRateBurstHttp.test_request_rate_on_the_limit Apr 26 04:52:53 192.168.122.209 [46123.565062] [tdb] Start Tempesta DB Apr 26 04:52:53 192.168.122.209 [46123.699395] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:52:54 192.168.122.209 [46124.442816] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46124.442816] Maybe that's fine, but it's worth checking the [46124.442816] config - if there is no relations between the [46124.442816] names, then host name confusion attack is possible. Apr 26 04:52:54 192.168.122.209 [46124.557629] [tempesta fw] Configuration processing is completed. Apr 26 04:52:54 192.168.122.209 [46124.604884] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:52:54 192.168.122.209 [46124.633220] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:52:54 192.168.122.209 [46124.660113] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:52:54 192.168.122.209 [46124.709605] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:52:54 192.168.122.209 [46124.711154] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:52:54 192.168.122.209 [46124.712876] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:52:54 192.168.122.209 [46124.749556] [tempesta fw] Tempesta FW is ready Apr 26 04:52:59 192.168.122.209 [46129.946809] [tdb] Close table 'client0.tdb' Apr 26 04:52:59 192.168.122.209 [46130.139189] [tdb] Close table 'sessions0.tdb' Apr 26 04:52:59 192.168.122.209 [46130.365449] [tdb] Close table 'filter0.tdb' Apr 26 04:52:59 192.168.122.209 [46130.366256] [tempesta fw] modules are stopped Apr 26 04:53:00 192.168.122.209 [46130.543630] [tempesta fw] exiting... Apr 26 04:53:00 192.168.122.209 [46130.684288] [tdb] Shutdown Tempesta DB Apr 26 04:53:00 192.168.122.209 [46130.872750] End test: t_frang.test_request_rate_burst.TestFrangRequestRateBurstHttp.test_request_rate_on_the_limit Apr 26 04:53:00 192.168.122.209 [46130.889033] Start test: t_frang.test_request_rate_burst.TestFrangRequestRateBurstHttp.test_request_rate_reached Apr 26 04:53:01 192.168.122.209 [46132.078493] [tdb] Start Tempesta DB Apr 26 04:53:01 192.168.122.209 [46132.211734] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:53:02 192.168.122.209 [46132.962994] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46132.962994] Maybe that's fine, but it's worth checking the [46132.962994] config - if there is no relations between the [46132.962994] names, then host name confusion attack is possible. Apr 26 04:53:02 192.168.122.209 [46133.089773] [tempesta fw] Configuration processing is completed. Apr 26 04:53:02 192.168.122.209 [46133.140521] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:53:02 192.168.122.209 [46133.170423] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:53:02 192.168.122.209 [46133.197056] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:53:02 192.168.122.209 [46133.249669] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:53:02 192.168.122.209 [46133.251325] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:53:02 192.168.122.209 [46133.252989] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:53:02 192.168.122.209 [46133.293661] [tempesta fw] Tempesta FW is ready Apr 26 04:53:07 192.168.122.209 [46137.952300] [tempesta fw] Warning: frang: request rate exceeded for 127.0.0.2: 6 (lim=5) Apr 26 04:53:07 192.168.122.209 [46137.954576] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:53:08 192.168.122.209 [46138.470454] [tdb] Close table 'client0.tdb' Apr 26 04:53:08 192.168.122.209 [46138.685256] [tdb] Close table 'sessions0.tdb' Apr 26 04:53:08 192.168.122.209 [46138.915702] [tdb] Close table 'filter0.tdb' Apr 26 04:53:08 192.168.122.209 [46138.916141] [tempesta fw] modules are stopped Apr 26 04:53:08 192.168.122.209 [46139.137156] [tempesta fw] exiting... Apr 26 04:53:08 192.168.122.209 [46139.271454] [tdb] Shutdown Tempesta DB Apr 26 04:53:09 192.168.122.209 [46139.440361] End test: t_frang.test_request_rate_burst.TestFrangRequestRateBurstHttp.test_request_rate_reached Apr 26 04:53:09 192.168.122.209 [46139.452448] Start test: t_frang.test_request_rate_burst.TestFrangRequestRateBurstHttp.test_request_rate_without_reaching_the_limit Apr 26 04:53:10 192.168.122.209 [46140.506976] [tdb] Start Tempesta DB Apr 26 04:53:10 192.168.122.209 [46140.643751] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:53:10 192.168.122.209 [46141.319058] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46141.319058] Maybe that's fine, but it's worth checking the [46141.319058] config - if there is no relations between the [46141.319058] names, then host name confusion attack is possible. Apr 26 04:53:11 192.168.122.209 [46141.421852] [tempesta fw] Configuration processing is completed. Apr 26 04:53:11 192.168.122.209 [46141.474641] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:53:11 192.168.122.209 [46141.503886] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:53:11 192.168.122.209 [46141.531246] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:53:11 192.168.122.209 [46141.585823] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:53:11 192.168.122.209 [46141.587393] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 04:53:11 192.168.122.209 [46141.589038] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:53:11 192.168.122.209 [46141.633772] [tempesta fw] Tempesta FW is ready Apr 26 04:53:16 192.168.122.209 [46146.884140] [tdb] Close table 'client0.tdb' Apr 26 04:53:16 192.168.122.209 [46147.072679] [tdb] Close table 'sessions0.tdb' Apr 26 04:53:16 192.168.122.209 [46147.313908] [tdb] Close table 'filter0.tdb' Apr 26 04:53:16 192.168.122.209 [46147.314347] [tempesta fw] modules are stopped Apr 26 04:53:17 192.168.122.209 [46147.518407] [tempesta fw] exiting... Apr 26 04:53:17 192.168.122.209 [46147.643804] [tdb] Shutdown Tempesta DB Apr 26 04:53:17 192.168.122.209 [46147.814124] End test: t_frang.test_request_rate_burst.TestFrangRequestRateBurstHttp.test_request_rate_without_reaching_the_limit Apr 26 04:53:17 192.168.122.209 [46147.825325] Start test: t_frang.test_request_rate_burst.TestFrangRequestRateH2.test_two_clients_one_ip Apr 26 04:53:18 192.168.122.209 [46148.886903] [tdb] Start Tempesta DB Apr 26 04:53:18 192.168.122.209 [46149.024857] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:53:19 192.168.122.209 [46149.628320] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46149.628320] Maybe that's fine, but it's worth checking the [46149.628320] config - if there is no relations between the [46149.628320] names, then host name confusion attack is possible. Apr 26 04:53:19 192.168.122.209 [46149.713984] [tempesta fw] Configuration processing is completed. Apr 26 04:53:19 192.168.122.209 [46149.766542] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:53:20 192.168.122.209 [46150.467687] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:53:20 192.168.122.209 [46150.514715] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:53:20 192.168.122.209 [46150.561109] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:53:20 192.168.122.209 [46150.613934] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:53:20 192.168.122.209 [46150.615554] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:53:20 192.168.122.209 [46150.653892] [tempesta fw] Tempesta FW is ready Apr 26 04:53:24 192.168.122.209 [46155.207539] [tempesta fw] Warning: frang: request rate exceeded for 127.0.0.2: 5 (lim=4) Apr 26 04:53:24 192.168.122.209 [46155.209110] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:53:24 192.168.122.209 [46155.210328] [tempesta fw] Warning: block client: 127.0.0.2 Apr 26 04:53:31 192.168.122.209 [46161.459846] [tdb] Close table 'client0.tdb' Apr 26 04:53:31 192.168.122.209 [46161.661319] [tdb] Close table 'sessions0.tdb' Apr 26 04:53:34 192.168.122.209 [46164.801827] [tdb] Close table 'cache0.tdb' Apr 26 04:53:34 192.168.122.209 [46165.070646] [tdb] Close table 'filter0.tdb' Apr 26 04:53:34 192.168.122.209 [46165.071088] [tempesta fw] modules are stopped Apr 26 04:53:34 192.168.122.209 [46165.265728] [tempesta fw] exiting... Apr 26 04:53:34 192.168.122.209 [46165.385518] [tdb] Shutdown Tempesta DB Apr 26 04:53:35 192.168.122.209 [46165.656078] End test: t_frang.test_request_rate_burst.TestFrangRequestRateH2.test_two_clients_one_ip Apr 26 04:53:35 192.168.122.209 [46165.663724] Start test: t_frang.test_request_rate_burst.TestFrangRequestRateH2.test_two_clients_two_ip Apr 26 04:53:36 192.168.122.209 [46166.846695] [tdb] Start Tempesta DB Apr 26 04:53:36 192.168.122.209 [46166.992620] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:53:38 192.168.122.209 [46168.515419] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46168.515419] Maybe that's fine, but it's worth checking the [46168.515419] config - if there is no relations between the [46168.515419] names, then host name confusion attack is possible. Apr 26 04:53:38 192.168.122.209 [46168.590196] [tempesta fw] Configuration processing is completed. Apr 26 04:53:38 192.168.122.209 [46168.638423] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:53:38 192.168.122.209 [46169.052251] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:53:38 192.168.122.209 [46169.077880] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:53:38 192.168.122.209 [46169.107166] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:53:38 192.168.122.209 [46169.186309] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:53:38 192.168.122.209 [46169.188028] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:53:38 192.168.122.209 [46169.226155] [tempesta fw] Tempesta FW is ready Apr 26 04:53:43 192.168.122.209 [46173.921296] [tempesta fw] Warning: frang: request rate exceeded for 192.168.123.2: 5 (lim=4) Apr 26 04:53:43 192.168.122.209 [46173.922520] [tempesta fw] Warning: parsed request has been filtered out: 192.168.123.2 Apr 26 04:53:43 192.168.122.209 [46173.923609] [tempesta fw] Warning: block client: 192.168.123.2 Apr 26 04:53:49 192.168.122.209 [46180.048486] [tdb] Close table 'client0.tdb' Apr 26 04:53:49 192.168.122.209 [46180.265205] [tdb] Close table 'sessions0.tdb' Apr 26 04:53:53 192.168.122.209 [46183.400730] [tdb] Close table 'cache0.tdb' Apr 26 04:53:53 192.168.122.209 [46183.651089] [tdb] Close table 'filter0.tdb' Apr 26 04:53:53 192.168.122.209 [46183.651527] [tempesta fw] modules are stopped Apr 26 04:53:53 192.168.122.209 [46183.852634] [tempesta fw] exiting... Apr 26 04:53:53 192.168.122.209 [46183.982435] [tdb] Shutdown Tempesta DB Apr 26 04:53:53 192.168.122.209 [46184.220182] End test: t_frang.test_request_rate_burst.TestFrangRequestRateH2.test_two_clients_two_ip Apr 26 04:53:53 192.168.122.209 [46184.233491] Start test: t_frang.test_request_rate_burst.TestFrangRequestRateHttp.test_two_clients_one_ip Apr 26 04:53:55 192.168.122.209 [46185.399253] [tdb] Start Tempesta DB Apr 26 04:53:55 192.168.122.209 [46185.537134] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:53:56 192.168.122.209 [46187.019685] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46187.019685] Maybe that's fine, but it's worth checking the [46187.019685] config - if there is no relations between the [46187.019685] names, then host name confusion attack is possible. Apr 26 04:53:56 192.168.122.209 [46187.082483] [tempesta fw] Configuration processing is completed. Apr 26 04:53:56 192.168.122.209 [46187.133917] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:53:57 192.168.122.209 [46187.546254] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:53:57 192.168.122.209 [46187.573129] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:53:57 192.168.122.209 [46187.599678] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:53:57 192.168.122.209 [46187.662416] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:53:57 192.168.122.209 [46187.664187] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:53:57 192.168.122.209 [46187.702374] [tempesta fw] Tempesta FW is ready Apr 26 04:54:01 192.168.122.209 [46192.353140] [tempesta fw] Warning: frang: request rate exceeded for 127.0.0.2: 5 (lim=4) Apr 26 04:54:01 192.168.122.209 [46192.353901] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 04:54:01 192.168.122.209 [46192.354603] [tempesta fw] Warning: block client: 127.0.0.2 Apr 26 04:54:08 192.168.122.209 [46198.493627] [tdb] Close table 'client0.tdb' Apr 26 04:54:08 192.168.122.209 [46198.684889] [tdb] Close table 'sessions0.tdb' Apr 26 04:54:11 192.168.122.209 [46201.812933] [tdb] Close table 'cache0.tdb' Apr 26 04:54:11 192.168.122.209 [46202.052217] [tdb] Close table 'filter0.tdb' Apr 26 04:54:11 192.168.122.209 [46202.052654] [tempesta fw] modules are stopped Apr 26 04:54:11 192.168.122.209 [46202.250228] [tempesta fw] exiting... Apr 26 04:54:11 192.168.122.209 [46202.373605] [tdb] Shutdown Tempesta DB Apr 26 04:54:12 192.168.122.209 [46202.575597] End test: t_frang.test_request_rate_burst.TestFrangRequestRateHttp.test_two_clients_one_ip Apr 26 04:54:12 192.168.122.209 [46202.584228] Start test: t_frang.test_request_rate_burst.TestFrangRequestRateHttp.test_two_clients_two_ip Apr 26 04:54:13 192.168.122.209 [46203.820502] [tdb] Start Tempesta DB Apr 26 04:54:13 192.168.122.209 [46203.944409] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:54:15 192.168.122.209 [46205.451794] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46205.451794] Maybe that's fine, but it's worth checking the [46205.451794] config - if there is no relations between the [46205.451794] names, then host name confusion attack is possible. Apr 26 04:54:15 192.168.122.209 [46205.526678] [tempesta fw] Configuration processing is completed. Apr 26 04:54:15 192.168.122.209 [46205.577738] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:54:15 192.168.122.209 [46205.988256] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:54:15 192.168.122.209 [46206.014045] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:54:15 192.168.122.209 [46206.039816] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:54:15 192.168.122.209 [46206.078639] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:54:15 192.168.122.209 [46206.080371] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:54:15 192.168.122.209 [46206.118611] [tempesta fw] Tempesta FW is ready Apr 26 04:54:20 192.168.122.209 [46210.767468] [tempesta fw] Warning: frang: request rate exceeded for 192.168.123.2: 5 (lim=4) Apr 26 04:54:20 192.168.122.209 [46210.769799] [tempesta fw] Warning: parsed request has been filtered out: 192.168.123.2 Apr 26 04:54:20 192.168.122.209 [46210.771771] [tempesta fw] Warning: block client: 192.168.123.2 Apr 26 04:54:26 192.168.122.209 [46216.899127] [tdb] Close table 'client0.tdb' Apr 26 04:54:26 192.168.122.209 [46217.090026] [tdb] Close table 'sessions0.tdb' Apr 26 04:54:29 192.168.122.209 [46220.186548] [tdb] Close table 'cache0.tdb' Apr 26 04:54:30 192.168.122.209 [46220.403882] [tdb] Close table 'filter0.tdb' Apr 26 04:54:30 192.168.122.209 [46220.404310] [tempesta fw] modules are stopped Apr 26 04:54:30 192.168.122.209 [46220.639921] [tempesta fw] exiting... Apr 26 04:54:30 192.168.122.209 [46220.765739] [tdb] Shutdown Tempesta DB Apr 26 04:54:30 192.168.122.209 [46220.972762] End test: t_frang.test_request_rate_burst.TestFrangRequestRateHttp.test_two_clients_two_ip Apr 26 04:54:30 192.168.122.209 [46220.984590] Start test: t_frang.test_tls_incomplete.FrangTlsIncompleteTestCase.test_tls_incomplete_connection_rate Apr 26 04:54:31 192.168.122.209 [46222.222232] [tdb] Start Tempesta DB Apr 26 04:54:31 192.168.122.209 [46222.358363] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:54:33 192.168.122.209 [46223.852077] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46223.852077] Maybe that's fine, but it's worth checking the [46223.852077] config - if there is no relations between the [46223.852077] names, then host name confusion attack is possible. Apr 26 04:54:33 192.168.122.209 [46223.954875] [tempesta fw] Configuration processing is completed. Apr 26 04:54:33 192.168.122.209 [46224.005759] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:54:33 192.168.122.209 [46224.033186] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:54:33 192.168.122.209 [46224.060018] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:54:33 192.168.122.209 [46224.102851] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:54:33 192.168.122.209 [46224.146813] [tempesta fw] Tempesta FW is ready Apr 26 04:54:34 192.168.122.209 [46224.480705] [tempesta fw] Warning: frang: incomplete TLS connections rate exceeded for 127.0.0.2: 5 (lim=4) Apr 26 04:54:35 192.168.122.209 [46225.495974] [tdb] Close table 'client0.tdb' Apr 26 04:54:35 192.168.122.209 [46225.686478] [tdb] Close table 'sessions0.tdb' Apr 26 04:54:35 192.168.122.209 [46225.918630] [tdb] Close table 'filter0.tdb' Apr 26 04:54:35 192.168.122.209 [46225.919083] [tempesta fw] modules are stopped Apr 26 04:54:35 192.168.122.209 [46226.132254] [tempesta fw] exiting... Apr 26 04:54:35 192.168.122.209 [46226.264790] [tdb] Shutdown Tempesta DB Apr 26 04:54:36 192.168.122.209 [46226.474638] End test: t_frang.test_tls_incomplete.FrangTlsIncompleteTestCase.test_tls_incomplete_connection_rate Apr 26 04:54:36 192.168.122.209 [46226.491069] Start test: t_frang.test_tls_incomplete.FrangTlsIncompleteTestCase.test_tls_incomplete_connection_rate_on_the_limit Apr 26 04:54:37 192.168.122.209 [46227.662071] [tdb] Start Tempesta DB Apr 26 04:54:37 192.168.122.209 [46227.810203] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:54:38 192.168.122.209 [46228.568132] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46228.568132] Maybe that's fine, but it's worth checking the [46228.568132] config - if there is no relations between the [46228.568132] names, then host name confusion attack is possible. Apr 26 04:54:38 192.168.122.209 [46228.674939] [tempesta fw] Configuration processing is completed. Apr 26 04:54:38 192.168.122.209 [46228.729984] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:54:38 192.168.122.209 [46228.757812] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:54:38 192.168.122.209 [46228.784478] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:54:38 192.168.122.209 [46228.831229] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:54:38 192.168.122.209 [46228.870884] [tempesta fw] Tempesta FW is ready Apr 26 04:54:39 192.168.122.209 [46230.188492] [tdb] Close table 'client0.tdb' Apr 26 04:54:40 192.168.122.209 [46230.402310] [tdb] Close table 'sessions0.tdb' Apr 26 04:54:40 192.168.122.209 [46230.616899] [tdb] Close table 'filter0.tdb' Apr 26 04:54:40 192.168.122.209 [46230.617328] [tempesta fw] modules are stopped Apr 26 04:54:40 192.168.122.209 [46230.836253] [tempesta fw] exiting... Apr 26 04:54:40 192.168.122.209 [46230.999099] [tdb] Shutdown Tempesta DB Apr 26 04:54:40 192.168.122.209 [46231.224758] End test: t_frang.test_tls_incomplete.FrangTlsIncompleteTestCase.test_tls_incomplete_connection_rate_on_the_limit Apr 26 04:54:40 192.168.122.209 [46231.237099] Start test: t_frang.test_tls_incomplete.FrangTlsIncompleteTestCase.test_tls_incomplete_connection_without_reaching_the_limit Apr 26 04:54:42 192.168.122.209 [46232.433167] [tdb] Start Tempesta DB Apr 26 04:54:42 192.168.122.209 [46232.581561] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:54:42 192.168.122.209 [46233.308249] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46233.308249] Maybe that's fine, but it's worth checking the [46233.308249] config - if there is no relations between the [46233.308249] names, then host name confusion attack is possible. Apr 26 04:54:43 192.168.122.209 [46233.415031] [tempesta fw] Configuration processing is completed. Apr 26 04:54:43 192.168.122.209 [46233.465062] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:54:43 192.168.122.209 [46233.496788] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:54:43 192.168.122.209 [46233.525364] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:54:43 192.168.122.209 [46233.590969] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:54:43 192.168.122.209 [46233.626934] [tempesta fw] Tempesta FW is ready Apr 26 04:54:44 192.168.122.209 [46234.963819] [tdb] Close table 'client0.tdb' Apr 26 04:54:44 192.168.122.209 [46235.167838] [tdb] Close table 'sessions0.tdb' Apr 26 04:54:45 192.168.122.209 [46235.425433] [tdb] Close table 'filter0.tdb' Apr 26 04:54:45 192.168.122.209 [46235.426031] [tempesta fw] modules are stopped Apr 26 04:54:45 192.168.122.209 [46235.672725] [tempesta fw] exiting... Apr 26 04:54:45 192.168.122.209 [46235.812428] [tdb] Shutdown Tempesta DB Apr 26 04:54:45 192.168.122.209 [46236.000674] End test: t_frang.test_tls_incomplete.FrangTlsIncompleteTestCase.test_tls_incomplete_connection_without_reaching_the_limit Apr 26 04:54:45 192.168.122.209 [46236.022414] Start test: t_frang.test_whitelist_mark.FrangWhitelistMarkTestCase.test_non_whitelisted_request_are_js_challenged Apr 26 04:54:46 192.168.122.209 [46237.220334] [tdb] Start Tempesta DB Apr 26 04:54:46 192.168.122.209 [46237.350664] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:54:48 192.168.122.209 [46238.721787] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:54:48 192.168.122.209 [46238.795137] [tempesta fw] Configuration processing is completed. Apr 26 04:54:48 192.168.122.209 [46238.846034] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:54:48 192.168.122.209 [46239.348030] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:54:48 192.168.122.209 [46239.380316] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:54:49 192.168.122.209 [46239.415205] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:54:49 192.168.122.209 [46239.459003] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:54:49 192.168.122.209 [46239.499022] [tempesta fw] Tempesta FW is ready Apr 26 04:54:49 192.168.122.209 [46240.045880] [tdb] Close table 'client0.tdb' Apr 26 04:54:49 192.168.122.209 [46240.237397] [tdb] Close table 'sessions0.tdb' Apr 26 04:54:53 192.168.122.209 [46243.400922] [tdb] Close table 'cache0.tdb' Apr 26 04:54:53 192.168.122.209 [46243.632239] [tdb] Close table 'filter0.tdb' Apr 26 04:54:53 192.168.122.209 [46243.632677] [tempesta fw] modules are stopped Apr 26 04:54:53 192.168.122.209 [46243.867673] [tempesta fw] exiting... Apr 26 04:54:53 192.168.122.209 [46243.992559] [tdb] Shutdown Tempesta DB Apr 26 04:54:53 192.168.122.209 [46244.225491] End test: t_frang.test_whitelist_mark.FrangWhitelistMarkTestCase.test_non_whitelisted_request_are_js_challenged Apr 26 04:54:53 192.168.122.209 [46244.235596] Start test: t_frang.test_whitelist_mark.FrangWhitelistMarkTestCase.test_whitelisted_basic_request Apr 26 04:54:55 192.168.122.209 [46245.434376] [tdb] Start Tempesta DB Apr 26 04:54:55 192.168.122.209 [46245.579688] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:54:57 192.168.122.209 [46247.769824] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:54:57 192.168.122.209 [46247.831312] [tempesta fw] Configuration processing is completed. Apr 26 04:54:57 192.168.122.209 [46247.888624] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:54:57 192.168.122.209 [46248.373774] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:54:58 192.168.122.209 [46248.404137] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:54:58 192.168.122.209 [46248.431185] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:54:58 192.168.122.209 [46248.475137] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:54:58 192.168.122.209 [46248.515154] [tempesta fw] Tempesta FW is ready Apr 26 04:54:58 192.168.122.209 [46249.100920] [tdb] Close table 'client0.tdb' Apr 26 04:54:58 192.168.122.209 [46249.290260] [tdb] Close table 'sessions0.tdb' Apr 26 04:55:02 192.168.122.209 [46252.501795] [tdb] Close table 'cache0.tdb' Apr 26 04:55:02 192.168.122.209 [46252.737856] [tdb] Close table 'filter0.tdb' Apr 26 04:55:02 192.168.122.209 [46252.738300] [tempesta fw] modules are stopped Apr 26 04:55:02 192.168.122.209 [46252.946283] [tempesta fw] exiting... Apr 26 04:55:02 192.168.122.209 [46253.068999] [tdb] Shutdown Tempesta DB Apr 26 04:55:02 192.168.122.209 [46253.262312] End test: t_frang.test_whitelist_mark.FrangWhitelistMarkTestCase.test_whitelisted_basic_request Apr 26 04:55:02 192.168.122.209 [46253.273286] Start test: t_frang.test_whitelist_mark.FrangWhitelistMarkTestCase.test_whitelisted_basic_request_xforwarded_for Apr 26 04:55:04 192.168.122.209 [46254.395998] [tdb] Start Tempesta DB Apr 26 04:55:04 192.168.122.209 [46254.531507] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:55:06 192.168.122.209 [46256.650074] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:55:06 192.168.122.209 [46256.715371] [tempesta fw] Configuration processing is completed. Apr 26 04:55:06 192.168.122.209 [46256.768918] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:55:06 192.168.122.209 [46257.286811] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:55:06 192.168.122.209 [46257.350405] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:55:06 192.168.122.209 [46257.382837] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:55:07 192.168.122.209 [46257.431289] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:55:07 192.168.122.209 [46257.475234] [tempesta fw] Tempesta FW is ready Apr 26 04:55:07 192.168.122.209 [46258.062970] [tdb] Close table 'client0.tdb' Apr 26 04:55:07 192.168.122.209 [46258.259856] [tdb] Close table 'sessions0.tdb' Apr 26 04:55:11 192.168.122.209 [46261.474978] [tdb] Close table 'cache0.tdb' Apr 26 04:55:11 192.168.122.209 [46261.723013] [tdb] Close table 'filter0.tdb' Apr 26 04:55:11 192.168.122.209 [46261.723877] [tempesta fw] modules are stopped Apr 26 04:55:11 192.168.122.209 [46261.926240] [tempesta fw] exiting... Apr 26 04:55:11 192.168.122.209 [46262.071663] [tdb] Shutdown Tempesta DB Apr 26 04:55:11 192.168.122.209 [46262.269698] End test: t_frang.test_whitelist_mark.FrangWhitelistMarkTestCase.test_whitelisted_basic_request_xforwarded_for Apr 26 04:55:11 192.168.122.209 [46262.292765] Start test: t_frang.test_whitelist_mark.FrangWhitelistMarkTestCase.test_whitelisted_frang_connection_rate Apr 26 04:55:13 192.168.122.209 [46263.483083] [tdb] Start Tempesta DB Apr 26 04:55:13 192.168.122.209 [46263.631890] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:55:15 192.168.122.209 [46265.834195] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:55:15 192.168.122.209 [46265.907491] [tempesta fw] Configuration processing is completed. Apr 26 04:55:15 192.168.122.209 [46265.957755] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:55:15 192.168.122.209 [46266.372294] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:55:16 192.168.122.209 [46266.430111] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:55:16 192.168.122.209 [46266.456756] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:55:16 192.168.122.209 [46266.499341] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:55:16 192.168.122.209 [46266.539348] [tempesta fw] Tempesta FW is ready Apr 26 04:55:16 192.168.122.209 [46267.156176] [tdb] Close table 'client0.tdb' Apr 26 04:55:16 192.168.122.209 [46267.353436] [tdb] Close table 'sessions0.tdb' Apr 26 04:55:20 192.168.122.209 [46270.494727] [tdb] Close table 'cache0.tdb' Apr 26 04:55:20 192.168.122.209 [46270.715914] [tdb] Close table 'filter0.tdb' Apr 26 04:55:20 192.168.122.209 [46270.716349] [tempesta fw] modules are stopped Apr 26 04:55:20 192.168.122.209 [46270.940136] [tempesta fw] exiting... Apr 26 04:55:20 192.168.122.209 [46271.090321] [tdb] Shutdown Tempesta DB Apr 26 04:55:20 192.168.122.209 [46271.316519] End test: t_frang.test_whitelist_mark.FrangWhitelistMarkTestCase.test_whitelisted_frang_connection_rate Apr 26 04:55:20 192.168.122.209 [46271.329681] Start test: t_frang.test_whitelist_mark.FrangWhitelistMarkTestCase.test_whitelisted_frang_http_uri_len Apr 26 04:55:22 192.168.122.209 [46272.490842] [tdb] Start Tempesta DB Apr 26 04:55:22 192.168.122.209 [46272.634682] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:55:24 192.168.122.209 [46274.830276] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:55:24 192.168.122.209 [46274.895566] [tempesta fw] Configuration processing is completed. Apr 26 04:55:24 192.168.122.209 [46274.949185] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:55:24 192.168.122.209 [46275.378132] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:55:25 192.168.122.209 [46275.404422] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:55:25 192.168.122.209 [46275.431206] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:55:25 192.168.122.209 [46275.483561] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:55:25 192.168.122.209 [46275.531487] [tempesta fw] Tempesta FW is ready Apr 26 04:55:25 192.168.122.209 [46276.092817] [tdb] Close table 'client0.tdb' Apr 26 04:55:25 192.168.122.209 [46276.301992] [tdb] Close table 'sessions0.tdb' Apr 26 04:55:29 192.168.122.209 [46279.456477] [tdb] Close table 'cache0.tdb' Apr 26 04:55:29 192.168.122.209 [46279.703744] [tdb] Close table 'filter0.tdb' Apr 26 04:55:29 192.168.122.209 [46279.704168] [tempesta fw] modules are stopped Apr 26 04:55:29 192.168.122.209 [46279.916711] [tempesta fw] exiting... Apr 26 04:55:29 192.168.122.209 [46280.065270] [tdb] Shutdown Tempesta DB Apr 26 04:55:29 192.168.122.209 [46280.252072] End test: t_frang.test_whitelist_mark.FrangWhitelistMarkTestCase.test_whitelisted_frang_http_uri_len Apr 26 04:55:29 192.168.122.209 [46280.263545] Start test: t_frang.test_whitelist_mark.FrangWhitelistMarkTestCase.test_whitelisted_frang_http_uri_len_xforwarded_for Apr 26 04:55:30 192.168.122.209 [46281.388466] [tdb] Start Tempesta DB Apr 26 04:55:31 192.168.122.209 [46281.540158] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:55:33 192.168.122.209 [46283.706287] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 04:55:33 192.168.122.209 [46283.783669] [tempesta fw] Configuration processing is completed. Apr 26 04:55:33 192.168.122.209 [46283.833203] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:55:33 192.168.122.209 [46284.235363] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:55:33 192.168.122.209 [46284.291712] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:55:33 192.168.122.209 [46284.316766] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:55:33 192.168.122.209 [46284.371603] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:55:34 192.168.122.209 [46284.419586] [tempesta fw] Tempesta FW is ready Apr 26 04:55:34 192.168.122.209 [46284.992021] [tdb] Close table 'client0.tdb' Apr 26 04:55:34 192.168.122.209 [46285.185476] [tdb] Close table 'sessions0.tdb' Apr 26 04:55:37 192.168.122.209 [46288.352429] [tdb] Close table 'cache0.tdb' Apr 26 04:55:38 192.168.122.209 [46288.597510] [tdb] Close table 'filter0.tdb' Apr 26 04:55:38 192.168.122.209 [46288.597988] [tempesta fw] modules are stopped Apr 26 04:55:38 192.168.122.209 [46288.807754] [tempesta fw] exiting... Apr 26 04:55:38 192.168.122.209 [46288.935103] [tdb] Shutdown Tempesta DB Apr 26 04:55:38 192.168.122.209 [46289.106394] End test: t_frang.test_whitelist_mark.FrangWhitelistMarkTestCase.test_whitelisted_frang_http_uri_len_xforwarded_for Apr 26 04:55:38 192.168.122.209 [46289.129870] Start test: t_health_monitoring.test_health_monitor.H2HmResponsesPipelined.test_hm_pipelined_1_hm Apr 26 04:55:39 192.168.122.209 [46290.246569] [tdb] Start Tempesta DB Apr 26 04:55:39 192.168.122.209 [46290.378461] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:55:41 192.168.122.209 [46292.341232] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46292.341232] Maybe that's fine, but it's worth checking the [46292.341232] config - if there is no relations between the [46292.341232] names, then host name confusion attack is possible. Apr 26 04:55:42 192.168.122.209 [46292.483775] [tempesta fw] Configuration processing is completed. Apr 26 04:55:42 192.168.122.209 [46292.538843] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:55:42 192.168.122.209 [46292.965503] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:55:42 192.168.122.209 [46292.991784] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:55:42 192.168.122.209 [46293.017504] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:55:42 192.168.122.209 [46293.063758] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:55:42 192.168.122.209 [46293.111704] [tempesta fw] Tempesta FW is ready Apr 26 04:55:44 192.168.122.209 [46295.050017] [tempesta fw] Warning: Response for health monitor 'hm0': crc32 value '0' mismatched (expected value: '838041247') Apr 26 04:55:44 192.168.122.209 [46295.053212] [tempesta fw] Warning: Response for health monitor 'hm0': crc32 value '0' mismatched (expected value: '838041247') Apr 26 04:55:44 192.168.122.209 [46295.056198] [tempesta fw] Warning: Response for health monitor 'hm0': crc32 value '0' mismatched (expected value: '838041247') Apr 26 04:55:44 192.168.122.209 [46295.058846] [tempesta fw] Warning: Response for health monitor 'hm0': crc32 value '0' mismatched (expected value: '838041247') Apr 26 04:55:45 192.168.122.209 [46295.508939] [tdb] Close table 'client0.tdb' Apr 26 04:55:45 192.168.122.209 [46295.694071] [tdb] Close table 'sessions0.tdb' Apr 26 04:55:48 192.168.122.209 [46298.860126] [tdb] Close table 'cache0.tdb' Apr 26 04:55:48 192.168.122.209 [46299.112474] [tdb] Close table 'filter0.tdb' Apr 26 04:55:48 192.168.122.209 [46299.112923] [tempesta fw] modules are stopped Apr 26 04:55:48 192.168.122.209 [46299.351643] [tempesta fw] exiting... Apr 26 04:55:49 192.168.122.209 [46299.504726] [tdb] Shutdown Tempesta DB Apr 26 04:55:49 192.168.122.209 [46299.706084] End test: t_health_monitoring.test_health_monitor.H2HmResponsesPipelined.test_hm_pipelined_1_hm Apr 26 04:55:49 192.168.122.209 [46299.720075] Start test: t_health_monitoring.test_health_monitor.H2HmResponsesPipelined.test_hm_pipelined_2_hm Apr 26 04:55:50 192.168.122.209 [46300.787011] [tdb] Start Tempesta DB Apr 26 04:55:50 192.168.122.209 [46300.927364] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:55:52 192.168.122.209 [46302.765297] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46302.765297] Maybe that's fine, but it's worth checking the [46302.765297] config - if there is no relations between the [46302.765297] names, then host name confusion attack is possible. Apr 26 04:55:52 192.168.122.209 [46302.907923] [tempesta fw] Configuration processing is completed. Apr 26 04:55:52 192.168.122.209 [46302.959060] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:55:52 192.168.122.209 [46303.365594] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:55:53 192.168.122.209 [46303.426929] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:55:53 192.168.122.209 [46303.452467] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:55:53 192.168.122.209 [46303.499857] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:55:53 192.168.122.209 [46303.539825] [tempesta fw] Tempesta FW is ready Apr 26 04:55:57 192.168.122.209 [46307.517926] [tempesta fw] Warning: Response for health monitor 'hm0': crc32 value '0' mismatched (expected value: '838041247') Apr 26 04:55:57 192.168.122.209 [46307.519012] [tempesta fw] Warning: Response for health monitor 'hm0': crc32 value '0' mismatched (expected value: '838041247') Apr 26 04:55:57 192.168.122.209 [46307.520055] [tempesta fw] Warning: Response for health monitor 'hm0': crc32 value '0' mismatched (expected value: '838041247') Apr 26 04:55:57 192.168.122.209 [46307.521061] [tempesta fw] Warning: Response for health monitor 'hm0': crc32 value '0' mismatched (expected value: '838041247') Apr 26 04:55:57 192.168.122.209 [46307.974193] [tdb] Close table 'client0.tdb' Apr 26 04:55:57 192.168.122.209 [46308.169751] [tdb] Close table 'sessions0.tdb' Apr 26 04:56:00 192.168.122.209 [46311.323127] [tdb] Close table 'cache0.tdb' Apr 26 04:56:01 192.168.122.209 [46311.566394] [tdb] Close table 'filter0.tdb' Apr 26 04:56:01 192.168.122.209 [46311.566822] [tempesta fw] modules are stopped Apr 26 04:56:01 192.168.122.209 [46311.814508] [tempesta fw] exiting... Apr 26 04:56:01 192.168.122.209 [46311.962768] [tdb] Shutdown Tempesta DB Apr 26 04:56:01 192.168.122.209 [46312.186324] End test: t_health_monitoring.test_health_monitor.H2HmResponsesPipelined.test_hm_pipelined_2_hm Apr 26 04:56:01 192.168.122.209 [46312.205950] Start test: t_health_monitoring.test_health_monitor.H2HmResponsesPipelined.test_hm_pipelined_3_hm Apr 26 04:56:02 192.168.122.209 [46313.351756] [tdb] Start Tempesta DB Apr 26 04:56:03 192.168.122.209 [46313.492017] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:56:05 192.168.122.209 [46315.549502] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46315.549502] Maybe that's fine, but it's worth checking the [46315.549502] config - if there is no relations between the [46315.549502] names, then host name confusion attack is possible. Apr 26 04:56:05 192.168.122.209 [46315.680077] [tempesta fw] Configuration processing is completed. Apr 26 04:56:05 192.168.122.209 [46315.732052] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:56:05 192.168.122.209 [46316.154766] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:56:05 192.168.122.209 [46316.180450] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:56:05 192.168.122.209 [46316.205765] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:56:05 192.168.122.209 [46316.243963] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:56:05 192.168.122.209 [46316.283988] [tempesta fw] Tempesta FW is ready Apr 26 04:56:09 192.168.122.209 [46320.248551] [tempesta fw] Warning: Response for health monitor 'hm0': crc32 value '0' mismatched (expected value: '838041247') Apr 26 04:56:09 192.168.122.209 [46320.249610] [tempesta fw] Warning: Response for health monitor 'hm0': crc32 value '0' mismatched (expected value: '838041247') Apr 26 04:56:09 192.168.122.209 [46320.250627] [tempesta fw] Warning: Response for health monitor 'hm0': crc32 value '0' mismatched (expected value: '838041247') Apr 26 04:56:09 192.168.122.209 [46320.251634] [tempesta fw] Warning: Response for health monitor 'hm0': crc32 value '0' mismatched (expected value: '838041247') Apr 26 04:56:10 192.168.122.209 [46320.654349] [tdb] Close table 'client0.tdb' Apr 26 04:56:10 192.168.122.209 [46320.857819] [tdb] Close table 'sessions0.tdb' Apr 26 04:56:13 192.168.122.209 [46324.042792] [tdb] Close table 'cache0.tdb' Apr 26 04:56:13 192.168.122.209 [46324.282695] [tdb] Close table 'filter0.tdb' Apr 26 04:56:13 192.168.122.209 [46324.283137] [tempesta fw] modules are stopped Apr 26 04:56:14 192.168.122.209 [46324.500688] [tempesta fw] exiting... Apr 26 04:56:14 192.168.122.209 [46324.632818] [tdb] Shutdown Tempesta DB Apr 26 04:56:14 192.168.122.209 [46324.838486] End test: t_health_monitoring.test_health_monitor.H2HmResponsesPipelined.test_hm_pipelined_3_hm Apr 26 04:56:14 192.168.122.209 [46324.861500] Start test: t_health_monitoring.test_health_monitor.H2HmResponsesPipelined.test_hm_pipelined_4_hm Apr 26 04:56:15 192.168.122.209 [46325.975410] [tdb] Start Tempesta DB Apr 26 04:56:15 192.168.122.209 [46326.100648] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:56:17 192.168.122.209 [46328.029640] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46328.029640] Maybe that's fine, but it's worth checking the [46328.029640] config - if there is no relations between the [46328.029640] names, then host name confusion attack is possible. Apr 26 04:56:17 192.168.122.209 [46328.164184] [tempesta fw] Configuration processing is completed. Apr 26 04:56:17 192.168.122.209 [46328.214650] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:56:18 192.168.122.209 [46328.619710] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:56:18 192.168.122.209 [46328.682685] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:56:18 192.168.122.209 [46328.709901] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:56:18 192.168.122.209 [46328.744144] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:56:18 192.168.122.209 [46328.784156] [tempesta fw] Tempesta FW is ready Apr 26 04:56:22 192.168.122.209 [46332.748638] [tempesta fw] Warning: Response for health monitor 'hm0': crc32 value '0' mismatched (expected value: '838041247') Apr 26 04:56:22 192.168.122.209 [46332.751849] [tempesta fw] Warning: Response for health monitor 'hm0': crc32 value '0' mismatched (expected value: '838041247') Apr 26 04:56:22 192.168.122.209 [46332.754971] [tempesta fw] Warning: Response for health monitor 'hm0': crc32 value '0' mismatched (expected value: '838041247') Apr 26 04:56:22 192.168.122.209 [46332.758097] [tempesta fw] Warning: Response for health monitor 'hm0': crc32 value '0' mismatched (expected value: '838041247') Apr 26 04:56:22 192.168.122.209 [46333.193505] [tdb] Close table 'client0.tdb' Apr 26 04:56:22 192.168.122.209 [46333.381197] [tdb] Close table 'sessions0.tdb' Apr 26 04:56:26 192.168.122.209 [46336.580200] [tdb] Close table 'cache0.tdb' Apr 26 04:56:26 192.168.122.209 [46336.810992] [tdb] Close table 'filter0.tdb' Apr 26 04:56:26 192.168.122.209 [46336.811430] [tempesta fw] modules are stopped Apr 26 04:56:26 192.168.122.209 [46337.039740] [tempesta fw] exiting... Apr 26 04:56:26 192.168.122.209 [46337.194874] [tdb] Shutdown Tempesta DB Apr 26 04:56:27 192.168.122.209 [46337.410137] End test: t_health_monitoring.test_health_monitor.H2HmResponsesPipelined.test_hm_pipelined_4_hm Apr 26 04:56:27 192.168.122.209 [46337.426168] Start test: t_health_monitoring.test_health_monitor.TestHealthMonitor.test Apr 26 04:56:28 192.168.122.209 [46338.547559] [tdb] Start Tempesta DB Apr 26 04:56:28 192.168.122.209 [46338.693663] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:56:30 192.168.122.209 [46340.820455] [tempesta fw] Configuration processing is completed. Apr 26 04:56:30 192.168.122.209 [46340.877241] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:56:30 192.168.122.209 [46340.906522] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:56:30 192.168.122.209 [46340.933656] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:56:30 192.168.122.209 [46341.172379] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:56:31 192.168.122.209 [46341.672323] [tempesta fw] Tempesta FW is ready Apr 26 04:56:31 192.168.122.209 [46341.964266] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8082 Apr 26 04:56:31 192.168.122.209 [46342.028253] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8081 Apr 26 04:56:31 192.168.122.209 [46342.060192] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8080 Apr 26 04:56:32 192.168.122.209 [46342.925653] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8082: 1 tries, keep trying... Apr 26 04:56:32 192.168.122.209 [46342.925695] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8082: 1 tries, keep trying... Apr 26 04:56:32 192.168.122.209 [46342.925767] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8082: 1 tries, keep trying... Apr 26 04:56:32 192.168.122.209 [46342.925845] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8082: 1 tries, keep trying... Apr 26 04:56:32 192.168.122.209 [46342.926717] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8082: 1 tries, keep trying... Apr 26 04:56:32 192.168.122.209 [46342.927705] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8081: 1 tries, keep trying... Apr 26 04:56:32 192.168.122.209 [46342.928601] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8081: 1 tries, keep trying... Apr 26 04:56:36 192.168.122.209 [46347.084280] net_ratelimit: 101 callbacks suppressed Apr 26 04:56:36 192.168.122.209 [46347.084283] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8082 Apr 26 04:56:36 192.168.122.209 [46347.152251] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8081 Apr 26 04:56:36 192.168.122.209 [46347.180313] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8080 Apr 26 04:56:37 192.168.122.209 [46348.108309] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8082 Apr 26 04:56:37 192.168.122.209 [46348.172386] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8081 Apr 26 04:56:37 192.168.122.209 [46348.208279] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8080 Apr 26 04:56:38 192.168.122.209 [46349.136279] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8082 Apr 26 04:56:38 192.168.122.209 [46349.200323] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8081 Apr 26 04:56:38 192.168.122.209 [46349.228337] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8080 Apr 26 04:56:39 192.168.122.209 [46350.156278] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8082 Apr 26 04:56:41 192.168.122.209 [46352.208344] net_ratelimit: 5 callbacks suppressed Apr 26 04:56:41 192.168.122.209 [46352.208349] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8082 Apr 26 04:56:41 192.168.122.209 [46352.272370] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8081 Apr 26 04:56:41 192.168.122.209 [46352.304872] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '400' mismatched Apr 26 04:56:42 192.168.122.209 [46353.229920] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:42 192.168.122.209 [46353.232354] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8082 Apr 26 04:56:42 192.168.122.209 [46353.296645] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '400' mismatched Apr 26 04:56:42 192.168.122.209 [46353.323378] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:43 192.168.122.209 [46353.408752] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:43 192.168.122.209 [46353.503278] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:43 192.168.122.209 [46353.596521] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:43 192.168.122.209 [46353.690992] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:43 192.168.122.209 [46353.780624] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:43 192.168.122.209 [46353.871053] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:43 192.168.122.209 [46353.958154] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:43 192.168.122.209 [46354.053145] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:43 192.168.122.209 [46354.152246] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:43 192.168.122.209 [46354.248331] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:43 192.168.122.209 [46354.252413] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8082 Apr 26 04:56:43 192.168.122.209 [46354.325415] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:44 192.168.122.209 [46354.428383] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:44 192.168.122.209 [46354.522263] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:44 192.168.122.209 [46354.621341] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:44 192.168.122.209 [46354.718157] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:44 192.168.122.209 [46354.813551] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:44 192.168.122.209 [46354.910273] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:44 192.168.122.209 [46355.000873] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:44 192.168.122.209 [46355.091349] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:44 192.168.122.209 [46355.185059] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:44 192.168.122.209 [46355.280525] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8082 Apr 26 04:56:44 192.168.122.209 [46355.283355] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:44 192.168.122.209 [46355.379694] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:45 192.168.122.209 [46355.478371] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:45 192.168.122.209 [46355.567255] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:45 192.168.122.209 [46355.653113] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:45 192.168.122.209 [46355.741068] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:45 192.168.122.209 [46355.838907] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:45 192.168.122.209 [46355.931802] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:45 192.168.122.209 [46356.026204] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:45 192.168.122.209 [46356.118437] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:45 192.168.122.209 [46356.205111] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:45 192.168.122.209 [46356.289678] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:45 192.168.122.209 [46356.300405] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8082 Apr 26 04:56:46 192.168.122.209 [46356.391848] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:46 192.168.122.209 [46356.486887] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:46 192.168.122.209 [46356.579351] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:46 192.168.122.209 [46356.664663] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:46 192.168.122.209 [46356.760582] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:46 192.168.122.209 [46356.853109] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:46 192.168.122.209 [46356.943276] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:46 192.168.122.209 [46357.031497] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:46 192.168.122.209 [46357.131826] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:46 192.168.122.209 [46357.224624] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:46 192.168.122.209 [46357.320905] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:46 192.168.122.209 [46357.328373] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8082 Apr 26 04:56:47 192.168.122.209 [46357.426296] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:47 192.168.122.209 [46357.520150] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:47 192.168.122.209 [46357.618611] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:47 192.168.122.209 [46357.723606] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:47 192.168.122.209 [46357.814940] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:47 192.168.122.209 [46357.911428] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:47 192.168.122.209 [46358.006136] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:47 192.168.122.209 [46358.102094] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:47 192.168.122.209 [46358.193127] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:47 192.168.122.209 [46358.286586] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:47 192.168.122.209 [46358.352463] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8082 Apr 26 04:56:47 192.168.122.209 [46358.386628] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:48 192.168.122.209 [46358.479362] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:48 192.168.122.209 [46358.583864] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:48 192.168.122.209 [46358.674203] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:48 192.168.122.209 [46358.765217] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:48 192.168.122.209 [46358.858915] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:48 192.168.122.209 [46358.955815] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:48 192.168.122.209 [46359.047897] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:48 192.168.122.209 [46359.137354] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:48 192.168.122.209 [46359.228493] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:48 192.168.122.209 [46359.323225] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:48 192.168.122.209 [46359.376395] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8082 Apr 26 04:56:49 192.168.122.209 [46359.421731] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:49 192.168.122.209 [46359.526359] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:49 192.168.122.209 [46359.625494] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:49 192.168.122.209 [46359.724391] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:49 192.168.122.209 [46359.818613] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:49 192.168.122.209 [46359.913046] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:49 192.168.122.209 [46360.009616] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:49 192.168.122.209 [46360.111355] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:49 192.168.122.209 [46360.210797] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:49 192.168.122.209 [46360.311799] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:50 192.168.122.209 [46360.396492] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8082 Apr 26 04:56:50 192.168.122.209 [46360.401414] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:50 192.168.122.209 [46360.495220] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:50 192.168.122.209 [46360.587663] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:50 192.168.122.209 [46360.674615] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:50 192.168.122.209 [46360.766097] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:50 192.168.122.209 [46360.861321] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:50 192.168.122.209 [46360.954002] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:50 192.168.122.209 [46361.049198] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:50 192.168.122.209 [46361.140079] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:50 192.168.122.209 [46361.232961] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:50 192.168.122.209 [46361.330429] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:51 192.168.122.209 [46361.411936] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:51 192.168.122.209 [46361.424492] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8082 Apr 26 04:56:51 192.168.122.209 [46361.514013] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:51 192.168.122.209 [46361.612062] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:51 192.168.122.209 [46361.699559] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:51 192.168.122.209 [46361.785260] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:51 192.168.122.209 [46361.869589] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:51 192.168.122.209 [46361.962738] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:51 192.168.122.209 [46362.052570] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:51 192.168.122.209 [46362.144635] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:51 192.168.122.209 [46362.236934] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:51 192.168.122.209 [46362.336335] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:52 192.168.122.209 [46362.429451] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:52 192.168.122.209 [46362.448457] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8082 Apr 26 04:56:52 192.168.122.209 [46362.530258] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:53 192.168.122.209 [46363.468913] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '400' mismatched Apr 26 04:56:53 192.168.122.209 [46363.536988] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '400' mismatched Apr 26 04:56:53 192.168.122.209 [46363.568469] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:53 192.168.122.209 [46363.570174] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '400' mismatched Apr 26 04:56:53 192.168.122.209 [46363.658178] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:53 192.168.122.209 [46363.748870] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:53 192.168.122.209 [46363.840560] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:53 192.168.122.209 [46363.932138] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:53 192.168.122.209 [46364.024714] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:53 192.168.122.209 [46364.124850] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:53 192.168.122.209 [46364.215958] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:54 192.168.122.209 [46364.390057] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:54 192.168.122.209 [46364.580343] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:54 192.168.122.209 [46364.677889] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:54 192.168.122.209 [46364.866212] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:54 192.168.122.209 [46365.044112] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:54 192.168.122.209 [46365.128356] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:54 192.168.122.209 [46365.318263] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:55 192.168.122.209 [46365.507961] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:55 192.168.122.209 [46365.599738] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:55 192.168.122.209 [46365.786521] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:55 192.168.122.209 [46365.969653] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:55 192.168.122.209 [46366.074332] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:55 192.168.122.209 [46366.267138] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:56 192.168.122.209 [46366.460913] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:56 192.168.122.209 [46366.557905] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:56 192.168.122.209 [46366.739161] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:56 192.168.122.209 [46366.934162] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:56 192.168.122.209 [46367.023217] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:56 192.168.122.209 [46367.227923] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:56 192.168.122.209 [46367.324886] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:57 192.168.122.209 [46367.512148] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:57 192.168.122.209 [46367.609442] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:57 192.168.122.209 [46367.812155] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:57 192.168.122.209 [46367.904913] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:57 192.168.122.209 [46368.099354] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:57 192.168.122.209 [46368.204909] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:57 192.168.122.209 [46368.385255] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:58 192.168.122.209 [46368.486457] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:58 192.168.122.209 [46368.581511] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:58 192.168.122.209 [46368.674090] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:58 192.168.122.209 [46368.762849] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:58 192.168.122.209 [46368.855211] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:58 192.168.122.209 [46368.956283] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:58 192.168.122.209 [46369.045717] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:58 192.168.122.209 [46369.230720] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:59 192.168.122.209 [46369.417707] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:59 192.168.122.209 [46369.509183] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:59 192.168.122.209 [46369.702458] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:59 192.168.122.209 [46369.891089] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:59 192.168.122.209 [46369.980804] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:56:59 192.168.122.209 [46370.166494] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:56:59 192.168.122.209 [46370.338991] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:57:00 192.168.122.209 [46370.430342] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:57:00 192.168.122.209 [46370.614719] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:57:00 192.168.122.209 [46370.796596] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:57:00 192.168.122.209 [46370.888812] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:57:00 192.168.122.209 [46371.081397] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:57:00 192.168.122.209 [46371.275223] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:57:00 192.168.122.209 [46371.371035] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:57:01 192.168.122.209 [46371.549200] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:57:01 192.168.122.209 [46371.733004] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:57:01 192.168.122.209 [46371.824504] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:57:01 192.168.122.209 [46372.010312] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:57:01 192.168.122.209 [46372.111052] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:57:01 192.168.122.209 [46372.304513] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:57:02 192.168.122.209 [46372.400253] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:57:02 192.168.122.209 [46372.595150] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:57:02 192.168.122.209 [46372.692381] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:57:02 192.168.122.209 [46372.866844] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:57:02 192.168.122.209 [46372.954221] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:57:02 192.168.122.209 [46373.136849] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:57:02 192.168.122.209 [46373.229536] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:57:02 192.168.122.209 [46373.324000] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:57:03 192.168.122.209 [46373.419285] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:57:03 192.168.122.209 [46373.516823] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:57:03 192.168.122.209 [46373.608720] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:57:03 192.168.122.209 [46373.700277] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:57:03 192.168.122.209 [46373.791301] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:57:03 192.168.122.209 [46373.991352] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:57:03 192.168.122.209 [46374.186006] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:57:03 192.168.122.209 [46374.279062] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:57:04 192.168.122.209 [46374.464134] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:57:04 192.168.122.209 [46374.664874] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:57:04 192.168.122.209 [46374.761017] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:57:04 192.168.122.209 [46374.947894] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:57:04 192.168.122.209 [46375.124854] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:57:04 192.168.122.209 [46375.219911] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:57:05 192.168.122.209 [46375.405252] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:57:05 192.168.122.209 [46375.587316] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:57:05 192.168.122.209 [46375.680493] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:57:05 192.168.122.209 [46375.850845] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:57:05 192.168.122.209 [46376.033572] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:57:05 192.168.122.209 [46376.132932] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:57:05 192.168.122.209 [46376.299320] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:57:06 192.168.122.209 [46376.491461] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:57:06 192.168.122.209 [46376.572764] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:57:06 192.168.122.209 [46376.753716] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:57:06 192.168.122.209 [46376.844040] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:57:06 192.168.122.209 [46377.029200] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:57:06 192.168.122.209 [46377.116035] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:57:06 192.168.122.209 [46377.306572] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:57:07 192.168.122.209 [46377.398117] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:57:07 192.168.122.209 [46377.581237] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:57:07 192.168.122.209 [46377.676315] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:57:07 192.168.122.209 [46377.858944] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:57:07 192.168.122.209 [46377.943544] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:57:07 192.168.122.209 [46378.028465] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:57:07 192.168.122.209 [46378.135771] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:57:07 192.168.122.209 [46378.228850] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:57:07 192.168.122.209 [46378.322367] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:57:08 192.168.122.209 [46378.413066] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:57:08 192.168.122.209 [46378.522134] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:57:08 192.168.122.209 [46378.707854] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:57:08 192.168.122.209 [46378.891607] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:57:08 192.168.122.209 [46378.974764] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:57:08 192.168.122.209 [46379.153886] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:57:08 192.168.122.209 [46379.331510] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:57:09 192.168.122.209 [46379.422862] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:57:09 192.168.122.209 [46379.608128] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:57:09 192.168.122.209 [46379.787081] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:57:09 192.168.122.209 [46379.865820] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:57:09 192.168.122.209 [46380.021260] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:57:09 192.168.122.209 [46380.223820] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:57:09 192.168.122.209 [46380.317863] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:57:10 192.168.122.209 [46380.500874] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:57:10 192.168.122.209 [46380.685122] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:57:10 192.168.122.209 [46380.781051] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:57:10 192.168.122.209 [46380.990908] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:57:10 192.168.122.209 [46381.172836] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:57:10 192.168.122.209 [46381.273723] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:57:11 192.168.122.209 [46381.445822] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:57:11 192.168.122.209 [46381.532029] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:57:11 192.168.122.209 [46381.703565] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:57:11 192.168.122.209 [46381.794901] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 04:57:11 192.168.122.209 [46381.976576] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 04:57:12 192.168.122.209 [46382.536763] [tdb] Close table 'client0.tdb' Apr 26 04:57:12 192.168.122.209 [46382.755043] [tdb] Close table 'sessions0.tdb' Apr 26 04:57:12 192.168.122.209 [46382.970984] [tdb] Close table 'filter0.tdb' Apr 26 04:57:12 192.168.122.209 [46382.971412] [tempesta fw] modules are stopped Apr 26 04:57:12 192.168.122.209 [46383.184919] [tempesta fw] exiting... Apr 26 04:57:12 192.168.122.209 [46383.298133] [tdb] Shutdown Tempesta DB Apr 26 04:57:13 192.168.122.209 [46383.558774] End test: t_health_monitoring.test_health_monitor.TestHealthMonitor.test Apr 26 04:57:13 192.168.122.209 [46383.570531] Start test: t_health_monitoring.test_health_monitor.TestHealthMonitorForDisabledServer.test Apr 26 04:57:14 192.168.122.209 [46384.708652] [tdb] Start Tempesta DB Apr 26 04:57:14 192.168.122.209 [46384.850527] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:57:15 192.168.122.209 [46385.813261] [tempesta fw] Configuration processing is completed. Apr 26 04:57:15 192.168.122.209 [46385.864904] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:57:15 192.168.122.209 [46386.273417] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:57:15 192.168.122.209 [46386.339073] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:57:15 192.168.122.209 [46386.366119] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:57:16 192.168.122.209 [46386.444863] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:57:16 192.168.122.209 [46386.484888] [tempesta fw] Tempesta FW is ready Apr 26 04:57:17 192.168.122.209 [46388.024018] [tdb] Close table 'client0.tdb' Apr 26 04:57:17 192.168.122.209 [46388.211784] [tdb] Close table 'sessions0.tdb' Apr 26 04:57:21 192.168.122.209 [46391.404189] [tdb] Close table 'cache0.tdb' Apr 26 04:57:21 192.168.122.209 [46391.644874] [tdb] Close table 'filter0.tdb' Apr 26 04:57:21 192.168.122.209 [46391.645311] [tempesta fw] modules are stopped Apr 26 04:57:21 192.168.122.209 [46391.842112] [tempesta fw] exiting... Apr 26 04:57:21 192.168.122.209 [46391.999590] [tdb] Shutdown Tempesta DB Apr 26 04:57:21 192.168.122.209 [46392.225760] End test: t_health_monitoring.test_health_monitor.TestHealthMonitorForDisabledServer.test Apr 26 04:57:21 192.168.122.209 [46392.239331] Start test: t_health_monitoring.test_health_monitor.TestHealthStatH2.test_cached_responses_included Apr 26 04:57:23 192.168.122.209 [46393.429110] [tdb] Start Tempesta DB Apr 26 04:57:23 192.168.122.209 [46393.586143] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:57:24 192.168.122.209 [46395.074321] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46395.074321] Maybe that's fine, but it's worth checking the [46395.074321] config - if there is no relations between the [46395.074321] names, then host name confusion attack is possible. Apr 26 04:57:24 192.168.122.209 [46395.221108] [tempesta fw] Configuration processing is completed. Apr 26 04:57:24 192.168.122.209 [46395.289337] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:57:25 192.168.122.209 [46395.698422] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:57:25 192.168.122.209 [46395.760357] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:57:25 192.168.122.209 [46395.785602] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:57:25 192.168.122.209 [46395.829047] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:57:25 192.168.122.209 [46395.830770] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:57:25 192.168.122.209 [46395.869009] [tempesta fw] Tempesta FW is ready Apr 26 04:57:26 192.168.122.209 [46396.481966] [tdb] Close table 'client0.tdb' Apr 26 04:57:26 192.168.122.209 [46396.694757] [tdb] Close table 'sessions0.tdb' Apr 26 04:57:29 192.168.122.209 [46399.922244] [tdb] Close table 'cache0.tdb' Apr 26 04:57:29 192.168.122.209 [46400.153091] [tdb] Close table 'filter0.tdb' Apr 26 04:57:29 192.168.122.209 [46400.153530] [tempesta fw] modules are stopped Apr 26 04:57:29 192.168.122.209 [46400.362079] [tempesta fw] exiting... Apr 26 04:57:30 192.168.122.209 [46400.481399] [tdb] Shutdown Tempesta DB Apr 26 04:57:30 192.168.122.209 [46400.702015] End test: t_health_monitoring.test_health_monitor.TestHealthStatH2.test_cached_responses_included Apr 26 04:57:30 192.168.122.209 [46400.716856] Start test: t_health_monitoring.test_health_monitor.TestHealthStatH2.test_smoke Apr 26 04:57:31 192.168.122.209 [46401.900131] [tdb] Start Tempesta DB Apr 26 04:57:31 192.168.122.209 [46402.053945] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:57:33 192.168.122.209 [46403.422546] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46403.422546] Maybe that's fine, but it's worth checking the [46403.422546] config - if there is no relations between the [46403.422546] names, then host name confusion attack is possible. Apr 26 04:57:33 192.168.122.209 [46403.521178] [tempesta fw] Configuration processing is completed. Apr 26 04:57:33 192.168.122.209 [46403.590888] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:57:33 192.168.122.209 [46404.097732] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:57:33 192.168.122.209 [46404.129545] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:57:33 192.168.122.209 [46404.161678] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:57:33 192.168.122.209 [46404.225148] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:57:33 192.168.122.209 [46404.226943] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:57:33 192.168.122.209 [46404.273057] [tempesta fw] Tempesta FW is ready Apr 26 04:57:34 192.168.122.209 [46404.953515] [tdb] Close table 'client0.tdb' Apr 26 04:57:34 192.168.122.209 [46405.136184] [tdb] Close table 'sessions0.tdb' Apr 26 04:57:37 192.168.122.209 [46408.343754] [tdb] Close table 'cache0.tdb' Apr 26 04:57:38 192.168.122.209 [46408.581790] [tdb] Close table 'filter0.tdb' Apr 26 04:57:38 192.168.122.209 [46408.582229] [tempesta fw] modules are stopped Apr 26 04:57:38 192.168.122.209 [46408.783421] [tempesta fw] exiting... Apr 26 04:57:38 192.168.122.209 [46408.948328] [tdb] Shutdown Tempesta DB Apr 26 04:57:38 192.168.122.209 [46409.162730] End test: t_health_monitoring.test_health_monitor.TestHealthStatH2.test_smoke Apr 26 04:57:38 192.168.122.209 [46409.176883] Start test: t_health_monitoring.test_health_monitor.TestHealthStatHttp.test_cached_responses_included Apr 26 04:57:39 192.168.122.209 [46410.347234] [tdb] Start Tempesta DB Apr 26 04:57:40 192.168.122.209 [46410.485853] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:57:41 192.168.122.209 [46411.906622] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46411.906622] Maybe that's fine, but it's worth checking the [46411.906622] config - if there is no relations between the [46411.906622] names, then host name confusion attack is possible. Apr 26 04:57:41 192.168.122.209 [46412.045309] [tempesta fw] Configuration processing is completed. Apr 26 04:57:41 192.168.122.209 [46412.099990] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:57:42 192.168.122.209 [46412.538687] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:57:42 192.168.122.209 [46412.597544] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:57:42 192.168.122.209 [46412.633221] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:57:42 192.168.122.209 [46412.693282] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:57:42 192.168.122.209 [46412.694994] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:57:42 192.168.122.209 [46412.737229] [tempesta fw] Tempesta FW is ready Apr 26 04:57:42 192.168.122.209 [46413.340117] [tdb] Close table 'client0.tdb' Apr 26 04:57:43 192.168.122.209 [46413.529136] [tdb] Close table 'sessions0.tdb' Apr 26 04:57:46 192.168.122.209 [46416.758144] [tdb] Close table 'cache0.tdb' Apr 26 04:57:46 192.168.122.209 [46417.013091] [tdb] Close table 'filter0.tdb' Apr 26 04:57:46 192.168.122.209 [46417.013582] [tempesta fw] modules are stopped Apr 26 04:57:46 192.168.122.209 [46417.227751] [tempesta fw] exiting... Apr 26 04:57:46 192.168.122.209 [46417.362027] [tdb] Shutdown Tempesta DB Apr 26 04:57:47 192.168.122.209 [46417.567866] End test: t_health_monitoring.test_health_monitor.TestHealthStatHttp.test_cached_responses_included Apr 26 04:57:47 192.168.122.209 [46417.582324] Start test: t_health_monitoring.test_health_monitor.TestHealthStatHttp.test_smoke Apr 26 04:57:48 192.168.122.209 [46418.715769] [tdb] Start Tempesta DB Apr 26 04:57:48 192.168.122.209 [46418.875501] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:57:49 192.168.122.209 [46420.194701] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46420.194701] Maybe that's fine, but it's worth checking the [46420.194701] config - if there is no relations between the [46420.194701] names, then host name confusion attack is possible. Apr 26 04:57:49 192.168.122.209 [46420.293359] [tempesta fw] Configuration processing is completed. Apr 26 04:57:49 192.168.122.209 [46420.349457] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:57:50 192.168.122.209 [46420.820926] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:57:50 192.168.122.209 [46420.849669] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:57:50 192.168.122.209 [46420.881371] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:57:50 192.168.122.209 [46420.945430] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:57:50 192.168.122.209 [46420.947176] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:57:50 192.168.122.209 [46420.985328] [tempesta fw] Tempesta FW is ready Apr 26 04:57:51 192.168.122.209 [46421.634736] [tdb] Close table 'client0.tdb' Apr 26 04:57:51 192.168.122.209 [46421.852619] [tdb] Close table 'sessions0.tdb' Apr 26 04:57:54 192.168.122.209 [46425.104581] [tdb] Close table 'cache0.tdb' Apr 26 04:57:55 192.168.122.209 [46425.392798] [tdb] Close table 'filter0.tdb' Apr 26 04:57:55 192.168.122.209 [46425.393290] [tempesta fw] modules are stopped Apr 26 04:57:55 192.168.122.209 [46425.599645] [tempesta fw] exiting... Apr 26 04:57:55 192.168.122.209 [46425.725040] [tdb] Shutdown Tempesta DB Apr 26 04:57:55 192.168.122.209 [46425.970025] End test: t_health_monitoring.test_health_monitor.TestHealthStatHttp.test_smoke Apr 26 04:57:55 192.168.122.209 [46425.977347] Start test: t_health_monitoring.test_health_monitor.TestHealthStatServerH2.test_smoke Apr 26 04:57:56 192.168.122.209 [46427.148387] [tdb] Start Tempesta DB Apr 26 04:57:56 192.168.122.209 [46427.296233] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:57:58 192.168.122.209 [46428.746187] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46428.746187] Maybe that's fine, but it's worth checking the [46428.746187] config - if there is no relations between the [46428.746187] names, then host name confusion attack is possible. Apr 26 04:57:58 192.168.122.209 [46428.877511] [tempesta fw] Configuration processing is completed. Apr 26 04:57:58 192.168.122.209 [46428.934834] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:57:59 192.168.122.209 [46429.456570] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:57:59 192.168.122.209 [46429.490798] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:57:59 192.168.122.209 [46429.526591] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:57:59 192.168.122.209 [46429.581530] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:57:59 192.168.122.209 [46429.583348] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:57:59 192.168.122.209 [46429.625423] [tempesta fw] Tempesta FW is ready Apr 26 04:57:59 192.168.122.209 [46430.367192] [tdb] Close table 'client0.tdb' Apr 26 04:58:00 192.168.122.209 [46430.554948] [tdb] Close table 'sessions0.tdb' Apr 26 04:58:03 192.168.122.209 [46433.688993] [tdb] Close table 'cache0.tdb' Apr 26 04:58:03 192.168.122.209 [46433.930780] [tdb] Close table 'filter0.tdb' Apr 26 04:58:03 192.168.122.209 [46433.931445] [tempesta fw] modules are stopped Apr 26 04:58:03 192.168.122.209 [46434.149861] [tempesta fw] exiting... Apr 26 04:58:03 192.168.122.209 [46434.308192] [tdb] Shutdown Tempesta DB Apr 26 04:58:04 192.168.122.209 [46434.525311] End test: t_health_monitoring.test_health_monitor.TestHealthStatServerH2.test_smoke Apr 26 04:58:04 192.168.122.209 [46434.537342] Start test: t_health_monitoring.test_health_monitor.TestHealthStatServerHttp.test_smoke Apr 26 04:58:05 192.168.122.209 [46435.647968] [tdb] Start Tempesta DB Apr 26 04:58:05 192.168.122.209 [46435.789726] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:58:06 192.168.122.209 [46437.138955] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46437.138955] Maybe that's fine, but it's worth checking the [46437.138955] config - if there is no relations between the [46437.138955] names, then host name confusion attack is possible. Apr 26 04:58:06 192.168.122.209 [46437.261622] [tempesta fw] Configuration processing is completed. Apr 26 04:58:06 192.168.122.209 [46437.312640] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:58:07 192.168.122.209 [46437.736120] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:58:07 192.168.122.209 [46437.762319] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:58:07 192.168.122.209 [46437.789935] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:58:07 192.168.122.209 [46437.841589] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:58:07 192.168.122.209 [46437.843274] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:58:07 192.168.122.209 [46437.897527] [tempesta fw] Tempesta FW is ready Apr 26 04:58:08 192.168.122.209 [46438.641329] [tdb] Close table 'client0.tdb' Apr 26 04:58:08 192.168.122.209 [46438.834977] [tdb] Close table 'sessions0.tdb' Apr 26 04:58:11 192.168.122.209 [46441.963805] [tdb] Close table 'cache0.tdb' Apr 26 04:58:11 192.168.122.209 [46442.203615] [tdb] Close table 'filter0.tdb' Apr 26 04:58:11 192.168.122.209 [46442.204050] [tempesta fw] modules are stopped Apr 26 04:58:12 192.168.122.209 [46442.409181] [tempesta fw] exiting... Apr 26 04:58:12 192.168.122.209 [46442.545405] [tdb] Shutdown Tempesta DB Apr 26 04:58:12 192.168.122.209 [46442.748798] End test: t_health_monitoring.test_health_monitor.TestHealthStatServerHttp.test_smoke Apr 26 04:58:12 192.168.122.209 [46442.770575] Start test: t_health_monitoring.test_health_monitor.TestHmCrcExplicitCRC.test Apr 26 04:58:13 192.168.122.209 [46443.974950] [tdb] Start Tempesta DB Apr 26 04:58:13 192.168.122.209 [46444.127421] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:58:15 192.168.122.209 [46445.793651] [tempesta fw] Configuration processing is completed. Apr 26 04:58:15 192.168.122.209 [46445.843836] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:58:15 192.168.122.209 [46446.251204] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:58:15 192.168.122.209 [46446.307325] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:58:15 192.168.122.209 [46446.332787] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:58:16 192.168.122.209 [46446.409664] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:58:16 192.168.122.209 [46446.449645] [tempesta fw] Tempesta FW is ready Apr 26 04:58:25 192.168.122.209 [46455.630927] [tempesta fw] Warning: Response for health monitor 'auto': crc32 value '3332881455' mismatched (expected value: '838041247') Apr 26 04:58:25 192.168.122.209 [46456.147653] [tdb] Close table 'client0.tdb' Apr 26 04:58:25 192.168.122.209 [46456.334206] [tdb] Close table 'sessions0.tdb' Apr 26 04:58:29 192.168.122.209 [46459.515714] [tdb] Close table 'cache0.tdb' Apr 26 04:58:29 192.168.122.209 [46459.753426] [tdb] Close table 'filter0.tdb' Apr 26 04:58:29 192.168.122.209 [46459.753900] [tempesta fw] modules are stopped Apr 26 04:58:29 192.168.122.209 [46459.919073] [tempesta fw] exiting... Apr 26 04:58:29 192.168.122.209 [46460.064956] [tdb] Shutdown Tempesta DB Apr 26 04:58:29 192.168.122.209 [46460.268005] End test: t_health_monitoring.test_health_monitor.TestHmCrcExplicitCRC.test Apr 26 04:58:29 192.168.122.209 [46460.287568] Start test: t_health_monitoring.test_health_monitor.TestHmCrcImplicitCRC.test Apr 26 04:58:31 192.168.122.209 [46461.480585] [tdb] Start Tempesta DB Apr 26 04:58:31 192.168.122.209 [46461.613357] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:58:32 192.168.122.209 [46462.977962] [tempesta fw] Configuration processing is completed. Apr 26 04:58:32 192.168.122.209 [46463.029852] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:58:33 192.168.122.209 [46463.449189] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:58:33 192.168.122.209 [46463.511963] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:58:33 192.168.122.209 [46463.539789] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:58:33 192.168.122.209 [46463.593926] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:58:33 192.168.122.209 [46463.641860] [tempesta fw] Tempesta FW is ready Apr 26 04:59:03 192.168.122.209 [46494.030842] [tempesta fw] Warning: Response for health monitor 'auto': crc32 value '3332881455' mismatched (expected value: '838041247') Apr 26 04:59:04 192.168.122.209 [46494.550829] [tdb] Close table 'client0.tdb' Apr 26 04:59:04 192.168.122.209 [46494.741900] [tdb] Close table 'sessions0.tdb' Apr 26 04:59:07 192.168.122.209 [46497.955341] [tdb] Close table 'cache0.tdb' Apr 26 04:59:07 192.168.122.209 [46498.196379] [tdb] Close table 'filter0.tdb' Apr 26 04:59:07 192.168.122.209 [46498.196849] [tempesta fw] modules are stopped Apr 26 04:59:07 192.168.122.209 [46498.382459] [tempesta fw] exiting... Apr 26 04:59:08 192.168.122.209 [46498.509567] [tdb] Shutdown Tempesta DB Apr 26 04:59:08 192.168.122.209 [46498.712052] End test: t_health_monitoring.test_health_monitor.TestHmCrcImplicitCRC.test Apr 26 04:59:08 192.168.122.209 [46498.721728] Start test: t_health_monitoring.test_health_monitor.TestHmCrcPredefinedCRC.test Apr 26 04:59:09 192.168.122.209 [46499.937298] [tdb] Start Tempesta DB Apr 26 04:59:09 192.168.122.209 [46500.088250] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:59:11 192.168.122.209 [46501.766525] [tempesta fw] Configuration processing is completed. Apr 26 04:59:11 192.168.122.209 [46501.820400] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:59:11 192.168.122.209 [46502.246658] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:59:11 192.168.122.209 [46502.273163] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:59:11 192.168.122.209 [46502.299264] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:59:11 192.168.122.209 [46502.362435] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:59:12 192.168.122.209 [46502.406377] [tempesta fw] Tempesta FW is ready Apr 26 04:59:18 192.168.122.209 [46508.623424] [tempesta fw] Warning: Response for health monitor 'hm0': crc32 value '3332881455' mismatched (expected value: '838041247') Apr 26 04:59:18 192.168.122.209 [46509.182954] [tdb] Close table 'client0.tdb' Apr 26 04:59:18 192.168.122.209 [46509.385368] [tdb] Close table 'sessions0.tdb' Apr 26 04:59:22 192.168.122.209 [46512.708126] [tdb] Close table 'cache0.tdb' Apr 26 04:59:22 192.168.122.209 [46512.972822] [tdb] Close table 'filter0.tdb' Apr 26 04:59:22 192.168.122.209 [46512.973264] [tempesta fw] modules are stopped Apr 26 04:59:22 192.168.122.209 [46513.136710] [tempesta fw] exiting... Apr 26 04:59:22 192.168.122.209 [46513.268545] [tdb] Shutdown Tempesta DB Apr 26 04:59:23 192.168.122.209 [46513.469590] End test: t_health_monitoring.test_health_monitor.TestHmCrcPredefinedCRC.test Apr 26 04:59:23 192.168.122.209 [46513.496309] Start test: t_health_monitoring.test_health_monitor.TestHmMalformedResponse.test Apr 26 04:59:24 192.168.122.209 [46514.597490] [tdb] Start Tempesta DB Apr 26 04:59:24 192.168.122.209 [46514.748956] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:59:25 192.168.122.209 [46516.338652] [tempesta fw] Configuration processing is completed. Apr 26 04:59:26 192.168.122.209 [46516.396049] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:59:26 192.168.122.209 [46516.862968] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:59:26 192.168.122.209 [46516.921694] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:59:26 192.168.122.209 [46516.951439] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:59:26 192.168.122.209 [46516.990624] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:59:26 192.168.122.209 [46517.030548] [tempesta fw] Tempesta FW is ready Apr 26 04:59:27 192.168.122.209 [46517.967467] [tempesta fw] Warning: Parser error: state=RGen_HdrOtherN input(-8)=0x6f('00 OK [46517.967467] Con tent-Length:5 [46517.967467] [46517.967467] Hello') data_len=43 off=18 Apr 26 04:59:28 192.168.122.209 [46517.972021] [tempesta fw] Warning: Health Monitor response malformed Apr 26 04:59:28 192.168.122.209 [46518.991204] [tempesta fw] Warning: Parser error: state=RGen_HdrOtherN input(-8)=0x6f('00 OK [46518.991204] Con tent-Length:5 [46518.991204] [46518.991204] Hello') data_len=43 off=18 Apr 26 04:59:29 192.168.122.209 [46518.997574] [tempesta fw] Warning: Health Monitor response malformed Apr 26 04:59:29 192.168.122.209 [46519.544276] [tdb] Close table 'client0.tdb' Apr 26 04:59:29 192.168.122.209 [46519.755306] [tdb] Close table 'sessions0.tdb' Apr 26 04:59:32 192.168.122.209 [46523.127099] [tdb] Close table 'cache0.tdb' Apr 26 04:59:32 192.168.122.209 [46523.381558] [tdb] Close table 'filter0.tdb' Apr 26 04:59:32 192.168.122.209 [46523.382012] [tempesta fw] modules are stopped Apr 26 04:59:33 192.168.122.209 [46523.560953] [tempesta fw] exiting... Apr 26 04:59:33 192.168.122.209 [46523.735939] [tdb] Shutdown Tempesta DB Apr 26 04:59:33 192.168.122.209 [46523.993259] End test: t_health_monitoring.test_health_monitor.TestHmMalformedResponse.test Apr 26 04:59:33 192.168.122.209 [46524.005995] Start test: t_http_rules.test_backup_servers.HttpRulesBackupServers.test_scheduler Apr 26 04:59:34 192.168.122.209 [46525.205129] [tdb] Start Tempesta DB Apr 26 04:59:34 192.168.122.209 [46525.359912] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:59:36 192.168.122.209 [46526.868024] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46526.868024] Maybe that's fine, but it's worth checking the [46526.868024] config - if there is no relations between the [46526.868024] names, then host name confusion attack is possible. Apr 26 04:59:36 192.168.122.209 [46527.050682] [tempesta fw] Configuration processing is completed. Apr 26 04:59:36 192.168.122.209 [46527.128034] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:59:36 192.168.122.209 [46527.167886] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:59:36 192.168.122.209 [46527.204960] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:59:36 192.168.122.209 [46527.258702] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:59:36 192.168.122.209 [46527.260611] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:59:36 192.168.122.209 [46527.302681] [tempesta fw] Tempesta FW is ready Apr 26 04:59:39 192.168.122.209 [46529.973960] [tdb] Close table 'client0.tdb' Apr 26 04:59:39 192.168.122.209 [46530.160829] [tdb] Close table 'sessions0.tdb' Apr 26 04:59:40 192.168.122.209 [46530.411084] [tdb] Close table 'filter0.tdb' Apr 26 04:59:40 192.168.122.209 [46530.411515] [tempesta fw] modules are stopped Apr 26 04:59:40 192.168.122.209 [46530.627549] [tempesta fw] exiting... Apr 26 04:59:40 192.168.122.209 [46530.753320] [tdb] Shutdown Tempesta DB Apr 26 04:59:40 192.168.122.209 [46530.960741] End test: t_http_rules.test_backup_servers.HttpRulesBackupServers.test_scheduler Apr 26 04:59:40 192.168.122.209 [46530.972719] Start test: t_http_rules.test_h2_backup_servers.HttpRulesBackupServersH2.test_scheduler Apr 26 04:59:41 192.168.122.209 [46532.102642] [tdb] Start Tempesta DB Apr 26 04:59:41 192.168.122.209 [46532.245574] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:59:42 192.168.122.209 [46532.991575] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46532.991575] Maybe that's fine, but it's worth checking the [46532.991575] config - if there is no relations between the [46532.991575] names, then host name confusion attack is possible. Apr 26 04:59:42 192.168.122.209 [46533.170845] [tempesta fw] Configuration processing is completed. Apr 26 04:59:42 192.168.122.209 [46533.221516] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:59:42 192.168.122.209 [46533.250645] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 04:59:42 192.168.122.209 [46533.280032] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 04:59:42 192.168.122.209 [46533.346741] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:59:42 192.168.122.209 [46533.347986] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:59:43 192.168.122.209 [46533.406725] [tempesta fw] Tempesta FW is ready Apr 26 04:59:45 192.168.122.209 [46536.018238] [tdb] Close table 'client0.tdb' Apr 26 04:59:45 192.168.122.209 [46536.204125] [tdb] Close table 'sessions0.tdb' Apr 26 04:59:46 192.168.122.209 [46536.439864] [tdb] Close table 'filter0.tdb' Apr 26 04:59:46 192.168.122.209 [46536.440309] [tempesta fw] modules are stopped Apr 26 04:59:46 192.168.122.209 [46536.682894] [tempesta fw] exiting... Apr 26 04:59:46 192.168.122.209 [46536.820517] [tdb] Shutdown Tempesta DB Apr 26 04:59:46 192.168.122.209 [46537.041639] End test: t_http_rules.test_h2_backup_servers.HttpRulesBackupServersH2.test_scheduler Apr 26 04:59:46 192.168.122.209 [46537.051537] Start test: t_http_rules.test_h2_http_rules.HttpRulesH2.test_scheduler Apr 26 04:59:47 192.168.122.209 [46538.149493] [tdb] Start Tempesta DB Apr 26 04:59:47 192.168.122.209 [46538.283375] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 04:59:49 192.168.122.209 [46539.888069] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46539.888069] Maybe that's fine, but it's worth checking the [46539.888069] config - if there is no relations between the [46539.888069] names, then host name confusion attack is possible. Apr 26 04:59:50 192.168.122.209 [46540.502876] [tempesta fw] Configuration processing is completed. Apr 26 04:59:50 192.168.122.209 [46540.555885] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 04:59:50 192.168.122.209 [46541.110073] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 04:59:50 192.168.122.209 [46541.150400] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 04:59:50 192.168.122.209 [46541.185904] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 04:59:51 192.168.122.209 [46541.531743] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 04:59:51 192.168.122.209 [46541.533605] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 04:59:51 192.168.122.209 [46541.574842] [tempesta fw] Tempesta FW is ready Apr 26 04:59:53 192.168.122.209 [46543.747880] [tdb] Close table 'client0.tdb' Apr 26 04:59:53 192.168.122.209 [46543.940650] [tdb] Close table 'sessions0.tdb' Apr 26 04:59:56 192.168.122.209 [46547.035605] [tdb] Close table 'cache0.tdb' Apr 26 04:59:56 192.168.122.209 [46547.282325] [tdb] Close table 'filter0.tdb' Apr 26 04:59:56 192.168.122.209 [46547.282792] [tempesta fw] modules are stopped Apr 26 04:59:57 192.168.122.209 [46547.740322] [tempesta fw] exiting... Apr 26 04:59:57 192.168.122.209 [46547.882100] [tdb] Shutdown Tempesta DB Apr 26 04:59:57 192.168.122.209 [46548.127481] End test: t_http_rules.test_h2_http_rules.HttpRulesH2.test_scheduler Apr 26 04:59:57 192.168.122.209 [46548.149843] Start test: t_http_rules.test_h2_http_rules.TestH2Host.test_different_authority_and_host_headers Apr 26 04:59:58 192.168.122.209 [46549.291337] [tdb] Start Tempesta DB Apr 26 04:59:59 192.168.122.209 [46549.425996] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:00:00 192.168.122.209 [46551.083726] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46551.083726] Maybe that's fine, but it's worth checking the [46551.083726] config - if there is no relations between the [46551.083726] names, then host name confusion attack is possible. Apr 26 05:00:00 192.168.122.209 [46551.315073] [tempesta fw] Configuration processing is completed. Apr 26 05:00:00 192.168.122.209 [46551.365755] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:00:01 192.168.122.209 [46551.780694] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:00:01 192.168.122.209 [46551.806701] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:00:01 192.168.122.209 [46551.832391] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:00:01 192.168.122.209 [46551.915009] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:00:01 192.168.122.209 [46551.916706] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:00:01 192.168.122.209 [46551.954987] [tempesta fw] Tempesta FW is ready Apr 26 05:00:02 192.168.122.209 [46552.801611] [tdb] Close table 'client0.tdb' Apr 26 05:00:02 192.168.122.209 [46552.994329] [tdb] Close table 'sessions0.tdb' Apr 26 05:00:05 192.168.122.209 [46556.158130] [tdb] Close table 'cache0.tdb' Apr 26 05:00:06 192.168.122.209 [46556.404808] [tdb] Close table 'filter0.tdb' Apr 26 05:00:06 192.168.122.209 [46556.405318] [tempesta fw] modules are stopped Apr 26 05:00:06 192.168.122.209 [46556.658465] [tempesta fw] exiting... Apr 26 05:00:06 192.168.122.209 [46556.778385] [tdb] Shutdown Tempesta DB Apr 26 05:00:06 192.168.122.209 [46556.987116] End test: t_http_rules.test_h2_http_rules.TestH2Host.test_different_authority_and_host_headers Apr 26 05:00:06 192.168.122.209 [46557.005202] Start test: t_http_rules.test_h2_http_rules.TestH2Host.test_hdr_host_in_authority_header Apr 26 05:00:07 192.168.122.209 [46558.116024] [tdb] Start Tempesta DB Apr 26 05:00:07 192.168.122.209 [46558.251382] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:00:09 192.168.122.209 [46559.940410] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46559.940410] Maybe that's fine, but it's worth checking the [46559.940410] config - if there is no relations between the [46559.940410] names, then host name confusion attack is possible. Apr 26 05:00:09 192.168.122.209 [46560.163352] [tempesta fw] Configuration processing is completed. Apr 26 05:00:09 192.168.122.209 [46560.214691] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:00:10 192.168.122.209 [46560.621950] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:00:10 192.168.122.209 [46560.678409] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:00:10 192.168.122.209 [46560.704100] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:00:10 192.168.122.209 [46560.811153] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:00:10 192.168.122.209 [46560.812794] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:00:10 192.168.122.209 [46560.851079] [tempesta fw] Tempesta FW is ready Apr 26 05:00:11 192.168.122.209 [46561.592143] [tdb] Close table 'client0.tdb' Apr 26 05:00:11 192.168.122.209 [46561.781285] [tdb] Close table 'sessions0.tdb' Apr 26 05:00:14 192.168.122.209 [46564.935477] [tdb] Close table 'cache0.tdb' Apr 26 05:00:14 192.168.122.209 [46565.195663] [tdb] Close table 'filter0.tdb' Apr 26 05:00:14 192.168.122.209 [46565.196104] [tempesta fw] modules are stopped Apr 26 05:00:15 192.168.122.209 [46565.459277] [tempesta fw] exiting... Apr 26 05:00:15 192.168.122.209 [46565.608795] [tdb] Shutdown Tempesta DB Apr 26 05:00:15 192.168.122.209 [46565.813392] End test: t_http_rules.test_h2_http_rules.TestH2Host.test_hdr_host_in_authority_header Apr 26 05:00:15 192.168.122.209 [46565.840395] Start test: t_http_rules.test_h2_http_rules.TestH2Host.test_hdr_host_in_forwarded_header Apr 26 05:00:16 192.168.122.209 [46566.984230] [tdb] Start Tempesta DB Apr 26 05:00:16 192.168.122.209 [46567.126198] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:00:18 192.168.122.209 [46568.868588] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46568.868588] Maybe that's fine, but it's worth checking the [46568.868588] config - if there is no relations between the [46568.868588] names, then host name confusion attack is possible. Apr 26 05:00:18 192.168.122.209 [46569.091318] [tempesta fw] Configuration processing is completed. Apr 26 05:00:18 192.168.122.209 [46569.142323] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:00:19 192.168.122.209 [46569.582854] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:00:19 192.168.122.209 [46569.609214] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:00:19 192.168.122.209 [46569.635332] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:00:19 192.168.122.209 [46569.727239] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:00:19 192.168.122.209 [46569.728945] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:00:19 192.168.122.209 [46569.771214] [tempesta fw] Tempesta FW is ready Apr 26 05:00:20 192.168.122.209 [46570.537830] [tdb] Close table 'client0.tdb' Apr 26 05:00:20 192.168.122.209 [46570.733189] [tdb] Close table 'sessions0.tdb' Apr 26 05:00:23 192.168.122.209 [46573.918953] [tdb] Close table 'cache0.tdb' Apr 26 05:00:23 192.168.122.209 [46574.166302] [tdb] Close table 'filter0.tdb' Apr 26 05:00:23 192.168.122.209 [46574.166728] [tempesta fw] modules are stopped Apr 26 05:00:24 192.168.122.209 [46574.436907] [tempesta fw] exiting... Apr 26 05:00:24 192.168.122.209 [46574.589608] [tdb] Shutdown Tempesta DB Apr 26 05:00:24 192.168.122.209 [46574.833958] End test: t_http_rules.test_h2_http_rules.TestH2Host.test_hdr_host_in_forwarded_header Apr 26 05:00:24 192.168.122.209 [46574.847846] Start test: t_http_rules.test_h2_http_rules.TestH2Host.test_host_in_authority_header Apr 26 05:00:25 192.168.122.209 [46576.016054] [tdb] Start Tempesta DB Apr 26 05:00:25 192.168.122.209 [46576.163925] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:00:27 192.168.122.209 [46577.844635] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46577.844635] Maybe that's fine, but it's worth checking the [46577.844635] config - if there is no relations between the [46577.844635] names, then host name confusion attack is possible. Apr 26 05:00:27 192.168.122.209 [46578.055428] [tempesta fw] Configuration processing is completed. Apr 26 05:00:27 192.168.122.209 [46578.108132] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:00:28 192.168.122.209 [46578.548674] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:00:28 192.168.122.209 [46578.615091] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:00:28 192.168.122.209 [46578.644987] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:00:28 192.168.122.209 [46578.739371] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:00:28 192.168.122.209 [46578.741037] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:00:28 192.168.122.209 [46578.779339] [tempesta fw] Tempesta FW is ready Apr 26 05:00:29 192.168.122.209 [46579.514683] [tdb] Close table 'client0.tdb' Apr 26 05:00:29 192.168.122.209 [46579.720746] [tdb] Close table 'sessions0.tdb' Apr 26 05:00:32 192.168.122.209 [46582.958936] [tdb] Close table 'cache0.tdb' Apr 26 05:00:32 192.168.122.209 [46583.226197] [tdb] Close table 'filter0.tdb' Apr 26 05:00:32 192.168.122.209 [46583.226665] [tempesta fw] modules are stopped Apr 26 05:00:33 192.168.122.209 [46583.497448] [tempesta fw] exiting... Apr 26 05:00:33 192.168.122.209 [46583.647910] [tdb] Shutdown Tempesta DB Apr 26 05:00:33 192.168.122.209 [46583.911797] End test: t_http_rules.test_h2_http_rules.TestH2Host.test_host_in_authority_header Apr 26 05:00:33 192.168.122.209 [46583.932999] Start test: t_http_rules.test_h2_http_rules.TestH2Host.test_host_in_forwarded_header Apr 26 05:00:34 192.168.122.209 [46585.172484] [tdb] Start Tempesta DB Apr 26 05:00:34 192.168.122.209 [46585.342996] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:00:36 192.168.122.209 [46587.188329] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46587.188329] Maybe that's fine, but it's worth checking the [46587.188329] config - if there is no relations between the [46587.188329] names, then host name confusion attack is possible. Apr 26 05:00:37 192.168.122.209 [46587.403603] [tempesta fw] Configuration processing is completed. Apr 26 05:00:37 192.168.122.209 [46587.474105] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:00:37 192.168.122.209 [46587.950371] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:00:37 192.168.122.209 [46588.011700] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:00:37 192.168.122.209 [46588.041277] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:00:37 192.168.122.209 [46588.135537] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:00:37 192.168.122.209 [46588.137423] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:00:37 192.168.122.209 [46588.175434] [tempesta fw] Tempesta FW is ready Apr 26 05:00:38 192.168.122.209 [46588.950899] [tdb] Close table 'client0.tdb' Apr 26 05:00:38 192.168.122.209 [46589.144358] [tdb] Close table 'sessions0.tdb' Apr 26 05:00:42 192.168.122.209 [46592.446634] [tdb] Close table 'cache0.tdb' Apr 26 05:00:42 192.168.122.209 [46592.668907] [tdb] Close table 'filter0.tdb' Apr 26 05:00:42 192.168.122.209 [46592.669429] [tempesta fw] modules are stopped Apr 26 05:00:42 192.168.122.209 [46592.954934] [tempesta fw] exiting... Apr 26 05:00:42 192.168.122.209 [46593.094951] [tdb] Shutdown Tempesta DB Apr 26 05:00:42 192.168.122.209 [46593.327969] End test: t_http_rules.test_h2_http_rules.TestH2Host.test_host_in_forwarded_header Apr 26 05:00:42 192.168.122.209 [46593.346757] Start test: t_http_rules.test_h2_http_rules.TestH2Host.test_host_in_host_header Apr 26 05:00:44 192.168.122.209 [46594.674167] [tdb] Start Tempesta DB Apr 26 05:00:44 192.168.122.209 [46594.842223] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:00:46 192.168.122.209 [46596.536961] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46596.536961] Maybe that's fine, but it's worth checking the [46596.536961] config - if there is no relations between the [46596.536961] names, then host name confusion attack is possible. Apr 26 05:00:46 192.168.122.209 [46596.775708] [tempesta fw] Configuration processing is completed. Apr 26 05:00:46 192.168.122.209 [46596.830082] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:00:46 192.168.122.209 [46597.300324] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:00:46 192.168.122.209 [46597.326584] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:00:46 192.168.122.209 [46597.352987] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:00:47 192.168.122.209 [46597.431647] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:00:47 192.168.122.209 [46597.433178] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:00:47 192.168.122.209 [46597.471568] [tempesta fw] Tempesta FW is ready Apr 26 05:00:47 192.168.122.209 [46598.236762] [tdb] Close table 'client0.tdb' Apr 26 05:00:48 192.168.122.209 [46598.435011] [tdb] Close table 'sessions0.tdb' Apr 26 05:00:51 192.168.122.209 [46602.037924] [tdb] Close table 'cache0.tdb' Apr 26 05:00:51 192.168.122.209 [46602.330657] [tdb] Close table 'filter0.tdb' Apr 26 05:00:51 192.168.122.209 [46602.331099] [tempesta fw] modules are stopped Apr 26 05:00:52 192.168.122.209 [46602.634704] [tempesta fw] exiting... Apr 26 05:00:52 192.168.122.209 [46602.809005] [tdb] Shutdown Tempesta DB Apr 26 05:00:52 192.168.122.209 [46603.110171] End test: t_http_rules.test_h2_http_rules.TestH2Host.test_host_in_host_header Apr 26 05:00:52 192.168.122.209 [46603.124145] Start test: t_http_rules.test_h2_http_tables.H2Redirects.test Apr 26 05:00:53 192.168.122.209 [46604.344086] [tdb] Start Tempesta DB Apr 26 05:00:54 192.168.122.209 [46604.501026] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:00:55 192.168.122.209 [46606.300846] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [46606.300846] Maybe that's fine, but it's worth checking the [46606.300846] config - if there is no relations between the [46606.300846] names, then host name confusion attack is possible. Apr 26 05:00:55 192.168.122.209 [46606.387767] [tempesta fw] Configuration processing is completed. Apr 26 05:00:56 192.168.122.209 [46606.454920] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:00:56 192.168.122.209 [46607.035870] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:00:56 192.168.122.209 [46607.070979] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:00:56 192.168.122.209 [46607.107302] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:00:56 192.168.122.209 [46607.147690] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:00:56 192.168.122.209 [46607.187684] [tempesta fw] Tempesta FW is ready Apr 26 05:00:57 192.168.122.209 [46607.820480] [tdb] Close table 'client0.tdb' Apr 26 05:00:57 192.168.122.209 [46608.006491] [tdb] Close table 'sessions0.tdb' Apr 26 05:01:00 192.168.122.209 [46611.278528] [tdb] Close table 'cache0.tdb' Apr 26 05:01:01 192.168.122.209 [46611.522516] [tdb] Close table 'filter0.tdb' Apr 26 05:01:01 192.168.122.209 [46611.523162] [tempesta fw] modules are stopped Apr 26 05:01:01 192.168.122.209 [46611.727839] [tempesta fw] exiting... Apr 26 05:01:01 192.168.122.209 [46611.883343] [tdb] Shutdown Tempesta DB Apr 26 05:01:01 192.168.122.209 [46612.096692] End test: t_http_rules.test_h2_http_tables.H2Redirects.test Apr 26 05:01:01 192.168.122.209 [46612.107515] Start test: t_http_rules.test_h2_http_tables.HttpTablesTestCustomRedirectCorrectVariablesAuthorityH2.test Apr 26 05:01:02 192.168.122.209 [46613.280498] [tdb] Start Tempesta DB Apr 26 05:01:03 192.168.122.209 [46613.424208] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:01:04 192.168.122.209 [46615.196180] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46615.196180] Maybe that's fine, but it's worth checking the [46615.196180] config - if there is no relations between the [46615.196180] names, then host name confusion attack is possible. Apr 26 05:01:04 192.168.122.209 [46615.336115] [tempesta fw] Configuration processing is completed. Apr 26 05:01:05 192.168.122.209 [46615.397920] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:01:05 192.168.122.209 [46615.872484] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:01:05 192.168.122.209 [46615.898328] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:01:05 192.168.122.209 [46615.924611] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:01:05 192.168.122.209 [46615.971902] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:01:05 192.168.122.209 [46615.973251] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:01:05 192.168.122.209 [46616.019798] [tempesta fw] Tempesta FW is ready Apr 26 05:01:06 192.168.122.209 [46616.608289] [tdb] Close table 'client0.tdb' Apr 26 05:01:06 192.168.122.209 [46616.821278] [tdb] Close table 'sessions0.tdb' Apr 26 05:01:09 192.168.122.209 [46619.986892] [tdb] Close table 'cache0.tdb' Apr 26 05:01:09 192.168.122.209 [46620.220423] [tdb] Close table 'filter0.tdb' Apr 26 05:01:09 192.168.122.209 [46620.220921] [tempesta fw] modules are stopped Apr 26 05:01:10 192.168.122.209 [46620.457232] [tempesta fw] exiting... Apr 26 05:01:10 192.168.122.209 [46620.604803] [tdb] Shutdown Tempesta DB Apr 26 05:01:10 192.168.122.209 [46620.830873] End test: t_http_rules.test_h2_http_tables.HttpTablesTestCustomRedirectCorrectVariablesAuthorityH2.test Apr 26 05:01:10 192.168.122.209 [46620.841654] Start test: t_http_rules.test_h2_http_tables.HttpTablesTestCustomRedirectCorrectVariablesHostH2.test Apr 26 05:01:11 192.168.122.209 [46622.004092] [tdb] Start Tempesta DB Apr 26 05:01:11 192.168.122.209 [46622.151236] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:01:13 192.168.122.209 [46623.877359] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46623.877359] Maybe that's fine, but it's worth checking the [46623.877359] config - if there is no relations between the [46623.877359] names, then host name confusion attack is possible. Apr 26 05:01:13 192.168.122.209 [46624.043918] [tempesta fw] Configuration processing is completed. Apr 26 05:01:13 192.168.122.209 [46624.098435] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:01:14 192.168.122.209 [46624.555432] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:01:14 192.168.122.209 [46624.614312] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:01:14 192.168.122.209 [46624.642474] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:01:14 192.168.122.209 [46624.679884] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:01:14 192.168.122.209 [46624.680935] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:01:14 192.168.122.209 [46624.719923] [tempesta fw] Tempesta FW is ready Apr 26 05:01:14 192.168.122.209 [46625.280978] [tdb] Close table 'client0.tdb' Apr 26 05:01:15 192.168.122.209 [46625.479180] [tdb] Close table 'sessions0.tdb' Apr 26 05:01:18 192.168.122.209 [46628.749747] [tdb] Close table 'cache0.tdb' Apr 26 05:01:18 192.168.122.209 [46628.990556] [tdb] Close table 'filter0.tdb' Apr 26 05:01:18 192.168.122.209 [46628.991055] [tempesta fw] modules are stopped Apr 26 05:01:18 192.168.122.209 [46629.209203] [tempesta fw] exiting... Apr 26 05:01:19 192.168.122.209 [46629.402513] [tdb] Shutdown Tempesta DB Apr 26 05:01:19 192.168.122.209 [46629.610671] End test: t_http_rules.test_h2_http_tables.HttpTablesTestCustomRedirectCorrectVariablesHostH2.test Apr 26 05:01:19 192.168.122.209 [46629.621095] Start test: t_http_rules.test_h2_http_tables.HttpTablesTestCustomRedirectDifferentResponseStatusH2.test Apr 26 05:01:20 192.168.122.209 [46630.758575] [tdb] Start Tempesta DB Apr 26 05:01:20 192.168.122.209 [46630.917942] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:01:22 192.168.122.209 [46632.776582] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46632.776582] Maybe that's fine, but it's worth checking the [46632.776582] config - if there is no relations between the [46632.776582] names, then host name confusion attack is possible. Apr 26 05:01:22 192.168.122.209 [46632.928065] [tempesta fw] Configuration processing is completed. Apr 26 05:01:22 192.168.122.209 [46632.989526] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:01:23 192.168.122.209 [46633.512786] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:01:23 192.168.122.209 [46633.541379] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:01:23 192.168.122.209 [46633.570325] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:01:23 192.168.122.209 [46633.616060] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:01:23 192.168.122.209 [46633.617462] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:01:23 192.168.122.209 [46633.656035] [tempesta fw] Tempesta FW is ready Apr 26 05:01:23 192.168.122.209 [46634.229543] [tdb] Close table 'client0.tdb' Apr 26 05:01:24 192.168.122.209 [46634.433184] [tdb] Close table 'sessions0.tdb' Apr 26 05:01:27 192.168.122.209 [46637.623505] [tdb] Close table 'cache0.tdb' Apr 26 05:01:27 192.168.122.209 [46637.894058] [tdb] Close table 'filter0.tdb' Apr 26 05:01:27 192.168.122.209 [46637.894497] [tempesta fw] modules are stopped Apr 26 05:01:27 192.168.122.209 [46638.102057] [tempesta fw] exiting... Apr 26 05:01:27 192.168.122.209 [46638.247391] [tdb] Shutdown Tempesta DB Apr 26 05:01:28 192.168.122.209 [46638.454510] End test: t_http_rules.test_h2_http_tables.HttpTablesTestCustomRedirectDifferentResponseStatusH2.test Apr 26 05:01:28 192.168.122.209 [46638.467611] Start test: t_http_rules.test_h2_http_tables.HttpTablesTestCustomRedirectNonExistentVariablesH2.test Apr 26 05:01:29 192.168.122.209 [46639.726825] [tdb] Start Tempesta DB Apr 26 05:01:29 192.168.122.209 [46639.876797] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:01:31 192.168.122.209 [46641.753461] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46641.753461] Maybe that's fine, but it's worth checking the [46641.753461] config - if there is no relations between the [46641.753461] names, then host name confusion attack is possible. Apr 26 05:01:31 192.168.122.209 [46641.908223] [tempesta fw] Configuration processing is completed. Apr 26 05:01:31 192.168.122.209 [46641.963752] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:01:32 192.168.122.209 [46642.422717] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:01:32 192.168.122.209 [46642.449659] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:01:32 192.168.122.209 [46642.476316] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:01:32 192.168.122.209 [46642.560087] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:01:32 192.168.122.209 [46642.561993] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:01:32 192.168.122.209 [46642.600069] [tempesta fw] Tempesta FW is ready Apr 26 05:01:32 192.168.122.209 [46643.224743] [tdb] Close table 'client0.tdb' Apr 26 05:01:33 192.168.122.209 [46643.416950] [tdb] Close table 'sessions0.tdb' Apr 26 05:01:36 192.168.122.209 [46646.602380] [tdb] Close table 'cache0.tdb' Apr 26 05:01:36 192.168.122.209 [46646.833968] [tdb] Close table 'filter0.tdb' Apr 26 05:01:36 192.168.122.209 [46646.834549] [tempesta fw] modules are stopped Apr 26 05:01:36 192.168.122.209 [46647.085076] [tempesta fw] exiting... Apr 26 05:01:36 192.168.122.209 [46647.233100] [tdb] Shutdown Tempesta DB Apr 26 05:01:37 192.168.122.209 [46647.469544] End test: t_http_rules.test_h2_http_tables.HttpTablesTestCustomRedirectNonExistentVariablesH2.test Apr 26 05:01:37 192.168.122.209 [46647.480217] Start test: t_http_rules.test_h2_http_tables.HttpTablesTestEmptyChainDefaultH2.test Apr 26 05:01:38 192.168.122.209 [46648.690529] [tdb] Start Tempesta DB Apr 26 05:01:38 192.168.122.209 [46648.851016] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:01:40 192.168.122.209 [46650.629776] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46650.629776] Maybe that's fine, but it's worth checking the [46650.629776] config - if there is no relations between the [46650.629776] names, then host name confusion attack is possible. Apr 26 05:01:40 192.168.122.209 [46650.776236] [tempesta fw] Configuration processing is completed. Apr 26 05:01:40 192.168.122.209 [46650.836782] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:01:40 192.168.122.209 [46651.308985] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:01:40 192.168.122.209 [46651.337149] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:01:40 192.168.122.209 [46651.365516] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:01:41 192.168.122.209 [46651.412307] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:01:41 192.168.122.209 [46651.414075] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:01:41 192.168.122.209 [46651.448228] [tempesta fw] Tempesta FW is ready Apr 26 05:01:41 192.168.122.209 [46651.612872] [tempesta fw] Warning: request dropped: cannot find appropriate virtual host, status 403: 127.0.0.2 Apr 26 05:01:41 192.168.122.209 [46652.051899] [tdb] Close table 'client0.tdb' Apr 26 05:01:41 192.168.122.209 [46652.244185] [tdb] Close table 'sessions0.tdb' Apr 26 05:01:45 192.168.122.209 [46655.482652] [tdb] Close table 'cache0.tdb' Apr 26 05:01:45 192.168.122.209 [46655.742054] [tdb] Close table 'filter0.tdb' Apr 26 05:01:45 192.168.122.209 [46655.742534] [tempesta fw] modules are stopped Apr 26 05:01:45 192.168.122.209 [46655.999027] [tempesta fw] exiting... Apr 26 05:01:45 192.168.122.209 [46656.161111] [tdb] Shutdown Tempesta DB Apr 26 05:01:46 192.168.122.209 [46656.398057] End test: t_http_rules.test_h2_http_tables.HttpTablesTestEmptyChainDefaultH2.test Apr 26 05:01:46 192.168.122.209 [46656.409926] Start test: t_http_rules.test_h2_http_tables.HttpTablesTestEmptyChainDropH2.test Apr 26 05:01:47 192.168.122.209 [46657.547425] [tdb] Start Tempesta DB Apr 26 05:01:47 192.168.122.209 [46657.689961] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:01:49 192.168.122.209 [46659.421706] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46659.421706] Maybe that's fine, but it's worth checking the [46659.421706] config - if there is no relations between the [46659.421706] names, then host name confusion attack is possible. Apr 26 05:01:49 192.168.122.209 [46659.588326] [tempesta fw] Configuration processing is completed. Apr 26 05:01:49 192.168.122.209 [46659.643515] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:01:49 192.168.122.209 [46660.158063] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:01:49 192.168.122.209 [46660.223095] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:01:49 192.168.122.209 [46660.256954] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:01:49 192.168.122.209 [46660.324411] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:01:49 192.168.122.209 [46660.325851] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:01:49 192.168.122.209 [46660.364369] [tempesta fw] Tempesta FW is ready Apr 26 05:01:50 192.168.122.209 [46660.518160] [tempesta fw] Warning: request dropped: cannot find appropriate virtual host, status 403: 127.0.0.2 Apr 26 05:01:50 192.168.122.209 [46660.988036] [tdb] Close table 'client0.tdb' Apr 26 05:01:50 192.168.122.209 [46661.162510] [tdb] Close table 'sessions0.tdb' Apr 26 05:01:53 192.168.122.209 [46664.385877] [tdb] Close table 'cache0.tdb' Apr 26 05:01:54 192.168.122.209 [46664.643095] [tdb] Close table 'filter0.tdb' Apr 26 05:01:54 192.168.122.209 [46664.643552] [tempesta fw] modules are stopped Apr 26 05:01:54 192.168.122.209 [46664.829877] [tempesta fw] exiting... Apr 26 05:01:54 192.168.122.209 [46664.966989] [tdb] Shutdown Tempesta DB Apr 26 05:01:54 192.168.122.209 [46665.217347] End test: t_http_rules.test_h2_http_tables.HttpTablesTestEmptyChainDropH2.test Apr 26 05:01:54 192.168.122.209 [46665.235213] Start test: t_http_rules.test_h2_http_tables.HttpTablesTestEmptyChainReplyH2.test Apr 26 05:01:56 192.168.122.209 [46666.448944] [tdb] Start Tempesta DB Apr 26 05:01:56 192.168.122.209 [46666.586363] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:01:57 192.168.122.209 [46668.337537] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46668.337537] Maybe that's fine, but it's worth checking the [46668.337537] config - if there is no relations between the [46668.337537] names, then host name confusion attack is possible. Apr 26 05:01:58 192.168.122.209 [46668.484746] [tempesta fw] Configuration processing is completed. Apr 26 05:01:58 192.168.122.209 [46668.541267] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:01:58 192.168.122.209 [46668.995300] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:01:58 192.168.122.209 [46669.021473] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:01:58 192.168.122.209 [46669.055731] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:01:58 192.168.122.209 [46669.104486] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:01:58 192.168.122.209 [46669.105885] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:01:58 192.168.122.209 [46669.156462] [tempesta fw] Tempesta FW is ready Apr 26 05:01:58 192.168.122.209 [46669.303585] [tempesta fw] Warning: request dropped: cannot find appropriate virtual host, status 403: 127.0.0.2 Apr 26 05:01:59 192.168.122.209 [46669.692322] [tdb] Close table 'client0.tdb' Apr 26 05:01:59 192.168.122.209 [46669.901305] [tdb] Close table 'sessions0.tdb' Apr 26 05:02:02 192.168.122.209 [46673.125127] [tdb] Close table 'cache0.tdb' Apr 26 05:02:02 192.168.122.209 [46673.369790] [tdb] Close table 'filter0.tdb' Apr 26 05:02:02 192.168.122.209 [46673.370230] [tempesta fw] modules are stopped Apr 26 05:02:03 192.168.122.209 [46673.569033] [tempesta fw] exiting... Apr 26 05:02:03 192.168.122.209 [46673.705073] [tdb] Shutdown Tempesta DB Apr 26 05:02:03 192.168.122.209 [46673.943121] End test: t_http_rules.test_h2_http_tables.HttpTablesTestEmptyChainReplyH2.test Apr 26 05:02:03 192.168.122.209 [46673.959444] Start test: t_http_rules.test_h2_http_tables.HttpTablesTestEmptyMainChainDefaultH2.test Apr 26 05:02:04 192.168.122.209 [46675.161964] [tdb] Start Tempesta DB Apr 26 05:02:04 192.168.122.209 [46675.312531] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:02:06 192.168.122.209 [46676.957965] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46676.957965] Maybe that's fine, but it's worth checking the [46676.957965] config - if there is no relations between the [46676.957965] names, then host name confusion attack is possible. Apr 26 05:02:06 192.168.122.209 [46677.092612] [tempesta fw] Configuration processing is completed. Apr 26 05:02:06 192.168.122.209 [46677.146771] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:02:07 192.168.122.209 [46677.667596] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:02:07 192.168.122.209 [46677.740676] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:02:07 192.168.122.209 [46677.768315] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:02:07 192.168.122.209 [46677.808585] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:02:07 192.168.122.209 [46677.809730] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:02:07 192.168.122.209 [46677.860584] [tempesta fw] Tempesta FW is ready Apr 26 05:02:07 192.168.122.209 [46678.001446] [tempesta fw] Warning: request dropped: cannot find appropriate virtual host, status 403: 127.0.0.2 Apr 26 05:02:08 192.168.122.209 [46678.433902] [tdb] Close table 'client0.tdb' Apr 26 05:02:08 192.168.122.209 [46678.641261] [tdb] Close table 'sessions0.tdb' Apr 26 05:02:11 192.168.122.209 [46681.923711] [tdb] Close table 'cache0.tdb' Apr 26 05:02:11 192.168.122.209 [46682.155838] [tdb] Close table 'filter0.tdb' Apr 26 05:02:11 192.168.122.209 [46682.156323] [tempesta fw] modules are stopped Apr 26 05:02:11 192.168.122.209 [46682.374812] [tempesta fw] exiting... Apr 26 05:02:12 192.168.122.209 [46682.540238] [tdb] Shutdown Tempesta DB Apr 26 05:02:12 192.168.122.209 [46682.752374] End test: t_http_rules.test_h2_http_tables.HttpTablesTestEmptyMainChainDefaultH2.test Apr 26 05:02:12 192.168.122.209 [46682.773120] Start test: t_http_rules.test_h2_http_tables.HttpTablesTestEmptyMainChainDropH2.test Apr 26 05:02:13 192.168.122.209 [46683.952817] [tdb] Start Tempesta DB Apr 26 05:02:13 192.168.122.209 [46684.102911] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:02:15 192.168.122.209 [46685.758079] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46685.758079] Maybe that's fine, but it's worth checking the [46685.758079] config - if there is no relations between the [46685.758079] names, then host name confusion attack is possible. Apr 26 05:02:15 192.168.122.209 [46685.900703] [tempesta fw] Configuration processing is completed. Apr 26 05:02:15 192.168.122.209 [46685.964060] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:02:16 192.168.122.209 [46686.430193] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:02:16 192.168.122.209 [46686.486772] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:02:16 192.168.122.209 [46686.511968] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:02:16 192.168.122.209 [46686.556664] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:02:16 192.168.122.209 [46686.557716] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:02:16 192.168.122.209 [46686.596702] [tempesta fw] Tempesta FW is ready Apr 26 05:02:16 192.168.122.209 [46686.739240] [tempesta fw] Warning: request dropped: cannot find appropriate virtual host, status 403: 127.0.0.2 Apr 26 05:02:16 192.168.122.209 [46687.166161] [tdb] Close table 'client0.tdb' Apr 26 05:02:16 192.168.122.209 [46687.351513] [tdb] Close table 'sessions0.tdb' Apr 26 05:02:20 192.168.122.209 [46690.542631] [tdb] Close table 'cache0.tdb' Apr 26 05:02:20 192.168.122.209 [46690.791109] [tdb] Close table 'filter0.tdb' Apr 26 05:02:20 192.168.122.209 [46690.791560] [tempesta fw] modules are stopped Apr 26 05:02:20 192.168.122.209 [46690.997570] [tempesta fw] exiting... Apr 26 05:02:20 192.168.122.209 [46691.114307] [tdb] Shutdown Tempesta DB Apr 26 05:02:20 192.168.122.209 [46691.356254] End test: t_http_rules.test_h2_http_tables.HttpTablesTestEmptyMainChainDropH2.test Apr 26 05:02:20 192.168.122.209 [46691.367264] Start test: t_http_rules.test_h2_http_tables.HttpTablesTestEmptyMainChainReplyH2.test Apr 26 05:02:22 192.168.122.209 [46692.468262] [tdb] Start Tempesta DB Apr 26 05:02:22 192.168.122.209 [46692.615204] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:02:23 192.168.122.209 [46694.310086] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46694.310086] Maybe that's fine, but it's worth checking the [46694.310086] config - if there is no relations between the [46694.310086] names, then host name confusion attack is possible. Apr 26 05:02:24 192.168.122.209 [46694.425015] [tempesta fw] Configuration processing is completed. Apr 26 05:02:24 192.168.122.209 [46694.481777] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:02:24 192.168.122.209 [46695.005317] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:02:24 192.168.122.209 [46695.039517] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:02:24 192.168.122.209 [46695.083892] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:02:24 192.168.122.209 [46695.144836] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:02:24 192.168.122.209 [46695.146646] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:02:24 192.168.122.209 [46695.184793] [tempesta fw] Tempesta FW is ready Apr 26 05:02:24 192.168.122.209 [46695.347029] [tempesta fw] Warning: request dropped: cannot find appropriate virtual host, status 403: 127.0.0.2 Apr 26 05:02:25 192.168.122.209 [46695.800427] [tdb] Close table 'client0.tdb' Apr 26 05:02:25 192.168.122.209 [46695.991745] [tdb] Close table 'sessions0.tdb' Apr 26 05:02:28 192.168.122.209 [46699.216800] [tdb] Close table 'cache0.tdb' Apr 26 05:02:29 192.168.122.209 [46699.461868] [tdb] Close table 'filter0.tdb' Apr 26 05:02:29 192.168.122.209 [46699.462395] [tempesta fw] modules are stopped Apr 26 05:02:29 192.168.122.209 [46699.693774] [tempesta fw] exiting... Apr 26 05:02:29 192.168.122.209 [46699.880454] [tdb] Shutdown Tempesta DB Apr 26 05:02:29 192.168.122.209 [46700.108648] End test: t_http_rules.test_h2_http_tables.HttpTablesTestEmptyMainChainReplyH2.test Apr 26 05:02:29 192.168.122.209 [46700.120380] Start test: t_http_rules.test_h2_http_tables.HttpTablesTestMarkRuleH2.test_reject_by_mark_disable_tso_gro_gso Apr 26 05:02:30 192.168.122.209 [46701.350078] [tdb] Start Tempesta DB Apr 26 05:02:31 192.168.122.209 [46701.503465] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:02:32 192.168.122.209 [46703.229587] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46703.229587] Maybe that's fine, but it's worth checking the [46703.229587] config - if there is no relations between the [46703.229587] names, then host name confusion attack is possible. Apr 26 05:02:32 192.168.122.209 [46703.376918] [tempesta fw] Configuration processing is completed. Apr 26 05:02:33 192.168.122.209 [46703.433110] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:02:33 192.168.122.209 [46703.890587] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:02:33 192.168.122.209 [46703.958875] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:02:33 192.168.122.209 [46703.986497] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:02:33 192.168.122.209 [46704.032903] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:02:33 192.168.122.209 [46704.034005] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:02:33 192.168.122.209 [46704.088909] [tempesta fw] Tempesta FW is ready Apr 26 05:02:37 192.168.122.209 [46708.109372] [tdb] Close table 'client0.tdb' Apr 26 05:02:37 192.168.122.209 [46708.301104] [tdb] Close table 'sessions0.tdb' Apr 26 05:02:41 192.168.122.209 [46711.534318] [tdb] Close table 'cache0.tdb' Apr 26 05:02:41 192.168.122.209 [46711.789808] [tdb] Close table 'filter0.tdb' Apr 26 05:02:41 192.168.122.209 [46711.790253] [tempesta fw] modules are stopped Apr 26 05:02:41 192.168.122.209 [46711.971264] [tempesta fw] exiting... Apr 26 05:02:41 192.168.122.209 [46712.111457] [tdb] Shutdown Tempesta DB Apr 26 05:02:41 192.168.122.209 [46712.304659] End test: t_http_rules.test_h2_http_tables.HttpTablesTestMarkRuleH2.test_reject_by_mark_disable_tso_gro_gso Apr 26 05:02:41 192.168.122.209 [46712.321293] Start test: t_http_rules.test_h2_http_tables.HttpTablesTestMarkRuleH2.test_reject_by_mark_enable_tso_gro_gso Apr 26 05:02:43 192.168.122.209 [46713.518017] [tdb] Start Tempesta DB Apr 26 05:02:43 192.168.122.209 [46713.664293] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:02:44 192.168.122.209 [46715.378439] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46715.378439] Maybe that's fine, but it's worth checking the [46715.378439] config - if there is no relations between the [46715.378439] names, then host name confusion attack is possible. Apr 26 05:02:45 192.168.122.209 [46715.525187] [tempesta fw] Configuration processing is completed. Apr 26 05:02:45 192.168.122.209 [46715.592624] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:02:45 192.168.122.209 [46716.117212] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:02:45 192.168.122.209 [46716.151973] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:02:45 192.168.122.209 [46716.196352] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:02:45 192.168.122.209 [46716.237078] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:02:45 192.168.122.209 [46716.238499] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:02:45 192.168.122.209 [46716.281051] [tempesta fw] Tempesta FW is ready Apr 26 05:02:49 192.168.122.209 [46720.280110] [tdb] Close table 'client0.tdb' Apr 26 05:02:50 192.168.122.209 [46720.465047] [tdb] Close table 'sessions0.tdb' Apr 26 05:02:53 192.168.122.209 [46723.723039] [tdb] Close table 'cache0.tdb' Apr 26 05:02:53 192.168.122.209 [46723.975733] [tdb] Close table 'filter0.tdb' Apr 26 05:02:53 192.168.122.209 [46723.976183] [tempesta fw] modules are stopped Apr 26 05:02:53 192.168.122.209 [46724.187150] [tempesta fw] exiting... Apr 26 05:02:53 192.168.122.209 [46724.330369] [tdb] Shutdown Tempesta DB Apr 26 05:02:54 192.168.122.209 [46724.549504] End test: t_http_rules.test_h2_http_tables.HttpTablesTestMarkRuleH2.test_reject_by_mark_enable_tso_gro_gso Apr 26 05:02:54 192.168.122.209 [46724.563175] Start test: t_http_rules.test_h2_http_tables.HttpTablesTestMarkRulesH2.test_chains Apr 26 05:02:55 192.168.122.209 [46725.770075] [tdb] Start Tempesta DB Apr 26 05:02:55 192.168.122.209 [46725.930000] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:02:58 192.168.122.209 [46729.190307] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46729.190307] Maybe that's fine, but it's worth checking the [46729.190307] config - if there is no relations between the [46729.190307] names, then host name confusion attack is possible. Apr 26 05:02:59 192.168.122.209 [46729.649413] [tempesta fw] Configuration processing is completed. Apr 26 05:02:59 192.168.122.209 [46729.706767] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:02:59 192.168.122.209 [46730.261552] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:02:59 192.168.122.209 [46730.328155] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:02:59 192.168.122.209 [46730.361947] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:03:00 192.168.122.209 [46730.541312] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:03:00 192.168.122.209 [46730.543212] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:03:00 192.168.122.209 [46730.581245] [tempesta fw] Tempesta FW is ready Apr 26 05:03:02 192.168.122.209 [46732.416479] [tdb] Close table 'client0.tdb' Apr 26 05:03:02 192.168.122.209 [46732.606860] [tdb] Close table 'sessions0.tdb' Apr 26 05:03:05 192.168.122.209 [46735.921975] [tdb] Close table 'cache0.tdb' Apr 26 05:03:05 192.168.122.209 [46736.197625] [tdb] Close table 'filter0.tdb' Apr 26 05:03:05 192.168.122.209 [46736.198075] [tempesta fw] modules are stopped Apr 26 05:03:06 192.168.122.209 [46736.514471] [tempesta fw] exiting... Apr 26 05:03:06 192.168.122.209 [46736.665896] [tdb] Shutdown Tempesta DB Apr 26 05:03:06 192.168.122.209 [46736.900504] End test: t_http_rules.test_h2_http_tables.HttpTablesTestMarkRulesH2.test_chains Apr 26 05:03:06 192.168.122.209 [46736.915859] Start test: t_http_rules.test_h2_http_tables.HttpTablesTestMixedChainDefaultH2.test Apr 26 05:03:07 192.168.122.209 [46738.058401] [tdb] Start Tempesta DB Apr 26 05:03:07 192.168.122.209 [46738.208115] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:03:09 192.168.122.209 [46739.942829] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46739.942829] Maybe that's fine, but it's worth checking the [46739.942829] config - if there is no relations between the [46739.942829] names, then host name confusion attack is possible. Apr 26 05:03:09 192.168.122.209 [46740.105319] [tempesta fw] Configuration processing is completed. Apr 26 05:03:09 192.168.122.209 [46740.161803] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:03:10 192.168.122.209 [46740.679492] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:03:10 192.168.122.209 [46740.740513] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:03:10 192.168.122.209 [46740.770746] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:03:10 192.168.122.209 [46740.809391] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:03:10 192.168.122.209 [46740.810521] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:03:10 192.168.122.209 [46740.853375] [tempesta fw] Tempesta FW is ready Apr 26 05:03:10 192.168.122.209 [46741.016658] [tempesta fw] Warning: request dropped: cannot find appropriate virtual host, status 403: 127.0.0.2 Apr 26 05:03:11 192.168.122.209 [46741.455701] [tdb] Close table 'client0.tdb' Apr 26 05:03:11 192.168.122.209 [46741.654412] [tdb] Close table 'sessions0.tdb' Apr 26 05:03:14 192.168.122.209 [46744.964928] [tdb] Close table 'cache0.tdb' Apr 26 05:03:14 192.168.122.209 [46745.221710] [tdb] Close table 'filter0.tdb' Apr 26 05:03:14 192.168.122.209 [46745.222212] [tempesta fw] modules are stopped Apr 26 05:03:15 192.168.122.209 [46745.468265] [tempesta fw] exiting... Apr 26 05:03:15 192.168.122.209 [46745.619178] [tdb] Shutdown Tempesta DB Apr 26 05:03:15 192.168.122.209 [46745.841318] End test: t_http_rules.test_h2_http_tables.HttpTablesTestMixedChainDefaultH2.test Apr 26 05:03:15 192.168.122.209 [46745.851261] Start test: t_http_rules.test_h2_http_tables.HttpTablesTestMixedChainDropH2.test Apr 26 05:03:16 192.168.122.209 [46747.037627] [tdb] Start Tempesta DB Apr 26 05:03:16 192.168.122.209 [46747.192353] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:03:18 192.168.122.209 [46749.066543] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46749.066543] Maybe that's fine, but it's worth checking the [46749.066543] config - if there is no relations between the [46749.066543] names, then host name confusion attack is possible. Apr 26 05:03:18 192.168.122.209 [46749.209539] [tempesta fw] Configuration processing is completed. Apr 26 05:03:18 192.168.122.209 [46749.263505] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:03:19 192.168.122.209 [46749.811653] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:03:19 192.168.122.209 [46749.847601] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:03:19 192.168.122.209 [46749.883745] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:03:19 192.168.122.209 [46749.933480] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:03:19 192.168.122.209 [46749.934681] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:03:19 192.168.122.209 [46749.973487] [tempesta fw] Tempesta FW is ready Apr 26 05:03:19 192.168.122.209 [46750.121193] [tempesta fw] Warning: request dropped: cannot find appropriate virtual host, status 403: 127.0.0.2 Apr 26 05:03:20 192.168.122.209 [46750.561002] [tdb] Close table 'client0.tdb' Apr 26 05:03:20 192.168.122.209 [46750.750774] [tdb] Close table 'sessions0.tdb' Apr 26 05:03:23 192.168.122.209 [46754.293634] [tdb] Close table 'cache0.tdb' Apr 26 05:03:24 192.168.122.209 [46754.571227] [tdb] Close table 'filter0.tdb' Apr 26 05:03:24 192.168.122.209 [46754.571675] [tempesta fw] modules are stopped Apr 26 05:03:24 192.168.122.209 [46754.797265] [tempesta fw] exiting... Apr 26 05:03:24 192.168.122.209 [46754.935805] [tdb] Shutdown Tempesta DB Apr 26 05:03:24 192.168.122.209 [46755.124860] End test: t_http_rules.test_h2_http_tables.HttpTablesTestMixedChainDropH2.test Apr 26 05:03:24 192.168.122.209 [46755.137843] Start test: t_http_rules.test_h2_http_tables.HttpTablesTestMixedChainReplyH2.test Apr 26 05:03:25 192.168.122.209 [46756.324664] [tdb] Start Tempesta DB Apr 26 05:03:26 192.168.122.209 [46756.480390] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:03:28 192.168.122.209 [46758.410889] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46758.410889] Maybe that's fine, but it's worth checking the [46758.410889] config - if there is no relations between the [46758.410889] names, then host name confusion attack is possible. Apr 26 05:03:28 192.168.122.209 [46758.573575] [tempesta fw] Configuration processing is completed. Apr 26 05:03:28 192.168.122.209 [46758.633615] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:03:28 192.168.122.209 [46759.148823] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:03:28 192.168.122.209 [46759.176854] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:03:28 192.168.122.209 [46759.205505] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:03:28 192.168.122.209 [46759.249607] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:03:28 192.168.122.209 [46759.250854] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:03:28 192.168.122.209 [46759.301595] [tempesta fw] Tempesta FW is ready Apr 26 05:03:29 192.168.122.209 [46759.440347] [tempesta fw] Warning: request dropped: cannot find appropriate virtual host, status 403: 127.0.0.2 Apr 26 05:03:29 192.168.122.209 [46759.845997] [tdb] Close table 'client0.tdb' Apr 26 05:03:29 192.168.122.209 [46760.035208] [tdb] Close table 'sessions0.tdb' Apr 26 05:03:32 192.168.122.209 [46763.170225] [tdb] Close table 'cache0.tdb' Apr 26 05:03:33 192.168.122.209 [46763.410224] [tdb] Close table 'filter0.tdb' Apr 26 05:03:33 192.168.122.209 [46763.410664] [tempesta fw] modules are stopped Apr 26 05:03:33 192.168.122.209 [46763.633486] [tempesta fw] exiting... Apr 26 05:03:33 192.168.122.209 [46763.788591] [tdb] Shutdown Tempesta DB Apr 26 05:03:33 192.168.122.209 [46763.961539] End test: t_http_rules.test_h2_http_tables.HttpTablesTestMixedChainReplyH2.test Apr 26 05:03:33 192.168.122.209 [46763.978559] Start test: t_http_rules.test_h2_http_tables.HttpTablesTestMixedChainRespH2.test Apr 26 05:03:34 192.168.122.209 [46765.097117] [tdb] Start Tempesta DB Apr 26 05:03:34 192.168.122.209 [46765.237807] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:03:36 192.168.122.209 [46766.930310] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46766.930310] Maybe that's fine, but it's worth checking the [46766.930310] config - if there is no relations between the [46766.930310] names, then host name confusion attack is possible. Apr 26 05:03:36 192.168.122.209 [46767.073747] [tempesta fw] Configuration processing is completed. Apr 26 05:03:36 192.168.122.209 [46767.141675] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:03:37 192.168.122.209 [46767.547160] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:03:37 192.168.122.209 [46767.579403] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:03:37 192.168.122.209 [46767.604869] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:03:37 192.168.122.209 [46767.657624] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:03:37 192.168.122.209 [46767.658428] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:03:37 192.168.122.209 [46767.697643] [tempesta fw] Tempesta FW is ready Apr 26 05:03:37 192.168.122.209 [46768.246624] [tdb] Close table 'client0.tdb' Apr 26 05:03:38 192.168.122.209 [46768.463393] [tdb] Close table 'sessions0.tdb' Apr 26 05:03:41 192.168.122.209 [46771.586723] [tdb] Close table 'cache0.tdb' Apr 26 05:03:41 192.168.122.209 [46771.820507] [tdb] Close table 'filter0.tdb' Apr 26 05:03:41 192.168.122.209 [46771.820939] [tempesta fw] modules are stopped Apr 26 05:03:41 192.168.122.209 [46772.048484] [tempesta fw] exiting... Apr 26 05:03:41 192.168.122.209 [46772.193156] [tdb] Shutdown Tempesta DB Apr 26 05:03:41 192.168.122.209 [46772.383781] End test: t_http_rules.test_h2_http_tables.HttpTablesTestMixedChainRespH2.test Apr 26 05:03:41 192.168.122.209 [46772.393596] Start test: t_http_rules.test_h2_http_tables.TestHttpTablesH2.test_chains Apr 26 05:03:43 192.168.122.209 [46773.496922] [tdb] Start Tempesta DB Apr 26 05:03:43 192.168.122.209 [46773.645734] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:03:46 192.168.122.209 [46776.842842] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46776.842842] Maybe that's fine, but it's worth checking the [46776.842842] config - if there is no relations between the [46776.842842] names, then host name confusion attack is possible. Apr 26 05:03:46 192.168.122.209 [46777.281972] [tempesta fw] Configuration processing is completed. Apr 26 05:03:46 192.168.122.209 [46777.332973] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:03:47 192.168.122.209 [46777.748532] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:03:47 192.168.122.209 [46777.821607] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:03:47 192.168.122.209 [46777.849517] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:03:47 192.168.122.209 [46778.033890] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:03:47 192.168.122.209 [46778.035718] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:03:47 192.168.122.209 [46778.073843] [tempesta fw] Tempesta FW is ready Apr 26 05:03:47 192.168.122.209 [46778.297893] [tempesta fw] Warning: request has been filtered out via http table: 127.0.0.2 Apr 26 05:03:47 192.168.122.209 [46778.310933] [tempesta fw] Warning: request has been filtered out via http table: 127.0.0.2 Apr 26 05:03:48 192.168.122.209 [46779.343210] [tdb] Close table 'client0.tdb' Apr 26 05:03:49 192.168.122.209 [46779.529297] [tdb] Close table 'sessions0.tdb' Apr 26 05:03:52 192.168.122.209 [46782.679464] [tdb] Close table 'cache0.tdb' Apr 26 05:03:52 192.168.122.209 [46782.920777] [tdb] Close table 'filter0.tdb' Apr 26 05:03:52 192.168.122.209 [46782.921215] [tempesta fw] modules are stopped Apr 26 05:03:52 192.168.122.209 [46783.303320] [tempesta fw] exiting... Apr 26 05:03:53 192.168.122.209 [46783.463621] [tdb] Shutdown Tempesta DB Apr 26 05:03:53 192.168.122.209 [46783.664228] End test: t_http_rules.test_h2_http_tables.TestHttpTablesH2.test_chains Apr 26 05:03:53 192.168.122.209 [46783.681913] Start test: t_http_rules.test_h2_match_duplicated_headers.DuplicatedHeadersMatchH2Test.test_match_fail Apr 26 05:03:54 192.168.122.209 [46784.920846] [tdb] Start Tempesta DB Apr 26 05:03:54 192.168.122.209 [46785.075646] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:03:56 192.168.122.209 [46786.687254] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46786.687254] Maybe that's fine, but it's worth checking the [46786.687254] config - if there is no relations between the [46786.687254] names, then host name confusion attack is possible. Apr 26 05:03:56 192.168.122.209 [46786.862026] [tempesta fw] Configuration processing is completed. Apr 26 05:03:56 192.168.122.209 [46786.914150] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:03:56 192.168.122.209 [46787.327673] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:03:56 192.168.122.209 [46787.354741] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:03:56 192.168.122.209 [46787.380478] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:03:57 192.168.122.209 [46787.429998] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:03:57 192.168.122.209 [46787.431630] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:03:57 192.168.122.209 [46787.478042] [tempesta fw] Tempesta FW is ready Apr 26 05:03:57 192.168.122.209 [46787.624508] [tempesta fw] Warning: request has been filtered out via http table: 127.0.0.2 Apr 26 05:03:57 192.168.122.209 [46788.054730] [tdb] Close table 'client0.tdb' Apr 26 05:03:57 192.168.122.209 [46788.243322] [tdb] Close table 'sessions0.tdb' Apr 26 05:04:01 192.168.122.209 [46791.421215] [tdb] Close table 'cache0.tdb' Apr 26 05:04:01 192.168.122.209 [46791.647126] [tdb] Close table 'filter0.tdb' Apr 26 05:04:01 192.168.122.209 [46791.647609] [tempesta fw] modules are stopped Apr 26 05:04:01 192.168.122.209 [46791.854859] [tempesta fw] exiting... Apr 26 05:04:01 192.168.122.209 [46792.025151] [tdb] Shutdown Tempesta DB Apr 26 05:04:01 192.168.122.209 [46792.263688] End test: t_http_rules.test_h2_match_duplicated_headers.DuplicatedHeadersMatchH2Test.test_match_fail Apr 26 05:04:01 192.168.122.209 [46792.270670] Start test: t_http_rules.test_h2_match_duplicated_headers.DuplicatedHeadersMatchH2Test.test_match_success Apr 26 05:04:02 192.168.122.209 [46793.376052] [tdb] Start Tempesta DB Apr 26 05:04:03 192.168.122.209 [46793.516956] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:04:04 192.168.122.209 [46795.071481] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46795.071481] Maybe that's fine, but it's worth checking the [46795.071481] config - if there is no relations between the [46795.071481] names, then host name confusion attack is possible. Apr 26 05:04:04 192.168.122.209 [46795.242176] [tempesta fw] Configuration processing is completed. Apr 26 05:04:04 192.168.122.209 [46795.292604] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:04:05 192.168.122.209 [46795.701725] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:04:05 192.168.122.209 [46795.765408] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:04:05 192.168.122.209 [46795.797085] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:04:05 192.168.122.209 [46795.834023] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:04:05 192.168.122.209 [46795.835052] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:04:05 192.168.122.209 [46795.874050] [tempesta fw] Tempesta FW is ready Apr 26 05:04:06 192.168.122.209 [46796.473935] [tdb] Close table 'client0.tdb' Apr 26 05:04:06 192.168.122.209 [46796.666525] [tdb] Close table 'sessions0.tdb' Apr 26 05:04:09 192.168.122.209 [46799.850638] [tdb] Close table 'cache0.tdb' Apr 26 05:04:09 192.168.122.209 [46800.098195] [tdb] Close table 'filter0.tdb' Apr 26 05:04:09 192.168.122.209 [46800.098629] [tempesta fw] modules are stopped Apr 26 05:04:09 192.168.122.209 [46800.329246] [tempesta fw] exiting... Apr 26 05:04:10 192.168.122.209 [46800.461908] [tdb] Shutdown Tempesta DB Apr 26 05:04:10 192.168.122.209 [46800.673816] End test: t_http_rules.test_h2_match_duplicated_headers.DuplicatedHeadersMatchH2Test.test_match_success Apr 26 05:04:10 192.168.122.209 [46800.688144] Start test: t_http_rules.test_http_rules.TestHost.test_different_host_in_uri_and_host_header Apr 26 05:04:11 192.168.122.209 [46801.776905] [tdb] Start Tempesta DB Apr 26 05:04:11 192.168.122.209 [46801.919059] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:04:13 192.168.122.209 [46803.530903] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46803.530903] Maybe that's fine, but it's worth checking the [46803.530903] config - if there is no relations between the [46803.530903] names, then host name confusion attack is possible. Apr 26 05:04:13 192.168.122.209 [46803.750396] [tempesta fw] Configuration processing is completed. Apr 26 05:04:13 192.168.122.209 [46803.801956] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:04:13 192.168.122.209 [46804.232668] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:04:13 192.168.122.209 [46804.259924] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:04:13 192.168.122.209 [46804.294263] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:04:13 192.168.122.209 [46804.378215] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:04:13 192.168.122.209 [46804.379699] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:04:14 192.168.122.209 [46804.418187] [tempesta fw] Tempesta FW is ready Apr 26 05:04:14 192.168.122.209 [46805.160100] [tdb] Close table 'client0.tdb' Apr 26 05:04:14 192.168.122.209 [46805.346838] [tdb] Close table 'sessions0.tdb' Apr 26 05:04:18 192.168.122.209 [46808.573543] [tdb] Close table 'cache0.tdb' Apr 26 05:04:18 192.168.122.209 [46808.801617] [tdb] Close table 'filter0.tdb' Apr 26 05:04:18 192.168.122.209 [46808.802539] [tempesta fw] modules are stopped Apr 26 05:04:18 192.168.122.209 [46809.119597] [tempesta fw] exiting... Apr 26 05:04:18 192.168.122.209 [46809.258622] [tdb] Shutdown Tempesta DB Apr 26 05:04:19 192.168.122.209 [46809.489930] End test: t_http_rules.test_http_rules.TestHost.test_different_host_in_uri_and_host_header Apr 26 05:04:19 192.168.122.209 [46809.503762] Start test: t_http_rules.test_http_rules.TestHost.test_forwarded_header_first Apr 26 05:04:20 192.168.122.209 [46810.600452] [tdb] Start Tempesta DB Apr 26 05:04:20 192.168.122.209 [46810.745985] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:04:21 192.168.122.209 [46812.383675] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46812.383675] Maybe that's fine, but it's worth checking the [46812.383675] config - if there is no relations between the [46812.383675] names, then host name confusion attack is possible. Apr 26 05:04:22 192.168.122.209 [46812.642745] [tempesta fw] Configuration processing is completed. Apr 26 05:04:22 192.168.122.209 [46812.697219] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:04:22 192.168.122.209 [46813.104767] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:04:22 192.168.122.209 [46813.161839] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:04:22 192.168.122.209 [46813.187617] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:04:22 192.168.122.209 [46813.274291] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:04:22 192.168.122.209 [46813.275827] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:04:22 192.168.122.209 [46813.314274] [tempesta fw] Tempesta FW is ready Apr 26 05:04:23 192.168.122.209 [46814.061267] [tdb] Close table 'client0.tdb' Apr 26 05:04:23 192.168.122.209 [46814.250341] [tdb] Close table 'sessions0.tdb' Apr 26 05:04:27 192.168.122.209 [46817.403492] [tdb] Close table 'cache0.tdb' Apr 26 05:04:27 192.168.122.209 [46817.654885] [tdb] Close table 'filter0.tdb' Apr 26 05:04:27 192.168.122.209 [46817.655321] [tempesta fw] modules are stopped Apr 26 05:04:27 192.168.122.209 [46817.941345] [tempesta fw] exiting... Apr 26 05:04:27 192.168.122.209 [46818.080998] [tdb] Shutdown Tempesta DB Apr 26 05:04:27 192.168.122.209 [46818.296128] End test: t_http_rules.test_http_rules.TestHost.test_forwarded_header_first Apr 26 05:04:27 192.168.122.209 [46818.303042] Start test: t_http_rules.test_http_rules.TestHost.test_forwarded_header_first_2 Apr 26 05:04:29 192.168.122.209 [46819.411359] [tdb] Start Tempesta DB Apr 26 05:04:29 192.168.122.209 [46819.551414] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:04:30 192.168.122.209 [46821.207110] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46821.207110] Maybe that's fine, but it's worth checking the [46821.207110] config - if there is no relations between the [46821.207110] names, then host name confusion attack is possible. Apr 26 05:04:31 192.168.122.209 [46821.438486] [tempesta fw] Configuration processing is completed. Apr 26 05:04:31 192.168.122.209 [46821.489742] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:04:31 192.168.122.209 [46821.903297] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:04:31 192.168.122.209 [46821.966043] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:04:31 192.168.122.209 [46821.991931] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:04:31 192.168.122.209 [46822.078484] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:04:31 192.168.122.209 [46822.080177] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:04:31 192.168.122.209 [46822.118352] [tempesta fw] Tempesta FW is ready Apr 26 05:04:32 192.168.122.209 [46822.836536] [tdb] Close table 'client0.tdb' Apr 26 05:04:32 192.168.122.209 [46823.033965] [tdb] Close table 'sessions0.tdb' Apr 26 05:04:35 192.168.122.209 [46826.171287] [tdb] Close table 'cache0.tdb' Apr 26 05:04:36 192.168.122.209 [46826.413544] [tdb] Close table 'filter0.tdb' Apr 26 05:04:36 192.168.122.209 [46826.413992] [tempesta fw] modules are stopped Apr 26 05:04:36 192.168.122.209 [46826.681830] [tempesta fw] exiting... Apr 26 05:04:36 192.168.122.209 [46826.848400] [tdb] Shutdown Tempesta DB Apr 26 05:04:36 192.168.122.209 [46827.065834] End test: t_http_rules.test_http_rules.TestHost.test_forwarded_header_first_2 Apr 26 05:04:36 192.168.122.209 [46827.075269] Start test: t_http_rules.test_http_rules.TestHost.test_hdr_host_in_forwarded_header Apr 26 05:04:37 192.168.122.209 [46828.188837] [tdb] Start Tempesta DB Apr 26 05:04:37 192.168.122.209 [46828.331095] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:04:39 192.168.122.209 [46830.031874] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46830.031874] Maybe that's fine, but it's worth checking the [46830.031874] config - if there is no relations between the [46830.031874] names, then host name confusion attack is possible. Apr 26 05:04:39 192.168.122.209 [46830.279046] [tempesta fw] Configuration processing is completed. Apr 26 05:04:39 192.168.122.209 [46830.329454] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:04:40 192.168.122.209 [46830.762577] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:04:40 192.168.122.209 [46830.793710] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:04:40 192.168.122.209 [46830.827498] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:04:40 192.168.122.209 [46830.906564] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:04:40 192.168.122.209 [46830.908050] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:04:40 192.168.122.209 [46830.954504] [tempesta fw] Tempesta FW is ready Apr 26 05:04:41 192.168.122.209 [46831.718675] [tdb] Close table 'client0.tdb' Apr 26 05:04:41 192.168.122.209 [46831.915543] [tdb] Close table 'sessions0.tdb' Apr 26 05:04:44 192.168.122.209 [46835.060905] [tdb] Close table 'cache0.tdb' Apr 26 05:04:44 192.168.122.209 [46835.316643] [tdb] Close table 'filter0.tdb' Apr 26 05:04:44 192.168.122.209 [46835.317079] [tempesta fw] modules are stopped Apr 26 05:04:45 192.168.122.209 [46835.652486] [tempesta fw] exiting... Apr 26 05:04:45 192.168.122.209 [46835.776196] [tdb] Shutdown Tempesta DB Apr 26 05:04:45 192.168.122.209 [46835.985982] End test: t_http_rules.test_http_rules.TestHost.test_hdr_host_in_forwarded_header Apr 26 05:04:45 192.168.122.209 [46836.007283] Start test: t_http_rules.test_http_rules.TestHost.test_hdr_host_in_uri Apr 26 05:04:46 192.168.122.209 [46837.139197] [tdb] Start Tempesta DB Apr 26 05:04:46 192.168.122.209 [46837.273182] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:04:48 192.168.122.209 [46838.943321] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46838.943321] Maybe that's fine, but it's worth checking the [46838.943321] config - if there is no relations between the [46838.943321] names, then host name confusion attack is possible. Apr 26 05:04:48 192.168.122.209 [46839.182618] [tempesta fw] Configuration processing is completed. Apr 26 05:04:48 192.168.122.209 [46839.233170] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:04:49 192.168.122.209 [46839.638433] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:04:49 192.168.122.209 [46839.702988] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:04:49 192.168.122.209 [46839.728221] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:04:49 192.168.122.209 [46839.818661] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:04:49 192.168.122.209 [46839.820139] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:04:49 192.168.122.209 [46839.862557] [tempesta fw] Tempesta FW is ready Apr 26 05:04:50 192.168.122.209 [46840.633428] [tdb] Close table 'client0.tdb' Apr 26 05:04:50 192.168.122.209 [46840.820390] [tdb] Close table 'sessions0.tdb' Apr 26 05:04:53 192.168.122.209 [46843.961423] [tdb] Close table 'cache0.tdb' Apr 26 05:04:53 192.168.122.209 [46844.189242] [tdb] Close table 'filter0.tdb' Apr 26 05:04:53 192.168.122.209 [46844.189681] [tempesta fw] modules are stopped Apr 26 05:04:54 192.168.122.209 [46844.467497] [tempesta fw] exiting... Apr 26 05:04:54 192.168.122.209 [46844.606067] [tdb] Shutdown Tempesta DB Apr 26 05:04:54 192.168.122.209 [46844.813348] End test: t_http_rules.test_http_rules.TestHost.test_hdr_host_in_uri Apr 26 05:04:54 192.168.122.209 [46844.833890] Start test: t_http_rules.test_http_rules.TestHost.test_host_in_forwarded_header Apr 26 05:04:55 192.168.122.209 [46845.922152] [tdb] Start Tempesta DB Apr 26 05:04:55 192.168.122.209 [46846.075648] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:04:57 192.168.122.209 [46847.735294] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46847.735294] Maybe that's fine, but it's worth checking the [46847.735294] config - if there is no relations between the [46847.735294] names, then host name confusion attack is possible. Apr 26 05:04:57 192.168.122.209 [46847.954816] [tempesta fw] Configuration processing is completed. Apr 26 05:04:57 192.168.122.209 [46848.006773] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:04:58 192.168.122.209 [46848.426975] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:04:58 192.168.122.209 [46848.452992] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:04:58 192.168.122.209 [46848.487257] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:04:58 192.168.122.209 [46848.570764] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:04:58 192.168.122.209 [46848.572542] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:04:58 192.168.122.209 [46848.610660] [tempesta fw] Tempesta FW is ready Apr 26 05:04:58 192.168.122.209 [46849.355455] [tdb] Close table 'client0.tdb' Apr 26 05:04:59 192.168.122.209 [46849.543292] [tdb] Close table 'sessions0.tdb' Apr 26 05:05:02 192.168.122.209 [46852.685775] [tdb] Close table 'cache0.tdb' Apr 26 05:05:02 192.168.122.209 [46852.930217] [tdb] Close table 'filter0.tdb' Apr 26 05:05:02 192.168.122.209 [46852.930670] [tempesta fw] modules are stopped Apr 26 05:05:02 192.168.122.209 [46853.179625] [tempesta fw] exiting... Apr 26 05:05:02 192.168.122.209 [46853.340265] [tdb] Shutdown Tempesta DB Apr 26 05:05:03 192.168.122.209 [46853.547846] End test: t_http_rules.test_http_rules.TestHost.test_host_in_forwarded_header Apr 26 05:05:03 192.168.122.209 [46853.559157] Start test: t_http_rules.test_http_rules.TestHost.test_host_in_host_header Apr 26 05:05:04 192.168.122.209 [46854.709952] [tdb] Start Tempesta DB Apr 26 05:05:04 192.168.122.209 [46854.859762] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:05:06 192.168.122.209 [46856.488187] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46856.488187] Maybe that's fine, but it's worth checking the [46856.488187] config - if there is no relations between the [46856.488187] names, then host name confusion attack is possible. Apr 26 05:05:06 192.168.122.209 [46856.710964] [tempesta fw] Configuration processing is completed. Apr 26 05:05:06 192.168.122.209 [46856.761056] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:05:06 192.168.122.209 [46857.176936] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:05:06 192.168.122.209 [46857.233564] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:05:06 192.168.122.209 [46857.259088] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:05:06 192.168.122.209 [46857.346883] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:05:06 192.168.122.209 [46857.348284] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:05:07 192.168.122.209 [46857.402832] [tempesta fw] Tempesta FW is ready Apr 26 05:05:07 192.168.122.209 [46858.154342] [tdb] Close table 'client0.tdb' Apr 26 05:05:07 192.168.122.209 [46858.355951] [tdb] Close table 'sessions0.tdb' Apr 26 05:05:11 192.168.122.209 [46861.488348] [tdb] Close table 'cache0.tdb' Apr 26 05:05:11 192.168.122.209 [46861.716426] [tdb] Close table 'filter0.tdb' Apr 26 05:05:11 192.168.122.209 [46861.716942] [tempesta fw] modules are stopped Apr 26 05:05:11 192.168.122.209 [46862.003665] [tempesta fw] exiting... Apr 26 05:05:11 192.168.122.209 [46862.124544] [tdb] Shutdown Tempesta DB Apr 26 05:05:11 192.168.122.209 [46862.328053] End test: t_http_rules.test_http_rules.TestHost.test_host_in_host_header Apr 26 05:05:11 192.168.122.209 [46862.339150] Start test: t_http_rules.test_http_rules.TestHost.test_host_in_uri Apr 26 05:05:13 192.168.122.209 [46863.508477] [tdb] Start Tempesta DB Apr 26 05:05:13 192.168.122.209 [46863.639227] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:05:14 192.168.122.209 [46865.303759] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46865.303759] Maybe that's fine, but it's worth checking the [46865.303759] config - if there is no relations between the [46865.303759] names, then host name confusion attack is possible. Apr 26 05:05:15 192.168.122.209 [46865.527060] [tempesta fw] Configuration processing is completed. Apr 26 05:05:15 192.168.122.209 [46865.579155] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:05:15 192.168.122.209 [46865.994980] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:05:15 192.168.122.209 [46866.021182] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:05:15 192.168.122.209 [46866.060195] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:05:15 192.168.122.209 [46866.159011] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:05:15 192.168.122.209 [46866.160925] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:05:15 192.168.122.209 [46866.214964] [tempesta fw] Tempesta FW is ready Apr 26 05:05:16 192.168.122.209 [46866.974415] [tdb] Close table 'client0.tdb' Apr 26 05:05:16 192.168.122.209 [46867.161954] [tdb] Close table 'sessions0.tdb' Apr 26 05:05:19 192.168.122.209 [46870.347249] [tdb] Close table 'cache0.tdb' Apr 26 05:05:20 192.168.122.209 [46870.617125] [tdb] Close table 'filter0.tdb' Apr 26 05:05:20 192.168.122.209 [46870.617559] [tempesta fw] modules are stopped Apr 26 05:05:20 192.168.122.209 [46870.860619] [tempesta fw] exiting... Apr 26 05:05:20 192.168.122.209 [46870.993431] [tdb] Shutdown Tempesta DB Apr 26 05:05:20 192.168.122.209 [46871.219590] End test: t_http_rules.test_http_rules.TestHost.test_host_in_uri Apr 26 05:05:20 192.168.122.209 [46871.230824] Start test: t_http_rules.test_http_tables.HttpTablesTestBase.test Apr 26 05:05:20 192.168.122.209 [46871.246061] End test: t_http_rules.test_http_tables.HttpTablesTestBase.test Apr 26 05:05:20 192.168.122.209 [46871.257054] Start test: t_http_rules.test_http_tables.HttpTablesTestCustomRedirectCorrectVariables.test Apr 26 05:05:22 192.168.122.209 [46872.406898] [tdb] Start Tempesta DB Apr 26 05:05:22 192.168.122.209 [46872.551332] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:05:23 192.168.122.209 [46874.247955] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46874.247955] Maybe that's fine, but it's worth checking the [46874.247955] config - if there is no relations between the [46874.247955] names, then host name confusion attack is possible. Apr 26 05:05:24 192.168.122.209 [46874.415094] [tempesta fw] Configuration processing is completed. Apr 26 05:05:24 192.168.122.209 [46874.464946] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:05:24 192.168.122.209 [46874.868307] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:05:24 192.168.122.209 [46874.924644] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:05:24 192.168.122.209 [46874.949577] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:05:24 192.168.122.209 [46875.018978] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:05:24 192.168.122.209 [46875.020153] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:05:24 192.168.122.209 [46875.059058] [tempesta fw] Tempesta FW is ready Apr 26 05:05:25 192.168.122.209 [46875.620466] [tdb] Close table 'client0.tdb' Apr 26 05:05:25 192.168.122.209 [46875.819380] [tdb] Close table 'sessions0.tdb' Apr 26 05:05:28 192.168.122.209 [46878.974792] [tdb] Close table 'cache0.tdb' Apr 26 05:05:28 192.168.122.209 [46879.198490] [tdb] Close table 'filter0.tdb' Apr 26 05:05:28 192.168.122.209 [46879.198934] [tempesta fw] modules are stopped Apr 26 05:05:29 192.168.122.209 [46879.415799] [tempesta fw] exiting... Apr 26 05:05:29 192.168.122.209 [46879.557546] [tdb] Shutdown Tempesta DB Apr 26 05:05:29 192.168.122.209 [46879.774831] End test: t_http_rules.test_http_tables.HttpTablesTestCustomRedirectCorrectVariables.test Apr 26 05:05:29 192.168.122.209 [46879.785304] Start test: t_http_rules.test_http_tables.HttpTablesTestCustomRedirectDifferentResponseStatus.test Apr 26 05:05:30 192.168.122.209 [46880.944041] [tdb] Start Tempesta DB Apr 26 05:05:30 192.168.122.209 [46881.087297] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:05:32 192.168.122.209 [46882.888391] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46882.888391] Maybe that's fine, but it's worth checking the [46882.888391] config - if there is no relations between the [46882.888391] names, then host name confusion attack is possible. Apr 26 05:05:32 192.168.122.209 [46883.051230] [tempesta fw] Configuration processing is completed. Apr 26 05:05:32 192.168.122.209 [46883.108239] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:05:33 192.168.122.209 [46883.524597] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:05:33 192.168.122.209 [46883.551377] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:05:33 192.168.122.209 [46883.585350] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:05:33 192.168.122.209 [46883.631197] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:05:33 192.168.122.209 [46883.632601] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:05:33 192.168.122.209 [46883.675188] [tempesta fw] Tempesta FW is ready Apr 26 05:05:33 192.168.122.209 [46884.241491] [tdb] Close table 'client0.tdb' Apr 26 05:05:34 192.168.122.209 [46884.427860] [tdb] Close table 'sessions0.tdb' Apr 26 05:05:37 192.168.122.209 [46887.608853] [tdb] Close table 'cache0.tdb' Apr 26 05:05:37 192.168.122.209 [46887.877164] [tdb] Close table 'filter0.tdb' Apr 26 05:05:37 192.168.122.209 [46887.877591] [tempesta fw] modules are stopped Apr 26 05:05:37 192.168.122.209 [46888.129565] [tempesta fw] exiting... Apr 26 05:05:37 192.168.122.209 [46888.263810] [tdb] Shutdown Tempesta DB Apr 26 05:05:38 192.168.122.209 [46888.466512] End test: t_http_rules.test_http_tables.HttpTablesTestCustomRedirectDifferentResponseStatus.test Apr 26 05:05:38 192.168.122.209 [46888.478028] Start test: t_http_rules.test_http_tables.HttpTablesTestCustomRedirectNonExistentVariables.test Apr 26 05:05:39 192.168.122.209 [46889.587832] [tdb] Start Tempesta DB Apr 26 05:05:39 192.168.122.209 [46889.719856] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:05:41 192.168.122.209 [46891.428722] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46891.428722] Maybe that's fine, but it's worth checking the [46891.428722] config - if there is no relations between the [46891.428722] names, then host name confusion attack is possible. Apr 26 05:05:41 192.168.122.209 [46891.583317] [tempesta fw] Configuration processing is completed. Apr 26 05:05:41 192.168.122.209 [46891.633398] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:05:41 192.168.122.209 [46892.047699] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:05:41 192.168.122.209 [46892.104095] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:05:41 192.168.122.209 [46892.129243] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:05:41 192.168.122.209 [46892.175295] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:05:41 192.168.122.209 [46892.176331] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:05:41 192.168.122.209 [46892.211281] [tempesta fw] Tempesta FW is ready Apr 26 05:05:42 192.168.122.209 [46892.767114] [tdb] Close table 'client0.tdb' Apr 26 05:05:42 192.168.122.209 [46892.951910] [tdb] Close table 'sessions0.tdb' Apr 26 05:05:45 192.168.122.209 [46896.107099] [tdb] Close table 'cache0.tdb' Apr 26 05:05:45 192.168.122.209 [46896.349444] [tdb] Close table 'filter0.tdb' Apr 26 05:05:45 192.168.122.209 [46896.349885] [tempesta fw] modules are stopped Apr 26 05:05:46 192.168.122.209 [46896.564808] [tempesta fw] exiting... Apr 26 05:05:46 192.168.122.209 [46896.698479] [tdb] Shutdown Tempesta DB Apr 26 05:05:46 192.168.122.209 [46896.919215] End test: t_http_rules.test_http_tables.HttpTablesTestCustomRedirectNonExistentVariables.test Apr 26 05:05:46 192.168.122.209 [46896.930439] Start test: t_http_rules.test_http_tables.HttpTablesTestCustomRedirectTooManyVariables.test Apr 26 05:05:47 192.168.122.209 [46898.025377] [tdb] Start Tempesta DB Apr 26 05:05:47 192.168.122.209 [46898.164710] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:05:49 192.168.122.209 [46899.832034] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46899.832034] Maybe that's fine, but it's worth checking the [46899.832034] config - if there is no relations between the [46899.832034] names, then host name confusion attack is possible. Apr 26 05:05:49 192.168.122.209 [46899.936087] [tempesta fw] ERROR: http_tbl: too many vars (more 8) in redirection url: 'https://$host$request_uri/$host$request_uri/$host$request_uri/$host$request_uri/$host' Apr 26 05:05:49 192.168.122.209 [46899.937759] [tempesta fw] ERROR: configuration parsing error: [46899.937759] 21: uri == "/static*" -> 301 = https://$host$request_uri/$host$request_uri/$host [46899.937759] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 05:05:49 192.168.122.209 [46899.940391] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 05:05:49 192.168.122.209 [46900.158980] [tempesta fw] exiting... Apr 26 05:05:49 192.168.122.209 [46900.283403] [tdb] Shutdown Tempesta DB Apr 26 05:05:52 192.168.122.209 [46903.011724] End test: t_http_rules.test_http_tables.HttpTablesTestCustomRedirectTooManyVariables.test Apr 26 05:05:52 192.168.122.209 [46903.023776] Start test: t_http_rules.test_http_tables.HttpTablesTestEmptyChainDefault.test Apr 26 05:05:53 192.168.122.209 [46904.111198] [tdb] Start Tempesta DB Apr 26 05:05:53 192.168.122.209 [46904.245956] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:05:54 192.168.122.209 [46904.904488] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46904.904488] Maybe that's fine, but it's worth checking the [46904.904488] config - if there is no relations between the [46904.904488] names, then host name confusion attack is possible. Apr 26 05:05:54 192.168.122.209 [46905.063458] [tempesta fw] Configuration processing is completed. Apr 26 05:05:54 192.168.122.209 [46905.122616] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:05:55 192.168.122.209 [46905.543142] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:05:55 192.168.122.209 [46905.603988] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:05:55 192.168.122.209 [46905.630194] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:05:55 192.168.122.209 [46905.671456] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:05:55 192.168.122.209 [46905.672618] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:05:55 192.168.122.209 [46905.727455] [tempesta fw] Tempesta FW is ready Apr 26 05:05:55 192.168.122.209 [46905.845745] [tempesta fw] Warning: request dropped: cannot find appropriate virtual host, status 403: 127.0.0.2 Apr 26 05:05:55 192.168.122.209 [46906.286016] [tdb] Close table 'client0.tdb' Apr 26 05:05:56 192.168.122.209 [46906.472311] [tdb] Close table 'sessions0.tdb' Apr 26 05:05:59 192.168.122.209 [46909.628652] [tdb] Close table 'cache0.tdb' Apr 26 05:05:59 192.168.122.209 [46909.860387] [tdb] Close table 'filter0.tdb' Apr 26 05:05:59 192.168.122.209 [46909.860824] [tempesta fw] modules are stopped Apr 26 05:05:59 192.168.122.209 [46910.051247] [tempesta fw] exiting... Apr 26 05:05:59 192.168.122.209 [46910.181036] [tdb] Shutdown Tempesta DB Apr 26 05:06:00 192.168.122.209 [46910.401805] End test: t_http_rules.test_http_tables.HttpTablesTestEmptyChainDefault.test Apr 26 05:06:00 192.168.122.209 [46910.425691] Start test: t_http_rules.test_http_tables.HttpTablesTestEmptyChainDrop.test Apr 26 05:06:01 192.168.122.209 [46911.522361] [tdb] Start Tempesta DB Apr 26 05:06:01 192.168.122.209 [46911.649184] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:06:02 192.168.122.209 [46913.328578] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46913.328578] Maybe that's fine, but it's worth checking the [46913.328578] config - if there is no relations between the [46913.328578] names, then host name confusion attack is possible. Apr 26 05:06:03 192.168.122.209 [46913.475578] [tempesta fw] Configuration processing is completed. Apr 26 05:06:03 192.168.122.209 [46913.528358] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:06:03 192.168.122.209 [46913.939263] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:06:03 192.168.122.209 [46913.996019] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:06:03 192.168.122.209 [46914.021432] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:06:03 192.168.122.209 [46914.071528] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:06:03 192.168.122.209 [46914.072325] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:06:03 192.168.122.209 [46914.115548] [tempesta fw] Tempesta FW is ready Apr 26 05:06:03 192.168.122.209 [46914.240355] [tempesta fw] Warning: request dropped: cannot find appropriate virtual host, status 403: 127.0.0.2 Apr 26 05:06:04 192.168.122.209 [46914.661104] [tdb] Close table 'client0.tdb' Apr 26 05:06:04 192.168.122.209 [46914.851620] [tdb] Close table 'sessions0.tdb' Apr 26 05:06:07 192.168.122.209 [46918.044999] [tdb] Close table 'cache0.tdb' Apr 26 05:06:07 192.168.122.209 [46918.320669] [tdb] Close table 'filter0.tdb' Apr 26 05:06:07 192.168.122.209 [46918.321118] [tempesta fw] modules are stopped Apr 26 05:06:08 192.168.122.209 [46918.529907] [tempesta fw] exiting... Apr 26 05:06:08 192.168.122.209 [46918.666013] [tdb] Shutdown Tempesta DB Apr 26 05:06:08 192.168.122.209 [46918.872421] End test: t_http_rules.test_http_tables.HttpTablesTestEmptyChainDrop.test Apr 26 05:06:08 192.168.122.209 [46918.882305] Start test: t_http_rules.test_http_tables.HttpTablesTestEmptyChainReply.test Apr 26 05:06:09 192.168.122.209 [46920.043529] [tdb] Start Tempesta DB Apr 26 05:06:09 192.168.122.209 [46920.188918] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:06:11 192.168.122.209 [46921.872961] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46921.872961] Maybe that's fine, but it's worth checking the [46921.872961] config - if there is no relations between the [46921.872961] names, then host name confusion attack is possible. Apr 26 05:06:11 192.168.122.209 [46922.043760] [tempesta fw] Configuration processing is completed. Apr 26 05:06:11 192.168.122.209 [46922.095333] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:06:12 192.168.122.209 [46922.546590] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:06:12 192.168.122.209 [46922.574394] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:06:12 192.168.122.209 [46922.611409] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:06:12 192.168.122.209 [46922.663711] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:06:12 192.168.122.209 [46922.665168] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:06:12 192.168.122.209 [46922.703689] [tempesta fw] Tempesta FW is ready Apr 26 05:06:12 192.168.122.209 [46922.844514] [tempesta fw] Warning: request dropped: cannot find appropriate virtual host, status 403: 127.0.0.2 Apr 26 05:06:12 192.168.122.209 [46923.300197] [tdb] Close table 'client0.tdb' Apr 26 05:06:13 192.168.122.209 [46923.493138] [tdb] Close table 'sessions0.tdb' Apr 26 05:06:16 192.168.122.209 [46926.660037] [tdb] Close table 'cache0.tdb' Apr 26 05:06:16 192.168.122.209 [46926.908595] [tdb] Close table 'filter0.tdb' Apr 26 05:06:16 192.168.122.209 [46926.909029] [tempesta fw] modules are stopped Apr 26 05:06:16 192.168.122.209 [46927.115795] [tempesta fw] exiting... Apr 26 05:06:16 192.168.122.209 [46927.253396] [tdb] Shutdown Tempesta DB Apr 26 05:06:17 192.168.122.209 [46927.484091] End test: t_http_rules.test_http_tables.HttpTablesTestEmptyChainReply.test Apr 26 05:06:17 192.168.122.209 [46927.498535] Start test: t_http_rules.test_http_tables.HttpTablesTestEmptyMainChainDefault.test Apr 26 05:06:18 192.168.122.209 [46928.633366] [tdb] Start Tempesta DB Apr 26 05:06:18 192.168.122.209 [46928.779671] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:06:19 192.168.122.209 [46930.285211] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46930.285211] Maybe that's fine, but it's worth checking the [46930.285211] config - if there is no relations between the [46930.285211] names, then host name confusion attack is possible. Apr 26 05:06:20 192.168.122.209 [46930.411785] [tempesta fw] Configuration processing is completed. Apr 26 05:06:20 192.168.122.209 [46930.463810] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:06:20 192.168.122.209 [46930.934742] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:06:20 192.168.122.209 [46930.993364] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:06:20 192.168.122.209 [46931.022076] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:06:20 192.168.122.209 [46931.067807] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:06:20 192.168.122.209 [46931.069085] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:06:20 192.168.122.209 [46931.107825] [tempesta fw] Tempesta FW is ready Apr 26 05:06:20 192.168.122.209 [46931.250107] [tempesta fw] Warning: request dropped: cannot find appropriate virtual host, status 403: 127.0.0.2 Apr 26 05:06:21 192.168.122.209 [46931.664988] [tdb] Close table 'client0.tdb' Apr 26 05:06:21 192.168.122.209 [46931.850792] [tdb] Close table 'sessions0.tdb' Apr 26 05:06:24 192.168.122.209 [46934.997878] [tdb] Close table 'cache0.tdb' Apr 26 05:06:24 192.168.122.209 [46935.236660] [tdb] Close table 'filter0.tdb' Apr 26 05:06:24 192.168.122.209 [46935.237096] [tempesta fw] modules are stopped Apr 26 05:06:25 192.168.122.209 [46935.452560] [tempesta fw] exiting... Apr 26 05:06:25 192.168.122.209 [46935.565168] [tdb] Shutdown Tempesta DB Apr 26 05:06:25 192.168.122.209 [46935.768986] End test: t_http_rules.test_http_tables.HttpTablesTestEmptyMainChainDefault.test Apr 26 05:06:25 192.168.122.209 [46935.782104] Start test: t_http_rules.test_http_tables.HttpTablesTestEmptyMainChainDrop.test Apr 26 05:06:26 192.168.122.209 [46936.928458] [tdb] Start Tempesta DB Apr 26 05:06:26 192.168.122.209 [46937.058083] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:06:28 192.168.122.209 [46938.688930] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46938.688930] Maybe that's fine, but it's worth checking the [46938.688930] config - if there is no relations between the [46938.688930] names, then host name confusion attack is possible. Apr 26 05:06:28 192.168.122.209 [46938.827907] [tempesta fw] Configuration processing is completed. Apr 26 05:06:28 192.168.122.209 [46938.884944] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:06:28 192.168.122.209 [46939.335545] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:06:29 192.168.122.209 [46939.399988] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:06:29 192.168.122.209 [46939.429065] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:06:29 192.168.122.209 [46939.479908] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:06:29 192.168.122.209 [46939.481299] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:06:29 192.168.122.209 [46939.523884] [tempesta fw] Tempesta FW is ready Apr 26 05:06:29 192.168.122.209 [46939.666111] [tempesta fw] Warning: request dropped: cannot find appropriate virtual host, status 403: 127.0.0.2 Apr 26 05:06:29 192.168.122.209 [46940.093936] [tdb] Close table 'client0.tdb' Apr 26 05:06:29 192.168.122.209 [46940.316986] [tdb] Close table 'sessions0.tdb' Apr 26 05:06:33 192.168.122.209 [46943.533506] [tdb] Close table 'cache0.tdb' Apr 26 05:06:33 192.168.122.209 [46943.789865] [tdb] Close table 'filter0.tdb' Apr 26 05:06:33 192.168.122.209 [46943.790295] [tempesta fw] modules are stopped Apr 26 05:06:33 192.168.122.209 [46944.018479] [tempesta fw] exiting... Apr 26 05:06:33 192.168.122.209 [46944.139740] [tdb] Shutdown Tempesta DB Apr 26 05:06:33 192.168.122.209 [46944.358697] End test: t_http_rules.test_http_tables.HttpTablesTestEmptyMainChainDrop.test Apr 26 05:06:33 192.168.122.209 [46944.370150] Start test: t_http_rules.test_http_tables.HttpTablesTestEmptyMainChainReply.test Apr 26 05:06:35 192.168.122.209 [46945.628482] [tdb] Start Tempesta DB Apr 26 05:06:35 192.168.122.209 [46945.773469] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:06:37 192.168.122.209 [46947.405371] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46947.405371] Maybe that's fine, but it's worth checking the [46947.405371] config - if there is no relations between the [46947.405371] names, then host name confusion attack is possible. Apr 26 05:06:37 192.168.122.209 [46947.539929] [tempesta fw] Configuration processing is completed. Apr 26 05:06:37 192.168.122.209 [46947.597412] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:06:37 192.168.122.209 [46948.088356] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:06:37 192.168.122.209 [46948.118729] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:06:37 192.168.122.209 [46948.156268] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:06:37 192.168.122.209 [46948.228062] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:06:37 192.168.122.209 [46948.229912] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:06:37 192.168.122.209 [46948.267998] [tempesta fw] Tempesta FW is ready Apr 26 05:06:38 192.168.122.209 [46948.407820] [tempesta fw] Warning: request dropped: cannot find appropriate virtual host, status 403: 127.0.0.2 Apr 26 05:06:38 192.168.122.209 [46948.854445] [tdb] Close table 'client0.tdb' Apr 26 05:06:38 192.168.122.209 [46949.043745] [tdb] Close table 'sessions0.tdb' Apr 26 05:06:41 192.168.122.209 [46952.238690] [tdb] Close table 'cache0.tdb' Apr 26 05:06:42 192.168.122.209 [46952.574281] [tdb] Close table 'filter0.tdb' Apr 26 05:06:42 192.168.122.209 [46952.574843] [tempesta fw] modules are stopped Apr 26 05:06:42 192.168.122.209 [46952.797067] [tempesta fw] exiting... Apr 26 05:06:42 192.168.122.209 [46952.920292] [tdb] Shutdown Tempesta DB Apr 26 05:06:42 192.168.122.209 [46953.169513] End test: t_http_rules.test_http_tables.HttpTablesTestEmptyMainChainReply.test Apr 26 05:06:42 192.168.122.209 [46953.192349] Start test: t_http_rules.test_http_tables.HttpTablesTestMarkRule.test_reject_by_mark_disable_tso_gro_gso Apr 26 05:06:43 192.168.122.209 [46954.334289] [tdb] Start Tempesta DB Apr 26 05:06:44 192.168.122.209 [46954.466523] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:06:45 192.168.122.209 [46956.093419] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46956.093419] Maybe that's fine, but it's worth checking the [46956.093419] config - if there is no relations between the [46956.093419] names, then host name confusion attack is possible. Apr 26 05:06:45 192.168.122.209 [46956.244125] [tempesta fw] Configuration processing is completed. Apr 26 05:06:45 192.168.122.209 [46956.298265] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:06:46 192.168.122.209 [46956.702338] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:06:46 192.168.122.209 [46956.765250] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:06:46 192.168.122.209 [46956.792374] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:06:46 192.168.122.209 [46956.840124] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:06:46 192.168.122.209 [46956.841497] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:06:46 192.168.122.209 [46956.880108] [tempesta fw] Tempesta FW is ready Apr 26 05:06:50 192.168.122.209 [46960.823900] [tdb] Close table 'client0.tdb' Apr 26 05:06:50 192.168.122.209 [46961.027586] [tdb] Close table 'sessions0.tdb' Apr 26 05:06:54 192.168.122.209 [46964.549490] [tdb] Close table 'cache0.tdb' Apr 26 05:06:54 192.168.122.209 [46965.094722] [tdb] Close table 'filter0.tdb' Apr 26 05:06:54 192.168.122.209 [46965.095166] [tempesta fw] modules are stopped Apr 26 05:06:54 192.168.122.209 [46965.316147] [tempesta fw] exiting... Apr 26 05:06:55 192.168.122.209 [46965.532261] [tdb] Shutdown Tempesta DB Apr 26 05:06:55 192.168.122.209 [46965.792729] End test: t_http_rules.test_http_tables.HttpTablesTestMarkRule.test_reject_by_mark_disable_tso_gro_gso Apr 26 05:06:55 192.168.122.209 [46965.817536] Start test: t_http_rules.test_http_tables.HttpTablesTestMarkRule.test_reject_by_mark_enable_tso_gro_gso Apr 26 05:06:56 192.168.122.209 [46967.090752] [tdb] Start Tempesta DB Apr 26 05:06:56 192.168.122.209 [46967.249980] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:06:59 192.168.122.209 [46969.597716] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46969.597716] Maybe that's fine, but it's worth checking the [46969.597716] config - if there is no relations between the [46969.597716] names, then host name confusion attack is possible. Apr 26 05:07:00 192.168.122.209 [46970.448626] [tempesta fw] Configuration processing is completed. Apr 26 05:07:00 192.168.122.209 [46970.596694] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:07:00 192.168.122.209 [46971.048391] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:07:00 192.168.122.209 [46971.112006] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:07:00 192.168.122.209 [46971.139861] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:07:00 192.168.122.209 [46971.184293] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:07:00 192.168.122.209 [46971.185517] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:07:00 192.168.122.209 [46971.224281] [tempesta fw] Tempesta FW is ready Apr 26 05:07:04 192.168.122.209 [46975.150268] [tdb] Close table 'client0.tdb' Apr 26 05:07:04 192.168.122.209 [46975.375944] [tdb] Close table 'sessions0.tdb' Apr 26 05:07:08 192.168.122.209 [46978.537584] [tdb] Close table 'cache0.tdb' Apr 26 05:07:08 192.168.122.209 [46978.786009] [tdb] Close table 'filter0.tdb' Apr 26 05:07:08 192.168.122.209 [46978.786494] [tempesta fw] modules are stopped Apr 26 05:07:08 192.168.122.209 [46978.991098] [tempesta fw] exiting... Apr 26 05:07:08 192.168.122.209 [46979.138840] [tdb] Shutdown Tempesta DB Apr 26 05:07:08 192.168.122.209 [46979.378623] End test: t_http_rules.test_http_tables.HttpTablesTestMarkRule.test_reject_by_mark_enable_tso_gro_gso Apr 26 05:07:08 192.168.122.209 [46979.389695] Start test: t_http_rules.test_http_tables.HttpTablesTestMarkRules.test_chains Apr 26 05:07:10 192.168.122.209 [46980.549048] [tdb] Start Tempesta DB Apr 26 05:07:10 192.168.122.209 [46980.697587] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:07:13 192.168.122.209 [46983.897907] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46983.897907] Maybe that's fine, but it's worth checking the [46983.897907] config - if there is no relations between the [46983.897907] names, then host name confusion attack is possible. Apr 26 05:07:13 192.168.122.209 [46984.364577] [tempesta fw] Configuration processing is completed. Apr 26 05:07:14 192.168.122.209 [46984.417278] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:07:14 192.168.122.209 [46984.851434] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:07:14 192.168.122.209 [46984.878378] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:07:14 192.168.122.209 [46984.914090] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:07:14 192.168.122.209 [46985.168499] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:07:14 192.168.122.209 [46985.170389] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:07:14 192.168.122.209 [46985.216471] [tempesta fw] Tempesta FW is ready Apr 26 05:07:16 192.168.122.209 [46987.113332] [tdb] Close table 'client0.tdb' Apr 26 05:07:16 192.168.122.209 [46987.313010] [tdb] Close table 'sessions0.tdb' Apr 26 05:07:20 192.168.122.209 [46990.441938] [tdb] Close table 'cache0.tdb' Apr 26 05:07:20 192.168.122.209 [46990.657960] [tdb] Close table 'filter0.tdb' Apr 26 05:07:20 192.168.122.209 [46990.658415] [tempesta fw] modules are stopped Apr 26 05:07:20 192.168.122.209 [46991.061641] [tempesta fw] exiting... Apr 26 05:07:20 192.168.122.209 [46991.191668] [tdb] Shutdown Tempesta DB Apr 26 05:07:20 192.168.122.209 [46991.391825] End test: t_http_rules.test_http_tables.HttpTablesTestMarkRules.test_chains Apr 26 05:07:21 192.168.122.209 [46991.404539] Start test: t_http_rules.test_http_tables.HttpTablesTestMixedChainDefault.test Apr 26 05:07:22 192.168.122.209 [46992.525961] [tdb] Start Tempesta DB Apr 26 05:07:22 192.168.122.209 [46992.655626] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:07:23 192.168.122.209 [46994.389955] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [46994.389955] Maybe that's fine, but it's worth checking the [46994.389955] config - if there is no relations between the [46994.389955] names, then host name confusion attack is possible. Apr 26 05:07:24 192.168.122.209 [46994.536617] [tempesta fw] Configuration processing is completed. Apr 26 05:07:24 192.168.122.209 [46994.584845] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:07:24 192.168.122.209 [46994.996797] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:07:24 192.168.122.209 [46995.054610] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:07:24 192.168.122.209 [46995.086304] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:07:24 192.168.122.209 [46995.136666] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:07:24 192.168.122.209 [46995.138443] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:07:24 192.168.122.209 [46995.180612] [tempesta fw] Tempesta FW is ready Apr 26 05:07:24 192.168.122.209 [46995.307375] [tempesta fw] Warning: request dropped: cannot find appropriate virtual host, status 403: 127.0.0.2 Apr 26 05:07:25 192.168.122.209 [46995.754175] [tdb] Close table 'client0.tdb' Apr 26 05:07:25 192.168.122.209 [46995.942952] [tdb] Close table 'sessions0.tdb' Apr 26 05:07:28 192.168.122.209 [46999.097741] [tdb] Close table 'cache0.tdb' Apr 26 05:07:28 192.168.122.209 [46999.330800] [tdb] Close table 'filter0.tdb' Apr 26 05:07:28 192.168.122.209 [46999.331244] [tempesta fw] modules are stopped Apr 26 05:07:29 192.168.122.209 [46999.518630] [tempesta fw] exiting... Apr 26 05:07:29 192.168.122.209 [46999.627815] [tdb] Shutdown Tempesta DB Apr 26 05:07:29 192.168.122.209 [46999.844798] End test: t_http_rules.test_http_tables.HttpTablesTestMixedChainDefault.test Apr 26 05:07:29 192.168.122.209 [46999.867350] Start test: t_http_rules.test_http_tables.HttpTablesTestMixedChainDrop.test Apr 26 05:07:30 192.168.122.209 [47000.988860] [tdb] Start Tempesta DB Apr 26 05:07:30 192.168.122.209 [47001.123151] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:07:32 192.168.122.209 [47002.818015] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47002.818015] Maybe that's fine, but it's worth checking the [47002.818015] config - if there is no relations between the [47002.818015] names, then host name confusion attack is possible. Apr 26 05:07:32 192.168.122.209 [47002.968710] [tempesta fw] Configuration processing is completed. Apr 26 05:07:32 192.168.122.209 [47003.021695] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:07:33 192.168.122.209 [47003.469220] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:07:33 192.168.122.209 [47003.529249] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:07:33 192.168.122.209 [47003.558066] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:07:33 192.168.122.209 [47003.624712] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:07:33 192.168.122.209 [47003.625882] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:07:33 192.168.122.209 [47003.668711] [tempesta fw] Tempesta FW is ready Apr 26 05:07:33 192.168.122.209 [47003.812439] [tempesta fw] Warning: request dropped: cannot find appropriate virtual host, status 403: 127.0.0.2 Apr 26 05:07:33 192.168.122.209 [47004.219690] [tdb] Close table 'client0.tdb' Apr 26 05:07:34 192.168.122.209 [47004.415824] [tdb] Close table 'sessions0.tdb' Apr 26 05:07:37 192.168.122.209 [47007.556352] [tdb] Close table 'cache0.tdb' Apr 26 05:07:37 192.168.122.209 [47007.818506] [tdb] Close table 'filter0.tdb' Apr 26 05:07:37 192.168.122.209 [47007.818933] [tempesta fw] modules are stopped Apr 26 05:07:37 192.168.122.209 [47008.045424] [tempesta fw] exiting... Apr 26 05:07:37 192.168.122.209 [47008.190986] [tdb] Shutdown Tempesta DB Apr 26 05:07:37 192.168.122.209 [47008.366260] End test: t_http_rules.test_http_tables.HttpTablesTestMixedChainDrop.test Apr 26 05:07:37 192.168.122.209 [47008.372535] Start test: t_http_rules.test_http_tables.HttpTablesTestMixedChainReply.test Apr 26 05:07:39 192.168.122.209 [47009.440019] [tdb] Start Tempesta DB Apr 26 05:07:39 192.168.122.209 [47009.574739] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:07:40 192.168.122.209 [47011.305883] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47011.305883] Maybe that's fine, but it's worth checking the [47011.305883] config - if there is no relations between the [47011.305883] names, then host name confusion attack is possible. Apr 26 05:07:41 192.168.122.209 [47011.456837] [tempesta fw] Configuration processing is completed. Apr 26 05:07:41 192.168.122.209 [47011.507827] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:07:41 192.168.122.209 [47011.925375] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:07:41 192.168.122.209 [47011.951525] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:07:41 192.168.122.209 [47011.985345] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:07:41 192.168.122.209 [47012.028854] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:07:41 192.168.122.209 [47012.031183] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:07:41 192.168.122.209 [47012.064773] [tempesta fw] Tempesta FW is ready Apr 26 05:07:41 192.168.122.209 [47012.203680] [tempesta fw] Warning: request dropped: cannot find appropriate virtual host, status 403: 127.0.0.2 Apr 26 05:07:42 192.168.122.209 [47012.639097] [tdb] Close table 'client0.tdb' Apr 26 05:07:42 192.168.122.209 [47012.832436] [tdb] Close table 'sessions0.tdb' Apr 26 05:07:45 192.168.122.209 [47015.996784] [tdb] Close table 'cache0.tdb' Apr 26 05:07:45 192.168.122.209 [47016.208333] [tdb] Close table 'filter0.tdb' Apr 26 05:07:45 192.168.122.209 [47016.208781] [tempesta fw] modules are stopped Apr 26 05:07:46 192.168.122.209 [47016.441542] [tempesta fw] exiting... Apr 26 05:07:46 192.168.122.209 [47016.581608] [tdb] Shutdown Tempesta DB Apr 26 05:07:46 192.168.122.209 [47016.758027] End test: t_http_rules.test_http_tables.HttpTablesTestMixedChainReply.test Apr 26 05:07:46 192.168.122.209 [47016.783599] Start test: t_http_rules.test_http_tables.HttpTablesTestMixedChainResp.test Apr 26 05:07:47 192.168.122.209 [47017.845610] [tdb] Start Tempesta DB Apr 26 05:07:47 192.168.122.209 [47017.983294] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:07:49 192.168.122.209 [47019.786150] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47019.786150] Maybe that's fine, but it's worth checking the [47019.786150] config - if there is no relations between the [47019.786150] names, then host name confusion attack is possible. Apr 26 05:07:49 192.168.122.209 [47019.936918] [tempesta fw] Configuration processing is completed. Apr 26 05:07:49 192.168.122.209 [47019.994974] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:07:50 192.168.122.209 [47020.401615] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:07:50 192.168.122.209 [47020.458743] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:07:50 192.168.122.209 [47020.483951] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:07:50 192.168.122.209 [47020.532946] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:07:50 192.168.122.209 [47020.534389] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:07:50 192.168.122.209 [47020.568858] [tempesta fw] Tempesta FW is ready Apr 26 05:07:50 192.168.122.209 [47021.138617] [tdb] Close table 'client0.tdb' Apr 26 05:07:50 192.168.122.209 [47021.336122] [tdb] Close table 'sessions0.tdb' Apr 26 05:07:54 192.168.122.209 [47024.493115] [tdb] Close table 'cache0.tdb' Apr 26 05:07:54 192.168.122.209 [47024.724703] [tdb] Close table 'filter0.tdb' Apr 26 05:07:54 192.168.122.209 [47024.725142] [tempesta fw] modules are stopped Apr 26 05:07:54 192.168.122.209 [47024.918688] [tempesta fw] exiting... Apr 26 05:07:54 192.168.122.209 [47025.022134] [tdb] Shutdown Tempesta DB Apr 26 05:07:54 192.168.122.209 [47025.213106] End test: t_http_rules.test_http_tables.HttpTablesTestMixedChainResp.test Apr 26 05:07:54 192.168.122.209 [47025.224549] Start test: t_http_rules.test_http_tables.HttpTablesTestMultipleCookiesH2.test_cookie_good_prefix Apr 26 05:07:55 192.168.122.209 [47026.373308] [tdb] Start Tempesta DB Apr 26 05:07:56 192.168.122.209 [47026.511058] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:07:58 192.168.122.209 [47028.485605] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47028.485605] Maybe that's fine, but it's worth checking the [47028.485605] config - if there is no relations between the [47028.485605] names, then host name confusion attack is possible. Apr 26 05:07:58 192.168.122.209 [47028.721119] [tempesta fw] Configuration processing is completed. Apr 26 05:07:58 192.168.122.209 [47028.771487] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:07:58 192.168.122.209 [47029.187770] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:07:58 192.168.122.209 [47029.244417] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:07:58 192.168.122.209 [47029.270023] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:07:58 192.168.122.209 [47029.381033] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:07:58 192.168.122.209 [47029.382630] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:07:59 192.168.122.209 [47029.421021] [tempesta fw] Tempesta FW is ready Apr 26 05:07:59 192.168.122.209 [47030.216205] [tdb] Close table 'client0.tdb' Apr 26 05:08:00 192.168.122.209 [47030.405543] [tdb] Close table 'sessions0.tdb' Apr 26 05:08:03 192.168.122.209 [47033.567611] [tdb] Close table 'cache0.tdb' Apr 26 05:08:03 192.168.122.209 [47033.798247] [tdb] Close table 'filter0.tdb' Apr 26 05:08:03 192.168.122.209 [47033.798673] [tempesta fw] modules are stopped Apr 26 05:08:03 192.168.122.209 [47034.089076] [tempesta fw] exiting... Apr 26 05:08:03 192.168.122.209 [47034.244326] [tdb] Shutdown Tempesta DB Apr 26 05:08:04 192.168.122.209 [47034.470557] End test: t_http_rules.test_http_tables.HttpTablesTestMultipleCookiesH2.test_cookie_good_prefix Apr 26 05:08:04 192.168.122.209 [47034.482109] Start test: t_http_rules.test_http_tables.HttpTablesTestMultipleCookiesH2.test_cookie_good_suffix Apr 26 05:08:05 192.168.122.209 [47035.574255] [tdb] Start Tempesta DB Apr 26 05:08:05 192.168.122.209 [47035.705749] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:08:07 192.168.122.209 [47037.653821] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47037.653821] Maybe that's fine, but it's worth checking the [47037.653821] config - if there is no relations between the [47037.653821] names, then host name confusion attack is possible. Apr 26 05:08:07 192.168.122.209 [47037.881266] [tempesta fw] Configuration processing is completed. Apr 26 05:08:07 192.168.122.209 [47037.936887] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:08:07 192.168.122.209 [47038.364050] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:08:07 192.168.122.209 [47038.390290] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:08:08 192.168.122.209 [47038.428261] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:08:08 192.168.122.209 [47038.513177] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:08:08 192.168.122.209 [47038.515010] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:08:08 192.168.122.209 [47038.561173] [tempesta fw] Tempesta FW is ready Apr 26 05:08:08 192.168.122.209 [47039.332046] [tdb] Close table 'client0.tdb' Apr 26 05:08:09 192.168.122.209 [47039.526566] [tdb] Close table 'sessions0.tdb' Apr 26 05:08:12 192.168.122.209 [47042.718935] [tdb] Close table 'cache0.tdb' Apr 26 05:08:12 192.168.122.209 [47042.964191] [tdb] Close table 'filter0.tdb' Apr 26 05:08:12 192.168.122.209 [47042.964644] [tempesta fw] modules are stopped Apr 26 05:08:12 192.168.122.209 [47043.274784] [tempesta fw] exiting... Apr 26 05:08:13 192.168.122.209 [47043.412655] [tdb] Shutdown Tempesta DB Apr 26 05:08:13 192.168.122.209 [47043.632306] End test: t_http_rules.test_http_tables.HttpTablesTestMultipleCookiesH2.test_cookie_good_suffix Apr 26 05:08:13 192.168.122.209 [47043.645510] Start test: t_http_rules.test_http_tables.HttpTablesTestMultipleCookiesH2.test_cookie_no_rules_matched Apr 26 05:08:14 192.168.122.209 [47044.709670] [tdb] Start Tempesta DB Apr 26 05:08:14 192.168.122.209 [47044.854470] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:08:16 192.168.122.209 [47046.814545] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47046.814545] Maybe that's fine, but it's worth checking the [47046.814545] config - if there is no relations between the [47046.814545] names, then host name confusion attack is possible. Apr 26 05:08:16 192.168.122.209 [47047.061278] [tempesta fw] Configuration processing is completed. Apr 26 05:08:16 192.168.122.209 [47047.111547] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:08:17 192.168.122.209 [47047.523892] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:08:17 192.168.122.209 [47047.580230] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:08:17 192.168.122.209 [47047.605722] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:08:17 192.168.122.209 [47047.689277] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:08:17 192.168.122.209 [47047.690666] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:08:17 192.168.122.209 [47047.729268] [tempesta fw] Tempesta FW is ready Apr 26 05:08:18 192.168.122.209 [47048.502234] [tdb] Close table 'client0.tdb' Apr 26 05:08:18 192.168.122.209 [47048.707239] [tdb] Close table 'sessions0.tdb' Apr 26 05:08:21 192.168.122.209 [47051.838059] [tdb] Close table 'cache0.tdb' Apr 26 05:08:21 192.168.122.209 [47052.082004] [tdb] Close table 'filter0.tdb' Apr 26 05:08:21 192.168.122.209 [47052.082426] [tempesta fw] modules are stopped Apr 26 05:08:21 192.168.122.209 [47052.340688] [tempesta fw] exiting... Apr 26 05:08:22 192.168.122.209 [47052.463008] [tdb] Shutdown Tempesta DB Apr 26 05:08:22 192.168.122.209 [47052.684551] End test: t_http_rules.test_http_tables.HttpTablesTestMultipleCookiesH2.test_cookie_no_rules_matched Apr 26 05:08:22 192.168.122.209 [47052.708454] Start test: t_http_rules.test_http_tables.HttpTablesTestMultipleCookiesH2.test_cookie_tempesta_bad Apr 26 05:08:23 192.168.122.209 [47053.773361] [tdb] Start Tempesta DB Apr 26 05:08:23 192.168.122.209 [47053.907556] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:08:25 192.168.122.209 [47055.921841] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47055.921841] Maybe that's fine, but it's worth checking the [47055.921841] config - if there is no relations between the [47055.921841] names, then host name confusion attack is possible. Apr 26 05:08:25 192.168.122.209 [47056.153557] [tempesta fw] Configuration processing is completed. Apr 26 05:08:25 192.168.122.209 [47056.216917] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:08:26 192.168.122.209 [47056.700804] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:08:26 192.168.122.209 [47056.736071] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:08:26 192.168.122.209 [47056.770236] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:08:26 192.168.122.209 [47056.873460] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:08:26 192.168.122.209 [47056.875286] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:08:26 192.168.122.209 [47056.921400] [tempesta fw] Tempesta FW is ready Apr 26 05:08:26 192.168.122.209 [47057.050344] [tempesta fw] Warning: request has been filtered out via http table: 127.0.0.2 Apr 26 05:08:27 192.168.122.209 [47057.678992] [tdb] Close table 'client0.tdb' Apr 26 05:08:27 192.168.122.209 [47057.869803] [tdb] Close table 'sessions0.tdb' Apr 26 05:08:30 192.168.122.209 [47061.025242] [tdb] Close table 'cache0.tdb' Apr 26 05:08:30 192.168.122.209 [47061.236863] [tdb] Close table 'filter0.tdb' Apr 26 05:08:30 192.168.122.209 [47061.237338] [tempesta fw] modules are stopped Apr 26 05:08:31 192.168.122.209 [47061.518264] [tempesta fw] exiting... Apr 26 05:08:31 192.168.122.209 [47061.673338] [tdb] Shutdown Tempesta DB Apr 26 05:08:31 192.168.122.209 [47061.890630] End test: t_http_rules.test_http_tables.HttpTablesTestMultipleCookiesH2.test_cookie_tempesta_bad Apr 26 05:08:31 192.168.122.209 [47061.904140] Start test: t_http_rules.test_http_tables.HttpTablesTestMultipleCookiesH2.test_cookie_tempesta_bad_2 Apr 26 05:08:32 192.168.122.209 [47063.062192] [tdb] Start Tempesta DB Apr 26 05:08:32 192.168.122.209 [47063.196128] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:08:34 192.168.122.209 [47065.155040] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47065.155040] Maybe that's fine, but it's worth checking the [47065.155040] config - if there is no relations between the [47065.155040] names, then host name confusion attack is possible. Apr 26 05:08:35 192.168.122.209 [47065.409492] [tempesta fw] Configuration processing is completed. Apr 26 05:08:35 192.168.122.209 [47065.459073] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:08:35 192.168.122.209 [47065.871857] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:08:35 192.168.122.209 [47065.928586] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:08:35 192.168.122.209 [47065.960165] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:08:35 192.168.122.209 [47066.117525] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:08:35 192.168.122.209 [47066.119324] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:08:35 192.168.122.209 [47066.157502] [tempesta fw] Tempesta FW is ready Apr 26 05:08:35 192.168.122.209 [47066.296107] [tempesta fw] Warning: request has been filtered out via http table: 127.0.0.2 Apr 26 05:08:36 192.168.122.209 [47066.828493] [tdb] Close table 'client0.tdb' Apr 26 05:08:36 192.168.122.209 [47067.028736] [tdb] Close table 'sessions0.tdb' Apr 26 05:08:39 192.168.122.209 [47070.171271] [tdb] Close table 'cache0.tdb' Apr 26 05:08:40 192.168.122.209 [47070.408867] [tdb] Close table 'filter0.tdb' Apr 26 05:08:40 192.168.122.209 [47070.409315] [tempesta fw] modules are stopped Apr 26 05:08:40 192.168.122.209 [47070.666045] [tempesta fw] exiting... Apr 26 05:08:40 192.168.122.209 [47070.784198] [tdb] Shutdown Tempesta DB Apr 26 05:08:40 192.168.122.209 [47071.006477] End test: t_http_rules.test_http_tables.HttpTablesTestMultipleCookiesH2.test_cookie_tempesta_bad_2 Apr 26 05:08:40 192.168.122.209 [47071.019204] Start test: t_http_rules.test_http_tables.HttpTablesTestMultipleCookiesH2.test_cookie_tempesta_good Apr 26 05:08:41 192.168.122.209 [47072.155616] [tdb] Start Tempesta DB Apr 26 05:08:41 192.168.122.209 [47072.298350] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:08:43 192.168.122.209 [47074.302262] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47074.302262] Maybe that's fine, but it's worth checking the [47074.302262] config - if there is no relations between the [47074.302262] names, then host name confusion attack is possible. Apr 26 05:08:44 192.168.122.209 [47074.537767] [tempesta fw] Configuration processing is completed. Apr 26 05:08:44 192.168.122.209 [47074.589117] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:08:44 192.168.122.209 [47074.998296] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:08:44 192.168.122.209 [47075.056177] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:08:44 192.168.122.209 [47075.091171] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:08:44 192.168.122.209 [47075.205596] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:08:44 192.168.122.209 [47075.206810] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:08:44 192.168.122.209 [47075.285593] [tempesta fw] Tempesta FW is ready Apr 26 05:08:45 192.168.122.209 [47076.017609] [tdb] Close table 'client0.tdb' Apr 26 05:08:45 192.168.122.209 [47076.206894] [tdb] Close table 'sessions0.tdb' Apr 26 05:08:48 192.168.122.209 [47079.376961] [tdb] Close table 'cache0.tdb' Apr 26 05:08:49 192.168.122.209 [47079.603961] [tdb] Close table 'filter0.tdb' Apr 26 05:08:49 192.168.122.209 [47079.604392] [tempesta fw] modules are stopped Apr 26 05:08:49 192.168.122.209 [47079.866681] [tempesta fw] exiting... Apr 26 05:08:49 192.168.122.209 [47080.007187] [tdb] Shutdown Tempesta DB Apr 26 05:08:49 192.168.122.209 [47080.206616] End test: t_http_rules.test_http_tables.HttpTablesTestMultipleCookiesH2.test_cookie_tempesta_good Apr 26 05:08:49 192.168.122.209 [47080.223418] Start test: t_http_rules.test_http_tables.HttpTablesTestMultipleCookiesH2.test_cookie_tempesta_good_is_last Apr 26 05:08:51 192.168.122.209 [47081.436410] [tdb] Start Tempesta DB Apr 26 05:08:51 192.168.122.209 [47081.577271] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:08:53 192.168.122.209 [47083.535028] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47083.535028] Maybe that's fine, but it's worth checking the [47083.535028] config - if there is no relations between the [47083.535028] names, then host name confusion attack is possible. Apr 26 05:08:53 192.168.122.209 [47083.773842] [tempesta fw] Configuration processing is completed. Apr 26 05:08:53 192.168.122.209 [47083.826407] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:08:53 192.168.122.209 [47084.257059] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:08:53 192.168.122.209 [47084.283504] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:08:53 192.168.122.209 [47084.317256] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:08:54 192.168.122.209 [47084.429835] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:08:54 192.168.122.209 [47084.431647] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:08:54 192.168.122.209 [47084.485713] [tempesta fw] Tempesta FW is ready Apr 26 05:08:54 192.168.122.209 [47085.275355] [tdb] Close table 'client0.tdb' Apr 26 05:08:55 192.168.122.209 [47085.470741] [tdb] Close table 'sessions0.tdb' Apr 26 05:08:58 192.168.122.209 [47088.638499] [tdb] Close table 'cache0.tdb' Apr 26 05:08:58 192.168.122.209 [47088.878955] [tdb] Close table 'filter0.tdb' Apr 26 05:08:58 192.168.122.209 [47088.879399] [tempesta fw] modules are stopped Apr 26 05:08:58 192.168.122.209 [47089.138836] [tempesta fw] exiting... Apr 26 05:08:58 192.168.122.209 [47089.277040] [tdb] Shutdown Tempesta DB Apr 26 05:08:59 192.168.122.209 [47089.508533] End test: t_http_rules.test_http_tables.HttpTablesTestMultipleCookiesH2.test_cookie_tempesta_good_is_last Apr 26 05:08:59 192.168.122.209 [47089.524046] Start test: t_http_rules.test_http_tables.HttpTablesTestMultipleCookiesHttp.test_cookie_good_prefix Apr 26 05:09:00 192.168.122.209 [47090.608499] [tdb] Start Tempesta DB Apr 26 05:09:00 192.168.122.209 [47090.743881] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:09:02 192.168.122.209 [47092.767202] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47092.767202] Maybe that's fine, but it's worth checking the [47092.767202] config - if there is no relations between the [47092.767202] names, then host name confusion attack is possible. Apr 26 05:09:02 192.168.122.209 [47093.033916] [tempesta fw] Configuration processing is completed. Apr 26 05:09:02 192.168.122.209 [47093.084795] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:09:03 192.168.122.209 [47093.495878] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:09:03 192.168.122.209 [47093.554591] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:09:03 192.168.122.209 [47093.580434] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:09:03 192.168.122.209 [47093.673892] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:09:03 192.168.122.209 [47093.675697] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:09:03 192.168.122.209 [47093.717863] [tempesta fw] Tempesta FW is ready Apr 26 05:09:04 192.168.122.209 [47094.465083] [tdb] Close table 'client0.tdb' Apr 26 05:09:04 192.168.122.209 [47094.662368] [tdb] Close table 'sessions0.tdb' Apr 26 05:09:07 192.168.122.209 [47097.835852] [tdb] Close table 'cache0.tdb' Apr 26 05:09:07 192.168.122.209 [47098.066882] [tdb] Close table 'filter0.tdb' Apr 26 05:09:07 192.168.122.209 [47098.067313] [tempesta fw] modules are stopped Apr 26 05:09:07 192.168.122.209 [47098.330281] [tempesta fw] exiting... Apr 26 05:09:08 192.168.122.209 [47098.483403] [tdb] Shutdown Tempesta DB Apr 26 05:09:08 192.168.122.209 [47098.723196] End test: t_http_rules.test_http_tables.HttpTablesTestMultipleCookiesHttp.test_cookie_good_prefix Apr 26 05:09:08 192.168.122.209 [47098.734500] Start test: t_http_rules.test_http_tables.HttpTablesTestMultipleCookiesHttp.test_cookie_good_suffix Apr 26 05:09:09 192.168.122.209 [47099.906659] [tdb] Start Tempesta DB Apr 26 05:09:09 192.168.122.209 [47100.048721] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:09:11 192.168.122.209 [47102.015352] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47102.015352] Maybe that's fine, but it's worth checking the [47102.015352] config - if there is no relations between the [47102.015352] names, then host name confusion attack is possible. Apr 26 05:09:11 192.168.122.209 [47102.270131] [tempesta fw] Configuration processing is completed. Apr 26 05:09:11 192.168.122.209 [47102.321988] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:09:12 192.168.122.209 [47102.739837] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:09:12 192.168.122.209 [47102.766560] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:09:12 192.168.122.209 [47102.800669] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:09:12 192.168.122.209 [47102.890003] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:09:12 192.168.122.209 [47102.891696] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:09:12 192.168.122.209 [47102.941918] [tempesta fw] Tempesta FW is ready Apr 26 05:09:13 192.168.122.209 [47103.682451] [tdb] Close table 'client0.tdb' Apr 26 05:09:13 192.168.122.209 [47103.882332] [tdb] Close table 'sessions0.tdb' Apr 26 05:09:16 192.168.122.209 [47107.084006] [tdb] Close table 'cache0.tdb' Apr 26 05:09:16 192.168.122.209 [47107.341156] [tdb] Close table 'filter0.tdb' Apr 26 05:09:16 192.168.122.209 [47107.341600] [tempesta fw] modules are stopped Apr 26 05:09:17 192.168.122.209 [47107.572090] [tempesta fw] exiting... Apr 26 05:09:17 192.168.122.209 [47107.701109] [tdb] Shutdown Tempesta DB Apr 26 05:09:17 192.168.122.209 [47107.937307] End test: t_http_rules.test_http_tables.HttpTablesTestMultipleCookiesHttp.test_cookie_good_suffix Apr 26 05:09:17 192.168.122.209 [47107.948878] Start test: t_http_rules.test_http_tables.HttpTablesTestMultipleCookiesHttp.test_cookie_no_rules_matched Apr 26 05:09:18 192.168.122.209 [47109.119615] [tdb] Start Tempesta DB Apr 26 05:09:18 192.168.122.209 [47109.265958] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:09:20 192.168.122.209 [47111.183373] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47111.183373] Maybe that's fine, but it's worth checking the [47111.183373] config - if there is no relations between the [47111.183373] names, then host name confusion attack is possible. Apr 26 05:09:21 192.168.122.209 [47111.458135] [tempesta fw] Configuration processing is completed. Apr 26 05:09:21 192.168.122.209 [47111.513605] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:09:21 192.168.122.209 [47111.926775] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:09:21 192.168.122.209 [47111.984492] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:09:21 192.168.122.209 [47112.010579] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:09:21 192.168.122.209 [47112.086130] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:09:21 192.168.122.209 [47112.087569] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:09:21 192.168.122.209 [47112.126062] [tempesta fw] Tempesta FW is ready Apr 26 05:09:22 192.168.122.209 [47112.903533] [tdb] Close table 'client0.tdb' Apr 26 05:09:22 192.168.122.209 [47113.104303] [tdb] Close table 'sessions0.tdb' Apr 26 05:09:25 192.168.122.209 [47116.251403] [tdb] Close table 'cache0.tdb' Apr 26 05:09:26 192.168.122.209 [47116.474610] [tdb] Close table 'filter0.tdb' Apr 26 05:09:26 192.168.122.209 [47116.475058] [tempesta fw] modules are stopped Apr 26 05:09:26 192.168.122.209 [47116.733599] [tempesta fw] exiting... Apr 26 05:09:26 192.168.122.209 [47116.846156] [tdb] Shutdown Tempesta DB Apr 26 05:09:26 192.168.122.209 [47117.043906] End test: t_http_rules.test_http_tables.HttpTablesTestMultipleCookiesHttp.test_cookie_no_rules_matched Apr 26 05:09:26 192.168.122.209 [47117.071236] Start test: t_http_rules.test_http_tables.HttpTablesTestMultipleCookiesHttp.test_cookie_tempesta_bad Apr 26 05:09:27 192.168.122.209 [47118.217047] [tdb] Start Tempesta DB Apr 26 05:09:27 192.168.122.209 [47118.362370] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:09:29 192.168.122.209 [47120.267226] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47120.267226] Maybe that's fine, but it's worth checking the [47120.267226] config - if there is no relations between the [47120.267226] names, then host name confusion attack is possible. Apr 26 05:09:30 192.168.122.209 [47120.502299] [tempesta fw] Configuration processing is completed. Apr 26 05:09:30 192.168.122.209 [47120.554311] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:09:30 192.168.122.209 [47120.999341] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:09:30 192.168.122.209 [47121.026534] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:09:30 192.168.122.209 [47121.061803] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:09:30 192.168.122.209 [47121.150187] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:09:30 192.168.122.209 [47121.151501] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:09:30 192.168.122.209 [47121.194120] [tempesta fw] Tempesta FW is ready Apr 26 05:09:30 192.168.122.209 [47121.323291] [tempesta fw] Warning: request has been filtered out via http table: 127.0.0.2 Apr 26 05:09:31 192.168.122.209 [47121.936946] [tdb] Close table 'client0.tdb' Apr 26 05:09:31 192.168.122.209 [47122.127632] [tdb] Close table 'sessions0.tdb' Apr 26 05:09:34 192.168.122.209 [47125.289444] [tdb] Close table 'cache0.tdb' Apr 26 05:09:35 192.168.122.209 [47125.503507] [tdb] Close table 'filter0.tdb' Apr 26 05:09:35 192.168.122.209 [47125.503950] [tempesta fw] modules are stopped Apr 26 05:09:35 192.168.122.209 [47125.785846] [tempesta fw] exiting... Apr 26 05:09:35 192.168.122.209 [47125.917679] [tdb] Shutdown Tempesta DB Apr 26 05:09:35 192.168.122.209 [47126.119332] End test: t_http_rules.test_http_tables.HttpTablesTestMultipleCookiesHttp.test_cookie_tempesta_bad Apr 26 05:09:35 192.168.122.209 [47126.134323] Start test: t_http_rules.test_http_tables.HttpTablesTestMultipleCookiesHttp.test_cookie_tempesta_bad_2 Apr 26 05:09:36 192.168.122.209 [47127.264217] [tdb] Start Tempesta DB Apr 26 05:09:37 192.168.122.209 [47127.402330] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:09:38 192.168.122.209 [47129.303692] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47129.303692] Maybe that's fine, but it's worth checking the [47129.303692] config - if there is no relations between the [47129.303692] names, then host name confusion attack is possible. Apr 26 05:09:39 192.168.122.209 [47129.578283] [tempesta fw] Configuration processing is completed. Apr 26 05:09:39 192.168.122.209 [47129.629783] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:09:39 192.168.122.209 [47130.040735] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:09:39 192.168.122.209 [47130.097895] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:09:39 192.168.122.209 [47130.123166] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:09:39 192.168.122.209 [47130.210336] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:09:39 192.168.122.209 [47130.212024] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:09:39 192.168.122.209 [47130.278299] [tempesta fw] Tempesta FW is ready Apr 26 05:09:40 192.168.122.209 [47130.418475] [tempesta fw] Warning: request has been filtered out via http table: 127.0.0.2 Apr 26 05:09:40 192.168.122.209 [47131.035080] [tdb] Close table 'client0.tdb' Apr 26 05:09:40 192.168.122.209 [47131.222898] [tdb] Close table 'sessions0.tdb' Apr 26 05:09:44 192.168.122.209 [47134.402441] [tdb] Close table 'cache0.tdb' Apr 26 05:09:44 192.168.122.209 [47134.629630] [tdb] Close table 'filter0.tdb' Apr 26 05:09:44 192.168.122.209 [47134.630269] [tempesta fw] modules are stopped Apr 26 05:09:44 192.168.122.209 [47134.894762] [tempesta fw] exiting... Apr 26 05:09:44 192.168.122.209 [47135.040011] [tdb] Shutdown Tempesta DB Apr 26 05:09:44 192.168.122.209 [47135.217618] End test: t_http_rules.test_http_tables.HttpTablesTestMultipleCookiesHttp.test_cookie_tempesta_bad_2 Apr 26 05:09:44 192.168.122.209 [47135.243238] Start test: t_http_rules.test_http_tables.HttpTablesTestMultipleCookiesHttp.test_cookie_tempesta_good Apr 26 05:09:45 192.168.122.209 [47136.356105] [tdb] Start Tempesta DB Apr 26 05:09:46 192.168.122.209 [47136.498279] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:09:47 192.168.122.209 [47138.379352] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47138.379352] Maybe that's fine, but it's worth checking the [47138.379352] config - if there is no relations between the [47138.379352] names, then host name confusion attack is possible. Apr 26 05:09:48 192.168.122.209 [47138.614540] [tempesta fw] Configuration processing is completed. Apr 26 05:09:48 192.168.122.209 [47138.665381] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:09:48 192.168.122.209 [47139.091886] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:09:48 192.168.122.209 [47139.152381] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:09:48 192.168.122.209 [47139.177991] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:09:48 192.168.122.209 [47139.262459] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:09:48 192.168.122.209 [47139.264142] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:09:48 192.168.122.209 [47139.314406] [tempesta fw] Tempesta FW is ready Apr 26 05:09:49 192.168.122.209 [47140.087201] [tdb] Close table 'client0.tdb' Apr 26 05:09:49 192.168.122.209 [47140.259078] [tdb] Close table 'sessions0.tdb' Apr 26 05:09:53 192.168.122.209 [47143.442422] [tdb] Close table 'cache0.tdb' Apr 26 05:09:53 192.168.122.209 [47143.695635] [tdb] Close table 'filter0.tdb' Apr 26 05:09:53 192.168.122.209 [47143.696081] [tempesta fw] modules are stopped Apr 26 05:09:53 192.168.122.209 [47143.978709] [tempesta fw] exiting... Apr 26 05:09:53 192.168.122.209 [47144.121008] [tdb] Shutdown Tempesta DB Apr 26 05:09:53 192.168.122.209 [47144.349371] End test: t_http_rules.test_http_tables.HttpTablesTestMultipleCookiesHttp.test_cookie_tempesta_good Apr 26 05:09:53 192.168.122.209 [47144.361514] Start test: t_http_rules.test_http_tables.HttpTablesTestMultipleCookiesHttp.test_cookie_tempesta_good_is_last Apr 26 05:09:55 192.168.122.209 [47145.468393] [tdb] Start Tempesta DB Apr 26 05:09:55 192.168.122.209 [47145.610617] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:09:57 192.168.122.209 [47147.490999] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47147.490999] Maybe that's fine, but it's worth checking the [47147.490999] config - if there is no relations between the [47147.490999] names, then host name confusion attack is possible. Apr 26 05:09:57 192.168.122.209 [47147.730635] [tempesta fw] Configuration processing is completed. Apr 26 05:09:57 192.168.122.209 [47147.781996] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:09:57 192.168.122.209 [47148.207472] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:09:57 192.168.122.209 [47148.234058] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:09:57 192.168.122.209 [47148.268907] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:09:57 192.168.122.209 [47148.366540] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:09:57 192.168.122.209 [47148.367690] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:09:58 192.168.122.209 [47148.450540] [tempesta fw] Tempesta FW is ready Apr 26 05:09:58 192.168.122.209 [47149.178488] [tdb] Close table 'client0.tdb' Apr 26 05:09:58 192.168.122.209 [47149.375634] [tdb] Close table 'sessions0.tdb' Apr 26 05:10:02 192.168.122.209 [47152.575781] [tdb] Close table 'cache0.tdb' Apr 26 05:10:02 192.168.122.209 [47152.815436] [tdb] Close table 'filter0.tdb' Apr 26 05:10:02 192.168.122.209 [47152.815877] [tempesta fw] modules are stopped Apr 26 05:10:02 192.168.122.209 [47153.101076] [tempesta fw] exiting... Apr 26 05:10:02 192.168.122.209 [47153.249013] [tdb] Shutdown Tempesta DB Apr 26 05:10:03 192.168.122.209 [47153.450054] End test: t_http_rules.test_http_tables.HttpTablesTestMultipleCookiesHttp.test_cookie_tempesta_good_is_last Apr 26 05:10:03 192.168.122.209 [47153.475396] Start test: t_http_rules.test_match_duplicated_headers.DuplicatedHeadersMatchTest.test_match_fail Apr 26 05:10:04 192.168.122.209 [47154.472631] [tdb] Start Tempesta DB Apr 26 05:10:04 192.168.122.209 [47154.602671] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:10:05 192.168.122.209 [47156.131723] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47156.131723] Maybe that's fine, but it's worth checking the [47156.131723] config - if there is no relations between the [47156.131723] names, then host name confusion attack is possible. Apr 26 05:10:05 192.168.122.209 [47156.294770] [tempesta fw] Configuration processing is completed. Apr 26 05:10:05 192.168.122.209 [47156.349710] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:10:06 192.168.122.209 [47156.772071] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:10:06 192.168.122.209 [47156.829001] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:10:06 192.168.122.209 [47156.855965] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:10:06 192.168.122.209 [47156.898636] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:10:06 192.168.122.209 [47156.899690] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:10:06 192.168.122.209 [47156.938629] [tempesta fw] Tempesta FW is ready Apr 26 05:10:06 192.168.122.209 [47157.068721] [tempesta fw] Warning: request has been filtered out via http table: 127.0.0.2 Apr 26 05:10:07 192.168.122.209 [47157.552177] [tdb] Close table 'client0.tdb' Apr 26 05:10:07 192.168.122.209 [47157.755310] [tdb] Close table 'sessions0.tdb' Apr 26 05:10:10 192.168.122.209 [47161.020297] [tdb] Close table 'cache0.tdb' Apr 26 05:10:10 192.168.122.209 [47161.256105] [tdb] Close table 'filter0.tdb' Apr 26 05:10:10 192.168.122.209 [47161.256542] [tempesta fw] modules are stopped Apr 26 05:10:11 192.168.122.209 [47161.462421] [tempesta fw] exiting... Apr 26 05:10:11 192.168.122.209 [47161.597814] [tdb] Shutdown Tempesta DB Apr 26 05:10:11 192.168.122.209 [47161.806149] End test: t_http_rules.test_match_duplicated_headers.DuplicatedHeadersMatchTest.test_match_fail Apr 26 05:10:11 192.168.122.209 [47161.816086] Start test: t_http_rules.test_match_duplicated_headers.DuplicatedHeadersMatchTest.test_match_success Apr 26 05:10:12 192.168.122.209 [47162.958168] [tdb] Start Tempesta DB Apr 26 05:10:12 192.168.122.209 [47163.087065] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:10:14 192.168.122.209 [47164.676074] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47164.676074] Maybe that's fine, but it's worth checking the [47164.676074] config - if there is no relations between the [47164.676074] names, then host name confusion attack is possible. Apr 26 05:10:14 192.168.122.209 [47164.846969] [tempesta fw] Configuration processing is completed. Apr 26 05:10:14 192.168.122.209 [47164.898899] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:10:14 192.168.122.209 [47165.327141] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:10:14 192.168.122.209 [47165.354649] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:10:14 192.168.122.209 [47165.389834] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:10:15 192.168.122.209 [47165.514813] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:10:15 192.168.122.209 [47165.516542] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:10:15 192.168.122.209 [47165.562693] [tempesta fw] Tempesta FW is ready Apr 26 05:10:15 192.168.122.209 [47166.156930] [tdb] Close table 'client0.tdb' Apr 26 05:10:15 192.168.122.209 [47166.344522] [tdb] Close table 'sessions0.tdb' Apr 26 05:10:19 192.168.122.209 [47169.534219] [tdb] Close table 'cache0.tdb' Apr 26 05:10:19 192.168.122.209 [47169.762546] [tdb] Close table 'filter0.tdb' Apr 26 05:10:19 192.168.122.209 [47169.763350] [tempesta fw] modules are stopped Apr 26 05:10:19 192.168.122.209 [47169.966843] [tempesta fw] exiting... Apr 26 05:10:19 192.168.122.209 [47170.115975] [tdb] Shutdown Tempesta DB Apr 26 05:10:19 192.168.122.209 [47170.359849] End test: t_http_rules.test_match_duplicated_headers.DuplicatedHeadersMatchTest.test_match_success Apr 26 05:10:19 192.168.122.209 [47170.371320] Start test: t_ipv6.test_ipv6.TestIPv6H2.test_ipv4_to_ipv6 Apr 26 05:10:21 192.168.122.209 [47171.532605] [tdb] Start Tempesta DB Apr 26 05:10:21 192.168.122.209 [47171.674541] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:10:23 192.168.122.209 [47173.444208] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47173.444208] Maybe that's fine, but it's worth checking the [47173.444208] config - if there is no relations between the [47173.444208] names, then host name confusion attack is possible. Apr 26 05:10:23 192.168.122.209 [47173.574858] [tempesta fw] Configuration processing is completed. Apr 26 05:10:23 192.168.122.209 [47173.625120] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:10:23 192.168.122.209 [47174.040092] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:10:23 192.168.122.209 [47174.096418] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:10:23 192.168.122.209 [47174.121737] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:10:23 192.168.122.209 [47174.206873] [tempesta fw] Open listen socket on: [::1]:443 Apr 26 05:10:23 192.168.122.209 [47174.208049] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 05:10:23 192.168.122.209 [47174.262880] [tempesta fw] Tempesta FW is ready Apr 26 05:10:24 192.168.122.209 [47174.940405] [tdb] Close table 'client0.tdb' Apr 26 05:10:24 192.168.122.209 [47175.131729] [tdb] Close table 'sessions0.tdb' Apr 26 05:10:27 192.168.122.209 [47178.259271] [tdb] Close table 'cache0.tdb' Apr 26 05:10:28 192.168.122.209 [47178.520395] [tdb] Close table 'filter0.tdb' Apr 26 05:10:28 192.168.122.209 [47178.520847] [tempesta fw] modules are stopped Apr 26 05:10:28 192.168.122.209 [47178.735229] [tempesta fw] exiting... Apr 26 05:10:28 192.168.122.209 [47178.904330] [tdb] Shutdown Tempesta DB Apr 26 05:10:28 192.168.122.209 [47179.140254] End test: t_ipv6.test_ipv6.TestIPv6H2.test_ipv4_to_ipv6 Apr 26 05:10:28 192.168.122.209 [47179.151056] Start test: t_ipv6.test_ipv6.TestIPv6H2.test_ipv6_to_ipv4 Apr 26 05:10:29 192.168.122.209 [47180.328802] [tdb] Start Tempesta DB Apr 26 05:10:30 192.168.122.209 [47180.478802] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:10:31 192.168.122.209 [47182.353116] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47182.353116] Maybe that's fine, but it's worth checking the [47182.353116] config - if there is no relations between the [47182.353116] names, then host name confusion attack is possible. Apr 26 05:10:32 192.168.122.209 [47182.475042] [tempesta fw] Configuration processing is completed. Apr 26 05:10:32 192.168.122.209 [47182.527802] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:10:32 192.168.122.209 [47182.970423] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:10:32 192.168.122.209 [47182.999700] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:10:32 192.168.122.209 [47183.038234] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:10:32 192.168.122.209 [47183.107042] [tempesta fw] Open listen socket on: [::1]:443 Apr 26 05:10:32 192.168.122.209 [47183.108477] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 05:10:32 192.168.122.209 [47183.146991] [tempesta fw] Tempesta FW is ready Apr 26 05:10:33 192.168.122.209 [47183.879379] [tdb] Close table 'client0.tdb' Apr 26 05:10:33 192.168.122.209 [47184.085984] [tdb] Close table 'sessions0.tdb' Apr 26 05:10:36 192.168.122.209 [47187.365062] [tdb] Close table 'cache0.tdb' Apr 26 05:10:37 192.168.122.209 [47187.596333] [tdb] Close table 'filter0.tdb' Apr 26 05:10:37 192.168.122.209 [47187.596775] [tempesta fw] modules are stopped Apr 26 05:10:37 192.168.122.209 [47187.854546] [tempesta fw] exiting... Apr 26 05:10:37 192.168.122.209 [47187.983261] [tdb] Shutdown Tempesta DB Apr 26 05:10:37 192.168.122.209 [47188.185606] End test: t_ipv6.test_ipv6.TestIPv6H2.test_ipv6_to_ipv4 Apr 26 05:10:37 192.168.122.209 [47188.196491] Start test: t_ipv6.test_ipv6.TestIPv6H2.test_ipv6_to_ipv6 Apr 26 05:10:38 192.168.122.209 [47189.314729] [tdb] Start Tempesta DB Apr 26 05:10:39 192.168.122.209 [47189.479025] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:10:40 192.168.122.209 [47191.272559] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47191.272559] Maybe that's fine, but it's worth checking the [47191.272559] config - if there is no relations between the [47191.272559] names, then host name confusion attack is possible. Apr 26 05:10:40 192.168.122.209 [47191.387180] [tempesta fw] Configuration processing is completed. Apr 26 05:10:41 192.168.122.209 [47191.439484] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:10:41 192.168.122.209 [47191.912130] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:10:41 192.168.122.209 [47191.975004] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:10:41 192.168.122.209 [47192.004064] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:10:41 192.168.122.209 [47192.127126] [tempesta fw] Open listen socket on: [::1]:443 Apr 26 05:10:41 192.168.122.209 [47192.128877] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 05:10:41 192.168.122.209 [47192.171058] [tempesta fw] Tempesta FW is ready Apr 26 05:10:42 192.168.122.209 [47192.856557] [tdb] Close table 'client0.tdb' Apr 26 05:10:42 192.168.122.209 [47193.022070] [tdb] Close table 'sessions0.tdb' Apr 26 05:10:45 192.168.122.209 [47196.317844] [tdb] Close table 'cache0.tdb' Apr 26 05:10:46 192.168.122.209 [47196.551723] [tdb] Close table 'filter0.tdb' Apr 26 05:10:46 192.168.122.209 [47196.552153] [tempesta fw] modules are stopped Apr 26 05:10:46 192.168.122.209 [47196.841721] [tempesta fw] exiting... Apr 26 05:10:46 192.168.122.209 [47196.987677] [tdb] Shutdown Tempesta DB Apr 26 05:10:46 192.168.122.209 [47197.215040] End test: t_ipv6.test_ipv6.TestIPv6H2.test_ipv6_to_ipv6 Apr 26 05:10:46 192.168.122.209 [47197.226396] Start test: t_ipv6.test_ipv6.TestIPv6Https.test_ipv4_to_ipv6 Apr 26 05:10:47 192.168.122.209 [47198.357756] [tdb] Start Tempesta DB Apr 26 05:10:48 192.168.122.209 [47198.514470] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:10:49 192.168.122.209 [47200.252739] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47200.252739] Maybe that's fine, but it's worth checking the [47200.252739] config - if there is no relations between the [47200.252739] names, then host name confusion attack is possible. Apr 26 05:10:49 192.168.122.209 [47200.383285] [tempesta fw] Configuration processing is completed. Apr 26 05:10:50 192.168.122.209 [47200.434060] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:10:50 192.168.122.209 [47200.858703] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:10:50 192.168.122.209 [47200.915246] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:10:50 192.168.122.209 [47200.948926] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:10:50 192.168.122.209 [47201.016242] [tempesta fw] Open listen socket on: [::1]:443 Apr 26 05:10:50 192.168.122.209 [47201.019402] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 05:10:50 192.168.122.209 [47201.055185] [tempesta fw] Tempesta FW is ready Apr 26 05:10:51 192.168.122.209 [47201.712489] [tdb] Close table 'client0.tdb' Apr 26 05:10:51 192.168.122.209 [47201.910461] [tdb] Close table 'sessions0.tdb' Apr 26 05:10:54 192.168.122.209 [47205.147907] [tdb] Close table 'cache0.tdb' Apr 26 05:10:55 192.168.122.209 [47205.401123] [tdb] Close table 'filter0.tdb' Apr 26 05:10:55 192.168.122.209 [47205.401561] [tempesta fw] modules are stopped Apr 26 05:10:55 192.168.122.209 [47205.648783] [tempesta fw] exiting... Apr 26 05:10:55 192.168.122.209 [47205.760913] [tdb] Shutdown Tempesta DB Apr 26 05:10:55 192.168.122.209 [47205.981419] End test: t_ipv6.test_ipv6.TestIPv6Https.test_ipv4_to_ipv6 Apr 26 05:10:55 192.168.122.209 [47205.988828] Start test: t_ipv6.test_ipv6.TestIPv6Https.test_ipv6_to_ipv4 Apr 26 05:10:56 192.168.122.209 [47207.155853] [tdb] Start Tempesta DB Apr 26 05:10:56 192.168.122.209 [47207.296458] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:10:58 192.168.122.209 [47209.056693] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47209.056693] Maybe that's fine, but it's worth checking the [47209.056693] config - if there is no relations between the [47209.056693] names, then host name confusion attack is possible. Apr 26 05:10:58 192.168.122.209 [47209.191405] [tempesta fw] Configuration processing is completed. Apr 26 05:10:58 192.168.122.209 [47209.247984] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:10:59 192.168.122.209 [47209.703949] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:10:59 192.168.122.209 [47209.730762] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:10:59 192.168.122.209 [47209.758551] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:10:59 192.168.122.209 [47209.819313] [tempesta fw] Open listen socket on: [::1]:443 Apr 26 05:10:59 192.168.122.209 [47209.820482] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 05:10:59 192.168.122.209 [47209.863238] [tempesta fw] Tempesta FW is ready Apr 26 05:11:00 192.168.122.209 [47210.537662] [tdb] Close table 'client0.tdb' Apr 26 05:11:00 192.168.122.209 [47210.724900] [tdb] Close table 'sessions0.tdb' Apr 26 05:11:03 192.168.122.209 [47213.946804] [tdb] Close table 'cache0.tdb' Apr 26 05:11:03 192.168.122.209 [47214.167900] [tdb] Close table 'filter0.tdb' Apr 26 05:11:03 192.168.122.209 [47214.168338] [tempesta fw] modules are stopped Apr 26 05:11:04 192.168.122.209 [47214.457515] [tempesta fw] exiting... Apr 26 05:11:04 192.168.122.209 [47214.625466] [tdb] Shutdown Tempesta DB Apr 26 05:11:04 192.168.122.209 [47214.872190] End test: t_ipv6.test_ipv6.TestIPv6Https.test_ipv6_to_ipv4 Apr 26 05:11:04 192.168.122.209 [47214.887830] Start test: t_ipv6.test_ipv6.TestIPv6Https.test_ipv6_to_ipv6 Apr 26 05:11:05 192.168.122.209 [47215.983482] [tdb] Start Tempesta DB Apr 26 05:11:05 192.168.122.209 [47216.115804] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:11:07 192.168.122.209 [47217.848888] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47217.848888] Maybe that's fine, but it's worth checking the [47217.848888] config - if there is no relations between the [47217.848888] names, then host name confusion attack is possible. Apr 26 05:11:07 192.168.122.209 [47217.979477] [tempesta fw] Configuration processing is completed. Apr 26 05:11:07 192.168.122.209 [47218.032655] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:11:08 192.168.122.209 [47218.459119] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:11:08 192.168.122.209 [47218.486108] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:11:08 192.168.122.209 [47218.513249] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:11:08 192.168.122.209 [47218.591436] [tempesta fw] Open listen socket on: [::1]:443 Apr 26 05:11:08 192.168.122.209 [47218.593175] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 05:11:08 192.168.122.209 [47218.643390] [tempesta fw] Tempesta FW is ready Apr 26 05:11:08 192.168.122.209 [47219.267061] [tdb] Close table 'client0.tdb' Apr 26 05:11:09 192.168.122.209 [47219.450055] [tdb] Close table 'sessions0.tdb' Apr 26 05:11:12 192.168.122.209 [47222.592435] [tdb] Close table 'cache0.tdb' Apr 26 05:11:12 192.168.122.209 [47222.833462] [tdb] Close table 'filter0.tdb' Apr 26 05:11:12 192.168.122.209 [47222.833899] [tempesta fw] modules are stopped Apr 26 05:11:12 192.168.122.209 [47223.139987] [tempesta fw] exiting... Apr 26 05:11:12 192.168.122.209 [47223.275969] [tdb] Shutdown Tempesta DB Apr 26 05:11:13 192.168.122.209 [47223.504933] End test: t_ipv6.test_ipv6.TestIPv6Https.test_ipv6_to_ipv6 Apr 26 05:11:13 192.168.122.209 [47223.519763] Start test: t_ja5.test_ja5_filters.TestConfigJa5hInvalidTableSize.test_config Apr 26 05:11:14 192.168.122.209 [47224.665678] [tdb] Start Tempesta DB Apr 26 05:11:14 192.168.122.209 [47224.812523] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:11:16 192.168.122.209 [47226.504940] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47226.504940] Maybe that's fine, but it's worth checking the [47226.504940] config - if there is no relations between the [47226.504940] names, then host name confusion attack is possible. Apr 26 05:11:16 192.168.122.209 [47226.667587] [tempesta fw] Configuration processing is completed. Apr 26 05:11:16 192.168.122.209 [47226.683484] [tdb] ERROR: Bad table size: 500 Apr 26 05:11:16 192.168.122.209 [47226.684708] [tempesta fw] ERROR: Unable to start module 'http': -12 Apr 26 05:11:16 192.168.122.209 [47226.686455] [tempesta fw] modules are stopped Apr 26 05:11:16 192.168.122.209 [47226.687823] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 05:11:16 192.168.122.209 [47227.076195] [tempesta fw] exiting... Apr 26 05:11:16 192.168.122.209 [47227.217527] [tdb] Shutdown Tempesta DB Apr 26 05:11:17 192.168.122.209 [47227.664862] End test: t_ja5.test_ja5_filters.TestConfigJa5hInvalidTableSize.test_config Apr 26 05:11:17 192.168.122.209 [47227.674700] Start test: t_ja5.test_ja5_filters.TestConfigJa5hInvalidValue.test_config Apr 26 05:11:18 192.168.122.209 [47228.790814] [tdb] Start Tempesta DB Apr 26 05:11:18 192.168.122.209 [47228.929655] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:11:19 192.168.122.209 [47229.616856] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47229.616856] Maybe that's fine, but it's worth checking the [47229.616856] config - if there is no relations between the [47229.616856] names, then host name confusion attack is possible. Apr 26 05:11:19 192.168.122.209 [47229.679918] [tempesta fw] ERROR: Failed to parse hash entry in ja5 section: invalid hash value invalid_hash Apr 26 05:11:19 192.168.122.209 [47229.679930] [tempesta fw] ERROR: configuration parsing error: [47229.679930] 10: ja5h {hash invalid_hash 5 5;} [47229.679930] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 05:11:19 192.168.122.209 [47229.687006] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 05:11:19 192.168.122.209 [47229.881336] [tempesta fw] exiting... Apr 26 05:11:19 192.168.122.209 [47229.994708] [tdb] Shutdown Tempesta DB Apr 26 05:11:20 192.168.122.209 [47230.441370] End test: t_ja5.test_ja5_filters.TestConfigJa5hInvalidValue.test_config Apr 26 05:11:20 192.168.122.209 [47230.460863] Start test: t_ja5.test_ja5_filters.TestConfigJa5tInvalidTableSize.test_config Apr 26 05:11:21 192.168.122.209 [47231.514214] [tdb] Start Tempesta DB Apr 26 05:11:21 192.168.122.209 [47231.665656] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:11:21 192.168.122.209 [47232.316677] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47232.316677] Maybe that's fine, but it's worth checking the [47232.316677] config - if there is no relations between the [47232.316677] names, then host name confusion attack is possible. Apr 26 05:11:22 192.168.122.209 [47232.471650] [tempesta fw] Configuration processing is completed. Apr 26 05:11:22 192.168.122.209 [47232.487560] [tdb] ERROR: Bad table size: 500 Apr 26 05:11:22 192.168.122.209 [47232.488841] [tempesta fw] ERROR: Unable to start module 'tls': -12 Apr 26 05:11:22 192.168.122.209 [47232.490537] [tempesta fw] modules are stopped Apr 26 05:11:22 192.168.122.209 [47232.491813] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 05:11:22 192.168.122.209 [47232.853456] [tempesta fw] exiting... Apr 26 05:11:22 192.168.122.209 [47232.975271] [tdb] Shutdown Tempesta DB Apr 26 05:11:23 192.168.122.209 [47233.401246] End test: t_ja5.test_ja5_filters.TestConfigJa5tInvalidTableSize.test_config Apr 26 05:11:23 192.168.122.209 [47233.417116] Start test: t_ja5.test_ja5_filters.TestConfigJa5tInvalidValue.test_config Apr 26 05:11:24 192.168.122.209 [47234.479589] [tdb] Start Tempesta DB Apr 26 05:11:24 192.168.122.209 [47234.609874] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:11:24 192.168.122.209 [47235.228969] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47235.228969] Maybe that's fine, but it's worth checking the [47235.228969] config - if there is no relations between the [47235.228969] names, then host name confusion attack is possible. Apr 26 05:11:24 192.168.122.209 [47235.291985] [tempesta fw] ERROR: Failed to parse hash entry in ja5 section: invalid hash value invalid_hash Apr 26 05:11:24 192.168.122.209 [47235.291997] [tempesta fw] ERROR: configuration parsing error: [47235.291997] 10: ja5t {hash invalid_hash 5 5;} [47235.291997] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 05:11:24 192.168.122.209 [47235.299166] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 05:11:25 192.168.122.209 [47235.489404] [tempesta fw] exiting... Apr 26 05:11:25 192.168.122.209 [47235.606806] [tdb] Shutdown Tempesta DB Apr 26 05:11:25 192.168.122.209 [47235.999805] End test: t_ja5.test_ja5_filters.TestConfigJa5tInvalidValue.test_config Apr 26 05:11:25 192.168.122.209 [47236.017439] Start test: t_ja5.test_ja5_filters.TestJa5FiltersTestSuiteCiphers.test_ja5_hash_difference Apr 26 05:11:26 192.168.122.209 [47237.093989] [tdb] Start Tempesta DB Apr 26 05:11:26 192.168.122.209 [47237.235200] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:11:27 192.168.122.209 [47238.045066] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47238.045066] Maybe that's fine, but it's worth checking the [47238.045066] config - if there is no relations between the [47238.045066] names, then host name confusion attack is possible. Apr 26 05:11:27 192.168.122.209 [47238.275664] [tempesta fw] Configuration processing is completed. Apr 26 05:11:28 192.168.122.209 [47238.435916] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 05:11:28 192.168.122.209 [47238.569800] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000003038fc3d Apr 26 05:11:28 192.168.122.209 [47238.609806] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000d11db51e Apr 26 05:11:28 192.168.122.209 [47239.218963] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6070ba4 Apr 26 05:11:28 192.168.122.209 [47239.277541] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000a968d47d Apr 26 05:11:28 192.168.122.209 [47239.337496] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000007aec66b3 Apr 26 05:11:28 192.168.122.209 [47239.395629] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:11:29 192.168.122.209 [47239.435650] [tempesta fw] Tempesta FW is ready Apr 26 05:11:33 192.168.122.209 [47244.243766] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=1271f8cc2c4c0011" "ja5h=65636588000c0180" Apr 26 05:11:34 192.168.122.209 [47244.411888] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=1271f8cc2c4c0011" "ja5h=65636588000c0180" Apr 26 05:11:34 192.168.122.209 [47244.590417] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=1271f8cc2c570011" "ja5h=65636588000c0180" Apr 26 05:11:34 192.168.122.209 [47244.765220] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=1271f8cc2c570011" "ja5h=65636588000c0180" Apr 26 05:11:34 192.168.122.209 [47245.386932] [tdb] Close table 'client0.tdb' Apr 26 05:11:35 192.168.122.209 [47245.572110] [tdb] Close table 'sessions0.tdb' Apr 26 05:11:38 192.168.122.209 [47248.714728] [tdb] Close table 'cache0.tdb' Apr 26 05:11:38 192.168.122.209 [47248.974029] [tdb] Close table 'filter0.tdb' Apr 26 05:11:39 192.168.122.209 [47249.652271] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 05:11:39 192.168.122.209 [47249.652728] [tempesta fw] modules are stopped Apr 26 05:11:39 192.168.122.209 [47249.971363] [tempesta fw] exiting... Apr 26 05:11:40 192.168.122.209 [47250.832845] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 05:11:40 192.168.122.209 [47250.886309] [tdb] Shutdown Tempesta DB Apr 26 05:11:41 192.168.122.209 [47252.036496] [tdb] Start Tempesta DB Apr 26 05:11:41 192.168.122.209 [47252.183746] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:11:43 192.168.122.209 [47254.125193] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47254.125193] Maybe that's fine, but it's worth checking the [47254.125193] config - if there is no relations between the [47254.125193] names, then host name confusion attack is possible. Apr 26 05:11:43 192.168.122.209 [47254.340028] [tempesta fw] Configuration processing is completed. Apr 26 05:11:44 192.168.122.209 [47254.455426] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 05:11:44 192.168.122.209 [47254.539435] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000003038fc3d Apr 26 05:11:44 192.168.122.209 [47254.566543] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000d11db51e Apr 26 05:11:44 192.168.122.209 [47254.971579] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6070ba4 Apr 26 05:11:44 192.168.122.209 [47255.011959] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000a968d47d Apr 26 05:11:44 192.168.122.209 [47255.044858] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000007aec66b3 Apr 26 05:11:44 192.168.122.209 [47255.203893] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:11:44 192.168.122.209 [47255.299854] [tempesta fw] Tempesta FW is ready Apr 26 05:11:45 192.168.122.209 [47255.426356] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=1271f8cc2c4c0011" "ja5h=65636588000c0180" Apr 26 05:11:45 192.168.122.209 [47255.436226] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=1271f8cc2c570011" "ja5h=65636588000c0180" Apr 26 05:11:45 192.168.122.209 [47255.445625] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=1271f8cc2c570011" "ja5h=65636588000c0180" Apr 26 05:11:45 192.168.122.209 [47255.956636] [tdb] Close table 'client0.tdb' Apr 26 05:11:45 192.168.122.209 [47256.156434] [tdb] Close table 'sessions0.tdb' Apr 26 05:11:48 192.168.122.209 [47259.306457] [tdb] Close table 'cache0.tdb' Apr 26 05:11:49 192.168.122.209 [47259.544511] [tdb] Close table 'filter0.tdb' Apr 26 05:11:49 192.168.122.209 [47260.174987] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 05:11:49 192.168.122.209 [47260.175466] [tempesta fw] modules are stopped Apr 26 05:11:50 192.168.122.209 [47260.468960] [tempesta fw] exiting... Apr 26 05:11:50 192.168.122.209 [47261.229592] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 05:11:50 192.168.122.209 [47261.302257] [tdb] Shutdown Tempesta DB Apr 26 05:11:51 192.168.122.209 [47261.526029] End test: t_ja5.test_ja5_filters.TestJa5FiltersTestSuiteCiphers.test_ja5_hash_difference Apr 26 05:11:51 192.168.122.209 [47261.536005] Start test: t_ja5.test_ja5_filters.TestJa5FiltersTestSuiteCookies.test_ja5_hash_difference Apr 26 05:11:52 192.168.122.209 [47262.728770] [tdb] Start Tempesta DB Apr 26 05:11:52 192.168.122.209 [47262.867404] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:11:54 192.168.122.209 [47265.113290] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47265.113290] Maybe that's fine, but it's worth checking the [47265.113290] config - if there is no relations between the [47265.113290] names, then host name confusion attack is possible. Apr 26 05:11:54 192.168.122.209 [47265.344007] [tempesta fw] Configuration processing is completed. Apr 26 05:11:55 192.168.122.209 [47265.462287] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 05:11:55 192.168.122.209 [47265.544332] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000003038fc3d Apr 26 05:11:55 192.168.122.209 [47265.570435] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000d11db51e Apr 26 05:11:55 192.168.122.209 [47265.974135] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6070ba4 Apr 26 05:11:55 192.168.122.209 [47266.041022] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000a968d47d Apr 26 05:11:55 192.168.122.209 [47266.080897] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000007aec66b3 Apr 26 05:11:55 192.168.122.209 [47266.172024] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:11:55 192.168.122.209 [47266.223966] [tempesta fw] Tempesta FW is ready Apr 26 05:12:00 192.168.122.209 [47271.053268] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=5b455ce2000c2200" Apr 26 05:12:00 192.168.122.209 [47271.203970] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=5b455ce2000c2200" Apr 26 05:12:00 192.168.122.209 [47271.364269] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=5b455ce2000c4200" Apr 26 05:12:01 192.168.122.209 [47271.544476] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=5b455ce2000c4200" Apr 26 05:12:01 192.168.122.209 [47272.123328] [tdb] Close table 'client0.tdb' Apr 26 05:12:01 192.168.122.209 [47272.311088] [tdb] Close table 'sessions0.tdb' Apr 26 05:12:05 192.168.122.209 [47275.429336] [tdb] Close table 'cache0.tdb' Apr 26 05:12:05 192.168.122.209 [47275.682476] [tdb] Close table 'filter0.tdb' Apr 26 05:12:05 192.168.122.209 [47276.328603] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 05:12:05 192.168.122.209 [47276.329055] [tempesta fw] modules are stopped Apr 26 05:12:06 192.168.122.209 [47276.662033] [tempesta fw] exiting... Apr 26 05:12:06 192.168.122.209 [47277.355850] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 05:12:07 192.168.122.209 [47277.431211] [tdb] Shutdown Tempesta DB Apr 26 05:12:08 192.168.122.209 [47278.669273] [tdb] Start Tempesta DB Apr 26 05:12:08 192.168.122.209 [47278.798539] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:12:10 192.168.122.209 [47280.949463] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47280.949463] Maybe that's fine, but it's worth checking the [47280.949463] config - if there is no relations between the [47280.949463] names, then host name confusion attack is possible. Apr 26 05:12:10 192.168.122.209 [47281.164209] [tempesta fw] Configuration processing is completed. Apr 26 05:12:10 192.168.122.209 [47281.276245] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 05:12:10 192.168.122.209 [47281.359502] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000003038fc3d Apr 26 05:12:10 192.168.122.209 [47281.385301] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000d11db51e Apr 26 05:12:11 192.168.122.209 [47281.783168] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6070ba4 Apr 26 05:12:11 192.168.122.209 [47281.845125] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000a968d47d Apr 26 05:12:11 192.168.122.209 [47281.871025] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000007aec66b3 Apr 26 05:12:11 192.168.122.209 [47282.028228] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:12:11 192.168.122.209 [47282.128169] [tempesta fw] Tempesta FW is ready Apr 26 05:12:11 192.168.122.209 [47282.239961] [tempesta fw] Warning: parsed request exceeded ja5h limit: 127.0.0.1 Apr 26 05:12:11 192.168.122.209 [47282.240675] [tempesta fw] 127.0.0.1 "-" "GET / HTTP/1.1" 403 0 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=5b455ce2000c2200" Apr 26 05:12:11 192.168.122.209 [47282.251438] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=5b455ce2000c2200" Apr 26 05:12:11 192.168.122.209 [47282.279914] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=5b455ce2000c4200" Apr 26 05:12:11 192.168.122.209 [47282.293341] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=5b455ce2000c4200" Apr 26 05:12:12 192.168.122.209 [47282.801840] [tdb] Close table 'client0.tdb' Apr 26 05:12:12 192.168.122.209 [47283.021314] [tdb] Close table 'sessions0.tdb' Apr 26 05:12:15 192.168.122.209 [47286.361328] [tdb] Close table 'cache0.tdb' Apr 26 05:12:16 192.168.122.209 [47286.587560] [tdb] Close table 'filter0.tdb' Apr 26 05:12:16 192.168.122.209 [47287.253376] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 05:12:16 192.168.122.209 [47287.253848] [tempesta fw] modules are stopped Apr 26 05:12:17 192.168.122.209 [47287.569447] [tempesta fw] exiting... Apr 26 05:12:17 192.168.122.209 [47288.295804] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 05:12:17 192.168.122.209 [47288.373774] [tdb] Shutdown Tempesta DB Apr 26 05:12:18 192.168.122.209 [47288.607106] End test: t_ja5.test_ja5_filters.TestJa5FiltersTestSuiteCookies.test_ja5_hash_difference Apr 26 05:12:18 192.168.122.209 [47288.631140] Start test: t_ja5.test_ja5_filters.TestJa5FiltersTestSuiteCookies_2.test_ja5_hash_difference Apr 26 05:12:19 192.168.122.209 [47289.709558] [tdb] Start Tempesta DB Apr 26 05:12:19 192.168.122.209 [47289.849488] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:12:21 192.168.122.209 [47292.049565] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47292.049565] Maybe that's fine, but it's worth checking the [47292.049565] config - if there is no relations between the [47292.049565] names, then host name confusion attack is possible. Apr 26 05:12:21 192.168.122.209 [47292.288210] [tempesta fw] Configuration processing is completed. Apr 26 05:12:22 192.168.122.209 [47292.402044] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 05:12:22 192.168.122.209 [47292.485765] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000003038fc3d Apr 26 05:12:22 192.168.122.209 [47292.512250] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000d11db51e Apr 26 05:12:22 192.168.122.209 [47292.917343] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6070ba4 Apr 26 05:12:22 192.168.122.209 [47292.974021] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000a968d47d Apr 26 05:12:22 192.168.122.209 [47293.005336] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000007aec66b3 Apr 26 05:12:22 192.168.122.209 [47293.084362] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:12:22 192.168.122.209 [47293.124316] [tempesta fw] Tempesta FW is ready Apr 26 05:12:27 192.168.122.209 [47297.933380] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=5b455ce2000c6200" Apr 26 05:12:27 192.168.122.209 [47298.104371] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=5b455ce2000c6200" Apr 26 05:12:27 192.168.122.209 [47298.258781] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=5b455ce2000c8200" Apr 26 05:12:28 192.168.122.209 [47298.432897] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=5b455ce2000c8200" Apr 26 05:12:28 192.168.122.209 [47298.991026] [tdb] Close table 'client0.tdb' Apr 26 05:12:28 192.168.122.209 [47299.194811] [tdb] Close table 'sessions0.tdb' Apr 26 05:12:31 192.168.122.209 [47302.375614] [tdb] Close table 'cache0.tdb' Apr 26 05:12:32 192.168.122.209 [47302.605238] [tdb] Close table 'filter0.tdb' Apr 26 05:12:32 192.168.122.209 [47303.251680] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 05:12:32 192.168.122.209 [47303.252349] [tempesta fw] modules are stopped Apr 26 05:12:33 192.168.122.209 [47303.553267] [tempesta fw] exiting... Apr 26 05:12:33 192.168.122.209 [47304.289180] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 05:12:33 192.168.122.209 [47304.317695] [tdb] Shutdown Tempesta DB Apr 26 05:12:35 192.168.122.209 [47305.509072] [tdb] Start Tempesta DB Apr 26 05:12:35 192.168.122.209 [47305.642063] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:12:37 192.168.122.209 [47307.720890] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47307.720890] Maybe that's fine, but it's worth checking the [47307.720890] config - if there is no relations between the [47307.720890] names, then host name confusion attack is possible. Apr 26 05:12:37 192.168.122.209 [47307.948517] [tempesta fw] Configuration processing is completed. Apr 26 05:12:37 192.168.122.209 [47308.062779] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 05:12:37 192.168.122.209 [47308.145912] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000003038fc3d Apr 26 05:12:37 192.168.122.209 [47308.172344] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000d11db51e Apr 26 05:12:38 192.168.122.209 [47308.575480] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6070ba4 Apr 26 05:12:38 192.168.122.209 [47308.631710] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000a968d47d Apr 26 05:12:38 192.168.122.209 [47308.663284] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000007aec66b3 Apr 26 05:12:38 192.168.122.209 [47308.816491] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:12:38 192.168.122.209 [47308.928454] [tempesta fw] Tempesta FW is ready Apr 26 05:12:38 192.168.122.209 [47309.043045] [tempesta fw] Warning: parsed request exceeded ja5h limit: 127.0.0.1 Apr 26 05:12:38 192.168.122.209 [47309.043731] [tempesta fw] 127.0.0.1 "-" "GET / HTTP/1.1" 403 0 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=5b455ce2000c6200" Apr 26 05:12:38 192.168.122.209 [47309.054976] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=5b455ce2000c6200" Apr 26 05:12:38 192.168.122.209 [47309.055353] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=5b455ce2000c8200" Apr 26 05:12:38 192.168.122.209 [47309.091171] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=5b455ce2000c8200" Apr 26 05:12:39 192.168.122.209 [47309.621556] [tdb] Close table 'client0.tdb' Apr 26 05:12:39 192.168.122.209 [47309.808203] [tdb] Close table 'sessions0.tdb' Apr 26 05:12:42 192.168.122.209 [47312.990249] [tdb] Close table 'cache0.tdb' Apr 26 05:12:42 192.168.122.209 [47313.238794] [tdb] Close table 'filter0.tdb' Apr 26 05:12:43 192.168.122.209 [47313.881206] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 05:12:43 192.168.122.209 [47313.881657] [tempesta fw] modules are stopped Apr 26 05:12:43 192.168.122.209 [47314.184972] [tempesta fw] exiting... Apr 26 05:12:44 192.168.122.209 [47314.878825] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 05:12:44 192.168.122.209 [47314.932683] [tdb] Shutdown Tempesta DB Apr 26 05:12:44 192.168.122.209 [47315.158638] End test: t_ja5.test_ja5_filters.TestJa5FiltersTestSuiteCookies_2.test_ja5_hash_difference Apr 26 05:12:44 192.168.122.209 [47315.182280] Start test: t_ja5.test_ja5_filters.TestJa5FiltersTestSuiteHeaders.test_ja5_hash_difference Apr 26 05:12:45 192.168.122.209 [47316.300150] [tdb] Start Tempesta DB Apr 26 05:12:46 192.168.122.209 [47316.433850] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:12:48 192.168.122.209 [47318.705918] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47318.705918] Maybe that's fine, but it's worth checking the [47318.705918] config - if there is no relations between the [47318.705918] names, then host name confusion attack is possible. Apr 26 05:12:48 192.168.122.209 [47318.928644] [tempesta fw] Configuration processing is completed. Apr 26 05:12:48 192.168.122.209 [47319.045465] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 05:12:48 192.168.122.209 [47319.127831] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000003038fc3d Apr 26 05:12:48 192.168.122.209 [47319.154080] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000d11db51e Apr 26 05:12:49 192.168.122.209 [47319.564906] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6070ba4 Apr 26 05:12:49 192.168.122.209 [47319.627516] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000a968d47d Apr 26 05:12:49 192.168.122.209 [47319.653176] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000007aec66b3 Apr 26 05:12:49 192.168.122.209 [47319.744689] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:12:49 192.168.122.209 [47319.788633] [tempesta fw] Tempesta FW is ready Apr 26 05:12:54 192.168.122.209 [47324.592883] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=c3b9d219000c0200" Apr 26 05:12:54 192.168.122.209 [47324.764455] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=c3b9d219000c0200" Apr 26 05:12:54 192.168.122.209 [47324.927821] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=b93d346b000c0280" Apr 26 05:12:54 192.168.122.209 [47325.089251] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=b93d346b000c0280" Apr 26 05:12:55 192.168.122.209 [47325.705051] [tdb] Close table 'client0.tdb' Apr 26 05:12:55 192.168.122.209 [47325.903856] [tdb] Close table 'sessions0.tdb' Apr 26 05:12:58 192.168.122.209 [47329.021634] [tdb] Close table 'cache0.tdb' Apr 26 05:12:58 192.168.122.209 [47329.265542] [tdb] Close table 'filter0.tdb' Apr 26 05:12:59 192.168.122.209 [47329.900946] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 05:12:59 192.168.122.209 [47329.901400] [tempesta fw] modules are stopped Apr 26 05:12:59 192.168.122.209 [47330.204864] [tempesta fw] exiting... Apr 26 05:13:00 192.168.122.209 [47330.910858] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 05:13:00 192.168.122.209 [47330.946544] [tdb] Shutdown Tempesta DB Apr 26 05:13:01 192.168.122.209 [47332.153958] [tdb] Start Tempesta DB Apr 26 05:13:01 192.168.122.209 [47332.288848] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:13:03 192.168.122.209 [47334.365327] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47334.365327] Maybe that's fine, but it's worth checking the [47334.365327] config - if there is no relations between the [47334.365327] names, then host name confusion attack is possible. Apr 26 05:13:04 192.168.122.209 [47334.604861] [tempesta fw] Configuration processing is completed. Apr 26 05:13:04 192.168.122.209 [47334.729294] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 05:13:04 192.168.122.209 [47334.813195] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000003038fc3d Apr 26 05:13:04 192.168.122.209 [47334.839690] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000d11db51e Apr 26 05:13:04 192.168.122.209 [47335.243856] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6070ba4 Apr 26 05:13:04 192.168.122.209 [47335.299903] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000a968d47d Apr 26 05:13:04 192.168.122.209 [47335.331209] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000007aec66b3 Apr 26 05:13:05 192.168.122.209 [47335.508868] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:13:05 192.168.122.209 [47335.620811] [tempesta fw] Tempesta FW is ready Apr 26 05:13:05 192.168.122.209 [47335.743600] [tempesta fw] Warning: parsed request exceeded ja5h limit: 127.0.0.1 Apr 26 05:13:05 192.168.122.209 [47335.744315] [tempesta fw] 127.0.0.1 "-" "GET / HTTP/1.1" 403 0 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=c3b9d219000c0200" Apr 26 05:13:05 192.168.122.209 [47335.749055] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=c3b9d219000c0200" Apr 26 05:13:05 192.168.122.209 [47335.756169] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=b93d346b000c0280" Apr 26 05:13:05 192.168.122.209 [47335.784302] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=b93d346b000c0280" Apr 26 05:13:05 192.168.122.209 [47336.330691] [tdb] Close table 'client0.tdb' Apr 26 05:13:06 192.168.122.209 [47336.520346] [tdb] Close table 'sessions0.tdb' Apr 26 05:13:09 192.168.122.209 [47339.699592] [tdb] Close table 'cache0.tdb' Apr 26 05:13:09 192.168.122.209 [47339.944199] [tdb] Close table 'filter0.tdb' Apr 26 05:13:10 192.168.122.209 [47340.740327] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 05:13:10 192.168.122.209 [47340.740793] [tempesta fw] modules are stopped Apr 26 05:13:10 192.168.122.209 [47341.068042] [tempesta fw] exiting... Apr 26 05:13:11 192.168.122.209 [47341.785735] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 05:13:11 192.168.122.209 [47341.856844] [tdb] Shutdown Tempesta DB Apr 26 05:13:11 192.168.122.209 [47342.078590] End test: t_ja5.test_ja5_filters.TestJa5FiltersTestSuiteHeaders.test_ja5_hash_difference Apr 26 05:13:11 192.168.122.209 [47342.086568] Start test: t_ja5.test_ja5_filters.TestJa5FiltersTestSuiteHttp.test_ja5_hash_difference Apr 26 05:13:12 192.168.122.209 [47343.237720] [tdb] Start Tempesta DB Apr 26 05:13:12 192.168.122.209 [47343.361620] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:13:15 192.168.122.209 [47345.582237] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47345.582237] Maybe that's fine, but it's worth checking the [47345.582237] config - if there is no relations between the [47345.582237] names, then host name confusion attack is possible. Apr 26 05:13:15 192.168.122.209 [47345.772981] [tempesta fw] Configuration processing is completed. Apr 26 05:13:15 192.168.122.209 [47345.885610] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 05:13:15 192.168.122.209 [47345.974674] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000003038fc3d Apr 26 05:13:15 192.168.122.209 [47346.000894] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000d11db51e Apr 26 05:13:16 192.168.122.209 [47346.414108] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6070ba4 Apr 26 05:13:16 192.168.122.209 [47346.483928] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000a968d47d Apr 26 05:13:16 192.168.122.209 [47346.509262] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000007aec66b3 Apr 26 05:13:16 192.168.122.209 [47346.612961] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:13:16 192.168.122.209 [47346.652918] [tempesta fw] Tempesta FW is ready Apr 26 05:13:21 192.168.122.209 [47351.467818] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=65636588000c0180" Apr 26 05:13:21 192.168.122.209 [47351.643300] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=65636588000c0180" Apr 26 05:13:21 192.168.122.209 [47351.849465] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/2.0" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170015" "ja5h=6564157c008c0300" Apr 26 05:13:21 192.168.122.209 [47352.016545] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/2.0" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170015" "ja5h=6564157c008c0300" Apr 26 05:13:22 192.168.122.209 [47352.658326] [tdb] Close table 'client0.tdb' Apr 26 05:13:22 192.168.122.209 [47352.845743] [tdb] Close table 'sessions0.tdb' Apr 26 05:13:25 192.168.122.209 [47355.936253] [tdb] Close table 'cache0.tdb' Apr 26 05:13:25 192.168.122.209 [47356.170747] [tdb] Close table 'filter0.tdb' Apr 26 05:13:26 192.168.122.209 [47356.814639] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 05:13:26 192.168.122.209 [47356.815096] [tempesta fw] modules are stopped Apr 26 05:13:26 192.168.122.209 [47357.154558] [tempesta fw] exiting... Apr 26 05:13:27 192.168.122.209 [47357.888027] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 05:13:27 192.168.122.209 [47357.945538] [tdb] Shutdown Tempesta DB Apr 26 05:13:28 192.168.122.209 [47359.081594] [tdb] Start Tempesta DB Apr 26 05:13:28 192.168.122.209 [47359.204211] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:13:30 192.168.122.209 [47361.186525] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47361.186525] Maybe that's fine, but it's worth checking the [47361.186525] config - if there is no relations between the [47361.186525] names, then host name confusion attack is possible. Apr 26 05:13:31 192.168.122.209 [47361.413175] [tempesta fw] Configuration processing is completed. Apr 26 05:13:31 192.168.122.209 [47361.533472] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 05:13:31 192.168.122.209 [47361.617868] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000003038fc3d Apr 26 05:13:31 192.168.122.209 [47361.643846] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000d11db51e Apr 26 05:13:31 192.168.122.209 [47362.042746] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6070ba4 Apr 26 05:13:31 192.168.122.209 [47362.105282] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000a968d47d Apr 26 05:13:31 192.168.122.209 [47362.130513] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000007aec66b3 Apr 26 05:13:31 192.168.122.209 [47362.301216] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:13:31 192.168.122.209 [47362.389163] [tempesta fw] Tempesta FW is ready Apr 26 05:13:32 192.168.122.209 [47362.497742] [tempesta fw] Warning: parsed request exceeded ja5h limit: 127.0.0.1 Apr 26 05:13:32 192.168.122.209 [47362.498439] [tempesta fw] 127.0.0.1 "-" "GET / HTTP/1.1" 403 0 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=65636588000c0180" Apr 26 05:13:32 192.168.122.209 [47362.528394] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=65636588000c0180" Apr 26 05:13:32 192.168.122.209 [47362.533497] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/2.0" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170015" "ja5h=6564157c008c0300" Apr 26 05:13:32 192.168.122.209 [47362.581155] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/2.0" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170015" "ja5h=6564157c008c0300" Apr 26 05:13:32 192.168.122.209 [47363.098614] [tdb] Close table 'client0.tdb' Apr 26 05:13:32 192.168.122.209 [47363.287726] [tdb] Close table 'sessions0.tdb' Apr 26 05:13:36 192.168.122.209 [47366.472252] [tdb] Close table 'cache0.tdb' Apr 26 05:13:36 192.168.122.209 [47366.717749] [tdb] Close table 'filter0.tdb' Apr 26 05:13:36 192.168.122.209 [47367.356800] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 05:13:36 192.168.122.209 [47367.357286] [tempesta fw] modules are stopped Apr 26 05:13:37 192.168.122.209 [47367.676167] [tempesta fw] exiting... Apr 26 05:13:37 192.168.122.209 [47368.330826] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 05:13:37 192.168.122.209 [47368.379683] [tdb] Shutdown Tempesta DB Apr 26 05:13:38 192.168.122.209 [47368.634376] End test: t_ja5.test_ja5_filters.TestJa5FiltersTestSuiteHttp.test_ja5_hash_difference Apr 26 05:13:38 192.168.122.209 [47368.646695] Start test: t_ja5.test_ja5_filters.TestJa5FiltersTestSuiteMethod.test_ja5_hash_difference Apr 26 05:13:39 192.168.122.209 [47369.838275] [tdb] Start Tempesta DB Apr 26 05:13:39 192.168.122.209 [47369.970370] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:13:41 192.168.122.209 [47372.170593] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47372.170593] Maybe that's fine, but it's worth checking the [47372.170593] config - if there is no relations between the [47372.170593] names, then host name confusion attack is possible. Apr 26 05:13:41 192.168.122.209 [47372.381304] [tempesta fw] Configuration processing is completed. Apr 26 05:13:42 192.168.122.209 [47372.498277] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 05:13:42 192.168.122.209 [47372.583581] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000003038fc3d Apr 26 05:13:42 192.168.122.209 [47372.610359] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000d11db51e Apr 26 05:13:42 192.168.122.209 [47373.020275] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6070ba4 Apr 26 05:13:42 192.168.122.209 [47373.088404] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000a968d47d Apr 26 05:13:42 192.168.122.209 [47373.113783] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000007aec66b3 Apr 26 05:13:42 192.168.122.209 [47373.209331] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:13:42 192.168.122.209 [47373.249293] [tempesta fw] Tempesta FW is ready Apr 26 05:13:47 192.168.122.209 [47378.031119] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=65636588000c0180" Apr 26 05:13:47 192.168.122.209 [47378.192303] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=65636588000c0180" Apr 26 05:13:47 192.168.122.209 [47378.364264] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "POST / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=6563658800280180" Apr 26 05:13:48 192.168.122.209 [47378.539218] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "POST / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=6563658800280180" Apr 26 05:13:48 192.168.122.209 [47379.094369] [tdb] Close table 'client0.tdb' Apr 26 05:13:48 192.168.122.209 [47379.308854] [tdb] Close table 'sessions0.tdb' Apr 26 05:13:52 192.168.122.209 [47382.428287] [tdb] Close table 'cache0.tdb' Apr 26 05:13:52 192.168.122.209 [47382.692268] [tdb] Close table 'filter0.tdb' Apr 26 05:13:52 192.168.122.209 [47383.364544] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 05:13:52 192.168.122.209 [47383.365180] [tempesta fw] modules are stopped Apr 26 05:13:53 192.168.122.209 [47383.689026] [tempesta fw] exiting... Apr 26 05:13:53 192.168.122.209 [47384.382936] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 05:13:54 192.168.122.209 [47384.445142] [tdb] Shutdown Tempesta DB Apr 26 05:13:55 192.168.122.209 [47385.619986] [tdb] Start Tempesta DB Apr 26 05:13:55 192.168.122.209 [47385.749668] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:13:57 192.168.122.209 [47387.810776] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47387.810776] Maybe that's fine, but it's worth checking the [47387.810776] config - if there is no relations between the [47387.810776] names, then host name confusion attack is possible. Apr 26 05:13:57 192.168.122.209 [47388.013496] [tempesta fw] Configuration processing is completed. Apr 26 05:13:57 192.168.122.209 [47388.144155] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 05:13:57 192.168.122.209 [47388.226604] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000003038fc3d Apr 26 05:13:57 192.168.122.209 [47388.252759] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000d11db51e Apr 26 05:13:58 192.168.122.209 [47388.655395] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6070ba4 Apr 26 05:13:58 192.168.122.209 [47388.713199] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000a968d47d Apr 26 05:13:58 192.168.122.209 [47388.738586] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000007aec66b3 Apr 26 05:13:58 192.168.122.209 [47388.889523] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:13:58 192.168.122.209 [47388.977472] [tempesta fw] Tempesta FW is ready Apr 26 05:13:58 192.168.122.209 [47389.078936] [tempesta fw] Warning: parsed request exceeded ja5h limit: 127.0.0.1 Apr 26 05:13:58 192.168.122.209 [47389.079673] [tempesta fw] 127.0.0.1 "-" "GET / HTTP/1.1" 403 0 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=65636588000c0180" Apr 26 05:13:58 192.168.122.209 [47389.090970] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=65636588000c0180" Apr 26 05:13:58 192.168.122.209 [47389.105449] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "POST / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=6563658800280180" Apr 26 05:13:58 192.168.122.209 [47389.123438] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "POST / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=6563658800280180" Apr 26 05:13:59 192.168.122.209 [47389.609800] [tdb] Close table 'client0.tdb' Apr 26 05:13:59 192.168.122.209 [47389.806240] [tdb] Close table 'sessions0.tdb' Apr 26 05:14:02 192.168.122.209 [47392.950675] [tdb] Close table 'cache0.tdb' Apr 26 05:14:02 192.168.122.209 [47393.190927] [tdb] Close table 'filter0.tdb' Apr 26 05:14:03 192.168.122.209 [47393.856827] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 05:14:03 192.168.122.209 [47393.857285] [tempesta fw] modules are stopped Apr 26 05:14:03 192.168.122.209 [47394.119024] [tempesta fw] exiting... Apr 26 05:14:04 192.168.122.209 [47394.799760] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 05:14:04 192.168.122.209 [47394.852769] [tdb] Shutdown Tempesta DB Apr 26 05:14:04 192.168.122.209 [47395.085462] End test: t_ja5.test_ja5_filters.TestJa5FiltersTestSuiteMethod.test_ja5_hash_difference Apr 26 05:14:04 192.168.122.209 [47395.107095] Start test: t_ja5.test_ja5_filters.TestJa5FiltersTestSuiteNoAlpn.test_ja5_hash_difference Apr 26 05:14:05 192.168.122.209 [47396.303412] [tdb] Start Tempesta DB Apr 26 05:14:06 192.168.122.209 [47396.444272] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:14:08 192.168.122.209 [47398.690837] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47398.690837] Maybe that's fine, but it's worth checking the [47398.690837] config - if there is no relations between the [47398.690837] names, then host name confusion attack is possible. Apr 26 05:14:08 192.168.122.209 [47398.889588] [tempesta fw] Configuration processing is completed. Apr 26 05:14:08 192.168.122.209 [47399.012772] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 05:14:08 192.168.122.209 [47399.095594] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000003038fc3d Apr 26 05:14:08 192.168.122.209 [47399.121964] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000d11db51e Apr 26 05:14:09 192.168.122.209 [47399.526090] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6070ba4 Apr 26 05:14:09 192.168.122.209 [47399.589464] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000a968d47d Apr 26 05:14:09 192.168.122.209 [47399.614695] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000007aec66b3 Apr 26 05:14:09 192.168.122.209 [47399.689671] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:14:09 192.168.122.209 [47399.745609] [tempesta fw] Tempesta FW is ready Apr 26 05:14:14 192.168.122.209 [47404.570177] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=1271f8cc2c4c0011" "ja5h=65636588000c0180" Apr 26 05:14:14 192.168.122.209 [47404.733478] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=1271f8cc2c4c0011" "ja5h=65636588000c0180" Apr 26 05:14:14 192.168.122.209 [47404.903201] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=1271532a2c4c0010" "ja5h=65636588000c0180" Apr 26 05:14:14 192.168.122.209 [47405.075797] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=1271532a2c4c0010" "ja5h=65636588000c0180" Apr 26 05:14:15 192.168.122.209 [47405.696284] [tdb] Close table 'client0.tdb' Apr 26 05:14:15 192.168.122.209 [47405.882921] [tdb] Close table 'sessions0.tdb' Apr 26 05:14:18 192.168.122.209 [47409.063351] [tdb] Close table 'cache0.tdb' Apr 26 05:14:18 192.168.122.209 [47409.326025] [tdb] Close table 'filter0.tdb' Apr 26 05:14:19 192.168.122.209 [47409.994074] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 05:14:19 192.168.122.209 [47409.994551] [tempesta fw] modules are stopped Apr 26 05:14:19 192.168.122.209 [47410.315112] [tempesta fw] exiting... Apr 26 05:14:20 192.168.122.209 [47411.030813] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 05:14:20 192.168.122.209 [47411.073850] [tdb] Shutdown Tempesta DB Apr 26 05:14:21 192.168.122.209 [47412.214522] [tdb] Start Tempesta DB Apr 26 05:14:21 192.168.122.209 [47412.360397] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:14:24 192.168.122.209 [47414.543202] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47414.543202] Maybe that's fine, but it's worth checking the [47414.543202] config - if there is no relations between the [47414.543202] names, then host name confusion attack is possible. Apr 26 05:14:24 192.168.122.209 [47414.797895] [tempesta fw] Configuration processing is completed. Apr 26 05:14:24 192.168.122.209 [47414.930611] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 05:14:24 192.168.122.209 [47415.035080] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000003038fc3d Apr 26 05:14:24 192.168.122.209 [47415.065630] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000d11db51e Apr 26 05:14:25 192.168.122.209 [47415.567563] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6070ba4 Apr 26 05:14:25 192.168.122.209 [47415.639361] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000a968d47d Apr 26 05:14:25 192.168.122.209 [47415.678058] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000007aec66b3 Apr 26 05:14:25 192.168.122.209 [47415.849879] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:14:25 192.168.122.209 [47415.941973] [tempesta fw] Tempesta FW is ready Apr 26 05:14:25 192.168.122.209 [47416.069600] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=1271f8cc2c4c0011" "ja5h=65636588000c0180" Apr 26 05:14:25 192.168.122.209 [47416.076424] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=1271532a2c4c0010" "ja5h=65636588000c0180" Apr 26 05:14:25 192.168.122.209 [47416.103600] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=1271532a2c4c0010" "ja5h=65636588000c0180" Apr 26 05:14:26 192.168.122.209 [47416.626955] [tdb] Close table 'client0.tdb' Apr 26 05:14:26 192.168.122.209 [47416.816073] [tdb] Close table 'sessions0.tdb' Apr 26 05:14:29 192.168.122.209 [47420.052985] [tdb] Close table 'cache0.tdb' Apr 26 05:14:29 192.168.122.209 [47420.298145] [tdb] Close table 'filter0.tdb' Apr 26 05:14:30 192.168.122.209 [47420.950850] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 05:14:30 192.168.122.209 [47420.951318] [tempesta fw] modules are stopped Apr 26 05:14:30 192.168.122.209 [47421.243530] [tempesta fw] exiting... Apr 26 05:14:31 192.168.122.209 [47421.963487] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 05:14:31 192.168.122.209 [47421.992790] [tdb] Shutdown Tempesta DB Apr 26 05:14:31 192.168.122.209 [47422.211834] End test: t_ja5.test_ja5_filters.TestJa5FiltersTestSuiteNoAlpn.test_ja5_hash_difference Apr 26 05:14:31 192.168.122.209 [47422.227218] Start test: t_ja5.test_ja5_filters.TestJa5FiltersTestSuiteReferer.test_ja5_hash_difference Apr 26 05:14:33 192.168.122.209 [47423.405804] [tdb] Start Tempesta DB Apr 26 05:14:33 192.168.122.209 [47423.587501] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:14:35 192.168.122.209 [47425.795510] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47425.795510] Maybe that's fine, but it's worth checking the [47425.795510] config - if there is no relations between the [47425.795510] names, then host name confusion attack is possible. Apr 26 05:14:35 192.168.122.209 [47426.041954] [tempesta fw] Configuration processing is completed. Apr 26 05:14:35 192.168.122.209 [47426.162455] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 05:14:35 192.168.122.209 [47426.251249] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000003038fc3d Apr 26 05:14:35 192.168.122.209 [47426.289169] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000d11db51e Apr 26 05:14:36 192.168.122.209 [47426.753545] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6070ba4 Apr 26 05:14:36 192.168.122.209 [47426.794104] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000a968d47d Apr 26 05:14:36 192.168.122.209 [47426.822800] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000007aec66b3 Apr 26 05:14:36 192.168.122.209 [47426.894039] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:14:36 192.168.122.209 [47426.937959] [tempesta fw] Tempesta FW is ready Apr 26 05:14:41 192.168.122.209 [47431.828765] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "tempesta-tech.com" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=5b455ce3000c0240" Apr 26 05:14:41 192.168.122.209 [47431.999920] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "tempesta-tech.com" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=5b455ce3000c0240" Apr 26 05:14:41 192.168.122.209 [47432.171331] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=65636588000c0180" Apr 26 05:14:41 192.168.122.209 [47432.344596] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=65636588000c0180" Apr 26 05:14:42 192.168.122.209 [47432.999484] [tdb] Close table 'client0.tdb' Apr 26 05:14:42 192.168.122.209 [47433.202547] [tdb] Close table 'sessions0.tdb' Apr 26 05:14:46 192.168.122.209 [47436.588377] [tdb] Close table 'cache0.tdb' Apr 26 05:14:46 192.168.122.209 [47436.865876] [tdb] Close table 'filter0.tdb' Apr 26 05:14:47 192.168.122.209 [47437.576392] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 05:14:47 192.168.122.209 [47437.576862] [tempesta fw] modules are stopped Apr 26 05:14:47 192.168.122.209 [47437.831585] [tempesta fw] exiting... Apr 26 05:14:48 192.168.122.209 [47438.629195] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 05:14:48 192.168.122.209 [47438.677298] [tdb] Shutdown Tempesta DB Apr 26 05:14:49 192.168.122.209 [47439.797797] [tdb] Start Tempesta DB Apr 26 05:14:49 192.168.122.209 [47439.940317] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:14:51 192.168.122.209 [47442.031153] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47442.031153] Maybe that's fine, but it's worth checking the [47442.031153] config - if there is no relations between the [47442.031153] names, then host name confusion attack is possible. Apr 26 05:14:51 192.168.122.209 [47442.250168] [tempesta fw] Configuration processing is completed. Apr 26 05:14:51 192.168.122.209 [47442.360137] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 05:14:52 192.168.122.209 [47442.443240] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000003038fc3d Apr 26 05:14:52 192.168.122.209 [47442.469673] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000d11db51e Apr 26 05:14:52 192.168.122.209 [47442.886976] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6070ba4 Apr 26 05:14:52 192.168.122.209 [47442.914009] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000a968d47d Apr 26 05:14:52 192.168.122.209 [47442.941134] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000007aec66b3 Apr 26 05:14:52 192.168.122.209 [47443.098571] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:14:52 192.168.122.209 [47443.178139] [tempesta fw] Tempesta FW is ready Apr 26 05:14:52 192.168.122.209 [47443.286692] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "tempesta-tech.com" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=5b455ce3000c0240" Apr 26 05:14:52 192.168.122.209 [47443.295382] [tempesta fw] Warning: parsed request exceeded ja5h limit: 127.0.0.1 Apr 26 05:14:52 192.168.122.209 [47443.296076] [tempesta fw] 127.0.0.1 "-" "GET / HTTP/1.1" 403 0 "tempesta-tech.com" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=5b455ce3000c0240" Apr 26 05:14:52 192.168.122.209 [47443.328813] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=65636588000c0180" Apr 26 05:14:52 192.168.122.209 [47443.338123] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=65636588000c0180" Apr 26 05:14:53 192.168.122.209 [47443.814229] [tdb] Close table 'client0.tdb' Apr 26 05:14:53 192.168.122.209 [47443.987710] [tdb] Close table 'sessions0.tdb' Apr 26 05:14:56 192.168.122.209 [47447.122514] [tdb] Close table 'cache0.tdb' Apr 26 05:14:56 192.168.122.209 [47447.347573] [tdb] Close table 'filter0.tdb' Apr 26 05:14:57 192.168.122.209 [47448.060961] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 05:14:57 192.168.122.209 [47448.061418] [tempesta fw] modules are stopped Apr 26 05:14:57 192.168.122.209 [47448.345707] [tempesta fw] exiting... Apr 26 05:14:58 192.168.122.209 [47449.051206] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 05:14:58 192.168.122.209 [47449.097537] [tdb] Shutdown Tempesta DB Apr 26 05:14:58 192.168.122.209 [47449.317202] End test: t_ja5.test_ja5_filters.TestJa5FiltersTestSuiteReferer.test_ja5_hash_difference Apr 26 05:14:58 192.168.122.209 [47449.327915] Start test: t_ja5.test_ja5_filters.TestJa5FiltersTestSuiteVhost.test_ja5_hash_difference Apr 26 05:15:00 192.168.122.209 [47450.490210] [tdb] Start Tempesta DB Apr 26 05:15:00 192.168.122.209 [47450.622962] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:15:02 192.168.122.209 [47452.835590] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47452.835590] Maybe that's fine, but it's worth checking the [47452.835590] config - if there is no relations between the [47452.835590] names, then host name confusion attack is possible. Apr 26 05:15:02 192.168.122.209 [47453.042413] [tempesta fw] Configuration processing is completed. Apr 26 05:15:02 192.168.122.209 [47453.150517] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 05:15:02 192.168.122.209 [47453.236613] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000003038fc3d Apr 26 05:15:02 192.168.122.209 [47453.264550] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000d11db51e Apr 26 05:15:03 192.168.122.209 [47453.674416] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6070ba4 Apr 26 05:15:03 192.168.122.209 [47453.699949] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000a968d47d Apr 26 05:15:03 192.168.122.209 [47453.726338] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000007aec66b3 Apr 26 05:15:03 192.168.122.209 [47453.802371] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:15:03 192.168.122.209 [47453.842272] [tempesta fw] Tempesta FW is ready Apr 26 05:15:08 192.168.122.209 [47458.635984] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=1271f8cc2c4c0011" "ja5h=65636588000c0180" Apr 26 05:15:08 192.168.122.209 [47458.812869] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=1271f8cc2c4c0011" "ja5h=65636588000c0180" Apr 26 05:15:08 192.168.122.209 [47458.978456] [tempesta fw] 127.0.0.1 "default" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=1471f8cc2c4c0001" "ja5h=65636588000c0180" Apr 26 05:15:08 192.168.122.209 [47459.148413] [tempesta fw] 127.0.0.1 "default" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=1471f8cc2c4c0001" "ja5h=65636588000c0180" Apr 26 05:15:09 192.168.122.209 [47459.719046] [tdb] Close table 'client0.tdb' Apr 26 05:15:09 192.168.122.209 [47459.912621] [tdb] Close table 'sessions0.tdb' Apr 26 05:15:12 192.168.122.209 [47463.071210] [tdb] Close table 'cache0.tdb' Apr 26 05:15:12 192.168.122.209 [47463.327051] [tdb] Close table 'filter0.tdb' Apr 26 05:15:13 192.168.122.209 [47463.964785] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 05:15:13 192.168.122.209 [47463.965254] [tempesta fw] modules are stopped Apr 26 05:15:13 192.168.122.209 [47464.324587] [tempesta fw] exiting... Apr 26 05:15:14 192.168.122.209 [47465.050453] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 05:15:14 192.168.122.209 [47465.080912] [tdb] Shutdown Tempesta DB Apr 26 05:15:15 192.168.122.209 [47466.232986] [tdb] Start Tempesta DB Apr 26 05:15:15 192.168.122.209 [47466.380602] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:15:18 192.168.122.209 [47468.444140] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47468.444140] Maybe that's fine, but it's worth checking the [47468.444140] config - if there is no relations between the [47468.444140] names, then host name confusion attack is possible. Apr 26 05:15:18 192.168.122.209 [47468.658489] [tempesta fw] Configuration processing is completed. Apr 26 05:15:18 192.168.122.209 [47468.774647] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 05:15:18 192.168.122.209 [47468.861361] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000003038fc3d Apr 26 05:15:18 192.168.122.209 [47468.889544] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000d11db51e Apr 26 05:15:18 192.168.122.209 [47469.361464] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6070ba4 Apr 26 05:15:18 192.168.122.209 [47469.392737] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000a968d47d Apr 26 05:15:19 192.168.122.209 [47469.424950] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000007aec66b3 Apr 26 05:15:19 192.168.122.209 [47469.586531] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:15:19 192.168.122.209 [47469.698455] [tempesta fw] Tempesta FW is ready Apr 26 05:15:19 192.168.122.209 [47469.836355] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=1271f8cc2c4c0011" "ja5h=65636588000c0180" Apr 26 05:15:19 192.168.122.209 [47469.846727] [tempesta fw] 127.0.0.1 "default" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=1471f8cc2c4c0001" "ja5h=65636588000c0180" Apr 26 05:15:19 192.168.122.209 [47469.865054] [tempesta fw] 127.0.0.1 "default" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=1471f8cc2c4c0001" "ja5h=65636588000c0180" Apr 26 05:15:20 192.168.122.209 [47470.407190] [tdb] Close table 'client0.tdb' Apr 26 05:15:20 192.168.122.209 [47470.581612] [tdb] Close table 'sessions0.tdb' Apr 26 05:15:23 192.168.122.209 [47473.877414] [tdb] Close table 'cache0.tdb' Apr 26 05:15:23 192.168.122.209 [47474.132439] [tdb] Close table 'filter0.tdb' Apr 26 05:15:24 192.168.122.209 [47474.828728] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 05:15:24 192.168.122.209 [47474.829193] [tempesta fw] modules are stopped Apr 26 05:15:24 192.168.122.209 [47475.099588] [tempesta fw] exiting... Apr 26 05:15:25 192.168.122.209 [47475.874044] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 05:15:25 192.168.122.209 [47475.925640] [tdb] Shutdown Tempesta DB Apr 26 05:15:25 192.168.122.209 [47476.195840] End test: t_ja5.test_ja5_filters.TestJa5FiltersTestSuiteVhost.test_ja5_hash_difference Apr 26 05:15:25 192.168.122.209 [47476.208540] Start test: t_ja5.test_ja5_filters.TestJa5HashDoesNotMatchedWithFiltered.test_default_values Apr 26 05:15:26 192.168.122.209 [47477.389950] [tdb] Start Tempesta DB Apr 26 05:15:27 192.168.122.209 [47477.536307] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:15:29 192.168.122.209 [47479.831979] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47479.831979] Maybe that's fine, but it's worth checking the [47479.831979] config - if there is no relations between the [47479.831979] names, then host name confusion attack is possible. Apr 26 05:15:29 192.168.122.209 [47480.026686] [tempesta fw] Configuration processing is completed. Apr 26 05:15:29 192.168.122.209 [47480.147327] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 05:15:29 192.168.122.209 [47480.231458] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000003038fc3d Apr 26 05:15:29 192.168.122.209 [47480.260534] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000d11db51e Apr 26 05:15:30 192.168.122.209 [47480.737769] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6070ba4 Apr 26 05:15:30 192.168.122.209 [47480.766877] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000a968d47d Apr 26 05:15:30 192.168.122.209 [47480.796903] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000007aec66b3 Apr 26 05:15:30 192.168.122.209 [47480.854600] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:15:30 192.168.122.209 [47480.894624] [tempesta fw] Tempesta FW is ready Apr 26 05:15:30 192.168.122.209 [47481.091841] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=1271f8cc2c4c0011" "ja5h=65636588000c0180" Apr 26 05:15:30 192.168.122.209 [47481.101826] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=1271f8cc2c4c0011" "ja5h=65636588000c0180" Apr 26 05:15:31 192.168.122.209 [47481.631321] [tdb] Close table 'client0.tdb' Apr 26 05:15:31 192.168.122.209 [47481.833145] [tdb] Close table 'sessions0.tdb' Apr 26 05:15:34 192.168.122.209 [47485.216246] [tdb] Close table 'cache0.tdb' Apr 26 05:15:35 192.168.122.209 [47485.477477] [tdb] Close table 'filter0.tdb' Apr 26 05:15:35 192.168.122.209 [47486.184937] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 05:15:35 192.168.122.209 [47486.185400] [tempesta fw] modules are stopped Apr 26 05:15:36 192.168.122.209 [47486.486994] [tempesta fw] exiting... Apr 26 05:15:36 192.168.122.209 [47487.259581] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 05:15:36 192.168.122.209 [47487.307690] [tdb] Shutdown Tempesta DB Apr 26 05:15:37 192.168.122.209 [47487.582291] End test: t_ja5.test_ja5_filters.TestJa5HashDoesNotMatchedWithFiltered.test_default_values Apr 26 05:15:37 192.168.122.209 [47487.605390] Start test: t_ja5.test_ja5_filters.TestRestartAppWithUpdatedHashJa5h.test_hot_reload Apr 26 05:15:38 192.168.122.209 [47488.795720] [tdb] Start Tempesta DB Apr 26 05:15:38 192.168.122.209 [47488.954853] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:15:40 192.168.122.209 [47491.344210] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47491.344210] Maybe that's fine, but it's worth checking the [47491.344210] config - if there is no relations between the [47491.344210] names, then host name confusion attack is possible. Apr 26 05:15:41 192.168.122.209 [47491.554787] [tempesta fw] Configuration processing is completed. Apr 26 05:15:41 192.168.122.209 [47491.673857] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 05:15:41 192.168.122.209 [47491.756108] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000003038fc3d Apr 26 05:15:41 192.168.122.209 [47491.783427] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000d11db51e Apr 26 05:15:41 192.168.122.209 [47492.230334] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6070ba4 Apr 26 05:15:41 192.168.122.209 [47492.259365] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000a968d47d Apr 26 05:15:41 192.168.122.209 [47492.292663] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000007aec66b3 Apr 26 05:15:41 192.168.122.209 [47492.354758] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:15:41 192.168.122.209 [47492.398749] [tempesta fw] Tempesta FW is ready Apr 26 05:15:42 192.168.122.209 [47492.612335] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=1271f8cc2c4c0011" "ja5h=65636588000c0180" Apr 26 05:15:42 192.168.122.209 [47492.721892] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=1271f8cc2c4c0011" "ja5h=65636588000c0180" Apr 26 05:15:42 192.168.122.209 [47493.291059] [tdb] Close table 'client0.tdb' Apr 26 05:15:43 192.168.122.209 [47493.491661] [tdb] Close table 'sessions0.tdb' Apr 26 05:15:46 192.168.122.209 [47496.649959] [tdb] Close table 'cache0.tdb' Apr 26 05:15:46 192.168.122.209 [47496.893416] [tdb] Close table 'filter0.tdb' Apr 26 05:15:47 192.168.122.209 [47497.545264] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 05:15:47 192.168.122.209 [47497.545723] [tempesta fw] modules are stopped Apr 26 05:15:47 192.168.122.209 [47497.844559] [tempesta fw] exiting... Apr 26 05:15:48 192.168.122.209 [47498.533018] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 05:15:48 192.168.122.209 [47498.587831] [tdb] Shutdown Tempesta DB Apr 26 05:15:49 192.168.122.209 [47499.694306] [tdb] Start Tempesta DB Apr 26 05:15:49 192.168.122.209 [47499.845485] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:15:51 192.168.122.209 [47501.915709] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47501.915709] Maybe that's fine, but it's worth checking the [47501.915709] config - if there is no relations between the [47501.915709] names, then host name confusion attack is possible. Apr 26 05:15:51 192.168.122.209 [47502.158823] [tempesta fw] Configuration processing is completed. Apr 26 05:15:51 192.168.122.209 [47502.269562] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 05:15:51 192.168.122.209 [47502.351935] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000003038fc3d Apr 26 05:15:51 192.168.122.209 [47502.387660] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000d11db51e Apr 26 05:15:52 192.168.122.209 [47502.802502] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6070ba4 Apr 26 05:15:52 192.168.122.209 [47502.829414] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000a968d47d Apr 26 05:15:52 192.168.122.209 [47502.855390] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000007aec66b3 Apr 26 05:15:52 192.168.122.209 [47503.007004] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:15:52 192.168.122.209 [47503.098888] [tempesta fw] Tempesta FW is ready Apr 26 05:15:52 192.168.122.209 [47503.213644] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=1271f8cc2c4c0011" "ja5h=65636588000c0180" Apr 26 05:15:53 192.168.122.209 [47503.716070] [tdb] Close table 'client0.tdb' Apr 26 05:15:53 192.168.122.209 [47503.915541] [tdb] Close table 'sessions0.tdb' Apr 26 05:15:56 192.168.122.209 [47507.062547] [tdb] Close table 'cache0.tdb' Apr 26 05:15:56 192.168.122.209 [47507.331688] [tdb] Close table 'filter0.tdb' Apr 26 05:15:57 192.168.122.209 [47507.967629] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 05:15:57 192.168.122.209 [47507.968076] [tempesta fw] modules are stopped Apr 26 05:15:57 192.168.122.209 [47508.311886] [tempesta fw] exiting... Apr 26 05:15:58 192.168.122.209 [47509.037797] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 05:15:58 192.168.122.209 [47509.109613] [tdb] Shutdown Tempesta DB Apr 26 05:15:58 192.168.122.209 [47509.312833] End test: t_ja5.test_ja5_filters.TestRestartAppWithUpdatedHashJa5h.test_hot_reload Apr 26 05:15:58 192.168.122.209 [47509.329926] Start test: t_ja5.test_ja5_filters.TestRestartAppWithUpdatedHashJa5h.test_restart_ok Apr 26 05:16:00 192.168.122.209 [47510.463696] [tdb] Start Tempesta DB Apr 26 05:16:00 192.168.122.209 [47510.598269] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:16:02 192.168.122.209 [47512.780366] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47512.780366] Maybe that's fine, but it's worth checking the [47512.780366] config - if there is no relations between the [47512.780366] names, then host name confusion attack is possible. Apr 26 05:16:02 192.168.122.209 [47512.994996] [tempesta fw] Configuration processing is completed. Apr 26 05:16:02 192.168.122.209 [47513.101627] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 05:16:02 192.168.122.209 [47513.189346] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000003038fc3d Apr 26 05:16:02 192.168.122.209 [47513.216517] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000d11db51e Apr 26 05:16:03 192.168.122.209 [47513.631278] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6070ba4 Apr 26 05:16:03 192.168.122.209 [47513.657471] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000a968d47d Apr 26 05:16:03 192.168.122.209 [47513.683442] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000007aec66b3 Apr 26 05:16:03 192.168.122.209 [47513.759085] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:16:03 192.168.122.209 [47513.807016] [tempesta fw] Tempesta FW is ready Apr 26 05:16:04 192.168.122.209 [47514.433981] [tdb] Close table 'client0.tdb' Apr 26 05:16:04 192.168.122.209 [47514.634256] [tdb] Close table 'sessions0.tdb' Apr 26 05:16:07 192.168.122.209 [47517.794219] [tdb] Close table 'cache0.tdb' Apr 26 05:16:07 192.168.122.209 [47518.035551] [tdb] Close table 'filter0.tdb' Apr 26 05:16:08 192.168.122.209 [47518.690421] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 05:16:08 192.168.122.209 [47518.690882] [tempesta fw] modules are stopped Apr 26 05:16:08 192.168.122.209 [47518.976853] [tempesta fw] exiting... Apr 26 05:16:09 192.168.122.209 [47519.672893] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 05:16:09 192.168.122.209 [47519.728038] [tdb] Shutdown Tempesta DB Apr 26 05:16:10 192.168.122.209 [47520.997075] [tdb] Start Tempesta DB Apr 26 05:16:10 192.168.122.209 [47521.129903] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:16:12 192.168.122.209 [47523.296428] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47523.296428] Maybe that's fine, but it's worth checking the [47523.296428] config - if there is no relations between the [47523.296428] names, then host name confusion attack is possible. Apr 26 05:16:13 192.168.122.209 [47523.515188] [tempesta fw] Configuration processing is completed. Apr 26 05:16:13 192.168.122.209 [47523.624312] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 05:16:13 192.168.122.209 [47523.717379] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000003038fc3d Apr 26 05:16:13 192.168.122.209 [47523.745509] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000d11db51e Apr 26 05:16:13 192.168.122.209 [47524.156868] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6070ba4 Apr 26 05:16:13 192.168.122.209 [47524.182839] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000a968d47d Apr 26 05:16:13 192.168.122.209 [47524.209127] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000007aec66b3 Apr 26 05:16:13 192.168.122.209 [47524.279195] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:16:13 192.168.122.209 [47524.355161] [tempesta fw] Tempesta FW is ready Apr 26 05:16:14 192.168.122.209 [47524.945664] [tdb] Close table 'client0.tdb' Apr 26 05:16:14 192.168.122.209 [47525.148223] [tdb] Close table 'sessions0.tdb' Apr 26 05:16:17 192.168.122.209 [47528.306114] [tdb] Close table 'cache0.tdb' Apr 26 05:16:18 192.168.122.209 [47528.544706] [tdb] Close table 'filter0.tdb' Apr 26 05:16:18 192.168.122.209 [47529.180800] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 05:16:18 192.168.122.209 [47529.181255] [tempesta fw] modules are stopped Apr 26 05:16:19 192.168.122.209 [47529.451120] [tempesta fw] exiting... Apr 26 05:16:19 192.168.122.209 [47530.147579] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 05:16:19 192.168.122.209 [47530.182849] [tdb] Shutdown Tempesta DB Apr 26 05:16:20 192.168.122.209 [47530.431731] End test: t_ja5.test_ja5_filters.TestRestartAppWithUpdatedHashJa5h.test_restart_ok Apr 26 05:16:20 192.168.122.209 [47530.458892] Start test: t_ja5.test_ja5_filters.TestRestartAppWithUpdatedHashJa5t.test_hot_reload Apr 26 05:16:21 192.168.122.209 [47531.648256] [tdb] Start Tempesta DB Apr 26 05:16:21 192.168.122.209 [47531.792949] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:16:23 192.168.122.209 [47533.960587] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47533.960587] Maybe that's fine, but it's worth checking the [47533.960587] config - if there is no relations between the [47533.960587] names, then host name confusion attack is possible. Apr 26 05:16:23 192.168.122.209 [47534.175308] [tempesta fw] Configuration processing is completed. Apr 26 05:16:23 192.168.122.209 [47534.295607] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 05:16:23 192.168.122.209 [47534.381272] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000003038fc3d Apr 26 05:16:24 192.168.122.209 [47534.408432] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000d11db51e Apr 26 05:16:24 192.168.122.209 [47534.834991] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6070ba4 Apr 26 05:16:24 192.168.122.209 [47534.862014] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000a968d47d Apr 26 05:16:24 192.168.122.209 [47534.887852] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000007aec66b3 Apr 26 05:16:24 192.168.122.209 [47534.959320] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:16:24 192.168.122.209 [47535.011288] [tempesta fw] Tempesta FW is ready Apr 26 05:16:24 192.168.122.209 [47535.210404] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=1271f8cc2c4c0011" "ja5h=65636588000c0180" Apr 26 05:16:24 192.168.122.209 [47535.302906] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=1271f8cc2c4c0011" "ja5h=65636588000c0180" Apr 26 05:16:25 192.168.122.209 [47535.888286] [tdb] Close table 'client0.tdb' Apr 26 05:16:25 192.168.122.209 [47536.105671] [tdb] Close table 'sessions0.tdb' Apr 26 05:16:28 192.168.122.209 [47539.280374] [tdb] Close table 'cache0.tdb' Apr 26 05:16:29 192.168.122.209 [47539.498367] [tdb] Close table 'filter0.tdb' Apr 26 05:16:29 192.168.122.209 [47540.170315] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 05:16:29 192.168.122.209 [47540.170768] [tempesta fw] modules are stopped Apr 26 05:16:30 192.168.122.209 [47540.484933] [tempesta fw] exiting... Apr 26 05:16:30 192.168.122.209 [47541.209254] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 05:16:30 192.168.122.209 [47541.260140] [tdb] Shutdown Tempesta DB Apr 26 05:16:31 192.168.122.209 [47542.396501] [tdb] Start Tempesta DB Apr 26 05:16:32 192.168.122.209 [47542.518505] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:16:34 192.168.122.209 [47544.531953] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47544.531953] Maybe that's fine, but it's worth checking the [47544.531953] config - if there is no relations between the [47544.531953] names, then host name confusion attack is possible. Apr 26 05:16:34 192.168.122.209 [47544.747444] [tempesta fw] Configuration processing is completed. Apr 26 05:16:34 192.168.122.209 [47544.856295] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 05:16:34 192.168.122.209 [47544.941926] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000003038fc3d Apr 26 05:16:34 192.168.122.209 [47544.968744] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000d11db51e Apr 26 05:16:34 192.168.122.209 [47545.387511] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6070ba4 Apr 26 05:16:35 192.168.122.209 [47545.413487] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000a968d47d Apr 26 05:16:35 192.168.122.209 [47545.439100] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000007aec66b3 Apr 26 05:16:35 192.168.122.209 [47545.595466] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:16:35 192.168.122.209 [47545.699413] [tempesta fw] Tempesta FW is ready Apr 26 05:16:35 192.168.122.209 [47545.824334] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=1271f8cc2c4c0011" "ja5h=65636588000c0180" Apr 26 05:16:35 192.168.122.209 [47546.332530] [tdb] Close table 'client0.tdb' Apr 26 05:16:36 192.168.122.209 [47546.535838] [tdb] Close table 'sessions0.tdb' Apr 26 05:16:39 192.168.122.209 [47549.664876] [tdb] Close table 'cache0.tdb' Apr 26 05:16:39 192.168.122.209 [47549.913608] [tdb] Close table 'filter0.tdb' Apr 26 05:16:40 192.168.122.209 [47550.562823] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 05:16:40 192.168.122.209 [47550.563279] [tempesta fw] modules are stopped Apr 26 05:16:40 192.168.122.209 [47550.906844] [tempesta fw] exiting... Apr 26 05:16:41 192.168.122.209 [47551.605861] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 05:16:41 192.168.122.209 [47551.669575] [tdb] Shutdown Tempesta DB Apr 26 05:16:41 192.168.122.209 [47551.906270] End test: t_ja5.test_ja5_filters.TestRestartAppWithUpdatedHashJa5t.test_hot_reload Apr 26 05:16:41 192.168.122.209 [47551.925738] Start test: t_ja5.test_ja5_filters.TestRestartAppWithUpdatedHashJa5t.test_restart_ok Apr 26 05:16:42 192.168.122.209 [47553.154750] [tdb] Start Tempesta DB Apr 26 05:16:42 192.168.122.209 [47553.293403] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:16:44 192.168.122.209 [47555.392991] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47555.392991] Maybe that's fine, but it's worth checking the [47555.392991] config - if there is no relations between the [47555.392991] names, then host name confusion attack is possible. Apr 26 05:16:45 192.168.122.209 [47555.615578] [tempesta fw] Configuration processing is completed. Apr 26 05:16:45 192.168.122.209 [47555.722460] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 05:16:45 192.168.122.209 [47555.805746] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000003038fc3d Apr 26 05:16:45 192.168.122.209 [47555.831726] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000d11db51e Apr 26 05:16:45 192.168.122.209 [47556.233938] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6070ba4 Apr 26 05:16:45 192.168.122.209 [47556.259387] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000a968d47d Apr 26 05:16:45 192.168.122.209 [47556.284778] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000007aec66b3 Apr 26 05:16:45 192.168.122.209 [47556.347606] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:16:45 192.168.122.209 [47556.387547] [tempesta fw] Tempesta FW is ready Apr 26 05:16:46 192.168.122.209 [47556.993812] [tdb] Close table 'client0.tdb' Apr 26 05:16:46 192.168.122.209 [47557.207061] [tdb] Close table 'sessions0.tdb' Apr 26 05:16:50 192.168.122.209 [47560.412841] [tdb] Close table 'cache0.tdb' Apr 26 05:16:50 192.168.122.209 [47560.655659] [tdb] Close table 'filter0.tdb' Apr 26 05:16:50 192.168.122.209 [47561.295374] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 05:16:50 192.168.122.209 [47561.295838] [tempesta fw] modules are stopped Apr 26 05:16:51 192.168.122.209 [47561.557048] [tempesta fw] exiting... Apr 26 05:16:51 192.168.122.209 [47562.238686] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 05:16:51 192.168.122.209 [47562.278832] [tdb] Shutdown Tempesta DB Apr 26 05:16:53 192.168.122.209 [47563.539725] [tdb] Start Tempesta DB Apr 26 05:16:53 192.168.122.209 [47563.672792] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:16:55 192.168.122.209 [47565.924926] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47565.924926] Maybe that's fine, but it's worth checking the [47565.924926] config - if there is no relations between the [47565.924926] names, then host name confusion attack is possible. Apr 26 05:16:55 192.168.122.209 [47566.127717] [tempesta fw] Configuration processing is completed. Apr 26 05:16:55 192.168.122.209 [47566.237426] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 05:16:55 192.168.122.209 [47566.321514] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000003038fc3d Apr 26 05:16:55 192.168.122.209 [47566.348459] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000d11db51e Apr 26 05:16:56 192.168.122.209 [47566.766215] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6070ba4 Apr 26 05:16:56 192.168.122.209 [47566.803810] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000a968d47d Apr 26 05:16:56 192.168.122.209 [47566.829006] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000007aec66b3 Apr 26 05:16:56 192.168.122.209 [47566.887682] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:16:56 192.168.122.209 [47566.931683] [tempesta fw] Tempesta FW is ready Apr 26 05:16:57 192.168.122.209 [47567.478543] [tdb] Close table 'client0.tdb' Apr 26 05:16:57 192.168.122.209 [47567.687280] [tdb] Close table 'sessions0.tdb' Apr 26 05:17:00 192.168.122.209 [47570.842724] [tdb] Close table 'cache0.tdb' Apr 26 05:17:00 192.168.122.209 [47571.081031] [tdb] Close table 'filter0.tdb' Apr 26 05:17:01 192.168.122.209 [47571.746770] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 05:17:01 192.168.122.209 [47571.747225] [tempesta fw] modules are stopped Apr 26 05:17:01 192.168.122.209 [47572.005095] [tempesta fw] exiting... Apr 26 05:17:02 192.168.122.209 [47572.707008] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 05:17:02 192.168.122.209 [47572.760824] [tdb] Shutdown Tempesta DB Apr 26 05:17:02 192.168.122.209 [47573.024849] End test: t_ja5.test_ja5_filters.TestRestartAppWithUpdatedHashJa5t.test_restart_ok Apr 26 05:17:02 192.168.122.209 [47573.036408] Start test: t_ja5.test_ja5t.TestJa5tH2.test_hash_for_client_block_by_conn Apr 26 05:17:03 192.168.122.209 [47574.190173] [tdb] Start Tempesta DB Apr 26 05:17:03 192.168.122.209 [47574.325203] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:17:05 192.168.122.209 [47576.381505] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47576.381505] Maybe that's fine, but it's worth checking the [47576.381505] config - if there is no relations between the [47576.381505] names, then host name confusion attack is possible. Apr 26 05:17:06 192.168.122.209 [47576.495924] [tempesta fw] Configuration processing is completed. Apr 26 05:17:06 192.168.122.209 [47576.617766] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 05:17:06 192.168.122.209 [47576.645359] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=000000004552ac63 Apr 26 05:17:06 192.168.122.209 [47577.058377] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=000000002cb2aedf Apr 26 05:17:06 192.168.122.209 [47577.084275] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000f7dd6c76 Apr 26 05:17:06 192.168.122.209 [47577.109979] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000004da5e5e5 Apr 26 05:17:06 192.168.122.209 [47577.159861] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:17:06 192.168.122.209 [47577.215818] [tempesta fw] Tempesta FW is ready Apr 26 05:17:07 192.168.122.209 [47577.799200] [tdb] Close table 'client0.tdb' Apr 26 05:17:07 192.168.122.209 [47577.983322] [tdb] Close table 'sessions0.tdb' Apr 26 05:17:10 192.168.122.209 [47581.122048] [tdb] Close table 'cache0.tdb' Apr 26 05:17:10 192.168.122.209 [47581.349710] [tdb] Close table 'filter0.tdb' Apr 26 05:17:10 192.168.122.209 [47581.350277] [tempesta fw] modules are stopped Apr 26 05:17:11 192.168.122.209 [47581.621026] [tempesta fw] exiting... Apr 26 05:17:11 192.168.122.209 [47582.321312] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 05:17:11 192.168.122.209 [47582.356335] [tdb] Shutdown Tempesta DB Apr 26 05:17:12 192.168.122.209 [47582.554524] End test: t_ja5.test_ja5t.TestJa5tH2.test_hash_for_client_block_by_conn Apr 26 05:17:12 192.168.122.209 [47582.568335] Start test: t_ja5.test_ja5t.TestJa5tH2.test_hash_for_client_block_by_rate Apr 26 05:17:13 192.168.122.209 [47583.752422] [tdb] Start Tempesta DB Apr 26 05:17:13 192.168.122.209 [47583.888275] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:17:15 192.168.122.209 [47585.649585] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47585.649585] Maybe that's fine, but it's worth checking the [47585.649585] config - if there is no relations between the [47585.649585] names, then host name confusion attack is possible. Apr 26 05:17:15 192.168.122.209 [47585.756134] [tempesta fw] Configuration processing is completed. Apr 26 05:17:15 192.168.122.209 [47585.865209] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 05:17:15 192.168.122.209 [47585.892572] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=000000004552ac63 Apr 26 05:17:15 192.168.122.209 [47586.300814] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=000000002cb2aedf Apr 26 05:17:15 192.168.122.209 [47586.357961] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000f7dd6c76 Apr 26 05:17:15 192.168.122.209 [47586.390998] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000004da5e5e5 Apr 26 05:17:16 192.168.122.209 [47586.680001] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:17:16 192.168.122.209 [47586.739931] [tempesta fw] Tempesta FW is ready Apr 26 05:17:17 192.168.122.209 [47588.263759] [tdb] Close table 'client0.tdb' Apr 26 05:17:18 192.168.122.209 [47588.526212] [tdb] Close table 'sessions0.tdb' Apr 26 05:17:22 192.168.122.209 [47592.928406] [tdb] Close table 'cache0.tdb' Apr 26 05:17:22 192.168.122.209 [47593.156322] [tdb] Close table 'filter0.tdb' Apr 26 05:17:22 192.168.122.209 [47593.156758] [tempesta fw] modules are stopped Apr 26 05:17:22 192.168.122.209 [47593.389983] [tempesta fw] exiting... Apr 26 05:17:23 192.168.122.209 [47594.096680] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 05:17:23 192.168.122.209 [47594.141842] [tdb] Shutdown Tempesta DB Apr 26 05:17:23 192.168.122.209 [47594.391035] End test: t_ja5.test_ja5t.TestJa5tH2.test_hash_for_client_block_by_rate Apr 26 05:17:24 192.168.122.209 [47594.405570] Start test: t_ja5.test_ja5t.TestJa5tH2.test_hash_for_client_not_block Apr 26 05:17:25 192.168.122.209 [47595.558004] [tdb] Start Tempesta DB Apr 26 05:17:25 192.168.122.209 [47595.692020] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:17:26 192.168.122.209 [47597.377756] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47597.377756] Maybe that's fine, but it's worth checking the [47597.377756] config - if there is no relations between the [47597.377756] names, then host name confusion attack is possible. Apr 26 05:17:27 192.168.122.209 [47597.476175] [tempesta fw] Configuration processing is completed. Apr 26 05:17:27 192.168.122.209 [47597.590560] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 05:17:27 192.168.122.209 [47597.619128] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=000000004552ac63 Apr 26 05:17:27 192.168.122.209 [47598.045847] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=000000002cb2aedf Apr 26 05:17:27 192.168.122.209 [47598.072384] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000f7dd6c76 Apr 26 05:17:27 192.168.122.209 [47598.098900] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000004da5e5e5 Apr 26 05:17:27 192.168.122.209 [47598.136061] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:17:27 192.168.122.209 [47598.176111] [tempesta fw] Tempesta FW is ready Apr 26 05:17:28 192.168.122.209 [47598.749610] [tdb] Close table 'client0.tdb' Apr 26 05:17:28 192.168.122.209 [47598.966690] [tdb] Close table 'sessions0.tdb' Apr 26 05:17:31 192.168.122.209 [47602.083027] [tdb] Close table 'cache0.tdb' Apr 26 05:17:31 192.168.122.209 [47602.312405] [tdb] Close table 'filter0.tdb' Apr 26 05:17:31 192.168.122.209 [47602.312838] [tempesta fw] modules are stopped Apr 26 05:17:32 192.168.122.209 [47602.548626] [tempesta fw] exiting... Apr 26 05:17:32 192.168.122.209 [47603.235037] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 05:17:32 192.168.122.209 [47603.277583] [tdb] Shutdown Tempesta DB Apr 26 05:17:33 192.168.122.209 [47603.485156] End test: t_ja5.test_ja5t.TestJa5tH2.test_hash_for_client_not_block Apr 26 05:17:33 192.168.122.209 [47603.499554] Start test: t_ja5.test_ja5t.TestJa5tH2.test_hash_not_for_client Apr 26 05:17:34 192.168.122.209 [47604.626673] [tdb] Start Tempesta DB Apr 26 05:17:34 192.168.122.209 [47604.770608] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:17:36 192.168.122.209 [47606.461758] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47606.461758] Maybe that's fine, but it's worth checking the [47606.461758] config - if there is no relations between the [47606.461758] names, then host name confusion attack is possible. Apr 26 05:17:36 192.168.122.209 [47606.584309] [tempesta fw] Configuration processing is completed. Apr 26 05:17:36 192.168.122.209 [47606.690956] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 05:17:36 192.168.122.209 [47606.717762] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=000000004552ac63 Apr 26 05:17:36 192.168.122.209 [47607.128973] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=000000002cb2aedf Apr 26 05:17:36 192.168.122.209 [47607.185561] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000f7dd6c76 Apr 26 05:17:36 192.168.122.209 [47607.212734] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000004da5e5e5 Apr 26 05:17:36 192.168.122.209 [47607.252178] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:17:36 192.168.122.209 [47607.296180] [tempesta fw] Tempesta FW is ready Apr 26 05:17:37 192.168.122.209 [47607.901756] [tdb] Close table 'client0.tdb' Apr 26 05:17:37 192.168.122.209 [47608.095352] [tdb] Close table 'sessions0.tdb' Apr 26 05:17:40 192.168.122.209 [47611.265753] [tdb] Close table 'cache0.tdb' Apr 26 05:17:41 192.168.122.209 [47611.506013] [tdb] Close table 'filter0.tdb' Apr 26 05:17:41 192.168.122.209 [47611.506473] [tempesta fw] modules are stopped Apr 26 05:17:41 192.168.122.209 [47611.726820] [tempesta fw] exiting... Apr 26 05:17:42 192.168.122.209 [47612.426650] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 05:17:42 192.168.122.209 [47612.464032] [tdb] Shutdown Tempesta DB Apr 26 05:17:42 192.168.122.209 [47612.679675] End test: t_ja5.test_ja5t.TestJa5tH2.test_hash_not_for_client Apr 26 05:17:42 192.168.122.209 [47612.690682] Start test: t_ja5.test_ja5t.TestJa5tH2.test_no_hash Apr 26 05:17:43 192.168.122.209 [47613.918541] [tdb] Start Tempesta DB Apr 26 05:17:43 192.168.122.209 [47614.070271] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:17:45 192.168.122.209 [47615.705498] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47615.705498] Maybe that's fine, but it's worth checking the [47615.705498] config - if there is no relations between the [47615.705498] names, then host name confusion attack is possible. Apr 26 05:17:45 192.168.122.209 [47615.792379] [tempesta fw] Configuration processing is completed. Apr 26 05:17:45 192.168.122.209 [47615.858324] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:17:45 192.168.122.209 [47616.363939] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:17:45 192.168.122.209 [47616.396483] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:17:46 192.168.122.209 [47616.440814] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:17:46 192.168.122.209 [47616.484286] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:17:46 192.168.122.209 [47616.528329] [tempesta fw] Tempesta FW is ready Apr 26 05:17:46 192.168.122.209 [47617.133094] [tdb] Close table 'client0.tdb' Apr 26 05:17:46 192.168.122.209 [47617.317222] [tdb] Close table 'sessions0.tdb' Apr 26 05:17:50 192.168.122.209 [47620.493950] [tdb] Close table 'cache0.tdb' Apr 26 05:17:50 192.168.122.209 [47620.711170] [tdb] Close table 'filter0.tdb' Apr 26 05:17:50 192.168.122.209 [47620.711614] [tempesta fw] modules are stopped Apr 26 05:17:50 192.168.122.209 [47620.937621] [tempesta fw] exiting... Apr 26 05:17:50 192.168.122.209 [47621.092156] [tdb] Shutdown Tempesta DB Apr 26 05:17:50 192.168.122.209 [47621.317559] End test: t_ja5.test_ja5t.TestJa5tH2.test_no_hash Apr 26 05:17:50 192.168.122.209 [47621.328059] Start test: t_ja5.test_ja5t.TestJa5tHttp.test_hash_for_client_block_by_conn Apr 26 05:17:51 192.168.122.209 [47622.404115] [tdb] Start Tempesta DB Apr 26 05:17:52 192.168.122.209 [47622.547518] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:17:53 192.168.122.209 [47624.122037] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47624.122037] Maybe that's fine, but it's worth checking the [47624.122037] config - if there is no relations between the [47624.122037] names, then host name confusion attack is possible. Apr 26 05:17:53 192.168.122.209 [47624.236433] [tempesta fw] Configuration processing is completed. Apr 26 05:17:53 192.168.122.209 [47624.351787] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 05:17:53 192.168.122.209 [47624.381575] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=000000004552ac63 Apr 26 05:17:54 192.168.122.209 [47624.822761] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=000000002cb2aedf Apr 26 05:17:54 192.168.122.209 [47624.854737] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000f7dd6c76 Apr 26 05:17:54 192.168.122.209 [47624.886438] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000004da5e5e5 Apr 26 05:17:54 192.168.122.209 [47624.936432] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:17:54 192.168.122.209 [47624.980395] [tempesta fw] Tempesta FW is ready Apr 26 05:17:55 192.168.122.209 [47625.566681] [tdb] Close table 'client0.tdb' Apr 26 05:17:55 192.168.122.209 [47625.757343] [tdb] Close table 'sessions0.tdb' Apr 26 05:17:58 192.168.122.209 [47628.935652] [tdb] Close table 'cache0.tdb' Apr 26 05:17:58 192.168.122.209 [47629.157464] [tdb] Close table 'filter0.tdb' Apr 26 05:17:58 192.168.122.209 [47629.157913] [tempesta fw] modules are stopped Apr 26 05:17:58 192.168.122.209 [47629.397076] [tempesta fw] exiting... Apr 26 05:17:59 192.168.122.209 [47630.102818] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 05:17:59 192.168.122.209 [47630.159386] [tdb] Shutdown Tempesta DB Apr 26 05:17:59 192.168.122.209 [47630.397786] End test: t_ja5.test_ja5t.TestJa5tHttp.test_hash_for_client_block_by_conn Apr 26 05:18:00 192.168.122.209 [47630.410846] Start test: t_ja5.test_ja5t.TestJa5tHttp.test_hash_for_client_block_by_rate Apr 26 05:18:01 192.168.122.209 [47631.540362] [tdb] Start Tempesta DB Apr 26 05:18:01 192.168.122.209 [47631.687363] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:18:03 192.168.122.209 [47633.414169] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47633.414169] Maybe that's fine, but it's worth checking the [47633.414169] config - if there is no relations between the [47633.414169] names, then host name confusion attack is possible. Apr 26 05:18:03 192.168.122.209 [47633.544602] [tempesta fw] Configuration processing is completed. Apr 26 05:18:03 192.168.122.209 [47633.655678] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 05:18:03 192.168.122.209 [47633.685209] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=000000004552ac63 Apr 26 05:18:03 192.168.122.209 [47634.159278] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=000000002cb2aedf Apr 26 05:18:03 192.168.122.209 [47634.188047] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000f7dd6c76 Apr 26 05:18:03 192.168.122.209 [47634.217886] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000004da5e5e5 Apr 26 05:18:03 192.168.122.209 [47634.256526] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:18:03 192.168.122.209 [47634.300519] [tempesta fw] Tempesta FW is ready Apr 26 05:18:04 192.168.122.209 [47634.860391] [tdb] Close table 'client0.tdb' Apr 26 05:18:04 192.168.122.209 [47635.051851] [tdb] Close table 'sessions0.tdb' Apr 26 05:18:07 192.168.122.209 [47638.372300] [tdb] Close table 'cache0.tdb' Apr 26 05:18:08 192.168.122.209 [47638.636276] [tdb] Close table 'filter0.tdb' Apr 26 05:18:08 192.168.122.209 [47638.636732] [tempesta fw] modules are stopped Apr 26 05:18:08 192.168.122.209 [47638.850483] [tempesta fw] exiting... Apr 26 05:18:09 192.168.122.209 [47639.626151] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 05:18:09 192.168.122.209 [47639.677347] [tdb] Shutdown Tempesta DB Apr 26 05:18:09 192.168.122.209 [47639.879994] End test: t_ja5.test_ja5t.TestJa5tHttp.test_hash_for_client_block_by_rate Apr 26 05:18:09 192.168.122.209 [47639.906152] Start test: t_ja5.test_ja5t.TestJa5tHttp.test_hash_for_client_not_block Apr 26 05:18:10 192.168.122.209 [47641.032727] [tdb] Start Tempesta DB Apr 26 05:18:10 192.168.122.209 [47641.175213] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:18:12 192.168.122.209 [47642.894163] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47642.894163] Maybe that's fine, but it's worth checking the [47642.894163] config - if there is no relations between the [47642.894163] names, then host name confusion attack is possible. Apr 26 05:18:12 192.168.122.209 [47642.996741] [tempesta fw] Configuration processing is completed. Apr 26 05:18:12 192.168.122.209 [47643.115581] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 05:18:12 192.168.122.209 [47643.145365] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=000000004552ac63 Apr 26 05:18:13 192.168.122.209 [47643.661829] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=000000002cb2aedf Apr 26 05:18:13 192.168.122.209 [47643.733257] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000f7dd6c76 Apr 26 05:18:13 192.168.122.209 [47643.769209] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000004da5e5e5 Apr 26 05:18:13 192.168.122.209 [47643.816647] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:18:13 192.168.122.209 [47643.856646] [tempesta fw] Tempesta FW is ready Apr 26 05:18:14 192.168.122.209 [47644.486555] [tdb] Close table 'client0.tdb' Apr 26 05:18:14 192.168.122.209 [47644.680997] [tdb] Close table 'sessions0.tdb' Apr 26 05:18:17 192.168.122.209 [47648.026078] [tdb] Close table 'cache0.tdb' Apr 26 05:18:17 192.168.122.209 [47648.289765] [tdb] Close table 'filter0.tdb' Apr 26 05:18:17 192.168.122.209 [47648.290237] [tempesta fw] modules are stopped Apr 26 05:18:18 192.168.122.209 [47648.498823] [tempesta fw] exiting... Apr 26 05:18:18 192.168.122.209 [47649.190372] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 05:18:18 192.168.122.209 [47649.239386] [tdb] Shutdown Tempesta DB Apr 26 05:18:19 192.168.122.209 [47649.472744] End test: t_ja5.test_ja5t.TestJa5tHttp.test_hash_for_client_not_block Apr 26 05:18:19 192.168.122.209 [47649.488731] Start test: t_ja5.test_ja5t.TestJa5tHttp.test_hash_not_for_client Apr 26 05:18:20 192.168.122.209 [47650.691969] [tdb] Start Tempesta DB Apr 26 05:18:20 192.168.122.209 [47650.842360] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:18:22 192.168.122.209 [47652.554526] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47652.554526] Maybe that's fine, but it's worth checking the [47652.554526] config - if there is no relations between the [47652.554526] names, then host name confusion attack is possible. Apr 26 05:18:22 192.168.122.209 [47652.652865] [tempesta fw] Configuration processing is completed. Apr 26 05:18:22 192.168.122.209 [47652.777889] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 05:18:22 192.168.122.209 [47652.805302] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=000000004552ac63 Apr 26 05:18:22 192.168.122.209 [47653.212224] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=000000002cb2aedf Apr 26 05:18:22 192.168.122.209 [47653.238931] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000f7dd6c76 Apr 26 05:18:22 192.168.122.209 [47653.271596] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000004da5e5e5 Apr 26 05:18:22 192.168.122.209 [47653.320834] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:18:22 192.168.122.209 [47653.360760] [tempesta fw] Tempesta FW is ready Apr 26 05:18:23 192.168.122.209 [47653.993035] [tdb] Close table 'client0.tdb' Apr 26 05:18:23 192.168.122.209 [47654.188323] [tdb] Close table 'sessions0.tdb' Apr 26 05:18:26 192.168.122.209 [47657.349685] [tdb] Close table 'cache0.tdb' Apr 26 05:18:27 192.168.122.209 [47657.576436] [tdb] Close table 'filter0.tdb' Apr 26 05:18:27 192.168.122.209 [47657.577280] [tempesta fw] modules are stopped Apr 26 05:18:27 192.168.122.209 [47657.841936] [tempesta fw] exiting... Apr 26 05:18:28 192.168.122.209 [47658.530545] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 05:18:28 192.168.122.209 [47658.565558] [tdb] Shutdown Tempesta DB Apr 26 05:18:28 192.168.122.209 [47658.782416] End test: t_ja5.test_ja5t.TestJa5tHttp.test_hash_not_for_client Apr 26 05:18:28 192.168.122.209 [47658.810464] Start test: t_ja5.test_ja5t.TestJa5tHttp.test_no_hash Apr 26 05:18:29 192.168.122.209 [47659.964496] [tdb] Start Tempesta DB Apr 26 05:18:29 192.168.122.209 [47660.104916] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:18:31 192.168.122.209 [47661.641797] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47661.641797] Maybe that's fine, but it's worth checking the [47661.641797] config - if there is no relations between the [47661.641797] names, then host name confusion attack is possible. Apr 26 05:18:31 192.168.122.209 [47661.724986] [tempesta fw] Configuration processing is completed. Apr 26 05:18:31 192.168.122.209 [47661.776574] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:18:31 192.168.122.209 [47662.214827] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:18:31 192.168.122.209 [47662.242518] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:18:31 192.168.122.209 [47662.269699] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:18:31 192.168.122.209 [47662.308938] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:18:31 192.168.122.209 [47662.348881] [tempesta fw] Tempesta FW is ready Apr 26 05:18:32 192.168.122.209 [47662.940586] [tdb] Close table 'client0.tdb' Apr 26 05:18:32 192.168.122.209 [47663.123082] [tdb] Close table 'sessions0.tdb' Apr 26 05:18:35 192.168.122.209 [47666.292721] [tdb] Close table 'cache0.tdb' Apr 26 05:18:36 192.168.122.209 [47666.525571] [tdb] Close table 'filter0.tdb' Apr 26 05:18:36 192.168.122.209 [47666.526013] [tempesta fw] modules are stopped Apr 26 05:18:36 192.168.122.209 [47666.717700] [tempesta fw] exiting... Apr 26 05:18:36 192.168.122.209 [47666.841800] [tdb] Shutdown Tempesta DB Apr 26 05:18:36 192.168.122.209 [47667.063277] End test: t_ja5.test_ja5t.TestJa5tHttp.test_no_hash Apr 26 05:18:36 192.168.122.209 [47667.079204] Start test: t_ja5.test_ja5t.TestJa5tStress.test_H2 Apr 26 05:18:37 192.168.122.209 [47668.233709] [tdb] Start Tempesta DB Apr 26 05:18:37 192.168.122.209 [47668.360131] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:18:39 192.168.122.209 [47669.778568] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47669.778568] Maybe that's fine, but it's worth checking the [47669.778568] config - if there is no relations between the [47669.778568] names, then host name confusion attack is possible. Apr 26 05:18:39 192.168.122.209 [47669.860984] [tempesta fw] Configuration processing is completed. Apr 26 05:18:39 192.168.122.209 [47669.912756] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:18:39 192.168.122.209 [47670.347860] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:18:39 192.168.122.209 [47670.374979] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:18:39 192.168.122.209 [47670.401605] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:18:40 192.168.122.209 [47670.440956] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:18:40 192.168.122.209 [47670.476975] [tempesta fw] Tempesta FW is ready Apr 26 05:18:40 192.168.122.209 [47671.136581] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:18:40 192.168.122.209 [47671.205533] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47671.205533] Maybe that's fine, but it's worth checking the [47671.205533] config - if there is no relations between the [47671.205533] names, then host name confusion attack is possible. Apr 26 05:18:40 192.168.122.209 [47671.297078] [tempesta fw] Configuration processing is completed. Apr 26 05:18:41 192.168.122.209 [47671.493031] [tempesta fw] Warning: request dropped: unable to find an available back end server, status 502: 127.0.0.1 Apr 26 05:18:41 192.168.122.209 [47671.493036] [tempesta fw] Warning: request dropped: unable to find an available back end server, status 502: 127.0.0.1 Apr 26 05:18:41 192.168.122.209 [47671.757747] [tempesta fw] Tempesta FW is ready Apr 26 05:18:42 192.168.122.209 [47672.488155] net_ratelimit: 990 callbacks suppressed Apr 26 05:18:42 192.168.122.209 [47672.488157] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:18:42 192.168.122.209 [47672.582253] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47672.582253] Maybe that's fine, but it's worth checking the [47672.582253] config - if there is no relations between the [47672.582253] names, then host name confusion attack is possible. Apr 26 05:18:42 192.168.122.209 [47672.677106] [tempesta fw] Configuration processing is completed. Apr 26 05:18:42 192.168.122.209 [47672.822407] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=000000004da5e5e5 Apr 26 05:18:42 192.168.122.209 [47672.865201] [tempesta fw] Warning: request dropped: unable to find an available back end server, status 502: 127.0.0.1 Apr 26 05:18:42 192.168.122.209 [47672.865208] [tempesta fw] Warning: request dropped: unable to find an available back end server, status 502: 127.0.0.1 Apr 26 05:18:42 192.168.122.209 [47672.865231] [tempesta fw] Warning: request dropped: unable to find an available back end server, status 502: 127.0.0.1 Apr 26 05:18:42 192.168.122.209 [47672.865245] [tempesta fw] Warning: request dropped: unable to find an available back end server, status 502: 127.0.0.1 Apr 26 05:18:42 192.168.122.209 [47672.865259] [tempesta fw] Warning: request dropped: unable to find an available back end server, status 502: 127.0.0.1 Apr 26 05:18:42 192.168.122.209 [47672.865274] [tempesta fw] Warning: request dropped: unable to find an available back end server, status 502: 127.0.0.1 Apr 26 05:18:42 192.168.122.209 [47672.865289] [tempesta fw] Warning: request dropped: unable to find an available back end server, status 502: 127.0.0.1 Apr 26 05:18:43 192.168.122.209 [47673.529302] [tempesta fw] Tempesta FW is ready Apr 26 05:18:45 192.168.122.209 [47676.222033] [tempesta fw] Tempesta FW is ready Apr 26 05:18:47 192.168.122.209 [47677.543601] net_ratelimit: 1985 callbacks suppressed Apr 26 05:18:47 192.168.122.209 [47677.543603] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:18:47 192.168.122.209 [47677.645722] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47677.645722] Maybe that's fine, but it's worth checking the [47677.645722] config - if there is no relations between the [47677.645722] names, then host name confusion attack is possible. Apr 26 05:18:47 192.168.122.209 [47677.725183] [tempesta fw] Configuration processing is completed. Apr 26 05:18:47 192.168.122.209 [47677.904657] [tempesta fw] Warning: request dropped: unable to find an available back end server, status 502: 127.0.0.1 Apr 26 05:18:47 192.168.122.209 [47677.904666] [tempesta fw] Warning: request dropped: unable to find an available back end server, status 502: 127.0.0.1 Apr 26 05:18:47 192.168.122.209 [47677.904679] [tempesta fw] Warning: request dropped: unable to find an available back end server, status 502: 127.0.0.1 Apr 26 05:18:47 192.168.122.209 [47677.904694] [tempesta fw] Warning: request dropped: unable to find an available back end server, status 502: 127.0.0.1 Apr 26 05:18:47 192.168.122.209 [47677.904728] [tempesta fw] Warning: request dropped: unable to find an available back end server, status 502: 127.0.0.1 Apr 26 05:18:47 192.168.122.209 [47677.904733] [tempesta fw] Warning: request dropped: unable to find an available back end server, status 502: 127.0.0.1 Apr 26 05:18:47 192.168.122.209 [47677.904742] [tempesta fw] Warning: request dropped: unable to find an available back end server, status 502: 127.0.0.1 Apr 26 05:18:48 192.168.122.209 [47678.958048] [tempesta fw] Tempesta FW is ready Apr 26 05:18:50 192.168.122.209 [47681.273606] [tempesta fw] Tempesta FW is ready Apr 26 05:18:51 192.168.122.209 [47682.385690] [tempesta fw] Tempesta FW is ready Apr 26 05:18:52 192.168.122.209 [47682.797576] net_ratelimit: 877 callbacks suppressed Apr 26 05:18:52 192.168.122.209 [47682.797578] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:18:52 192.168.122.209 [47682.870464] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47682.870464] Maybe that's fine, but it's worth checking the [47682.870464] config - if there is no relations between the [47682.870464] names, then host name confusion attack is possible. Apr 26 05:18:52 192.168.122.209 [47682.965226] [tempesta fw] Configuration processing is completed. Apr 26 05:18:52 192.168.122.209 [47683.205669] [tempesta fw] Tempesta FW is ready Apr 26 05:18:53 192.168.122.209 [47683.711100] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:18:53 192.168.122.209 [47683.798402] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47683.798402] Maybe that's fine, but it's worth checking the [47683.798402] config - if there is no relations between the [47683.798402] names, then host name confusion attack is possible. Apr 26 05:18:53 192.168.122.209 [47683.941232] [tempesta fw] Configuration processing is completed. Apr 26 05:18:53 192.168.122.209 [47684.217545] [tempesta fw] Tempesta FW is ready Apr 26 05:18:54 192.168.122.209 [47684.755727] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:18:54 192.168.122.209 [47684.838570] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47684.838570] Maybe that's fine, but it's worth checking the [47684.838570] config - if there is no relations between the [47684.838570] names, then host name confusion attack is possible. Apr 26 05:18:54 192.168.122.209 [47684.977328] [tempesta fw] Configuration processing is completed. Apr 26 05:18:54 192.168.122.209 [47685.285663] [tempesta fw] Tempesta FW is ready Apr 26 05:18:55 192.168.122.209 [47685.778946] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:18:55 192.168.122.209 [47686.201659] [tempesta fw] Tempesta FW is ready Apr 26 05:18:56 192.168.122.209 [47687.205681] [tempesta fw] Tempesta FW is ready Apr 26 05:18:57 192.168.122.209 [47687.822413] net_ratelimit: 6 callbacks suppressed Apr 26 05:18:57 192.168.122.209 [47687.822422] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47687.822422] Maybe that's fine, but it's worth checking the [47687.822422] config - if there is no relations between the [47687.822422] names, then host name confusion attack is possible. Apr 26 05:18:57 192.168.122.209 [47687.973321] [tempesta fw] Configuration processing is completed. Apr 26 05:18:57 192.168.122.209 [47688.233668] [tempesta fw] Tempesta FW is ready Apr 26 05:18:58 192.168.122.209 [47688.714245] [tdb] Close table 'client0.tdb' Apr 26 05:18:58 192.168.122.209 [47688.924194] [tdb] Close table 'sessions0.tdb' Apr 26 05:19:01 192.168.122.209 [47692.352142] [tdb] Close table 'cache0.tdb' Apr 26 05:19:02 192.168.122.209 [47692.664842] [tdb] Close table 'filter0.tdb' Apr 26 05:19:02 192.168.122.209 [47692.665313] [tempesta fw] modules are stopped Apr 26 05:19:02 192.168.122.209 [47692.894347] [tempesta fw] exiting... Apr 26 05:19:03 192.168.122.209 [47693.645053] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 05:19:03 192.168.122.209 [47693.687174] [tdb] Shutdown Tempesta DB Apr 26 05:19:03 192.168.122.209 [47693.972977] End test: t_ja5.test_ja5t.TestJa5tStress.test_H2 Apr 26 05:19:03 192.168.122.209 [47693.982330] Start test: t_ja5.test_ja5t.TestJa5tStress.test_Http Apr 26 05:19:04 192.168.122.209 [47695.258556] [tdb] Start Tempesta DB Apr 26 05:19:05 192.168.122.209 [47695.452009] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:19:06 192.168.122.209 [47697.115065] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47697.115065] Maybe that's fine, but it's worth checking the [47697.115065] config - if there is no relations between the [47697.115065] names, then host name confusion attack is possible. Apr 26 05:19:06 192.168.122.209 [47697.209435] [tempesta fw] Configuration processing is completed. Apr 26 05:19:06 192.168.122.209 [47697.278099] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:19:07 192.168.122.209 [47697.858599] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:19:07 192.168.122.209 [47697.893772] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:19:07 192.168.122.209 [47697.928454] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:19:07 192.168.122.209 [47698.009383] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:19:07 192.168.122.209 [47698.049303] [tempesta fw] Tempesta FW is ready Apr 26 05:19:08 192.168.122.209 [47698.787712] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:19:08 192.168.122.209 [47698.862824] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47698.862824] Maybe that's fine, but it's worth checking the [47698.862824] config - if there is no relations between the [47698.862824] names, then host name confusion attack is possible. Apr 26 05:19:08 192.168.122.209 [47698.953409] [tempesta fw] Configuration processing is completed. Apr 26 05:19:08 192.168.122.209 [47699.169541] [tempesta fw] Warning: request dropped: unable to find an available back end server, status 502: 127.0.0.1 Apr 26 05:19:08 192.168.122.209 [47699.169565] [tempesta fw] Warning: request dropped: unable to find an available back end server, status 502: 127.0.0.1 Apr 26 05:19:08 192.168.122.209 [47699.169591] [tempesta fw] Warning: request dropped: unable to find an available back end server, status 502: 127.0.0.1 Apr 26 05:19:09 192.168.122.209 [47699.873241] [tempesta fw] Tempesta FW is ready Apr 26 05:19:10 192.168.122.209 [47700.655740] net_ratelimit: 1001 callbacks suppressed Apr 26 05:19:10 192.168.122.209 [47700.655742] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:19:10 192.168.122.209 [47700.729887] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47700.729887] Maybe that's fine, but it's worth checking the [47700.729887] config - if there is no relations between the [47700.729887] names, then host name confusion attack is possible. Apr 26 05:19:10 192.168.122.209 [47700.873488] [tempesta fw] Configuration processing is completed. Apr 26 05:19:10 192.168.122.209 [47701.067785] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=000000004da5e5e5 Apr 26 05:19:10 192.168.122.209 [47701.157405] [tempesta fw] Warning: request dropped: unable to find an available back end server, status 502: 127.0.0.1 Apr 26 05:19:10 192.168.122.209 [47701.157478] [tempesta fw] Warning: request dropped: unable to find an available back end server, status 502: 127.0.0.1 Apr 26 05:19:10 192.168.122.209 [47701.157488] [tempesta fw] Warning: request dropped: unable to find an available back end server, status 502: 127.0.0.1 Apr 26 05:19:10 192.168.122.209 [47701.157498] [tempesta fw] Warning: request dropped: unable to find an available back end server, status 502: 127.0.0.1 Apr 26 05:19:10 192.168.122.209 [47701.157561] [tempesta fw] Warning: request dropped: unable to find an available back end server, status 502: 127.0.0.1 Apr 26 05:19:10 192.168.122.209 [47701.157567] [tempesta fw] Warning: request dropped: unable to find an available back end server, status 502: 127.0.0.1 Apr 26 05:19:10 192.168.122.209 [47701.157592] [tempesta fw] Warning: request dropped: unable to find an available back end server, status 502: 127.0.0.1 Apr 26 05:19:11 192.168.122.209 [47701.417935] [tempesta fw] Tempesta FW is ready Apr 26 05:19:13 192.168.122.209 [47703.930299] [tempesta fw] Tempesta FW is ready Apr 26 05:19:15 192.168.122.209 [47705.878256] [tempesta fw] Tempesta FW is ready Apr 26 05:19:17 192.168.122.209 [47707.661858] net_ratelimit: 2929 callbacks suppressed Apr 26 05:19:17 192.168.122.209 [47707.661861] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:19:17 192.168.122.209 [47707.755090] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47707.755090] Maybe that's fine, but it's worth checking the [47707.755090] config - if there is no relations between the [47707.755090] names, then host name confusion attack is possible. Apr 26 05:19:17 192.168.122.209 [47707.941755] [tempesta fw] Configuration processing is completed. Apr 26 05:19:17 192.168.122.209 [47708.111014] [tempesta fw] Warning: request dropped: unable to find an available back end server, status 502: 127.0.0.1 Apr 26 05:19:17 192.168.122.209 [47708.111023] [tempesta fw] Warning: request dropped: unable to find an available back end server, status 502: 127.0.0.1 Apr 26 05:19:17 192.168.122.209 [47708.111032] [tempesta fw] Warning: request dropped: unable to find an available back end server, status 502: 127.0.0.1 Apr 26 05:19:17 192.168.122.209 [47708.111050] [tempesta fw] Warning: request dropped: unable to find an available back end server, status 502: 127.0.0.1 Apr 26 05:19:17 192.168.122.209 [47708.111061] [tempesta fw] Warning: request dropped: unable to find an available back end server, status 502: 127.0.0.1 Apr 26 05:19:17 192.168.122.209 [47708.111072] [tempesta fw] Warning: request dropped: unable to find an available back end server, status 502: 127.0.0.1 Apr 26 05:19:17 192.168.122.209 [47708.111084] [tempesta fw] Warning: request dropped: unable to find an available back end server, status 502: 127.0.0.1 Apr 26 05:19:17 192.168.122.209 [47708.341763] [tempesta fw] Tempesta FW is ready Apr 26 05:19:18 192.168.122.209 [47709.357852] [tempesta fw] Tempesta FW is ready Apr 26 05:19:19 192.168.122.209 [47710.249939] [tempesta fw] Tempesta FW is ready Apr 26 05:19:20 192.168.122.209 [47711.361889] [tempesta fw] Tempesta FW is ready Apr 26 05:19:22 192.168.122.209 [47712.449994] [tempesta fw] Tempesta FW is ready Apr 26 05:19:22 192.168.122.209 [47712.894821] net_ratelimit: 992 callbacks suppressed Apr 26 05:19:22 192.168.122.209 [47712.894824] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:19:22 192.168.122.209 [47712.959083] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47712.959083] Maybe that's fine, but it's worth checking the [47712.959083] config - if there is no relations between the [47712.959083] names, then host name confusion attack is possible. Apr 26 05:19:22 192.168.122.209 [47713.057660] [tempesta fw] Configuration processing is completed. Apr 26 05:19:22 192.168.122.209 [47713.321981] [tempesta fw] Tempesta FW is ready Apr 26 05:19:23 192.168.122.209 [47713.948591] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:19:23 192.168.122.209 [47714.010893] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47714.010893] Maybe that's fine, but it's worth checking the [47714.010893] config - if there is no relations between the [47714.010893] names, then host name confusion attack is possible. Apr 26 05:19:23 192.168.122.209 [47714.149647] [tempesta fw] Configuration processing is completed. Apr 26 05:19:24 192.168.122.209 [47714.422002] [tempesta fw] Tempesta FW is ready Apr 26 05:19:24 192.168.122.209 [47715.055043] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:19:24 192.168.122.209 [47715.115091] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47715.115091] Maybe that's fine, but it's worth checking the [47715.115091] config - if there is no relations between the [47715.115091] names, then host name confusion attack is possible. Apr 26 05:19:24 192.168.122.209 [47715.257620] [tempesta fw] Configuration processing is completed. Apr 26 05:19:25 192.168.122.209 [47715.529950] [tempesta fw] Tempesta FW is ready Apr 26 05:19:25 192.168.122.209 [47716.044938] [tdb] Close table 'client0.tdb' Apr 26 05:19:25 192.168.122.209 [47716.235298] [tdb] Close table 'sessions0.tdb' Apr 26 05:19:29 192.168.122.209 [47719.571909] [tdb] Close table 'cache0.tdb' Apr 26 05:19:29 192.168.122.209 [47719.837020] [tdb] Close table 'filter0.tdb' Apr 26 05:19:29 192.168.122.209 [47719.837487] [tempesta fw] modules are stopped Apr 26 05:19:29 192.168.122.209 [47720.120884] [tempesta fw] exiting... Apr 26 05:19:30 192.168.122.209 [47720.831831] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 05:19:30 192.168.122.209 [47720.873562] [tdb] Shutdown Tempesta DB Apr 26 05:19:30 192.168.122.209 [47721.102206] End test: t_ja5.test_ja5t.TestJa5tStress.test_Http Apr 26 05:19:30 192.168.122.209 [47721.111196] Start test: t_leaks.test_leak.LeakTest.test_slab_memory Apr 26 05:19:32 192.168.122.209 [47722.452847] sh (413584): drop_caches: 3 Apr 26 05:19:34 192.168.122.209 [47725.126488] [tdb] Start Tempesta DB Apr 26 05:19:34 192.168.122.209 [47725.333723] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:19:35 192.168.122.209 [47726.252603] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47726.252603] Maybe that's fine, but it's worth checking the [47726.252603] config - if there is no relations between the [47726.252603] names, then host name confusion attack is possible. Apr 26 05:19:35 192.168.122.209 [47726.337650] [tempesta fw] Configuration processing is completed. Apr 26 05:19:36 192.168.122.209 [47726.433052] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:19:36 192.168.122.209 [47726.483232] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:19:36 192.168.122.209 [47726.541656] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:19:36 192.168.122.209 [47726.613729] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:19:36 192.168.122.209 [47726.615522] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:19:36 192.168.122.209 [47726.661676] [tempesta fw] Tempesta FW is ready Apr 26 05:19:46 192.168.122.209 [47737.262889] [tdb] Close table 'client0.tdb' Apr 26 05:19:47 192.168.122.209 [47737.457235] [tdb] Close table 'sessions0.tdb' Apr 26 05:19:47 192.168.122.209 [47737.697124] [tdb] Close table 'filter0.tdb' Apr 26 05:19:47 192.168.122.209 [47737.697565] [tempesta fw] modules are stopped Apr 26 05:19:47 192.168.122.209 [47737.899637] [tempesta fw] exiting... Apr 26 05:19:47 192.168.122.209 [47738.055807] [tdb] Shutdown Tempesta DB Apr 26 05:19:47 192.168.122.209 [47738.337312] sh (413822): drop_caches: 3 Apr 26 05:19:49 192.168.122.209 [47740.043296] End test: t_leaks.test_leak.LeakTest.test_slab_memory Apr 26 05:19:49 192.168.122.209 [47740.062561] Start test: t_leaks.test_leak.LeakTest.test_used_memory Apr 26 05:19:49 192.168.122.209 [47740.309561] sh (413835): drop_caches: 3 Apr 26 05:19:52 192.168.122.209 [47742.903610] [tdb] Start Tempesta DB Apr 26 05:19:52 192.168.122.209 [47743.113938] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:19:53 192.168.122.209 [47743.688599] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47743.688599] Maybe that's fine, but it's worth checking the [47743.688599] config - if there is no relations between the [47743.688599] names, then host name confusion attack is possible. Apr 26 05:19:53 192.168.122.209 [47743.769964] [tempesta fw] Configuration processing is completed. Apr 26 05:19:53 192.168.122.209 [47743.819396] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:19:53 192.168.122.209 [47743.848368] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:19:53 192.168.122.209 [47743.886845] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:19:53 192.168.122.209 [47743.965948] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:19:53 192.168.122.209 [47743.967706] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:19:53 192.168.122.209 [47744.005881] [tempesta fw] Tempesta FW is ready Apr 26 05:20:04 192.168.122.209 [47754.608422] [tdb] Close table 'client0.tdb' Apr 26 05:20:04 192.168.122.209 [47754.812664] [tdb] Close table 'sessions0.tdb' Apr 26 05:20:04 192.168.122.209 [47755.049931] [tdb] Close table 'filter0.tdb' Apr 26 05:20:04 192.168.122.209 [47755.050382] [tempesta fw] modules are stopped Apr 26 05:20:04 192.168.122.209 [47755.257333] [tempesta fw] exiting... Apr 26 05:20:04 192.168.122.209 [47755.385609] [tdb] Shutdown Tempesta DB Apr 26 05:20:05 192.168.122.209 [47755.705427] sh (414074): drop_caches: 3 Apr 26 05:20:07 192.168.122.209 [47757.505275] End test: t_leaks.test_leak.LeakTest.test_used_memory Apr 26 05:20:07 192.168.122.209 [47757.517918] Start test: t_leaks.test_leak.LeakTestH2.test_kmemleak Apr 26 05:20:08 192.168.122.209 [47759.191306] [tdb] Start Tempesta DB Apr 26 05:20:08 192.168.122.209 [47759.393728] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:20:09 192.168.122.209 [47760.051935] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47760.051935] Maybe that's fine, but it's worth checking the [47760.051935] config - if there is no relations between the [47760.051935] names, then host name confusion attack is possible. Apr 26 05:20:09 192.168.122.209 [47760.142501] [tempesta fw] Configuration processing is completed. Apr 26 05:20:09 192.168.122.209 [47760.204766] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:20:09 192.168.122.209 [47760.241939] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:20:09 192.168.122.209 [47760.281439] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:20:09 192.168.122.209 [47760.362152] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:20:09 192.168.122.209 [47760.363979] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:20:10 192.168.122.209 [47760.418098] [tempesta fw] Tempesta FW is ready Apr 26 05:20:20 192.168.122.209 [47771.087121] [tdb] Close table 'client0.tdb' Apr 26 05:20:20 192.168.122.209 [47771.274055] [tdb] Close table 'sessions0.tdb' Apr 26 05:20:21 192.168.122.209 [47771.515264] [tdb] Close table 'filter0.tdb' Apr 26 05:20:21 192.168.122.209 [47771.515723] [tempesta fw] modules are stopped Apr 26 05:20:21 192.168.122.209 [47771.692478] [tempesta fw] exiting... Apr 26 05:20:21 192.168.122.209 [47771.838207] [tdb] Shutdown Tempesta DB Apr 26 05:20:21 192.168.122.209 [47772.225999] End test: t_leaks.test_leak.LeakTestH2.test_kmemleak Apr 26 05:20:21 192.168.122.209 [47772.249689] Start test: t_leaks.test_leak.LeakTestH2.test_slab_memory Apr 26 05:20:22 192.168.122.209 [47772.537533] sh (414331): drop_caches: 3 Apr 26 05:20:24 192.168.122.209 [47775.156487] [tdb] Start Tempesta DB Apr 26 05:20:24 192.168.122.209 [47775.358091] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:20:25 192.168.122.209 [47775.976833] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47775.976833] Maybe that's fine, but it's worth checking the [47775.976833] config - if there is no relations between the [47775.976833] names, then host name confusion attack is possible. Apr 26 05:20:25 192.168.122.209 [47776.066359] [tempesta fw] Configuration processing is completed. Apr 26 05:20:25 192.168.122.209 [47776.122037] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:20:25 192.168.122.209 [47776.151338] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:20:25 192.168.122.209 [47776.181155] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:20:25 192.168.122.209 [47776.254359] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:20:25 192.168.122.209 [47776.256114] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:20:25 192.168.122.209 [47776.314281] [tempesta fw] Tempesta FW is ready Apr 26 05:20:36 192.168.122.209 [47786.953293] [tdb] Close table 'client0.tdb' Apr 26 05:20:36 192.168.122.209 [47787.125025] [tdb] Close table 'sessions0.tdb' Apr 26 05:20:36 192.168.122.209 [47787.360555] [tdb] Close table 'filter0.tdb' Apr 26 05:20:36 192.168.122.209 [47787.361020] [tempesta fw] modules are stopped Apr 26 05:20:37 192.168.122.209 [47787.580090] [tempesta fw] exiting... Apr 26 05:20:37 192.168.122.209 [47787.708906] [tdb] Shutdown Tempesta DB Apr 26 05:20:37 192.168.122.209 [47788.081697] sh (414565): drop_caches: 3 Apr 26 05:20:39 192.168.122.209 [47789.776445] End test: t_leaks.test_leak.LeakTestH2.test_slab_memory Apr 26 05:20:39 192.168.122.209 [47789.790248] Start test: t_leaks.test_leak.LeakTestH2.test_used_memory Apr 26 05:20:39 192.168.122.209 [47790.005949] sh (414577): drop_caches: 3 Apr 26 05:20:42 192.168.122.209 [47792.499603] [tdb] Start Tempesta DB Apr 26 05:20:42 192.168.122.209 [47792.692490] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:20:42 192.168.122.209 [47793.345188] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47793.345188] Maybe that's fine, but it's worth checking the [47793.345188] config - if there is no relations between the [47793.345188] names, then host name confusion attack is possible. Apr 26 05:20:43 192.168.122.209 [47793.438574] [tempesta fw] Configuration processing is completed. Apr 26 05:20:43 192.168.122.209 [47793.488378] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:20:43 192.168.122.209 [47793.516750] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:20:43 192.168.122.209 [47793.546845] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:20:43 192.168.122.209 [47793.618591] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:20:43 192.168.122.209 [47793.620321] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:20:43 192.168.122.209 [47793.662501] [tempesta fw] Tempesta FW is ready Apr 26 05:20:53 192.168.122.209 [47804.287476] [tdb] Close table 'client0.tdb' Apr 26 05:20:54 192.168.122.209 [47804.502948] [tdb] Close table 'sessions0.tdb' Apr 26 05:20:54 192.168.122.209 [47804.738259] [tdb] Close table 'filter0.tdb' Apr 26 05:20:54 192.168.122.209 [47804.739103] [tempesta fw] modules are stopped Apr 26 05:20:54 192.168.122.209 [47804.940476] [tempesta fw] exiting... Apr 26 05:20:54 192.168.122.209 [47805.081994] [tdb] Shutdown Tempesta DB Apr 26 05:20:54 192.168.122.209 [47805.403418] sh (414811): drop_caches: 3 Apr 26 05:20:56 192.168.122.209 [47807.085955] End test: t_leaks.test_leak.LeakTestH2.test_used_memory Apr 26 05:20:56 192.168.122.209 [47807.093839] Start test: t_long_body.test_long_request.LongBodyInRequest.test_http Apr 26 05:21:07 192.168.122.209 [47817.557520] [tdb] Start Tempesta DB Apr 26 05:21:07 192.168.122.209 [47817.756798] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:21:07 192.168.122.209 [47818.284406] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47818.284406] Maybe that's fine, but it's worth checking the [47818.284406] config - if there is no relations between the [47818.284406] names, then host name confusion attack is possible. Apr 26 05:21:08 192.168.122.209 [47818.406886] [tempesta fw] Configuration processing is completed. Apr 26 05:21:08 192.168.122.209 [47818.457093] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:21:08 192.168.122.209 [47818.490459] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:21:08 192.168.122.209 [47818.517781] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:21:08 192.168.122.209 [47818.602899] [tempesta fw] Open listen socket on: 0.0.0.0:4433 Apr 26 05:21:08 192.168.122.209 [47818.604711] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:21:08 192.168.122.209 [47818.606326] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:21:08 192.168.122.209 [47818.642840] [tempesta fw] Tempesta FW is ready Apr 26 05:21:14 192.168.122.209 [47824.977593] TCP: out of memory -- consider tuning tcp_mem Apr 26 05:21:14 192.168.122.209 [47825.371684] [tdb] Close table 'client0.tdb' Apr 26 05:21:15 192.168.122.209 [47825.589521] [tdb] Close table 'sessions0.tdb' Apr 26 05:21:15 192.168.122.209 [47825.844458] [tdb] Close table 'filter0.tdb' Apr 26 05:21:15 192.168.122.209 [47825.844868] [tempesta fw] modules are stopped Apr 26 05:21:15 192.168.122.209 [47826.018794] [tempesta fw] exiting... Apr 26 05:21:15 192.168.122.209 [47826.138023] [tdb] Shutdown Tempesta DB Apr 26 05:21:16 192.168.122.209 [47826.819478] End test: t_long_body.test_long_request.LongBodyInRequest.test_http Apr 26 05:21:16 192.168.122.209 [47826.833576] Start test: t_long_body.test_long_request.LongBodyInRequest.test_https Apr 26 05:21:26 192.168.122.209 [47836.415200] [tdb] Start Tempesta DB Apr 26 05:21:26 192.168.122.209 [47836.608901] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:21:26 192.168.122.209 [47837.104689] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47837.104689] Maybe that's fine, but it's worth checking the [47837.104689] config - if there is no relations between the [47837.104689] names, then host name confusion attack is possible. Apr 26 05:21:26 192.168.122.209 [47837.207128] [tempesta fw] Configuration processing is completed. Apr 26 05:21:26 192.168.122.209 [47837.257833] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:21:26 192.168.122.209 [47837.289168] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:21:26 192.168.122.209 [47837.316811] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:21:26 192.168.122.209 [47837.391125] [tempesta fw] Open listen socket on: 0.0.0.0:4433 Apr 26 05:21:26 192.168.122.209 [47837.392883] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:21:26 192.168.122.209 [47837.394507] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:21:27 192.168.122.209 [47837.455129] [tempesta fw] Tempesta FW is ready Apr 26 05:21:34 192.168.122.209 [47844.724304] TCP: out of memory -- consider tuning tcp_mem Apr 26 05:21:34 192.168.122.209 [47845.133507] [tdb] Close table 'client0.tdb' Apr 26 05:21:34 192.168.122.209 [47845.346007] [tdb] Close table 'sessions0.tdb' Apr 26 05:21:35 192.168.122.209 [47845.610080] [tdb] Close table 'filter0.tdb' Apr 26 05:21:35 192.168.122.209 [47845.610511] [tempesta fw] modules are stopped Apr 26 05:21:35 192.168.122.209 [47845.812854] [tempesta fw] exiting... Apr 26 05:21:35 192.168.122.209 [47845.927960] [tdb] Shutdown Tempesta DB Apr 26 05:21:36 192.168.122.209 [47846.762316] End test: t_long_body.test_long_request.LongBodyInRequest.test_https Apr 26 05:21:36 192.168.122.209 [47846.776583] Start test: t_long_body.test_long_request.LongBodyInRequest.test_many_big_chunks_in_request_http Apr 26 05:21:46 192.168.122.209 [47857.043959] [tdb] Start Tempesta DB Apr 26 05:21:46 192.168.122.209 [47857.252304] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:21:47 192.168.122.209 [47857.745122] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47857.745122] Maybe that's fine, but it's worth checking the [47857.745122] config - if there is no relations between the [47857.745122] names, then host name confusion attack is possible. Apr 26 05:21:47 192.168.122.209 [47857.847403] [tempesta fw] Configuration processing is completed. Apr 26 05:21:47 192.168.122.209 [47857.909639] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:21:47 192.168.122.209 [47857.938797] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:21:47 192.168.122.209 [47857.968234] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:21:47 192.168.122.209 [47858.023441] [tempesta fw] Open listen socket on: 0.0.0.0:4433 Apr 26 05:21:47 192.168.122.209 [47858.024867] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:21:47 192.168.122.209 [47858.026169] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:21:47 192.168.122.209 [47858.071308] [tempesta fw] Tempesta FW is ready Apr 26 05:21:52 192.168.122.209 [47862.984355] TCP: out of memory -- consider tuning tcp_mem Apr 26 05:21:52 192.168.122.209 [47863.376573] [tdb] Close table 'client0.tdb' Apr 26 05:21:53 192.168.122.209 [47863.610432] [tdb] Close table 'sessions0.tdb' Apr 26 05:21:53 192.168.122.209 [47863.892000] [tdb] Close table 'filter0.tdb' Apr 26 05:21:53 192.168.122.209 [47863.892418] [tempesta fw] modules are stopped Apr 26 05:21:53 192.168.122.209 [47864.079131] [tempesta fw] exiting... Apr 26 05:21:53 192.168.122.209 [47864.225994] [tdb] Shutdown Tempesta DB Apr 26 05:21:54 192.168.122.209 [47864.946112] End test: t_long_body.test_long_request.LongBodyInRequest.test_many_big_chunks_in_request_http Apr 26 05:21:54 192.168.122.209 [47864.959687] Start test: t_long_body.test_long_request.LongBodyInRequest.test_many_big_chunks_in_request_https Apr 26 05:22:04 192.168.122.209 [47874.469709] [tdb] Start Tempesta DB Apr 26 05:22:04 192.168.122.209 [47874.636691] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:22:04 192.168.122.209 [47875.021145] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47875.021145] Maybe that's fine, but it's worth checking the [47875.021145] config - if there is no relations between the [47875.021145] names, then host name confusion attack is possible. Apr 26 05:22:04 192.168.122.209 [47875.147925] [tempesta fw] Configuration processing is completed. Apr 26 05:22:04 192.168.122.209 [47875.209732] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:22:04 192.168.122.209 [47875.236783] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:22:04 192.168.122.209 [47875.264469] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:22:04 192.168.122.209 [47875.331600] [tempesta fw] Open listen socket on: 0.0.0.0:4433 Apr 26 05:22:04 192.168.122.209 [47875.333426] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:22:04 192.168.122.209 [47875.335088] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:22:04 192.168.122.209 [47875.403554] [tempesta fw] Tempesta FW is ready Apr 26 05:22:10 192.168.122.209 [47880.843875] TCP: out of memory -- consider tuning tcp_mem Apr 26 05:22:10 192.168.122.209 [47881.210940] [tdb] Close table 'client0.tdb' Apr 26 05:22:11 192.168.122.209 [47881.431119] [tdb] Close table 'sessions0.tdb' Apr 26 05:22:11 192.168.122.209 [47881.703856] [tdb] Close table 'filter0.tdb' Apr 26 05:22:11 192.168.122.209 [47881.704329] [tempesta fw] modules are stopped Apr 26 05:22:11 192.168.122.209 [47881.953145] [tempesta fw] exiting... Apr 26 05:22:11 192.168.122.209 [47882.090328] [tdb] Shutdown Tempesta DB Apr 26 05:22:12 192.168.122.209 [47882.808509] End test: t_long_body.test_long_request.LongBodyInRequest.test_many_big_chunks_in_request_https Apr 26 05:22:12 192.168.122.209 [47882.830260] Start test: t_malformed.test_h2_field_validity.TestH2HeaderFieldRequest.test_ascii_0x00_0x0a_0x0d_in_header_value Apr 26 05:22:13 192.168.122.209 [47884.178815] [tdb] Start Tempesta DB Apr 26 05:22:13 192.168.122.209 [47884.355976] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:22:14 192.168.122.209 [47884.900471] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47884.900471] Maybe that's fine, but it's worth checking the [47884.900471] config - if there is no relations between the [47884.900471] names, then host name confusion attack is possible. Apr 26 05:22:14 192.168.122.209 [47885.035685] [tempesta fw] Configuration processing is completed. Apr 26 05:22:14 192.168.122.209 [47885.092541] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:22:15 192.168.122.209 [47885.785273] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:22:15 192.168.122.209 [47885.859405] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:22:15 192.168.122.209 [47885.899728] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:22:15 192.168.122.209 [47885.939684] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:22:15 192.168.122.209 [47885.987659] [tempesta fw] Tempesta FW is ready Apr 26 05:22:15 192.168.122.209 [47886.307607] [tempesta fw] Warning: HTTP/2 request dropped: state=RGen_HdrOtherV input=0x76('val'), len=6, off=0 Apr 26 05:22:20 192.168.122.209 [47890.939730] [tempesta fw] Warning: HTTP/2 request dropped: state=RGen_HdrOtherV input=0x76('val [47890.939730] ue'), len=6, off=0 Apr 26 05:22:25 192.168.122.209 [47895.518469] [tempesta fw] Warning: HTTP/2 request dropped: state=RGen_HdrOtherV input=0x76('val ue'), len=6, off=0 Apr 26 05:22:25 192.168.122.209 [47895.924509] [tdb] Close table 'client0.tdb' Apr 26 05:22:25 192.168.122.209 [47896.136967] [tdb] Close table 'sessions0.tdb' Apr 26 05:22:29 192.168.122.209 [47899.486906] [tdb] Close table 'cache0.tdb' Apr 26 05:22:29 192.168.122.209 [47899.770525] [tdb] Close table 'filter0.tdb' Apr 26 05:22:29 192.168.122.209 [47899.770978] [tempesta fw] modules are stopped Apr 26 05:22:29 192.168.122.209 [47900.161189] [tempesta fw] exiting... Apr 26 05:22:29 192.168.122.209 [47900.277146] [tdb] Shutdown Tempesta DB Apr 26 05:22:30 192.168.122.209 [47900.502311] End test: t_malformed.test_h2_field_validity.TestH2HeaderFieldRequest.test_ascii_0x00_0x0a_0x0d_in_header_value Apr 26 05:22:30 192.168.122.209 [47900.510237] Start test: t_malformed.test_h2_field_validity.TestH2HeaderFieldRequest.test_ascii_from_0x00_to_0x20_in_header_name Apr 26 05:22:30 192.168.122.209 [47901.397790] [tdb] Start Tempesta DB Apr 26 05:22:31 192.168.122.209 [47901.536061] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:22:32 192.168.122.209 [47902.739667] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47902.739667] Maybe that's fine, but it's worth checking the [47902.739667] config - if there is no relations between the [47902.739667] names, then host name confusion attack is possible. Apr 26 05:22:32 192.168.122.209 [47902.900188] [tempesta fw] Configuration processing is completed. Apr 26 05:22:32 192.168.122.209 [47902.952621] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:22:32 192.168.122.209 [47903.376951] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:22:32 192.168.122.209 [47903.404212] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:22:33 192.168.122.209 [47903.432009] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:22:33 192.168.122.209 [47903.483938] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:22:33 192.168.122.209 [47903.523908] [tempesta fw] Tempesta FW is ready Apr 26 05:22:33 192.168.122.209 [47903.670045] [tempesta fw] Warning: HTTP/2 request dropped: state=RGen_HdrOtherN input=0x78('x-my-hdr'), len=9, off=0 Apr 26 05:22:37 192.168.122.209 [47908.297529] [tempesta fw] Warning: HTTP/2 request dropped: state=RGen_HdrOtherN input=0x78('x-my-hdr'), len=40, off=0 Apr 26 05:22:38 192.168.122.209 [47908.720948] [tdb] Close table 'client0.tdb' Apr 26 05:22:38 192.168.122.209 [47908.924655] [tdb] Close table 'sessions0.tdb' Apr 26 05:22:41 192.168.122.209 [47912.131131] [tdb] Close table 'cache0.tdb' Apr 26 05:22:41 192.168.122.209 [47912.369062] [tdb] Close table 'filter0.tdb' Apr 26 05:22:41 192.168.122.209 [47912.369502] [tempesta fw] modules are stopped Apr 26 05:22:42 192.168.122.209 [47912.571362] [tempesta fw] exiting... Apr 26 05:22:42 192.168.122.209 [47912.681771] [tdb] Shutdown Tempesta DB Apr 26 05:22:42 192.168.122.209 [47912.883615] End test: t_malformed.test_h2_field_validity.TestH2HeaderFieldRequest.test_ascii_from_0x00_to_0x20_in_header_name Apr 26 05:22:42 192.168.122.209 [47912.896615] Start test: t_malformed.test_h2_field_validity.TestH2HeaderFieldRequest.test_ascii_from_0x7f_to_0xff_in_header_name Apr 26 05:22:43 192.168.122.209 [47914.042646] [tdb] Start Tempesta DB Apr 26 05:22:43 192.168.122.209 [47914.175510] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:22:45 192.168.122.209 [47915.441505] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47915.441505] Maybe that's fine, but it's worth checking the [47915.441505] config - if there is no relations between the [47915.441505] names, then host name confusion attack is possible. Apr 26 05:22:45 192.168.122.209 [47915.556124] [tempesta fw] Configuration processing is completed. Apr 26 05:22:45 192.168.122.209 [47915.608731] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:22:45 192.168.122.209 [47916.021526] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:22:45 192.168.122.209 [47916.085877] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:22:45 192.168.122.209 [47916.113674] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:22:45 192.168.122.209 [47916.172090] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:22:45 192.168.122.209 [47916.232044] [tempesta fw] Tempesta FW is ready Apr 26 05:22:45 192.168.122.209 [47916.393995] [tempesta fw] Warning: HTTP/2 request dropped: state=RGen_HdrOtherN input=0x78('x-my-hdrи'), len=9, off=0 Apr 26 05:22:50 192.168.122.209 [47921.005448] [tempesta fw] Warning: HTTP/2 request dropped: state=RGen_HdrOtherN input=0x78('x-my-hdrАБВГДЕЖ'), len=136, off=0 Apr 26 05:22:51 192.168.122.209 [47921.477291] [tdb] Close table 'client0.tdb' Apr 26 05:22:51 192.168.122.209 [47921.652488] [tdb] Close table 'sessions0.tdb' Apr 26 05:22:54 192.168.122.209 [47925.039109] [tdb] Close table 'cache0.tdb' Apr 26 05:22:54 192.168.122.209 [47925.245972] [tdb] Close table 'filter0.tdb' Apr 26 05:22:54 192.168.122.209 [47925.246404] [tempesta fw] modules are stopped Apr 26 05:22:55 192.168.122.209 [47925.427509] [tempesta fw] exiting... Apr 26 05:22:55 192.168.122.209 [47925.537322] [tdb] Shutdown Tempesta DB Apr 26 05:22:55 192.168.122.209 [47925.770819] End test: t_malformed.test_h2_field_validity.TestH2HeaderFieldRequest.test_ascii_from_0x7f_to_0xff_in_header_name Apr 26 05:22:55 192.168.122.209 [47925.782584] Start test: t_malformed.test_h2_field_validity.TestH2HeaderFieldRequest.test_ascii_uppercase_in_header_name Apr 26 05:22:56 192.168.122.209 [47926.876951] [tdb] Start Tempesta DB Apr 26 05:22:56 192.168.122.209 [47927.045044] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:22:57 192.168.122.209 [47928.373491] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47928.373491] Maybe that's fine, but it's worth checking the [47928.373491] config - if there is no relations between the [47928.373491] names, then host name confusion attack is possible. Apr 26 05:22:58 192.168.122.209 [47928.488280] [tempesta fw] Configuration processing is completed. Apr 26 05:22:58 192.168.122.209 [47928.548264] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:22:58 192.168.122.209 [47928.981954] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:22:58 192.168.122.209 [47929.009682] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:22:58 192.168.122.209 [47929.037026] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:22:58 192.168.122.209 [47929.084226] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:22:58 192.168.122.209 [47929.128141] [tempesta fw] Tempesta FW is ready Apr 26 05:22:58 192.168.122.209 [47929.280020] [tempesta fw] Warning: HTTP/2 request dropped: state=RGen_HdrOtherN input=0x78('x-my-hdrG'), len=9, off=0 Apr 26 05:23:03 192.168.122.209 [47933.809939] [tempesta fw] Warning: HTTP/2 request dropped: state=RGen_HdrOtherN input=0x78('x-my-hdrABCDEFGH'), len=33, off=0 Apr 26 05:23:03 192.168.122.209 [47934.235713] [tdb] Close table 'client0.tdb' Apr 26 05:23:04 192.168.122.209 [47934.425790] [tdb] Close table 'sessions0.tdb' Apr 26 05:23:07 192.168.122.209 [47937.691233] [tdb] Close table 'cache0.tdb' Apr 26 05:23:07 192.168.122.209 [47937.929645] [tdb] Close table 'filter0.tdb' Apr 26 05:23:07 192.168.122.209 [47937.930091] [tempesta fw] modules are stopped Apr 26 05:23:07 192.168.122.209 [47938.132386] [tempesta fw] exiting... Apr 26 05:23:07 192.168.122.209 [47938.280328] [tdb] Shutdown Tempesta DB Apr 26 05:23:08 192.168.122.209 [47938.495509] End test: t_malformed.test_h2_field_validity.TestH2HeaderFieldRequest.test_ascii_uppercase_in_header_name Apr 26 05:23:08 192.168.122.209 [47938.512746] Start test: t_malformed.test_h2_field_validity.TestH2HeaderFieldResponse.test_ascii_0x00_0x0a_0x0d_in_header_value Apr 26 05:23:09 192.168.122.209 [47939.607781] [tdb] Start Tempesta DB Apr 26 05:23:09 192.168.122.209 [47939.776504] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:23:10 192.168.122.209 [47941.109691] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47941.109691] Maybe that's fine, but it's worth checking the [47941.109691] config - if there is no relations between the [47941.109691] names, then host name confusion attack is possible. Apr 26 05:23:10 192.168.122.209 [47941.232494] [tempesta fw] Configuration processing is completed. Apr 26 05:23:10 192.168.122.209 [47941.285194] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:23:11 192.168.122.209 [47941.763542] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:23:11 192.168.122.209 [47941.828866] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:23:11 192.168.122.209 [47941.859802] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:23:11 192.168.122.209 [47941.908367] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:23:11 192.168.122.209 [47941.960356] [tempesta fw] Tempesta FW is ready Apr 26 05:23:11 192.168.122.209 [47942.113213] [tempesta fw] Warning: Parser error: state=RGen_HdrOtherV input(-8)=0x76('my-hdr: val') data_len=84 off=55 Apr 26 05:23:11 192.168.122.209 [47942.114201] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 05:23:16 192.168.122.209 [47946.740118] [tempesta fw] Warning: Parser error: state=RGen_HdrOtherN input(-8)=0x65('r: val [47946.740118] ue [47946.740118] Content-Length: 0 [47946.740118] [47946.740118] ') data_len=84 off=60 Apr 26 05:23:16 192.168.122.209 [47946.745049] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 05:23:20 192.168.122.209 [47951.387846] [tempesta fw] Warning: Parser error: state=RGen_CR input(-8)=0x75('dr: val ue [47951.387846] Content-Length: 0 [47951.387846] [47951.387846] ') data_len=84 off=59 Apr 26 05:23:20 192.168.122.209 [47951.392014] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 05:23:21 192.168.122.209 [47951.814794] [tdb] Close table 'client0.tdb' Apr 26 05:23:21 192.168.122.209 [47952.027267] [tdb] Close table 'sessions0.tdb' Apr 26 05:23:25 192.168.122.209 [47955.615594] [tdb] Close table 'cache0.tdb' Apr 26 05:23:25 192.168.122.209 [47955.900044] [tdb] Close table 'filter0.tdb' Apr 26 05:23:25 192.168.122.209 [47955.900896] [tempesta fw] modules are stopped Apr 26 05:23:25 192.168.122.209 [47956.096796] [tempesta fw] exiting... Apr 26 05:23:25 192.168.122.209 [47956.223650] [tdb] Shutdown Tempesta DB Apr 26 05:23:26 192.168.122.209 [47956.475667] End test: t_malformed.test_h2_field_validity.TestH2HeaderFieldResponse.test_ascii_0x00_0x0a_0x0d_in_header_value Apr 26 05:23:26 192.168.122.209 [47956.501130] Start test: t_malformed.test_h2_field_validity.TestH2HeaderFieldResponse.test_ascii_from_0x00_to_0x20_in_header_name Apr 26 05:23:27 192.168.122.209 [47957.625195] [tdb] Start Tempesta DB Apr 26 05:23:27 192.168.122.209 [47957.781073] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:23:28 192.168.122.209 [47959.165313] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47959.165313] Maybe that's fine, but it's worth checking the [47959.165313] config - if there is no relations between the [47959.165313] names, then host name confusion attack is possible. Apr 26 05:23:28 192.168.122.209 [47959.308847] [tempesta fw] Configuration processing is completed. Apr 26 05:23:28 192.168.122.209 [47959.354956] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:23:29 192.168.122.209 [47959.774322] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:23:29 192.168.122.209 [47959.810519] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:23:29 192.168.122.209 [47959.838130] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:23:29 192.168.122.209 [47959.884613] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:23:29 192.168.122.209 [47959.928583] [tempesta fw] Tempesta FW is ready Apr 26 05:23:29 192.168.122.209 [47960.062829] [tempesta fw] Warning: Parser error: state=RGen_HdrOtherN input(-8)=0x78('debian [47960.062829] x-my-hdr: value [47960.062829] Content-Length: 0 [47960.062829] [47960.062829] ') data_len=84 off=45 Apr 26 05:23:29 192.168.122.209 [47960.068105] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 05:23:34 192.168.122.209 [47964.615716] [tempesta fw] Warning: Parser error: state=RGen_HdrOtherN input(-8)=0x78('debian [47964.615716] x-my-hdr') data_len=115 off=45 Apr 26 05:23:34 192.168.122.209 [47964.619243] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 05:23:34 192.168.122.209 [47965.054326] [tdb] Close table 'client0.tdb' Apr 26 05:23:34 192.168.122.209 [47965.247605] [tdb] Close table 'sessions0.tdb' Apr 26 05:23:38 192.168.122.209 [47968.490438] [tdb] Close table 'cache0.tdb' Apr 26 05:23:38 192.168.122.209 [47968.743931] [tdb] Close table 'filter0.tdb' Apr 26 05:23:38 192.168.122.209 [47968.744377] [tempesta fw] modules are stopped Apr 26 05:23:38 192.168.122.209 [47968.930082] [tempesta fw] exiting... Apr 26 05:23:38 192.168.122.209 [47969.054761] [tdb] Shutdown Tempesta DB Apr 26 05:23:38 192.168.122.209 [47969.243704] End test: t_malformed.test_h2_field_validity.TestH2HeaderFieldResponse.test_ascii_from_0x00_to_0x20_in_header_name Apr 26 05:23:38 192.168.122.209 [47969.254015] Start test: t_malformed.test_h2_field_validity.TestH2HeaderFieldResponse.test_ascii_from_0x7f_to_0xff_in_header_name Apr 26 05:23:39 192.168.122.209 [47970.341673] [tdb] Start Tempesta DB Apr 26 05:23:40 192.168.122.209 [47970.485078] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:23:41 192.168.122.209 [47971.801688] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47971.801688] Maybe that's fine, but it's worth checking the [47971.801688] config - if there is no relations between the [47971.801688] names, then host name confusion attack is possible. Apr 26 05:23:41 192.168.122.209 [47971.928852] [tempesta fw] Configuration processing is completed. Apr 26 05:23:41 192.168.122.209 [47971.981222] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:23:41 192.168.122.209 [47972.408186] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:23:42 192.168.122.209 [47972.434736] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:23:42 192.168.122.209 [47972.461555] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:23:42 192.168.122.209 [47972.512821] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:23:42 192.168.122.209 [47972.552742] [tempesta fw] Tempesta FW is ready Apr 26 05:23:42 192.168.122.209 [47972.743719] [tempesta fw] Warning: Parser error: state=RGen_HdrOtherN input(-8)=0x78('debian [47972.743719] x-my-hdrъ: value [47972.743719] Content-Length: 0 [47972.743719] [47972.743719] ') data_len=84 off=45 Apr 26 05:23:42 192.168.122.209 [47972.746880] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 05:23:46 192.168.122.209 [47977.373542] [tempesta fw] Warning: Parser error: state=RGen_HdrOtherN input(-8)=0x78('debian [47977.373542] x-my-hdrАБВГДЕЖЗИЙКЛМНОПРСТУФХЦЧШЩЪЫЬЭЮ') data_len=211 off=45 Apr 26 05:23:46 192.168.122.209 [47977.377620] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 05:23:47 192.168.122.209 [47977.778285] [tdb] Close table 'client0.tdb' Apr 26 05:23:47 192.168.122.209 [47977.971353] [tdb] Close table 'sessions0.tdb' Apr 26 05:23:50 192.168.122.209 [47981.127546] [tdb] Close table 'cache0.tdb' Apr 26 05:23:50 192.168.122.209 [47981.368766] [tdb] Close table 'filter0.tdb' Apr 26 05:23:50 192.168.122.209 [47981.369185] [tempesta fw] modules are stopped Apr 26 05:23:51 192.168.122.209 [47981.562352] [tempesta fw] exiting... Apr 26 05:23:51 192.168.122.209 [47981.684320] [tdb] Shutdown Tempesta DB Apr 26 05:23:51 192.168.122.209 [47981.884898] End test: t_malformed.test_h2_field_validity.TestH2HeaderFieldResponse.test_ascii_from_0x7f_to_0xff_in_header_name Apr 26 05:23:51 192.168.122.209 [47981.910432] Start test: t_malformed.test_h2_field_validity.TestH2HeaderFieldResponse.test_ascii_uppercase_in_header_name Apr 26 05:23:51 192.168.122.209 [47982.031260] End test: t_malformed.test_h2_field_validity.TestH2HeaderFieldResponse.test_ascii_uppercase_in_header_name Apr 26 05:23:51 192.168.122.209 [47982.047471] Start test: t_malformed.test_h2_malformed_headers.H2EtagAlphabetTest.test_etag_with_x21 Apr 26 05:23:52 192.168.122.209 [47983.135795] [tdb] Start Tempesta DB Apr 26 05:23:52 192.168.122.209 [47983.270601] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:23:54 192.168.122.209 [47984.754405] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47984.754405] Maybe that's fine, but it's worth checking the [47984.754405] config - if there is no relations between the [47984.754405] names, then host name confusion attack is possible. Apr 26 05:23:54 192.168.122.209 [47984.928990] [tempesta fw] Configuration processing is completed. Apr 26 05:23:54 192.168.122.209 [47984.987290] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:23:54 192.168.122.209 [47985.018611] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:23:54 192.168.122.209 [47985.046436] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:23:54 192.168.122.209 [47985.092949] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:23:54 192.168.122.209 [47985.094633] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:23:54 192.168.122.209 [47985.136917] [tempesta fw] Tempesta FW is ready Apr 26 05:23:55 192.168.122.209 [47985.724337] [tdb] Close table 'client0.tdb' Apr 26 05:23:55 192.168.122.209 [47985.920302] [tdb] Close table 'sessions0.tdb' Apr 26 05:23:55 192.168.122.209 [47986.147070] [tdb] Close table 'filter0.tdb' Apr 26 05:23:55 192.168.122.209 [47986.147499] [tempesta fw] modules are stopped Apr 26 05:23:55 192.168.122.209 [47986.330086] [tempesta fw] exiting... Apr 26 05:23:56 192.168.122.209 [47986.448377] [tdb] Shutdown Tempesta DB Apr 26 05:23:56 192.168.122.209 [47986.685630] End test: t_malformed.test_h2_malformed_headers.H2EtagAlphabetTest.test_etag_with_x21 Apr 26 05:23:56 192.168.122.209 [47986.699712] Start test: t_malformed.test_h2_malformed_headers.H2EtagAlphabetTest.test_etag_with_x23 Apr 26 05:23:57 192.168.122.209 [47987.804613] [tdb] Start Tempesta DB Apr 26 05:23:57 192.168.122.209 [47987.927088] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:23:58 192.168.122.209 [47988.566291] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47988.566291] Maybe that's fine, but it's worth checking the [47988.566291] config - if there is no relations between the [47988.566291] names, then host name confusion attack is possible. Apr 26 05:23:58 192.168.122.209 [47988.737060] [tempesta fw] Configuration processing is completed. Apr 26 05:23:58 192.168.122.209 [47988.791762] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:23:58 192.168.122.209 [47988.819900] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:23:58 192.168.122.209 [47988.848254] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:23:58 192.168.122.209 [47988.928942] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:23:58 192.168.122.209 [47988.930114] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:23:58 192.168.122.209 [47988.976956] [tempesta fw] Tempesta FW is ready Apr 26 05:23:59 192.168.122.209 [47989.549069] [tdb] Close table 'client0.tdb' Apr 26 05:23:59 192.168.122.209 [47989.738756] [tdb] Close table 'sessions0.tdb' Apr 26 05:23:59 192.168.122.209 [47989.981730] [tdb] Close table 'filter0.tdb' Apr 26 05:23:59 192.168.122.209 [47989.982163] [tempesta fw] modules are stopped Apr 26 05:23:59 192.168.122.209 [47990.216097] [tempesta fw] exiting... Apr 26 05:23:59 192.168.122.209 [47990.386591] [tdb] Shutdown Tempesta DB Apr 26 05:24:00 192.168.122.209 [47990.635327] End test: t_malformed.test_h2_malformed_headers.H2EtagAlphabetTest.test_etag_with_x23 Apr 26 05:24:00 192.168.122.209 [47990.647632] Start test: t_malformed.test_h2_malformed_headers.H2EtagAlphabetTest.test_etag_with_x7f Apr 26 05:24:01 192.168.122.209 [47991.740733] [tdb] Start Tempesta DB Apr 26 05:24:01 192.168.122.209 [47991.878824] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:24:02 192.168.122.209 [47992.501638] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47992.501638] Maybe that's fine, but it's worth checking the [47992.501638] config - if there is no relations between the [47992.501638] names, then host name confusion attack is possible. Apr 26 05:24:02 192.168.122.209 [47992.657088] [tempesta fw] Configuration processing is completed. Apr 26 05:24:02 192.168.122.209 [47992.712439] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:24:02 192.168.122.209 [47992.740133] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:24:02 192.168.122.209 [47992.766664] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:24:02 192.168.122.209 [47992.816992] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:24:02 192.168.122.209 [47992.818673] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:24:02 192.168.122.209 [47992.865012] [tempesta fw] Tempesta FW is ready Apr 26 05:24:02 192.168.122.209 [47993.397821] [tdb] Close table 'client0.tdb' Apr 26 05:24:03 192.168.122.209 [47993.605323] [tdb] Close table 'sessions0.tdb' Apr 26 05:24:03 192.168.122.209 [47993.831079] [tdb] Close table 'filter0.tdb' Apr 26 05:24:03 192.168.122.209 [47993.831538] net_ratelimit: 2 callbacks suppressed Apr 26 05:24:03 192.168.122.209 [47993.831540] [tempesta fw] modules are stopped Apr 26 05:24:03 192.168.122.209 [47994.037231] [tempesta fw] exiting... Apr 26 05:24:03 192.168.122.209 [47994.169789] [tdb] Shutdown Tempesta DB Apr 26 05:24:03 192.168.122.209 [47994.369204] End test: t_malformed.test_h2_malformed_headers.H2EtagAlphabetTest.test_etag_with_x7f Apr 26 05:24:03 192.168.122.209 [47994.381195] Start test: t_malformed.test_h2_malformed_headers.H2EtagAlphabetTest.test_etag_with_xf7 Apr 26 05:24:05 192.168.122.209 [47995.489045] [tdb] Start Tempesta DB Apr 26 05:24:05 192.168.122.209 [47995.625104] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:24:05 192.168.122.209 [47996.286356] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [47996.286356] Maybe that's fine, but it's worth checking the [47996.286356] config - if there is no relations between the [47996.286356] names, then host name confusion attack is possible. Apr 26 05:24:06 192.168.122.209 [47996.437103] [tempesta fw] Configuration processing is completed. Apr 26 05:24:06 192.168.122.209 [47996.496050] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:24:06 192.168.122.209 [47996.523662] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:24:06 192.168.122.209 [47996.550451] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:24:06 192.168.122.209 [47996.593098] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:24:06 192.168.122.209 [47996.594844] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:24:06 192.168.122.209 [47996.633065] [tempesta fw] Tempesta FW is ready Apr 26 05:24:06 192.168.122.209 [47997.193478] [tdb] Close table 'client0.tdb' Apr 26 05:24:06 192.168.122.209 [47997.379931] [tdb] Close table 'sessions0.tdb' Apr 26 05:24:07 192.168.122.209 [47997.619659] [tdb] Close table 'filter0.tdb' Apr 26 05:24:07 192.168.122.209 [47997.620095] [tempesta fw] modules are stopped Apr 26 05:24:07 192.168.122.209 [47997.806893] [tempesta fw] exiting... Apr 26 05:24:07 192.168.122.209 [47997.925806] [tdb] Shutdown Tempesta DB Apr 26 05:24:07 192.168.122.209 [47998.120728] End test: t_malformed.test_h2_malformed_headers.H2EtagAlphabetTest.test_etag_with_xf7 Apr 26 05:24:07 192.168.122.209 [47998.134981] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsTest.test_accept Apr 26 05:24:08 192.168.122.209 [47999.213570] [tdb] Start Tempesta DB Apr 26 05:24:08 192.168.122.209 [47999.357085] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:24:09 192.168.122.209 [48000.050459] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48000.050459] Maybe that's fine, but it's worth checking the [48000.050459] config - if there is no relations between the [48000.050459] names, then host name confusion attack is possible. Apr 26 05:24:09 192.168.122.209 [48000.185183] [tempesta fw] Configuration processing is completed. Apr 26 05:24:09 192.168.122.209 [48000.241997] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:24:09 192.168.122.209 [48000.275800] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:24:09 192.168.122.209 [48000.304887] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:24:09 192.168.122.209 [48000.353177] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:24:09 192.168.122.209 [48000.354917] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:24:09 192.168.122.209 [48000.401106] [tempesta fw] Tempesta FW is ready Apr 26 05:24:10 192.168.122.209 [48000.554183] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrAcceptV input=0x69('invalid'), len=7, off=0 Apr 26 05:24:10 192.168.122.209 [48000.978055] [tdb] Close table 'client0.tdb' Apr 26 05:24:10 192.168.122.209 [48001.163204] [tdb] Close table 'sessions0.tdb' Apr 26 05:24:10 192.168.122.209 [48001.388023] [tdb] Close table 'filter0.tdb' Apr 26 05:24:10 192.168.122.209 [48001.388454] [tempesta fw] modules are stopped Apr 26 05:24:11 192.168.122.209 [48001.572928] [tempesta fw] exiting... Apr 26 05:24:11 192.168.122.209 [48001.716402] [tdb] Shutdown Tempesta DB Apr 26 05:24:11 192.168.122.209 [48001.956539] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsTest.test_accept Apr 26 05:24:11 192.168.122.209 [48001.980357] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsTest.test_expect Apr 26 05:24:12 192.168.122.209 [48003.069065] [tdb] Start Tempesta DB Apr 26 05:24:12 192.168.122.209 [48003.205917] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:24:13 192.168.122.209 [48003.882534] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48003.882534] Maybe that's fine, but it's worth checking the [48003.882534] config - if there is no relations between the [48003.882534] names, then host name confusion attack is possible. Apr 26 05:24:13 192.168.122.209 [48004.025233] [tempesta fw] Configuration processing is completed. Apr 26 05:24:13 192.168.122.209 [48004.083140] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:24:13 192.168.122.209 [48004.115347] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:24:13 192.168.122.209 [48004.144658] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:24:13 192.168.122.209 [48004.233152] [tempesta fw] Tempesta FW is ready Apr 26 05:24:13 192.168.122.209 [48004.394151] net_ratelimit: 2 callbacks suppressed Apr 26 05:24:13 192.168.122.209 [48004.394159] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrExpectV input=0x31('100-continue'), len=12, off=0 Apr 26 05:24:14 192.168.122.209 [48004.822165] [tdb] Close table 'client0.tdb' Apr 26 05:24:14 192.168.122.209 [48005.008704] [tdb] Close table 'sessions0.tdb' Apr 26 05:24:14 192.168.122.209 [48005.250953] [tdb] Close table 'filter0.tdb' Apr 26 05:24:14 192.168.122.209 [48005.251378] [tempesta fw] modules are stopped Apr 26 05:24:15 192.168.122.209 [48005.458218] [tempesta fw] exiting... Apr 26 05:24:15 192.168.122.209 [48005.604438] [tdb] Shutdown Tempesta DB Apr 26 05:24:15 192.168.122.209 [48005.840001] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsTest.test_expect Apr 26 05:24:15 192.168.122.209 [48005.862451] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsTest.test_expect_invalid Apr 26 05:24:16 192.168.122.209 [48006.891481] [tdb] Start Tempesta DB Apr 26 05:24:16 192.168.122.209 [48007.032048] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:24:17 192.168.122.209 [48007.726540] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48007.726540] Maybe that's fine, but it's worth checking the [48007.726540] config - if there is no relations between the [48007.726540] names, then host name confusion attack is possible. Apr 26 05:24:17 192.168.122.209 [48007.865254] [tempesta fw] Configuration processing is completed. Apr 26 05:24:17 192.168.122.209 [48007.919011] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:24:17 192.168.122.209 [48007.947050] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:24:17 192.168.122.209 [48007.973446] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:24:17 192.168.122.209 [48008.029260] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:24:17 192.168.122.209 [48008.030948] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:24:17 192.168.122.209 [48008.069216] [tempesta fw] Tempesta FW is ready Apr 26 05:24:17 192.168.122.209 [48008.211520] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrExpectV input=0x69('invalid'), len=7, off=0 Apr 26 05:24:18 192.168.122.209 [48008.634728] [tdb] Close table 'client0.tdb' Apr 26 05:24:18 192.168.122.209 [48008.825687] [tdb] Close table 'sessions0.tdb' Apr 26 05:24:18 192.168.122.209 [48009.064334] [tdb] Close table 'filter0.tdb' Apr 26 05:24:18 192.168.122.209 [48009.064777] [tempesta fw] modules are stopped Apr 26 05:24:18 192.168.122.209 [48009.257101] [tempesta fw] exiting... Apr 26 05:24:19 192.168.122.209 [48009.416978] [tdb] Shutdown Tempesta DB Apr 26 05:24:19 192.168.122.209 [48009.612514] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsTest.test_expect_invalid Apr 26 05:24:19 192.168.122.209 [48009.638469] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsTest.test_host Apr 26 05:24:20 192.168.122.209 [48010.696570] [tdb] Start Tempesta DB Apr 26 05:24:20 192.168.122.209 [48010.821370] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:24:21 192.168.122.209 [48011.518087] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48011.518087] Maybe that's fine, but it's worth checking the [48011.518087] config - if there is no relations between the [48011.518087] names, then host name confusion attack is possible. Apr 26 05:24:21 192.168.122.209 [48011.657318] [tempesta fw] Configuration processing is completed. Apr 26 05:24:21 192.168.122.209 [48011.709211] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:24:21 192.168.122.209 [48011.738762] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:24:21 192.168.122.209 [48011.765490] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:24:21 192.168.122.209 [48011.817226] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:24:21 192.168.122.209 [48011.818774] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:24:21 192.168.122.209 [48011.865232] [tempesta fw] Tempesta FW is ready Apr 26 05:24:21 192.168.122.209 [48012.017318] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrPsAuthorityV input=0x68('http://'), len=7, off=0 Apr 26 05:24:21 192.168.122.209 [48012.408420] [tdb] Close table 'client0.tdb' Apr 26 05:24:22 192.168.122.209 [48012.601427] [tdb] Close table 'sessions0.tdb' Apr 26 05:24:22 192.168.122.209 [48012.826540] [tdb] Close table 'filter0.tdb' Apr 26 05:24:22 192.168.122.209 [48012.826979] [tempesta fw] modules are stopped Apr 26 05:24:22 192.168.122.209 [48013.033490] [tempesta fw] exiting... Apr 26 05:24:22 192.168.122.209 [48013.177082] [tdb] Shutdown Tempesta DB Apr 26 05:24:22 192.168.122.209 [48013.368508] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsTest.test_host Apr 26 05:24:22 192.168.122.209 [48013.395396] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsTest.test_if_none_match Apr 26 05:24:24 192.168.122.209 [48014.485917] [tdb] Start Tempesta DB Apr 26 05:24:24 192.168.122.209 [48014.625042] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:24:24 192.168.122.209 [48015.230601] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48015.230601] Maybe that's fine, but it's worth checking the [48015.230601] config - if there is no relations between the [48015.230601] names, then host name confusion attack is possible. Apr 26 05:24:24 192.168.122.209 [48015.385334] [tempesta fw] Configuration processing is completed. Apr 26 05:24:25 192.168.122.209 [48015.435728] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:24:25 192.168.122.209 [48015.465862] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:24:25 192.168.122.209 [48015.492190] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:24:25 192.168.122.209 [48015.573276] [tempesta fw] Tempesta FW is ready Apr 26 05:24:25 192.168.122.209 [48016.162167] [tdb] Close table 'client0.tdb' Apr 26 05:24:25 192.168.122.209 [48016.347728] [tdb] Close table 'sessions0.tdb' Apr 26 05:24:26 192.168.122.209 [48016.579619] [tdb] Close table 'filter0.tdb' Apr 26 05:24:26 192.168.122.209 [48016.580059] net_ratelimit: 3 callbacks suppressed Apr 26 05:24:26 192.168.122.209 [48016.580060] [tempesta fw] modules are stopped Apr 26 05:24:26 192.168.122.209 [48016.780637] [tempesta fw] exiting... Apr 26 05:24:26 192.168.122.209 [48016.906476] [tdb] Shutdown Tempesta DB Apr 26 05:24:26 192.168.122.209 [48017.118827] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsTest.test_if_none_match Apr 26 05:24:26 192.168.122.209 [48017.126024] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsTest.test_missing_name Apr 26 05:24:27 192.168.122.209 [48018.233026] [tdb] Start Tempesta DB Apr 26 05:24:27 192.168.122.209 [48018.379642] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:24:28 192.168.122.209 [48019.054130] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48019.054130] Maybe that's fine, but it's worth checking the [48019.054130] config - if there is no relations between the [48019.054130] names, then host name confusion attack is possible. Apr 26 05:24:28 192.168.122.209 [48019.221439] [tempesta fw] Configuration processing is completed. Apr 26 05:24:28 192.168.122.209 [48019.284219] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:24:28 192.168.122.209 [48019.315979] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:24:28 192.168.122.209 [48019.345661] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:24:28 192.168.122.209 [48019.389386] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:24:28 192.168.122.209 [48019.390584] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:24:29 192.168.122.209 [48019.433328] [tempesta fw] Tempesta FW is ready Apr 26 05:24:29 192.168.122.209 [48019.975664] [tdb] Close table 'client0.tdb' Apr 26 05:24:29 192.168.122.209 [48020.165805] [tdb] Close table 'sessions0.tdb' Apr 26 05:24:29 192.168.122.209 [48020.395488] [tdb] Close table 'filter0.tdb' Apr 26 05:24:29 192.168.122.209 [48020.395928] [tempesta fw] modules are stopped Apr 26 05:24:30 192.168.122.209 [48020.566880] [tempesta fw] exiting... Apr 26 05:24:30 192.168.122.209 [48020.690951] [tdb] Shutdown Tempesta DB Apr 26 05:24:30 192.168.122.209 [48020.885847] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsTest.test_missing_name Apr 26 05:24:30 192.168.122.209 [48020.895346] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsTest.test_te Apr 26 05:24:31 192.168.122.209 [48022.018182] [tdb] Start Tempesta DB Apr 26 05:24:31 192.168.122.209 [48022.164659] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:24:32 192.168.122.209 [48022.910758] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48022.910758] Maybe that's fine, but it's worth checking the [48022.910758] config - if there is no relations between the [48022.910758] names, then host name confusion attack is possible. Apr 26 05:24:32 192.168.122.209 [48023.053458] [tempesta fw] Configuration processing is completed. Apr 26 05:24:32 192.168.122.209 [48023.109674] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:24:32 192.168.122.209 [48023.141978] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:24:32 192.168.122.209 [48023.171388] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:24:32 192.168.122.209 [48023.205435] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:24:32 192.168.122.209 [48023.207130] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:24:32 192.168.122.209 [48023.245391] [tempesta fw] Tempesta FW is ready Apr 26 05:24:32 192.168.122.209 [48023.397334] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrTeV input=0x69('invalid'), len=7, off=0 Apr 26 05:24:33 192.168.122.209 [48023.814376] [tdb] Close table 'client0.tdb' Apr 26 05:24:33 192.168.122.209 [48024.007442] [tdb] Close table 'sessions0.tdb' Apr 26 05:24:33 192.168.122.209 [48024.240237] [tdb] Close table 'filter0.tdb' Apr 26 05:24:33 192.168.122.209 [48024.240666] [tempesta fw] modules are stopped Apr 26 05:24:34 192.168.122.209 [48024.462180] [tempesta fw] exiting... Apr 26 05:24:34 192.168.122.209 [48024.585861] [tdb] Shutdown Tempesta DB Apr 26 05:24:34 192.168.122.209 [48024.811425] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsTest.test_te Apr 26 05:24:34 192.168.122.209 [48024.822090] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsTest.test_transfer_encoding Apr 26 05:24:35 192.168.122.209 [48026.119986] [tdb] Start Tempesta DB Apr 26 05:24:35 192.168.122.209 [48026.261904] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:24:36 192.168.122.209 [48027.022777] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48027.022777] Maybe that's fine, but it's worth checking the [48027.022777] config - if there is no relations between the [48027.022777] names, then host name confusion attack is possible. Apr 26 05:24:36 192.168.122.209 [48027.173498] [tempesta fw] Configuration processing is completed. Apr 26 05:24:36 192.168.122.209 [48027.225430] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:24:36 192.168.122.209 [48027.255818] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:24:36 192.168.122.209 [48027.282981] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:24:36 192.168.122.209 [48027.337477] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:24:36 192.168.122.209 [48027.339224] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:24:36 192.168.122.209 [48027.377428] [tempesta fw] Tempesta FW is ready Apr 26 05:24:37 192.168.122.209 [48027.540853] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrTeV input=0x6e('nottoken'), len=8, off=0 Apr 26 05:24:37 192.168.122.209 [48027.978758] [tdb] Close table 'client0.tdb' Apr 26 05:24:37 192.168.122.209 [48028.181330] [tdb] Close table 'sessions0.tdb' Apr 26 05:24:38 192.168.122.209 [48028.445002] [tdb] Close table 'filter0.tdb' Apr 26 05:24:38 192.168.122.209 [48028.445453] [tempesta fw] modules are stopped Apr 26 05:24:38 192.168.122.209 [48028.666958] [tempesta fw] exiting... Apr 26 05:24:38 192.168.122.209 [48028.781000] [tdb] Shutdown Tempesta DB Apr 26 05:24:38 192.168.122.209 [48029.008668] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsTest.test_transfer_encoding Apr 26 05:24:38 192.168.122.209 [48029.021166] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsTest.test_upgrade Apr 26 05:24:39 192.168.122.209 [48030.229514] [tdb] Start Tempesta DB Apr 26 05:24:39 192.168.122.209 [48030.383153] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:24:40 192.168.122.209 [48031.122827] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48031.122827] Maybe that's fine, but it's worth checking the [48031.122827] config - if there is no relations between the [48031.122827] names, then host name confusion attack is possible. Apr 26 05:24:40 192.168.122.209 [48031.261503] [tempesta fw] Configuration processing is completed. Apr 26 05:24:40 192.168.122.209 [48031.312085] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:24:40 192.168.122.209 [48031.339961] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:24:40 192.168.122.209 [48031.366772] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:24:41 192.168.122.209 [48031.417558] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:24:41 192.168.122.209 [48031.419235] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:24:41 192.168.122.209 [48031.457423] [tempesta fw] Tempesta FW is ready Apr 26 05:24:41 192.168.122.209 [48032.014071] [tdb] Close table 'client0.tdb' Apr 26 05:24:41 192.168.122.209 [48032.202683] [tdb] Close table 'sessions0.tdb' Apr 26 05:24:42 192.168.122.209 [48032.444777] [tdb] Close table 'filter0.tdb' Apr 26 05:24:42 192.168.122.209 [48032.445239] net_ratelimit: 1 callbacks suppressed Apr 26 05:24:42 192.168.122.209 [48032.445241] [tempesta fw] modules are stopped Apr 26 05:24:42 192.168.122.209 [48032.675301] [tempesta fw] exiting... Apr 26 05:24:42 192.168.122.209 [48032.822399] [tdb] Shutdown Tempesta DB Apr 26 05:24:42 192.168.122.209 [48033.052333] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsTest.test_upgrade Apr 26 05:24:42 192.168.122.209 [48033.066076] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_accept_charset Apr 26 05:24:43 192.168.122.209 [48034.197094] [tdb] Start Tempesta DB Apr 26 05:24:43 192.168.122.209 [48034.330587] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:24:44 192.168.122.209 [48034.989889] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48034.989889] Maybe that's fine, but it's worth checking the [48034.989889] config - if there is no relations between the [48034.989889] names, then host name confusion attack is possible. Apr 26 05:24:44 192.168.122.209 [48035.109797] [tempesta fw] Configuration processing is completed. Apr 26 05:24:44 192.168.122.209 [48035.164225] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:24:44 192.168.122.209 [48035.198119] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:24:44 192.168.122.209 [48035.227145] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:24:44 192.168.122.209 [48035.277465] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:24:44 192.168.122.209 [48035.278372] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:24:44 192.168.122.209 [48035.337470] [tempesta fw] Tempesta FW is ready Apr 26 05:24:45 192.168.122.209 [48035.920712] [tdb] Close table 'client0.tdb' Apr 26 05:24:45 192.168.122.209 [48036.141673] [tdb] Close table 'sessions0.tdb' Apr 26 05:24:45 192.168.122.209 [48036.355595] [tdb] Close table 'filter0.tdb' Apr 26 05:24:45 192.168.122.209 [48036.356049] [tempesta fw] modules are stopped Apr 26 05:24:46 192.168.122.209 [48036.582951] [tempesta fw] exiting... Apr 26 05:24:46 192.168.122.209 [48036.704043] [tdb] Shutdown Tempesta DB Apr 26 05:24:46 192.168.122.209 [48036.948304] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_accept_charset Apr 26 05:24:46 192.168.122.209 [48036.957320] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_accept_encoding Apr 26 05:24:47 192.168.122.209 [48038.040671] [tdb] Start Tempesta DB Apr 26 05:24:47 192.168.122.209 [48038.188237] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:24:48 192.168.122.209 [48038.862891] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48038.862891] Maybe that's fine, but it's worth checking the [48038.862891] config - if there is no relations between the [48038.862891] names, then host name confusion attack is possible. Apr 26 05:24:48 192.168.122.209 [48039.017664] [tempesta fw] Configuration processing is completed. Apr 26 05:24:48 192.168.122.209 [48039.067426] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:24:48 192.168.122.209 [48039.094876] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:24:48 192.168.122.209 [48039.121134] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:24:48 192.168.122.209 [48039.197630] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:24:48 192.168.122.209 [48039.199323] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:24:48 192.168.122.209 [48039.237524] [tempesta fw] Tempesta FW is ready Apr 26 05:24:49 192.168.122.209 [48039.762036] [tdb] Close table 'client0.tdb' Apr 26 05:24:49 192.168.122.209 [48039.950490] [tdb] Close table 'sessions0.tdb' Apr 26 05:24:49 192.168.122.209 [48040.192338] [tdb] Close table 'filter0.tdb' Apr 26 05:24:49 192.168.122.209 [48040.192781] [tempesta fw] modules are stopped Apr 26 05:24:49 192.168.122.209 [48040.394104] [tempesta fw] exiting... Apr 26 05:24:50 192.168.122.209 [48040.535697] [tdb] Shutdown Tempesta DB Apr 26 05:24:50 192.168.122.209 [48040.727676] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_accept_encoding Apr 26 05:24:50 192.168.122.209 [48040.749881] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_accept_language Apr 26 05:24:51 192.168.122.209 [48041.810433] [tdb] Start Tempesta DB Apr 26 05:24:51 192.168.122.209 [48041.946503] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:24:52 192.168.122.209 [48042.638968] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48042.638968] Maybe that's fine, but it's worth checking the [48042.638968] config - if there is no relations between the [48042.638968] names, then host name confusion attack is possible. Apr 26 05:24:52 192.168.122.209 [48042.769720] [tempesta fw] Configuration processing is completed. Apr 26 05:24:52 192.168.122.209 [48042.827426] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:24:52 192.168.122.209 [48042.861168] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:24:52 192.168.122.209 [48042.889875] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:24:52 192.168.122.209 [48042.941692] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:24:52 192.168.122.209 [48042.985623] [tempesta fw] Tempesta FW is ready Apr 26 05:24:53 192.168.122.209 [48043.615149] [tdb] Close table 'client0.tdb' Apr 26 05:24:53 192.168.122.209 [48043.807443] [tdb] Close table 'sessions0.tdb' Apr 26 05:24:53 192.168.122.209 [48044.053673] [tdb] Close table 'filter0.tdb' Apr 26 05:24:53 192.168.122.209 [48044.054110] net_ratelimit: 1 callbacks suppressed Apr 26 05:24:53 192.168.122.209 [48044.054111] [tempesta fw] modules are stopped Apr 26 05:24:53 192.168.122.209 [48044.261798] [tempesta fw] exiting... Apr 26 05:24:53 192.168.122.209 [48044.403474] [tdb] Shutdown Tempesta DB Apr 26 05:24:54 192.168.122.209 [48044.601876] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_accept_language Apr 26 05:24:54 192.168.122.209 [48044.613661] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_content_encoding Apr 26 05:24:55 192.168.122.209 [48045.686374] [tdb] Start Tempesta DB Apr 26 05:24:55 192.168.122.209 [48045.826696] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:24:56 192.168.122.209 [48046.506994] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48046.506994] Maybe that's fine, but it's worth checking the [48046.506994] config - if there is no relations between the [48046.506994] names, then host name confusion attack is possible. Apr 26 05:24:56 192.168.122.209 [48046.645759] [tempesta fw] Configuration processing is completed. Apr 26 05:24:56 192.168.122.209 [48046.696157] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:24:56 192.168.122.209 [48046.724188] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:24:56 192.168.122.209 [48046.751329] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:24:56 192.168.122.209 [48046.793701] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:24:56 192.168.122.209 [48046.795045] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:24:56 192.168.122.209 [48046.841704] [tempesta fw] Tempesta FW is ready Apr 26 05:24:57 192.168.122.209 [48047.431817] [tdb] Close table 'client0.tdb' Apr 26 05:24:57 192.168.122.209 [48047.621220] [tdb] Close table 'sessions0.tdb' Apr 26 05:24:57 192.168.122.209 [48047.883325] [tdb] Close table 'filter0.tdb' Apr 26 05:24:57 192.168.122.209 [48047.883761] [tempesta fw] modules are stopped Apr 26 05:24:57 192.168.122.209 [48048.084990] [tempesta fw] exiting... Apr 26 05:24:57 192.168.122.209 [48048.203287] [tdb] Shutdown Tempesta DB Apr 26 05:24:57 192.168.122.209 [48048.401388] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_content_encoding Apr 26 05:24:58 192.168.122.209 [48048.416006] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_content_language Apr 26 05:24:59 192.168.122.209 [48049.469023] [tdb] Start Tempesta DB Apr 26 05:24:59 192.168.122.209 [48049.621731] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:24:59 192.168.122.209 [48050.287021] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48050.287021] Maybe that's fine, but it's worth checking the [48050.287021] config - if there is no relations between the [48050.287021] names, then host name confusion attack is possible. Apr 26 05:25:00 192.168.122.209 [48050.421790] [tempesta fw] Configuration processing is completed. Apr 26 05:25:00 192.168.122.209 [48050.481576] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:25:00 192.168.122.209 [48050.509484] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:25:00 192.168.122.209 [48050.536098] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:25:00 192.168.122.209 [48050.593774] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:25:00 192.168.122.209 [48050.595448] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:25:00 192.168.122.209 [48050.633732] [tempesta fw] Tempesta FW is ready Apr 26 05:25:00 192.168.122.209 [48051.205276] [tdb] Close table 'client0.tdb' Apr 26 05:25:00 192.168.122.209 [48051.401128] [tdb] Close table 'sessions0.tdb' Apr 26 05:25:01 192.168.122.209 [48051.622505] [tdb] Close table 'filter0.tdb' Apr 26 05:25:01 192.168.122.209 [48051.622943] [tempesta fw] modules are stopped Apr 26 05:25:01 192.168.122.209 [48051.833683] [tempesta fw] exiting... Apr 26 05:25:01 192.168.122.209 [48051.952075] [tdb] Shutdown Tempesta DB Apr 26 05:25:01 192.168.122.209 [48052.169650] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_content_language Apr 26 05:25:01 192.168.122.209 [48052.180204] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_content_location Apr 26 05:25:02 192.168.122.209 [48053.235564] [tdb] Start Tempesta DB Apr 26 05:25:02 192.168.122.209 [48053.367100] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:25:03 192.168.122.209 [48054.039649] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48054.039649] Maybe that's fine, but it's worth checking the [48054.039649] config - if there is no relations between the [48054.039649] names, then host name confusion attack is possible. Apr 26 05:25:03 192.168.122.209 [48054.233743] [tempesta fw] Configuration processing is completed. Apr 26 05:25:03 192.168.122.209 [48054.294421] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:25:03 192.168.122.209 [48054.322290] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:25:03 192.168.122.209 [48054.349238] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:25:04 192.168.122.209 [48054.429818] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:25:04 192.168.122.209 [48054.473776] [tempesta fw] Tempesta FW is ready Apr 26 05:25:04 192.168.122.209 [48055.070234] [tdb] Close table 'client0.tdb' Apr 26 05:25:04 192.168.122.209 [48055.252831] [tdb] Close table 'sessions0.tdb' Apr 26 05:25:05 192.168.122.209 [48055.486880] [tdb] Close table 'filter0.tdb' Apr 26 05:25:05 192.168.122.209 [48055.487319] net_ratelimit: 1 callbacks suppressed Apr 26 05:25:05 192.168.122.209 [48055.487320] [tempesta fw] modules are stopped Apr 26 05:25:05 192.168.122.209 [48055.690177] [tempesta fw] exiting... Apr 26 05:25:05 192.168.122.209 [48055.836833] [tdb] Shutdown Tempesta DB Apr 26 05:25:05 192.168.122.209 [48056.054799] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_content_location Apr 26 05:25:05 192.168.122.209 [48056.068304] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_content_range Apr 26 05:25:06 192.168.122.209 [48057.188420] [tdb] Start Tempesta DB Apr 26 05:25:06 192.168.122.209 [48057.324192] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:25:07 192.168.122.209 [48058.003167] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48058.003167] Maybe that's fine, but it's worth checking the [48058.003167] config - if there is no relations between the [48058.003167] names, then host name confusion attack is possible. Apr 26 05:25:07 192.168.122.209 [48058.169911] [tempesta fw] Configuration processing is completed. Apr 26 05:25:07 192.168.122.209 [48058.227735] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:25:07 192.168.122.209 [48058.260763] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:25:07 192.168.122.209 [48058.289081] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:25:07 192.168.122.209 [48058.341975] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:25:07 192.168.122.209 [48058.343728] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:25:07 192.168.122.209 [48058.381821] [tempesta fw] Tempesta FW is ready Apr 26 05:25:08 192.168.122.209 [48059.023394] [tdb] Close table 'client0.tdb' Apr 26 05:25:08 192.168.122.209 [48059.212123] [tdb] Close table 'sessions0.tdb' Apr 26 05:25:09 192.168.122.209 [48059.452634] [tdb] Close table 'filter0.tdb' Apr 26 05:25:09 192.168.122.209 [48059.453433] [tempesta fw] modules are stopped Apr 26 05:25:09 192.168.122.209 [48059.625106] [tempesta fw] exiting... Apr 26 05:25:09 192.168.122.209 [48059.780041] [tdb] Shutdown Tempesta DB Apr 26 05:25:09 192.168.122.209 [48059.953938] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_content_range Apr 26 05:25:09 192.168.122.209 [48059.967691] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_content_type Apr 26 05:25:10 192.168.122.209 [48061.092445] [tdb] Start Tempesta DB Apr 26 05:25:10 192.168.122.209 [48061.234002] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:25:11 192.168.122.209 [48061.903261] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48061.903261] Maybe that's fine, but it's worth checking the [48061.903261] config - if there is no relations between the [48061.903261] names, then host name confusion attack is possible. Apr 26 05:25:11 192.168.122.209 [48062.049951] [tempesta fw] Configuration processing is completed. Apr 26 05:25:11 192.168.122.209 [48062.101028] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:25:11 192.168.122.209 [48062.128728] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:25:11 192.168.122.209 [48062.155543] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:25:11 192.168.122.209 [48062.193855] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:25:11 192.168.122.209 [48062.194901] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:25:11 192.168.122.209 [48062.229862] [tempesta fw] Tempesta FW is ready Apr 26 05:25:12 192.168.122.209 [48062.850767] [tdb] Close table 'client0.tdb' Apr 26 05:25:12 192.168.122.209 [48063.043693] [tdb] Close table 'sessions0.tdb' Apr 26 05:25:12 192.168.122.209 [48063.347788] [tdb] Close table 'filter0.tdb' Apr 26 05:25:12 192.168.122.209 [48063.348217] [tempesta fw] modules are stopped Apr 26 05:25:13 192.168.122.209 [48063.562257] [tempesta fw] exiting... Apr 26 05:25:13 192.168.122.209 [48063.692079] [tdb] Shutdown Tempesta DB Apr 26 05:25:13 192.168.122.209 [48063.922382] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_content_type Apr 26 05:25:13 192.168.122.209 [48063.944058] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_date Apr 26 05:25:14 192.168.122.209 [48065.028253] [tdb] Start Tempesta DB Apr 26 05:25:14 192.168.122.209 [48065.171757] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:25:15 192.168.122.209 [48065.891323] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48065.891323] Maybe that's fine, but it's worth checking the [48065.891323] config - if there is no relations between the [48065.891323] names, then host name confusion attack is possible. Apr 26 05:25:15 192.168.122.209 [48066.033936] [tempesta fw] Configuration processing is completed. Apr 26 05:25:15 192.168.122.209 [48066.089391] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:25:15 192.168.122.209 [48066.117247] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:25:15 192.168.122.209 [48066.143886] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:25:15 192.168.122.209 [48066.197881] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:25:15 192.168.122.209 [48066.250244] [tempesta fw] Tempesta FW is ready Apr 26 05:25:16 192.168.122.209 [48066.820465] [tdb] Close table 'client0.tdb' Apr 26 05:25:16 192.168.122.209 [48067.009671] [tdb] Close table 'sessions0.tdb' Apr 26 05:25:16 192.168.122.209 [48067.249129] [tdb] Close table 'filter0.tdb' Apr 26 05:25:16 192.168.122.209 [48067.249572] net_ratelimit: 1 callbacks suppressed Apr 26 05:25:16 192.168.122.209 [48067.249574] [tempesta fw] modules are stopped Apr 26 05:25:17 192.168.122.209 [48067.435994] [tempesta fw] exiting... Apr 26 05:25:17 192.168.122.209 [48067.568711] [tdb] Shutdown Tempesta DB Apr 26 05:25:17 192.168.122.209 [48067.767068] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_date Apr 26 05:25:17 192.168.122.209 [48067.805231] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_from Apr 26 05:25:18 192.168.122.209 [48068.903099] [tdb] Start Tempesta DB Apr 26 05:25:18 192.168.122.209 [48069.038902] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:25:19 192.168.122.209 [48069.707275] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48069.707275] Maybe that's fine, but it's worth checking the [48069.707275] config - if there is no relations between the [48069.707275] names, then host name confusion attack is possible. Apr 26 05:25:19 192.168.122.209 [48069.846026] [tempesta fw] Configuration processing is completed. Apr 26 05:25:19 192.168.122.209 [48069.902558] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:25:19 192.168.122.209 [48069.929875] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:25:19 192.168.122.209 [48069.956231] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:25:19 192.168.122.209 [48070.001958] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:25:19 192.168.122.209 [48070.003185] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:25:19 192.168.122.209 [48070.041958] [tempesta fw] Tempesta FW is ready Apr 26 05:25:20 192.168.122.209 [48070.619992] [tdb] Close table 'client0.tdb' Apr 26 05:25:20 192.168.122.209 [48070.904947] [tdb] Close table 'sessions0.tdb' Apr 26 05:25:20 192.168.122.209 [48071.143120] [tdb] Close table 'filter0.tdb' Apr 26 05:25:20 192.168.122.209 [48071.143555] [tempesta fw] modules are stopped Apr 26 05:25:20 192.168.122.209 [48071.334929] [tempesta fw] exiting... Apr 26 05:25:21 192.168.122.209 [48071.451782] [tdb] Shutdown Tempesta DB Apr 26 05:25:21 192.168.122.209 [48071.707739] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_from Apr 26 05:25:21 192.168.122.209 [48071.716700] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_if_match Apr 26 05:25:22 192.168.122.209 [48072.824566] [tdb] Start Tempesta DB Apr 26 05:25:22 192.168.122.209 [48072.967173] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:25:23 192.168.122.209 [48073.655349] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48073.655349] Maybe that's fine, but it's worth checking the [48073.655349] config - if there is no relations between the [48073.655349] names, then host name confusion attack is possible. Apr 26 05:25:23 192.168.122.209 [48073.790055] [tempesta fw] Configuration processing is completed. Apr 26 05:25:23 192.168.122.209 [48073.844898] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:25:23 192.168.122.209 [48073.872308] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:25:23 192.168.122.209 [48073.899125] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:25:23 192.168.122.209 [48073.942017] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:25:23 192.168.122.209 [48073.943042] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:25:23 192.168.122.209 [48073.998005] [tempesta fw] Tempesta FW is ready Apr 26 05:25:24 192.168.122.209 [48074.564199] [tdb] Close table 'client0.tdb' Apr 26 05:25:24 192.168.122.209 [48074.763536] [tdb] Close table 'sessions0.tdb' Apr 26 05:25:24 192.168.122.209 [48074.986729] [tdb] Close table 'filter0.tdb' Apr 26 05:25:24 192.168.122.209 [48074.987170] [tempesta fw] modules are stopped Apr 26 05:25:24 192.168.122.209 [48075.155851] [tempesta fw] exiting... Apr 26 05:25:24 192.168.122.209 [48075.300278] [tdb] Shutdown Tempesta DB Apr 26 05:25:25 192.168.122.209 [48075.511777] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_if_match Apr 26 05:25:25 192.168.122.209 [48075.524865] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_if_modified_since Apr 26 05:25:26 192.168.122.209 [48076.630255] [tdb] Start Tempesta DB Apr 26 05:25:26 192.168.122.209 [48076.769742] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:25:27 192.168.122.209 [48077.471381] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48077.471381] Maybe that's fine, but it's worth checking the [48077.471381] config - if there is no relations between the [48077.471381] names, then host name confusion attack is possible. Apr 26 05:25:27 192.168.122.209 [48077.602126] [tempesta fw] Configuration processing is completed. Apr 26 05:25:27 192.168.122.209 [48077.652538] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:25:27 192.168.122.209 [48077.680776] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:25:27 192.168.122.209 [48077.707409] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:25:27 192.168.122.209 [48077.750082] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:25:27 192.168.122.209 [48077.790011] [tempesta fw] Tempesta FW is ready Apr 26 05:25:27 192.168.122.209 [48078.373767] [tdb] Close table 'client0.tdb' Apr 26 05:25:28 192.168.122.209 [48078.557480] [tdb] Close table 'sessions0.tdb' Apr 26 05:25:28 192.168.122.209 [48078.792140] [tdb] Close table 'filter0.tdb' Apr 26 05:25:28 192.168.122.209 [48078.792578] net_ratelimit: 1 callbacks suppressed Apr 26 05:25:28 192.168.122.209 [48078.792580] [tempesta fw] modules are stopped Apr 26 05:25:28 192.168.122.209 [48078.987123] [tempesta fw] exiting... Apr 26 05:25:28 192.168.122.209 [48079.123720] [tdb] Shutdown Tempesta DB Apr 26 05:25:28 192.168.122.209 [48079.335629] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_if_modified_since Apr 26 05:25:28 192.168.122.209 [48079.348331] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_if_range Apr 26 05:25:30 192.168.122.209 [48080.443034] [tdb] Start Tempesta DB Apr 26 05:25:30 192.168.122.209 [48080.560794] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:25:30 192.168.122.209 [48081.259426] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48081.259426] Maybe that's fine, but it's worth checking the [48081.259426] config - if there is no relations between the [48081.259426] names, then host name confusion attack is possible. Apr 26 05:25:31 192.168.122.209 [48081.410204] [tempesta fw] Configuration processing is completed. Apr 26 05:25:31 192.168.122.209 [48081.460742] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:25:31 192.168.122.209 [48081.489304] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:25:31 192.168.122.209 [48081.516138] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:25:31 192.168.122.209 [48081.566135] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:25:31 192.168.122.209 [48081.567500] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:25:31 192.168.122.209 [48081.614073] [tempesta fw] Tempesta FW is ready Apr 26 05:25:31 192.168.122.209 [48082.184884] [tdb] Close table 'client0.tdb' Apr 26 05:25:31 192.168.122.209 [48082.372635] [tdb] Close table 'sessions0.tdb' Apr 26 05:25:32 192.168.122.209 [48082.603713] [tdb] Close table 'filter0.tdb' Apr 26 05:25:32 192.168.122.209 [48082.604156] [tempesta fw] modules are stopped Apr 26 05:25:32 192.168.122.209 [48082.862374] [tempesta fw] exiting... Apr 26 05:25:32 192.168.122.209 [48082.981301] [tdb] Shutdown Tempesta DB Apr 26 05:25:32 192.168.122.209 [48083.196148] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_if_range Apr 26 05:25:32 192.168.122.209 [48083.217286] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_if_unmodified_since Apr 26 05:25:33 192.168.122.209 [48084.320748] [tdb] Start Tempesta DB Apr 26 05:25:34 192.168.122.209 [48084.461666] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:25:34 192.168.122.209 [48085.135482] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48085.135482] Maybe that's fine, but it's worth checking the [48085.135482] config - if there is no relations between the [48085.135482] names, then host name confusion attack is possible. Apr 26 05:25:34 192.168.122.209 [48085.294256] [tempesta fw] Configuration processing is completed. Apr 26 05:25:34 192.168.122.209 [48085.346045] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:25:34 192.168.122.209 [48085.383766] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:25:35 192.168.122.209 [48085.410936] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:25:35 192.168.122.209 [48085.450143] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:25:35 192.168.122.209 [48085.451181] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:25:35 192.168.122.209 [48085.502157] [tempesta fw] Tempesta FW is ready Apr 26 05:25:35 192.168.122.209 [48086.119176] [tdb] Close table 'client0.tdb' Apr 26 05:25:35 192.168.122.209 [48086.311395] [tdb] Close table 'sessions0.tdb' Apr 26 05:25:36 192.168.122.209 [48086.543971] [tdb] Close table 'filter0.tdb' Apr 26 05:25:36 192.168.122.209 [48086.544412] [tempesta fw] modules are stopped Apr 26 05:25:36 192.168.122.209 [48086.746351] [tempesta fw] exiting... Apr 26 05:25:36 192.168.122.209 [48086.861759] [tdb] Shutdown Tempesta DB Apr 26 05:25:36 192.168.122.209 [48087.137465] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_if_unmodified_since Apr 26 05:25:36 192.168.122.209 [48087.149624] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_last_modified Apr 26 05:25:37 192.168.122.209 [48088.322346] [tdb] Start Tempesta DB Apr 26 05:25:38 192.168.122.209 [48088.483967] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:25:38 192.168.122.209 [48089.191535] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48089.191535] Maybe that's fine, but it's worth checking the [48089.191535] config - if there is no relations between the [48089.191535] names, then host name confusion attack is possible. Apr 26 05:25:38 192.168.122.209 [48089.330222] [tempesta fw] Configuration processing is completed. Apr 26 05:25:38 192.168.122.209 [48089.384998] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:25:39 192.168.122.209 [48089.412604] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:25:39 192.168.122.209 [48089.439071] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:25:39 192.168.122.209 [48089.498267] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:25:39 192.168.122.209 [48089.499969] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:25:39 192.168.122.209 [48089.546210] [tempesta fw] Tempesta FW is ready Apr 26 05:25:39 192.168.122.209 [48090.116935] [tdb] Close table 'client0.tdb' Apr 26 05:25:39 192.168.122.209 [48090.317475] [tdb] Close table 'sessions0.tdb' Apr 26 05:25:40 192.168.122.209 [48090.545137] [tdb] Close table 'filter0.tdb' Apr 26 05:25:40 192.168.122.209 [48090.545563] [tempesta fw] modules are stopped Apr 26 05:25:40 192.168.122.209 [48090.785685] [tempesta fw] exiting... Apr 26 05:25:40 192.168.122.209 [48090.941341] [tdb] Shutdown Tempesta DB Apr 26 05:25:40 192.168.122.209 [48091.141561] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_last_modified Apr 26 05:25:40 192.168.122.209 [48091.157800] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_max_forwards Apr 26 05:25:41 192.168.122.209 [48092.235319] [tdb] Start Tempesta DB Apr 26 05:25:41 192.168.122.209 [48092.387016] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:25:42 192.168.122.209 [48093.099348] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48093.099348] Maybe that's fine, but it's worth checking the [48093.099348] config - if there is no relations between the [48093.099348] names, then host name confusion attack is possible. Apr 26 05:25:42 192.168.122.209 [48093.246328] [tempesta fw] Configuration processing is completed. Apr 26 05:25:42 192.168.122.209 [48093.297431] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:25:42 192.168.122.209 [48093.326932] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:25:42 192.168.122.209 [48093.354688] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:25:43 192.168.122.209 [48093.426310] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:25:43 192.168.122.209 [48093.428050] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:25:43 192.168.122.209 [48093.470252] [tempesta fw] Tempesta FW is ready Apr 26 05:25:43 192.168.122.209 [48094.061100] [tdb] Close table 'client0.tdb' Apr 26 05:25:43 192.168.122.209 [48094.251627] [tdb] Close table 'sessions0.tdb' Apr 26 05:25:44 192.168.122.209 [48094.497483] [tdb] Close table 'filter0.tdb' Apr 26 05:25:44 192.168.122.209 [48094.497934] [tempesta fw] modules are stopped Apr 26 05:25:44 192.168.122.209 [48094.696263] [tempesta fw] exiting... Apr 26 05:25:44 192.168.122.209 [48094.834580] [tdb] Shutdown Tempesta DB Apr 26 05:25:44 192.168.122.209 [48095.044329] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_max_forwards Apr 26 05:25:44 192.168.122.209 [48095.057313] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_pragma Apr 26 05:25:45 192.168.122.209 [48096.136806] [tdb] Start Tempesta DB Apr 26 05:25:45 192.168.122.209 [48096.274056] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:25:46 192.168.122.209 [48096.931541] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48096.931541] Maybe that's fine, but it's worth checking the [48096.931541] config - if there is no relations between the [48096.931541] names, then host name confusion attack is possible. Apr 26 05:25:46 192.168.122.209 [48097.062321] [tempesta fw] Configuration processing is completed. Apr 26 05:25:46 192.168.122.209 [48097.113667] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:25:46 192.168.122.209 [48097.141599] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:25:46 192.168.122.209 [48097.168364] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:25:46 192.168.122.209 [48097.218353] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:25:46 192.168.122.209 [48097.219756] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:25:46 192.168.122.209 [48097.266317] [tempesta fw] Tempesta FW is ready Apr 26 05:25:47 192.168.122.209 [48097.838457] [tdb] Close table 'client0.tdb' Apr 26 05:25:47 192.168.122.209 [48098.033078] [tdb] Close table 'sessions0.tdb' Apr 26 05:25:47 192.168.122.209 [48098.284829] [tdb] Close table 'filter0.tdb' Apr 26 05:25:47 192.168.122.209 [48098.285260] [tempesta fw] modules are stopped Apr 26 05:25:48 192.168.122.209 [48098.484567] [tempesta fw] exiting... Apr 26 05:25:48 192.168.122.209 [48098.608696] [tdb] Shutdown Tempesta DB Apr 26 05:25:48 192.168.122.209 [48098.832074] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_pragma Apr 26 05:25:48 192.168.122.209 [48098.839600] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_range Apr 26 05:25:49 192.168.122.209 [48099.917557] [tdb] Start Tempesta DB Apr 26 05:25:49 192.168.122.209 [48100.055026] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:25:50 192.168.122.209 [48100.735687] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48100.735687] Maybe that's fine, but it's worth checking the [48100.735687] config - if there is no relations between the [48100.735687] names, then host name confusion attack is possible. Apr 26 05:25:50 192.168.122.209 [48100.874467] [tempesta fw] Configuration processing is completed. Apr 26 05:25:50 192.168.122.209 [48100.935229] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:25:50 192.168.122.209 [48100.966268] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:25:50 192.168.122.209 [48100.994464] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:25:50 192.168.122.209 [48101.038406] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:25:50 192.168.122.209 [48101.082295] [tempesta fw] Tempesta FW is ready Apr 26 05:25:51 192.168.122.209 [48101.659029] [tdb] Close table 'client0.tdb' Apr 26 05:25:51 192.168.122.209 [48101.851055] [tdb] Close table 'sessions0.tdb' Apr 26 05:25:51 192.168.122.209 [48102.084193] [tdb] Close table 'filter0.tdb' Apr 26 05:25:51 192.168.122.209 [48102.084682] net_ratelimit: 1 callbacks suppressed Apr 26 05:25:51 192.168.122.209 [48102.084684] [tempesta fw] modules are stopped Apr 26 05:25:51 192.168.122.209 [48102.304021] [tempesta fw] exiting... Apr 26 05:25:52 192.168.122.209 [48102.425992] [tdb] Shutdown Tempesta DB Apr 26 05:25:52 192.168.122.209 [48102.636880] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_range Apr 26 05:25:52 192.168.122.209 [48102.667638] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_referer Apr 26 05:25:53 192.168.122.209 [48103.725320] [tdb] Start Tempesta DB Apr 26 05:25:53 192.168.122.209 [48103.876092] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:25:54 192.168.122.209 [48104.496013] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48104.496013] Maybe that's fine, but it's worth checking the [48104.496013] config - if there is no relations between the [48104.496013] names, then host name confusion attack is possible. Apr 26 05:25:54 192.168.122.209 [48104.630468] [tempesta fw] Configuration processing is completed. Apr 26 05:25:54 192.168.122.209 [48104.681754] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:25:54 192.168.122.209 [48104.709897] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:25:54 192.168.122.209 [48104.737036] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:25:54 192.168.122.209 [48104.782426] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:25:54 192.168.122.209 [48104.783964] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:25:54 192.168.122.209 [48104.822399] [tempesta fw] Tempesta FW is ready Apr 26 05:25:54 192.168.122.209 [48105.401186] [tdb] Close table 'client0.tdb' Apr 26 05:25:55 192.168.122.209 [48105.589688] [tdb] Close table 'sessions0.tdb' Apr 26 05:25:55 192.168.122.209 [48105.819964] [tdb] Close table 'filter0.tdb' Apr 26 05:25:55 192.168.122.209 [48105.820395] [tempesta fw] modules are stopped Apr 26 05:25:55 192.168.122.209 [48106.026841] [tempesta fw] exiting... Apr 26 05:25:55 192.168.122.209 [48106.170201] [tdb] Shutdown Tempesta DB Apr 26 05:25:55 192.168.122.209 [48106.385883] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_referer Apr 26 05:25:55 192.168.122.209 [48106.399054] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_trailer Apr 26 05:25:57 192.168.122.209 [48107.452503] [tdb] Start Tempesta DB Apr 26 05:25:57 192.168.122.209 [48107.589730] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:25:57 192.168.122.209 [48108.295802] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48108.295802] Maybe that's fine, but it's worth checking the [48108.295802] config - if there is no relations between the [48108.295802] names, then host name confusion attack is possible. Apr 26 05:25:58 192.168.122.209 [48108.434843] [tempesta fw] Configuration processing is completed. Apr 26 05:25:58 192.168.122.209 [48108.493742] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:25:58 192.168.122.209 [48108.524146] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:25:58 192.168.122.209 [48108.550856] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:25:58 192.168.122.209 [48108.606467] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:25:58 192.168.122.209 [48108.608041] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:25:58 192.168.122.209 [48108.646460] [tempesta fw] Tempesta FW is ready Apr 26 05:25:58 192.168.122.209 [48109.203679] [tdb] Close table 'client0.tdb' Apr 26 05:25:58 192.168.122.209 [48109.395838] [tdb] Close table 'sessions0.tdb' Apr 26 05:25:59 192.168.122.209 [48109.658906] [tdb] Close table 'filter0.tdb' Apr 26 05:25:59 192.168.122.209 [48109.659350] [tempesta fw] modules are stopped Apr 26 05:25:59 192.168.122.209 [48109.843990] [tempesta fw] exiting... Apr 26 05:25:59 192.168.122.209 [48109.959154] [tdb] Shutdown Tempesta DB Apr 26 05:25:59 192.168.122.209 [48110.185927] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_trailer Apr 26 05:25:59 192.168.122.209 [48110.198295] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_user_agent Apr 26 05:26:00 192.168.122.209 [48111.338091] [tdb] Start Tempesta DB Apr 26 05:26:01 192.168.122.209 [48111.470854] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:26:01 192.168.122.209 [48112.159624] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48112.159624] Maybe that's fine, but it's worth checking the [48112.159624] config - if there is no relations between the [48112.159624] names, then host name confusion attack is possible. Apr 26 05:26:01 192.168.122.209 [48112.282983] [tempesta fw] Configuration processing is completed. Apr 26 05:26:01 192.168.122.209 [48112.332860] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:26:01 192.168.122.209 [48112.360767] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:26:01 192.168.122.209 [48112.387816] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:26:02 192.168.122.209 [48112.438537] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:26:02 192.168.122.209 [48112.494535] [tempesta fw] Tempesta FW is ready Apr 26 05:26:02 192.168.122.209 [48113.067778] [tdb] Close table 'client0.tdb' Apr 26 05:26:02 192.168.122.209 [48113.258725] [tdb] Close table 'sessions0.tdb' Apr 26 05:26:03 192.168.122.209 [48113.511696] [tdb] Close table 'filter0.tdb' Apr 26 05:26:03 192.168.122.209 [48113.512205] net_ratelimit: 1 callbacks suppressed Apr 26 05:26:03 192.168.122.209 [48113.512206] [tempesta fw] modules are stopped Apr 26 05:26:03 192.168.122.209 [48113.711858] [tempesta fw] exiting... Apr 26 05:26:03 192.168.122.209 [48113.831585] [tdb] Shutdown Tempesta DB Apr 26 05:26:03 192.168.122.209 [48114.029769] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_user_agent Apr 26 05:26:03 192.168.122.209 [48114.045964] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_via Apr 26 05:26:04 192.168.122.209 [48115.096368] [tdb] Start Tempesta DB Apr 26 05:26:04 192.168.122.209 [48115.239907] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:26:05 192.168.122.209 [48115.943873] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48115.943873] Maybe that's fine, but it's worth checking the [48115.943873] config - if there is no relations between the [48115.943873] names, then host name confusion attack is possible. Apr 26 05:26:05 192.168.122.209 [48116.086666] [tempesta fw] Configuration processing is completed. Apr 26 05:26:05 192.168.122.209 [48116.140354] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:26:05 192.168.122.209 [48116.170388] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:26:05 192.168.122.209 [48116.197372] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:26:05 192.168.122.209 [48116.238546] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:26:05 192.168.122.209 [48116.239641] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:26:05 192.168.122.209 [48116.286540] [tempesta fw] Tempesta FW is ready Apr 26 05:26:06 192.168.122.209 [48116.843255] [tdb] Close table 'client0.tdb' Apr 26 05:26:06 192.168.122.209 [48117.041713] [tdb] Close table 'sessions0.tdb' Apr 26 05:26:06 192.168.122.209 [48117.281381] [tdb] Close table 'filter0.tdb' Apr 26 05:26:06 192.168.122.209 [48117.281812] [tempesta fw] modules are stopped Apr 26 05:26:07 192.168.122.209 [48117.467479] [tempesta fw] exiting... Apr 26 05:26:07 192.168.122.209 [48117.585672] [tdb] Shutdown Tempesta DB Apr 26 05:26:07 192.168.122.209 [48117.822030] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_via Apr 26 05:26:07 192.168.122.209 [48117.838030] Start test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_accept_ranges Apr 26 05:26:08 192.168.122.209 [48118.981669] [tdb] Start Tempesta DB Apr 26 05:26:08 192.168.122.209 [48119.127259] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:26:09 192.168.122.209 [48119.783243] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48119.783243] Maybe that's fine, but it's worth checking the [48119.783243] config - if there is no relations between the [48119.783243] names, then host name confusion attack is possible. Apr 26 05:26:09 192.168.122.209 [48119.938627] [tempesta fw] Configuration processing is completed. Apr 26 05:26:09 192.168.122.209 [48119.994459] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:26:09 192.168.122.209 [48120.022518] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:26:09 192.168.122.209 [48120.049601] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:26:09 192.168.122.209 [48120.102624] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:26:09 192.168.122.209 [48120.104020] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:26:09 192.168.122.209 [48120.142601] [tempesta fw] Tempesta FW is ready Apr 26 05:26:10 192.168.122.209 [48120.736023] [tdb] Close table 'client0.tdb' Apr 26 05:26:10 192.168.122.209 [48120.942212] [tdb] Close table 'sessions0.tdb' Apr 26 05:26:10 192.168.122.209 [48121.196439] [tdb] Close table 'filter0.tdb' Apr 26 05:26:10 192.168.122.209 [48121.196881] [tempesta fw] modules are stopped Apr 26 05:26:10 192.168.122.209 [48121.396419] [tempesta fw] exiting... Apr 26 05:26:11 192.168.122.209 [48121.529131] [tdb] Shutdown Tempesta DB Apr 26 05:26:11 192.168.122.209 [48121.796687] End test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_accept_ranges Apr 26 05:26:11 192.168.122.209 [48121.806048] Start test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_allow Apr 26 05:26:12 192.168.122.209 [48122.936373] [tdb] Start Tempesta DB Apr 26 05:26:12 192.168.122.209 [48123.073515] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:26:13 192.168.122.209 [48123.772027] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48123.772027] Maybe that's fine, but it's worth checking the [48123.772027] config - if there is no relations between the [48123.772027] names, then host name confusion attack is possible. Apr 26 05:26:13 192.168.122.209 [48123.915071] [tempesta fw] Configuration processing is completed. Apr 26 05:26:13 192.168.122.209 [48123.966739] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:26:13 192.168.122.209 [48123.997476] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:26:13 192.168.122.209 [48124.024963] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:26:13 192.168.122.209 [48124.070695] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:26:13 192.168.122.209 [48124.110570] [tempesta fw] Tempesta FW is ready Apr 26 05:26:14 192.168.122.209 [48124.746248] [tdb] Close table 'client0.tdb' Apr 26 05:26:14 192.168.122.209 [48124.936753] [tdb] Close table 'sessions0.tdb' Apr 26 05:26:14 192.168.122.209 [48125.187531] [tdb] Close table 'filter0.tdb' Apr 26 05:26:14 192.168.122.209 [48125.187978] net_ratelimit: 1 callbacks suppressed Apr 26 05:26:14 192.168.122.209 [48125.187979] [tempesta fw] modules are stopped Apr 26 05:26:14 192.168.122.209 [48125.400265] [tempesta fw] exiting... Apr 26 05:26:15 192.168.122.209 [48125.523410] [tdb] Shutdown Tempesta DB Apr 26 05:26:15 192.168.122.209 [48125.740992] End test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_allow Apr 26 05:26:15 192.168.122.209 [48125.751646] Start test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_connection Apr 26 05:26:16 192.168.122.209 [48126.852655] [tdb] Start Tempesta DB Apr 26 05:26:16 192.168.122.209 [48126.996272] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:26:17 192.168.122.209 [48127.683803] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48127.683803] Maybe that's fine, but it's worth checking the [48127.683803] config - if there is no relations between the [48127.683803] names, then host name confusion attack is possible. Apr 26 05:26:17 192.168.122.209 [48127.854776] [tempesta fw] Configuration processing is completed. Apr 26 05:26:17 192.168.122.209 [48127.906040] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:26:17 192.168.122.209 [48127.933790] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:26:17 192.168.122.209 [48127.960702] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:26:17 192.168.122.209 [48128.010723] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:26:17 192.168.122.209 [48128.012110] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:26:17 192.168.122.209 [48128.050702] [tempesta fw] Tempesta FW is ready Apr 26 05:26:18 192.168.122.209 [48128.552693] [tdb] Close table 'client0.tdb' Apr 26 05:26:18 192.168.122.209 [48128.775279] [tdb] Close table 'sessions0.tdb' Apr 26 05:26:18 192.168.122.209 [48129.008385] [tdb] Close table 'filter0.tdb' Apr 26 05:26:18 192.168.122.209 [48129.008836] [tempesta fw] modules are stopped Apr 26 05:26:18 192.168.122.209 [48129.212301] [tempesta fw] exiting... Apr 26 05:26:18 192.168.122.209 [48129.324877] [tdb] Shutdown Tempesta DB Apr 26 05:26:19 192.168.122.209 [48129.535677] End test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_connection Apr 26 05:26:19 192.168.122.209 [48129.547090] Start test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_content_encoding Apr 26 05:26:20 192.168.122.209 [48130.690543] [tdb] Start Tempesta DB Apr 26 05:26:20 192.168.122.209 [48130.853048] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:26:21 192.168.122.209 [48131.572073] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48131.572073] Maybe that's fine, but it's worth checking the [48131.572073] config - if there is no relations between the [48131.572073] names, then host name confusion attack is possible. Apr 26 05:26:21 192.168.122.209 [48131.750811] [tempesta fw] Configuration processing is completed. Apr 26 05:26:21 192.168.122.209 [48131.802288] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:26:21 192.168.122.209 [48131.832763] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:26:21 192.168.122.209 [48131.859758] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:26:21 192.168.122.209 [48131.910804] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:26:21 192.168.122.209 [48131.912484] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:26:21 192.168.122.209 [48131.950755] [tempesta fw] Tempesta FW is ready Apr 26 05:26:22 192.168.122.209 [48132.544428] [tdb] Close table 'client0.tdb' Apr 26 05:26:22 192.168.122.209 [48132.734770] [tdb] Close table 'sessions0.tdb' Apr 26 05:26:22 192.168.122.209 [48132.983982] [tdb] Close table 'filter0.tdb' Apr 26 05:26:22 192.168.122.209 [48132.984443] [tempesta fw] modules are stopped Apr 26 05:26:22 192.168.122.209 [48133.204316] [tempesta fw] exiting... Apr 26 05:26:22 192.168.122.209 [48133.327029] [tdb] Shutdown Tempesta DB Apr 26 05:26:23 192.168.122.209 [48133.544214] End test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_content_encoding Apr 26 05:26:23 192.168.122.209 [48133.558886] Start test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_content_language Apr 26 05:26:24 192.168.122.209 [48134.650096] [tdb] Start Tempesta DB Apr 26 05:26:24 192.168.122.209 [48134.802035] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:26:25 192.168.122.209 [48135.488205] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48135.488205] Maybe that's fine, but it's worth checking the [48135.488205] config - if there is no relations between the [48135.488205] names, then host name confusion attack is possible. Apr 26 05:26:25 192.168.122.209 [48135.654939] [tempesta fw] Configuration processing is completed. Apr 26 05:26:25 192.168.122.209 [48135.708074] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:26:25 192.168.122.209 [48135.736778] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:26:25 192.168.122.209 [48135.765207] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:26:25 192.168.122.209 [48135.822874] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:26:25 192.168.122.209 [48135.870808] [tempesta fw] Tempesta FW is ready Apr 26 05:26:26 192.168.122.209 [48136.457106] [tdb] Close table 'client0.tdb' Apr 26 05:26:26 192.168.122.209 [48136.649415] [tdb] Close table 'sessions0.tdb' Apr 26 05:26:26 192.168.122.209 [48136.880844] [tdb] Close table 'filter0.tdb' Apr 26 05:26:26 192.168.122.209 [48136.881289] net_ratelimit: 1 callbacks suppressed Apr 26 05:26:26 192.168.122.209 [48136.881291] [tempesta fw] modules are stopped Apr 26 05:26:26 192.168.122.209 [48137.060559] [tempesta fw] exiting... Apr 26 05:26:26 192.168.122.209 [48137.178531] [tdb] Shutdown Tempesta DB Apr 26 05:26:26 192.168.122.209 [48137.389146] End test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_content_language Apr 26 05:26:26 192.168.122.209 [48137.403756] Start test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_content_location Apr 26 05:26:28 192.168.122.209 [48138.535045] [tdb] Start Tempesta DB Apr 26 05:26:28 192.168.122.209 [48138.665425] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:26:28 192.168.122.209 [48139.355485] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48139.355485] Maybe that's fine, but it's worth checking the [48139.355485] config - if there is no relations between the [48139.355485] names, then host name confusion attack is possible. Apr 26 05:26:29 192.168.122.209 [48139.513120] [tempesta fw] Configuration processing is completed. Apr 26 05:26:29 192.168.122.209 [48139.557753] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:26:29 192.168.122.209 [48139.587407] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:26:29 192.168.122.209 [48139.613797] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:26:29 192.168.122.209 [48139.670864] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:26:29 192.168.122.209 [48139.672347] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:26:29 192.168.122.209 [48139.710834] [tempesta fw] Tempesta FW is ready Apr 26 05:26:29 192.168.122.209 [48140.253453] [tdb] Close table 'client0.tdb' Apr 26 05:26:30 192.168.122.209 [48140.449075] [tdb] Close table 'sessions0.tdb' Apr 26 05:26:30 192.168.122.209 [48140.697023] [tdb] Close table 'filter0.tdb' Apr 26 05:26:30 192.168.122.209 [48140.697474] [tempesta fw] modules are stopped Apr 26 05:26:30 192.168.122.209 [48140.911633] [tempesta fw] exiting... Apr 26 05:26:30 192.168.122.209 [48141.061078] [tdb] Shutdown Tempesta DB Apr 26 05:26:30 192.168.122.209 [48141.308620] End test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_content_location Apr 26 05:26:30 192.168.122.209 [48141.318749] Start test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_content_range Apr 26 05:26:32 192.168.122.209 [48142.488180] [tdb] Start Tempesta DB Apr 26 05:26:32 192.168.122.209 [48142.642860] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:26:32 192.168.122.209 [48143.348208] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48143.348208] Maybe that's fine, but it's worth checking the [48143.348208] config - if there is no relations between the [48143.348208] names, then host name confusion attack is possible. Apr 26 05:26:33 192.168.122.209 [48143.503107] [tempesta fw] Configuration processing is completed. Apr 26 05:26:33 192.168.122.209 [48143.550166] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:26:33 192.168.122.209 [48143.578388] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:26:33 192.168.122.209 [48143.605819] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:26:33 192.168.122.209 [48143.666939] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:26:33 192.168.122.209 [48143.668660] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:26:33 192.168.122.209 [48143.706900] [tempesta fw] Tempesta FW is ready Apr 26 05:26:33 192.168.122.209 [48144.260721] [tdb] Close table 'client0.tdb' Apr 26 05:26:34 192.168.122.209 [48144.451210] [tdb] Close table 'sessions0.tdb' Apr 26 05:26:34 192.168.122.209 [48144.670807] [tdb] Close table 'filter0.tdb' Apr 26 05:26:34 192.168.122.209 [48144.671254] [tempesta fw] modules are stopped Apr 26 05:26:34 192.168.122.209 [48144.904713] [tempesta fw] exiting... Apr 26 05:26:34 192.168.122.209 [48145.012882] [tdb] Shutdown Tempesta DB Apr 26 05:26:34 192.168.122.209 [48145.247734] End test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_content_range Apr 26 05:26:34 192.168.122.209 [48145.270288] Start test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_content_type Apr 26 05:26:35 192.168.122.209 [48146.337273] [tdb] Start Tempesta DB Apr 26 05:26:36 192.168.122.209 [48146.499519] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:26:36 192.168.122.209 [48147.196231] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48147.196231] Maybe that's fine, but it's worth checking the [48147.196231] config - if there is no relations between the [48147.196231] names, then host name confusion attack is possible. Apr 26 05:26:36 192.168.122.209 [48147.342938] [tempesta fw] Configuration processing is completed. Apr 26 05:26:36 192.168.122.209 [48147.404418] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:26:37 192.168.122.209 [48147.455671] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:26:37 192.168.122.209 [48147.491834] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:26:37 192.168.122.209 [48147.538933] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:26:37 192.168.122.209 [48147.578882] [tempesta fw] Tempesta FW is ready Apr 26 05:26:37 192.168.122.209 [48148.126537] [tdb] Close table 'client0.tdb' Apr 26 05:26:37 192.168.122.209 [48148.343972] [tdb] Close table 'sessions0.tdb' Apr 26 05:26:38 192.168.122.209 [48148.591810] [tdb] Close table 'filter0.tdb' Apr 26 05:26:38 192.168.122.209 [48148.592255] net_ratelimit: 1 callbacks suppressed Apr 26 05:26:38 192.168.122.209 [48148.592257] [tempesta fw] modules are stopped Apr 26 05:26:38 192.168.122.209 [48148.783722] [tempesta fw] exiting... Apr 26 05:26:38 192.168.122.209 [48148.924814] [tdb] Shutdown Tempesta DB Apr 26 05:26:38 192.168.122.209 [48149.128918] End test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_content_type Apr 26 05:26:38 192.168.122.209 [48149.141326] Start test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_date Apr 26 05:26:39 192.168.122.209 [48150.258569] [tdb] Start Tempesta DB Apr 26 05:26:39 192.168.122.209 [48150.400218] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:26:40 192.168.122.209 [48151.012308] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48151.012308] Maybe that's fine, but it's worth checking the [48151.012308] config - if there is no relations between the [48151.012308] names, then host name confusion attack is possible. Apr 26 05:26:40 192.168.122.209 [48151.179081] [tempesta fw] Configuration processing is completed. Apr 26 05:26:40 192.168.122.209 [48151.231783] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:26:40 192.168.122.209 [48151.261347] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:26:40 192.168.122.209 [48151.290891] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:26:40 192.168.122.209 [48151.338988] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:26:40 192.168.122.209 [48151.340173] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:26:40 192.168.122.209 [48151.378985] [tempesta fw] Tempesta FW is ready Apr 26 05:26:41 192.168.122.209 [48151.989312] [tdb] Close table 'client0.tdb' Apr 26 05:26:41 192.168.122.209 [48152.190626] [tdb] Close table 'sessions0.tdb' Apr 26 05:26:42 192.168.122.209 [48152.458886] [tdb] Close table 'filter0.tdb' Apr 26 05:26:42 192.168.122.209 [48152.459321] [tempesta fw] modules are stopped Apr 26 05:26:42 192.168.122.209 [48152.672371] [tempesta fw] exiting... Apr 26 05:26:42 192.168.122.209 [48152.798292] [tdb] Shutdown Tempesta DB Apr 26 05:26:42 192.168.122.209 [48153.035630] End test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_date Apr 26 05:26:42 192.168.122.209 [48153.043589] Start test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_expires Apr 26 05:26:43 192.168.122.209 [48154.140612] [tdb] Start Tempesta DB Apr 26 05:26:43 192.168.122.209 [48154.289924] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:26:44 192.168.122.209 [48154.940341] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48154.940341] Maybe that's fine, but it's worth checking the [48154.940341] config - if there is no relations between the [48154.940341] names, then host name confusion attack is possible. Apr 26 05:26:44 192.168.122.209 [48155.111060] [tempesta fw] Configuration processing is completed. Apr 26 05:26:44 192.168.122.209 [48155.165534] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:26:44 192.168.122.209 [48155.197043] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:26:44 192.168.122.209 [48155.226804] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:26:44 192.168.122.209 [48155.283099] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:26:44 192.168.122.209 [48155.284765] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:26:44 192.168.122.209 [48155.331053] [tempesta fw] Tempesta FW is ready Apr 26 05:26:45 192.168.122.209 [48155.908594] [tdb] Close table 'client0.tdb' Apr 26 05:26:45 192.168.122.209 [48156.129318] [tdb] Close table 'sessions0.tdb' Apr 26 05:26:45 192.168.122.209 [48156.357006] [tdb] Close table 'filter0.tdb' Apr 26 05:26:45 192.168.122.209 [48156.357450] [tempesta fw] modules are stopped Apr 26 05:26:46 192.168.122.209 [48156.536654] [tempesta fw] exiting... Apr 26 05:26:46 192.168.122.209 [48156.657959] [tdb] Shutdown Tempesta DB Apr 26 05:26:46 192.168.122.209 [48156.892691] End test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_expires Apr 26 05:26:46 192.168.122.209 [48156.907008] Start test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_last_modified Apr 26 05:26:47 192.168.122.209 [48157.939689] [tdb] Start Tempesta DB Apr 26 05:26:47 192.168.122.209 [48158.077492] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:26:48 192.168.122.209 [48158.724395] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48158.724395] Maybe that's fine, but it's worth checking the [48158.724395] config - if there is no relations between the [48158.724395] names, then host name confusion attack is possible. Apr 26 05:26:48 192.168.122.209 [48158.887173] [tempesta fw] Configuration processing is completed. Apr 26 05:26:48 192.168.122.209 [48158.940185] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:26:48 192.168.122.209 [48158.969012] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:26:48 192.168.122.209 [48158.996587] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:26:48 192.168.122.209 [48159.039036] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:26:48 192.168.122.209 [48159.087118] [tempesta fw] Tempesta FW is ready Apr 26 05:26:49 192.168.122.209 [48159.651319] [tdb] Close table 'client0.tdb' Apr 26 05:26:49 192.168.122.209 [48159.858168] [tdb] Close table 'sessions0.tdb' Apr 26 05:26:49 192.168.122.209 [48160.079422] [tdb] Close table 'filter0.tdb' Apr 26 05:26:49 192.168.122.209 [48160.079856] net_ratelimit: 1 callbacks suppressed Apr 26 05:26:49 192.168.122.209 [48160.079859] [tempesta fw] modules are stopped Apr 26 05:26:49 192.168.122.209 [48160.276486] [tempesta fw] exiting... Apr 26 05:26:49 192.168.122.209 [48160.401073] [tdb] Shutdown Tempesta DB Apr 26 05:26:50 192.168.122.209 [48160.615680] End test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_last_modified Apr 26 05:26:50 192.168.122.209 [48160.627890] Start test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_location Apr 26 05:26:51 192.168.122.209 [48161.771283] [tdb] Start Tempesta DB Apr 26 05:26:51 192.168.122.209 [48161.918925] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:26:52 192.168.122.209 [48162.584431] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48162.584431] Maybe that's fine, but it's worth checking the [48162.584431] config - if there is no relations between the [48162.584431] names, then host name confusion attack is possible. Apr 26 05:26:52 192.168.122.209 [48162.739200] [tempesta fw] Configuration processing is completed. Apr 26 05:26:52 192.168.122.209 [48162.803666] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:26:52 192.168.122.209 [48162.833463] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:26:52 192.168.122.209 [48162.862080] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:26:52 192.168.122.209 [48162.907171] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:26:52 192.168.122.209 [48162.908783] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:26:52 192.168.122.209 [48162.943140] [tempesta fw] Tempesta FW is ready Apr 26 05:26:53 192.168.122.209 [48163.547356] [tdb] Close table 'client0.tdb' Apr 26 05:26:53 192.168.122.209 [48163.765924] [tdb] Close table 'sessions0.tdb' Apr 26 05:26:53 192.168.122.209 [48164.008076] [tdb] Close table 'filter0.tdb' Apr 26 05:26:53 192.168.122.209 [48164.008520] [tempesta fw] modules are stopped Apr 26 05:26:53 192.168.122.209 [48164.180482] [tempesta fw] exiting... Apr 26 05:26:53 192.168.122.209 [48164.311356] [tdb] Shutdown Tempesta DB Apr 26 05:26:54 192.168.122.209 [48164.557445] End test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_location Apr 26 05:26:54 192.168.122.209 [48164.567892] Start test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_retry_after Apr 26 05:26:55 192.168.122.209 [48165.686019] [tdb] Start Tempesta DB Apr 26 05:26:55 192.168.122.209 [48165.859120] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:26:56 192.168.122.209 [48166.595875] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48166.595875] Maybe that's fine, but it's worth checking the [48166.595875] config - if there is no relations between the [48166.595875] names, then host name confusion attack is possible. Apr 26 05:26:56 192.168.122.209 [48166.743198] [tempesta fw] Configuration processing is completed. Apr 26 05:26:56 192.168.122.209 [48166.800535] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:26:56 192.168.122.209 [48166.830254] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:26:56 192.168.122.209 [48166.860558] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:26:56 192.168.122.209 [48166.915203] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:26:56 192.168.122.209 [48166.917019] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:26:56 192.168.122.209 [48166.955183] [tempesta fw] Tempesta FW is ready Apr 26 05:26:57 192.168.122.209 [48167.561265] [tdb] Close table 'client0.tdb' Apr 26 05:26:57 192.168.122.209 [48167.742066] [tdb] Close table 'sessions0.tdb' Apr 26 05:26:57 192.168.122.209 [48167.970416] [tdb] Close table 'filter0.tdb' Apr 26 05:26:57 192.168.122.209 [48167.970868] [tempesta fw] modules are stopped Apr 26 05:26:57 192.168.122.209 [48168.147282] [tempesta fw] exiting... Apr 26 05:26:57 192.168.122.209 [48168.269537] [tdb] Shutdown Tempesta DB Apr 26 05:26:58 192.168.122.209 [48168.485612] End test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_retry_after Apr 26 05:26:58 192.168.122.209 [48168.514191] Start test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_server Apr 26 05:26:59 192.168.122.209 [48169.630008] [tdb] Start Tempesta DB Apr 26 05:26:59 192.168.122.209 [48169.784716] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:27:00 192.168.122.209 [48170.440648] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48170.440648] Maybe that's fine, but it's worth checking the [48170.440648] config - if there is no relations between the [48170.440648] names, then host name confusion attack is possible. Apr 26 05:27:00 192.168.122.209 [48170.623269] [tempesta fw] Configuration processing is completed. Apr 26 05:27:00 192.168.122.209 [48170.676290] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:27:00 192.168.122.209 [48170.706978] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:27:00 192.168.122.209 [48170.734584] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:27:00 192.168.122.209 [48170.799284] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:27:00 192.168.122.209 [48170.839243] [tempesta fw] Tempesta FW is ready Apr 26 05:27:01 192.168.122.209 [48171.437367] [tdb] Close table 'client0.tdb' Apr 26 05:27:01 192.168.122.209 [48171.619282] [tdb] Close table 'sessions0.tdb' Apr 26 05:27:01 192.168.122.209 [48171.871612] [tdb] Close table 'filter0.tdb' Apr 26 05:27:01 192.168.122.209 [48171.872064] net_ratelimit: 1 callbacks suppressed Apr 26 05:27:01 192.168.122.209 [48171.872066] [tempesta fw] modules are stopped Apr 26 05:27:01 192.168.122.209 [48172.074942] [tempesta fw] exiting... Apr 26 05:27:01 192.168.122.209 [48172.208958] [tdb] Shutdown Tempesta DB Apr 26 05:27:02 192.168.122.209 [48172.441111] End test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_server Apr 26 05:27:02 192.168.122.209 [48172.460526] Start test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_vary Apr 26 05:27:03 192.168.122.209 [48173.571027] [tdb] Start Tempesta DB Apr 26 05:27:03 192.168.122.209 [48173.722076] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:27:03 192.168.122.209 [48174.392615] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48174.392615] Maybe that's fine, but it's worth checking the [48174.392615] config - if there is no relations between the [48174.392615] names, then host name confusion attack is possible. Apr 26 05:27:04 192.168.122.209 [48174.551347] [tempesta fw] Configuration processing is completed. Apr 26 05:27:04 192.168.122.209 [48174.610672] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:27:04 192.168.122.209 [48174.641925] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:27:04 192.168.122.209 [48174.671562] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:27:04 192.168.122.209 [48174.731290] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:27:04 192.168.122.209 [48174.733065] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:27:04 192.168.122.209 [48174.803297] [tempesta fw] Tempesta FW is ready Apr 26 05:27:04 192.168.122.209 [48175.365023] [tdb] Close table 'client0.tdb' Apr 26 05:27:05 192.168.122.209 [48175.565479] [tdb] Close table 'sessions0.tdb' Apr 26 05:27:05 192.168.122.209 [48175.809387] [tdb] Close table 'filter0.tdb' Apr 26 05:27:05 192.168.122.209 [48175.809823] [tempesta fw] modules are stopped Apr 26 05:27:05 192.168.122.209 [48175.975460] [tempesta fw] exiting... Apr 26 05:27:05 192.168.122.209 [48176.110978] [tdb] Shutdown Tempesta DB Apr 26 05:27:05 192.168.122.209 [48176.340258] End test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_vary Apr 26 05:27:05 192.168.122.209 [48176.349425] Start test: t_malformed.test_h2_malformed_headers.H2MalformedResponsesTest.test_age Apr 26 05:27:07 192.168.122.209 [48177.461011] [tdb] Start Tempesta DB Apr 26 05:27:07 192.168.122.209 [48177.592156] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:27:07 192.168.122.209 [48178.268265] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48178.268265] Maybe that's fine, but it's worth checking the [48178.268265] config - if there is no relations between the [48178.268265] names, then host name confusion attack is possible. Apr 26 05:27:08 192.168.122.209 [48178.415413] [tempesta fw] Configuration processing is completed. Apr 26 05:27:08 192.168.122.209 [48178.472368] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:27:08 192.168.122.209 [48178.501354] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:27:08 192.168.122.209 [48178.529917] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:27:08 192.168.122.209 [48178.575326] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:27:08 192.168.122.209 [48178.576529] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:27:08 192.168.122.209 [48178.623305] [tempesta fw] Tempesta FW is ready Apr 26 05:27:08 192.168.122.209 [48178.770624] [tempesta fw] Warning: Parser error: state=Resp_HdrAgeV input(-8)=0x69('K [48178.770624] Age: invalid [48178.770624] Content-Length: 0 [48178.770624] [48178.770624] ') data_len=52 off=22 Apr 26 05:27:08 192.168.122.209 [48178.772294] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 05:27:08 192.168.122.209 [48179.217099] [tdb] Close table 'client0.tdb' Apr 26 05:27:08 192.168.122.209 [48179.411973] [tdb] Close table 'sessions0.tdb' Apr 26 05:27:09 192.168.122.209 [48179.664635] [tdb] Close table 'filter0.tdb' Apr 26 05:27:09 192.168.122.209 [48179.665091] [tempesta fw] modules are stopped Apr 26 05:27:09 192.168.122.209 [48179.863832] [tempesta fw] exiting... Apr 26 05:27:09 192.168.122.209 [48180.014295] [tdb] Shutdown Tempesta DB Apr 26 05:27:09 192.168.122.209 [48180.252780] End test: t_malformed.test_h2_malformed_headers.H2MalformedResponsesTest.test_age Apr 26 05:27:09 192.168.122.209 [48180.272322] Start test: t_malformed.test_h2_malformed_headers.H2MalformedResponsesTest.test_cache_control1 Apr 26 05:27:11 192.168.122.209 [48181.412409] [tdb] Start Tempesta DB Apr 26 05:27:11 192.168.122.209 [48181.565989] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:27:11 192.168.122.209 [48182.244427] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48182.244427] Maybe that's fine, but it's worth checking the [48182.244427] config - if there is no relations between the [48182.244427] names, then host name confusion attack is possible. Apr 26 05:27:12 192.168.122.209 [48182.458767] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:27:12 192.168.122.209 [48182.494335] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:27:12 192.168.122.209 [48182.529332] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:27:12 192.168.122.209 [48182.599399] [tempesta fw] Tempesta FW is ready Apr 26 05:27:12 192.168.122.209 [48182.739753] net_ratelimit: 3 callbacks suppressed Apr 26 05:27:12 192.168.122.209 [48182.739757] [tempesta fw] Warning: Parser error: state=Resp_HdrCache_CtrlV input(-8)=0x6e('ontrol: not a token [48182.739757] Content-Length: 0 [48182.739757] [48182.739757] ') data_len=66 off=32 Apr 26 05:27:12 192.168.122.209 [48182.742883] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 05:27:12 192.168.122.209 [48183.180719] [tdb] Close table 'client0.tdb' Apr 26 05:27:12 192.168.122.209 [48183.377722] [tdb] Close table 'sessions0.tdb' Apr 26 05:27:13 192.168.122.209 [48183.626889] [tdb] Close table 'filter0.tdb' Apr 26 05:27:13 192.168.122.209 [48183.627679] [tempesta fw] modules are stopped Apr 26 05:27:13 192.168.122.209 [48183.869503] [tempesta fw] exiting... Apr 26 05:27:13 192.168.122.209 [48184.000532] [tdb] Shutdown Tempesta DB Apr 26 05:27:13 192.168.122.209 [48184.222659] End test: t_malformed.test_h2_malformed_headers.H2MalformedResponsesTest.test_cache_control1 Apr 26 05:27:13 192.168.122.209 [48184.239147] Start test: t_malformed.test_h2_malformed_headers.H2MalformedResponsesTest.test_cache_control2 Apr 26 05:27:14 192.168.122.209 [48185.304618] [tdb] Start Tempesta DB Apr 26 05:27:15 192.168.122.209 [48185.452696] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:27:15 192.168.122.209 [48186.132828] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48186.132828] Maybe that's fine, but it's worth checking the [48186.132828] config - if there is no relations between the [48186.132828] names, then host name confusion attack is possible. Apr 26 05:27:15 192.168.122.209 [48186.283505] [tempesta fw] Configuration processing is completed. Apr 26 05:27:15 192.168.122.209 [48186.335796] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:27:15 192.168.122.209 [48186.366358] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:27:15 192.168.122.209 [48186.394535] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:27:16 192.168.122.209 [48186.439456] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:27:16 192.168.122.209 [48186.440667] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:27:16 192.168.122.209 [48186.483437] [tempesta fw] Tempesta FW is ready Apr 26 05:27:16 192.168.122.209 [48186.629015] [tempesta fw] Warning: Parser error: state=Resp_HdrCache_CtrlV input(-8)=0x6d('ontrol: max-age=text [48186.629015] Content-Length: 0 [48186.629015] [48186.629015] ') data_len=67 off=32 Apr 26 05:27:16 192.168.122.209 [48186.633265] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 05:27:16 192.168.122.209 [48187.062514] [tdb] Close table 'client0.tdb' Apr 26 05:27:16 192.168.122.209 [48187.261685] [tdb] Close table 'sessions0.tdb' Apr 26 05:27:17 192.168.122.209 [48187.501999] [tdb] Close table 'filter0.tdb' Apr 26 05:27:17 192.168.122.209 [48187.726801] [tempesta fw] exiting... Apr 26 05:27:17 192.168.122.209 [48187.849524] [tdb] Shutdown Tempesta DB Apr 26 05:27:17 192.168.122.209 [48188.061784] End test: t_malformed.test_h2_malformed_headers.H2MalformedResponsesTest.test_cache_control2 Apr 26 05:27:17 192.168.122.209 [48188.080683] Start test: t_malformed.test_h2_malformed_headers.H2MalformedResponsesTest.test_missing_name Apr 26 05:27:18 192.168.122.209 [48189.174447] [tdb] Start Tempesta DB Apr 26 05:27:18 192.168.122.209 [48189.315228] net_ratelimit: 1 callbacks suppressed Apr 26 05:27:18 192.168.122.209 [48189.315230] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:27:19 192.168.122.209 [48189.968031] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48189.968031] Maybe that's fine, but it's worth checking the [48189.968031] config - if there is no relations between the [48189.968031] names, then host name confusion attack is possible. Apr 26 05:27:19 192.168.122.209 [48190.123673] [tempesta fw] Configuration processing is completed. Apr 26 05:27:19 192.168.122.209 [48190.177516] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:27:19 192.168.122.209 [48190.208247] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:27:19 192.168.122.209 [48190.238157] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:27:19 192.168.122.209 [48190.291481] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:27:19 192.168.122.209 [48190.292571] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:27:19 192.168.122.209 [48190.347436] [tempesta fw] Tempesta FW is ready Apr 26 05:27:20 192.168.122.209 [48190.482515] [tempesta fw] Warning: Parser error: state=RGen_HdrOtherN input(-8)=0x3a('200 OK [48190.482515] : invalid header [48190.482515] Content-Length: 0 [48190.482515] [48190.482515] ') data_len=56 off=17 Apr 26 05:27:20 192.168.122.209 [48190.484263] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 05:27:20 192.168.122.209 [48190.877770] [tdb] Close table 'client0.tdb' Apr 26 05:27:20 192.168.122.209 [48191.062970] [tdb] Close table 'sessions0.tdb' Apr 26 05:27:20 192.168.122.209 [48191.326585] [tdb] Close table 'filter0.tdb' Apr 26 05:27:20 192.168.122.209 [48191.327031] [tempesta fw] modules are stopped Apr 26 05:27:21 192.168.122.209 [48191.496028] [tempesta fw] exiting... Apr 26 05:27:21 192.168.122.209 [48191.646479] [tdb] Shutdown Tempesta DB Apr 26 05:27:21 192.168.122.209 [48191.856332] End test: t_malformed.test_h2_malformed_headers.H2MalformedResponsesTest.test_missing_name Apr 26 05:27:21 192.168.122.209 [48191.876688] Start test: t_malformed.test_malformed_crlfs.MalformedCrlfTest.test_02_no_crlf_pipeline Apr 26 05:27:22 192.168.122.209 [48192.900278] [tdb] Start Tempesta DB Apr 26 05:27:22 192.168.122.209 [48193.045048] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:27:23 192.168.122.209 [48193.623677] [tempesta fw] Configuration processing is completed. Apr 26 05:27:23 192.168.122.209 [48193.684308] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:27:23 192.168.122.209 [48193.715819] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:27:23 192.168.122.209 [48193.746316] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:27:23 192.168.122.209 [48193.811494] [tempesta fw] Tempesta FW is ready Apr 26 05:27:23 192.168.122.209 [48194.364933] [tdb] Close table 'client0.tdb' Apr 26 05:27:24 192.168.122.209 [48194.555340] [tdb] Close table 'sessions0.tdb' Apr 26 05:27:24 192.168.122.209 [48194.809824] [tdb] Close table 'filter0.tdb' Apr 26 05:27:24 192.168.122.209 [48194.810267] net_ratelimit: 1 callbacks suppressed Apr 26 05:27:24 192.168.122.209 [48194.810269] [tempesta fw] modules are stopped Apr 26 05:27:24 192.168.122.209 [48194.972461] [tempesta fw] exiting... Apr 26 05:27:24 192.168.122.209 [48195.085775] [tdb] Shutdown Tempesta DB Apr 26 05:27:24 192.168.122.209 [48195.274316] End test: t_malformed.test_malformed_crlfs.MalformedCrlfTest.test_02_no_crlf_pipeline Apr 26 05:27:24 192.168.122.209 [48195.285778] Start test: t_malformed.test_malformed_crlfs.MalformedCrlfTest.test_03_single_crlf Apr 26 05:27:25 192.168.122.209 [48196.331725] [tdb] Start Tempesta DB Apr 26 05:27:26 192.168.122.209 [48196.479335] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:27:26 192.168.122.209 [48197.071680] [tempesta fw] Configuration processing is completed. Apr 26 05:27:26 192.168.122.209 [48197.124180] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:27:26 192.168.122.209 [48197.154636] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:27:26 192.168.122.209 [48197.184660] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:27:26 192.168.122.209 [48197.219580] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:27:26 192.168.122.209 [48197.267562] [tempesta fw] Tempesta FW is ready Apr 26 05:27:27 192.168.122.209 [48197.837643] [tdb] Close table 'client0.tdb' Apr 26 05:27:27 192.168.122.209 [48198.023196] [tdb] Close table 'sessions0.tdb' Apr 26 05:27:27 192.168.122.209 [48198.264262] [tdb] Close table 'filter0.tdb' Apr 26 05:27:27 192.168.122.209 [48198.264701] [tempesta fw] modules are stopped Apr 26 05:27:28 192.168.122.209 [48198.461171] [tempesta fw] exiting... Apr 26 05:27:28 192.168.122.209 [48198.603602] [tdb] Shutdown Tempesta DB Apr 26 05:27:28 192.168.122.209 [48198.838764] End test: t_malformed.test_malformed_crlfs.MalformedCrlfTest.test_03_single_crlf Apr 26 05:27:28 192.168.122.209 [48198.856666] Start test: t_malformed.test_malformed_crlfs.MalformedCrlfTest.test_04_single_crlf_pipeline Apr 26 05:27:29 192.168.122.209 [48199.955485] [tdb] Start Tempesta DB Apr 26 05:27:29 192.168.122.209 [48200.106091] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:27:30 192.168.122.209 [48200.715696] [tempesta fw] Configuration processing is completed. Apr 26 05:27:30 192.168.122.209 [48200.767227] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:27:30 192.168.122.209 [48200.797447] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:27:30 192.168.122.209 [48200.824332] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:27:30 192.168.122.209 [48200.863629] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:27:30 192.168.122.209 [48200.907606] [tempesta fw] Tempesta FW is ready Apr 26 05:27:31 192.168.122.209 [48201.453379] [tdb] Close table 'client0.tdb' Apr 26 05:27:31 192.168.122.209 [48201.640887] [tdb] Close table 'sessions0.tdb' Apr 26 05:27:31 192.168.122.209 [48201.875164] [tdb] Close table 'filter0.tdb' Apr 26 05:27:31 192.168.122.209 [48201.875653] [tempesta fw] modules are stopped Apr 26 05:27:31 192.168.122.209 [48202.062611] [tempesta fw] exiting... Apr 26 05:27:31 192.168.122.209 [48202.216153] [tdb] Shutdown Tempesta DB Apr 26 05:27:32 192.168.122.209 [48202.482756] End test: t_malformed.test_malformed_crlfs.MalformedCrlfTest.test_04_single_crlf_pipeline Apr 26 05:27:32 192.168.122.209 [48202.494646] Start test: t_malformed.test_malformed_crlfs.MalformedCrlfTest.test_05_single_lf Apr 26 05:27:33 192.168.122.209 [48203.557298] [tdb] Start Tempesta DB Apr 26 05:27:33 192.168.122.209 [48203.683239] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:27:33 192.168.122.209 [48204.255789] [tempesta fw] Configuration processing is completed. Apr 26 05:27:33 192.168.122.209 [48204.310330] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:27:33 192.168.122.209 [48204.340456] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:27:33 192.168.122.209 [48204.368144] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:27:33 192.168.122.209 [48204.407642] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:27:34 192.168.122.209 [48204.459568] [tempesta fw] Tempesta FW is ready Apr 26 05:27:34 192.168.122.209 [48205.048510] [tdb] Close table 'client0.tdb' Apr 26 05:27:34 192.168.122.209 [48205.241376] [tdb] Close table 'sessions0.tdb' Apr 26 05:27:35 192.168.122.209 [48205.457194] [tdb] Close table 'filter0.tdb' Apr 26 05:27:35 192.168.122.209 [48205.457647] [tempesta fw] modules are stopped Apr 26 05:27:35 192.168.122.209 [48205.654625] [tempesta fw] exiting... Apr 26 05:27:35 192.168.122.209 [48205.787019] [tdb] Shutdown Tempesta DB Apr 26 05:27:35 192.168.122.209 [48205.993698] End test: t_malformed.test_malformed_crlfs.MalformedCrlfTest.test_05_single_lf Apr 26 05:27:35 192.168.122.209 [48206.018212] Start test: t_malformed.test_malformed_crlfs.MalformedCrlfTest.test_06_single_lf_pipeline Apr 26 05:27:36 192.168.122.209 [48206.985879] [tdb] Start Tempesta DB Apr 26 05:27:36 192.168.122.209 [48207.119567] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:27:37 192.168.122.209 [48207.663817] [tempesta fw] Configuration processing is completed. Apr 26 05:27:37 192.168.122.209 [48207.714116] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:27:37 192.168.122.209 [48207.741732] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:27:37 192.168.122.209 [48207.768288] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:27:37 192.168.122.209 [48207.811747] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:27:37 192.168.122.209 [48207.855690] [tempesta fw] Tempesta FW is ready Apr 26 05:27:37 192.168.122.209 [48208.404988] [tdb] Close table 'client0.tdb' Apr 26 05:27:38 192.168.122.209 [48208.570971] [tdb] Close table 'sessions0.tdb' Apr 26 05:27:38 192.168.122.209 [48208.821415] [tdb] Close table 'filter0.tdb' Apr 26 05:27:38 192.168.122.209 [48208.821850] [tempesta fw] modules are stopped Apr 26 05:27:39 192.168.122.209 [48210.099981] [tempesta fw] exiting... Apr 26 05:27:40 192.168.122.209 [48210.687861] [tdb] Shutdown Tempesta DB Apr 26 05:27:40 192.168.122.209 [48210.896689] End test: t_malformed.test_malformed_crlfs.MalformedCrlfTest.test_06_single_lf_pipeline Apr 26 05:27:40 192.168.122.209 [48210.920598] Start test: t_malformed.test_malformed_crlfs.MalformedCrlfTest.test_07_double_crlf Apr 26 05:27:41 192.168.122.209 [48212.086635] [tdb] Start Tempesta DB Apr 26 05:27:41 192.168.122.209 [48212.296029] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:27:43 192.168.122.209 [48213.680034] [tempesta fw] Configuration processing is completed. Apr 26 05:27:43 192.168.122.209 [48213.976596] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:27:43 192.168.122.209 [48214.008378] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:27:43 192.168.122.209 [48214.036652] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:27:43 192.168.122.209 [48214.387678] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:27:44 192.168.122.209 [48214.847658] [tempesta fw] Tempesta FW is ready Apr 26 05:27:44 192.168.122.209 [48214.961787] [tempesta fw] Warning: Parser error: state=Req_MethodUnknown input(-2)=0xd(' [48214.961787] [48214.961787] GET / HTTP/1.1 [48214.961787] Host: localhost [48214.961787] [48214.961787] ') data_len=39 off=2 Apr 26 05:27:45 192.168.122.209 [48215.443463] [tdb] Close table 'client0.tdb' Apr 26 05:27:45 192.168.122.209 [48215.634329] [tdb] Close table 'sessions0.tdb' Apr 26 05:27:45 192.168.122.209 [48215.892832] [tdb] Close table 'filter0.tdb' Apr 26 05:27:45 192.168.122.209 [48215.893308] [tempesta fw] modules are stopped Apr 26 05:27:45 192.168.122.209 [48216.063478] [tempesta fw] exiting... Apr 26 05:27:45 192.168.122.209 [48216.179580] [tdb] Shutdown Tempesta DB Apr 26 05:27:45 192.168.122.209 [48216.401295] End test: t_malformed.test_malformed_crlfs.MalformedCrlfTest.test_07_double_crlf Apr 26 05:27:46 192.168.122.209 [48216.419947] Start test: t_malformed.test_malformed_crlfs.MalformedCrlfTest.test_08_double_crlf_pipeline Apr 26 05:27:47 192.168.122.209 [48217.435164] [tdb] Start Tempesta DB Apr 26 05:27:47 192.168.122.209 [48217.566143] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:27:47 192.168.122.209 [48218.139925] [tempesta fw] Configuration processing is completed. Apr 26 05:27:47 192.168.122.209 [48218.193238] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:27:47 192.168.122.209 [48218.221739] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:27:47 192.168.122.209 [48218.248564] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:27:47 192.168.122.209 [48218.291883] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:27:47 192.168.122.209 [48218.339927] [tempesta fw] Tempesta FW is ready Apr 26 05:27:48 192.168.122.209 [48218.460391] [tempesta fw] Warning: Parser error: state=Req_MethodUnknown input(-2)=0xd(' [48218.460391] [48218.460391] GET /bbb HTTP/1.1 [48218.460391] Host: localhost [48218.460391] [48218.460391] ') data_len=42 off=2 Apr 26 05:27:48 192.168.122.209 [48218.897371] [tdb] Close table 'client0.tdb' Apr 26 05:27:48 192.168.122.209 [48219.086522] [tdb] Close table 'sessions0.tdb' Apr 26 05:27:48 192.168.122.209 [48219.317147] [tdb] Close table 'filter0.tdb' Apr 26 05:27:48 192.168.122.209 [48219.317585] [tempesta fw] modules are stopped Apr 26 05:27:49 192.168.122.209 [48219.468546] [tempesta fw] exiting... Apr 26 05:27:49 192.168.122.209 [48219.613300] [tdb] Shutdown Tempesta DB Apr 26 05:27:49 192.168.122.209 [48219.830690] End test: t_malformed.test_malformed_crlfs.MalformedCrlfTest.test_08_double_crlf_pipeline Apr 26 05:27:49 192.168.122.209 [48219.843041] Start test: t_malformed.test_malformed_crlfs.MalformedCrlfTest.test_09_double_lf Apr 26 05:27:50 192.168.122.209 [48220.882199] [tdb] Start Tempesta DB Apr 26 05:27:50 192.168.122.209 [48221.046714] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:27:51 192.168.122.209 [48221.639978] [tempesta fw] Configuration processing is completed. Apr 26 05:27:51 192.168.122.209 [48221.693201] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:27:51 192.168.122.209 [48221.734698] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:27:51 192.168.122.209 [48221.764732] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:27:51 192.168.122.209 [48221.807929] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:27:51 192.168.122.209 [48221.863884] [tempesta fw] Tempesta FW is ready Apr 26 05:27:51 192.168.122.209 [48221.984533] [tempesta fw] Warning: Parser error: state=Req_MethodUnknown input(-1)=0xa(' [48221.984533] [48221.984533] GET / HTTP/1.1 [48221.984533] Host: localhost [48221.984533] [48221.984533] ') data_len=37 off=1 Apr 26 05:27:51 192.168.122.209 [48222.411159] [tdb] Close table 'client0.tdb' Apr 26 05:27:52 192.168.122.209 [48222.604135] [tdb] Close table 'sessions0.tdb' Apr 26 05:27:52 192.168.122.209 [48222.835563] [tdb] Close table 'filter0.tdb' Apr 26 05:27:52 192.168.122.209 [48222.836027] [tempesta fw] modules are stopped Apr 26 05:27:52 192.168.122.209 [48223.016802] [tempesta fw] exiting... Apr 26 05:27:52 192.168.122.209 [48223.137221] [tdb] Shutdown Tempesta DB Apr 26 05:27:52 192.168.122.209 [48223.362058] End test: t_malformed.test_malformed_crlfs.MalformedCrlfTest.test_09_double_lf Apr 26 05:27:52 192.168.122.209 [48223.383824] Start test: t_malformed.test_malformed_crlfs.MalformedCrlfTest.test_10_double_lf_pipeline Apr 26 05:27:54 192.168.122.209 [48224.472548] [tdb] Start Tempesta DB Apr 26 05:27:54 192.168.122.209 [48224.605518] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:27:54 192.168.122.209 [48225.164052] [tempesta fw] Configuration processing is completed. Apr 26 05:27:54 192.168.122.209 [48225.218319] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:27:54 192.168.122.209 [48225.249869] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:27:54 192.168.122.209 [48225.279471] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:27:54 192.168.122.209 [48225.319950] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:27:54 192.168.122.209 [48225.359952] [tempesta fw] Tempesta FW is ready Apr 26 05:27:55 192.168.122.209 [48225.497342] [tempesta fw] Warning: Parser error: state=Req_MethodUnknown input(-1)=0xa(' [48225.497342] [48225.497342] GET /bbb HTTP/1.1 [48225.497342] Host: localhost [48225.497342] [48225.497342] ') data_len=40 off=1 Apr 26 05:27:55 192.168.122.209 [48225.936631] [tdb] Close table 'client0.tdb' Apr 26 05:27:55 192.168.122.209 [48226.141464] [tdb] Close table 'sessions0.tdb' Apr 26 05:27:55 192.168.122.209 [48226.378443] [tdb] Close table 'filter0.tdb' Apr 26 05:27:55 192.168.122.209 [48226.378884] [tempesta fw] modules are stopped Apr 26 05:27:56 192.168.122.209 [48226.534644] [tempesta fw] exiting... Apr 26 05:27:56 192.168.122.209 [48226.657624] [tdb] Shutdown Tempesta DB Apr 26 05:27:56 192.168.122.209 [48226.874523] End test: t_malformed.test_malformed_crlfs.MalformedCrlfTest.test_10_double_lf_pipeline Apr 26 05:27:56 192.168.122.209 [48226.887843] Start test: t_malformed.test_malformed_headers.EtagAlphabetTest.test_etag_with_x21 Apr 26 05:27:57 192.168.122.209 [48227.996022] [tdb] Start Tempesta DB Apr 26 05:27:57 192.168.122.209 [48228.150400] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:27:58 192.168.122.209 [48228.804896] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48228.804896] Maybe that's fine, but it's worth checking the [48228.804896] config - if there is no relations between the [48228.804896] names, then host name confusion attack is possible. Apr 26 05:27:58 192.168.122.209 [48228.956048] [tempesta fw] Configuration processing is completed. Apr 26 05:27:58 192.168.122.209 [48229.010193] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:27:58 192.168.122.209 [48229.038431] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:27:58 192.168.122.209 [48229.065405] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:27:58 192.168.122.209 [48229.144086] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:27:58 192.168.122.209 [48229.145878] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:27:58 192.168.122.209 [48229.188261] [tempesta fw] Tempesta FW is ready Apr 26 05:27:59 192.168.122.209 [48229.788912] [tdb] Close table 'client0.tdb' Apr 26 05:27:59 192.168.122.209 [48229.981376] [tdb] Close table 'sessions0.tdb' Apr 26 05:27:59 192.168.122.209 [48230.216613] [tdb] Close table 'filter0.tdb' Apr 26 05:27:59 192.168.122.209 [48230.217067] [tempesta fw] modules are stopped Apr 26 05:28:00 192.168.122.209 [48230.423134] [tempesta fw] exiting... Apr 26 05:28:00 192.168.122.209 [48230.536871] [tdb] Shutdown Tempesta DB Apr 26 05:28:00 192.168.122.209 [48230.729040] End test: t_malformed.test_malformed_headers.EtagAlphabetTest.test_etag_with_x21 Apr 26 05:28:00 192.168.122.209 [48230.738868] Start test: t_malformed.test_malformed_headers.EtagAlphabetTest.test_etag_with_x23 Apr 26 05:28:01 192.168.122.209 [48231.812414] [tdb] Start Tempesta DB Apr 26 05:28:01 192.168.122.209 [48231.969920] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:28:02 192.168.122.209 [48232.633322] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48232.633322] Maybe that's fine, but it's worth checking the [48232.633322] config - if there is no relations between the [48232.633322] names, then host name confusion attack is possible. Apr 26 05:28:02 192.168.122.209 [48232.804043] [tempesta fw] Configuration processing is completed. Apr 26 05:28:02 192.168.122.209 [48232.863788] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:28:02 192.168.122.209 [48232.893776] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:28:02 192.168.122.209 [48232.920729] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:28:02 192.168.122.209 [48232.972072] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:28:02 192.168.122.209 [48233.012010] [tempesta fw] Tempesta FW is ready Apr 26 05:28:03 192.168.122.209 [48233.575523] [tdb] Close table 'client0.tdb' Apr 26 05:28:03 192.168.122.209 [48233.759206] [tdb] Close table 'sessions0.tdb' Apr 26 05:28:03 192.168.122.209 [48233.993583] [tdb] Close table 'filter0.tdb' Apr 26 05:28:03 192.168.122.209 [48233.994104] net_ratelimit: 1 callbacks suppressed Apr 26 05:28:03 192.168.122.209 [48233.994106] [tempesta fw] modules are stopped Apr 26 05:28:03 192.168.122.209 [48234.211417] [tempesta fw] exiting... Apr 26 05:28:03 192.168.122.209 [48234.352383] [tdb] Shutdown Tempesta DB Apr 26 05:28:04 192.168.122.209 [48234.595025] End test: t_malformed.test_malformed_headers.EtagAlphabetTest.test_etag_with_x23 Apr 26 05:28:04 192.168.122.209 [48234.616637] Start test: t_malformed.test_malformed_headers.EtagAlphabetTest.test_etag_with_x7f Apr 26 05:28:05 192.168.122.209 [48235.923766] [tdb] Start Tempesta DB Apr 26 05:28:05 192.168.122.209 [48236.090239] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:28:06 192.168.122.209 [48236.881480] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48236.881480] Maybe that's fine, but it's worth checking the [48236.881480] config - if there is no relations between the [48236.881480] names, then host name confusion attack is possible. Apr 26 05:28:06 192.168.122.209 [48237.064111] [tempesta fw] Configuration processing is completed. Apr 26 05:28:06 192.168.122.209 [48237.122562] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:28:06 192.168.122.209 [48237.153676] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:28:06 192.168.122.209 [48237.183432] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:28:06 192.168.122.209 [48237.236145] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:28:06 192.168.122.209 [48237.237968] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:28:06 192.168.122.209 [48237.288074] [tempesta fw] Tempesta FW is ready Apr 26 05:28:07 192.168.122.209 [48237.417461] [tempesta fw] Warning: Parser error: state=Resp_HdrEtagV input(-8)=0x57(' [48237.417461] Etag: W/"0123456789" [48237.417461] [48237.417461] ') data_len=61 off=42 Apr 26 05:28:07 192.168.122.209 [48237.419813] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 05:28:07 192.168.122.209 [48237.847495] [tdb] Close table 'client0.tdb' Apr 26 05:28:07 192.168.122.209 [48238.042295] [tdb] Close table 'sessions0.tdb' Apr 26 05:28:07 192.168.122.209 [48238.300015] [tdb] Close table 'filter0.tdb' Apr 26 05:28:07 192.168.122.209 [48238.300469] [tempesta fw] modules are stopped Apr 26 05:28:08 192.168.122.209 [48238.504006] [tempesta fw] exiting... Apr 26 05:28:08 192.168.122.209 [48238.654344] [tdb] Shutdown Tempesta DB Apr 26 05:28:08 192.168.122.209 [48238.866480] End test: t_malformed.test_malformed_headers.EtagAlphabetTest.test_etag_with_x7f Apr 26 05:28:08 192.168.122.209 [48238.879203] Start test: t_malformed.test_malformed_headers.EtagAlphabetTest.test_etag_with_xf7 Apr 26 05:28:09 192.168.122.209 [48239.988230] [tdb] Start Tempesta DB Apr 26 05:28:09 192.168.122.209 [48240.150249] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:28:10 192.168.122.209 [48240.849086] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48240.849086] Maybe that's fine, but it's worth checking the [48240.849086] config - if there is no relations between the [48240.849086] names, then host name confusion attack is possible. Apr 26 05:28:10 192.168.122.209 [48240.988310] [tempesta fw] Configuration processing is completed. Apr 26 05:28:10 192.168.122.209 [48241.043625] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:28:10 192.168.122.209 [48241.084960] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:28:10 192.168.122.209 [48241.123802] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:28:10 192.168.122.209 [48241.188066] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:28:10 192.168.122.209 [48241.188921] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:28:10 192.168.122.209 [48241.228023] [tempesta fw] Tempesta FW is ready Apr 26 05:28:11 192.168.122.209 [48241.830074] [tdb] Close table 'client0.tdb' Apr 26 05:28:11 192.168.122.209 [48242.017684] [tdb] Close table 'sessions0.tdb' Apr 26 05:28:11 192.168.122.209 [48242.253893] [tdb] Close table 'filter0.tdb' Apr 26 05:28:11 192.168.122.209 [48242.254335] [tempesta fw] modules are stopped Apr 26 05:28:12 192.168.122.209 [48242.453552] [tempesta fw] exiting... Apr 26 05:28:12 192.168.122.209 [48242.589198] [tdb] Shutdown Tempesta DB Apr 26 05:28:12 192.168.122.209 [48242.782636] End test: t_malformed.test_malformed_headers.EtagAlphabetTest.test_etag_with_xf7 Apr 26 05:28:12 192.168.122.209 [48242.794811] Start test: t_malformed.test_malformed_headers.MalformedRequestsTest.test_accept Apr 26 05:28:13 192.168.122.209 [48243.902623] [tdb] Start Tempesta DB Apr 26 05:28:13 192.168.122.209 [48244.070906] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:28:14 192.168.122.209 [48244.697509] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48244.697509] Maybe that's fine, but it's worth checking the [48244.697509] config - if there is no relations between the [48244.697509] names, then host name confusion attack is possible. Apr 26 05:28:14 192.168.122.209 [48244.844222] [tempesta fw] Configuration processing is completed. Apr 26 05:28:14 192.168.122.209 [48244.903120] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:28:14 192.168.122.209 [48244.933476] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:28:14 192.168.122.209 [48244.961592] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:28:14 192.168.122.209 [48245.008187] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:28:14 192.168.122.209 [48245.052177] [tempesta fw] Tempesta FW is ready Apr 26 05:28:14 192.168.122.209 [48245.165377] net_ratelimit: 1 callbacks suppressed Apr 26 05:28:14 192.168.122.209 [48245.165380] [tempesta fw] Warning: Parser error: state=Req_HdrAcceptV input(-8)=0x69('Accept: invalid [48245.165380] [48245.165380] ') data_len=52 off=41 Apr 26 05:28:15 192.168.122.209 [48245.606826] [tdb] Close table 'client0.tdb' Apr 26 05:28:15 192.168.122.209 [48245.836350] [tdb] Close table 'sessions0.tdb' Apr 26 05:28:15 192.168.122.209 [48246.085824] [tdb] Close table 'filter0.tdb' Apr 26 05:28:15 192.168.122.209 [48246.086269] [tempesta fw] modules are stopped Apr 26 05:28:15 192.168.122.209 [48246.286923] [tempesta fw] exiting... Apr 26 05:28:16 192.168.122.209 [48246.426750] [tdb] Shutdown Tempesta DB Apr 26 05:28:16 192.168.122.209 [48246.651191] End test: t_malformed.test_malformed_headers.MalformedRequestsTest.test_accept Apr 26 05:28:16 192.168.122.209 [48246.669657] Start test: t_malformed.test_malformed_headers.MalformedRequestsTest.test_expect_invalid Apr 26 05:28:17 192.168.122.209 [48247.813188] [tdb] Start Tempesta DB Apr 26 05:28:17 192.168.122.209 [48247.958792] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:28:18 192.168.122.209 [48248.665571] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48248.665571] Maybe that's fine, but it's worth checking the [48248.665571] config - if there is no relations between the [48248.665571] names, then host name confusion attack is possible. Apr 26 05:28:18 192.168.122.209 [48248.808322] [tempesta fw] Configuration processing is completed. Apr 26 05:28:18 192.168.122.209 [48248.868428] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:28:18 192.168.122.209 [48248.908440] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:28:18 192.168.122.209 [48248.942873] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:28:18 192.168.122.209 [48248.984208] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:28:18 192.168.122.209 [48248.985327] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:28:18 192.168.122.209 [48249.044158] [tempesta fw] Tempesta FW is ready Apr 26 05:28:18 192.168.122.209 [48249.171886] [tempesta fw] Warning: Parser error: state=Req_HdrExpectV input(-8)=0x69('Expect: invalid [48249.171886] [48249.171886] ') data_len=52 off=41 Apr 26 05:28:19 192.168.122.209 [48249.631781] [tdb] Close table 'client0.tdb' Apr 26 05:28:19 192.168.122.209 [48249.834987] [tdb] Close table 'sessions0.tdb' Apr 26 05:28:19 192.168.122.209 [48250.075178] [tdb] Close table 'filter0.tdb' Apr 26 05:28:19 192.168.122.209 [48250.075629] [tempesta fw] modules are stopped Apr 26 05:28:19 192.168.122.209 [48250.333116] [tempesta fw] exiting... Apr 26 05:28:20 192.168.122.209 [48250.478034] [tdb] Shutdown Tempesta DB Apr 26 05:28:20 192.168.122.209 [48250.724696] End test: t_malformed.test_malformed_headers.MalformedRequestsTest.test_expect_invalid Apr 26 05:28:20 192.168.122.209 [48250.734493] Start test: t_malformed.test_malformed_headers.MalformedRequestsTest.test_host Apr 26 05:28:21 192.168.122.209 [48251.790966] [tdb] Start Tempesta DB Apr 26 05:28:21 192.168.122.209 [48251.951614] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:28:22 192.168.122.209 [48252.657108] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48252.657108] Maybe that's fine, but it's worth checking the [48252.657108] config - if there is no relations between the [48252.657108] names, then host name confusion attack is possible. Apr 26 05:28:22 192.168.122.209 [48252.780395] [tempesta fw] Configuration processing is completed. Apr 26 05:28:22 192.168.122.209 [48252.843526] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:28:22 192.168.122.209 [48252.882888] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:28:22 192.168.122.209 [48252.918250] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:28:22 192.168.122.209 [48252.972344] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:28:22 192.168.122.209 [48252.974074] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:28:22 192.168.122.209 [48253.024262] [tempesta fw] Tempesta FW is ready Apr 26 05:28:22 192.168.122.209 [48253.153588] [tempesta fw] Warning: Parser error: state=Req_HdrHostV input(-8)=0x68(' [48253.153588] Host: http:// [48253.153588] [48253.153588] ') data_len=33 off=22 Apr 26 05:28:23 192.168.122.209 [48253.596497] [tdb] Close table 'client0.tdb' Apr 26 05:28:23 192.168.122.209 [48253.783918] [tdb] Close table 'sessions0.tdb' Apr 26 05:28:23 192.168.122.209 [48254.028686] [tdb] Close table 'filter0.tdb' Apr 26 05:28:23 192.168.122.209 [48254.029129] [tempesta fw] modules are stopped Apr 26 05:28:23 192.168.122.209 [48254.255824] [tempesta fw] exiting... Apr 26 05:28:23 192.168.122.209 [48254.376116] [tdb] Shutdown Tempesta DB Apr 26 05:28:24 192.168.122.209 [48254.585563] End test: t_malformed.test_malformed_headers.MalformedRequestsTest.test_host Apr 26 05:28:24 192.168.122.209 [48254.608563] Start test: t_malformed.test_malformed_headers.MalformedRequestsTest.test_if_none_match Apr 26 05:28:25 192.168.122.209 [48255.758825] [tdb] Start Tempesta DB Apr 26 05:28:25 192.168.122.209 [48255.912670] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:28:26 192.168.122.209 [48256.537663] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48256.537663] Maybe that's fine, but it's worth checking the [48256.537663] config - if there is no relations between the [48256.537663] names, then host name confusion attack is possible. Apr 26 05:28:26 192.168.122.209 [48256.676367] [tempesta fw] Configuration processing is completed. Apr 26 05:28:26 192.168.122.209 [48256.727200] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:28:26 192.168.122.209 [48256.755017] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:28:26 192.168.122.209 [48256.781724] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:28:26 192.168.122.209 [48256.856239] [tempesta fw] Tempesta FW is ready Apr 26 05:28:26 192.168.122.209 [48256.983299] net_ratelimit: 2 callbacks suppressed Apr 26 05:28:26 192.168.122.209 [48256.983309] [tempesta fw] Warning: Parser error: state=Req_HdrIf_None_MatchV input(-8)=0x71('-Match: quotes [48256.983309] [48256.983309] ') data_len=58 off=48 Apr 26 05:28:27 192.168.122.209 [48257.442732] [tdb] Close table 'client0.tdb' Apr 26 05:28:27 192.168.122.209 [48257.631942] [tdb] Close table 'sessions0.tdb' Apr 26 05:28:27 192.168.122.209 [48257.878061] [tdb] Close table 'filter0.tdb' Apr 26 05:28:27 192.168.122.209 [48257.878497] [tempesta fw] modules are stopped Apr 26 05:28:27 192.168.122.209 [48258.114080] [tempesta fw] exiting... Apr 26 05:28:27 192.168.122.209 [48258.234871] [tdb] Shutdown Tempesta DB Apr 26 05:28:28 192.168.122.209 [48258.457206] End test: t_malformed.test_malformed_headers.MalformedRequestsTest.test_if_none_match Apr 26 05:28:28 192.168.122.209 [48258.470325] Start test: t_malformed.test_malformed_headers.MalformedRequestsTest.test_missing_name Apr 26 05:28:29 192.168.122.209 [48259.512244] [tdb] Start Tempesta DB Apr 26 05:28:29 192.168.122.209 [48259.669088] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:28:29 192.168.122.209 [48260.401670] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48260.401670] Maybe that's fine, but it's worth checking the [48260.401670] config - if there is no relations between the [48260.401670] names, then host name confusion attack is possible. Apr 26 05:28:30 192.168.122.209 [48260.536431] [tempesta fw] Configuration processing is completed. Apr 26 05:28:30 192.168.122.209 [48260.590010] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:28:30 192.168.122.209 [48260.618133] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:28:30 192.168.122.209 [48260.645022] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:28:30 192.168.122.209 [48260.688359] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:28:30 192.168.122.209 [48260.689631] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:28:30 192.168.122.209 [48260.728390] [tempesta fw] Tempesta FW is ready Apr 26 05:28:30 192.168.122.209 [48260.860038] [tempesta fw] Warning: Parser error: state=RGen_HdrOtherN input(-8)=0x3a('alhost [48260.860038] : invalid header [48260.860038] [48260.860038] ') data_len=53 off=33 Apr 26 05:28:30 192.168.122.209 [48261.340805] [tdb] Close table 'client0.tdb' Apr 26 05:28:31 192.168.122.209 [48261.538531] [tdb] Close table 'sessions0.tdb' Apr 26 05:28:31 192.168.122.209 [48261.787406] [tdb] Close table 'filter0.tdb' Apr 26 05:28:31 192.168.122.209 [48261.787815] [tempesta fw] modules are stopped Apr 26 05:28:31 192.168.122.209 [48261.966284] [tempesta fw] exiting... Apr 26 05:28:31 192.168.122.209 [48262.101757] [tdb] Shutdown Tempesta DB Apr 26 05:28:31 192.168.122.209 [48262.314312] End test: t_malformed.test_malformed_headers.MalformedRequestsTest.test_missing_name Apr 26 05:28:31 192.168.122.209 [48262.326735] Start test: t_malformed.test_malformed_headers.MalformedRequestsTest.test_transfer_encoding Apr 26 05:28:33 192.168.122.209 [48263.416380] [tdb] Start Tempesta DB Apr 26 05:28:33 192.168.122.209 [48263.565238] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:28:33 192.168.122.209 [48264.269703] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48264.269703] Maybe that's fine, but it's worth checking the [48264.269703] config - if there is no relations between the [48264.269703] names, then host name confusion attack is possible. Apr 26 05:28:34 192.168.122.209 [48264.412478] [tempesta fw] Configuration processing is completed. Apr 26 05:28:34 192.168.122.209 [48264.464102] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:28:34 192.168.122.209 [48264.494618] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:28:34 192.168.122.209 [48264.522488] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:28:34 192.168.122.209 [48264.568435] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:28:34 192.168.122.209 [48264.570156] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:28:34 192.168.122.209 [48264.608430] [tempesta fw] Tempesta FW is ready Apr 26 05:28:34 192.168.122.209 [48264.759614] [tempesta fw] Warning: Parser error: state=RGen_BodyInit input(-8)=0xa('token [48264.759614] [48264.759614] ') data_len=64 off=63 Apr 26 05:28:34 192.168.122.209 [48265.172359] [tdb] Close table 'client0.tdb' Apr 26 05:28:34 192.168.122.209 [48265.361509] [tdb] Close table 'sessions0.tdb' Apr 26 05:28:35 192.168.122.209 [48265.579013] [tdb] Close table 'filter0.tdb' Apr 26 05:28:35 192.168.122.209 [48265.579453] [tempesta fw] modules are stopped Apr 26 05:28:35 192.168.122.209 [48265.793472] [tempesta fw] exiting... Apr 26 05:28:35 192.168.122.209 [48265.937074] [tdb] Shutdown Tempesta DB Apr 26 05:28:35 192.168.122.209 [48266.171071] End test: t_malformed.test_malformed_headers.MalformedRequestsTest.test_transfer_encoding Apr 26 05:28:35 192.168.122.209 [48266.184539] Start test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_accept_charset Apr 26 05:28:36 192.168.122.209 [48267.352261] [tdb] Start Tempesta DB Apr 26 05:28:37 192.168.122.209 [48267.496107] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:28:37 192.168.122.209 [48268.181786] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48268.181786] Maybe that's fine, but it's worth checking the [48268.181786] config - if there is no relations between the [48268.181786] names, then host name confusion attack is possible. Apr 26 05:28:37 192.168.122.209 [48268.344436] [tempesta fw] Configuration processing is completed. Apr 26 05:28:37 192.168.122.209 [48268.402770] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:28:38 192.168.122.209 [48268.430567] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:28:38 192.168.122.209 [48268.457605] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:28:38 192.168.122.209 [48268.548457] [tempesta fw] Tempesta FW is ready Apr 26 05:28:38 192.168.122.209 [48269.139283] [tdb] Close table 'client0.tdb' Apr 26 05:28:38 192.168.122.209 [48269.337392] [tdb] Close table 'sessions0.tdb' Apr 26 05:28:39 192.168.122.209 [48269.585294] [tdb] Close table 'filter0.tdb' Apr 26 05:28:39 192.168.122.209 [48269.585751] net_ratelimit: 2 callbacks suppressed Apr 26 05:28:39 192.168.122.209 [48269.585752] [tempesta fw] modules are stopped Apr 26 05:28:39 192.168.122.209 [48269.773830] [tempesta fw] exiting... Apr 26 05:28:39 192.168.122.209 [48269.894549] [tdb] Shutdown Tempesta DB Apr 26 05:28:39 192.168.122.209 [48270.119632] End test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_accept_charset Apr 26 05:28:39 192.168.122.209 [48270.128200] Start test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_accept_encoding Apr 26 05:28:40 192.168.122.209 [48271.047131] [tdb] Start Tempesta DB Apr 26 05:28:40 192.168.122.209 [48271.166840] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:28:41 192.168.122.209 [48271.797807] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48271.797807] Maybe that's fine, but it's worth checking the [48271.797807] config - if there is no relations between the [48271.797807] names, then host name confusion attack is possible. Apr 26 05:28:41 192.168.122.209 [48271.948515] [tempesta fw] Configuration processing is completed. Apr 26 05:28:41 192.168.122.209 [48271.999831] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:28:41 192.168.122.209 [48272.027899] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:28:41 192.168.122.209 [48272.055385] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:28:41 192.168.122.209 [48272.128549] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:28:41 192.168.122.209 [48272.130380] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:28:41 192.168.122.209 [48272.168515] [tempesta fw] Tempesta FW is ready Apr 26 05:28:42 192.168.122.209 [48272.715007] [tdb] Close table 'client0.tdb' Apr 26 05:28:42 192.168.122.209 [48272.900693] [tdb] Close table 'sessions0.tdb' Apr 26 05:28:42 192.168.122.209 [48273.123326] [tdb] Close table 'filter0.tdb' Apr 26 05:28:42 192.168.122.209 [48273.123767] [tempesta fw] modules are stopped Apr 26 05:28:42 192.168.122.209 [48273.384591] [tempesta fw] exiting... Apr 26 05:28:43 192.168.122.209 [48273.482190] [tdb] Shutdown Tempesta DB Apr 26 05:28:43 192.168.122.209 [48273.685963] End test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_accept_encoding Apr 26 05:28:43 192.168.122.209 [48273.699500] Start test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_accept_language Apr 26 05:28:44 192.168.122.209 [48274.756172] [tdb] Start Tempesta DB Apr 26 05:28:44 192.168.122.209 [48274.896143] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:28:45 192.168.122.209 [48275.525346] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48275.525346] Maybe that's fine, but it's worth checking the [48275.525346] config - if there is no relations between the [48275.525346] names, then host name confusion attack is possible. Apr 26 05:28:45 192.168.122.209 [48275.668615] [tempesta fw] Configuration processing is completed. Apr 26 05:28:45 192.168.122.209 [48275.719139] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:28:45 192.168.122.209 [48275.747690] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:28:45 192.168.122.209 [48275.774338] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:28:45 192.168.122.209 [48275.816568] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:28:45 192.168.122.209 [48275.817952] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:28:45 192.168.122.209 [48275.856564] [tempesta fw] Tempesta FW is ready Apr 26 05:28:46 192.168.122.209 [48276.433536] [tdb] Close table 'client0.tdb' Apr 26 05:28:46 192.168.122.209 [48276.633181] [tdb] Close table 'sessions0.tdb' Apr 26 05:28:46 192.168.122.209 [48276.856807] [tdb] Close table 'filter0.tdb' Apr 26 05:28:46 192.168.122.209 [48276.857248] [tempesta fw] modules are stopped Apr 26 05:28:46 192.168.122.209 [48277.047742] [tempesta fw] exiting... Apr 26 05:28:46 192.168.122.209 [48277.183450] [tdb] Shutdown Tempesta DB Apr 26 05:28:46 192.168.122.209 [48277.395803] End test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_accept_language Apr 26 05:28:46 192.168.122.209 [48277.407943] Start test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_content_encoding Apr 26 05:28:48 192.168.122.209 [48278.481751] [tdb] Start Tempesta DB Apr 26 05:28:48 192.168.122.209 [48278.639690] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:28:48 192.168.122.209 [48279.341631] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48279.341631] Maybe that's fine, but it's worth checking the [48279.341631] config - if there is no relations between the [48279.341631] names, then host name confusion attack is possible. Apr 26 05:28:49 192.168.122.209 [48279.484613] [tempesta fw] Configuration processing is completed. Apr 26 05:28:49 192.168.122.209 [48279.537697] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:28:49 192.168.122.209 [48279.567242] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:28:49 192.168.122.209 [48279.593923] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:28:49 192.168.122.209 [48279.648659] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:28:49 192.168.122.209 [48279.696544] [tempesta fw] Tempesta FW is ready Apr 26 05:28:49 192.168.122.209 [48280.290825] [tdb] Close table 'client0.tdb' Apr 26 05:28:50 192.168.122.209 [48280.486971] [tdb] Close table 'sessions0.tdb' Apr 26 05:28:50 192.168.122.209 [48280.729484] [tdb] Close table 'filter0.tdb' Apr 26 05:28:50 192.168.122.209 [48280.729933] net_ratelimit: 1 callbacks suppressed Apr 26 05:28:50 192.168.122.209 [48280.729934] [tempesta fw] modules are stopped Apr 26 05:28:50 192.168.122.209 [48280.949096] [tempesta fw] exiting... Apr 26 05:28:50 192.168.122.209 [48281.088967] [tdb] Shutdown Tempesta DB Apr 26 05:28:50 192.168.122.209 [48281.297532] End test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_content_encoding Apr 26 05:28:50 192.168.122.209 [48281.311554] Start test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_content_language Apr 26 05:28:51 192.168.122.209 [48282.385124] [tdb] Start Tempesta DB Apr 26 05:28:52 192.168.122.209 [48282.524971] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:28:52 192.168.122.209 [48283.245948] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48283.245948] Maybe that's fine, but it's worth checking the [48283.245948] config - if there is no relations between the [48283.245948] names, then host name confusion attack is possible. Apr 26 05:28:52 192.168.122.209 [48283.396728] [tempesta fw] Configuration processing is completed. Apr 26 05:28:53 192.168.122.209 [48283.451176] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:28:53 192.168.122.209 [48283.478988] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:28:53 192.168.122.209 [48283.506043] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:28:53 192.168.122.209 [48283.544645] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:28:53 192.168.122.209 [48283.545836] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:28:53 192.168.122.209 [48283.588641] [tempesta fw] Tempesta FW is ready Apr 26 05:28:53 192.168.122.209 [48284.135650] [tdb] Close table 'client0.tdb' Apr 26 05:28:53 192.168.122.209 [48284.324713] [tdb] Close table 'sessions0.tdb' Apr 26 05:28:54 192.168.122.209 [48284.569100] [tdb] Close table 'filter0.tdb' Apr 26 05:28:54 192.168.122.209 [48284.569552] [tempesta fw] modules are stopped Apr 26 05:28:54 192.168.122.209 [48284.739297] [tempesta fw] exiting... Apr 26 05:28:54 192.168.122.209 [48284.850402] [tdb] Shutdown Tempesta DB Apr 26 05:28:54 192.168.122.209 [48285.064488] End test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_content_language Apr 26 05:28:54 192.168.122.209 [48285.086488] Start test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_content_location Apr 26 05:28:55 192.168.122.209 [48286.133675] [tdb] Start Tempesta DB Apr 26 05:28:55 192.168.122.209 [48286.270846] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:28:56 192.168.122.209 [48286.958066] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48286.958066] Maybe that's fine, but it's worth checking the [48286.958066] config - if there is no relations between the [48286.958066] names, then host name confusion attack is possible. Apr 26 05:28:56 192.168.122.209 [48287.100706] [tempesta fw] Configuration processing is completed. Apr 26 05:28:56 192.168.122.209 [48287.153783] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:28:56 192.168.122.209 [48287.183949] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:28:56 192.168.122.209 [48287.211079] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:28:56 192.168.122.209 [48287.256756] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:28:56 192.168.122.209 [48287.258390] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:28:56 192.168.122.209 [48287.304703] [tempesta fw] Tempesta FW is ready Apr 26 05:28:57 192.168.122.209 [48287.891216] [tdb] Close table 'client0.tdb' Apr 26 05:28:57 192.168.122.209 [48288.086643] [tdb] Close table 'sessions0.tdb' Apr 26 05:28:57 192.168.122.209 [48288.328123] [tdb] Close table 'filter0.tdb' Apr 26 05:28:57 192.168.122.209 [48288.328586] [tempesta fw] modules are stopped Apr 26 05:28:58 192.168.122.209 [48288.519603] [tempesta fw] exiting... Apr 26 05:28:58 192.168.122.209 [48288.624041] [tdb] Shutdown Tempesta DB Apr 26 05:28:58 192.168.122.209 [48288.855281] End test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_content_location Apr 26 05:28:58 192.168.122.209 [48288.873974] Start test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_content_range Apr 26 05:28:59 192.168.122.209 [48289.945439] [tdb] Start Tempesta DB Apr 26 05:28:59 192.168.122.209 [48290.088668] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:29:00 192.168.122.209 [48290.797906] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48290.797906] Maybe that's fine, but it's worth checking the [48290.797906] config - if there is no relations between the [48290.797906] names, then host name confusion attack is possible. Apr 26 05:29:00 192.168.122.209 [48290.940844] [tempesta fw] Configuration processing is completed. Apr 26 05:29:00 192.168.122.209 [48290.993718] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:29:00 192.168.122.209 [48291.022199] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:29:00 192.168.122.209 [48291.049838] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:29:00 192.168.122.209 [48291.096758] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:29:00 192.168.122.209 [48291.136756] [tempesta fw] Tempesta FW is ready Apr 26 05:29:01 192.168.122.209 [48291.699705] [tdb] Close table 'client0.tdb' Apr 26 05:29:01 192.168.122.209 [48291.891043] [tdb] Close table 'sessions0.tdb' Apr 26 05:29:01 192.168.122.209 [48292.126790] [tdb] Close table 'filter0.tdb' Apr 26 05:29:01 192.168.122.209 [48292.127240] net_ratelimit: 1 callbacks suppressed Apr 26 05:29:01 192.168.122.209 [48292.127241] [tempesta fw] modules are stopped Apr 26 05:29:01 192.168.122.209 [48292.328733] [tempesta fw] exiting... Apr 26 05:29:02 192.168.122.209 [48292.475304] [tdb] Shutdown Tempesta DB Apr 26 05:29:02 192.168.122.209 [48292.700221] End test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_content_range Apr 26 05:29:02 192.168.122.209 [48292.716246] Start test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_content_type Apr 26 05:29:03 192.168.122.209 [48293.786567] [tdb] Start Tempesta DB Apr 26 05:29:03 192.168.122.209 [48293.925583] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:29:04 192.168.122.209 [48294.613648] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48294.613648] Maybe that's fine, but it's worth checking the [48294.613648] config - if there is no relations between the [48294.613648] names, then host name confusion attack is possible. Apr 26 05:29:04 192.168.122.209 [48294.757146] [tempesta fw] Configuration processing is completed. Apr 26 05:29:04 192.168.122.209 [48294.812451] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:29:04 192.168.122.209 [48294.853354] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:29:04 192.168.122.209 [48294.880561] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:29:04 192.168.122.209 [48294.932814] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:29:04 192.168.122.209 [48294.934585] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:29:04 192.168.122.209 [48294.988799] [tempesta fw] Tempesta FW is ready Apr 26 05:29:05 192.168.122.209 [48295.545293] [tdb] Close table 'client0.tdb' Apr 26 05:29:05 192.168.122.209 [48295.738492] [tdb] Close table 'sessions0.tdb' Apr 26 05:29:05 192.168.122.209 [48295.978098] [tdb] Close table 'filter0.tdb' Apr 26 05:29:05 192.168.122.209 [48295.978526] [tempesta fw] modules are stopped Apr 26 05:29:05 192.168.122.209 [48296.178682] [tempesta fw] exiting... Apr 26 05:29:05 192.168.122.209 [48296.323838] [tdb] Shutdown Tempesta DB Apr 26 05:29:06 192.168.122.209 [48296.531561] End test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_content_type Apr 26 05:29:06 192.168.122.209 [48296.544680] Start test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_date Apr 26 05:29:07 192.168.122.209 [48297.599910] [tdb] Start Tempesta DB Apr 26 05:29:07 192.168.122.209 [48297.749185] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:29:08 192.168.122.209 [48298.453932] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48298.453932] Maybe that's fine, but it's worth checking the [48298.453932] config - if there is no relations between the [48298.453932] names, then host name confusion attack is possible. Apr 26 05:29:08 192.168.122.209 [48298.588871] [tempesta fw] Configuration processing is completed. Apr 26 05:29:08 192.168.122.209 [48298.642032] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:29:08 192.168.122.209 [48298.672292] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:29:08 192.168.122.209 [48298.701801] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:29:08 192.168.122.209 [48298.736831] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:29:08 192.168.122.209 [48298.737721] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:29:08 192.168.122.209 [48298.776852] [tempesta fw] Tempesta FW is ready Apr 26 05:29:08 192.168.122.209 [48299.321814] [tdb] Close table 'client0.tdb' Apr 26 05:29:09 192.168.122.209 [48299.502458] [tdb] Close table 'sessions0.tdb' Apr 26 05:29:09 192.168.122.209 [48299.716790] [tdb] Close table 'filter0.tdb' Apr 26 05:29:09 192.168.122.209 [48299.717246] [tempesta fw] modules are stopped Apr 26 05:29:09 192.168.122.209 [48299.948860] [tempesta fw] exiting... Apr 26 05:29:09 192.168.122.209 [48300.065313] [tdb] Shutdown Tempesta DB Apr 26 05:29:09 192.168.122.209 [48300.253500] End test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_date Apr 26 05:29:09 192.168.122.209 [48300.277161] Start test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_expect Apr 26 05:29:10 192.168.122.209 [48301.356168] [tdb] Start Tempesta DB Apr 26 05:29:11 192.168.122.209 [48301.500819] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:29:11 192.168.122.209 [48302.226329] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48302.226329] Maybe that's fine, but it's worth checking the [48302.226329] config - if there is no relations between the [48302.226329] names, then host name confusion attack is possible. Apr 26 05:29:11 192.168.122.209 [48302.361278] [tempesta fw] Configuration processing is completed. Apr 26 05:29:12 192.168.122.209 [48302.415930] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:29:12 192.168.122.209 [48302.449044] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:29:12 192.168.122.209 [48302.477497] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:29:12 192.168.122.209 [48302.521117] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:29:12 192.168.122.209 [48302.564879] [tempesta fw] Tempesta FW is ready Apr 26 05:29:12 192.168.122.209 [48303.136177] [tdb] Close table 'client0.tdb' Apr 26 05:29:12 192.168.122.209 [48303.332255] [tdb] Close table 'sessions0.tdb' Apr 26 05:29:13 192.168.122.209 [48303.568804] [tdb] Close table 'filter0.tdb' Apr 26 05:29:13 192.168.122.209 [48303.569242] net_ratelimit: 1 callbacks suppressed Apr 26 05:29:13 192.168.122.209 [48303.569243] [tempesta fw] modules are stopped Apr 26 05:29:13 192.168.122.209 [48303.759289] [tempesta fw] exiting... Apr 26 05:29:13 192.168.122.209 [48303.914166] [tdb] Shutdown Tempesta DB Apr 26 05:29:13 192.168.122.209 [48304.134835] End test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_expect Apr 26 05:29:13 192.168.122.209 [48304.142853] Start test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_from Apr 26 05:29:14 192.168.122.209 [48305.232787] [tdb] Start Tempesta DB Apr 26 05:29:14 192.168.122.209 [48305.379162] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:29:15 192.168.122.209 [48306.046318] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48306.046318] Maybe that's fine, but it's worth checking the [48306.046318] config - if there is no relations between the [48306.046318] names, then host name confusion attack is possible. Apr 26 05:29:15 192.168.122.209 [48306.193005] [tempesta fw] Configuration processing is completed. Apr 26 05:29:15 192.168.122.209 [48306.246320] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:29:15 192.168.122.209 [48306.276763] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:29:15 192.168.122.209 [48306.306280] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:29:15 192.168.122.209 [48306.352948] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:29:15 192.168.122.209 [48306.354358] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:29:15 192.168.122.209 [48306.400933] [tempesta fw] Tempesta FW is ready Apr 26 05:29:16 192.168.122.209 [48306.984287] [tdb] Close table 'client0.tdb' Apr 26 05:29:16 192.168.122.209 [48307.194589] [tdb] Close table 'sessions0.tdb' Apr 26 05:29:17 192.168.122.209 [48307.434759] [tdb] Close table 'filter0.tdb' Apr 26 05:29:17 192.168.122.209 [48307.435199] [tempesta fw] modules are stopped Apr 26 05:29:17 192.168.122.209 [48307.666765] [tempesta fw] exiting... Apr 26 05:29:17 192.168.122.209 [48307.797699] [tdb] Shutdown Tempesta DB Apr 26 05:29:17 192.168.122.209 [48308.015708] End test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_from Apr 26 05:29:17 192.168.122.209 [48308.037807] Start test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_if_match Apr 26 05:29:18 192.168.122.209 [48309.066850] [tdb] Start Tempesta DB Apr 26 05:29:18 192.168.122.209 [48309.200429] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:29:19 192.168.122.209 [48309.910314] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48309.910314] Maybe that's fine, but it's worth checking the [48309.910314] config - if there is no relations between the [48309.910314] names, then host name confusion attack is possible. Apr 26 05:29:19 192.168.122.209 [48310.057041] [tempesta fw] Configuration processing is completed. Apr 26 05:29:19 192.168.122.209 [48310.111820] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:29:19 192.168.122.209 [48310.139528] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:29:19 192.168.122.209 [48310.167885] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:29:19 192.168.122.209 [48310.249044] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:29:19 192.168.122.209 [48310.250761] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:29:19 192.168.122.209 [48310.288998] [tempesta fw] Tempesta FW is ready Apr 26 05:29:20 192.168.122.209 [48310.845165] [tdb] Close table 'client0.tdb' Apr 26 05:29:20 192.168.122.209 [48311.061821] [tdb] Close table 'sessions0.tdb' Apr 26 05:29:20 192.168.122.209 [48311.322378] [tdb] Close table 'filter0.tdb' Apr 26 05:29:20 192.168.122.209 [48311.322798] [tempesta fw] modules are stopped Apr 26 05:29:21 192.168.122.209 [48311.518605] [tempesta fw] exiting... Apr 26 05:29:21 192.168.122.209 [48311.642106] [tdb] Shutdown Tempesta DB Apr 26 05:29:21 192.168.122.209 [48311.837161] End test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_if_match Apr 26 05:29:21 192.168.122.209 [48311.858575] Start test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_if_modified_since Apr 26 05:29:22 192.168.122.209 [48312.999718] [tdb] Start Tempesta DB Apr 26 05:29:22 192.168.122.209 [48313.148457] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:29:23 192.168.122.209 [48313.878395] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48313.878395] Maybe that's fine, but it's worth checking the [48313.878395] config - if there is no relations between the [48313.878395] names, then host name confusion attack is possible. Apr 26 05:29:23 192.168.122.209 [48314.017097] [tempesta fw] Configuration processing is completed. Apr 26 05:29:23 192.168.122.209 [48314.070814] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:29:23 192.168.122.209 [48314.106403] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:29:23 192.168.122.209 [48314.135101] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:29:23 192.168.122.209 [48314.181119] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:29:23 192.168.122.209 [48314.233025] [tempesta fw] Tempesta FW is ready Apr 26 05:29:24 192.168.122.209 [48314.787075] [tdb] Close table 'client0.tdb' Apr 26 05:29:24 192.168.122.209 [48314.978649] [tdb] Close table 'sessions0.tdb' Apr 26 05:29:24 192.168.122.209 [48315.228578] [tdb] Close table 'filter0.tdb' Apr 26 05:29:24 192.168.122.209 [48315.229074] net_ratelimit: 1 callbacks suppressed Apr 26 05:29:24 192.168.122.209 [48315.229075] [tempesta fw] modules are stopped Apr 26 05:29:25 192.168.122.209 [48315.447639] [tempesta fw] exiting... Apr 26 05:29:25 192.168.122.209 [48315.561922] [tdb] Shutdown Tempesta DB Apr 26 05:29:25 192.168.122.209 [48315.785184] End test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_if_modified_since Apr 26 05:29:25 192.168.122.209 [48315.807420] Start test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_if_range Apr 26 05:29:26 192.168.122.209 [48316.861906] [tdb] Start Tempesta DB Apr 26 05:29:26 192.168.122.209 [48317.001571] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:29:27 192.168.122.209 [48317.706058] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48317.706058] Maybe that's fine, but it's worth checking the [48317.706058] config - if there is no relations between the [48317.706058] names, then host name confusion attack is possible. Apr 26 05:29:27 192.168.122.209 [48317.837079] [tempesta fw] Configuration processing is completed. Apr 26 05:29:27 192.168.122.209 [48317.888730] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:29:27 192.168.122.209 [48317.916803] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:29:27 192.168.122.209 [48317.943717] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:29:27 192.168.122.209 [48318.005128] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:29:27 192.168.122.209 [48318.006919] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:29:27 192.168.122.209 [48318.053110] [tempesta fw] Tempesta FW is ready Apr 26 05:29:28 192.168.122.209 [48318.643605] [tdb] Close table 'client0.tdb' Apr 26 05:29:28 192.168.122.209 [48318.822593] [tdb] Close table 'sessions0.tdb' Apr 26 05:29:28 192.168.122.209 [48319.058166] [tdb] Close table 'filter0.tdb' Apr 26 05:29:28 192.168.122.209 [48319.058629] [tempesta fw] modules are stopped Apr 26 05:29:28 192.168.122.209 [48319.261099] [tempesta fw] exiting... Apr 26 05:29:28 192.168.122.209 [48319.375638] [tdb] Shutdown Tempesta DB Apr 26 05:29:29 192.168.122.209 [48319.583417] End test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_if_range Apr 26 05:29:29 192.168.122.209 [48319.602464] Start test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_if_unmodified_since Apr 26 05:29:30 192.168.122.209 [48320.774821] [tdb] Start Tempesta DB Apr 26 05:29:30 192.168.122.209 [48320.939577] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:29:31 192.168.122.209 [48321.650534] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48321.650534] Maybe that's fine, but it's worth checking the [48321.650534] config - if there is no relations between the [48321.650534] names, then host name confusion attack is possible. Apr 26 05:29:31 192.168.122.209 [48321.793269] [tempesta fw] Configuration processing is completed. Apr 26 05:29:31 192.168.122.209 [48321.847133] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:29:31 192.168.122.209 [48321.877696] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:29:31 192.168.122.209 [48321.905198] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:29:31 192.168.122.209 [48321.953201] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:29:31 192.168.122.209 [48321.954825] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:29:31 192.168.122.209 [48322.005132] [tempesta fw] Tempesta FW is ready Apr 26 05:29:32 192.168.122.209 [48322.568594] [tdb] Close table 'client0.tdb' Apr 26 05:29:32 192.168.122.209 [48322.773995] [tdb] Close table 'sessions0.tdb' Apr 26 05:29:32 192.168.122.209 [48323.013892] [tdb] Close table 'filter0.tdb' Apr 26 05:29:32 192.168.122.209 [48323.014331] [tempesta fw] modules are stopped Apr 26 05:29:32 192.168.122.209 [48323.246306] [tempesta fw] exiting... Apr 26 05:29:32 192.168.122.209 [48323.368795] [tdb] Shutdown Tempesta DB Apr 26 05:29:33 192.168.122.209 [48323.590457] End test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_if_unmodified_since Apr 26 05:29:33 192.168.122.209 [48323.604636] Start test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_last_modified Apr 26 05:29:34 192.168.122.209 [48324.654138] [tdb] Start Tempesta DB Apr 26 05:29:34 192.168.122.209 [48324.784350] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:29:35 192.168.122.209 [48325.482387] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48325.482387] Maybe that's fine, but it's worth checking the [48325.482387] config - if there is no relations between the [48325.482387] names, then host name confusion attack is possible. Apr 26 05:29:35 192.168.122.209 [48325.637183] [tempesta fw] Configuration processing is completed. Apr 26 05:29:35 192.168.122.209 [48325.687619] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:29:35 192.168.122.209 [48325.715552] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:29:35 192.168.122.209 [48325.742319] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:29:35 192.168.122.209 [48325.801225] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:29:35 192.168.122.209 [48325.841196] [tempesta fw] Tempesta FW is ready Apr 26 05:29:35 192.168.122.209 [48326.399288] [tdb] Close table 'client0.tdb' Apr 26 05:29:36 192.168.122.209 [48326.589797] [tdb] Close table 'sessions0.tdb' Apr 26 05:29:36 192.168.122.209 [48326.813531] [tdb] Close table 'filter0.tdb' Apr 26 05:29:36 192.168.122.209 [48326.813984] net_ratelimit: 1 callbacks suppressed Apr 26 05:29:36 192.168.122.209 [48326.813985] [tempesta fw] modules are stopped Apr 26 05:29:36 192.168.122.209 [48327.000333] [tempesta fw] exiting... Apr 26 05:29:36 192.168.122.209 [48327.132015] [tdb] Shutdown Tempesta DB Apr 26 05:29:36 192.168.122.209 [48327.341312] End test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_last_modified Apr 26 05:29:36 192.168.122.209 [48327.362516] Start test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_max_forwards Apr 26 05:29:38 192.168.122.209 [48328.430958] [tdb] Start Tempesta DB Apr 26 05:29:38 192.168.122.209 [48328.585611] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:29:38 192.168.122.209 [48329.258612] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48329.258612] Maybe that's fine, but it's worth checking the [48329.258612] config - if there is no relations between the [48329.258612] names, then host name confusion attack is possible. Apr 26 05:29:38 192.168.122.209 [48329.409342] [tempesta fw] Configuration processing is completed. Apr 26 05:29:39 192.168.122.209 [48329.467030] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:29:39 192.168.122.209 [48329.495083] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:29:39 192.168.122.209 [48329.521946] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:29:39 192.168.122.209 [48329.565291] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:29:39 192.168.122.209 [48329.567025] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:29:39 192.168.122.209 [48329.609221] [tempesta fw] Tempesta FW is ready Apr 26 05:29:39 192.168.122.209 [48330.149730] [tdb] Close table 'client0.tdb' Apr 26 05:29:39 192.168.122.209 [48330.367699] [tdb] Close table 'sessions0.tdb' Apr 26 05:29:40 192.168.122.209 [48330.598433] [tdb] Close table 'filter0.tdb' Apr 26 05:29:40 192.168.122.209 [48330.598875] [tempesta fw] modules are stopped Apr 26 05:29:40 192.168.122.209 [48330.782898] [tempesta fw] exiting... Apr 26 05:29:40 192.168.122.209 [48330.904630] [tdb] Shutdown Tempesta DB Apr 26 05:29:40 192.168.122.209 [48331.129564] End test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_max_forwards Apr 26 05:29:40 192.168.122.209 [48331.139018] Start test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_pragma Apr 26 05:29:41 192.168.122.209 [48332.269024] [tdb] Start Tempesta DB Apr 26 05:29:41 192.168.122.209 [48332.400622] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:29:42 192.168.122.209 [48333.090483] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48333.090483] Maybe that's fine, but it's worth checking the [48333.090483] config - if there is no relations between the [48333.090483] names, then host name confusion attack is possible. Apr 26 05:29:42 192.168.122.209 [48333.225611] [tempesta fw] Configuration processing is completed. Apr 26 05:29:42 192.168.122.209 [48333.289106] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:29:42 192.168.122.209 [48333.326538] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:29:42 192.168.122.209 [48333.360851] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:29:42 192.168.122.209 [48333.405283] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:29:42 192.168.122.209 [48333.406443] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:29:43 192.168.122.209 [48333.449270] [tempesta fw] Tempesta FW is ready Apr 26 05:29:43 192.168.122.209 [48334.012673] [tdb] Close table 'client0.tdb' Apr 26 05:29:43 192.168.122.209 [48334.193981] [tdb] Close table 'sessions0.tdb' Apr 26 05:29:43 192.168.122.209 [48334.412924] [tdb] Close table 'filter0.tdb' Apr 26 05:29:43 192.168.122.209 [48334.413376] [tempesta fw] modules are stopped Apr 26 05:29:44 192.168.122.209 [48334.635406] [tempesta fw] exiting... Apr 26 05:29:44 192.168.122.209 [48334.765107] [tdb] Shutdown Tempesta DB Apr 26 05:29:44 192.168.122.209 [48334.987078] End test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_pragma Apr 26 05:29:44 192.168.122.209 [48335.001439] Start test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_range Apr 26 05:29:45 192.168.122.209 [48336.079589] [tdb] Start Tempesta DB Apr 26 05:29:45 192.168.122.209 [48336.217180] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:29:46 192.168.122.209 [48336.926714] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48336.926714] Maybe that's fine, but it's worth checking the [48336.926714] config - if there is no relations between the [48336.926714] names, then host name confusion attack is possible. Apr 26 05:29:46 192.168.122.209 [48337.065397] [tempesta fw] Configuration processing is completed. Apr 26 05:29:46 192.168.122.209 [48337.119612] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:29:46 192.168.122.209 [48337.151913] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:29:46 192.168.122.209 [48337.180606] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:29:46 192.168.122.209 [48337.233399] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:29:46 192.168.122.209 [48337.273330] [tempesta fw] Tempesta FW is ready Apr 26 05:29:47 192.168.122.209 [48337.832506] [tdb] Close table 'client0.tdb' Apr 26 05:29:47 192.168.122.209 [48338.040205] [tdb] Close table 'sessions0.tdb' Apr 26 05:29:47 192.168.122.209 [48338.278955] [tdb] Close table 'filter0.tdb' Apr 26 05:29:47 192.168.122.209 [48338.279406] net_ratelimit: 1 callbacks suppressed Apr 26 05:29:47 192.168.122.209 [48338.279408] [tempesta fw] modules are stopped Apr 26 05:29:48 192.168.122.209 [48338.477329] [tempesta fw] exiting... Apr 26 05:29:48 192.168.122.209 [48338.600623] [tdb] Shutdown Tempesta DB Apr 26 05:29:48 192.168.122.209 [48338.825976] End test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_range Apr 26 05:29:48 192.168.122.209 [48338.851385] Start test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_referer Apr 26 05:29:49 192.168.122.209 [48339.877614] [tdb] Start Tempesta DB Apr 26 05:29:49 192.168.122.209 [48340.029890] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:29:50 192.168.122.209 [48340.722891] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48340.722891] Maybe that's fine, but it's worth checking the [48340.722891] config - if there is no relations between the [48340.722891] names, then host name confusion attack is possible. Apr 26 05:29:50 192.168.122.209 [48340.853524] [tempesta fw] Configuration processing is completed. Apr 26 05:29:50 192.168.122.209 [48340.909565] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:29:50 192.168.122.209 [48340.937957] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:29:50 192.168.122.209 [48340.965087] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:29:50 192.168.122.209 [48341.033482] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:29:50 192.168.122.209 [48341.035383] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:29:50 192.168.122.209 [48341.093443] [tempesta fw] Tempesta FW is ready Apr 26 05:29:51 192.168.122.209 [48341.658270] [tdb] Close table 'client0.tdb' Apr 26 05:29:51 192.168.122.209 [48341.839501] [tdb] Close table 'sessions0.tdb' Apr 26 05:29:51 192.168.122.209 [48342.068749] [tdb] Close table 'filter0.tdb' Apr 26 05:29:51 192.168.122.209 [48342.069194] [tempesta fw] modules are stopped Apr 26 05:29:51 192.168.122.209 [48342.313488] [tempesta fw] exiting... Apr 26 05:29:52 192.168.122.209 [48342.458359] [tdb] Shutdown Tempesta DB Apr 26 05:29:52 192.168.122.209 [48342.666757] End test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_referer Apr 26 05:29:52 192.168.122.209 [48342.676095] Start test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_te Apr 26 05:29:53 192.168.122.209 [48343.756119] [tdb] Start Tempesta DB Apr 26 05:29:53 192.168.122.209 [48343.907513] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:29:54 192.168.122.209 [48344.543515] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48344.543515] Maybe that's fine, but it's worth checking the [48344.543515] config - if there is no relations between the [48344.543515] names, then host name confusion attack is possible. Apr 26 05:29:54 192.168.122.209 [48344.677496] [tempesta fw] Configuration processing is completed. Apr 26 05:29:54 192.168.122.209 [48344.753922] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:29:54 192.168.122.209 [48344.793076] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:29:54 192.168.122.209 [48344.829825] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:29:54 192.168.122.209 [48344.881341] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:29:54 192.168.122.209 [48344.882276] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:29:54 192.168.122.209 [48344.921309] [tempesta fw] Tempesta FW is ready Apr 26 05:29:55 192.168.122.209 [48345.476022] [tdb] Close table 'client0.tdb' Apr 26 05:29:55 192.168.122.209 [48345.670641] [tdb] Close table 'sessions0.tdb' Apr 26 05:29:55 192.168.122.209 [48345.908667] [tdb] Close table 'filter0.tdb' Apr 26 05:29:55 192.168.122.209 [48345.909101] [tempesta fw] modules are stopped Apr 26 05:29:55 192.168.122.209 [48346.082822] [tempesta fw] exiting... Apr 26 05:29:55 192.168.122.209 [48346.209798] [tdb] Shutdown Tempesta DB Apr 26 05:29:55 192.168.122.209 [48346.411878] End test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_te Apr 26 05:29:56 192.168.122.209 [48346.427821] Start test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_trailer Apr 26 05:29:57 192.168.122.209 [48347.540907] [tdb] Start Tempesta DB Apr 26 05:29:57 192.168.122.209 [48347.698929] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:29:58 192.168.122.209 [48348.434818] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48348.434818] Maybe that's fine, but it's worth checking the [48348.434818] config - if there is no relations between the [48348.434818] names, then host name confusion attack is possible. Apr 26 05:29:58 192.168.122.209 [48348.601541] [tempesta fw] Configuration processing is completed. Apr 26 05:29:58 192.168.122.209 [48348.653436] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:29:58 192.168.122.209 [48348.681724] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:29:58 192.168.122.209 [48348.708810] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:29:58 192.168.122.209 [48348.753481] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:29:58 192.168.122.209 [48348.793473] [tempesta fw] Tempesta FW is ready Apr 26 05:29:58 192.168.122.209 [48349.356240] [tdb] Close table 'client0.tdb' Apr 26 05:29:59 192.168.122.209 [48349.545304] [tdb] Close table 'sessions0.tdb' Apr 26 05:29:59 192.168.122.209 [48349.782508] [tdb] Close table 'filter0.tdb' Apr 26 05:29:59 192.168.122.209 [48349.782961] net_ratelimit: 1 callbacks suppressed Apr 26 05:29:59 192.168.122.209 [48349.782963] [tempesta fw] modules are stopped Apr 26 05:29:59 192.168.122.209 [48349.988643] [tempesta fw] exiting... Apr 26 05:29:59 192.168.122.209 [48350.110755] [tdb] Shutdown Tempesta DB Apr 26 05:29:59 192.168.122.209 [48350.311433] End test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_trailer Apr 26 05:29:59 192.168.122.209 [48350.324411] Start test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_upgrade Apr 26 05:30:00 192.168.122.209 [48351.375049] [tdb] Start Tempesta DB Apr 26 05:30:01 192.168.122.209 [48351.524089] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:30:01 192.168.122.209 [48352.238842] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48352.238842] Maybe that's fine, but it's worth checking the [48352.238842] config - if there is no relations between the [48352.238842] names, then host name confusion attack is possible. Apr 26 05:30:01 192.168.122.209 [48352.381578] [tempesta fw] Configuration processing is completed. Apr 26 05:30:02 192.168.122.209 [48352.433442] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:30:02 192.168.122.209 [48352.463018] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:30:02 192.168.122.209 [48352.489499] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:30:02 192.168.122.209 [48352.553571] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:30:02 192.168.122.209 [48352.555333] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:30:02 192.168.122.209 [48352.593625] [tempesta fw] Tempesta FW is ready Apr 26 05:30:02 192.168.122.209 [48353.169215] [tdb] Close table 'client0.tdb' Apr 26 05:30:02 192.168.122.209 [48353.362567] [tdb] Close table 'sessions0.tdb' Apr 26 05:30:03 192.168.122.209 [48353.597347] [tdb] Close table 'filter0.tdb' Apr 26 05:30:03 192.168.122.209 [48353.597791] [tempesta fw] modules are stopped Apr 26 05:30:03 192.168.122.209 [48353.767463] [tempesta fw] exiting... Apr 26 05:30:03 192.168.122.209 [48353.917122] [tdb] Shutdown Tempesta DB Apr 26 05:30:03 192.168.122.209 [48354.188907] End test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_upgrade Apr 26 05:30:03 192.168.122.209 [48354.199481] Start test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_user_agent Apr 26 05:30:04 192.168.122.209 [48355.212778] [tdb] Start Tempesta DB Apr 26 05:30:04 192.168.122.209 [48355.347857] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:30:05 192.168.122.209 [48356.038300] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48356.038300] Maybe that's fine, but it's worth checking the [48356.038300] config - if there is no relations between the [48356.038300] names, then host name confusion attack is possible. Apr 26 05:30:05 192.168.122.209 [48356.161699] [tempesta fw] Configuration processing is completed. Apr 26 05:30:05 192.168.122.209 [48356.213486] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:30:05 192.168.122.209 [48356.245593] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:30:05 192.168.122.209 [48356.280709] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:30:05 192.168.122.209 [48356.321510] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:30:05 192.168.122.209 [48356.322581] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:30:05 192.168.122.209 [48356.361503] [tempesta fw] Tempesta FW is ready Apr 26 05:30:06 192.168.122.209 [48356.937843] [tdb] Close table 'client0.tdb' Apr 26 05:30:06 192.168.122.209 [48357.118685] [tdb] Close table 'sessions0.tdb' Apr 26 05:30:06 192.168.122.209 [48357.369549] [tdb] Close table 'filter0.tdb' Apr 26 05:30:06 192.168.122.209 [48357.370026] [tempesta fw] modules are stopped Apr 26 05:30:07 192.168.122.209 [48357.579463] [tempesta fw] exiting... Apr 26 05:30:07 192.168.122.209 [48357.730326] [tdb] Shutdown Tempesta DB Apr 26 05:30:07 192.168.122.209 [48357.956220] End test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_user_agent Apr 26 05:30:07 192.168.122.209 [48357.981998] Start test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_via Apr 26 05:30:08 192.168.122.209 [48359.234806] [tdb] Start Tempesta DB Apr 26 05:30:08 192.168.122.209 [48359.403455] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:30:09 192.168.122.209 [48360.106969] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48360.106969] Maybe that's fine, but it's worth checking the [48360.106969] config - if there is no relations between the [48360.106969] names, then host name confusion attack is possible. Apr 26 05:30:09 192.168.122.209 [48360.261710] [tempesta fw] Configuration processing is completed. Apr 26 05:30:09 192.168.122.209 [48360.323422] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:30:09 192.168.122.209 [48360.351871] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:30:09 192.168.122.209 [48360.379209] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:30:10 192.168.122.209 [48360.421634] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:30:10 192.168.122.209 [48360.422739] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:30:10 192.168.122.209 [48360.461617] [tempesta fw] Tempesta FW is ready Apr 26 05:30:10 192.168.122.209 [48361.021885] [tdb] Close table 'client0.tdb' Apr 26 05:30:10 192.168.122.209 [48361.225897] [tdb] Close table 'sessions0.tdb' Apr 26 05:30:11 192.168.122.209 [48361.476169] [tdb] Close table 'filter0.tdb' Apr 26 05:30:11 192.168.122.209 [48361.476636] [tempesta fw] modules are stopped Apr 26 05:30:11 192.168.122.209 [48361.728980] [tempesta fw] exiting... Apr 26 05:30:11 192.168.122.209 [48361.842729] [tdb] Shutdown Tempesta DB Apr 26 05:30:11 192.168.122.209 [48362.032820] End test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_via Apr 26 05:30:11 192.168.122.209 [48362.047658] Start test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_accept_ranges Apr 26 05:30:12 192.168.122.209 [48363.195015] [tdb] Start Tempesta DB Apr 26 05:30:12 192.168.122.209 [48363.359711] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:30:13 192.168.122.209 [48364.038343] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48364.038343] Maybe that's fine, but it's worth checking the [48364.038343] config - if there is no relations between the [48364.038343] names, then host name confusion attack is possible. Apr 26 05:30:13 192.168.122.209 [48364.181706] [tempesta fw] Configuration processing is completed. Apr 26 05:30:13 192.168.122.209 [48364.241044] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:30:13 192.168.122.209 [48364.279714] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:30:13 192.168.122.209 [48364.315257] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:30:13 192.168.122.209 [48364.361700] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:30:13 192.168.122.209 [48364.363137] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:30:14 192.168.122.209 [48364.421692] [tempesta fw] Tempesta FW is ready Apr 26 05:30:14 192.168.122.209 [48365.017048] [tdb] Close table 'client0.tdb' Apr 26 05:30:14 192.168.122.209 [48365.210419] [tdb] Close table 'sessions0.tdb' Apr 26 05:30:15 192.168.122.209 [48365.440310] [tdb] Close table 'filter0.tdb' Apr 26 05:30:15 192.168.122.209 [48365.440757] [tempesta fw] modules are stopped Apr 26 05:30:15 192.168.122.209 [48365.615285] [tempesta fw] exiting... Apr 26 05:30:15 192.168.122.209 [48365.754200] [tdb] Shutdown Tempesta DB Apr 26 05:30:15 192.168.122.209 [48365.975348] End test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_accept_ranges Apr 26 05:30:15 192.168.122.209 [48365.990282] Start test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_allow Apr 26 05:30:16 192.168.122.209 [48367.100465] [tdb] Start Tempesta DB Apr 26 05:30:16 192.168.122.209 [48367.257103] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:30:17 192.168.122.209 [48367.962725] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48367.962725] Maybe that's fine, but it's worth checking the [48367.962725] config - if there is no relations between the [48367.962725] names, then host name confusion attack is possible. Apr 26 05:30:17 192.168.122.209 [48368.113790] [tempesta fw] Configuration processing is completed. Apr 26 05:30:17 192.168.122.209 [48368.176586] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:30:17 192.168.122.209 [48368.215596] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:30:17 192.168.122.209 [48368.251787] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:30:17 192.168.122.209 [48368.305736] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:30:17 192.168.122.209 [48368.307358] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:30:17 192.168.122.209 [48368.353731] [tempesta fw] Tempesta FW is ready Apr 26 05:30:18 192.168.122.209 [48368.931035] [tdb] Close table 'client0.tdb' Apr 26 05:30:18 192.168.122.209 [48369.122564] [tdb] Close table 'sessions0.tdb' Apr 26 05:30:18 192.168.122.209 [48369.358167] [tdb] Close table 'filter0.tdb' Apr 26 05:30:18 192.168.122.209 [48369.358598] [tempesta fw] modules are stopped Apr 26 05:30:19 192.168.122.209 [48369.560077] [tempesta fw] exiting... Apr 26 05:30:19 192.168.122.209 [48369.706567] [tdb] Shutdown Tempesta DB Apr 26 05:30:19 192.168.122.209 [48369.920194] End test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_allow Apr 26 05:30:19 192.168.122.209 [48369.940037] Start test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_connection Apr 26 05:30:20 192.168.122.209 [48371.095722] [tdb] Start Tempesta DB Apr 26 05:30:20 192.168.122.209 [48371.235854] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:30:21 192.168.122.209 [48371.902726] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48371.902726] Maybe that's fine, but it's worth checking the [48371.902726] config - if there is no relations between the [48371.902726] names, then host name confusion attack is possible. Apr 26 05:30:21 192.168.122.209 [48372.061855] [tempesta fw] Configuration processing is completed. Apr 26 05:30:21 192.168.122.209 [48372.120485] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:30:21 192.168.122.209 [48372.157487] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:30:21 192.168.122.209 [48372.192594] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:30:21 192.168.122.209 [48372.249803] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:30:21 192.168.122.209 [48372.251547] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:30:21 192.168.122.209 [48372.289797] [tempesta fw] Tempesta FW is ready Apr 26 05:30:22 192.168.122.209 [48372.835385] [tdb] Close table 'client0.tdb' Apr 26 05:30:22 192.168.122.209 [48373.047821] [tdb] Close table 'sessions0.tdb' Apr 26 05:30:22 192.168.122.209 [48373.287653] [tdb] Close table 'filter0.tdb' Apr 26 05:30:22 192.168.122.209 [48373.288065] [tempesta fw] modules are stopped Apr 26 05:30:23 192.168.122.209 [48373.529992] [tempesta fw] exiting... Apr 26 05:30:23 192.168.122.209 [48373.646507] [tdb] Shutdown Tempesta DB Apr 26 05:30:23 192.168.122.209 [48373.853061] End test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_connection Apr 26 05:30:23 192.168.122.209 [48373.864024] Start test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_content_encoding Apr 26 05:30:24 192.168.122.209 [48374.966524] [tdb] Start Tempesta DB Apr 26 05:30:24 192.168.122.209 [48375.113127] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:30:25 192.168.122.209 [48375.870436] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48375.870436] Maybe that's fine, but it's worth checking the [48375.870436] config - if there is no relations between the [48375.870436] names, then host name confusion attack is possible. Apr 26 05:30:25 192.168.122.209 [48376.005942] [tempesta fw] Configuration processing is completed. Apr 26 05:30:25 192.168.122.209 [48376.063022] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:30:25 192.168.122.209 [48376.100725] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:30:25 192.168.122.209 [48376.135601] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:30:25 192.168.122.209 [48376.189802] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:30:25 192.168.122.209 [48376.233809] [tempesta fw] Tempesta FW is ready Apr 26 05:30:26 192.168.122.209 [48376.817649] [tdb] Close table 'client0.tdb' Apr 26 05:30:26 192.168.122.209 [48377.005571] [tdb] Close table 'sessions0.tdb' Apr 26 05:30:26 192.168.122.209 [48377.243569] [tdb] Close table 'filter0.tdb' Apr 26 05:30:26 192.168.122.209 [48377.244001] net_ratelimit: 1 callbacks suppressed Apr 26 05:30:26 192.168.122.209 [48377.244003] [tempesta fw] modules are stopped Apr 26 05:30:27 192.168.122.209 [48377.447416] [tempesta fw] exiting... Apr 26 05:30:27 192.168.122.209 [48377.550357] [tdb] Shutdown Tempesta DB Apr 26 05:30:27 192.168.122.209 [48377.782278] End test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_content_encoding Apr 26 05:30:27 192.168.122.209 [48377.790760] Start test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_content_language Apr 26 05:30:28 192.168.122.209 [48378.885648] [tdb] Start Tempesta DB Apr 26 05:30:28 192.168.122.209 [48379.022817] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:30:29 192.168.122.209 [48379.739309] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48379.739309] Maybe that's fine, but it's worth checking the [48379.739309] config - if there is no relations between the [48379.739309] names, then host name confusion attack is possible. Apr 26 05:30:29 192.168.122.209 [48379.897858] [tempesta fw] Configuration processing is completed. Apr 26 05:30:29 192.168.122.209 [48379.954933] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:30:29 192.168.122.209 [48379.985216] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:30:29 192.168.122.209 [48380.012927] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:30:29 192.168.122.209 [48380.065870] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:30:29 192.168.122.209 [48380.067149] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:30:29 192.168.122.209 [48380.105867] [tempesta fw] Tempesta FW is ready Apr 26 05:30:30 192.168.122.209 [48380.681208] [tdb] Close table 'client0.tdb' Apr 26 05:30:30 192.168.122.209 [48380.871213] [tdb] Close table 'sessions0.tdb' Apr 26 05:30:30 192.168.122.209 [48381.096157] [tdb] Close table 'filter0.tdb' Apr 26 05:30:30 192.168.122.209 [48381.096596] [tempesta fw] modules are stopped Apr 26 05:30:30 192.168.122.209 [48381.307685] [tempesta fw] exiting... Apr 26 05:30:31 192.168.122.209 [48381.444418] [tdb] Shutdown Tempesta DB Apr 26 05:30:31 192.168.122.209 [48381.651902] End test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_content_language Apr 26 05:30:31 192.168.122.209 [48381.662070] Start test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_content_location Apr 26 05:30:32 192.168.122.209 [48382.781331] [tdb] Start Tempesta DB Apr 26 05:30:32 192.168.122.209 [48382.938735] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:30:33 192.168.122.209 [48383.638810] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48383.638810] Maybe that's fine, but it's worth checking the [48383.638810] config - if there is no relations between the [48383.638810] names, then host name confusion attack is possible. Apr 26 05:30:33 192.168.122.209 [48383.793988] [tempesta fw] Configuration processing is completed. Apr 26 05:30:33 192.168.122.209 [48383.848853] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:30:33 192.168.122.209 [48383.876456] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:30:33 192.168.122.209 [48383.902849] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:30:33 192.168.122.209 [48383.961958] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:30:33 192.168.122.209 [48383.963665] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:30:33 192.168.122.209 [48384.005906] [tempesta fw] Tempesta FW is ready Apr 26 05:30:34 192.168.122.209 [48384.582075] [tdb] Close table 'client0.tdb' Apr 26 05:30:34 192.168.122.209 [48384.769604] [tdb] Close table 'sessions0.tdb' Apr 26 05:30:34 192.168.122.209 [48385.012121] [tdb] Close table 'filter0.tdb' Apr 26 05:30:34 192.168.122.209 [48385.012568] [tempesta fw] modules are stopped Apr 26 05:30:34 192.168.122.209 [48385.186568] [tempesta fw] exiting... Apr 26 05:30:34 192.168.122.209 [48385.312534] [tdb] Shutdown Tempesta DB Apr 26 05:30:35 192.168.122.209 [48385.500315] End test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_content_location Apr 26 05:30:35 192.168.122.209 [48385.521261] Start test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_content_range Apr 26 05:30:36 192.168.122.209 [48386.640863] [tdb] Start Tempesta DB Apr 26 05:30:36 192.168.122.209 [48386.782568] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:30:37 192.168.122.209 [48387.486990] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48387.486990] Maybe that's fine, but it's worth checking the [48387.486990] config - if there is no relations between the [48387.486990] names, then host name confusion attack is possible. Apr 26 05:30:37 192.168.122.209 [48387.630030] [tempesta fw] Configuration processing is completed. Apr 26 05:30:37 192.168.122.209 [48387.685479] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:30:37 192.168.122.209 [48387.715382] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:30:37 192.168.122.209 [48387.742214] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:30:37 192.168.122.209 [48387.785969] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:30:37 192.168.122.209 [48387.829971] [tempesta fw] Tempesta FW is ready Apr 26 05:30:38 192.168.122.209 [48388.437712] [tdb] Close table 'client0.tdb' Apr 26 05:30:38 192.168.122.209 [48388.634657] [tdb] Close table 'sessions0.tdb' Apr 26 05:30:38 192.168.122.209 [48388.882700] [tdb] Close table 'filter0.tdb' Apr 26 05:30:38 192.168.122.209 [48388.883150] net_ratelimit: 1 callbacks suppressed Apr 26 05:30:38 192.168.122.209 [48388.883151] [tempesta fw] modules are stopped Apr 26 05:30:38 192.168.122.209 [48389.098947] [tempesta fw] exiting... Apr 26 05:30:38 192.168.122.209 [48389.239059] [tdb] Shutdown Tempesta DB Apr 26 05:30:39 192.168.122.209 [48389.465382] End test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_content_range Apr 26 05:30:39 192.168.122.209 [48389.475776] Start test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_content_type Apr 26 05:30:40 192.168.122.209 [48390.584089] [tdb] Start Tempesta DB Apr 26 05:30:40 192.168.122.209 [48390.740833] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:30:41 192.168.122.209 [48391.431420] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48391.431420] Maybe that's fine, but it's worth checking the [48391.431420] config - if there is no relations between the [48391.431420] names, then host name confusion attack is possible. Apr 26 05:30:41 192.168.122.209 [48391.594152] [tempesta fw] Configuration processing is completed. Apr 26 05:30:41 192.168.122.209 [48391.645286] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:30:41 192.168.122.209 [48391.673946] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:30:41 192.168.122.209 [48391.700908] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:30:41 192.168.122.209 [48391.762152] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:30:41 192.168.122.209 [48391.765330] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:30:41 192.168.122.209 [48391.826005] [tempesta fw] Tempesta FW is ready Apr 26 05:30:42 192.168.122.209 [48392.416987] [tdb] Close table 'client0.tdb' Apr 26 05:30:42 192.168.122.209 [48392.609829] [tdb] Close table 'sessions0.tdb' Apr 26 05:30:42 192.168.122.209 [48392.853565] [tdb] Close table 'filter0.tdb' Apr 26 05:30:42 192.168.122.209 [48392.854411] [tempesta fw] modules are stopped Apr 26 05:30:42 192.168.122.209 [48393.061512] [tempesta fw] exiting... Apr 26 05:30:42 192.168.122.209 [48393.165253] [tdb] Shutdown Tempesta DB Apr 26 05:30:42 192.168.122.209 [48393.376764] End test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_content_type Apr 26 05:30:42 192.168.122.209 [48393.389980] Start test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_date Apr 26 05:30:44 192.168.122.209 [48394.455377] [tdb] Start Tempesta DB Apr 26 05:30:44 192.168.122.209 [48394.598803] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:30:44 192.168.122.209 [48395.263685] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48395.263685] Maybe that's fine, but it's worth checking the [48395.263685] config - if there is no relations between the [48395.263685] names, then host name confusion attack is possible. Apr 26 05:30:45 192.168.122.209 [48395.426124] [tempesta fw] Configuration processing is completed. Apr 26 05:30:45 192.168.122.209 [48395.483433] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:30:45 192.168.122.209 [48395.513637] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:30:45 192.168.122.209 [48395.540446] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:30:45 192.168.122.209 [48395.602104] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:30:45 192.168.122.209 [48395.603833] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:30:45 192.168.122.209 [48395.650064] [tempesta fw] Tempesta FW is ready Apr 26 05:30:45 192.168.122.209 [48396.238501] [tdb] Close table 'client0.tdb' Apr 26 05:30:46 192.168.122.209 [48396.445249] [tdb] Close table 'sessions0.tdb' Apr 26 05:30:46 192.168.122.209 [48396.698792] [tdb] Close table 'filter0.tdb' Apr 26 05:30:46 192.168.122.209 [48396.699337] [tempesta fw] modules are stopped Apr 26 05:30:46 192.168.122.209 [48396.940410] [tempesta fw] exiting... Apr 26 05:30:46 192.168.122.209 [48397.068206] [tdb] Shutdown Tempesta DB Apr 26 05:30:46 192.168.122.209 [48397.268615] End test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_date Apr 26 05:30:46 192.168.122.209 [48397.281835] Start test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_expires Apr 26 05:30:47 192.168.122.209 [48398.396721] [tdb] Start Tempesta DB Apr 26 05:30:48 192.168.122.209 [48398.557086] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:30:48 192.168.122.209 [48399.219472] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48399.219472] Maybe that's fine, but it's worth checking the [48399.219472] config - if there is no relations between the [48399.219472] names, then host name confusion attack is possible. Apr 26 05:30:48 192.168.122.209 [48399.378182] [tempesta fw] Configuration processing is completed. Apr 26 05:30:49 192.168.122.209 [48399.433380] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:30:49 192.168.122.209 [48399.465721] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:30:49 192.168.122.209 [48399.496103] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:30:49 192.168.122.209 [48399.534178] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:30:49 192.168.122.209 [48399.582121] [tempesta fw] Tempesta FW is ready Apr 26 05:30:49 192.168.122.209 [48400.171491] [tdb] Close table 'client0.tdb' Apr 26 05:30:49 192.168.122.209 [48400.362133] [tdb] Close table 'sessions0.tdb' Apr 26 05:30:50 192.168.122.209 [48400.618362] [tdb] Close table 'filter0.tdb' Apr 26 05:30:50 192.168.122.209 [48400.618877] net_ratelimit: 1 callbacks suppressed Apr 26 05:30:50 192.168.122.209 [48400.618878] [tempesta fw] modules are stopped Apr 26 05:30:50 192.168.122.209 [48400.800055] [tempesta fw] exiting... Apr 26 05:30:50 192.168.122.209 [48400.928518] [tdb] Shutdown Tempesta DB Apr 26 05:30:50 192.168.122.209 [48401.158252] End test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_expires Apr 26 05:30:50 192.168.122.209 [48401.175051] Start test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_last_modified Apr 26 05:30:51 192.168.122.209 [48402.289544] [tdb] Start Tempesta DB Apr 26 05:30:52 192.168.122.209 [48402.448460] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:30:52 192.168.122.209 [48403.170822] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48403.170822] Maybe that's fine, but it's worth checking the [48403.170822] config - if there is no relations between the [48403.170822] names, then host name confusion attack is possible. Apr 26 05:30:52 192.168.122.209 [48403.346237] [tempesta fw] Configuration processing is completed. Apr 26 05:30:52 192.168.122.209 [48403.395154] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:30:53 192.168.122.209 [48403.425959] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:30:53 192.168.122.209 [48403.453334] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:30:53 192.168.122.209 [48403.494205] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:30:53 192.168.122.209 [48403.495614] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:30:53 192.168.122.209 [48403.534183] [tempesta fw] Tempesta FW is ready Apr 26 05:30:53 192.168.122.209 [48404.113350] [tdb] Close table 'client0.tdb' Apr 26 05:30:53 192.168.122.209 [48404.313743] [tdb] Close table 'sessions0.tdb' Apr 26 05:30:54 192.168.122.209 [48404.571691] [tdb] Close table 'filter0.tdb' Apr 26 05:30:54 192.168.122.209 [48404.572146] [tempesta fw] modules are stopped Apr 26 05:30:54 192.168.122.209 [48404.787637] [tempesta fw] exiting... Apr 26 05:30:54 192.168.122.209 [48404.912506] [tdb] Shutdown Tempesta DB Apr 26 05:30:54 192.168.122.209 [48405.124296] End test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_last_modified Apr 26 05:30:54 192.168.122.209 [48405.147045] Start test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_location Apr 26 05:30:55 192.168.122.209 [48406.271574] [tdb] Start Tempesta DB Apr 26 05:30:55 192.168.122.209 [48406.409624] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:30:56 192.168.122.209 [48407.055569] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48407.055569] Maybe that's fine, but it's worth checking the [48407.055569] config - if there is no relations between the [48407.055569] names, then host name confusion attack is possible. Apr 26 05:30:56 192.168.122.209 [48407.222245] [tempesta fw] Configuration processing is completed. Apr 26 05:30:56 192.168.122.209 [48407.284115] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:30:56 192.168.122.209 [48407.314620] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:30:56 192.168.122.209 [48407.344174] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:30:56 192.168.122.209 [48407.394250] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:30:56 192.168.122.209 [48407.395674] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:30:57 192.168.122.209 [48407.434125] [tempesta fw] Tempesta FW is ready Apr 26 05:30:57 192.168.122.209 [48408.075181] [tdb] Close table 'client0.tdb' Apr 26 05:30:57 192.168.122.209 [48408.258100] [tdb] Close table 'sessions0.tdb' Apr 26 05:30:58 192.168.122.209 [48408.495383] [tdb] Close table 'filter0.tdb' Apr 26 05:30:58 192.168.122.209 [48408.495815] [tempesta fw] modules are stopped Apr 26 05:30:58 192.168.122.209 [48408.748431] [tempesta fw] exiting... Apr 26 05:30:58 192.168.122.209 [48408.912489] [tdb] Shutdown Tempesta DB Apr 26 05:30:58 192.168.122.209 [48409.107637] End test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_location Apr 26 05:30:58 192.168.122.209 [48409.128861] Start test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_retry_after Apr 26 05:30:59 192.168.122.209 [48410.224251] [tdb] Start Tempesta DB Apr 26 05:30:59 192.168.122.209 [48410.371685] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:31:00 192.168.122.209 [48411.110706] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48411.110706] Maybe that's fine, but it's worth checking the [48411.110706] config - if there is no relations between the [48411.110706] names, then host name confusion attack is possible. Apr 26 05:31:00 192.168.122.209 [48411.254346] [tempesta fw] Configuration processing is completed. Apr 26 05:31:00 192.168.122.209 [48411.315193] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:31:00 192.168.122.209 [48411.354758] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:31:00 192.168.122.209 [48411.389322] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:31:01 192.168.122.209 [48411.458359] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:31:01 192.168.122.209 [48411.460131] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:31:01 192.168.122.209 [48411.506263] [tempesta fw] Tempesta FW is ready Apr 26 05:31:01 192.168.122.209 [48412.050113] [tdb] Close table 'client0.tdb' Apr 26 05:31:01 192.168.122.209 [48412.236835] [tdb] Close table 'sessions0.tdb' Apr 26 05:31:02 192.168.122.209 [48412.447391] [tdb] Close table 'filter0.tdb' Apr 26 05:31:02 192.168.122.209 [48412.447837] [tempesta fw] modules are stopped Apr 26 05:31:02 192.168.122.209 [48412.646080] [tempesta fw] exiting... Apr 26 05:31:02 192.168.122.209 [48412.764453] [tdb] Shutdown Tempesta DB Apr 26 05:31:02 192.168.122.209 [48412.981641] End test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_retry_after Apr 26 05:31:02 192.168.122.209 [48412.992828] Start test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_server Apr 26 05:31:03 192.168.122.209 [48414.134492] [tdb] Start Tempesta DB Apr 26 05:31:03 192.168.122.209 [48414.284705] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:31:04 192.168.122.209 [48415.011010] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48415.011010] Maybe that's fine, but it's worth checking the [48415.011010] config - if there is no relations between the [48415.011010] names, then host name confusion attack is possible. Apr 26 05:31:04 192.168.122.209 [48415.166372] [tempesta fw] Configuration processing is completed. Apr 26 05:31:04 192.168.122.209 [48415.217118] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:31:04 192.168.122.209 [48415.245046] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:31:04 192.168.122.209 [48415.272085] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:31:04 192.168.122.209 [48415.322376] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:31:04 192.168.122.209 [48415.324087] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:31:04 192.168.122.209 [48415.366326] [tempesta fw] Tempesta FW is ready Apr 26 05:31:05 192.168.122.209 [48415.929778] [tdb] Close table 'client0.tdb' Apr 26 05:31:05 192.168.122.209 [48416.122028] [tdb] Close table 'sessions0.tdb' Apr 26 05:31:05 192.168.122.209 [48416.349774] [tdb] Close table 'filter0.tdb' Apr 26 05:31:05 192.168.122.209 [48416.350215] [tempesta fw] modules are stopped Apr 26 05:31:06 192.168.122.209 [48416.515476] [tempesta fw] exiting... Apr 26 05:31:06 192.168.122.209 [48416.620015] [tdb] Shutdown Tempesta DB Apr 26 05:31:06 192.168.122.209 [48416.849041] End test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_server Apr 26 05:31:06 192.168.122.209 [48416.860197] Start test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_vary Apr 26 05:31:07 192.168.122.209 [48417.988984] [tdb] Start Tempesta DB Apr 26 05:31:07 192.168.122.209 [48418.170634] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:31:08 192.168.122.209 [48418.851680] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48418.851680] Maybe that's fine, but it's worth checking the [48418.851680] config - if there is no relations between the [48418.851680] names, then host name confusion attack is possible. Apr 26 05:31:08 192.168.122.209 [48419.014420] [tempesta fw] Configuration processing is completed. Apr 26 05:31:08 192.168.122.209 [48419.065233] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:31:08 192.168.122.209 [48419.094835] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:31:08 192.168.122.209 [48419.121619] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:31:08 192.168.122.209 [48419.182426] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:31:08 192.168.122.209 [48419.184621] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:31:08 192.168.122.209 [48419.222224] [tempesta fw] Tempesta FW is ready Apr 26 05:31:09 192.168.122.209 [48419.809828] [tdb] Close table 'client0.tdb' Apr 26 05:31:09 192.168.122.209 [48420.002090] [tdb] Close table 'sessions0.tdb' Apr 26 05:31:09 192.168.122.209 [48420.249856] [tdb] Close table 'filter0.tdb' Apr 26 05:31:09 192.168.122.209 [48420.250316] [tempesta fw] modules are stopped Apr 26 05:31:10 192.168.122.209 [48420.429574] [tempesta fw] exiting... Apr 26 05:31:10 192.168.122.209 [48420.557750] [tdb] Shutdown Tempesta DB Apr 26 05:31:10 192.168.122.209 [48420.792141] End test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_vary Apr 26 05:31:10 192.168.122.209 [48420.815037] Start test: t_malformed.test_malformed_headers.MalformedResponsesTest.test_age Apr 26 05:31:11 192.168.122.209 [48421.872435] [tdb] Start Tempesta DB Apr 26 05:31:11 192.168.122.209 [48422.026756] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:31:12 192.168.122.209 [48422.751664] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48422.751664] Maybe that's fine, but it's worth checking the [48422.751664] config - if there is no relations between the [48422.751664] names, then host name confusion attack is possible. Apr 26 05:31:12 192.168.122.209 [48422.910462] [tempesta fw] Configuration processing is completed. Apr 26 05:31:12 192.168.122.209 [48422.963797] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:31:12 192.168.122.209 [48422.992561] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:31:12 192.168.122.209 [48423.034559] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:31:12 192.168.122.209 [48423.078454] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:31:12 192.168.122.209 [48423.122407] [tempesta fw] Tempesta FW is ready Apr 26 05:31:12 192.168.122.209 [48423.272469] net_ratelimit: 1 callbacks suppressed Apr 26 05:31:12 192.168.122.209 [48423.272474] [tempesta fw] Warning: Parser error: state=Resp_HdrAgeV input(-8)=0x69('K [48423.272474] Age: invalid [48423.272474] Content-Length: 0 [48423.272474] [48423.272474] ') data_len=52 off=22 Apr 26 05:31:12 192.168.122.209 [48423.275066] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 05:31:13 192.168.122.209 [48423.734477] [tdb] Close table 'client0.tdb' Apr 26 05:31:13 192.168.122.209 [48423.923911] [tdb] Close table 'sessions0.tdb' Apr 26 05:31:13 192.168.122.209 [48424.169004] [tdb] Close table 'filter0.tdb' Apr 26 05:31:13 192.168.122.209 [48424.169457] [tempesta fw] modules are stopped Apr 26 05:31:13 192.168.122.209 [48424.387548] [tempesta fw] exiting... Apr 26 05:31:14 192.168.122.209 [48424.536362] [tdb] Shutdown Tempesta DB Apr 26 05:31:14 192.168.122.209 [48424.726053] End test: t_malformed.test_malformed_headers.MalformedResponsesTest.test_age Apr 26 05:31:14 192.168.122.209 [48424.734587] Start test: t_malformed.test_malformed_headers.MalformedResponsesTest.test_cache_control1 Apr 26 05:31:15 192.168.122.209 [48425.837380] [tdb] Start Tempesta DB Apr 26 05:31:15 192.168.122.209 [48425.987240] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:31:16 192.168.122.209 [48426.667797] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48426.667797] Maybe that's fine, but it's worth checking the [48426.667797] config - if there is no relations between the [48426.667797] names, then host name confusion attack is possible. Apr 26 05:31:16 192.168.122.209 [48426.818827] [tempesta fw] Configuration processing is completed. Apr 26 05:31:16 192.168.122.209 [48426.879130] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:31:16 192.168.122.209 [48426.925034] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:31:16 192.168.122.209 [48426.960947] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:31:16 192.168.122.209 [48427.006537] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:31:16 192.168.122.209 [48427.007921] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:31:16 192.168.122.209 [48427.050465] [tempesta fw] Tempesta FW is ready Apr 26 05:31:16 192.168.122.209 [48427.185695] [tempesta fw] Warning: Parser error: state=Resp_HdrCache_CtrlV input(-8)=0x6e('ontrol: not a token [48427.185695] Content-Length: 0 [48427.185695] [48427.185695] ') data_len=66 off=32 Apr 26 05:31:16 192.168.122.209 [48427.187677] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 05:31:17 192.168.122.209 [48427.596231] [tdb] Close table 'client0.tdb' Apr 26 05:31:17 192.168.122.209 [48427.810755] [tdb] Close table 'sessions0.tdb' Apr 26 05:31:17 192.168.122.209 [48428.041954] [tdb] Close table 'filter0.tdb' Apr 26 05:31:17 192.168.122.209 [48428.275299] [tempesta fw] exiting... Apr 26 05:31:17 192.168.122.209 [48428.392950] [tdb] Shutdown Tempesta DB Apr 26 05:31:18 192.168.122.209 [48428.607398] End test: t_malformed.test_malformed_headers.MalformedResponsesTest.test_cache_control1 Apr 26 05:31:18 192.168.122.209 [48428.622643] Start test: t_malformed.test_malformed_headers.MalformedResponsesTest.test_cache_control2 Apr 26 05:31:19 192.168.122.209 [48429.722097] [tdb] Start Tempesta DB Apr 26 05:31:19 192.168.122.209 [48429.884684] net_ratelimit: 1 callbacks suppressed Apr 26 05:31:19 192.168.122.209 [48429.884686] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:31:20 192.168.122.209 [48430.611181] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48430.611181] Maybe that's fine, but it's worth checking the [48430.611181] config - if there is no relations between the [48430.611181] names, then host name confusion attack is possible. Apr 26 05:31:20 192.168.122.209 [48430.762613] [tempesta fw] Configuration processing is completed. Apr 26 05:31:20 192.168.122.209 [48430.822811] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:31:20 192.168.122.209 [48430.850743] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:31:20 192.168.122.209 [48430.878201] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:31:20 192.168.122.209 [48430.938560] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:31:20 192.168.122.209 [48430.940294] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:31:20 192.168.122.209 [48430.991040] [tempesta fw] Tempesta FW is ready Apr 26 05:31:20 192.168.122.209 [48431.109132] [tempesta fw] Warning: Parser error: state=Resp_HdrCache_CtrlV input(-8)=0x6d('ontrol: max-age=text [48431.109132] Content-Length: 0 [48431.109132] [48431.109132] ') data_len=67 off=32 Apr 26 05:31:20 192.168.122.209 [48431.114069] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 05:31:21 192.168.122.209 [48431.537266] [tdb] Close table 'client0.tdb' Apr 26 05:31:21 192.168.122.209 [48431.726648] [tdb] Close table 'sessions0.tdb' Apr 26 05:31:21 192.168.122.209 [48431.957414] [tdb] Close table 'filter0.tdb' Apr 26 05:31:21 192.168.122.209 [48431.957846] [tempesta fw] modules are stopped Apr 26 05:31:21 192.168.122.209 [48432.141935] [tempesta fw] exiting... Apr 26 05:31:21 192.168.122.209 [48432.252145] [tdb] Shutdown Tempesta DB Apr 26 05:31:22 192.168.122.209 [48432.464717] End test: t_malformed.test_malformed_headers.MalformedResponsesTest.test_cache_control2 Apr 26 05:31:22 192.168.122.209 [48432.478660] Start test: t_malformed.test_malformed_headers.MalformedResponsesTest.test_missing_name Apr 26 05:31:23 192.168.122.209 [48433.583407] [tdb] Start Tempesta DB Apr 26 05:31:23 192.168.122.209 [48433.707276] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:31:23 192.168.122.209 [48434.391815] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48434.391815] Maybe that's fine, but it's worth checking the [48434.391815] config - if there is no relations between the [48434.391815] names, then host name confusion attack is possible. Apr 26 05:31:24 192.168.122.209 [48434.599912] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:31:24 192.168.122.209 [48434.630767] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:31:24 192.168.122.209 [48434.658094] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:31:24 192.168.122.209 [48434.738565] [tempesta fw] Tempesta FW is ready Apr 26 05:31:24 192.168.122.209 [48435.318219] [tdb] Close table 'client0.tdb' Apr 26 05:31:25 192.168.122.209 [48435.504363] [tdb] Close table 'sessions0.tdb' Apr 26 05:31:25 192.168.122.209 [48435.749755] [tdb] Close table 'filter0.tdb' Apr 26 05:31:25 192.168.122.209 [48435.750210] net_ratelimit: 5 callbacks suppressed Apr 26 05:31:25 192.168.122.209 [48435.750211] [tempesta fw] modules are stopped Apr 26 05:31:25 192.168.122.209 [48435.939197] [tempesta fw] exiting... Apr 26 05:31:25 192.168.122.209 [48436.032799] [tdb] Shutdown Tempesta DB Apr 26 05:31:25 192.168.122.209 [48436.237799] End test: t_malformed.test_malformed_headers.MalformedResponsesTest.test_missing_name Apr 26 05:31:25 192.168.122.209 [48436.250739] Start test: t_malformed.test_malformed_structure.MalformedStructureTest.test_crSPlf Apr 26 05:31:26 192.168.122.209 [48437.380824] [tdb] Start Tempesta DB Apr 26 05:31:27 192.168.122.209 [48437.518168] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:31:27 192.168.122.209 [48438.114709] [tempesta fw] Configuration processing is completed. Apr 26 05:31:27 192.168.122.209 [48438.165893] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:31:27 192.168.122.209 [48438.193909] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:31:27 192.168.122.209 [48438.220583] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:31:27 192.168.122.209 [48438.270636] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:31:27 192.168.122.209 [48438.314587] [tempesta fw] Tempesta FW is ready Apr 26 05:31:28 192.168.122.209 [48438.454871] [tempesta fw] Warning: Parser error: state=RGen_CR input(-8)=0x20('calhost [48438.454871] [48438.454871] ') data_len=36 off=32 Apr 26 05:31:28 192.168.122.209 [48438.870710] [tdb] Close table 'client0.tdb' Apr 26 05:31:28 192.168.122.209 [48439.060443] [tdb] Close table 'sessions0.tdb' Apr 26 05:31:28 192.168.122.209 [48439.296351] [tdb] Close table 'filter0.tdb' Apr 26 05:31:28 192.168.122.209 [48439.296789] [tempesta fw] modules are stopped Apr 26 05:31:29 192.168.122.209 [48439.459726] [tempesta fw] exiting... Apr 26 05:31:29 192.168.122.209 [48439.595245] [tdb] Shutdown Tempesta DB Apr 26 05:31:29 192.168.122.209 [48439.792790] End test: t_malformed.test_malformed_structure.MalformedStructureTest.test_crSPlf Apr 26 05:31:29 192.168.122.209 [48439.803321] Start test: t_malformed.test_malformed_structure.MalformedStructureTest.test_lfcr Apr 26 05:31:30 192.168.122.209 [48440.968918] [tdb] Start Tempesta DB Apr 26 05:31:30 192.168.122.209 [48441.140999] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:31:31 192.168.122.209 [48441.774764] [tempesta fw] Configuration processing is completed. Apr 26 05:31:31 192.168.122.209 [48441.835262] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:31:31 192.168.122.209 [48441.864403] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:31:31 192.168.122.209 [48441.892210] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:31:31 192.168.122.209 [48441.930620] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:31:31 192.168.122.209 [48441.974655] [tempesta fw] Tempesta FW is ready Apr 26 05:31:31 192.168.122.209 [48442.091391] [tempesta fw] Warning: Parser error: state=RGen_CRLFCR input(-8)=0x48('TP/1.1 [48442.091391] Host: localhost [48442.091391] [48442.091391] ') data_len=35 off=16 Apr 26 05:31:32 192.168.122.209 [48442.551239] [tdb] Close table 'client0.tdb' Apr 26 05:31:32 192.168.122.209 [48442.737459] [tdb] Close table 'sessions0.tdb' Apr 26 05:31:32 192.168.122.209 [48442.970916] [tdb] Close table 'filter0.tdb' Apr 26 05:31:32 192.168.122.209 [48442.971379] [tempesta fw] modules are stopped Apr 26 05:31:32 192.168.122.209 [48443.219399] [tempesta fw] exiting... Apr 26 05:31:32 192.168.122.209 [48443.360677] [tdb] Shutdown Tempesta DB Apr 26 05:31:33 192.168.122.209 [48443.569735] End test: t_malformed.test_malformed_structure.MalformedStructureTest.test_lfcr Apr 26 05:31:33 192.168.122.209 [48443.591188] Start test: t_malformed.test_malformed_structure.MalformedStructureTest.test_space Apr 26 05:31:34 192.168.122.209 [48444.688945] [tdb] Start Tempesta DB Apr 26 05:31:34 192.168.122.209 [48444.845058] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:31:35 192.168.122.209 [48445.427257] [tempesta fw] Configuration processing is completed. Apr 26 05:31:35 192.168.122.209 [48445.478647] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:31:35 192.168.122.209 [48445.507674] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 05:31:35 192.168.122.209 [48445.535509] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 05:31:35 192.168.122.209 [48445.582733] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:31:35 192.168.122.209 [48445.642709] [tempesta fw] Tempesta FW is ready Apr 26 05:31:35 192.168.122.209 [48445.786970] [tempesta fw] Warning: Parser error: state=RGen_HdrOtherN input(-8)=0x20('.1 [48445.786970] Host : localhost [48445.786970] [48445.786970] ') data_len=36 off=20 Apr 26 05:31:35 192.168.122.209 [48446.190353] [tdb] Close table 'client0.tdb' Apr 26 05:31:35 192.168.122.209 [48446.369477] [tdb] Close table 'sessions0.tdb' Apr 26 05:31:36 192.168.122.209 [48446.594931] [tdb] Close table 'filter0.tdb' Apr 26 05:31:36 192.168.122.209 [48446.595361] [tempesta fw] modules are stopped Apr 26 05:31:36 192.168.122.209 [48446.782671] [tempesta fw] exiting... Apr 26 05:31:36 192.168.122.209 [48446.917313] [tdb] Shutdown Tempesta DB Apr 26 05:31:36 192.168.122.209 [48447.143686] End test: t_malformed.test_malformed_structure.MalformedStructureTest.test_space Apr 26 05:31:36 192.168.122.209 [48447.165407] Start test: t_modify_http_headers.test_common_config.TestCachedRespAddHeader.test_add_hdrs_derive_config Apr 26 05:31:37 192.168.122.209 [48448.270076] [tdb] Start Tempesta DB Apr 26 05:31:37 192.168.122.209 [48448.406076] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:31:38 192.168.122.209 [48449.088121] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48449.088121] Maybe that's fine, but it's worth checking the [48449.088121] config - if there is no relations between the [48449.088121] names, then host name confusion attack is possible. Apr 26 05:31:38 192.168.122.209 [48449.242885] [tempesta fw] Configuration processing is completed. Apr 26 05:31:38 192.168.122.209 [48449.305394] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:31:39 192.168.122.209 [48450.156687] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:31:39 192.168.122.209 [48450.213756] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:31:39 192.168.122.209 [48450.270470] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:31:39 192.168.122.209 [48450.338834] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:31:39 192.168.122.209 [48450.340583] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:31:39 192.168.122.209 [48450.378767] [tempesta fw] Tempesta FW is ready Apr 26 05:31:40 192.168.122.209 [48450.977304] [tdb] Close table 'client0.tdb' Apr 26 05:31:40 192.168.122.209 [48451.165068] [tdb] Close table 'sessions0.tdb' Apr 26 05:31:43 192.168.122.209 [48454.385254] [tdb] Close table 'cache0.tdb' Apr 26 05:31:44 192.168.122.209 [48454.602059] [tdb] Close table 'filter0.tdb' Apr 26 05:31:44 192.168.122.209 [48454.602507] [tempesta fw] modules are stopped Apr 26 05:31:44 192.168.122.209 [48454.783065] [tempesta fw] exiting... Apr 26 05:31:44 192.168.122.209 [48454.939644] [tdb] Shutdown Tempesta DB Apr 26 05:31:44 192.168.122.209 [48455.167415] End test: t_modify_http_headers.test_common_config.TestCachedRespAddHeader.test_add_hdrs_derive_config Apr 26 05:31:44 192.168.122.209 [48455.179943] Start test: t_modify_http_headers.test_common_config.TestCachedRespAddHeader.test_add_hdrs_override_config Apr 26 05:31:45 192.168.122.209 [48456.280959] [tdb] Start Tempesta DB Apr 26 05:31:46 192.168.122.209 [48456.416686] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:31:47 192.168.122.209 [48457.960129] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48457.960129] Maybe that's fine, but it's worth checking the [48457.960129] config - if there is no relations between the [48457.960129] names, then host name confusion attack is possible. Apr 26 05:31:47 192.168.122.209 [48458.114930] [tempesta fw] Configuration processing is completed. Apr 26 05:31:47 192.168.122.209 [48458.177477] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:31:48 192.168.122.209 [48458.714638] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:31:48 192.168.122.209 [48458.787887] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:31:48 192.168.122.209 [48458.823393] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:31:48 192.168.122.209 [48458.878855] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:31:48 192.168.122.209 [48458.880617] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:31:48 192.168.122.209 [48458.926882] [tempesta fw] Tempesta FW is ready Apr 26 05:31:49 192.168.122.209 [48459.495533] [tdb] Close table 'client0.tdb' Apr 26 05:31:49 192.168.122.209 [48459.693183] [tdb] Close table 'sessions0.tdb' Apr 26 05:31:52 192.168.122.209 [48462.912953] [tdb] Close table 'cache0.tdb' Apr 26 05:31:52 192.168.122.209 [48463.144368] [tdb] Close table 'filter0.tdb' Apr 26 05:31:52 192.168.122.209 [48463.144805] [tempesta fw] modules are stopped Apr 26 05:31:52 192.168.122.209 [48463.368739] [tempesta fw] exiting... Apr 26 05:31:53 192.168.122.209 [48463.499110] [tdb] Shutdown Tempesta DB Apr 26 05:31:53 192.168.122.209 [48463.722254] End test: t_modify_http_headers.test_common_config.TestCachedRespAddHeader.test_add_hdrs_override_config Apr 26 05:31:53 192.168.122.209 [48463.751182] Start test: t_modify_http_headers.test_common_config.TestCachedRespAddHeader.test_add_some_hdrs Apr 26 05:31:54 192.168.122.209 [48464.870013] [tdb] Start Tempesta DB Apr 26 05:31:54 192.168.122.209 [48465.005654] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:31:56 192.168.122.209 [48466.492247] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48466.492247] Maybe that's fine, but it's worth checking the [48466.492247] config - if there is no relations between the [48466.492247] names, then host name confusion attack is possible. Apr 26 05:31:56 192.168.122.209 [48466.639030] [tempesta fw] Configuration processing is completed. Apr 26 05:31:56 192.168.122.209 [48466.692045] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:31:56 192.168.122.209 [48467.142179] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:31:56 192.168.122.209 [48467.169607] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:31:56 192.168.122.209 [48467.199815] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:31:56 192.168.122.209 [48467.267018] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:31:56 192.168.122.209 [48467.268745] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:31:56 192.168.122.209 [48467.314964] [tempesta fw] Tempesta FW is ready Apr 26 05:31:57 192.168.122.209 [48467.866122] [tdb] Close table 'client0.tdb' Apr 26 05:31:57 192.168.122.209 [48468.054081] [tdb] Close table 'sessions0.tdb' Apr 26 05:32:00 192.168.122.209 [48471.321629] [tdb] Close table 'cache0.tdb' Apr 26 05:32:01 192.168.122.209 [48471.565686] [tdb] Close table 'filter0.tdb' Apr 26 05:32:01 192.168.122.209 [48471.566118] [tempesta fw] modules are stopped Apr 26 05:32:01 192.168.122.209 [48471.764775] [tempesta fw] exiting... Apr 26 05:32:01 192.168.122.209 [48471.917361] [tdb] Shutdown Tempesta DB Apr 26 05:32:01 192.168.122.209 [48472.126942] End test: t_modify_http_headers.test_common_config.TestCachedRespAddHeader.test_add_some_hdrs Apr 26 05:32:01 192.168.122.209 [48472.140307] Start test: t_modify_http_headers.test_common_config.TestCachedRespAddHeader.test_add_some_hdrs_custom_location Apr 26 05:32:02 192.168.122.209 [48473.252163] [tdb] Start Tempesta DB Apr 26 05:32:02 192.168.122.209 [48473.404114] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:32:04 192.168.122.209 [48474.908360] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48474.908360] Maybe that's fine, but it's worth checking the [48474.908360] config - if there is no relations between the [48474.908360] names, then host name confusion attack is possible. Apr 26 05:32:04 192.168.122.209 [48475.043124] [tempesta fw] Configuration processing is completed. Apr 26 05:32:04 192.168.122.209 [48475.093744] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:32:05 192.168.122.209 [48475.515794] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:32:05 192.168.122.209 [48475.576718] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:32:05 192.168.122.209 [48475.610357] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:32:05 192.168.122.209 [48475.654999] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:32:05 192.168.122.209 [48475.656329] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:32:05 192.168.122.209 [48475.699073] [tempesta fw] Tempesta FW is ready Apr 26 05:32:05 192.168.122.209 [48476.318445] [tdb] Close table 'client0.tdb' Apr 26 05:32:06 192.168.122.209 [48476.508691] [tdb] Close table 'sessions0.tdb' Apr 26 05:32:09 192.168.122.209 [48479.761223] [tdb] Close table 'cache0.tdb' Apr 26 05:32:09 192.168.122.209 [48479.978733] [tdb] Close table 'filter0.tdb' Apr 26 05:32:09 192.168.122.209 [48479.979180] [tempesta fw] modules are stopped Apr 26 05:32:09 192.168.122.209 [48480.196368] [tempesta fw] exiting... Apr 26 05:32:09 192.168.122.209 [48480.339992] [tdb] Shutdown Tempesta DB Apr 26 05:32:10 192.168.122.209 [48480.565569] End test: t_modify_http_headers.test_common_config.TestCachedRespAddHeader.test_add_some_hdrs_custom_location Apr 26 05:32:10 192.168.122.209 [48480.589079] Start test: t_modify_http_headers.test_common_config.TestCachedRespSetHeader.test_add_hdrs_derive_config Apr 26 05:32:11 192.168.122.209 [48481.674153] [tdb] Start Tempesta DB Apr 26 05:32:11 192.168.122.209 [48481.809836] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:32:12 192.168.122.209 [48483.268078] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48483.268078] Maybe that's fine, but it's worth checking the [48483.268078] config - if there is no relations between the [48483.268078] names, then host name confusion attack is possible. Apr 26 05:32:13 192.168.122.209 [48483.419259] [tempesta fw] Configuration processing is completed. Apr 26 05:32:13 192.168.122.209 [48483.479159] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:32:13 192.168.122.209 [48483.935386] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:32:13 192.168.122.209 [48483.994729] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:32:13 192.168.122.209 [48484.029646] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:32:13 192.168.122.209 [48484.075127] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:32:13 192.168.122.209 [48484.076505] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:32:13 192.168.122.209 [48484.123163] [tempesta fw] Tempesta FW is ready Apr 26 05:32:14 192.168.122.209 [48484.702484] [tdb] Close table 'client0.tdb' Apr 26 05:32:14 192.168.122.209 [48484.889042] [tdb] Close table 'sessions0.tdb' Apr 26 05:32:17 192.168.122.209 [48488.205799] [tdb] Close table 'cache0.tdb' Apr 26 05:32:18 192.168.122.209 [48488.458783] [tdb] Close table 'filter0.tdb' Apr 26 05:32:18 192.168.122.209 [48488.459235] [tempesta fw] modules are stopped Apr 26 05:32:18 192.168.122.209 [48488.665669] [tempesta fw] exiting... Apr 26 05:32:18 192.168.122.209 [48488.786264] [tdb] Shutdown Tempesta DB Apr 26 05:32:18 192.168.122.209 [48489.031008] End test: t_modify_http_headers.test_common_config.TestCachedRespSetHeader.test_add_hdrs_derive_config Apr 26 05:32:18 192.168.122.209 [48489.044347] Start test: t_modify_http_headers.test_common_config.TestCachedRespSetHeader.test_add_hdrs_override_config Apr 26 05:32:19 192.168.122.209 [48490.222026] [tdb] Start Tempesta DB Apr 26 05:32:19 192.168.122.209 [48490.368900] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:32:21 192.168.122.209 [48491.912858] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48491.912858] Maybe that's fine, but it's worth checking the [48491.912858] config - if there is no relations between the [48491.912858] names, then host name confusion attack is possible. Apr 26 05:32:21 192.168.122.209 [48492.067389] [tempesta fw] Configuration processing is completed. Apr 26 05:32:21 192.168.122.209 [48492.121520] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:32:22 192.168.122.209 [48492.614027] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:32:22 192.168.122.209 [48492.648382] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:32:22 192.168.122.209 [48492.682423] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:32:22 192.168.122.209 [48492.727310] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:32:22 192.168.122.209 [48492.728694] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:32:22 192.168.122.209 [48492.767317] [tempesta fw] Tempesta FW is ready Apr 26 05:32:22 192.168.122.209 [48493.363067] [tdb] Close table 'client0.tdb' Apr 26 05:32:23 192.168.122.209 [48493.563076] [tdb] Close table 'sessions0.tdb' Apr 26 05:32:26 192.168.122.209 [48496.941398] [tdb] Close table 'cache0.tdb' Apr 26 05:32:26 192.168.122.209 [48497.184340] [tdb] Close table 'filter0.tdb' Apr 26 05:32:26 192.168.122.209 [48497.184797] [tempesta fw] modules are stopped Apr 26 05:32:26 192.168.122.209 [48497.398390] [tempesta fw] exiting... Apr 26 05:32:27 192.168.122.209 [48497.523632] [tdb] Shutdown Tempesta DB Apr 26 05:32:27 192.168.122.209 [48497.747334] End test: t_modify_http_headers.test_common_config.TestCachedRespSetHeader.test_add_hdrs_override_config Apr 26 05:32:27 192.168.122.209 [48497.758815] Start test: t_modify_http_headers.test_common_config.TestCachedRespSetHeader.test_add_some_hdrs Apr 26 05:32:28 192.168.122.209 [48498.868529] [tdb] Start Tempesta DB Apr 26 05:32:28 192.168.122.209 [48499.029469] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:32:30 192.168.122.209 [48500.521179] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48500.521179] Maybe that's fine, but it's worth checking the [48500.521179] config - if there is no relations between the [48500.521179] names, then host name confusion attack is possible. Apr 26 05:32:30 192.168.122.209 [48500.671462] [tempesta fw] Configuration processing is completed. Apr 26 05:32:30 192.168.122.209 [48500.722720] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:32:30 192.168.122.209 [48501.141462] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:32:30 192.168.122.209 [48501.199068] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:32:30 192.168.122.209 [48501.226193] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:32:30 192.168.122.209 [48501.271381] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:32:30 192.168.122.209 [48501.272249] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:32:30 192.168.122.209 [48501.311389] [tempesta fw] Tempesta FW is ready Apr 26 05:32:31 192.168.122.209 [48501.878873] [tdb] Close table 'client0.tdb' Apr 26 05:32:31 192.168.122.209 [48502.068374] [tdb] Close table 'sessions0.tdb' Apr 26 05:32:34 192.168.122.209 [48505.273772] [tdb] Close table 'cache0.tdb' Apr 26 05:32:35 192.168.122.209 [48505.519062] [tdb] Close table 'filter0.tdb' Apr 26 05:32:35 192.168.122.209 [48505.519621] [tempesta fw] modules are stopped Apr 26 05:32:35 192.168.122.209 [48505.683271] [tempesta fw] exiting... Apr 26 05:32:35 192.168.122.209 [48505.781010] [tdb] Shutdown Tempesta DB Apr 26 05:32:35 192.168.122.209 [48506.004515] End test: t_modify_http_headers.test_common_config.TestCachedRespSetHeader.test_add_some_hdrs Apr 26 05:32:35 192.168.122.209 [48506.021392] Start test: t_modify_http_headers.test_common_config.TestCachedRespSetHeader.test_add_some_hdrs_custom_location Apr 26 05:32:36 192.168.122.209 [48507.091003] [tdb] Start Tempesta DB Apr 26 05:32:36 192.168.122.209 [48507.234156] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:32:38 192.168.122.209 [48508.716808] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48508.716808] Maybe that's fine, but it's worth checking the [48508.716808] config - if there is no relations between the [48508.716808] names, then host name confusion attack is possible. Apr 26 05:32:38 192.168.122.209 [48508.863578] [tempesta fw] Configuration processing is completed. Apr 26 05:32:38 192.168.122.209 [48508.919139] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:32:38 192.168.122.209 [48509.343413] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:32:38 192.168.122.209 [48509.369606] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:32:38 192.168.122.209 [48509.395816] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:32:39 192.168.122.209 [48509.443480] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:32:39 192.168.122.209 [48509.444974] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:32:39 192.168.122.209 [48509.495480] [tempesta fw] Tempesta FW is ready Apr 26 05:32:39 192.168.122.209 [48510.087470] [tdb] Close table 'client0.tdb' Apr 26 05:32:39 192.168.122.209 [48510.274052] [tdb] Close table 'sessions0.tdb' Apr 26 05:32:43 192.168.122.209 [48513.458336] [tdb] Close table 'cache0.tdb' Apr 26 05:32:43 192.168.122.209 [48513.699122] [tdb] Close table 'filter0.tdb' Apr 26 05:32:43 192.168.122.209 [48513.699581] [tempesta fw] modules are stopped Apr 26 05:32:43 192.168.122.209 [48513.905741] [tempesta fw] exiting... Apr 26 05:32:43 192.168.122.209 [48514.032059] [tdb] Shutdown Tempesta DB Apr 26 05:32:43 192.168.122.209 [48514.234149] End test: t_modify_http_headers.test_common_config.TestCachedRespSetHeader.test_add_some_hdrs_custom_location Apr 26 05:32:43 192.168.122.209 [48514.249711] Start test: t_modify_http_headers.test_common_config.TestReqAddHeader.test_add_hdrs_derive_config Apr 26 05:32:44 192.168.122.209 [48515.285772] [tdb] Start Tempesta DB Apr 26 05:32:45 192.168.122.209 [48515.418933] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:32:46 192.168.122.209 [48516.828464] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48516.828464] Maybe that's fine, but it's worth checking the [48516.828464] config - if there is no relations between the [48516.828464] names, then host name confusion attack is possible. Apr 26 05:32:46 192.168.122.209 [48516.923660] [tempesta fw] Configuration processing is completed. Apr 26 05:32:46 192.168.122.209 [48516.984455] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:32:46 192.168.122.209 [48517.396238] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:32:47 192.168.122.209 [48517.422052] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:32:47 192.168.122.209 [48517.448856] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:32:47 192.168.122.209 [48517.491605] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:32:47 192.168.122.209 [48517.493006] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:32:47 192.168.122.209 [48517.531603] [tempesta fw] Tempesta FW is ready Apr 26 05:32:47 192.168.122.209 [48518.111204] [tdb] Close table 'client0.tdb' Apr 26 05:32:47 192.168.122.209 [48518.308227] [tdb] Close table 'sessions0.tdb' Apr 26 05:32:51 192.168.122.209 [48521.505916] [tdb] Close table 'cache0.tdb' Apr 26 05:32:51 192.168.122.209 [48521.759434] [tdb] Close table 'filter0.tdb' Apr 26 05:32:51 192.168.122.209 [48521.759921] [tempesta fw] modules are stopped Apr 26 05:32:51 192.168.122.209 [48521.938465] [tempesta fw] exiting... Apr 26 05:32:51 192.168.122.209 [48522.058139] [tdb] Shutdown Tempesta DB Apr 26 05:32:51 192.168.122.209 [48522.280980] End test: t_modify_http_headers.test_common_config.TestReqAddHeader.test_add_hdrs_derive_config Apr 26 05:32:51 192.168.122.209 [48522.293014] Start test: t_modify_http_headers.test_common_config.TestReqAddHeader.test_add_hdrs_override_config Apr 26 05:32:52 192.168.122.209 [48523.374225] [tdb] Start Tempesta DB Apr 26 05:32:53 192.168.122.209 [48523.515758] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:32:54 192.168.122.209 [48524.949022] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48524.949022] Maybe that's fine, but it's worth checking the [48524.949022] config - if there is no relations between the [48524.949022] names, then host name confusion attack is possible. Apr 26 05:32:54 192.168.122.209 [48525.067780] [tempesta fw] Configuration processing is completed. Apr 26 05:32:54 192.168.122.209 [48525.119250] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:32:55 192.168.122.209 [48525.541071] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:32:55 192.168.122.209 [48525.567845] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:32:55 192.168.122.209 [48525.593728] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:32:55 192.168.122.209 [48525.635707] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:32:55 192.168.122.209 [48525.636913] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:32:55 192.168.122.209 [48525.671685] [tempesta fw] Tempesta FW is ready Apr 26 05:32:55 192.168.122.209 [48526.214062] [tdb] Close table 'client0.tdb' Apr 26 05:32:55 192.168.122.209 [48526.405733] [tdb] Close table 'sessions0.tdb' Apr 26 05:32:59 192.168.122.209 [48529.600674] [tdb] Close table 'cache0.tdb' Apr 26 05:32:59 192.168.122.209 [48529.831810] [tdb] Close table 'filter0.tdb' Apr 26 05:32:59 192.168.122.209 [48529.832283] [tempesta fw] modules are stopped Apr 26 05:32:59 192.168.122.209 [48530.033745] [tempesta fw] exiting... Apr 26 05:32:59 192.168.122.209 [48530.148288] [tdb] Shutdown Tempesta DB Apr 26 05:32:59 192.168.122.209 [48530.335836] End test: t_modify_http_headers.test_common_config.TestReqAddHeader.test_add_hdrs_override_config Apr 26 05:32:59 192.168.122.209 [48530.347426] Start test: t_modify_http_headers.test_common_config.TestReqAddHeader.test_add_some_hdrs Apr 26 05:33:01 192.168.122.209 [48531.428699] [tdb] Start Tempesta DB Apr 26 05:33:01 192.168.122.209 [48531.548926] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:33:02 192.168.122.209 [48532.988888] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48532.988888] Maybe that's fine, but it's worth checking the [48532.988888] config - if there is no relations between the [48532.988888] names, then host name confusion attack is possible. Apr 26 05:33:02 192.168.122.209 [48533.099864] [tempesta fw] Configuration processing is completed. Apr 26 05:33:02 192.168.122.209 [48533.150656] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:33:03 192.168.122.209 [48533.559720] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:33:03 192.168.122.209 [48533.585720] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:33:03 192.168.122.209 [48533.612254] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:33:03 192.168.122.209 [48533.711872] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:33:03 192.168.122.209 [48533.713601] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:33:03 192.168.122.209 [48533.751755] [tempesta fw] Tempesta FW is ready Apr 26 05:33:03 192.168.122.209 [48534.330212] [tdb] Close table 'client0.tdb' Apr 26 05:33:04 192.168.122.209 [48534.515076] [tdb] Close table 'sessions0.tdb' Apr 26 05:33:07 192.168.122.209 [48537.778062] [tdb] Close table 'cache0.tdb' Apr 26 05:33:07 192.168.122.209 [48538.069710] [tdb] Close table 'filter0.tdb' Apr 26 05:33:07 192.168.122.209 [48538.070232] [tempesta fw] modules are stopped Apr 26 05:33:07 192.168.122.209 [48538.254933] [tempesta fw] exiting... Apr 26 05:33:07 192.168.122.209 [48538.369937] [tdb] Shutdown Tempesta DB Apr 26 05:33:08 192.168.122.209 [48538.569146] End test: t_modify_http_headers.test_common_config.TestReqAddHeader.test_add_some_hdrs Apr 26 05:33:08 192.168.122.209 [48538.576006] Start test: t_modify_http_headers.test_common_config.TestReqAddHeader.test_add_some_hdrs_custom_location Apr 26 05:33:09 192.168.122.209 [48539.641001] [tdb] Start Tempesta DB Apr 26 05:33:09 192.168.122.209 [48539.770656] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:33:10 192.168.122.209 [48541.197189] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48541.197189] Maybe that's fine, but it's worth checking the [48541.197189] config - if there is no relations between the [48541.197189] names, then host name confusion attack is possible. Apr 26 05:33:10 192.168.122.209 [48541.307977] [tempesta fw] Configuration processing is completed. Apr 26 05:33:10 192.168.122.209 [48541.358434] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:33:11 192.168.122.209 [48541.760424] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:33:11 192.168.122.209 [48541.795544] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:33:11 192.168.122.209 [48541.830226] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:33:11 192.168.122.209 [48541.879921] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:33:11 192.168.122.209 [48541.881310] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:33:11 192.168.122.209 [48541.923894] [tempesta fw] Tempesta FW is ready Apr 26 05:33:12 192.168.122.209 [48542.464434] [tdb] Close table 'client0.tdb' Apr 26 05:33:12 192.168.122.209 [48542.670353] [tdb] Close table 'sessions0.tdb' Apr 26 05:33:15 192.168.122.209 [48545.841995] [tdb] Close table 'cache0.tdb' Apr 26 05:33:15 192.168.122.209 [48546.058807] [tdb] Close table 'filter0.tdb' Apr 26 05:33:15 192.168.122.209 [48546.059230] [tempesta fw] modules are stopped Apr 26 05:33:15 192.168.122.209 [48546.281740] [tempesta fw] exiting... Apr 26 05:33:15 192.168.122.209 [48546.414533] [tdb] Shutdown Tempesta DB Apr 26 05:33:16 192.168.122.209 [48546.635487] End test: t_modify_http_headers.test_common_config.TestReqAddHeader.test_add_some_hdrs_custom_location Apr 26 05:33:16 192.168.122.209 [48546.645492] Start test: t_modify_http_headers.test_common_config.TestReqSetHeader.test_add_hdrs_derive_config Apr 26 05:33:17 192.168.122.209 [48547.701239] [tdb] Start Tempesta DB Apr 26 05:33:17 192.168.122.209 [48547.841602] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:33:18 192.168.122.209 [48549.209347] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48549.209347] Maybe that's fine, but it's worth checking the [48549.209347] config - if there is no relations between the [48549.209347] names, then host name confusion attack is possible. Apr 26 05:33:18 192.168.122.209 [48549.336006] [tempesta fw] Configuration processing is completed. Apr 26 05:33:18 192.168.122.209 [48549.387979] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:33:19 192.168.122.209 [48549.813406] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:33:19 192.168.122.209 [48549.839000] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:33:19 192.168.122.209 [48549.864734] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:33:19 192.168.122.209 [48549.908019] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:33:19 192.168.122.209 [48549.909217] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:33:19 192.168.122.209 [48549.952016] [tempesta fw] Tempesta FW is ready Apr 26 05:33:20 192.168.122.209 [48550.524635] [tdb] Close table 'client0.tdb' Apr 26 05:33:20 192.168.122.209 [48550.699174] [tdb] Close table 'sessions0.tdb' Apr 26 05:33:23 192.168.122.209 [48553.874122] [tdb] Close table 'cache0.tdb' Apr 26 05:33:23 192.168.122.209 [48554.129671] [tdb] Close table 'filter0.tdb' Apr 26 05:33:23 192.168.122.209 [48554.130113] [tempesta fw] modules are stopped Apr 26 05:33:23 192.168.122.209 [48554.341469] [tempesta fw] exiting... Apr 26 05:33:24 192.168.122.209 [48554.508685] [tdb] Shutdown Tempesta DB Apr 26 05:33:24 192.168.122.209 [48554.714361] End test: t_modify_http_headers.test_common_config.TestReqSetHeader.test_add_hdrs_derive_config Apr 26 05:33:24 192.168.122.209 [48554.726257] Start test: t_modify_http_headers.test_common_config.TestReqSetHeader.test_add_hdrs_override_config Apr 26 05:33:25 192.168.122.209 [48555.759202] [tdb] Start Tempesta DB Apr 26 05:33:25 192.168.122.209 [48555.903923] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:33:26 192.168.122.209 [48557.329121] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48557.329121] Maybe that's fine, but it's worth checking the [48557.329121] config - if there is no relations between the [48557.329121] names, then host name confusion attack is possible. Apr 26 05:33:27 192.168.122.209 [48557.440188] [tempesta fw] Configuration processing is completed. Apr 26 05:33:27 192.168.122.209 [48557.489656] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:33:27 192.168.122.209 [48557.901636] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:33:27 192.168.122.209 [48557.928316] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:33:27 192.168.122.209 [48557.954719] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:33:27 192.168.122.209 [48557.988101] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:33:27 192.168.122.209 [48557.989182] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:33:27 192.168.122.209 [48558.040125] [tempesta fw] Tempesta FW is ready Apr 26 05:33:28 192.168.122.209 [48558.608749] [tdb] Close table 'client0.tdb' Apr 26 05:33:28 192.168.122.209 [48558.799066] [tdb] Close table 'sessions0.tdb' Apr 26 05:33:31 192.168.122.209 [48562.029417] [tdb] Close table 'cache0.tdb' Apr 26 05:33:31 192.168.122.209 [48562.262050] [tdb] Close table 'filter0.tdb' Apr 26 05:33:31 192.168.122.209 [48562.262488] [tempesta fw] modules are stopped Apr 26 05:33:32 192.168.122.209 [48562.516117] [tempesta fw] exiting... Apr 26 05:33:32 192.168.122.209 [48562.651093] [tdb] Shutdown Tempesta DB Apr 26 05:33:32 192.168.122.209 [48562.879720] End test: t_modify_http_headers.test_common_config.TestReqSetHeader.test_add_hdrs_override_config Apr 26 05:33:32 192.168.122.209 [48562.889521] Start test: t_modify_http_headers.test_common_config.TestReqSetHeader.test_add_some_hdrs Apr 26 05:33:33 192.168.122.209 [48563.899560] [tdb] Start Tempesta DB Apr 26 05:33:33 192.168.122.209 [48564.032246] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:33:34 192.168.122.209 [48565.344679] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48565.344679] Maybe that's fine, but it's worth checking the [48565.344679] config - if there is no relations between the [48565.344679] names, then host name confusion attack is possible. Apr 26 05:33:35 192.168.122.209 [48565.464295] [tempesta fw] Configuration processing is completed. Apr 26 05:33:35 192.168.122.209 [48565.514971] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:33:35 192.168.122.209 [48565.948542] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:33:35 192.168.122.209 [48565.983335] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:33:35 192.168.122.209 [48566.009449] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:33:35 192.168.122.209 [48566.064261] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:33:35 192.168.122.209 [48566.065889] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:33:35 192.168.122.209 [48566.104219] [tempesta fw] Tempesta FW is ready Apr 26 05:33:36 192.168.122.209 [48566.688800] [tdb] Close table 'client0.tdb' Apr 26 05:33:36 192.168.122.209 [48566.873048] [tdb] Close table 'sessions0.tdb' Apr 26 05:33:39 192.168.122.209 [48570.062457] [tdb] Close table 'cache0.tdb' Apr 26 05:33:39 192.168.122.209 [48570.315871] [tdb] Close table 'filter0.tdb' Apr 26 05:33:39 192.168.122.209 [48570.316667] [tempesta fw] modules are stopped Apr 26 05:33:40 192.168.122.209 [48570.522137] [tempesta fw] exiting... Apr 26 05:33:40 192.168.122.209 [48570.635999] [tdb] Shutdown Tempesta DB Apr 26 05:33:40 192.168.122.209 [48570.831763] End test: t_modify_http_headers.test_common_config.TestReqSetHeader.test_add_some_hdrs Apr 26 05:33:40 192.168.122.209 [48570.841176] Start test: t_modify_http_headers.test_common_config.TestReqSetHeader.test_add_some_hdrs_custom_location Apr 26 05:33:41 192.168.122.209 [48571.927948] [tdb] Start Tempesta DB Apr 26 05:33:41 192.168.122.209 [48572.071376] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:33:43 192.168.122.209 [48573.537610] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48573.537610] Maybe that's fine, but it's worth checking the [48573.537610] config - if there is no relations between the [48573.537610] names, then host name confusion attack is possible. Apr 26 05:33:43 192.168.122.209 [48573.644392] [tempesta fw] Configuration processing is completed. Apr 26 05:33:43 192.168.122.209 [48573.697372] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:33:43 192.168.122.209 [48574.141062] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:33:43 192.168.122.209 [48574.171291] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:33:43 192.168.122.209 [48574.199606] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:33:43 192.168.122.209 [48574.252365] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:33:43 192.168.122.209 [48574.253998] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:33:43 192.168.122.209 [48574.292326] [tempesta fw] Tempesta FW is ready Apr 26 05:33:44 192.168.122.209 [48574.838378] [tdb] Close table 'client0.tdb' Apr 26 05:33:44 192.168.122.209 [48575.031876] [tdb] Close table 'sessions0.tdb' Apr 26 05:33:47 192.168.122.209 [48578.230089] [tdb] Close table 'cache0.tdb' Apr 26 05:33:48 192.168.122.209 [48578.438969] [tdb] Close table 'filter0.tdb' Apr 26 05:33:48 192.168.122.209 [48578.439400] [tempesta fw] modules are stopped Apr 26 05:33:48 192.168.122.209 [48578.675905] [tempesta fw] exiting... Apr 26 05:33:48 192.168.122.209 [48578.787020] [tdb] Shutdown Tempesta DB Apr 26 05:33:48 192.168.122.209 [48579.007554] End test: t_modify_http_headers.test_common_config.TestReqSetHeader.test_add_some_hdrs_custom_location Apr 26 05:33:48 192.168.122.209 [48579.016005] Start test: t_modify_http_headers.test_common_config.TestRespAddHeader.test_add_hdrs_derive_config Apr 26 05:33:49 192.168.122.209 [48580.045318] [tdb] Start Tempesta DB Apr 26 05:33:49 192.168.122.209 [48580.178384] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:33:51 192.168.122.209 [48581.605829] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48581.605829] Maybe that's fine, but it's worth checking the [48581.605829] config - if there is no relations between the [48581.605829] names, then host name confusion attack is possible. Apr 26 05:33:51 192.168.122.209 [48581.720501] [tempesta fw] Configuration processing is completed. Apr 26 05:33:51 192.168.122.209 [48581.781347] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:33:51 192.168.122.209 [48582.231911] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:33:51 192.168.122.209 [48582.271057] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:33:51 192.168.122.209 [48582.308469] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:33:51 192.168.122.209 [48582.356450] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:33:51 192.168.122.209 [48582.357856] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:33:51 192.168.122.209 [48582.396404] [tempesta fw] Tempesta FW is ready Apr 26 05:33:52 192.168.122.209 [48582.951226] [tdb] Close table 'client0.tdb' Apr 26 05:33:52 192.168.122.209 [48583.138959] [tdb] Close table 'sessions0.tdb' Apr 26 05:33:55 192.168.122.209 [48586.318654] [tdb] Close table 'cache0.tdb' Apr 26 05:33:56 192.168.122.209 [48586.560789] [tdb] Close table 'filter0.tdb' Apr 26 05:33:56 192.168.122.209 [48586.561219] [tempesta fw] modules are stopped Apr 26 05:33:56 192.168.122.209 [48586.786014] [tempesta fw] exiting... Apr 26 05:33:56 192.168.122.209 [48586.888639] [tdb] Shutdown Tempesta DB Apr 26 05:33:56 192.168.122.209 [48587.095996] End test: t_modify_http_headers.test_common_config.TestRespAddHeader.test_add_hdrs_derive_config Apr 26 05:33:56 192.168.122.209 [48587.109349] Start test: t_modify_http_headers.test_common_config.TestRespAddHeader.test_add_hdrs_override_config Apr 26 05:33:57 192.168.122.209 [48588.211154] [tdb] Start Tempesta DB Apr 26 05:33:57 192.168.122.209 [48588.345824] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:33:59 192.168.122.209 [48589.745825] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48589.745825] Maybe that's fine, but it's worth checking the [48589.745825] config - if there is no relations between the [48589.745825] names, then host name confusion attack is possible. Apr 26 05:33:59 192.168.122.209 [48589.868593] [tempesta fw] Configuration processing is completed. Apr 26 05:33:59 192.168.122.209 [48589.926421] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:33:59 192.168.122.209 [48590.379237] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:33:59 192.168.122.209 [48590.407511] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:34:00 192.168.122.209 [48590.434582] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:34:00 192.168.122.209 [48590.484560] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:34:00 192.168.122.209 [48590.485949] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:34:00 192.168.122.209 [48590.528445] [tempesta fw] Tempesta FW is ready Apr 26 05:34:00 192.168.122.209 [48591.076644] [tdb] Close table 'client0.tdb' Apr 26 05:34:00 192.168.122.209 [48591.263455] [tdb] Close table 'sessions0.tdb' Apr 26 05:34:04 192.168.122.209 [48594.474408] [tdb] Close table 'cache0.tdb' Apr 26 05:34:04 192.168.122.209 [48594.726207] [tdb] Close table 'filter0.tdb' Apr 26 05:34:04 192.168.122.209 [48594.726643] [tempesta fw] modules are stopped Apr 26 05:34:04 192.168.122.209 [48594.939248] [tempesta fw] exiting... Apr 26 05:34:04 192.168.122.209 [48595.055138] [tdb] Shutdown Tempesta DB Apr 26 05:34:04 192.168.122.209 [48595.250601] End test: t_modify_http_headers.test_common_config.TestRespAddHeader.test_add_hdrs_override_config Apr 26 05:34:04 192.168.122.209 [48595.262715] Start test: t_modify_http_headers.test_common_config.TestRespAddHeader.test_add_some_hdrs Apr 26 05:34:05 192.168.122.209 [48596.348867] [tdb] Start Tempesta DB Apr 26 05:34:06 192.168.122.209 [48596.489221] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:34:07 192.168.122.209 [48597.897489] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48597.897489] Maybe that's fine, but it's worth checking the [48597.897489] config - if there is no relations between the [48597.897489] names, then host name confusion attack is possible. Apr 26 05:34:07 192.168.122.209 [48598.028719] [tempesta fw] Configuration processing is completed. Apr 26 05:34:07 192.168.122.209 [48598.086231] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:34:08 192.168.122.209 [48598.553426] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:34:08 192.168.122.209 [48598.582273] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:34:08 192.168.122.209 [48598.612003] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:34:08 192.168.122.209 [48598.652615] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:34:08 192.168.122.209 [48598.653670] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:34:08 192.168.122.209 [48598.708611] [tempesta fw] Tempesta FW is ready Apr 26 05:34:08 192.168.122.209 [48599.350807] [tdb] Close table 'client0.tdb' Apr 26 05:34:09 192.168.122.209 [48599.562196] [tdb] Close table 'sessions0.tdb' Apr 26 05:34:12 192.168.122.209 [48602.833684] [tdb] Close table 'cache0.tdb' Apr 26 05:34:12 192.168.122.209 [48603.080189] [tdb] Close table 'filter0.tdb' Apr 26 05:34:12 192.168.122.209 [48603.080669] [tempesta fw] modules are stopped Apr 26 05:34:12 192.168.122.209 [48603.331514] [tempesta fw] exiting... Apr 26 05:34:13 192.168.122.209 [48603.464958] [tdb] Shutdown Tempesta DB Apr 26 05:34:13 192.168.122.209 [48603.676175] End test: t_modify_http_headers.test_common_config.TestRespAddHeader.test_add_some_hdrs Apr 26 05:34:13 192.168.122.209 [48603.700983] Start test: t_modify_http_headers.test_common_config.TestRespAddHeader.test_add_some_hdrs_custom_location Apr 26 05:34:14 192.168.122.209 [48604.806653] [tdb] Start Tempesta DB Apr 26 05:34:14 192.168.122.209 [48604.952161] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:34:16 192.168.122.209 [48606.442057] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48606.442057] Maybe that's fine, but it's worth checking the [48606.442057] config - if there is no relations between the [48606.442057] names, then host name confusion attack is possible. Apr 26 05:34:16 192.168.122.209 [48606.544815] [tempesta fw] Configuration processing is completed. Apr 26 05:34:16 192.168.122.209 [48606.603152] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:34:16 192.168.122.209 [48607.015310] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:34:16 192.168.122.209 [48607.041332] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:34:16 192.168.122.209 [48607.067190] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:34:16 192.168.122.209 [48607.112753] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:34:16 192.168.122.209 [48607.113988] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:34:16 192.168.122.209 [48607.152796] [tempesta fw] Tempesta FW is ready Apr 26 05:34:17 192.168.122.209 [48607.737357] [tdb] Close table 'client0.tdb' Apr 26 05:34:17 192.168.122.209 [48607.930220] [tdb] Close table 'sessions0.tdb' Apr 26 05:34:20 192.168.122.209 [48611.254615] [tdb] Close table 'cache0.tdb' Apr 26 05:34:21 192.168.122.209 [48611.493787] [tdb] Close table 'filter0.tdb' Apr 26 05:34:21 192.168.122.209 [48611.494232] [tempesta fw] modules are stopped Apr 26 05:34:21 192.168.122.209 [48611.679613] [tempesta fw] exiting... Apr 26 05:34:21 192.168.122.209 [48611.808147] [tdb] Shutdown Tempesta DB Apr 26 05:34:21 192.168.122.209 [48612.013763] End test: t_modify_http_headers.test_common_config.TestRespAddHeader.test_add_some_hdrs_custom_location Apr 26 05:34:21 192.168.122.209 [48612.024570] Start test: t_modify_http_headers.test_common_config.TestRespSetHeader.test_add_hdrs_derive_config Apr 26 05:34:22 192.168.122.209 [48613.126523] [tdb] Start Tempesta DB Apr 26 05:34:22 192.168.122.209 [48613.284158] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:34:24 192.168.122.209 [48614.698007] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48614.698007] Maybe that's fine, but it's worth checking the [48614.698007] config - if there is no relations between the [48614.698007] names, then host name confusion attack is possible. Apr 26 05:34:24 192.168.122.209 [48614.828831] [tempesta fw] Configuration processing is completed. Apr 26 05:34:24 192.168.122.209 [48614.888423] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:34:25 192.168.122.209 [48615.427182] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:34:25 192.168.122.209 [48615.462440] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:34:25 192.168.122.209 [48615.497268] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:34:25 192.168.122.209 [48615.556912] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:34:25 192.168.122.209 [48615.558683] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:34:25 192.168.122.209 [48615.596835] [tempesta fw] Tempesta FW is ready Apr 26 05:34:25 192.168.122.209 [48616.156175] [tdb] Close table 'client0.tdb' Apr 26 05:34:25 192.168.122.209 [48616.346753] [tdb] Close table 'sessions0.tdb' Apr 26 05:34:29 192.168.122.209 [48619.591595] [tdb] Close table 'cache0.tdb' Apr 26 05:34:29 192.168.122.209 [48619.826056] [tdb] Close table 'filter0.tdb' Apr 26 05:34:29 192.168.122.209 [48619.826498] [tempesta fw] modules are stopped Apr 26 05:34:29 192.168.122.209 [48620.038959] [tempesta fw] exiting... Apr 26 05:34:29 192.168.122.209 [48620.190810] [tdb] Shutdown Tempesta DB Apr 26 05:34:29 192.168.122.209 [48620.398414] End test: t_modify_http_headers.test_common_config.TestRespSetHeader.test_add_hdrs_derive_config Apr 26 05:34:29 192.168.122.209 [48620.409393] Start test: t_modify_http_headers.test_common_config.TestRespSetHeader.test_add_hdrs_override_config Apr 26 05:34:31 192.168.122.209 [48621.474673] [tdb] Start Tempesta DB Apr 26 05:34:31 192.168.122.209 [48621.611169] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:34:32 192.168.122.209 [48623.126379] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48623.126379] Maybe that's fine, but it's worth checking the [48623.126379] config - if there is no relations between the [48623.126379] names, then host name confusion attack is possible. Apr 26 05:34:32 192.168.122.209 [48623.249054] [tempesta fw] Configuration processing is completed. Apr 26 05:34:32 192.168.122.209 [48623.302954] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:34:33 192.168.122.209 [48623.721919] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:34:33 192.168.122.209 [48623.758689] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:34:33 192.168.122.209 [48623.785968] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:34:33 192.168.122.209 [48623.844975] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:34:33 192.168.122.209 [48623.846997] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:34:33 192.168.122.209 [48623.888920] [tempesta fw] Tempesta FW is ready Apr 26 05:34:34 192.168.122.209 [48624.446731] [tdb] Close table 'client0.tdb' Apr 26 05:34:34 192.168.122.209 [48624.646627] [tdb] Close table 'sessions0.tdb' Apr 26 05:34:37 192.168.122.209 [48627.883573] [tdb] Close table 'cache0.tdb' Apr 26 05:34:37 192.168.122.209 [48628.121935] [tdb] Close table 'filter0.tdb' Apr 26 05:34:37 192.168.122.209 [48628.122375] [tempesta fw] modules are stopped Apr 26 05:34:37 192.168.122.209 [48628.315297] [tempesta fw] exiting... Apr 26 05:34:38 192.168.122.209 [48628.427563] [tdb] Shutdown Tempesta DB Apr 26 05:34:38 192.168.122.209 [48628.616752] End test: t_modify_http_headers.test_common_config.TestRespSetHeader.test_add_hdrs_override_config Apr 26 05:34:38 192.168.122.209 [48628.632114] Start test: t_modify_http_headers.test_common_config.TestRespSetHeader.test_add_some_hdrs Apr 26 05:34:39 192.168.122.209 [48629.743960] [tdb] Start Tempesta DB Apr 26 05:34:39 192.168.122.209 [48629.880889] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:34:40 192.168.122.209 [48631.302335] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48631.302335] Maybe that's fine, but it's worth checking the [48631.302335] config - if there is no relations between the [48631.302335] names, then host name confusion attack is possible. Apr 26 05:34:41 192.168.122.209 [48631.421099] [tempesta fw] Configuration processing is completed. Apr 26 05:34:41 192.168.122.209 [48631.476781] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:34:41 192.168.122.209 [48631.887391] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:34:41 192.168.122.209 [48631.913082] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:34:41 192.168.122.209 [48631.938950] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:34:41 192.168.122.209 [48631.989115] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:34:41 192.168.122.209 [48631.990857] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:34:41 192.168.122.209 [48632.045024] [tempesta fw] Tempesta FW is ready Apr 26 05:34:42 192.168.122.209 [48632.596678] [tdb] Close table 'client0.tdb' Apr 26 05:34:42 192.168.122.209 [48632.780679] [tdb] Close table 'sessions0.tdb' Apr 26 05:34:45 192.168.122.209 [48635.945222] [tdb] Close table 'cache0.tdb' Apr 26 05:34:45 192.168.122.209 [48636.211142] [tdb] Close table 'filter0.tdb' Apr 26 05:34:45 192.168.122.209 [48636.211590] [tempesta fw] modules are stopped Apr 26 05:34:46 192.168.122.209 [48636.418551] [tempesta fw] exiting... Apr 26 05:34:46 192.168.122.209 [48636.552535] [tdb] Shutdown Tempesta DB Apr 26 05:34:46 192.168.122.209 [48636.760617] End test: t_modify_http_headers.test_common_config.TestRespSetHeader.test_add_some_hdrs Apr 26 05:34:46 192.168.122.209 [48636.773584] Start test: t_modify_http_headers.test_common_config.TestRespSetHeader.test_add_some_hdrs_custom_location Apr 26 05:34:47 192.168.122.209 [48637.816931] [tdb] Start Tempesta DB Apr 26 05:34:47 192.168.122.209 [48637.964359] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:34:48 192.168.122.209 [48639.393822] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48639.393822] Maybe that's fine, but it's worth checking the [48639.393822] config - if there is no relations between the [48639.393822] names, then host name confusion attack is possible. Apr 26 05:34:49 192.168.122.209 [48639.493262] [tempesta fw] Configuration processing is completed. Apr 26 05:34:49 192.168.122.209 [48639.561911] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:34:49 192.168.122.209 [48639.979485] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:34:49 192.168.122.209 [48640.006798] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:34:49 192.168.122.209 [48640.033804] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:34:49 192.168.122.209 [48640.081193] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:34:49 192.168.122.209 [48640.082628] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:34:49 192.168.122.209 [48640.121106] [tempesta fw] Tempesta FW is ready Apr 26 05:34:50 192.168.122.209 [48640.692183] [tdb] Close table 'client0.tdb' Apr 26 05:34:50 192.168.122.209 [48640.901689] [tdb] Close table 'sessions0.tdb' Apr 26 05:34:53 192.168.122.209 [48644.213045] [tdb] Close table 'cache0.tdb' Apr 26 05:34:54 192.168.122.209 [48644.472486] [tdb] Close table 'filter0.tdb' Apr 26 05:34:54 192.168.122.209 [48644.472916] [tempesta fw] modules are stopped Apr 26 05:34:54 192.168.122.209 [48644.692845] [tempesta fw] exiting... Apr 26 05:34:54 192.168.122.209 [48644.849824] [tdb] Shutdown Tempesta DB Apr 26 05:34:54 192.168.122.209 [48645.088381] End test: t_modify_http_headers.test_common_config.TestRespSetHeader.test_add_some_hdrs_custom_location Apr 26 05:34:54 192.168.122.209 [48645.099750] Start test: t_modify_http_headers.test_common_config_h2.TestCachedRespAddHeaderH2.test_add_hdrs_derive_config Apr 26 05:34:55 192.168.122.209 [48646.189366] [tdb] Start Tempesta DB Apr 26 05:34:55 192.168.122.209 [48646.330039] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:34:57 192.168.122.209 [48647.822485] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48647.822485] Maybe that's fine, but it's worth checking the [48647.822485] config - if there is no relations between the [48647.822485] names, then host name confusion attack is possible. Apr 26 05:34:57 192.168.122.209 [48647.977314] [tempesta fw] Configuration processing is completed. Apr 26 05:34:57 192.168.122.209 [48648.028335] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:34:58 192.168.122.209 [48648.443214] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:34:58 192.168.122.209 [48648.468871] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:34:58 192.168.122.209 [48648.494646] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:34:58 192.168.122.209 [48648.565306] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:34:58 192.168.122.209 [48648.567041] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:34:58 192.168.122.209 [48648.605238] [tempesta fw] Tempesta FW is ready Apr 26 05:34:58 192.168.122.209 [48649.195094] [tdb] Close table 'client0.tdb' Apr 26 05:34:58 192.168.122.209 [48649.392862] [tdb] Close table 'sessions0.tdb' Apr 26 05:35:02 192.168.122.209 [48652.625077] [tdb] Close table 'cache0.tdb' Apr 26 05:35:02 192.168.122.209 [48652.847727] [tdb] Close table 'filter0.tdb' Apr 26 05:35:02 192.168.122.209 [48652.848165] [tempesta fw] modules are stopped Apr 26 05:35:02 192.168.122.209 [48653.099846] [tempesta fw] exiting... Apr 26 05:35:02 192.168.122.209 [48653.230322] [tdb] Shutdown Tempesta DB Apr 26 05:35:03 192.168.122.209 [48653.449086] End test: t_modify_http_headers.test_common_config_h2.TestCachedRespAddHeaderH2.test_add_hdrs_derive_config Apr 26 05:35:03 192.168.122.209 [48653.467382] Start test: t_modify_http_headers.test_common_config_h2.TestCachedRespAddHeaderH2.test_add_hdrs_override_config Apr 26 05:35:04 192.168.122.209 [48654.534045] [tdb] Start Tempesta DB Apr 26 05:35:04 192.168.122.209 [48654.665262] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:35:05 192.168.122.209 [48656.130661] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48656.130661] Maybe that's fine, but it's worth checking the [48656.130661] config - if there is no relations between the [48656.130661] names, then host name confusion attack is possible. Apr 26 05:35:05 192.168.122.209 [48656.285415] [tempesta fw] Configuration processing is completed. Apr 26 05:35:05 192.168.122.209 [48656.337969] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:35:06 192.168.122.209 [48656.741133] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:35:06 192.168.122.209 [48656.798795] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:35:06 192.168.122.209 [48656.824420] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:35:06 192.168.122.209 [48656.869396] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:35:06 192.168.122.209 [48656.871161] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:35:06 192.168.122.209 [48656.929353] [tempesta fw] Tempesta FW is ready Apr 26 05:35:07 192.168.122.209 [48657.490705] [tdb] Close table 'client0.tdb' Apr 26 05:35:07 192.168.122.209 [48657.690756] [tdb] Close table 'sessions0.tdb' Apr 26 05:35:10 192.168.122.209 [48660.929882] [tdb] Close table 'cache0.tdb' Apr 26 05:35:10 192.168.122.209 [48661.165740] [tdb] Close table 'filter0.tdb' Apr 26 05:35:10 192.168.122.209 [48661.166188] [tempesta fw] modules are stopped Apr 26 05:35:10 192.168.122.209 [48661.366993] [tempesta fw] exiting... Apr 26 05:35:11 192.168.122.209 [48661.510950] [tdb] Shutdown Tempesta DB Apr 26 05:35:11 192.168.122.209 [48661.729802] End test: t_modify_http_headers.test_common_config_h2.TestCachedRespAddHeaderH2.test_add_hdrs_override_config Apr 26 05:35:11 192.168.122.209 [48661.744719] Start test: t_modify_http_headers.test_common_config_h2.TestCachedRespAddHeaderH2.test_add_some_hdrs Apr 26 05:35:12 192.168.122.209 [48662.840704] [tdb] Start Tempesta DB Apr 26 05:35:12 192.168.122.209 [48662.983609] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:35:13 192.168.122.209 [48664.338796] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48664.338796] Maybe that's fine, but it's worth checking the [48664.338796] config - if there is no relations between the [48664.338796] names, then host name confusion attack is possible. Apr 26 05:35:14 192.168.122.209 [48664.497519] [tempesta fw] Configuration processing is completed. Apr 26 05:35:14 192.168.122.209 [48664.556649] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:35:14 192.168.122.209 [48665.016031] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:35:14 192.168.122.209 [48665.044654] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:35:14 192.168.122.209 [48665.073549] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:35:14 192.168.122.209 [48665.129502] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:35:14 192.168.122.209 [48665.131280] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:35:14 192.168.122.209 [48665.173364] [tempesta fw] Tempesta FW is ready Apr 26 05:35:15 192.168.122.209 [48665.732753] [tdb] Close table 'client0.tdb' Apr 26 05:35:15 192.168.122.209 [48665.928489] [tdb] Close table 'sessions0.tdb' Apr 26 05:35:18 192.168.122.209 [48669.138572] [tdb] Close table 'cache0.tdb' Apr 26 05:35:18 192.168.122.209 [48669.353022] [tdb] Close table 'filter0.tdb' Apr 26 05:35:18 192.168.122.209 [48669.353480] [tempesta fw] modules are stopped Apr 26 05:35:19 192.168.122.209 [48669.542938] [tempesta fw] exiting... Apr 26 05:35:19 192.168.122.209 [48669.666732] [tdb] Shutdown Tempesta DB Apr 26 05:35:19 192.168.122.209 [48669.905884] End test: t_modify_http_headers.test_common_config_h2.TestCachedRespAddHeaderH2.test_add_some_hdrs Apr 26 05:35:19 192.168.122.209 [48669.921011] Start test: t_modify_http_headers.test_common_config_h2.TestCachedRespAddHeaderH2.test_add_some_hdrs_custom_location Apr 26 05:35:20 192.168.122.209 [48670.969441] [tdb] Start Tempesta DB Apr 26 05:35:20 192.168.122.209 [48671.122049] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:35:22 192.168.122.209 [48672.690886] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48672.690886] Maybe that's fine, but it's worth checking the [48672.690886] config - if there is no relations between the [48672.690886] names, then host name confusion attack is possible. Apr 26 05:35:22 192.168.122.209 [48672.842047] [tempesta fw] Configuration processing is completed. Apr 26 05:35:22 192.168.122.209 [48672.891116] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:35:22 192.168.122.209 [48673.299502] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:35:22 192.168.122.209 [48673.356686] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:35:22 192.168.122.209 [48673.383200] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:35:23 192.168.122.209 [48673.425549] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:35:23 192.168.122.209 [48673.426760] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:35:23 192.168.122.209 [48673.473562] [tempesta fw] Tempesta FW is ready Apr 26 05:35:23 192.168.122.209 [48674.087503] [tdb] Close table 'client0.tdb' Apr 26 05:35:23 192.168.122.209 [48674.271999] [tdb] Close table 'sessions0.tdb' Apr 26 05:35:27 192.168.122.209 [48677.500304] [tdb] Close table 'cache0.tdb' Apr 26 05:35:27 192.168.122.209 [48677.739452] [tdb] Close table 'filter0.tdb' Apr 26 05:35:27 192.168.122.209 [48677.739894] [tempesta fw] modules are stopped Apr 26 05:35:27 192.168.122.209 [48677.917987] [tempesta fw] exiting... Apr 26 05:35:27 192.168.122.209 [48678.051808] [tdb] Shutdown Tempesta DB Apr 26 05:35:27 192.168.122.209 [48678.276840] End test: t_modify_http_headers.test_common_config_h2.TestCachedRespAddHeaderH2.test_add_some_hdrs_custom_location Apr 26 05:35:27 192.168.122.209 [48678.290870] Start test: t_modify_http_headers.test_common_config_h2.TestCachedRespSetHeaderH2.test_add_hdrs_derive_config Apr 26 05:35:28 192.168.122.209 [48679.361942] [tdb] Start Tempesta DB Apr 26 05:35:29 192.168.122.209 [48679.511399] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:35:30 192.168.122.209 [48680.946978] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48680.946978] Maybe that's fine, but it's worth checking the [48680.946978] config - if there is no relations between the [48680.946978] names, then host name confusion attack is possible. Apr 26 05:35:30 192.168.122.209 [48681.105747] [tempesta fw] Configuration processing is completed. Apr 26 05:35:30 192.168.122.209 [48681.164746] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:35:31 192.168.122.209 [48681.569825] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:35:31 192.168.122.209 [48681.631323] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:35:31 192.168.122.209 [48681.657040] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:35:31 192.168.122.209 [48681.713688] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:35:31 192.168.122.209 [48681.715095] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:35:31 192.168.122.209 [48681.753652] [tempesta fw] Tempesta FW is ready Apr 26 05:35:31 192.168.122.209 [48682.336059] [tdb] Close table 'client0.tdb' Apr 26 05:35:32 192.168.122.209 [48682.520393] [tdb] Close table 'sessions0.tdb' Apr 26 05:35:35 192.168.122.209 [48685.807210] [tdb] Close table 'cache0.tdb' Apr 26 05:35:35 192.168.122.209 [48686.050059] [tdb] Close table 'filter0.tdb' Apr 26 05:35:35 192.168.122.209 [48686.050520] [tempesta fw] modules are stopped Apr 26 05:35:35 192.168.122.209 [48686.233704] [tempesta fw] exiting... Apr 26 05:35:35 192.168.122.209 [48686.406819] [tdb] Shutdown Tempesta DB Apr 26 05:35:36 192.168.122.209 [48686.620368] End test: t_modify_http_headers.test_common_config_h2.TestCachedRespSetHeaderH2.test_add_hdrs_derive_config Apr 26 05:35:36 192.168.122.209 [48686.629215] Start test: t_modify_http_headers.test_common_config_h2.TestCachedRespSetHeaderH2.test_add_hdrs_override_config Apr 26 05:35:37 192.168.122.209 [48687.734161] [tdb] Start Tempesta DB Apr 26 05:35:37 192.168.122.209 [48687.871114] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:35:38 192.168.122.209 [48689.391140] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48689.391140] Maybe that's fine, but it's worth checking the [48689.391140] config - if there is no relations between the [48689.391140] names, then host name confusion attack is possible. Apr 26 05:35:39 192.168.122.209 [48689.533851] [tempesta fw] Configuration processing is completed. Apr 26 05:35:39 192.168.122.209 [48689.586337] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:35:39 192.168.122.209 [48690.013956] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:35:39 192.168.122.209 [48690.040156] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:35:39 192.168.122.209 [48690.066236] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:35:39 192.168.122.209 [48690.105787] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:35:39 192.168.122.209 [48690.106777] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:35:39 192.168.122.209 [48690.153672] [tempesta fw] Tempesta FW is ready Apr 26 05:35:40 192.168.122.209 [48690.677822] [tdb] Close table 'client0.tdb' Apr 26 05:35:40 192.168.122.209 [48690.890604] [tdb] Close table 'sessions0.tdb' Apr 26 05:35:43 192.168.122.209 [48694.149890] [tdb] Close table 'cache0.tdb' Apr 26 05:35:43 192.168.122.209 [48694.377589] [tdb] Close table 'filter0.tdb' Apr 26 05:35:43 192.168.122.209 [48694.378059] [tempesta fw] modules are stopped Apr 26 05:35:44 192.168.122.209 [48694.565678] [tempesta fw] exiting... Apr 26 05:35:44 192.168.122.209 [48694.690763] [tdb] Shutdown Tempesta DB Apr 26 05:35:44 192.168.122.209 [48694.918016] End test: t_modify_http_headers.test_common_config_h2.TestCachedRespSetHeaderH2.test_add_hdrs_override_config Apr 26 05:35:44 192.168.122.209 [48694.931211] Start test: t_modify_http_headers.test_common_config_h2.TestCachedRespSetHeaderH2.test_add_some_hdrs Apr 26 05:35:45 192.168.122.209 [48696.002848] [tdb] Start Tempesta DB Apr 26 05:35:45 192.168.122.209 [48696.136018] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:35:47 192.168.122.209 [48697.555210] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48697.555210] Maybe that's fine, but it's worth checking the [48697.555210] config - if there is no relations between the [48697.555210] names, then host name confusion attack is possible. Apr 26 05:35:47 192.168.122.209 [48697.717939] [tempesta fw] Configuration processing is completed. Apr 26 05:35:47 192.168.122.209 [48697.770162] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:35:47 192.168.122.209 [48698.174499] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:35:47 192.168.122.209 [48698.230984] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:35:47 192.168.122.209 [48698.262501] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:35:47 192.168.122.209 [48698.317914] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:35:47 192.168.122.209 [48698.319622] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:35:47 192.168.122.209 [48698.357875] [tempesta fw] Tempesta FW is ready Apr 26 05:35:48 192.168.122.209 [48698.938505] [tdb] Close table 'client0.tdb' Apr 26 05:35:48 192.168.122.209 [48699.115767] [tdb] Close table 'sessions0.tdb' Apr 26 05:35:51 192.168.122.209 [48702.358497] [tdb] Close table 'cache0.tdb' Apr 26 05:35:52 192.168.122.209 [48702.597231] [tdb] Close table 'filter0.tdb' Apr 26 05:35:52 192.168.122.209 [48702.597698] [tempesta fw] modules are stopped Apr 26 05:35:52 192.168.122.209 [48702.779367] [tempesta fw] exiting... Apr 26 05:35:52 192.168.122.209 [48702.903948] [tdb] Shutdown Tempesta DB Apr 26 05:35:52 192.168.122.209 [48703.081702] End test: t_modify_http_headers.test_common_config_h2.TestCachedRespSetHeaderH2.test_add_some_hdrs Apr 26 05:35:52 192.168.122.209 [48703.104651] Start test: t_modify_http_headers.test_common_config_h2.TestCachedRespSetHeaderH2.test_add_some_hdrs_custom_location Apr 26 05:35:53 192.168.122.209 [48704.161937] [tdb] Start Tempesta DB Apr 26 05:35:53 192.168.122.209 [48704.288770] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:35:55 192.168.122.209 [48705.875422] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48705.875422] Maybe that's fine, but it's worth checking the [48705.875422] config - if there is no relations between the [48705.875422] names, then host name confusion attack is possible. Apr 26 05:35:55 192.168.122.209 [48706.022078] [tempesta fw] Configuration processing is completed. Apr 26 05:35:55 192.168.122.209 [48706.078834] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:35:56 192.168.122.209 [48706.503396] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:35:56 192.168.122.209 [48706.530924] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:35:56 192.168.122.209 [48706.557533] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:35:56 192.168.122.209 [48706.621993] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:35:56 192.168.122.209 [48706.623507] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:35:56 192.168.122.209 [48706.665982] [tempesta fw] Tempesta FW is ready Apr 26 05:35:56 192.168.122.209 [48707.261553] [tdb] Close table 'client0.tdb' Apr 26 05:35:57 192.168.122.209 [48707.454249] [tdb] Close table 'sessions0.tdb' Apr 26 05:36:00 192.168.122.209 [48710.649145] [tdb] Close table 'cache0.tdb' Apr 26 05:36:00 192.168.122.209 [48710.898522] [tdb] Close table 'filter0.tdb' Apr 26 05:36:00 192.168.122.209 [48710.898963] [tempesta fw] modules are stopped Apr 26 05:36:00 192.168.122.209 [48711.073477] [tempesta fw] exiting... Apr 26 05:36:00 192.168.122.209 [48711.216722] [tdb] Shutdown Tempesta DB Apr 26 05:36:01 192.168.122.209 [48711.439561] End test: t_modify_http_headers.test_common_config_h2.TestCachedRespSetHeaderH2.test_add_some_hdrs_custom_location Apr 26 05:36:01 192.168.122.209 [48711.455062] Start test: t_modify_http_headers.test_common_config_h2.TestReqAddHeaderH2.test_add_hdrs_derive_config Apr 26 05:36:02 192.168.122.209 [48712.553264] [tdb] Start Tempesta DB Apr 26 05:36:02 192.168.122.209 [48712.692427] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:36:03 192.168.122.209 [48714.051101] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48714.051101] Maybe that's fine, but it's worth checking the [48714.051101] config - if there is no relations between the [48714.051101] names, then host name confusion attack is possible. Apr 26 05:36:03 192.168.122.209 [48714.162459] [tempesta fw] Configuration processing is completed. Apr 26 05:36:03 192.168.122.209 [48714.215089] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:36:04 192.168.122.209 [48714.635769] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:36:04 192.168.122.209 [48714.698836] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:36:04 192.168.122.209 [48714.725265] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:36:04 192.168.122.209 [48714.786135] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:36:04 192.168.122.209 [48714.787918] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:36:04 192.168.122.209 [48714.830083] [tempesta fw] Tempesta FW is ready Apr 26 05:36:04 192.168.122.209 [48715.376313] [tdb] Close table 'client0.tdb' Apr 26 05:36:05 192.168.122.209 [48715.552828] [tdb] Close table 'sessions0.tdb' Apr 26 05:36:08 192.168.122.209 [48718.765529] [tdb] Close table 'cache0.tdb' Apr 26 05:36:08 192.168.122.209 [48718.990301] [tdb] Close table 'filter0.tdb' Apr 26 05:36:08 192.168.122.209 [48718.990759] [tempesta fw] modules are stopped Apr 26 05:36:08 192.168.122.209 [48719.227431] [tempesta fw] exiting... Apr 26 05:36:08 192.168.122.209 [48719.364929] [tdb] Shutdown Tempesta DB Apr 26 05:36:09 192.168.122.209 [48719.584395] End test: t_modify_http_headers.test_common_config_h2.TestReqAddHeaderH2.test_add_hdrs_derive_config Apr 26 05:36:09 192.168.122.209 [48719.596024] Start test: t_modify_http_headers.test_common_config_h2.TestReqAddHeaderH2.test_add_hdrs_override_config Apr 26 05:36:10 192.168.122.209 [48720.722395] [tdb] Start Tempesta DB Apr 26 05:36:10 192.168.122.209 [48720.868167] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:36:11 192.168.122.209 [48722.287512] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48722.287512] Maybe that's fine, but it's worth checking the [48722.287512] config - if there is no relations between the [48722.287512] names, then host name confusion attack is possible. Apr 26 05:36:11 192.168.122.209 [48722.414304] [tempesta fw] Configuration processing is completed. Apr 26 05:36:12 192.168.122.209 [48722.466630] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:36:12 192.168.122.209 [48722.896587] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:36:12 192.168.122.209 [48722.921878] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:36:12 192.168.122.209 [48722.947316] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:36:12 192.168.122.209 [48722.990192] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:36:12 192.168.122.209 [48722.991584] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:36:12 192.168.122.209 [48723.030182] [tempesta fw] Tempesta FW is ready Apr 26 05:36:13 192.168.122.209 [48723.607781] [tdb] Close table 'client0.tdb' Apr 26 05:36:13 192.168.122.209 [48723.795840] [tdb] Close table 'sessions0.tdb' Apr 26 05:36:16 192.168.122.209 [48726.978808] [tdb] Close table 'cache0.tdb' Apr 26 05:36:16 192.168.122.209 [48727.201401] [tdb] Close table 'filter0.tdb' Apr 26 05:36:16 192.168.122.209 [48727.201833] [tempesta fw] modules are stopped Apr 26 05:36:17 192.168.122.209 [48727.456235] [tempesta fw] exiting... Apr 26 05:36:17 192.168.122.209 [48727.602564] [tdb] Shutdown Tempesta DB Apr 26 05:36:17 192.168.122.209 [48727.835287] End test: t_modify_http_headers.test_common_config_h2.TestReqAddHeaderH2.test_add_hdrs_override_config Apr 26 05:36:17 192.168.122.209 [48727.851130] Start test: t_modify_http_headers.test_common_config_h2.TestReqAddHeaderH2.test_add_some_hdrs Apr 26 05:36:18 192.168.122.209 [48728.932355] [tdb] Start Tempesta DB Apr 26 05:36:18 192.168.122.209 [48729.091377] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:36:20 192.168.122.209 [48730.547046] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48730.547046] Maybe that's fine, but it's worth checking the [48730.547046] config - if there is no relations between the [48730.547046] names, then host name confusion attack is possible. Apr 26 05:36:20 192.168.122.209 [48730.686362] [tempesta fw] Configuration processing is completed. Apr 26 05:36:20 192.168.122.209 [48730.742512] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:36:20 192.168.122.209 [48731.148442] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:36:20 192.168.122.209 [48731.175462] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:36:20 192.168.122.209 [48731.203313] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:36:20 192.168.122.209 [48731.246271] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:36:20 192.168.122.209 [48731.247688] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:36:20 192.168.122.209 [48731.290221] [tempesta fw] Tempesta FW is ready Apr 26 05:36:21 192.168.122.209 [48731.865213] [tdb] Close table 'client0.tdb' Apr 26 05:36:21 192.168.122.209 [48732.071539] [tdb] Close table 'sessions0.tdb' Apr 26 05:36:24 192.168.122.209 [48735.259487] [tdb] Close table 'cache0.tdb' Apr 26 05:36:25 192.168.122.209 [48735.473615] [tdb] Close table 'filter0.tdb' Apr 26 05:36:25 192.168.122.209 [48735.474045] [tempesta fw] modules are stopped Apr 26 05:36:25 192.168.122.209 [48735.721708] [tempesta fw] exiting... Apr 26 05:36:25 192.168.122.209 [48735.839588] [tdb] Shutdown Tempesta DB Apr 26 05:36:25 192.168.122.209 [48736.072450] End test: t_modify_http_headers.test_common_config_h2.TestReqAddHeaderH2.test_add_some_hdrs Apr 26 05:36:25 192.168.122.209 [48736.081656] Start test: t_modify_http_headers.test_common_config_h2.TestReqAddHeaderH2.test_add_some_hdrs_custom_location Apr 26 05:36:26 192.168.122.209 [48737.114545] [tdb] Start Tempesta DB Apr 26 05:36:26 192.168.122.209 [48737.251831] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:36:28 192.168.122.209 [48738.667702] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48738.667702] Maybe that's fine, but it's worth checking the [48738.667702] config - if there is no relations between the [48738.667702] names, then host name confusion attack is possible. Apr 26 05:36:28 192.168.122.209 [48738.766468] [tempesta fw] Configuration processing is completed. Apr 26 05:36:28 192.168.122.209 [48738.820506] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:36:28 192.168.122.209 [48739.232697] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:36:28 192.168.122.209 [48739.288243] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:36:28 192.168.122.209 [48739.313601] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:36:28 192.168.122.209 [48739.366412] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:36:28 192.168.122.209 [48739.367793] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:36:28 192.168.122.209 [48739.406383] [tempesta fw] Tempesta FW is ready Apr 26 05:36:29 192.168.122.209 [48739.940892] [tdb] Close table 'client0.tdb' Apr 26 05:36:29 192.168.122.209 [48740.148740] [tdb] Close table 'sessions0.tdb' Apr 26 05:36:32 192.168.122.209 [48743.378376] [tdb] Close table 'cache0.tdb' Apr 26 05:36:33 192.168.122.209 [48743.594952] [tdb] Close table 'filter0.tdb' Apr 26 05:36:33 192.168.122.209 [48743.595386] [tempesta fw] modules are stopped Apr 26 05:36:33 192.168.122.209 [48743.829398] [tempesta fw] exiting... Apr 26 05:36:33 192.168.122.209 [48743.958649] [tdb] Shutdown Tempesta DB Apr 26 05:36:33 192.168.122.209 [48744.183249] End test: t_modify_http_headers.test_common_config_h2.TestReqAddHeaderH2.test_add_some_hdrs_custom_location Apr 26 05:36:33 192.168.122.209 [48744.205683] Start test: t_modify_http_headers.test_common_config_h2.TestReqSetHeaderH2.test_add_hdrs_derive_config Apr 26 05:36:34 192.168.122.209 [48745.216565] [tdb] Start Tempesta DB Apr 26 05:36:34 192.168.122.209 [48745.351019] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:36:36 192.168.122.209 [48746.807881] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48746.807881] Maybe that's fine, but it's worth checking the [48746.807881] config - if there is no relations between the [48746.807881] names, then host name confusion attack is possible. Apr 26 05:36:36 192.168.122.209 [48746.926770] [tempesta fw] Configuration processing is completed. Apr 26 05:36:36 192.168.122.209 [48746.978048] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:36:36 192.168.122.209 [48747.391399] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:36:37 192.168.122.209 [48747.426060] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:36:37 192.168.122.209 [48747.451359] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:36:37 192.168.122.209 [48747.494476] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:36:37 192.168.122.209 [48747.495561] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:36:37 192.168.122.209 [48747.542477] [tempesta fw] Tempesta FW is ready Apr 26 05:36:37 192.168.122.209 [48748.113921] [tdb] Close table 'client0.tdb' Apr 26 05:36:37 192.168.122.209 [48748.298201] [tdb] Close table 'sessions0.tdb' Apr 26 05:36:41 192.168.122.209 [48751.501037] [tdb] Close table 'cache0.tdb' Apr 26 05:36:41 192.168.122.209 [48751.729047] [tdb] Close table 'filter0.tdb' Apr 26 05:36:41 192.168.122.209 [48751.729506] [tempesta fw] modules are stopped Apr 26 05:36:41 192.168.122.209 [48751.947626] [tempesta fw] exiting... Apr 26 05:36:41 192.168.122.209 [48752.077545] [tdb] Shutdown Tempesta DB Apr 26 05:36:41 192.168.122.209 [48752.270468] End test: t_modify_http_headers.test_common_config_h2.TestReqSetHeaderH2.test_add_hdrs_derive_config Apr 26 05:36:41 192.168.122.209 [48752.282775] Start test: t_modify_http_headers.test_common_config_h2.TestReqSetHeaderH2.test_add_hdrs_override_config Apr 26 05:36:42 192.168.122.209 [48753.342061] [tdb] Start Tempesta DB Apr 26 05:36:43 192.168.122.209 [48753.482598] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:36:44 192.168.122.209 [48754.903890] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48754.903890] Maybe that's fine, but it's worth checking the [48754.903890] config - if there is no relations between the [48754.903890] names, then host name confusion attack is possible. Apr 26 05:36:44 192.168.122.209 [48755.026597] [tempesta fw] Configuration processing is completed. Apr 26 05:36:44 192.168.122.209 [48755.080827] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:36:45 192.168.122.209 [48755.544004] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:36:45 192.168.122.209 [48755.610920] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:36:45 192.168.122.209 [48755.641528] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:36:45 192.168.122.209 [48755.686586] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:36:45 192.168.122.209 [48755.687748] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:36:45 192.168.122.209 [48755.726512] [tempesta fw] Tempesta FW is ready Apr 26 05:36:45 192.168.122.209 [48756.306200] [tdb] Close table 'client0.tdb' Apr 26 05:36:46 192.168.122.209 [48756.503760] [tdb] Close table 'sessions0.tdb' Apr 26 05:36:49 192.168.122.209 [48759.768818] [tdb] Close table 'cache0.tdb' Apr 26 05:36:49 192.168.122.209 [48760.034269] [tdb] Close table 'filter0.tdb' Apr 26 05:36:49 192.168.122.209 [48760.035096] [tempesta fw] modules are stopped Apr 26 05:36:49 192.168.122.209 [48760.225029] [tempesta fw] exiting... Apr 26 05:36:49 192.168.122.209 [48760.364328] [tdb] Shutdown Tempesta DB Apr 26 05:36:50 192.168.122.209 [48760.574478] End test: t_modify_http_headers.test_common_config_h2.TestReqSetHeaderH2.test_add_hdrs_override_config Apr 26 05:36:50 192.168.122.209 [48760.590870] Start test: t_modify_http_headers.test_common_config_h2.TestReqSetHeaderH2.test_add_some_hdrs Apr 26 05:36:51 192.168.122.209 [48761.720855] [tdb] Start Tempesta DB Apr 26 05:36:51 192.168.122.209 [48761.878238] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:36:52 192.168.122.209 [48763.367607] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48763.367607] Maybe that's fine, but it's worth checking the [48763.367607] config - if there is no relations between the [48763.367607] names, then host name confusion attack is possible. Apr 26 05:36:53 192.168.122.209 [48763.487077] [tempesta fw] Configuration processing is completed. Apr 26 05:36:53 192.168.122.209 [48763.540717] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:36:53 192.168.122.209 [48764.016497] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:36:53 192.168.122.209 [48764.097374] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:36:53 192.168.122.209 [48764.127895] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:36:53 192.168.122.209 [48764.170732] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:36:53 192.168.122.209 [48764.171944] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:36:53 192.168.122.209 [48764.226703] [tempesta fw] Tempesta FW is ready Apr 26 05:36:54 192.168.122.209 [48764.820137] [tdb] Close table 'client0.tdb' Apr 26 05:36:54 192.168.122.209 [48765.007417] [tdb] Close table 'sessions0.tdb' Apr 26 05:36:57 192.168.122.209 [48768.341432] [tdb] Close table 'cache0.tdb' Apr 26 05:36:58 192.168.122.209 [48768.604932] [tdb] Close table 'filter0.tdb' Apr 26 05:36:58 192.168.122.209 [48768.605390] [tempesta fw] modules are stopped Apr 26 05:36:58 192.168.122.209 [48768.812401] [tempesta fw] exiting... Apr 26 05:36:58 192.168.122.209 [48768.982710] [tdb] Shutdown Tempesta DB Apr 26 05:36:58 192.168.122.209 [48769.192526] End test: t_modify_http_headers.test_common_config_h2.TestReqSetHeaderH2.test_add_some_hdrs Apr 26 05:36:58 192.168.122.209 [48769.207545] Start test: t_modify_http_headers.test_common_config_h2.TestReqSetHeaderH2.test_add_some_hdrs_custom_location Apr 26 05:36:59 192.168.122.209 [48770.297023] [tdb] Start Tempesta DB Apr 26 05:37:00 192.168.122.209 [48770.446817] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:37:01 192.168.122.209 [48771.948164] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48771.948164] Maybe that's fine, but it's worth checking the [48771.948164] config - if there is no relations between the [48771.948164] names, then host name confusion attack is possible. Apr 26 05:37:01 192.168.122.209 [48772.046860] [tempesta fw] Configuration processing is completed. Apr 26 05:37:01 192.168.122.209 [48772.098968] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:37:02 192.168.122.209 [48772.590917] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:37:02 192.168.122.209 [48772.623252] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:37:02 192.168.122.209 [48772.657383] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:37:02 192.168.122.209 [48772.706781] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:37:02 192.168.122.209 [48772.708294] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:37:02 192.168.122.209 [48772.754749] [tempesta fw] Tempesta FW is ready Apr 26 05:37:02 192.168.122.209 [48773.328788] [tdb] Close table 'client0.tdb' Apr 26 05:37:03 192.168.122.209 [48773.515571] [tdb] Close table 'sessions0.tdb' Apr 26 05:37:06 192.168.122.209 [48776.780233] [tdb] Close table 'cache0.tdb' Apr 26 05:37:06 192.168.122.209 [48777.034732] [tdb] Close table 'filter0.tdb' Apr 26 05:37:06 192.168.122.209 [48777.035156] [tempesta fw] modules are stopped Apr 26 05:37:06 192.168.122.209 [48777.210956] [tempesta fw] exiting... Apr 26 05:37:06 192.168.122.209 [48777.392153] [tdb] Shutdown Tempesta DB Apr 26 05:37:07 192.168.122.209 [48777.609944] End test: t_modify_http_headers.test_common_config_h2.TestReqSetHeaderH2.test_add_some_hdrs_custom_location Apr 26 05:37:07 192.168.122.209 [48777.628941] Start test: t_modify_http_headers.test_common_config_h2.TestRespAddHeaderH2.test_add_hdrs_derive_config Apr 26 05:37:08 192.168.122.209 [48778.657346] [tdb] Start Tempesta DB Apr 26 05:37:08 192.168.122.209 [48778.797202] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:37:09 192.168.122.209 [48780.248266] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48780.248266] Maybe that's fine, but it's worth checking the [48780.248266] config - if there is no relations between the [48780.248266] names, then host name confusion attack is possible. Apr 26 05:37:09 192.168.122.209 [48780.375017] [tempesta fw] Configuration processing is completed. Apr 26 05:37:10 192.168.122.209 [48780.425622] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:37:10 192.168.122.209 [48780.853108] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:37:10 192.168.122.209 [48780.911181] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:37:10 192.168.122.209 [48780.938422] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:37:10 192.168.122.209 [48780.982894] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:37:10 192.168.122.209 [48780.983985] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:37:10 192.168.122.209 [48781.026908] [tempesta fw] Tempesta FW is ready Apr 26 05:37:11 192.168.122.209 [48781.557053] [tdb] Close table 'client0.tdb' Apr 26 05:37:11 192.168.122.209 [48781.743595] [tdb] Close table 'sessions0.tdb' Apr 26 05:37:14 192.168.122.209 [48784.995773] [tdb] Close table 'cache0.tdb' Apr 26 05:37:14 192.168.122.209 [48785.228559] [tdb] Close table 'filter0.tdb' Apr 26 05:37:14 192.168.122.209 [48785.229001] [tempesta fw] modules are stopped Apr 26 05:37:15 192.168.122.209 [48785.457023] [tempesta fw] exiting... Apr 26 05:37:15 192.168.122.209 [48785.566557] [tdb] Shutdown Tempesta DB Apr 26 05:37:15 192.168.122.209 [48785.763658] End test: t_modify_http_headers.test_common_config_h2.TestRespAddHeaderH2.test_add_hdrs_derive_config Apr 26 05:37:15 192.168.122.209 [48785.776979] Start test: t_modify_http_headers.test_common_config_h2.TestRespAddHeaderH2.test_add_hdrs_override_config Apr 26 05:37:16 192.168.122.209 [48786.778438] [tdb] Start Tempesta DB Apr 26 05:37:16 192.168.122.209 [48786.903294] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:37:17 192.168.122.209 [48788.272315] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48788.272315] Maybe that's fine, but it's worth checking the [48788.272315] config - if there is no relations between the [48788.272315] names, then host name confusion attack is possible. Apr 26 05:37:17 192.168.122.209 [48788.411107] [tempesta fw] Configuration processing is completed. Apr 26 05:37:18 192.168.122.209 [48788.467422] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:37:18 192.168.122.209 [48788.884417] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:37:18 192.168.122.209 [48788.909743] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:37:18 192.168.122.209 [48788.935479] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:37:18 192.168.122.209 [48788.995056] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:37:18 192.168.122.209 [48788.996798] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:37:18 192.168.122.209 [48789.047004] [tempesta fw] Tempesta FW is ready Apr 26 05:37:19 192.168.122.209 [48789.558410] [tdb] Close table 'client0.tdb' Apr 26 05:37:19 192.168.122.209 [48789.770908] [tdb] Close table 'sessions0.tdb' Apr 26 05:37:22 192.168.122.209 [48792.989813] [tdb] Close table 'cache0.tdb' Apr 26 05:37:22 192.168.122.209 [48793.220671] [tdb] Close table 'filter0.tdb' Apr 26 05:37:22 192.168.122.209 [48793.221071] [tempesta fw] modules are stopped Apr 26 05:37:22 192.168.122.209 [48793.402885] [tempesta fw] exiting... Apr 26 05:37:23 192.168.122.209 [48793.538501] [tdb] Shutdown Tempesta DB Apr 26 05:37:23 192.168.122.209 [48793.757558] End test: t_modify_http_headers.test_common_config_h2.TestRespAddHeaderH2.test_add_hdrs_override_config Apr 26 05:37:23 192.168.122.209 [48793.771376] Start test: t_modify_http_headers.test_common_config_h2.TestRespAddHeaderH2.test_add_some_hdrs Apr 26 05:37:24 192.168.122.209 [48794.823405] [tdb] Start Tempesta DB Apr 26 05:37:24 192.168.122.209 [48794.943899] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:37:25 192.168.122.209 [48796.408434] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48796.408434] Maybe that's fine, but it's worth checking the [48796.408434] config - if there is no relations between the [48796.408434] names, then host name confusion attack is possible. Apr 26 05:37:26 192.168.122.209 [48796.531175] [tempesta fw] Configuration processing is completed. Apr 26 05:37:26 192.168.122.209 [48796.587184] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:37:26 192.168.122.209 [48796.996786] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:37:26 192.168.122.209 [48797.023511] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:37:26 192.168.122.209 [48797.051356] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:37:26 192.168.122.209 [48797.099142] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:37:26 192.168.122.209 [48797.100570] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:37:26 192.168.122.209 [48797.139107] [tempesta fw] Tempesta FW is ready Apr 26 05:37:27 192.168.122.209 [48797.703890] [tdb] Close table 'client0.tdb' Apr 26 05:37:27 192.168.122.209 [48797.896970] [tdb] Close table 'sessions0.tdb' Apr 26 05:37:30 192.168.122.209 [48801.142038] [tdb] Close table 'cache0.tdb' Apr 26 05:37:30 192.168.122.209 [48801.367966] [tdb] Close table 'filter0.tdb' Apr 26 05:37:30 192.168.122.209 [48801.368378] [tempesta fw] modules are stopped Apr 26 05:37:31 192.168.122.209 [48801.538847] [tempesta fw] exiting... Apr 26 05:37:31 192.168.122.209 [48801.698718] [tdb] Shutdown Tempesta DB Apr 26 05:37:31 192.168.122.209 [48801.891706] End test: t_modify_http_headers.test_common_config_h2.TestRespAddHeaderH2.test_add_some_hdrs Apr 26 05:37:31 192.168.122.209 [48801.901096] Start test: t_modify_http_headers.test_common_config_h2.TestRespAddHeaderH2.test_add_some_hdrs_custom_location Apr 26 05:37:32 192.168.122.209 [48802.955404] [tdb] Start Tempesta DB Apr 26 05:37:32 192.168.122.209 [48803.088061] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:37:34 192.168.122.209 [48804.508046] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48804.508046] Maybe that's fine, but it's worth checking the [48804.508046] config - if there is no relations between the [48804.508046] names, then host name confusion attack is possible. Apr 26 05:37:34 192.168.122.209 [48804.611599] [tempesta fw] Configuration processing is completed. Apr 26 05:37:34 192.168.122.209 [48804.663638] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:37:34 192.168.122.209 [48805.071303] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:37:34 192.168.122.209 [48805.128001] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:37:34 192.168.122.209 [48805.159601] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:37:34 192.168.122.209 [48805.219283] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:37:34 192.168.122.209 [48805.221040] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:37:34 192.168.122.209 [48805.259207] [tempesta fw] Tempesta FW is ready Apr 26 05:37:35 192.168.122.209 [48805.828114] [tdb] Close table 'client0.tdb' Apr 26 05:37:35 192.168.122.209 [48806.026334] [tdb] Close table 'sessions0.tdb' Apr 26 05:37:38 192.168.122.209 [48809.208283] [tdb] Close table 'cache0.tdb' Apr 26 05:37:39 192.168.122.209 [48809.440019] [tdb] Close table 'filter0.tdb' Apr 26 05:37:39 192.168.122.209 [48809.440489] [tempesta fw] modules are stopped Apr 26 05:37:39 192.168.122.209 [48809.638723] [tempesta fw] exiting... Apr 26 05:37:39 192.168.122.209 [48809.753614] [tdb] Shutdown Tempesta DB Apr 26 05:37:39 192.168.122.209 [48809.972364] End test: t_modify_http_headers.test_common_config_h2.TestRespAddHeaderH2.test_add_some_hdrs_custom_location Apr 26 05:37:39 192.168.122.209 [48809.992405] Start test: t_modify_http_headers.test_common_config_h2.TestRespSetHeaderH2.test_add_hdrs_derive_config Apr 26 05:37:40 192.168.122.209 [48811.063767] [tdb] Start Tempesta DB Apr 26 05:37:40 192.168.122.209 [48811.211959] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:37:42 192.168.122.209 [48812.632613] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48812.632613] Maybe that's fine, but it's worth checking the [48812.632613] config - if there is no relations between the [48812.632613] names, then host name confusion attack is possible. Apr 26 05:37:42 192.168.122.209 [48812.751400] [tempesta fw] Configuration processing is completed. Apr 26 05:37:42 192.168.122.209 [48812.814660] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:37:42 192.168.122.209 [48813.224468] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:37:42 192.168.122.209 [48813.250523] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:37:42 192.168.122.209 [48813.276110] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:37:42 192.168.122.209 [48813.335387] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:37:42 192.168.122.209 [48813.337046] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:37:42 192.168.122.209 [48813.375328] [tempesta fw] Tempesta FW is ready Apr 26 05:37:43 192.168.122.209 [48813.960052] [tdb] Close table 'client0.tdb' Apr 26 05:37:43 192.168.122.209 [48814.131086] [tdb] Close table 'sessions0.tdb' Apr 26 05:37:46 192.168.122.209 [48817.380965] [tdb] Close table 'cache0.tdb' Apr 26 05:37:47 192.168.122.209 [48817.621023] [tdb] Close table 'filter0.tdb' Apr 26 05:37:47 192.168.122.209 [48817.621448] [tempesta fw] modules are stopped Apr 26 05:37:47 192.168.122.209 [48817.821676] [tempesta fw] exiting... Apr 26 05:37:47 192.168.122.209 [48817.943969] [tdb] Shutdown Tempesta DB Apr 26 05:37:47 192.168.122.209 [48818.159360] End test: t_modify_http_headers.test_common_config_h2.TestRespSetHeaderH2.test_add_hdrs_derive_config Apr 26 05:37:47 192.168.122.209 [48818.174012] Start test: t_modify_http_headers.test_common_config_h2.TestRespSetHeaderH2.test_add_hdrs_override_config Apr 26 05:37:48 192.168.122.209 [48819.209739] [tdb] Start Tempesta DB Apr 26 05:37:48 192.168.122.209 [48819.361889] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:37:50 192.168.122.209 [48820.892806] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48820.892806] Maybe that's fine, but it's worth checking the [48820.892806] config - if there is no relations between the [48820.892806] names, then host name confusion attack is possible. Apr 26 05:37:50 192.168.122.209 [48821.055521] [tempesta fw] Configuration processing is completed. Apr 26 05:37:50 192.168.122.209 [48821.105989] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:37:51 192.168.122.209 [48821.509990] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:37:51 192.168.122.209 [48821.566859] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:37:51 192.168.122.209 [48821.592451] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:37:51 192.168.122.209 [48821.639434] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:37:51 192.168.122.209 [48821.640782] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:37:51 192.168.122.209 [48821.679414] [tempesta fw] Tempesta FW is ready Apr 26 05:37:51 192.168.122.209 [48822.232069] [tdb] Close table 'client0.tdb' Apr 26 05:37:51 192.168.122.209 [48822.419065] [tdb] Close table 'sessions0.tdb' Apr 26 05:37:55 192.168.122.209 [48825.646943] [tdb] Close table 'cache0.tdb' Apr 26 05:37:55 192.168.122.209 [48825.876473] [tdb] Close table 'filter0.tdb' Apr 26 05:37:55 192.168.122.209 [48825.876923] [tempesta fw] modules are stopped Apr 26 05:37:55 192.168.122.209 [48826.127292] [tempesta fw] exiting... Apr 26 05:37:55 192.168.122.209 [48826.243205] [tdb] Shutdown Tempesta DB Apr 26 05:37:56 192.168.122.209 [48826.473083] End test: t_modify_http_headers.test_common_config_h2.TestRespSetHeaderH2.test_add_hdrs_override_config Apr 26 05:37:56 192.168.122.209 [48826.484888] Start test: t_modify_http_headers.test_common_config_h2.TestRespSetHeaderH2.test_add_some_hdrs Apr 26 05:37:57 192.168.122.209 [48827.525148] [tdb] Start Tempesta DB Apr 26 05:37:57 192.168.122.209 [48827.671637] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:37:58 192.168.122.209 [48829.044868] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48829.044868] Maybe that's fine, but it's worth checking the [48829.044868] config - if there is no relations between the [48829.044868] names, then host name confusion attack is possible. Apr 26 05:37:58 192.168.122.209 [48829.167600] [tempesta fw] Configuration processing is completed. Apr 26 05:37:58 192.168.122.209 [48829.220771] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:37:59 192.168.122.209 [48829.632405] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:37:59 192.168.122.209 [48829.658435] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:37:59 192.168.122.209 [48829.684627] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:37:59 192.168.122.209 [48829.739608] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:37:59 192.168.122.209 [48829.741358] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:37:59 192.168.122.209 [48829.799537] [tempesta fw] Tempesta FW is ready Apr 26 05:37:59 192.168.122.209 [48830.380289] [tdb] Close table 'client0.tdb' Apr 26 05:38:00 192.168.122.209 [48830.565788] [tdb] Close table 'sessions0.tdb' Apr 26 05:38:04 192.168.122.209 [48834.853644] [tdb] Close table 'cache0.tdb' Apr 26 05:38:05 192.168.122.209 [48835.444959] [tdb] Close table 'filter0.tdb' Apr 26 05:38:05 192.168.122.209 [48835.445412] [tempesta fw] modules are stopped Apr 26 05:38:07 192.168.122.209 [48837.766791] [tempesta fw] exiting... Apr 26 05:38:07 192.168.122.209 [48837.898523] [tdb] Shutdown Tempesta DB Apr 26 05:38:07 192.168.122.209 [48838.116130] End test: t_modify_http_headers.test_common_config_h2.TestRespSetHeaderH2.test_add_some_hdrs Apr 26 05:38:07 192.168.122.209 [48838.125890] Start test: t_modify_http_headers.test_common_config_h2.TestRespSetHeaderH2.test_add_some_hdrs_custom_location Apr 26 05:38:08 192.168.122.209 [48839.099889] [tdb] Start Tempesta DB Apr 26 05:38:08 192.168.122.209 [48839.237383] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:38:10 192.168.122.209 [48840.645133] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48840.645133] Maybe that's fine, but it's worth checking the [48840.645133] config - if there is no relations between the [48840.645133] names, then host name confusion attack is possible. Apr 26 05:38:10 192.168.122.209 [48840.747749] [tempesta fw] Configuration processing is completed. Apr 26 05:38:10 192.168.122.209 [48840.806909] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:38:10 192.168.122.209 [48841.223428] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:38:10 192.168.122.209 [48841.249447] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:38:10 192.168.122.209 [48841.275328] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:38:10 192.168.122.209 [48841.319636] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:38:10 192.168.122.209 [48841.320430] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:38:10 192.168.122.209 [48841.375665] [tempesta fw] Tempesta FW is ready Apr 26 05:38:11 192.168.122.209 [48841.940768] [tdb] Close table 'client0.tdb' Apr 26 05:38:11 192.168.122.209 [48842.124061] [tdb] Close table 'sessions0.tdb' Apr 26 05:38:14 192.168.122.209 [48845.324995] [tdb] Close table 'cache0.tdb' Apr 26 05:38:15 192.168.122.209 [48845.559048] [tdb] Close table 'filter0.tdb' Apr 26 05:38:15 192.168.122.209 [48845.559488] [tempesta fw] modules are stopped Apr 26 05:38:15 192.168.122.209 [48845.795857] [tempesta fw] exiting... Apr 26 05:38:15 192.168.122.209 [48845.923650] [tdb] Shutdown Tempesta DB Apr 26 05:38:15 192.168.122.209 [48846.126173] End test: t_modify_http_headers.test_common_config_h2.TestRespSetHeaderH2.test_add_some_hdrs_custom_location Apr 26 05:38:15 192.168.122.209 [48846.142678] Start test: t_modify_http_headers.test_logic.TestCachedRespHeader.test_add_non_exist_header Apr 26 05:38:16 192.168.122.209 [48847.187692] [tdb] Start Tempesta DB Apr 26 05:38:16 192.168.122.209 [48847.330400] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:38:18 192.168.122.209 [48848.705118] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48848.705118] Maybe that's fine, but it's worth checking the [48848.705118] config - if there is no relations between the [48848.705118] names, then host name confusion attack is possible. Apr 26 05:38:18 192.168.122.209 [48848.847856] [tempesta fw] Configuration processing is completed. Apr 26 05:38:18 192.168.122.209 [48848.898783] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:38:18 192.168.122.209 [48849.307949] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:38:18 192.168.122.209 [48849.334724] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:38:18 192.168.122.209 [48849.360862] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:38:18 192.168.122.209 [48849.407806] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:38:18 192.168.122.209 [48849.409145] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:38:19 192.168.122.209 [48849.451712] [tempesta fw] Tempesta FW is ready Apr 26 05:38:19 192.168.122.209 [48850.069648] [tdb] Close table 'client0.tdb' Apr 26 05:38:19 192.168.122.209 [48850.260504] [tdb] Close table 'sessions0.tdb' Apr 26 05:38:23 192.168.122.209 [48853.434323] [tdb] Close table 'cache0.tdb' Apr 26 05:38:23 192.168.122.209 [48853.679914] [tdb] Close table 'filter0.tdb' Apr 26 05:38:23 192.168.122.209 [48853.680394] [tempesta fw] modules are stopped Apr 26 05:38:23 192.168.122.209 [48853.872210] [tempesta fw] exiting... Apr 26 05:38:23 192.168.122.209 [48854.006322] [tdb] Shutdown Tempesta DB Apr 26 05:38:23 192.168.122.209 [48854.223552] End test: t_modify_http_headers.test_logic.TestCachedRespHeader.test_add_non_exist_header Apr 26 05:38:23 192.168.122.209 [48854.236106] Start test: t_modify_http_headers.test_logic.TestCachedRespHeader.test_delete_headers Apr 26 05:38:24 192.168.122.209 [48855.310315] [tdb] Start Tempesta DB Apr 26 05:38:25 192.168.122.209 [48855.446665] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:38:26 192.168.122.209 [48856.893230] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48856.893230] Maybe that's fine, but it's worth checking the [48856.893230] config - if there is no relations between the [48856.893230] names, then host name confusion attack is possible. Apr 26 05:38:26 192.168.122.209 [48857.023860] [tempesta fw] Configuration processing is completed. Apr 26 05:38:26 192.168.122.209 [48857.083949] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:38:27 192.168.122.209 [48857.503342] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:38:27 192.168.122.209 [48857.530996] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:38:27 192.168.122.209 [48857.558199] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:38:27 192.168.122.209 [48857.595877] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:38:27 192.168.122.209 [48857.597076] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:38:27 192.168.122.209 [48857.643868] [tempesta fw] Tempesta FW is ready Apr 26 05:38:27 192.168.122.209 [48858.212680] [tdb] Close table 'client0.tdb' Apr 26 05:38:27 192.168.122.209 [48858.396851] [tdb] Close table 'sessions0.tdb' Apr 26 05:38:31 192.168.122.209 [48861.673178] [tdb] Close table 'cache0.tdb' Apr 26 05:38:31 192.168.122.209 [48861.905660] [tdb] Close table 'filter0.tdb' Apr 26 05:38:31 192.168.122.209 [48861.906088] [tempesta fw] modules are stopped Apr 26 05:38:31 192.168.122.209 [48862.129307] [tempesta fw] exiting... Apr 26 05:38:31 192.168.122.209 [48862.248123] [tdb] Shutdown Tempesta DB Apr 26 05:38:32 192.168.122.209 [48862.451973] End test: t_modify_http_headers.test_logic.TestCachedRespHeader.test_delete_headers Apr 26 05:38:32 192.168.122.209 [48862.469972] Start test: t_modify_http_headers.test_logic.TestCachedRespHeader.test_delete_many_headers Apr 26 05:38:33 192.168.122.209 [48863.541705] [tdb] Start Tempesta DB Apr 26 05:38:33 192.168.122.209 [48863.682297] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:38:34 192.168.122.209 [48865.161097] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48865.161097] Maybe that's fine, but it's worth checking the [48865.161097] config - if there is no relations between the [48865.161097] names, then host name confusion attack is possible. Apr 26 05:38:34 192.168.122.209 [48865.300084] [tempesta fw] Configuration processing is completed. Apr 26 05:38:34 192.168.122.209 [48865.351278] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:38:35 192.168.122.209 [48865.780356] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:38:35 192.168.122.209 [48865.855152] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:38:35 192.168.122.209 [48865.882089] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:38:35 192.168.122.209 [48865.923997] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:38:35 192.168.122.209 [48865.925251] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:38:35 192.168.122.209 [48865.967994] [tempesta fw] Tempesta FW is ready Apr 26 05:38:36 192.168.122.209 [48866.524519] [tdb] Close table 'client0.tdb' Apr 26 05:38:36 192.168.122.209 [48866.715707] [tdb] Close table 'sessions0.tdb' Apr 26 05:38:39 192.168.122.209 [48869.923437] [tdb] Close table 'cache0.tdb' Apr 26 05:38:39 192.168.122.209 [48870.197047] [tdb] Close table 'filter0.tdb' Apr 26 05:38:39 192.168.122.209 [48870.197950] [tempesta fw] modules are stopped Apr 26 05:38:39 192.168.122.209 [48870.390039] [tempesta fw] exiting... Apr 26 05:38:40 192.168.122.209 [48870.512244] [tdb] Shutdown Tempesta DB Apr 26 05:38:40 192.168.122.209 [48870.757792] End test: t_modify_http_headers.test_logic.TestCachedRespHeader.test_delete_many_headers Apr 26 05:38:40 192.168.122.209 [48870.771414] Start test: t_modify_http_headers.test_logic.TestCachedRespHeader.test_delete_many_special_headers Apr 26 05:38:41 192.168.122.209 [48871.851118] [tdb] Start Tempesta DB Apr 26 05:38:41 192.168.122.209 [48872.007721] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:38:43 192.168.122.209 [48873.501628] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48873.501628] Maybe that's fine, but it's worth checking the [48873.501628] config - if there is no relations between the [48873.501628] names, then host name confusion attack is possible. Apr 26 05:38:43 192.168.122.209 [48873.640166] [tempesta fw] Configuration processing is completed. Apr 26 05:38:43 192.168.122.209 [48873.699034] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:38:43 192.168.122.209 [48874.123805] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:38:43 192.168.122.209 [48874.149988] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:38:43 192.168.122.209 [48874.175996] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:38:43 192.168.122.209 [48874.216035] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:38:43 192.168.122.209 [48874.217199] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:38:43 192.168.122.209 [48874.264109] [tempesta fw] Tempesta FW is ready Apr 26 05:38:44 192.168.122.209 [48874.872645] [tdb] Close table 'client0.tdb' Apr 26 05:38:44 192.168.122.209 [48875.107704] [tdb] Close table 'sessions0.tdb' Apr 26 05:38:47 192.168.122.209 [48878.362966] [tdb] Close table 'cache0.tdb' Apr 26 05:38:48 192.168.122.209 [48878.614998] [tdb] Close table 'filter0.tdb' Apr 26 05:38:48 192.168.122.209 [48878.615424] [tempesta fw] modules are stopped Apr 26 05:38:48 192.168.122.209 [48878.809966] [tempesta fw] exiting... Apr 26 05:38:48 192.168.122.209 [48878.932559] [tdb] Shutdown Tempesta DB Apr 26 05:38:48 192.168.122.209 [48879.127512] End test: t_modify_http_headers.test_logic.TestCachedRespHeader.test_delete_many_special_headers Apr 26 05:38:48 192.168.122.209 [48879.147303] Start test: t_modify_http_headers.test_logic.TestCachedRespHeader.test_delete_non_exist_header Apr 26 05:38:49 192.168.122.209 [48880.218895] [tdb] Start Tempesta DB Apr 26 05:38:49 192.168.122.209 [48880.369101] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:38:51 192.168.122.209 [48881.825514] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48881.825514] Maybe that's fine, but it's worth checking the [48881.825514] config - if there is no relations between the [48881.825514] names, then host name confusion attack is possible. Apr 26 05:38:51 192.168.122.209 [48881.964595] [tempesta fw] Configuration processing is completed. Apr 26 05:38:51 192.168.122.209 [48882.019145] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:38:52 192.168.122.209 [48882.437525] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:38:52 192.168.122.209 [48882.500114] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:38:52 192.168.122.209 [48882.525766] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:38:52 192.168.122.209 [48882.580237] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:38:52 192.168.122.209 [48882.581980] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:38:52 192.168.122.209 [48882.620196] [tempesta fw] Tempesta FW is ready Apr 26 05:38:52 192.168.122.209 [48883.194164] [tdb] Close table 'client0.tdb' Apr 26 05:38:52 192.168.122.209 [48883.375548] [tdb] Close table 'sessions0.tdb' Apr 26 05:38:56 192.168.122.209 [48886.593843] [tdb] Close table 'cache0.tdb' Apr 26 05:38:56 192.168.122.209 [48886.845167] [tdb] Close table 'filter0.tdb' Apr 26 05:38:56 192.168.122.209 [48886.845607] [tempesta fw] modules are stopped Apr 26 05:38:56 192.168.122.209 [48887.069501] [tempesta fw] exiting... Apr 26 05:38:56 192.168.122.209 [48887.231032] [tdb] Shutdown Tempesta DB Apr 26 05:38:57 192.168.122.209 [48887.442579] End test: t_modify_http_headers.test_logic.TestCachedRespHeader.test_delete_non_exist_header Apr 26 05:38:57 192.168.122.209 [48887.452401] Start test: t_modify_http_headers.test_logic.TestCachedRespHeader.test_delete_special_headers Apr 26 05:38:58 192.168.122.209 [48888.480025] [tdb] Start Tempesta DB Apr 26 05:38:58 192.168.122.209 [48888.627079] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:38:59 192.168.122.209 [48890.129574] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48890.129574] Maybe that's fine, but it's worth checking the [48890.129574] config - if there is no relations between the [48890.129574] names, then host name confusion attack is possible. Apr 26 05:38:59 192.168.122.209 [48890.276283] [tempesta fw] Configuration processing is completed. Apr 26 05:38:59 192.168.122.209 [48890.336662] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:39:00 192.168.122.209 [48890.810158] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:39:00 192.168.122.209 [48890.838649] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:39:00 192.168.122.209 [48890.867973] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:39:00 192.168.122.209 [48890.920386] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:39:00 192.168.122.209 [48890.922008] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:39:00 192.168.122.209 [48890.972291] [tempesta fw] Tempesta FW is ready Apr 26 05:39:01 192.168.122.209 [48891.548987] [tdb] Close table 'client0.tdb' Apr 26 05:39:01 192.168.122.209 [48891.741019] [tdb] Close table 'sessions0.tdb' Apr 26 05:39:04 192.168.122.209 [48894.968790] [tdb] Close table 'cache0.tdb' Apr 26 05:39:04 192.168.122.209 [48895.188026] [tdb] Close table 'filter0.tdb' Apr 26 05:39:04 192.168.122.209 [48895.188480] [tempesta fw] modules are stopped Apr 26 05:39:04 192.168.122.209 [48895.410143] [tempesta fw] exiting... Apr 26 05:39:05 192.168.122.209 [48895.564296] [tdb] Shutdown Tempesta DB Apr 26 05:39:05 192.168.122.209 [48895.786836] End test: t_modify_http_headers.test_logic.TestCachedRespHeader.test_delete_special_headers Apr 26 05:39:05 192.168.122.209 [48895.801591] Start test: t_modify_http_headers.test_logic.TestCachedRespHeader.test_long_header_name Apr 26 05:39:06 192.168.122.209 [48896.871681] [tdb] Start Tempesta DB Apr 26 05:39:06 192.168.122.209 [48897.002692] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:39:07 192.168.122.209 [48898.397697] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48898.397697] Maybe that's fine, but it's worth checking the [48898.397697] config - if there is no relations between the [48898.397697] names, then host name confusion attack is possible. Apr 26 05:39:08 192.168.122.209 [48898.532452] [tempesta fw] Configuration processing is completed. Apr 26 05:39:08 192.168.122.209 [48898.583393] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:39:08 192.168.122.209 [48898.996836] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:39:08 192.168.122.209 [48899.023259] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:39:08 192.168.122.209 [48899.050612] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:39:08 192.168.122.209 [48899.104449] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:39:08 192.168.122.209 [48899.106068] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:39:08 192.168.122.209 [48899.152408] [tempesta fw] Tempesta FW is ready Apr 26 05:39:09 192.168.122.209 [48899.727607] [tdb] Close table 'client0.tdb' Apr 26 05:39:09 192.168.122.209 [48899.902803] [tdb] Close table 'sessions0.tdb' Apr 26 05:39:12 192.168.122.209 [48903.213482] [tdb] Close table 'cache0.tdb' Apr 26 05:39:13 192.168.122.209 [48903.455952] [tdb] Close table 'filter0.tdb' Apr 26 05:39:13 192.168.122.209 [48903.457102] [tempesta fw] modules are stopped Apr 26 05:39:13 192.168.122.209 [48903.640024] [tempesta fw] exiting... Apr 26 05:39:13 192.168.122.209 [48903.767803] [tdb] Shutdown Tempesta DB Apr 26 05:39:13 192.168.122.209 [48903.977901] End test: t_modify_http_headers.test_logic.TestCachedRespHeader.test_long_header_name Apr 26 05:39:13 192.168.122.209 [48903.990898] Start test: t_modify_http_headers.test_logic.TestCachedRespHeader.test_set_exist_header Apr 26 05:39:14 192.168.122.209 [48905.033106] [tdb] Start Tempesta DB Apr 26 05:39:14 192.168.122.209 [48905.184660] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:39:16 192.168.122.209 [48906.677049] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48906.677049] Maybe that's fine, but it's worth checking the [48906.677049] config - if there is no relations between the [48906.677049] names, then host name confusion attack is possible. Apr 26 05:39:16 192.168.122.209 [48906.812588] [tempesta fw] Configuration processing is completed. Apr 26 05:39:16 192.168.122.209 [48906.862942] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:39:16 192.168.122.209 [48907.296298] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:39:16 192.168.122.209 [48907.323400] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:39:16 192.168.122.209 [48907.350787] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:39:16 192.168.122.209 [48907.396514] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:39:16 192.168.122.209 [48907.397539] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:39:17 192.168.122.209 [48907.436581] [tempesta fw] Tempesta FW is ready Apr 26 05:39:17 192.168.122.209 [48907.983298] [tdb] Close table 'client0.tdb' Apr 26 05:39:17 192.168.122.209 [48908.190808] [tdb] Close table 'sessions0.tdb' Apr 26 05:39:21 192.168.122.209 [48911.428978] [tdb] Close table 'cache0.tdb' Apr 26 05:39:21 192.168.122.209 [48911.681845] [tdb] Close table 'filter0.tdb' Apr 26 05:39:21 192.168.122.209 [48911.682294] [tempesta fw] modules are stopped Apr 26 05:39:21 192.168.122.209 [48911.893780] [tempesta fw] exiting... Apr 26 05:39:21 192.168.122.209 [48912.030767] [tdb] Shutdown Tempesta DB Apr 26 05:39:21 192.168.122.209 [48912.270517] End test: t_modify_http_headers.test_logic.TestCachedRespHeader.test_set_exist_header Apr 26 05:39:21 192.168.122.209 [48912.283808] Start test: t_modify_http_headers.test_logic.TestCachedRespHeader.test_set_exist_special_header Apr 26 05:39:22 192.168.122.209 [48913.377726] [tdb] Start Tempesta DB Apr 26 05:39:23 192.168.122.209 [48913.526575] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:39:24 192.168.122.209 [48914.949961] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48914.949961] Maybe that's fine, but it's worth checking the [48914.949961] config - if there is no relations between the [48914.949961] names, then host name confusion attack is possible. Apr 26 05:39:24 192.168.122.209 [48915.092994] [tempesta fw] Configuration processing is completed. Apr 26 05:39:24 192.168.122.209 [48915.144367] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:39:25 192.168.122.209 [48915.674828] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:39:25 192.168.122.209 [48915.709824] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:39:25 192.168.122.209 [48915.744143] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:39:25 192.168.122.209 [48915.792630] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:39:25 192.168.122.209 [48915.794043] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:39:25 192.168.122.209 [48915.844629] [tempesta fw] Tempesta FW is ready Apr 26 05:39:25 192.168.122.209 [48916.412693] [tdb] Close table 'client0.tdb' Apr 26 05:39:26 192.168.122.209 [48916.613965] [tdb] Close table 'sessions0.tdb' Apr 26 05:39:29 192.168.122.209 [48919.816155] [tdb] Close table 'cache0.tdb' Apr 26 05:39:29 192.168.122.209 [48920.041889] [tdb] Close table 'filter0.tdb' Apr 26 05:39:29 192.168.122.209 [48920.042334] [tempesta fw] modules are stopped Apr 26 05:39:29 192.168.122.209 [48920.220291] [tempesta fw] exiting... Apr 26 05:39:29 192.168.122.209 [48920.363044] [tdb] Shutdown Tempesta DB Apr 26 05:39:30 192.168.122.209 [48920.579694] End test: t_modify_http_headers.test_logic.TestCachedRespHeader.test_set_exist_special_header Apr 26 05:39:30 192.168.122.209 [48920.596756] Start test: t_modify_http_headers.test_logic.TestCachedRespHeader.test_set_header_name_greater_than_1024 Apr 26 05:39:31 192.168.122.209 [48921.655630] [tdb] Start Tempesta DB Apr 26 05:39:31 192.168.122.209 [48921.791353] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:39:32 192.168.122.209 [48923.194045] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48923.194045] Maybe that's fine, but it's worth checking the [48923.194045] config - if there is no relations between the [48923.194045] names, then host name confusion attack is possible. Apr 26 05:39:32 192.168.122.209 [48923.333198] [tempesta fw] Configuration processing is completed. Apr 26 05:39:32 192.168.122.209 [48923.398567] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:39:33 192.168.122.209 [48923.831942] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:39:33 192.168.122.209 [48923.858502] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:39:33 192.168.122.209 [48923.885204] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:39:33 192.168.122.209 [48923.932696] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:39:33 192.168.122.209 [48923.933892] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:39:33 192.168.122.209 [48923.980645] [tempesta fw] Tempesta FW is ready Apr 26 05:39:34 192.168.122.209 [48924.552500] [tdb] Close table 'client0.tdb' Apr 26 05:39:34 192.168.122.209 [48924.731903] [tdb] Close table 'sessions0.tdb' Apr 26 05:39:37 192.168.122.209 [48927.936586] [tdb] Close table 'cache0.tdb' Apr 26 05:39:37 192.168.122.209 [48928.173187] [tdb] Close table 'filter0.tdb' Apr 26 05:39:37 192.168.122.209 [48928.174461] [tempesta fw] modules are stopped Apr 26 05:39:37 192.168.122.209 [48928.414042] [tempesta fw] exiting... Apr 26 05:39:38 192.168.122.209 [48928.506917] [tdb] Shutdown Tempesta DB Apr 26 05:39:38 192.168.122.209 [48928.739896] End test: t_modify_http_headers.test_logic.TestCachedRespHeader.test_set_header_name_greater_than_1024 Apr 26 05:39:38 192.168.122.209 [48928.752722] Start test: t_modify_http_headers.test_logic.TestCachedRespHeader.test_set_large_header Apr 26 05:39:39 192.168.122.209 [48929.823601] [tdb] Start Tempesta DB Apr 26 05:39:39 192.168.122.209 [48929.970895] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:39:40 192.168.122.209 [48931.398123] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48931.398123] Maybe that's fine, but it's worth checking the [48931.398123] config - if there is no relations between the [48931.398123] names, then host name confusion attack is possible. Apr 26 05:39:41 192.168.122.209 [48931.540878] [tempesta fw] Configuration processing is completed. Apr 26 05:39:41 192.168.122.209 [48931.603245] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:39:41 192.168.122.209 [48931.999268] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:39:41 192.168.122.209 [48932.024665] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:39:41 192.168.122.209 [48932.050310] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:39:41 192.168.122.209 [48932.088866] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:39:41 192.168.122.209 [48932.090597] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:39:41 192.168.122.209 [48932.132807] [tempesta fw] Tempesta FW is ready Apr 26 05:39:42 192.168.122.209 [48932.720141] [tdb] Close table 'client0.tdb' Apr 26 05:39:42 192.168.122.209 [48932.901865] [tdb] Close table 'sessions0.tdb' Apr 26 05:39:45 192.168.122.209 [48936.071975] [tdb] Close table 'cache0.tdb' Apr 26 05:39:45 192.168.122.209 [48936.308867] [tdb] Close table 'filter0.tdb' Apr 26 05:39:45 192.168.122.209 [48936.309286] [tempesta fw] modules are stopped Apr 26 05:39:46 192.168.122.209 [48936.530281] [tempesta fw] exiting... Apr 26 05:39:46 192.168.122.209 [48936.662095] [tdb] Shutdown Tempesta DB Apr 26 05:39:46 192.168.122.209 [48936.879615] End test: t_modify_http_headers.test_logic.TestCachedRespHeader.test_set_large_header Apr 26 05:39:46 192.168.122.209 [48936.894636] Start test: t_modify_http_headers.test_logic.TestCachedRespHeader.test_set_long_header_name Apr 26 05:39:47 192.168.122.209 [48937.882673] [tdb] Start Tempesta DB Apr 26 05:39:47 192.168.122.209 [48938.012387] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:39:49 192.168.122.209 [48939.466264] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48939.466264] Maybe that's fine, but it's worth checking the [48939.466264] config - if there is no relations between the [48939.466264] names, then host name confusion attack is possible. Apr 26 05:39:49 192.168.122.209 [48939.688940] [tempesta fw] Configuration processing is completed. Apr 26 05:39:49 192.168.122.209 [48939.741573] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:39:49 192.168.122.209 [48940.158990] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:39:49 192.168.122.209 [48940.185090] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:39:49 192.168.122.209 [48940.212515] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:39:49 192.168.122.209 [48940.276970] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:39:49 192.168.122.209 [48940.278698] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:39:49 192.168.122.209 [48940.316929] [tempesta fw] Tempesta FW is ready Apr 26 05:39:50 192.168.122.209 [48940.899930] [tdb] Close table 'client0.tdb' Apr 26 05:39:50 192.168.122.209 [48941.086487] [tdb] Close table 'sessions0.tdb' Apr 26 05:39:53 192.168.122.209 [48944.281989] [tdb] Close table 'cache0.tdb' Apr 26 05:39:54 192.168.122.209 [48944.536001] [tdb] Close table 'filter0.tdb' Apr 26 05:39:54 192.168.122.209 [48944.536432] [tempesta fw] modules are stopped Apr 26 05:39:54 192.168.122.209 [48944.738966] [tempesta fw] exiting... Apr 26 05:39:54 192.168.122.209 [48944.871855] [tdb] Shutdown Tempesta DB Apr 26 05:39:54 192.168.122.209 [48945.062388] End test: t_modify_http_headers.test_logic.TestCachedRespHeader.test_set_long_header_name Apr 26 05:39:54 192.168.122.209 [48945.075607] Start test: t_modify_http_headers.test_logic.TestCachedRespHeader.test_set_non_exist_header Apr 26 05:39:55 192.168.122.209 [48946.150608] [tdb] Start Tempesta DB Apr 26 05:39:55 192.168.122.209 [48946.295924] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:39:57 192.168.122.209 [48947.730335] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48947.730335] Maybe that's fine, but it's worth checking the [48947.730335] config - if there is no relations between the [48947.730335] names, then host name confusion attack is possible. Apr 26 05:39:57 192.168.122.209 [48947.881084] [tempesta fw] Configuration processing is completed. Apr 26 05:39:57 192.168.122.209 [48947.928124] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:39:57 192.168.122.209 [48948.346843] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:39:57 192.168.122.209 [48948.381400] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:39:57 192.168.122.209 [48948.407085] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:39:58 192.168.122.209 [48948.445068] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:39:58 192.168.122.209 [48948.446831] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:39:58 192.168.122.209 [48948.505031] [tempesta fw] Tempesta FW is ready Apr 26 05:39:58 192.168.122.209 [48949.064991] [tdb] Close table 'client0.tdb' Apr 26 05:39:58 192.168.122.209 [48949.256986] [tdb] Close table 'sessions0.tdb' Apr 26 05:40:02 192.168.122.209 [48952.443980] [tdb] Close table 'cache0.tdb' Apr 26 05:40:02 192.168.122.209 [48952.675996] [tdb] Close table 'filter0.tdb' Apr 26 05:40:02 192.168.122.209 [48952.676421] [tempesta fw] modules are stopped Apr 26 05:40:02 192.168.122.209 [48952.871451] [tempesta fw] exiting... Apr 26 05:40:02 192.168.122.209 [48953.017676] [tdb] Shutdown Tempesta DB Apr 26 05:40:02 192.168.122.209 [48953.274909] End test: t_modify_http_headers.test_logic.TestCachedRespHeader.test_set_non_exist_header Apr 26 05:40:02 192.168.122.209 [48953.293704] Start test: t_modify_http_headers.test_logic.TestCachedRespHeaderH2.test_add_header_from_static_table Apr 26 05:40:03 192.168.122.209 [48954.344031] [tdb] Start Tempesta DB Apr 26 05:40:04 192.168.122.209 [48954.483499] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:40:05 192.168.122.209 [48955.922413] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48955.922413] Maybe that's fine, but it's worth checking the [48955.922413] config - if there is no relations between the [48955.922413] names, then host name confusion attack is possible. Apr 26 05:40:05 192.168.122.209 [48956.041197] [tempesta fw] Configuration processing is completed. Apr 26 05:40:05 192.168.122.209 [48956.093279] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:40:06 192.168.122.209 [48956.502480] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:40:06 192.168.122.209 [48956.559410] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:40:06 192.168.122.209 [48956.585356] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:40:06 192.168.122.209 [48956.633089] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:40:06 192.168.122.209 [48956.633863] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:40:06 192.168.122.209 [48956.681089] [tempesta fw] Tempesta FW is ready Apr 26 05:40:06 192.168.122.209 [48957.260034] [tdb] Close table 'client0.tdb' Apr 26 05:40:07 192.168.122.209 [48957.464377] [tdb] Close table 'sessions0.tdb' Apr 26 05:40:10 192.168.122.209 [48960.667146] [tdb] Close table 'cache0.tdb' Apr 26 05:40:10 192.168.122.209 [48960.891415] [tdb] Close table 'filter0.tdb' Apr 26 05:40:10 192.168.122.209 [48960.891847] [tempesta fw] modules are stopped Apr 26 05:40:10 192.168.122.209 [48961.134059] [tempesta fw] exiting... Apr 26 05:40:10 192.168.122.209 [48961.301107] [tdb] Shutdown Tempesta DB Apr 26 05:40:11 192.168.122.209 [48961.528579] End test: t_modify_http_headers.test_logic.TestCachedRespHeaderH2.test_add_header_from_static_table Apr 26 05:40:11 192.168.122.209 [48961.536413] Start test: t_modify_http_headers.test_logic.TestCachedRespHeaderH2.test_add_non_exist_header Apr 26 05:40:12 192.168.122.209 [48962.626633] [tdb] Start Tempesta DB Apr 26 05:40:12 192.168.122.209 [48962.765018] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:40:13 192.168.122.209 [48964.194568] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48964.194568] Maybe that's fine, but it's worth checking the [48964.194568] config - if there is no relations between the [48964.194568] names, then host name confusion attack is possible. Apr 26 05:40:13 192.168.122.209 [48964.345221] [tempesta fw] Configuration processing is completed. Apr 26 05:40:13 192.168.122.209 [48964.397276] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:40:14 192.168.122.209 [48964.820543] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:40:14 192.168.122.209 [48964.846743] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:40:14 192.168.122.209 [48964.881625] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:40:14 192.168.122.209 [48964.929879] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:40:14 192.168.122.209 [48964.931610] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:40:14 192.168.122.209 [48964.969219] [tempesta fw] Tempesta FW is ready Apr 26 05:40:15 192.168.122.209 [48965.494192] [tdb] Close table 'client0.tdb' Apr 26 05:40:15 192.168.122.209 [48965.698321] [tdb] Close table 'sessions0.tdb' Apr 26 05:40:18 192.168.122.209 [48968.879805] [tdb] Close table 'cache0.tdb' Apr 26 05:40:18 192.168.122.209 [48969.110255] [tdb] Close table 'filter0.tdb' Apr 26 05:40:18 192.168.122.209 [48969.110695] [tempesta fw] modules are stopped Apr 26 05:40:18 192.168.122.209 [48969.294349] [tempesta fw] exiting... Apr 26 05:40:19 192.168.122.209 [48969.452858] [tdb] Shutdown Tempesta DB Apr 26 05:40:19 192.168.122.209 [48969.644310] End test: t_modify_http_headers.test_logic.TestCachedRespHeaderH2.test_add_non_exist_header Apr 26 05:40:19 192.168.122.209 [48969.656114] Start test: t_modify_http_headers.test_logic.TestCachedRespHeaderH2.test_delete_headers Apr 26 05:40:20 192.168.122.209 [48970.662875] [tdb] Start Tempesta DB Apr 26 05:40:20 192.168.122.209 [48970.795563] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:40:21 192.168.122.209 [48972.246902] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48972.246902] Maybe that's fine, but it's worth checking the [48972.246902] config - if there is no relations between the [48972.246902] names, then host name confusion attack is possible. Apr 26 05:40:21 192.168.122.209 [48972.389387] [tempesta fw] Configuration processing is completed. Apr 26 05:40:22 192.168.122.209 [48972.445880] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:40:22 192.168.122.209 [48972.854375] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:40:22 192.168.122.209 [48972.916316] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:40:22 192.168.122.209 [48972.942366] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:40:22 192.168.122.209 [48972.989352] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:40:22 192.168.122.209 [48972.990731] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:40:22 192.168.122.209 [48973.029337] [tempesta fw] Tempesta FW is ready Apr 26 05:40:23 192.168.122.209 [48973.583029] [tdb] Close table 'client0.tdb' Apr 26 05:40:23 192.168.122.209 [48973.793554] [tdb] Close table 'sessions0.tdb' Apr 26 05:40:26 192.168.122.209 [48977.042150] [tdb] Close table 'cache0.tdb' Apr 26 05:40:26 192.168.122.209 [48977.313985] [tdb] Close table 'filter0.tdb' Apr 26 05:40:26 192.168.122.209 [48977.314426] [tempesta fw] modules are stopped Apr 26 05:40:27 192.168.122.209 [48977.525665] [tempesta fw] exiting... Apr 26 05:40:27 192.168.122.209 [48977.662997] [tdb] Shutdown Tempesta DB Apr 26 05:40:27 192.168.122.209 [48977.899579] End test: t_modify_http_headers.test_logic.TestCachedRespHeaderH2.test_delete_headers Apr 26 05:40:27 192.168.122.209 [48977.912494] Start test: t_modify_http_headers.test_logic.TestCachedRespHeaderH2.test_delete_many_headers Apr 26 05:40:28 192.168.122.209 [48978.991035] [tdb] Start Tempesta DB Apr 26 05:40:28 192.168.122.209 [48979.131639] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:40:30 192.168.122.209 [48980.518710] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48980.518710] Maybe that's fine, but it's worth checking the [48980.518710] config - if there is no relations between the [48980.518710] names, then host name confusion attack is possible. Apr 26 05:40:30 192.168.122.209 [48980.653509] [tempesta fw] Configuration processing is completed. Apr 26 05:40:30 192.168.122.209 [48980.710084] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:40:30 192.168.122.209 [48981.127185] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:40:30 192.168.122.209 [48981.153030] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:40:30 192.168.122.209 [48981.178750] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:40:30 192.168.122.209 [48981.225445] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:40:30 192.168.122.209 [48981.227033] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:40:30 192.168.122.209 [48981.273401] [tempesta fw] Tempesta FW is ready Apr 26 05:40:31 192.168.122.209 [48981.820714] [tdb] Close table 'client0.tdb' Apr 26 05:40:31 192.168.122.209 [48982.025302] [tdb] Close table 'sessions0.tdb' Apr 26 05:40:34 192.168.122.209 [48985.391035] [tdb] Close table 'cache0.tdb' Apr 26 05:40:35 192.168.122.209 [48985.605930] [tdb] Close table 'filter0.tdb' Apr 26 05:40:35 192.168.122.209 [48985.606372] [tempesta fw] modules are stopped Apr 26 05:40:35 192.168.122.209 [48985.799642] [tempesta fw] exiting... Apr 26 05:40:35 192.168.122.209 [48985.914753] [tdb] Shutdown Tempesta DB Apr 26 05:40:35 192.168.122.209 [48986.110904] End test: t_modify_http_headers.test_logic.TestCachedRespHeaderH2.test_delete_many_headers Apr 26 05:40:35 192.168.122.209 [48986.121505] Start test: t_modify_http_headers.test_logic.TestCachedRespHeaderH2.test_delete_many_special_headers Apr 26 05:40:36 192.168.122.209 [48987.141945] [tdb] Start Tempesta DB Apr 26 05:40:36 192.168.122.209 [48987.283497] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:40:38 192.168.122.209 [48988.758889] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48988.758889] Maybe that's fine, but it's worth checking the [48988.758889] config - if there is no relations between the [48988.758889] names, then host name confusion attack is possible. Apr 26 05:40:38 192.168.122.209 [48988.897614] [tempesta fw] Configuration processing is completed. Apr 26 05:40:38 192.168.122.209 [48988.955025] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:40:38 192.168.122.209 [48989.359425] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:40:38 192.168.122.209 [48989.385702] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:40:38 192.168.122.209 [48989.412876] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:40:39 192.168.122.209 [48989.461564] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:40:39 192.168.122.209 [48989.463056] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:40:39 192.168.122.209 [48989.505554] [tempesta fw] Tempesta FW is ready Apr 26 05:40:39 192.168.122.209 [48990.159576] [tdb] Close table 'client0.tdb' Apr 26 05:40:39 192.168.122.209 [48990.346283] [tdb] Close table 'sessions0.tdb' Apr 26 05:40:43 192.168.122.209 [48993.623720] [tdb] Close table 'cache0.tdb' Apr 26 05:40:43 192.168.122.209 [48993.837623] [tdb] Close table 'filter0.tdb' Apr 26 05:40:43 192.168.122.209 [48993.838068] [tempesta fw] modules are stopped Apr 26 05:40:43 192.168.122.209 [48994.038101] [tempesta fw] exiting... Apr 26 05:40:43 192.168.122.209 [48994.149134] [tdb] Shutdown Tempesta DB Apr 26 05:40:43 192.168.122.209 [48994.376270] End test: t_modify_http_headers.test_logic.TestCachedRespHeaderH2.test_delete_many_special_headers Apr 26 05:40:43 192.168.122.209 [48994.388737] Start test: t_modify_http_headers.test_logic.TestCachedRespHeaderH2.test_delete_non_exist_header Apr 26 05:40:45 192.168.122.209 [48995.487333] [tdb] Start Tempesta DB Apr 26 05:40:45 192.168.122.209 [48995.631487] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:40:46 192.168.122.209 [48997.110701] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [48997.110701] Maybe that's fine, but it's worth checking the [48997.110701] config - if there is no relations between the [48997.110701] names, then host name confusion attack is possible. Apr 26 05:40:46 192.168.122.209 [48997.257706] [tempesta fw] Configuration processing is completed. Apr 26 05:40:46 192.168.122.209 [48997.308155] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:40:47 192.168.122.209 [48997.723483] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:40:47 192.168.122.209 [48997.750463] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:40:47 192.168.122.209 [48997.784704] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:40:47 192.168.122.209 [48997.835026] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:40:47 192.168.122.209 [48997.836748] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:40:47 192.168.122.209 [48997.893652] [tempesta fw] Tempesta FW is ready Apr 26 05:40:48 192.168.122.209 [48998.465451] [tdb] Close table 'client0.tdb' Apr 26 05:40:48 192.168.122.209 [48998.653177] [tdb] Close table 'sessions0.tdb' Apr 26 05:40:51 192.168.122.209 [49001.836276] [tdb] Close table 'cache0.tdb' Apr 26 05:40:51 192.168.122.209 [49002.065474] [tdb] Close table 'filter0.tdb' Apr 26 05:40:51 192.168.122.209 [49002.066004] [tempesta fw] modules are stopped Apr 26 05:40:51 192.168.122.209 [49002.291250] [tempesta fw] exiting... Apr 26 05:40:52 192.168.122.209 [49002.444006] [tdb] Shutdown Tempesta DB Apr 26 05:40:52 192.168.122.209 [49002.652336] End test: t_modify_http_headers.test_logic.TestCachedRespHeaderH2.test_delete_non_exist_header Apr 26 05:40:52 192.168.122.209 [49002.672802] Start test: t_modify_http_headers.test_logic.TestCachedRespHeaderH2.test_delete_special_headers Apr 26 05:40:53 192.168.122.209 [49003.714306] [tdb] Start Tempesta DB Apr 26 05:40:53 192.168.122.209 [49003.847822] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:40:54 192.168.122.209 [49005.303139] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49005.303139] Maybe that's fine, but it's worth checking the [49005.303139] config - if there is no relations between the [49005.303139] names, then host name confusion attack is possible. Apr 26 05:40:55 192.168.122.209 [49005.453748] [tempesta fw] Configuration processing is completed. Apr 26 05:40:55 192.168.122.209 [49005.505322] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:40:55 192.168.122.209 [49005.910160] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:40:55 192.168.122.209 [49005.936233] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:40:55 192.168.122.209 [49005.964507] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:40:55 192.168.122.209 [49006.001810] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:40:55 192.168.122.209 [49006.003077] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:40:55 192.168.122.209 [49006.061784] [tempesta fw] Tempesta FW is ready Apr 26 05:40:56 192.168.122.209 [49006.602997] [tdb] Close table 'client0.tdb' Apr 26 05:40:56 192.168.122.209 [49006.819901] [tdb] Close table 'sessions0.tdb' Apr 26 05:40:59 192.168.122.209 [49010.050955] [tdb] Close table 'cache0.tdb' Apr 26 05:40:59 192.168.122.209 [49010.284402] [tdb] Close table 'filter0.tdb' Apr 26 05:40:59 192.168.122.209 [49010.284877] [tempesta fw] modules are stopped Apr 26 05:41:00 192.168.122.209 [49010.493858] [tempesta fw] exiting... Apr 26 05:41:00 192.168.122.209 [49010.638739] [tdb] Shutdown Tempesta DB Apr 26 05:41:00 192.168.122.209 [49010.852064] End test: t_modify_http_headers.test_logic.TestCachedRespHeaderH2.test_delete_special_headers Apr 26 05:41:00 192.168.122.209 [49010.864087] Start test: t_modify_http_headers.test_logic.TestCachedRespHeaderH2.test_long_header_name Apr 26 05:41:01 192.168.122.209 [49011.894645] [tdb] Start Tempesta DB Apr 26 05:41:01 192.168.122.209 [49012.031683] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:41:03 192.168.122.209 [49013.483132] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49013.483132] Maybe that's fine, but it's worth checking the [49013.483132] config - if there is no relations between the [49013.483132] names, then host name confusion attack is possible. Apr 26 05:41:03 192.168.122.209 [49013.614026] [tempesta fw] Configuration processing is completed. Apr 26 05:41:03 192.168.122.209 [49013.664550] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:41:03 192.168.122.209 [49014.075273] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:41:03 192.168.122.209 [49014.101935] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:41:03 192.168.122.209 [49014.129248] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:41:03 192.168.122.209 [49014.169898] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:41:03 192.168.122.209 [49014.171637] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:41:03 192.168.122.209 [49014.215164] [tempesta fw] Tempesta FW is ready Apr 26 05:41:04 192.168.122.209 [49014.753705] [tdb] Close table 'client0.tdb' Apr 26 05:41:04 192.168.122.209 [49014.938702] [tdb] Close table 'sessions0.tdb' Apr 26 05:41:07 192.168.122.209 [49018.105203] [tdb] Close table 'cache0.tdb' Apr 26 05:41:07 192.168.122.209 [49018.337553] [tdb] Close table 'filter0.tdb' Apr 26 05:41:07 192.168.122.209 [49018.338005] [tempesta fw] modules are stopped Apr 26 05:41:08 192.168.122.209 [49018.569698] [tempesta fw] exiting... Apr 26 05:41:08 192.168.122.209 [49018.685393] [tdb] Shutdown Tempesta DB Apr 26 05:41:08 192.168.122.209 [49018.931303] End test: t_modify_http_headers.test_logic.TestCachedRespHeaderH2.test_long_header_name Apr 26 05:41:08 192.168.122.209 [49018.942651] Start test: t_modify_http_headers.test_logic.TestCachedRespHeaderH2.test_set_exist_header Apr 26 05:41:09 192.168.122.209 [49019.987777] [tdb] Start Tempesta DB Apr 26 05:41:09 192.168.122.209 [49020.130429] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:41:11 192.168.122.209 [49021.519207] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49021.519207] Maybe that's fine, but it's worth checking the [49021.519207] config - if there is no relations between the [49021.519207] names, then host name confusion attack is possible. Apr 26 05:41:11 192.168.122.209 [49021.658005] [tempesta fw] Configuration processing is completed. Apr 26 05:41:11 192.168.122.209 [49021.709061] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:41:11 192.168.122.209 [49022.108738] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:41:11 192.168.122.209 [49022.134045] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:41:11 192.168.122.209 [49022.159823] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:41:11 192.168.122.209 [49022.221993] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:41:11 192.168.122.209 [49022.223706] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:41:11 192.168.122.209 [49022.265956] [tempesta fw] Tempesta FW is ready Apr 26 05:41:12 192.168.122.209 [49022.851670] [tdb] Close table 'client0.tdb' Apr 26 05:41:12 192.168.122.209 [49023.038101] [tdb] Close table 'sessions0.tdb' Apr 26 05:41:15 192.168.122.209 [49026.185132] [tdb] Close table 'cache0.tdb' Apr 26 05:41:16 192.168.122.209 [49026.431855] [tdb] Close table 'filter0.tdb' Apr 26 05:41:16 192.168.122.209 [49026.432320] [tempesta fw] modules are stopped Apr 26 05:41:16 192.168.122.209 [49026.681434] [tempesta fw] exiting... Apr 26 05:41:16 192.168.122.209 [49026.811223] [tdb] Shutdown Tempesta DB Apr 26 05:41:16 192.168.122.209 [49027.002806] End test: t_modify_http_headers.test_logic.TestCachedRespHeaderH2.test_set_exist_header Apr 26 05:41:16 192.168.122.209 [49027.028918] Start test: t_modify_http_headers.test_logic.TestCachedRespHeaderH2.test_set_exist_special_header Apr 26 05:41:17 192.168.122.209 [49028.113108] [tdb] Start Tempesta DB Apr 26 05:41:17 192.168.122.209 [49028.258139] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:41:19 192.168.122.209 [49029.683377] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49029.683377] Maybe that's fine, but it's worth checking the [49029.683377] config - if there is no relations between the [49029.683377] names, then host name confusion attack is possible. Apr 26 05:41:19 192.168.122.209 [49029.826107] [tempesta fw] Configuration processing is completed. Apr 26 05:41:19 192.168.122.209 [49029.881292] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:41:19 192.168.122.209 [49030.293576] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:41:19 192.168.122.209 [49030.321252] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:41:19 192.168.122.209 [49030.348647] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:41:19 192.168.122.209 [49030.406140] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:41:19 192.168.122.209 [49030.407890] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:41:20 192.168.122.209 [49030.454051] [tempesta fw] Tempesta FW is ready Apr 26 05:41:20 192.168.122.209 [49031.037500] [tdb] Close table 'client0.tdb' Apr 26 05:41:20 192.168.122.209 [49031.227325] [tdb] Close table 'sessions0.tdb' Apr 26 05:41:24 192.168.122.209 [49034.537086] [tdb] Close table 'cache0.tdb' Apr 26 05:41:24 192.168.122.209 [49034.785101] [tdb] Close table 'filter0.tdb' Apr 26 05:41:24 192.168.122.209 [49034.785527] [tempesta fw] modules are stopped Apr 26 05:41:24 192.168.122.209 [49035.031306] [tempesta fw] exiting... Apr 26 05:41:24 192.168.122.209 [49035.192028] [tdb] Shutdown Tempesta DB Apr 26 05:41:24 192.168.122.209 [49035.389199] End test: t_modify_http_headers.test_logic.TestCachedRespHeaderH2.test_set_exist_special_header Apr 26 05:41:24 192.168.122.209 [49035.403732] Start test: t_modify_http_headers.test_logic.TestCachedRespHeaderH2.test_set_header_name_greater_than_1024 Apr 26 05:41:26 192.168.122.209 [49036.489607] [tdb] Start Tempesta DB Apr 26 05:41:26 192.168.122.209 [49036.638329] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:41:27 192.168.122.209 [49038.010957] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49038.010957] Maybe that's fine, but it's worth checking the [49038.010957] config - if there is no relations between the [49038.010957] names, then host name confusion attack is possible. Apr 26 05:41:27 192.168.122.209 [49038.146219] [tempesta fw] Configuration processing is completed. Apr 26 05:41:27 192.168.122.209 [49038.197810] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:41:28 192.168.122.209 [49038.597785] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:41:28 192.168.122.209 [49038.660237] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:41:28 192.168.122.209 [49038.686476] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:41:28 192.168.122.209 [49038.726208] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:41:28 192.168.122.209 [49038.727938] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:41:28 192.168.122.209 [49038.766241] [tempesta fw] Tempesta FW is ready Apr 26 05:41:28 192.168.122.209 [49039.341317] [tdb] Close table 'client0.tdb' Apr 26 05:41:29 192.168.122.209 [49039.526527] [tdb] Close table 'sessions0.tdb' Apr 26 05:41:32 192.168.122.209 [49042.699562] [tdb] Close table 'cache0.tdb' Apr 26 05:41:32 192.168.122.209 [49042.936100] [tdb] Close table 'filter0.tdb' Apr 26 05:41:32 192.168.122.209 [49042.936537] [tempesta fw] modules are stopped Apr 26 05:41:32 192.168.122.209 [49043.163727] [tempesta fw] exiting... Apr 26 05:41:32 192.168.122.209 [49043.294643] [tdb] Shutdown Tempesta DB Apr 26 05:41:33 192.168.122.209 [49043.543725] End test: t_modify_http_headers.test_logic.TestCachedRespHeaderH2.test_set_header_name_greater_than_1024 Apr 26 05:41:33 192.168.122.209 [49043.561381] Start test: t_modify_http_headers.test_logic.TestCachedRespHeaderH2.test_set_large_header Apr 26 05:41:34 192.168.122.209 [49044.609136] [tdb] Start Tempesta DB Apr 26 05:41:34 192.168.122.209 [49044.736182] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:41:35 192.168.122.209 [49046.175339] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49046.175339] Maybe that's fine, but it's worth checking the [49046.175339] config - if there is no relations between the [49046.175339] names, then host name confusion attack is possible. Apr 26 05:41:35 192.168.122.209 [49046.306356] [tempesta fw] Configuration processing is completed. Apr 26 05:41:35 192.168.122.209 [49046.367116] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:41:36 192.168.122.209 [49046.801092] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:41:36 192.168.122.209 [49046.836780] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:41:36 192.168.122.209 [49046.865650] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:41:36 192.168.122.209 [49046.906268] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:41:36 192.168.122.209 [49046.907243] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:41:36 192.168.122.209 [49046.950282] [tempesta fw] Tempesta FW is ready Apr 26 05:41:37 192.168.122.209 [49047.515225] [tdb] Close table 'client0.tdb' Apr 26 05:41:37 192.168.122.209 [49047.713786] [tdb] Close table 'sessions0.tdb' Apr 26 05:41:40 192.168.122.209 [49050.903207] [tdb] Close table 'cache0.tdb' Apr 26 05:41:40 192.168.122.209 [49051.152646] [tdb] Close table 'filter0.tdb' Apr 26 05:41:40 192.168.122.209 [49051.153087] [tempesta fw] modules are stopped Apr 26 05:41:40 192.168.122.209 [49051.408270] [tempesta fw] exiting... Apr 26 05:41:41 192.168.122.209 [49051.536323] [tdb] Shutdown Tempesta DB Apr 26 05:41:41 192.168.122.209 [49051.736955] End test: t_modify_http_headers.test_logic.TestCachedRespHeaderH2.test_set_large_header Apr 26 05:41:41 192.168.122.209 [49051.750078] Start test: t_modify_http_headers.test_logic.TestCachedRespHeaderH2.test_set_long_header_name Apr 26 05:41:42 192.168.122.209 [49052.800528] [tdb] Start Tempesta DB Apr 26 05:41:42 192.168.122.209 [49052.948702] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:41:44 192.168.122.209 [49054.419317] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49054.419317] Maybe that's fine, but it's worth checking the [49054.419317] config - if there is no relations between the [49054.419317] names, then host name confusion attack is possible. Apr 26 05:41:44 192.168.122.209 [49054.598446] [tempesta fw] Configuration processing is completed. Apr 26 05:41:44 192.168.122.209 [49054.649256] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:41:44 192.168.122.209 [49055.050946] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:41:44 192.168.122.209 [49055.112874] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:41:44 192.168.122.209 [49055.139193] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:41:44 192.168.122.209 [49055.194407] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:41:44 192.168.122.209 [49055.196136] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:41:44 192.168.122.209 [49055.234382] [tempesta fw] Tempesta FW is ready Apr 26 05:41:45 192.168.122.209 [49055.816581] [tdb] Close table 'client0.tdb' Apr 26 05:41:45 192.168.122.209 [49056.006103] [tdb] Close table 'sessions0.tdb' Apr 26 05:41:48 192.168.122.209 [49059.197250] [tdb] Close table 'cache0.tdb' Apr 26 05:41:48 192.168.122.209 [49059.422060] [tdb] Close table 'filter0.tdb' Apr 26 05:41:48 192.168.122.209 [49059.422508] [tempesta fw] modules are stopped Apr 26 05:41:49 192.168.122.209 [49059.659125] [tempesta fw] exiting... Apr 26 05:41:49 192.168.122.209 [49059.787557] [tdb] Shutdown Tempesta DB Apr 26 05:41:49 192.168.122.209 [49059.992634] End test: t_modify_http_headers.test_logic.TestCachedRespHeaderH2.test_set_long_header_name Apr 26 05:41:49 192.168.122.209 [49060.016756] Start test: t_modify_http_headers.test_logic.TestCachedRespHeaderH2.test_set_non_exist_header Apr 26 05:41:50 192.168.122.209 [49061.063936] [tdb] Start Tempesta DB Apr 26 05:41:50 192.168.122.209 [49061.194013] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:41:52 192.168.122.209 [49062.615776] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49062.615776] Maybe that's fine, but it's worth checking the [49062.615776] config - if there is no relations between the [49062.615776] names, then host name confusion attack is possible. Apr 26 05:41:52 192.168.122.209 [49062.770794] [tempesta fw] Configuration processing is completed. Apr 26 05:41:52 192.168.122.209 [49062.826197] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:41:52 192.168.122.209 [49063.245717] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:41:52 192.168.122.209 [49063.274008] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:41:52 192.168.122.209 [49063.299554] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:41:52 192.168.122.209 [49063.342516] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:41:52 192.168.122.209 [49063.344075] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:41:52 192.168.122.209 [49063.390495] [tempesta fw] Tempesta FW is ready Apr 26 05:41:53 192.168.122.209 [49063.960969] [tdb] Close table 'client0.tdb' Apr 26 05:41:53 192.168.122.209 [49064.151141] [tdb] Close table 'sessions0.tdb' Apr 26 05:41:56 192.168.122.209 [49067.378337] [tdb] Close table 'cache0.tdb' Apr 26 05:41:57 192.168.122.209 [49067.605644] [tdb] Close table 'filter0.tdb' Apr 26 05:41:57 192.168.122.209 [49067.606071] [tempesta fw] modules are stopped Apr 26 05:41:57 192.168.122.209 [49067.835448] [tempesta fw] exiting... Apr 26 05:41:57 192.168.122.209 [49067.977447] [tdb] Shutdown Tempesta DB Apr 26 05:41:57 192.168.122.209 [49068.187942] End test: t_modify_http_headers.test_logic.TestCachedRespHeaderH2.test_set_non_exist_header Apr 26 05:41:57 192.168.122.209 [49068.209048] Start test: t_modify_http_headers.test_logic.TestLogicBase.test_add_non_exist_header Apr 26 05:41:57 192.168.122.209 [49068.224505] End test: t_modify_http_headers.test_logic.TestLogicBase.test_add_non_exist_header Apr 26 05:41:57 192.168.122.209 [49068.236234] Start test: t_modify_http_headers.test_logic.TestLogicBase.test_delete_headers Apr 26 05:41:57 192.168.122.209 [49068.244491] End test: t_modify_http_headers.test_logic.TestLogicBase.test_delete_headers Apr 26 05:41:57 192.168.122.209 [49068.251921] Start test: t_modify_http_headers.test_logic.TestLogicBase.test_delete_many_headers Apr 26 05:41:57 192.168.122.209 [49068.263112] End test: t_modify_http_headers.test_logic.TestLogicBase.test_delete_many_headers Apr 26 05:41:57 192.168.122.209 [49068.274450] Start test: t_modify_http_headers.test_logic.TestLogicBase.test_delete_many_special_headers Apr 26 05:41:57 192.168.122.209 [49068.284112] End test: t_modify_http_headers.test_logic.TestLogicBase.test_delete_many_special_headers Apr 26 05:41:57 192.168.122.209 [49068.291202] Start test: t_modify_http_headers.test_logic.TestLogicBase.test_delete_non_exist_header Apr 26 05:41:57 192.168.122.209 [49068.302551] End test: t_modify_http_headers.test_logic.TestLogicBase.test_delete_non_exist_header Apr 26 05:41:57 192.168.122.209 [49068.314082] Start test: t_modify_http_headers.test_logic.TestLogicBase.test_delete_special_headers Apr 26 05:41:57 192.168.122.209 [49068.324914] End test: t_modify_http_headers.test_logic.TestLogicBase.test_delete_special_headers Apr 26 05:41:57 192.168.122.209 [49068.341078] Start test: t_modify_http_headers.test_logic.TestLogicBase.test_long_header_name Apr 26 05:41:57 192.168.122.209 [49068.349931] End test: t_modify_http_headers.test_logic.TestLogicBase.test_long_header_name Apr 26 05:41:57 192.168.122.209 [49068.358744] Start test: t_modify_http_headers.test_logic.TestLogicBase.test_set_exist_header Apr 26 05:41:57 192.168.122.209 [49068.366963] End test: t_modify_http_headers.test_logic.TestLogicBase.test_set_exist_header Apr 26 05:41:57 192.168.122.209 [49068.380599] Start test: t_modify_http_headers.test_logic.TestLogicBase.test_set_exist_special_header Apr 26 05:41:57 192.168.122.209 [49068.387738] End test: t_modify_http_headers.test_logic.TestLogicBase.test_set_exist_special_header Apr 26 05:41:57 192.168.122.209 [49068.398993] Start test: t_modify_http_headers.test_logic.TestLogicBase.test_set_header_name_greater_than_1024 Apr 26 05:41:57 192.168.122.209 [49068.419481] End test: t_modify_http_headers.test_logic.TestLogicBase.test_set_header_name_greater_than_1024 Apr 26 05:41:58 192.168.122.209 [49068.425995] Start test: t_modify_http_headers.test_logic.TestLogicBase.test_set_large_header Apr 26 05:41:58 192.168.122.209 [49068.436856] End test: t_modify_http_headers.test_logic.TestLogicBase.test_set_large_header Apr 26 05:41:58 192.168.122.209 [49068.445452] Start test: t_modify_http_headers.test_logic.TestLogicBase.test_set_long_header_name Apr 26 05:41:58 192.168.122.209 [49068.453828] End test: t_modify_http_headers.test_logic.TestLogicBase.test_set_long_header_name Apr 26 05:41:58 192.168.122.209 [49068.461630] Start test: t_modify_http_headers.test_logic.TestLogicBase.test_set_non_exist_header Apr 26 05:41:58 192.168.122.209 [49068.469410] End test: t_modify_http_headers.test_logic.TestLogicBase.test_set_non_exist_header Apr 26 05:41:58 192.168.122.209 [49068.479386] Start test: t_modify_http_headers.test_logic.TestManyCachedResponseHeaders.test_many_headers Apr 26 05:41:59 192.168.122.209 [49069.513821] [tdb] Start Tempesta DB Apr 26 05:41:59 192.168.122.209 [49069.662786] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:42:02 192.168.122.209 [49072.528646] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49072.528646] Maybe that's fine, but it's worth checking the [49072.528646] config - if there is no relations between the [49072.528646] names, then host name confusion attack is possible. Apr 26 05:42:03 192.168.122.209 [49073.762672] [tempesta fw] Configuration processing is completed. Apr 26 05:42:03 192.168.122.209 [49073.825336] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:42:03 192.168.122.209 [49074.309303] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:42:03 192.168.122.209 [49074.371170] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:42:03 192.168.122.209 [49074.400202] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:42:04 192.168.122.209 [49074.442673] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:42:04 192.168.122.209 [49074.444424] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:42:04 192.168.122.209 [49074.494555] [tempesta fw] Tempesta FW is ready Apr 26 05:42:04 192.168.122.209 [49075.092576] [tdb] Close table 'client0.tdb' Apr 26 05:42:04 192.168.122.209 [49075.279668] [tdb] Close table 'sessions0.tdb' Apr 26 05:42:08 192.168.122.209 [49078.534562] [tdb] Close table 'cache0.tdb' Apr 26 05:42:08 192.168.122.209 [49078.781473] [tdb] Close table 'filter0.tdb' Apr 26 05:42:08 192.168.122.209 [49078.781911] [tempesta fw] modules are stopped Apr 26 05:42:08 192.168.122.209 [49079.007862] [tempesta fw] exiting... Apr 26 05:42:08 192.168.122.209 [49079.129434] [tdb] Shutdown Tempesta DB Apr 26 05:42:08 192.168.122.209 [49079.380878] End test: t_modify_http_headers.test_logic.TestManyCachedResponseHeaders.test_many_headers Apr 26 05:42:08 192.168.122.209 [49079.399812] Start test: t_modify_http_headers.test_logic.TestManyCachedResponseHeadersH2.test_many_headers Apr 26 05:42:10 192.168.122.209 [49080.467724] [tdb] Start Tempesta DB Apr 26 05:42:10 192.168.122.209 [49080.599641] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:42:13 192.168.122.209 [49083.567926] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49083.567926] Maybe that's fine, but it's worth checking the [49083.567926] config - if there is no relations between the [49083.567926] names, then host name confusion attack is possible. Apr 26 05:42:14 192.168.122.209 [49084.770832] [tempesta fw] Configuration processing is completed. Apr 26 05:42:14 192.168.122.209 [49084.825455] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:42:14 192.168.122.209 [49085.273774] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:42:14 192.168.122.209 [49085.334571] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:42:14 192.168.122.209 [49085.367797] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:42:14 192.168.122.209 [49085.422812] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:42:15 192.168.122.209 [49085.423948] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:42:15 192.168.122.209 [49085.462686] [tempesta fw] Tempesta FW is ready Apr 26 05:42:15 192.168.122.209 [49086.126127] [tdb] Close table 'client0.tdb' Apr 26 05:42:15 192.168.122.209 [49086.309623] [tdb] Close table 'sessions0.tdb' Apr 26 05:42:19 192.168.122.209 [49089.538919] [tdb] Close table 'cache0.tdb' Apr 26 05:42:19 192.168.122.209 [49089.814412] [tdb] Close table 'filter0.tdb' Apr 26 05:42:19 192.168.122.209 [49089.814860] [tempesta fw] modules are stopped Apr 26 05:42:19 192.168.122.209 [49090.061255] [tempesta fw] exiting... Apr 26 05:42:19 192.168.122.209 [49090.197406] [tdb] Shutdown Tempesta DB Apr 26 05:42:20 192.168.122.209 [49090.446492] End test: t_modify_http_headers.test_logic.TestManyCachedResponseHeadersH2.test_many_headers Apr 26 05:42:20 192.168.122.209 [49090.457015] Start test: t_modify_http_headers.test_logic.TestManyRequestHeaders.test_many_headers Apr 26 05:42:21 192.168.122.209 [49091.549548] [tdb] Start Tempesta DB Apr 26 05:42:21 192.168.122.209 [49091.707021] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:42:24 192.168.122.209 [49094.508285] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49094.508285] Maybe that's fine, but it's worth checking the [49094.508285] config - if there is no relations between the [49094.508285] names, then host name confusion attack is possible. Apr 26 05:42:25 192.168.122.209 [49095.694965] [tempesta fw] Configuration processing is completed. Apr 26 05:42:25 192.168.122.209 [49095.749792] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:42:25 192.168.122.209 [49096.162483] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:42:25 192.168.122.209 [49096.223394] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:42:25 192.168.122.209 [49096.251504] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:42:25 192.168.122.209 [49096.302977] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:42:25 192.168.122.209 [49096.304745] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:42:25 192.168.122.209 [49096.346895] [tempesta fw] Tempesta FW is ready Apr 26 05:42:26 192.168.122.209 [49096.930512] [tdb] Close table 'client0.tdb' Apr 26 05:42:26 192.168.122.209 [49097.112025] [tdb] Close table 'sessions0.tdb' Apr 26 05:42:29 192.168.122.209 [49100.353058] [tdb] Close table 'cache0.tdb' Apr 26 05:42:30 192.168.122.209 [49100.589963] [tdb] Close table 'filter0.tdb' Apr 26 05:42:30 192.168.122.209 [49100.590419] [tempesta fw] modules are stopped Apr 26 05:42:30 192.168.122.209 [49100.810587] [tempesta fw] exiting... Apr 26 05:42:30 192.168.122.209 [49100.952899] [tdb] Shutdown Tempesta DB Apr 26 05:42:30 192.168.122.209 [49101.157871] End test: t_modify_http_headers.test_logic.TestManyRequestHeaders.test_many_headers Apr 26 05:42:30 192.168.122.209 [49101.175978] Start test: t_modify_http_headers.test_logic.TestManyRequestHeadersH2.test_many_headers Apr 26 05:42:31 192.168.122.209 [49102.244996] [tdb] Start Tempesta DB Apr 26 05:42:31 192.168.122.209 [49102.402035] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:42:34 192.168.122.209 [49105.304299] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49105.304299] Maybe that's fine, but it's worth checking the [49105.304299] config - if there is no relations between the [49105.304299] names, then host name confusion attack is possible. Apr 26 05:42:36 192.168.122.209 [49106.455044] [tempesta fw] Configuration processing is completed. Apr 26 05:42:36 192.168.122.209 [49106.527823] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:42:36 192.168.122.209 [49107.056241] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:42:36 192.168.122.209 [49107.119105] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:42:36 192.168.122.209 [49107.151594] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:42:36 192.168.122.209 [49107.195011] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:42:36 192.168.122.209 [49107.196333] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:42:36 192.168.122.209 [49107.234936] [tempesta fw] Tempesta FW is ready Apr 26 05:42:37 192.168.122.209 [49107.820030] [tdb] Close table 'client0.tdb' Apr 26 05:42:37 192.168.122.209 [49108.016106] [tdb] Close table 'sessions0.tdb' Apr 26 05:42:40 192.168.122.209 [49111.267794] [tdb] Close table 'cache0.tdb' Apr 26 05:42:41 192.168.122.209 [49111.516136] [tdb] Close table 'filter0.tdb' Apr 26 05:42:41 192.168.122.209 [49111.516664] [tempesta fw] modules are stopped Apr 26 05:42:41 192.168.122.209 [49111.757142] [tempesta fw] exiting... Apr 26 05:42:41 192.168.122.209 [49111.895706] [tdb] Shutdown Tempesta DB Apr 26 05:42:41 192.168.122.209 [49112.129952] End test: t_modify_http_headers.test_logic.TestManyRequestHeadersH2.test_many_headers Apr 26 05:42:41 192.168.122.209 [49112.142097] Start test: t_modify_http_headers.test_logic.TestManyResponseHeaders.test_many_headers Apr 26 05:42:42 192.168.122.209 [49113.242975] [tdb] Start Tempesta DB Apr 26 05:42:42 192.168.122.209 [49113.399849] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:42:45 192.168.122.209 [49116.320525] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49116.320525] Maybe that's fine, but it's worth checking the [49116.320525] config - if there is no relations between the [49116.320525] names, then host name confusion attack is possible. Apr 26 05:42:47 192.168.122.209 [49117.499255] [tempesta fw] Configuration processing is completed. Apr 26 05:42:47 192.168.122.209 [49117.554818] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:42:47 192.168.122.209 [49117.979894] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:42:47 192.168.122.209 [49118.037567] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:42:47 192.168.122.209 [49118.065104] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:42:47 192.168.122.209 [49118.111208] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:42:47 192.168.122.209 [49118.112680] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:42:47 192.168.122.209 [49118.151177] [tempesta fw] Tempesta FW is ready Apr 26 05:42:48 192.168.122.209 [49118.749021] [tdb] Close table 'client0.tdb' Apr 26 05:42:48 192.168.122.209 [49118.948645] [tdb] Close table 'sessions0.tdb' Apr 26 05:42:51 192.168.122.209 [49122.092161] [tdb] Close table 'cache0.tdb' Apr 26 05:42:51 192.168.122.209 [49122.314482] [tdb] Close table 'filter0.tdb' Apr 26 05:42:51 192.168.122.209 [49122.314941] [tempesta fw] modules are stopped Apr 26 05:42:52 192.168.122.209 [49122.519230] [tempesta fw] exiting... Apr 26 05:42:52 192.168.122.209 [49122.669181] [tdb] Shutdown Tempesta DB Apr 26 05:42:52 192.168.122.209 [49122.863714] End test: t_modify_http_headers.test_logic.TestManyResponseHeaders.test_many_headers Apr 26 05:42:52 192.168.122.209 [49122.882036] Start test: t_modify_http_headers.test_logic.TestManyResponseHeadersH2.test_many_headers Apr 26 05:42:53 192.168.122.209 [49123.937689] [tdb] Start Tempesta DB Apr 26 05:42:53 192.168.122.209 [49124.076192] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:42:56 192.168.122.209 [49126.868557] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49126.868557] Maybe that's fine, but it's worth checking the [49126.868557] config - if there is no relations between the [49126.868557] names, then host name confusion attack is possible. Apr 26 05:42:57 192.168.122.209 [49128.031381] [tempesta fw] Configuration processing is completed. Apr 26 05:42:57 192.168.122.209 [49128.086268] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:42:58 192.168.122.209 [49128.488079] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:42:58 192.168.122.209 [49128.544917] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:42:58 192.168.122.209 [49128.571219] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:42:58 192.168.122.209 [49128.631343] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:42:58 192.168.122.209 [49128.633081] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:42:58 192.168.122.209 [49128.671300] [tempesta fw] Tempesta FW is ready Apr 26 05:42:58 192.168.122.209 [49129.276019] [tdb] Close table 'client0.tdb' Apr 26 05:42:59 192.168.122.209 [49129.447014] [tdb] Close table 'sessions0.tdb' Apr 26 05:43:02 192.168.122.209 [49132.632925] [tdb] Close table 'cache0.tdb' Apr 26 05:43:02 192.168.122.209 [49132.865724] [tdb] Close table 'filter0.tdb' Apr 26 05:43:02 192.168.122.209 [49132.866201] [tempesta fw] modules are stopped Apr 26 05:43:02 192.168.122.209 [49133.100977] [tempesta fw] exiting... Apr 26 05:43:02 192.168.122.209 [49133.214291] [tdb] Shutdown Tempesta DB Apr 26 05:43:02 192.168.122.209 [49133.399715] End test: t_modify_http_headers.test_logic.TestManyResponseHeadersH2.test_many_headers Apr 26 05:43:02 192.168.122.209 [49133.409830] Start test: t_modify_http_headers.test_logic.TestReqHdrSetHost.test_req_hdr_set_host Apr 26 05:43:04 192.168.122.209 [49134.501519] [tdb] Start Tempesta DB Apr 26 05:43:04 192.168.122.209 [49134.640921] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:43:05 192.168.122.209 [49136.040683] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49136.040683] Maybe that's fine, but it's worth checking the [49136.040683] config - if there is no relations between the [49136.040683] names, then host name confusion attack is possible. Apr 26 05:43:05 192.168.122.209 [49136.143504] [tempesta fw] Configuration processing is completed. Apr 26 05:43:05 192.168.122.209 [49136.198046] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:43:06 192.168.122.209 [49136.657815] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:43:06 192.168.122.209 [49136.686178] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:43:06 192.168.122.209 [49136.714668] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:43:06 192.168.122.209 [49136.767498] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:43:06 192.168.122.209 [49136.769283] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:43:06 192.168.122.209 [49136.827403] [tempesta fw] Tempesta FW is ready Apr 26 05:43:06 192.168.122.209 [49137.380741] [tdb] Close table 'client0.tdb' Apr 26 05:43:07 192.168.122.209 [49137.565222] [tdb] Close table 'sessions0.tdb' Apr 26 05:43:10 192.168.122.209 [49140.737622] [tdb] Close table 'cache0.tdb' Apr 26 05:43:10 192.168.122.209 [49140.956687] [tdb] Close table 'filter0.tdb' Apr 26 05:43:10 192.168.122.209 [49140.957122] [tempesta fw] modules are stopped Apr 26 05:43:10 192.168.122.209 [49141.144551] [tempesta fw] exiting... Apr 26 05:43:10 192.168.122.209 [49141.312808] [tdb] Shutdown Tempesta DB Apr 26 05:43:11 192.168.122.209 [49141.493325] End test: t_modify_http_headers.test_logic.TestReqHdrSetHost.test_req_hdr_set_host Apr 26 05:43:11 192.168.122.209 [49141.507538] Start test: t_modify_http_headers.test_logic.TestReqHdrSetHostH2.test_req_hdr_set_host Apr 26 05:43:12 192.168.122.209 [49142.613073] [tdb] Start Tempesta DB Apr 26 05:43:12 192.168.122.209 [49142.754032] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:43:13 192.168.122.209 [49144.116793] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49144.116793] Maybe that's fine, but it's worth checking the [49144.116793] config - if there is no relations between the [49144.116793] names, then host name confusion attack is possible. Apr 26 05:43:13 192.168.122.209 [49144.215562] [tempesta fw] Configuration processing is completed. Apr 26 05:43:13 192.168.122.209 [49144.266348] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:43:14 192.168.122.209 [49144.670168] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:43:14 192.168.122.209 [49144.732992] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:43:14 192.168.122.209 [49144.759787] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:43:14 192.168.122.209 [49144.799550] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:43:14 192.168.122.209 [49144.801290] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:43:14 192.168.122.209 [49144.839506] [tempesta fw] Tempesta FW is ready Apr 26 05:43:14 192.168.122.209 [49145.396523] [tdb] Close table 'client0.tdb' Apr 26 05:43:15 192.168.122.209 [49145.588626] [tdb] Close table 'sessions0.tdb' Apr 26 05:43:18 192.168.122.209 [49148.805884] [tdb] Close table 'cache0.tdb' Apr 26 05:43:18 192.168.122.209 [49149.053913] [tdb] Close table 'filter0.tdb' Apr 26 05:43:18 192.168.122.209 [49149.054338] [tempesta fw] modules are stopped Apr 26 05:43:18 192.168.122.209 [49149.263190] [tempesta fw] exiting... Apr 26 05:43:18 192.168.122.209 [49149.394671] [tdb] Shutdown Tempesta DB Apr 26 05:43:19 192.168.122.209 [49149.637427] End test: t_modify_http_headers.test_logic.TestReqHdrSetHostH2.test_req_hdr_set_host Apr 26 05:43:19 192.168.122.209 [49149.652963] Start test: t_modify_http_headers.test_logic.TestReqHeader.test_add_non_exist_header Apr 26 05:43:20 192.168.122.209 [49150.690312] [tdb] Start Tempesta DB Apr 26 05:43:20 192.168.122.209 [49150.828713] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:43:21 192.168.122.209 [49152.240918] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49152.240918] Maybe that's fine, but it's worth checking the [49152.240918] config - if there is no relations between the [49152.240918] names, then host name confusion attack is possible. Apr 26 05:43:21 192.168.122.209 [49152.339714] [tempesta fw] Configuration processing is completed. Apr 26 05:43:21 192.168.122.209 [49152.390293] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:43:22 192.168.122.209 [49152.800474] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:43:22 192.168.122.209 [49152.857074] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:43:22 192.168.122.209 [49152.883825] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:43:22 192.168.122.209 [49152.943681] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:43:22 192.168.122.209 [49152.945442] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:43:22 192.168.122.209 [49152.983627] [tempesta fw] Tempesta FW is ready Apr 26 05:43:23 192.168.122.209 [49153.545669] [tdb] Close table 'client0.tdb' Apr 26 05:43:23 192.168.122.209 [49153.729869] [tdb] Close table 'sessions0.tdb' Apr 26 05:43:26 192.168.122.209 [49156.923041] [tdb] Close table 'cache0.tdb' Apr 26 05:43:26 192.168.122.209 [49157.171154] [tdb] Close table 'filter0.tdb' Apr 26 05:43:26 192.168.122.209 [49157.171602] [tempesta fw] modules are stopped Apr 26 05:43:26 192.168.122.209 [49157.352425] [tempesta fw] exiting... Apr 26 05:43:27 192.168.122.209 [49157.457755] [tdb] Shutdown Tempesta DB Apr 26 05:43:27 192.168.122.209 [49157.666796] End test: t_modify_http_headers.test_logic.TestReqHeader.test_add_non_exist_header Apr 26 05:43:27 192.168.122.209 [49157.677779] Start test: t_modify_http_headers.test_logic.TestReqHeader.test_delete_headers Apr 26 05:43:28 192.168.122.209 [49158.750817] [tdb] Start Tempesta DB Apr 26 05:43:28 192.168.122.209 [49158.884669] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:43:29 192.168.122.209 [49160.296979] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49160.296979] Maybe that's fine, but it's worth checking the [49160.296979] config - if there is no relations between the [49160.296979] names, then host name confusion attack is possible. Apr 26 05:43:29 192.168.122.209 [49160.411786] [tempesta fw] Configuration processing is completed. Apr 26 05:43:30 192.168.122.209 [49160.467683] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:43:30 192.168.122.209 [49160.878991] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:43:30 192.168.122.209 [49160.904286] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:43:30 192.168.122.209 [49160.929696] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:43:30 192.168.122.209 [49160.975686] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:43:30 192.168.122.209 [49160.976986] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:43:30 192.168.122.209 [49161.023690] [tempesta fw] Tempesta FW is ready Apr 26 05:43:31 192.168.122.209 [49161.573331] [tdb] Close table 'client0.tdb' Apr 26 05:43:31 192.168.122.209 [49161.741541] [tdb] Close table 'sessions0.tdb' Apr 26 05:43:34 192.168.122.209 [49164.903784] [tdb] Close table 'cache0.tdb' Apr 26 05:43:34 192.168.122.209 [49165.144366] [tdb] Close table 'filter0.tdb' Apr 26 05:43:34 192.168.122.209 [49165.144798] [tempesta fw] modules are stopped Apr 26 05:43:34 192.168.122.209 [49165.317578] [tempesta fw] exiting... Apr 26 05:43:35 192.168.122.209 [49165.429296] [tdb] Shutdown Tempesta DB Apr 26 05:43:35 192.168.122.209 [49165.647978] End test: t_modify_http_headers.test_logic.TestReqHeader.test_delete_headers Apr 26 05:43:35 192.168.122.209 [49165.658926] Start test: t_modify_http_headers.test_logic.TestReqHeader.test_delete_many_headers Apr 26 05:43:36 192.168.122.209 [49166.751649] [tdb] Start Tempesta DB Apr 26 05:43:36 192.168.122.209 [49166.880182] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:43:37 192.168.122.209 [49168.273107] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49168.273107] Maybe that's fine, but it's worth checking the [49168.273107] config - if there is no relations between the [49168.273107] names, then host name confusion attack is possible. Apr 26 05:43:37 192.168.122.209 [49168.387776] [tempesta fw] Configuration processing is completed. Apr 26 05:43:38 192.168.122.209 [49168.437043] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:43:38 192.168.122.209 [49168.839869] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:43:38 192.168.122.209 [49168.896227] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:43:38 192.168.122.209 [49168.921797] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:43:38 192.168.122.209 [49168.963791] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:43:38 192.168.122.209 [49168.965155] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:43:38 192.168.122.209 [49169.007804] [tempesta fw] Tempesta FW is ready Apr 26 05:43:39 192.168.122.209 [49169.577203] [tdb] Close table 'client0.tdb' Apr 26 05:43:39 192.168.122.209 [49169.763639] [tdb] Close table 'sessions0.tdb' Apr 26 05:43:42 192.168.122.209 [49172.947528] [tdb] Close table 'cache0.tdb' Apr 26 05:43:42 192.168.122.209 [49173.207170] [tdb] Close table 'filter0.tdb' Apr 26 05:43:42 192.168.122.209 [49173.207591] [tempesta fw] modules are stopped Apr 26 05:43:43 192.168.122.209 [49173.431067] [tempesta fw] exiting... Apr 26 05:43:43 192.168.122.209 [49173.533542] [tdb] Shutdown Tempesta DB Apr 26 05:43:43 192.168.122.209 [49173.751570] End test: t_modify_http_headers.test_logic.TestReqHeader.test_delete_many_headers Apr 26 05:43:43 192.168.122.209 [49173.765936] Start test: t_modify_http_headers.test_logic.TestReqHeader.test_delete_many_special_headers Apr 26 05:43:44 192.168.122.209 [49174.852358] [tdb] Start Tempesta DB Apr 26 05:43:44 192.168.122.209 [49174.989039] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:43:45 192.168.122.209 [49176.317216] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49176.317216] Maybe that's fine, but it's worth checking the [49176.317216] config - if there is no relations between the [49176.317216] names, then host name confusion attack is possible. Apr 26 05:43:46 192.168.122.209 [49176.431976] [tempesta fw] Configuration processing is completed. Apr 26 05:43:46 192.168.122.209 [49176.486645] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:43:46 192.168.122.209 [49176.941804] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:43:46 192.168.122.209 [49176.969848] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:43:46 192.168.122.209 [49176.997719] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:43:46 192.168.122.209 [49177.035975] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:43:46 192.168.122.209 [49177.037736] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:43:46 192.168.122.209 [49177.083895] [tempesta fw] Tempesta FW is ready Apr 26 05:43:47 192.168.122.209 [49177.645597] [tdb] Close table 'client0.tdb' Apr 26 05:43:47 192.168.122.209 [49177.843497] [tdb] Close table 'sessions0.tdb' Apr 26 05:43:50 192.168.122.209 [49181.109762] [tdb] Close table 'cache0.tdb' Apr 26 05:43:50 192.168.122.209 [49181.355560] [tdb] Close table 'filter0.tdb' Apr 26 05:43:50 192.168.122.209 [49181.356012] [tempesta fw] modules are stopped Apr 26 05:43:51 192.168.122.209 [49181.581455] [tempesta fw] exiting... Apr 26 05:43:51 192.168.122.209 [49181.708225] [tdb] Shutdown Tempesta DB Apr 26 05:43:51 192.168.122.209 [49181.915284] End test: t_modify_http_headers.test_logic.TestReqHeader.test_delete_many_special_headers Apr 26 05:43:51 192.168.122.209 [49181.932673] Start test: t_modify_http_headers.test_logic.TestReqHeader.test_delete_non_exist_header Apr 26 05:43:52 192.168.122.209 [49183.020134] [tdb] Start Tempesta DB Apr 26 05:43:52 192.168.122.209 [49183.163131] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:43:54 192.168.122.209 [49184.557341] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49184.557341] Maybe that's fine, but it's worth checking the [49184.557341] config - if there is no relations between the [49184.557341] names, then host name confusion attack is possible. Apr 26 05:43:54 192.168.122.209 [49184.664099] [tempesta fw] Configuration processing is completed. Apr 26 05:43:54 192.168.122.209 [49184.715333] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:43:54 192.168.122.209 [49185.119299] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:43:54 192.168.122.209 [49185.181490] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:43:54 192.168.122.209 [49185.207197] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:43:54 192.168.122.209 [49185.264061] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:43:54 192.168.122.209 [49185.265800] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:43:54 192.168.122.209 [49185.308010] [tempesta fw] Tempesta FW is ready Apr 26 05:43:55 192.168.122.209 [49185.846237] [tdb] Close table 'client0.tdb' Apr 26 05:43:55 192.168.122.209 [49186.031140] [tdb] Close table 'sessions0.tdb' Apr 26 05:43:58 192.168.122.209 [49189.227161] [tdb] Close table 'cache0.tdb' Apr 26 05:43:59 192.168.122.209 [49189.447179] [tdb] Close table 'filter0.tdb' Apr 26 05:43:59 192.168.122.209 [49189.447626] [tempesta fw] modules are stopped Apr 26 05:43:59 192.168.122.209 [49189.655992] [tempesta fw] exiting... Apr 26 05:43:59 192.168.122.209 [49189.773840] [tdb] Shutdown Tempesta DB Apr 26 05:43:59 192.168.122.209 [49189.986635] End test: t_modify_http_headers.test_logic.TestReqHeader.test_delete_non_exist_header Apr 26 05:43:59 192.168.122.209 [49190.011456] Start test: t_modify_http_headers.test_logic.TestReqHeader.test_delete_special_headers Apr 26 05:44:00 192.168.122.209 [49191.071437] [tdb] Start Tempesta DB Apr 26 05:44:00 192.168.122.209 [49191.203646] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:44:02 192.168.122.209 [49192.533391] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49192.533391] Maybe that's fine, but it's worth checking the [49192.533391] config - if there is no relations between the [49192.533391] names, then host name confusion attack is possible. Apr 26 05:44:02 192.168.122.209 [49192.640179] [tempesta fw] Configuration processing is completed. Apr 26 05:44:02 192.168.122.209 [49192.702830] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:44:02 192.168.122.209 [49193.121621] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:44:02 192.168.122.209 [49193.147094] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:44:02 192.168.122.209 [49193.172998] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:44:02 192.168.122.209 [49193.228129] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:44:02 192.168.122.209 [49193.229605] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:44:02 192.168.122.209 [49193.280097] [tempesta fw] Tempesta FW is ready Apr 26 05:44:03 192.168.122.209 [49193.843155] [tdb] Close table 'client0.tdb' Apr 26 05:44:03 192.168.122.209 [49194.024363] [tdb] Close table 'sessions0.tdb' Apr 26 05:44:06 192.168.122.209 [49197.197117] [tdb] Close table 'cache0.tdb' Apr 26 05:44:07 192.168.122.209 [49197.462464] [tdb] Close table 'filter0.tdb' Apr 26 05:44:07 192.168.122.209 [49197.462914] [tempesta fw] modules are stopped Apr 26 05:44:07 192.168.122.209 [49197.669692] [tempesta fw] exiting... Apr 26 05:44:07 192.168.122.209 [49197.807529] [tdb] Shutdown Tempesta DB Apr 26 05:44:07 192.168.122.209 [49198.018464] End test: t_modify_http_headers.test_logic.TestReqHeader.test_delete_special_headers Apr 26 05:44:07 192.168.122.209 [49198.027906] Start test: t_modify_http_headers.test_logic.TestReqHeader.test_long_header_name Apr 26 05:44:08 192.168.122.209 [49199.074130] [tdb] Start Tempesta DB Apr 26 05:44:08 192.168.122.209 [49199.202958] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:44:10 192.168.122.209 [49200.557063] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49200.557063] Maybe that's fine, but it's worth checking the [49200.557063] config - if there is no relations between the [49200.557063] names, then host name confusion attack is possible. Apr 26 05:44:10 192.168.122.209 [49200.672270] [tempesta fw] Configuration processing is completed. Apr 26 05:44:10 192.168.122.209 [49200.727458] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:44:10 192.168.122.209 [49201.133386] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:44:10 192.168.122.209 [49201.190154] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:44:10 192.168.122.209 [49201.215898] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:44:10 192.168.122.209 [49201.264166] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:44:10 192.168.122.209 [49201.264936] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:44:10 192.168.122.209 [49201.304199] [tempesta fw] Tempesta FW is ready Apr 26 05:44:11 192.168.122.209 [49201.896203] [tdb] Close table 'client0.tdb' Apr 26 05:44:11 192.168.122.209 [49202.114451] [tdb] Close table 'sessions0.tdb' Apr 26 05:44:14 192.168.122.209 [49205.241134] [tdb] Close table 'cache0.tdb' Apr 26 05:44:15 192.168.122.209 [49205.484689] [tdb] Close table 'filter0.tdb' Apr 26 05:44:15 192.168.122.209 [49205.485130] [tempesta fw] modules are stopped Apr 26 05:44:15 192.168.122.209 [49205.725319] [tempesta fw] exiting... Apr 26 05:44:15 192.168.122.209 [49205.873590] [tdb] Shutdown Tempesta DB Apr 26 05:44:15 192.168.122.209 [49206.089470] End test: t_modify_http_headers.test_logic.TestReqHeader.test_long_header_name Apr 26 05:44:15 192.168.122.209 [49206.097627] Start test: t_modify_http_headers.test_logic.TestReqHeader.test_set_exist_header Apr 26 05:44:16 192.168.122.209 [49207.108140] [tdb] Start Tempesta DB Apr 26 05:44:16 192.168.122.209 [49207.249092] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:44:18 192.168.122.209 [49208.653082] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49208.653082] Maybe that's fine, but it's worth checking the [49208.653082] config - if there is no relations between the [49208.653082] names, then host name confusion attack is possible. Apr 26 05:44:18 192.168.122.209 [49208.748392] [tempesta fw] Configuration processing is completed. Apr 26 05:44:18 192.168.122.209 [49208.802561] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:44:18 192.168.122.209 [49209.218730] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:44:18 192.168.122.209 [49209.257511] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:44:18 192.168.122.209 [49209.282880] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:44:18 192.168.122.209 [49209.328315] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:44:18 192.168.122.209 [49209.329786] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:44:18 192.168.122.209 [49209.368247] [tempesta fw] Tempesta FW is ready Apr 26 05:44:19 192.168.122.209 [49209.924718] [tdb] Close table 'client0.tdb' Apr 26 05:44:19 192.168.122.209 [49210.110383] [tdb] Close table 'sessions0.tdb' Apr 26 05:44:22 192.168.122.209 [49213.299625] [tdb] Close table 'cache0.tdb' Apr 26 05:44:23 192.168.122.209 [49213.537665] [tdb] Close table 'filter0.tdb' Apr 26 05:44:23 192.168.122.209 [49213.538100] [tempesta fw] modules are stopped Apr 26 05:44:23 192.168.122.209 [49213.716719] [tempesta fw] exiting... Apr 26 05:44:23 192.168.122.209 [49213.850312] [tdb] Shutdown Tempesta DB Apr 26 05:44:23 192.168.122.209 [49214.062191] End test: t_modify_http_headers.test_logic.TestReqHeader.test_set_exist_header Apr 26 05:44:23 192.168.122.209 [49214.080677] Start test: t_modify_http_headers.test_logic.TestReqHeader.test_set_exist_special_header Apr 26 05:44:24 192.168.122.209 [49215.159511] [tdb] Start Tempesta DB Apr 26 05:44:24 192.168.122.209 [49215.289196] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:44:26 192.168.122.209 [49216.621719] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49216.621719] Maybe that's fine, but it's worth checking the [49216.621719] config - if there is no relations between the [49216.621719] names, then host name confusion attack is possible. Apr 26 05:44:26 192.168.122.209 [49216.732373] [tempesta fw] Configuration processing is completed. Apr 26 05:44:26 192.168.122.209 [49216.788838] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:44:26 192.168.122.209 [49217.194918] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:44:26 192.168.122.209 [49217.251468] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:44:26 192.168.122.209 [49217.278563] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:44:26 192.168.122.209 [49217.324437] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:44:26 192.168.122.209 [49217.325503] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:44:26 192.168.122.209 [49217.372403] [tempesta fw] Tempesta FW is ready Apr 26 05:44:27 192.168.122.209 [49217.955968] [tdb] Close table 'client0.tdb' Apr 26 05:44:27 192.168.122.209 [49218.138830] [tdb] Close table 'sessions0.tdb' Apr 26 05:44:30 192.168.122.209 [49221.322158] [tdb] Close table 'cache0.tdb' Apr 26 05:44:31 192.168.122.209 [49221.561926] [tdb] Close table 'filter0.tdb' Apr 26 05:44:31 192.168.122.209 [49221.562358] [tempesta fw] modules are stopped Apr 26 05:44:31 192.168.122.209 [49221.740187] [tempesta fw] exiting... Apr 26 05:44:31 192.168.122.209 [49221.876287] [tdb] Shutdown Tempesta DB Apr 26 05:44:31 192.168.122.209 [49222.110446] End test: t_modify_http_headers.test_logic.TestReqHeader.test_set_exist_special_header Apr 26 05:44:31 192.168.122.209 [49222.121951] Start test: t_modify_http_headers.test_logic.TestReqHeader.test_set_header_name_greater_than_1024 Apr 26 05:44:32 192.168.122.209 [49223.204659] [tdb] Start Tempesta DB Apr 26 05:44:32 192.168.122.209 [49223.341058] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:44:34 192.168.122.209 [49224.697857] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49224.697857] Maybe that's fine, but it's worth checking the [49224.697857] config - if there is no relations between the [49224.697857] names, then host name confusion attack is possible. Apr 26 05:44:34 192.168.122.209 [49224.804584] [tempesta fw] Configuration processing is completed. Apr 26 05:44:34 192.168.122.209 [49224.855579] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:44:34 192.168.122.209 [49225.264516] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:44:34 192.168.122.209 [49225.289862] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:44:34 192.168.122.209 [49225.315054] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:44:34 192.168.122.209 [49225.360543] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:44:34 192.168.122.209 [49225.361935] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:44:34 192.168.122.209 [49225.396520] [tempesta fw] Tempesta FW is ready Apr 26 05:44:35 192.168.122.209 [49225.953490] [tdb] Close table 'client0.tdb' Apr 26 05:44:35 192.168.122.209 [49226.145359] [tdb] Close table 'sessions0.tdb' Apr 26 05:44:38 192.168.122.209 [49229.346687] [tdb] Close table 'cache0.tdb' Apr 26 05:44:39 192.168.122.209 [49229.577051] [tdb] Close table 'filter0.tdb' Apr 26 05:44:39 192.168.122.209 [49229.577494] [tempesta fw] modules are stopped Apr 26 05:44:39 192.168.122.209 [49229.775875] [tempesta fw] exiting... Apr 26 05:44:39 192.168.122.209 [49229.915522] [tdb] Shutdown Tempesta DB Apr 26 05:44:39 192.168.122.209 [49230.131040] End test: t_modify_http_headers.test_logic.TestReqHeader.test_set_header_name_greater_than_1024 Apr 26 05:44:39 192.168.122.209 [49230.159044] Start test: t_modify_http_headers.test_logic.TestReqHeader.test_set_large_header Apr 26 05:44:40 192.168.122.209 [49231.236282] [tdb] Start Tempesta DB Apr 26 05:44:40 192.168.122.209 [49231.389325] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:44:42 192.168.122.209 [49232.757924] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49232.757924] Maybe that's fine, but it's worth checking the [49232.757924] config - if there is no relations between the [49232.757924] names, then host name confusion attack is possible. Apr 26 05:44:42 192.168.122.209 [49232.864688] [tempesta fw] Configuration processing is completed. Apr 26 05:44:42 192.168.122.209 [49232.915178] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:44:42 192.168.122.209 [49233.315991] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:44:42 192.168.122.209 [49233.372083] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:44:42 192.168.122.209 [49233.400632] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:44:43 192.168.122.209 [49233.460663] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:44:43 192.168.122.209 [49233.462393] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:44:43 192.168.122.209 [49233.504610] [tempesta fw] Tempesta FW is ready Apr 26 05:44:43 192.168.122.209 [49234.062584] [tdb] Close table 'client0.tdb' Apr 26 05:44:43 192.168.122.209 [49234.254381] [tdb] Close table 'sessions0.tdb' Apr 26 05:44:46 192.168.122.209 [49237.415066] [tdb] Close table 'cache0.tdb' Apr 26 05:44:47 192.168.122.209 [49237.694350] [tdb] Close table 'filter0.tdb' Apr 26 05:44:47 192.168.122.209 [49237.694768] [tempesta fw] modules are stopped Apr 26 05:44:47 192.168.122.209 [49237.901883] [tempesta fw] exiting... Apr 26 05:44:47 192.168.122.209 [49238.018320] [tdb] Shutdown Tempesta DB Apr 26 05:44:47 192.168.122.209 [49238.221486] End test: t_modify_http_headers.test_logic.TestReqHeader.test_set_large_header Apr 26 05:44:47 192.168.122.209 [49238.234888] Start test: t_modify_http_headers.test_logic.TestReqHeader.test_set_long_header_name Apr 26 05:44:48 192.168.122.209 [49239.283127] [tdb] Start Tempesta DB Apr 26 05:44:48 192.168.122.209 [49239.413722] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:44:50 192.168.122.209 [49240.814050] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49240.814050] Maybe that's fine, but it's worth checking the [49240.814050] config - if there is no relations between the [49240.814050] names, then host name confusion attack is possible. Apr 26 05:44:50 192.168.122.209 [49240.976638] [tempesta fw] Configuration processing is completed. Apr 26 05:44:50 192.168.122.209 [49241.026547] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:44:51 192.168.122.209 [49241.456557] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:44:51 192.168.122.209 [49241.482410] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:44:51 192.168.122.209 [49241.508458] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:44:51 192.168.122.209 [49241.564781] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:44:51 192.168.122.209 [49241.566511] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:44:51 192.168.122.209 [49241.604716] [tempesta fw] Tempesta FW is ready Apr 26 05:44:51 192.168.122.209 [49242.185247] [tdb] Close table 'client0.tdb' Apr 26 05:44:51 192.168.122.209 [49242.377845] [tdb] Close table 'sessions0.tdb' Apr 26 05:44:55 192.168.122.209 [49245.681928] [tdb] Close table 'cache0.tdb' Apr 26 05:44:55 192.168.122.209 [49245.931015] [tdb] Close table 'filter0.tdb' Apr 26 05:44:55 192.168.122.209 [49245.931436] [tempesta fw] modules are stopped Apr 26 05:44:55 192.168.122.209 [49246.136412] [tempesta fw] exiting... Apr 26 05:44:55 192.168.122.209 [49246.265366] [tdb] Shutdown Tempesta DB Apr 26 05:44:56 192.168.122.209 [49246.478240] End test: t_modify_http_headers.test_logic.TestReqHeader.test_set_long_header_name Apr 26 05:44:56 192.168.122.209 [49246.486930] Start test: t_modify_http_headers.test_logic.TestReqHeader.test_set_non_exist_header Apr 26 05:44:57 192.168.122.209 [49247.565361] [tdb] Start Tempesta DB Apr 26 05:44:57 192.168.122.209 [49247.696900] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:44:58 192.168.122.209 [49249.097831] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49249.097831] Maybe that's fine, but it's worth checking the [49249.097831] config - if there is no relations between the [49249.097831] names, then host name confusion attack is possible. Apr 26 05:44:58 192.168.122.209 [49249.212933] [tempesta fw] Configuration processing is completed. Apr 26 05:44:58 192.168.122.209 [49249.266612] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:44:59 192.168.122.209 [49249.678633] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:44:59 192.168.122.209 [49249.705352] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:44:59 192.168.122.209 [49249.732723] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:44:59 192.168.122.209 [49249.776858] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:44:59 192.168.122.209 [49249.778243] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:44:59 192.168.122.209 [49249.824819] [tempesta fw] Tempesta FW is ready Apr 26 05:44:59 192.168.122.209 [49250.403420] [tdb] Close table 'client0.tdb' Apr 26 05:45:00 192.168.122.209 [49250.600338] [tdb] Close table 'sessions0.tdb' Apr 26 05:45:03 192.168.122.209 [49253.765013] [tdb] Close table 'cache0.tdb' Apr 26 05:45:03 192.168.122.209 [49254.027024] [tdb] Close table 'filter0.tdb' Apr 26 05:45:03 192.168.122.209 [49254.027441] [tempesta fw] modules are stopped Apr 26 05:45:03 192.168.122.209 [49254.257453] [tempesta fw] exiting... Apr 26 05:45:03 192.168.122.209 [49254.385771] [tdb] Shutdown Tempesta DB Apr 26 05:45:04 192.168.122.209 [49254.605716] End test: t_modify_http_headers.test_logic.TestReqHeader.test_set_non_exist_header Apr 26 05:45:04 192.168.122.209 [49254.614571] Start test: t_modify_http_headers.test_logic.TestReqHeaderH2.test_add_non_exist_header Apr 26 05:45:05 192.168.122.209 [49255.633620] [tdb] Start Tempesta DB Apr 26 05:45:05 192.168.122.209 [49255.779250] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:45:06 192.168.122.209 [49257.113829] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49257.113829] Maybe that's fine, but it's worth checking the [49257.113829] config - if there is no relations between the [49257.113829] names, then host name confusion attack is possible. Apr 26 05:45:06 192.168.122.209 [49257.216952] [tempesta fw] Configuration processing is completed. Apr 26 05:45:06 192.168.122.209 [49257.267659] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:45:07 192.168.122.209 [49257.670324] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:45:07 192.168.122.209 [49257.725975] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:45:07 192.168.122.209 [49257.751411] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:45:07 192.168.122.209 [49257.812837] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:45:07 192.168.122.209 [49257.813688] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:45:07 192.168.122.209 [49257.852911] [tempesta fw] Tempesta FW is ready Apr 26 05:45:08 192.168.122.209 [49258.439236] [tdb] Close table 'client0.tdb' Apr 26 05:45:08 192.168.122.209 [49258.636516] [tdb] Close table 'sessions0.tdb' Apr 26 05:45:11 192.168.122.209 [49261.836305] [tdb] Close table 'cache0.tdb' Apr 26 05:45:11 192.168.122.209 [49262.066914] [tdb] Close table 'filter0.tdb' Apr 26 05:45:11 192.168.122.209 [49262.067353] [tempesta fw] modules are stopped Apr 26 05:45:11 192.168.122.209 [49262.293400] [tempesta fw] exiting... Apr 26 05:45:11 192.168.122.209 [49262.415251] [tdb] Shutdown Tempesta DB Apr 26 05:45:12 192.168.122.209 [49262.620914] End test: t_modify_http_headers.test_logic.TestReqHeaderH2.test_add_non_exist_header Apr 26 05:45:12 192.168.122.209 [49262.629645] Start test: t_modify_http_headers.test_logic.TestReqHeaderH2.test_delete_headers Apr 26 05:45:13 192.168.122.209 [49263.585647] [tdb] Start Tempesta DB Apr 26 05:45:13 192.168.122.209 [49263.707096] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:45:14 192.168.122.209 [49265.126318] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49265.126318] Maybe that's fine, but it's worth checking the [49265.126318] config - if there is no relations between the [49265.126318] names, then host name confusion attack is possible. Apr 26 05:45:14 192.168.122.209 [49265.225093] [tempesta fw] Configuration processing is completed. Apr 26 05:45:14 192.168.122.209 [49265.278680] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:45:15 192.168.122.209 [49265.694617] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:45:15 192.168.122.209 [49265.733261] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:45:15 192.168.122.209 [49265.758870] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:45:15 192.168.122.209 [49265.801014] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:45:15 192.168.122.209 [49265.802168] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:45:15 192.168.122.209 [49265.849025] [tempesta fw] Tempesta FW is ready Apr 26 05:45:15 192.168.122.209 [49266.405899] [tdb] Close table 'client0.tdb' Apr 26 05:45:16 192.168.122.209 [49266.587597] [tdb] Close table 'sessions0.tdb' Apr 26 05:45:19 192.168.122.209 [49269.867909] [tdb] Close table 'cache0.tdb' Apr 26 05:45:19 192.168.122.209 [49270.097670] [tdb] Close table 'filter0.tdb' Apr 26 05:45:19 192.168.122.209 [49270.098102] [tempesta fw] modules are stopped Apr 26 05:45:19 192.168.122.209 [49270.289029] [tempesta fw] exiting... Apr 26 05:45:19 192.168.122.209 [49270.419842] [tdb] Shutdown Tempesta DB Apr 26 05:45:20 192.168.122.209 [49270.653701] End test: t_modify_http_headers.test_logic.TestReqHeaderH2.test_delete_headers Apr 26 05:45:20 192.168.122.209 [49270.663344] Start test: t_modify_http_headers.test_logic.TestReqHeaderH2.test_delete_many_headers Apr 26 05:45:21 192.168.122.209 [49271.776362] [tdb] Start Tempesta DB Apr 26 05:45:21 192.168.122.209 [49271.926880] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:45:22 192.168.122.209 [49273.310427] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49273.310427] Maybe that's fine, but it's worth checking the [49273.310427] config - if there is no relations between the [49273.310427] names, then host name confusion attack is possible. Apr 26 05:45:22 192.168.122.209 [49273.409210] [tempesta fw] Configuration processing is completed. Apr 26 05:45:23 192.168.122.209 [49273.474638] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:45:23 192.168.122.209 [49273.927306] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:45:23 192.168.122.209 [49273.990253] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:45:23 192.168.122.209 [49274.020284] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:45:23 192.168.122.209 [49274.085217] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:45:23 192.168.122.209 [49274.087001] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:45:23 192.168.122.209 [49274.129150] [tempesta fw] Tempesta FW is ready Apr 26 05:45:24 192.168.122.209 [49274.733573] [tdb] Close table 'client0.tdb' Apr 26 05:45:24 192.168.122.209 [49274.920471] [tdb] Close table 'sessions0.tdb' Apr 26 05:45:27 192.168.122.209 [49278.135259] [tdb] Close table 'cache0.tdb' Apr 26 05:45:27 192.168.122.209 [49278.374176] [tdb] Close table 'filter0.tdb' Apr 26 05:45:27 192.168.122.209 [49278.374601] [tempesta fw] modules are stopped Apr 26 05:45:28 192.168.122.209 [49278.556983] [tempesta fw] exiting... Apr 26 05:45:28 192.168.122.209 [49278.667963] [tdb] Shutdown Tempesta DB Apr 26 05:45:28 192.168.122.209 [49278.871491] End test: t_modify_http_headers.test_logic.TestReqHeaderH2.test_delete_many_headers Apr 26 05:45:28 192.168.122.209 [49278.889923] Start test: t_modify_http_headers.test_logic.TestReqHeaderH2.test_delete_many_special_headers Apr 26 05:45:29 192.168.122.209 [49279.982109] [tdb] Start Tempesta DB Apr 26 05:45:29 192.168.122.209 [49280.122957] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:45:31 192.168.122.209 [49281.470546] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49281.470546] Maybe that's fine, but it's worth checking the [49281.470546] config - if there is no relations between the [49281.470546] names, then host name confusion attack is possible. Apr 26 05:45:31 192.168.122.209 [49281.573310] [tempesta fw] Configuration processing is completed. Apr 26 05:45:31 192.168.122.209 [49281.627590] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:45:31 192.168.122.209 [49282.108578] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:45:31 192.168.122.209 [49282.136835] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:45:31 192.168.122.209 [49282.166346] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:45:31 192.168.122.209 [49282.221279] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:45:31 192.168.122.209 [49282.223074] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:45:31 192.168.122.209 [49282.261158] [tempesta fw] Tempesta FW is ready Apr 26 05:45:32 192.168.122.209 [49282.826511] [tdb] Close table 'client0.tdb' Apr 26 05:45:32 192.168.122.209 [49283.010344] [tdb] Close table 'sessions0.tdb' Apr 26 05:45:35 192.168.122.209 [49286.200114] [tdb] Close table 'cache0.tdb' Apr 26 05:45:36 192.168.122.209 [49286.444976] [tdb] Close table 'filter0.tdb' Apr 26 05:45:36 192.168.122.209 [49286.445422] [tempesta fw] modules are stopped Apr 26 05:45:36 192.168.122.209 [49286.666467] [tempesta fw] exiting... Apr 26 05:45:36 192.168.122.209 [49286.770160] [tdb] Shutdown Tempesta DB Apr 26 05:45:36 192.168.122.209 [49287.019200] End test: t_modify_http_headers.test_logic.TestReqHeaderH2.test_delete_many_special_headers Apr 26 05:45:36 192.168.122.209 [49287.030784] Start test: t_modify_http_headers.test_logic.TestReqHeaderH2.test_delete_non_exist_header Apr 26 05:45:37 192.168.122.209 [49288.116189] [tdb] Start Tempesta DB Apr 26 05:45:37 192.168.122.209 [49288.253732] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:45:39 192.168.122.209 [49289.642549] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49289.642549] Maybe that's fine, but it's worth checking the [49289.642549] config - if there is no relations between the [49289.642549] names, then host name confusion attack is possible. Apr 26 05:45:39 192.168.122.209 [49289.741396] [tempesta fw] Configuration processing is completed. Apr 26 05:45:39 192.168.122.209 [49289.793206] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:45:39 192.168.122.209 [49290.225400] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:45:39 192.168.122.209 [49290.254540] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:45:39 192.168.122.209 [49290.283305] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:45:39 192.168.122.209 [49290.329380] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:45:39 192.168.122.209 [49290.330697] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:45:39 192.168.122.209 [49290.369334] [tempesta fw] Tempesta FW is ready Apr 26 05:45:40 192.168.122.209 [49290.938332] [tdb] Close table 'client0.tdb' Apr 26 05:45:40 192.168.122.209 [49291.123283] [tdb] Close table 'sessions0.tdb' Apr 26 05:45:44 192.168.122.209 [49294.490368] [tdb] Close table 'cache0.tdb' Apr 26 05:45:44 192.168.122.209 [49294.738935] [tdb] Close table 'filter0.tdb' Apr 26 05:45:44 192.168.122.209 [49294.739376] [tempesta fw] modules are stopped Apr 26 05:45:44 192.168.122.209 [49294.965029] [tempesta fw] exiting... Apr 26 05:45:44 192.168.122.209 [49295.088216] [tdb] Shutdown Tempesta DB Apr 26 05:45:44 192.168.122.209 [49295.303754] End test: t_modify_http_headers.test_logic.TestReqHeaderH2.test_delete_non_exist_header Apr 26 05:45:44 192.168.122.209 [49295.319238] Start test: t_modify_http_headers.test_logic.TestReqHeaderH2.test_delete_special_headers Apr 26 05:45:46 192.168.122.209 [49296.433956] [tdb] Start Tempesta DB Apr 26 05:45:46 192.168.122.209 [49296.587346] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:45:47 192.168.122.209 [49298.015008] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49298.015008] Maybe that's fine, but it's worth checking the [49298.015008] config - if there is no relations between the [49298.015008] names, then host name confusion attack is possible. Apr 26 05:45:47 192.168.122.209 [49298.113579] [tempesta fw] Configuration processing is completed. Apr 26 05:45:47 192.168.122.209 [49298.164487] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:45:48 192.168.122.209 [49298.569253] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:45:48 192.168.122.209 [49298.632292] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:45:48 192.168.122.209 [49298.660072] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:45:48 192.168.122.209 [49298.725405] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:45:48 192.168.122.209 [49298.726933] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:45:48 192.168.122.209 [49298.765473] [tempesta fw] Tempesta FW is ready Apr 26 05:45:48 192.168.122.209 [49299.371174] [tdb] Close table 'client0.tdb' Apr 26 05:45:49 192.168.122.209 [49299.558701] [tdb] Close table 'sessions0.tdb' Apr 26 05:45:52 192.168.122.209 [49302.821099] [tdb] Close table 'cache0.tdb' Apr 26 05:45:52 192.168.122.209 [49303.061912] [tdb] Close table 'filter0.tdb' Apr 26 05:45:52 192.168.122.209 [49303.062371] [tempesta fw] modules are stopped Apr 26 05:45:52 192.168.122.209 [49303.297762] [tempesta fw] exiting... Apr 26 05:45:52 192.168.122.209 [49303.406705] [tdb] Shutdown Tempesta DB Apr 26 05:45:53 192.168.122.209 [49303.648421] End test: t_modify_http_headers.test_logic.TestReqHeaderH2.test_delete_special_headers Apr 26 05:45:53 192.168.122.209 [49303.664416] Start test: t_modify_http_headers.test_logic.TestReqHeaderH2.test_long_header_name Apr 26 05:45:54 192.168.122.209 [49304.751140] [tdb] Start Tempesta DB Apr 26 05:45:54 192.168.122.209 [49304.905264] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:45:55 192.168.122.209 [49306.350852] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49306.350852] Maybe that's fine, but it's worth checking the [49306.350852] config - if there is no relations between the [49306.350852] names, then host name confusion attack is possible. Apr 26 05:45:56 192.168.122.209 [49306.461712] [tempesta fw] Configuration processing is completed. Apr 26 05:45:56 192.168.122.209 [49306.529813] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:45:56 192.168.122.209 [49307.085294] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:45:56 192.168.122.209 [49307.118244] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:45:56 192.168.122.209 [49307.151161] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:45:56 192.168.122.209 [49307.193521] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:45:56 192.168.122.209 [49307.194618] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:45:56 192.168.122.209 [49307.237534] [tempesta fw] Tempesta FW is ready Apr 26 05:45:57 192.168.122.209 [49307.810568] [tdb] Close table 'client0.tdb' Apr 26 05:45:57 192.168.122.209 [49307.991270] [tdb] Close table 'sessions0.tdb' Apr 26 05:46:00 192.168.122.209 [49311.348894] [tdb] Close table 'cache0.tdb' Apr 26 05:46:01 192.168.122.209 [49311.589810] [tdb] Close table 'filter0.tdb' Apr 26 05:46:01 192.168.122.209 [49311.590267] [tempesta fw] modules are stopped Apr 26 05:46:01 192.168.122.209 [49311.788221] [tempesta fw] exiting... Apr 26 05:46:01 192.168.122.209 [49311.934365] [tdb] Shutdown Tempesta DB Apr 26 05:46:01 192.168.122.209 [49312.164240] End test: t_modify_http_headers.test_logic.TestReqHeaderH2.test_long_header_name Apr 26 05:46:01 192.168.122.209 [49312.181599] Start test: t_modify_http_headers.test_logic.TestReqHeaderH2.test_set_exist_header Apr 26 05:46:02 192.168.122.209 [49313.338994] [tdb] Start Tempesta DB Apr 26 05:46:03 192.168.122.209 [49313.474105] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:46:04 192.168.122.209 [49314.858478] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49314.858478] Maybe that's fine, but it's worth checking the [49314.858478] config - if there is no relations between the [49314.858478] names, then host name confusion attack is possible. Apr 26 05:46:04 192.168.122.209 [49314.961751] [tempesta fw] Configuration processing is completed. Apr 26 05:46:04 192.168.122.209 [49315.020311] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:46:05 192.168.122.209 [49315.432227] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:46:05 192.168.122.209 [49315.489935] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:46:05 192.168.122.209 [49315.517056] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:46:05 192.168.122.209 [49315.569609] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:46:05 192.168.122.209 [49315.570436] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:46:05 192.168.122.209 [49315.645672] [tempesta fw] Tempesta FW is ready Apr 26 05:46:05 192.168.122.209 [49316.213748] [tdb] Close table 'client0.tdb' Apr 26 05:46:05 192.168.122.209 [49316.398782] [tdb] Close table 'sessions0.tdb' Apr 26 05:46:09 192.168.122.209 [49319.560709] [tdb] Close table 'cache0.tdb' Apr 26 05:46:09 192.168.122.209 [49319.814472] [tdb] Close table 'filter0.tdb' Apr 26 05:46:09 192.168.122.209 [49319.814915] [tempesta fw] modules are stopped Apr 26 05:46:09 192.168.122.209 [49320.023455] [tempesta fw] exiting... Apr 26 05:46:09 192.168.122.209 [49320.171511] [tdb] Shutdown Tempesta DB Apr 26 05:46:09 192.168.122.209 [49320.372097] End test: t_modify_http_headers.test_logic.TestReqHeaderH2.test_set_exist_header Apr 26 05:46:09 192.168.122.209 [49320.386132] Start test: t_modify_http_headers.test_logic.TestReqHeaderH2.test_set_exist_special_header Apr 26 05:46:10 192.168.122.209 [49321.411664] [tdb] Start Tempesta DB Apr 26 05:46:11 192.168.122.209 [49321.545491] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:46:12 192.168.122.209 [49322.919052] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49322.919052] Maybe that's fine, but it's worth checking the [49322.919052] config - if there is no relations between the [49322.919052] names, then host name confusion attack is possible. Apr 26 05:46:12 192.168.122.209 [49323.017894] [tempesta fw] Configuration processing is completed. Apr 26 05:46:12 192.168.122.209 [49323.062206] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:46:13 192.168.122.209 [49323.471814] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:46:13 192.168.122.209 [49323.497425] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:46:13 192.168.122.209 [49323.522692] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:46:13 192.168.122.209 [49323.561724] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:46:13 192.168.122.209 [49323.562719] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:46:13 192.168.122.209 [49323.605680] [tempesta fw] Tempesta FW is ready Apr 26 05:46:13 192.168.122.209 [49324.150991] [tdb] Close table 'client0.tdb' Apr 26 05:46:13 192.168.122.209 [49324.418924] [tdb] Close table 'sessions0.tdb' Apr 26 05:46:17 192.168.122.209 [49327.672920] [tdb] Close table 'cache0.tdb' Apr 26 05:46:17 192.168.122.209 [49327.885927] [tdb] Close table 'filter0.tdb' Apr 26 05:46:17 192.168.122.209 [49327.886364] [tempesta fw] modules are stopped Apr 26 05:46:17 192.168.122.209 [49328.070236] [tempesta fw] exiting... Apr 26 05:46:17 192.168.122.209 [49328.202430] [tdb] Shutdown Tempesta DB Apr 26 05:46:17 192.168.122.209 [49328.402332] End test: t_modify_http_headers.test_logic.TestReqHeaderH2.test_set_exist_special_header Apr 26 05:46:17 192.168.122.209 [49328.419947] Start test: t_modify_http_headers.test_logic.TestReqHeaderH2.test_set_header_name_greater_than_1024 Apr 26 05:46:18 192.168.122.209 [49329.414369] [tdb] Start Tempesta DB Apr 26 05:46:19 192.168.122.209 [49329.554326] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:46:20 192.168.122.209 [49330.907162] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49330.907162] Maybe that's fine, but it's worth checking the [49330.907162] config - if there is no relations between the [49330.907162] names, then host name confusion attack is possible. Apr 26 05:46:20 192.168.122.209 [49331.013920] [tempesta fw] Configuration processing is completed. Apr 26 05:46:20 192.168.122.209 [49331.065512] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:46:21 192.168.122.209 [49331.473476] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:46:21 192.168.122.209 [49331.529439] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:46:21 192.168.122.209 [49331.555215] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:46:21 192.168.122.209 [49331.605809] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:46:21 192.168.122.209 [49331.606562] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:46:21 192.168.122.209 [49331.645840] [tempesta fw] Tempesta FW is ready Apr 26 05:46:21 192.168.122.209 [49332.193436] [tdb] Close table 'client0.tdb' Apr 26 05:46:21 192.168.122.209 [49332.390632] [tdb] Close table 'sessions0.tdb' Apr 26 05:46:25 192.168.122.209 [49335.580058] [tdb] Close table 'cache0.tdb' Apr 26 05:46:25 192.168.122.209 [49335.815813] [tdb] Close table 'filter0.tdb' Apr 26 05:46:25 192.168.122.209 [49335.816250] [tempesta fw] modules are stopped Apr 26 05:46:25 192.168.122.209 [49336.005473] [tempesta fw] exiting... Apr 26 05:46:25 192.168.122.209 [49336.133055] [tdb] Shutdown Tempesta DB Apr 26 05:46:25 192.168.122.209 [49336.340005] End test: t_modify_http_headers.test_logic.TestReqHeaderH2.test_set_header_name_greater_than_1024 Apr 26 05:46:25 192.168.122.209 [49336.355117] Start test: t_modify_http_headers.test_logic.TestReqHeaderH2.test_set_large_header Apr 26 05:46:27 192.168.122.209 [49337.444397] [tdb] Start Tempesta DB Apr 26 05:46:27 192.168.122.209 [49337.579317] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:46:28 192.168.122.209 [49339.039243] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49339.039243] Maybe that's fine, but it's worth checking the [49339.039243] config - if there is no relations between the [49339.039243] names, then host name confusion attack is possible. Apr 26 05:46:28 192.168.122.209 [49339.138002] [tempesta fw] Configuration processing is completed. Apr 26 05:46:28 192.168.122.209 [49339.188051] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:46:29 192.168.122.209 [49339.601396] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:46:29 192.168.122.209 [49339.626947] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:46:29 192.168.122.209 [49339.652882] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:46:29 192.168.122.209 [49339.697965] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:46:29 192.168.122.209 [49339.699119] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:46:29 192.168.122.209 [49339.737950] [tempesta fw] Tempesta FW is ready Apr 26 05:46:29 192.168.122.209 [49340.314964] [tdb] Close table 'client0.tdb' Apr 26 05:46:30 192.168.122.209 [49340.500535] [tdb] Close table 'sessions0.tdb' Apr 26 05:46:33 192.168.122.209 [49343.687796] [tdb] Close table 'cache0.tdb' Apr 26 05:46:33 192.168.122.209 [49343.928343] [tdb] Close table 'filter0.tdb' Apr 26 05:46:33 192.168.122.209 [49343.928778] [tempesta fw] modules are stopped Apr 26 05:46:33 192.168.122.209 [49344.119829] [tempesta fw] exiting... Apr 26 05:46:33 192.168.122.209 [49344.246415] [tdb] Shutdown Tempesta DB Apr 26 05:46:33 192.168.122.209 [49344.409840] End test: t_modify_http_headers.test_logic.TestReqHeaderH2.test_set_large_header Apr 26 05:46:33 192.168.122.209 [49344.420630] Start test: t_modify_http_headers.test_logic.TestReqHeaderH2.test_set_long_header_name Apr 26 05:46:35 192.168.122.209 [49345.492715] [tdb] Start Tempesta DB Apr 26 05:46:35 192.168.122.209 [49345.631287] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:46:36 192.168.122.209 [49347.078866] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49347.078866] Maybe that's fine, but it's worth checking the [49347.078866] config - if there is no relations between the [49347.078866] names, then host name confusion attack is possible. Apr 26 05:46:36 192.168.122.209 [49347.226004] [tempesta fw] Configuration processing is completed. Apr 26 05:46:36 192.168.122.209 [49347.273118] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:46:37 192.168.122.209 [49347.741136] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:46:37 192.168.122.209 [49347.769837] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:46:37 192.168.122.209 [49347.798917] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:46:37 192.168.122.209 [49347.854017] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:46:37 192.168.122.209 [49347.855454] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:46:37 192.168.122.209 [49347.902063] [tempesta fw] Tempesta FW is ready Apr 26 05:46:38 192.168.122.209 [49348.468267] [tdb] Close table 'client0.tdb' Apr 26 05:46:38 192.168.122.209 [49348.653825] [tdb] Close table 'sessions0.tdb' Apr 26 05:46:41 192.168.122.209 [49351.839133] [tdb] Close table 'cache0.tdb' Apr 26 05:46:41 192.168.122.209 [49352.068544] [tdb] Close table 'filter0.tdb' Apr 26 05:46:41 192.168.122.209 [49352.068972] [tempesta fw] modules are stopped Apr 26 05:46:41 192.168.122.209 [49352.244916] [tempesta fw] exiting... Apr 26 05:46:41 192.168.122.209 [49352.356473] [tdb] Shutdown Tempesta DB Apr 26 05:46:42 192.168.122.209 [49352.579586] End test: t_modify_http_headers.test_logic.TestReqHeaderH2.test_set_long_header_name Apr 26 05:46:42 192.168.122.209 [49352.601905] Start test: t_modify_http_headers.test_logic.TestReqHeaderH2.test_set_non_exist_header Apr 26 05:46:43 192.168.122.209 [49353.601255] [tdb] Start Tempesta DB Apr 26 05:46:43 192.168.122.209 [49353.739469] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:46:44 192.168.122.209 [49355.251164] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49355.251164] Maybe that's fine, but it's worth checking the [49355.251164] config - if there is no relations between the [49355.251164] names, then host name confusion attack is possible. Apr 26 05:46:44 192.168.122.209 [49355.354228] [tempesta fw] Configuration processing is completed. Apr 26 05:46:44 192.168.122.209 [49355.404414] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:46:45 192.168.122.209 [49355.804779] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:46:45 192.168.122.209 [49355.867726] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:46:45 192.168.122.209 [49355.894414] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:46:45 192.168.122.209 [49355.938172] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:46:45 192.168.122.209 [49355.939499] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:46:45 192.168.122.209 [49355.986145] [tempesta fw] Tempesta FW is ready Apr 26 05:46:46 192.168.122.209 [49356.552648] [tdb] Close table 'client0.tdb' Apr 26 05:46:46 192.168.122.209 [49356.740495] [tdb] Close table 'sessions0.tdb' Apr 26 05:46:49 192.168.122.209 [49359.905972] [tdb] Close table 'cache0.tdb' Apr 26 05:46:49 192.168.122.209 [49360.166861] [tdb] Close table 'filter0.tdb' Apr 26 05:46:49 192.168.122.209 [49360.167300] [tempesta fw] modules are stopped Apr 26 05:46:49 192.168.122.209 [49360.361891] [tempesta fw] exiting... Apr 26 05:46:50 192.168.122.209 [49360.498457] [tdb] Shutdown Tempesta DB Apr 26 05:46:50 192.168.122.209 [49360.728106] End test: t_modify_http_headers.test_logic.TestReqHeaderH2.test_set_non_exist_header Apr 26 05:46:50 192.168.122.209 [49360.737886] Start test: t_modify_http_headers.test_logic.TestRespHeader.test_add_non_exist_header Apr 26 05:46:51 192.168.122.209 [49361.796863] [tdb] Start Tempesta DB Apr 26 05:46:51 192.168.122.209 [49361.927893] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:46:52 192.168.122.209 [49363.263599] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49363.263599] Maybe that's fine, but it's worth checking the [49363.263599] config - if there is no relations between the [49363.263599] names, then host name confusion attack is possible. Apr 26 05:46:52 192.168.122.209 [49363.378264] [tempesta fw] Configuration processing is completed. Apr 26 05:46:53 192.168.122.209 [49363.430578] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:46:53 192.168.122.209 [49363.842976] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:46:53 192.168.122.209 [49363.869535] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:46:53 192.168.122.209 [49363.895197] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:46:53 192.168.122.209 [49363.966301] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:46:53 192.168.122.209 [49363.968071] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:46:53 192.168.122.209 [49364.010244] [tempesta fw] Tempesta FW is ready Apr 26 05:46:54 192.168.122.209 [49364.574751] [tdb] Close table 'client0.tdb' Apr 26 05:46:54 192.168.122.209 [49364.771944] [tdb] Close table 'sessions0.tdb' Apr 26 05:46:57 192.168.122.209 [49367.956482] [tdb] Close table 'cache0.tdb' Apr 26 05:46:57 192.168.122.209 [49368.196739] [tdb] Close table 'filter0.tdb' Apr 26 05:46:57 192.168.122.209 [49368.197161] [tempesta fw] modules are stopped Apr 26 05:46:57 192.168.122.209 [49368.379906] [tempesta fw] exiting... Apr 26 05:46:58 192.168.122.209 [49368.495884] [tdb] Shutdown Tempesta DB Apr 26 05:46:58 192.168.122.209 [49368.742044] End test: t_modify_http_headers.test_logic.TestRespHeader.test_add_non_exist_header Apr 26 05:46:58 192.168.122.209 [49368.753590] Start test: t_modify_http_headers.test_logic.TestRespHeader.test_delete_headers Apr 26 05:46:59 192.168.122.209 [49369.819587] [tdb] Start Tempesta DB Apr 26 05:46:59 192.168.122.209 [49369.950884] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:47:00 192.168.122.209 [49371.347573] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49371.347573] Maybe that's fine, but it's worth checking the [49371.347573] config - if there is no relations between the [49371.347573] names, then host name confusion attack is possible. Apr 26 05:47:01 192.168.122.209 [49371.482291] [tempesta fw] Configuration processing is completed. Apr 26 05:47:01 192.168.122.209 [49371.533233] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:47:01 192.168.122.209 [49371.939470] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:47:01 192.168.122.209 [49371.964913] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:47:01 192.168.122.209 [49371.990653] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:47:01 192.168.122.209 [49372.030341] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:47:01 192.168.122.209 [49372.031252] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:47:01 192.168.122.209 [49372.074344] [tempesta fw] Tempesta FW is ready Apr 26 05:47:02 192.168.122.209 [49372.638485] [tdb] Close table 'client0.tdb' Apr 26 05:47:02 192.168.122.209 [49372.829404] [tdb] Close table 'sessions0.tdb' Apr 26 05:47:05 192.168.122.209 [49376.011035] [tdb] Close table 'cache0.tdb' Apr 26 05:47:05 192.168.122.209 [49376.260589] [tdb] Close table 'filter0.tdb' Apr 26 05:47:05 192.168.122.209 [49376.261032] [tempesta fw] modules are stopped Apr 26 05:47:06 192.168.122.209 [49376.462611] [tempesta fw] exiting... Apr 26 05:47:06 192.168.122.209 [49376.609424] [tdb] Shutdown Tempesta DB Apr 26 05:47:06 192.168.122.209 [49376.839165] End test: t_modify_http_headers.test_logic.TestRespHeader.test_delete_headers Apr 26 05:47:06 192.168.122.209 [49376.846125] Start test: t_modify_http_headers.test_logic.TestRespHeader.test_delete_many_headers Apr 26 05:47:07 192.168.122.209 [49377.869191] [tdb] Start Tempesta DB Apr 26 05:47:07 192.168.122.209 [49378.015228] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:47:09 192.168.122.209 [49379.432007] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49379.432007] Maybe that's fine, but it's worth checking the [49379.432007] config - if there is no relations between the [49379.432007] names, then host name confusion attack is possible. Apr 26 05:47:09 192.168.122.209 [49379.534521] [tempesta fw] Configuration processing is completed. Apr 26 05:47:09 192.168.122.209 [49379.584527] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:47:09 192.168.122.209 [49380.027732] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:47:09 192.168.122.209 [49380.087270] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:47:09 192.168.122.209 [49380.113158] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:47:09 192.168.122.209 [49380.158496] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:47:09 192.168.122.209 [49380.159718] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:47:09 192.168.122.209 [49380.194450] [tempesta fw] Tempesta FW is ready Apr 26 05:47:10 192.168.122.209 [49380.736252] [tdb] Close table 'client0.tdb' Apr 26 05:47:10 192.168.122.209 [49380.913416] [tdb] Close table 'sessions0.tdb' Apr 26 05:47:13 192.168.122.209 [49384.104970] [tdb] Close table 'cache0.tdb' Apr 26 05:47:13 192.168.122.209 [49384.329275] [tdb] Close table 'filter0.tdb' Apr 26 05:47:13 192.168.122.209 [49384.329707] [tempesta fw] modules are stopped Apr 26 05:47:14 192.168.122.209 [49384.563174] [tempesta fw] exiting... Apr 26 05:47:14 192.168.122.209 [49384.689708] [tdb] Shutdown Tempesta DB Apr 26 05:47:14 192.168.122.209 [49384.924336] End test: t_modify_http_headers.test_logic.TestRespHeader.test_delete_many_headers Apr 26 05:47:14 192.168.122.209 [49384.935928] Start test: t_modify_http_headers.test_logic.TestRespHeader.test_delete_many_special_headers Apr 26 05:47:15 192.168.122.209 [49385.988830] [tdb] Start Tempesta DB Apr 26 05:47:15 192.168.122.209 [49386.149666] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:47:17 192.168.122.209 [49387.663419] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49387.663419] Maybe that's fine, but it's worth checking the [49387.663419] config - if there is no relations between the [49387.663419] names, then host name confusion attack is possible. Apr 26 05:47:17 192.168.122.209 [49387.758630] [tempesta fw] Configuration processing is completed. Apr 26 05:47:17 192.168.122.209 [49387.811480] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:47:17 192.168.122.209 [49388.226486] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:47:17 192.168.122.209 [49388.251977] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:47:17 192.168.122.209 [49388.278024] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:47:17 192.168.122.209 [49388.330539] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:47:17 192.168.122.209 [49388.332115] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:47:17 192.168.122.209 [49388.374561] [tempesta fw] Tempesta FW is ready Apr 26 05:47:18 192.168.122.209 [49389.001842] [tdb] Close table 'client0.tdb' Apr 26 05:47:18 192.168.122.209 [49389.232882] [tdb] Close table 'sessions0.tdb' Apr 26 05:47:22 192.168.122.209 [49392.545265] [tdb] Close table 'cache0.tdb' Apr 26 05:47:22 192.168.122.209 [49392.780574] [tdb] Close table 'filter0.tdb' Apr 26 05:47:22 192.168.122.209 [49392.781015] [tempesta fw] modules are stopped Apr 26 05:47:22 192.168.122.209 [49392.987057] [tempesta fw] exiting... Apr 26 05:47:22 192.168.122.209 [49393.111319] [tdb] Shutdown Tempesta DB Apr 26 05:47:22 192.168.122.209 [49393.302449] End test: t_modify_http_headers.test_logic.TestRespHeader.test_delete_many_special_headers Apr 26 05:47:22 192.168.122.209 [49393.326696] Start test: t_modify_http_headers.test_logic.TestRespHeader.test_delete_non_exist_header Apr 26 05:47:23 192.168.122.209 [49394.423015] [tdb] Start Tempesta DB Apr 26 05:47:24 192.168.122.209 [49394.559006] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:47:25 192.168.122.209 [49395.964347] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49395.964347] Maybe that's fine, but it's worth checking the [49395.964347] config - if there is no relations between the [49395.964347] names, then host name confusion attack is possible. Apr 26 05:47:25 192.168.122.209 [49396.058731] [tempesta fw] Configuration processing is completed. Apr 26 05:47:25 192.168.122.209 [49396.110374] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:47:26 192.168.122.209 [49396.516735] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:47:26 192.168.122.209 [49396.572775] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:47:26 192.168.122.209 [49396.598550] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:47:26 192.168.122.209 [49396.638647] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:47:26 192.168.122.209 [49396.639674] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:47:26 192.168.122.209 [49396.686652] [tempesta fw] Tempesta FW is ready Apr 26 05:47:26 192.168.122.209 [49397.218695] [tdb] Close table 'client0.tdb' Apr 26 05:47:26 192.168.122.209 [49397.420806] [tdb] Close table 'sessions0.tdb' Apr 26 05:47:30 192.168.122.209 [49400.605771] [tdb] Close table 'cache0.tdb' Apr 26 05:47:30 192.168.122.209 [49400.849431] [tdb] Close table 'filter0.tdb' Apr 26 05:47:30 192.168.122.209 [49400.849850] [tempesta fw] modules are stopped Apr 26 05:47:30 192.168.122.209 [49401.022755] [tempesta fw] exiting... Apr 26 05:47:30 192.168.122.209 [49401.148005] [tdb] Shutdown Tempesta DB Apr 26 05:47:30 192.168.122.209 [49401.371763] End test: t_modify_http_headers.test_logic.TestRespHeader.test_delete_non_exist_header Apr 26 05:47:30 192.168.122.209 [49401.381587] Start test: t_modify_http_headers.test_logic.TestRespHeader.test_delete_special_headers Apr 26 05:47:31 192.168.122.209 [49402.425180] [tdb] Start Tempesta DB Apr 26 05:47:32 192.168.122.209 [49402.561187] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:47:33 192.168.122.209 [49403.936031] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49403.936031] Maybe that's fine, but it's worth checking the [49403.936031] config - if there is no relations between the [49403.936031] names, then host name confusion attack is possible. Apr 26 05:47:33 192.168.122.209 [49404.042869] [tempesta fw] Configuration processing is completed. Apr 26 05:47:33 192.168.122.209 [49404.094765] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:47:34 192.168.122.209 [49404.510118] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:47:34 192.168.122.209 [49404.536005] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:47:34 192.168.122.209 [49404.561284] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:47:34 192.168.122.209 [49404.610803] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:47:34 192.168.122.209 [49404.612409] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:47:34 192.168.122.209 [49404.662765] [tempesta fw] Tempesta FW is ready Apr 26 05:47:34 192.168.122.209 [49405.221177] [tdb] Close table 'client0.tdb' Apr 26 05:47:34 192.168.122.209 [49405.414090] [tdb] Close table 'sessions0.tdb' Apr 26 05:47:38 192.168.122.209 [49408.629374] [tdb] Close table 'cache0.tdb' Apr 26 05:47:38 192.168.122.209 [49408.877797] [tdb] Close table 'filter0.tdb' Apr 26 05:47:38 192.168.122.209 [49408.878247] [tempesta fw] modules are stopped Apr 26 05:47:38 192.168.122.209 [49409.082374] [tempesta fw] exiting... Apr 26 05:47:38 192.168.122.209 [49409.218007] [tdb] Shutdown Tempesta DB Apr 26 05:47:39 192.168.122.209 [49409.438999] End test: t_modify_http_headers.test_logic.TestRespHeader.test_delete_special_headers Apr 26 05:47:39 192.168.122.209 [49409.464328] Start test: t_modify_http_headers.test_logic.TestRespHeader.test_long_header_name Apr 26 05:47:40 192.168.122.209 [49410.548463] [tdb] Start Tempesta DB Apr 26 05:47:40 192.168.122.209 [49410.683082] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:47:41 192.168.122.209 [49412.100240] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49412.100240] Maybe that's fine, but it's worth checking the [49412.100240] config - if there is no relations between the [49412.100240] names, then host name confusion attack is possible. Apr 26 05:47:41 192.168.122.209 [49412.206949] [tempesta fw] Configuration processing is completed. Apr 26 05:47:41 192.168.122.209 [49412.263837] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:47:42 192.168.122.209 [49412.672255] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:47:42 192.168.122.209 [49412.729559] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:47:42 192.168.122.209 [49412.762859] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:47:42 192.168.122.209 [49412.810901] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:47:42 192.168.122.209 [49412.812296] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:47:42 192.168.122.209 [49412.854784] [tempesta fw] Tempesta FW is ready Apr 26 05:47:42 192.168.122.209 [49413.414651] [tdb] Close table 'client0.tdb' Apr 26 05:47:43 192.168.122.209 [49413.603338] [tdb] Close table 'sessions0.tdb' Apr 26 05:47:46 192.168.122.209 [49416.812886] [tdb] Close table 'cache0.tdb' Apr 26 05:47:46 192.168.122.209 [49417.077671] [tdb] Close table 'filter0.tdb' Apr 26 05:47:46 192.168.122.209 [49417.078507] [tempesta fw] modules are stopped Apr 26 05:47:46 192.168.122.209 [49417.271033] [tempesta fw] exiting... Apr 26 05:47:46 192.168.122.209 [49417.378126] [tdb] Shutdown Tempesta DB Apr 26 05:47:47 192.168.122.209 [49417.595119] End test: t_modify_http_headers.test_logic.TestRespHeader.test_long_header_name Apr 26 05:47:47 192.168.122.209 [49417.603734] Start test: t_modify_http_headers.test_logic.TestRespHeader.test_set_exist_header Apr 26 05:47:48 192.168.122.209 [49418.687393] [tdb] Start Tempesta DB Apr 26 05:47:48 192.168.122.209 [49418.830159] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:47:49 192.168.122.209 [49420.215740] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49420.215740] Maybe that's fine, but it's worth checking the [49420.215740] config - if there is no relations between the [49420.215740] names, then host name confusion attack is possible. Apr 26 05:47:49 192.168.122.209 [49420.311048] [tempesta fw] Configuration processing is completed. Apr 26 05:47:49 192.168.122.209 [49420.363984] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:47:50 192.168.122.209 [49420.779352] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:47:50 192.168.122.209 [49420.852782] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:47:50 192.168.122.209 [49420.878544] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:47:50 192.168.122.209 [49420.922982] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:47:50 192.168.122.209 [49420.924376] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:47:50 192.168.122.209 [49420.958968] [tempesta fw] Tempesta FW is ready Apr 26 05:47:51 192.168.122.209 [49421.516429] [tdb] Close table 'client0.tdb' Apr 26 05:47:51 192.168.122.209 [49421.700969] [tdb] Close table 'sessions0.tdb' Apr 26 05:47:54 192.168.122.209 [49425.058815] [tdb] Close table 'cache0.tdb' Apr 26 05:47:54 192.168.122.209 [49425.281619] [tdb] Close table 'filter0.tdb' Apr 26 05:47:54 192.168.122.209 [49425.282062] [tempesta fw] modules are stopped Apr 26 05:47:55 192.168.122.209 [49425.524555] [tempesta fw] exiting... Apr 26 05:47:55 192.168.122.209 [49425.643266] [tdb] Shutdown Tempesta DB Apr 26 05:47:55 192.168.122.209 [49425.871798] End test: t_modify_http_headers.test_logic.TestRespHeader.test_set_exist_header Apr 26 05:47:55 192.168.122.209 [49425.893795] Start test: t_modify_http_headers.test_logic.TestRespHeader.test_set_exist_special_header Apr 26 05:47:56 192.168.122.209 [49426.950620] [tdb] Start Tempesta DB Apr 26 05:47:56 192.168.122.209 [49427.097950] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:47:58 192.168.122.209 [49428.520348] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49428.520348] Maybe that's fine, but it's worth checking the [49428.520348] config - if there is no relations between the [49428.520348] names, then host name confusion attack is possible. Apr 26 05:47:58 192.168.122.209 [49428.635186] [tempesta fw] Configuration processing is completed. Apr 26 05:47:58 192.168.122.209 [49428.701459] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:47:58 192.168.122.209 [49429.116917] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:47:58 192.168.122.209 [49429.142817] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:47:58 192.168.122.209 [49429.168634] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:47:58 192.168.122.209 [49429.219129] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:47:58 192.168.122.209 [49429.220882] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:47:58 192.168.122.209 [49429.259076] [tempesta fw] Tempesta FW is ready Apr 26 05:47:59 192.168.122.209 [49429.842440] [tdb] Close table 'client0.tdb' Apr 26 05:47:59 192.168.122.209 [49430.033009] [tdb] Close table 'sessions0.tdb' Apr 26 05:48:02 192.168.122.209 [49433.316123] [tdb] Close table 'cache0.tdb' Apr 26 05:48:03 192.168.122.209 [49433.542802] [tdb] Close table 'filter0.tdb' Apr 26 05:48:03 192.168.122.209 [49433.543257] [tempesta fw] modules are stopped Apr 26 05:48:03 192.168.122.209 [49433.724506] [tempesta fw] exiting... Apr 26 05:48:03 192.168.122.209 [49433.863831] [tdb] Shutdown Tempesta DB Apr 26 05:48:03 192.168.122.209 [49434.083692] End test: t_modify_http_headers.test_logic.TestRespHeader.test_set_exist_special_header Apr 26 05:48:03 192.168.122.209 [49434.107841] Start test: t_modify_http_headers.test_logic.TestRespHeader.test_set_header_name_greater_than_1024 Apr 26 05:48:04 192.168.122.209 [49435.183613] [tdb] Start Tempesta DB Apr 26 05:48:04 192.168.122.209 [49435.327111] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:48:06 192.168.122.209 [49436.724490] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49436.724490] Maybe that's fine, but it's worth checking the [49436.724490] config - if there is no relations between the [49436.724490] names, then host name confusion attack is possible. Apr 26 05:48:06 192.168.122.209 [49436.831246] [tempesta fw] Configuration processing is completed. Apr 26 05:48:06 192.168.122.209 [49436.881964] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:48:06 192.168.122.209 [49437.288079] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:48:06 192.168.122.209 [49437.345263] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:48:06 192.168.122.209 [49437.378102] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:48:06 192.168.122.209 [49437.423171] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:48:06 192.168.122.209 [49437.424348] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:48:07 192.168.122.209 [49437.467195] [tempesta fw] Tempesta FW is ready Apr 26 05:48:07 192.168.122.209 [49437.995165] [tdb] Close table 'client0.tdb' Apr 26 05:48:07 192.168.122.209 [49438.179532] [tdb] Close table 'sessions0.tdb' Apr 26 05:48:11 192.168.122.209 [49441.487239] [tdb] Close table 'cache0.tdb' Apr 26 05:48:11 192.168.122.209 [49441.717351] [tdb] Close table 'filter0.tdb' Apr 26 05:48:11 192.168.122.209 [49441.717791] [tempesta fw] modules are stopped Apr 26 05:48:11 192.168.122.209 [49441.906512] [tempesta fw] exiting... Apr 26 05:48:11 192.168.122.209 [49442.072675] [tdb] Shutdown Tempesta DB Apr 26 05:48:11 192.168.122.209 [49442.280759] End test: t_modify_http_headers.test_logic.TestRespHeader.test_set_header_name_greater_than_1024 Apr 26 05:48:11 192.168.122.209 [49442.293032] Start test: t_modify_http_headers.test_logic.TestRespHeader.test_set_large_header Apr 26 05:48:12 192.168.122.209 [49443.268225] [tdb] Start Tempesta DB Apr 26 05:48:12 192.168.122.209 [49443.410399] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:48:14 192.168.122.209 [49444.692577] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49444.692577] Maybe that's fine, but it's worth checking the [49444.692577] config - if there is no relations between the [49444.692577] names, then host name confusion attack is possible. Apr 26 05:48:14 192.168.122.209 [49444.795346] [tempesta fw] Configuration processing is completed. Apr 26 05:48:14 192.168.122.209 [49444.852782] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:48:14 192.168.122.209 [49445.280247] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:48:14 192.168.122.209 [49445.306408] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:48:14 192.168.122.209 [49445.336293] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:48:14 192.168.122.209 [49445.371263] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:48:14 192.168.122.209 [49445.372326] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:48:14 192.168.122.209 [49445.411280] [tempesta fw] Tempesta FW is ready Apr 26 05:48:15 192.168.122.209 [49446.022002] [tdb] Close table 'client0.tdb' Apr 26 05:48:15 192.168.122.209 [49446.230208] [tdb] Close table 'sessions0.tdb' Apr 26 05:48:19 192.168.122.209 [49449.495765] [tdb] Close table 'cache0.tdb' Apr 26 05:48:19 192.168.122.209 [49449.733322] [tdb] Close table 'filter0.tdb' Apr 26 05:48:19 192.168.122.209 [49449.733769] [tempesta fw] modules are stopped Apr 26 05:48:19 192.168.122.209 [49449.937568] [tempesta fw] exiting... Apr 26 05:48:19 192.168.122.209 [49450.058444] [tdb] Shutdown Tempesta DB Apr 26 05:48:19 192.168.122.209 [49450.276270] End test: t_modify_http_headers.test_logic.TestRespHeader.test_set_large_header Apr 26 05:48:19 192.168.122.209 [49450.311723] Start test: t_modify_http_headers.test_logic.TestRespHeader.test_set_long_header_name Apr 26 05:48:20 192.168.122.209 [49451.419433] [tdb] Start Tempesta DB Apr 26 05:48:21 192.168.122.209 [49451.558016] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:48:22 192.168.122.209 [49453.028146] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49453.028146] Maybe that's fine, but it's worth checking the [49453.028146] config - if there is no relations between the [49453.028146] names, then host name confusion attack is possible. Apr 26 05:48:22 192.168.122.209 [49453.179460] [tempesta fw] Configuration processing is completed. Apr 26 05:48:22 192.168.122.209 [49453.230307] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:48:23 192.168.122.209 [49453.642118] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:48:23 192.168.122.209 [49453.715334] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:48:23 192.168.122.209 [49453.741047] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:48:23 192.168.122.209 [49453.795442] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:48:23 192.168.122.209 [49453.797220] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:48:23 192.168.122.209 [49453.835369] [tempesta fw] Tempesta FW is ready Apr 26 05:48:24 192.168.122.209 [49455.149228] [tdb] Close table 'client0.tdb' Apr 26 05:48:25 192.168.122.209 [49455.440524] [tdb] Close table 'sessions0.tdb' Apr 26 05:48:29 192.168.122.209 [49460.173920] [tdb] Close table 'cache0.tdb' Apr 26 05:48:30 192.168.122.209 [49460.623454] [tdb] Close table 'filter0.tdb' Apr 26 05:48:30 192.168.122.209 [49460.623903] [tempesta fw] modules are stopped Apr 26 05:48:30 192.168.122.209 [49460.839796] [tempesta fw] exiting... Apr 26 05:48:30 192.168.122.209 [49460.965703] [tdb] Shutdown Tempesta DB Apr 26 05:48:30 192.168.122.209 [49461.180460] End test: t_modify_http_headers.test_logic.TestRespHeader.test_set_long_header_name Apr 26 05:48:30 192.168.122.209 [49461.200766] Start test: t_modify_http_headers.test_logic.TestRespHeader.test_set_non_exist_header Apr 26 05:48:31 192.168.122.209 [49462.293316] [tdb] Start Tempesta DB Apr 26 05:48:32 192.168.122.209 [49462.440025] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:48:33 192.168.122.209 [49463.840258] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49463.840258] Maybe that's fine, but it's worth checking the [49463.840258] config - if there is no relations between the [49463.840258] names, then host name confusion attack is possible. Apr 26 05:48:33 192.168.122.209 [49463.939600] [tempesta fw] Configuration processing is completed. Apr 26 05:48:33 192.168.122.209 [49463.996010] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:48:33 192.168.122.209 [49464.417453] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:48:34 192.168.122.209 [49464.443568] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:48:34 192.168.122.209 [49464.469436] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:48:34 192.168.122.209 [49464.507506] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:48:34 192.168.122.209 [49464.508555] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:48:34 192.168.122.209 [49464.551510] [tempesta fw] Tempesta FW is ready Apr 26 05:48:34 192.168.122.209 [49465.140995] [tdb] Close table 'client0.tdb' Apr 26 05:48:34 192.168.122.209 [49465.320089] [tdb] Close table 'sessions0.tdb' Apr 26 05:48:38 192.168.122.209 [49468.630937] [tdb] Close table 'cache0.tdb' Apr 26 05:48:38 192.168.122.209 [49468.878824] [tdb] Close table 'filter0.tdb' Apr 26 05:48:38 192.168.122.209 [49468.879269] [tempesta fw] modules are stopped Apr 26 05:48:38 192.168.122.209 [49469.106676] [tempesta fw] exiting... Apr 26 05:48:38 192.168.122.209 [49469.253140] [tdb] Shutdown Tempesta DB Apr 26 05:48:39 192.168.122.209 [49469.442913] End test: t_modify_http_headers.test_logic.TestRespHeader.test_set_non_exist_header Apr 26 05:48:39 192.168.122.209 [49469.456657] Start test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_add_header_from_dynamic_table Apr 26 05:48:40 192.168.122.209 [49470.581035] [tdb] Start Tempesta DB Apr 26 05:48:40 192.168.122.209 [49470.707781] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:48:41 192.168.122.209 [49472.024909] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49472.024909] Maybe that's fine, but it's worth checking the [49472.024909] config - if there is no relations between the [49472.024909] names, then host name confusion attack is possible. Apr 26 05:48:41 192.168.122.209 [49472.139705] [tempesta fw] Configuration processing is completed. Apr 26 05:48:41 192.168.122.209 [49472.207885] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:48:42 192.168.122.209 [49472.614356] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:48:42 192.168.122.209 [49472.671066] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:48:42 192.168.122.209 [49472.698568] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:48:42 192.168.122.209 [49472.739643] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:48:42 192.168.122.209 [49472.740895] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:48:42 192.168.122.209 [49472.783608] [tempesta fw] Tempesta FW is ready Apr 26 05:48:42 192.168.122.209 [49473.363036] [tdb] Close table 'client0.tdb' Apr 26 05:48:43 192.168.122.209 [49473.549642] [tdb] Close table 'sessions0.tdb' Apr 26 05:48:46 192.168.122.209 [49476.846095] [tdb] Close table 'cache0.tdb' Apr 26 05:48:46 192.168.122.209 [49477.105134] [tdb] Close table 'filter0.tdb' Apr 26 05:48:46 192.168.122.209 [49477.105568] [tempesta fw] modules are stopped Apr 26 05:48:46 192.168.122.209 [49477.296420] [tempesta fw] exiting... Apr 26 05:48:47 192.168.122.209 [49477.452969] [tdb] Shutdown Tempesta DB Apr 26 05:48:47 192.168.122.209 [49477.646813] End test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_add_header_from_dynamic_table Apr 26 05:48:47 192.168.122.209 [49477.658588] Start test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_add_header_from_static_table Apr 26 05:48:48 192.168.122.209 [49478.731400] [tdb] Start Tempesta DB Apr 26 05:48:48 192.168.122.209 [49478.875675] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:48:49 192.168.122.209 [49480.269028] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49480.269028] Maybe that's fine, but it's worth checking the [49480.269028] config - if there is no relations between the [49480.269028] names, then host name confusion attack is possible. Apr 26 05:48:49 192.168.122.209 [49480.367818] [tempesta fw] Configuration processing is completed. Apr 26 05:48:49 192.168.122.209 [49480.425969] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:48:50 192.168.122.209 [49480.856723] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:48:50 192.168.122.209 [49480.891393] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:48:50 192.168.122.209 [49480.917156] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:48:50 192.168.122.209 [49480.963773] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:48:50 192.168.122.209 [49480.965195] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:48:50 192.168.122.209 [49481.003766] [tempesta fw] Tempesta FW is ready Apr 26 05:48:51 192.168.122.209 [49481.550605] [tdb] Close table 'client0.tdb' Apr 26 05:48:51 192.168.122.209 [49481.737948] [tdb] Close table 'sessions0.tdb' Apr 26 05:48:54 192.168.122.209 [49484.973377] [tdb] Close table 'cache0.tdb' Apr 26 05:48:54 192.168.122.209 [49485.219403] [tdb] Close table 'filter0.tdb' Apr 26 05:48:54 192.168.122.209 [49485.219866] [tempesta fw] modules are stopped Apr 26 05:48:55 192.168.122.209 [49485.449822] [tempesta fw] exiting... Apr 26 05:48:55 192.168.122.209 [49485.622020] [tdb] Shutdown Tempesta DB Apr 26 05:48:55 192.168.122.209 [49485.848935] End test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_add_header_from_static_table Apr 26 05:48:55 192.168.122.209 [49485.870435] Start test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_add_non_exist_header Apr 26 05:48:56 192.168.122.209 [49486.940180] [tdb] Start Tempesta DB Apr 26 05:48:56 192.168.122.209 [49487.067858] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:48:58 192.168.122.209 [49488.500835] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49488.500835] Maybe that's fine, but it's worth checking the [49488.500835] config - if there is no relations between the [49488.500835] names, then host name confusion attack is possible. Apr 26 05:48:58 192.168.122.209 [49488.595924] [tempesta fw] Configuration processing is completed. Apr 26 05:48:58 192.168.122.209 [49488.649340] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:48:58 192.168.122.209 [49489.062246] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:48:58 192.168.122.209 [49489.089010] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:48:58 192.168.122.209 [49489.115190] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:48:58 192.168.122.209 [49489.183903] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:48:58 192.168.122.209 [49489.185683] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:48:58 192.168.122.209 [49489.227775] [tempesta fw] Tempesta FW is ready Apr 26 05:48:59 192.168.122.209 [49489.773981] [tdb] Close table 'client0.tdb' Apr 26 05:48:59 192.168.122.209 [49489.958500] [tdb] Close table 'sessions0.tdb' Apr 26 05:49:02 192.168.122.209 [49493.236874] [tdb] Close table 'cache0.tdb' Apr 26 05:49:03 192.168.122.209 [49493.525018] [tdb] Close table 'filter0.tdb' Apr 26 05:49:03 192.168.122.209 [49493.525673] [tempesta fw] modules are stopped Apr 26 05:49:03 192.168.122.209 [49493.728850] [tempesta fw] exiting... Apr 26 05:49:03 192.168.122.209 [49493.849852] [tdb] Shutdown Tempesta DB Apr 26 05:49:03 192.168.122.209 [49494.068131] End test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_add_non_exist_header Apr 26 05:49:03 192.168.122.209 [49494.098153] Start test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_delete_headers Apr 26 05:49:04 192.168.122.209 [49495.155999] [tdb] Start Tempesta DB Apr 26 05:49:04 192.168.122.209 [49495.295585] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:49:06 192.168.122.209 [49496.745303] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49496.745303] Maybe that's fine, but it's worth checking the [49496.745303] config - if there is no relations between the [49496.745303] names, then host name confusion attack is possible. Apr 26 05:49:06 192.168.122.209 [49496.856031] [tempesta fw] Configuration processing is completed. Apr 26 05:49:06 192.168.122.209 [49496.909639] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:49:06 192.168.122.209 [49497.321779] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:49:06 192.168.122.209 [49497.393529] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:49:06 192.168.122.209 [49497.418919] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:49:07 192.168.122.209 [49497.475978] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:49:07 192.168.122.209 [49497.477714] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:49:07 192.168.122.209 [49497.523929] [tempesta fw] Tempesta FW is ready Apr 26 05:49:07 192.168.122.209 [49498.118978] [tdb] Close table 'client0.tdb' Apr 26 05:49:07 192.168.122.209 [49498.294667] [tdb] Close table 'sessions0.tdb' Apr 26 05:49:11 192.168.122.209 [49501.508623] [tdb] Close table 'cache0.tdb' Apr 26 05:49:11 192.168.122.209 [49501.748703] [tdb] Close table 'filter0.tdb' Apr 26 05:49:11 192.168.122.209 [49501.749150] [tempesta fw] modules are stopped Apr 26 05:49:11 192.168.122.209 [49501.929147] [tempesta fw] exiting... Apr 26 05:49:11 192.168.122.209 [49502.025312] [tdb] Shutdown Tempesta DB Apr 26 05:49:11 192.168.122.209 [49502.251251] End test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_delete_headers Apr 26 05:49:11 192.168.122.209 [49502.260451] Start test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_delete_many_headers Apr 26 05:49:12 192.168.122.209 [49503.366195] [tdb] Start Tempesta DB Apr 26 05:49:13 192.168.122.209 [49503.498387] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:49:14 192.168.122.209 [49504.829357] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49504.829357] Maybe that's fine, but it's worth checking the [49504.829357] config - if there is no relations between the [49504.829357] names, then host name confusion attack is possible. Apr 26 05:49:14 192.168.122.209 [49504.936105] [tempesta fw] Configuration processing is completed. Apr 26 05:49:14 192.168.122.209 [49504.993430] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:49:15 192.168.122.209 [49505.433090] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:49:15 192.168.122.209 [49505.461790] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:49:15 192.168.122.209 [49505.489016] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:49:15 192.168.122.209 [49505.532039] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:49:15 192.168.122.209 [49505.533233] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:49:15 192.168.122.209 [49505.575973] [tempesta fw] Tempesta FW is ready Apr 26 05:49:15 192.168.122.209 [49506.123805] [tdb] Close table 'client0.tdb' Apr 26 05:49:15 192.168.122.209 [49506.314352] [tdb] Close table 'sessions0.tdb' Apr 26 05:49:19 192.168.122.209 [49509.533444] [tdb] Close table 'cache0.tdb' Apr 26 05:49:19 192.168.122.209 [49509.786245] [tdb] Close table 'filter0.tdb' Apr 26 05:49:19 192.168.122.209 [49509.786681] [tempesta fw] modules are stopped Apr 26 05:49:19 192.168.122.209 [49509.983566] [tempesta fw] exiting... Apr 26 05:49:19 192.168.122.209 [49510.125595] [tdb] Shutdown Tempesta DB Apr 26 05:49:19 192.168.122.209 [49510.346203] End test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_delete_many_headers Apr 26 05:49:19 192.168.122.209 [49510.360226] Start test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_delete_many_special_headers Apr 26 05:49:21 192.168.122.209 [49511.475275] [tdb] Start Tempesta DB Apr 26 05:49:21 192.168.122.209 [49511.618143] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:49:22 192.168.122.209 [49513.001553] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49513.001553] Maybe that's fine, but it's worth checking the [49513.001553] config - if there is no relations between the [49513.001553] names, then host name confusion attack is possible. Apr 26 05:49:22 192.168.122.209 [49513.092222] [tempesta fw] Configuration processing is completed. Apr 26 05:49:22 192.168.122.209 [49513.148249] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:49:23 192.168.122.209 [49513.576637] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:49:23 192.168.122.209 [49513.636225] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:49:23 192.168.122.209 [49513.665248] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:49:23 192.168.122.209 [49513.704114] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:49:23 192.168.122.209 [49513.704992] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:49:23 192.168.122.209 [49513.744135] [tempesta fw] Tempesta FW is ready Apr 26 05:49:23 192.168.122.209 [49514.296087] [tdb] Close table 'client0.tdb' Apr 26 05:49:24 192.168.122.209 [49514.498197] [tdb] Close table 'sessions0.tdb' Apr 26 05:49:27 192.168.122.209 [49517.770022] [tdb] Close table 'cache0.tdb' Apr 26 05:49:27 192.168.122.209 [49518.015578] [tdb] Close table 'filter0.tdb' Apr 26 05:49:27 192.168.122.209 [49518.016005] [tempesta fw] modules are stopped Apr 26 05:49:27 192.168.122.209 [49518.208484] [tempesta fw] exiting... Apr 26 05:49:27 192.168.122.209 [49518.351951] [tdb] Shutdown Tempesta DB Apr 26 05:49:28 192.168.122.209 [49518.526395] End test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_delete_many_special_headers Apr 26 05:49:28 192.168.122.209 [49518.552236] Start test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_delete_non_exist_header Apr 26 05:49:29 192.168.122.209 [49519.622204] [tdb] Start Tempesta DB Apr 26 05:49:29 192.168.122.209 [49519.756966] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:49:30 192.168.122.209 [49521.149243] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49521.149243] Maybe that's fine, but it's worth checking the [49521.149243] config - if there is no relations between the [49521.149243] names, then host name confusion attack is possible. Apr 26 05:49:30 192.168.122.209 [49521.252312] [tempesta fw] Configuration processing is completed. Apr 26 05:49:30 192.168.122.209 [49521.302602] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:49:31 192.168.122.209 [49521.754609] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:49:31 192.168.122.209 [49521.790415] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:49:31 192.168.122.209 [49521.818433] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:49:31 192.168.122.209 [49521.864250] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:49:31 192.168.122.209 [49521.865417] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:49:31 192.168.122.209 [49521.908174] [tempesta fw] Tempesta FW is ready Apr 26 05:49:32 192.168.122.209 [49522.506895] [tdb] Close table 'client0.tdb' Apr 26 05:49:32 192.168.122.209 [49522.693485] [tdb] Close table 'sessions0.tdb' Apr 26 05:49:35 192.168.122.209 [49526.024592] [tdb] Close table 'cache0.tdb' Apr 26 05:49:35 192.168.122.209 [49526.242706] [tdb] Close table 'filter0.tdb' Apr 26 05:49:35 192.168.122.209 [49526.243150] [tempesta fw] modules are stopped Apr 26 05:49:36 192.168.122.209 [49526.445913] [tempesta fw] exiting... Apr 26 05:49:36 192.168.122.209 [49526.586864] [tdb] Shutdown Tempesta DB Apr 26 05:49:36 192.168.122.209 [49526.795261] End test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_delete_non_exist_header Apr 26 05:49:36 192.168.122.209 [49526.805434] Start test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_delete_special_headers Apr 26 05:49:37 192.168.122.209 [49527.906685] [tdb] Start Tempesta DB Apr 26 05:49:37 192.168.122.209 [49528.041276] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:49:39 192.168.122.209 [49529.489659] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49529.489659] Maybe that's fine, but it's worth checking the [49529.489659] config - if there is no relations between the [49529.489659] names, then host name confusion attack is possible. Apr 26 05:49:39 192.168.122.209 [49529.600419] [tempesta fw] Configuration processing is completed. Apr 26 05:49:39 192.168.122.209 [49529.651427] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:49:39 192.168.122.209 [49530.068461] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:49:39 192.168.122.209 [49530.127582] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:49:39 192.168.122.209 [49530.155324] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:49:39 192.168.122.209 [49530.204417] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:49:39 192.168.122.209 [49530.206233] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:49:39 192.168.122.209 [49530.248373] [tempesta fw] Tempesta FW is ready Apr 26 05:49:40 192.168.122.209 [49530.818708] [tdb] Close table 'client0.tdb' Apr 26 05:49:40 192.168.122.209 [49531.018311] [tdb] Close table 'sessions0.tdb' Apr 26 05:49:43 192.168.122.209 [49534.249982] [tdb] Close table 'cache0.tdb' Apr 26 05:49:44 192.168.122.209 [49534.473247] [tdb] Close table 'filter0.tdb' Apr 26 05:49:44 192.168.122.209 [49534.473729] [tempesta fw] modules are stopped Apr 26 05:49:44 192.168.122.209 [49534.681429] [tempesta fw] exiting... Apr 26 05:49:44 192.168.122.209 [49534.817056] [tdb] Shutdown Tempesta DB Apr 26 05:49:44 192.168.122.209 [49535.083574] End test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_delete_special_headers Apr 26 05:49:44 192.168.122.209 [49535.095917] Start test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_long_header_name Apr 26 05:49:45 192.168.122.209 [49536.111362] [tdb] Start Tempesta DB Apr 26 05:49:45 192.168.122.209 [49536.268797] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:49:47 192.168.122.209 [49537.589786] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49537.589786] Maybe that's fine, but it's worth checking the [49537.589786] config - if there is no relations between the [49537.589786] names, then host name confusion attack is possible. Apr 26 05:49:47 192.168.122.209 [49537.692526] [tempesta fw] Configuration processing is completed. Apr 26 05:49:47 192.168.122.209 [49537.742391] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:49:47 192.168.122.209 [49538.202168] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:49:47 192.168.122.209 [49538.235195] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:49:47 192.168.122.209 [49538.268011] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:49:47 192.168.122.209 [49538.316497] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:49:47 192.168.122.209 [49538.318220] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:49:47 192.168.122.209 [49538.356458] [tempesta fw] Tempesta FW is ready Apr 26 05:49:48 192.168.122.209 [49538.963113] [tdb] Close table 'client0.tdb' Apr 26 05:49:48 192.168.122.209 [49539.151538] [tdb] Close table 'sessions0.tdb' Apr 26 05:49:52 192.168.122.209 [49542.452725] [tdb] Close table 'cache0.tdb' Apr 26 05:49:52 192.168.122.209 [49542.708919] [tdb] Close table 'filter0.tdb' Apr 26 05:49:52 192.168.122.209 [49542.709374] [tempesta fw] modules are stopped Apr 26 05:49:52 192.168.122.209 [49542.941043] [tempesta fw] exiting... Apr 26 05:49:52 192.168.122.209 [49543.056618] [tdb] Shutdown Tempesta DB Apr 26 05:49:52 192.168.122.209 [49543.251295] End test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_long_header_name Apr 26 05:49:52 192.168.122.209 [49543.264190] Start test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_set_exist_header Apr 26 05:49:53 192.168.122.209 [49544.275777] [tdb] Start Tempesta DB Apr 26 05:49:53 192.168.122.209 [49544.410986] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:49:55 192.168.122.209 [49545.789495] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49545.789495] Maybe that's fine, but it's worth checking the [49545.789495] config - if there is no relations between the [49545.789495] names, then host name confusion attack is possible. Apr 26 05:49:55 192.168.122.209 [49545.896631] [tempesta fw] Configuration processing is completed. Apr 26 05:49:55 192.168.122.209 [49545.949461] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:49:55 192.168.122.209 [49546.365014] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:49:55 192.168.122.209 [49546.391587] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:49:55 192.168.122.209 [49546.418573] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:49:56 192.168.122.209 [49546.456629] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:49:56 192.168.122.209 [49546.458004] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:49:56 192.168.122.209 [49546.496555] [tempesta fw] Tempesta FW is ready Apr 26 05:49:56 192.168.122.209 [49547.086538] [tdb] Close table 'client0.tdb' Apr 26 05:49:56 192.168.122.209 [49547.290997] [tdb] Close table 'sessions0.tdb' Apr 26 05:50:00 192.168.122.209 [49550.574617] [tdb] Close table 'cache0.tdb' Apr 26 05:50:00 192.168.122.209 [49550.830175] [tdb] Close table 'filter0.tdb' Apr 26 05:50:00 192.168.122.209 [49550.830631] [tempesta fw] modules are stopped Apr 26 05:50:00 192.168.122.209 [49551.021466] [tempesta fw] exiting... Apr 26 05:50:00 192.168.122.209 [49551.182118] [tdb] Shutdown Tempesta DB Apr 26 05:50:00 192.168.122.209 [49551.402678] End test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_set_exist_header Apr 26 05:50:00 192.168.122.209 [49551.412582] Start test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_set_exist_special_header Apr 26 05:50:02 192.168.122.209 [49552.441028] [tdb] Start Tempesta DB Apr 26 05:50:02 192.168.122.209 [49552.578679] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:50:03 192.168.122.209 [49553.990007] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49553.990007] Maybe that's fine, but it's worth checking the [49553.990007] config - if there is no relations between the [49553.990007] names, then host name confusion attack is possible. Apr 26 05:50:03 192.168.122.209 [49554.092862] [tempesta fw] Configuration processing is completed. Apr 26 05:50:03 192.168.122.209 [49554.152319] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:50:04 192.168.122.209 [49554.567161] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:50:04 192.168.122.209 [49554.626068] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:50:04 192.168.122.209 [49554.654093] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:50:04 192.168.122.209 [49554.712700] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:50:04 192.168.122.209 [49554.714497] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:50:04 192.168.122.209 [49554.752653] [tempesta fw] Tempesta FW is ready Apr 26 05:50:04 192.168.122.209 [49555.346221] [tdb] Close table 'client0.tdb' Apr 26 05:50:05 192.168.122.209 [49555.532096] [tdb] Close table 'sessions0.tdb' Apr 26 05:50:08 192.168.122.209 [49558.751118] [tdb] Close table 'cache0.tdb' Apr 26 05:50:08 192.168.122.209 [49558.996909] [tdb] Close table 'filter0.tdb' Apr 26 05:50:08 192.168.122.209 [49558.997378] [tempesta fw] modules are stopped Apr 26 05:50:08 192.168.122.209 [49559.201409] [tempesta fw] exiting... Apr 26 05:50:08 192.168.122.209 [49559.334677] [tdb] Shutdown Tempesta DB Apr 26 05:50:09 192.168.122.209 [49559.534365] End test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_set_exist_special_header Apr 26 05:50:09 192.168.122.209 [49559.548372] Start test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_set_header_name_greater_than_1024 Apr 26 05:50:10 192.168.122.209 [49560.626406] [tdb] Start Tempesta DB Apr 26 05:50:10 192.168.122.209 [49560.762804] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:50:11 192.168.122.209 [49562.225934] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49562.225934] Maybe that's fine, but it's worth checking the [49562.225934] config - if there is no relations between the [49562.225934] names, then host name confusion attack is possible. Apr 26 05:50:11 192.168.122.209 [49562.324827] [tempesta fw] Configuration processing is completed. Apr 26 05:50:11 192.168.122.209 [49562.385108] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:50:12 192.168.122.209 [49562.805302] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:50:12 192.168.122.209 [49562.831362] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:50:12 192.168.122.209 [49562.857592] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:50:12 192.168.122.209 [49562.900796] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:50:12 192.168.122.209 [49562.902534] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:50:12 192.168.122.209 [49562.944699] [tempesta fw] Tempesta FW is ready Apr 26 05:50:13 192.168.122.209 [49563.485676] [tdb] Close table 'client0.tdb' Apr 26 05:50:13 192.168.122.209 [49563.675146] [tdb] Close table 'sessions0.tdb' Apr 26 05:50:16 192.168.122.209 [49566.870563] [tdb] Close table 'cache0.tdb' Apr 26 05:50:16 192.168.122.209 [49567.101512] [tdb] Close table 'filter0.tdb' Apr 26 05:50:16 192.168.122.209 [49567.101949] [tempesta fw] modules are stopped Apr 26 05:50:16 192.168.122.209 [49567.292832] [tempesta fw] exiting... Apr 26 05:50:16 192.168.122.209 [49567.417662] [tdb] Shutdown Tempesta DB Apr 26 05:50:17 192.168.122.209 [49567.634982] End test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_set_header_name_greater_than_1024 Apr 26 05:50:17 192.168.122.209 [49567.646474] Start test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_set_large_header Apr 26 05:50:18 192.168.122.209 [49568.715631] [tdb] Start Tempesta DB Apr 26 05:50:18 192.168.122.209 [49568.842585] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:50:19 192.168.122.209 [49570.214161] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49570.214161] Maybe that's fine, but it's worth checking the [49570.214161] config - if there is no relations between the [49570.214161] names, then host name confusion attack is possible. Apr 26 05:50:19 192.168.122.209 [49570.320954] [tempesta fw] Configuration processing is completed. Apr 26 05:50:19 192.168.122.209 [49570.373702] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:50:20 192.168.122.209 [49570.786979] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:50:20 192.168.122.209 [49570.822931] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:50:20 192.168.122.209 [49570.849244] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:50:20 192.168.122.209 [49570.900794] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:50:20 192.168.122.209 [49570.901849] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:50:20 192.168.122.209 [49570.940850] [tempesta fw] Tempesta FW is ready Apr 26 05:50:21 192.168.122.209 [49571.509249] [tdb] Close table 'client0.tdb' Apr 26 05:50:21 192.168.122.209 [49571.701902] [tdb] Close table 'sessions0.tdb' Apr 26 05:50:24 192.168.122.209 [49574.895056] [tdb] Close table 'cache0.tdb' Apr 26 05:50:24 192.168.122.209 [49575.113893] [tdb] Close table 'filter0.tdb' Apr 26 05:50:24 192.168.122.209 [49575.114331] [tempesta fw] modules are stopped Apr 26 05:50:24 192.168.122.209 [49575.297292] [tempesta fw] exiting... Apr 26 05:50:25 192.168.122.209 [49575.442171] [tdb] Shutdown Tempesta DB Apr 26 05:50:25 192.168.122.209 [49575.680799] End test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_set_large_header Apr 26 05:50:25 192.168.122.209 [49575.694669] Start test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_set_long_header_name Apr 26 05:50:26 192.168.122.209 [49576.831527] [tdb] Start Tempesta DB Apr 26 05:50:26 192.168.122.209 [49576.966871] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:50:27 192.168.122.209 [49578.397590] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49578.397590] Maybe that's fine, but it's worth checking the [49578.397590] config - if there is no relations between the [49578.397590] names, then host name confusion attack is possible. Apr 26 05:50:28 192.168.122.209 [49578.553092] [tempesta fw] Configuration processing is completed. Apr 26 05:50:28 192.168.122.209 [49578.607477] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:50:28 192.168.122.209 [49579.024003] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:50:28 192.168.122.209 [49579.083080] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:50:28 192.168.122.209 [49579.109422] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:50:28 192.168.122.209 [49579.165012] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:50:28 192.168.122.209 [49579.166784] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:50:28 192.168.122.209 [49579.212987] [tempesta fw] Tempesta FW is ready Apr 26 05:50:29 192.168.122.209 [49579.826832] [tdb] Close table 'client0.tdb' Apr 26 05:50:29 192.168.122.209 [49580.014393] [tdb] Close table 'sessions0.tdb' Apr 26 05:50:32 192.168.122.209 [49583.212174] [tdb] Close table 'cache0.tdb' Apr 26 05:50:33 192.168.122.209 [49583.490531] [tdb] Close table 'filter0.tdb' Apr 26 05:50:33 192.168.122.209 [49583.490969] [tempesta fw] modules are stopped Apr 26 05:50:33 192.168.122.209 [49583.697694] [tempesta fw] exiting... Apr 26 05:50:33 192.168.122.209 [49583.829178] [tdb] Shutdown Tempesta DB Apr 26 05:50:33 192.168.122.209 [49584.035312] End test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_set_long_header_name Apr 26 05:50:33 192.168.122.209 [49584.051083] Start test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_set_non_exist_header Apr 26 05:50:34 192.168.122.209 [49585.135717] [tdb] Start Tempesta DB Apr 26 05:50:34 192.168.122.209 [49585.283785] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:50:36 192.168.122.209 [49586.638374] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49586.638374] Maybe that's fine, but it's worth checking the [49586.638374] config - if there is no relations between the [49586.638374] names, then host name confusion attack is possible. Apr 26 05:50:36 192.168.122.209 [49586.753068] [tempesta fw] Configuration processing is completed. Apr 26 05:50:36 192.168.122.209 [49586.802496] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:50:36 192.168.122.209 [49587.213197] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:50:36 192.168.122.209 [49587.238766] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:50:36 192.168.122.209 [49587.264309] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:50:36 192.168.122.209 [49587.309082] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:50:36 192.168.122.209 [49587.310485] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:50:36 192.168.122.209 [49587.349051] [tempesta fw] Tempesta FW is ready Apr 26 05:50:37 192.168.122.209 [49587.880216] [tdb] Close table 'client0.tdb' Apr 26 05:50:37 192.168.122.209 [49588.085390] [tdb] Close table 'sessions0.tdb' Apr 26 05:50:40 192.168.122.209 [49591.312576] [tdb] Close table 'cache0.tdb' Apr 26 05:50:41 192.168.122.209 [49591.558554] [tdb] Close table 'filter0.tdb' Apr 26 05:50:41 192.168.122.209 [49591.558996] [tempesta fw] modules are stopped Apr 26 05:50:41 192.168.122.209 [49591.747531] [tempesta fw] exiting... Apr 26 05:50:41 192.168.122.209 [49591.881671] [tdb] Shutdown Tempesta DB Apr 26 05:50:41 192.168.122.209 [49592.069462] End test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_set_non_exist_header Apr 26 05:50:41 192.168.122.209 [49592.090173] Start test: t_reconf.test_reconf_base.TestHttpTablesReconf.test_add_rule Apr 26 05:50:42 192.168.122.209 [49593.120090] [tdb] Start Tempesta DB Apr 26 05:50:42 192.168.122.209 [49593.260099] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:50:44 192.168.122.209 [49594.997286] [tempesta fw] Configuration processing is completed. Apr 26 05:50:44 192.168.122.209 [49595.056767] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:50:45 192.168.122.209 [49595.471483] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:50:45 192.168.122.209 [49595.532315] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:50:45 192.168.122.209 [49595.558514] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:50:45 192.168.122.209 [49595.621161] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:50:45 192.168.122.209 [49595.665179] [tempesta fw] Tempesta FW is ready Apr 26 05:50:45 192.168.122.209 [49596.404463] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:50:46 192.168.122.209 [49596.617217] [tempesta fw] Configuration processing is completed. Apr 26 05:50:46 192.168.122.209 [49597.001444] [tempesta fw] Tempesta FW is ready Apr 26 05:50:46 192.168.122.209 [49597.047601] [tempesta fw] Warning: request has been filtered out via http table: 127.0.0.2 Apr 26 05:50:47 192.168.122.209 [49597.573956] [tdb] Close table 'client0.tdb' Apr 26 05:50:47 192.168.122.209 [49597.758284] [tdb] Close table 'sessions0.tdb' Apr 26 05:50:50 192.168.122.209 [49600.928528] [tdb] Close table 'cache0.tdb' Apr 26 05:50:50 192.168.122.209 [49601.176353] [tdb] Close table 'filter0.tdb' Apr 26 05:50:50 192.168.122.209 [49601.176784] [tempesta fw] modules are stopped Apr 26 05:50:50 192.168.122.209 [49601.406724] [tempesta fw] exiting... Apr 26 05:50:51 192.168.122.209 [49601.542990] [tdb] Shutdown Tempesta DB Apr 26 05:50:51 192.168.122.209 [49601.739278] End test: t_reconf.test_reconf_base.TestHttpTablesReconf.test_add_rule Apr 26 05:50:51 192.168.122.209 [49601.765028] Start test: t_reconf.test_reconf_base.TestHttpTablesReconf.test_reconf_action Apr 26 05:50:52 192.168.122.209 [49602.822707] [tdb] Start Tempesta DB Apr 26 05:50:52 192.168.122.209 [49602.958706] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:50:54 192.168.122.209 [49604.637483] [tempesta fw] Configuration processing is completed. Apr 26 05:50:54 192.168.122.209 [49604.691444] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:50:54 192.168.122.209 [49605.112372] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:50:54 192.168.122.209 [49605.138279] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:50:54 192.168.122.209 [49605.164165] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:50:54 192.168.122.209 [49605.233373] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:50:54 192.168.122.209 [49605.277281] [tempesta fw] Tempesta FW is ready Apr 26 05:50:55 192.168.122.209 [49605.941949] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:50:55 192.168.122.209 [49606.169286] [tempesta fw] Configuration processing is completed. Apr 26 05:50:56 192.168.122.209 [49606.557560] [tempesta fw] Tempesta FW is ready Apr 26 05:50:56 192.168.122.209 [49606.620461] [tempesta fw] Warning: request has been filtered out via http table: 127.0.0.2 Apr 26 05:50:56 192.168.122.209 [49607.152909] [tdb] Close table 'client0.tdb' Apr 26 05:50:56 192.168.122.209 [49607.338282] [tdb] Close table 'sessions0.tdb' Apr 26 05:51:00 192.168.122.209 [49610.533161] [tdb] Close table 'cache0.tdb' Apr 26 05:51:00 192.168.122.209 [49610.805594] [tdb] Close table 'filter0.tdb' Apr 26 05:51:00 192.168.122.209 [49610.806033] [tempesta fw] modules are stopped Apr 26 05:51:00 192.168.122.209 [49611.013864] [tempesta fw] exiting... Apr 26 05:51:00 192.168.122.209 [49611.158142] [tdb] Shutdown Tempesta DB Apr 26 05:51:00 192.168.122.209 [49611.381423] End test: t_reconf.test_reconf_base.TestHttpTablesReconf.test_reconf_action Apr 26 05:51:00 192.168.122.209 [49611.408661] Start test: t_reconf.test_reconf_base.TestHttpTablesReconf.test_reconf_condition Apr 26 05:51:01 192.168.122.209 [49612.430554] [tdb] Start Tempesta DB Apr 26 05:51:02 192.168.122.209 [49612.580181] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:51:03 192.168.122.209 [49614.317520] [tempesta fw] Configuration processing is completed. Apr 26 05:51:03 192.168.122.209 [49614.367749] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:51:04 192.168.122.209 [49614.774520] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:51:04 192.168.122.209 [49614.844808] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:51:04 192.168.122.209 [49614.870328] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:51:04 192.168.122.209 [49614.937429] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:51:04 192.168.122.209 [49615.001409] [tempesta fw] Tempesta FW is ready Apr 26 05:51:05 192.168.122.209 [49615.644796] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:51:05 192.168.122.209 [49615.881508] [tempesta fw] Configuration processing is completed. Apr 26 05:51:05 192.168.122.209 [49616.305662] [tempesta fw] Tempesta FW is ready Apr 26 05:51:06 192.168.122.209 [49616.911321] [tdb] Close table 'client0.tdb' Apr 26 05:51:06 192.168.122.209 [49617.099803] [tdb] Close table 'sessions0.tdb' Apr 26 05:51:09 192.168.122.209 [49620.276783] [tdb] Close table 'cache0.tdb' Apr 26 05:51:10 192.168.122.209 [49620.516140] [tdb] Close table 'filter0.tdb' Apr 26 05:51:10 192.168.122.209 [49620.516570] [tempesta fw] modules are stopped Apr 26 05:51:10 192.168.122.209 [49620.864758] [tempesta fw] exiting... Apr 26 05:51:10 192.168.122.209 [49621.004079] [tdb] Shutdown Tempesta DB Apr 26 05:51:10 192.168.122.209 [49621.218539] End test: t_reconf.test_reconf_base.TestHttpTablesReconf.test_reconf_condition Apr 26 05:51:10 192.168.122.209 [49621.229371] Start test: t_reconf.test_reconf_base.TestHttpTablesReconf.test_reconf_field_arg Apr 26 05:51:11 192.168.122.209 [49622.312412] [tdb] Start Tempesta DB Apr 26 05:51:12 192.168.122.209 [49622.468264] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:51:13 192.168.122.209 [49624.129634] [tempesta fw] Configuration processing is completed. Apr 26 05:51:13 192.168.122.209 [49624.188315] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:51:14 192.168.122.209 [49624.624232] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:51:14 192.168.122.209 [49624.650381] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:51:14 192.168.122.209 [49624.676502] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:51:14 192.168.122.209 [49624.769575] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:51:14 192.168.122.209 [49624.809541] [tempesta fw] Tempesta FW is ready Apr 26 05:51:15 192.168.122.209 [49625.492738] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:51:15 192.168.122.209 [49625.685525] [tempesta fw] Configuration processing is completed. Apr 26 05:51:15 192.168.122.209 [49626.057719] [tempesta fw] Tempesta FW is ready Apr 26 05:51:16 192.168.122.209 [49626.640585] [tdb] Close table 'client0.tdb' Apr 26 05:51:16 192.168.122.209 [49626.824072] [tdb] Close table 'sessions0.tdb' Apr 26 05:51:19 192.168.122.209 [49630.008571] [tdb] Close table 'cache0.tdb' Apr 26 05:51:19 192.168.122.209 [49630.235037] [tdb] Close table 'filter0.tdb' Apr 26 05:51:19 192.168.122.209 [49630.235479] [tempesta fw] modules are stopped Apr 26 05:51:20 192.168.122.209 [49630.465725] [tempesta fw] exiting... Apr 26 05:51:20 192.168.122.209 [49630.587409] [tdb] Shutdown Tempesta DB Apr 26 05:51:20 192.168.122.209 [49630.813268] End test: t_reconf.test_reconf_base.TestHttpTablesReconf.test_reconf_field_arg Apr 26 05:51:20 192.168.122.209 [49630.830068] Start test: t_reconf.test_reconf_base.TestHttpTablesReconf.test_reconf_field_name Apr 26 05:51:21 192.168.122.209 [49631.920327] [tdb] Start Tempesta DB Apr 26 05:51:21 192.168.122.209 [49632.057638] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:51:23 192.168.122.209 [49633.825673] [tempesta fw] Configuration processing is completed. Apr 26 05:51:23 192.168.122.209 [49633.881292] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:51:23 192.168.122.209 [49634.315123] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:51:23 192.168.122.209 [49634.340894] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:51:23 192.168.122.209 [49634.366911] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:51:24 192.168.122.209 [49634.445696] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:51:24 192.168.122.209 [49634.497645] [tempesta fw] Tempesta FW is ready Apr 26 05:51:24 192.168.122.209 [49635.171163] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:51:24 192.168.122.209 [49635.381657] [tempesta fw] Configuration processing is completed. Apr 26 05:51:25 192.168.122.209 [49635.765871] [tempesta fw] Tempesta FW is ready Apr 26 05:51:25 192.168.122.209 [49636.339870] [tdb] Close table 'client0.tdb' Apr 26 05:51:26 192.168.122.209 [49636.529614] [tdb] Close table 'sessions0.tdb' Apr 26 05:51:29 192.168.122.209 [49639.714242] [tdb] Close table 'cache0.tdb' Apr 26 05:51:29 192.168.122.209 [49639.950257] [tdb] Close table 'filter0.tdb' Apr 26 05:51:29 192.168.122.209 [49639.950703] [tempesta fw] modules are stopped Apr 26 05:51:29 192.168.122.209 [49640.160229] [tempesta fw] exiting... Apr 26 05:51:29 192.168.122.209 [49640.267377] [tdb] Shutdown Tempesta DB Apr 26 05:51:30 192.168.122.209 [49640.467020] End test: t_reconf.test_reconf_base.TestHttpTablesReconf.test_reconf_field_name Apr 26 05:51:30 192.168.122.209 [49640.493818] Start test: t_reconf.test_reconf_base.TestHttpTablesReconf.test_reconf_val Apr 26 05:51:31 192.168.122.209 [49641.590332] [tdb] Start Tempesta DB Apr 26 05:51:31 192.168.122.209 [49641.732088] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:51:32 192.168.122.209 [49643.381877] [tempesta fw] Configuration processing is completed. Apr 26 05:51:33 192.168.122.209 [49643.433656] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:51:33 192.168.122.209 [49643.851488] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:51:33 192.168.122.209 [49643.878272] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:51:33 192.168.122.209 [49643.906029] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:51:33 192.168.122.209 [49643.989894] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:51:33 192.168.122.209 [49644.029767] [tempesta fw] Tempesta FW is ready Apr 26 05:51:34 192.168.122.209 [49644.631875] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:51:34 192.168.122.209 [49644.869841] [tempesta fw] Configuration processing is completed. Apr 26 05:51:34 192.168.122.209 [49645.249987] [tempesta fw] Tempesta FW is ready Apr 26 05:51:35 192.168.122.209 [49645.806509] [tdb] Close table 'client0.tdb' Apr 26 05:51:35 192.168.122.209 [49645.989260] [tdb] Close table 'sessions0.tdb' Apr 26 05:51:38 192.168.122.209 [49649.223467] [tdb] Close table 'cache0.tdb' Apr 26 05:51:39 192.168.122.209 [49649.465894] [tdb] Close table 'filter0.tdb' Apr 26 05:51:39 192.168.122.209 [49649.466329] [tempesta fw] modules are stopped Apr 26 05:51:39 192.168.122.209 [49649.708985] [tempesta fw] exiting... Apr 26 05:51:39 192.168.122.209 [49649.841572] [tdb] Shutdown Tempesta DB Apr 26 05:51:39 192.168.122.209 [49650.080171] End test: t_reconf.test_reconf_base.TestHttpTablesReconf.test_reconf_val Apr 26 05:51:39 192.168.122.209 [49650.091799] Start test: t_reconf.test_reconf_base.TestHttpTablesReconf.test_remove_rule Apr 26 05:51:40 192.168.122.209 [49651.157679] [tdb] Start Tempesta DB Apr 26 05:51:40 192.168.122.209 [49651.301672] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:51:42 192.168.122.209 [49652.993963] [tempesta fw] Configuration processing is completed. Apr 26 05:51:42 192.168.122.209 [49653.041503] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:51:43 192.168.122.209 [49653.454673] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:51:43 192.168.122.209 [49653.480737] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:51:43 192.168.122.209 [49653.506757] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:51:43 192.168.122.209 [49653.581892] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:51:43 192.168.122.209 [49653.621908] [tempesta fw] Tempesta FW is ready Apr 26 05:51:43 192.168.122.209 [49654.308161] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:51:44 192.168.122.209 [49654.497891] [tempesta fw] Configuration processing is completed. Apr 26 05:51:44 192.168.122.209 [49654.874110] [tempesta fw] Tempesta FW is ready Apr 26 05:51:45 192.168.122.209 [49655.469175] [tdb] Close table 'client0.tdb' Apr 26 05:51:45 192.168.122.209 [49655.652746] [tdb] Close table 'sessions0.tdb' Apr 26 05:51:48 192.168.122.209 [49658.899171] [tdb] Close table 'cache0.tdb' Apr 26 05:51:48 192.168.122.209 [49659.160192] [tdb] Close table 'filter0.tdb' Apr 26 05:51:48 192.168.122.209 [49659.160663] [tempesta fw] modules are stopped Apr 26 05:51:48 192.168.122.209 [49659.370870] [tempesta fw] exiting... Apr 26 05:51:49 192.168.122.209 [49659.521370] [tdb] Shutdown Tempesta DB Apr 26 05:51:49 192.168.122.209 [49659.757997] End test: t_reconf.test_reconf_base.TestHttpTablesReconf.test_remove_rule Apr 26 05:51:49 192.168.122.209 [49659.772009] Start test: t_reconf.test_reconf_base.TestListenCommonReconf.test_reconf_busy_socks Apr 26 05:51:50 192.168.122.209 [49660.871814] [tdb] Start Tempesta DB Apr 26 05:51:50 192.168.122.209 [49661.011589] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:51:51 192.168.122.209 [49662.239238] [tempesta fw] Configuration processing is completed. Apr 26 05:51:51 192.168.122.209 [49662.295594] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:51:52 192.168.122.209 [49662.728799] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:51:52 192.168.122.209 [49662.758048] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:51:52 192.168.122.209 [49662.787130] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:51:52 192.168.122.209 [49662.788246] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:51:52 192.168.122.209 [49662.802172] [tempesta fw] Tempesta FW is ready Apr 26 05:51:52 192.168.122.209 [49663.302923] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:51:52 192.168.122.209 [49663.366836] [tempesta fw] Configuration processing is completed. Apr 26 05:51:52 192.168.122.209 [49663.394388] [tempesta fw] Open listen socket on: 0.0.0.0:4433 Apr 26 05:51:52 192.168.122.209 [49663.396124] [tempesta fw] Open listen socket on: 0.0.0.0:8000 Apr 26 05:51:52 192.168.122.209 [49663.397774] [tempesta fw] ERROR: can't bind to: 0.0.0.0:8000 Apr 26 05:51:52 192.168.122.209 [49663.399901] [tempesta fw] ERROR: can't start listening on: 0.0.0.0:8000 Apr 26 05:51:52 192.168.122.209 [49663.401772] [tempesta fw] ERROR: Unable to start module 'sock_clnt': -98 Apr 26 05:51:53 192.168.122.209 [49663.597822] [tdb] Close table 'client0.tdb' Apr 26 05:51:53 192.168.122.209 [49663.776996] [tdb] Close table 'sessions0.tdb' Apr 26 05:51:56 192.168.122.209 [49667.007996] [tdb] Close table 'cache0.tdb' Apr 26 05:51:56 192.168.122.209 [49667.261785] [tdb] Close table 'filter0.tdb' Apr 26 05:51:56 192.168.122.209 [49667.262240] [tempesta fw] modules are stopped Apr 26 05:51:56 192.168.122.209 [49667.262626] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 05:51:57 192.168.122.209 [49667.498732] [tempesta fw] exiting... Apr 26 05:51:57 192.168.122.209 [49667.611494] [tdb] Shutdown Tempesta DB Apr 26 05:51:57 192.168.122.209 [49668.231187] End test: t_reconf.test_reconf_base.TestListenCommonReconf.test_reconf_busy_socks Apr 26 05:51:57 192.168.122.209 [49668.241484] Start test: t_reconf.test_reconf_base.TestListenCommonReconf.test_stop Apr 26 05:51:58 192.168.122.209 [49669.094307] [tdb] Start Tempesta DB Apr 26 05:51:58 192.168.122.209 [49669.233685] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:51:59 192.168.122.209 [49670.233379] [tempesta fw] Configuration processing is completed. Apr 26 05:51:59 192.168.122.209 [49670.296839] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:52:00 192.168.122.209 [49670.719163] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:52:00 192.168.122.209 [49670.776122] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:52:00 192.168.122.209 [49670.803387] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:52:00 192.168.122.209 [49670.804471] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:52:00 192.168.122.209 [49670.826171] [tempesta fw] Tempesta FW is ready Apr 26 05:52:00 192.168.122.209 [49671.154585] [tdb] Close table 'client0.tdb' Apr 26 05:52:00 192.168.122.209 [49671.329761] [tdb] Close table 'sessions0.tdb' Apr 26 05:52:04 192.168.122.209 [49674.625277] [tdb] Close table 'cache0.tdb' Apr 26 05:52:04 192.168.122.209 [49674.858153] [tdb] Close table 'filter0.tdb' Apr 26 05:52:04 192.168.122.209 [49674.858594] [tempesta fw] modules are stopped Apr 26 05:52:05 192.168.122.209 [49676.350251] [tempesta fw] Configuration processing is completed. Apr 26 05:52:05 192.168.122.209 [49676.406739] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:52:06 192.168.122.209 [49676.815287] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:52:06 192.168.122.209 [49676.841303] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:52:06 192.168.122.209 [49676.867397] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:52:06 192.168.122.209 [49676.868504] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:52:06 192.168.122.209 [49676.882137] [tempesta fw] Tempesta FW is ready Apr 26 05:52:06 192.168.122.209 [49677.293205] [tdb] Close table 'client0.tdb' Apr 26 05:52:07 192.168.122.209 [49677.478834] [tdb] Close table 'sessions0.tdb' Apr 26 05:52:10 192.168.122.209 [49680.663185] [tdb] Close table 'cache0.tdb' Apr 26 05:52:10 192.168.122.209 [49680.882669] [tdb] Close table 'filter0.tdb' Apr 26 05:52:10 192.168.122.209 [49680.883126] [tempesta fw] modules are stopped Apr 26 05:52:10 192.168.122.209 [49681.079146] [tempesta fw] exiting... Apr 26 05:52:10 192.168.122.209 [49681.209393] [tdb] Shutdown Tempesta DB Apr 26 05:52:11 192.168.122.209 [49681.436497] End test: t_reconf.test_reconf_base.TestListenCommonReconf.test_stop Apr 26 05:52:11 192.168.122.209 [49681.463988] Start test: t_reconf.test_reconf_base.TestListenReconfH2.test_reconf_add_listen Apr 26 05:52:12 192.168.122.209 [49682.533946] [tdb] Start Tempesta DB Apr 26 05:52:12 192.168.122.209 [49682.666223] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:52:13 192.168.122.209 [49683.898846] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49683.898846] Maybe that's fine, but it's worth checking the [49683.898846] config - if there is no relations between the [49683.898846] names, then host name confusion attack is possible. Apr 26 05:52:13 192.168.122.209 [49683.990405] [tempesta fw] Configuration processing is completed. Apr 26 05:52:13 192.168.122.209 [49684.041386] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:52:14 192.168.122.209 [49684.453507] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:52:14 192.168.122.209 [49684.479961] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:52:14 192.168.122.209 [49684.505934] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:52:14 192.168.122.209 [49684.546286] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:52:14 192.168.122.209 [49684.590297] [tempesta fw] Tempesta FW is ready Apr 26 05:52:14 192.168.122.209 [49685.064680] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:52:14 192.168.122.209 [49685.143603] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49685.143603] Maybe that's fine, but it's worth checking the [49685.143603] config - if there is no relations between the [49685.143603] names, then host name confusion attack is possible. Apr 26 05:52:14 192.168.122.209 [49685.270355] [tempesta fw] Configuration processing is completed. Apr 26 05:52:15 192.168.122.209 [49685.510351] [tempesta fw] Open listen socket on: 0.0.0.0:444 Apr 26 05:52:15 192.168.122.209 [49685.574743] [tempesta fw] Tempesta FW is ready Apr 26 05:52:15 192.168.122.209 [49686.076074] [tdb] Close table 'client0.tdb' Apr 26 05:52:15 192.168.122.209 [49686.265513] [tdb] Close table 'sessions0.tdb' Apr 26 05:52:19 192.168.122.209 [49689.456021] [tdb] Close table 'cache0.tdb' Apr 26 05:52:19 192.168.122.209 [49689.686667] [tdb] Close table 'filter0.tdb' Apr 26 05:52:19 192.168.122.209 [49689.687101] [tempesta fw] modules are stopped Apr 26 05:52:19 192.168.122.209 [49689.922733] [tempesta fw] exiting... Apr 26 05:52:19 192.168.122.209 [49690.075868] [tdb] Shutdown Tempesta DB Apr 26 05:52:19 192.168.122.209 [49690.284143] End test: t_reconf.test_reconf_base.TestListenReconfH2.test_reconf_add_listen Apr 26 05:52:19 192.168.122.209 [49690.296463] Start test: t_reconf.test_reconf_base.TestListenReconfH2.test_reconf_ip_default_to_ipv4_port_default Apr 26 05:52:20 192.168.122.209 [49691.374482] [tdb] Start Tempesta DB Apr 26 05:52:21 192.168.122.209 [49691.506491] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:52:22 192.168.122.209 [49692.735611] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49692.735611] Maybe that's fine, but it's worth checking the [49692.735611] config - if there is no relations between the [49692.735611] names, then host name confusion attack is possible. Apr 26 05:52:22 192.168.122.209 [49692.827520] [tempesta fw] Warning: TLS: no HTTPS listener set, configuration is ignored. Apr 26 05:52:22 192.168.122.209 [49692.846432] [tempesta fw] Configuration processing is completed. Apr 26 05:52:22 192.168.122.209 [49692.898028] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:52:22 192.168.122.209 [49693.307162] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:52:22 192.168.122.209 [49693.341619] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:52:22 192.168.122.209 [49693.376730] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:52:22 192.168.122.209 [49693.422357] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:52:23 192.168.122.209 [49693.462388] [tempesta fw] Tempesta FW is ready Apr 26 05:52:23 192.168.122.209 [49693.919186] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:52:23 192.168.122.209 [49693.967733] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49693.967733] Maybe that's fine, but it's worth checking the [49693.967733] config - if there is no relations between the [49693.967733] names, then host name confusion attack is possible. Apr 26 05:52:23 192.168.122.209 [49694.078519] [tempesta fw] Configuration processing is completed. Apr 26 05:52:23 192.168.122.209 [49694.258562] [tempesta fw] Open listen socket on: 127.0.0.1 Apr 26 05:52:23 192.168.122.209 [49694.314811] [tempesta fw] Tempesta FW is ready Apr 26 05:52:24 192.168.122.209 [49694.804043] [tdb] Close table 'client0.tdb' Apr 26 05:52:24 192.168.122.209 [49694.973428] [tdb] Close table 'sessions0.tdb' Apr 26 05:52:27 192.168.122.209 [49698.222705] [tdb] Close table 'cache0.tdb' Apr 26 05:52:28 192.168.122.209 [49698.473020] [tdb] Close table 'filter0.tdb' Apr 26 05:52:28 192.168.122.209 [49698.473451] [tempesta fw] modules are stopped Apr 26 05:52:28 192.168.122.209 [49698.715044] [tempesta fw] exiting... Apr 26 05:52:28 192.168.122.209 [49698.839562] [tdb] Shutdown Tempesta DB Apr 26 05:52:28 192.168.122.209 [49699.026767] End test: t_reconf.test_reconf_base.TestListenReconfH2.test_reconf_ip_default_to_ipv4_port_default Apr 26 05:52:28 192.168.122.209 [49699.036508] Start test: t_reconf.test_reconf_base.TestListenReconfH2.test_reconf_ip_ipv4_to_ipv4_port_443 Apr 26 05:52:29 192.168.122.209 [49700.117141] [tdb] Start Tempesta DB Apr 26 05:52:29 192.168.122.209 [49700.255522] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:52:31 192.168.122.209 [49701.535741] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49701.535741] Maybe that's fine, but it's worth checking the [49701.535741] config - if there is no relations between the [49701.535741] names, then host name confusion attack is possible. Apr 26 05:52:31 192.168.122.209 [49701.646834] [tempesta fw] Configuration processing is completed. Apr 26 05:52:31 192.168.122.209 [49701.701289] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:52:31 192.168.122.209 [49702.103982] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:52:31 192.168.122.209 [49702.161051] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:52:31 192.168.122.209 [49702.187639] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:52:31 192.168.122.209 [49702.226569] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 05:52:31 192.168.122.209 [49702.266511] [tempesta fw] Tempesta FW is ready Apr 26 05:52:32 192.168.122.209 [49702.709119] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:52:32 192.168.122.209 [49702.763791] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49702.763791] Maybe that's fine, but it's worth checking the [49702.763791] config - if there is no relations between the [49702.763791] names, then host name confusion attack is possible. Apr 26 05:52:32 192.168.122.209 [49702.906540] [tempesta fw] Configuration processing is completed. Apr 26 05:52:32 192.168.122.209 [49703.126704] [tempesta fw] Open listen socket on: 127.0.1.100:443 Apr 26 05:52:32 192.168.122.209 [49703.182907] [tempesta fw] Tempesta FW is ready Apr 26 05:52:33 192.168.122.209 [49703.689983] [tdb] Close table 'client0.tdb' Apr 26 05:52:33 192.168.122.209 [49703.884940] [tdb] Close table 'sessions0.tdb' Apr 26 05:52:36 192.168.122.209 [49707.068746] [tdb] Close table 'cache0.tdb' Apr 26 05:52:36 192.168.122.209 [49707.317533] [tdb] Close table 'filter0.tdb' Apr 26 05:52:36 192.168.122.209 [49707.317977] [tempesta fw] modules are stopped Apr 26 05:52:37 192.168.122.209 [49707.520305] [tempesta fw] exiting... Apr 26 05:52:37 192.168.122.209 [49707.646072] [tdb] Shutdown Tempesta DB Apr 26 05:52:37 192.168.122.209 [49707.846834] End test: t_reconf.test_reconf_base.TestListenReconfH2.test_reconf_ip_ipv4_to_ipv4_port_443 Apr 26 05:52:37 192.168.122.209 [49707.858806] Start test: t_reconf.test_reconf_base.TestListenReconfH2.test_reconf_ip_ipv4_to_ipv4_port_default Apr 26 05:52:38 192.168.122.209 [49708.965050] [tdb] Start Tempesta DB Apr 26 05:52:38 192.168.122.209 [49709.099665] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:52:40 192.168.122.209 [49710.435215] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49710.435215] Maybe that's fine, but it's worth checking the [49710.435215] config - if there is no relations between the [49710.435215] names, then host name confusion attack is possible. Apr 26 05:52:40 192.168.122.209 [49710.538729] [tempesta fw] Configuration processing is completed. Apr 26 05:52:40 192.168.122.209 [49710.590757] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:52:40 192.168.122.209 [49711.019368] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:52:40 192.168.122.209 [49711.053766] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:52:40 192.168.122.209 [49711.089062] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:52:40 192.168.122.209 [49711.162675] [tempesta fw] Open listen socket on: 127.0.0.1 Apr 26 05:52:40 192.168.122.209 [49711.202629] [tempesta fw] Tempesta FW is ready Apr 26 05:52:41 192.168.122.209 [49711.676443] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:52:41 192.168.122.209 [49711.719655] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49711.719655] Maybe that's fine, but it's worth checking the [49711.719655] config - if there is no relations between the [49711.719655] names, then host name confusion attack is possible. Apr 26 05:52:41 192.168.122.209 [49711.854818] [tempesta fw] Configuration processing is completed. Apr 26 05:52:41 192.168.122.209 [49712.095007] [tempesta fw] Open listen socket on: 127.0.1.100 Apr 26 05:52:41 192.168.122.209 [49712.167044] [tempesta fw] Tempesta FW is ready Apr 26 05:52:42 192.168.122.209 [49712.637595] [tdb] Close table 'client0.tdb' Apr 26 05:52:42 192.168.122.209 [49712.831311] [tdb] Close table 'sessions0.tdb' Apr 26 05:52:45 192.168.122.209 [49716.047101] [tdb] Close table 'cache0.tdb' Apr 26 05:52:45 192.168.122.209 [49716.315528] [tdb] Close table 'filter0.tdb' Apr 26 05:52:45 192.168.122.209 [49716.315963] [tempesta fw] modules are stopped Apr 26 05:52:46 192.168.122.209 [49716.493999] [tempesta fw] exiting... Apr 26 05:52:46 192.168.122.209 [49716.632426] [tdb] Shutdown Tempesta DB Apr 26 05:52:46 192.168.122.209 [49716.844370] End test: t_reconf.test_reconf_base.TestListenReconfH2.test_reconf_ip_ipv4_to_ipv4_port_default Apr 26 05:52:46 192.168.122.209 [49716.857145] Start test: t_reconf.test_reconf_base.TestListenReconfH2.test_reconf_port Apr 26 05:52:47 192.168.122.209 [49717.933261] [tdb] Start Tempesta DB Apr 26 05:52:47 192.168.122.209 [49718.071613] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:52:48 192.168.122.209 [49719.279720] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49719.279720] Maybe that's fine, but it's worth checking the [49719.279720] config - if there is no relations between the [49719.279720] names, then host name confusion attack is possible. Apr 26 05:52:48 192.168.122.209 [49719.386806] [tempesta fw] Configuration processing is completed. Apr 26 05:52:49 192.168.122.209 [49719.443148] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:52:49 192.168.122.209 [49719.855959] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:52:49 192.168.122.209 [49719.934166] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:52:49 192.168.122.209 [49719.960189] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:52:49 192.168.122.209 [49720.034795] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:52:49 192.168.122.209 [49720.074736] [tempesta fw] Tempesta FW is ready Apr 26 05:52:50 192.168.122.209 [49720.545614] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:52:50 192.168.122.209 [49720.596063] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49720.596063] Maybe that's fine, but it's worth checking the [49720.596063] config - if there is no relations between the [49720.596063] names, then host name confusion attack is possible. Apr 26 05:52:50 192.168.122.209 [49720.730810] [tempesta fw] Configuration processing is completed. Apr 26 05:52:50 192.168.122.209 [49720.958941] [tempesta fw] Open listen socket on: 0.0.0.0:4433 Apr 26 05:52:50 192.168.122.209 [49721.015131] [tempesta fw] Tempesta FW is ready Apr 26 05:52:51 192.168.122.209 [49721.520930] [tdb] Close table 'client0.tdb' Apr 26 05:52:51 192.168.122.209 [49721.730396] [tdb] Close table 'sessions0.tdb' Apr 26 05:52:54 192.168.122.209 [49724.936304] [tdb] Close table 'cache0.tdb' Apr 26 05:52:54 192.168.122.209 [49725.158604] [tdb] Close table 'filter0.tdb' Apr 26 05:52:54 192.168.122.209 [49725.159069] [tempesta fw] modules are stopped Apr 26 05:52:54 192.168.122.209 [49725.349222] [tempesta fw] exiting... Apr 26 05:52:55 192.168.122.209 [49725.473808] [tdb] Shutdown Tempesta DB Apr 26 05:52:55 192.168.122.209 [49725.674956] End test: t_reconf.test_reconf_base.TestListenReconfH2.test_reconf_port Apr 26 05:52:55 192.168.122.209 [49725.684609] Start test: t_reconf.test_reconf_base.TestListenReconfH2.test_reconf_proto_h2 Apr 26 05:52:56 192.168.122.209 [49726.791468] [tdb] Start Tempesta DB Apr 26 05:52:56 192.168.122.209 [49726.935796] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:52:57 192.168.122.209 [49728.203524] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49728.203524] Maybe that's fine, but it's worth checking the [49728.203524] config - if there is no relations between the [49728.203524] names, then host name confusion attack is possible. Apr 26 05:52:57 192.168.122.209 [49728.298935] [tempesta fw] Configuration processing is completed. Apr 26 05:52:57 192.168.122.209 [49728.366631] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:52:58 192.168.122.209 [49728.789383] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:52:58 192.168.122.209 [49728.829825] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:52:58 192.168.122.209 [49728.865039] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:52:58 192.168.122.209 [49728.918948] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:52:58 192.168.122.209 [49728.962838] [tempesta fw] Tempesta FW is ready Apr 26 05:52:58 192.168.122.209 [49729.413238] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:52:59 192.168.122.209 [49729.460262] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49729.460262] Maybe that's fine, but it's worth checking the [49729.460262] config - if there is no relations between the [49729.460262] names, then host name confusion attack is possible. Apr 26 05:52:59 192.168.122.209 [49729.579010] [tempesta fw] Configuration processing is completed. Apr 26 05:52:59 192.168.122.209 [49729.859375] [tempesta fw] Tempesta FW is ready Apr 26 05:52:59 192.168.122.209 [49730.326168] [tdb] Close table 'client0.tdb' Apr 26 05:53:00 192.168.122.209 [49730.530822] [tdb] Close table 'sessions0.tdb' Apr 26 05:53:03 192.168.122.209 [49733.807662] [tdb] Close table 'cache0.tdb' Apr 26 05:53:03 192.168.122.209 [49734.040872] [tdb] Close table 'filter0.tdb' Apr 26 05:53:03 192.168.122.209 [49734.041322] [tempesta fw] modules are stopped Apr 26 05:53:03 192.168.122.209 [49734.243064] [tempesta fw] exiting... Apr 26 05:53:03 192.168.122.209 [49734.365027] [tdb] Shutdown Tempesta DB Apr 26 05:53:04 192.168.122.209 [49734.560616] End test: t_reconf.test_reconf_base.TestListenReconfH2.test_reconf_proto_h2 Apr 26 05:53:04 192.168.122.209 [49734.578399] Start test: t_reconf.test_reconf_base.TestListenReconfH2.test_reconf_proto_h2_https Apr 26 05:53:05 192.168.122.209 [49735.694075] [tdb] Start Tempesta DB Apr 26 05:53:05 192.168.122.209 [49735.823514] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:53:06 192.168.122.209 [49737.059494] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49737.059494] Maybe that's fine, but it's worth checking the [49737.059494] config - if there is no relations between the [49737.059494] names, then host name confusion attack is possible. Apr 26 05:53:06 192.168.122.209 [49737.159098] [tempesta fw] Configuration processing is completed. Apr 26 05:53:06 192.168.122.209 [49737.211495] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:53:07 192.168.122.209 [49737.619347] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:53:07 192.168.122.209 [49737.676842] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:53:07 192.168.122.209 [49737.709416] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:53:07 192.168.122.209 [49737.763020] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:53:07 192.168.122.209 [49737.806958] [tempesta fw] Tempesta FW is ready Apr 26 05:53:07 192.168.122.209 [49738.249159] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:53:07 192.168.122.209 [49738.291480] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49738.291480] Maybe that's fine, but it's worth checking the [49738.291480] config - if there is no relations between the [49738.291480] names, then host name confusion attack is possible. Apr 26 05:53:07 192.168.122.209 [49738.371020] [tempesta fw] Configuration processing is completed. Apr 26 05:53:08 192.168.122.209 [49738.563194] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:53:08 192.168.122.209 [49738.619385] [tempesta fw] Tempesta FW is ready Apr 26 05:53:08 192.168.122.209 [49739.086225] [tdb] Close table 'client0.tdb' Apr 26 05:53:08 192.168.122.209 [49739.288525] [tdb] Close table 'sessions0.tdb' Apr 26 05:53:12 192.168.122.209 [49742.515323] [tdb] Close table 'cache0.tdb' Apr 26 05:53:12 192.168.122.209 [49742.758693] [tdb] Close table 'filter0.tdb' Apr 26 05:53:12 192.168.122.209 [49742.759529] [tempesta fw] modules are stopped Apr 26 05:53:12 192.168.122.209 [49742.983458] [tempesta fw] exiting... Apr 26 05:53:12 192.168.122.209 [49743.089955] [tdb] Shutdown Tempesta DB Apr 26 05:53:12 192.168.122.209 [49743.307120] End test: t_reconf.test_reconf_base.TestListenReconfH2.test_reconf_proto_h2_https Apr 26 05:53:12 192.168.122.209 [49743.318637] Start test: t_reconf.test_reconf_base.TestListenReconfH2.test_reconf_proto_http Apr 26 05:53:13 192.168.122.209 [49744.290632] [tdb] Start Tempesta DB Apr 26 05:53:13 192.168.122.209 [49744.431436] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:53:15 192.168.122.209 [49745.675587] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49745.675587] Maybe that's fine, but it's worth checking the [49745.675587] config - if there is no relations between the [49745.675587] names, then host name confusion attack is possible. Apr 26 05:53:15 192.168.122.209 [49745.771169] [tempesta fw] Configuration processing is completed. Apr 26 05:53:15 192.168.122.209 [49745.836841] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:53:15 192.168.122.209 [49746.263834] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:53:15 192.168.122.209 [49746.291852] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:53:15 192.168.122.209 [49746.326972] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:53:15 192.168.122.209 [49746.379119] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:53:15 192.168.122.209 [49746.423175] [tempesta fw] Tempesta FW is ready Apr 26 05:53:16 192.168.122.209 [49746.885174] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:53:16 192.168.122.209 [49746.936287] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49746.936287] Maybe that's fine, but it's worth checking the [49746.936287] config - if there is no relations between the [49746.936287] names, then host name confusion attack is possible. Apr 26 05:53:16 192.168.122.209 [49747.059079] [tempesta fw] Configuration processing is completed. Apr 26 05:53:16 192.168.122.209 [49747.259297] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:53:16 192.168.122.209 [49747.323439] [tempesta fw] Tempesta FW is ready Apr 26 05:53:17 192.168.122.209 [49747.832343] [tdb] Close table 'client0.tdb' Apr 26 05:53:17 192.168.122.209 [49748.020106] [tdb] Close table 'sessions0.tdb' Apr 26 05:53:20 192.168.122.209 [49751.212995] [tdb] Close table 'cache0.tdb' Apr 26 05:53:20 192.168.122.209 [49751.429497] [tdb] Close table 'filter0.tdb' Apr 26 05:53:20 192.168.122.209 [49751.429954] [tempesta fw] modules are stopped Apr 26 05:53:21 192.168.122.209 [49751.643638] [tempesta fw] exiting... Apr 26 05:53:21 192.168.122.209 [49751.755471] [tdb] Shutdown Tempesta DB Apr 26 05:53:21 192.168.122.209 [49752.002516] End test: t_reconf.test_reconf_base.TestListenReconfH2.test_reconf_proto_http Apr 26 05:53:21 192.168.122.209 [49752.024131] Start test: t_reconf.test_reconf_base.TestListenReconfH2.test_reconf_proto_https Apr 26 05:53:22 192.168.122.209 [49753.155544] [tdb] Start Tempesta DB Apr 26 05:53:22 192.168.122.209 [49753.298141] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:53:24 192.168.122.209 [49754.479967] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49754.479967] Maybe that's fine, but it's worth checking the [49754.479967] config - if there is no relations between the [49754.479967] names, then host name confusion attack is possible. Apr 26 05:53:24 192.168.122.209 [49754.579423] [tempesta fw] Configuration processing is completed. Apr 26 05:53:24 192.168.122.209 [49754.632361] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:53:24 192.168.122.209 [49755.033772] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:53:24 192.168.122.209 [49755.090809] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:53:24 192.168.122.209 [49755.116433] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:53:24 192.168.122.209 [49755.191321] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:53:24 192.168.122.209 [49755.231183] [tempesta fw] Tempesta FW is ready Apr 26 05:53:25 192.168.122.209 [49755.708459] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:53:25 192.168.122.209 [49755.752235] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49755.752235] Maybe that's fine, but it's worth checking the [49755.752235] config - if there is no relations between the [49755.752235] names, then host name confusion attack is possible. Apr 26 05:53:25 192.168.122.209 [49755.875262] [tempesta fw] Configuration processing is completed. Apr 26 05:53:25 192.168.122.209 [49756.095368] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:53:25 192.168.122.209 [49756.167405] [tempesta fw] Tempesta FW is ready Apr 26 05:53:26 192.168.122.209 [49756.673615] [tdb] Close table 'client0.tdb' Apr 26 05:53:26 192.168.122.209 [49756.870790] [tdb] Close table 'sessions0.tdb' Apr 26 05:53:29 192.168.122.209 [49760.107611] [tdb] Close table 'cache0.tdb' Apr 26 05:53:29 192.168.122.209 [49760.367750] [tdb] Close table 'filter0.tdb' Apr 26 05:53:29 192.168.122.209 [49760.368195] [tempesta fw] modules are stopped Apr 26 05:53:30 192.168.122.209 [49760.533511] [tempesta fw] exiting... Apr 26 05:53:30 192.168.122.209 [49760.657533] [tdb] Shutdown Tempesta DB Apr 26 05:53:30 192.168.122.209 [49760.864530] End test: t_reconf.test_reconf_base.TestListenReconfH2.test_reconf_proto_https Apr 26 05:53:30 192.168.122.209 [49760.886438] Start test: t_reconf.test_reconf_base.TestListenReconfH2.test_reconf_remove_listen Apr 26 05:53:31 192.168.122.209 [49761.953027] [tdb] Start Tempesta DB Apr 26 05:53:31 192.168.122.209 [49762.092172] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:53:33 192.168.122.209 [49763.471968] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49763.471968] Maybe that's fine, but it's worth checking the [49763.471968] config - if there is no relations between the [49763.471968] names, then host name confusion attack is possible. Apr 26 05:53:33 192.168.122.209 [49763.559326] [tempesta fw] Configuration processing is completed. Apr 26 05:53:33 192.168.122.209 [49763.611490] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:53:33 192.168.122.209 [49764.065284] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:53:33 192.168.122.209 [49764.091685] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:53:33 192.168.122.209 [49764.125594] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:53:33 192.168.122.209 [49764.171307] [tempesta fw] Open listen socket on: 0.0.0.0:444 Apr 26 05:53:33 192.168.122.209 [49764.172819] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:53:33 192.168.122.209 [49764.231296] [tempesta fw] Tempesta FW is ready Apr 26 05:53:34 192.168.122.209 [49764.695949] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:53:34 192.168.122.209 [49764.741063] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49764.741063] Maybe that's fine, but it's worth checking the [49764.741063] config - if there is no relations between the [49764.741063] names, then host name confusion attack is possible. Apr 26 05:53:34 192.168.122.209 [49764.851410] [tempesta fw] Configuration processing is completed. Apr 26 05:53:34 192.168.122.209 [49765.139710] [tempesta fw] Tempesta FW is ready Apr 26 05:53:35 192.168.122.209 [49765.724767] [tdb] Close table 'client0.tdb' Apr 26 05:53:35 192.168.122.209 [49765.907589] [tdb] Close table 'sessions0.tdb' Apr 26 05:53:38 192.168.122.209 [49769.134627] [tdb] Close table 'cache0.tdb' Apr 26 05:53:38 192.168.122.209 [49769.377413] [tdb] Close table 'filter0.tdb' Apr 26 05:53:38 192.168.122.209 [49769.377835] [tempesta fw] modules are stopped Apr 26 05:53:39 192.168.122.209 [49769.554117] [tempesta fw] exiting... Apr 26 05:53:39 192.168.122.209 [49769.705696] [tdb] Shutdown Tempesta DB Apr 26 05:53:39 192.168.122.209 [49769.905890] End test: t_reconf.test_reconf_base.TestListenReconfH2.test_reconf_remove_listen Apr 26 05:53:39 192.168.122.209 [49769.926098] Start test: t_reconf.test_reconf_base.TestListenReconfH2AndHttps.test_reconf_add_listen Apr 26 05:53:40 192.168.122.209 [49771.003718] [tdb] Start Tempesta DB Apr 26 05:53:40 192.168.122.209 [49771.166206] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:53:41 192.168.122.209 [49772.424543] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49772.424543] Maybe that's fine, but it's worth checking the [49772.424543] config - if there is no relations between the [49772.424543] names, then host name confusion attack is possible. Apr 26 05:53:42 192.168.122.209 [49772.531332] [tempesta fw] Configuration processing is completed. Apr 26 05:53:42 192.168.122.209 [49772.583377] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:53:42 192.168.122.209 [49773.018233] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:53:42 192.168.122.209 [49773.076722] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:53:42 192.168.122.209 [49773.104573] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:53:42 192.168.122.209 [49773.151414] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:53:42 192.168.122.209 [49773.195336] [tempesta fw] Tempesta FW is ready Apr 26 05:53:43 192.168.122.209 [49773.658866] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:53:43 192.168.122.209 [49773.732712] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49773.732712] Maybe that's fine, but it's worth checking the [49773.732712] config - if there is no relations between the [49773.732712] names, then host name confusion attack is possible. Apr 26 05:53:43 192.168.122.209 [49773.847537] [tempesta fw] Configuration processing is completed. Apr 26 05:53:43 192.168.122.209 [49774.059457] [tempesta fw] Open listen socket on: 0.0.0.0:444 Apr 26 05:53:43 192.168.122.209 [49774.115758] [tempesta fw] Tempesta FW is ready Apr 26 05:53:44 192.168.122.209 [49774.617115] [tdb] Close table 'client0.tdb' Apr 26 05:53:44 192.168.122.209 [49774.818955] [tdb] Close table 'sessions0.tdb' Apr 26 05:53:47 192.168.122.209 [49778.125462] [tdb] Close table 'cache0.tdb' Apr 26 05:53:47 192.168.122.209 [49778.362450] [tdb] Close table 'filter0.tdb' Apr 26 05:53:47 192.168.122.209 [49778.362889] [tempesta fw] modules are stopped Apr 26 05:53:48 192.168.122.209 [49778.579840] [tempesta fw] exiting... Apr 26 05:53:48 192.168.122.209 [49778.727617] [tdb] Shutdown Tempesta DB Apr 26 05:53:48 192.168.122.209 [49778.927479] End test: t_reconf.test_reconf_base.TestListenReconfH2AndHttps.test_reconf_add_listen Apr 26 05:53:48 192.168.122.209 [49778.947909] Start test: t_reconf.test_reconf_base.TestListenReconfH2AndHttps.test_reconf_ip_default_to_ipv4_port_default Apr 26 05:53:49 192.168.122.209 [49780.012415] [tdb] Start Tempesta DB Apr 26 05:53:49 192.168.122.209 [49780.154388] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:53:50 192.168.122.209 [49781.392757] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49781.392757] Maybe that's fine, but it's worth checking the [49781.392757] config - if there is no relations between the [49781.392757] names, then host name confusion attack is possible. Apr 26 05:53:51 192.168.122.209 [49781.469064] [tempesta fw] Warning: TLS: no HTTPS listener set, configuration is ignored. Apr 26 05:53:51 192.168.122.209 [49781.487655] [tempesta fw] Configuration processing is completed. Apr 26 05:53:51 192.168.122.209 [49781.542423] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:53:51 192.168.122.209 [49781.961562] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:53:51 192.168.122.209 [49781.988412] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:53:51 192.168.122.209 [49782.028165] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:53:51 192.168.122.209 [49782.099556] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:53:51 192.168.122.209 [49782.143510] [tempesta fw] Tempesta FW is ready Apr 26 05:53:52 192.168.122.209 [49782.618350] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:53:52 192.168.122.209 [49782.664821] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49782.664821] Maybe that's fine, but it's worth checking the [49782.664821] config - if there is no relations between the [49782.664821] names, then host name confusion attack is possible. Apr 26 05:53:52 192.168.122.209 [49782.771667] [tempesta fw] Configuration processing is completed. Apr 26 05:53:52 192.168.122.209 [49782.975707] [tempesta fw] Open listen socket on: 127.0.0.1 Apr 26 05:53:52 192.168.122.209 [49783.039928] [tempesta fw] Tempesta FW is ready Apr 26 05:53:53 192.168.122.209 [49783.535065] [tdb] Close table 'client0.tdb' Apr 26 05:53:53 192.168.122.209 [49783.726265] [tdb] Close table 'sessions0.tdb' Apr 26 05:53:56 192.168.122.209 [49787.000309] [tdb] Close table 'cache0.tdb' Apr 26 05:53:56 192.168.122.209 [49787.262305] [tdb] Close table 'filter0.tdb' Apr 26 05:53:56 192.168.122.209 [49787.262734] [tempesta fw] modules are stopped Apr 26 05:53:57 192.168.122.209 [49787.466639] [tempesta fw] exiting... Apr 26 05:53:57 192.168.122.209 [49787.584498] [tdb] Shutdown Tempesta DB Apr 26 05:53:57 192.168.122.209 [49787.788493] End test: t_reconf.test_reconf_base.TestListenReconfH2AndHttps.test_reconf_ip_default_to_ipv4_port_default Apr 26 05:53:57 192.168.122.209 [49787.801213] Start test: t_reconf.test_reconf_base.TestListenReconfH2AndHttps.test_reconf_ip_ipv4_to_ipv4_port_443 Apr 26 05:53:58 192.168.122.209 [49788.845521] [tdb] Start Tempesta DB Apr 26 05:53:58 192.168.122.209 [49788.967337] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:53:59 192.168.122.209 [49790.272328] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49790.272328] Maybe that's fine, but it's worth checking the [49790.272328] config - if there is no relations between the [49790.272328] names, then host name confusion attack is possible. Apr 26 05:53:59 192.168.122.209 [49790.371767] [tempesta fw] Configuration processing is completed. Apr 26 05:53:59 192.168.122.209 [49790.422254] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:54:00 192.168.122.209 [49790.842487] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:54:00 192.168.122.209 [49790.917153] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:54:00 192.168.122.209 [49790.944849] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:54:00 192.168.122.209 [49790.983627] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 05:54:00 192.168.122.209 [49791.023616] [tempesta fw] Tempesta FW is ready Apr 26 05:54:01 192.168.122.209 [49791.481153] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:54:01 192.168.122.209 [49791.524686] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49791.524686] Maybe that's fine, but it's worth checking the [49791.524686] config - if there is no relations between the [49791.524686] names, then host name confusion attack is possible. Apr 26 05:54:01 192.168.122.209 [49791.659708] [tempesta fw] Configuration processing is completed. Apr 26 05:54:01 192.168.122.209 [49791.871827] [tempesta fw] Open listen socket on: 127.0.1.100:443 Apr 26 05:54:01 192.168.122.209 [49791.920038] [tempesta fw] Tempesta FW is ready Apr 26 05:54:02 192.168.122.209 [49792.454128] [tdb] Close table 'client0.tdb' Apr 26 05:54:02 192.168.122.209 [49792.653631] [tdb] Close table 'sessions0.tdb' Apr 26 05:54:05 192.168.122.209 [49796.012611] [tdb] Close table 'cache0.tdb' Apr 26 05:54:05 192.168.122.209 [49796.296703] [tdb] Close table 'filter0.tdb' Apr 26 05:54:05 192.168.122.209 [49796.297128] [tempesta fw] modules are stopped Apr 26 05:54:06 192.168.122.209 [49796.499697] [tempesta fw] exiting... Apr 26 05:54:06 192.168.122.209 [49796.632837] [tdb] Shutdown Tempesta DB Apr 26 05:54:06 192.168.122.209 [49796.851699] End test: t_reconf.test_reconf_base.TestListenReconfH2AndHttps.test_reconf_ip_ipv4_to_ipv4_port_443 Apr 26 05:54:06 192.168.122.209 [49796.873285] Start test: t_reconf.test_reconf_base.TestListenReconfH2AndHttps.test_reconf_ip_ipv4_to_ipv4_port_default Apr 26 05:54:07 192.168.122.209 [49797.920008] [tdb] Start Tempesta DB Apr 26 05:54:07 192.168.122.209 [49798.055415] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:54:08 192.168.122.209 [49799.316495] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49799.316495] Maybe that's fine, but it's worth checking the [49799.316495] config - if there is no relations between the [49799.316495] names, then host name confusion attack is possible. Apr 26 05:54:08 192.168.122.209 [49799.411675] [tempesta fw] Configuration processing is completed. Apr 26 05:54:09 192.168.122.209 [49799.464035] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:54:09 192.168.122.209 [49799.910809] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:54:09 192.168.122.209 [49799.939514] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:54:09 192.168.122.209 [49799.975720] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:54:09 192.168.122.209 [49800.015689] [tempesta fw] Open listen socket on: 127.0.0.1 Apr 26 05:54:09 192.168.122.209 [49800.063664] [tempesta fw] Tempesta FW is ready Apr 26 05:54:10 192.168.122.209 [49800.584349] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:54:10 192.168.122.209 [49800.633059] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49800.633059] Maybe that's fine, but it's worth checking the [49800.633059] config - if there is no relations between the [49800.633059] names, then host name confusion attack is possible. Apr 26 05:54:10 192.168.122.209 [49800.755753] [tempesta fw] Configuration processing is completed. Apr 26 05:54:10 192.168.122.209 [49800.991944] [tempesta fw] Open listen socket on: 127.0.1.100 Apr 26 05:54:10 192.168.122.209 [49801.060170] [tempesta fw] Tempesta FW is ready Apr 26 05:54:11 192.168.122.209 [49801.556289] [tdb] Close table 'client0.tdb' Apr 26 05:54:11 192.168.122.209 [49801.747758] [tdb] Close table 'sessions0.tdb' Apr 26 05:54:14 192.168.122.209 [49805.078856] [tdb] Close table 'cache0.tdb' Apr 26 05:54:14 192.168.122.209 [49805.315390] [tdb] Close table 'filter0.tdb' Apr 26 05:54:14 192.168.122.209 [49805.315834] [tempesta fw] modules are stopped Apr 26 05:54:15 192.168.122.209 [49805.486905] [tempesta fw] exiting... Apr 26 05:54:15 192.168.122.209 [49805.605258] [tdb] Shutdown Tempesta DB Apr 26 05:54:15 192.168.122.209 [49805.813545] End test: t_reconf.test_reconf_base.TestListenReconfH2AndHttps.test_reconf_ip_ipv4_to_ipv4_port_default Apr 26 05:54:15 192.168.122.209 [49805.834289] Start test: t_reconf.test_reconf_base.TestListenReconfH2AndHttps.test_reconf_port Apr 26 05:54:16 192.168.122.209 [49806.929434] [tdb] Start Tempesta DB Apr 26 05:54:16 192.168.122.209 [49807.076452] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:54:17 192.168.122.209 [49808.389170] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49808.389170] Maybe that's fine, but it's worth checking the [49808.389170] config - if there is no relations between the [49808.389170] names, then host name confusion attack is possible. Apr 26 05:54:18 192.168.122.209 [49808.487970] [tempesta fw] Configuration processing is completed. Apr 26 05:54:18 192.168.122.209 [49808.546442] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:54:18 192.168.122.209 [49808.949360] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:54:18 192.168.122.209 [49809.006908] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:54:18 192.168.122.209 [49809.038793] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:54:18 192.168.122.209 [49809.083846] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:54:18 192.168.122.209 [49809.127841] [tempesta fw] Tempesta FW is ready Apr 26 05:54:19 192.168.122.209 [49809.604569] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:54:19 192.168.122.209 [49809.649160] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49809.649160] Maybe that's fine, but it's worth checking the [49809.649160] config - if there is no relations between the [49809.649160] names, then host name confusion attack is possible. Apr 26 05:54:19 192.168.122.209 [49809.795961] [tempesta fw] Configuration processing is completed. Apr 26 05:54:19 192.168.122.209 [49810.004050] [tempesta fw] Open listen socket on: 0.0.0.0:4433 Apr 26 05:54:19 192.168.122.209 [49810.076274] [tempesta fw] Tempesta FW is ready Apr 26 05:54:20 192.168.122.209 [49810.588894] [tdb] Close table 'client0.tdb' Apr 26 05:54:20 192.168.122.209 [49810.790816] [tdb] Close table 'sessions0.tdb' Apr 26 05:54:23 192.168.122.209 [49814.031921] [tdb] Close table 'cache0.tdb' Apr 26 05:54:23 192.168.122.209 [49814.277133] [tdb] Close table 'filter0.tdb' Apr 26 05:54:23 192.168.122.209 [49814.277578] [tempesta fw] modules are stopped Apr 26 05:54:24 192.168.122.209 [49814.480364] [tempesta fw] exiting... Apr 26 05:54:24 192.168.122.209 [49814.603960] [tdb] Shutdown Tempesta DB Apr 26 05:54:24 192.168.122.209 [49814.798677] End test: t_reconf.test_reconf_base.TestListenReconfH2AndHttps.test_reconf_port Apr 26 05:54:24 192.168.122.209 [49814.820770] Start test: t_reconf.test_reconf_base.TestListenReconfH2AndHttps.test_reconf_proto_h2 Apr 26 05:54:25 192.168.122.209 [49815.929833] [tdb] Start Tempesta DB Apr 26 05:54:25 192.168.122.209 [49816.085391] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:54:26 192.168.122.209 [49817.337255] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49817.337255] Maybe that's fine, but it's worth checking the [49817.337255] config - if there is no relations between the [49817.337255] names, then host name confusion attack is possible. Apr 26 05:54:27 192.168.122.209 [49817.444106] [tempesta fw] Configuration processing is completed. Apr 26 05:54:27 192.168.122.209 [49817.497299] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:54:27 192.168.122.209 [49817.941461] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:54:27 192.168.122.209 [49818.008747] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:54:27 192.168.122.209 [49818.037718] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:54:27 192.168.122.209 [49818.079998] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:54:27 192.168.122.209 [49818.135960] [tempesta fw] Tempesta FW is ready Apr 26 05:54:28 192.168.122.209 [49818.585544] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:54:28 192.168.122.209 [49818.647783] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49818.647783] Maybe that's fine, but it's worth checking the [49818.647783] config - if there is no relations between the [49818.647783] names, then host name confusion attack is possible. Apr 26 05:54:28 192.168.122.209 [49818.768108] [tempesta fw] Configuration processing is completed. Apr 26 05:54:28 192.168.122.209 [49819.000218] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:54:28 192.168.122.209 [49819.064388] [tempesta fw] Tempesta FW is ready Apr 26 05:54:29 192.168.122.209 [49819.531779] [tdb] Close table 'client0.tdb' Apr 26 05:54:29 192.168.122.209 [49819.715136] [tdb] Close table 'sessions0.tdb' Apr 26 05:54:32 192.168.122.209 [49822.947096] [tdb] Close table 'cache0.tdb' Apr 26 05:54:32 192.168.122.209 [49823.182600] [tdb] Close table 'filter0.tdb' Apr 26 05:54:32 192.168.122.209 [49823.183040] [tempesta fw] modules are stopped Apr 26 05:54:32 192.168.122.209 [49823.378350] [tempesta fw] exiting... Apr 26 05:54:33 192.168.122.209 [49823.492438] [tdb] Shutdown Tempesta DB Apr 26 05:54:33 192.168.122.209 [49823.707344] End test: t_reconf.test_reconf_base.TestListenReconfH2AndHttps.test_reconf_proto_h2 Apr 26 05:54:33 192.168.122.209 [49823.716826] Start test: t_reconf.test_reconf_base.TestListenReconfH2AndHttps.test_reconf_proto_h2_https Apr 26 05:54:34 192.168.122.209 [49824.798541] [tdb] Start Tempesta DB Apr 26 05:54:34 192.168.122.209 [49824.935304] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:54:35 192.168.122.209 [49826.225394] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49826.225394] Maybe that's fine, but it's worth checking the [49826.225394] config - if there is no relations between the [49826.225394] names, then host name confusion attack is possible. Apr 26 05:54:35 192.168.122.209 [49826.332231] [tempesta fw] Configuration processing is completed. Apr 26 05:54:35 192.168.122.209 [49826.394977] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:54:36 192.168.122.209 [49826.864009] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:54:36 192.168.122.209 [49826.893204] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:54:36 192.168.122.209 [49826.930834] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:54:36 192.168.122.209 [49826.988136] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:54:36 192.168.122.209 [49827.040133] [tempesta fw] Tempesta FW is ready Apr 26 05:54:37 192.168.122.209 [49827.477272] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:54:37 192.168.122.209 [49827.516699] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49827.516699] Maybe that's fine, but it's worth checking the [49827.516699] config - if there is no relations between the [49827.516699] names, then host name confusion attack is possible. Apr 26 05:54:37 192.168.122.209 [49827.660194] [tempesta fw] Configuration processing is completed. Apr 26 05:54:37 192.168.122.209 [49827.896549] [tempesta fw] Tempesta FW is ready Apr 26 05:54:37 192.168.122.209 [49828.324581] [tdb] Close table 'client0.tdb' Apr 26 05:54:38 192.168.122.209 [49828.536375] [tdb] Close table 'sessions0.tdb' Apr 26 05:54:41 192.168.122.209 [49831.738712] [tdb] Close table 'cache0.tdb' Apr 26 05:54:41 192.168.122.209 [49831.978914] [tdb] Close table 'filter0.tdb' Apr 26 05:54:41 192.168.122.209 [49831.979341] [tempesta fw] modules are stopped Apr 26 05:54:41 192.168.122.209 [49832.204350] [tempesta fw] exiting... Apr 26 05:54:41 192.168.122.209 [49832.342907] [tdb] Shutdown Tempesta DB Apr 26 05:54:42 192.168.122.209 [49832.560958] End test: t_reconf.test_reconf_base.TestListenReconfH2AndHttps.test_reconf_proto_h2_https Apr 26 05:54:42 192.168.122.209 [49832.575314] Start test: t_reconf.test_reconf_base.TestListenReconfH2AndHttps.test_reconf_proto_http Apr 26 05:54:43 192.168.122.209 [49833.656142] [tdb] Start Tempesta DB Apr 26 05:54:43 192.168.122.209 [49833.806311] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:54:44 192.168.122.209 [49835.141058] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49835.141058] Maybe that's fine, but it's worth checking the [49835.141058] config - if there is no relations between the [49835.141058] names, then host name confusion attack is possible. Apr 26 05:54:44 192.168.122.209 [49835.236415] [tempesta fw] Configuration processing is completed. Apr 26 05:54:44 192.168.122.209 [49835.298936] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:54:45 192.168.122.209 [49835.712661] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:54:45 192.168.122.209 [49835.771075] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:54:45 192.168.122.209 [49835.797806] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:54:45 192.168.122.209 [49835.840173] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:54:45 192.168.122.209 [49835.880202] [tempesta fw] Tempesta FW is ready Apr 26 05:54:45 192.168.122.209 [49836.331130] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:54:45 192.168.122.209 [49836.389463] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49836.389463] Maybe that's fine, but it's worth checking the [49836.389463] config - if there is no relations between the [49836.389463] names, then host name confusion attack is possible. Apr 26 05:54:46 192.168.122.209 [49836.516398] [tempesta fw] Configuration processing is completed. Apr 26 05:54:46 192.168.122.209 [49836.732454] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:54:46 192.168.122.209 [49836.780660] [tempesta fw] Tempesta FW is ready Apr 26 05:54:46 192.168.122.209 [49837.257557] [tdb] Close table 'client0.tdb' Apr 26 05:54:47 192.168.122.209 [49837.451797] [tdb] Close table 'sessions0.tdb' Apr 26 05:54:50 192.168.122.209 [49840.646627] [tdb] Close table 'cache0.tdb' Apr 26 05:54:50 192.168.122.209 [49840.856789] [tdb] Close table 'filter0.tdb' Apr 26 05:54:50 192.168.122.209 [49840.857238] [tempesta fw] modules are stopped Apr 26 05:54:50 192.168.122.209 [49841.068770] [tempesta fw] exiting... Apr 26 05:54:50 192.168.122.209 [49841.193151] [tdb] Shutdown Tempesta DB Apr 26 05:54:50 192.168.122.209 [49841.409470] End test: t_reconf.test_reconf_base.TestListenReconfH2AndHttps.test_reconf_proto_http Apr 26 05:54:50 192.168.122.209 [49841.421747] Start test: t_reconf.test_reconf_base.TestListenReconfH2AndHttps.test_reconf_proto_https Apr 26 05:54:52 192.168.122.209 [49842.489641] [tdb] Start Tempesta DB Apr 26 05:54:52 192.168.122.209 [49842.627190] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:54:53 192.168.122.209 [49843.921649] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49843.921649] Maybe that's fine, but it's worth checking the [49843.921649] config - if there is no relations between the [49843.921649] names, then host name confusion attack is possible. Apr 26 05:54:53 192.168.122.209 [49844.020416] [tempesta fw] Configuration processing is completed. Apr 26 05:54:53 192.168.122.209 [49844.074217] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:54:54 192.168.122.209 [49844.495508] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:54:54 192.168.122.209 [49844.524773] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:54:54 192.168.122.209 [49844.564820] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:54:54 192.168.122.209 [49844.632373] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:54:54 192.168.122.209 [49844.672287] [tempesta fw] Tempesta FW is ready Apr 26 05:54:54 192.168.122.209 [49845.092863] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:54:54 192.168.122.209 [49845.145205] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49845.145205] Maybe that's fine, but it's worth checking the [49845.145205] config - if there is no relations between the [49845.145205] names, then host name confusion attack is possible. Apr 26 05:54:54 192.168.122.209 [49845.268340] [tempesta fw] Configuration processing is completed. Apr 26 05:54:55 192.168.122.209 [49845.488500] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:54:55 192.168.122.209 [49845.548836] [tempesta fw] Tempesta FW is ready Apr 26 05:54:55 192.168.122.209 [49846.032994] [tdb] Close table 'client0.tdb' Apr 26 05:54:55 192.168.122.209 [49846.224358] [tdb] Close table 'sessions0.tdb' Apr 26 05:54:58 192.168.122.209 [49849.432084] [tdb] Close table 'cache0.tdb' Apr 26 05:54:59 192.168.122.209 [49849.668403] [tdb] Close table 'filter0.tdb' Apr 26 05:54:59 192.168.122.209 [49849.668828] [tempesta fw] modules are stopped Apr 26 05:54:59 192.168.122.209 [49849.856601] [tempesta fw] exiting... Apr 26 05:54:59 192.168.122.209 [49850.001793] [tdb] Shutdown Tempesta DB Apr 26 05:54:59 192.168.122.209 [49850.261800] End test: t_reconf.test_reconf_base.TestListenReconfH2AndHttps.test_reconf_proto_https Apr 26 05:54:59 192.168.122.209 [49850.285725] Start test: t_reconf.test_reconf_base.TestListenReconfH2AndHttps.test_reconf_remove_listen Apr 26 05:55:00 192.168.122.209 [49851.314149] [tdb] Start Tempesta DB Apr 26 05:55:01 192.168.122.209 [49851.457044] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:55:02 192.168.122.209 [49852.838043] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49852.838043] Maybe that's fine, but it's worth checking the [49852.838043] config - if there is no relations between the [49852.838043] names, then host name confusion attack is possible. Apr 26 05:55:02 192.168.122.209 [49852.936505] [tempesta fw] Configuration processing is completed. Apr 26 05:55:02 192.168.122.209 [49852.987382] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:55:02 192.168.122.209 [49853.391540] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:55:03 192.168.122.209 [49853.455797] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:55:03 192.168.122.209 [49853.483174] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:55:03 192.168.122.209 [49853.516468] [tempesta fw] Open listen socket on: 0.0.0.0:444 Apr 26 05:55:03 192.168.122.209 [49853.518248] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:55:03 192.168.122.209 [49853.552402] [tempesta fw] Tempesta FW is ready Apr 26 05:55:03 192.168.122.209 [49853.985519] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:55:03 192.168.122.209 [49854.038658] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49854.038658] Maybe that's fine, but it's worth checking the [49854.038658] config - if there is no relations between the [49854.038658] names, then host name confusion attack is possible. Apr 26 05:55:03 192.168.122.209 [49854.168551] [tempesta fw] Configuration processing is completed. Apr 26 05:55:03 192.168.122.209 [49854.432812] [tempesta fw] Tempesta FW is ready Apr 26 05:55:04 192.168.122.209 [49854.907270] [tdb] Close table 'client0.tdb' Apr 26 05:55:04 192.168.122.209 [49855.086338] [tdb] Close table 'sessions0.tdb' Apr 26 05:55:07 192.168.122.209 [49858.301165] [tdb] Close table 'cache0.tdb' Apr 26 05:55:08 192.168.122.209 [49858.536739] [tdb] Close table 'filter0.tdb' Apr 26 05:55:08 192.168.122.209 [49858.537183] [tempesta fw] modules are stopped Apr 26 05:55:08 192.168.122.209 [49858.765010] [tempesta fw] exiting... Apr 26 05:55:08 192.168.122.209 [49858.910067] [tdb] Shutdown Tempesta DB Apr 26 05:55:08 192.168.122.209 [49859.115576] End test: t_reconf.test_reconf_base.TestListenReconfH2AndHttps.test_reconf_remove_listen Apr 26 05:55:08 192.168.122.209 [49859.133397] Start test: t_reconf.test_reconf_base.TestListenReconfHttp.test_reconf_add_listen Apr 26 05:55:09 192.168.122.209 [49860.198707] [tdb] Start Tempesta DB Apr 26 05:55:09 192.168.122.209 [49860.330483] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:55:11 192.168.122.209 [49861.585810] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49861.585810] Maybe that's fine, but it's worth checking the [49861.585810] config - if there is no relations between the [49861.585810] names, then host name confusion attack is possible. Apr 26 05:55:11 192.168.122.209 [49861.673875] [tempesta fw] Warning: TLS: no HTTPS listener set, configuration is ignored. Apr 26 05:55:11 192.168.122.209 [49861.696677] [tempesta fw] Configuration processing is completed. Apr 26 05:55:11 192.168.122.209 [49861.747822] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:55:11 192.168.122.209 [49862.164319] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:55:11 192.168.122.209 [49862.191420] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:55:11 192.168.122.209 [49862.226177] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:55:11 192.168.122.209 [49862.264510] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:55:11 192.168.122.209 [49862.304529] [tempesta fw] Tempesta FW is ready Apr 26 05:55:12 192.168.122.209 [49862.769339] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:55:12 192.168.122.209 [49862.841779] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49862.841779] Maybe that's fine, but it's worth checking the [49862.841779] config - if there is no relations between the [49862.841779] names, then host name confusion attack is possible. Apr 26 05:55:12 192.168.122.209 [49862.941468] [tempesta fw] Warning: TLS: no HTTPS listener set, configuration is ignored. Apr 26 05:55:12 192.168.122.209 [49862.961078] [tempesta fw] Configuration processing is completed. Apr 26 05:55:12 192.168.122.209 [49863.196952] [tempesta fw] Open listen socket on: 0.0.0.0:444 Apr 26 05:55:12 192.168.122.209 [49863.252931] [tempesta fw] Tempesta FW is ready Apr 26 05:55:13 192.168.122.209 [49863.733306] [tdb] Close table 'client0.tdb' Apr 26 05:55:13 192.168.122.209 [49863.940623] [tdb] Close table 'sessions0.tdb' Apr 26 05:55:16 192.168.122.209 [49867.229436] [tdb] Close table 'cache0.tdb' Apr 26 05:55:17 192.168.122.209 [49867.451314] [tdb] Close table 'filter0.tdb' Apr 26 05:55:17 192.168.122.209 [49867.451758] [tempesta fw] modules are stopped Apr 26 05:55:17 192.168.122.209 [49867.658224] [tempesta fw] exiting... Apr 26 05:55:17 192.168.122.209 [49867.792926] [tdb] Shutdown Tempesta DB Apr 26 05:55:17 192.168.122.209 [49867.997495] End test: t_reconf.test_reconf_base.TestListenReconfHttp.test_reconf_add_listen Apr 26 05:55:17 192.168.122.209 [49868.005604] Start test: t_reconf.test_reconf_base.TestListenReconfHttp.test_reconf_ip_default_to_ipv4_port_default Apr 26 05:55:18 192.168.122.209 [49869.084529] [tdb] Start Tempesta DB Apr 26 05:55:18 192.168.122.209 [49869.228618] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:55:20 192.168.122.209 [49870.461774] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49870.461774] Maybe that's fine, but it's worth checking the [49870.461774] config - if there is no relations between the [49870.461774] names, then host name confusion attack is possible. Apr 26 05:55:20 192.168.122.209 [49870.546323] [tempesta fw] Warning: TLS: no HTTPS listener set, configuration is ignored. Apr 26 05:55:20 192.168.122.209 [49870.564778] [tempesta fw] Configuration processing is completed. Apr 26 05:55:20 192.168.122.209 [49870.615797] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:55:20 192.168.122.209 [49871.032200] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:55:20 192.168.122.209 [49871.091550] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:55:20 192.168.122.209 [49871.118205] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:55:20 192.168.122.209 [49871.168675] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:55:20 192.168.122.209 [49871.212665] [tempesta fw] Tempesta FW is ready Apr 26 05:55:21 192.168.122.209 [49871.648050] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:55:21 192.168.122.209 [49871.681604] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49871.681604] Maybe that's fine, but it's worth checking the [49871.681604] config - if there is no relations between the [49871.681604] names, then host name confusion attack is possible. Apr 26 05:55:21 192.168.122.209 [49871.785381] [tempesta fw] Warning: TLS: no HTTPS listener set, configuration is ignored. Apr 26 05:55:21 192.168.122.209 [49871.808709] [tempesta fw] Configuration processing is completed. Apr 26 05:55:21 192.168.122.209 [49872.004891] [tempesta fw] Open listen socket on: 127.0.0.1 Apr 26 05:55:21 192.168.122.209 [49872.061049] [tempesta fw] Tempesta FW is ready Apr 26 05:55:22 192.168.122.209 [49872.570261] [tdb] Close table 'client0.tdb' Apr 26 05:55:22 192.168.122.209 [49872.759574] [tdb] Close table 'sessions0.tdb' Apr 26 05:55:25 192.168.122.209 [49875.996930] [tdb] Close table 'cache0.tdb' Apr 26 05:55:25 192.168.122.209 [49876.241311] [tdb] Close table 'filter0.tdb' Apr 26 05:55:25 192.168.122.209 [49876.241753] [tempesta fw] modules are stopped Apr 26 05:55:26 192.168.122.209 [49876.461926] [tempesta fw] exiting... Apr 26 05:55:26 192.168.122.209 [49876.591888] [tdb] Shutdown Tempesta DB Apr 26 05:55:26 192.168.122.209 [49876.814810] End test: t_reconf.test_reconf_base.TestListenReconfHttp.test_reconf_ip_default_to_ipv4_port_default Apr 26 05:55:26 192.168.122.209 [49876.823003] Start test: t_reconf.test_reconf_base.TestListenReconfHttp.test_reconf_ip_ipv4_to_ipv4_port_443 Apr 26 05:55:27 192.168.122.209 [49877.891445] [tdb] Start Tempesta DB Apr 26 05:55:27 192.168.122.209 [49878.053130] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:55:28 192.168.122.209 [49879.354184] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49879.354184] Maybe that's fine, but it's worth checking the [49879.354184] config - if there is no relations between the [49879.354184] names, then host name confusion attack is possible. Apr 26 05:55:28 192.168.122.209 [49879.430261] [tempesta fw] Warning: TLS: no HTTPS listener set, configuration is ignored. Apr 26 05:55:29 192.168.122.209 [49879.448890] [tempesta fw] Configuration processing is completed. Apr 26 05:55:29 192.168.122.209 [49879.505001] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:55:29 192.168.122.209 [49879.985257] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:55:29 192.168.122.209 [49880.015606] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:55:29 192.168.122.209 [49880.054001] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:55:29 192.168.122.209 [49880.100796] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 05:55:29 192.168.122.209 [49880.140752] [tempesta fw] Tempesta FW is ready Apr 26 05:55:30 192.168.122.209 [49880.571823] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:55:30 192.168.122.209 [49880.618067] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49880.618067] Maybe that's fine, but it's worth checking the [49880.618067] config - if there is no relations between the [49880.618067] names, then host name confusion attack is possible. Apr 26 05:55:30 192.168.122.209 [49880.725441] [tempesta fw] Warning: TLS: no HTTPS listener set, configuration is ignored. Apr 26 05:55:30 192.168.122.209 [49880.744847] [tempesta fw] Configuration processing is completed. Apr 26 05:55:30 192.168.122.209 [49880.968991] [tempesta fw] Open listen socket on: 127.0.1.100:443 Apr 26 05:55:30 192.168.122.209 [49881.033179] [tempesta fw] Tempesta FW is ready Apr 26 05:55:31 192.168.122.209 [49881.548240] [tdb] Close table 'client0.tdb' Apr 26 05:55:31 192.168.122.209 [49881.732061] [tdb] Close table 'sessions0.tdb' Apr 26 05:55:34 192.168.122.209 [49885.045346] [tdb] Close table 'cache0.tdb' Apr 26 05:55:34 192.168.122.209 [49885.287252] [tdb] Close table 'filter0.tdb' Apr 26 05:55:34 192.168.122.209 [49885.287721] [tempesta fw] modules are stopped Apr 26 05:55:35 192.168.122.209 [49885.470051] [tempesta fw] exiting... Apr 26 05:55:35 192.168.122.209 [49885.611351] [tdb] Shutdown Tempesta DB Apr 26 05:55:35 192.168.122.209 [49885.796998] End test: t_reconf.test_reconf_base.TestListenReconfHttp.test_reconf_ip_ipv4_to_ipv4_port_443 Apr 26 05:55:35 192.168.122.209 [49885.807018] Start test: t_reconf.test_reconf_base.TestListenReconfHttp.test_reconf_ip_ipv4_to_ipv4_port_default Apr 26 05:55:36 192.168.122.209 [49886.805162] [tdb] Start Tempesta DB Apr 26 05:55:36 192.168.122.209 [49886.948360] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:55:37 192.168.122.209 [49888.306100] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49888.306100] Maybe that's fine, but it's worth checking the [49888.306100] config - if there is no relations between the [49888.306100] names, then host name confusion attack is possible. Apr 26 05:55:37 192.168.122.209 [49888.394380] [tempesta fw] Warning: TLS: no HTTPS listener set, configuration is ignored. Apr 26 05:55:37 192.168.122.209 [49888.424980] [tempesta fw] Configuration processing is completed. Apr 26 05:55:38 192.168.122.209 [49888.480798] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:55:38 192.168.122.209 [49888.896129] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:55:38 192.168.122.209 [49888.961896] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:55:38 192.168.122.209 [49888.988187] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:55:38 192.168.122.209 [49889.028981] [tempesta fw] Open listen socket on: 127.0.0.1 Apr 26 05:55:38 192.168.122.209 [49889.068862] [tempesta fw] Tempesta FW is ready Apr 26 05:55:39 192.168.122.209 [49889.566958] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:55:39 192.168.122.209 [49889.605824] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49889.605824] Maybe that's fine, but it's worth checking the [49889.605824] config - if there is no relations between the [49889.605824] names, then host name confusion attack is possible. Apr 26 05:55:39 192.168.122.209 [49889.705550] [tempesta fw] Warning: TLS: no HTTPS listener set, configuration is ignored. Apr 26 05:55:39 192.168.122.209 [49889.728969] [tempesta fw] Configuration processing is completed. Apr 26 05:55:39 192.168.122.209 [49889.933241] [tempesta fw] Open listen socket on: 127.0.1.100 Apr 26 05:55:39 192.168.122.209 [49889.989310] [tempesta fw] Tempesta FW is ready Apr 26 05:55:40 192.168.122.209 [49890.508238] [tdb] Close table 'client0.tdb' Apr 26 05:55:40 192.168.122.209 [49890.696272] [tdb] Close table 'sessions0.tdb' Apr 26 05:55:43 192.168.122.209 [49894.062228] [tdb] Close table 'cache0.tdb' Apr 26 05:55:43 192.168.122.209 [49894.302751] [tdb] Close table 'filter0.tdb' Apr 26 05:55:43 192.168.122.209 [49894.303209] [tempesta fw] modules are stopped Apr 26 05:55:44 192.168.122.209 [49894.511980] [tempesta fw] exiting... Apr 26 05:55:44 192.168.122.209 [49894.652264] [tdb] Shutdown Tempesta DB Apr 26 05:55:44 192.168.122.209 [49894.866691] End test: t_reconf.test_reconf_base.TestListenReconfHttp.test_reconf_ip_ipv4_to_ipv4_port_default Apr 26 05:55:44 192.168.122.209 [49894.884363] Start test: t_reconf.test_reconf_base.TestListenReconfHttp.test_reconf_port Apr 26 05:55:45 192.168.122.209 [49896.039118] [tdb] Start Tempesta DB Apr 26 05:55:45 192.168.122.209 [49896.175749] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:55:47 192.168.122.209 [49897.529424] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49897.529424] Maybe that's fine, but it's worth checking the [49897.529424] config - if there is no relations between the [49897.529424] names, then host name confusion attack is possible. Apr 26 05:55:47 192.168.122.209 [49897.602402] [tempesta fw] Warning: TLS: no HTTPS listener set, configuration is ignored. Apr 26 05:55:47 192.168.122.209 [49897.621112] [tempesta fw] Configuration processing is completed. Apr 26 05:55:47 192.168.122.209 [49897.673719] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:55:47 192.168.122.209 [49898.101205] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:55:47 192.168.122.209 [49898.127658] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:55:47 192.168.122.209 [49898.154639] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:55:47 192.168.122.209 [49898.200996] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:55:47 192.168.122.209 [49898.240920] [tempesta fw] Tempesta FW is ready Apr 26 05:55:48 192.168.122.209 [49898.679841] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:55:48 192.168.122.209 [49898.730597] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49898.730597] Maybe that's fine, but it's worth checking the [49898.730597] config - if there is no relations between the [49898.730597] names, then host name confusion attack is possible. Apr 26 05:55:48 192.168.122.209 [49898.820342] [tempesta fw] Warning: TLS: no HTTPS listener set, configuration is ignored. Apr 26 05:55:48 192.168.122.209 [49898.845031] [tempesta fw] Configuration processing is completed. Apr 26 05:55:48 192.168.122.209 [49899.033122] [tempesta fw] Open listen socket on: 0.0.0.0:4433 Apr 26 05:55:48 192.168.122.209 [49899.089163] [tempesta fw] Tempesta FW is ready Apr 26 05:55:49 192.168.122.209 [49899.562343] [tdb] Close table 'client0.tdb' Apr 26 05:55:49 192.168.122.209 [49899.751228] [tdb] Close table 'sessions0.tdb' Apr 26 05:55:52 192.168.122.209 [49903.066357] [tdb] Close table 'cache0.tdb' Apr 26 05:55:52 192.168.122.209 [49903.325181] [tdb] Close table 'filter0.tdb' Apr 26 05:55:52 192.168.122.209 [49903.325643] [tempesta fw] modules are stopped Apr 26 05:55:53 192.168.122.209 [49903.541737] [tempesta fw] exiting... Apr 26 05:55:53 192.168.122.209 [49903.662400] [tdb] Shutdown Tempesta DB Apr 26 05:55:53 192.168.122.209 [49903.885129] End test: t_reconf.test_reconf_base.TestListenReconfHttp.test_reconf_port Apr 26 05:55:53 192.168.122.209 [49903.905467] Start test: t_reconf.test_reconf_base.TestListenReconfHttp.test_reconf_proto_h2 Apr 26 05:55:54 192.168.122.209 [49904.983403] [tdb] Start Tempesta DB Apr 26 05:55:54 192.168.122.209 [49905.133378] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:55:56 192.168.122.209 [49906.434363] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49906.434363] Maybe that's fine, but it's worth checking the [49906.434363] config - if there is no relations between the [49906.434363] names, then host name confusion attack is possible. Apr 26 05:55:56 192.168.122.209 [49906.514456] [tempesta fw] Warning: TLS: no HTTPS listener set, configuration is ignored. Apr 26 05:55:56 192.168.122.209 [49906.533137] [tempesta fw] Configuration processing is completed. Apr 26 05:55:56 192.168.122.209 [49906.588905] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:55:56 192.168.122.209 [49907.005006] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:55:56 192.168.122.209 [49907.031780] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:55:56 192.168.122.209 [49907.058504] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:55:56 192.168.122.209 [49907.109756] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:55:56 192.168.122.209 [49907.149013] [tempesta fw] Tempesta FW is ready Apr 26 05:55:57 192.168.122.209 [49907.620281] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:55:57 192.168.122.209 [49907.677816] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49907.677816] Maybe that's fine, but it's worth checking the [49907.677816] config - if there is no relations between the [49907.677816] names, then host name confusion attack is possible. Apr 26 05:55:57 192.168.122.209 [49907.793054] [tempesta fw] Configuration processing is completed. Apr 26 05:55:57 192.168.122.209 [49907.973229] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:55:57 192.168.122.209 [49908.029243] [tempesta fw] Tempesta FW is ready Apr 26 05:55:58 192.168.122.209 [49908.466849] [tdb] Close table 'client0.tdb' Apr 26 05:55:58 192.168.122.209 [49908.689593] [tdb] Close table 'sessions0.tdb' Apr 26 05:56:01 192.168.122.209 [49911.999263] [tdb] Close table 'cache0.tdb' Apr 26 05:56:01 192.168.122.209 [49912.225958] [tdb] Close table 'filter0.tdb' Apr 26 05:56:01 192.168.122.209 [49912.226400] [tempesta fw] modules are stopped Apr 26 05:56:02 192.168.122.209 [49912.460784] [tempesta fw] exiting... Apr 26 05:56:02 192.168.122.209 [49912.599636] [tdb] Shutdown Tempesta DB Apr 26 05:56:02 192.168.122.209 [49912.777073] End test: t_reconf.test_reconf_base.TestListenReconfHttp.test_reconf_proto_h2 Apr 26 05:56:02 192.168.122.209 [49912.790583] Start test: t_reconf.test_reconf_base.TestListenReconfHttp.test_reconf_proto_h2_https Apr 26 05:56:03 192.168.122.209 [49913.788235] [tdb] Start Tempesta DB Apr 26 05:56:03 192.168.122.209 [49913.937813] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:56:04 192.168.122.209 [49915.258578] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49915.258578] Maybe that's fine, but it's worth checking the [49915.258578] config - if there is no relations between the [49915.258578] names, then host name confusion attack is possible. Apr 26 05:56:04 192.168.122.209 [49915.334681] [tempesta fw] Warning: TLS: no HTTPS listener set, configuration is ignored. Apr 26 05:56:04 192.168.122.209 [49915.357274] [tempesta fw] Configuration processing is completed. Apr 26 05:56:04 192.168.122.209 [49915.411541] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:56:05 192.168.122.209 [49915.892846] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:56:05 192.168.122.209 [49915.927588] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:56:05 192.168.122.209 [49915.972693] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:56:05 192.168.122.209 [49916.017198] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:56:05 192.168.122.209 [49916.057107] [tempesta fw] Tempesta FW is ready Apr 26 05:56:06 192.168.122.209 [49916.459808] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:56:06 192.168.122.209 [49916.502429] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49916.502429] Maybe that's fine, but it's worth checking the [49916.502429] config - if there is no relations between the [49916.502429] names, then host name confusion attack is possible. Apr 26 05:56:06 192.168.122.209 [49916.625206] [tempesta fw] Configuration processing is completed. Apr 26 05:56:06 192.168.122.209 [49916.853444] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:56:06 192.168.122.209 [49916.917620] [tempesta fw] Tempesta FW is ready Apr 26 05:56:06 192.168.122.209 [49917.376466] [tdb] Close table 'client0.tdb' Apr 26 05:56:07 192.168.122.209 [49917.574031] [tdb] Close table 'sessions0.tdb' Apr 26 05:56:10 192.168.122.209 [49920.804119] [tdb] Close table 'cache0.tdb' Apr 26 05:56:10 192.168.122.209 [49921.041382] [tdb] Close table 'filter0.tdb' Apr 26 05:56:10 192.168.122.209 [49921.041813] [tempesta fw] modules are stopped Apr 26 05:56:10 192.168.122.209 [49921.220269] [tempesta fw] exiting... Apr 26 05:56:10 192.168.122.209 [49921.385556] [tdb] Shutdown Tempesta DB Apr 26 05:56:11 192.168.122.209 [49921.618991] End test: t_reconf.test_reconf_base.TestListenReconfHttp.test_reconf_proto_h2_https Apr 26 05:56:11 192.168.122.209 [49921.636677] Start test: t_reconf.test_reconf_base.TestListenReconfHttp.test_reconf_proto_http Apr 26 05:56:12 192.168.122.209 [49922.669642] [tdb] Start Tempesta DB Apr 26 05:56:12 192.168.122.209 [49922.811253] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:56:13 192.168.122.209 [49924.130365] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49924.130365] Maybe that's fine, but it's worth checking the [49924.130365] config - if there is no relations between the [49924.130365] names, then host name confusion attack is possible. Apr 26 05:56:13 192.168.122.209 [49924.242439] [tempesta fw] Warning: TLS: no HTTPS listener set, configuration is ignored. Apr 26 05:56:13 192.168.122.209 [49924.273504] [tempesta fw] Configuration processing is completed. Apr 26 05:56:13 192.168.122.209 [49924.329665] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:56:14 192.168.122.209 [49924.763569] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:56:14 192.168.122.209 [49924.799265] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:56:14 192.168.122.209 [49924.826307] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:56:14 192.168.122.209 [49924.893393] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:56:14 192.168.122.209 [49924.933348] [tempesta fw] Tempesta FW is ready Apr 26 05:56:14 192.168.122.209 [49925.383105] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:56:15 192.168.122.209 [49925.446592] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49925.446592] Maybe that's fine, but it's worth checking the [49925.446592] config - if there is no relations between the [49925.446592] names, then host name confusion attack is possible. Apr 26 05:56:15 192.168.122.209 [49925.546328] [tempesta fw] Warning: TLS: no HTTPS listener set, configuration is ignored. Apr 26 05:56:15 192.168.122.209 [49925.565949] [tempesta fw] Configuration processing is completed. Apr 26 05:56:15 192.168.122.209 [49925.833501] [tempesta fw] Tempesta FW is ready Apr 26 05:56:15 192.168.122.209 [49926.300126] [tdb] Close table 'client0.tdb' Apr 26 05:56:16 192.168.122.209 [49926.512209] [tdb] Close table 'sessions0.tdb' Apr 26 05:56:19 192.168.122.209 [49929.789349] [tdb] Close table 'cache0.tdb' Apr 26 05:56:19 192.168.122.209 [49930.036872] [tdb] Close table 'filter0.tdb' Apr 26 05:56:19 192.168.122.209 [49930.037339] [tempesta fw] modules are stopped Apr 26 05:56:19 192.168.122.209 [49930.241691] [tempesta fw] exiting... Apr 26 05:56:19 192.168.122.209 [49930.375920] [tdb] Shutdown Tempesta DB Apr 26 05:56:20 192.168.122.209 [49930.587958] End test: t_reconf.test_reconf_base.TestListenReconfHttp.test_reconf_proto_http Apr 26 05:56:20 192.168.122.209 [49930.604956] Start test: t_reconf.test_reconf_base.TestListenReconfHttp.test_reconf_proto_https Apr 26 05:56:21 192.168.122.209 [49931.716285] [tdb] Start Tempesta DB Apr 26 05:56:21 192.168.122.209 [49931.852087] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:56:22 192.168.122.209 [49933.142685] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49933.142685] Maybe that's fine, but it's worth checking the [49933.142685] config - if there is no relations between the [49933.142685] names, then host name confusion attack is possible. Apr 26 05:56:22 192.168.122.209 [49933.243641] [tempesta fw] Warning: TLS: no HTTPS listener set, configuration is ignored. Apr 26 05:56:22 192.168.122.209 [49933.257539] [tempesta fw] Configuration processing is completed. Apr 26 05:56:22 192.168.122.209 [49933.308268] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:56:23 192.168.122.209 [49933.723487] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:56:23 192.168.122.209 [49933.749453] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:56:23 192.168.122.209 [49933.775379] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:56:23 192.168.122.209 [49933.833408] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:56:23 192.168.122.209 [49933.873417] [tempesta fw] Tempesta FW is ready Apr 26 05:56:23 192.168.122.209 [49934.300675] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:56:23 192.168.122.209 [49934.362818] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49934.362818] Maybe that's fine, but it's worth checking the [49934.362818] config - if there is no relations between the [49934.362818] names, then host name confusion attack is possible. Apr 26 05:56:24 192.168.122.209 [49934.497490] [tempesta fw] Configuration processing is completed. Apr 26 05:56:24 192.168.122.209 [49934.741836] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:56:24 192.168.122.209 [49934.813876] [tempesta fw] Tempesta FW is ready Apr 26 05:56:24 192.168.122.209 [49935.300031] [tdb] Close table 'client0.tdb' Apr 26 05:56:25 192.168.122.209 [49935.505797] [tdb] Close table 'sessions0.tdb' Apr 26 05:56:28 192.168.122.209 [49938.734531] [tdb] Close table 'cache0.tdb' Apr 26 05:56:28 192.168.122.209 [49938.953461] [tdb] Close table 'filter0.tdb' Apr 26 05:56:28 192.168.122.209 [49938.953904] [tempesta fw] modules are stopped Apr 26 05:56:28 192.168.122.209 [49939.157033] [tempesta fw] exiting... Apr 26 05:56:28 192.168.122.209 [49939.276175] [tdb] Shutdown Tempesta DB Apr 26 05:56:29 192.168.122.209 [49939.467029] End test: t_reconf.test_reconf_base.TestListenReconfHttp.test_reconf_proto_https Apr 26 05:56:29 192.168.122.209 [49939.473448] Start test: t_reconf.test_reconf_base.TestListenReconfHttp.test_reconf_remove_listen Apr 26 05:56:30 192.168.122.209 [49940.560243] [tdb] Start Tempesta DB Apr 26 05:56:30 192.168.122.209 [49940.705988] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:56:31 192.168.122.209 [49942.010835] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49942.010835] Maybe that's fine, but it's worth checking the [49942.010835] config - if there is no relations between the [49942.010835] names, then host name confusion attack is possible. Apr 26 05:56:31 192.168.122.209 [49942.098940] [tempesta fw] Warning: TLS: no HTTPS listener set, configuration is ignored. Apr 26 05:56:31 192.168.122.209 [49942.121703] [tempesta fw] Configuration processing is completed. Apr 26 05:56:31 192.168.122.209 [49942.173285] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:56:32 192.168.122.209 [49942.580774] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:56:32 192.168.122.209 [49942.607463] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:56:32 192.168.122.209 [49942.633582] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:56:32 192.168.122.209 [49942.697565] [tempesta fw] Open listen socket on: 0.0.0.0:444 Apr 26 05:56:32 192.168.122.209 [49942.699417] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:56:32 192.168.122.209 [49942.737557] [tempesta fw] Tempesta FW is ready Apr 26 05:56:32 192.168.122.209 [49943.226913] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:56:32 192.168.122.209 [49943.270612] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49943.270612] Maybe that's fine, but it's worth checking the [49943.270612] config - if there is no relations between the [49943.270612] names, then host name confusion attack is possible. Apr 26 05:56:32 192.168.122.209 [49943.358641] [tempesta fw] Warning: TLS: no HTTPS listener set, configuration is ignored. Apr 26 05:56:32 192.168.122.209 [49943.377739] [tempesta fw] Configuration processing is completed. Apr 26 05:56:33 192.168.122.209 [49943.637895] [tempesta fw] Tempesta FW is ready Apr 26 05:56:33 192.168.122.209 [49944.121966] [tdb] Close table 'client0.tdb' Apr 26 05:56:33 192.168.122.209 [49944.300853] [tdb] Close table 'sessions0.tdb' Apr 26 05:56:37 192.168.122.209 [49947.537917] [tdb] Close table 'cache0.tdb' Apr 26 05:56:37 192.168.122.209 [49947.783983] [tdb] Close table 'filter0.tdb' Apr 26 05:56:37 192.168.122.209 [49947.784414] [tempesta fw] modules are stopped Apr 26 05:56:37 192.168.122.209 [49947.987611] [tempesta fw] exiting... Apr 26 05:56:37 192.168.122.209 [49948.130107] [tdb] Shutdown Tempesta DB Apr 26 05:56:37 192.168.122.209 [49948.342528] End test: t_reconf.test_reconf_base.TestListenReconfHttp.test_reconf_remove_listen Apr 26 05:56:37 192.168.122.209 [49948.357335] Start test: t_reconf.test_reconf_base.TestListenReconfHttps.test_reconf_add_listen Apr 26 05:56:38 192.168.122.209 [49949.384592] [tdb] Start Tempesta DB Apr 26 05:56:39 192.168.122.209 [49949.506993] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:56:40 192.168.122.209 [49950.766765] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49950.766765] Maybe that's fine, but it's worth checking the [49950.766765] config - if there is no relations between the [49950.766765] names, then host name confusion attack is possible. Apr 26 05:56:40 192.168.122.209 [49950.881795] [tempesta fw] Configuration processing is completed. Apr 26 05:56:40 192.168.122.209 [49950.941240] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:56:40 192.168.122.209 [49951.358188] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:56:40 192.168.122.209 [49951.384198] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:56:40 192.168.122.209 [49951.411768] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:56:41 192.168.122.209 [49951.485787] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:56:41 192.168.122.209 [49951.529651] [tempesta fw] Tempesta FW is ready Apr 26 05:56:41 192.168.122.209 [49952.019072] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:56:41 192.168.122.209 [49952.090994] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49952.090994] Maybe that's fine, but it's worth checking the [49952.090994] config - if there is no relations between the [49952.090994] names, then host name confusion attack is possible. Apr 26 05:56:41 192.168.122.209 [49952.205787] [tempesta fw] Configuration processing is completed. Apr 26 05:56:42 192.168.122.209 [49952.441841] [tempesta fw] Open listen socket on: 0.0.0.0:444 Apr 26 05:56:42 192.168.122.209 [49952.498053] [tempesta fw] Tempesta FW is ready Apr 26 05:56:42 192.168.122.209 [49953.001390] [tdb] Close table 'client0.tdb' Apr 26 05:56:42 192.168.122.209 [49953.199133] [tdb] Close table 'sessions0.tdb' Apr 26 05:56:45 192.168.122.209 [49956.349028] [tdb] Close table 'cache0.tdb' Apr 26 05:56:46 192.168.122.209 [49956.607121] [tdb] Close table 'filter0.tdb' Apr 26 05:56:46 192.168.122.209 [49956.607568] [tempesta fw] modules are stopped Apr 26 05:56:46 192.168.122.209 [49956.789743] [tempesta fw] exiting... Apr 26 05:56:46 192.168.122.209 [49956.920761] [tdb] Shutdown Tempesta DB Apr 26 05:56:46 192.168.122.209 [49957.123824] End test: t_reconf.test_reconf_base.TestListenReconfHttps.test_reconf_add_listen Apr 26 05:56:46 192.168.122.209 [49957.135949] Start test: t_reconf.test_reconf_base.TestListenReconfHttps.test_reconf_ip_default_to_ipv4_port_default Apr 26 05:56:47 192.168.122.209 [49958.182569] [tdb] Start Tempesta DB Apr 26 05:56:47 192.168.122.209 [49958.326318] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:56:49 192.168.122.209 [49959.559726] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49959.559726] Maybe that's fine, but it's worth checking the [49959.559726] config - if there is no relations between the [49959.559726] names, then host name confusion attack is possible. Apr 26 05:56:49 192.168.122.209 [49959.650596] [tempesta fw] Warning: TLS: no HTTPS listener set, configuration is ignored. Apr 26 05:56:49 192.168.122.209 [49959.669871] [tempesta fw] Configuration processing is completed. Apr 26 05:56:49 192.168.122.209 [49959.725453] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:56:49 192.168.122.209 [49960.149705] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:56:49 192.168.122.209 [49960.209118] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:56:49 192.168.122.209 [49960.237838] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:56:49 192.168.122.209 [49960.285766] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:56:49 192.168.122.209 [49960.333746] [tempesta fw] Tempesta FW is ready Apr 26 05:56:50 192.168.122.209 [49960.786571] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:56:50 192.168.122.209 [49960.834828] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49960.834828] Maybe that's fine, but it's worth checking the [49960.834828] config - if there is no relations between the [49960.834828] names, then host name confusion attack is possible. Apr 26 05:56:50 192.168.122.209 [49960.941896] [tempesta fw] Configuration processing is completed. Apr 26 05:56:50 192.168.122.209 [49961.162031] [tempesta fw] Open listen socket on: 127.0.0.1 Apr 26 05:56:50 192.168.122.209 [49961.242245] [tempesta fw] Tempesta FW is ready Apr 26 05:56:51 192.168.122.209 [49961.704300] [tdb] Close table 'client0.tdb' Apr 26 05:56:51 192.168.122.209 [49961.942985] [tdb] Close table 'sessions0.tdb' Apr 26 05:56:54 192.168.122.209 [49965.234954] [tdb] Close table 'cache0.tdb' Apr 26 05:56:55 192.168.122.209 [49965.488088] [tdb] Close table 'filter0.tdb' Apr 26 05:56:55 192.168.122.209 [49965.488536] [tempesta fw] modules are stopped Apr 26 05:56:55 192.168.122.209 [49965.686817] [tempesta fw] exiting... Apr 26 05:56:55 192.168.122.209 [49965.827044] [tdb] Shutdown Tempesta DB Apr 26 05:56:55 192.168.122.209 [49966.022049] End test: t_reconf.test_reconf_base.TestListenReconfHttps.test_reconf_ip_default_to_ipv4_port_default Apr 26 05:56:55 192.168.122.209 [49966.034382] Start test: t_reconf.test_reconf_base.TestListenReconfHttps.test_reconf_ip_ipv4_to_ipv4_port_443 Apr 26 05:56:56 192.168.122.209 [49967.081821] [tdb] Start Tempesta DB Apr 26 05:56:56 192.168.122.209 [49967.222153] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:56:58 192.168.122.209 [49968.470525] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49968.470525] Maybe that's fine, but it's worth checking the [49968.470525] config - if there is no relations between the [49968.470525] names, then host name confusion attack is possible. Apr 26 05:56:58 192.168.122.209 [49968.573977] [tempesta fw] Configuration processing is completed. Apr 26 05:56:58 192.168.122.209 [49968.625399] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:56:58 192.168.122.209 [49969.049680] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:56:58 192.168.122.209 [49969.075950] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:56:58 192.168.122.209 [49969.110040] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:56:58 192.168.122.209 [49969.165923] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 05:56:58 192.168.122.209 [49969.221879] [tempesta fw] Tempesta FW is ready Apr 26 05:56:59 192.168.122.209 [49969.704563] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:56:59 192.168.122.209 [49969.755233] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49969.755233] Maybe that's fine, but it's worth checking the [49969.755233] config - if there is no relations between the [49969.755233] names, then host name confusion attack is possible. Apr 26 05:56:59 192.168.122.209 [49969.870037] [tempesta fw] Configuration processing is completed. Apr 26 05:56:59 192.168.122.209 [49970.086207] [tempesta fw] Open listen socket on: 127.0.1.100:443 Apr 26 05:56:59 192.168.122.209 [49970.134313] [tempesta fw] Tempesta FW is ready Apr 26 05:57:00 192.168.122.209 [49970.655729] [tdb] Close table 'client0.tdb' Apr 26 05:57:00 192.168.122.209 [49970.843365] [tdb] Close table 'sessions0.tdb' Apr 26 05:57:03 192.168.122.209 [49974.094195] [tdb] Close table 'cache0.tdb' Apr 26 05:57:03 192.168.122.209 [49974.331972] [tdb] Close table 'filter0.tdb' Apr 26 05:57:03 192.168.122.209 [49974.332410] [tempesta fw] modules are stopped Apr 26 05:57:04 192.168.122.209 [49974.552520] [tempesta fw] exiting... Apr 26 05:57:04 192.168.122.209 [49974.690065] [tdb] Shutdown Tempesta DB Apr 26 05:57:04 192.168.122.209 [49974.931832] End test: t_reconf.test_reconf_base.TestListenReconfHttps.test_reconf_ip_ipv4_to_ipv4_port_443 Apr 26 05:57:04 192.168.122.209 [49974.940972] Start test: t_reconf.test_reconf_base.TestListenReconfHttps.test_reconf_ip_ipv4_to_ipv4_port_default Apr 26 05:57:05 192.168.122.209 [49975.994437] [tdb] Start Tempesta DB Apr 26 05:57:05 192.168.122.209 [49976.142495] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:57:06 192.168.122.209 [49977.403056] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49977.403056] Maybe that's fine, but it's worth checking the [49977.403056] config - if there is no relations between the [49977.403056] names, then host name confusion attack is possible. Apr 26 05:57:07 192.168.122.209 [49977.510242] [tempesta fw] Configuration processing is completed. Apr 26 05:57:07 192.168.122.209 [49977.559446] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:57:07 192.168.122.209 [49977.983397] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:57:07 192.168.122.209 [49978.039965] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:57:07 192.168.122.209 [49978.067058] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:57:07 192.168.122.209 [49978.114003] [tempesta fw] Open listen socket on: 127.0.0.1 Apr 26 05:57:07 192.168.122.209 [49978.165979] [tempesta fw] Tempesta FW is ready Apr 26 05:57:08 192.168.122.209 [49978.617670] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:57:08 192.168.122.209 [49978.662597] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49978.662597] Maybe that's fine, but it's worth checking the [49978.662597] config - if there is no relations between the [49978.662597] names, then host name confusion attack is possible. Apr 26 05:57:08 192.168.122.209 [49978.786079] [tempesta fw] Configuration processing is completed. Apr 26 05:57:08 192.168.122.209 [49979.006142] [tempesta fw] Open listen socket on: 127.0.1.100 Apr 26 05:57:08 192.168.122.209 [49979.062413] [tempesta fw] Tempesta FW is ready Apr 26 05:57:09 192.168.122.209 [49979.557931] [tdb] Close table 'client0.tdb' Apr 26 05:57:09 192.168.122.209 [49979.759679] [tdb] Close table 'sessions0.tdb' Apr 26 05:57:12 192.168.122.209 [49982.992495] [tdb] Close table 'cache0.tdb' Apr 26 05:57:12 192.168.122.209 [49983.230860] [tdb] Close table 'filter0.tdb' Apr 26 05:57:12 192.168.122.209 [49983.231305] [tempesta fw] modules are stopped Apr 26 05:57:12 192.168.122.209 [49983.433034] [tempesta fw] exiting... Apr 26 05:57:13 192.168.122.209 [49983.568883] [tdb] Shutdown Tempesta DB Apr 26 05:57:13 192.168.122.209 [49983.786543] End test: t_reconf.test_reconf_base.TestListenReconfHttps.test_reconf_ip_ipv4_to_ipv4_port_default Apr 26 05:57:13 192.168.122.209 [49983.796263] Start test: t_reconf.test_reconf_base.TestListenReconfHttps.test_reconf_port Apr 26 05:57:14 192.168.122.209 [49984.864304] [tdb] Start Tempesta DB Apr 26 05:57:14 192.168.122.209 [49985.012476] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:57:15 192.168.122.209 [49986.255326] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49986.255326] Maybe that's fine, but it's worth checking the [49986.255326] config - if there is no relations between the [49986.255326] names, then host name confusion attack is possible. Apr 26 05:57:15 192.168.122.209 [49986.358186] [tempesta fw] Configuration processing is completed. Apr 26 05:57:15 192.168.122.209 [49986.409813] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:57:16 192.168.122.209 [49986.831470] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:57:16 192.168.122.209 [49986.870111] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:57:16 192.168.122.209 [49986.910114] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:57:16 192.168.122.209 [49986.950089] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:57:16 192.168.122.209 [49987.002096] [tempesta fw] Tempesta FW is ready Apr 26 05:57:16 192.168.122.209 [49987.425856] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:57:17 192.168.122.209 [49987.483318] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49987.483318] Maybe that's fine, but it's worth checking the [49987.483318] config - if there is no relations between the [49987.483318] names, then host name confusion attack is possible. Apr 26 05:57:17 192.168.122.209 [49987.610122] [tempesta fw] Configuration processing is completed. Apr 26 05:57:17 192.168.122.209 [49987.842452] [tempesta fw] Open listen socket on: 0.0.0.0:4433 Apr 26 05:57:17 192.168.122.209 [49987.898615] [tempesta fw] Tempesta FW is ready Apr 26 05:57:17 192.168.122.209 [49988.387066] [tdb] Close table 'client0.tdb' Apr 26 05:57:18 192.168.122.209 [49988.573500] [tdb] Close table 'sessions0.tdb' Apr 26 05:57:21 192.168.122.209 [49991.807898] [tdb] Close table 'cache0.tdb' Apr 26 05:57:21 192.168.122.209 [49992.070983] [tdb] Close table 'filter0.tdb' Apr 26 05:57:21 192.168.122.209 [49992.071414] [tempesta fw] modules are stopped Apr 26 05:57:21 192.168.122.209 [49992.259466] [tempesta fw] exiting... Apr 26 05:57:21 192.168.122.209 [49992.418603] [tdb] Shutdown Tempesta DB Apr 26 05:57:22 192.168.122.209 [49992.639721] End test: t_reconf.test_reconf_base.TestListenReconfHttps.test_reconf_port Apr 26 05:57:22 192.168.122.209 [49992.661746] Start test: t_reconf.test_reconf_base.TestListenReconfHttps.test_reconf_proto_h2 Apr 26 05:57:23 192.168.122.209 [49993.725362] [tdb] Start Tempesta DB Apr 26 05:57:23 192.168.122.209 [49993.872117] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:57:24 192.168.122.209 [49995.134615] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49995.134615] Maybe that's fine, but it's worth checking the [49995.134615] config - if there is no relations between the [49995.134615] names, then host name confusion attack is possible. Apr 26 05:57:24 192.168.122.209 [49995.246588] [tempesta fw] Configuration processing is completed. Apr 26 05:57:24 192.168.122.209 [49995.305215] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:57:25 192.168.122.209 [49995.765518] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:57:25 192.168.122.209 [49995.824524] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:57:25 192.168.122.209 [49995.852951] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:57:25 192.168.122.209 [49995.926216] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:57:25 192.168.122.209 [49995.970199] [tempesta fw] Tempesta FW is ready Apr 26 05:57:26 192.168.122.209 [49996.473441] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:57:26 192.168.122.209 [49996.523479] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [49996.523479] Maybe that's fine, but it's worth checking the [49996.523479] config - if there is no relations between the [49996.523479] names, then host name confusion attack is possible. Apr 26 05:57:26 192.168.122.209 [49996.662329] [tempesta fw] Configuration processing is completed. Apr 26 05:57:26 192.168.122.209 [49996.870420] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:57:26 192.168.122.209 [49996.918656] [tempesta fw] Tempesta FW is ready Apr 26 05:57:26 192.168.122.209 [49997.377355] [tdb] Close table 'client0.tdb' Apr 26 05:57:27 192.168.122.209 [49997.589051] [tdb] Close table 'sessions0.tdb' Apr 26 05:57:30 192.168.122.209 [50000.783610] [tdb] Close table 'cache0.tdb' Apr 26 05:57:30 192.168.122.209 [50001.037683] [tdb] Close table 'filter0.tdb' Apr 26 05:57:30 192.168.122.209 [50001.038255] [tempesta fw] modules are stopped Apr 26 05:57:30 192.168.122.209 [50001.221914] [tempesta fw] exiting... Apr 26 05:57:30 192.168.122.209 [50001.364199] [tdb] Shutdown Tempesta DB Apr 26 05:57:31 192.168.122.209 [50001.555072] End test: t_reconf.test_reconf_base.TestListenReconfHttps.test_reconf_proto_h2 Apr 26 05:57:31 192.168.122.209 [50001.568507] Start test: t_reconf.test_reconf_base.TestListenReconfHttps.test_reconf_proto_h2_https Apr 26 05:57:32 192.168.122.209 [50002.680654] [tdb] Start Tempesta DB Apr 26 05:57:32 192.168.122.209 [50002.833201] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:57:33 192.168.122.209 [50004.099575] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50004.099575] Maybe that's fine, but it's worth checking the [50004.099575] config - if there is no relations between the [50004.099575] names, then host name confusion attack is possible. Apr 26 05:57:33 192.168.122.209 [50004.190429] [tempesta fw] Configuration processing is completed. Apr 26 05:57:33 192.168.122.209 [50004.242366] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:57:34 192.168.122.209 [50004.688497] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:57:34 192.168.122.209 [50004.716830] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:57:34 192.168.122.209 [50004.754518] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:57:34 192.168.122.209 [50004.802425] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:57:34 192.168.122.209 [50004.842368] [tempesta fw] Tempesta FW is ready Apr 26 05:57:34 192.168.122.209 [50005.365633] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:57:34 192.168.122.209 [50005.403634] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50005.403634] Maybe that's fine, but it's worth checking the [50005.403634] config - if there is no relations between the [50005.403634] names, then host name confusion attack is possible. Apr 26 05:57:35 192.168.122.209 [50005.518366] [tempesta fw] Configuration processing is completed. Apr 26 05:57:35 192.168.122.209 [50005.734582] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:57:35 192.168.122.209 [50005.790773] [tempesta fw] Tempesta FW is ready Apr 26 05:57:35 192.168.122.209 [50006.250015] [tdb] Close table 'client0.tdb' Apr 26 05:57:36 192.168.122.209 [50006.461153] [tdb] Close table 'sessions0.tdb' Apr 26 05:57:39 192.168.122.209 [50009.656241] [tdb] Close table 'cache0.tdb' Apr 26 05:57:39 192.168.122.209 [50009.880416] [tdb] Close table 'filter0.tdb' Apr 26 05:57:39 192.168.122.209 [50009.880853] [tempesta fw] modules are stopped Apr 26 05:57:39 192.168.122.209 [50010.054891] [tempesta fw] exiting... Apr 26 05:57:39 192.168.122.209 [50010.194826] [tdb] Shutdown Tempesta DB Apr 26 05:57:39 192.168.122.209 [50010.403824] End test: t_reconf.test_reconf_base.TestListenReconfHttps.test_reconf_proto_h2_https Apr 26 05:57:39 192.168.122.209 [50010.409996] Start test: t_reconf.test_reconf_base.TestListenReconfHttps.test_reconf_proto_http Apr 26 05:57:40 192.168.122.209 [50011.410622] [tdb] Start Tempesta DB Apr 26 05:57:41 192.168.122.209 [50011.556930] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:57:42 192.168.122.209 [50012.815784] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50012.815784] Maybe that's fine, but it's worth checking the [50012.815784] config - if there is no relations between the [50012.815784] names, then host name confusion attack is possible. Apr 26 05:57:42 192.168.122.209 [50012.922548] [tempesta fw] Configuration processing is completed. Apr 26 05:57:42 192.168.122.209 [50012.973567] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:57:42 192.168.122.209 [50013.377814] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:57:42 192.168.122.209 [50013.433815] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:57:43 192.168.122.209 [50013.461040] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:57:43 192.168.122.209 [50013.510474] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:57:43 192.168.122.209 [50013.558436] [tempesta fw] Tempesta FW is ready Apr 26 05:57:43 192.168.122.209 [50013.953139] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:57:43 192.168.122.209 [50013.991098] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50013.991098] Maybe that's fine, but it's worth checking the [50013.991098] config - if there is no relations between the [50013.991098] names, then host name confusion attack is possible. Apr 26 05:57:43 192.168.122.209 [50014.110597] [tempesta fw] Configuration processing is completed. Apr 26 05:57:43 192.168.122.209 [50014.302440] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:57:43 192.168.122.209 [50014.362585] [tempesta fw] Tempesta FW is ready Apr 26 05:57:44 192.168.122.209 [50014.883945] [tdb] Close table 'client0.tdb' Apr 26 05:57:44 192.168.122.209 [50015.126061] [tdb] Close table 'sessions0.tdb' Apr 26 05:57:47 192.168.122.209 [50018.380896] [tdb] Close table 'cache0.tdb' Apr 26 05:57:48 192.168.122.209 [50018.630405] [tdb] Close table 'filter0.tdb' Apr 26 05:57:48 192.168.122.209 [50018.630839] [tempesta fw] modules are stopped Apr 26 05:57:48 192.168.122.209 [50018.827365] [tempesta fw] exiting... Apr 26 05:57:48 192.168.122.209 [50018.969001] [tdb] Shutdown Tempesta DB Apr 26 05:57:48 192.168.122.209 [50019.177560] End test: t_reconf.test_reconf_base.TestListenReconfHttps.test_reconf_proto_http Apr 26 05:57:48 192.168.122.209 [50019.195956] Start test: t_reconf.test_reconf_base.TestListenReconfHttps.test_reconf_proto_https Apr 26 05:57:49 192.168.122.209 [50020.281041] [tdb] Start Tempesta DB Apr 26 05:57:49 192.168.122.209 [50020.405782] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:57:51 192.168.122.209 [50021.776010] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50021.776010] Maybe that's fine, but it's worth checking the [50021.776010] config - if there is no relations between the [50021.776010] names, then host name confusion attack is possible. Apr 26 05:57:51 192.168.122.209 [50021.878767] [tempesta fw] Configuration processing is completed. Apr 26 05:57:51 192.168.122.209 [50021.947051] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:57:51 192.168.122.209 [50022.432393] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:57:52 192.168.122.209 [50022.466204] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:57:52 192.168.122.209 [50022.508113] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:57:52 192.168.122.209 [50022.566552] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:57:52 192.168.122.209 [50022.606555] [tempesta fw] Tempesta FW is ready Apr 26 05:57:52 192.168.122.209 [50023.069385] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:57:52 192.168.122.209 [50023.129057] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50023.129057] Maybe that's fine, but it's worth checking the [50023.129057] config - if there is no relations between the [50023.129057] names, then host name confusion attack is possible. Apr 26 05:57:52 192.168.122.209 [50023.250610] [tempesta fw] Configuration processing is completed. Apr 26 05:57:53 192.168.122.209 [50023.526982] [tempesta fw] Tempesta FW is ready Apr 26 05:57:53 192.168.122.209 [50023.976586] [tdb] Close table 'client0.tdb' Apr 26 05:57:53 192.168.122.209 [50024.179192] [tdb] Close table 'sessions0.tdb' Apr 26 05:57:56 192.168.122.209 [50027.316182] [tdb] Close table 'cache0.tdb' Apr 26 05:57:57 192.168.122.209 [50027.550694] [tdb] Close table 'filter0.tdb' Apr 26 05:57:57 192.168.122.209 [50027.551133] [tempesta fw] modules are stopped Apr 26 05:57:57 192.168.122.209 [50027.751138] [tempesta fw] exiting... Apr 26 05:57:57 192.168.122.209 [50027.863517] [tdb] Shutdown Tempesta DB Apr 26 05:57:57 192.168.122.209 [50028.044428] End test: t_reconf.test_reconf_base.TestListenReconfHttps.test_reconf_proto_https Apr 26 05:57:57 192.168.122.209 [50028.055548] Start test: t_reconf.test_reconf_base.TestListenReconfHttps.test_reconf_remove_listen Apr 26 05:57:58 192.168.122.209 [50029.070135] [tdb] Start Tempesta DB Apr 26 05:57:58 192.168.122.209 [50029.210489] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:58:00 192.168.122.209 [50030.484021] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50030.484021] Maybe that's fine, but it's worth checking the [50030.484021] config - if there is no relations between the [50030.484021] names, then host name confusion attack is possible. Apr 26 05:58:00 192.168.122.209 [50030.598795] [tempesta fw] Configuration processing is completed. Apr 26 05:58:00 192.168.122.209 [50030.652136] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:58:00 192.168.122.209 [50031.057881] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:58:00 192.168.122.209 [50031.114251] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:58:00 192.168.122.209 [50031.141175] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:58:00 192.168.122.209 [50031.182709] [tempesta fw] Open listen socket on: 0.0.0.0:444 Apr 26 05:58:00 192.168.122.209 [50031.184444] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:58:00 192.168.122.209 [50031.226642] [tempesta fw] Tempesta FW is ready Apr 26 05:58:01 192.168.122.209 [50031.685121] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:58:01 192.168.122.209 [50031.744113] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50031.744113] Maybe that's fine, but it's worth checking the [50031.744113] config - if there is no relations between the [50031.744113] names, then host name confusion attack is possible. Apr 26 05:58:01 192.168.122.209 [50031.866731] [tempesta fw] Configuration processing is completed. Apr 26 05:58:01 192.168.122.209 [50032.151049] [tempesta fw] Tempesta FW is ready Apr 26 05:58:02 192.168.122.209 [50032.640087] [tdb] Close table 'client0.tdb' Apr 26 05:58:02 192.168.122.209 [50032.815395] [tdb] Close table 'sessions0.tdb' Apr 26 05:58:05 192.168.122.209 [50036.130562] [tdb] Close table 'cache0.tdb' Apr 26 05:58:05 192.168.122.209 [50036.371414] [tdb] Close table 'filter0.tdb' Apr 26 05:58:05 192.168.122.209 [50036.371836] [tempesta fw] modules are stopped Apr 26 05:58:06 192.168.122.209 [50036.591360] [tempesta fw] exiting... Apr 26 05:58:06 192.168.122.209 [50036.724763] [tdb] Shutdown Tempesta DB Apr 26 05:58:06 192.168.122.209 [50036.967988] End test: t_reconf.test_reconf_base.TestListenReconfHttps.test_reconf_remove_listen Apr 26 05:58:06 192.168.122.209 [50036.979538] Start test: t_reconf.test_reconf_base.TestLocationReconf.test_add_location Apr 26 05:58:07 192.168.122.209 [50038.020978] [tdb] Start Tempesta DB Apr 26 05:58:07 192.168.122.209 [50038.163966] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:58:09 192.168.122.209 [50039.524484] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50039.524484] Maybe that's fine, but it's worth checking the [50039.524484] config - if there is no relations between the [50039.524484] names, then host name confusion attack is possible. Apr 26 05:58:09 192.168.122.209 [50039.659244] [tempesta fw] Configuration processing is completed. Apr 26 05:58:09 192.168.122.209 [50039.721208] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:58:09 192.168.122.209 [50040.157987] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:58:09 192.168.122.209 [50040.185655] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:58:09 192.168.122.209 [50040.221831] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:58:09 192.168.122.209 [50040.262812] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:58:09 192.168.122.209 [50040.302845] [tempesta fw] Tempesta FW is ready Apr 26 05:58:10 192.168.122.209 [50040.895230] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:58:10 192.168.122.209 [50040.919867] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50040.919867] Maybe that's fine, but it's worth checking the [50040.919867] config - if there is no relations between the [50040.919867] names, then host name confusion attack is possible. Apr 26 05:58:10 192.168.122.209 [50041.126874] [tempesta fw] Configuration processing is completed. Apr 26 05:58:10 192.168.122.209 [50041.403289] [tempesta fw] Tempesta FW is ready Apr 26 05:58:11 192.168.122.209 [50041.867942] [tdb] Close table 'client0.tdb' Apr 26 05:58:11 192.168.122.209 [50042.084575] [tdb] Close table 'sessions0.tdb' Apr 26 05:58:14 192.168.122.209 [50045.307447] [tdb] Close table 'cache0.tdb' Apr 26 05:58:15 192.168.122.209 [50045.539970] [tdb] Close table 'filter0.tdb' Apr 26 05:58:15 192.168.122.209 [50045.540417] [tempesta fw] modules are stopped Apr 26 05:58:15 192.168.122.209 [50045.755557] [tempesta fw] exiting... Apr 26 05:58:15 192.168.122.209 [50045.903729] [tdb] Shutdown Tempesta DB Apr 26 05:58:15 192.168.122.209 [50046.121946] End test: t_reconf.test_reconf_base.TestLocationReconf.test_add_location Apr 26 05:58:15 192.168.122.209 [50046.146590] Start test: t_reconf.test_reconf_base.TestLocationReconf.test_remove_location Apr 26 05:58:16 192.168.122.209 [50047.192705] [tdb] Start Tempesta DB Apr 26 05:58:16 192.168.122.209 [50047.325652] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:58:18 192.168.122.209 [50048.732704] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50048.732704] Maybe that's fine, but it's worth checking the [50048.732704] config - if there is no relations between the [50048.732704] names, then host name confusion attack is possible. Apr 26 05:58:18 192.168.122.209 [50048.874971] [tempesta fw] Configuration processing is completed. Apr 26 05:58:18 192.168.122.209 [50048.927017] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:58:18 192.168.122.209 [50049.341409] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:58:18 192.168.122.209 [50049.420418] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:58:19 192.168.122.209 [50049.446101] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:58:19 192.168.122.209 [50049.490933] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 05:58:19 192.168.122.209 [50049.530904] [tempesta fw] Tempesta FW is ready Apr 26 05:58:19 192.168.122.209 [50050.108475] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:58:19 192.168.122.209 [50050.124040] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50050.124040] Maybe that's fine, but it's worth checking the [50050.124040] config - if there is no relations between the [50050.124040] names, then host name confusion attack is possible. Apr 26 05:58:19 192.168.122.209 [50050.270969] [tempesta fw] Configuration processing is completed. Apr 26 05:58:20 192.168.122.209 [50050.515420] [tempesta fw] Tempesta FW is ready Apr 26 05:58:20 192.168.122.209 [50050.991472] [tdb] Close table 'client0.tdb' Apr 26 05:58:20 192.168.122.209 [50051.199161] [tdb] Close table 'sessions0.tdb' Apr 26 05:58:23 192.168.122.209 [50054.369611] [tdb] Close table 'cache0.tdb' Apr 26 05:58:24 192.168.122.209 [50054.601339] [tdb] Close table 'filter0.tdb' Apr 26 05:58:24 192.168.122.209 [50054.601772] [tempesta fw] modules are stopped Apr 26 05:58:24 192.168.122.209 [50054.812689] [tempesta fw] exiting... Apr 26 05:58:24 192.168.122.209 [50054.942013] [tdb] Shutdown Tempesta DB Apr 26 05:58:24 192.168.122.209 [50055.164521] End test: t_reconf.test_reconf_base.TestLocationReconf.test_remove_location Apr 26 05:58:24 192.168.122.209 [50055.179253] Start test: t_reconf.test_reconf_base.TestNegativeReconf.test_negative_reconf_http_chain Apr 26 05:58:25 192.168.122.209 [50056.167459] [tdb] Start Tempesta DB Apr 26 05:58:25 192.168.122.209 [50056.331563] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:58:27 192.168.122.209 [50057.863034] [tempesta fw] Configuration processing is completed. Apr 26 05:58:27 192.168.122.209 [50057.913896] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:58:27 192.168.122.209 [50058.324871] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:58:27 192.168.122.209 [50058.350666] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:58:27 192.168.122.209 [50058.384379] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:58:28 192.168.122.209 [50058.479324] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:58:28 192.168.122.209 [50058.522977] [tempesta fw] Tempesta FW is ready Apr 26 05:58:28 192.168.122.209 [50059.168561] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:58:28 192.168.122.209 [50059.255394] [tempesta fw] ERROR: parser error Apr 26 05:58:28 192.168.122.209 [50059.256675] [tempesta fw] ERROR: configuration parsing error: [50059.256675] 12: cookie "__cookie" == "value_1"; [50059.256675] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 05:58:28 192.168.122.209 [50059.261003] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 05:58:29 192.168.122.209 [50060.322328] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 05:58:29 192.168.122.209 [50060.322460] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 05:58:29 192.168.122.209 [50060.322526] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 05:58:29 192.168.122.209 [50060.322595] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 05:58:29 192.168.122.209 [50060.322697] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 05:58:29 192.168.122.209 [50060.322751] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 05:58:29 192.168.122.209 [50060.322833] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 05:58:29 192.168.122.209 [50060.322932] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 05:58:29 192.168.122.209 [50060.323030] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 05:58:29 192.168.122.209 [50060.323053] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 05:58:34 192.168.122.209 [50064.727960] [tdb] Close table 'client0.tdb' Apr 26 05:58:34 192.168.122.209 [50064.905581] [tdb] Close table 'sessions0.tdb' Apr 26 05:58:37 192.168.122.209 [50068.126567] [tdb] Close table 'cache0.tdb' Apr 26 05:58:37 192.168.122.209 [50068.351746] [tdb] Close table 'filter0.tdb' Apr 26 05:58:37 192.168.122.209 [50068.352190] net_ratelimit: 22 callbacks suppressed Apr 26 05:58:37 192.168.122.209 [50068.352192] [tempesta fw] modules are stopped Apr 26 05:58:38 192.168.122.209 [50068.535498] [tempesta fw] exiting... Apr 26 05:58:38 192.168.122.209 [50068.662924] [tdb] Shutdown Tempesta DB Apr 26 05:58:38 192.168.122.209 [50068.890928] End test: t_reconf.test_reconf_base.TestNegativeReconf.test_negative_reconf_http_chain Apr 26 05:58:38 192.168.122.209 [50068.907435] Start test: t_reconf.test_reconf_base.TestNegativeReconf.test_negative_reconf_location Apr 26 05:58:39 192.168.122.209 [50069.855725] [tdb] Start Tempesta DB Apr 26 05:58:39 192.168.122.209 [50069.985895] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:58:40 192.168.122.209 [50071.143646] [tempesta fw] Configuration processing is completed. Apr 26 05:58:40 192.168.122.209 [50071.195607] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:58:41 192.168.122.209 [50071.608027] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:58:41 192.168.122.209 [50071.665795] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:58:41 192.168.122.209 [50071.692227] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:58:41 192.168.122.209 [50071.759138] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:58:41 192.168.122.209 [50071.815166] [tempesta fw] Tempesta FW is ready Apr 26 05:58:41 192.168.122.209 [50072.173230] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:58:41 192.168.122.209 [50072.195287] [tempesta fw] ERROR: location: Invalid number of arguments: 0, must be == 2 Apr 26 05:58:41 192.168.122.209 [50072.196802] [tempesta fw] ERROR: configuration parsing error: [50072.196802] 3: location { [50072.196802] ^^^^^^^^^^ Apr 26 05:58:41 192.168.122.209 [50072.198955] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 05:58:47 192.168.122.209 [50078.240191] [tdb] Close table 'client0.tdb' Apr 26 05:58:48 192.168.122.209 [50078.521740] [tdb] Close table 'sessions0.tdb' Apr 26 05:58:52 192.168.122.209 [50083.100265] [tdb] Close table 'cache0.tdb' Apr 26 05:58:52 192.168.122.209 [50083.386652] [tdb] Close table 'filter0.tdb' Apr 26 05:58:52 192.168.122.209 [50083.387085] [tempesta fw] modules are stopped Apr 26 05:58:53 192.168.122.209 [50083.570856] [tempesta fw] exiting... Apr 26 05:58:53 192.168.122.209 [50083.717980] [tdb] Shutdown Tempesta DB Apr 26 05:58:53 192.168.122.209 [50083.897937] End test: t_reconf.test_reconf_base.TestNegativeReconf.test_negative_reconf_location Apr 26 05:58:53 192.168.122.209 [50083.921500] Start test: t_reconf.test_reconf_base.TestNegativeReconf.test_negative_reconf_proxy_pass Apr 26 05:58:54 192.168.122.209 [50084.993031] [tdb] Start Tempesta DB Apr 26 05:58:54 192.168.122.209 [50085.119573] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:58:56 192.168.122.209 [50086.491459] [tempesta fw] Configuration processing is completed. Apr 26 05:58:56 192.168.122.209 [50086.539381] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:58:56 192.168.122.209 [50087.022704] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:58:56 192.168.122.209 [50087.049080] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:58:56 192.168.122.209 [50087.083352] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:58:56 192.168.122.209 [50087.224417] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:58:56 192.168.122.209 [50087.265828] [tempesta fw] Tempesta FW is ready Apr 26 05:58:57 192.168.122.209 [50087.747452] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:58:57 192.168.122.209 [50087.799956] [tempesta fw] ERROR: parser error Apr 26 05:58:57 192.168.122.209 [50087.801253] [tempesta fw] ERROR: configuration parsing error: [50087.801253] 7: proxy_pass grp1 backup=; [50087.801253] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 05:58:57 192.168.122.209 [50087.805276] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 05:58:58 192.168.122.209 [50089.025847] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 05:58:58 192.168.122.209 [50089.025886] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 05:58:58 192.168.122.209 [50089.026002] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 05:58:58 192.168.122.209 [50089.026022] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 05:58:58 192.168.122.209 [50089.026128] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 05:58:58 192.168.122.209 [50089.026192] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 05:58:58 192.168.122.209 [50089.026247] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 05:58:58 192.168.122.209 [50089.026322] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 05:58:58 192.168.122.209 [50089.026359] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 05:58:58 192.168.122.209 [50089.026429] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 05:59:02 192.168.122.209 [50093.134750] [tdb] Close table 'client0.tdb' Apr 26 05:59:02 192.168.122.209 [50093.321296] [tdb] Close table 'sessions0.tdb' Apr 26 05:59:06 192.168.122.209 [50096.500018] [tdb] Close table 'cache0.tdb' Apr 26 05:59:06 192.168.122.209 [50096.760909] [tdb] Close table 'filter0.tdb' Apr 26 05:59:06 192.168.122.209 [50096.761360] net_ratelimit: 22 callbacks suppressed Apr 26 05:59:06 192.168.122.209 [50096.761362] [tempesta fw] modules are stopped Apr 26 05:59:06 192.168.122.209 [50096.973059] [tempesta fw] exiting... Apr 26 05:59:06 192.168.122.209 [50097.093069] [tdb] Shutdown Tempesta DB Apr 26 05:59:06 192.168.122.209 [50097.272868] End test: t_reconf.test_reconf_base.TestNegativeReconf.test_negative_reconf_proxy_pass Apr 26 05:59:06 192.168.122.209 [50097.300238] Start test: t_reconf.test_reconf_base.TestNegativeReconf.test_negative_reconf_server Apr 26 05:59:07 192.168.122.209 [50098.323239] [tdb] Start Tempesta DB Apr 26 05:59:08 192.168.122.209 [50098.460673] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:59:09 192.168.122.209 [50099.567960] [tempesta fw] Configuration processing is completed. Apr 26 05:59:09 192.168.122.209 [50099.621986] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:59:09 192.168.122.209 [50100.017305] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:59:09 192.168.122.209 [50100.072963] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:59:09 192.168.122.209 [50100.098695] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:59:09 192.168.122.209 [50100.183557] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:59:09 192.168.122.209 [50100.223532] [tempesta fw] Tempesta FW is ready Apr 26 05:59:10 192.168.122.209 [50100.557324] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:59:10 192.168.122.209 [50100.559309] [tempesta fw] ERROR: Invalid IP address: '127.0.0.3:8000:443' Apr 26 05:59:10 192.168.122.209 [50100.560014] [tempesta fw] ERROR: configuration parsing error: [50100.560014] 1: server 127.0.0.3:8000:443; [50100.560014] ^^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 05:59:10 192.168.122.209 [50100.561306] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 05:59:15 192.168.122.209 [50105.774980] [tdb] Close table 'client0.tdb' Apr 26 05:59:15 192.168.122.209 [50105.945979] [tdb] Close table 'sessions0.tdb' Apr 26 05:59:18 192.168.122.209 [50109.128099] [tdb] Close table 'cache0.tdb' Apr 26 05:59:18 192.168.122.209 [50109.358978] [tdb] Close table 'filter0.tdb' Apr 26 05:59:18 192.168.122.209 [50109.359439] [tempesta fw] modules are stopped Apr 26 05:59:19 192.168.122.209 [50109.555719] [tempesta fw] exiting... Apr 26 05:59:19 192.168.122.209 [50109.692767] [tdb] Shutdown Tempesta DB Apr 26 05:59:19 192.168.122.209 [50109.907205] End test: t_reconf.test_reconf_base.TestNegativeReconf.test_negative_reconf_server Apr 26 05:59:19 192.168.122.209 [50109.918453] Start test: t_reconf.test_reconf_base.TestNegativeReconf.test_negative_reconf_srv_group Apr 26 05:59:20 192.168.122.209 [50110.974641] [tdb] Start Tempesta DB Apr 26 05:59:20 192.168.122.209 [50111.125898] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:59:21 192.168.122.209 [50112.387832] [tempesta fw] Configuration processing is completed. Apr 26 05:59:22 192.168.122.209 [50112.444813] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:59:22 192.168.122.209 [50112.861747] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:59:22 192.168.122.209 [50112.887810] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:59:22 192.168.122.209 [50112.926734] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:59:22 192.168.122.209 [50112.995643] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:59:22 192.168.122.209 [50113.051675] [tempesta fw] Tempesta FW is ready Apr 26 05:59:22 192.168.122.209 [50113.426461] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:59:22 192.168.122.209 [50113.429625] [tempesta fw] ERROR: srv_group: Invalid number of arguments: 2, must be == 1 Apr 26 05:59:22 192.168.122.209 [50113.430846] [tempesta fw] ERROR: configuration parsing error: [50113.430846] 1: srv_group default grp2 { [50113.430846] ^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 05:59:22 192.168.122.209 [50113.433033] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 05:59:28 192.168.122.209 [50118.640219] [tdb] Close table 'client0.tdb' Apr 26 05:59:28 192.168.122.209 [50118.820533] [tdb] Close table 'sessions0.tdb' Apr 26 05:59:31 192.168.122.209 [50122.044089] [tdb] Close table 'cache0.tdb' Apr 26 05:59:31 192.168.122.209 [50122.278008] [tdb] Close table 'filter0.tdb' Apr 26 05:59:31 192.168.122.209 [50122.278440] [tempesta fw] modules are stopped Apr 26 05:59:32 192.168.122.209 [50122.438896] [tempesta fw] exiting... Apr 26 05:59:32 192.168.122.209 [50122.588889] [tdb] Shutdown Tempesta DB Apr 26 05:59:32 192.168.122.209 [50122.794209] End test: t_reconf.test_reconf_base.TestNegativeReconf.test_negative_reconf_srv_group Apr 26 05:59:32 192.168.122.209 [50122.812563] Start test: t_reconf.test_reconf_base.TestNegativeReconf.test_negative_reconf_srv_group_options Apr 26 05:59:33 192.168.122.209 [50123.821654] [tdb] Start Tempesta DB Apr 26 05:59:33 192.168.122.209 [50123.957728] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:59:34 192.168.122.209 [50125.172277] [tempesta fw] Configuration processing is completed. Apr 26 05:59:34 192.168.122.209 [50125.226269] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:59:35 192.168.122.209 [50125.635801] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:59:35 192.168.122.209 [50125.700038] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:59:35 192.168.122.209 [50125.726379] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:59:35 192.168.122.209 [50125.803888] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:59:35 192.168.122.209 [50125.843870] [tempesta fw] Tempesta FW is ready Apr 26 05:59:35 192.168.122.209 [50126.313926] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:59:35 192.168.122.209 [50126.316233] [tempesta fw] ERROR: server_forward_retries: Invalid number of arguments: 2, must be == 1 Apr 26 05:59:35 192.168.122.209 [50126.317061] [tempesta fw] ERROR: configuration parsing error: [50126.317061] 4: server_forward_retries 1000 100; [50126.317061] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 05:59:35 192.168.122.209 [50126.318462] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 05:59:41 192.168.122.209 [50131.540550] [tdb] Close table 'client0.tdb' Apr 26 05:59:41 192.168.122.209 [50131.724738] [tdb] Close table 'sessions0.tdb' Apr 26 05:59:44 192.168.122.209 [50134.916175] [tdb] Close table 'cache0.tdb' Apr 26 05:59:44 192.168.122.209 [50135.173411] [tdb] Close table 'filter0.tdb' Apr 26 05:59:44 192.168.122.209 [50135.173850] [tempesta fw] modules are stopped Apr 26 05:59:44 192.168.122.209 [50135.324749] [tempesta fw] exiting... Apr 26 05:59:45 192.168.122.209 [50135.457916] [tdb] Shutdown Tempesta DB Apr 26 05:59:45 192.168.122.209 [50135.673553] End test: t_reconf.test_reconf_base.TestNegativeReconf.test_negative_reconf_srv_group_options Apr 26 05:59:45 192.168.122.209 [50135.686250] Start test: t_reconf.test_reconf_base.TestNegativeReconf.test_negative_reconf_vhost Apr 26 05:59:46 192.168.122.209 [50136.708490] [tdb] Start Tempesta DB Apr 26 05:59:46 192.168.122.209 [50136.853386] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 05:59:47 192.168.122.209 [50138.340149] [tempesta fw] Configuration processing is completed. Apr 26 05:59:47 192.168.122.209 [50138.390239] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 05:59:48 192.168.122.209 [50138.800933] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 05:59:48 192.168.122.209 [50138.866690] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 05:59:48 192.168.122.209 [50138.892249] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 05:59:48 192.168.122.209 [50138.956062] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 05:59:48 192.168.122.209 [50138.999968] [tempesta fw] Tempesta FW is ready Apr 26 05:59:49 192.168.122.209 [50139.552025] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 05:59:49 192.168.122.209 [50139.575050] [tempesta fw] ERROR: vhost: Invalid number of arguments: 2, must be == 1 Apr 26 05:59:49 192.168.122.209 [50139.576224] [tempesta fw] ERROR: configuration parsing error: [50139.576224] 6: vhost prefix "/" { [50139.576224] ^^^^^^^^^^^^^^^^^^ Apr 26 05:59:49 192.168.122.209 [50139.578071] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 05:59:54 192.168.122.209 [50144.829957] [tdb] Close table 'client0.tdb' Apr 26 05:59:54 192.168.122.209 [50145.024058] [tdb] Close table 'sessions0.tdb' Apr 26 05:59:57 192.168.122.209 [50148.246043] [tdb] Close table 'cache0.tdb' Apr 26 05:59:58 192.168.122.209 [50148.465947] [tdb] Close table 'filter0.tdb' Apr 26 05:59:58 192.168.122.209 [50148.466444] [tempesta fw] modules are stopped Apr 26 05:59:58 192.168.122.209 [50148.741126] [tempesta fw] exiting... Apr 26 05:59:58 192.168.122.209 [50148.882049] [tdb] Shutdown Tempesta DB Apr 26 05:59:58 192.168.122.209 [50149.098116] End test: t_reconf.test_reconf_base.TestNegativeReconf.test_negative_reconf_vhost Apr 26 05:59:58 192.168.122.209 [50149.108419] Start test: t_reconf.test_reconf_base.TestProxyPassReconf.test_reconf_backup_group Apr 26 05:59:59 192.168.122.209 [50150.223629] [tdb] Start Tempesta DB Apr 26 05:59:59 192.168.122.209 [50150.372550] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:00:01 192.168.122.209 [50152.101306] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50152.101306] Maybe that's fine, but it's worth checking the [50152.101306] config - if there is no relations between the [50152.101306] names, then host name confusion attack is possible. Apr 26 06:00:01 192.168.122.209 [50152.292308] [tempesta fw] Configuration processing is completed. Apr 26 06:00:01 192.168.122.209 [50152.343388] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:00:02 192.168.122.209 [50152.763022] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:00:02 192.168.122.209 [50152.790243] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:00:02 192.168.122.209 [50152.825197] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:00:02 192.168.122.209 [50152.916192] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:00:02 192.168.122.209 [50152.956191] [tempesta fw] Tempesta FW is ready Apr 26 06:00:03 192.168.122.209 [50153.743501] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 06:00:03 192.168.122.209 [50153.769199] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50153.769199] Maybe that's fine, but it's worth checking the [50153.769199] config - if there is no relations between the [50153.769199] names, then host name confusion attack is possible. Apr 26 06:00:03 192.168.122.209 [50154.060217] [tempesta fw] Configuration processing is completed. Apr 26 06:00:04 192.168.122.209 [50154.592690] [tempesta fw] Tempesta FW is ready Apr 26 06:00:05 192.168.122.209 [50156.162837] [tdb] Close table 'client0.tdb' Apr 26 06:00:05 192.168.122.209 [50156.354110] [tdb] Close table 'sessions0.tdb' Apr 26 06:00:09 192.168.122.209 [50159.581630] [tdb] Close table 'cache0.tdb' Apr 26 06:00:09 192.168.122.209 [50159.828844] [tdb] Close table 'filter0.tdb' Apr 26 06:00:09 192.168.122.209 [50159.829295] [tempesta fw] modules are stopped Apr 26 06:00:09 192.168.122.209 [50160.080638] [tempesta fw] exiting... Apr 26 06:00:09 192.168.122.209 [50160.197223] [tdb] Shutdown Tempesta DB Apr 26 06:00:09 192.168.122.209 [50160.420277] End test: t_reconf.test_reconf_base.TestProxyPassReconf.test_reconf_backup_group Apr 26 06:00:09 192.168.122.209 [50160.429791] Start test: t_reconf.test_reconf_base.TestProxyPassReconf.test_reconf_group Apr 26 06:00:11 192.168.122.209 [50161.531180] [tdb] Start Tempesta DB Apr 26 06:00:11 192.168.122.209 [50161.665423] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:00:12 192.168.122.209 [50163.313986] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50163.313986] Maybe that's fine, but it's worth checking the [50163.313986] config - if there is no relations between the [50163.313986] names, then host name confusion attack is possible. Apr 26 06:00:13 192.168.122.209 [50163.496408] [tempesta fw] Configuration processing is completed. Apr 26 06:00:13 192.168.122.209 [50163.551871] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:00:13 192.168.122.209 [50163.961310] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:00:13 192.168.122.209 [50164.018680] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:00:13 192.168.122.209 [50164.045126] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:00:13 192.168.122.209 [50164.124398] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:00:13 192.168.122.209 [50164.172324] [tempesta fw] Tempesta FW is ready Apr 26 06:00:14 192.168.122.209 [50164.822684] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 06:00:14 192.168.122.209 [50164.845270] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50164.845270] Maybe that's fine, but it's worth checking the [50164.845270] config - if there is no relations between the [50164.845270] names, then host name confusion attack is possible. Apr 26 06:00:14 192.168.122.209 [50165.132391] [tempesta fw] Configuration processing is completed. Apr 26 06:00:15 192.168.122.209 [50165.560843] [tempesta fw] Tempesta FW is ready Apr 26 06:00:15 192.168.122.209 [50165.621255] [tempesta fw] Warning: request has been filtered out via http table: 127.0.0.2 Apr 26 06:00:15 192.168.122.209 [50166.133856] [tdb] Close table 'client0.tdb' Apr 26 06:00:15 192.168.122.209 [50166.321730] [tdb] Close table 'sessions0.tdb' Apr 26 06:00:19 192.168.122.209 [50169.567765] [tdb] Close table 'cache0.tdb' Apr 26 06:00:19 192.168.122.209 [50169.824490] [tdb] Close table 'filter0.tdb' Apr 26 06:00:19 192.168.122.209 [50169.824929] [tempesta fw] modules are stopped Apr 26 06:00:19 192.168.122.209 [50170.055704] [tempesta fw] exiting... Apr 26 06:00:19 192.168.122.209 [50170.211725] [tdb] Shutdown Tempesta DB Apr 26 06:00:19 192.168.122.209 [50170.410781] End test: t_reconf.test_reconf_base.TestProxyPassReconf.test_reconf_group Apr 26 06:00:19 192.168.122.209 [50170.425691] Start test: t_reconf.test_reconf_base.TestServerOptionsReconf.test_reconf_health_disabled Apr 26 06:00:21 192.168.122.209 [50171.532320] [tdb] Start Tempesta DB Apr 26 06:00:21 192.168.122.209 [50171.658497] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:00:22 192.168.122.209 [50173.210123] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50173.210123] Maybe that's fine, but it's worth checking the [50173.210123] config - if there is no relations between the [50173.210123] names, then host name confusion attack is possible. Apr 26 06:00:22 192.168.122.209 [50173.340447] [tempesta fw] Configuration processing is completed. Apr 26 06:00:22 192.168.122.209 [50173.392214] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:00:23 192.168.122.209 [50173.815682] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:00:23 192.168.122.209 [50173.844904] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:00:23 192.168.122.209 [50173.880080] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:00:23 192.168.122.209 [50173.928469] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:00:23 192.168.122.209 [50173.980465] [tempesta fw] Tempesta FW is ready Apr 26 06:00:24 192.168.122.209 [50174.613158] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 06:00:24 192.168.122.209 [50174.641543] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50174.641543] Maybe that's fine, but it's worth checking the [50174.641543] config - if there is no relations between the [50174.641543] names, then host name confusion attack is possible. Apr 26 06:00:24 192.168.122.209 [50174.840882] [tempesta fw] Configuration processing is completed. Apr 26 06:00:24 192.168.122.209 [50175.116882] [tempesta fw] Tempesta FW is ready Apr 26 06:00:25 192.168.122.209 [50175.658643] [tdb] Close table 'client0.tdb' Apr 26 06:00:25 192.168.122.209 [50175.850909] [tdb] Close table 'sessions0.tdb' Apr 26 06:00:28 192.168.122.209 [50179.055784] [tdb] Close table 'cache0.tdb' Apr 26 06:00:28 192.168.122.209 [50179.309847] [tdb] Close table 'filter0.tdb' Apr 26 06:00:28 192.168.122.209 [50179.310290] [tempesta fw] modules are stopped Apr 26 06:00:29 192.168.122.209 [50179.498359] [tempesta fw] exiting... Apr 26 06:00:29 192.168.122.209 [50179.643307] [tdb] Shutdown Tempesta DB Apr 26 06:00:29 192.168.122.209 [50179.854924] End test: t_reconf.test_reconf_base.TestServerOptionsReconf.test_reconf_health_disabled Apr 26 06:00:29 192.168.122.209 [50179.866931] Start test: t_reconf.test_reconf_base.TestServerOptionsReconf.test_reconf_health_enabled Apr 26 06:00:30 192.168.122.209 [50180.998799] [tdb] Start Tempesta DB Apr 26 06:00:30 192.168.122.209 [50181.135058] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:00:32 192.168.122.209 [50182.650010] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50182.650010] Maybe that's fine, but it's worth checking the [50182.650010] config - if there is no relations between the [50182.650010] names, then host name confusion attack is possible. Apr 26 06:00:32 192.168.122.209 [50182.780651] [tempesta fw] Configuration processing is completed. Apr 26 06:00:32 192.168.122.209 [50182.834710] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:00:32 192.168.122.209 [50183.243206] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:00:32 192.168.122.209 [50183.299917] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:00:32 192.168.122.209 [50183.325671] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:00:32 192.168.122.209 [50183.380526] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:00:32 192.168.122.209 [50183.428500] [tempesta fw] Tempesta FW is ready Apr 26 06:00:33 192.168.122.209 [50184.081387] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 06:00:33 192.168.122.209 [50184.110864] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50184.110864] Maybe that's fine, but it's worth checking the [50184.110864] config - if there is no relations between the [50184.110864] names, then host name confusion attack is possible. Apr 26 06:00:33 192.168.122.209 [50184.252626] [tempesta fw] Configuration processing is completed. Apr 26 06:00:34 192.168.122.209 [50184.504977] [tempesta fw] Tempesta FW is ready Apr 26 06:00:34 192.168.122.209 [50184.562783] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '502' mismatched Apr 26 06:00:34 192.168.122.209 [50184.563727] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '502' mismatched Apr 26 06:00:34 192.168.122.209 [50184.563975] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '502' mismatched Apr 26 06:00:34 192.168.122.209 [50184.564359] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '502' mismatched Apr 26 06:00:34 192.168.122.209 [50184.566342] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '502' mismatched Apr 26 06:00:34 192.168.122.209 [50184.567092] [tempesta fw] Warning: Error limit exceeded for server: 127.0.0.3:8000 Apr 26 06:00:34 192.168.122.209 [50184.570559] [tempesta fw] Warning: server has been suspended: limit for bad responses is exceeded, status 502: 127.0.0.3:8000 Apr 26 06:00:34 192.168.122.209 [50184.571547] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '502' mismatched Apr 26 06:00:34 192.168.122.209 [50185.045074] [tdb] Close table 'client0.tdb' Apr 26 06:00:34 192.168.122.209 [50185.229306] [tdb] Close table 'sessions0.tdb' Apr 26 06:00:37 192.168.122.209 [50188.430841] [tdb] Close table 'cache0.tdb' Apr 26 06:00:38 192.168.122.209 [50188.674268] [tdb] Close table 'filter0.tdb' Apr 26 06:00:38 192.168.122.209 [50188.674712] [tempesta fw] modules are stopped Apr 26 06:00:38 192.168.122.209 [50188.856461] [tempesta fw] exiting... Apr 26 06:00:38 192.168.122.209 [50188.997533] [tdb] Shutdown Tempesta DB Apr 26 06:00:38 192.168.122.209 [50189.210107] End test: t_reconf.test_reconf_base.TestServerOptionsReconf.test_reconf_health_enabled Apr 26 06:00:38 192.168.122.209 [50189.221000] Start test: t_reconf.test_reconf_base.TestServerOptionsReconf.test_reconf_server_connect_retries_from_0 Apr 26 06:00:39 192.168.122.209 [50190.307004] [tdb] Start Tempesta DB Apr 26 06:00:40 192.168.122.209 [50190.450457] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:00:41 192.168.122.209 [50191.737538] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50191.737538] Maybe that's fine, but it's worth checking the [50191.737538] config - if there is no relations between the [50191.737538] names, then host name confusion attack is possible. Apr 26 06:00:41 192.168.122.209 [50191.832768] [tempesta fw] Configuration processing is completed. Apr 26 06:00:41 192.168.122.209 [50191.910290] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:00:41 192.168.122.209 [50192.332097] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:00:41 192.168.122.209 [50192.359025] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:00:41 192.168.122.209 [50192.394162] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:00:41 192.168.122.209 [50192.428702] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:00:42 192.168.122.209 [50192.468697] [tempesta fw] Tempesta FW is ready Apr 26 06:00:42 192.168.122.209 [50192.982160] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 06:00:42 192.168.122.209 [50193.014979] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50193.014979] Maybe that's fine, but it's worth checking the [50193.014979] config - if there is no relations between the [50193.014979] names, then host name confusion attack is possible. Apr 26 06:00:42 192.168.122.209 [50193.120785] [tempesta fw] Configuration processing is completed. Apr 26 06:00:42 192.168.122.209 [50193.289183] [tempesta fw] Tempesta FW is ready Apr 26 06:00:44 192.168.122.209 [50195.292982] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 06:00:54 192.168.122.209 [50204.978996] [tdb] Close table 'client0.tdb' Apr 26 06:00:54 192.168.122.209 [50205.166319] [tdb] Close table 'sessions0.tdb' Apr 26 06:00:57 192.168.122.209 [50208.425241] [tdb] Close table 'cache0.tdb' Apr 26 06:00:58 192.168.122.209 [50208.656822] [tdb] Close table 'filter0.tdb' Apr 26 06:00:58 192.168.122.209 [50208.657267] [tempesta fw] modules are stopped Apr 26 06:00:58 192.168.122.209 [50208.897625] [tempesta fw] exiting... Apr 26 06:00:58 192.168.122.209 [50209.044812] [tdb] Shutdown Tempesta DB Apr 26 06:00:58 192.168.122.209 [50209.271952] End test: t_reconf.test_reconf_base.TestServerOptionsReconf.test_reconf_server_connect_retries_from_0 Apr 26 06:00:58 192.168.122.209 [50209.281918] Start test: t_reconf.test_reconf_base.TestServerOptionsReconf.test_reconf_server_connect_retries_from_10 Apr 26 06:00:59 192.168.122.209 [50210.342775] [tdb] Start Tempesta DB Apr 26 06:01:00 192.168.122.209 [50210.489562] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:01:01 192.168.122.209 [50211.854568] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50211.854568] Maybe that's fine, but it's worth checking the [50211.854568] config - if there is no relations between the [50211.854568] names, then host name confusion attack is possible. Apr 26 06:01:01 192.168.122.209 [50211.969000] [tempesta fw] Configuration processing is completed. Apr 26 06:01:01 192.168.122.209 [50212.017452] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:01:01 192.168.122.209 [50212.422188] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:01:02 192.168.122.209 [50212.481216] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:01:02 192.168.122.209 [50212.519524] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:01:02 192.168.122.209 [50212.552954] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:01:02 192.168.122.209 [50212.596946] [tempesta fw] Tempesta FW is ready Apr 26 06:01:02 192.168.122.209 [50213.130308] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 06:01:02 192.168.122.209 [50213.153862] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50213.153862] Maybe that's fine, but it's worth checking the [50213.153862] config - if there is no relations between the [50213.153862] names, then host name confusion attack is possible. Apr 26 06:01:02 192.168.122.209 [50213.264952] [tempesta fw] Configuration processing is completed. Apr 26 06:01:02 192.168.122.209 [50213.433358] [tempesta fw] Tempesta FW is ready Apr 26 06:01:04 192.168.122.209 [50215.421637] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 06:01:14 192.168.122.209 [50225.127170] [tdb] Close table 'client0.tdb' Apr 26 06:01:14 192.168.122.209 [50225.311530] [tdb] Close table 'sessions0.tdb' Apr 26 06:01:18 192.168.122.209 [50228.556906] [tdb] Close table 'cache0.tdb' Apr 26 06:01:18 192.168.122.209 [50228.804987] [tdb] Close table 'filter0.tdb' Apr 26 06:01:18 192.168.122.209 [50228.805438] [tempesta fw] modules are stopped Apr 26 06:01:18 192.168.122.209 [50228.987098] [tempesta fw] exiting... Apr 26 06:01:18 192.168.122.209 [50229.129449] [tdb] Shutdown Tempesta DB Apr 26 06:01:18 192.168.122.209 [50229.344867] End test: t_reconf.test_reconf_base.TestServerOptionsReconf.test_reconf_server_connect_retries_from_10 Apr 26 06:01:18 192.168.122.209 [50229.352509] Start test: t_reconf.test_reconf_base.TestServerOptionsReconf.test_reconf_server_connect_retries_from_default Apr 26 06:01:19 192.168.122.209 [50230.362093] [tdb] Start Tempesta DB Apr 26 06:01:20 192.168.122.209 [50230.501069] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:01:21 192.168.122.209 [50231.914541] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50231.914541] Maybe that's fine, but it's worth checking the [50231.914541] config - if there is no relations between the [50231.914541] names, then host name confusion attack is possible. Apr 26 06:01:21 192.168.122.209 [50232.021297] [tempesta fw] Configuration processing is completed. Apr 26 06:01:21 192.168.122.209 [50232.073324] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:01:22 192.168.122.209 [50232.509409] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:01:22 192.168.122.209 [50232.536238] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:01:22 192.168.122.209 [50232.571480] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:01:22 192.168.122.209 [50232.625276] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:01:22 192.168.122.209 [50232.685193] [tempesta fw] Tempesta FW is ready Apr 26 06:01:22 192.168.122.209 [50233.223109] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 06:01:22 192.168.122.209 [50233.256395] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50233.256395] Maybe that's fine, but it's worth checking the [50233.256395] config - if there is no relations between the [50233.256395] names, then host name confusion attack is possible. Apr 26 06:01:22 192.168.122.209 [50233.369302] [tempesta fw] Configuration processing is completed. Apr 26 06:01:23 192.168.122.209 [50233.525642] [tempesta fw] Tempesta FW is ready Apr 26 06:01:25 192.168.122.209 [50235.517795] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 06:01:34 192.168.122.209 [50245.229011] [tdb] Close table 'client0.tdb' Apr 26 06:01:34 192.168.122.209 [50245.414883] [tdb] Close table 'sessions0.tdb' Apr 26 06:01:38 192.168.122.209 [50248.579811] [tdb] Close table 'cache0.tdb' Apr 26 06:01:38 192.168.122.209 [50248.825446] [tdb] Close table 'filter0.tdb' Apr 26 06:01:38 192.168.122.209 [50248.825896] [tempesta fw] modules are stopped Apr 26 06:01:38 192.168.122.209 [50249.017460] [tempesta fw] exiting... Apr 26 06:01:38 192.168.122.209 [50249.148792] [tdb] Shutdown Tempesta DB Apr 26 06:01:38 192.168.122.209 [50249.366544] End test: t_reconf.test_reconf_base.TestServerOptionsReconf.test_reconf_server_connect_retries_from_default Apr 26 06:01:38 192.168.122.209 [50249.379288] Start test: t_reconf.test_reconf_base.TestServerOptionsReconf.test_reconf_server_forward_retries_from_0 Apr 26 06:01:40 192.168.122.209 [50250.477140] [tdb] Start Tempesta DB Apr 26 06:01:40 192.168.122.209 [50250.613153] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:01:41 192.168.122.209 [50251.958644] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50251.958644] Maybe that's fine, but it's worth checking the [50251.958644] config - if there is no relations between the [50251.958644] names, then host name confusion attack is possible. Apr 26 06:01:41 192.168.122.209 [50252.057463] [tempesta fw] Configuration processing is completed. Apr 26 06:01:41 192.168.122.209 [50252.110742] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:01:42 192.168.122.209 [50252.626726] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:01:42 192.168.122.209 [50252.706697] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:01:42 192.168.122.209 [50252.741001] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:01:42 192.168.122.209 [50252.785420] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:01:42 192.168.122.209 [50252.825435] [tempesta fw] Tempesta FW is ready Apr 26 06:01:42 192.168.122.209 [50253.321217] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 06:01:42 192.168.122.209 [50253.342405] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50253.342405] Maybe that's fine, but it's worth checking the [50253.342405] config - if there is no relations between the [50253.342405] names, then host name confusion attack is possible. Apr 26 06:01:43 192.168.122.209 [50253.469526] [tempesta fw] Configuration processing is completed. Apr 26 06:01:43 192.168.122.209 [50253.770289] [tempesta fw] Tempesta FW is ready Apr 26 06:01:43 192.168.122.209 [50253.859398] [tempesta fw] Warning: request evicted: the number of retries exceeded, status 504: 127.0.0.2 Apr 26 06:01:48 192.168.122.209 [50258.728324] [tdb] Close table 'client0.tdb' Apr 26 06:01:48 192.168.122.209 [50258.919597] [tdb] Close table 'sessions0.tdb' Apr 26 06:01:51 192.168.122.209 [50262.167152] [tdb] Close table 'cache0.tdb' Apr 26 06:01:51 192.168.122.209 [50262.419901] [tdb] Close table 'filter0.tdb' Apr 26 06:01:51 192.168.122.209 [50262.420344] [tempesta fw] modules are stopped Apr 26 06:01:52 192.168.122.209 [50262.631059] [tempesta fw] exiting... Apr 26 06:01:52 192.168.122.209 [50262.783370] [tdb] Shutdown Tempesta DB Apr 26 06:01:52 192.168.122.209 [50262.971301] End test: t_reconf.test_reconf_base.TestServerOptionsReconf.test_reconf_server_forward_retries_from_0 Apr 26 06:01:52 192.168.122.209 [50262.983769] Start test: t_reconf.test_reconf_base.TestServerOptionsReconf.test_reconf_server_forward_retries_from_1 Apr 26 06:01:53 192.168.122.209 [50264.020326] [tdb] Start Tempesta DB Apr 26 06:01:53 192.168.122.209 [50264.167247] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:01:55 192.168.122.209 [50265.518079] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50265.518079] Maybe that's fine, but it's worth checking the [50265.518079] config - if there is no relations between the [50265.518079] names, then host name confusion attack is possible. Apr 26 06:01:55 192.168.122.209 [50265.629712] [tempesta fw] Configuration processing is completed. Apr 26 06:01:55 192.168.122.209 [50265.682079] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:01:55 192.168.122.209 [50266.095395] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:01:55 192.168.122.209 [50266.152724] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:01:55 192.168.122.209 [50266.179722] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:01:55 192.168.122.209 [50266.225584] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:01:55 192.168.122.209 [50266.277604] [tempesta fw] Tempesta FW is ready Apr 26 06:01:56 192.168.122.209 [50266.757405] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 06:01:56 192.168.122.209 [50266.778202] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50266.778202] Maybe that's fine, but it's worth checking the [50266.778202] config - if there is no relations between the [50266.778202] names, then host name confusion attack is possible. Apr 26 06:01:56 192.168.122.209 [50266.889704] [tempesta fw] Configuration processing is completed. Apr 26 06:01:56 192.168.122.209 [50267.162020] [tempesta fw] Tempesta FW is ready Apr 26 06:01:56 192.168.122.209 [50267.246253] [tempesta fw] Warning: request evicted: the number of retries exceeded, status 504: 127.0.0.2 Apr 26 06:02:01 192.168.122.209 [50272.008343] [tdb] Close table 'client0.tdb' Apr 26 06:02:01 192.168.122.209 [50272.196602] [tdb] Close table 'sessions0.tdb' Apr 26 06:02:04 192.168.122.209 [50275.398914] [tdb] Close table 'cache0.tdb' Apr 26 06:02:05 192.168.122.209 [50275.620840] [tdb] Close table 'filter0.tdb' Apr 26 06:02:05 192.168.122.209 [50275.621287] [tempesta fw] modules are stopped Apr 26 06:02:05 192.168.122.209 [50275.825210] [tempesta fw] exiting... Apr 26 06:02:05 192.168.122.209 [50275.956808] [tdb] Shutdown Tempesta DB Apr 26 06:02:05 192.168.122.209 [50276.146941] End test: t_reconf.test_reconf_base.TestServerOptionsReconf.test_reconf_server_forward_retries_from_1 Apr 26 06:02:05 192.168.122.209 [50276.168344] Start test: t_reconf.test_reconf_base.TestServerOptionsReconf.test_reconf_server_forward_retries_from_default Apr 26 06:02:06 192.168.122.209 [50277.317610] [tdb] Start Tempesta DB Apr 26 06:02:07 192.168.122.209 [50277.450096] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:02:08 192.168.122.209 [50278.857310] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50278.857310] Maybe that's fine, but it's worth checking the [50278.857310] config - if there is no relations between the [50278.857310] names, then host name confusion attack is possible. Apr 26 06:02:08 192.168.122.209 [50278.957862] [tempesta fw] Configuration processing is completed. Apr 26 06:02:08 192.168.122.209 [50279.011593] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:02:08 192.168.122.209 [50279.434795] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:02:09 192.168.122.209 [50279.461328] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:02:09 192.168.122.209 [50279.487664] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:02:09 192.168.122.209 [50279.565865] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:02:09 192.168.122.209 [50279.617782] [tempesta fw] Tempesta FW is ready Apr 26 06:02:09 192.168.122.209 [50280.095177] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 06:02:09 192.168.122.209 [50280.127170] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50280.127170] Maybe that's fine, but it's worth checking the [50280.127170] config - if there is no relations between the [50280.127170] names, then host name confusion attack is possible. Apr 26 06:02:09 192.168.122.209 [50280.265836] [tempesta fw] Configuration processing is completed. Apr 26 06:02:10 192.168.122.209 [50280.542189] [tempesta fw] Tempesta FW is ready Apr 26 06:02:10 192.168.122.209 [50280.626535] [tempesta fw] Warning: request evicted: the number of retries exceeded, status 504: 127.0.0.2 Apr 26 06:02:14 192.168.122.209 [50285.332187] [tdb] Close table 'client0.tdb' Apr 26 06:02:15 192.168.122.209 [50285.525107] [tdb] Close table 'sessions0.tdb' Apr 26 06:02:18 192.168.122.209 [50288.727554] [tdb] Close table 'cache0.tdb' Apr 26 06:02:18 192.168.122.209 [50288.953014] [tdb] Close table 'filter0.tdb' Apr 26 06:02:18 192.168.122.209 [50288.953453] [tempesta fw] modules are stopped Apr 26 06:02:18 192.168.122.209 [50289.134377] [tempesta fw] exiting... Apr 26 06:02:18 192.168.122.209 [50289.264411] [tdb] Shutdown Tempesta DB Apr 26 06:02:19 192.168.122.209 [50289.467733] End test: t_reconf.test_reconf_base.TestServerOptionsReconf.test_reconf_server_forward_retries_from_default Apr 26 06:02:19 192.168.122.209 [50289.478891] Start test: t_reconf.test_reconf_base.TestServerOptionsReconf.test_reconf_server_forward_retries_from_x Apr 26 06:02:20 192.168.122.209 [50290.591971] [tdb] Start Tempesta DB Apr 26 06:02:20 192.168.122.209 [50290.722279] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:02:21 192.168.122.209 [50292.035734] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50292.035734] Maybe that's fine, but it's worth checking the [50292.035734] config - if there is no relations between the [50292.035734] names, then host name confusion attack is possible. Apr 26 06:02:21 192.168.122.209 [50292.129929] [tempesta fw] Configuration processing is completed. Apr 26 06:02:21 192.168.122.209 [50292.188841] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:02:22 192.168.122.209 [50292.596983] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:02:22 192.168.122.209 [50292.665394] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:02:22 192.168.122.209 [50292.691371] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:02:22 192.168.122.209 [50292.737952] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:02:22 192.168.122.209 [50292.777979] [tempesta fw] Tempesta FW is ready Apr 26 06:02:22 192.168.122.209 [50293.302654] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 06:02:22 192.168.122.209 [50293.330885] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50293.330885] Maybe that's fine, but it's worth checking the [50293.330885] config - if there is no relations between the [50293.330885] names, then host name confusion attack is possible. Apr 26 06:02:23 192.168.122.209 [50293.461961] [tempesta fw] Configuration processing is completed. Apr 26 06:02:23 192.168.122.209 [50293.746348] [tempesta fw] Tempesta FW is ready Apr 26 06:02:23 192.168.122.209 [50293.834280] [tempesta fw] Warning: request evicted: the number of retries exceeded, status 504: 127.0.0.2 Apr 26 06:02:28 192.168.122.209 [50298.530932] [tdb] Close table 'client0.tdb' Apr 26 06:02:28 192.168.122.209 [50298.712998] [tdb] Close table 'sessions0.tdb' Apr 26 06:02:31 192.168.122.209 [50301.913504] [tdb] Close table 'cache0.tdb' Apr 26 06:02:31 192.168.122.209 [50302.139689] [tdb] Close table 'filter0.tdb' Apr 26 06:02:31 192.168.122.209 [50302.140130] [tempesta fw] modules are stopped Apr 26 06:02:31 192.168.122.209 [50302.402366] [tempesta fw] exiting... Apr 26 06:02:32 192.168.122.209 [50302.546212] [tdb] Shutdown Tempesta DB Apr 26 06:02:32 192.168.122.209 [50302.753475] End test: t_reconf.test_reconf_base.TestServerOptionsReconf.test_reconf_server_forward_retries_from_x Apr 26 06:02:32 192.168.122.209 [50302.766986] Start test: t_reconf.test_reconf_base.TestServerOptionsReconf.test_reconf_server_forward_timeout_disabled Apr 26 06:02:33 192.168.122.209 [50303.901612] [tdb] Start Tempesta DB Apr 26 06:02:33 192.168.122.209 [50304.052577] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:02:34 192.168.122.209 [50305.427780] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50305.427780] Maybe that's fine, but it's worth checking the [50305.427780] config - if there is no relations between the [50305.427780] names, then host name confusion attack is possible. Apr 26 06:02:35 192.168.122.209 [50305.522205] [tempesta fw] Configuration processing is completed. Apr 26 06:02:35 192.168.122.209 [50305.574217] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:02:35 192.168.122.209 [50305.994723] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:02:35 192.168.122.209 [50306.021560] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:02:35 192.168.122.209 [50306.048125] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:02:35 192.168.122.209 [50306.094132] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:02:35 192.168.122.209 [50306.134123] [tempesta fw] Tempesta FW is ready Apr 26 06:02:36 192.168.122.209 [50306.584283] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 06:02:36 192.168.122.209 [50306.615296] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50306.615296] Maybe that's fine, but it's worth checking the [50306.615296] config - if there is no relations between the [50306.615296] names, then host name confusion attack is possible. Apr 26 06:02:36 192.168.122.209 [50306.742123] [tempesta fw] Configuration processing is completed. Apr 26 06:02:36 192.168.122.209 [50307.030533] [tempesta fw] Tempesta FW is ready Apr 26 06:02:39 192.168.122.209 [50309.570579] [tdb] Close table 'client0.tdb' Apr 26 06:02:39 192.168.122.209 [50309.758322] [tdb] Close table 'sessions0.tdb' Apr 26 06:02:42 192.168.122.209 [50313.157722] [tdb] Close table 'cache0.tdb' Apr 26 06:02:42 192.168.122.209 [50313.391514] [tdb] Close table 'filter0.tdb' Apr 26 06:02:42 192.168.122.209 [50313.391979] [tempesta fw] modules are stopped Apr 26 06:02:43 192.168.122.209 [50313.611139] [tempesta fw] exiting... Apr 26 06:02:43 192.168.122.209 [50313.740412] [tdb] Shutdown Tempesta DB Apr 26 06:02:43 192.168.122.209 [50313.953554] End test: t_reconf.test_reconf_base.TestServerOptionsReconf.test_reconf_server_forward_timeout_disabled Apr 26 06:02:43 192.168.122.209 [50313.966896] Start test: t_reconf.test_reconf_base.TestServerOptionsReconf.test_reconf_server_forward_timeout_enabled Apr 26 06:02:44 192.168.122.209 [50315.054748] [tdb] Start Tempesta DB Apr 26 06:02:44 192.168.122.209 [50315.194481] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:02:46 192.168.122.209 [50316.631792] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50316.631792] Maybe that's fine, but it's worth checking the [50316.631792] config - if there is no relations between the [50316.631792] names, then host name confusion attack is possible. Apr 26 06:02:46 192.168.122.209 [50316.726341] [tempesta fw] Configuration processing is completed. Apr 26 06:02:46 192.168.122.209 [50316.780024] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:02:46 192.168.122.209 [50317.200260] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:02:46 192.168.122.209 [50317.257379] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:02:46 192.168.122.209 [50317.283298] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:02:46 192.168.122.209 [50317.326244] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:02:46 192.168.122.209 [50317.366263] [tempesta fw] Tempesta FW is ready Apr 26 06:02:47 192.168.122.209 [50317.888600] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 06:02:47 192.168.122.209 [50317.915169] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50317.915169] Maybe that's fine, but it's worth checking the [50317.915169] config - if there is no relations between the [50317.915169] names, then host name confusion attack is possible. Apr 26 06:02:47 192.168.122.209 [50318.026384] [tempesta fw] Configuration processing is completed. Apr 26 06:02:47 192.168.122.209 [50318.274703] [tempesta fw] Tempesta FW is ready Apr 26 06:02:48 192.168.122.209 [50319.322518] [tempesta fw] Warning: request evicted: timed out, status 504: 127.0.0.2 Apr 26 06:02:49 192.168.122.209 [50319.833819] [tdb] Close table 'client0.tdb' Apr 26 06:02:49 192.168.122.209 [50320.026979] [tdb] Close table 'sessions0.tdb' Apr 26 06:02:53 192.168.122.209 [50323.478761] [tdb] Close table 'cache0.tdb' Apr 26 06:02:53 192.168.122.209 [50323.726498] [tdb] Close table 'filter0.tdb' Apr 26 06:02:53 192.168.122.209 [50323.726955] [tempesta fw] modules are stopped Apr 26 06:02:53 192.168.122.209 [50323.923513] [tempesta fw] exiting... Apr 26 06:02:53 192.168.122.209 [50324.042717] [tdb] Shutdown Tempesta DB Apr 26 06:02:53 192.168.122.209 [50324.252248] End test: t_reconf.test_reconf_base.TestServerOptionsReconf.test_reconf_server_forward_timeout_enabled Apr 26 06:02:53 192.168.122.209 [50324.263672] Start test: t_reconf.test_reconf_base.TestServerOptionsReconf.test_reconf_server_queue_size_disabled Apr 26 06:02:54 192.168.122.209 [50325.361277] [tdb] Start Tempesta DB Apr 26 06:02:55 192.168.122.209 [50325.501095] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:02:56 192.168.122.209 [50326.875097] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50326.875097] Maybe that's fine, but it's worth checking the [50326.875097] config - if there is no relations between the [50326.875097] names, then host name confusion attack is possible. Apr 26 06:02:56 192.168.122.209 [50326.986455] [tempesta fw] Configuration processing is completed. Apr 26 06:02:56 192.168.122.209 [50327.040636] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:02:57 192.168.122.209 [50327.489295] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:02:57 192.168.122.209 [50327.517817] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:02:57 192.168.122.209 [50327.545948] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:02:57 192.168.122.209 [50327.586416] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:02:57 192.168.122.209 [50327.646392] [tempesta fw] Tempesta FW is ready Apr 26 06:02:57 192.168.122.209 [50328.275580] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 06:02:57 192.168.122.209 [50328.299400] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50328.299400] Maybe that's fine, but it's worth checking the [50328.299400] config - if there is no relations between the [50328.299400] names, then host name confusion attack is possible. Apr 26 06:02:57 192.168.122.209 [50328.402469] [tempesta fw] Configuration processing is completed. Apr 26 06:02:58 192.168.122.209 [50328.610831] [tempesta fw] Tempesta FW is ready Apr 26 06:02:59 192.168.122.209 [50330.124677] [tdb] Close table 'client0.tdb' Apr 26 06:02:59 192.168.122.209 [50330.319244] [tdb] Close table 'sessions0.tdb' Apr 26 06:03:03 192.168.122.209 [50333.596052] [tdb] Close table 'cache0.tdb' Apr 26 06:03:03 192.168.122.209 [50333.849094] [tdb] Close table 'filter0.tdb' Apr 26 06:03:03 192.168.122.209 [50333.849536] [tempesta fw] modules are stopped Apr 26 06:03:03 192.168.122.209 [50334.030742] [tempesta fw] exiting... Apr 26 06:03:03 192.168.122.209 [50334.172727] [tdb] Shutdown Tempesta DB Apr 26 06:03:03 192.168.122.209 [50334.385245] End test: t_reconf.test_reconf_base.TestServerOptionsReconf.test_reconf_server_queue_size_disabled Apr 26 06:03:03 192.168.122.209 [50334.393873] Start test: t_reconf.test_reconf_base.TestServerOptionsReconf.test_reconf_server_retry_nonidempotent_disabled Apr 26 06:03:05 192.168.122.209 [50335.508458] [tdb] Start Tempesta DB Apr 26 06:03:05 192.168.122.209 [50335.667890] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:03:06 192.168.122.209 [50337.215480] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50337.215480] Maybe that's fine, but it's worth checking the [50337.215480] config - if there is no relations between the [50337.215480] names, then host name confusion attack is possible. Apr 26 06:03:06 192.168.122.209 [50337.342613] [tempesta fw] Configuration processing is completed. Apr 26 06:03:06 192.168.122.209 [50337.407841] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:03:07 192.168.122.209 [50337.853065] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:03:07 192.168.122.209 [50337.917656] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:03:07 192.168.122.209 [50337.947834] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:03:07 192.168.122.209 [50337.990534] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:03:07 192.168.122.209 [50338.034548] [tempesta fw] Tempesta FW is ready Apr 26 06:03:08 192.168.122.209 [50338.684076] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 06:03:08 192.168.122.209 [50338.719792] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50338.719792] Maybe that's fine, but it's worth checking the [50338.719792] config - if there is no relations between the [50338.719792] names, then host name confusion attack is possible. Apr 26 06:03:08 192.168.122.209 [50338.890643] [tempesta fw] Configuration processing is completed. Apr 26 06:03:08 192.168.122.209 [50339.147108] [tempesta fw] Tempesta FW is ready Apr 26 06:03:08 192.168.122.209 [50339.216041] [tempesta fw] Warning: request dropped: non-idempotent requests aren't re-forwarded or re-scheduled, status 504: 127.0.0.2 Apr 26 06:03:09 192.168.122.209 [50339.737433] [tdb] Close table 'client0.tdb' Apr 26 06:03:09 192.168.122.209 [50339.920133] [tdb] Close table 'sessions0.tdb' Apr 26 06:03:12 192.168.122.209 [50343.180108] [tdb] Close table 'cache0.tdb' Apr 26 06:03:12 192.168.122.209 [50343.423396] [tdb] Close table 'filter0.tdb' Apr 26 06:03:12 192.168.122.209 [50343.423828] [tempesta fw] modules are stopped Apr 26 06:03:13 192.168.122.209 [50343.667670] [tempesta fw] exiting... Apr 26 06:03:13 192.168.122.209 [50343.823727] [tdb] Shutdown Tempesta DB Apr 26 06:03:13 192.168.122.209 [50344.022402] End test: t_reconf.test_reconf_base.TestServerOptionsReconf.test_reconf_server_retry_nonidempotent_disabled Apr 26 06:03:13 192.168.122.209 [50344.044540] Start test: t_reconf.test_reconf_base.TestServerOptionsReconf.test_reconf_server_retry_nonidempotent_enabled Apr 26 06:03:14 192.168.122.209 [50345.138638] [tdb] Start Tempesta DB Apr 26 06:03:14 192.168.122.209 [50345.292566] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:03:16 192.168.122.209 [50346.784223] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50346.784223] Maybe that's fine, but it's worth checking the [50346.784223] config - if there is no relations between the [50346.784223] names, then host name confusion attack is possible. Apr 26 06:03:16 192.168.122.209 [50346.922728] [tempesta fw] Configuration processing is completed. Apr 26 06:03:16 192.168.122.209 [50346.983804] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:03:17 192.168.122.209 [50347.556545] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:03:17 192.168.122.209 [50347.593452] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:03:17 192.168.122.209 [50347.627853] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:03:17 192.168.122.209 [50347.674739] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:03:17 192.168.122.209 [50347.722638] [tempesta fw] Tempesta FW is ready Apr 26 06:03:17 192.168.122.209 [50348.332775] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 06:03:17 192.168.122.209 [50348.351276] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50348.351276] Maybe that's fine, but it's worth checking the [50348.351276] config - if there is no relations between the [50348.351276] names, then host name confusion attack is possible. Apr 26 06:03:18 192.168.122.209 [50348.502764] [tempesta fw] Configuration processing is completed. Apr 26 06:03:18 192.168.122.209 [50348.775186] [tempesta fw] Tempesta FW is ready Apr 26 06:03:18 192.168.122.209 [50348.882861] [tempesta fw] Warning: request evicted: the number of retries exceeded, status 504: 127.0.0.2 Apr 26 06:03:18 192.168.122.209 [50349.364463] [tdb] Close table 'client0.tdb' Apr 26 06:03:19 192.168.122.209 [50349.554781] [tdb] Close table 'sessions0.tdb' Apr 26 06:03:22 192.168.122.209 [50352.821606] [tdb] Close table 'cache0.tdb' Apr 26 06:03:22 192.168.122.209 [50353.071171] [tdb] Close table 'filter0.tdb' Apr 26 06:03:22 192.168.122.209 [50353.071619] [tempesta fw] modules are stopped Apr 26 06:03:22 192.168.122.209 [50353.269352] [tempesta fw] exiting... Apr 26 06:03:22 192.168.122.209 [50353.408894] [tdb] Shutdown Tempesta DB Apr 26 06:03:23 192.168.122.209 [50353.629983] End test: t_reconf.test_reconf_base.TestServerOptionsReconf.test_reconf_server_retry_nonidempotent_enabled Apr 26 06:03:23 192.168.122.209 [50353.640529] Start test: t_reconf.test_reconf_base.TestServerReconf.test_add_new_server_group Apr 26 06:03:24 192.168.122.209 [50354.637551] [tdb] Start Tempesta DB Apr 26 06:03:24 192.168.122.209 [50354.778203] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:03:25 192.168.122.209 [50356.286911] [tempesta fw] Configuration processing is completed. Apr 26 06:03:25 192.168.122.209 [50356.343835] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:03:26 192.168.122.209 [50356.756526] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:03:26 192.168.122.209 [50356.815079] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:03:26 192.168.122.209 [50356.841302] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:03:26 192.168.122.209 [50356.882755] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:03:26 192.168.122.209 [50356.934744] [tempesta fw] Tempesta FW is ready Apr 26 06:03:27 192.168.122.209 [50357.608627] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 06:03:27 192.168.122.209 [50357.794768] [tempesta fw] Configuration processing is completed. Apr 26 06:03:27 192.168.122.209 [50358.146956] [tempesta fw] Tempesta FW is ready Apr 26 06:03:28 192.168.122.209 [50358.904321] [tdb] Close table 'client0.tdb' Apr 26 06:03:28 192.168.122.209 [50359.091882] [tdb] Close table 'sessions0.tdb' Apr 26 06:03:31 192.168.122.209 [50362.315623] [tdb] Close table 'cache0.tdb' Apr 26 06:03:32 192.168.122.209 [50362.557320] [tdb] Close table 'filter0.tdb' Apr 26 06:03:32 192.168.122.209 [50362.557757] [tempesta fw] modules are stopped Apr 26 06:03:32 192.168.122.209 [50362.808630] [tempesta fw] exiting... Apr 26 06:03:32 192.168.122.209 [50362.946209] [tdb] Shutdown Tempesta DB Apr 26 06:03:32 192.168.122.209 [50363.159616] End test: t_reconf.test_reconf_base.TestServerReconf.test_add_new_server_group Apr 26 06:03:32 192.168.122.209 [50363.181069] Start test: t_reconf.test_reconf_base.TestServerReconf.test_add_new_server_to_default_srv_group Apr 26 06:03:33 192.168.122.209 [50364.242505] [tdb] Start Tempesta DB Apr 26 06:03:33 192.168.122.209 [50364.385914] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:03:35 192.168.122.209 [50365.475312] [tempesta fw] Configuration processing is completed. Apr 26 06:03:35 192.168.122.209 [50365.532015] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:03:35 192.168.122.209 [50365.966408] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:03:35 192.168.122.209 [50365.992150] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:03:35 192.168.122.209 [50366.018111] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:03:35 192.168.122.209 [50366.070843] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:03:35 192.168.122.209 [50366.106859] [tempesta fw] Tempesta FW is ready Apr 26 06:03:36 192.168.122.209 [50366.488262] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 06:03:36 192.168.122.209 [50366.591019] [tempesta fw] Configuration processing is completed. Apr 26 06:03:36 192.168.122.209 [50366.854941] [tempesta fw] Tempesta FW is ready Apr 26 06:03:37 192.168.122.209 [50367.625313] [tdb] Close table 'client0.tdb' Apr 26 06:03:37 192.168.122.209 [50367.821946] [tdb] Close table 'sessions0.tdb' Apr 26 06:03:40 192.168.122.209 [50371.031891] [tdb] Close table 'cache0.tdb' Apr 26 06:03:40 192.168.122.209 [50371.268285] [tdb] Close table 'filter0.tdb' Apr 26 06:03:40 192.168.122.209 [50371.268720] [tempesta fw] modules are stopped Apr 26 06:03:40 192.168.122.209 [50371.438283] [tempesta fw] exiting... Apr 26 06:03:41 192.168.122.209 [50371.571537] [tdb] Shutdown Tempesta DB Apr 26 06:03:41 192.168.122.209 [50371.785235] End test: t_reconf.test_reconf_base.TestServerReconf.test_add_new_server_to_default_srv_group Apr 26 06:03:41 192.168.122.209 [50371.798350] Start test: t_reconf.test_reconf_base.TestServerReconf.test_add_new_server_to_srv_group Apr 26 06:03:42 192.168.122.209 [50372.860934] [tdb] Start Tempesta DB Apr 26 06:03:42 192.168.122.209 [50373.009111] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:03:44 192.168.122.209 [50374.502994] [tempesta fw] Configuration processing is completed. Apr 26 06:03:44 192.168.122.209 [50374.558296] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:03:44 192.168.122.209 [50374.974342] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:03:44 192.168.122.209 [50375.001142] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:03:44 192.168.122.209 [50375.027395] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:03:44 192.168.122.209 [50375.074936] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:03:44 192.168.122.209 [50375.114975] [tempesta fw] Tempesta FW is ready Apr 26 06:03:45 192.168.122.209 [50375.644452] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 06:03:45 192.168.122.209 [50375.771076] [tempesta fw] Configuration processing is completed. Apr 26 06:03:45 192.168.122.209 [50376.063204] [tempesta fw] Tempesta FW is ready Apr 26 06:03:46 192.168.122.209 [50376.829776] [tdb] Close table 'client0.tdb' Apr 26 06:03:46 192.168.122.209 [50377.017653] [tdb] Close table 'sessions0.tdb' Apr 26 06:03:49 192.168.122.209 [50380.240102] [tdb] Close table 'cache0.tdb' Apr 26 06:03:50 192.168.122.209 [50380.461596] [tdb] Close table 'filter0.tdb' Apr 26 06:03:50 192.168.122.209 [50380.462053] [tempesta fw] modules are stopped Apr 26 06:03:50 192.168.122.209 [50380.714295] [tempesta fw] exiting... Apr 26 06:03:50 192.168.122.209 [50380.847256] [tdb] Shutdown Tempesta DB Apr 26 06:03:50 192.168.122.209 [50381.035603] End test: t_reconf.test_reconf_base.TestServerReconf.test_add_new_server_to_srv_group Apr 26 06:03:50 192.168.122.209 [50381.056534] Start test: t_reconf.test_reconf_base.TestServerReconf.test_conns_n_decrease Apr 26 06:03:51 192.168.122.209 [50382.082646] [tdb] Start Tempesta DB Apr 26 06:03:51 192.168.122.209 [50382.230121] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:03:52 192.168.122.209 [50383.427406] [tempesta fw] Configuration processing is completed. Apr 26 06:03:53 192.168.122.209 [50383.477041] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:03:53 192.168.122.209 [50383.896825] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:03:53 192.168.122.209 [50383.923694] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:03:53 192.168.122.209 [50383.950470] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:03:53 192.168.122.209 [50383.995094] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:03:53 192.168.122.209 [50384.035088] [tempesta fw] Tempesta FW is ready Apr 26 06:03:53 192.168.122.209 [50384.422198] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 06:03:54 192.168.122.209 [50384.475125] [tempesta fw] Configuration processing is completed. Apr 26 06:03:54 192.168.122.209 [50384.695046] [tempesta fw] Tempesta FW is ready Apr 26 06:03:54 192.168.122.209 [50385.249278] [tdb] Close table 'client0.tdb' Apr 26 06:03:54 192.168.122.209 [50385.436918] [tdb] Close table 'sessions0.tdb' Apr 26 06:03:58 192.168.122.209 [50388.622165] [tdb] Close table 'cache0.tdb' Apr 26 06:03:58 192.168.122.209 [50388.855200] [tdb] Close table 'filter0.tdb' Apr 26 06:03:58 192.168.122.209 [50388.855642] [tempesta fw] modules are stopped Apr 26 06:03:58 192.168.122.209 [50389.016372] [tempesta fw] exiting... Apr 26 06:03:58 192.168.122.209 [50389.156791] [tdb] Shutdown Tempesta DB Apr 26 06:03:58 192.168.122.209 [50389.373859] End test: t_reconf.test_reconf_base.TestServerReconf.test_conns_n_decrease Apr 26 06:03:58 192.168.122.209 [50389.385519] Start test: t_reconf.test_reconf_base.TestServerReconf.test_conns_n_decrease_from_default Apr 26 06:03:59 192.168.122.209 [50390.427703] [tdb] Start Tempesta DB Apr 26 06:04:00 192.168.122.209 [50390.557765] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:04:01 192.168.122.209 [50391.663610] [tempesta fw] Configuration processing is completed. Apr 26 06:04:01 192.168.122.209 [50391.715995] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:04:01 192.168.122.209 [50392.123432] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:04:01 192.168.122.209 [50392.149237] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:04:01 192.168.122.209 [50392.175395] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:04:01 192.168.122.209 [50392.227172] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:04:01 192.168.122.209 [50392.267118] [tempesta fw] Tempesta FW is ready Apr 26 06:04:02 192.168.122.209 [50392.605211] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 06:04:02 192.168.122.209 [50392.655672] [tempesta fw] Configuration processing is completed. Apr 26 06:04:02 192.168.122.209 [50392.887293] [tempesta fw] Tempesta FW is ready Apr 26 06:04:02 192.168.122.209 [50393.384946] [tdb] Close table 'client0.tdb' Apr 26 06:04:03 192.168.122.209 [50393.566993] [tdb] Close table 'sessions0.tdb' Apr 26 06:04:06 192.168.122.209 [50396.728799] [tdb] Close table 'cache0.tdb' Apr 26 06:04:06 192.168.122.209 [50396.949849] [tdb] Close table 'filter0.tdb' Apr 26 06:04:06 192.168.122.209 [50396.950287] [tempesta fw] modules are stopped Apr 26 06:04:06 192.168.122.209 [50397.191011] [tempesta fw] exiting... Apr 26 06:04:06 192.168.122.209 [50397.328402] [tdb] Shutdown Tempesta DB Apr 26 06:04:07 192.168.122.209 [50397.560775] End test: t_reconf.test_reconf_base.TestServerReconf.test_conns_n_decrease_from_default Apr 26 06:04:07 192.168.122.209 [50397.573885] Start test: t_reconf.test_reconf_base.TestServerReconf.test_conns_n_for_srv_group_decrease Apr 26 06:04:08 192.168.122.209 [50398.628321] [tdb] Start Tempesta DB Apr 26 06:04:08 192.168.122.209 [50398.758012] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:04:09 192.168.122.209 [50400.103409] [tempesta fw] Configuration processing is completed. Apr 26 06:04:09 192.168.122.209 [50400.155246] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:04:10 192.168.122.209 [50400.568588] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:04:10 192.168.122.209 [50400.594565] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:04:10 192.168.122.209 [50400.620456] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:04:10 192.168.122.209 [50400.671403] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:04:10 192.168.122.209 [50400.719309] [tempesta fw] Tempesta FW is ready Apr 26 06:04:10 192.168.122.209 [50401.220555] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 06:04:10 192.168.122.209 [50401.327315] [tempesta fw] Configuration processing is completed. Apr 26 06:04:11 192.168.122.209 [50401.543474] [tempesta fw] Tempesta FW is ready Apr 26 06:04:11 192.168.122.209 [50402.006900] [tdb] Close table 'client0.tdb' Apr 26 06:04:11 192.168.122.209 [50402.188669] [tdb] Close table 'sessions0.tdb' Apr 26 06:04:15 192.168.122.209 [50405.447739] [tdb] Close table 'cache0.tdb' Apr 26 06:04:15 192.168.122.209 [50405.687532] [tdb] Close table 'filter0.tdb' Apr 26 06:04:15 192.168.122.209 [50405.687952] [tempesta fw] modules are stopped Apr 26 06:04:15 192.168.122.209 [50405.934005] [tempesta fw] exiting... Apr 26 06:04:15 192.168.122.209 [50406.052040] [tdb] Shutdown Tempesta DB Apr 26 06:04:15 192.168.122.209 [50406.248139] End test: t_reconf.test_reconf_base.TestServerReconf.test_conns_n_for_srv_group_decrease Apr 26 06:04:15 192.168.122.209 [50406.258418] Start test: t_reconf.test_reconf_base.TestServerReconf.test_conns_n_for_srv_group_increase Apr 26 06:04:16 192.168.122.209 [50407.239278] [tdb] Start Tempesta DB Apr 26 06:04:16 192.168.122.209 [50407.367872] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:04:18 192.168.122.209 [50408.803527] [tempesta fw] Configuration processing is completed. Apr 26 06:04:18 192.168.122.209 [50408.853830] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:04:18 192.168.122.209 [50409.264147] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:04:18 192.168.122.209 [50409.290701] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:04:18 192.168.122.209 [50409.317027] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:04:18 192.168.122.209 [50409.375482] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:04:18 192.168.122.209 [50409.415369] [tempesta fw] Tempesta FW is ready Apr 26 06:04:19 192.168.122.209 [50409.886174] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 06:04:19 192.168.122.209 [50409.983534] [tempesta fw] Configuration processing is completed. Apr 26 06:04:20 192.168.122.209 [50410.855574] [tempesta fw] Tempesta FW is ready Apr 26 06:04:20 192.168.122.209 [50411.347824] [tdb] Close table 'client0.tdb' Apr 26 06:04:21 192.168.122.209 [50411.533217] [tdb] Close table 'sessions0.tdb' Apr 26 06:04:24 192.168.122.209 [50414.745132] [tdb] Close table 'cache0.tdb' Apr 26 06:04:24 192.168.122.209 [50414.980581] [tdb] Close table 'filter0.tdb' Apr 26 06:04:24 192.168.122.209 [50414.981024] [tempesta fw] modules are stopped Apr 26 06:04:24 192.168.122.209 [50415.237046] [tempesta fw] exiting... Apr 26 06:04:24 192.168.122.209 [50415.386427] [tdb] Shutdown Tempesta DB Apr 26 06:04:25 192.168.122.209 [50415.574461] End test: t_reconf.test_reconf_base.TestServerReconf.test_conns_n_for_srv_group_increase Apr 26 06:04:25 192.168.122.209 [50415.599407] Start test: t_reconf.test_reconf_base.TestServerReconf.test_conns_n_increase Apr 26 06:04:26 192.168.122.209 [50416.636461] [tdb] Start Tempesta DB Apr 26 06:04:26 192.168.122.209 [50416.777626] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:04:27 192.168.122.209 [50417.911906] [tempesta fw] Configuration processing is completed. Apr 26 06:04:27 192.168.122.209 [50417.962612] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:04:27 192.168.122.209 [50418.389143] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:04:27 192.168.122.209 [50418.414221] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:04:27 192.168.122.209 [50418.440293] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:04:28 192.168.122.209 [50418.483523] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:04:28 192.168.122.209 [50418.539525] [tempesta fw] Tempesta FW is ready Apr 26 06:04:28 192.168.122.209 [50418.913599] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 06:04:28 192.168.122.209 [50418.959990] [tempesta fw] Configuration processing is completed. Apr 26 06:04:28 192.168.122.209 [50419.199922] [tempesta fw] Tempesta FW is ready Apr 26 06:04:29 192.168.122.209 [50419.678806] [tdb] Close table 'client0.tdb' Apr 26 06:04:29 192.168.122.209 [50419.877468] [tdb] Close table 'sessions0.tdb' Apr 26 06:04:32 192.168.122.209 [50423.052286] [tdb] Close table 'cache0.tdb' Apr 26 06:04:32 192.168.122.209 [50423.297809] [tdb] Close table 'filter0.tdb' Apr 26 06:04:32 192.168.122.209 [50423.298244] [tempesta fw] modules are stopped Apr 26 06:04:33 192.168.122.209 [50423.461187] [tempesta fw] exiting... Apr 26 06:04:33 192.168.122.209 [50423.613682] [tdb] Shutdown Tempesta DB Apr 26 06:04:33 192.168.122.209 [50423.817485] End test: t_reconf.test_reconf_base.TestServerReconf.test_conns_n_increase Apr 26 06:04:33 192.168.122.209 [50423.828664] Start test: t_reconf.test_reconf_base.TestServerReconf.test_conns_n_increase_from_default Apr 26 06:04:34 192.168.122.209 [50424.964612] [tdb] Start Tempesta DB Apr 26 06:04:34 192.168.122.209 [50425.108688] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:04:35 192.168.122.209 [50426.263797] [tempesta fw] Configuration processing is completed. Apr 26 06:04:35 192.168.122.209 [50426.326073] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:04:36 192.168.122.209 [50426.799969] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:04:36 192.168.122.209 [50426.827085] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:04:36 192.168.122.209 [50426.860575] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:04:36 192.168.122.209 [50426.899620] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:04:36 192.168.122.209 [50426.939571] [tempesta fw] Tempesta FW is ready Apr 26 06:04:36 192.168.122.209 [50427.280443] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 06:04:36 192.168.122.209 [50427.323693] [tempesta fw] Configuration processing is completed. Apr 26 06:04:37 192.168.122.209 [50427.567749] [tempesta fw] Tempesta FW is ready Apr 26 06:04:37 192.168.122.209 [50428.017019] [tdb] Close table 'client0.tdb' Apr 26 06:04:37 192.168.122.209 [50428.221664] [tdb] Close table 'sessions0.tdb' Apr 26 06:04:40 192.168.122.209 [50431.408270] [tdb] Close table 'cache0.tdb' Apr 26 06:04:41 192.168.122.209 [50431.665196] [tdb] Close table 'filter0.tdb' Apr 26 06:04:41 192.168.122.209 [50431.665773] [tempesta fw] modules are stopped Apr 26 06:04:41 192.168.122.209 [50431.899482] [tempesta fw] exiting... Apr 26 06:04:41 192.168.122.209 [50432.043189] [tdb] Shutdown Tempesta DB Apr 26 06:04:41 192.168.122.209 [50432.248956] End test: t_reconf.test_reconf_base.TestServerReconf.test_conns_n_increase_from_default Apr 26 06:04:41 192.168.122.209 [50432.263280] Start test: t_reconf.test_reconf_base.TestServerReconf.test_remove_server_from_default_srv_group Apr 26 06:04:42 192.168.122.209 [50433.356839] [tdb] Start Tempesta DB Apr 26 06:04:43 192.168.122.209 [50433.512691] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:04:44 192.168.122.209 [50434.756269] [tempesta fw] Configuration processing is completed. Apr 26 06:04:44 192.168.122.209 [50434.808448] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:04:44 192.168.122.209 [50435.231450] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:04:44 192.168.122.209 [50435.259473] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:04:44 192.168.122.209 [50435.286271] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:04:44 192.168.122.209 [50435.371848] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:04:44 192.168.122.209 [50435.419692] [tempesta fw] Tempesta FW is ready Apr 26 06:04:45 192.168.122.209 [50435.837443] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 06:04:45 192.168.122.209 [50435.883757] [tempesta fw] Configuration processing is completed. Apr 26 06:04:45 192.168.122.209 [50436.167866] [tempesta fw] Tempesta FW is ready Apr 26 06:04:46 192.168.122.209 [50436.741803] [tdb] Close table 'client0.tdb' Apr 26 06:04:46 192.168.122.209 [50436.935997] [tdb] Close table 'sessions0.tdb' Apr 26 06:04:49 192.168.122.209 [50440.156939] [tdb] Close table 'cache0.tdb' Apr 26 06:04:49 192.168.122.209 [50440.400210] [tdb] Close table 'filter0.tdb' Apr 26 06:04:49 192.168.122.209 [50440.400669] [tempesta fw] modules are stopped Apr 26 06:04:50 192.168.122.209 [50440.564428] [tempesta fw] exiting... Apr 26 06:04:50 192.168.122.209 [50440.706253] [tdb] Shutdown Tempesta DB Apr 26 06:04:50 192.168.122.209 [50440.903154] End test: t_reconf.test_reconf_base.TestServerReconf.test_remove_server_from_default_srv_group Apr 26 06:04:50 192.168.122.209 [50440.919584] Start test: t_reconf.test_reconf_base.TestServerReconf.test_remove_server_from_srv_group Apr 26 06:04:51 192.168.122.209 [50441.978497] [tdb] Start Tempesta DB Apr 26 06:04:51 192.168.122.209 [50442.122295] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:04:53 192.168.122.209 [50443.763962] [tempesta fw] Configuration processing is completed. Apr 26 06:04:53 192.168.122.209 [50443.813506] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:04:53 192.168.122.209 [50444.231984] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:04:53 192.168.122.209 [50444.295515] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:04:53 192.168.122.209 [50444.321821] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:04:53 192.168.122.209 [50444.391860] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:04:53 192.168.122.209 [50444.431856] [tempesta fw] Tempesta FW is ready Apr 26 06:04:54 192.168.122.209 [50444.990576] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 06:04:54 192.168.122.209 [50445.119935] [tempesta fw] Configuration processing is completed. Apr 26 06:04:54 192.168.122.209 [50445.428111] [tempesta fw] Tempesta FW is ready Apr 26 06:04:55 192.168.122.209 [50445.998627] [tdb] Close table 'client0.tdb' Apr 26 06:04:55 192.168.122.209 [50446.189401] [tdb] Close table 'sessions0.tdb' Apr 26 06:04:58 192.168.122.209 [50449.339091] [tdb] Close table 'cache0.tdb' Apr 26 06:04:59 192.168.122.209 [50449.591869] [tdb] Close table 'filter0.tdb' Apr 26 06:04:59 192.168.122.209 [50449.592305] [tempesta fw] modules are stopped Apr 26 06:04:59 192.168.122.209 [50449.833382] [tempesta fw] exiting... Apr 26 06:04:59 192.168.122.209 [50449.957337] [tdb] Shutdown Tempesta DB Apr 26 06:04:59 192.168.122.209 [50450.163293] End test: t_reconf.test_reconf_base.TestServerReconf.test_remove_server_from_srv_group Apr 26 06:04:59 192.168.122.209 [50450.175931] Start test: t_reconf.test_reconf_base.TestVhostReconf.test_add_vhost Apr 26 06:05:00 192.168.122.209 [50451.107655] [tdb] Start Tempesta DB Apr 26 06:05:00 192.168.122.209 [50451.241910] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:05:02 192.168.122.209 [50452.612463] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50452.612463] Maybe that's fine, but it's worth checking the [50452.612463] config - if there is no relations between the [50452.612463] names, then host name confusion attack is possible. Apr 26 06:05:02 192.168.122.209 [50452.784045] [tempesta fw] Configuration processing is completed. Apr 26 06:05:02 192.168.122.209 [50452.834387] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:05:02 192.168.122.209 [50453.237472] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:05:02 192.168.122.209 [50453.263303] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:05:02 192.168.122.209 [50453.289280] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:05:02 192.168.122.209 [50453.348024] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:05:02 192.168.122.209 [50453.399958] [tempesta fw] Tempesta FW is ready Apr 26 06:05:03 192.168.122.209 [50454.094845] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 06:05:03 192.168.122.209 [50454.116749] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50454.116749] Maybe that's fine, but it's worth checking the [50454.116749] config - if there is no relations between the [50454.116749] names, then host name confusion attack is possible. Apr 26 06:05:03 192.168.122.209 [50454.412031] [tempesta fw] Configuration processing is completed. Apr 26 06:05:04 192.168.122.209 [50454.764457] [tempesta fw] Tempesta FW is ready Apr 26 06:05:04 192.168.122.209 [50455.363613] [tdb] Close table 'client0.tdb' Apr 26 06:05:05 192.168.122.209 [50455.549249] [tdb] Close table 'sessions0.tdb' Apr 26 06:05:08 192.168.122.209 [50458.744497] [tdb] Close table 'cache0.tdb' Apr 26 06:05:08 192.168.122.209 [50458.988006] [tdb] Close table 'filter0.tdb' Apr 26 06:05:08 192.168.122.209 [50458.988438] [tempesta fw] modules are stopped Apr 26 06:05:08 192.168.122.209 [50459.240422] [tempesta fw] exiting... Apr 26 06:05:08 192.168.122.209 [50459.389103] [tdb] Shutdown Tempesta DB Apr 26 06:05:09 192.168.122.209 [50459.600116] End test: t_reconf.test_reconf_base.TestVhostReconf.test_add_vhost Apr 26 06:05:09 192.168.122.209 [50459.626500] Start test: t_reconf.test_reconf_base.TestVhostReconf.test_change_vhost_name Apr 26 06:05:10 192.168.122.209 [50460.659438] [tdb] Start Tempesta DB Apr 26 06:05:10 192.168.122.209 [50460.789658] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:05:11 192.168.122.209 [50462.276363] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50462.276363] Maybe that's fine, but it's worth checking the [50462.276363] config - if there is no relations between the [50462.276363] names, then host name confusion attack is possible. Apr 26 06:05:11 192.168.122.209 [50462.432111] [tempesta fw] Configuration processing is completed. Apr 26 06:05:12 192.168.122.209 [50462.481961] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:05:12 192.168.122.209 [50462.887588] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:05:12 192.168.122.209 [50462.943571] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:05:12 192.168.122.209 [50462.969010] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:05:12 192.168.122.209 [50463.012068] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:05:12 192.168.122.209 [50463.052100] [tempesta fw] Tempesta FW is ready Apr 26 06:05:13 192.168.122.209 [50463.588887] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 06:05:13 192.168.122.209 [50463.609120] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50463.609120] Maybe that's fine, but it's worth checking the [50463.609120] config - if there is no relations between the [50463.609120] names, then host name confusion attack is possible. Apr 26 06:05:13 192.168.122.209 [50463.820167] [tempesta fw] Configuration processing is completed. Apr 26 06:05:13 192.168.122.209 [50464.084558] [tempesta fw] Tempesta FW is ready Apr 26 06:05:14 192.168.122.209 [50464.542696] [tdb] Close table 'client0.tdb' Apr 26 06:05:14 192.168.122.209 [50464.738440] [tdb] Close table 'sessions0.tdb' Apr 26 06:05:17 192.168.122.209 [50467.956715] [tdb] Close table 'cache0.tdb' Apr 26 06:05:17 192.168.122.209 [50468.195250] [tdb] Close table 'filter0.tdb' Apr 26 06:05:17 192.168.122.209 [50468.195678] [tempesta fw] modules are stopped Apr 26 06:05:17 192.168.122.209 [50468.416480] [tempesta fw] exiting... Apr 26 06:05:18 192.168.122.209 [50468.546259] [tdb] Shutdown Tempesta DB Apr 26 06:05:18 192.168.122.209 [50468.757509] End test: t_reconf.test_reconf_base.TestVhostReconf.test_change_vhost_name Apr 26 06:05:18 192.168.122.209 [50468.766456] Start test: t_reconf.test_reconf_base.TestVhostReconf.test_remove_vhost Apr 26 06:05:19 192.168.122.209 [50469.721853] [tdb] Start Tempesta DB Apr 26 06:05:19 192.168.122.209 [50469.856719] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:05:21 192.168.122.209 [50471.482693] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50471.482693] Maybe that's fine, but it's worth checking the [50471.482693] config - if there is no relations between the [50471.482693] names, then host name confusion attack is possible. Apr 26 06:05:21 192.168.122.209 [50471.696059] [tempesta fw] Configuration processing is completed. Apr 26 06:05:21 192.168.122.209 [50471.738951] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:05:21 192.168.122.209 [50472.155961] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:05:21 192.168.122.209 [50472.182331] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:05:21 192.168.122.209 [50472.208439] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:05:21 192.168.122.209 [50472.352240] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:05:22 192.168.122.209 [50472.452221] [tempesta fw] Tempesta FW is ready Apr 26 06:05:22 192.168.122.209 [50473.021196] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 06:05:22 192.168.122.209 [50473.040942] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50473.040942] Maybe that's fine, but it's worth checking the [50473.040942] config - if there is no relations between the [50473.040942] names, then host name confusion attack is possible. Apr 26 06:05:22 192.168.122.209 [50473.256288] [tempesta fw] Configuration processing is completed. Apr 26 06:05:23 192.168.122.209 [50473.588821] [tempesta fw] Tempesta FW is ready Apr 26 06:05:28 192.168.122.209 [50479.105774] [tdb] Close table 'client0.tdb' Apr 26 06:05:28 192.168.122.209 [50479.283685] [tdb] Close table 'sessions0.tdb' Apr 26 06:05:32 192.168.122.209 [50482.465459] [tdb] Close table 'cache0.tdb' Apr 26 06:05:32 192.168.122.209 [50482.703238] [tdb] Close table 'filter0.tdb' Apr 26 06:05:32 192.168.122.209 [50482.703668] [tempesta fw] modules are stopped Apr 26 06:05:32 192.168.122.209 [50482.921856] [tempesta fw] exiting... Apr 26 06:05:32 192.168.122.209 [50483.046747] [tdb] Shutdown Tempesta DB Apr 26 06:05:32 192.168.122.209 [50483.234924] End test: t_reconf.test_reconf_base.TestVhostReconf.test_remove_vhost Apr 26 06:05:32 192.168.122.209 [50483.255618] Start test: t_reconf.test_stress_grace_shutdown.TestGraceShutdownLiveReconf.test_reconf_on_the_fly_for_grace_shutdown Apr 26 06:05:34 192.168.122.209 [50484.508237] [tdb] Start Tempesta DB Apr 26 06:05:34 192.168.122.209 [50484.642976] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:05:36 192.168.122.209 [50486.522108] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50486.522108] Maybe that's fine, but it's worth checking the [50486.522108] config - if there is no relations between the [50486.522108] names, then host name confusion attack is possible. Apr 26 06:05:36 192.168.122.209 [50486.768443] [tempesta fw] Configuration processing is completed. Apr 26 06:05:36 192.168.122.209 [50486.818200] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:05:36 192.168.122.209 [50486.846925] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:05:36 192.168.122.209 [50486.873880] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:05:36 192.168.122.209 [50486.968431] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 06:05:36 192.168.122.209 [50487.017354] [tempesta fw] Tempesta FW is ready Apr 26 06:05:37 192.168.122.209 [50487.496099] [tempesta fw] Warning: frang: max rmisses exceeded for 127.0.0.1: 2 (lim=1) Apr 26 06:05:37 192.168.122.209 [50487.499419] [tempesta fw] Warning: frang: max rmisses exceeded for 127.0.0.1: 2 (lim=1) Apr 26 06:05:37 192.168.122.209 [50487.500324] [tempesta fw] Warning: frang: max rmisses exceeded for 127.0.0.1: 2 (lim=1) Apr 26 06:05:37 192.168.122.209 [50487.501199] [tempesta fw] Warning: frang: max rmisses exceeded for 127.0.0.1: 2 (lim=1) Apr 26 06:05:37 192.168.122.209 [50487.502817] [tempesta fw] Warning: frang: max rmisses exceeded for 127.0.0.1: 2 (lim=1) Apr 26 06:05:37 192.168.122.209 [50487.505544] [tempesta fw] Warning: frang: max rmisses exceeded for 127.0.0.1: 2 (lim=1) Apr 26 06:05:37 192.168.122.209 [50487.507929] [tempesta fw] Warning: frang: max rmisses exceeded for 127.0.0.1: 2 (lim=1) Apr 26 06:05:37 192.168.122.209 [50487.508670] [tempesta fw] Warning: frang: max rmisses exceeded for 127.0.0.1: 2 (lim=1) Apr 26 06:05:37 192.168.122.209 [50487.509546] [tempesta fw] Warning: frang: max rmisses exceeded for 127.0.0.1: 2 (lim=1) Apr 26 06:05:37 192.168.122.209 [50487.512295] [tempesta fw] Warning: frang: max rmisses exceeded for 127.0.0.1: 2 (lim=1) Apr 26 06:05:37 192.168.122.209 [50488.271162] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 06:05:37 192.168.122.209 [50488.297187] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50488.297187] Maybe that's fine, but it's worth checking the [50488.297187] config - if there is no relations between the [50488.297187] names, then host name confusion attack is possible. Apr 26 06:05:38 192.168.122.209 [50488.544450] [tempesta fw] Configuration processing is completed. Apr 26 06:05:38 192.168.122.209 [50488.764428] [tempesta fw] Tempesta FW is ready Apr 26 06:05:47 192.168.122.209 [50498.012025] [tdb] Close table 'client0.tdb' Apr 26 06:05:47 192.168.122.209 [50498.201260] [tdb] Close table 'sessions0.tdb' Apr 26 06:05:47 192.168.122.209 [50498.422909] [tdb] Close table 'filter0.tdb' Apr 26 06:05:47 192.168.122.209 [50498.423353] [tempesta fw] modules are stopped Apr 26 06:05:48 192.168.122.209 [50498.641886] [tempesta fw] exiting... Apr 26 06:05:48 192.168.122.209 [50498.771871] [tdb] Shutdown Tempesta DB Apr 26 06:05:48 192.168.122.209 [50499.003523] End test: t_reconf.test_stress_grace_shutdown.TestGraceShutdownLiveReconf.test_reconf_on_the_fly_for_grace_shutdown Apr 26 06:05:48 192.168.122.209 [50499.023159] Start test: t_reconf.test_stress_reconf.TestLiveReconf.test_stress_reconfig_on_the_fly Apr 26 06:05:49 192.168.122.209 [50500.084655] [tdb] Start Tempesta DB Apr 26 06:05:49 192.168.122.209 [50500.236791] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:05:50 192.168.122.209 [50500.802164] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50500.802164] Maybe that's fine, but it's worth checking the [50500.802164] config - if there is no relations between the [50500.802164] names, then host name confusion attack is possible. Apr 26 06:05:50 192.168.122.209 [50500.932642] [tempesta fw] Configuration processing is completed. Apr 26 06:05:50 192.168.122.209 [50500.987976] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:05:50 192.168.122.209 [50501.020056] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:05:50 192.168.122.209 [50501.057796] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:05:50 192.168.122.209 [50501.100625] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 06:05:50 192.168.122.209 [50501.160595] [tempesta fw] Tempesta FW is ready Apr 26 06:05:54 192.168.122.209 [50505.310608] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 06:05:54 192.168.122.209 [50505.358422] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50505.358422] Maybe that's fine, but it's worth checking the [50505.358422] config - if there is no relations between the [50505.358422] names, then host name confusion attack is possible. Apr 26 06:05:55 192.168.122.209 [50505.533024] [tempesta fw] Configuration processing is completed. Apr 26 06:05:55 192.168.122.209 [50505.680051] [tempesta fw] Warning: request dropped: unable to find an available back end server, status 502: 127.0.0.1 Apr 26 06:05:55 192.168.122.209 [50505.680097] [tempesta fw] Warning: request dropped: unable to find an available back end server, status 502: 127.0.0.1 Apr 26 06:05:55 192.168.122.209 [50505.680318] [tempesta fw] Warning: request dropped: unable to find an available back end server, status 502: 127.0.0.1 Apr 26 06:05:55 192.168.122.209 [50505.680329] [tempesta fw] Warning: request dropped: unable to find an available back end server, status 502: 127.0.0.1 Apr 26 06:05:55 192.168.122.209 [50505.680336] [tempesta fw] Warning: request dropped: unable to find an available back end server, status 502: 127.0.0.1 Apr 26 06:05:55 192.168.122.209 [50505.680344] [tempesta fw] Warning: request dropped: unable to find an available back end server, status 502: 127.0.0.1 Apr 26 06:05:55 192.168.122.209 [50505.680352] [tempesta fw] Warning: request dropped: unable to find an available back end server, status 502: 127.0.0.1 Apr 26 06:05:55 192.168.122.209 [50506.256662] [tempesta fw] Tempesta FW is ready Apr 26 06:06:01 192.168.122.209 [50511.906940] [tdb] Close table 'client0.tdb' Apr 26 06:06:01 192.168.122.209 [50512.103788] [tdb] Close table 'sessions0.tdb' Apr 26 06:06:01 192.168.122.209 [50512.310612] [tdb] Close table 'filter0.tdb' Apr 26 06:06:01 192.168.122.209 [50512.311044] [tempesta fw] modules are stopped Apr 26 06:06:02 192.168.122.209 [50512.498189] [tempesta fw] exiting... Apr 26 06:06:02 192.168.122.209 [50512.640275] [tdb] Shutdown Tempesta DB Apr 26 06:06:02 192.168.122.209 [50512.862959] End test: t_reconf.test_stress_reconf.TestLiveReconf.test_stress_reconfig_on_the_fly Apr 26 06:06:02 192.168.122.209 [50512.876152] Start test: t_reconf.test_stress_sched_dynamic.TestSchedRatioDynamicLiveReconf.test_reconf_on_the_fly_for_dynamic_ratio_sched Apr 26 06:06:04 192.168.122.209 [50515.070526] [tdb] Start Tempesta DB Apr 26 06:06:04 192.168.122.209 [50515.212719] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:06:05 192.168.122.209 [50516.055717] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50516.055717] Maybe that's fine, but it's worth checking the [50516.055717] config - if there is no relations between the [50516.055717] names, then host name confusion attack is possible. Apr 26 06:06:06 192.168.122.209 [50516.460817] [tempesta fw] Configuration processing is completed. Apr 26 06:06:06 192.168.122.209 [50516.511813] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:06:06 192.168.122.209 [50516.540287] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:06:06 192.168.122.209 [50516.576106] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:06:06 192.168.122.209 [50516.844816] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:06:06 192.168.122.209 [50516.944771] [tempesta fw] Tempesta FW is ready Apr 26 06:06:17 192.168.122.209 [50528.208207] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 06:06:17 192.168.122.209 [50528.233961] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50528.233961] Maybe that's fine, but it's worth checking the [50528.233961] config - if there is no relations between the [50528.233961] names, then host name confusion attack is possible. Apr 26 06:06:18 192.168.122.209 [50528.928968] [tempesta fw] Configuration processing is completed. Apr 26 06:06:19 192.168.122.209 [50529.565374] [tempesta fw] Tempesta FW is ready Apr 26 06:06:30 192.168.122.209 [50540.832958] [tdb] Close table 'client0.tdb' Apr 26 06:06:30 192.168.122.209 [50541.051637] [tdb] Close table 'sessions0.tdb' Apr 26 06:06:30 192.168.122.209 [50541.302084] [tdb] Close table 'filter0.tdb' Apr 26 06:06:30 192.168.122.209 [50541.302539] [tempesta fw] modules are stopped Apr 26 06:06:31 192.168.122.209 [50541.512202] [tempesta fw] exiting... Apr 26 06:06:31 192.168.122.209 [50541.663883] [tdb] Shutdown Tempesta DB Apr 26 06:06:31 192.168.122.209 [50542.122771] End test: t_reconf.test_stress_sched_dynamic.TestSchedRatioDynamicLiveReconf.test_reconf_on_the_fly_for_dynamic_ratio_sched Apr 26 06:06:31 192.168.122.209 [50542.138743] Start test: t_reconf.test_stress_sched_hash.TestSchedHashLiveReconf.test_reconf_on_the_fly_for_hash_sched Apr 26 06:06:34 192.168.122.209 [50544.585830] [tdb] Start Tempesta DB Apr 26 06:06:34 192.168.122.209 [50544.778752] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:06:35 192.168.122.209 [50545.653907] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50545.653907] Maybe that's fine, but it's worth checking the [50545.653907] config - if there is no relations between the [50545.653907] names, then host name confusion attack is possible. Apr 26 06:06:35 192.168.122.209 [50545.969204] [tempesta fw] Configuration processing is completed. Apr 26 06:06:35 192.168.122.209 [50546.019734] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:06:35 192.168.122.209 [50546.047693] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:06:35 192.168.122.209 [50546.075355] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:06:35 192.168.122.209 [50546.349284] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 06:06:35 192.168.122.209 [50546.425140] [tempesta fw] Tempesta FW is ready Apr 26 06:06:46 192.168.122.209 [50556.611789] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:06:46 192.168.122.209 [50556.612396] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:06:47 192.168.122.209 [50557.558991] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 06:06:47 192.168.122.209 [50557.593546] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50557.593546] Maybe that's fine, but it's worth checking the [50557.593546] config - if there is no relations between the [50557.593546] names, then host name confusion attack is possible. Apr 26 06:06:47 192.168.122.209 [50557.993410] [tempesta fw] Configuration processing is completed. Apr 26 06:06:48 192.168.122.209 [50558.613678] [tempesta fw] Tempesta FW is ready Apr 26 06:06:59 192.168.122.209 [50569.840947] [tdb] Close table 'client0.tdb' Apr 26 06:06:59 192.168.122.209 [50570.043386] [tdb] Close table 'sessions0.tdb' Apr 26 06:06:59 192.168.122.209 [50570.289251] [tdb] Close table 'filter0.tdb' Apr 26 06:06:59 192.168.122.209 [50570.289714] [tempesta fw] modules are stopped Apr 26 06:07:00 192.168.122.209 [50570.490327] [tempesta fw] exiting... Apr 26 06:07:00 192.168.122.209 [50570.599995] [tdb] Shutdown Tempesta DB Apr 26 06:07:00 192.168.122.209 [50571.019741] End test: t_reconf.test_stress_sched_hash.TestSchedHashLiveReconf.test_reconf_on_the_fly_for_hash_sched Apr 26 06:07:00 192.168.122.209 [50571.030037] Start test: t_reconf.test_stress_sched_http.TestSchedHttpLiveReconf.test_reconfig_on_the_fly_for_sched_http Apr 26 06:07:01 192.168.122.209 [50572.311895] [tdb] Start Tempesta DB Apr 26 06:07:02 192.168.122.209 [50572.464447] net_ratelimit: 877 callbacks suppressed Apr 26 06:07:02 192.168.122.209 [50572.464452] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:07:03 192.168.122.209 [50573.626825] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50573.626825] Maybe that's fine, but it's worth checking the [50573.626825] config - if there is no relations between the [50573.626825] names, then host name confusion attack is possible. Apr 26 06:07:03 192.168.122.209 [50573.781484] [tempesta fw] Configuration processing is completed. Apr 26 06:07:03 192.168.122.209 [50573.829900] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:07:03 192.168.122.209 [50573.862108] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:07:03 192.168.122.209 [50573.894432] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:07:03 192.168.122.209 [50573.957479] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:07:03 192.168.122.209 [50574.033473] [tempesta fw] Tempesta FW is ready Apr 26 06:07:04 192.168.122.209 [50575.288489] [tempesta fw] Warning: request has been filtered out via http table: 127.0.0.1 Apr 26 06:07:06 192.168.122.209 [50576.692137] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 06:07:06 192.168.122.209 [50576.890513] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50576.890513] Maybe that's fine, but it's worth checking the [50576.890513] config - if there is no relations between the [50576.890513] names, then host name confusion attack is possible. Apr 26 06:07:06 192.168.122.209 [50577.098463] [tempesta fw] Configuration processing is completed. Apr 26 06:07:07 192.168.122.209 [50577.446026] [tempesta fw] Tempesta FW is ready Apr 26 06:07:14 192.168.122.209 [50584.820478] [tdb] Close table 'client0.tdb' Apr 26 06:07:14 192.168.122.209 [50585.010628] [tdb] Close table 'sessions0.tdb' Apr 26 06:07:14 192.168.122.209 [50585.248520] [tdb] Close table 'filter0.tdb' Apr 26 06:07:14 192.168.122.209 [50585.248971] [tempesta fw] modules are stopped Apr 26 06:07:15 192.168.122.209 [50585.493124] [tempesta fw] exiting... Apr 26 06:07:15 192.168.122.209 [50585.640715] [tdb] Shutdown Tempesta DB Apr 26 06:07:15 192.168.122.209 [50585.855657] End test: t_reconf.test_stress_sched_http.TestSchedHttpLiveReconf.test_reconfig_on_the_fly_for_sched_http Apr 26 06:07:15 192.168.122.209 [50585.869322] Start test: t_reconf.test_stress_sched_ratio.TestSchedRatioLiveReconf.test_reconf_on_the_fly_for_static_ratio_sched Apr 26 06:07:16 192.168.122.209 [50587.081756] [tdb] Start Tempesta DB Apr 26 06:07:16 192.168.122.209 [50587.243777] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:07:17 192.168.122.209 [50587.951289] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50587.951289] Maybe that's fine, but it's worth checking the [50587.951289] config - if there is no relations between the [50587.951289] names, then host name confusion attack is possible. Apr 26 06:07:17 192.168.122.209 [50588.121699] [tempesta fw] Configuration processing is completed. Apr 26 06:07:17 192.168.122.209 [50588.177813] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:07:17 192.168.122.209 [50588.206151] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:07:17 192.168.122.209 [50588.235431] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:07:17 192.168.122.209 [50588.329733] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 06:07:17 192.168.122.209 [50588.373695] [tempesta fw] Tempesta FW is ready Apr 26 06:07:28 192.168.122.209 [50598.612413] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:07:28 192.168.122.209 [50598.612858] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:07:28 192.168.122.209 [50598.613019] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:07:28 192.168.122.209 [50598.613595] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:07:28 192.168.122.209 [50598.626671] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:07:28 192.168.122.209 [50598.627255] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:07:28 192.168.122.209 [50599.188773] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 06:07:28 192.168.122.209 [50599.239312] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50599.239312] Maybe that's fine, but it's worth checking the [50599.239312] config - if there is no relations between the [50599.239312] names, then host name confusion attack is possible. Apr 26 06:07:28 192.168.122.209 [50599.406193] [tempesta fw] Configuration processing is completed. Apr 26 06:07:29 192.168.122.209 [50599.649850] [tempesta fw] Tempesta FW is ready Apr 26 06:07:39 192.168.122.209 [50609.844563] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:07:39 192.168.122.209 [50609.845162] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:07:39 192.168.122.209 [50609.845165] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:07:39 192.168.122.209 [50609.845169] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:07:39 192.168.122.209 [50609.848953] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:07:39 192.168.122.209 [50609.849517] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:07:39 192.168.122.209 [50609.850071] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:07:39 192.168.122.209 [50609.850165] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:07:39 192.168.122.209 [50609.850168] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:07:39 192.168.122.209 [50609.850345] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:07:39 192.168.122.209 [50609.850840] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:07:39 192.168.122.209 [50609.851380] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:07:39 192.168.122.209 [50609.852854] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:07:39 192.168.122.209 [50609.854741] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:07:39 192.168.122.209 [50609.855131] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:07:39 192.168.122.209 [50609.856046] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:07:39 192.168.122.209 [50609.856285] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:07:39 192.168.122.209 [50609.857347] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:07:39 192.168.122.209 [50609.858306] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:07:39 192.168.122.209 [50609.858574] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:07:39 192.168.122.209 [50609.858870] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:07:39 192.168.122.209 [50609.860176] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:07:39 192.168.122.209 [50609.860186] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:07:39 192.168.122.209 [50609.861467] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:07:39 192.168.122.209 [50609.861670] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:07:39 192.168.122.209 [50609.862319] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:07:39 192.168.122.209 [50609.862806] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:07:39 192.168.122.209 [50609.863077] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:07:39 192.168.122.209 [50609.863392] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:07:39 192.168.122.209 [50609.863400] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:07:39 192.168.122.209 [50609.863403] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:07:39 192.168.122.209 [50609.864154] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:07:39 192.168.122.209 [50609.864267] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:07:39 192.168.122.209 [50609.868035] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:07:39 192.168.122.209 [50610.319570] [tdb] Close table 'client0.tdb' Apr 26 06:07:40 192.168.122.209 [50610.513721] [tdb] Close table 'sessions0.tdb' Apr 26 06:07:40 192.168.122.209 [50610.761611] [tdb] Close table 'filter0.tdb' Apr 26 06:07:40 192.168.122.209 [50610.762448] [tempesta fw] modules are stopped Apr 26 06:07:40 192.168.122.209 [50610.942401] [tempesta fw] exiting... Apr 26 06:07:40 192.168.122.209 [50611.051535] [tdb] Shutdown Tempesta DB Apr 26 06:07:40 192.168.122.209 [50611.335307] End test: t_reconf.test_stress_sched_ratio.TestSchedRatioLiveReconf.test_reconf_on_the_fly_for_static_ratio_sched Apr 26 06:07:40 192.168.122.209 [50611.348105] Start test: t_reconf.test_stress_sticky.TestGraceShutdownLiveReconf.test_reconf_on_the_fly_for_sticky_cookie_sched Apr 26 06:07:42 192.168.122.209 [50612.644044] [tdb] Start Tempesta DB Apr 26 06:07:42 192.168.122.209 [50612.787479] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:07:43 192.168.122.209 [50613.551881] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50613.551881] Maybe that's fine, but it's worth checking the [50613.551881] config - if there is no relations between the [50613.551881] names, then host name confusion attack is possible. Apr 26 06:07:43 192.168.122.209 [50613.794028] [tempesta fw] Configuration processing is completed. Apr 26 06:07:43 192.168.122.209 [50613.846241] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:07:43 192.168.122.209 [50613.877270] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:07:43 192.168.122.209 [50613.905965] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:07:43 192.168.122.209 [50613.998043] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 06:07:43 192.168.122.209 [50614.038014] [tempesta fw] Tempesta FW is ready Apr 26 06:07:48 192.168.122.209 [50619.141543] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 06:07:48 192.168.122.209 [50619.376098] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50619.376098] Maybe that's fine, but it's worth checking the [50619.376098] config - if there is no relations between the [50619.376098] names, then host name confusion attack is possible. Apr 26 06:07:50 192.168.122.209 [50620.605497] [tempesta fw] Configuration processing is completed. Apr 26 06:07:50 192.168.122.209 [50621.342140] [tempesta fw] Warning: request dropped: unable to find an available back end server, status 502: 127.0.0.1 Apr 26 06:07:50 192.168.122.209 [50621.342186] [tempesta fw] Warning: request dropped: unable to find an available back end server, status 502: 127.0.0.1 Apr 26 06:07:50 192.168.122.209 [50621.342816] [tempesta fw] Warning: request dropped: unable to find an available back end server, status 502: 127.0.0.1 Apr 26 06:07:50 192.168.122.209 [50621.342949] [tempesta fw] Warning: request dropped: unable to find an available back end server, status 502: 127.0.0.1 Apr 26 06:07:50 192.168.122.209 [50621.343150] [tempesta fw] Warning: request dropped: unable to find an available back end server, status 502: 127.0.0.1 Apr 26 06:07:50 192.168.122.209 [50621.343176] [tempesta fw] Warning: request dropped: unable to find an available back end server, status 502: 127.0.0.1 Apr 26 06:07:50 192.168.122.209 [50621.343208] [tempesta fw] Warning: request dropped: unable to find an available back end server, status 502: 127.0.0.1 Apr 26 06:07:51 192.168.122.209 [50621.930796] [tempesta fw] Tempesta FW is ready Apr 26 06:07:54 192.168.122.209 [50624.976103] [tdb] Close table 'client0.tdb' Apr 26 06:07:54 192.168.122.209 [50625.202376] [tdb] Close table 'sessions0.tdb' Apr 26 06:07:55 192.168.122.209 [50625.451164] [tdb] Close table 'filter0.tdb' Apr 26 06:07:55 192.168.122.209 [50625.451612] [tempesta fw] modules are stopped Apr 26 06:07:55 192.168.122.209 [50625.701934] [tempesta fw] exiting... Apr 26 06:07:55 192.168.122.209 [50625.814667] [tdb] Shutdown Tempesta DB Apr 26 06:07:55 192.168.122.209 [50626.075110] End test: t_reconf.test_stress_sticky.TestGraceShutdownLiveReconf.test_reconf_on_the_fly_for_sticky_cookie_sched Apr 26 06:07:55 192.168.122.209 [50626.088069] Start test: t_regress.test_reboot_under_load.TestRebootUnderLoadNoTimeoutTfwNoCache.test_reboot_under_load Apr 26 06:07:56 192.168.122.209 [50627.165618] [tdb] Start Tempesta DB Apr 26 06:07:56 192.168.122.209 [50627.330798] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:07:57 192.168.122.209 [50628.019075] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50628.019075] Maybe that's fine, but it's worth checking the [50628.019075] config - if there is no relations between the [50628.019075] names, then host name confusion attack is possible. Apr 26 06:07:57 192.168.122.209 [50628.202146] [tempesta fw] Configuration processing is completed. Apr 26 06:07:57 192.168.122.209 [50628.255851] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:07:57 192.168.122.209 [50628.289382] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:07:57 192.168.122.209 [50628.323515] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:07:57 192.168.122.209 [50628.358158] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 06:07:57 192.168.122.209 [50628.398182] [tempesta fw] Tempesta FW is ready Apr 26 06:08:03 192.168.122.209 [50634.353818] [tdb] Close table 'client0.tdb' Apr 26 06:08:04 192.168.122.209 [50634.556666] [tdb] Close table 'sessions0.tdb' Apr 26 06:08:04 192.168.122.209 [50634.811446] [tdb] Close table 'filter0.tdb' Apr 26 06:08:04 192.168.122.209 [50634.811925] [tempesta fw] modules are stopped Apr 26 06:08:04 192.168.122.209 [50635.013150] [tempesta fw] exiting... Apr 26 06:08:04 192.168.122.209 [50635.173616] [tdb] Shutdown Tempesta DB Apr 26 06:08:05 192.168.122.209 [50636.313479] [tdb] Start Tempesta DB Apr 26 06:08:06 192.168.122.209 [50636.453148] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:08:06 192.168.122.209 [50637.078917] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50637.078917] Maybe that's fine, but it's worth checking the [50637.078917] config - if there is no relations between the [50637.078917] names, then host name confusion attack is possible. Apr 26 06:08:06 192.168.122.209 [50637.250309] [tempesta fw] Configuration processing is completed. Apr 26 06:08:06 192.168.122.209 [50637.309652] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:08:06 192.168.122.209 [50637.348043] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:08:06 192.168.122.209 [50637.383766] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:08:07 192.168.122.209 [50637.450381] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 06:08:07 192.168.122.209 [50637.510229] [tempesta fw] Tempesta FW is ready Apr 26 06:08:07 192.168.122.209 [50638.040677] [tdb] Close table 'client0.tdb' Apr 26 06:08:07 192.168.122.209 [50638.228348] [tdb] Close table 'sessions0.tdb' Apr 26 06:08:08 192.168.122.209 [50638.462881] [tdb] Close table 'filter0.tdb' Apr 26 06:08:08 192.168.122.209 [50638.463321] [tempesta fw] modules are stopped Apr 26 06:08:08 192.168.122.209 [50638.769180] [tempesta fw] exiting... Apr 26 06:08:08 192.168.122.209 [50638.901392] [tdb] Shutdown Tempesta DB Apr 26 06:08:09 192.168.122.209 [50640.029436] [tdb] Start Tempesta DB Apr 26 06:08:09 192.168.122.209 [50640.161825] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:08:10 192.168.122.209 [50640.759450] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50640.759450] Maybe that's fine, but it's worth checking the [50640.759450] config - if there is no relations between the [50640.759450] names, then host name confusion attack is possible. Apr 26 06:08:10 192.168.122.209 [50640.918420] [tempesta fw] Configuration processing is completed. Apr 26 06:08:10 192.168.122.209 [50640.971383] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:08:10 192.168.122.209 [50640.999523] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:08:10 192.168.122.209 [50641.029058] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:08:10 192.168.122.209 [50641.110424] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 06:08:10 192.168.122.209 [50641.162339] [tempesta fw] Tempesta FW is ready Apr 26 06:08:11 192.168.122.209 [50641.670912] [tdb] Close table 'client0.tdb' Apr 26 06:08:11 192.168.122.209 [50641.854231] [tdb] Close table 'sessions0.tdb' Apr 26 06:08:11 192.168.122.209 [50642.066663] [tdb] Close table 'filter0.tdb' Apr 26 06:08:11 192.168.122.209 [50642.067116] [tempesta fw] modules are stopped Apr 26 06:08:11 192.168.122.209 [50642.279089] [tempesta fw] exiting... Apr 26 06:08:11 192.168.122.209 [50642.415460] [tdb] Shutdown Tempesta DB Apr 26 06:08:13 192.168.122.209 [50643.513090] [tdb] Start Tempesta DB Apr 26 06:08:13 192.168.122.209 [50643.650517] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:08:13 192.168.122.209 [50644.230887] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50644.230887] Maybe that's fine, but it's worth checking the [50644.230887] config - if there is no relations between the [50644.230887] names, then host name confusion attack is possible. Apr 26 06:08:13 192.168.122.209 [50644.406420] [tempesta fw] Configuration processing is completed. Apr 26 06:08:14 192.168.122.209 [50644.460669] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:08:14 192.168.122.209 [50644.486331] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:08:14 192.168.122.209 [50644.514362] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:08:14 192.168.122.209 [50644.590425] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 06:08:14 192.168.122.209 [50644.638367] [tempesta fw] Tempesta FW is ready Apr 26 06:08:14 192.168.122.209 [50645.159527] [tdb] Close table 'client0.tdb' Apr 26 06:08:14 192.168.122.209 [50645.342032] [tdb] Close table 'sessions0.tdb' Apr 26 06:08:15 192.168.122.209 [50645.565618] [tdb] Close table 'filter0.tdb' Apr 26 06:08:15 192.168.122.209 [50645.566053] [tempesta fw] modules are stopped Apr 26 06:08:15 192.168.122.209 [50645.764210] [tempesta fw] exiting... Apr 26 06:08:15 192.168.122.209 [50645.878634] [tdb] Shutdown Tempesta DB Apr 26 06:08:16 192.168.122.209 [50646.997975] [tdb] Start Tempesta DB Apr 26 06:08:16 192.168.122.209 [50647.141030] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:08:17 192.168.122.209 [50647.751650] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50647.751650] Maybe that's fine, but it's worth checking the [50647.751650] config - if there is no relations between the [50647.751650] names, then host name confusion attack is possible. Apr 26 06:08:17 192.168.122.209 [50647.934491] [tempesta fw] Configuration processing is completed. Apr 26 06:08:17 192.168.122.209 [50647.990664] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:08:17 192.168.122.209 [50648.016798] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:08:17 192.168.122.209 [50648.047265] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:08:17 192.168.122.209 [50648.122462] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 06:08:17 192.168.122.209 [50648.182415] [tempesta fw] Tempesta FW is ready Apr 26 06:08:18 192.168.122.209 [50648.695745] [tdb] Close table 'client0.tdb' Apr 26 06:08:18 192.168.122.209 [50648.906264] [tdb] Close table 'sessions0.tdb' Apr 26 06:08:18 192.168.122.209 [50649.163985] [tdb] Close table 'filter0.tdb' Apr 26 06:08:18 192.168.122.209 [50649.164439] [tempesta fw] modules are stopped Apr 26 06:08:18 192.168.122.209 [50649.351670] [tempesta fw] exiting... Apr 26 06:08:19 192.168.122.209 [50649.455678] [tdb] Shutdown Tempesta DB Apr 26 06:08:20 192.168.122.209 [50650.549081] [tdb] Start Tempesta DB Apr 26 06:08:20 192.168.122.209 [50650.680023] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:08:20 192.168.122.209 [50651.279594] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50651.279594] Maybe that's fine, but it's worth checking the [50651.279594] config - if there is no relations between the [50651.279594] names, then host name confusion attack is possible. Apr 26 06:08:21 192.168.122.209 [50651.450568] [tempesta fw] Configuration processing is completed. Apr 26 06:08:21 192.168.122.209 [50651.499487] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:08:21 192.168.122.209 [50651.527189] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:08:21 192.168.122.209 [50651.558005] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:08:21 192.168.122.209 [50651.634530] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 06:08:21 192.168.122.209 [50651.694515] [tempesta fw] Tempesta FW is ready Apr 26 06:08:21 192.168.122.209 [50652.226321] [tdb] Close table 'client0.tdb' Apr 26 06:08:21 192.168.122.209 [50652.435134] [tdb] Close table 'sessions0.tdb' Apr 26 06:08:22 192.168.122.209 [50652.680625] [tdb] Close table 'filter0.tdb' Apr 26 06:08:22 192.168.122.209 [50652.681070] [tempesta fw] modules are stopped Apr 26 06:08:22 192.168.122.209 [50652.919715] [tempesta fw] exiting... Apr 26 06:08:22 192.168.122.209 [50653.042837] [tdb] Shutdown Tempesta DB Apr 26 06:08:23 192.168.122.209 [50654.099637] [tdb] Start Tempesta DB Apr 26 06:08:23 192.168.122.209 [50654.247580] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:08:24 192.168.122.209 [50654.835158] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50654.835158] Maybe that's fine, but it's worth checking the [50654.835158] config - if there is no relations between the [50654.835158] names, then host name confusion attack is possible. Apr 26 06:08:24 192.168.122.209 [50654.994526] [tempesta fw] Configuration processing is completed. Apr 26 06:08:24 192.168.122.209 [50655.046697] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:08:24 192.168.122.209 [50655.076282] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:08:24 192.168.122.209 [50655.110723] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:08:24 192.168.122.209 [50655.182573] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 06:08:24 192.168.122.209 [50655.238514] [tempesta fw] Tempesta FW is ready Apr 26 06:08:25 192.168.122.209 [50655.733770] [tdb] Close table 'client0.tdb' Apr 26 06:08:25 192.168.122.209 [50655.952394] [tdb] Close table 'sessions0.tdb' Apr 26 06:08:25 192.168.122.209 [50656.158941] [tdb] Close table 'filter0.tdb' Apr 26 06:08:25 192.168.122.209 [50656.159394] [tempesta fw] modules are stopped Apr 26 06:08:25 192.168.122.209 [50656.384090] [tempesta fw] exiting... Apr 26 06:08:26 192.168.122.209 [50656.530492] [tdb] Shutdown Tempesta DB Apr 26 06:08:27 192.168.122.209 [50657.591628] [tdb] Start Tempesta DB Apr 26 06:08:27 192.168.122.209 [50657.745182] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:08:27 192.168.122.209 [50658.374859] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50658.374859] Maybe that's fine, but it's worth checking the [50658.374859] config - if there is no relations between the [50658.374859] names, then host name confusion attack is possible. Apr 26 06:08:28 192.168.122.209 [50658.542671] [tempesta fw] Configuration processing is completed. Apr 26 06:08:28 192.168.122.209 [50658.590613] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:08:28 192.168.122.209 [50658.616749] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:08:28 192.168.122.209 [50658.648316] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:08:28 192.168.122.209 [50658.730183] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 06:08:28 192.168.122.209 [50658.782570] [tempesta fw] Tempesta FW is ready Apr 26 06:08:28 192.168.122.209 [50659.299362] [tdb] Close table 'client0.tdb' Apr 26 06:08:29 192.168.122.209 [50659.490969] [tdb] Close table 'sessions0.tdb' Apr 26 06:08:29 192.168.122.209 [50659.708301] [tdb] Close table 'filter0.tdb' Apr 26 06:08:29 192.168.122.209 [50659.708757] [tempesta fw] modules are stopped Apr 26 06:08:29 192.168.122.209 [50659.904046] [tempesta fw] exiting... Apr 26 06:08:29 192.168.122.209 [50660.036149] [tdb] Shutdown Tempesta DB Apr 26 06:08:30 192.168.122.209 [50661.090265] [tdb] Start Tempesta DB Apr 26 06:08:30 192.168.122.209 [50661.233168] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:08:31 192.168.122.209 [50661.819163] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50661.819163] Maybe that's fine, but it's worth checking the [50661.819163] config - if there is no relations between the [50661.819163] names, then host name confusion attack is possible. Apr 26 06:08:31 192.168.122.209 [50662.002953] [tempesta fw] Configuration processing is completed. Apr 26 06:08:31 192.168.122.209 [50662.051605] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:08:31 192.168.122.209 [50662.079261] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:08:31 192.168.122.209 [50662.108791] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:08:31 192.168.122.209 [50662.178656] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 06:08:31 192.168.122.209 [50662.242589] [tempesta fw] Tempesta FW is ready Apr 26 06:08:32 192.168.122.209 [50662.803418] [tdb] Close table 'client0.tdb' Apr 26 06:08:32 192.168.122.209 [50662.990088] [tdb] Close table 'sessions0.tdb' Apr 26 06:08:32 192.168.122.209 [50663.229495] [tdb] Close table 'filter0.tdb' Apr 26 06:08:32 192.168.122.209 [50663.229933] [tempesta fw] modules are stopped Apr 26 06:08:33 192.168.122.209 [50663.446473] [tempesta fw] exiting... Apr 26 06:08:33 192.168.122.209 [50663.558923] [tdb] Shutdown Tempesta DB Apr 26 06:08:34 192.168.122.209 [50664.612898] [tdb] Start Tempesta DB Apr 26 06:08:34 192.168.122.209 [50664.752678] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:08:34 192.168.122.209 [50665.335864] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50665.335864] Maybe that's fine, but it's worth checking the [50665.335864] config - if there is no relations between the [50665.335864] names, then host name confusion attack is possible. Apr 26 06:08:35 192.168.122.209 [50665.520131] [tempesta fw] Configuration processing is completed. Apr 26 06:08:35 192.168.122.209 [50665.572209] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:08:35 192.168.122.209 [50665.597947] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:08:35 192.168.122.209 [50665.626700] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:08:35 192.168.122.209 [50665.710738] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 06:08:35 192.168.122.209 [50665.770635] [tempesta fw] Tempesta FW is ready Apr 26 06:08:35 192.168.122.209 [50666.311552] [tdb] Close table 'client0.tdb' Apr 26 06:08:36 192.168.122.209 [50666.525212] [tdb] Close table 'sessions0.tdb' Apr 26 06:08:36 192.168.122.209 [50666.749263] [tdb] Close table 'filter0.tdb' Apr 26 06:08:36 192.168.122.209 [50666.749702] [tempesta fw] modules are stopped Apr 26 06:08:36 192.168.122.209 [50666.942902] [tempesta fw] exiting... Apr 26 06:08:36 192.168.122.209 [50667.058479] [tdb] Shutdown Tempesta DB Apr 26 06:08:37 192.168.122.209 [50668.080041] [tdb] Start Tempesta DB Apr 26 06:08:37 192.168.122.209 [50668.233184] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:08:38 192.168.122.209 [50668.823251] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50668.823251] Maybe that's fine, but it's worth checking the [50668.823251] config - if there is no relations between the [50668.823251] names, then host name confusion attack is possible. Apr 26 06:08:38 192.168.122.209 [50668.998777] [tempesta fw] Configuration processing is completed. Apr 26 06:08:38 192.168.122.209 [50669.050080] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:08:38 192.168.122.209 [50669.078573] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:08:38 192.168.122.209 [50669.109800] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:08:38 192.168.122.209 [50669.198738] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 06:08:38 192.168.122.209 [50669.262681] [tempesta fw] Tempesta FW is ready Apr 26 06:08:39 192.168.122.209 [50669.934589] [tdb] Close table 'client0.tdb' Apr 26 06:08:39 192.168.122.209 [50670.123046] [tdb] Close table 'sessions0.tdb' Apr 26 06:08:39 192.168.122.209 [50670.358979] [tdb] Close table 'filter0.tdb' Apr 26 06:08:39 192.168.122.209 [50670.359429] [tempesta fw] modules are stopped Apr 26 06:08:40 192.168.122.209 [50670.561154] [tempesta fw] exiting... Apr 26 06:08:40 192.168.122.209 [50670.692154] [tdb] Shutdown Tempesta DB Apr 26 06:08:40 192.168.122.209 [50670.935835] End test: t_regress.test_reboot_under_load.TestRebootUnderLoadNoTimeoutTfwNoCache.test_reboot_under_load Apr 26 06:08:40 192.168.122.209 [50670.950595] Start test: t_regress.test_reboot_under_load.TestRebootUnderLoadNoTimeoutTfwWithCache.test_reboot_under_load Apr 26 06:08:41 192.168.122.209 [50672.089590] [tdb] Start Tempesta DB Apr 26 06:08:41 192.168.122.209 [50672.240177] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:08:42 192.168.122.209 [50672.988223] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50672.988223] Maybe that's fine, but it's worth checking the [50672.988223] config - if there is no relations between the [50672.988223] names, then host name confusion attack is possible. Apr 26 06:08:42 192.168.122.209 [50673.186822] [tempesta fw] Configuration processing is completed. Apr 26 06:08:42 192.168.122.209 [50673.239547] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:08:43 192.168.122.209 [50674.004700] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:08:43 192.168.122.209 [50674.054213] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:08:43 192.168.122.209 [50674.106080] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:08:43 192.168.122.209 [50674.154803] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 06:08:43 192.168.122.209 [50674.194745] [tempesta fw] Tempesta FW is ready Apr 26 06:08:49 192.168.122.209 [50680.218395] [tdb] Close table 'client0.tdb' Apr 26 06:08:49 192.168.122.209 [50680.420889] [tdb] Close table 'sessions0.tdb' Apr 26 06:08:53 192.168.122.209 [50683.788622] [tdb] Close table 'cache0.tdb' Apr 26 06:08:53 192.168.122.209 [50684.063710] [tdb] Close table 'filter0.tdb' Apr 26 06:08:53 192.168.122.209 [50684.064259] [tempesta fw] modules are stopped Apr 26 06:08:53 192.168.122.209 [50684.227932] [tempesta fw] exiting... Apr 26 06:08:53 192.168.122.209 [50684.346480] [tdb] Shutdown Tempesta DB Apr 26 06:08:55 192.168.122.209 [50685.466895] [tdb] Start Tempesta DB Apr 26 06:08:55 192.168.122.209 [50685.600660] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:08:56 192.168.122.209 [50687.048136] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50687.048136] Maybe that's fine, but it's worth checking the [50687.048136] config - if there is no relations between the [50687.048136] names, then host name confusion attack is possible. Apr 26 06:08:56 192.168.122.209 [50687.238912] [tempesta fw] Configuration processing is completed. Apr 26 06:08:56 192.168.122.209 [50687.290691] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:08:57 192.168.122.209 [50687.757704] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:08:57 192.168.122.209 [50687.788053] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:08:57 192.168.122.209 [50687.818124] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:08:57 192.168.122.209 [50687.910971] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 06:08:57 192.168.122.209 [50687.962917] [tempesta fw] Tempesta FW is ready Apr 26 06:08:58 192.168.122.209 [50688.484090] [tdb] Close table 'client0.tdb' Apr 26 06:08:58 192.168.122.209 [50688.687784] [tdb] Close table 'sessions0.tdb' Apr 26 06:09:01 192.168.122.209 [50692.057715] [tdb] Close table 'cache0.tdb' Apr 26 06:09:01 192.168.122.209 [50692.330731] [tdb] Close table 'filter0.tdb' Apr 26 06:09:01 192.168.122.209 [50692.331276] [tempesta fw] modules are stopped Apr 26 06:09:02 192.168.122.209 [50692.552667] [tempesta fw] exiting... Apr 26 06:09:02 192.168.122.209 [50692.705631] [tdb] Shutdown Tempesta DB Apr 26 06:09:03 192.168.122.209 [50693.811690] [tdb] Start Tempesta DB Apr 26 06:09:03 192.168.122.209 [50693.951875] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:09:04 192.168.122.209 [50695.384305] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50695.384305] Maybe that's fine, but it's worth checking the [50695.384305] config - if there is no relations between the [50695.384305] names, then host name confusion attack is possible. Apr 26 06:09:05 192.168.122.209 [50695.591079] [tempesta fw] Configuration processing is completed. Apr 26 06:09:05 192.168.122.209 [50695.647772] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:09:05 192.168.122.209 [50696.080953] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:09:05 192.168.122.209 [50696.108882] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:09:05 192.168.122.209 [50696.136382] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:09:05 192.168.122.209 [50696.211091] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 06:09:05 192.168.122.209 [50696.274962] [tempesta fw] Tempesta FW is ready Apr 26 06:09:06 192.168.122.209 [50696.845938] [tdb] Close table 'client0.tdb' Apr 26 06:09:06 192.168.122.209 [50697.023348] [tdb] Close table 'sessions0.tdb' Apr 26 06:09:10 192.168.122.209 [50700.872694] [tdb] Close table 'cache0.tdb' Apr 26 06:09:11 192.168.122.209 [50701.583373] [tdb] Close table 'filter0.tdb' Apr 26 06:09:11 192.168.122.209 [50701.584041] [tempesta fw] modules are stopped Apr 26 06:09:12 192.168.122.209 [50703.314138] [tempesta fw] exiting... Apr 26 06:09:13 192.168.122.209 [50703.867431] [tdb] Shutdown Tempesta DB Apr 26 06:09:15 192.168.122.209 [50705.696942] [tdb] Start Tempesta DB Apr 26 06:09:15 192.168.122.209 [50705.866221] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:09:16 192.168.122.209 [50707.227793] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50707.227793] Maybe that's fine, but it's worth checking the [50707.227793] config - if there is no relations between the [50707.227793] names, then host name confusion attack is possible. Apr 26 06:09:16 192.168.122.209 [50707.407222] [tempesta fw] Configuration processing is completed. Apr 26 06:09:17 192.168.122.209 [50707.459602] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:09:17 192.168.122.209 [50707.865184] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:09:17 192.168.122.209 [50707.921331] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:09:17 192.168.122.209 [50707.946575] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:09:17 192.168.122.209 [50708.027157] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 06:09:17 192.168.122.209 [50708.079201] [tempesta fw] Tempesta FW is ready Apr 26 06:09:18 192.168.122.209 [50708.606058] [tdb] Close table 'client0.tdb' Apr 26 06:09:18 192.168.122.209 [50708.789622] [tdb] Close table 'sessions0.tdb' Apr 26 06:09:21 192.168.122.209 [50712.001796] [tdb] Close table 'cache0.tdb' Apr 26 06:09:21 192.168.122.209 [50712.232475] [tdb] Close table 'filter0.tdb' Apr 26 06:09:21 192.168.122.209 [50712.232922] [tempesta fw] modules are stopped Apr 26 06:09:21 192.168.122.209 [50712.421385] [tempesta fw] exiting... Apr 26 06:09:22 192.168.122.209 [50712.542836] [tdb] Shutdown Tempesta DB Apr 26 06:09:23 192.168.122.209 [50713.593576] [tdb] Start Tempesta DB Apr 26 06:09:23 192.168.122.209 [50713.734832] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:09:24 192.168.122.209 [50715.159686] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50715.159686] Maybe that's fine, but it's worth checking the [50715.159686] config - if there is no relations between the [50715.159686] names, then host name confusion attack is possible. Apr 26 06:09:24 192.168.122.209 [50715.327320] [tempesta fw] Configuration processing is completed. Apr 26 06:09:24 192.168.122.209 [50715.386121] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:09:25 192.168.122.209 [50715.807597] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:09:25 192.168.122.209 [50715.833685] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:09:25 192.168.122.209 [50715.867606] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:09:25 192.168.122.209 [50715.935338] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 06:09:25 192.168.122.209 [50715.991264] [tempesta fw] Tempesta FW is ready Apr 26 06:09:26 192.168.122.209 [50716.525447] [tdb] Close table 'client0.tdb' Apr 26 06:09:26 192.168.122.209 [50716.718379] [tdb] Close table 'sessions0.tdb' Apr 26 06:09:29 192.168.122.209 [50720.029257] [tdb] Close table 'cache0.tdb' Apr 26 06:09:29 192.168.122.209 [50720.262792] [tdb] Close table 'filter0.tdb' Apr 26 06:09:29 192.168.122.209 [50720.263972] [tempesta fw] modules are stopped Apr 26 06:09:30 192.168.122.209 [50720.451150] [tempesta fw] exiting... Apr 26 06:09:30 192.168.122.209 [50720.544251] [tdb] Shutdown Tempesta DB Apr 26 06:09:31 192.168.122.209 [50721.579402] [tdb] Start Tempesta DB Apr 26 06:09:31 192.168.122.209 [50721.718746] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:09:32 192.168.122.209 [50723.204590] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50723.204590] Maybe that's fine, but it's worth checking the [50723.204590] config - if there is no relations between the [50723.204590] names, then host name confusion attack is possible. Apr 26 06:09:32 192.168.122.209 [50723.411445] [tempesta fw] Configuration processing is completed. Apr 26 06:09:33 192.168.122.209 [50723.461755] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:09:33 192.168.122.209 [50723.873985] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:09:33 192.168.122.209 [50723.930788] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:09:33 192.168.122.209 [50723.956605] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:09:33 192.168.122.209 [50724.027570] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 06:09:33 192.168.122.209 [50724.083342] [tempesta fw] Tempesta FW is ready Apr 26 06:09:34 192.168.122.209 [50724.599605] [tdb] Close table 'client0.tdb' Apr 26 06:09:34 192.168.122.209 [50724.795695] [tdb] Close table 'sessions0.tdb' Apr 26 06:09:37 192.168.122.209 [50728.027239] [tdb] Close table 'cache0.tdb' Apr 26 06:09:37 192.168.122.209 [50728.273301] [tdb] Close table 'filter0.tdb' Apr 26 06:09:37 192.168.122.209 [50728.273747] [tempesta fw] modules are stopped Apr 26 06:09:38 192.168.122.209 [50728.472268] [tempesta fw] exiting... Apr 26 06:09:38 192.168.122.209 [50728.603590] [tdb] Shutdown Tempesta DB Apr 26 06:09:39 192.168.122.209 [50729.711333] [tdb] Start Tempesta DB Apr 26 06:09:39 192.168.122.209 [50729.830555] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:09:40 192.168.122.209 [50731.244701] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50731.244701] Maybe that's fine, but it's worth checking the [50731.244701] config - if there is no relations between the [50731.244701] names, then host name confusion attack is possible. Apr 26 06:09:40 192.168.122.209 [50731.439540] [tempesta fw] Configuration processing is completed. Apr 26 06:09:41 192.168.122.209 [50731.503084] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:09:41 192.168.122.209 [50731.963874] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:09:41 192.168.122.209 [50731.993462] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:09:41 192.168.122.209 [50732.022454] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:09:41 192.168.122.209 [50732.099558] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 06:09:41 192.168.122.209 [50732.155474] [tempesta fw] Tempesta FW is ready Apr 26 06:09:42 192.168.122.209 [50732.669835] [tdb] Close table 'client0.tdb' Apr 26 06:09:42 192.168.122.209 [50732.860855] [tdb] Close table 'sessions0.tdb' Apr 26 06:09:45 192.168.122.209 [50736.070227] [tdb] Close table 'cache0.tdb' Apr 26 06:09:45 192.168.122.209 [50736.313101] [tdb] Close table 'filter0.tdb' Apr 26 06:09:45 192.168.122.209 [50736.313551] [tempesta fw] modules are stopped Apr 26 06:09:46 192.168.122.209 [50736.540966] [tempesta fw] exiting... Apr 26 06:09:46 192.168.122.209 [50736.655720] [tdb] Shutdown Tempesta DB Apr 26 06:09:47 192.168.122.209 [50737.686568] [tdb] Start Tempesta DB Apr 26 06:09:47 192.168.122.209 [50737.814678] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:09:48 192.168.122.209 [50739.216278] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50739.216278] Maybe that's fine, but it's worth checking the [50739.216278] config - if there is no relations between the [50739.216278] names, then host name confusion attack is possible. Apr 26 06:09:48 192.168.122.209 [50739.411661] [tempesta fw] Configuration processing is completed. Apr 26 06:09:49 192.168.122.209 [50739.461671] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:09:49 192.168.122.209 [50739.938509] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:09:49 192.168.122.209 [50740.013226] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:09:49 192.168.122.209 [50740.038629] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:09:49 192.168.122.209 [50740.123634] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 06:09:49 192.168.122.209 [50740.179596] [tempesta fw] Tempesta FW is ready Apr 26 06:09:50 192.168.122.209 [50740.697676] [tdb] Close table 'client0.tdb' Apr 26 06:09:50 192.168.122.209 [50740.892690] [tdb] Close table 'sessions0.tdb' Apr 26 06:09:53 192.168.122.209 [50744.276687] [tdb] Close table 'cache0.tdb' Apr 26 06:09:54 192.168.122.209 [50744.502603] [tdb] Close table 'filter0.tdb' Apr 26 06:09:54 192.168.122.209 [50744.503044] [tempesta fw] modules are stopped Apr 26 06:09:54 192.168.122.209 [50744.705403] [tempesta fw] exiting... Apr 26 06:09:54 192.168.122.209 [50744.816768] [tdb] Shutdown Tempesta DB Apr 26 06:09:55 192.168.122.209 [50745.950723] [tdb] Start Tempesta DB Apr 26 06:09:55 192.168.122.209 [50746.084017] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:09:57 192.168.122.209 [50747.528259] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50747.528259] Maybe that's fine, but it's worth checking the [50747.528259] config - if there is no relations between the [50747.528259] names, then host name confusion attack is possible. Apr 26 06:09:57 192.168.122.209 [50747.735730] [tempesta fw] Configuration processing is completed. Apr 26 06:09:57 192.168.122.209 [50747.778301] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:09:57 192.168.122.209 [50748.190894] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:09:57 192.168.122.209 [50748.253258] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:09:57 192.168.122.209 [50748.279171] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:09:57 192.168.122.209 [50748.355883] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 06:09:57 192.168.122.209 [50748.403629] [tempesta fw] Tempesta FW is ready Apr 26 06:09:58 192.168.122.209 [50748.987990] [tdb] Close table 'client0.tdb' Apr 26 06:09:58 192.168.122.209 [50749.180603] [tdb] Close table 'sessions0.tdb' Apr 26 06:10:01 192.168.122.209 [50752.425520] [tdb] Close table 'cache0.tdb' Apr 26 06:10:02 192.168.122.209 [50752.666850] [tdb] Close table 'filter0.tdb' Apr 26 06:10:02 192.168.122.209 [50752.667297] [tempesta fw] modules are stopped Apr 26 06:10:02 192.168.122.209 [50752.872665] [tempesta fw] exiting... Apr 26 06:10:02 192.168.122.209 [50752.998527] [tdb] Shutdown Tempesta DB Apr 26 06:10:03 192.168.122.209 [50754.083070] [tdb] Start Tempesta DB Apr 26 06:10:03 192.168.122.209 [50754.227855] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:10:05 192.168.122.209 [50755.600259] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50755.600259] Maybe that's fine, but it's worth checking the [50755.600259] config - if there is no relations between the [50755.600259] names, then host name confusion attack is possible. Apr 26 06:10:05 192.168.122.209 [50755.815851] [tempesta fw] Configuration processing is completed. Apr 26 06:10:05 192.168.122.209 [50755.874346] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:10:05 192.168.122.209 [50756.304905] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:10:05 192.168.122.209 [50756.331185] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:10:05 192.168.122.209 [50756.365467] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:10:05 192.168.122.209 [50756.431850] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 06:10:06 192.168.122.209 [50756.483808] [tempesta fw] Tempesta FW is ready Apr 26 06:10:06 192.168.122.209 [50757.033067] [tdb] Close table 'client0.tdb' Apr 26 06:10:06 192.168.122.209 [50757.244366] [tdb] Close table 'sessions0.tdb' Apr 26 06:10:10 192.168.122.209 [50760.662606] [tdb] Close table 'cache0.tdb' Apr 26 06:10:10 192.168.122.209 [50760.910435] [tdb] Close table 'filter0.tdb' Apr 26 06:10:10 192.168.122.209 [50760.910883] [tempesta fw] modules are stopped Apr 26 06:10:10 192.168.122.209 [50761.093232] [tempesta fw] exiting... Apr 26 06:10:10 192.168.122.209 [50761.213123] [tdb] Shutdown Tempesta DB Apr 26 06:10:11 192.168.122.209 [50762.316831] [tdb] Start Tempesta DB Apr 26 06:10:12 192.168.122.209 [50762.458992] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:10:13 192.168.122.209 [50763.936444] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50763.936444] Maybe that's fine, but it's worth checking the [50763.936444] config - if there is no relations between the [50763.936444] names, then host name confusion attack is possible. Apr 26 06:10:13 192.168.122.209 [50764.131951] [tempesta fw] Configuration processing is completed. Apr 26 06:10:13 192.168.122.209 [50764.180785] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:10:14 192.168.122.209 [50764.601699] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:10:14 192.168.122.209 [50764.666305] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:10:14 192.168.122.209 [50764.693018] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:10:14 192.168.122.209 [50764.795874] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 06:10:14 192.168.122.209 [50764.859884] [tempesta fw] Tempesta FW is ready Apr 26 06:10:15 192.168.122.209 [50765.507373] [tdb] Close table 'client0.tdb' Apr 26 06:10:15 192.168.122.209 [50765.684833] [tdb] Close table 'sessions0.tdb' Apr 26 06:10:18 192.168.122.209 [50768.929288] [tdb] Close table 'cache0.tdb' Apr 26 06:10:18 192.168.122.209 [50769.154344] [tdb] Close table 'filter0.tdb' Apr 26 06:10:18 192.168.122.209 [50769.154796] [tempesta fw] modules are stopped Apr 26 06:10:18 192.168.122.209 [50769.342021] [tempesta fw] exiting... Apr 26 06:10:19 192.168.122.209 [50769.472429] [tdb] Shutdown Tempesta DB Apr 26 06:10:19 192.168.122.209 [50769.727590] End test: t_regress.test_reboot_under_load.TestRebootUnderLoadNoTimeoutTfwWithCache.test_reboot_under_load Apr 26 06:10:19 192.168.122.209 [50769.740791] Start test: t_regress.test_reboot_under_load.TestRebootUnderLoadTfwNoCache.test_reboot_under_load Apr 26 06:10:20 192.168.122.209 [50770.829019] [tdb] Start Tempesta DB Apr 26 06:10:20 192.168.122.209 [50770.971178] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:10:21 192.168.122.209 [50772.369430] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50772.369430] Maybe that's fine, but it's worth checking the [50772.369430] config - if there is no relations between the [50772.369430] names, then host name confusion attack is possible. Apr 26 06:10:22 192.168.122.209 [50772.567971] [tempesta fw] Configuration processing is completed. Apr 26 06:10:22 192.168.122.209 [50772.629421] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:10:22 192.168.122.209 [50772.672748] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:10:22 192.168.122.209 [50772.719890] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:10:22 192.168.122.209 [50772.759976] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 06:10:22 192.168.122.209 [50772.799992] [tempesta fw] Tempesta FW is ready Apr 26 06:10:32 192.168.122.209 [50782.992827] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50782.993309] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50782.993421] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50782.993983] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.000742] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.000750] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.001303] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.002066] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.002862] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.004366] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.004368] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.004371] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.005212] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.006952] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.006961] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.008250] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.008255] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.009742] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.009745] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.011034] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.011037] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.012341] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.012345] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.013809] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.013818] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.015158] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.015161] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.015164] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.015237] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.015240] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.015316] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.015318] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.015394] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.015395] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.015451] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.015452] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.015515] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.015516] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.015545] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.015547] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.015616] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.015617] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.015686] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.015687] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.015700] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.015702] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.015780] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.015782] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.015799] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.015800] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.015857] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.015859] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.015997] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.033057] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.033066] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.034486] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.034489] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.035774] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.035785] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.037292] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.037301] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.038998] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.039002] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.039006] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.039065] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.039068] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.039194] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.039196] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.039210] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.039212] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.039232] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.039234] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.039255] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.039256] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.040415] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.049090] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.049941] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.050482] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.051291] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.051834] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.052617] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.053164] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.053919] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.054477] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.055263] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.055807] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.056613] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.057158] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.058029] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.058568] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.059333] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.059878] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.060661] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.061212] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.061979] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.062517] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.063318] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.063863] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.064700] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.065241] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.066016] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.066561] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.067379] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.067918] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.068693] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.069232] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.070040] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.070582] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.071365] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.071908] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.072779] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.073317] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.074072] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.074613] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.075367] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.075908] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.076787] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.077327] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.078126] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.078667] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.079425] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.079985] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.080744] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.081280] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.082133] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.082677] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.083434] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.083992] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.084764] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.085300] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.086058] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.086597] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.087351] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.087892] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.088727] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.089272] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.090410] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.090986] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.091788] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.092352] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.093145] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.093700] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.094475] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.095027] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.095832] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.096403] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.097269] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.097822] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.098597] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.099147] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.099947] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.100508] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.101292] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.101853] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.102620] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.103170] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.104049] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.104600] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.105419] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.105977] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.106765] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.107319] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.108120] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.108674] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.109454] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.110017] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.110791] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.111338] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.112135] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.112688] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.113473] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.114026] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.114808] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.115362] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.116217] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.116779] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.117549] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.118109] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.118891] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.119441] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.120237] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.120801] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.121569] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.122121] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.122897] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.123443] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.124234] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.124790] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.125562] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.126118] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.126978] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.127532] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.128359] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.128912] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.129684] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.130240] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.131028] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.131579] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.132402] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.132952] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.133805] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.134361] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.135165] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.135716] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.136504] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.137063] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.137849] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.138402] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.139213] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.139766] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.140576] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.141131] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.141950] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.142508] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.143292] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.143847] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.144634] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.145196] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.145984] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.146532] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.147349] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.147904] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.148699] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.149255] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.150123] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.150679] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.151476] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.152046] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.152834] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.153381] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.154169] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.154723] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.155501] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.156077] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.156924] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.157473] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.158576] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.159131] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.159927] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.160494] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.161278] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.161838] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.162606] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.163159] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.163976] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.164530] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.165306] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.165859] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.166739] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.167289] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.168072] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.168617] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.169430] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.169982] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.170822] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.171368] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.172158] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.172719] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.173507] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.174062] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.174903] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.175453] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.176323] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.176879] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.177719] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.178270] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.179123] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.179671] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.180718] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.181274] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.182208] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.182761] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.184088] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.184646] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.185422] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.185973] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:32 192.168.122.209 [50783.186881] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:10:32 192.168.122.209 [50783.187434] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:10:33 192.168.122.209 [50783.722098] [tdb] Close table 'client0.tdb' Apr 26 06:10:33 192.168.122.209 [50783.926951] [tdb] Close table 'sessions0.tdb' Apr 26 06:10:33 192.168.122.209 [50784.162492] [tdb] Close table 'filter0.tdb' Apr 26 06:10:33 192.168.122.209 [50784.162925] [tempesta fw] modules are stopped Apr 26 06:10:33 192.168.122.209 [50784.366393] [tempesta fw] exiting... Apr 26 06:10:34 192.168.122.209 [50784.499604] [tdb] Shutdown Tempesta DB Apr 26 06:10:35 192.168.122.209 [50785.626169] [tdb] Start Tempesta DB Apr 26 06:10:35 192.168.122.209 [50785.758887] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:10:35 192.168.122.209 [50786.384821] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50786.384821] Maybe that's fine, but it's worth checking the [50786.384821] config - if there is no relations between the [50786.384821] names, then host name confusion attack is possible. Apr 26 06:10:36 192.168.122.209 [50786.560226] [tempesta fw] Configuration processing is completed. Apr 26 06:10:36 192.168.122.209 [50786.609700] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:10:36 192.168.122.209 [50786.635084] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:10:36 192.168.122.209 [50786.660325] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:10:36 192.168.122.209 [50786.720238] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 06:10:36 192.168.122.209 [50786.772168] [tempesta fw] Tempesta FW is ready Apr 26 06:10:46 192.168.122.209 [50797.358524] [tdb] Close table 'client0.tdb' Apr 26 06:10:47 192.168.122.209 [50797.562734] [tdb] Close table 'sessions0.tdb' Apr 26 06:10:47 192.168.122.209 [50797.810950] [tdb] Close table 'filter0.tdb' Apr 26 06:10:47 192.168.122.209 [50797.811417] [tempesta fw] modules are stopped Apr 26 06:10:47 192.168.122.209 [50798.024398] [tempesta fw] exiting... Apr 26 06:10:47 192.168.122.209 [50798.149612] [tdb] Shutdown Tempesta DB Apr 26 06:10:48 192.168.122.209 [50799.221262] [tdb] Start Tempesta DB Apr 26 06:10:48 192.168.122.209 [50799.365938] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:10:49 192.168.122.209 [50799.965065] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50799.965065] Maybe that's fine, but it's worth checking the [50799.965065] config - if there is no relations between the [50799.965065] names, then host name confusion attack is possible. Apr 26 06:10:49 192.168.122.209 [50800.152421] [tempesta fw] Configuration processing is completed. Apr 26 06:10:49 192.168.122.209 [50800.208349] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:10:49 192.168.122.209 [50800.234167] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:10:49 192.168.122.209 [50800.259621] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:10:49 192.168.122.209 [50800.336406] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 06:10:49 192.168.122.209 [50800.388340] [tempesta fw] Tempesta FW is ready Apr 26 06:11:00 192.168.122.209 [50810.955485] [tdb] Close table 'client0.tdb' Apr 26 06:11:00 192.168.122.209 [50811.164027] [tdb] Close table 'sessions0.tdb' Apr 26 06:11:00 192.168.122.209 [50811.397058] [tdb] Close table 'filter0.tdb' Apr 26 06:11:00 192.168.122.209 [50811.397503] [tempesta fw] modules are stopped Apr 26 06:11:01 192.168.122.209 [50811.602454] [tempesta fw] exiting... Apr 26 06:11:01 192.168.122.209 [50811.738616] [tdb] Shutdown Tempesta DB Apr 26 06:11:02 192.168.122.209 [50812.822092] [tdb] Start Tempesta DB Apr 26 06:11:02 192.168.122.209 [50812.971678] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:11:03 192.168.122.209 [50813.557772] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50813.557772] Maybe that's fine, but it's worth checking the [50813.557772] config - if there is no relations between the [50813.557772] names, then host name confusion attack is possible. Apr 26 06:11:03 192.168.122.209 [50813.776569] [tempesta fw] Configuration processing is completed. Apr 26 06:11:03 192.168.122.209 [50813.826241] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:11:03 192.168.122.209 [50813.854606] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:11:03 192.168.122.209 [50813.879693] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:11:03 192.168.122.209 [50813.956568] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 06:11:03 192.168.122.209 [50814.012500] [tempesta fw] Tempesta FW is ready Apr 26 06:11:14 192.168.122.209 [50824.565723] [tdb] Close table 'client0.tdb' Apr 26 06:11:14 192.168.122.209 [50824.771524] [tdb] Close table 'sessions0.tdb' Apr 26 06:11:14 192.168.122.209 [50824.995183] [tdb] Close table 'filter0.tdb' Apr 26 06:11:14 192.168.122.209 [50824.995647] [tempesta fw] modules are stopped Apr 26 06:11:14 192.168.122.209 [50825.187607] [tempesta fw] exiting... Apr 26 06:11:14 192.168.122.209 [50825.297940] [tdb] Shutdown Tempesta DB Apr 26 06:11:15 192.168.122.209 [50826.379369] [tdb] Start Tempesta DB Apr 26 06:11:16 192.168.122.209 [50826.514754] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:11:16 192.168.122.209 [50827.174013] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50827.174013] Maybe that's fine, but it's worth checking the [50827.174013] config - if there is no relations between the [50827.174013] names, then host name confusion attack is possible. Apr 26 06:11:16 192.168.122.209 [50827.352762] [tempesta fw] Configuration processing is completed. Apr 26 06:11:16 192.168.122.209 [50827.402160] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:11:16 192.168.122.209 [50827.428558] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:11:17 192.168.122.209 [50827.454523] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:11:17 192.168.122.209 [50827.520712] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 06:11:17 192.168.122.209 [50827.584736] [tempesta fw] Tempesta FW is ready Apr 26 06:11:27 192.168.122.209 [50838.171309] [tdb] Close table 'client0.tdb' Apr 26 06:11:27 192.168.122.209 [50838.379042] [tdb] Close table 'sessions0.tdb' Apr 26 06:11:28 192.168.122.209 [50838.608376] [tdb] Close table 'filter0.tdb' Apr 26 06:11:28 192.168.122.209 [50838.609207] [tempesta fw] modules are stopped Apr 26 06:11:28 192.168.122.209 [50838.802953] [tempesta fw] exiting... Apr 26 06:11:28 192.168.122.209 [50838.937962] [tdb] Shutdown Tempesta DB Apr 26 06:11:29 192.168.122.209 [50840.004754] [tdb] Start Tempesta DB Apr 26 06:11:29 192.168.122.209 [50840.174518] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:11:30 192.168.122.209 [50840.813648] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50840.813648] Maybe that's fine, but it's worth checking the [50840.813648] config - if there is no relations between the [50840.813648] names, then host name confusion attack is possible. Apr 26 06:11:30 192.168.122.209 [50840.996922] [tempesta fw] Configuration processing is completed. Apr 26 06:11:30 192.168.122.209 [50841.047062] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:11:30 192.168.122.209 [50841.075274] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:11:30 192.168.122.209 [50841.101066] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:11:30 192.168.122.209 [50841.160984] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 06:11:30 192.168.122.209 [50841.216850] [tempesta fw] Tempesta FW is ready Apr 26 06:11:41 192.168.122.209 [50851.856392] [tdb] Close table 'client0.tdb' Apr 26 06:11:41 192.168.122.209 [50852.084728] [tdb] Close table 'sessions0.tdb' Apr 26 06:11:41 192.168.122.209 [50852.339965] [tdb] Close table 'filter0.tdb' Apr 26 06:11:41 192.168.122.209 [50852.340413] [tempesta fw] modules are stopped Apr 26 06:11:42 192.168.122.209 [50852.522369] [tempesta fw] exiting... Apr 26 06:11:42 192.168.122.209 [50852.709839] [tdb] Shutdown Tempesta DB Apr 26 06:11:43 192.168.122.209 [50853.813852] [tdb] Start Tempesta DB Apr 26 06:11:43 192.168.122.209 [50853.968923] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:11:44 192.168.122.209 [50854.589944] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50854.589944] Maybe that's fine, but it's worth checking the [50854.589944] config - if there is no relations between the [50854.589944] names, then host name confusion attack is possible. Apr 26 06:11:44 192.168.122.209 [50854.761207] [tempesta fw] Configuration processing is completed. Apr 26 06:11:44 192.168.122.209 [50854.812140] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:11:44 192.168.122.209 [50854.838478] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:11:44 192.168.122.209 [50854.864754] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:11:44 192.168.122.209 [50854.933149] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 06:11:44 192.168.122.209 [50854.985046] [tempesta fw] Tempesta FW is ready Apr 26 06:11:55 192.168.122.209 [50865.588139] [tdb] Close table 'client0.tdb' Apr 26 06:11:55 192.168.122.209 [50865.780427] [tdb] Close table 'sessions0.tdb' Apr 26 06:11:55 192.168.122.209 [50866.010076] [tdb] Close table 'filter0.tdb' Apr 26 06:11:55 192.168.122.209 [50866.010516] [tempesta fw] modules are stopped Apr 26 06:11:55 192.168.122.209 [50866.209049] [tempesta fw] exiting... Apr 26 06:11:55 192.168.122.209 [50866.327461] [tdb] Shutdown Tempesta DB Apr 26 06:11:56 192.168.122.209 [50867.392773] [tdb] Start Tempesta DB Apr 26 06:11:57 192.168.122.209 [50867.547671] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:11:57 192.168.122.209 [50868.146386] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50868.146386] Maybe that's fine, but it's worth checking the [50868.146386] config - if there is no relations between the [50868.146386] names, then host name confusion attack is possible. Apr 26 06:11:57 192.168.122.209 [50868.333282] [tempesta fw] Configuration processing is completed. Apr 26 06:11:57 192.168.122.209 [50868.388172] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:11:57 192.168.122.209 [50868.415565] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:11:57 192.168.122.209 [50868.440841] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:11:58 192.168.122.209 [50868.525247] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 06:11:58 192.168.122.209 [50868.581196] [tempesta fw] Tempesta FW is ready Apr 26 06:12:08 192.168.122.209 [50879.154011] [tdb] Close table 'client0.tdb' Apr 26 06:12:08 192.168.122.209 [50879.342533] [tdb] Close table 'sessions0.tdb' Apr 26 06:12:09 192.168.122.209 [50879.580065] [tdb] Close table 'filter0.tdb' Apr 26 06:12:09 192.168.122.209 [50879.580508] [tempesta fw] modules are stopped Apr 26 06:12:09 192.168.122.209 [50879.815148] [tempesta fw] exiting... Apr 26 06:12:09 192.168.122.209 [50879.977853] [tdb] Shutdown Tempesta DB Apr 26 06:12:10 192.168.122.209 [50881.014440] [tdb] Start Tempesta DB Apr 26 06:12:10 192.168.122.209 [50881.144648] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:12:11 192.168.122.209 [50881.758358] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50881.758358] Maybe that's fine, but it's worth checking the [50881.758358] config - if there is no relations between the [50881.758358] names, then host name confusion attack is possible. Apr 26 06:12:11 192.168.122.209 [50881.945420] [tempesta fw] Configuration processing is completed. Apr 26 06:12:11 192.168.122.209 [50881.999813] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:12:11 192.168.122.209 [50882.025339] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:12:11 192.168.122.209 [50882.050601] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:12:11 192.168.122.209 [50882.141530] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 06:12:11 192.168.122.209 [50882.193363] [tempesta fw] Tempesta FW is ready Apr 26 06:12:22 192.168.122.209 [50892.799667] [tdb] Close table 'client0.tdb' Apr 26 06:12:22 192.168.122.209 [50892.993428] [tdb] Close table 'sessions0.tdb' Apr 26 06:12:22 192.168.122.209 [50893.225483] [tdb] Close table 'filter0.tdb' Apr 26 06:12:22 192.168.122.209 [50893.225910] [tempesta fw] modules are stopped Apr 26 06:12:22 192.168.122.209 [50893.399051] [tempesta fw] exiting... Apr 26 06:12:23 192.168.122.209 [50893.548369] [tdb] Shutdown Tempesta DB Apr 26 06:12:24 192.168.122.209 [50894.607578] [tdb] Start Tempesta DB Apr 26 06:12:24 192.168.122.209 [50894.744398] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:12:24 192.168.122.209 [50895.323352] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50895.323352] Maybe that's fine, but it's worth checking the [50895.323352] config - if there is no relations between the [50895.323352] names, then host name confusion attack is possible. Apr 26 06:12:25 192.168.122.209 [50895.485604] [tempesta fw] Configuration processing is completed. Apr 26 06:12:25 192.168.122.209 [50895.535533] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:12:25 192.168.122.209 [50895.563112] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:12:25 192.168.122.209 [50895.587976] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:12:25 192.168.122.209 [50895.669687] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 06:12:25 192.168.122.209 [50895.725529] [tempesta fw] Tempesta FW is ready Apr 26 06:12:35 192.168.122.209 [50906.307245] [tdb] Close table 'client0.tdb' Apr 26 06:12:36 192.168.122.209 [50906.507712] [tdb] Close table 'sessions0.tdb' Apr 26 06:12:36 192.168.122.209 [50906.748833] [tdb] Close table 'filter0.tdb' Apr 26 06:12:36 192.168.122.209 [50906.749270] [tempesta fw] modules are stopped Apr 26 06:12:36 192.168.122.209 [50906.975281] [tempesta fw] exiting... Apr 26 06:12:36 192.168.122.209 [50907.123752] [tdb] Shutdown Tempesta DB Apr 26 06:12:37 192.168.122.209 [50908.181590] [tdb] Start Tempesta DB Apr 26 06:12:37 192.168.122.209 [50908.310632] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:12:38 192.168.122.209 [50908.906933] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50908.906933] Maybe that's fine, but it's worth checking the [50908.906933] config - if there is no relations between the [50908.906933] names, then host name confusion attack is possible. Apr 26 06:12:38 192.168.122.209 [50909.069765] [tempesta fw] Configuration processing is completed. Apr 26 06:12:38 192.168.122.209 [50909.118766] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:12:38 192.168.122.209 [50909.144251] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:12:38 192.168.122.209 [50909.170533] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:12:38 192.168.122.209 [50909.261780] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 06:12:38 192.168.122.209 [50909.309713] [tempesta fw] Tempesta FW is ready Apr 26 06:12:39 192.168.122.209 [50909.955583] [tdb] Close table 'client0.tdb' Apr 26 06:12:39 192.168.122.209 [50910.141638] [tdb] Close table 'sessions0.tdb' Apr 26 06:12:39 192.168.122.209 [50910.380628] [tdb] Close table 'filter0.tdb' Apr 26 06:12:39 192.168.122.209 [50910.381186] [tempesta fw] modules are stopped Apr 26 06:12:40 192.168.122.209 [50910.582973] [tempesta fw] exiting... Apr 26 06:12:40 192.168.122.209 [50910.672610] [tdb] Shutdown Tempesta DB Apr 26 06:12:40 192.168.122.209 [50910.920028] End test: t_regress.test_reboot_under_load.TestRebootUnderLoadTfwNoCache.test_reboot_under_load Apr 26 06:12:40 192.168.122.209 [50910.931892] Start test: t_regress.test_reboot_under_load.TestRebootUnderLoadTfwWithCache.test_reboot_under_load Apr 26 06:12:41 192.168.122.209 [50911.969252] [tdb] Start Tempesta DB Apr 26 06:12:41 192.168.122.209 [50912.110406] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:12:42 192.168.122.209 [50912.851124] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50912.851124] Maybe that's fine, but it's worth checking the [50912.851124] config - if there is no relations between the [50912.851124] names, then host name confusion attack is possible. Apr 26 06:12:42 192.168.122.209 [50913.037830] [tempesta fw] Configuration processing is completed. Apr 26 06:12:42 192.168.122.209 [50913.091811] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:12:43 192.168.122.209 [50913.791793] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:12:43 192.168.122.209 [50913.844851] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:12:43 192.168.122.209 [50913.888578] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:12:43 192.168.122.209 [50913.933817] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 06:12:43 192.168.122.209 [50913.981821] [tempesta fw] Tempesta FW is ready Apr 26 06:12:54 192.168.122.209 [50924.975139] [tdb] Close table 'client0.tdb' Apr 26 06:12:54 192.168.122.209 [50925.166746] [tdb] Close table 'sessions0.tdb' Apr 26 06:12:57 192.168.122.209 [50928.394298] [tdb] Close table 'cache0.tdb' Apr 26 06:12:58 192.168.122.209 [50928.619576] [tdb] Close table 'filter0.tdb' Apr 26 06:12:58 192.168.122.209 [50928.620005] [tempesta fw] modules are stopped Apr 26 06:12:58 192.168.122.209 [50928.842931] [tempesta fw] exiting... Apr 26 06:12:58 192.168.122.209 [50928.985128] [tdb] Shutdown Tempesta DB Apr 26 06:12:59 192.168.122.209 [50930.042857] [tdb] Start Tempesta DB Apr 26 06:12:59 192.168.122.209 [50930.186597] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:13:01 192.168.122.209 [50931.527627] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50931.527627] Maybe that's fine, but it's worth checking the [50931.527627] config - if there is no relations between the [50931.527627] names, then host name confusion attack is possible. Apr 26 06:13:01 192.168.122.209 [50931.714051] [tempesta fw] Configuration processing is completed. Apr 26 06:13:01 192.168.122.209 [50931.763776] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:13:01 192.168.122.209 [50932.181615] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:13:01 192.168.122.209 [50932.238309] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:13:01 192.168.122.209 [50932.270583] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:13:01 192.168.122.209 [50932.342037] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 06:13:01 192.168.122.209 [50932.409998] [tempesta fw] Tempesta FW is ready Apr 26 06:13:12 192.168.122.209 [50942.925463] [tdb] Close table 'client0.tdb' Apr 26 06:13:12 192.168.122.209 [50943.113867] [tdb] Close table 'sessions0.tdb' Apr 26 06:13:15 192.168.122.209 [50946.312540] [tdb] Close table 'cache0.tdb' Apr 26 06:13:16 192.168.122.209 [50946.535847] [tdb] Close table 'filter0.tdb' Apr 26 06:13:16 192.168.122.209 [50946.536275] [tempesta fw] modules are stopped Apr 26 06:13:16 192.168.122.209 [50946.725578] [tempesta fw] exiting... Apr 26 06:13:16 192.168.122.209 [50946.876513] [tdb] Shutdown Tempesta DB Apr 26 06:13:17 192.168.122.209 [50947.893860] [tdb] Start Tempesta DB Apr 26 06:13:17 192.168.122.209 [50948.028165] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:13:19 192.168.122.209 [50949.462784] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50949.462784] Maybe that's fine, but it's worth checking the [50949.462784] config - if there is no relations between the [50949.462784] names, then host name confusion attack is possible. Apr 26 06:13:19 192.168.122.209 [50949.626301] [tempesta fw] Configuration processing is completed. Apr 26 06:13:19 192.168.122.209 [50949.675677] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:13:19 192.168.122.209 [50950.098357] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:13:19 192.168.122.209 [50950.123789] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:13:19 192.168.122.209 [50950.149522] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:13:19 192.168.122.209 [50950.246276] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 06:13:19 192.168.122.209 [50950.306241] [tempesta fw] Tempesta FW is ready Apr 26 06:13:30 192.168.122.209 [50960.877844] [tdb] Close table 'client0.tdb' Apr 26 06:13:30 192.168.122.209 [50961.080862] [tdb] Close table 'sessions0.tdb' Apr 26 06:13:33 192.168.122.209 [50964.273819] [tdb] Close table 'cache0.tdb' Apr 26 06:13:34 192.168.122.209 [50964.517217] [tdb] Close table 'filter0.tdb' Apr 26 06:13:34 192.168.122.209 [50964.517656] [tempesta fw] modules are stopped Apr 26 06:13:34 192.168.122.209 [50964.714860] [tempesta fw] exiting... Apr 26 06:13:34 192.168.122.209 [50964.831577] [tdb] Shutdown Tempesta DB Apr 26 06:13:35 192.168.122.209 [50965.906217] [tdb] Start Tempesta DB Apr 26 06:13:35 192.168.122.209 [50966.039868] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:13:36 192.168.122.209 [50967.403671] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50967.403671] Maybe that's fine, but it's worth checking the [50967.403671] config - if there is no relations between the [50967.403671] names, then host name confusion attack is possible. Apr 26 06:13:37 192.168.122.209 [50967.602499] [tempesta fw] Configuration processing is completed. Apr 26 06:13:37 192.168.122.209 [50967.651523] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:13:37 192.168.122.209 [50968.067866] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:13:37 192.168.122.209 [50968.094461] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:13:37 192.168.122.209 [50968.120336] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:13:37 192.168.122.209 [50968.190524] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 06:13:37 192.168.122.209 [50968.246494] [tempesta fw] Tempesta FW is ready Apr 26 06:13:48 192.168.122.209 [50978.796655] [tdb] Close table 'client0.tdb' Apr 26 06:13:48 192.168.122.209 [50978.975176] [tdb] Close table 'sessions0.tdb' Apr 26 06:13:51 192.168.122.209 [50982.268063] [tdb] Close table 'cache0.tdb' Apr 26 06:13:52 192.168.122.209 [50982.504127] [tdb] Close table 'filter0.tdb' Apr 26 06:13:52 192.168.122.209 [50982.504611] [tempesta fw] modules are stopped Apr 26 06:13:52 192.168.122.209 [50982.726722] [tempesta fw] exiting... Apr 26 06:13:52 192.168.122.209 [50982.877368] [tdb] Shutdown Tempesta DB Apr 26 06:13:53 192.168.122.209 [50983.935011] [tdb] Start Tempesta DB Apr 26 06:13:53 192.168.122.209 [50984.079169] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:13:55 192.168.122.209 [50985.555435] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [50985.555435] Maybe that's fine, but it's worth checking the [50985.555435] config - if there is no relations between the [50985.555435] names, then host name confusion attack is possible. Apr 26 06:13:55 192.168.122.209 [50985.754748] [tempesta fw] Configuration processing is completed. Apr 26 06:13:55 192.168.122.209 [50985.803824] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:13:55 192.168.122.209 [50986.259453] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:13:55 192.168.122.209 [50986.289687] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:13:55 192.168.122.209 [50986.320211] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:13:55 192.168.122.209 [50986.394782] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 06:13:56 192.168.122.209 [50986.454679] [tempesta fw] Tempesta FW is ready Apr 26 06:14:06 192.168.122.209 [50997.054328] [tdb] Close table 'client0.tdb' Apr 26 06:14:06 192.168.122.209 [50997.256640] [tdb] Close table 'sessions0.tdb' Apr 26 06:14:10 192.168.122.209 [51000.651985] [tdb] Close table 'cache0.tdb' Apr 26 06:14:10 192.168.122.209 [51000.897112] [tdb] Close table 'filter0.tdb' Apr 26 06:14:10 192.168.122.209 [51000.897600] [tempesta fw] modules are stopped Apr 26 06:14:10 192.168.122.209 [51001.128617] [tempesta fw] exiting... Apr 26 06:14:10 192.168.122.209 [51001.264811] [tdb] Shutdown Tempesta DB Apr 26 06:14:11 192.168.122.209 [51002.377892] [tdb] Start Tempesta DB Apr 26 06:14:12 192.168.122.209 [51002.545676] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:14:13 192.168.122.209 [51004.052269] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [51004.052269] Maybe that's fine, but it's worth checking the [51004.052269] config - if there is no relations between the [51004.052269] names, then host name confusion attack is possible. Apr 26 06:14:13 192.168.122.209 [51004.251034] [tempesta fw] Configuration processing is completed. Apr 26 06:14:13 192.168.122.209 [51004.311136] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:14:14 192.168.122.209 [51004.747493] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:14:14 192.168.122.209 [51004.774016] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:14:14 192.168.122.209 [51004.801165] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:14:14 192.168.122.209 [51004.894955] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 06:14:14 192.168.122.209 [51004.950915] [tempesta fw] Tempesta FW is ready Apr 26 06:14:25 192.168.122.209 [51015.514151] [tdb] Close table 'client0.tdb' Apr 26 06:14:25 192.168.122.209 [51015.718620] [tdb] Close table 'sessions0.tdb' Apr 26 06:14:28 192.168.122.209 [51019.209458] [tdb] Close table 'cache0.tdb' Apr 26 06:14:29 192.168.122.209 [51019.494030] [tdb] Close table 'filter0.tdb' Apr 26 06:14:29 192.168.122.209 [51019.494471] [tempesta fw] modules are stopped Apr 26 06:14:29 192.168.122.209 [51019.720436] [tempesta fw] exiting... Apr 26 06:14:29 192.168.122.209 [51019.841385] [tdb] Shutdown Tempesta DB Apr 26 06:14:30 192.168.122.209 [51020.901072] [tdb] Start Tempesta DB Apr 26 06:14:30 192.168.122.209 [51021.043712] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:14:32 192.168.122.209 [51022.456137] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [51022.456137] Maybe that's fine, but it's worth checking the [51022.456137] config - if there is no relations between the [51022.456137] names, then host name confusion attack is possible. Apr 26 06:14:32 192.168.122.209 [51022.647210] [tempesta fw] Configuration processing is completed. Apr 26 06:14:32 192.168.122.209 [51022.696724] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:14:32 192.168.122.209 [51023.118981] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:14:32 192.168.122.209 [51023.145611] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:14:32 192.168.122.209 [51023.171684] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:14:32 192.168.122.209 [51023.255201] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 06:14:32 192.168.122.209 [51023.307141] [tempesta fw] Tempesta FW is ready Apr 26 06:14:43 192.168.122.209 [51033.844638] [tdb] Close table 'client0.tdb' Apr 26 06:14:43 192.168.122.209 [51034.031860] [tdb] Close table 'sessions0.tdb' Apr 26 06:14:46 192.168.122.209 [51037.241497] [tdb] Close table 'cache0.tdb' Apr 26 06:14:47 192.168.122.209 [51037.488138] [tdb] Close table 'filter0.tdb' Apr 26 06:14:47 192.168.122.209 [51037.488572] [tempesta fw] modules are stopped Apr 26 06:14:47 192.168.122.209 [51037.671768] [tempesta fw] exiting... Apr 26 06:14:47 192.168.122.209 [51037.789916] [tdb] Shutdown Tempesta DB Apr 26 06:14:48 192.168.122.209 [51038.829670] [tdb] Start Tempesta DB Apr 26 06:14:48 192.168.122.209 [51038.973174] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:14:49 192.168.122.209 [51040.391857] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [51040.391857] Maybe that's fine, but it's worth checking the [51040.391857] config - if there is no relations between the [51040.391857] names, then host name confusion attack is possible. Apr 26 06:14:50 192.168.122.209 [51040.591441] [tempesta fw] Configuration processing is completed. Apr 26 06:14:50 192.168.122.209 [51040.640783] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:14:50 192.168.122.209 [51041.056489] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:14:50 192.168.122.209 [51041.083046] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:14:50 192.168.122.209 [51041.110134] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:14:50 192.168.122.209 [51041.203418] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 06:14:50 192.168.122.209 [51041.267374] [tempesta fw] Tempesta FW is ready Apr 26 06:15:01 192.168.122.209 [51051.811122] [tdb] Close table 'client0.tdb' Apr 26 06:15:01 192.168.122.209 [51051.992721] [tdb] Close table 'sessions0.tdb' Apr 26 06:15:04 192.168.122.209 [51055.234658] [tdb] Close table 'cache0.tdb' Apr 26 06:15:05 192.168.122.209 [51055.457178] [tdb] Close table 'filter0.tdb' Apr 26 06:15:05 192.168.122.209 [51055.457617] [tempesta fw] modules are stopped Apr 26 06:15:05 192.168.122.209 [51055.679136] [tempesta fw] exiting... Apr 26 06:15:05 192.168.122.209 [51055.815949] [tdb] Shutdown Tempesta DB Apr 26 06:15:06 192.168.122.209 [51056.892362] [tdb] Start Tempesta DB Apr 26 06:15:06 192.168.122.209 [51057.039335] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:15:08 192.168.122.209 [51058.448836] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [51058.448836] Maybe that's fine, but it's worth checking the [51058.448836] config - if there is no relations between the [51058.448836] names, then host name confusion attack is possible. Apr 26 06:15:08 192.168.122.209 [51058.663662] [tempesta fw] Configuration processing is completed. Apr 26 06:15:08 192.168.122.209 [51058.712436] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:15:08 192.168.122.209 [51059.118874] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:15:08 192.168.122.209 [51059.145086] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:15:08 192.168.122.209 [51059.171015] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:15:08 192.168.122.209 [51059.235649] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 06:15:08 192.168.122.209 [51059.283596] [tempesta fw] Tempesta FW is ready Apr 26 06:15:19 192.168.122.209 [51069.861438] [tdb] Close table 'client0.tdb' Apr 26 06:15:19 192.168.122.209 [51070.052973] [tdb] Close table 'sessions0.tdb' Apr 26 06:15:22 192.168.122.209 [51073.251077] [tdb] Close table 'cache0.tdb' Apr 26 06:15:23 192.168.122.209 [51073.496021] [tdb] Close table 'filter0.tdb' Apr 26 06:15:23 192.168.122.209 [51073.496474] [tempesta fw] modules are stopped Apr 26 06:15:23 192.168.122.209 [51073.667836] [tempesta fw] exiting... Apr 26 06:15:23 192.168.122.209 [51073.780192] [tdb] Shutdown Tempesta DB Apr 26 06:15:24 192.168.122.209 [51074.845512] [tdb] Start Tempesta DB Apr 26 06:15:24 192.168.122.209 [51074.985107] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:15:25 192.168.122.209 [51076.369229] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [51076.369229] Maybe that's fine, but it's worth checking the [51076.369229] config - if there is no relations between the [51076.369229] names, then host name confusion attack is possible. Apr 26 06:15:26 192.168.122.209 [51076.583876] [tempesta fw] Configuration processing is completed. Apr 26 06:15:26 192.168.122.209 [51076.633050] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:15:26 192.168.122.209 [51077.041434] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:15:26 192.168.122.209 [51077.067917] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:15:26 192.168.122.209 [51077.094820] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:15:26 192.168.122.209 [51077.183880] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 06:15:26 192.168.122.209 [51077.239831] [tempesta fw] Tempesta FW is ready Apr 26 06:15:37 192.168.122.209 [51087.775585] [tdb] Close table 'client0.tdb' Apr 26 06:15:37 192.168.122.209 [51087.991235] [tdb] Close table 'sessions0.tdb' Apr 26 06:15:40 192.168.122.209 [51091.185103] [tdb] Close table 'cache0.tdb' Apr 26 06:15:40 192.168.122.209 [51091.405243] [tdb] Close table 'filter0.tdb' Apr 26 06:15:40 192.168.122.209 [51091.405687] [tempesta fw] modules are stopped Apr 26 06:15:41 192.168.122.209 [51091.589851] [tempesta fw] exiting... Apr 26 06:15:41 192.168.122.209 [51091.703705] [tdb] Shutdown Tempesta DB Apr 26 06:15:42 192.168.122.209 [51092.731243] [tdb] Start Tempesta DB Apr 26 06:15:42 192.168.122.209 [51092.872164] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:15:43 192.168.122.209 [51094.361297] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [51094.361297] Maybe that's fine, but it's worth checking the [51094.361297] config - if there is no relations between the [51094.361297] names, then host name confusion attack is possible. Apr 26 06:15:44 192.168.122.209 [51094.564108] [tempesta fw] Configuration processing is completed. Apr 26 06:15:44 192.168.122.209 [51094.612988] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:15:44 192.168.122.209 [51095.021659] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:15:44 192.168.122.209 [51095.048044] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:15:44 192.168.122.209 [51095.074137] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:15:44 192.168.122.209 [51095.160114] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 06:15:44 192.168.122.209 [51095.223992] [tempesta fw] Tempesta FW is ready Apr 26 06:15:45 192.168.122.209 [51095.871981] [tdb] Close table 'client0.tdb' Apr 26 06:15:45 192.168.122.209 [51096.071601] [tdb] Close table 'sessions0.tdb' Apr 26 06:15:48 192.168.122.209 [51099.313697] [tdb] Close table 'cache0.tdb' Apr 26 06:15:49 192.168.122.209 [51099.567462] [tdb] Close table 'filter0.tdb' Apr 26 06:15:49 192.168.122.209 [51099.568020] [tempesta fw] modules are stopped Apr 26 06:15:49 192.168.122.209 [51099.760280] [tempesta fw] exiting... Apr 26 06:15:49 192.168.122.209 [51099.902554] [tdb] Shutdown Tempesta DB Apr 26 06:15:49 192.168.122.209 [51100.123020] End test: t_regress.test_reboot_under_load.TestRebootUnderLoadTfwWithCache.test_reboot_under_load Apr 26 06:15:49 192.168.122.209 [51100.135695] Start test: t_regress.test_srv_failovering.TestFailovering.test_on_close Apr 26 06:15:50 192.168.122.209 [51101.207567] [tdb] Start Tempesta DB Apr 26 06:15:50 192.168.122.209 [51101.357989] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:15:52 192.168.122.209 [51103.321830] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [51103.321830] Maybe that's fine, but it's worth checking the [51103.321830] config - if there is no relations between the [51103.321830] names, then host name confusion attack is possible. Apr 26 06:15:53 192.168.122.209 [51104.140246] [tempesta fw] Configuration processing is completed. Apr 26 06:15:53 192.168.122.209 [51104.189303] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:15:53 192.168.122.209 [51104.214826] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:15:53 192.168.122.209 [51104.240137] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:15:53 192.168.122.209 [51104.416155] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:15:54 192.168.122.209 [51104.488144] [tempesta fw] Tempesta FW is ready Apr 26 06:15:56 192.168.122.209 [51106.740023] [tdb] Close table 'client0.tdb' Apr 26 06:15:56 192.168.122.209 [51106.920301] [tdb] Close table 'sessions0.tdb' Apr 26 06:15:56 192.168.122.209 [51107.167863] [tdb] Close table 'filter0.tdb' Apr 26 06:15:56 192.168.122.209 [51107.168680] [tempesta fw] modules are stopped Apr 26 06:15:57 192.168.122.209 [51107.520260] [tempesta fw] exiting... Apr 26 06:15:57 192.168.122.209 [51107.653298] [tdb] Shutdown Tempesta DB Apr 26 06:15:57 192.168.122.209 [51107.915325] End test: t_regress.test_srv_failovering.TestFailovering.test_on_close Apr 26 06:15:57 192.168.122.209 [51107.928052] Start test: t_regress.test_stress_failovering.TestStressFailovering.test_failovering_sched_ratio Apr 26 06:15:58 192.168.122.209 [51109.103931] [tdb] Start Tempesta DB Apr 26 06:15:58 192.168.122.209 [51109.246141] net_ratelimit: 48 callbacks suppressed Apr 26 06:15:58 192.168.122.209 [51109.246144] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:15:59 192.168.122.209 [51109.869593] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [51109.869593] Maybe that's fine, but it's worth checking the [51109.869593] config - if there is no relations between the [51109.869593] names, then host name confusion attack is possible. Apr 26 06:15:59 192.168.122.209 [51110.032299] [tempesta fw] Configuration processing is completed. Apr 26 06:15:59 192.168.122.209 [51110.082116] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:15:59 192.168.122.209 [51110.109444] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:15:59 192.168.122.209 [51110.134624] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:15:59 192.168.122.209 [51110.212314] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:15:59 192.168.122.209 [51110.248243] [tempesta fw] Tempesta FW is ready Apr 26 06:16:00 192.168.122.209 [51110.620762] [tempesta fw] Warning: request evicted: the number of retries exceeded, status 504: 127.0.0.1 Apr 26 06:16:00 192.168.122.209 [51110.621976] [tempesta fw] Warning: request evicted: the number of retries exceeded, status 504: 127.0.0.1 Apr 26 06:16:00 192.168.122.209 [51110.623143] [tempesta fw] Warning: request evicted: the number of retries exceeded, status 504: 127.0.0.1 Apr 26 06:16:00 192.168.122.209 [51110.624326] [tempesta fw] Warning: request evicted: the number of retries exceeded, status 504: 127.0.0.1 Apr 26 06:16:00 192.168.122.209 [51110.625481] [tempesta fw] Warning: request evicted: the number of retries exceeded, status 504: 127.0.0.1 Apr 26 06:16:00 192.168.122.209 [51110.626640] [tempesta fw] Warning: request evicted: the number of retries exceeded, status 504: 127.0.0.1 Apr 26 06:16:10 192.168.122.209 [51120.991845] [tdb] Close table 'client0.tdb' Apr 26 06:16:10 192.168.122.209 [51121.185994] [tdb] Close table 'sessions0.tdb' Apr 26 06:16:10 192.168.122.209 [51121.406900] [tdb] Close table 'filter0.tdb' Apr 26 06:16:10 192.168.122.209 [51121.407330] [tempesta fw] modules are stopped Apr 26 06:16:11 192.168.122.209 [51121.603993] [tempesta fw] exiting... Apr 26 06:16:11 192.168.122.209 [51121.752433] [tdb] Shutdown Tempesta DB Apr 26 06:16:11 192.168.122.209 [51122.001214] End test: t_regress.test_stress_failovering.TestStressFailovering.test_failovering_sched_ratio Apr 26 06:16:11 192.168.122.209 [51122.011819] Start test: t_regress.test_stress_failovering.TestStressFailoveringWithUnlimKAReq.test_failovering_with_unlim_ka_requests Apr 26 06:16:12 192.168.122.209 [51123.129774] [tdb] Start Tempesta DB Apr 26 06:16:12 192.168.122.209 [51123.273015] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:16:13 192.168.122.209 [51123.898923] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [51123.898923] Maybe that's fine, but it's worth checking the [51123.898923] config - if there is no relations between the [51123.898923] names, then host name confusion attack is possible. Apr 26 06:16:13 192.168.122.209 [51124.060485] [tempesta fw] Configuration processing is completed. Apr 26 06:16:13 192.168.122.209 [51124.109533] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:16:13 192.168.122.209 [51124.135053] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:16:13 192.168.122.209 [51124.160359] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:16:13 192.168.122.209 [51124.236470] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 06:16:13 192.168.122.209 [51124.276431] [tempesta fw] Tempesta FW is ready Apr 26 06:16:24 192.168.122.209 [51134.492739] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:16:24 192.168.122.209 [51134.493340] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:16:24 192.168.122.209 [51134.493344] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:16:24 192.168.122.209 [51134.493348] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:16:24 192.168.122.209 [51134.494112] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:16:24 192.168.122.209 [51134.495970] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:16:24 192.168.122.209 [51134.495980] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:16:24 192.168.122.209 [51134.496844] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:16:24 192.168.122.209 [51134.497304] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:16:24 192.168.122.209 [51134.497851] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:16:24 192.168.122.209 [51134.497876] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:16:24 192.168.122.209 [51134.499888] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:16:24 192.168.122.209 [51134.504955] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:16:24 192.168.122.209 [51134.505528] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:16:24 192.168.122.209 [51134.982931] [tdb] Close table 'client0.tdb' Apr 26 06:16:24 192.168.122.209 [51135.182136] [tdb] Close table 'sessions0.tdb' Apr 26 06:16:24 192.168.122.209 [51135.410334] [tdb] Close table 'filter0.tdb' Apr 26 06:16:24 192.168.122.209 [51135.410764] [tempesta fw] modules are stopped Apr 26 06:16:25 192.168.122.209 [51135.594718] [tempesta fw] exiting... Apr 26 06:16:25 192.168.122.209 [51135.725345] [tdb] Shutdown Tempesta DB Apr 26 06:16:25 192.168.122.209 [51135.960776] End test: t_regress.test_stress_failovering.TestStressFailoveringWithUnlimKAReq.test_failovering_with_unlim_ka_requests Apr 26 06:16:25 192.168.122.209 [51135.991346] Start test: t_regress.test_stress_pipeline.TestStressPipeline.test_pipeline Apr 26 06:16:26 192.168.122.209 [51137.129646] [tdb] Start Tempesta DB Apr 26 06:16:26 192.168.122.209 [51137.266463] net_ratelimit: 708 callbacks suppressed Apr 26 06:16:26 192.168.122.209 [51137.266466] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:16:27 192.168.122.209 [51137.736765] [tempesta fw] Configuration processing is completed. Apr 26 06:16:27 192.168.122.209 [51137.790407] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:16:27 192.168.122.209 [51137.817693] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:16:27 192.168.122.209 [51137.843922] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:16:27 192.168.122.209 [51137.928727] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:16:27 192.168.122.209 [51137.972610] [tempesta fw] Tempesta FW is ready Apr 26 06:16:38 192.168.122.209 [51148.727257] [tdb] Close table 'client0.tdb' Apr 26 06:16:38 192.168.122.209 [51148.926063] [tdb] Close table 'sessions0.tdb' Apr 26 06:16:38 192.168.122.209 [51149.191369] [tdb] Close table 'filter0.tdb' Apr 26 06:16:38 192.168.122.209 [51149.191827] [tempesta fw] modules are stopped Apr 26 06:16:39 192.168.122.209 [51149.567473] [tempesta fw] exiting... Apr 26 06:16:39 192.168.122.209 [51149.710878] [tdb] Shutdown Tempesta DB Apr 26 06:16:39 192.168.122.209 [51149.927289] End test: t_regress.test_stress_pipeline.TestStressPipeline.test_pipeline Apr 26 06:16:39 192.168.122.209 [51149.941910] Start test: t_sched.test_h2_hash_func.HashSchedulerH2.test_hash_scheduler Apr 26 06:16:40 192.168.122.209 [51150.865989] [tdb] Start Tempesta DB Apr 26 06:16:40 192.168.122.209 [51150.993982] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:16:41 192.168.122.209 [51151.594130] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [51151.594130] Maybe that's fine, but it's worth checking the [51151.594130] config - if there is no relations between the [51151.594130] names, then host name confusion attack is possible. Apr 26 06:16:41 192.168.122.209 [51152.056821] [tempesta fw] Configuration processing is completed. Apr 26 06:16:41 192.168.122.209 [51152.122367] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:16:41 192.168.122.209 [51152.147715] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:16:41 192.168.122.209 [51152.173748] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:16:41 192.168.122.209 [51152.356776] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:16:41 192.168.122.209 [51152.358536] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:16:42 192.168.122.209 [51152.512774] [tempesta fw] Tempesta FW is ready Apr 26 06:16:43 192.168.122.209 [51154.328126] [tdb] Close table 'client0.tdb' Apr 26 06:16:44 192.168.122.209 [51154.557825] [tdb] Close table 'sessions0.tdb' Apr 26 06:16:44 192.168.122.209 [51154.810023] [tdb] Close table 'filter0.tdb' Apr 26 06:16:44 192.168.122.209 [51154.810453] [tempesta fw] modules are stopped Apr 26 06:16:44 192.168.122.209 [51155.109210] [tempesta fw] exiting... Apr 26 06:16:44 192.168.122.209 [51155.228784] [tdb] Shutdown Tempesta DB Apr 26 06:16:44 192.168.122.209 [51155.438134] End test: t_sched.test_h2_hash_func.HashSchedulerH2.test_hash_scheduler Apr 26 06:16:44 192.168.122.209 [51155.447093] Start test: t_sched.test_h2_hash_stress.BindToServerH2.test_hash Apr 26 06:16:51 192.168.122.209 [51161.584659] [tdb] Start Tempesta DB Apr 26 06:16:51 192.168.122.209 [51161.748003] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:16:52 192.168.122.209 [51163.069593] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [51163.069593] Maybe that's fine, but it's worth checking the [51163.069593] config - if there is no relations between the [51163.069593] names, then host name confusion attack is possible. Apr 26 06:16:53 192.168.122.209 [51163.776987] [tempesta fw] Configuration processing is completed. Apr 26 06:16:53 192.168.122.209 [51163.838077] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:16:53 192.168.122.209 [51163.865676] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:16:53 192.168.122.209 [51163.892098] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:16:54 192.168.122.209 [51164.613005] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:16:54 192.168.122.209 [51164.614800] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:16:54 192.168.122.209 [51164.660856] [tempesta fw] Tempesta FW is ready Apr 26 06:17:04 192.168.122.209 [51174.842605] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.843205] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.843977] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.844520] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.845323] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.845870] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.846672] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.847215] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.848007] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.848551] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.849380] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.849928] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.850706] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.851246] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.852032] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.852570] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.853368] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.853915] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.854688] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.855238] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.856341] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.856918] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.857729] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.858272] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.859067] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.859618] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.861301] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.861865] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.863010] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.863553] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.864346] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.864901] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.865702] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.866244] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.867014] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.867556] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.868336] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.868881] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.869676] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.870219] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.871001] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.871546] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.872312] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.872861] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.873873] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.874421] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.875229] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.875777] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.876550] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.877112] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.877890] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.878432] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.879210] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.879759] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.880521] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.881079] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.881960] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.882504] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.883272] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.883816] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.884606] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.885163] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.885946] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.886488] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.887272] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.887818] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.888582] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.889139] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.889918] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.890456] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.891222] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.891763] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.892535] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.893096] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.893882] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.894424] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.895216] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.895764] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.896536] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.897096] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.897963] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.898505] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.899314] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.899857] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.900650] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.901207] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.901986] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.902526] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.904056] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.904611] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.905405] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.905954] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.906742] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.907280] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.908157] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.908700] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.909607] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.910154] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.910919] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.911462] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.912237] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.912778] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.913556] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.914113] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.914888] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.915429] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.916200] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.916745] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.917530] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.918082] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.919160] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.919712] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.920542] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.921108] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.921886] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.922429] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.923228] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.923773] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.924558] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.925116] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.926009] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.926549] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.927325] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.927875] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.928658] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.929221] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.929994] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.930537] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.931337] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.931887] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.932720] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.933286] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.934086] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.934631] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.935399] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.935948] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.936744] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.937304] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.938074] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.938615] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.939405] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.939950] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.940750] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.941308] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.942102] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.942648] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.943437] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.943987] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.944782] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.945343] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.946187] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.946734] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.947518] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.948067] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.948843] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.949399] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.950168] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.950715] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.951486] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.952036] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.952804] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.953358] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.954155] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.954706] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.955499] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.956048] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.956842] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.957400] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.958177] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.958721] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.959528] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.960072] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.960842] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.961397] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.962200] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.962747] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.963516] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.964066] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.964870] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.965424] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.966217] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.966766] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.967551] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.968103] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.968982] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.969524] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.970574] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.971123] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.971919] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.972467] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.973272] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.973820] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.974609] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.975158] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.975949] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.976493] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.977308] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.977863] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.978654] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.979196] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.979993] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.980537] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.981346] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.981894] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.982676] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.983220] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.984015] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.984562] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.985813] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.986361] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.987190] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.987733] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.988607] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.989163] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.990030] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.990577] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.991889] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.992434] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.993224] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.993768] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.994552] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.995103] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.995874] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.996413] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.997218] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.997763] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.998533] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51174.999078] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51174.999865] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.000408] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.001258] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.001804] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.002581] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.003135] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.003997] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.004537] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.005363] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.005917] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.006742] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.007282] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.008057] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.008600] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.009421] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.009972] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.010758] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.011307] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.012075] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.012616] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.013416] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.013962] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.014746] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.015289] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.016242] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.016970] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.017790] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.018423] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.019313] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.019859] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.020649] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.021215] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.021984] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.022529] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.023303] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.023852] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.024617] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.025173] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.025965] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.026509] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.027280] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.027825] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.028609] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.029171] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.029970] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.030513] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.031405] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.031955] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.032760] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.033320] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.034124] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.034672] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.035568] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.036111] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.036927] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.037466] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.038261] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.038809] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.039582] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.040125] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.043208] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.043768] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.044550] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.045112] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.045907] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.046456] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.047255] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.047803] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.048638] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.049194] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.050010] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.050557] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.051408] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.051963] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.052739] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.053293] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.054244] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.054796] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.055579] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.056128] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.057024] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.057566] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.058750] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.059294] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.060097] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.060646] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.061467] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.062015] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.063174] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.063728] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.064503] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.065065] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.065875] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.066419] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.067204] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.067756] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.068516] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.069079] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.069858] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.070399] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.071186] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.071727] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.072941] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.073488] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.074298] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.074845] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.075620] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.076171] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.076971] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.077514] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.078304] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.078859] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.079640] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.080183] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.080989] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.081528] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.082303] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.082847] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.083635] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.084185] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.084985] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.085530] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.086312] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.086858] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.087623] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.088168] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.088974] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.089519] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.090285] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.090832] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.091612] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.092156] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.092951] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.093494] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.094273] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.094821] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.095591] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.096138] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.096935] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.097483] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.098273] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.098817] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.099635] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.100182] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.101061] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.101604] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.102401] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.102948] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.103735] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.104277] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.105107] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.105658] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.106506] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.107057] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.107831] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.108370] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.113823] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.114385] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.115436] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.115990] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.116773] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.117332] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.118100] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.118646] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.119414] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.119957] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.120734] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.121290] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.122066] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.122605] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.123376] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.123924] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.124701] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.125255] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.126024] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.126566] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.127344] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.127892] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.128658] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.129216] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.129991] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.130531] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.131304] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.131847] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.132617] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.133181] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.133967] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.134510] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.135288] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.135836] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.136603] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.137161] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.137937] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.138481] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.139248] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.139824] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.140591] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.141149] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.144648] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.145215] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.145994] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.146539] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.147302] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.147846] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.148620] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.149171] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.163367] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.163928] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.164704] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.165258] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.166043] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.166580] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.167354] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.167906] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.168693] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.169249] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.170031] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.170577] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.171363] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.171910] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.172693] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.173254] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.174035] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.174573] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.175347] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.175892] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.176670] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.177226] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.178007] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.178549] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:04 192.168.122.209 [51175.180091] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:04 192.168.122.209 [51175.180644] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:06 192.168.122.209 [51177.330487] [tdb] Close table 'client0.tdb' Apr 26 06:17:07 192.168.122.209 [51177.518837] [tdb] Close table 'sessions0.tdb' Apr 26 06:17:07 192.168.122.209 [51177.733879] [tdb] Close table 'filter0.tdb' Apr 26 06:17:07 192.168.122.209 [51177.734318] [tempesta fw] modules are stopped Apr 26 06:17:07 192.168.122.209 [51177.937360] [tempesta fw] exiting... Apr 26 06:17:07 192.168.122.209 [51178.055592] [tdb] Shutdown Tempesta DB Apr 26 06:17:08 192.168.122.209 [51178.985224] End test: t_sched.test_h2_hash_stress.BindToServerH2.test_hash Apr 26 06:17:08 192.168.122.209 [51178.994721] Start test: t_sched.test_h2_ratio_static.RatioH2.test_load_distribution Apr 26 06:17:10 192.168.122.209 [51181.354931] [tdb] Start Tempesta DB Apr 26 06:17:11 192.168.122.209 [51181.494875] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:17:11 192.168.122.209 [51182.278569] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [51182.278569] Maybe that's fine, but it's worth checking the [51182.278569] config - if there is no relations between the [51182.278569] names, then host name confusion attack is possible. Apr 26 06:17:12 192.168.122.209 [51182.637229] [tempesta fw] Configuration processing is completed. Apr 26 06:17:12 192.168.122.209 [51182.685924] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:17:12 192.168.122.209 [51182.714827] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:17:12 192.168.122.209 [51182.741848] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:17:12 192.168.122.209 [51183.017217] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:17:12 192.168.122.209 [51183.019108] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:17:12 192.168.122.209 [51183.061070] [tempesta fw] Tempesta FW is ready Apr 26 06:17:22 192.168.122.209 [51193.245435] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.246042] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.246048] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.247370] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.247374] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.247380] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.247388] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.247390] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.247571] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.247572] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.247649] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.247651] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.247829] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.247830] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.247894] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.247896] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.248035] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.248037] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.248162] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.248734] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.249432] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.249437] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.249987] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.250736] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.250743] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.250746] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.250825] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.250826] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.250867] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.250869] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.250903] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.250905] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.250971] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.250973] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.251093] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.251095] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.251194] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.251196] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.251228] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.251230] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.251346] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.255845] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.255888] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.255960] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.255964] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.256465] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.256469] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.256472] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.256531] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.256543] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.258781] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.278328] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.278346] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.279706] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.279716] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.281182] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.281185] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.281189] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.281195] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.281198] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.281641] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.281644] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.282240] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.287423] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.287427] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.288870] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.288875] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.290256] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.290264] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.291632] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.291707] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.292950] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.292955] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.294260] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.294266] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.295541] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.295544] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.295549] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.296652] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.298167] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.298174] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.299453] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.299455] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.300792] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.300798] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.302116] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.302118] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.303423] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.303427] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.304731] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.304733] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.306032] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.306037] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.307346] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.307349] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.308639] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.308645] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.309967] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.309975] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.311271] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.311277] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.312565] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.312571] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.313895] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.313902] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.315205] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.315208] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.316506] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.316508] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.316513] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.316590] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.316594] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.316649] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.316651] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.316766] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.316768] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.316900] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.316902] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.316986] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.316988] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.317457] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.325523] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.325531] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.326811] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.326821] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.328118] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.328121] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.329427] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.329432] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.330742] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.330754] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.332057] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.332062] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.333411] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.333417] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.334761] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.334768] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.336117] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.336122] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.337433] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.337437] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.338784] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.338786] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.338790] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.346432] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.346997] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.347845] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.348408] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.348412] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.349720] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.349723] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.349726] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.350515] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.352307] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.352310] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.352315] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.352326] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.352333] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.352344] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.352348] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.352385] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.352387] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.352398] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.352401] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.352454] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.352456] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.352773] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.352775] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.353219] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.356606] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.356923] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.356998] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.357504] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.358270] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.358282] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.358288] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.358291] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.358293] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.358416] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.358418] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.358607] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.358609] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.358692] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.358693] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.358720] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.358722] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.361126] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.361517] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.362164] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.362711] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.362961] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.362964] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.363118] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.363120] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.363211] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.363213] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.363342] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.364331] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.364558] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.364566] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.364571] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.365317] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.365323] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.366510] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.366628] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.366638] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.366640] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.366879] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.366891] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.367012] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.367014] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.367376] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.367411] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.371037] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.371266] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.371268] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.371270] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.371471] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.371473] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.371828] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.374083] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.374411] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.374414] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.374471] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.374998] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.375358] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.375361] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.375582] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.375585] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.375764] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.375767] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.375841] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.375843] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.376566] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.377080] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.377092] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.377095] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.377175] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.377177] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.377256] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.377258] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.377297] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.377298] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.377336] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.377338] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.377368] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.377370] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.377408] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.377410] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.377443] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.377445] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.377482] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.377484] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.377839] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.377843] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.377845] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.378120] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.378122] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.378147] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.378149] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.378182] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.378183] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.378308] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.378310] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.378463] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.379162] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.379680] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.379686] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.379689] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.379722] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.379723] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.380443] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.380446] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.380450] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.380453] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.380457] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.380485] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.380487] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.380497] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.380500] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.380522] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.380525] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.380534] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.380536] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.380550] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.380552] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.380571] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.380573] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.380582] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.380584] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.380608] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.380610] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.380613] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.380617] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.380648] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.380649] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.380654] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.380657] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.380690] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.380692] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.380727] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.380729] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.380757] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:22 192.168.122.209 [51193.380759] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:22 192.168.122.209 [51193.380799] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.380801] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.380836] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.380837] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.380885] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.380887] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.380917] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.380918] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.381023] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.381025] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.381028] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.381562] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.382275] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.382289] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.382293] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.382298] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.382301] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.382332] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.382334] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.382377] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.382379] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.382819] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.382959] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.382962] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.383051] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.383053] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.383601] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.383619] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.383622] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.383764] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.383766] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.384107] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.384109] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.384328] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.384893] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.384900] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.384902] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.385011] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.385013] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.385461] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.385464] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.385469] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.385477] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.385479] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.385538] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.385540] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.385564] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.385565] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.385594] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.385596] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.386334] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.386374] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.386376] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.386434] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.386436] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.387038] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.387537] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.387547] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.387549] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.388094] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.388096] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.388098] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.388155] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.388157] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.388248] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.388250] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.388286] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.388288] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.388334] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.388336] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.388359] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.388361] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.388435] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.388437] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.388469] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.388471] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.388501] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.388503] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.388533] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.388535] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.388878] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.394171] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.394521] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.394524] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.394527] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.395300] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.395303] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.395306] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.395347] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.395349] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.395381] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.395383] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.395442] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.395444] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.395496] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.395498] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.395521] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.395523] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.396073] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.396671] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.397146] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.403207] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.403623] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.403695] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.403699] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.404387] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.404390] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.404392] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.404446] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.404448] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.404487] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.404489] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.404647] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.404648] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.404710] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.404711] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.404782] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.404784] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.404817] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.404819] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.404840] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.404841] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.404876] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.404878] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.404938] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.404959] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.404961] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.405003] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.405006] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.405114] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.405117] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.405190] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.405192] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.405223] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.405225] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.405254] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.405256] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.405290] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.405292] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.405400] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.405401] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.405554] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.405555] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.541595] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.541612] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.543214] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.543228] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.546064] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.546071] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.548468] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.548474] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.548480] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.548542] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.548546] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.548841] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.548845] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.548895] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.548897] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.548936] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.548938] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.549033] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.549035] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.549199] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.549201] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.549233] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.549235] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.549271] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.549327] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.549329] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.549365] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.549367] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.563483] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.563497] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.564780] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.564783] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.564834] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.565351] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.565358] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.565361] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.565416] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.565418] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.565527] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.565529] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.566129] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.566133] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.566136] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.566707] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.567506] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.567997] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.568788] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.568792] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.568795] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.568841] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.568844] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.568899] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.568902] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.569450] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.580400] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.580474] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.581715] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.581722] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.583052] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.583055] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.584340] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.584343] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.584345] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.584348] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.584350] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.584408] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.584410] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.584636] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.584638] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.584665] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.584666] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.584852] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.584854] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.584892] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.584894] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.584988] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.584990] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.585050] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.585052] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.585120] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.597217] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.597222] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.598730] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.598740] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.600503] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.600506] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.602299] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.602306] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.603881] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.603889] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.605391] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.605398] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.606925] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.606927] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.608211] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.608215] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.609513] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.609516] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.609520] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.609525] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.609528] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.609596] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.609597] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.609696] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.609698] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.609922] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.609923] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.610484] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.617271] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.617274] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.618581] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.618585] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.619879] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.619884] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.621180] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.621186] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.622478] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.622482] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.623780] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:23 192.168.122.209 [51193.623783] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:23 192.168.122.209 [51193.623786] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:24 192.168.122.209 [51194.650480] [tdb] Close table 'client0.tdb' Apr 26 06:17:24 192.168.122.209 [51194.845659] [tdb] Close table 'sessions0.tdb' Apr 26 06:17:24 192.168.122.209 [51195.091900] [tdb] Close table 'filter0.tdb' Apr 26 06:17:24 192.168.122.209 [51195.092340] [tempesta fw] modules are stopped Apr 26 06:17:24 192.168.122.209 [51195.276955] [tempesta fw] exiting... Apr 26 06:17:24 192.168.122.209 [51195.389147] [tdb] Shutdown Tempesta DB Apr 26 06:17:25 192.168.122.209 [51195.880282] End test: t_sched.test_h2_ratio_static.RatioH2.test_load_distribution Apr 26 06:17:25 192.168.122.209 [51195.888528] Start test: t_sched.test_h2_ratio_static.RatioVariableConnsH2.test_load_distribution Apr 26 06:17:27 192.168.122.209 [51198.311674] [tdb] Start Tempesta DB Apr 26 06:17:28 192.168.122.209 [51198.450295] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:17:28 192.168.122.209 [51199.314755] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [51199.314755] Maybe that's fine, but it's worth checking the [51199.314755] config - if there is no relations between the [51199.314755] names, then host name confusion attack is possible. Apr 26 06:17:29 192.168.122.209 [51199.633446] [tempesta fw] Configuration processing is completed. Apr 26 06:17:29 192.168.122.209 [51199.690389] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:17:29 192.168.122.209 [51199.727153] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:17:29 192.168.122.209 [51199.762175] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:17:29 192.168.122.209 [51200.009445] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:17:29 192.168.122.209 [51200.011293] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:17:29 192.168.122.209 [51200.053393] [tempesta fw] Tempesta FW is ready Apr 26 06:17:39 192.168.122.209 [51210.269433] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:39 192.168.122.209 [51210.270029] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:39 192.168.122.209 [51210.270815] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:39 192.168.122.209 [51210.271364] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:39 192.168.122.209 [51210.273632] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:39 192.168.122.209 [51210.274241] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:39 192.168.122.209 [51210.274244] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:39 192.168.122.209 [51210.274248] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:39 192.168.122.209 [51210.274251] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:39 192.168.122.209 [51210.274254] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:39 192.168.122.209 [51210.274348] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:39 192.168.122.209 [51210.274350] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:39 192.168.122.209 [51210.274463] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:39 192.168.122.209 [51210.274465] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:39 192.168.122.209 [51210.274544] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:39 192.168.122.209 [51210.274545] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:39 192.168.122.209 [51210.275082] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:39 192.168.122.209 [51210.282293] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:39 192.168.122.209 [51210.282302] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:39 192.168.122.209 [51210.283638] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:39 192.168.122.209 [51210.283646] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:39 192.168.122.209 [51210.284976] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:39 192.168.122.209 [51210.284986] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:39 192.168.122.209 [51210.286311] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:39 192.168.122.209 [51210.286314] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:39 192.168.122.209 [51210.286319] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:39 192.168.122.209 [51210.297182] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:39 192.168.122.209 [51210.297763] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:39 192.168.122.209 [51210.299745] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:39 192.168.122.209 [51210.300304] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:39 192.168.122.209 [51210.301301] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:39 192.168.122.209 [51210.301646] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:39 192.168.122.209 [51210.301877] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:39 192.168.122.209 [51210.301880] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:39 192.168.122.209 [51210.301882] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:39 192.168.122.209 [51210.301942] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:39 192.168.122.209 [51210.301944] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:39 192.168.122.209 [51210.302038] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:39 192.168.122.209 [51210.302040] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:39 192.168.122.209 [51210.302443] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:39 192.168.122.209 [51210.302912] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:39 192.168.122.209 [51210.302915] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:39 192.168.122.209 [51210.303175] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:39 192.168.122.209 [51210.303177] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:39 192.168.122.209 [51210.303355] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:39 192.168.122.209 [51210.303666] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:39 192.168.122.209 [51210.303668] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:39 192.168.122.209 [51210.312243] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:40 192.168.122.209 [51211.383647] [tdb] Close table 'client0.tdb' Apr 26 06:17:41 192.168.122.209 [51211.574526] [tdb] Close table 'sessions0.tdb' Apr 26 06:17:41 192.168.122.209 [51211.795663] [tdb] Close table 'filter0.tdb' Apr 26 06:17:41 192.168.122.209 [51211.796111] [tempesta fw] modules are stopped Apr 26 06:17:41 192.168.122.209 [51212.074951] [tempesta fw] exiting... Apr 26 06:17:41 192.168.122.209 [51212.202279] [tdb] Shutdown Tempesta DB Apr 26 06:17:42 192.168.122.209 [51212.605310] End test: t_sched.test_h2_ratio_static.RatioVariableConnsH2.test_load_distribution Apr 26 06:17:42 192.168.122.209 [51212.628168] Start test: t_sched.test_h2_ratio_weight.RatioH2.test_load_distribution Apr 26 06:17:44 192.168.122.209 [51214.918951] [tdb] Start Tempesta DB Apr 26 06:17:44 192.168.122.209 [51215.065098] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:17:45 192.168.122.209 [51215.918202] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [51215.918202] Maybe that's fine, but it's worth checking the [51215.918202] config - if there is no relations between the [51215.918202] names, then host name confusion attack is possible. Apr 26 06:17:45 192.168.122.209 [51216.205694] [tempesta fw] Configuration processing is completed. Apr 26 06:17:45 192.168.122.209 [51216.262122] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:17:45 192.168.122.209 [51216.298491] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:17:45 192.168.122.209 [51216.333375] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:17:46 192.168.122.209 [51216.613707] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:17:46 192.168.122.209 [51216.615567] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:17:46 192.168.122.209 [51216.705597] [tempesta fw] Tempesta FW is ready Apr 26 06:17:56 192.168.122.209 [51226.911176] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:56 192.168.122.209 [51226.911776] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:56 192.168.122.209 [51226.911780] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:56 192.168.122.209 [51226.911784] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:56 192.168.122.209 [51226.912592] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:56 192.168.122.209 [51226.914445] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:56 192.168.122.209 [51226.914454] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:56 192.168.122.209 [51226.915232] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:56 192.168.122.209 [51226.915726] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:56 192.168.122.209 [51226.916238] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:56 192.168.122.209 [51226.916241] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:56 192.168.122.209 [51226.916268] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:56 192.168.122.209 [51226.917082] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:56 192.168.122.209 [51226.919601] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:56 192.168.122.209 [51226.919613] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:56 192.168.122.209 [51226.920943] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:56 192.168.122.209 [51226.920947] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:56 192.168.122.209 [51226.920953] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:56 192.168.122.209 [51226.920958] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:56 192.168.122.209 [51226.920963] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:56 192.168.122.209 [51226.920971] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:56 192.168.122.209 [51226.920973] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:56 192.168.122.209 [51226.921147] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:56 192.168.122.209 [51226.921149] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:56 192.168.122.209 [51226.921234] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:56 192.168.122.209 [51226.921236] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:56 192.168.122.209 [51226.921285] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:56 192.168.122.209 [51226.921287] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:56 192.168.122.209 [51226.921506] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:56 192.168.122.209 [51226.921508] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:56 192.168.122.209 [51226.922002] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:17:56 192.168.122.209 [51226.931561] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:17:57 192.168.122.209 [51228.085219] [tdb] Close table 'client0.tdb' Apr 26 06:17:57 192.168.122.209 [51228.304600] [tdb] Close table 'sessions0.tdb' Apr 26 06:17:58 192.168.122.209 [51228.558199] [tdb] Close table 'filter0.tdb' Apr 26 06:17:58 192.168.122.209 [51228.558672] [tempesta fw] modules are stopped Apr 26 06:17:58 192.168.122.209 [51228.750835] [tempesta fw] exiting... Apr 26 06:17:58 192.168.122.209 [51228.866233] [tdb] Shutdown Tempesta DB Apr 26 06:17:58 192.168.122.209 [51229.347038] End test: t_sched.test_h2_ratio_weight.RatioH2.test_load_distribution Apr 26 06:17:58 192.168.122.209 [51229.355829] Start test: t_sched.test_h2_ratio_weight.RatioVariableConnsH2.test_load_distribution Apr 26 06:18:01 192.168.122.209 [51231.858659] [tdb] Start Tempesta DB Apr 26 06:18:01 192.168.122.209 [51232.060820] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:18:02 192.168.122.209 [51232.954937] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [51232.954937] Maybe that's fine, but it's worth checking the [51232.954937] config - if there is no relations between the [51232.954937] names, then host name confusion attack is possible. Apr 26 06:18:02 192.168.122.209 [51233.249926] [tempesta fw] Configuration processing is completed. Apr 26 06:18:02 192.168.122.209 [51233.306056] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:18:02 192.168.122.209 [51233.342346] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:18:02 192.168.122.209 [51233.376993] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:18:03 192.168.122.209 [51233.602277] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:18:03 192.168.122.209 [51233.604065] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:18:03 192.168.122.209 [51233.661804] [tempesta fw] Tempesta FW is ready Apr 26 06:18:13 192.168.122.209 [51243.867869] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.868576] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.868589] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.869174] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.869178] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.869184] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.869406] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.869408] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.870080] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.873886] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.873889] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.873895] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.873898] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.873904] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.873912] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.873915] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.873940] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.873942] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.874977] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.875185] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.875196] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.879229] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.879804] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.879816] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.879820] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.880378] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.880380] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.880384] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.883858] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.884431] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.885019] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.885585] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.885597] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.885600] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.885643] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.885644] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.885844] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.885846] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.886145] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.886147] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.886391] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.886474] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.886477] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.886584] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.886586] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.886608] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.886610] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.886637] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.886638] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.886973] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.887436] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.888184] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.889017] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.902322] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.902328] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.903647] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.903650] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.903655] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.904503] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.905389] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.905713] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.905756] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.906294] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.906299] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.906302] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.906455] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.906484] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.906486] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.906519] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.906521] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.906544] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.906546] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.906551] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.906554] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.906612] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.906614] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.906650] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.906653] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.906677] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.906680] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.906864] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.907275] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.907278] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.907701] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.908573] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.909068] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.909567] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.910323] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.910918] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.911311] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.911314] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.911487] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.911772] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.911775] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.912175] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.912271] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.912274] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.912724] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.912727] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.912729] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.912757] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.912759] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.912786] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.912788] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.912816] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.912818] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.912930] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.912932] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.913968] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.939666] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.939680] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.940647] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.941197] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.941207] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.941212] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.941627] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.941660] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.941796] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.942290] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.942294] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.942892] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.943475] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.944241] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.944246] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.944250] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.944370] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.944373] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.944463] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.944466] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.944824] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.944828] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.944831] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.945818] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.946527] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.947032] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.947822] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.947830] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.947833] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.947869] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.947871] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.947921] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.947923] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.947998] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.948000] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.948030] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.948032] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.948465] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.948638] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.948643] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.948695] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.948697] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.948788] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.948790] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.948851] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.948853] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.948877] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.948879] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.948919] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.948921] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.948993] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.948997] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.949856] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.950534] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.951336] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.951863] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.952695] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.953303] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.978655] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.978667] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.979469] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.980161] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.980714] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.981940] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.982547] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.983206] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.983752] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.984532] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.985558] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.985802] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.986352] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.987423] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.988411] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.988413] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.988418] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.989202] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.991049] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.991741] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.991963] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.992330] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.992332] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.992393] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.992447] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.992470] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.992472] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.992535] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.992537] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.992967] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.992970] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.992973] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.993517] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.993522] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.993624] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.993627] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.993715] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.993720] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.994416] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.995049] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.995051] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.995055] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.995097] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.995098] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.995600] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.995602] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.995604] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.995634] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.995636] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.995696] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.995698] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.995739] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.995741] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.995762] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.995764] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.995783] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.995785] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.995804] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.995806] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.995825] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.995826] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.995956] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.995958] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.995980] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.995982] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.996000] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.996002] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.996027] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.996028] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.996051] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.996052] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.996074] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.996075] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.996096] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.996098] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.996119] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.996120] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.996146] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.996180] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.996189] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.996924] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.997453] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.997455] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.997458] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.997504] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.997510] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.997543] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.997545] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.997629] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.997650] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.997680] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.997682] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.998210] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.998213] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.998215] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.998335] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.998337] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.998479] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.998481] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.998528] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.998530] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.998569] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.998575] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.998667] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.998669] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.998698] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.998700] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.998800] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.998802] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.998900] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.998901] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.998938] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.998940] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.998974] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.998982] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.998985] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.999007] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.999009] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.999031] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.999033] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.999055] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.999057] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.999122] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.999124] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.999159] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.999161] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.999181] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51243.999182] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51243.999538] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.000273] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.000277] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.000279] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.000396] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.000398] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.000433] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.000440] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.000508] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.000510] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.000827] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.000829] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.000899] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.000901] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.000949] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.000951] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.000977] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.000979] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.001024] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.001028] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.001032] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.001087] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.001090] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.001122] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.001124] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.001148] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.001149] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.001161] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.001163] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.001177] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.001179] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.001203] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.001205] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.001212] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.001215] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.001250] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.001252] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.001262] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.001265] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.001295] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.001297] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.001381] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.001383] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.001404] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.001406] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.001437] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.001439] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.001483] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.001484] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.001517] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.001519] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.001548] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.001550] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.001615] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.002161] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.002888] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.002890] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.002895] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.002922] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.002924] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.002993] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.002996] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.003054] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.003057] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.003112] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.003115] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.003442] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.003444] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.003446] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.003483] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.003485] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.003514] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.003516] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.003550] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.003552] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.003605] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.003606] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.003630] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.003631] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.003663] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.003665] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.003695] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.003697] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.003737] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.003739] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.003785] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.003787] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.003812] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.003814] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.003849] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.003850] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.003885] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.003887] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.003914] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.003916] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.003941] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.003943] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.003968] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.003970] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.003998] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.004000] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.004039] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.004041] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.004200] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.004259] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.004262] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.004312] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.004315] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.004787] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.005498] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.005503] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.006052] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.006815] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.006818] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.006821] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.006847] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.006848] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.006909] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.006911] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.007391] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.008316] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.008866] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.009415] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.009421] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.010240] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.010745] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.010749] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.010751] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.010793] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.010795] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.010837] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.010839] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.011483] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.014748] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.150580] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.150591] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.151891] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.151894] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.153180] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.153204] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.155715] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.155801] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.158667] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.158673] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.159964] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.159974] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.162491] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.162507] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.162514] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.162521] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.162523] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.162572] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.162573] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.162592] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.162593] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.162627] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.162629] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:13 192.168.122.209 [51244.162647] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:18:13 192.168.122.209 [51244.162648] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 06:18:14 192.168.122.209 [51245.251128] [tdb] Close table 'client0.tdb' Apr 26 06:18:15 192.168.122.209 [51245.463845] [tdb] Close table 'sessions0.tdb' Apr 26 06:18:15 192.168.122.209 [51245.716950] [tdb] Close table 'filter0.tdb' Apr 26 06:18:15 192.168.122.209 [51245.717395] [tempesta fw] modules are stopped Apr 26 06:18:15 192.168.122.209 [51245.911331] [tempesta fw] exiting... Apr 26 06:18:15 192.168.122.209 [51246.052039] [tdb] Shutdown Tempesta DB Apr 26 06:18:16 192.168.122.209 [51246.633716] End test: t_sched.test_h2_ratio_weight.RatioVariableConnsH2.test_load_distribution Apr 26 06:18:16 192.168.122.209 [51246.646233] Start test: t_sched.test_hash_func.HashScheduler.test_hash_scheduler Apr 26 06:18:17 192.168.122.209 [51247.844627] [tdb] Start Tempesta DB Apr 26 06:18:17 192.168.122.209 [51248.022334] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:18:18 192.168.122.209 [51248.778904] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [51248.778904] Maybe that's fine, but it's worth checking the [51248.778904] config - if there is no relations between the [51248.778904] names, then host name confusion attack is possible. Apr 26 06:18:18 192.168.122.209 [51249.046066] [tempesta fw] Configuration processing is completed. Apr 26 06:18:18 192.168.122.209 [51249.100498] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:18:18 192.168.122.209 [51249.130674] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:18:18 192.168.122.209 [51249.163911] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:18:18 192.168.122.209 [51249.277973] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:18:18 192.168.122.209 [51249.279643] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:18:18 192.168.122.209 [51249.334009] [tempesta fw] Tempesta FW is ready Apr 26 06:18:20 192.168.122.209 [51250.573356] [tdb] Close table 'client0.tdb' Apr 26 06:18:20 192.168.122.209 [51250.761767] [tdb] Close table 'sessions0.tdb' Apr 26 06:18:20 192.168.122.209 [51250.996176] [tdb] Close table 'filter0.tdb' Apr 26 06:18:20 192.168.122.209 [51250.996612] [tempesta fw] modules are stopped Apr 26 06:18:20 192.168.122.209 [51251.198309] [tempesta fw] exiting... Apr 26 06:18:20 192.168.122.209 [51251.337456] [tdb] Shutdown Tempesta DB Apr 26 06:18:21 192.168.122.209 [51251.540083] End test: t_sched.test_hash_func.HashScheduler.test_hash_scheduler Apr 26 06:18:21 192.168.122.209 [51251.548496] Start test: t_sched.test_hash_stress.BindToServer.test_hash Apr 26 06:18:27 192.168.122.209 [51257.755877] [tdb] Start Tempesta DB Apr 26 06:18:27 192.168.122.209 [51257.912717] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:18:28 192.168.122.209 [51259.199508] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [51259.199508] Maybe that's fine, but it's worth checking the [51259.199508] config - if there is no relations between the [51259.199508] names, then host name confusion attack is possible. Apr 26 06:18:29 192.168.122.209 [51259.966179] [tempesta fw] Configuration processing is completed. Apr 26 06:18:29 192.168.122.209 [51260.015314] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:18:29 192.168.122.209 [51260.040986] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:18:29 192.168.122.209 [51260.068871] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:18:30 192.168.122.209 [51260.806213] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:18:30 192.168.122.209 [51260.808035] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:18:30 192.168.122.209 [51260.850157] [tempesta fw] Tempesta FW is ready Apr 26 06:18:43 192.168.122.209 [51273.468878] [tdb] Close table 'client0.tdb' Apr 26 06:18:43 192.168.122.209 [51273.661534] [tdb] Close table 'sessions0.tdb' Apr 26 06:18:43 192.168.122.209 [51273.899087] [tdb] Close table 'filter0.tdb' Apr 26 06:18:43 192.168.122.209 [51273.899533] [tempesta fw] modules are stopped Apr 26 06:18:43 192.168.122.209 [51274.087565] [tempesta fw] exiting... Apr 26 06:18:43 192.168.122.209 [51274.206110] [tdb] Shutdown Tempesta DB Apr 26 06:18:44 192.168.122.209 [51275.128610] End test: t_sched.test_hash_stress.BindToServer.test_hash Apr 26 06:18:44 192.168.122.209 [51275.154799] Start test: t_sched.test_ratio_static.Ratio.test_load_distribution Apr 26 06:18:47 192.168.122.209 [51277.624770] [tdb] Start Tempesta DB Apr 26 06:18:47 192.168.122.209 [51277.764984] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:18:48 192.168.122.209 [51278.607799] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [51278.607799] Maybe that's fine, but it's worth checking the [51278.607799] config - if there is no relations between the [51278.607799] names, then host name confusion attack is possible. Apr 26 06:18:48 192.168.122.209 [51278.998443] [tempesta fw] Configuration processing is completed. Apr 26 06:18:48 192.168.122.209 [51279.061270] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:18:48 192.168.122.209 [51279.089959] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:18:48 192.168.122.209 [51279.118714] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:18:48 192.168.122.209 [51279.422533] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:18:48 192.168.122.209 [51279.424311] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:18:49 192.168.122.209 [51279.470377] [tempesta fw] Tempesta FW is ready Apr 26 06:19:00 192.168.122.209 [51290.685193] [tdb] Close table 'client0.tdb' Apr 26 06:19:00 192.168.122.209 [51290.867516] [tdb] Close table 'sessions0.tdb' Apr 26 06:19:00 192.168.122.209 [51291.113440] [tdb] Close table 'filter0.tdb' Apr 26 06:19:00 192.168.122.209 [51291.113869] [tempesta fw] modules are stopped Apr 26 06:19:00 192.168.122.209 [51291.320421] [tempesta fw] exiting... Apr 26 06:19:01 192.168.122.209 [51291.452276] [tdb] Shutdown Tempesta DB Apr 26 06:19:01 192.168.122.209 [51291.972784] End test: t_sched.test_ratio_static.Ratio.test_load_distribution Apr 26 06:19:01 192.168.122.209 [51291.993972] Start test: t_sched.test_ratio_static.RatioVariableConns.test_load_distribution Apr 26 06:19:04 192.168.122.209 [51294.522216] [tdb] Start Tempesta DB Apr 26 06:19:04 192.168.122.209 [51294.676420] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:19:05 192.168.122.209 [51295.607967] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [51295.607967] Maybe that's fine, but it's worth checking the [51295.607967] config - if there is no relations between the [51295.607967] names, then host name confusion attack is possible. Apr 26 06:19:05 192.168.122.209 [51295.942663] [tempesta fw] Configuration processing is completed. Apr 26 06:19:05 192.168.122.209 [51295.995122] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:19:05 192.168.122.209 [51296.022081] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:19:05 192.168.122.209 [51296.049770] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:19:05 192.168.122.209 [51296.291481] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:19:05 192.168.122.209 [51296.293289] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:19:05 192.168.122.209 [51296.366575] [tempesta fw] Tempesta FW is ready Apr 26 06:19:17 192.168.122.209 [51307.634256] [tdb] Close table 'client0.tdb' Apr 26 06:19:17 192.168.122.209 [51307.825870] [tdb] Close table 'sessions0.tdb' Apr 26 06:19:17 192.168.122.209 [51308.064217] [tdb] Close table 'filter0.tdb' Apr 26 06:19:17 192.168.122.209 [51308.064668] [tempesta fw] modules are stopped Apr 26 06:19:17 192.168.122.209 [51308.252006] [tempesta fw] exiting... Apr 26 06:19:17 192.168.122.209 [51308.384758] [tdb] Shutdown Tempesta DB Apr 26 06:19:18 192.168.122.209 [51308.910957] End test: t_sched.test_ratio_static.RatioVariableConns.test_load_distribution Apr 26 06:19:18 192.168.122.209 [51308.919887] Start test: t_sched.test_ratio_weight.Ratio.test_load_distribution Apr 26 06:19:21 192.168.122.209 [51311.529869] [tdb] Start Tempesta DB Apr 26 06:19:21 192.168.122.209 [51311.679206] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:19:22 192.168.122.209 [51312.572276] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [51312.572276] Maybe that's fine, but it's worth checking the [51312.572276] config - if there is no relations between the [51312.572276] names, then host name confusion attack is possible. Apr 26 06:19:22 192.168.122.209 [51312.946905] [tempesta fw] Configuration processing is completed. Apr 26 06:19:22 192.168.122.209 [51313.009707] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:19:22 192.168.122.209 [51313.049579] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:19:22 192.168.122.209 [51313.084457] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:19:22 192.168.122.209 [51313.355097] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:19:22 192.168.122.209 [51313.357059] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:19:22 192.168.122.209 [51313.418835] [tempesta fw] Tempesta FW is ready Apr 26 06:19:37 192.168.122.209 [51327.744574] [tdb] Close table 'client0.tdb' Apr 26 06:19:37 192.168.122.209 [51328.059540] [tdb] Close table 'sessions0.tdb' Apr 26 06:19:38 192.168.122.209 [51328.633769] [tdb] Close table 'filter0.tdb' Apr 26 06:19:38 192.168.122.209 [51328.634234] [tempesta fw] modules are stopped Apr 26 06:19:38 192.168.122.209 [51329.283959] [tempesta fw] exiting... Apr 26 06:19:39 192.168.122.209 [51329.585590] [tdb] Shutdown Tempesta DB Apr 26 06:19:39 192.168.122.209 [51330.054759] End test: t_sched.test_ratio_weight.Ratio.test_load_distribution Apr 26 06:19:39 192.168.122.209 [51330.070483] Start test: t_sched.test_ratio_weight.RatioVariableConns.test_load_distribution Apr 26 06:19:42 192.168.122.209 [51332.725705] [tdb] Start Tempesta DB Apr 26 06:19:42 192.168.122.209 [51332.895641] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:19:43 192.168.122.209 [51333.836398] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [51333.836398] Maybe that's fine, but it's worth checking the [51333.836398] config - if there is no relations between the [51333.836398] names, then host name confusion attack is possible. Apr 26 06:19:43 192.168.122.209 [51334.203099] [tempesta fw] Configuration processing is completed. Apr 26 06:19:43 192.168.122.209 [51334.259382] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:19:43 192.168.122.209 [51334.294947] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:19:43 192.168.122.209 [51334.330461] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:19:44 192.168.122.209 [51334.559110] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:19:44 192.168.122.209 [51334.560949] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:19:44 192.168.122.209 [51334.599044] [tempesta fw] Tempesta FW is ready Apr 26 06:19:55 192.168.122.209 [51345.834502] [tdb] Close table 'client0.tdb' Apr 26 06:19:55 192.168.122.209 [51346.026797] [tdb] Close table 'sessions0.tdb' Apr 26 06:19:55 192.168.122.209 [51346.283015] [tdb] Close table 'filter0.tdb' Apr 26 06:19:55 192.168.122.209 [51346.283472] [tempesta fw] modules are stopped Apr 26 06:19:55 192.168.122.209 [51346.448968] [tempesta fw] exiting... Apr 26 06:19:56 192.168.122.209 [51346.565795] [tdb] Shutdown Tempesta DB Apr 26 06:19:56 192.168.122.209 [51347.028824] End test: t_sched.test_ratio_weight.RatioVariableConns.test_load_distribution Apr 26 06:19:56 192.168.122.209 [51347.040285] Start test: t_sched.test_reconnection_logic.ReconnectionLogic.test_reconnection_to_primary_server Apr 26 06:19:57 192.168.122.209 [51348.326720] [tdb] Start Tempesta DB Apr 26 06:19:58 192.168.122.209 [51348.479267] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:19:58 192.168.122.209 [51349.304539] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [51349.304539] Maybe that's fine, but it's worth checking the [51349.304539] config - if there is no relations between the [51349.304539] names, then host name confusion attack is possible. Apr 26 06:19:59 192.168.122.209 [51349.479261] [tempesta fw] Configuration processing is completed. Apr 26 06:19:59 192.168.122.209 [51349.529224] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:19:59 192.168.122.209 [51350.077439] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:19:59 192.168.122.209 [51350.113415] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:19:59 192.168.122.209 [51350.151029] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:19:59 192.168.122.209 [51350.207299] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:19:59 192.168.122.209 [51350.209074] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:19:59 192.168.122.209 [51350.263178] [tempesta fw] Tempesta FW is ready Apr 26 06:20:00 192.168.122.209 [51350.954832] [tdb] Close table 'client0.tdb' Apr 26 06:20:00 192.168.122.209 [51351.159641] [tdb] Close table 'sessions0.tdb' Apr 26 06:20:04 192.168.122.209 [51354.502214] [tdb] Close table 'cache0.tdb' Apr 26 06:20:04 192.168.122.209 [51354.766383] [tdb] Close table 'filter0.tdb' Apr 26 06:20:04 192.168.122.209 [51354.766839] [tempesta fw] modules are stopped Apr 26 06:20:04 192.168.122.209 [51355.024203] [tempesta fw] exiting... Apr 26 06:20:04 192.168.122.209 [51355.142773] [tdb] Shutdown Tempesta DB Apr 26 06:20:04 192.168.122.209 [51355.381264] End test: t_sched.test_reconnection_logic.ReconnectionLogic.test_reconnection_to_primary_server Apr 26 06:20:04 192.168.122.209 [51355.401464] Start test: t_server_options.test_server_options.TestServerOptions.test_requests_after_nonidempotent_request_conn_n_1 Apr 26 06:20:06 192.168.122.209 [51356.621022] [tdb] Start Tempesta DB Apr 26 06:20:06 192.168.122.209 [51356.760900] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:20:07 192.168.122.209 [51358.372677] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [51358.372677] Maybe that's fine, but it's worth checking the [51358.372677] config - if there is no relations between the [51358.372677] names, then host name confusion attack is possible. Apr 26 06:20:08 192.168.122.209 [51358.519435] [tempesta fw] Configuration processing is completed. Apr 26 06:20:08 192.168.122.209 [51358.574272] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:20:08 192.168.122.209 [51359.118083] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:20:08 192.168.122.209 [51359.152243] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:20:08 192.168.122.209 [51359.186112] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:20:08 192.168.122.209 [51359.235466] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:20:08 192.168.122.209 [51359.237218] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:20:08 192.168.122.209 [51359.295343] [tempesta fw] Tempesta FW is ready Apr 26 06:20:11 192.168.122.209 [51361.883501] [tdb] Close table 'client0.tdb' Apr 26 06:20:11 192.168.122.209 [51362.071091] [tdb] Close table 'sessions0.tdb' Apr 26 06:20:15 192.168.122.209 [51365.492042] [tdb] Close table 'cache0.tdb' Apr 26 06:20:15 192.168.122.209 [51365.709604] [tdb] Close table 'filter0.tdb' Apr 26 06:20:15 192.168.122.209 [51365.710058] [tempesta fw] modules are stopped Apr 26 06:20:15 192.168.122.209 [51365.925973] [tempesta fw] exiting... Apr 26 06:20:15 192.168.122.209 [51366.072185] [tdb] Shutdown Tempesta DB Apr 26 06:20:15 192.168.122.209 [51366.293539] End test: t_server_options.test_server_options.TestServerOptions.test_requests_after_nonidempotent_request_conn_n_1 Apr 26 06:20:15 192.168.122.209 [51366.317061] Start test: t_server_options.test_server_options.TestServerOptions.test_requests_after_nonidempotent_request_conn_n_2 Apr 26 06:20:17 192.168.122.209 [51367.526990] [tdb] Start Tempesta DB Apr 26 06:20:17 192.168.122.209 [51367.680344] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:20:18 192.168.122.209 [51369.272829] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [51369.272829] Maybe that's fine, but it's worth checking the [51369.272829] config - if there is no relations between the [51369.272829] names, then host name confusion attack is possible. Apr 26 06:20:18 192.168.122.209 [51369.419648] [tempesta fw] Configuration processing is completed. Apr 26 06:20:19 192.168.122.209 [51369.470923] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:20:19 192.168.122.209 [51369.886953] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:20:19 192.168.122.209 [51369.913916] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:20:19 192.168.122.209 [51369.940373] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:20:19 192.168.122.209 [51369.991589] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:20:19 192.168.122.209 [51369.993327] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:20:19 192.168.122.209 [51370.063475] [tempesta fw] Tempesta FW is ready Apr 26 06:20:20 192.168.122.209 [51370.638003] [tdb] Close table 'client0.tdb' Apr 26 06:20:20 192.168.122.209 [51370.836058] [tdb] Close table 'sessions0.tdb' Apr 26 06:20:23 192.168.122.209 [51374.128969] [tdb] Close table 'cache0.tdb' Apr 26 06:20:23 192.168.122.209 [51374.356088] [tdb] Close table 'filter0.tdb' Apr 26 06:20:23 192.168.122.209 [51374.356543] [tempesta fw] modules are stopped Apr 26 06:20:24 192.168.122.209 [51374.581082] [tempesta fw] exiting... Apr 26 06:20:24 192.168.122.209 [51374.699678] [tdb] Shutdown Tempesta DB Apr 26 06:20:24 192.168.122.209 [51374.911339] End test: t_server_options.test_server_options.TestServerOptions.test_requests_after_nonidempotent_request_conn_n_2 Apr 26 06:20:24 192.168.122.209 [51374.931048] Start test: t_server_options.test_server_options.TestServerOptions.test_server_connect_retries_exceeded_conns_n_1 Apr 26 06:20:25 192.168.122.209 [51376.142079] [tdb] Start Tempesta DB Apr 26 06:20:25 192.168.122.209 [51376.275965] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:20:27 192.168.122.209 [51378.016888] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [51378.016888] Maybe that's fine, but it's worth checking the [51378.016888] config - if there is no relations between the [51378.016888] names, then host name confusion attack is possible. Apr 26 06:20:27 192.168.122.209 [51378.151662] [tempesta fw] Configuration processing is completed. Apr 26 06:20:27 192.168.122.209 [51378.202215] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:20:28 192.168.122.209 [51378.616343] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:20:28 192.168.122.209 [51378.679201] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:20:28 192.168.122.209 [51378.707396] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:20:28 192.168.122.209 [51378.747539] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:20:28 192.168.122.209 [51378.748786] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:20:28 192.168.122.209 [51378.791624] [tempesta fw] Tempesta FW is ready Apr 26 06:20:30 192.168.122.209 [51380.876029] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 06:20:38 192.168.122.209 [51389.068396] [tempesta fw] Warning: request dropped: unable to find an available back end server, status 502: 127.0.0.2 Apr 26 06:20:44 192.168.122.209 [51394.552923] [tdb] Close table 'client0.tdb' Apr 26 06:20:44 192.168.122.209 [51394.743978] [tdb] Close table 'sessions0.tdb' Apr 26 06:20:47 192.168.122.209 [51398.061641] [tdb] Close table 'cache0.tdb' Apr 26 06:20:47 192.168.122.209 [51398.291065] [tdb] Close table 'filter0.tdb' Apr 26 06:20:47 192.168.122.209 [51398.291512] [tempesta fw] modules are stopped Apr 26 06:20:48 192.168.122.209 [51398.504293] [tempesta fw] exiting... Apr 26 06:20:48 192.168.122.209 [51398.612125] [tdb] Shutdown Tempesta DB Apr 26 06:20:48 192.168.122.209 [51398.846077] End test: t_server_options.test_server_options.TestServerOptions.test_server_connect_retries_exceeded_conns_n_1 Apr 26 06:20:48 192.168.122.209 [51398.860753] Start test: t_server_options.test_server_options.TestServerOptions.test_server_connect_retries_exceeded_conns_n_2 Apr 26 06:20:49 192.168.122.209 [51399.981114] [tdb] Start Tempesta DB Apr 26 06:20:49 192.168.122.209 [51400.119915] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:20:51 192.168.122.209 [51401.693298] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [51401.693298] Maybe that's fine, but it's worth checking the [51401.693298] config - if there is no relations between the [51401.693298] names, then host name confusion attack is possible. Apr 26 06:20:51 192.168.122.209 [51401.827954] [tempesta fw] Configuration processing is completed. Apr 26 06:20:51 192.168.122.209 [51401.890373] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:20:51 192.168.122.209 [51402.344939] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:20:51 192.168.122.209 [51402.373122] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:20:51 192.168.122.209 [51402.410479] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:20:51 192.168.122.209 [51402.443863] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:20:51 192.168.122.209 [51402.444877] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:20:52 192.168.122.209 [51402.495923] [tempesta fw] Tempesta FW is ready Apr 26 06:20:54 192.168.122.209 [51404.588324] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 06:21:07 192.168.122.209 [51418.270647] [tdb] Close table 'client0.tdb' Apr 26 06:21:08 192.168.122.209 [51418.483363] [tdb] Close table 'sessions0.tdb' Apr 26 06:21:11 192.168.122.209 [51422.121652] [tdb] Close table 'cache0.tdb' Apr 26 06:21:11 192.168.122.209 [51422.376654] [tdb] Close table 'filter0.tdb' Apr 26 06:21:11 192.168.122.209 [51422.377122] [tempesta fw] modules are stopped Apr 26 06:21:12 192.168.122.209 [51422.617331] [tempesta fw] exiting... Apr 26 06:21:12 192.168.122.209 [51422.738503] [tdb] Shutdown Tempesta DB Apr 26 06:21:12 192.168.122.209 [51422.955457] End test: t_server_options.test_server_options.TestServerOptions.test_server_connect_retries_exceeded_conns_n_2 Apr 26 06:21:12 192.168.122.209 [51422.968716] Start test: t_server_options.test_server_options.TestServerOptions.test_server_connect_retries_not_exceeded Apr 26 06:21:13 192.168.122.209 [51424.099529] [tdb] Start Tempesta DB Apr 26 06:21:13 192.168.122.209 [51424.306985] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:21:15 192.168.122.209 [51425.869531] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [51425.869531] Maybe that's fine, but it's worth checking the [51425.869531] config - if there is no relations between the [51425.869531] names, then host name confusion attack is possible. Apr 26 06:21:15 192.168.122.209 [51425.988267] [tempesta fw] Configuration processing is completed. Apr 26 06:21:15 192.168.122.209 [51426.037671] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:21:15 192.168.122.209 [51426.447540] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:21:16 192.168.122.209 [51426.505425] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:21:16 192.168.122.209 [51426.532628] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:21:16 192.168.122.209 [51426.588239] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:21:16 192.168.122.209 [51426.589999] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:21:16 192.168.122.209 [51426.628165] [tempesta fw] Tempesta FW is ready Apr 26 06:21:18 192.168.122.209 [51428.685121] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 06:21:19 192.168.122.209 [51430.214177] [tdb] Close table 'client0.tdb' Apr 26 06:21:19 192.168.122.209 [51430.428579] [tdb] Close table 'sessions0.tdb' Apr 26 06:21:23 192.168.122.209 [51433.645611] [tdb] Close table 'cache0.tdb' Apr 26 06:21:23 192.168.122.209 [51433.889274] [tdb] Close table 'filter0.tdb' Apr 26 06:21:23 192.168.122.209 [51433.889690] [tempesta fw] modules are stopped Apr 26 06:21:23 192.168.122.209 [51434.119467] [tempesta fw] exiting... Apr 26 06:21:23 192.168.122.209 [51434.255581] [tdb] Shutdown Tempesta DB Apr 26 06:21:24 192.168.122.209 [51434.474856] End test: t_server_options.test_server_options.TestServerOptions.test_server_connect_retries_not_exceeded Apr 26 06:21:24 192.168.122.209 [51434.488940] Start test: t_server_options.test_server_options.TestServerOptions.test_server_forward_retries_exceeded_0 Apr 26 06:21:25 192.168.122.209 [51435.553843] [tdb] Start Tempesta DB Apr 26 06:21:25 192.168.122.209 [51435.691590] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:21:26 192.168.122.209 [51437.321588] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [51437.321588] Maybe that's fine, but it's worth checking the [51437.321588] config - if there is no relations between the [51437.321588] names, then host name confusion attack is possible. Apr 26 06:21:27 192.168.122.209 [51437.456421] [tempesta fw] Configuration processing is completed. Apr 26 06:21:27 192.168.122.209 [51437.505871] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:21:27 192.168.122.209 [51437.926896] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:21:27 192.168.122.209 [51437.953580] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:21:27 192.168.122.209 [51437.991100] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:21:27 192.168.122.209 [51438.032347] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:21:27 192.168.122.209 [51438.033743] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:21:27 192.168.122.209 [51438.072305] [tempesta fw] Tempesta FW is ready Apr 26 06:21:27 192.168.122.209 [51438.204835] [tempesta fw] Warning: request evicted: the number of retries exceeded, status 504: 127.0.0.2 Apr 26 06:21:28 192.168.122.209 [51438.700829] [tdb] Close table 'client0.tdb' Apr 26 06:21:28 192.168.122.209 [51438.886442] [tdb] Close table 'sessions0.tdb' Apr 26 06:21:31 192.168.122.209 [51442.083920] [tdb] Close table 'cache0.tdb' Apr 26 06:21:31 192.168.122.209 [51442.300004] [tdb] Close table 'filter0.tdb' Apr 26 06:21:31 192.168.122.209 [51442.300451] [tempesta fw] modules are stopped Apr 26 06:21:32 192.168.122.209 [51442.522525] [tempesta fw] exiting... Apr 26 06:21:32 192.168.122.209 [51442.644146] [tdb] Shutdown Tempesta DB Apr 26 06:21:32 192.168.122.209 [51442.855464] End test: t_server_options.test_server_options.TestServerOptions.test_server_forward_retries_exceeded_0 Apr 26 06:21:32 192.168.122.209 [51442.870903] Start test: t_server_options.test_server_options.TestServerOptions.test_server_forward_retries_exceeded_5 Apr 26 06:21:33 192.168.122.209 [51443.909119] [tdb] Start Tempesta DB Apr 26 06:21:33 192.168.122.209 [51444.044498] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:21:35 192.168.122.209 [51445.593754] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [51445.593754] Maybe that's fine, but it's worth checking the [51445.593754] config - if there is no relations between the [51445.593754] names, then host name confusion attack is possible. Apr 26 06:21:35 192.168.122.209 [51445.740554] [tempesta fw] Configuration processing is completed. Apr 26 06:21:35 192.168.122.209 [51445.794469] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:21:35 192.168.122.209 [51446.191678] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:21:35 192.168.122.209 [51446.252432] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:21:35 192.168.122.209 [51446.288026] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:21:35 192.168.122.209 [51446.328469] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:21:35 192.168.122.209 [51446.330211] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:21:35 192.168.122.209 [51446.380418] [tempesta fw] Tempesta FW is ready Apr 26 06:21:36 192.168.122.209 [51446.572875] [tempesta fw] Warning: request evicted: the number of retries exceeded, status 504: 127.0.0.2 Apr 26 06:21:36 192.168.122.209 [51447.064252] [tdb] Close table 'client0.tdb' Apr 26 06:21:36 192.168.122.209 [51447.253037] [tdb] Close table 'sessions0.tdb' Apr 26 06:21:40 192.168.122.209 [51450.521867] [tdb] Close table 'cache0.tdb' Apr 26 06:21:40 192.168.122.209 [51450.743300] [tdb] Close table 'filter0.tdb' Apr 26 06:21:40 192.168.122.209 [51450.743733] [tempesta fw] modules are stopped Apr 26 06:21:40 192.168.122.209 [51450.968757] [tempesta fw] exiting... Apr 26 06:21:40 192.168.122.209 [51451.133217] [tdb] Shutdown Tempesta DB Apr 26 06:21:40 192.168.122.209 [51451.363244] End test: t_server_options.test_server_options.TestServerOptions.test_server_forward_retries_exceeded_5 Apr 26 06:21:40 192.168.122.209 [51451.391342] Start test: t_server_options.test_server_options.TestServerOptions.test_server_forward_retries_not_exceeded Apr 26 06:21:42 192.168.122.209 [51452.509305] [tdb] Start Tempesta DB Apr 26 06:21:42 192.168.122.209 [51452.653504] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:21:43 192.168.122.209 [51454.269341] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [51454.269341] Maybe that's fine, but it's worth checking the [51454.269341] config - if there is no relations between the [51454.269341] names, then host name confusion attack is possible. Apr 26 06:21:43 192.168.122.209 [51454.420650] [tempesta fw] Configuration processing is completed. Apr 26 06:21:44 192.168.122.209 [51454.473764] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:21:44 192.168.122.209 [51454.919669] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:21:44 192.168.122.209 [51454.984212] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:21:44 192.168.122.209 [51455.018491] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:21:44 192.168.122.209 [51455.084588] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:21:44 192.168.122.209 [51455.086378] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:21:44 192.168.122.209 [51455.124516] [tempesta fw] Tempesta FW is ready Apr 26 06:21:45 192.168.122.209 [51456.204865] [tdb] Close table 'client0.tdb' Apr 26 06:21:45 192.168.122.209 [51456.392885] [tdb] Close table 'sessions0.tdb' Apr 26 06:21:49 192.168.122.209 [51459.630932] [tdb] Close table 'cache0.tdb' Apr 26 06:21:49 192.168.122.209 [51459.875909] [tdb] Close table 'filter0.tdb' Apr 26 06:21:49 192.168.122.209 [51459.876353] [tempesta fw] modules are stopped Apr 26 06:21:49 192.168.122.209 [51460.147873] [tempesta fw] exiting... Apr 26 06:21:49 192.168.122.209 [51460.285815] [tdb] Shutdown Tempesta DB Apr 26 06:21:50 192.168.122.209 [51460.508608] End test: t_server_options.test_server_options.TestServerOptions.test_server_forward_retries_not_exceeded Apr 26 06:21:50 192.168.122.209 [51460.538116] Start test: t_server_options.test_server_options.TestServerOptions.test_server_forward_timeout_exceeded Apr 26 06:21:51 192.168.122.209 [51461.591812] [tdb] Start Tempesta DB Apr 26 06:21:51 192.168.122.209 [51461.754614] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:21:52 192.168.122.209 [51463.441763] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [51463.441763] Maybe that's fine, but it's worth checking the [51463.441763] config - if there is no relations between the [51463.441763] names, then host name confusion attack is possible. Apr 26 06:21:53 192.168.122.209 [51463.572724] [tempesta fw] Configuration processing is completed. Apr 26 06:21:53 192.168.122.209 [51463.638337] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:21:53 192.168.122.209 [51464.084487] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:21:53 192.168.122.209 [51464.113080] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:21:53 192.168.122.209 [51464.150799] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:21:53 192.168.122.209 [51464.200698] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:21:53 192.168.122.209 [51464.202472] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:21:53 192.168.122.209 [51464.252557] [tempesta fw] Tempesta FW is ready Apr 26 06:21:56 192.168.122.209 [51467.396811] [tempesta fw] Warning: request evicted: timed out, status 504: 127.0.0.2 Apr 26 06:21:57 192.168.122.209 [51467.882651] [tdb] Close table 'client0.tdb' Apr 26 06:21:57 192.168.122.209 [51468.075444] [tdb] Close table 'sessions0.tdb' Apr 26 06:22:00 192.168.122.209 [51471.269529] [tdb] Close table 'cache0.tdb' Apr 26 06:22:01 192.168.122.209 [51471.493953] [tdb] Close table 'filter0.tdb' Apr 26 06:22:01 192.168.122.209 [51471.494410] [tempesta fw] modules are stopped Apr 26 06:22:01 192.168.122.209 [51471.778719] [tempesta fw] exiting... Apr 26 06:22:01 192.168.122.209 [51471.881614] [tdb] Shutdown Tempesta DB Apr 26 06:22:01 192.168.122.209 [51472.103867] End test: t_server_options.test_server_options.TestServerOptions.test_server_forward_timeout_exceeded Apr 26 06:22:01 192.168.122.209 [51472.118578] Start test: t_server_options.test_server_options.TestServerOptions.test_server_forward_timeout_not_exceeded Apr 26 06:22:02 192.168.122.209 [51473.204119] [tdb] Start Tempesta DB Apr 26 06:22:02 192.168.122.209 [51473.348303] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:22:04 192.168.122.209 [51474.982119] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [51474.982119] Maybe that's fine, but it's worth checking the [51474.982119] config - if there is no relations between the [51474.982119] names, then host name confusion attack is possible. Apr 26 06:22:04 192.168.122.209 [51475.116965] [tempesta fw] Configuration processing is completed. Apr 26 06:22:04 192.168.122.209 [51475.180316] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:22:05 192.168.122.209 [51475.603839] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:22:05 192.168.122.209 [51475.660943] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:22:05 192.168.122.209 [51475.687100] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:22:05 192.168.122.209 [51475.756779] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:22:05 192.168.122.209 [51475.757849] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:22:05 192.168.122.209 [51475.796779] [tempesta fw] Tempesta FW is ready Apr 26 06:22:06 192.168.122.209 [51477.413699] [tdb] Close table 'client0.tdb' Apr 26 06:22:07 192.168.122.209 [51477.591312] [tdb] Close table 'sessions0.tdb' Apr 26 06:22:10 192.168.122.209 [51481.052888] [tdb] Close table 'cache0.tdb' Apr 26 06:22:10 192.168.122.209 [51481.284629] [tdb] Close table 'filter0.tdb' Apr 26 06:22:10 192.168.122.209 [51481.285098] [tempesta fw] modules are stopped Apr 26 06:22:11 192.168.122.209 [51481.554131] [tempesta fw] exiting... Apr 26 06:22:11 192.168.122.209 [51481.692327] [tdb] Shutdown Tempesta DB Apr 26 06:22:11 192.168.122.209 [51481.895907] End test: t_server_options.test_server_options.TestServerOptions.test_server_forward_timeout_not_exceeded Apr 26 06:22:11 192.168.122.209 [51481.908421] Start test: t_server_options.test_server_options.TestServerOptions.test_server_queue_size_exceeded Apr 26 06:22:12 192.168.122.209 [51483.009162] [tdb] Start Tempesta DB Apr 26 06:22:12 192.168.122.209 [51483.165347] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:22:14 192.168.122.209 [51484.773751] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [51484.773751] Maybe that's fine, but it's worth checking the [51484.773751] config - if there is no relations between the [51484.773751] names, then host name confusion attack is possible. Apr 26 06:22:14 192.168.122.209 [51484.924982] [tempesta fw] Configuration processing is completed. Apr 26 06:22:14 192.168.122.209 [51484.973978] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:22:14 192.168.122.209 [51485.389937] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:22:15 192.168.122.209 [51485.461326] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:22:15 192.168.122.209 [51485.488095] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:22:15 192.168.122.209 [51485.528976] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:22:15 192.168.122.209 [51485.530766] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:22:15 192.168.122.209 [51485.572892] [tempesta fw] Tempesta FW is ready Apr 26 06:22:17 192.168.122.209 [51488.224636] [tdb] Close table 'client0.tdb' Apr 26 06:22:17 192.168.122.209 [51488.409196] [tdb] Close table 'sessions0.tdb' Apr 26 06:22:21 192.168.122.209 [51491.573263] [tdb] Close table 'cache0.tdb' Apr 26 06:22:21 192.168.122.209 [51491.822773] [tdb] Close table 'filter0.tdb' Apr 26 06:22:21 192.168.122.209 [51491.823214] [tempesta fw] modules are stopped Apr 26 06:22:21 192.168.122.209 [51492.022569] [tempesta fw] exiting... Apr 26 06:22:21 192.168.122.209 [51492.166232] [tdb] Shutdown Tempesta DB Apr 26 06:22:21 192.168.122.209 [51492.381657] End test: t_server_options.test_server_options.TestServerOptions.test_server_queue_size_exceeded Apr 26 06:22:21 192.168.122.209 [51492.395854] Start test: t_server_options.test_server_options.TestServerOptions.test_server_queue_size_not_exceeded Apr 26 06:22:23 192.168.122.209 [51493.463591] [tdb] Start Tempesta DB Apr 26 06:22:23 192.168.122.209 [51493.606967] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:22:24 192.168.122.209 [51495.190336] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [51495.190336] Maybe that's fine, but it's worth checking the [51495.190336] config - if there is no relations between the [51495.190336] names, then host name confusion attack is possible. Apr 26 06:22:24 192.168.122.209 [51495.341165] [tempesta fw] Configuration processing is completed. Apr 26 06:22:24 192.168.122.209 [51495.396475] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:22:25 192.168.122.209 [51495.819742] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:22:25 192.168.122.209 [51495.891436] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:22:25 192.168.122.209 [51495.917647] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:22:25 192.168.122.209 [51495.961086] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:22:25 192.168.122.209 [51495.962802] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:22:25 192.168.122.209 [51496.005020] [tempesta fw] Tempesta FW is ready Apr 26 06:22:28 192.168.122.209 [51498.652330] [tdb] Close table 'client0.tdb' Apr 26 06:22:28 192.168.122.209 [51498.834061] [tdb] Close table 'sessions0.tdb' Apr 26 06:22:31 192.168.122.209 [51502.025991] [tdb] Close table 'cache0.tdb' Apr 26 06:22:31 192.168.122.209 [51502.278010] [tdb] Close table 'filter0.tdb' Apr 26 06:22:31 192.168.122.209 [51502.278453] [tempesta fw] modules are stopped Apr 26 06:22:32 192.168.122.209 [51502.503236] [tempesta fw] exiting... Apr 26 06:22:32 192.168.122.209 [51502.629219] [tdb] Shutdown Tempesta DB Apr 26 06:22:32 192.168.122.209 [51502.840917] End test: t_server_options.test_server_options.TestServerOptions.test_server_queue_size_not_exceeded Apr 26 06:22:32 192.168.122.209 [51502.850641] Start test: t_server_options.test_server_options.TestServerOptions.test_server_queue_size_pipeline_disable Apr 26 06:22:33 192.168.122.209 [51503.975829] [tdb] Start Tempesta DB Apr 26 06:22:33 192.168.122.209 [51504.108076] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:22:35 192.168.122.209 [51505.618446] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [51505.618446] Maybe that's fine, but it's worth checking the [51505.618446] config - if there is no relations between the [51505.618446] names, then host name confusion attack is possible. Apr 26 06:22:35 192.168.122.209 [51505.781214] [tempesta fw] Configuration processing is completed. Apr 26 06:22:35 192.168.122.209 [51505.838531] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:22:35 192.168.122.209 [51506.250066] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:22:35 192.168.122.209 [51506.318197] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:22:35 192.168.122.209 [51506.344367] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:22:35 192.168.122.209 [51506.405213] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:22:35 192.168.122.209 [51506.406926] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:22:35 192.168.122.209 [51506.453154] [tempesta fw] Tempesta FW is ready Apr 26 06:22:38 192.168.122.209 [51509.086055] [tdb] Close table 'client0.tdb' Apr 26 06:22:38 192.168.122.209 [51509.269078] [tdb] Close table 'sessions0.tdb' Apr 26 06:22:42 192.168.122.209 [51512.458200] [tdb] Close table 'cache0.tdb' Apr 26 06:22:42 192.168.122.209 [51512.711381] [tdb] Close table 'filter0.tdb' Apr 26 06:22:42 192.168.122.209 [51512.711823] [tempesta fw] modules are stopped Apr 26 06:22:42 192.168.122.209 [51512.931775] [tempesta fw] exiting... Apr 26 06:22:42 192.168.122.209 [51513.068128] [tdb] Shutdown Tempesta DB Apr 26 06:22:42 192.168.122.209 [51513.265435] End test: t_server_options.test_server_options.TestServerOptions.test_server_queue_size_pipeline_disable Apr 26 06:22:42 192.168.122.209 [51513.277146] Start test: t_server_options.test_server_options.TestServerOptions.test_server_retry_nonidempotent_disabled Apr 26 06:22:43 192.168.122.209 [51514.385535] [tdb] Start Tempesta DB Apr 26 06:22:44 192.168.122.209 [51514.516584] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:22:45 192.168.122.209 [51516.110578] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [51516.110578] Maybe that's fine, but it's worth checking the [51516.110578] config - if there is no relations between the [51516.110578] names, then host name confusion attack is possible. Apr 26 06:22:45 192.168.122.209 [51516.249375] [tempesta fw] Configuration processing is completed. Apr 26 06:22:45 192.168.122.209 [51516.298650] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:22:46 192.168.122.209 [51516.690516] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:22:46 192.168.122.209 [51516.744710] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:22:46 192.168.122.209 [51516.769876] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:22:46 192.168.122.209 [51516.821345] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:22:46 192.168.122.209 [51516.823038] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:22:46 192.168.122.209 [51516.877286] [tempesta fw] Tempesta FW is ready Apr 26 06:22:46 192.168.122.209 [51517.013359] [tempesta fw] Warning: request dropped: non-idempotent requests aren't re-forwarded or re-scheduled, status 504: 127.0.0.2 Apr 26 06:22:47 192.168.122.209 [51517.514335] [tdb] Close table 'client0.tdb' Apr 26 06:22:47 192.168.122.209 [51517.720269] [tdb] Close table 'sessions0.tdb' Apr 26 06:22:50 192.168.122.209 [51520.922710] [tdb] Close table 'cache0.tdb' Apr 26 06:22:50 192.168.122.209 [51521.150044] [tdb] Close table 'filter0.tdb' Apr 26 06:22:50 192.168.122.209 [51521.150483] [tempesta fw] modules are stopped Apr 26 06:22:50 192.168.122.209 [51521.358473] [tempesta fw] exiting... Apr 26 06:22:51 192.168.122.209 [51521.515094] [tdb] Shutdown Tempesta DB Apr 26 06:22:51 192.168.122.209 [51521.726046] End test: t_server_options.test_server_options.TestServerOptions.test_server_retry_nonidempotent_disabled Apr 26 06:22:51 192.168.122.209 [51521.738634] Start test: t_server_options.test_server_options.TestServerOptions.test_server_retry_nonidempotent_enabled Apr 26 06:22:52 192.168.122.209 [51522.840725] [tdb] Start Tempesta DB Apr 26 06:22:52 192.168.122.209 [51522.979675] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:22:54 192.168.122.209 [51524.554679] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [51524.554679] Maybe that's fine, but it's worth checking the [51524.554679] config - if there is no relations between the [51524.554679] names, then host name confusion attack is possible. Apr 26 06:22:54 192.168.122.209 [51524.685533] [tempesta fw] Configuration processing is completed. Apr 26 06:22:54 192.168.122.209 [51524.734978] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:22:54 192.168.122.209 [51525.154166] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:22:54 192.168.122.209 [51525.180938] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:22:54 192.168.122.209 [51525.215684] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:22:54 192.168.122.209 [51525.265396] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:22:54 192.168.122.209 [51525.266419] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:22:54 192.168.122.209 [51525.305410] [tempesta fw] Tempesta FW is ready Apr 26 06:22:55 192.168.122.209 [51525.465532] [tempesta fw] Warning: request evicted: the number of retries exceeded, status 504: 127.0.0.2 Apr 26 06:22:55 192.168.122.209 [51525.956000] [tdb] Close table 'client0.tdb' Apr 26 06:22:55 192.168.122.209 [51526.136033] [tdb] Close table 'sessions0.tdb' Apr 26 06:22:58 192.168.122.209 [51529.324931] [tdb] Close table 'cache0.tdb' Apr 26 06:22:59 192.168.122.209 [51529.549043] [tdb] Close table 'filter0.tdb' Apr 26 06:22:59 192.168.122.209 [51529.549514] [tempesta fw] modules are stopped Apr 26 06:22:59 192.168.122.209 [51529.768005] [tempesta fw] exiting... Apr 26 06:22:59 192.168.122.209 [51529.908863] [tdb] Shutdown Tempesta DB Apr 26 06:22:59 192.168.122.209 [51530.109768] End test: t_server_options.test_server_options.TestServerOptions.test_server_retry_nonidempotent_enabled Apr 26 06:22:59 192.168.122.209 [51530.119951] Start test: t_sites.test_tempesta_tech.TestTempestaTechSite.test_auth_not_cached Apr 26 06:23:04 192.168.122.209 [51534.779262] lxdbr0: port 1(veth5822cb19) entered blocking state Apr 26 06:23:04 192.168.122.209 [51534.779867] lxdbr0: port 1(veth5822cb19) entered disabled state Apr 26 06:23:04 192.168.122.209 [51534.782772] device veth5822cb19 entered promiscuous mode Apr 26 06:23:06 192.168.122.209 [51536.711884] physVRXB85: renamed from veth443975e2 Apr 26 06:23:06 192.168.122.209 [51536.732072] eth0: renamed from physVRXB85 Apr 26 06:23:06 192.168.122.209 [51536.749614] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Apr 26 06:23:06 192.168.122.209 [51536.751088] lxdbr0: port 1(veth5822cb19) entered blocking state Apr 26 06:23:06 192.168.122.209 [51536.751878] lxdbr0: port 1(veth5822cb19) entered forwarding state Apr 26 06:23:06 192.168.122.209 [51536.752838] IPv6: ADDRCONF(NETDEV_CHANGE): lxdbr0: link becomes ready Apr 26 06:23:07 192.168.122.209 [51537.593867] Not activating Mandatory Access Control as /sbin/tomoyo-init does not exist. Apr 26 06:23:09 192.168.122.209 [51539.888406] [tdb] Start Tempesta DB Apr 26 06:23:09 192.168.122.209 [51540.048745] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:23:11 192.168.122.209 [51542.203908] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [51542.203908] Maybe that's fine, but it's worth checking the [51542.203908] config - if there is no relations between the [51542.203908] names, then host name confusion attack is possible. Apr 26 06:23:11 192.168.122.209 [51542.361739] [tempesta fw] Configuration processing is completed. Apr 26 06:23:11 192.168.122.209 [51542.404436] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:23:12 192.168.122.209 [51542.839762] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:23:12 192.168.122.209 [51542.922778] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:23:12 192.168.122.209 [51542.956836] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:23:12 192.168.122.209 [51543.108078] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:23:12 192.168.122.209 [51543.108682] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:23:12 192.168.122.209 [51543.169897] [tempesta fw] Tempesta FW is ready Apr 26 06:23:21 192.168.122.209 [51551.643421] [tempesta fw] 127.0.0.2 "default" "POST /wp-login.php HTTP/2.0" 302 0 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef17000a" "ja5h=ec4e27da00a80400" Apr 26 06:23:21 192.168.122.209 [51552.127565] [tempesta fw] 127.0.0.2 "default" "POST /wp-login.php HTTP/2.0" 302 0 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef17000a" "ja5h=ec4e27da00a80400" Apr 26 06:23:22 192.168.122.209 [51552.653619] [tempesta fw] 127.0.0.2 "default" "POST /wp-login.php HTTP/2.0" 302 0 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef17000a" "ja5h=ec4e27da00a80400" Apr 26 06:23:22 192.168.122.209 [51553.088739] [tdb] Close table 'client0.tdb' Apr 26 06:23:22 192.168.122.209 [51553.410568] [tdb] Close table 'sessions0.tdb' Apr 26 06:23:26 192.168.122.209 [51557.172871] [tdb] Close table 'cache0.tdb' Apr 26 06:23:26 192.168.122.209 [51557.450781] [tdb] Close table 'filter0.tdb' Apr 26 06:23:26 192.168.122.209 [51557.451197] [tempesta fw] modules are stopped Apr 26 06:23:27 192.168.122.209 [51557.690899] [tempesta fw] exiting... Apr 26 06:23:27 192.168.122.209 [51557.829294] [tdb] Shutdown Tempesta DB Apr 26 06:23:37 192.168.122.209 [51567.993827] physVRXB85: renamed from eth0 Apr 26 06:23:37 192.168.122.209 [51568.012706] lxdbr0: port 1(veth5822cb19) entered disabled state Apr 26 06:23:37 192.168.122.209 [51568.026741] veth443975e2: renamed from physVRXB85 Apr 26 06:23:38 192.168.122.209 [51568.955520] device veth5822cb19 left promiscuous mode Apr 26 06:23:38 192.168.122.209 [51568.956746] lxdbr0: port 1(veth5822cb19) entered disabled state Apr 26 06:23:39 192.168.122.209 [51570.441959] End test: t_sites.test_tempesta_tech.TestTempestaTechSite.test_auth_not_cached Apr 26 06:23:40 192.168.122.209 [51570.461494] Start test: t_sites.test_tempesta_tech.TestTempestaTechSite.test_blog_post_cached Apr 26 06:23:40 192.168.122.209 [51571.033873] lxdbr0: port 1(veth12ff36ee) entered blocking state Apr 26 06:23:40 192.168.122.209 [51571.034483] lxdbr0: port 1(veth12ff36ee) entered disabled state Apr 26 06:23:40 192.168.122.209 [51571.036510] device veth12ff36ee entered promiscuous mode Apr 26 06:23:41 192.168.122.209 [51571.896345] physZdvRdj: renamed from veth53bf5c87 Apr 26 06:23:41 192.168.122.209 [51571.936245] eth0: renamed from physZdvRdj Apr 26 06:23:41 192.168.122.209 [51571.956733] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Apr 26 06:23:41 192.168.122.209 [51571.959518] lxdbr0: port 1(veth12ff36ee) entered blocking state Apr 26 06:23:41 192.168.122.209 [51571.960955] lxdbr0: port 1(veth12ff36ee) entered forwarding state Apr 26 06:23:42 192.168.122.209 [51572.678210] Not activating Mandatory Access Control as /sbin/tomoyo-init does not exist. Apr 26 06:23:44 192.168.122.209 [51575.096822] [tdb] Start Tempesta DB Apr 26 06:23:44 192.168.122.209 [51575.278271] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:23:46 192.168.122.209 [51577.031401] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [51577.031401] Maybe that's fine, but it's worth checking the [51577.031401] config - if there is no relations between the [51577.031401] names, then host name confusion attack is possible. Apr 26 06:23:46 192.168.122.209 [51577.182784] [tempesta fw] Configuration processing is completed. Apr 26 06:23:46 192.168.122.209 [51577.241423] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:23:47 192.168.122.209 [51577.674182] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:23:47 192.168.122.209 [51577.750170] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:23:47 192.168.122.209 [51577.781748] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:23:47 192.168.122.209 [51577.896259] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:23:47 192.168.122.209 [51577.896872] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:23:47 192.168.122.209 [51577.953982] [tempesta fw] Tempesta FW is ready Apr 26 06:23:55 192.168.122.209 [51586.012284] [tempesta fw] 127.0.0.2 "default" "GET /blog/cdn-non-hierarchical-caching/ HTTP/2.0" 200 151660 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef17000a" "ja5h=6564157c008c0300" Apr 26 06:23:55 192.168.122.209 [51586.121608] [tempesta fw] 127.0.0.2 "default" "GET /blog/cdn-non-hierarchical-caching/ HTTP/2.0" 200 151660 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef17000a" "ja5h=6564157c008c0300" Apr 26 06:23:55 192.168.122.209 [51586.234311] [tempesta fw] 127.0.0.2 "default" "GET /blog/cdn-non-hierarchical-caching/ HTTP/2.0" 200 151660 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef17000a" "ja5h=6564157c008c0300" Apr 26 06:23:56 192.168.122.209 [51586.697237] [tdb] Close table 'client0.tdb' Apr 26 06:23:56 192.168.122.209 [51586.885253] [tdb] Close table 'sessions0.tdb' Apr 26 06:24:02 192.168.122.209 [51593.298004] [tdb] Close table 'cache0.tdb' Apr 26 06:24:03 192.168.122.209 [51593.617283] [tdb] Close table 'filter0.tdb' Apr 26 06:24:03 192.168.122.209 [51593.617732] [tempesta fw] modules are stopped Apr 26 06:24:03 192.168.122.209 [51593.857913] [tempesta fw] exiting... Apr 26 06:24:03 192.168.122.209 [51594.002779] [tdb] Shutdown Tempesta DB Apr 26 06:24:12 192.168.122.209 [51602.755343] physZdvRdj: renamed from eth0 Apr 26 06:24:12 192.168.122.209 [51602.787018] lxdbr0: port 1(veth12ff36ee) entered disabled state Apr 26 06:24:12 192.168.122.209 [51602.802972] veth53bf5c87: renamed from physZdvRdj Apr 26 06:24:13 192.168.122.209 [51603.782360] device veth12ff36ee left promiscuous mode Apr 26 06:24:13 192.168.122.209 [51603.782882] lxdbr0: port 1(veth12ff36ee) entered disabled state Apr 26 06:24:14 192.168.122.209 [51604.925570] End test: t_sites.test_tempesta_tech.TestTempestaTechSite.test_blog_post_cached Apr 26 06:24:14 192.168.122.209 [51604.947059] Start test: t_sites.test_tempesta_tech.TestTempestaTechSite.test_blog_post_flow Apr 26 06:24:15 192.168.122.209 [51605.472290] lxdbr0: port 1(vethedf84587) entered blocking state Apr 26 06:24:15 192.168.122.209 [51605.472892] lxdbr0: port 1(vethedf84587) entered disabled state Apr 26 06:24:15 192.168.122.209 [51605.475607] device vethedf84587 entered promiscuous mode Apr 26 06:24:15 192.168.122.209 [51606.260494] physdcmSGX: renamed from veth6190274c Apr 26 06:24:15 192.168.122.209 [51606.308340] eth0: renamed from physdcmSGX Apr 26 06:24:15 192.168.122.209 [51606.332570] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Apr 26 06:24:15 192.168.122.209 [51606.334938] lxdbr0: port 1(vethedf84587) entered blocking state Apr 26 06:24:15 192.168.122.209 [51606.336516] lxdbr0: port 1(vethedf84587) entered forwarding state Apr 26 06:24:16 192.168.122.209 [51607.057296] Not activating Mandatory Access Control as /sbin/tomoyo-init does not exist. Apr 26 06:24:18 192.168.122.209 [51609.410914] [tdb] Start Tempesta DB Apr 26 06:24:19 192.168.122.209 [51609.625472] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:24:21 192.168.122.209 [51611.590845] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [51611.590845] Maybe that's fine, but it's worth checking the [51611.590845] config - if there is no relations between the [51611.590845] names, then host name confusion attack is possible. Apr 26 06:24:21 192.168.122.209 [51611.768183] [tempesta fw] Configuration processing is completed. Apr 26 06:24:21 192.168.122.209 [51611.827327] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:24:22 192.168.122.209 [51612.586352] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:24:22 192.168.122.209 [51612.667147] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:24:22 192.168.122.209 [51612.712784] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:24:22 192.168.122.209 [51612.798407] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:24:22 192.168.122.209 [51612.799079] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:24:22 192.168.122.209 [51612.846449] [tempesta fw] Tempesta FW is ready Apr 26 06:24:29 192.168.122.209 [51619.854130] [tempesta fw] 127.0.0.2 "default" "POST /wp-login.php HTTP/2.0" 302 0 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef17000a" "ja5h=ec4e27da00a80400" Apr 26 06:24:30 192.168.122.209 [51620.733953] [tempesta fw] 127.0.0.2 "default" "GET /wp-admin/admin-ajax.php?action=rest-nonce HTTP/2.0" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef17000a" "ja5h=5b4cec5e008c6380" Apr 26 06:24:31 192.168.122.209 [51621.550878] [tempesta fw] 127.0.0.2 "default" "POST /index.php?rest_route=/wp/v2/posts HTTP/2.0" 201 9740 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef17000a" "ja5h=860fe43600a84500" Apr 26 06:24:32 192.168.122.209 [51622.695627] [tempesta fw] 127.0.0.2 "default" "GET /uncategorized/1745648654.5858269_post_title/ HTTP/2.0" 200 137596 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef17000a" "ja5h=6564157c008c0300" Apr 26 06:24:32 192.168.122.209 [51623.244119] [tempesta fw] 127.0.0.2 "default" "GET /comments/feed/ HTTP/2.0" 200 6776 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef17000a" "ja5h=6564157c008c0300" Apr 26 06:24:33 192.168.122.209 [51623.661276] [tempesta fw] 127.0.0.2 "default" "POST /wp-comments-post.php HTTP/2.0" 302 0 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef17000a" "ja5h=275bb8c000a84480" Apr 26 06:24:33 192.168.122.209 [51623.757912] [tempesta fw] 127.0.0.2 "default" "GET /uncategorized/1745648654.5858269_post_title/ HTTP/2.0" 200 137596 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef17000a" "ja5h=6564157c008c0300" Apr 26 06:24:33 192.168.122.209 [51623.855971] [tempesta fw] 127.0.0.2 "default" "GET /comments/feed/ HTTP/2.0" 200 6776 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef17000a" "ja5h=6564157c008c0300" Apr 26 06:24:33 192.168.122.209 [51623.939114] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:24:33 192.168.122.209 [51623.940674] [tempesta fw] 127.0.0.2 "default" "PURGE /uncategorized/1745648654.5858269_post_title/ HTTP/2.0" 200 0 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef17000a" "ja5h=c0c119cc00c00380" Apr 26 06:24:33 192.168.122.209 [51624.043072] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:24:33 192.168.122.209 [51624.044360] [tempesta fw] 127.0.0.2 "default" "PURGE /comments/feed/ HTTP/2.0" 200 0 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef17000a" "ja5h=c0c119cc00c00380" Apr 26 06:24:34 192.168.122.209 [51624.978781] [tempesta fw] 127.0.0.2 "default" "GET /uncategorized/1745648654.5858269_post_title/ HTTP/2.0" 200 139512 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef17000a" "ja5h=6564157c008c0300" Apr 26 06:24:35 192.168.122.209 [51625.621669] [tempesta fw] 127.0.0.2 "default" "GET /comments/feed/ HTTP/2.0" 200 6777 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef17000a" "ja5h=6564157c008c0300" Apr 26 06:24:35 192.168.122.209 [51626.070367] [tdb] Close table 'client0.tdb' Apr 26 06:24:35 192.168.122.209 [51626.283398] [tdb] Close table 'sessions0.tdb' Apr 26 06:24:39 192.168.122.209 [51630.401157] [tdb] Close table 'cache0.tdb' Apr 26 06:24:40 192.168.122.209 [51630.683082] [tdb] Close table 'filter0.tdb' Apr 26 06:24:40 192.168.122.209 [51630.683512] [tempesta fw] modules are stopped Apr 26 06:24:40 192.168.122.209 [51630.928785] [tempesta fw] exiting... Apr 26 06:24:40 192.168.122.209 [51631.090004] [tdb] Shutdown Tempesta DB Apr 26 06:24:47 192.168.122.209 [51638.284215] physdcmSGX: renamed from eth0 Apr 26 06:24:47 192.168.122.209 [51638.304875] lxdbr0: port 1(vethedf84587) entered disabled state Apr 26 06:24:47 192.168.122.209 [51638.330265] veth6190274c: renamed from physdcmSGX Apr 26 06:24:48 192.168.122.209 [51639.307613] device vethedf84587 left promiscuous mode Apr 26 06:24:48 192.168.122.209 [51639.308132] lxdbr0: port 1(vethedf84587) entered disabled state Apr 26 06:24:49 192.168.122.209 [51640.364506] End test: t_sites.test_tempesta_tech.TestTempestaTechSite.test_blog_post_flow Apr 26 06:24:49 192.168.122.209 [51640.379297] Start test: t_sites.test_tempesta_tech.TestTempestaTechSite.test_blog_post_not_cached_for_authenticated_user Apr 26 06:24:50 192.168.122.209 [51640.926895] lxdbr0: port 1(vethae62dd7f) entered blocking state Apr 26 06:24:50 192.168.122.209 [51640.927508] lxdbr0: port 1(vethae62dd7f) entered disabled state Apr 26 06:24:50 192.168.122.209 [51640.929453] device vethae62dd7f entered promiscuous mode Apr 26 06:24:51 192.168.122.209 [51641.553914] physyNcnTp: renamed from vethb77149ec Apr 26 06:24:51 192.168.122.209 [51641.582106] eth0: renamed from physyNcnTp Apr 26 06:24:51 192.168.122.209 [51641.600637] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Apr 26 06:24:51 192.168.122.209 [51641.602541] lxdbr0: port 1(vethae62dd7f) entered blocking state Apr 26 06:24:51 192.168.122.209 [51641.603736] lxdbr0: port 1(vethae62dd7f) entered forwarding state Apr 26 06:24:51 192.168.122.209 [51642.278239] Not activating Mandatory Access Control as /sbin/tomoyo-init does not exist. Apr 26 06:24:54 192.168.122.209 [51644.612597] [tdb] Start Tempesta DB Apr 26 06:24:54 192.168.122.209 [51644.791682] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:24:56 192.168.122.209 [51646.823349] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [51646.823349] Maybe that's fine, but it's worth checking the [51646.823349] config - if there is no relations between the [51646.823349] names, then host name confusion attack is possible. Apr 26 06:24:56 192.168.122.209 [51647.002857] [tempesta fw] Configuration processing is completed. Apr 26 06:24:56 192.168.122.209 [51647.056520] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:24:57 192.168.122.209 [51647.613316] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:24:57 192.168.122.209 [51647.671463] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:24:57 192.168.122.209 [51647.699311] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:24:57 192.168.122.209 [51647.843035] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:24:57 192.168.122.209 [51647.843987] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:24:57 192.168.122.209 [51647.930806] [tempesta fw] Tempesta FW is ready Apr 26 06:25:03 192.168.122.209 [51654.286586] [tempesta fw] 127.0.0.2 "default" "POST /wp-login.php HTTP/2.0" 302 0 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef17000a" "ja5h=ec4e27da00a80400" Apr 26 06:25:05 192.168.122.209 [51655.460518] [tempesta fw] 127.0.0.2 "default" "GET /blog/cdn-non-hierarchical-caching/ HTTP/2.0" 200 167939 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef17000a" "ja5h=5b4cec5e008c4380" Apr 26 06:25:05 192.168.122.209 [51656.283467] [tempesta fw] 127.0.0.2 "default" "GET /blog/cdn-non-hierarchical-caching/ HTTP/2.0" 200 167939 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef17000a" "ja5h=5b4cec5e008c4380" Apr 26 06:25:06 192.168.122.209 [51657.147872] [tempesta fw] 127.0.0.2 "default" "GET /blog/cdn-non-hierarchical-caching/ HTTP/2.0" 200 167939 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef17000a" "ja5h=5b4cec5e008c4380" Apr 26 06:25:07 192.168.122.209 [51657.592338] [tdb] Close table 'client0.tdb' Apr 26 06:25:07 192.168.122.209 [51657.787273] [tdb] Close table 'sessions0.tdb' Apr 26 06:25:12 192.168.122.209 [51663.443533] [tdb] Close table 'cache0.tdb' Apr 26 06:25:13 192.168.122.209 [51663.742290] [tdb] Close table 'filter0.tdb' Apr 26 06:25:13 192.168.122.209 [51663.742720] [tempesta fw] modules are stopped Apr 26 06:25:13 192.168.122.209 [51663.931523] [tempesta fw] exiting... Apr 26 06:25:13 192.168.122.209 [51664.075163] [tdb] Shutdown Tempesta DB Apr 26 06:25:21 192.168.122.209 [51671.466902] physyNcnTp: renamed from eth0 Apr 26 06:25:21 192.168.122.209 [51671.487836] lxdbr0: port 1(vethae62dd7f) entered disabled state Apr 26 06:25:21 192.168.122.209 [51671.512682] vethb77149ec: renamed from physyNcnTp Apr 26 06:25:21 192.168.122.209 [51672.341903] device vethae62dd7f left promiscuous mode Apr 26 06:25:21 192.168.122.209 [51672.342426] lxdbr0: port 1(vethae62dd7f) entered disabled state Apr 26 06:25:22 192.168.122.209 [51673.285942] End test: t_sites.test_tempesta_tech.TestTempestaTechSite.test_blog_post_not_cached_for_authenticated_user Apr 26 06:25:22 192.168.122.209 [51673.298311] Start test: t_sites.test_tempesta_tech.TestTempestaTechSite.test_get_admin_resource_with_assets Apr 26 06:25:24 192.168.122.209 [51674.651430] lxdbr0: port 1(veth9ab0cf90) entered blocking state Apr 26 06:25:24 192.168.122.209 [51674.652046] lxdbr0: port 1(veth9ab0cf90) entered disabled state Apr 26 06:25:24 192.168.122.209 [51674.654092] device veth9ab0cf90 entered promiscuous mode Apr 26 06:25:25 192.168.122.209 [51675.729834] physSZHZVB: renamed from veth47dffb4b Apr 26 06:25:25 192.168.122.209 [51675.768834] eth0: renamed from physSZHZVB Apr 26 06:25:25 192.168.122.209 [51675.784279] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Apr 26 06:25:25 192.168.122.209 [51675.785249] lxdbr0: port 1(veth9ab0cf90) entered blocking state Apr 26 06:25:25 192.168.122.209 [51675.785812] lxdbr0: port 1(veth9ab0cf90) entered forwarding state Apr 26 06:25:26 192.168.122.209 [51676.491734] Not activating Mandatory Access Control as /sbin/tomoyo-init does not exist. Apr 26 06:25:28 192.168.122.209 [51678.801035] [tdb] Start Tempesta DB Apr 26 06:25:28 192.168.122.209 [51679.017843] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:25:30 192.168.122.209 [51681.048198] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [51681.048198] Maybe that's fine, but it's worth checking the [51681.048198] config - if there is no relations between the [51681.048198] names, then host name confusion attack is possible. Apr 26 06:25:30 192.168.122.209 [51681.235391] [tempesta fw] Configuration processing is completed. Apr 26 06:25:30 192.168.122.209 [51681.279646] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:25:31 192.168.122.209 [51681.715920] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:25:31 192.168.122.209 [51681.778563] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:25:31 192.168.122.209 [51681.806499] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:25:31 192.168.122.209 [51681.923240] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:25:31 192.168.122.209 [51681.923849] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:25:31 192.168.122.209 [51682.003203] [tempesta fw] Tempesta FW is ready Apr 26 06:25:37 192.168.122.209 [51688.326069] [tempesta fw] 127.0.0.2 "default" "POST /wp-login.php HTTP/2.0" 302 0 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef17000a" "ja5h=ec4e27da00a80400" Apr 26 06:25:41 192.168.122.209 [51691.957991] [tempesta fw] 127.0.0.2 "default" "GET /wp-admin/index.php HTTP/2.0" 200 2101412 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef17000a" "ja5h=5b4cec5e008c6380" Apr 26 06:25:42 192.168.122.209 [51693.069122] [tempesta fw] 127.0.0.1 "default" "GET /wp-admin/index.php HTTP/2.0" 200 217215 "-" "nghttp2/1.59.0" "ja5t=66cb8f0004e3000a" "ja5h=2cc58318008c8480" Apr 26 06:25:44 192.168.122.209 [51694.886275] [tempesta fw] 127.0.0.2 "default" "GET /wp-admin/profile.php HTTP/2.0" 200 2350792 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef17000a" "ja5h=5b4cec5e008c6380" Apr 26 06:25:45 192.168.122.209 [51696.150911] [tempesta fw] 127.0.0.1 "default" "GET /wp-admin/profile.php HTTP/2.0" 200 238018 "-" "nghttp2/1.59.0" "ja5t=66cb8f0004e3000a" "ja5h=2cc58318008c8480" Apr 26 06:25:46 192.168.122.209 [51696.903152] [tempesta fw] 127.0.0.2 "default" "GET /wp-admin/edit-comments.php HTTP/2.0" 200 2173487 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef17000a" "ja5h=5b4cec5e008c6380" Apr 26 06:25:47 192.168.122.209 [51697.882771] [tempesta fw] 127.0.0.1 "default" "GET /wp-admin/edit-comments.php HTTP/2.0" 200 211786 "-" "nghttp2/1.59.0" "ja5t=66cb8f0004e3000a" "ja5h=2cc58318008c8480" Apr 26 06:25:48 192.168.122.209 [51698.935232] [tempesta fw] 127.0.0.2 "default" "GET /wp-admin/edit.php HTTP/2.0" 200 2280236 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef17000a" "ja5h=5b4cec5e008c6380" Apr 26 06:25:49 192.168.122.209 [51699.833739] [tempesta fw] 127.0.0.1 "default" "GET /wp-admin/edit.php HTTP/2.0" 200 217667 "-" "nghttp2/1.59.0" "ja5t=66cb8f0004e3000a" "ja5h=2cc58318008c8480" Apr 26 06:25:49 192.168.122.209 [51700.355473] [tdb] Close table 'client0.tdb' Apr 26 06:25:50 192.168.122.209 [51700.623823] [tdb] Close table 'sessions0.tdb' Apr 26 06:25:56 192.168.122.209 [51706.581597] [tdb] Close table 'cache0.tdb' Apr 26 06:25:56 192.168.122.209 [51706.880204] [tdb] Close table 'filter0.tdb' Apr 26 06:25:56 192.168.122.209 [51706.880643] [tempesta fw] modules are stopped Apr 26 06:25:56 192.168.122.209 [51707.090116] [tempesta fw] exiting... Apr 26 06:25:56 192.168.122.209 [51707.191749] [tdb] Shutdown Tempesta DB Apr 26 06:26:05 192.168.122.209 [51716.174664] physSZHZVB: renamed from eth0 Apr 26 06:26:05 192.168.122.209 [51716.189570] lxdbr0: port 1(veth9ab0cf90) entered disabled state Apr 26 06:26:05 192.168.122.209 [51716.212555] veth47dffb4b: renamed from physSZHZVB Apr 26 06:26:06 192.168.122.209 [51717.231997] device veth9ab0cf90 left promiscuous mode Apr 26 06:26:06 192.168.122.209 [51717.232521] lxdbr0: port 1(veth9ab0cf90) entered disabled state Apr 26 06:26:08 192.168.122.209 [51718.485552] End test: t_sites.test_tempesta_tech.TestTempestaTechSite.test_get_admin_resource_with_assets Apr 26 06:26:08 192.168.122.209 [51718.495379] Start test: t_sites.test_tempesta_tech.TestTempestaTechSite.test_get_resource Apr 26 06:26:08 192.168.122.209 [51718.950410] lxdbr0: port 1(veth2b2d836c) entered blocking state Apr 26 06:26:08 192.168.122.209 [51718.951011] lxdbr0: port 1(veth2b2d836c) entered disabled state Apr 26 06:26:08 192.168.122.209 [51718.953949] device veth2b2d836c entered promiscuous mode Apr 26 06:26:09 192.168.122.209 [51719.574170] physpTs2Pt: renamed from vethd81074bb Apr 26 06:26:09 192.168.122.209 [51719.602352] eth0: renamed from physpTs2Pt Apr 26 06:26:09 192.168.122.209 [51719.623030] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Apr 26 06:26:09 192.168.122.209 [51719.625850] lxdbr0: port 1(veth2b2d836c) entered blocking state Apr 26 06:26:09 192.168.122.209 [51719.627583] lxdbr0: port 1(veth2b2d836c) entered forwarding state Apr 26 06:26:09 192.168.122.209 [51720.305233] Not activating Mandatory Access Control as /sbin/tomoyo-init does not exist. Apr 26 06:26:12 192.168.122.209 [51722.538584] [tdb] Start Tempesta DB Apr 26 06:26:12 192.168.122.209 [51722.728948] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:26:14 192.168.122.209 [51724.665176] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [51724.665176] Maybe that's fine, but it's worth checking the [51724.665176] config - if there is no relations between the [51724.665176] names, then host name confusion attack is possible. Apr 26 06:26:14 192.168.122.209 [51724.852442] [tempesta fw] Configuration processing is completed. Apr 26 06:26:14 192.168.122.209 [51724.903053] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:26:14 192.168.122.209 [51725.333929] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:26:14 192.168.122.209 [51725.362555] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:26:14 192.168.122.209 [51725.395469] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:26:15 192.168.122.209 [51725.493789] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:26:15 192.168.122.209 [51725.494401] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:26:15 192.168.122.209 [51725.559998] [tempesta fw] Tempesta FW is ready Apr 26 06:26:21 192.168.122.209 [51732.109766] [tempesta fw] 127.0.0.2 "default" "GET /license.txt HTTP/2.0" 200 19915 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef17000a" "ja5h=6564157c008c0300" Apr 26 06:26:21 192.168.122.209 [51732.212937] [tempesta fw] 127.0.0.2 "default" "GET /wp-content/uploads/2023/10/tfw_wp_http2-150x150.png HTTP/2.0" 200 16033 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef17000a" "ja5h=6564157c008c0300" Apr 26 06:26:21 192.168.122.209 [51732.325809] [tempesta fw] 127.0.0.2 "default" "GET /wp-content/uploads/2023/10/tfw_wp_http2-1536x981.png HTTP/2.0" 200 484438 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef17000a" "ja5h=6564157c008c0300" Apr 26 06:26:23 192.168.122.209 [51733.630154] [tempesta fw] 127.0.0.2 "default" "GET / HTTP/2.0" 200 298279 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef17000a" "ja5h=6564157c008c0300" Apr 26 06:26:24 192.168.122.209 [51734.585386] [tempesta fw] 127.0.0.2 "default" "GET /knowledge-base/DDoS-mitigation/ HTTP/2.0" 200 144515 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef17000a" "ja5h=6564157c008c0300" Apr 26 06:26:25 192.168.122.209 [51735.460623] [tempesta fw] 127.0.0.2 "default" "GET /404-absolutely/doesnt-exist HTTP/2.0" 404 105810 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef17000a" "ja5h=6564157c008c0300" Apr 26 06:26:25 192.168.122.209 [51735.941621] [tdb] Close table 'client0.tdb' Apr 26 06:26:25 192.168.122.209 [51736.157789] [tdb] Close table 'sessions0.tdb' Apr 26 06:26:29 192.168.122.209 [51739.503425] [tdb] Close table 'cache0.tdb' Apr 26 06:26:29 192.168.122.209 [51739.779601] [tdb] Close table 'filter0.tdb' Apr 26 06:26:29 192.168.122.209 [51739.780091] [tempesta fw] modules are stopped Apr 26 06:26:29 192.168.122.209 [51740.077235] [tempesta fw] exiting... Apr 26 06:26:29 192.168.122.209 [51740.240372] [tdb] Shutdown Tempesta DB Apr 26 06:26:36 192.168.122.209 [51747.290647] physpTs2Pt: renamed from eth0 Apr 26 06:26:36 192.168.122.209 [51747.319421] lxdbr0: port 1(veth2b2d836c) entered disabled state Apr 26 06:26:36 192.168.122.209 [51747.346636] vethd81074bb: renamed from physpTs2Pt Apr 26 06:26:37 192.168.122.209 [51748.013822] device veth2b2d836c left promiscuous mode Apr 26 06:26:37 192.168.122.209 [51748.014402] lxdbr0: port 1(veth2b2d836c) entered disabled state Apr 26 06:26:38 192.168.122.209 [51748.971312] End test: t_sites.test_tempesta_tech.TestTempestaTechSite.test_get_resource Apr 26 06:26:38 192.168.122.209 [51748.993434] Start test: t_sites.test_tempesta_tech.TestTempestaTechSite.test_get_resource_with_assets Apr 26 06:26:39 192.168.122.209 [51749.550975] lxdbr0: port 1(veth8e21eeba) entered blocking state Apr 26 06:26:39 192.168.122.209 [51749.551650] lxdbr0: port 1(veth8e21eeba) entered disabled state Apr 26 06:26:39 192.168.122.209 [51749.559325] device veth8e21eeba entered promiscuous mode Apr 26 06:26:39 192.168.122.209 [51750.139077] physO7aj9b: renamed from veth597764ee Apr 26 06:26:39 192.168.122.209 [51750.189760] eth0: renamed from physO7aj9b Apr 26 06:26:39 192.168.122.209 [51750.216098] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Apr 26 06:26:39 192.168.122.209 [51750.218884] lxdbr0: port 1(veth8e21eeba) entered blocking state Apr 26 06:26:39 192.168.122.209 [51750.220270] lxdbr0: port 1(veth8e21eeba) entered forwarding state Apr 26 06:26:40 192.168.122.209 [51750.917713] Not activating Mandatory Access Control as /sbin/tomoyo-init does not exist. Apr 26 06:26:42 192.168.122.209 [51753.305969] [tdb] Start Tempesta DB Apr 26 06:26:43 192.168.122.209 [51753.533362] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:26:45 192.168.122.209 [51755.526497] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [51755.526497] Maybe that's fine, but it's worth checking the [51755.526497] config - if there is no relations between the [51755.526497] names, then host name confusion attack is possible. Apr 26 06:26:45 192.168.122.209 [51755.724360] [tempesta fw] Configuration processing is completed. Apr 26 06:26:45 192.168.122.209 [51755.768153] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:26:45 192.168.122.209 [51756.246281] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:26:45 192.168.122.209 [51756.277720] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:26:45 192.168.122.209 [51756.305790] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:26:45 192.168.122.209 [51756.453022] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:26:45 192.168.122.209 [51756.453645] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:26:46 192.168.122.209 [51756.528164] [tempesta fw] Tempesta FW is ready Apr 26 06:26:51 192.168.122.209 [51762.062103] [tempesta fw] 127.0.0.2 "default" "GET /license.txt HTTP/2.0" 200 19915 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef17000a" "ja5h=6564157c008c0300" Apr 26 06:26:51 192.168.122.209 [51762.252769] [tempesta fw] 127.0.0.1 "default" "GET /license.txt HTTP/2.0" 200 7297 "-" "nghttp2/1.59.0" "ja5t=66cb8f0004e3000a" "ja5h=786f0bea008c0400" Apr 26 06:26:52 192.168.122.209 [51763.440113] [tempesta fw] 127.0.0.2 "default" "GET / HTTP/2.0" 200 298279 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef17000a" "ja5h=6564157c008c0300" Apr 26 06:26:53 192.168.122.209 [51764.003660] [tempesta fw] 127.0.0.1 "default" "GET / HTTP/2.0" 301 0 "-" "nghttp2/1.59.0" "ja5t=66cb8f0004e3000a" "ja5h=786f0bea008c0400" Apr 26 06:26:54 192.168.122.209 [51765.087834] [tempesta fw] 127.0.0.2 "default" "GET /network-security-performance-analysis/ HTTP/2.0" 200 275641 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef17000a" "ja5h=6564157c008c0300" Apr 26 06:26:55 192.168.122.209 [51766.139663] [tempesta fw] 127.0.0.1 "default" "GET /network-security-performance-analysis/ HTTP/2.0" 200 34190 "-" "nghttp2/1.59.0" "ja5t=66cb8f0004e3000a" "ja5h=786f0bea008c0400" Apr 26 06:26:55 192.168.122.209 [51766.159626] [tempesta fw] 127.0.0.1 "default" "GET /wp-content/uploads/2022/10/main.js HTTP/2.0" 200 2863 "-" "nghttp2/1.59.0" "ja5t=66cb8f0004e3000a" "ja5h=786f0bea008c0400" Apr 26 06:26:55 192.168.122.209 [51766.169634] [tempesta fw] 127.0.0.1 "default" "GET /wp-content/uploads/2022/10/highcharts.min_.js HTTP/2.0" 200 69628 "-" "nghttp2/1.59.0" "ja5t=66cb8f0004e3000a" "ja5h=786f0bea008c0400" Apr 26 06:26:56 192.168.122.209 [51767.156059] [tempesta fw] 127.0.0.2 "default" "GET /blog/cdn-non-hierarchical-caching/ HTTP/2.0" 200 151660 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef17000a" "ja5h=6564157c008c0300" Apr 26 06:26:57 192.168.122.209 [51768.180341] [tempesta fw] 127.0.0.1 "default" "GET /blog/cdn-non-hierarchical-caching/ HTTP/2.0" 200 30307 "-" "nghttp2/1.59.0" "ja5t=66cb8f0004e3000a" "ja5h=786f0bea008c0400" Apr 26 06:26:57 192.168.122.209 [51768.198836] [tempesta fw] 127.0.0.1 "default" "GET /wp-content/uploads/2022/10/main.js HTTP/2.0" 200 2863 "-" "nghttp2/1.59.0" "ja5t=66cb8f0004e3000a" "ja5h=786f0bea008c0400" Apr 26 06:26:57 192.168.122.209 [51768.215739] [tempesta fw] 127.0.0.1 "default" "GET /wp-content/uploads/2022/10/highcharts.min_.js HTTP/2.0" 200 69628 "-" "nghttp2/1.59.0" "ja5t=66cb8f0004e3000a" "ja5h=786f0bea008c0400" Apr 26 06:26:58 192.168.122.209 [51769.284012] [tempesta fw] 127.0.0.2 "default" "GET /blog/nginx-tail-latency/ HTTP/2.0" 200 191757 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef17000a" "ja5h=6564157c008c0300" Apr 26 06:26:59 192.168.122.209 [51770.243161] [tempesta fw] 127.0.0.1 "default" "GET /blog/nginx-tail-latency/ HTTP/2.0" 200 40128 "-" "nghttp2/1.59.0" "ja5t=66cb8f0004e3000a" "ja5h=786f0bea008c0400" Apr 26 06:26:59 192.168.122.209 [51770.252191] [tempesta fw] 127.0.0.1 "default" "GET /wp-content/uploads/2022/10/main.js HTTP/2.0" 200 2863 "-" "nghttp2/1.59.0" "ja5t=66cb8f0004e3000a" "ja5h=786f0bea008c0400" Apr 26 06:26:59 192.168.122.209 [51770.261422] [tempesta fw] 127.0.0.1 "default" "GET /wp-content/uploads/2022/10/highcharts.min_.js HTTP/2.0" 200 69628 "-" "nghttp2/1.59.0" "ja5t=66cb8f0004e3000a" "ja5h=786f0bea008c0400" Apr 26 06:27:00 192.168.122.209 [51770.711406] [tdb] Close table 'client0.tdb' Apr 26 06:27:00 192.168.122.209 [51770.914701] [tdb] Close table 'sessions0.tdb' Apr 26 06:27:06 192.168.122.209 [51776.607815] [tdb] Close table 'cache0.tdb' Apr 26 06:27:06 192.168.122.209 [51776.926042] [tdb] Close table 'filter0.tdb' Apr 26 06:27:06 192.168.122.209 [51776.926458] [tempesta fw] modules are stopped Apr 26 06:27:06 192.168.122.209 [51777.209591] [tempesta fw] exiting... Apr 26 06:27:06 192.168.122.209 [51777.338920] [tdb] Shutdown Tempesta DB Apr 26 06:27:15 192.168.122.209 [51785.640052] physO7aj9b: renamed from eth0 Apr 26 06:27:15 192.168.122.209 [51785.665561] lxdbr0: port 1(veth8e21eeba) entered disabled state Apr 26 06:27:15 192.168.122.209 [51785.685177] veth597764ee: renamed from physO7aj9b Apr 26 06:27:16 192.168.122.209 [51786.627515] device veth8e21eeba left promiscuous mode Apr 26 06:27:16 192.168.122.209 [51786.628067] lxdbr0: port 1(veth8e21eeba) entered disabled state Apr 26 06:27:17 192.168.122.209 [51787.653500] End test: t_sites.test_tempesta_tech.TestTempestaTechSite.test_get_resource_with_assets Apr 26 06:27:17 192.168.122.209 [51787.666771] Start test: t_sites.test_tempesta_tech.TestTempestaTechSite.test_page_cached Apr 26 06:27:17 192.168.122.209 [51788.212948] lxdbr0: port 1(veth88843c7f) entered blocking state Apr 26 06:27:17 192.168.122.209 [51788.213600] lxdbr0: port 1(veth88843c7f) entered disabled state Apr 26 06:27:17 192.168.122.209 [51788.215954] device veth88843c7f entered promiscuous mode Apr 26 06:27:18 192.168.122.209 [51788.974810] physHK4auR: renamed from veth11a1dee7 Apr 26 06:27:18 192.168.122.209 [51789.011180] eth0: renamed from physHK4auR Apr 26 06:27:18 192.168.122.209 [51789.027520] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Apr 26 06:27:18 192.168.122.209 [51789.030400] lxdbr0: port 1(veth88843c7f) entered blocking state Apr 26 06:27:18 192.168.122.209 [51789.032141] lxdbr0: port 1(veth88843c7f) entered forwarding state Apr 26 06:27:19 192.168.122.209 [51789.742460] Not activating Mandatory Access Control as /sbin/tomoyo-init does not exist. Apr 26 06:27:21 192.168.122.209 [51792.342542] [tdb] Start Tempesta DB Apr 26 06:27:22 192.168.122.209 [51792.522731] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:27:24 192.168.122.209 [51794.667892] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [51794.667892] Maybe that's fine, but it's worth checking the [51794.667892] config - if there is no relations between the [51794.667892] names, then host name confusion attack is possible. Apr 26 06:27:24 192.168.122.209 [51794.853497] [tempesta fw] Configuration processing is completed. Apr 26 06:27:24 192.168.122.209 [51794.935762] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:27:25 192.168.122.209 [51795.602236] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:27:25 192.168.122.209 [51795.646208] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:27:25 192.168.122.209 [51795.689596] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:27:25 192.168.122.209 [51795.772752] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:27:25 192.168.122.209 [51795.773343] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:27:25 192.168.122.209 [51795.836605] [tempesta fw] Tempesta FW is ready Apr 26 06:27:31 192.168.122.209 [51801.712072] [tempesta fw] 127.0.0.2 "default" "GET /license.txt HTTP/2.0" 200 19915 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef17000a" "ja5h=6564157c008c0300" Apr 26 06:27:31 192.168.122.209 [51801.819642] [tempesta fw] 127.0.0.2 "default" "GET /license.txt HTTP/2.0" 200 19915 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef17000a" "ja5h=6564157c008c0300" Apr 26 06:27:31 192.168.122.209 [51801.934728] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:27:31 192.168.122.209 [51801.935394] [tempesta fw] 127.0.0.2 "default" "PURGE /license.txt HTTP/2.0" 200 0 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef17000a" "ja5h=6564157c00c00300" Apr 26 06:27:31 192.168.122.209 [51802.031966] [tempesta fw] 127.0.0.2 "default" "GET /license.txt HTTP/2.0" 200 19915 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef17000a" "ja5h=6564157c008c0300" Apr 26 06:27:32 192.168.122.209 [51802.508095] [tdb] Close table 'client0.tdb' Apr 26 06:27:32 192.168.122.209 [51802.706046] [tdb] Close table 'sessions0.tdb' Apr 26 06:27:35 192.168.122.209 [51806.144169] [tdb] Close table 'cache0.tdb' Apr 26 06:27:35 192.168.122.209 [51806.434633] [tdb] Close table 'filter0.tdb' Apr 26 06:27:35 192.168.122.209 [51806.435076] [tempesta fw] modules are stopped Apr 26 06:27:36 192.168.122.209 [51806.643498] [tempesta fw] exiting... Apr 26 06:27:36 192.168.122.209 [51806.798136] [tdb] Shutdown Tempesta DB Apr 26 06:27:42 192.168.122.209 [51813.372013] physHK4auR: renamed from eth0 Apr 26 06:27:42 192.168.122.209 [51813.405917] lxdbr0: port 1(veth88843c7f) entered disabled state Apr 26 06:27:42 192.168.122.209 [51813.428029] veth11a1dee7: renamed from physHK4auR Apr 26 06:27:43 192.168.122.209 [51814.134101] device veth88843c7f left promiscuous mode Apr 26 06:27:43 192.168.122.209 [51814.134602] lxdbr0: port 1(veth88843c7f) entered disabled state Apr 26 06:27:44 192.168.122.209 [51815.124781] End test: t_sites.test_tempesta_tech.TestTempestaTechSite.test_page_cached Apr 26 06:27:44 192.168.122.209 [51815.139562] Start test: t_stress.test_ddos.TestDDoSL7.test Apr 26 06:27:44 192.168.122.209 [51815.158572] End test: t_stress.test_ddos.TestDDoSL7.test Apr 26 06:27:44 192.168.122.209 [51815.180791] Start test: t_stress.test_stress.BaseCurlStress.test_concurrent_requests Apr 26 06:27:44 192.168.122.209 [51815.204002] End test: t_stress.test_stress.BaseCurlStress.test_concurrent_requests Apr 26 06:27:44 192.168.122.209 [51815.221260] Start test: t_stress.test_stress.BaseCurlStress.test_pipelined_requests Apr 26 06:27:44 192.168.122.209 [51815.234579] End test: t_stress.test_stress.BaseCurlStress.test_pipelined_requests Apr 26 06:27:44 192.168.122.209 [51815.254496] Start test: t_stress.test_stress.BaseCurlStress.test_range_requests Apr 26 06:27:44 192.168.122.209 [51815.277858] End test: t_stress.test_stress.BaseCurlStress.test_range_requests Apr 26 06:27:44 192.168.122.209 [51815.294364] Start test: t_stress.test_stress.BaseCurlStress.test_sequential_requests Apr 26 06:27:44 192.168.122.209 [51815.316450] End test: t_stress.test_stress.BaseCurlStress.test_sequential_requests Apr 26 06:27:44 192.168.122.209 [51815.336740] Start test: t_stress.test_stress.BaseWrkStress.test_concurrent_connections Apr 26 06:27:44 192.168.122.209 [51815.351977] End test: t_stress.test_stress.BaseWrkStress.test_concurrent_connections Apr 26 06:27:44 192.168.122.209 [51815.365982] Start test: t_stress.test_nginx.NginxCurlStress.test_concurrent_requests Apr 26 06:27:47 192.168.122.209 [51817.811467] End test: t_stress.test_nginx.NginxCurlStress.test_concurrent_requests Apr 26 06:27:47 192.168.122.209 [51817.826574] Start test: t_stress.test_nginx.NginxCurlStress.test_pipelined_requests Apr 26 06:27:48 192.168.122.209 [51819.098249] End test: t_stress.test_nginx.NginxCurlStress.test_pipelined_requests Apr 26 06:27:48 192.168.122.209 [51819.127592] Start test: t_stress.test_nginx.NginxCurlStress.test_range_requests Apr 26 06:27:59 192.168.122.209 [51829.794170] End test: t_stress.test_nginx.NginxCurlStress.test_range_requests Apr 26 06:27:59 192.168.122.209 [51829.809289] Start test: t_stress.test_nginx.NginxCurlStress.test_sequential_requests Apr 26 06:28:00 192.168.122.209 [51831.169046] End test: t_stress.test_nginx.NginxCurlStress.test_sequential_requests Apr 26 06:28:00 192.168.122.209 [51831.180202] Start test: t_stress.test_nginx.NginxH2CurlStress.test_concurrent_requests Apr 26 06:28:02 192.168.122.209 [51832.481841] End test: t_stress.test_nginx.NginxH2CurlStress.test_concurrent_requests Apr 26 06:28:02 192.168.122.209 [51832.504033] Start test: t_stress.test_nginx.NginxH2CurlStress.test_pipelined_requests Apr 26 06:28:03 192.168.122.209 [51833.590388] End test: t_stress.test_nginx.NginxH2CurlStress.test_pipelined_requests Apr 26 06:28:03 192.168.122.209 [51833.603048] Start test: t_stress.test_nginx.NginxH2CurlStress.test_range_requests Apr 26 06:28:13 192.168.122.209 [51843.733016] End test: t_stress.test_nginx.NginxH2CurlStress.test_range_requests Apr 26 06:28:13 192.168.122.209 [51843.761011] Start test: t_stress.test_nginx.NginxH2CurlStress.test_sequential_requests Apr 26 06:28:14 192.168.122.209 [51844.823044] End test: t_stress.test_nginx.NginxH2CurlStress.test_sequential_requests Apr 26 06:28:14 192.168.122.209 [51844.844955] Start test: t_stress.test_nginx.NginxTlsCurlStress.test_concurrent_requests Apr 26 06:28:15 192.168.122.209 [51845.958573] End test: t_stress.test_nginx.NginxTlsCurlStress.test_concurrent_requests Apr 26 06:28:15 192.168.122.209 [51845.969305] Start test: t_stress.test_nginx.NginxTlsCurlStress.test_pipelined_requests Apr 26 06:28:16 192.168.122.209 [51847.055615] End test: t_stress.test_nginx.NginxTlsCurlStress.test_pipelined_requests Apr 26 06:28:16 192.168.122.209 [51847.070996] Start test: t_stress.test_nginx.NginxTlsCurlStress.test_range_requests Apr 26 06:28:27 192.168.122.209 [51857.794140] End test: t_stress.test_nginx.NginxTlsCurlStress.test_range_requests Apr 26 06:28:27 192.168.122.209 [51857.808240] Start test: t_stress.test_nginx.NginxTlsCurlStress.test_sequential_requests Apr 26 06:28:28 192.168.122.209 [51859.205710] End test: t_stress.test_nginx.NginxTlsCurlStress.test_sequential_requests Apr 26 06:28:28 192.168.122.209 [51859.231225] Start test: t_stress.test_nginx.NginxTlsWrkStress.test_concurrent_connections Apr 26 06:28:39 192.168.122.209 [51870.451561] End test: t_stress.test_nginx.NginxTlsWrkStress.test_concurrent_connections Apr 26 06:28:40 192.168.122.209 [51870.468535] Start test: t_stress.test_nginx.NginxWrkStress.test_concurrent_connections Apr 26 06:28:51 192.168.122.209 [51881.608387] End test: t_stress.test_nginx.NginxWrkStress.test_concurrent_connections Apr 26 06:28:51 192.168.122.209 [51881.621938] Start test: t_stress.test_stress.BaseCurlStress.test_concurrent_requests Apr 26 06:28:51 192.168.122.209 [51881.634493] End test: t_stress.test_stress.BaseCurlStress.test_concurrent_requests Apr 26 06:28:51 192.168.122.209 [51881.658402] Start test: t_stress.test_stress.BaseCurlStress.test_pipelined_requests Apr 26 06:28:51 192.168.122.209 [51881.668959] End test: t_stress.test_stress.BaseCurlStress.test_pipelined_requests Apr 26 06:28:51 192.168.122.209 [51881.694804] Start test: t_stress.test_stress.BaseCurlStress.test_range_requests Apr 26 06:28:51 192.168.122.209 [51881.709275] End test: t_stress.test_stress.BaseCurlStress.test_range_requests Apr 26 06:28:51 192.168.122.209 [51881.727541] Start test: t_stress.test_stress.BaseCurlStress.test_sequential_requests Apr 26 06:28:51 192.168.122.209 [51881.742938] End test: t_stress.test_stress.BaseCurlStress.test_sequential_requests Apr 26 06:28:51 192.168.122.209 [51881.756045] Start test: t_stress.test_stress.BaseWrkStress.test_concurrent_connections Apr 26 06:28:51 192.168.122.209 [51881.766083] End test: t_stress.test_stress.BaseWrkStress.test_concurrent_connections Apr 26 06:28:51 192.168.122.209 [51881.782259] Start test: t_stress.test_stress.H2CurlStress.test_concurrent_requests Apr 26 06:28:52 192.168.122.209 [51883.401161] [tdb] Start Tempesta DB Apr 26 06:28:53 192.168.122.209 [51883.579421] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:28:54 192.168.122.209 [51884.899261] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [51884.899261] Maybe that's fine, but it's worth checking the [51884.899261] config - if there is no relations between the [51884.899261] names, then host name confusion attack is possible. Apr 26 06:28:54 192.168.122.209 [51885.021968] [tempesta fw] Configuration processing is completed. Apr 26 06:28:54 192.168.122.209 [51885.097789] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:28:54 192.168.122.209 [51885.148538] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:28:54 192.168.122.209 [51885.212322] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:28:54 192.168.122.209 [51885.289914] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:28:54 192.168.122.209 [51885.337859] [tempesta fw] Tempesta FW is ready Apr 26 06:28:55 192.168.122.209 [51886.410453] [tdb] Close table 'client0.tdb' Apr 26 06:28:56 192.168.122.209 [51886.608424] [tdb] Close table 'sessions0.tdb' Apr 26 06:28:56 192.168.122.209 [51886.847620] [tdb] Close table 'filter0.tdb' Apr 26 06:28:56 192.168.122.209 [51886.848059] [tempesta fw] modules are stopped Apr 26 06:28:56 192.168.122.209 [51887.034569] [tempesta fw] exiting... Apr 26 06:28:56 192.168.122.209 [51887.158862] [tdb] Shutdown Tempesta DB Apr 26 06:28:56 192.168.122.209 [51887.422233] End test: t_stress.test_stress.H2CurlStress.test_concurrent_requests Apr 26 06:28:56 192.168.122.209 [51887.433408] Start test: t_stress.test_stress.H2CurlStress.test_pipelined_requests Apr 26 06:28:58 192.168.122.209 [51889.138708] [tdb] Start Tempesta DB Apr 26 06:28:58 192.168.122.209 [51889.302233] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:28:59 192.168.122.209 [51889.842991] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [51889.842991] Maybe that's fine, but it's worth checking the [51889.842991] config - if there is no relations between the [51889.842991] names, then host name confusion attack is possible. Apr 26 06:28:59 192.168.122.209 [51889.962135] [tempesta fw] Configuration processing is completed. Apr 26 06:28:59 192.168.122.209 [51890.011191] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:28:59 192.168.122.209 [51890.044052] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:28:59 192.168.122.209 [51890.082458] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:28:59 192.168.122.209 [51890.157842] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:28:59 192.168.122.209 [51890.197926] [tempesta fw] Tempesta FW is ready Apr 26 06:29:00 192.168.122.209 [51891.356532] [tdb] Close table 'client0.tdb' Apr 26 06:29:01 192.168.122.209 [51891.641061] [tdb] Close table 'sessions0.tdb' Apr 26 06:29:01 192.168.122.209 [51891.881222] [tdb] Close table 'filter0.tdb' Apr 26 06:29:01 192.168.122.209 [51891.881649] [tempesta fw] modules are stopped Apr 26 06:29:01 192.168.122.209 [51892.114182] [tempesta fw] exiting... Apr 26 06:29:01 192.168.122.209 [51892.225111] [tdb] Shutdown Tempesta DB Apr 26 06:29:02 192.168.122.209 [51892.513712] End test: t_stress.test_stress.H2CurlStress.test_pipelined_requests Apr 26 06:29:02 192.168.122.209 [51892.534583] Start test: t_stress.test_stress.H2CurlStress.test_range_requests Apr 26 06:29:03 192.168.122.209 [51894.086534] [tdb] Start Tempesta DB Apr 26 06:29:03 192.168.122.209 [51894.240895] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:29:04 192.168.122.209 [51894.799639] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [51894.799639] Maybe that's fine, but it's worth checking the [51894.799639] config - if there is no relations between the [51894.799639] names, then host name confusion attack is possible. Apr 26 06:29:04 192.168.122.209 [51894.910037] [tempesta fw] Configuration processing is completed. Apr 26 06:29:04 192.168.122.209 [51894.968385] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:29:04 192.168.122.209 [51895.000818] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:29:04 192.168.122.209 [51895.033792] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:29:04 192.168.122.209 [51895.106030] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:29:04 192.168.122.209 [51895.149983] [tempesta fw] Tempesta FW is ready Apr 26 06:29:15 192.168.122.209 [51906.360498] [tdb] Close table 'client0.tdb' Apr 26 06:29:16 192.168.122.209 [51906.550990] [tdb] Close table 'sessions0.tdb' Apr 26 06:29:16 192.168.122.209 [51906.779052] [tdb] Close table 'filter0.tdb' Apr 26 06:29:16 192.168.122.209 [51906.779473] [tempesta fw] modules are stopped Apr 26 06:29:16 192.168.122.209 [51907.002502] [tempesta fw] exiting... Apr 26 06:29:16 192.168.122.209 [51907.160391] [tdb] Shutdown Tempesta DB Apr 26 06:29:16 192.168.122.209 [51907.420295] End test: t_stress.test_stress.H2CurlStress.test_range_requests Apr 26 06:29:16 192.168.122.209 [51907.436754] Start test: t_stress.test_stress.H2CurlStress.test_sequential_requests Apr 26 06:29:18 192.168.122.209 [51908.959419] [tdb] Start Tempesta DB Apr 26 06:29:18 192.168.122.209 [51909.107776] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:29:19 192.168.122.209 [51909.651635] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [51909.651635] Maybe that's fine, but it's worth checking the [51909.651635] config - if there is no relations between the [51909.651635] names, then host name confusion attack is possible. Apr 26 06:29:19 192.168.122.209 [51909.778252] [tempesta fw] Configuration processing is completed. Apr 26 06:29:19 192.168.122.209 [51909.828144] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:29:19 192.168.122.209 [51909.856239] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:29:19 192.168.122.209 [51909.883987] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:29:19 192.168.122.209 [51909.970209] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:29:19 192.168.122.209 [51910.018167] [tempesta fw] Tempesta FW is ready Apr 26 06:29:20 192.168.122.209 [51911.170488] [tdb] Close table 'client0.tdb' Apr 26 06:29:20 192.168.122.209 [51911.359391] [tdb] Close table 'sessions0.tdb' Apr 26 06:29:21 192.168.122.209 [51911.603642] [tdb] Close table 'filter0.tdb' Apr 26 06:29:21 192.168.122.209 [51911.604128] [tempesta fw] modules are stopped Apr 26 06:29:21 192.168.122.209 [51911.790229] [tempesta fw] exiting... Apr 26 06:29:21 192.168.122.209 [51911.898073] [tdb] Shutdown Tempesta DB Apr 26 06:29:21 192.168.122.209 [51912.184891] End test: t_stress.test_stress.H2CurlStress.test_sequential_requests Apr 26 06:29:21 192.168.122.209 [51912.199968] Start test: t_stress.test_stress.H2LoadStress.test_no_cache Apr 26 06:29:23 192.168.122.209 [51913.799024] [tdb] Start Tempesta DB Apr 26 06:29:23 192.168.122.209 [51913.944244] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:29:24 192.168.122.209 [51914.511727] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [51914.511727] Maybe that's fine, but it's worth checking the [51914.511727] config - if there is no relations between the [51914.511727] names, then host name confusion attack is possible. Apr 26 06:29:24 192.168.122.209 [51914.642294] [tempesta fw] Configuration processing is completed. Apr 26 06:29:24 192.168.122.209 [51914.689765] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:29:24 192.168.122.209 [51914.720074] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:29:24 192.168.122.209 [51914.748205] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:29:24 192.168.122.209 [51914.826242] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:29:24 192.168.122.209 [51914.874169] [tempesta fw] Tempesta FW is ready Apr 26 06:29:26 192.168.122.209 [51917.387090] [tempesta fw] Warning: request evicted: the number of retries exceeded, status 504: 127.0.0.1 Apr 26 06:29:26 192.168.122.209 [51917.387989] [tempesta fw] Warning: request evicted: the number of retries exceeded, status 504: 127.0.0.1 Apr 26 06:29:26 192.168.122.209 [51917.388851] [tempesta fw] Warning: request evicted: the number of retries exceeded, status 504: 127.0.0.1 Apr 26 06:29:26 192.168.122.209 [51917.389700] [tempesta fw] Warning: request evicted: the number of retries exceeded, status 504: 127.0.0.1 Apr 26 06:29:26 192.168.122.209 [51917.390563] [tempesta fw] Warning: request evicted: the number of retries exceeded, status 504: 127.0.0.1 Apr 26 06:29:26 192.168.122.209 [51917.391410] [tempesta fw] Warning: request evicted: the number of retries exceeded, status 504: 127.0.0.1 Apr 26 06:29:28 192.168.122.209 [51918.973017] net_ratelimit: 198 callbacks suppressed Apr 26 06:29:28 192.168.122.209 [51918.973021] [tempesta fw] Warning: request evicted: the number of retries exceeded, status 504: 127.0.0.1 Apr 26 06:29:28 192.168.122.209 [51918.974374] [tempesta fw] Warning: request evicted: the number of retries exceeded, status 504: 127.0.0.1 Apr 26 06:29:28 192.168.122.209 [51918.975280] [tempesta fw] Warning: request evicted: the number of retries exceeded, status 504: 127.0.0.1 Apr 26 06:29:28 192.168.122.209 [51918.976137] [tempesta fw] Warning: request evicted: the number of retries exceeded, status 504: 127.0.0.1 Apr 26 06:29:28 192.168.122.209 [51918.977023] [tempesta fw] Warning: request evicted: the number of retries exceeded, status 504: 127.0.0.1 Apr 26 06:29:28 192.168.122.209 [51918.977882] [tempesta fw] Warning: request evicted: the number of retries exceeded, status 504: 127.0.0.1 Apr 26 06:29:28 192.168.122.209 [51918.978750] [tempesta fw] Warning: request evicted: the number of retries exceeded, status 504: 127.0.0.1 Apr 26 06:29:28 192.168.122.209 [51918.979653] [tempesta fw] Warning: request evicted: the number of retries exceeded, status 504: 127.0.0.1 Apr 26 06:29:28 192.168.122.209 [51918.980530] [tempesta fw] Warning: request evicted: the number of retries exceeded, status 504: 127.0.0.1 Apr 26 06:29:28 192.168.122.209 [51918.981386] [tempesta fw] Warning: request evicted: the number of retries exceeded, status 504: 127.0.0.1 Apr 26 06:29:35 192.168.122.209 [51925.745610] [tdb] Close table 'client0.tdb' Apr 26 06:29:35 192.168.122.209 [51925.953741] [tdb] Close table 'sessions0.tdb' Apr 26 06:29:35 192.168.122.209 [51926.204080] [tdb] Close table 'filter0.tdb' Apr 26 06:29:35 192.168.122.209 [51926.204504] [tempesta fw] modules are stopped Apr 26 06:29:35 192.168.122.209 [51926.397139] [tempesta fw] exiting... Apr 26 06:29:36 192.168.122.209 [51926.520284] [tdb] Shutdown Tempesta DB Apr 26 06:29:36 192.168.122.209 [51926.790235] End test: t_stress.test_stress.H2LoadStress.test_no_cache Apr 26 06:29:36 192.168.122.209 [51926.806998] Start test: t_stress.test_stress.H2LoadStress.test_with_cache Apr 26 06:29:38 192.168.122.209 [51928.500283] [tdb] Start Tempesta DB Apr 26 06:29:38 192.168.122.209 [51928.649512] net_ratelimit: 137 callbacks suppressed Apr 26 06:29:38 192.168.122.209 [51928.649514] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:29:38 192.168.122.209 [51929.239770] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [51929.239770] Maybe that's fine, but it's worth checking the [51929.239770] config - if there is no relations between the [51929.239770] names, then host name confusion attack is possible. Apr 26 06:29:38 192.168.122.209 [51929.394826] [tempesta fw] Configuration processing is completed. Apr 26 06:29:38 192.168.122.209 [51929.454882] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:29:39 192.168.122.209 [51930.455484] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:29:40 192.168.122.209 [51930.547974] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:29:40 192.168.122.209 [51930.614199] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:29:40 192.168.122.209 [51930.694503] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:29:40 192.168.122.209 [51930.742450] [tempesta fw] Tempesta FW is ready Apr 26 06:29:51 192.168.122.209 [51941.673871] [tdb] Close table 'client0.tdb' Apr 26 06:29:51 192.168.122.209 [51941.893014] [tdb] Close table 'sessions0.tdb' Apr 26 06:29:55 192.168.122.209 [51945.713516] [tdb] Close table 'cache0.tdb' Apr 26 06:29:55 192.168.122.209 [51946.372479] [tdb] Close table 'filter0.tdb' Apr 26 06:29:55 192.168.122.209 [51946.372968] [tempesta fw] modules are stopped Apr 26 06:29:57 192.168.122.209 [51947.815406] [tempesta fw] exiting... Apr 26 06:29:58 192.168.122.209 [51948.639476] [tdb] Shutdown Tempesta DB Apr 26 06:29:58 192.168.122.209 [51948.955944] End test: t_stress.test_stress.H2LoadStress.test_with_cache Apr 26 06:29:58 192.168.122.209 [51948.979108] Start test: t_stress.test_stress.RequestStress.test_h2_post_request Apr 26 06:30:00 192.168.122.209 [51951.007771] [tdb] Start Tempesta DB Apr 26 06:30:00 192.168.122.209 [51951.199469] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:30:02 192.168.122.209 [51952.863736] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [51952.863736] Maybe that's fine, but it's worth checking the [51952.863736] config - if there is no relations between the [51952.863736] names, then host name confusion attack is possible. Apr 26 06:30:02 192.168.122.209 [51953.026768] [tempesta fw] Configuration processing is completed. Apr 26 06:30:02 192.168.122.209 [51953.081699] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:30:02 192.168.122.209 [51953.110139] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:30:02 192.168.122.209 [51953.143373] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:30:02 192.168.122.209 [51953.218770] [tempesta fw] Open listen socket on: 0.0.0.0:4433 Apr 26 06:30:02 192.168.122.209 [51953.220551] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:30:02 192.168.122.209 [51953.222176] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:30:02 192.168.122.209 [51953.262709] [tempesta fw] Tempesta FW is ready Apr 26 06:30:04 192.168.122.209 [51954.886053] [tempesta fw] Warning: request dropped: non-idempotent requests aren't re-forwarded or re-scheduled, status 504: 127.0.0.1 Apr 26 06:30:04 192.168.122.209 [51954.899813] [tempesta fw] Warning: request dropped: non-idempotent requests aren't re-forwarded or re-scheduled, status 504: 127.0.0.1 Apr 26 06:30:06 192.168.122.209 [51957.290887] [tempesta fw] Warning: request dropped: non-idempotent requests aren't re-forwarded or re-scheduled, status 504: 127.0.0.1 Apr 26 06:30:09 192.168.122.209 [51959.607301] [tempesta fw] Warning: request dropped: non-idempotent requests aren't re-forwarded or re-scheduled, status 504: 127.0.0.1 Apr 26 06:30:11 192.168.122.209 [51962.047149] [tempesta fw] Warning: request dropped: non-idempotent requests aren't re-forwarded or re-scheduled, status 504: 127.0.0.1 Apr 26 06:30:13 192.168.122.209 [51964.041588] [tdb] Close table 'client0.tdb' Apr 26 06:30:13 192.168.122.209 [51964.250955] [tdb] Close table 'sessions0.tdb' Apr 26 06:30:14 192.168.122.209 [51964.507712] [tdb] Close table 'filter0.tdb' Apr 26 06:30:14 192.168.122.209 [51964.508166] [tempesta fw] modules are stopped Apr 26 06:30:14 192.168.122.209 [51964.684946] [tempesta fw] exiting... Apr 26 06:30:14 192.168.122.209 [51964.817348] [tdb] Shutdown Tempesta DB Apr 26 06:30:14 192.168.122.209 [51965.100799] End test: t_stress.test_stress.RequestStress.test_h2_post_request Apr 26 06:30:14 192.168.122.209 [51965.115521] Start test: t_stress.test_stress.RequestStress.test_h2_put_request Apr 26 06:30:16 192.168.122.209 [51966.791110] [tdb] Start Tempesta DB Apr 26 06:30:16 192.168.122.209 [51966.969873] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:30:17 192.168.122.209 [51967.840274] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [51967.840274] Maybe that's fine, but it's worth checking the [51967.840274] config - if there is no relations between the [51967.840274] names, then host name confusion attack is possible. Apr 26 06:30:17 192.168.122.209 [51967.967000] [tempesta fw] Configuration processing is completed. Apr 26 06:30:17 192.168.122.209 [51968.024888] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:30:17 192.168.122.209 [51968.070978] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:30:17 192.168.122.209 [51968.107645] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:30:17 192.168.122.209 [51968.186982] [tempesta fw] Open listen socket on: 0.0.0.0:4433 Apr 26 06:30:17 192.168.122.209 [51968.188791] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:30:17 192.168.122.209 [51968.190416] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:30:17 192.168.122.209 [51968.226922] [tempesta fw] Tempesta FW is ready Apr 26 06:30:18 192.168.122.209 [51969.375484] [tempesta fw] Warning: request dropped: non-idempotent requests aren't re-forwarded or re-scheduled, status 504: 127.0.0.1 Apr 26 06:30:18 192.168.122.209 [51969.379072] [tempesta fw] Warning: request dropped: non-idempotent requests aren't re-forwarded or re-scheduled, status 504: 127.0.0.1 Apr 26 06:30:24 192.168.122.209 [51975.083082] [tempesta fw] Warning: request dropped: non-idempotent requests aren't re-forwarded or re-scheduled, status 504: 127.0.0.1 Apr 26 06:30:24 192.168.122.209 [51975.279241] [tempesta fw] Warning: request dropped: non-idempotent requests aren't re-forwarded or re-scheduled, status 504: 127.0.0.1 Apr 26 06:30:25 192.168.122.209 [51975.999886] [tempesta fw] Warning: request dropped: non-idempotent requests aren't re-forwarded or re-scheduled, status 504: 127.0.0.1 Apr 26 06:30:25 192.168.122.209 [51976.002644] [tempesta fw] Warning: request dropped: non-idempotent requests aren't re-forwarded or re-scheduled, status 504: 127.0.0.1 Apr 26 06:30:25 192.168.122.209 [51976.171699] [tempesta fw] Warning: request dropped: non-idempotent requests aren't re-forwarded or re-scheduled, status 504: 127.0.0.1 Apr 26 06:30:25 192.168.122.209 [51976.191391] [tempesta fw] Warning: request dropped: non-idempotent requests aren't re-forwarded or re-scheduled, status 504: 127.0.0.1 Apr 26 06:30:25 192.168.122.209 [51976.196047] [tempesta fw] Warning: request dropped: non-idempotent requests aren't re-forwarded or re-scheduled, status 504: 127.0.0.1 Apr 26 06:30:25 192.168.122.209 [51976.199165] [tempesta fw] Warning: request dropped: non-idempotent requests aren't re-forwarded or re-scheduled, status 504: 127.0.0.1 Apr 26 06:30:26 192.168.122.209 [51976.583445] [tempesta fw] Warning: request dropped: non-idempotent requests aren't re-forwarded or re-scheduled, status 504: 127.0.0.1 Apr 26 06:30:28 192.168.122.209 [51978.492106] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 06:30:28 192.168.122.209 [51979.077507] [tdb] Close table 'client0.tdb' Apr 26 06:30:28 192.168.122.209 [51979.274703] [tdb] Close table 'sessions0.tdb' Apr 26 06:30:29 192.168.122.209 [51979.511493] [tdb] Close table 'filter0.tdb' Apr 26 06:30:29 192.168.122.209 [51979.511946] [tempesta fw] modules are stopped Apr 26 06:30:29 192.168.122.209 [51979.680876] [tempesta fw] exiting... Apr 26 06:30:29 192.168.122.209 [51979.798788] [tdb] Shutdown Tempesta DB Apr 26 06:30:29 192.168.122.209 [51980.052739] End test: t_stress.test_stress.RequestStress.test_h2_put_request Apr 26 06:30:29 192.168.122.209 [51980.068248] Start test: t_stress.test_stress.RequestStress.test_http_post_request Apr 26 06:30:31 192.168.122.209 [51981.793293] [tdb] Start Tempesta DB Apr 26 06:30:31 192.168.122.209 [51981.989209] net_ratelimit: 1 callbacks suppressed Apr 26 06:30:31 192.168.122.209 [51981.989211] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:30:32 192.168.122.209 [51982.784413] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [51982.784413] Maybe that's fine, but it's worth checking the [51982.784413] config - if there is no relations between the [51982.784413] names, then host name confusion attack is possible. Apr 26 06:30:32 192.168.122.209 [51982.915065] [tempesta fw] Configuration processing is completed. Apr 26 06:30:32 192.168.122.209 [51982.971801] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:30:32 192.168.122.209 [51983.006799] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:30:32 192.168.122.209 [51983.043859] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:30:32 192.168.122.209 [51983.123119] [tempesta fw] Open listen socket on: 0.0.0.0:4433 Apr 26 06:30:32 192.168.122.209 [51983.124983] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:30:32 192.168.122.209 [51983.126607] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:30:32 192.168.122.209 [51983.175075] [tempesta fw] Tempesta FW is ready Apr 26 06:30:33 192.168.122.209 [51983.768094] [tempesta fw] Warning: request dropped: non-idempotent requests aren't re-forwarded or re-scheduled, status 504: 127.0.0.1 Apr 26 06:30:33 192.168.122.209 [51983.768134] [tempesta fw] Warning: request dropped: non-idempotent requests aren't re-forwarded or re-scheduled, status 504: 127.0.0.1 Apr 26 06:30:33 192.168.122.209 [51983.769260] [tempesta fw] Warning: request dropped: non-idempotent requests aren't re-forwarded or re-scheduled, status 504: 127.0.0.1 Apr 26 06:30:33 192.168.122.209 [51983.770351] [tempesta fw] Warning: request dropped: non-idempotent requests aren't re-forwarded or re-scheduled, status 504: 127.0.0.1 Apr 26 06:30:43 192.168.122.209 [51994.005364] [tdb] Close table 'client0.tdb' Apr 26 06:30:43 192.168.122.209 [51994.213550] [tdb] Close table 'sessions0.tdb' Apr 26 06:30:44 192.168.122.209 [51994.475593] [tdb] Close table 'filter0.tdb' Apr 26 06:30:44 192.168.122.209 [51994.476041] [tempesta fw] modules are stopped Apr 26 06:30:44 192.168.122.209 [51994.676968] [tempesta fw] exiting... Apr 26 06:30:44 192.168.122.209 [51994.782605] [tdb] Shutdown Tempesta DB Apr 26 06:30:44 192.168.122.209 [51995.000800] End test: t_stress.test_stress.RequestStress.test_http_post_request Apr 26 06:30:44 192.168.122.209 [51995.009248] Start test: t_stress.test_stress.RequestStress.test_http_put_request Apr 26 06:30:46 192.168.122.209 [51996.675902] [tdb] Start Tempesta DB Apr 26 06:30:46 192.168.122.209 [51996.849714] net_ratelimit: 1 callbacks suppressed Apr 26 06:30:46 192.168.122.209 [51996.849717] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:30:47 192.168.122.209 [51997.708599] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [51997.708599] Maybe that's fine, but it's worth checking the [51997.708599] config - if there is no relations between the [51997.708599] names, then host name confusion attack is possible. Apr 26 06:30:47 192.168.122.209 [51997.831311] [tempesta fw] Configuration processing is completed. Apr 26 06:30:47 192.168.122.209 [51997.882515] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:30:47 192.168.122.209 [51997.912478] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:30:47 192.168.122.209 [51997.941860] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:30:47 192.168.122.209 [51998.015316] [tempesta fw] Open listen socket on: 0.0.0.0:4433 Apr 26 06:30:47 192.168.122.209 [51998.017055] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:30:47 192.168.122.209 [51998.018701] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:30:47 192.168.122.209 [51998.055265] [tempesta fw] Tempesta FW is ready Apr 26 06:30:48 192.168.122.209 [51998.640800] [tempesta fw] Warning: request dropped: non-idempotent requests aren't re-forwarded or re-scheduled, status 504: 127.0.0.1 Apr 26 06:30:48 192.168.122.209 [51998.640805] [tempesta fw] Warning: request dropped: non-idempotent requests aren't re-forwarded or re-scheduled, status 504: 127.0.0.1 Apr 26 06:30:48 192.168.122.209 [51998.647541] [tempesta fw] Warning: request dropped: non-idempotent requests aren't re-forwarded or re-scheduled, status 504: 127.0.0.1 Apr 26 06:30:48 192.168.122.209 [51998.996373] [tempesta fw] Warning: request dropped: non-idempotent requests aren't re-forwarded or re-scheduled, status 504: 127.0.0.1 Apr 26 06:30:58 192.168.122.209 [52008.951919] [tdb] Close table 'client0.tdb' Apr 26 06:30:58 192.168.122.209 [52009.130945] [tdb] Close table 'sessions0.tdb' Apr 26 06:30:58 192.168.122.209 [52009.395018] [tdb] Close table 'filter0.tdb' Apr 26 06:30:58 192.168.122.209 [52009.395475] [tempesta fw] modules are stopped Apr 26 06:30:59 192.168.122.209 [52009.613743] [tempesta fw] exiting... Apr 26 06:30:59 192.168.122.209 [52009.715683] [tdb] Shutdown Tempesta DB Apr 26 06:30:59 192.168.122.209 [52010.001388] End test: t_stress.test_stress.RequestStress.test_http_put_request Apr 26 06:30:59 192.168.122.209 [52010.010981] Start test: t_stress.test_stress.RequestStress.test_https_post_request Apr 26 06:31:01 192.168.122.209 [52011.661677] [tdb] Start Tempesta DB Apr 26 06:31:01 192.168.122.209 [52011.822793] net_ratelimit: 3 callbacks suppressed Apr 26 06:31:01 192.168.122.209 [52011.822795] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:31:02 192.168.122.209 [52012.620739] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52012.620739] Maybe that's fine, but it's worth checking the [52012.620739] config - if there is no relations between the [52012.620739] names, then host name confusion attack is possible. Apr 26 06:31:02 192.168.122.209 [52012.739519] [tempesta fw] Configuration processing is completed. Apr 26 06:31:02 192.168.122.209 [52012.791143] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:31:02 192.168.122.209 [52012.822945] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:31:02 192.168.122.209 [52012.852350] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:31:02 192.168.122.209 [52012.927517] [tempesta fw] Open listen socket on: 0.0.0.0:4433 Apr 26 06:31:02 192.168.122.209 [52012.929227] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:31:02 192.168.122.209 [52012.930895] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:31:02 192.168.122.209 [52012.975456] [tempesta fw] Tempesta FW is ready Apr 26 06:31:13 192.168.122.209 [52023.797357] [tdb] Close table 'client0.tdb' Apr 26 06:31:13 192.168.122.209 [52023.984633] [tdb] Close table 'sessions0.tdb' Apr 26 06:31:13 192.168.122.209 [52024.205982] [tdb] Close table 'filter0.tdb' Apr 26 06:31:13 192.168.122.209 [52024.206901] [tempesta fw] modules are stopped Apr 26 06:31:13 192.168.122.209 [52024.396899] [tempesta fw] exiting... Apr 26 06:31:14 192.168.122.209 [52024.507269] [tdb] Shutdown Tempesta DB Apr 26 06:31:14 192.168.122.209 [52024.754770] End test: t_stress.test_stress.RequestStress.test_https_post_request Apr 26 06:31:14 192.168.122.209 [52024.768506] Start test: t_stress.test_stress.RequestStress.test_https_put_request Apr 26 06:31:16 192.168.122.209 [52026.503138] [tdb] Start Tempesta DB Apr 26 06:31:16 192.168.122.209 [52026.654955] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:31:17 192.168.122.209 [52027.516915] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52027.516915] Maybe that's fine, but it's worth checking the [52027.516915] config - if there is no relations between the [52027.516915] names, then host name confusion attack is possible. Apr 26 06:31:17 192.168.122.209 [52027.631675] [tempesta fw] Configuration processing is completed. Apr 26 06:31:17 192.168.122.209 [52027.685189] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:31:17 192.168.122.209 [52027.715751] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:31:17 192.168.122.209 [52027.745164] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:31:17 192.168.122.209 [52027.823688] [tempesta fw] Open listen socket on: 0.0.0.0:4433 Apr 26 06:31:17 192.168.122.209 [52027.825522] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:31:17 192.168.122.209 [52027.827212] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:31:17 192.168.122.209 [52027.863636] [tempesta fw] Tempesta FW is ready Apr 26 06:31:28 192.168.122.209 [52038.692084] [tdb] Close table 'client0.tdb' Apr 26 06:31:28 192.168.122.209 [52038.918180] [tdb] Close table 'sessions0.tdb' Apr 26 06:31:28 192.168.122.209 [52039.144495] [tdb] Close table 'filter0.tdb' Apr 26 06:31:28 192.168.122.209 [52039.144957] [tempesta fw] modules are stopped Apr 26 06:31:28 192.168.122.209 [52039.374324] [tempesta fw] exiting... Apr 26 06:31:29 192.168.122.209 [52039.500088] [tdb] Shutdown Tempesta DB Apr 26 06:31:29 192.168.122.209 [52039.764886] End test: t_stress.test_stress.RequestStress.test_https_put_request Apr 26 06:31:29 192.168.122.209 [52039.786744] Start test: t_stress.test_stress.TestTdbStressH2.test_cache_eviction_tdb Apr 26 06:31:30 192.168.122.209 [52041.189075] [tdb] Start Tempesta DB Apr 26 06:31:30 192.168.122.209 [52041.341048] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:31:31 192.168.122.209 [52042.037242] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52042.037242] Maybe that's fine, but it's worth checking the [52042.037242] config - if there is no relations between the [52042.037242] names, then host name confusion attack is possible. Apr 26 06:31:31 192.168.122.209 [52042.212070] [tempesta fw] Configuration processing is completed. Apr 26 06:31:31 192.168.122.209 [52042.280374] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:31:32 192.168.122.209 [52042.909467] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:31:32 192.168.122.209 [52042.946710] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:31:32 192.168.122.209 [52042.974905] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:31:32 192.168.122.209 [52043.047868] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:31:32 192.168.122.209 [52043.049613] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:31:32 192.168.122.209 [52043.087817] [tempesta fw] Tempesta FW is ready Apr 26 06:31:34 192.168.122.209 [52044.924274] [tdb] ERROR: out of free space Apr 26 06:31:34 192.168.122.209 [52044.925520] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:31:34 192.168.122.209 [52044.927307] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:31:34 192.168.122.209 [52044.930213] [tdb] ERROR: out of free space Apr 26 06:31:34 192.168.122.209 [52044.930849] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:31:34 192.168.122.209 [52044.931577] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:31:34 192.168.122.209 [52044.943283] [tdb] ERROR: out of free space Apr 26 06:31:34 192.168.122.209 [52044.943700] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab2dcc6f945 Apr 26 06:31:34 192.168.122.209 [52045.109050] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.119120] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.123917] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.124124] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.125370] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.126055] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.127261] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.128050] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.128279] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.128950] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.129094] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.129870] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.132948] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.133718] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.134681] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.135645] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.136490] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.137428] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.138230] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.139009] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.141476] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.142275] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.143034] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.143807] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.144611] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.145384] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.146170] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.146938] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.147713] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.148489] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.151004] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.151813] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.152598] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.153360] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.154136] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.154888] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.155655] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.156435] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.157225] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.157996] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.161669] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.162440] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.163198] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.163995] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.164872] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.165652] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.166403] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.167171] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.167965] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.168742] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.171734] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.172542] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.173315] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.174087] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.174853] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.175617] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.176433] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.177199] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.177972] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.178746] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.182975] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.183855] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.184641] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.185389] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.186182] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.186954] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.187748] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.188507] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.189286] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.190057] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.194640] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.195448] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.196276] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.197033] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.197787] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.198557] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.199330] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.200110] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.200906] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.201697] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.205886] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.206713] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.207494] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.208294] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.209092] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.209867] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.210646] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.211560] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.212417] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.213235] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.217026] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.217818] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.218597] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.219359] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.220162] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.220936] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.221726] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.222506] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.223278] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.224082] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.232845] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.233682] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.234461] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.235271] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.236132] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.236945] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.237757] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.238584] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.239393] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.240216] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.243819] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.244689] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.245517] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.246291] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.247074] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.247877] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.248657] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.249414] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.250195] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.250956] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.254687] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.255465] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.256261] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.257048] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.257833] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.258599] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.259366] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.260152] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.260989] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.261764] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.265496] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.266310] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.267091] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.267905] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.268689] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.269474] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.270257] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.271031] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.271828] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.272613] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.276592] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.277381] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.278183] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.278953] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.279750] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.280537] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.281320] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.282114] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.282891] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.283657] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.286342] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.287308] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.288354] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.289305] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.290254] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.291233] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.292280] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.293241] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.294201] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.295141] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.296996] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.297948] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.298893] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.299890] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.300854] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.301796] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.302774] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.303735] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.304841] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.305780] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.307478] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.308526] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.309462] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.310398] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.311323] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.312300] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.313233] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.314159] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.315084] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.316227] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.317867] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.318808] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.319760] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.320735] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.321682] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.322612] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.323528] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.324627] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.325551] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.326492] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.328195] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.329144] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.330118] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.331069] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.332059] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.333000] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.333933] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.334872] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.335836] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.336852] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.341653] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.342596] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.343543] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.344680] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.345613] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.346542] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.347512] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.348649] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.349596] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.350537] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.352169] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.353120] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.354055] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.354987] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.355950] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.356892] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.358030] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.358994] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.360130] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.361075] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.362649] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.363602] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.364567] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.365500] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.366424] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.367359] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.368355] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.369285] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.370206] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.371127] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.372509] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.373455] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.374398] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.375365] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.376674] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.377616] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.378544] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.379472] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.380444] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.381392] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.382745] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.383777] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.384730] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.385708] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.386634] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.387555] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.388599] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.389532] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.390460] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.391390] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.392849] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.393876] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.394816] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.395719] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.396612] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:34 192.168.122.209 [52045.397572] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.071809] [tdb] ERROR: out of free space Apr 26 06:31:36 192.168.122.209 [52047.072235] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:31:36 192.168.122.209 [52047.072832] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:31:36 192.168.122.209 [52047.080446] [tdb] ERROR: out of free space Apr 26 06:31:36 192.168.122.209 [52047.081671] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab2f787651d Apr 26 06:31:36 192.168.122.209 [52047.086688] [tdb] ERROR: out of free space Apr 26 06:31:36 192.168.122.209 [52047.087587] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab205ece61e Apr 26 06:31:36 192.168.122.209 [52047.094206] [tdb] ERROR: out of free space Apr 26 06:31:36 192.168.122.209 [52047.094703] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab2e4d796e9 Apr 26 06:31:36 192.168.122.209 [52047.249245] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.250323] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.258351] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.264027] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.269788] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.273554] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.277128] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.279456] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.280472] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.282108] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.282233] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.283754] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.285372] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.287013] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.287806] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.288580] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.289347] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.290084] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.290853] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.293193] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.293983] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.294758] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.295511] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.296303] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.297122] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.297941] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.298725] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.299495] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.300288] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.302643] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.303402] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.304197] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.304958] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.305717] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.306466] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.307224] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.308000] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.308789] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.309543] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.312565] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.313496] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.314265] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.315020] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.315812] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.316569] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.317459] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.318245] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.319023] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.319830] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.322911] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.323680] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.324462] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.325218] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.325977] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.326743] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.327546] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.328337] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.329171] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.329936] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.334158] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.334965] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.335783] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.336554] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.337334] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.338118] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.338900] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.339642] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.340443] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.341200] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.345254] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.346042] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.346815] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.347569] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.348385] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.349167] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.349947] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.350660] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.351415] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.352214] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.356549] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.357355] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.358141] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.358898] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.359677] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.360470] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.361234] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.361994] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.362785] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.363546] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.367369] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.368173] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.368940] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.369713] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.370507] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.371273] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.372071] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.372834] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.373596] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.374365] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.383770] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.384570] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.385343] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.386109] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.386881] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.387645] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.388449] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.389237] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.390048] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.390853] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.393893] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.394696] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.395468] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.396261] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.397045] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.397830] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.398593] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.399356] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.400164] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.401083] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.405241] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.406038] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.406817] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.407576] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.408383] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.409189] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.409975] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.410747] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.411477] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.412284] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.416636] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.417401] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.418164] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.418940] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.419726] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.420520] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.421304] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.422074] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.422852] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.423637] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.428118] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.428927] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.429716] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.430474] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.431252] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.432056] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.432829] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.433588] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.434380] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.435164] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.438970] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.439765] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.440538] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.441300] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.442102] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.442908] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.443691] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.444481] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.445254] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.446016] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.450055] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.450854] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.451639] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.452426] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.453205] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.453976] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.454757] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.455509] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.456300] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:36 192.168.122.209 [52047.457061] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.460860] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.461661] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.462488] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.463262] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.464069] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.464854] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.465632] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.466389] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.467164] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.467960] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.471244] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.472052] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.472838] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.473593] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.474362] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.475122] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.475941] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.476721] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.477497] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.478248] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.481673] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.482465] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.483233] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.484017] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.484905] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.485677] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.486433] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.487184] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.487990] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.488792] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.491266] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.492056] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.492828] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.493585] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.494355] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.495112] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.495919] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.496748] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.497517] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.498279] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.501520] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.502309] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.503073] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.503864] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.504647] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.505380] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.506128] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.506885] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.507657] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.508439] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.511159] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.512180] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.513123] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.514074] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.515005] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.516049] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.516986] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.517923] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.518844] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.519792] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.521182] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.522142] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.523089] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.524085] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.524997] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.525905] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.526810] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.527738] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.528865] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.529783] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.531109] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.532087] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.533034] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.533985] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.534905] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.535857] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.536813] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.537731] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.538664] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.539582] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.540987] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.541921] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.542853] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.543746] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.544637] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.545497] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:37 192.168.122.209 [52047.546423] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52048.808698] [tdb] ERROR: out of free space Apr 26 06:31:38 192.168.122.209 [52048.809771] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:31:38 192.168.122.209 [52048.811054] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:31:38 192.168.122.209 [52048.813543] [tdb] ERROR: out of free space Apr 26 06:31:38 192.168.122.209 [52048.814226] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:31:38 192.168.122.209 [52048.815229] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:31:38 192.168.122.209 [52048.817025] [tdb] ERROR: out of free space Apr 26 06:31:38 192.168.122.209 [52048.817268] [tdb] ERROR: out of free space Apr 26 06:31:38 192.168.122.209 [52048.817694] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:31:38 192.168.122.209 [52048.817700] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:31:38 192.168.122.209 [52048.818118] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab2ace4261d Apr 26 06:31:38 192.168.122.209 [52048.962052] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52048.963265] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52048.975576] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52048.976558] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52048.978176] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52048.980030] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52048.980639] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52048.980932] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52048.981222] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52048.981661] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52048.982839] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52048.983397] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52048.984328] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52048.984933] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52048.986359] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52048.986423] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52048.990851] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52048.991788] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52048.992734] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52048.993661] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52048.994879] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52048.996460] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52048.997536] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52048.998440] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52048.999365] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.000595] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.001519] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.002427] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.003312] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.004264] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.005368] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.006901] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.007873] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.008826] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.009730] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.010628] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.011524] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.012699] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.013666] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.014613] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.015905] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.017593] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.018519] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.019438] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.020472] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.021424] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.022339] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.023274] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.024252] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.025181] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.026333] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.028260] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.029197] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.030180] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.031131] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.032106] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.033174] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.034181] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.035125] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.036123] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.037507] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.039230] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.040378] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.041268] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.042190] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.043101] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.044104] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.045011] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.045909] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.046827] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.048392] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.049311] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.050851] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.051757] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.052720] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.053629] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.054533] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.055440] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.056443] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.057394] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.058633] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.059573] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.061337] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.062363] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.063278] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.064235] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.065179] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.066089] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.067014] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.068020] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.069307] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.070227] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.071818] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.072971] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.073856] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.074779] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.075691] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.076645] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.077579] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.078495] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.079814] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.080739] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.081717] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.083184] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.084207] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.085130] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.086047] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.086960] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.087928] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.088861] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.090226] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.091114] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.092105] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.093045] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.094936] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.096615] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.097834] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.099097] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.100687] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.101962] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.104086] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.105383] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.106637] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.107938] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.109252] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.111397] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.112550] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.113451] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.114378] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.115331] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.116326] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.117730] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.118612] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.119563] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.120541] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.121526] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.122928] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.123856] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.124830] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.125739] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.126654] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.128376] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.129288] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.130213] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.131147] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.132134] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.133497] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.134388] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.135314] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.136305] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.137220] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.138632] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.139529] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.140535] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.141466] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.142391] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.143837] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.144767] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.145725] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.146712] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.147637] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.149409] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.150365] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.151308] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.152356] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.153392] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.154934] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.155881] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.156827] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.157757] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.158690] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.160129] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.161084] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.162086] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.163051] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.164179] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.165775] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.166742] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.167678] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.168678] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.169666] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.171099] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.172037] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.172957] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.173970] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.174938] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.176456] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.177376] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.178307] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.179249] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.180394] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.183461] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.184443] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.185345] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.186265] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.187172] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.188851] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.189758] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.190690] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.191608] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.192590] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.193728] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.195167] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.196400] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.197322] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.198285] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.199884] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.200871] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.201918] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.202844] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.203785] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.204824] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.205762] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.206887] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.207809] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.208772] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.210122] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.211014] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.212124] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.213085] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.213992] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.214939] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.215897] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.217020] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.217946] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.218852] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.220199] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.221103] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.222011] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.222917] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.223840] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.224920] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.225840] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.226940] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.227866] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.228827] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.230116] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.231006] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.232175] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.233102] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.234052] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.234983] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.235958] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.237147] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.238069] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.238969] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.240292] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.241211] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.242162] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.243081] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.244056] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.244942] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.245857] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.246985] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.247844] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:38 192.168.122.209 [52049.248799] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:40 192.168.122.209 [52051.346628] [tdb] ERROR: out of free space Apr 26 06:31:40 192.168.122.209 [52051.347078] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:31:40 192.168.122.209 [52051.347694] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:31:40 192.168.122.209 [52051.357058] [tdb] ERROR: out of free space Apr 26 06:31:40 192.168.122.209 [52051.357561] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab275ce3946 Apr 26 06:31:40 192.168.122.209 [52051.358708] [tdb] ERROR: out of free space Apr 26 06:31:40 192.168.122.209 [52051.359098] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab287a5ba45 Apr 26 06:31:40 192.168.122.209 [52051.384876] [tdb] ERROR: out of free space Apr 26 06:31:40 192.168.122.209 [52051.386103] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab294f549b1 Apr 26 06:31:41 192.168.122.209 [52051.543126] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.544248] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.544565] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.546517] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.546873] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.548435] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.548963] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.549657] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.550251] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.550858] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.552916] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.555639] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.556546] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.557378] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.558213] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.559164] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.559929] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.560684] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.561413] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.562170] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.562926] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.565690] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.566465] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.567216] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.567974] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.568719] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.569443] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.570178] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.570920] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.571650] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.572401] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.575092] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.575857] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.576602] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.577334] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.578087] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.578841] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.579569] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.580311] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.581052] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.581789] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.584755] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.585515] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.586273] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.587024] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.587779] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.588535] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.589301] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.590032] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.590771] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.591490] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.594345] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.595108] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.595877] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.596662] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.597408] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.598143] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.598889] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.599609] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.600367] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.601119] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.603989] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.604743] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.605502] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.606229] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.606971] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.607701] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.608469] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.609222] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.609962] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.610759] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.616425] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.617161] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.617908] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.618640] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.619391] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.620158] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.620899] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.621635] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.622386] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.623117] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.625933] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.626702] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.627478] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.628227] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.628965] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.629713] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.630463] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.631205] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.631954] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.632693] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.635295] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.636077] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.636819] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.637546] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.638302] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.639041] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.639790] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.640517] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.641267] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.642016] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.645504] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.646258] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.647001] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.647739] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.648511] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.649273] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.650028] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.650781] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.651512] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.652273] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.656634] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.657390] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.658137] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.658904] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.659652] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.660428] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.661173] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.661916] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.662680] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.663403] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.667447] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.668248] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.668995] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.669741] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.670475] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.671214] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.671986] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.672717] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.673451] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.674184] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.678816] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.679640] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.680401] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.681136] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.681878] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.682603] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.683359] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.684142] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.684906] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.685660] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.689945] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.690764] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.691521] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.692273] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.693008] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.693735] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.694498] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.695230] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.695982] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.696727] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.701085] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.701844] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.702586] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.703315] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.704078] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.704832] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.705564] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.706294] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.707054] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.707805] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.712001] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.712783] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.713544] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.714292] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.715039] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.715788] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.716535] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.717262] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.718025] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.718778] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.723451] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.724284] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.725048] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.725803] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.726559] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.727283] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.728043] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.728776] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.729520] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.730251] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.737617] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.739942] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.741630] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.743309] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.745032] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.746690] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.748370] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.750007] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.750850] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.751595] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.758165] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.758969] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.760200] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.760978] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.761729] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.762473] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.763254] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.764036] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.764793] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.765531] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.770293] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.771080] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.771865] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.772618] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.773373] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.774120] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.774872] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.775629] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.776399] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.777150] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.781391] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.782181] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.782953] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.783692] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.784455] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.785221] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.785989] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.786747] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.787499] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.788263] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.801810] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.802851] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.803903] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.804917] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.805934] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.806934] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.807959] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.808971] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.809987] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.810996] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.813239] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.814182] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.815171] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.816123] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.817041] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.817985] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.818914] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.819866] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.820811] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.821750] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.823050] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.824021] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.824946] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.825903] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.826883] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.827829] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.828891] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.829880] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.830804] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.831737] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.833293] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.834169] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.835042] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.835927] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:41 192.168.122.209 [52051.836786] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.038976] [tdb] ERROR: out of free space Apr 26 06:31:42 192.168.122.209 [52053.039620] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:31:42 192.168.122.209 [52053.040526] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:31:42 192.168.122.209 [52053.047024] [tdb] ERROR: out of free space Apr 26 06:31:42 192.168.122.209 [52053.047452] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab2ddb83702 Apr 26 06:31:42 192.168.122.209 [52053.049149] [tdb] ERROR: out of free space Apr 26 06:31:42 192.168.122.209 [52053.049549] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab22fd3b401 Apr 26 06:31:42 192.168.122.209 [52053.070160] [tdb] ERROR: out of free space Apr 26 06:31:42 192.168.122.209 [52053.070572] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab23c8347f5 Apr 26 06:31:42 192.168.122.209 [52053.192343] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.193590] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.194541] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.195478] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.196462] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.197398] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.198344] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.199316] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.200570] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.202747] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.203729] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.204751] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.205685] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.206604] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.207524] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.208490] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.209432] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.210358] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.212625] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.213576] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.214513] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.215471] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.216469] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.217387] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.218308] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.219228] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.220250] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.222547] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.224251] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.225914] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.227515] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.228907] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.229861] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.230797] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.232088] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.233021] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.233931] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.234981] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.235927] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.236870] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.237781] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.238666] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.239426] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.240192] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.242064] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.242867] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.243624] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.244395] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.245177] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.245936] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.246699] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.247663] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.248450] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.249212] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.252336] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.253102] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.253859] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.254595] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.255380] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.256164] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.257043] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.257795] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.258557] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.259320] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.263076] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.263920] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.264699] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.265468] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.266236] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.267016] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.267807] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.268576] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.269370] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.270125] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.274036] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.274807] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.275598] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.276383] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.277147] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.277896] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.278665] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.279415] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.280200] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.281129] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.286355] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.287691] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.288474] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.289228] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.289999] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.290758] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.291521] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.292298] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.293071] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.293824] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.298852] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.299626] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.300437] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.301199] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.301969] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.302722] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.303484] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.304256] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.305022] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.305814] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.309956] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.310734] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.311491] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.312292] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.313066] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.313822] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.314575] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.315342] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.316164] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.316937] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.327806] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.328919] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.330032] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.331210] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.332497] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.333666] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.334909] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.336178] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.337410] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.338625] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.342573] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.343707] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.344505] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.345268] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.346056] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.346804] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.347567] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.348364] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.349139] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.349896] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.354083] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.354904] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.355669] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.356483] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.357256] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.358009] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.358783] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.359530] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.360312] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.361069] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.369331] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.370110] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.370879] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.371623] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.372407] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.373167] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.373935] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.374700] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.375475] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.376263] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.379769] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.380579] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.381370] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.382130] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.382891] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.383652] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.384435] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.385194] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.385957] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.386736] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.390778] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.391682] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.392491] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.393248] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.394011] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.394766] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.395535] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.396317] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.397102] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.397856] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.402293] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.403385] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.404573] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.405710] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.406875] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.408029] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.409167] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.410291] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.411425] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.412506] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.421261] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.422066] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.422865] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.423646] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.424469] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.425272] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.426073] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.426894] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.427698] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.428510] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.431844] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.432670] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.433448] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.434228] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.435003] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.435759] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.436529] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.437369] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.438145] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.438910] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.442280] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.443061] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.443841] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.444595] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.445358] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.446109] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.446899] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.447651] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.448433] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.449187] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.453488] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.454264] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.455023] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.455778] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.456556] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.457460] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.458232] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.459005] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.459767] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:42 192.168.122.209 [52053.460542] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:43 192.168.122.209 [52053.463935] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:43 192.168.122.209 [52053.465005] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:43 192.168.122.209 [52053.466073] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:43 192.168.122.209 [52053.467142] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:43 192.168.122.209 [52053.468229] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:43 192.168.122.209 [52053.469280] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:43 192.168.122.209 [52053.470340] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:43 192.168.122.209 [52053.471400] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:43 192.168.122.209 [52053.472490] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:43 192.168.122.209 [52053.473566] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:43 192.168.122.209 [52053.477382] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:43 192.168.122.209 [52053.478167] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:43 192.168.122.209 [52053.478937] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:43 192.168.122.209 [52053.479692] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:43 192.168.122.209 [52053.480465] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:43 192.168.122.209 [52053.481229] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:43 192.168.122.209 [52053.481983] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:43 192.168.122.209 [52053.482777] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:43 192.168.122.209 [52053.483533] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:43 192.168.122.209 [52053.484329] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:43 192.168.122.209 [52053.487447] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:43 192.168.122.209 [52053.488273] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:43 192.168.122.209 [52053.489047] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:43 192.168.122.209 [52053.489808] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:43 192.168.122.209 [52053.490561] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:43 192.168.122.209 [52053.491315] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:43 192.168.122.209 [52053.492095] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:43 192.168.122.209 [52053.492883] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:43 192.168.122.209 [52053.493589] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:43 192.168.122.209 [52053.494281] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:43 192.168.122.209 [52053.497487] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:43 192.168.122.209 [52053.498205] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.462836] [tdb] ERROR: out of free space Apr 26 06:31:45 192.168.122.209 [52055.464083] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:31:45 192.168.122.209 [52055.465872] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:31:45 192.168.122.209 [52055.473259] [tdb] ERROR: out of free space Apr 26 06:31:45 192.168.122.209 [52055.474408] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab217c2dbad Apr 26 06:31:45 192.168.122.209 [52055.474943] [tdb] ERROR: out of free space Apr 26 06:31:45 192.168.122.209 [52055.476606] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab204922859 Apr 26 06:31:45 192.168.122.209 [52055.480247] [tdb] ERROR: out of free space Apr 26 06:31:45 192.168.122.209 [52055.480919] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab2e5a958ae Apr 26 06:31:45 192.168.122.209 [52055.630360] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.634533] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.636324] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.637781] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.639314] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.641199] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.641305] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.641985] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.642167] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.642334] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.642594] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.642842] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.643278] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.643870] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.649234] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.653620] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.655502] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.656585] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.657466] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.658373] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.659768] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.660739] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.662257] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.663175] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.664137] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.665041] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.665936] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.666827] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.667729] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.668688] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.669691] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.670821] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.672324] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.673227] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.674110] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.675013] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.675943] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.676944] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.677843] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.678734] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.679644] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.680862] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.682377] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.683292] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.684436] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.685335] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.686232] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.687129] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.688300] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.689219] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.690099] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.691220] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.692831] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.693722] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.694630] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.695529] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.696520] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.697418] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.698316] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.699196] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.700183] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.701300] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.702825] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.703747] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.704854] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.705761] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.706662] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.707564] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.708644] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.709551] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.710432] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.714118] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.715635] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.716733] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.717629] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.718540] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.719428] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.720370] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.721299] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.722219] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.723106] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.724302] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.725188] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.726674] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.727569] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.728554] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.729472] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.730374] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.731253] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.732179] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.733065] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.734223] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.735116] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.736763] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.737653] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.738563] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.739443] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.740376] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.741268] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.742167] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.743069] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.744236] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.745300] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.746840] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.747756] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.748882] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.749807] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.750767] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.751687] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.752637] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.753598] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.754821] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.755700] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.757380] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.758303] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.759284] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.760233] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.761122] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.762032] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.762947] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.763870] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.765070] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.765955] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.767470] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.768591] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.769470] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.770378] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.771285] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.772229] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.773119] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.774025] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.775331] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.776302] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.777197] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.780656] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.781530] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.782442] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.783350] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.784366] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.785280] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.786187] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.787067] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.788292] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.789191] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.790656] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.791556] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.792513] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.793435] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.794319] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.795202] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.796155] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.797078] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.798242] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.799123] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.800921] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.801824] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.802752] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.803639] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.804586] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.805514] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.806412] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.807303] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.808677] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.809603] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.811152] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.812112] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.813017] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.813902] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.814790] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.815696] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.816821] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.817736] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.818904] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.819779] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.821337] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.822248] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.823138] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.824050] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.824949] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.825855] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.826743] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.827663] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.829108] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.830066] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.831663] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.832793] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.833681] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.834593] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.835529] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.836518] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.837452] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.838382] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.839617] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.840844] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.841776] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.843326] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.844299] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.845220] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.846128] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.847044] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.847987] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.848950] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.849911] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.851147] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.852268] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.853875] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.855507] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.856449] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.857378] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.858283] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.859188] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.860146] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.861082] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.861994] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.863068] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.864115] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.865415] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.866334] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.867277] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.868222] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.869148] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.870049] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.870949] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.871883] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.873024] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.873944] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.875228] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.876360] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.877267] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.878175] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.879076] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.880007] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.880942] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.881843] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.883014] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.883939] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.885153] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.886409] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.887320] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.888289] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.889219] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.890127] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.891030] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.891961] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.893232] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.894128] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.895051] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.896306] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.897199] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.898105] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.899015] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.899951] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.900821] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.901658] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.902802] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:45 192.168.122.209 [52055.903625] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:46 192.168.122.209 [52057.344339] [tdb] ERROR: out of free space Apr 26 06:31:46 192.168.122.209 [52057.344777] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:31:46 192.168.122.209 [52057.345359] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:31:46 192.168.122.209 [52057.351725] [tdb] ERROR: out of free space Apr 26 06:31:46 192.168.122.209 [52057.352617] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab2ad9ae85a Apr 26 06:31:46 192.168.122.209 [52057.358378] [tdb] ERROR: out of free space Apr 26 06:31:46 192.168.122.209 [52057.359305] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab25ff16b59 Apr 26 06:31:46 192.168.122.209 [52057.359829] [tdb] ERROR: out of free space Apr 26 06:31:46 192.168.122.209 [52057.361195] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab24ca198ad Apr 26 06:31:47 192.168.122.209 [52057.508794] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.508927] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.509815] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.510128] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.510567] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.510675] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.511033] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.512003] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.516043] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.516173] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.518164] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.519613] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.520769] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.521595] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.522440] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.523261] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.524108] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.524932] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.525747] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.528055] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.528901] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.529722] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.530460] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.531202] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.532000] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.532768] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.533523] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.534291] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.535033] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.537869] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.538662] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.539435] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.540245] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.541022] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.541815] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.542587] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.543361] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.544168] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.544945] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.556426] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.557839] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.558980] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.560125] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.561183] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.562054] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.562939] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.563824] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.564766] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.565638] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.567640] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.568617] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.569538] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.570450] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.571305] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.572114] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.572910] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.573685] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.574486] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.575255] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.578493] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.579288] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.580107] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.580883] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.581657] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.582428] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.583202] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.584007] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.584783] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.585563] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.590279] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.591050] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.591863] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.592623] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.593413] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.594162] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.594936] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.595675] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.596457] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.597210] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.599424] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.601585] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.602617] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.603624] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.604651] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.605677] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.606650] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.607631] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.608657] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.609646] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.610613] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.613052] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.614283] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.615068] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.615830] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.616598] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.617367] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.618125] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.618894] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.619639] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.620434] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.621196] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.624844] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.625803] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.626560] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.627310] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.628105] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.628915] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.629690] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.630627] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.631420] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.632206] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.634843] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.635856] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.637221] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.638007] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.638786] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.639538] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.640312] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.641087] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.641839] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.642586] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.643324] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.645011] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.645778] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.647724] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.648545] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.649319] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.650062] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.650809] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.651553] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.652332] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.653089] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.654572] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.656718] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.657494] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.658275] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.659054] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.659802] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.660571] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.661319] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.662232] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.662984] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.664615] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.665385] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.667256] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.668062] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.668860] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.669603] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.670356] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.671100] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.671876] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.672620] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.674224] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.674998] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.678985] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.679756] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.680534] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.681296] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.682089] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.682859] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.683626] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.684405] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.688824] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.689628] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.690397] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.691150] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.691925] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.692683] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.693476] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.694250] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.695013] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.695767] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.700127] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.700924] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.701706] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.702464] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.703222] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.704000] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.704779] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.705524] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.706289] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.707040] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.711378] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.712182] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.712954] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.713703] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.714474] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.715238] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.716043] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.716805] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.717563] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.718317] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.722588] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.723403] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.724210] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.724981] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.725751] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.726505] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.727262] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.728049] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.728823] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.729594] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.733878] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.735071] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.736246] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.737372] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.738506] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.739670] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.740922] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.742067] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.743209] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.744276] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.748461] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.749261] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.750068] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.750844] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.751628] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.752398] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.753167] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.753916] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.754684] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.755438] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.763008] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.763807] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.764623] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.765389] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.766165] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.766935] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.767698] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.768470] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.769236] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.770012] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.773605] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.774400] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.775232] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.776062] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.776940] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.777698] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.778465] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.779226] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.780043] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.780795] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.784480] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.785633] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.786730] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.787865] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.788974] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.790073] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.791173] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.792271] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.793356] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.794440] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.797939] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.798661] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.799415] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:47 192.168.122.209 [52057.800156] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:48 192.168.122.209 [52059.428495] [tdb] ERROR: out of free space Apr 26 06:31:48 192.168.122.209 [52059.429766] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:31:48 192.168.122.209 [52059.431069] [tdb] ERROR: out of free space Apr 26 06:31:48 192.168.122.209 [52059.431617] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:31:48 192.168.122.209 [52059.432033] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab2958b87f6 Apr 26 06:31:48 192.168.122.209 [52059.445496] [tdb] ERROR: out of free space Apr 26 06:31:48 192.168.122.209 [52059.445900] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab267e004f5 Apr 26 06:31:48 192.168.122.209 [52059.451716] [tdb] ERROR: out of free space Apr 26 06:31:48 192.168.122.209 [52059.452920] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab274b0f701 Apr 26 06:31:49 192.168.122.209 [52059.609819] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.619131] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.621950] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.622618] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.623987] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.624576] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.626122] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.626481] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.628903] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.629641] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.630593] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.631938] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.632715] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.633688] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.634420] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.635160] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.635915] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.636661] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.637395] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.638141] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.638872] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.640734] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.641484] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.642231] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.642953] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.643672] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.644422] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.645160] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.645902] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.646629] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.647345] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.649959] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.650700] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.651438] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.652191] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.652956] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.653673] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.654411] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.655136] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.655890] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.656619] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.664131] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.664911] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.665667] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.666396] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.667127] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.667879] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.668632] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.669356] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.670084] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.670812] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.673428] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.674185] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.674926] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.675666] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.676457] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.677195] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.677927] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.678649] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.679385] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.680151] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.682305] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.683054] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.683795] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.684536] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.685273] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.686001] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.686745] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.687470] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.688228] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.688954] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.690727] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.691462] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.692242] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.692985] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.693762] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.694481] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.695216] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.695986] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.696746] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.697468] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.700377] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.701122] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.701878] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.702603] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.703335] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.704107] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.704862] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.705591] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.706334] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.707057] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.710535] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.711328] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.712095] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.712827] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.713565] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.714295] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.715032] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.715747] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.716523] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.717249] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.721552] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.722303] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.723043] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.723786] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.724555] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.725309] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.726165] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.726900] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.727628] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.728379] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.737737] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.738652] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.739591] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.740534] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.741488] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.742401] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.743318] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.744264] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.745205] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.746131] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.749362] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.750147] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.750896] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.751644] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.752420] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.753151] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.753983] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.754711] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.755454] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.756199] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.759520] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.760321] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.761078] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.761842] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.762585] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.763313] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.764084] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.764827] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.765577] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.766304] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.769239] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.770877] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.771630] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.772385] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.773128] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.773862] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.774609] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.775365] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.776112] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.776876] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.777631] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.779488] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.781072] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.781829] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.782565] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.783310] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.784064] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.784802] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.785525] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.786253] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.786988] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.787710] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.791028] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.791808] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.792589] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.793322] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.794055] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.794783] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.795538] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.796305] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.797067] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.797794] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.799932] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.800675] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.801866] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.802601] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.803336] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.804084] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.804845] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.805581] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.806336] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.807085] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.807830] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.808590] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.814818] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.816056] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.816820] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.817585] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.818334] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.819090] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.819841] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.820630] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.821378] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.822145] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.822893] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.825234] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.826010] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.826764] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.827497] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.828263] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.829013] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.829755] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.830504] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.831245] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.832005] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.837994] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.838768] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.839518] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.840280] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.841040] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.841787] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.842534] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.843280] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.844055] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.844800] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.846896] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.847661] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.848442] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.849194] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.849945] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.850680] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.851443] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.852199] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.852951] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.853694] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.856036] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.856801] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.857553] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.858299] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.859046] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.859798] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.860561] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.861308] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.862070] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.862824] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.865856] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.866622] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.867382] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.868153] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.868909] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.869645] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.870401] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.871154] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.871931] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.872673] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.875743] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.876517] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.877277] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.878016] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.878781] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.879525] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.880235] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.880928] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.881612] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:49 192.168.122.209 [52059.882295] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52061.833171] [tdb] ERROR: out of free space Apr 26 06:31:51 192.168.122.209 [52061.833599] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:31:51 192.168.122.209 [52061.834186] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:31:51 192.168.122.209 [52061.854070] [tdb] ERROR: out of free space Apr 26 06:31:51 192.168.122.209 [52061.855266] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab2f89a8223 Apr 26 06:31:51 192.168.122.209 [52061.859707] [tdb] ERROR: out of free space Apr 26 06:31:51 192.168.122.209 [52061.860924] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab20af10120 Apr 26 06:31:51 192.168.122.209 [52061.864858] [tdb] ERROR: out of free space Apr 26 06:31:51 192.168.122.209 [52061.865254] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab219a1f2d4 Apr 26 06:31:51 192.168.122.209 [52062.030947] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.033901] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.039729] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.041123] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.042682] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.043684] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.044679] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.046236] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.047450] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.048294] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.048483] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.049996] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.050749] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.051506] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.052283] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.053049] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.053979] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.054737] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.056489] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.057266] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.058040] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.058792] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.059554] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.060326] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.061091] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.061844] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.062600] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.063346] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.065936] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.066691] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.067459] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.068234] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.068995] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.069732] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.070490] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.071239] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.072022] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.072771] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.074373] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.075141] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.075922] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.076670] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.077430] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.078178] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.078934] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.079692] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.080472] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.081236] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.082915] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.083678] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.084457] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.085227] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.085992] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.086731] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.087490] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.088257] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.089028] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.089814] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.091616] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.093043] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.093809] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.094557] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.095306] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.096087] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.096839] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.097599] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.098339] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.099101] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.099849] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.102783] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.103542] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.104333] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.105083] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.105841] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.106578] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.107333] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.108114] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.108877] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.109622] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.111448] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.112205] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.112945] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.113675] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.114437] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.115171] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.115923] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.116669] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.117421] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.118154] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.120083] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.121556] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.122304] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.123057] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.123785] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.124547] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.125276] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.126014] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.126738] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.127474] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.128238] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.130369] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.131115] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.131860] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.132603] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.133347] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.134100] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.134876] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.135622] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.136382] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.137114] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.139219] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.141883] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.142651] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.143401] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.144152] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.144917] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.145658] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.146398] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.147147] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.147921] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.148653] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.150985] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.152687] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.153431] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.154192] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.154927] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.155661] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.156437] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.157184] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.157925] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.158692] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.159442] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.161504] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.162838] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.163565] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.164328] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.165064] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.165826] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.166568] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.167323] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.168078] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.168823] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.169551] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.177282] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.178051] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.178810] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.179545] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.180320] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.181054] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.181813] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.182562] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.183329] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.184108] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.185677] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.186430] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.187168] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.187944] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.188689] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.189423] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.190173] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.190910] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.191655] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.192423] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.194233] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.194982] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.195714] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.196468] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.197207] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.197938] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.198696] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.199429] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.200212] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.200949] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.204026] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.204771] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.205533] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.206284] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.207028] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.207756] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.208533] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.209272] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.210007] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.210754] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.215109] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.215906] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.216658] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.217412] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.218162] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.218907] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.219643] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.220397] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.221141] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.221871] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.225378] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.226196] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.226968] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.227702] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.228464] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.229206] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.229950] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.230674] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.231428] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.232212] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.235638] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.236418] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.237164] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.237898] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.238649] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.239390] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.240157] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.240914] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.241671] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.242414] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.246048] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.246837] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.247586] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.248341] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.249082] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.249811] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.250538] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.251294] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.252041] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.252772] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.261528] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.262318] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.263119] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.263924] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.264735] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.265511] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.266287] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.267056] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.267841] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.268615] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.271124] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.271915] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.272676] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.273417] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.274158] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.274908] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.275661] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.276419] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.277165] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.277904] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.280628] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.281385] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.282141] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.282920] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.283675] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.284429] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.285185] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.285926] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.286682] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.287397] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.296082] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.296821] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:51 192.168.122.209 [52062.297520] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.127312] [tdb] ERROR: out of free space Apr 26 06:31:53 192.168.122.209 [52064.127721] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:31:53 192.168.122.209 [52064.128345] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:31:53 192.168.122.209 [52064.129175] [tdb] ERROR: out of free space Apr 26 06:31:53 192.168.122.209 [52064.129561] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:31:53 192.168.122.209 [52064.130146] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:31:53 192.168.122.209 [52064.133918] [tdb] ERROR: out of free space Apr 26 06:31:53 192.168.122.209 [52064.134298] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:31:53 192.168.122.209 [52064.134901] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:31:53 192.168.122.209 [52064.143982] [tdb] ERROR: out of free space Apr 26 06:31:53 192.168.122.209 [52064.144369] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab221b09d78 Apr 26 06:31:53 192.168.122.209 [52064.306846] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.311125] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.318758] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.319542] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.320710] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.321709] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.322421] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.323756] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.324505] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.327543] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.328979] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.329722] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.330750] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.331169] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.332314] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.333326] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.334093] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.334825] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.335560] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.336318] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.337064] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.337797] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.338553] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.339306] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.340065] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.341719] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.342480] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.343214] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.343976] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.344721] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.345440] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.346177] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.346897] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.347632] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.348378] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.354674] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.355439] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.356209] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.356963] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.357694] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.358423] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.359173] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.359937] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.360696] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.361425] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.363704] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.364465] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.365230] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.365958] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.366687] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.367413] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.368186] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.368922] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.369664] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.370407] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.373004] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.373767] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.374510] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.375235] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.375992] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.376746] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.377491] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.378219] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.378956] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.379679] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.382765] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.383524] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.384304] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.385036] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.385761] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.386491] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.387222] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.387967] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.388732] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.389488] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.392932] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.393665] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.394409] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.395135] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.395887] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.396629] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.397390] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.398122] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.398879] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.399610] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.403258] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.404061] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.404834] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.405554] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.406290] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.407018] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.407747] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.408512] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.409258] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.409992] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.421710] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.422697] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.423657] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.424645] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.425620] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.426573] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.427552] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.428511] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.429471] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.430385] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.433482] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.434270] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.435028] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.435752] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.436513] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.437264] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.438020] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.438746] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.439484] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.440232] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.443825] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.444613] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.445363] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.446114] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.446862] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.447586] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.448345] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.449081] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.449833] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.450571] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.453179] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.453953] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.454686] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.455437] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.456200] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.456940] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.457684] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.458412] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.459143] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:53 192.168.122.209 [52064.459870] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.462922] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.463689] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.464469] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.465218] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.465974] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.466701] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.467452] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.468199] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.468956] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.469684] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.472578] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.473318] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.474068] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.474792] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.475559] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.476325] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.477081] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.477804] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.478516] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.479243] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.482704] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.483487] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.484245] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.484977] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.485710] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.486441] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.487173] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.487906] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.488688] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.489419] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.491592] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.498146] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.498927] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.499663] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.500429] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.501192] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.501950] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.502668] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.503379] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.504142] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.504906] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.507350] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.508113] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.508859] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.509602] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.510351] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.511098] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.511856] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.512604] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.513365] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.514107] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.517287] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.518045] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.518798] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.519539] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.520327] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.521079] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.521811] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.522536] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.523318] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.524066] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.527551] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.528359] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.529123] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.529893] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.530643] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.531392] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.532167] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.532947] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.533696] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.534458] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.538405] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.539193] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.539981] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.540724] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.541475] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.542226] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.542973] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.543710] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.544498] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.545246] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.549468] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.550256] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.551019] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.551763] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.552541] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.553295] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.554048] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.554788] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.555538] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.556303] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.559356] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.560197] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.560960] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.561703] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.562452] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.563190] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.563958] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.564706] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.565473] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.566219] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.569001] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.570050] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.570800] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.571558] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.572320] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.573077] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.573827] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.574579] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.575326] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.576092] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.576843] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.580016] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.580798] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.581566] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.582317] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.583017] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.583753] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.584463] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.585146] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:54 192.168.122.209 [52064.585835] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:55 192.168.122.209 [52066.400224] [tdb] ERROR: out of free space Apr 26 06:31:55 192.168.122.209 [52066.401355] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:31:55 192.168.122.209 [52066.403012] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:31:55 192.168.122.209 [52066.410173] [tdb] ERROR: out of free space Apr 26 06:31:55 192.168.122.209 [52066.411367] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab29a1df840 Apr 26 06:31:55 192.168.122.209 [52066.415472] [tdb] ERROR: out of free space Apr 26 06:31:55 192.168.122.209 [52066.416595] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab268767b43 Apr 26 06:31:55 192.168.122.209 [52066.425920] [tdb] ERROR: out of free space Apr 26 06:31:55 192.168.122.209 [52066.426318] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab27b2688b7 Apr 26 06:31:56 192.168.122.209 [52066.572987] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.574034] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.574951] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.575882] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.583748] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.584830] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.585772] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.586744] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.588277] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.588988] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.589384] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.589462] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.591161] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.591590] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.594294] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.595190] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.596106] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.597025] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.597970] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.598866] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.599777] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.602601] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.603370] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.604134] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.604890] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.605629] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.606374] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.607118] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.607866] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.608627] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.609399] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.612093] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.612863] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.613607] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.614352] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.615108] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.615849] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.616625] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.617378] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.618132] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.618878] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.621867] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.622637] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.623398] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.624172] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.624941] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.625685] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.626433] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.627182] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.627931] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.628692] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.634045] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.634803] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.635557] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.636318] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.637077] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.637816] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.638572] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.639315] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.640098] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.640861] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.643151] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.643917] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.644684] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.645441] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.646193] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.646951] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.647718] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.648474] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.649236] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.649998] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.652992] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.653753] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.654507] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.655254] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.656022] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.656761] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.657511] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.658254] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.659003] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.659721] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.662051] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.662956] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.664499] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.665413] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.666326] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.667243] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.668189] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.669088] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.669971] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.670870] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.672456] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.673382] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.674280] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.675170] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.676084] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.677010] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.677898] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.678790] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.679712] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.680786] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.684577] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.685483] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.686387] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.687273] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.688216] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.689134] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.690066] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.690965] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.691861] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.692803] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.694349] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.695264] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.696308] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.697203] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.698117] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.699017] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.699898] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.700835] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.701753] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.702639] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.704349] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.705250] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.706135] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.707046] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.707933] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.708869] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.709760] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.710658] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.711590] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.712657] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.714248] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.715160] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.716093] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.717028] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.717923] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.718817] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.719724] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.720814] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.721732] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.722631] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.724204] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.725112] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.726025] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.726923] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.727805] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.728878] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.729788] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.730675] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.731559] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.732499] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.734056] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.734994] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.735898] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.736967] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.737889] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.738794] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.739681] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.740632] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.741540] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.742447] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.746510] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.747429] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.748374] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.749275] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.750156] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.751046] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.751927] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.752995] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.753921] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.754870] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.756427] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.757328] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.758226] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.759116] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.760038] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.761029] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.761954] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.762841] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.763745] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.764720] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.766240] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.767169] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.768102] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.769013] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.769902] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.770823] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.771742] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.772862] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.773745] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.774653] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.776201] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.777105] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.777994] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.778886] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.779791] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.780747] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.781641] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.782525] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.783424] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.784366] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.785908] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.786853] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.787761] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.788804] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.789694] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.790594] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.791503] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.792422] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.793330] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.794223] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.795760] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.796827] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.797730] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.798650] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.799561] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.800489] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.801388] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.802289] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.803181] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.804117] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.805606] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.806504] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.807397] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.808327] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.809224] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.810110] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.811030] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.811929] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.813108] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.814026] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.815446] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.816377] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.817290] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.818206] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.819133] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.820042] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.820959] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.821856] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.822752] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.823648] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.825128] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.826114] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.827023] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.827908] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.828875] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.829794] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.830696] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.831596] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.832549] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.833454] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.834695] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.835553] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.836586] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.837431] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:56 192.168.122.209 [52066.838279] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.727161] [tdb] ERROR: out of free space Apr 26 06:31:58 192.168.122.209 [52068.727651] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:31:58 192.168.122.209 [52068.728265] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:31:58 192.168.122.209 [52068.733989] [tdb] ERROR: out of free space Apr 26 06:31:58 192.168.122.209 [52068.735198] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab2a20c97ec Apr 26 06:31:58 192.168.122.209 [52068.740195] [tdb] ERROR: out of free space Apr 26 06:31:58 192.168.122.209 [52068.740816] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab2506714ef Apr 26 06:31:58 192.168.122.209 [52068.743773] [tdb] ERROR: out of free space Apr 26 06:31:58 192.168.122.209 [52068.744195] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab24337e71b Apr 26 06:31:58 192.168.122.209 [52068.920460] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.930734] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.930757] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.931346] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.931680] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.932398] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.936289] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.937189] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.938492] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.939804] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.941127] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.942224] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.943062] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.943822] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.944576] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.945340] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.946071] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.948912] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.949666] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.950406] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.951149] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.951890] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.952650] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.953392] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.954148] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.954888] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.955630] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.957779] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.963743] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.964507] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.965268] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.965994] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.966719] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.967447] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.968211] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.968977] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.969707] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.970427] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.973170] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.973936] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.974675] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.975415] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.976199] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.976946] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.977685] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.978407] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.979137] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.979879] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.982657] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.983424] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.984190] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.984934] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.985670] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.986394] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.987163] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.987935] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.988669] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.989402] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.992559] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.993346] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.994109] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.994824] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.995569] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.996312] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.997054] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.997775] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.998528] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52068.999269] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.002697] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.003455] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.004216] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.004941] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.005664] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.006401] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.007151] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.007883] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.008628] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.009347] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.012970] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.013724] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.014462] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.015199] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.015925] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.016692] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.017423] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.018168] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.018917] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.019651] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.023449] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.024240] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.024986] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.025707] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.026475] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.027199] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.027931] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.028666] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.029403] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.030129] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.041439] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.042205] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.042961] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.043687] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.044509] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.045484] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.046471] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.047456] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.048483] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.049482] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.052886] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.053881] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.054710] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.055455] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.056219] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.056965] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.057693] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.058437] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.059171] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.059896] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.063007] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.063770] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.064540] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.065267] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.066012] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.066734] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.067481] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.068216] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.068948] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.069671] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.073615] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.074406] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.075172] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.075929] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.076678] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.077427] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.078154] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.078872] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.079600] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.080371] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.084591] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.085363] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.086101] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.086826] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.087564] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.088328] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.089069] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.089794] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.090529] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.091275] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.095227] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.096021] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.096792] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.097534] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.098265] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.098988] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.099714] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.100457] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.101230] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.101953] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.106419] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.107172] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.107908] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.108665] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.109396] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.110141] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.110863] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.111585] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.112328] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.113053] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.118096] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.118866] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.119620] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.120391] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.121125] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.121850] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.122581] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.123337] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.124095] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.124818] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.140187] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.141219] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.142231] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.143224] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.144238] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.145234] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.146209] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.147045] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.147906] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.148770] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.152063] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.152944] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.153819] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.154663] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.155520] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.156300] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.157046] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.157785] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.158534] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.159290] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.163681] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.164492] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.165287] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.166034] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.166788] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.167536] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.168306] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.169060] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.169806] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.170547] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.174599] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.175380] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.176165] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.176924] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.177676] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.178417] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.179175] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.179919] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.180689] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.181434] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.185894] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.186670] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.187431] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.188198] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.188956] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.189703] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.190486] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.191245] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.192019] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.192768] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.196037] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.196813] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.197573] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.198314] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.199064] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.199809] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.200586] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.201341] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.202100] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.202841] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.206470] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.207243] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.208016] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.208766] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.209523] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.210270] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.211032] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.211770] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.212546] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.213302] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.216854] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.217631] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.218384] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.219108] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.219798] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.220497] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.221185] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:31:58 192.168.122.209 [52069.221862] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.565530] [tdb] ERROR: out of free space Apr 26 06:32:00 192.168.122.209 [52070.565938] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:32:00 192.168.122.209 [52070.566521] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:32:00 192.168.122.209 [52070.569066] [tdb] ERROR: out of free space Apr 26 06:32:00 192.168.122.209 [52070.569465] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:32:00 192.168.122.209 [52070.570075] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:32:00 192.168.122.209 [52070.575856] [tdb] ERROR: out of free space Apr 26 06:32:00 192.168.122.209 [52070.576330] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab20b0457ef Apr 26 06:32:00 192.168.122.209 [52070.594037] [tdb] ERROR: out of free space Apr 26 06:32:00 192.168.122.209 [52070.594431] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:32:00 192.168.122.209 [52070.595030] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:32:00 192.168.122.209 [52070.731788] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.745181] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.745732] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.747593] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.748596] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.749978] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.750399] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.751385] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.752596] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.752859] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.754359] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.755705] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.756744] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.757529] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.758287] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.759087] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.759831] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.760599] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.761361] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.763689] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.764496] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.765249] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.766000] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.766746] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.767492] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.768265] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.769016] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.769764] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.770522] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.773516] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.774300] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.775070] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.775818] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.776597] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.777354] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.778118] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.778862] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.779622] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.780414] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.782913] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.783701] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.784515] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.785276] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.786046] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.786799] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.787555] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.788334] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.789092] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.789842] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.793973] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.794740] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.795501] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.796278] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.797073] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.797826] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.798575] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.799321] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.800090] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.800845] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.803428] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.804254] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.805050] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.805802] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.806559] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.807321] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.808097] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.808866] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.809637] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.810388] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.812960] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.813757] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.814511] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.815259] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.816045] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.816801] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.817554] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.818309] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.819063] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.819792] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.821843] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.822593] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.823335] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.824074] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.824832] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.825560] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.826305] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.827073] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.827831] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.828583] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.831108] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.831845] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.832609] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.833361] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.834234] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.834973] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.835707] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.836455] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.837196] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.837923] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.840624] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.841386] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.842132] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.842854] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.843603] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.844348] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.845109] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.845851] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.846601] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.847382] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.850087] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.850860] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.851618] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.852372] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.853119] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.853845] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.854600] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.855333] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.856087] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.856854] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.860920] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.861663] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.862404] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.863129] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.863852] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.864619] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.865360] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.866101] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.866865] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.867615] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.870219] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.870977] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.871722] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.872482] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.873255] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.874000] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.874744] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.875491] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.876264] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.876999] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.879643] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.880435] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.881199] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.881972] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.882746] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.883511] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.884263] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.885018] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.885755] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.886502] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.889327] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.890096] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.890829] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.891567] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.892327] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.893054] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.893792] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.894529] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.895283] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.896026] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.898749] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.899500] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.900285] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.901021] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.901770] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.902499] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.903249] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.904012] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.904784] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.905531] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.908394] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.909141] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.909871] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.910611] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.911351] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.912112] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.912852] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.913580] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.914322] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.915062] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.917919] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.918687] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.919424] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.920172] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.920919] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.921654] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.922383] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.923120] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.923846] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.924605] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.928538] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.929297] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.930056] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.930789] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.931543] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.932362] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.933121] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.933839] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.934597] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.935341] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.938274] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.939046] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.939805] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.940566] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.941314] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.942060] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.942803] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.943546] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.944301] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.945031] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.948142] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.948907] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.949682] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.950410] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.951152] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.951909] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.952672] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.953405] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.954136] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.954878] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.958710] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.959474] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.960270] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.961108] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.961908] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.962663] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.963449] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.964209] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.964959] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.965686] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.969466] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.970241] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.971004] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.971754] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.972530] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.973273] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.974010] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.974765] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.975513] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.976324] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.979888] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.980673] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.981422] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.982165] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.982890] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.983626] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.984409] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.985165] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.985920] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.986663] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.990432] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.991155] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.991919] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.992628] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.993391] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.994076] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:00 192.168.122.209 [52070.994762] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52072.859709] [tdb] ERROR: out of free space Apr 26 06:32:02 192.168.122.209 [52072.860158] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:32:02 192.168.122.209 [52072.860746] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:32:02 192.168.122.209 [52072.866091] [tdb] ERROR: out of free space Apr 26 06:32:02 192.168.122.209 [52072.866506] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab2d22e48b4 Apr 26 06:32:02 192.168.122.209 [52072.875628] [tdb] ERROR: out of free space Apr 26 06:32:02 192.168.122.209 [52072.876075] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:32:02 192.168.122.209 [52072.876660] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:32:02 192.168.122.209 [52072.877105] [tdb] ERROR: out of free space Apr 26 06:32:02 192.168.122.209 [52072.877579] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab233153843 Apr 26 06:32:02 192.168.122.209 [52073.044715] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.049398] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.050587] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.051372] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.052446] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.053808] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.055580] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.057435] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.060709] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.060947] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.063685] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.065109] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.066474] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.067830] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.069202] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.070517] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.071286] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.072074] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.072837] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.073936] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.074700] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.075440] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.076194] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.076948] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.077672] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.078418] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.079149] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.079893] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.080648] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.086292] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.087064] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.087841] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.088588] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.089351] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.090104] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.090838] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.091569] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.092347] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.093108] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.095259] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.096024] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.096790] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.097526] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.098268] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.099022] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.099756] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.100537] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.101290] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.102040] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.104932] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.105719] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.106457] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.107200] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.107944] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.108692] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.109474] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.110218] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.110959] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.111692] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.114698] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.115471] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.116261] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.117005] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.117762] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.118496] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.119258] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.119996] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.120755] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.121500] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.125019] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.125774] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.126546] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.127315] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.128080] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.128823] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.129579] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.130338] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.131079] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.131833] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.135459] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.136249] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.137005] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.137752] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.138495] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.139230] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.139971] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.140719] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.141471] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.142229] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.146863] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.147643] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.148414] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.149160] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.149913] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.150645] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.151401] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.152157] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.152922] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.153664] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.157202] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.157966] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.158721] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.159472] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.160261] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.161019] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.161960] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.162697] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.163436] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.164208] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.167784] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.168595] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.169364] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.170097] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.170877] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.171685] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.172456] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.173208] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.173957] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.174663] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.178440] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.179227] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.179985] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.180741] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.181527] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.182278] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.183039] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.183775] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.184563] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.185301] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.189045] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.189796] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.190553] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.191314] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.192094] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.192846] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.193612] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.194347] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.195070] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.195778] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.198027] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.198962] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.199853] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.200962] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.201714] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.202446] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.203165] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.203907] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.204659] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.205389] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.207711] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.208476] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.209218] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.209948] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.210679] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.211410] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.212170] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.212904] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.213675] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.214387] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.216809] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.217559] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.218318] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.219043] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.219758] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.220526] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.221298] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.222051] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.222808] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.223541] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.225740] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.226474] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.227195] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.227918] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.228684] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.229440] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.230180] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.230921] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.231652] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.232418] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.236548] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.237305] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.238078] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.238827] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.239601] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.240370] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.241141] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.241902] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.242658] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.243419] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.247122] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.247910] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.248714] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.249466] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.250237] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.250989] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.251738] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.252510] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.253288] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.254042] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.262803] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.263579] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.264446] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.265297] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.266136] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.266971] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.267800] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.268662] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.269503] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.270334] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.273488] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.274284] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.275047] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.275797] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.276574] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.277327] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.278090] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.278815] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.279576] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.280342] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.282900] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.283728] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.284520] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.285275] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.286042] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.286786] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.287547] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.288317] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.289079] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.289825] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.295313] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.296130] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.296902] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.297656] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.298417] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.299172] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.299922] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.300689] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.301455] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.302208] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.304633] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.305392] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.306172] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.306897] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.307627] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.308416] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.309181] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.309936] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.310690] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.311450] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.313829] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.314603] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.315368] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.316077] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.316772] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.317460] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:02 192.168.122.209 [52073.318154] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.189590] [tdb] ERROR: out of free space Apr 26 06:32:04 192.168.122.209 [52075.190017] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:32:04 192.168.122.209 [52075.190619] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:32:04 192.168.122.209 [52075.205837] [tdb] ERROR: out of free space Apr 26 06:32:04 192.168.122.209 [52075.207054] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab27a5846f0 Apr 26 06:32:04 192.168.122.209 [52075.207177] [tdb] ERROR: out of free space Apr 26 06:32:04 192.168.122.209 [52075.209428] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:32:04 192.168.122.209 [52075.210020] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:32:04 192.168.122.209 [52075.220267] [tdb] ERROR: out of free space Apr 26 06:32:04 192.168.122.209 [52075.220849] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab29b633607 Apr 26 06:32:04 192.168.122.209 [52075.382747] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.383936] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.385028] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.385990] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.386922] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.387858] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.391432] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.392439] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.393394] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.394308] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.395236] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.396210] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.400249] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.401284] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.402255] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.403193] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.404139] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.405099] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.406767] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.407804] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.408822] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.409841] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.410667] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.411444] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.412293] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.413078] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.413877] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.414667] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.417210] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.418003] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.418766] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.419522] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.420316] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.421081] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.421881] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.422675] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.423428] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.424195] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.427199] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.427971] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.428762] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.429528] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.430302] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.431059] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.431832] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.432641] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.433401] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.434155] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.442528] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.443492] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.444553] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.445582] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.446636] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.447646] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.448633] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.449643] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.450602] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.451419] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.454725] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.455742] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.456568] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.457335] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.458120] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.458874] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.459647] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.460443] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:04 192.168.122.209 [52075.461217] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.461985] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.463975] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.465677] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.466453] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.467220] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.467968] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.468765] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.469539] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.470329] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.471071] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.471897] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.472715] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.477598] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.478684] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.479476] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.480270] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.481068] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.481825] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.482593] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.483385] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.484200] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.484971] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.487643] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.489507] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.490493] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.491261] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.492023] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.492844] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.493639] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.494416] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.495172] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.495936] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.496714] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.499007] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.499848] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.500639] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.501406] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.502162] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.502972] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.503725] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.504541] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.505310] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.506077] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.508779] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.509682] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.510493] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.511243] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.512051] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.512804] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.513660] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.514421] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.515191] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.515945] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.520238] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.521031] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.521797] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.522575] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.523350] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.524134] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.524901] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.525660] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.526424] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.527196] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.529467] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.531227] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.532751] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.533834] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.534881] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.535930] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.537017] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.538124] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.539172] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.540248] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.541323] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.544141] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.546149] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.547012] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.547775] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.548564] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.549337] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.550095] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.550878] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.551638] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.552434] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.553198] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.555577] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.565366] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.566361] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.567191] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.568009] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.568880] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.569704] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.570581] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.571414] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.572268] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.573090] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.575321] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.576131] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.576899] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.577701] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.578488] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.579246] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.580013] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.580802] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.581608] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.582378] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.585802] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.586584] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.587361] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.588149] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.588937] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.589718] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.590492] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.591262] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.592032] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.592806] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.595675] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.596494] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.597283] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.598037] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.598816] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.599573] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.600361] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.601159] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.601917] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.602681] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.604813] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.605883] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.606656] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.607418] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.608208] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.608977] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.609791] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.610575] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.611355] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.612133] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.613473] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.614939] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.615826] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.616627] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.617393] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.618163] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.618926] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.619699] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.620481] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.621282] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.622035] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.623309] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.624150] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.624936] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.625695] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.626456] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.627243] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.628014] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.628824] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.629601] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.630365] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.631556] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.632380] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.633140] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.633900] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.634672] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.635421] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.636212] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.636972] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.637725] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.638532] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.639826] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.640632] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.641789] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.642554] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.643319] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.644092] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.644863] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.645627] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.646385] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.647160] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.647920] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.648727] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.650066] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.650851] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.651622] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.652400] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.653179] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.653868] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.654636] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.655332] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.656032] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:05 192.168.122.209 [52075.656744] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.475422] [tdb] ERROR: out of free space Apr 26 06:32:07 192.168.122.209 [52077.475845] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:32:07 192.168.122.209 [52077.476465] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:32:07 192.168.122.209 [52077.477623] [tdb] ERROR: out of free space Apr 26 06:32:07 192.168.122.209 [52077.478837] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab24249295c Apr 26 06:32:07 192.168.122.209 [52077.483074] [tdb] ERROR: out of free space Apr 26 06:32:07 192.168.122.209 [52077.483467] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:32:07 192.168.122.209 [52077.484054] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:32:07 192.168.122.209 [52077.495034] [tdb] ERROR: out of free space Apr 26 06:32:07 192.168.122.209 [52077.495962] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab2a37259ab Apr 26 06:32:07 192.168.122.209 [52077.641890] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.642939] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.643865] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.645169] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.646129] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.647037] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.647945] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.649058] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.650154] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.653964] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.654888] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.655806] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.656768] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.657700] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.658600] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.659586] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.660528] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.661477] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.663440] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.664428] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.665303] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.666173] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.667072] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.667933] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.668904] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.669933] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.670800] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.671786] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.673611] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.674500] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.675400] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.676313] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.677200] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.678087] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.678952] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.679916] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.680943] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.681836] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.685823] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.686707] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.687622] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.688533] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.689401] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.690367] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.691275] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.692173] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.693089] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.694027] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.695661] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.696782] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.697660] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.698552] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.699445] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.700402] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.701358] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.702235] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.703134] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.704022] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.705282] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.706769] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.707628] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.708616] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.709511] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.710393] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.711295] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.712285] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.713171] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.714046] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.715173] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.717129] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.718030] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.718924] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.719830] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.720748] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.721624] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.722603] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.723500] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.724484] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.725588] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.727097] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.727961] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.728888] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.729788] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.730688] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.731589] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.732804] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.733693] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.734638] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.735742] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.737235] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.738096] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.738993] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.739868] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.740879] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.741756] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.742671] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.743624] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.744561] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.745749] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.749620] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.750504] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.751410] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.752520] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.753429] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.754455] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.755343] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.756256] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.757157] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.758288] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.759781] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.760876] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.761737] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.762641] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.763525] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.764532] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.765420] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.766298] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.767195] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.768408] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.769275] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.770838] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.771730] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.772797] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.773681] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.774659] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.775559] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.776466] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.777360] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.778536] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.779444] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.780996] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.781866] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.782755] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.783646] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.784727] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.785645] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.786577] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.787463] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.788642] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.789532] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.790974] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.791840] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.792939] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.793810] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.794710] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.795670] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.796602] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.797479] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.798634] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.799500] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.801253] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.802153] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.803038] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.803916] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.804843] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.805789] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.806674] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.807610] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.811255] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.812192] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.813762] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.814642] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.815527] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.816522] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.817396] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.818302] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.819194] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.820137] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.821394] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.822256] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.823784] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.824883] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.825766] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.826674] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.827566] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.828474] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.829368] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.830257] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.831493] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.832586] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.833461] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.834993] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.835872] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.836812] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.837711] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.838591] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.839485] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.840560] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.841495] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.842706] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.843631] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.845252] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.846145] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.847064] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.847946] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.848976] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.849871] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.850762] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.851668] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.852929] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.853848] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.855396] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.856337] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.857254] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.858148] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.859047] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.859942] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.860878] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.861789] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.863055] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.863991] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.865614] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.866613] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.867538] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.868742] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.869773] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.870668] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.871561] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.872518] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.873632] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.874508] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.878492] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.879391] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.880321] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.881240] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.882144] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.883037] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.883924] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.884892] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.886035] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.886915] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.888246] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.889153] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.890068] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.890960] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.891864] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.892941] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.893990] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.894895] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.896025] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.897261] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.898558] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.899425] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.900383] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.901277] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.902155] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.903051] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.903927] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.905108] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.906015] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.907123] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.908447] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.909282] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.910136] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.910952] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:07 192.168.122.209 [52077.911790] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52079.828758] [tdb] ERROR: out of free space Apr 26 06:32:09 192.168.122.209 [52079.830055] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:32:09 192.168.122.209 [52079.831068] [tdb] ERROR: out of free space Apr 26 06:32:09 192.168.122.209 [52079.831803] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:32:09 192.168.122.209 [52079.833163] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab20a7a99a8 Apr 26 06:32:09 192.168.122.209 [52079.838251] [tdb] ERROR: out of free space Apr 26 06:32:09 192.168.122.209 [52079.838690] [tdb] ERROR: out of free space Apr 26 06:32:09 192.168.122.209 [52079.839150] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:32:09 192.168.122.209 [52079.840350] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab2eb41e95f Apr 26 06:32:09 192.168.122.209 [52079.842613] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:32:09 192.168.122.209 [52080.007831] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.009078] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.010054] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.010975] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.016095] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.022542] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.023498] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.024489] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.025439] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.026901] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.026910] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.027361] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.030927] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.032673] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.034410] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.035459] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.036280] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.037093] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.038728] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.038743] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.041877] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.042690] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.045347] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.046157] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.046925] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.047691] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.048587] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.049376] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.050150] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.050905] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.051684] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.052486] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.054725] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.055494] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.056272] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.057056] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.057809] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.058566] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.059325] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.060099] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.060876] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.061639] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.063857] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.064652] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.065457] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.066231] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.066987] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.067741] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.068526] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.069289] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.070045] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.070789] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.073457] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.074228] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.074980] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.075736] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.076537] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.077312] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.078093] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.078859] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.079626] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.080396] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.082646] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.083442] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.101120] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.102029] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.102857] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.103658] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.104473] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.105300] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.106076] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.106826] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.109746] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.110559] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.111338] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.112087] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.112862] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.113713] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.114478] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.115220] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.115957] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.116708] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.118530] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.119282] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.124101] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.124871] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.125759] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.126538] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.127317] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.128069] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.128890] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.129665] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.130461] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.131289] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.133561] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.134357] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.135139] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.135911] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.136719] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.137511] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.138274] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.139098] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.139902] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.140710] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.142560] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.143337] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.144105] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.144896] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.145680] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.146432] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.147198] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.147924] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.148698] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.149470] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.153306] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.154086] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.154833] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.155585] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.156361] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.157137] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.157895] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.158645] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.159423] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.160222] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.163747] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.164588] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.165371] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.166160] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.166924] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.167680] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.168474] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.169222] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.169975] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.170735] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.174423] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.175215] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.175974] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.176748] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.177553] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.178302] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.179061] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.179801] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.180599] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.181378] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.185679] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.186464] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.187239] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.187977] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.188754] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.189511] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.190285] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.191022] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.191779] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.192557] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.201216] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.201993] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.202753] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.203541] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.204331] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.205092] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.205873] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.206665] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.207419] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.208170] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.211075] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.211880] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.212666] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.213480] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.214243] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.214977] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.215722] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.216493] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.217269] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.218009] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.221967] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.222747] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.223500] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.224261] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.225051] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.225786] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.226551] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.227290] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.228034] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.228791] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.232147] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.232913] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.233668] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.234407] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.235162] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.235950] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.236737] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.237532] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.238325] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.239088] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.243284] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.244068] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.244861] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.245657] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.246431] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.247204] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.247986] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.248745] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.249507] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.250272] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.255178] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.255962] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.256791] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.257559] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.258327] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.259083] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.259857] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.260617] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.261361] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.262115] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.266943] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.267739] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.268513] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.269251] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.269990] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.270726] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.271467] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.272239] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.272984] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.273745] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.283738] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.284584] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.285333] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.286102] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.286850] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.287612] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.288404] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.289170] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.289954] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.290698] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.293075] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.294013] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.294955] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.295871] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.296842] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.297787] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.298728] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.299643] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.300607] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.301537] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.303215] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.304155] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.305133] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.306062] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.306969] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.307913] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.308918] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.309853] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.310711] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.311606] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.313374] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:09 192.168.122.209 [52080.314241] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:11 192.168.122.209 [52082.257960] [tdb] ERROR: out of free space Apr 26 06:32:11 192.168.122.209 [52082.259199] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:32:11 192.168.122.209 [52082.261064] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:32:11 192.168.122.209 [52082.262447] [tdb] ERROR: out of free space Apr 26 06:32:11 192.168.122.209 [52082.263885] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab2326bf604 Apr 26 06:32:11 192.168.122.209 [52082.270956] [tdb] ERROR: out of free space Apr 26 06:32:11 192.168.122.209 [52082.271562] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:32:11 192.168.122.209 [52082.272413] [tdb] ERROR: out of free space Apr 26 06:32:11 192.168.122.209 [52082.272477] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:32:11 192.168.122.209 [52082.273323] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab2d35086f3 Apr 26 06:32:11 192.168.122.209 [52082.442279] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:11 192.168.122.209 [52082.452644] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.463956] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.465211] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.467463] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.468247] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.469304] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.469602] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.470461] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.471421] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.471682] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.472355] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.473407] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.473798] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.474561] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.476019] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.477245] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.479008] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.479935] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.481728] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.482617] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.483507] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.484577] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.485466] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.486384] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.487620] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.488630] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.489514] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.490427] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.491884] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.492782] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.493688] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.494583] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.495503] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.496439] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.497321] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.498513] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.499417] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.500446] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.501910] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.502807] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.503725] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.504704] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.505604] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.506509] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.507400] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.508653] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.509528] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.510406] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.511831] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.512840] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.513705] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.514624] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.515512] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.516439] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.517331] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.518575] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.519461] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.520739] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.521644] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.523022] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.523909] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.524909] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.525826] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.526730] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.527643] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.529055] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.529920] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.530799] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.531705] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.533179] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.534068] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.534974] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.535897] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.536836] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.537756] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.539053] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.539924] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.540878] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.541788] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.543178] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.544039] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.545097] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.545985] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.546863] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.547743] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.549064] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.549965] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.550889] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.551776] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.553401] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.554282] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.555178] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.556085] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.557022] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.557937] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.559181] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.560085] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.561023] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.561920] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.563290] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.564201] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.565119] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.566017] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.566919] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.567821] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.569174] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.570036] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.570936] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.571814] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.573268] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.574141] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.575034] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.575928] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.576951] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.577836] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.579126] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.579985] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.580915] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.581835] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.583276] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.584180] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.585105] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.585995] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.586878] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.587767] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.589300] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.590192] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.591077] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.591988] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.593460] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.594308] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.595186] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.596095] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.597148] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.598027] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.599342] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.600255] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.601176] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.602101] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.603512] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.604445] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.605389] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.606261] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.607133] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.608005] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.609475] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.610348] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.611253] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.612137] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.613548] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.614426] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.615307] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.616238] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.617131] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.617997] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.619285] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.620181] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.621270] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.622199] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.623525] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.624467] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.625331] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.626900] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.627768] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.628835] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.629741] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.630642] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.631537] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.632469] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.633362] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.634517] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.635392] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.636893] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.637787] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.638667] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.639543] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.640645] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.641552] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.642447] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.643337] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.644530] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.645419] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.646925] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.647813] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.648898] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.649805] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.650717] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.651625] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.652671] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.653601] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.654855] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.655739] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.657523] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.658428] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.659370] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.660286] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.661215] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.662116] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.663011] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.663915] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.668008] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.669094] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.672973] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.673868] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.674762] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.675681] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.676764] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.677661] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.678566] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.679451] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.680380] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.681467] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.682828] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.683716] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.684705] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.685599] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.686486] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.687369] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.688273] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.689210] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.690140] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.691223] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.692711] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.693609] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.694520] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.695418] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.696339] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.697247] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.698145] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.699071] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.699982] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.701088] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.702423] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.703318] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.704255] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.705183] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.706128] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.707031] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.707921] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.708979] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.709895] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.710996] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.712357] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.713270] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.714175] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.715084] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.715973] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.717141] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.718021] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.718894] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.719793] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.720864] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.722278] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.723138] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:12 192.168.122.209 [52082.723964] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:13 192.168.122.209 [52084.222372] [tdb] ERROR: out of free space Apr 26 06:32:13 192.168.122.209 [52084.222440] [tdb] ERROR: out of free space Apr 26 06:32:13 192.168.122.209 [52084.222809] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:32:13 192.168.122.209 [52084.224010] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab28bb0973a Apr 26 06:32:13 192.168.122.209 [52084.224610] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:32:13 192.168.122.209 [52084.243510] [tdb] ERROR: out of free space Apr 26 06:32:13 192.168.122.209 [52084.244361] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab2ad1170d2 Apr 26 06:32:13 192.168.122.209 [52084.253274] [tdb] ERROR: out of free space Apr 26 06:32:13 192.168.122.209 [52084.253697] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:32:13 192.168.122.209 [52084.254294] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:32:13 192.168.122.209 [52084.385704] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:13 192.168.122.209 [52084.394670] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:13 192.168.122.209 [52084.400019] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:13 192.168.122.209 [52084.406293] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:13 192.168.122.209 [52084.410014] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:13 192.168.122.209 [52084.410945] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:13 192.168.122.209 [52084.414591] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:13 192.168.122.209 [52084.414785] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:13 192.168.122.209 [52084.419937] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:13 192.168.122.209 [52084.422465] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:13 192.168.122.209 [52084.425082] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:13 192.168.122.209 [52084.426589] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:13 192.168.122.209 [52084.429498] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:13 192.168.122.209 [52084.430911] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:13 192.168.122.209 [52084.432931] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:13 192.168.122.209 [52084.436236] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:13 192.168.122.209 [52084.439167] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:13 192.168.122.209 [52084.441840] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:13 192.168.122.209 [52084.444697] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:13 192.168.122.209 [52084.447492] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:13 192.168.122.209 [52084.450243] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:13 192.168.122.209 [52084.453328] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:13 192.168.122.209 [52084.456538] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:13 192.168.122.209 [52084.459478] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.462634] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.467467] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.470410] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.473487] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.476501] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.479497] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.482535] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.485479] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.488434] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.491558] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.494660] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.500149] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.503104] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.506109] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.509035] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.511976] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.514901] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.518353] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.521273] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.524215] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.527115] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.532036] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.534989] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.537934] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.540973] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.544602] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.547552] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.550511] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.553442] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.556394] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.559294] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.563941] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.567363] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.570326] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.573233] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.576124] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.579041] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.582008] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.584912] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.587830] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.591238] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.598563] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.601515] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.604486] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.607269] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.609655] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.612527] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.615424] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.618505] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.621570] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.624507] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.631348] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.633657] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.635831] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.637131] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.639318] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.640737] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.641991] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.643225] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.644476] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.645694] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.651298] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.652561] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.653827] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.655057] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.656296] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.657548] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.658789] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.659523] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.660307] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.661037] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.665743] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.666537] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.667310] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.668066] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.668837] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.669587] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.670353] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.671117] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.671872] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.672661] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.677323] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.678114] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.678878] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.679638] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.680418] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.681189] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.681957] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.682709] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.683452] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.684238] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.688308] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.689066] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.689822] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.690564] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.691307] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.692050] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.692813] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.693561] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.694316] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.695047] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.699982] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.700815] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.701601] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.702322] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.703086] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.703823] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.704597] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.705357] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.706123] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.706867] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.711270] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.712047] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.712826] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.713568] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.714318] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.715086] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.715834] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.716600] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.717350] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.718101] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.722921] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.723707] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.724496] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.725258] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.726000] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.726739] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.727508] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.728272] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.729007] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.729784] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.734867] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.735639] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.736427] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.737167] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.737940] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.738687] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.739473] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.740240] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.740987] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.741716] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.745978] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.746770] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.747547] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.748326] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.749085] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.749823] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.750568] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.751345] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.752098] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.752860] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.756159] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.756956] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.757722] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.758478] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.759230] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.759988] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.760767] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.761512] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.762263] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.763204] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.767720] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.768736] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.769668] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.770563] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.771496] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.772912] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.773856] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.774770] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.775695] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.776751] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.778435] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.779374] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.780363] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.781336] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.782240] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.783186] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.784101] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.785236] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.786158] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.787123] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.788813] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.789748] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.790677] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.791583] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.792584] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.793513] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.794426] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.795330] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.796258] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.797382] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.798965] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.799876] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.800829] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.801741] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.802648] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.803555] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.804515] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.805424] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.806356] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.807277] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.808863] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.809793] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.810705] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.811614] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.812591] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.813521] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.814436] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.815352] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.816275] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.817205] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.818482] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.819436] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.820384] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.821345] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.822261] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.823169] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.824070] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.825229] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.826138] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.827048] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.828406] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.829332] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.830249] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.831177] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.832086] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.833227] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.834149] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.835015] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.835875] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.836794] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:14 192.168.122.209 [52084.851506] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.152732] [tdb] ERROR: out of free space Apr 26 06:32:15 192.168.122.209 [52086.153156] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:32:15 192.168.122.209 [52086.153747] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:32:15 192.168.122.209 [52086.159539] [tdb] ERROR: out of free space Apr 26 06:32:15 192.168.122.209 [52086.159950] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:32:15 192.168.122.209 [52086.160026] [tdb] ERROR: out of free space Apr 26 06:32:15 192.168.122.209 [52086.160567] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:32:15 192.168.122.209 [52086.161004] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab2676b9c7d Apr 26 06:32:15 192.168.122.209 [52086.170345] [tdb] ERROR: out of free space Apr 26 06:32:15 192.168.122.209 [52086.170742] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab28650ec8a Apr 26 06:32:15 192.168.122.209 [52086.315706] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.327841] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.328029] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.328906] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.330236] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.330283] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.330696] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.331476] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.331826] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.332481] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.335880] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.336937] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.337901] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.338736] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.339576] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.340442] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.341304] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.342139] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.342984] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.343813] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.345997] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.346772] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.347514] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.348274] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.349027] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.349755] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.350499] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.351241] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.351970] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.352748] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.354963] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.355740] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.356517] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.357262] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.358016] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.358749] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.359494] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.360262] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.361019] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.361772] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.363955] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.364718] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.365468] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.366194] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.366957] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.367700] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.368475] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.369231] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.369980] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.370719] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.373589] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.374346] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.375084] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.375813] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.376576] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.377309] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.378035] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.378770] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.379508] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.380257] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.382769] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.383557] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.384327] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.385079] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.385820] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.386565] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.387301] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.388049] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.388809] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.389561] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.395331] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.396118] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.396905] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.397644] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.398387] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.399126] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.399877] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.400626] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.401382] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.402107] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.404944] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.405724] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.406483] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.407207] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.407937] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.408689] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.409432] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.410166] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.410918] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.411648] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.414531] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.415303] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.416046] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.416844] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.417581] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.418328] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.419064] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.419813] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.420571] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.421306] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.423846] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.424632] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.425390] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.426136] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.426904] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.427638] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.428401] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.429128] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.429871] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.430601] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.433918] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.434672] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.435433] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.436166] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.436936] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.437662] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.438396] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.439141] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.439873] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.440627] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.448937] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.449683] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.450428] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.451150] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.451902] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.452672] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.453441] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.454194] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.454927] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.455660] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.458304] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.459063] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.459814] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.460587] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:15 192.168.122.209 [52086.461348] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.462077] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.462856] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.463586] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.464339] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.465066] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.468003] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.468766] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.469525] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.470254] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.470997] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.471722] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.472497] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.473227] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.473981] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.474719] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.478715] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.479494] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.480265] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.481001] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.481751] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.482536] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.483287] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.484036] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.484803] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.485571] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.489631] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.490435] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.491227] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.491971] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.492776] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.493541] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.494331] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.495108] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.495883] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.496656] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.502569] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.503330] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.504077] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.504831] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.505576] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.506289] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.507016] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.507754] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.508523] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.509285] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.513849] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.514610] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.515369] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.516107] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.516875] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.517630] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.518403] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.519160] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.519903] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.520683] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.526932] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.527711] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.528499] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.529258] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.529991] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.530742] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.531478] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.532241] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.533021] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.533788] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.536904] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.537656] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.538390] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.539132] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.539883] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.540638] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.541391] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.542123] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.542863] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.543600] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.547070] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.547839] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.548600] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.549331] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.550101] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.550834] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.551576] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.552330] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.553092] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.553837] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.557715] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.558476] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.559206] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.559925] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.560689] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.561463] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.562216] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.562973] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.563741] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.564504] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.567986] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.568780] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.569525] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.570266] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.571000] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.571745] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.572513] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.573263] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.574021] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.574758] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.578580] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.579347] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.580121] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.580871] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.581626] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.582363] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.583129] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.583856] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.584632] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.585400] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.588910] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.589686] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.590469] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.591174] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.591863] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:16 192.168.122.209 [52086.592577] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:17 192.168.122.209 [52087.531119] [tdb] Close table 'client0.tdb' Apr 26 06:32:17 192.168.122.209 [52087.752041] [tdb] Close table 'sessions0.tdb' Apr 26 06:32:21 192.168.122.209 [52091.476895] [tdb] Close table 'cache0.tdb' Apr 26 06:32:21 192.168.122.209 [52091.774513] [tdb] Close table 'filter0.tdb' Apr 26 06:32:21 192.168.122.209 [52091.775044] [tempesta fw] modules are stopped Apr 26 06:32:21 192.168.122.209 [52092.019648] [tempesta fw] exiting... Apr 26 06:32:21 192.168.122.209 [52092.154291] [tdb] Shutdown Tempesta DB Apr 26 06:32:22 192.168.122.209 [52092.701783] End test: t_stress.test_stress.TestTdbStressH2.test_cache_eviction_tdb Apr 26 06:32:22 192.168.122.209 [52092.718120] Start test: t_stress.test_stress.TestTdbStressHttp.test_cache_eviction_tdb Apr 26 06:32:23 192.168.122.209 [52094.112885] [tdb] Start Tempesta DB Apr 26 06:32:23 192.168.122.209 [52094.359401] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:32:25 192.168.122.209 [52095.885954] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52095.885954] Maybe that's fine, but it's worth checking the [52095.885954] config - if there is no relations between the [52095.885954] names, then host name confusion attack is possible. Apr 26 06:32:25 192.168.122.209 [52096.096641] [tempesta fw] Configuration processing is completed. Apr 26 06:32:25 192.168.122.209 [52096.155226] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:32:26 192.168.122.209 [52096.753182] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:32:26 192.168.122.209 [52096.804922] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:32:26 192.168.122.209 [52096.844615] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:32:26 192.168.122.209 [52096.924555] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:32:26 192.168.122.209 [52096.926385] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:32:26 192.168.122.209 [52096.972514] [tempesta fw] Tempesta FW is ready Apr 26 06:32:27 192.168.122.209 [52097.641135] [tdb] ERROR: out of free space Apr 26 06:32:27 192.168.122.209 [52097.641563] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:32:27 192.168.122.209 [52097.642167] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:32:27 192.168.122.209 [52097.644564] [tdb] ERROR: out of free space Apr 26 06:32:27 192.168.122.209 [52097.644953] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab2cf960ab1 Apr 26 06:32:27 192.168.122.209 [52097.645054] [tdb] ERROR: out of free space Apr 26 06:32:27 192.168.122.209 [52097.645972] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab2dcc6f945 Apr 26 06:32:27 192.168.122.209 [52097.741163] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.741971] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.742017] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.742072] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.742122] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.742225] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.742726] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.742730] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.742925] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.743384] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.743577] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.743701] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.743915] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.744378] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.745289] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.746386] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.746848] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.747904] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.753926] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.753964] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.754777] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.755690] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.758370] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.759187] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.759415] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.759704] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.759858] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.759919] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.760073] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.760169] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.765343] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.766243] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.767419] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.768268] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.768928] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.769049] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.769747] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.771230] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.771493] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.771506] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.771516] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.774539] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.775560] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.776703] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.777985] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.778810] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.778996] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.779011] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.779022] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.779463] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.779629] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.779647] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.780030] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.780169] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.780200] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.780285] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.786143] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.786991] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.787818] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.788373] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.789336] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.790540] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.790637] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.790640] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.790643] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.791050] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.791495] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.791596] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.792281] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.793064] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.793622] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.794319] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.798548] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.799408] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.799462] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.799911] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.800132] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.800151] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.800357] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.800676] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.800847] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.801131] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.801278] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.801411] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.801693] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.801833] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.802204] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.802362] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.802810] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.803259] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.803974] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.804201] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.804440] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.804493] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.804610] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.804763] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.805199] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.805561] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.805708] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.806150] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.806318] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.806521] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.807034] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.807921] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.808269] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.809773] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.809786] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.810163] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.810852] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.811410] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.812569] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.824636] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.825517] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.825524] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.825752] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.826219] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.830131] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.831479] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.831569] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.831584] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.831603] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.831865] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.831878] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.832067] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.832357] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.832425] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.833396] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.833673] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.834464] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.834716] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.834894] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.834908] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.835055] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.843580] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.844485] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.844592] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.844926] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.845199] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.845247] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.845263] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.845432] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.845449] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.845752] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.846091] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.846166] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.846509] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.846922] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.846943] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.847384] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.848011] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.849129] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.856712] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.857532] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.857790] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.857856] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.857886] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.858068] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.858290] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.858330] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.858421] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.862785] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.863890] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.864889] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.865269] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.867699] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.868205] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.868215] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.868232] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.868413] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.868708] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.868782] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.869294] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.869350] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.869905] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.871093] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.871696] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.872444] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.872472] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.872618] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.872642] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.873070] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.878734] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.878836] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.885900] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.886959] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.887221] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.887373] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.887387] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.887552] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.887651] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.888665] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.888875] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.889748] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.889859] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.890065] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.890082] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.890371] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.892362] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.893150] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.899151] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.899987] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.900110] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.900248] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.900578] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.900585] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.900757] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.900952] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.901000] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.901260] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.901397] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.901625] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.901857] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.902011] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.902222] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.902573] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.902614] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.903322] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.903984] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.912740] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.913714] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.913843] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.916360] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.916736] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.916813] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.916830] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.916974] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.917057] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.917149] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.921073] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.922067] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.922208] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.925019] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.925832] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.925904] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.925935] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.926020] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.926221] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.926468] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.926534] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.926774] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.926818] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.927098] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.927400] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.928166] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.929136] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.929652] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.930363] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.930381] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.930558] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.930580] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.930861] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.931212] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.931216] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.931409] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.933379] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52097.942228] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:27 192.168.122.209 [52098.434798] [tdb] ERROR: out of free space Apr 26 06:32:27 192.168.122.209 [52098.435220] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:32:27 192.168.122.209 [52098.435802] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:32:27 192.168.122.209 [52098.435826] [tdb] ERROR: out of free space Apr 26 06:32:27 192.168.122.209 [52098.436496] [tdb] ERROR: out of free space Apr 26 06:32:27 192.168.122.209 [52098.436735] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab2f787651d Apr 26 06:32:27 192.168.122.209 [52098.436950] [tdb] ERROR: out of free space Apr 26 06:32:27 192.168.122.209 [52098.436952] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:32:27 192.168.122.209 [52098.436953] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:32:27 192.168.122.209 [52098.437141] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab205ece61e Apr 26 06:32:28 192.168.122.209 [52098.551696] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.552666] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.552701] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.553395] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.554581] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.555175] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.556361] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.556953] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.557556] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.558171] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.559354] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.559396] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.560142] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.561462] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.562255] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.562648] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.563212] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.564388] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.564848] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.565461] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.566045] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.567148] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.567256] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.567992] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.568476] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.569157] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.570644] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.572040] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.573170] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.574010] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.574105] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.575341] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.576156] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.576472] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.577147] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.577664] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.578581] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.578872] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.579770] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.580086] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.581005] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.581322] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.582284] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.582670] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.583739] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.583781] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.584570] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.584655] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.584962] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.585521] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.585676] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.586383] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.586872] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.587706] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.588078] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.589008] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.589322] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.589963] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.590501] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.591586] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.591817] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.593358] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.593776] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.594443] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.594548] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.595321] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.595637] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.596502] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.596999] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.597998] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.598201] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.598889] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.599405] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.600242] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.600616] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.601526] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.603716] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.605115] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.605942] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.606499] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.607479] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.607584] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.608178] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.609087] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.609377] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.610332] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.610592] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.611364] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.611378] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.611810] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.612674] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.613004] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.613886] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.615601] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.616815] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.618221] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.619046] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.619105] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.619155] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.619504] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.619759] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.619844] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.620185] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.620537] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.620816] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.620863] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.621133] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.621358] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.621438] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.621742] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.622028] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.622346] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.622942] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.623929] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.624142] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.624870] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.625377] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.626114] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.626308] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.626440] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.626964] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.627384] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.627707] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.627765] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.628295] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.629496] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.630153] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.631157] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.631365] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.632078] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.632649] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.633326] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.646974] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.647827] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.647972] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.648331] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.648543] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.648601] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.648954] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.649256] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.649540] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.649814] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.650099] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.650388] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.650678] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.651320] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.652200] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.652760] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.653543] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.654155] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.655016] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.655560] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.656261] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.662769] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.663725] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.664139] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.666447] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.666550] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.667154] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.668052] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.668374] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.669597] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.669662] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.670314] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.671041] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.671199] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.671571] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.672412] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.672559] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.672719] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.673202] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.673584] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.673904] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.674198] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.674487] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.674771] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.674824] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.675193] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.675299] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.675457] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.675688] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.675903] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.676113] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.676337] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.676594] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.676849] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.677080] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.677751] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.678690] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.679044] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.679732] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.680287] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.681097] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.681151] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.681298] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.681531] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.681557] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.681782] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.682023] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.682241] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.682465] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.682699] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.682916] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.683167] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.699799] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.704706] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.705530] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.705733] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.705754] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.706456] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.707235] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.707844] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.709066] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.709268] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.709943] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.710673] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.711607] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.711641] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.712068] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.712776] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.715861] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.716745] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.717573] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.717754] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.717763] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.718040] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.718296] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.718477] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.718571] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.718804] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.719032] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.719273] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.719515] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.719761] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.719994] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.720222] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.720489] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.720540] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.720689] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.720936] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.720947] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.721032] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.721109] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.721191] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.733849] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.734953] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.735726] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.735772] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.735905] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.736122] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.736378] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.740141] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.740867] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.741591] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.742312] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52098.742968] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.213900] [tdb] ERROR: out of free space Apr 26 06:32:28 192.168.122.209 [52099.214206] [tdb] ERROR: out of free space Apr 26 06:32:28 192.168.122.209 [52099.214326] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:32:28 192.168.122.209 [52099.214656] [tdb] ERROR: out of free space Apr 26 06:32:28 192.168.122.209 [52099.214659] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab2e155824e Apr 26 06:32:28 192.168.122.209 [52099.214753] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab2ace4261d Apr 26 06:32:28 192.168.122.209 [52099.215344] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:32:28 192.168.122.209 [52099.215416] [tdb] ERROR: out of free space Apr 26 06:32:28 192.168.122.209 [52099.215419] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab299153201 Apr 26 06:32:28 192.168.122.209 [52099.347389] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.349053] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.349062] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.350896] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.350901] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.350983] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.351728] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.351774] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.352147] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.353104] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.353208] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.353349] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.353485] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.353616] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.353778] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.353935] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.361201] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.361950] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.361970] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.362109] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.362249] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.362413] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.362864] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.363048] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.363515] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.365077] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.370141] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.370822] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.372622] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.372654] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.373473] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.375576] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.376497] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.376505] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.377744] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.378808] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.379522] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.380266] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.380296] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.380764] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.381164] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.382330] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.385238] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.385262] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.388075] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.388095] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.390041] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.390071] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.390088] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.390624] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.390829] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.390943] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.391036] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.391375] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.391532] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.391677] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.392036] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.392182] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.392318] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.392512] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.392811] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.393203] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.393662] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.393725] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.402012] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.402837] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.402868] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.404262] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.404509] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.405066] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.405271] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.405322] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.405540] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.405783] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.405967] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.406366] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.406550] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.406625] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.406707] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.407001] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.407355] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.407738] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.407823] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.407900] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.415308] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.415317] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.416723] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.417605] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.417752] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.418289] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.418494] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.418513] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.418584] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.418664] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.418722] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.418766] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.419160] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.419485] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.419772] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.419846] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.420142] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.420470] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.420612] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.420801] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.421113] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.422171] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.423096] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.423574] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.423782] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.423837] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.424423] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.425318] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.425346] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.439979] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.440838] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.440874] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.442555] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.442561] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.442569] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.442702] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.445177] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.446125] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.446198] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.446306] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.446333] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.446939] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.447011] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.447059] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.447405] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.447577] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.447695] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.447782] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.447787] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.448110] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.448441] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.448604] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.448642] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.448960] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.449224] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.449314] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.449318] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:28 192.168.122.209 [52099.449714] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.450091] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.450284] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.450528] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.450650] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.450795] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.451001] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.451324] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.451358] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.452293] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.453217] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.453640] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.453813] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.454408] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.455233] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.455306] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.471857] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.472547] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.473626] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.473632] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.473637] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.473758] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.476399] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.476496] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.476514] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.477846] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.478735] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.479245] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.479491] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.479893] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.480060] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.480067] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.480166] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.480269] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.481290] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.486400] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.486424] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.487887] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.487904] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.489020] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.492284] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.492313] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.493765] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.493787] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.494162] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.494329] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.494599] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.494670] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.494980] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.495000] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.495101] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.495198] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.495529] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.496375] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.505687] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.505731] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.507228] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.507389] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.507415] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.507580] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.507902] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.507922] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.508181] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.508425] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.508905] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.509096] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.509276] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.509409] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.509561] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.509788] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.510032] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.510246] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.510482] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.510694] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.510925] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.510976] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.511104] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.522303] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.522334] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.524071] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.524098] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.525711] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.525760] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.525783] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.525954] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.528767] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.529070] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.529078] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.529099] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.529499] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.529724] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.529970] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.530185] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.530403] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.530695] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.530707] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.530836] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.530981] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.531188] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.532074] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.539521] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.539528] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.541083] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.541098] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.541321] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.541417] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.541683] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.541727] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.541775] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.543554] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.544347] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.544513] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.546022] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.546482] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52099.548411] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.060324] [tdb] ERROR: out of free space Apr 26 06:32:29 192.168.122.209 [52100.060843] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:32:29 192.168.122.209 [52100.061544] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:32:29 192.168.122.209 [52100.062709] [tdb] ERROR: out of free space Apr 26 06:32:29 192.168.122.209 [52100.063171] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:32:29 192.168.122.209 [52100.063865] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:32:29 192.168.122.209 [52100.066798] [tdb] ERROR: out of free space Apr 26 06:32:29 192.168.122.209 [52100.067291] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab287a5ba45 Apr 26 06:32:29 192.168.122.209 [52100.068737] [tdb] ERROR: out of free space Apr 26 06:32:29 192.168.122.209 [52100.069153] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab294f549b1 Apr 26 06:32:29 192.168.122.209 [52100.182699] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.183564] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.184415] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.184473] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.184608] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.186467] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.190897] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.192673] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.193756] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.194834] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.196042] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.196790] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.199083] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.199897] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.200926] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.201725] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.202492] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.203296] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.203567] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.203718] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.203848] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.204087] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.208079] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.208880] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.209692] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.210476] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.211334] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.211393] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.214313] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.215112] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.215867] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.216704] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.216905] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.217067] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.217443] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.217449] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.221183] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.221880] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.222583] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.223284] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.224037] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.224055] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.225650] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.226430] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.227191] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.227704] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.227880] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.228631] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.229801] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.230571] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.230775] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.230965] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.231115] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.231278] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.231606] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.231787] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.231960] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.232274] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.232575] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.232873] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.233282] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.234148] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.234498] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.235422] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.235708] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.236489] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.242377] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.243157] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.243927] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.244484] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.245343] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.246115] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.246873] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.247122] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.247301] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.247454] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.247585] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.247892] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.248037] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.248253] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.248568] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.248844] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.249153] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.249735] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.250574] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.250962] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.251800] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.252168] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.256951] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.258290] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.259079] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.259800] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.260617] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.261374] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.262128] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.262320] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.262396] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.262578] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.262822] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.262983] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.263671] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.264034] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.264958] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.265285] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.266110] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.266497] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.267505] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.267684] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.268384] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.271540] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.272214] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.274309] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.275079] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.275856] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.275973] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.276217] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.276561] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.276656] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.276902] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.277429] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.277768] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.278636] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.278973] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.279846] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.280182] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.281083] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.281404] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.282254] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.285948] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.286731] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.288137] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.289116] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.289875] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.290634] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.290844] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.291087] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.291229] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.291344] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.291400] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.291624] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.291964] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.292581] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.293469] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.293952] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.294827] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.295322] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.296329] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.296656] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.297378] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.301305] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.302443] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.303229] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.308585] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.309363] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.310133] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.310279] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.310408] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.310513] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.310858] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.310889] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.311674] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.312056] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.313148] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.313281] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.314212] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.314634] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.315493] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.315973] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.316862] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.320197] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.321179] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.321966] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.323320] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.324091] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.324918] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.325215] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.325234] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.325359] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.325508] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.325661] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.326492] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.326846] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.327739] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.328052] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.328858] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.329315] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.330151] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.330488] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.331147] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.334388] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.334753] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.336828] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.337595] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.338367] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.338494] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.338651] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.338964] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.339081] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.339261] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.339858] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.340287] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.341148] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.341517] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.342344] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.342727] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.343581] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.343953] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.344742] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.347849] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.349002] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.349808] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.350563] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.350747] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.350808] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.350883] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.351149] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.351290] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.352070] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.352483] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.353299] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.353708] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.354506] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.354921] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.355690] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.356160] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.357090] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.360071] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.360895] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.362009] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.362784] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.363549] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.363712] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.363871] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.363891] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.364149] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.364256] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.365061] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.365486] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.366276] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.366703] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.367473] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.367918] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.368711] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.369145] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.369982] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.372846] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.373733] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.374166] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.376417] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.377211] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.377303] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.377934] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.379134] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.379781] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.380423] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:29 192.168.122.209 [52100.381079] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52100.986435] [tdb] ERROR: out of free space Apr 26 06:32:30 192.168.122.209 [52100.986839] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:32:30 192.168.122.209 [52100.987442] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:32:30 192.168.122.209 [52100.988480] [tdb] ERROR: out of free space Apr 26 06:32:30 192.168.122.209 [52100.988873] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:32:30 192.168.122.209 [52100.989467] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:32:30 192.168.122.209 [52100.993036] [tdb] ERROR: out of free space Apr 26 06:32:30 192.168.122.209 [52100.993560] [tdb] ERROR: out of free space Apr 26 06:32:30 192.168.122.209 [52100.993672] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab23c8347f5 Apr 26 06:32:30 192.168.122.209 [52100.994142] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab22fd3b401 Apr 26 06:32:30 192.168.122.209 [52101.119611] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.120865] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.120914] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.120959] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.121113] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.123522] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.123624] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.123738] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.123759] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.123933] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.124493] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.124635] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.124834] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.124989] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.125071] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.125525] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.125874] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.126411] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.128014] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.128831] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.130533] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.136460] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.138554] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.138692] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.138851] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.139015] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.139260] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.140090] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.140677] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.141426] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.142028] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.142782] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.147695] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.147842] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.147859] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.148257] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.148483] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.149042] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.149843] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.152308] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.152415] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.152444] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.153002] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.153037] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.153676] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.154470] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.154569] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.155008] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.155037] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.155049] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.155222] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.155436] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.155658] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.155841] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.155854] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.156242] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.156531] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.156624] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.156741] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.157167] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.157171] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.157830] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.158949] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.159006] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.159703] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.160198] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.161057] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.170937] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.171759] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.172182] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.172411] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.172553] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.172611] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.172890] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.172894] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.173009] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.173589] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.173687] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.173877] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.173999] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.174285] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.174317] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.174713] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.174925] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.175083] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.175382] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.175452] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.175535] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.175739] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.185741] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.186423] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.186712] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.186771] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.186888] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.189075] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.189186] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.189208] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.189638] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.190054] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.190148] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.190321] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.190589] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.191586] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.194101] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.194425] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.194641] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.194665] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.194969] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.195005] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.195364] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.195546] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.195588] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.195713] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.196008] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.196397] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.196440] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.205453] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.205757] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.206427] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.206432] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.206584] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.206702] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.206910] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.207043] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.207396] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.207572] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.207707] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.207823] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.207923] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.208025] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.214825] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.215546] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.215605] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.216366] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.216449] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.217058] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.217547] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.217565] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.217712] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.217741] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.217836] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.217913] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.218409] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.218739] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.218856] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.218991] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.219013] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.219401] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.219499] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.219750] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.219938] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.220053] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.220375] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.220792] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.220821] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.221026] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.221157] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.221517] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.221861] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.222064] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.222100] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.222533] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.222667] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.222916] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.222922] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.223101] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.223267] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.223640] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.223823] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.223962] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.224270] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.247485] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.247570] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.247974] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.248387] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.248405] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.248432] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.248505] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.249006] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.249225] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.249241] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.249376] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.249494] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.249620] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.249892] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.250913] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.251190] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.252266] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.253314] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.260057] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.260116] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.260288] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.260524] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.260615] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.260784] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.260904] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.260962] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.260987] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.261262] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.261462] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.261557] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.261684] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.261893] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.262111] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.262772] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.263606] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.263760] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.263916] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.263987] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.264028] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.264225] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.264538] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.264616] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.265391] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.266272] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.266623] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.266665] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.266721] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.278529] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.279414] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.279441] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.279822] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.279992] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.280039] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.280081] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.280351] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.280395] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.280654] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.280820] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.280901] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.280972] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.281061] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.281149] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.288884] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.288950] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.289236] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.289432] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.289642] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.289679] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.289686] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.289951] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.290098] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.290257] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.290277] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.290496] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.290533] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.290684] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.290706] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.290944] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.291031] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.291046] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.291204] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.291344] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.291368] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.304010] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:30 192.168.122.209 [52101.304731] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52101.872408] [tdb] ERROR: out of free space Apr 26 06:32:31 192.168.122.209 [52101.872489] [tdb] ERROR: out of free space Apr 26 06:32:31 192.168.122.209 [52101.872838] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:32:31 192.168.122.209 [52101.873118] [tdb] ERROR: out of free space Apr 26 06:32:31 192.168.122.209 [52101.873131] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab204922859 Apr 26 06:32:31 192.168.122.209 [52101.873276] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab217c2dbad Apr 26 06:32:31 192.168.122.209 [52101.875487] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:32:31 192.168.122.209 [52101.876550] [tdb] ERROR: out of free space Apr 26 06:32:31 192.168.122.209 [52101.876939] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:32:31 192.168.122.209 [52101.877533] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:32:31 192.168.122.209 [52102.002270] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.002324] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.002362] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.002528] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.003225] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.003272] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.004979] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.005657] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.005775] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.005954] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.011609] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.012335] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.012340] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.012581] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.012818] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.013690] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.014749] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.016866] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.017095] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.017269] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.018080] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.019662] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.020448] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.022061] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.022923] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.024622] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.029808] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.029881] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.029936] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.030618] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.031342] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.031403] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.031621] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.032138] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.032272] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.032565] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.032718] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.033761] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.033976] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.034624] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.035440] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.036315] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.037237] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.037645] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.037743] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.038031] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.038219] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.038401] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.038511] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.046429] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.047130] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.047137] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.047176] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.049265] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.049387] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.049392] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.049622] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.050302] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.050399] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.050438] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.050615] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.050945] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.051318] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.051348] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.051510] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.051901] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.051905] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.052265] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.052677] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.052936] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.053063] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.053426] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.053981] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.054008] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.054187] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.055051] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.065657] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.070920] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.070968] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.070975] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.071249] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.071521] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.071617] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.071745] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.071824] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.071872] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.072183] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.072480] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.072594] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.072766] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.072927] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.073258] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.081190] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.081235] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.081751] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.081998] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.082034] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.082067] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.082282] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.082654] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.082852] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.082891] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.083073] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.083387] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.083619] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.083649] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.083811] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.084157] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.084477] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.084511] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.084734] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.084738] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.094879] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.094976] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.094997] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.095195] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.095238] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.095396] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.095525] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.095537] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.095635] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.096302] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.097721] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.097786] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.097964] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.097996] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.098167] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.098252] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.098788] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.098816] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.098865] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.099705] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.099746] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.099749] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.099924] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.100694] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.100772] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.100932] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.101015] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.101170] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.101691] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.102276] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.105651] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.105703] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.105719] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.106268] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.106725] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.106779] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.106834] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.107018] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.107743] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.107775] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.107791] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.107949] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.108105] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.108466] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.108914] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.109395] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.110131] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.125878] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.125927] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.126361] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.126704] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.126766] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.126775] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.127006] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.127433] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.127491] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.127550] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.127708] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.128062] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.128218] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.128344] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.128348] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.128807] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.128851] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.129331] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.129344] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.129447] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.129641] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.130006] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.130416] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.130712] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.130750] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.131253] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.131786] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.132713] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.133693] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.133710] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.133731] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.133901] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.134028] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.134033] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.134655] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.134745] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.134923] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.134969] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.135153] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.135168] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.135301] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.135481] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.135595] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.135972] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.135988] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.136153] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.136301] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.136489] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.136628] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.137005] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.158927] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.160102] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.160105] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.160436] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.160464] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.160699] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.160753] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.160924] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.161004] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.161066] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.161300] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.161425] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.161740] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.161919] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.162018] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.162060] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.162435] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.162482] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.173483] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.173639] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.174454] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.176196] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.179401] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.179493] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.180383] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.181495] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.183007] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.184048] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.185118] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.186156] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.187662] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.187735] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.188499] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.189536] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.190857] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.191637] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.192429] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.193211] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.194372] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.194394] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.195148] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.195672] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.196360] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.197600] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.198319] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.199027] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:31 192.168.122.209 [52102.200134] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.831941] [tdb] ERROR: out of free space Apr 26 06:32:32 192.168.122.209 [52102.832215] [tdb] ERROR: out of free space Apr 26 06:32:32 192.168.122.209 [52102.832355] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:32:32 192.168.122.209 [52102.832797] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab279508cb1 Apr 26 06:32:32 192.168.122.209 [52102.833150] [tdb] ERROR: out of free space Apr 26 06:32:32 192.168.122.209 [52102.833396] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:32:32 192.168.122.209 [52102.834019] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab2ad9ae85a Apr 26 06:32:32 192.168.122.209 [52102.836108] [tdb] ERROR: out of free space Apr 26 06:32:32 192.168.122.209 [52102.836543] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab24ca198ad Apr 26 06:32:32 192.168.122.209 [52102.945048] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.945112] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.945170] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.945212] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.945470] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.945864] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.946148] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.946394] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.946643] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.946846] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.946997] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.948021] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.948063] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.948225] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.948422] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.949105] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.950355] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.950514] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.950616] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.951194] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.951760] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.953320] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.954397] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.955462] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.958645] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.958749] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.958901] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.959359] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.959679] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.959974] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.960012] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.960098] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.960363] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.960385] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.960525] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.961092] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.962742] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.963141] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.963238] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.963245] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.964081] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.965747] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.965816] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.965921] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.966263] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.966435] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.966610] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.966820] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.966847] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.966924] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.967290] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.967508] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.968313] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.968944] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.968965] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.969824] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.987386] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.988218] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.989065] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.989882] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.991311] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.992116] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.992974] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.993782] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.994635] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.995423] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.997043] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.997866] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.998665] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52102.999460] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.000238] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.001067] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.001869] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.002661] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.003458] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.004237] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.005856] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.006667] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.007468] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.008248] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.009169] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.009966] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.010756] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.011537] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.012337] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.013291] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.014823] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.015637] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.016447] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.017263] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.018049] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.018843] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.019630] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.020445] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.021262] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.022057] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.027589] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.028422] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.029246] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.030044] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.030832] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.031622] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.032448] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.033308] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.034099] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.034906] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.036443] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.037266] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.038058] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.038845] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.039625] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.040438] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.041444] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.042237] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.043033] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.043809] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.045379] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.046182] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.046979] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.047773] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.048639] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.049446] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.050221] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.051017] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.051828] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.052684] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.054205] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.055014] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.055805] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.056733] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.057529] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.058323] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.059100] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.059886] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.060755] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.061549] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.063026] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.063836] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.064803] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.065600] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.066390] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.067183] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.067967] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.068902] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.069739] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.070545] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.072056] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.072910] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.073718] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.074525] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.075309] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.076098] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.077032] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.077835] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.078628] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.079437] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.080941] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.081747] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.082552] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.083349] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.084149] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.085017] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.085805] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.086609] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.087421] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.088206] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.089804] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.090614] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.091410] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.092194] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.093139] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.093942] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.094730] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.095522] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.096325] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.097159] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.102498] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.103320] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.104112] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.105057] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.105855] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.106649] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.107444] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.108237] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.109167] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.109979] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.111455] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.112266] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.113103] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.113914] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.114767] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.115588] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.116385] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.117344] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.118163] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.118951] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.120499] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.121334] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.122126] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.122913] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.123702] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.124524] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.125346] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.126138] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.126931] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.127732] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.129249] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.130066] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.130862] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.131654] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.132459] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.133267] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.134069] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.134858] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.135640] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.136461] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.137746] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.138548] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.139340] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.140123] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.140955] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.141766] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.142560] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.143352] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.144123] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.144943] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.146119] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.146916] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.147696] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.148524] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.149318] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.150095] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.150872] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.151654] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.152453] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.153394] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.154598] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.155401] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.156178] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.157241] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.158044] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.158841] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.159623] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.160439] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.161236] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.162030] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.163193] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.163991] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.164978] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.165776] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.166501] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.167287] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.168010] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.168773] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.169559] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:32 192.168.122.209 [52103.170280] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.755912] [tdb] ERROR: out of free space Apr 26 06:32:33 192.168.122.209 [52103.756346] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:32:33 192.168.122.209 [52103.756872] [tdb] ERROR: out of free space Apr 26 06:32:33 192.168.122.209 [52103.756947] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:32:33 192.168.122.209 [52103.757354] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab267e004f5 Apr 26 06:32:33 192.168.122.209 [52103.758373] [tdb] ERROR: out of free space Apr 26 06:32:33 192.168.122.209 [52103.758872] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:32:33 192.168.122.209 [52103.759464] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:32:33 192.168.122.209 [52103.760572] [tdb] ERROR: out of free space Apr 26 06:32:33 192.168.122.209 [52103.761269] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab274b0f701 Apr 26 06:32:33 192.168.122.209 [52103.891269] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.892175] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.893393] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.893508] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.893542] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.893546] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.893731] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.894178] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.894232] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.894573] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.894655] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.894698] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.895105] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.895171] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.895538] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.895609] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.895990] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.896055] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.896118] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.897365] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.898415] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.898528] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.898716] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.899092] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.899222] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.901516] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.902382] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.904718] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.905716] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.905825] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.906150] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.906184] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.908032] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.908832] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.909040] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.909220] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.909634] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.909988] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.910172] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.910345] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.925516] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.925651] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.926145] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.926190] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.926410] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.926488] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.926589] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.926673] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.926769] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.928467] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.932908] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.933373] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.933594] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.933962] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.934126] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.934485] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.934675] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.934702] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.935437] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.936527] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.936862] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.937154] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.937330] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.937703] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.937869] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.938629] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.939510] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.940048] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.940753] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.941456] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.942515] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.942660] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.943057] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.943341] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.943421] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.943497] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.943591] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.943670] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.943748] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.944964] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.949343] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.949755] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.949815] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.950018] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.950726] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.951815] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.952057] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.952069] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.952084] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.952259] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.952732] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.952741] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.953091] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.953149] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.953535] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.953555] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.953912] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.954090] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.954156] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.954242] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.973848] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.973918] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.974390] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.974443] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.974650] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.974790] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.975056] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.975089] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.975466] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.975521] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.975888] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.975926] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.976319] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.976345] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.977137] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.977165] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.977176] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.977537] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.977694] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.977794] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.977907] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.977998] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.990522] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.990601] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.991108] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.991181] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.991409] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.991435] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.991522] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.991613] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.991699] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.993413] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.994360] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.994776] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.994845] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.995034] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.995456] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.995475] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.995893] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.996148] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.996329] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.996642] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.996707] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.996864] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.997237] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.998117] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.998832] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52103.999607] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.000571] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.000691] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.001097] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.002057] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.002335] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.002340] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.002521] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.015143] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.015158] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.015646] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.015700] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.015863] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.015904] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.016329] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.016350] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.016793] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.016831] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.017188] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.017231] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.017625] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.017658] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.017845] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.018076] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.018109] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.018481] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.018538] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.018601] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.018680] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.018777] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.031710] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.031741] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.032332] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.032409] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.033291] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.033351] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.033881] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.034777] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.034939] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.034951] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.035089] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.035132] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.035410] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.035575] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.035940] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.036080] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.036094] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.036236] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.036318] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.036548] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.036709] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.036956] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.037534] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.038246] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.047931] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.047955] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.048186] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.048255] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.048450] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.048678] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.048764] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.048797] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.049080] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.049101] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.049402] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.049422] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.049712] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.049718] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.049990] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.050019] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.050329] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.050355] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.051025] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.051044] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.051047] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.051141] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.051350] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.051366] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.051642] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.051671] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.051964] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.051988] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.052268] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.052285] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.052613] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.052615] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.052898] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.052933] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.053261] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.053269] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.053621] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.054486] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.054621] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.054739] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.054807] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.054826] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.080328] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.080416] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.080627] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.080648] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.080793] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.081008] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.081031] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.081243] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.081263] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.081366] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.081450] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.081535] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:33 192.168.122.209 [52104.083299] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.682271] [tdb] ERROR: out of free space Apr 26 06:32:34 192.168.122.209 [52104.682608] [tdb] ERROR: out of free space Apr 26 06:32:34 192.168.122.209 [52104.682728] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:32:34 192.168.122.209 [52104.683151] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab2de3b65cb Apr 26 06:32:34 192.168.122.209 [52104.683735] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:32:34 192.168.122.209 [52104.686875] [tdb] ERROR: out of free space Apr 26 06:32:34 192.168.122.209 [52104.687263] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab23f00153c Apr 26 06:32:34 192.168.122.209 [52104.690038] [tdb] ERROR: out of free space Apr 26 06:32:34 192.168.122.209 [52104.690438] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab20af10120 Apr 26 06:32:34 192.168.122.209 [52104.803561] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.804629] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.804661] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.804751] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.804768] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.805010] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.805102] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.805182] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.805653] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.806139] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.806685] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.806759] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.807047] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.807669] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.807949] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.808614] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.810511] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.811114] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.812970] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.814279] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.814418] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.814577] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.814772] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.814881] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.814979] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.815653] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.815877] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.816103] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.817753] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.819380] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.819456] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.819690] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.819815] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.820959] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.821151] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.821465] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.821670] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.822097] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.822128] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.822662] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.822708] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.822956] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.823173] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.823215] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.823809] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.823877] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.823881] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.824306] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.824534] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.824540] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.849988] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.850945] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.852278] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.854095] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.855384] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.856688] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.857946] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.858989] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.859748] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.860538] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.862071] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.862125] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.862868] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.864314] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.865122] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.865923] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.866693] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.867485] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.868241] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.869697] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.869826] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.870525] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.872122] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.873066] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.873852] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.874638] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.875403] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.876182] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.877743] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.877848] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.878532] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.880281] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.881094] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.881863] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.882636] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.883390] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.884164] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.885679] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.885752] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.886493] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.888285] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.889161] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.889938] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.890710] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.891475] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.892241] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.893768] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.893847] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.894584] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.896967] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.897749] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.898507] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.899278] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.900043] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.900874] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.902292] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.902505] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.903079] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.905589] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.906364] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.907142] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.907917] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.908717] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.909488] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.915235] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.915496] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.916031] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.918534] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.919303] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.920064] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.920859] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.921659] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.922418] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.923820] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.924000] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.924651] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.927089] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.927875] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.928794] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.929568] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.930318] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.931095] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.932545] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.932647] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.933338] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.935820] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.936624] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.937387] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.938162] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.938926] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.939691] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.941108] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.941301] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.941894] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.944372] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.945381] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.946144] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.946904] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.947671] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.948459] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.949911] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.950032] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.950686] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.953282] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.954080] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.954844] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.955636] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.956392] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.957387] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.958827] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.959003] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.959619] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.962016] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.962786] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.963549] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.964305] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.965225] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.965985] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.967429] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.967596] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.968195] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.970671] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.971448] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.972199] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.973000] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.973770] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.974549] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.975980] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.976129] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.976817] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.979261] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.980043] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.980853] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.981641] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.982411] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.983174] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.984590] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.984752] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.985380] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.987890] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.988717] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.989491] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.990250] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.991028] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.991798] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.996913] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.997015] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52104.997702] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52105.000149] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52105.001344] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52105.002110] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52105.002871] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52105.003646] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52105.004416] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52105.005870] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52105.006067] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52105.006651] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52105.009213] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52105.009978] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52105.010756] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52105.011523] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52105.012292] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52105.013101] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52105.014373] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52105.014531] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52105.015143] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52105.017673] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52105.018438] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52105.019208] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52105.019973] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52105.020781] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52105.021551] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52105.022675] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52105.022840] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52105.023466] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52105.026017] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52105.026788] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52105.027551] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52105.028310] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52105.029122] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52105.029899] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52105.031051] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52105.031200] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52105.031833] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52105.034459] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52105.035212] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52105.035984] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52105.036784] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52105.037551] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52105.038314] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52105.039462] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52105.039644] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52105.040227] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52105.042658] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52105.043434] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52105.044189] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52105.044991] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52105.045757] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52105.046514] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52105.047650] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52105.047723] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52105.048398] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52105.051126] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52105.051897] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52105.052643] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:34 192.168.122.209 [52105.053360] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.602472] [tdb] ERROR: out of free space Apr 26 06:32:35 192.168.122.209 [52105.602742] [tdb] ERROR: out of free space Apr 26 06:32:35 192.168.122.209 [52105.602904] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:32:35 192.168.122.209 [52105.602910] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:32:35 192.168.122.209 [52105.603344] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab2e62a0a67 Apr 26 06:32:35 192.168.122.209 [52105.606945] [tdb] ERROR: out of free space Apr 26 06:32:35 192.168.122.209 [52105.607330] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab214418964 Apr 26 06:32:35 192.168.122.209 [52105.608280] [tdb] ERROR: out of free space Apr 26 06:32:35 192.168.122.209 [52105.608671] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab221b09d78 Apr 26 06:32:35 192.168.122.209 [52105.719331] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.720251] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.721254] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.722510] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.722524] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.724635] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.725315] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.725366] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.726397] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.727131] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.730285] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.730850] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.733137] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.734003] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.736405] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.736608] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.736961] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.741981] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.742011] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.742591] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.742682] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.742790] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.743017] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.743082] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.743477] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.743870] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.744043] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.744472] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.744546] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.744722] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.744924] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.749818] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.750112] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.751235] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.754586] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.755409] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.755451] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.755524] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.757613] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.757733] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.758278] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.758554] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.759347] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.759862] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.761383] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.761634] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.761964] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.762579] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.762796] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.763164] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.764348] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.764394] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.764595] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.765036] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.765740] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.766209] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.766893] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.771208] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.771980] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.773391] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.774158] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.774928] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.775774] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.776612] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.777401] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.778782] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.779560] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.780326] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.781168] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.781966] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.782745] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.783514] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.784274] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.785104] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.786599] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.787376] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.788150] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.789013] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.789790] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.790569] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.791320] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.792100] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.793065] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.794487] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.795264] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.796137] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.796950] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.797729] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.798497] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.799300] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.800067] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.800978] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.802386] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.803150] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.803935] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.804741] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.805513] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.806365] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.807153] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.807918] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.808764] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.810187] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.810966] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.811730] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.812532] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.813334] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.814120] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.814879] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.815646] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.816551] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.817986] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.818764] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.819524] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.820294] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.821211] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.821988] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.822771] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.823545] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.824301] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.826488] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.827359] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.828126] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.829039] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.829812] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.830574] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.831327] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.832102] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.832984] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.834427] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.835203] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.835994] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.836808] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.837655] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.838445] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.839236] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.839999] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.840808] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.842203] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.843000] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.843788] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.844645] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.845417] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.846169] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.846943] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.847781] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.848612] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.850018] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.850782] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.851556] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.852318] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.853265] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.854047] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.854812] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.855577] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.856331] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.857899] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.858665] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.859434] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.860195] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.861023] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.861801] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.862576] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.863350] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.864126] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.865596] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.866374] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.867147] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.867982] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.868791] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.869568] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.870347] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.871123] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.871889] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.873586] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.874381] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.875157] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.875920] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.876730] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.877496] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.878326] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.879126] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.879887] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.881389] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.882188] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.883021] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.883798] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.884602] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.885393] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.886161] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.886939] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.887707] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.889247] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.890061] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.890837] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.891608] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.892381] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.893285] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.894065] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.894842] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.895622] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.897043] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.897840] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.898727] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.899524] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.900293] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.901317] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.902094] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.902891] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.903666] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.905104] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.905921] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.906690] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.907468] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.908226] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.909345] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.910127] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.910902] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.911676] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.912881] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.913651] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.914419] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.915188] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.915962] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.916877] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.917967] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.918751] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.919526] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.920679] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.921448] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.922222] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.922998] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.923774] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.924583] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.925375] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.926146] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.926915] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.928020] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.928961] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.929727] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.930502] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.931267] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.932046] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.932844] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.933624] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.934390] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.935497] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.936258] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.937182] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.937960] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.938765] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.939553] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.940276] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.941023] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.941740] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.942853] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:35 192.168.122.209 [52105.943571] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.479201] [tdb] ERROR: out of free space Apr 26 06:32:36 192.168.122.209 [52106.479778] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:32:36 192.168.122.209 [52106.480589] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:32:36 192.168.122.209 [52106.484145] [tdb] ERROR: out of free space Apr 26 06:32:36 192.168.122.209 [52106.484565] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab268767b43 Apr 26 06:32:36 192.168.122.209 [52106.485447] [tdb] ERROR: out of free space Apr 26 06:32:36 192.168.122.209 [52106.485829] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab2afecec5c Apr 26 06:32:36 192.168.122.209 [52106.486781] [tdb] ERROR: out of free space Apr 26 06:32:36 192.168.122.209 [52106.487209] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab27b2688b7 Apr 26 06:32:36 192.168.122.209 [52106.597701] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.598681] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.599573] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.600483] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.602575] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.602588] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.602614] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.602671] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.602767] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.602848] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.604138] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.605735] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.606745] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.611419] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.611959] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.612438] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.612543] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.612657] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.612756] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.612864] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.613292] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.613657] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.614527] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.615601] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.617126] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.617664] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.618982] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.619037] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.619071] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.619259] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.619421] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.619635] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.619802] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.620497] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.621118] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.621397] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.621777] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.622323] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.623042] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.623619] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.624198] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.631509] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.633498] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.633715] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.633742] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.633765] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.633938] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.634045] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.634130] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.634255] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.634367] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.639572] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.644309] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.644500] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.644563] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.644568] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.644877] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.645121] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.645147] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.645321] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.645694] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.645891] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.646062] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.646385] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.647337] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.648240] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.648804] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.648813] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.649005] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.649161] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.649604] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.649740] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.649808] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.649854] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.650179] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.650234] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.650550] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.651162] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.651429] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.652337] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.652673] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.653849] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.654465] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.655261] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.655481] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.655644] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.666455] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.667538] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.667648] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.668466] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.668489] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.668492] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.670853] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.670904] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.671640] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.673259] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.674059] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.674772] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.675303] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.675328] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.675342] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.675460] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.675588] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.675596] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.675758] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.676135] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.676411] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.676579] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.676895] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.677399] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.677451] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.677776] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.678041] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.678464] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.678483] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.678671] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.678777] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.679369] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.680325] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.689610] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.689657] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.689702] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.690296] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.693757] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.693819] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.693914] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.693945] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.694140] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.694449] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.694613] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.694639] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.694816] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.695192] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.695428] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.695560] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.695872] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.696009] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.696503] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.696534] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.696617] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.697076] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.706123] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.706175] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.706339] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.706802] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.706845] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.709644] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.710556] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.710576] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.711330] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.713807] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.714912] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.715021] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.715671] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.715713] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.715767] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.718557] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.718692] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.719340] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.721939] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.722722] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.723441] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.723614] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.723780] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.723787] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.724142] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.724156] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.724187] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.727918] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.728744] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.729772] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.730876] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.730968] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.731004] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.731027] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.731200] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.731260] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.731378] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.731578] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.732296] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.732308] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.732336] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.732513] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.738530] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.739638] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.740593] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.740879] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.740906] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.740933] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.741114] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.741239] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.741289] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.741464] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.741755] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.741825] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.741962] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.742014] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.742417] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.742538] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.742541] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.742697] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.742855] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.743242] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.743269] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.743435] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.743888] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.747935] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.748033] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.748154] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.748770] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.749657] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.760591] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.761378] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.762454] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.762507] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.762976] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.762984] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.763180] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.763205] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.763367] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.763429] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.763804] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.764012] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.764683] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.764686] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.770699] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.771784] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.772040] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.772209] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.772234] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.772403] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.772582] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.772631] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.773225] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.773867] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.773928] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.774313] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.774626] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.774683] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.774967] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.775374] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.775783] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.776166] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.776680] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.776763] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.776789] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.777019] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.777397] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.777513] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.777659] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.779227] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.779985] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.780057] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.780164] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.780259] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52106.780300] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:36 192.168.122.209 [52107.367896] [tdb] ERROR: out of free space Apr 26 06:32:36 192.168.122.209 [52107.368631] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:32:36 192.168.122.209 [52107.369651] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:32:36 192.168.122.209 [52107.371678] [tdb] ERROR: out of free space Apr 26 06:32:36 192.168.122.209 [52107.372075] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:32:36 192.168.122.209 [52107.372712] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:32:36 192.168.122.209 [52107.376131] [tdb] ERROR: out of free space Apr 26 06:32:36 192.168.122.209 [52107.376570] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:32:36 192.168.122.209 [52107.377157] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:32:36 192.168.122.209 [52107.378785] [tdb] ERROR: out of free space Apr 26 06:32:36 192.168.122.209 [52107.379193] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab2506714ef Apr 26 06:32:37 192.168.122.209 [52107.499855] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.500724] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.505329] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.506122] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.506211] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.506263] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.506965] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.507131] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.507487] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.507899] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.508227] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.508596] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.508995] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.509112] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.509289] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.509864] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.510883] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.511352] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.512231] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.512756] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.513803] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.513834] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.514016] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.514662] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.515429] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.516022] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.516828] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.517409] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.518044] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.518688] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.525611] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.526077] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.526471] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.527587] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.527759] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.527822] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.528123] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.528283] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.528451] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.528805] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.528902] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.529823] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.530092] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.530710] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.531310] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.531535] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.531885] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.532513] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.533636] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.534577] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.534923] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.535943] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.536154] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.536998] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.540535] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.541258] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.542048] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.542103] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.542528] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.542748] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.542954] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.543352] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.543955] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.544544] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.545659] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.545756] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.546410] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.547010] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.547369] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.547626] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.549023] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.551890] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.552718] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.552761] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.553189] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.553436] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.553460] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.553788] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.554041] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.554095] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.554415] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.554638] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.554720] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.555025] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.555250] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.555324] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.555668] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.555852] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.555957] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.556259] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.557695] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.558278] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.559355] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.559460] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.560092] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.561155] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.561308] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.562446] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.568702] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.568791] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.569399] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.570281] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.570603] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.571691] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.572559] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.572756] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.573070] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.573262] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.573602] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.573872] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.573875] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.573954] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.574029] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.574698] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.575615] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.580274] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.581121] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.581151] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.581624] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.581819] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.581868] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.582142] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.582469] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.582661] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.582760] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.583057] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.583229] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.583353] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.583634] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.583936] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.583996] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.584617] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.585871] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.592215] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.596909] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.597721] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.597751] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.598173] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.598468] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.598480] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.598560] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.598627] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.599048] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.599998] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.600249] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.601694] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.604617] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.604681] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.605313] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.606493] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.606520] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.607289] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.607571] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.607784] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.607983] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.608289] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.608387] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.608733] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.609010] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.609065] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.609378] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.609608] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.609694] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.609996] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.610311] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.616655] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.618055] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.618869] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.618971] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.619088] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.619347] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.619583] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.619604] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.619844] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.620055] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.620194] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.620271] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.620531] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.620792] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.620968] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.621269] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.621394] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.621605] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.621903] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.622004] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.622201] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.622513] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.623195] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.624145] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.632622] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.633408] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.633662] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.634112] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.635072] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.635335] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.636153] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.636156] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.636381] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.636628] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.637439] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.638198] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.638395] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.638666] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.638835] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.638874] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.639087] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.639309] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.639429] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.639540] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.639748] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.639976] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.640197] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.640243] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.640842] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.641883] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.649481] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.650568] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.651378] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.651428] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.651661] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.651908] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.652069] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.652126] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.652347] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.652605] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.652859] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.652867] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.652954] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.653041] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.653438] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.654289] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.664703] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.665560] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.665587] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.665795] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.666031] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.666275] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.666278] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.666515] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.666743] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.666956] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.667168] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.667389] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.667606] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.667748] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.667869] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.667988] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.668295] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.669119] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.677061] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.677898] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.677950] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.678083] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.678544] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.680330] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52107.684402] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52108.301214] [tdb] ERROR: out of free space Apr 26 06:32:37 192.168.122.209 [52108.301961] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:32:37 192.168.122.209 [52108.303015] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:32:37 192.168.122.209 [52108.304759] [tdb] ERROR: out of free space Apr 26 06:32:37 192.168.122.209 [52108.305455] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:32:37 192.168.122.209 [52108.306483] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:32:37 192.168.122.209 [52108.309147] [tdb] ERROR: out of free space Apr 26 06:32:37 192.168.122.209 [52108.309571] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab23ef543f3 Apr 26 06:32:37 192.168.122.209 [52108.324042] [tdb] ERROR: out of free space Apr 26 06:32:37 192.168.122.209 [52108.324609] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab20b0457ef Apr 26 06:32:37 192.168.122.209 [52108.439277] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52108.440183] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52108.441175] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52108.442041] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52108.443324] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52108.443335] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52108.443392] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52108.443603] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52108.443800] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52108.444005] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52108.444565] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52108.444721] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52108.444985] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52108.445189] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52108.445383] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52108.445803] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52108.445956] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52108.446143] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52108.446322] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52108.446502] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52108.446997] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52108.447191] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52108.447380] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:37 192.168.122.209 [52108.448882] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.449724] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.450883] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.451974] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.453052] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.453607] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.455280] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.456358] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.456391] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.456519] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.467885] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.469293] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.469344] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.470460] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.471693] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.471872] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.472046] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.472259] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.472398] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.473310] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.474428] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.474906] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.475604] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.476645] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.477512] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.478995] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.479615] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.484542] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.485523] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.486876] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.486879] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.486969] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.487309] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.487539] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.487699] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.487858] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.488389] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.488393] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.488606] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.488770] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.488953] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.488955] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.489507] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.489681] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.489840] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.490021] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.490649] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.490661] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.490843] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.490851] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.492190] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.493278] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.493315] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.493491] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.494016] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.494685] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.495403] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.506905] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.507677] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.509239] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.509263] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.509792] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.509993] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.510163] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.510295] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.510352] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.510823] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.510985] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.511099] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.511154] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.511321] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.511812] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.511982] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.512855] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.513574] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.514256] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.514997] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.522682] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.522722] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.523207] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.523436] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.523594] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.523776] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.523999] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.524249] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.524418] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.524591] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.524635] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.524812] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.525324] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.525491] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.525652] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.525839] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.526363] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.527508] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.527565] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.527679] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.528171] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.528897] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.538017] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.538071] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.538455] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.538671] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.538805] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.538842] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.539007] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.539496] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.539650] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.539811] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.539955] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.540435] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.540648] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.540759] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.541336] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.542048] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.542622] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.543304] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.551109] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.551212] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.551693] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.551842] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.551876] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.552026] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.552171] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.552700] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.552872] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.553038] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.553210] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.553755] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.553836] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.554356] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.555071] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.555568] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.556259] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.563138] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.564454] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.564619] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.565063] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.565162] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.565252] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.565422] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.565572] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.566053] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.566207] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.566368] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.566522] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.566982] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.567119] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.567656] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.568395] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.569026] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.570114] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.577308] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.578710] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.578732] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.579162] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.579341] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.579518] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.579671] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.580133] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.580295] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.580487] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.580645] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.580752] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.581416] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.585194] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.585237] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.585415] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.585718] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.586435] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.587042] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.588180] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.588219] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.589178] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.591009] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.592052] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.592068] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.592145] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.598988] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.600361] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.600426] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.600842] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.601005] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.601166] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.601355] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.601358] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.601705] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.601855] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.602006] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.602158] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.602480] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.602585] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.603367] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.604075] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.604810] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.605517] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.612567] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.613752] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.613781] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.614052] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.614209] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.614364] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.614456] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.614534] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.614845] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.615000] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.615147] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.615300] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.615623] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.615780] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.615940] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.616035] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.616567] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.617717] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.617877] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.618842] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.618956] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.619135] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.619795] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.630354] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.630359] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.630463] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.630562] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.630757] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.630905] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.631001] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.631271] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.631446] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.631613] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.631708] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.632414] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.633149] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52108.641795] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.189296] [tdb] ERROR: out of free space Apr 26 06:32:38 192.168.122.209 [52109.189730] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:32:38 192.168.122.209 [52109.190341] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:32:38 192.168.122.209 [52109.190885] [tdb] ERROR: out of free space Apr 26 06:32:38 192.168.122.209 [52109.191237] [tdb] ERROR: out of free space Apr 26 06:32:38 192.168.122.209 [52109.191306] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab2d22e48b4 Apr 26 06:32:38 192.168.122.209 [52109.191708] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab2f48faf5c Apr 26 06:32:38 192.168.122.209 [52109.191988] [tdb] ERROR: out of free space Apr 26 06:32:38 192.168.122.209 [52109.193353] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab22045cbb7 Apr 26 06:32:38 192.168.122.209 [52109.306718] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.307741] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.307772] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.307794] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.307961] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.308119] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.308281] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.308477] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.310485] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.310990] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.311161] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.311684] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.311871] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.312588] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.313233] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.314000] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.314356] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.314543] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.315500] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.325138] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.329869] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.331328] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.332186] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.333188] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.333201] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.333251] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.333372] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.333496] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.333604] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.333711] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.333866] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.333915] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.339370] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.341321] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.342147] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.342358] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.342452] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.342484] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.342618] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.342769] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.342864] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.343220] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.343593] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.343947] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.344298] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.344705] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.344954] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.345416] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.345896] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.346031] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.346166] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.346359] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.346468] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.347394] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.357199] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.357317] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.357835] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.357904] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.359463] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.360122] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.360173] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.361540] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.362582] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.363597] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.364477] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.365785] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.366592] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.367828] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.367839] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.368909] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.368928] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.368945] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.369120] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.369567] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.369658] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.369680] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.369834] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.369979] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.370412] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.370445] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.371143] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.371147] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.371193] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.371242] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.371840] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.371871] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.371900] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.372062] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.372511] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.372557] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.373228] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.373939] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.385281] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.385302] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.385309] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.385599] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.385652] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.385807] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.385839] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.385986] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.386132] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.386303] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.395895] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.395981] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.396392] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.396425] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.396810] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.396828] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.396975] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.397119] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.397264] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.397494] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.397951] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.398272] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.398438] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.398533] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.398588] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.398975] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.399116] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.399523] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.408023] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.408832] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.410214] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.410225] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.410557] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.410583] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.410747] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.410763] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.410915] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.411074] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.411213] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.411426] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.422946] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.422959] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.423163] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.423196] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.423346] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.423379] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.423534] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.423679] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.423838] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.424050] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.424458] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.424536] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.425113] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.425125] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.425278] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.425735] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.425740] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.426144] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.426170] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.426627] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.426762] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.426805] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.427174] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.427320] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.427698] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.427842] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.428175] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.441977] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.443600] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.443647] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.443677] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.443722] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.444291] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.444447] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.444608] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.444767] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.444970] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.445500] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.446723] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.446744] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.446901] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.447055] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.447199] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.447356] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.454885] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.456023] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.456134] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.456568] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.456597] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.456770] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.456782] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:38 192.168.122.209 [52109.456936] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.457104] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.462837] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.463622] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.464931] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.464988] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.465247] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.465278] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.465451] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.465487] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.465643] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.465788] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.465933] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.472332] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.473639] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.473682] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.473760] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.473782] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.473946] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.473962] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.474103] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.474243] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.474399] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.474598] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.474890] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.475083] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.475231] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.475360] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.475727] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.475734] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.476058] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.476069] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.476401] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.476409] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.476754] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.476765] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.477448] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.478436] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.478443] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.491213] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.491465] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.491496] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.491548] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.491874] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.492528] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.493236] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.495592] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.496362] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.497437] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.498486] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.498654] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.498814] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.498830] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.499000] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.499020] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.499169] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.504277] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.505089] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.505854] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.506913] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.506961] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.507202] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.507226] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.507389] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.507418] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.507580] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.507737] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.507890] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.514028] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.515029] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.515126] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.515322] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52109.515405] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.052425] [tdb] ERROR: out of free space Apr 26 06:32:39 192.168.122.209 [52110.052843] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:32:39 192.168.122.209 [52110.052849] [tdb] ERROR: out of free space Apr 26 06:32:39 192.168.122.209 [52110.053449] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:32:39 192.168.122.209 [52110.053860] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab28833c5f3 Apr 26 06:32:39 192.168.122.209 [52110.054729] [tdb] ERROR: out of free space Apr 26 06:32:39 192.168.122.209 [52110.055256] [tdb] ERROR: out of free space Apr 26 06:32:39 192.168.122.209 [52110.055417] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab29b633607 Apr 26 06:32:39 192.168.122.209 [52110.055795] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab27a5846f0 Apr 26 06:32:39 192.168.122.209 [52110.165954] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.166938] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.167828] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.169086] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.169909] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.170704] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.171924] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.171945] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.172756] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.173743] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.175326] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.175557] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.177522] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.178864] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.179744] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.180560] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.181378] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.185701] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.185731] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.187177] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.187218] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.187342] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.187942] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.187946] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.188306] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.188683] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.189056] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.189399] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.189728] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.189799] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.189885] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.189967] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.190042] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.190117] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.191045] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.191760] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.192459] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.193126] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.193831] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.202820] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.203606] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.204901] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.204932] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.206437] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.206504] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.206865] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.207018] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.207140] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.207211] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.207364] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.207528] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.208117] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.208275] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.208441] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.208624] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.208791] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.208959] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.216931] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.216961] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.218668] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.218717] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.218746] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.220732] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.222055] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.222085] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.223614] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.223717] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.223757] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.225690] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.227016] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.227027] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.228534] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.228624] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.228668] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.230758] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.232078] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.232105] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.233764] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.233846] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.233870] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.235780] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.237343] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.237385] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.239153] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.239186] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.239206] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.241444] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.246176] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.246205] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.247927] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.247989] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.248009] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.250456] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.251777] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.251812] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.253314] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.254513] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.254546] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.254565] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.257091] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.257135] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.258773] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.258832] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.258858] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.260843] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.262169] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.262197] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.263903] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.263952] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.263973] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.265992] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.267310] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.267333] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.268850] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.269917] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.269995] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.270014] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.272457] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.272519] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.274202] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.274253] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.274272] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.276253] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.277729] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.277756] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.279499] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.279532] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.279559] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.281729] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.283017] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.283040] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.284691] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.284752] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.284796] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.286713] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.287951] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.287982] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.289823] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.289855] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.289871] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.291822] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.293111] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.293133] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.294809] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.294863] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.294883] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.297089] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.298417] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.298447] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.300180] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.300232] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.300250] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.302188] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.303467] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.303488] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.304969] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.306148] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.307071] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.307109] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.307532] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.307704] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.307781] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.311651] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.312453] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.313270] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.314615] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.314650] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.316238] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.317253] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.318106] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.318125] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.318568] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.318717] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.318914] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.319070] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.319642] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.320343] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.324066] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.324090] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.325767] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.325782] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.325799] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.326005] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.326657] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.326790] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.327443] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.328130] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.331914] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.332965] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.334265] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.334293] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.335966] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.335996] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.336008] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.338025] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.339353] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.339378] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.341029] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.342128] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.342166] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.342181] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.344701] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.344738] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.346532] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.346541] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.346548] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.346763] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.347475] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.347518] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.347698] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.347898] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.348056] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.348525] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.348707] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.348855] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.349540] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.350238] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.356297] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.357278] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.358401] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.358434] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.360083] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.360157] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.360181] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.362135] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.363263] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.363281] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.364911] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.366032] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.366089] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.366114] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.372461] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.372518] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.374184] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.374239] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.374264] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.376217] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.377377] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.377403] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.379044] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.379136] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.379156] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.381124] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.382246] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.382271] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.383924] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.383981] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.384013] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.385983] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.387088] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.387116] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.388444] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.388472] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.388633] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.390494] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:39 192.168.122.209 [52110.391598] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.023424] [tdb] ERROR: out of free space Apr 26 06:32:40 192.168.122.209 [52111.023430] [tdb] ERROR: out of free space Apr 26 06:32:40 192.168.122.209 [52111.023452] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:32:40 192.168.122.209 [52111.023852] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:32:40 192.168.122.209 [52111.024139] [tdb] ERROR: out of free space Apr 26 06:32:40 192.168.122.209 [52111.024143] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab264e8ceb4 Apr 26 06:32:40 192.168.122.209 [52111.024277] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:32:40 192.168.122.209 [52111.027012] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:32:40 192.168.122.209 [52111.030868] [tdb] ERROR: out of free space Apr 26 06:32:40 192.168.122.209 [52111.031523] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:32:40 192.168.122.209 [52111.032109] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:32:40 192.168.122.209 [52111.145385] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.145401] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.145454] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.145549] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.145642] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.145695] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.145876] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.146088] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.146477] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.146690] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.146707] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.146905] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.147100] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.147133] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.148028] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.150313] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.150358] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.151212] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.151235] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.151831] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.151926] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.151946] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.152330] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.152915] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.153412] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.155169] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.157598] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.159269] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.159307] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.159393] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.159499] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.169965] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.172431] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.172552] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.172583] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.175518] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.176935] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.178255] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.179927] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.179981] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.179987] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.180361] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.180796] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.180975] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.181169] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.181599] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.181767] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.181942] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.182078] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.182469] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.183178] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.190078] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.190119] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.190128] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.193092] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.193149] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.193152] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.196234] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.196487] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.196499] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.196522] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.197032] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.197435] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.197608] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.197828] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.197839] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.198247] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.198371] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.198438] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.198600] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.199061] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.199162] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.199214] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.199663] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.199766] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.208908] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.209696] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.211246] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.211253] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.211259] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.214189] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.214205] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.214209] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.214616] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.215328] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.215950] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.216950] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.218430] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.220531] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.220633] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.221563] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.221613] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.221617] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.222167] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.222455] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.222461] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.222932] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.223178] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.223182] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.223749] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.224850] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.224864] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.224978] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.225122] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.225388] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.225573] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.225647] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.233583] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.235058] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.235072] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.235086] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.237821] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.237888] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.237892] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.238229] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.238425] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.238553] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.238604] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.238767] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.239221] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.239241] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.239767] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.240485] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.245767] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.247308] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.247320] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.247326] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.250070] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.250130] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.250138] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.252108] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.252214] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.252340] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.252591] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.253010] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.253044] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.253205] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.253365] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.253651] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.253810] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.253972] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.254143] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.254392] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.254579] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.254752] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.254913] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.263330] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.263351] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.263355] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.265946] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.266050] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.266056] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.268090] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.268119] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.268240] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.268485] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.268826] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.268934] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.269106] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.269267] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.269464] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.270051] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.274180] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.275122] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.275149] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.275395] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.275463] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.275841] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.276037] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.276082] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.276121] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.276243] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.276417] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.276866] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.276905] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.277090] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.277548] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.277564] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.277771] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.287181] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.287186] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.287197] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.288462] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.288649] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.288720] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.288877] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.289051] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.289161] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.289738] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.290824] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.290973] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.291858] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.292138] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.292142] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.297992] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.298787] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.299215] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.299218] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.299523] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.299853] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.299978] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.300073] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.300140] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.300223] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.304450] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.305750] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.305818] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.305822] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.308402] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.308431] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.308437] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.310676] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.310683] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.310775] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.310820] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.311108] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.311334] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.311387] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.311483] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.312011] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.312935] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.317472] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.317542] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.317548] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.320142] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.320169] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.320173] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.322210] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.322304] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.322450] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.322538] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.322852] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.322971] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.323074] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.323251] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.323579] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.323614] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.324439] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.325299] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.330245] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.331630] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.331642] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.331662] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.334299] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.334360] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.334364] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.336373] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.336561] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.336584] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.336658] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.337140] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.341541] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.341598] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.341647] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.343876] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:40 192.168.122.209 [52111.343904] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52111.962070] [tdb] ERROR: out of free space Apr 26 06:32:41 192.168.122.209 [52111.962495] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:32:41 192.168.122.209 [52111.963071] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:32:41 192.168.122.209 [52111.966256] [tdb] ERROR: out of free space Apr 26 06:32:41 192.168.122.209 [52111.966701] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab2a6f04d0c Apr 26 06:32:41 192.168.122.209 [52111.967809] [tdb] ERROR: out of free space Apr 26 06:32:41 192.168.122.209 [52111.968196] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab2cde00eb7 Apr 26 06:32:41 192.168.122.209 [52111.969223] [tdb] ERROR: out of free space Apr 26 06:32:41 192.168.122.209 [52111.969609] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab2f8111aab Apr 26 06:32:41 192.168.122.209 [52112.084610] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.085539] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.086426] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.087313] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.088186] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.089112] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.089989] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.090861] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.091731] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.093610] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.093620] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.094554] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.097214] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.098020] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.098826] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.099632] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.100428] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.101250] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.102057] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.103465] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.103472] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.104262] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.105888] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.106689] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.107482] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.108272] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.109172] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.109958] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.111412] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.112570] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.113571] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.116136] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.116994] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.117107] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.117119] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.117164] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.119601] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.120072] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.120296] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.121055] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.122232] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.123023] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.124495] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.124550] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.126100] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.126887] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.127663] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.128434] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.129546] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.130318] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.131724] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.131743] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.133172] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.133961] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.134744] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.135528] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.136314] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.137248] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.138033] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.139472] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.139506] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.140907] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.141713] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.142486] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.143269] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.144062] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.144907] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.145690] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.147105] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.147128] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.148531] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.149318] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.150105] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.150893] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.151669] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.152455] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.153425] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.154845] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.154862] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.156260] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.157175] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.157948] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.158731] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.159513] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.160280] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.161096] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.162492] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.162542] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.163939] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.165384] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.166161] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.166931] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.167714] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.168494] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.169411] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.170882] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.170906] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.172302] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.173129] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.173903] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.174678] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.175444] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.176270] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.177183] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.178597] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.178629] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.180034] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.180847] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.181648] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.182429] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.183193] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.183967] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.184783] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.186191] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.186214] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.187595] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.188360] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.189320] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.190098] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.190886] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.191665] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.192447] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.193928] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.193966] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.195356] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.196125] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.197128] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.197920] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.198705] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.199493] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.200264] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.201952] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.201981] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.203343] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.204110] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.204922] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.205699] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.206458] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.207228] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.207999] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.209465] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.209496] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.210851] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.211620] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.212376] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.213198] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.213976] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.214761] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.215524] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.217113] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.217134] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.218515] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.219301] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.220073] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.220875] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.221649] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.222444] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.223210] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.224598] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.224645] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.226007] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.226812] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.227586] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.228357] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.229373] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.230159] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.230943] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.232333] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.232358] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.233938] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.234714] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.235478] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.236246] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.237049] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.237842] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.238625] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.240043] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.240065] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.241476] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.242252] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.243017] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.243790] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.244586] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.245378] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.246151] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.247599] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.247605] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.249125] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.249916] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.250689] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.251473] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.252249] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.253207] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.253994] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.255394] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.255410] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.256849] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.257635] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.258397] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.259171] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.259929] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.260740] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.261508] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.266964] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.266990] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.268379] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.269193] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.269975] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.270747] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.271518] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.272300] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.273116] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.274553] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.274580] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.275953] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.276984] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.277775] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.278564] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.279330] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.280113] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.281137] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.282546] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.282587] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.283947] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.284763] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.285549] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.286311] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.287080] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.287860] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.288655] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.289804] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.289824] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.291216] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.291992] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.292809] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.293602] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.294369] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.295156] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.295929] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.297133] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.297159] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.298544] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.299316] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.300082] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.300975] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.301758] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.302536] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.303305] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.304360] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.304384] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.305734] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.306507] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.307264] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.308049] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.308934] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:41 192.168.122.209 [52112.309717] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52112.856099] [tdb] ERROR: out of free space Apr 26 06:32:42 192.168.122.209 [52112.856570] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:32:42 192.168.122.209 [52112.857173] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:32:42 192.168.122.209 [52112.858218] [tdb] ERROR: out of free space Apr 26 06:32:42 192.168.122.209 [52112.858297] [tdb] ERROR: out of free space Apr 26 06:32:42 192.168.122.209 [52112.858649] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab214ca11ec Apr 26 06:32:42 192.168.122.209 [52112.859058] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:32:42 192.168.122.209 [52112.860293] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:32:42 192.168.122.209 [52112.860568] [tdb] ERROR: out of free space Apr 26 06:32:42 192.168.122.209 [52112.861371] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab2d35086f3 Apr 26 06:32:42 192.168.122.209 [52112.982115] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52112.982234] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52112.982967] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52112.983061] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52112.984507] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52112.985234] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52112.988323] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52112.988357] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52112.989169] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52112.989253] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52112.989575] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52112.989601] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52112.990208] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52112.990350] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52112.990393] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52112.994717] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52112.995502] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52112.996644] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52112.997186] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52112.999017] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.000081] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.000133] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.000176] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.000882] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.003568] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.003614] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.004746] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.005133] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.005347] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.005497] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.005959] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.007757] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.009405] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.009806] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.010361] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.010888] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.011252] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.011404] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.011808] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.018363] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.019026] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.020268] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.020949] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.021978] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.023161] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.023193] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.023205] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.023925] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.026535] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.027409] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.027443] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.028496] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.028582] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.031258] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.031339] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.032154] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.032211] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.033242] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.033959] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.036277] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.036670] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.036702] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.038696] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.040032] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.040085] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.041048] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.043065] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.043074] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.043079] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.045500] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.046693] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.046717] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.048367] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.048378] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.048843] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.048993] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.049132] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.049302] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.049475] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.049667] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.049872] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.050131] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.050289] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.050438] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.057613] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.057633] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.059089] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.059587] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.059602] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.059781] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.059913] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.060100] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.060491] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.060594] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.060953] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.061021] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.066537] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.067724] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.067766] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.068595] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.069048] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.071019] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.071092] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.071781] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.073245] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.074126] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.074166] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.075182] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.075250] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.078393] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.078458] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.079289] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.079349] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.079824] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.080485] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.082543] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.082563] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.083604] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.083618] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.084233] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.084403] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.084634] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.084868] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.084924] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.085437] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.086119] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.090742] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.090794] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.091619] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.092099] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.093968] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.094774] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.094828] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.095527] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.096864] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.097705] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.098010] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.098045] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.098669] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.098844] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.098984] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.099198] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.099209] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.099705] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.100408] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.104276] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.104887] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.106244] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.106268] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.106297] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.108207] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.109106] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.109146] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.109879] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.110209] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.110631] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.110838] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.110865] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.111020] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.111146] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.111319] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.111522] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.111691] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.118144] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.118761] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.119819] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.119888] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.119936] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.121918] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.122676] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.123450] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.123627] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.124218] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.124459] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.124991] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.125203] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.125221] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.125377] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.125545] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.125707] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.125893] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.126097] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.132607] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.133312] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.134456] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.134497] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.134536] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.136438] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.137375] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.138283] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.138332] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.139066] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.139397] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.139816] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.140036] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.140048] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.140199] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.140331] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.140504] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.140718] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.140997] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.141087] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.141238] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.141508] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.150480] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.150777] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.152779] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.152786] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.152792] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.154783] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.155662] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.155681] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.156449] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.156563] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.157207] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.157212] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.157493] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.157502] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.157659] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.157805] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.158106] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.158171] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.168335] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.168470] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.169275] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.171910] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.172059] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.172069] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.172720] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.175692] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.175753] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.176480] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.176988] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.177191] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.177446] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.177451] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.177602] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.177736] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.177912] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.178010] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.178271] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.178975] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.178995] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.179004] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.179265] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.179527] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.180011] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.189364] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.190157] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.190922] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.191903] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.191962] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.192658] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.194584] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.194658] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:42 192.168.122.209 [52113.195341] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.774913] [tdb] ERROR: out of free space Apr 26 06:32:43 192.168.122.209 [52113.774917] [tdb] ERROR: out of free space Apr 26 06:32:43 192.168.122.209 [52113.774934] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:32:43 192.168.122.209 [52113.775351] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:32:43 192.168.122.209 [52113.775785] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:32:43 192.168.122.209 [52113.776363] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:32:43 192.168.122.209 [52113.778358] [tdb] ERROR: out of free space Apr 26 06:32:43 192.168.122.209 [52113.778758] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:32:43 192.168.122.209 [52113.779483] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:32:43 192.168.122.209 [52113.781257] [tdb] ERROR: out of free space Apr 26 06:32:43 192.168.122.209 [52113.781969] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab2be418326 Apr 26 06:32:43 192.168.122.209 [52113.914460] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.915455] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.916359] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.917504] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.918348] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.919193] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.920582] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.920640] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.920650] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.922672] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.923453] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.925146] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.925846] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.929053] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.929861] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.930672] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.932663] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.932673] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.932679] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.932823] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.933607] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.934643] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.935774] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.938474] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.939289] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.940097] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.941091] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.941928] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.943492] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.943548] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.943613] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.944405] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.945169] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.945822] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.950545] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.950649] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.950753] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.951390] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.952140] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.952770] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.954122] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.955611] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.956420] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.957283] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.958090] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.958955] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.960313] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.960407] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.960568] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.961081] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.961849] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.962354] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.963612] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.965301] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.966275] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.967193] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.968116] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.969049] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.970749] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.970884] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.971151] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.971602] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.972427] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.972985] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.974249] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.976006] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.977381] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.978482] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.979472] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.980465] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.982428] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.982615] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.982752] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.983319] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.984214] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.984786] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.986415] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.987826] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.989046] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.989984] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.991017] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.992124] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.994302] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.994400] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.994612] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.995194] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.995989] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.996495] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.997957] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52113.999266] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.000077] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.000915] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.001717] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.002530] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.004082] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.004141] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.004210] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.004858] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.005604] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.006056] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.007259] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.008640] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.009632] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.010447] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.011236] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.012032] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.013499] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.013703] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.013714] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.014221] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.014941] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.015416] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.020792] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.020943] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.020959] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.021193] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.021525] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.021853] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.022043] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.022232] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.022421] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.022615] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.022812] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.023453] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.023954] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.024705] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.030953] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.031784] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.032612] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.033459] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.034842] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.034956] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.035074] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.035623] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.036391] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.036891] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.038129] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.039466] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.040260] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.041115] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.041954] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.042759] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.044224] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.044306] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.044365] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.044991] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.045780] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.046204] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.047376] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.048755] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.049581] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.050385] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.051209] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.052013] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.053722] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.053897] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.053930] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.054469] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.055231] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.055664] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.056871] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.058206] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.059026] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.059879] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.060763] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.061613] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.063311] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.063404] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.063467] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.064063] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.064933] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.065364] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.066659] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.067990] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.068880] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.069719] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.070557] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.071416] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.073082] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.073269] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.073300] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.073835] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.074686] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.075087] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.076392] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.077778] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.078651] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.079549] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.080388] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.081293] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.086954] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.087074] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.087122] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.087697] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.088575] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.089025] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.090223] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.091908] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.092838] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.093681] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.094536] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.095385] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.097336] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.097478] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.097558] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.098352] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.099144] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.099814] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.101120] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.102731] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.103626] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.104484] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.105602] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.106452] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.108134] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.108187] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.108258] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.109020] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.109832] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.110294] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.111339] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.113178] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.114032] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.114897] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.115747] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.116641] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.117811] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.117967] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.118006] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.118541] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.119343] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.119817] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.120862] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.122479] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.123331] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.124170] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.125054] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.125893] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.127267] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.127313] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.127376] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.128004] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.128863] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.129301] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.130330] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.132046] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.132932] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.133787] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.134618] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.135514] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.136734] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.136752] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.136894] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.137473] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.137994] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:43 192.168.122.209 [52114.139824] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.715978] [tdb] ERROR: out of free space Apr 26 06:32:44 192.168.122.209 [52114.716361] [tdb] ERROR: out of free space Apr 26 06:32:44 192.168.122.209 [52114.716403] [tempesta fw] ERROR: Cache: cannot copy chunk of HTTP body Apr 26 06:32:44 192.168.122.209 [52114.716800] [tdb] ERROR: out of free space Apr 26 06:32:44 192.168.122.209 [52114.716812] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab28650ec8a Apr 26 06:32:44 192.168.122.209 [52114.716849] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab295001f7e Apr 26 06:32:44 192.168.122.209 [52114.717133] [tdb] ERROR: out of free space Apr 26 06:32:44 192.168.122.209 [52114.717464] [tempesta fw] ERROR: Cache: cannot copy HTTP body Apr 26 06:32:44 192.168.122.209 [52114.717888] [tdb] ERROR: Cannot allocate db entry for key=0xc288cab2676b9c7d Apr 26 06:32:44 192.168.122.209 [52114.845162] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.846013] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.846857] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.846996] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.847682] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.847687] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.847887] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.847990] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.848187] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.849078] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.849264] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.849441] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.849685] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.850053] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.850159] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.850363] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.850694] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.851116] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.851595] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.852110] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.852823] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.861661] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.862342] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.863032] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.864329] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.866059] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.866899] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.867686] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.868493] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.868636] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.869317] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.871605] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.871663] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.872383] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.872676] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.872707] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.873158] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.873408] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.874024] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.874061] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.874150] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.874235] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.874321] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.875023] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.881387] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.882163] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.883511] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.884306] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.885242] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.886008] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.886797] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.887037] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.888000] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.888909] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.889608] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.891195] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.891960] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.892844] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.897692] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.898491] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.899287] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.899472] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.900209] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.900547] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.901206] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.901350] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.901494] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.901631] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.902193] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.907429] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.908194] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.909128] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.910358] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.911123] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.911907] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.912086] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.912745] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.912791] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.916166] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.917083] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.917850] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.918855] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.919179] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.921554] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.922321] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.923080] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.923876] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.924007] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.924688] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.925019] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.925164] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.925430] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.925755] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.925903] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.926250] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.926319] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.926505] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.926729] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.927358] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.927846] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.928203] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.934768] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.935455] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.936129] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.937243] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.938603] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.939372] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.940168] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.940342] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.940979] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.943527] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.943538] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.945081] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.945849] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.946180] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.947282] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.948049] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.949415] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.950218] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.950983] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.951773] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.951969] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.952594] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.952640] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.955934] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.957187] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.957990] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.958797] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.958969] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.959599] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.959976] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.960136] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.960289] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.960436] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.960616] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.961182] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.961347] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.966408] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.967183] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.967941] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.969160] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.969925] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.970711] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.970843] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.971575] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.971928] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.972083] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.972225] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.972361] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.972505] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.973234] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.977322] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.978097] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.978875] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.979640] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.980795] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.981568] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.982350] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.982544] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.983598] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.985847] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.986612] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.987366] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.988160] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.988212] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.989365] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.990314] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.991075] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.991867] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.992045] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.993278] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.995120] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.995900] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.996693] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.997477] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.998685] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52114.999501] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.000283] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.000485] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.001159] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.003673] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.004046] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.005924] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.006695] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.007503] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.007618] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.008808] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.010406] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.011168] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.011968] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.012065] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.013200] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.014921] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.015687] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.016479] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.016683] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.017870] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.019291] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.020050] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.020864] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.021667] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.021730] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.026830] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.027619] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.028392] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.029211] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.030342] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.031137] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.031921] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.032731] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.033535] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.033726] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.034360] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.034420] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.037716] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.038496] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.039298] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.039519] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.040237] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.040305] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.040472] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.040630] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.040860] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.041007] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.041359] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.041513] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.041659] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.041833] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.049556] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.050358] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.051129] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.051922] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.052062] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.052935] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.054686] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.055447] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.056246] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.056375] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.057129] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.059529] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.060321] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.061125] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.061891] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.062954] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.063732] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.064602] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.064707] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.065449] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.065509] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.068494] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.068611] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.068759] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.068853] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.069218] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.069245] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:44 192.168.122.209 [52115.073201] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 06:32:45 192.168.122.209 [52115.955783] [tdb] Close table 'client0.tdb' Apr 26 06:32:45 192.168.122.209 [52116.156613] [tdb] Close table 'sessions0.tdb' Apr 26 06:32:48 192.168.122.209 [52119.390313] [tdb] Close table 'cache0.tdb' Apr 26 06:32:49 192.168.122.209 [52119.642680] [tdb] Close table 'filter0.tdb' Apr 26 06:32:49 192.168.122.209 [52119.643138] [tempesta fw] modules are stopped Apr 26 06:32:49 192.168.122.209 [52119.837609] [tempesta fw] exiting... Apr 26 06:32:49 192.168.122.209 [52119.956429] [tdb] Shutdown Tempesta DB Apr 26 06:32:50 192.168.122.209 [52120.494637] End test: t_stress.test_stress.TestTdbStressHttp.test_cache_eviction_tdb Apr 26 06:32:50 192.168.122.209 [52120.509759] Start test: t_stress.test_stress.TlsCurlStress.test_concurrent_requests Apr 26 06:32:51 192.168.122.209 [52122.180244] [tdb] Start Tempesta DB Apr 26 06:32:51 192.168.122.209 [52122.344319] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:32:53 192.168.122.209 [52123.742053] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52123.742053] Maybe that's fine, but it's worth checking the [52123.742053] config - if there is no relations between the [52123.742053] names, then host name confusion attack is possible. Apr 26 06:32:53 192.168.122.209 [52123.852906] [tempesta fw] Configuration processing is completed. Apr 26 06:32:53 192.168.122.209 [52123.904855] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:32:53 192.168.122.209 [52123.934678] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:32:53 192.168.122.209 [52123.969290] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:32:53 192.168.122.209 [52124.036873] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:32:53 192.168.122.209 [52124.072844] [tempesta fw] Tempesta FW is ready Apr 26 06:32:54 192.168.122.209 [52125.146176] [tdb] Close table 'client0.tdb' Apr 26 06:32:54 192.168.122.209 [52125.340615] [tdb] Close table 'sessions0.tdb' Apr 26 06:32:55 192.168.122.209 [52125.563879] [tdb] Close table 'filter0.tdb' Apr 26 06:32:55 192.168.122.209 [52125.564313] [tempesta fw] modules are stopped Apr 26 06:32:55 192.168.122.209 [52125.803666] [tempesta fw] exiting... Apr 26 06:32:55 192.168.122.209 [52125.958416] [tdb] Shutdown Tempesta DB Apr 26 06:32:55 192.168.122.209 [52126.239662] End test: t_stress.test_stress.TlsCurlStress.test_concurrent_requests Apr 26 06:32:55 192.168.122.209 [52126.250858] Start test: t_stress.test_stress.TlsCurlStress.test_pipelined_requests Apr 26 06:32:57 192.168.122.209 [52127.857947] [tdb] Start Tempesta DB Apr 26 06:32:57 192.168.122.209 [52128.019196] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:32:58 192.168.122.209 [52128.554398] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52128.554398] Maybe that's fine, but it's worth checking the [52128.554398] config - if there is no relations between the [52128.554398] names, then host name confusion attack is possible. Apr 26 06:32:58 192.168.122.209 [52128.672938] [tempesta fw] Configuration processing is completed. Apr 26 06:32:58 192.168.122.209 [52128.724129] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:32:58 192.168.122.209 [52128.758304] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:32:58 192.168.122.209 [52128.788294] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:32:58 192.168.122.209 [52128.864965] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:32:58 192.168.122.209 [52128.904912] [tempesta fw] Tempesta FW is ready Apr 26 06:32:59 192.168.122.209 [52130.079622] [tdb] Close table 'client0.tdb' Apr 26 06:32:59 192.168.122.209 [52130.287858] [tdb] Close table 'sessions0.tdb' Apr 26 06:33:00 192.168.122.209 [52130.517532] [tdb] Close table 'filter0.tdb' Apr 26 06:33:00 192.168.122.209 [52130.517977] [tempesta fw] modules are stopped Apr 26 06:33:00 192.168.122.209 [52130.746017] [tempesta fw] exiting... Apr 26 06:33:00 192.168.122.209 [52130.889414] [tdb] Shutdown Tempesta DB Apr 26 06:33:00 192.168.122.209 [52131.145833] End test: t_stress.test_stress.TlsCurlStress.test_pipelined_requests Apr 26 06:33:00 192.168.122.209 [52131.181586] Start test: t_stress.test_stress.TlsCurlStress.test_range_requests Apr 26 06:33:02 192.168.122.209 [52132.765523] [tdb] Start Tempesta DB Apr 26 06:33:02 192.168.122.209 [52132.936424] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:33:03 192.168.122.209 [52133.513868] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52133.513868] Maybe that's fine, but it's worth checking the [52133.513868] config - if there is no relations between the [52133.513868] names, then host name confusion attack is possible. Apr 26 06:33:03 192.168.122.209 [52133.633015] [tempesta fw] Configuration processing is completed. Apr 26 06:33:03 192.168.122.209 [52133.684919] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:33:03 192.168.122.209 [52133.716753] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:33:03 192.168.122.209 [52133.746545] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:33:03 192.168.122.209 [52133.817031] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:33:03 192.168.122.209 [52133.856946] [tempesta fw] Tempesta FW is ready Apr 26 06:33:16 192.168.122.209 [52146.512633] [tdb] Close table 'client0.tdb' Apr 26 06:33:16 192.168.122.209 [52146.698778] [tdb] Close table 'sessions0.tdb' Apr 26 06:33:16 192.168.122.209 [52146.946358] [tdb] Close table 'filter0.tdb' Apr 26 06:33:16 192.168.122.209 [52146.946787] [tempesta fw] modules are stopped Apr 26 06:33:16 192.168.122.209 [52147.135117] [tempesta fw] exiting... Apr 26 06:33:16 192.168.122.209 [52147.283828] [tdb] Shutdown Tempesta DB Apr 26 06:33:17 192.168.122.209 [52147.572696] End test: t_stress.test_stress.TlsCurlStress.test_range_requests Apr 26 06:33:17 192.168.122.209 [52147.583434] Start test: t_stress.test_stress.TlsCurlStress.test_sequential_requests Apr 26 06:33:18 192.168.122.209 [52149.319794] [tdb] Start Tempesta DB Apr 26 06:33:19 192.168.122.209 [52149.488192] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:33:19 192.168.122.209 [52150.114489] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52150.114489] Maybe that's fine, but it's worth checking the [52150.114489] config - if there is no relations between the [52150.114489] names, then host name confusion attack is possible. Apr 26 06:33:19 192.168.122.209 [52150.233144] [tempesta fw] Configuration processing is completed. Apr 26 06:33:19 192.168.122.209 [52150.292149] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:33:19 192.168.122.209 [52150.327225] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:33:19 192.168.122.209 [52150.362099] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:33:19 192.168.122.209 [52150.437220] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:33:20 192.168.122.209 [52150.497161] [tempesta fw] Tempesta FW is ready Apr 26 06:33:21 192.168.122.209 [52152.057430] [tdb] Close table 'client0.tdb' Apr 26 06:33:21 192.168.122.209 [52152.258614] [tdb] Close table 'sessions0.tdb' Apr 26 06:33:22 192.168.122.209 [52152.491066] [tdb] Close table 'filter0.tdb' Apr 26 06:33:22 192.168.122.209 [52152.491527] [tempesta fw] modules are stopped Apr 26 06:33:22 192.168.122.209 [52152.782641] [tempesta fw] exiting... Apr 26 06:33:22 192.168.122.209 [52152.916445] [tdb] Shutdown Tempesta DB Apr 26 06:33:22 192.168.122.209 [52153.180613] End test: t_stress.test_stress.TlsCurlStress.test_sequential_requests Apr 26 06:33:22 192.168.122.209 [52153.196061] Start test: t_stress.test_stress.TlsWrkStress.test_concurrent_connections Apr 26 06:33:24 192.168.122.209 [52154.916452] [tdb] Start Tempesta DB Apr 26 06:33:24 192.168.122.209 [52155.079490] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:33:25 192.168.122.209 [52155.679388] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52155.679388] Maybe that's fine, but it's worth checking the [52155.679388] config - if there is no relations between the [52155.679388] names, then host name confusion attack is possible. Apr 26 06:33:25 192.168.122.209 [52155.817280] [tempesta fw] Configuration processing is completed. Apr 26 06:33:25 192.168.122.209 [52155.879602] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:33:25 192.168.122.209 [52155.912653] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:33:25 192.168.122.209 [52155.943254] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:33:25 192.168.122.209 [52156.013296] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:33:25 192.168.122.209 [52156.053238] [tempesta fw] Tempesta FW is ready Apr 26 06:33:36 192.168.122.209 [52166.898496] [tdb] Close table 'client0.tdb' Apr 26 06:33:36 192.168.122.209 [52167.090830] [tdb] Close table 'sessions0.tdb' Apr 26 06:33:36 192.168.122.209 [52167.310232] [tdb] Close table 'filter0.tdb' Apr 26 06:33:36 192.168.122.209 [52167.310645] [tempesta fw] modules are stopped Apr 26 06:33:37 192.168.122.209 [52167.489083] [tempesta fw] exiting... Apr 26 06:33:37 192.168.122.209 [52167.610720] [tdb] Shutdown Tempesta DB Apr 26 06:33:37 192.168.122.209 [52167.926834] End test: t_stress.test_stress.TlsWrkStress.test_concurrent_connections Apr 26 06:33:37 192.168.122.209 [52167.941354] Start test: t_stress.test_stress.TlsWrkStressDocker.test_concurrent_connections Apr 26 06:33:40 192.168.122.209 [52170.909264] docker0: port 1(veth0408226) entered blocking state Apr 26 06:33:40 192.168.122.209 [52170.909888] docker0: port 1(veth0408226) entered disabled state Apr 26 06:33:40 192.168.122.209 [52170.911896] device veth0408226 entered promiscuous mode Apr 26 06:33:41 192.168.122.209 [52171.838932] eth0: renamed from vethbff6739 Apr 26 06:33:41 192.168.122.209 [52171.863264] IPv6: ADDRCONF(NETDEV_CHANGE): veth0408226: link becomes ready Apr 26 06:33:41 192.168.122.209 [52171.865192] docker0: port 1(veth0408226) entered blocking state Apr 26 06:33:41 192.168.122.209 [52171.866439] docker0: port 1(veth0408226) entered forwarding state Apr 26 06:33:42 192.168.122.209 [52173.121253] [tdb] Start Tempesta DB Apr 26 06:33:42 192.168.122.209 [52173.282246] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:33:43 192.168.122.209 [52173.815206] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52173.815206] Maybe that's fine, but it's worth checking the [52173.815206] config - if there is no relations between the [52173.815206] names, then host name confusion attack is possible. Apr 26 06:33:43 192.168.122.209 [52173.965476] [tempesta fw] Configuration processing is completed. Apr 26 06:33:43 192.168.122.209 [52174.027894] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:33:43 192.168.122.209 [52174.063823] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:33:43 192.168.122.209 [52174.097646] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:33:43 192.168.122.209 [52174.209523] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:33:43 192.168.122.209 [52174.249469] [tempesta fw] Tempesta FW is ready Apr 26 06:33:54 192.168.122.209 [52185.206984] [tdb] Close table 'client0.tdb' Apr 26 06:33:54 192.168.122.209 [52185.405714] [tdb] Close table 'sessions0.tdb' Apr 26 06:33:55 192.168.122.209 [52185.644179] [tdb] Close table 'filter0.tdb' Apr 26 06:33:55 192.168.122.209 [52185.644624] [tempesta fw] modules are stopped Apr 26 06:33:55 192.168.122.209 [52185.868761] [tempesta fw] exiting... Apr 26 06:33:55 192.168.122.209 [52185.982610] [tdb] Shutdown Tempesta DB Apr 26 06:33:56 192.168.122.209 [52186.562376] docker0: port 1(veth0408226) entered disabled state Apr 26 06:33:56 192.168.122.209 [52186.563112] vethbff6739: renamed from eth0 Apr 26 06:33:56 192.168.122.209 [52186.620057] docker0: port 1(veth0408226) entered disabled state Apr 26 06:33:56 192.168.122.209 [52186.625033] device veth0408226 left promiscuous mode Apr 26 06:33:56 192.168.122.209 [52186.625587] docker0: port 1(veth0408226) entered disabled state Apr 26 06:33:56 192.168.122.209 [52186.895716] End test: t_stress.test_stress.TlsWrkStressDocker.test_concurrent_connections Apr 26 06:33:56 192.168.122.209 [52186.914240] Start test: t_stress.test_stress.WrkStress.test_concurrent_connections Apr 26 06:33:58 192.168.122.209 [52188.463683] [tdb] Start Tempesta DB Apr 26 06:33:58 192.168.122.209 [52188.619153] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:33:58 192.168.122.209 [52189.133750] [tempesta fw] Configuration processing is completed. Apr 26 06:33:58 192.168.122.209 [52189.185817] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:33:58 192.168.122.209 [52189.217817] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:33:58 192.168.122.209 [52189.247669] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:33:58 192.168.122.209 [52189.321732] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:33:58 192.168.122.209 [52189.365619] [tempesta fw] Tempesta FW is ready Apr 26 06:34:09 192.168.122.209 [52200.141908] [tdb] Close table 'client0.tdb' Apr 26 06:34:09 192.168.122.209 [52200.339344] [tdb] Close table 'sessions0.tdb' Apr 26 06:34:10 192.168.122.209 [52200.578466] [tdb] Close table 'filter0.tdb' Apr 26 06:34:10 192.168.122.209 [52200.578909] [tempesta fw] modules are stopped Apr 26 06:34:10 192.168.122.209 [52200.738764] [tempesta fw] exiting... Apr 26 06:34:10 192.168.122.209 [52200.869397] [tdb] Shutdown Tempesta DB Apr 26 06:34:10 192.168.122.209 [52201.104643] End test: t_stress.test_stress.WrkStress.test_concurrent_connections Apr 26 06:34:10 192.168.122.209 [52201.121517] Start test: t_stress.test_wordpress.TestWordpressStressHttps.test_get_large_images Apr 26 06:34:12 192.168.122.209 [52202.487086] lxdbr0: port 1(veth47eafc54) entered blocking state Apr 26 06:34:12 192.168.122.209 [52202.487721] lxdbr0: port 1(veth47eafc54) entered disabled state Apr 26 06:34:12 192.168.122.209 [52202.490644] device veth47eafc54 entered promiscuous mode Apr 26 06:34:12 192.168.122.209 [52203.024982] physFeUkhZ: renamed from vethb80882e0 Apr 26 06:34:12 192.168.122.209 [52203.078938] eth0: renamed from physFeUkhZ Apr 26 06:34:12 192.168.122.209 [52203.099251] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Apr 26 06:34:12 192.168.122.209 [52203.100575] lxdbr0: port 1(veth47eafc54) entered blocking state Apr 26 06:34:12 192.168.122.209 [52203.101353] lxdbr0: port 1(veth47eafc54) entered forwarding state Apr 26 06:34:13 192.168.122.209 [52203.840872] Not activating Mandatory Access Control as /sbin/tomoyo-init does not exist. Apr 26 06:34:15 192.168.122.209 [52206.343569] [tdb] Start Tempesta DB Apr 26 06:34:16 192.168.122.209 [52206.512158] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:34:16 192.168.122.209 [52206.978355] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52206.978355] Maybe that's fine, but it's worth checking the [52206.978355] config - if there is no relations between the [52206.978355] names, then host name confusion attack is possible. Apr 26 06:34:16 192.168.122.209 [52207.149881] [tempesta fw] Configuration processing is completed. Apr 26 06:34:16 192.168.122.209 [52207.205488] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:34:16 192.168.122.209 [52207.237579] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:34:16 192.168.122.209 [52207.268200] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:34:16 192.168.122.209 [52207.387292] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:34:16 192.168.122.209 [52207.449855] [tempesta fw] Tempesta FW is ready Apr 26 06:34:33 192.168.122.209 [52223.912330] [tdb] Close table 'client0.tdb' Apr 26 06:34:33 192.168.122.209 [52224.112361] [tdb] Close table 'sessions0.tdb' Apr 26 06:34:33 192.168.122.209 [52224.436612] [tdb] Close table 'filter0.tdb' Apr 26 06:34:33 192.168.122.209 [52224.437111] [tempesta fw] modules are stopped Apr 26 06:34:34 192.168.122.209 [52224.718875] [tempesta fw] exiting... Apr 26 06:34:34 192.168.122.209 [52224.844514] [tdb] Shutdown Tempesta DB Apr 26 06:34:41 192.168.122.209 [52232.176401] physFeUkhZ: renamed from eth0 Apr 26 06:34:41 192.168.122.209 [52232.203979] lxdbr0: port 1(veth47eafc54) entered disabled state Apr 26 06:34:41 192.168.122.209 [52232.222268] vethb80882e0: renamed from physFeUkhZ Apr 26 06:34:42 192.168.122.209 [52233.081369] device veth47eafc54 left promiscuous mode Apr 26 06:34:42 192.168.122.209 [52233.081917] lxdbr0: port 1(veth47eafc54) entered disabled state Apr 26 06:34:43 192.168.122.209 [52234.038041] End test: t_stress.test_wordpress.TestWordpressStressHttps.test_get_large_images Apr 26 06:34:43 192.168.122.209 [52234.062977] Start test: t_tcp_options.test_tcp_options.TestTcpOptionsH2.test_large_response_tcp_mtu_probing_1500 Apr 26 06:34:45 192.168.122.209 [52235.704127] [tdb] Start Tempesta DB Apr 26 06:34:45 192.168.122.209 [52235.867694] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:34:46 192.168.122.209 [52236.507137] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52236.507137] Maybe that's fine, but it's worth checking the [52236.507137] config - if there is no relations between the [52236.507137] names, then host name confusion attack is possible. Apr 26 06:34:46 192.168.122.209 [52236.626328] [tempesta fw] Configuration processing is completed. Apr 26 06:34:46 192.168.122.209 [52236.700716] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:34:46 192.168.122.209 [52237.406728] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:34:46 192.168.122.209 [52237.457606] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:34:47 192.168.122.209 [52237.502082] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:34:47 192.168.122.209 [52237.562356] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:34:47 192.168.122.209 [52237.564111] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:34:47 192.168.122.209 [52237.602254] [tempesta fw] Tempesta FW is ready Apr 26 06:34:48 192.168.122.209 [52238.617803] [tdb] Close table 'client0.tdb' Apr 26 06:34:48 192.168.122.209 [52238.813855] [tdb] Close table 'sessions0.tdb' Apr 26 06:34:51 192.168.122.209 [52242.249932] [tdb] Close table 'cache0.tdb' Apr 26 06:34:52 192.168.122.209 [52242.495758] [tdb] Close table 'filter0.tdb' Apr 26 06:34:52 192.168.122.209 [52242.496230] [tempesta fw] modules are stopped Apr 26 06:34:52 192.168.122.209 [52242.706002] [tempesta fw] exiting... Apr 26 06:34:52 192.168.122.209 [52242.833702] [tdb] Shutdown Tempesta DB Apr 26 06:34:52 192.168.122.209 [52243.060306] End test: t_tcp_options.test_tcp_options.TestTcpOptionsH2.test_large_response_tcp_mtu_probing_1500 Apr 26 06:34:52 192.168.122.209 [52243.071846] Start test: t_tcp_options.test_tcp_options.TestTcpOptionsH2.test_large_response_tcp_mtu_probing_40000 Apr 26 06:34:54 192.168.122.209 [52244.494861] [tdb] Start Tempesta DB Apr 26 06:34:54 192.168.122.209 [52244.688441] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:34:55 192.168.122.209 [52246.127796] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52246.127796] Maybe that's fine, but it's worth checking the [52246.127796] config - if there is no relations between the [52246.127796] names, then host name confusion attack is possible. Apr 26 06:34:55 192.168.122.209 [52246.234465] [tempesta fw] Configuration processing is completed. Apr 26 06:34:55 192.168.122.209 [52246.293409] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:34:56 192.168.122.209 [52246.879350] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:34:56 192.168.122.209 [52246.914522] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:34:56 192.168.122.209 [52246.952294] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:34:56 192.168.122.209 [52247.026480] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:34:56 192.168.122.209 [52247.028306] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:34:56 192.168.122.209 [52247.074383] [tempesta fw] Tempesta FW is ready Apr 26 06:34:57 192.168.122.209 [52247.790949] [tdb] Close table 'client0.tdb' Apr 26 06:34:57 192.168.122.209 [52247.998132] [tdb] Close table 'sessions0.tdb' Apr 26 06:35:00 192.168.122.209 [52251.339554] [tdb] Close table 'cache0.tdb' Apr 26 06:35:01 192.168.122.209 [52251.587361] [tdb] Close table 'filter0.tdb' Apr 26 06:35:01 192.168.122.209 [52251.587802] [tempesta fw] modules are stopped Apr 26 06:35:01 192.168.122.209 [52251.864831] [tempesta fw] exiting... Apr 26 06:35:01 192.168.122.209 [52251.983308] [tdb] Shutdown Tempesta DB Apr 26 06:35:01 192.168.122.209 [52252.208586] End test: t_tcp_options.test_tcp_options.TestTcpOptionsH2.test_large_response_tcp_mtu_probing_40000 Apr 26 06:35:01 192.168.122.209 [52252.231406] Start test: t_tcp_options.test_tcp_options.TestTcpOptionsHttp.test_large_response_tcp_mtu_probing_1500 Apr 26 06:35:03 192.168.122.209 [52253.618765] [tdb] Start Tempesta DB Apr 26 06:35:03 192.168.122.209 [52253.797299] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:35:04 192.168.122.209 [52255.201572] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52255.201572] Maybe that's fine, but it's worth checking the [52255.201572] config - if there is no relations between the [52255.201572] names, then host name confusion attack is possible. Apr 26 06:35:04 192.168.122.209 [52255.306602] [tempesta fw] Configuration processing is completed. Apr 26 06:35:04 192.168.122.209 [52255.362691] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:35:05 192.168.122.209 [52255.808255] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:35:05 192.168.122.209 [52255.844346] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:35:05 192.168.122.209 [52255.873140] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:35:05 192.168.122.209 [52255.946549] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:35:05 192.168.122.209 [52255.948371] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:35:05 192.168.122.209 [52255.990469] [tempesta fw] Tempesta FW is ready Apr 26 06:35:06 192.168.122.209 [52256.695473] [tdb] Close table 'client0.tdb' Apr 26 06:35:06 192.168.122.209 [52256.885637] [tdb] Close table 'sessions0.tdb' Apr 26 06:35:09 192.168.122.209 [52260.165543] [tdb] Close table 'cache0.tdb' Apr 26 06:35:09 192.168.122.209 [52260.403400] [tdb] Close table 'filter0.tdb' Apr 26 06:35:09 192.168.122.209 [52260.403849] [tempesta fw] modules are stopped Apr 26 06:35:10 192.168.122.209 [52260.624894] [tempesta fw] exiting... Apr 26 06:35:10 192.168.122.209 [52260.754170] [tdb] Shutdown Tempesta DB Apr 26 06:35:10 192.168.122.209 [52260.933662] End test: t_tcp_options.test_tcp_options.TestTcpOptionsHttp.test_large_response_tcp_mtu_probing_1500 Apr 26 06:35:10 192.168.122.209 [52260.946852] Start test: t_tcp_options.test_tcp_options.TestTcpOptionsHttp.test_large_response_tcp_mtu_probing_40000 Apr 26 06:35:11 192.168.122.209 [52262.307155] [tdb] Start Tempesta DB Apr 26 06:35:11 192.168.122.209 [52262.460437] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:35:13 192.168.122.209 [52263.831975] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52263.831975] Maybe that's fine, but it's worth checking the [52263.831975] config - if there is no relations between the [52263.831975] names, then host name confusion attack is possible. Apr 26 06:35:13 192.168.122.209 [52263.930684] [tempesta fw] Configuration processing is completed. Apr 26 06:35:13 192.168.122.209 [52263.980786] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:35:13 192.168.122.209 [52264.421008] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:35:14 192.168.122.209 [52264.464186] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:35:14 192.168.122.209 [52264.497988] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:35:14 192.168.122.209 [52264.562631] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:35:14 192.168.122.209 [52264.564328] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:35:14 192.168.122.209 [52264.602545] [tempesta fw] Tempesta FW is ready Apr 26 06:35:14 192.168.122.209 [52265.314089] [tdb] Close table 'client0.tdb' Apr 26 06:35:15 192.168.122.209 [52265.508866] [tdb] Close table 'sessions0.tdb' Apr 26 06:35:18 192.168.122.209 [52268.731420] [tdb] Close table 'cache0.tdb' Apr 26 06:35:18 192.168.122.209 [52268.996596] [tdb] Close table 'filter0.tdb' Apr 26 06:35:18 192.168.122.209 [52268.997030] [tempesta fw] modules are stopped Apr 26 06:35:18 192.168.122.209 [52269.191452] [tempesta fw] exiting... Apr 26 06:35:18 192.168.122.209 [52269.325122] [tdb] Shutdown Tempesta DB Apr 26 06:35:19 192.168.122.209 [52269.542167] End test: t_tcp_options.test_tcp_options.TestTcpOptionsHttp.test_large_response_tcp_mtu_probing_40000 Apr 26 06:35:19 192.168.122.209 [52269.560083] Start test: t_tcp_options.test_tcp_options.TestTcpOptionsHttps.test_large_response_tcp_mtu_probing_1500 Apr 26 06:35:20 192.168.122.209 [52271.017486] [tdb] Start Tempesta DB Apr 26 06:35:20 192.168.122.209 [52271.160325] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:35:22 192.168.122.209 [52272.499979] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52272.499979] Maybe that's fine, but it's worth checking the [52272.499979] config - if there is no relations between the [52272.499979] names, then host name confusion attack is possible. Apr 26 06:35:22 192.168.122.209 [52272.598793] [tempesta fw] Configuration processing is completed. Apr 26 06:35:22 192.168.122.209 [52272.649101] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:35:22 192.168.122.209 [52273.145881] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:35:22 192.168.122.209 [52273.172757] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:35:22 192.168.122.209 [52273.198950] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:35:22 192.168.122.209 [52273.290738] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:35:22 192.168.122.209 [52273.292512] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:35:22 192.168.122.209 [52273.338702] [tempesta fw] Tempesta FW is ready Apr 26 06:35:23 192.168.122.209 [52274.128766] [tdb] Close table 'client0.tdb' Apr 26 06:35:23 192.168.122.209 [52274.329118] [tdb] Close table 'sessions0.tdb' Apr 26 06:35:27 192.168.122.209 [52277.719871] [tdb] Close table 'cache0.tdb' Apr 26 06:35:27 192.168.122.209 [52277.963019] [tdb] Close table 'filter0.tdb' Apr 26 06:35:27 192.168.122.209 [52277.963476] [tempesta fw] modules are stopped Apr 26 06:35:27 192.168.122.209 [52278.178861] [tempesta fw] exiting... Apr 26 06:35:27 192.168.122.209 [52278.338187] [tdb] Shutdown Tempesta DB Apr 26 06:35:28 192.168.122.209 [52278.564804] End test: t_tcp_options.test_tcp_options.TestTcpOptionsHttps.test_large_response_tcp_mtu_probing_1500 Apr 26 06:35:28 192.168.122.209 [52278.583703] Start test: t_tcp_options.test_tcp_options.TestTcpOptionsHttps.test_large_response_tcp_mtu_probing_40000 Apr 26 06:35:29 192.168.122.209 [52279.998407] [tdb] Start Tempesta DB Apr 26 06:35:29 192.168.122.209 [52280.145119] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:35:31 192.168.122.209 [52281.592223] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52281.592223] Maybe that's fine, but it's worth checking the [52281.592223] config - if there is no relations between the [52281.592223] names, then host name confusion attack is possible. Apr 26 06:35:31 192.168.122.209 [52281.694880] [tempesta fw] Configuration processing is completed. Apr 26 06:35:31 192.168.122.209 [52281.755265] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:35:31 192.168.122.209 [52282.201497] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:35:31 192.168.122.209 [52282.228378] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:35:31 192.168.122.209 [52282.254758] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:35:31 192.168.122.209 [52282.338844] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:35:31 192.168.122.209 [52282.340793] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:35:31 192.168.122.209 [52282.386814] [tempesta fw] Tempesta FW is ready Apr 26 06:35:32 192.168.122.209 [52283.104391] [tdb] Close table 'client0.tdb' Apr 26 06:35:32 192.168.122.209 [52283.290807] [tdb] Close table 'sessions0.tdb' Apr 26 06:35:35 192.168.122.209 [52286.443238] [tdb] Close table 'cache0.tdb' Apr 26 06:35:36 192.168.122.209 [52286.704127] [tdb] Close table 'filter0.tdb' Apr 26 06:35:36 192.168.122.209 [52286.704591] [tempesta fw] modules are stopped Apr 26 06:35:36 192.168.122.209 [52286.911290] [tempesta fw] exiting... Apr 26 06:35:36 192.168.122.209 [52287.033728] [tdb] Shutdown Tempesta DB Apr 26 06:35:36 192.168.122.209 [52287.240947] End test: t_tcp_options.test_tcp_options.TestTcpOptionsHttps.test_large_response_tcp_mtu_probing_40000 Apr 26 06:35:36 192.168.122.209 [52287.252096] Start test: t_wrong_body_length.test_h2_request_wrong_length.RequestCorrectBodyLength.test_post_request Apr 26 06:35:37 192.168.122.209 [52288.350875] [tdb] Start Tempesta DB Apr 26 06:35:38 192.168.122.209 [52288.495862] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:35:39 192.168.122.209 [52289.964417] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52289.964417] Maybe that's fine, but it's worth checking the [52289.964417] config - if there is no relations between the [52289.964417] names, then host name confusion attack is possible. Apr 26 06:35:39 192.168.122.209 [52290.094974] [tempesta fw] Configuration processing is completed. Apr 26 06:35:39 192.168.122.209 [52290.140150] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:35:39 192.168.122.209 [52290.168309] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:35:39 192.168.122.209 [52290.203558] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:35:39 192.168.122.209 [52290.246912] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:35:39 192.168.122.209 [52290.294905] [tempesta fw] Tempesta FW is ready Apr 26 06:35:40 192.168.122.209 [52290.905465] [tdb] Close table 'client0.tdb' Apr 26 06:35:40 192.168.122.209 [52291.112748] [tdb] Close table 'sessions0.tdb' Apr 26 06:35:40 192.168.122.209 [52291.350252] [tdb] Close table 'filter0.tdb' Apr 26 06:35:40 192.168.122.209 [52291.350706] [tempesta fw] modules are stopped Apr 26 06:35:41 192.168.122.209 [52291.551549] [tempesta fw] exiting... Apr 26 06:35:41 192.168.122.209 [52291.670386] [tdb] Shutdown Tempesta DB Apr 26 06:35:41 192.168.122.209 [52291.876263] End test: t_wrong_body_length.test_h2_request_wrong_length.RequestCorrectBodyLength.test_post_request Apr 26 06:35:41 192.168.122.209 [52291.892402] Start test: t_wrong_body_length.test_h2_request_wrong_length.RequestCorrectBodyLength.test_put_request Apr 26 06:35:42 192.168.122.209 [52293.016988] [tdb] Start Tempesta DB Apr 26 06:35:42 192.168.122.209 [52293.157405] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:35:43 192.168.122.209 [52293.828637] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52293.828637] Maybe that's fine, but it's worth checking the [52293.828637] config - if there is no relations between the [52293.828637] names, then host name confusion attack is possible. Apr 26 06:35:43 192.168.122.209 [52293.959046] [tempesta fw] Configuration processing is completed. Apr 26 06:35:43 192.168.122.209 [52294.008886] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:35:43 192.168.122.209 [52294.036416] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:35:43 192.168.122.209 [52294.064184] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:35:43 192.168.122.209 [52294.142951] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:35:43 192.168.122.209 [52294.182957] [tempesta fw] Tempesta FW is ready Apr 26 06:35:44 192.168.122.209 [52294.820761] [tdb] Close table 'client0.tdb' Apr 26 06:35:44 192.168.122.209 [52295.006544] [tdb] Close table 'sessions0.tdb' Apr 26 06:35:44 192.168.122.209 [52295.249997] [tdb] Close table 'filter0.tdb' Apr 26 06:35:44 192.168.122.209 [52295.250429] [tempesta fw] modules are stopped Apr 26 06:35:44 192.168.122.209 [52295.446984] [tempesta fw] exiting... Apr 26 06:35:45 192.168.122.209 [52295.585608] [tdb] Shutdown Tempesta DB Apr 26 06:35:45 192.168.122.209 [52295.790603] End test: t_wrong_body_length.test_h2_request_wrong_length.RequestCorrectBodyLength.test_put_request Apr 26 06:35:45 192.168.122.209 [52295.809158] Start test: t_wrong_body_length.test_h2_request_wrong_length.RequestDecimalBodyLength.test_post_request Apr 26 06:35:46 192.168.122.209 [52296.854029] [tdb] Start Tempesta DB Apr 26 06:35:46 192.168.122.209 [52296.985597] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:35:47 192.168.122.209 [52297.688714] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52297.688714] Maybe that's fine, but it's worth checking the [52297.688714] config - if there is no relations between the [52297.688714] names, then host name confusion attack is possible. Apr 26 06:35:47 192.168.122.209 [52297.823080] [tempesta fw] Configuration processing is completed. Apr 26 06:35:47 192.168.122.209 [52297.876308] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:35:47 192.168.122.209 [52297.904085] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:35:47 192.168.122.209 [52297.932376] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:35:47 192.168.122.209 [52297.983036] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:35:47 192.168.122.209 [52298.031015] [tempesta fw] Tempesta FW is ready Apr 26 06:35:47 192.168.122.209 [52298.177870] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrContent_LengthV input=0x30('0.5'), len=3, off=0 Apr 26 06:35:48 192.168.122.209 [52298.605986] [tdb] Close table 'client0.tdb' Apr 26 06:35:48 192.168.122.209 [52298.797090] [tdb] Close table 'sessions0.tdb' Apr 26 06:35:48 192.168.122.209 [52299.042846] [tdb] Close table 'filter0.tdb' Apr 26 06:35:48 192.168.122.209 [52299.043290] [tempesta fw] modules are stopped Apr 26 06:35:48 192.168.122.209 [52299.241871] [tempesta fw] exiting... Apr 26 06:35:48 192.168.122.209 [52299.346328] [tdb] Shutdown Tempesta DB Apr 26 06:35:49 192.168.122.209 [52299.591019] End test: t_wrong_body_length.test_h2_request_wrong_length.RequestDecimalBodyLength.test_post_request Apr 26 06:35:49 192.168.122.209 [52299.627248] Start test: t_wrong_body_length.test_h2_request_wrong_length.RequestDecimalBodyLength.test_put_request Apr 26 06:35:50 192.168.122.209 [52300.686210] [tdb] Start Tempesta DB Apr 26 06:35:50 192.168.122.209 [52300.821532] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:35:51 192.168.122.209 [52301.480637] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52301.480637] Maybe that's fine, but it's worth checking the [52301.480637] config - if there is no relations between the [52301.480637] names, then host name confusion attack is possible. Apr 26 06:35:51 192.168.122.209 [52301.619114] [tempesta fw] Configuration processing is completed. Apr 26 06:35:51 192.168.122.209 [52301.665850] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:35:51 192.168.122.209 [52301.693300] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:35:51 192.168.122.209 [52301.721349] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:35:51 192.168.122.209 [52301.771096] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:35:51 192.168.122.209 [52301.811045] [tempesta fw] Tempesta FW is ready Apr 26 06:35:51 192.168.122.209 [52301.933795] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrContent_LengthV input=0x30('0.5'), len=3, off=0 Apr 26 06:35:51 192.168.122.209 [52302.372087] [tdb] Close table 'client0.tdb' Apr 26 06:35:52 192.168.122.209 [52302.556242] [tdb] Close table 'sessions0.tdb' Apr 26 06:35:52 192.168.122.209 [52302.788907] [tdb] Close table 'filter0.tdb' Apr 26 06:35:52 192.168.122.209 [52302.789306] [tempesta fw] modules are stopped Apr 26 06:35:52 192.168.122.209 [52302.979232] [tempesta fw] exiting... Apr 26 06:35:52 192.168.122.209 [52303.128839] [tdb] Shutdown Tempesta DB Apr 26 06:35:52 192.168.122.209 [52303.331439] End test: t_wrong_body_length.test_h2_request_wrong_length.RequestDecimalBodyLength.test_put_request Apr 26 06:35:52 192.168.122.209 [52303.340951] Start test: t_wrong_body_length.test_h2_request_wrong_length.RequestDuplicateBodyLength.test_post_request Apr 26 06:35:53 192.168.122.209 [52304.319573] [tdb] Start Tempesta DB Apr 26 06:35:53 192.168.122.209 [52304.461051] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:35:54 192.168.122.209 [52305.224700] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52305.224700] Maybe that's fine, but it's worth checking the [52305.224700] config - if there is no relations between the [52305.224700] names, then host name confusion attack is possible. Apr 26 06:35:54 192.168.122.209 [52305.363160] [tempesta fw] Configuration processing is completed. Apr 26 06:35:54 192.168.122.209 [52305.413930] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:35:54 192.168.122.209 [52305.441251] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:35:55 192.168.122.209 [52305.468688] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:35:55 192.168.122.209 [52305.531143] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:35:55 192.168.122.209 [52305.575095] [tempesta fw] Tempesta FW is ready Apr 26 06:35:55 192.168.122.209 [52305.709464] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrContent_LengthV input=0x33('33, 33'), len=6, off=0 Apr 26 06:35:55 192.168.122.209 [52306.120331] [tdb] Close table 'client0.tdb' Apr 26 06:35:55 192.168.122.209 [52306.307273] [tdb] Close table 'sessions0.tdb' Apr 26 06:35:56 192.168.122.209 [52306.524156] [tdb] Close table 'filter0.tdb' Apr 26 06:35:56 192.168.122.209 [52306.524586] [tempesta fw] modules are stopped Apr 26 06:35:56 192.168.122.209 [52306.739330] [tempesta fw] exiting... Apr 26 06:35:56 192.168.122.209 [52306.861008] [tdb] Shutdown Tempesta DB Apr 26 06:35:56 192.168.122.209 [52307.079857] End test: t_wrong_body_length.test_h2_request_wrong_length.RequestDuplicateBodyLength.test_post_request Apr 26 06:35:56 192.168.122.209 [52307.096139] Start test: t_wrong_body_length.test_h2_request_wrong_length.RequestDuplicateBodyLength.test_put_request Apr 26 06:35:57 192.168.122.209 [52308.157590] [tdb] Start Tempesta DB Apr 26 06:35:57 192.168.122.209 [52308.294695] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:35:58 192.168.122.209 [52308.964731] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52308.964731] Maybe that's fine, but it's worth checking the [52308.964731] config - if there is no relations between the [52308.964731] names, then host name confusion attack is possible. Apr 26 06:35:58 192.168.122.209 [52309.111218] [tempesta fw] Configuration processing is completed. Apr 26 06:35:58 192.168.122.209 [52309.165110] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:35:58 192.168.122.209 [52309.195151] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:35:58 192.168.122.209 [52309.222804] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:35:58 192.168.122.209 [52309.271229] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:35:58 192.168.122.209 [52309.319148] [tempesta fw] Tempesta FW is ready Apr 26 06:35:58 192.168.122.209 [52309.451970] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrContent_LengthV input=0x33('33, 33'), len=6, off=0 Apr 26 06:35:59 192.168.122.209 [52309.922181] [tdb] Close table 'client0.tdb' Apr 26 06:35:59 192.168.122.209 [52310.110938] [tdb] Close table 'sessions0.tdb' Apr 26 06:35:59 192.168.122.209 [52310.342957] [tdb] Close table 'filter0.tdb' Apr 26 06:35:59 192.168.122.209 [52310.343400] [tempesta fw] modules are stopped Apr 26 06:36:00 192.168.122.209 [52310.553176] [tempesta fw] exiting... Apr 26 06:36:00 192.168.122.209 [52310.677978] [tdb] Shutdown Tempesta DB Apr 26 06:36:00 192.168.122.209 [52310.904535] End test: t_wrong_body_length.test_h2_request_wrong_length.RequestDuplicateBodyLength.test_put_request Apr 26 06:36:00 192.168.122.209 [52310.930411] Start test: t_wrong_body_length.test_h2_request_wrong_length.RequestEmptyBodyLength.test_post_request Apr 26 06:36:01 192.168.122.209 [52311.946941] [tdb] Start Tempesta DB Apr 26 06:36:01 192.168.122.209 [52312.091566] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:36:02 192.168.122.209 [52312.784899] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52312.784899] Maybe that's fine, but it's worth checking the [52312.784899] config - if there is no relations between the [52312.784899] names, then host name confusion attack is possible. Apr 26 06:36:02 192.168.122.209 [52312.919656] [tempesta fw] Configuration processing is completed. Apr 26 06:36:02 192.168.122.209 [52312.969146] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:36:02 192.168.122.209 [52312.996901] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:36:02 192.168.122.209 [52313.024880] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:36:02 192.168.122.209 [52313.067227] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:36:02 192.168.122.209 [52313.107200] [tempesta fw] Tempesta FW is ready Apr 26 06:36:03 192.168.122.209 [52313.672743] [tdb] Close table 'client0.tdb' Apr 26 06:36:03 192.168.122.209 [52313.865019] [tdb] Close table 'sessions0.tdb' Apr 26 06:36:03 192.168.122.209 [52314.087247] [tdb] Close table 'filter0.tdb' Apr 26 06:36:03 192.168.122.209 [52314.087673] [tempesta fw] modules are stopped Apr 26 06:36:03 192.168.122.209 [52314.287366] [tempesta fw] exiting... Apr 26 06:36:03 192.168.122.209 [52314.414681] [tdb] Shutdown Tempesta DB Apr 26 06:36:04 192.168.122.209 [52314.608811] End test: t_wrong_body_length.test_h2_request_wrong_length.RequestEmptyBodyLength.test_post_request Apr 26 06:36:04 192.168.122.209 [52314.629803] Start test: t_wrong_body_length.test_h2_request_wrong_length.RequestEmptyBodyLength.test_put_request Apr 26 06:36:05 192.168.122.209 [52315.648077] [tdb] Start Tempesta DB Apr 26 06:36:05 192.168.122.209 [52315.792163] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:36:06 192.168.122.209 [52316.520847] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52316.520847] Maybe that's fine, but it's worth checking the [52316.520847] config - if there is no relations between the [52316.520847] names, then host name confusion attack is possible. Apr 26 06:36:06 192.168.122.209 [52316.663296] [tempesta fw] Configuration processing is completed. Apr 26 06:36:06 192.168.122.209 [52316.713270] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:36:06 192.168.122.209 [52316.742402] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:36:06 192.168.122.209 [52316.769750] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:36:06 192.168.122.209 [52316.843219] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:36:06 192.168.122.209 [52316.887227] [tempesta fw] Tempesta FW is ready Apr 26 06:36:07 192.168.122.209 [52317.479286] [tdb] Close table 'client0.tdb' Apr 26 06:36:07 192.168.122.209 [52317.668424] [tdb] Close table 'sessions0.tdb' Apr 26 06:36:07 192.168.122.209 [52317.896191] [tdb] Close table 'filter0.tdb' Apr 26 06:36:07 192.168.122.209 [52317.896620] [tempesta fw] modules are stopped Apr 26 06:36:07 192.168.122.209 [52318.084333] [tempesta fw] exiting... Apr 26 06:36:07 192.168.122.209 [52318.214182] [tdb] Shutdown Tempesta DB Apr 26 06:36:07 192.168.122.209 [52318.456892] End test: t_wrong_body_length.test_h2_request_wrong_length.RequestEmptyBodyLength.test_put_request Apr 26 06:36:08 192.168.122.209 [52318.476912] Start test: t_wrong_body_length.test_h2_request_wrong_length.RequestInvalidBodyLength.test_post_request Apr 26 06:36:09 192.168.122.209 [52319.547348] [tdb] Start Tempesta DB Apr 26 06:36:09 192.168.122.209 [52319.681864] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:36:09 192.168.122.209 [52320.424933] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52320.424933] Maybe that's fine, but it's worth checking the [52320.424933] config - if there is no relations between the [52320.424933] names, then host name confusion attack is possible. Apr 26 06:36:10 192.168.122.209 [52320.579337] [tempesta fw] Configuration processing is completed. Apr 26 06:36:10 192.168.122.209 [52320.625704] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:36:10 192.168.122.209 [52320.654727] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:36:10 192.168.122.209 [52320.683466] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:36:10 192.168.122.209 [52320.735370] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:36:10 192.168.122.209 [52320.775287] [tempesta fw] Tempesta FW is ready Apr 26 06:36:10 192.168.122.209 [52320.914848] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrContent_LengthV input=0x69('invalid'), len=7, off=0 Apr 26 06:36:10 192.168.122.209 [52321.361060] [tdb] Close table 'client0.tdb' Apr 26 06:36:11 192.168.122.209 [52321.549173] [tdb] Close table 'sessions0.tdb' Apr 26 06:36:11 192.168.122.209 [52321.771184] [tdb] Close table 'filter0.tdb' Apr 26 06:36:11 192.168.122.209 [52321.771608] [tempesta fw] modules are stopped Apr 26 06:36:11 192.168.122.209 [52321.970256] [tempesta fw] exiting... Apr 26 06:36:11 192.168.122.209 [52322.091695] [tdb] Shutdown Tempesta DB Apr 26 06:36:11 192.168.122.209 [52322.285099] End test: t_wrong_body_length.test_h2_request_wrong_length.RequestInvalidBodyLength.test_post_request Apr 26 06:36:11 192.168.122.209 [52322.293233] Start test: t_wrong_body_length.test_h2_request_wrong_length.RequestInvalidBodyLength.test_put_request Apr 26 06:36:12 192.168.122.209 [52323.316278] [tdb] Start Tempesta DB Apr 26 06:36:12 192.168.122.209 [52323.445218] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:36:13 192.168.122.209 [52324.152945] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52324.152945] Maybe that's fine, but it's worth checking the [52324.152945] config - if there is no relations between the [52324.152945] names, then host name confusion attack is possible. Apr 26 06:36:13 192.168.122.209 [52324.283418] [tempesta fw] Configuration processing is completed. Apr 26 06:36:13 192.168.122.209 [52324.333777] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:36:13 192.168.122.209 [52324.362096] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:36:13 192.168.122.209 [52324.390934] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:36:13 192.168.122.209 [52324.435345] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:36:14 192.168.122.209 [52324.475347] [tempesta fw] Tempesta FW is ready Apr 26 06:36:14 192.168.122.209 [52324.604431] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrContent_LengthV input=0x69('invalid'), len=7, off=0 Apr 26 06:36:14 192.168.122.209 [52325.017031] [tdb] Close table 'client0.tdb' Apr 26 06:36:14 192.168.122.209 [52325.205001] [tdb] Close table 'sessions0.tdb' Apr 26 06:36:14 192.168.122.209 [52325.453490] [tdb] Close table 'filter0.tdb' Apr 26 06:36:14 192.168.122.209 [52325.453931] [tempesta fw] modules are stopped Apr 26 06:36:15 192.168.122.209 [52325.660477] [tempesta fw] exiting... Apr 26 06:36:15 192.168.122.209 [52325.755704] [tdb] Shutdown Tempesta DB Apr 26 06:36:15 192.168.122.209 [52325.971280] End test: t_wrong_body_length.test_h2_request_wrong_length.RequestInvalidBodyLength.test_put_request Apr 26 06:36:15 192.168.122.209 [52325.980853] Start test: t_wrong_body_length.test_h2_request_wrong_length.RequestMissingBodyLength.test_post_request Apr 26 06:36:16 192.168.122.209 [52327.049210] [tdb] Start Tempesta DB Apr 26 06:36:16 192.168.122.209 [52327.184520] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:36:17 192.168.122.209 [52327.881044] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52327.881044] Maybe that's fine, but it's worth checking the [52327.881044] config - if there is no relations between the [52327.881044] names, then host name confusion attack is possible. Apr 26 06:36:17 192.168.122.209 [52328.027393] [tempesta fw] Configuration processing is completed. Apr 26 06:36:17 192.168.122.209 [52328.078509] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:36:17 192.168.122.209 [52328.108817] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:36:17 192.168.122.209 [52328.140341] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:36:17 192.168.122.209 [52328.183412] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:36:17 192.168.122.209 [52328.223659] [tempesta fw] Tempesta FW is ready Apr 26 06:36:18 192.168.122.209 [52328.817851] [tdb] Close table 'client0.tdb' Apr 26 06:36:18 192.168.122.209 [52329.002255] [tdb] Close table 'sessions0.tdb' Apr 26 06:36:18 192.168.122.209 [52329.264194] [tdb] Close table 'filter0.tdb' Apr 26 06:36:18 192.168.122.209 [52329.264640] [tempesta fw] modules are stopped Apr 26 06:36:19 192.168.122.209 [52329.621845] [tempesta fw] exiting... Apr 26 06:36:19 192.168.122.209 [52329.753212] [tdb] Shutdown Tempesta DB Apr 26 06:36:19 192.168.122.209 [52329.985446] End test: t_wrong_body_length.test_h2_request_wrong_length.RequestMissingBodyLength.test_post_request Apr 26 06:36:19 192.168.122.209 [52330.001511] Start test: t_wrong_body_length.test_h2_request_wrong_length.RequestMissingBodyLength.test_put_request Apr 26 06:36:20 192.168.122.209 [52331.019955] [tdb] Start Tempesta DB Apr 26 06:36:20 192.168.122.209 [52331.159721] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:36:21 192.168.122.209 [52331.893031] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52331.893031] Maybe that's fine, but it's worth checking the [52331.893031] config - if there is no relations between the [52331.893031] names, then host name confusion attack is possible. Apr 26 06:36:21 192.168.122.209 [52332.027517] [tempesta fw] Configuration processing is completed. Apr 26 06:36:21 192.168.122.209 [52332.075875] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:36:21 192.168.122.209 [52332.103718] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:36:21 192.168.122.209 [52332.131374] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:36:21 192.168.122.209 [52332.191474] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:36:21 192.168.122.209 [52332.231432] [tempesta fw] Tempesta FW is ready Apr 26 06:36:22 192.168.122.209 [52332.771164] [tdb] Close table 'client0.tdb' Apr 26 06:36:22 192.168.122.209 [52332.964384] [tdb] Close table 'sessions0.tdb' Apr 26 06:36:22 192.168.122.209 [52333.190780] [tdb] Close table 'filter0.tdb' Apr 26 06:36:22 192.168.122.209 [52333.191221] [tempesta fw] modules are stopped Apr 26 06:36:22 192.168.122.209 [52333.379883] [tempesta fw] exiting... Apr 26 06:36:23 192.168.122.209 [52333.486086] [tdb] Shutdown Tempesta DB Apr 26 06:36:23 192.168.122.209 [52333.707670] End test: t_wrong_body_length.test_h2_request_wrong_length.RequestMissingBodyLength.test_put_request Apr 26 06:36:23 192.168.122.209 [52333.724849] Start test: t_wrong_body_length.test_h2_request_wrong_length.RequestNegativeBodyLength.test_post_request Apr 26 06:36:24 192.168.122.209 [52334.792049] [tdb] Start Tempesta DB Apr 26 06:36:24 192.168.122.209 [52334.944577] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:36:25 192.168.122.209 [52335.649063] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52335.649063] Maybe that's fine, but it's worth checking the [52335.649063] config - if there is no relations between the [52335.649063] names, then host name confusion attack is possible. Apr 26 06:36:25 192.168.122.209 [52335.783545] [tempesta fw] Configuration processing is completed. Apr 26 06:36:25 192.168.122.209 [52335.842052] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:36:25 192.168.122.209 [52335.869692] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:36:25 192.168.122.209 [52335.897593] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:36:25 192.168.122.209 [52335.943489] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:36:25 192.168.122.209 [52335.991482] [tempesta fw] Tempesta FW is ready Apr 26 06:36:25 192.168.122.209 [52336.118794] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrContent_LengthV input=0x2d('-10'), len=3, off=0 Apr 26 06:36:26 192.168.122.209 [52336.535542] [tdb] Close table 'client0.tdb' Apr 26 06:36:26 192.168.122.209 [52336.747727] [tdb] Close table 'sessions0.tdb' Apr 26 06:36:26 192.168.122.209 [52336.988357] [tdb] Close table 'filter0.tdb' Apr 26 06:36:26 192.168.122.209 [52336.988795] [tempesta fw] modules are stopped Apr 26 06:36:26 192.168.122.209 [52337.181182] [tempesta fw] exiting... Apr 26 06:36:26 192.168.122.209 [52337.305859] [tdb] Shutdown Tempesta DB Apr 26 06:36:27 192.168.122.209 [52337.528215] End test: t_wrong_body_length.test_h2_request_wrong_length.RequestNegativeBodyLength.test_post_request Apr 26 06:36:27 192.168.122.209 [52337.544481] Start test: t_wrong_body_length.test_h2_request_wrong_length.RequestNegativeBodyLength.test_put_request Apr 26 06:36:28 192.168.122.209 [52338.571034] [tdb] Start Tempesta DB Apr 26 06:36:28 192.168.122.209 [52338.706262] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:36:29 192.168.122.209 [52339.465275] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52339.465275] Maybe that's fine, but it's worth checking the [52339.465275] config - if there is no relations between the [52339.465275] names, then host name confusion attack is possible. Apr 26 06:36:29 192.168.122.209 [52339.611654] [tempesta fw] Configuration processing is completed. Apr 26 06:36:29 192.168.122.209 [52339.662158] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:36:29 192.168.122.209 [52339.690601] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:36:29 192.168.122.209 [52339.718738] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:36:29 192.168.122.209 [52339.759574] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:36:29 192.168.122.209 [52339.799553] [tempesta fw] Tempesta FW is ready Apr 26 06:36:29 192.168.122.209 [52339.941039] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrContent_LengthV input=0x2d('-10'), len=3, off=0 Apr 26 06:36:29 192.168.122.209 [52340.382183] [tdb] Close table 'client0.tdb' Apr 26 06:36:30 192.168.122.209 [52340.572629] [tdb] Close table 'sessions0.tdb' Apr 26 06:36:30 192.168.122.209 [52340.795847] [tdb] Close table 'filter0.tdb' Apr 26 06:36:30 192.168.122.209 [52340.796265] [tempesta fw] modules are stopped Apr 26 06:36:30 192.168.122.209 [52340.984545] [tempesta fw] exiting... Apr 26 06:36:30 192.168.122.209 [52341.092710] [tdb] Shutdown Tempesta DB Apr 26 06:36:30 192.168.122.209 [52341.322375] End test: t_wrong_body_length.test_h2_request_wrong_length.RequestNegativeBodyLength.test_put_request Apr 26 06:36:30 192.168.122.209 [52341.341228] Start test: t_wrong_body_length.test_h2_request_wrong_length.RequestSecondBodyLength.test_post_request Apr 26 06:36:31 192.168.122.209 [52342.447108] [tdb] Start Tempesta DB Apr 26 06:36:32 192.168.122.209 [52342.601304] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:36:32 192.168.122.209 [52343.349012] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52343.349012] Maybe that's fine, but it's worth checking the [52343.349012] config - if there is no relations between the [52343.349012] names, then host name confusion attack is possible. Apr 26 06:36:33 192.168.122.209 [52343.491643] [tempesta fw] Configuration processing is completed. Apr 26 06:36:33 192.168.122.209 [52343.549622] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:36:33 192.168.122.209 [52343.580720] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:36:33 192.168.122.209 [52343.608828] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:36:33 192.168.122.209 [52343.659606] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:36:33 192.168.122.209 [52343.704317] [tempesta fw] Tempesta FW is ready Apr 26 06:36:33 192.168.122.209 [52344.240133] [tdb] Close table 'client0.tdb' Apr 26 06:36:33 192.168.122.209 [52344.442435] [tdb] Close table 'sessions0.tdb' Apr 26 06:36:34 192.168.122.209 [52344.667530] [tdb] Close table 'filter0.tdb' Apr 26 06:36:34 192.168.122.209 [52344.667967] [tempesta fw] modules are stopped Apr 26 06:36:34 192.168.122.209 [52344.891828] [tempesta fw] exiting... Apr 26 06:36:34 192.168.122.209 [52345.019288] [tdb] Shutdown Tempesta DB Apr 26 06:36:34 192.168.122.209 [52345.251156] End test: t_wrong_body_length.test_h2_request_wrong_length.RequestSecondBodyLength.test_post_request Apr 26 06:36:34 192.168.122.209 [52345.263456] Start test: t_wrong_body_length.test_h2_request_wrong_length.RequestSecondBodyLength.test_put_request Apr 26 06:36:35 192.168.122.209 [52346.208170] [tdb] Start Tempesta DB Apr 26 06:36:35 192.168.122.209 [52346.339490] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:36:36 192.168.122.209 [52346.972539] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52346.972539] Maybe that's fine, but it's worth checking the [52346.972539] config - if there is no relations between the [52346.972539] names, then host name confusion attack is possible. Apr 26 06:36:36 192.168.122.209 [52347.107683] [tempesta fw] Configuration processing is completed. Apr 26 06:36:36 192.168.122.209 [52347.155997] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:36:36 192.168.122.209 [52347.183799] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:36:36 192.168.122.209 [52347.211763] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:36:36 192.168.122.209 [52347.267664] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:36:36 192.168.122.209 [52347.307610] [tempesta fw] Tempesta FW is ready Apr 26 06:36:37 192.168.122.209 [52347.849074] [tdb] Close table 'client0.tdb' Apr 26 06:36:37 192.168.122.209 [52348.040597] [tdb] Close table 'sessions0.tdb' Apr 26 06:36:37 192.168.122.209 [52348.284230] [tdb] Close table 'filter0.tdb' Apr 26 06:36:37 192.168.122.209 [52348.284676] [tempesta fw] modules are stopped Apr 26 06:36:38 192.168.122.209 [52348.537615] [tempesta fw] exiting... Apr 26 06:36:38 192.168.122.209 [52348.680456] [tdb] Shutdown Tempesta DB Apr 26 06:36:38 192.168.122.209 [52348.928751] End test: t_wrong_body_length.test_h2_request_wrong_length.RequestSecondBodyLength.test_put_request Apr 26 06:36:38 192.168.122.209 [52348.938798] Start test: t_wrong_body_length.test_request_wrong_length.RequestCorrectBodyLength.test_post_request Apr 26 06:36:39 192.168.122.209 [52349.880432] [tdb] Start Tempesta DB Apr 26 06:36:39 192.168.122.209 [52350.022339] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:36:40 192.168.122.209 [52350.712978] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52350.712978] Maybe that's fine, but it's worth checking the [52350.712978] config - if there is no relations between the [52350.712978] names, then host name confusion attack is possible. Apr 26 06:36:40 192.168.122.209 [52350.883732] [tempesta fw] Configuration processing is completed. Apr 26 06:36:40 192.168.122.209 [52350.937926] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:36:40 192.168.122.209 [52350.969048] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:36:40 192.168.122.209 [52350.996911] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:36:40 192.168.122.209 [52351.047727] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:36:40 192.168.122.209 [52351.049422] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:36:40 192.168.122.209 [52351.087665] [tempesta fw] Tempesta FW is ready Apr 26 06:36:41 192.168.122.209 [52351.663013] [tdb] Close table 'client0.tdb' Apr 26 06:36:41 192.168.122.209 [52351.846143] [tdb] Close table 'sessions0.tdb' Apr 26 06:36:41 192.168.122.209 [52352.053604] [tdb] Close table 'filter0.tdb' Apr 26 06:36:41 192.168.122.209 [52352.054013] [tempesta fw] modules are stopped Apr 26 06:36:41 192.168.122.209 [52352.255782] [tempesta fw] exiting... Apr 26 06:36:41 192.168.122.209 [52352.391144] [tdb] Shutdown Tempesta DB Apr 26 06:36:42 192.168.122.209 [52352.597040] End test: t_wrong_body_length.test_request_wrong_length.RequestCorrectBodyLength.test_post_request Apr 26 06:36:42 192.168.122.209 [52352.618334] Start test: t_wrong_body_length.test_request_wrong_length.RequestCorrectBodyLength.test_put_request Apr 26 06:36:43 192.168.122.209 [52353.657368] [tdb] Start Tempesta DB Apr 26 06:36:43 192.168.122.209 [52353.803251] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:36:44 192.168.122.209 [52354.633141] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52354.633141] Maybe that's fine, but it's worth checking the [52354.633141] config - if there is no relations between the [52354.633141] names, then host name confusion attack is possible. Apr 26 06:36:44 192.168.122.209 [52354.815807] [tempesta fw] Configuration processing is completed. Apr 26 06:36:44 192.168.122.209 [52354.870056] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:36:44 192.168.122.209 [52354.898064] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:36:44 192.168.122.209 [52354.926182] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:36:44 192.168.122.209 [52354.983771] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:36:44 192.168.122.209 [52354.985485] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:36:44 192.168.122.209 [52355.023749] [tempesta fw] Tempesta FW is ready Apr 26 06:36:45 192.168.122.209 [52355.590283] [tdb] Close table 'client0.tdb' Apr 26 06:36:45 192.168.122.209 [52355.778728] [tdb] Close table 'sessions0.tdb' Apr 26 06:36:45 192.168.122.209 [52356.001146] [tdb] Close table 'filter0.tdb' Apr 26 06:36:45 192.168.122.209 [52356.001614] [tempesta fw] modules are stopped Apr 26 06:36:45 192.168.122.209 [52356.196335] [tempesta fw] exiting... Apr 26 06:36:45 192.168.122.209 [52356.310204] [tdb] Shutdown Tempesta DB Apr 26 06:36:46 192.168.122.209 [52356.504211] End test: t_wrong_body_length.test_request_wrong_length.RequestCorrectBodyLength.test_put_request Apr 26 06:36:46 192.168.122.209 [52356.518307] Start test: t_wrong_body_length.test_request_wrong_length.RequestDecimalBodyLength.test_post_request Apr 26 06:36:47 192.168.122.209 [52357.626443] [tdb] Start Tempesta DB Apr 26 06:36:47 192.168.122.209 [52357.763696] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:36:48 192.168.122.209 [52358.580887] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52358.580887] Maybe that's fine, but it's worth checking the [52358.580887] config - if there is no relations between the [52358.580887] names, then host name confusion attack is possible. Apr 26 06:36:48 192.168.122.209 [52358.751877] [tempesta fw] Configuration processing is completed. Apr 26 06:36:48 192.168.122.209 [52358.803240] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:36:48 192.168.122.209 [52358.833638] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:36:48 192.168.122.209 [52358.861866] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:36:48 192.168.122.209 [52358.899784] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:36:48 192.168.122.209 [52358.900847] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:36:48 192.168.122.209 [52358.943766] [tempesta fw] Tempesta FW is ready Apr 26 06:36:48 192.168.122.209 [52359.078223] [tempesta fw] Warning: Parser error: state=Req_HdrContent_LengthV input(-8)=0x30('Length: 0.5 [52359.078223] Content-type: text/plain [52359.078223] [52359.078223] PUT / H') data_len=153 off=87 Apr 26 06:36:49 192.168.122.209 [52359.540479] [tdb] Close table 'client0.tdb' Apr 26 06:36:49 192.168.122.209 [52359.724055] [tdb] Close table 'sessions0.tdb' Apr 26 06:36:49 192.168.122.209 [52359.962688] [tdb] Close table 'filter0.tdb' Apr 26 06:36:49 192.168.122.209 [52359.963116] [tempesta fw] modules are stopped Apr 26 06:36:49 192.168.122.209 [52360.193125] [tempesta fw] exiting... Apr 26 06:36:49 192.168.122.209 [52360.313167] [tdb] Shutdown Tempesta DB Apr 26 06:36:50 192.168.122.209 [52360.520282] End test: t_wrong_body_length.test_request_wrong_length.RequestDecimalBodyLength.test_post_request Apr 26 06:36:50 192.168.122.209 [52360.533382] Start test: t_wrong_body_length.test_request_wrong_length.RequestDecimalBodyLength.test_put_request Apr 26 06:36:51 192.168.122.209 [52361.566976] [tdb] Start Tempesta DB Apr 26 06:36:51 192.168.122.209 [52361.701572] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:36:52 192.168.122.209 [52362.497210] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52362.497210] Maybe that's fine, but it's worth checking the [52362.497210] config - if there is no relations between the [52362.497210] names, then host name confusion attack is possible. Apr 26 06:36:52 192.168.122.209 [52362.663891] [tempesta fw] Configuration processing is completed. Apr 26 06:36:52 192.168.122.209 [52362.715567] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:36:52 192.168.122.209 [52362.743631] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:36:52 192.168.122.209 [52362.771734] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:36:52 192.168.122.209 [52362.819859] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:36:52 192.168.122.209 [52362.821561] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:36:52 192.168.122.209 [52362.859807] [tempesta fw] Tempesta FW is ready Apr 26 06:36:52 192.168.122.209 [52362.987791] [tempesta fw] Warning: Parser error: state=Req_HdrContent_LengthV input(-8)=0x30('Length: 0.5 [52362.987791] Content-type: text/plain [52362.987791] [52362.987791] PUT / H') data_len=152 off=86 Apr 26 06:36:52 192.168.122.209 [52363.424949] [tdb] Close table 'client0.tdb' Apr 26 06:36:53 192.168.122.209 [52363.614719] [tdb] Close table 'sessions0.tdb' Apr 26 06:36:53 192.168.122.209 [52363.847996] [tdb] Close table 'filter0.tdb' Apr 26 06:36:53 192.168.122.209 [52363.848436] [tempesta fw] modules are stopped Apr 26 06:36:53 192.168.122.209 [52364.024418] [tempesta fw] exiting... Apr 26 06:36:53 192.168.122.209 [52364.168062] [tdb] Shutdown Tempesta DB Apr 26 06:36:53 192.168.122.209 [52364.388961] End test: t_wrong_body_length.test_request_wrong_length.RequestDecimalBodyLength.test_put_request Apr 26 06:36:53 192.168.122.209 [52364.406345] Start test: t_wrong_body_length.test_request_wrong_length.RequestDuplicateBodyLength.test_post_request Apr 26 06:36:54 192.168.122.209 [52365.443570] [tdb] Start Tempesta DB Apr 26 06:36:55 192.168.122.209 [52365.586697] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:36:55 192.168.122.209 [52366.332822] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52366.332822] Maybe that's fine, but it's worth checking the [52366.332822] config - if there is no relations between the [52366.332822] names, then host name confusion attack is possible. Apr 26 06:36:56 192.168.122.209 [52366.491923] [tempesta fw] Configuration processing is completed. Apr 26 06:36:56 192.168.122.209 [52366.545735] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:36:56 192.168.122.209 [52366.573832] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:36:56 192.168.122.209 [52366.603096] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:36:56 192.168.122.209 [52366.647883] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:36:56 192.168.122.209 [52366.649261] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:36:56 192.168.122.209 [52366.687909] [tempesta fw] Tempesta FW is ready Apr 26 06:36:56 192.168.122.209 [52366.803880] [tempesta fw] Warning: Parser error: state=Req_HdrContent_LengthV input(-8)=0x33('Length: 33, 33 [52366.803880] Content-type: text/plain [52366.803880] [52366.803880] PUT ') data_len=156 off=87 Apr 26 06:36:56 192.168.122.209 [52367.232681] [tdb] Close table 'client0.tdb' Apr 26 06:36:56 192.168.122.209 [52367.422756] [tdb] Close table 'sessions0.tdb' Apr 26 06:36:57 192.168.122.209 [52367.645196] [tdb] Close table 'filter0.tdb' Apr 26 06:36:57 192.168.122.209 [52367.645652] [tempesta fw] modules are stopped Apr 26 06:36:57 192.168.122.209 [52367.848471] [tempesta fw] exiting... Apr 26 06:36:57 192.168.122.209 [52367.950259] [tdb] Shutdown Tempesta DB Apr 26 06:36:57 192.168.122.209 [52368.145419] End test: t_wrong_body_length.test_request_wrong_length.RequestDuplicateBodyLength.test_post_request Apr 26 06:36:57 192.168.122.209 [52368.160371] Start test: t_wrong_body_length.test_request_wrong_length.RequestDuplicateBodyLength.test_put_request Apr 26 06:36:58 192.168.122.209 [52369.218760] [tdb] Start Tempesta DB Apr 26 06:36:58 192.168.122.209 [52369.361427] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:36:59 192.168.122.209 [52370.161297] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52370.161297] Maybe that's fine, but it's worth checking the [52370.161297] config - if there is no relations between the [52370.161297] names, then host name confusion attack is possible. Apr 26 06:36:59 192.168.122.209 [52370.331977] [tempesta fw] Configuration processing is completed. Apr 26 06:36:59 192.168.122.209 [52370.397114] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:36:59 192.168.122.209 [52370.424850] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:36:59 192.168.122.209 [52370.452359] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:37:00 192.168.122.209 [52370.495949] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:37:00 192.168.122.209 [52370.497289] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:37:00 192.168.122.209 [52370.535911] [tempesta fw] Tempesta FW is ready Apr 26 06:37:00 192.168.122.209 [52370.663029] [tempesta fw] Warning: Parser error: state=Req_HdrContent_LengthV input(-8)=0x33('Length: 33, 33 [52370.663029] Content-type: text/plain [52370.663029] [52370.663029] PUT ') data_len=155 off=86 Apr 26 06:37:00 192.168.122.209 [52371.115104] [tdb] Close table 'client0.tdb' Apr 26 06:37:00 192.168.122.209 [52371.304729] [tdb] Close table 'sessions0.tdb' Apr 26 06:37:01 192.168.122.209 [52371.547510] [tdb] Close table 'filter0.tdb' Apr 26 06:37:01 192.168.122.209 [52371.547966] [tempesta fw] modules are stopped Apr 26 06:37:01 192.168.122.209 [52371.762656] [tempesta fw] exiting... Apr 26 06:37:01 192.168.122.209 [52371.885338] [tdb] Shutdown Tempesta DB Apr 26 06:37:01 192.168.122.209 [52372.083849] End test: t_wrong_body_length.test_request_wrong_length.RequestDuplicateBodyLength.test_put_request Apr 26 06:37:01 192.168.122.209 [52372.101527] Start test: t_wrong_body_length.test_request_wrong_length.RequestEmptyBodyLength.test_post_request Apr 26 06:37:02 192.168.122.209 [52373.183902] [tdb] Start Tempesta DB Apr 26 06:37:02 192.168.122.209 [52373.323030] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:37:03 192.168.122.209 [52374.117265] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52374.117265] Maybe that's fine, but it's worth checking the [52374.117265] config - if there is no relations between the [52374.117265] names, then host name confusion attack is possible. Apr 26 06:37:03 192.168.122.209 [52374.296022] [tempesta fw] Configuration processing is completed. Apr 26 06:37:03 192.168.122.209 [52374.346610] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:37:03 192.168.122.209 [52374.376014] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:37:03 192.168.122.209 [52374.403620] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:37:04 192.168.122.209 [52374.464006] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:37:04 192.168.122.209 [52374.465686] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:37:04 192.168.122.209 [52374.503967] [tempesta fw] Tempesta FW is ready Apr 26 06:37:04 192.168.122.209 [52374.631083] [tempesta fw] Warning: Parser error: state=Req_HdrContent_LengthV input(-8)=0xd('Length: [52374.631083] Content-type: text/plain [52374.631083] [52374.631083] PUT / HTTP') data_len=150 off=87 Apr 26 06:37:04 192.168.122.209 [52375.103713] [tdb] Close table 'client0.tdb' Apr 26 06:37:04 192.168.122.209 [52375.290056] [tdb] Close table 'sessions0.tdb' Apr 26 06:37:05 192.168.122.209 [52375.533401] [tdb] Close table 'filter0.tdb' Apr 26 06:37:05 192.168.122.209 [52375.533837] [tempesta fw] modules are stopped Apr 26 06:37:05 192.168.122.209 [52375.724351] [tempesta fw] exiting... Apr 26 06:37:05 192.168.122.209 [52375.859438] [tdb] Shutdown Tempesta DB Apr 26 06:37:05 192.168.122.209 [52376.087005] End test: t_wrong_body_length.test_request_wrong_length.RequestEmptyBodyLength.test_post_request Apr 26 06:37:05 192.168.122.209 [52376.100898] Start test: t_wrong_body_length.test_request_wrong_length.RequestEmptyBodyLength.test_put_request Apr 26 06:37:06 192.168.122.209 [52377.162620] [tdb] Start Tempesta DB Apr 26 06:37:06 192.168.122.209 [52377.306046] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:37:07 192.168.122.209 [52378.125278] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52378.125278] Maybe that's fine, but it's worth checking the [52378.125278] config - if there is no relations between the [52378.125278] names, then host name confusion attack is possible. Apr 26 06:37:07 192.168.122.209 [52378.292093] [tempesta fw] Configuration processing is completed. Apr 26 06:37:07 192.168.122.209 [52378.343507] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:37:07 192.168.122.209 [52378.373327] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:37:07 192.168.122.209 [52378.401878] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:37:07 192.168.122.209 [52378.448062] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:37:07 192.168.122.209 [52378.449489] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:37:08 192.168.122.209 [52378.487965] [tempesta fw] Tempesta FW is ready Apr 26 06:37:08 192.168.122.209 [52378.623267] [tempesta fw] Warning: Parser error: state=Req_HdrContent_LengthV input(-8)=0xd('Length: [52378.623267] Content-type: text/plain [52378.623267] [52378.623267] PUT / HTTP') data_len=149 off=86 Apr 26 06:37:08 192.168.122.209 [52379.035237] [tdb] Close table 'client0.tdb' Apr 26 06:37:08 192.168.122.209 [52379.244474] [tdb] Close table 'sessions0.tdb' Apr 26 06:37:09 192.168.122.209 [52379.496988] [tdb] Close table 'filter0.tdb' Apr 26 06:37:09 192.168.122.209 [52379.497409] [tempesta fw] modules are stopped Apr 26 06:37:09 192.168.122.209 [52379.722440] [tempesta fw] exiting... Apr 26 06:37:09 192.168.122.209 [52379.831986] [tdb] Shutdown Tempesta DB Apr 26 06:37:09 192.168.122.209 [52380.040269] End test: t_wrong_body_length.test_request_wrong_length.RequestEmptyBodyLength.test_put_request Apr 26 06:37:09 192.168.122.209 [52380.051569] Start test: t_wrong_body_length.test_request_wrong_length.RequestInvalidBodyLength.test_post_request Apr 26 06:37:10 192.168.122.209 [52381.115876] [tdb] Start Tempesta DB Apr 26 06:37:10 192.168.122.209 [52381.251698] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:37:11 192.168.122.209 [52381.993375] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52381.993375] Maybe that's fine, but it's worth checking the [52381.993375] config - if there is no relations between the [52381.993375] names, then host name confusion attack is possible. Apr 26 06:37:11 192.168.122.209 [52382.168080] [tempesta fw] Configuration processing is completed. Apr 26 06:37:11 192.168.122.209 [52382.213889] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:37:11 192.168.122.209 [52382.242344] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:37:11 192.168.122.209 [52382.270133] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:37:11 192.168.122.209 [52382.320096] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:37:11 192.168.122.209 [52382.321552] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:37:11 192.168.122.209 [52382.360071] [tempesta fw] Tempesta FW is ready Apr 26 06:37:12 192.168.122.209 [52382.482484] [tempesta fw] Warning: Parser error: state=Req_HdrContent_LengthV input(-8)=0x69('Length: invalid [52382.482484] Content-type: text/plain [52382.482484] [52382.482484] PUT') data_len=157 off=87 Apr 26 06:37:12 192.168.122.209 [52382.934676] [tdb] Close table 'client0.tdb' Apr 26 06:37:12 192.168.122.209 [52383.194563] [tdb] Close table 'sessions0.tdb' Apr 26 06:37:12 192.168.122.209 [52383.418839] [tdb] Close table 'filter0.tdb' Apr 26 06:37:12 192.168.122.209 [52383.419280] [tempesta fw] modules are stopped Apr 26 06:37:13 192.168.122.209 [52383.618615] [tempesta fw] exiting... Apr 26 06:37:13 192.168.122.209 [52383.740500] [tdb] Shutdown Tempesta DB Apr 26 06:37:13 192.168.122.209 [52383.926097] End test: t_wrong_body_length.test_request_wrong_length.RequestInvalidBodyLength.test_post_request Apr 26 06:37:13 192.168.122.209 [52383.938479] Start test: t_wrong_body_length.test_request_wrong_length.RequestInvalidBodyLength.test_put_request Apr 26 06:37:14 192.168.122.209 [52385.002627] [tdb] Start Tempesta DB Apr 26 06:37:14 192.168.122.209 [52385.139617] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:37:15 192.168.122.209 [52385.872945] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52385.872945] Maybe that's fine, but it's worth checking the [52385.872945] config - if there is no relations between the [52385.872945] names, then host name confusion attack is possible. Apr 26 06:37:15 192.168.122.209 [52386.044484] [tempesta fw] Configuration processing is completed. Apr 26 06:37:15 192.168.122.209 [52386.093852] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:37:15 192.168.122.209 [52386.124420] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:37:15 192.168.122.209 [52386.151939] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:37:15 192.168.122.209 [52386.200163] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:37:15 192.168.122.209 [52386.201839] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:37:15 192.168.122.209 [52386.240132] [tempesta fw] Tempesta FW is ready Apr 26 06:37:15 192.168.122.209 [52386.373034] [tempesta fw] Warning: Parser error: state=Req_HdrContent_LengthV input(-8)=0x69('Length: invalid [52386.373034] Content-type: text/plain [52386.373034] [52386.373034] PUT') data_len=156 off=86 Apr 26 06:37:16 192.168.122.209 [52386.814542] [tdb] Close table 'client0.tdb' Apr 26 06:37:16 192.168.122.209 [52387.003942] [tdb] Close table 'sessions0.tdb' Apr 26 06:37:16 192.168.122.209 [52387.250474] [tdb] Close table 'filter0.tdb' Apr 26 06:37:16 192.168.122.209 [52387.250921] [tempesta fw] modules are stopped Apr 26 06:37:17 192.168.122.209 [52387.472268] [tempesta fw] exiting... Apr 26 06:37:17 192.168.122.209 [52387.598086] [tdb] Shutdown Tempesta DB Apr 26 06:37:17 192.168.122.209 [52387.831711] End test: t_wrong_body_length.test_request_wrong_length.RequestInvalidBodyLength.test_put_request Apr 26 06:37:17 192.168.122.209 [52387.847814] Start test: t_wrong_body_length.test_request_wrong_length.RequestLongBodyLength.test_post_request Apr 26 06:37:18 192.168.122.209 [52388.940516] [tdb] Start Tempesta DB Apr 26 06:37:18 192.168.122.209 [52389.081618] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:37:19 192.168.122.209 [52390.004508] [tempesta fw] Configuration processing is completed. Apr 26 06:37:19 192.168.122.209 [52390.061163] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:37:19 192.168.122.209 [52390.088340] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:37:19 192.168.122.209 [52390.115668] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:37:19 192.168.122.209 [52390.176213] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:37:19 192.168.122.209 [52390.212147] [tempesta fw] Tempesta FW is ready Apr 26 06:37:21 192.168.122.209 [52391.770537] [tdb] Close table 'client0.tdb' Apr 26 06:37:21 192.168.122.209 [52391.963296] [tdb] Close table 'sessions0.tdb' Apr 26 06:37:21 192.168.122.209 [52392.210374] [tdb] Close table 'filter0.tdb' Apr 26 06:37:21 192.168.122.209 [52392.210796] [tempesta fw] modules are stopped Apr 26 06:37:21 192.168.122.209 [52392.393080] [tempesta fw] exiting... Apr 26 06:37:22 192.168.122.209 [52392.539247] [tdb] Shutdown Tempesta DB Apr 26 06:37:22 192.168.122.209 [52392.763566] End test: t_wrong_body_length.test_request_wrong_length.RequestLongBodyLength.test_post_request Apr 26 06:37:22 192.168.122.209 [52392.782985] Start test: t_wrong_body_length.test_request_wrong_length.RequestLongBodyLength.test_put_request Apr 26 06:37:23 192.168.122.209 [52393.782462] [tdb] Start Tempesta DB Apr 26 06:37:23 192.168.122.209 [52393.922694] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:37:24 192.168.122.209 [52394.832633] [tempesta fw] Configuration processing is completed. Apr 26 06:37:24 192.168.122.209 [52394.883669] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:37:24 192.168.122.209 [52394.914404] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:37:24 192.168.122.209 [52394.946319] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:37:24 192.168.122.209 [52394.992274] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:37:24 192.168.122.209 [52395.032159] [tempesta fw] Tempesta FW is ready Apr 26 06:37:26 192.168.122.209 [52396.636985] [tdb] Close table 'client0.tdb' Apr 26 06:37:26 192.168.122.209 [52396.845591] [tdb] Close table 'sessions0.tdb' Apr 26 06:37:26 192.168.122.209 [52397.081671] [tdb] Close table 'filter0.tdb' Apr 26 06:37:26 192.168.122.209 [52397.082125] [tempesta fw] modules are stopped Apr 26 06:37:26 192.168.122.209 [52397.243201] [tempesta fw] exiting... Apr 26 06:37:26 192.168.122.209 [52397.370844] [tdb] Shutdown Tempesta DB Apr 26 06:37:27 192.168.122.209 [52397.577610] End test: t_wrong_body_length.test_request_wrong_length.RequestLongBodyLength.test_put_request Apr 26 06:37:27 192.168.122.209 [52397.592401] Start test: t_wrong_body_length.test_request_wrong_length.RequestNegativeBodyLength.test_post_request Apr 26 06:37:28 192.168.122.209 [52398.661140] [tdb] Start Tempesta DB Apr 26 06:37:28 192.168.122.209 [52398.808611] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:37:29 192.168.122.209 [52399.593584] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52399.593584] Maybe that's fine, but it's worth checking the [52399.593584] config - if there is no relations between the [52399.593584] names, then host name confusion attack is possible. Apr 26 06:37:29 192.168.122.209 [52399.768364] [tempesta fw] Configuration processing is completed. Apr 26 06:37:29 192.168.122.209 [52399.817756] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:37:29 192.168.122.209 [52399.845644] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:37:29 192.168.122.209 [52399.874641] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:37:29 192.168.122.209 [52399.944343] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:37:29 192.168.122.209 [52399.946078] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:37:29 192.168.122.209 [52399.984284] [tempesta fw] Tempesta FW is ready Apr 26 06:37:29 192.168.122.209 [52400.116446] [tempesta fw] Warning: Parser error: state=Req_HdrContent_LengthV input(-8)=0x2d('Length: -10 [52400.116446] Content-type: text/plain [52400.116446] [52400.116446] PUT / H') data_len=153 off=87 Apr 26 06:37:30 192.168.122.209 [52400.565404] [tdb] Close table 'client0.tdb' Apr 26 06:37:30 192.168.122.209 [52400.760035] [tdb] Close table 'sessions0.tdb' Apr 26 06:37:30 192.168.122.209 [52400.987581] [tdb] Close table 'filter0.tdb' Apr 26 06:37:30 192.168.122.209 [52400.988004] [tempesta fw] modules are stopped Apr 26 06:37:30 192.168.122.209 [52401.183025] [tempesta fw] exiting... Apr 26 06:37:30 192.168.122.209 [52401.307595] [tdb] Shutdown Tempesta DB Apr 26 06:37:31 192.168.122.209 [52401.543524] End test: t_wrong_body_length.test_request_wrong_length.RequestNegativeBodyLength.test_post_request Apr 26 06:37:31 192.168.122.209 [52401.557304] Start test: t_wrong_body_length.test_request_wrong_length.RequestNegativeBodyLength.test_put_request Apr 26 06:37:32 192.168.122.209 [52402.594645] [tdb] Start Tempesta DB Apr 26 06:37:32 192.168.122.209 [52402.721704] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:37:33 192.168.122.209 [52403.553546] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52403.553546] Maybe that's fine, but it's worth checking the [52403.553546] config - if there is no relations between the [52403.553546] names, then host name confusion attack is possible. Apr 26 06:37:33 192.168.122.209 [52403.724550] [tempesta fw] Configuration processing is completed. Apr 26 06:37:33 192.168.122.209 [52403.778170] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:37:33 192.168.122.209 [52403.807472] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:37:33 192.168.122.209 [52403.834651] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:37:33 192.168.122.209 [52403.884376] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:37:33 192.168.122.209 [52403.886067] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:37:33 192.168.122.209 [52403.948315] [tempesta fw] Tempesta FW is ready Apr 26 06:37:33 192.168.122.209 [52404.061763] [tempesta fw] Warning: Parser error: state=Req_HdrContent_LengthV input(-8)=0x2d('Length: -10 [52404.061763] Content-type: text/plain [52404.061763] [52404.061763] PUT / H') data_len=152 off=86 Apr 26 06:37:34 192.168.122.209 [52404.480300] [tdb] Close table 'client0.tdb' Apr 26 06:37:34 192.168.122.209 [52404.670611] [tdb] Close table 'sessions0.tdb' Apr 26 06:37:34 192.168.122.209 [52404.897332] [tdb] Close table 'filter0.tdb' Apr 26 06:37:34 192.168.122.209 [52404.897758] [tempesta fw] modules are stopped Apr 26 06:37:34 192.168.122.209 [52405.080786] [tempesta fw] exiting... Apr 26 06:37:34 192.168.122.209 [52405.202435] [tdb] Shutdown Tempesta DB Apr 26 06:37:35 192.168.122.209 [52405.467165] End test: t_wrong_body_length.test_request_wrong_length.RequestNegativeBodyLength.test_put_request Apr 26 06:37:35 192.168.122.209 [52405.481983] Start test: t_wrong_body_length.test_request_wrong_length.RequestSecondBodyLength.test_post_request Apr 26 06:37:36 192.168.122.209 [52406.520410] [tdb] Start Tempesta DB Apr 26 06:37:36 192.168.122.209 [52406.651959] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:37:36 192.168.122.209 [52407.445689] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52407.445689] Maybe that's fine, but it's worth checking the [52407.445689] config - if there is no relations between the [52407.445689] names, then host name confusion attack is possible. Apr 26 06:37:37 192.168.122.209 [52407.624401] [tempesta fw] Configuration processing is completed. Apr 26 06:37:37 192.168.122.209 [52407.671831] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:37:37 192.168.122.209 [52407.700135] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:37:37 192.168.122.209 [52407.727820] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:37:37 192.168.122.209 [52407.772422] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:37:37 192.168.122.209 [52407.773977] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:37:37 192.168.122.209 [52407.816444] [tempesta fw] Tempesta FW is ready Apr 26 06:37:37 192.168.122.209 [52407.958921] [tempesta fw] Warning: Parser error: state=Req_HdrContent_LengthV input(-8)=0x33('Length: 33 [52407.958921] [52407.958921] PUT / HTTP/1.1 [52407.958921] Host: localhost [52407.958921] ') data_len=172 off=133 Apr 26 06:37:37 192.168.122.209 [52408.364166] [tdb] Close table 'client0.tdb' Apr 26 06:37:38 192.168.122.209 [52408.562487] [tdb] Close table 'sessions0.tdb' Apr 26 06:37:38 192.168.122.209 [52408.787784] [tdb] Close table 'filter0.tdb' Apr 26 06:37:38 192.168.122.209 [52408.788221] [tempesta fw] modules are stopped Apr 26 06:37:38 192.168.122.209 [52409.049034] [tempesta fw] exiting... Apr 26 06:37:38 192.168.122.209 [52409.142639] [tdb] Shutdown Tempesta DB Apr 26 06:37:38 192.168.122.209 [52409.350544] End test: t_wrong_body_length.test_request_wrong_length.RequestSecondBodyLength.test_post_request Apr 26 06:37:38 192.168.122.209 [52409.366460] Start test: t_wrong_body_length.test_request_wrong_length.RequestSecondBodyLength.test_put_request Apr 26 06:37:39 192.168.122.209 [52410.428179] [tdb] Start Tempesta DB Apr 26 06:37:40 192.168.122.209 [52410.563555] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:37:40 192.168.122.209 [52411.369731] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52411.369731] Maybe that's fine, but it's worth checking the [52411.369731] config - if there is no relations between the [52411.369731] names, then host name confusion attack is possible. Apr 26 06:37:41 192.168.122.209 [52411.544477] [tempesta fw] Configuration processing is completed. Apr 26 06:37:41 192.168.122.209 [52411.595322] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:37:41 192.168.122.209 [52411.625663] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:37:41 192.168.122.209 [52411.653633] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:37:41 192.168.122.209 [52411.696473] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:37:41 192.168.122.209 [52411.697803] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:37:41 192.168.122.209 [52411.748415] [tempesta fw] Tempesta FW is ready Apr 26 06:37:41 192.168.122.209 [52411.891115] [tempesta fw] Warning: Parser error: state=Req_HdrContent_LengthV input(-8)=0x33('Length: 33 [52411.891115] [52411.891115] PUT / HTTP/1.1 [52411.891115] Host: localhost [52411.891115] ') data_len=171 off=132 Apr 26 06:37:41 192.168.122.209 [52412.278222] [tdb] Close table 'client0.tdb' Apr 26 06:37:42 192.168.122.209 [52412.467220] [tdb] Close table 'sessions0.tdb' Apr 26 06:37:42 192.168.122.209 [52412.734328] [tdb] Close table 'filter0.tdb' Apr 26 06:37:42 192.168.122.209 [52412.735269] [tempesta fw] modules are stopped Apr 26 06:37:42 192.168.122.209 [52412.926987] [tempesta fw] exiting... Apr 26 06:37:42 192.168.122.209 [52413.059303] [tdb] Shutdown Tempesta DB Apr 26 06:37:42 192.168.122.209 [52413.290659] End test: t_wrong_body_length.test_request_wrong_length.RequestSecondBodyLength.test_put_request Apr 26 06:37:42 192.168.122.209 [52413.307938] Start test: t_wrong_body_length.test_response_wrong_length.H2CachedResponseMissingContentLength.test Apr 26 06:37:43 192.168.122.209 [52414.355594] [tdb] Start Tempesta DB Apr 26 06:37:44 192.168.122.209 [52414.494011] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:37:44 192.168.122.209 [52415.153526] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52415.153526] Maybe that's fine, but it's worth checking the [52415.153526] config - if there is no relations between the [52415.153526] names, then host name confusion attack is possible. Apr 26 06:37:44 192.168.122.209 [52415.308548] [tempesta fw] Configuration processing is completed. Apr 26 06:37:44 192.168.122.209 [52415.359335] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:37:45 192.168.122.209 [52415.787188] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:37:45 192.168.122.209 [52415.817837] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:37:45 192.168.122.209 [52415.849028] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:37:45 192.168.122.209 [52415.892523] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:37:45 192.168.122.209 [52415.936476] [tempesta fw] Tempesta FW is ready Apr 26 06:37:46 192.168.122.209 [52416.519482] [tdb] Close table 'client0.tdb' Apr 26 06:37:46 192.168.122.209 [52416.697079] [tdb] Close table 'sessions0.tdb' Apr 26 06:37:49 192.168.122.209 [52419.980312] [tdb] Close table 'cache0.tdb' Apr 26 06:37:49 192.168.122.209 [52420.203812] [tdb] Close table 'filter0.tdb' Apr 26 06:37:49 192.168.122.209 [52420.204257] [tempesta fw] modules are stopped Apr 26 06:37:49 192.168.122.209 [52420.421935] [tempesta fw] exiting... Apr 26 06:37:50 192.168.122.209 [52420.548214] [tdb] Shutdown Tempesta DB Apr 26 06:37:50 192.168.122.209 [52420.768751] End test: t_wrong_body_length.test_response_wrong_length.H2CachedResponseMissingContentLength.test Apr 26 06:37:50 192.168.122.209 [52420.792363] Start test: t_wrong_body_length.test_response_wrong_length.H2ResponseMissingEmptyBodyLength.test Apr 26 06:37:51 192.168.122.209 [52421.815919] [tdb] Start Tempesta DB Apr 26 06:37:51 192.168.122.209 [52421.950647] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:37:53 192.168.122.209 [52423.485913] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52423.485913] Maybe that's fine, but it's worth checking the [52423.485913] config - if there is no relations between the [52423.485913] names, then host name confusion attack is possible. Apr 26 06:37:53 192.168.122.209 [52423.664682] [tempesta fw] Configuration processing is completed. Apr 26 06:37:53 192.168.122.209 [52423.718329] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:37:53 192.168.122.209 [52423.748783] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:37:53 192.168.122.209 [52423.778524] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:37:53 192.168.122.209 [52423.836647] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:37:53 192.168.122.209 [52423.838427] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:37:53 192.168.122.209 [52423.888576] [tempesta fw] Tempesta FW is ready Apr 26 06:37:54 192.168.122.209 [52424.488195] [tdb] Close table 'client0.tdb' Apr 26 06:37:54 192.168.122.209 [52424.687056] [tdb] Close table 'sessions0.tdb' Apr 26 06:37:54 192.168.122.209 [52424.915596] [tdb] Close table 'filter0.tdb' Apr 26 06:37:54 192.168.122.209 [52424.916027] [tempesta fw] modules are stopped Apr 26 06:37:54 192.168.122.209 [52425.142887] [tempesta fw] exiting... Apr 26 06:37:54 192.168.122.209 [52425.290289] [tdb] Shutdown Tempesta DB Apr 26 06:37:55 192.168.122.209 [52425.530392] End test: t_wrong_body_length.test_response_wrong_length.H2ResponseMissingEmptyBodyLength.test Apr 26 06:37:55 192.168.122.209 [52425.546371] Start test: t_wrong_body_length.test_response_wrong_length.ResponseContentLengthBase.test Apr 26 06:37:55 192.168.122.209 [52425.561510] End test: t_wrong_body_length.test_response_wrong_length.ResponseContentLengthBase.test Apr 26 06:37:55 192.168.122.209 [52425.580218] Start test: t_wrong_body_length.test_response_wrong_length.ResponseCorrectBodyLength.test Apr 26 06:37:56 192.168.122.209 [52426.652172] [tdb] Start Tempesta DB Apr 26 06:37:56 192.168.122.209 [52426.808558] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:37:57 192.168.122.209 [52427.601286] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52427.601286] Maybe that's fine, but it's worth checking the [52427.601286] config - if there is no relations between the [52427.601286] names, then host name confusion attack is possible. Apr 26 06:37:57 192.168.122.209 [52427.772674] [tempesta fw] Configuration processing is completed. Apr 26 06:37:57 192.168.122.209 [52427.823037] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:37:57 192.168.122.209 [52427.852514] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:37:57 192.168.122.209 [52427.880767] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:37:57 192.168.122.209 [52427.928676] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:37:57 192.168.122.209 [52427.930498] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:37:57 192.168.122.209 [52427.968623] [tempesta fw] Tempesta FW is ready Apr 26 06:37:58 192.168.122.209 [52428.548115] [tdb] Close table 'client0.tdb' Apr 26 06:37:58 192.168.122.209 [52428.741670] [tdb] Close table 'sessions0.tdb' Apr 26 06:37:58 192.168.122.209 [52428.979527] [tdb] Close table 'filter0.tdb' Apr 26 06:37:58 192.168.122.209 [52428.979961] [tempesta fw] modules are stopped Apr 26 06:37:58 192.168.122.209 [52429.160360] [tempesta fw] exiting... Apr 26 06:37:58 192.168.122.209 [52429.301717] [tdb] Shutdown Tempesta DB Apr 26 06:37:59 192.168.122.209 [52429.511831] End test: t_wrong_body_length.test_response_wrong_length.ResponseCorrectBodyLength.test Apr 26 06:37:59 192.168.122.209 [52429.527199] Start test: t_wrong_body_length.test_response_wrong_length.ResponseCorrectEmptyBodyLength.test Apr 26 06:38:00 192.168.122.209 [52430.579138] [tdb] Start Tempesta DB Apr 26 06:38:00 192.168.122.209 [52430.724825] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:38:01 192.168.122.209 [52431.502162] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52431.502162] Maybe that's fine, but it's worth checking the [52431.502162] config - if there is no relations between the [52431.502162] names, then host name confusion attack is possible. Apr 26 06:38:01 192.168.122.209 [52431.656762] [tempesta fw] Configuration processing is completed. Apr 26 06:38:01 192.168.122.209 [52431.707185] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:38:01 192.168.122.209 [52431.739701] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:38:01 192.168.122.209 [52431.767634] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:38:01 192.168.122.209 [52431.824671] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:38:01 192.168.122.209 [52431.825842] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:38:01 192.168.122.209 [52431.872676] [tempesta fw] Tempesta FW is ready Apr 26 06:38:01 192.168.122.209 [52432.416892] [tdb] Close table 'client0.tdb' Apr 26 06:38:02 192.168.122.209 [52432.626229] [tdb] Close table 'sessions0.tdb' Apr 26 06:38:02 192.168.122.209 [52432.856674] [tdb] Close table 'filter0.tdb' Apr 26 06:38:02 192.168.122.209 [52432.857126] [tempesta fw] modules are stopped Apr 26 06:38:02 192.168.122.209 [52433.044044] [tempesta fw] exiting... Apr 26 06:38:02 192.168.122.209 [52433.172922] [tdb] Shutdown Tempesta DB Apr 26 06:38:02 192.168.122.209 [52433.381163] End test: t_wrong_body_length.test_response_wrong_length.ResponseCorrectEmptyBodyLength.test Apr 26 06:38:02 192.168.122.209 [52433.394003] Start test: t_wrong_body_length.test_response_wrong_length.ResponseDecimalBodyLength.test Apr 26 06:38:04 192.168.122.209 [52434.501152] [tdb] Start Tempesta DB Apr 26 06:38:04 192.168.122.209 [52434.633222] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:38:04 192.168.122.209 [52435.430125] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52435.430125] Maybe that's fine, but it's worth checking the [52435.430125] config - if there is no relations between the [52435.430125] names, then host name confusion attack is possible. Apr 26 06:38:05 192.168.122.209 [52435.612812] [tempesta fw] Configuration processing is completed. Apr 26 06:38:05 192.168.122.209 [52435.661696] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:38:05 192.168.122.209 [52435.689961] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:38:05 192.168.122.209 [52435.717618] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:38:05 192.168.122.209 [52435.768768] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:38:05 192.168.122.209 [52435.770157] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:38:05 192.168.122.209 [52435.816732] [tempesta fw] Tempesta FW is ready Apr 26 06:38:05 192.168.122.209 [52435.942287] [tempesta fw] Warning: Parser error: state=Resp_HdrContent_LengthV input(-8)=0x30('length: 0.5 [52435.942287] Content-type: text/html [52435.942287] Last-Modif') data_len=139 off=57 Apr 26 06:38:05 192.168.122.209 [52435.943807] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 06:38:05 192.168.122.209 [52436.386520] [tdb] Close table 'client0.tdb' Apr 26 06:38:06 192.168.122.209 [52436.585359] [tdb] Close table 'sessions0.tdb' Apr 26 06:38:06 192.168.122.209 [52436.818000] [tdb] Close table 'filter0.tdb' Apr 26 06:38:06 192.168.122.209 [52436.818404] [tempesta fw] modules are stopped Apr 26 06:38:06 192.168.122.209 [52437.009187] [tempesta fw] exiting... Apr 26 06:38:06 192.168.122.209 [52437.135768] [tdb] Shutdown Tempesta DB Apr 26 06:38:06 192.168.122.209 [52437.337893] End test: t_wrong_body_length.test_response_wrong_length.ResponseDecimalBodyLength.test Apr 26 06:38:06 192.168.122.209 [52437.358059] Start test: t_wrong_body_length.test_response_wrong_length.ResponseDuplicateBodyLength.test Apr 26 06:38:07 192.168.122.209 [52438.453679] [tdb] Start Tempesta DB Apr 26 06:38:08 192.168.122.209 [52438.582786] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:38:08 192.168.122.209 [52439.374171] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52439.374171] Maybe that's fine, but it's worth checking the [52439.374171] config - if there is no relations between the [52439.374171] names, then host name confusion attack is possible. Apr 26 06:38:09 192.168.122.209 [52439.532887] [tempesta fw] Configuration processing is completed. Apr 26 06:38:09 192.168.122.209 [52439.588818] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:38:09 192.168.122.209 [52439.619195] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:38:09 192.168.122.209 [52439.647292] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:38:09 192.168.122.209 [52439.696823] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:38:09 192.168.122.209 [52439.698550] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:38:09 192.168.122.209 [52439.736769] [tempesta fw] Tempesta FW is ready Apr 26 06:38:09 192.168.122.209 [52439.859165] [tempesta fw] Warning: Parser error: state=Resp_HdrContent_LengthV input(-8)=0x34('length: 4, 4 [52439.859165] Content-type: text/html [52439.859165] Last-Modi') data_len=140 off=57 Apr 26 06:38:09 192.168.122.209 [52439.863914] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 06:38:09 192.168.122.209 [52440.310317] [tdb] Close table 'client0.tdb' Apr 26 06:38:10 192.168.122.209 [52440.502193] [tdb] Close table 'sessions0.tdb' Apr 26 06:38:10 192.168.122.209 [52440.733167] [tdb] Close table 'filter0.tdb' Apr 26 06:38:10 192.168.122.209 [52440.733640] [tempesta fw] modules are stopped Apr 26 06:38:10 192.168.122.209 [52440.925208] [tempesta fw] exiting... Apr 26 06:38:10 192.168.122.209 [52441.072611] [tdb] Shutdown Tempesta DB Apr 26 06:38:10 192.168.122.209 [52441.294862] End test: t_wrong_body_length.test_response_wrong_length.ResponseDuplicateBodyLength.test Apr 26 06:38:10 192.168.122.209 [52441.308234] Start test: t_wrong_body_length.test_response_wrong_length.ResponseEmptyBodyLength.test Apr 26 06:38:11 192.168.122.209 [52442.422096] [tdb] Start Tempesta DB Apr 26 06:38:12 192.168.122.209 [52442.553421] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:38:12 192.168.122.209 [52443.349949] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52443.349949] Maybe that's fine, but it's worth checking the [52443.349949] config - if there is no relations between the [52443.349949] names, then host name confusion attack is possible. Apr 26 06:38:13 192.168.122.209 [52443.532918] [tempesta fw] Configuration processing is completed. Apr 26 06:38:13 192.168.122.209 [52443.588894] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:38:13 192.168.122.209 [52443.616577] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:38:13 192.168.122.209 [52443.644339] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:38:13 192.168.122.209 [52443.692873] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:38:13 192.168.122.209 [52443.694312] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:38:13 192.168.122.209 [52443.736819] [tempesta fw] Tempesta FW is ready Apr 26 06:38:13 192.168.122.209 [52443.860253] [tempesta fw] Warning: Parser error: state=Resp_HdrContent_LengthV input(-8)=0xd('length: [52443.860253] Content-type: text/html [52443.860253] Last-Modified') data_len=136 off=57 Apr 26 06:38:13 192.168.122.209 [52443.865060] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 06:38:13 192.168.122.209 [52444.305957] [tdb] Close table 'client0.tdb' Apr 26 06:38:14 192.168.122.209 [52444.514109] [tdb] Close table 'sessions0.tdb' Apr 26 06:38:14 192.168.122.209 [52444.746095] [tdb] Close table 'filter0.tdb' Apr 26 06:38:14 192.168.122.209 [52444.746524] [tempesta fw] modules are stopped Apr 26 06:38:14 192.168.122.209 [52444.973593] [tempesta fw] exiting... Apr 26 06:38:14 192.168.122.209 [52445.111167] [tdb] Shutdown Tempesta DB Apr 26 06:38:14 192.168.122.209 [52445.331793] End test: t_wrong_body_length.test_response_wrong_length.ResponseEmptyBodyLength.test Apr 26 06:38:14 192.168.122.209 [52445.349825] Start test: t_wrong_body_length.test_response_wrong_length.ResponseForbiddenBodyLength.test Apr 26 06:38:15 192.168.122.209 [52446.424005] [tdb] Start Tempesta DB Apr 26 06:38:16 192.168.122.209 [52446.569885] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:38:16 192.168.122.209 [52447.301538] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52447.301538] Maybe that's fine, but it's worth checking the [52447.301538] config - if there is no relations between the [52447.301538] names, then host name confusion attack is possible. Apr 26 06:38:17 192.168.122.209 [52447.476931] [tempesta fw] Configuration processing is completed. Apr 26 06:38:17 192.168.122.209 [52447.533699] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:38:17 192.168.122.209 [52447.563250] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:38:17 192.168.122.209 [52447.590941] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:38:17 192.168.122.209 [52447.640880] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:38:17 192.168.122.209 [52447.641877] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:38:17 192.168.122.209 [52447.680876] [tempesta fw] Tempesta FW is ready Apr 26 06:38:17 192.168.122.209 [52448.251753] [tdb] Close table 'client0.tdb' Apr 26 06:38:17 192.168.122.209 [52448.460794] [tdb] Close table 'sessions0.tdb' Apr 26 06:38:18 192.168.122.209 [52448.707198] [tdb] Close table 'filter0.tdb' Apr 26 06:38:18 192.168.122.209 [52448.707647] [tempesta fw] modules are stopped Apr 26 06:38:18 192.168.122.209 [52448.949879] [tempesta fw] exiting... Apr 26 06:38:18 192.168.122.209 [52449.077618] [tdb] Shutdown Tempesta DB Apr 26 06:38:18 192.168.122.209 [52449.275013] End test: t_wrong_body_length.test_response_wrong_length.ResponseForbiddenBodyLength.test Apr 26 06:38:18 192.168.122.209 [52449.285932] Start test: t_wrong_body_length.test_response_wrong_length.ResponseInvalidBodyLength.test Apr 26 06:38:19 192.168.122.209 [52450.350432] [tdb] Start Tempesta DB Apr 26 06:38:20 192.168.122.209 [52450.480032] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:38:20 192.168.122.209 [52451.247101] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52451.247101] Maybe that's fine, but it's worth checking the [52451.247101] config - if there is no relations between the [52451.247101] names, then host name confusion attack is possible. Apr 26 06:38:20 192.168.122.209 [52451.401006] [tempesta fw] Configuration processing is completed. Apr 26 06:38:20 192.168.122.209 [52451.451315] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:38:21 192.168.122.209 [52451.479287] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:38:21 192.168.122.209 [52451.516263] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:38:21 192.168.122.209 [52451.560934] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:38:21 192.168.122.209 [52451.562384] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:38:21 192.168.122.209 [52451.600913] [tempesta fw] Tempesta FW is ready Apr 26 06:38:21 192.168.122.209 [52451.727132] [tempesta fw] Warning: Parser error: state=Resp_HdrContent_LengthV input(-8)=0x69('length: invalid [52451.727132] Content-type: text/html [52451.727132] Last-M') data_len=143 off=57 Apr 26 06:38:21 192.168.122.209 [52451.729057] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 06:38:21 192.168.122.209 [52452.158006] [tdb] Close table 'client0.tdb' Apr 26 06:38:21 192.168.122.209 [52452.357739] [tdb] Close table 'sessions0.tdb' Apr 26 06:38:22 192.168.122.209 [52452.595181] [tdb] Close table 'filter0.tdb' Apr 26 06:38:22 192.168.122.209 [52452.595611] [tempesta fw] modules are stopped Apr 26 06:38:22 192.168.122.209 [52452.801592] [tempesta fw] exiting... Apr 26 06:38:22 192.168.122.209 [52452.931816] [tdb] Shutdown Tempesta DB Apr 26 06:38:22 192.168.122.209 [52453.155891] End test: t_wrong_body_length.test_response_wrong_length.ResponseInvalidBodyLength.test Apr 26 06:38:22 192.168.122.209 [52453.177594] Start test: t_wrong_body_length.test_response_wrong_length.ResponseMissingEmptyBodyLength.test Apr 26 06:38:23 192.168.122.209 [52454.180202] [tdb] Start Tempesta DB Apr 26 06:38:23 192.168.122.209 [52454.326823] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:38:24 192.168.122.209 [52455.129951] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52455.129951] Maybe that's fine, but it's worth checking the [52455.129951] config - if there is no relations between the [52455.129951] names, then host name confusion attack is possible. Apr 26 06:38:24 192.168.122.209 [52455.308994] [tempesta fw] Configuration processing is completed. Apr 26 06:38:24 192.168.122.209 [52455.363724] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:38:24 192.168.122.209 [52455.397516] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:38:24 192.168.122.209 [52455.426429] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:38:25 192.168.122.209 [52455.468962] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:38:25 192.168.122.209 [52455.470034] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:38:25 192.168.122.209 [52455.520970] [tempesta fw] Tempesta FW is ready Apr 26 06:38:25 192.168.122.209 [52456.060512] [tdb] Close table 'client0.tdb' Apr 26 06:38:25 192.168.122.209 [52456.252787] [tdb] Close table 'sessions0.tdb' Apr 26 06:38:26 192.168.122.209 [52456.509056] [tdb] Close table 'filter0.tdb' Apr 26 06:38:26 192.168.122.209 [52456.509504] [tempesta fw] modules are stopped Apr 26 06:38:26 192.168.122.209 [52456.692975] [tempesta fw] exiting... Apr 26 06:38:26 192.168.122.209 [52456.821904] [tdb] Shutdown Tempesta DB Apr 26 06:38:26 192.168.122.209 [52457.034811] End test: t_wrong_body_length.test_response_wrong_length.ResponseMissingEmptyBodyLength.test Apr 26 06:38:26 192.168.122.209 [52457.050005] Start test: t_wrong_body_length.test_response_wrong_length.ResponseNegativeBodyLength.test Apr 26 06:38:27 192.168.122.209 [52458.130842] [tdb] Start Tempesta DB Apr 26 06:38:27 192.168.122.209 [52458.262954] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:38:28 192.168.122.209 [52459.022346] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52459.022346] Maybe that's fine, but it's worth checking the [52459.022346] config - if there is no relations between the [52459.022346] names, then host name confusion attack is possible. Apr 26 06:38:28 192.168.122.209 [52459.204993] [tempesta fw] Configuration processing is completed. Apr 26 06:38:28 192.168.122.209 [52459.262974] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:38:28 192.168.122.209 [52459.290282] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:38:28 192.168.122.209 [52459.318043] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:38:28 192.168.122.209 [52459.373055] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:38:28 192.168.122.209 [52459.374803] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:38:28 192.168.122.209 [52459.413013] [tempesta fw] Tempesta FW is ready Apr 26 06:38:29 192.168.122.209 [52459.545805] [tempesta fw] Warning: Parser error: state=Resp_HdrContent_LengthV input(-8)=0x2d('length: -4 [52459.545805] Content-type: text/html [52459.545805] Last-Modifi') data_len=138 off=57 Apr 26 06:38:29 192.168.122.209 [52459.550535] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 06:38:29 192.168.122.209 [52460.000768] [tdb] Close table 'client0.tdb' Apr 26 06:38:29 192.168.122.209 [52460.193457] [tdb] Close table 'sessions0.tdb' Apr 26 06:38:29 192.168.122.209 [52460.403233] [tdb] Close table 'filter0.tdb' Apr 26 06:38:29 192.168.122.209 [52460.403675] [tempesta fw] modules are stopped Apr 26 06:38:30 192.168.122.209 [52460.636185] [tempesta fw] exiting... Apr 26 06:38:30 192.168.122.209 [52460.748093] [tdb] Shutdown Tempesta DB Apr 26 06:38:30 192.168.122.209 [52460.965655] End test: t_wrong_body_length.test_response_wrong_length.ResponseNegativeBodyLength.test Apr 26 06:38:30 192.168.122.209 [52460.977806] Start test: t_wrong_body_length.test_response_wrong_length.ResponseSecondBodyLength.test Apr 26 06:38:31 192.168.122.209 [52462.044351] [tdb] Start Tempesta DB Apr 26 06:38:31 192.168.122.209 [52462.191736] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:38:32 192.168.122.209 [52462.933573] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52462.933573] Maybe that's fine, but it's worth checking the [52462.933573] config - if there is no relations between the [52462.933573] names, then host name confusion attack is possible. Apr 26 06:38:32 192.168.122.209 [52463.097138] [tempesta fw] Configuration processing is completed. Apr 26 06:38:32 192.168.122.209 [52463.146363] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:38:32 192.168.122.209 [52463.178498] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:38:32 192.168.122.209 [52463.207481] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:38:32 192.168.122.209 [52463.261116] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:38:32 192.168.122.209 [52463.262701] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:38:32 192.168.122.209 [52463.301073] [tempesta fw] Tempesta FW is ready Apr 26 06:38:32 192.168.122.209 [52463.424536] [tempesta fw] Warning: Parser error: state=Resp_HdrContent_LengthV input(-8)=0x34('length: 4 [52463.424536] [52463.424536] text') data_len=156 off=147 Apr 26 06:38:32 192.168.122.209 [52463.426715] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 06:38:33 192.168.122.209 [52463.856549] [tdb] Close table 'client0.tdb' Apr 26 06:38:33 192.168.122.209 [52464.041834] [tdb] Close table 'sessions0.tdb' Apr 26 06:38:33 192.168.122.209 [52464.265348] [tdb] Close table 'filter0.tdb' Apr 26 06:38:33 192.168.122.209 [52464.265759] [tempesta fw] modules are stopped Apr 26 06:38:33 192.168.122.209 [52464.458246] [tempesta fw] exiting... Apr 26 06:38:34 192.168.122.209 [52464.597710] [tdb] Shutdown Tempesta DB Apr 26 06:38:34 192.168.122.209 [52464.803769] End test: t_wrong_body_length.test_response_wrong_length.ResponseSecondBodyLength.test Apr 26 06:38:34 192.168.122.209 [52464.821425] Start test: ws.test_ws_ping.CacheTest.test Apr 26 06:38:35 192.168.122.209 [52465.907321] [tdb] Start Tempesta DB Apr 26 06:38:35 192.168.122.209 [52466.037518] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:38:36 192.168.122.209 [52467.025142] [tempesta fw] Configuration processing is completed. Apr 26 06:38:36 192.168.122.209 [52467.075517] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:38:37 192.168.122.209 [52467.533859] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:38:37 192.168.122.209 [52467.573524] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:38:37 192.168.122.209 [52467.603646] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:38:37 192.168.122.209 [52467.673224] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 06:38:37 192.168.122.209 [52467.713259] [tempesta fw] Tempesta FW is ready Apr 26 06:38:37 192.168.122.209 [52467.934989] [tempesta fw] 127.0.0.1 "default" "GET / HTTP/1.1" 101 0 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/99.0.4844.51 Safari/537.36" "ja5t=0" "ja5h=f47f0107000c0700" Apr 26 06:38:39 192.168.122.209 [52469.915486] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18099: 1 tries, keep trying... Apr 26 06:38:39 192.168.122.209 [52469.915579] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18099: 1 tries, keep trying... Apr 26 06:38:39 192.168.122.209 [52469.918697] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18099: 1 tries, keep trying... Apr 26 06:38:39 192.168.122.209 [52469.919191] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18099: 1 tries, keep trying... Apr 26 06:38:39 192.168.122.209 [52469.919299] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18099: 1 tries, keep trying... Apr 26 06:38:39 192.168.122.209 [52469.919504] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18099: 1 tries, keep trying... Apr 26 06:38:39 192.168.122.209 [52469.919556] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18099: 1 tries, keep trying... Apr 26 06:38:39 192.168.122.209 [52469.919668] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18099: 1 tries, keep trying... Apr 26 06:38:39 192.168.122.209 [52469.919673] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18099: 1 tries, keep trying... Apr 26 06:38:39 192.168.122.209 [52469.919779] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18099: 1 tries, keep trying... Apr 26 06:38:39 192.168.122.209 [52469.919790] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18099: 1 tries, keep trying... Apr 26 06:38:39 192.168.122.209 [52469.919883] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18099: 1 tries, keep trying... Apr 26 06:38:39 192.168.122.209 [52469.919918] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18099: 1 tries, keep trying... Apr 26 06:38:39 192.168.122.209 [52469.919993] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18099: 1 tries, keep trying... Apr 26 06:38:39 192.168.122.209 [52469.920067] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18099: 1 tries, keep trying... Apr 26 06:38:39 192.168.122.209 [52469.920089] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18099: 1 tries, keep trying... Apr 26 06:38:39 192.168.122.209 [52469.920183] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18099: 1 tries, keep trying... Apr 26 06:38:39 192.168.122.209 [52469.920253] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18099: 1 tries, keep trying... Apr 26 06:38:39 192.168.122.209 [52469.921494] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18099: 1 tries, keep trying... Apr 26 06:38:39 192.168.122.209 [52469.924287] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18099: 1 tries, keep trying... Apr 26 06:38:39 192.168.122.209 [52469.926062] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18099: 1 tries, keep trying... Apr 26 06:38:39 192.168.122.209 [52469.927190] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18099: 1 tries, keep trying... Apr 26 06:38:39 192.168.122.209 [52469.928546] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18099: 1 tries, keep trying... Apr 26 06:38:39 192.168.122.209 [52469.929687] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18099: 1 tries, keep trying... Apr 26 06:38:39 192.168.122.209 [52469.931057] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18099: 1 tries, keep trying... Apr 26 06:38:39 192.168.122.209 [52469.932191] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18099: 1 tries, keep trying... Apr 26 06:38:39 192.168.122.209 [52469.933561] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18099: 1 tries, keep trying... Apr 26 06:38:39 192.168.122.209 [52469.934706] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18099: 1 tries, keep trying... Apr 26 06:38:39 192.168.122.209 [52469.935865] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18099: 1 tries, keep trying... Apr 26 06:38:39 192.168.122.209 [52469.936724] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18099: 1 tries, keep trying... Apr 26 06:38:39 192.168.122.209 [52469.953944] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18099: 1 tries, keep trying... Apr 26 06:38:39 192.168.122.209 [52469.954932] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18099: 1 tries, keep trying... Apr 26 06:38:55 192.168.122.209 [52486.302173] [tempesta fw] Warning: request dropped: non-idempotent requests aren't re-forwarded or re-scheduled, status 504: 127.0.0.1 Apr 26 06:38:55 192.168.122.209 [52486.305562] [tempesta fw] 127.0.0.1 "default" "GET / HTTP/1.1" 504 0 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/99.0.4844.51 Safari/537.36" "ja5t=0" "ja5h=f47f0107000c0700" Apr 26 06:38:56 192.168.122.209 [52486.745250] [tdb] Close table 'client0.tdb' Apr 26 06:38:56 192.168.122.209 [52486.939191] [tdb] Close table 'sessions0.tdb' Apr 26 06:38:59 192.168.122.209 [52490.312760] [tdb] Close table 'cache0.tdb' Apr 26 06:39:00 192.168.122.209 [52490.544813] [tdb] Close table 'filter0.tdb' Apr 26 06:39:00 192.168.122.209 [52490.545282] [tempesta fw] modules are stopped Apr 26 06:39:00 192.168.122.209 [52490.738443] [tempesta fw] exiting... Apr 26 06:39:00 192.168.122.209 [52490.861682] [tdb] Shutdown Tempesta DB Apr 26 06:39:00 192.168.122.209 [52491.111012] End test: ws.test_ws_ping.CacheTest.test Apr 26 06:39:00 192.168.122.209 [52491.120325] Start test: ws.test_ws_ping.WsPing.test Apr 26 06:39:01 192.168.122.209 [52492.179612] [tdb] Start Tempesta DB Apr 26 06:39:01 192.168.122.209 [52492.337967] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:39:03 192.168.122.209 [52494.003018] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52494.003018] Maybe that's fine, but it's worth checking the [52494.003018] config - if there is no relations between the [52494.003018] names, then host name confusion attack is possible. Apr 26 06:39:03 192.168.122.209 [52494.121467] [tempesta fw] Configuration processing is completed. Apr 26 06:39:03 192.168.122.209 [52494.171380] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:39:04 192.168.122.209 [52494.639538] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:39:04 192.168.122.209 [52494.668882] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:39:04 192.168.122.209 [52494.697969] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:39:04 192.168.122.209 [52494.769515] [tempesta fw] Open listen socket on: 0.0.0.0:82 Apr 26 06:39:04 192.168.122.209 [52494.771222] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 06:39:04 192.168.122.209 [52494.809471] [tempesta fw] Tempesta FW is ready Apr 26 06:39:05 192.168.122.209 [52495.487864] [tdb] Close table 'client0.tdb' Apr 26 06:39:05 192.168.122.209 [52495.701510] [tdb] Close table 'sessions0.tdb' Apr 26 06:39:08 192.168.122.209 [52498.905934] [tdb] Close table 'cache0.tdb' Apr 26 06:39:08 192.168.122.209 [52499.156249] [tdb] Close table 'filter0.tdb' Apr 26 06:39:08 192.168.122.209 [52499.156653] [tempesta fw] modules are stopped Apr 26 06:39:08 192.168.122.209 [52499.356687] [tempesta fw] exiting... Apr 26 06:39:09 192.168.122.209 [52499.484401] [tdb] Shutdown Tempesta DB Apr 26 06:39:09 192.168.122.209 [52499.728108] End test: ws.test_ws_ping.WsPing.test Apr 26 06:39:09 192.168.122.209 [52499.737511] Start test: ws.test_ws_ping.WsScheduler.test Apr 26 06:39:10 192.168.122.209 [52500.829661] [tdb] Start Tempesta DB Apr 26 06:39:10 192.168.122.209 [52500.992244] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:39:12 192.168.122.209 [52502.561624] [tempesta fw] Configuration processing is completed. Apr 26 06:39:12 192.168.122.209 [52502.611533] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:39:12 192.168.122.209 [52503.051838] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:39:12 192.168.122.209 [52503.079730] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:39:12 192.168.122.209 [52503.108300] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:39:12 192.168.122.209 [52503.193632] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 06:39:12 192.168.122.209 [52503.233562] [tempesta fw] Tempesta FW is ready Apr 26 06:39:19 192.168.122.209 [52510.002597] [tdb] Close table 'client0.tdb' Apr 26 06:39:19 192.168.122.209 [52510.200261] [tdb] Close table 'sessions0.tdb' Apr 26 06:39:23 192.168.122.209 [52513.638728] [tdb] Close table 'cache0.tdb' Apr 26 06:39:23 192.168.122.209 [52513.895447] [tdb] Close table 'filter0.tdb' Apr 26 06:39:23 192.168.122.209 [52513.895900] [tempesta fw] modules are stopped Apr 26 06:39:23 192.168.122.209 [52514.079616] [tempesta fw] exiting... Apr 26 06:39:23 192.168.122.209 [52514.211313] [tdb] Shutdown Tempesta DB Apr 26 06:39:23 192.168.122.209 [52514.439318] End test: ws.test_ws_ping.WsScheduler.test Apr 26 06:39:23 192.168.122.209 [52514.457836] Start test: ws.test_ws_ping.WssPing.test Apr 26 06:39:25 192.168.122.209 [52515.528720] [tdb] Start Tempesta DB Apr 26 06:39:25 192.168.122.209 [52515.675198] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:39:26 192.168.122.209 [52517.379550] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52517.379550] Maybe that's fine, but it's worth checking the [52517.379550] config - if there is no relations between the [52517.379550] names, then host name confusion attack is possible. Apr 26 06:39:27 192.168.122.209 [52517.505786] [tempesta fw] Configuration processing is completed. Apr 26 06:39:27 192.168.122.209 [52517.557030] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:39:27 192.168.122.209 [52518.017161] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:39:27 192.168.122.209 [52518.046184] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:39:27 192.168.122.209 [52518.074259] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:39:27 192.168.122.209 [52518.145829] [tempesta fw] Open listen socket on: 0.0.0.0:82 Apr 26 06:39:27 192.168.122.209 [52518.147552] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 06:39:27 192.168.122.209 [52518.185754] [tempesta fw] Tempesta FW is ready Apr 26 06:39:28 192.168.122.209 [52518.932668] [tdb] Close table 'client0.tdb' Apr 26 06:39:28 192.168.122.209 [52519.120867] [tdb] Close table 'sessions0.tdb' Apr 26 06:39:31 192.168.122.209 [52522.306215] [tdb] Close table 'cache0.tdb' Apr 26 06:39:32 192.168.122.209 [52522.576288] [tdb] Close table 'filter0.tdb' Apr 26 06:39:32 192.168.122.209 [52522.576727] [tempesta fw] modules are stopped Apr 26 06:39:32 192.168.122.209 [52522.775765] [tempesta fw] exiting... Apr 26 06:39:32 192.168.122.209 [52522.912303] [tdb] Shutdown Tempesta DB Apr 26 06:39:32 192.168.122.209 [52523.168881] End test: ws.test_ws_ping.WssPing.test Apr 26 06:39:32 192.168.122.209 [52523.180714] Start test: ws.test_ws_ping.WssPingMultipleListenersH2Https.test Apr 26 06:39:33 192.168.122.209 [52524.254400] [tdb] Start Tempesta DB Apr 26 06:39:33 192.168.122.209 [52524.401063] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:39:35 192.168.122.209 [52525.995433] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52525.995433] Maybe that's fine, but it's worth checking the [52525.995433] config - if there is no relations between the [52525.995433] names, then host name confusion attack is possible. Apr 26 06:39:35 192.168.122.209 [52526.121884] [tempesta fw] Configuration processing is completed. Apr 26 06:39:35 192.168.122.209 [52526.171256] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:39:36 192.168.122.209 [52526.594711] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:39:36 192.168.122.209 [52526.621627] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:39:36 192.168.122.209 [52526.649795] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:39:36 192.168.122.209 [52526.725936] [tempesta fw] Open listen socket on: 0.0.0.0:82 Apr 26 06:39:36 192.168.122.209 [52526.727619] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 06:39:36 192.168.122.209 [52526.773878] [tempesta fw] Tempesta FW is ready Apr 26 06:39:37 192.168.122.209 [52527.492897] [tdb] Close table 'client0.tdb' Apr 26 06:39:37 192.168.122.209 [52527.691954] [tdb] Close table 'sessions0.tdb' Apr 26 06:39:40 192.168.122.209 [52530.978166] [tdb] Close table 'cache0.tdb' Apr 26 06:39:40 192.168.122.209 [52531.213748] [tdb] Close table 'filter0.tdb' Apr 26 06:39:40 192.168.122.209 [52531.214195] [tempesta fw] modules are stopped Apr 26 06:39:40 192.168.122.209 [52531.427264] [tempesta fw] exiting... Apr 26 06:39:41 192.168.122.209 [52531.552100] [tdb] Shutdown Tempesta DB Apr 26 06:39:41 192.168.122.209 [52531.783646] End test: ws.test_ws_ping.WssPingMultipleListenersH2Https.test Apr 26 06:39:41 192.168.122.209 [52531.819070] Start test: ws.test_ws_ping.WssPingMultipleListenersHttpsH2.test Apr 26 06:39:42 192.168.122.209 [52532.949880] [tdb] Start Tempesta DB Apr 26 06:39:42 192.168.122.209 [52533.086887] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:39:44 192.168.122.209 [52534.719559] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52534.719559] Maybe that's fine, but it's worth checking the [52534.719559] config - if there is no relations between the [52534.719559] names, then host name confusion attack is possible. Apr 26 06:39:44 192.168.122.209 [52534.842003] [tempesta fw] Configuration processing is completed. Apr 26 06:39:44 192.168.122.209 [52534.900349] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:39:44 192.168.122.209 [52535.319423] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:39:44 192.168.122.209 [52535.345668] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:39:44 192.168.122.209 [52535.371790] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:39:44 192.168.122.209 [52535.446028] [tempesta fw] Open listen socket on: 0.0.0.0:82 Apr 26 06:39:44 192.168.122.209 [52535.447689] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 06:39:45 192.168.122.209 [52535.485986] [tempesta fw] Tempesta FW is ready Apr 26 06:39:45 192.168.122.209 [52536.181618] [tdb] Close table 'client0.tdb' Apr 26 06:39:45 192.168.122.209 [52536.364684] [tdb] Close table 'sessions0.tdb' Apr 26 06:39:49 192.168.122.209 [52539.580435] [tdb] Close table 'cache0.tdb' Apr 26 06:39:49 192.168.122.209 [52539.829235] [tdb] Close table 'filter0.tdb' Apr 26 06:39:49 192.168.122.209 [52539.829682] [tempesta fw] modules are stopped Apr 26 06:39:49 192.168.122.209 [52540.019945] [tempesta fw] exiting... Apr 26 06:39:49 192.168.122.209 [52540.146927] [tdb] Shutdown Tempesta DB Apr 26 06:39:49 192.168.122.209 [52540.372212] End test: ws.test_ws_ping.WssPingMultipleListenersHttpsH2.test Apr 26 06:39:49 192.168.122.209 [52540.385520] Start test: ws.test_ws_ping.WssPingProxy.test Apr 26 06:39:50 192.168.122.209 [52541.328175] [tdb] Start Tempesta DB Apr 26 06:39:51 192.168.122.209 [52541.470736] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:39:52 192.168.122.209 [52543.115734] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52543.115734] Maybe that's fine, but it's worth checking the [52543.115734] config - if there is no relations between the [52543.115734] names, then host name confusion attack is possible. Apr 26 06:39:52 192.168.122.209 [52543.234101] [tempesta fw] Configuration processing is completed. Apr 26 06:39:52 192.168.122.209 [52543.284153] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:39:53 192.168.122.209 [52543.705624] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:39:53 192.168.122.209 [52543.731733] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:39:53 192.168.122.209 [52543.758626] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:39:53 192.168.122.209 [52543.846128] [tempesta fw] Open listen socket on: 0.0.0.0:82 Apr 26 06:39:53 192.168.122.209 [52543.847769] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 06:39:53 192.168.122.209 [52543.886049] [tempesta fw] Tempesta FW is ready Apr 26 06:39:54 192.168.122.209 [52544.603919] [tdb] Close table 'client0.tdb' Apr 26 06:39:54 192.168.122.209 [52544.798513] [tdb] Close table 'sessions0.tdb' Apr 26 06:39:57 192.168.122.209 [52548.050265] [tdb] Close table 'cache0.tdb' Apr 26 06:39:57 192.168.122.209 [52548.273709] [tdb] Close table 'filter0.tdb' Apr 26 06:39:57 192.168.122.209 [52548.274162] [tempesta fw] modules are stopped Apr 26 06:39:58 192.168.122.209 [52548.482385] [tempesta fw] exiting... Apr 26 06:39:58 192.168.122.209 [52548.613864] [tdb] Shutdown Tempesta DB Apr 26 06:39:58 192.168.122.209 [52548.855803] End test: ws.test_ws_ping.WssPingProxy.test Apr 26 06:39:58 192.168.122.209 [52548.866448] Start test: ws.test_ws_ping.WssPipelining.test Apr 26 06:39:59 192.168.122.209 [52550.000237] [tdb] Start Tempesta DB Apr 26 06:39:59 192.168.122.209 [52550.142479] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:40:01 192.168.122.209 [52551.719783] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52551.719783] Maybe that's fine, but it's worth checking the [52551.719783] config - if there is no relations between the [52551.719783] names, then host name confusion attack is possible. Apr 26 06:40:01 192.168.122.209 [52551.842207] [tempesta fw] Configuration processing is completed. Apr 26 06:40:01 192.168.122.209 [52551.892360] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:40:01 192.168.122.209 [52552.315813] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:40:01 192.168.122.209 [52552.342035] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:40:01 192.168.122.209 [52552.368061] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:40:02 192.168.122.209 [52552.466232] [tempesta fw] Open listen socket on: 0.0.0.0:82 Apr 26 06:40:02 192.168.122.209 [52552.467942] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 06:40:02 192.168.122.209 [52552.506217] [tempesta fw] Tempesta FW is ready Apr 26 06:40:07 192.168.122.209 [52557.672627] [tempesta fw] Warning: Request dropped: Pipelined request received after UPGRADE request: 127.0.0.2 Apr 26 06:40:07 192.168.122.209 [52558.132748] [tdb] Close table 'client0.tdb' Apr 26 06:40:07 192.168.122.209 [52558.315152] [tdb] Close table 'sessions0.tdb' Apr 26 06:40:11 192.168.122.209 [52561.471401] [tdb] Close table 'cache0.tdb' Apr 26 06:40:11 192.168.122.209 [52561.713263] [tdb] Close table 'filter0.tdb' Apr 26 06:40:11 192.168.122.209 [52561.713709] [tempesta fw] modules are stopped Apr 26 06:40:11 192.168.122.209 [52561.930600] [tempesta fw] exiting... Apr 26 06:40:11 192.168.122.209 [52562.058849] [tdb] Shutdown Tempesta DB Apr 26 06:40:11 192.168.122.209 [52562.272570] End test: ws.test_ws_ping.WssPipelining.test Apr 26 06:40:11 192.168.122.209 [52562.289082] Start test: ws.test_ws_ping.WssStress.test Apr 26 06:40:12 192.168.122.209 [52563.342660] [tdb] Start Tempesta DB Apr 26 06:40:13 192.168.122.209 [52563.477936] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:40:18 192.168.122.209 [52568.923942] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52568.923942] Maybe that's fine, but it's worth checking the [52568.923942] config - if there is no relations between the [52568.923942] names, then host name confusion attack is possible. Apr 26 06:40:19 192.168.122.209 [52569.922696] [tempesta fw] Configuration processing is completed. Apr 26 06:40:19 192.168.122.209 [52569.988874] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:40:19 192.168.122.209 [52570.421646] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:40:19 192.168.122.209 [52570.450448] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:40:20 192.168.122.209 [52570.480845] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:40:21 192.168.122.209 [52572.412856] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18149: 1 tries, keep trying... Apr 26 06:40:21 192.168.122.209 [52572.413308] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18149: 1 tries, keep trying... Apr 26 06:40:21 192.168.122.209 [52572.413317] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18149: 1 tries, keep trying... Apr 26 06:40:21 192.168.122.209 [52572.413406] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18149: 1 tries, keep trying... Apr 26 06:40:21 192.168.122.209 [52572.413492] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18149: 1 tries, keep trying... Apr 26 06:40:21 192.168.122.209 [52572.413534] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18149: 1 tries, keep trying... Apr 26 06:40:21 192.168.122.209 [52572.413622] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18149: 1 tries, keep trying... Apr 26 06:40:21 192.168.122.209 [52572.413646] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18149: 1 tries, keep trying... Apr 26 06:40:21 192.168.122.209 [52572.413744] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18149: 1 tries, keep trying... Apr 26 06:40:21 192.168.122.209 [52572.413756] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18149: 1 tries, keep trying... Apr 26 06:40:21 192.168.122.209 [52572.413857] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18149: 1 tries, keep trying... Apr 26 06:40:21 192.168.122.209 [52572.413866] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18149: 1 tries, keep trying... Apr 26 06:40:21 192.168.122.209 [52572.413910] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18149: 1 tries, keep trying... Apr 26 06:40:21 192.168.122.209 [52572.413963] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18149: 1 tries, keep trying... Apr 26 06:40:21 192.168.122.209 [52572.413980] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18149: 1 tries, keep trying... Apr 26 06:40:21 192.168.122.209 [52572.414002] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18149: 1 tries, keep trying... Apr 26 06:40:21 192.168.122.209 [52572.414043] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18149: 1 tries, keep trying... Apr 26 06:40:21 192.168.122.209 [52572.414087] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18149: 1 tries, keep trying... Apr 26 06:40:21 192.168.122.209 [52572.414090] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18149: 1 tries, keep trying... Apr 26 06:40:21 192.168.122.209 [52572.414134] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18149: 1 tries, keep trying... Apr 26 06:40:21 192.168.122.209 [52572.414173] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18149: 1 tries, keep trying... Apr 26 06:40:21 192.168.122.209 [52572.414217] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18149: 1 tries, keep trying... Apr 26 06:40:21 192.168.122.209 [52572.414261] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18149: 1 tries, keep trying... Apr 26 06:40:21 192.168.122.209 [52572.414316] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18149: 1 tries, keep trying... Apr 26 06:40:21 192.168.122.209 [52572.414356] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18149: 1 tries, keep trying... Apr 26 06:40:21 192.168.122.209 [52572.414397] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18149: 1 tries, keep trying... Apr 26 06:40:21 192.168.122.209 [52572.417126] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18149: 1 tries, keep trying... Apr 26 06:40:21 192.168.122.209 [52572.448376] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18149: 1 tries, keep trying... Apr 26 06:40:21 192.168.122.209 [52572.449510] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18149: 1 tries, keep trying... Apr 26 06:40:21 192.168.122.209 [52572.450509] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18149: 1 tries, keep trying... Apr 26 06:40:21 192.168.122.209 [52572.451500] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18149: 1 tries, keep trying... Apr 26 06:40:21 192.168.122.209 [52572.452518] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:18149: 1 tries, keep trying... Apr 26 06:40:24 192.168.122.209 [52574.570536] [tempesta fw] Open listen socket on: 0.0.0.0:82 Apr 26 06:40:24 192.168.122.209 [52574.572450] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 06:40:25 192.168.122.209 [52576.042354] [tempesta fw] Tempesta FW is ready Apr 26 06:40:30 192.168.122.209 [52581.257474] [tempesta fw] Warning: request dropped: non-idempotent requests aren't re-forwarded or re-scheduled, status 504: 127.0.0.1 Apr 26 06:40:32 192.168.122.209 [52582.942154] [tdb] Close table 'client0.tdb' Apr 26 06:40:32 192.168.122.209 [52583.128787] [tdb] Close table 'sessions0.tdb' Apr 26 06:40:35 192.168.122.209 [52586.287034] [tdb] Close table 'cache0.tdb' Apr 26 06:40:36 192.168.122.209 [52586.546346] [tdb] Close table 'filter0.tdb' Apr 26 06:40:36 192.168.122.209 [52586.546823] [tempesta fw] modules are stopped Apr 26 06:40:36 192.168.122.209 [52586.748263] [tempesta fw] exiting... Apr 26 06:40:36 192.168.122.209 [52586.859750] [tdb] Shutdown Tempesta DB Apr 26 06:40:36 192.168.122.209 [52587.127251] End test: ws.test_ws_ping.WssStress.test Apr 26 06:40:37 192.168.122.209 [52588.101917] [tdb] Start Tempesta DB Apr 26 06:40:37 192.168.122.209 [52588.237764] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:40:38 192.168.122.209 [52589.354449] [tempesta fw] Configuration processing is completed. Apr 26 06:40:38 192.168.122.209 [52589.406645] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:40:39 192.168.122.209 [52589.837564] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:40:39 192.168.122.209 [52589.865133] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:40:39 192.168.122.209 [52589.892536] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:40:39 192.168.122.209 [52589.893577] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:40:39 192.168.122.209 [52589.910574] [tempesta fw] Tempesta FW is ready Apr 26 06:40:45 192.168.122.209 [52595.848197] [tdb] Close table 'client0.tdb' Apr 26 06:40:45 192.168.122.209 [52596.050234] [tdb] Close table 'sessions0.tdb' Apr 26 06:40:48 192.168.122.209 [52599.256638] [tdb] Close table 'cache0.tdb' Apr 26 06:40:49 192.168.122.209 [52599.500380] [tdb] Close table 'filter0.tdb' Apr 26 06:40:49 192.168.122.209 [52599.500803] [tempesta fw] modules are stopped Apr 26 06:40:49 192.168.122.209 [52599.695286] [tempesta fw] exiting... Apr 26 06:40:49 192.168.122.209 [52599.808921] [tdb] Shutdown Tempesta DB Apr 26 06:40:54 192.168.122.209 [52604.602434] Start test: tls.test_tls_tickets.TlsVhostConfusionDfltVhost.test Apr 26 06:40:55 192.168.122.209 [52605.648164] [tdb] Start Tempesta DB Apr 26 06:40:55 192.168.122.209 [52605.787024] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:40:57 192.168.122.209 [52607.568544] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52607.568544] Maybe that's fine, but it's worth checking the [52607.568544] config - if there is no relations between the [52607.568544] names, then host name confusion attack is possible. Apr 26 06:40:57 192.168.122.209 [52607.625383] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [52607.625383] Maybe that's fine, but it's worth checking the [52607.625383] config - if there is no relations between the [52607.625383] names, then host name confusion attack is possible. Apr 26 06:40:57 192.168.122.209 [52607.715009] [tempesta fw] Configuration processing is completed. Apr 26 06:40:57 192.168.122.209 [52607.765019] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:40:57 192.168.122.209 [52607.792863] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:40:57 192.168.122.209 [52607.820839] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:40:57 192.168.122.209 [52607.938957] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:40:57 192.168.122.209 [52607.978877] [tempesta fw] Tempesta FW is ready Apr 26 06:40:57 192.168.122.209 [52608.141886] device enp1s0 entered promiscuous mode Apr 26 06:40:57 192.168.122.209 [52608.288926] device enp1s0 left promiscuous mode Apr 26 06:40:57 192.168.122.209 [52608.311131] device enp1s0 entered promiscuous mode Apr 26 06:40:57 192.168.122.209 [52608.415239] device enp1s0 left promiscuous mode Apr 26 06:40:58 192.168.122.209 [52608.935889] [tdb] Close table 'client0.tdb' Apr 26 06:40:58 192.168.122.209 [52609.122038] [tdb] Close table 'sessions0.tdb' Apr 26 06:40:58 192.168.122.209 [52609.367549] [tdb] Close table 'filter0.tdb' Apr 26 06:40:58 192.168.122.209 [52609.367988] [tempesta fw] modules are stopped Apr 26 06:40:59 192.168.122.209 [52609.589327] [tempesta fw] exiting... Apr 26 06:40:59 192.168.122.209 [52609.696631] [tdb] Shutdown Tempesta DB Apr 26 06:40:59 192.168.122.209 [52609.924966] End test: tls.test_tls_tickets.TlsVhostConfusionDfltVhost.test Apr 26 06:40:59 192.168.122.209 [52609.932255] Start test: tls.test_tls_tickets.TlsVhostConfusionDfltCertsWithUnknown.test Apr 26 06:41:00 192.168.122.209 [52611.035536] [tdb] Start Tempesta DB Apr 26 06:41:00 192.168.122.209 [52611.172232] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:41:01 192.168.122.209 [52612.136213] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52612.136213] Maybe that's fine, but it's worth checking the [52612.136213] config - if there is no relations between the [52612.136213] names, then host name confusion attack is possible. Apr 26 06:41:01 192.168.122.209 [52612.267051] [tempesta fw] Configuration processing is completed. Apr 26 06:41:01 192.168.122.209 [52612.317578] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:41:01 192.168.122.209 [52612.347639] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:41:01 192.168.122.209 [52612.376996] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:41:01 192.168.122.209 [52612.438938] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:41:02 192.168.122.209 [52612.482932] [tempesta fw] Tempesta FW is ready Apr 26 06:41:02 192.168.122.209 [52612.617365] device enp1s0 entered promiscuous mode Apr 26 06:41:02 192.168.122.209 [52612.731579] device enp1s0 left promiscuous mode Apr 26 06:41:02 192.168.122.209 [52612.753724] device enp1s0 entered promiscuous mode Apr 26 06:41:02 192.168.122.209 [52612.847315] device enp1s0 left promiscuous mode Apr 26 06:41:02 192.168.122.209 [52613.333245] [tdb] Close table 'client0.tdb' Apr 26 06:41:03 192.168.122.209 [52613.531178] [tdb] Close table 'sessions0.tdb' Apr 26 06:41:03 192.168.122.209 [52613.773436] [tdb] Close table 'filter0.tdb' Apr 26 06:41:03 192.168.122.209 [52613.773867] [tempesta fw] modules are stopped Apr 26 06:41:03 192.168.122.209 [52614.127297] [tempesta fw] exiting... Apr 26 06:41:03 192.168.122.209 [52614.281390] [tdb] Shutdown Tempesta DB Apr 26 06:41:04 192.168.122.209 [52614.488232] End test: tls.test_tls_tickets.TlsVhostConfusionDfltCertsWithUnknown.test Apr 26 06:41:04 192.168.122.209 [52614.513960] Start test: tls.test_tls_tickets.TlsVhostConfusionDfltCerts.test Apr 26 06:41:05 192.168.122.209 [52615.569582] [tdb] Start Tempesta DB Apr 26 06:41:05 192.168.122.209 [52615.710530] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:41:06 192.168.122.209 [52616.748893] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [52616.748893] Maybe that's fine, but it's worth checking the [52616.748893] config - if there is no relations between the [52616.748893] names, then host name confusion attack is possible. Apr 26 06:41:06 192.168.122.209 [52616.784733] [tempesta fw] Warning: Vhost tempesta.com doesn't have certificate with matching SAN/CN. [52616.784733] Maybe that's fine, but it's worth checking the [52616.784733] config - if there is no relations between the [52616.784733] names, then host name confusion attack is possible. Apr 26 06:41:06 192.168.122.209 [52616.875120] [tempesta fw] Configuration processing is completed. Apr 26 06:41:06 192.168.122.209 [52616.927138] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:41:06 192.168.122.209 [52616.954945] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:41:06 192.168.122.209 [52616.982707] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:41:06 192.168.122.209 [52617.042982] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:41:06 192.168.122.209 [52617.083019] [tempesta fw] Tempesta FW is ready Apr 26 06:41:06 192.168.122.209 [52617.221067] device enp1s0 entered promiscuous mode Apr 26 06:41:06 192.168.122.209 [52617.335722] device enp1s0 left promiscuous mode Apr 26 06:41:06 192.168.122.209 [52617.358559] device enp1s0 entered promiscuous mode Apr 26 06:41:06 192.168.122.209 [52617.463446] device enp1s0 left promiscuous mode Apr 26 06:41:07 192.168.122.209 [52618.000121] [tdb] Close table 'client0.tdb' Apr 26 06:41:07 192.168.122.209 [52618.183474] [tdb] Close table 'sessions0.tdb' Apr 26 06:41:07 192.168.122.209 [52618.391972] [tdb] Close table 'filter0.tdb' Apr 26 06:41:07 192.168.122.209 [52618.392402] [tempesta fw] modules are stopped Apr 26 06:41:08 192.168.122.209 [52618.610705] [tempesta fw] exiting... Apr 26 06:41:08 192.168.122.209 [52618.761320] [tdb] Shutdown Tempesta DB Apr 26 06:41:08 192.168.122.209 [52619.009898] End test: tls.test_tls_tickets.TlsVhostConfusionDfltCerts.test Apr 26 06:41:08 192.168.122.209 [52619.029422] Start test: tls.test_tls_tickets.TlsVhostConfusion.test Apr 26 06:41:09 192.168.122.209 [52620.090646] [tdb] Start Tempesta DB Apr 26 06:41:09 192.168.122.209 [52620.231770] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:41:10 192.168.122.209 [52621.285047] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [52621.285047] Maybe that's fine, but it's worth checking the [52621.285047] config - if there is no relations between the [52621.285047] names, then host name confusion attack is possible. Apr 26 06:41:10 192.168.122.209 [52621.313235] [tempesta fw] Warning: Vhost tempesta.com doesn't have certificate with matching SAN/CN. [52621.313235] Maybe that's fine, but it's worth checking the [52621.313235] config - if there is no relations between the [52621.313235] names, then host name confusion attack is possible. Apr 26 06:41:10 192.168.122.209 [52621.379209] [tempesta fw] Configuration processing is completed. Apr 26 06:41:10 192.168.122.209 [52621.434187] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:41:10 192.168.122.209 [52621.465992] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:41:11 192.168.122.209 [52621.495003] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:41:11 192.168.122.209 [52621.559017] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:41:11 192.168.122.209 [52621.599065] [tempesta fw] Tempesta FW is ready Apr 26 06:41:11 192.168.122.209 [52621.732425] device enp1s0 entered promiscuous mode Apr 26 06:41:11 192.168.122.209 [52621.851734] device enp1s0 left promiscuous mode Apr 26 06:41:11 192.168.122.209 [52621.872764] device enp1s0 entered promiscuous mode Apr 26 06:41:11 192.168.122.209 [52621.967225] device enp1s0 left promiscuous mode Apr 26 06:41:12 192.168.122.209 [52622.478144] [tdb] Close table 'client0.tdb' Apr 26 06:41:12 192.168.122.209 [52622.656784] [tdb] Close table 'sessions0.tdb' Apr 26 06:41:12 192.168.122.209 [52622.893633] [tdb] Close table 'filter0.tdb' Apr 26 06:41:12 192.168.122.209 [52622.894057] [tempesta fw] modules are stopped Apr 26 06:41:12 192.168.122.209 [52623.123643] [tempesta fw] exiting... Apr 26 06:41:12 192.168.122.209 [52623.252896] [tdb] Shutdown Tempesta DB Apr 26 06:41:12 192.168.122.209 [52623.447452] End test: tls.test_tls_tickets.TlsVhostConfusion.test Apr 26 06:41:13 192.168.122.209 [52623.469228] Start test: tls.test_tls_tickets.TlsTicketTest.test_no_ticket_support Apr 26 06:41:14 192.168.122.209 [52624.569944] [tdb] Start Tempesta DB Apr 26 06:41:14 192.168.122.209 [52624.701127] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:41:15 192.168.122.209 [52625.496613] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52625.496613] Maybe that's fine, but it's worth checking the [52625.496613] config - if there is no relations between the [52625.496613] names, then host name confusion attack is possible. Apr 26 06:41:15 192.168.122.209 [52625.615209] [tempesta fw] Configuration processing is completed. Apr 26 06:41:15 192.168.122.209 [52625.666090] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:41:15 192.168.122.209 [52625.693516] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:41:15 192.168.122.209 [52625.721555] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:41:15 192.168.122.209 [52625.783168] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:41:15 192.168.122.209 [52625.827134] [tempesta fw] Tempesta FW is ready Apr 26 06:41:15 192.168.122.209 [52625.954035] device enp1s0 entered promiscuous mode Apr 26 06:41:15 192.168.122.209 [52626.079221] device enp1s0 left promiscuous mode Apr 26 06:41:16 192.168.122.209 [52626.523981] [tdb] Close table 'client0.tdb' Apr 26 06:41:16 192.168.122.209 [52626.703273] [tdb] Close table 'sessions0.tdb' Apr 26 06:41:16 192.168.122.209 [52626.955604] [tdb] Close table 'filter0.tdb' Apr 26 06:41:16 192.168.122.209 [52626.956020] [tempesta fw] modules are stopped Apr 26 06:41:16 192.168.122.209 [52627.204278] [tempesta fw] exiting... Apr 26 06:41:16 192.168.122.209 [52627.327473] [tdb] Shutdown Tempesta DB Apr 26 06:41:17 192.168.122.209 [52627.530508] End test: tls.test_tls_tickets.TlsTicketTest.test_no_ticket_support Apr 26 06:41:17 192.168.122.209 [52627.554117] Start test: tls.test_tls_tickets.TlsTicketTest.test_invalid_ticket Apr 26 06:41:18 192.168.122.209 [52628.602392] [tdb] Start Tempesta DB Apr 26 06:41:18 192.168.122.209 [52628.734957] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:41:19 192.168.122.209 [52629.531472] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52629.531472] Maybe that's fine, but it's worth checking the [52629.531472] config - if there is no relations between the [52629.531472] names, then host name confusion attack is possible. Apr 26 06:41:19 192.168.122.209 [52629.659250] [tempesta fw] Configuration processing is completed. Apr 26 06:41:19 192.168.122.209 [52629.714490] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:41:19 192.168.122.209 [52629.743832] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:41:19 192.168.122.209 [52629.771433] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:41:19 192.168.122.209 [52629.851587] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:41:19 192.168.122.209 [52629.895155] [tempesta fw] Tempesta FW is ready Apr 26 06:41:19 192.168.122.209 [52630.040984] device enp1s0 entered promiscuous mode Apr 26 06:41:19 192.168.122.209 [52630.143492] device enp1s0 left promiscuous mode Apr 26 06:41:19 192.168.122.209 [52630.165883] device enp1s0 entered promiscuous mode Apr 26 06:41:19 192.168.122.209 [52630.211674] [tempesta tls] Warning: AEAD decryption failed while ticket decryption: -74 Apr 26 06:41:19 192.168.122.209 [52630.279792] device enp1s0 left promiscuous mode Apr 26 06:41:20 192.168.122.209 [52630.730431] [tdb] Close table 'client0.tdb' Apr 26 06:41:20 192.168.122.209 [52630.928752] [tdb] Close table 'sessions0.tdb' Apr 26 06:41:20 192.168.122.209 [52631.175608] [tdb] Close table 'filter0.tdb' Apr 26 06:41:20 192.168.122.209 [52631.176054] [tempesta fw] modules are stopped Apr 26 06:41:20 192.168.122.209 [52631.415495] [tempesta fw] exiting... Apr 26 06:41:21 192.168.122.209 [52631.549862] [tdb] Shutdown Tempesta DB Apr 26 06:41:21 192.168.122.209 [52631.775630] End test: tls.test_tls_tickets.TlsTicketTest.test_invalid_ticket Apr 26 06:41:21 192.168.122.209 [52631.792445] Start test: tls.test_tls_tickets.TlsTicketTest.test_empty_ticket Apr 26 06:41:22 192.168.122.209 [52632.856641] [tdb] Start Tempesta DB Apr 26 06:41:22 192.168.122.209 [52632.978370] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:41:23 192.168.122.209 [52633.767715] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52633.767715] Maybe that's fine, but it's worth checking the [52633.767715] config - if there is no relations between the [52633.767715] names, then host name confusion attack is possible. Apr 26 06:41:23 192.168.122.209 [52633.907199] [tempesta fw] Configuration processing is completed. Apr 26 06:41:23 192.168.122.209 [52633.964872] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:41:23 192.168.122.209 [52633.992442] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:41:23 192.168.122.209 [52634.020933] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:41:23 192.168.122.209 [52634.059199] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:41:23 192.168.122.209 [52634.107113] [tempesta fw] Tempesta FW is ready Apr 26 06:41:23 192.168.122.209 [52634.238126] device enp1s0 entered promiscuous mode Apr 26 06:41:23 192.168.122.209 [52634.351952] device enp1s0 left promiscuous mode Apr 26 06:41:23 192.168.122.209 [52634.377869] device enp1s0 entered promiscuous mode Apr 26 06:41:23 192.168.122.209 [52634.455611] device enp1s0 left promiscuous mode Apr 26 06:41:24 192.168.122.209 [52634.910823] [tdb] Close table 'client0.tdb' Apr 26 06:41:24 192.168.122.209 [52635.099195] [tdb] Close table 'sessions0.tdb' Apr 26 06:41:24 192.168.122.209 [52635.338878] [tdb] Close table 'filter0.tdb' Apr 26 06:41:24 192.168.122.209 [52635.339328] [tempesta fw] modules are stopped Apr 26 06:41:25 192.168.122.209 [52635.555995] [tempesta fw] exiting... Apr 26 06:41:25 192.168.122.209 [52635.667336] [tdb] Shutdown Tempesta DB Apr 26 06:41:25 192.168.122.209 [52635.888747] End test: tls.test_tls_tickets.TlsTicketTest.test_empty_ticket Apr 26 06:41:25 192.168.122.209 [52635.912470] Start test: tls.test_tls_tickets.StandardTlsClient.test Apr 26 06:41:26 192.168.122.209 [52636.941253] [tdb] Start Tempesta DB Apr 26 06:41:26 192.168.122.209 [52637.083808] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:41:27 192.168.122.209 [52637.824574] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52637.824574] Maybe that's fine, but it's worth checking the [52637.824574] config - if there is no relations between the [52637.824574] names, then host name confusion attack is possible. Apr 26 06:41:27 192.168.122.209 [52637.975348] [tempesta fw] Configuration processing is completed. Apr 26 06:41:27 192.168.122.209 [52638.027244] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:41:27 192.168.122.209 [52638.057646] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:41:27 192.168.122.209 [52638.086587] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:41:27 192.168.122.209 [52638.131277] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:41:27 192.168.122.209 [52638.179292] [tempesta fw] Tempesta FW is ready Apr 26 06:41:29 192.168.122.209 [52639.816778] [tdb] Close table 'client0.tdb' Apr 26 06:41:29 192.168.122.209 [52640.004556] [tdb] Close table 'sessions0.tdb' Apr 26 06:41:29 192.168.122.209 [52640.243533] [tdb] Close table 'filter0.tdb' Apr 26 06:41:29 192.168.122.209 [52640.243971] [tempesta fw] modules are stopped Apr 26 06:41:29 192.168.122.209 [52640.443572] [tempesta fw] exiting... Apr 26 06:41:30 192.168.122.209 [52640.604337] [tdb] Shutdown Tempesta DB Apr 26 06:41:30 192.168.122.209 [52640.848708] End test: tls.test_tls_tickets.StandardTlsClient.test Apr 26 06:41:30 192.168.122.209 [52640.859732] Start test: tls.test_tls_limits.TLSMatchHostSni.test_host_sni_mismatch Apr 26 06:41:31 192.168.122.209 [52641.846025] [tdb] Start Tempesta DB Apr 26 06:41:31 192.168.122.209 [52641.972232] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:41:32 192.168.122.209 [52642.928874] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52642.928874] Maybe that's fine, but it's worth checking the [52642.928874] config - if there is no relations between the [52642.928874] names, then host name confusion attack is possible. Apr 26 06:41:32 192.168.122.209 [52643.059402] [tempesta fw] Configuration processing is completed. Apr 26 06:41:32 192.168.122.209 [52643.109302] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:41:32 192.168.122.209 [52643.136654] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:41:32 192.168.122.209 [52643.164010] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:41:32 192.168.122.209 [52643.227287] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:41:32 192.168.122.209 [52643.279326] [tempesta fw] Tempesta FW is ready Apr 26 06:41:33 192.168.122.209 [52643.512993] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.2 ('default' vs 'dummy') Apr 26 06:41:33 192.168.122.209 [52643.514018] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 06:41:33 192.168.122.209 [52644.048037] [tdb] Close table 'client0.tdb' Apr 26 06:41:33 192.168.122.209 [52644.232999] [tdb] Close table 'sessions0.tdb' Apr 26 06:41:34 192.168.122.209 [52644.477970] [tdb] Close table 'filter0.tdb' Apr 26 06:41:34 192.168.122.209 [52644.478402] [tempesta fw] modules are stopped Apr 26 06:41:34 192.168.122.209 [52644.743313] [tempesta fw] exiting... Apr 26 06:41:34 192.168.122.209 [52644.862545] [tdb] Shutdown Tempesta DB Apr 26 06:41:34 192.168.122.209 [52645.080226] End test: tls.test_tls_limits.TLSMatchHostSni.test_host_sni_mismatch Apr 26 06:41:34 192.168.122.209 [52645.088722] Start test: tls.test_tls_kernel.TCrypt.test_tcrypt Apr 26 06:41:35 192.168.122.209 [52645.529587] End test: tls.test_tls_kernel.TCrypt.test_tcrypt Apr 26 06:41:35 192.168.122.209 [52645.537662] Start test: tls.test_tls_integrity.Proxy.test_various_req_resp_sizes Apr 26 06:41:36 192.168.122.209 [52646.572903] [tdb] Start Tempesta DB Apr 26 06:41:36 192.168.122.209 [52646.698722] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:41:36 192.168.122.209 [52647.216758] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52647.216758] Maybe that's fine, but it's worth checking the [52647.216758] config - if there is no relations between the [52647.216758] names, then host name confusion attack is possible. Apr 26 06:41:36 192.168.122.209 [52647.319521] [tempesta fw] Configuration processing is completed. Apr 26 06:41:36 192.168.122.209 [52647.370096] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:41:36 192.168.122.209 [52647.399937] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:41:36 192.168.122.209 [52647.428288] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:41:37 192.168.122.209 [52647.495422] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:41:37 192.168.122.209 [52647.535345] [tempesta fw] Tempesta FW is ready Apr 26 06:42:12 192.168.122.209 [52682.746497] [tdb] Close table 'client0.tdb' Apr 26 06:42:12 192.168.122.209 [52682.996415] [tdb] Close table 'sessions0.tdb' Apr 26 06:42:12 192.168.122.209 [52683.269776] [tdb] Close table 'filter0.tdb' Apr 26 06:42:12 192.168.122.209 [52683.270238] [tempesta fw] modules are stopped Apr 26 06:42:12 192.168.122.209 [52683.465798] [tempesta fw] exiting... Apr 26 06:42:13 192.168.122.209 [52683.611062] [tdb] Shutdown Tempesta DB Apr 26 06:42:13 192.168.122.209 [52684.045238] End test: tls.test_tls_integrity.Proxy.test_various_req_resp_sizes Apr 26 06:42:13 192.168.122.209 [52684.065553] Start test: tls.test_tls_integrity.ManyClientsH2.test_various_req_resp_sizes Apr 26 06:42:14 192.168.122.209 [52685.242683] [tdb] Start Tempesta DB Apr 26 06:42:14 192.168.122.209 [52685.455739] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:42:15 192.168.122.209 [52686.109262] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52686.109262] Maybe that's fine, but it's worth checking the [52686.109262] config - if there is no relations between the [52686.109262] names, then host name confusion attack is possible. Apr 26 06:42:15 192.168.122.209 [52686.243992] [tempesta fw] Configuration processing is completed. Apr 26 06:42:15 192.168.122.209 [52686.301400] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:42:15 192.168.122.209 [52686.334517] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:42:15 192.168.122.209 [52686.374463] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:42:15 192.168.122.209 [52686.431911] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:42:16 192.168.122.209 [52686.471859] [tempesta fw] Tempesta FW is ready Apr 26 06:42:25 192.168.122.209 [52696.043460] [tdb] Close table 'client0.tdb' Apr 26 06:42:25 192.168.122.209 [52696.250200] [tdb] Close table 'sessions0.tdb' Apr 26 06:42:26 192.168.122.209 [52696.481757] [tdb] Close table 'filter0.tdb' Apr 26 06:42:26 192.168.122.209 [52696.482212] [tempesta fw] modules are stopped Apr 26 06:42:26 192.168.122.209 [52696.740692] [tempesta fw] exiting... Apr 26 06:42:26 192.168.122.209 [52696.846512] [tdb] Shutdown Tempesta DB Apr 26 06:42:26 192.168.122.209 [52697.081487] End test: tls.test_tls_integrity.ManyClientsH2.test_various_req_resp_sizes Apr 26 06:42:26 192.168.122.209 [52697.095641] Start test: tls.test_tls_integrity.ManyClients.test_various_req_resp_sizes Apr 26 06:42:27 192.168.122.209 [52698.125368] [tdb] Start Tempesta DB Apr 26 06:42:27 192.168.122.209 [52698.272208] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:42:28 192.168.122.209 [52698.824572] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52698.824572] Maybe that's fine, but it's worth checking the [52698.824572] config - if there is no relations between the [52698.824572] names, then host name confusion attack is possible. Apr 26 06:42:28 192.168.122.209 [52698.920094] [tempesta fw] Configuration processing is completed. Apr 26 06:42:28 192.168.122.209 [52698.971525] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:42:28 192.168.122.209 [52699.004469] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:42:28 192.168.122.209 [52699.045536] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:42:28 192.168.122.209 [52699.084127] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:42:28 192.168.122.209 [52699.132035] [tempesta fw] Tempesta FW is ready Apr 26 06:42:33 192.168.122.209 [52703.476250] [tdb] Close table 'client0.tdb' Apr 26 06:42:33 192.168.122.209 [52703.663267] [tdb] Close table 'sessions0.tdb' Apr 26 06:42:33 192.168.122.209 [52703.889669] [tdb] Close table 'filter0.tdb' Apr 26 06:42:33 192.168.122.209 [52703.890146] [tempesta fw] modules are stopped Apr 26 06:42:33 192.168.122.209 [52704.101498] [tempesta fw] exiting... Apr 26 06:42:33 192.168.122.209 [52704.276628] [tdb] Shutdown Tempesta DB Apr 26 06:42:34 192.168.122.209 [52704.491735] End test: tls.test_tls_integrity.ManyClients.test_various_req_resp_sizes Apr 26 06:42:34 192.168.122.209 [52704.509911] Start test: tls.test_tls_integrity.CloseConnection.test7 Apr 26 06:42:35 192.168.122.209 [52705.600261] [tdb] Start Tempesta DB Apr 26 06:42:35 192.168.122.209 [52705.743043] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:42:35 192.168.122.209 [52706.348683] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52706.348683] Maybe that's fine, but it's worth checking the [52706.348683] config - if there is no relations between the [52706.348683] names, then host name confusion attack is possible. Apr 26 06:42:35 192.168.122.209 [52706.436206] [tempesta fw] Configuration processing is completed. Apr 26 06:42:36 192.168.122.209 [52706.490856] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:42:36 192.168.122.209 [52706.519281] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:42:36 192.168.122.209 [52706.558550] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:42:36 192.168.122.209 [52706.600190] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:42:36 192.168.122.209 [52706.640056] [tempesta fw] Tempesta FW is ready Apr 26 06:42:49 192.168.122.209 [52719.536641] [tdb] Close table 'client0.tdb' Apr 26 06:42:49 192.168.122.209 [52719.747318] [tdb] Close table 'sessions0.tdb' Apr 26 06:42:49 192.168.122.209 [52720.010507] [tdb] Close table 'filter0.tdb' Apr 26 06:42:49 192.168.122.209 [52720.011050] [tempesta fw] modules are stopped Apr 26 06:42:49 192.168.122.209 [52720.314401] [tempesta fw] exiting... Apr 26 06:42:49 192.168.122.209 [52720.441240] [tdb] Shutdown Tempesta DB Apr 26 06:42:50 192.168.122.209 [52720.668923] End test: tls.test_tls_integrity.CloseConnection.test7 Apr 26 06:42:50 192.168.122.209 [52720.682082] Start test: tls.test_tls_integrity.CloseConnection.test6 Apr 26 06:42:51 192.168.122.209 [52721.759235] [tdb] Start Tempesta DB Apr 26 06:42:51 192.168.122.209 [52721.902380] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:42:52 192.168.122.209 [52722.497696] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52722.497696] Maybe that's fine, but it's worth checking the [52722.497696] config - if there is no relations between the [52722.497696] names, then host name confusion attack is possible. Apr 26 06:42:52 192.168.122.209 [52722.612447] [tempesta fw] Configuration processing is completed. Apr 26 06:42:52 192.168.122.209 [52722.667132] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:42:52 192.168.122.209 [52722.696905] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:42:52 192.168.122.209 [52722.734297] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:42:52 192.168.122.209 [52722.796403] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:42:52 192.168.122.209 [52722.844333] [tempesta fw] Tempesta FW is ready Apr 26 06:42:55 192.168.122.209 [52726.332032] [tdb] Close table 'client0.tdb' Apr 26 06:42:56 192.168.122.209 [52726.521328] [tdb] Close table 'sessions0.tdb' Apr 26 06:42:56 192.168.122.209 [52726.753721] [tdb] Close table 'filter0.tdb' Apr 26 06:42:56 192.168.122.209 [52726.754151] [tempesta fw] modules are stopped Apr 26 06:42:56 192.168.122.209 [52726.933907] [tempesta fw] exiting... Apr 26 06:42:56 192.168.122.209 [52727.075177] [tdb] Shutdown Tempesta DB Apr 26 06:42:56 192.168.122.209 [52727.296431] End test: tls.test_tls_integrity.CloseConnection.test6 Apr 26 06:42:56 192.168.122.209 [52727.307248] Start test: tls.test_tls_integrity.CloseConnection.test5 Apr 26 06:42:57 192.168.122.209 [52728.383742] [tdb] Start Tempesta DB Apr 26 06:42:58 192.168.122.209 [52728.517443] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:42:58 192.168.122.209 [52729.101896] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52729.101896] Maybe that's fine, but it's worth checking the [52729.101896] config - if there is no relations between the [52729.101896] names, then host name confusion attack is possible. Apr 26 06:42:58 192.168.122.209 [52729.204521] [tempesta fw] Configuration processing is completed. Apr 26 06:42:58 192.168.122.209 [52729.254780] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:42:58 192.168.122.209 [52729.286097] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:42:58 192.168.122.209 [52729.312894] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:42:58 192.168.122.209 [52729.368454] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:42:58 192.168.122.209 [52729.412405] [tempesta fw] Tempesta FW is ready Apr 26 06:43:00 192.168.122.209 [52730.706861] [tdb] Close table 'client0.tdb' Apr 26 06:43:00 192.168.122.209 [52730.895537] [tdb] Close table 'sessions0.tdb' Apr 26 06:43:00 192.168.122.209 [52731.131524] [tdb] Close table 'filter0.tdb' Apr 26 06:43:00 192.168.122.209 [52731.131963] [tempesta fw] modules are stopped Apr 26 06:43:00 192.168.122.209 [52731.316201] [tempesta fw] exiting... Apr 26 06:43:00 192.168.122.209 [52731.440985] [tdb] Shutdown Tempesta DB Apr 26 06:43:01 192.168.122.209 [52731.650871] End test: tls.test_tls_integrity.CloseConnection.test5 Apr 26 06:43:01 192.168.122.209 [52731.669090] Start test: tls.test_tls_integrity.CloseConnection.test4 Apr 26 06:43:02 192.168.122.209 [52732.689419] [tdb] Start Tempesta DB Apr 26 06:43:02 192.168.122.209 [52732.824041] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:43:02 192.168.122.209 [52733.429820] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52733.429820] Maybe that's fine, but it's worth checking the [52733.429820] config - if there is no relations between the [52733.429820] names, then host name confusion attack is possible. Apr 26 06:43:03 192.168.122.209 [52733.532612] [tempesta fw] Configuration processing is completed. Apr 26 06:43:03 192.168.122.209 [52733.583245] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:43:03 192.168.122.209 [52733.613041] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:43:03 192.168.122.209 [52733.640393] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:43:03 192.168.122.209 [52733.688514] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:43:03 192.168.122.209 [52733.736458] [tempesta fw] Tempesta FW is ready Apr 26 06:43:04 192.168.122.209 [52734.674278] [tdb] Close table 'client0.tdb' Apr 26 06:43:04 192.168.122.209 [52734.867204] [tdb] Close table 'sessions0.tdb' Apr 26 06:43:04 192.168.122.209 [52735.111191] [tdb] Close table 'filter0.tdb' Apr 26 06:43:04 192.168.122.209 [52735.111635] [tempesta fw] modules are stopped Apr 26 06:43:04 192.168.122.209 [52735.299008] [tempesta fw] exiting... Apr 26 06:43:04 192.168.122.209 [52735.459760] [tdb] Shutdown Tempesta DB Apr 26 06:43:05 192.168.122.209 [52735.696128] End test: tls.test_tls_integrity.CloseConnection.test4 Apr 26 06:43:05 192.168.122.209 [52735.713690] Start test: tls.test_tls_integrity.CloseConnection.test3 Apr 26 06:43:06 192.168.122.209 [52736.778463] [tdb] Start Tempesta DB Apr 26 06:43:06 192.168.122.209 [52736.917997] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:43:07 192.168.122.209 [52737.529696] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52737.529696] Maybe that's fine, but it's worth checking the [52737.529696] config - if there is no relations between the [52737.529696] names, then host name confusion attack is possible. Apr 26 06:43:07 192.168.122.209 [52737.640611] [tempesta fw] Configuration processing is completed. Apr 26 06:43:07 192.168.122.209 [52737.691483] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:43:07 192.168.122.209 [52737.718753] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:43:07 192.168.122.209 [52737.749789] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:43:07 192.168.122.209 [52737.788608] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:43:07 192.168.122.209 [52737.832506] [tempesta fw] Tempesta FW is ready Apr 26 06:43:08 192.168.122.209 [52738.537655] [tdb] Close table 'client0.tdb' Apr 26 06:43:08 192.168.122.209 [52738.727983] [tdb] Close table 'sessions0.tdb' Apr 26 06:43:08 192.168.122.209 [52738.983555] [tdb] Close table 'filter0.tdb' Apr 26 06:43:08 192.168.122.209 [52738.984008] [tempesta fw] modules are stopped Apr 26 06:43:08 192.168.122.209 [52739.207285] [tempesta fw] exiting... Apr 26 06:43:08 192.168.122.209 [52739.340971] [tdb] Shutdown Tempesta DB Apr 26 06:43:09 192.168.122.209 [52739.561134] End test: tls.test_tls_integrity.CloseConnection.test3 Apr 26 06:43:09 192.168.122.209 [52739.583454] Start test: tls.test_tls_integrity.CloseConnection.test2 Apr 26 06:43:10 192.168.122.209 [52740.660173] [tdb] Start Tempesta DB Apr 26 06:43:10 192.168.122.209 [52740.798145] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:43:10 192.168.122.209 [52741.369092] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52741.369092] Maybe that's fine, but it's worth checking the [52741.369092] config - if there is no relations between the [52741.369092] names, then host name confusion attack is possible. Apr 26 06:43:11 192.168.122.209 [52741.480943] [tempesta fw] Configuration processing is completed. Apr 26 06:43:11 192.168.122.209 [52741.536163] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:43:11 192.168.122.209 [52741.563478] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:43:11 192.168.122.209 [52741.591883] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:43:11 192.168.122.209 [52741.676605] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:43:11 192.168.122.209 [52741.724546] [tempesta fw] Tempesta FW is ready Apr 26 06:43:11 192.168.122.209 [52742.307958] [tdb] Close table 'client0.tdb' Apr 26 06:43:12 192.168.122.209 [52742.520334] [tdb] Close table 'sessions0.tdb' Apr 26 06:43:12 192.168.122.209 [52742.762557] [tdb] Close table 'filter0.tdb' Apr 26 06:43:12 192.168.122.209 [52742.762998] [tempesta fw] modules are stopped Apr 26 06:43:12 192.168.122.209 [52742.969049] [tempesta fw] exiting... Apr 26 06:43:12 192.168.122.209 [52743.118881] [tdb] Shutdown Tempesta DB Apr 26 06:43:12 192.168.122.209 [52743.364210] End test: tls.test_tls_integrity.CloseConnection.test2 Apr 26 06:43:12 192.168.122.209 [52743.375060] Start test: tls.test_tls_integrity.CloseConnection.test1 Apr 26 06:43:13 192.168.122.209 [52744.327933] [tdb] Start Tempesta DB Apr 26 06:43:13 192.168.122.209 [52744.465674] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:43:14 192.168.122.209 [52745.001951] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52745.001951] Maybe that's fine, but it's worth checking the [52745.001951] config - if there is no relations between the [52745.001951] names, then host name confusion attack is possible. Apr 26 06:43:14 192.168.122.209 [52745.100723] [tempesta fw] Configuration processing is completed. Apr 26 06:43:14 192.168.122.209 [52745.170134] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:43:14 192.168.122.209 [52745.200570] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:43:14 192.168.122.209 [52745.230089] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:43:14 192.168.122.209 [52745.316649] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:43:14 192.168.122.209 [52745.360608] [tempesta fw] Tempesta FW is ready Apr 26 06:43:15 192.168.122.209 [52745.909838] [tdb] Close table 'client0.tdb' Apr 26 06:43:15 192.168.122.209 [52746.103701] [tdb] Close table 'sessions0.tdb' Apr 26 06:43:15 192.168.122.209 [52746.340225] [tdb] Close table 'filter0.tdb' Apr 26 06:43:15 192.168.122.209 [52746.340678] [tempesta fw] modules are stopped Apr 26 06:43:16 192.168.122.209 [52746.581193] [tempesta fw] exiting... Apr 26 06:43:16 192.168.122.209 [52746.703986] [tdb] Shutdown Tempesta DB Apr 26 06:43:16 192.168.122.209 [52746.936673] End test: tls.test_tls_integrity.CloseConnection.test1 Apr 26 06:43:16 192.168.122.209 [52746.958303] Start test: tls.test_tls_integrity.CacheH2.test_various_req_resp_sizes Apr 26 06:43:17 192.168.122.209 [52748.025943] [tdb] Start Tempesta DB Apr 26 06:43:17 192.168.122.209 [52748.167194] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:43:18 192.168.122.209 [52748.714012] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52748.714012] Maybe that's fine, but it's worth checking the [52748.714012] config - if there is no relations between the [52748.714012] names, then host name confusion attack is possible. Apr 26 06:43:18 192.168.122.209 [52748.796725] [tempesta fw] Configuration processing is completed. Apr 26 06:43:18 192.168.122.209 [52748.852555] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:43:19 192.168.122.209 [52749.563225] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:43:19 192.168.122.209 [52749.611915] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:43:19 192.168.122.209 [52749.659499] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:43:19 192.168.122.209 [52749.704676] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:43:19 192.168.122.209 [52749.748577] [tempesta fw] Tempesta FW is ready Apr 26 06:43:29 192.168.122.209 [52760.399300] [tdb] Close table 'client0.tdb' Apr 26 06:43:30 192.168.122.209 [52760.590296] [tdb] Close table 'sessions0.tdb' Apr 26 06:43:33 192.168.122.209 [52763.778935] [tdb] Close table 'cache0.tdb' Apr 26 06:43:33 192.168.122.209 [52764.014301] [tdb] Close table 'filter0.tdb' Apr 26 06:43:33 192.168.122.209 [52764.015036] [tempesta fw] modules are stopped Apr 26 06:43:33 192.168.122.209 [52764.186316] [tempesta fw] exiting... Apr 26 06:43:33 192.168.122.209 [52764.317919] [tdb] Shutdown Tempesta DB Apr 26 06:43:34 192.168.122.209 [52764.510763] End test: tls.test_tls_integrity.CacheH2.test_various_req_resp_sizes Apr 26 06:43:34 192.168.122.209 [52764.535749] Start test: tls.test_tls_integrity.Cache.test_various_req_resp_sizes Apr 26 06:43:35 192.168.122.209 [52765.549419] [tdb] Start Tempesta DB Apr 26 06:43:35 192.168.122.209 [52765.688074] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:43:36 192.168.122.209 [52767.058201] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52767.058201] Maybe that's fine, but it's worth checking the [52767.058201] config - if there is no relations between the [52767.058201] names, then host name confusion attack is possible. Apr 26 06:43:36 192.168.122.209 [52767.172983] [tempesta fw] Configuration processing is completed. Apr 26 06:43:36 192.168.122.209 [52767.223016] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:43:37 192.168.122.209 [52767.661022] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:43:37 192.168.122.209 [52767.688310] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:43:37 192.168.122.209 [52767.715082] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:43:37 192.168.122.209 [52767.756886] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:43:37 192.168.122.209 [52767.796819] [tempesta fw] Tempesta FW is ready Apr 26 06:43:48 192.168.122.209 [52778.816669] [tdb] Close table 'client0.tdb' Apr 26 06:43:48 192.168.122.209 [52779.014470] [tdb] Close table 'sessions0.tdb' Apr 26 06:43:51 192.168.122.209 [52782.286592] [tdb] Close table 'cache0.tdb' Apr 26 06:43:52 192.168.122.209 [52782.500676] [tdb] Close table 'filter0.tdb' Apr 26 06:43:52 192.168.122.209 [52782.501142] [tempesta fw] modules are stopped Apr 26 06:43:52 192.168.122.209 [52782.710470] [tempesta fw] exiting... Apr 26 06:43:52 192.168.122.209 [52782.813686] [tdb] Shutdown Tempesta DB Apr 26 06:43:52 192.168.122.209 [52783.013914] End test: tls.test_tls_integrity.Cache.test_various_req_resp_sizes Apr 26 06:43:52 192.168.122.209 [52783.042050] Start test: tls.test_tls_handshake.TlsVhostHandshakeTest.test_vhost_sni Apr 26 06:43:53 192.168.122.209 [52784.106318] [tdb] Start Tempesta DB Apr 26 06:43:53 192.168.122.209 [52784.242675] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:43:55 192.168.122.209 [52785.990524] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52785.990524] Maybe that's fine, but it's worth checking the [52785.990524] config - if there is no relations between the [52785.990524] names, then host name confusion attack is possible. Apr 26 06:43:55 192.168.122.209 [52786.063361] [tempesta fw] Warning: Vhost vhost2.net doesn't have certificate with matching SAN/CN. [52786.063361] Maybe that's fine, but it's worth checking the [52786.063361] config - if there is no relations between the [52786.063361] names, then host name confusion attack is possible. Apr 26 06:43:55 192.168.122.209 [52786.145229] [tempesta fw] Configuration processing is completed. Apr 26 06:43:55 192.168.122.209 [52786.195072] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:43:55 192.168.122.209 [52786.222167] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:43:55 192.168.122.209 [52786.250058] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:43:55 192.168.122.209 [52786.317207] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:43:55 192.168.122.209 [52786.409125] [tempesta fw] Tempesta FW is ready Apr 26 06:43:56 192.168.122.209 [52786.548706] device enp1s0 entered promiscuous mode Apr 26 06:43:56 192.168.122.209 [52786.657384] device enp1s0 left promiscuous mode Apr 26 06:43:56 192.168.122.209 [52786.679042] device enp1s0 entered promiscuous mode Apr 26 06:43:56 192.168.122.209 [52786.889601] device enp1s0 left promiscuous mode Apr 26 06:43:56 192.168.122.209 [52787.409971] [tdb] Close table 'client0.tdb' Apr 26 06:43:57 192.168.122.209 [52787.613560] [tdb] Close table 'sessions0.tdb' Apr 26 06:43:57 192.168.122.209 [52787.842924] [tdb] Close table 'filter0.tdb' Apr 26 06:43:57 192.168.122.209 [52787.843363] [tempesta fw] modules are stopped Apr 26 06:43:57 192.168.122.209 [52788.101290] [tempesta fw] exiting... Apr 26 06:43:57 192.168.122.209 [52788.240898] [tdb] Shutdown Tempesta DB Apr 26 06:43:57 192.168.122.209 [52788.428277] End test: tls.test_tls_handshake.TlsVhostHandshakeTest.test_vhost_sni Apr 26 06:43:57 192.168.122.209 [52788.440550] Start test: tls.test_tls_handshake.TlsVhostHandshakeTest.test_empty_sni_default Apr 26 06:43:58 192.168.122.209 [52789.455430] [tdb] Start Tempesta DB Apr 26 06:43:59 192.168.122.209 [52789.602344] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:44:00 192.168.122.209 [52790.594479] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52790.594479] Maybe that's fine, but it's worth checking the [52790.594479] config - if there is no relations between the [52790.594479] names, then host name confusion attack is possible. Apr 26 06:44:00 192.168.122.209 [52790.663122] [tempesta fw] Warning: Vhost vhost2.net doesn't have certificate with matching SAN/CN. [52790.663122] Maybe that's fine, but it's worth checking the [52790.663122] config - if there is no relations between the [52790.663122] names, then host name confusion attack is possible. Apr 26 06:44:00 192.168.122.209 [52790.741282] [tempesta fw] Configuration processing is completed. Apr 26 06:44:00 192.168.122.209 [52790.803531] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:44:00 192.168.122.209 [52790.833821] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:44:00 192.168.122.209 [52790.862705] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:44:00 192.168.122.209 [52790.941169] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:44:00 192.168.122.209 [52791.001170] [tempesta fw] Tempesta FW is ready Apr 26 06:44:00 192.168.122.209 [52791.156955] device enp1s0 entered promiscuous mode Apr 26 06:44:00 192.168.122.209 [52791.199504] [tempesta fw] Warning: client 127.0.0.1 requested missing server name, reject connection. Apr 26 06:44:00 192.168.122.209 [52791.225653] device enp1s0 left promiscuous mode Apr 26 06:44:00 192.168.122.209 [52791.249143] device enp1s0 entered promiscuous mode Apr 26 06:44:00 192.168.122.209 [52791.357699] device enp1s0 left promiscuous mode Apr 26 06:44:01 192.168.122.209 [52791.853798] [tdb] Close table 'client0.tdb' Apr 26 06:44:01 192.168.122.209 [52792.039684] [tdb] Close table 'sessions0.tdb' Apr 26 06:44:01 192.168.122.209 [52792.262437] [tdb] Close table 'filter0.tdb' Apr 26 06:44:01 192.168.122.209 [52792.262852] [tempesta fw] modules are stopped Apr 26 06:44:02 192.168.122.209 [52792.498476] [tempesta fw] exiting... Apr 26 06:44:02 192.168.122.209 [52792.617297] [tdb] Shutdown Tempesta DB Apr 26 06:44:02 192.168.122.209 [52792.823245] End test: tls.test_tls_handshake.TlsVhostHandshakeTest.test_empty_sni_default Apr 26 06:44:02 192.168.122.209 [52792.847076] Start test: tls.test_tls_handshake.TlsVhostHandshakeTest.test_bad_host Apr 26 06:44:03 192.168.122.209 [52793.910290] [tdb] Start Tempesta DB Apr 26 06:44:03 192.168.122.209 [52794.054194] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:44:04 192.168.122.209 [52795.058539] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52795.058539] Maybe that's fine, but it's worth checking the [52795.058539] config - if there is no relations between the [52795.058539] names, then host name confusion attack is possible. Apr 26 06:44:04 192.168.122.209 [52795.119202] [tempesta fw] Warning: Vhost vhost2.net doesn't have certificate with matching SAN/CN. [52795.119202] Maybe that's fine, but it's worth checking the [52795.119202] config - if there is no relations between the [52795.119202] names, then host name confusion attack is possible. Apr 26 06:44:04 192.168.122.209 [52795.209320] [tempesta fw] Configuration processing is completed. Apr 26 06:44:04 192.168.122.209 [52795.260140] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:44:04 192.168.122.209 [52795.290112] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:44:04 192.168.122.209 [52795.318488] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:44:04 192.168.122.209 [52795.377279] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:44:04 192.168.122.209 [52795.437246] [tempesta fw] Tempesta FW is ready Apr 26 06:44:05 192.168.122.209 [52795.576698] device enp1s0 entered promiscuous mode Apr 26 06:44:05 192.168.122.209 [52795.658536] [tempesta fw] Warning: request has been filtered out via http table: 127.0.0.1 Apr 26 06:44:05 192.168.122.209 [52795.673511] device enp1s0 left promiscuous mode Apr 26 06:44:10 192.168.122.209 [52801.097790] [tdb] Close table 'client0.tdb' Apr 26 06:44:10 192.168.122.209 [52801.288637] [tdb] Close table 'sessions0.tdb' Apr 26 06:44:11 192.168.122.209 [52801.495829] [tdb] Close table 'filter0.tdb' Apr 26 06:44:11 192.168.122.209 [52801.496251] [tempesta fw] modules are stopped Apr 26 06:44:11 192.168.122.209 [52801.759138] [tempesta fw] exiting... Apr 26 06:44:11 192.168.122.209 [52801.886351] [tdb] Shutdown Tempesta DB Apr 26 06:44:11 192.168.122.209 [52802.111805] End test: tls.test_tls_handshake.TlsVhostHandshakeTest.test_bad_host Apr 26 06:44:11 192.168.122.209 [52802.134859] Start test: tls.test_tls_handshake.TlsMissingDefaultKey.test Apr 26 06:44:12 192.168.122.209 [52803.194139] [tdb] Start Tempesta DB Apr 26 06:44:12 192.168.122.209 [52803.357788] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:44:13 192.168.122.209 [52804.055298] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [52804.055298] Maybe that's fine, but it's worth checking the [52804.055298] config - if there is no relations between the [52804.055298] names, then host name confusion attack is possible. Apr 26 06:44:13 192.168.122.209 [52804.109470] [tempesta fw] Configuration processing is completed. Apr 26 06:44:13 192.168.122.209 [52804.163425] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:44:13 192.168.122.209 [52804.196644] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:44:13 192.168.122.209 [52804.228850] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:44:13 192.168.122.209 [52804.277387] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:44:13 192.168.122.209 [52804.317335] [tempesta fw] Tempesta FW is ready Apr 26 06:44:13 192.168.122.209 [52804.452750] device enp1s0 entered promiscuous mode Apr 26 06:44:14 192.168.122.209 [52804.545619] device enp1s0 left promiscuous mode Apr 26 06:44:14 192.168.122.209 [52804.567601] device enp1s0 entered promiscuous mode Apr 26 06:44:14 192.168.122.209 [52804.623725] [tempesta fw] Warning: client 127.0.0.1 requested unknown server name 'example.com' in TLS SNI, reject connection. Apr 26 06:44:14 192.168.122.209 [52804.645965] device enp1s0 left promiscuous mode Apr 26 06:44:14 192.168.122.209 [52804.668059] device enp1s0 entered promiscuous mode Apr 26 06:44:14 192.168.122.209 [52804.715946] [tempesta fw] Warning: client 127.0.0.1 requested missing server name, reject connection. Apr 26 06:44:14 192.168.122.209 [52804.741834] device enp1s0 left promiscuous mode Apr 26 06:44:14 192.168.122.209 [52805.303599] [tdb] Close table 'client0.tdb' Apr 26 06:44:15 192.168.122.209 [52805.491847] [tdb] Close table 'sessions0.tdb' Apr 26 06:44:15 192.168.122.209 [52805.726347] [tdb] Close table 'filter0.tdb' Apr 26 06:44:15 192.168.122.209 [52805.726771] [tempesta fw] modules are stopped Apr 26 06:44:15 192.168.122.209 [52805.983348] [tempesta fw] exiting... Apr 26 06:44:15 192.168.122.209 [52806.085136] [tdb] Shutdown Tempesta DB Apr 26 06:44:15 192.168.122.209 [52806.290553] End test: tls.test_tls_handshake.TlsMissingDefaultKey.test Apr 26 06:44:15 192.168.122.209 [52806.304211] Start test: tls.test_tls_handshake.TlsHandshakeTest.test_tls12_synthetic Apr 26 06:44:16 192.168.122.209 [52807.360483] [tdb] Start Tempesta DB Apr 26 06:44:17 192.168.122.209 [52807.500065] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:44:17 192.168.122.209 [52808.258885] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52808.258885] Maybe that's fine, but it's worth checking the [52808.258885] config - if there is no relations between the [52808.258885] names, then host name confusion attack is possible. Apr 26 06:44:17 192.168.122.209 [52808.373324] [tempesta fw] Configuration processing is completed. Apr 26 06:44:17 192.168.122.209 [52808.421877] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:44:17 192.168.122.209 [52808.449980] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:44:18 192.168.122.209 [52808.478566] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:44:18 192.168.122.209 [52808.521461] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:44:18 192.168.122.209 [52808.561404] [tempesta fw] Tempesta FW is ready Apr 26 06:44:18 192.168.122.209 [52808.696379] device enp1s0 entered promiscuous mode Apr 26 06:44:18 192.168.122.209 [52808.801763] device enp1s0 left promiscuous mode Apr 26 06:44:18 192.168.122.209 [52809.245008] [tdb] Close table 'client0.tdb' Apr 26 06:44:18 192.168.122.209 [52809.449254] [tdb] Close table 'sessions0.tdb' Apr 26 06:44:19 192.168.122.209 [52809.675859] [tdb] Close table 'filter0.tdb' Apr 26 06:44:19 192.168.122.209 [52809.676316] [tempesta fw] modules are stopped Apr 26 06:44:19 192.168.122.209 [52809.997241] [tempesta fw] exiting... Apr 26 06:44:19 192.168.122.209 [52810.142510] [tdb] Shutdown Tempesta DB Apr 26 06:44:19 192.168.122.209 [52810.391116] End test: tls.test_tls_handshake.TlsHandshakeTest.test_tls12_synthetic Apr 26 06:44:19 192.168.122.209 [52810.400291] Start test: tls.test_tls_handshake.TlsHandshakeTest.test_regression_1 Apr 26 06:44:20 192.168.122.209 [52811.451740] [tdb] Start Tempesta DB Apr 26 06:44:21 192.168.122.209 [52811.600910] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:44:21 192.168.122.209 [52812.390956] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52812.390956] Maybe that's fine, but it's worth checking the [52812.390956] config - if there is no relations between the [52812.390956] names, then host name confusion attack is possible. Apr 26 06:44:22 192.168.122.209 [52812.521546] [tempesta fw] Configuration processing is completed. Apr 26 06:44:22 192.168.122.209 [52812.572796] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:44:22 192.168.122.209 [52812.601725] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:44:22 192.168.122.209 [52812.629629] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:44:22 192.168.122.209 [52812.673492] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:44:22 192.168.122.209 [52812.713476] [tempesta fw] Tempesta FW is ready Apr 26 06:44:22 192.168.122.209 [52812.857956] device enp1s0 entered promiscuous mode Apr 26 06:44:22 192.168.122.209 [52812.933052] [tempesta tls] Warning: [::ffff:127.0.0.1] TLS context isn't ready after handshake Apr 26 06:44:22 192.168.122.209 [52812.949711] device enp1s0 left promiscuous mode Apr 26 06:44:22 192.168.122.209 [52813.393457] [tdb] Close table 'client0.tdb' Apr 26 06:44:23 192.168.122.209 [52813.583380] [tdb] Close table 'sessions0.tdb' Apr 26 06:44:23 192.168.122.209 [52813.789540] [tdb] Close table 'filter0.tdb' Apr 26 06:44:23 192.168.122.209 [52813.789983] [tempesta fw] modules are stopped Apr 26 06:44:23 192.168.122.209 [52814.005223] [tempesta fw] exiting... Apr 26 06:44:23 192.168.122.209 [52814.122178] [tdb] Shutdown Tempesta DB Apr 26 06:44:23 192.168.122.209 [52814.338001] End test: tls.test_tls_handshake.TlsHandshakeTest.test_regression_1 Apr 26 06:44:23 192.168.122.209 [52814.354128] Start test: tls.test_tls_handshake.TlsHandshakeTest.test_old_handshakes Apr 26 06:44:24 192.168.122.209 [52815.370255] [tdb] Start Tempesta DB Apr 26 06:44:25 192.168.122.209 [52815.506187] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:44:25 192.168.122.209 [52816.230624] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52816.230624] Maybe that's fine, but it's worth checking the [52816.230624] config - if there is no relations between the [52816.230624] names, then host name confusion attack is possible. Apr 26 06:44:25 192.168.122.209 [52816.345558] [tempesta fw] Configuration processing is completed. Apr 26 06:44:25 192.168.122.209 [52816.399755] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:44:25 192.168.122.209 [52816.427329] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:44:25 192.168.122.209 [52816.454559] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:44:26 192.168.122.209 [52816.501549] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:44:26 192.168.122.209 [52816.541514] [tempesta fw] Tempesta FW is ready Apr 26 06:44:26 192.168.122.209 [52817.165195] [tdb] Close table 'client0.tdb' Apr 26 06:44:26 192.168.122.209 [52817.351848] [tdb] Close table 'sessions0.tdb' Apr 26 06:44:27 192.168.122.209 [52817.579814] [tdb] Close table 'filter0.tdb' Apr 26 06:44:27 192.168.122.209 [52817.580229] [tempesta fw] modules are stopped Apr 26 06:44:27 192.168.122.209 [52817.826763] [tempesta fw] exiting... Apr 26 06:44:27 192.168.122.209 [52817.943795] [tdb] Shutdown Tempesta DB Apr 26 06:44:27 192.168.122.209 [52818.154610] End test: tls.test_tls_handshake.TlsHandshakeTest.test_old_handshakes Apr 26 06:44:27 192.168.122.209 [52818.161795] Start test: tls.test_tls_handshake.TlsHandshakeTest.test_many_ciphers Apr 26 06:44:28 192.168.122.209 [52819.235278] [tdb] Start Tempesta DB Apr 26 06:44:28 192.168.122.209 [52819.377903] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:44:29 192.168.122.209 [52820.106864] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52820.106864] Maybe that's fine, but it's worth checking the [52820.106864] config - if there is no relations between the [52820.106864] names, then host name confusion attack is possible. Apr 26 06:44:29 192.168.122.209 [52820.237673] [tempesta fw] Configuration processing is completed. Apr 26 06:44:29 192.168.122.209 [52820.291402] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:44:29 192.168.122.209 [52820.323147] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:44:29 192.168.122.209 [52820.351440] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:44:29 192.168.122.209 [52820.389527] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:44:29 192.168.122.209 [52820.429561] [tempesta fw] Tempesta FW is ready Apr 26 06:44:30 192.168.122.209 [52820.629865] device enp1s0 entered promiscuous mode Apr 26 06:44:30 192.168.122.209 [52820.742057] device enp1s0 left promiscuous mode Apr 26 06:44:30 192.168.122.209 [52821.188714] [tdb] Close table 'client0.tdb' Apr 26 06:44:30 192.168.122.209 [52821.377245] [tdb] Close table 'sessions0.tdb' Apr 26 06:44:31 192.168.122.209 [52821.612692] [tdb] Close table 'filter0.tdb' Apr 26 06:44:31 192.168.122.209 [52821.613118] [tempesta fw] modules are stopped Apr 26 06:44:31 192.168.122.209 [52821.879785] [tempesta fw] exiting... Apr 26 06:44:31 192.168.122.209 [52821.999177] [tdb] Shutdown Tempesta DB Apr 26 06:44:31 192.168.122.209 [52822.220422] End test: tls.test_tls_handshake.TlsHandshakeTest.test_many_ciphers Apr 26 06:44:31 192.168.122.209 [52822.254064] Start test: tls.test_tls_handshake.TlsHandshakeTest.test_long_sni Apr 26 06:44:32 192.168.122.209 [52823.379115] [tdb] Start Tempesta DB Apr 26 06:44:33 192.168.122.209 [52823.512884] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:44:33 192.168.122.209 [52824.258920] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52824.258920] Maybe that's fine, but it's worth checking the [52824.258920] config - if there is no relations between the [52824.258920] names, then host name confusion attack is possible. Apr 26 06:44:33 192.168.122.209 [52824.381685] [tempesta fw] Configuration processing is completed. Apr 26 06:44:33 192.168.122.209 [52824.431572] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:44:33 192.168.122.209 [52824.458744] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:44:34 192.168.122.209 [52824.486299] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:44:34 192.168.122.209 [52824.533613] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:44:34 192.168.122.209 [52824.577554] [tempesta fw] Tempesta FW is ready Apr 26 06:44:34 192.168.122.209 [52824.704664] device enp1s0 entered promiscuous mode Apr 26 06:44:34 192.168.122.209 [52824.748411] [tempesta tls] Warning: [::ffff:127.0.0.1] ClientHello: bad extension size 1005 (remaining extensions size 1065) Apr 26 06:44:34 192.168.122.209 [52824.769879] device enp1s0 left promiscuous mode Apr 26 06:44:34 192.168.122.209 [52825.278690] [tdb] Close table 'client0.tdb' Apr 26 06:44:34 192.168.122.209 [52825.462743] [tdb] Close table 'sessions0.tdb' Apr 26 06:44:35 192.168.122.209 [52825.709237] [tdb] Close table 'filter0.tdb' Apr 26 06:44:35 192.168.122.209 [52825.709664] [tempesta fw] modules are stopped Apr 26 06:44:35 192.168.122.209 [52825.957036] [tempesta fw] exiting... Apr 26 06:44:35 192.168.122.209 [52826.061093] [tdb] Shutdown Tempesta DB Apr 26 06:44:35 192.168.122.209 [52826.301447] End test: tls.test_tls_handshake.TlsHandshakeTest.test_long_sni Apr 26 06:44:35 192.168.122.209 [52826.326183] Start test: tls.test_tls_handshake.TlsHandshakeTest.test_fuzzing Apr 26 06:44:36 192.168.122.209 [52827.327803] [tdb] Start Tempesta DB Apr 26 06:44:37 192.168.122.209 [52827.474149] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:44:37 192.168.122.209 [52828.178958] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52828.178958] Maybe that's fine, but it's worth checking the [52828.178958] config - if there is no relations between the [52828.178958] names, then host name confusion attack is possible. Apr 26 06:44:37 192.168.122.209 [52828.309749] [tempesta fw] Configuration processing is completed. Apr 26 06:44:37 192.168.122.209 [52828.364262] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:44:37 192.168.122.209 [52828.391256] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:44:37 192.168.122.209 [52828.427074] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:44:38 192.168.122.209 [52828.477710] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:44:38 192.168.122.209 [52828.525652] [tempesta fw] Tempesta FW is ready Apr 26 06:44:38 192.168.122.209 [52829.124568] [tdb] Close table 'client0.tdb' Apr 26 06:44:38 192.168.122.209 [52829.314789] [tdb] Close table 'sessions0.tdb' Apr 26 06:44:39 192.168.122.209 [52829.551392] [tdb] Close table 'filter0.tdb' Apr 26 06:44:39 192.168.122.209 [52829.551835] [tempesta fw] modules are stopped Apr 26 06:44:39 192.168.122.209 [52829.765617] [tempesta fw] exiting... Apr 26 06:44:39 192.168.122.209 [52829.899691] [tdb] Shutdown Tempesta DB Apr 26 06:44:39 192.168.122.209 [52830.103039] End test: tls.test_tls_handshake.TlsHandshakeTest.test_fuzzing Apr 26 06:44:39 192.168.122.209 [52830.116749] Start test: tls.test_tls_handshake.TlsHandshakeTest.test_empty_sni_default Apr 26 06:44:40 192.168.122.209 [52831.104611] [tdb] Start Tempesta DB Apr 26 06:44:40 192.168.122.209 [52831.252989] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:44:41 192.168.122.209 [52831.959397] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52831.959397] Maybe that's fine, but it's worth checking the [52831.959397] config - if there is no relations between the [52831.959397] names, then host name confusion attack is possible. Apr 26 06:44:41 192.168.122.209 [52832.081801] [tempesta fw] Configuration processing is completed. Apr 26 06:44:41 192.168.122.209 [52832.132178] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:44:41 192.168.122.209 [52832.159284] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:44:41 192.168.122.209 [52832.186638] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:44:41 192.168.122.209 [52832.229755] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:44:41 192.168.122.209 [52832.273700] [tempesta fw] Tempesta FW is ready Apr 26 06:44:41 192.168.122.209 [52832.388108] device enp1s0 entered promiscuous mode Apr 26 06:44:41 192.168.122.209 [52832.432111] [tempesta fw] Warning: client 127.0.0.1 requested missing server name, reject connection. Apr 26 06:44:41 192.168.122.209 [52832.454039] device enp1s0 left promiscuous mode Apr 26 06:44:42 192.168.122.209 [52832.862845] [tdb] Close table 'client0.tdb' Apr 26 06:44:42 192.168.122.209 [52833.039244] [tdb] Close table 'sessions0.tdb' Apr 26 06:44:42 192.168.122.209 [52833.259326] [tdb] Close table 'filter0.tdb' Apr 26 06:44:42 192.168.122.209 [52833.259753] [tempesta fw] modules are stopped Apr 26 06:44:43 192.168.122.209 [52833.470689] [tempesta fw] exiting... Apr 26 06:44:43 192.168.122.209 [52833.579665] [tdb] Shutdown Tempesta DB Apr 26 06:44:43 192.168.122.209 [52833.797801] End test: tls.test_tls_handshake.TlsHandshakeTest.test_empty_sni_default Apr 26 06:44:43 192.168.122.209 [52833.811127] Start test: tls.test_tls_handshake.TlsHandshakeTest.test_close_notify Apr 26 06:44:44 192.168.122.209 [52834.832060] [tdb] Start Tempesta DB Apr 26 06:44:44 192.168.122.209 [52834.968623] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:44:45 192.168.122.209 [52835.718554] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52835.718554] Maybe that's fine, but it's worth checking the [52835.718554] config - if there is no relations between the [52835.718554] names, then host name confusion attack is possible. Apr 26 06:44:45 192.168.122.209 [52835.833838] [tempesta fw] Configuration processing is completed. Apr 26 06:44:45 192.168.122.209 [52835.887243] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:44:45 192.168.122.209 [52835.916944] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:44:45 192.168.122.209 [52835.944950] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:44:45 192.168.122.209 [52835.993765] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:44:45 192.168.122.209 [52836.033699] [tempesta fw] Tempesta FW is ready Apr 26 06:44:45 192.168.122.209 [52836.151038] device enp1s0 entered promiscuous mode Apr 26 06:44:45 192.168.122.209 [52836.270082] device enp1s0 left promiscuous mode Apr 26 06:44:46 192.168.122.209 [52836.712937] [tdb] Close table 'client0.tdb' Apr 26 06:44:46 192.168.122.209 [52836.903812] [tdb] Close table 'sessions0.tdb' Apr 26 06:44:46 192.168.122.209 [52837.127111] [tdb] Close table 'filter0.tdb' Apr 26 06:44:46 192.168.122.209 [52837.127559] [tempesta fw] modules are stopped Apr 26 06:44:46 192.168.122.209 [52837.369324] [tempesta fw] exiting... Apr 26 06:44:47 192.168.122.209 [52837.482266] [tdb] Shutdown Tempesta DB Apr 26 06:44:47 192.168.122.209 [52837.695020] End test: tls.test_tls_handshake.TlsHandshakeTest.test_close_notify Apr 26 06:44:47 192.168.122.209 [52837.709702] Start test: tls.test_tls_handshake.TlsHandshakeTest.test_bad_sni Apr 26 06:44:48 192.168.122.209 [52838.785276] [tdb] Start Tempesta DB Apr 26 06:44:48 192.168.122.209 [52838.926151] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:44:49 192.168.122.209 [52839.751174] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52839.751174] Maybe that's fine, but it's worth checking the [52839.751174] config - if there is no relations between the [52839.751174] names, then host name confusion attack is possible. Apr 26 06:44:49 192.168.122.209 [52839.869868] [tempesta fw] Configuration processing is completed. Apr 26 06:44:49 192.168.122.209 [52839.920305] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:44:49 192.168.122.209 [52839.948220] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:44:49 192.168.122.209 [52839.976335] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:44:49 192.168.122.209 [52840.013794] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:44:49 192.168.122.209 [52840.061813] [tempesta fw] Tempesta FW is ready Apr 26 06:44:49 192.168.122.209 [52840.193856] device enp1s0 entered promiscuous mode Apr 26 06:44:49 192.168.122.209 [52840.256584] [tempesta fw] Warning: client 127.0.0.1 requested unknown server name 'badservername' in TLS SNI, reject connection. Apr 26 06:44:49 192.168.122.209 [52840.282050] device enp1s0 left promiscuous mode Apr 26 06:44:50 192.168.122.209 [52840.813062] [tdb] Close table 'client0.tdb' Apr 26 06:44:50 192.168.122.209 [52840.997299] [tdb] Close table 'sessions0.tdb' Apr 26 06:44:50 192.168.122.209 [52841.233766] [tdb] Close table 'filter0.tdb' Apr 26 06:44:50 192.168.122.209 [52841.234198] [tempesta fw] modules are stopped Apr 26 06:44:50 192.168.122.209 [52841.465766] [tempesta fw] exiting... Apr 26 06:44:51 192.168.122.209 [52841.578291] [tdb] Shutdown Tempesta DB Apr 26 06:44:51 192.168.122.209 [52841.782719] End test: tls.test_tls_handshake.TlsHandshakeTest.test_bad_sni Apr 26 06:44:51 192.168.122.209 [52841.793550] Start test: tls.test_tls_handshake.TlsHandshakeTest.test_bad_sign_algs Apr 26 06:44:52 192.168.122.209 [52842.871598] [tdb] Start Tempesta DB Apr 26 06:44:52 192.168.122.209 [52843.012123] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:44:53 192.168.122.209 [52843.767362] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52843.767362] Maybe that's fine, but it's worth checking the [52843.767362] config - if there is no relations between the [52843.767362] names, then host name confusion attack is possible. Apr 26 06:44:53 192.168.122.209 [52843.881948] [tempesta fw] Configuration processing is completed. Apr 26 06:44:53 192.168.122.209 [52843.932286] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:44:53 192.168.122.209 [52843.960172] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:44:53 192.168.122.209 [52843.988211] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:44:53 192.168.122.209 [52844.061908] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:44:53 192.168.122.209 [52844.105843] [tempesta fw] Tempesta FW is ready Apr 26 06:44:53 192.168.122.209 [52844.237157] device enp1s0 entered promiscuous mode Apr 26 06:44:53 192.168.122.209 [52844.291979] [tempesta tls] Warning: [::ffff:127.0.0.1] ClientHello: bad signature algorithm extension Apr 26 06:44:53 192.168.122.209 [52844.310098] device enp1s0 left promiscuous mode Apr 26 06:44:54 192.168.122.209 [52844.798913] [tdb] Close table 'client0.tdb' Apr 26 06:44:54 192.168.122.209 [52844.987539] [tdb] Close table 'sessions0.tdb' Apr 26 06:44:54 192.168.122.209 [52845.220836] [tdb] Close table 'filter0.tdb' Apr 26 06:44:54 192.168.122.209 [52845.221284] [tempesta fw] modules are stopped Apr 26 06:44:54 192.168.122.209 [52845.415836] [tempesta fw] exiting... Apr 26 06:44:55 192.168.122.209 [52845.527609] [tdb] Shutdown Tempesta DB Apr 26 06:44:55 192.168.122.209 [52845.721197] End test: tls.test_tls_handshake.TlsHandshakeTest.test_bad_sign_algs Apr 26 06:44:55 192.168.122.209 [52845.734717] Start test: tls.test_tls_handshake.TlsHandshakeTest.test_bad_renegotiation_info Apr 26 06:44:56 192.168.122.209 [52846.867823] [tdb] Start Tempesta DB Apr 26 06:44:56 192.168.122.209 [52847.002702] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:44:57 192.168.122.209 [52847.746693] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52847.746693] Maybe that's fine, but it's worth checking the [52847.746693] config - if there is no relations between the [52847.746693] names, then host name confusion attack is possible. Apr 26 06:44:57 192.168.122.209 [52847.865972] [tempesta fw] Configuration processing is completed. Apr 26 06:44:57 192.168.122.209 [52847.917057] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:44:57 192.168.122.209 [52847.946625] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:44:57 192.168.122.209 [52847.974183] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:44:57 192.168.122.209 [52848.013960] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:44:57 192.168.122.209 [52848.065892] [tempesta fw] Tempesta FW is ready Apr 26 06:44:57 192.168.122.209 [52848.196149] device enp1s0 entered promiscuous mode Apr 26 06:44:57 192.168.122.209 [52848.244677] [tempesta tls] Warning: [::ffff:127.0.0.1] ClientHello: bad renegotiation_info extension Apr 26 06:44:57 192.168.122.209 [52848.266275] device enp1s0 left promiscuous mode Apr 26 06:44:58 192.168.122.209 [52848.755115] [tdb] Close table 'client0.tdb' Apr 26 06:44:58 192.168.122.209 [52848.951805] [tdb] Close table 'sessions0.tdb' Apr 26 06:44:58 192.168.122.209 [52849.194286] [tdb] Close table 'filter0.tdb' Apr 26 06:44:58 192.168.122.209 [52849.194725] [tempesta fw] modules are stopped Apr 26 06:44:58 192.168.122.209 [52849.413208] [tempesta fw] exiting... Apr 26 06:44:59 192.168.122.209 [52849.513418] [tdb] Shutdown Tempesta DB Apr 26 06:44:59 192.168.122.209 [52849.734571] End test: tls.test_tls_handshake.TlsHandshakeTest.test_bad_renegotiation_info Apr 26 06:44:59 192.168.122.209 [52849.750537] Start test: tls.test_tls_handshake.TlsHandshakeTest.test_bad_elliptic_curves Apr 26 06:45:00 192.168.122.209 [52850.906075] [tdb] Start Tempesta DB Apr 26 06:45:00 192.168.122.209 [52851.049424] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:45:01 192.168.122.209 [52851.813428] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52851.813428] Maybe that's fine, but it's worth checking the [52851.813428] config - if there is no relations between the [52851.813428] names, then host name confusion attack is possible. Apr 26 06:45:01 192.168.122.209 [52851.926096] [tempesta fw] Configuration processing is completed. Apr 26 06:45:01 192.168.122.209 [52851.975416] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:45:01 192.168.122.209 [52852.002531] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:45:01 192.168.122.209 [52852.029952] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:45:01 192.168.122.209 [52852.098003] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:45:01 192.168.122.209 [52852.137945] [tempesta fw] Tempesta FW is ready Apr 26 06:45:01 192.168.122.209 [52852.264062] device enp1s0 entered promiscuous mode Apr 26 06:45:01 192.168.122.209 [52852.322211] [tempesta tls] Warning: [::ffff:127.0.0.1] None of the common ciphersuites is usable (e.g. no suitable certificate), like TLS-ECDHE-RSA-WITH-AES-256-GCM-SHA384 Apr 26 06:45:01 192.168.122.209 [52852.350285] device enp1s0 left promiscuous mode Apr 26 06:45:02 192.168.122.209 [52852.871847] [tdb] Close table 'client0.tdb' Apr 26 06:45:02 192.168.122.209 [52853.063865] [tdb] Close table 'sessions0.tdb' Apr 26 06:45:02 192.168.122.209 [52853.305603] [tdb] Close table 'filter0.tdb' Apr 26 06:45:02 192.168.122.209 [52853.306056] [tempesta fw] modules are stopped Apr 26 06:45:03 192.168.122.209 [52853.527567] [tempesta fw] exiting... Apr 26 06:45:03 192.168.122.209 [52853.632077] [tdb] Shutdown Tempesta DB Apr 26 06:45:03 192.168.122.209 [52853.832508] End test: tls.test_tls_handshake.TlsHandshakeTest.test_bad_elliptic_curves Apr 26 06:45:03 192.168.122.209 [52853.853329] Start test: tls.test_tls_handshake.TlsHandshakeTest.test_alert Apr 26 06:45:04 192.168.122.209 [52854.971620] [tdb] Start Tempesta DB Apr 26 06:45:04 192.168.122.209 [52855.108033] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:45:05 192.168.122.209 [52855.857925] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52855.857925] Maybe that's fine, but it's worth checking the [52855.857925] config - if there is no relations between the [52855.857925] names, then host name confusion attack is possible. Apr 26 06:45:05 192.168.122.209 [52855.982087] [tempesta fw] Configuration processing is completed. Apr 26 06:45:05 192.168.122.209 [52856.032603] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:45:05 192.168.122.209 [52856.062182] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:45:05 192.168.122.209 [52856.089534] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:45:05 192.168.122.209 [52856.146022] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:45:05 192.168.122.209 [52856.197986] [tempesta fw] Tempesta FW is ready Apr 26 06:45:05 192.168.122.209 [52856.315443] device enp1s0 entered promiscuous mode Apr 26 06:45:06 192.168.122.209 [52856.734744] device enp1s0 left promiscuous mode Apr 26 06:45:06 192.168.122.209 [52856.760721] device enp1s0 entered promiscuous mode Apr 26 06:45:06 192.168.122.209 [52857.175106] device enp1s0 left promiscuous mode Apr 26 06:45:06 192.168.122.209 [52857.197590] device enp1s0 entered promiscuous mode Apr 26 06:45:06 192.168.122.209 [52857.294320] device enp1s0 left promiscuous mode Apr 26 06:45:07 192.168.122.209 [52857.728240] [tdb] Close table 'client0.tdb' Apr 26 06:45:07 192.168.122.209 [52857.920295] [tdb] Close table 'sessions0.tdb' Apr 26 06:45:07 192.168.122.209 [52858.161889] [tdb] Close table 'filter0.tdb' Apr 26 06:45:07 192.168.122.209 [52858.162335] [tempesta fw] modules are stopped Apr 26 06:45:07 192.168.122.209 [52858.430079] [tempesta fw] exiting... Apr 26 06:45:08 192.168.122.209 [52858.540101] [tdb] Shutdown Tempesta DB Apr 26 06:45:08 192.168.122.209 [52858.740061] End test: tls.test_tls_handshake.TlsHandshakeTest.test_alert Apr 26 06:45:08 192.168.122.209 [52858.755198] Start test: tls.test_tls_handshake.TlsHandshakeTest.test_9byte_transfer Apr 26 06:45:09 192.168.122.209 [52859.776973] [tdb] Start Tempesta DB Apr 26 06:45:09 192.168.122.209 [52859.913225] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:45:10 192.168.122.209 [52860.646645] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52860.646645] Maybe that's fine, but it's worth checking the [52860.646645] config - if there is no relations between the [52860.646645] names, then host name confusion attack is possible. Apr 26 06:45:10 192.168.122.209 [52860.750162] [tempesta fw] Configuration processing is completed. Apr 26 06:45:10 192.168.122.209 [52860.804682] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:45:10 192.168.122.209 [52860.836226] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:45:10 192.168.122.209 [52860.866644] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:45:10 192.168.122.209 [52860.914126] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:45:10 192.168.122.209 [52860.970099] [tempesta fw] Tempesta FW is ready Apr 26 06:45:10 192.168.122.209 [52861.109207] device enp1s0 entered promiscuous mode Apr 26 06:45:10 192.168.122.209 [52861.218479] device enp1s0 left promiscuous mode Apr 26 06:45:11 192.168.122.209 [52861.672732] [tdb] Close table 'client0.tdb' Apr 26 06:45:11 192.168.122.209 [52861.862536] [tdb] Close table 'sessions0.tdb' Apr 26 06:45:11 192.168.122.209 [52862.112304] [tdb] Close table 'filter0.tdb' Apr 26 06:45:11 192.168.122.209 [52862.112731] [tempesta fw] modules are stopped Apr 26 06:45:11 192.168.122.209 [52862.366245] [tempesta fw] exiting... Apr 26 06:45:12 192.168.122.209 [52862.479134] [tdb] Shutdown Tempesta DB Apr 26 06:45:12 192.168.122.209 [52862.707085] End test: tls.test_tls_handshake.TlsHandshakeTest.test_9byte_transfer Apr 26 06:45:12 192.168.122.209 [52862.717286] Start test: tls.test_tls_handshake.TlsHandshakeTest.test_1byte_transfer Apr 26 06:45:13 192.168.122.209 [52863.744920] [tdb] Start Tempesta DB Apr 26 06:45:13 192.168.122.209 [52863.887726] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:45:14 192.168.122.209 [52864.686847] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52864.686847] Maybe that's fine, but it's worth checking the [52864.686847] config - if there is no relations between the [52864.686847] names, then host name confusion attack is possible. Apr 26 06:45:14 192.168.122.209 [52864.802212] [tempesta fw] Configuration processing is completed. Apr 26 06:45:14 192.168.122.209 [52864.854848] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:45:14 192.168.122.209 [52864.884003] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:45:14 192.168.122.209 [52864.911374] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:45:14 192.168.122.209 [52864.970160] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:45:14 192.168.122.209 [52865.022098] [tempesta fw] Tempesta FW is ready Apr 26 06:45:14 192.168.122.209 [52865.148343] device enp1s0 entered promiscuous mode Apr 26 06:45:14 192.168.122.209 [52865.258676] device enp1s0 left promiscuous mode Apr 26 06:45:15 192.168.122.209 [52865.696670] [tdb] Close table 'client0.tdb' Apr 26 06:45:15 192.168.122.209 [52865.892810] [tdb] Close table 'sessions0.tdb' Apr 26 06:45:15 192.168.122.209 [52866.131055] [tdb] Close table 'filter0.tdb' Apr 26 06:45:15 192.168.122.209 [52866.131494] [tempesta fw] modules are stopped Apr 26 06:45:15 192.168.122.209 [52866.343154] [tempesta fw] exiting... Apr 26 06:45:16 192.168.122.209 [52866.480718] [tdb] Shutdown Tempesta DB Apr 26 06:45:16 192.168.122.209 [52866.734874] End test: tls.test_tls_handshake.TlsHandshakeTest.test_1byte_transfer Apr 26 06:45:16 192.168.122.209 [52866.750952] Start test: tls.test_tls_handshake.TlsHandshakeTest.test_10byte_transfer Apr 26 06:45:17 192.168.122.209 [52867.841429] [tdb] Start Tempesta DB Apr 26 06:45:17 192.168.122.209 [52867.989278] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:45:18 192.168.122.209 [52868.751530] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52868.751530] Maybe that's fine, but it's worth checking the [52868.751530] config - if there is no relations between the [52868.751530] names, then host name confusion attack is possible. Apr 26 06:45:18 192.168.122.209 [52868.870250] [tempesta fw] Configuration processing is completed. Apr 26 06:45:18 192.168.122.209 [52868.923421] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:45:18 192.168.122.209 [52868.954720] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:45:18 192.168.122.209 [52868.984522] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:45:18 192.168.122.209 [52869.018144] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:45:18 192.168.122.209 [52869.058190] [tempesta fw] Tempesta FW is ready Apr 26 06:45:18 192.168.122.209 [52869.198274] device enp1s0 entered promiscuous mode Apr 26 06:45:18 192.168.122.209 [52869.322516] device enp1s0 left promiscuous mode Apr 26 06:45:19 192.168.122.209 [52869.823601] [tdb] Close table 'client0.tdb' Apr 26 06:45:19 192.168.122.209 [52870.027304] [tdb] Close table 'sessions0.tdb' Apr 26 06:45:19 192.168.122.209 [52870.257662] [tdb] Close table 'filter0.tdb' Apr 26 06:45:19 192.168.122.209 [52870.258126] [tempesta fw] modules are stopped Apr 26 06:45:20 192.168.122.209 [52870.489816] [tempesta fw] exiting... Apr 26 06:45:20 192.168.122.209 [52870.616088] [tdb] Shutdown Tempesta DB Apr 26 06:45:20 192.168.122.209 [52870.866798] End test: tls.test_tls_handshake.TlsHandshakeTest.test_10byte_transfer Apr 26 06:45:20 192.168.122.209 [52870.877689] Start test: tls.test_tls_handshake.TlsCertReconfig.test Apr 26 06:45:21 192.168.122.209 [52871.950312] [tdb] Start Tempesta DB Apr 26 06:45:21 192.168.122.209 [52872.097290] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:45:22 192.168.122.209 [52872.863169] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52872.863169] Maybe that's fine, but it's worth checking the [52872.863169] config - if there is no relations between the [52872.863169] names, then host name confusion attack is possible. Apr 26 06:45:22 192.168.122.209 [52872.982301] [tempesta fw] Configuration processing is completed. Apr 26 06:45:22 192.168.122.209 [52873.033967] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:45:22 192.168.122.209 [52873.063642] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:45:22 192.168.122.209 [52873.092794] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:45:22 192.168.122.209 [52873.154254] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:45:22 192.168.122.209 [52873.198207] [tempesta fw] Tempesta FW is ready Apr 26 06:45:22 192.168.122.209 [52873.328852] device enp1s0 entered promiscuous mode Apr 26 06:45:22 192.168.122.209 [52873.450704] device enp1s0 left promiscuous mode Apr 26 06:45:23 192.168.122.209 [52873.934673] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 06:45:23 192.168.122.209 [52873.983525] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52873.983525] Maybe that's fine, but it's worth checking the [52873.983525] config - if there is no relations between the [52873.983525] names, then host name confusion attack is possible. Apr 26 06:45:23 192.168.122.209 [52874.126389] [tempesta fw] Configuration processing is completed. Apr 26 06:45:23 192.168.122.209 [52874.390745] [tempesta fw] Tempesta FW is ready Apr 26 06:45:23 192.168.122.209 [52874.443951] device enp1s0 entered promiscuous mode Apr 26 06:45:24 192.168.122.209 [52874.546495] device enp1s0 left promiscuous mode Apr 26 06:45:24 192.168.122.209 [52875.009036] [tdb] Close table 'client0.tdb' Apr 26 06:45:24 192.168.122.209 [52875.201163] [tdb] Close table 'sessions0.tdb' Apr 26 06:45:24 192.168.122.209 [52875.454409] [tdb] Close table 'filter0.tdb' Apr 26 06:45:24 192.168.122.209 [52875.454866] [tempesta fw] modules are stopped Apr 26 06:45:25 192.168.122.209 [52875.750624] [tempesta fw] exiting... Apr 26 06:45:25 192.168.122.209 [52875.861294] [tdb] Shutdown Tempesta DB Apr 26 06:45:25 192.168.122.209 [52876.086930] End test: tls.test_tls_handshake.TlsCertReconfig.test Apr 26 06:45:25 192.168.122.209 [52876.096632] Start test: tls.test_tls_cert.TlsSniWithHttpTableMultiH2.test_alternating_access Apr 26 06:45:26 192.168.122.209 [52877.179074] [tdb] Start Tempesta DB Apr 26 06:45:26 192.168.122.209 [52877.314308] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:45:27 192.168.122.209 [52878.360479] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [52878.360479] Maybe that's fine, but it's worth checking the [52878.360479] config - if there is no relations between the [52878.360479] names, then host name confusion attack is possible. Apr 26 06:45:27 192.168.122.209 [52878.442429] [tempesta fw] Configuration processing is completed. Apr 26 06:45:28 192.168.122.209 [52878.496853] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:45:28 192.168.122.209 [52878.525650] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:45:28 192.168.122.209 [52878.555477] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:45:28 192.168.122.209 [52878.614209] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:45:28 192.168.122.209 [52878.670219] [tempesta fw] Tempesta FW is ready Apr 26 06:45:28 192.168.122.209 [52878.905844] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.2 ('example.com' vs 'localhost-vhost') Apr 26 06:45:28 192.168.122.209 [52878.907005] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 06:45:28 192.168.122.209 [52879.410396] [tdb] Close table 'client0.tdb' Apr 26 06:45:29 192.168.122.209 [52879.597180] [tdb] Close table 'sessions0.tdb' Apr 26 06:45:29 192.168.122.209 [52879.843373] [tdb] Close table 'filter0.tdb' Apr 26 06:45:29 192.168.122.209 [52879.843817] [tempesta fw] modules are stopped Apr 26 06:45:29 192.168.122.209 [52880.063084] [tempesta fw] exiting... Apr 26 06:45:29 192.168.122.209 [52880.205223] [tdb] Shutdown Tempesta DB Apr 26 06:45:29 192.168.122.209 [52880.416967] End test: tls.test_tls_cert.TlsSniWithHttpTableMultiH2.test_alternating_access Apr 26 06:45:29 192.168.122.209 [52880.426273] Start test: tls.test_tls_cert.TlsSniWithHttpTableMulti.test_alternating_access Apr 26 06:45:30 192.168.122.209 [52881.451049] [tdb] Start Tempesta DB Apr 26 06:45:31 192.168.122.209 [52881.585400] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:45:32 192.168.122.209 [52882.612630] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [52882.612630] Maybe that's fine, but it's worth checking the [52882.612630] config - if there is no relations between the [52882.612630] names, then host name confusion attack is possible. Apr 26 06:45:32 192.168.122.209 [52882.702450] [tempesta fw] Configuration processing is completed. Apr 26 06:45:32 192.168.122.209 [52882.759807] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:45:32 192.168.122.209 [52882.788868] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:45:32 192.168.122.209 [52882.817976] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:45:32 192.168.122.209 [52882.882417] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:45:32 192.168.122.209 [52882.922341] [tempesta fw] Tempesta FW is ready Apr 26 06:45:32 192.168.122.209 [52883.091080] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.2 ('example.com' vs 'localhost-vhost') Apr 26 06:45:32 192.168.122.209 [52883.092468] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 06:45:33 192.168.122.209 [52883.586934] [tdb] Close table 'client0.tdb' Apr 26 06:45:33 192.168.122.209 [52883.771702] [tdb] Close table 'sessions0.tdb' Apr 26 06:45:33 192.168.122.209 [52884.041111] [tdb] Close table 'filter0.tdb' Apr 26 06:45:33 192.168.122.209 [52884.041540] [tempesta fw] modules are stopped Apr 26 06:45:33 192.168.122.209 [52884.276860] [tempesta fw] exiting... Apr 26 06:45:33 192.168.122.209 [52884.429566] [tdb] Shutdown Tempesta DB Apr 26 06:45:34 192.168.122.209 [52884.633320] End test: tls.test_tls_cert.TlsSniWithHttpTableMulti.test_alternating_access Apr 26 06:45:34 192.168.122.209 [52884.659445] Start test: tls.test_tls_cert.TlsSniWithHttpTable.test_with_san Apr 26 06:45:35 192.168.122.209 [52885.673586] [tdb] Start Tempesta DB Apr 26 06:45:35 192.168.122.209 [52885.816610] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:45:36 192.168.122.209 [52887.188078] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [52887.188078] Maybe that's fine, but it's worth checking the [52887.188078] config - if there is no relations between the [52887.188078] names, then host name confusion attack is possible. Apr 26 06:45:36 192.168.122.209 [52887.224024] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [52887.224024] Maybe that's fine, but it's worth checking the [52887.224024] config - if there is no relations between the [52887.224024] names, then host name confusion attack is possible. Apr 26 06:45:36 192.168.122.209 [52887.334481] [tempesta fw] Configuration processing is completed. Apr 26 06:45:36 192.168.122.209 [52887.385943] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:45:36 192.168.122.209 [52887.413897] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:45:36 192.168.122.209 [52887.441999] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:45:37 192.168.122.209 [52887.550442] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:45:37 192.168.122.209 [52887.590397] [tempesta fw] Tempesta FW is ready Apr 26 06:45:37 192.168.122.209 [52887.746759] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.2 ('tempesta-tech.com' vs 'localhost-vhost') Apr 26 06:45:37 192.168.122.209 [52887.747971] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 06:45:37 192.168.122.209 [52888.405590] [tdb] Close table 'client0.tdb' Apr 26 06:45:38 192.168.122.209 [52888.595359] [tdb] Close table 'sessions0.tdb' Apr 26 06:45:38 192.168.122.209 [52888.821018] [tdb] Close table 'filter0.tdb' Apr 26 06:45:38 192.168.122.209 [52888.821454] [tempesta fw] modules are stopped Apr 26 06:45:38 192.168.122.209 [52889.180581] [tempesta fw] exiting... Apr 26 06:45:38 192.168.122.209 [52889.326479] [tdb] Shutdown Tempesta DB Apr 26 06:45:39 192.168.122.209 [52889.568653] End test: tls.test_tls_cert.TlsSniWithHttpTable.test_with_san Apr 26 06:45:39 192.168.122.209 [52889.592041] Start test: tls.test_tls_cert.TlsSniWithHttpTable.test_with_common_name Apr 26 06:45:40 192.168.122.209 [52890.653016] [tdb] Start Tempesta DB Apr 26 06:45:40 192.168.122.209 [52890.798287] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:45:41 192.168.122.209 [52892.136543] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [52892.136543] Maybe that's fine, but it's worth checking the [52892.136543] config - if there is no relations between the [52892.136543] names, then host name confusion attack is possible. Apr 26 06:45:41 192.168.122.209 [52892.164686] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [52892.164686] Maybe that's fine, but it's worth checking the [52892.164686] config - if there is no relations between the [52892.164686] names, then host name confusion attack is possible. Apr 26 06:45:41 192.168.122.209 [52892.262570] [tempesta fw] Configuration processing is completed. Apr 26 06:45:41 192.168.122.209 [52892.319981] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:45:41 192.168.122.209 [52892.360697] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:45:41 192.168.122.209 [52892.391239] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:45:42 192.168.122.209 [52892.494550] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:45:42 192.168.122.209 [52892.534451] [tempesta fw] Tempesta FW is ready Apr 26 06:45:42 192.168.122.209 [52892.702797] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.2 ('tempesta-tech.com' vs 'localhost-vhost') Apr 26 06:45:42 192.168.122.209 [52892.704561] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 06:45:42 192.168.122.209 [52893.367706] [tdb] Close table 'client0.tdb' Apr 26 06:45:43 192.168.122.209 [52893.557644] [tdb] Close table 'sessions0.tdb' Apr 26 06:45:43 192.168.122.209 [52893.790187] [tdb] Close table 'filter0.tdb' Apr 26 06:45:43 192.168.122.209 [52893.790635] [tempesta fw] modules are stopped Apr 26 06:45:43 192.168.122.209 [52894.070376] [tempesta fw] exiting... Apr 26 06:45:43 192.168.122.209 [52894.208000] [tdb] Shutdown Tempesta DB Apr 26 06:45:43 192.168.122.209 [52894.425615] End test: tls.test_tls_cert.TlsSniWithHttpTable.test_with_common_name Apr 26 06:45:43 192.168.122.209 [52894.437737] Start test: tls.test_tls_cert.TlsSniWithHttpTable.test_with_any_host Apr 26 06:45:44 192.168.122.209 [52895.429044] [tdb] Start Tempesta DB Apr 26 06:45:45 192.168.122.209 [52895.580357] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:45:46 192.168.122.209 [52896.988657] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [52896.988657] Maybe that's fine, but it's worth checking the [52896.988657] config - if there is no relations between the [52896.988657] names, then host name confusion attack is possible. Apr 26 06:45:46 192.168.122.209 [52897.015856] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [52897.015856] Maybe that's fine, but it's worth checking the [52897.015856] config - if there is no relations between the [52897.015856] names, then host name confusion attack is possible. Apr 26 06:45:46 192.168.122.209 [52897.110633] [tempesta fw] Configuration processing is completed. Apr 26 06:45:46 192.168.122.209 [52897.167260] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:45:46 192.168.122.209 [52897.198252] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:45:46 192.168.122.209 [52897.228909] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:45:46 192.168.122.209 [52897.366580] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:45:46 192.168.122.209 [52897.414524] [tempesta fw] Tempesta FW is ready Apr 26 06:45:47 192.168.122.209 [52897.578191] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.2 ('tempesta-tech.com' vs 'default-vhost') Apr 26 06:45:47 192.168.122.209 [52897.579820] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 06:45:47 192.168.122.209 [52898.180324] [tdb] Close table 'client0.tdb' Apr 26 06:45:47 192.168.122.209 [52898.378270] [tdb] Close table 'sessions0.tdb' Apr 26 06:45:48 192.168.122.209 [52898.609222] [tdb] Close table 'filter0.tdb' Apr 26 06:45:48 192.168.122.209 [52898.609664] [tempesta fw] modules are stopped Apr 26 06:45:48 192.168.122.209 [52898.878685] [tempesta fw] exiting... Apr 26 06:45:48 192.168.122.209 [52898.989051] [tdb] Shutdown Tempesta DB Apr 26 06:45:48 192.168.122.209 [52899.209240] End test: tls.test_tls_cert.TlsSniWithHttpTable.test_with_any_host Apr 26 06:45:48 192.168.122.209 [52899.221278] Start test: tls.test_tls_cert.TlsSniWithHttpTable.test_valid Apr 26 06:45:49 192.168.122.209 [52900.308369] [tdb] Start Tempesta DB Apr 26 06:45:49 192.168.122.209 [52900.467086] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:45:51 192.168.122.209 [52901.816853] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [52901.816853] Maybe that's fine, but it's worth checking the [52901.816853] config - if there is no relations between the [52901.816853] names, then host name confusion attack is possible. Apr 26 06:45:51 192.168.122.209 [52901.848361] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [52901.848361] Maybe that's fine, but it's worth checking the [52901.848361] config - if there is no relations between the [52901.848361] names, then host name confusion attack is possible. Apr 26 06:45:51 192.168.122.209 [52901.970579] [tempesta fw] Configuration processing is completed. Apr 26 06:45:51 192.168.122.209 [52902.021699] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:45:51 192.168.122.209 [52902.051714] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:45:51 192.168.122.209 [52902.079989] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:45:51 192.168.122.209 [52902.186647] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:45:51 192.168.122.209 [52902.234589] [tempesta fw] Tempesta FW is ready Apr 26 06:45:52 192.168.122.209 [52903.156174] [tdb] Close table 'client0.tdb' Apr 26 06:45:52 192.168.122.209 [52903.339442] [tdb] Close table 'sessions0.tdb' Apr 26 06:45:53 192.168.122.209 [52903.557516] [tdb] Close table 'filter0.tdb' Apr 26 06:45:53 192.168.122.209 [52903.557956] [tempesta fw] modules are stopped Apr 26 06:45:53 192.168.122.209 [52903.896540] [tempesta fw] exiting... Apr 26 06:45:53 192.168.122.209 [52904.014135] [tdb] Shutdown Tempesta DB Apr 26 06:45:53 192.168.122.209 [52904.265960] End test: tls.test_tls_cert.TlsSniWithHttpTable.test_valid Apr 26 06:45:53 192.168.122.209 [52904.280185] Start test: tls.test_tls_cert.TlsCertSelectBySanwitMultipleSections.test Apr 26 06:45:54 192.168.122.209 [52905.359688] [tdb] Start Tempesta DB Apr 26 06:45:55 192.168.122.209 [52905.495037] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:45:55 192.168.122.209 [52906.250071] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [52906.250071] Maybe that's fine, but it's worth checking the [52906.250071] config - if there is no relations between the [52906.250071] names, then host name confusion attack is possible. Apr 26 06:45:55 192.168.122.209 [52906.280058] [tempesta fw] Warning: Vhost private.example.com doesn't have certificate with matching SAN/CN. [52906.280058] Maybe that's fine, but it's worth checking the [52906.280058] config - if there is no relations between the [52906.280058] names, then host name confusion attack is possible. Apr 26 06:45:55 192.168.122.209 [52906.318945] [tempesta fw] Configuration processing is completed. Apr 26 06:45:55 192.168.122.209 [52906.388376] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:45:55 192.168.122.209 [52906.423589] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:45:55 192.168.122.209 [52906.462995] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:45:56 192.168.122.209 [52906.502629] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:45:56 192.168.122.209 [52906.542629] [tempesta fw] Tempesta FW is ready Apr 26 06:45:56 192.168.122.209 [52906.665925] device enp1s0 entered promiscuous mode Apr 26 06:45:56 192.168.122.209 [52906.742432] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.1 ('private.example.com' vs 'default') Apr 26 06:45:56 192.168.122.209 [52906.745084] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.1 Apr 26 06:45:56 192.168.122.209 [52906.766967] device enp1s0 left promiscuous mode Apr 26 06:45:56 192.168.122.209 [52906.788471] device enp1s0 entered promiscuous mode Apr 26 06:45:56 192.168.122.209 [52906.867775] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.1 ('private.example.com' vs 'default') Apr 26 06:45:56 192.168.122.209 [52906.871201] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.1 Apr 26 06:45:56 192.168.122.209 [52906.894971] device enp1s0 left promiscuous mode Apr 26 06:45:56 192.168.122.209 [52906.924967] device enp1s0 entered promiscuous mode Apr 26 06:45:56 192.168.122.209 [52907.005215] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.1 ('example.com' vs 'default') Apr 26 06:45:56 192.168.122.209 [52907.006235] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.1 Apr 26 06:45:56 192.168.122.209 [52907.022915] device enp1s0 left promiscuous mode Apr 26 06:45:57 192.168.122.209 [52907.480114] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 06:45:57 192.168.122.209 [52907.556686] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [52907.556686] Maybe that's fine, but it's worth checking the [52907.556686] config - if there is no relations between the [52907.556686] names, then host name confusion attack is possible. Apr 26 06:45:57 192.168.122.209 [52907.614668] [tempesta fw] Configuration processing is completed. Apr 26 06:45:57 192.168.122.209 [52907.934715] [tempesta fw] Tempesta FW is ready Apr 26 06:45:57 192.168.122.209 [52907.984768] device enp1s0 entered promiscuous mode Apr 26 06:45:57 192.168.122.209 [52908.073875] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.1 ('example.com' vs 'default') Apr 26 06:45:57 192.168.122.209 [52908.077190] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.1 Apr 26 06:45:57 192.168.122.209 [52908.103071] device enp1s0 left promiscuous mode Apr 26 06:45:57 192.168.122.209 [52908.129938] device enp1s0 entered promiscuous mode Apr 26 06:45:57 192.168.122.209 [52908.215439] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.1 ('example.com' vs 'default') Apr 26 06:45:57 192.168.122.209 [52908.218618] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.1 Apr 26 06:45:57 192.168.122.209 [52908.234905] device enp1s0 left promiscuous mode Apr 26 06:45:57 192.168.122.209 [52908.253794] device enp1s0 entered promiscuous mode Apr 26 06:45:57 192.168.122.209 [52908.340960] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.1 ('example.com' vs 'default') Apr 26 06:45:57 192.168.122.209 [52908.343706] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.1 Apr 26 06:45:57 192.168.122.209 [52908.362925] device enp1s0 left promiscuous mode Apr 26 06:45:58 192.168.122.209 [52908.759940] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 06:45:58 192.168.122.209 [52908.820595] [tempesta fw] Warning: Vhost private.example.com doesn't have certificate with matching SAN/CN. [52908.820595] Maybe that's fine, but it's worth checking the [52908.820595] config - if there is no relations between the [52908.820595] names, then host name confusion attack is possible. Apr 26 06:45:58 192.168.122.209 [52908.882744] [tempesta fw] Configuration processing is completed. Apr 26 06:45:58 192.168.122.209 [52909.142729] [tempesta fw] Tempesta FW is ready Apr 26 06:45:58 192.168.122.209 [52909.192800] device enp1s0 entered promiscuous mode Apr 26 06:45:58 192.168.122.209 [52909.282734] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.1 ('private.example.com' vs 'default') Apr 26 06:45:58 192.168.122.209 [52909.286103] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.1 Apr 26 06:45:58 192.168.122.209 [52909.307075] device enp1s0 left promiscuous mode Apr 26 06:45:58 192.168.122.209 [52909.328767] device enp1s0 entered promiscuous mode Apr 26 06:45:58 192.168.122.209 [52909.414588] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.1 ('private.example.com' vs 'default') Apr 26 06:45:58 192.168.122.209 [52909.416496] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.1 Apr 26 06:45:58 192.168.122.209 [52909.438983] device enp1s0 left promiscuous mode Apr 26 06:45:58 192.168.122.209 [52909.460904] device enp1s0 entered promiscuous mode Apr 26 06:45:59 192.168.122.209 [52909.508091] [tempesta fw] Warning: client 127.0.0.1 requested unknown server name 'public.example.com' in TLS SNI, reject connection. Apr 26 06:45:59 192.168.122.209 [52909.539199] device enp1s0 left promiscuous mode Apr 26 06:45:59 192.168.122.209 [52910.019301] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 06:45:59 192.168.122.209 [52910.092708] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [52910.092708] Maybe that's fine, but it's worth checking the [52910.092708] config - if there is no relations between the [52910.092708] names, then host name confusion attack is possible. Apr 26 06:45:59 192.168.122.209 [52910.120124] [tempesta fw] Warning: Vhost private.example.com doesn't have certificate with matching SAN/CN. [52910.120124] Maybe that's fine, but it's worth checking the [52910.120124] config - if there is no relations between the [52910.120124] names, then host name confusion attack is possible. Apr 26 06:45:59 192.168.122.209 [52910.171107] [tempesta fw] Configuration processing is completed. Apr 26 06:45:59 192.168.122.209 [52910.442962] [tempesta fw] Tempesta FW is ready Apr 26 06:46:00 192.168.122.209 [52910.492125] device enp1s0 entered promiscuous mode Apr 26 06:46:00 192.168.122.209 [52910.579771] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.1 ('private.example.com' vs 'default') Apr 26 06:46:00 192.168.122.209 [52910.583195] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.1 Apr 26 06:46:00 192.168.122.209 [52910.615236] device enp1s0 left promiscuous mode Apr 26 06:46:00 192.168.122.209 [52910.633364] device enp1s0 entered promiscuous mode Apr 26 06:46:00 192.168.122.209 [52910.721554] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.1 ('private.example.com' vs 'default') Apr 26 06:46:00 192.168.122.209 [52910.723498] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.1 Apr 26 06:46:00 192.168.122.209 [52910.755130] device enp1s0 left promiscuous mode Apr 26 06:46:00 192.168.122.209 [52910.777242] device enp1s0 entered promiscuous mode Apr 26 06:46:00 192.168.122.209 [52910.864469] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.1 ('example.com' vs 'default') Apr 26 06:46:00 192.168.122.209 [52910.867702] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.1 Apr 26 06:46:00 192.168.122.209 [52910.891020] device enp1s0 left promiscuous mode Apr 26 06:46:00 192.168.122.209 [52911.375822] [tdb] Close table 'client0.tdb' Apr 26 06:46:01 192.168.122.209 [52911.592389] [tdb] Close table 'sessions0.tdb' Apr 26 06:46:01 192.168.122.209 [52911.834918] [tdb] Close table 'filter0.tdb' Apr 26 06:46:01 192.168.122.209 [52911.835361] [tempesta fw] modules are stopped Apr 26 06:46:01 192.168.122.209 [52912.085331] [tempesta fw] exiting... Apr 26 06:46:01 192.168.122.209 [52912.224770] [tdb] Shutdown Tempesta DB Apr 26 06:46:01 192.168.122.209 [52912.446908] End test: tls.test_tls_cert.TlsCertSelectBySanwitMultipleSections.test Apr 26 06:46:01 192.168.122.209 [52912.470366] Start test: tls.test_tls_cert.TlsCertSelectBySan.test_various_san_and_sni_not_matched Apr 26 06:46:03 192.168.122.209 [52913.568651] [tdb] Start Tempesta DB Apr 26 06:46:03 192.168.122.209 [52913.723024] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:46:03 192.168.122.209 [52914.352811] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [52914.352811] Maybe that's fine, but it's worth checking the [52914.352811] config - if there is no relations between the [52914.352811] names, then host name confusion attack is possible. Apr 26 06:46:03 192.168.122.209 [52914.410771] [tempesta fw] Configuration processing is completed. Apr 26 06:46:03 192.168.122.209 [52914.463696] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:46:04 192.168.122.209 [52914.494302] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:46:04 192.168.122.209 [52914.522190] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:46:04 192.168.122.209 [52914.574710] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:46:04 192.168.122.209 [52914.622728] [tempesta fw] Tempesta FW is ready Apr 26 06:46:04 192.168.122.209 [52915.175682] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 06:46:04 192.168.122.209 [52915.248667] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [52915.248667] Maybe that's fine, but it's worth checking the [52915.248667] config - if there is no relations between the [52915.248667] names, then host name confusion attack is possible. Apr 26 06:46:04 192.168.122.209 [52915.318748] [tempesta fw] Configuration processing is completed. Apr 26 06:46:05 192.168.122.209 [52915.562841] [tempesta fw] Tempesta FW is ready Apr 26 06:46:05 192.168.122.209 [52915.609506] device enp1s0 entered promiscuous mode Apr 26 06:46:05 192.168.122.209 [52915.652521] [tempesta fw] Warning: client 127.0.0.1 requested unknown server name 'a.b.example.com' in TLS SNI, reject connection. Apr 26 06:46:05 192.168.122.209 [52915.671086] device enp1s0 left promiscuous mode Apr 26 06:46:05 192.168.122.209 [52916.090229] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 06:46:05 192.168.122.209 [52916.156642] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [52916.156642] Maybe that's fine, but it's worth checking the [52916.156642] config - if there is no relations between the [52916.156642] names, then host name confusion attack is possible. Apr 26 06:46:05 192.168.122.209 [52916.214788] [tempesta fw] Configuration processing is completed. Apr 26 06:46:05 192.168.122.209 [52916.442848] [tempesta fw] Tempesta FW is ready Apr 26 06:46:06 192.168.122.209 [52916.494901] device enp1s0 entered promiscuous mode Apr 26 06:46:06 192.168.122.209 [52916.544685] [tempesta fw] Warning: client 127.0.0.1 requested unknown server name 'www.example.com' in TLS SNI, reject connection. Apr 26 06:46:06 192.168.122.209 [52916.563005] device enp1s0 left promiscuous mode Apr 26 06:46:06 192.168.122.209 [52916.987931] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 06:46:06 192.168.122.209 [52917.061083] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [52917.061083] Maybe that's fine, but it's worth checking the [52917.061083] config - if there is no relations between the [52917.061083] names, then host name confusion attack is possible. Apr 26 06:46:06 192.168.122.209 [52917.122811] [tempesta fw] Configuration processing is completed. Apr 26 06:46:06 192.168.122.209 [52917.362839] [tempesta fw] Tempesta FW is ready Apr 26 06:46:06 192.168.122.209 [52917.421752] device enp1s0 entered promiscuous mode Apr 26 06:46:07 192.168.122.209 [52917.473458] [tempesta fw] Warning: client 127.0.0.1 requested unknown server name 'b.example.com' in TLS SNI, reject connection. Apr 26 06:46:07 192.168.122.209 [52917.504366] device enp1s0 left promiscuous mode Apr 26 06:46:07 192.168.122.209 [52917.941050] [tdb] Close table 'client0.tdb' Apr 26 06:46:07 192.168.122.209 [52918.130892] [tdb] Close table 'sessions0.tdb' Apr 26 06:46:07 192.168.122.209 [52918.352920] [tdb] Close table 'filter0.tdb' Apr 26 06:46:07 192.168.122.209 [52918.353360] [tempesta fw] modules are stopped Apr 26 06:46:08 192.168.122.209 [52918.520521] [tempesta fw] exiting... Apr 26 06:46:08 192.168.122.209 [52918.639499] [tdb] Shutdown Tempesta DB Apr 26 06:46:08 192.168.122.209 [52918.861216] End test: tls.test_tls_cert.TlsCertSelectBySan.test_various_san_and_sni_not_matched Apr 26 06:46:08 192.168.122.209 [52918.889193] Start test: tls.test_tls_cert.TlsCertSelectBySan.test_various_san_and_sni_matched Apr 26 06:46:09 192.168.122.209 [52919.976995] [tdb] Start Tempesta DB Apr 26 06:46:09 192.168.122.209 [52920.113780] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:46:10 192.168.122.209 [52920.756853] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [52920.756853] Maybe that's fine, but it's worth checking the [52920.756853] config - if there is no relations between the [52920.756853] names, then host name confusion attack is possible. Apr 26 06:46:10 192.168.122.209 [52920.811233] [tempesta fw] Configuration processing is completed. Apr 26 06:46:10 192.168.122.209 [52920.864561] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:46:10 192.168.122.209 [52920.894610] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:46:10 192.168.122.209 [52920.923814] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:46:10 192.168.122.209 [52920.970861] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:46:10 192.168.122.209 [52921.010824] [tempesta fw] Tempesta FW is ready Apr 26 06:46:11 192.168.122.209 [52921.545274] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 06:46:11 192.168.122.209 [52921.624920] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [52921.624920] Maybe that's fine, but it's worth checking the [52921.624920] config - if there is no relations between the [52921.624920] names, then host name confusion attack is possible. Apr 26 06:46:11 192.168.122.209 [52921.678882] [tempesta fw] Configuration processing is completed. Apr 26 06:46:11 192.168.122.209 [52921.934905] [tempesta fw] Tempesta FW is ready Apr 26 06:46:11 192.168.122.209 [52921.992361] device enp1s0 entered promiscuous mode Apr 26 06:46:11 192.168.122.209 [52922.065950] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.1 ('example.com' vs 'default') Apr 26 06:46:11 192.168.122.209 [52922.069207] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.1 Apr 26 06:46:11 192.168.122.209 [52922.091132] device enp1s0 left promiscuous mode Apr 26 06:46:11 192.168.122.209 [52922.462166] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 06:46:12 192.168.122.209 [52922.536728] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [52922.536728] Maybe that's fine, but it's worth checking the [52922.536728] config - if there is no relations between the [52922.536728] names, then host name confusion attack is possible. Apr 26 06:46:12 192.168.122.209 [52922.579246] [tempesta fw] Configuration processing is completed. Apr 26 06:46:12 192.168.122.209 [52922.866930] [tempesta fw] Tempesta FW is ready Apr 26 06:46:12 192.168.122.209 [52922.917332] device enp1s0 entered promiscuous mode Apr 26 06:46:12 192.168.122.209 [52922.998416] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.1 ('example.com' vs 'default') Apr 26 06:46:12 192.168.122.209 [52923.001691] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.1 Apr 26 06:46:12 192.168.122.209 [52923.023463] device enp1s0 left promiscuous mode Apr 26 06:46:12 192.168.122.209 [52923.431582] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 06:46:13 192.168.122.209 [52923.497100] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [52923.497100] Maybe that's fine, but it's worth checking the [52923.497100] config - if there is no relations between the [52923.497100] names, then host name confusion attack is possible. Apr 26 06:46:13 192.168.122.209 [52923.554937] [tempesta fw] Configuration processing is completed. Apr 26 06:46:13 192.168.122.209 [52923.782925] [tempesta fw] Tempesta FW is ready Apr 26 06:46:13 192.168.122.209 [52923.832069] device enp1s0 entered promiscuous mode Apr 26 06:46:13 192.168.122.209 [52923.905715] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.1 ('example.com' vs 'default') Apr 26 06:46:13 192.168.122.209 [52923.906828] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.1 Apr 26 06:46:13 192.168.122.209 [52923.923092] device enp1s0 left promiscuous mode Apr 26 06:46:13 192.168.122.209 [52924.329223] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 06:46:13 192.168.122.209 [52924.412922] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [52924.412922] Maybe that's fine, but it's worth checking the [52924.412922] config - if there is no relations between the [52924.412922] names, then host name confusion attack is possible. Apr 26 06:46:14 192.168.122.209 [52924.478926] [tempesta fw] Configuration processing is completed. Apr 26 06:46:14 192.168.122.209 [52924.702936] [tempesta fw] Tempesta FW is ready Apr 26 06:46:14 192.168.122.209 [52924.749346] device enp1s0 entered promiscuous mode Apr 26 06:46:14 192.168.122.209 [52924.833736] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.1 ('example.com' vs 'default') Apr 26 06:46:14 192.168.122.209 [52924.837008] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.1 Apr 26 06:46:14 192.168.122.209 [52924.855988] device enp1s0 left promiscuous mode Apr 26 06:46:14 192.168.122.209 [52925.283997] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 06:46:14 192.168.122.209 [52925.372754] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [52925.372754] Maybe that's fine, but it's worth checking the [52925.372754] config - if there is no relations between the [52925.372754] names, then host name confusion attack is possible. Apr 26 06:46:14 192.168.122.209 [52925.430873] [tempesta fw] Configuration processing is completed. Apr 26 06:46:15 192.168.122.209 [52925.714941] [tempesta fw] Tempesta FW is ready Apr 26 06:46:15 192.168.122.209 [52925.757081] device enp1s0 entered promiscuous mode Apr 26 06:46:15 192.168.122.209 [52925.835097] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.1 ('example.com' vs 'default') Apr 26 06:46:15 192.168.122.209 [52925.838319] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.1 Apr 26 06:46:15 192.168.122.209 [52925.855135] device enp1s0 left promiscuous mode Apr 26 06:46:15 192.168.122.209 [52926.321417] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 06:46:15 192.168.122.209 [52926.408910] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [52926.408910] Maybe that's fine, but it's worth checking the [52926.408910] config - if there is no relations between the [52926.408910] names, then host name confusion attack is possible. Apr 26 06:46:15 192.168.122.209 [52926.466988] [tempesta fw] Configuration processing is completed. Apr 26 06:46:16 192.168.122.209 [52926.718986] [tempesta fw] Tempesta FW is ready Apr 26 06:46:16 192.168.122.209 [52926.763254] device enp1s0 entered promiscuous mode Apr 26 06:46:16 192.168.122.209 [52926.848817] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.1 ('example.com' vs 'default') Apr 26 06:46:16 192.168.122.209 [52926.849874] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.1 Apr 26 06:46:16 192.168.122.209 [52926.879315] device enp1s0 left promiscuous mode Apr 26 06:46:16 192.168.122.209 [52927.247509] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 06:46:16 192.168.122.209 [52927.305061] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [52927.305061] Maybe that's fine, but it's worth checking the [52927.305061] config - if there is no relations between the [52927.305061] names, then host name confusion attack is possible. Apr 26 06:46:16 192.168.122.209 [52927.366931] [tempesta fw] Configuration processing is completed. Apr 26 06:46:17 192.168.122.209 [52927.598973] [tempesta fw] Tempesta FW is ready Apr 26 06:46:17 192.168.122.209 [52927.655560] device enp1s0 entered promiscuous mode Apr 26 06:46:17 192.168.122.209 [52927.722524] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.1 ('example.com' vs 'default') Apr 26 06:46:17 192.168.122.209 [52927.724775] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.1 Apr 26 06:46:17 192.168.122.209 [52927.747256] device enp1s0 left promiscuous mode Apr 26 06:46:17 192.168.122.209 [52928.197608] [tdb] Close table 'client0.tdb' Apr 26 06:46:17 192.168.122.209 [52928.386115] [tdb] Close table 'sessions0.tdb' Apr 26 06:46:18 192.168.122.209 [52928.658332] [tdb] Close table 'filter0.tdb' Apr 26 06:46:18 192.168.122.209 [52928.659145] [tempesta fw] modules are stopped Apr 26 06:46:18 192.168.122.209 [52928.883110] [tempesta fw] exiting... Apr 26 06:46:18 192.168.122.209 [52928.996404] [tdb] Shutdown Tempesta DB Apr 26 06:46:18 192.168.122.209 [52929.207170] End test: tls.test_tls_cert.TlsCertSelectBySan.test_various_san_and_sni_matched Apr 26 06:46:18 192.168.122.209 [52929.227181] Start test: tls.test_tls_cert.TlsCertSelectBySan.test_unknown_server_name_warning Apr 26 06:46:19 192.168.122.209 [52930.352629] [tdb] Start Tempesta DB Apr 26 06:46:20 192.168.122.209 [52930.515295] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:46:20 192.168.122.209 [52931.153103] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [52931.153103] Maybe that's fine, but it's worth checking the [52931.153103] config - if there is no relations between the [52931.153103] names, then host name confusion attack is possible. Apr 26 06:46:20 192.168.122.209 [52931.218958] [tempesta fw] Configuration processing is completed. Apr 26 06:46:20 192.168.122.209 [52931.270174] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:46:20 192.168.122.209 [52931.299296] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:46:20 192.168.122.209 [52931.327871] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:46:20 192.168.122.209 [52931.366936] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:46:20 192.168.122.209 [52931.406950] [tempesta fw] Tempesta FW is ready Apr 26 06:46:21 192.168.122.209 [52931.593983] device enp1s0 entered promiscuous mode Apr 26 06:46:21 192.168.122.209 [52931.631327] [tempesta fw] Warning: client 127.0.0.1 requested unknown server name 'localhost' in TLS SNI, reject connection. Apr 26 06:46:21 192.168.122.209 [52931.655238] device enp1s0 left promiscuous mode Apr 26 06:46:21 192.168.122.209 [52931.806828] device enp1s0 entered promiscuous mode Apr 26 06:46:21 192.168.122.209 [52931.872240] [tempesta fw] Warning: client 127.0.0.1 requested unknown server name 'a.localhost' in TLS SNI, reject connection. Apr 26 06:46:21 192.168.122.209 [52931.895268] device enp1s0 left promiscuous mode Apr 26 06:46:21 192.168.122.209 [52932.043125] device enp1s0 entered promiscuous mode Apr 26 06:46:21 192.168.122.209 [52932.084644] [tempesta fw] Warning: client 127.0.0.1 requested unknown server name 'a.b.localhost' in TLS SNI, reject connection. Apr 26 06:46:21 192.168.122.209 [52932.103108] device enp1s0 left promiscuous mode Apr 26 06:46:21 192.168.122.209 [52932.266148] device enp1s0 entered promiscuous mode Apr 26 06:46:21 192.168.122.209 [52932.320648] [tempesta fw] Warning: client 127.0.0.1 requested unknown server name 'a.b.c.localhost' in TLS SNI, reject connection. Apr 26 06:46:21 192.168.122.209 [52932.339198] device enp1s0 left promiscuous mode Apr 26 06:46:22 192.168.122.209 [52932.506549] device enp1s0 entered promiscuous mode Apr 26 06:46:22 192.168.122.209 [52932.549055] [tempesta fw] Warning: client 127.0.0.1 requested unknown server name 'a.b.c.localhost.com' in TLS SNI, reject connection. Apr 26 06:46:22 192.168.122.209 [52932.567278] device enp1s0 left promiscuous mode Apr 26 06:46:22 192.168.122.209 [52932.725899] device enp1s0 entered promiscuous mode Apr 26 06:46:22 192.168.122.209 [52932.769390] [tempesta fw] Warning: client 127.0.0.1 requested unknown server name 'a.b.c.example.com' in TLS SNI, reject connection. Apr 26 06:46:22 192.168.122.209 [52932.787250] device enp1s0 left promiscuous mode Apr 26 06:46:22 192.168.122.209 [52932.922388] device enp1s0 entered promiscuous mode Apr 26 06:46:22 192.168.122.209 [52932.975112] [tempesta fw] Warning: client 127.0.0.1 requested unknown server name '' in TLS SNI, reject connection. Apr 26 06:46:22 192.168.122.209 [52933.009017] device enp1s0 left promiscuous mode Apr 26 06:46:22 192.168.122.209 [52933.168193] device enp1s0 entered promiscuous mode Apr 26 06:46:22 192.168.122.209 [52933.225947] [tempesta fw] Warning: client 127.0.0.1 requested unknown server name ' [52933.225947] [52933.225947] [52933.225947] ' in TLS SNI, reject connection. Apr 26 06:46:22 192.168.122.209 [52933.251443] device enp1s0 left promiscuous mode Apr 26 06:46:23 192.168.122.209 [52933.799910] [tdb] Close table 'client0.tdb' Apr 26 06:46:23 192.168.122.209 [52933.994241] [tdb] Close table 'sessions0.tdb' Apr 26 06:46:23 192.168.122.209 [52934.240445] [tdb] Close table 'filter0.tdb' Apr 26 06:46:23 192.168.122.209 [52934.240865] [tempesta fw] modules are stopped Apr 26 06:46:24 192.168.122.209 [52934.476444] [tempesta fw] exiting... Apr 26 06:46:24 192.168.122.209 [52934.593570] [tdb] Shutdown Tempesta DB Apr 26 06:46:24 192.168.122.209 [52934.805248] End test: tls.test_tls_cert.TlsCertSelectBySan.test_unknown_server_name_warning Apr 26 06:46:24 192.168.122.209 [52934.828927] Start test: tls.test_tls_cert.TlsCertSelectBySan.test_sni_not_matched Apr 26 06:46:25 192.168.122.209 [52935.872107] [tdb] Start Tempesta DB Apr 26 06:46:25 192.168.122.209 [52936.022548] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:46:26 192.168.122.209 [52936.681140] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [52936.681140] Maybe that's fine, but it's worth checking the [52936.681140] config - if there is no relations between the [52936.681140] names, then host name confusion attack is possible. Apr 26 06:46:26 192.168.122.209 [52936.727223] [tempesta fw] Configuration processing is completed. Apr 26 06:46:26 192.168.122.209 [52936.779059] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:46:26 192.168.122.209 [52936.806922] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:46:26 192.168.122.209 [52936.836616] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:46:26 192.168.122.209 [52936.879071] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:46:26 192.168.122.209 [52936.923000] [tempesta fw] Tempesta FW is ready Apr 26 06:46:26 192.168.122.209 [52937.058011] device enp1s0 entered promiscuous mode Apr 26 06:46:26 192.168.122.209 [52937.117528] [tempesta fw] Warning: client 127.0.0.1 requested unknown server name 'b.a.example.com' in TLS SNI, reject connection. Apr 26 06:46:26 192.168.122.209 [52937.139420] device enp1s0 left promiscuous mode Apr 26 06:46:26 192.168.122.209 [52937.162226] device enp1s0 entered promiscuous mode Apr 26 06:46:26 192.168.122.209 [52937.216777] [tempesta fw] Warning: client 127.0.0.1 requested unknown server name '..example.com' in TLS SNI, reject connection. Apr 26 06:46:26 192.168.122.209 [52937.239412] device enp1s0 left promiscuous mode Apr 26 06:46:26 192.168.122.209 [52937.261854] device enp1s0 entered promiscuous mode Apr 26 06:46:26 192.168.122.209 [52937.304572] [tempesta fw] Warning: client 127.0.0.1 requested unknown server name '.a.example.com' in TLS SNI, reject connection. Apr 26 06:46:26 192.168.122.209 [52937.327318] device enp1s0 left promiscuous mode Apr 26 06:46:26 192.168.122.209 [52937.356954] device enp1s0 entered promiscuous mode Apr 26 06:46:26 192.168.122.209 [52937.405196] [tempesta fw] Warning: client 127.0.0.1 requested unknown server name 'www.www.example.com' in TLS SNI, reject connection. Apr 26 06:46:26 192.168.122.209 [52937.431479] device enp1s0 left promiscuous mode Apr 26 06:46:26 192.168.122.209 [52937.452928] device enp1s0 entered promiscuous mode Apr 26 06:46:27 192.168.122.209 [52937.496550] [tempesta fw] Warning: client 127.0.0.1 requested unknown server name 'example.com.www' in TLS SNI, reject connection. Apr 26 06:46:27 192.168.122.209 [52937.519460] device enp1s0 left promiscuous mode Apr 26 06:46:27 192.168.122.209 [52937.545997] device enp1s0 entered promiscuous mode Apr 26 06:46:27 192.168.122.209 [52937.608454] [tempesta fw] Warning: client 127.0.0.1 requested unknown server name 'example.com.' in TLS SNI, reject connection. Apr 26 06:46:27 192.168.122.209 [52937.635387] device enp1s0 left promiscuous mode Apr 26 06:46:27 192.168.122.209 [52937.654283] device enp1s0 entered promiscuous mode Apr 26 06:46:27 192.168.122.209 [52937.697400] [tempesta fw] Warning: client 127.0.0.1 requested unknown server name 'a-example.com' in TLS SNI, reject connection. Apr 26 06:46:27 192.168.122.209 [52937.715315] device enp1s0 left promiscuous mode Apr 26 06:46:27 192.168.122.209 [52937.738630] device enp1s0 entered promiscuous mode Apr 26 06:46:27 192.168.122.209 [52937.790506] [tempesta fw] Warning: client 127.0.0.1 requested unknown server name 'a.example.comm' in TLS SNI, reject connection. Apr 26 06:46:27 192.168.122.209 [52937.811359] device enp1s0 left promiscuous mode Apr 26 06:46:27 192.168.122.209 [52937.830385] device enp1s0 entered promiscuous mode Apr 26 06:46:27 192.168.122.209 [52937.877030] [tempesta fw] Warning: client 127.0.0.1 requested unknown server name 'a.example.com-' in TLS SNI, reject connection. Apr 26 06:46:27 192.168.122.209 [52937.911688] device enp1s0 left promiscuous mode Apr 26 06:46:27 192.168.122.209 [52937.942299] device enp1s0 entered promiscuous mode Apr 26 06:46:27 192.168.122.209 [52937.984118] [tempesta fw] Warning: client 127.0.0.1 requested unknown server name 'a.example.com.' in TLS SNI, reject connection. Apr 26 06:46:27 192.168.122.209 [52938.007436] device enp1s0 left promiscuous mode Apr 26 06:46:27 192.168.122.209 [52938.036947] device enp1s0 entered promiscuous mode Apr 26 06:46:27 192.168.122.209 [52938.084574] [tempesta fw] Warning: client 127.0.0.1 requested unknown server name 'a.example.com.example.com' in TLS SNI, reject connection. Apr 26 06:46:27 192.168.122.209 [52938.107485] device enp1s0 left promiscuous mode Apr 26 06:46:27 192.168.122.209 [52938.134216] device enp1s0 entered promiscuous mode Apr 26 06:46:27 192.168.122.209 [52938.193454] [tempesta fw] Warning: client 127.0.0.1 requested unknown server name '127.0.0.3' in TLS SNI, reject connection. Apr 26 06:46:27 192.168.122.209 [52938.211263] device enp1s0 left promiscuous mode Apr 26 06:46:27 192.168.122.209 [52938.228867] device enp1s0 entered promiscuous mode Apr 26 06:46:27 192.168.122.209 [52938.281074] [tempesta fw] Warning: client 127.0.0.1 requested unknown server name 'aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa' in TLS SNI, reject connection. Apr 26 06:46:27 192.168.122.209 [52938.307570] device enp1s0 left promiscuous mode Apr 26 06:46:28 192.168.122.209 [52938.773869] [tdb] Close table 'client0.tdb' Apr 26 06:46:28 192.168.122.209 [52938.952283] [tdb] Close table 'sessions0.tdb' Apr 26 06:46:28 192.168.122.209 [52939.172425] [tdb] Close table 'filter0.tdb' Apr 26 06:46:28 192.168.122.209 [52939.172868] [tempesta fw] modules are stopped Apr 26 06:46:28 192.168.122.209 [52939.404632] [tempesta fw] exiting... Apr 26 06:46:29 192.168.122.209 [52939.503239] [tdb] Shutdown Tempesta DB Apr 26 06:46:29 192.168.122.209 [52939.731092] End test: tls.test_tls_cert.TlsCertSelectBySan.test_sni_not_matched Apr 26 06:46:29 192.168.122.209 [52939.747396] Start test: tls.test_tls_cert.TlsCertSelectBySan.test_sni_matched Apr 26 06:46:30 192.168.122.209 [52940.853470] [tdb] Start Tempesta DB Apr 26 06:46:30 192.168.122.209 [52940.995940] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:46:31 192.168.122.209 [52941.685249] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [52941.685249] Maybe that's fine, but it's worth checking the [52941.685249] config - if there is no relations between the [52941.685249] names, then host name confusion attack is possible. Apr 26 06:46:31 192.168.122.209 [52941.727569] [tempesta fw] Configuration processing is completed. Apr 26 06:46:31 192.168.122.209 [52941.781768] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:46:31 192.168.122.209 [52941.813491] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:46:31 192.168.122.209 [52941.847098] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:46:31 192.168.122.209 [52941.891080] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:46:31 192.168.122.209 [52941.931092] [tempesta fw] Tempesta FW is ready Apr 26 06:46:31 192.168.122.209 [52942.068871] device enp1s0 entered promiscuous mode Apr 26 06:46:31 192.168.122.209 [52942.140418] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.1 ('example.com' vs 'default') Apr 26 06:46:31 192.168.122.209 [52942.141479] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.1 Apr 26 06:46:31 192.168.122.209 [52942.159248] device enp1s0 left promiscuous mode Apr 26 06:46:31 192.168.122.209 [52942.178134] device enp1s0 entered promiscuous mode Apr 26 06:46:31 192.168.122.209 [52942.261814] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.1 ('example.com' vs 'default') Apr 26 06:46:31 192.168.122.209 [52942.265046] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.1 Apr 26 06:46:31 192.168.122.209 [52942.291372] device enp1s0 left promiscuous mode Apr 26 06:46:31 192.168.122.209 [52942.318289] device enp1s0 entered promiscuous mode Apr 26 06:46:31 192.168.122.209 [52942.397142] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.1 ('example.com' vs 'default') Apr 26 06:46:31 192.168.122.209 [52942.399543] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.1 Apr 26 06:46:31 192.168.122.209 [52942.415266] device enp1s0 left promiscuous mode Apr 26 06:46:31 192.168.122.209 [52942.434329] device enp1s0 entered promiscuous mode Apr 26 06:46:32 192.168.122.209 [52942.517140] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.1 ('example.com' vs 'default') Apr 26 06:46:32 192.168.122.209 [52942.519359] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.1 Apr 26 06:46:32 192.168.122.209 [52942.539470] device enp1s0 left promiscuous mode Apr 26 06:46:32 192.168.122.209 [52942.554075] device enp1s0 entered promiscuous mode Apr 26 06:46:32 192.168.122.209 [52942.626367] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.1 ('example.com' vs 'default') Apr 26 06:46:32 192.168.122.209 [52942.628944] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.1 Apr 26 06:46:32 192.168.122.209 [52942.647287] device enp1s0 left promiscuous mode Apr 26 06:46:32 192.168.122.209 [52942.674136] device enp1s0 entered promiscuous mode Apr 26 06:46:32 192.168.122.209 [52942.758019] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.1 ('example.com' vs 'default') Apr 26 06:46:32 192.168.122.209 [52942.761242] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.1 Apr 26 06:46:32 192.168.122.209 [52942.787481] device enp1s0 left promiscuous mode Apr 26 06:46:32 192.168.122.209 [52942.810221] device enp1s0 entered promiscuous mode Apr 26 06:46:32 192.168.122.209 [52942.899006] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.1 ('example.com' vs 'default') Apr 26 06:46:32 192.168.122.209 [52942.900049] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.1 Apr 26 06:46:32 192.168.122.209 [52942.919319] device enp1s0 left promiscuous mode Apr 26 06:46:32 192.168.122.209 [52942.938186] device enp1s0 entered promiscuous mode Apr 26 06:46:32 192.168.122.209 [52943.030561] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.1 ('example.com' vs 'default') Apr 26 06:46:32 192.168.122.209 [52943.033822] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.1 Apr 26 06:46:32 192.168.122.209 [52943.055514] device enp1s0 left promiscuous mode Apr 26 06:46:32 192.168.122.209 [52943.074479] device enp1s0 entered promiscuous mode Apr 26 06:46:32 192.168.122.209 [52943.161026] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.1 ('example.com' vs 'default') Apr 26 06:46:32 192.168.122.209 [52943.164313] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.1 Apr 26 06:46:32 192.168.122.209 [52943.187290] device enp1s0 left promiscuous mode Apr 26 06:46:32 192.168.122.209 [52943.209076] device enp1s0 entered promiscuous mode Apr 26 06:46:32 192.168.122.209 [52943.284432] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.1 ('example.com' vs 'default') Apr 26 06:46:32 192.168.122.209 [52943.287654] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.1 Apr 26 06:46:32 192.168.122.209 [52943.311380] device enp1s0 left promiscuous mode Apr 26 06:46:33 192.168.122.209 [52943.747599] [tdb] Close table 'client0.tdb' Apr 26 06:46:33 192.168.122.209 [52943.928782] [tdb] Close table 'sessions0.tdb' Apr 26 06:46:33 192.168.122.209 [52944.160094] [tdb] Close table 'filter0.tdb' Apr 26 06:46:33 192.168.122.209 [52944.160507] [tempesta fw] modules are stopped Apr 26 06:46:33 192.168.122.209 [52944.360171] [tempesta fw] exiting... Apr 26 06:46:33 192.168.122.209 [52944.465180] [tdb] Shutdown Tempesta DB Apr 26 06:46:34 192.168.122.209 [52944.679538] End test: tls.test_tls_cert.TlsCertSelectBySan.test_sni_matched Apr 26 06:46:34 192.168.122.209 [52944.694512] Start test: tls.test_tls_cert.TlsCertSelectBySan.test_sni_match_after_reload Apr 26 06:46:35 192.168.122.209 [52945.719984] [tdb] Start Tempesta DB Apr 26 06:46:35 192.168.122.209 [52945.863553] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:46:36 192.168.122.209 [52946.501092] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [52946.501092] Maybe that's fine, but it's worth checking the [52946.501092] config - if there is no relations between the [52946.501092] names, then host name confusion attack is possible. Apr 26 06:46:36 192.168.122.209 [52946.559134] [tempesta fw] Configuration processing is completed. Apr 26 06:46:36 192.168.122.209 [52946.613202] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:46:36 192.168.122.209 [52946.640886] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:46:36 192.168.122.209 [52946.668995] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:46:36 192.168.122.209 [52946.727193] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:46:36 192.168.122.209 [52946.779126] [tempesta fw] Tempesta FW is ready Apr 26 06:46:36 192.168.122.209 [52947.300391] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 06:46:36 192.168.122.209 [52947.366342] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [52947.366342] Maybe that's fine, but it's worth checking the [52947.366342] config - if there is no relations between the [52947.366342] names, then host name confusion attack is possible. Apr 26 06:46:36 192.168.122.209 [52947.419187] [tempesta fw] Configuration processing is completed. Apr 26 06:46:37 192.168.122.209 [52947.659231] [tempesta fw] Tempesta FW is ready Apr 26 06:46:37 192.168.122.209 [52947.710925] device enp1s0 entered promiscuous mode Apr 26 06:46:37 192.168.122.209 [52947.806907] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.1 ('example.com' vs 'default') Apr 26 06:46:37 192.168.122.209 [52947.809085] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.1 Apr 26 06:46:37 192.168.122.209 [52947.839651] device enp1s0 left promiscuous mode Apr 26 06:46:37 192.168.122.209 [52947.869638] device enp1s0 entered promiscuous mode Apr 26 06:46:37 192.168.122.209 [52947.917248] [tempesta fw] Warning: client 127.0.0.1 requested unknown server name 'b.tempesta-tech.com' in TLS SNI, reject connection. Apr 26 06:46:37 192.168.122.209 [52947.939508] device enp1s0 left promiscuous mode Apr 26 06:46:37 192.168.122.209 [52948.339680] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 06:46:37 192.168.122.209 [52948.406837] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [52948.406837] Maybe that's fine, but it's worth checking the [52948.406837] config - if there is no relations between the [52948.406837] names, then host name confusion attack is possible. Apr 26 06:46:37 192.168.122.209 [52948.455462] [tempesta fw] Configuration processing is completed. Apr 26 06:46:38 192.168.122.209 [52948.711258] [tempesta fw] Tempesta FW is ready Apr 26 06:46:38 192.168.122.209 [52948.766670] device enp1s0 entered promiscuous mode Apr 26 06:46:38 192.168.122.209 [52948.839080] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.1 ('example.com' vs 'default') Apr 26 06:46:38 192.168.122.209 [52948.840137] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.1 Apr 26 06:46:38 192.168.122.209 [52948.859458] device enp1s0 left promiscuous mode Apr 26 06:46:38 192.168.122.209 [52948.880459] device enp1s0 entered promiscuous mode Apr 26 06:46:38 192.168.122.209 [52948.930465] [tempesta fw] Warning: client 127.0.0.1 requested unknown server name 'a.example.com' in TLS SNI, reject connection. Apr 26 06:46:38 192.168.122.209 [52948.951508] device enp1s0 left promiscuous mode Apr 26 06:46:38 192.168.122.209 [52949.375759] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 06:46:38 192.168.122.209 [52949.449139] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [52949.449139] Maybe that's fine, but it's worth checking the [52949.449139] config - if there is no relations between the [52949.449139] names, then host name confusion attack is possible. Apr 26 06:46:39 192.168.122.209 [52949.503150] [tempesta fw] Configuration processing is completed. Apr 26 06:46:39 192.168.122.209 [52949.747243] [tempesta fw] Tempesta FW is ready Apr 26 06:46:39 192.168.122.209 [52949.805764] device enp1s0 entered promiscuous mode Apr 26 06:46:39 192.168.122.209 [52949.882815] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.1 ('example.com' vs 'default') Apr 26 06:46:39 192.168.122.209 [52949.883890] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.1 Apr 26 06:46:39 192.168.122.209 [52949.899482] device enp1s0 left promiscuous mode Apr 26 06:46:39 192.168.122.209 [52949.933718] device enp1s0 entered promiscuous mode Apr 26 06:46:39 192.168.122.209 [52949.977531] [tempesta fw] Warning: client 127.0.0.1 requested unknown server name 'b.tempesta-tech.com' in TLS SNI, reject connection. Apr 26 06:46:39 192.168.122.209 [52950.007606] device enp1s0 left promiscuous mode Apr 26 06:46:39 192.168.122.209 [52950.423683] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 06:46:40 192.168.122.209 [52950.489278] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [52950.489278] Maybe that's fine, but it's worth checking the [52950.489278] config - if there is no relations between the [52950.489278] names, then host name confusion attack is possible. Apr 26 06:46:40 192.168.122.209 [52950.547595] [tempesta fw] Configuration processing is completed. Apr 26 06:46:40 192.168.122.209 [52950.791286] [tempesta fw] Tempesta FW is ready Apr 26 06:46:40 192.168.122.209 [52950.833504] device enp1s0 entered promiscuous mode Apr 26 06:46:40 192.168.122.209 [52950.909263] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.1 ('example.com' vs 'default') Apr 26 06:46:40 192.168.122.209 [52950.912502] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.1 Apr 26 06:46:40 192.168.122.209 [52950.943585] device enp1s0 left promiscuous mode Apr 26 06:46:40 192.168.122.209 [52950.969636] device enp1s0 entered promiscuous mode Apr 26 06:46:40 192.168.122.209 [52951.027071] [tempesta fw] Warning: client 127.0.0.1 requested unknown server name 'a.example.com' in TLS SNI, reject connection. Apr 26 06:46:40 192.168.122.209 [52951.047663] device enp1s0 left promiscuous mode Apr 26 06:46:41 192.168.122.209 [52951.512925] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 06:46:41 192.168.122.209 [52951.577169] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [52951.577169] Maybe that's fine, but it's worth checking the [52951.577169] config - if there is no relations between the [52951.577169] names, then host name confusion attack is possible. Apr 26 06:46:41 192.168.122.209 [52951.635262] [tempesta fw] Configuration processing is completed. Apr 26 06:46:41 192.168.122.209 [52951.847286] [tempesta fw] Tempesta FW is ready Apr 26 06:46:41 192.168.122.209 [52951.893174] device enp1s0 entered promiscuous mode Apr 26 06:46:41 192.168.122.209 [52951.978577] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 127.0.0.1 ('example.com' vs 'default') Apr 26 06:46:41 192.168.122.209 [52951.979645] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.1 Apr 26 06:46:41 192.168.122.209 [52951.999460] device enp1s0 left promiscuous mode Apr 26 06:46:41 192.168.122.209 [52952.029505] device enp1s0 entered promiscuous mode Apr 26 06:46:41 192.168.122.209 [52952.083982] [tempesta fw] Warning: client 127.0.0.1 requested unknown server name 'b.tempesta-tech.com' in TLS SNI, reject connection. Apr 26 06:46:41 192.168.122.209 [52952.115479] device enp1s0 left promiscuous mode Apr 26 06:46:42 192.168.122.209 [52952.572745] [tdb] Close table 'client0.tdb' Apr 26 06:46:42 192.168.122.209 [52952.769990] [tdb] Close table 'sessions0.tdb' Apr 26 06:46:42 192.168.122.209 [52952.990663] [tdb] Close table 'filter0.tdb' Apr 26 06:46:42 192.168.122.209 [52952.991112] [tempesta fw] modules are stopped Apr 26 06:46:42 192.168.122.209 [52953.189179] [tempesta fw] exiting... Apr 26 06:46:42 192.168.122.209 [52953.289365] [tdb] Shutdown Tempesta DB Apr 26 06:46:43 192.168.122.209 [52953.508509] End test: tls.test_tls_cert.TlsCertSelectBySan.test_sni_match_after_reload Apr 26 06:46:43 192.168.122.209 [52953.535779] Start test: tls.test_tls_cert.TlsCertSelect.test_vhost_cert_selection Apr 26 06:46:44 192.168.122.209 [52954.944312] [tdb] Start Tempesta DB Apr 26 06:46:44 192.168.122.209 [52955.103232] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:46:45 192.168.122.209 [52956.034008] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52956.034008] Maybe that's fine, but it's worth checking the [52956.034008] config - if there is no relations between the [52956.034008] names, then host name confusion attack is possible. Apr 26 06:46:45 192.168.122.209 [52956.123006] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [52956.123006] Maybe that's fine, but it's worth checking the [52956.123006] config - if there is no relations between the [52956.123006] names, then host name confusion attack is possible. Apr 26 06:46:45 192.168.122.209 [52956.136136] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [52956.136136] Maybe that's fine, but it's worth checking the [52956.136136] config - if there is no relations between the [52956.136136] names, then host name confusion attack is possible. Apr 26 06:46:45 192.168.122.209 [52956.211409] [tempesta fw] Configuration processing is completed. Apr 26 06:46:45 192.168.122.209 [52956.267716] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:46:45 192.168.122.209 [52956.299535] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:46:45 192.168.122.209 [52956.329345] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:46:45 192.168.122.209 [52956.371254] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:46:45 192.168.122.209 [52956.415289] [tempesta fw] Tempesta FW is ready Apr 26 06:46:46 192.168.122.209 [52956.558641] device enp1s0 entered promiscuous mode Apr 26 06:46:46 192.168.122.209 [52956.683800] device enp1s0 left promiscuous mode Apr 26 06:46:46 192.168.122.209 [52956.709875] device enp1s0 entered promiscuous mode Apr 26 06:46:46 192.168.122.209 [52956.765410] [tempesta fw] Warning: client 127.0.0.1 requested unknown server name 'example.com' in TLS SNI, reject connection. Apr 26 06:46:46 192.168.122.209 [52956.799773] device enp1s0 left promiscuous mode Apr 26 06:46:46 192.168.122.209 [52957.216684] [tdb] Close table 'client0.tdb' Apr 26 06:46:46 192.168.122.209 [52957.415837] [tdb] Close table 'sessions0.tdb' Apr 26 06:46:47 192.168.122.209 [52957.669993] [tdb] Close table 'filter0.tdb' Apr 26 06:46:47 192.168.122.209 [52957.670427] [tempesta fw] modules are stopped Apr 26 06:46:47 192.168.122.209 [52957.920313] [tempesta fw] exiting... Apr 26 06:46:47 192.168.122.209 [52958.031050] [tdb] Shutdown Tempesta DB Apr 26 06:46:47 192.168.122.209 [52958.269223] End test: tls.test_tls_cert.TlsCertSelect.test_vhost_cert_selection Apr 26 06:46:47 192.168.122.209 [52958.287983] Start test: tls.test_tls_cert.StaleCert.test Apr 26 06:46:48 192.168.122.209 [52959.426958] [tdb] Start Tempesta DB Apr 26 06:46:49 192.168.122.209 [52959.562393] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:46:49 192.168.122.209 [52960.092780] [tempesta fw] Warning: The certificate '/tmp/host/tempesta.crt' has expired! Please renew [52960.092780] the certificate to maintain functionality. Apr 26 06:46:49 192.168.122.209 [52960.092852] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52960.092852] Maybe that's fine, but it's worth checking the [52960.092852] config - if there is no relations between the [52960.092852] names, then host name confusion attack is possible. Apr 26 06:46:49 192.168.122.209 [52960.183426] [tempesta fw] Configuration processing is completed. Apr 26 06:46:49 192.168.122.209 [52960.244677] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:46:49 192.168.122.209 [52960.274025] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:46:49 192.168.122.209 [52960.303800] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:46:49 192.168.122.209 [52960.379388] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:46:49 192.168.122.209 [52960.427299] [tempesta fw] Tempesta FW is ready Apr 26 06:46:50 192.168.122.209 [52960.997198] [tdb] Close table 'client0.tdb' Apr 26 06:46:50 192.168.122.209 [52961.210250] [tdb] Close table 'sessions0.tdb' Apr 26 06:46:50 192.168.122.209 [52961.452059] [tdb] Close table 'filter0.tdb' Apr 26 06:46:50 192.168.122.209 [52961.452495] [tempesta fw] modules are stopped Apr 26 06:46:51 192.168.122.209 [52961.630868] [tempesta fw] exiting... Apr 26 06:46:51 192.168.122.209 [52961.751928] [tdb] Shutdown Tempesta DB Apr 26 06:46:51 192.168.122.209 [52961.995565] End test: tls.test_tls_cert.StaleCert.test Apr 26 06:46:51 192.168.122.209 [52962.010219] Start test: tls.test_tls_cert.RSA512_SHA256.test Apr 26 06:46:52 192.168.122.209 [52963.171123] [tdb] Start Tempesta DB Apr 26 06:46:52 192.168.122.209 [52963.311452] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:46:53 192.168.122.209 [52963.836544] [tempesta tls] Warning: Trying to load an RSA key smaller than 1024 bits. Please use stronger keys. Apr 26 06:46:53 192.168.122.209 [52963.839179] [tempesta fw] ERROR: tls_certificate: Invalid certificate specified, err=c Apr 26 06:46:53 192.168.122.209 [52963.841140] [tempesta fw] ERROR: configuration parsing error: [52963.841140] 4: tls_certificate /tmp/host/tempesta.crt; [52963.841140] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 06:46:53 192.168.122.209 [52963.844951] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 06:46:53 192.168.122.209 [52963.990400] [tempesta fw] exiting... Apr 26 06:46:53 192.168.122.209 [52964.124619] [tdb] Shutdown Tempesta DB Apr 26 06:46:54 192.168.122.209 [52964.710053] End test: tls.test_tls_cert.RSA512_SHA256.test Apr 26 06:46:54 192.168.122.209 [52964.733905] Start test: tls.test_tls_cert.RSA4096_SHA512.test Apr 26 06:46:57 192.168.122.209 [52968.284286] [tdb] Start Tempesta DB Apr 26 06:46:57 192.168.122.209 [52968.438877] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:46:58 192.168.122.209 [52968.781871] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52968.781871] Maybe that's fine, but it's worth checking the [52968.781871] config - if there is no relations between the [52968.781871] names, then host name confusion attack is possible. Apr 26 06:46:58 192.168.122.209 [52968.891795] [tempesta fw] Configuration processing is completed. Apr 26 06:46:58 192.168.122.209 [52968.956333] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:46:58 192.168.122.209 [52968.996552] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:46:58 192.168.122.209 [52969.037354] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:46:58 192.168.122.209 [52969.079433] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:46:58 192.168.122.209 [52969.119410] [tempesta fw] Tempesta FW is ready Apr 26 06:46:59 192.168.122.209 [52969.779782] [tdb] Close table 'client0.tdb' Apr 26 06:46:59 192.168.122.209 [52969.968142] [tdb] Close table 'sessions0.tdb' Apr 26 06:46:59 192.168.122.209 [52970.219640] [tdb] Close table 'filter0.tdb' Apr 26 06:46:59 192.168.122.209 [52970.220092] [tempesta fw] modules are stopped Apr 26 06:46:59 192.168.122.209 [52970.413336] [tempesta fw] exiting... Apr 26 06:47:00 192.168.122.209 [52970.524131] [tdb] Shutdown Tempesta DB Apr 26 06:47:00 192.168.122.209 [52970.758958] End test: tls.test_tls_cert.RSA4096_SHA512.test Apr 26 06:47:00 192.168.122.209 [52970.777359] Start test: tls.test_tls_cert.RSA2048_SHA512.test Apr 26 06:47:01 192.168.122.209 [52971.944113] [tdb] Start Tempesta DB Apr 26 06:47:01 192.168.122.209 [52972.094142] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:47:02 192.168.122.209 [52972.613431] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52972.613431] Maybe that's fine, but it's worth checking the [52972.613431] config - if there is no relations between the [52972.613431] names, then host name confusion attack is possible. Apr 26 06:47:02 192.168.122.209 [52972.699867] [tempesta fw] Configuration processing is completed. Apr 26 06:47:02 192.168.122.209 [52972.763380] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:47:02 192.168.122.209 [52972.796411] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:47:02 192.168.122.209 [52972.825059] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:47:02 192.168.122.209 [52972.867447] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:47:02 192.168.122.209 [52972.907472] [tempesta fw] Tempesta FW is ready Apr 26 06:47:03 192.168.122.209 [52973.496974] [tdb] Close table 'client0.tdb' Apr 26 06:47:03 192.168.122.209 [52973.702680] [tdb] Close table 'sessions0.tdb' Apr 26 06:47:03 192.168.122.209 [52973.931259] [tdb] Close table 'filter0.tdb' Apr 26 06:47:03 192.168.122.209 [52973.932061] [tempesta fw] modules are stopped Apr 26 06:47:03 192.168.122.209 [52974.124910] [tempesta fw] exiting... Apr 26 06:47:03 192.168.122.209 [52974.226449] [tdb] Shutdown Tempesta DB Apr 26 06:47:03 192.168.122.209 [52974.445225] End test: tls.test_tls_cert.RSA2048_SHA512.test Apr 26 06:47:03 192.168.122.209 [52974.466047] Start test: tls.test_tls_cert.RSA1024_SHA384.test Apr 26 06:47:05 192.168.122.209 [52975.522580] [tdb] Start Tempesta DB Apr 26 06:47:05 192.168.122.209 [52975.652454] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:47:05 192.168.122.209 [52976.126449] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52976.126449] Maybe that's fine, but it's worth checking the [52976.126449] config - if there is no relations between the [52976.126449] names, then host name confusion attack is possible. Apr 26 06:47:05 192.168.122.209 [52976.223692] [tempesta fw] Configuration processing is completed. Apr 26 06:47:05 192.168.122.209 [52976.277740] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:47:05 192.168.122.209 [52976.304919] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:47:05 192.168.122.209 [52976.332768] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:47:05 192.168.122.209 [52976.375588] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:47:05 192.168.122.209 [52976.415594] [tempesta fw] Tempesta FW is ready Apr 26 06:47:06 192.168.122.209 [52977.014444] [tdb] Close table 'client0.tdb' Apr 26 06:47:06 192.168.122.209 [52977.221834] [tdb] Close table 'sessions0.tdb' Apr 26 06:47:06 192.168.122.209 [52977.438721] [tdb] Close table 'filter0.tdb' Apr 26 06:47:06 192.168.122.209 [52977.439168] [tempesta fw] modules are stopped Apr 26 06:47:07 192.168.122.209 [52977.677006] [tempesta fw] exiting... Apr 26 06:47:07 192.168.122.209 [52977.772528] [tdb] Shutdown Tempesta DB Apr 26 06:47:07 192.168.122.209 [52978.001762] End test: tls.test_tls_cert.RSA1024_SHA384.test Apr 26 06:47:07 192.168.122.209 [52978.021130] Start test: tls.test_tls_cert.InvalidKeyWithGoodCert.test Apr 26 06:47:08 192.168.122.209 [52979.240841] [tdb] Start Tempesta DB Apr 26 06:47:08 192.168.122.209 [52979.373979] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:47:09 192.168.122.209 [52979.844789] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52979.844789] Maybe that's fine, but it's worth checking the [52979.844789] config - if there is no relations between the [52979.844789] names, then host name confusion attack is possible. Apr 26 06:47:09 192.168.122.209 [52979.868002] [tempesta tls] Warning: PK - Elliptic curve with OID 1.2.840.10045.3.1.1 is unsupported Apr 26 06:47:09 192.168.122.209 [52979.870566] [tempesta fw] ERROR: tls_certificate_key: Invalid private key specified (16) Apr 26 06:47:09 192.168.122.209 [52979.872828] [tempesta fw] ERROR: configuration parsing error: [52979.872828] 5: tls_certificate_key /tmp/host/tempesta.key; [52979.872828] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 06:47:09 192.168.122.209 [52979.877878] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 06:47:09 192.168.122.209 [52980.031895] [tempesta fw] exiting... Apr 26 06:47:09 192.168.122.209 [52980.180356] [tdb] Shutdown Tempesta DB Apr 26 06:47:10 192.168.122.209 [52980.717291] End test: tls.test_tls_cert.InvalidKeyWithGoodCert.test Apr 26 06:47:10 192.168.122.209 [52980.733384] Start test: tls.test_tls_cert.InvalidHash.test Apr 26 06:47:11 192.168.122.209 [52981.850935] [tdb] Start Tempesta DB Apr 26 06:47:11 192.168.122.209 [52981.983631] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:47:11 192.168.122.209 [52982.308119] [tempesta tls] Warning: X509 - Signature algorithm with OID 1.2.840.10045.4.1 is unsupported Apr 26 06:47:11 192.168.122.209 [52982.308135] [tempesta fw] ERROR: tls_certificate: Invalid certificate specified, err=2600 Apr 26 06:47:11 192.168.122.209 [52982.313240] [tempesta fw] ERROR: configuration parsing error: [52982.313240] 4: tls_certificate /tmp/host/tempesta.crt; [52982.313240] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 06:47:11 192.168.122.209 [52982.317389] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 06:47:11 192.168.122.209 [52982.442426] [tempesta fw] exiting... Apr 26 06:47:12 192.168.122.209 [52982.561021] [tdb] Shutdown Tempesta DB Apr 26 06:47:12 192.168.122.209 [52983.098760] End test: tls.test_tls_cert.InvalidHash.test Apr 26 06:47:12 192.168.122.209 [52983.125743] Start test: tls.test_tls_cert.ECDSA_SHA384_SECP521.test Apr 26 06:47:13 192.168.122.209 [52984.244854] [tdb] Start Tempesta DB Apr 26 06:47:13 192.168.122.209 [52984.381219] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:47:14 192.168.122.209 [52984.677012] [tempesta tls] Warning: PK - Elliptic curve with OID 1.3.132.0.35 is unsupported Apr 26 06:47:14 192.168.122.209 [52984.679702] [tempesta fw] ERROR: tls_certificate: Invalid certificate specified, err=16 Apr 26 06:47:14 192.168.122.209 [52984.681904] [tempesta fw] ERROR: configuration parsing error: [52984.681904] 4: tls_certificate /tmp/host/tempesta.crt; [52984.681904] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 06:47:14 192.168.122.209 [52984.686796] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 06:47:14 192.168.122.209 [52984.879631] [tempesta fw] exiting... Apr 26 06:47:14 192.168.122.209 [52984.994682] [tdb] Shutdown Tempesta DB Apr 26 06:47:15 192.168.122.209 [52985.520954] End test: tls.test_tls_cert.ECDSA_SHA384_SECP521.test Apr 26 06:47:15 192.168.122.209 [52985.545944] Start test: tls.test_tls_cert.ECDSA_SHA384_SECP256.test Apr 26 06:47:16 192.168.122.209 [52986.530808] [tdb] Start Tempesta DB Apr 26 06:47:16 192.168.122.209 [52986.676745] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:47:16 192.168.122.209 [52986.976946] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52986.976946] Maybe that's fine, but it's worth checking the [52986.976946] config - if there is no relations between the [52986.976946] names, then host name confusion attack is possible. Apr 26 06:47:16 192.168.122.209 [52987.059728] [tempesta fw] Configuration processing is completed. Apr 26 06:47:16 192.168.122.209 [52987.109238] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:47:16 192.168.122.209 [52987.137045] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:47:16 192.168.122.209 [52987.164912] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:47:16 192.168.122.209 [52987.211699] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:47:16 192.168.122.209 [52987.271643] [tempesta fw] Tempesta FW is ready Apr 26 06:47:17 192.168.122.209 [52987.842807] [tdb] Close table 'client0.tdb' Apr 26 06:47:17 192.168.122.209 [52988.038176] [tdb] Close table 'sessions0.tdb' Apr 26 06:47:17 192.168.122.209 [52988.261128] [tdb] Close table 'filter0.tdb' Apr 26 06:47:17 192.168.122.209 [52988.261525] [tempesta fw] modules are stopped Apr 26 06:47:18 192.168.122.209 [52988.483875] [tempesta fw] exiting... Apr 26 06:47:18 192.168.122.209 [52988.614324] [tdb] Shutdown Tempesta DB Apr 26 06:47:18 192.168.122.209 [52988.844256] End test: tls.test_tls_cert.ECDSA_SHA384_SECP256.test Apr 26 06:47:18 192.168.122.209 [52988.863119] Start test: tls.test_tls_cert.ECDSA_SHA256_SECP256.test Apr 26 06:47:19 192.168.122.209 [52989.896199] [tdb] Start Tempesta DB Apr 26 06:47:19 192.168.122.209 [52990.044476] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:47:20 192.168.122.209 [52990.573106] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52990.573106] Maybe that's fine, but it's worth checking the [52990.573106] config - if there is no relations between the [52990.573106] names, then host name confusion attack is possible. Apr 26 06:47:20 192.168.122.209 [52990.667759] [tempesta fw] Configuration processing is completed. Apr 26 06:47:20 192.168.122.209 [52990.722906] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:47:20 192.168.122.209 [52990.752771] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:47:20 192.168.122.209 [52990.780673] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:47:20 192.168.122.209 [52990.827733] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:47:20 192.168.122.209 [52990.867693] [tempesta fw] Tempesta FW is ready Apr 26 06:47:20 192.168.122.209 [52991.430046] [tdb] Close table 'client0.tdb' Apr 26 06:47:21 192.168.122.209 [52991.642000] [tdb] Close table 'sessions0.tdb' Apr 26 06:47:21 192.168.122.209 [52991.884647] [tdb] Close table 'filter0.tdb' Apr 26 06:47:21 192.168.122.209 [52991.885061] [tempesta fw] modules are stopped Apr 26 06:47:21 192.168.122.209 [52992.096001] [tempesta fw] exiting... Apr 26 06:47:21 192.168.122.209 [52992.229689] [tdb] Shutdown Tempesta DB Apr 26 06:47:22 192.168.122.209 [52992.475400] End test: tls.test_tls_cert.ECDSA_SHA256_SECP256.test Apr 26 06:47:22 192.168.122.209 [52992.499146] Start test: tls.test_tls_cert.ECDSA_SHA256_SECP192.test Apr 26 06:47:23 192.168.122.209 [52993.639936] [tdb] Start Tempesta DB Apr 26 06:47:23 192.168.122.209 [52993.781791] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:47:23 192.168.122.209 [52994.280996] [tempesta tls] Warning: PK - Elliptic curve with OID 1.2.840.10045.3.1.1 is unsupported Apr 26 06:47:23 192.168.122.209 [52994.283843] [tempesta fw] ERROR: tls_certificate: Invalid certificate specified, err=16 Apr 26 06:47:23 192.168.122.209 [52994.286039] [tempesta fw] ERROR: configuration parsing error: [52994.286039] 4: tls_certificate /tmp/host/tempesta.crt; [52994.286039] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 06:47:23 192.168.122.209 [52994.289530] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 06:47:23 192.168.122.209 [52994.455049] [tempesta fw] exiting... Apr 26 06:47:24 192.168.122.209 [52994.559235] [tdb] Shutdown Tempesta DB Apr 26 06:47:24 192.168.122.209 [52995.085192] End test: tls.test_tls_cert.ECDSA_SHA256_SECP192.test Apr 26 06:47:24 192.168.122.209 [52995.106365] Start test: tls.test_tls_cert.BaseTlsSniWithHttpTable.test_with_san Apr 26 06:47:24 192.168.122.209 [52995.121974] End test: tls.test_tls_cert.BaseTlsSniWithHttpTable.test_with_san Apr 26 06:47:24 192.168.122.209 [52995.141419] Start test: tls.test_tls_cert.BaseTlsSniWithHttpTable.test_with_common_name Apr 26 06:47:24 192.168.122.209 [52995.155478] End test: tls.test_tls_cert.BaseTlsSniWithHttpTable.test_with_common_name Apr 26 06:47:24 192.168.122.209 [52995.171263] Start test: tls.test_tls_cert.BaseTlsSniWithHttpTable.test_with_any_host Apr 26 06:47:24 192.168.122.209 [52995.189276] End test: tls.test_tls_cert.BaseTlsSniWithHttpTable.test_with_any_host Apr 26 06:47:24 192.168.122.209 [52995.199918] Start test: tls.test_tls_cert.BaseTlsSniWithHttpTable.test_valid Apr 26 06:47:24 192.168.122.209 [52995.210969] End test: tls.test_tls_cert.BaseTlsSniWithHttpTable.test_valid Apr 26 06:47:24 192.168.122.209 [52995.234405] Start test: tls.test_tls_basic.TlsBasic.test_connection_close Apr 26 06:47:25 192.168.122.209 [52996.217619] [tdb] Start Tempesta DB Apr 26 06:47:25 192.168.122.209 [52996.360230] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:47:26 192.168.122.209 [52996.657113] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [52996.657113] Maybe that's fine, but it's worth checking the [52996.657113] config - if there is no relations between the [52996.657113] names, then host name confusion attack is possible. Apr 26 06:47:26 192.168.122.209 [52996.748133] [tempesta fw] Configuration processing is completed. Apr 26 06:47:26 192.168.122.209 [52996.804832] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:47:26 192.168.122.209 [52996.831886] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:47:26 192.168.122.209 [52996.858783] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:47:26 192.168.122.209 [52996.903823] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:47:26 192.168.122.209 [52996.943753] [tempesta fw] Tempesta FW is ready Apr 26 06:47:27 192.168.122.209 [52997.544056] [tdb] Close table 'client0.tdb' Apr 26 06:47:27 192.168.122.209 [52997.733916] [tdb] Close table 'sessions0.tdb' Apr 26 06:47:27 192.168.122.209 [52997.965461] [tdb] Close table 'filter0.tdb' Apr 26 06:47:27 192.168.122.209 [52997.965917] [tempesta fw] modules are stopped Apr 26 06:47:27 192.168.122.209 [52998.175795] [tempesta fw] exiting... Apr 26 06:47:27 192.168.122.209 [52998.313426] [tdb] Shutdown Tempesta DB Apr 26 06:47:28 192.168.122.209 [52998.567239] End test: tls.test_tls_basic.TlsBasic.test_connection_close Apr 26 06:47:28 192.168.122.209 [52998.587604] Start test: tls.test_tls_basic.TlsBasic.test_bad_request Apr 26 06:47:29 192.168.122.209 [52999.628639] [tdb] Start Tempesta DB Apr 26 06:47:29 192.168.122.209 [52999.780600] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:47:29 192.168.122.209 [53000.273148] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53000.273148] Maybe that's fine, but it's worth checking the [53000.273148] config - if there is no relations between the [53000.273148] names, then host name confusion attack is possible. Apr 26 06:47:29 192.168.122.209 [53000.355900] [tempesta fw] Configuration processing is completed. Apr 26 06:47:29 192.168.122.209 [53000.406684] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:47:29 192.168.122.209 [53000.436393] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:47:29 192.168.122.209 [53000.465389] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:47:30 192.168.122.209 [53000.511851] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:47:30 192.168.122.209 [53000.563820] [tempesta fw] Tempesta FW is ready Apr 26 06:47:30 192.168.122.209 [53000.715327] [tempesta fw] Warning: Parser error: state=Req_HttpVerT2 input(-0)=0x78('x') data_len=1 off=0 Apr 26 06:47:30 192.168.122.209 [53001.094660] [tdb] Close table 'client0.tdb' Apr 26 06:47:30 192.168.122.209 [53001.312831] [tdb] Close table 'sessions0.tdb' Apr 26 06:47:31 192.168.122.209 [53001.545134] [tdb] Close table 'filter0.tdb' Apr 26 06:47:31 192.168.122.209 [53001.545546] [tempesta fw] modules are stopped Apr 26 06:47:31 192.168.122.209 [53001.794276] [tempesta fw] exiting... Apr 26 06:47:31 192.168.122.209 [53001.916713] [tdb] Shutdown Tempesta DB Apr 26 06:47:31 192.168.122.209 [53002.140509] End test: tls.test_tls_basic.TlsBasic.test_bad_request Apr 26 06:47:31 192.168.122.209 [53002.151822] Start test: tls.test_tls_alpn_basic.TestALPN.test_proto_order_https_least_prio Apr 26 06:47:32 192.168.122.209 [53003.191118] [tdb] Start Tempesta DB Apr 26 06:47:32 192.168.122.209 [53003.343352] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:47:33 192.168.122.209 [53004.065804] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [53004.065804] Maybe that's fine, but it's worth checking the [53004.065804] config - if there is no relations between the [53004.065804] names, then host name confusion attack is possible. Apr 26 06:47:33 192.168.122.209 [53004.108357] [tempesta fw] Configuration processing is completed. Apr 26 06:47:33 192.168.122.209 [53004.158385] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:47:34 192.168.122.209 [53004.865642] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:47:34 192.168.122.209 [53004.923529] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:47:34 192.168.122.209 [53004.971917] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:47:34 192.168.122.209 [53005.035978] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:47:34 192.168.122.209 [53005.075865] [tempesta fw] Tempesta FW is ready Apr 26 06:47:35 192.168.122.209 [53005.706745] [tdb] Close table 'client0.tdb' Apr 26 06:47:35 192.168.122.209 [53005.882322] [tdb] Close table 'sessions0.tdb' Apr 26 06:47:38 192.168.122.209 [53009.108701] [tdb] Close table 'cache0.tdb' Apr 26 06:47:38 192.168.122.209 [53009.343057] [tdb] Close table 'filter0.tdb' Apr 26 06:47:38 192.168.122.209 [53009.343486] [tempesta fw] modules are stopped Apr 26 06:47:39 192.168.122.209 [53009.529227] [tempesta fw] exiting... Apr 26 06:47:39 192.168.122.209 [53009.644327] [tdb] Shutdown Tempesta DB Apr 26 06:47:39 192.168.122.209 [53009.893718] End test: tls.test_tls_alpn_basic.TestALPN.test_proto_order_https_least_prio Apr 26 06:47:39 192.168.122.209 [53009.910814] Start test: tls.test_tls_alpn_basic.TestALPN.test_proto_order_https Apr 26 06:47:40 192.168.122.209 [53010.993569] [tdb] Start Tempesta DB Apr 26 06:47:40 192.168.122.209 [53011.140012] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:47:42 192.168.122.209 [53012.633914] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [53012.633914] Maybe that's fine, but it's worth checking the [53012.633914] config - if there is no relations between the [53012.633914] names, then host name confusion attack is possible. Apr 26 06:47:42 192.168.122.209 [53012.712332] [tempesta fw] Configuration processing is completed. Apr 26 06:47:42 192.168.122.209 [53012.770280] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:47:42 192.168.122.209 [53013.189642] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:47:42 192.168.122.209 [53013.216456] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:47:42 192.168.122.209 [53013.243916] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:47:42 192.168.122.209 [53013.304008] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:47:42 192.168.122.209 [53013.343961] [tempesta fw] Tempesta FW is ready Apr 26 06:47:43 192.168.122.209 [53013.996660] [tdb] Close table 'client0.tdb' Apr 26 06:47:43 192.168.122.209 [53014.199670] [tdb] Close table 'sessions0.tdb' Apr 26 06:47:46 192.168.122.209 [53017.376208] [tdb] Close table 'cache0.tdb' Apr 26 06:47:47 192.168.122.209 [53017.595733] [tdb] Close table 'filter0.tdb' Apr 26 06:47:47 192.168.122.209 [53017.596177] [tempesta fw] modules are stopped Apr 26 06:47:47 192.168.122.209 [53017.818482] [tempesta fw] exiting... Apr 26 06:47:47 192.168.122.209 [53017.956235] [tdb] Shutdown Tempesta DB Apr 26 06:47:47 192.168.122.209 [53018.204739] End test: tls.test_tls_alpn_basic.TestALPN.test_proto_order_https Apr 26 06:47:47 192.168.122.209 [53018.224806] Start test: tls.test_tls_alpn_basic.TestALPN.test_proto_order_h2_least_prio Apr 26 06:47:48 192.168.122.209 [53019.374793] [tdb] Start Tempesta DB Apr 26 06:47:49 192.168.122.209 [53019.502431] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:47:50 192.168.122.209 [53020.993955] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [53020.993955] Maybe that's fine, but it's worth checking the [53020.993955] config - if there is no relations between the [53020.993955] names, then host name confusion attack is possible. Apr 26 06:47:50 192.168.122.209 [53021.044444] [tempesta fw] Configuration processing is completed. Apr 26 06:47:50 192.168.122.209 [53021.101660] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:47:51 192.168.122.209 [53021.566437] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:47:51 192.168.122.209 [53021.596323] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:47:51 192.168.122.209 [53021.626726] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:47:51 192.168.122.209 [53021.696132] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:47:51 192.168.122.209 [53021.736084] [tempesta fw] Tempesta FW is ready Apr 26 06:47:51 192.168.122.209 [53022.368592] [tdb] Close table 'client0.tdb' Apr 26 06:47:52 192.168.122.209 [53022.568981] [tdb] Close table 'sessions0.tdb' Apr 26 06:47:55 192.168.122.209 [53025.799309] [tdb] Close table 'cache0.tdb' Apr 26 06:47:55 192.168.122.209 [53026.045144] [tdb] Close table 'filter0.tdb' Apr 26 06:47:55 192.168.122.209 [53026.045576] [tempesta fw] modules are stopped Apr 26 06:47:55 192.168.122.209 [53026.236606] [tempesta fw] exiting... Apr 26 06:47:55 192.168.122.209 [53026.370951] [tdb] Shutdown Tempesta DB Apr 26 06:47:56 192.168.122.209 [53026.611468] End test: tls.test_tls_alpn_basic.TestALPN.test_proto_order_h2_least_prio Apr 26 06:47:56 192.168.122.209 [53026.622826] Start test: tls.test_tls_alpn_basic.TestALPN.test_proto_order_h2 Apr 26 06:47:57 192.168.122.209 [53027.652159] [tdb] Start Tempesta DB Apr 26 06:47:57 192.168.122.209 [53027.796094] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:47:58 192.168.122.209 [53029.230269] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [53029.230269] Maybe that's fine, but it's worth checking the [53029.230269] config - if there is no relations between the [53029.230269] names, then host name confusion attack is possible. Apr 26 06:47:58 192.168.122.209 [53029.272523] [tempesta fw] Configuration processing is completed. Apr 26 06:47:58 192.168.122.209 [53029.323658] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:47:59 192.168.122.209 [53029.752187] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:47:59 192.168.122.209 [53029.779317] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:47:59 192.168.122.209 [53029.807650] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:47:59 192.168.122.209 [53029.876244] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:47:59 192.168.122.209 [53029.916220] [tempesta fw] Tempesta FW is ready Apr 26 06:48:00 192.168.122.209 [53030.492806] [tdb] Close table 'client0.tdb' Apr 26 06:48:00 192.168.122.209 [53030.689012] [tdb] Close table 'sessions0.tdb' Apr 26 06:48:03 192.168.122.209 [53033.901503] [tdb] Close table 'cache0.tdb' Apr 26 06:48:03 192.168.122.209 [53034.154035] [tdb] Close table 'filter0.tdb' Apr 26 06:48:03 192.168.122.209 [53034.154461] [tempesta fw] modules are stopped Apr 26 06:48:03 192.168.122.209 [53034.345930] [tempesta fw] exiting... Apr 26 06:48:04 192.168.122.209 [53034.495450] [tdb] Shutdown Tempesta DB Apr 26 06:48:04 192.168.122.209 [53034.757915] End test: tls.test_tls_alpn_basic.TestALPN.test_proto_order_h2 Apr 26 06:48:04 192.168.122.209 [53034.769489] Start test: tls.test_tls_alpn_basic.TestALPN.test_proto_mixed_https Apr 26 06:48:05 192.168.122.209 [53035.916650] [tdb] Start Tempesta DB Apr 26 06:48:05 192.168.122.209 [53036.063525] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:48:07 192.168.122.209 [53037.538134] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [53037.538134] Maybe that's fine, but it's worth checking the [53037.538134] config - if there is no relations between the [53037.538134] names, then host name confusion attack is possible. Apr 26 06:48:07 192.168.122.209 [53037.596340] [tempesta fw] Configuration processing is completed. Apr 26 06:48:07 192.168.122.209 [53037.650935] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:48:07 192.168.122.209 [53038.115543] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:48:07 192.168.122.209 [53038.144987] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:48:07 192.168.122.209 [53038.173391] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:48:07 192.168.122.209 [53038.252368] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:48:07 192.168.122.209 [53038.292308] [tempesta fw] Tempesta FW is ready Apr 26 06:48:08 192.168.122.209 [53038.903848] [tdb] Close table 'client0.tdb' Apr 26 06:48:08 192.168.122.209 [53039.091599] [tdb] Close table 'sessions0.tdb' Apr 26 06:48:11 192.168.122.209 [53042.301205] [tdb] Close table 'cache0.tdb' Apr 26 06:48:12 192.168.122.209 [53042.540334] [tdb] Close table 'filter0.tdb' Apr 26 06:48:12 192.168.122.209 [53042.540774] [tempesta fw] modules are stopped Apr 26 06:48:12 192.168.122.209 [53042.750046] [tempesta fw] exiting... Apr 26 06:48:12 192.168.122.209 [53042.918562] [tdb] Shutdown Tempesta DB Apr 26 06:48:12 192.168.122.209 [53043.107910] End test: tls.test_tls_alpn_basic.TestALPN.test_proto_mixed_https Apr 26 06:48:12 192.168.122.209 [53043.135273] Start test: tls.test_tls_alpn_basic.TestALPN.test_proto_mixed_h2_only Apr 26 06:48:13 192.168.122.209 [53044.192772] [tdb] Start Tempesta DB Apr 26 06:48:13 192.168.122.209 [53044.356422] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:48:15 192.168.122.209 [53045.802213] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [53045.802213] Maybe that's fine, but it's worth checking the [53045.802213] config - if there is no relations between the [53045.802213] names, then host name confusion attack is possible. Apr 26 06:48:15 192.168.122.209 [53045.848800] [tempesta fw] Configuration processing is completed. Apr 26 06:48:15 192.168.122.209 [53045.906925] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:48:15 192.168.122.209 [53046.327388] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:48:15 192.168.122.209 [53046.354317] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:48:15 192.168.122.209 [53046.382003] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:48:15 192.168.122.209 [53046.440431] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:48:16 192.168.122.209 [53046.480432] [tempesta fw] Tempesta FW is ready Apr 26 06:48:16 192.168.122.209 [53047.125535] [tdb] Close table 'client0.tdb' Apr 26 06:48:16 192.168.122.209 [53047.311373] [tdb] Close table 'sessions0.tdb' Apr 26 06:48:19 192.168.122.209 [53050.452379] [tdb] Close table 'cache0.tdb' Apr 26 06:48:20 192.168.122.209 [53050.712419] [tdb] Close table 'filter0.tdb' Apr 26 06:48:20 192.168.122.209 [53050.712855] [tempesta fw] modules are stopped Apr 26 06:48:20 192.168.122.209 [53050.918085] [tempesta fw] exiting... Apr 26 06:48:20 192.168.122.209 [53051.034289] [tdb] Shutdown Tempesta DB Apr 26 06:48:20 192.168.122.209 [53051.233909] End test: tls.test_tls_alpn_basic.TestALPN.test_proto_mixed_h2_only Apr 26 06:48:20 192.168.122.209 [53051.258194] Start test: tls.test_tls_alpn_basic.TestALPN.test_proto_mixed_h2_https Apr 26 06:48:21 192.168.122.209 [53052.355459] [tdb] Start Tempesta DB Apr 26 06:48:22 192.168.122.209 [53052.493075] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:48:23 192.168.122.209 [53053.986341] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [53053.986341] Maybe that's fine, but it's worth checking the [53053.986341] config - if there is no relations between the [53053.986341] names, then host name confusion attack is possible. Apr 26 06:48:23 192.168.122.209 [53054.056471] [tempesta fw] Configuration processing is completed. Apr 26 06:48:23 192.168.122.209 [53054.107826] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:48:24 192.168.122.209 [53054.531200] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:48:24 192.168.122.209 [53054.567065] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:48:24 192.168.122.209 [53054.593133] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:48:24 192.168.122.209 [53054.668533] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:48:24 192.168.122.209 [53054.712482] [tempesta fw] Tempesta FW is ready Apr 26 06:48:24 192.168.122.209 [53055.332907] [tdb] Close table 'client0.tdb' Apr 26 06:48:25 192.168.122.209 [53055.509504] [tdb] Close table 'sessions0.tdb' Apr 26 06:48:28 192.168.122.209 [53058.799540] [tdb] Close table 'cache0.tdb' Apr 26 06:48:28 192.168.122.209 [53059.039474] [tdb] Close table 'filter0.tdb' Apr 26 06:48:28 192.168.122.209 [53059.039897] [tempesta fw] modules are stopped Apr 26 06:48:28 192.168.122.209 [53059.236939] [tempesta fw] exiting... Apr 26 06:48:28 192.168.122.209 [53059.350715] [tdb] Shutdown Tempesta DB Apr 26 06:48:29 192.168.122.209 [53059.561326] End test: tls.test_tls_alpn_basic.TestALPN.test_proto_mixed_h2_https Apr 26 06:48:29 192.168.122.209 [53059.572891] Start test: tls.test_tls_alpn_basic.TestALPN.test_negative_https Apr 26 06:48:30 192.168.122.209 [53060.693768] [tdb] Start Tempesta DB Apr 26 06:48:30 192.168.122.209 [53060.849780] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:48:31 192.168.122.209 [53062.254418] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [53062.254418] Maybe that's fine, but it's worth checking the [53062.254418] config - if there is no relations between the [53062.254418] names, then host name confusion attack is possible. Apr 26 06:48:31 192.168.122.209 [53062.312611] [tempesta fw] Configuration processing is completed. Apr 26 06:48:31 192.168.122.209 [53062.370693] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:48:32 192.168.122.209 [53062.831776] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:48:32 192.168.122.209 [53062.860526] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:48:32 192.168.122.209 [53062.890063] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:48:32 192.168.122.209 [53062.956657] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:48:32 192.168.122.209 [53063.000594] [tempesta fw] Tempesta FW is ready Apr 26 06:48:32 192.168.122.209 [53063.155988] [tempesta tls] Warning: [::ffff:127.0.0.1] ClientHello: cannot find matching ALPN for h2 Apr 26 06:48:33 192.168.122.209 [53063.663359] [tdb] Close table 'client0.tdb' Apr 26 06:48:33 192.168.122.209 [53063.859724] [tdb] Close table 'sessions0.tdb' Apr 26 06:48:36 192.168.122.209 [53067.130095] [tdb] Close table 'cache0.tdb' Apr 26 06:48:36 192.168.122.209 [53067.373450] [tdb] Close table 'filter0.tdb' Apr 26 06:48:36 192.168.122.209 [53067.373891] [tempesta fw] modules are stopped Apr 26 06:48:37 192.168.122.209 [53067.578145] [tempesta fw] exiting... Apr 26 06:48:37 192.168.122.209 [53067.704261] [tdb] Shutdown Tempesta DB Apr 26 06:48:37 192.168.122.209 [53067.946914] End test: tls.test_tls_alpn_basic.TestALPN.test_negative_https Apr 26 06:48:37 192.168.122.209 [53067.964259] Start test: tls.test_tls_alpn_basic.TestALPN.test_negative_h2 Apr 26 06:48:38 192.168.122.209 [53069.095101] [tdb] Start Tempesta DB Apr 26 06:48:38 192.168.122.209 [53069.239862] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:48:40 192.168.122.209 [53070.706392] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [53070.706392] Maybe that's fine, but it's worth checking the [53070.706392] config - if there is no relations between the [53070.706392] names, then host name confusion attack is possible. Apr 26 06:48:40 192.168.122.209 [53070.768695] [tempesta fw] Configuration processing is completed. Apr 26 06:48:40 192.168.122.209 [53070.817818] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:48:40 192.168.122.209 [53071.248177] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:48:40 192.168.122.209 [53071.281778] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:48:40 192.168.122.209 [53071.310605] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:48:40 192.168.122.209 [53071.384740] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:48:40 192.168.122.209 [53071.444698] [tempesta fw] Tempesta FW is ready Apr 26 06:48:41 192.168.122.209 [53071.604743] [tempesta tls] Warning: [::ffff:127.0.0.1] ClientHello: cannot find matching ALPN for http/1.1 Apr 26 06:48:41 192.168.122.209 [53072.125677] [tdb] Close table 'client0.tdb' Apr 26 06:48:41 192.168.122.209 [53072.315920] [tdb] Close table 'sessions0.tdb' Apr 26 06:48:45 192.168.122.209 [53075.593457] [tdb] Close table 'cache0.tdb' Apr 26 06:48:45 192.168.122.209 [53075.836474] [tdb] Close table 'filter0.tdb' Apr 26 06:48:45 192.168.122.209 [53075.836911] [tempesta fw] modules are stopped Apr 26 06:48:45 192.168.122.209 [53076.049393] [tempesta fw] exiting... Apr 26 06:48:45 192.168.122.209 [53076.175492] [tdb] Shutdown Tempesta DB Apr 26 06:48:45 192.168.122.209 [53076.403769] End test: tls.test_tls_alpn_basic.TestALPN.test_negative_h2 Apr 26 06:48:45 192.168.122.209 [53076.421269] Start test: tls.test_tls_alpn_basic.TestALPN.test_alpn_default Apr 26 06:48:46 192.168.122.209 [53077.451970] [tdb] Start Tempesta DB Apr 26 06:48:47 192.168.122.209 [53077.597946] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:48:48 192.168.122.209 [53079.033887] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [53079.033887] Maybe that's fine, but it's worth checking the [53079.033887] config - if there is no relations between the [53079.033887] names, then host name confusion attack is possible. Apr 26 06:48:48 192.168.122.209 [53079.073039] [tempesta fw] Configuration processing is completed. Apr 26 06:48:48 192.168.122.209 [53079.130802] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:48:49 192.168.122.209 [53079.544004] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:48:49 192.168.122.209 [53079.571253] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:48:49 192.168.122.209 [53079.598152] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:48:49 192.168.122.209 [53079.640789] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:48:49 192.168.122.209 [53079.680809] [tempesta fw] Tempesta FW is ready Apr 26 06:48:49 192.168.122.209 [53080.313344] [tdb] Close table 'client0.tdb' Apr 26 06:48:50 192.168.122.209 [53080.490392] [tdb] Close table 'sessions0.tdb' Apr 26 06:48:53 192.168.122.209 [53083.744271] [tdb] Close table 'cache0.tdb' Apr 26 06:48:53 192.168.122.209 [53083.981709] [tdb] Close table 'filter0.tdb' Apr 26 06:48:53 192.168.122.209 [53083.982166] [tempesta fw] modules are stopped Apr 26 06:48:53 192.168.122.209 [53084.186179] [tempesta fw] exiting... Apr 26 06:48:53 192.168.122.209 [53084.298192] [tdb] Shutdown Tempesta DB Apr 26 06:48:54 192.168.122.209 [53084.510704] End test: tls.test_tls_alpn_basic.TestALPN.test_alpn_default Apr 26 06:48:54 192.168.122.209 [53084.538039] Start test: cache.test_cache.TestCacheAgeInResponseH2.test Apr 26 06:48:55 192.168.122.209 [53085.606545] [tdb] Start Tempesta DB Apr 26 06:48:55 192.168.122.209 [53085.758086] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:48:56 192.168.122.209 [53087.189604] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53087.189604] Maybe that's fine, but it's worth checking the [53087.189604] config - if there is no relations between the [53087.189604] names, then host name confusion attack is possible. Apr 26 06:48:56 192.168.122.209 [53087.268919] [tempesta fw] Configuration processing is completed. Apr 26 06:48:56 192.168.122.209 [53087.321509] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:48:57 192.168.122.209 [53087.751175] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:48:57 192.168.122.209 [53087.777581] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:48:57 192.168.122.209 [53087.803603] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:48:57 192.168.122.209 [53087.844987] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:48:57 192.168.122.209 [53087.846677] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:48:57 192.168.122.209 [53087.900903] [tempesta fw] Tempesta FW is ready Apr 26 06:48:58 192.168.122.209 [53088.558573] [tdb] Close table 'client0.tdb' Apr 26 06:48:58 192.168.122.209 [53088.766043] [tdb] Close table 'sessions0.tdb' Apr 26 06:49:01 192.168.122.209 [53091.956822] [tdb] Close table 'cache0.tdb' Apr 26 06:49:01 192.168.122.209 [53092.250896] [tdb] Close table 'filter0.tdb' Apr 26 06:49:01 192.168.122.209 [53092.251542] [tempesta fw] modules are stopped Apr 26 06:49:01 192.168.122.209 [53092.465859] [tempesta fw] exiting... Apr 26 06:49:02 192.168.122.209 [53092.575572] [tdb] Shutdown Tempesta DB Apr 26 06:49:02 192.168.122.209 [53092.800742] End test: cache.test_cache.TestCacheAgeInResponseH2.test Apr 26 06:49:02 192.168.122.209 [53092.824297] Start test: cache.test_cache.TestCacheAgeInResponseHttp.test Apr 26 06:49:03 192.168.122.209 [53093.870065] [tdb] Start Tempesta DB Apr 26 06:49:03 192.168.122.209 [53094.007296] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:49:04 192.168.122.209 [53095.426312] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53095.426312] Maybe that's fine, but it's worth checking the [53095.426312] config - if there is no relations between the [53095.426312] names, then host name confusion attack is possible. Apr 26 06:49:05 192.168.122.209 [53095.509085] [tempesta fw] Configuration processing is completed. Apr 26 06:49:05 192.168.122.209 [53095.568247] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:49:05 192.168.122.209 [53095.978996] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:49:05 192.168.122.209 [53096.005018] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:49:05 192.168.122.209 [53096.031670] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:49:05 192.168.122.209 [53096.073001] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:49:05 192.168.122.209 [53096.074540] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:49:05 192.168.122.209 [53096.124999] [tempesta fw] Tempesta FW is ready Apr 26 06:49:06 192.168.122.209 [53096.724695] [tdb] Close table 'client0.tdb' Apr 26 06:49:06 192.168.122.209 [53096.911170] [tdb] Close table 'sessions0.tdb' Apr 26 06:49:09 192.168.122.209 [53100.120418] [tdb] Close table 'cache0.tdb' Apr 26 06:49:09 192.168.122.209 [53100.343833] [tdb] Close table 'filter0.tdb' Apr 26 06:49:09 192.168.122.209 [53100.344258] [tempesta fw] modules are stopped Apr 26 06:49:10 192.168.122.209 [53100.533379] [tempesta fw] exiting... Apr 26 06:49:10 192.168.122.209 [53100.674994] [tdb] Shutdown Tempesta DB Apr 26 06:49:10 192.168.122.209 [53100.902403] End test: cache.test_cache.TestCacheAgeInResponseHttp.test Apr 26 06:49:10 192.168.122.209 [53100.915966] Start test: cache.test_cache.TestCacheClean.test Apr 26 06:49:11 192.168.122.209 [53101.986288] [tdb] Start Tempesta DB Apr 26 06:49:11 192.168.122.209 [53102.123331] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:49:13 192.168.122.209 [53103.722297] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [53103.722297] Maybe that's fine, but it's worth checking the [53103.722297] config - if there is no relations between the [53103.722297] names, then host name confusion attack is possible. Apr 26 06:49:13 192.168.122.209 [53103.817198] [tempesta fw] Configuration processing is completed. Apr 26 06:49:13 192.168.122.209 [53103.873592] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:49:13 192.168.122.209 [53104.303681] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:49:13 192.168.122.209 [53104.329485] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:49:13 192.168.122.209 [53104.355566] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:49:13 192.168.122.209 [53104.417165] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:49:13 192.168.122.209 [53104.461120] [tempesta fw] Tempesta FW is ready Apr 26 06:49:17 192.168.122.209 [53108.173983] [tdb] Close table 'client0.tdb' Apr 26 06:49:17 192.168.122.209 [53108.356515] [tdb] Close table 'sessions0.tdb' Apr 26 06:49:21 192.168.122.209 [53111.568685] [tdb] Close table 'cache0.tdb' Apr 26 06:49:21 192.168.122.209 [53111.803921] [tdb] Close table 'filter0.tdb' Apr 26 06:49:21 192.168.122.209 [53111.804369] [tempesta fw] modules are stopped Apr 26 06:49:21 192.168.122.209 [53112.050366] [tempesta fw] exiting... Apr 26 06:49:21 192.168.122.209 [53112.183139] [tdb] Shutdown Tempesta DB Apr 26 06:49:21 192.168.122.209 [53112.396764] End test: cache.test_cache.TestCacheClean.test Apr 26 06:49:21 192.168.122.209 [53112.407489] Start test: cache.test_cache.TestCacheDockerH2Body.test Apr 26 06:49:24 192.168.122.209 [53115.427745] docker0: port 1(vethf46f535) entered blocking state Apr 26 06:49:24 192.168.122.209 [53115.428365] docker0: port 1(vethf46f535) entered disabled state Apr 26 06:49:24 192.168.122.209 [53115.430775] device vethf46f535 entered promiscuous mode Apr 26 06:49:25 192.168.122.209 [53116.239982] eth0: renamed from veth5207ea7 Apr 26 06:49:25 192.168.122.209 [53116.264552] IPv6: ADDRCONF(NETDEV_CHANGE): vethf46f535: link becomes ready Apr 26 06:49:25 192.168.122.209 [53116.265926] docker0: port 1(vethf46f535) entered blocking state Apr 26 06:49:25 192.168.122.209 [53116.266658] docker0: port 1(vethf46f535) entered forwarding state Apr 26 06:49:26 192.168.122.209 [53117.320193] [tdb] Start Tempesta DB Apr 26 06:49:26 192.168.122.209 [53117.468567] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:49:28 192.168.122.209 [53118.862731] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53118.862731] Maybe that's fine, but it's worth checking the [53118.862731] config - if there is no relations between the [53118.862731] names, then host name confusion attack is possible. Apr 26 06:49:28 192.168.122.209 [53118.989410] [tempesta fw] Configuration processing is completed. Apr 26 06:49:28 192.168.122.209 [53119.050843] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:49:29 192.168.122.209 [53119.498664] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:49:29 192.168.122.209 [53119.525605] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:49:29 192.168.122.209 [53119.553929] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:49:29 192.168.122.209 [53119.641412] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:49:29 192.168.122.209 [53119.643115] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:49:29 192.168.122.209 [53119.701333] [tempesta fw] Tempesta FW is ready Apr 26 06:49:30 192.168.122.209 [53120.707301] [tdb] Close table 'client0.tdb' Apr 26 06:49:30 192.168.122.209 [53120.992323] [tdb] Close table 'sessions0.tdb' Apr 26 06:49:33 192.168.122.209 [53124.265811] [tdb] Close table 'cache0.tdb' Apr 26 06:49:34 192.168.122.209 [53124.488432] [tdb] Close table 'filter0.tdb' Apr 26 06:49:34 192.168.122.209 [53124.488873] [tempesta fw] modules are stopped Apr 26 06:49:34 192.168.122.209 [53124.702238] [tempesta fw] exiting... Apr 26 06:49:34 192.168.122.209 [53124.812920] [tdb] Shutdown Tempesta DB Apr 26 06:49:34 192.168.122.209 [53125.293549] docker0: port 1(vethf46f535) entered disabled state Apr 26 06:49:34 192.168.122.209 [53125.294294] veth5207ea7: renamed from eth0 Apr 26 06:49:34 192.168.122.209 [53125.348324] docker0: port 1(vethf46f535) entered disabled state Apr 26 06:49:34 192.168.122.209 [53125.352945] device vethf46f535 left promiscuous mode Apr 26 06:49:34 192.168.122.209 [53125.353602] docker0: port 1(vethf46f535) entered disabled state Apr 26 06:49:35 192.168.122.209 [53125.686636] End test: cache.test_cache.TestCacheDockerH2Body.test Apr 26 06:49:35 192.168.122.209 [53125.705069] Start test: cache.test_cache.TestCacheDockerH2Headers.test Apr 26 06:49:36 192.168.122.209 [53127.155056] docker0: port 1(veth2a518b5) entered blocking state Apr 26 06:49:36 192.168.122.209 [53127.156849] docker0: port 1(veth2a518b5) entered disabled state Apr 26 06:49:36 192.168.122.209 [53127.162189] device veth2a518b5 entered promiscuous mode Apr 26 06:49:36 192.168.122.209 [53127.166294] docker0: port 1(veth2a518b5) entered blocking state Apr 26 06:49:36 192.168.122.209 [53127.167549] docker0: port 1(veth2a518b5) entered forwarding state Apr 26 06:49:36 192.168.122.209 [53127.168872] docker0: port 1(veth2a518b5) entered disabled state Apr 26 06:49:37 192.168.122.209 [53127.679119] eth0: renamed from veth96bac0d Apr 26 06:49:37 192.168.122.209 [53127.704554] IPv6: ADDRCONF(NETDEV_CHANGE): veth2a518b5: link becomes ready Apr 26 06:49:37 192.168.122.209 [53127.706619] docker0: port 1(veth2a518b5) entered blocking state Apr 26 06:49:37 192.168.122.209 [53127.707728] docker0: port 1(veth2a518b5) entered forwarding state Apr 26 06:49:38 192.168.122.209 [53128.788960] [tdb] Start Tempesta DB Apr 26 06:49:38 192.168.122.209 [53128.938625] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:49:39 192.168.122.209 [53130.310888] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53130.310888] Maybe that's fine, but it's worth checking the [53130.310888] config - if there is no relations between the [53130.310888] names, then host name confusion attack is possible. Apr 26 06:49:39 192.168.122.209 [53130.413536] [tempesta fw] Configuration processing is completed. Apr 26 06:49:39 192.168.122.209 [53130.465325] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:49:40 192.168.122.209 [53130.926152] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:49:40 192.168.122.209 [53130.955159] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:49:40 192.168.122.209 [53130.984794] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:49:40 192.168.122.209 [53131.069591] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:49:40 192.168.122.209 [53131.070675] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:49:40 192.168.122.209 [53131.113437] [tempesta fw] Tempesta FW is ready Apr 26 06:49:41 192.168.122.209 [53131.991445] [tdb] Close table 'client0.tdb' Apr 26 06:49:41 192.168.122.209 [53132.189227] [tdb] Close table 'sessions0.tdb' Apr 26 06:49:45 192.168.122.209 [53135.489073] [tdb] Close table 'cache0.tdb' Apr 26 06:49:45 192.168.122.209 [53135.747308] [tdb] Close table 'filter0.tdb' Apr 26 06:49:45 192.168.122.209 [53135.747767] [tempesta fw] modules are stopped Apr 26 06:49:45 192.168.122.209 [53135.980673] [tempesta fw] exiting... Apr 26 06:49:45 192.168.122.209 [53136.080759] [tdb] Shutdown Tempesta DB Apr 26 06:49:46 192.168.122.209 [53136.562817] docker0: port 1(veth2a518b5) entered disabled state Apr 26 06:49:46 192.168.122.209 [53136.563546] veth96bac0d: renamed from eth0 Apr 26 06:49:46 192.168.122.209 [53136.627532] docker0: port 1(veth2a518b5) entered disabled state Apr 26 06:49:46 192.168.122.209 [53136.632664] device veth2a518b5 left promiscuous mode Apr 26 06:49:46 192.168.122.209 [53136.633192] docker0: port 1(veth2a518b5) entered disabled state Apr 26 06:49:46 192.168.122.209 [53136.972500] End test: cache.test_cache.TestCacheDockerH2Headers.test Apr 26 06:49:46 192.168.122.209 [53136.993646] Start test: cache.test_cache.TestCacheDockerHttpBody.test Apr 26 06:49:48 192.168.122.209 [53138.628742] docker0: port 1(vethc548b9c) entered blocking state Apr 26 06:49:48 192.168.122.209 [53138.629570] docker0: port 1(vethc548b9c) entered disabled state Apr 26 06:49:48 192.168.122.209 [53138.631976] device vethc548b9c entered promiscuous mode Apr 26 06:49:48 192.168.122.209 [53139.171179] eth0: renamed from veth5a05131 Apr 26 06:49:48 192.168.122.209 [53139.203457] IPv6: ADDRCONF(NETDEV_CHANGE): vethc548b9c: link becomes ready Apr 26 06:49:48 192.168.122.209 [53139.205436] docker0: port 1(vethc548b9c) entered blocking state Apr 26 06:49:48 192.168.122.209 [53139.206511] docker0: port 1(vethc548b9c) entered forwarding state Apr 26 06:49:49 192.168.122.209 [53140.340631] [tdb] Start Tempesta DB Apr 26 06:49:50 192.168.122.209 [53140.512859] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:49:51 192.168.122.209 [53141.959075] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53141.959075] Maybe that's fine, but it's worth checking the [53141.959075] config - if there is no relations between the [53141.959075] names, then host name confusion attack is possible. Apr 26 06:49:51 192.168.122.209 [53142.069843] [tempesta fw] Configuration processing is completed. Apr 26 06:49:51 192.168.122.209 [53142.121610] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:49:52 192.168.122.209 [53142.677966] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:49:52 192.168.122.209 [53142.716314] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:49:52 192.168.122.209 [53142.753290] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:49:52 192.168.122.209 [53142.837659] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:49:52 192.168.122.209 [53142.839429] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:49:52 192.168.122.209 [53142.893512] [tempesta fw] Tempesta FW is ready Apr 26 06:49:53 192.168.122.209 [53143.677811] [tdb] Close table 'client0.tdb' Apr 26 06:49:53 192.168.122.209 [53143.870104] [tdb] Close table 'sessions0.tdb' Apr 26 06:49:56 192.168.122.209 [53147.255153] [tdb] Close table 'cache0.tdb' Apr 26 06:49:57 192.168.122.209 [53147.543617] [tdb] Close table 'filter0.tdb' Apr 26 06:49:57 192.168.122.209 [53147.544105] [tempesta fw] modules are stopped Apr 26 06:49:57 192.168.122.209 [53147.818040] [tempesta fw] exiting... Apr 26 06:49:57 192.168.122.209 [53147.952740] [tdb] Shutdown Tempesta DB Apr 26 06:49:57 192.168.122.209 [53148.454154] docker0: port 1(vethc548b9c) entered disabled state Apr 26 06:49:57 192.168.122.209 [53148.454932] veth5a05131: renamed from eth0 Apr 26 06:49:58 192.168.122.209 [53148.514270] docker0: port 1(vethc548b9c) entered disabled state Apr 26 06:49:58 192.168.122.209 [53148.517455] device vethc548b9c left promiscuous mode Apr 26 06:49:58 192.168.122.209 [53148.518018] docker0: port 1(vethc548b9c) entered disabled state Apr 26 06:49:58 192.168.122.209 [53148.842737] End test: cache.test_cache.TestCacheDockerHttpBody.test Apr 26 06:49:58 192.168.122.209 [53148.852166] Start test: cache.test_cache.TestCacheDockerHttpHeaders.test Apr 26 06:49:59 192.168.122.209 [53150.230439] docker0: port 1(veth1530d94) entered blocking state Apr 26 06:49:59 192.168.122.209 [53150.231988] docker0: port 1(veth1530d94) entered disabled state Apr 26 06:49:59 192.168.122.209 [53150.237512] device veth1530d94 entered promiscuous mode Apr 26 06:49:59 192.168.122.209 [53150.239896] docker0: port 1(veth1530d94) entered blocking state Apr 26 06:49:59 192.168.122.209 [53150.240835] docker0: port 1(veth1530d94) entered forwarding state Apr 26 06:49:59 192.168.122.209 [53150.243019] docker0: port 1(veth1530d94) entered disabled state Apr 26 06:50:00 192.168.122.209 [53150.772023] eth0: renamed from veth38892e4 Apr 26 06:50:00 192.168.122.209 [53150.795836] IPv6: ADDRCONF(NETDEV_CHANGE): veth1530d94: link becomes ready Apr 26 06:50:00 192.168.122.209 [53150.797102] docker0: port 1(veth1530d94) entered blocking state Apr 26 06:50:00 192.168.122.209 [53150.797801] docker0: port 1(veth1530d94) entered forwarding state Apr 26 06:50:01 192.168.122.209 [53151.934357] [tdb] Start Tempesta DB Apr 26 06:50:01 192.168.122.209 [53152.091668] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:50:03 192.168.122.209 [53153.483301] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53153.483301] Maybe that's fine, but it's worth checking the [53153.483301] config - if there is no relations between the [53153.483301] names, then host name confusion attack is possible. Apr 26 06:50:03 192.168.122.209 [53153.597844] [tempesta fw] Configuration processing is completed. Apr 26 06:50:03 192.168.122.209 [53153.648600] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:50:03 192.168.122.209 [53154.089286] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:50:03 192.168.122.209 [53154.117009] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:50:03 192.168.122.209 [53154.146069] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:50:03 192.168.122.209 [53154.213641] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:50:03 192.168.122.209 [53154.214664] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:50:03 192.168.122.209 [53154.281636] [tempesta fw] Tempesta FW is ready Apr 26 06:50:04 192.168.122.209 [53155.155852] [tdb] Close table 'client0.tdb' Apr 26 06:50:04 192.168.122.209 [53155.353746] [tdb] Close table 'sessions0.tdb' Apr 26 06:50:08 192.168.122.209 [53158.587397] [tdb] Close table 'cache0.tdb' Apr 26 06:50:08 192.168.122.209 [53158.854496] [tdb] Close table 'filter0.tdb' Apr 26 06:50:08 192.168.122.209 [53158.854936] [tempesta fw] modules are stopped Apr 26 06:50:08 192.168.122.209 [53159.065294] [tempesta fw] exiting... Apr 26 06:50:08 192.168.122.209 [53159.164501] [tdb] Shutdown Tempesta DB Apr 26 06:50:09 192.168.122.209 [53159.664024] docker0: port 1(veth1530d94) entered disabled state Apr 26 06:50:09 192.168.122.209 [53159.664731] veth38892e4: renamed from eth0 Apr 26 06:50:09 192.168.122.209 [53159.722532] docker0: port 1(veth1530d94) entered disabled state Apr 26 06:50:09 192.168.122.209 [53159.726166] device veth1530d94 left promiscuous mode Apr 26 06:50:09 192.168.122.209 [53159.726674] docker0: port 1(veth1530d94) entered disabled state Apr 26 06:50:09 192.168.122.209 [53160.046949] End test: cache.test_cache.TestCacheDockerHttpHeaders.test Apr 26 06:50:09 192.168.122.209 [53160.060253] Start test: cache.test_cache.TestCacheDockerHttpsBody.test Apr 26 06:50:11 192.168.122.209 [53161.620695] docker0: port 1(veth5744ccf) entered blocking state Apr 26 06:50:11 192.168.122.209 [53161.621455] docker0: port 1(veth5744ccf) entered disabled state Apr 26 06:50:11 192.168.122.209 [53161.623957] device veth5744ccf entered promiscuous mode Apr 26 06:50:11 192.168.122.209 [53161.625328] docker0: port 1(veth5744ccf) entered blocking state Apr 26 06:50:11 192.168.122.209 [53161.626088] docker0: port 1(veth5744ccf) entered forwarding state Apr 26 06:50:11 192.168.122.209 [53161.627778] docker0: port 1(veth5744ccf) entered disabled state Apr 26 06:50:11 192.168.122.209 [53162.154876] eth0: renamed from veth98ad19b Apr 26 06:50:11 192.168.122.209 [53162.176522] IPv6: ADDRCONF(NETDEV_CHANGE): veth5744ccf: link becomes ready Apr 26 06:50:11 192.168.122.209 [53162.177628] docker0: port 1(veth5744ccf) entered blocking state Apr 26 06:50:11 192.168.122.209 [53162.178211] docker0: port 1(veth5744ccf) entered forwarding state Apr 26 06:50:12 192.168.122.209 [53163.215872] [tdb] Start Tempesta DB Apr 26 06:50:12 192.168.122.209 [53163.347616] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:50:14 192.168.122.209 [53164.631271] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53164.631271] Maybe that's fine, but it's worth checking the [53164.631271] config - if there is no relations between the [53164.631271] names, then host name confusion attack is possible. Apr 26 06:50:14 192.168.122.209 [53164.737948] [tempesta fw] Configuration processing is completed. Apr 26 06:50:14 192.168.122.209 [53164.787441] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:50:14 192.168.122.209 [53165.200210] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:50:14 192.168.122.209 [53165.232756] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:50:14 192.168.122.209 [53165.259576] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:50:14 192.168.122.209 [53165.337974] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:50:14 192.168.122.209 [53165.338839] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:50:14 192.168.122.209 [53165.373865] [tempesta fw] Tempesta FW is ready Apr 26 06:50:15 192.168.122.209 [53166.336803] [tdb] Close table 'client0.tdb' Apr 26 06:50:16 192.168.122.209 [53166.534873] [tdb] Close table 'sessions0.tdb' Apr 26 06:50:19 192.168.122.209 [53169.789196] [tdb] Close table 'cache0.tdb' Apr 26 06:50:19 192.168.122.209 [53170.044673] [tdb] Close table 'filter0.tdb' Apr 26 06:50:19 192.168.122.209 [53170.045111] [tempesta fw] modules are stopped Apr 26 06:50:19 192.168.122.209 [53170.233009] [tempesta fw] exiting... Apr 26 06:50:19 192.168.122.209 [53170.335860] [tdb] Shutdown Tempesta DB Apr 26 06:50:20 192.168.122.209 [53170.759253] docker0: port 1(veth5744ccf) entered disabled state Apr 26 06:50:20 192.168.122.209 [53170.759949] veth98ad19b: renamed from eth0 Apr 26 06:50:20 192.168.122.209 [53170.828660] docker0: port 1(veth5744ccf) entered disabled state Apr 26 06:50:20 192.168.122.209 [53170.841136] device veth5744ccf left promiscuous mode Apr 26 06:50:20 192.168.122.209 [53170.841643] docker0: port 1(veth5744ccf) entered disabled state Apr 26 06:50:20 192.168.122.209 [53171.143739] End test: cache.test_cache.TestCacheDockerHttpsBody.test Apr 26 06:50:20 192.168.122.209 [53171.152677] Start test: cache.test_cache.TestCacheDockerHttpsHeaders.test Apr 26 06:50:22 192.168.122.209 [53172.501013] docker0: port 1(veth00e1be2) entered blocking state Apr 26 06:50:22 192.168.122.209 [53172.501622] docker0: port 1(veth00e1be2) entered disabled state Apr 26 06:50:22 192.168.122.209 [53172.503785] device veth00e1be2 entered promiscuous mode Apr 26 06:50:22 192.168.122.209 [53172.505622] docker0: port 1(veth00e1be2) entered blocking state Apr 26 06:50:22 192.168.122.209 [53172.506297] docker0: port 1(veth00e1be2) entered forwarding state Apr 26 06:50:22 192.168.122.209 [53172.507897] docker0: port 1(veth00e1be2) entered disabled state Apr 26 06:50:22 192.168.122.209 [53173.007450] eth0: renamed from veth305f427 Apr 26 06:50:22 192.168.122.209 [53173.030772] IPv6: ADDRCONF(NETDEV_CHANGE): veth00e1be2: link becomes ready Apr 26 06:50:22 192.168.122.209 [53173.032797] docker0: port 1(veth00e1be2) entered blocking state Apr 26 06:50:22 192.168.122.209 [53173.033870] docker0: port 1(veth00e1be2) entered forwarding state Apr 26 06:50:23 192.168.122.209 [53174.035091] [tdb] Start Tempesta DB Apr 26 06:50:23 192.168.122.209 [53174.177808] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:50:25 192.168.122.209 [53175.547410] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53175.547410] Maybe that's fine, but it's worth checking the [53175.547410] config - if there is no relations between the [53175.547410] names, then host name confusion attack is possible. Apr 26 06:50:25 192.168.122.209 [53175.654116] [tempesta fw] Configuration processing is completed. Apr 26 06:50:25 192.168.122.209 [53175.704470] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:50:25 192.168.122.209 [53176.130296] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:50:25 192.168.122.209 [53176.156835] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:50:25 192.168.122.209 [53176.184633] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:50:25 192.168.122.209 [53176.278042] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:50:25 192.168.122.209 [53176.278869] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:50:25 192.168.122.209 [53176.330019] [tempesta fw] Tempesta FW is ready Apr 26 06:50:26 192.168.122.209 [53177.104729] [tdb] Close table 'client0.tdb' Apr 26 06:50:26 192.168.122.209 [53177.299900] [tdb] Close table 'sessions0.tdb' Apr 26 06:50:30 192.168.122.209 [53180.492679] [tdb] Close table 'cache0.tdb' Apr 26 06:50:30 192.168.122.209 [53180.733963] [tdb] Close table 'filter0.tdb' Apr 26 06:50:30 192.168.122.209 [53180.734397] [tempesta fw] modules are stopped Apr 26 06:50:30 192.168.122.209 [53181.056798] [tempesta fw] exiting... Apr 26 06:50:30 192.168.122.209 [53181.189426] [tdb] Shutdown Tempesta DB Apr 26 06:50:31 192.168.122.209 [53181.672266] docker0: port 1(veth00e1be2) entered disabled state Apr 26 06:50:31 192.168.122.209 [53181.672973] veth305f427: renamed from eth0 Apr 26 06:50:31 192.168.122.209 [53181.730232] docker0: port 1(veth00e1be2) entered disabled state Apr 26 06:50:31 192.168.122.209 [53181.740115] device veth00e1be2 left promiscuous mode Apr 26 06:50:31 192.168.122.209 [53181.740642] docker0: port 1(veth00e1be2) entered disabled state Apr 26 06:50:31 192.168.122.209 [53182.045876] End test: cache.test_cache.TestCacheDockerHttpsHeaders.test Apr 26 06:50:31 192.168.122.209 [53182.057625] Start test: cache.test_cache.TestCacheDublicateHeadersH2.test_raw Apr 26 06:50:32 192.168.122.209 [53183.161311] [tdb] Start Tempesta DB Apr 26 06:50:32 192.168.122.209 [53183.305659] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:50:34 192.168.122.209 [53184.687439] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53184.687439] Maybe that's fine, but it's worth checking the [53184.687439] config - if there is no relations between the [53184.687439] names, then host name confusion attack is possible. Apr 26 06:50:34 192.168.122.209 [53184.778187] [tempesta fw] Configuration processing is completed. Apr 26 06:50:34 192.168.122.209 [53184.828545] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:50:34 192.168.122.209 [53185.241998] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:50:34 192.168.122.209 [53185.267820] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:50:34 192.168.122.209 [53185.293321] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:50:34 192.168.122.209 [53185.354179] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:50:34 192.168.122.209 [53185.355918] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:50:34 192.168.122.209 [53185.394119] [tempesta fw] Tempesta FW is ready Apr 26 06:50:35 192.168.122.209 [53186.042843] [tdb] Close table 'client0.tdb' Apr 26 06:50:35 192.168.122.209 [53186.229396] [tdb] Close table 'sessions0.tdb' Apr 26 06:50:38 192.168.122.209 [53189.457306] [tdb] Close table 'cache0.tdb' Apr 26 06:50:39 192.168.122.209 [53189.691844] [tdb] Close table 'filter0.tdb' Apr 26 06:50:39 192.168.122.209 [53189.692282] [tempesta fw] modules are stopped Apr 26 06:50:40 192.168.122.209 [53191.048055] [tempesta fw] exiting... Apr 26 06:50:40 192.168.122.209 [53191.423649] [tdb] Shutdown Tempesta DB Apr 26 06:50:41 192.168.122.209 [53191.876394] End test: cache.test_cache.TestCacheDublicateHeadersH2.test_raw Apr 26 06:50:41 192.168.122.209 [53191.898489] Start test: cache.test_cache.TestCacheDublicateHeadersH2.test_regular Apr 26 06:50:42 192.168.122.209 [53193.157702] [tdb] Start Tempesta DB Apr 26 06:50:42 192.168.122.209 [53193.338463] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:50:45 192.168.122.209 [53195.896253] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53195.896253] Maybe that's fine, but it's worth checking the [53195.896253] config - if there is no relations between the [53195.896253] names, then host name confusion attack is possible. Apr 26 06:50:45 192.168.122.209 [53196.390277] [tempesta fw] Configuration processing is completed. Apr 26 06:50:46 192.168.122.209 [53196.488431] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:50:46 192.168.122.209 [53196.927669] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:50:46 192.168.122.209 [53196.954752] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:50:46 192.168.122.209 [53196.982910] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:50:46 192.168.122.209 [53197.022366] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:50:46 192.168.122.209 [53197.024098] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:50:46 192.168.122.209 [53197.078191] [tempesta fw] Tempesta FW is ready Apr 26 06:50:47 192.168.122.209 [53197.744672] [tdb] Close table 'client0.tdb' Apr 26 06:50:47 192.168.122.209 [53197.971496] [tdb] Close table 'sessions0.tdb' Apr 26 06:50:50 192.168.122.209 [53201.272314] [tdb] Close table 'cache0.tdb' Apr 26 06:50:51 192.168.122.209 [53201.496047] [tdb] Close table 'filter0.tdb' Apr 26 06:50:51 192.168.122.209 [53201.496498] [tempesta fw] modules are stopped Apr 26 06:50:51 192.168.122.209 [53201.673115] [tempesta fw] exiting... Apr 26 06:50:51 192.168.122.209 [53201.787691] [tdb] Shutdown Tempesta DB Apr 26 06:50:51 192.168.122.209 [53202.030613] End test: cache.test_cache.TestCacheDublicateHeadersH2.test_regular Apr 26 06:50:51 192.168.122.209 [53202.042959] Start test: cache.test_cache.TestCacheDublicateHeadersHttp.test_raw Apr 26 06:50:52 192.168.122.209 [53203.134602] [tdb] Start Tempesta DB Apr 26 06:50:52 192.168.122.209 [53203.275907] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:50:54 192.168.122.209 [53204.707732] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53204.707732] Maybe that's fine, but it's worth checking the [53204.707732] config - if there is no relations between the [53204.707732] names, then host name confusion attack is possible. Apr 26 06:50:54 192.168.122.209 [53204.798434] [tempesta fw] Configuration processing is completed. Apr 26 06:50:54 192.168.122.209 [53204.848951] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:50:54 192.168.122.209 [53205.268510] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:50:54 192.168.122.209 [53205.295081] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:50:54 192.168.122.209 [53205.321590] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:50:54 192.168.122.209 [53205.398435] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:50:54 192.168.122.209 [53205.400161] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:50:54 192.168.122.209 [53205.438407] [tempesta fw] Tempesta FW is ready Apr 26 06:50:55 192.168.122.209 [53206.056529] [tdb] Close table 'client0.tdb' Apr 26 06:50:55 192.168.122.209 [53206.242453] [tdb] Close table 'sessions0.tdb' Apr 26 06:50:58 192.168.122.209 [53209.468981] [tdb] Close table 'cache0.tdb' Apr 26 06:50:59 192.168.122.209 [53209.714822] [tdb] Close table 'filter0.tdb' Apr 26 06:50:59 192.168.122.209 [53209.715262] [tempesta fw] modules are stopped Apr 26 06:50:59 192.168.122.209 [53209.930469] [tempesta fw] exiting... Apr 26 06:50:59 192.168.122.209 [53210.081867] [tdb] Shutdown Tempesta DB Apr 26 06:50:59 192.168.122.209 [53210.326500] End test: cache.test_cache.TestCacheDublicateHeadersHttp.test_raw Apr 26 06:50:59 192.168.122.209 [53210.351790] Start test: cache.test_cache.TestCacheDublicateHeadersHttp.test_regular Apr 26 06:51:00 192.168.122.209 [53211.396163] [tdb] Start Tempesta DB Apr 26 06:51:01 192.168.122.209 [53211.532383] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:51:02 192.168.122.209 [53212.907787] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53212.907787] Maybe that's fine, but it's worth checking the [53212.907787] config - if there is no relations between the [53212.907787] names, then host name confusion attack is possible. Apr 26 06:51:02 192.168.122.209 [53213.006559] [tempesta fw] Configuration processing is completed. Apr 26 06:51:02 192.168.122.209 [53213.058068] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:51:03 192.168.122.209 [53213.483767] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:51:03 192.168.122.209 [53213.510642] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:51:03 192.168.122.209 [53213.538200] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:51:03 192.168.122.209 [53213.586532] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:51:03 192.168.122.209 [53213.588250] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:51:03 192.168.122.209 [53213.626487] [tempesta fw] Tempesta FW is ready Apr 26 06:51:03 192.168.122.209 [53214.271671] [tdb] Close table 'client0.tdb' Apr 26 06:51:03 192.168.122.209 [53214.455200] [tdb] Close table 'sessions0.tdb' Apr 26 06:51:07 192.168.122.209 [53217.636520] [tdb] Close table 'cache0.tdb' Apr 26 06:51:07 192.168.122.209 [53217.897297] [tdb] Close table 'filter0.tdb' Apr 26 06:51:07 192.168.122.209 [53217.897750] [tempesta fw] modules are stopped Apr 26 06:51:07 192.168.122.209 [53218.146491] [tempesta fw] exiting... Apr 26 06:51:07 192.168.122.209 [53218.270549] [tdb] Shutdown Tempesta DB Apr 26 06:51:08 192.168.122.209 [53218.494076] End test: cache.test_cache.TestCacheDublicateHeadersHttp.test_regular Apr 26 06:51:08 192.168.122.209 [53218.508055] Start test: cache.test_cache.TestCacheH2.test_cache_date Apr 26 06:51:09 192.168.122.209 [53219.589432] [tdb] Start Tempesta DB Apr 26 06:51:09 192.168.122.209 [53219.733075] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:51:10 192.168.122.209 [53221.203956] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53221.203956] Maybe that's fine, but it's worth checking the [53221.203956] config - if there is no relations between the [53221.203956] names, then host name confusion attack is possible. Apr 26 06:51:10 192.168.122.209 [53221.370640] [tempesta fw] Configuration processing is completed. Apr 26 06:51:10 192.168.122.209 [53221.430717] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:51:11 192.168.122.209 [53221.863104] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:51:11 192.168.122.209 [53221.889932] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:51:11 192.168.122.209 [53221.916171] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:51:11 192.168.122.209 [53221.966629] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:51:11 192.168.122.209 [53221.968134] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:51:11 192.168.122.209 [53222.010575] [tempesta fw] Tempesta FW is ready Apr 26 06:51:12 192.168.122.209 [53222.864827] [tdb] Close table 'client0.tdb' Apr 26 06:51:12 192.168.122.209 [53223.058603] [tdb] Close table 'sessions0.tdb' Apr 26 06:51:15 192.168.122.209 [53226.286111] [tdb] Close table 'cache0.tdb' Apr 26 06:51:16 192.168.122.209 [53226.532917] [tdb] Close table 'filter0.tdb' Apr 26 06:51:16 192.168.122.209 [53226.533368] [tempesta fw] modules are stopped Apr 26 06:51:16 192.168.122.209 [53226.743305] [tempesta fw] exiting... Apr 26 06:51:16 192.168.122.209 [53226.876910] [tdb] Shutdown Tempesta DB Apr 26 06:51:16 192.168.122.209 [53227.081125] End test: cache.test_cache.TestCacheH2.test_cache_date Apr 26 06:51:16 192.168.122.209 [53227.096668] Start test: cache.test_cache.TestCacheH2.test_disabled_cache_bypass_all Apr 26 06:51:17 192.168.122.209 [53228.225361] [tdb] Start Tempesta DB Apr 26 06:51:17 192.168.122.209 [53228.370976] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:51:19 192.168.122.209 [53229.771977] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53229.771977] Maybe that's fine, but it's worth checking the [53229.771977] config - if there is no relations between the [53229.771977] names, then host name confusion attack is possible. Apr 26 06:51:19 192.168.122.209 [53229.890768] [tempesta fw] Configuration processing is completed. Apr 26 06:51:19 192.168.122.209 [53229.943652] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:51:19 192.168.122.209 [53229.972716] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:51:19 192.168.122.209 [53230.001919] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:51:19 192.168.122.209 [53230.046732] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:51:19 192.168.122.209 [53230.048158] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:51:19 192.168.122.209 [53230.090687] [tempesta fw] Tempesta FW is ready Apr 26 06:51:20 192.168.122.209 [53231.117770] [tdb] Close table 'client0.tdb' Apr 26 06:51:20 192.168.122.209 [53231.317379] [tdb] Close table 'sessions0.tdb' Apr 26 06:51:21 192.168.122.209 [53231.549578] [tdb] Close table 'filter0.tdb' Apr 26 06:51:21 192.168.122.209 [53231.550023] [tempesta fw] modules are stopped Apr 26 06:51:21 192.168.122.209 [53231.760297] [tempesta fw] exiting... Apr 26 06:51:21 192.168.122.209 [53231.855877] [tdb] Shutdown Tempesta DB Apr 26 06:51:21 192.168.122.209 [53232.074999] End test: cache.test_cache.TestCacheH2.test_disabled_cache_bypass_all Apr 26 06:51:21 192.168.122.209 [53232.085500] Start test: cache.test_cache.TestCacheH2.test_disabled_cache_bypass_prefix Apr 26 06:51:22 192.168.122.209 [53233.126027] [tdb] Start Tempesta DB Apr 26 06:51:22 192.168.122.209 [53233.279467] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:51:23 192.168.122.209 [53234.008117] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53234.008117] Maybe that's fine, but it's worth checking the [53234.008117] config - if there is no relations between the [53234.008117] names, then host name confusion attack is possible. Apr 26 06:51:23 192.168.122.209 [53234.178818] [tempesta fw] Configuration processing is completed. Apr 26 06:51:23 192.168.122.209 [53234.234986] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:51:23 192.168.122.209 [53234.262798] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:51:23 192.168.122.209 [53234.291021] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:51:23 192.168.122.209 [53234.354792] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:51:23 192.168.122.209 [53234.356551] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:51:23 192.168.122.209 [53234.398734] [tempesta fw] Tempesta FW is ready Apr 26 06:51:24 192.168.122.209 [53235.451059] [tdb] Close table 'client0.tdb' Apr 26 06:51:25 192.168.122.209 [53235.632583] [tdb] Close table 'sessions0.tdb' Apr 26 06:51:25 192.168.122.209 [53235.928262] [tdb] Close table 'filter0.tdb' Apr 26 06:51:25 192.168.122.209 [53235.928903] [tempesta fw] modules are stopped Apr 26 06:51:25 192.168.122.209 [53236.128512] [tempesta fw] exiting... Apr 26 06:51:25 192.168.122.209 [53236.248247] [tdb] Shutdown Tempesta DB Apr 26 06:51:25 192.168.122.209 [53236.462301] End test: cache.test_cache.TestCacheH2.test_disabled_cache_bypass_prefix Apr 26 06:51:25 192.168.122.209 [53236.474171] Start test: cache.test_cache.TestCacheH2.test_disabled_cache_bypass_suffix Apr 26 06:51:27 192.168.122.209 [53237.577523] [tdb] Start Tempesta DB Apr 26 06:51:27 192.168.122.209 [53237.711450] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:51:27 192.168.122.209 [53238.452104] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53238.452104] Maybe that's fine, but it's worth checking the [53238.452104] config - if there is no relations between the [53238.452104] names, then host name confusion attack is possible. Apr 26 06:51:28 192.168.122.209 [53238.642883] [tempesta fw] Configuration processing is completed. Apr 26 06:51:28 192.168.122.209 [53238.695915] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:51:28 192.168.122.209 [53238.726786] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:51:28 192.168.122.209 [53238.755904] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:51:28 192.168.122.209 [53238.802846] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:51:28 192.168.122.209 [53238.804276] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:51:28 192.168.122.209 [53238.842812] [tempesta fw] Tempesta FW is ready Apr 26 06:51:29 192.168.122.209 [53239.872663] [tdb] Close table 'client0.tdb' Apr 26 06:51:29 192.168.122.209 [53240.089973] [tdb] Close table 'sessions0.tdb' Apr 26 06:51:29 192.168.122.209 [53240.312592] [tdb] Close table 'filter0.tdb' Apr 26 06:51:29 192.168.122.209 [53240.313037] [tempesta fw] modules are stopped Apr 26 06:51:30 192.168.122.209 [53240.536908] [tempesta fw] exiting... Apr 26 06:51:30 192.168.122.209 [53240.672987] [tdb] Shutdown Tempesta DB Apr 26 06:51:30 192.168.122.209 [53240.903169] End test: cache.test_cache.TestCacheH2.test_disabled_cache_bypass_suffix Apr 26 06:51:30 192.168.122.209 [53240.918646] Start test: cache.test_cache.TestCacheH2.test_disabled_cache_fulfill_all Apr 26 06:51:31 192.168.122.209 [53241.997243] [tdb] Start Tempesta DB Apr 26 06:51:31 192.168.122.209 [53242.135219] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:51:32 192.168.122.209 [53242.759815] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53242.759815] Maybe that's fine, but it's worth checking the [53242.759815] config - if there is no relations between the [53242.759815] names, then host name confusion attack is possible. Apr 26 06:51:32 192.168.122.209 [53242.870975] [tempesta fw] Configuration processing is completed. Apr 26 06:51:32 192.168.122.209 [53242.926059] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:51:32 192.168.122.209 [53242.954419] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:51:32 192.168.122.209 [53242.982472] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:51:32 192.168.122.209 [53243.018832] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:51:32 192.168.122.209 [53243.019873] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:51:32 192.168.122.209 [53243.058865] [tempesta fw] Tempesta FW is ready Apr 26 06:51:33 192.168.122.209 [53244.086161] [tdb] Close table 'client0.tdb' Apr 26 06:51:33 192.168.122.209 [53244.287189] [tdb] Close table 'sessions0.tdb' Apr 26 06:51:34 192.168.122.209 [53244.558272] [tdb] Close table 'filter0.tdb' Apr 26 06:51:34 192.168.122.209 [53244.558693] [tempesta fw] modules are stopped Apr 26 06:51:34 192.168.122.209 [53244.810991] [tempesta fw] exiting... Apr 26 06:51:34 192.168.122.209 [53244.958174] [tdb] Shutdown Tempesta DB Apr 26 06:51:34 192.168.122.209 [53245.199331] End test: cache.test_cache.TestCacheH2.test_disabled_cache_fulfill_all Apr 26 06:51:34 192.168.122.209 [53245.217063] Start test: cache.test_cache.TestCacheH2.test_disabled_cache_fulfill_prefix Apr 26 06:51:35 192.168.122.209 [53246.299781] [tdb] Start Tempesta DB Apr 26 06:51:35 192.168.122.209 [53246.447746] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:51:36 192.168.122.209 [53247.147583] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53247.147583] Maybe that's fine, but it's worth checking the [53247.147583] config - if there is no relations between the [53247.147583] names, then host name confusion attack is possible. Apr 26 06:51:36 192.168.122.209 [53247.318970] [tempesta fw] Configuration processing is completed. Apr 26 06:51:36 192.168.122.209 [53247.369459] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:51:36 192.168.122.209 [53247.399025] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:51:36 192.168.122.209 [53247.435026] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:51:36 192.168.122.209 [53247.470947] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:51:36 192.168.122.209 [53247.472685] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:51:37 192.168.122.209 [53247.518917] [tempesta fw] Tempesta FW is ready Apr 26 06:51:38 192.168.122.209 [53248.555982] [tdb] Close table 'client0.tdb' Apr 26 06:51:38 192.168.122.209 [53248.735899] [tdb] Close table 'sessions0.tdb' Apr 26 06:51:38 192.168.122.209 [53248.966027] [tdb] Close table 'filter0.tdb' Apr 26 06:51:38 192.168.122.209 [53248.966459] [tempesta fw] modules are stopped Apr 26 06:51:38 192.168.122.209 [53249.202515] [tempesta fw] exiting... Apr 26 06:51:38 192.168.122.209 [53249.334380] [tdb] Shutdown Tempesta DB Apr 26 06:51:39 192.168.122.209 [53249.573135] End test: cache.test_cache.TestCacheH2.test_disabled_cache_fulfill_prefix Apr 26 06:51:39 192.168.122.209 [53249.590010] Start test: cache.test_cache.TestCacheH2.test_disabled_cache_fulfill_suffix Apr 26 06:51:40 192.168.122.209 [53250.678668] [tdb] Start Tempesta DB Apr 26 06:51:40 192.168.122.209 [53250.829907] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:51:41 192.168.122.209 [53251.544308] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53251.544308] Maybe that's fine, but it's worth checking the [53251.544308] config - if there is no relations between the [53251.544308] names, then host name confusion attack is possible. Apr 26 06:51:41 192.168.122.209 [53251.719086] [tempesta fw] Configuration processing is completed. Apr 26 06:51:41 192.168.122.209 [53251.785800] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:51:41 192.168.122.209 [53251.813633] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:51:41 192.168.122.209 [53251.841545] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:51:41 192.168.122.209 [53251.899007] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:51:41 192.168.122.209 [53251.900627] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:51:41 192.168.122.209 [53251.946984] [tempesta fw] Tempesta FW is ready Apr 26 06:51:42 192.168.122.209 [53252.942196] [tdb] Close table 'client0.tdb' Apr 26 06:51:42 192.168.122.209 [53253.128949] [tdb] Close table 'sessions0.tdb' Apr 26 06:51:42 192.168.122.209 [53253.368497] [tdb] Close table 'filter0.tdb' Apr 26 06:51:42 192.168.122.209 [53253.368952] [tempesta fw] modules are stopped Apr 26 06:51:43 192.168.122.209 [53253.559574] [tempesta fw] exiting... Apr 26 06:51:43 192.168.122.209 [53253.716216] [tdb] Shutdown Tempesta DB Apr 26 06:51:43 192.168.122.209 [53253.959739] End test: cache.test_cache.TestCacheH2.test_disabled_cache_fulfill_suffix Apr 26 06:51:43 192.168.122.209 [53253.973617] Start test: cache.test_cache.TestCacheH2.test_disabled_cache_fulfill_suffix2 Apr 26 06:51:44 192.168.122.209 [53255.005001] [tdb] Start Tempesta DB Apr 26 06:51:44 192.168.122.209 [53255.145743] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:51:45 192.168.122.209 [53255.868354] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53255.868354] Maybe that's fine, but it's worth checking the [53255.868354] config - if there is no relations between the [53255.868354] names, then host name confusion attack is possible. Apr 26 06:51:45 192.168.122.209 [53256.043078] [tempesta fw] Configuration processing is completed. Apr 26 06:51:45 192.168.122.209 [53256.097899] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:51:45 192.168.122.209 [53256.125390] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:51:45 192.168.122.209 [53256.152868] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:51:45 192.168.122.209 [53256.207095] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:51:45 192.168.122.209 [53256.208840] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:51:45 192.168.122.209 [53256.255017] [tempesta fw] Tempesta FW is ready Apr 26 06:51:46 192.168.122.209 [53257.259595] [tdb] Close table 'client0.tdb' Apr 26 06:51:46 192.168.122.209 [53257.449079] [tdb] Close table 'sessions0.tdb' Apr 26 06:51:47 192.168.122.209 [53257.693919] [tdb] Close table 'filter0.tdb' Apr 26 06:51:47 192.168.122.209 [53257.694359] [tempesta fw] modules are stopped Apr 26 06:51:47 192.168.122.209 [53257.919441] [tempesta fw] exiting... Apr 26 06:51:47 192.168.122.209 [53258.065872] [tdb] Shutdown Tempesta DB Apr 26 06:51:47 192.168.122.209 [53258.318333] End test: cache.test_cache.TestCacheH2.test_disabled_cache_fulfill_suffix2 Apr 26 06:51:47 192.168.122.209 [53258.335806] Start test: cache.test_cache.TestCacheH2.test_replicated_cache_bypass_all Apr 26 06:51:48 192.168.122.209 [53259.424759] [tdb] Start Tempesta DB Apr 26 06:51:49 192.168.122.209 [53259.553507] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:51:49 192.168.122.209 [53260.176424] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53260.176424] Maybe that's fine, but it's worth checking the [53260.176424] config - if there is no relations between the [53260.176424] names, then host name confusion attack is possible. Apr 26 06:51:49 192.168.122.209 [53260.295051] [tempesta fw] Configuration processing is completed. Apr 26 06:51:49 192.168.122.209 [53260.347230] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:51:50 192.168.122.209 [53260.761823] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:51:50 192.168.122.209 [53260.788577] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:51:50 192.168.122.209 [53260.825653] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:51:50 192.168.122.209 [53260.883149] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:51:50 192.168.122.209 [53260.884896] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:51:50 192.168.122.209 [53260.947066] [tempesta fw] Tempesta FW is ready Apr 26 06:51:51 192.168.122.209 [53262.006173] [tdb] Close table 'client0.tdb' Apr 26 06:51:51 192.168.122.209 [53262.181968] [tdb] Close table 'sessions0.tdb' Apr 26 06:51:54 192.168.122.209 [53265.439980] [tdb] Close table 'cache0.tdb' Apr 26 06:51:55 192.168.122.209 [53265.655275] [tdb] Close table 'filter0.tdb' Apr 26 06:51:55 192.168.122.209 [53265.655716] [tempesta fw] modules are stopped Apr 26 06:51:55 192.168.122.209 [53265.879193] [tempesta fw] exiting... Apr 26 06:51:55 192.168.122.209 [53266.023042] [tdb] Shutdown Tempesta DB Apr 26 06:51:55 192.168.122.209 [53266.234593] End test: cache.test_cache.TestCacheH2.test_replicated_cache_bypass_all Apr 26 06:51:55 192.168.122.209 [53266.253609] Start test: cache.test_cache.TestCacheH2.test_replicated_cache_bypass_prefix Apr 26 06:51:56 192.168.122.209 [53267.325660] [tdb] Start Tempesta DB Apr 26 06:51:57 192.168.122.209 [53267.479959] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:51:58 192.168.122.209 [53268.900466] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53268.900466] Maybe that's fine, but it's worth checking the [53268.900466] config - if there is no relations between the [53268.900466] names, then host name confusion attack is possible. Apr 26 06:51:58 192.168.122.209 [53269.079299] [tempesta fw] Configuration processing is completed. Apr 26 06:51:58 192.168.122.209 [53269.141116] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:51:59 192.168.122.209 [53269.574936] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:51:59 192.168.122.209 [53269.600637] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:51:59 192.168.122.209 [53269.626469] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:51:59 192.168.122.209 [53269.663154] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:51:59 192.168.122.209 [53269.664094] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:51:59 192.168.122.209 [53269.703181] [tempesta fw] Tempesta FW is ready Apr 26 06:52:00 192.168.122.209 [53270.765276] [tdb] Close table 'client0.tdb' Apr 26 06:52:00 192.168.122.209 [53270.988255] [tdb] Close table 'sessions0.tdb' Apr 26 06:52:03 192.168.122.209 [53274.293843] [tdb] Close table 'cache0.tdb' Apr 26 06:52:04 192.168.122.209 [53274.536092] [tdb] Close table 'filter0.tdb' Apr 26 06:52:04 192.168.122.209 [53274.536539] [tempesta fw] modules are stopped Apr 26 06:52:04 192.168.122.209 [53274.720579] [tempesta fw] exiting... Apr 26 06:52:04 192.168.122.209 [53274.830445] [tdb] Shutdown Tempesta DB Apr 26 06:52:04 192.168.122.209 [53275.056816] End test: cache.test_cache.TestCacheH2.test_replicated_cache_bypass_prefix Apr 26 06:52:04 192.168.122.209 [53275.069776] Start test: cache.test_cache.TestCacheH2.test_replicated_cache_bypass_suffix Apr 26 06:52:05 192.168.122.209 [53276.134253] [tdb] Start Tempesta DB Apr 26 06:52:05 192.168.122.209 [53276.277837] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:52:07 192.168.122.209 [53277.652601] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53277.652601] Maybe that's fine, but it's worth checking the [53277.652601] config - if there is no relations between the [53277.652601] names, then host name confusion attack is possible. Apr 26 06:52:07 192.168.122.209 [53277.851419] [tempesta fw] Configuration processing is completed. Apr 26 06:52:07 192.168.122.209 [53277.904112] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:52:07 192.168.122.209 [53278.325861] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:52:07 192.168.122.209 [53278.352120] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:52:07 192.168.122.209 [53278.379600] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:52:07 192.168.122.209 [53278.435342] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:52:07 192.168.122.209 [53278.436743] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:52:08 192.168.122.209 [53278.475315] [tempesta fw] Tempesta FW is ready Apr 26 06:52:09 192.168.122.209 [53279.520910] [tdb] Close table 'client0.tdb' Apr 26 06:52:09 192.168.122.209 [53279.709424] [tdb] Close table 'sessions0.tdb' Apr 26 06:52:12 192.168.122.209 [53282.945172] [tdb] Close table 'cache0.tdb' Apr 26 06:52:12 192.168.122.209 [53283.190285] [tdb] Close table 'filter0.tdb' Apr 26 06:52:12 192.168.122.209 [53283.190730] [tempesta fw] modules are stopped Apr 26 06:52:12 192.168.122.209 [53283.371099] [tempesta fw] exiting... Apr 26 06:52:13 192.168.122.209 [53283.492984] [tdb] Shutdown Tempesta DB Apr 26 06:52:13 192.168.122.209 [53283.708314] End test: cache.test_cache.TestCacheH2.test_replicated_cache_bypass_suffix Apr 26 06:52:13 192.168.122.209 [53283.728553] Start test: cache.test_cache.TestCacheH2.test_replicated_cache_fulfill_all Apr 26 06:52:14 192.168.122.209 [53284.840281] [tdb] Start Tempesta DB Apr 26 06:52:14 192.168.122.209 [53284.988631] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:52:15 192.168.122.209 [53286.360985] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53286.360985] Maybe that's fine, but it's worth checking the [53286.360985] config - if there is no relations between the [53286.360985] names, then host name confusion attack is possible. Apr 26 06:52:16 192.168.122.209 [53286.491463] [tempesta fw] Configuration processing is completed. Apr 26 06:52:16 192.168.122.209 [53286.542360] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:52:16 192.168.122.209 [53286.984507] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:52:16 192.168.122.209 [53287.012306] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:52:16 192.168.122.209 [53287.041747] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:52:16 192.168.122.209 [53287.091462] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:52:16 192.168.122.209 [53287.093209] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:52:16 192.168.122.209 [53287.139404] [tempesta fw] Tempesta FW is ready Apr 26 06:52:17 192.168.122.209 [53288.019979] [tdb] Close table 'client0.tdb' Apr 26 06:52:17 192.168.122.209 [53288.212499] [tdb] Close table 'sessions0.tdb' Apr 26 06:52:20 192.168.122.209 [53291.461362] [tdb] Close table 'cache0.tdb' Apr 26 06:52:21 192.168.122.209 [53291.735069] [tdb] Close table 'filter0.tdb' Apr 26 06:52:21 192.168.122.209 [53291.735582] [tempesta fw] modules are stopped Apr 26 06:52:21 192.168.122.209 [53291.945668] [tempesta fw] exiting... Apr 26 06:52:21 192.168.122.209 [53292.052132] [tdb] Shutdown Tempesta DB Apr 26 06:52:21 192.168.122.209 [53292.290780] End test: cache.test_cache.TestCacheH2.test_replicated_cache_fulfill_all Apr 26 06:52:21 192.168.122.209 [53292.302988] Start test: cache.test_cache.TestCacheH2.test_replicated_cache_fulfill_prefix Apr 26 06:52:22 192.168.122.209 [53293.423240] [tdb] Start Tempesta DB Apr 26 06:52:23 192.168.122.209 [53293.587668] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:52:24 192.168.122.209 [53295.084836] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53295.084836] Maybe that's fine, but it's worth checking the [53295.084836] config - if there is no relations between the [53295.084836] names, then host name confusion attack is possible. Apr 26 06:52:24 192.168.122.209 [53295.263573] [tempesta fw] Configuration processing is completed. Apr 26 06:52:24 192.168.122.209 [53295.316452] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:52:25 192.168.122.209 [53295.801971] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:52:25 192.168.122.209 [53295.842621] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:52:25 192.168.122.209 [53295.872550] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:52:25 192.168.122.209 [53295.919572] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:52:25 192.168.122.209 [53295.921334] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:52:25 192.168.122.209 [53295.975527] [tempesta fw] Tempesta FW is ready Apr 26 06:52:26 192.168.122.209 [53296.861264] [tdb] Close table 'client0.tdb' Apr 26 06:52:26 192.168.122.209 [53297.053244] [tdb] Close table 'sessions0.tdb' Apr 26 06:52:29 192.168.122.209 [53300.320905] [tdb] Close table 'cache0.tdb' Apr 26 06:52:30 192.168.122.209 [53300.567293] [tdb] Close table 'filter0.tdb' Apr 26 06:52:30 192.168.122.209 [53300.567736] [tempesta fw] modules are stopped Apr 26 06:52:30 192.168.122.209 [53300.759062] [tempesta fw] exiting... Apr 26 06:52:30 192.168.122.209 [53300.883838] [tdb] Shutdown Tempesta DB Apr 26 06:52:30 192.168.122.209 [53301.122738] End test: cache.test_cache.TestCacheH2.test_replicated_cache_fulfill_prefix Apr 26 06:52:30 192.168.122.209 [53301.144884] Start test: cache.test_cache.TestCacheH2.test_replicated_cache_fulfill_suffix Apr 26 06:52:31 192.168.122.209 [53302.181292] [tdb] Start Tempesta DB Apr 26 06:52:31 192.168.122.209 [53302.326278] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:52:33 192.168.122.209 [53303.796904] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53303.796904] Maybe that's fine, but it's worth checking the [53303.796904] config - if there is no relations between the [53303.796904] names, then host name confusion attack is possible. Apr 26 06:52:33 192.168.122.209 [53303.955673] [tempesta fw] Configuration processing is completed. Apr 26 06:52:33 192.168.122.209 [53304.005652] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:52:33 192.168.122.209 [53304.428953] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:52:33 192.168.122.209 [53304.456662] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:52:34 192.168.122.209 [53304.483866] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:52:34 192.168.122.209 [53304.527700] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:52:34 192.168.122.209 [53304.529426] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:52:34 192.168.122.209 [53304.575655] [tempesta fw] Tempesta FW is ready Apr 26 06:52:34 192.168.122.209 [53305.422216] [tdb] Close table 'client0.tdb' Apr 26 06:52:35 192.168.122.209 [53305.609709] [tdb] Close table 'sessions0.tdb' Apr 26 06:52:38 192.168.122.209 [53308.809580] [tdb] Close table 'cache0.tdb' Apr 26 06:52:38 192.168.122.209 [53309.043097] [tdb] Close table 'filter0.tdb' Apr 26 06:52:38 192.168.122.209 [53309.043549] [tempesta fw] modules are stopped Apr 26 06:52:38 192.168.122.209 [53309.256311] [tempesta fw] exiting... Apr 26 06:52:38 192.168.122.209 [53309.391938] [tdb] Shutdown Tempesta DB Apr 26 06:52:39 192.168.122.209 [53309.613062] End test: cache.test_cache.TestCacheH2.test_replicated_cache_fulfill_suffix Apr 26 06:52:39 192.168.122.209 [53309.634837] Start test: cache.test_cache.TestCacheH2.test_replicated_cache_fulfill_suffix2 Apr 26 06:52:40 192.168.122.209 [53310.725748] [tdb] Start Tempesta DB Apr 26 06:52:40 192.168.122.209 [53310.863385] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:52:41 192.168.122.209 [53312.337022] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53312.337022] Maybe that's fine, but it's worth checking the [53312.337022] config - if there is no relations between the [53312.337022] names, then host name confusion attack is possible. Apr 26 06:52:42 192.168.122.209 [53312.519788] [tempesta fw] Configuration processing is completed. Apr 26 06:52:42 192.168.122.209 [53312.571858] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:52:42 192.168.122.209 [53312.989518] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:52:42 192.168.122.209 [53313.017480] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:52:42 192.168.122.209 [53313.045253] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:52:42 192.168.122.209 [53313.087793] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:52:42 192.168.122.209 [53313.089527] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:52:42 192.168.122.209 [53313.135745] [tempesta fw] Tempesta FW is ready Apr 26 06:52:43 192.168.122.209 [53313.986024] [tdb] Close table 'client0.tdb' Apr 26 06:52:43 192.168.122.209 [53314.171315] [tdb] Close table 'sessions0.tdb' Apr 26 06:52:46 192.168.122.209 [53317.461044] [tdb] Close table 'cache0.tdb' Apr 26 06:52:47 192.168.122.209 [53317.702613] [tdb] Close table 'filter0.tdb' Apr 26 06:52:47 192.168.122.209 [53317.703049] [tempesta fw] modules are stopped Apr 26 06:52:47 192.168.122.209 [53317.900091] [tempesta fw] exiting... Apr 26 06:52:47 192.168.122.209 [53318.037958] [tdb] Shutdown Tempesta DB Apr 26 06:52:47 192.168.122.209 [53318.270616] End test: cache.test_cache.TestCacheH2.test_replicated_cache_fulfill_suffix2 Apr 26 06:52:47 192.168.122.209 [53318.293398] Start test: cache.test_cache.TestCacheH2.test_sharding_cache_bypass_all Apr 26 06:52:48 192.168.122.209 [53319.384512] [tdb] Start Tempesta DB Apr 26 06:52:49 192.168.122.209 [53319.538138] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:52:50 192.168.122.209 [53320.913225] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53320.913225] Maybe that's fine, but it's worth checking the [53320.913225] config - if there is no relations between the [53320.913225] names, then host name confusion attack is possible. Apr 26 06:52:50 192.168.122.209 [53321.051924] [tempesta fw] Configuration processing is completed. Apr 26 06:52:50 192.168.122.209 [53321.102938] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:52:51 192.168.122.209 [53321.545598] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:52:51 192.168.122.209 [53321.574109] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:52:51 192.168.122.209 [53321.602010] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:52:51 192.168.122.209 [53321.647915] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:52:51 192.168.122.209 [53321.649641] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:52:51 192.168.122.209 [53321.691833] [tempesta fw] Tempesta FW is ready Apr 26 06:52:52 192.168.122.209 [53322.732702] [tdb] Close table 'client0.tdb' Apr 26 06:52:52 192.168.122.209 [53322.924081] [tdb] Close table 'sessions0.tdb' Apr 26 06:52:55 192.168.122.209 [53326.091710] [tdb] Close table 'cache0.tdb' Apr 26 06:52:55 192.168.122.209 [53326.337086] [tdb] Close table 'filter0.tdb' Apr 26 06:52:55 192.168.122.209 [53326.337513] [tempesta fw] modules are stopped Apr 26 06:52:56 192.168.122.209 [53326.584324] [tempesta fw] exiting... Apr 26 06:52:56 192.168.122.209 [53326.712472] [tdb] Shutdown Tempesta DB Apr 26 06:52:56 192.168.122.209 [53326.934963] End test: cache.test_cache.TestCacheH2.test_sharding_cache_bypass_all Apr 26 06:52:56 192.168.122.209 [53326.948855] Start test: cache.test_cache.TestCacheH2.test_sharding_cache_bypass_prefix Apr 26 06:52:57 192.168.122.209 [53328.003516] [tdb] Start Tempesta DB Apr 26 06:52:57 192.168.122.209 [53328.149125] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:52:59 192.168.122.209 [53329.669253] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53329.669253] Maybe that's fine, but it's worth checking the [53329.669253] config - if there is no relations between the [53329.669253] names, then host name confusion attack is possible. Apr 26 06:52:59 192.168.122.209 [53329.824038] [tempesta fw] Configuration processing is completed. Apr 26 06:52:59 192.168.122.209 [53329.876018] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:52:59 192.168.122.209 [53330.296562] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:52:59 192.168.122.209 [53330.323247] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:52:59 192.168.122.209 [53330.350975] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:52:59 192.168.122.209 [53330.416030] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:52:59 192.168.122.209 [53330.417769] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:52:59 192.168.122.209 [53330.459939] [tempesta fw] Tempesta FW is ready Apr 26 06:53:01 192.168.122.209 [53331.500404] [tdb] Close table 'client0.tdb' Apr 26 06:53:01 192.168.122.209 [53331.688539] [tdb] Close table 'sessions0.tdb' Apr 26 06:53:04 192.168.122.209 [53334.992663] [tdb] Close table 'cache0.tdb' Apr 26 06:53:04 192.168.122.209 [53335.263885] [tdb] Close table 'filter0.tdb' Apr 26 06:53:04 192.168.122.209 [53335.264329] [tempesta fw] modules are stopped Apr 26 06:53:04 192.168.122.209 [53335.444711] [tempesta fw] exiting... Apr 26 06:53:05 192.168.122.209 [53335.573948] [tdb] Shutdown Tempesta DB Apr 26 06:53:05 192.168.122.209 [53335.787919] End test: cache.test_cache.TestCacheH2.test_sharding_cache_bypass_prefix Apr 26 06:53:05 192.168.122.209 [53335.806811] Start test: cache.test_cache.TestCacheH2.test_sharding_cache_bypass_suffix Apr 26 06:53:06 192.168.122.209 [53336.852057] [tdb] Start Tempesta DB Apr 26 06:53:06 192.168.122.209 [53336.988548] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:53:07 192.168.122.209 [53338.397346] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53338.397346] Maybe that's fine, but it's worth checking the [53338.397346] config - if there is no relations between the [53338.397346] names, then host name confusion attack is possible. Apr 26 06:53:08 192.168.122.209 [53338.576119] [tempesta fw] Configuration processing is completed. Apr 26 06:53:08 192.168.122.209 [53338.629504] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:53:08 192.168.122.209 [53339.098423] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:53:08 192.168.122.209 [53339.132170] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:53:08 192.168.122.209 [53339.159581] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:53:08 192.168.122.209 [53339.216122] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:53:08 192.168.122.209 [53339.217797] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:53:08 192.168.122.209 [53339.264061] [tempesta fw] Tempesta FW is ready Apr 26 06:53:09 192.168.122.209 [53340.363844] [tdb] Close table 'client0.tdb' Apr 26 06:53:10 192.168.122.209 [53340.554873] [tdb] Close table 'sessions0.tdb' Apr 26 06:53:13 192.168.122.209 [53343.902154] [tdb] Close table 'cache0.tdb' Apr 26 06:53:13 192.168.122.209 [53344.160525] [tdb] Close table 'filter0.tdb' Apr 26 06:53:13 192.168.122.209 [53344.160981] [tempesta fw] modules are stopped Apr 26 06:53:13 192.168.122.209 [53344.386524] [tempesta fw] exiting... Apr 26 06:53:14 192.168.122.209 [53344.509156] [tdb] Shutdown Tempesta DB Apr 26 06:53:14 192.168.122.209 [53344.708123] End test: cache.test_cache.TestCacheH2.test_sharding_cache_bypass_suffix Apr 26 06:53:14 192.168.122.209 [53344.726962] Start test: cache.test_cache.TestCacheH2.test_sharding_cache_fulfill_all Apr 26 06:53:15 192.168.122.209 [53345.795308] [tdb] Start Tempesta DB Apr 26 06:53:15 192.168.122.209 [53345.958048] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:53:16 192.168.122.209 [53347.413572] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53347.413572] Maybe that's fine, but it's worth checking the [53347.413572] config - if there is no relations between the [53347.413572] names, then host name confusion attack is possible. Apr 26 06:53:17 192.168.122.209 [53347.528247] [tempesta fw] Configuration processing is completed. Apr 26 06:53:17 192.168.122.209 [53347.579293] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:53:17 192.168.122.209 [53348.018302] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:53:17 192.168.122.209 [53348.045199] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:53:17 192.168.122.209 [53348.072546] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:53:17 192.168.122.209 [53348.116188] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:53:17 192.168.122.209 [53348.117612] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:53:17 192.168.122.209 [53348.160170] [tempesta fw] Tempesta FW is ready Apr 26 06:53:18 192.168.122.209 [53349.122620] [tdb] Close table 'client0.tdb' Apr 26 06:53:18 192.168.122.209 [53349.307819] [tdb] Close table 'sessions0.tdb' Apr 26 06:53:22 192.168.122.209 [53352.539250] [tdb] Close table 'cache0.tdb' Apr 26 06:53:22 192.168.122.209 [53352.769690] [tdb] Close table 'filter0.tdb' Apr 26 06:53:22 192.168.122.209 [53352.770125] [tempesta fw] modules are stopped Apr 26 06:53:22 192.168.122.209 [53352.974271] [tempesta fw] exiting... Apr 26 06:53:22 192.168.122.209 [53353.121095] [tdb] Shutdown Tempesta DB Apr 26 06:53:22 192.168.122.209 [53353.354114] End test: cache.test_cache.TestCacheH2.test_sharding_cache_fulfill_all Apr 26 06:53:22 192.168.122.209 [53353.382260] Start test: cache.test_cache.TestCacheH2.test_sharding_cache_fulfill_prefix Apr 26 06:53:23 192.168.122.209 [53354.410415] [tdb] Start Tempesta DB Apr 26 06:53:24 192.168.122.209 [53354.548129] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:53:25 192.168.122.209 [53356.044982] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53356.044982] Maybe that's fine, but it's worth checking the [53356.044982] config - if there is no relations between the [53356.044982] names, then host name confusion attack is possible. Apr 26 06:53:25 192.168.122.209 [53356.216267] [tempesta fw] Configuration processing is completed. Apr 26 06:53:25 192.168.122.209 [53356.275389] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:53:26 192.168.122.209 [53356.693421] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:53:26 192.168.122.209 [53356.720087] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:53:26 192.168.122.209 [53356.747604] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:53:26 192.168.122.209 [53356.788265] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:53:26 192.168.122.209 [53356.789310] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:53:26 192.168.122.209 [53356.828277] [tempesta fw] Tempesta FW is ready Apr 26 06:53:27 192.168.122.209 [53357.679865] [tdb] Close table 'client0.tdb' Apr 26 06:53:27 192.168.122.209 [53357.876538] [tdb] Close table 'sessions0.tdb' Apr 26 06:53:30 192.168.122.209 [53361.062337] [tdb] Close table 'cache0.tdb' Apr 26 06:53:30 192.168.122.209 [53361.314621] [tdb] Close table 'filter0.tdb' Apr 26 06:53:30 192.168.122.209 [53361.315072] [tempesta fw] modules are stopped Apr 26 06:53:31 192.168.122.209 [53361.523268] [tempesta fw] exiting... Apr 26 06:53:31 192.168.122.209 [53361.644459] [tdb] Shutdown Tempesta DB Apr 26 06:53:31 192.168.122.209 [53361.837691] End test: cache.test_cache.TestCacheH2.test_sharding_cache_fulfill_prefix Apr 26 06:53:31 192.168.122.209 [53361.850399] Start test: cache.test_cache.TestCacheH2.test_sharding_cache_fulfill_suffix Apr 26 06:53:32 192.168.122.209 [53362.907706] [tdb] Start Tempesta DB Apr 26 06:53:32 192.168.122.209 [53363.049078] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:53:34 192.168.122.209 [53364.509776] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53364.509776] Maybe that's fine, but it's worth checking the [53364.509776] config - if there is no relations between the [53364.509776] names, then host name confusion attack is possible. Apr 26 06:53:34 192.168.122.209 [53364.684442] [tempesta fw] Configuration processing is completed. Apr 26 06:53:34 192.168.122.209 [53364.734306] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:53:34 192.168.122.209 [53365.149959] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:53:34 192.168.122.209 [53365.175995] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:53:34 192.168.122.209 [53365.203084] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:53:34 192.168.122.209 [53365.284431] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:53:34 192.168.122.209 [53365.286193] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:53:34 192.168.122.209 [53365.332345] [tempesta fw] Tempesta FW is ready Apr 26 06:53:35 192.168.122.209 [53366.162186] [tdb] Close table 'client0.tdb' Apr 26 06:53:35 192.168.122.209 [53366.351155] [tdb] Close table 'sessions0.tdb' Apr 26 06:53:39 192.168.122.209 [53369.543173] [tdb] Close table 'cache0.tdb' Apr 26 06:53:39 192.168.122.209 [53369.795092] [tdb] Close table 'filter0.tdb' Apr 26 06:53:39 192.168.122.209 [53369.795522] [tempesta fw] modules are stopped Apr 26 06:53:39 192.168.122.209 [53369.972475] [tempesta fw] exiting... Apr 26 06:53:39 192.168.122.209 [53370.078023] [tdb] Shutdown Tempesta DB Apr 26 06:53:39 192.168.122.209 [53370.316418] End test: cache.test_cache.TestCacheH2.test_sharding_cache_fulfill_suffix Apr 26 06:53:39 192.168.122.209 [53370.329530] Start test: cache.test_cache.TestCacheH2.test_sharding_cache_fulfill_suffix2 Apr 26 06:53:40 192.168.122.209 [53371.314176] [tdb] Start Tempesta DB Apr 26 06:53:40 192.168.122.209 [53371.453933] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:53:42 192.168.122.209 [53372.885352] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53372.885352] Maybe that's fine, but it's worth checking the [53372.885352] config - if there is no relations between the [53372.885352] names, then host name confusion attack is possible. Apr 26 06:53:42 192.168.122.209 [53373.064571] [tempesta fw] Configuration processing is completed. Apr 26 06:53:42 192.168.122.209 [53373.115863] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:53:43 192.168.122.209 [53373.541252] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:53:43 192.168.122.209 [53373.567890] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:53:43 192.168.122.209 [53373.594632] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:53:43 192.168.122.209 [53373.632490] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:53:43 192.168.122.209 [53373.633540] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:53:43 192.168.122.209 [53373.676484] [tempesta fw] Tempesta FW is ready Apr 26 06:53:44 192.168.122.209 [53374.541593] [tdb] Close table 'client0.tdb' Apr 26 06:53:44 192.168.122.209 [53374.736423] [tdb] Close table 'sessions0.tdb' Apr 26 06:53:47 192.168.122.209 [53377.957657] [tdb] Close table 'cache0.tdb' Apr 26 06:53:47 192.168.122.209 [53378.204705] [tdb] Close table 'filter0.tdb' Apr 26 06:53:47 192.168.122.209 [53378.205145] [tempesta fw] modules are stopped Apr 26 06:53:47 192.168.122.209 [53378.389398] [tempesta fw] exiting... Apr 26 06:53:48 192.168.122.209 [53378.495883] [tdb] Shutdown Tempesta DB Apr 26 06:53:48 192.168.122.209 [53378.696950] End test: cache.test_cache.TestCacheH2.test_sharding_cache_fulfill_suffix2 Apr 26 06:53:48 192.168.122.209 [53378.707971] Start test: cache.test_cache.TestCacheHttp.test_cache_date Apr 26 06:53:49 192.168.122.209 [53379.713824] [tdb] Start Tempesta DB Apr 26 06:53:49 192.168.122.209 [53379.859642] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:53:50 192.168.122.209 [53381.217910] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53381.217910] Maybe that's fine, but it's worth checking the [53381.217910] config - if there is no relations between the [53381.217910] names, then host name confusion attack is possible. Apr 26 06:53:50 192.168.122.209 [53381.392677] [tempesta fw] Configuration processing is completed. Apr 26 06:53:50 192.168.122.209 [53381.443925] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:53:51 192.168.122.209 [53381.864920] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:53:51 192.168.122.209 [53381.901118] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:53:51 192.168.122.209 [53381.928954] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:53:51 192.168.122.209 [53381.976658] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:53:51 192.168.122.209 [53381.978306] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:53:51 192.168.122.209 [53382.024593] [tempesta fw] Tempesta FW is ready Apr 26 06:53:52 192.168.122.209 [53382.901529] [tdb] Close table 'client0.tdb' Apr 26 06:53:52 192.168.122.209 [53383.111678] [tdb] Close table 'sessions0.tdb' Apr 26 06:53:55 192.168.122.209 [53386.350584] [tdb] Close table 'cache0.tdb' Apr 26 06:53:56 192.168.122.209 [53386.576551] [tdb] Close table 'filter0.tdb' Apr 26 06:53:56 192.168.122.209 [53386.576976] [tempesta fw] modules are stopped Apr 26 06:53:56 192.168.122.209 [53386.778374] [tempesta fw] exiting... Apr 26 06:53:56 192.168.122.209 [53386.906707] [tdb] Shutdown Tempesta DB Apr 26 06:53:56 192.168.122.209 [53387.116818] End test: cache.test_cache.TestCacheHttp.test_cache_date Apr 26 06:53:56 192.168.122.209 [53387.129801] Start test: cache.test_cache.TestCacheHttp.test_disabled_cache_bypass_all Apr 26 06:53:57 192.168.122.209 [53388.162597] [tdb] Start Tempesta DB Apr 26 06:53:57 192.168.122.209 [53388.307047] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:53:59 192.168.122.209 [53389.682047] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53389.682047] Maybe that's fine, but it's worth checking the [53389.682047] config - if there is no relations between the [53389.682047] names, then host name confusion attack is possible. Apr 26 06:53:59 192.168.122.209 [53389.808820] [tempesta fw] Configuration processing is completed. Apr 26 06:53:59 192.168.122.209 [53389.855394] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:53:59 192.168.122.209 [53389.883077] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:53:59 192.168.122.209 [53389.911106] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:53:59 192.168.122.209 [53389.956746] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:53:59 192.168.122.209 [53389.958476] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:53:59 192.168.122.209 [53389.996696] [tempesta fw] Tempesta FW is ready Apr 26 06:54:00 192.168.122.209 [53391.145253] [tdb] Close table 'client0.tdb' Apr 26 06:54:00 192.168.122.209 [53391.341899] [tdb] Close table 'sessions0.tdb' Apr 26 06:54:01 192.168.122.209 [53391.576266] [tdb] Close table 'filter0.tdb' Apr 26 06:54:01 192.168.122.209 [53391.576706] [tempesta fw] modules are stopped Apr 26 06:54:01 192.168.122.209 [53391.789952] [tempesta fw] exiting... Apr 26 06:54:01 192.168.122.209 [53391.941906] [tdb] Shutdown Tempesta DB Apr 26 06:54:01 192.168.122.209 [53392.163725] End test: cache.test_cache.TestCacheHttp.test_disabled_cache_bypass_all Apr 26 06:54:01 192.168.122.209 [53392.174044] Start test: cache.test_cache.TestCacheHttp.test_disabled_cache_bypass_prefix Apr 26 06:54:02 192.168.122.209 [53393.250439] [tdb] Start Tempesta DB Apr 26 06:54:02 192.168.122.209 [53393.395075] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:54:03 192.168.122.209 [53394.106153] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53394.106153] Maybe that's fine, but it's worth checking the [53394.106153] config - if there is no relations between the [53394.106153] names, then host name confusion attack is possible. Apr 26 06:54:03 192.168.122.209 [53394.284839] [tempesta fw] Configuration processing is completed. Apr 26 06:54:03 192.168.122.209 [53394.334682] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:54:03 192.168.122.209 [53394.363694] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:54:03 192.168.122.209 [53394.390483] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:54:03 192.168.122.209 [53394.444810] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:54:03 192.168.122.209 [53394.446557] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:54:04 192.168.122.209 [53394.496770] [tempesta fw] Tempesta FW is ready Apr 26 06:54:05 192.168.122.209 [53395.545037] [tdb] Close table 'client0.tdb' Apr 26 06:54:05 192.168.122.209 [53395.737005] [tdb] Close table 'sessions0.tdb' Apr 26 06:54:05 192.168.122.209 [53395.979393] [tdb] Close table 'filter0.tdb' Apr 26 06:54:05 192.168.122.209 [53395.979815] [tempesta fw] modules are stopped Apr 26 06:54:05 192.168.122.209 [53396.186373] [tempesta fw] exiting... Apr 26 06:54:05 192.168.122.209 [53396.301626] [tdb] Shutdown Tempesta DB Apr 26 06:54:06 192.168.122.209 [53396.550834] End test: cache.test_cache.TestCacheHttp.test_disabled_cache_bypass_prefix Apr 26 06:54:06 192.168.122.209 [53396.568459] Start test: cache.test_cache.TestCacheHttp.test_disabled_cache_bypass_suffix Apr 26 06:54:07 192.168.122.209 [53397.650002] [tdb] Start Tempesta DB Apr 26 06:54:07 192.168.122.209 [53397.779018] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:54:08 192.168.122.209 [53398.494409] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53398.494409] Maybe that's fine, but it's worth checking the [53398.494409] config - if there is no relations between the [53398.494409] names, then host name confusion attack is possible. Apr 26 06:54:08 192.168.122.209 [53398.660917] [tempesta fw] Configuration processing is completed. Apr 26 06:54:08 192.168.122.209 [53398.716715] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:54:08 192.168.122.209 [53398.744494] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:54:08 192.168.122.209 [53398.772390] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:54:08 192.168.122.209 [53398.820875] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:54:08 192.168.122.209 [53398.822602] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:54:08 192.168.122.209 [53398.868825] [tempesta fw] Tempesta FW is ready Apr 26 06:54:09 192.168.122.209 [53399.941197] [tdb] Close table 'client0.tdb' Apr 26 06:54:09 192.168.122.209 [53400.148291] [tdb] Close table 'sessions0.tdb' Apr 26 06:54:09 192.168.122.209 [53400.374884] [tdb] Close table 'filter0.tdb' Apr 26 06:54:09 192.168.122.209 [53400.375298] [tempesta fw] modules are stopped Apr 26 06:54:10 192.168.122.209 [53400.573225] [tempesta fw] exiting... Apr 26 06:54:10 192.168.122.209 [53400.694611] [tdb] Shutdown Tempesta DB Apr 26 06:54:10 192.168.122.209 [53400.952212] End test: cache.test_cache.TestCacheHttp.test_disabled_cache_bypass_suffix Apr 26 06:54:10 192.168.122.209 [53400.981286] Start test: cache.test_cache.TestCacheHttp.test_disabled_cache_fulfill_all Apr 26 06:54:11 192.168.122.209 [53401.984592] [tdb] Start Tempesta DB Apr 26 06:54:11 192.168.122.209 [53402.113797] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:54:12 192.168.122.209 [53402.774173] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53402.774173] Maybe that's fine, but it's worth checking the [53402.774173] config - if there is no relations between the [53402.774173] names, then host name confusion attack is possible. Apr 26 06:54:12 192.168.122.209 [53402.904927] [tempesta fw] Configuration processing is completed. Apr 26 06:54:12 192.168.122.209 [53402.957459] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:54:12 192.168.122.209 [53402.986760] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:54:12 192.168.122.209 [53403.014092] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:54:12 192.168.122.209 [53403.068920] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:54:12 192.168.122.209 [53403.070673] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:54:12 192.168.122.209 [53403.112858] [tempesta fw] Tempesta FW is ready Apr 26 06:54:13 192.168.122.209 [53404.125664] [tdb] Close table 'client0.tdb' Apr 26 06:54:13 192.168.122.209 [53404.302571] [tdb] Close table 'sessions0.tdb' Apr 26 06:54:14 192.168.122.209 [53404.523922] [tdb] Close table 'filter0.tdb' Apr 26 06:54:14 192.168.122.209 [53404.524352] [tempesta fw] modules are stopped Apr 26 06:54:14 192.168.122.209 [53404.753110] [tempesta fw] exiting... Apr 26 06:54:14 192.168.122.209 [53404.880014] [tdb] Shutdown Tempesta DB Apr 26 06:54:14 192.168.122.209 [53405.117110] End test: cache.test_cache.TestCacheHttp.test_disabled_cache_fulfill_all Apr 26 06:54:14 192.168.122.209 [53405.132654] Start test: cache.test_cache.TestCacheHttp.test_disabled_cache_fulfill_prefix Apr 26 06:54:15 192.168.122.209 [53406.191989] [tdb] Start Tempesta DB Apr 26 06:54:15 192.168.122.209 [53406.319148] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:54:16 192.168.122.209 [53407.002102] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53407.002102] Maybe that's fine, but it's worth checking the [53407.002102] config - if there is no relations between the [53407.002102] names, then host name confusion attack is possible. Apr 26 06:54:16 192.168.122.209 [53407.177080] [tempesta fw] Configuration processing is completed. Apr 26 06:54:16 192.168.122.209 [53407.231294] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:54:16 192.168.122.209 [53407.258755] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:54:16 192.168.122.209 [53407.286507] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:54:16 192.168.122.209 [53407.344963] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:54:16 192.168.122.209 [53407.346712] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:54:16 192.168.122.209 [53407.392914] [tempesta fw] Tempesta FW is ready Apr 26 06:54:17 192.168.122.209 [53408.450957] [tdb] Close table 'client0.tdb' Apr 26 06:54:18 192.168.122.209 [53408.647668] [tdb] Close table 'sessions0.tdb' Apr 26 06:54:18 192.168.122.209 [53408.869683] [tdb] Close table 'filter0.tdb' Apr 26 06:54:18 192.168.122.209 [53408.870111] [tempesta fw] modules are stopped Apr 26 06:54:18 192.168.122.209 [53409.109288] [tempesta fw] exiting... Apr 26 06:54:18 192.168.122.209 [53409.234714] [tdb] Shutdown Tempesta DB Apr 26 06:54:18 192.168.122.209 [53409.435039] End test: cache.test_cache.TestCacheHttp.test_disabled_cache_fulfill_prefix Apr 26 06:54:18 192.168.122.209 [53409.450461] Start test: cache.test_cache.TestCacheHttp.test_disabled_cache_fulfill_suffix Apr 26 06:54:20 192.168.122.209 [53410.487258] [tdb] Start Tempesta DB Apr 26 06:54:20 192.168.122.209 [53410.637877] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:54:20 192.168.122.209 [53411.295364] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53411.295364] Maybe that's fine, but it's worth checking the [53411.295364] config - if there is no relations between the [53411.295364] names, then host name confusion attack is possible. Apr 26 06:54:20 192.168.122.209 [53411.453044] [tempesta fw] Configuration processing is completed. Apr 26 06:54:21 192.168.122.209 [53411.503443] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:54:21 192.168.122.209 [53411.531186] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:54:21 192.168.122.209 [53411.560451] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:54:21 192.168.122.209 [53411.604937] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:54:21 192.168.122.209 [53411.606651] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:54:21 192.168.122.209 [53411.645005] [tempesta fw] Tempesta FW is ready Apr 26 06:54:22 192.168.122.209 [53412.675661] [tdb] Close table 'client0.tdb' Apr 26 06:54:22 192.168.122.209 [53412.858764] [tdb] Close table 'sessions0.tdb' Apr 26 06:54:22 192.168.122.209 [53413.088490] [tdb] Close table 'filter0.tdb' Apr 26 06:54:22 192.168.122.209 [53413.089769] [tempesta fw] modules are stopped Apr 26 06:54:22 192.168.122.209 [53413.272976] [tempesta fw] exiting... Apr 26 06:54:22 192.168.122.209 [53413.389277] [tdb] Shutdown Tempesta DB Apr 26 06:54:23 192.168.122.209 [53413.580266] End test: cache.test_cache.TestCacheHttp.test_disabled_cache_fulfill_suffix Apr 26 06:54:23 192.168.122.209 [53413.600861] Start test: cache.test_cache.TestCacheHttp.test_disabled_cache_fulfill_suffix2 Apr 26 06:54:24 192.168.122.209 [53414.610746] [tdb] Start Tempesta DB Apr 26 06:54:24 192.168.122.209 [53414.751464] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:54:24 192.168.122.209 [53415.463892] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53415.463892] Maybe that's fine, but it's worth checking the [53415.463892] config - if there is no relations between the [53415.463892] names, then host name confusion attack is possible. Apr 26 06:54:25 192.168.122.209 [53415.637100] [tempesta fw] Configuration processing is completed. Apr 26 06:54:25 192.168.122.209 [53415.687291] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:54:25 192.168.122.209 [53415.715151] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 06:54:25 192.168.122.209 [53415.744456] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 06:54:25 192.168.122.209 [53415.781079] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:54:25 192.168.122.209 [53415.782825] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:54:25 192.168.122.209 [53415.821114] [tempesta fw] Tempesta FW is ready Apr 26 06:54:26 192.168.122.209 [53416.865354] [tdb] Close table 'client0.tdb' Apr 26 06:54:26 192.168.122.209 [53417.044597] [tdb] Close table 'sessions0.tdb' Apr 26 06:54:26 192.168.122.209 [53417.267141] [tdb] Close table 'filter0.tdb' Apr 26 06:54:26 192.168.122.209 [53417.267576] [tempesta fw] modules are stopped Apr 26 06:54:27 192.168.122.209 [53417.517334] [tempesta fw] exiting... Apr 26 06:54:27 192.168.122.209 [53417.620710] [tdb] Shutdown Tempesta DB Apr 26 06:54:27 192.168.122.209 [53417.834228] End test: cache.test_cache.TestCacheHttp.test_disabled_cache_fulfill_suffix2 Apr 26 06:54:27 192.168.122.209 [53417.852022] Start test: cache.test_cache.TestCacheHttp.test_replicated_cache_bypass_all Apr 26 06:54:28 192.168.122.209 [53418.889176] [tdb] Start Tempesta DB Apr 26 06:54:28 192.168.122.209 [53419.023124] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:54:29 192.168.122.209 [53419.634377] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53419.634377] Maybe that's fine, but it's worth checking the [53419.634377] config - if there is no relations between the [53419.634377] names, then host name confusion attack is possible. Apr 26 06:54:29 192.168.122.209 [53419.765153] [tempesta fw] Configuration processing is completed. Apr 26 06:54:29 192.168.122.209 [53419.820221] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:54:29 192.168.122.209 [53420.229678] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:54:29 192.168.122.209 [53420.255287] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:54:29 192.168.122.209 [53420.282276] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:54:29 192.168.122.209 [53420.325177] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:54:29 192.168.122.209 [53420.326906] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:54:29 192.168.122.209 [53420.365081] [tempesta fw] Tempesta FW is ready Apr 26 06:54:30 192.168.122.209 [53421.392710] [tdb] Close table 'client0.tdb' Apr 26 06:54:31 192.168.122.209 [53421.569794] [tdb] Close table 'sessions0.tdb' Apr 26 06:54:34 192.168.122.209 [53424.756723] [tdb] Close table 'cache0.tdb' Apr 26 06:54:34 192.168.122.209 [53425.009972] [tdb] Close table 'filter0.tdb' Apr 26 06:54:34 192.168.122.209 [53425.010403] [tempesta fw] modules are stopped Apr 26 06:54:34 192.168.122.209 [53425.180247] [tempesta fw] exiting... Apr 26 06:54:34 192.168.122.209 [53425.334472] [tdb] Shutdown Tempesta DB Apr 26 06:54:35 192.168.122.209 [53425.547495] End test: cache.test_cache.TestCacheHttp.test_replicated_cache_bypass_all Apr 26 06:54:35 192.168.122.209 [53425.558089] Start test: cache.test_cache.TestCacheHttp.test_replicated_cache_bypass_prefix Apr 26 06:54:36 192.168.122.209 [53426.671708] [tdb] Start Tempesta DB Apr 26 06:54:36 192.168.122.209 [53426.813044] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:54:37 192.168.122.209 [53428.206608] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53428.206608] Maybe that's fine, but it's worth checking the [53428.206608] config - if there is no relations between the [53428.206608] names, then host name confusion attack is possible. Apr 26 06:54:37 192.168.122.209 [53428.381273] [tempesta fw] Configuration processing is completed. Apr 26 06:54:37 192.168.122.209 [53428.431702] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:54:38 192.168.122.209 [53428.848834] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:54:38 192.168.122.209 [53428.875123] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:54:38 192.168.122.209 [53428.901136] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:54:38 192.168.122.209 [53428.941187] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:54:38 192.168.122.209 [53428.942357] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:54:38 192.168.122.209 [53428.985195] [tempesta fw] Tempesta FW is ready Apr 26 06:54:39 192.168.122.209 [53430.072101] [tdb] Close table 'client0.tdb' Apr 26 06:54:39 192.168.122.209 [53430.265070] [tdb] Close table 'sessions0.tdb' Apr 26 06:54:42 192.168.122.209 [53433.436842] [tdb] Close table 'cache0.tdb' Apr 26 06:54:43 192.168.122.209 [53433.670128] [tdb] Close table 'filter0.tdb' Apr 26 06:54:43 192.168.122.209 [53433.670581] [tempesta fw] modules are stopped Apr 26 06:54:43 192.168.122.209 [53433.882112] [tempesta fw] exiting... Apr 26 06:54:43 192.168.122.209 [53433.986640] [tdb] Shutdown Tempesta DB Apr 26 06:54:43 192.168.122.209 [53434.199769] End test: cache.test_cache.TestCacheHttp.test_replicated_cache_bypass_prefix Apr 26 06:54:43 192.168.122.209 [53434.214114] Start test: cache.test_cache.TestCacheHttp.test_replicated_cache_bypass_suffix Apr 26 06:54:44 192.168.122.209 [53435.295258] [tdb] Start Tempesta DB Apr 26 06:54:44 192.168.122.209 [53435.435139] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:54:46 192.168.122.209 [53436.938608] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53436.938608] Maybe that's fine, but it's worth checking the [53436.938608] config - if there is no relations between the [53436.938608] names, then host name confusion attack is possible. Apr 26 06:54:46 192.168.122.209 [53437.105363] [tempesta fw] Configuration processing is completed. Apr 26 06:54:46 192.168.122.209 [53437.155660] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:54:47 192.168.122.209 [53437.576876] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:54:47 192.168.122.209 [53437.602509] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:54:47 192.168.122.209 [53437.629261] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:54:47 192.168.122.209 [53437.717383] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:54:47 192.168.122.209 [53437.719149] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:54:47 192.168.122.209 [53437.757300] [tempesta fw] Tempesta FW is ready Apr 26 06:54:48 192.168.122.209 [53438.780391] [tdb] Close table 'client0.tdb' Apr 26 06:54:48 192.168.122.209 [53438.965958] [tdb] Close table 'sessions0.tdb' Apr 26 06:54:51 192.168.122.209 [53442.144733] [tdb] Close table 'cache0.tdb' Apr 26 06:54:51 192.168.122.209 [53442.381645] [tdb] Close table 'filter0.tdb' Apr 26 06:54:51 192.168.122.209 [53442.382087] [tempesta fw] modules are stopped Apr 26 06:54:52 192.168.122.209 [53442.573105] [tempesta fw] exiting... Apr 26 06:54:52 192.168.122.209 [53442.713218] [tdb] Shutdown Tempesta DB Apr 26 06:54:52 192.168.122.209 [53442.904512] End test: cache.test_cache.TestCacheHttp.test_replicated_cache_bypass_suffix Apr 26 06:54:52 192.168.122.209 [53442.932277] Start test: cache.test_cache.TestCacheHttp.test_replicated_cache_fulfill_all Apr 26 06:54:53 192.168.122.209 [53443.986668] [tdb] Start Tempesta DB Apr 26 06:54:53 192.168.122.209 [53444.118073] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:54:54 192.168.122.209 [53445.446632] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53445.446632] Maybe that's fine, but it's worth checking the [53445.446632] config - if there is no relations between the [53445.446632] names, then host name confusion attack is possible. Apr 26 06:54:55 192.168.122.209 [53445.573469] [tempesta fw] Configuration processing is completed. Apr 26 06:54:55 192.168.122.209 [53445.623572] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:54:55 192.168.122.209 [53446.050062] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:54:55 192.168.122.209 [53446.076431] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:54:55 192.168.122.209 [53446.103581] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:54:55 192.168.122.209 [53446.141409] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:54:55 192.168.122.209 [53446.142505] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:54:55 192.168.122.209 [53446.181404] [tempesta fw] Tempesta FW is ready Apr 26 06:54:56 192.168.122.209 [53447.052822] [tdb] Close table 'client0.tdb' Apr 26 06:54:56 192.168.122.209 [53447.243898] [tdb] Close table 'sessions0.tdb' Apr 26 06:54:59 192.168.122.209 [53450.435394] [tdb] Close table 'cache0.tdb' Apr 26 06:55:00 192.168.122.209 [53450.706358] [tdb] Close table 'filter0.tdb' Apr 26 06:55:00 192.168.122.209 [53450.706779] [tempesta fw] modules are stopped Apr 26 06:55:00 192.168.122.209 [53450.890885] [tempesta fw] exiting... Apr 26 06:55:00 192.168.122.209 [53451.025647] [tdb] Shutdown Tempesta DB Apr 26 06:55:00 192.168.122.209 [53451.246613] End test: cache.test_cache.TestCacheHttp.test_replicated_cache_fulfill_all Apr 26 06:55:00 192.168.122.209 [53451.264463] Start test: cache.test_cache.TestCacheHttp.test_replicated_cache_fulfill_prefix Apr 26 06:55:01 192.168.122.209 [53452.316862] [tdb] Start Tempesta DB Apr 26 06:55:01 192.168.122.209 [53452.459511] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:55:03 192.168.122.209 [53453.878807] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53453.878807] Maybe that's fine, but it's worth checking the [53453.878807] config - if there is no relations between the [53453.878807] names, then host name confusion attack is possible. Apr 26 06:55:03 192.168.122.209 [53454.057612] [tempesta fw] Configuration processing is completed. Apr 26 06:55:03 192.168.122.209 [53454.109021] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:55:04 192.168.122.209 [53454.533434] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:55:04 192.168.122.209 [53454.559731] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:55:04 192.168.122.209 [53454.587237] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:55:04 192.168.122.209 [53454.625525] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:55:04 192.168.122.209 [53454.626693] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:55:04 192.168.122.209 [53454.673549] [tempesta fw] Tempesta FW is ready Apr 26 06:55:05 192.168.122.209 [53455.573471] [tdb] Close table 'client0.tdb' Apr 26 06:55:05 192.168.122.209 [53455.758923] [tdb] Close table 'sessions0.tdb' Apr 26 06:55:08 192.168.122.209 [53458.959050] [tdb] Close table 'cache0.tdb' Apr 26 06:55:08 192.168.122.209 [53459.211637] [tdb] Close table 'filter0.tdb' Apr 26 06:55:08 192.168.122.209 [53459.212070] [tempesta fw] modules are stopped Apr 26 06:55:08 192.168.122.209 [53459.448219] [tempesta fw] exiting... Apr 26 06:55:09 192.168.122.209 [53459.557963] [tdb] Shutdown Tempesta DB Apr 26 06:55:09 192.168.122.209 [53459.784621] End test: cache.test_cache.TestCacheHttp.test_replicated_cache_fulfill_prefix Apr 26 06:55:09 192.168.122.209 [53459.804682] Start test: cache.test_cache.TestCacheHttp.test_replicated_cache_fulfill_suffix Apr 26 06:55:10 192.168.122.209 [53460.884813] [tdb] Start Tempesta DB Apr 26 06:55:10 192.168.122.209 [53461.030457] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:55:11 192.168.122.209 [53462.466981] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53462.466981] Maybe that's fine, but it's worth checking the [53462.466981] config - if there is no relations between the [53462.466981] names, then host name confusion attack is possible. Apr 26 06:55:12 192.168.122.209 [53462.633679] [tempesta fw] Configuration processing is completed. Apr 26 06:55:12 192.168.122.209 [53462.684034] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:55:12 192.168.122.209 [53463.108480] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:55:12 192.168.122.209 [53463.134750] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:55:12 192.168.122.209 [53463.162161] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:55:12 192.168.122.209 [53463.213687] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:55:12 192.168.122.209 [53463.215331] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:55:12 192.168.122.209 [53463.289673] [tempesta fw] Tempesta FW is ready Apr 26 06:55:13 192.168.122.209 [53464.202880] [tdb] Close table 'client0.tdb' Apr 26 06:55:13 192.168.122.209 [53464.399326] [tdb] Close table 'sessions0.tdb' Apr 26 06:55:17 192.168.122.209 [53467.628332] [tdb] Close table 'cache0.tdb' Apr 26 06:55:17 192.168.122.209 [53467.876814] [tdb] Close table 'filter0.tdb' Apr 26 06:55:17 192.168.122.209 [53467.877255] [tempesta fw] modules are stopped Apr 26 06:55:17 192.168.122.209 [53468.108699] [tempesta fw] exiting... Apr 26 06:55:17 192.168.122.209 [53468.226557] [tdb] Shutdown Tempesta DB Apr 26 06:55:17 192.168.122.209 [53468.436771] End test: cache.test_cache.TestCacheHttp.test_replicated_cache_fulfill_suffix Apr 26 06:55:17 192.168.122.209 [53468.454662] Start test: cache.test_cache.TestCacheHttp.test_replicated_cache_fulfill_suffix2 Apr 26 06:55:19 192.168.122.209 [53469.557360] [tdb] Start Tempesta DB Apr 26 06:55:19 192.168.122.209 [53469.687937] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:55:20 192.168.122.209 [53471.103107] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53471.103107] Maybe that's fine, but it's worth checking the [53471.103107] config - if there is no relations between the [53471.103107] names, then host name confusion attack is possible. Apr 26 06:55:20 192.168.122.209 [53471.281825] [tempesta fw] Configuration processing is completed. Apr 26 06:55:20 192.168.122.209 [53471.337759] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:55:21 192.168.122.209 [53471.758740] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:55:21 192.168.122.209 [53471.784884] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:55:21 192.168.122.209 [53471.810858] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:55:21 192.168.122.209 [53471.857707] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:55:21 192.168.122.209 [53471.858615] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:55:21 192.168.122.209 [53471.901784] [tempesta fw] Tempesta FW is ready Apr 26 06:55:22 192.168.122.209 [53472.789617] [tdb] Close table 'client0.tdb' Apr 26 06:55:22 192.168.122.209 [53472.968724] [tdb] Close table 'sessions0.tdb' Apr 26 06:55:25 192.168.122.209 [53476.189253] [tdb] Close table 'cache0.tdb' Apr 26 06:55:25 192.168.122.209 [53476.439140] [tdb] Close table 'filter0.tdb' Apr 26 06:55:25 192.168.122.209 [53476.439574] [tempesta fw] modules are stopped Apr 26 06:55:26 192.168.122.209 [53476.631496] [tempesta fw] exiting... Apr 26 06:55:26 192.168.122.209 [53476.749593] [tdb] Shutdown Tempesta DB Apr 26 06:55:26 192.168.122.209 [53476.974897] End test: cache.test_cache.TestCacheHttp.test_replicated_cache_fulfill_suffix2 Apr 26 06:55:26 192.168.122.209 [53476.985771] Start test: cache.test_cache.TestCacheHttp.test_sharding_cache_bypass_all Apr 26 06:55:27 192.168.122.209 [53478.040246] [tdb] Start Tempesta DB Apr 26 06:55:27 192.168.122.209 [53478.174317] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:55:29 192.168.122.209 [53479.590384] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53479.590384] Maybe that's fine, but it's worth checking the [53479.590384] config - if there is no relations between the [53479.590384] names, then host name confusion attack is possible. Apr 26 06:55:29 192.168.122.209 [53479.713963] [tempesta fw] Configuration processing is completed. Apr 26 06:55:29 192.168.122.209 [53479.763295] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:55:29 192.168.122.209 [53480.182115] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:55:29 192.168.122.209 [53480.217321] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:55:29 192.168.122.209 [53480.244734] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:55:29 192.168.122.209 [53480.297903] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:55:29 192.168.122.209 [53480.299651] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:55:29 192.168.122.209 [53480.341767] [tempesta fw] Tempesta FW is ready Apr 26 06:55:30 192.168.122.209 [53481.339381] [tdb] Close table 'client0.tdb' Apr 26 06:55:31 192.168.122.209 [53481.523937] [tdb] Close table 'sessions0.tdb' Apr 26 06:55:34 192.168.122.209 [53484.693697] [tdb] Close table 'cache0.tdb' Apr 26 06:55:34 192.168.122.209 [53484.952956] [tdb] Close table 'filter0.tdb' Apr 26 06:55:34 192.168.122.209 [53484.953402] [tempesta fw] modules are stopped Apr 26 06:55:34 192.168.122.209 [53485.159905] [tempesta fw] exiting... Apr 26 06:55:34 192.168.122.209 [53485.317342] [tdb] Shutdown Tempesta DB Apr 26 06:55:35 192.168.122.209 [53485.527130] End test: cache.test_cache.TestCacheHttp.test_sharding_cache_bypass_all Apr 26 06:55:35 192.168.122.209 [53485.549135] Start test: cache.test_cache.TestCacheHttp.test_sharding_cache_bypass_prefix Apr 26 06:55:36 192.168.122.209 [53486.595122] [tdb] Start Tempesta DB Apr 26 06:55:36 192.168.122.209 [53486.727948] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:55:37 192.168.122.209 [53488.222683] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53488.222683] Maybe that's fine, but it's worth checking the [53488.222683] config - if there is no relations between the [53488.222683] names, then host name confusion attack is possible. Apr 26 06:55:37 192.168.122.209 [53488.386015] [tempesta fw] Configuration processing is completed. Apr 26 06:55:37 192.168.122.209 [53488.436295] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:55:38 192.168.122.209 [53488.859857] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:55:38 192.168.122.209 [53488.886910] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:55:38 192.168.122.209 [53488.914613] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:55:38 192.168.122.209 [53488.966027] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:55:38 192.168.122.209 [53488.967784] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:55:38 192.168.122.209 [53489.009956] [tempesta fw] Tempesta FW is ready Apr 26 06:55:39 192.168.122.209 [53490.079214] [tdb] Close table 'client0.tdb' Apr 26 06:55:39 192.168.122.209 [53490.270302] [tdb] Close table 'sessions0.tdb' Apr 26 06:55:43 192.168.122.209 [53493.491340] [tdb] Close table 'cache0.tdb' Apr 26 06:55:43 192.168.122.209 [53493.735698] [tdb] Close table 'filter0.tdb' Apr 26 06:55:43 192.168.122.209 [53493.736128] [tempesta fw] modules are stopped Apr 26 06:55:43 192.168.122.209 [53493.951357] [tempesta fw] exiting... Apr 26 06:55:43 192.168.122.209 [53494.080134] [tdb] Shutdown Tempesta DB Apr 26 06:55:43 192.168.122.209 [53494.292609] End test: cache.test_cache.TestCacheHttp.test_sharding_cache_bypass_prefix Apr 26 06:55:43 192.168.122.209 [53494.309559] Start test: cache.test_cache.TestCacheHttp.test_sharding_cache_bypass_suffix Apr 26 06:55:44 192.168.122.209 [53495.378687] [tdb] Start Tempesta DB Apr 26 06:55:45 192.168.122.209 [53495.528282] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:55:46 192.168.122.209 [53497.047235] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53497.047235] Maybe that's fine, but it's worth checking the [53497.047235] config - if there is no relations between the [53497.047235] names, then host name confusion attack is possible. Apr 26 06:55:46 192.168.122.209 [53497.210150] [tempesta fw] Configuration processing is completed. Apr 26 06:55:46 192.168.122.209 [53497.268632] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:55:47 192.168.122.209 [53497.696318] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:55:47 192.168.122.209 [53497.722729] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:55:47 192.168.122.209 [53497.748972] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:55:47 192.168.122.209 [53497.810126] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:55:47 192.168.122.209 [53497.811866] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:55:47 192.168.122.209 [53497.850076] [tempesta fw] Tempesta FW is ready Apr 26 06:55:48 192.168.122.209 [53498.913337] [tdb] Close table 'client0.tdb' Apr 26 06:55:48 192.168.122.209 [53499.099834] [tdb] Close table 'sessions0.tdb' Apr 26 06:55:51 192.168.122.209 [53502.303886] [tdb] Close table 'cache0.tdb' Apr 26 06:55:52 192.168.122.209 [53502.526821] [tdb] Close table 'filter0.tdb' Apr 26 06:55:52 192.168.122.209 [53502.527263] [tempesta fw] modules are stopped Apr 26 06:55:52 192.168.122.209 [53502.757845] [tempesta fw] exiting... Apr 26 06:55:52 192.168.122.209 [53502.899215] [tdb] Shutdown Tempesta DB Apr 26 06:55:52 192.168.122.209 [53503.114109] End test: cache.test_cache.TestCacheHttp.test_sharding_cache_bypass_suffix Apr 26 06:55:52 192.168.122.209 [53503.133383] Start test: cache.test_cache.TestCacheHttp.test_sharding_cache_fulfill_all Apr 26 06:55:53 192.168.122.209 [53504.203468] [tdb] Start Tempesta DB Apr 26 06:55:53 192.168.122.209 [53504.355937] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:55:55 192.168.122.209 [53505.759553] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53505.759553] Maybe that's fine, but it's worth checking the [53505.759553] config - if there is no relations between the [53505.759553] names, then host name confusion attack is possible. Apr 26 06:55:55 192.168.122.209 [53505.890149] [tempesta fw] Configuration processing is completed. Apr 26 06:55:55 192.168.122.209 [53505.941917] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:55:55 192.168.122.209 [53506.388057] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:55:55 192.168.122.209 [53506.420177] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:55:55 192.168.122.209 [53506.449389] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:55:56 192.168.122.209 [53506.490089] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:55:56 192.168.122.209 [53506.491125] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:55:56 192.168.122.209 [53506.530191] [tempesta fw] Tempesta FW is ready Apr 26 06:55:56 192.168.122.209 [53507.388341] [tdb] Close table 'client0.tdb' Apr 26 06:55:57 192.168.122.209 [53507.576638] [tdb] Close table 'sessions0.tdb' Apr 26 06:56:00 192.168.122.209 [53510.793294] [tdb] Close table 'cache0.tdb' Apr 26 06:56:00 192.168.122.209 [53511.035169] [tdb] Close table 'filter0.tdb' Apr 26 06:56:00 192.168.122.209 [53511.035614] [tempesta fw] modules are stopped Apr 26 06:56:00 192.168.122.209 [53511.234468] [tempesta fw] exiting... Apr 26 06:56:00 192.168.122.209 [53511.333383] [tdb] Shutdown Tempesta DB Apr 26 06:56:01 192.168.122.209 [53511.545214] End test: cache.test_cache.TestCacheHttp.test_sharding_cache_fulfill_all Apr 26 06:56:01 192.168.122.209 [53511.575029] Start test: cache.test_cache.TestCacheHttp.test_sharding_cache_fulfill_prefix Apr 26 06:56:02 192.168.122.209 [53512.656221] [tdb] Start Tempesta DB Apr 26 06:56:02 192.168.122.209 [53512.806039] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:56:03 192.168.122.209 [53514.215947] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53514.215947] Maybe that's fine, but it's worth checking the [53514.215947] config - if there is no relations between the [53514.215947] names, then host name confusion attack is possible. Apr 26 06:56:03 192.168.122.209 [53514.390360] [tempesta fw] Configuration processing is completed. Apr 26 06:56:03 192.168.122.209 [53514.441713] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:56:04 192.168.122.209 [53514.882413] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:56:04 192.168.122.209 [53514.910848] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:56:04 192.168.122.209 [53514.939749] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:56:04 192.168.122.209 [53514.978272] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:56:04 192.168.122.209 [53514.979353] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:56:04 192.168.122.209 [53515.034313] [tempesta fw] Tempesta FW is ready Apr 26 06:56:05 192.168.122.209 [53515.925872] [tdb] Close table 'client0.tdb' Apr 26 06:56:05 192.168.122.209 [53516.131639] [tdb] Close table 'sessions0.tdb' Apr 26 06:56:08 192.168.122.209 [53519.384813] [tdb] Close table 'cache0.tdb' Apr 26 06:56:09 192.168.122.209 [53519.602533] [tdb] Close table 'filter0.tdb' Apr 26 06:56:09 192.168.122.209 [53519.602968] [tempesta fw] modules are stopped Apr 26 06:56:09 192.168.122.209 [53519.799054] [tempesta fw] exiting... Apr 26 06:56:09 192.168.122.209 [53519.927203] [tdb] Shutdown Tempesta DB Apr 26 06:56:09 192.168.122.209 [53520.168461] End test: cache.test_cache.TestCacheHttp.test_sharding_cache_fulfill_prefix Apr 26 06:56:09 192.168.122.209 [53520.192422] Start test: cache.test_cache.TestCacheHttp.test_sharding_cache_fulfill_suffix Apr 26 06:56:10 192.168.122.209 [53521.318096] [tdb] Start Tempesta DB Apr 26 06:56:10 192.168.122.209 [53521.470118] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:56:12 192.168.122.209 [53522.991752] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53522.991752] Maybe that's fine, but it's worth checking the [53522.991752] config - if there is no relations between the [53522.991752] names, then host name confusion attack is possible. Apr 26 06:56:12 192.168.122.209 [53523.162492] [tempesta fw] Configuration processing is completed. Apr 26 06:56:12 192.168.122.209 [53523.221617] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:56:13 192.168.122.209 [53523.710883] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:56:13 192.168.122.209 [53523.742360] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:56:13 192.168.122.209 [53523.773588] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:56:13 192.168.122.209 [53523.830462] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:56:13 192.168.122.209 [53523.832194] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:56:13 192.168.122.209 [53523.870395] [tempesta fw] Tempesta FW is ready Apr 26 06:56:14 192.168.122.209 [53524.774744] [tdb] Close table 'client0.tdb' Apr 26 06:56:14 192.168.122.209 [53524.972957] [tdb] Close table 'sessions0.tdb' Apr 26 06:56:17 192.168.122.209 [53528.239186] [tdb] Close table 'cache0.tdb' Apr 26 06:56:18 192.168.122.209 [53528.531377] [tdb] Close table 'filter0.tdb' Apr 26 06:56:18 192.168.122.209 [53528.531862] [tempesta fw] modules are stopped Apr 26 06:56:18 192.168.122.209 [53528.752840] [tempesta fw] exiting... Apr 26 06:56:18 192.168.122.209 [53528.855759] [tdb] Shutdown Tempesta DB Apr 26 06:56:18 192.168.122.209 [53529.111646] End test: cache.test_cache.TestCacheHttp.test_sharding_cache_fulfill_suffix Apr 26 06:56:18 192.168.122.209 [53529.128140] Start test: cache.test_cache.TestCacheHttp.test_sharding_cache_fulfill_suffix2 Apr 26 06:56:19 192.168.122.209 [53530.266423] [tdb] Start Tempesta DB Apr 26 06:56:19 192.168.122.209 [53530.420500] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:56:21 192.168.122.209 [53531.831873] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53531.831873] Maybe that's fine, but it's worth checking the [53531.831873] config - if there is no relations between the [53531.831873] names, then host name confusion attack is possible. Apr 26 06:56:21 192.168.122.209 [53532.002580] [tempesta fw] Configuration processing is completed. Apr 26 06:56:21 192.168.122.209 [53532.056725] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:56:21 192.168.122.209 [53532.478629] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:56:22 192.168.122.209 [53532.505284] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:56:22 192.168.122.209 [53532.532750] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:56:22 192.168.122.209 [53532.574500] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:56:22 192.168.122.209 [53532.575574] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:56:22 192.168.122.209 [53532.614512] [tempesta fw] Tempesta FW is ready Apr 26 06:56:23 192.168.122.209 [53533.529758] [tdb] Close table 'client0.tdb' Apr 26 06:56:23 192.168.122.209 [53533.746023] [tdb] Close table 'sessions0.tdb' Apr 26 06:56:26 192.168.122.209 [53537.097073] [tdb] Close table 'cache0.tdb' Apr 26 06:56:26 192.168.122.209 [53537.345138] [tdb] Close table 'filter0.tdb' Apr 26 06:56:26 192.168.122.209 [53537.345580] [tempesta fw] modules are stopped Apr 26 06:56:27 192.168.122.209 [53537.556293] [tempesta fw] exiting... Apr 26 06:56:27 192.168.122.209 [53537.669849] [tdb] Shutdown Tempesta DB Apr 26 06:56:27 192.168.122.209 [53537.911547] End test: cache.test_cache.TestCacheHttp.test_sharding_cache_fulfill_suffix2 Apr 26 06:56:27 192.168.122.209 [53537.931743] Start test: cache.test_cache.TestCacheLocationH2.test_prefix_bypassed Apr 26 06:56:28 192.168.122.209 [53539.099512] [tdb] Start Tempesta DB Apr 26 06:56:28 192.168.122.209 [53539.253541] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:56:30 192.168.122.209 [53541.260075] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53541.260075] Maybe that's fine, but it's worth checking the [53541.260075] config - if there is no relations between the [53541.260075] names, then host name confusion attack is possible. Apr 26 06:56:30 192.168.122.209 [53541.359068] [tempesta fw] Configuration processing is completed. Apr 26 06:56:30 192.168.122.209 [53541.420311] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:56:31 192.168.122.209 [53541.992934] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:56:31 192.168.122.209 [53542.029069] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:56:31 192.168.122.209 [53542.064070] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:56:31 192.168.122.209 [53542.110665] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:56:31 192.168.122.209 [53542.112098] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:56:31 192.168.122.209 [53542.150650] [tempesta fw] Tempesta FW is ready Apr 26 06:56:32 192.168.122.209 [53542.828310] [tdb] Close table 'client0.tdb' Apr 26 06:56:32 192.168.122.209 [53543.026077] [tdb] Close table 'sessions0.tdb' Apr 26 06:56:35 192.168.122.209 [53546.399144] [tdb] Close table 'cache0.tdb' Apr 26 06:56:36 192.168.122.209 [53546.634317] [tdb] Close table 'filter0.tdb' Apr 26 06:56:36 192.168.122.209 [53546.634774] [tempesta fw] modules are stopped Apr 26 06:56:36 192.168.122.209 [53546.871122] [tempesta fw] exiting... Apr 26 06:56:36 192.168.122.209 [53547.024402] [tdb] Shutdown Tempesta DB Apr 26 06:56:36 192.168.122.209 [53547.241783] End test: cache.test_cache.TestCacheLocationH2.test_prefix_bypassed Apr 26 06:56:36 192.168.122.209 [53547.258908] Start test: cache.test_cache.TestCacheLocationH2.test_suffix_cached Apr 26 06:56:37 192.168.122.209 [53548.431875] [tdb] Start Tempesta DB Apr 26 06:56:38 192.168.122.209 [53548.620879] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:56:40 192.168.122.209 [53550.668020] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53550.668020] Maybe that's fine, but it's worth checking the [53550.668020] config - if there is no relations between the [53550.668020] names, then host name confusion attack is possible. Apr 26 06:56:40 192.168.122.209 [53550.758786] [tempesta fw] Configuration processing is completed. Apr 26 06:56:40 192.168.122.209 [53550.813705] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:56:40 192.168.122.209 [53551.242916] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:56:40 192.168.122.209 [53551.269809] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:56:40 192.168.122.209 [53551.297351] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:56:40 192.168.122.209 [53551.342776] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:56:40 192.168.122.209 [53551.344389] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:56:40 192.168.122.209 [53551.394744] [tempesta fw] Tempesta FW is ready Apr 26 06:56:41 192.168.122.209 [53552.095377] [tdb] Close table 'client0.tdb' Apr 26 06:56:41 192.168.122.209 [53552.283675] [tdb] Close table 'sessions0.tdb' Apr 26 06:56:45 192.168.122.209 [53555.546573] [tdb] Close table 'cache0.tdb' Apr 26 06:56:45 192.168.122.209 [53555.796832] [tdb] Close table 'filter0.tdb' Apr 26 06:56:45 192.168.122.209 [53555.797263] [tempesta fw] modules are stopped Apr 26 06:56:45 192.168.122.209 [53555.999667] [tempesta fw] exiting... Apr 26 06:56:45 192.168.122.209 [53556.143635] [tdb] Shutdown Tempesta DB Apr 26 06:56:45 192.168.122.209 [53556.387412] End test: cache.test_cache.TestCacheLocationH2.test_suffix_cached Apr 26 06:56:45 192.168.122.209 [53556.401675] Start test: cache.test_cache.TestCacheLocationH2.test_suffix_cached_and_prefix_bypassed Apr 26 06:56:46 192.168.122.209 [53557.446796] [tdb] Start Tempesta DB Apr 26 06:56:47 192.168.122.209 [53557.591731] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:56:48 192.168.122.209 [53559.456145] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53559.456145] Maybe that's fine, but it's worth checking the [53559.456145] config - if there is no relations between the [53559.456145] names, then host name confusion attack is possible. Apr 26 06:56:49 192.168.122.209 [53559.554875] [tempesta fw] Configuration processing is completed. Apr 26 06:56:49 192.168.122.209 [53559.606765] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:56:49 192.168.122.209 [53560.039066] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:56:49 192.168.122.209 [53560.065038] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:56:49 192.168.122.209 [53560.091033] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:56:49 192.168.122.209 [53560.134839] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:56:49 192.168.122.209 [53560.135970] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:56:49 192.168.122.209 [53560.174875] [tempesta fw] Tempesta FW is ready Apr 26 06:56:50 192.168.122.209 [53560.862395] [tdb] Close table 'client0.tdb' Apr 26 06:56:50 192.168.122.209 [53561.049543] [tdb] Close table 'sessions0.tdb' Apr 26 06:56:53 192.168.122.209 [53564.277119] [tdb] Close table 'cache0.tdb' Apr 26 06:56:54 192.168.122.209 [53564.522217] [tdb] Close table 'filter0.tdb' Apr 26 06:56:54 192.168.122.209 [53564.522660] [tempesta fw] modules are stopped Apr 26 06:56:54 192.168.122.209 [53564.747788] [tempesta fw] exiting... Apr 26 06:56:54 192.168.122.209 [53564.858370] [tdb] Shutdown Tempesta DB Apr 26 06:56:54 192.168.122.209 [53565.083875] End test: cache.test_cache.TestCacheLocationH2.test_suffix_cached_and_prefix_bypassed Apr 26 06:56:54 192.168.122.209 [53565.098715] Start test: cache.test_cache.TestCacheLocationHttp.test_prefix_bypassed Apr 26 06:56:55 192.168.122.209 [53566.114120] [tdb] Start Tempesta DB Apr 26 06:56:55 192.168.122.209 [53566.248668] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:56:57 192.168.122.209 [53568.100359] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53568.100359] Maybe that's fine, but it's worth checking the [53568.100359] config - if there is no relations between the [53568.100359] names, then host name confusion attack is possible. Apr 26 06:56:57 192.168.122.209 [53568.183300] [tempesta fw] Configuration processing is completed. Apr 26 06:56:57 192.168.122.209 [53568.242918] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:56:58 192.168.122.209 [53568.683572] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:56:58 192.168.122.209 [53568.709755] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:56:58 192.168.122.209 [53568.736999] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:56:58 192.168.122.209 [53568.778978] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:56:58 192.168.122.209 [53568.780355] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:56:58 192.168.122.209 [53568.822969] [tempesta fw] Tempesta FW is ready Apr 26 06:56:58 192.168.122.209 [53569.417104] [tdb] Close table 'client0.tdb' Apr 26 06:56:59 192.168.122.209 [53569.606195] [tdb] Close table 'sessions0.tdb' Apr 26 06:57:02 192.168.122.209 [53572.876508] [tdb] Close table 'cache0.tdb' Apr 26 06:57:02 192.168.122.209 [53573.105980] [tdb] Close table 'filter0.tdb' Apr 26 06:57:02 192.168.122.209 [53573.106400] [tempesta fw] modules are stopped Apr 26 06:57:02 192.168.122.209 [53573.295356] [tempesta fw] exiting... Apr 26 06:57:02 192.168.122.209 [53573.432287] [tdb] Shutdown Tempesta DB Apr 26 06:57:03 192.168.122.209 [53573.657129] End test: cache.test_cache.TestCacheLocationHttp.test_prefix_bypassed Apr 26 06:57:03 192.168.122.209 [53573.680376] Start test: cache.test_cache.TestCacheLocationHttp.test_suffix_cached Apr 26 06:57:04 192.168.122.209 [53574.705034] [tdb] Start Tempesta DB Apr 26 06:57:04 192.168.122.209 [53574.844863] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:57:06 192.168.122.209 [53576.684475] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53576.684475] Maybe that's fine, but it's worth checking the [53576.684475] config - if there is no relations between the [53576.684475] names, then host name confusion attack is possible. Apr 26 06:57:06 192.168.122.209 [53576.787502] [tempesta fw] Configuration processing is completed. Apr 26 06:57:06 192.168.122.209 [53576.841462] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:57:06 192.168.122.209 [53577.271853] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:57:06 192.168.122.209 [53577.298472] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:57:06 192.168.122.209 [53577.325940] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:57:06 192.168.122.209 [53577.383063] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:57:06 192.168.122.209 [53577.384778] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:57:06 192.168.122.209 [53577.427066] [tempesta fw] Tempesta FW is ready Apr 26 06:57:07 192.168.122.209 [53578.019912] [tdb] Close table 'client0.tdb' Apr 26 06:57:07 192.168.122.209 [53578.190370] [tdb] Close table 'sessions0.tdb' Apr 26 06:57:10 192.168.122.209 [53581.389368] [tdb] Close table 'cache0.tdb' Apr 26 06:57:11 192.168.122.209 [53581.603478] [tdb] Close table 'filter0.tdb' Apr 26 06:57:11 192.168.122.209 [53581.603929] [tempesta fw] modules are stopped Apr 26 06:57:11 192.168.122.209 [53581.787310] [tempesta fw] exiting... Apr 26 06:57:11 192.168.122.209 [53581.908368] [tdb] Shutdown Tempesta DB Apr 26 06:57:11 192.168.122.209 [53582.126193] End test: cache.test_cache.TestCacheLocationHttp.test_suffix_cached Apr 26 06:57:11 192.168.122.209 [53582.145358] Start test: cache.test_cache.TestCacheLocationHttp.test_suffix_cached_and_prefix_bypassed Apr 26 06:57:12 192.168.122.209 [53583.125560] [tdb] Start Tempesta DB Apr 26 06:57:12 192.168.122.209 [53583.261492] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:57:14 192.168.122.209 [53584.928474] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53584.928474] Maybe that's fine, but it's worth checking the [53584.928474] config - if there is no relations between the [53584.928474] names, then host name confusion attack is possible. Apr 26 06:57:14 192.168.122.209 [53585.015452] [tempesta fw] Configuration processing is completed. Apr 26 06:57:14 192.168.122.209 [53585.065448] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:57:15 192.168.122.209 [53585.499645] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:57:15 192.168.122.209 [53585.527409] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:57:15 192.168.122.209 [53585.554246] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:57:15 192.168.122.209 [53585.603211] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:57:15 192.168.122.209 [53585.604577] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:57:15 192.168.122.209 [53585.655172] [tempesta fw] Tempesta FW is ready Apr 26 06:57:15 192.168.122.209 [53586.237383] [tdb] Close table 'client0.tdb' Apr 26 06:57:15 192.168.122.209 [53586.425599] [tdb] Close table 'sessions0.tdb' Apr 26 06:57:19 192.168.122.209 [53589.688932] [tdb] Close table 'cache0.tdb' Apr 26 06:57:19 192.168.122.209 [53589.933091] [tdb] Close table 'filter0.tdb' Apr 26 06:57:19 192.168.122.209 [53589.933528] [tempesta fw] modules are stopped Apr 26 06:57:19 192.168.122.209 [53590.141175] [tempesta fw] exiting... Apr 26 06:57:19 192.168.122.209 [53590.243732] [tdb] Shutdown Tempesta DB Apr 26 06:57:20 192.168.122.209 [53590.490074] End test: cache.test_cache.TestCacheLocationHttp.test_suffix_cached_and_prefix_bypassed Apr 26 06:57:20 192.168.122.209 [53590.506681] Start test: cache.test_cache.TestCacheMultipleMethodsH2.test_GET_after_GET Apr 26 06:57:21 192.168.122.209 [53591.483661] [tdb] Start Tempesta DB Apr 26 06:57:21 192.168.122.209 [53591.626934] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:57:22 192.168.122.209 [53593.140550] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53593.140550] Maybe that's fine, but it's worth checking the [53593.140550] config - if there is no relations between the [53593.140550] names, then host name confusion attack is possible. Apr 26 06:57:22 192.168.122.209 [53593.215337] [tempesta fw] Configuration processing is completed. Apr 26 06:57:22 192.168.122.209 [53593.265791] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:57:23 192.168.122.209 [53593.699135] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:57:23 192.168.122.209 [53593.725411] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:57:23 192.168.122.209 [53593.752846] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:57:23 192.168.122.209 [53593.811340] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:57:23 192.168.122.209 [53593.813104] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:57:23 192.168.122.209 [53593.851284] [tempesta fw] Tempesta FW is ready Apr 26 06:57:24 192.168.122.209 [53594.563171] [tdb] Close table 'client0.tdb' Apr 26 06:57:24 192.168.122.209 [53594.757365] [tdb] Close table 'sessions0.tdb' Apr 26 06:57:27 192.168.122.209 [53597.979171] [tdb] Close table 'cache0.tdb' Apr 26 06:57:27 192.168.122.209 [53598.227132] [tdb] Close table 'filter0.tdb' Apr 26 06:57:27 192.168.122.209 [53598.227573] [tempesta fw] modules are stopped Apr 26 06:57:27 192.168.122.209 [53598.431850] [tempesta fw] exiting... Apr 26 06:57:28 192.168.122.209 [53598.557369] [tdb] Shutdown Tempesta DB Apr 26 06:57:28 192.168.122.209 [53598.793517] End test: cache.test_cache.TestCacheMultipleMethodsH2.test_GET_after_GET Apr 26 06:57:28 192.168.122.209 [53598.810491] Start test: cache.test_cache.TestCacheMultipleMethodsH2.test_GET_after_HEAD Apr 26 06:57:29 192.168.122.209 [53599.794627] [tdb] Start Tempesta DB Apr 26 06:57:29 192.168.122.209 [53599.936748] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:57:30 192.168.122.209 [53601.456674] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53601.456674] Maybe that's fine, but it's worth checking the [53601.456674] config - if there is no relations between the [53601.456674] names, then host name confusion attack is possible. Apr 26 06:57:31 192.168.122.209 [53601.527355] [tempesta fw] Configuration processing is completed. Apr 26 06:57:31 192.168.122.209 [53601.591250] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:57:31 192.168.122.209 [53602.019351] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:57:31 192.168.122.209 [53602.045078] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:57:31 192.168.122.209 [53602.070959] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:57:31 192.168.122.209 [53602.115421] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:57:31 192.168.122.209 [53602.116810] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:57:31 192.168.122.209 [53602.159377] [tempesta fw] Tempesta FW is ready Apr 26 06:57:32 192.168.122.209 [53602.800365] [tdb] Close table 'client0.tdb' Apr 26 06:57:32 192.168.122.209 [53602.978878] [tdb] Close table 'sessions0.tdb' Apr 26 06:57:35 192.168.122.209 [53606.266217] [tdb] Close table 'cache0.tdb' Apr 26 06:57:36 192.168.122.209 [53606.518636] [tdb] Close table 'filter0.tdb' Apr 26 06:57:36 192.168.122.209 [53606.519105] [tempesta fw] modules are stopped Apr 26 06:57:36 192.168.122.209 [53606.713729] [tempesta fw] exiting... Apr 26 06:57:36 192.168.122.209 [53606.843743] [tdb] Shutdown Tempesta DB Apr 26 06:57:36 192.168.122.209 [53607.046164] End test: cache.test_cache.TestCacheMultipleMethodsH2.test_GET_after_HEAD Apr 26 06:57:36 192.168.122.209 [53607.060941] Start test: cache.test_cache.TestCacheMultipleMethodsH2.test_HEAD_after_GET Apr 26 06:57:37 192.168.122.209 [53608.125638] [tdb] Start Tempesta DB Apr 26 06:57:37 192.168.122.209 [53608.263876] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:57:39 192.168.122.209 [53609.816775] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53609.816775] Maybe that's fine, but it's worth checking the [53609.816775] config - if there is no relations between the [53609.816775] names, then host name confusion attack is possible. Apr 26 06:57:39 192.168.122.209 [53609.891433] [tempesta fw] Configuration processing is completed. Apr 26 06:57:39 192.168.122.209 [53609.938301] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:57:39 192.168.122.209 [53610.366628] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:57:39 192.168.122.209 [53610.393070] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:57:39 192.168.122.209 [53610.428940] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:57:39 192.168.122.209 [53610.471486] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:57:39 192.168.122.209 [53610.472650] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:57:40 192.168.122.209 [53610.507505] [tempesta fw] Tempesta FW is ready Apr 26 06:57:40 192.168.122.209 [53611.146117] [tdb] Close table 'client0.tdb' Apr 26 06:57:40 192.168.122.209 [53611.315936] [tdb] Close table 'sessions0.tdb' Apr 26 06:57:44 192.168.122.209 [53614.535181] [tdb] Close table 'cache0.tdb' Apr 26 06:57:44 192.168.122.209 [53614.796252] [tdb] Close table 'filter0.tdb' Apr 26 06:57:44 192.168.122.209 [53614.796686] [tempesta fw] modules are stopped Apr 26 06:57:44 192.168.122.209 [53615.013543] [tempesta fw] exiting... Apr 26 06:57:44 192.168.122.209 [53615.131782] [tdb] Shutdown Tempesta DB Apr 26 06:57:44 192.168.122.209 [53615.340293] End test: cache.test_cache.TestCacheMultipleMethodsH2.test_HEAD_after_GET Apr 26 06:57:44 192.168.122.209 [53615.370835] Start test: cache.test_cache.TestCacheMultipleMethodsH2.test_HEAD_after_HEAD Apr 26 06:57:45 192.168.122.209 [53616.445604] [tdb] Start Tempesta DB Apr 26 06:57:46 192.168.122.209 [53616.582509] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:57:47 192.168.122.209 [53618.116879] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53618.116879] Maybe that's fine, but it's worth checking the [53618.116879] config - if there is no relations between the [53618.116879] names, then host name confusion attack is possible. Apr 26 06:57:47 192.168.122.209 [53618.183649] [tempesta fw] Configuration processing is completed. Apr 26 06:57:47 192.168.122.209 [53618.238712] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:57:48 192.168.122.209 [53618.668082] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:57:48 192.168.122.209 [53618.695170] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:57:48 192.168.122.209 [53618.721566] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:57:48 192.168.122.209 [53618.759605] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:57:48 192.168.122.209 [53618.760667] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:57:48 192.168.122.209 [53618.795609] [tempesta fw] Tempesta FW is ready Apr 26 06:57:48 192.168.122.209 [53619.446565] [tdb] Close table 'client0.tdb' Apr 26 06:57:49 192.168.122.209 [53619.631838] [tdb] Close table 'sessions0.tdb' Apr 26 06:57:52 192.168.122.209 [53622.883437] [tdb] Close table 'cache0.tdb' Apr 26 06:57:52 192.168.122.209 [53623.108774] [tdb] Close table 'filter0.tdb' Apr 26 06:57:52 192.168.122.209 [53623.109206] [tempesta fw] modules are stopped Apr 26 06:57:52 192.168.122.209 [53623.321248] [tempesta fw] exiting... Apr 26 06:57:52 192.168.122.209 [53623.444545] [tdb] Shutdown Tempesta DB Apr 26 06:57:53 192.168.122.209 [53623.668007] End test: cache.test_cache.TestCacheMultipleMethodsH2.test_HEAD_after_HEAD Apr 26 06:57:53 192.168.122.209 [53623.683805] Start test: cache.test_cache.TestCacheMultipleMethodsH2.test_POST_after_GET Apr 26 06:57:54 192.168.122.209 [53624.771050] [tdb] Start Tempesta DB Apr 26 06:57:54 192.168.122.209 [53624.907162] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:57:55 192.168.122.209 [53626.444996] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53626.444996] Maybe that's fine, but it's worth checking the [53626.444996] config - if there is no relations between the [53626.444996] names, then host name confusion attack is possible. Apr 26 06:57:56 192.168.122.209 [53626.503762] [tempesta fw] Configuration processing is completed. Apr 26 06:57:56 192.168.122.209 [53626.554441] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:57:56 192.168.122.209 [53626.976787] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:57:56 192.168.122.209 [53627.003196] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:57:56 192.168.122.209 [53627.028691] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:57:56 192.168.122.209 [53627.083736] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:57:56 192.168.122.209 [53627.085344] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:57:56 192.168.122.209 [53627.143732] [tempesta fw] Tempesta FW is ready Apr 26 06:57:57 192.168.122.209 [53627.797461] [tdb] Close table 'client0.tdb' Apr 26 06:57:57 192.168.122.209 [53627.984603] [tdb] Close table 'sessions0.tdb' Apr 26 06:58:00 192.168.122.209 [53631.344133] [tdb] Close table 'cache0.tdb' Apr 26 06:58:01 192.168.122.209 [53631.581049] [tdb] Close table 'filter0.tdb' Apr 26 06:58:01 192.168.122.209 [53631.581494] [tempesta fw] modules are stopped Apr 26 06:58:01 192.168.122.209 [53631.804170] [tempesta fw] exiting... Apr 26 06:58:01 192.168.122.209 [53631.920398] [tdb] Shutdown Tempesta DB Apr 26 06:58:01 192.168.122.209 [53632.131935] End test: cache.test_cache.TestCacheMultipleMethodsH2.test_POST_after_GET Apr 26 06:58:01 192.168.122.209 [53632.161513] Start test: cache.test_cache.TestCacheMultipleMethodsH2.test_POST_after_HEAD Apr 26 06:58:02 192.168.122.209 [53633.228072] [tdb] Start Tempesta DB Apr 26 06:58:02 192.168.122.209 [53633.362720] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:58:04 192.168.122.209 [53634.921118] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53634.921118] Maybe that's fine, but it's worth checking the [53634.921118] config - if there is no relations between the [53634.921118] names, then host name confusion attack is possible. Apr 26 06:58:04 192.168.122.209 [53634.983850] [tempesta fw] Configuration processing is completed. Apr 26 06:58:04 192.168.122.209 [53635.036666] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:58:04 192.168.122.209 [53635.460177] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:58:05 192.168.122.209 [53635.486358] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:58:05 192.168.122.209 [53635.512746] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:58:05 192.168.122.209 [53635.555820] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:58:05 192.168.122.209 [53635.557183] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:58:05 192.168.122.209 [53635.595799] [tempesta fw] Tempesta FW is ready Apr 26 06:58:05 192.168.122.209 [53636.240347] [tdb] Close table 'client0.tdb' Apr 26 06:58:05 192.168.122.209 [53636.433871] [tdb] Close table 'sessions0.tdb' Apr 26 06:58:09 192.168.122.209 [53639.651820] [tdb] Close table 'cache0.tdb' Apr 26 06:58:09 192.168.122.209 [53639.906165] [tdb] Close table 'filter0.tdb' Apr 26 06:58:09 192.168.122.209 [53639.906611] [tempesta fw] modules are stopped Apr 26 06:58:09 192.168.122.209 [53640.077687] [tempesta fw] exiting... Apr 26 06:58:09 192.168.122.209 [53640.193511] [tdb] Shutdown Tempesta DB Apr 26 06:58:09 192.168.122.209 [53640.420497] End test: cache.test_cache.TestCacheMultipleMethodsH2.test_POST_after_HEAD Apr 26 06:58:09 192.168.122.209 [53640.443032] Start test: cache.test_cache.TestCacheMultipleMethodsH2.test_cache_POST_request_not_cached_no_cache_control Apr 26 06:58:11 192.168.122.209 [53641.532862] [tdb] Start Tempesta DB Apr 26 06:58:11 192.168.122.209 [53641.672070] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:58:12 192.168.122.209 [53643.245199] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53643.245199] Maybe that's fine, but it's worth checking the [53643.245199] config - if there is no relations between the [53643.245199] names, then host name confusion attack is possible. Apr 26 06:58:12 192.168.122.209 [53643.319966] [tempesta fw] Configuration processing is completed. Apr 26 06:58:12 192.168.122.209 [53643.370788] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:58:13 192.168.122.209 [53643.794325] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:58:13 192.168.122.209 [53643.830866] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:58:13 192.168.122.209 [53643.858319] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:58:13 192.168.122.209 [53643.899920] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:58:13 192.168.122.209 [53643.901083] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:58:13 192.168.122.209 [53643.947915] [tempesta fw] Tempesta FW is ready Apr 26 06:58:14 192.168.122.209 [53644.706786] [tdb] Close table 'client0.tdb' Apr 26 06:58:14 192.168.122.209 [53644.897682] [tdb] Close table 'sessions0.tdb' Apr 26 06:58:17 192.168.122.209 [53648.128777] [tdb] Close table 'cache0.tdb' Apr 26 06:58:17 192.168.122.209 [53648.373750] [tdb] Close table 'filter0.tdb' Apr 26 06:58:17 192.168.122.209 [53648.374201] [tempesta fw] modules are stopped Apr 26 06:58:18 192.168.122.209 [53648.543682] [tempesta fw] exiting... Apr 26 06:58:18 192.168.122.209 [53648.702379] [tdb] Shutdown Tempesta DB Apr 26 06:58:18 192.168.122.209 [53648.905379] End test: cache.test_cache.TestCacheMultipleMethodsH2.test_cache_POST_request_not_cached_no_cache_control Apr 26 06:58:18 192.168.122.209 [53648.925372] Start test: cache.test_cache.TestCacheMultipleMethodsH2.test_cache_POST_request_not_cached_not_same_location Apr 26 06:58:19 192.168.122.209 [53649.971554] [tdb] Start Tempesta DB Apr 26 06:58:19 192.168.122.209 [53650.104792] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:58:21 192.168.122.209 [53651.621284] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53651.621284] Maybe that's fine, but it's worth checking the [53651.621284] config - if there is no relations between the [53651.621284] names, then host name confusion attack is possible. Apr 26 06:58:21 192.168.122.209 [53651.700057] [tempesta fw] Configuration processing is completed. Apr 26 06:58:21 192.168.122.209 [53651.755378] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:58:21 192.168.122.209 [53652.179776] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:58:21 192.168.122.209 [53652.205925] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:58:21 192.168.122.209 [53652.231910] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:58:21 192.168.122.209 [53652.320113] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:58:21 192.168.122.209 [53652.322018] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:58:21 192.168.122.209 [53652.364001] [tempesta fw] Tempesta FW is ready Apr 26 06:58:22 192.168.122.209 [53653.015978] [tdb] Close table 'client0.tdb' Apr 26 06:58:22 192.168.122.209 [53653.199485] [tdb] Close table 'sessions0.tdb' Apr 26 06:58:25 192.168.122.209 [53656.400998] [tdb] Close table 'cache0.tdb' Apr 26 06:58:26 192.168.122.209 [53656.636081] [tdb] Close table 'filter0.tdb' Apr 26 06:58:26 192.168.122.209 [53656.636510] [tempesta fw] modules are stopped Apr 26 06:58:26 192.168.122.209 [53656.874959] [tempesta fw] exiting... Apr 26 06:58:26 192.168.122.209 [53657.012890] [tdb] Shutdown Tempesta DB Apr 26 06:58:26 192.168.122.209 [53657.214134] End test: cache.test_cache.TestCacheMultipleMethodsH2.test_cache_POST_request_not_cached_not_same_location Apr 26 06:58:26 192.168.122.209 [53657.231257] Start test: cache.test_cache.TestCacheMultipleMethodsH2.test_cache_POST_request_with_location_GET Apr 26 06:58:27 192.168.122.209 [53658.275421] [tdb] Start Tempesta DB Apr 26 06:58:27 192.168.122.209 [53658.428083] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:58:29 192.168.122.209 [53659.973428] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53659.973428] Maybe that's fine, but it's worth checking the [53659.973428] config - if there is no relations between the [53659.973428] names, then host name confusion attack is possible. Apr 26 06:58:29 192.168.122.209 [53660.044058] [tempesta fw] Configuration processing is completed. Apr 26 06:58:29 192.168.122.209 [53660.099208] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:58:30 192.168.122.209 [53660.542064] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:58:30 192.168.122.209 [53660.569874] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:58:30 192.168.122.209 [53660.598217] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:58:30 192.168.122.209 [53660.640128] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:58:30 192.168.122.209 [53660.641352] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:58:30 192.168.122.209 [53660.680126] [tempesta fw] Tempesta FW is ready Apr 26 06:58:30 192.168.122.209 [53661.344128] [tdb] Close table 'client0.tdb' Apr 26 06:58:31 192.168.122.209 [53661.526137] [tdb] Close table 'sessions0.tdb' Apr 26 06:58:34 192.168.122.209 [53664.775750] [tdb] Close table 'cache0.tdb' Apr 26 06:58:34 192.168.122.209 [53665.025354] [tdb] Close table 'filter0.tdb' Apr 26 06:58:34 192.168.122.209 [53665.025814] [tempesta fw] modules are stopped Apr 26 06:58:34 192.168.122.209 [53665.231782] [tempesta fw] exiting... Apr 26 06:58:34 192.168.122.209 [53665.365672] [tdb] Shutdown Tempesta DB Apr 26 06:58:35 192.168.122.209 [53665.636211] End test: cache.test_cache.TestCacheMultipleMethodsH2.test_cache_POST_request_with_location_GET Apr 26 06:58:35 192.168.122.209 [53665.654283] Start test: cache.test_cache.TestCacheMultipleMethodsH2.test_cache_POST_request_with_location_HEAD Apr 26 06:58:36 192.168.122.209 [53666.692830] [tdb] Start Tempesta DB Apr 26 06:58:36 192.168.122.209 [53666.853117] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:58:37 192.168.122.209 [53668.321515] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53668.321515] Maybe that's fine, but it's worth checking the [53668.321515] config - if there is no relations between the [53668.321515] names, then host name confusion attack is possible. Apr 26 06:58:37 192.168.122.209 [53668.388325] [tempesta fw] Configuration processing is completed. Apr 26 06:58:37 192.168.122.209 [53668.440040] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:58:38 192.168.122.209 [53668.925241] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:58:38 192.168.122.209 [53668.956186] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:58:38 192.168.122.209 [53668.986325] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:58:38 192.168.122.209 [53669.032277] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:58:38 192.168.122.209 [53669.034017] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:58:38 192.168.122.209 [53669.072279] [tempesta fw] Tempesta FW is ready Apr 26 06:58:39 192.168.122.209 [53669.722089] [tdb] Close table 'client0.tdb' Apr 26 06:58:39 192.168.122.209 [53669.924574] [tdb] Close table 'sessions0.tdb' Apr 26 06:58:42 192.168.122.209 [53673.171075] [tdb] Close table 'cache0.tdb' Apr 26 06:58:42 192.168.122.209 [53673.420641] [tdb] Close table 'filter0.tdb' Apr 26 06:58:42 192.168.122.209 [53673.421082] [tempesta fw] modules are stopped Apr 26 06:58:43 192.168.122.209 [53673.651405] [tempesta fw] exiting... Apr 26 06:58:43 192.168.122.209 [53673.783424] [tdb] Shutdown Tempesta DB Apr 26 06:58:43 192.168.122.209 [53674.014536] End test: cache.test_cache.TestCacheMultipleMethodsH2.test_cache_POST_request_with_location_HEAD Apr 26 06:58:43 192.168.122.209 [53674.032907] Start test: cache.test_cache.TestCacheMultipleMethodsH2.test_cache_POST_request_with_location_POST Apr 26 06:58:44 192.168.122.209 [53675.096450] [tdb] Start Tempesta DB Apr 26 06:58:44 192.168.122.209 [53675.228376] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:58:46 192.168.122.209 [53676.757656] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53676.757656] Maybe that's fine, but it's worth checking the [53676.757656] config - if there is no relations between the [53676.757656] names, then host name confusion attack is possible. Apr 26 06:58:46 192.168.122.209 [53676.828414] [tempesta fw] Configuration processing is completed. Apr 26 06:58:46 192.168.122.209 [53676.881645] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:58:46 192.168.122.209 [53677.352123] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:58:46 192.168.122.209 [53677.379958] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:58:46 192.168.122.209 [53677.407693] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:58:46 192.168.122.209 [53677.460300] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:58:46 192.168.122.209 [53677.461985] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:58:47 192.168.122.209 [53677.500331] [tempesta fw] Tempesta FW is ready Apr 26 06:58:47 192.168.122.209 [53678.179634] [tdb] Close table 'client0.tdb' Apr 26 06:58:47 192.168.122.209 [53678.378644] [tdb] Close table 'sessions0.tdb' Apr 26 06:58:51 192.168.122.209 [53681.608951] [tdb] Close table 'cache0.tdb' Apr 26 06:58:51 192.168.122.209 [53681.858234] [tdb] Close table 'filter0.tdb' Apr 26 06:58:51 192.168.122.209 [53681.858669] [tempesta fw] modules are stopped Apr 26 06:58:51 192.168.122.209 [53682.033094] [tempesta fw] exiting... Apr 26 06:58:51 192.168.122.209 [53682.170818] [tdb] Shutdown Tempesta DB Apr 26 06:58:51 192.168.122.209 [53682.390096] End test: cache.test_cache.TestCacheMultipleMethodsH2.test_cache_POST_request_with_location_POST Apr 26 06:58:51 192.168.122.209 [53682.412589] Start test: cache.test_cache.TestCacheMultipleMethodsH2.test_several_entries_GET_GET Apr 26 06:58:52 192.168.122.209 [53683.462536] [tdb] Start Tempesta DB Apr 26 06:58:53 192.168.122.209 [53683.620409] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:58:54 192.168.122.209 [53685.121780] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53685.121780] Maybe that's fine, but it's worth checking the [53685.121780] config - if there is no relations between the [53685.121780] names, then host name confusion attack is possible. Apr 26 06:58:54 192.168.122.209 [53685.196488] [tempesta fw] Configuration processing is completed. Apr 26 06:58:54 192.168.122.209 [53685.248215] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:58:55 192.168.122.209 [53685.694066] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:58:55 192.168.122.209 [53685.723397] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:58:55 192.168.122.209 [53685.754428] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:58:55 192.168.122.209 [53685.808504] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:58:55 192.168.122.209 [53685.810190] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:58:55 192.168.122.209 [53685.856371] [tempesta fw] Tempesta FW is ready Apr 26 06:58:58 192.168.122.209 [53688.590172] [tdb] Close table 'client0.tdb' Apr 26 06:58:58 192.168.122.209 [53688.777143] [tdb] Close table 'sessions0.tdb' Apr 26 06:59:01 192.168.122.209 [53692.131955] [tdb] Close table 'cache0.tdb' Apr 26 06:59:01 192.168.122.209 [53692.400183] [tdb] Close table 'filter0.tdb' Apr 26 06:59:01 192.168.122.209 [53692.400643] [tempesta fw] modules are stopped Apr 26 06:59:02 192.168.122.209 [53692.636971] [tempesta fw] exiting... Apr 26 06:59:02 192.168.122.209 [53692.766917] [tdb] Shutdown Tempesta DB Apr 26 06:59:02 192.168.122.209 [53692.994738] End test: cache.test_cache.TestCacheMultipleMethodsH2.test_several_entries_GET_GET Apr 26 06:59:02 192.168.122.209 [53693.008204] Start test: cache.test_cache.TestCacheMultipleMethodsH2.test_several_entries_GET_HEAD Apr 26 06:59:03 192.168.122.209 [53694.156584] [tdb] Start Tempesta DB Apr 26 06:59:03 192.168.122.209 [53694.306657] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:59:05 192.168.122.209 [53695.845887] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53695.845887] Maybe that's fine, but it's worth checking the [53695.845887] config - if there is no relations between the [53695.845887] names, then host name confusion attack is possible. Apr 26 06:59:05 192.168.122.209 [53695.920951] [tempesta fw] Configuration processing is completed. Apr 26 06:59:05 192.168.122.209 [53695.972192] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:59:06 192.168.122.209 [53696.492733] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:59:06 192.168.122.209 [53696.526815] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:59:06 192.168.122.209 [53696.560916] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:59:06 192.168.122.209 [53696.600564] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:59:06 192.168.122.209 [53696.601574] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:59:06 192.168.122.209 [53696.640584] [tempesta fw] Tempesta FW is ready Apr 26 06:59:08 192.168.122.209 [53699.325170] [tdb] Close table 'client0.tdb' Apr 26 06:59:09 192.168.122.209 [53699.514359] [tdb] Close table 'sessions0.tdb' Apr 26 06:59:12 192.168.122.209 [53702.755952] [tdb] Close table 'cache0.tdb' Apr 26 06:59:12 192.168.122.209 [53702.999393] [tdb] Close table 'filter0.tdb' Apr 26 06:59:12 192.168.122.209 [53702.999833] [tempesta fw] modules are stopped Apr 26 06:59:12 192.168.122.209 [53703.185850] [tempesta fw] exiting... Apr 26 06:59:12 192.168.122.209 [53703.321160] [tdb] Shutdown Tempesta DB Apr 26 06:59:13 192.168.122.209 [53703.526164] End test: cache.test_cache.TestCacheMultipleMethodsH2.test_several_entries_GET_HEAD Apr 26 06:59:13 192.168.122.209 [53703.545239] Start test: cache.test_cache.TestCacheMultipleMethodsH2.test_several_entries_GET_POST Apr 26 06:59:14 192.168.122.209 [53704.712578] [tdb] Start Tempesta DB Apr 26 06:59:14 192.168.122.209 [53704.880749] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:59:16 192.168.122.209 [53706.514036] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53706.514036] Maybe that's fine, but it's worth checking the [53706.514036] config - if there is no relations between the [53706.514036] names, then host name confusion attack is possible. Apr 26 06:59:16 192.168.122.209 [53706.580779] [tempesta fw] Configuration processing is completed. Apr 26 06:59:16 192.168.122.209 [53706.640083] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:59:16 192.168.122.209 [53707.124142] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:59:16 192.168.122.209 [53707.150737] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:59:16 192.168.122.209 [53707.178556] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:59:16 192.168.122.209 [53707.220697] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:59:16 192.168.122.209 [53707.221776] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:59:16 192.168.122.209 [53707.260706] [tempesta fw] Tempesta FW is ready Apr 26 06:59:17 192.168.122.209 [53707.960379] [tdb] Close table 'client0.tdb' Apr 26 06:59:17 192.168.122.209 [53708.168208] [tdb] Close table 'sessions0.tdb' Apr 26 06:59:21 192.168.122.209 [53711.502944] [tdb] Close table 'cache0.tdb' Apr 26 06:59:21 192.168.122.209 [53711.770419] [tdb] Close table 'filter0.tdb' Apr 26 06:59:21 192.168.122.209 [53711.770870] [tempesta fw] modules are stopped Apr 26 06:59:21 192.168.122.209 [53711.948552] [tempesta fw] exiting... Apr 26 06:59:21 192.168.122.209 [53712.084283] [tdb] Shutdown Tempesta DB Apr 26 06:59:21 192.168.122.209 [53712.316393] End test: cache.test_cache.TestCacheMultipleMethodsH2.test_several_entries_GET_POST Apr 26 06:59:21 192.168.122.209 [53712.341146] Start test: cache.test_cache.TestCacheMultipleMethodsH2.test_several_entries_POST_GET Apr 26 06:59:22 192.168.122.209 [53713.425380] [tdb] Start Tempesta DB Apr 26 06:59:23 192.168.122.209 [53713.577836] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:59:24 192.168.122.209 [53715.206164] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53715.206164] Maybe that's fine, but it's worth checking the [53715.206164] config - if there is no relations between the [53715.206164] names, then host name confusion attack is possible. Apr 26 06:59:24 192.168.122.209 [53715.276879] [tempesta fw] Configuration processing is completed. Apr 26 06:59:24 192.168.122.209 [53715.346894] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:59:25 192.168.122.209 [53715.777594] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:59:25 192.168.122.209 [53715.806307] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:59:25 192.168.122.209 [53715.835535] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:59:25 192.168.122.209 [53715.896853] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:59:25 192.168.122.209 [53715.898302] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:59:25 192.168.122.209 [53715.940731] [tempesta fw] Tempesta FW is ready Apr 26 06:59:28 192.168.122.209 [53718.642799] [tdb] Close table 'client0.tdb' Apr 26 06:59:28 192.168.122.209 [53718.854235] [tdb] Close table 'sessions0.tdb' Apr 26 06:59:31 192.168.122.209 [53722.097957] [tdb] Close table 'cache0.tdb' Apr 26 06:59:31 192.168.122.209 [53722.372612] [tdb] Close table 'filter0.tdb' Apr 26 06:59:31 192.168.122.209 [53722.373320] [tempesta fw] modules are stopped Apr 26 06:59:32 192.168.122.209 [53722.571644] [tempesta fw] exiting... Apr 26 06:59:32 192.168.122.209 [53722.710780] [tdb] Shutdown Tempesta DB Apr 26 06:59:32 192.168.122.209 [53722.943192] End test: cache.test_cache.TestCacheMultipleMethodsH2.test_several_entries_POST_GET Apr 26 06:59:32 192.168.122.209 [53722.963561] Start test: cache.test_cache.TestCacheMultipleMethodsH2.test_several_entries_POST_HEAD Apr 26 06:59:33 192.168.122.209 [53724.133553] [tdb] Start Tempesta DB Apr 26 06:59:33 192.168.122.209 [53724.275501] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:59:35 192.168.122.209 [53725.742268] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53725.742268] Maybe that's fine, but it's worth checking the [53725.742268] config - if there is no relations between the [53725.742268] names, then host name confusion attack is possible. Apr 26 06:59:35 192.168.122.209 [53725.813015] [tempesta fw] Configuration processing is completed. Apr 26 06:59:35 192.168.122.209 [53725.867589] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:59:35 192.168.122.209 [53726.286868] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:59:35 192.168.122.209 [53726.313821] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:59:35 192.168.122.209 [53726.340122] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:59:35 192.168.122.209 [53726.429006] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:59:35 192.168.122.209 [53726.430758] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:59:35 192.168.122.209 [53726.468951] [tempesta fw] Tempesta FW is ready Apr 26 06:59:38 192.168.122.209 [53729.184740] [tdb] Close table 'client0.tdb' Apr 26 06:59:38 192.168.122.209 [53729.377141] [tdb] Close table 'sessions0.tdb' Apr 26 06:59:42 192.168.122.209 [53732.627779] [tdb] Close table 'cache0.tdb' Apr 26 06:59:42 192.168.122.209 [53732.855827] [tdb] Close table 'filter0.tdb' Apr 26 06:59:42 192.168.122.209 [53732.856311] [tempesta fw] modules are stopped Apr 26 06:59:42 192.168.122.209 [53733.046241] [tempesta fw] exiting... Apr 26 06:59:42 192.168.122.209 [53733.198792] [tdb] Shutdown Tempesta DB Apr 26 06:59:42 192.168.122.209 [53733.465388] End test: cache.test_cache.TestCacheMultipleMethodsH2.test_several_entries_POST_HEAD Apr 26 06:59:43 192.168.122.209 [53733.488729] Start test: cache.test_cache.TestCacheMultipleMethodsH2.test_several_entries_POST_POST Apr 26 06:59:44 192.168.122.209 [53734.561483] [tdb] Start Tempesta DB Apr 26 06:59:44 192.168.122.209 [53734.711043] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:59:45 192.168.122.209 [53736.166388] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53736.166388] Maybe that's fine, but it's worth checking the [53736.166388] config - if there is no relations between the [53736.166388] names, then host name confusion attack is possible. Apr 26 06:59:45 192.168.122.209 [53736.237145] [tempesta fw] Configuration processing is completed. Apr 26 06:59:45 192.168.122.209 [53736.295759] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:59:46 192.168.122.209 [53736.854374] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:59:46 192.168.122.209 [53736.888815] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:59:46 192.168.122.209 [53736.924256] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:59:46 192.168.122.209 [53736.973119] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:59:46 192.168.122.209 [53736.974524] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:59:46 192.168.122.209 [53737.021098] [tempesta fw] Tempesta FW is ready Apr 26 06:59:47 192.168.122.209 [53737.714809] [tdb] Close table 'client0.tdb' Apr 26 06:59:47 192.168.122.209 [53737.900269] [tdb] Close table 'sessions0.tdb' Apr 26 06:59:50 192.168.122.209 [53741.200520] [tdb] Close table 'cache0.tdb' Apr 26 06:59:50 192.168.122.209 [53741.458899] [tdb] Close table 'filter0.tdb' Apr 26 06:59:50 192.168.122.209 [53741.459351] [tempesta fw] modules are stopped Apr 26 06:59:51 192.168.122.209 [53741.692699] [tempesta fw] exiting... Apr 26 06:59:51 192.168.122.209 [53741.826782] [tdb] Shutdown Tempesta DB Apr 26 06:59:51 192.168.122.209 [53742.039988] End test: cache.test_cache.TestCacheMultipleMethodsH2.test_several_entries_POST_POST Apr 26 06:59:51 192.168.122.209 [53742.064252] Start test: cache.test_cache.TestCacheMultipleMethodsH2.test_update_cache_via_DELETE_request Apr 26 06:59:52 192.168.122.209 [53743.130710] [tdb] Start Tempesta DB Apr 26 06:59:52 192.168.122.209 [53743.285398] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 06:59:54 192.168.122.209 [53744.746580] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53744.746580] Maybe that's fine, but it's worth checking the [53744.746580] config - if there is no relations between the [53744.746580] names, then host name confusion attack is possible. Apr 26 06:59:54 192.168.122.209 [53744.809406] [tempesta fw] Configuration processing is completed. Apr 26 06:59:54 192.168.122.209 [53744.861569] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 06:59:54 192.168.122.209 [53745.283823] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 06:59:54 192.168.122.209 [53745.310887] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 06:59:54 192.168.122.209 [53745.336853] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 06:59:54 192.168.122.209 [53745.393222] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 06:59:54 192.168.122.209 [53745.394723] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 06:59:54 192.168.122.209 [53745.433195] [tempesta fw] Tempesta FW is ready Apr 26 06:59:55 192.168.122.209 [53746.118107] [tdb] Close table 'client0.tdb' Apr 26 06:59:55 192.168.122.209 [53746.312305] [tdb] Close table 'sessions0.tdb' Apr 26 06:59:59 192.168.122.209 [53749.666133] [tdb] Close table 'cache0.tdb' Apr 26 06:59:59 192.168.122.209 [53749.890579] [tdb] Close table 'filter0.tdb' Apr 26 06:59:59 192.168.122.209 [53749.891017] [tempesta fw] modules are stopped Apr 26 06:59:59 192.168.122.209 [53750.114625] [tempesta fw] exiting... Apr 26 06:59:59 192.168.122.209 [53750.236438] [tdb] Shutdown Tempesta DB Apr 26 06:59:59 192.168.122.209 [53750.477261] End test: cache.test_cache.TestCacheMultipleMethodsH2.test_update_cache_via_DELETE_request Apr 26 07:00:00 192.168.122.209 [53750.498491] Start test: cache.test_cache.TestCacheMultipleMethodsH2.test_update_cache_via_PUT_request Apr 26 07:00:01 192.168.122.209 [53751.600345] [tdb] Start Tempesta DB Apr 26 07:00:01 192.168.122.209 [53751.762031] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:00:02 192.168.122.209 [53753.290886] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53753.290886] Maybe that's fine, but it's worth checking the [53753.290886] config - if there is no relations between the [53753.290886] names, then host name confusion attack is possible. Apr 26 07:00:02 192.168.122.209 [53753.377318] [tempesta fw] Configuration processing is completed. Apr 26 07:00:02 192.168.122.209 [53753.431067] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:00:03 192.168.122.209 [53753.856802] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:00:03 192.168.122.209 [53753.883483] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:00:03 192.168.122.209 [53753.910756] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:00:03 192.168.122.209 [53753.957319] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:00:03 192.168.122.209 [53753.958702] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:00:03 192.168.122.209 [53754.001253] [tempesta fw] Tempesta FW is ready Apr 26 07:00:04 192.168.122.209 [53754.637997] [tdb] Close table 'client0.tdb' Apr 26 07:00:04 192.168.122.209 [53754.836973] [tdb] Close table 'sessions0.tdb' Apr 26 07:00:07 192.168.122.209 [53758.093358] [tdb] Close table 'cache0.tdb' Apr 26 07:00:07 192.168.122.209 [53758.341620] [tdb] Close table 'filter0.tdb' Apr 26 07:00:07 192.168.122.209 [53758.342053] [tempesta fw] modules are stopped Apr 26 07:00:08 192.168.122.209 [53758.542746] [tempesta fw] exiting... Apr 26 07:00:08 192.168.122.209 [53758.659753] [tdb] Shutdown Tempesta DB Apr 26 07:00:08 192.168.122.209 [53758.897059] End test: cache.test_cache.TestCacheMultipleMethodsH2.test_update_cache_via_PUT_request Apr 26 07:00:08 192.168.122.209 [53758.909565] Start test: cache.test_cache.TestCacheMultipleMethodsHttp.test_GET_after_GET Apr 26 07:00:09 192.168.122.209 [53759.985440] [tdb] Start Tempesta DB Apr 26 07:00:09 192.168.122.209 [53760.123826] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:00:11 192.168.122.209 [53761.650679] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53761.650679] Maybe that's fine, but it's worth checking the [53761.650679] config - if there is no relations between the [53761.650679] names, then host name confusion attack is possible. Apr 26 07:00:11 192.168.122.209 [53761.725438] [tempesta fw] Configuration processing is completed. Apr 26 07:00:11 192.168.122.209 [53761.783792] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:00:11 192.168.122.209 [53762.342245] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:00:11 192.168.122.209 [53762.376459] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:00:11 192.168.122.209 [53762.410580] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:00:11 192.168.122.209 [53762.457436] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:00:11 192.168.122.209 [53762.458607] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:00:12 192.168.122.209 [53762.501429] [tempesta fw] Tempesta FW is ready Apr 26 07:00:12 192.168.122.209 [53763.104806] [tdb] Close table 'client0.tdb' Apr 26 07:00:12 192.168.122.209 [53763.302578] [tdb] Close table 'sessions0.tdb' Apr 26 07:00:16 192.168.122.209 [53766.498640] [tdb] Close table 'cache0.tdb' Apr 26 07:00:16 192.168.122.209 [53766.745887] [tdb] Close table 'filter0.tdb' Apr 26 07:00:16 192.168.122.209 [53766.746326] [tempesta fw] modules are stopped Apr 26 07:00:16 192.168.122.209 [53766.918640] [tempesta fw] exiting... Apr 26 07:00:16 192.168.122.209 [53767.030604] [tdb] Shutdown Tempesta DB Apr 26 07:00:16 192.168.122.209 [53767.215284] End test: cache.test_cache.TestCacheMultipleMethodsHttp.test_GET_after_GET Apr 26 07:00:16 192.168.122.209 [53767.239967] Start test: cache.test_cache.TestCacheMultipleMethodsHttp.test_GET_after_HEAD Apr 26 07:00:17 192.168.122.209 [53768.339959] [tdb] Start Tempesta DB Apr 26 07:00:18 192.168.122.209 [53768.501522] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:00:19 192.168.122.209 [53770.162870] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53770.162870] Maybe that's fine, but it's worth checking the [53770.162870] config - if there is no relations between the [53770.162870] names, then host name confusion attack is possible. Apr 26 07:00:19 192.168.122.209 [53770.237557] [tempesta fw] Configuration processing is completed. Apr 26 07:00:19 192.168.122.209 [53770.290491] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:00:20 192.168.122.209 [53770.726693] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:00:20 192.168.122.209 [53770.754468] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:00:20 192.168.122.209 [53770.782965] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:00:20 192.168.122.209 [53770.833537] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:00:20 192.168.122.209 [53770.835245] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:00:20 192.168.122.209 [53770.877509] [tempesta fw] Tempesta FW is ready Apr 26 07:00:21 192.168.122.209 [53771.492923] [tdb] Close table 'client0.tdb' Apr 26 07:00:21 192.168.122.209 [53771.683330] [tdb] Close table 'sessions0.tdb' Apr 26 07:00:24 192.168.122.209 [53774.931330] [tdb] Close table 'cache0.tdb' Apr 26 07:00:24 192.168.122.209 [53775.207324] [tdb] Close table 'filter0.tdb' Apr 26 07:00:24 192.168.122.209 [53775.207769] [tempesta fw] modules are stopped Apr 26 07:00:24 192.168.122.209 [53775.390856] [tempesta fw] exiting... Apr 26 07:00:25 192.168.122.209 [53775.512661] [tdb] Shutdown Tempesta DB Apr 26 07:00:25 192.168.122.209 [53775.731257] End test: cache.test_cache.TestCacheMultipleMethodsHttp.test_GET_after_HEAD Apr 26 07:00:25 192.168.122.209 [53775.741702] Start test: cache.test_cache.TestCacheMultipleMethodsHttp.test_HEAD_after_GET Apr 26 07:00:26 192.168.122.209 [53776.856497] [tdb] Start Tempesta DB Apr 26 07:00:26 192.168.122.209 [53776.989542] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:00:27 192.168.122.209 [53778.470839] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53778.470839] Maybe that's fine, but it's worth checking the [53778.470839] config - if there is no relations between the [53778.470839] names, then host name confusion attack is possible. Apr 26 07:00:28 192.168.122.209 [53778.533660] [tempesta fw] Configuration processing is completed. Apr 26 07:00:28 192.168.122.209 [53778.583272] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:00:28 192.168.122.209 [53778.997368] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:00:28 192.168.122.209 [53779.023380] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:00:28 192.168.122.209 [53779.055511] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:00:28 192.168.122.209 [53779.101644] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:00:28 192.168.122.209 [53779.103011] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:00:28 192.168.122.209 [53779.161556] [tempesta fw] Tempesta FW is ready Apr 26 07:00:29 192.168.122.209 [53779.769203] [tdb] Close table 'client0.tdb' Apr 26 07:00:29 192.168.122.209 [53779.957167] [tdb] Close table 'sessions0.tdb' Apr 26 07:00:32 192.168.122.209 [53783.137792] [tdb] Close table 'cache0.tdb' Apr 26 07:00:32 192.168.122.209 [53783.407610] [tdb] Close table 'filter0.tdb' Apr 26 07:00:32 192.168.122.209 [53783.408046] [tempesta fw] modules are stopped Apr 26 07:00:33 192.168.122.209 [53783.577621] [tempesta fw] exiting... Apr 26 07:00:33 192.168.122.209 [53783.710837] [tdb] Shutdown Tempesta DB Apr 26 07:00:33 192.168.122.209 [53783.951525] End test: cache.test_cache.TestCacheMultipleMethodsHttp.test_HEAD_after_GET Apr 26 07:00:33 192.168.122.209 [53783.966928] Start test: cache.test_cache.TestCacheMultipleMethodsHttp.test_HEAD_after_HEAD Apr 26 07:00:34 192.168.122.209 [53785.000792] [tdb] Start Tempesta DB Apr 26 07:00:34 192.168.122.209 [53785.143889] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:00:36 192.168.122.209 [53786.695081] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53786.695081] Maybe that's fine, but it's worth checking the [53786.695081] config - if there is no relations between the [53786.695081] names, then host name confusion attack is possible. Apr 26 07:00:36 192.168.122.209 [53786.761798] [tempesta fw] Configuration processing is completed. Apr 26 07:00:36 192.168.122.209 [53786.816115] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:00:36 192.168.122.209 [53787.275004] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:00:36 192.168.122.209 [53787.303636] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:00:36 192.168.122.209 [53787.336312] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:00:36 192.168.122.209 [53787.381781] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:00:36 192.168.122.209 [53787.383274] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:00:36 192.168.122.209 [53787.425752] [tempesta fw] Tempesta FW is ready Apr 26 07:00:37 192.168.122.209 [53787.979320] [tdb] Close table 'client0.tdb' Apr 26 07:00:37 192.168.122.209 [53788.159276] [tdb] Close table 'sessions0.tdb' Apr 26 07:00:40 192.168.122.209 [53791.411954] [tdb] Close table 'cache0.tdb' Apr 26 07:00:41 192.168.122.209 [53791.679006] [tdb] Close table 'filter0.tdb' Apr 26 07:00:41 192.168.122.209 [53791.679453] [tempesta fw] modules are stopped Apr 26 07:00:41 192.168.122.209 [53791.904298] [tempesta fw] exiting... Apr 26 07:00:41 192.168.122.209 [53792.007438] [tdb] Shutdown Tempesta DB Apr 26 07:00:41 192.168.122.209 [53792.218084] End test: cache.test_cache.TestCacheMultipleMethodsHttp.test_HEAD_after_HEAD Apr 26 07:00:41 192.168.122.209 [53792.243800] Start test: cache.test_cache.TestCacheMultipleMethodsHttp.test_POST_after_GET Apr 26 07:00:42 192.168.122.209 [53793.389117] [tdb] Start Tempesta DB Apr 26 07:00:43 192.168.122.209 [53793.553011] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:00:44 192.168.122.209 [53795.171194] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53795.171194] Maybe that's fine, but it's worth checking the [53795.171194] config - if there is no relations between the [53795.171194] names, then host name confusion attack is possible. Apr 26 07:00:44 192.168.122.209 [53795.257902] [tempesta fw] Configuration processing is completed. Apr 26 07:00:44 192.168.122.209 [53795.308974] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:00:45 192.168.122.209 [53795.794629] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:00:45 192.168.122.209 [53795.836969] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:00:45 192.168.122.209 [53795.873151] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:00:45 192.168.122.209 [53795.921864] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:00:45 192.168.122.209 [53795.923285] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:00:45 192.168.122.209 [53795.961818] [tempesta fw] Tempesta FW is ready Apr 26 07:00:46 192.168.122.209 [53796.517006] [tdb] Close table 'client0.tdb' Apr 26 07:00:46 192.168.122.209 [53796.726630] [tdb] Close table 'sessions0.tdb' Apr 26 07:00:49 192.168.122.209 [53800.040388] [tdb] Close table 'cache0.tdb' Apr 26 07:00:49 192.168.122.209 [53800.271247] [tdb] Close table 'filter0.tdb' Apr 26 07:00:49 192.168.122.209 [53800.271671] [tempesta fw] modules are stopped Apr 26 07:00:50 192.168.122.209 [53800.495147] [tempesta fw] exiting... Apr 26 07:00:50 192.168.122.209 [53800.622068] [tdb] Shutdown Tempesta DB Apr 26 07:00:50 192.168.122.209 [53800.816434] End test: cache.test_cache.TestCacheMultipleMethodsHttp.test_POST_after_GET Apr 26 07:00:50 192.168.122.209 [53800.831197] Start test: cache.test_cache.TestCacheMultipleMethodsHttp.test_POST_after_HEAD Apr 26 07:00:51 192.168.122.209 [53801.836242] [tdb] Start Tempesta DB Apr 26 07:00:51 192.168.122.209 [53801.971930] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:00:53 192.168.122.209 [53803.483243] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53803.483243] Maybe that's fine, but it's worth checking the [53803.483243] config - if there is no relations between the [53803.483243] names, then host name confusion attack is possible. Apr 26 07:00:53 192.168.122.209 [53803.546423] [tempesta fw] Configuration processing is completed. Apr 26 07:00:53 192.168.122.209 [53803.595875] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:00:53 192.168.122.209 [53804.041338] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:00:53 192.168.122.209 [53804.075492] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:00:53 192.168.122.209 [53804.110307] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:00:53 192.168.122.209 [53804.145963] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:00:53 192.168.122.209 [53804.146740] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:00:53 192.168.122.209 [53804.197922] [tempesta fw] Tempesta FW is ready Apr 26 07:00:54 192.168.122.209 [53804.803882] [tdb] Close table 'client0.tdb' Apr 26 07:00:54 192.168.122.209 [53804.998940] [tdb] Close table 'sessions0.tdb' Apr 26 07:00:57 192.168.122.209 [53808.178679] [tdb] Close table 'cache0.tdb' Apr 26 07:00:57 192.168.122.209 [53808.425692] [tdb] Close table 'filter0.tdb' Apr 26 07:00:57 192.168.122.209 [53808.426752] [tempesta fw] modules are stopped Apr 26 07:00:58 192.168.122.209 [53808.648872] [tempesta fw] exiting... Apr 26 07:00:58 192.168.122.209 [53808.785761] [tdb] Shutdown Tempesta DB Apr 26 07:00:58 192.168.122.209 [53808.987513] End test: cache.test_cache.TestCacheMultipleMethodsHttp.test_POST_after_HEAD Apr 26 07:00:58 192.168.122.209 [53809.004196] Start test: cache.test_cache.TestCacheMultipleMethodsHttp.test_cache_POST_request_not_cached_no_cache_control Apr 26 07:00:59 192.168.122.209 [53810.061079] [tdb] Start Tempesta DB Apr 26 07:00:59 192.168.122.209 [53810.204003] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:01:01 192.168.122.209 [53811.707742] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53811.707742] Maybe that's fine, but it's worth checking the [53811.707742] config - if there is no relations between the [53811.707742] names, then host name confusion attack is possible. Apr 26 07:01:01 192.168.122.209 [53811.778088] [tempesta fw] Configuration processing is completed. Apr 26 07:01:01 192.168.122.209 [53811.837930] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:01:01 192.168.122.209 [53812.322023] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:01:01 192.168.122.209 [53812.357151] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:01:01 192.168.122.209 [53812.383035] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:01:02 192.168.122.209 [53812.588223] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:01:02 192.168.122.209 [53812.588943] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:01:02 192.168.122.209 [53812.861925] [tempesta fw] Tempesta FW is ready Apr 26 07:01:03 192.168.122.209 [53813.755174] [tdb] Close table 'client0.tdb' Apr 26 07:01:03 192.168.122.209 [53814.026813] [tdb] Close table 'sessions0.tdb' Apr 26 07:01:08 192.168.122.209 [53818.825032] [tdb] Close table 'cache0.tdb' Apr 26 07:01:08 192.168.122.209 [53819.264479] [tdb] Close table 'filter0.tdb' Apr 26 07:01:08 192.168.122.209 [53819.264911] [tempesta fw] modules are stopped Apr 26 07:01:09 192.168.122.209 [53819.483462] [tempesta fw] exiting... Apr 26 07:01:09 192.168.122.209 [53819.621650] [tdb] Shutdown Tempesta DB Apr 26 07:01:09 192.168.122.209 [53819.853685] End test: cache.test_cache.TestCacheMultipleMethodsHttp.test_cache_POST_request_not_cached_no_cache_control Apr 26 07:01:09 192.168.122.209 [53819.888943] Start test: cache.test_cache.TestCacheMultipleMethodsHttp.test_cache_POST_request_not_cached_not_same_location Apr 26 07:01:10 192.168.122.209 [53820.909035] [tdb] Start Tempesta DB Apr 26 07:01:10 192.168.122.209 [53821.054297] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:01:12 192.168.122.209 [53822.514997] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53822.514997] Maybe that's fine, but it's worth checking the [53822.514997] config - if there is no relations between the [53822.514997] names, then host name confusion attack is possible. Apr 26 07:01:12 192.168.122.209 [53822.574235] [tempesta fw] Configuration processing is completed. Apr 26 07:01:12 192.168.122.209 [53822.624578] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:01:12 192.168.122.209 [53823.046959] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:01:12 192.168.122.209 [53823.073401] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:01:12 192.168.122.209 [53823.100721] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:01:12 192.168.122.209 [53823.146217] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:01:12 192.168.122.209 [53823.147969] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:01:12 192.168.122.209 [53823.190162] [tempesta fw] Tempesta FW is ready Apr 26 07:01:13 192.168.122.209 [53823.804985] [tdb] Close table 'client0.tdb' Apr 26 07:01:13 192.168.122.209 [53823.998181] [tdb] Close table 'sessions0.tdb' Apr 26 07:01:16 192.168.122.209 [53827.253036] [tdb] Close table 'cache0.tdb' Apr 26 07:01:17 192.168.122.209 [53827.483122] [tdb] Close table 'filter0.tdb' Apr 26 07:01:17 192.168.122.209 [53827.483551] [tempesta fw] modules are stopped Apr 26 07:01:17 192.168.122.209 [53827.675791] [tempesta fw] exiting... Apr 26 07:01:17 192.168.122.209 [53827.788319] [tdb] Shutdown Tempesta DB Apr 26 07:01:17 192.168.122.209 [53827.985235] End test: cache.test_cache.TestCacheMultipleMethodsHttp.test_cache_POST_request_not_cached_not_same_location Apr 26 07:01:17 192.168.122.209 [53828.013574] Start test: cache.test_cache.TestCacheMultipleMethodsHttp.test_cache_POST_request_with_location_GET Apr 26 07:01:18 192.168.122.209 [53829.087867] [tdb] Start Tempesta DB Apr 26 07:01:18 192.168.122.209 [53829.224647] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:01:20 192.168.122.209 [53830.743544] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53830.743544] Maybe that's fine, but it's worth checking the [53830.743544] config - if there is no relations between the [53830.743544] names, then host name confusion attack is possible. Apr 26 07:01:20 192.168.122.209 [53830.818392] [tempesta fw] Configuration processing is completed. Apr 26 07:01:20 192.168.122.209 [53830.886537] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:01:20 192.168.122.209 [53831.304087] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:01:20 192.168.122.209 [53831.330476] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:01:20 192.168.122.209 [53831.357322] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:01:20 192.168.122.209 [53831.398342] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:01:20 192.168.122.209 [53831.400085] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:01:20 192.168.122.209 [53831.442270] [tempesta fw] Tempesta FW is ready Apr 26 07:01:21 192.168.122.209 [53832.019818] [tdb] Close table 'client0.tdb' Apr 26 07:01:21 192.168.122.209 [53832.201036] [tdb] Close table 'sessions0.tdb' Apr 26 07:01:24 192.168.122.209 [53835.368667] [tdb] Close table 'cache0.tdb' Apr 26 07:01:25 192.168.122.209 [53835.627006] [tdb] Close table 'filter0.tdb' Apr 26 07:01:25 192.168.122.209 [53835.627446] [tempesta fw] modules are stopped Apr 26 07:01:25 192.168.122.209 [53835.803367] [tempesta fw] exiting... Apr 26 07:01:25 192.168.122.209 [53835.905016] [tdb] Shutdown Tempesta DB Apr 26 07:01:25 192.168.122.209 [53836.127946] End test: cache.test_cache.TestCacheMultipleMethodsHttp.test_cache_POST_request_with_location_GET Apr 26 07:01:25 192.168.122.209 [53836.138889] Start test: cache.test_cache.TestCacheMultipleMethodsHttp.test_cache_POST_request_with_location_HEAD Apr 26 07:01:26 192.168.122.209 [53837.147907] [tdb] Start Tempesta DB Apr 26 07:01:26 192.168.122.209 [53837.288955] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:01:28 192.168.122.209 [53838.811649] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53838.811649] Maybe that's fine, but it's worth checking the [53838.811649] config - if there is no relations between the [53838.811649] names, then host name confusion attack is possible. Apr 26 07:01:28 192.168.122.209 [53838.882731] [tempesta fw] Configuration processing is completed. Apr 26 07:01:28 192.168.122.209 [53838.929781] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:01:28 192.168.122.209 [53839.355332] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:01:28 192.168.122.209 [53839.381889] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:01:28 192.168.122.209 [53839.409439] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:01:28 192.168.122.209 [53839.450367] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:01:28 192.168.122.209 [53839.451414] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:01:29 192.168.122.209 [53839.498387] [tempesta fw] Tempesta FW is ready Apr 26 07:01:29 192.168.122.209 [53840.075959] [tdb] Close table 'client0.tdb' Apr 26 07:01:29 192.168.122.209 [53840.261385] [tdb] Close table 'sessions0.tdb' Apr 26 07:01:32 192.168.122.209 [53843.444180] [tdb] Close table 'cache0.tdb' Apr 26 07:01:33 192.168.122.209 [53843.669708] [tdb] Close table 'filter0.tdb' Apr 26 07:01:33 192.168.122.209 [53843.670147] [tempesta fw] modules are stopped Apr 26 07:01:33 192.168.122.209 [53843.875832] [tempesta fw] exiting... Apr 26 07:01:33 192.168.122.209 [53843.975511] [tdb] Shutdown Tempesta DB Apr 26 07:01:33 192.168.122.209 [53844.208057] End test: cache.test_cache.TestCacheMultipleMethodsHttp.test_cache_POST_request_with_location_HEAD Apr 26 07:01:33 192.168.122.209 [53844.235825] Start test: cache.test_cache.TestCacheMultipleMethodsHttp.test_cache_POST_request_with_location_POST Apr 26 07:01:34 192.168.122.209 [53845.270143] [tdb] Start Tempesta DB Apr 26 07:01:34 192.168.122.209 [53845.412284] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:01:36 192.168.122.209 [53846.911658] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53846.911658] Maybe that's fine, but it's worth checking the [53846.911658] config - if there is no relations between the [53846.911658] names, then host name confusion attack is possible. Apr 26 07:01:36 192.168.122.209 [53846.974523] [tempesta fw] Configuration processing is completed. Apr 26 07:01:36 192.168.122.209 [53847.025106] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:01:36 192.168.122.209 [53847.444044] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:01:36 192.168.122.209 [53847.470236] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:01:37 192.168.122.209 [53847.499956] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:01:37 192.168.122.209 [53847.550475] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:01:37 192.168.122.209 [53847.551984] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:01:37 192.168.122.209 [53847.590483] [tempesta fw] Tempesta FW is ready Apr 26 07:01:37 192.168.122.209 [53848.203485] [tdb] Close table 'client0.tdb' Apr 26 07:01:37 192.168.122.209 [53848.398049] [tdb] Close table 'sessions0.tdb' Apr 26 07:01:41 192.168.122.209 [53851.607030] [tdb] Close table 'cache0.tdb' Apr 26 07:01:41 192.168.122.209 [53851.847907] [tdb] Close table 'filter0.tdb' Apr 26 07:01:41 192.168.122.209 [53851.848339] [tempesta fw] modules are stopped Apr 26 07:01:41 192.168.122.209 [53852.028458] [tempesta fw] exiting... Apr 26 07:01:41 192.168.122.209 [53852.144963] [tdb] Shutdown Tempesta DB Apr 26 07:01:41 192.168.122.209 [53852.368224] End test: cache.test_cache.TestCacheMultipleMethodsHttp.test_cache_POST_request_with_location_POST Apr 26 07:01:41 192.168.122.209 [53852.378254] Start test: cache.test_cache.TestCacheMultipleMethodsHttp.test_several_entries_GET_GET Apr 26 07:01:42 192.168.122.209 [53853.414756] [tdb] Start Tempesta DB Apr 26 07:01:43 192.168.122.209 [53853.566517] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:01:44 192.168.122.209 [53855.051873] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53855.051873] Maybe that's fine, but it's worth checking the [53855.051873] config - if there is no relations between the [53855.051873] names, then host name confusion attack is possible. Apr 26 07:01:44 192.168.122.209 [53855.126615] [tempesta fw] Configuration processing is completed. Apr 26 07:01:44 192.168.122.209 [53855.177429] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:01:45 192.168.122.209 [53855.598977] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:01:45 192.168.122.209 [53855.625299] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:01:45 192.168.122.209 [53855.652455] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:01:45 192.168.122.209 [53855.694564] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:01:45 192.168.122.209 [53855.695866] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:01:45 192.168.122.209 [53855.750571] [tempesta fw] Tempesta FW is ready Apr 26 07:01:47 192.168.122.209 [53858.391305] [tdb] Close table 'client0.tdb' Apr 26 07:01:48 192.168.122.209 [53858.590006] [tdb] Close table 'sessions0.tdb' Apr 26 07:01:51 192.168.122.209 [53861.772450] [tdb] Close table 'cache0.tdb' Apr 26 07:01:51 192.168.122.209 [53862.021787] [tdb] Close table 'filter0.tdb' Apr 26 07:01:51 192.168.122.209 [53862.022243] [tempesta fw] modules are stopped Apr 26 07:01:51 192.168.122.209 [53862.219627] [tempesta fw] exiting... Apr 26 07:01:51 192.168.122.209 [53862.336310] [tdb] Shutdown Tempesta DB Apr 26 07:01:52 192.168.122.209 [53862.543226] End test: cache.test_cache.TestCacheMultipleMethodsHttp.test_several_entries_GET_GET Apr 26 07:01:52 192.168.122.209 [53862.562062] Start test: cache.test_cache.TestCacheMultipleMethodsHttp.test_several_entries_GET_HEAD Apr 26 07:01:53 192.168.122.209 [53863.626640] [tdb] Start Tempesta DB Apr 26 07:01:53 192.168.122.209 [53863.782699] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:01:54 192.168.122.209 [53865.311892] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53865.311892] Maybe that's fine, but it's worth checking the [53865.311892] config - if there is no relations between the [53865.311892] names, then host name confusion attack is possible. Apr 26 07:01:54 192.168.122.209 [53865.390714] [tempesta fw] Configuration processing is completed. Apr 26 07:01:54 192.168.122.209 [53865.446505] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:01:55 192.168.122.209 [53865.861169] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:01:55 192.168.122.209 [53865.896255] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:01:55 192.168.122.209 [53865.922544] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:01:55 192.168.122.209 [53865.967633] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:01:55 192.168.122.209 [53865.969334] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:01:55 192.168.122.209 [53866.022707] [tempesta fw] Tempesta FW is ready Apr 26 07:01:58 192.168.122.209 [53868.749580] [tdb] Close table 'client0.tdb' Apr 26 07:01:58 192.168.122.209 [53868.932901] [tdb] Close table 'sessions0.tdb' Apr 26 07:02:01 192.168.122.209 [53872.128793] [tdb] Close table 'cache0.tdb' Apr 26 07:02:01 192.168.122.209 [53872.394166] [tdb] Close table 'filter0.tdb' Apr 26 07:02:01 192.168.122.209 [53872.394607] [tempesta fw] modules are stopped Apr 26 07:02:02 192.168.122.209 [53872.608226] [tempesta fw] exiting... Apr 26 07:02:02 192.168.122.209 [53872.757289] [tdb] Shutdown Tempesta DB Apr 26 07:02:02 192.168.122.209 [53872.955978] End test: cache.test_cache.TestCacheMultipleMethodsHttp.test_several_entries_GET_HEAD Apr 26 07:02:02 192.168.122.209 [53872.972885] Start test: cache.test_cache.TestCacheMultipleMethodsHttp.test_several_entries_GET_POST Apr 26 07:02:03 192.168.122.209 [53874.004499] [tdb] Start Tempesta DB Apr 26 07:02:03 192.168.122.209 [53874.153485] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:02:05 192.168.122.209 [53875.724166] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53875.724166] Maybe that's fine, but it's worth checking the [53875.724166] config - if there is no relations between the [53875.724166] names, then host name confusion attack is possible. Apr 26 07:02:05 192.168.122.209 [53875.802913] [tempesta fw] Configuration processing is completed. Apr 26 07:02:05 192.168.122.209 [53875.854076] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:02:05 192.168.122.209 [53876.279590] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:02:05 192.168.122.209 [53876.313608] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:02:05 192.168.122.209 [53876.341361] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:02:05 192.168.122.209 [53876.386835] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:02:05 192.168.122.209 [53876.388000] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:02:05 192.168.122.209 [53876.434837] [tempesta fw] Tempesta FW is ready Apr 26 07:02:06 192.168.122.209 [53877.041078] [tdb] Close table 'client0.tdb' Apr 26 07:02:06 192.168.122.209 [53877.229866] [tdb] Close table 'sessions0.tdb' Apr 26 07:02:09 192.168.122.209 [53880.370747] [tdb] Close table 'cache0.tdb' Apr 26 07:02:10 192.168.122.209 [53880.604049] [tdb] Close table 'filter0.tdb' Apr 26 07:02:10 192.168.122.209 [53880.604483] [tempesta fw] modules are stopped Apr 26 07:02:10 192.168.122.209 [53880.797797] [tempesta fw] exiting... Apr 26 07:02:10 192.168.122.209 [53880.893825] [tdb] Shutdown Tempesta DB Apr 26 07:02:10 192.168.122.209 [53881.100106] End test: cache.test_cache.TestCacheMultipleMethodsHttp.test_several_entries_GET_POST Apr 26 07:02:10 192.168.122.209 [53881.119498] Start test: cache.test_cache.TestCacheMultipleMethodsHttp.test_several_entries_POST_GET Apr 26 07:02:11 192.168.122.209 [53882.152691] [tdb] Start Tempesta DB Apr 26 07:02:11 192.168.122.209 [53882.278201] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:02:13 192.168.122.209 [53883.816229] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53883.816229] Maybe that's fine, but it's worth checking the [53883.816229] config - if there is no relations between the [53883.816229] names, then host name confusion attack is possible. Apr 26 07:02:13 192.168.122.209 [53883.871293] [tempesta fw] Configuration processing is completed. Apr 26 07:02:13 192.168.122.209 [53883.925280] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:02:13 192.168.122.209 [53884.350770] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:02:13 192.168.122.209 [53884.385315] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:02:13 192.168.122.209 [53884.411631] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:02:13 192.168.122.209 [53884.454921] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:02:13 192.168.122.209 [53884.455961] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:02:14 192.168.122.209 [53884.494948] [tempesta fw] Tempesta FW is ready Apr 26 07:02:16 192.168.122.209 [53887.150835] [tdb] Close table 'client0.tdb' Apr 26 07:02:16 192.168.122.209 [53887.329136] [tdb] Close table 'sessions0.tdb' Apr 26 07:02:20 192.168.122.209 [53890.521450] [tdb] Close table 'cache0.tdb' Apr 26 07:02:20 192.168.122.209 [53890.781794] [tdb] Close table 'filter0.tdb' Apr 26 07:02:20 192.168.122.209 [53890.782242] [tempesta fw] modules are stopped Apr 26 07:02:20 192.168.122.209 [53890.955126] [tempesta fw] exiting... Apr 26 07:02:20 192.168.122.209 [53891.075397] [tdb] Shutdown Tempesta DB Apr 26 07:02:20 192.168.122.209 [53891.292633] End test: cache.test_cache.TestCacheMultipleMethodsHttp.test_several_entries_POST_GET Apr 26 07:02:20 192.168.122.209 [53891.303655] Start test: cache.test_cache.TestCacheMultipleMethodsHttp.test_several_entries_POST_HEAD Apr 26 07:02:21 192.168.122.209 [53892.375843] [tdb] Start Tempesta DB Apr 26 07:02:22 192.168.122.209 [53892.511879] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:02:23 192.168.122.209 [53893.984413] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53893.984413] Maybe that's fine, but it's worth checking the [53893.984413] config - if there is no relations between the [53893.984413] names, then host name confusion attack is possible. Apr 26 07:02:23 192.168.122.209 [53894.051132] [tempesta fw] Configuration processing is completed. Apr 26 07:02:23 192.168.122.209 [53894.101596] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:02:24 192.168.122.209 [53894.522088] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:02:24 192.168.122.209 [53894.548220] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:02:24 192.168.122.209 [53894.575320] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:02:24 192.168.122.209 [53894.635139] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:02:24 192.168.122.209 [53894.636160] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:02:24 192.168.122.209 [53894.679070] [tempesta fw] Tempesta FW is ready Apr 26 07:02:26 192.168.122.209 [53897.305947] [tdb] Close table 'client0.tdb' Apr 26 07:02:27 192.168.122.209 [53897.502936] [tdb] Close table 'sessions0.tdb' Apr 26 07:02:30 192.168.122.209 [53900.725667] [tdb] Close table 'cache0.tdb' Apr 26 07:02:30 192.168.122.209 [53900.982270] [tdb] Close table 'filter0.tdb' Apr 26 07:02:30 192.168.122.209 [53900.982706] [tempesta fw] modules are stopped Apr 26 07:02:30 192.168.122.209 [53901.168330] [tempesta fw] exiting... Apr 26 07:02:30 192.168.122.209 [53901.302869] [tdb] Shutdown Tempesta DB Apr 26 07:02:31 192.168.122.209 [53901.517687] End test: cache.test_cache.TestCacheMultipleMethodsHttp.test_several_entries_POST_HEAD Apr 26 07:02:31 192.168.122.209 [53901.535271] Start test: cache.test_cache.TestCacheMultipleMethodsHttp.test_several_entries_POST_POST Apr 26 07:02:32 192.168.122.209 [53902.592789] [tdb] Start Tempesta DB Apr 26 07:02:32 192.168.122.209 [53902.735264] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:02:33 192.168.122.209 [53904.196488] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53904.196488] Maybe that's fine, but it's worth checking the [53904.196488] config - if there is no relations between the [53904.196488] names, then host name confusion attack is possible. Apr 26 07:02:33 192.168.122.209 [53904.271245] [tempesta fw] Configuration processing is completed. Apr 26 07:02:33 192.168.122.209 [53904.323028] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:02:34 192.168.122.209 [53904.755285] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:02:34 192.168.122.209 [53904.781444] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:02:34 192.168.122.209 [53904.807414] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:02:34 192.168.122.209 [53904.863250] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:02:34 192.168.122.209 [53904.864985] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:02:34 192.168.122.209 [53904.919208] [tempesta fw] Tempesta FW is ready Apr 26 07:02:35 192.168.122.209 [53905.538746] [tdb] Close table 'client0.tdb' Apr 26 07:02:35 192.168.122.209 [53905.744720] [tdb] Close table 'sessions0.tdb' Apr 26 07:02:38 192.168.122.209 [53908.935346] [tdb] Close table 'cache0.tdb' Apr 26 07:02:38 192.168.122.209 [53909.185205] [tdb] Close table 'filter0.tdb' Apr 26 07:02:38 192.168.122.209 [53909.185636] [tempesta fw] modules are stopped Apr 26 07:02:38 192.168.122.209 [53909.371242] [tempesta fw] exiting... Apr 26 07:02:39 192.168.122.209 [53909.505804] [tdb] Shutdown Tempesta DB Apr 26 07:02:39 192.168.122.209 [53909.725806] End test: cache.test_cache.TestCacheMultipleMethodsHttp.test_several_entries_POST_POST Apr 26 07:02:39 192.168.122.209 [53909.747083] Start test: cache.test_cache.TestCacheMultipleMethodsHttp.test_update_cache_via_DELETE_request Apr 26 07:02:40 192.168.122.209 [53910.851680] [tdb] Start Tempesta DB Apr 26 07:02:40 192.168.122.209 [53910.985331] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:02:42 192.168.122.209 [53912.592591] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53912.592591] Maybe that's fine, but it's worth checking the [53912.592591] config - if there is no relations between the [53912.592591] names, then host name confusion attack is possible. Apr 26 07:02:42 192.168.122.209 [53912.667405] [tempesta fw] Configuration processing is completed. Apr 26 07:02:42 192.168.122.209 [53912.715879] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:02:42 192.168.122.209 [53913.137294] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:02:42 192.168.122.209 [53913.163914] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:02:42 192.168.122.209 [53913.191446] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:02:42 192.168.122.209 [53913.243330] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:02:42 192.168.122.209 [53913.244873] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:02:42 192.168.122.209 [53913.291312] [tempesta fw] Tempesta FW is ready Apr 26 07:02:43 192.168.122.209 [53913.893599] [tdb] Close table 'client0.tdb' Apr 26 07:02:43 192.168.122.209 [53914.080463] [tdb] Close table 'sessions0.tdb' Apr 26 07:02:46 192.168.122.209 [53917.286870] [tdb] Close table 'cache0.tdb' Apr 26 07:02:47 192.168.122.209 [53917.551025] [tdb] Close table 'filter0.tdb' Apr 26 07:02:47 192.168.122.209 [53917.551474] [tempesta fw] modules are stopped Apr 26 07:02:47 192.168.122.209 [53917.751414] [tempesta fw] exiting... Apr 26 07:02:47 192.168.122.209 [53917.880018] [tdb] Shutdown Tempesta DB Apr 26 07:02:47 192.168.122.209 [53918.087471] End test: cache.test_cache.TestCacheMultipleMethodsHttp.test_update_cache_via_DELETE_request Apr 26 07:02:47 192.168.122.209 [53918.107274] Start test: cache.test_cache.TestCacheMultipleMethodsHttp.test_update_cache_via_PUT_request Apr 26 07:02:48 192.168.122.209 [53919.145377] [tdb] Start Tempesta DB Apr 26 07:02:48 192.168.122.209 [53919.286590] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:02:50 192.168.122.209 [53920.808706] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53920.808706] Maybe that's fine, but it's worth checking the [53920.808706] config - if there is no relations between the [53920.808706] names, then host name confusion attack is possible. Apr 26 07:02:50 192.168.122.209 [53920.883496] [tempesta fw] Configuration processing is completed. Apr 26 07:02:50 192.168.122.209 [53920.933975] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:02:50 192.168.122.209 [53921.357491] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:02:50 192.168.122.209 [53921.383849] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:02:50 192.168.122.209 [53921.418379] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:02:50 192.168.122.209 [53921.463455] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:02:50 192.168.122.209 [53921.465244] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:02:51 192.168.122.209 [53921.503413] [tempesta fw] Tempesta FW is ready Apr 26 07:02:51 192.168.122.209 [53922.094990] [tdb] Close table 'client0.tdb' Apr 26 07:02:51 192.168.122.209 [53922.294551] [tdb] Close table 'sessions0.tdb' Apr 26 07:02:55 192.168.122.209 [53925.503042] [tdb] Close table 'cache0.tdb' Apr 26 07:02:55 192.168.122.209 [53925.744980] [tdb] Close table 'filter0.tdb' Apr 26 07:02:55 192.168.122.209 [53925.745405] [tempesta fw] modules are stopped Apr 26 07:02:55 192.168.122.209 [53925.972952] [tempesta fw] exiting... Apr 26 07:02:55 192.168.122.209 [53926.115534] [tdb] Shutdown Tempesta DB Apr 26 07:02:55 192.168.122.209 [53926.315531] End test: cache.test_cache.TestCacheMultipleMethodsHttp.test_update_cache_via_PUT_request Apr 26 07:02:55 192.168.122.209 [53926.329469] Start test: cache.test_cache.TestCacheOverriddenHostH2.test Apr 26 07:02:56 192.168.122.209 [53927.351157] [tdb] Start Tempesta DB Apr 26 07:02:57 192.168.122.209 [53927.486531] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:02:58 192.168.122.209 [53929.052821] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53929.052821] Maybe that's fine, but it's worth checking the [53929.052821] config - if there is no relations between the [53929.052821] names, then host name confusion attack is possible. Apr 26 07:02:58 192.168.122.209 [53929.171509] [tempesta fw] Configuration processing is completed. Apr 26 07:02:58 192.168.122.209 [53929.219062] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:02:59 192.168.122.209 [53929.641021] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:02:59 192.168.122.209 [53929.667467] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:02:59 192.168.122.209 [53929.694817] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:02:59 192.168.122.209 [53929.739526] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:02:59 192.168.122.209 [53929.740614] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:02:59 192.168.122.209 [53929.779519] [tempesta fw] Tempesta FW is ready Apr 26 07:03:00 192.168.122.209 [53930.512527] [tdb] Close table 'client0.tdb' Apr 26 07:03:00 192.168.122.209 [53930.698934] [tdb] Close table 'sessions0.tdb' Apr 26 07:03:03 192.168.122.209 [53933.900217] [tdb] Close table 'cache0.tdb' Apr 26 07:03:03 192.168.122.209 [53934.139683] [tdb] Close table 'filter0.tdb' Apr 26 07:03:03 192.168.122.209 [53934.140120] [tempesta fw] modules are stopped Apr 26 07:03:03 192.168.122.209 [53934.340418] [tempesta fw] exiting... Apr 26 07:03:03 192.168.122.209 [53934.462034] [tdb] Shutdown Tempesta DB Apr 26 07:03:04 192.168.122.209 [53934.656737] End test: cache.test_cache.TestCacheOverriddenHostH2.test Apr 26 07:03:04 192.168.122.209 [53934.678008] Start test: cache.test_cache.TestCacheOverriddenHostHttp.test Apr 26 07:03:05 192.168.122.209 [53935.696645] [tdb] Start Tempesta DB Apr 26 07:03:05 192.168.122.209 [53935.833352] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:03:06 192.168.122.209 [53937.276905] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53937.276905] Maybe that's fine, but it's worth checking the [53937.276905] config - if there is no relations between the [53937.276905] names, then host name confusion attack is possible. Apr 26 07:03:06 192.168.122.209 [53937.403674] [tempesta fw] Configuration processing is completed. Apr 26 07:03:06 192.168.122.209 [53937.458584] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:03:07 192.168.122.209 [53937.879956] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:03:07 192.168.122.209 [53937.910745] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:03:07 192.168.122.209 [53937.936309] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:03:07 192.168.122.209 [53937.979671] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:03:07 192.168.122.209 [53937.981405] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:03:07 192.168.122.209 [53938.023648] [tempesta fw] Tempesta FW is ready Apr 26 07:03:08 192.168.122.209 [53938.683989] [tdb] Close table 'client0.tdb' Apr 26 07:03:08 192.168.122.209 [53938.873511] [tdb] Close table 'sessions0.tdb' Apr 26 07:03:11 192.168.122.209 [53942.099864] [tdb] Close table 'cache0.tdb' Apr 26 07:03:11 192.168.122.209 [53942.319762] [tdb] Close table 'filter0.tdb' Apr 26 07:03:11 192.168.122.209 [53942.320198] [tempesta fw] modules are stopped Apr 26 07:03:12 192.168.122.209 [53942.501252] [tempesta fw] exiting... Apr 26 07:03:12 192.168.122.209 [53942.640222] [tdb] Shutdown Tempesta DB Apr 26 07:03:12 192.168.122.209 [53942.849514] End test: cache.test_cache.TestCacheOverriddenHostHttp.test Apr 26 07:03:12 192.168.122.209 [53942.867281] Start test: cache.test_cache.TestCacheResponseWithCacheDifferentClients.test_GET_deproxy_deproxy_h2 Apr 26 07:03:13 192.168.122.209 [53943.919662] [tdb] Start Tempesta DB Apr 26 07:03:13 192.168.122.209 [53944.053803] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:03:15 192.168.122.209 [53945.629469] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53945.629469] Maybe that's fine, but it's worth checking the [53945.629469] config - if there is no relations between the [53945.629469] names, then host name confusion attack is possible. Apr 26 07:03:15 192.168.122.209 [53945.687794] [tempesta fw] Configuration processing is completed. Apr 26 07:03:15 192.168.122.209 [53945.738640] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:03:15 192.168.122.209 [53946.166525] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:03:15 192.168.122.209 [53946.194015] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:03:15 192.168.122.209 [53946.222302] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:03:15 192.168.122.209 [53946.275746] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:03:15 192.168.122.209 [53946.277292] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:03:15 192.168.122.209 [53946.327708] [tempesta fw] Tempesta FW is ready Apr 26 07:03:16 192.168.122.209 [53946.999883] [tdb] Close table 'client0.tdb' Apr 26 07:03:16 192.168.122.209 [53947.213403] [tdb] Close table 'sessions0.tdb' Apr 26 07:03:19 192.168.122.209 [53950.449378] [tdb] Close table 'cache0.tdb' Apr 26 07:03:20 192.168.122.209 [53950.704373] [tdb] Close table 'filter0.tdb' Apr 26 07:03:20 192.168.122.209 [53950.704810] [tempesta fw] modules are stopped Apr 26 07:03:20 192.168.122.209 [53950.889921] [tempesta fw] exiting... Apr 26 07:03:20 192.168.122.209 [53951.010459] [tdb] Shutdown Tempesta DB Apr 26 07:03:20 192.168.122.209 [53951.234940] End test: cache.test_cache.TestCacheResponseWithCacheDifferentClients.test_GET_deproxy_deproxy_h2 Apr 26 07:03:20 192.168.122.209 [53951.262713] Start test: cache.test_cache.TestCacheResponseWithCacheDifferentClients.test_GET_deproxy_h2_deproxy Apr 26 07:03:21 192.168.122.209 [53952.350163] [tdb] Start Tempesta DB Apr 26 07:03:22 192.168.122.209 [53952.509194] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:03:23 192.168.122.209 [53954.069575] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53954.069575] Maybe that's fine, but it's worth checking the [53954.069575] config - if there is no relations between the [53954.069575] names, then host name confusion attack is possible. Apr 26 07:03:23 192.168.122.209 [53954.112157] [tempesta fw] Configuration processing is completed. Apr 26 07:03:23 192.168.122.209 [53954.178333] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:03:24 192.168.122.209 [53954.654209] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:03:24 192.168.122.209 [53954.684393] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:03:24 192.168.122.209 [53954.714040] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:03:24 192.168.122.209 [53954.763875] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:03:24 192.168.122.209 [53954.765651] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:03:24 192.168.122.209 [53954.819844] [tempesta fw] Tempesta FW is ready Apr 26 07:03:25 192.168.122.209 [53955.506276] [tdb] Close table 'client0.tdb' Apr 26 07:03:25 192.168.122.209 [53955.738943] [tdb] Close table 'sessions0.tdb' Apr 26 07:03:28 192.168.122.209 [53958.970250] [tdb] Close table 'cache0.tdb' Apr 26 07:03:28 192.168.122.209 [53959.209665] [tdb] Close table 'filter0.tdb' Apr 26 07:03:28 192.168.122.209 [53959.210096] [tempesta fw] modules are stopped Apr 26 07:03:28 192.168.122.209 [53959.404839] [tempesta fw] exiting... Apr 26 07:03:29 192.168.122.209 [53959.537560] [tdb] Shutdown Tempesta DB Apr 26 07:03:29 192.168.122.209 [53959.764214] End test: cache.test_cache.TestCacheResponseWithCacheDifferentClients.test_GET_deproxy_h2_deproxy Apr 26 07:03:29 192.168.122.209 [53959.775447] Start test: cache.test_cache.TestCacheResponseWithCacheDifferentClients.test_HEAD_deproxy_deproxy_h2 Apr 26 07:03:30 192.168.122.209 [53960.810229] [tdb] Start Tempesta DB Apr 26 07:03:30 192.168.122.209 [53960.965981] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:03:32 192.168.122.209 [53962.513791] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53962.513791] Maybe that's fine, but it's worth checking the [53962.513791] config - if there is no relations between the [53962.513791] names, then host name confusion attack is possible. Apr 26 07:03:32 192.168.122.209 [53962.556204] [tempesta fw] Configuration processing is completed. Apr 26 07:03:32 192.168.122.209 [53962.613773] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:03:32 192.168.122.209 [53963.064935] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:03:32 192.168.122.209 [53963.092846] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:03:32 192.168.122.209 [53963.120502] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:03:32 192.168.122.209 [53963.163974] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:03:32 192.168.122.209 [53963.165137] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:03:32 192.168.122.209 [53963.207927] [tempesta fw] Tempesta FW is ready Apr 26 07:03:33 192.168.122.209 [53963.930262] [tdb] Close table 'client0.tdb' Apr 26 07:03:33 192.168.122.209 [53964.122192] [tdb] Close table 'sessions0.tdb' Apr 26 07:03:37 192.168.122.209 [53967.522745] [tdb] Close table 'cache0.tdb' Apr 26 07:03:37 192.168.122.209 [53967.782811] [tdb] Close table 'filter0.tdb' Apr 26 07:03:37 192.168.122.209 [53967.783268] [tempesta fw] modules are stopped Apr 26 07:03:37 192.168.122.209 [53967.975068] [tempesta fw] exiting... Apr 26 07:03:37 192.168.122.209 [53968.106707] [tdb] Shutdown Tempesta DB Apr 26 07:03:37 192.168.122.209 [53968.329094] End test: cache.test_cache.TestCacheResponseWithCacheDifferentClients.test_HEAD_deproxy_deproxy_h2 Apr 26 07:03:37 192.168.122.209 [53968.339063] Start test: cache.test_cache.TestCacheResponseWithCacheDifferentClients.test_HEAD_deproxy_h2_deproxy Apr 26 07:03:38 192.168.122.209 [53969.476143] [tdb] Start Tempesta DB Apr 26 07:03:39 192.168.122.209 [53969.630343] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:03:40 192.168.122.209 [53971.205809] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53971.205809] Maybe that's fine, but it's worth checking the [53971.205809] config - if there is no relations between the [53971.205809] names, then host name confusion attack is possible. Apr 26 07:03:40 192.168.122.209 [53971.252353] [tempesta fw] Configuration processing is completed. Apr 26 07:03:40 192.168.122.209 [53971.303577] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:03:41 192.168.122.209 [53971.724037] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:03:41 192.168.122.209 [53971.750202] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:03:41 192.168.122.209 [53971.777837] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:03:41 192.168.122.209 [53971.828113] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:03:41 192.168.122.209 [53971.829907] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:03:41 192.168.122.209 [53971.884024] [tempesta fw] Tempesta FW is ready Apr 26 07:03:42 192.168.122.209 [53972.583010] [tdb] Close table 'client0.tdb' Apr 26 07:03:42 192.168.122.209 [53972.780843] [tdb] Close table 'sessions0.tdb' Apr 26 07:03:45 192.168.122.209 [53976.202138] [tdb] Close table 'cache0.tdb' Apr 26 07:03:45 192.168.122.209 [53976.436500] [tdb] Close table 'filter0.tdb' Apr 26 07:03:45 192.168.122.209 [53976.436932] [tempesta fw] modules are stopped Apr 26 07:03:46 192.168.122.209 [53976.626317] [tempesta fw] exiting... Apr 26 07:03:46 192.168.122.209 [53976.755994] [tdb] Shutdown Tempesta DB Apr 26 07:03:46 192.168.122.209 [53976.968995] End test: cache.test_cache.TestCacheResponseWithCacheDifferentClients.test_HEAD_deproxy_h2_deproxy Apr 26 07:03:46 192.168.122.209 [53976.993719] Start test: cache.test_cache.TestCacheResponseWithTrailersH2.test_GET_GET Apr 26 07:03:47 192.168.122.209 [53978.100326] [tdb] Start Tempesta DB Apr 26 07:03:47 192.168.122.209 [53978.261664] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:03:49 192.168.122.209 [53979.874091] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53979.874091] Maybe that's fine, but it's worth checking the [53979.874091] config - if there is no relations between the [53979.874091] names, then host name confusion attack is possible. Apr 26 07:03:49 192.168.122.209 [53979.912434] [tempesta fw] Configuration processing is completed. Apr 26 07:03:49 192.168.122.209 [53979.966358] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:03:49 192.168.122.209 [53980.430591] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:03:49 192.168.122.209 [53980.472235] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:03:50 192.168.122.209 [53980.501276] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:03:50 192.168.122.209 [53980.548187] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:03:50 192.168.122.209 [53980.549652] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:03:50 192.168.122.209 [53980.588146] [tempesta fw] Tempesta FW is ready Apr 26 07:03:50 192.168.122.209 [53981.234032] [tdb] Close table 'client0.tdb' Apr 26 07:03:50 192.168.122.209 [53981.412445] [tdb] Close table 'sessions0.tdb' Apr 26 07:03:54 192.168.122.209 [53984.659035] [tdb] Close table 'cache0.tdb' Apr 26 07:03:54 192.168.122.209 [53984.898286] [tdb] Close table 'filter0.tdb' Apr 26 07:03:54 192.168.122.209 [53984.898713] [tempesta fw] modules are stopped Apr 26 07:03:54 192.168.122.209 [53985.135349] [tempesta fw] exiting... Apr 26 07:03:54 192.168.122.209 [53985.261079] [tdb] Shutdown Tempesta DB Apr 26 07:03:54 192.168.122.209 [53985.470822] End test: cache.test_cache.TestCacheResponseWithTrailersH2.test_GET_GET Apr 26 07:03:55 192.168.122.209 [53985.492563] Start test: cache.test_cache.TestCacheResponseWithTrailersH2.test_GET_HEAD Apr 26 07:03:56 192.168.122.209 [53986.541375] [tdb] Start Tempesta DB Apr 26 07:03:56 192.168.122.209 [53986.684215] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:03:57 192.168.122.209 [53988.229972] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53988.229972] Maybe that's fine, but it's worth checking the [53988.229972] config - if there is no relations between the [53988.229972] names, then host name confusion attack is possible. Apr 26 07:03:57 192.168.122.209 [53988.276577] [tempesta fw] Configuration processing is completed. Apr 26 07:03:57 192.168.122.209 [53988.326412] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:03:58 192.168.122.209 [53988.739495] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:03:58 192.168.122.209 [53988.765831] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:03:58 192.168.122.209 [53988.793049] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:03:58 192.168.122.209 [53988.856331] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:03:58 192.168.122.209 [53988.858132] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:03:58 192.168.122.209 [53988.896295] [tempesta fw] Tempesta FW is ready Apr 26 07:03:59 192.168.122.209 [53989.595007] [tdb] Close table 'client0.tdb' Apr 26 07:03:59 192.168.122.209 [53989.776271] [tdb] Close table 'sessions0.tdb' Apr 26 07:04:02 192.168.122.209 [53992.957346] [tdb] Close table 'cache0.tdb' Apr 26 07:04:02 192.168.122.209 [53993.202977] [tdb] Close table 'filter0.tdb' Apr 26 07:04:02 192.168.122.209 [53993.203413] [tempesta fw] modules are stopped Apr 26 07:04:02 192.168.122.209 [53993.391697] [tempesta fw] exiting... Apr 26 07:04:03 192.168.122.209 [53993.534656] [tdb] Shutdown Tempesta DB Apr 26 07:04:03 192.168.122.209 [53993.778700] End test: cache.test_cache.TestCacheResponseWithTrailersH2.test_GET_HEAD Apr 26 07:04:03 192.168.122.209 [53993.788730] Start test: cache.test_cache.TestCacheResponseWithTrailersH2.test_HEAD_GET Apr 26 07:04:04 192.168.122.209 [53994.830504] [tdb] Start Tempesta DB Apr 26 07:04:04 192.168.122.209 [53994.969964] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:04:06 192.168.122.209 [53996.518060] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [53996.518060] Maybe that's fine, but it's worth checking the [53996.518060] config - if there is no relations between the [53996.518060] names, then host name confusion attack is possible. Apr 26 07:04:06 192.168.122.209 [53996.568659] [tempesta fw] Configuration processing is completed. Apr 26 07:04:06 192.168.122.209 [53996.618749] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:04:06 192.168.122.209 [53997.049572] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:04:06 192.168.122.209 [53997.076130] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:04:06 192.168.122.209 [53997.103391] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:04:06 192.168.122.209 [53997.184409] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:04:06 192.168.122.209 [53997.186187] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:04:06 192.168.122.209 [53997.240383] [tempesta fw] Tempesta FW is ready Apr 26 07:04:07 192.168.122.209 [53997.946975] [tdb] Close table 'client0.tdb' Apr 26 07:04:07 192.168.122.209 [53998.134594] [tdb] Close table 'sessions0.tdb' Apr 26 07:04:10 192.168.122.209 [54001.287138] [tdb] Close table 'cache0.tdb' Apr 26 07:04:11 192.168.122.209 [54001.528346] [tdb] Close table 'filter0.tdb' Apr 26 07:04:11 192.168.122.209 [54001.528782] [tempesta fw] modules are stopped Apr 26 07:04:11 192.168.122.209 [54001.737009] [tempesta fw] exiting... Apr 26 07:04:11 192.168.122.209 [54001.865992] [tdb] Shutdown Tempesta DB Apr 26 07:04:11 192.168.122.209 [54002.079752] End test: cache.test_cache.TestCacheResponseWithTrailersH2.test_HEAD_GET Apr 26 07:04:11 192.168.122.209 [54002.093374] Start test: cache.test_cache.TestCacheResponseWithTrailersH2.test_HEAD_HEAD Apr 26 07:04:12 192.168.122.209 [54003.138210] [tdb] Start Tempesta DB Apr 26 07:04:12 192.168.122.209 [54003.265891] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:04:14 192.168.122.209 [54004.834815] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54004.834815] Maybe that's fine, but it's worth checking the [54004.834815] config - if there is no relations between the [54004.834815] names, then host name confusion attack is possible. Apr 26 07:04:14 192.168.122.209 [54004.872689] [tempesta fw] Configuration processing is completed. Apr 26 07:04:14 192.168.122.209 [54004.923900] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:04:14 192.168.122.209 [54005.345245] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:04:14 192.168.122.209 [54005.371541] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:04:14 192.168.122.209 [54005.398822] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:04:14 192.168.122.209 [54005.440482] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:04:14 192.168.122.209 [54005.441610] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:04:15 192.168.122.209 [54005.484466] [tempesta fw] Tempesta FW is ready Apr 26 07:04:15 192.168.122.209 [54006.149329] [tdb] Close table 'client0.tdb' Apr 26 07:04:15 192.168.122.209 [54006.349668] [tdb] Close table 'sessions0.tdb' Apr 26 07:04:19 192.168.122.209 [54009.555650] [tdb] Close table 'cache0.tdb' Apr 26 07:04:19 192.168.122.209 [54009.778699] [tdb] Close table 'filter0.tdb' Apr 26 07:04:19 192.168.122.209 [54009.779126] [tempesta fw] modules are stopped Apr 26 07:04:19 192.168.122.209 [54009.965247] [tempesta fw] exiting... Apr 26 07:04:19 192.168.122.209 [54010.097531] [tdb] Shutdown Tempesta DB Apr 26 07:04:19 192.168.122.209 [54010.341515] End test: cache.test_cache.TestCacheResponseWithTrailersH2.test_HEAD_HEAD Apr 26 07:04:19 192.168.122.209 [54010.355491] Start test: cache.test_cache.TestCacheResponseWithTrailersH2.test_empty_body_head_to_get Apr 26 07:04:20 192.168.122.209 [54011.406516] [tdb] Start Tempesta DB Apr 26 07:04:21 192.168.122.209 [54011.550645] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:04:22 192.168.122.209 [54013.074346] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54013.074346] Maybe that's fine, but it's worth checking the [54013.074346] config - if there is no relations between the [54013.074346] names, then host name confusion attack is possible. Apr 26 07:04:22 192.168.122.209 [54013.120899] [tempesta fw] Configuration processing is completed. Apr 26 07:04:22 192.168.122.209 [54013.171859] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:04:23 192.168.122.209 [54013.601476] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:04:23 192.168.122.209 [54013.627550] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:04:23 192.168.122.209 [54013.653462] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:04:23 192.168.122.209 [54013.696584] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:04:23 192.168.122.209 [54013.697953] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:04:23 192.168.122.209 [54013.748562] [tempesta fw] Tempesta FW is ready Apr 26 07:04:23 192.168.122.209 [54014.438449] [tdb] Close table 'client0.tdb' Apr 26 07:04:24 192.168.122.209 [54014.628091] [tdb] Close table 'sessions0.tdb' Apr 26 07:04:27 192.168.122.209 [54017.974427] [tdb] Close table 'cache0.tdb' Apr 26 07:04:27 192.168.122.209 [54018.207631] [tdb] Close table 'filter0.tdb' Apr 26 07:04:27 192.168.122.209 [54018.208058] [tempesta fw] modules are stopped Apr 26 07:04:27 192.168.122.209 [54018.437408] [tempesta fw] exiting... Apr 26 07:04:28 192.168.122.209 [54018.558185] [tdb] Shutdown Tempesta DB Apr 26 07:04:28 192.168.122.209 [54018.802107] End test: cache.test_cache.TestCacheResponseWithTrailersH2.test_empty_body_head_to_get Apr 26 07:04:28 192.168.122.209 [54018.813075] Start test: cache.test_cache.TestCacheResponseWithTrailersH2.test_hbh_headers_hbp_GET Apr 26 07:04:29 192.168.122.209 [54019.846804] [tdb] Start Tempesta DB Apr 26 07:04:29 192.168.122.209 [54019.977871] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:04:31 192.168.122.209 [54021.494394] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54021.494394] Maybe that's fine, but it's worth checking the [54021.494394] config - if there is no relations between the [54021.494394] names, then host name confusion attack is possible. Apr 26 07:04:31 192.168.122.209 [54021.544798] [tempesta fw] Configuration processing is completed. Apr 26 07:04:31 192.168.122.209 [54021.594926] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:04:31 192.168.122.209 [54022.016831] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:04:31 192.168.122.209 [54022.043243] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:04:31 192.168.122.209 [54022.070623] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:04:31 192.168.122.209 [54022.116698] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:04:31 192.168.122.209 [54022.118018] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:04:31 192.168.122.209 [54022.164684] [tempesta fw] Tempesta FW is ready Apr 26 07:04:31 192.168.122.209 [54022.403146] [tempesta fw] Warning: Parser error: state=Resp_HdrConnectionV input(-0)=0xd(' ') data_len=1 off=0 Apr 26 07:04:31 192.168.122.209 [54022.404274] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 07:04:32 192.168.122.209 [54022.853238] [tdb] Close table 'client0.tdb' Apr 26 07:04:32 192.168.122.209 [54023.033548] [tdb] Close table 'sessions0.tdb' Apr 26 07:04:35 192.168.122.209 [54026.210868] [tdb] Close table 'cache0.tdb' Apr 26 07:04:35 192.168.122.209 [54026.464629] [tdb] Close table 'filter0.tdb' Apr 26 07:04:35 192.168.122.209 [54026.465065] [tempesta fw] modules are stopped Apr 26 07:04:36 192.168.122.209 [54026.653381] [tempesta fw] exiting... Apr 26 07:04:36 192.168.122.209 [54026.767246] [tdb] Shutdown Tempesta DB Apr 26 07:04:36 192.168.122.209 [54026.975855] End test: cache.test_cache.TestCacheResponseWithTrailersH2.test_hbh_headers_hbp_GET Apr 26 07:04:36 192.168.122.209 [54026.998404] Start test: cache.test_cache.TestCacheResponseWithTrailersH2.test_hbh_headers_hbp_HEAD Apr 26 07:04:37 192.168.122.209 [54028.030394] [tdb] Start Tempesta DB Apr 26 07:04:37 192.168.122.209 [54028.155936] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:04:39 192.168.122.209 [54029.726586] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54029.726586] Maybe that's fine, but it's worth checking the [54029.726586] config - if there is no relations between the [54029.726586] names, then host name confusion attack is possible. Apr 26 07:04:39 192.168.122.209 [54029.773065] [tempesta fw] Configuration processing is completed. Apr 26 07:04:39 192.168.122.209 [54029.825338] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:04:39 192.168.122.209 [54030.255095] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:04:39 192.168.122.209 [54030.280848] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:04:39 192.168.122.209 [54030.305962] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:04:39 192.168.122.209 [54030.344847] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:04:39 192.168.122.209 [54030.346550] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:04:39 192.168.122.209 [54030.416806] [tempesta fw] Tempesta FW is ready Apr 26 07:04:40 192.168.122.209 [54030.642968] [tempesta fw] Warning: Parser error: state=Resp_HdrConnectionV input(-0)=0xd(' ') data_len=1 off=0 Apr 26 07:04:40 192.168.122.209 [54030.644296] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 07:04:40 192.168.122.209 [54031.072111] [tdb] Close table 'client0.tdb' Apr 26 07:04:40 192.168.122.209 [54031.257061] [tdb] Close table 'sessions0.tdb' Apr 26 07:04:43 192.168.122.209 [54034.449410] [tdb] Close table 'cache0.tdb' Apr 26 07:04:44 192.168.122.209 [54034.721029] [tdb] Close table 'filter0.tdb' Apr 26 07:04:44 192.168.122.209 [54034.721455] [tempesta fw] modules are stopped Apr 26 07:04:44 192.168.122.209 [54034.913008] [tempesta fw] exiting... Apr 26 07:04:44 192.168.122.209 [54035.042520] [tdb] Shutdown Tempesta DB Apr 26 07:04:44 192.168.122.209 [54035.234441] End test: cache.test_cache.TestCacheResponseWithTrailersH2.test_hbh_headers_hbp_HEAD Apr 26 07:04:44 192.168.122.209 [54035.265950] Start test: cache.test_cache.TestCacheResponseWithTrailersH2.test_hbh_headers_mix_GET Apr 26 07:04:45 192.168.122.209 [54036.373886] [tdb] Start Tempesta DB Apr 26 07:04:46 192.168.122.209 [54036.502080] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:04:47 192.168.122.209 [54037.986572] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54037.986572] Maybe that's fine, but it's worth checking the [54037.986572] config - if there is no relations between the [54037.986572] names, then host name confusion attack is possible. Apr 26 07:04:47 192.168.122.209 [54038.049199] [tempesta fw] Configuration processing is completed. Apr 26 07:04:47 192.168.122.209 [54038.098704] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:04:48 192.168.122.209 [54038.517655] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:04:48 192.168.122.209 [54038.543742] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:04:48 192.168.122.209 [54038.571045] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:04:48 192.168.122.209 [54038.620921] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:04:48 192.168.122.209 [54038.622676] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:04:48 192.168.122.209 [54038.676903] [tempesta fw] Tempesta FW is ready Apr 26 07:04:48 192.168.122.209 [54038.923908] [tempesta fw] Warning: Parser error: state=Resp_HdrConnectionV input(-0)=0xd(' ') data_len=1 off=0 Apr 26 07:04:48 192.168.122.209 [54038.925067] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 07:04:48 192.168.122.209 [54039.317337] [tdb] Close table 'client0.tdb' Apr 26 07:04:49 192.168.122.209 [54039.485529] [tdb] Close table 'sessions0.tdb' Apr 26 07:04:52 192.168.122.209 [54042.714462] [tdb] Close table 'cache0.tdb' Apr 26 07:04:52 192.168.122.209 [54042.978409] [tdb] Close table 'filter0.tdb' Apr 26 07:04:52 192.168.122.209 [54042.978830] [tempesta fw] modules are stopped Apr 26 07:04:52 192.168.122.209 [54043.204147] [tempesta fw] exiting... Apr 26 07:04:52 192.168.122.209 [54043.330486] [tdb] Shutdown Tempesta DB Apr 26 07:04:53 192.168.122.209 [54043.560311] End test: cache.test_cache.TestCacheResponseWithTrailersH2.test_hbh_headers_mix_GET Apr 26 07:04:53 192.168.122.209 [54043.581694] Start test: cache.test_cache.TestCacheResponseWithTrailersH2.test_hbh_headers_mix_HEAD Apr 26 07:04:54 192.168.122.209 [54044.629644] [tdb] Start Tempesta DB Apr 26 07:04:54 192.168.122.209 [54044.767671] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:04:55 192.168.122.209 [54046.271427] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54046.271427] Maybe that's fine, but it's worth checking the [54046.271427] config - if there is no relations between the [54046.271427] names, then host name confusion attack is possible. Apr 26 07:04:55 192.168.122.209 [54046.333485] [tempesta fw] Configuration processing is completed. Apr 26 07:04:55 192.168.122.209 [54046.383949] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:04:56 192.168.122.209 [54046.807513] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:04:56 192.168.122.209 [54046.833842] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:04:56 192.168.122.209 [54046.859725] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:04:56 192.168.122.209 [54046.913055] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:04:56 192.168.122.209 [54046.914789] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:04:56 192.168.122.209 [54046.952985] [tempesta fw] Tempesta FW is ready Apr 26 07:04:56 192.168.122.209 [54047.209413] [tempesta fw] Warning: Parser error: state=Resp_HdrConnectionV input(-0)=0xd(' ') data_len=1 off=0 Apr 26 07:04:56 192.168.122.209 [54047.210579] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 07:04:57 192.168.122.209 [54047.586084] [tdb] Close table 'client0.tdb' Apr 26 07:04:57 192.168.122.209 [54047.786691] [tdb] Close table 'sessions0.tdb' Apr 26 07:05:00 192.168.122.209 [54050.941978] [tdb] Close table 'cache0.tdb' Apr 26 07:05:00 192.168.122.209 [54051.184601] [tdb] Close table 'filter0.tdb' Apr 26 07:05:00 192.168.122.209 [54051.185040] [tempesta fw] modules are stopped Apr 26 07:05:00 192.168.122.209 [54051.393100] [tempesta fw] exiting... Apr 26 07:05:01 192.168.122.209 [54051.509801] [tdb] Shutdown Tempesta DB Apr 26 07:05:01 192.168.122.209 [54051.736750] End test: cache.test_cache.TestCacheResponseWithTrailersH2.test_hbh_headers_mix_HEAD Apr 26 07:05:01 192.168.122.209 [54051.768325] Start test: cache.test_cache.TestCacheResponseWithTrailersH2.test_same_hdr_and_trailer_head_to_get Apr 26 07:05:02 192.168.122.209 [54052.807859] [tdb] Start Tempesta DB Apr 26 07:05:02 192.168.122.209 [54052.956428] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:05:04 192.168.122.209 [54054.570799] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54054.570799] Maybe that's fine, but it's worth checking the [54054.570799] config - if there is no relations between the [54054.570799] names, then host name confusion attack is possible. Apr 26 07:05:04 192.168.122.209 [54054.613369] [tempesta fw] Configuration processing is completed. Apr 26 07:05:04 192.168.122.209 [54054.664470] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:05:04 192.168.122.209 [54055.094783] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:05:04 192.168.122.209 [54055.121179] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:05:04 192.168.122.209 [54055.148536] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:05:04 192.168.122.209 [54055.197105] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:05:04 192.168.122.209 [54055.198532] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:05:04 192.168.122.209 [54055.241112] [tempesta fw] Tempesta FW is ready Apr 26 07:05:05 192.168.122.209 [54055.907044] [tdb] Close table 'client0.tdb' Apr 26 07:05:05 192.168.122.209 [54056.093699] [tdb] Close table 'sessions0.tdb' Apr 26 07:05:08 192.168.122.209 [54059.279709] [tdb] Close table 'cache0.tdb' Apr 26 07:05:09 192.168.122.209 [54059.511410] [tdb] Close table 'filter0.tdb' Apr 26 07:05:09 192.168.122.209 [54059.511838] [tempesta fw] modules are stopped Apr 26 07:05:09 192.168.122.209 [54059.698742] [tempesta fw] exiting... Apr 26 07:05:09 192.168.122.209 [54059.838308] [tdb] Shutdown Tempesta DB Apr 26 07:05:09 192.168.122.209 [54060.054499] End test: cache.test_cache.TestCacheResponseWithTrailersH2.test_same_hdr_and_trailer_head_to_get Apr 26 07:05:09 192.168.122.209 [54060.078156] Start test: cache.test_cache.TestCacheResponseWithTrailersH2.test_same_hdr_and_trailer_head_to_get_multiple_1 Apr 26 07:05:10 192.168.122.209 [54061.075450] [tdb] Start Tempesta DB Apr 26 07:05:10 192.168.122.209 [54061.219355] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:05:12 192.168.122.209 [54062.778970] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54062.778970] Maybe that's fine, but it's worth checking the [54062.778970] config - if there is no relations between the [54062.778970] names, then host name confusion attack is possible. Apr 26 07:05:12 192.168.122.209 [54062.841224] [tempesta fw] Configuration processing is completed. Apr 26 07:05:12 192.168.122.209 [54062.891805] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:05:12 192.168.122.209 [54063.311816] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:05:12 192.168.122.209 [54063.350736] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:05:12 192.168.122.209 [54063.376819] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:05:12 192.168.122.209 [54063.429185] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:05:12 192.168.122.209 [54063.430911] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:05:13 192.168.122.209 [54063.489279] [tempesta fw] Tempesta FW is ready Apr 26 07:05:13 192.168.122.209 [54064.156187] [tdb] Close table 'client0.tdb' Apr 26 07:05:13 192.168.122.209 [54064.348720] [tdb] Close table 'sessions0.tdb' Apr 26 07:05:17 192.168.122.209 [54067.556157] [tdb] Close table 'cache0.tdb' Apr 26 07:05:17 192.168.122.209 [54067.839547] [tdb] Close table 'filter0.tdb' Apr 26 07:05:17 192.168.122.209 [54067.839949] [tempesta fw] modules are stopped Apr 26 07:05:17 192.168.122.209 [54068.011980] [tempesta fw] exiting... Apr 26 07:05:17 192.168.122.209 [54068.145372] [tdb] Shutdown Tempesta DB Apr 26 07:05:17 192.168.122.209 [54068.356022] End test: cache.test_cache.TestCacheResponseWithTrailersH2.test_same_hdr_and_trailer_head_to_get_multiple_1 Apr 26 07:05:17 192.168.122.209 [54068.369279] Start test: cache.test_cache.TestCacheResponseWithTrailersH2.test_same_hdr_and_trailer_head_to_get_multiple_2 Apr 26 07:05:18 192.168.122.209 [54069.441789] [tdb] Start Tempesta DB Apr 26 07:05:19 192.168.122.209 [54069.579061] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:05:20 192.168.122.209 [54071.151005] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54071.151005] Maybe that's fine, but it's worth checking the [54071.151005] config - if there is no relations between the [54071.151005] names, then host name confusion attack is possible. Apr 26 07:05:20 192.168.122.209 [54071.197519] [tempesta fw] Configuration processing is completed. Apr 26 07:05:20 192.168.122.209 [54071.247428] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:05:21 192.168.122.209 [54071.678550] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:05:21 192.168.122.209 [54071.705592] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:05:21 192.168.122.209 [54071.733384] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:05:21 192.168.122.209 [54071.777321] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:05:21 192.168.122.209 [54071.778365] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:05:21 192.168.122.209 [54071.829311] [tempesta fw] Tempesta FW is ready Apr 26 07:05:22 192.168.122.209 [54072.519069] [tdb] Close table 'client0.tdb' Apr 26 07:05:22 192.168.122.209 [54072.709211] [tdb] Close table 'sessions0.tdb' Apr 26 07:05:25 192.168.122.209 [54075.890408] [tdb] Close table 'cache0.tdb' Apr 26 07:05:25 192.168.122.209 [54076.129830] [tdb] Close table 'filter0.tdb' Apr 26 07:05:25 192.168.122.209 [54076.130263] [tempesta fw] modules are stopped Apr 26 07:05:25 192.168.122.209 [54076.313411] [tempesta fw] exiting... Apr 26 07:05:25 192.168.122.209 [54076.450590] [tdb] Shutdown Tempesta DB Apr 26 07:05:26 192.168.122.209 [54076.643600] End test: cache.test_cache.TestCacheResponseWithTrailersH2.test_same_hdr_and_trailer_head_to_get_multiple_2 Apr 26 07:05:26 192.168.122.209 [54076.661324] Start test: cache.test_cache.TestCacheResponseWithTrailersH2.test_same_trailer_head_to_get Apr 26 07:05:27 192.168.122.209 [54077.544116] [tdb] Start Tempesta DB Apr 26 07:05:27 192.168.122.209 [54077.702443] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:05:28 192.168.122.209 [54079.339112] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54079.339112] Maybe that's fine, but it's worth checking the [54079.339112] config - if there is no relations between the [54079.339112] names, then host name confusion attack is possible. Apr 26 07:05:28 192.168.122.209 [54079.397616] [tempesta fw] Configuration processing is completed. Apr 26 07:05:28 192.168.122.209 [54079.456002] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:05:29 192.168.122.209 [54079.871131] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:05:29 192.168.122.209 [54079.897381] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:05:29 192.168.122.209 [54079.923578] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:05:29 192.168.122.209 [54079.965467] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:05:29 192.168.122.209 [54079.967204] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:05:29 192.168.122.209 [54080.005365] [tempesta fw] Tempesta FW is ready Apr 26 07:05:30 192.168.122.209 [54080.653652] [tdb] Close table 'client0.tdb' Apr 26 07:05:30 192.168.122.209 [54080.869160] [tdb] Close table 'sessions0.tdb' Apr 26 07:05:33 192.168.122.209 [54084.101108] [tdb] Close table 'cache0.tdb' Apr 26 07:05:33 192.168.122.209 [54084.338012] [tdb] Close table 'filter0.tdb' Apr 26 07:05:33 192.168.122.209 [54084.338444] [tempesta fw] modules are stopped Apr 26 07:05:34 192.168.122.209 [54084.543945] [tempesta fw] exiting... Apr 26 07:05:34 192.168.122.209 [54084.665227] [tdb] Shutdown Tempesta DB Apr 26 07:05:34 192.168.122.209 [54084.882297] End test: cache.test_cache.TestCacheResponseWithTrailersH2.test_same_trailer_head_to_get Apr 26 07:05:34 192.168.122.209 [54084.901629] Start test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_GET_GET Apr 26 07:05:35 192.168.122.209 [54086.008962] [tdb] Start Tempesta DB Apr 26 07:05:35 192.168.122.209 [54086.142215] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:05:37 192.168.122.209 [54087.775226] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54087.775226] Maybe that's fine, but it's worth checking the [54087.775226] config - if there is no relations between the [54087.775226] names, then host name confusion attack is possible. Apr 26 07:05:37 192.168.122.209 [54087.821585] [tempesta fw] Configuration processing is completed. Apr 26 07:05:37 192.168.122.209 [54087.871513] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:05:37 192.168.122.209 [54088.297929] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:05:37 192.168.122.209 [54088.324284] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:05:37 192.168.122.209 [54088.352210] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:05:37 192.168.122.209 [54088.401551] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:05:37 192.168.122.209 [54088.403253] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:05:37 192.168.122.209 [54088.453515] [tempesta fw] Tempesta FW is ready Apr 26 07:05:38 192.168.122.209 [54089.067246] [tdb] Close table 'client0.tdb' Apr 26 07:05:38 192.168.122.209 [54089.252870] [tdb] Close table 'sessions0.tdb' Apr 26 07:05:41 192.168.122.209 [54092.461543] [tdb] Close table 'cache0.tdb' Apr 26 07:05:42 192.168.122.209 [54092.678242] [tdb] Close table 'filter0.tdb' Apr 26 07:05:42 192.168.122.209 [54092.678672] [tempesta fw] modules are stopped Apr 26 07:05:42 192.168.122.209 [54092.899748] [tempesta fw] exiting... Apr 26 07:05:42 192.168.122.209 [54093.043666] [tdb] Shutdown Tempesta DB Apr 26 07:05:42 192.168.122.209 [54093.250262] End test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_GET_GET Apr 26 07:05:42 192.168.122.209 [54093.267894] Start test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_GET_HEAD Apr 26 07:05:43 192.168.122.209 [54094.282990] [tdb] Start Tempesta DB Apr 26 07:05:43 192.168.122.209 [54094.430231] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:05:45 192.168.122.209 [54096.071334] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54096.071334] Maybe that's fine, but it's worth checking the [54096.071334] config - if there is no relations between the [54096.071334] names, then host name confusion attack is possible. Apr 26 07:05:45 192.168.122.209 [54096.117931] [tempesta fw] Configuration processing is completed. Apr 26 07:05:45 192.168.122.209 [54096.169273] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:05:46 192.168.122.209 [54096.598962] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:05:46 192.168.122.209 [54096.626532] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:05:46 192.168.122.209 [54096.653879] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:05:46 192.168.122.209 [54096.717699] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:05:46 192.168.122.209 [54096.719472] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:05:46 192.168.122.209 [54096.773658] [tempesta fw] Tempesta FW is ready Apr 26 07:05:46 192.168.122.209 [54097.437944] [tdb] Close table 'client0.tdb' Apr 26 07:05:47 192.168.122.209 [54097.637823] [tdb] Close table 'sessions0.tdb' Apr 26 07:05:50 192.168.122.209 [54100.845780] [tdb] Close table 'cache0.tdb' Apr 26 07:05:50 192.168.122.209 [54101.062935] [tdb] Close table 'filter0.tdb' Apr 26 07:05:50 192.168.122.209 [54101.063379] [tempesta fw] modules are stopped Apr 26 07:05:50 192.168.122.209 [54101.258838] [tempesta fw] exiting... Apr 26 07:05:50 192.168.122.209 [54101.376568] [tdb] Shutdown Tempesta DB Apr 26 07:05:51 192.168.122.209 [54101.599422] End test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_GET_HEAD Apr 26 07:05:51 192.168.122.209 [54101.609772] Start test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_HEAD_GET Apr 26 07:05:52 192.168.122.209 [54102.688812] [tdb] Start Tempesta DB Apr 26 07:05:52 192.168.122.209 [54102.822822] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:05:53 192.168.122.209 [54104.381483] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54104.381483] Maybe that's fine, but it's worth checking the [54104.381483] config - if there is no relations between the [54104.381483] names, then host name confusion attack is possible. Apr 26 07:05:53 192.168.122.209 [54104.426059] [tempesta fw] Configuration processing is completed. Apr 26 07:05:53 192.168.122.209 [54104.479607] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:05:54 192.168.122.209 [54104.896785] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:05:54 192.168.122.209 [54104.922902] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:05:54 192.168.122.209 [54104.949816] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:05:54 192.168.122.209 [54105.009780] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:05:54 192.168.122.209 [54105.011497] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:05:54 192.168.122.209 [54105.061733] [tempesta fw] Tempesta FW is ready Apr 26 07:05:55 192.168.122.209 [54105.698266] [tdb] Close table 'client0.tdb' Apr 26 07:05:55 192.168.122.209 [54105.892494] [tdb] Close table 'sessions0.tdb' Apr 26 07:05:58 192.168.122.209 [54109.092486] [tdb] Close table 'cache0.tdb' Apr 26 07:05:58 192.168.122.209 [54109.349353] [tdb] Close table 'filter0.tdb' Apr 26 07:05:58 192.168.122.209 [54109.349788] [tempesta fw] modules are stopped Apr 26 07:05:59 192.168.122.209 [54109.540780] [tempesta fw] exiting... Apr 26 07:05:59 192.168.122.209 [54109.646543] [tdb] Shutdown Tempesta DB Apr 26 07:05:59 192.168.122.209 [54109.879797] End test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_HEAD_GET Apr 26 07:05:59 192.168.122.209 [54109.912650] Start test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_HEAD_HEAD Apr 26 07:06:00 192.168.122.209 [54110.890718] [tdb] Start Tempesta DB Apr 26 07:06:00 192.168.122.209 [54111.045960] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:06:02 192.168.122.209 [54112.591504] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54112.591504] Maybe that's fine, but it's worth checking the [54112.591504] config - if there is no relations between the [54112.591504] names, then host name confusion attack is possible. Apr 26 07:06:02 192.168.122.209 [54112.638114] [tempesta fw] Configuration processing is completed. Apr 26 07:06:02 192.168.122.209 [54112.688417] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:06:02 192.168.122.209 [54113.112819] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:06:02 192.168.122.209 [54113.138603] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:06:02 192.168.122.209 [54113.164407] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:06:02 192.168.122.209 [54113.217881] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:06:02 192.168.122.209 [54113.219486] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:06:02 192.168.122.209 [54113.257817] [tempesta fw] Tempesta FW is ready Apr 26 07:06:03 192.168.122.209 [54113.874351] [tdb] Close table 'client0.tdb' Apr 26 07:06:03 192.168.122.209 [54114.071061] [tdb] Close table 'sessions0.tdb' Apr 26 07:06:06 192.168.122.209 [54117.295727] [tdb] Close table 'cache0.tdb' Apr 26 07:06:07 192.168.122.209 [54117.518132] [tdb] Close table 'filter0.tdb' Apr 26 07:06:07 192.168.122.209 [54117.518571] [tempesta fw] modules are stopped Apr 26 07:06:07 192.168.122.209 [54117.708038] [tempesta fw] exiting... Apr 26 07:06:07 192.168.122.209 [54117.829229] [tdb] Shutdown Tempesta DB Apr 26 07:06:07 192.168.122.209 [54118.030600] End test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_HEAD_HEAD Apr 26 07:06:07 192.168.122.209 [54118.046983] Start test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_empty_body_head_to_get Apr 26 07:06:08 192.168.122.209 [54119.104785] [tdb] Start Tempesta DB Apr 26 07:06:08 192.168.122.209 [54119.240523] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:06:10 192.168.122.209 [54120.919696] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54120.919696] Maybe that's fine, but it's worth checking the [54120.919696] config - if there is no relations between the [54120.919696] names, then host name confusion attack is possible. Apr 26 07:06:10 192.168.122.209 [54120.966345] [tempesta fw] Configuration processing is completed. Apr 26 07:06:10 192.168.122.209 [54121.016568] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:06:10 192.168.122.209 [54121.441032] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:06:10 192.168.122.209 [54121.476301] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:06:11 192.168.122.209 [54121.503652] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:06:11 192.168.122.209 [54121.545981] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:06:11 192.168.122.209 [54121.547372] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:06:11 192.168.122.209 [54121.597923] [tempesta fw] Tempesta FW is ready Apr 26 07:06:11 192.168.122.209 [54122.234836] [tdb] Close table 'client0.tdb' Apr 26 07:06:11 192.168.122.209 [54122.425977] [tdb] Close table 'sessions0.tdb' Apr 26 07:06:15 192.168.122.209 [54125.641548] [tdb] Close table 'cache0.tdb' Apr 26 07:06:15 192.168.122.209 [54125.900332] [tdb] Close table 'filter0.tdb' Apr 26 07:06:15 192.168.122.209 [54125.900772] [tempesta fw] modules are stopped Apr 26 07:06:15 192.168.122.209 [54126.080645] [tempesta fw] exiting... Apr 26 07:06:15 192.168.122.209 [54126.239368] [tdb] Shutdown Tempesta DB Apr 26 07:06:15 192.168.122.209 [54126.466377] End test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_empty_body_head_to_get Apr 26 07:06:16 192.168.122.209 [54126.491685] Start test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_hbh_headers_hbp_GET Apr 26 07:06:17 192.168.122.209 [54127.586609] [tdb] Start Tempesta DB Apr 26 07:06:17 192.168.122.209 [54127.728407] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:06:18 192.168.122.209 [54129.271750] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54129.271750] Maybe that's fine, but it's worth checking the [54129.271750] config - if there is no relations between the [54129.271750] names, then host name confusion attack is possible. Apr 26 07:06:18 192.168.122.209 [54129.314361] [tempesta fw] Configuration processing is completed. Apr 26 07:06:18 192.168.122.209 [54129.364924] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:06:19 192.168.122.209 [54129.798953] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:06:19 192.168.122.209 [54129.826962] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:06:19 192.168.122.209 [54129.854040] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:06:19 192.168.122.209 [54129.954159] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:06:19 192.168.122.209 [54129.955968] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:06:19 192.168.122.209 [54130.010044] [tempesta fw] Tempesta FW is ready Apr 26 07:06:19 192.168.122.209 [54130.207990] [tempesta fw] Warning: Parser error: state=Resp_HdrConnectionV input(-0)=0xd(' ') data_len=1 off=0 Apr 26 07:06:19 192.168.122.209 [54130.209148] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 07:06:20 192.168.122.209 [54130.647886] [tdb] Close table 'client0.tdb' Apr 26 07:06:20 192.168.122.209 [54130.835012] [tdb] Close table 'sessions0.tdb' Apr 26 07:06:23 192.168.122.209 [54134.079550] [tdb] Close table 'cache0.tdb' Apr 26 07:06:23 192.168.122.209 [54134.321608] [tdb] Close table 'filter0.tdb' Apr 26 07:06:23 192.168.122.209 [54134.322065] [tempesta fw] modules are stopped Apr 26 07:06:24 192.168.122.209 [54134.514907] [tempesta fw] exiting... Apr 26 07:06:24 192.168.122.209 [54134.634046] [tdb] Shutdown Tempesta DB Apr 26 07:06:24 192.168.122.209 [54134.865037] End test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_hbh_headers_hbp_GET Apr 26 07:06:24 192.168.122.209 [54134.884346] Start test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_hbh_headers_hbp_HEAD Apr 26 07:06:25 192.168.122.209 [54136.063202] [tdb] Start Tempesta DB Apr 26 07:06:25 192.168.122.209 [54136.206786] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:06:27 192.168.122.209 [54137.803810] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54137.803810] Maybe that's fine, but it's worth checking the [54137.803810] config - if there is no relations between the [54137.803810] names, then host name confusion attack is possible. Apr 26 07:06:27 192.168.122.209 [54137.850481] [tempesta fw] Configuration processing is completed. Apr 26 07:06:27 192.168.122.209 [54137.902516] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:06:27 192.168.122.209 [54138.330790] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:06:27 192.168.122.209 [54138.357211] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:06:27 192.168.122.209 [54138.383245] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:06:27 192.168.122.209 [54138.430160] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:06:27 192.168.122.209 [54138.431551] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:06:27 192.168.122.209 [54138.478691] [tempesta fw] Tempesta FW is ready Apr 26 07:06:28 192.168.122.209 [54138.665888] [tempesta fw] Warning: Parser error: state=Resp_HdrConnectionV input(-0)=0xd(' ') data_len=1 off=0 Apr 26 07:06:28 192.168.122.209 [54138.667027] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 07:06:28 192.168.122.209 [54139.052396] [tdb] Close table 'client0.tdb' Apr 26 07:06:28 192.168.122.209 [54139.258961] [tdb] Close table 'sessions0.tdb' Apr 26 07:06:32 192.168.122.209 [54142.507609] [tdb] Close table 'cache0.tdb' Apr 26 07:06:32 192.168.122.209 [54142.749594] [tdb] Close table 'filter0.tdb' Apr 26 07:06:32 192.168.122.209 [54142.750101] [tempesta fw] modules are stopped Apr 26 07:06:32 192.168.122.209 [54142.937426] [tempesta fw] exiting... Apr 26 07:06:32 192.168.122.209 [54143.045734] [tdb] Shutdown Tempesta DB Apr 26 07:06:32 192.168.122.209 [54143.274259] End test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_hbh_headers_hbp_HEAD Apr 26 07:06:32 192.168.122.209 [54143.288875] Start test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_hbh_headers_mix_GET Apr 26 07:06:33 192.168.122.209 [54144.300628] [tdb] Start Tempesta DB Apr 26 07:06:33 192.168.122.209 [54144.450459] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:06:35 192.168.122.209 [54146.048039] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54146.048039] Maybe that's fine, but it's worth checking the [54146.048039] config - if there is no relations between the [54146.048039] names, then host name confusion attack is possible. Apr 26 07:06:35 192.168.122.209 [54146.098180] [tempesta fw] Configuration processing is completed. Apr 26 07:06:35 192.168.122.209 [54146.155758] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:06:36 192.168.122.209 [54146.613382] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:06:36 192.168.122.209 [54146.642316] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:06:36 192.168.122.209 [54146.671859] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:06:36 192.168.122.209 [54146.718292] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:06:36 192.168.122.209 [54146.720028] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:06:36 192.168.122.209 [54146.766274] [tempesta fw] Tempesta FW is ready Apr 26 07:06:36 192.168.122.209 [54146.963734] [tempesta fw] Warning: Parser error: state=Resp_HdrConnectionV input(-0)=0xd(' ') data_len=1 off=0 Apr 26 07:06:36 192.168.122.209 [54146.964872] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 07:06:36 192.168.122.209 [54147.405365] [tdb] Close table 'client0.tdb' Apr 26 07:06:37 192.168.122.209 [54147.591747] [tdb] Close table 'sessions0.tdb' Apr 26 07:06:40 192.168.122.209 [54150.903505] [tdb] Close table 'cache0.tdb' Apr 26 07:06:40 192.168.122.209 [54151.137958] [tdb] Close table 'filter0.tdb' Apr 26 07:06:40 192.168.122.209 [54151.138423] [tempesta fw] modules are stopped Apr 26 07:06:40 192.168.122.209 [54151.403204] [tempesta fw] exiting... Apr 26 07:06:41 192.168.122.209 [54151.511449] [tdb] Shutdown Tempesta DB Apr 26 07:06:41 192.168.122.209 [54151.714099] End test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_hbh_headers_mix_GET Apr 26 07:06:41 192.168.122.209 [54151.739644] Start test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_hbh_headers_mix_HEAD Apr 26 07:06:42 192.168.122.209 [54152.831990] [tdb] Start Tempesta DB Apr 26 07:06:42 192.168.122.209 [54152.972620] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:06:44 192.168.122.209 [54154.620113] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54154.620113] Maybe that's fine, but it's worth checking the [54154.620113] config - if there is no relations between the [54154.620113] names, then host name confusion attack is possible. Apr 26 07:06:44 192.168.122.209 [54154.662676] [tempesta fw] Configuration processing is completed. Apr 26 07:06:44 192.168.122.209 [54154.713800] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:06:44 192.168.122.209 [54155.145741] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:06:44 192.168.122.209 [54155.174188] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:06:44 192.168.122.209 [54155.201797] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:06:44 192.168.122.209 [54155.262440] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:06:44 192.168.122.209 [54155.264264] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:06:44 192.168.122.209 [54155.306368] [tempesta fw] Tempesta FW is ready Apr 26 07:06:45 192.168.122.209 [54155.497820] [tempesta fw] Warning: Parser error: state=Resp_HdrConnectionV input(-0)=0xd(' ') data_len=1 off=0 Apr 26 07:06:45 192.168.122.209 [54155.498997] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 07:06:45 192.168.122.209 [54155.883818] [tdb] Close table 'client0.tdb' Apr 26 07:06:45 192.168.122.209 [54156.089428] [tdb] Close table 'sessions0.tdb' Apr 26 07:06:48 192.168.122.209 [54159.360770] [tdb] Close table 'cache0.tdb' Apr 26 07:06:49 192.168.122.209 [54159.588168] [tdb] Close table 'filter0.tdb' Apr 26 07:06:49 192.168.122.209 [54159.588615] [tempesta fw] modules are stopped Apr 26 07:06:49 192.168.122.209 [54159.775731] [tempesta fw] exiting... Apr 26 07:06:49 192.168.122.209 [54159.887363] [tdb] Shutdown Tempesta DB Apr 26 07:06:49 192.168.122.209 [54160.110564] End test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_hbh_headers_mix_HEAD Apr 26 07:06:49 192.168.122.209 [54160.133508] Start test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_same_hdr_and_trailer_head_to_get Apr 26 07:06:50 192.168.122.209 [54161.235029] [tdb] Start Tempesta DB Apr 26 07:06:50 192.168.122.209 [54161.388048] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:06:52 192.168.122.209 [54162.988223] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54162.988223] Maybe that's fine, but it's worth checking the [54162.988223] config - if there is no relations between the [54162.988223] names, then host name confusion attack is possible. Apr 26 07:06:52 192.168.122.209 [54163.046483] [tempesta fw] Configuration processing is completed. Apr 26 07:06:52 192.168.122.209 [54163.101169] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:06:53 192.168.122.209 [54163.612563] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:06:53 192.168.122.209 [54163.646777] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:06:53 192.168.122.209 [54163.679564] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:06:53 192.168.122.209 [54163.738548] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:06:53 192.168.122.209 [54163.740281] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:06:53 192.168.122.209 [54163.794461] [tempesta fw] Tempesta FW is ready Apr 26 07:06:53 192.168.122.209 [54164.439400] [tdb] Close table 'client0.tdb' Apr 26 07:06:54 192.168.122.209 [54164.629907] [tdb] Close table 'sessions0.tdb' Apr 26 07:06:57 192.168.122.209 [54167.891210] [tdb] Close table 'cache0.tdb' Apr 26 07:06:57 192.168.122.209 [54168.138496] [tdb] Close table 'filter0.tdb' Apr 26 07:06:57 192.168.122.209 [54168.138948] [tempesta fw] modules are stopped Apr 26 07:06:57 192.168.122.209 [54168.374312] [tempesta fw] exiting... Apr 26 07:06:57 192.168.122.209 [54168.482176] [tdb] Shutdown Tempesta DB Apr 26 07:06:58 192.168.122.209 [54168.723609] End test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_same_hdr_and_trailer_head_to_get Apr 26 07:06:58 192.168.122.209 [54168.749261] Start test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_same_hdr_and_trailer_head_to_get_multiple_1 Apr 26 07:06:59 192.168.122.209 [54169.860246] [tdb] Start Tempesta DB Apr 26 07:06:59 192.168.122.209 [54170.001117] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:07:01 192.168.122.209 [54171.660404] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54171.660404] Maybe that's fine, but it's worth checking the [54171.660404] config - if there is no relations between the [54171.660404] names, then host name confusion attack is possible. Apr 26 07:07:01 192.168.122.209 [54171.702751] [tempesta fw] Configuration processing is completed. Apr 26 07:07:01 192.168.122.209 [54171.753782] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:07:01 192.168.122.209 [54172.183699] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:07:01 192.168.122.209 [54172.211312] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:07:01 192.168.122.209 [54172.240173] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:07:01 192.168.122.209 [54172.306629] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:07:01 192.168.122.209 [54172.308371] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:07:01 192.168.122.209 [54172.350485] [tempesta fw] Tempesta FW is ready Apr 26 07:07:02 192.168.122.209 [54173.037666] [tdb] Close table 'client0.tdb' Apr 26 07:07:02 192.168.122.209 [54173.229903] [tdb] Close table 'sessions0.tdb' Apr 26 07:07:05 192.168.122.209 [54176.460486] [tdb] Close table 'cache0.tdb' Apr 26 07:07:06 192.168.122.209 [54176.703840] [tdb] Close table 'filter0.tdb' Apr 26 07:07:06 192.168.122.209 [54176.704272] [tempesta fw] modules are stopped Apr 26 07:07:06 192.168.122.209 [54176.940079] [tempesta fw] exiting... Apr 26 07:07:06 192.168.122.209 [54177.065627] [tdb] Shutdown Tempesta DB Apr 26 07:07:06 192.168.122.209 [54177.286955] End test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_same_hdr_and_trailer_head_to_get_multiple_1 Apr 26 07:07:06 192.168.122.209 [54177.309350] Start test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_same_hdr_and_trailer_head_to_get_multiple_2 Apr 26 07:07:07 192.168.122.209 [54178.414230] [tdb] Start Tempesta DB Apr 26 07:07:08 192.168.122.209 [54178.559520] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:07:09 192.168.122.209 [54180.116422] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54180.116422] Maybe that's fine, but it's worth checking the [54180.116422] config - if there is no relations between the [54180.116422] names, then host name confusion attack is possible. Apr 26 07:07:09 192.168.122.209 [54180.190688] [tempesta fw] Configuration processing is completed. Apr 26 07:07:09 192.168.122.209 [54180.254367] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:07:10 192.168.122.209 [54180.759678] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:07:10 192.168.122.209 [54180.794480] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:07:10 192.168.122.209 [54180.829812] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:07:10 192.168.122.209 [54180.874742] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:07:10 192.168.122.209 [54180.876478] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:07:10 192.168.122.209 [54180.922671] [tempesta fw] Tempesta FW is ready Apr 26 07:07:11 192.168.122.209 [54181.531925] [tdb] Close table 'client0.tdb' Apr 26 07:07:11 192.168.122.209 [54181.720769] [tdb] Close table 'sessions0.tdb' Apr 26 07:07:14 192.168.122.209 [54184.951778] [tdb] Close table 'cache0.tdb' Apr 26 07:07:14 192.168.122.209 [54185.181530] [tdb] Close table 'filter0.tdb' Apr 26 07:07:14 192.168.122.209 [54185.181980] [tempesta fw] modules are stopped Apr 26 07:07:14 192.168.122.209 [54185.366626] [tempesta fw] exiting... Apr 26 07:07:14 192.168.122.209 [54185.482725] [tdb] Shutdown Tempesta DB Apr 26 07:07:15 192.168.122.209 [54185.701498] End test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_same_hdr_and_trailer_head_to_get_multiple_2 Apr 26 07:07:15 192.168.122.209 [54185.720524] Start test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_same_trailer_head_to_get Apr 26 07:07:16 192.168.122.209 [54186.778228] [tdb] Start Tempesta DB Apr 26 07:07:16 192.168.122.209 [54186.933092] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:07:18 192.168.122.209 [54188.504516] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54188.504516] Maybe that's fine, but it's worth checking the [54188.504516] config - if there is no relations between the [54188.504516] names, then host name confusion attack is possible. Apr 26 07:07:18 192.168.122.209 [54188.558797] [tempesta fw] Configuration processing is completed. Apr 26 07:07:18 192.168.122.209 [54188.613783] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:07:18 192.168.122.209 [54189.033352] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:07:18 192.168.122.209 [54189.061468] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:07:18 192.168.122.209 [54189.090542] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:07:18 192.168.122.209 [54189.134878] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:07:18 192.168.122.209 [54189.136635] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:07:18 192.168.122.209 [54189.174785] [tempesta fw] Tempesta FW is ready Apr 26 07:07:19 192.168.122.209 [54189.821573] [tdb] Close table 'client0.tdb' Apr 26 07:07:19 192.168.122.209 [54190.016374] [tdb] Close table 'sessions0.tdb' Apr 26 07:07:22 192.168.122.209 [54193.250571] [tdb] Close table 'cache0.tdb' Apr 26 07:07:22 192.168.122.209 [54193.482284] [tdb] Close table 'filter0.tdb' Apr 26 07:07:22 192.168.122.209 [54193.482739] [tempesta fw] modules are stopped Apr 26 07:07:23 192.168.122.209 [54193.711616] [tempesta fw] exiting... Apr 26 07:07:23 192.168.122.209 [54193.853169] [tdb] Shutdown Tempesta DB Apr 26 07:07:23 192.168.122.209 [54194.086579] End test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_same_trailer_head_to_get Apr 26 07:07:23 192.168.122.209 [54194.098688] Start test: cache.test_cache.TestCacheUseStaleCfg.test_cache_use_stale_config_dupl Apr 26 07:07:24 192.168.122.209 [54195.158816] [tdb] Start Tempesta DB Apr 26 07:07:24 192.168.122.209 [54195.288129] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:07:26 192.168.122.209 [54196.776264] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54196.776264] Maybe that's fine, but it's worth checking the [54196.776264] config - if there is no relations between the [54196.776264] names, then host name confusion attack is possible. Apr 26 07:07:26 192.168.122.209 [54196.854990] [tempesta fw] ERROR: duplicate entry: 'cache_use_stale', only one such entry is allowed. Apr 26 07:07:26 192.168.122.209 [54196.857611] [tempesta fw] ERROR: configuration parsing error: [54196.857611] 15: cache_use_stale 5*;cache_use_stale 4*; [54196.857611] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 07:07:26 192.168.122.209 [54196.862083] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 07:07:26 192.168.122.209 [54197.048644] [tempesta fw] exiting... Apr 26 07:07:26 192.168.122.209 [54197.164148] [tdb] Shutdown Tempesta DB Apr 26 07:07:27 192.168.122.209 [54197.661857] End test: cache.test_cache.TestCacheUseStaleCfg.test_cache_use_stale_config_dupl Apr 26 07:07:27 192.168.122.209 [54197.684593] Start test: cache.test_cache.TestCacheUseStaleCfg.test_cache_use_stale_config_wrong_code Apr 26 07:07:28 192.168.122.209 [54198.771199] [tdb] Start Tempesta DB Apr 26 07:07:28 192.168.122.209 [54198.904221] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:07:28 192.168.122.209 [54199.380723] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54199.380723] Maybe that's fine, but it's worth checking the [54199.380723] config - if there is no relations between the [54199.380723] names, then host name confusion attack is possible. Apr 26 07:07:28 192.168.122.209 [54199.439115] [tempesta fw] ERROR: Please specify status code above than 399. Apr 26 07:07:28 192.168.122.209 [54199.439127] [tempesta fw] ERROR: configuration parsing error: [54199.439127] 15: cache_use_stale 200; [54199.439127] ^^^^^^^^^^^^^^^^^^^^ Apr 26 07:07:28 192.168.122.209 [54199.444710] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 07:07:29 192.168.122.209 [54199.598660] [tempesta fw] exiting... Apr 26 07:07:29 192.168.122.209 [54199.718038] [tdb] Shutdown Tempesta DB Apr 26 07:07:29 192.168.122.209 [54200.210118] End test: cache.test_cache.TestCacheUseStaleCfg.test_cache_use_stale_config_wrong_code Apr 26 07:07:29 192.168.122.209 [54200.233498] Start test: cache.test_cache.TestCacheUseStaleCfg.test_cache_use_stale_config_wrong_mask Apr 26 07:07:30 192.168.122.209 [54201.295467] [tdb] Start Tempesta DB Apr 26 07:07:30 192.168.122.209 [54201.420896] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:07:31 192.168.122.209 [54201.948630] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54201.948630] Maybe that's fine, but it's worth checking the [54201.948630] config - if there is no relations between the [54201.948630] names, then host name confusion attack is possible. Apr 26 07:07:31 192.168.122.209 [54202.007128] [tempesta fw] ERROR: cache_use_stale Unsupported argument "3*" Apr 26 07:07:31 192.168.122.209 [54202.007139] [tempesta fw] ERROR: configuration parsing error: [54202.007139] 15: cache_use_stale 3*; [54202.007139] ^^^^^^^^^^^^^^^^^^^ Apr 26 07:07:31 192.168.122.209 [54202.012679] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 07:07:31 192.168.122.209 [54202.201366] [tempesta fw] exiting... Apr 26 07:07:31 192.168.122.209 [54202.317847] [tdb] Shutdown Tempesta DB Apr 26 07:07:32 192.168.122.209 [54202.844359] End test: cache.test_cache.TestCacheUseStaleCfg.test_cache_use_stale_config_wrong_mask Apr 26 07:07:32 192.168.122.209 [54202.865367] Start test: cache.test_cache.TestCacheVhost.test_h2 Apr 26 07:07:33 192.168.122.209 [54203.916137] [tdb] Start Tempesta DB Apr 26 07:07:33 192.168.122.209 [54204.057773] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:07:34 192.168.122.209 [54204.885041] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [54204.885041] Maybe that's fine, but it's worth checking the [54204.885041] config - if there is no relations between the [54204.885041] names, then host name confusion attack is possible. Apr 26 07:07:34 192.168.122.209 [54204.999099] [tempesta fw] Configuration processing is completed. Apr 26 07:07:34 192.168.122.209 [54205.049824] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:07:34 192.168.122.209 [54205.470933] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:07:35 192.168.122.209 [54205.497081] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:07:35 192.168.122.209 [54205.523999] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:07:35 192.168.122.209 [54205.627084] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:07:35 192.168.122.209 [54205.674988] [tempesta fw] Tempesta FW is ready Apr 26 07:07:36 192.168.122.209 [54206.689506] [tdb] Close table 'client0.tdb' Apr 26 07:07:36 192.168.122.209 [54206.872755] [tdb] Close table 'sessions0.tdb' Apr 26 07:07:39 192.168.122.209 [54210.064565] [tdb] Close table 'cache0.tdb' Apr 26 07:07:39 192.168.122.209 [54210.297022] [tdb] Close table 'filter0.tdb' Apr 26 07:07:39 192.168.122.209 [54210.297468] [tempesta fw] modules are stopped Apr 26 07:07:40 192.168.122.209 [54210.531135] [tempesta fw] exiting... Apr 26 07:07:40 192.168.122.209 [54210.660106] [tdb] Shutdown Tempesta DB Apr 26 07:07:40 192.168.122.209 [54210.867227] End test: cache.test_cache.TestCacheVhost.test_h2 Apr 26 07:07:40 192.168.122.209 [54210.880325] Start test: cache.test_cache.TestCacheVhost.test_https Apr 26 07:07:41 192.168.122.209 [54211.904732] [tdb] Start Tempesta DB Apr 26 07:07:41 192.168.122.209 [54212.047752] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:07:43 192.168.122.209 [54213.809168] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [54213.809168] Maybe that's fine, but it's worth checking the [54213.809168] config - if there is no relations between the [54213.809168] names, then host name confusion attack is possible. Apr 26 07:07:43 192.168.122.209 [54213.907235] [tempesta fw] Configuration processing is completed. Apr 26 07:07:43 192.168.122.209 [54213.958257] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:07:43 192.168.122.209 [54214.388698] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:07:43 192.168.122.209 [54214.415825] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:07:43 192.168.122.209 [54214.442663] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:07:44 192.168.122.209 [54214.523149] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:07:44 192.168.122.209 [54214.563113] [tempesta fw] Tempesta FW is ready Apr 26 07:07:45 192.168.122.209 [54215.558841] [tdb] Close table 'client0.tdb' Apr 26 07:07:45 192.168.122.209 [54215.754369] [tdb] Close table 'sessions0.tdb' Apr 26 07:07:48 192.168.122.209 [54218.932411] [tdb] Close table 'cache0.tdb' Apr 26 07:07:48 192.168.122.209 [54219.168890] [tdb] Close table 'filter0.tdb' Apr 26 07:07:48 192.168.122.209 [54219.169318] [tempesta fw] modules are stopped Apr 26 07:07:48 192.168.122.209 [54219.418844] [tempesta fw] exiting... Apr 26 07:07:49 192.168.122.209 [54219.546865] [tdb] Shutdown Tempesta DB Apr 26 07:07:49 192.168.122.209 [54219.743911] End test: cache.test_cache.TestCacheVhost.test_https Apr 26 07:07:49 192.168.122.209 [54219.759092] Start test: cache.test_cache.TestChunkedResponse.test_cached_data_equal_to_original Apr 26 07:07:50 192.168.122.209 [54220.815984] [tdb] Start Tempesta DB Apr 26 07:07:50 192.168.122.209 [54220.952657] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:07:51 192.168.122.209 [54222.287898] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54222.287898] Maybe that's fine, but it's worth checking the [54222.287898] config - if there is no relations between the [54222.287898] names, then host name confusion attack is possible. Apr 26 07:07:51 192.168.122.209 [54222.415261] [tempesta fw] Configuration processing is completed. Apr 26 07:07:51 192.168.122.209 [54222.469248] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:07:52 192.168.122.209 [54222.891365] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:07:52 192.168.122.209 [54222.918155] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:07:52 192.168.122.209 [54222.945329] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:07:52 192.168.122.209 [54222.987254] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:07:52 192.168.122.209 [54222.989037] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:07:52 192.168.122.209 [54223.047205] [tempesta fw] Tempesta FW is ready Apr 26 07:07:53 192.168.122.209 [54223.740699] [tdb] Close table 'client0.tdb' Apr 26 07:07:53 192.168.122.209 [54223.951538] [tdb] Close table 'sessions0.tdb' Apr 26 07:07:56 192.168.122.209 [54227.154382] [tdb] Close table 'cache0.tdb' Apr 26 07:07:56 192.168.122.209 [54227.395442] [tdb] Close table 'filter0.tdb' Apr 26 07:07:56 192.168.122.209 [54227.395967] [tempesta fw] modules are stopped Apr 26 07:07:57 192.168.122.209 [54227.587388] [tempesta fw] exiting... Apr 26 07:07:57 192.168.122.209 [54227.737357] [tdb] Shutdown Tempesta DB Apr 26 07:07:57 192.168.122.209 [54227.955534] End test: cache.test_cache.TestChunkedResponse.test_cached_data_equal_to_original Apr 26 07:07:57 192.168.122.209 [54227.968530] Start test: cache.test_cache.TestChunkedResponse.test_h2_cached_data_equal_to_original Apr 26 07:07:58 192.168.122.209 [54229.003460] [tdb] Start Tempesta DB Apr 26 07:07:58 192.168.122.209 [54229.135938] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:08:00 192.168.122.209 [54230.528595] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54230.528595] Maybe that's fine, but it's worth checking the [54230.528595] config - if there is no relations between the [54230.528595] names, then host name confusion attack is possible. Apr 26 07:08:00 192.168.122.209 [54230.659396] [tempesta fw] Configuration processing is completed. Apr 26 07:08:00 192.168.122.209 [54230.722183] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:08:00 192.168.122.209 [54231.149781] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:08:00 192.168.122.209 [54231.175755] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:08:00 192.168.122.209 [54231.201939] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:08:00 192.168.122.209 [54231.247295] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:08:00 192.168.122.209 [54231.248351] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:08:00 192.168.122.209 [54231.295305] [tempesta fw] Tempesta FW is ready Apr 26 07:08:01 192.168.122.209 [54232.047634] [tdb] Close table 'client0.tdb' Apr 26 07:08:01 192.168.122.209 [54232.251515] [tdb] Close table 'sessions0.tdb' Apr 26 07:08:05 192.168.122.209 [54235.492709] [tdb] Close table 'cache0.tdb' Apr 26 07:08:05 192.168.122.209 [54235.751727] [tdb] Close table 'filter0.tdb' Apr 26 07:08:05 192.168.122.209 [54235.752163] [tempesta fw] modules are stopped Apr 26 07:08:05 192.168.122.209 [54235.961510] [tempesta fw] exiting... Apr 26 07:08:05 192.168.122.209 [54236.083904] [tdb] Shutdown Tempesta DB Apr 26 07:08:05 192.168.122.209 [54236.323315] End test: cache.test_cache.TestChunkedResponse.test_h2_cached_data_equal_to_original Apr 26 07:08:05 192.168.122.209 [54236.343523] Start test: cache.test_cache.TestH2CacheDisable.test_cache_disable Apr 26 07:08:06 192.168.122.209 [54237.318862] [tdb] Start Tempesta DB Apr 26 07:08:06 192.168.122.209 [54237.462295] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:08:08 192.168.122.209 [54239.048734] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54239.048734] Maybe that's fine, but it's worth checking the [54239.048734] config - if there is no relations between the [54239.048734] names, then host name confusion attack is possible. Apr 26 07:08:08 192.168.122.209 [54239.243476] [tempesta fw] Configuration processing is completed. Apr 26 07:08:08 192.168.122.209 [54239.295206] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:08:09 192.168.122.209 [54239.721251] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:08:09 192.168.122.209 [54239.757491] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:08:09 192.168.122.209 [54239.785513] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:08:09 192.168.122.209 [54239.835481] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:08:09 192.168.122.209 [54239.837233] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:08:09 192.168.122.209 [54239.875466] [tempesta fw] Tempesta FW is ready Apr 26 07:08:10 192.168.122.209 [54240.523112] [tdb] Close table 'client0.tdb' Apr 26 07:08:10 192.168.122.209 [54240.715935] [tdb] Close table 'sessions0.tdb' Apr 26 07:08:13 192.168.122.209 [54243.880730] [tdb] Close table 'cache0.tdb' Apr 26 07:08:13 192.168.122.209 [54244.139679] [tdb] Close table 'filter0.tdb' Apr 26 07:08:13 192.168.122.209 [54244.140126] [tempesta fw] modules are stopped Apr 26 07:08:13 192.168.122.209 [54244.354389] [tempesta fw] exiting... Apr 26 07:08:13 192.168.122.209 [54244.485665] [tdb] Shutdown Tempesta DB Apr 26 07:08:14 192.168.122.209 [54244.707298] End test: cache.test_cache.TestH2CacheDisable.test_cache_disable Apr 26 07:08:14 192.168.122.209 [54244.725580] Start test: cache.test_cache.TestH2CacheDisable.test_cache_disable_0 Apr 26 07:08:15 192.168.122.209 [54245.785412] [tdb] Start Tempesta DB Apr 26 07:08:15 192.168.122.209 [54245.940681] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:08:17 192.168.122.209 [54247.560830] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54247.560830] Maybe that's fine, but it's worth checking the [54247.560830] config - if there is no relations between the [54247.560830] names, then host name confusion attack is possible. Apr 26 07:08:17 192.168.122.209 [54247.771602] [tempesta fw] Configuration processing is completed. Apr 26 07:08:17 192.168.122.209 [54247.822779] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:08:17 192.168.122.209 [54248.266739] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:08:17 192.168.122.209 [54248.296098] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:08:17 192.168.122.209 [54248.324765] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:08:17 192.168.122.209 [54248.363571] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:08:17 192.168.122.209 [54248.365376] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:08:17 192.168.122.209 [54248.407521] [tempesta fw] Tempesta FW is ready Apr 26 07:08:18 192.168.122.209 [54249.044730] [tdb] Close table 'client0.tdb' Apr 26 07:08:18 192.168.122.209 [54249.243009] [tdb] Close table 'sessions0.tdb' Apr 26 07:08:21 192.168.122.209 [54252.477831] [tdb] Close table 'cache0.tdb' Apr 26 07:08:22 192.168.122.209 [54252.720877] [tdb] Close table 'filter0.tdb' Apr 26 07:08:22 192.168.122.209 [54252.721311] [tempesta fw] modules are stopped Apr 26 07:08:22 192.168.122.209 [54252.972874] [tempesta fw] exiting... Apr 26 07:08:22 192.168.122.209 [54253.098718] [tdb] Shutdown Tempesta DB Apr 26 07:08:22 192.168.122.209 [54253.318371] End test: cache.test_cache.TestH2CacheDisable.test_cache_disable_0 Apr 26 07:08:22 192.168.122.209 [54253.334717] Start test: cache.test_cache.TestH2CacheDisable.test_cache_disable_1 Apr 26 07:08:23 192.168.122.209 [54254.394918] [tdb] Start Tempesta DB Apr 26 07:08:24 192.168.122.209 [54254.539665] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:08:25 192.168.122.209 [54256.161061] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54256.161061] Maybe that's fine, but it's worth checking the [54256.161061] config - if there is no relations between the [54256.161061] names, then host name confusion attack is possible. Apr 26 07:08:25 192.168.122.209 [54256.339716] [tempesta fw] Configuration processing is completed. Apr 26 07:08:25 192.168.122.209 [54256.395942] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:08:26 192.168.122.209 [54256.886496] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:08:26 192.168.122.209 [54256.926818] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:08:26 192.168.122.209 [54256.961258] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:08:26 192.168.122.209 [54257.003639] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:08:26 192.168.122.209 [54257.004680] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:08:26 192.168.122.209 [54257.051640] [tempesta fw] Tempesta FW is ready Apr 26 07:08:27 192.168.122.209 [54257.749333] [tdb] Close table 'client0.tdb' Apr 26 07:08:27 192.168.122.209 [54257.951724] [tdb] Close table 'sessions0.tdb' Apr 26 07:08:30 192.168.122.209 [54261.174434] [tdb] Close table 'cache0.tdb' Apr 26 07:08:30 192.168.122.209 [54261.430637] [tdb] Close table 'filter0.tdb' Apr 26 07:08:30 192.168.122.209 [54261.431055] [tempesta fw] modules are stopped Apr 26 07:08:31 192.168.122.209 [54261.657141] [tempesta fw] exiting... Apr 26 07:08:31 192.168.122.209 [54261.806257] [tdb] Shutdown Tempesta DB Apr 26 07:08:31 192.168.122.209 [54262.045525] End test: cache.test_cache.TestH2CacheDisable.test_cache_disable_1 Apr 26 07:08:31 192.168.122.209 [54262.058955] Start test: cache.test_cache.TestH2CacheDisable.test_cache_disable_with_override_http_chain Apr 26 07:08:32 192.168.122.209 [54263.131730] [tdb] Start Tempesta DB Apr 26 07:08:32 192.168.122.209 [54263.273157] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:08:34 192.168.122.209 [54264.877097] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54264.877097] Maybe that's fine, but it's worth checking the [54264.877097] config - if there is no relations between the [54264.877097] names, then host name confusion attack is possible. Apr 26 07:08:34 192.168.122.209 [54265.048073] [tempesta fw] Configuration processing is completed. Apr 26 07:08:34 192.168.122.209 [54265.105974] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:08:35 192.168.122.209 [54265.648430] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:08:35 192.168.122.209 [54265.681644] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:08:35 192.168.122.209 [54265.715058] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:08:35 192.168.122.209 [54265.791805] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:08:35 192.168.122.209 [54265.793562] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:08:35 192.168.122.209 [54265.851745] [tempesta fw] Tempesta FW is ready Apr 26 07:08:35 192.168.122.209 [54266.487742] [tdb] Close table 'client0.tdb' Apr 26 07:08:36 192.168.122.209 [54266.683573] [tdb] Close table 'sessions0.tdb' Apr 26 07:08:39 192.168.122.209 [54269.866506] [tdb] Close table 'cache0.tdb' Apr 26 07:08:39 192.168.122.209 [54270.134638] [tdb] Close table 'filter0.tdb' Apr 26 07:08:39 192.168.122.209 [54270.135100] [tempesta fw] modules are stopped Apr 26 07:08:39 192.168.122.209 [54270.367477] [tempesta fw] exiting... Apr 26 07:08:40 192.168.122.209 [54270.500670] [tdb] Shutdown Tempesta DB Apr 26 07:08:40 192.168.122.209 [54270.744465] End test: cache.test_cache.TestH2CacheDisable.test_cache_disable_with_override_http_chain Apr 26 07:08:40 192.168.122.209 [54270.760157] Start test: cache.test_cache.TestH2CacheHdrDel.test_cache_bypass Apr 26 07:08:41 192.168.122.209 [54271.858787] [tdb] Start Tempesta DB Apr 26 07:08:41 192.168.122.209 [54272.023019] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:08:42 192.168.122.209 [54273.413352] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54273.413352] Maybe that's fine, but it's worth checking the [54273.413352] config - if there is no relations between the [54273.413352] names, then host name confusion attack is possible. Apr 26 07:08:43 192.168.122.209 [54273.511974] [tempesta fw] Configuration processing is completed. Apr 26 07:08:43 192.168.122.209 [54273.564555] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:08:43 192.168.122.209 [54274.015969] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:08:43 192.168.122.209 [54274.045138] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:08:43 192.168.122.209 [54274.074406] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:08:43 192.168.122.209 [54274.151933] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:08:43 192.168.122.209 [54274.153770] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:08:43 192.168.122.209 [54274.191859] [tempesta fw] Tempesta FW is ready Apr 26 07:08:44 192.168.122.209 [54274.911206] [tdb] Close table 'client0.tdb' Apr 26 07:08:44 192.168.122.209 [54275.099536] [tdb] Close table 'sessions0.tdb' Apr 26 07:08:47 192.168.122.209 [54278.272866] [tdb] Close table 'cache0.tdb' Apr 26 07:08:48 192.168.122.209 [54278.510101] [tdb] Close table 'filter0.tdb' Apr 26 07:08:48 192.168.122.209 [54278.510540] [tempesta fw] modules are stopped Apr 26 07:08:48 192.168.122.209 [54278.713507] [tempesta fw] exiting... Apr 26 07:08:48 192.168.122.209 [54278.822407] [tdb] Shutdown Tempesta DB Apr 26 07:08:48 192.168.122.209 [54279.069461] End test: cache.test_cache.TestH2CacheHdrDel.test_cache_bypass Apr 26 07:08:48 192.168.122.209 [54279.091011] Start test: cache.test_cache.TestH2CacheHdrDel.test_cache_bypass_and_hdr_del Apr 26 07:08:49 192.168.122.209 [54280.170993] [tdb] Start Tempesta DB Apr 26 07:08:49 192.168.122.209 [54280.325349] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:08:51 192.168.122.209 [54281.717259] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54281.717259] Maybe that's fine, but it's worth checking the [54281.717259] config - if there is no relations between the [54281.717259] names, then host name confusion attack is possible. Apr 26 07:08:51 192.168.122.209 [54281.836032] [tempesta fw] Configuration processing is completed. Apr 26 07:08:51 192.168.122.209 [54281.889623] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:08:51 192.168.122.209 [54282.311237] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:08:51 192.168.122.209 [54282.337352] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:08:51 192.168.122.209 [54282.364553] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:08:51 192.168.122.209 [54282.436003] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:08:51 192.168.122.209 [54282.437763] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:08:51 192.168.122.209 [54282.479961] [tempesta fw] Tempesta FW is ready Apr 26 07:08:52 192.168.122.209 [54283.155081] [tdb] Close table 'client0.tdb' Apr 26 07:08:52 192.168.122.209 [54283.353108] [tdb] Close table 'sessions0.tdb' Apr 26 07:08:56 192.168.122.209 [54286.555071] [tdb] Close table 'cache0.tdb' Apr 26 07:08:56 192.168.122.209 [54286.794930] [tdb] Close table 'filter0.tdb' Apr 26 07:08:56 192.168.122.209 [54286.795364] [tempesta fw] modules are stopped Apr 26 07:08:56 192.168.122.209 [54287.009337] [tempesta fw] exiting... Apr 26 07:08:56 192.168.122.209 [54287.145363] [tdb] Shutdown Tempesta DB Apr 26 07:08:56 192.168.122.209 [54287.341421] End test: cache.test_cache.TestH2CacheHdrDel.test_cache_bypass_and_hdr_del Apr 26 07:08:56 192.168.122.209 [54287.355343] Start test: cache.test_cache.TestH2CacheHdrDel.test_cache_bypass_no_cache_with_arg Apr 26 07:08:57 192.168.122.209 [54288.401161] [tdb] Start Tempesta DB Apr 26 07:08:58 192.168.122.209 [54288.538891] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:08:59 192.168.122.209 [54289.905377] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54289.905377] Maybe that's fine, but it's worth checking the [54289.905377] config - if there is no relations between the [54289.905377] names, then host name confusion attack is possible. Apr 26 07:08:59 192.168.122.209 [54290.016122] [tempesta fw] Configuration processing is completed. Apr 26 07:08:59 192.168.122.209 [54290.067237] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:09:00 192.168.122.209 [54290.492868] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:09:00 192.168.122.209 [54290.520109] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:09:00 192.168.122.209 [54290.547080] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:09:00 192.168.122.209 [54290.584130] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:09:00 192.168.122.209 [54290.585054] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:09:00 192.168.122.209 [54290.631981] [tempesta fw] Tempesta FW is ready Apr 26 07:09:00 192.168.122.209 [54291.317197] [tdb] Close table 'client0.tdb' Apr 26 07:09:01 192.168.122.209 [54291.497377] [tdb] Close table 'sessions0.tdb' Apr 26 07:09:04 192.168.122.209 [54294.654967] [tdb] Close table 'cache0.tdb' Apr 26 07:09:04 192.168.122.209 [54294.896673] [tdb] Close table 'filter0.tdb' Apr 26 07:09:04 192.168.122.209 [54294.897115] [tempesta fw] modules are stopped Apr 26 07:09:04 192.168.122.209 [54295.093562] [tempesta fw] exiting... Apr 26 07:09:04 192.168.122.209 [54295.210131] [tdb] Shutdown Tempesta DB Apr 26 07:09:04 192.168.122.209 [54295.438004] End test: cache.test_cache.TestH2CacheHdrDel.test_cache_bypass_no_cache_with_arg Apr 26 07:09:04 192.168.122.209 [54295.451176] Start test: cache.test_cache.TestH2CacheHdrDel.test_cache_bypass_private_with_arg Apr 26 07:09:05 192.168.122.209 [54296.449364] [tdb] Start Tempesta DB Apr 26 07:09:06 192.168.122.209 [54296.584584] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:09:07 192.168.122.209 [54297.953326] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54297.953326] Maybe that's fine, but it's worth checking the [54297.953326] config - if there is no relations between the [54297.953326] names, then host name confusion attack is possible. Apr 26 07:09:07 192.168.122.209 [54298.052216] [tempesta fw] Configuration processing is completed. Apr 26 07:09:07 192.168.122.209 [54298.102469] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:09:08 192.168.122.209 [54298.523610] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:09:08 192.168.122.209 [54298.550451] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:09:08 192.168.122.209 [54298.577867] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:09:08 192.168.122.209 [54298.636210] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:09:08 192.168.122.209 [54298.637934] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:09:08 192.168.122.209 [54298.680159] [tempesta fw] Tempesta FW is ready Apr 26 07:09:08 192.168.122.209 [54299.333189] [tdb] Close table 'client0.tdb' Apr 26 07:09:09 192.168.122.209 [54299.515129] [tdb] Close table 'sessions0.tdb' Apr 26 07:09:12 192.168.122.209 [54302.738828] [tdb] Close table 'cache0.tdb' Apr 26 07:09:12 192.168.122.209 [54302.991473] [tdb] Close table 'filter0.tdb' Apr 26 07:09:12 192.168.122.209 [54302.991914] [tempesta fw] modules are stopped Apr 26 07:09:12 192.168.122.209 [54303.174305] [tempesta fw] exiting... Apr 26 07:09:12 192.168.122.209 [54303.276734] [tdb] Shutdown Tempesta DB Apr 26 07:09:12 192.168.122.209 [54303.488262] End test: cache.test_cache.TestH2CacheHdrDel.test_cache_bypass_private_with_arg Apr 26 07:09:13 192.168.122.209 [54303.507837] Start test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfill Apr 26 07:09:14 192.168.122.209 [54304.547825] [tdb] Start Tempesta DB Apr 26 07:09:14 192.168.122.209 [54304.689516] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:09:15 192.168.122.209 [54306.105561] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54306.105561] Maybe that's fine, but it's worth checking the [54306.105561] config - if there is no relations between the [54306.105561] names, then host name confusion attack is possible. Apr 26 07:09:15 192.168.122.209 [54306.212344] [tempesta fw] Configuration processing is completed. Apr 26 07:09:15 192.168.122.209 [54306.263760] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:09:16 192.168.122.209 [54306.690329] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:09:16 192.168.122.209 [54306.716669] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:09:16 192.168.122.209 [54306.742799] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:09:16 192.168.122.209 [54306.804308] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:09:16 192.168.122.209 [54306.806032] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:09:16 192.168.122.209 [54306.844253] [tempesta fw] Tempesta FW is ready Apr 26 07:09:17 192.168.122.209 [54307.494369] [tdb] Close table 'client0.tdb' Apr 26 07:09:17 192.168.122.209 [54307.687051] [tdb] Close table 'sessions0.tdb' Apr 26 07:09:20 192.168.122.209 [54310.889406] [tdb] Close table 'cache0.tdb' Apr 26 07:09:20 192.168.122.209 [54311.138885] [tdb] Close table 'filter0.tdb' Apr 26 07:09:20 192.168.122.209 [54311.139304] [tempesta fw] modules are stopped Apr 26 07:09:20 192.168.122.209 [54311.382339] [tempesta fw] exiting... Apr 26 07:09:21 192.168.122.209 [54311.495854] [tdb] Shutdown Tempesta DB Apr 26 07:09:21 192.168.122.209 [54311.724774] End test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfill Apr 26 07:09:21 192.168.122.209 [54311.743191] Start test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfill_and_hdr_del Apr 26 07:09:22 192.168.122.209 [54312.781676] [tdb] Start Tempesta DB Apr 26 07:09:22 192.168.122.209 [54312.924185] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:09:23 192.168.122.209 [54314.361704] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54314.361704] Maybe that's fine, but it's worth checking the [54314.361704] config - if there is no relations between the [54314.361704] names, then host name confusion attack is possible. Apr 26 07:09:23 192.168.122.209 [54314.476454] [tempesta fw] Configuration processing is completed. Apr 26 07:09:24 192.168.122.209 [54314.526110] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:09:24 192.168.122.209 [54314.948958] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:09:24 192.168.122.209 [54314.982946] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:09:24 192.168.122.209 [54315.010321] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:09:24 192.168.122.209 [54315.056434] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:09:24 192.168.122.209 [54315.057889] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:09:24 192.168.122.209 [54315.100360] [tempesta fw] Tempesta FW is ready Apr 26 07:09:25 192.168.122.209 [54315.749076] [tdb] Close table 'client0.tdb' Apr 26 07:09:25 192.168.122.209 [54315.933798] [tdb] Close table 'sessions0.tdb' Apr 26 07:09:28 192.168.122.209 [54319.134151] [tdb] Close table 'cache0.tdb' Apr 26 07:09:28 192.168.122.209 [54319.377799] [tdb] Close table 'filter0.tdb' Apr 26 07:09:28 192.168.122.209 [54319.378244] [tempesta fw] modules are stopped Apr 26 07:09:29 192.168.122.209 [54319.553040] [tempesta fw] exiting... Apr 26 07:09:29 192.168.122.209 [54319.698069] [tdb] Shutdown Tempesta DB Apr 26 07:09:29 192.168.122.209 [54319.938407] End test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfill_and_hdr_del Apr 26 07:09:29 192.168.122.209 [54319.947649] Start test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfilll_multi_cache_control Apr 26 07:09:30 192.168.122.209 [54320.991423] [tdb] Start Tempesta DB Apr 26 07:09:30 192.168.122.209 [54321.117031] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:09:32 192.168.122.209 [54322.581749] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54322.581749] Maybe that's fine, but it's worth checking the [54322.581749] config - if there is no relations between the [54322.581749] names, then host name confusion attack is possible. Apr 26 07:09:32 192.168.122.209 [54322.692526] [tempesta fw] Configuration processing is completed. Apr 26 07:09:32 192.168.122.209 [54322.752366] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:09:32 192.168.122.209 [54323.214292] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:09:32 192.168.122.209 [54323.243814] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:09:32 192.168.122.209 [54323.273523] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:09:32 192.168.122.209 [54323.344500] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:09:32 192.168.122.209 [54323.346225] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:09:32 192.168.122.209 [54323.388412] [tempesta fw] Tempesta FW is ready Apr 26 07:09:33 192.168.122.209 [54324.082652] [tdb] Close table 'client0.tdb' Apr 26 07:09:33 192.168.122.209 [54324.264744] [tdb] Close table 'sessions0.tdb' Apr 26 07:09:36 192.168.122.209 [54327.484024] [tdb] Close table 'cache0.tdb' Apr 26 07:09:37 192.168.122.209 [54327.726054] [tdb] Close table 'filter0.tdb' Apr 26 07:09:37 192.168.122.209 [54327.726491] [tempesta fw] modules are stopped Apr 26 07:09:37 192.168.122.209 [54327.917484] [tempesta fw] exiting... Apr 26 07:09:37 192.168.122.209 [54328.050201] [tdb] Shutdown Tempesta DB Apr 26 07:09:37 192.168.122.209 [54328.290300] End test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfilll_multi_cache_control Apr 26 07:09:37 192.168.122.209 [54328.303827] Start test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfilll_multi_cache_control_2 Apr 26 07:09:38 192.168.122.209 [54329.366562] [tdb] Start Tempesta DB Apr 26 07:09:39 192.168.122.209 [54329.516975] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:09:40 192.168.122.209 [54331.005870] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54331.005870] Maybe that's fine, but it's worth checking the [54331.005870] config - if there is no relations between the [54331.005870] names, then host name confusion attack is possible. Apr 26 07:09:40 192.168.122.209 [54331.124577] [tempesta fw] Configuration processing is completed. Apr 26 07:09:40 192.168.122.209 [54331.175696] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:09:41 192.168.122.209 [54331.602683] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:09:41 192.168.122.209 [54331.629272] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:09:41 192.168.122.209 [54331.655855] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:09:41 192.168.122.209 [54331.716627] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:09:41 192.168.122.209 [54331.718397] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:09:41 192.168.122.209 [54331.752504] [tempesta fw] Tempesta FW is ready Apr 26 07:09:41 192.168.122.209 [54332.422200] [tdb] Close table 'client0.tdb' Apr 26 07:09:42 192.168.122.209 [54332.630644] [tdb] Close table 'sessions0.tdb' Apr 26 07:09:45 192.168.122.209 [54335.891674] [tdb] Close table 'cache0.tdb' Apr 26 07:09:45 192.168.122.209 [54336.146179] [tdb] Close table 'filter0.tdb' Apr 26 07:09:45 192.168.122.209 [54336.146607] [tempesta fw] modules are stopped Apr 26 07:09:45 192.168.122.209 [54336.325804] [tempesta fw] exiting... Apr 26 07:09:45 192.168.122.209 [54336.440969] [tdb] Shutdown Tempesta DB Apr 26 07:09:46 192.168.122.209 [54336.668954] End test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfilll_multi_cache_control_2 Apr 26 07:09:46 192.168.122.209 [54336.690345] Start test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfilll_no_cache_with_arg Apr 26 07:09:47 192.168.122.209 [54337.758775] [tdb] Start Tempesta DB Apr 26 07:09:47 192.168.122.209 [54337.913489] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:09:48 192.168.122.209 [54339.281959] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54339.281959] Maybe that's fine, but it's worth checking the [54339.281959] config - if there is no relations between the [54339.281959] names, then host name confusion attack is possible. Apr 26 07:09:48 192.168.122.209 [54339.388737] [tempesta fw] Configuration processing is completed. Apr 26 07:09:48 192.168.122.209 [54339.442632] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:09:49 192.168.122.209 [54339.861898] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:09:49 192.168.122.209 [54339.888222] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:09:49 192.168.122.209 [54339.915292] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:09:49 192.168.122.209 [54339.960675] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:09:49 192.168.122.209 [54339.961852] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:09:49 192.168.122.209 [54340.000681] [tempesta fw] Tempesta FW is ready Apr 26 07:09:50 192.168.122.209 [54340.675326] [tdb] Close table 'client0.tdb' Apr 26 07:09:50 192.168.122.209 [54340.894939] [tdb] Close table 'sessions0.tdb' Apr 26 07:09:53 192.168.122.209 [54344.081691] [tdb] Close table 'cache0.tdb' Apr 26 07:09:53 192.168.122.209 [54344.334530] [tdb] Close table 'filter0.tdb' Apr 26 07:09:53 192.168.122.209 [54344.334968] [tempesta fw] modules are stopped Apr 26 07:09:54 192.168.122.209 [54344.522096] [tempesta fw] exiting... Apr 26 07:09:54 192.168.122.209 [54344.629360] [tdb] Shutdown Tempesta DB Apr 26 07:09:54 192.168.122.209 [54344.847186] End test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfilll_no_cache_with_arg Apr 26 07:09:54 192.168.122.209 [54344.861707] Start test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfilll_no_cache_with_arg_2 Apr 26 07:09:55 192.168.122.209 [54345.915292] [tdb] Start Tempesta DB Apr 26 07:09:55 192.168.122.209 [54346.057121] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:09:56 192.168.122.209 [54347.421996] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54347.421996] Maybe that's fine, but it's worth checking the [54347.421996] config - if there is no relations between the [54347.421996] names, then host name confusion attack is possible. Apr 26 07:09:57 192.168.122.209 [54347.544837] [tempesta fw] Configuration processing is completed. Apr 26 07:09:57 192.168.122.209 [54347.596374] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:09:57 192.168.122.209 [54348.019502] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:09:57 192.168.122.209 [54348.045596] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:09:57 192.168.122.209 [54348.071255] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:09:57 192.168.122.209 [54348.132825] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:09:57 192.168.122.209 [54348.134553] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:09:57 192.168.122.209 [54348.184788] [tempesta fw] Tempesta FW is ready Apr 26 07:09:58 192.168.122.209 [54348.873723] [tdb] Close table 'client0.tdb' Apr 26 07:09:58 192.168.122.209 [54349.058820] [tdb] Close table 'sessions0.tdb' Apr 26 07:10:01 192.168.122.209 [54352.245463] [tdb] Close table 'cache0.tdb' Apr 26 07:10:02 192.168.122.209 [54352.496161] [tdb] Close table 'filter0.tdb' Apr 26 07:10:02 192.168.122.209 [54352.496584] [tempesta fw] modules are stopped Apr 26 07:10:02 192.168.122.209 [54352.694312] [tempesta fw] exiting... Apr 26 07:10:02 192.168.122.209 [54352.834467] [tdb] Shutdown Tempesta DB Apr 26 07:10:02 192.168.122.209 [54353.099598] End test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfilll_no_cache_with_arg_2 Apr 26 07:10:02 192.168.122.209 [54353.120966] Start test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfilll_no_cache_with_args Apr 26 07:10:03 192.168.122.209 [54354.148822] [tdb] Start Tempesta DB Apr 26 07:10:03 192.168.122.209 [54354.284397] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:10:05 192.168.122.209 [54355.822187] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54355.822187] Maybe that's fine, but it's worth checking the [54355.822187] config - if there is no relations between the [54355.822187] names, then host name confusion attack is possible. Apr 26 07:10:05 192.168.122.209 [54355.920991] [tempesta fw] Configuration processing is completed. Apr 26 07:10:05 192.168.122.209 [54355.970942] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:10:05 192.168.122.209 [54356.398529] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:10:05 192.168.122.209 [54356.432757] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:10:05 192.168.122.209 [54356.460277] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:10:06 192.168.122.209 [54356.520942] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:10:06 192.168.122.209 [54356.522705] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:10:06 192.168.122.209 [54356.560880] [tempesta fw] Tempesta FW is ready Apr 26 07:10:06 192.168.122.209 [54357.240713] [tdb] Close table 'client0.tdb' Apr 26 07:10:06 192.168.122.209 [54357.430292] [tdb] Close table 'sessions0.tdb' Apr 26 07:10:10 192.168.122.209 [54360.616821] [tdb] Close table 'cache0.tdb' Apr 26 07:10:10 192.168.122.209 [54360.853816] [tdb] Close table 'filter0.tdb' Apr 26 07:10:10 192.168.122.209 [54360.854237] [tempesta fw] modules are stopped Apr 26 07:10:10 192.168.122.209 [54361.024580] [tempesta fw] exiting... Apr 26 07:10:10 192.168.122.209 [54361.125121] [tdb] Shutdown Tempesta DB Apr 26 07:10:10 192.168.122.209 [54361.330659] End test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfilll_no_cache_with_args Apr 26 07:10:10 192.168.122.209 [54361.350789] Start test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfilll_private_with_arg Apr 26 07:10:11 192.168.122.209 [54362.431490] [tdb] Start Tempesta DB Apr 26 07:10:12 192.168.122.209 [54362.577070] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:10:13 192.168.122.209 [54364.034344] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54364.034344] Maybe that's fine, but it's worth checking the [54364.034344] config - if there is no relations between the [54364.034344] names, then host name confusion attack is possible. Apr 26 07:10:13 192.168.122.209 [54364.129064] [tempesta fw] Configuration processing is completed. Apr 26 07:10:13 192.168.122.209 [54364.183457] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:10:14 192.168.122.209 [54364.601035] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:10:14 192.168.122.209 [54364.627169] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:10:14 192.168.122.209 [54364.653284] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:10:14 192.168.122.209 [54364.697013] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:10:14 192.168.122.209 [54364.698189] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:10:14 192.168.122.209 [54364.748992] [tempesta fw] Tempesta FW is ready Apr 26 07:10:14 192.168.122.209 [54365.404247] [tdb] Close table 'client0.tdb' Apr 26 07:10:15 192.168.122.209 [54365.607090] [tdb] Close table 'sessions0.tdb' Apr 26 07:10:18 192.168.122.209 [54368.965536] [tdb] Close table 'cache0.tdb' Apr 26 07:10:18 192.168.122.209 [54369.214076] [tdb] Close table 'filter0.tdb' Apr 26 07:10:18 192.168.122.209 [54369.214504] [tempesta fw] modules are stopped Apr 26 07:10:18 192.168.122.209 [54369.397337] [tempesta fw] exiting... Apr 26 07:10:19 192.168.122.209 [54369.539570] [tdb] Shutdown Tempesta DB Apr 26 07:10:19 192.168.122.209 [54369.755012] End test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfilll_private_with_arg Apr 26 07:10:19 192.168.122.209 [54369.775681] Start test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfilll_private_with_arg_2 Apr 26 07:10:20 192.168.122.209 [54370.804524] [tdb] Start Tempesta DB Apr 26 07:10:20 192.168.122.209 [54370.942923] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:10:21 192.168.122.209 [54372.326380] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54372.326380] Maybe that's fine, but it's worth checking the [54372.326380] config - if there is no relations between the [54372.326380] names, then host name confusion attack is possible. Apr 26 07:10:21 192.168.122.209 [54372.429122] [tempesta fw] Configuration processing is completed. Apr 26 07:10:21 192.168.122.209 [54372.474985] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:10:22 192.168.122.209 [54372.897398] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:10:22 192.168.122.209 [54372.923799] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:10:22 192.168.122.209 [54372.950878] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:10:22 192.168.122.209 [54372.993033] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:10:22 192.168.122.209 [54372.994067] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:10:22 192.168.122.209 [54373.033027] [tempesta fw] Tempesta FW is ready Apr 26 07:10:23 192.168.122.209 [54373.689088] [tdb] Close table 'client0.tdb' Apr 26 07:10:23 192.168.122.209 [54373.871798] [tdb] Close table 'sessions0.tdb' Apr 26 07:10:26 192.168.122.209 [54377.106393] [tdb] Close table 'cache0.tdb' Apr 26 07:10:26 192.168.122.209 [54377.359680] [tdb] Close table 'filter0.tdb' Apr 26 07:10:26 192.168.122.209 [54377.360110] [tempesta fw] modules are stopped Apr 26 07:10:27 192.168.122.209 [54377.572715] [tempesta fw] exiting... Apr 26 07:10:27 192.168.122.209 [54377.724362] [tdb] Shutdown Tempesta DB Apr 26 07:10:27 192.168.122.209 [54377.947957] End test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfilll_private_with_arg_2 Apr 26 07:10:27 192.168.122.209 [54377.972521] Start test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfilll_private_with_args Apr 26 07:10:28 192.168.122.209 [54379.011523] [tdb] Start Tempesta DB Apr 26 07:10:28 192.168.122.209 [54379.163282] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:10:30 192.168.122.209 [54380.546564] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54380.546564] Maybe that's fine, but it's worth checking the [54380.546564] config - if there is no relations between the [54380.546564] names, then host name confusion attack is possible. Apr 26 07:10:30 192.168.122.209 [54380.645276] [tempesta fw] Configuration processing is completed. Apr 26 07:10:30 192.168.122.209 [54380.700650] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:10:30 192.168.122.209 [54381.124073] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:10:30 192.168.122.209 [54381.151032] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:10:30 192.168.122.209 [54381.177315] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:10:30 192.168.122.209 [54381.245258] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:10:30 192.168.122.209 [54381.247017] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:10:30 192.168.122.209 [54381.289192] [tempesta fw] Tempesta FW is ready Apr 26 07:10:31 192.168.122.209 [54381.944564] [tdb] Close table 'client0.tdb' Apr 26 07:10:31 192.168.122.209 [54382.123221] [tdb] Close table 'sessions0.tdb' Apr 26 07:10:34 192.168.122.209 [54385.310296] [tdb] Close table 'cache0.tdb' Apr 26 07:10:35 192.168.122.209 [54385.542435] [tdb] Close table 'filter0.tdb' Apr 26 07:10:35 192.168.122.209 [54385.542888] [tempesta fw] modules are stopped Apr 26 07:10:35 192.168.122.209 [54385.804396] [tempesta fw] exiting... Apr 26 07:10:35 192.168.122.209 [54385.943643] [tdb] Shutdown Tempesta DB Apr 26 07:10:35 192.168.122.209 [54386.157873] End test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfilll_private_with_args Apr 26 07:10:35 192.168.122.209 [54386.174438] Start test: cache.test_cache.TestH2CacheTtl.test_global_cache_ttl_3_sleep_0 Apr 26 07:10:36 192.168.122.209 [54387.214313] [tdb] Start Tempesta DB Apr 26 07:10:36 192.168.122.209 [54387.365885] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:10:38 192.168.122.209 [54389.014305] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54389.014305] Maybe that's fine, but it's worth checking the [54389.014305] config - if there is no relations between the [54389.014305] names, then host name confusion attack is possible. Apr 26 07:10:38 192.168.122.209 [54389.189382] [tempesta fw] Configuration processing is completed. Apr 26 07:10:38 192.168.122.209 [54389.240093] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:10:39 192.168.122.209 [54389.666931] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:10:39 192.168.122.209 [54389.694952] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:10:39 192.168.122.209 [54389.721674] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:10:39 192.168.122.209 [54389.809316] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:10:39 192.168.122.209 [54389.811334] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:10:39 192.168.122.209 [54389.849302] [tempesta fw] Tempesta FW is ready Apr 26 07:10:40 192.168.122.209 [54390.521147] [tdb] Close table 'client0.tdb' Apr 26 07:10:40 192.168.122.209 [54390.711405] [tdb] Close table 'sessions0.tdb' Apr 26 07:10:43 192.168.122.209 [54393.898227] [tdb] Close table 'cache0.tdb' Apr 26 07:10:43 192.168.122.209 [54394.138316] [tdb] Close table 'filter0.tdb' Apr 26 07:10:43 192.168.122.209 [54394.138759] [tempesta fw] modules are stopped Apr 26 07:10:43 192.168.122.209 [54394.370519] [tempesta fw] exiting... Apr 26 07:10:44 192.168.122.209 [54394.498412] [tdb] Shutdown Tempesta DB Apr 26 07:10:44 192.168.122.209 [54394.715543] End test: cache.test_cache.TestH2CacheTtl.test_global_cache_ttl_3_sleep_0 Apr 26 07:10:44 192.168.122.209 [54394.739038] Start test: cache.test_cache.TestH2CacheTtl.test_global_cache_ttl_3_sleep_2_max_age_1 Apr 26 07:10:45 192.168.122.209 [54395.821033] [tdb] Start Tempesta DB Apr 26 07:10:45 192.168.122.209 [54395.962021] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:10:47 192.168.122.209 [54397.606722] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54397.606722] Maybe that's fine, but it's worth checking the [54397.606722] config - if there is no relations between the [54397.606722] names, then host name confusion attack is possible. Apr 26 07:10:47 192.168.122.209 [54397.793490] [tempesta fw] Configuration processing is completed. Apr 26 07:10:47 192.168.122.209 [54397.856516] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:10:47 192.168.122.209 [54398.269083] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:10:47 192.168.122.209 [54398.295676] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:10:47 192.168.122.209 [54398.322921] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:10:47 192.168.122.209 [54398.401506] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:10:47 192.168.122.209 [54398.403251] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:10:47 192.168.122.209 [54398.457423] [tempesta fw] Tempesta FW is ready Apr 26 07:10:50 192.168.122.209 [54401.114348] [tdb] Close table 'client0.tdb' Apr 26 07:10:50 192.168.122.209 [54401.283009] [tdb] Close table 'sessions0.tdb' Apr 26 07:10:53 192.168.122.209 [54404.487114] [tdb] Close table 'cache0.tdb' Apr 26 07:10:54 192.168.122.209 [54404.750147] [tdb] Close table 'filter0.tdb' Apr 26 07:10:54 192.168.122.209 [54404.750602] [tempesta fw] modules are stopped Apr 26 07:10:54 192.168.122.209 [54405.018083] [tempesta fw] exiting... Apr 26 07:10:54 192.168.122.209 [54405.143590] [tdb] Shutdown Tempesta DB Apr 26 07:10:54 192.168.122.209 [54405.381710] End test: cache.test_cache.TestH2CacheTtl.test_global_cache_ttl_3_sleep_2_max_age_1 Apr 26 07:10:54 192.168.122.209 [54405.405906] Start test: cache.test_cache.TestH2CacheTtl.test_global_cache_ttl_3_sleep_2_s_maxage_1 Apr 26 07:10:55 192.168.122.209 [54406.450485] [tdb] Start Tempesta DB Apr 26 07:10:56 192.168.122.209 [54406.581536] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:10:57 192.168.122.209 [54408.202825] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54408.202825] Maybe that's fine, but it's worth checking the [54408.202825] config - if there is no relations between the [54408.202825] names, then host name confusion attack is possible. Apr 26 07:10:57 192.168.122.209 [54408.385612] [tempesta fw] Configuration processing is completed. Apr 26 07:10:57 192.168.122.209 [54408.436521] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:10:58 192.168.122.209 [54408.853781] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:10:58 192.168.122.209 [54408.879773] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:10:58 192.168.122.209 [54408.905661] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:10:58 192.168.122.209 [54408.953609] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:10:58 192.168.122.209 [54408.955339] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:10:58 192.168.122.209 [54408.997542] [tempesta fw] Tempesta FW is ready Apr 26 07:11:01 192.168.122.209 [54411.598256] [tdb] Close table 'client0.tdb' Apr 26 07:11:01 192.168.122.209 [54411.789786] [tdb] Close table 'sessions0.tdb' Apr 26 07:11:04 192.168.122.209 [54414.963953] [tdb] Close table 'cache0.tdb' Apr 26 07:11:04 192.168.122.209 [54415.217112] [tdb] Close table 'filter0.tdb' Apr 26 07:11:04 192.168.122.209 [54415.217573] [tempesta fw] modules are stopped Apr 26 07:11:04 192.168.122.209 [54415.422089] [tempesta fw] exiting... Apr 26 07:11:05 192.168.122.209 [54415.567853] [tdb] Shutdown Tempesta DB Apr 26 07:11:05 192.168.122.209 [54415.782483] End test: cache.test_cache.TestH2CacheTtl.test_global_cache_ttl_3_sleep_2_s_maxage_1 Apr 26 07:11:05 192.168.122.209 [54415.800935] Start test: cache.test_cache.TestH2CacheTtl.test_global_cache_ttl_3_sleep_4 Apr 26 07:11:06 192.168.122.209 [54416.899859] [tdb] Start Tempesta DB Apr 26 07:11:06 192.168.122.209 [54417.038608] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:11:08 192.168.122.209 [54418.671027] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54418.671027] Maybe that's fine, but it's worth checking the [54418.671027] config - if there is no relations between the [54418.671027] names, then host name confusion attack is possible. Apr 26 07:11:08 192.168.122.209 [54418.861737] [tempesta fw] Configuration processing is completed. Apr 26 07:11:08 192.168.122.209 [54418.919845] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:11:08 192.168.122.209 [54419.383119] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:11:08 192.168.122.209 [54419.418932] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:11:08 192.168.122.209 [54419.447293] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:11:08 192.168.122.209 [54419.481668] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:11:08 192.168.122.209 [54419.482606] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:11:09 192.168.122.209 [54419.521688] [tempesta fw] Tempesta FW is ready Apr 26 07:11:13 192.168.122.209 [54424.166057] [tdb] Close table 'client0.tdb' Apr 26 07:11:13 192.168.122.209 [54424.348940] [tdb] Close table 'sessions0.tdb' Apr 26 07:11:17 192.168.122.209 [54427.548021] [tdb] Close table 'cache0.tdb' Apr 26 07:11:17 192.168.122.209 [54427.786494] [tdb] Close table 'filter0.tdb' Apr 26 07:11:17 192.168.122.209 [54427.786945] [tempesta fw] modules are stopped Apr 26 07:11:17 192.168.122.209 [54428.036697] [tempesta fw] exiting... Apr 26 07:11:17 192.168.122.209 [54428.153094] [tdb] Shutdown Tempesta DB Apr 26 07:11:17 192.168.122.209 [54428.345925] End test: cache.test_cache.TestH2CacheTtl.test_global_cache_ttl_3_sleep_4 Apr 26 07:11:17 192.168.122.209 [54428.380820] Start test: cache.test_cache.TestH2CacheTtl.test_global_cache_ttl_3_sleep_4_max_age_10 Apr 26 07:11:18 192.168.122.209 [54429.428253] [tdb] Start Tempesta DB Apr 26 07:11:19 192.168.122.209 [54429.557558] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:11:20 192.168.122.209 [54431.170535] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54431.170535] Maybe that's fine, but it's worth checking the [54431.170535] config - if there is no relations between the [54431.170535] names, then host name confusion attack is possible. Apr 26 07:11:20 192.168.122.209 [54431.345876] [tempesta fw] Configuration processing is completed. Apr 26 07:11:20 192.168.122.209 [54431.400015] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:11:21 192.168.122.209 [54431.816532] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:11:21 192.168.122.209 [54431.843646] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:11:21 192.168.122.209 [54431.869586] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:11:21 192.168.122.209 [54431.953896] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:11:21 192.168.122.209 [54431.955636] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:11:21 192.168.122.209 [54432.005865] [tempesta fw] Tempesta FW is ready Apr 26 07:11:26 192.168.122.209 [54437.119783] [tdb] Close table 'client0.tdb' Apr 26 07:11:26 192.168.122.209 [54437.387194] [tdb] Close table 'sessions0.tdb' Apr 26 07:11:31 192.168.122.209 [54441.827037] [tdb] Close table 'cache0.tdb' Apr 26 07:11:31 192.168.122.209 [54442.075679] [tdb] Close table 'filter0.tdb' Apr 26 07:11:31 192.168.122.209 [54442.076101] [tempesta fw] modules are stopped Apr 26 07:11:31 192.168.122.209 [54442.303033] [tempesta fw] exiting... Apr 26 07:11:31 192.168.122.209 [54442.431591] [tdb] Shutdown Tempesta DB Apr 26 07:11:32 192.168.122.209 [54442.647518] End test: cache.test_cache.TestH2CacheTtl.test_global_cache_ttl_3_sleep_4_max_age_10 Apr 26 07:11:32 192.168.122.209 [54442.667040] Start test: cache.test_cache.TestH2CacheTtl.test_priority_for_cache_control_header_no_cache Apr 26 07:11:33 192.168.122.209 [54443.745836] [tdb] Start Tempesta DB Apr 26 07:11:33 192.168.122.209 [54443.879801] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:11:35 192.168.122.209 [54445.539285] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54445.539285] Maybe that's fine, but it's worth checking the [54445.539285] config - if there is no relations between the [54445.539285] names, then host name confusion attack is possible. Apr 26 07:11:35 192.168.122.209 [54445.726059] [tempesta fw] Configuration processing is completed. Apr 26 07:11:35 192.168.122.209 [54445.777294] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:11:35 192.168.122.209 [54446.186516] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:11:35 192.168.122.209 [54446.212655] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:11:35 192.168.122.209 [54446.239618] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:11:35 192.168.122.209 [54446.290072] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:11:35 192.168.122.209 [54446.291830] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:11:35 192.168.122.209 [54446.338013] [tempesta fw] Tempesta FW is ready Apr 26 07:11:36 192.168.122.209 [54446.993603] [tdb] Close table 'client0.tdb' Apr 26 07:11:36 192.168.122.209 [54447.187334] [tdb] Close table 'sessions0.tdb' Apr 26 07:11:39 192.168.122.209 [54450.378464] [tdb] Close table 'cache0.tdb' Apr 26 07:11:40 192.168.122.209 [54450.638174] [tdb] Close table 'filter0.tdb' Apr 26 07:11:40 192.168.122.209 [54450.638635] [tempesta fw] modules are stopped Apr 26 07:11:40 192.168.122.209 [54450.864615] [tempesta fw] exiting... Apr 26 07:11:40 192.168.122.209 [54451.003865] [tdb] Shutdown Tempesta DB Apr 26 07:11:40 192.168.122.209 [54451.208008] End test: cache.test_cache.TestH2CacheTtl.test_priority_for_cache_control_header_no_cache Apr 26 07:11:40 192.168.122.209 [54451.236308] Start test: cache.test_cache.TestH2CacheTtl.test_priority_for_cache_control_header_no_store Apr 26 07:11:41 192.168.122.209 [54452.288519] [tdb] Start Tempesta DB Apr 26 07:11:41 192.168.122.209 [54452.430572] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:11:43 192.168.122.209 [54454.039408] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54454.039408] Maybe that's fine, but it's worth checking the [54454.039408] config - if there is no relations between the [54454.039408] names, then host name confusion attack is possible. Apr 26 07:11:43 192.168.122.209 [54454.214176] [tempesta fw] Configuration processing is completed. Apr 26 07:11:43 192.168.122.209 [54454.265109] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:11:44 192.168.122.209 [54454.684586] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:11:44 192.168.122.209 [54454.710654] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:11:44 192.168.122.209 [54454.736315] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:11:44 192.168.122.209 [54454.774125] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:11:44 192.168.122.209 [54454.775268] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:11:44 192.168.122.209 [54454.822118] [tempesta fw] Tempesta FW is ready Apr 26 07:11:44 192.168.122.209 [54455.484140] [tdb] Close table 'client0.tdb' Apr 26 07:11:45 192.168.122.209 [54455.672895] [tdb] Close table 'sessions0.tdb' Apr 26 07:11:48 192.168.122.209 [54458.878290] [tdb] Close table 'cache0.tdb' Apr 26 07:11:48 192.168.122.209 [54459.094619] [tdb] Close table 'filter0.tdb' Apr 26 07:11:48 192.168.122.209 [54459.095072] [tempesta fw] modules are stopped Apr 26 07:11:48 192.168.122.209 [54459.386176] [tempesta fw] exiting... Apr 26 07:11:49 192.168.122.209 [54459.513421] [tdb] Shutdown Tempesta DB Apr 26 07:11:49 192.168.122.209 [54459.741013] End test: cache.test_cache.TestH2CacheTtl.test_priority_for_cache_control_header_no_store Apr 26 07:11:49 192.168.122.209 [54459.759031] Start test: cache.test_cache.TestH2CacheTtl.test_priority_for_cache_control_header_private Apr 26 07:11:50 192.168.122.209 [54460.796011] [tdb] Start Tempesta DB Apr 26 07:11:50 192.168.122.209 [54460.936205] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:11:52 192.168.122.209 [54462.591546] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54462.591546] Maybe that's fine, but it's worth checking the [54462.591546] config - if there is no relations between the [54462.591546] names, then host name confusion attack is possible. Apr 26 07:11:52 192.168.122.209 [54462.778271] [tempesta fw] Configuration processing is completed. Apr 26 07:11:52 192.168.122.209 [54462.830556] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:11:52 192.168.122.209 [54463.254132] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:11:52 192.168.122.209 [54463.281488] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:11:52 192.168.122.209 [54463.309681] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:11:52 192.168.122.209 [54463.362290] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:11:52 192.168.122.209 [54463.363758] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:11:52 192.168.122.209 [54463.402245] [tempesta fw] Tempesta FW is ready Apr 26 07:11:53 192.168.122.209 [54464.095182] [tdb] Close table 'client0.tdb' Apr 26 07:11:53 192.168.122.209 [54464.281014] [tdb] Close table 'sessions0.tdb' Apr 26 07:11:57 192.168.122.209 [54467.516456] [tdb] Close table 'cache0.tdb' Apr 26 07:11:57 192.168.122.209 [54467.747283] [tdb] Close table 'filter0.tdb' Apr 26 07:11:57 192.168.122.209 [54467.747723] [tempesta fw] modules are stopped Apr 26 07:11:57 192.168.122.209 [54467.949960] [tempesta fw] exiting... Apr 26 07:11:57 192.168.122.209 [54468.088951] [tdb] Shutdown Tempesta DB Apr 26 07:11:57 192.168.122.209 [54468.314909] End test: cache.test_cache.TestH2CacheTtl.test_priority_for_cache_control_header_private Apr 26 07:11:57 192.168.122.209 [54468.333503] Start test: cache.test_cache.TestH2CacheTtl.test_vhost_cache_ttl_1_sleep_2 Apr 26 07:11:58 192.168.122.209 [54469.400441] [tdb] Start Tempesta DB Apr 26 07:11:59 192.168.122.209 [54469.540415] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:12:00 192.168.122.209 [54471.175752] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54471.175752] Maybe that's fine, but it's worth checking the [54471.175752] config - if there is no relations between the [54471.175752] names, then host name confusion attack is possible. Apr 26 07:12:00 192.168.122.209 [54471.370323] [tempesta fw] Configuration processing is completed. Apr 26 07:12:00 192.168.122.209 [54471.422620] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:12:01 192.168.122.209 [54471.841424] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:12:01 192.168.122.209 [54471.878523] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:12:01 192.168.122.209 [54471.904774] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:12:01 192.168.122.209 [54471.954375] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:12:01 192.168.122.209 [54471.955867] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:12:01 192.168.122.209 [54472.002337] [tempesta fw] Tempesta FW is ready Apr 26 07:12:04 192.168.122.209 [54474.693021] [tdb] Close table 'client0.tdb' Apr 26 07:12:04 192.168.122.209 [54474.873046] [tdb] Close table 'sessions0.tdb' Apr 26 07:12:07 192.168.122.209 [54478.163045] [tdb] Close table 'cache0.tdb' Apr 26 07:12:07 192.168.122.209 [54478.408752] [tdb] Close table 'filter0.tdb' Apr 26 07:12:07 192.168.122.209 [54478.409230] [tempesta fw] modules are stopped Apr 26 07:12:08 192.168.122.209 [54478.651043] [tempesta fw] exiting... Apr 26 07:12:08 192.168.122.209 [54478.777531] [tdb] Shutdown Tempesta DB Apr 26 07:12:08 192.168.122.209 [54479.018025] End test: cache.test_cache.TestH2CacheTtl.test_vhost_cache_ttl_1_sleep_2 Apr 26 07:12:08 192.168.122.209 [54479.037663] Start test: cache.test_cache.TestH2CacheTtl.test_vhost_cache_ttl_1_sleep_4 Apr 26 07:12:09 192.168.122.209 [54480.214023] [tdb] Start Tempesta DB Apr 26 07:12:09 192.168.122.209 [54480.362586] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:12:11 192.168.122.209 [54482.051895] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54482.051895] Maybe that's fine, but it's worth checking the [54482.051895] config - if there is no relations between the [54482.051895] names, then host name confusion attack is possible. Apr 26 07:12:11 192.168.122.209 [54482.246523] [tempesta fw] Configuration processing is completed. Apr 26 07:12:11 192.168.122.209 [54482.296851] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:12:12 192.168.122.209 [54482.717678] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:12:12 192.168.122.209 [54482.744338] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:12:12 192.168.122.209 [54482.772149] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:12:12 192.168.122.209 [54482.814478] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:12:12 192.168.122.209 [54482.815869] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:12:12 192.168.122.209 [54482.862479] [tempesta fw] Tempesta FW is ready Apr 26 07:12:17 192.168.122.209 [54487.541204] [tdb] Close table 'client0.tdb' Apr 26 07:12:17 192.168.122.209 [54487.740730] [tdb] Close table 'sessions0.tdb' Apr 26 07:12:20 192.168.122.209 [54490.929800] [tdb] Close table 'cache0.tdb' Apr 26 07:12:20 192.168.122.209 [54491.174514] [tdb] Close table 'filter0.tdb' Apr 26 07:12:20 192.168.122.209 [54491.174953] [tempesta fw] modules are stopped Apr 26 07:12:20 192.168.122.209 [54491.429072] [tempesta fw] exiting... Apr 26 07:12:21 192.168.122.209 [54491.528820] [tdb] Shutdown Tempesta DB Apr 26 07:12:21 192.168.122.209 [54491.792800] End test: cache.test_cache.TestH2CacheTtl.test_vhost_cache_ttl_1_sleep_4 Apr 26 07:12:21 192.168.122.209 [54491.812051] Start test: cache.test_cache.TestQueryparamsAndRedirectH2.test_query_param_different_key Apr 26 07:12:22 192.168.122.209 [54492.838918] [tdb] Start Tempesta DB Apr 26 07:12:22 192.168.122.209 [54492.972621] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:12:23 192.168.122.209 [54494.431919] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54494.431919] Maybe that's fine, but it's worth checking the [54494.431919] config - if there is no relations between the [54494.431919] names, then host name confusion attack is possible. Apr 26 07:12:24 192.168.122.209 [54494.518695] [tempesta fw] Configuration processing is completed. Apr 26 07:12:24 192.168.122.209 [54494.568877] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:12:24 192.168.122.209 [54494.980954] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:12:24 192.168.122.209 [54495.009115] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:12:24 192.168.122.209 [54495.034584] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:12:24 192.168.122.209 [54495.074679] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:12:24 192.168.122.209 [54495.076387] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:12:24 192.168.122.209 [54495.114625] [tempesta fw] Tempesta FW is ready Apr 26 07:12:25 192.168.122.209 [54495.778868] [tdb] Close table 'client0.tdb' Apr 26 07:12:25 192.168.122.209 [54495.974855] [tdb] Close table 'sessions0.tdb' Apr 26 07:12:28 192.168.122.209 [54499.181387] [tdb] Close table 'cache0.tdb' Apr 26 07:12:28 192.168.122.209 [54499.435712] [tdb] Close table 'filter0.tdb' Apr 26 07:12:28 192.168.122.209 [54499.436146] [tempesta fw] modules are stopped Apr 26 07:12:29 192.168.122.209 [54499.623431] [tempesta fw] exiting... Apr 26 07:12:29 192.168.122.209 [54499.725049] [tdb] Shutdown Tempesta DB Apr 26 07:12:29 192.168.122.209 [54499.935049] End test: cache.test_cache.TestQueryparamsAndRedirectH2.test_query_param_different_key Apr 26 07:12:29 192.168.122.209 [54499.946248] Start test: cache.test_cache.TestQueryparamsAndRedirectH2.test_query_param_different_value Apr 26 07:12:30 192.168.122.209 [54501.007121] [tdb] Start Tempesta DB Apr 26 07:12:30 192.168.122.209 [54501.142041] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:12:32 192.168.122.209 [54502.560019] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54502.560019] Maybe that's fine, but it's worth checking the [54502.560019] config - if there is no relations between the [54502.560019] names, then host name confusion attack is possible. Apr 26 07:12:32 192.168.122.209 [54502.646791] [tempesta fw] Configuration processing is completed. Apr 26 07:12:32 192.168.122.209 [54502.697291] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:12:32 192.168.122.209 [54503.112397] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:12:32 192.168.122.209 [54503.138384] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:12:32 192.168.122.209 [54503.165353] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:12:32 192.168.122.209 [54503.214778] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:12:32 192.168.122.209 [54503.216520] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:12:32 192.168.122.209 [54503.258728] [tempesta fw] Tempesta FW is ready Apr 26 07:12:33 192.168.122.209 [54503.914400] [tdb] Close table 'client0.tdb' Apr 26 07:12:33 192.168.122.209 [54504.100536] [tdb] Close table 'sessions0.tdb' Apr 26 07:12:36 192.168.122.209 [54507.273164] [tdb] Close table 'cache0.tdb' Apr 26 07:12:37 192.168.122.209 [54507.507586] [tdb] Close table 'filter0.tdb' Apr 26 07:12:37 192.168.122.209 [54507.508005] [tempesta fw] modules are stopped Apr 26 07:12:37 192.168.122.209 [54507.699482] [tempesta fw] exiting... Apr 26 07:12:37 192.168.122.209 [54507.820102] [tdb] Shutdown Tempesta DB Apr 26 07:12:37 192.168.122.209 [54508.034840] End test: cache.test_cache.TestQueryparamsAndRedirectH2.test_query_param_different_value Apr 26 07:12:37 192.168.122.209 [54508.058453] Start test: cache.test_cache.TestQueryparamsAndRedirectH2.test_query_param_same_params Apr 26 07:12:38 192.168.122.209 [54509.162852] [tdb] Start Tempesta DB Apr 26 07:12:38 192.168.122.209 [54509.282928] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:12:40 192.168.122.209 [54510.648126] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54510.648126] Maybe that's fine, but it's worth checking the [54510.648126] config - if there is no relations between the [54510.648126] names, then host name confusion attack is possible. Apr 26 07:12:40 192.168.122.209 [54510.746894] [tempesta fw] Configuration processing is completed. Apr 26 07:12:40 192.168.122.209 [54510.799267] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:12:40 192.168.122.209 [54511.232989] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:12:40 192.168.122.209 [54511.258955] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:12:40 192.168.122.209 [54511.284934] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:12:40 192.168.122.209 [54511.330920] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:12:40 192.168.122.209 [54511.332306] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:12:40 192.168.122.209 [54511.378840] [tempesta fw] Tempesta FW is ready Apr 26 07:12:41 192.168.122.209 [54512.038868] [tdb] Close table 'client0.tdb' Apr 26 07:12:41 192.168.122.209 [54512.228814] [tdb] Close table 'sessions0.tdb' Apr 26 07:12:44 192.168.122.209 [54515.422291] [tdb] Close table 'cache0.tdb' Apr 26 07:12:45 192.168.122.209 [54515.689115] [tdb] Close table 'filter0.tdb' Apr 26 07:12:45 192.168.122.209 [54515.689581] [tempesta fw] modules are stopped Apr 26 07:12:45 192.168.122.209 [54515.881371] [tempesta fw] exiting... Apr 26 07:12:45 192.168.122.209 [54515.986269] [tdb] Shutdown Tempesta DB Apr 26 07:12:45 192.168.122.209 [54516.219324] End test: cache.test_cache.TestQueryparamsAndRedirectH2.test_query_param_same_params Apr 26 07:12:45 192.168.122.209 [54516.228911] Start test: cache.test_cache.TestQueryparamsAndRedirectH2.test_query_param_with_new_param Apr 26 07:12:46 192.168.122.209 [54517.228141] [tdb] Start Tempesta DB Apr 26 07:12:46 192.168.122.209 [54517.377020] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:12:48 192.168.122.209 [54518.792238] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54518.792238] Maybe that's fine, but it's worth checking the [54518.792238] config - if there is no relations between the [54518.792238] names, then host name confusion attack is possible. Apr 26 07:12:48 192.168.122.209 [54518.874995] [tempesta fw] Configuration processing is completed. Apr 26 07:12:48 192.168.122.209 [54518.926805] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:12:48 192.168.122.209 [54519.363212] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:12:48 192.168.122.209 [54519.390735] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:12:48 192.168.122.209 [54519.418815] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:12:48 192.168.122.209 [54519.470997] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:12:48 192.168.122.209 [54519.472722] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:12:49 192.168.122.209 [54519.522976] [tempesta fw] Tempesta FW is ready Apr 26 07:12:49 192.168.122.209 [54520.204906] [tdb] Close table 'client0.tdb' Apr 26 07:12:49 192.168.122.209 [54520.394991] [tdb] Close table 'sessions0.tdb' Apr 26 07:12:53 192.168.122.209 [54523.560381] [tdb] Close table 'cache0.tdb' Apr 26 07:12:53 192.168.122.209 [54523.811521] [tdb] Close table 'filter0.tdb' Apr 26 07:12:53 192.168.122.209 [54523.811966] [tempesta fw] modules are stopped Apr 26 07:12:53 192.168.122.209 [54523.995242] [tempesta fw] exiting... Apr 26 07:12:53 192.168.122.209 [54524.093322] [tdb] Shutdown Tempesta DB Apr 26 07:12:53 192.168.122.209 [54524.312002] End test: cache.test_cache.TestQueryparamsAndRedirectH2.test_query_param_with_new_param Apr 26 07:12:53 192.168.122.209 [54524.330462] Start test: cache.test_cache.TestQueryparamsAndRedirectH2.test_redirect_300_multiple_choices Apr 26 07:12:54 192.168.122.209 [54525.404881] [tdb] Start Tempesta DB Apr 26 07:12:55 192.168.122.209 [54525.537996] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:12:56 192.168.122.209 [54526.920443] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54526.920443] Maybe that's fine, but it's worth checking the [54526.920443] config - if there is no relations between the [54526.920443] names, then host name confusion attack is possible. Apr 26 07:12:56 192.168.122.209 [54527.007048] [tempesta fw] Configuration processing is completed. Apr 26 07:12:56 192.168.122.209 [54527.059217] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:12:57 192.168.122.209 [54527.516966] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:12:57 192.168.122.209 [54527.558345] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:12:57 192.168.122.209 [54527.589746] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:12:57 192.168.122.209 [54527.635045] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:12:57 192.168.122.209 [54527.636829] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:12:57 192.168.122.209 [54527.683042] [tempesta fw] Tempesta FW is ready Apr 26 07:12:57 192.168.122.209 [54528.363626] [tdb] Close table 'client0.tdb' Apr 26 07:12:58 192.168.122.209 [54528.557973] [tdb] Close table 'sessions0.tdb' Apr 26 07:13:01 192.168.122.209 [54531.888115] [tdb] Close table 'cache0.tdb' Apr 26 07:13:01 192.168.122.209 [54532.129406] [tdb] Close table 'filter0.tdb' Apr 26 07:13:01 192.168.122.209 [54532.129871] [tempesta fw] modules are stopped Apr 26 07:13:01 192.168.122.209 [54532.317778] [tempesta fw] exiting... Apr 26 07:13:01 192.168.122.209 [54532.448239] [tdb] Shutdown Tempesta DB Apr 26 07:13:02 192.168.122.209 [54532.658133] End test: cache.test_cache.TestQueryparamsAndRedirectH2.test_redirect_300_multiple_choices Apr 26 07:13:02 192.168.122.209 [54532.673879] Start test: cache.test_cache.TestQueryparamsAndRedirectH2.test_redirect_301_moved_permanently Apr 26 07:13:03 192.168.122.209 [54533.779398] [tdb] Start Tempesta DB Apr 26 07:13:03 192.168.122.209 [54533.938407] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:13:04 192.168.122.209 [54535.328477] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54535.328477] Maybe that's fine, but it's worth checking the [54535.328477] config - if there is no relations between the [54535.328477] names, then host name confusion attack is possible. Apr 26 07:13:04 192.168.122.209 [54535.411201] [tempesta fw] Configuration processing is completed. Apr 26 07:13:04 192.168.122.209 [54535.469874] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:13:05 192.168.122.209 [54535.973263] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:13:05 192.168.122.209 [54536.003361] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:13:05 192.168.122.209 [54536.033078] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:13:05 192.168.122.209 [54536.083190] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:13:05 192.168.122.209 [54536.084780] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:13:05 192.168.122.209 [54536.131138] [tempesta fw] Tempesta FW is ready Apr 26 07:13:06 192.168.122.209 [54536.787390] [tdb] Close table 'client0.tdb' Apr 26 07:13:06 192.168.122.209 [54536.978802] [tdb] Close table 'sessions0.tdb' Apr 26 07:13:09 192.168.122.209 [54540.274154] [tdb] Close table 'cache0.tdb' Apr 26 07:13:10 192.168.122.209 [54540.504657] [tdb] Close table 'filter0.tdb' Apr 26 07:13:10 192.168.122.209 [54540.505087] [tempesta fw] modules are stopped Apr 26 07:13:10 192.168.122.209 [54540.695325] [tempesta fw] exiting... Apr 26 07:13:10 192.168.122.209 [54540.825030] [tdb] Shutdown Tempesta DB Apr 26 07:13:10 192.168.122.209 [54541.047315] End test: cache.test_cache.TestQueryparamsAndRedirectH2.test_redirect_301_moved_permanently Apr 26 07:13:10 192.168.122.209 [54541.068035] Start test: cache.test_cache.TestQueryparamsAndRedirectH2.test_redirect_302_found Apr 26 07:13:11 192.168.122.209 [54542.152378] [tdb] Start Tempesta DB Apr 26 07:13:11 192.168.122.209 [54542.293749] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:13:13 192.168.122.209 [54543.784577] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54543.784577] Maybe that's fine, but it's worth checking the [54543.784577] config - if there is no relations between the [54543.784577] names, then host name confusion attack is possible. Apr 26 07:13:13 192.168.122.209 [54543.867323] [tempesta fw] Configuration processing is completed. Apr 26 07:13:13 192.168.122.209 [54543.924814] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:13:13 192.168.122.209 [54544.365563] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:13:13 192.168.122.209 [54544.395444] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:13:13 192.168.122.209 [54544.425897] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:13:13 192.168.122.209 [54544.479340] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:13:13 192.168.122.209 [54544.481037] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:13:14 192.168.122.209 [54544.527285] [tempesta fw] Tempesta FW is ready Apr 26 07:13:14 192.168.122.209 [54545.191619] [tdb] Close table 'client0.tdb' Apr 26 07:13:14 192.168.122.209 [54545.413062] [tdb] Close table 'sessions0.tdb' Apr 26 07:13:18 192.168.122.209 [54548.615022] [tdb] Close table 'cache0.tdb' Apr 26 07:13:18 192.168.122.209 [54548.866751] [tdb] Close table 'filter0.tdb' Apr 26 07:13:18 192.168.122.209 [54548.867228] [tempesta fw] modules are stopped Apr 26 07:13:18 192.168.122.209 [54549.048084] [tempesta fw] exiting... Apr 26 07:13:18 192.168.122.209 [54549.173776] [tdb] Shutdown Tempesta DB Apr 26 07:13:18 192.168.122.209 [54549.390708] End test: cache.test_cache.TestQueryparamsAndRedirectH2.test_redirect_302_found Apr 26 07:13:18 192.168.122.209 [54549.419523] Start test: cache.test_cache.TestQueryparamsAndRedirectH2.test_redirect_303_see_other Apr 26 07:13:19 192.168.122.209 [54550.489811] [tdb] Start Tempesta DB Apr 26 07:13:20 192.168.122.209 [54550.624943] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:13:21 192.168.122.209 [54552.032651] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54552.032651] Maybe that's fine, but it's worth checking the [54552.032651] config - if there is no relations between the [54552.032651] names, then host name confusion attack is possible. Apr 26 07:13:21 192.168.122.209 [54552.115851] [tempesta fw] Configuration processing is completed. Apr 26 07:13:21 192.168.122.209 [54552.166394] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:13:22 192.168.122.209 [54552.671970] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:13:22 192.168.122.209 [54552.706233] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:13:22 192.168.122.209 [54552.743150] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:13:22 192.168.122.209 [54552.823425] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:13:22 192.168.122.209 [54552.825175] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:13:22 192.168.122.209 [54552.863362] [tempesta fw] Tempesta FW is ready Apr 26 07:13:23 192.168.122.209 [54553.543365] [tdb] Close table 'client0.tdb' Apr 26 07:13:23 192.168.122.209 [54553.719598] [tdb] Close table 'sessions0.tdb' Apr 26 07:13:26 192.168.122.209 [54557.045358] [tdb] Close table 'cache0.tdb' Apr 26 07:13:26 192.168.122.209 [54557.303054] [tdb] Close table 'filter0.tdb' Apr 26 07:13:26 192.168.122.209 [54557.303501] [tempesta fw] modules are stopped Apr 26 07:13:27 192.168.122.209 [54557.497127] [tempesta fw] exiting... Apr 26 07:13:27 192.168.122.209 [54557.585887] [tdb] Shutdown Tempesta DB Apr 26 07:13:27 192.168.122.209 [54557.817709] End test: cache.test_cache.TestQueryparamsAndRedirectH2.test_redirect_303_see_other Apr 26 07:13:27 192.168.122.209 [54557.838106] Start test: cache.test_cache.TestQueryparamsAndRedirectH2.test_redirect_304_not_modified Apr 26 07:13:28 192.168.122.209 [54558.926975] [tdb] Start Tempesta DB Apr 26 07:13:28 192.168.122.209 [54559.080863] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:13:30 192.168.122.209 [54560.528778] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54560.528778] Maybe that's fine, but it's worth checking the [54560.528778] config - if there is no relations between the [54560.528778] names, then host name confusion attack is possible. Apr 26 07:13:30 192.168.122.209 [54560.611530] [tempesta fw] Configuration processing is completed. Apr 26 07:13:30 192.168.122.209 [54560.670702] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:13:30 192.168.122.209 [54561.104149] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:13:30 192.168.122.209 [54561.132261] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:13:30 192.168.122.209 [54561.166777] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:13:30 192.168.122.209 [54561.219529] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:13:30 192.168.122.209 [54561.221292] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:13:30 192.168.122.209 [54561.259467] [tempesta fw] Tempesta FW is ready Apr 26 07:13:31 192.168.122.209 [54561.934671] [tdb] Close table 'client0.tdb' Apr 26 07:13:31 192.168.122.209 [54562.132488] [tdb] Close table 'sessions0.tdb' Apr 26 07:13:34 192.168.122.209 [54565.357851] [tdb] Close table 'cache0.tdb' Apr 26 07:13:35 192.168.122.209 [54565.605219] [tdb] Close table 'filter0.tdb' Apr 26 07:13:35 192.168.122.209 [54565.605670] [tempesta fw] modules are stopped Apr 26 07:13:35 192.168.122.209 [54565.824182] [tempesta fw] exiting... Apr 26 07:13:35 192.168.122.209 [54565.956872] [tdb] Shutdown Tempesta DB Apr 26 07:13:35 192.168.122.209 [54566.167454] End test: cache.test_cache.TestQueryparamsAndRedirectH2.test_redirect_304_not_modified Apr 26 07:13:35 192.168.122.209 [54566.195446] Start test: cache.test_cache.TestQueryparamsAndRedirectH2.test_redirect_305_user_proxy Apr 26 07:13:36 192.168.122.209 [54567.218340] [tdb] Start Tempesta DB Apr 26 07:13:36 192.168.122.209 [54567.367771] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:13:38 192.168.122.209 [54568.736904] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54568.736904] Maybe that's fine, but it's worth checking the [54568.736904] config - if there is no relations between the [54568.736904] names, then host name confusion attack is possible. Apr 26 07:13:38 192.168.122.209 [54568.831651] [tempesta fw] Configuration processing is completed. Apr 26 07:13:38 192.168.122.209 [54568.882050] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:13:38 192.168.122.209 [54569.303359] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:13:38 192.168.122.209 [54569.331139] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:13:38 192.168.122.209 [54569.358154] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:13:38 192.168.122.209 [54569.407598] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:13:38 192.168.122.209 [54569.409091] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:13:38 192.168.122.209 [54569.459564] [tempesta fw] Tempesta FW is ready Apr 26 07:13:39 192.168.122.209 [54570.166298] [tdb] Close table 'client0.tdb' Apr 26 07:13:39 192.168.122.209 [54570.364578] [tdb] Close table 'sessions0.tdb' Apr 26 07:13:43 192.168.122.209 [54573.565160] [tdb] Close table 'cache0.tdb' Apr 26 07:13:43 192.168.122.209 [54573.800036] [tdb] Close table 'filter0.tdb' Apr 26 07:13:43 192.168.122.209 [54573.800489] [tempesta fw] modules are stopped Apr 26 07:13:43 192.168.122.209 [54573.995570] [tempesta fw] exiting... Apr 26 07:13:43 192.168.122.209 [54574.125970] [tdb] Shutdown Tempesta DB Apr 26 07:13:43 192.168.122.209 [54574.341758] End test: cache.test_cache.TestQueryparamsAndRedirectH2.test_redirect_305_user_proxy Apr 26 07:13:43 192.168.122.209 [54574.365269] Start test: cache.test_cache.TestQueryparamsAndRedirectH2.test_redirect_307_temporary_redirect Apr 26 07:13:44 192.168.122.209 [54575.408478] [tdb] Start Tempesta DB Apr 26 07:13:45 192.168.122.209 [54575.553498] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:13:46 192.168.122.209 [54576.928972] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54576.928972] Maybe that's fine, but it's worth checking the [54576.928972] config - if there is no relations between the [54576.928972] names, then host name confusion attack is possible. Apr 26 07:13:46 192.168.122.209 [54577.019995] [tempesta fw] Configuration processing is completed. Apr 26 07:13:46 192.168.122.209 [54577.070716] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:13:47 192.168.122.209 [54577.502583] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:13:47 192.168.122.209 [54577.528475] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:13:47 192.168.122.209 [54577.554369] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:13:47 192.168.122.209 [54577.599730] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:13:47 192.168.122.209 [54577.601450] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:13:47 192.168.122.209 [54577.651745] [tempesta fw] Tempesta FW is ready Apr 26 07:13:47 192.168.122.209 [54578.314529] [tdb] Close table 'client0.tdb' Apr 26 07:13:48 192.168.122.209 [54578.503511] [tdb] Close table 'sessions0.tdb' Apr 26 07:13:51 192.168.122.209 [54581.700093] [tdb] Close table 'cache0.tdb' Apr 26 07:13:51 192.168.122.209 [54581.974161] [tdb] Close table 'filter0.tdb' Apr 26 07:13:51 192.168.122.209 [54581.974597] [tempesta fw] modules are stopped Apr 26 07:13:51 192.168.122.209 [54582.195784] [tempesta fw] exiting... Apr 26 07:13:51 192.168.122.209 [54582.314079] [tdb] Shutdown Tempesta DB Apr 26 07:13:52 192.168.122.209 [54582.530971] End test: cache.test_cache.TestQueryparamsAndRedirectH2.test_redirect_307_temporary_redirect Apr 26 07:13:52 192.168.122.209 [54582.541795] Start test: cache.test_cache.TestQueryparamsAndRedirectH2.test_redirect_308_permanent_redirect Apr 26 07:13:53 192.168.122.209 [54583.633129] [tdb] Start Tempesta DB Apr 26 07:13:53 192.168.122.209 [54583.773187] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:13:54 192.168.122.209 [54585.193064] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54585.193064] Maybe that's fine, but it's worth checking the [54585.193064] config - if there is no relations between the [54585.193064] names, then host name confusion attack is possible. Apr 26 07:13:54 192.168.122.209 [54585.283860] [tempesta fw] Configuration processing is completed. Apr 26 07:13:54 192.168.122.209 [54585.338162] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:13:55 192.168.122.209 [54585.768063] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:13:55 192.168.122.209 [54585.795377] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:13:55 192.168.122.209 [54585.822619] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:13:55 192.168.122.209 [54585.879846] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:13:55 192.168.122.209 [54585.881635] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:13:55 192.168.122.209 [54585.919763] [tempesta fw] Tempesta FW is ready Apr 26 07:13:56 192.168.122.209 [54586.644252] [tdb] Close table 'client0.tdb' Apr 26 07:13:56 192.168.122.209 [54586.840512] [tdb] Close table 'sessions0.tdb' Apr 26 07:13:59 192.168.122.209 [54589.993199] [tdb] Close table 'cache0.tdb' Apr 26 07:13:59 192.168.122.209 [54590.235650] [tdb] Close table 'filter0.tdb' Apr 26 07:13:59 192.168.122.209 [54590.236112] [tempesta fw] modules are stopped Apr 26 07:13:59 192.168.122.209 [54590.428512] [tempesta fw] exiting... Apr 26 07:14:00 192.168.122.209 [54590.553358] [tdb] Shutdown Tempesta DB Apr 26 07:14:00 192.168.122.209 [54590.775206] End test: cache.test_cache.TestQueryparamsAndRedirectH2.test_redirect_308_permanent_redirect Apr 26 07:14:00 192.168.122.209 [54590.794870] Start test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_query_param_different_key Apr 26 07:14:01 192.168.122.209 [54591.911872] [tdb] Start Tempesta DB Apr 26 07:14:01 192.168.122.209 [54592.057873] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:14:02 192.168.122.209 [54593.421170] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54593.421170] Maybe that's fine, but it's worth checking the [54593.421170] config - if there is no relations between the [54593.421170] names, then host name confusion attack is possible. Apr 26 07:14:03 192.168.122.209 [54593.507986] [tempesta fw] Configuration processing is completed. Apr 26 07:14:03 192.168.122.209 [54593.558189] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:14:03 192.168.122.209 [54593.976166] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:14:03 192.168.122.209 [54594.002887] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:14:03 192.168.122.209 [54594.030200] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:14:03 192.168.122.209 [54594.075955] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:14:03 192.168.122.209 [54594.077737] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:14:03 192.168.122.209 [54594.123878] [tempesta fw] Tempesta FW is ready Apr 26 07:14:04 192.168.122.209 [54594.736175] [tdb] Close table 'client0.tdb' Apr 26 07:14:04 192.168.122.209 [54594.926955] [tdb] Close table 'sessions0.tdb' Apr 26 07:14:07 192.168.122.209 [54598.156768] [tdb] Close table 'cache0.tdb' Apr 26 07:14:07 192.168.122.209 [54598.397805] [tdb] Close table 'filter0.tdb' Apr 26 07:14:07 192.168.122.209 [54598.398239] [tempesta fw] modules are stopped Apr 26 07:14:08 192.168.122.209 [54598.617758] [tempesta fw] exiting... Apr 26 07:14:08 192.168.122.209 [54598.746564] [tdb] Shutdown Tempesta DB Apr 26 07:14:08 192.168.122.209 [54598.955413] End test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_query_param_different_key Apr 26 07:14:08 192.168.122.209 [54598.970395] Start test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_query_param_different_value Apr 26 07:14:09 192.168.122.209 [54600.036033] [tdb] Start Tempesta DB Apr 26 07:14:09 192.168.122.209 [54600.179324] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:14:11 192.168.122.209 [54601.637283] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54601.637283] Maybe that's fine, but it's worth checking the [54601.637283] config - if there is no relations between the [54601.637283] names, then host name confusion attack is possible. Apr 26 07:14:11 192.168.122.209 [54601.724042] [tempesta fw] Configuration processing is completed. Apr 26 07:14:11 192.168.122.209 [54601.777124] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:14:11 192.168.122.209 [54602.207152] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:14:11 192.168.122.209 [54602.234450] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:14:11 192.168.122.209 [54602.261325] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:14:11 192.168.122.209 [54602.303986] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:14:11 192.168.122.209 [54602.305092] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:14:11 192.168.122.209 [54602.343983] [tempesta fw] Tempesta FW is ready Apr 26 07:14:12 192.168.122.209 [54603.014181] [tdb] Close table 'client0.tdb' Apr 26 07:14:12 192.168.122.209 [54603.206293] [tdb] Close table 'sessions0.tdb' Apr 26 07:14:15 192.168.122.209 [54606.489779] [tdb] Close table 'cache0.tdb' Apr 26 07:14:16 192.168.122.209 [54606.723328] [tdb] Close table 'filter0.tdb' Apr 26 07:14:16 192.168.122.209 [54606.723781] [tempesta fw] modules are stopped Apr 26 07:14:16 192.168.122.209 [54606.947109] [tempesta fw] exiting... Apr 26 07:14:16 192.168.122.209 [54607.041921] [tdb] Shutdown Tempesta DB Apr 26 07:14:16 192.168.122.209 [54607.291211] End test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_query_param_different_value Apr 26 07:14:16 192.168.122.209 [54607.307461] Start test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_query_param_same_params Apr 26 07:14:17 192.168.122.209 [54608.356784] [tdb] Start Tempesta DB Apr 26 07:14:18 192.168.122.209 [54608.500294] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:14:19 192.168.122.209 [54609.969398] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54609.969398] Maybe that's fine, but it's worth checking the [54609.969398] config - if there is no relations between the [54609.969398] names, then host name confusion attack is possible. Apr 26 07:14:19 192.168.122.209 [54610.052141] [tempesta fw] Configuration processing is completed. Apr 26 07:14:19 192.168.122.209 [54610.106555] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:14:20 192.168.122.209 [54610.533210] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:14:20 192.168.122.209 [54610.559769] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:14:20 192.168.122.209 [54610.586742] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:14:20 192.168.122.209 [54610.644049] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:14:20 192.168.122.209 [54610.644927] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:14:20 192.168.122.209 [54610.684078] [tempesta fw] Tempesta FW is ready Apr 26 07:14:20 192.168.122.209 [54611.269849] [tdb] Close table 'client0.tdb' Apr 26 07:14:20 192.168.122.209 [54611.462082] [tdb] Close table 'sessions0.tdb' Apr 26 07:14:24 192.168.122.209 [54614.705979] [tdb] Close table 'cache0.tdb' Apr 26 07:14:24 192.168.122.209 [54614.934848] [tdb] Close table 'filter0.tdb' Apr 26 07:14:24 192.168.122.209 [54614.935268] [tempesta fw] modules are stopped Apr 26 07:14:24 192.168.122.209 [54615.139627] [tempesta fw] exiting... Apr 26 07:14:24 192.168.122.209 [54615.248165] [tdb] Shutdown Tempesta DB Apr 26 07:14:24 192.168.122.209 [54615.482792] End test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_query_param_same_params Apr 26 07:14:25 192.168.122.209 [54615.498628] Start test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_query_param_with_new_param Apr 26 07:14:26 192.168.122.209 [54616.515952] [tdb] Start Tempesta DB Apr 26 07:14:26 192.168.122.209 [54616.655195] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:14:27 192.168.122.209 [54618.089492] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54618.089492] Maybe that's fine, but it's worth checking the [54618.089492] config - if there is no relations between the [54618.089492] names, then host name confusion attack is possible. Apr 26 07:14:27 192.168.122.209 [54618.176260] [tempesta fw] Configuration processing is completed. Apr 26 07:14:27 192.168.122.209 [54618.226403] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:14:28 192.168.122.209 [54618.649680] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:14:28 192.168.122.209 [54618.676202] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:14:28 192.168.122.209 [54618.701656] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:14:28 192.168.122.209 [54618.748242] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:14:28 192.168.122.209 [54618.749967] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:14:28 192.168.122.209 [54618.788191] [tempesta fw] Tempesta FW is ready Apr 26 07:14:28 192.168.122.209 [54619.435250] [tdb] Close table 'client0.tdb' Apr 26 07:14:29 192.168.122.209 [54619.629755] [tdb] Close table 'sessions0.tdb' Apr 26 07:14:32 192.168.122.209 [54622.866324] [tdb] Close table 'cache0.tdb' Apr 26 07:14:32 192.168.122.209 [54623.101118] [tdb] Close table 'filter0.tdb' Apr 26 07:14:32 192.168.122.209 [54623.101571] [tempesta fw] modules are stopped Apr 26 07:14:32 192.168.122.209 [54623.305166] [tempesta fw] exiting... Apr 26 07:14:32 192.168.122.209 [54623.472374] [tdb] Shutdown Tempesta DB Apr 26 07:14:33 192.168.122.209 [54623.733662] End test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_query_param_with_new_param Apr 26 07:14:33 192.168.122.209 [54623.753619] Start test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_redirect_300_multiple_choices Apr 26 07:14:34 192.168.122.209 [54624.853108] [tdb] Start Tempesta DB Apr 26 07:14:34 192.168.122.209 [54624.992050] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:14:35 192.168.122.209 [54626.405630] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54626.405630] Maybe that's fine, but it's worth checking the [54626.405630] config - if there is no relations between the [54626.405630] names, then host name confusion attack is possible. Apr 26 07:14:36 192.168.122.209 [54626.492370] [tempesta fw] Configuration processing is completed. Apr 26 07:14:36 192.168.122.209 [54626.543181] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:14:36 192.168.122.209 [54626.968526] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:14:36 192.168.122.209 [54626.995861] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:14:36 192.168.122.209 [54627.023747] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:14:36 192.168.122.209 [54627.076335] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:14:36 192.168.122.209 [54627.077828] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:14:36 192.168.122.209 [54627.124289] [tempesta fw] Tempesta FW is ready Apr 26 07:14:37 192.168.122.209 [54627.714825] [tdb] Close table 'client0.tdb' Apr 26 07:14:37 192.168.122.209 [54627.897260] [tdb] Close table 'sessions0.tdb' Apr 26 07:14:40 192.168.122.209 [54631.056780] [tdb] Close table 'cache0.tdb' Apr 26 07:14:40 192.168.122.209 [54631.292424] [tdb] Close table 'filter0.tdb' Apr 26 07:14:40 192.168.122.209 [54631.292875] [tempesta fw] modules are stopped Apr 26 07:14:41 192.168.122.209 [54631.549202] [tempesta fw] exiting... Apr 26 07:14:41 192.168.122.209 [54631.691134] [tdb] Shutdown Tempesta DB Apr 26 07:14:41 192.168.122.209 [54631.924407] End test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_redirect_300_multiple_choices Apr 26 07:14:41 192.168.122.209 [54631.941978] Start test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_redirect_301_moved_permanently Apr 26 07:14:42 192.168.122.209 [54632.976126] [tdb] Start Tempesta DB Apr 26 07:14:42 192.168.122.209 [54633.127082] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:14:44 192.168.122.209 [54634.557698] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54634.557698] Maybe that's fine, but it's worth checking the [54634.557698] config - if there is no relations between the [54634.557698] names, then host name confusion attack is possible. Apr 26 07:14:44 192.168.122.209 [54634.644459] [tempesta fw] Configuration processing is completed. Apr 26 07:14:44 192.168.122.209 [54634.696021] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:14:44 192.168.122.209 [54635.122465] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:14:44 192.168.122.209 [54635.149488] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:14:44 192.168.122.209 [54635.183282] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:14:44 192.168.122.209 [54635.224389] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:14:44 192.168.122.209 [54635.225573] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:14:44 192.168.122.209 [54635.272313] [tempesta fw] Tempesta FW is ready Apr 26 07:14:45 192.168.122.209 [54635.865075] [tdb] Close table 'client0.tdb' Apr 26 07:14:45 192.168.122.209 [54636.062389] [tdb] Close table 'sessions0.tdb' Apr 26 07:14:48 192.168.122.209 [54639.241025] [tdb] Close table 'cache0.tdb' Apr 26 07:14:48 192.168.122.209 [54639.491948] [tdb] Close table 'filter0.tdb' Apr 26 07:14:48 192.168.122.209 [54639.492421] [tempesta fw] modules are stopped Apr 26 07:14:49 192.168.122.209 [54639.718761] [tempesta fw] exiting... Apr 26 07:14:49 192.168.122.209 [54639.858295] [tdb] Shutdown Tempesta DB Apr 26 07:14:49 192.168.122.209 [54640.084725] End test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_redirect_301_moved_permanently Apr 26 07:14:49 192.168.122.209 [54640.098470] Start test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_redirect_302_found Apr 26 07:14:50 192.168.122.209 [54641.189309] [tdb] Start Tempesta DB Apr 26 07:14:50 192.168.122.209 [54641.339816] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:14:52 192.168.122.209 [54642.785879] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54642.785879] Maybe that's fine, but it's worth checking the [54642.785879] config - if there is no relations between the [54642.785879] names, then host name confusion attack is possible. Apr 26 07:14:52 192.168.122.209 [54642.868694] [tempesta fw] Configuration processing is completed. Apr 26 07:14:52 192.168.122.209 [54642.919977] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:14:52 192.168.122.209 [54643.342847] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:14:52 192.168.122.209 [54643.379054] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:14:52 192.168.122.209 [54643.404723] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:14:52 192.168.122.209 [54643.444509] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:14:52 192.168.122.209 [54643.445659] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:14:53 192.168.122.209 [54643.492482] [tempesta fw] Tempesta FW is ready Apr 26 07:14:53 192.168.122.209 [54644.073933] [tdb] Close table 'client0.tdb' Apr 26 07:14:53 192.168.122.209 [54644.262661] [tdb] Close table 'sessions0.tdb' Apr 26 07:14:56 192.168.122.209 [54647.443592] [tdb] Close table 'cache0.tdb' Apr 26 07:14:57 192.168.122.209 [54647.689458] [tdb] Close table 'filter0.tdb' Apr 26 07:14:57 192.168.122.209 [54647.689918] [tempesta fw] modules are stopped Apr 26 07:14:57 192.168.122.209 [54647.886343] [tempesta fw] exiting... Apr 26 07:14:57 192.168.122.209 [54647.980980] [tdb] Shutdown Tempesta DB Apr 26 07:14:57 192.168.122.209 [54648.155091] End test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_redirect_302_found Apr 26 07:14:57 192.168.122.209 [54648.194780] Start test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_redirect_303_see_other Apr 26 07:14:58 192.168.122.209 [54649.124414] [tdb] Start Tempesta DB Apr 26 07:14:58 192.168.122.209 [54649.250866] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:15:00 192.168.122.209 [54650.677941] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54650.677941] Maybe that's fine, but it's worth checking the [54650.677941] config - if there is no relations between the [54650.677941] names, then host name confusion attack is possible. Apr 26 07:15:00 192.168.122.209 [54650.764671] [tempesta fw] Configuration processing is completed. Apr 26 07:15:00 192.168.122.209 [54650.815650] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:15:00 192.168.122.209 [54651.232810] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:15:00 192.168.122.209 [54651.259111] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:15:00 192.168.122.209 [54651.286089] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:15:00 192.168.122.209 [54651.336653] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:15:00 192.168.122.209 [54651.338389] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:15:00 192.168.122.209 [54651.384607] [tempesta fw] Tempesta FW is ready Apr 26 07:15:01 192.168.122.209 [54651.976923] [tdb] Close table 'client0.tdb' Apr 26 07:15:01 192.168.122.209 [54652.199539] [tdb] Close table 'sessions0.tdb' Apr 26 07:15:04 192.168.122.209 [54655.397092] [tdb] Close table 'cache0.tdb' Apr 26 07:15:05 192.168.122.209 [54655.659264] [tdb] Close table 'filter0.tdb' Apr 26 07:15:05 192.168.122.209 [54655.659698] [tempesta fw] modules are stopped Apr 26 07:15:05 192.168.122.209 [54655.881442] [tempesta fw] exiting... Apr 26 07:15:05 192.168.122.209 [54656.007616] [tdb] Shutdown Tempesta DB Apr 26 07:15:05 192.168.122.209 [54656.221079] End test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_redirect_303_see_other Apr 26 07:15:05 192.168.122.209 [54656.239106] Start test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_redirect_304_not_modified Apr 26 07:15:06 192.168.122.209 [54657.203714] [tdb] Start Tempesta DB Apr 26 07:15:06 192.168.122.209 [54657.322145] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:15:08 192.168.122.209 [54658.717980] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54658.717980] Maybe that's fine, but it's worth checking the [54658.717980] config - if there is no relations between the [54658.717980] names, then host name confusion attack is possible. Apr 26 07:15:08 192.168.122.209 [54658.824773] [tempesta fw] Configuration processing is completed. Apr 26 07:15:08 192.168.122.209 [54658.868590] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:15:08 192.168.122.209 [54659.293378] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:15:08 192.168.122.209 [54659.319565] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:15:08 192.168.122.209 [54659.345450] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:15:08 192.168.122.209 [54659.400762] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:15:08 192.168.122.209 [54659.402486] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:15:08 192.168.122.209 [54659.452692] [tempesta fw] Tempesta FW is ready Apr 26 07:15:09 192.168.122.209 [54660.062104] [tdb] Close table 'client0.tdb' Apr 26 07:15:09 192.168.122.209 [54660.242696] [tdb] Close table 'sessions0.tdb' Apr 26 07:15:12 192.168.122.209 [54663.425773] [tdb] Close table 'cache0.tdb' Apr 26 07:15:13 192.168.122.209 [54663.664814] [tdb] Close table 'filter0.tdb' Apr 26 07:15:13 192.168.122.209 [54663.665255] [tempesta fw] modules are stopped Apr 26 07:15:13 192.168.122.209 [54663.862460] [tempesta fw] exiting... Apr 26 07:15:13 192.168.122.209 [54663.970108] [tdb] Shutdown Tempesta DB Apr 26 07:15:13 192.168.122.209 [54664.191066] End test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_redirect_304_not_modified Apr 26 07:15:13 192.168.122.209 [54664.206442] Start test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_redirect_305_user_proxy Apr 26 07:15:14 192.168.122.209 [54665.141509] [tdb] Start Tempesta DB Apr 26 07:15:14 192.168.122.209 [54665.289453] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:15:16 192.168.122.209 [54666.682098] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54666.682098] Maybe that's fine, but it's worth checking the [54666.682098] config - if there is no relations between the [54666.682098] names, then host name confusion attack is possible. Apr 26 07:15:16 192.168.122.209 [54666.764958] [tempesta fw] Configuration processing is completed. Apr 26 07:15:16 192.168.122.209 [54666.823255] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:15:16 192.168.122.209 [54667.244424] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:15:16 192.168.122.209 [54667.271382] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:15:16 192.168.122.209 [54667.298338] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:15:16 192.168.122.209 [54667.344825] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:15:16 192.168.122.209 [54667.346342] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:15:16 192.168.122.209 [54667.396791] [tempesta fw] Tempesta FW is ready Apr 26 07:15:17 192.168.122.209 [54668.010458] [tdb] Close table 'client0.tdb' Apr 26 07:15:17 192.168.122.209 [54668.199175] [tdb] Close table 'sessions0.tdb' Apr 26 07:15:20 192.168.122.209 [54671.438083] [tdb] Close table 'cache0.tdb' Apr 26 07:15:21 192.168.122.209 [54671.689766] [tdb] Close table 'filter0.tdb' Apr 26 07:15:21 192.168.122.209 [54671.690208] [tempesta fw] modules are stopped Apr 26 07:15:21 192.168.122.209 [54671.885477] [tempesta fw] exiting... Apr 26 07:15:21 192.168.122.209 [54672.000967] [tdb] Shutdown Tempesta DB Apr 26 07:15:21 192.168.122.209 [54672.216502] End test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_redirect_305_user_proxy Apr 26 07:15:21 192.168.122.209 [54672.234512] Start test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_redirect_307_temporary_redirect Apr 26 07:15:22 192.168.122.209 [54673.303175] [tdb] Start Tempesta DB Apr 26 07:15:22 192.168.122.209 [54673.447269] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:15:24 192.168.122.209 [54674.910190] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54674.910190] Maybe that's fine, but it's worth checking the [54674.910190] config - if there is no relations between the [54674.910190] names, then host name confusion attack is possible. Apr 26 07:15:24 192.168.122.209 [54674.992972] [tempesta fw] Configuration processing is completed. Apr 26 07:15:24 192.168.122.209 [54675.051778] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:15:25 192.168.122.209 [54675.502616] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:15:25 192.168.122.209 [54675.528316] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:15:25 192.168.122.209 [54675.553880] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:15:25 192.168.122.209 [54675.616954] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:15:25 192.168.122.209 [54675.618714] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:15:25 192.168.122.209 [54675.660893] [tempesta fw] Tempesta FW is ready Apr 26 07:15:25 192.168.122.209 [54676.292141] [tdb] Close table 'client0.tdb' Apr 26 07:15:25 192.168.122.209 [54676.491973] [tdb] Close table 'sessions0.tdb' Apr 26 07:15:29 192.168.122.209 [54679.733053] [tdb] Close table 'cache0.tdb' Apr 26 07:15:29 192.168.122.209 [54680.007027] [tdb] Close table 'filter0.tdb' Apr 26 07:15:29 192.168.122.209 [54680.007469] [tempesta fw] modules are stopped Apr 26 07:15:29 192.168.122.209 [54680.208132] [tempesta fw] exiting... Apr 26 07:15:29 192.168.122.209 [54680.323115] [tdb] Shutdown Tempesta DB Apr 26 07:15:30 192.168.122.209 [54680.527240] End test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_redirect_307_temporary_redirect Apr 26 07:15:30 192.168.122.209 [54680.541187] Start test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_redirect_308_permanent_redirect Apr 26 07:15:31 192.168.122.209 [54681.500367] [tdb] Start Tempesta DB Apr 26 07:15:31 192.168.122.209 [54681.654795] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:15:32 192.168.122.209 [54683.090317] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [54683.090317] Maybe that's fine, but it's worth checking the [54683.090317] config - if there is no relations between the [54683.090317] names, then host name confusion attack is possible. Apr 26 07:15:32 192.168.122.209 [54683.185094] [tempesta fw] Configuration processing is completed. Apr 26 07:15:32 192.168.122.209 [54683.238376] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:15:33 192.168.122.209 [54683.662539] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:15:33 192.168.122.209 [54683.689106] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:15:33 192.168.122.209 [54683.716703] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:15:33 192.168.122.209 [54683.765004] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:15:33 192.168.122.209 [54683.766441] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:15:33 192.168.122.209 [54683.805013] [tempesta fw] Tempesta FW is ready Apr 26 07:15:33 192.168.122.209 [54684.462411] [tdb] Close table 'client0.tdb' Apr 26 07:15:34 192.168.122.209 [54684.650923] [tdb] Close table 'sessions0.tdb' Apr 26 07:15:37 192.168.122.209 [54687.851801] [tdb] Close table 'cache0.tdb' Apr 26 07:15:37 192.168.122.209 [54688.103798] [tdb] Close table 'filter0.tdb' Apr 26 07:15:37 192.168.122.209 [54688.104237] [tempesta fw] modules are stopped Apr 26 07:15:37 192.168.122.209 [54688.269561] [tempesta fw] exiting... Apr 26 07:15:37 192.168.122.209 [54688.403694] [tdb] Shutdown Tempesta DB Apr 26 07:15:38 192.168.122.209 [54688.646347] End test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_redirect_308_permanent_redirect Apr 26 07:15:38 192.168.122.209 [54688.664111] Start test: cache.test_cache_control.CCArgBothNoCacheCached.test Apr 26 07:15:39 192.168.122.209 [54689.684724] [tdb] Start Tempesta DB Apr 26 07:15:39 192.168.122.209 [54689.824195] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:15:40 192.168.122.209 [54691.325254] [tempesta fw] Configuration processing is completed. Apr 26 07:15:40 192.168.122.209 [54691.386025] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:15:41 192.168.122.209 [54691.855639] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:15:41 192.168.122.209 [54691.892680] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:15:41 192.168.122.209 [54691.917948] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:15:41 192.168.122.209 [54691.969164] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:15:41 192.168.122.209 [54692.013100] [tempesta fw] Tempesta FW is ready Apr 26 07:15:42 192.168.122.209 [54692.627508] [tdb] Close table 'client0.tdb' Apr 26 07:15:42 192.168.122.209 [54692.818650] [tdb] Close table 'sessions0.tdb' Apr 26 07:15:45 192.168.122.209 [54696.034160] [tdb] Close table 'cache0.tdb' Apr 26 07:15:45 192.168.122.209 [54696.249181] [tdb] Close table 'filter0.tdb' Apr 26 07:15:45 192.168.122.209 [54696.249603] [tempesta fw] modules are stopped Apr 26 07:15:45 192.168.122.209 [54696.470825] [tempesta fw] exiting... Apr 26 07:15:46 192.168.122.209 [54696.606209] [tdb] Shutdown Tempesta DB Apr 26 07:15:46 192.168.122.209 [54696.803891] End test: cache.test_cache_control.CCArgBothNoCacheCached.test Apr 26 07:15:46 192.168.122.209 [54696.826226] Start test: cache.test_cache_control.CCArgNoCacheBypass.test Apr 26 07:15:47 192.168.122.209 [54697.895633] [tdb] Start Tempesta DB Apr 26 07:15:47 192.168.122.209 [54698.035606] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:15:49 192.168.122.209 [54699.505201] [tempesta fw] Configuration processing is completed. Apr 26 07:15:49 192.168.122.209 [54699.559915] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:15:49 192.168.122.209 [54700.023843] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:15:49 192.168.122.209 [54700.052735] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:15:49 192.168.122.209 [54700.081365] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:15:49 192.168.122.209 [54700.125223] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:15:49 192.168.122.209 [54700.165207] [tempesta fw] Tempesta FW is ready Apr 26 07:15:50 192.168.122.209 [54700.811481] [tdb] Close table 'client0.tdb' Apr 26 07:15:50 192.168.122.209 [54700.995944] [tdb] Close table 'sessions0.tdb' Apr 26 07:15:53 192.168.122.209 [54704.181879] [tdb] Close table 'cache0.tdb' Apr 26 07:15:53 192.168.122.209 [54704.421799] [tdb] Close table 'filter0.tdb' Apr 26 07:15:53 192.168.122.209 [54704.422232] [tempesta fw] modules are stopped Apr 26 07:15:54 192.168.122.209 [54704.666966] [tempesta fw] exiting... Apr 26 07:15:54 192.168.122.209 [54704.792199] [tdb] Shutdown Tempesta DB Apr 26 07:15:54 192.168.122.209 [54705.011867] End test: cache.test_cache_control.CCArgNoCacheBypass.test Apr 26 07:15:54 192.168.122.209 [54705.030288] Start test: cache.test_cache_control.CCArgNoCacheCached.test Apr 26 07:15:55 192.168.122.209 [54706.127220] [tdb] Start Tempesta DB Apr 26 07:15:55 192.168.122.209 [54706.267547] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:15:57 192.168.122.209 [54707.757427] [tempesta fw] Configuration processing is completed. Apr 26 07:15:57 192.168.122.209 [54707.818110] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:15:57 192.168.122.209 [54708.241014] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:15:57 192.168.122.209 [54708.268261] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:15:57 192.168.122.209 [54708.295940] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:15:57 192.168.122.209 [54708.341261] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:15:57 192.168.122.209 [54708.381322] [tempesta fw] Tempesta FW is ready Apr 26 07:15:58 192.168.122.209 [54709.004469] [tdb] Close table 'client0.tdb' Apr 26 07:15:58 192.168.122.209 [54709.191182] [tdb] Close table 'sessions0.tdb' Apr 26 07:16:01 192.168.122.209 [54712.388627] [tdb] Close table 'cache0.tdb' Apr 26 07:16:02 192.168.122.209 [54712.623151] [tdb] Close table 'filter0.tdb' Apr 26 07:16:02 192.168.122.209 [54712.623597] [tempesta fw] modules are stopped Apr 26 07:16:02 192.168.122.209 [54712.825923] [tempesta fw] exiting... Apr 26 07:16:02 192.168.122.209 [54712.950731] [tdb] Shutdown Tempesta DB Apr 26 07:16:02 192.168.122.209 [54713.152301] End test: cache.test_cache_control.CCArgNoCacheCached.test Apr 26 07:16:02 192.168.122.209 [54713.176865] Start test: cache.test_cache_control.CCArgNoCacheCached2.test Apr 26 07:16:03 192.168.122.209 [54714.247234] [tdb] Start Tempesta DB Apr 26 07:16:03 192.168.122.209 [54714.402073] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:16:05 192.168.122.209 [54715.833500] [tempesta fw] Configuration processing is completed. Apr 26 07:16:05 192.168.122.209 [54715.887938] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:16:05 192.168.122.209 [54716.318992] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:16:05 192.168.122.209 [54716.344976] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:16:05 192.168.122.209 [54716.370929] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:16:05 192.168.122.209 [54716.421462] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:16:05 192.168.122.209 [54716.465406] [tempesta fw] Tempesta FW is ready Apr 26 07:16:06 192.168.122.209 [54717.032496] [tdb] Close table 'client0.tdb' Apr 26 07:16:06 192.168.122.209 [54717.232801] [tdb] Close table 'sessions0.tdb' Apr 26 07:16:09 192.168.122.209 [54720.449070] [tdb] Close table 'cache0.tdb' Apr 26 07:16:10 192.168.122.209 [54720.693926] [tdb] Close table 'filter0.tdb' Apr 26 07:16:10 192.168.122.209 [54720.694362] [tempesta fw] modules are stopped Apr 26 07:16:10 192.168.122.209 [54720.893800] [tempesta fw] exiting... Apr 26 07:16:10 192.168.122.209 [54721.021559] [tdb] Shutdown Tempesta DB Apr 26 07:16:10 192.168.122.209 [54721.266470] End test: cache.test_cache_control.CCArgNoCacheCached2.test Apr 26 07:16:10 192.168.122.209 [54721.280065] Start test: cache.test_cache_control.CCArgNoCacheCached3.test Apr 26 07:16:11 192.168.122.209 [54722.290663] [tdb] Start Tempesta DB Apr 26 07:16:11 192.168.122.209 [54722.425124] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:16:13 192.168.122.209 [54723.897600] [tempesta fw] Configuration processing is completed. Apr 26 07:16:13 192.168.122.209 [54723.956310] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:16:13 192.168.122.209 [54724.374048] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:16:13 192.168.122.209 [54724.400610] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:16:13 192.168.122.209 [54724.427218] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:16:13 192.168.122.209 [54724.477540] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:16:14 192.168.122.209 [54724.521510] [tempesta fw] Tempesta FW is ready Apr 26 07:16:14 192.168.122.209 [54725.136639] [tdb] Close table 'client0.tdb' Apr 26 07:16:14 192.168.122.209 [54725.322241] [tdb] Close table 'sessions0.tdb' Apr 26 07:16:18 192.168.122.209 [54728.529084] [tdb] Close table 'cache0.tdb' Apr 26 07:16:18 192.168.122.209 [54728.776337] [tdb] Close table 'filter0.tdb' Apr 26 07:16:18 192.168.122.209 [54728.776785] [tempesta fw] modules are stopped Apr 26 07:16:18 192.168.122.209 [54728.962447] [tempesta fw] exiting... Apr 26 07:16:18 192.168.122.209 [54729.082564] [tdb] Shutdown Tempesta DB Apr 26 07:16:18 192.168.122.209 [54729.307711] End test: cache.test_cache_control.CCArgNoCacheCached3.test Apr 26 07:16:18 192.168.122.209 [54729.318660] Start test: cache.test_cache_control.CCArgPrivateBypass.test Apr 26 07:16:19 192.168.122.209 [54730.363044] [tdb] Start Tempesta DB Apr 26 07:16:20 192.168.122.209 [54730.497380] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:16:21 192.168.122.209 [54731.909721] [tempesta fw] Configuration processing is completed. Apr 26 07:16:21 192.168.122.209 [54731.971928] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:16:21 192.168.122.209 [54732.393559] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:16:21 192.168.122.209 [54732.420730] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:16:21 192.168.122.209 [54732.447074] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:16:22 192.168.122.209 [54732.493675] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:16:22 192.168.122.209 [54732.533637] [tempesta fw] Tempesta FW is ready Apr 26 07:16:22 192.168.122.209 [54733.172459] [tdb] Close table 'client0.tdb' Apr 26 07:16:22 192.168.122.209 [54733.363392] [tdb] Close table 'sessions0.tdb' Apr 26 07:16:26 192.168.122.209 [54736.514757] [tdb] Close table 'cache0.tdb' Apr 26 07:16:26 192.168.122.209 [54736.780459] [tdb] Close table 'filter0.tdb' Apr 26 07:16:26 192.168.122.209 [54736.780885] [tempesta fw] modules are stopped Apr 26 07:16:26 192.168.122.209 [54736.974303] [tempesta fw] exiting... Apr 26 07:16:26 192.168.122.209 [54737.097449] [tdb] Shutdown Tempesta DB Apr 26 07:16:26 192.168.122.209 [54737.321586] End test: cache.test_cache_control.CCArgPrivateBypass.test Apr 26 07:16:26 192.168.122.209 [54737.332060] Start test: cache.test_cache_control.CCArgPrivateCached.test Apr 26 07:16:27 192.168.122.209 [54738.391563] [tdb] Start Tempesta DB Apr 26 07:16:28 192.168.122.209 [54738.526848] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:16:29 192.168.122.209 [54740.005803] [tempesta fw] Configuration processing is completed. Apr 26 07:16:29 192.168.122.209 [54740.060551] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:16:29 192.168.122.209 [54740.480268] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:16:30 192.168.122.209 [54740.506625] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:16:30 192.168.122.209 [54740.532440] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:16:30 192.168.122.209 [54740.585774] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:16:30 192.168.122.209 [54740.633713] [tempesta fw] Tempesta FW is ready Apr 26 07:16:30 192.168.122.209 [54741.222962] [tdb] Close table 'client0.tdb' Apr 26 07:16:30 192.168.122.209 [54741.408772] [tdb] Close table 'sessions0.tdb' Apr 26 07:16:34 192.168.122.209 [54744.569149] [tdb] Close table 'cache0.tdb' Apr 26 07:16:34 192.168.122.209 [54744.834689] [tdb] Close table 'filter0.tdb' Apr 26 07:16:34 192.168.122.209 [54744.835111] [tempesta fw] modules are stopped Apr 26 07:16:34 192.168.122.209 [54745.055502] [tempesta fw] exiting... Apr 26 07:16:34 192.168.122.209 [54745.167405] [tdb] Shutdown Tempesta DB Apr 26 07:16:34 192.168.122.209 [54745.384337] End test: cache.test_cache_control.CCArgPrivateCached.test Apr 26 07:16:34 192.168.122.209 [54745.421704] Start test: cache.test_cache_control.CCArgPrivateCached2.test Apr 26 07:16:35 192.168.122.209 [54746.430554] [tdb] Start Tempesta DB Apr 26 07:16:36 192.168.122.209 [54746.563890] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:16:37 192.168.122.209 [54748.097906] [tempesta fw] Configuration processing is completed. Apr 26 07:16:37 192.168.122.209 [54748.148185] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:16:38 192.168.122.209 [54748.563268] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:16:38 192.168.122.209 [54748.589888] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:16:38 192.168.122.209 [54748.617246] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:16:38 192.168.122.209 [54748.661787] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:16:38 192.168.122.209 [54748.717982] [tempesta fw] Tempesta FW is ready Apr 26 07:16:38 192.168.122.209 [54749.287889] [tdb] Close table 'client0.tdb' Apr 26 07:16:39 192.168.122.209 [54749.499450] [tdb] Close table 'sessions0.tdb' Apr 26 07:16:42 192.168.122.209 [54752.674332] [tdb] Close table 'cache0.tdb' Apr 26 07:16:42 192.168.122.209 [54752.934397] [tdb] Close table 'filter0.tdb' Apr 26 07:16:42 192.168.122.209 [54752.934810] [tempesta fw] modules are stopped Apr 26 07:16:42 192.168.122.209 [54753.133534] [tempesta fw] exiting... Apr 26 07:16:42 192.168.122.209 [54753.264453] [tdb] Shutdown Tempesta DB Apr 26 07:16:42 192.168.122.209 [54753.493409] End test: cache.test_cache_control.CCArgPrivateCached2.test Apr 26 07:16:43 192.168.122.209 [54753.510758] Start test: cache.test_cache_control.CacheHdrDelBypass.test Apr 26 07:16:44 192.168.122.209 [54754.529973] [tdb] Start Tempesta DB Apr 26 07:16:44 192.168.122.209 [54754.671054] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:16:45 192.168.122.209 [54756.218389] [tempesta fw] Configuration processing is completed. Apr 26 07:16:45 192.168.122.209 [54756.269654] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:16:46 192.168.122.209 [54756.714314] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:16:46 192.168.122.209 [54756.740290] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:16:46 192.168.122.209 [54756.765988] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:16:46 192.168.122.209 [54756.821944] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:16:46 192.168.122.209 [54756.881937] [tempesta fw] Tempesta FW is ready Apr 26 07:16:47 192.168.122.209 [54757.509752] [tdb] Close table 'client0.tdb' Apr 26 07:16:47 192.168.122.209 [54757.695351] [tdb] Close table 'sessions0.tdb' Apr 26 07:16:50 192.168.122.209 [54760.902794] [tdb] Close table 'cache0.tdb' Apr 26 07:16:50 192.168.122.209 [54761.137166] [tdb] Close table 'filter0.tdb' Apr 26 07:16:50 192.168.122.209 [54761.137613] [tempesta fw] modules are stopped Apr 26 07:16:50 192.168.122.209 [54761.329349] [tempesta fw] exiting... Apr 26 07:16:50 192.168.122.209 [54761.456493] [tdb] Shutdown Tempesta DB Apr 26 07:16:51 192.168.122.209 [54761.667830] End test: cache.test_cache_control.CacheHdrDelBypass.test Apr 26 07:16:51 192.168.122.209 [54761.687142] Start test: cache.test_cache_control.CacheHdrDelCached.test Apr 26 07:16:52 192.168.122.209 [54762.732293] [tdb] Start Tempesta DB Apr 26 07:16:52 192.168.122.209 [54762.866337] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:16:53 192.168.122.209 [54764.378019] [tempesta fw] Configuration processing is completed. Apr 26 07:16:53 192.168.122.209 [54764.428679] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:16:54 192.168.122.209 [54764.844077] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:16:54 192.168.122.209 [54764.882264] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:16:54 192.168.122.209 [54764.908959] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:16:54 192.168.122.209 [54764.953985] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:16:54 192.168.122.209 [54764.998030] [tempesta fw] Tempesta FW is ready Apr 26 07:16:55 192.168.122.209 [54765.582873] [tdb] Close table 'client0.tdb' Apr 26 07:16:55 192.168.122.209 [54765.753470] [tdb] Close table 'sessions0.tdb' Apr 26 07:16:58 192.168.122.209 [54768.963190] [tdb] Close table 'cache0.tdb' Apr 26 07:16:58 192.168.122.209 [54769.222798] [tdb] Close table 'filter0.tdb' Apr 26 07:16:58 192.168.122.209 [54769.223225] [tempesta fw] modules are stopped Apr 26 07:16:58 192.168.122.209 [54769.398043] [tempesta fw] exiting... Apr 26 07:16:59 192.168.122.209 [54769.533020] [tdb] Shutdown Tempesta DB Apr 26 07:16:59 192.168.122.209 [54769.744979] End test: cache.test_cache_control.CacheHdrDelCached.test Apr 26 07:16:59 192.168.122.209 [54769.762152] Start test: cache.test_cache_control.CacheHdrDelCached2.test Apr 26 07:17:00 192.168.122.209 [54770.821947] [tdb] Start Tempesta DB Apr 26 07:17:00 192.168.122.209 [54770.947982] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:17:01 192.168.122.209 [54772.446207] [tempesta fw] Configuration processing is completed. Apr 26 07:17:02 192.168.122.209 [54772.501790] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:17:02 192.168.122.209 [54772.920990] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:17:02 192.168.122.209 [54772.947462] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:17:02 192.168.122.209 [54772.972990] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:17:02 192.168.122.209 [54773.014122] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:17:02 192.168.122.209 [54773.074136] [tempesta fw] Tempesta FW is ready Apr 26 07:17:03 192.168.122.209 [54773.685071] [tdb] Close table 'client0.tdb' Apr 26 07:17:03 192.168.122.209 [54773.867771] [tdb] Close table 'sessions0.tdb' Apr 26 07:17:06 192.168.122.209 [54777.048996] [tdb] Close table 'cache0.tdb' Apr 26 07:17:06 192.168.122.209 [54777.299104] [tdb] Close table 'filter0.tdb' Apr 26 07:17:06 192.168.122.209 [54777.299591] [tempesta fw] modules are stopped Apr 26 07:17:07 192.168.122.209 [54777.527592] [tempesta fw] exiting... Apr 26 07:17:07 192.168.122.209 [54777.670805] [tdb] Shutdown Tempesta DB Apr 26 07:17:07 192.168.122.209 [54777.892014] End test: cache.test_cache_control.CacheHdrDelCached2.test Apr 26 07:17:07 192.168.122.209 [54777.921849] Start test: cache.test_cache_control.CacheTtlGlobalApplied.test Apr 26 07:17:08 192.168.122.209 [54778.999340] [tdb] Start Tempesta DB Apr 26 07:17:08 192.168.122.209 [54779.127571] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:17:10 192.168.122.209 [54780.694306] [tempesta fw] Configuration processing is completed. Apr 26 07:17:10 192.168.122.209 [54780.746269] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:17:10 192.168.122.209 [54781.172817] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:17:10 192.168.122.209 [54781.198692] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:17:10 192.168.122.209 [54781.224106] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:17:10 192.168.122.209 [54781.290294] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:17:10 192.168.122.209 [54781.338237] [tempesta fw] Tempesta FW is ready Apr 26 07:17:13 192.168.122.209 [54783.923502] [tdb] Close table 'client0.tdb' Apr 26 07:17:13 192.168.122.209 [54784.113821] [tdb] Close table 'sessions0.tdb' Apr 26 07:17:16 192.168.122.209 [54787.327208] [tdb] Close table 'cache0.tdb' Apr 26 07:17:17 192.168.122.209 [54787.559436] [tdb] Close table 'filter0.tdb' Apr 26 07:17:17 192.168.122.209 [54787.559864] [tempesta fw] modules are stopped Apr 26 07:17:17 192.168.122.209 [54787.784823] [tempesta fw] exiting... Apr 26 07:17:17 192.168.122.209 [54787.888621] [tdb] Shutdown Tempesta DB Apr 26 07:17:17 192.168.122.209 [54788.109102] End test: cache.test_cache_control.CacheTtlGlobalApplied.test Apr 26 07:17:17 192.168.122.209 [54788.131249] Start test: cache.test_cache_control.CacheTtlGlobalApplied2.test Apr 26 07:17:18 192.168.122.209 [54789.173596] [tdb] Start Tempesta DB Apr 26 07:17:18 192.168.122.209 [54789.319034] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:17:20 192.168.122.209 [54790.822430] [tempesta fw] Configuration processing is completed. Apr 26 07:17:20 192.168.122.209 [54790.877004] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:17:20 192.168.122.209 [54791.306416] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:17:20 192.168.122.209 [54791.334700] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:17:20 192.168.122.209 [54791.363733] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:17:20 192.168.122.209 [54791.410404] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:17:20 192.168.122.209 [54791.458355] [tempesta fw] Tempesta FW is ready Apr 26 07:17:24 192.168.122.209 [54795.086766] [tdb] Close table 'client0.tdb' Apr 26 07:17:24 192.168.122.209 [54795.277945] [tdb] Close table 'sessions0.tdb' Apr 26 07:17:28 192.168.122.209 [54798.542241] [tdb] Close table 'cache0.tdb' Apr 26 07:17:28 192.168.122.209 [54798.781355] [tdb] Close table 'filter0.tdb' Apr 26 07:17:28 192.168.122.209 [54798.781807] [tempesta fw] modules are stopped Apr 26 07:17:28 192.168.122.209 [54798.991297] [tempesta fw] exiting... Apr 26 07:17:28 192.168.122.209 [54799.139561] [tdb] Shutdown Tempesta DB Apr 26 07:17:28 192.168.122.209 [54799.368058] End test: cache.test_cache_control.CacheTtlGlobalApplied2.test Apr 26 07:17:28 192.168.122.209 [54799.397244] Start test: cache.test_cache_control.CacheTtlGlobalHonourMaxAge.test Apr 26 07:17:29 192.168.122.209 [54800.402491] [tdb] Start Tempesta DB Apr 26 07:17:30 192.168.122.209 [54800.561981] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:17:31 192.168.122.209 [54802.063003] [tempesta fw] Configuration processing is completed. Apr 26 07:17:31 192.168.122.209 [54802.113495] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:17:32 192.168.122.209 [54802.538290] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:17:32 192.168.122.209 [54802.578068] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:17:32 192.168.122.209 [54802.604543] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:17:32 192.168.122.209 [54802.650530] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:17:32 192.168.122.209 [54802.702525] [tempesta fw] Tempesta FW is ready Apr 26 07:17:35 192.168.122.209 [54806.318944] [tdb] Close table 'client0.tdb' Apr 26 07:17:36 192.168.122.209 [54806.503870] [tdb] Close table 'sessions0.tdb' Apr 26 07:17:39 192.168.122.209 [54809.717127] [tdb] Close table 'cache0.tdb' Apr 26 07:17:39 192.168.122.209 [54809.952904] [tdb] Close table 'filter0.tdb' Apr 26 07:17:39 192.168.122.209 [54809.953312] [tempesta fw] modules are stopped Apr 26 07:17:39 192.168.122.209 [54810.203488] [tempesta fw] exiting... Apr 26 07:17:39 192.168.122.209 [54810.317602] [tdb] Shutdown Tempesta DB Apr 26 07:17:40 192.168.122.209 [54810.554805] End test: cache.test_cache_control.CacheTtlGlobalHonourMaxAge.test Apr 26 07:17:40 192.168.122.209 [54810.574875] Start test: cache.test_cache_control.CacheTtlGlobalHonourMaxAge2.test Apr 26 07:17:41 192.168.122.209 [54811.656173] [tdb] Start Tempesta DB Apr 26 07:17:41 192.168.122.209 [54811.797535] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:17:42 192.168.122.209 [54813.366699] [tempesta fw] Configuration processing is completed. Apr 26 07:17:42 192.168.122.209 [54813.417062] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:17:43 192.168.122.209 [54813.846288] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:17:43 192.168.122.209 [54813.884034] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:17:43 192.168.122.209 [54813.912517] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:17:43 192.168.122.209 [54813.958717] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:17:43 192.168.122.209 [54814.018645] [tempesta fw] Tempesta FW is ready Apr 26 07:17:47 192.168.122.209 [54817.629936] [tdb] Close table 'client0.tdb' Apr 26 07:17:47 192.168.122.209 [54817.813735] [tdb] Close table 'sessions0.tdb' Apr 26 07:17:50 192.168.122.209 [54821.032945] [tdb] Close table 'cache0.tdb' Apr 26 07:17:50 192.168.122.209 [54821.274188] [tdb] Close table 'filter0.tdb' Apr 26 07:17:50 192.168.122.209 [54821.275002] [tempesta fw] modules are stopped Apr 26 07:17:51 192.168.122.209 [54821.529238] [tempesta fw] exiting... Apr 26 07:17:51 192.168.122.209 [54821.639882] [tdb] Shutdown Tempesta DB Apr 26 07:17:51 192.168.122.209 [54821.867474] End test: cache.test_cache_control.CacheTtlGlobalHonourMaxAge2.test Apr 26 07:17:51 192.168.122.209 [54821.883225] Start test: cache.test_cache_control.CacheTtlHonourNoCache.test Apr 26 07:17:52 192.168.122.209 [54822.928931] [tdb] Start Tempesta DB Apr 26 07:17:52 192.168.122.209 [54823.073478] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:17:54 192.168.122.209 [54824.655113] [tempesta fw] Configuration processing is completed. Apr 26 07:17:54 192.168.122.209 [54824.707904] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:17:54 192.168.122.209 [54825.174455] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:17:54 192.168.122.209 [54825.211555] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:17:54 192.168.122.209 [54825.240919] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:17:54 192.168.122.209 [54825.286822] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:17:54 192.168.122.209 [54825.338777] [tempesta fw] Tempesta FW is ready Apr 26 07:17:57 192.168.122.209 [54827.977763] [tdb] Close table 'client0.tdb' Apr 26 07:17:57 192.168.122.209 [54828.159937] [tdb] Close table 'sessions0.tdb' Apr 26 07:18:00 192.168.122.209 [54831.407326] [tdb] Close table 'cache0.tdb' Apr 26 07:18:01 192.168.122.209 [54831.659765] [tdb] Close table 'filter0.tdb' Apr 26 07:18:01 192.168.122.209 [54831.660296] [tempesta fw] modules are stopped Apr 26 07:18:01 192.168.122.209 [54831.880617] [tempesta fw] exiting... Apr 26 07:18:01 192.168.122.209 [54832.024858] [tdb] Shutdown Tempesta DB Apr 26 07:18:01 192.168.122.209 [54832.247425] End test: cache.test_cache_control.CacheTtlHonourNoCache.test Apr 26 07:18:01 192.168.122.209 [54832.279178] Start test: cache.test_cache_control.CacheTtlHttpChainHonourMaxAge.test Apr 26 07:18:02 192.168.122.209 [54833.427344] [tdb] Start Tempesta DB Apr 26 07:18:03 192.168.122.209 [54833.561080] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:18:04 192.168.122.209 [54835.223010] [tempesta fw] Configuration processing is completed. Apr 26 07:18:04 192.168.122.209 [54835.281693] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:18:05 192.168.122.209 [54835.697668] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:18:05 192.168.122.209 [54835.724169] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:18:05 192.168.122.209 [54835.751426] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:18:05 192.168.122.209 [54835.798987] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:18:05 192.168.122.209 [54835.854962] [tempesta fw] Tempesta FW is ready Apr 26 07:18:10 192.168.122.209 [54840.528558] [tdb] Close table 'client0.tdb' Apr 26 07:18:10 192.168.122.209 [54840.722992] [tdb] Close table 'sessions0.tdb' Apr 26 07:18:13 192.168.122.209 [54844.155839] [tdb] Close table 'cache0.tdb' Apr 26 07:18:13 192.168.122.209 [54844.414251] [tdb] Close table 'filter0.tdb' Apr 26 07:18:13 192.168.122.209 [54844.414684] [tempesta fw] modules are stopped Apr 26 07:18:14 192.168.122.209 [54844.634992] [tempesta fw] exiting... Apr 26 07:18:14 192.168.122.209 [54844.768913] [tdb] Shutdown Tempesta DB Apr 26 07:18:14 192.168.122.209 [54844.982690] End test: cache.test_cache_control.CacheTtlHttpChainHonourMaxAge.test Apr 26 07:18:14 192.168.122.209 [54844.993451] Start test: cache.test_cache_control.CacheTtlHttpChainOverride.test Apr 26 07:18:15 192.168.122.209 [54846.078524] [tdb] Start Tempesta DB Apr 26 07:18:15 192.168.122.209 [54846.212513] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:18:17 192.168.122.209 [54847.815157] [tempesta fw] Configuration processing is completed. Apr 26 07:18:17 192.168.122.209 [54847.873988] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:18:17 192.168.122.209 [54848.339891] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:18:17 192.168.122.209 [54848.369003] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:18:17 192.168.122.209 [54848.397986] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:18:17 192.168.122.209 [54848.463123] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:18:18 192.168.122.209 [54848.515096] [tempesta fw] Tempesta FW is ready Apr 26 07:18:20 192.168.122.209 [54851.136998] [tdb] Close table 'client0.tdb' Apr 26 07:18:20 192.168.122.209 [54851.327663] [tdb] Close table 'sessions0.tdb' Apr 26 07:18:24 192.168.122.209 [54854.632841] [tdb] Close table 'cache0.tdb' Apr 26 07:18:24 192.168.122.209 [54854.886268] [tdb] Close table 'filter0.tdb' Apr 26 07:18:24 192.168.122.209 [54854.886723] [tempesta fw] modules are stopped Apr 26 07:18:24 192.168.122.209 [54855.111498] [tempesta fw] exiting... Apr 26 07:18:24 192.168.122.209 [54855.273626] [tdb] Shutdown Tempesta DB Apr 26 07:18:25 192.168.122.209 [54855.501672] End test: cache.test_cache_control.CacheTtlHttpChainOverride.test Apr 26 07:18:25 192.168.122.209 [54855.526693] Start test: cache.test_cache_control.HttpChainCacheActionBypass.test Apr 26 07:18:26 192.168.122.209 [54856.603770] [tdb] Start Tempesta DB Apr 26 07:18:26 192.168.122.209 [54856.753637] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:18:27 192.168.122.209 [54858.443314] [tempesta fw] Configuration processing is completed. Apr 26 07:18:27 192.168.122.209 [54858.494868] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:18:28 192.168.122.209 [54858.910205] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:18:28 192.168.122.209 [54858.937442] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:18:28 192.168.122.209 [54858.965215] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:18:28 192.168.122.209 [54859.011268] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:18:28 192.168.122.209 [54859.047220] [tempesta fw] Tempesta FW is ready Apr 26 07:18:29 192.168.122.209 [54859.636767] [tdb] Close table 'client0.tdb' Apr 26 07:18:29 192.168.122.209 [54859.833723] [tdb] Close table 'sessions0.tdb' Apr 26 07:18:32 192.168.122.209 [54862.986021] [tdb] Close table 'cache0.tdb' Apr 26 07:18:32 192.168.122.209 [54863.233498] [tdb] Close table 'filter0.tdb' Apr 26 07:18:32 192.168.122.209 [54863.233961] [tempesta fw] modules are stopped Apr 26 07:18:32 192.168.122.209 [54863.416578] [tempesta fw] exiting... Apr 26 07:18:33 192.168.122.209 [54863.526085] [tdb] Shutdown Tempesta DB Apr 26 07:18:33 192.168.122.209 [54863.755081] End test: cache.test_cache_control.HttpChainCacheActionBypass.test Apr 26 07:18:33 192.168.122.209 [54863.768718] Start test: cache.test_cache_control.HttpChainCacheActionCached.test Apr 26 07:18:34 192.168.122.209 [54864.810092] [tdb] Start Tempesta DB Apr 26 07:18:34 192.168.122.209 [54864.941313] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:18:36 192.168.122.209 [54866.639401] [tempesta fw] Configuration processing is completed. Apr 26 07:18:36 192.168.122.209 [54866.716295] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:18:36 192.168.122.209 [54867.124963] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:18:36 192.168.122.209 [54867.150978] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:18:36 192.168.122.209 [54867.177918] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:18:36 192.168.122.209 [54867.223368] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:18:36 192.168.122.209 [54867.267327] [tempesta fw] Tempesta FW is ready Apr 26 07:18:37 192.168.122.209 [54867.831422] [tdb] Close table 'client0.tdb' Apr 26 07:18:37 192.168.122.209 [54868.007309] [tdb] Close table 'sessions0.tdb' Apr 26 07:18:40 192.168.122.209 [54871.247085] [tdb] Close table 'cache0.tdb' Apr 26 07:18:41 192.168.122.209 [54871.514416] [tdb] Close table 'filter0.tdb' Apr 26 07:18:41 192.168.122.209 [54871.514859] [tempesta fw] modules are stopped Apr 26 07:18:41 192.168.122.209 [54871.717589] [tempesta fw] exiting... Apr 26 07:18:41 192.168.122.209 [54871.838867] [tdb] Shutdown Tempesta DB Apr 26 07:18:41 192.168.122.209 [54872.062849] End test: cache.test_cache_control.HttpChainCacheActionCached.test Apr 26 07:18:41 192.168.122.209 [54872.081012] Start test: cache.test_cache_control.HttpChainCacheActionOverrideBypass.test Apr 26 07:18:42 192.168.122.209 [54873.113764] [tdb] Start Tempesta DB Apr 26 07:18:42 192.168.122.209 [54873.245286] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:18:44 192.168.122.209 [54874.879543] [tempesta fw] Configuration processing is completed. Apr 26 07:18:44 192.168.122.209 [54874.933786] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:18:44 192.168.122.209 [54875.351199] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:18:44 192.168.122.209 [54875.378013] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:18:44 192.168.122.209 [54875.404012] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:18:44 192.168.122.209 [54875.443419] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:18:44 192.168.122.209 [54875.487416] [tempesta fw] Tempesta FW is ready Apr 26 07:18:45 192.168.122.209 [54876.110265] [tdb] Close table 'client0.tdb' Apr 26 07:18:45 192.168.122.209 [54876.297611] [tdb] Close table 'sessions0.tdb' Apr 26 07:18:48 192.168.122.209 [54879.468886] [tdb] Close table 'cache0.tdb' Apr 26 07:18:49 192.168.122.209 [54879.702819] [tdb] Close table 'filter0.tdb' Apr 26 07:18:49 192.168.122.209 [54879.703278] [tempesta fw] modules are stopped Apr 26 07:18:49 192.168.122.209 [54879.893253] [tempesta fw] exiting... Apr 26 07:18:49 192.168.122.209 [54880.030481] [tdb] Shutdown Tempesta DB Apr 26 07:18:49 192.168.122.209 [54880.246355] End test: cache.test_cache_control.HttpChainCacheActionOverrideBypass.test Apr 26 07:18:49 192.168.122.209 [54880.261171] Start test: cache.test_cache_control.HttpChainCacheActionOverrideCached.test Apr 26 07:18:50 192.168.122.209 [54881.339343] [tdb] Start Tempesta DB Apr 26 07:18:50 192.168.122.209 [54881.482849] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:18:52 192.168.122.209 [54883.075615] [tempesta fw] Configuration processing is completed. Apr 26 07:18:52 192.168.122.209 [54883.125185] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:18:53 192.168.122.209 [54883.536261] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:18:53 192.168.122.209 [54883.562508] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:18:53 192.168.122.209 [54883.589759] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:18:53 192.168.122.209 [54883.631562] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:18:53 192.168.122.209 [54883.679511] [tempesta fw] Tempesta FW is ready Apr 26 07:18:53 192.168.122.209 [54884.284809] [tdb] Close table 'client0.tdb' Apr 26 07:18:53 192.168.122.209 [54884.490431] [tdb] Close table 'sessions0.tdb' Apr 26 07:18:57 192.168.122.209 [54887.654333] [tdb] Close table 'cache0.tdb' Apr 26 07:18:57 192.168.122.209 [54887.894057] [tdb] Close table 'filter0.tdb' Apr 26 07:18:57 192.168.122.209 [54887.894480] [tempesta fw] modules are stopped Apr 26 07:18:57 192.168.122.209 [54888.115580] [tempesta fw] exiting... Apr 26 07:18:57 192.168.122.209 [54888.297995] [tdb] Shutdown Tempesta DB Apr 26 07:18:58 192.168.122.209 [54888.515490] End test: cache.test_cache_control.HttpChainCacheActionOverrideCached.test Apr 26 07:18:58 192.168.122.209 [54888.529657] Start test: cache.test_cache_control.RequestMaxAge0NoCache.test Apr 26 07:18:59 192.168.122.209 [54889.579384] [tdb] Start Tempesta DB Apr 26 07:18:59 192.168.122.209 [54889.726098] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:19:00 192.168.122.209 [54891.191768] [tempesta fw] Configuration processing is completed. Apr 26 07:19:00 192.168.122.209 [54891.252366] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:19:01 192.168.122.209 [54891.674422] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:19:01 192.168.122.209 [54891.700106] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:19:01 192.168.122.209 [54891.726266] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:19:01 192.168.122.209 [54891.775677] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:19:01 192.168.122.209 [54891.831646] [tempesta fw] Tempesta FW is ready Apr 26 07:19:01 192.168.122.209 [54892.439117] [tdb] Close table 'client0.tdb' Apr 26 07:19:02 192.168.122.209 [54892.633608] [tdb] Close table 'sessions0.tdb' Apr 26 07:19:05 192.168.122.209 [54895.806724] [tdb] Close table 'cache0.tdb' Apr 26 07:19:05 192.168.122.209 [54896.033054] [tdb] Close table 'filter0.tdb' Apr 26 07:19:05 192.168.122.209 [54896.033485] [tempesta fw] modules are stopped Apr 26 07:19:05 192.168.122.209 [54896.206272] [tempesta fw] exiting... Apr 26 07:19:05 192.168.122.209 [54896.318871] [tdb] Shutdown Tempesta DB Apr 26 07:19:06 192.168.122.209 [54896.545891] End test: cache.test_cache_control.RequestMaxAge0NoCache.test Apr 26 07:19:06 192.168.122.209 [54896.564434] Start test: cache.test_cache_control.RequestMaxAge0NoCache2.test Apr 26 07:19:07 192.168.122.209 [54897.581471] [tdb] Start Tempesta DB Apr 26 07:19:07 192.168.122.209 [54897.717518] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:19:08 192.168.122.209 [54899.151804] [tempesta fw] Configuration processing is completed. Apr 26 07:19:08 192.168.122.209 [54899.203637] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:19:09 192.168.122.209 [54899.621102] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:19:09 192.168.122.209 [54899.647697] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:19:09 192.168.122.209 [54899.674911] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:19:09 192.168.122.209 [54899.719795] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:19:09 192.168.122.209 [54899.759714] [tempesta fw] Tempesta FW is ready Apr 26 07:19:09 192.168.122.209 [54900.358345] [tdb] Close table 'client0.tdb' Apr 26 07:19:10 192.168.122.209 [54900.557163] [tdb] Close table 'sessions0.tdb' Apr 26 07:19:13 192.168.122.209 [54903.779909] [tdb] Close table 'cache0.tdb' Apr 26 07:19:13 192.168.122.209 [54904.025404] [tdb] Close table 'filter0.tdb' Apr 26 07:19:13 192.168.122.209 [54904.025835] [tempesta fw] modules are stopped Apr 26 07:19:13 192.168.122.209 [54904.214037] [tempesta fw] exiting... Apr 26 07:19:13 192.168.122.209 [54904.345059] [tdb] Shutdown Tempesta DB Apr 26 07:19:14 192.168.122.209 [54904.564364] End test: cache.test_cache_control.RequestMaxAge0NoCache2.test Apr 26 07:19:14 192.168.122.209 [54904.582894] Start test: cache.test_cache_control.RequestMaxAgeCached.test Apr 26 07:19:15 192.168.122.209 [54905.608865] [tdb] Start Tempesta DB Apr 26 07:19:15 192.168.122.209 [54905.745116] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:19:16 192.168.122.209 [54907.200245] [tempesta fw] Configuration processing is completed. Apr 26 07:19:16 192.168.122.209 [54907.252348] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:19:17 192.168.122.209 [54907.670573] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:19:17 192.168.122.209 [54907.706095] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:19:17 192.168.122.209 [54907.732857] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:19:17 192.168.122.209 [54907.775910] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:19:17 192.168.122.209 [54907.811823] [tempesta fw] Tempesta FW is ready Apr 26 07:19:17 192.168.122.209 [54908.378044] [tdb] Close table 'client0.tdb' Apr 26 07:19:18 192.168.122.209 [54908.563129] [tdb] Close table 'sessions0.tdb' Apr 26 07:19:21 192.168.122.209 [54911.751900] [tdb] Close table 'cache0.tdb' Apr 26 07:19:21 192.168.122.209 [54911.972256] [tdb] Close table 'filter0.tdb' Apr 26 07:19:21 192.168.122.209 [54911.972702] [tempesta fw] modules are stopped Apr 26 07:19:21 192.168.122.209 [54912.169147] [tempesta fw] exiting... Apr 26 07:19:21 192.168.122.209 [54912.288058] [tdb] Shutdown Tempesta DB Apr 26 07:19:22 192.168.122.209 [54912.546942] End test: cache.test_cache_control.RequestMaxAgeCached.test Apr 26 07:19:22 192.168.122.209 [54912.569077] Start test: cache.test_cache_control.RequestMaxAgeMaxStaleCached.test Apr 26 07:19:23 192.168.122.209 [54913.601759] [tdb] Start Tempesta DB Apr 26 07:19:23 192.168.122.209 [54913.746686] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:19:24 192.168.122.209 [54915.220000] [tempesta fw] Configuration processing is completed. Apr 26 07:19:24 192.168.122.209 [54915.274957] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:19:25 192.168.122.209 [54915.695440] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:19:25 192.168.122.209 [54915.722956] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:19:25 192.168.122.209 [54915.748907] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:19:25 192.168.122.209 [54915.819966] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:19:25 192.168.122.209 [54915.863914] [tempesta fw] Tempesta FW is ready Apr 26 07:19:27 192.168.122.209 [54917.991120] [tdb] Close table 'client0.tdb' Apr 26 07:19:27 192.168.122.209 [54918.167016] [tdb] Close table 'sessions0.tdb' Apr 26 07:19:30 192.168.122.209 [54921.374374] [tdb] Close table 'cache0.tdb' Apr 26 07:19:31 192.168.122.209 [54921.718977] [tdb] Close table 'filter0.tdb' Apr 26 07:19:31 192.168.122.209 [54921.719427] [tempesta fw] modules are stopped Apr 26 07:19:31 192.168.122.209 [54921.937985] [tempesta fw] exiting... Apr 26 07:19:31 192.168.122.209 [54922.103374] [tdb] Shutdown Tempesta DB Apr 26 07:19:31 192.168.122.209 [54922.325199] End test: cache.test_cache_control.RequestMaxAgeMaxStaleCached.test Apr 26 07:19:31 192.168.122.209 [54922.344419] Start test: cache.test_cache_control.RequestMaxAgeMaxStaleNotCached.test Apr 26 07:19:32 192.168.122.209 [54923.421819] [tdb] Start Tempesta DB Apr 26 07:19:33 192.168.122.209 [54923.564284] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:19:34 192.168.122.209 [54925.016161] [tempesta fw] Configuration processing is completed. Apr 26 07:19:34 192.168.122.209 [54925.075636] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:19:35 192.168.122.209 [54925.500647] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:19:35 192.168.122.209 [54925.527178] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:19:35 192.168.122.209 [54925.554226] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:19:35 192.168.122.209 [54925.620137] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:19:35 192.168.122.209 [54925.664041] [tempesta fw] Tempesta FW is ready Apr 26 07:19:38 192.168.122.209 [54929.304175] [tdb] Close table 'client0.tdb' Apr 26 07:19:38 192.168.122.209 [54929.489897] [tdb] Close table 'sessions0.tdb' Apr 26 07:19:42 192.168.122.209 [54932.653418] [tdb] Close table 'cache0.tdb' Apr 26 07:19:42 192.168.122.209 [54932.899528] [tdb] Close table 'filter0.tdb' Apr 26 07:19:42 192.168.122.209 [54932.900080] [tempesta fw] modules are stopped Apr 26 07:19:42 192.168.122.209 [54933.083174] [tempesta fw] exiting... Apr 26 07:19:42 192.168.122.209 [54933.197461] [tdb] Shutdown Tempesta DB Apr 26 07:19:42 192.168.122.209 [54933.402109] End test: cache.test_cache_control.RequestMaxAgeMaxStaleNotCached.test Apr 26 07:19:42 192.168.122.209 [54933.413061] Start test: cache.test_cache_control.RequestMaxAgeNoCached.test Apr 26 07:19:43 192.168.122.209 [54934.496347] [tdb] Start Tempesta DB Apr 26 07:19:44 192.168.122.209 [54934.641403] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:19:45 192.168.122.209 [54936.120263] [tempesta fw] Configuration processing is completed. Apr 26 07:19:45 192.168.122.209 [54936.176554] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:19:46 192.168.122.209 [54936.591987] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:19:46 192.168.122.209 [54936.619106] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:19:46 192.168.122.209 [54936.645737] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:19:46 192.168.122.209 [54936.692208] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:19:46 192.168.122.209 [54936.732194] [tempesta fw] Tempesta FW is ready Apr 26 07:19:48 192.168.122.209 [54939.336713] [tdb] Close table 'client0.tdb' Apr 26 07:19:49 192.168.122.209 [54939.544124] [tdb] Close table 'sessions0.tdb' Apr 26 07:19:52 192.168.122.209 [54942.768899] [tdb] Close table 'cache0.tdb' Apr 26 07:19:52 192.168.122.209 [54943.001963] [tdb] Close table 'filter0.tdb' Apr 26 07:19:52 192.168.122.209 [54943.002370] [tempesta fw] modules are stopped Apr 26 07:19:52 192.168.122.209 [54943.212935] [tempesta fw] exiting... Apr 26 07:19:52 192.168.122.209 [54943.341970] [tdb] Shutdown Tempesta DB Apr 26 07:19:53 192.168.122.209 [54943.565006] End test: cache.test_cache_control.RequestMaxAgeNoCached.test Apr 26 07:19:53 192.168.122.209 [54943.581855] Start test: cache.test_cache_control.RequestMaxStaleCached.test Apr 26 07:19:54 192.168.122.209 [54944.718219] [tdb] Start Tempesta DB Apr 26 07:19:54 192.168.122.209 [54944.860786] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:19:55 192.168.122.209 [54946.284399] [tempesta fw] Configuration processing is completed. Apr 26 07:19:55 192.168.122.209 [54946.336478] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:19:56 192.168.122.209 [54946.755094] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:19:56 192.168.122.209 [54946.781191] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:19:56 192.168.122.209 [54946.808132] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:19:56 192.168.122.209 [54946.852357] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:19:56 192.168.122.209 [54946.892303] [tempesta fw] Tempesta FW is ready Apr 26 07:19:58 192.168.122.209 [54948.980769] [tdb] Close table 'client0.tdb' Apr 26 07:19:58 192.168.122.209 [54949.165097] [tdb] Close table 'sessions0.tdb' Apr 26 07:20:01 192.168.122.209 [54952.341571] [tdb] Close table 'cache0.tdb' Apr 26 07:20:02 192.168.122.209 [54952.577270] [tdb] Close table 'filter0.tdb' Apr 26 07:20:02 192.168.122.209 [54952.577714] [tempesta fw] modules are stopped Apr 26 07:20:02 192.168.122.209 [54952.770432] [tempesta fw] exiting... Apr 26 07:20:02 192.168.122.209 [54952.875189] [tdb] Shutdown Tempesta DB Apr 26 07:20:02 192.168.122.209 [54953.137245] End test: cache.test_cache_control.RequestMaxStaleCached.test Apr 26 07:20:02 192.168.122.209 [54953.158708] Start test: cache.test_cache_control.RequestMinFreshCached.test Apr 26 07:20:03 192.168.122.209 [54954.193484] [tdb] Start Tempesta DB Apr 26 07:20:03 192.168.122.209 [54954.321023] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:20:05 192.168.122.209 [54955.728581] [tempesta fw] Configuration processing is completed. Apr 26 07:20:05 192.168.122.209 [54955.780459] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:20:05 192.168.122.209 [54956.202521] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:20:05 192.168.122.209 [54956.249780] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:20:05 192.168.122.209 [54956.275174] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:20:05 192.168.122.209 [54956.316480] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:20:05 192.168.122.209 [54956.364428] [tempesta fw] Tempesta FW is ready Apr 26 07:20:06 192.168.122.209 [54956.931626] [tdb] Close table 'client0.tdb' Apr 26 07:20:06 192.168.122.209 [54957.139746] [tdb] Close table 'sessions0.tdb' Apr 26 07:20:09 192.168.122.209 [54960.235996] [tdb] Close table 'cache0.tdb' Apr 26 07:20:09 192.168.122.209 [54960.480110] [tdb] Close table 'filter0.tdb' Apr 26 07:20:09 192.168.122.209 [54960.480562] [tempesta fw] modules are stopped Apr 26 07:20:10 192.168.122.209 [54960.660877] [tempesta fw] exiting... Apr 26 07:20:10 192.168.122.209 [54960.787792] [tdb] Shutdown Tempesta DB Apr 26 07:20:10 192.168.122.209 [54961.014625] End test: cache.test_cache_control.RequestMinFreshCached.test Apr 26 07:20:10 192.168.122.209 [54961.030385] Start test: cache.test_cache_control.RequestMinFreshNotCached.test Apr 26 07:20:11 192.168.122.209 [54962.032998] [tdb] Start Tempesta DB Apr 26 07:20:11 192.168.122.209 [54962.145887] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:20:13 192.168.122.209 [54963.608657] [tempesta fw] Configuration processing is completed. Apr 26 07:20:13 192.168.122.209 [54963.664038] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:20:13 192.168.122.209 [54964.081870] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:20:13 192.168.122.209 [54964.108318] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:20:13 192.168.122.209 [54964.135349] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:20:13 192.168.122.209 [54964.196578] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:20:13 192.168.122.209 [54964.240537] [tempesta fw] Tempesta FW is ready Apr 26 07:20:16 192.168.122.209 [54966.883176] [tdb] Close table 'client0.tdb' Apr 26 07:20:16 192.168.122.209 [54967.073302] [tdb] Close table 'sessions0.tdb' Apr 26 07:20:19 192.168.122.209 [54970.264930] [tdb] Close table 'cache0.tdb' Apr 26 07:20:20 192.168.122.209 [54970.499057] [tdb] Close table 'filter0.tdb' Apr 26 07:20:20 192.168.122.209 [54970.499477] [tempesta fw] modules are stopped Apr 26 07:20:20 192.168.122.209 [54970.699658] [tempesta fw] exiting... Apr 26 07:20:20 192.168.122.209 [54970.823737] [tdb] Shutdown Tempesta DB Apr 26 07:20:20 192.168.122.209 [54971.037021] End test: cache.test_cache_control.RequestMinFreshNotCached.test Apr 26 07:20:20 192.168.122.209 [54971.051462] Start test: cache.test_cache_control.RequestNoChacheNotCached.test Apr 26 07:20:21 192.168.122.209 [54972.085612] [tdb] Start Tempesta DB Apr 26 07:20:21 192.168.122.209 [54972.215162] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:20:23 192.168.122.209 [54973.608744] [tempesta fw] Configuration processing is completed. Apr 26 07:20:23 192.168.122.209 [54973.659267] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:20:23 192.168.122.209 [54974.070336] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:20:23 192.168.122.209 [54974.096103] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:20:23 192.168.122.209 [54974.121809] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:20:23 192.168.122.209 [54974.172713] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:20:23 192.168.122.209 [54974.212669] [tempesta fw] Tempesta FW is ready Apr 26 07:20:24 192.168.122.209 [54974.819058] [tdb] Close table 'client0.tdb' Apr 26 07:20:24 192.168.122.209 [54975.013961] [tdb] Close table 'sessions0.tdb' Apr 26 07:20:27 192.168.122.209 [54978.138445] [tdb] Close table 'cache0.tdb' Apr 26 07:20:27 192.168.122.209 [54978.385609] [tdb] Close table 'filter0.tdb' Apr 26 07:20:27 192.168.122.209 [54978.386046] [tempesta fw] modules are stopped Apr 26 07:20:28 192.168.122.209 [54978.569999] [tempesta fw] exiting... Apr 26 07:20:28 192.168.122.209 [54978.661789] [tdb] Shutdown Tempesta DB Apr 26 07:20:28 192.168.122.209 [54978.881769] End test: cache.test_cache_control.RequestNoChacheNotCached.test Apr 26 07:20:28 192.168.122.209 [54978.893413] Start test: cache.test_cache_control.RequestNoStoreNotCached.test Apr 26 07:20:29 192.168.122.209 [54979.922249] [tdb] Start Tempesta DB Apr 26 07:20:29 192.168.122.209 [54980.051317] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:20:31 192.168.122.209 [54981.544878] [tempesta fw] Configuration processing is completed. Apr 26 07:20:31 192.168.122.209 [54981.595766] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:20:31 192.168.122.209 [54982.021056] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:20:31 192.168.122.209 [54982.047306] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:20:31 192.168.122.209 [54982.074218] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:20:31 192.168.122.209 [54982.120784] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:20:31 192.168.122.209 [54982.188783] [tempesta fw] Tempesta FW is ready Apr 26 07:20:32 192.168.122.209 [54982.795951] [tdb] Close table 'client0.tdb' Apr 26 07:20:32 192.168.122.209 [54982.974061] [tdb] Close table 'sessions0.tdb' Apr 26 07:20:35 192.168.122.209 [54986.122566] [tdb] Close table 'cache0.tdb' Apr 26 07:20:35 192.168.122.209 [54986.344482] [tdb] Close table 'filter0.tdb' Apr 26 07:20:35 192.168.122.209 [54986.344925] [tempesta fw] modules are stopped Apr 26 07:20:36 192.168.122.209 [54986.537101] [tempesta fw] exiting... Apr 26 07:20:36 192.168.122.209 [54986.661524] [tdb] Shutdown Tempesta DB Apr 26 07:20:36 192.168.122.209 [54986.887272] End test: cache.test_cache_control.RequestNoStoreNotCached.test Apr 26 07:20:36 192.168.122.209 [54986.903752] Start test: cache.test_cache_control.RequestOnlyIfCached504.test Apr 26 07:20:37 192.168.122.209 [54987.943154] [tdb] Start Tempesta DB Apr 26 07:20:37 192.168.122.209 [54988.090848] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:20:39 192.168.122.209 [54989.536942] [tempesta fw] Configuration processing is completed. Apr 26 07:20:39 192.168.122.209 [54989.588446] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:20:39 192.168.122.209 [54990.004018] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:20:39 192.168.122.209 [54990.030387] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:20:39 192.168.122.209 [54990.056450] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:20:39 192.168.122.209 [54990.092923] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:20:39 192.168.122.209 [54990.132858] [tempesta fw] Tempesta FW is ready Apr 26 07:20:42 192.168.122.209 [54992.817581] [tempesta fw] Warning: resource not cached, status 504: 127.0.0.2 Apr 26 07:20:42 192.168.122.209 [54993.246688] [tdb] Close table 'client0.tdb' Apr 26 07:20:42 192.168.122.209 [54993.434789] [tdb] Close table 'sessions0.tdb' Apr 26 07:20:46 192.168.122.209 [54996.645643] [tdb] Close table 'cache0.tdb' Apr 26 07:20:46 192.168.122.209 [54996.876381] [tdb] Close table 'filter0.tdb' Apr 26 07:20:46 192.168.122.209 [54996.876834] [tempesta fw] modules are stopped Apr 26 07:20:46 192.168.122.209 [54997.074149] [tempesta fw] exiting... Apr 26 07:20:46 192.168.122.209 [54997.181717] [tdb] Shutdown Tempesta DB Apr 26 07:20:46 192.168.122.209 [54997.377334] End test: cache.test_cache_control.RequestOnlyIfCached504.test Apr 26 07:20:46 192.168.122.209 [54997.402413] Start test: cache.test_cache_control.RequestOnlyIfCachedCached.test Apr 26 07:20:47 192.168.122.209 [54998.435672] [tdb] Start Tempesta DB Apr 26 07:20:48 192.168.122.209 [54998.587089] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:20:49 192.168.122.209 [55000.093025] [tempesta fw] Configuration processing is completed. Apr 26 07:20:49 192.168.122.209 [55000.147096] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:20:50 192.168.122.209 [55000.560762] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:20:50 192.168.122.209 [55000.587280] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:20:50 192.168.122.209 [55000.614340] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:20:50 192.168.122.209 [55000.657059] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:20:50 192.168.122.209 [55000.697000] [tempesta fw] Tempesta FW is ready Apr 26 07:20:50 192.168.122.209 [55001.307258] [tdb] Close table 'client0.tdb' Apr 26 07:20:50 192.168.122.209 [55001.484063] [tdb] Close table 'sessions0.tdb' Apr 26 07:20:54 192.168.122.209 [55004.726394] [tdb] Close table 'cache0.tdb' Apr 26 07:20:54 192.168.122.209 [55004.953327] [tdb] Close table 'filter0.tdb' Apr 26 07:20:54 192.168.122.209 [55004.953764] [tempesta fw] modules are stopped Apr 26 07:20:54 192.168.122.209 [55005.150238] [tempesta fw] exiting... Apr 26 07:20:54 192.168.122.209 [55005.256943] [tdb] Shutdown Tempesta DB Apr 26 07:20:54 192.168.122.209 [55005.442034] End test: cache.test_cache_control.RequestOnlyIfCachedCached.test Apr 26 07:20:54 192.168.122.209 [55005.466577] Start test: cache.test_cache_control.ResponseForAuthorizationUserMustRevalidateNotCached.test Apr 26 07:20:56 192.168.122.209 [55006.535735] [tdb] Start Tempesta DB Apr 26 07:20:56 192.168.122.209 [55006.677347] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:20:57 192.168.122.209 [55008.201180] [tempesta fw] Configuration processing is completed. Apr 26 07:20:57 192.168.122.209 [55008.256091] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:20:58 192.168.122.209 [55008.692026] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:20:58 192.168.122.209 [55008.718856] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:20:58 192.168.122.209 [55008.745153] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:20:58 192.168.122.209 [55008.789157] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:20:58 192.168.122.209 [55008.829096] [tempesta fw] Tempesta FW is ready Apr 26 07:21:00 192.168.122.209 [55011.460875] [tdb] Close table 'client0.tdb' Apr 26 07:21:01 192.168.122.209 [55011.646462] [tdb] Close table 'sessions0.tdb' Apr 26 07:21:04 192.168.122.209 [55014.878397] [tdb] Close table 'cache0.tdb' Apr 26 07:21:04 192.168.122.209 [55015.114631] [tdb] Close table 'filter0.tdb' Apr 26 07:21:04 192.168.122.209 [55015.115071] [tempesta fw] modules are stopped Apr 26 07:21:04 192.168.122.209 [55015.332776] [tempesta fw] exiting... Apr 26 07:21:04 192.168.122.209 [55015.454745] [tdb] Shutdown Tempesta DB Apr 26 07:21:05 192.168.122.209 [55015.654803] End test: cache.test_cache_control.ResponseForAuthorizationUserMustRevalidateNotCached.test Apr 26 07:21:05 192.168.122.209 [55015.673494] Start test: cache.test_cache_control.ResponseMaxAgeCached.test Apr 26 07:21:06 192.168.122.209 [55016.715423] [tdb] Start Tempesta DB Apr 26 07:21:06 192.168.122.209 [55016.863113] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:21:07 192.168.122.209 [55018.325333] [tempesta fw] Configuration processing is completed. Apr 26 07:21:07 192.168.122.209 [55018.383559] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:21:08 192.168.122.209 [55018.820016] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:21:08 192.168.122.209 [55018.846335] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:21:08 192.168.122.209 [55018.885923] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:21:08 192.168.122.209 [55018.929387] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:21:08 192.168.122.209 [55018.973226] [tempesta fw] Tempesta FW is ready Apr 26 07:21:09 192.168.122.209 [55019.581319] [tdb] Close table 'client0.tdb' Apr 26 07:21:09 192.168.122.209 [55019.862514] [tdb] Close table 'sessions0.tdb' Apr 26 07:21:12 192.168.122.209 [55023.043869] [tdb] Close table 'cache0.tdb' Apr 26 07:21:12 192.168.122.209 [55023.290598] [tdb] Close table 'filter0.tdb' Apr 26 07:21:12 192.168.122.209 [55023.291167] [tempesta fw] modules are stopped Apr 26 07:21:12 192.168.122.209 [55023.465722] [tempesta fw] exiting... Apr 26 07:21:13 192.168.122.209 [55023.598146] [tdb] Shutdown Tempesta DB Apr 26 07:21:13 192.168.122.209 [55023.807752] End test: cache.test_cache_control.ResponseMaxAgeCached.test Apr 26 07:21:13 192.168.122.209 [55023.824083] Start test: cache.test_cache_control.ResponseMaxAgeCached2.test Apr 26 07:21:14 192.168.122.209 [55024.898639] [tdb] Start Tempesta DB Apr 26 07:21:14 192.168.122.209 [55025.055609] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:21:16 192.168.122.209 [55026.569431] [tempesta fw] Configuration processing is completed. Apr 26 07:21:16 192.168.122.209 [55026.619268] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:21:16 192.168.122.209 [55027.044198] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:21:16 192.168.122.209 [55027.070010] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:21:16 192.168.122.209 [55027.095772] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:21:16 192.168.122.209 [55027.133397] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:21:16 192.168.122.209 [55027.181315] [tempesta fw] Tempesta FW is ready Apr 26 07:21:17 192.168.122.209 [55027.782094] [tdb] Close table 'client0.tdb' Apr 26 07:21:17 192.168.122.209 [55027.953896] [tdb] Close table 'sessions0.tdb' Apr 26 07:21:20 192.168.122.209 [55031.098217] [tdb] Close table 'cache0.tdb' Apr 26 07:21:20 192.168.122.209 [55031.352455] [tdb] Close table 'filter0.tdb' Apr 26 07:21:20 192.168.122.209 [55031.352891] [tempesta fw] modules are stopped Apr 26 07:21:21 192.168.122.209 [55031.538191] [tempesta fw] exiting... Apr 26 07:21:21 192.168.122.209 [55031.668582] [tdb] Shutdown Tempesta DB Apr 26 07:21:21 192.168.122.209 [55031.922025] End test: cache.test_cache_control.ResponseMaxAgeCached2.test Apr 26 07:21:21 192.168.122.209 [55031.937607] Start test: cache.test_cache_control.ResponseMaxAgeIgnore.test Apr 26 07:21:22 192.168.122.209 [55033.043106] [tdb] Start Tempesta DB Apr 26 07:21:22 192.168.122.209 [55033.176104] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:21:24 192.168.122.209 [55034.709519] [tempesta fw] Configuration processing is completed. Apr 26 07:21:24 192.168.122.209 [55034.764821] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:21:24 192.168.122.209 [55035.177780] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:21:24 192.168.122.209 [55035.204703] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:21:24 192.168.122.209 [55035.232088] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:21:24 192.168.122.209 [55035.285415] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:21:24 192.168.122.209 [55035.325431] [tempesta fw] Tempesta FW is ready Apr 26 07:21:26 192.168.122.209 [55037.427479] [tdb] Close table 'client0.tdb' Apr 26 07:21:27 192.168.122.209 [55037.618427] [tdb] Close table 'sessions0.tdb' Apr 26 07:21:30 192.168.122.209 [55040.828700] [tdb] Close table 'cache0.tdb' Apr 26 07:21:30 192.168.122.209 [55041.057981] [tdb] Close table 'filter0.tdb' Apr 26 07:21:30 192.168.122.209 [55041.058385] [tempesta fw] modules are stopped Apr 26 07:21:30 192.168.122.209 [55041.275609] [tempesta fw] exiting... Apr 26 07:21:30 192.168.122.209 [55041.373434] [tdb] Shutdown Tempesta DB Apr 26 07:21:31 192.168.122.209 [55041.598874] End test: cache.test_cache_control.ResponseMaxAgeIgnore.test Apr 26 07:21:31 192.168.122.209 [55041.615304] Start test: cache.test_cache_control.ResponseMaxAgeNotCached.test Apr 26 07:21:32 192.168.122.209 [55042.669863] [tdb] Start Tempesta DB Apr 26 07:21:32 192.168.122.209 [55042.816327] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:21:33 192.168.122.209 [55044.413696] [tempesta fw] Configuration processing is completed. Apr 26 07:21:33 192.168.122.209 [55044.472912] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:21:34 192.168.122.209 [55044.895834] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:21:34 192.168.122.209 [55044.931478] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:21:34 192.168.122.209 [55044.957564] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:21:34 192.168.122.209 [55044.997596] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:21:34 192.168.122.209 [55045.037536] [tempesta fw] Tempesta FW is ready Apr 26 07:21:37 192.168.122.209 [55047.641035] [tdb] Close table 'client0.tdb' Apr 26 07:21:37 192.168.122.209 [55047.833525] [tdb] Close table 'sessions0.tdb' Apr 26 07:21:40 192.168.122.209 [55051.071268] [tdb] Close table 'cache0.tdb' Apr 26 07:21:40 192.168.122.209 [55051.312235] [tdb] Close table 'filter0.tdb' Apr 26 07:21:40 192.168.122.209 [55051.312694] [tempesta fw] modules are stopped Apr 26 07:21:40 192.168.122.209 [55051.489787] [tempesta fw] exiting... Apr 26 07:21:41 192.168.122.209 [55051.611399] [tdb] Shutdown Tempesta DB Apr 26 07:21:41 192.168.122.209 [55051.841556] End test: cache.test_cache_control.ResponseMaxAgeNotCached.test Apr 26 07:21:41 192.168.122.209 [55051.861981] Start test: cache.test_cache_control.ResponseMaxAgeNotCached2.test Apr 26 07:21:42 192.168.122.209 [55052.873745] [tdb] Start Tempesta DB Apr 26 07:21:42 192.168.122.209 [55053.013038] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:21:44 192.168.122.209 [55054.565765] [tempesta fw] Configuration processing is completed. Apr 26 07:21:44 192.168.122.209 [55054.616453] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:21:44 192.168.122.209 [55055.032285] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:21:44 192.168.122.209 [55055.059364] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:21:44 192.168.122.209 [55055.086696] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:21:44 192.168.122.209 [55055.125665] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:21:44 192.168.122.209 [55055.169669] [tempesta fw] Tempesta FW is ready Apr 26 07:21:45 192.168.122.209 [55055.801344] [tdb] Close table 'client0.tdb' Apr 26 07:21:45 192.168.122.209 [55055.978378] [tdb] Close table 'sessions0.tdb' Apr 26 07:21:49 192.168.122.209 [55060.070558] [tdb] Close table 'cache0.tdb' Apr 26 07:21:50 192.168.122.209 [55060.856691] [tdb] Close table 'filter0.tdb' Apr 26 07:21:50 192.168.122.209 [55060.857138] [tempesta fw] modules are stopped Apr 26 07:21:52 192.168.122.209 [55062.523704] [tempesta fw] exiting... Apr 26 07:21:52 192.168.122.209 [55063.338183] [tdb] Shutdown Tempesta DB Apr 26 07:21:53 192.168.122.209 [55063.946786] End test: cache.test_cache_control.ResponseMaxAgeNotCached2.test Apr 26 07:21:53 192.168.122.209 [55063.960771] Start test: cache.test_cache_control.ResponseMultipleNoCacheIgnore.test Apr 26 07:21:54 192.168.122.209 [55064.969303] [tdb] Start Tempesta DB Apr 26 07:21:54 192.168.122.209 [55065.100511] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:21:56 192.168.122.209 [55066.721923] [tempesta fw] Configuration processing is completed. Apr 26 07:21:56 192.168.122.209 [55066.772962] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:21:56 192.168.122.209 [55067.204939] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:21:56 192.168.122.209 [55067.231668] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:21:56 192.168.122.209 [55067.258236] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:21:56 192.168.122.209 [55067.297883] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:21:56 192.168.122.209 [55067.345818] [tempesta fw] Tempesta FW is ready Apr 26 07:21:57 192.168.122.209 [55067.938846] [tdb] Close table 'client0.tdb' Apr 26 07:21:57 192.168.122.209 [55068.137407] [tdb] Close table 'sessions0.tdb' Apr 26 07:22:00 192.168.122.209 [55071.338537] [tdb] Close table 'cache0.tdb' Apr 26 07:22:01 192.168.122.209 [55071.556667] [tdb] Close table 'filter0.tdb' Apr 26 07:22:01 192.168.122.209 [55071.557096] [tempesta fw] modules are stopped Apr 26 07:22:01 192.168.122.209 [55071.760792] [tempesta fw] exiting... Apr 26 07:22:01 192.168.122.209 [55071.884386] [tdb] Shutdown Tempesta DB Apr 26 07:22:01 192.168.122.209 [55072.113877] End test: cache.test_cache_control.ResponseMultipleNoCacheIgnore.test Apr 26 07:22:01 192.168.122.209 [55072.133150] Start test: cache.test_cache_control.ResponseMustRevalidateCached.test Apr 26 07:22:02 192.168.122.209 [55073.202427] [tdb] Start Tempesta DB Apr 26 07:22:02 192.168.122.209 [55073.330933] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:22:04 192.168.122.209 [55074.842302] [tempesta fw] Configuration processing is completed. Apr 26 07:22:04 192.168.122.209 [55074.895144] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:22:04 192.168.122.209 [55075.304342] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:22:04 192.168.122.209 [55075.330949] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:22:04 192.168.122.209 [55075.369021] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:22:04 192.168.122.209 [55075.421988] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:22:04 192.168.122.209 [55075.469931] [tempesta fw] Tempesta FW is ready Apr 26 07:22:05 192.168.122.209 [55076.066458] [tdb] Close table 'client0.tdb' Apr 26 07:22:05 192.168.122.209 [55076.250571] [tdb] Close table 'sessions0.tdb' Apr 26 07:22:09 192.168.122.209 [55079.501275] [tdb] Close table 'cache0.tdb' Apr 26 07:22:09 192.168.122.209 [55079.714257] [tdb] Close table 'filter0.tdb' Apr 26 07:22:09 192.168.122.209 [55079.714704] [tempesta fw] modules are stopped Apr 26 07:22:09 192.168.122.209 [55079.908187] [tempesta fw] exiting... Apr 26 07:22:09 192.168.122.209 [55080.019932] [tdb] Shutdown Tempesta DB Apr 26 07:22:09 192.168.122.209 [55080.263171] End test: cache.test_cache_control.ResponseMustRevalidateCached.test Apr 26 07:22:09 192.168.122.209 [55080.276172] Start test: cache.test_cache_control.ResponseMustRevalidateHalfIgnore.test Apr 26 07:22:10 192.168.122.209 [55081.365426] [tdb] Start Tempesta DB Apr 26 07:22:11 192.168.122.209 [55081.516233] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:22:12 192.168.122.209 [55083.054127] [tempesta fw] Configuration processing is completed. Apr 26 07:22:12 192.168.122.209 [55083.105084] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:22:13 192.168.122.209 [55083.537514] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:22:13 192.168.122.209 [55083.565267] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:22:13 192.168.122.209 [55083.591308] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:22:13 192.168.122.209 [55083.678085] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:22:13 192.168.122.209 [55083.725935] [tempesta fw] Tempesta FW is ready Apr 26 07:22:15 192.168.122.209 [55085.835812] [tdb] Close table 'client0.tdb' Apr 26 07:22:15 192.168.122.209 [55086.006716] [tdb] Close table 'sessions0.tdb' Apr 26 07:22:18 192.168.122.209 [55089.184527] [tdb] Close table 'cache0.tdb' Apr 26 07:22:18 192.168.122.209 [55089.408640] [tdb] Close table 'filter0.tdb' Apr 26 07:22:18 192.168.122.209 [55089.409088] [tempesta fw] modules are stopped Apr 26 07:22:19 192.168.122.209 [55089.645027] [tempesta fw] exiting... Apr 26 07:22:19 192.168.122.209 [55089.779475] [tdb] Shutdown Tempesta DB Apr 26 07:22:19 192.168.122.209 [55090.000382] End test: cache.test_cache_control.ResponseMustRevalidateHalfIgnore.test Apr 26 07:22:19 192.168.122.209 [55090.018116] Start test: cache.test_cache_control.ResponseMustRevalidateIgnore.test Apr 26 07:22:20 192.168.122.209 [55091.074958] [tdb] Start Tempesta DB Apr 26 07:22:20 192.168.122.209 [55091.215346] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:22:22 192.168.122.209 [55092.746543] [tempesta fw] Configuration processing is completed. Apr 26 07:22:22 192.168.122.209 [55092.796782] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:22:22 192.168.122.209 [55093.209579] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:22:22 192.168.122.209 [55093.237272] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:22:22 192.168.122.209 [55093.263734] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:22:22 192.168.122.209 [55093.318209] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:22:22 192.168.122.209 [55093.362153] [tempesta fw] Tempesta FW is ready Apr 26 07:22:25 192.168.122.209 [55095.976504] [tdb] Close table 'client0.tdb' Apr 26 07:22:25 192.168.122.209 [55096.160258] [tdb] Close table 'sessions0.tdb' Apr 26 07:22:28 192.168.122.209 [55099.332885] [tdb] Close table 'cache0.tdb' Apr 26 07:22:29 192.168.122.209 [55099.592435] [tdb] Close table 'filter0.tdb' Apr 26 07:22:29 192.168.122.209 [55099.592872] [tempesta fw] modules are stopped Apr 26 07:22:29 192.168.122.209 [55099.778781] [tempesta fw] exiting... Apr 26 07:22:29 192.168.122.209 [55099.932664] [tdb] Shutdown Tempesta DB Apr 26 07:22:29 192.168.122.209 [55100.152188] End test: cache.test_cache_control.ResponseMustRevalidateIgnore.test Apr 26 07:22:29 192.168.122.209 [55100.170807] Start test: cache.test_cache_control.ResponseMustRevalidateMultiIgnore.test Apr 26 07:22:30 192.168.122.209 [55101.244902] [tdb] Start Tempesta DB Apr 26 07:22:30 192.168.122.209 [55101.376108] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:22:32 192.168.122.209 [55102.942329] [tempesta fw] Configuration processing is completed. Apr 26 07:22:32 192.168.122.209 [55102.992945] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:22:32 192.168.122.209 [55103.418430] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:22:32 192.168.122.209 [55103.444907] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:22:32 192.168.122.209 [55103.470973] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:22:33 192.168.122.209 [55103.522317] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:22:33 192.168.122.209 [55103.562288] [tempesta fw] Tempesta FW is ready Apr 26 07:22:35 192.168.122.209 [55105.683633] [tdb] Close table 'client0.tdb' Apr 26 07:22:35 192.168.122.209 [55105.875393] [tdb] Close table 'sessions0.tdb' Apr 26 07:22:38 192.168.122.209 [55109.107822] [tdb] Close table 'cache0.tdb' Apr 26 07:22:38 192.168.122.209 [55109.335149] [tdb] Close table 'filter0.tdb' Apr 26 07:22:38 192.168.122.209 [55109.335590] [tempesta fw] modules are stopped Apr 26 07:22:39 192.168.122.209 [55109.530623] [tempesta fw] exiting... Apr 26 07:22:39 192.168.122.209 [55109.679316] [tdb] Shutdown Tempesta DB Apr 26 07:22:39 192.168.122.209 [55109.920624] End test: cache.test_cache_control.ResponseMustRevalidateMultiIgnore.test Apr 26 07:22:39 192.168.122.209 [55109.933605] Start test: cache.test_cache_control.ResponseMustRevalidateNotCached.test Apr 26 07:22:40 192.168.122.209 [55111.032673] [tdb] Start Tempesta DB Apr 26 07:22:40 192.168.122.209 [55111.166981] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:22:42 192.168.122.209 [55112.686525] [tempesta fw] Configuration processing is completed. Apr 26 07:22:42 192.168.122.209 [55112.737552] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:22:42 192.168.122.209 [55113.161382] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:22:42 192.168.122.209 [55113.188508] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:22:42 192.168.122.209 [55113.216860] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:22:42 192.168.122.209 [55113.258406] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:22:42 192.168.122.209 [55113.302400] [tempesta fw] Tempesta FW is ready Apr 26 07:22:45 192.168.122.209 [55115.900463] [tdb] Close table 'client0.tdb' Apr 26 07:22:45 192.168.122.209 [55116.079344] [tdb] Close table 'sessions0.tdb' Apr 26 07:22:48 192.168.122.209 [55119.291308] [tdb] Close table 'cache0.tdb' Apr 26 07:22:49 192.168.122.209 [55119.520223] [tdb] Close table 'filter0.tdb' Apr 26 07:22:49 192.168.122.209 [55119.520653] [tempesta fw] modules are stopped Apr 26 07:22:49 192.168.122.209 [55119.718536] [tempesta fw] exiting... Apr 26 07:22:49 192.168.122.209 [55119.853363] [tdb] Shutdown Tempesta DB Apr 26 07:22:49 192.168.122.209 [55120.099988] End test: cache.test_cache_control.ResponseMustRevalidateNotCached.test Apr 26 07:22:49 192.168.122.209 [55120.135138] Start test: cache.test_cache_control.ResponseMustRevalidateStaleCached.test Apr 26 07:22:50 192.168.122.209 [55121.192301] [tdb] Start Tempesta DB Apr 26 07:22:50 192.168.122.209 [55121.331889] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:22:52 192.168.122.209 [55122.798619] [tempesta fw] Configuration processing is completed. Apr 26 07:22:52 192.168.122.209 [55122.848848] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:22:52 192.168.122.209 [55123.273083] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:22:52 192.168.122.209 [55123.300002] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:22:52 192.168.122.209 [55123.326698] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:22:52 192.168.122.209 [55123.374603] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:22:52 192.168.122.209 [55123.410539] [tempesta fw] Tempesta FW is ready Apr 26 07:22:53 192.168.122.209 [55124.022788] [tdb] Close table 'client0.tdb' Apr 26 07:22:53 192.168.122.209 [55124.214798] [tdb] Close table 'sessions0.tdb' Apr 26 07:22:56 192.168.122.209 [55127.424054] [tdb] Close table 'cache0.tdb' Apr 26 07:22:57 192.168.122.209 [55127.637534] [tdb] Close table 'filter0.tdb' Apr 26 07:22:57 192.168.122.209 [55127.637977] [tempesta fw] modules are stopped Apr 26 07:22:57 192.168.122.209 [55127.818235] [tempesta fw] exiting... Apr 26 07:22:57 192.168.122.209 [55127.932210] [tdb] Shutdown Tempesta DB Apr 26 07:22:57 192.168.122.209 [55128.135967] End test: cache.test_cache_control.ResponseMustRevalidateStaleCached.test Apr 26 07:22:57 192.168.122.209 [55128.154353] Start test: cache.test_cache_control.ResponseMustRevalidateStaleIgnore.test Apr 26 07:22:58 192.168.122.209 [55129.223004] [tdb] Start Tempesta DB Apr 26 07:22:58 192.168.122.209 [55129.371094] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:23:00 192.168.122.209 [55130.814712] [tempesta fw] Configuration processing is completed. Apr 26 07:23:00 192.168.122.209 [55130.868537] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:23:00 192.168.122.209 [55131.281706] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:23:00 192.168.122.209 [55131.312145] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:23:00 192.168.122.209 [55131.338248] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:23:00 192.168.122.209 [55131.378695] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:23:00 192.168.122.209 [55131.434641] [tempesta fw] Tempesta FW is ready Apr 26 07:23:03 192.168.122.209 [55133.569320] [tdb] Close table 'client0.tdb' Apr 26 07:23:03 192.168.122.209 [55133.757529] [tdb] Close table 'sessions0.tdb' Apr 26 07:23:06 192.168.122.209 [55137.101965] [tdb] Close table 'cache0.tdb' Apr 26 07:23:06 192.168.122.209 [55137.354900] [tdb] Close table 'filter0.tdb' Apr 26 07:23:06 192.168.122.209 [55137.355332] [tempesta fw] modules are stopped Apr 26 07:23:07 192.168.122.209 [55137.544680] [tempesta fw] exiting... Apr 26 07:23:07 192.168.122.209 [55137.656231] [tdb] Shutdown Tempesta DB Apr 26 07:23:07 192.168.122.209 [55137.880635] End test: cache.test_cache_control.ResponseMustRevalidateStaleIgnore.test Apr 26 07:23:07 192.168.122.209 [55137.907468] Start test: cache.test_cache_control.ResponseMustRevalidateStaleNotCached.test Apr 26 07:23:08 192.168.122.209 [55138.989814] [tdb] Start Tempesta DB Apr 26 07:23:08 192.168.122.209 [55139.124161] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:23:10 192.168.122.209 [55140.626834] [tempesta fw] Configuration processing is completed. Apr 26 07:23:10 192.168.122.209 [55140.676829] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:23:10 192.168.122.209 [55141.094157] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:23:10 192.168.122.209 [55141.121797] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:23:10 192.168.122.209 [55141.148566] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:23:10 192.168.122.209 [55141.194812] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:23:10 192.168.122.209 [55141.242750] [tempesta fw] Tempesta FW is ready Apr 26 07:23:13 192.168.122.209 [55143.893893] [tdb] Close table 'client0.tdb' Apr 26 07:23:13 192.168.122.209 [55144.086732] [tdb] Close table 'sessions0.tdb' Apr 26 07:23:16 192.168.122.209 [55147.252909] [tdb] Close table 'cache0.tdb' Apr 26 07:23:17 192.168.122.209 [55147.516569] [tdb] Close table 'filter0.tdb' Apr 26 07:23:17 192.168.122.209 [55147.516987] [tempesta fw] modules are stopped Apr 26 07:23:17 192.168.122.209 [55147.734307] [tempesta fw] exiting... Apr 26 07:23:17 192.168.122.209 [55147.859435] [tdb] Shutdown Tempesta DB Apr 26 07:23:17 192.168.122.209 [55148.056460] End test: cache.test_cache_control.ResponseMustRevalidateStaleNotCached.test Apr 26 07:23:17 192.168.122.209 [55148.066571] Start test: cache.test_cache_control.ResponseNoCache.test Apr 26 07:23:18 192.168.122.209 [55149.130023] [tdb] Start Tempesta DB Apr 26 07:23:18 192.168.122.209 [55149.274630] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:23:20 192.168.122.209 [55150.766966] [tempesta fw] Configuration processing is completed. Apr 26 07:23:20 192.168.122.209 [55150.831437] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:23:20 192.168.122.209 [55151.254440] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:23:20 192.168.122.209 [55151.281443] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:23:20 192.168.122.209 [55151.309526] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:23:20 192.168.122.209 [55151.354963] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:23:20 192.168.122.209 [55151.402892] [tempesta fw] Tempesta FW is ready Apr 26 07:23:21 192.168.122.209 [55151.993460] [tdb] Close table 'client0.tdb' Apr 26 07:23:21 192.168.122.209 [55152.179197] [tdb] Close table 'sessions0.tdb' Apr 26 07:23:24 192.168.122.209 [55155.380282] [tdb] Close table 'cache0.tdb' Apr 26 07:23:25 192.168.122.209 [55155.603427] [tdb] Close table 'filter0.tdb' Apr 26 07:23:25 192.168.122.209 [55155.603860] [tempesta fw] modules are stopped Apr 26 07:23:25 192.168.122.209 [55155.831293] [tempesta fw] exiting... Apr 26 07:23:25 192.168.122.209 [55155.942689] [tdb] Shutdown Tempesta DB Apr 26 07:23:25 192.168.122.209 [55156.174472] End test: cache.test_cache_control.ResponseNoCache.test Apr 26 07:23:25 192.168.122.209 [55156.187233] Start test: cache.test_cache_control.ResponseNoCacheIgnore.test Apr 26 07:23:26 192.168.122.209 [55157.190487] [tdb] Start Tempesta DB Apr 26 07:23:26 192.168.122.209 [55157.342564] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:23:28 192.168.122.209 [55158.859088] [tempesta fw] Configuration processing is completed. Apr 26 07:23:28 192.168.122.209 [55158.909728] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:23:28 192.168.122.209 [55159.346311] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:23:28 192.168.122.209 [55159.373141] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:23:28 192.168.122.209 [55159.403183] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:23:28 192.168.122.209 [55159.451000] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:23:28 192.168.122.209 [55159.494978] [tempesta fw] Tempesta FW is ready Apr 26 07:23:29 192.168.122.209 [55160.095097] [tdb] Close table 'client0.tdb' Apr 26 07:23:29 192.168.122.209 [55160.281294] [tdb] Close table 'sessions0.tdb' Apr 26 07:23:32 192.168.122.209 [55163.452212] [tdb] Close table 'cache0.tdb' Apr 26 07:23:33 192.168.122.209 [55163.730733] [tdb] Close table 'filter0.tdb' Apr 26 07:23:33 192.168.122.209 [55163.731191] [tempesta fw] modules are stopped Apr 26 07:23:33 192.168.122.209 [55163.922559] [tempesta fw] exiting... Apr 26 07:23:33 192.168.122.209 [55164.054596] [tdb] Shutdown Tempesta DB Apr 26 07:23:33 192.168.122.209 [55164.267455] End test: cache.test_cache_control.ResponseNoCacheIgnore.test Apr 26 07:23:33 192.168.122.209 [55164.277887] Start test: cache.test_cache_control.ResponseNoCacheIgnoreMulti.test Apr 26 07:23:34 192.168.122.209 [55165.326273] [tdb] Start Tempesta DB Apr 26 07:23:34 192.168.122.209 [55165.470541] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:23:36 192.168.122.209 [55167.067177] [tempesta fw] Configuration processing is completed. Apr 26 07:23:36 192.168.122.209 [55167.118313] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:23:37 192.168.122.209 [55167.532298] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:23:37 192.168.122.209 [55167.559117] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:23:37 192.168.122.209 [55167.586953] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:23:37 192.168.122.209 [55167.639146] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:23:37 192.168.122.209 [55167.679091] [tempesta fw] Tempesta FW is ready Apr 26 07:23:37 192.168.122.209 [55168.261969] [tdb] Close table 'client0.tdb' Apr 26 07:23:37 192.168.122.209 [55168.446372] [tdb] Close table 'sessions0.tdb' Apr 26 07:23:41 192.168.122.209 [55171.609705] [tdb] Close table 'cache0.tdb' Apr 26 07:23:41 192.168.122.209 [55171.866130] [tdb] Close table 'filter0.tdb' Apr 26 07:23:41 192.168.122.209 [55171.866563] [tempesta fw] modules are stopped Apr 26 07:23:41 192.168.122.209 [55172.057971] [tempesta fw] exiting... Apr 26 07:23:41 192.168.122.209 [55172.186634] [tdb] Shutdown Tempesta DB Apr 26 07:23:41 192.168.122.209 [55172.411620] End test: cache.test_cache_control.ResponseNoCacheIgnoreMulti.test Apr 26 07:23:41 192.168.122.209 [55172.433838] Start test: cache.test_cache_control.ResponseNoStore.test Apr 26 07:23:43 192.168.122.209 [55173.512542] [tdb] Start Tempesta DB Apr 26 07:23:43 192.168.122.209 [55173.661056] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:23:44 192.168.122.209 [55175.179287] [tempesta fw] Configuration processing is completed. Apr 26 07:23:44 192.168.122.209 [55175.230828] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:23:45 192.168.122.209 [55175.663267] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:23:45 192.168.122.209 [55175.690074] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:23:45 192.168.122.209 [55175.717519] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:23:45 192.168.122.209 [55175.779267] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:23:45 192.168.122.209 [55175.819188] [tempesta fw] Tempesta FW is ready Apr 26 07:23:45 192.168.122.209 [55176.449385] [tdb] Close table 'client0.tdb' Apr 26 07:23:46 192.168.122.209 [55176.635029] [tdb] Close table 'sessions0.tdb' Apr 26 07:23:49 192.168.122.209 [55179.825824] [tdb] Close table 'cache0.tdb' Apr 26 07:23:49 192.168.122.209 [55180.079127] [tdb] Close table 'filter0.tdb' Apr 26 07:23:49 192.168.122.209 [55180.079568] [tempesta fw] modules are stopped Apr 26 07:23:49 192.168.122.209 [55180.256969] [tempesta fw] exiting... Apr 26 07:23:49 192.168.122.209 [55180.365828] [tdb] Shutdown Tempesta DB Apr 26 07:23:50 192.168.122.209 [55180.597238] End test: cache.test_cache_control.ResponseNoStore.test Apr 26 07:23:50 192.168.122.209 [55180.621661] Start test: cache.test_cache_control.ResponsePrivate.test Apr 26 07:23:51 192.168.122.209 [55181.634394] [tdb] Start Tempesta DB Apr 26 07:23:51 192.168.122.209 [55181.796496] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:23:52 192.168.122.209 [55183.331685] [tempesta fw] Configuration processing is completed. Apr 26 07:23:52 192.168.122.209 [55183.386006] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:23:53 192.168.122.209 [55183.804267] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:23:53 192.168.122.209 [55183.830786] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:23:53 192.168.122.209 [55183.858424] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:23:53 192.168.122.209 [55183.899346] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:23:53 192.168.122.209 [55183.943235] [tempesta fw] Tempesta FW is ready Apr 26 07:23:54 192.168.122.209 [55184.593750] [tdb] Close table 'client0.tdb' Apr 26 07:23:54 192.168.122.209 [55184.790887] [tdb] Close table 'sessions0.tdb' Apr 26 07:23:57 192.168.122.209 [55187.965962] [tdb] Close table 'cache0.tdb' Apr 26 07:23:57 192.168.122.209 [55188.198647] [tdb] Close table 'filter0.tdb' Apr 26 07:23:57 192.168.122.209 [55188.199087] [tempesta fw] modules are stopped Apr 26 07:23:57 192.168.122.209 [55188.418836] [tempesta fw] exiting... Apr 26 07:23:58 192.168.122.209 [55188.530607] [tdb] Shutdown Tempesta DB Apr 26 07:23:58 192.168.122.209 [55188.759461] End test: cache.test_cache_control.ResponsePrivate.test Apr 26 07:23:58 192.168.122.209 [55188.780217] Start test: cache.test_cache_control.ResponseProxyRevalidateIgnore.test Apr 26 07:23:59 192.168.122.209 [55189.828985] [tdb] Start Tempesta DB Apr 26 07:23:59 192.168.122.209 [55189.983218] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:24:01 192.168.122.209 [55191.599506] [tempesta fw] Configuration processing is completed. Apr 26 07:24:01 192.168.122.209 [55191.649741] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:24:01 192.168.122.209 [55192.064063] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:24:01 192.168.122.209 [55192.090738] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:24:01 192.168.122.209 [55192.117659] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:24:01 192.168.122.209 [55192.199446] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:24:01 192.168.122.209 [55192.239410] [tempesta fw] Tempesta FW is ready Apr 26 07:24:04 192.168.122.209 [55194.860681] [tdb] Close table 'client0.tdb' Apr 26 07:24:04 192.168.122.209 [55195.047641] [tdb] Close table 'sessions0.tdb' Apr 26 07:24:07 192.168.122.209 [55198.253936] [tdb] Close table 'cache0.tdb' Apr 26 07:24:08 192.168.122.209 [55198.500654] [tdb] Close table 'filter0.tdb' Apr 26 07:24:08 192.168.122.209 [55198.501097] [tempesta fw] modules are stopped Apr 26 07:24:08 192.168.122.209 [55198.698238] [tempesta fw] exiting... Apr 26 07:24:08 192.168.122.209 [55198.804251] [tdb] Shutdown Tempesta DB Apr 26 07:24:08 192.168.122.209 [55199.002309] End test: cache.test_cache_control.ResponseProxyRevalidateIgnore.test Apr 26 07:24:08 192.168.122.209 [55199.018371] Start test: cache.test_cache_control.ResponseProxyRevalidateNotCached.test Apr 26 07:24:09 192.168.122.209 [55200.090920] [tdb] Start Tempesta DB Apr 26 07:24:09 192.168.122.209 [55200.230790] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:24:11 192.168.122.209 [55201.647616] [tempesta fw] Configuration processing is completed. Apr 26 07:24:11 192.168.122.209 [55201.699870] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:24:11 192.168.122.209 [55202.123077] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:24:11 192.168.122.209 [55202.151021] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:24:11 192.168.122.209 [55202.176767] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:24:11 192.168.122.209 [55202.223575] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:24:11 192.168.122.209 [55202.267562] [tempesta fw] Tempesta FW is ready Apr 26 07:24:14 192.168.122.209 [55204.881977] [tdb] Close table 'client0.tdb' Apr 26 07:24:14 192.168.122.209 [55205.066537] [tdb] Close table 'sessions0.tdb' Apr 26 07:24:17 192.168.122.209 [55208.248409] [tdb] Close table 'cache0.tdb' Apr 26 07:24:17 192.168.122.209 [55208.473733] [tdb] Close table 'filter0.tdb' Apr 26 07:24:17 192.168.122.209 [55208.474174] [tempesta fw] modules are stopped Apr 26 07:24:18 192.168.122.209 [55208.740497] [tempesta fw] exiting... Apr 26 07:24:18 192.168.122.209 [55208.861478] [tdb] Shutdown Tempesta DB Apr 26 07:24:18 192.168.122.209 [55209.068715] End test: cache.test_cache_control.ResponseProxyRevalidateNotCached.test Apr 26 07:24:18 192.168.122.209 [55209.086757] Start test: cache.test_cache_control.ResponseProxyRevalidateStaleIgnore.test Apr 26 07:24:19 192.168.122.209 [55210.211283] [tdb] Start Tempesta DB Apr 26 07:24:19 192.168.122.209 [55210.348257] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:24:21 192.168.122.209 [55211.903739] [tempesta fw] Configuration processing is completed. Apr 26 07:24:21 192.168.122.209 [55211.955980] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:24:21 192.168.122.209 [55212.376413] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:24:21 192.168.122.209 [55212.402983] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:24:21 192.168.122.209 [55212.430223] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:24:21 192.168.122.209 [55212.483748] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:24:22 192.168.122.209 [55212.535656] [tempesta fw] Tempesta FW is ready Apr 26 07:24:24 192.168.122.209 [55215.193432] [tdb] Close table 'client0.tdb' Apr 26 07:24:24 192.168.122.209 [55215.396645] [tdb] Close table 'sessions0.tdb' Apr 26 07:24:28 192.168.122.209 [55218.625758] [tdb] Close table 'cache0.tdb' Apr 26 07:24:28 192.168.122.209 [55218.893576] [tdb] Close table 'filter0.tdb' Apr 26 07:24:28 192.168.122.209 [55218.893999] [tempesta fw] modules are stopped Apr 26 07:24:28 192.168.122.209 [55219.067372] [tempesta fw] exiting... Apr 26 07:24:28 192.168.122.209 [55219.203334] [tdb] Shutdown Tempesta DB Apr 26 07:24:28 192.168.122.209 [55219.406717] End test: cache.test_cache_control.ResponseProxyRevalidateStaleIgnore.test Apr 26 07:24:28 192.168.122.209 [55219.423073] Start test: cache.test_cache_control.ResponseProxyRevalidateStaleNotCached.test Apr 26 07:24:29 192.168.122.209 [55220.424644] [tdb] Start Tempesta DB Apr 26 07:24:30 192.168.122.209 [55220.556446] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:24:31 192.168.122.209 [55222.087865] [tempesta fw] Configuration processing is completed. Apr 26 07:24:31 192.168.122.209 [55222.139358] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:24:32 192.168.122.209 [55222.556706] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:24:32 192.168.122.209 [55222.583665] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:24:32 192.168.122.209 [55222.609477] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:24:32 192.168.122.209 [55222.651834] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:24:32 192.168.122.209 [55222.691796] [tempesta fw] Tempesta FW is ready Apr 26 07:24:34 192.168.122.209 [55225.320578] [tdb] Close table 'client0.tdb' Apr 26 07:24:35 192.168.122.209 [55225.506335] [tdb] Close table 'sessions0.tdb' Apr 26 07:24:38 192.168.122.209 [55228.695561] [tdb] Close table 'cache0.tdb' Apr 26 07:24:38 192.168.122.209 [55228.922685] [tdb] Close table 'filter0.tdb' Apr 26 07:24:38 192.168.122.209 [55228.923129] [tempesta fw] modules are stopped Apr 26 07:24:38 192.168.122.209 [55229.129738] [tempesta fw] exiting... Apr 26 07:24:38 192.168.122.209 [55229.253523] [tdb] Shutdown Tempesta DB Apr 26 07:24:38 192.168.122.209 [55229.469002] End test: cache.test_cache_control.ResponseProxyRevalidateStaleNotCached.test Apr 26 07:24:38 192.168.122.209 [55229.485333] Start test: cache.test_cache_control.ResponsePublicCached.test Apr 26 07:24:40 192.168.122.209 [55230.539490] [tdb] Start Tempesta DB Apr 26 07:24:40 192.168.122.209 [55230.666297] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:24:41 192.168.122.209 [55232.259985] [tempesta fw] Configuration processing is completed. Apr 26 07:24:41 192.168.122.209 [55232.309026] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:24:42 192.168.122.209 [55232.729882] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:24:42 192.168.122.209 [55232.756445] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:24:42 192.168.122.209 [55232.783735] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:24:42 192.168.122.209 [55232.847953] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:24:42 192.168.122.209 [55232.891926] [tempesta fw] Tempesta FW is ready Apr 26 07:24:42 192.168.122.209 [55233.496685] [tdb] Close table 'client0.tdb' Apr 26 07:24:43 192.168.122.209 [55233.683384] [tdb] Close table 'sessions0.tdb' Apr 26 07:24:46 192.168.122.209 [55236.966131] [tdb] Close table 'cache0.tdb' Apr 26 07:24:46 192.168.122.209 [55237.234369] [tdb] Close table 'filter0.tdb' Apr 26 07:24:46 192.168.122.209 [55237.234807] [tempesta fw] modules are stopped Apr 26 07:24:46 192.168.122.209 [55237.433023] [tempesta fw] exiting... Apr 26 07:24:47 192.168.122.209 [55237.548774] [tdb] Shutdown Tempesta DB Apr 26 07:24:47 192.168.122.209 [55237.772250] End test: cache.test_cache_control.ResponsePublicCached.test Apr 26 07:24:47 192.168.122.209 [55237.792286] Start test: cache.test_cache_control.ResponsePublicCached2.test Apr 26 07:24:48 192.168.122.209 [55238.717602] [tdb] Start Tempesta DB Apr 26 07:24:48 192.168.122.209 [55238.877581] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:24:49 192.168.122.209 [55240.400109] [tempesta fw] Configuration processing is completed. Apr 26 07:24:49 192.168.122.209 [55240.450923] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:24:50 192.168.122.209 [55240.888566] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:24:50 192.168.122.209 [55240.917292] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:24:50 192.168.122.209 [55240.946354] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:24:50 192.168.122.209 [55240.988061] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:24:50 192.168.122.209 [55241.028008] [tempesta fw] Tempesta FW is ready Apr 26 07:24:51 192.168.122.209 [55241.608645] [tdb] Close table 'client0.tdb' Apr 26 07:24:51 192.168.122.209 [55241.803759] [tdb] Close table 'sessions0.tdb' Apr 26 07:24:54 192.168.122.209 [55245.039241] [tdb] Close table 'cache0.tdb' Apr 26 07:24:54 192.168.122.209 [55245.293135] [tdb] Close table 'filter0.tdb' Apr 26 07:24:54 192.168.122.209 [55245.293576] [tempesta fw] modules are stopped Apr 26 07:24:55 192.168.122.209 [55245.519287] [tempesta fw] exiting... Apr 26 07:24:55 192.168.122.209 [55245.630176] [tdb] Shutdown Tempesta DB Apr 26 07:24:55 192.168.122.209 [55245.864257] End test: cache.test_cache_control.ResponsePublicCached2.test Apr 26 07:24:55 192.168.122.209 [55245.875182] Start test: cache.test_cache_control.ResponsePublicIgnore.test Apr 26 07:24:56 192.168.122.209 [55246.943688] [tdb] Start Tempesta DB Apr 26 07:24:56 192.168.122.209 [55247.096246] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:24:57 192.168.122.209 [55248.488195] [tempesta fw] Configuration processing is completed. Apr 26 07:24:58 192.168.122.209 [55248.540822] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:24:58 192.168.122.209 [55248.970914] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:24:58 192.168.122.209 [55248.998381] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:24:58 192.168.122.209 [55249.025302] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:24:58 192.168.122.209 [55249.068181] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:24:58 192.168.122.209 [55249.108125] [tempesta fw] Tempesta FW is ready Apr 26 07:24:59 192.168.122.209 [55249.746473] [tdb] Close table 'client0.tdb' Apr 26 07:24:59 192.168.122.209 [55249.921029] [tdb] Close table 'sessions0.tdb' Apr 26 07:25:02 192.168.122.209 [55253.215319] [tdb] Close table 'cache0.tdb' Apr 26 07:25:02 192.168.122.209 [55253.437586] [tdb] Close table 'filter0.tdb' Apr 26 07:25:02 192.168.122.209 [55253.438026] [tempesta fw] modules are stopped Apr 26 07:25:03 192.168.122.209 [55253.643646] [tempesta fw] exiting... Apr 26 07:25:03 192.168.122.209 [55253.765714] [tdb] Shutdown Tempesta DB Apr 26 07:25:03 192.168.122.209 [55253.973654] End test: cache.test_cache_control.ResponsePublicIgnore.test Apr 26 07:25:03 192.168.122.209 [55253.990998] Start test: cache.test_cache_control.ResponsePublicIgnore2.test Apr 26 07:25:04 192.168.122.209 [55255.052991] [tdb] Start Tempesta DB Apr 26 07:25:04 192.168.122.209 [55255.202159] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:25:06 192.168.122.209 [55256.788320] [tempesta fw] Configuration processing is completed. Apr 26 07:25:06 192.168.122.209 [55256.840644] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:25:06 192.168.122.209 [55257.302110] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:25:06 192.168.122.209 [55257.331343] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:25:06 192.168.122.209 [55257.370457] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:25:06 192.168.122.209 [55257.428265] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:25:06 192.168.122.209 [55257.468227] [tempesta fw] Tempesta FW is ready Apr 26 07:25:07 192.168.122.209 [55258.095211] [tdb] Close table 'client0.tdb' Apr 26 07:25:07 192.168.122.209 [55258.283349] [tdb] Close table 'sessions0.tdb' Apr 26 07:25:11 192.168.122.209 [55261.563678] [tdb] Close table 'cache0.tdb' Apr 26 07:25:11 192.168.122.209 [55261.839707] [tdb] Close table 'filter0.tdb' Apr 26 07:25:11 192.168.122.209 [55261.840200] [tempesta fw] modules are stopped Apr 26 07:25:11 192.168.122.209 [55262.026689] [tempesta fw] exiting... Apr 26 07:25:11 192.168.122.209 [55262.181151] [tdb] Shutdown Tempesta DB Apr 26 07:25:11 192.168.122.209 [55262.423452] End test: cache.test_cache_control.ResponsePublicIgnore2.test Apr 26 07:25:11 192.168.122.209 [55262.441418] Start test: cache.test_cache_control.ResponsePublicNotCached.test Apr 26 07:25:13 192.168.122.209 [55263.538483] [tdb] Start Tempesta DB Apr 26 07:25:13 192.168.122.209 [55263.690025] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:25:14 192.168.122.209 [55265.176453] [tempesta fw] Configuration processing is completed. Apr 26 07:25:14 192.168.122.209 [55265.234469] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:25:15 192.168.122.209 [55265.727240] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:25:15 192.168.122.209 [55265.759223] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:25:15 192.168.122.209 [55265.790655] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:25:15 192.168.122.209 [55265.836332] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:25:15 192.168.122.209 [55265.880328] [tempesta fw] Tempesta FW is ready Apr 26 07:25:15 192.168.122.209 [55266.466860] [tdb] Close table 'client0.tdb' Apr 26 07:25:16 192.168.122.209 [55266.650673] [tdb] Close table 'sessions0.tdb' Apr 26 07:25:19 192.168.122.209 [55269.840691] [tdb] Close table 'cache0.tdb' Apr 26 07:25:19 192.168.122.209 [55270.090242] [tdb] Close table 'filter0.tdb' Apr 26 07:25:19 192.168.122.209 [55270.090674] [tempesta fw] modules are stopped Apr 26 07:25:19 192.168.122.209 [55270.280440] [tempesta fw] exiting... Apr 26 07:25:19 192.168.122.209 [55270.379589] [tdb] Shutdown Tempesta DB Apr 26 07:25:20 192.168.122.209 [55270.606142] End test: cache.test_cache_control.ResponsePublicNotCached.test Apr 26 07:25:20 192.168.122.209 [55270.624731] Start test: cache.test_cache_control.ResponseSMaxageCached.test Apr 26 07:25:21 192.168.122.209 [55271.663727] [tdb] Start Tempesta DB Apr 26 07:25:21 192.168.122.209 [55271.798917] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:25:22 192.168.122.209 [55273.324511] [tempesta fw] Configuration processing is completed. Apr 26 07:25:22 192.168.122.209 [55273.378716] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:25:23 192.168.122.209 [55273.798110] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:25:23 192.168.122.209 [55273.824534] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:25:23 192.168.122.209 [55273.851552] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:25:23 192.168.122.209 [55273.908474] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:25:23 192.168.122.209 [55273.952416] [tempesta fw] Tempesta FW is ready Apr 26 07:25:24 192.168.122.209 [55274.501499] [tdb] Close table 'client0.tdb' Apr 26 07:25:24 192.168.122.209 [55274.673545] [tdb] Close table 'sessions0.tdb' Apr 26 07:25:27 192.168.122.209 [55277.899861] [tdb] Close table 'cache0.tdb' Apr 26 07:25:27 192.168.122.209 [55278.175283] [tdb] Close table 'filter0.tdb' Apr 26 07:25:27 192.168.122.209 [55278.175712] [tempesta fw] modules are stopped Apr 26 07:25:27 192.168.122.209 [55278.413144] [tempesta fw] exiting... Apr 26 07:25:28 192.168.122.209 [55278.517104] [tdb] Shutdown Tempesta DB Apr 26 07:25:28 192.168.122.209 [55278.738812] End test: cache.test_cache_control.ResponseSMaxageCached.test Apr 26 07:25:28 192.168.122.209 [55278.764139] Start test: cache.test_cache_control.ResponseSMaxageIgnore.test Apr 26 07:25:29 192.168.122.209 [55279.774095] [tdb] Start Tempesta DB Apr 26 07:25:29 192.168.122.209 [55279.921971] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:25:30 192.168.122.209 [55281.488684] [tempesta fw] Configuration processing is completed. Apr 26 07:25:31 192.168.122.209 [55281.548802] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:25:31 192.168.122.209 [55282.039877] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:25:31 192.168.122.209 [55282.072722] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:25:31 192.168.122.209 [55282.105335] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:25:31 192.168.122.209 [55282.148573] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:25:31 192.168.122.209 [55282.188524] [tempesta fw] Tempesta FW is ready Apr 26 07:25:33 192.168.122.209 [55284.296036] [tdb] Close table 'client0.tdb' Apr 26 07:25:33 192.168.122.209 [55284.479958] [tdb] Close table 'sessions0.tdb' Apr 26 07:25:37 192.168.122.209 [55287.732142] [tdb] Close table 'cache0.tdb' Apr 26 07:25:37 192.168.122.209 [55287.997021] [tdb] Close table 'filter0.tdb' Apr 26 07:25:37 192.168.122.209 [55287.997458] [tempesta fw] modules are stopped Apr 26 07:25:37 192.168.122.209 [55288.190249] [tempesta fw] exiting... Apr 26 07:25:37 192.168.122.209 [55288.301848] [tdb] Shutdown Tempesta DB Apr 26 07:25:38 192.168.122.209 [55288.504850] End test: cache.test_cache_control.ResponseSMaxageIgnore.test Apr 26 07:25:38 192.168.122.209 [55288.529580] Start test: cache.test_cache_control.ResponseSMaxageMaxAgeIgnore.test Apr 26 07:25:39 192.168.122.209 [55289.587995] [tdb] Start Tempesta DB Apr 26 07:25:39 192.168.122.209 [55289.739220] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:25:40 192.168.122.209 [55291.224748] [tempesta fw] Configuration processing is completed. Apr 26 07:25:40 192.168.122.209 [55291.278632] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:25:41 192.168.122.209 [55291.698691] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:25:41 192.168.122.209 [55291.742412] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:25:41 192.168.122.209 [55291.769487] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:25:41 192.168.122.209 [55291.816732] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:25:41 192.168.122.209 [55291.856643] [tempesta fw] Tempesta FW is ready Apr 26 07:25:43 192.168.122.209 [55293.945389] [tdb] Close table 'client0.tdb' Apr 26 07:25:43 192.168.122.209 [55294.131127] [tdb] Close table 'sessions0.tdb' Apr 26 07:25:46 192.168.122.209 [55297.411479] [tdb] Close table 'cache0.tdb' Apr 26 07:25:47 192.168.122.209 [55297.659019] [tdb] Close table 'filter0.tdb' Apr 26 07:25:47 192.168.122.209 [55297.659455] [tempesta fw] modules are stopped Apr 26 07:25:47 192.168.122.209 [55297.840101] [tempesta fw] exiting... Apr 26 07:25:47 192.168.122.209 [55297.988001] [tdb] Shutdown Tempesta DB Apr 26 07:25:47 192.168.122.209 [55298.196985] End test: cache.test_cache_control.ResponseSMaxageMaxAgeIgnore.test Apr 26 07:25:47 192.168.122.209 [55298.219806] Start test: cache.test_cache_control.ResponseSMaxageMaxAgeNotCached.test Apr 26 07:25:48 192.168.122.209 [55299.252096] [tdb] Start Tempesta DB Apr 26 07:25:48 192.168.122.209 [55299.404595] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:25:50 192.168.122.209 [55300.945294] [tempesta fw] Configuration processing is completed. Apr 26 07:25:50 192.168.122.209 [55300.994907] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:25:50 192.168.122.209 [55301.413914] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:25:50 192.168.122.209 [55301.440747] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:25:50 192.168.122.209 [55301.466266] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:25:51 192.168.122.209 [55301.512819] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:25:51 192.168.122.209 [55301.552774] [tempesta fw] Tempesta FW is ready Apr 26 07:25:53 192.168.122.209 [55304.219498] [tdb] Close table 'client0.tdb' Apr 26 07:25:53 192.168.122.209 [55304.411789] [tdb] Close table 'sessions0.tdb' Apr 26 07:25:57 192.168.122.209 [55307.652703] [tdb] Close table 'cache0.tdb' Apr 26 07:25:57 192.168.122.209 [55307.958083] [tdb] Close table 'filter0.tdb' Apr 26 07:25:57 192.168.122.209 [55307.958535] [tempesta fw] modules are stopped Apr 26 07:25:57 192.168.122.209 [55308.141302] [tempesta fw] exiting... Apr 26 07:25:57 192.168.122.209 [55308.272454] [tdb] Shutdown Tempesta DB Apr 26 07:25:57 192.168.122.209 [55308.466715] End test: cache.test_cache_control.ResponseSMaxageMaxAgeNotCached.test Apr 26 07:25:57 192.168.122.209 [55308.492467] Start test: cache.test_cache_control.ResponseSMaxageNotCached.test Apr 26 07:25:58 192.168.122.209 [55309.490658] [tdb] Start Tempesta DB Apr 26 07:25:59 192.168.122.209 [55309.620071] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:26:00 192.168.122.209 [55311.145002] [tempesta fw] Configuration processing is completed. Apr 26 07:26:00 192.168.122.209 [55311.196985] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:26:01 192.168.122.209 [55311.618961] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:26:01 192.168.122.209 [55311.645479] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:26:01 192.168.122.209 [55311.672966] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:26:01 192.168.122.209 [55311.732960] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:26:01 192.168.122.209 [55311.776916] [tempesta fw] Tempesta FW is ready Apr 26 07:26:03 192.168.122.209 [55314.397567] [tdb] Close table 'client0.tdb' Apr 26 07:26:04 192.168.122.209 [55314.583178] [tdb] Close table 'sessions0.tdb' Apr 26 07:26:07 192.168.122.209 [55317.855523] [tdb] Close table 'cache0.tdb' Apr 26 07:26:07 192.168.122.209 [55318.117753] [tdb] Close table 'filter0.tdb' Apr 26 07:26:07 192.168.122.209 [55318.118296] [tempesta fw] modules are stopped Apr 26 07:26:07 192.168.122.209 [55318.308133] [tempesta fw] exiting... Apr 26 07:26:07 192.168.122.209 [55318.426994] [tdb] Shutdown Tempesta DB Apr 26 07:26:08 192.168.122.209 [55318.651959] End test: cache.test_cache_control.ResponseSMaxageNotCached.test Apr 26 07:26:08 192.168.122.209 [55318.665251] Start test: cache.test_cache_control.ResponseSMaxageNotCached2.test Apr 26 07:26:09 192.168.122.209 [55319.708554] [tdb] Start Tempesta DB Apr 26 07:26:09 192.168.122.209 [55319.869819] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:26:10 192.168.122.209 [55321.341161] [tempesta fw] Configuration processing is completed. Apr 26 07:26:10 192.168.122.209 [55321.391904] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:26:11 192.168.122.209 [55321.820118] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:26:11 192.168.122.209 [55321.856723] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:26:11 192.168.122.209 [55321.884291] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:26:11 192.168.122.209 [55321.929077] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:26:11 192.168.122.209 [55321.977024] [tempesta fw] Tempesta FW is ready Apr 26 07:26:14 192.168.122.209 [55324.600255] [tdb] Close table 'client0.tdb' Apr 26 07:26:14 192.168.122.209 [55324.793297] [tdb] Close table 'sessions0.tdb' Apr 26 07:26:17 192.168.122.209 [55328.039671] [tdb] Close table 'cache0.tdb' Apr 26 07:26:17 192.168.122.209 [55328.299033] [tdb] Close table 'filter0.tdb' Apr 26 07:26:17 192.168.122.209 [55328.299471] [tempesta fw] modules are stopped Apr 26 07:26:18 192.168.122.209 [55328.508448] [tempesta fw] exiting... Apr 26 07:26:18 192.168.122.209 [55328.679327] [tdb] Shutdown Tempesta DB Apr 26 07:26:18 192.168.122.209 [55328.893520] End test: cache.test_cache_control.ResponseSMaxageNotCached2.test Apr 26 07:26:18 192.168.122.209 [55328.909235] Start test: cache.test_cache_control.ResponseStaleCached.test Apr 26 07:26:19 192.168.122.209 [55329.922790] [tdb] Start Tempesta DB Apr 26 07:26:19 192.168.122.209 [55330.061914] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:26:21 192.168.122.209 [55331.581258] [tempesta fw] Configuration processing is completed. Apr 26 07:26:21 192.168.122.209 [55331.634230] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:26:21 192.168.122.209 [55332.055619] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:26:21 192.168.122.209 [55332.082845] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:26:21 192.168.122.209 [55332.111249] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:26:21 192.168.122.209 [55332.157214] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:26:21 192.168.122.209 [55332.197163] [tempesta fw] Tempesta FW is ready Apr 26 07:26:23 192.168.122.209 [55334.326601] [tdb] Close table 'client0.tdb' Apr 26 07:26:24 192.168.122.209 [55334.517128] [tdb] Close table 'sessions0.tdb' Apr 26 07:26:27 192.168.122.209 [55337.750749] [tdb] Close table 'cache0.tdb' Apr 26 07:26:27 192.168.122.209 [55337.991208] [tdb] Close table 'filter0.tdb' Apr 26 07:26:27 192.168.122.209 [55337.991636] [tempesta fw] modules are stopped Apr 26 07:26:27 192.168.122.209 [55338.169281] [tempesta fw] exiting... Apr 26 07:26:27 192.168.122.209 [55338.315711] [tdb] Shutdown Tempesta DB Apr 26 07:26:28 192.168.122.209 [55338.565441] End test: cache.test_cache_control.ResponseStaleCached.test Apr 26 07:26:28 192.168.122.209 [55338.578639] Start test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsDefaultCache.test Apr 26 07:26:29 192.168.122.209 [55339.604428] [tdb] Start Tempesta DB Apr 26 07:26:29 192.168.122.209 [55339.744331] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:26:30 192.168.122.209 [55341.201357] [tempesta fw] Configuration processing is completed. Apr 26 07:26:30 192.168.122.209 [55341.252554] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:26:31 192.168.122.209 [55341.667884] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:26:31 192.168.122.209 [55341.694459] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:26:31 192.168.122.209 [55341.721596] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:26:31 192.168.122.209 [55341.793559] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:26:31 192.168.122.209 [55341.841281] [tempesta fw] Tempesta FW is ready Apr 26 07:26:31 192.168.122.209 [55342.439134] [tdb] Close table 'client0.tdb' Apr 26 07:26:32 192.168.122.209 [55342.610888] [tdb] Close table 'sessions0.tdb' Apr 26 07:26:35 192.168.122.209 [55345.826744] [tdb] Close table 'cache0.tdb' Apr 26 07:26:35 192.168.122.209 [55346.070250] [tdb] Close table 'filter0.tdb' Apr 26 07:26:35 192.168.122.209 [55346.070701] [tempesta fw] modules are stopped Apr 26 07:26:35 192.168.122.209 [55346.253693] [tempesta fw] exiting... Apr 26 07:26:35 192.168.122.209 [55346.373212] [tdb] Shutdown Tempesta DB Apr 26 07:26:36 192.168.122.209 [55346.605753] End test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsDefaultCache.test Apr 26 07:26:36 192.168.122.209 [55346.618941] Start test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsMaxAgeCache.test Apr 26 07:26:37 192.168.122.209 [55347.665325] [tdb] Start Tempesta DB Apr 26 07:26:37 192.168.122.209 [55347.806320] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:26:38 192.168.122.209 [55349.321465] [tempesta fw] Configuration processing is completed. Apr 26 07:26:38 192.168.122.209 [55349.379341] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:26:39 192.168.122.209 [55349.797101] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:26:39 192.168.122.209 [55349.823581] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:26:39 192.168.122.209 [55349.849936] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:26:39 192.168.122.209 [55349.893442] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:26:39 192.168.122.209 [55349.933388] [tempesta fw] Tempesta FW is ready Apr 26 07:26:40 192.168.122.209 [55350.537838] [tdb] Close table 'client0.tdb' Apr 26 07:26:40 192.168.122.209 [55350.731007] [tdb] Close table 'sessions0.tdb' Apr 26 07:26:43 192.168.122.209 [55353.973607] [tdb] Close table 'cache0.tdb' Apr 26 07:26:43 192.168.122.209 [55354.211729] [tdb] Close table 'filter0.tdb' Apr 26 07:26:43 192.168.122.209 [55354.212177] [tempesta fw] modules are stopped Apr 26 07:26:43 192.168.122.209 [55354.430410] [tempesta fw] exiting... Apr 26 07:26:44 192.168.122.209 [55354.545446] [tdb] Shutdown Tempesta DB Apr 26 07:26:44 192.168.122.209 [55354.739827] End test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsMaxAgeCache.test Apr 26 07:26:44 192.168.122.209 [55354.752049] Start test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsMustRevalidateCache2.test Apr 26 07:26:45 192.168.122.209 [55355.864847] [tdb] Start Tempesta DB Apr 26 07:26:45 192.168.122.209 [55355.999815] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:26:46 192.168.122.209 [55357.453578] [tempesta fw] Configuration processing is completed. Apr 26 07:26:47 192.168.122.209 [55357.507273] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:26:47 192.168.122.209 [55357.931855] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:26:47 192.168.122.209 [55357.958676] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:26:47 192.168.122.209 [55357.986286] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:26:47 192.168.122.209 [55358.045519] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:26:47 192.168.122.209 [55358.085488] [tempesta fw] Tempesta FW is ready Apr 26 07:26:48 192.168.122.209 [55358.710109] [tdb] Close table 'client0.tdb' Apr 26 07:26:48 192.168.122.209 [55358.898116] [tdb] Close table 'sessions0.tdb' Apr 26 07:26:51 192.168.122.209 [55362.126546] [tdb] Close table 'cache0.tdb' Apr 26 07:26:51 192.168.122.209 [55362.372315] [tdb] Close table 'filter0.tdb' Apr 26 07:26:51 192.168.122.209 [55362.372737] [tempesta fw] modules are stopped Apr 26 07:26:52 192.168.122.209 [55362.561017] [tempesta fw] exiting... Apr 26 07:26:52 192.168.122.209 [55362.683071] [tdb] Shutdown Tempesta DB Apr 26 07:26:52 192.168.122.209 [55362.917112] End test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsMustRevalidateCache2.test Apr 26 07:26:52 192.168.122.209 [55362.936934] Start test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsNoCacheCache.test Apr 26 07:26:53 192.168.122.209 [55364.008382] [tdb] Start Tempesta DB Apr 26 07:26:53 192.168.122.209 [55364.149260] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:26:55 192.168.122.209 [55365.573691] [tempesta fw] Configuration processing is completed. Apr 26 07:26:55 192.168.122.209 [55365.624534] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:26:55 192.168.122.209 [55366.055291] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:26:55 192.168.122.209 [55366.081301] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:26:55 192.168.122.209 [55366.107264] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:26:55 192.168.122.209 [55366.149640] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:26:55 192.168.122.209 [55366.189590] [tempesta fw] Tempesta FW is ready Apr 26 07:26:56 192.168.122.209 [55366.798618] [tdb] Close table 'client0.tdb' Apr 26 07:26:56 192.168.122.209 [55366.981258] [tdb] Close table 'sessions0.tdb' Apr 26 07:26:59 192.168.122.209 [55370.146389] [tdb] Close table 'cache0.tdb' Apr 26 07:26:59 192.168.122.209 [55370.389050] [tdb] Close table 'filter0.tdb' Apr 26 07:26:59 192.168.122.209 [55370.389529] [tempesta fw] modules are stopped Apr 26 07:27:00 192.168.122.209 [55370.594731] [tempesta fw] exiting... Apr 26 07:27:00 192.168.122.209 [55370.705816] [tdb] Shutdown Tempesta DB Apr 26 07:27:00 192.168.122.209 [55370.923823] End test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsNoCacheCache.test Apr 26 07:27:00 192.168.122.209 [55370.936899] Start test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsNoStoreCache.test Apr 26 07:27:01 192.168.122.209 [55372.048622] [tdb] Start Tempesta DB Apr 26 07:27:01 192.168.122.209 [55372.187323] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:27:03 192.168.122.209 [55373.649803] [tempesta fw] Configuration processing is completed. Apr 26 07:27:03 192.168.122.209 [55373.704428] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:27:03 192.168.122.209 [55374.131414] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:27:03 192.168.122.209 [55374.158429] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:27:03 192.168.122.209 [55374.186051] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:27:03 192.168.122.209 [55374.233708] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:27:03 192.168.122.209 [55374.281685] [tempesta fw] Tempesta FW is ready Apr 26 07:27:04 192.168.122.209 [55374.943886] [tdb] Close table 'client0.tdb' Apr 26 07:27:04 192.168.122.209 [55375.141452] [tdb] Close table 'sessions0.tdb' Apr 26 07:27:07 192.168.122.209 [55378.406850] [tdb] Close table 'cache0.tdb' Apr 26 07:27:08 192.168.122.209 [55378.674656] [tdb] Close table 'filter0.tdb' Apr 26 07:27:08 192.168.122.209 [55378.675091] [tempesta fw] modules are stopped Apr 26 07:27:08 192.168.122.209 [55378.850730] [tempesta fw] exiting... Apr 26 07:27:08 192.168.122.209 [55378.955388] [tdb] Shutdown Tempesta DB Apr 26 07:27:08 192.168.122.209 [55379.196585] End test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsNoStoreCache.test Apr 26 07:27:08 192.168.122.209 [55379.218959] Start test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsNoTransformCache.test Apr 26 07:27:09 192.168.122.209 [55380.342668] [tdb] Start Tempesta DB Apr 26 07:27:09 192.168.122.209 [55380.479620] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:27:11 192.168.122.209 [55381.981987] [tempesta fw] Configuration processing is completed. Apr 26 07:27:11 192.168.122.209 [55382.032758] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:27:11 192.168.122.209 [55382.457763] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:27:11 192.168.122.209 [55382.497208] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:27:12 192.168.122.209 [55382.523534] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:27:12 192.168.122.209 [55382.561830] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:27:12 192.168.122.209 [55382.609782] [tempesta fw] Tempesta FW is ready Apr 26 07:27:12 192.168.122.209 [55383.260067] [tdb] Close table 'client0.tdb' Apr 26 07:27:12 192.168.122.209 [55383.447674] [tdb] Close table 'sessions0.tdb' Apr 26 07:27:16 192.168.122.209 [55386.744251] [tdb] Close table 'cache0.tdb' Apr 26 07:27:16 192.168.122.209 [55386.985251] [tdb] Close table 'filter0.tdb' Apr 26 07:27:16 192.168.122.209 [55386.985698] [tempesta fw] modules are stopped Apr 26 07:27:16 192.168.122.209 [55387.208908] [tempesta fw] exiting... Apr 26 07:27:16 192.168.122.209 [55387.341015] [tdb] Shutdown Tempesta DB Apr 26 07:27:17 192.168.122.209 [55387.550042] End test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsNoTransformCache.test Apr 26 07:27:17 192.168.122.209 [55387.575485] Start test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsPrivateCache.test Apr 26 07:27:18 192.168.122.209 [55388.589598] [tdb] Start Tempesta DB Apr 26 07:27:18 192.168.122.209 [55388.726777] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:27:19 192.168.122.209 [55390.213995] [tempesta fw] Configuration processing is completed. Apr 26 07:27:19 192.168.122.209 [55390.265298] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:27:20 192.168.122.209 [55390.682442] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:27:20 192.168.122.209 [55390.709603] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:27:20 192.168.122.209 [55390.736930] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:27:20 192.168.122.209 [55390.801931] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:27:20 192.168.122.209 [55390.845929] [tempesta fw] Tempesta FW is ready Apr 26 07:27:20 192.168.122.209 [55391.482356] [tdb] Close table 'client0.tdb' Apr 26 07:27:21 192.168.122.209 [55391.669485] [tdb] Close table 'sessions0.tdb' Apr 26 07:27:24 192.168.122.209 [55394.953507] [tdb] Close table 'cache0.tdb' Apr 26 07:27:24 192.168.122.209 [55395.185721] [tdb] Close table 'filter0.tdb' Apr 26 07:27:24 192.168.122.209 [55395.186168] [tempesta fw] modules are stopped Apr 26 07:27:24 192.168.122.209 [55395.393573] [tempesta fw] exiting... Apr 26 07:27:25 192.168.122.209 [55395.536451] [tdb] Shutdown Tempesta DB Apr 26 07:27:25 192.168.122.209 [55395.765330] End test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsPrivateCache.test Apr 26 07:27:25 192.168.122.209 [55395.783767] Start test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsProxyRevalidateCache.test Apr 26 07:27:26 192.168.122.209 [55396.833367] [tdb] Start Tempesta DB Apr 26 07:27:26 192.168.122.209 [55396.973451] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:27:28 192.168.122.209 [55398.578069] [tempesta fw] Configuration processing is completed. Apr 26 07:27:28 192.168.122.209 [55398.635975] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:27:28 192.168.122.209 [55399.059035] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:27:28 192.168.122.209 [55399.086019] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:27:28 192.168.122.209 [55399.129058] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:27:28 192.168.122.209 [55399.198167] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:27:28 192.168.122.209 [55399.237941] [tempesta fw] Tempesta FW is ready Apr 26 07:27:29 192.168.122.209 [55399.843050] [tdb] Close table 'client0.tdb' Apr 26 07:27:29 192.168.122.209 [55400.020141] [tdb] Close table 'sessions0.tdb' Apr 26 07:27:32 192.168.122.209 [55403.302723] [tdb] Close table 'cache0.tdb' Apr 26 07:27:33 192.168.122.209 [55403.542777] [tdb] Close table 'filter0.tdb' Apr 26 07:27:33 192.168.122.209 [55403.543209] [tempesta fw] modules are stopped Apr 26 07:27:33 192.168.122.209 [55403.732790] [tempesta fw] exiting... Apr 26 07:27:33 192.168.122.209 [55403.852927] [tdb] Shutdown Tempesta DB Apr 26 07:27:33 192.168.122.209 [55404.093083] End test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsProxyRevalidateCache.test Apr 26 07:27:33 192.168.122.209 [55404.118309] Start test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsPublicCache.test Apr 26 07:27:34 192.168.122.209 [55405.175248] [tdb] Start Tempesta DB Apr 26 07:27:34 192.168.122.209 [55405.326093] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:27:36 192.168.122.209 [55406.874380] [tempesta fw] Configuration processing is completed. Apr 26 07:27:36 192.168.122.209 [55406.925915] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:27:36 192.168.122.209 [55407.349235] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:27:36 192.168.122.209 [55407.376331] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:27:36 192.168.122.209 [55407.403891] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:27:36 192.168.122.209 [55407.450121] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:27:36 192.168.122.209 [55407.490119] [tempesta fw] Tempesta FW is ready Apr 26 07:27:37 192.168.122.209 [55408.084959] [tdb] Close table 'client0.tdb' Apr 26 07:27:37 192.168.122.209 [55408.292868] [tdb] Close table 'sessions0.tdb' Apr 26 07:27:40 192.168.122.209 [55411.484694] [tdb] Close table 'cache0.tdb' Apr 26 07:27:41 192.168.122.209 [55411.725913] [tdb] Close table 'filter0.tdb' Apr 26 07:27:41 192.168.122.209 [55411.726356] [tempesta fw] modules are stopped Apr 26 07:27:41 192.168.122.209 [55411.922125] [tempesta fw] exiting... Apr 26 07:27:41 192.168.122.209 [55412.059779] [tdb] Shutdown Tempesta DB Apr 26 07:27:41 192.168.122.209 [55412.278966] End test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsPublicCache.test Apr 26 07:27:41 192.168.122.209 [55412.298344] Start test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsSMaxAgeCache.test Apr 26 07:27:42 192.168.122.209 [55413.385283] [tdb] Start Tempesta DB Apr 26 07:27:43 192.168.122.209 [55413.524374] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:27:44 192.168.122.209 [55415.010275] [tempesta fw] Configuration processing is completed. Apr 26 07:27:44 192.168.122.209 [55415.066080] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:27:44 192.168.122.209 [55415.492280] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:27:45 192.168.122.209 [55415.519042] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:27:45 192.168.122.209 [55415.546565] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:27:45 192.168.122.209 [55415.594245] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:27:45 192.168.122.209 [55415.642124] [tempesta fw] Tempesta FW is ready Apr 26 07:27:45 192.168.122.209 [55416.255993] [tdb] Close table 'client0.tdb' Apr 26 07:27:45 192.168.122.209 [55416.442942] [tdb] Close table 'sessions0.tdb' Apr 26 07:27:49 192.168.122.209 [55419.650712] [tdb] Close table 'cache0.tdb' Apr 26 07:27:49 192.168.122.209 [55419.904111] [tdb] Close table 'filter0.tdb' Apr 26 07:27:49 192.168.122.209 [55419.904579] [tempesta fw] modules are stopped Apr 26 07:27:49 192.168.122.209 [55420.090628] [tempesta fw] exiting... Apr 26 07:27:49 192.168.122.209 [55420.239361] [tdb] Shutdown Tempesta DB Apr 26 07:27:49 192.168.122.209 [55420.433843] End test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsSMaxAgeCache.test Apr 26 07:27:49 192.168.122.209 [55420.451354] Start test: cache.test_cache_control.StoringResponsesWithSetCookieHeaderDefaultCache.test Apr 26 07:27:51 192.168.122.209 [55421.564057] [tdb] Start Tempesta DB Apr 26 07:27:51 192.168.122.209 [55421.707492] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:27:52 192.168.122.209 [55423.174376] [tempesta fw] Configuration processing is completed. Apr 26 07:27:52 192.168.122.209 [55423.224685] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:27:53 192.168.122.209 [55423.661356] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:27:53 192.168.122.209 [55423.688519] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:27:53 192.168.122.209 [55423.716014] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:27:53 192.168.122.209 [55423.762338] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:27:53 192.168.122.209 [55423.802308] [tempesta fw] Tempesta FW is ready Apr 26 07:27:53 192.168.122.209 [55424.403366] [tdb] Close table 'client0.tdb' Apr 26 07:27:54 192.168.122.209 [55424.589438] [tdb] Close table 'sessions0.tdb' Apr 26 07:27:57 192.168.122.209 [55427.793928] [tdb] Close table 'cache0.tdb' Apr 26 07:27:57 192.168.122.209 [55428.027061] [tdb] Close table 'filter0.tdb' Apr 26 07:27:57 192.168.122.209 [55428.027483] [tempesta fw] modules are stopped Apr 26 07:27:57 192.168.122.209 [55428.230356] [tempesta fw] exiting... Apr 26 07:27:57 192.168.122.209 [55428.382798] [tdb] Shutdown Tempesta DB Apr 26 07:27:58 192.168.122.209 [55428.633391] End test: cache.test_cache_control.StoringResponsesWithSetCookieHeaderDefaultCache.test Apr 26 07:27:58 192.168.122.209 [55428.652312] Start test: cache.test_cache_control.TestCache.test Apr 26 07:27:59 192.168.122.209 [55429.739293] [tdb] Start Tempesta DB Apr 26 07:27:59 192.168.122.209 [55429.889602] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:28:00 192.168.122.209 [55431.338785] [tempesta fw] Configuration processing is completed. Apr 26 07:28:00 192.168.122.209 [55431.389274] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:28:01 192.168.122.209 [55431.825540] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:28:01 192.168.122.209 [55431.852385] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:28:01 192.168.122.209 [55431.878711] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:28:01 192.168.122.209 [55431.926453] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:28:01 192.168.122.209 [55431.966425] [tempesta fw] Tempesta FW is ready Apr 26 07:28:02 192.168.122.209 [55432.573393] [tdb] Close table 'client0.tdb' Apr 26 07:28:02 192.168.122.209 [55432.767113] [tdb] Close table 'sessions0.tdb' Apr 26 07:28:05 192.168.122.209 [55435.914243] [tdb] Close table 'cache0.tdb' Apr 26 07:28:05 192.168.122.209 [55436.167557] [tdb] Close table 'filter0.tdb' Apr 26 07:28:05 192.168.122.209 [55436.167998] [tempesta fw] modules are stopped Apr 26 07:28:05 192.168.122.209 [55436.402763] [tempesta fw] exiting... Apr 26 07:28:06 192.168.122.209 [55436.537577] [tdb] Shutdown Tempesta DB Apr 26 07:28:06 192.168.122.209 [55436.760639] End test: cache.test_cache_control.TestCache.test Apr 26 07:28:06 192.168.122.209 [55436.771661] Start test: cache.test_cache_control.TestCache2.test Apr 26 07:28:07 192.168.122.209 [55437.794527] [tdb] Start Tempesta DB Apr 26 07:28:07 192.168.122.209 [55437.940856] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:28:08 192.168.122.209 [55439.402577] [tempesta fw] Configuration processing is completed. Apr 26 07:28:08 192.168.122.209 [55439.452663] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:28:09 192.168.122.209 [55439.872026] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:28:09 192.168.122.209 [55439.912678] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:28:09 192.168.122.209 [55439.940061] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:28:09 192.168.122.209 [55439.970540] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:28:09 192.168.122.209 [55440.010499] [tempesta fw] Tempesta FW is ready Apr 26 07:28:10 192.168.122.209 [55440.611843] [tdb] Close table 'client0.tdb' Apr 26 07:28:10 192.168.122.209 [55440.796633] [tdb] Close table 'sessions0.tdb' Apr 26 07:28:13 192.168.122.209 [55444.000252] [tdb] Close table 'cache0.tdb' Apr 26 07:28:13 192.168.122.209 [55444.247317] [tdb] Close table 'filter0.tdb' Apr 26 07:28:13 192.168.122.209 [55444.247774] [tempesta fw] modules are stopped Apr 26 07:28:13 192.168.122.209 [55444.432958] [tempesta fw] exiting... Apr 26 07:28:14 192.168.122.209 [55444.581567] [tdb] Shutdown Tempesta DB Apr 26 07:28:14 192.168.122.209 [55444.780196] End test: cache.test_cache_control.TestCache2.test Apr 26 07:28:14 192.168.122.209 [55444.797841] Start test: cache.test_cache_control.TestCacheBypass.test Apr 26 07:28:15 192.168.122.209 [55445.842866] [tdb] Start Tempesta DB Apr 26 07:28:15 192.168.122.209 [55445.990723] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:28:17 192.168.122.209 [55447.555017] [tempesta fw] Configuration processing is completed. Apr 26 07:28:17 192.168.122.209 [55447.608681] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:28:17 192.168.122.209 [55448.076674] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:28:17 192.168.122.209 [55448.105636] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:28:17 192.168.122.209 [55448.135070] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:28:17 192.168.122.209 [55448.174613] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:28:17 192.168.122.209 [55448.214621] [tempesta fw] Tempesta FW is ready Apr 26 07:28:18 192.168.122.209 [55448.810984] [tdb] Close table 'client0.tdb' Apr 26 07:28:18 192.168.122.209 [55449.008538] [tdb] Close table 'sessions0.tdb' Apr 26 07:28:21 192.168.122.209 [55452.260188] [tdb] Close table 'cache0.tdb' Apr 26 07:28:21 192.168.122.209 [55452.484132] [tdb] Close table 'filter0.tdb' Apr 26 07:28:21 192.168.122.209 [55452.484563] [tempesta fw] modules are stopped Apr 26 07:28:22 192.168.122.209 [55452.714561] [tempesta fw] exiting... Apr 26 07:28:22 192.168.122.209 [55452.859782] [tdb] Shutdown Tempesta DB Apr 26 07:28:22 192.168.122.209 [55453.064058] End test: cache.test_cache_control.TestCacheBypass.test Apr 26 07:28:22 192.168.122.209 [55453.076796] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_no_cache_in_request_and_cache_lvl_1 Apr 26 07:28:23 192.168.122.209 [55454.109792] [tdb] Start Tempesta DB Apr 26 07:28:23 192.168.122.209 [55454.238432] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:28:25 192.168.122.209 [55455.588067] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [55455.588067] Maybe that's fine, but it's worth checking the [55455.588067] config - if there is no relations between the [55455.588067] names, then host name confusion attack is possible. Apr 26 07:28:25 192.168.122.209 [55455.682766] [tempesta fw] Configuration processing is completed. Apr 26 07:28:25 192.168.122.209 [55455.733863] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:28:25 192.168.122.209 [55456.159298] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:28:25 192.168.122.209 [55456.186011] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:28:25 192.168.122.209 [55456.213045] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:28:25 192.168.122.209 [55456.270763] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:28:25 192.168.122.209 [55456.272513] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:28:25 192.168.122.209 [55456.314690] [tempesta fw] Tempesta FW is ready Apr 26 07:28:26 192.168.122.209 [55456.922242] [tdb] Close table 'client0.tdb' Apr 26 07:28:26 192.168.122.209 [55457.115971] [tdb] Close table 'sessions0.tdb' Apr 26 07:28:29 192.168.122.209 [55460.314123] [tdb] Close table 'cache0.tdb' Apr 26 07:28:30 192.168.122.209 [55460.551465] [tdb] Close table 'filter0.tdb' Apr 26 07:28:30 192.168.122.209 [55460.551910] [tempesta fw] modules are stopped Apr 26 07:28:30 192.168.122.209 [55460.756879] [tempesta fw] exiting... Apr 26 07:28:30 192.168.122.209 [55460.885962] [tdb] Shutdown Tempesta DB Apr 26 07:28:30 192.168.122.209 [55461.088888] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_no_cache_in_request_and_cache_lvl_1 Apr 26 07:28:30 192.168.122.209 [55461.105797] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_no_cache_in_request_and_cache_lvl_2 Apr 26 07:28:31 192.168.122.209 [55462.166800] [tdb] Start Tempesta DB Apr 26 07:28:31 192.168.122.209 [55462.313955] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:28:33 192.168.122.209 [55463.692135] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [55463.692135] Maybe that's fine, but it's worth checking the [55463.692135] config - if there is no relations between the [55463.692135] names, then host name confusion attack is possible. Apr 26 07:28:33 192.168.122.209 [55463.774925] [tempesta fw] Configuration processing is completed. Apr 26 07:28:33 192.168.122.209 [55463.826064] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:28:33 192.168.122.209 [55464.257422] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:28:33 192.168.122.209 [55464.284650] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:28:33 192.168.122.209 [55464.310438] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:28:33 192.168.122.209 [55464.354810] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:28:33 192.168.122.209 [55464.356188] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:28:33 192.168.122.209 [55464.394822] [tempesta fw] Tempesta FW is ready Apr 26 07:28:34 192.168.122.209 [55465.017851] [tdb] Close table 'client0.tdb' Apr 26 07:28:34 192.168.122.209 [55465.197777] [tdb] Close table 'sessions0.tdb' Apr 26 07:28:37 192.168.122.209 [55468.437531] [tdb] Close table 'cache0.tdb' Apr 26 07:28:38 192.168.122.209 [55468.673883] [tdb] Close table 'filter0.tdb' Apr 26 07:28:38 192.168.122.209 [55468.674300] [tempesta fw] modules are stopped Apr 26 07:28:38 192.168.122.209 [55468.844629] [tempesta fw] exiting... Apr 26 07:28:38 192.168.122.209 [55468.988371] [tdb] Shutdown Tempesta DB Apr 26 07:28:38 192.168.122.209 [55469.192916] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_no_cache_in_request_and_cache_lvl_2 Apr 26 07:28:38 192.168.122.209 [55469.224889] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_no_cache_in_response_and_cache_lvl_1 Apr 26 07:28:39 192.168.122.209 [55470.181844] [tdb] Start Tempesta DB Apr 26 07:28:39 192.168.122.209 [55470.316524] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:28:41 192.168.122.209 [55471.752398] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [55471.752398] Maybe that's fine, but it's worth checking the [55471.752398] config - if there is no relations between the [55471.752398] names, then host name confusion attack is possible. Apr 26 07:28:41 192.168.122.209 [55471.839029] [tempesta fw] Configuration processing is completed. Apr 26 07:28:41 192.168.122.209 [55471.890494] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:28:41 192.168.122.209 [55472.319308] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:28:41 192.168.122.209 [55472.346128] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:28:41 192.168.122.209 [55472.372529] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:28:41 192.168.122.209 [55472.418860] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:28:41 192.168.122.209 [55472.420582] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:28:41 192.168.122.209 [55472.470888] [tempesta fw] Tempesta FW is ready Apr 26 07:28:42 192.168.122.209 [55473.063487] [tdb] Close table 'client0.tdb' Apr 26 07:28:42 192.168.122.209 [55473.252580] [tdb] Close table 'sessions0.tdb' Apr 26 07:28:45 192.168.122.209 [55476.459964] [tdb] Close table 'cache0.tdb' Apr 26 07:28:46 192.168.122.209 [55476.702556] [tdb] Close table 'filter0.tdb' Apr 26 07:28:46 192.168.122.209 [55476.703012] [tempesta fw] modules are stopped Apr 26 07:28:46 192.168.122.209 [55476.932407] [tempesta fw] exiting... Apr 26 07:28:46 192.168.122.209 [55477.061342] [tdb] Shutdown Tempesta DB Apr 26 07:28:46 192.168.122.209 [55477.291509] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_no_cache_in_response_and_cache_lvl_1 Apr 26 07:28:46 192.168.122.209 [55477.312840] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_no_cache_in_response_and_cache_lvl_2 Apr 26 07:28:47 192.168.122.209 [55478.415635] [tdb] Start Tempesta DB Apr 26 07:28:48 192.168.122.209 [55478.554553] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:28:49 192.168.122.209 [55480.024286] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [55480.024286] Maybe that's fine, but it's worth checking the [55480.024286] config - if there is no relations between the [55480.024286] names, then host name confusion attack is possible. Apr 26 07:28:49 192.168.122.209 [55480.119053] [tempesta fw] Configuration processing is completed. Apr 26 07:28:49 192.168.122.209 [55480.174703] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:28:50 192.168.122.209 [55480.596372] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:28:50 192.168.122.209 [55480.623305] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:28:50 192.168.122.209 [55480.651021] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:28:50 192.168.122.209 [55480.699021] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:28:50 192.168.122.209 [55480.700419] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:28:50 192.168.122.209 [55480.739029] [tempesta fw] Tempesta FW is ready Apr 26 07:28:50 192.168.122.209 [55481.300724] [tdb] Close table 'client0.tdb' Apr 26 07:28:50 192.168.122.209 [55481.497896] [tdb] Close table 'sessions0.tdb' Apr 26 07:28:54 192.168.122.209 [55484.747290] [tdb] Close table 'cache0.tdb' Apr 26 07:28:54 192.168.122.209 [55484.995672] [tdb] Close table 'filter0.tdb' Apr 26 07:28:54 192.168.122.209 [55484.996107] [tempesta fw] modules are stopped Apr 26 07:28:54 192.168.122.209 [55485.215021] [tempesta fw] exiting... Apr 26 07:28:54 192.168.122.209 [55485.320506] [tdb] Shutdown Tempesta DB Apr 26 07:28:55 192.168.122.209 [55485.535908] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_no_cache_in_response_and_cache_lvl_2 Apr 26 07:28:55 192.168.122.209 [55485.566005] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_no_store_in_request_and_cache_lvl_1 Apr 26 07:28:56 192.168.122.209 [55486.648947] [tdb] Start Tempesta DB Apr 26 07:28:56 192.168.122.209 [55486.776314] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:28:57 192.168.122.209 [55488.176378] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [55488.176378] Maybe that's fine, but it's worth checking the [55488.176378] config - if there is no relations between the [55488.176378] names, then host name confusion attack is possible. Apr 26 07:28:57 192.168.122.209 [55488.267185] [tempesta fw] Configuration processing is completed. Apr 26 07:28:57 192.168.122.209 [55488.318501] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:28:58 192.168.122.209 [55488.762911] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:28:58 192.168.122.209 [55488.788946] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:28:58 192.168.122.209 [55488.815002] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:28:58 192.168.122.209 [55488.855161] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:28:58 192.168.122.209 [55488.856905] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:28:58 192.168.122.209 [55488.895134] [tempesta fw] Tempesta FW is ready Apr 26 07:28:58 192.168.122.209 [55489.493319] [tdb] Close table 'client0.tdb' Apr 26 07:28:59 192.168.122.209 [55489.686518] [tdb] Close table 'sessions0.tdb' Apr 26 07:29:02 192.168.122.209 [55492.912468] [tdb] Close table 'cache0.tdb' Apr 26 07:29:02 192.168.122.209 [55493.150850] [tdb] Close table 'filter0.tdb' Apr 26 07:29:02 192.168.122.209 [55493.151322] [tempesta fw] modules are stopped Apr 26 07:29:02 192.168.122.209 [55493.328073] [tempesta fw] exiting... Apr 26 07:29:02 192.168.122.209 [55493.470224] [tdb] Shutdown Tempesta DB Apr 26 07:29:03 192.168.122.209 [55493.675058] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_no_store_in_request_and_cache_lvl_1 Apr 26 07:29:03 192.168.122.209 [55493.696263] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_no_store_in_request_and_cache_lvl_2 Apr 26 07:29:04 192.168.122.209 [55494.763865] [tdb] Start Tempesta DB Apr 26 07:29:04 192.168.122.209 [55494.903413] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:29:05 192.168.122.209 [55496.212504] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [55496.212504] Maybe that's fine, but it's worth checking the [55496.212504] config - if there is no relations between the [55496.212504] names, then host name confusion attack is possible. Apr 26 07:29:05 192.168.122.209 [55496.307295] [tempesta fw] Configuration processing is completed. Apr 26 07:29:05 192.168.122.209 [55496.364783] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:29:06 192.168.122.209 [55496.830453] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:29:06 192.168.122.209 [55496.859890] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:29:06 192.168.122.209 [55496.896700] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:29:06 192.168.122.209 [55496.943251] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:29:06 192.168.122.209 [55496.945069] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:29:06 192.168.122.209 [55496.983202] [tempesta fw] Tempesta FW is ready Apr 26 07:29:07 192.168.122.209 [55497.539680] [tdb] Close table 'client0.tdb' Apr 26 07:29:07 192.168.122.209 [55497.725559] [tdb] Close table 'sessions0.tdb' Apr 26 07:29:10 192.168.122.209 [55500.947221] [tdb] Close table 'cache0.tdb' Apr 26 07:29:10 192.168.122.209 [55501.199801] [tdb] Close table 'filter0.tdb' Apr 26 07:29:10 192.168.122.209 [55501.200239] [tempesta fw] modules are stopped Apr 26 07:29:10 192.168.122.209 [55501.373020] [tempesta fw] exiting... Apr 26 07:29:10 192.168.122.209 [55501.481079] [tdb] Shutdown Tempesta DB Apr 26 07:29:11 192.168.122.209 [55501.685115] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_no_store_in_request_and_cache_lvl_2 Apr 26 07:29:11 192.168.122.209 [55501.704431] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_no_store_in_response_and_cache_lvl_1 Apr 26 07:29:12 192.168.122.209 [55502.733258] [tdb] Start Tempesta DB Apr 26 07:29:12 192.168.122.209 [55502.865798] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:29:13 192.168.122.209 [55504.272570] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [55504.272570] Maybe that's fine, but it's worth checking the [55504.272570] config - if there is no relations between the [55504.272570] names, then host name confusion attack is possible. Apr 26 07:29:13 192.168.122.209 [55504.363371] [tempesta fw] Configuration processing is completed. Apr 26 07:29:13 192.168.122.209 [55504.417933] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:29:14 192.168.122.209 [55504.840248] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:29:14 192.168.122.209 [55504.867133] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:29:14 192.168.122.209 [55504.894656] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:29:14 192.168.122.209 [55504.951342] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:29:14 192.168.122.209 [55504.953079] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:29:14 192.168.122.209 [55504.991297] [tempesta fw] Tempesta FW is ready Apr 26 07:29:15 192.168.122.209 [55505.595358] [tdb] Close table 'client0.tdb' Apr 26 07:29:15 192.168.122.209 [55505.785455] [tdb] Close table 'sessions0.tdb' Apr 26 07:29:18 192.168.122.209 [55508.972238] [tdb] Close table 'cache0.tdb' Apr 26 07:29:18 192.168.122.209 [55509.227950] [tdb] Close table 'filter0.tdb' Apr 26 07:29:18 192.168.122.209 [55509.228384] [tempesta fw] modules are stopped Apr 26 07:29:18 192.168.122.209 [55509.443253] [tempesta fw] exiting... Apr 26 07:29:19 192.168.122.209 [55509.558927] [tdb] Shutdown Tempesta DB Apr 26 07:29:19 192.168.122.209 [55509.808236] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_no_store_in_response_and_cache_lvl_1 Apr 26 07:29:19 192.168.122.209 [55509.820811] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_no_store_in_response_and_cache_lvl_2 Apr 26 07:29:20 192.168.122.209 [55510.866674] [tdb] Start Tempesta DB Apr 26 07:29:20 192.168.122.209 [55511.009468] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:29:21 192.168.122.209 [55512.408670] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [55512.408670] Maybe that's fine, but it's worth checking the [55512.408670] config - if there is no relations between the [55512.408670] names, then host name confusion attack is possible. Apr 26 07:29:21 192.168.122.209 [55512.491470] [tempesta fw] Configuration processing is completed. Apr 26 07:29:22 192.168.122.209 [55512.549879] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:29:22 192.168.122.209 [55512.977300] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:29:22 192.168.122.209 [55513.004761] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:29:22 192.168.122.209 [55513.031593] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:29:22 192.168.122.209 [55513.075407] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:29:22 192.168.122.209 [55513.076800] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:29:22 192.168.122.209 [55513.123403] [tempesta fw] Tempesta FW is ready Apr 26 07:29:23 192.168.122.209 [55513.685056] [tdb] Close table 'client0.tdb' Apr 26 07:29:23 192.168.122.209 [55513.875499] [tdb] Close table 'sessions0.tdb' Apr 26 07:29:26 192.168.122.209 [55517.106608] [tdb] Close table 'cache0.tdb' Apr 26 07:29:26 192.168.122.209 [55517.335587] [tdb] Close table 'filter0.tdb' Apr 26 07:29:26 192.168.122.209 [55517.336029] [tempesta fw] modules are stopped Apr 26 07:29:27 192.168.122.209 [55517.547328] [tempesta fw] exiting... Apr 26 07:29:27 192.168.122.209 [55517.674251] [tdb] Shutdown Tempesta DB Apr 26 07:29:27 192.168.122.209 [55517.871898] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_no_store_in_response_and_cache_lvl_2 Apr 26 07:29:27 192.168.122.209 [55517.882894] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_private_in_response_and_cache_lvl_1 Apr 26 07:29:28 192.168.122.209 [55518.928264] [tdb] Start Tempesta DB Apr 26 07:29:28 192.168.122.209 [55519.062240] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:29:29 192.168.122.209 [55520.444817] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [55520.444817] Maybe that's fine, but it's worth checking the [55520.444817] config - if there is no relations between the [55520.444817] names, then host name confusion attack is possible. Apr 26 07:29:30 192.168.122.209 [55520.547582] [tempesta fw] Configuration processing is completed. Apr 26 07:29:30 192.168.122.209 [55520.599169] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:29:30 192.168.122.209 [55521.027195] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:29:30 192.168.122.209 [55521.053879] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:29:30 192.168.122.209 [55521.081163] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:29:30 192.168.122.209 [55521.131564] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:29:30 192.168.122.209 [55521.133288] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:29:30 192.168.122.209 [55521.175487] [tempesta fw] Tempesta FW is ready Apr 26 07:29:31 192.168.122.209 [55521.802402] [tdb] Close table 'client0.tdb' Apr 26 07:29:31 192.168.122.209 [55521.999126] [tdb] Close table 'sessions0.tdb' Apr 26 07:29:34 192.168.122.209 [55525.213244] [tdb] Close table 'cache0.tdb' Apr 26 07:29:34 192.168.122.209 [55525.443750] [tdb] Close table 'filter0.tdb' Apr 26 07:29:34 192.168.122.209 [55525.444184] [tempesta fw] modules are stopped Apr 26 07:29:35 192.168.122.209 [55525.669011] [tempesta fw] exiting... Apr 26 07:29:35 192.168.122.209 [55525.776839] [tdb] Shutdown Tempesta DB Apr 26 07:29:35 192.168.122.209 [55525.984436] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_private_in_response_and_cache_lvl_1 Apr 26 07:29:35 192.168.122.209 [55525.999280] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_private_in_response_and_cache_lvl_2 Apr 26 07:29:36 192.168.122.209 [55527.058151] [tdb] Start Tempesta DB Apr 26 07:29:36 192.168.122.209 [55527.190790] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:29:38 192.168.122.209 [55528.524916] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [55528.524916] Maybe that's fine, but it's worth checking the [55528.524916] config - if there is no relations between the [55528.524916] names, then host name confusion attack is possible. Apr 26 07:29:38 192.168.122.209 [55528.611685] [tempesta fw] Configuration processing is completed. Apr 26 07:29:38 192.168.122.209 [55528.664052] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:29:38 192.168.122.209 [55529.090347] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:29:38 192.168.122.209 [55529.116902] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:29:38 192.168.122.209 [55529.142294] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:29:38 192.168.122.209 [55529.187650] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:29:38 192.168.122.209 [55529.189387] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:29:38 192.168.122.209 [55529.239635] [tempesta fw] Tempesta FW is ready Apr 26 07:29:39 192.168.122.209 [55529.843171] [tdb] Close table 'client0.tdb' Apr 26 07:29:39 192.168.122.209 [55530.029823] [tdb] Close table 'sessions0.tdb' Apr 26 07:29:42 192.168.122.209 [55533.249879] [tdb] Close table 'cache0.tdb' Apr 26 07:29:42 192.168.122.209 [55533.483025] [tdb] Close table 'filter0.tdb' Apr 26 07:29:42 192.168.122.209 [55533.483447] [tempesta fw] modules are stopped Apr 26 07:29:43 192.168.122.209 [55533.675668] [tempesta fw] exiting... Apr 26 07:29:43 192.168.122.209 [55533.793196] [tdb] Shutdown Tempesta DB Apr 26 07:29:43 192.168.122.209 [55534.008214] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_private_in_response_and_cache_lvl_2 Apr 26 07:29:43 192.168.122.209 [55534.024993] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_pragma_no_cache_in_request_and_cache_lvl_1 Apr 26 07:29:44 192.168.122.209 [55535.117004] [tdb] Start Tempesta DB Apr 26 07:29:44 192.168.122.209 [55535.261707] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:29:46 192.168.122.209 [55536.640935] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [55536.640935] Maybe that's fine, but it's worth checking the [55536.640935] config - if there is no relations between the [55536.640935] names, then host name confusion attack is possible. Apr 26 07:29:46 192.168.122.209 [55536.755770] [tempesta fw] Configuration processing is completed. Apr 26 07:29:46 192.168.122.209 [55536.807021] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:29:46 192.168.122.209 [55537.231742] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:29:46 192.168.122.209 [55537.263507] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:29:46 192.168.122.209 [55537.290641] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:29:46 192.168.122.209 [55537.335757] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:29:46 192.168.122.209 [55537.337520] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:29:46 192.168.122.209 [55537.387701] [tempesta fw] Tempesta FW is ready Apr 26 07:29:47 192.168.122.209 [55538.008185] [tdb] Close table 'client0.tdb' Apr 26 07:29:47 192.168.122.209 [55538.196693] [tdb] Close table 'sessions0.tdb' Apr 26 07:29:50 192.168.122.209 [55541.382331] [tdb] Close table 'cache0.tdb' Apr 26 07:29:51 192.168.122.209 [55541.638116] [tdb] Close table 'filter0.tdb' Apr 26 07:29:51 192.168.122.209 [55541.638536] [tempesta fw] modules are stopped Apr 26 07:29:51 192.168.122.209 [55541.836048] [tempesta fw] exiting... Apr 26 07:29:51 192.168.122.209 [55541.968425] [tdb] Shutdown Tempesta DB Apr 26 07:29:51 192.168.122.209 [55542.188840] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_pragma_no_cache_in_request_and_cache_lvl_1 Apr 26 07:29:51 192.168.122.209 [55542.206665] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_pragma_no_cache_in_request_and_cache_lvl_2 Apr 26 07:29:52 192.168.122.209 [55543.242496] [tdb] Start Tempesta DB Apr 26 07:29:52 192.168.122.209 [55543.385156] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:29:54 192.168.122.209 [55544.777045] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [55544.777045] Maybe that's fine, but it's worth checking the [55544.777045] config - if there is no relations between the [55544.777045] names, then host name confusion attack is possible. Apr 26 07:29:54 192.168.122.209 [55544.859891] [tempesta fw] Configuration processing is completed. Apr 26 07:29:54 192.168.122.209 [55544.911038] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:29:54 192.168.122.209 [55545.329780] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:29:54 192.168.122.209 [55545.357429] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:29:54 192.168.122.209 [55545.383970] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:29:54 192.168.122.209 [55545.431861] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:29:54 192.168.122.209 [55545.433583] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:29:54 192.168.122.209 [55545.475786] [tempesta fw] Tempesta FW is ready Apr 26 07:29:55 192.168.122.209 [55546.070722] [tdb] Close table 'client0.tdb' Apr 26 07:29:55 192.168.122.209 [55546.259319] [tdb] Close table 'sessions0.tdb' Apr 26 07:29:58 192.168.122.209 [55549.497980] [tdb] Close table 'cache0.tdb' Apr 26 07:29:59 192.168.122.209 [55549.736794] [tdb] Close table 'filter0.tdb' Apr 26 07:29:59 192.168.122.209 [55549.737238] [tempesta fw] modules are stopped Apr 26 07:29:59 192.168.122.209 [55549.923780] [tempesta fw] exiting... Apr 26 07:29:59 192.168.122.209 [55550.056135] [tdb] Shutdown Tempesta DB Apr 26 07:29:59 192.168.122.209 [55550.289159] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_pragma_no_cache_in_request_and_cache_lvl_2 Apr 26 07:29:59 192.168.122.209 [55550.304230] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_pragma_no_cache_in_response_and_cache_lvl_1 Apr 26 07:30:00 192.168.122.209 [55551.288856] [tdb] Start Tempesta DB Apr 26 07:30:00 192.168.122.209 [55551.428209] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:30:02 192.168.122.209 [55552.829179] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [55552.829179] Maybe that's fine, but it's worth checking the [55552.829179] config - if there is no relations between the [55552.829179] names, then host name confusion attack is possible. Apr 26 07:30:02 192.168.122.209 [55552.923976] [tempesta fw] Configuration processing is completed. Apr 26 07:30:02 192.168.122.209 [55552.976876] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:30:02 192.168.122.209 [55553.393767] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:30:02 192.168.122.209 [55553.420133] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:30:02 192.168.122.209 [55553.445853] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:30:03 192.168.122.209 [55553.511956] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:30:03 192.168.122.209 [55553.513678] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:30:03 192.168.122.209 [55553.555888] [tempesta fw] Tempesta FW is ready Apr 26 07:30:03 192.168.122.209 [55554.140857] [tdb] Close table 'client0.tdb' Apr 26 07:30:03 192.168.122.209 [55554.369186] [tdb] Close table 'sessions0.tdb' Apr 26 07:30:07 192.168.122.209 [55557.573338] [tdb] Close table 'cache0.tdb' Apr 26 07:30:07 192.168.122.209 [55557.828599] [tdb] Close table 'filter0.tdb' Apr 26 07:30:07 192.168.122.209 [55557.829029] [tempesta fw] modules are stopped Apr 26 07:30:07 192.168.122.209 [55558.003264] [tempesta fw] exiting... Apr 26 07:30:07 192.168.122.209 [55558.118322] [tdb] Shutdown Tempesta DB Apr 26 07:30:07 192.168.122.209 [55558.354688] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_pragma_no_cache_in_response_and_cache_lvl_1 Apr 26 07:30:07 192.168.122.209 [55558.372939] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_pragma_no_cache_in_response_and_cache_lvl_2 Apr 26 07:30:08 192.168.122.209 [55559.421358] [tdb] Start Tempesta DB Apr 26 07:30:09 192.168.122.209 [55559.556258] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:30:10 192.168.122.209 [55560.917305] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [55560.917305] Maybe that's fine, but it's worth checking the [55560.917305] config - if there is no relations between the [55560.917305] names, then host name confusion attack is possible. Apr 26 07:30:10 192.168.122.209 [55561.004291] [tempesta fw] Configuration processing is completed. Apr 26 07:30:10 192.168.122.209 [55561.055455] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:30:10 192.168.122.209 [55561.485962] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:30:11 192.168.122.209 [55561.512481] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:30:11 192.168.122.209 [55561.538419] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:30:11 192.168.122.209 [55561.580061] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:30:11 192.168.122.209 [55561.581799] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:30:11 192.168.122.209 [55561.639995] [tempesta fw] Tempesta FW is ready Apr 26 07:30:11 192.168.122.209 [55562.227233] [tdb] Close table 'client0.tdb' Apr 26 07:30:11 192.168.122.209 [55562.420087] [tdb] Close table 'sessions0.tdb' Apr 26 07:30:15 192.168.122.209 [55565.602059] [tdb] Close table 'cache0.tdb' Apr 26 07:30:15 192.168.122.209 [55565.863992] [tdb] Close table 'filter0.tdb' Apr 26 07:30:15 192.168.122.209 [55565.864428] [tempesta fw] modules are stopped Apr 26 07:30:15 192.168.122.209 [55566.035124] [tempesta fw] exiting... Apr 26 07:30:15 192.168.122.209 [55566.173079] [tdb] Shutdown Tempesta DB Apr 26 07:30:15 192.168.122.209 [55566.385004] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_pragma_no_cache_in_response_and_cache_lvl_2 Apr 26 07:30:15 192.168.122.209 [55566.412809] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_no_cache_in_request_and_cache_lvl_1 Apr 26 07:30:16 192.168.122.209 [55567.385952] [tdb] Start Tempesta DB Apr 26 07:30:17 192.168.122.209 [55567.520775] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:30:18 192.168.122.209 [55568.865379] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [55568.865379] Maybe that's fine, but it's worth checking the [55568.865379] config - if there is no relations between the [55568.865379] names, then host name confusion attack is possible. Apr 26 07:30:18 192.168.122.209 [55568.952214] [tempesta fw] Configuration processing is completed. Apr 26 07:30:18 192.168.122.209 [55569.012037] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:30:18 192.168.122.209 [55569.436069] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:30:18 192.168.122.209 [55569.463297] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:30:18 192.168.122.209 [55569.491055] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:30:19 192.168.122.209 [55569.544169] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:30:19 192.168.122.209 [55569.545892] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:30:19 192.168.122.209 [55569.584088] [tempesta fw] Tempesta FW is ready Apr 26 07:30:19 192.168.122.209 [55570.211314] [tdb] Close table 'client0.tdb' Apr 26 07:30:19 192.168.122.209 [55570.381210] [tdb] Close table 'sessions0.tdb' Apr 26 07:30:23 192.168.122.209 [55573.592331] [tdb] Close table 'cache0.tdb' Apr 26 07:30:23 192.168.122.209 [55573.850042] [tdb] Close table 'filter0.tdb' Apr 26 07:30:23 192.168.122.209 [55573.850501] [tempesta fw] modules are stopped Apr 26 07:30:23 192.168.122.209 [55574.050485] [tempesta fw] exiting... Apr 26 07:30:23 192.168.122.209 [55574.146688] [tdb] Shutdown Tempesta DB Apr 26 07:30:23 192.168.122.209 [55574.393203] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_no_cache_in_request_and_cache_lvl_1 Apr 26 07:30:23 192.168.122.209 [55574.405096] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_no_cache_in_request_and_cache_lvl_2 Apr 26 07:30:24 192.168.122.209 [55575.499903] [tdb] Start Tempesta DB Apr 26 07:30:25 192.168.122.209 [55575.634696] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:30:26 192.168.122.209 [55577.041509] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [55577.041509] Maybe that's fine, but it's worth checking the [55577.041509] config - if there is no relations between the [55577.041509] names, then host name confusion attack is possible. Apr 26 07:30:26 192.168.122.209 [55577.124263] [tempesta fw] Configuration processing is completed. Apr 26 07:30:26 192.168.122.209 [55577.185006] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:30:27 192.168.122.209 [55577.624114] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:30:27 192.168.122.209 [55577.651080] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:30:27 192.168.122.209 [55577.677832] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:30:27 192.168.122.209 [55577.724245] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:30:27 192.168.122.209 [55577.725610] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:30:27 192.168.122.209 [55577.776217] [tempesta fw] Tempesta FW is ready Apr 26 07:30:27 192.168.122.209 [55578.408778] [tdb] Close table 'client0.tdb' Apr 26 07:30:28 192.168.122.209 [55578.592119] [tdb] Close table 'sessions0.tdb' Apr 26 07:30:31 192.168.122.209 [55581.865273] [tdb] Close table 'cache0.tdb' Apr 26 07:30:31 192.168.122.209 [55582.116309] [tdb] Close table 'filter0.tdb' Apr 26 07:30:31 192.168.122.209 [55582.116760] [tempesta fw] modules are stopped Apr 26 07:30:31 192.168.122.209 [55582.316666] [tempesta fw] exiting... Apr 26 07:30:31 192.168.122.209 [55582.458160] [tdb] Shutdown Tempesta DB Apr 26 07:30:32 192.168.122.209 [55582.660700] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_no_cache_in_request_and_cache_lvl_2 Apr 26 07:30:32 192.168.122.209 [55582.694085] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_no_cache_in_response_and_cache_lvl_1 Apr 26 07:30:33 192.168.122.209 [55583.725085] [tdb] Start Tempesta DB Apr 26 07:30:33 192.168.122.209 [55583.868107] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:30:34 192.168.122.209 [55585.169582] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [55585.169582] Maybe that's fine, but it's worth checking the [55585.169582] config - if there is no relations between the [55585.169582] names, then host name confusion attack is possible. Apr 26 07:30:34 192.168.122.209 [55585.252395] [tempesta fw] Configuration processing is completed. Apr 26 07:30:34 192.168.122.209 [55585.311873] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:30:35 192.168.122.209 [55585.732109] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:30:35 192.168.122.209 [55585.758233] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:30:35 192.168.122.209 [55585.783976] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:30:35 192.168.122.209 [55585.836374] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:30:35 192.168.122.209 [55585.838126] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:30:35 192.168.122.209 [55585.896296] [tempesta fw] Tempesta FW is ready Apr 26 07:30:36 192.168.122.209 [55586.561486] [tdb] Close table 'client0.tdb' Apr 26 07:30:36 192.168.122.209 [55586.749831] [tdb] Close table 'sessions0.tdb' Apr 26 07:30:39 192.168.122.209 [55589.914708] [tdb] Close table 'cache0.tdb' Apr 26 07:30:39 192.168.122.209 [55590.135327] [tdb] Close table 'filter0.tdb' Apr 26 07:30:39 192.168.122.209 [55590.135766] [tempesta fw] modules are stopped Apr 26 07:30:39 192.168.122.209 [55590.344116] [tempesta fw] exiting... Apr 26 07:30:39 192.168.122.209 [55590.458249] [tdb] Shutdown Tempesta DB Apr 26 07:30:40 192.168.122.209 [55590.677299] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_no_cache_in_response_and_cache_lvl_1 Apr 26 07:30:40 192.168.122.209 [55590.707798] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_no_cache_in_response_and_cache_lvl_2 Apr 26 07:30:41 192.168.122.209 [55591.780055] [tdb] Start Tempesta DB Apr 26 07:30:41 192.168.122.209 [55591.916488] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:30:42 192.168.122.209 [55593.289807] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [55593.289807] Maybe that's fine, but it's worth checking the [55593.289807] config - if there is no relations between the [55593.289807] names, then host name confusion attack is possible. Apr 26 07:30:42 192.168.122.209 [55593.376535] [tempesta fw] Configuration processing is completed. Apr 26 07:30:42 192.168.122.209 [55593.433616] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:30:43 192.168.122.209 [55593.877934] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:30:43 192.168.122.209 [55593.905739] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:30:43 192.168.122.209 [55593.934082] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:30:43 192.168.122.209 [55593.992462] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:30:43 192.168.122.209 [55593.994194] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:30:43 192.168.122.209 [55594.032422] [tempesta fw] Tempesta FW is ready Apr 26 07:30:44 192.168.122.209 [55594.684451] [tdb] Close table 'client0.tdb' Apr 26 07:30:44 192.168.122.209 [55594.881008] [tdb] Close table 'sessions0.tdb' Apr 26 07:30:47 192.168.122.209 [55598.116911] [tdb] Close table 'cache0.tdb' Apr 26 07:30:47 192.168.122.209 [55598.341346] [tdb] Close table 'filter0.tdb' Apr 26 07:30:47 192.168.122.209 [55598.341772] [tempesta fw] modules are stopped Apr 26 07:30:48 192.168.122.209 [55598.527821] [tempesta fw] exiting... Apr 26 07:30:48 192.168.122.209 [55598.651535] [tdb] Shutdown Tempesta DB Apr 26 07:30:48 192.168.122.209 [55598.889005] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_no_cache_in_response_and_cache_lvl_2 Apr 26 07:30:48 192.168.122.209 [55598.913974] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_no_store_in_request_and_cache_lvl_1 Apr 26 07:30:49 192.168.122.209 [55599.954967] [tdb] Start Tempesta DB Apr 26 07:30:49 192.168.122.209 [55600.097141] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:30:50 192.168.122.209 [55601.449823] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [55601.449823] Maybe that's fine, but it's worth checking the [55601.449823] config - if there is no relations between the [55601.449823] names, then host name confusion attack is possible. Apr 26 07:30:51 192.168.122.209 [55601.536571] [tempesta fw] Configuration processing is completed. Apr 26 07:30:51 192.168.122.209 [55601.588060] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:30:51 192.168.122.209 [55602.023551] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:30:51 192.168.122.209 [55602.059265] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:30:51 192.168.122.209 [55602.085522] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:30:51 192.168.122.209 [55602.132556] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:30:51 192.168.122.209 [55602.134272] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:30:51 192.168.122.209 [55602.172520] [tempesta fw] Tempesta FW is ready Apr 26 07:30:52 192.168.122.209 [55602.821301] [tdb] Close table 'client0.tdb' Apr 26 07:30:52 192.168.122.209 [55603.006856] [tdb] Close table 'sessions0.tdb' Apr 26 07:30:55 192.168.122.209 [55606.200847] [tdb] Close table 'cache0.tdb' Apr 26 07:30:55 192.168.122.209 [55606.444907] [tdb] Close table 'filter0.tdb' Apr 26 07:30:55 192.168.122.209 [55606.445349] [tempesta fw] modules are stopped Apr 26 07:30:56 192.168.122.209 [55606.656395] [tempesta fw] exiting... Apr 26 07:30:56 192.168.122.209 [55606.764607] [tdb] Shutdown Tempesta DB Apr 26 07:30:56 192.168.122.209 [55606.976220] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_no_store_in_request_and_cache_lvl_1 Apr 26 07:30:56 192.168.122.209 [55606.987667] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_no_store_in_request_and_cache_lvl_2 Apr 26 07:30:57 192.168.122.209 [55608.022813] [tdb] Start Tempesta DB Apr 26 07:30:57 192.168.122.209 [55608.172661] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:30:59 192.168.122.209 [55609.557911] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [55609.557911] Maybe that's fine, but it's worth checking the [55609.557911] config - if there is no relations between the [55609.557911] names, then host name confusion attack is possible. Apr 26 07:30:59 192.168.122.209 [55609.640684] [tempesta fw] Configuration processing is completed. Apr 26 07:30:59 192.168.122.209 [55609.694037] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:30:59 192.168.122.209 [55610.118722] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:30:59 192.168.122.209 [55610.146291] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:30:59 192.168.122.209 [55610.174243] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:30:59 192.168.122.209 [55610.220654] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:30:59 192.168.122.209 [55610.222438] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:30:59 192.168.122.209 [55610.264601] [tempesta fw] Tempesta FW is ready Apr 26 07:31:00 192.168.122.209 [55610.935343] [tdb] Close table 'client0.tdb' Apr 26 07:31:00 192.168.122.209 [55611.102391] [tdb] Close table 'sessions0.tdb' Apr 26 07:31:03 192.168.122.209 [55614.341596] [tdb] Close table 'cache0.tdb' Apr 26 07:31:04 192.168.122.209 [55614.603797] [tdb] Close table 'filter0.tdb' Apr 26 07:31:04 192.168.122.209 [55614.604241] [tempesta fw] modules are stopped Apr 26 07:31:04 192.168.122.209 [55614.807981] [tempesta fw] exiting... Apr 26 07:31:04 192.168.122.209 [55614.933784] [tdb] Shutdown Tempesta DB Apr 26 07:31:04 192.168.122.209 [55615.156269] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_no_store_in_request_and_cache_lvl_2 Apr 26 07:31:04 192.168.122.209 [55615.181047] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_no_store_in_response_and_cache_lvl_1 Apr 26 07:31:05 192.168.122.209 [55616.242222] [tdb] Start Tempesta DB Apr 26 07:31:05 192.168.122.209 [55616.378144] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:31:07 192.168.122.209 [55617.697994] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [55617.697994] Maybe that's fine, but it's worth checking the [55617.697994] config - if there is no relations between the [55617.697994] names, then host name confusion attack is possible. Apr 26 07:31:07 192.168.122.209 [55617.780778] [tempesta fw] Configuration processing is completed. Apr 26 07:31:07 192.168.122.209 [55617.831652] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:31:07 192.168.122.209 [55618.256848] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:31:07 192.168.122.209 [55618.283993] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:31:07 192.168.122.209 [55618.310928] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:31:07 192.168.122.209 [55618.356666] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:31:07 192.168.122.209 [55618.358403] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:31:07 192.168.122.209 [55618.396724] [tempesta fw] Tempesta FW is ready Apr 26 07:31:08 192.168.122.209 [55619.039891] [tdb] Close table 'client0.tdb' Apr 26 07:31:08 192.168.122.209 [55619.242707] [tdb] Close table 'sessions0.tdb' Apr 26 07:31:11 192.168.122.209 [55622.455937] [tdb] Close table 'cache0.tdb' Apr 26 07:31:12 192.168.122.209 [55622.697128] [tdb] Close table 'filter0.tdb' Apr 26 07:31:12 192.168.122.209 [55622.697572] [tempesta fw] modules are stopped Apr 26 07:31:12 192.168.122.209 [55622.880357] [tempesta fw] exiting... Apr 26 07:31:12 192.168.122.209 [55623.029632] [tdb] Shutdown Tempesta DB Apr 26 07:31:12 192.168.122.209 [55623.263832] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_no_store_in_response_and_cache_lvl_1 Apr 26 07:31:12 192.168.122.209 [55623.279498] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_no_store_in_response_and_cache_lvl_2 Apr 26 07:31:13 192.168.122.209 [55624.371222] [tdb] Start Tempesta DB Apr 26 07:31:14 192.168.122.209 [55624.517703] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:31:15 192.168.122.209 [55625.818086] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [55625.818086] Maybe that's fine, but it's worth checking the [55625.818086] config - if there is no relations between the [55625.818086] names, then host name confusion attack is possible. Apr 26 07:31:15 192.168.122.209 [55625.916869] [tempesta fw] Configuration processing is completed. Apr 26 07:31:15 192.168.122.209 [55625.972978] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:31:15 192.168.122.209 [55626.420822] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:31:15 192.168.122.209 [55626.449516] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:31:15 192.168.122.209 [55626.479219] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:31:16 192.168.122.209 [55626.528906] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:31:16 192.168.122.209 [55626.530657] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:31:16 192.168.122.209 [55626.572805] [tempesta fw] Tempesta FW is ready Apr 26 07:31:16 192.168.122.209 [55627.297794] [tdb] Close table 'client0.tdb' Apr 26 07:31:16 192.168.122.209 [55627.478968] [tdb] Close table 'sessions0.tdb' Apr 26 07:31:20 192.168.122.209 [55630.683988] [tdb] Close table 'cache0.tdb' Apr 26 07:31:20 192.168.122.209 [55630.939593] [tdb] Close table 'filter0.tdb' Apr 26 07:31:20 192.168.122.209 [55630.940037] [tempesta fw] modules are stopped Apr 26 07:31:20 192.168.122.209 [55631.141191] [tempesta fw] exiting... Apr 26 07:31:20 192.168.122.209 [55631.254540] [tdb] Shutdown Tempesta DB Apr 26 07:31:20 192.168.122.209 [55631.499325] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_no_store_in_response_and_cache_lvl_2 Apr 26 07:31:21 192.168.122.209 [55631.519477] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_private_in_response_and_cache_lvl_1 Apr 26 07:31:22 192.168.122.209 [55632.552856] [tdb] Start Tempesta DB Apr 26 07:31:22 192.168.122.209 [55632.699380] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:31:23 192.168.122.209 [55634.066213] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [55634.066213] Maybe that's fine, but it's worth checking the [55634.066213] config - if there is no relations between the [55634.066213] names, then host name confusion attack is possible. Apr 26 07:31:23 192.168.122.209 [55634.156981] [tempesta fw] Configuration processing is completed. Apr 26 07:31:23 192.168.122.209 [55634.211136] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:31:24 192.168.122.209 [55634.659192] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:31:24 192.168.122.209 [55634.687706] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:31:24 192.168.122.209 [55634.715734] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:31:24 192.168.122.209 [55634.780977] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:31:24 192.168.122.209 [55634.782709] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:31:24 192.168.122.209 [55634.824909] [tempesta fw] Tempesta FW is ready Apr 26 07:31:24 192.168.122.209 [55635.486169] [tdb] Close table 'client0.tdb' Apr 26 07:31:25 192.168.122.209 [55635.676042] [tdb] Close table 'sessions0.tdb' Apr 26 07:31:28 192.168.122.209 [55638.909474] [tdb] Close table 'cache0.tdb' Apr 26 07:31:28 192.168.122.209 [55639.163760] [tdb] Close table 'filter0.tdb' Apr 26 07:31:28 192.168.122.209 [55639.164203] [tempesta fw] modules are stopped Apr 26 07:31:28 192.168.122.209 [55639.349807] [tempesta fw] exiting... Apr 26 07:31:28 192.168.122.209 [55639.476551] [tdb] Shutdown Tempesta DB Apr 26 07:31:29 192.168.122.209 [55639.697694] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_private_in_response_and_cache_lvl_1 Apr 26 07:31:29 192.168.122.209 [55639.720555] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_private_in_response_and_cache_lvl_2 Apr 26 07:31:30 192.168.122.209 [55640.755181] [tdb] Start Tempesta DB Apr 26 07:31:30 192.168.122.209 [55640.905810] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:31:31 192.168.122.209 [55642.302316] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [55642.302316] Maybe that's fine, but it's worth checking the [55642.302316] config - if there is no relations between the [55642.302316] names, then host name confusion attack is possible. Apr 26 07:31:31 192.168.122.209 [55642.389090] [tempesta fw] Configuration processing is completed. Apr 26 07:31:31 192.168.122.209 [55642.440346] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:31:32 192.168.122.209 [55642.870289] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:31:32 192.168.122.209 [55642.898786] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:31:32 192.168.122.209 [55642.926419] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:31:32 192.168.122.209 [55642.973031] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:31:32 192.168.122.209 [55642.974439] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:31:32 192.168.122.209 [55643.013045] [tempesta fw] Tempesta FW is ready Apr 26 07:31:33 192.168.122.209 [55643.657905] [tdb] Close table 'client0.tdb' Apr 26 07:31:33 192.168.122.209 [55643.845042] [tdb] Close table 'sessions0.tdb' Apr 26 07:31:36 192.168.122.209 [55646.980036] [tdb] Close table 'cache0.tdb' Apr 26 07:31:36 192.168.122.209 [55647.224767] [tdb] Close table 'filter0.tdb' Apr 26 07:31:36 192.168.122.209 [55647.225221] [tempesta fw] modules are stopped Apr 26 07:31:36 192.168.122.209 [55647.467045] [tempesta fw] exiting... Apr 26 07:31:37 192.168.122.209 [55647.563636] [tdb] Shutdown Tempesta DB Apr 26 07:31:37 192.168.122.209 [55647.790341] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_private_in_response_and_cache_lvl_2 Apr 26 07:31:37 192.168.122.209 [55647.813180] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_pragma_no_cache_in_request_and_cache_lvl_1 Apr 26 07:31:38 192.168.122.209 [55648.893607] [tdb] Start Tempesta DB Apr 26 07:31:38 192.168.122.209 [55649.016953] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:31:39 192.168.122.209 [55650.330395] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [55650.330395] Maybe that's fine, but it's worth checking the [55650.330395] config - if there is no relations between the [55650.330395] names, then host name confusion attack is possible. Apr 26 07:31:39 192.168.122.209 [55650.425166] [tempesta fw] Configuration processing is completed. Apr 26 07:31:39 192.168.122.209 [55650.480099] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:31:40 192.168.122.209 [55650.903340] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:31:40 192.168.122.209 [55650.937880] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:31:40 192.168.122.209 [55650.965364] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:31:40 192.168.122.209 [55651.013163] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:31:40 192.168.122.209 [55651.014873] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:31:40 192.168.122.209 [55651.069150] [tempesta fw] Tempesta FW is ready Apr 26 07:31:41 192.168.122.209 [55651.742487] [tdb] Close table 'client0.tdb' Apr 26 07:31:41 192.168.122.209 [55651.934090] [tdb] Close table 'sessions0.tdb' Apr 26 07:31:44 192.168.122.209 [55655.138278] [tdb] Close table 'cache0.tdb' Apr 26 07:31:44 192.168.122.209 [55655.415222] [tdb] Close table 'filter0.tdb' Apr 26 07:31:44 192.168.122.209 [55655.415691] [tempesta fw] modules are stopped Apr 26 07:31:45 192.168.122.209 [55655.620445] [tempesta fw] exiting... Apr 26 07:31:45 192.168.122.209 [55655.755429] [tdb] Shutdown Tempesta DB Apr 26 07:31:45 192.168.122.209 [55656.000631] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_pragma_no_cache_in_request_and_cache_lvl_1 Apr 26 07:31:45 192.168.122.209 [55656.018744] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_pragma_no_cache_in_request_and_cache_lvl_2 Apr 26 07:31:46 192.168.122.209 [55657.081108] [tdb] Start Tempesta DB Apr 26 07:31:46 192.168.122.209 [55657.230090] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:31:48 192.168.122.209 [55658.606541] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [55658.606541] Maybe that's fine, but it's worth checking the [55658.606541] config - if there is no relations between the [55658.606541] names, then host name confusion attack is possible. Apr 26 07:31:48 192.168.122.209 [55658.697296] [tempesta fw] Configuration processing is completed. Apr 26 07:31:48 192.168.122.209 [55658.751943] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:31:48 192.168.122.209 [55659.169423] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:31:48 192.168.122.209 [55659.195239] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:31:48 192.168.122.209 [55659.220627] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:31:48 192.168.122.209 [55659.289265] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:31:48 192.168.122.209 [55659.291049] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:31:48 192.168.122.209 [55659.333214] [tempesta fw] Tempesta FW is ready Apr 26 07:31:49 192.168.122.209 [55659.986973] [tdb] Close table 'client0.tdb' Apr 26 07:31:49 192.168.122.209 [55660.186821] [tdb] Close table 'sessions0.tdb' Apr 26 07:31:52 192.168.122.209 [55663.426538] [tdb] Close table 'cache0.tdb' Apr 26 07:31:53 192.168.122.209 [55663.683533] [tdb] Close table 'filter0.tdb' Apr 26 07:31:53 192.168.122.209 [55663.683968] [tempesta fw] modules are stopped Apr 26 07:31:53 192.168.122.209 [55663.872243] [tempesta fw] exiting... Apr 26 07:31:53 192.168.122.209 [55663.998927] [tdb] Shutdown Tempesta DB Apr 26 07:31:53 192.168.122.209 [55664.237021] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_pragma_no_cache_in_request_and_cache_lvl_2 Apr 26 07:31:53 192.168.122.209 [55664.247114] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_pragma_no_cache_in_response_and_cache_lvl_1 Apr 26 07:31:54 192.168.122.209 [55665.320988] [tdb] Start Tempesta DB Apr 26 07:31:54 192.168.122.209 [55665.476418] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:31:56 192.168.122.209 [55666.822606] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [55666.822606] Maybe that's fine, but it's worth checking the [55666.822606] config - if there is no relations between the [55666.822606] names, then host name confusion attack is possible. Apr 26 07:31:56 192.168.122.209 [55666.905399] [tempesta fw] Configuration processing is completed. Apr 26 07:31:56 192.168.122.209 [55666.963786] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:31:56 192.168.122.209 [55667.504937] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:31:57 192.168.122.209 [55667.538744] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:31:57 192.168.122.209 [55667.572562] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:31:57 192.168.122.209 [55667.617360] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:31:57 192.168.122.209 [55667.619083] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:31:57 192.168.122.209 [55667.665323] [tempesta fw] Tempesta FW is ready Apr 26 07:31:57 192.168.122.209 [55668.287547] [tdb] Close table 'client0.tdb' Apr 26 07:31:57 192.168.122.209 [55668.496202] [tdb] Close table 'sessions0.tdb' Apr 26 07:32:01 192.168.122.209 [55671.783710] [tdb] Close table 'cache0.tdb' Apr 26 07:32:01 192.168.122.209 [55672.021628] [tdb] Close table 'filter0.tdb' Apr 26 07:32:01 192.168.122.209 [55672.022068] [tempesta fw] modules are stopped Apr 26 07:32:01 192.168.122.209 [55672.221436] [tempesta fw] exiting... Apr 26 07:32:01 192.168.122.209 [55672.359637] [tdb] Shutdown Tempesta DB Apr 26 07:32:02 192.168.122.209 [55672.578357] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_pragma_no_cache_in_response_and_cache_lvl_1 Apr 26 07:32:02 192.168.122.209 [55672.597763] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_pragma_no_cache_in_response_and_cache_lvl_2 Apr 26 07:32:03 192.168.122.209 [55673.658413] [tdb] Start Tempesta DB Apr 26 07:32:03 192.168.122.209 [55673.798591] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:32:04 192.168.122.209 [55675.174815] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [55675.174815] Maybe that's fine, but it's worth checking the [55675.174815] config - if there is no relations between the [55675.174815] names, then host name confusion attack is possible. Apr 26 07:32:04 192.168.122.209 [55675.253522] [tempesta fw] Configuration processing is completed. Apr 26 07:32:04 192.168.122.209 [55675.317039] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:32:05 192.168.122.209 [55675.790054] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:32:05 192.168.122.209 [55675.820458] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:32:05 192.168.122.209 [55675.848560] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:32:05 192.168.122.209 [55675.893438] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:32:05 192.168.122.209 [55675.894845] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:32:05 192.168.122.209 [55675.937410] [tempesta fw] Tempesta FW is ready Apr 26 07:32:06 192.168.122.209 [55676.642163] [tdb] Close table 'client0.tdb' Apr 26 07:32:06 192.168.122.209 [55676.827669] [tdb] Close table 'sessions0.tdb' Apr 26 07:32:09 192.168.122.209 [55680.008648] [tdb] Close table 'cache0.tdb' Apr 26 07:32:09 192.168.122.209 [55680.476626] [tdb] Close table 'filter0.tdb' Apr 26 07:32:09 192.168.122.209 [55680.477079] [tempesta fw] modules are stopped Apr 26 07:32:10 192.168.122.209 [55681.287332] [tempesta fw] exiting... Apr 26 07:32:11 192.168.122.209 [55681.903627] [tdb] Shutdown Tempesta DB Apr 26 07:32:11 192.168.122.209 [55682.142244] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_pragma_no_cache_in_response_and_cache_lvl_2 Apr 26 07:32:11 192.168.122.209 [55682.166422] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_max_stale Apr 26 07:32:12 192.168.122.209 [55683.448415] [tdb] Start Tempesta DB Apr 26 07:32:13 192.168.122.209 [55683.615603] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:32:15 192.168.122.209 [55685.870668] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [55685.870668] Maybe that's fine, but it's worth checking the [55685.870668] config - if there is no relations between the [55685.870668] names, then host name confusion attack is possible. Apr 26 07:32:16 192.168.122.209 [55686.605665] [tempesta fw] Configuration processing is completed. Apr 26 07:32:16 192.168.122.209 [55686.699589] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:32:16 192.168.122.209 [55687.116008] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:32:16 192.168.122.209 [55687.142206] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:32:16 192.168.122.209 [55687.169459] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:32:16 192.168.122.209 [55687.217603] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:32:16 192.168.122.209 [55687.265556] [tempesta fw] Tempesta FW is ready Apr 26 07:32:28 192.168.122.209 [55698.940437] [tdb] Close table 'client0.tdb' Apr 26 07:32:28 192.168.122.209 [55699.129901] [tdb] Close table 'sessions0.tdb' Apr 26 07:32:31 192.168.122.209 [55702.280842] [tdb] Close table 'cache0.tdb' Apr 26 07:32:31 192.168.122.209 [55702.494967] [tdb] Close table 'filter0.tdb' Apr 26 07:32:31 192.168.122.209 [55702.495418] [tempesta fw] modules are stopped Apr 26 07:32:32 192.168.122.209 [55702.699173] [tempesta fw] exiting... Apr 26 07:32:32 192.168.122.209 [55702.818214] [tdb] Shutdown Tempesta DB Apr 26 07:32:32 192.168.122.209 [55703.012625] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_max_stale Apr 26 07:32:32 192.168.122.209 [55703.029157] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_stale_if_error_not_use_304 Apr 26 07:32:33 192.168.122.209 [55704.078506] [tdb] Start Tempesta DB Apr 26 07:32:33 192.168.122.209 [55704.224478] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:32:35 192.168.122.209 [55705.647483] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [55705.647483] Maybe that's fine, but it's worth checking the [55705.647483] config - if there is no relations between the [55705.647483] names, then host name confusion attack is possible. Apr 26 07:32:35 192.168.122.209 [55705.730131] [tempesta fw] Configuration processing is completed. Apr 26 07:32:35 192.168.122.209 [55705.780094] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:32:35 192.168.122.209 [55706.199311] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:32:35 192.168.122.209 [55706.226160] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:32:35 192.168.122.209 [55706.252132] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:32:35 192.168.122.209 [55706.301840] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:32:35 192.168.122.209 [55706.353785] [tempesta fw] Tempesta FW is ready Apr 26 07:32:38 192.168.122.209 [55709.032594] [tdb] Close table 'client0.tdb' Apr 26 07:32:38 192.168.122.209 [55709.217545] [tdb] Close table 'sessions0.tdb' Apr 26 07:32:41 192.168.122.209 [55712.413632] [tdb] Close table 'cache0.tdb' Apr 26 07:32:42 192.168.122.209 [55712.653982] [tdb] Close table 'filter0.tdb' Apr 26 07:32:42 192.168.122.209 [55712.654405] [tempesta fw] modules are stopped Apr 26 07:32:42 192.168.122.209 [55712.857863] [tempesta fw] exiting... Apr 26 07:32:42 192.168.122.209 [55712.984258] [tdb] Shutdown Tempesta DB Apr 26 07:32:42 192.168.122.209 [55713.215582] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_stale_if_error_not_use_304 Apr 26 07:32:42 192.168.122.209 [55713.225611] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_fresh_200 Apr 26 07:32:43 192.168.122.209 [55714.266051] [tdb] Start Tempesta DB Apr 26 07:32:43 192.168.122.209 [55714.411382] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:32:45 192.168.122.209 [55715.863579] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [55715.863579] Maybe that's fine, but it's worth checking the [55715.863579] config - if there is no relations between the [55715.863579] names, then host name confusion attack is possible. Apr 26 07:32:45 192.168.122.209 [55715.966145] [tempesta fw] Configuration processing is completed. Apr 26 07:32:45 192.168.122.209 [55716.026100] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:32:45 192.168.122.209 [55716.441213] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:32:45 192.168.122.209 [55716.467684] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:32:45 192.168.122.209 [55716.494891] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:32:46 192.168.122.209 [55716.537968] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:32:46 192.168.122.209 [55716.577939] [tempesta fw] Tempesta FW is ready Apr 26 07:32:49 192.168.122.209 [55720.244653] [tdb] Close table 'client0.tdb' Apr 26 07:32:49 192.168.122.209 [55720.429545] [tdb] Close table 'sessions0.tdb' Apr 26 07:32:53 192.168.122.209 [55723.614056] [tdb] Close table 'cache0.tdb' Apr 26 07:32:53 192.168.122.209 [55723.856234] [tdb] Close table 'filter0.tdb' Apr 26 07:32:53 192.168.122.209 [55723.856648] [tempesta fw] modules are stopped Apr 26 07:32:53 192.168.122.209 [55724.026698] [tempesta fw] exiting... Apr 26 07:32:53 192.168.122.209 [55724.160783] [tdb] Shutdown Tempesta DB Apr 26 07:32:53 192.168.122.209 [55724.350250] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_fresh_200 Apr 26 07:32:53 192.168.122.209 [55724.366538] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_fresh_403 Apr 26 07:32:54 192.168.122.209 [55725.397816] [tdb] Start Tempesta DB Apr 26 07:32:55 192.168.122.209 [55725.531135] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:32:56 192.168.122.209 [55727.019774] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [55727.019774] Maybe that's fine, but it's worth checking the [55727.019774] config - if there is no relations between the [55727.019774] names, then host name confusion attack is possible. Apr 26 07:32:56 192.168.122.209 [55727.126132] [tempesta fw] Configuration processing is completed. Apr 26 07:32:56 192.168.122.209 [55727.177810] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:32:57 192.168.122.209 [55727.604279] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:32:57 192.168.122.209 [55727.632457] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:32:57 192.168.122.209 [55727.659114] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:32:57 192.168.122.209 [55727.702104] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:32:57 192.168.122.209 [55727.742095] [tempesta fw] Tempesta FW is ready Apr 26 07:33:00 192.168.122.209 [55731.434770] [tdb] Close table 'client0.tdb' Apr 26 07:33:01 192.168.122.209 [55731.608099] [tdb] Close table 'sessions0.tdb' Apr 26 07:33:04 192.168.122.209 [55734.818523] [tdb] Close table 'cache0.tdb' Apr 26 07:33:04 192.168.122.209 [55735.070794] [tdb] Close table 'filter0.tdb' Apr 26 07:33:04 192.168.122.209 [55735.071244] [tempesta fw] modules are stopped Apr 26 07:33:04 192.168.122.209 [55735.258128] [tempesta fw] exiting... Apr 26 07:33:04 192.168.122.209 [55735.372820] [tdb] Shutdown Tempesta DB Apr 26 07:33:05 192.168.122.209 [55735.602379] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_fresh_403 Apr 26 07:33:05 192.168.122.209 [55735.620817] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_fresh_on_error_must_revalidate Apr 26 07:33:06 192.168.122.209 [55736.686469] [tdb] Start Tempesta DB Apr 26 07:33:06 192.168.122.209 [55736.833953] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:33:07 192.168.122.209 [55738.355891] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [55738.355891] Maybe that's fine, but it's worth checking the [55738.355891] config - if there is no relations between the [55738.355891] names, then host name confusion attack is possible. Apr 26 07:33:07 192.168.122.209 [55738.446541] [tempesta fw] Configuration processing is completed. Apr 26 07:33:07 192.168.122.209 [55738.501125] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:33:08 192.168.122.209 [55738.917826] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:33:08 192.168.122.209 [55738.944406] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:33:08 192.168.122.209 [55738.971347] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:33:08 192.168.122.209 [55739.014229] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:33:08 192.168.122.209 [55739.062195] [tempesta fw] Tempesta FW is ready Apr 26 07:33:12 192.168.122.209 [55742.771648] [tdb] Close table 'client0.tdb' Apr 26 07:33:12 192.168.122.209 [55742.973021] [tdb] Close table 'sessions0.tdb' Apr 26 07:33:15 192.168.122.209 [55746.180175] [tdb] Close table 'cache0.tdb' Apr 26 07:33:15 192.168.122.209 [55746.404786] [tdb] Close table 'filter0.tdb' Apr 26 07:33:15 192.168.122.209 [55746.405207] [tempesta fw] modules are stopped Apr 26 07:33:16 192.168.122.209 [55746.595703] [tempesta fw] exiting... Apr 26 07:33:16 192.168.122.209 [55746.710544] [tdb] Shutdown Tempesta DB Apr 26 07:33:16 192.168.122.209 [55746.948171] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_fresh_on_error_must_revalidate Apr 26 07:33:16 192.168.122.209 [55746.959354] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_fresh_on_error_proxy_revalidate Apr 26 07:33:17 192.168.122.209 [55748.031776] [tdb] Start Tempesta DB Apr 26 07:33:17 192.168.122.209 [55748.170890] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:33:19 192.168.122.209 [55749.563508] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [55749.563508] Maybe that's fine, but it's worth checking the [55749.563508] config - if there is no relations between the [55749.563508] names, then host name confusion attack is possible. Apr 26 07:33:19 192.168.122.209 [55749.662644] [tempesta fw] Configuration processing is completed. Apr 26 07:33:19 192.168.122.209 [55749.720772] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:33:19 192.168.122.209 [55750.146282] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:33:19 192.168.122.209 [55750.172977] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:33:19 192.168.122.209 [55750.199398] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:33:19 192.168.122.209 [55750.258385] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:33:19 192.168.122.209 [55750.298366] [tempesta fw] Tempesta FW is ready Apr 26 07:33:23 192.168.122.209 [55754.006657] [tdb] Close table 'client0.tdb' Apr 26 07:33:23 192.168.122.209 [55754.202397] [tdb] Close table 'sessions0.tdb' Apr 26 07:33:26 192.168.122.209 [55757.384497] [tdb] Close table 'cache0.tdb' Apr 26 07:33:27 192.168.122.209 [55757.623954] [tdb] Close table 'filter0.tdb' Apr 26 07:33:27 192.168.122.209 [55757.624363] [tempesta fw] modules are stopped Apr 26 07:33:27 192.168.122.209 [55757.814591] [tempesta fw] exiting... Apr 26 07:33:27 192.168.122.209 [55757.938625] [tdb] Shutdown Tempesta DB Apr 26 07:33:27 192.168.122.209 [55758.158618] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_fresh_on_error_proxy_revalidate Apr 26 07:33:27 192.168.122.209 [55758.175213] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_fresh_on_error_s_maxage Apr 26 07:33:28 192.168.122.209 [55759.297235] [tdb] Start Tempesta DB Apr 26 07:33:28 192.168.122.209 [55759.441290] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:33:30 192.168.122.209 [55760.928211] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [55760.928211] Maybe that's fine, but it's worth checking the [55760.928211] config - if there is no relations between the [55760.928211] names, then host name confusion attack is possible. Apr 26 07:33:30 192.168.122.209 [55761.038913] [tempesta fw] Configuration processing is completed. Apr 26 07:33:30 192.168.122.209 [55761.094457] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:33:31 192.168.122.209 [55761.536335] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:33:31 192.168.122.209 [55761.563314] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:33:31 192.168.122.209 [55761.594664] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:33:31 192.168.122.209 [55761.642521] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:33:31 192.168.122.209 [55761.682476] [tempesta fw] Tempesta FW is ready Apr 26 07:33:34 192.168.122.209 [55765.346033] [tdb] Close table 'client0.tdb' Apr 26 07:33:35 192.168.122.209 [55765.542752] [tdb] Close table 'sessions0.tdb' Apr 26 07:33:38 192.168.122.209 [55768.741908] [tdb] Close table 'cache0.tdb' Apr 26 07:33:38 192.168.122.209 [55769.025533] [tdb] Close table 'filter0.tdb' Apr 26 07:33:38 192.168.122.209 [55769.025975] [tempesta fw] modules are stopped Apr 26 07:33:38 192.168.122.209 [55769.219595] [tempesta fw] exiting... Apr 26 07:33:38 192.168.122.209 [55769.334483] [tdb] Shutdown Tempesta DB Apr 26 07:33:39 192.168.122.209 [55769.545198] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_fresh_on_error_s_maxage Apr 26 07:33:39 192.168.122.209 [55769.556988] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_400 Apr 26 07:33:40 192.168.122.209 [55770.638967] [tdb] Start Tempesta DB Apr 26 07:33:40 192.168.122.209 [55770.786481] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:33:41 192.168.122.209 [55772.336294] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [55772.336294] Maybe that's fine, but it's worth checking the [55772.336294] config - if there is no relations between the [55772.336294] names, then host name confusion attack is possible. Apr 26 07:33:41 192.168.122.209 [55772.426933] [tempesta fw] Configuration processing is completed. Apr 26 07:33:41 192.168.122.209 [55772.477116] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:33:42 192.168.122.209 [55772.897044] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:33:42 192.168.122.209 [55772.924372] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:33:42 192.168.122.209 [55772.950632] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:33:42 192.168.122.209 [55772.986556] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:33:42 192.168.122.209 [55773.030619] [tempesta fw] Tempesta FW is ready Apr 26 07:33:46 192.168.122.209 [55776.692602] [tdb] Close table 'client0.tdb' Apr 26 07:33:46 192.168.122.209 [55776.887502] [tdb] Close table 'sessions0.tdb' Apr 26 07:33:49 192.168.122.209 [55780.074747] [tdb] Close table 'cache0.tdb' Apr 26 07:33:49 192.168.122.209 [55780.334942] [tdb] Close table 'filter0.tdb' Apr 26 07:33:49 192.168.122.209 [55780.335400] [tempesta fw] modules are stopped Apr 26 07:33:50 192.168.122.209 [55780.536222] [tempesta fw] exiting... Apr 26 07:33:50 192.168.122.209 [55780.668951] [tdb] Shutdown Tempesta DB Apr 26 07:33:50 192.168.122.209 [55780.886592] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_400 Apr 26 07:33:50 192.168.122.209 [55780.908520] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_4xx_400 Apr 26 07:33:51 192.168.122.209 [55781.972114] [tdb] Start Tempesta DB Apr 26 07:33:51 192.168.122.209 [55782.118653] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:33:53 192.168.122.209 [55783.504241] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [55783.504241] Maybe that's fine, but it's worth checking the [55783.504241] config - if there is no relations between the [55783.504241] names, then host name confusion attack is possible. Apr 26 07:33:53 192.168.122.209 [55783.606722] [tempesta fw] Configuration processing is completed. Apr 26 07:33:53 192.168.122.209 [55783.660491] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:33:53 192.168.122.209 [55784.118905] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:33:53 192.168.122.209 [55784.153177] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:33:53 192.168.122.209 [55784.179786] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:33:53 192.168.122.209 [55784.270807] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:33:53 192.168.122.209 [55784.310731] [tempesta fw] Tempesta FW is ready Apr 26 07:33:57 192.168.122.209 [55787.968127] [tdb] Close table 'client0.tdb' Apr 26 07:33:57 192.168.122.209 [55788.154384] [tdb] Close table 'sessions0.tdb' Apr 26 07:34:00 192.168.122.209 [55791.370103] [tdb] Close table 'cache0.tdb' Apr 26 07:34:01 192.168.122.209 [55791.616858] [tdb] Close table 'filter0.tdb' Apr 26 07:34:01 192.168.122.209 [55791.617295] [tempesta fw] modules are stopped Apr 26 07:34:01 192.168.122.209 [55791.827603] [tempesta fw] exiting... Apr 26 07:34:01 192.168.122.209 [55791.960623] [tdb] Shutdown Tempesta DB Apr 26 07:34:01 192.168.122.209 [55792.180984] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_4xx_400 Apr 26 07:34:01 192.168.122.209 [55792.203820] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_4xx_403 Apr 26 07:34:02 192.168.122.209 [55793.276657] [tdb] Start Tempesta DB Apr 26 07:34:02 192.168.122.209 [55793.430660] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:34:04 192.168.122.209 [55794.900617] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [55794.900617] Maybe that's fine, but it's worth checking the [55794.900617] config - if there is no relations between the [55794.900617] names, then host name confusion attack is possible. Apr 26 07:34:04 192.168.122.209 [55795.007371] [tempesta fw] Configuration processing is completed. Apr 26 07:34:04 192.168.122.209 [55795.060312] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:34:05 192.168.122.209 [55795.526672] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:34:05 192.168.122.209 [55795.556325] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:34:05 192.168.122.209 [55795.585542] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:34:05 192.168.122.209 [55795.626911] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:34:05 192.168.122.209 [55795.666874] [tempesta fw] Tempesta FW is ready Apr 26 07:34:08 192.168.122.209 [55799.342241] [tdb] Close table 'client0.tdb' Apr 26 07:34:09 192.168.122.209 [55799.532645] [tdb] Close table 'sessions0.tdb' Apr 26 07:34:12 192.168.122.209 [55802.774316] [tdb] Close table 'cache0.tdb' Apr 26 07:34:12 192.168.122.209 [55803.007934] [tdb] Close table 'filter0.tdb' Apr 26 07:34:12 192.168.122.209 [55803.008390] [tempesta fw] modules are stopped Apr 26 07:34:12 192.168.122.209 [55803.226969] [tempesta fw] exiting... Apr 26 07:34:12 192.168.122.209 [55803.360597] [tdb] Shutdown Tempesta DB Apr 26 07:34:13 192.168.122.209 [55803.588580] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_4xx_403 Apr 26 07:34:13 192.168.122.209 [55803.611407] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_4xx_5xx Apr 26 07:34:14 192.168.122.209 [55804.658678] [tdb] Start Tempesta DB Apr 26 07:34:14 192.168.122.209 [55804.810160] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:34:15 192.168.122.209 [55806.312744] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [55806.312744] Maybe that's fine, but it's worth checking the [55806.312744] config - if there is no relations between the [55806.312744] names, then host name confusion attack is possible. Apr 26 07:34:15 192.168.122.209 [55806.403382] [tempesta fw] Configuration processing is completed. Apr 26 07:34:15 192.168.122.209 [55806.459123] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:34:16 192.168.122.209 [55806.881785] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:34:16 192.168.122.209 [55806.919803] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:34:16 192.168.122.209 [55806.952991] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:34:16 192.168.122.209 [55806.999068] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:34:16 192.168.122.209 [55807.047050] [tempesta fw] Tempesta FW is ready Apr 26 07:34:20 192.168.122.209 [55810.733120] [tdb] Close table 'client0.tdb' Apr 26 07:34:20 192.168.122.209 [55810.924913] [tdb] Close table 'sessions0.tdb' Apr 26 07:34:23 192.168.122.209 [55814.129682] [tdb] Close table 'cache0.tdb' Apr 26 07:34:23 192.168.122.209 [55814.368429] [tdb] Close table 'filter0.tdb' Apr 26 07:34:23 192.168.122.209 [55814.368910] [tempesta fw] modules are stopped Apr 26 07:34:24 192.168.122.209 [55814.551819] [tempesta fw] exiting... Apr 26 07:34:24 192.168.122.209 [55814.673849] [tdb] Shutdown Tempesta DB Apr 26 07:34:24 192.168.122.209 [55814.907634] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_4xx_5xx Apr 26 07:34:24 192.168.122.209 [55814.925334] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_500 Apr 26 07:34:25 192.168.122.209 [55815.974237] [tdb] Start Tempesta DB Apr 26 07:34:25 192.168.122.209 [55816.127110] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:34:27 192.168.122.209 [55817.712864] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [55817.712864] Maybe that's fine, but it's worth checking the [55817.712864] config - if there is no relations between the [55817.712864] names, then host name confusion attack is possible. Apr 26 07:34:27 192.168.122.209 [55817.811535] [tempesta fw] Configuration processing is completed. Apr 26 07:34:27 192.168.122.209 [55817.861427] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:34:27 192.168.122.209 [55818.285809] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:34:27 192.168.122.209 [55818.314470] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:34:27 192.168.122.209 [55818.340904] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:34:27 192.168.122.209 [55818.379202] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:34:27 192.168.122.209 [55818.435189] [tempesta fw] Tempesta FW is ready Apr 26 07:34:31 192.168.122.209 [55822.151138] [tdb] Close table 'client0.tdb' Apr 26 07:34:31 192.168.122.209 [55822.338166] [tdb] Close table 'sessions0.tdb' Apr 26 07:34:34 192.168.122.209 [55825.506406] [tdb] Close table 'cache0.tdb' Apr 26 07:34:35 192.168.122.209 [55825.738385] [tdb] Close table 'filter0.tdb' Apr 26 07:34:35 192.168.122.209 [55825.738806] [tempesta fw] modules are stopped Apr 26 07:34:35 192.168.122.209 [55825.913652] [tempesta fw] exiting... Apr 26 07:34:35 192.168.122.209 [55826.014740] [tdb] Shutdown Tempesta DB Apr 26 07:34:35 192.168.122.209 [55826.239927] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_500 Apr 26 07:34:35 192.168.122.209 [55826.261149] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_5xx_500 Apr 26 07:34:36 192.168.122.209 [55827.334117] [tdb] Start Tempesta DB Apr 26 07:34:36 192.168.122.209 [55827.458494] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:34:38 192.168.122.209 [55828.901063] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [55828.901063] Maybe that's fine, but it's worth checking the [55828.901063] config - if there is no relations between the [55828.901063] names, then host name confusion attack is possible. Apr 26 07:34:38 192.168.122.209 [55828.995669] [tempesta fw] Configuration processing is completed. Apr 26 07:34:38 192.168.122.209 [55829.046321] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:34:38 192.168.122.209 [55829.457183] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:34:38 192.168.122.209 [55829.483680] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:34:39 192.168.122.209 [55829.510503] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:34:39 192.168.122.209 [55829.551370] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:34:39 192.168.122.209 [55829.595320] [tempesta fw] Tempesta FW is ready Apr 26 07:34:42 192.168.122.209 [55833.268753] [tdb] Close table 'client0.tdb' Apr 26 07:34:42 192.168.122.209 [55833.458748] [tdb] Close table 'sessions0.tdb' Apr 26 07:34:46 192.168.122.209 [55836.589952] [tdb] Close table 'cache0.tdb' Apr 26 07:34:46 192.168.122.209 [55836.854706] [tdb] Close table 'filter0.tdb' Apr 26 07:34:46 192.168.122.209 [55836.855136] [tempesta fw] modules are stopped Apr 26 07:34:46 192.168.122.209 [55837.056461] [tempesta fw] exiting... Apr 26 07:34:46 192.168.122.209 [55837.170455] [tdb] Shutdown Tempesta DB Apr 26 07:34:46 192.168.122.209 [55837.418587] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_5xx_500 Apr 26 07:34:46 192.168.122.209 [55837.434499] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_5xx_502 Apr 26 07:34:47 192.168.122.209 [55838.418883] [tdb] Start Tempesta DB Apr 26 07:34:48 192.168.122.209 [55838.566323] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:34:49 192.168.122.209 [55840.049108] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [55840.049108] Maybe that's fine, but it's worth checking the [55840.049108] config - if there is no relations between the [55840.049108] names, then host name confusion attack is possible. Apr 26 07:34:49 192.168.122.209 [55840.151647] [tempesta fw] Configuration processing is completed. Apr 26 07:34:49 192.168.122.209 [55840.205630] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:34:50 192.168.122.209 [55840.631231] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:34:50 192.168.122.209 [55840.662639] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:34:50 192.168.122.209 [55840.689159] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:34:50 192.168.122.209 [55840.767540] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:34:50 192.168.122.209 [55840.807471] [tempesta fw] Tempesta FW is ready Apr 26 07:34:54 192.168.122.209 [55844.511244] [tdb] Close table 'client0.tdb' Apr 26 07:34:54 192.168.122.209 [55844.689910] [tdb] Close table 'sessions0.tdb' Apr 26 07:34:57 192.168.122.209 [55847.841724] [tdb] Close table 'cache0.tdb' Apr 26 07:34:57 192.168.122.209 [55848.071824] [tdb] Close table 'filter0.tdb' Apr 26 07:34:57 192.168.122.209 [55848.072254] [tempesta fw] modules are stopped Apr 26 07:34:57 192.168.122.209 [55848.324264] [tempesta fw] exiting... Apr 26 07:34:57 192.168.122.209 [55848.441609] [tdb] Shutdown Tempesta DB Apr 26 07:34:58 192.168.122.209 [55848.645985] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_5xx_502 Apr 26 07:34:58 192.168.122.209 [55848.671080] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_if_error_duplicated_req Apr 26 07:34:59 192.168.122.209 [55849.690922] [tdb] Start Tempesta DB Apr 26 07:34:59 192.168.122.209 [55849.838551] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:35:00 192.168.122.209 [55851.373303] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [55851.373303] Maybe that's fine, but it's worth checking the [55851.373303] config - if there is no relations between the [55851.373303] names, then host name confusion attack is possible. Apr 26 07:35:00 192.168.122.209 [55851.455575] [tempesta fw] Configuration processing is completed. Apr 26 07:35:00 192.168.122.209 [55851.504781] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:35:01 192.168.122.209 [55851.930773] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:35:01 192.168.122.209 [55851.957280] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:35:01 192.168.122.209 [55851.985058] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:35:01 192.168.122.209 [55852.027616] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:35:01 192.168.122.209 [55852.067538] [tempesta fw] Tempesta FW is ready Apr 26 07:35:02 192.168.122.209 [55852.717132] [tdb] Close table 'client0.tdb' Apr 26 07:35:02 192.168.122.209 [55852.908854] [tdb] Close table 'sessions0.tdb' Apr 26 07:35:05 192.168.122.209 [55856.143889] [tdb] Close table 'cache0.tdb' Apr 26 07:35:05 192.168.122.209 [55856.377706] [tdb] Close table 'filter0.tdb' Apr 26 07:35:05 192.168.122.209 [55856.378141] [tempesta fw] modules are stopped Apr 26 07:35:06 192.168.122.209 [55856.563627] [tempesta fw] exiting... Apr 26 07:35:06 192.168.122.209 [55856.690169] [tdb] Shutdown Tempesta DB Apr 26 07:35:06 192.168.122.209 [55856.898363] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_if_error_duplicated_req Apr 26 07:35:06 192.168.122.209 [55856.918615] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_if_error_duplicated_resp Apr 26 07:35:07 192.168.122.209 [55857.993830] [tdb] Start Tempesta DB Apr 26 07:35:07 192.168.122.209 [55858.140589] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:35:09 192.168.122.209 [55859.564730] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [55859.564730] Maybe that's fine, but it's worth checking the [55859.564730] config - if there is no relations between the [55859.564730] names, then host name confusion attack is possible. Apr 26 07:35:09 192.168.122.209 [55859.636008] [tempesta fw] Configuration processing is completed. Apr 26 07:35:09 192.168.122.209 [55859.689935] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:35:09 192.168.122.209 [55860.130219] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:35:09 192.168.122.209 [55860.157444] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:35:09 192.168.122.209 [55860.200609] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:35:09 192.168.122.209 [55860.259804] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:35:09 192.168.122.209 [55860.311703] [tempesta fw] Tempesta FW is ready Apr 26 07:35:09 192.168.122.209 [55860.489524] [tempesta fw] Warning: Parser error: state=Resp_HdrCache_CtrlV input(-0)=0x31('1') data_len=1 off=0 Apr 26 07:35:09 192.168.122.209 [55860.491224] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 07:35:10 192.168.122.209 [55860.927047] [tdb] Close table 'client0.tdb' Apr 26 07:35:10 192.168.122.209 [55861.112996] [tdb] Close table 'sessions0.tdb' Apr 26 07:35:13 192.168.122.209 [55864.343468] [tdb] Close table 'cache0.tdb' Apr 26 07:35:14 192.168.122.209 [55864.569084] [tdb] Close table 'filter0.tdb' Apr 26 07:35:14 192.168.122.209 [55864.569508] [tempesta fw] modules are stopped Apr 26 07:35:14 192.168.122.209 [55864.773628] [tempesta fw] exiting... Apr 26 07:35:14 192.168.122.209 [55864.904323] [tdb] Shutdown Tempesta DB Apr 26 07:35:14 192.168.122.209 [55865.119274] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_if_error_duplicated_resp Apr 26 07:35:14 192.168.122.209 [55865.152922] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_if_error_param_req Apr 26 07:35:15 192.168.122.209 [55866.287653] [tdb] Start Tempesta DB Apr 26 07:35:15 192.168.122.209 [55866.436225] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:35:17 192.168.122.209 [55867.929763] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [55867.929763] Maybe that's fine, but it's worth checking the [55867.929763] config - if there is no relations between the [55867.929763] names, then host name confusion attack is possible. Apr 26 07:35:17 192.168.122.209 [55868.023841] [tempesta fw] Configuration processing is completed. Apr 26 07:35:17 192.168.122.209 [55868.084739] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:35:18 192.168.122.209 [55868.516819] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:35:18 192.168.122.209 [55868.543386] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:35:18 192.168.122.209 [55868.569480] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:35:18 192.168.122.209 [55868.615834] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:35:18 192.168.122.209 [55868.659820] [tempesta fw] Tempesta FW is ready Apr 26 07:35:21 192.168.122.209 [55872.445959] [tdb] Close table 'client0.tdb' Apr 26 07:35:22 192.168.122.209 [55872.633758] [tdb] Close table 'sessions0.tdb' Apr 26 07:35:25 192.168.122.209 [55875.821232] [tdb] Close table 'cache0.tdb' Apr 26 07:35:25 192.168.122.209 [55876.061114] [tdb] Close table 'filter0.tdb' Apr 26 07:35:25 192.168.122.209 [55876.061546] [tempesta fw] modules are stopped Apr 26 07:35:25 192.168.122.209 [55876.239030] [tempesta fw] exiting... Apr 26 07:35:25 192.168.122.209 [55876.374810] [tdb] Shutdown Tempesta DB Apr 26 07:35:26 192.168.122.209 [55876.590100] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_if_error_param_req Apr 26 07:35:26 192.168.122.209 [55876.602377] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_if_error_param_resp Apr 26 07:35:27 192.168.122.209 [55877.640720] [tdb] Start Tempesta DB Apr 26 07:35:27 192.168.122.209 [55877.782054] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:35:28 192.168.122.209 [55879.301681] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [55879.301681] Maybe that's fine, but it's worth checking the [55879.301681] config - if there is no relations between the [55879.301681] names, then host name confusion attack is possible. Apr 26 07:35:28 192.168.122.209 [55879.380238] [tempesta fw] Configuration processing is completed. Apr 26 07:35:28 192.168.122.209 [55879.430332] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:35:29 192.168.122.209 [55879.858297] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:35:29 192.168.122.209 [55879.893040] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:35:29 192.168.122.209 [55879.919933] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:35:29 192.168.122.209 [55879.988130] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:35:29 192.168.122.209 [55880.031954] [tempesta fw] Tempesta FW is ready Apr 26 07:35:33 192.168.122.209 [55883.851585] [tdb] Close table 'client0.tdb' Apr 26 07:35:33 192.168.122.209 [55884.042605] [tdb] Close table 'sessions0.tdb' Apr 26 07:35:36 192.168.122.209 [55887.252032] [tdb] Close table 'cache0.tdb' Apr 26 07:35:36 192.168.122.209 [55887.497431] [tdb] Close table 'filter0.tdb' Apr 26 07:35:36 192.168.122.209 [55887.497872] [tempesta fw] modules are stopped Apr 26 07:35:37 192.168.122.209 [55887.716013] [tempesta fw] exiting... Apr 26 07:35:37 192.168.122.209 [55887.850719] [tdb] Shutdown Tempesta DB Apr 26 07:35:37 192.168.122.209 [55888.051141] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_if_error_param_resp Apr 26 07:35:37 192.168.122.209 [55888.078748] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_invalid_response Apr 26 07:35:38 192.168.122.209 [55889.168846] [tdb] Start Tempesta DB Apr 26 07:35:38 192.168.122.209 [55889.311723] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:35:40 192.168.122.209 [55890.829777] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [55890.829777] Maybe that's fine, but it's worth checking the [55890.829777] config - if there is no relations between the [55890.829777] names, then host name confusion attack is possible. Apr 26 07:35:40 192.168.122.209 [55890.928400] [tempesta fw] Configuration processing is completed. Apr 26 07:35:40 192.168.122.209 [55890.986005] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:35:40 192.168.122.209 [55891.403476] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:35:40 192.168.122.209 [55891.430141] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:35:40 192.168.122.209 [55891.461732] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:35:40 192.168.122.209 [55891.504160] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:35:41 192.168.122.209 [55891.548094] [tempesta fw] Tempesta FW is ready Apr 26 07:35:44 192.168.122.209 [55894.788609] [tempesta fw] Warning: Parser error: state=RGen_HdrOtherN input(-0)=0x3e('>') data_len=1 off=0 Apr 26 07:35:44 192.168.122.209 [55895.217008] [tdb] Close table 'client0.tdb' Apr 26 07:35:44 192.168.122.209 [55895.424652] [tdb] Close table 'sessions0.tdb' Apr 26 07:35:48 192.168.122.209 [55898.572649] [tdb] Close table 'cache0.tdb' Apr 26 07:35:48 192.168.122.209 [55898.828555] [tdb] Close table 'filter0.tdb' Apr 26 07:35:48 192.168.122.209 [55898.828970] [tempesta fw] modules are stopped Apr 26 07:35:48 192.168.122.209 [55899.024217] [tempesta fw] exiting... Apr 26 07:35:48 192.168.122.209 [55899.157786] [tdb] Shutdown Tempesta DB Apr 26 07:35:48 192.168.122.209 [55899.378322] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_invalid_response Apr 26 07:35:48 192.168.122.209 [55899.400618] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_then_fresh_req Apr 26 07:35:50 192.168.122.209 [55900.523266] [tdb] Start Tempesta DB Apr 26 07:35:50 192.168.122.209 [55900.668897] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:35:51 192.168.122.209 [55902.097938] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [55902.097938] Maybe that's fine, but it's worth checking the [55902.097938] config - if there is no relations between the [55902.097938] names, then host name confusion attack is possible. Apr 26 07:35:51 192.168.122.209 [55902.192477] [tempesta fw] Configuration processing is completed. Apr 26 07:35:51 192.168.122.209 [55902.241652] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:35:52 192.168.122.209 [55902.662237] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:35:52 192.168.122.209 [55902.688903] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:35:52 192.168.122.209 [55902.721820] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:35:52 192.168.122.209 [55902.784282] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:35:52 192.168.122.209 [55902.824218] [tempesta fw] Tempesta FW is ready Apr 26 07:35:59 192.168.122.209 [55909.510891] [tdb] Close table 'client0.tdb' Apr 26 07:35:59 192.168.122.209 [55909.696515] [tdb] Close table 'sessions0.tdb' Apr 26 07:36:02 192.168.122.209 [55912.949825] [tdb] Close table 'cache0.tdb' Apr 26 07:36:02 192.168.122.209 [55913.194146] [tdb] Close table 'filter0.tdb' Apr 26 07:36:02 192.168.122.209 [55913.194587] [tempesta fw] modules are stopped Apr 26 07:36:02 192.168.122.209 [55913.412285] [tempesta fw] exiting... Apr 26 07:36:03 192.168.122.209 [55913.535702] [tdb] Shutdown Tempesta DB Apr 26 07:36:03 192.168.122.209 [55913.723853] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_then_fresh_req Apr 26 07:36:03 192.168.122.209 [55913.749124] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_then_fresh_resp Apr 26 07:36:04 192.168.122.209 [55914.828001] [tdb] Start Tempesta DB Apr 26 07:36:04 192.168.122.209 [55914.967402] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:36:05 192.168.122.209 [55916.386121] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [55916.386121] Maybe that's fine, but it's worth checking the [55916.386121] config - if there is no relations between the [55916.386121] names, then host name confusion attack is possible. Apr 26 07:36:05 192.168.122.209 [55916.472649] [tempesta fw] Configuration processing is completed. Apr 26 07:36:06 192.168.122.209 [55916.522576] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:36:06 192.168.122.209 [55916.945198] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:36:06 192.168.122.209 [55916.971784] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:36:06 192.168.122.209 [55916.999280] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:36:06 192.168.122.209 [55917.052486] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:36:06 192.168.122.209 [55917.100426] [tempesta fw] Tempesta FW is ready Apr 26 07:36:13 192.168.122.209 [55923.784024] [tdb] Close table 'client0.tdb' Apr 26 07:36:13 192.168.122.209 [55923.989364] [tdb] Close table 'sessions0.tdb' Apr 26 07:36:16 192.168.122.209 [55927.128435] [tdb] Close table 'cache0.tdb' Apr 26 07:36:16 192.168.122.209 [55927.374677] [tdb] Close table 'filter0.tdb' Apr 26 07:36:16 192.168.122.209 [55927.375115] [tempesta fw] modules are stopped Apr 26 07:36:17 192.168.122.209 [55927.584668] [tempesta fw] exiting... Apr 26 07:36:17 192.168.122.209 [55927.725968] [tdb] Shutdown Tempesta DB Apr 26 07:36:17 192.168.122.209 [55927.922293] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_then_fresh_resp Apr 26 07:36:17 192.168.122.209 [55927.935637] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_max_stale Apr 26 07:36:18 192.168.122.209 [55928.908266] [tdb] Start Tempesta DB Apr 26 07:36:18 192.168.122.209 [55929.056661] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:36:20 192.168.122.209 [55930.510318] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [55930.510318] Maybe that's fine, but it's worth checking the [55930.510318] config - if there is no relations between the [55930.510318] names, then host name confusion attack is possible. Apr 26 07:36:20 192.168.122.209 [55930.612620] [tempesta fw] Configuration processing is completed. Apr 26 07:36:20 192.168.122.209 [55930.662790] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:36:20 192.168.122.209 [55931.083467] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:36:20 192.168.122.209 [55931.110056] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:36:20 192.168.122.209 [55931.136021] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:36:20 192.168.122.209 [55931.180685] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:36:20 192.168.122.209 [55931.228601] [tempesta fw] Tempesta FW is ready Apr 26 07:36:32 192.168.122.209 [55942.907007] [tdb] Close table 'client0.tdb' Apr 26 07:36:32 192.168.122.209 [55943.099574] [tdb] Close table 'sessions0.tdb' Apr 26 07:36:35 192.168.122.209 [55946.360066] [tdb] Close table 'cache0.tdb' Apr 26 07:36:36 192.168.122.209 [55946.606533] [tdb] Close table 'filter0.tdb' Apr 26 07:36:36 192.168.122.209 [55946.606973] [tempesta fw] modules are stopped Apr 26 07:36:36 192.168.122.209 [55946.804865] [tempesta fw] exiting... Apr 26 07:36:36 192.168.122.209 [55946.940924] [tdb] Shutdown Tempesta DB Apr 26 07:36:36 192.168.122.209 [55947.144168] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_max_stale Apr 26 07:36:36 192.168.122.209 [55947.164778] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_stale_if_error_not_use_304 Apr 26 07:36:37 192.168.122.209 [55948.271406] [tdb] Start Tempesta DB Apr 26 07:36:37 192.168.122.209 [55948.409652] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:36:39 192.168.122.209 [55949.914543] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [55949.914543] Maybe that's fine, but it's worth checking the [55949.914543] config - if there is no relations between the [55949.914543] names, then host name confusion attack is possible. Apr 26 07:36:39 192.168.122.209 [55949.989179] [tempesta fw] Configuration processing is completed. Apr 26 07:36:39 192.168.122.209 [55950.039656] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:36:39 192.168.122.209 [55950.462989] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:36:39 192.168.122.209 [55950.490186] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:36:40 192.168.122.209 [55950.517846] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:36:40 192.168.122.209 [55950.560851] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:36:40 192.168.122.209 [55950.600764] [tempesta fw] Tempesta FW is ready Apr 26 07:36:42 192.168.122.209 [55953.320886] [tdb] Close table 'client0.tdb' Apr 26 07:36:42 192.168.122.209 [55953.509175] [tdb] Close table 'sessions0.tdb' Apr 26 07:36:46 192.168.122.209 [55956.746398] [tdb] Close table 'cache0.tdb' Apr 26 07:36:46 192.168.122.209 [55956.998937] [tdb] Close table 'filter0.tdb' Apr 26 07:36:46 192.168.122.209 [55956.999403] [tempesta fw] modules are stopped Apr 26 07:36:46 192.168.122.209 [55957.205242] [tempesta fw] exiting... Apr 26 07:36:46 192.168.122.209 [55957.322734] [tdb] Shutdown Tempesta DB Apr 26 07:36:47 192.168.122.209 [55957.542810] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_stale_if_error_not_use_304 Apr 26 07:36:47 192.168.122.209 [55957.559033] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_fresh_200 Apr 26 07:36:48 192.168.122.209 [55958.659388] [tdb] Start Tempesta DB Apr 26 07:36:48 192.168.122.209 [55958.801327] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:36:49 192.168.122.209 [55960.250665] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [55960.250665] Maybe that's fine, but it's worth checking the [55960.250665] config - if there is no relations between the [55960.250665] names, then host name confusion attack is possible. Apr 26 07:36:49 192.168.122.209 [55960.349063] [tempesta fw] Configuration processing is completed. Apr 26 07:36:49 192.168.122.209 [55960.402327] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:36:50 192.168.122.209 [55960.829963] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:36:50 192.168.122.209 [55960.856065] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:36:50 192.168.122.209 [55960.881761] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:36:50 192.168.122.209 [55960.920962] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:36:50 192.168.122.209 [55960.972961] [tempesta fw] Tempesta FW is ready Apr 26 07:36:54 192.168.122.209 [55964.566104] [tdb] Close table 'client0.tdb' Apr 26 07:36:54 192.168.122.209 [55964.752415] [tdb] Close table 'sessions0.tdb' Apr 26 07:36:57 192.168.122.209 [55967.974329] [tdb] Close table 'cache0.tdb' Apr 26 07:36:57 192.168.122.209 [55968.221275] [tdb] Close table 'filter0.tdb' Apr 26 07:36:57 192.168.122.209 [55968.221705] [tempesta fw] modules are stopped Apr 26 07:36:57 192.168.122.209 [55968.420779] [tempesta fw] exiting... Apr 26 07:36:58 192.168.122.209 [55968.549545] [tdb] Shutdown Tempesta DB Apr 26 07:36:58 192.168.122.209 [55968.767665] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_fresh_200 Apr 26 07:36:58 192.168.122.209 [55968.792781] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_fresh_403 Apr 26 07:36:59 192.168.122.209 [55969.802403] [tdb] Start Tempesta DB Apr 26 07:36:59 192.168.122.209 [55969.962273] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:37:00 192.168.122.209 [55971.490834] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [55971.490834] Maybe that's fine, but it's worth checking the [55971.490834] config - if there is no relations between the [55971.490834] names, then host name confusion attack is possible. Apr 26 07:37:01 192.168.122.209 [55971.589474] [tempesta fw] Configuration processing is completed. Apr 26 07:37:01 192.168.122.209 [55971.643795] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:37:01 192.168.122.209 [55972.063739] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:37:01 192.168.122.209 [55972.090623] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:37:01 192.168.122.209 [55972.118376] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:37:01 192.168.122.209 [55972.161036] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:37:01 192.168.122.209 [55972.205097] [tempesta fw] Tempesta FW is ready Apr 26 07:37:05 192.168.122.209 [55975.867685] [tdb] Close table 'client0.tdb' Apr 26 07:37:05 192.168.122.209 [55976.054706] [tdb] Close table 'sessions0.tdb' Apr 26 07:37:08 192.168.122.209 [55979.331747] [tdb] Close table 'cache0.tdb' Apr 26 07:37:09 192.168.122.209 [55979.548974] [tdb] Close table 'filter0.tdb' Apr 26 07:37:09 192.168.122.209 [55979.549419] [tempesta fw] modules are stopped Apr 26 07:37:09 192.168.122.209 [55979.771660] [tempesta fw] exiting... Apr 26 07:37:09 192.168.122.209 [55979.881890] [tdb] Shutdown Tempesta DB Apr 26 07:37:09 192.168.122.209 [55980.116256] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_fresh_403 Apr 26 07:37:09 192.168.122.209 [55980.131220] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_fresh_on_error_must_revalidate Apr 26 07:37:10 192.168.122.209 [55981.251736] [tdb] Start Tempesta DB Apr 26 07:37:10 192.168.122.209 [55981.399431] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:37:12 192.168.122.209 [55982.810887] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [55982.810887] Maybe that's fine, but it's worth checking the [55982.810887] config - if there is no relations between the [55982.810887] names, then host name confusion attack is possible. Apr 26 07:37:12 192.168.122.209 [55982.905645] [tempesta fw] Configuration processing is completed. Apr 26 07:37:12 192.168.122.209 [55982.955643] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:37:12 192.168.122.209 [55983.378407] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:37:12 192.168.122.209 [55983.406627] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:37:12 192.168.122.209 [55983.433141] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:37:12 192.168.122.209 [55983.473290] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:37:13 192.168.122.209 [55983.513252] [tempesta fw] Tempesta FW is ready Apr 26 07:37:16 192.168.122.209 [55987.157468] [tdb] Close table 'client0.tdb' Apr 26 07:37:16 192.168.122.209 [55987.346982] [tdb] Close table 'sessions0.tdb' Apr 26 07:37:20 192.168.122.209 [55990.560509] [tdb] Close table 'cache0.tdb' Apr 26 07:37:20 192.168.122.209 [55990.811277] [tdb] Close table 'filter0.tdb' Apr 26 07:37:20 192.168.122.209 [55990.811697] [tempesta fw] modules are stopped Apr 26 07:37:20 192.168.122.209 [55990.996817] [tempesta fw] exiting... Apr 26 07:37:20 192.168.122.209 [55991.113445] [tdb] Shutdown Tempesta DB Apr 26 07:37:20 192.168.122.209 [55991.322751] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_fresh_on_error_must_revalidate Apr 26 07:37:20 192.168.122.209 [55991.337605] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_fresh_on_error_proxy_revalidate Apr 26 07:37:21 192.168.122.209 [55992.459389] [tdb] Start Tempesta DB Apr 26 07:37:22 192.168.122.209 [55992.601886] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:37:23 192.168.122.209 [55994.103085] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [55994.103085] Maybe that's fine, but it's worth checking the [55994.103085] config - if there is no relations between the [55994.103085] names, then host name confusion attack is possible. Apr 26 07:37:23 192.168.122.209 [55994.201730] [tempesta fw] Configuration processing is completed. Apr 26 07:37:23 192.168.122.209 [55994.258523] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:37:24 192.168.122.209 [55994.675150] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:37:24 192.168.122.209 [55994.701446] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:37:24 192.168.122.209 [55994.727109] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:37:24 192.168.122.209 [55994.777471] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:37:24 192.168.122.209 [55994.841409] [tempesta fw] Tempesta FW is ready Apr 26 07:37:27 192.168.122.209 [55998.480439] [tdb] Close table 'client0.tdb' Apr 26 07:37:28 192.168.122.209 [55998.674059] [tdb] Close table 'sessions0.tdb' Apr 26 07:37:31 192.168.122.209 [56001.838881] [tdb] Close table 'cache0.tdb' Apr 26 07:37:31 192.168.122.209 [56002.075778] [tdb] Close table 'filter0.tdb' Apr 26 07:37:31 192.168.122.209 [56002.076213] [tempesta fw] modules are stopped Apr 26 07:37:31 192.168.122.209 [56002.262968] [tempesta fw] exiting... Apr 26 07:37:31 192.168.122.209 [56002.392614] [tdb] Shutdown Tempesta DB Apr 26 07:37:32 192.168.122.209 [56002.601474] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_fresh_on_error_proxy_revalidate Apr 26 07:37:32 192.168.122.209 [56002.628122] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_fresh_on_error_s_maxage Apr 26 07:37:33 192.168.122.209 [56003.698166] [tdb] Start Tempesta DB Apr 26 07:37:33 192.168.122.209 [56003.837479] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:37:34 192.168.122.209 [56005.315261] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56005.315261] Maybe that's fine, but it's worth checking the [56005.315261] config - if there is no relations between the [56005.315261] names, then host name confusion attack is possible. Apr 26 07:37:34 192.168.122.209 [56005.401836] [tempesta fw] Configuration processing is completed. Apr 26 07:37:34 192.168.122.209 [56005.451869] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:37:35 192.168.122.209 [56005.876620] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:37:35 192.168.122.209 [56005.915370] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:37:35 192.168.122.209 [56005.941626] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:37:35 192.168.122.209 [56005.985578] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:37:35 192.168.122.209 [56006.025521] [tempesta fw] Tempesta FW is ready Apr 26 07:37:39 192.168.122.209 [56009.660597] [tdb] Close table 'client0.tdb' Apr 26 07:37:39 192.168.122.209 [56009.863188] [tdb] Close table 'sessions0.tdb' Apr 26 07:37:42 192.168.122.209 [56013.092338] [tdb] Close table 'cache0.tdb' Apr 26 07:37:42 192.168.122.209 [56013.335347] [tdb] Close table 'filter0.tdb' Apr 26 07:37:42 192.168.122.209 [56013.335778] [tempesta fw] modules are stopped Apr 26 07:37:43 192.168.122.209 [56013.517099] [tempesta fw] exiting... Apr 26 07:37:43 192.168.122.209 [56013.661300] [tdb] Shutdown Tempesta DB Apr 26 07:37:43 192.168.122.209 [56013.901080] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_fresh_on_error_s_maxage Apr 26 07:37:43 192.168.122.209 [56013.915694] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_400 Apr 26 07:37:44 192.168.122.209 [56015.024773] [tdb] Start Tempesta DB Apr 26 07:37:44 192.168.122.209 [56015.172535] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:37:46 192.168.122.209 [56016.599388] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56016.599388] Maybe that's fine, but it's worth checking the [56016.599388] config - if there is no relations between the [56016.599388] names, then host name confusion attack is possible. Apr 26 07:37:46 192.168.122.209 [56016.690012] [tempesta fw] Configuration processing is completed. Apr 26 07:37:46 192.168.122.209 [56016.741381] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:37:46 192.168.122.209 [56017.157380] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:37:46 192.168.122.209 [56017.184523] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:37:46 192.168.122.209 [56017.212393] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:37:46 192.168.122.209 [56017.261709] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:37:46 192.168.122.209 [56017.305663] [tempesta fw] Tempesta FW is ready Apr 26 07:37:50 192.168.122.209 [56020.917914] [tdb] Close table 'client0.tdb' Apr 26 07:37:50 192.168.122.209 [56021.103162] [tdb] Close table 'sessions0.tdb' Apr 26 07:37:53 192.168.122.209 [56024.333582] [tdb] Close table 'cache0.tdb' Apr 26 07:37:54 192.168.122.209 [56024.606691] [tdb] Close table 'filter0.tdb' Apr 26 07:37:54 192.168.122.209 [56024.607146] [tempesta fw] modules are stopped Apr 26 07:37:54 192.168.122.209 [56024.825305] [tempesta fw] exiting... Apr 26 07:37:54 192.168.122.209 [56024.943879] [tdb] Shutdown Tempesta DB Apr 26 07:37:54 192.168.122.209 [56025.155000] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_400 Apr 26 07:37:54 192.168.122.209 [56025.167930] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_4xx_400 Apr 26 07:37:55 192.168.122.209 [56026.259561] [tdb] Start Tempesta DB Apr 26 07:37:55 192.168.122.209 [56026.399786] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:37:57 192.168.122.209 [56027.887591] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56027.887591] Maybe that's fine, but it's worth checking the [56027.887591] config - if there is no relations between the [56027.887591] names, then host name confusion attack is possible. Apr 26 07:37:57 192.168.122.209 [56027.990353] [tempesta fw] Configuration processing is completed. Apr 26 07:37:57 192.168.122.209 [56028.048156] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:37:57 192.168.122.209 [56028.502450] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:37:58 192.168.122.209 [56028.532308] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:37:58 192.168.122.209 [56028.560988] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:37:58 192.168.122.209 [56028.601858] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:37:58 192.168.122.209 [56028.645830] [tempesta fw] Tempesta FW is ready Apr 26 07:38:01 192.168.122.209 [56032.253864] [tdb] Close table 'client0.tdb' Apr 26 07:38:01 192.168.122.209 [56032.441872] [tdb] Close table 'sessions0.tdb' Apr 26 07:38:05 192.168.122.209 [56035.694133] [tdb] Close table 'cache0.tdb' Apr 26 07:38:05 192.168.122.209 [56035.927129] [tdb] Close table 'filter0.tdb' Apr 26 07:38:05 192.168.122.209 [56035.927577] [tempesta fw] modules are stopped Apr 26 07:38:05 192.168.122.209 [56036.131574] [tempesta fw] exiting... Apr 26 07:38:05 192.168.122.209 [56036.249271] [tdb] Shutdown Tempesta DB Apr 26 07:38:05 192.168.122.209 [56036.488664] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_4xx_400 Apr 26 07:38:06 192.168.122.209 [56036.511020] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_4xx_403 Apr 26 07:38:07 192.168.122.209 [56037.589013] [tdb] Start Tempesta DB Apr 26 07:38:07 192.168.122.209 [56037.746306] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:38:08 192.168.122.209 [56039.359707] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56039.359707] Maybe that's fine, but it's worth checking the [56039.359707] config - if there is no relations between the [56039.359707] names, then host name confusion attack is possible. Apr 26 07:38:08 192.168.122.209 [56039.470337] [tempesta fw] Configuration processing is completed. Apr 26 07:38:09 192.168.122.209 [56039.529351] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:38:09 192.168.122.209 [56039.996952] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:38:09 192.168.122.209 [56040.028492] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:38:09 192.168.122.209 [56040.063997] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:38:09 192.168.122.209 [56040.146023] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:38:09 192.168.122.209 [56040.193979] [tempesta fw] Tempesta FW is ready Apr 26 07:38:13 192.168.122.209 [56043.824169] [tdb] Close table 'client0.tdb' Apr 26 07:38:13 192.168.122.209 [56044.021627] [tdb] Close table 'sessions0.tdb' Apr 26 07:38:16 192.168.122.209 [56047.312740] [tdb] Close table 'cache0.tdb' Apr 26 07:38:17 192.168.122.209 [56047.578374] [tdb] Close table 'filter0.tdb' Apr 26 07:38:17 192.168.122.209 [56047.578831] [tempesta fw] modules are stopped Apr 26 07:38:17 192.168.122.209 [56047.836847] [tempesta fw] exiting... Apr 26 07:38:17 192.168.122.209 [56047.991477] [tdb] Shutdown Tempesta DB Apr 26 07:38:17 192.168.122.209 [56048.207719] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_4xx_403 Apr 26 07:38:17 192.168.122.209 [56048.226939] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_4xx_5xx Apr 26 07:38:18 192.168.122.209 [56049.298516] [tdb] Start Tempesta DB Apr 26 07:38:18 192.168.122.209 [56049.458153] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:38:20 192.168.122.209 [56050.939816] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56050.939816] Maybe that's fine, but it's worth checking the [56050.939816] config - if there is no relations between the [56050.939816] names, then host name confusion attack is possible. Apr 26 07:38:20 192.168.122.209 [56051.054112] [tempesta fw] Configuration processing is completed. Apr 26 07:38:20 192.168.122.209 [56051.115382] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:38:21 192.168.122.209 [56051.541746] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:38:21 192.168.122.209 [56051.569460] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:38:21 192.168.122.209 [56051.596917] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:38:21 192.168.122.209 [56051.638160] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:38:21 192.168.122.209 [56051.678099] [tempesta fw] Tempesta FW is ready Apr 26 07:38:24 192.168.122.209 [56055.281251] [tdb] Close table 'client0.tdb' Apr 26 07:38:24 192.168.122.209 [56055.481630] [tdb] Close table 'sessions0.tdb' Apr 26 07:38:28 192.168.122.209 [56058.911543] [tdb] Close table 'cache0.tdb' Apr 26 07:38:28 192.168.122.209 [56059.165946] [tdb] Close table 'filter0.tdb' Apr 26 07:38:28 192.168.122.209 [56059.166404] [tempesta fw] modules are stopped Apr 26 07:38:28 192.168.122.209 [56059.330413] [tempesta fw] exiting... Apr 26 07:38:28 192.168.122.209 [56059.426361] [tdb] Shutdown Tempesta DB Apr 26 07:38:29 192.168.122.209 [56059.620096] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_4xx_5xx Apr 26 07:38:29 192.168.122.209 [56059.634613] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_500 Apr 26 07:38:30 192.168.122.209 [56060.733965] [tdb] Start Tempesta DB Apr 26 07:38:30 192.168.122.209 [56060.876467] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:38:31 192.168.122.209 [56062.447964] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56062.447964] Maybe that's fine, but it's worth checking the [56062.447964] config - if there is no relations between the [56062.447964] names, then host name confusion attack is possible. Apr 26 07:38:32 192.168.122.209 [56062.550254] [tempesta fw] Configuration processing is completed. Apr 26 07:38:32 192.168.122.209 [56062.601691] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:38:32 192.168.122.209 [56063.035325] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:38:32 192.168.122.209 [56063.076413] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:38:32 192.168.122.209 [56063.105120] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:38:32 192.168.122.209 [56063.170284] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:38:32 192.168.122.209 [56063.218262] [tempesta fw] Tempesta FW is ready Apr 26 07:38:36 192.168.122.209 [56066.852962] [tdb] Close table 'client0.tdb' Apr 26 07:38:36 192.168.122.209 [56067.051933] [tdb] Close table 'sessions0.tdb' Apr 26 07:38:39 192.168.122.209 [56070.339788] [tdb] Close table 'cache0.tdb' Apr 26 07:38:40 192.168.122.209 [56070.599547] [tdb] Close table 'filter0.tdb' Apr 26 07:38:40 192.168.122.209 [56070.600006] [tempesta fw] modules are stopped Apr 26 07:38:40 192.168.122.209 [56070.775353] [tempesta fw] exiting... Apr 26 07:38:40 192.168.122.209 [56070.886214] [tdb] Shutdown Tempesta DB Apr 26 07:38:40 192.168.122.209 [56071.129512] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_500 Apr 26 07:38:40 192.168.122.209 [56071.148293] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_5xx_500 Apr 26 07:38:41 192.168.122.209 [56072.354752] [tdb] Start Tempesta DB Apr 26 07:38:41 192.168.122.209 [56072.510694] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:38:43 192.168.122.209 [56074.012166] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56074.012166] Maybe that's fine, but it's worth checking the [56074.012166] config - if there is no relations between the [56074.012166] names, then host name confusion attack is possible. Apr 26 07:38:43 192.168.122.209 [56074.106477] [tempesta fw] Configuration processing is completed. Apr 26 07:38:43 192.168.122.209 [56074.151936] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:38:44 192.168.122.209 [56074.579089] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:38:44 192.168.122.209 [56074.625376] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:38:44 192.168.122.209 [56074.660885] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:38:44 192.168.122.209 [56074.718458] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:38:44 192.168.122.209 [56074.758334] [tempesta fw] Tempesta FW is ready Apr 26 07:38:47 192.168.122.209 [56078.402057] [tdb] Close table 'client0.tdb' Apr 26 07:38:48 192.168.122.209 [56078.599287] [tdb] Close table 'sessions0.tdb' Apr 26 07:38:51 192.168.122.209 [56081.825596] [tdb] Close table 'cache0.tdb' Apr 26 07:38:51 192.168.122.209 [56082.080158] [tdb] Close table 'filter0.tdb' Apr 26 07:38:51 192.168.122.209 [56082.080598] [tempesta fw] modules are stopped Apr 26 07:38:51 192.168.122.209 [56082.282267] [tempesta fw] exiting... Apr 26 07:38:51 192.168.122.209 [56082.397086] [tdb] Shutdown Tempesta DB Apr 26 07:38:52 192.168.122.209 [56082.623943] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_5xx_500 Apr 26 07:38:52 192.168.122.209 [56082.643153] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_5xx_502 Apr 26 07:38:53 192.168.122.209 [56083.840567] [tdb] Start Tempesta DB Apr 26 07:38:53 192.168.122.209 [56083.985056] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:38:55 192.168.122.209 [56085.612230] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56085.612230] Maybe that's fine, but it's worth checking the [56085.612230] config - if there is no relations between the [56085.612230] names, then host name confusion attack is possible. Apr 26 07:38:55 192.168.122.209 [56085.714530] [tempesta fw] Configuration processing is completed. Apr 26 07:38:55 192.168.122.209 [56085.772295] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:38:55 192.168.122.209 [56086.181732] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:38:55 192.168.122.209 [56086.208358] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:38:55 192.168.122.209 [56086.235753] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:38:55 192.168.122.209 [56086.274581] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:38:55 192.168.122.209 [56086.314534] [tempesta fw] Tempesta FW is ready Apr 26 07:38:59 192.168.122.209 [56089.944218] [tdb] Close table 'client0.tdb' Apr 26 07:38:59 192.168.122.209 [56090.148716] [tdb] Close table 'sessions0.tdb' Apr 26 07:39:02 192.168.122.209 [56093.376534] [tdb] Close table 'cache0.tdb' Apr 26 07:39:03 192.168.122.209 [56093.605590] [tdb] Close table 'filter0.tdb' Apr 26 07:39:03 192.168.122.209 [56093.606021] [tempesta fw] modules are stopped Apr 26 07:39:03 192.168.122.209 [56093.823183] [tempesta fw] exiting... Apr 26 07:39:03 192.168.122.209 [56093.964556] [tdb] Shutdown Tempesta DB Apr 26 07:39:03 192.168.122.209 [56094.208406] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_5xx_502 Apr 26 07:39:03 192.168.122.209 [56094.227058] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_if_error_duplicated_req Apr 26 07:39:04 192.168.122.209 [56095.462054] [tdb] Start Tempesta DB Apr 26 07:39:05 192.168.122.209 [56095.606827] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:39:06 192.168.122.209 [56097.068368] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56097.068368] Maybe that's fine, but it's worth checking the [56097.068368] config - if there is no relations between the [56097.068368] names, then host name confusion attack is possible. Apr 26 07:39:06 192.168.122.209 [56097.147023] [tempesta fw] Configuration processing is completed. Apr 26 07:39:06 192.168.122.209 [56097.197406] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:39:07 192.168.122.209 [56097.630240] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:39:07 192.168.122.209 [56097.656876] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:39:07 192.168.122.209 [56097.683141] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:39:07 192.168.122.209 [56097.730689] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:39:07 192.168.122.209 [56097.774681] [tempesta fw] Tempesta FW is ready Apr 26 07:39:07 192.168.122.209 [56098.334587] [tdb] Close table 'client0.tdb' Apr 26 07:39:08 192.168.122.209 [56098.547302] [tdb] Close table 'sessions0.tdb' Apr 26 07:39:11 192.168.122.209 [56101.742255] [tdb] Close table 'cache0.tdb' Apr 26 07:39:11 192.168.122.209 [56102.000651] [tdb] Close table 'filter0.tdb' Apr 26 07:39:11 192.168.122.209 [56102.001113] [tempesta fw] modules are stopped Apr 26 07:39:11 192.168.122.209 [56102.178594] [tempesta fw] exiting... Apr 26 07:39:11 192.168.122.209 [56102.318204] [tdb] Shutdown Tempesta DB Apr 26 07:39:12 192.168.122.209 [56102.535862] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_if_error_duplicated_req Apr 26 07:39:12 192.168.122.209 [56102.555339] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_if_error_duplicated_resp Apr 26 07:39:13 192.168.122.209 [56103.627310] [tdb] Start Tempesta DB Apr 26 07:39:13 192.168.122.209 [56103.767522] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:39:14 192.168.122.209 [56105.143993] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56105.143993] Maybe that's fine, but it's worth checking the [56105.143993] config - if there is no relations between the [56105.143993] names, then host name confusion attack is possible. Apr 26 07:39:14 192.168.122.209 [56105.215156] [tempesta fw] Configuration processing is completed. Apr 26 07:39:14 192.168.122.209 [56105.266581] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:39:15 192.168.122.209 [56105.693918] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:39:15 192.168.122.209 [56105.722177] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:39:15 192.168.122.209 [56105.750558] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:39:15 192.168.122.209 [56105.794794] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:39:15 192.168.122.209 [56105.834781] [tempesta fw] Tempesta FW is ready Apr 26 07:39:15 192.168.122.209 [56105.985869] [tempesta fw] Warning: Parser error: state=Resp_HdrCache_CtrlV input(-0)=0x31('1') data_len=1 off=0 Apr 26 07:39:15 192.168.122.209 [56105.987704] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 07:39:15 192.168.122.209 [56106.404723] [tdb] Close table 'client0.tdb' Apr 26 07:39:16 192.168.122.209 [56106.595180] [tdb] Close table 'sessions0.tdb' Apr 26 07:39:19 192.168.122.209 [56109.780638] [tdb] Close table 'cache0.tdb' Apr 26 07:39:19 192.168.122.209 [56110.030168] [tdb] Close table 'filter0.tdb' Apr 26 07:39:19 192.168.122.209 [56110.030604] [tempesta fw] modules are stopped Apr 26 07:39:19 192.168.122.209 [56110.207907] [tempesta fw] exiting... Apr 26 07:39:19 192.168.122.209 [56110.336096] [tdb] Shutdown Tempesta DB Apr 26 07:39:20 192.168.122.209 [56110.562536] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_if_error_duplicated_resp Apr 26 07:39:20 192.168.122.209 [56110.587354] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_if_error_param_req Apr 26 07:39:21 192.168.122.209 [56111.656802] [tdb] Start Tempesta DB Apr 26 07:39:21 192.168.122.209 [56111.795061] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:39:22 192.168.122.209 [56113.192581] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56113.192581] Maybe that's fine, but it's worth checking the [56113.192581] config - if there is no relations between the [56113.192581] names, then host name confusion attack is possible. Apr 26 07:39:22 192.168.122.209 [56113.283292] [tempesta fw] Configuration processing is completed. Apr 26 07:39:22 192.168.122.209 [56113.333265] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:39:23 192.168.122.209 [56113.752256] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:39:23 192.168.122.209 [56113.779499] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:39:23 192.168.122.209 [56113.805759] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:39:23 192.168.122.209 [56113.850915] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:39:23 192.168.122.209 [56113.894865] [tempesta fw] Tempesta FW is ready Apr 26 07:39:27 192.168.122.209 [56117.748906] [tdb] Close table 'client0.tdb' Apr 26 07:39:27 192.168.122.209 [56117.944370] [tdb] Close table 'sessions0.tdb' Apr 26 07:39:30 192.168.122.209 [56121.159896] [tdb] Close table 'cache0.tdb' Apr 26 07:39:30 192.168.122.209 [56121.399446] [tdb] Close table 'filter0.tdb' Apr 26 07:39:30 192.168.122.209 [56121.399875] [tempesta fw] modules are stopped Apr 26 07:39:31 192.168.122.209 [56121.678671] [tempesta fw] exiting... Apr 26 07:39:31 192.168.122.209 [56121.788503] [tdb] Shutdown Tempesta DB Apr 26 07:39:31 192.168.122.209 [56121.989027] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_if_error_param_req Apr 26 07:39:31 192.168.122.209 [56122.023020] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_if_error_param_resp Apr 26 07:39:32 192.168.122.209 [56123.090157] [tdb] Start Tempesta DB Apr 26 07:39:32 192.168.122.209 [56123.228629] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:39:34 192.168.122.209 [56124.752605] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56124.752605] Maybe that's fine, but it's worth checking the [56124.752605] config - if there is no relations between the [56124.752605] names, then host name confusion attack is possible. Apr 26 07:39:34 192.168.122.209 [56124.843353] [tempesta fw] Configuration processing is completed. Apr 26 07:39:34 192.168.122.209 [56124.893965] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:39:34 192.168.122.209 [56125.323310] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:39:34 192.168.122.209 [56125.349335] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:39:34 192.168.122.209 [56125.379434] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:39:34 192.168.122.209 [56125.419080] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:39:34 192.168.122.209 [56125.463011] [tempesta fw] Tempesta FW is ready Apr 26 07:39:38 192.168.122.209 [56129.232827] [tdb] Close table 'client0.tdb' Apr 26 07:39:38 192.168.122.209 [56129.422235] [tdb] Close table 'sessions0.tdb' Apr 26 07:39:42 192.168.122.209 [56132.609356] [tdb] Close table 'cache0.tdb' Apr 26 07:39:42 192.168.122.209 [56132.848189] [tdb] Close table 'filter0.tdb' Apr 26 07:39:42 192.168.122.209 [56132.849088] [tempesta fw] modules are stopped Apr 26 07:39:42 192.168.122.209 [56133.023272] [tempesta fw] exiting... Apr 26 07:39:42 192.168.122.209 [56133.175966] [tdb] Shutdown Tempesta DB Apr 26 07:39:42 192.168.122.209 [56133.374363] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_if_error_param_resp Apr 26 07:39:42 192.168.122.209 [56133.395542] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_invalid_response Apr 26 07:39:43 192.168.122.209 [56134.473741] [tdb] Start Tempesta DB Apr 26 07:39:44 192.168.122.209 [56134.622893] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:39:45 192.168.122.209 [56136.128224] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56136.128224] Maybe that's fine, but it's worth checking the [56136.128224] config - if there is no relations between the [56136.128224] names, then host name confusion attack is possible. Apr 26 07:39:45 192.168.122.209 [56136.223494] [tempesta fw] Configuration processing is completed. Apr 26 07:39:45 192.168.122.209 [56136.285328] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:39:46 192.168.122.209 [56136.714972] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:39:46 192.168.122.209 [56136.741759] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:39:46 192.168.122.209 [56136.768388] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:39:46 192.168.122.209 [56136.811187] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:39:46 192.168.122.209 [56136.851168] [tempesta fw] Tempesta FW is ready Apr 26 07:39:49 192.168.122.209 [56140.035907] [tempesta fw] Warning: Parser error: state=RGen_HdrOtherN input(-0)=0x3e('>') data_len=1 off=0 Apr 26 07:39:49 192.168.122.209 [56140.497598] [tdb] Close table 'client0.tdb' Apr 26 07:39:50 192.168.122.209 [56140.682982] [tdb] Close table 'sessions0.tdb' Apr 26 07:39:53 192.168.122.209 [56143.840233] [tdb] Close table 'cache0.tdb' Apr 26 07:39:53 192.168.122.209 [56144.069392] [tdb] Close table 'filter0.tdb' Apr 26 07:39:53 192.168.122.209 [56144.069828] [tempesta fw] modules are stopped Apr 26 07:39:53 192.168.122.209 [56144.257228] [tempesta fw] exiting... Apr 26 07:39:53 192.168.122.209 [56144.369088] [tdb] Shutdown Tempesta DB Apr 26 07:39:54 192.168.122.209 [56144.607366] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_invalid_response Apr 26 07:39:54 192.168.122.209 [56144.632268] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_then_fresh_req Apr 26 07:39:55 192.168.122.209 [56145.672590] [tdb] Start Tempesta DB Apr 26 07:39:55 192.168.122.209 [56145.812450] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:39:56 192.168.122.209 [56147.308574] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56147.308574] Maybe that's fine, but it's worth checking the [56147.308574] config - if there is no relations between the [56147.308574] names, then host name confusion attack is possible. Apr 26 07:39:56 192.168.122.209 [56147.383646] [tempesta fw] Configuration processing is completed. Apr 26 07:39:56 192.168.122.209 [56147.437181] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:39:57 192.168.122.209 [56147.852772] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:39:57 192.168.122.209 [56147.892632] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:39:57 192.168.122.209 [56147.918327] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:39:57 192.168.122.209 [56147.975249] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:39:57 192.168.122.209 [56148.027290] [tempesta fw] Tempesta FW is ready Apr 26 07:40:04 192.168.122.209 [56154.649334] [tdb] Close table 'client0.tdb' Apr 26 07:40:04 192.168.122.209 [56154.846150] [tdb] Close table 'sessions0.tdb' Apr 26 07:40:07 192.168.122.209 [56158.023277] [tdb] Close table 'cache0.tdb' Apr 26 07:40:07 192.168.122.209 [56158.264537] [tdb] Close table 'filter0.tdb' Apr 26 07:40:07 192.168.122.209 [56158.264985] [tempesta fw] modules are stopped Apr 26 07:40:07 192.168.122.209 [56158.481141] [tempesta fw] exiting... Apr 26 07:40:08 192.168.122.209 [56158.611319] [tdb] Shutdown Tempesta DB Apr 26 07:40:08 192.168.122.209 [56158.859300] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_then_fresh_req Apr 26 07:40:08 192.168.122.209 [56158.872766] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_then_fresh_resp Apr 26 07:40:09 192.168.122.209 [56159.937555] [tdb] Start Tempesta DB Apr 26 07:40:09 192.168.122.209 [56160.076917] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:40:11 192.168.122.209 [56161.544438] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56161.544438] Maybe that's fine, but it's worth checking the [56161.544438] config - if there is no relations between the [56161.544438] names, then host name confusion attack is possible. Apr 26 07:40:11 192.168.122.209 [56161.627483] [tempesta fw] Configuration processing is completed. Apr 26 07:40:11 192.168.122.209 [56161.680147] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:40:11 192.168.122.209 [56162.103476] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:40:11 192.168.122.209 [56162.130247] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:40:11 192.168.122.209 [56162.156344] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:40:11 192.168.122.209 [56162.203492] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:40:11 192.168.122.209 [56162.243487] [tempesta fw] Tempesta FW is ready Apr 26 07:40:18 192.168.122.209 [56168.964390] [tdb] Close table 'client0.tdb' Apr 26 07:40:18 192.168.122.209 [56169.160754] [tdb] Close table 'sessions0.tdb' Apr 26 07:40:21 192.168.122.209 [56172.331851] [tdb] Close table 'cache0.tdb' Apr 26 07:40:22 192.168.122.209 [56172.569136] [tdb] Close table 'filter0.tdb' Apr 26 07:40:22 192.168.122.209 [56172.569582] [tempesta fw] modules are stopped Apr 26 07:40:22 192.168.122.209 [56172.789133] [tempesta fw] exiting... Apr 26 07:40:22 192.168.122.209 [56172.928517] [tdb] Shutdown Tempesta DB Apr 26 07:40:22 192.168.122.209 [56173.136737] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_then_fresh_resp Apr 26 07:40:22 192.168.122.209 [56173.147883] Start test: cache.test_cache_stale.TestCacheUseStaleTimeoutH2.test_timeout_no_stale Apr 26 07:40:23 192.168.122.209 [56174.267160] [tdb] Start Tempesta DB Apr 26 07:40:23 192.168.122.209 [56174.389314] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:40:25 192.168.122.209 [56175.861344] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56175.861344] Maybe that's fine, but it's worth checking the [56175.861344] config - if there is no relations between the [56175.861344] names, then host name confusion attack is possible. Apr 26 07:40:25 192.168.122.209 [56175.967960] [tempesta fw] Configuration processing is completed. Apr 26 07:40:25 192.168.122.209 [56176.018078] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:40:25 192.168.122.209 [56176.441917] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:40:25 192.168.122.209 [56176.469059] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:40:25 192.168.122.209 [56176.496398] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:40:26 192.168.122.209 [56176.535638] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:40:26 192.168.122.209 [56176.575669] [tempesta fw] Tempesta FW is ready Apr 26 07:40:29 192.168.122.209 [56179.855820] [tempesta fw] Warning: request evicted: the number of retries exceeded, status 504: 127.0.0.2 Apr 26 07:40:29 192.168.122.209 [56180.293191] [tdb] Close table 'client0.tdb' Apr 26 07:40:29 192.168.122.209 [56180.493783] [tdb] Close table 'sessions0.tdb' Apr 26 07:40:33 192.168.122.209 [56183.703230] [tdb] Close table 'cache0.tdb' Apr 26 07:40:33 192.168.122.209 [56183.939457] [tdb] Close table 'filter0.tdb' Apr 26 07:40:33 192.168.122.209 [56183.939902] [tempesta fw] modules are stopped Apr 26 07:40:33 192.168.122.209 [56184.154769] [tempesta fw] exiting... Apr 26 07:40:33 192.168.122.209 [56184.300403] [tdb] Shutdown Tempesta DB Apr 26 07:40:34 192.168.122.209 [56184.531382] End test: cache.test_cache_stale.TestCacheUseStaleTimeoutH2.test_timeout_no_stale Apr 26 07:40:34 192.168.122.209 [56184.550523] Start test: cache.test_cache_stale.TestCacheUseStaleTimeoutH2.test_use_stale_timeout Apr 26 07:40:35 192.168.122.209 [56185.605553] [tdb] Start Tempesta DB Apr 26 07:40:35 192.168.122.209 [56185.746833] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:40:36 192.168.122.209 [56187.157468] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56187.157468] Maybe that's fine, but it's worth checking the [56187.157468] config - if there is no relations between the [56187.157468] names, then host name confusion attack is possible. Apr 26 07:40:36 192.168.122.209 [56187.248223] [tempesta fw] Configuration processing is completed. Apr 26 07:40:36 192.168.122.209 [56187.299800] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:40:37 192.168.122.209 [56187.728163] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:40:37 192.168.122.209 [56187.755001] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:40:37 192.168.122.209 [56187.781114] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:40:37 192.168.122.209 [56187.823795] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:40:37 192.168.122.209 [56187.863831] [tempesta fw] Tempesta FW is ready Apr 26 07:40:40 192.168.122.209 [56191.119998] [tempesta fw] Warning: request evicted: the number of retries exceeded, status 504: 127.0.0.2 Apr 26 07:40:41 192.168.122.209 [56191.540647] [tdb] Close table 'client0.tdb' Apr 26 07:40:41 192.168.122.209 [56191.730058] [tdb] Close table 'sessions0.tdb' Apr 26 07:40:44 192.168.122.209 [56194.881852] [tdb] Close table 'cache0.tdb' Apr 26 07:40:44 192.168.122.209 [56195.129480] [tdb] Close table 'filter0.tdb' Apr 26 07:40:44 192.168.122.209 [56195.129912] [tempesta fw] modules are stopped Apr 26 07:40:44 192.168.122.209 [56195.317912] [tempesta fw] exiting... Apr 26 07:40:44 192.168.122.209 [56195.441213] [tdb] Shutdown Tempesta DB Apr 26 07:40:45 192.168.122.209 [56195.654599] End test: cache.test_cache_stale.TestCacheUseStaleTimeoutH2.test_use_stale_timeout Apr 26 07:40:45 192.168.122.209 [56195.671232] Start test: cache.test_cache_stale.TestCacheUseStaleTimeoutHttp.test_timeout_no_stale Apr 26 07:40:46 192.168.122.209 [56196.660362] [tdb] Start Tempesta DB Apr 26 07:40:46 192.168.122.209 [56196.788687] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:40:47 192.168.122.209 [56198.213638] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56198.213638] Maybe that's fine, but it's worth checking the [56198.213638] config - if there is no relations between the [56198.213638] names, then host name confusion attack is possible. Apr 26 07:40:47 192.168.122.209 [56198.308374] [tempesta fw] Configuration processing is completed. Apr 26 07:40:47 192.168.122.209 [56198.368089] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:40:48 192.168.122.209 [56198.792977] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:40:48 192.168.122.209 [56198.828218] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:40:48 192.168.122.209 [56198.855327] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:40:48 192.168.122.209 [56198.899959] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:40:48 192.168.122.209 [56198.943929] [tempesta fw] Tempesta FW is ready Apr 26 07:40:51 192.168.122.209 [56202.180441] [tempesta fw] Warning: request evicted: the number of retries exceeded, status 504: 127.0.0.2 Apr 26 07:40:52 192.168.122.209 [56202.612552] [tdb] Close table 'client0.tdb' Apr 26 07:40:52 192.168.122.209 [56202.807298] [tdb] Close table 'sessions0.tdb' Apr 26 07:40:55 192.168.122.209 [56206.145481] [tdb] Close table 'cache0.tdb' Apr 26 07:40:55 192.168.122.209 [56206.382198] [tdb] Close table 'filter0.tdb' Apr 26 07:40:55 192.168.122.209 [56206.382661] [tempesta fw] modules are stopped Apr 26 07:40:56 192.168.122.209 [56206.594715] [tempesta fw] exiting... Apr 26 07:40:56 192.168.122.209 [56206.728430] [tdb] Shutdown Tempesta DB Apr 26 07:40:56 192.168.122.209 [56206.975787] End test: cache.test_cache_stale.TestCacheUseStaleTimeoutHttp.test_timeout_no_stale Apr 26 07:40:56 192.168.122.209 [56206.986767] Start test: cache.test_cache_stale.TestCacheUseStaleTimeoutHttp.test_use_stale_timeout Apr 26 07:40:57 192.168.122.209 [56208.025308] [tdb] Start Tempesta DB Apr 26 07:40:57 192.168.122.209 [56208.170479] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:40:59 192.168.122.209 [56209.657792] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56209.657792] Maybe that's fine, but it's worth checking the [56209.657792] config - if there is no relations between the [56209.657792] names, then host name confusion attack is possible. Apr 26 07:40:59 192.168.122.209 [56209.756415] [tempesta fw] Configuration processing is completed. Apr 26 07:40:59 192.168.122.209 [56209.807028] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:40:59 192.168.122.209 [56210.230047] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:40:59 192.168.122.209 [56210.256935] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:40:59 192.168.122.209 [56210.283335] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:40:59 192.168.122.209 [56210.332136] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:40:59 192.168.122.209 [56210.372084] [tempesta fw] Tempesta FW is ready Apr 26 07:41:03 192.168.122.209 [56213.600538] [tempesta fw] Warning: request evicted: the number of retries exceeded, status 504: 127.0.0.2 Apr 26 07:41:03 192.168.122.209 [56214.029261] [tdb] Close table 'client0.tdb' Apr 26 07:41:03 192.168.122.209 [56214.236546] [tdb] Close table 'sessions0.tdb' Apr 26 07:41:06 192.168.122.209 [56217.448736] [tdb] Close table 'cache0.tdb' Apr 26 07:41:07 192.168.122.209 [56217.706830] [tdb] Close table 'filter0.tdb' Apr 26 07:41:07 192.168.122.209 [56217.707360] [tempesta fw] modules are stopped Apr 26 07:41:07 192.168.122.209 [56217.901899] [tempesta fw] exiting... Apr 26 07:41:07 192.168.122.209 [56218.037383] [tdb] Shutdown Tempesta DB Apr 26 07:41:07 192.168.122.209 [56218.279034] End test: cache.test_cache_stale.TestCacheUseStaleTimeoutHttp.test_use_stale_timeout Apr 26 07:41:07 192.168.122.209 [56218.297890] Start test: cache.test_conditional.TestConditionalH2.test_correct_none_match_and_modified_since Apr 26 07:41:08 192.168.122.209 [56219.396929] [tdb] Start Tempesta DB Apr 26 07:41:09 192.168.122.209 [56219.532121] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:41:10 192.168.122.209 [56221.021568] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56221.021568] Maybe that's fine, but it's worth checking the [56221.021568] config - if there is no relations between the [56221.021568] names, then host name confusion attack is possible. Apr 26 07:41:10 192.168.122.209 [56221.164406] [tempesta fw] Configuration processing is completed. Apr 26 07:41:10 192.168.122.209 [56221.230155] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:41:11 192.168.122.209 [56221.707445] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:41:11 192.168.122.209 [56221.737019] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:41:11 192.168.122.209 [56221.766979] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:41:11 192.168.122.209 [56221.816305] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:41:11 192.168.122.209 [56221.817700] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:41:11 192.168.122.209 [56221.860223] [tempesta fw] Tempesta FW is ready Apr 26 07:41:11 192.168.122.209 [56222.490079] [tdb] Close table 'client0.tdb' Apr 26 07:41:12 192.168.122.209 [56222.707034] [tdb] Close table 'sessions0.tdb' Apr 26 07:41:15 192.168.122.209 [56225.952794] [tdb] Close table 'cache0.tdb' Apr 26 07:41:15 192.168.122.209 [56226.193321] [tdb] Close table 'filter0.tdb' Apr 26 07:41:15 192.168.122.209 [56226.193773] [tempesta fw] modules are stopped Apr 26 07:41:15 192.168.122.209 [56226.371043] [tempesta fw] exiting... Apr 26 07:41:16 192.168.122.209 [56226.517967] [tdb] Shutdown Tempesta DB Apr 26 07:41:16 192.168.122.209 [56226.754055] End test: cache.test_conditional.TestConditionalH2.test_correct_none_match_and_modified_since Apr 26 07:41:16 192.168.122.209 [56226.771161] Start test: cache.test_conditional.TestConditionalH2.test_incorrect_none_match_and_correct_modified_since Apr 26 07:41:17 192.168.122.209 [56227.794944] [tdb] Start Tempesta DB Apr 26 07:41:17 192.168.122.209 [56227.925424] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:41:18 192.168.122.209 [56229.341633] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56229.341633] Maybe that's fine, but it's worth checking the [56229.341633] config - if there is no relations between the [56229.341633] names, then host name confusion attack is possible. Apr 26 07:41:18 192.168.122.209 [56229.472425] [tempesta fw] Configuration processing is completed. Apr 26 07:41:19 192.168.122.209 [56229.524303] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:41:19 192.168.122.209 [56229.943739] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:41:19 192.168.122.209 [56229.971158] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:41:19 192.168.122.209 [56229.997803] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:41:19 192.168.122.209 [56230.044352] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:41:19 192.168.122.209 [56230.046076] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:41:19 192.168.122.209 [56230.084351] [tempesta fw] Tempesta FW is ready Apr 26 07:41:20 192.168.122.209 [56230.771461] [tdb] Close table 'client0.tdb' Apr 26 07:41:20 192.168.122.209 [56230.965369] [tdb] Close table 'sessions0.tdb' Apr 26 07:41:23 192.168.122.209 [56234.291197] [tdb] Close table 'cache0.tdb' Apr 26 07:41:24 192.168.122.209 [56234.546667] [tdb] Close table 'filter0.tdb' Apr 26 07:41:24 192.168.122.209 [56234.547114] [tempesta fw] modules are stopped Apr 26 07:41:24 192.168.122.209 [56234.728843] [tempesta fw] exiting... Apr 26 07:41:24 192.168.122.209 [56234.856584] [tdb] Shutdown Tempesta DB Apr 26 07:41:24 192.168.122.209 [56235.081239] End test: cache.test_conditional.TestConditionalH2.test_incorrect_none_match_and_correct_modified_since Apr 26 07:41:24 192.168.122.209 [56235.093669] Start test: cache.test_conditional.TestConditionalH2.test_mod_since Apr 26 07:41:25 192.168.122.209 [56236.181965] [tdb] Start Tempesta DB Apr 26 07:41:25 192.168.122.209 [56236.338280] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:41:27 192.168.122.209 [56237.805741] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56237.805741] Maybe that's fine, but it's worth checking the [56237.805741] config - if there is no relations between the [56237.805741] names, then host name confusion attack is possible. Apr 26 07:41:27 192.168.122.209 [56237.940502] [tempesta fw] Configuration processing is completed. Apr 26 07:41:27 192.168.122.209 [56238.007875] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:41:27 192.168.122.209 [56238.483363] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:41:28 192.168.122.209 [56238.514117] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:41:28 192.168.122.209 [56238.544713] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:41:28 192.168.122.209 [56238.592507] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:41:28 192.168.122.209 [56238.594242] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:41:28 192.168.122.209 [56238.644480] [tempesta fw] Tempesta FW is ready Apr 26 07:41:28 192.168.122.209 [56239.323071] [tdb] Close table 'client0.tdb' Apr 26 07:41:29 192.168.122.209 [56239.523983] [tdb] Close table 'sessions0.tdb' Apr 26 07:41:32 192.168.122.209 [56242.840492] [tdb] Close table 'cache0.tdb' Apr 26 07:41:32 192.168.122.209 [56243.060081] [tdb] Close table 'filter0.tdb' Apr 26 07:41:32 192.168.122.209 [56243.060527] [tempesta fw] modules are stopped Apr 26 07:41:32 192.168.122.209 [56243.242252] [tempesta fw] exiting... Apr 26 07:41:32 192.168.122.209 [56243.372094] [tdb] Shutdown Tempesta DB Apr 26 07:41:33 192.168.122.209 [56243.635852] End test: cache.test_conditional.TestConditionalH2.test_mod_since Apr 26 07:41:33 192.168.122.209 [56243.647993] Start test: cache.test_conditional.TestConditionalH2.test_mod_since_nc Apr 26 07:41:34 192.168.122.209 [56244.698249] [tdb] Start Tempesta DB Apr 26 07:41:34 192.168.122.209 [56244.859253] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:41:35 192.168.122.209 [56246.289955] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56246.289955] Maybe that's fine, but it's worth checking the [56246.289955] config - if there is no relations between the [56246.289955] names, then host name confusion attack is possible. Apr 26 07:41:35 192.168.122.209 [56246.436619] [tempesta fw] Configuration processing is completed. Apr 26 07:41:35 192.168.122.209 [56246.496500] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:41:36 192.168.122.209 [56246.981736] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:41:36 192.168.122.209 [56247.015550] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:41:36 192.168.122.209 [56247.048678] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:41:36 192.168.122.209 [56247.092658] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:41:36 192.168.122.209 [56247.094422] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:41:36 192.168.122.209 [56247.132567] [tempesta fw] Tempesta FW is ready Apr 26 07:41:37 192.168.122.209 [56247.815318] [tdb] Close table 'client0.tdb' Apr 26 07:41:37 192.168.122.209 [56248.015524] [tdb] Close table 'sessions0.tdb' Apr 26 07:41:40 192.168.122.209 [56251.233016] [tdb] Close table 'cache0.tdb' Apr 26 07:41:40 192.168.122.209 [56251.493658] [tdb] Close table 'filter0.tdb' Apr 26 07:41:40 192.168.122.209 [56251.494094] [tempesta fw] modules are stopped Apr 26 07:41:41 192.168.122.209 [56251.716586] [tempesta fw] exiting... Apr 26 07:41:41 192.168.122.209 [56251.831210] [tdb] Shutdown Tempesta DB Apr 26 07:41:41 192.168.122.209 [56252.060648] End test: cache.test_conditional.TestConditionalH2.test_mod_since_nc Apr 26 07:41:41 192.168.122.209 [56252.080042] Start test: cache.test_conditional.TestConditionalH2.test_mod_since_nc_with_invalid_date Apr 26 07:41:42 192.168.122.209 [56253.113914] [tdb] Start Tempesta DB Apr 26 07:41:42 192.168.122.209 [56253.269603] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:41:44 192.168.122.209 [56254.681978] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56254.681978] Maybe that's fine, but it's worth checking the [56254.681978] config - if there is no relations between the [56254.681978] names, then host name confusion attack is possible. Apr 26 07:41:44 192.168.122.209 [56254.828730] [tempesta fw] Configuration processing is completed. Apr 26 07:41:44 192.168.122.209 [56254.880108] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:41:44 192.168.122.209 [56255.440937] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:41:44 192.168.122.209 [56255.477147] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:41:44 192.168.122.209 [56255.510711] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:41:45 192.168.122.209 [56255.548720] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:41:45 192.168.122.209 [56255.550524] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:41:45 192.168.122.209 [56255.592552] [tempesta fw] Tempesta FW is ready Apr 26 07:41:45 192.168.122.209 [56256.258098] [tdb] Close table 'client0.tdb' Apr 26 07:41:45 192.168.122.209 [56256.435521] [tdb] Close table 'sessions0.tdb' Apr 26 07:41:49 192.168.122.209 [56259.697490] [tdb] Close table 'cache0.tdb' Apr 26 07:41:49 192.168.122.209 [56259.972374] [tdb] Close table 'filter0.tdb' Apr 26 07:41:49 192.168.122.209 [56259.972824] [tempesta fw] modules are stopped Apr 26 07:41:49 192.168.122.209 [56260.187736] [tempesta fw] exiting... Apr 26 07:41:49 192.168.122.209 [56260.306489] [tdb] Shutdown Tempesta DB Apr 26 07:41:50 192.168.122.209 [56260.518485] End test: cache.test_conditional.TestConditionalH2.test_mod_since_nc_with_invalid_date Apr 26 07:41:50 192.168.122.209 [56260.538735] Start test: cache.test_conditional.TestConditionalH2.test_none_match Apr 26 07:41:51 192.168.122.209 [56261.633309] [tdb] Start Tempesta DB Apr 26 07:41:51 192.168.122.209 [56261.799549] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:41:52 192.168.122.209 [56263.302073] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56263.302073] Maybe that's fine, but it's worth checking the [56263.302073] config - if there is no relations between the [56263.302073] names, then host name confusion attack is possible. Apr 26 07:41:52 192.168.122.209 [56263.440807] [tempesta fw] Configuration processing is completed. Apr 26 07:41:52 192.168.122.209 [56263.498004] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:41:53 192.168.122.209 [56263.922196] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:41:53 192.168.122.209 [56263.949879] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:41:53 192.168.122.209 [56263.986585] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:41:53 192.168.122.209 [56264.028819] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:41:53 192.168.122.209 [56264.030593] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:41:53 192.168.122.209 [56264.092744] [tempesta fw] Tempesta FW is ready Apr 26 07:41:54 192.168.122.209 [56264.772994] [tdb] Close table 'client0.tdb' Apr 26 07:41:54 192.168.122.209 [56264.976001] [tdb] Close table 'sessions0.tdb' Apr 26 07:41:57 192.168.122.209 [56268.174416] [tdb] Close table 'cache0.tdb' Apr 26 07:41:57 192.168.122.209 [56268.419338] [tdb] Close table 'filter0.tdb' Apr 26 07:41:57 192.168.122.209 [56268.419781] [tempesta fw] modules are stopped Apr 26 07:41:58 192.168.122.209 [56268.588893] [tempesta fw] exiting... Apr 26 07:41:58 192.168.122.209 [56268.719022] [tdb] Shutdown Tempesta DB Apr 26 07:41:58 192.168.122.209 [56268.951280] End test: cache.test_conditional.TestConditionalH2.test_none_match Apr 26 07:41:58 192.168.122.209 [56268.979947] Start test: cache.test_conditional.TestConditionalH2.test_none_match_HEAD Apr 26 07:41:59 192.168.122.209 [56270.001067] [tdb] Start Tempesta DB Apr 26 07:41:59 192.168.122.209 [56270.132265] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:42:01 192.168.122.209 [56271.582214] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56271.582214] Maybe that's fine, but it's worth checking the [56271.582214] config - if there is no relations between the [56271.582214] names, then host name confusion attack is possible. Apr 26 07:42:01 192.168.122.209 [56271.732902] [tempesta fw] Configuration processing is completed. Apr 26 07:42:01 192.168.122.209 [56271.783433] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:42:01 192.168.122.209 [56272.212774] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:42:01 192.168.122.209 [56272.240853] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:42:01 192.168.122.209 [56272.267235] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:42:01 192.168.122.209 [56272.324925] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:42:01 192.168.122.209 [56272.326658] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:42:01 192.168.122.209 [56272.368849] [tempesta fw] Tempesta FW is ready Apr 26 07:42:02 192.168.122.209 [56273.062009] [tdb] Close table 'client0.tdb' Apr 26 07:42:02 192.168.122.209 [56273.246457] [tdb] Close table 'sessions0.tdb' Apr 26 07:42:05 192.168.122.209 [56276.479819] [tdb] Close table 'cache0.tdb' Apr 26 07:42:06 192.168.122.209 [56276.717879] [tdb] Close table 'filter0.tdb' Apr 26 07:42:06 192.168.122.209 [56276.718315] [tempesta fw] modules are stopped Apr 26 07:42:06 192.168.122.209 [56276.962686] [tempesta fw] exiting... Apr 26 07:42:06 192.168.122.209 [56277.071362] [tdb] Shutdown Tempesta DB Apr 26 07:42:06 192.168.122.209 [56277.299411] End test: cache.test_conditional.TestConditionalH2.test_none_match_HEAD Apr 26 07:42:06 192.168.122.209 [56277.310640] Start test: cache.test_conditional.TestConditionalH2.test_none_match_any Apr 26 07:42:07 192.168.122.209 [56278.376088] [tdb] Start Tempesta DB Apr 26 07:42:07 192.168.122.209 [56278.510142] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:42:09 192.168.122.209 [56279.898257] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56279.898257] Maybe that's fine, but it's worth checking the [56279.898257] config - if there is no relations between the [56279.898257] names, then host name confusion attack is possible. Apr 26 07:42:09 192.168.122.209 [56280.036991] [tempesta fw] Configuration processing is completed. Apr 26 07:42:09 192.168.122.209 [56280.091403] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:42:09 192.168.122.209 [56280.510065] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:42:10 192.168.122.209 [56280.537393] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:42:10 192.168.122.209 [56280.564864] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:42:10 192.168.122.209 [56280.613006] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:42:10 192.168.122.209 [56280.614421] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:42:10 192.168.122.209 [56280.668959] [tempesta fw] Tempesta FW is ready Apr 26 07:42:10 192.168.122.209 [56281.323438] [tdb] Close table 'client0.tdb' Apr 26 07:42:11 192.168.122.209 [56281.515386] [tdb] Close table 'sessions0.tdb' Apr 26 07:42:14 192.168.122.209 [56284.722003] [tdb] Close table 'cache0.tdb' Apr 26 07:42:14 192.168.122.209 [56284.990747] [tdb] Close table 'filter0.tdb' Apr 26 07:42:14 192.168.122.209 [56284.991184] [tempesta fw] modules are stopped Apr 26 07:42:14 192.168.122.209 [56285.169729] [tempesta fw] exiting... Apr 26 07:42:14 192.168.122.209 [56285.272747] [tdb] Shutdown Tempesta DB Apr 26 07:42:14 192.168.122.209 [56285.493720] End test: cache.test_conditional.TestConditionalH2.test_none_match_any Apr 26 07:42:14 192.168.122.209 [56285.508476] Start test: cache.test_conditional.TestConditionalH2.test_none_match_list Apr 26 07:42:16 192.168.122.209 [56286.585369] [tdb] Start Tempesta DB Apr 26 07:42:16 192.168.122.209 [56286.719369] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:42:17 192.168.122.209 [56288.174107] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56288.174107] Maybe that's fine, but it's worth checking the [56288.174107] config - if there is no relations between the [56288.174107] names, then host name confusion attack is possible. Apr 26 07:42:17 192.168.122.209 [56288.313145] [tempesta fw] Configuration processing is completed. Apr 26 07:42:17 192.168.122.209 [56288.376898] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:42:18 192.168.122.209 [56288.797163] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:42:18 192.168.122.209 [56288.824013] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:42:18 192.168.122.209 [56288.850252] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:42:18 192.168.122.209 [56288.897148] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:42:18 192.168.122.209 [56288.898924] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:42:18 192.168.122.209 [56288.957114] [tempesta fw] Tempesta FW is ready Apr 26 07:42:19 192.168.122.209 [56289.641610] [tdb] Close table 'client0.tdb' Apr 26 07:42:19 192.168.122.209 [56289.844398] [tdb] Close table 'sessions0.tdb' Apr 26 07:42:22 192.168.122.209 [56293.114444] [tdb] Close table 'cache0.tdb' Apr 26 07:42:22 192.168.122.209 [56293.339180] [tdb] Close table 'filter0.tdb' Apr 26 07:42:22 192.168.122.209 [56293.339617] [tempesta fw] modules are stopped Apr 26 07:42:23 192.168.122.209 [56293.542386] [tempesta fw] exiting... Apr 26 07:42:23 192.168.122.209 [56293.675707] [tdb] Shutdown Tempesta DB Apr 26 07:42:23 192.168.122.209 [56293.904213] End test: cache.test_conditional.TestConditionalH2.test_none_match_list Apr 26 07:42:23 192.168.122.209 [56293.934250] Start test: cache.test_conditional.TestConditionalH2.test_none_match_nc_GET Apr 26 07:42:24 192.168.122.209 [56294.998469] [tdb] Start Tempesta DB Apr 26 07:42:24 192.168.122.209 [56295.131345] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:42:26 192.168.122.209 [56296.562450] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56296.562450] Maybe that's fine, but it's worth checking the [56296.562450] config - if there is no relations between the [56296.562450] names, then host name confusion attack is possible. Apr 26 07:42:26 192.168.122.209 [56296.713276] [tempesta fw] Configuration processing is completed. Apr 26 07:42:26 192.168.122.209 [56296.765549] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:42:26 192.168.122.209 [56297.185060] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:42:26 192.168.122.209 [56297.212322] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:42:26 192.168.122.209 [56297.240622] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:42:26 192.168.122.209 [56297.293232] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:42:26 192.168.122.209 [56297.294992] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:42:26 192.168.122.209 [56297.333173] [tempesta fw] Tempesta FW is ready Apr 26 07:42:27 192.168.122.209 [56297.993457] [tdb] Close table 'client0.tdb' Apr 26 07:42:27 192.168.122.209 [56298.181594] [tdb] Close table 'sessions0.tdb' Apr 26 07:42:30 192.168.122.209 [56301.418699] [tdb] Close table 'cache0.tdb' Apr 26 07:42:31 192.168.122.209 [56301.639692] [tdb] Close table 'filter0.tdb' Apr 26 07:42:31 192.168.122.209 [56301.640132] [tempesta fw] modules are stopped Apr 26 07:42:31 192.168.122.209 [56301.856279] [tempesta fw] exiting... Apr 26 07:42:31 192.168.122.209 [56302.002144] [tdb] Shutdown Tempesta DB Apr 26 07:42:31 192.168.122.209 [56302.232697] End test: cache.test_conditional.TestConditionalH2.test_none_match_nc_GET Apr 26 07:42:31 192.168.122.209 [56302.251565] Start test: cache.test_conditional.TestConditionalH2.test_none_match_nc_HEAD Apr 26 07:42:32 192.168.122.209 [56303.246539] [tdb] Start Tempesta DB Apr 26 07:42:32 192.168.122.209 [56303.402815] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:42:35 192.168.122.209 [56305.994814] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56305.994814] Maybe that's fine, but it's worth checking the [56305.994814] config - if there is no relations between the [56305.994814] names, then host name confusion attack is possible. Apr 26 07:42:36 192.168.122.209 [56307.385400] [tempesta fw] Configuration processing is completed. Apr 26 07:42:37 192.168.122.209 [56307.536426] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:42:37 192.168.122.209 [56307.959495] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:42:37 192.168.122.209 [56307.987389] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:42:37 192.168.122.209 [56308.016797] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:42:37 192.168.122.209 [56308.509931] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:42:37 192.168.122.209 [56308.511644] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:42:38 192.168.122.209 [56308.796799] [tempesta fw] Tempesta FW is ready Apr 26 07:42:39 192.168.122.209 [56309.704851] [tdb] Close table 'client0.tdb' Apr 26 07:42:39 192.168.122.209 [56309.917976] [tdb] Close table 'sessions0.tdb' Apr 26 07:42:42 192.168.122.209 [56313.110912] [tdb] Close table 'cache0.tdb' Apr 26 07:42:42 192.168.122.209 [56313.359019] [tdb] Close table 'filter0.tdb' Apr 26 07:42:42 192.168.122.209 [56313.359461] [tempesta fw] modules are stopped Apr 26 07:42:43 192.168.122.209 [56313.582609] [tempesta fw] exiting... Apr 26 07:42:43 192.168.122.209 [56313.693827] [tdb] Shutdown Tempesta DB Apr 26 07:42:43 192.168.122.209 [56313.900559] End test: cache.test_conditional.TestConditionalH2.test_none_match_nc_HEAD Apr 26 07:42:43 192.168.122.209 [56313.921495] Start test: cache.test_conditional.TestConditionalH2.test_none_match_no_quotes_etag Apr 26 07:42:44 192.168.122.209 [56315.021674] [tdb] Start Tempesta DB Apr 26 07:42:44 192.168.122.209 [56315.150302] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:42:46 192.168.122.209 [56316.594746] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56316.594746] Maybe that's fine, but it's worth checking the [56316.594746] config - if there is no relations between the [56316.594746] names, then host name confusion attack is possible. Apr 26 07:42:46 192.168.122.209 [56316.725413] [tempesta fw] Configuration processing is completed. Apr 26 07:42:46 192.168.122.209 [56316.776378] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:42:46 192.168.122.209 [56317.207697] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:42:46 192.168.122.209 [56317.235016] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:42:46 192.168.122.209 [56317.261437] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:42:46 192.168.122.209 [56317.305490] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:42:46 192.168.122.209 [56317.307227] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:42:46 192.168.122.209 [56317.345422] [tempesta fw] Tempesta FW is ready Apr 26 07:42:47 192.168.122.209 [56318.042572] [tdb] Close table 'client0.tdb' Apr 26 07:42:47 192.168.122.209 [56318.219757] [tdb] Close table 'sessions0.tdb' Apr 26 07:42:50 192.168.122.209 [56321.471030] [tdb] Close table 'cache0.tdb' Apr 26 07:42:51 192.168.122.209 [56321.733608] [tdb] Close table 'filter0.tdb' Apr 26 07:42:51 192.168.122.209 [56321.734050] [tempesta fw] modules are stopped Apr 26 07:42:51 192.168.122.209 [56321.915302] [tempesta fw] exiting... Apr 26 07:42:51 192.168.122.209 [56322.009474] [tdb] Shutdown Tempesta DB Apr 26 07:42:51 192.168.122.209 [56322.256181] End test: cache.test_conditional.TestConditionalH2.test_none_match_no_quotes_etag Apr 26 07:42:51 192.168.122.209 [56322.272817] Start test: cache.test_conditional.TestConditionalH2.test_none_match_no_quotes_etag_with_extra_spaces Apr 26 07:42:52 192.168.122.209 [56323.331230] [tdb] Start Tempesta DB Apr 26 07:42:52 192.168.122.209 [56323.488842] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:42:54 192.168.122.209 [56324.914821] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56324.914821] Maybe that's fine, but it's worth checking the [56324.914821] config - if there is no relations between the [56324.914821] names, then host name confusion attack is possible. Apr 26 07:42:54 192.168.122.209 [56325.057600] [tempesta fw] Configuration processing is completed. Apr 26 07:42:54 192.168.122.209 [56325.120510] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:42:55 192.168.122.209 [56325.539459] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:42:55 192.168.122.209 [56325.566408] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:42:55 192.168.122.209 [56325.593945] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:42:55 192.168.122.209 [56325.665596] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:42:55 192.168.122.209 [56325.667321] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:42:55 192.168.122.209 [56325.705554] [tempesta fw] Tempesta FW is ready Apr 26 07:42:55 192.168.122.209 [56326.397635] [tdb] Close table 'client0.tdb' Apr 26 07:42:56 192.168.122.209 [56326.590338] [tdb] Close table 'sessions0.tdb' Apr 26 07:42:59 192.168.122.209 [56329.824949] [tdb] Close table 'cache0.tdb' Apr 26 07:42:59 192.168.122.209 [56330.061050] [tdb] Close table 'filter0.tdb' Apr 26 07:42:59 192.168.122.209 [56330.062228] [tempesta fw] modules are stopped Apr 26 07:42:59 192.168.122.209 [56330.289544] [tempesta fw] exiting... Apr 26 07:42:59 192.168.122.209 [56330.434197] [tdb] Shutdown Tempesta DB Apr 26 07:43:00 192.168.122.209 [56330.663770] End test: cache.test_conditional.TestConditionalH2.test_none_match_no_quotes_etag_with_extra_spaces Apr 26 07:43:00 192.168.122.209 [56330.682075] Start test: cache.test_conditional.TestConditionalH2.test_none_match_weak_all Apr 26 07:43:01 192.168.122.209 [56331.700642] [tdb] Start Tempesta DB Apr 26 07:43:01 192.168.122.209 [56331.838211] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:43:02 192.168.122.209 [56333.286900] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56333.286900] Maybe that's fine, but it's worth checking the [56333.286900] config - if there is no relations between the [56333.286900] names, then host name confusion attack is possible. Apr 26 07:43:02 192.168.122.209 [56333.421817] [tempesta fw] Configuration processing is completed. Apr 26 07:43:02 192.168.122.209 [56333.476340] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:43:03 192.168.122.209 [56333.902490] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:43:03 192.168.122.209 [56333.929166] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:43:03 192.168.122.209 [56333.955241] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:43:03 192.168.122.209 [56334.001591] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:43:03 192.168.122.209 [56334.002975] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:43:03 192.168.122.209 [56334.049670] [tempesta fw] Tempesta FW is ready Apr 26 07:43:04 192.168.122.209 [56334.705038] [tdb] Close table 'client0.tdb' Apr 26 07:43:04 192.168.122.209 [56334.893405] [tdb] Close table 'sessions0.tdb' Apr 26 07:43:07 192.168.122.209 [56338.049233] [tdb] Close table 'cache0.tdb' Apr 26 07:43:07 192.168.122.209 [56338.307118] [tdb] Close table 'filter0.tdb' Apr 26 07:43:07 192.168.122.209 [56338.307557] [tempesta fw] modules are stopped Apr 26 07:43:08 192.168.122.209 [56338.527180] [tempesta fw] exiting... Apr 26 07:43:08 192.168.122.209 [56338.647637] [tdb] Shutdown Tempesta DB Apr 26 07:43:08 192.168.122.209 [56338.873246] End test: cache.test_conditional.TestConditionalH2.test_none_match_weak_all Apr 26 07:43:08 192.168.122.209 [56338.889693] Start test: cache.test_conditional.TestConditionalH2.test_none_match_weak_clnt Apr 26 07:43:09 192.168.122.209 [56339.986044] [tdb] Start Tempesta DB Apr 26 07:43:09 192.168.122.209 [56340.128648] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:43:10 192.168.122.209 [56341.487199] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56341.487199] Maybe that's fine, but it's worth checking the [56341.487199] config - if there is no relations between the [56341.487199] names, then host name confusion attack is possible. Apr 26 07:43:11 192.168.122.209 [56341.629708] [tempesta fw] Configuration processing is completed. Apr 26 07:43:11 192.168.122.209 [56341.683626] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:43:11 192.168.122.209 [56342.106746] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:43:11 192.168.122.209 [56342.132769] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:43:11 192.168.122.209 [56342.159634] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:43:11 192.168.122.209 [56342.241798] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:43:11 192.168.122.209 [56342.243530] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:43:11 192.168.122.209 [56342.281750] [tempesta fw] Tempesta FW is ready Apr 26 07:43:12 192.168.122.209 [56342.960234] [tdb] Close table 'client0.tdb' Apr 26 07:43:12 192.168.122.209 [56343.132707] [tdb] Close table 'sessions0.tdb' Apr 26 07:43:15 192.168.122.209 [56346.321700] [tdb] Close table 'cache0.tdb' Apr 26 07:43:16 192.168.122.209 [56346.573821] [tdb] Close table 'filter0.tdb' Apr 26 07:43:16 192.168.122.209 [56346.574258] [tempesta fw] modules are stopped Apr 26 07:43:16 192.168.122.209 [56346.758675] [tempesta fw] exiting... Apr 26 07:43:16 192.168.122.209 [56346.877963] [tdb] Shutdown Tempesta DB Apr 26 07:43:16 192.168.122.209 [56347.090941] End test: cache.test_conditional.TestConditionalH2.test_none_match_weak_clnt Apr 26 07:43:16 192.168.122.209 [56347.111329] Start test: cache.test_conditional.TestConditionalH2.test_none_match_weak_srv Apr 26 07:43:17 192.168.122.209 [56348.194008] [tdb] Start Tempesta DB Apr 26 07:43:17 192.168.122.209 [56348.340991] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:43:19 192.168.122.209 [56349.896003] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56349.896003] Maybe that's fine, but it's worth checking the [56349.896003] config - if there is no relations between the [56349.896003] names, then host name confusion attack is possible. Apr 26 07:43:19 192.168.122.209 [56350.029884] [tempesta fw] Configuration processing is completed. Apr 26 07:43:19 192.168.122.209 [56350.083855] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:43:19 192.168.122.209 [56350.508772] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:43:20 192.168.122.209 [56350.535239] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:43:20 192.168.122.209 [56350.561457] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:43:20 192.168.122.209 [56350.605855] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:43:20 192.168.122.209 [56350.607128] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:43:20 192.168.122.209 [56350.653831] [tempesta fw] Tempesta FW is ready Apr 26 07:43:20 192.168.122.209 [56351.385108] [tdb] Close table 'client0.tdb' Apr 26 07:43:21 192.168.122.209 [56351.570765] [tdb] Close table 'sessions0.tdb' Apr 26 07:43:24 192.168.122.209 [56354.780378] [tdb] Close table 'cache0.tdb' Apr 26 07:43:24 192.168.122.209 [56355.017597] [tdb] Close table 'filter0.tdb' Apr 26 07:43:24 192.168.122.209 [56355.018403] [tempesta fw] modules are stopped Apr 26 07:43:24 192.168.122.209 [56355.205086] [tempesta fw] exiting... Apr 26 07:43:24 192.168.122.209 [56355.323764] [tdb] Shutdown Tempesta DB Apr 26 07:43:25 192.168.122.209 [56355.534323] End test: cache.test_conditional.TestConditionalH2.test_none_match_weak_srv Apr 26 07:43:25 192.168.122.209 [56355.549910] Start test: cache.test_conditional.TestConditionalH2.test_response_without_last_modified Apr 26 07:43:26 192.168.122.209 [56356.558183] [tdb] Start Tempesta DB Apr 26 07:43:26 192.168.122.209 [56356.714409] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:43:27 192.168.122.209 [56358.131239] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56358.131239] Maybe that's fine, but it's worth checking the [56358.131239] config - if there is no relations between the [56358.131239] names, then host name confusion attack is possible. Apr 26 07:43:27 192.168.122.209 [56358.269934] [tempesta fw] Configuration processing is completed. Apr 26 07:43:27 192.168.122.209 [56358.321408] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:43:28 192.168.122.209 [56358.736874] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:43:28 192.168.122.209 [56358.763775] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:43:28 192.168.122.209 [56358.789637] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:43:28 192.168.122.209 [56358.829954] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:43:28 192.168.122.209 [56358.831350] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:43:28 192.168.122.209 [56358.869928] [tempesta fw] Tempesta FW is ready Apr 26 07:43:29 192.168.122.209 [56359.557284] [tdb] Close table 'client0.tdb' Apr 26 07:43:29 192.168.122.209 [56359.754983] [tdb] Close table 'sessions0.tdb' Apr 26 07:43:32 192.168.122.209 [56362.974359] [tdb] Close table 'cache0.tdb' Apr 26 07:43:32 192.168.122.209 [56363.203050] [tdb] Close table 'filter0.tdb' Apr 26 07:43:32 192.168.122.209 [56363.203465] [tempesta fw] modules are stopped Apr 26 07:43:32 192.168.122.209 [56363.381950] [tempesta fw] exiting... Apr 26 07:43:32 192.168.122.209 [56363.490712] [tdb] Shutdown Tempesta DB Apr 26 07:43:33 192.168.122.209 [56363.703898] End test: cache.test_conditional.TestConditionalH2.test_response_without_last_modified Apr 26 07:43:33 192.168.122.209 [56363.729196] Start test: cache.test_conditional.TestConditionalH2.test_response_without_last_modified_and_date Apr 26 07:43:34 192.168.122.209 [56364.846133] [tdb] Start Tempesta DB Apr 26 07:43:34 192.168.122.209 [56364.987462] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:43:35 192.168.122.209 [56366.463310] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56366.463310] Maybe that's fine, but it's worth checking the [56366.463310] config - if there is no relations between the [56366.463310] names, then host name confusion attack is possible. Apr 26 07:43:36 192.168.122.209 [56366.598082] [tempesta fw] Configuration processing is completed. Apr 26 07:43:36 192.168.122.209 [56366.648733] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:43:36 192.168.122.209 [56367.064674] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:43:36 192.168.122.209 [56367.091225] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:43:36 192.168.122.209 [56367.118213] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:43:36 192.168.122.209 [56367.159407] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:43:36 192.168.122.209 [56367.161132] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:43:36 192.168.122.209 [56367.198033] [tempesta fw] Tempesta FW is ready Apr 26 07:43:37 192.168.122.209 [56367.832736] [tdb] Close table 'client0.tdb' Apr 26 07:43:37 192.168.122.209 [56368.049765] [tdb] Close table 'sessions0.tdb' Apr 26 07:43:40 192.168.122.209 [56371.280597] [tdb] Close table 'cache0.tdb' Apr 26 07:43:41 192.168.122.209 [56371.515837] [tdb] Close table 'filter0.tdb' Apr 26 07:43:41 192.168.122.209 [56371.516277] [tempesta fw] modules are stopped Apr 26 07:43:41 192.168.122.209 [56371.686088] [tempesta fw] exiting... Apr 26 07:43:41 192.168.122.209 [56371.800793] [tdb] Shutdown Tempesta DB Apr 26 07:43:41 192.168.122.209 [56372.030631] End test: cache.test_conditional.TestConditionalH2.test_response_without_last_modified_and_date Apr 26 07:43:41 192.168.122.209 [56372.044727] Start test: cache.test_conditional.TestConditionalH2.test_response_without_last_modified_and_date_nc Apr 26 07:43:42 192.168.122.209 [56373.104201] [tdb] Start Tempesta DB Apr 26 07:43:42 192.168.122.209 [56373.247520] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:43:44 192.168.122.209 [56374.667229] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56374.667229] Maybe that's fine, but it's worth checking the [56374.667229] config - if there is no relations between the [56374.667229] names, then host name confusion attack is possible. Apr 26 07:43:44 192.168.122.209 [56374.806303] [tempesta fw] Configuration processing is completed. Apr 26 07:43:44 192.168.122.209 [56374.856761] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:43:44 192.168.122.209 [56375.278427] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:43:44 192.168.122.209 [56375.304722] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:43:44 192.168.122.209 [56375.330781] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:43:44 192.168.122.209 [56375.374165] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:43:44 192.168.122.209 [56375.375548] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:43:44 192.168.122.209 [56375.418138] [tempesta fw] Tempesta FW is ready Apr 26 07:43:45 192.168.122.209 [56376.064341] [tdb] Close table 'client0.tdb' Apr 26 07:43:45 192.168.122.209 [56376.261080] [tdb] Close table 'sessions0.tdb' Apr 26 07:43:48 192.168.122.209 [56379.488622] [tdb] Close table 'cache0.tdb' Apr 26 07:43:49 192.168.122.209 [56379.723380] [tdb] Close table 'filter0.tdb' Apr 26 07:43:49 192.168.122.209 [56379.723813] [tempesta fw] modules are stopped Apr 26 07:43:49 192.168.122.209 [56380.022055] [tempesta fw] exiting... Apr 26 07:43:49 192.168.122.209 [56380.139716] [tdb] Shutdown Tempesta DB Apr 26 07:43:49 192.168.122.209 [56380.345511] End test: cache.test_conditional.TestConditionalH2.test_response_without_last_modified_and_date_nc Apr 26 07:43:49 192.168.122.209 [56380.361875] Start test: cache.test_conditional.TestConditionalH2.test_response_without_last_modified_nc Apr 26 07:43:50 192.168.122.209 [56381.470687] [tdb] Start Tempesta DB Apr 26 07:43:51 192.168.122.209 [56381.621978] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:43:52 192.168.122.209 [56383.067500] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56383.067500] Maybe that's fine, but it's worth checking the [56383.067500] config - if there is no relations between the [56383.067500] names, then host name confusion attack is possible. Apr 26 07:43:52 192.168.122.209 [56383.198250] [tempesta fw] Configuration processing is completed. Apr 26 07:43:52 192.168.122.209 [56383.251336] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:43:53 192.168.122.209 [56383.668426] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:43:53 192.168.122.209 [56383.695555] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:43:53 192.168.122.209 [56383.721893] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:43:53 192.168.122.209 [56383.778291] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:43:53 192.168.122.209 [56383.780039] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:43:53 192.168.122.209 [56383.818273] [tempesta fw] Tempesta FW is ready Apr 26 07:43:53 192.168.122.209 [56384.454066] [tdb] Close table 'client0.tdb' Apr 26 07:43:54 192.168.122.209 [56384.649972] [tdb] Close table 'sessions0.tdb' Apr 26 07:43:57 192.168.122.209 [56387.831461] [tdb] Close table 'cache0.tdb' Apr 26 07:43:57 192.168.122.209 [56388.073918] [tdb] Close table 'filter0.tdb' Apr 26 07:43:57 192.168.122.209 [56388.074366] [tempesta fw] modules are stopped Apr 26 07:43:57 192.168.122.209 [56388.266441] [tempesta fw] exiting... Apr 26 07:43:57 192.168.122.209 [56388.375471] [tdb] Shutdown Tempesta DB Apr 26 07:43:58 192.168.122.209 [56388.613412] End test: cache.test_conditional.TestConditionalH2.test_response_without_last_modified_nc Apr 26 07:43:58 192.168.122.209 [56388.631740] Start test: cache.test_conditional.TestConditionalHttp.test_correct_none_match_and_modified_since Apr 26 07:43:59 192.168.122.209 [56389.678230] [tdb] Start Tempesta DB Apr 26 07:43:59 192.168.122.209 [56389.816040] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:44:00 192.168.122.209 [56391.223725] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56391.223725] Maybe that's fine, but it's worth checking the [56391.223725] config - if there is no relations between the [56391.223725] names, then host name confusion attack is possible. Apr 26 07:44:00 192.168.122.209 [56391.370416] [tempesta fw] Configuration processing is completed. Apr 26 07:44:00 192.168.122.209 [56391.421930] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:44:01 192.168.122.209 [56391.853023] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:44:01 192.168.122.209 [56391.880332] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:44:01 192.168.122.209 [56391.906515] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:44:01 192.168.122.209 [56391.954380] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:44:01 192.168.122.209 [56391.955776] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:44:01 192.168.122.209 [56392.010384] [tempesta fw] Tempesta FW is ready Apr 26 07:44:02 192.168.122.209 [56392.648147] [tdb] Close table 'client0.tdb' Apr 26 07:44:02 192.168.122.209 [56392.820610] [tdb] Close table 'sessions0.tdb' Apr 26 07:44:05 192.168.122.209 [56396.089488] [tdb] Close table 'cache0.tdb' Apr 26 07:44:05 192.168.122.209 [56396.314467] [tdb] Close table 'filter0.tdb' Apr 26 07:44:05 192.168.122.209 [56396.314913] [tempesta fw] modules are stopped Apr 26 07:44:06 192.168.122.209 [56396.531659] [tempesta fw] exiting... Apr 26 07:44:06 192.168.122.209 [56396.641893] [tdb] Shutdown Tempesta DB Apr 26 07:44:06 192.168.122.209 [56396.858548] End test: cache.test_conditional.TestConditionalHttp.test_correct_none_match_and_modified_since Apr 26 07:44:06 192.168.122.209 [56396.875997] Start test: cache.test_conditional.TestConditionalHttp.test_incorrect_none_match_and_correct_modified_since Apr 26 07:44:07 192.168.122.209 [56397.940758] [tdb] Start Tempesta DB Apr 26 07:44:07 192.168.122.209 [56398.087946] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:44:09 192.168.122.209 [56399.527359] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56399.527359] Maybe that's fine, but it's worth checking the [56399.527359] config - if there is no relations between the [56399.527359] names, then host name confusion attack is possible. Apr 26 07:44:09 192.168.122.209 [56399.670526] [tempesta fw] Configuration processing is completed. Apr 26 07:44:09 192.168.122.209 [56399.722733] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:44:09 192.168.122.209 [56400.169550] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:44:09 192.168.122.209 [56400.198790] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:44:09 192.168.122.209 [56400.228333] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:44:09 192.168.122.209 [56400.274478] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:44:09 192.168.122.209 [56400.275872] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:44:09 192.168.122.209 [56400.330406] [tempesta fw] Tempesta FW is ready Apr 26 07:44:10 192.168.122.209 [56400.951227] [tdb] Close table 'client0.tdb' Apr 26 07:44:10 192.168.122.209 [56401.140639] [tdb] Close table 'sessions0.tdb' Apr 26 07:44:13 192.168.122.209 [56404.443182] [tdb] Close table 'cache0.tdb' Apr 26 07:44:14 192.168.122.209 [56404.695878] [tdb] Close table 'filter0.tdb' Apr 26 07:44:14 192.168.122.209 [56404.696331] [tempesta fw] modules are stopped Apr 26 07:44:14 192.168.122.209 [56404.877687] [tempesta fw] exiting... Apr 26 07:44:14 192.168.122.209 [56404.988288] [tdb] Shutdown Tempesta DB Apr 26 07:44:14 192.168.122.209 [56405.201970] End test: cache.test_conditional.TestConditionalHttp.test_incorrect_none_match_and_correct_modified_since Apr 26 07:44:14 192.168.122.209 [56405.224203] Start test: cache.test_conditional.TestConditionalHttp.test_mod_since Apr 26 07:44:15 192.168.122.209 [56406.179530] [tdb] Start Tempesta DB Apr 26 07:44:15 192.168.122.209 [56406.345456] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:44:17 192.168.122.209 [56407.859906] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56407.859906] Maybe that's fine, but it's worth checking the [56407.859906] config - if there is no relations between the [56407.859906] names, then host name confusion attack is possible. Apr 26 07:44:17 192.168.122.209 [56407.990621] [tempesta fw] Configuration processing is completed. Apr 26 07:44:17 192.168.122.209 [56408.044721] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:44:18 192.168.122.209 [56408.528158] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:44:18 192.168.122.209 [56408.560454] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:44:18 192.168.122.209 [56408.593087] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:44:18 192.168.122.209 [56408.682612] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:44:18 192.168.122.209 [56408.684377] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:44:18 192.168.122.209 [56408.722568] [tempesta fw] Tempesta FW is ready Apr 26 07:44:18 192.168.122.209 [56409.333532] [tdb] Close table 'client0.tdb' Apr 26 07:44:19 192.168.122.209 [56409.526198] [tdb] Close table 'sessions0.tdb' Apr 26 07:44:22 192.168.122.209 [56412.789838] [tdb] Close table 'cache0.tdb' Apr 26 07:44:22 192.168.122.209 [56413.033327] [tdb] Close table 'filter0.tdb' Apr 26 07:44:22 192.168.122.209 [56413.033777] [tempesta fw] modules are stopped Apr 26 07:44:22 192.168.122.209 [56413.219151] [tempesta fw] exiting... Apr 26 07:44:22 192.168.122.209 [56413.342755] [tdb] Shutdown Tempesta DB Apr 26 07:44:23 192.168.122.209 [56413.590940] End test: cache.test_conditional.TestConditionalHttp.test_mod_since Apr 26 07:44:23 192.168.122.209 [56413.604375] Start test: cache.test_conditional.TestConditionalHttp.test_mod_since_nc Apr 26 07:44:24 192.168.122.209 [56414.706078] [tdb] Start Tempesta DB Apr 26 07:44:24 192.168.122.209 [56414.856359] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:44:25 192.168.122.209 [56416.292029] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56416.292029] Maybe that's fine, but it's worth checking the [56416.292029] config - if there is no relations between the [56416.292029] names, then host name confusion attack is possible. Apr 26 07:44:25 192.168.122.209 [56416.422719] [tempesta fw] Configuration processing is completed. Apr 26 07:44:25 192.168.122.209 [56416.480858] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:44:26 192.168.122.209 [56416.921856] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:44:26 192.168.122.209 [56416.951479] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:44:26 192.168.122.209 [56416.981868] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:44:26 192.168.122.209 [56417.038730] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:44:26 192.168.122.209 [56417.040803] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:44:26 192.168.122.209 [56417.086663] [tempesta fw] Tempesta FW is ready Apr 26 07:44:27 192.168.122.209 [56417.735688] [tdb] Close table 'client0.tdb' Apr 26 07:44:27 192.168.122.209 [56417.929424] [tdb] Close table 'sessions0.tdb' Apr 26 07:44:30 192.168.122.209 [56421.182504] [tdb] Close table 'cache0.tdb' Apr 26 07:44:30 192.168.122.209 [56421.445235] [tdb] Close table 'filter0.tdb' Apr 26 07:44:30 192.168.122.209 [56421.445664] [tempesta fw] modules are stopped Apr 26 07:44:31 192.168.122.209 [56421.654228] [tempesta fw] exiting... Apr 26 07:44:31 192.168.122.209 [56421.790097] [tdb] Shutdown Tempesta DB Apr 26 07:44:31 192.168.122.209 [56422.013984] End test: cache.test_conditional.TestConditionalHttp.test_mod_since_nc Apr 26 07:44:31 192.168.122.209 [56422.038175] Start test: cache.test_conditional.TestConditionalHttp.test_mod_since_nc_with_invalid_date Apr 26 07:44:32 192.168.122.209 [56423.115047] [tdb] Start Tempesta DB Apr 26 07:44:32 192.168.122.209 [56423.263074] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:44:34 192.168.122.209 [56424.640062] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56424.640062] Maybe that's fine, but it's worth checking the [56424.640062] config - if there is no relations between the [56424.640062] names, then host name confusion attack is possible. Apr 26 07:44:34 192.168.122.209 [56424.770835] [tempesta fw] Configuration processing is completed. Apr 26 07:44:34 192.168.122.209 [56424.822313] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:44:34 192.168.122.209 [56425.241068] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:44:34 192.168.122.209 [56425.267901] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:44:34 192.168.122.209 [56425.293974] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:44:34 192.168.122.209 [56425.342776] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:44:34 192.168.122.209 [56425.344500] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:44:34 192.168.122.209 [56425.398775] [tempesta fw] Tempesta FW is ready Apr 26 07:44:35 192.168.122.209 [56426.047509] [tdb] Close table 'client0.tdb' Apr 26 07:44:35 192.168.122.209 [56426.252677] [tdb] Close table 'sessions0.tdb' Apr 26 07:44:39 192.168.122.209 [56429.611641] [tdb] Close table 'cache0.tdb' Apr 26 07:44:39 192.168.122.209 [56429.895785] [tdb] Close table 'filter0.tdb' Apr 26 07:44:39 192.168.122.209 [56429.896229] [tempesta fw] modules are stopped Apr 26 07:44:39 192.168.122.209 [56430.139663] [tempesta fw] exiting... Apr 26 07:44:39 192.168.122.209 [56430.264496] [tdb] Shutdown Tempesta DB Apr 26 07:44:39 192.168.122.209 [56430.494092] End test: cache.test_conditional.TestConditionalHttp.test_mod_since_nc_with_invalid_date Apr 26 07:44:39 192.168.122.209 [56430.513794] Start test: cache.test_conditional.TestConditionalHttp.test_none_match Apr 26 07:44:41 192.168.122.209 [56431.611487] [tdb] Start Tempesta DB Apr 26 07:44:41 192.168.122.209 [56431.733838] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:44:42 192.168.122.209 [56433.131797] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56433.131797] Maybe that's fine, but it's worth checking the [56433.131797] config - if there is no relations between the [56433.131797] names, then host name confusion attack is possible. Apr 26 07:44:42 192.168.122.209 [56433.274867] [tempesta fw] Configuration processing is completed. Apr 26 07:44:42 192.168.122.209 [56433.331565] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:44:43 192.168.122.209 [56433.766580] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:44:43 192.168.122.209 [56433.793929] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:44:43 192.168.122.209 [56433.821976] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:44:43 192.168.122.209 [56433.874907] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:44:43 192.168.122.209 [56433.876283] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:44:43 192.168.122.209 [56433.914875] [tempesta fw] Tempesta FW is ready Apr 26 07:44:44 192.168.122.209 [56434.540384] [tdb] Close table 'client0.tdb' Apr 26 07:44:44 192.168.122.209 [56434.754608] [tdb] Close table 'sessions0.tdb' Apr 26 07:44:47 192.168.122.209 [56438.019228] [tdb] Close table 'cache0.tdb' Apr 26 07:44:47 192.168.122.209 [56438.304788] [tdb] Close table 'filter0.tdb' Apr 26 07:44:47 192.168.122.209 [56438.305226] [tempesta fw] modules are stopped Apr 26 07:44:48 192.168.122.209 [56438.521508] [tempesta fw] exiting... Apr 26 07:44:48 192.168.122.209 [56438.643822] [tdb] Shutdown Tempesta DB Apr 26 07:44:48 192.168.122.209 [56438.872708] End test: cache.test_conditional.TestConditionalHttp.test_none_match Apr 26 07:44:48 192.168.122.209 [56438.900861] Start test: cache.test_conditional.TestConditionalHttp.test_none_match_HEAD Apr 26 07:44:49 192.168.122.209 [56439.995382] [tdb] Start Tempesta DB Apr 26 07:44:49 192.168.122.209 [56440.147448] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:44:51 192.168.122.209 [56441.616413] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56441.616413] Maybe that's fine, but it's worth checking the [56441.616413] config - if there is no relations between the [56441.616413] names, then host name confusion attack is possible. Apr 26 07:44:51 192.168.122.209 [56441.747278] [tempesta fw] Configuration processing is completed. Apr 26 07:44:51 192.168.122.209 [56441.806165] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:44:51 192.168.122.209 [56442.239255] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:44:51 192.168.122.209 [56442.266641] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:44:51 192.168.122.209 [56442.293499] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:44:51 192.168.122.209 [56442.343029] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:44:51 192.168.122.209 [56442.344810] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:44:51 192.168.122.209 [56442.382988] [tempesta fw] Tempesta FW is ready Apr 26 07:44:52 192.168.122.209 [56443.016215] [tdb] Close table 'client0.tdb' Apr 26 07:44:52 192.168.122.209 [56443.210574] [tdb] Close table 'sessions0.tdb' Apr 26 07:44:55 192.168.122.209 [56446.400441] [tdb] Close table 'cache0.tdb' Apr 26 07:44:56 192.168.122.209 [56446.639252] [tdb] Close table 'filter0.tdb' Apr 26 07:44:56 192.168.122.209 [56446.639688] [tempesta fw] modules are stopped Apr 26 07:44:56 192.168.122.209 [56446.911017] [tempesta fw] exiting... Apr 26 07:44:56 192.168.122.209 [56447.011989] [tdb] Shutdown Tempesta DB Apr 26 07:44:56 192.168.122.209 [56447.262134] End test: cache.test_conditional.TestConditionalHttp.test_none_match_HEAD Apr 26 07:44:56 192.168.122.209 [56447.275745] Start test: cache.test_conditional.TestConditionalHttp.test_none_match_any Apr 26 07:44:57 192.168.122.209 [56448.318995] [tdb] Start Tempesta DB Apr 26 07:44:57 192.168.122.209 [56448.460164] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:44:59 192.168.122.209 [56449.955931] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56449.955931] Maybe that's fine, but it's worth checking the [56449.955931] config - if there is no relations between the [56449.955931] names, then host name confusion attack is possible. Apr 26 07:44:59 192.168.122.209 [56450.087198] [tempesta fw] Configuration processing is completed. Apr 26 07:44:59 192.168.122.209 [56450.158963] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:45:00 192.168.122.209 [56450.574966] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:45:00 192.168.122.209 [56450.602240] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:45:00 192.168.122.209 [56450.628797] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:45:00 192.168.122.209 [56450.679110] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:45:00 192.168.122.209 [56450.680525] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:45:00 192.168.122.209 [56450.723075] [tempesta fw] Tempesta FW is ready Apr 26 07:45:00 192.168.122.209 [56451.356765] [tdb] Close table 'client0.tdb' Apr 26 07:45:01 192.168.122.209 [56451.550086] [tdb] Close table 'sessions0.tdb' Apr 26 07:45:04 192.168.122.209 [56454.786748] [tdb] Close table 'cache0.tdb' Apr 26 07:45:04 192.168.122.209 [56455.045165] [tdb] Close table 'filter0.tdb' Apr 26 07:45:04 192.168.122.209 [56455.045595] [tempesta fw] modules are stopped Apr 26 07:45:04 192.168.122.209 [56455.297989] [tempesta fw] exiting... Apr 26 07:45:04 192.168.122.209 [56455.410374] [tdb] Shutdown Tempesta DB Apr 26 07:45:05 192.168.122.209 [56455.622717] End test: cache.test_conditional.TestConditionalHttp.test_none_match_any Apr 26 07:45:05 192.168.122.209 [56455.638214] Start test: cache.test_conditional.TestConditionalHttp.test_none_match_empty_etag Apr 26 07:45:06 192.168.122.209 [56456.759405] [tdb] Start Tempesta DB Apr 26 07:45:06 192.168.122.209 [56456.891564] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:45:07 192.168.122.209 [56458.336485] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56458.336485] Maybe that's fine, but it's worth checking the [56458.336485] config - if there is no relations between the [56458.336485] names, then host name confusion attack is possible. Apr 26 07:45:07 192.168.122.209 [56458.463236] [tempesta fw] Configuration processing is completed. Apr 26 07:45:07 192.168.122.209 [56458.514693] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:45:08 192.168.122.209 [56458.936411] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:45:08 192.168.122.209 [56458.963698] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:45:08 192.168.122.209 [56458.991046] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:45:08 192.168.122.209 [56459.031177] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:45:08 192.168.122.209 [56459.032217] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:45:08 192.168.122.209 [56459.079185] [tempesta fw] Tempesta FW is ready Apr 26 07:45:09 192.168.122.209 [56459.641863] [tdb] Close table 'client0.tdb' Apr 26 07:45:09 192.168.122.209 [56459.842271] [tdb] Close table 'sessions0.tdb' Apr 26 07:45:12 192.168.122.209 [56463.028288] [tdb] Close table 'cache0.tdb' Apr 26 07:45:12 192.168.122.209 [56463.280051] [tdb] Close table 'filter0.tdb' Apr 26 07:45:12 192.168.122.209 [56463.280492] [tempesta fw] modules are stopped Apr 26 07:45:12 192.168.122.209 [56463.458112] [tempesta fw] exiting... Apr 26 07:45:13 192.168.122.209 [56463.567164] [tdb] Shutdown Tempesta DB Apr 26 07:45:13 192.168.122.209 [56463.783251] End test: cache.test_conditional.TestConditionalHttp.test_none_match_empty_etag Apr 26 07:45:13 192.168.122.209 [56463.803365] Start test: cache.test_conditional.TestConditionalHttp.test_none_match_list Apr 26 07:45:14 192.168.122.209 [56464.897650] [tdb] Start Tempesta DB Apr 26 07:45:14 192.168.122.209 [56465.022909] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:45:15 192.168.122.209 [56466.481013] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56466.481013] Maybe that's fine, but it's worth checking the [56466.481013] config - if there is no relations between the [56466.481013] names, then host name confusion attack is possible. Apr 26 07:45:16 192.168.122.209 [56466.619337] [tempesta fw] Configuration processing is completed. Apr 26 07:45:16 192.168.122.209 [56466.669613] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:45:16 192.168.122.209 [56467.091125] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:45:16 192.168.122.209 [56467.117809] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:45:16 192.168.122.209 [56467.143634] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:45:16 192.168.122.209 [56467.187310] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:45:16 192.168.122.209 [56467.188708] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:45:16 192.168.122.209 [56467.235316] [tempesta fw] Tempesta FW is ready Apr 26 07:45:17 192.168.122.209 [56467.875662] [tdb] Close table 'client0.tdb' Apr 26 07:45:17 192.168.122.209 [56468.057201] [tdb] Close table 'sessions0.tdb' Apr 26 07:45:20 192.168.122.209 [56471.240953] [tdb] Close table 'cache0.tdb' Apr 26 07:45:20 192.168.122.209 [56471.493874] [tdb] Close table 'filter0.tdb' Apr 26 07:45:20 192.168.122.209 [56471.494306] [tempesta fw] modules are stopped Apr 26 07:45:21 192.168.122.209 [56471.703053] [tempesta fw] exiting... Apr 26 07:45:21 192.168.122.209 [56471.847232] [tdb] Shutdown Tempesta DB Apr 26 07:45:21 192.168.122.209 [56472.082964] End test: cache.test_conditional.TestConditionalHttp.test_none_match_list Apr 26 07:45:21 192.168.122.209 [56472.096393] Start test: cache.test_conditional.TestConditionalHttp.test_none_match_nc_GET Apr 26 07:45:22 192.168.122.209 [56473.125967] [tdb] Start Tempesta DB Apr 26 07:45:22 192.168.122.209 [56473.277688] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:45:24 192.168.122.209 [56474.712703] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56474.712703] Maybe that's fine, but it's worth checking the [56474.712703] config - if there is no relations between the [56474.712703] names, then host name confusion attack is possible. Apr 26 07:45:24 192.168.122.209 [56474.863446] [tempesta fw] Configuration processing is completed. Apr 26 07:45:24 192.168.122.209 [56474.913676] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:45:24 192.168.122.209 [56475.330752] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:45:24 192.168.122.209 [56475.360740] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:45:24 192.168.122.209 [56475.386741] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:45:24 192.168.122.209 [56475.427384] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:45:24 192.168.122.209 [56475.428544] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:45:24 192.168.122.209 [56475.471386] [tempesta fw] Tempesta FW is ready Apr 26 07:45:25 192.168.122.209 [56476.102156] [tdb] Close table 'client0.tdb' Apr 26 07:45:25 192.168.122.209 [56476.290461] [tdb] Close table 'sessions0.tdb' Apr 26 07:45:28 192.168.122.209 [56479.462030] [tdb] Close table 'cache0.tdb' Apr 26 07:45:29 192.168.122.209 [56479.696548] [tdb] Close table 'filter0.tdb' Apr 26 07:45:29 192.168.122.209 [56479.696983] [tempesta fw] modules are stopped Apr 26 07:45:29 192.168.122.209 [56479.923557] [tempesta fw] exiting... Apr 26 07:45:29 192.168.122.209 [56480.053747] [tdb] Shutdown Tempesta DB Apr 26 07:45:29 192.168.122.209 [56480.250019] End test: cache.test_conditional.TestConditionalHttp.test_none_match_nc_GET Apr 26 07:45:29 192.168.122.209 [56480.278754] Start test: cache.test_conditional.TestConditionalHttp.test_none_match_nc_HEAD Apr 26 07:45:30 192.168.122.209 [56481.318976] [tdb] Start Tempesta DB Apr 26 07:45:30 192.168.122.209 [56481.469876] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:45:32 192.168.122.209 [56482.840812] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56482.840812] Maybe that's fine, but it's worth checking the [56482.840812] config - if there is no relations between the [56482.840812] names, then host name confusion attack is possible. Apr 26 07:45:32 192.168.122.209 [56482.983522] [tempesta fw] Configuration processing is completed. Apr 26 07:45:32 192.168.122.209 [56483.034910] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:45:32 192.168.122.209 [56483.449984] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:45:32 192.168.122.209 [56483.476231] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:45:32 192.168.122.209 [56483.502214] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:45:33 192.168.122.209 [56483.547496] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:45:33 192.168.122.209 [56483.548647] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:45:33 192.168.122.209 [56483.591437] [tempesta fw] Tempesta FW is ready Apr 26 07:45:33 192.168.122.209 [56484.252089] [tdb] Close table 'client0.tdb' Apr 26 07:45:33 192.168.122.209 [56484.452258] [tdb] Close table 'sessions0.tdb' Apr 26 07:45:37 192.168.122.209 [56487.608502] [tdb] Close table 'cache0.tdb' Apr 26 07:45:37 192.168.122.209 [56487.849104] [tdb] Close table 'filter0.tdb' Apr 26 07:45:37 192.168.122.209 [56487.849542] [tempesta fw] modules are stopped Apr 26 07:45:37 192.168.122.209 [56488.032148] [tempesta fw] exiting... Apr 26 07:45:37 192.168.122.209 [56488.142468] [tdb] Shutdown Tempesta DB Apr 26 07:45:37 192.168.122.209 [56488.358911] End test: cache.test_conditional.TestConditionalHttp.test_none_match_nc_HEAD Apr 26 07:45:37 192.168.122.209 [56488.378885] Start test: cache.test_conditional.TestConditionalHttp.test_none_match_no_quotes_empty_etag Apr 26 07:45:38 192.168.122.209 [56489.433786] [tdb] Start Tempesta DB Apr 26 07:45:39 192.168.122.209 [56489.562416] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:45:40 192.168.122.209 [56490.952888] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56490.952888] Maybe that's fine, but it's worth checking the [56490.952888] config - if there is no relations between the [56490.952888] names, then host name confusion attack is possible. Apr 26 07:45:40 192.168.122.209 [56491.091657] [tempesta fw] Configuration processing is completed. Apr 26 07:45:40 192.168.122.209 [56491.146485] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:45:41 192.168.122.209 [56491.571938] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:45:41 192.168.122.209 [56491.598796] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:45:41 192.168.122.209 [56491.625012] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:45:41 192.168.122.209 [56491.707645] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:45:41 192.168.122.209 [56491.709413] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:45:41 192.168.122.209 [56491.755605] [tempesta fw] Tempesta FW is ready Apr 26 07:45:41 192.168.122.209 [56492.362818] [tdb] Close table 'client0.tdb' Apr 26 07:45:42 192.168.122.209 [56492.542564] [tdb] Close table 'sessions0.tdb' Apr 26 07:45:45 192.168.122.209 [56495.733995] [tdb] Close table 'cache0.tdb' Apr 26 07:45:45 192.168.122.209 [56495.982224] [tdb] Close table 'filter0.tdb' Apr 26 07:45:45 192.168.122.209 [56495.982646] [tempesta fw] modules are stopped Apr 26 07:45:45 192.168.122.209 [56496.158451] [tempesta fw] exiting... Apr 26 07:45:45 192.168.122.209 [56496.275750] [tdb] Shutdown Tempesta DB Apr 26 07:45:45 192.168.122.209 [56496.504397] End test: cache.test_conditional.TestConditionalHttp.test_none_match_no_quotes_empty_etag Apr 26 07:45:45 192.168.122.209 [56496.515450] Start test: cache.test_conditional.TestConditionalHttp.test_none_match_no_quotes_empty_etag_with_extra_spaces Apr 26 07:45:47 192.168.122.209 [56497.573640] [tdb] Start Tempesta DB Apr 26 07:45:47 192.168.122.209 [56497.717040] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:45:48 192.168.122.209 [56499.177049] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56499.177049] Maybe that's fine, but it's worth checking the [56499.177049] config - if there is no relations between the [56499.177049] names, then host name confusion attack is possible. Apr 26 07:45:48 192.168.122.209 [56499.307746] [tempesta fw] Configuration processing is completed. Apr 26 07:45:48 192.168.122.209 [56499.366828] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:45:49 192.168.122.209 [56499.780330] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:45:49 192.168.122.209 [56499.813875] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:45:49 192.168.122.209 [56499.840173] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:45:49 192.168.122.209 [56499.899708] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:45:49 192.168.122.209 [56499.901452] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:45:49 192.168.122.209 [56499.935692] [tempesta fw] Tempesta FW is ready Apr 26 07:45:50 192.168.122.209 [56500.544098] [tdb] Close table 'client0.tdb' Apr 26 07:45:50 192.168.122.209 [56500.724462] [tdb] Close table 'sessions0.tdb' Apr 26 07:45:53 192.168.122.209 [56503.920513] [tdb] Close table 'cache0.tdb' Apr 26 07:45:53 192.168.122.209 [56504.148291] [tdb] Close table 'filter0.tdb' Apr 26 07:45:53 192.168.122.209 [56504.148725] [tempesta fw] modules are stopped Apr 26 07:45:53 192.168.122.209 [56504.363709] [tempesta fw] exiting... Apr 26 07:45:53 192.168.122.209 [56504.510391] [tdb] Shutdown Tempesta DB Apr 26 07:45:54 192.168.122.209 [56504.756751] End test: cache.test_conditional.TestConditionalHttp.test_none_match_no_quotes_empty_etag_with_extra_spaces Apr 26 07:45:54 192.168.122.209 [56504.781846] Start test: cache.test_conditional.TestConditionalHttp.test_none_match_no_quotes_etag Apr 26 07:45:55 192.168.122.209 [56505.813168] [tdb] Start Tempesta DB Apr 26 07:45:55 192.168.122.209 [56505.959658] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:45:56 192.168.122.209 [56507.384624] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56507.384624] Maybe that's fine, but it's worth checking the [56507.384624] config - if there is no relations between the [56507.384624] names, then host name confusion attack is possible. Apr 26 07:45:57 192.168.122.209 [56507.519807] [tempesta fw] Configuration processing is completed. Apr 26 07:45:57 192.168.122.209 [56507.580130] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:45:57 192.168.122.209 [56507.999721] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:45:57 192.168.122.209 [56508.026825] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:45:57 192.168.122.209 [56508.053102] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:45:57 192.168.122.209 [56508.099817] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:45:57 192.168.122.209 [56508.101228] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:45:57 192.168.122.209 [56508.159808] [tempesta fw] Tempesta FW is ready Apr 26 07:45:58 192.168.122.209 [56508.791390] [tdb] Close table 'client0.tdb' Apr 26 07:45:58 192.168.122.209 [56508.976767] [tdb] Close table 'sessions0.tdb' Apr 26 07:46:01 192.168.122.209 [56512.188162] [tdb] Close table 'cache0.tdb' Apr 26 07:46:01 192.168.122.209 [56512.430710] [tdb] Close table 'filter0.tdb' Apr 26 07:46:01 192.168.122.209 [56512.431152] [tempesta fw] modules are stopped Apr 26 07:46:02 192.168.122.209 [56512.624234] [tempesta fw] exiting... Apr 26 07:46:02 192.168.122.209 [56512.753075] [tdb] Shutdown Tempesta DB Apr 26 07:46:02 192.168.122.209 [56512.968636] End test: cache.test_conditional.TestConditionalHttp.test_none_match_no_quotes_etag Apr 26 07:46:02 192.168.122.209 [56512.991242] Start test: cache.test_conditional.TestConditionalHttp.test_none_match_no_quotes_etag_with_extra_spaces Apr 26 07:46:03 192.168.122.209 [56514.036811] [tdb] Start Tempesta DB Apr 26 07:46:03 192.168.122.209 [56514.169880] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:46:05 192.168.122.209 [56515.657207] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56515.657207] Maybe that's fine, but it's worth checking the [56515.657207] config - if there is no relations between the [56515.657207] names, then host name confusion attack is possible. Apr 26 07:46:05 192.168.122.209 [56515.811886] [tempesta fw] Configuration processing is completed. Apr 26 07:46:05 192.168.122.209 [56515.867597] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:46:05 192.168.122.209 [56516.290093] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:46:05 192.168.122.209 [56516.316506] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:46:05 192.168.122.209 [56516.342507] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:46:05 192.168.122.209 [56516.447968] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:46:05 192.168.122.209 [56516.449728] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:46:05 192.168.122.209 [56516.487900] [tempesta fw] Tempesta FW is ready Apr 26 07:46:06 192.168.122.209 [56517.078711] [tdb] Close table 'client0.tdb' Apr 26 07:46:06 192.168.122.209 [56517.281991] [tdb] Close table 'sessions0.tdb' Apr 26 07:46:10 192.168.122.209 [56520.657975] [tdb] Close table 'cache0.tdb' Apr 26 07:46:10 192.168.122.209 [56520.903979] [tdb] Close table 'filter0.tdb' Apr 26 07:46:10 192.168.122.209 [56520.904408] [tempesta fw] modules are stopped Apr 26 07:46:10 192.168.122.209 [56521.104990] [tempesta fw] exiting... Apr 26 07:46:10 192.168.122.209 [56521.234085] [tdb] Shutdown Tempesta DB Apr 26 07:46:10 192.168.122.209 [56521.451081] End test: cache.test_conditional.TestConditionalHttp.test_none_match_no_quotes_etag_with_extra_spaces Apr 26 07:46:10 192.168.122.209 [56521.469662] Start test: cache.test_conditional.TestConditionalHttp.test_none_match_weak_all Apr 26 07:46:12 192.168.122.209 [56522.577636] [tdb] Start Tempesta DB Apr 26 07:46:12 192.168.122.209 [56522.726452] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:46:13 192.168.122.209 [56524.185313] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56524.185313] Maybe that's fine, but it's worth checking the [56524.185313] config - if there is no relations between the [56524.185313] names, then host name confusion attack is possible. Apr 26 07:46:13 192.168.122.209 [56524.316072] [tempesta fw] Configuration processing is completed. Apr 26 07:46:13 192.168.122.209 [56524.368537] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:46:14 192.168.122.209 [56524.783169] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:46:14 192.168.122.209 [56524.810265] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:46:14 192.168.122.209 [56524.837827] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:46:14 192.168.122.209 [56524.876000] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:46:14 192.168.122.209 [56524.876985] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:46:14 192.168.122.209 [56524.916006] [tempesta fw] Tempesta FW is ready Apr 26 07:46:15 192.168.122.209 [56525.553232] [tdb] Close table 'client0.tdb' Apr 26 07:46:15 192.168.122.209 [56525.738669] [tdb] Close table 'sessions0.tdb' Apr 26 07:46:18 192.168.122.209 [56528.936530] [tdb] Close table 'cache0.tdb' Apr 26 07:46:18 192.168.122.209 [56529.163913] [tdb] Close table 'filter0.tdb' Apr 26 07:46:18 192.168.122.209 [56529.164352] [tempesta fw] modules are stopped Apr 26 07:46:18 192.168.122.209 [56529.375215] [tempesta fw] exiting... Apr 26 07:46:18 192.168.122.209 [56529.497754] [tdb] Shutdown Tempesta DB Apr 26 07:46:19 192.168.122.209 [56529.712225] End test: cache.test_conditional.TestConditionalHttp.test_none_match_weak_all Apr 26 07:46:19 192.168.122.209 [56529.731954] Start test: cache.test_conditional.TestConditionalHttp.test_none_match_weak_clnt Apr 26 07:46:20 192.168.122.209 [56530.813360] [tdb] Start Tempesta DB Apr 26 07:46:20 192.168.122.209 [56530.949303] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:46:21 192.168.122.209 [56532.321469] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56532.321469] Maybe that's fine, but it's worth checking the [56532.321469] config - if there is no relations between the [56532.321469] names, then host name confusion attack is possible. Apr 26 07:46:21 192.168.122.209 [56532.452104] [tempesta fw] Configuration processing is completed. Apr 26 07:46:21 192.168.122.209 [56532.507000] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:46:22 192.168.122.209 [56532.929169] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:46:22 192.168.122.209 [56532.955512] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:46:22 192.168.122.209 [56532.981803] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:46:22 192.168.122.209 [56533.028084] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:46:22 192.168.122.209 [56533.029555] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:46:22 192.168.122.209 [56533.068055] [tempesta fw] Tempesta FW is ready Apr 26 07:46:23 192.168.122.209 [56533.701716] [tdb] Close table 'client0.tdb' Apr 26 07:46:23 192.168.122.209 [56533.893677] [tdb] Close table 'sessions0.tdb' Apr 26 07:46:26 192.168.122.209 [56537.145559] [tdb] Close table 'cache0.tdb' Apr 26 07:46:26 192.168.122.209 [56537.439058] [tdb] Close table 'filter0.tdb' Apr 26 07:46:26 192.168.122.209 [56537.439706] [tempesta fw] modules are stopped Apr 26 07:46:27 192.168.122.209 [56537.629175] [tempesta fw] exiting... Apr 26 07:46:27 192.168.122.209 [56537.731891] [tdb] Shutdown Tempesta DB Apr 26 07:46:27 192.168.122.209 [56537.973413] End test: cache.test_conditional.TestConditionalHttp.test_none_match_weak_clnt Apr 26 07:46:27 192.168.122.209 [56537.993499] Start test: cache.test_conditional.TestConditionalHttp.test_none_match_weak_srv Apr 26 07:46:28 192.168.122.209 [56539.025205] [tdb] Start Tempesta DB Apr 26 07:46:28 192.168.122.209 [56539.181829] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:46:30 192.168.122.209 [56540.693425] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56540.693425] Maybe that's fine, but it's worth checking the [56540.693425] config - if there is no relations between the [56540.693425] names, then host name confusion attack is possible. Apr 26 07:46:30 192.168.122.209 [56540.828276] [tempesta fw] Configuration processing is completed. Apr 26 07:46:30 192.168.122.209 [56540.879519] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:46:30 192.168.122.209 [56541.320301] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:46:30 192.168.122.209 [56541.360889] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:46:30 192.168.122.209 [56541.402859] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:46:30 192.168.122.209 [56541.448306] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:46:30 192.168.122.209 [56541.450109] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:46:30 192.168.122.209 [56541.492228] [tempesta fw] Tempesta FW is ready Apr 26 07:46:31 192.168.122.209 [56542.129385] [tdb] Close table 'client0.tdb' Apr 26 07:46:31 192.168.122.209 [56542.326448] [tdb] Close table 'sessions0.tdb' Apr 26 07:46:34 192.168.122.209 [56545.509590] [tdb] Close table 'cache0.tdb' Apr 26 07:46:35 192.168.122.209 [56545.756881] [tdb] Close table 'filter0.tdb' Apr 26 07:46:35 192.168.122.209 [56545.757307] [tempesta fw] modules are stopped Apr 26 07:46:35 192.168.122.209 [56545.963221] [tempesta fw] exiting... Apr 26 07:46:35 192.168.122.209 [56546.062785] [tdb] Shutdown Tempesta DB Apr 26 07:46:35 192.168.122.209 [56546.267834] End test: cache.test_conditional.TestConditionalHttp.test_none_match_weak_srv Apr 26 07:46:35 192.168.122.209 [56546.294621] Start test: cache.test_conditional.TestConditionalHttp.test_response_without_last_modified Apr 26 07:46:36 192.168.122.209 [56547.344827] [tdb] Start Tempesta DB Apr 26 07:46:36 192.168.122.209 [56547.491656] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:46:38 192.168.122.209 [56548.961627] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56548.961627] Maybe that's fine, but it's worth checking the [56548.961627] config - if there is no relations between the [56548.961627] names, then host name confusion attack is possible. Apr 26 07:46:38 192.168.122.209 [56549.108369] [tempesta fw] Configuration processing is completed. Apr 26 07:46:38 192.168.122.209 [56549.163983] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:46:39 192.168.122.209 [56549.591055] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:46:39 192.168.122.209 [56549.617524] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:46:39 192.168.122.209 [56549.643596] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:46:39 192.168.122.209 [56549.688324] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:46:39 192.168.122.209 [56549.689493] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:46:39 192.168.122.209 [56549.732317] [tempesta fw] Tempesta FW is ready Apr 26 07:46:39 192.168.122.209 [56550.387060] [tdb] Close table 'client0.tdb' Apr 26 07:46:40 192.168.122.209 [56550.583230] [tdb] Close table 'sessions0.tdb' Apr 26 07:46:43 192.168.122.209 [56553.817135] [tdb] Close table 'cache0.tdb' Apr 26 07:46:43 192.168.122.209 [56554.050601] [tdb] Close table 'filter0.tdb' Apr 26 07:46:43 192.168.122.209 [56554.051033] [tempesta fw] modules are stopped Apr 26 07:46:43 192.168.122.209 [56554.221352] [tempesta fw] exiting... Apr 26 07:46:43 192.168.122.209 [56554.350002] [tdb] Shutdown Tempesta DB Apr 26 07:46:44 192.168.122.209 [56554.571510] End test: cache.test_conditional.TestConditionalHttp.test_response_without_last_modified Apr 26 07:46:44 192.168.122.209 [56554.590045] Start test: cache.test_conditional.TestConditionalHttp.test_response_without_last_modified_and_date Apr 26 07:46:45 192.168.122.209 [56555.652687] [tdb] Start Tempesta DB Apr 26 07:46:45 192.168.122.209 [56555.786680] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:46:46 192.168.122.209 [56557.201734] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56557.201734] Maybe that's fine, but it's worth checking the [56557.201734] config - if there is no relations between the [56557.201734] names, then host name confusion attack is possible. Apr 26 07:46:46 192.168.122.209 [56557.336490] [tempesta fw] Configuration processing is completed. Apr 26 07:46:46 192.168.122.209 [56557.391024] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:46:47 192.168.122.209 [56557.804756] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:46:47 192.168.122.209 [56557.839499] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:46:47 192.168.122.209 [56557.866303] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:46:47 192.168.122.209 [56557.908484] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:46:47 192.168.122.209 [56557.909527] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:46:47 192.168.122.209 [56557.956424] [tempesta fw] Tempesta FW is ready Apr 26 07:46:48 192.168.122.209 [56558.554806] [tdb] Close table 'client0.tdb' Apr 26 07:46:48 192.168.122.209 [56558.749790] [tdb] Close table 'sessions0.tdb' Apr 26 07:46:51 192.168.122.209 [56561.947849] [tdb] Close table 'cache0.tdb' Apr 26 07:46:51 192.168.122.209 [56562.175663] [tdb] Close table 'filter0.tdb' Apr 26 07:46:51 192.168.122.209 [56562.176094] [tempesta fw] modules are stopped Apr 26 07:46:51 192.168.122.209 [56562.369516] [tempesta fw] exiting... Apr 26 07:46:52 192.168.122.209 [56562.522271] [tdb] Shutdown Tempesta DB Apr 26 07:46:52 192.168.122.209 [56562.741117] End test: cache.test_conditional.TestConditionalHttp.test_response_without_last_modified_and_date Apr 26 07:46:52 192.168.122.209 [56562.752232] Start test: cache.test_conditional.TestConditionalHttp.test_response_without_last_modified_and_date_nc Apr 26 07:46:53 192.168.122.209 [56563.736670] [tdb] Start Tempesta DB Apr 26 07:46:53 192.168.122.209 [56563.872909] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:46:54 192.168.122.209 [56565.293836] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56565.293836] Maybe that's fine, but it's worth checking the [56565.293836] config - if there is no relations between the [56565.293836] names, then host name confusion attack is possible. Apr 26 07:46:54 192.168.122.209 [56565.428601] [tempesta fw] Configuration processing is completed. Apr 26 07:46:54 192.168.122.209 [56565.483382] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:46:55 192.168.122.209 [56565.960224] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:46:55 192.168.122.209 [56565.989578] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:46:55 192.168.122.209 [56566.018952] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:46:55 192.168.122.209 [56566.064606] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:46:55 192.168.122.209 [56566.066074] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:46:55 192.168.122.209 [56566.104539] [tempesta fw] Tempesta FW is ready Apr 26 07:46:56 192.168.122.209 [56566.684540] [tdb] Close table 'client0.tdb' Apr 26 07:46:56 192.168.122.209 [56566.868183] [tdb] Close table 'sessions0.tdb' Apr 26 07:46:59 192.168.122.209 [56570.131858] [tdb] Close table 'cache0.tdb' Apr 26 07:46:59 192.168.122.209 [56570.378586] [tdb] Close table 'filter0.tdb' Apr 26 07:46:59 192.168.122.209 [56570.379025] [tempesta fw] modules are stopped Apr 26 07:47:00 192.168.122.209 [56570.564411] [tempesta fw] exiting... Apr 26 07:47:00 192.168.122.209 [56570.666700] [tdb] Shutdown Tempesta DB Apr 26 07:47:00 192.168.122.209 [56570.899437] End test: cache.test_conditional.TestConditionalHttp.test_response_without_last_modified_and_date_nc Apr 26 07:47:00 192.168.122.209 [56570.914073] Start test: cache.test_conditional.TestConditionalHttp.test_response_without_last_modified_nc Apr 26 07:47:01 192.168.122.209 [56572.043709] [tdb] Start Tempesta DB Apr 26 07:47:01 192.168.122.209 [56572.189237] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:47:03 192.168.122.209 [56573.609943] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56573.609943] Maybe that's fine, but it's worth checking the [56573.609943] config - if there is no relations between the [56573.609943] names, then host name confusion attack is possible. Apr 26 07:47:03 192.168.122.209 [56573.752640] [tempesta fw] Configuration processing is completed. Apr 26 07:47:03 192.168.122.209 [56573.804530] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:47:03 192.168.122.209 [56574.225193] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:47:03 192.168.122.209 [56574.252360] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:47:03 192.168.122.209 [56574.279071] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:47:03 192.168.122.209 [56574.336706] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:47:03 192.168.122.209 [56574.338467] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:47:03 192.168.122.209 [56574.376647] [tempesta fw] Tempesta FW is ready Apr 26 07:47:04 192.168.122.209 [56574.968457] [tdb] Close table 'client0.tdb' Apr 26 07:47:04 192.168.122.209 [56575.156782] [tdb] Close table 'sessions0.tdb' Apr 26 07:47:07 192.168.122.209 [56578.407141] [tdb] Close table 'cache0.tdb' Apr 26 07:47:08 192.168.122.209 [56578.659439] [tdb] Close table 'filter0.tdb' Apr 26 07:47:08 192.168.122.209 [56578.659872] [tempesta fw] modules are stopped Apr 26 07:47:08 192.168.122.209 [56578.833765] [tempesta fw] exiting... Apr 26 07:47:08 192.168.122.209 [56578.946722] [tdb] Shutdown Tempesta DB Apr 26 07:47:08 192.168.122.209 [56579.156017] End test: cache.test_conditional.TestConditionalHttp.test_response_without_last_modified_nc Apr 26 07:47:08 192.168.122.209 [56579.175151] Start test: cache.test_conditional.TestNotModifiedResponseHeadersH2.test_cachable_headers_cache_control Apr 26 07:47:09 192.168.122.209 [56580.171019] [tdb] Start Tempesta DB Apr 26 07:47:09 192.168.122.209 [56580.310449] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:47:11 192.168.122.209 [56581.666010] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56581.666010] Maybe that's fine, but it's worth checking the [56581.666010] config - if there is no relations between the [56581.666010] names, then host name confusion attack is possible. Apr 26 07:47:11 192.168.122.209 [56581.812795] [tempesta fw] Configuration processing is completed. Apr 26 07:47:11 192.168.122.209 [56581.864174] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:47:11 192.168.122.209 [56582.287402] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:47:11 192.168.122.209 [56582.314550] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:47:11 192.168.122.209 [56582.341202] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:47:11 192.168.122.209 [56582.384750] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:47:11 192.168.122.209 [56582.385917] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:47:11 192.168.122.209 [56582.432726] [tempesta fw] Tempesta FW is ready Apr 26 07:47:12 192.168.122.209 [56583.122478] [tdb] Close table 'client0.tdb' Apr 26 07:47:12 192.168.122.209 [56583.291714] [tdb] Close table 'sessions0.tdb' Apr 26 07:47:16 192.168.122.209 [56586.567155] [tdb] Close table 'cache0.tdb' Apr 26 07:47:16 192.168.122.209 [56586.808161] [tdb] Close table 'filter0.tdb' Apr 26 07:47:16 192.168.122.209 [56586.808597] [tempesta fw] modules are stopped Apr 26 07:47:16 192.168.122.209 [56587.013328] [tempesta fw] exiting... Apr 26 07:47:16 192.168.122.209 [56587.140364] [tdb] Shutdown Tempesta DB Apr 26 07:47:16 192.168.122.209 [56587.358852] End test: cache.test_conditional.TestNotModifiedResponseHeadersH2.test_cachable_headers_cache_control Apr 26 07:47:16 192.168.122.209 [56587.370840] Start test: cache.test_conditional.TestNotModifiedResponseHeadersH2.test_cachable_headers_content_location Apr 26 07:47:17 192.168.122.209 [56588.425169] [tdb] Start Tempesta DB Apr 26 07:47:18 192.168.122.209 [56588.569873] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:47:19 192.168.122.209 [56590.090182] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56590.090182] Maybe that's fine, but it's worth checking the [56590.090182] config - if there is no relations between the [56590.090182] names, then host name confusion attack is possible. Apr 26 07:47:19 192.168.122.209 [56590.232903] [tempesta fw] Configuration processing is completed. Apr 26 07:47:19 192.168.122.209 [56590.292598] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:47:20 192.168.122.209 [56590.718702] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:47:20 192.168.122.209 [56590.745612] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:47:20 192.168.122.209 [56590.772372] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:47:20 192.168.122.209 [56590.820905] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:47:20 192.168.122.209 [56590.822623] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:47:20 192.168.122.209 [56590.864832] [tempesta fw] Tempesta FW is ready Apr 26 07:47:21 192.168.122.209 [56591.603727] [tdb] Close table 'client0.tdb' Apr 26 07:47:21 192.168.122.209 [56591.795491] [tdb] Close table 'sessions0.tdb' Apr 26 07:47:24 192.168.122.209 [56595.040672] [tdb] Close table 'cache0.tdb' Apr 26 07:47:24 192.168.122.209 [56595.279918] [tdb] Close table 'filter0.tdb' Apr 26 07:47:24 192.168.122.209 [56595.280347] [tempesta fw] modules are stopped Apr 26 07:47:24 192.168.122.209 [56595.506482] [tempesta fw] exiting... Apr 26 07:47:25 192.168.122.209 [56595.656052] [tdb] Shutdown Tempesta DB Apr 26 07:47:25 192.168.122.209 [56595.884992] End test: cache.test_conditional.TestNotModifiedResponseHeadersH2.test_cachable_headers_content_location Apr 26 07:47:25 192.168.122.209 [56595.903145] Start test: cache.test_conditional.TestNotModifiedResponseHeadersH2.test_cachable_headers_etag Apr 26 07:47:26 192.168.122.209 [56596.998558] [tdb] Start Tempesta DB Apr 26 07:47:26 192.168.122.209 [56597.128067] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:47:28 192.168.122.209 [56598.570275] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56598.570275] Maybe that's fine, but it's worth checking the [56598.570275] config - if there is no relations between the [56598.570275] names, then host name confusion attack is possible. Apr 26 07:47:28 192.168.122.209 [56598.705026] [tempesta fw] Configuration processing is completed. Apr 26 07:47:28 192.168.122.209 [56598.755995] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:47:28 192.168.122.209 [56599.187622] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:47:28 192.168.122.209 [56599.215077] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:47:28 192.168.122.209 [56599.242730] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:47:28 192.168.122.209 [56599.301012] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:47:28 192.168.122.209 [56599.302757] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:47:28 192.168.122.209 [56599.340952] [tempesta fw] Tempesta FW is ready Apr 26 07:47:29 192.168.122.209 [56599.992576] [tdb] Close table 'client0.tdb' Apr 26 07:47:29 192.168.122.209 [56600.189525] [tdb] Close table 'sessions0.tdb' Apr 26 07:47:32 192.168.122.209 [56603.426657] [tdb] Close table 'cache0.tdb' Apr 26 07:47:33 192.168.122.209 [56603.672448] [tdb] Close table 'filter0.tdb' Apr 26 07:47:33 192.168.122.209 [56603.672894] [tempesta fw] modules are stopped Apr 26 07:47:33 192.168.122.209 [56603.842706] [tempesta fw] exiting... Apr 26 07:47:33 192.168.122.209 [56603.945075] [tdb] Shutdown Tempesta DB Apr 26 07:47:33 192.168.122.209 [56604.147686] End test: cache.test_conditional.TestNotModifiedResponseHeadersH2.test_cachable_headers_etag Apr 26 07:47:33 192.168.122.209 [56604.168293] Start test: cache.test_conditional.TestNotModifiedResponseHeadersH2.test_cachable_headers_expires Apr 26 07:47:34 192.168.122.209 [56605.258142] [tdb] Start Tempesta DB Apr 26 07:47:34 192.168.122.209 [56605.398666] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:47:36 192.168.122.209 [56606.806367] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56606.806367] Maybe that's fine, but it's worth checking the [56606.806367] config - if there is no relations between the [56606.806367] names, then host name confusion attack is possible. Apr 26 07:47:36 192.168.122.209 [56606.941136] [tempesta fw] Configuration processing is completed. Apr 26 07:47:36 192.168.122.209 [56607.002485] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:47:36 192.168.122.209 [56607.442889] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:47:36 192.168.122.209 [56607.469796] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:47:36 192.168.122.209 [56607.496088] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:47:37 192.168.122.209 [56607.541095] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:47:37 192.168.122.209 [56607.542853] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:47:37 192.168.122.209 [56607.581047] [tempesta fw] Tempesta FW is ready Apr 26 07:47:37 192.168.122.209 [56608.250045] [tdb] Close table 'client0.tdb' Apr 26 07:47:37 192.168.122.209 [56608.441937] [tdb] Close table 'sessions0.tdb' Apr 26 07:47:41 192.168.122.209 [56611.656995] [tdb] Close table 'cache0.tdb' Apr 26 07:47:41 192.168.122.209 [56611.914294] [tdb] Close table 'filter0.tdb' Apr 26 07:47:41 192.168.122.209 [56611.914747] [tempesta fw] modules are stopped Apr 26 07:47:41 192.168.122.209 [56612.129630] [tempesta fw] exiting... Apr 26 07:47:41 192.168.122.209 [56612.258839] [tdb] Shutdown Tempesta DB Apr 26 07:47:41 192.168.122.209 [56612.477447] End test: cache.test_conditional.TestNotModifiedResponseHeadersH2.test_cachable_headers_expires Apr 26 07:47:41 192.168.122.209 [56612.496576] Start test: cache.test_conditional.TestNotModifiedResponseHeadersH2.test_cachable_headers_vary Apr 26 07:47:43 192.168.122.209 [56613.604750] [tdb] Start Tempesta DB Apr 26 07:47:43 192.168.122.209 [56613.742553] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:47:44 192.168.122.209 [56615.206438] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56615.206438] Maybe that's fine, but it's worth checking the [56615.206438] config - if there is no relations between the [56615.206438] names, then host name confusion attack is possible. Apr 26 07:47:44 192.168.122.209 [56615.337205] [tempesta fw] Configuration processing is completed. Apr 26 07:47:44 192.168.122.209 [56615.388698] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:47:45 192.168.122.209 [56615.828469] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:47:45 192.168.122.209 [56615.857599] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:47:45 192.168.122.209 [56615.885851] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:47:45 192.168.122.209 [56615.933267] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:47:45 192.168.122.209 [56615.935277] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:47:45 192.168.122.209 [56615.973163] [tempesta fw] Tempesta FW is ready Apr 26 07:47:46 192.168.122.209 [56616.638893] [tdb] Close table 'client0.tdb' Apr 26 07:47:46 192.168.122.209 [56616.827276] [tdb] Close table 'sessions0.tdb' Apr 26 07:47:49 192.168.122.209 [56620.156774] [tdb] Close table 'cache0.tdb' Apr 26 07:47:49 192.168.122.209 [56620.411445] [tdb] Close table 'filter0.tdb' Apr 26 07:47:49 192.168.122.209 [56620.411917] [tempesta fw] modules are stopped Apr 26 07:47:50 192.168.122.209 [56620.610534] [tempesta fw] exiting... Apr 26 07:47:50 192.168.122.209 [56620.726094] [tdb] Shutdown Tempesta DB Apr 26 07:47:50 192.168.122.209 [56620.976118] End test: cache.test_conditional.TestNotModifiedResponseHeadersH2.test_cachable_headers_vary Apr 26 07:47:50 192.168.122.209 [56620.989973] Start test: cache.test_conditional.TestNotModifiedResponseHeadersH2.test_non_cachable_header Apr 26 07:47:51 192.168.122.209 [56622.091416] [tdb] Start Tempesta DB Apr 26 07:47:51 192.168.122.209 [56622.268255] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:47:53 192.168.122.209 [56623.722513] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56623.722513] Maybe that's fine, but it's worth checking the [56623.722513] config - if there is no relations between the [56623.722513] names, then host name confusion attack is possible. Apr 26 07:47:53 192.168.122.209 [56623.865337] [tempesta fw] Configuration processing is completed. Apr 26 07:47:53 192.168.122.209 [56623.921451] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:47:53 192.168.122.209 [56624.389291] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:47:53 192.168.122.209 [56624.436417] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:47:53 192.168.122.209 [56624.469696] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:47:54 192.168.122.209 [56624.593728] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:47:54 192.168.122.209 [56624.595805] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:47:54 192.168.122.209 [56624.649256] [tempesta fw] Tempesta FW is ready Apr 26 07:47:54 192.168.122.209 [56625.275567] [tdb] Close table 'client0.tdb' Apr 26 07:47:54 192.168.122.209 [56625.471669] [tdb] Close table 'sessions0.tdb' Apr 26 07:47:58 192.168.122.209 [56628.696180] [tdb] Close table 'cache0.tdb' Apr 26 07:47:58 192.168.122.209 [56628.935190] [tdb] Close table 'filter0.tdb' Apr 26 07:47:58 192.168.122.209 [56628.935633] [tempesta fw] modules are stopped Apr 26 07:47:58 192.168.122.209 [56629.122537] [tempesta fw] exiting... Apr 26 07:47:58 192.168.122.209 [56629.234974] [tdb] Shutdown Tempesta DB Apr 26 07:47:58 192.168.122.209 [56629.446364] End test: cache.test_conditional.TestNotModifiedResponseHeadersH2.test_non_cachable_header Apr 26 07:47:58 192.168.122.209 [56629.458244] Start test: cache.test_conditional.TestNotModifiedResponseHeadersHttp.test_cachable_headers_cache_control Apr 26 07:48:00 192.168.122.209 [56630.531167] [tdb] Start Tempesta DB Apr 26 07:48:00 192.168.122.209 [56630.674916] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:48:01 192.168.122.209 [56632.150681] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56632.150681] Maybe that's fine, but it's worth checking the [56632.150681] config - if there is no relations between the [56632.150681] names, then host name confusion attack is possible. Apr 26 07:48:01 192.168.122.209 [56632.285451] [tempesta fw] Configuration processing is completed. Apr 26 07:48:01 192.168.122.209 [56632.341826] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:48:02 192.168.122.209 [56632.820241] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:48:02 192.168.122.209 [56632.850710] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:48:02 192.168.122.209 [56632.881167] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:48:02 192.168.122.209 [56632.925452] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:48:02 192.168.122.209 [56632.927167] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:48:02 192.168.122.209 [56632.977362] [tempesta fw] Tempesta FW is ready Apr 26 07:48:03 192.168.122.209 [56633.571620] [tdb] Close table 'client0.tdb' Apr 26 07:48:03 192.168.122.209 [56633.779962] [tdb] Close table 'sessions0.tdb' Apr 26 07:48:06 192.168.122.209 [56637.081734] [tdb] Close table 'cache0.tdb' Apr 26 07:48:06 192.168.122.209 [56637.359090] [tdb] Close table 'filter0.tdb' Apr 26 07:48:06 192.168.122.209 [56637.359521] [tempesta fw] modules are stopped Apr 26 07:48:07 192.168.122.209 [56637.555389] [tempesta fw] exiting... Apr 26 07:48:07 192.168.122.209 [56637.664623] [tdb] Shutdown Tempesta DB Apr 26 07:48:07 192.168.122.209 [56637.891570] End test: cache.test_conditional.TestNotModifiedResponseHeadersHttp.test_cachable_headers_cache_control Apr 26 07:48:07 192.168.122.209 [56637.905815] Start test: cache.test_conditional.TestNotModifiedResponseHeadersHttp.test_cachable_headers_content_location Apr 26 07:48:08 192.168.122.209 [56639.010294] [tdb] Start Tempesta DB Apr 26 07:48:08 192.168.122.209 [56639.172188] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:48:10 192.168.122.209 [56640.618828] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56640.618828] Maybe that's fine, but it's worth checking the [56640.618828] config - if there is no relations between the [56640.618828] names, then host name confusion attack is possible. Apr 26 07:48:10 192.168.122.209 [56640.761535] [tempesta fw] Configuration processing is completed. Apr 26 07:48:10 192.168.122.209 [56640.812076] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:48:10 192.168.122.209 [56641.246533] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:48:10 192.168.122.209 [56641.275391] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:48:10 192.168.122.209 [56641.313425] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:48:10 192.168.122.209 [56641.385558] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:48:10 192.168.122.209 [56641.387336] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:48:10 192.168.122.209 [56641.433467] [tempesta fw] Tempesta FW is ready Apr 26 07:48:11 192.168.122.209 [56642.053443] [tdb] Close table 'client0.tdb' Apr 26 07:48:11 192.168.122.209 [56642.246767] [tdb] Close table 'sessions0.tdb' Apr 26 07:48:14 192.168.122.209 [56645.446020] [tdb] Close table 'cache0.tdb' Apr 26 07:48:15 192.168.122.209 [56645.676084] [tdb] Close table 'filter0.tdb' Apr 26 07:48:15 192.168.122.209 [56645.676495] [tempesta fw] modules are stopped Apr 26 07:48:15 192.168.122.209 [56645.870980] [tempesta fw] exiting... Apr 26 07:48:15 192.168.122.209 [56645.994871] [tdb] Shutdown Tempesta DB Apr 26 07:48:15 192.168.122.209 [56646.219711] End test: cache.test_conditional.TestNotModifiedResponseHeadersHttp.test_cachable_headers_content_location Apr 26 07:48:15 192.168.122.209 [56646.236007] Start test: cache.test_conditional.TestNotModifiedResponseHeadersHttp.test_cachable_headers_etag Apr 26 07:48:16 192.168.122.209 [56647.299351] [tdb] Start Tempesta DB Apr 26 07:48:16 192.168.122.209 [56647.432787] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:48:18 192.168.122.209 [56648.842866] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56648.842866] Maybe that's fine, but it's worth checking the [56648.842866] config - if there is no relations between the [56648.842866] names, then host name confusion attack is possible. Apr 26 07:48:18 192.168.122.209 [56648.977622] [tempesta fw] Configuration processing is completed. Apr 26 07:48:18 192.168.122.209 [56649.028074] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:48:18 192.168.122.209 [56649.512649] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:48:19 192.168.122.209 [56649.556764] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:48:19 192.168.122.209 [56649.590893] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:48:19 192.168.122.209 [56649.637584] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:48:19 192.168.122.209 [56649.639317] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:48:19 192.168.122.209 [56649.689568] [tempesta fw] Tempesta FW is ready Apr 26 07:48:19 192.168.122.209 [56650.288796] [tdb] Close table 'client0.tdb' Apr 26 07:48:19 192.168.122.209 [56650.477643] [tdb] Close table 'sessions0.tdb' Apr 26 07:48:23 192.168.122.209 [56653.908248] [tdb] Close table 'cache0.tdb' Apr 26 07:48:23 192.168.122.209 [56654.171948] [tdb] Close table 'filter0.tdb' Apr 26 07:48:23 192.168.122.209 [56654.172397] [tempesta fw] modules are stopped Apr 26 07:48:23 192.168.122.209 [56654.365871] [tempesta fw] exiting... Apr 26 07:48:23 192.168.122.209 [56654.495389] [tdb] Shutdown Tempesta DB Apr 26 07:48:24 192.168.122.209 [56654.722854] End test: cache.test_conditional.TestNotModifiedResponseHeadersHttp.test_cachable_headers_etag Apr 26 07:48:24 192.168.122.209 [56654.734048] Start test: cache.test_conditional.TestNotModifiedResponseHeadersHttp.test_cachable_headers_expires Apr 26 07:48:25 192.168.122.209 [56655.798861] [tdb] Start Tempesta DB Apr 26 07:48:25 192.168.122.209 [56655.948764] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:48:26 192.168.122.209 [56657.379035] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56657.379035] Maybe that's fine, but it's worth checking the [56657.379035] config - if there is no relations between the [56657.379035] names, then host name confusion attack is possible. Apr 26 07:48:27 192.168.122.209 [56657.529735] [tempesta fw] Configuration processing is completed. Apr 26 07:48:27 192.168.122.209 [56657.580550] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:48:27 192.168.122.209 [56658.007517] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:48:27 192.168.122.209 [56658.035110] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:48:27 192.168.122.209 [56658.063435] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:48:27 192.168.122.209 [56658.109742] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:48:27 192.168.122.209 [56658.111532] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:48:27 192.168.122.209 [56658.153677] [tempesta fw] Tempesta FW is ready Apr 26 07:48:28 192.168.122.209 [56658.736849] [tdb] Close table 'client0.tdb' Apr 26 07:48:28 192.168.122.209 [56658.915063] [tdb] Close table 'sessions0.tdb' Apr 26 07:48:31 192.168.122.209 [56662.142159] [tdb] Close table 'cache0.tdb' Apr 26 07:48:31 192.168.122.209 [56662.392063] [tdb] Close table 'filter0.tdb' Apr 26 07:48:31 192.168.122.209 [56662.392500] [tempesta fw] modules are stopped Apr 26 07:48:32 192.168.122.209 [56662.593188] [tempesta fw] exiting... Apr 26 07:48:32 192.168.122.209 [56662.713023] [tdb] Shutdown Tempesta DB Apr 26 07:48:32 192.168.122.209 [56662.956061] End test: cache.test_conditional.TestNotModifiedResponseHeadersHttp.test_cachable_headers_expires Apr 26 07:48:32 192.168.122.209 [56662.975257] Start test: cache.test_conditional.TestNotModifiedResponseHeadersHttp.test_cachable_headers_vary Apr 26 07:48:33 192.168.122.209 [56664.051653] [tdb] Start Tempesta DB Apr 26 07:48:33 192.168.122.209 [56664.204717] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:48:35 192.168.122.209 [56665.615089] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56665.615089] Maybe that's fine, but it's worth checking the [56665.615089] config - if there is no relations between the [56665.615089] names, then host name confusion attack is possible. Apr 26 07:48:35 192.168.122.209 [56665.761863] [tempesta fw] Configuration processing is completed. Apr 26 07:48:35 192.168.122.209 [56665.816607] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:48:35 192.168.122.209 [56666.241569] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:48:35 192.168.122.209 [56666.268771] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:48:35 192.168.122.209 [56666.294999] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:48:35 192.168.122.209 [56666.337839] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:48:35 192.168.122.209 [56666.339592] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:48:35 192.168.122.209 [56666.385780] [tempesta fw] Tempesta FW is ready Apr 26 07:48:36 192.168.122.209 [56667.016890] [tdb] Close table 'client0.tdb' Apr 26 07:48:36 192.168.122.209 [56667.212907] [tdb] Close table 'sessions0.tdb' Apr 26 07:48:39 192.168.122.209 [56670.469983] [tdb] Close table 'cache0.tdb' Apr 26 07:48:40 192.168.122.209 [56670.708884] [tdb] Close table 'filter0.tdb' Apr 26 07:48:40 192.168.122.209 [56670.709333] [tempesta fw] modules are stopped Apr 26 07:48:40 192.168.122.209 [56670.919424] [tempesta fw] exiting... Apr 26 07:48:40 192.168.122.209 [56671.030526] [tdb] Shutdown Tempesta DB Apr 26 07:48:40 192.168.122.209 [56671.250551] End test: cache.test_conditional.TestNotModifiedResponseHeadersHttp.test_cachable_headers_vary Apr 26 07:48:40 192.168.122.209 [56671.269497] Start test: cache.test_conditional.TestNotModifiedResponseHeadersHttp.test_non_cachable_header Apr 26 07:48:41 192.168.122.209 [56672.287722] [tdb] Start Tempesta DB Apr 26 07:48:41 192.168.122.209 [56672.436807] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:48:43 192.168.122.209 [56673.894909] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56673.894909] Maybe that's fine, but it's worth checking the [56673.894909] config - if there is no relations between the [56673.894909] names, then host name confusion attack is possible. Apr 26 07:48:43 192.168.122.209 [56674.025935] [tempesta fw] Configuration processing is completed. Apr 26 07:48:43 192.168.122.209 [56674.077099] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:48:44 192.168.122.209 [56674.528717] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:48:44 192.168.122.209 [56674.555876] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:48:44 192.168.122.209 [56674.582245] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:48:44 192.168.122.209 [56674.653962] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:48:44 192.168.122.209 [56674.655760] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:48:44 192.168.122.209 [56674.705826] [tempesta fw] Tempesta FW is ready Apr 26 07:48:44 192.168.122.209 [56675.279401] [tdb] Close table 'client0.tdb' Apr 26 07:48:44 192.168.122.209 [56675.489193] [tdb] Close table 'sessions0.tdb' Apr 26 07:48:48 192.168.122.209 [56678.714544] [tdb] Close table 'cache0.tdb' Apr 26 07:48:48 192.168.122.209 [56678.972836] [tdb] Close table 'filter0.tdb' Apr 26 07:48:48 192.168.122.209 [56678.973267] [tempesta fw] modules are stopped Apr 26 07:48:48 192.168.122.209 [56679.168607] [tempesta fw] exiting... Apr 26 07:48:48 192.168.122.209 [56679.281362] [tdb] Shutdown Tempesta DB Apr 26 07:48:48 192.168.122.209 [56679.502258] End test: cache.test_conditional.TestNotModifiedResponseHeadersHttp.test_non_cachable_header Apr 26 07:48:49 192.168.122.209 [56679.523849] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_authorization_in_first_request_must_revalidate_in_response Apr 26 07:48:50 192.168.122.209 [56680.640145] [tdb] Start Tempesta DB Apr 26 07:48:50 192.168.122.209 [56680.787759] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:48:51 192.168.122.209 [56682.223292] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56682.223292] Maybe that's fine, but it's worth checking the [56682.223292] config - if there is no relations between the [56682.223292] names, then host name confusion attack is possible. Apr 26 07:48:51 192.168.122.209 [56682.357988] [tempesta fw] Configuration processing is completed. Apr 26 07:48:51 192.168.122.209 [56682.412714] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:48:52 192.168.122.209 [56682.842150] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:48:52 192.168.122.209 [56682.876833] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:48:52 192.168.122.209 [56682.903568] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:48:52 192.168.122.209 [56682.938045] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:48:52 192.168.122.209 [56682.939763] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:48:52 192.168.122.209 [56682.977988] [tempesta fw] Tempesta FW is ready Apr 26 07:48:53 192.168.122.209 [56683.616933] [tdb] Close table 'client0.tdb' Apr 26 07:48:53 192.168.122.209 [56683.809517] [tdb] Close table 'sessions0.tdb' Apr 26 07:48:56 192.168.122.209 [56687.045128] [tdb] Close table 'cache0.tdb' Apr 26 07:48:56 192.168.122.209 [56687.276430] [tdb] Close table 'filter0.tdb' Apr 26 07:48:56 192.168.122.209 [56687.276884] [tempesta fw] modules are stopped Apr 26 07:48:56 192.168.122.209 [56687.487755] [tempesta fw] exiting... Apr 26 07:48:57 192.168.122.209 [56687.632812] [tdb] Shutdown Tempesta DB Apr 26 07:48:57 192.168.122.209 [56687.849833] End test: cache.test_h2_cache_control.TestH2CacheControl.test_authorization_in_first_request_must_revalidate_in_response Apr 26 07:48:57 192.168.122.209 [56687.867940] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_authorization_in_first_request_proxy_revalidate_in_response Apr 26 07:48:58 192.168.122.209 [56688.965817] [tdb] Start Tempesta DB Apr 26 07:48:58 192.168.122.209 [56689.126108] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:49:00 192.168.122.209 [56690.531505] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56690.531505] Maybe that's fine, but it's worth checking the [56690.531505] config - if there is no relations between the [56690.531505] names, then host name confusion attack is possible. Apr 26 07:49:00 192.168.122.209 [56690.650155] [tempesta fw] Configuration processing is completed. Apr 26 07:49:00 192.168.122.209 [56690.702381] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:49:00 192.168.122.209 [56691.125713] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:49:00 192.168.122.209 [56691.152577] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:49:00 192.168.122.209 [56691.179410] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:49:00 192.168.122.209 [56691.226173] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:49:00 192.168.122.209 [56691.227903] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:49:00 192.168.122.209 [56691.266109] [tempesta fw] Tempesta FW is ready Apr 26 07:49:01 192.168.122.209 [56691.922503] [tdb] Close table 'client0.tdb' Apr 26 07:49:01 192.168.122.209 [56692.108285] [tdb] Close table 'sessions0.tdb' Apr 26 07:49:04 192.168.122.209 [56695.328959] [tdb] Close table 'cache0.tdb' Apr 26 07:49:05 192.168.122.209 [56695.573677] [tdb] Close table 'filter0.tdb' Apr 26 07:49:05 192.168.122.209 [56695.574155] [tempesta fw] modules are stopped Apr 26 07:49:05 192.168.122.209 [56695.754378] [tempesta fw] exiting... Apr 26 07:49:05 192.168.122.209 [56695.871023] [tdb] Shutdown Tempesta DB Apr 26 07:49:05 192.168.122.209 [56696.098921] End test: cache.test_h2_cache_control.TestH2CacheControl.test_authorization_in_first_request_proxy_revalidate_in_response Apr 26 07:49:05 192.168.122.209 [56696.111893] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_authorization_in_first_request_public_in_response Apr 26 07:49:06 192.168.122.209 [56697.123665] [tdb] Start Tempesta DB Apr 26 07:49:06 192.168.122.209 [56697.272671] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:49:08 192.168.122.209 [56698.724018] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56698.724018] Maybe that's fine, but it's worth checking the [56698.724018] config - if there is no relations between the [56698.724018] names, then host name confusion attack is possible. Apr 26 07:49:08 192.168.122.209 [56698.850256] [tempesta fw] Configuration processing is completed. Apr 26 07:49:08 192.168.122.209 [56698.905267] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:49:08 192.168.122.209 [56699.334786] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:49:08 192.168.122.209 [56699.361881] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:49:08 192.168.122.209 [56699.390393] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:49:08 192.168.122.209 [56699.438255] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:49:08 192.168.122.209 [56699.439996] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:49:08 192.168.122.209 [56699.490174] [tempesta fw] Tempesta FW is ready Apr 26 07:49:09 192.168.122.209 [56700.097104] [tdb] Close table 'client0.tdb' Apr 26 07:49:09 192.168.122.209 [56700.289094] [tdb] Close table 'sessions0.tdb' Apr 26 07:49:13 192.168.122.209 [56703.541044] [tdb] Close table 'cache0.tdb' Apr 26 07:49:13 192.168.122.209 [56703.761055] [tdb] Close table 'filter0.tdb' Apr 26 07:49:13 192.168.122.209 [56703.761486] [tempesta fw] modules are stopped Apr 26 07:49:13 192.168.122.209 [56704.008195] [tempesta fw] exiting... Apr 26 07:49:13 192.168.122.209 [56704.129305] [tdb] Shutdown Tempesta DB Apr 26 07:49:13 192.168.122.209 [56704.374685] End test: cache.test_h2_cache_control.TestH2CacheControl.test_authorization_in_first_request_public_in_response Apr 26 07:49:13 192.168.122.209 [56704.391556] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_authorization_in_first_request_s_maxage_in_response Apr 26 07:49:14 192.168.122.209 [56705.429436] [tdb] Start Tempesta DB Apr 26 07:49:15 192.168.122.209 [56705.564562] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:49:16 192.168.122.209 [56706.963583] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56706.963583] Maybe that's fine, but it's worth checking the [56706.963583] config - if there is no relations between the [56706.963583] names, then host name confusion attack is possible. Apr 26 07:49:16 192.168.122.209 [56707.098368] [tempesta fw] Configuration processing is completed. Apr 26 07:49:16 192.168.122.209 [56707.149604] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:49:17 192.168.122.209 [56707.571562] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:49:17 192.168.122.209 [56707.598942] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:49:17 192.168.122.209 [56707.630493] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:49:17 192.168.122.209 [56707.678352] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:49:17 192.168.122.209 [56707.680084] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:49:17 192.168.122.209 [56707.730296] [tempesta fw] Tempesta FW is ready Apr 26 07:49:17 192.168.122.209 [56708.387785] [tdb] Close table 'client0.tdb' Apr 26 07:49:18 192.168.122.209 [56708.581091] [tdb] Close table 'sessions0.tdb' Apr 26 07:49:21 192.168.122.209 [56711.776513] [tdb] Close table 'cache0.tdb' Apr 26 07:49:21 192.168.122.209 [56712.032982] [tdb] Close table 'filter0.tdb' Apr 26 07:49:21 192.168.122.209 [56712.033388] [tempesta fw] modules are stopped Apr 26 07:49:21 192.168.122.209 [56712.215881] [tempesta fw] exiting... Apr 26 07:49:21 192.168.122.209 [56712.351732] [tdb] Shutdown Tempesta DB Apr 26 07:49:22 192.168.122.209 [56712.539064] End test: cache.test_h2_cache_control.TestH2CacheControl.test_authorization_in_first_request_s_maxage_in_response Apr 26 07:49:22 192.168.122.209 [56712.557766] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_authorization_in_second_request Apr 26 07:49:23 192.168.122.209 [56713.639413] [tdb] Start Tempesta DB Apr 26 07:49:23 192.168.122.209 [56713.784215] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:49:24 192.168.122.209 [56715.139780] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56715.139780] Maybe that's fine, but it's worth checking the [56715.139780] config - if there is no relations between the [56715.139780] names, then host name confusion attack is possible. Apr 26 07:49:24 192.168.122.209 [56715.258489] [tempesta fw] Configuration processing is completed. Apr 26 07:49:24 192.168.122.209 [56715.315616] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:49:25 192.168.122.209 [56715.745370] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:49:25 192.168.122.209 [56715.782174] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:49:25 192.168.122.209 [56715.809488] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:49:25 192.168.122.209 [56715.850453] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:49:25 192.168.122.209 [56715.852331] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:49:25 192.168.122.209 [56715.898413] [tempesta fw] Tempesta FW is ready Apr 26 07:49:26 192.168.122.209 [56716.543115] [tdb] Close table 'client0.tdb' Apr 26 07:49:26 192.168.122.209 [56716.719784] [tdb] Close table 'sessions0.tdb' Apr 26 07:49:29 192.168.122.209 [56719.940557] [tdb] Close table 'cache0.tdb' Apr 26 07:49:29 192.168.122.209 [56720.220164] [tdb] Close table 'filter0.tdb' Apr 26 07:49:29 192.168.122.209 [56720.220589] [tempesta fw] modules are stopped Apr 26 07:49:29 192.168.122.209 [56720.399977] [tempesta fw] exiting... Apr 26 07:49:29 192.168.122.209 [56720.504060] [tdb] Shutdown Tempesta DB Apr 26 07:49:30 192.168.122.209 [56720.746961] End test: cache.test_h2_cache_control.TestH2CacheControl.test_authorization_in_second_request Apr 26 07:49:30 192.168.122.209 [56720.765803] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_max_age_0_in_request Apr 26 07:49:31 192.168.122.209 [56721.829858] [tdb] Start Tempesta DB Apr 26 07:49:31 192.168.122.209 [56721.978592] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:49:32 192.168.122.209 [56723.379754] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56723.379754] Maybe that's fine, but it's worth checking the [56723.379754] config - if there is no relations between the [56723.379754] names, then host name confusion attack is possible. Apr 26 07:49:32 192.168.122.209 [56723.494592] [tempesta fw] Configuration processing is completed. Apr 26 07:49:33 192.168.122.209 [56723.554373] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:49:33 192.168.122.209 [56723.982628] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:49:33 192.168.122.209 [56724.009719] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:49:33 192.168.122.209 [56724.036765] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:49:33 192.168.122.209 [56724.078558] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:49:33 192.168.122.209 [56724.080331] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:49:33 192.168.122.209 [56724.122504] [tempesta fw] Tempesta FW is ready Apr 26 07:49:34 192.168.122.209 [56724.767090] [tdb] Close table 'client0.tdb' Apr 26 07:49:34 192.168.122.209 [56724.961933] [tdb] Close table 'sessions0.tdb' Apr 26 07:49:37 192.168.122.209 [56728.208050] [tdb] Close table 'cache0.tdb' Apr 26 07:49:37 192.168.122.209 [56728.446200] [tdb] Close table 'filter0.tdb' Apr 26 07:49:37 192.168.122.209 [56728.447051] [tempesta fw] modules are stopped Apr 26 07:49:38 192.168.122.209 [56728.649915] [tempesta fw] exiting... Apr 26 07:49:38 192.168.122.209 [56728.795020] [tdb] Shutdown Tempesta DB Apr 26 07:49:38 192.168.122.209 [56729.005768] End test: cache.test_h2_cache_control.TestH2CacheControl.test_max_age_0_in_request Apr 26 07:49:38 192.168.122.209 [56729.037023] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_max_age_0_in_response Apr 26 07:49:39 192.168.122.209 [56730.129923] [tdb] Start Tempesta DB Apr 26 07:49:39 192.168.122.209 [56730.263641] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:49:41 192.168.122.209 [56731.699918] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56731.699918] Maybe that's fine, but it's worth checking the [56731.699918] config - if there is no relations between the [56731.699918] names, then host name confusion attack is possible. Apr 26 07:49:41 192.168.122.209 [56731.838689] [tempesta fw] Configuration processing is completed. Apr 26 07:49:41 192.168.122.209 [56731.885280] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:49:41 192.168.122.209 [56732.306083] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:49:41 192.168.122.209 [56732.333118] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:49:41 192.168.122.209 [56732.360011] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:49:41 192.168.122.209 [56732.422664] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:49:41 192.168.122.209 [56732.424397] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:49:41 192.168.122.209 [56732.466638] [tempesta fw] Tempesta FW is ready Apr 26 07:49:42 192.168.122.209 [56733.103253] [tdb] Close table 'client0.tdb' Apr 26 07:49:42 192.168.122.209 [56733.314519] [tdb] Close table 'sessions0.tdb' Apr 26 07:49:45 192.168.122.209 [56736.518938] [tdb] Close table 'cache0.tdb' Apr 26 07:49:46 192.168.122.209 [56736.758124] [tdb] Close table 'filter0.tdb' Apr 26 07:49:46 192.168.122.209 [56736.758612] [tempesta fw] modules are stopped Apr 26 07:49:46 192.168.122.209 [56736.970612] [tempesta fw] exiting... Apr 26 07:49:46 192.168.122.209 [56737.084730] [tdb] Shutdown Tempesta DB Apr 26 07:49:46 192.168.122.209 [56737.293160] End test: cache.test_h2_cache_control.TestH2CacheControl.test_max_age_0_in_response Apr 26 07:49:46 192.168.122.209 [56737.321454] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_max_age_1_in_request_sleep_2 Apr 26 07:49:47 192.168.122.209 [56738.395036] [tdb] Start Tempesta DB Apr 26 07:49:48 192.168.122.209 [56738.532112] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:49:49 192.168.122.209 [56739.912071] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56739.912071] Maybe that's fine, but it's worth checking the [56739.912071] config - if there is no relations between the [56739.912071] names, then host name confusion attack is possible. Apr 26 07:49:49 192.168.122.209 [56740.030799] [tempesta fw] Configuration processing is completed. Apr 26 07:49:49 192.168.122.209 [56740.089567] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:49:49 192.168.122.209 [56740.518243] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:49:50 192.168.122.209 [56740.545005] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:49:50 192.168.122.209 [56740.571467] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:49:50 192.168.122.209 [56740.610704] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:49:50 192.168.122.209 [56740.611794] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:49:50 192.168.122.209 [56740.662715] [tempesta fw] Tempesta FW is ready Apr 26 07:49:52 192.168.122.209 [56743.348628] [tdb] Close table 'client0.tdb' Apr 26 07:49:52 192.168.122.209 [56743.514757] [tdb] Close table 'sessions0.tdb' Apr 26 07:49:56 192.168.122.209 [56746.754231] [tdb] Close table 'cache0.tdb' Apr 26 07:49:56 192.168.122.209 [56746.993721] [tdb] Close table 'filter0.tdb' Apr 26 07:49:56 192.168.122.209 [56746.994168] [tempesta fw] modules are stopped Apr 26 07:49:56 192.168.122.209 [56747.186251] [tempesta fw] exiting... Apr 26 07:49:56 192.168.122.209 [56747.316170] [tdb] Shutdown Tempesta DB Apr 26 07:49:57 192.168.122.209 [56747.547769] End test: cache.test_h2_cache_control.TestH2CacheControl.test_max_age_1_in_request_sleep_2 Apr 26 07:49:57 192.168.122.209 [56747.560775] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_max_age_1_in_request_sleep_2_from_hpack_dynamic_table Apr 26 07:49:58 192.168.122.209 [56748.620651] [tdb] Start Tempesta DB Apr 26 07:49:58 192.168.122.209 [56748.767360] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:49:59 192.168.122.209 [56750.151826] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56750.151826] Maybe that's fine, but it's worth checking the [56750.151826] config - if there is no relations between the [56750.151826] names, then host name confusion attack is possible. Apr 26 07:49:59 192.168.122.209 [56750.278982] [tempesta fw] Configuration processing is completed. Apr 26 07:49:59 192.168.122.209 [56750.330300] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:50:00 192.168.122.209 [56750.794687] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:50:00 192.168.122.209 [56750.830503] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:50:00 192.168.122.209 [56750.856580] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:50:00 192.168.122.209 [56750.898919] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:50:00 192.168.122.209 [56750.900654] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:50:00 192.168.122.209 [56750.942838] [tempesta fw] Tempesta FW is ready Apr 26 07:50:03 192.168.122.209 [56753.656921] [tdb] Close table 'client0.tdb' Apr 26 07:50:03 192.168.122.209 [56753.841933] [tdb] Close table 'sessions0.tdb' Apr 26 07:50:06 192.168.122.209 [56757.026708] [tdb] Close table 'cache0.tdb' Apr 26 07:50:06 192.168.122.209 [56757.275138] [tdb] Close table 'filter0.tdb' Apr 26 07:50:06 192.168.122.209 [56757.275578] [tempesta fw] modules are stopped Apr 26 07:50:06 192.168.122.209 [56757.487071] [tempesta fw] exiting... Apr 26 07:50:07 192.168.122.209 [56757.640999] [tdb] Shutdown Tempesta DB Apr 26 07:50:07 192.168.122.209 [56757.856356] End test: cache.test_h2_cache_control.TestH2CacheControl.test_max_age_1_in_request_sleep_2_from_hpack_dynamic_table Apr 26 07:50:07 192.168.122.209 [56757.868955] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_max_age_1_in_response_sleep_2 Apr 26 07:50:08 192.168.122.209 [56758.979215] [tdb] Start Tempesta DB Apr 26 07:50:08 192.168.122.209 [56759.124708] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:50:09 192.168.122.209 [56760.504300] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56760.504300] Maybe that's fine, but it's worth checking the [56760.504300] config - if there is no relations between the [56760.504300] names, then host name confusion attack is possible. Apr 26 07:50:10 192.168.122.209 [56760.619054] [tempesta fw] Configuration processing is completed. Apr 26 07:50:10 192.168.122.209 [56760.674368] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:50:10 192.168.122.209 [56761.100392] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:50:10 192.168.122.209 [56761.128172] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:50:10 192.168.122.209 [56761.163213] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:50:10 192.168.122.209 [56761.215046] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:50:10 192.168.122.209 [56761.216686] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:50:10 192.168.122.209 [56761.254970] [tempesta fw] Tempesta FW is ready Apr 26 07:50:13 192.168.122.209 [56763.930712] [tdb] Close table 'client0.tdb' Apr 26 07:50:13 192.168.122.209 [56764.128782] [tdb] Close table 'sessions0.tdb' Apr 26 07:50:16 192.168.122.209 [56767.324210] [tdb] Close table 'cache0.tdb' Apr 26 07:50:17 192.168.122.209 [56767.550493] [tdb] Close table 'filter0.tdb' Apr 26 07:50:17 192.168.122.209 [56767.550950] [tempesta fw] modules are stopped Apr 26 07:50:17 192.168.122.209 [56767.785766] [tempesta fw] exiting... Apr 26 07:50:17 192.168.122.209 [56767.934599] [tdb] Shutdown Tempesta DB Apr 26 07:50:17 192.168.122.209 [56768.158534] End test: cache.test_h2_cache_control.TestH2CacheControl.test_max_age_1_in_response_sleep_2 Apr 26 07:50:17 192.168.122.209 [56768.178523] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_max_age_2_in_request_sleep_0 Apr 26 07:50:18 192.168.122.209 [56769.239098] [tdb] Start Tempesta DB Apr 26 07:50:18 192.168.122.209 [56769.380322] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:50:20 192.168.122.209 [56770.816457] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56770.816457] Maybe that's fine, but it's worth checking the [56770.816457] config - if there is no relations between the [56770.816457] names, then host name confusion attack is possible. Apr 26 07:50:20 192.168.122.209 [56770.935238] [tempesta fw] Configuration processing is completed. Apr 26 07:50:20 192.168.122.209 [56770.986001] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:50:20 192.168.122.209 [56771.405255] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:50:20 192.168.122.209 [56771.432111] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:50:20 192.168.122.209 [56771.458658] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:50:21 192.168.122.209 [56771.527179] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:50:21 192.168.122.209 [56771.530284] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:50:21 192.168.122.209 [56771.571106] [tempesta fw] Tempesta FW is ready Apr 26 07:50:21 192.168.122.209 [56772.197930] [tdb] Close table 'client0.tdb' Apr 26 07:50:21 192.168.122.209 [56772.384977] [tdb] Close table 'sessions0.tdb' Apr 26 07:50:25 192.168.122.209 [56775.616111] [tdb] Close table 'cache0.tdb' Apr 26 07:50:25 192.168.122.209 [56775.848175] [tdb] Close table 'filter0.tdb' Apr 26 07:50:25 192.168.122.209 [56775.848618] [tempesta fw] modules are stopped Apr 26 07:50:25 192.168.122.209 [56776.052283] [tempesta fw] exiting... Apr 26 07:50:25 192.168.122.209 [56776.181354] [tdb] Shutdown Tempesta DB Apr 26 07:50:25 192.168.122.209 [56776.413779] End test: cache.test_h2_cache_control.TestH2CacheControl.test_max_age_2_in_request_sleep_0 Apr 26 07:50:25 192.168.122.209 [56776.429394] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_max_age_2_in_response_sleep_0 Apr 26 07:50:26 192.168.122.209 [56777.487563] [tdb] Start Tempesta DB Apr 26 07:50:27 192.168.122.209 [56777.630964] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:50:28 192.168.122.209 [56779.052508] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56779.052508] Maybe that's fine, but it's worth checking the [56779.052508] config - if there is no relations between the [56779.052508] names, then host name confusion attack is possible. Apr 26 07:50:28 192.168.122.209 [56779.171265] [tempesta fw] Configuration processing is completed. Apr 26 07:50:28 192.168.122.209 [56779.226549] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:50:29 192.168.122.209 [56779.685932] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:50:29 192.168.122.209 [56779.713895] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:50:29 192.168.122.209 [56779.741201] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:50:29 192.168.122.209 [56779.779254] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:50:29 192.168.122.209 [56779.780973] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:50:29 192.168.122.209 [56779.823186] [tempesta fw] Tempesta FW is ready Apr 26 07:50:29 192.168.122.209 [56780.495520] [tdb] Close table 'client0.tdb' Apr 26 07:50:30 192.168.122.209 [56780.664345] [tdb] Close table 'sessions0.tdb' Apr 26 07:50:33 192.168.122.209 [56783.915107] [tdb] Close table 'cache0.tdb' Apr 26 07:50:33 192.168.122.209 [56784.154680] [tdb] Close table 'filter0.tdb' Apr 26 07:50:33 192.168.122.209 [56784.155123] [tempesta fw] modules are stopped Apr 26 07:50:33 192.168.122.209 [56784.388744] [tempesta fw] exiting... Apr 26 07:50:34 192.168.122.209 [56784.532240] [tdb] Shutdown Tempesta DB Apr 26 07:50:34 192.168.122.209 [56784.779399] End test: cache.test_h2_cache_control.TestH2CacheControl.test_max_age_2_in_response_sleep_0 Apr 26 07:50:34 192.168.122.209 [56784.793159] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_max_stale_1_in_request_sleep_3 Apr 26 07:50:35 192.168.122.209 [56785.863907] [tdb] Start Tempesta DB Apr 26 07:50:35 192.168.122.209 [56786.022339] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:50:36 192.168.122.209 [56787.452610] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56787.452610] Maybe that's fine, but it's worth checking the [56787.452610] config - if there is no relations between the [56787.452610] names, then host name confusion attack is possible. Apr 26 07:50:37 192.168.122.209 [56787.583738] [tempesta fw] Configuration processing is completed. Apr 26 07:50:37 192.168.122.209 [56787.644776] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:50:37 192.168.122.209 [56788.065056] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:50:37 192.168.122.209 [56788.100921] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:50:37 192.168.122.209 [56788.129493] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:50:37 192.168.122.209 [56788.163365] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:50:37 192.168.122.209 [56788.165186] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:50:37 192.168.122.209 [56788.203303] [tempesta fw] Tempesta FW is ready Apr 26 07:50:41 192.168.122.209 [56791.859033] [tdb] Close table 'client0.tdb' Apr 26 07:50:41 192.168.122.209 [56792.050090] [tdb] Close table 'sessions0.tdb' Apr 26 07:50:44 192.168.122.209 [56795.305434] [tdb] Close table 'cache0.tdb' Apr 26 07:50:45 192.168.122.209 [56795.530091] [tdb] Close table 'filter0.tdb' Apr 26 07:50:45 192.168.122.209 [56795.530536] [tempesta fw] modules are stopped Apr 26 07:50:45 192.168.122.209 [56795.757857] [tempesta fw] exiting... Apr 26 07:50:45 192.168.122.209 [56795.893946] [tdb] Shutdown Tempesta DB Apr 26 07:50:45 192.168.122.209 [56796.131047] End test: cache.test_h2_cache_control.TestH2CacheControl.test_max_stale_1_in_request_sleep_3 Apr 26 07:50:45 192.168.122.209 [56796.148399] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_max_stale_5_in_request_sleep_2 Apr 26 07:50:46 192.168.122.209 [56797.197838] [tdb] Start Tempesta DB Apr 26 07:50:46 192.168.122.209 [56797.336659] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:50:48 192.168.122.209 [56798.788838] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56798.788838] Maybe that's fine, but it's worth checking the [56798.788838] config - if there is no relations between the [56798.788838] names, then host name confusion attack is possible. Apr 26 07:50:48 192.168.122.209 [56798.911546] [tempesta fw] Configuration processing is completed. Apr 26 07:50:48 192.168.122.209 [56798.967414] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:50:48 192.168.122.209 [56799.411580] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:50:48 192.168.122.209 [56799.439863] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:50:48 192.168.122.209 [56799.467812] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:50:49 192.168.122.209 [56799.523502] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:50:49 192.168.122.209 [56799.525243] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:50:49 192.168.122.209 [56799.571485] [tempesta fw] Tempesta FW is ready Apr 26 07:50:51 192.168.122.209 [56802.252209] [tdb] Close table 'client0.tdb' Apr 26 07:50:51 192.168.122.209 [56802.449914] [tdb] Close table 'sessions0.tdb' Apr 26 07:50:55 192.168.122.209 [56805.755854] [tdb] Close table 'cache0.tdb' Apr 26 07:50:55 192.168.122.209 [56805.974277] [tdb] Close table 'filter0.tdb' Apr 26 07:50:55 192.168.122.209 [56805.974701] [tempesta fw] modules are stopped Apr 26 07:50:55 192.168.122.209 [56806.196380] [tempesta fw] exiting... Apr 26 07:50:55 192.168.122.209 [56806.339490] [tdb] Shutdown Tempesta DB Apr 26 07:50:56 192.168.122.209 [56806.577529] End test: cache.test_h2_cache_control.TestH2CacheControl.test_max_stale_5_in_request_sleep_2 Apr 26 07:50:56 192.168.122.209 [56806.589755] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_max_stale_5_in_request_sleep_2_from_dynamic_table Apr 26 07:50:57 192.168.122.209 [56807.690004] [tdb] Start Tempesta DB Apr 26 07:50:57 192.168.122.209 [56807.841047] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:50:58 192.168.122.209 [56809.228896] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56809.228896] Maybe that's fine, but it's worth checking the [56809.228896] config - if there is no relations between the [56809.228896] names, then host name confusion attack is possible. Apr 26 07:50:58 192.168.122.209 [56809.347653] [tempesta fw] Configuration processing is completed. Apr 26 07:50:58 192.168.122.209 [56809.400328] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:50:59 192.168.122.209 [56809.864275] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:50:59 192.168.122.209 [56809.894340] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:50:59 192.168.122.209 [56809.924553] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:50:59 192.168.122.209 [56809.979635] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:50:59 192.168.122.209 [56809.981431] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:50:59 192.168.122.209 [56810.031575] [tempesta fw] Tempesta FW is ready Apr 26 07:51:02 192.168.122.209 [56812.716469] [tdb] Close table 'client0.tdb' Apr 26 07:51:02 192.168.122.209 [56812.907329] [tdb] Close table 'sessions0.tdb' Apr 26 07:51:05 192.168.122.209 [56816.186589] [tdb] Close table 'cache0.tdb' Apr 26 07:51:05 192.168.122.209 [56816.420894] [tdb] Close table 'filter0.tdb' Apr 26 07:51:05 192.168.122.209 [56816.421351] [tempesta fw] modules are stopped Apr 26 07:51:06 192.168.122.209 [56816.594172] [tempesta fw] exiting... Apr 26 07:51:06 192.168.122.209 [56816.715479] [tdb] Shutdown Tempesta DB Apr 26 07:51:06 192.168.122.209 [56816.923823] End test: cache.test_h2_cache_control.TestH2CacheControl.test_max_stale_5_in_request_sleep_2_from_dynamic_table Apr 26 07:51:06 192.168.122.209 [56816.939014] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_max_stale_in_request_sleep_2 Apr 26 07:51:07 192.168.122.209 [56818.008539] [tdb] Start Tempesta DB Apr 26 07:51:07 192.168.122.209 [56818.152839] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:51:08 192.168.122.209 [56819.485081] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56819.485081] Maybe that's fine, but it's worth checking the [56819.485081] config - if there is no relations between the [56819.485081] names, then host name confusion attack is possible. Apr 26 07:51:09 192.168.122.209 [56819.607801] [tempesta fw] Configuration processing is completed. Apr 26 07:51:09 192.168.122.209 [56819.675933] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:51:09 192.168.122.209 [56820.121715] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:51:09 192.168.122.209 [56820.159938] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:51:09 192.168.122.209 [56820.193390] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:51:09 192.168.122.209 [56820.243802] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:51:09 192.168.122.209 [56820.245534] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:51:09 192.168.122.209 [56820.283721] [tempesta fw] Tempesta FW is ready Apr 26 07:51:12 192.168.122.209 [56822.962722] [tdb] Close table 'client0.tdb' Apr 26 07:51:12 192.168.122.209 [56823.176323] [tdb] Close table 'sessions0.tdb' Apr 26 07:51:15 192.168.122.209 [56826.402938] [tdb] Close table 'cache0.tdb' Apr 26 07:51:16 192.168.122.209 [56826.639806] [tdb] Close table 'filter0.tdb' Apr 26 07:51:16 192.168.122.209 [56826.640255] [tempesta fw] modules are stopped Apr 26 07:51:16 192.168.122.209 [56826.831203] [tempesta fw] exiting... Apr 26 07:51:16 192.168.122.209 [56826.951569] [tdb] Shutdown Tempesta DB Apr 26 07:51:16 192.168.122.209 [56827.175289] End test: cache.test_h2_cache_control.TestH2CacheControl.test_max_stale_in_request_sleep_2 Apr 26 07:51:16 192.168.122.209 [56827.186252] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_min_fresh_1_in_request_sleep_0 Apr 26 07:51:17 192.168.122.209 [56828.310010] [tdb] Start Tempesta DB Apr 26 07:51:17 192.168.122.209 [56828.441854] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:51:19 192.168.122.209 [56829.853205] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56829.853205] Maybe that's fine, but it's worth checking the [56829.853205] config - if there is no relations between the [56829.853205] names, then host name confusion attack is possible. Apr 26 07:51:19 192.168.122.209 [56829.967900] [tempesta fw] Configuration processing is completed. Apr 26 07:51:19 192.168.122.209 [56830.023096] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:51:19 192.168.122.209 [56830.440093] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:51:19 192.168.122.209 [56830.466634] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:51:19 192.168.122.209 [56830.494234] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:51:20 192.168.122.209 [56830.543838] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:51:20 192.168.122.209 [56830.545608] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:51:20 192.168.122.209 [56830.587850] [tempesta fw] Tempesta FW is ready Apr 26 07:51:20 192.168.122.209 [56831.232629] [tdb] Close table 'client0.tdb' Apr 26 07:51:20 192.168.122.209 [56831.423777] [tdb] Close table 'sessions0.tdb' Apr 26 07:51:24 192.168.122.209 [56834.744640] [tdb] Close table 'cache0.tdb' Apr 26 07:51:24 192.168.122.209 [56834.997754] [tdb] Close table 'filter0.tdb' Apr 26 07:51:24 192.168.122.209 [56834.998184] [tempesta fw] modules are stopped Apr 26 07:51:24 192.168.122.209 [56835.199456] [tempesta fw] exiting... Apr 26 07:51:24 192.168.122.209 [56835.342205] [tdb] Shutdown Tempesta DB Apr 26 07:51:25 192.168.122.209 [56835.560782] End test: cache.test_h2_cache_control.TestH2CacheControl.test_min_fresh_1_in_request_sleep_0 Apr 26 07:51:25 192.168.122.209 [56835.589127] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_min_fresh_1_in_request_sleep_0_from_dynamic_table Apr 26 07:51:26 192.168.122.209 [56836.711443] [tdb] Start Tempesta DB Apr 26 07:51:26 192.168.122.209 [56836.851342] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:51:27 192.168.122.209 [56838.253254] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56838.253254] Maybe that's fine, but it's worth checking the [56838.253254] config - if there is no relations between the [56838.253254] names, then host name confusion attack is possible. Apr 26 07:51:27 192.168.122.209 [56838.368006] [tempesta fw] Configuration processing is completed. Apr 26 07:51:27 192.168.122.209 [56838.422228] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:51:28 192.168.122.209 [56838.963654] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:51:28 192.168.122.209 [56838.997783] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:51:28 192.168.122.209 [56839.031090] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:51:28 192.168.122.209 [56839.096000] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:51:28 192.168.122.209 [56839.097746] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:51:28 192.168.122.209 [56839.143954] [tempesta fw] Tempesta FW is ready Apr 26 07:51:29 192.168.122.209 [56839.780810] [tdb] Close table 'client0.tdb' Apr 26 07:51:29 192.168.122.209 [56839.997208] [tdb] Close table 'sessions0.tdb' Apr 26 07:51:32 192.168.122.209 [56843.287063] [tdb] Close table 'cache0.tdb' Apr 26 07:51:33 192.168.122.209 [56843.525644] [tdb] Close table 'filter0.tdb' Apr 26 07:51:33 192.168.122.209 [56843.526104] [tempesta fw] modules are stopped Apr 26 07:51:33 192.168.122.209 [56843.728044] [tempesta fw] exiting... Apr 26 07:51:33 192.168.122.209 [56843.823822] [tdb] Shutdown Tempesta DB Apr 26 07:51:33 192.168.122.209 [56844.039537] End test: cache.test_h2_cache_control.TestH2CacheControl.test_min_fresh_1_in_request_sleep_0_from_dynamic_table Apr 26 07:51:33 192.168.122.209 [56844.066522] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_min_fresh_2_in_request_sleep_2 Apr 26 07:51:34 192.168.122.209 [56845.117828] [tdb] Start Tempesta DB Apr 26 07:51:34 192.168.122.209 [56845.264927] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:51:36 192.168.122.209 [56846.681457] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56846.681457] Maybe that's fine, but it's worth checking the [56846.681457] config - if there is no relations between the [56846.681457] names, then host name confusion attack is possible. Apr 26 07:51:36 192.168.122.209 [56846.800080] [tempesta fw] Configuration processing is completed. Apr 26 07:51:36 192.168.122.209 [56846.853069] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:51:36 192.168.122.209 [56847.270319] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:51:36 192.168.122.209 [56847.297504] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:51:36 192.168.122.209 [56847.323737] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:51:36 192.168.122.209 [56847.372115] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:51:36 192.168.122.209 [56847.373854] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:51:36 192.168.122.209 [56847.420059] [tempesta fw] Tempesta FW is ready Apr 26 07:51:39 192.168.122.209 [56850.137297] [tdb] Close table 'client0.tdb' Apr 26 07:51:39 192.168.122.209 [56850.330350] [tdb] Close table 'sessions0.tdb' Apr 26 07:51:43 192.168.122.209 [56853.662925] [tdb] Close table 'cache0.tdb' Apr 26 07:51:43 192.168.122.209 [56853.921556] [tdb] Close table 'filter0.tdb' Apr 26 07:51:43 192.168.122.209 [56853.922019] [tempesta fw] modules are stopped Apr 26 07:51:43 192.168.122.209 [56854.101258] [tempesta fw] exiting... Apr 26 07:51:43 192.168.122.209 [56854.219613] [tdb] Shutdown Tempesta DB Apr 26 07:51:43 192.168.122.209 [56854.457417] End test: cache.test_h2_cache_control.TestH2CacheControl.test_min_fresh_2_in_request_sleep_2 Apr 26 07:51:43 192.168.122.209 [56854.476189] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_must_revalidate_in_response_from_cache Apr 26 07:51:44 192.168.122.209 [56855.481770] [tdb] Start Tempesta DB Apr 26 07:51:45 192.168.122.209 [56855.634160] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:51:46 192.168.122.209 [56857.173558] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56857.173558] Maybe that's fine, but it's worth checking the [56857.173558] config - if there is no relations between the [56857.173558] names, then host name confusion attack is possible. Apr 26 07:51:46 192.168.122.209 [56857.304273] [tempesta fw] Configuration processing is completed. Apr 26 07:51:46 192.168.122.209 [56857.360869] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:51:47 192.168.122.209 [56857.788246] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:51:47 192.168.122.209 [56857.816576] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:51:47 192.168.122.209 [56857.844415] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:51:47 192.168.122.209 [56857.884243] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:51:47 192.168.122.209 [56857.886008] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:51:47 192.168.122.209 [56857.920193] [tempesta fw] Tempesta FW is ready Apr 26 07:51:48 192.168.122.209 [56858.589457] [tdb] Close table 'client0.tdb' Apr 26 07:51:48 192.168.122.209 [56858.775774] [tdb] Close table 'sessions0.tdb' Apr 26 07:51:51 192.168.122.209 [56861.993231] [tdb] Close table 'cache0.tdb' Apr 26 07:51:51 192.168.122.209 [56862.254595] [tdb] Close table 'filter0.tdb' Apr 26 07:51:51 192.168.122.209 [56862.255016] [tempesta fw] modules are stopped Apr 26 07:51:51 192.168.122.209 [56862.446825] [tempesta fw] exiting... Apr 26 07:51:52 192.168.122.209 [56862.573756] [tdb] Shutdown Tempesta DB Apr 26 07:51:52 192.168.122.209 [56862.783265] End test: cache.test_h2_cache_control.TestH2CacheControl.test_must_revalidate_in_response_from_cache Apr 26 07:51:52 192.168.122.209 [56862.810484] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_must_revalidate_in_response_max_stale_in_request_from_cache Apr 26 07:51:53 192.168.122.209 [56863.890289] [tdb] Start Tempesta DB Apr 26 07:51:53 192.168.122.209 [56864.025906] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:51:54 192.168.122.209 [56865.413589] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56865.413589] Maybe that's fine, but it's worth checking the [56865.413589] config - if there is no relations between the [56865.413589] names, then host name confusion attack is possible. Apr 26 07:51:55 192.168.122.209 [56865.532432] [tempesta fw] Configuration processing is completed. Apr 26 07:51:55 192.168.122.209 [56865.581040] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:51:55 192.168.122.209 [56866.002460] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:51:55 192.168.122.209 [56866.029465] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:51:55 192.168.122.209 [56866.055545] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:51:55 192.168.122.209 [56866.124348] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:51:55 192.168.122.209 [56866.126093] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:51:55 192.168.122.209 [56866.172296] [tempesta fw] Tempesta FW is ready Apr 26 07:51:56 192.168.122.209 [56866.793007] [tdb] Close table 'client0.tdb' Apr 26 07:51:56 192.168.122.209 [56866.978188] [tdb] Close table 'sessions0.tdb' Apr 26 07:51:59 192.168.122.209 [56870.192125] [tdb] Close table 'cache0.tdb' Apr 26 07:51:59 192.168.122.209 [56870.427135] [tdb] Close table 'filter0.tdb' Apr 26 07:51:59 192.168.122.209 [56870.427578] [tempesta fw] modules are stopped Apr 26 07:52:00 192.168.122.209 [56870.636475] [tempesta fw] exiting... Apr 26 07:52:00 192.168.122.209 [56870.787100] [tdb] Shutdown Tempesta DB Apr 26 07:52:00 192.168.122.209 [56871.014836] End test: cache.test_h2_cache_control.TestH2CacheControl.test_must_revalidate_in_response_max_stale_in_request_from_cache Apr 26 07:52:00 192.168.122.209 [56871.044329] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_must_revalidate_in_response_max_stale_in_request_not_from_cache Apr 26 07:52:01 192.168.122.209 [56872.181999] [tdb] Start Tempesta DB Apr 26 07:52:01 192.168.122.209 [56872.315990] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:52:03 192.168.122.209 [56873.737487] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56873.737487] Maybe that's fine, but it's worth checking the [56873.737487] config - if there is no relations between the [56873.737487] names, then host name confusion attack is possible. Apr 26 07:52:03 192.168.122.209 [56873.848394] [tempesta fw] Configuration processing is completed. Apr 26 07:52:03 192.168.122.209 [56873.898439] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:52:03 192.168.122.209 [56874.320988] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:52:03 192.168.122.209 [56874.347191] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:52:03 192.168.122.209 [56874.373774] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:52:03 192.168.122.209 [56874.416475] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:52:03 192.168.122.209 [56874.418220] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:52:03 192.168.122.209 [56874.460386] [tempesta fw] Tempesta FW is ready Apr 26 07:52:06 192.168.122.209 [56877.126062] [tdb] Close table 'client0.tdb' Apr 26 07:52:06 192.168.122.209 [56877.315465] [tdb] Close table 'sessions0.tdb' Apr 26 07:52:10 192.168.122.209 [56880.523585] [tdb] Close table 'cache0.tdb' Apr 26 07:52:10 192.168.122.209 [56880.762246] [tdb] Close table 'filter0.tdb' Apr 26 07:52:10 192.168.122.209 [56880.762677] [tempesta fw] modules are stopped Apr 26 07:52:10 192.168.122.209 [56880.938237] [tempesta fw] exiting... Apr 26 07:52:10 192.168.122.209 [56881.045711] [tdb] Shutdown Tempesta DB Apr 26 07:52:10 192.168.122.209 [56881.257004] End test: cache.test_h2_cache_control.TestH2CacheControl.test_must_revalidate_in_response_max_stale_in_request_not_from_cache Apr 26 07:52:10 192.168.122.209 [56881.274313] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_must_revalidate_in_response_not_from_cache Apr 26 07:52:11 192.168.122.209 [56882.325123] [tdb] Start Tempesta DB Apr 26 07:52:11 192.168.122.209 [56882.456688] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:52:13 192.168.122.209 [56883.853807] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56883.853807] Maybe that's fine, but it's worth checking the [56883.853807] config - if there is no relations between the [56883.853807] names, then host name confusion attack is possible. Apr 26 07:52:13 192.168.122.209 [56883.968595] [tempesta fw] Configuration processing is completed. Apr 26 07:52:13 192.168.122.209 [56884.023137] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:52:13 192.168.122.209 [56884.436357] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:52:13 192.168.122.209 [56884.462747] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:52:13 192.168.122.209 [56884.488507] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:52:14 192.168.122.209 [56884.552480] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:52:14 192.168.122.209 [56884.554208] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:52:14 192.168.122.209 [56884.600529] [tempesta fw] Tempesta FW is ready Apr 26 07:52:16 192.168.122.209 [56887.261564] [tdb] Close table 'client0.tdb' Apr 26 07:52:16 192.168.122.209 [56887.438810] [tdb] Close table 'sessions0.tdb' Apr 26 07:52:20 192.168.122.209 [56890.657298] [tdb] Close table 'cache0.tdb' Apr 26 07:52:20 192.168.122.209 [56890.912609] [tdb] Close table 'filter0.tdb' Apr 26 07:52:20 192.168.122.209 [56890.913043] [tempesta fw] modules are stopped Apr 26 07:52:20 192.168.122.209 [56891.124579] [tempesta fw] exiting... Apr 26 07:52:20 192.168.122.209 [56891.263893] [tdb] Shutdown Tempesta DB Apr 26 07:52:20 192.168.122.209 [56891.484206] End test: cache.test_h2_cache_control.TestH2CacheControl.test_must_revalidate_in_response_not_from_cache Apr 26 07:52:20 192.168.122.209 [56891.496493] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_no_cache_in_first_request Apr 26 07:52:22 192.168.122.209 [56892.547701] [tdb] Start Tempesta DB Apr 26 07:52:22 192.168.122.209 [56892.686343] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:52:23 192.168.122.209 [56894.113985] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56894.113985] Maybe that's fine, but it's worth checking the [56894.113985] config - if there is no relations between the [56894.113985] names, then host name confusion attack is possible. Apr 26 07:52:23 192.168.122.209 [56894.232725] [tempesta fw] Configuration processing is completed. Apr 26 07:52:23 192.168.122.209 [56894.283709] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:52:24 192.168.122.209 [56894.712751] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:52:24 192.168.122.209 [56894.742942] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:52:24 192.168.122.209 [56894.768939] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:52:24 192.168.122.209 [56894.808651] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:52:24 192.168.122.209 [56894.809812] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:52:24 192.168.122.209 [56894.852645] [tempesta fw] Tempesta FW is ready Apr 26 07:52:24 192.168.122.209 [56895.505920] [tdb] Close table 'client0.tdb' Apr 26 07:52:25 192.168.122.209 [56895.692293] [tdb] Close table 'sessions0.tdb' Apr 26 07:52:28 192.168.122.209 [56898.864035] [tdb] Close table 'cache0.tdb' Apr 26 07:52:28 192.168.122.209 [56899.082629] [tdb] Close table 'filter0.tdb' Apr 26 07:52:28 192.168.122.209 [56899.083054] [tempesta fw] modules are stopped Apr 26 07:52:28 192.168.122.209 [56899.280987] [tempesta fw] exiting... Apr 26 07:52:28 192.168.122.209 [56899.409195] [tdb] Shutdown Tempesta DB Apr 26 07:52:29 192.168.122.209 [56899.644145] End test: cache.test_h2_cache_control.TestH2CacheControl.test_no_cache_in_first_request Apr 26 07:52:29 192.168.122.209 [56899.658824] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_no_cache_in_response Apr 26 07:52:30 192.168.122.209 [56900.789049] [tdb] Start Tempesta DB Apr 26 07:52:30 192.168.122.209 [56900.935665] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:52:31 192.168.122.209 [56902.398054] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56902.398054] Maybe that's fine, but it's worth checking the [56902.398054] config - if there is no relations between the [56902.398054] names, then host name confusion attack is possible. Apr 26 07:52:31 192.168.122.209 [56902.512805] [tempesta fw] Configuration processing is completed. Apr 26 07:52:32 192.168.122.209 [56902.565641] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:52:32 192.168.122.209 [56903.004487] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:52:32 192.168.122.209 [56903.031162] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:52:32 192.168.122.209 [56903.057537] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:52:32 192.168.122.209 [56903.100796] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:52:32 192.168.122.209 [56903.102548] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:52:32 192.168.122.209 [56903.168757] [tempesta fw] Tempesta FW is ready Apr 26 07:52:33 192.168.122.209 [56903.818348] [tdb] Close table 'client0.tdb' Apr 26 07:52:33 192.168.122.209 [56904.014412] [tdb] Close table 'sessions0.tdb' Apr 26 07:52:36 192.168.122.209 [56907.326733] [tdb] Close table 'cache0.tdb' Apr 26 07:52:37 192.168.122.209 [56907.566648] [tdb] Close table 'filter0.tdb' Apr 26 07:52:37 192.168.122.209 [56907.567246] [tempesta fw] modules are stopped Apr 26 07:52:37 192.168.122.209 [56907.800495] [tempesta fw] exiting... Apr 26 07:52:37 192.168.122.209 [56907.943202] [tdb] Shutdown Tempesta DB Apr 26 07:52:37 192.168.122.209 [56908.149406] End test: cache.test_h2_cache_control.TestH2CacheControl.test_no_cache_in_response Apr 26 07:52:37 192.168.122.209 [56908.177443] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_no_cache_in_second_request Apr 26 07:52:38 192.168.122.209 [56909.235609] [tdb] Start Tempesta DB Apr 26 07:52:38 192.168.122.209 [56909.371613] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:52:40 192.168.122.209 [56910.774152] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56910.774152] Maybe that's fine, but it's worth checking the [56910.774152] config - if there is no relations between the [56910.774152] names, then host name confusion attack is possible. Apr 26 07:52:40 192.168.122.209 [56910.892911] [tempesta fw] Configuration processing is completed. Apr 26 07:52:40 192.168.122.209 [56910.949602] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:52:40 192.168.122.209 [56911.389405] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:52:40 192.168.122.209 [56911.416267] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:52:40 192.168.122.209 [56911.443120] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:52:40 192.168.122.209 [56911.484868] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:52:40 192.168.122.209 [56911.486055] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:52:41 192.168.122.209 [56911.524864] [tempesta fw] Tempesta FW is ready Apr 26 07:52:41 192.168.122.209 [56912.231147] [tdb] Close table 'client0.tdb' Apr 26 07:52:41 192.168.122.209 [56912.420493] [tdb] Close table 'sessions0.tdb' Apr 26 07:52:45 192.168.122.209 [56915.626121] [tdb] Close table 'cache0.tdb' Apr 26 07:52:45 192.168.122.209 [56915.873359] [tdb] Close table 'filter0.tdb' Apr 26 07:52:45 192.168.122.209 [56915.873798] [tempesta fw] modules are stopped Apr 26 07:52:45 192.168.122.209 [56916.050546] [tempesta fw] exiting... Apr 26 07:52:45 192.168.122.209 [56916.180605] [tdb] Shutdown Tempesta DB Apr 26 07:52:45 192.168.122.209 [56916.410242] End test: cache.test_h2_cache_control.TestH2CacheControl.test_no_cache_in_second_request Apr 26 07:52:45 192.168.122.209 [56916.429639] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_no_store_in_first_and_second_request_from_dynamic_table Apr 26 07:52:46 192.168.122.209 [56917.452026] [tdb] Start Tempesta DB Apr 26 07:52:47 192.168.122.209 [56917.598445] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:52:48 192.168.122.209 [56918.990185] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56918.990185] Maybe that's fine, but it's worth checking the [56918.990185] config - if there is no relations between the [56918.990185] names, then host name confusion attack is possible. Apr 26 07:52:48 192.168.122.209 [56919.136976] [tempesta fw] Configuration processing is completed. Apr 26 07:52:48 192.168.122.209 [56919.181503] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:52:49 192.168.122.209 [56919.598389] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:52:49 192.168.122.209 [56919.637973] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:52:49 192.168.122.209 [56919.664659] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:52:49 192.168.122.209 [56919.725009] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:52:49 192.168.122.209 [56919.726761] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:52:49 192.168.122.209 [56919.772985] [tempesta fw] Tempesta FW is ready Apr 26 07:52:49 192.168.122.209 [56920.432420] [tdb] Close table 'client0.tdb' Apr 26 07:52:50 192.168.122.209 [56920.628305] [tdb] Close table 'sessions0.tdb' Apr 26 07:52:53 192.168.122.209 [56923.834612] [tdb] Close table 'cache0.tdb' Apr 26 07:52:53 192.168.122.209 [56924.049343] [tdb] Close table 'filter0.tdb' Apr 26 07:52:53 192.168.122.209 [56924.049795] [tempesta fw] modules are stopped Apr 26 07:52:53 192.168.122.209 [56924.250548] [tempesta fw] exiting... Apr 26 07:52:53 192.168.122.209 [56924.388199] [tdb] Shutdown Tempesta DB Apr 26 07:52:54 192.168.122.209 [56924.597594] End test: cache.test_h2_cache_control.TestH2CacheControl.test_no_store_in_first_and_second_request_from_dynamic_table Apr 26 07:52:54 192.168.122.209 [56924.621361] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_no_store_in_first_request Apr 26 07:52:55 192.168.122.209 [56925.564916] [tdb] Start Tempesta DB Apr 26 07:52:55 192.168.122.209 [56925.729798] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:52:57 192.168.122.209 [56928.042688] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56928.042688] Maybe that's fine, but it's worth checking the [56928.042688] config - if there is no relations between the [56928.042688] names, then host name confusion attack is possible. Apr 26 07:52:58 192.168.122.209 [56928.857261] [tempesta fw] Configuration processing is completed. Apr 26 07:52:58 192.168.122.209 [56929.018203] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:52:58 192.168.122.209 [56929.464688] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:52:58 192.168.122.209 [56929.493427] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:52:59 192.168.122.209 [56929.522891] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:52:59 192.168.122.209 [56930.049208] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:52:59 192.168.122.209 [56930.051003] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:52:59 192.168.122.209 [56930.421133] [tempesta fw] Tempesta FW is ready Apr 26 07:53:01 192.168.122.209 [56931.599934] [tdb] Close table 'client0.tdb' Apr 26 07:53:01 192.168.122.209 [56931.828071] [tdb] Close table 'sessions0.tdb' Apr 26 07:53:04 192.168.122.209 [56935.093320] [tdb] Close table 'cache0.tdb' Apr 26 07:53:04 192.168.122.209 [56935.336558] [tdb] Close table 'filter0.tdb' Apr 26 07:53:04 192.168.122.209 [56935.337055] [tempesta fw] modules are stopped Apr 26 07:53:05 192.168.122.209 [56935.536696] [tempesta fw] exiting... Apr 26 07:53:05 192.168.122.209 [56935.654913] [tdb] Shutdown Tempesta DB Apr 26 07:53:05 192.168.122.209 [56935.867393] End test: cache.test_h2_cache_control.TestH2CacheControl.test_no_store_in_first_request Apr 26 07:53:05 192.168.122.209 [56935.884373] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_no_store_in_response Apr 26 07:53:06 192.168.122.209 [56936.977232] [tdb] Start Tempesta DB Apr 26 07:53:06 192.168.122.209 [56937.118518] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:53:07 192.168.122.209 [56938.406494] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56938.406494] Maybe that's fine, but it's worth checking the [56938.406494] config - if there is no relations between the [56938.406494] names, then host name confusion attack is possible. Apr 26 07:53:08 192.168.122.209 [56938.529168] [tempesta fw] Configuration processing is completed. Apr 26 07:53:08 192.168.122.209 [56938.591012] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:53:08 192.168.122.209 [56939.006945] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:53:08 192.168.122.209 [56939.035868] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:53:08 192.168.122.209 [56939.062256] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:53:08 192.168.122.209 [56939.101194] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:53:08 192.168.122.209 [56939.102235] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:53:08 192.168.122.209 [56939.145195] [tempesta fw] Tempesta FW is ready Apr 26 07:53:09 192.168.122.209 [56939.808031] [tdb] Close table 'client0.tdb' Apr 26 07:53:09 192.168.122.209 [56939.993024] [tdb] Close table 'sessions0.tdb' Apr 26 07:53:12 192.168.122.209 [56943.218710] [tdb] Close table 'cache0.tdb' Apr 26 07:53:12 192.168.122.209 [56943.460437] [tdb] Close table 'filter0.tdb' Apr 26 07:53:12 192.168.122.209 [56943.460871] [tempesta fw] modules are stopped Apr 26 07:53:13 192.168.122.209 [56943.652126] [tempesta fw] exiting... Apr 26 07:53:13 192.168.122.209 [56943.798351] [tdb] Shutdown Tempesta DB Apr 26 07:53:13 192.168.122.209 [56944.022574] End test: cache.test_h2_cache_control.TestH2CacheControl.test_no_store_in_response Apr 26 07:53:13 192.168.122.209 [56944.033028] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_no_store_in_second_request Apr 26 07:53:14 192.168.122.209 [56945.133076] [tdb] Start Tempesta DB Apr 26 07:53:14 192.168.122.209 [56945.271938] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:53:16 192.168.122.209 [56946.638694] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56946.638694] Maybe that's fine, but it's worth checking the [56946.638694] config - if there is no relations between the [56946.638694] names, then host name confusion attack is possible. Apr 26 07:53:16 192.168.122.209 [56946.773369] [tempesta fw] Configuration processing is completed. Apr 26 07:53:16 192.168.122.209 [56946.826722] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:53:16 192.168.122.209 [56947.247258] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:53:16 192.168.122.209 [56947.274969] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:53:16 192.168.122.209 [56947.301286] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:53:16 192.168.122.209 [56947.349326] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:53:16 192.168.122.209 [56947.350787] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:53:16 192.168.122.209 [56947.397303] [tempesta fw] Tempesta FW is ready Apr 26 07:53:17 192.168.122.209 [56948.057820] [tdb] Close table 'client0.tdb' Apr 26 07:53:17 192.168.122.209 [56948.243738] [tdb] Close table 'sessions0.tdb' Apr 26 07:53:20 192.168.122.209 [56951.433784] [tdb] Close table 'cache0.tdb' Apr 26 07:53:21 192.168.122.209 [56951.678588] [tdb] Close table 'filter0.tdb' Apr 26 07:53:21 192.168.122.209 [56951.679030] [tempesta fw] modules are stopped Apr 26 07:53:21 192.168.122.209 [56951.851395] [tempesta fw] exiting... Apr 26 07:53:21 192.168.122.209 [56951.970118] [tdb] Shutdown Tempesta DB Apr 26 07:53:21 192.168.122.209 [56952.233862] End test: cache.test_h2_cache_control.TestH2CacheControl.test_no_store_in_second_request Apr 26 07:53:21 192.168.122.209 [56952.244860] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_only_if_cached_in_request_from_cache Apr 26 07:53:22 192.168.122.209 [56953.298338] [tdb] Start Tempesta DB Apr 26 07:53:22 192.168.122.209 [56953.439758] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:53:24 192.168.122.209 [56954.918734] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56954.918734] Maybe that's fine, but it's worth checking the [56954.918734] config - if there is no relations between the [56954.918734] names, then host name confusion attack is possible. Apr 26 07:53:24 192.168.122.209 [56955.033483] [tempesta fw] Configuration processing is completed. Apr 26 07:53:24 192.168.122.209 [56955.085345] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:53:24 192.168.122.209 [56955.501684] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:53:25 192.168.122.209 [56955.528607] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:53:25 192.168.122.209 [56955.555629] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:53:25 192.168.122.209 [56955.617458] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:53:25 192.168.122.209 [56955.619172] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:53:25 192.168.122.209 [56955.665408] [tempesta fw] Tempesta FW is ready Apr 26 07:53:25 192.168.122.209 [56956.315400] [tdb] Close table 'client0.tdb' Apr 26 07:53:25 192.168.122.209 [56956.503900] [tdb] Close table 'sessions0.tdb' Apr 26 07:53:29 192.168.122.209 [56959.682615] [tdb] Close table 'cache0.tdb' Apr 26 07:53:29 192.168.122.209 [56959.918329] [tdb] Close table 'filter0.tdb' Apr 26 07:53:29 192.168.122.209 [56959.918761] [tempesta fw] modules are stopped Apr 26 07:53:29 192.168.122.209 [56960.114515] [tempesta fw] exiting... Apr 26 07:53:29 192.168.122.209 [56960.238971] [tdb] Shutdown Tempesta DB Apr 26 07:53:29 192.168.122.209 [56960.441667] End test: cache.test_h2_cache_control.TestH2CacheControl.test_only_if_cached_in_request_from_cache Apr 26 07:53:29 192.168.122.209 [56960.471303] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_only_if_cached_in_request_from_cache_from_dynamic_table Apr 26 07:53:31 192.168.122.209 [56961.535470] [tdb] Start Tempesta DB Apr 26 07:53:31 192.168.122.209 [56961.687182] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:53:32 192.168.122.209 [56963.214804] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56963.214804] Maybe that's fine, but it's worth checking the [56963.214804] config - if there is no relations between the [56963.214804] names, then host name confusion attack is possible. Apr 26 07:53:32 192.168.122.209 [56963.329587] [tempesta fw] Configuration processing is completed. Apr 26 07:53:32 192.168.122.209 [56963.381296] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:53:33 192.168.122.209 [56963.808165] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:53:33 192.168.122.209 [56963.834582] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:53:33 192.168.122.209 [56963.861063] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:53:33 192.168.122.209 [56963.909578] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:53:33 192.168.122.209 [56963.911295] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:53:33 192.168.122.209 [56963.957436] [tempesta fw] Tempesta FW is ready Apr 26 07:53:34 192.168.122.209 [56964.598945] [tdb] Close table 'client0.tdb' Apr 26 07:53:34 192.168.122.209 [56964.784666] [tdb] Close table 'sessions0.tdb' Apr 26 07:53:37 192.168.122.209 [56967.966044] [tdb] Close table 'cache0.tdb' Apr 26 07:53:37 192.168.122.209 [56968.188336] [tdb] Close table 'filter0.tdb' Apr 26 07:53:37 192.168.122.209 [56968.188784] [tempesta fw] modules are stopped Apr 26 07:53:37 192.168.122.209 [56968.458199] [tempesta fw] exiting... Apr 26 07:53:38 192.168.122.209 [56968.574194] [tdb] Shutdown Tempesta DB Apr 26 07:53:38 192.168.122.209 [56968.801143] End test: cache.test_h2_cache_control.TestH2CacheControl.test_only_if_cached_in_request_from_cache_from_dynamic_table Apr 26 07:53:38 192.168.122.209 [56968.822479] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_only_if_cached_in_request_not_from_cache Apr 26 07:53:39 192.168.122.209 [56969.839138] [tdb] Start Tempesta DB Apr 26 07:53:39 192.168.122.209 [56969.975132] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:53:40 192.168.122.209 [56971.390921] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56971.390921] Maybe that's fine, but it's worth checking the [56971.390921] config - if there is no relations between the [56971.390921] names, then host name confusion attack is possible. Apr 26 07:53:40 192.168.122.209 [56971.505679] [tempesta fw] Configuration processing is completed. Apr 26 07:53:41 192.168.122.209 [56971.557709] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:53:41 192.168.122.209 [56971.972919] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:53:41 192.168.122.209 [56971.999024] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:53:41 192.168.122.209 [56972.025413] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:53:41 192.168.122.209 [56972.069666] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:53:41 192.168.122.209 [56972.071379] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:53:41 192.168.122.209 [56972.129621] [tempesta fw] Tempesta FW is ready Apr 26 07:53:43 192.168.122.209 [56974.368606] [tempesta fw] Warning: resource not cached, status 504: 127.0.0.2 Apr 26 07:53:44 192.168.122.209 [56974.796746] [tdb] Close table 'client0.tdb' Apr 26 07:53:44 192.168.122.209 [56974.989192] [tdb] Close table 'sessions0.tdb' Apr 26 07:53:47 192.168.122.209 [56978.213453] [tdb] Close table 'cache0.tdb' Apr 26 07:53:47 192.168.122.209 [56978.462401] [tdb] Close table 'filter0.tdb' Apr 26 07:53:47 192.168.122.209 [56978.462833] [tempesta fw] modules are stopped Apr 26 07:53:48 192.168.122.209 [56978.665892] [tempesta fw] exiting... Apr 26 07:53:48 192.168.122.209 [56978.791829] [tdb] Shutdown Tempesta DB Apr 26 07:53:48 192.168.122.209 [56979.013259] End test: cache.test_h2_cache_control.TestH2CacheControl.test_only_if_cached_in_request_not_from_cache Apr 26 07:53:48 192.168.122.209 [56979.028522] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_private_in_response Apr 26 07:53:49 192.168.122.209 [56980.040759] [tdb] Start Tempesta DB Apr 26 07:53:49 192.168.122.209 [56980.171778] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:53:51 192.168.122.209 [56981.575089] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56981.575089] Maybe that's fine, but it's worth checking the [56981.575089] config - if there is no relations between the [56981.575089] names, then host name confusion attack is possible. Apr 26 07:53:51 192.168.122.209 [56981.689823] [tempesta fw] Configuration processing is completed. Apr 26 07:53:51 192.168.122.209 [56981.743092] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:53:51 192.168.122.209 [56982.176168] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:53:51 192.168.122.209 [56982.212663] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:53:51 192.168.122.209 [56982.240021] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:53:51 192.168.122.209 [56982.281790] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:53:51 192.168.122.209 [56982.283521] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:53:51 192.168.122.209 [56982.333756] [tempesta fw] Tempesta FW is ready Apr 26 07:53:52 192.168.122.209 [56983.009756] [tdb] Close table 'client0.tdb' Apr 26 07:53:52 192.168.122.209 [56983.191196] [tdb] Close table 'sessions0.tdb' Apr 26 07:53:55 192.168.122.209 [56986.415206] [tdb] Close table 'cache0.tdb' Apr 26 07:53:56 192.168.122.209 [56986.659039] [tdb] Close table 'filter0.tdb' Apr 26 07:53:56 192.168.122.209 [56986.659474] [tempesta fw] modules are stopped Apr 26 07:53:56 192.168.122.209 [56986.862632] [tempesta fw] exiting... Apr 26 07:53:56 192.168.122.209 [56987.009782] [tdb] Shutdown Tempesta DB Apr 26 07:53:56 192.168.122.209 [56987.248804] End test: cache.test_h2_cache_control.TestH2CacheControl.test_private_in_response Apr 26 07:53:56 192.168.122.209 [56987.269349] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_proxy_revalidate_in_response_from_cache Apr 26 07:53:57 192.168.122.209 [56988.326055] [tdb] Start Tempesta DB Apr 26 07:53:57 192.168.122.209 [56988.478076] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:53:59 192.168.122.209 [56989.935161] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56989.935161] Maybe that's fine, but it's worth checking the [56989.935161] config - if there is no relations between the [56989.935161] names, then host name confusion attack is possible. Apr 26 07:53:59 192.168.122.209 [56990.053938] [tempesta fw] Configuration processing is completed. Apr 26 07:53:59 192.168.122.209 [56990.111016] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:54:00 192.168.122.209 [56990.531552] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:54:00 192.168.122.209 [56990.558229] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:54:00 192.168.122.209 [56990.585828] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:54:00 192.168.122.209 [56990.633813] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:54:00 192.168.122.209 [56990.635549] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:54:00 192.168.122.209 [56990.681854] [tempesta fw] Tempesta FW is ready Apr 26 07:54:00 192.168.122.209 [56991.311276] [tdb] Close table 'client0.tdb' Apr 26 07:54:00 192.168.122.209 [56991.515860] [tdb] Close table 'sessions0.tdb' Apr 26 07:54:04 192.168.122.209 [56994.696348] [tdb] Close table 'cache0.tdb' Apr 26 07:54:04 192.168.122.209 [56994.921558] [tdb] Close table 'filter0.tdb' Apr 26 07:54:04 192.168.122.209 [56994.922024] [tempesta fw] modules are stopped Apr 26 07:54:04 192.168.122.209 [56995.127671] [tempesta fw] exiting... Apr 26 07:54:04 192.168.122.209 [56995.249488] [tdb] Shutdown Tempesta DB Apr 26 07:54:04 192.168.122.209 [56995.484566] End test: cache.test_h2_cache_control.TestH2CacheControl.test_proxy_revalidate_in_response_from_cache Apr 26 07:54:04 192.168.122.209 [56995.507209] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_proxy_revalidate_in_response_max_stale_in_request_from_cache Apr 26 07:54:06 192.168.122.209 [56996.570020] [tdb] Start Tempesta DB Apr 26 07:54:06 192.168.122.209 [56996.702589] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:54:07 192.168.122.209 [56998.183209] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [56998.183209] Maybe that's fine, but it's worth checking the [56998.183209] config - if there is no relations between the [56998.183209] names, then host name confusion attack is possible. Apr 26 07:54:07 192.168.122.209 [56998.302020] [tempesta fw] Configuration processing is completed. Apr 26 07:54:07 192.168.122.209 [56998.353412] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:54:08 192.168.122.209 [56998.779291] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:54:08 192.168.122.209 [56998.811296] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:54:08 192.168.122.209 [56998.837966] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:54:08 192.168.122.209 [56998.877950] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:54:08 192.168.122.209 [56998.879062] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:54:08 192.168.122.209 [56998.917960] [tempesta fw] Tempesta FW is ready Apr 26 07:54:09 192.168.122.209 [56999.574206] [tdb] Close table 'client0.tdb' Apr 26 07:54:09 192.168.122.209 [56999.788778] [tdb] Close table 'sessions0.tdb' Apr 26 07:54:12 192.168.122.209 [57002.979082] [tdb] Close table 'cache0.tdb' Apr 26 07:54:12 192.168.122.209 [57003.229381] [tdb] Close table 'filter0.tdb' Apr 26 07:54:12 192.168.122.209 [57003.229824] [tempesta fw] modules are stopped Apr 26 07:54:12 192.168.122.209 [57003.447736] [tempesta fw] exiting... Apr 26 07:54:13 192.168.122.209 [57003.602116] [tdb] Shutdown Tempesta DB Apr 26 07:54:13 192.168.122.209 [57003.854693] End test: cache.test_h2_cache_control.TestH2CacheControl.test_proxy_revalidate_in_response_max_stale_in_request_from_cache Apr 26 07:54:13 192.168.122.209 [57003.873141] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_proxy_revalidate_in_response_max_stale_in_request_not_from_cache Apr 26 07:54:14 192.168.122.209 [57004.939629] [tdb] Start Tempesta DB Apr 26 07:54:14 192.168.122.209 [57005.080436] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:54:15 192.168.122.209 [57006.503350] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [57006.503350] Maybe that's fine, but it's worth checking the [57006.503350] config - if there is no relations between the [57006.503350] names, then host name confusion attack is possible. Apr 26 07:54:16 192.168.122.209 [57006.622129] [tempesta fw] Configuration processing is completed. Apr 26 07:54:16 192.168.122.209 [57006.673784] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:54:16 192.168.122.209 [57007.092140] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:54:16 192.168.122.209 [57007.119657] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:54:16 192.168.122.209 [57007.146589] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:54:16 192.168.122.209 [57007.186085] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:54:16 192.168.122.209 [57007.187086] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:54:16 192.168.122.209 [57007.238074] [tempesta fw] Tempesta FW is ready Apr 26 07:54:19 192.168.122.209 [57009.962494] [tdb] Close table 'client0.tdb' Apr 26 07:54:19 192.168.122.209 [57010.144825] [tdb] Close table 'sessions0.tdb' Apr 26 07:54:22 192.168.122.209 [57013.399248] [tdb] Close table 'cache0.tdb' Apr 26 07:54:23 192.168.122.209 [57013.655423] [tdb] Close table 'filter0.tdb' Apr 26 07:54:23 192.168.122.209 [57013.655846] [tempesta fw] modules are stopped Apr 26 07:54:23 192.168.122.209 [57013.862733] [tempesta fw] exiting... Apr 26 07:54:23 192.168.122.209 [57013.986673] [tdb] Shutdown Tempesta DB Apr 26 07:54:23 192.168.122.209 [57014.221180] End test: cache.test_h2_cache_control.TestH2CacheControl.test_proxy_revalidate_in_response_max_stale_in_request_not_from_cache Apr 26 07:54:23 192.168.122.209 [57014.244545] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_proxy_revalidate_in_response_not_from_cache Apr 26 07:54:24 192.168.122.209 [57015.297506] [tdb] Start Tempesta DB Apr 26 07:54:24 192.168.122.209 [57015.441873] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:54:26 192.168.122.209 [57016.831458] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [57016.831458] Maybe that's fine, but it's worth checking the [57016.831458] config - if there is no relations between the [57016.831458] names, then host name confusion attack is possible. Apr 26 07:54:26 192.168.122.209 [57016.958248] [tempesta fw] Configuration processing is completed. Apr 26 07:54:26 192.168.122.209 [57017.018320] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:54:26 192.168.122.209 [57017.436532] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:54:26 192.168.122.209 [57017.463629] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:54:26 192.168.122.209 [57017.490492] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:54:27 192.168.122.209 [57017.538213] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:54:27 192.168.122.209 [57017.539600] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:54:27 192.168.122.209 [57017.578200] [tempesta fw] Tempesta FW is ready Apr 26 07:54:29 192.168.122.209 [57020.243169] [tdb] Close table 'client0.tdb' Apr 26 07:54:29 192.168.122.209 [57020.443401] [tdb] Close table 'sessions0.tdb' Apr 26 07:54:33 192.168.122.209 [57023.638211] [tdb] Close table 'cache0.tdb' Apr 26 07:54:33 192.168.122.209 [57023.893749] [tdb] Close table 'filter0.tdb' Apr 26 07:54:33 192.168.122.209 [57023.894228] [tempesta fw] modules are stopped Apr 26 07:54:33 192.168.122.209 [57024.074650] [tempesta fw] exiting... Apr 26 07:54:33 192.168.122.209 [57024.223090] [tdb] Shutdown Tempesta DB Apr 26 07:54:33 192.168.122.209 [57024.433776] End test: cache.test_h2_cache_control.TestH2CacheControl.test_proxy_revalidate_in_response_not_from_cache Apr 26 07:54:33 192.168.122.209 [57024.457335] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_s_maxage_0_in_response Apr 26 07:54:35 192.168.122.209 [57025.543318] [tdb] Start Tempesta DB Apr 26 07:54:35 192.168.122.209 [57025.673200] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:54:36 192.168.122.209 [57027.079601] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [57027.079601] Maybe that's fine, but it's worth checking the [57027.079601] config - if there is no relations between the [57027.079601] names, then host name confusion attack is possible. Apr 26 07:54:36 192.168.122.209 [57027.198368] [tempesta fw] Configuration processing is completed. Apr 26 07:54:36 192.168.122.209 [57027.256187] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:54:37 192.168.122.209 [57027.667322] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:54:37 192.168.122.209 [57027.711141] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:54:37 192.168.122.209 [57027.737538] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:54:37 192.168.122.209 [57027.778377] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:54:37 192.168.122.209 [57027.780108] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:54:37 192.168.122.209 [57027.818333] [tempesta fw] Tempesta FW is ready Apr 26 07:54:37 192.168.122.209 [57028.483169] [tdb] Close table 'client0.tdb' Apr 26 07:54:38 192.168.122.209 [57028.670825] [tdb] Close table 'sessions0.tdb' Apr 26 07:54:41 192.168.122.209 [57031.912087] [tdb] Close table 'cache0.tdb' Apr 26 07:54:41 192.168.122.209 [57032.146817] [tdb] Close table 'filter0.tdb' Apr 26 07:54:41 192.168.122.209 [57032.147243] [tempesta fw] modules are stopped Apr 26 07:54:41 192.168.122.209 [57032.362531] [tempesta fw] exiting... Apr 26 07:54:41 192.168.122.209 [57032.505494] [tdb] Shutdown Tempesta DB Apr 26 07:54:42 192.168.122.209 [57032.700672] End test: cache.test_h2_cache_control.TestH2CacheControl.test_s_maxage_0_in_response Apr 26 07:54:42 192.168.122.209 [57032.732276] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_s_maxage_1_in_response_sleep_2 Apr 26 07:54:43 192.168.122.209 [57033.811313] [tdb] Start Tempesta DB Apr 26 07:54:43 192.168.122.209 [57033.953937] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:54:44 192.168.122.209 [57035.355778] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [57035.355778] Maybe that's fine, but it's worth checking the [57035.355778] config - if there is no relations between the [57035.355778] names, then host name confusion attack is possible. Apr 26 07:54:44 192.168.122.209 [57035.470482] [tempesta fw] Configuration processing is completed. Apr 26 07:54:44 192.168.122.209 [57035.521814] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:54:45 192.168.122.209 [57035.940368] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:54:45 192.168.122.209 [57035.968672] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:54:45 192.168.122.209 [57035.995552] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:54:45 192.168.122.209 [57036.038457] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:54:45 192.168.122.209 [57036.039933] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:54:45 192.168.122.209 [57036.078418] [tempesta fw] Tempesta FW is ready Apr 26 07:54:48 192.168.122.209 [57038.766656] [tdb] Close table 'client0.tdb' Apr 26 07:54:48 192.168.122.209 [57038.974599] [tdb] Close table 'sessions0.tdb' Apr 26 07:54:51 192.168.122.209 [57042.232404] [tdb] Close table 'cache0.tdb' Apr 26 07:54:51 192.168.122.209 [57042.479570] [tdb] Close table 'filter0.tdb' Apr 26 07:54:51 192.168.122.209 [57042.480012] [tempesta fw] modules are stopped Apr 26 07:54:52 192.168.122.209 [57042.665207] [tempesta fw] exiting... Apr 26 07:54:52 192.168.122.209 [57042.787140] [tdb] Shutdown Tempesta DB Apr 26 07:54:52 192.168.122.209 [57043.009015] End test: cache.test_h2_cache_control.TestH2CacheControl.test_s_maxage_1_in_response_sleep_2 Apr 26 07:54:52 192.168.122.209 [57043.027812] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_s_maxage_1_max_age_5_in_response_sleep_2 Apr 26 07:54:53 192.168.122.209 [57044.107515] [tdb] Start Tempesta DB Apr 26 07:54:53 192.168.122.209 [57044.251396] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:54:55 192.168.122.209 [57045.723846] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [57045.723846] Maybe that's fine, but it's worth checking the [57045.723846] config - if there is no relations between the [57045.723846] names, then host name confusion attack is possible. Apr 26 07:54:55 192.168.122.209 [57045.858555] [tempesta fw] Configuration processing is completed. Apr 26 07:54:55 192.168.122.209 [57045.910763] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:54:55 192.168.122.209 [57046.344151] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:54:55 192.168.122.209 [57046.371362] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:54:55 192.168.122.209 [57046.397950] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:54:55 192.168.122.209 [57046.446593] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:54:55 192.168.122.209 [57046.448339] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:54:55 192.168.122.209 [57046.490542] [tempesta fw] Tempesta FW is ready Apr 26 07:54:58 192.168.122.209 [57049.156383] [tdb] Close table 'client0.tdb' Apr 26 07:54:58 192.168.122.209 [57049.356737] [tdb] Close table 'sessions0.tdb' Apr 26 07:55:02 192.168.122.209 [57052.527783] [tdb] Close table 'cache0.tdb' Apr 26 07:55:02 192.168.122.209 [57052.766862] [tdb] Close table 'filter0.tdb' Apr 26 07:55:02 192.168.122.209 [57052.767321] [tempesta fw] modules are stopped Apr 26 07:55:02 192.168.122.209 [57052.991253] [tempesta fw] exiting... Apr 26 07:55:02 192.168.122.209 [57053.094593] [tdb] Shutdown Tempesta DB Apr 26 07:55:02 192.168.122.209 [57053.324141] End test: cache.test_h2_cache_control.TestH2CacheControl.test_s_maxage_1_max_age_5_in_response_sleep_2 Apr 26 07:55:02 192.168.122.209 [57053.346482] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_s_maxage_2_in_response_sleep_0 Apr 26 07:55:03 192.168.122.209 [57054.384338] [tdb] Start Tempesta DB Apr 26 07:55:04 192.168.122.209 [57054.525253] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:55:05 192.168.122.209 [57055.940001] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [57055.940001] Maybe that's fine, but it's worth checking the [57055.940001] config - if there is no relations between the [57055.940001] names, then host name confusion attack is possible. Apr 26 07:55:05 192.168.122.209 [57056.062735] [tempesta fw] Configuration processing is completed. Apr 26 07:55:05 192.168.122.209 [57056.115442] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:55:06 192.168.122.209 [57056.540268] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:55:06 192.168.122.209 [57056.576789] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:55:06 192.168.122.209 [57056.603155] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:55:06 192.168.122.209 [57056.650721] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:55:06 192.168.122.209 [57056.652457] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:55:06 192.168.122.209 [57056.690667] [tempesta fw] Tempesta FW is ready Apr 26 07:55:06 192.168.122.209 [57057.386632] [tdb] Close table 'client0.tdb' Apr 26 07:55:07 192.168.122.209 [57057.633367] [tdb] Close table 'sessions0.tdb' Apr 26 07:55:10 192.168.122.209 [57060.861061] [tdb] Close table 'cache0.tdb' Apr 26 07:55:10 192.168.122.209 [57061.100360] [tdb] Close table 'filter0.tdb' Apr 26 07:55:10 192.168.122.209 [57061.100782] [tempesta fw] modules are stopped Apr 26 07:55:10 192.168.122.209 [57061.312461] [tempesta fw] exiting... Apr 26 07:55:10 192.168.122.209 [57061.460913] [tdb] Shutdown Tempesta DB Apr 26 07:55:11 192.168.122.209 [57061.677773] End test: cache.test_h2_cache_control.TestH2CacheControl.test_s_maxage_2_in_response_sleep_0 Apr 26 07:55:11 192.168.122.209 [57061.697317] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_s_maxage_in_request Apr 26 07:55:12 192.168.122.209 [57062.767861] [tdb] Start Tempesta DB Apr 26 07:55:12 192.168.122.209 [57062.913219] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:55:13 192.168.122.209 [57064.360066] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [57064.360066] Maybe that's fine, but it's worth checking the [57064.360066] config - if there is no relations between the [57064.360066] names, then host name confusion attack is possible. Apr 26 07:55:13 192.168.122.209 [57064.494839] [tempesta fw] Configuration processing is completed. Apr 26 07:55:14 192.168.122.209 [57064.559979] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:55:14 192.168.122.209 [57064.976291] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:55:14 192.168.122.209 [57065.002295] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:55:14 192.168.122.209 [57065.029344] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:55:14 192.168.122.209 [57065.070827] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:55:14 192.168.122.209 [57065.072559] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:55:14 192.168.122.209 [57065.114791] [tempesta fw] Tempesta FW is ready Apr 26 07:55:15 192.168.122.209 [57065.808899] [tdb] Close table 'client0.tdb' Apr 26 07:55:15 192.168.122.209 [57065.996509] [tdb] Close table 'sessions0.tdb' Apr 26 07:55:18 192.168.122.209 [57069.186635] [tdb] Close table 'cache0.tdb' Apr 26 07:55:18 192.168.122.209 [57069.432739] [tdb] Close table 'filter0.tdb' Apr 26 07:55:18 192.168.122.209 [57069.433171] [tempesta fw] modules are stopped Apr 26 07:55:19 192.168.122.209 [57069.610863] [tempesta fw] exiting... Apr 26 07:55:19 192.168.122.209 [57069.740912] [tdb] Shutdown Tempesta DB Apr 26 07:55:19 192.168.122.209 [57069.966703] End test: cache.test_h2_cache_control.TestH2CacheControl.test_s_maxage_in_request Apr 26 07:55:19 192.168.122.209 [57069.986654] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_s_maxage_in_response_and_max_stale_in_request Apr 26 07:55:20 192.168.122.209 [57070.971968] [tdb] Start Tempesta DB Apr 26 07:55:20 192.168.122.209 [57071.118004] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:55:21 192.168.122.209 [57072.460175] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [57072.460175] Maybe that's fine, but it's worth checking the [57072.460175] config - if there is no relations between the [57072.460175] names, then host name confusion attack is possible. Apr 26 07:55:22 192.168.122.209 [57072.590963] [tempesta fw] Configuration processing is completed. Apr 26 07:55:22 192.168.122.209 [57072.641264] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:55:22 192.168.122.209 [57073.065207] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:55:22 192.168.122.209 [57073.091749] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:55:22 192.168.122.209 [57073.117890] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:55:22 192.168.122.209 [57073.194940] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:55:22 192.168.122.209 [57073.196705] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:55:22 192.168.122.209 [57073.234879] [tempesta fw] Tempesta FW is ready Apr 26 07:55:25 192.168.122.209 [57075.900498] [tdb] Close table 'client0.tdb' Apr 26 07:55:25 192.168.122.209 [57076.097549] [tdb] Close table 'sessions0.tdb' Apr 26 07:55:28 192.168.122.209 [57079.358365] [tdb] Close table 'cache0.tdb' Apr 26 07:55:29 192.168.122.209 [57079.589168] [tdb] Close table 'filter0.tdb' Apr 26 07:55:29 192.168.122.209 [57079.589616] [tempesta fw] modules are stopped Apr 26 07:55:29 192.168.122.209 [57079.773995] [tempesta fw] exiting... Apr 26 07:55:29 192.168.122.209 [57079.929722] [tdb] Shutdown Tempesta DB Apr 26 07:55:29 192.168.122.209 [57080.164747] End test: cache.test_h2_cache_control.TestH2CacheControl.test_s_maxage_in_response_and_max_stale_in_request Apr 26 07:55:29 192.168.122.209 [57080.189380] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_same_authorization_in_requests Apr 26 07:55:30 192.168.122.209 [57081.235242] [tdb] Start Tempesta DB Apr 26 07:55:30 192.168.122.209 [57081.363064] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:55:32 192.168.122.209 [57082.740367] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [57082.740367] Maybe that's fine, but it's worth checking the [57082.740367] config - if there is no relations between the [57082.740367] names, then host name confusion attack is possible. Apr 26 07:55:32 192.168.122.209 [57082.895103] [tempesta fw] Configuration processing is completed. Apr 26 07:55:32 192.168.122.209 [57082.946629] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:55:32 192.168.122.209 [57083.359419] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:55:32 192.168.122.209 [57083.394564] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:55:32 192.168.122.209 [57083.429194] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:55:32 192.168.122.209 [57083.471056] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:55:32 192.168.122.209 [57083.472815] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:55:32 192.168.122.209 [57083.511006] [tempesta fw] Tempesta FW is ready Apr 26 07:55:33 192.168.122.209 [57084.190573] [tdb] Close table 'client0.tdb' Apr 26 07:55:33 192.168.122.209 [57084.379571] [tdb] Close table 'sessions0.tdb' Apr 26 07:55:37 192.168.122.209 [57087.570869] [tdb] Close table 'cache0.tdb' Apr 26 07:55:37 192.168.122.209 [57087.806880] [tdb] Close table 'filter0.tdb' Apr 26 07:55:37 192.168.122.209 [57087.807725] [tempesta fw] modules are stopped Apr 26 07:55:37 192.168.122.209 [57088.004361] [tempesta fw] exiting... Apr 26 07:55:37 192.168.122.209 [57088.155952] [tdb] Shutdown Tempesta DB Apr 26 07:55:37 192.168.122.209 [57088.379801] End test: cache.test_h2_cache_control.TestH2CacheControl.test_same_authorization_in_requests Apr 26 07:55:37 192.168.122.209 [57088.404145] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_same_authorization_in_requests_from_dynamic_table Apr 26 07:55:38 192.168.122.209 [57089.513806] [tdb] Start Tempesta DB Apr 26 07:55:39 192.168.122.209 [57089.654161] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:55:40 192.168.122.209 [57091.084398] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [57091.084398] Maybe that's fine, but it's worth checking the [57091.084398] config - if there is no relations between the [57091.084398] names, then host name confusion attack is possible. Apr 26 07:55:40 192.168.122.209 [57091.199193] [tempesta fw] Configuration processing is completed. Apr 26 07:55:40 192.168.122.209 [57091.249925] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:55:41 192.168.122.209 [57091.663931] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:55:41 192.168.122.209 [57091.690361] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:55:41 192.168.122.209 [57091.717374] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:55:41 192.168.122.209 [57091.795176] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:55:41 192.168.122.209 [57091.796923] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:55:41 192.168.122.209 [57091.835108] [tempesta fw] Tempesta FW is ready Apr 26 07:55:41 192.168.122.209 [57092.490191] [tdb] Close table 'client0.tdb' Apr 26 07:55:42 192.168.122.209 [57092.674606] [tdb] Close table 'sessions0.tdb' Apr 26 07:55:45 192.168.122.209 [57095.894674] [tdb] Close table 'cache0.tdb' Apr 26 07:55:45 192.168.122.209 [57096.121916] [tdb] Close table 'filter0.tdb' Apr 26 07:55:45 192.168.122.209 [57096.122360] [tempesta fw] modules are stopped Apr 26 07:55:45 192.168.122.209 [57096.317949] [tempesta fw] exiting... Apr 26 07:55:45 192.168.122.209 [57096.447961] [tdb] Shutdown Tempesta DB Apr 26 07:55:46 192.168.122.209 [57096.641744] End test: cache.test_h2_cache_control.TestH2CacheControl.test_same_authorization_in_requests_from_dynamic_table Apr 26 07:55:46 192.168.122.209 [57096.664201] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_same_authorization_in_requests_max_age_in_response Apr 26 07:55:47 192.168.122.209 [57097.699217] [tdb] Start Tempesta DB Apr 26 07:55:47 192.168.122.209 [57097.852956] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:55:48 192.168.122.209 [57099.280527] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [57099.280527] Maybe that's fine, but it's worth checking the [57099.280527] config - if there is no relations between the [57099.280527] names, then host name confusion attack is possible. Apr 26 07:55:48 192.168.122.209 [57099.411290] [tempesta fw] Configuration processing is completed. Apr 26 07:55:48 192.168.122.209 [57099.462621] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:55:49 192.168.122.209 [57099.888859] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:55:49 192.168.122.209 [57099.915810] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:55:49 192.168.122.209 [57099.942256] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:55:49 192.168.122.209 [57099.987267] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:55:49 192.168.122.209 [57099.989007] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:55:49 192.168.122.209 [57100.031216] [tempesta fw] Tempesta FW is ready Apr 26 07:55:50 192.168.122.209 [57100.728963] [tdb] Close table 'client0.tdb' Apr 26 07:55:50 192.168.122.209 [57100.924279] [tdb] Close table 'sessions0.tdb' Apr 26 07:55:53 192.168.122.209 [57104.132800] [tdb] Close table 'cache0.tdb' Apr 26 07:55:53 192.168.122.209 [57104.382579] [tdb] Close table 'filter0.tdb' Apr 26 07:55:53 192.168.122.209 [57104.383040] [tempesta fw] modules are stopped Apr 26 07:55:54 192.168.122.209 [57104.571934] [tempesta fw] exiting... Apr 26 07:55:54 192.168.122.209 [57104.710769] [tdb] Shutdown Tempesta DB Apr 26 07:55:54 192.168.122.209 [57104.932792] End test: cache.test_h2_cache_control.TestH2CacheControl.test_same_authorization_in_requests_max_age_in_response Apr 26 07:55:54 192.168.122.209 [57104.944406] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_same_authorization_in_requests_no_transform_in_response Apr 26 07:55:55 192.168.122.209 [57106.063522] [tdb] Start Tempesta DB Apr 26 07:55:55 192.168.122.209 [57106.194162] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:55:57 192.168.122.209 [57107.580636] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [57107.580636] Maybe that's fine, but it's worth checking the [57107.580636] config - if there is no relations between the [57107.580636] names, then host name confusion attack is possible. Apr 26 07:55:57 192.168.122.209 [57107.707382] [tempesta fw] Configuration processing is completed. Apr 26 07:55:57 192.168.122.209 [57107.764273] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:55:57 192.168.122.209 [57108.186815] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:55:57 192.168.122.209 [57108.213811] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:55:57 192.168.122.209 [57108.240085] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:55:57 192.168.122.209 [57108.283392] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:55:57 192.168.122.209 [57108.285132] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:55:57 192.168.122.209 [57108.323329] [tempesta fw] Tempesta FW is ready Apr 26 07:55:58 192.168.122.209 [57108.973108] [tdb] Close table 'client0.tdb' Apr 26 07:55:58 192.168.122.209 [57109.159600] [tdb] Close table 'sessions0.tdb' Apr 26 07:56:01 192.168.122.209 [57112.346135] [tdb] Close table 'cache0.tdb' Apr 26 07:56:02 192.168.122.209 [57112.553830] [tdb] Close table 'filter0.tdb' Apr 26 07:56:02 192.168.122.209 [57112.554265] [tempesta fw] modules are stopped Apr 26 07:56:02 192.168.122.209 [57112.730593] [tempesta fw] exiting... Apr 26 07:56:02 192.168.122.209 [57112.840628] [tdb] Shutdown Tempesta DB Apr 26 07:56:02 192.168.122.209 [57113.074205] End test: cache.test_h2_cache_control.TestH2CacheControl.test_same_authorization_in_requests_no_transform_in_response Apr 26 07:56:02 192.168.122.209 [57113.093965] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_set_cookie_no_cached Apr 26 07:56:03 192.168.122.209 [57114.140305] [tdb] Start Tempesta DB Apr 26 07:56:03 192.168.122.209 [57114.274736] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:56:05 192.168.122.209 [57115.752716] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [57115.752716] Maybe that's fine, but it's worth checking the [57115.752716] config - if there is no relations between the [57115.752716] names, then host name confusion attack is possible. Apr 26 07:56:05 192.168.122.209 [57115.871502] [tempesta fw] Configuration processing is completed. Apr 26 07:56:05 192.168.122.209 [57115.922661] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:56:05 192.168.122.209 [57116.341701] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:56:05 192.168.122.209 [57116.368226] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:56:05 192.168.122.209 [57116.394366] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:56:05 192.168.122.209 [57116.447483] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:56:05 192.168.122.209 [57116.449234] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:56:05 192.168.122.209 [57116.487424] [tempesta fw] Tempesta FW is ready Apr 26 07:56:06 192.168.122.209 [57117.173432] [tdb] Close table 'client0.tdb' Apr 26 07:56:06 192.168.122.209 [57117.372703] [tdb] Close table 'sessions0.tdb' Apr 26 07:56:10 192.168.122.209 [57120.578010] [tdb] Close table 'cache0.tdb' Apr 26 07:56:10 192.168.122.209 [57120.820024] [tdb] Close table 'filter0.tdb' Apr 26 07:56:10 192.168.122.209 [57120.820469] [tempesta fw] modules are stopped Apr 26 07:56:10 192.168.122.209 [57120.993734] [tempesta fw] exiting... Apr 26 07:56:10 192.168.122.209 [57121.092853] [tdb] Shutdown Tempesta DB Apr 26 07:56:10 192.168.122.209 [57121.329866] End test: cache.test_h2_cache_control.TestH2CacheControl.test_set_cookie_no_cached Apr 26 07:56:10 192.168.122.209 [57121.343640] Start test: cache.test_h2_cache_control.TestH2CacheControlIgnore.test_ignore_max_age_not_ignore_s_maxage Apr 26 07:56:11 192.168.122.209 [57122.431816] [tdb] Start Tempesta DB Apr 26 07:56:12 192.168.122.209 [57122.575511] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:56:13 192.168.122.209 [57123.900887] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [57123.900887] Maybe that's fine, but it's worth checking the [57123.900887] config - if there is no relations between the [57123.900887] names, then host name confusion attack is possible. Apr 26 07:56:13 192.168.122.209 [57124.043594] [tempesta fw] Configuration processing is completed. Apr 26 07:56:13 192.168.122.209 [57124.098072] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:56:13 192.168.122.209 [57124.518320] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:56:14 192.168.122.209 [57124.545292] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:56:14 192.168.122.209 [57124.572686] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:56:14 192.168.122.209 [57124.619588] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:56:14 192.168.122.209 [57124.621333] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:56:14 192.168.122.209 [57124.659559] [tempesta fw] Tempesta FW is ready Apr 26 07:56:16 192.168.122.209 [57127.342320] [tdb] Close table 'client0.tdb' Apr 26 07:56:17 192.168.122.209 [57127.530818] [tdb] Close table 'sessions0.tdb' Apr 26 07:56:20 192.168.122.209 [57130.790364] [tdb] Close table 'cache0.tdb' Apr 26 07:56:20 192.168.122.209 [57131.010564] [tdb] Close table 'filter0.tdb' Apr 26 07:56:20 192.168.122.209 [57131.011007] [tempesta fw] modules are stopped Apr 26 07:56:20 192.168.122.209 [57131.226646] [tempesta fw] exiting... Apr 26 07:56:20 192.168.122.209 [57131.349027] [tdb] Shutdown Tempesta DB Apr 26 07:56:21 192.168.122.209 [57131.589178] End test: cache.test_h2_cache_control.TestH2CacheControlIgnore.test_ignore_max_age_not_ignore_s_maxage Apr 26 07:56:21 192.168.122.209 [57131.604906] Start test: cache.test_h2_cache_control.TestH2CacheControlIgnore.test_ignore_max_age_s_maxage Apr 26 07:56:22 192.168.122.209 [57132.669942] [tdb] Start Tempesta DB Apr 26 07:56:22 192.168.122.209 [57132.811268] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:56:23 192.168.122.209 [57134.240909] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [57134.240909] Maybe that's fine, but it's worth checking the [57134.240909] config - if there is no relations between the [57134.240909] names, then host name confusion attack is possible. Apr 26 07:56:23 192.168.122.209 [57134.375734] [tempesta fw] Configuration processing is completed. Apr 26 07:56:23 192.168.122.209 [57134.425800] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:56:24 192.168.122.209 [57134.844433] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:56:24 192.168.122.209 [57134.871455] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:56:24 192.168.122.209 [57134.898026] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:56:24 192.168.122.209 [57134.939725] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:56:24 192.168.122.209 [57134.941468] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:56:24 192.168.122.209 [57134.991655] [tempesta fw] Tempesta FW is ready Apr 26 07:56:27 192.168.122.209 [57137.654977] [tdb] Close table 'client0.tdb' Apr 26 07:56:27 192.168.122.209 [57137.841864] [tdb] Close table 'sessions0.tdb' Apr 26 07:56:30 192.168.122.209 [57141.166429] [tdb] Close table 'cache0.tdb' Apr 26 07:56:30 192.168.122.209 [57141.390436] [tdb] Close table 'filter0.tdb' Apr 26 07:56:30 192.168.122.209 [57141.390865] [tempesta fw] modules are stopped Apr 26 07:56:31 192.168.122.209 [57141.566671] [tempesta fw] exiting... Apr 26 07:56:31 192.168.122.209 [57141.689820] [tdb] Shutdown Tempesta DB Apr 26 07:56:31 192.168.122.209 [57141.886328] End test: cache.test_h2_cache_control.TestH2CacheControlIgnore.test_ignore_max_age_s_maxage Apr 26 07:56:31 192.168.122.209 [57141.902872] Start test: cache.test_h2_cache_control.TestH2CacheControlIgnore.test_ignore_max_stale_in_request Apr 26 07:56:32 192.168.122.209 [57142.938981] [tdb] Start Tempesta DB Apr 26 07:56:32 192.168.122.209 [57143.069598] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:56:33 192.168.122.209 [57144.397103] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [57144.397103] Maybe that's fine, but it's worth checking the [57144.397103] config - if there is no relations between the [57144.397103] names, then host name confusion attack is possible. Apr 26 07:56:34 192.168.122.209 [57144.527876] [tempesta fw] Configuration processing is completed. Apr 26 07:56:34 192.168.122.209 [57144.579867] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:56:34 192.168.122.209 [57145.002409] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:56:34 192.168.122.209 [57145.029797] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:56:34 192.168.122.209 [57145.057234] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:56:34 192.168.122.209 [57145.095775] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:56:34 192.168.122.209 [57145.096765] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:56:34 192.168.122.209 [57145.135790] [tempesta fw] Tempesta FW is ready Apr 26 07:56:37 192.168.122.209 [57147.825186] [tdb] Close table 'client0.tdb' Apr 26 07:56:37 192.168.122.209 [57148.015284] [tdb] Close table 'sessions0.tdb' Apr 26 07:56:40 192.168.122.209 [57151.213265] [tdb] Close table 'cache0.tdb' Apr 26 07:56:40 192.168.122.209 [57151.456665] [tdb] Close table 'filter0.tdb' Apr 26 07:56:40 192.168.122.209 [57151.457081] [tempesta fw] modules are stopped Apr 26 07:56:41 192.168.122.209 [57151.674783] [tempesta fw] exiting... Apr 26 07:56:41 192.168.122.209 [57151.785811] [tdb] Shutdown Tempesta DB Apr 26 07:56:41 192.168.122.209 [57151.988584] End test: cache.test_h2_cache_control.TestH2CacheControlIgnore.test_ignore_max_stale_in_request Apr 26 07:56:41 192.168.122.209 [57152.008700] Start test: cache.test_h2_cache_control.TestH2CacheControlIgnore.test_ignore_must_revalidate Apr 26 07:56:42 192.168.122.209 [57153.082450] [tdb] Start Tempesta DB Apr 26 07:56:42 192.168.122.209 [57153.205087] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:56:44 192.168.122.209 [57154.609279] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [57154.609279] Maybe that's fine, but it's worth checking the [57154.609279] config - if there is no relations between the [57154.609279] names, then host name confusion attack is possible. Apr 26 07:56:44 192.168.122.209 [57154.739967] [tempesta fw] Configuration processing is completed. Apr 26 07:56:44 192.168.122.209 [57154.791422] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:56:44 192.168.122.209 [57155.211222] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:56:44 192.168.122.209 [57155.238021] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:56:44 192.168.122.209 [57155.263886] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:56:44 192.168.122.209 [57155.351932] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:56:44 192.168.122.209 [57155.353672] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:56:44 192.168.122.209 [57155.407907] [tempesta fw] Tempesta FW is ready Apr 26 07:56:47 192.168.122.209 [57158.052918] [tdb] Close table 'client0.tdb' Apr 26 07:56:47 192.168.122.209 [57158.266974] [tdb] Close table 'sessions0.tdb' Apr 26 07:56:51 192.168.122.209 [57161.528203] [tdb] Close table 'cache0.tdb' Apr 26 07:56:51 192.168.122.209 [57161.757583] [tdb] Close table 'filter0.tdb' Apr 26 07:56:51 192.168.122.209 [57161.758000] [tempesta fw] modules are stopped Apr 26 07:56:51 192.168.122.209 [57161.976676] [tempesta fw] exiting... Apr 26 07:56:51 192.168.122.209 [57162.121820] [tdb] Shutdown Tempesta DB Apr 26 07:56:51 192.168.122.209 [57162.343799] End test: cache.test_h2_cache_control.TestH2CacheControlIgnore.test_ignore_must_revalidate Apr 26 07:56:51 192.168.122.209 [57162.363378] Start test: cache.test_h2_cache_control.TestH2CacheControlIgnore.test_ignore_public_with_authorization Apr 26 07:56:52 192.168.122.209 [57163.411809] [tdb] Start Tempesta DB Apr 26 07:56:53 192.168.122.209 [57163.557968] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:56:54 192.168.122.209 [57164.977352] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [57164.977352] Maybe that's fine, but it's worth checking the [57164.977352] config - if there is no relations between the [57164.977352] names, then host name confusion attack is possible. Apr 26 07:56:54 192.168.122.209 [57165.112105] [tempesta fw] Configuration processing is completed. Apr 26 07:56:54 192.168.122.209 [57165.166374] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:56:55 192.168.122.209 [57165.581742] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:56:55 192.168.122.209 [57165.608362] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:56:55 192.168.122.209 [57165.635412] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:56:55 192.168.122.209 [57165.692105] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:56:55 192.168.122.209 [57165.693858] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:56:55 192.168.122.209 [57165.732049] [tempesta fw] Tempesta FW is ready Apr 26 07:56:55 192.168.122.209 [57166.390704] [tdb] Close table 'client0.tdb' Apr 26 07:56:56 192.168.122.209 [57166.578159] [tdb] Close table 'sessions0.tdb' Apr 26 07:56:59 192.168.122.209 [57169.788808] [tdb] Close table 'cache0.tdb' Apr 26 07:56:59 192.168.122.209 [57170.028943] [tdb] Close table 'filter0.tdb' Apr 26 07:56:59 192.168.122.209 [57170.029379] [tempesta fw] modules are stopped Apr 26 07:56:59 192.168.122.209 [57170.213054] [tempesta fw] exiting... Apr 26 07:56:59 192.168.122.209 [57170.361182] [tdb] Shutdown Tempesta DB Apr 26 07:57:00 192.168.122.209 [57170.572590] End test: cache.test_h2_cache_control.TestH2CacheControlIgnore.test_ignore_public_with_authorization Apr 26 07:57:00 192.168.122.209 [57170.589612] Start test: cache.test_h2_cache_control.TestH2CacheControlIgnore.test_multi_ignore_private_no_cache_no_store Apr 26 07:57:01 192.168.122.209 [57171.619725] [tdb] Start Tempesta DB Apr 26 07:57:01 192.168.122.209 [57171.759272] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:57:02 192.168.122.209 [57173.137453] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [57173.137453] Maybe that's fine, but it's worth checking the [57173.137453] config - if there is no relations between the [57173.137453] names, then host name confusion attack is possible. Apr 26 07:57:02 192.168.122.209 [57173.280129] [tempesta fw] Configuration processing is completed. Apr 26 07:57:02 192.168.122.209 [57173.330712] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:57:03 192.168.122.209 [57173.745840] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:57:03 192.168.122.209 [57173.782762] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:57:03 192.168.122.209 [57173.808318] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:57:03 192.168.122.209 [57173.856198] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:57:03 192.168.122.209 [57173.857904] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:57:03 192.168.122.209 [57173.900144] [tempesta fw] Tempesta FW is ready Apr 26 07:57:04 192.168.122.209 [57174.553725] [tdb] Close table 'client0.tdb' Apr 26 07:57:04 192.168.122.209 [57174.754458] [tdb] Close table 'sessions0.tdb' Apr 26 07:57:07 192.168.122.209 [57177.981531] [tdb] Close table 'cache0.tdb' Apr 26 07:57:07 192.168.122.209 [57178.243804] [tdb] Close table 'filter0.tdb' Apr 26 07:57:07 192.168.122.209 [57178.244780] [tempesta fw] modules are stopped Apr 26 07:57:07 192.168.122.209 [57178.470592] [tempesta fw] exiting... Apr 26 07:57:08 192.168.122.209 [57178.614298] [tdb] Shutdown Tempesta DB Apr 26 07:57:08 192.168.122.209 [57178.829213] End test: cache.test_h2_cache_control.TestH2CacheControlIgnore.test_multi_ignore_private_no_cache_no_store Apr 26 07:57:08 192.168.122.209 [57178.846378] Start test: cache.test_h2_cache_control.TestH2CacheType.test_cache_is_shared Apr 26 07:57:09 192.168.122.209 [57179.902749] [tdb] Start Tempesta DB Apr 26 07:57:09 192.168.122.209 [57180.044821] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:57:10 192.168.122.209 [57181.469560] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [57181.469560] Maybe that's fine, but it's worth checking the [57181.469560] config - if there is no relations between the [57181.469560] names, then host name confusion attack is possible. Apr 26 07:57:11 192.168.122.209 [57181.616313] [tempesta fw] Configuration processing is completed. Apr 26 07:57:11 192.168.122.209 [57181.676495] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:57:11 192.168.122.209 [57182.116731] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:57:11 192.168.122.209 [57182.144196] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:57:11 192.168.122.209 [57182.173340] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:57:11 192.168.122.209 [57182.212247] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 07:57:11 192.168.122.209 [57182.213523] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:57:11 192.168.122.209 [57182.256250] [tempesta fw] Tempesta FW is ready Apr 26 07:57:14 192.168.122.209 [57184.966245] [tdb] Close table 'client0.tdb' Apr 26 07:57:14 192.168.122.209 [57185.153658] [tdb] Close table 'sessions0.tdb' Apr 26 07:57:17 192.168.122.209 [57188.402440] [tdb] Close table 'cache0.tdb' Apr 26 07:57:18 192.168.122.209 [57188.633530] [tdb] Close table 'filter0.tdb' Apr 26 07:57:18 192.168.122.209 [57188.633955] [tempesta fw] modules are stopped Apr 26 07:57:18 192.168.122.209 [57188.872017] [tempesta fw] exiting... Apr 26 07:57:18 192.168.122.209 [57188.987355] [tdb] Shutdown Tempesta DB Apr 26 07:57:18 192.168.122.209 [57189.202765] End test: cache.test_h2_cache_control.TestH2CacheType.test_cache_is_shared Apr 26 07:57:18 192.168.122.209 [57189.221870] Start test: cache.test_purge.TestPurgeAcl.test_purge_acl_fail Apr 26 07:57:19 192.168.122.209 [57190.241264] [tdb] Start Tempesta DB Apr 26 07:57:19 192.168.122.209 [57190.379734] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:57:21 192.168.122.209 [57191.960440] [tempesta fw] Configuration processing is completed. Apr 26 07:57:21 192.168.122.209 [57192.017416] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:57:21 192.168.122.209 [57192.434731] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:57:21 192.168.122.209 [57192.461643] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:57:21 192.168.122.209 [57192.488279] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:57:22 192.168.122.209 [57192.524435] [tempesta fw] Open listen socket on: ::1 Apr 26 07:57:22 192.168.122.209 [57192.525999] [tempesta fw] Open listen socket on: 127.0.0.1 Apr 26 07:57:22 192.168.122.209 [57192.568374] [tempesta fw] Tempesta FW is ready Apr 26 07:57:22 192.168.122.209 [57192.714205] [tempesta fw] Warning: purge: ACL violation, status 403: 127.0.0.2 Apr 26 07:57:22 192.168.122.209 [57193.149762] [tdb] Close table 'client0.tdb' Apr 26 07:57:22 192.168.122.209 [57193.344744] [tdb] Close table 'sessions0.tdb' Apr 26 07:57:25 192.168.122.209 [57196.475885] [tdb] Close table 'cache0.tdb' Apr 26 07:57:26 192.168.122.209 [57196.740473] [tdb] Close table 'filter0.tdb' Apr 26 07:57:26 192.168.122.209 [57196.740907] [tempesta fw] modules are stopped Apr 26 07:57:26 192.168.122.209 [57196.953754] [tempesta fw] exiting... Apr 26 07:57:26 192.168.122.209 [57197.089567] [tdb] Shutdown Tempesta DB Apr 26 07:57:26 192.168.122.209 [57197.338547] End test: cache.test_purge.TestPurgeAcl.test_purge_acl_fail Apr 26 07:57:26 192.168.122.209 [57197.364974] Start test: cache.test_purge.TestPurgeAcl.test_purge_acl_ipv4 Apr 26 07:57:27 192.168.122.209 [57198.380465] [tdb] Start Tempesta DB Apr 26 07:57:27 192.168.122.209 [57198.505865] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:57:29 192.168.122.209 [57200.060553] [tempesta fw] Configuration processing is completed. Apr 26 07:57:29 192.168.122.209 [57200.112502] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:57:30 192.168.122.209 [57200.553824] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:57:30 192.168.122.209 [57200.580052] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:57:30 192.168.122.209 [57200.605750] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:57:30 192.168.122.209 [57200.672542] [tempesta fw] Open listen socket on: ::1 Apr 26 07:57:30 192.168.122.209 [57200.674098] [tempesta fw] Open listen socket on: 127.0.0.1 Apr 26 07:57:30 192.168.122.209 [57200.716472] [tempesta fw] Tempesta FW is ready Apr 26 07:57:30 192.168.122.209 [57200.902380] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 07:57:30 192.168.122.209 [57201.377342] [tdb] Close table 'client0.tdb' Apr 26 07:57:31 192.168.122.209 [57201.566165] [tdb] Close table 'sessions0.tdb' Apr 26 07:57:34 192.168.122.209 [57204.762509] [tdb] Close table 'cache0.tdb' Apr 26 07:57:34 192.168.122.209 [57205.000306] [tdb] Close table 'filter0.tdb' Apr 26 07:57:34 192.168.122.209 [57205.000747] [tempesta fw] modules are stopped Apr 26 07:57:34 192.168.122.209 [57205.229113] [tempesta fw] exiting... Apr 26 07:57:34 192.168.122.209 [57205.359442] [tdb] Shutdown Tempesta DB Apr 26 07:57:35 192.168.122.209 [57205.587012] End test: cache.test_purge.TestPurgeAcl.test_purge_acl_ipv4 Apr 26 07:57:35 192.168.122.209 [57205.596299] Start test: cache.test_purge.TestPurgeAcl.test_purge_acl_ipv4_and_ipv6 Apr 26 07:57:36 192.168.122.209 [57206.661509] [tdb] Start Tempesta DB Apr 26 07:57:36 192.168.122.209 [57206.802307] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:57:37 192.168.122.209 [57208.316638] [tempesta fw] Configuration processing is completed. Apr 26 07:57:37 192.168.122.209 [57208.374663] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:57:38 192.168.122.209 [57208.796662] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:57:38 192.168.122.209 [57208.823709] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:57:38 192.168.122.209 [57208.852576] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:57:38 192.168.122.209 [57208.904646] [tempesta fw] Open listen socket on: ::1 Apr 26 07:57:38 192.168.122.209 [57208.906188] [tempesta fw] Open listen socket on: 127.0.0.1 Apr 26 07:57:38 192.168.122.209 [57208.972594] [tempesta fw] Tempesta FW is ready Apr 26 07:57:38 192.168.122.209 [57209.151254] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 07:57:39 192.168.122.209 [57209.633931] [tdb] Close table 'client0.tdb' Apr 26 07:57:39 192.168.122.209 [57209.825574] [tdb] Close table 'sessions0.tdb' Apr 26 07:57:42 192.168.122.209 [57213.016645] [tdb] Close table 'cache0.tdb' Apr 26 07:57:42 192.168.122.209 [57213.252635] [tdb] Close table 'filter0.tdb' Apr 26 07:57:42 192.168.122.209 [57213.253062] [tempesta fw] modules are stopped Apr 26 07:57:42 192.168.122.209 [57213.438027] [tempesta fw] exiting... Apr 26 07:57:43 192.168.122.209 [57213.549034] [tdb] Shutdown Tempesta DB Apr 26 07:57:43 192.168.122.209 [57213.778455] End test: cache.test_purge.TestPurgeAcl.test_purge_acl_ipv4_and_ipv6 Apr 26 07:57:43 192.168.122.209 [57213.797907] Start test: cache.test_purge.TestPurgeAcl.test_purge_acl_ipv4_with_mask Apr 26 07:57:44 192.168.122.209 [57214.817475] [tdb] Start Tempesta DB Apr 26 07:57:44 192.168.122.209 [57214.947258] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:57:45 192.168.122.209 [57216.456776] [tempesta fw] Configuration processing is completed. Apr 26 07:57:45 192.168.122.209 [57216.514261] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:57:46 192.168.122.209 [57216.959881] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:57:46 192.168.122.209 [57216.998223] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:57:46 192.168.122.209 [57217.025181] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:57:46 192.168.122.209 [57217.072694] [tempesta fw] Open listen socket on: ::1 Apr 26 07:57:46 192.168.122.209 [57217.073882] [tempesta fw] Open listen socket on: 127.0.0.1 Apr 26 07:57:46 192.168.122.209 [57217.108707] [tempesta fw] Tempesta FW is ready Apr 26 07:57:46 192.168.122.209 [57217.273018] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 07:57:47 192.168.122.209 [57217.775189] [tdb] Close table 'client0.tdb' Apr 26 07:57:47 192.168.122.209 [57217.975338] [tdb] Close table 'sessions0.tdb' Apr 26 07:57:50 192.168.122.209 [57221.235667] [tdb] Close table 'cache0.tdb' Apr 26 07:57:50 192.168.122.209 [57221.491467] [tdb] Close table 'filter0.tdb' Apr 26 07:57:50 192.168.122.209 [57221.491902] [tempesta fw] modules are stopped Apr 26 07:57:51 192.168.122.209 [57221.669000] [tempesta fw] exiting... Apr 26 07:57:51 192.168.122.209 [57221.786182] [tdb] Shutdown Tempesta DB Apr 26 07:57:51 192.168.122.209 [57222.026537] End test: cache.test_purge.TestPurgeAcl.test_purge_acl_ipv4_with_mask Apr 26 07:57:51 192.168.122.209 [57222.041013] Start test: cache.test_purge.TestPurgeAcl.test_purge_fail Apr 26 07:57:52 192.168.122.209 [57223.050243] [tdb] Start Tempesta DB Apr 26 07:57:52 192.168.122.209 [57223.180828] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:57:54 192.168.122.209 [57224.628864] [tempesta fw] Configuration processing is completed. Apr 26 07:57:54 192.168.122.209 [57224.679376] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:57:54 192.168.122.209 [57225.100700] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:57:54 192.168.122.209 [57225.128046] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:57:54 192.168.122.209 [57225.154151] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:57:54 192.168.122.209 [57225.196867] [tempesta fw] Open listen socket on: ::1 Apr 26 07:57:54 192.168.122.209 [57225.198406] [tempesta fw] Open listen socket on: 127.0.0.1 Apr 26 07:57:54 192.168.122.209 [57225.244794] [tempesta fw] Tempesta FW is ready Apr 26 07:57:54 192.168.122.209 [57225.386611] [tempesta fw] Warning: purge: not configured, status 403: 127.0.0.2 Apr 26 07:57:55 192.168.122.209 [57225.801744] [tdb] Close table 'client0.tdb' Apr 26 07:57:55 192.168.122.209 [57225.985044] [tdb] Close table 'sessions0.tdb' Apr 26 07:57:58 192.168.122.209 [57229.199079] [tdb] Close table 'cache0.tdb' Apr 26 07:57:58 192.168.122.209 [57229.409620] [tdb] Close table 'filter0.tdb' Apr 26 07:57:58 192.168.122.209 [57229.410049] [tempesta fw] modules are stopped Apr 26 07:57:59 192.168.122.209 [57229.610323] [tempesta fw] exiting... Apr 26 07:57:59 192.168.122.209 [57229.752843] [tdb] Shutdown Tempesta DB Apr 26 07:57:59 192.168.122.209 [57229.938946] End test: cache.test_purge.TestPurgeAcl.test_purge_fail Apr 26 07:57:59 192.168.122.209 [57229.956537] Start test: cache.test_purge.TestPurgeImmediate.test_purge Apr 26 07:58:00 192.168.122.209 [57230.851535] [tdb] Start Tempesta DB Apr 26 07:58:00 192.168.122.209 [57230.987348] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:58:02 192.168.122.209 [57232.701265] [tempesta fw] Configuration processing is completed. Apr 26 07:58:02 192.168.122.209 [57232.759561] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:58:02 192.168.122.209 [57233.179406] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:58:02 192.168.122.209 [57233.218632] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:58:02 192.168.122.209 [57233.244354] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:58:02 192.168.122.209 [57233.292949] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:58:02 192.168.122.209 [57233.332886] [tempesta fw] Tempesta FW is ready Apr 26 07:58:03 192.168.122.209 [57233.578880] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 07:58:03 192.168.122.209 [57234.220267] [tdb] Close table 'client0.tdb' Apr 26 07:58:03 192.168.122.209 [57234.408277] [tdb] Close table 'sessions0.tdb' Apr 26 07:58:07 192.168.122.209 [57237.602375] [tdb] Close table 'cache0.tdb' Apr 26 07:58:07 192.168.122.209 [57237.825015] [tdb] Close table 'filter0.tdb' Apr 26 07:58:07 192.168.122.209 [57237.825445] [tempesta fw] modules are stopped Apr 26 07:58:07 192.168.122.209 [57237.993578] [tempesta fw] exiting... Apr 26 07:58:07 192.168.122.209 [57238.113975] [tdb] Shutdown Tempesta DB Apr 26 07:58:07 192.168.122.209 [57238.350746] End test: cache.test_purge.TestPurgeImmediate.test_purge Apr 26 07:58:07 192.168.122.209 [57238.377727] Start test: cache.test_purge.TestPurgeImmediate.test_purge_get_basic Apr 26 07:58:08 192.168.122.209 [57239.486470] [tdb] Start Tempesta DB Apr 26 07:58:09 192.168.122.209 [57239.622819] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:58:10 192.168.122.209 [57241.469028] [tempesta fw] Configuration processing is completed. Apr 26 07:58:10 192.168.122.209 [57241.518930] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:58:11 192.168.122.209 [57241.939018] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:58:11 192.168.122.209 [57241.966149] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:58:11 192.168.122.209 [57241.992115] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:58:11 192.168.122.209 [57242.037061] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:58:11 192.168.122.209 [57242.093009] [tempesta fw] Tempesta FW is ready Apr 26 07:58:12 192.168.122.209 [57242.902618] [tdb] Close table 'client0.tdb' Apr 26 07:58:12 192.168.122.209 [57243.077898] [tdb] Close table 'sessions0.tdb' Apr 26 07:58:15 192.168.122.209 [57246.342152] [tdb] Close table 'cache0.tdb' Apr 26 07:58:16 192.168.122.209 [57246.570027] [tdb] Close table 'filter0.tdb' Apr 26 07:58:16 192.168.122.209 [57246.570462] [tempesta fw] modules are stopped Apr 26 07:58:16 192.168.122.209 [57246.759408] [tempesta fw] exiting... Apr 26 07:58:16 192.168.122.209 [57246.890471] [tdb] Shutdown Tempesta DB Apr 26 07:58:16 192.168.122.209 [57247.114856] End test: cache.test_purge.TestPurgeImmediate.test_purge_get_basic Apr 26 07:58:16 192.168.122.209 [57247.125539] Start test: cache.test_purge.TestPurgeImmediate.test_purge_get_garbage Apr 26 07:58:17 192.168.122.209 [57248.174084] [tdb] Start Tempesta DB Apr 26 07:58:17 192.168.122.209 [57248.312122] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:58:19 192.168.122.209 [57250.129139] [tempesta fw] Configuration processing is completed. Apr 26 07:58:19 192.168.122.209 [57250.179145] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:58:20 192.168.122.209 [57250.602138] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:58:20 192.168.122.209 [57250.629050] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:58:20 192.168.122.209 [57250.655801] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:58:20 192.168.122.209 [57250.705154] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:58:20 192.168.122.209 [57250.745052] [tempesta fw] Tempesta FW is ready Apr 26 07:58:20 192.168.122.209 [57250.973373] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 07:58:20 192.168.122.209 [57251.100903] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 07:58:21 192.168.122.209 [57251.666852] [tdb] Close table 'client0.tdb' Apr 26 07:58:21 192.168.122.209 [57251.860499] [tdb] Close table 'sessions0.tdb' Apr 26 07:58:24 192.168.122.209 [57255.066387] [tdb] Close table 'cache0.tdb' Apr 26 07:58:24 192.168.122.209 [57255.284991] [tdb] Close table 'filter0.tdb' Apr 26 07:58:24 192.168.122.209 [57255.285430] [tempesta fw] modules are stopped Apr 26 07:58:24 192.168.122.209 [57255.459880] [tempesta fw] exiting... Apr 26 07:58:25 192.168.122.209 [57255.575173] [tdb] Shutdown Tempesta DB Apr 26 07:58:25 192.168.122.209 [57255.815683] End test: cache.test_purge.TestPurgeImmediate.test_purge_get_garbage Apr 26 07:58:25 192.168.122.209 [57255.835070] Start test: cache.test_purge.TestPurgeImmediate.test_purge_get_uncacheable Apr 26 07:58:26 192.168.122.209 [57256.879593] [tdb] Start Tempesta DB Apr 26 07:58:26 192.168.122.209 [57257.041458] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:58:28 192.168.122.209 [57258.901608] [tempesta fw] Configuration processing is completed. Apr 26 07:58:28 192.168.122.209 [57258.961498] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:58:28 192.168.122.209 [57259.424231] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:58:28 192.168.122.209 [57259.453714] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:58:28 192.168.122.209 [57259.483098] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:58:29 192.168.122.209 [57259.525277] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:58:29 192.168.122.209 [57259.569254] [tempesta fw] Tempesta FW is ready Apr 26 07:58:29 192.168.122.209 [57260.399681] [tdb] Close table 'client0.tdb' Apr 26 07:58:30 192.168.122.209 [57260.589164] [tdb] Close table 'sessions0.tdb' Apr 26 07:58:33 192.168.122.209 [57263.788105] [tdb] Close table 'cache0.tdb' Apr 26 07:58:33 192.168.122.209 [57264.039248] [tdb] Close table 'filter0.tdb' Apr 26 07:58:33 192.168.122.209 [57264.039686] [tempesta fw] modules are stopped Apr 26 07:58:33 192.168.122.209 [57264.235169] [tempesta fw] exiting... Apr 26 07:58:33 192.168.122.209 [57264.389104] [tdb] Shutdown Tempesta DB Apr 26 07:58:34 192.168.122.209 [57264.628789] End test: cache.test_purge.TestPurgeImmediate.test_purge_get_uncacheable Apr 26 07:58:34 192.168.122.209 [57264.652799] Start test: cache.test_purge.TestPurgeImmediate.test_purge_get_uncached Apr 26 07:58:35 192.168.122.209 [57265.684031] [tdb] Start Tempesta DB Apr 26 07:58:35 192.168.122.209 [57265.831263] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:58:37 192.168.122.209 [57267.629404] [tempesta fw] Configuration processing is completed. Apr 26 07:58:37 192.168.122.209 [57267.694716] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:58:37 192.168.122.209 [57268.175856] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:58:37 192.168.122.209 [57268.207651] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:58:37 192.168.122.209 [57268.240319] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:58:37 192.168.122.209 [57268.293391] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:58:37 192.168.122.209 [57268.333338] [tempesta fw] Tempesta FW is ready Apr 26 07:58:38 192.168.122.209 [57268.986006] [tdb] Close table 'client0.tdb' Apr 26 07:58:38 192.168.122.209 [57269.177103] [tdb] Close table 'sessions0.tdb' Apr 26 07:58:41 192.168.122.209 [57272.396381] [tdb] Close table 'cache0.tdb' Apr 26 07:58:42 192.168.122.209 [57272.640973] [tdb] Close table 'filter0.tdb' Apr 26 07:58:42 192.168.122.209 [57272.641416] [tempesta fw] modules are stopped Apr 26 07:58:42 192.168.122.209 [57272.862403] [tempesta fw] exiting... Apr 26 07:58:42 192.168.122.209 [57273.017636] [tdb] Shutdown Tempesta DB Apr 26 07:58:42 192.168.122.209 [57273.249517] End test: cache.test_purge.TestPurgeImmediate.test_purge_get_uncached Apr 26 07:58:42 192.168.122.209 [57273.276627] Start test: cache.test_purge.TestPurgeImmediate.test_purge_get_update Apr 26 07:58:43 192.168.122.209 [57274.357944] [tdb] Start Tempesta DB Apr 26 07:58:43 192.168.122.209 [57274.499703] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:58:45 192.168.122.209 [57276.289475] [tempesta fw] Configuration processing is completed. Apr 26 07:58:45 192.168.122.209 [57276.359482] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:58:46 192.168.122.209 [57276.816546] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:58:46 192.168.122.209 [57276.845221] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:58:46 192.168.122.209 [57276.873666] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:58:46 192.168.122.209 [57276.929523] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:58:46 192.168.122.209 [57276.969452] [tempesta fw] Tempesta FW is ready Apr 26 07:58:47 192.168.122.209 [57277.755683] [tdb] Close table 'client0.tdb' Apr 26 07:58:47 192.168.122.209 [57277.950927] [tdb] Close table 'sessions0.tdb' Apr 26 07:58:50 192.168.122.209 [57281.246716] [tdb] Close table 'cache0.tdb' Apr 26 07:58:50 192.168.122.209 [57281.476357] [tdb] Close table 'filter0.tdb' Apr 26 07:58:50 192.168.122.209 [57281.476789] [tempesta fw] modules are stopped Apr 26 07:58:51 192.168.122.209 [57281.684369] [tempesta fw] exiting... Apr 26 07:58:51 192.168.122.209 [57281.813596] [tdb] Shutdown Tempesta DB Apr 26 07:58:51 192.168.122.209 [57282.066251] End test: cache.test_purge.TestPurgeImmediate.test_purge_get_update Apr 26 07:58:51 192.168.122.209 [57282.078234] Start test: cache.test_purge.TestPurgeImmediate.test_purge_get_update_cc Apr 26 07:58:52 192.168.122.209 [57283.118050] [tdb] Start Tempesta DB Apr 26 07:58:52 192.168.122.209 [57283.258653] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:58:54 192.168.122.209 [57285.233834] [tempesta fw] Configuration processing is completed. Apr 26 07:58:54 192.168.122.209 [57285.289438] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:58:55 192.168.122.209 [57285.716125] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:58:55 192.168.122.209 [57285.744590] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:58:55 192.168.122.209 [57285.774286] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:58:55 192.168.122.209 [57285.825607] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:58:55 192.168.122.209 [57285.865543] [tempesta fw] Tempesta FW is ready Apr 26 07:58:56 192.168.122.209 [57286.583443] [tdb] Close table 'client0.tdb' Apr 26 07:58:56 192.168.122.209 [57286.778275] [tdb] Close table 'sessions0.tdb' Apr 26 07:58:59 192.168.122.209 [57290.029104] [tdb] Close table 'cache0.tdb' Apr 26 07:58:59 192.168.122.209 [57290.283854] [tdb] Close table 'filter0.tdb' Apr 26 07:58:59 192.168.122.209 [57290.284275] [tempesta fw] modules are stopped Apr 26 07:58:59 192.168.122.209 [57290.490017] [tempesta fw] exiting... Apr 26 07:59:00 192.168.122.209 [57290.634395] [tdb] Shutdown Tempesta DB Apr 26 07:59:00 192.168.122.209 [57290.863731] End test: cache.test_purge.TestPurgeImmediate.test_purge_get_update_cc Apr 26 07:59:00 192.168.122.209 [57290.874612] Start test: cache.test_purge.TestPurgeImmediate.test_purge_get_update_hdr_del Apr 26 07:59:01 192.168.122.209 [57291.966656] [tdb] Start Tempesta DB Apr 26 07:59:01 192.168.122.209 [57292.098749] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:59:03 192.168.122.209 [57293.925692] [tempesta fw] Configuration processing is completed. Apr 26 07:59:03 192.168.122.209 [57293.978240] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:59:03 192.168.122.209 [57294.395667] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:59:03 192.168.122.209 [57294.422201] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:59:03 192.168.122.209 [57294.450061] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:59:03 192.168.122.209 [57294.505641] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:59:04 192.168.122.209 [57294.549675] [tempesta fw] Tempesta FW is ready Apr 26 07:59:04 192.168.122.209 [57295.306017] [tdb] Close table 'client0.tdb' Apr 26 07:59:04 192.168.122.209 [57295.490766] [tdb] Close table 'sessions0.tdb' Apr 26 07:59:08 192.168.122.209 [57298.659179] [tdb] Close table 'cache0.tdb' Apr 26 07:59:08 192.168.122.209 [57298.921869] [tdb] Close table 'filter0.tdb' Apr 26 07:59:08 192.168.122.209 [57298.922395] [tempesta fw] modules are stopped Apr 26 07:59:08 192.168.122.209 [57299.095529] [tempesta fw] exiting... Apr 26 07:59:08 192.168.122.209 [57299.226684] [tdb] Shutdown Tempesta DB Apr 26 07:59:08 192.168.122.209 [57299.441729] End test: cache.test_purge.TestPurgeImmediate.test_purge_get_update_hdr_del Apr 26 07:59:08 192.168.122.209 [57299.456421] Start test: cache.test_purge.TestPurgeImmediate.test_useless_x_tempesta_cache Apr 26 07:59:09 192.168.122.209 [57300.496285] [tdb] Start Tempesta DB Apr 26 07:59:10 192.168.122.209 [57300.640640] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:59:11 192.168.122.209 [57302.407091] [tempesta fw] Configuration processing is completed. Apr 26 07:59:11 192.168.122.209 [57302.468346] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:59:12 192.168.122.209 [57302.889424] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:59:12 192.168.122.209 [57302.922671] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:59:12 192.168.122.209 [57302.948809] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:59:12 192.168.122.209 [57303.005814] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:59:12 192.168.122.209 [57303.049759] [tempesta fw] Tempesta FW is ready Apr 26 07:59:13 192.168.122.209 [57303.679585] [tdb] Close table 'client0.tdb' Apr 26 07:59:13 192.168.122.209 [57303.870602] [tdb] Close table 'sessions0.tdb' Apr 26 07:59:16 192.168.122.209 [57307.072862] [tdb] Close table 'cache0.tdb' Apr 26 07:59:16 192.168.122.209 [57307.325499] [tdb] Close table 'filter0.tdb' Apr 26 07:59:16 192.168.122.209 [57307.326286] [tempesta fw] modules are stopped Apr 26 07:59:16 192.168.122.209 [57307.499421] [tempesta fw] exiting... Apr 26 07:59:17 192.168.122.209 [57307.623342] [tdb] Shutdown Tempesta DB Apr 26 07:59:17 192.168.122.209 [57307.828626] End test: cache.test_purge.TestPurgeImmediate.test_useless_x_tempesta_cache Apr 26 07:59:17 192.168.122.209 [57307.846050] Start test: cache.test_purge.TestPurgeInvalidate.test_purge Apr 26 07:59:18 192.168.122.209 [57308.839415] [tdb] Start Tempesta DB Apr 26 07:59:18 192.168.122.209 [57308.972462] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:59:20 192.168.122.209 [57310.709903] [tempesta fw] Configuration processing is completed. Apr 26 07:59:20 192.168.122.209 [57310.763201] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:59:20 192.168.122.209 [57311.263849] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:59:20 192.168.122.209 [57311.297903] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:59:20 192.168.122.209 [57311.332261] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:59:20 192.168.122.209 [57311.381921] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:59:20 192.168.122.209 [57311.429861] [tempesta fw] Tempesta FW is ready Apr 26 07:59:21 192.168.122.209 [57311.686043] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 07:59:21 192.168.122.209 [57312.261888] [tdb] Close table 'client0.tdb' Apr 26 07:59:21 192.168.122.209 [57312.459508] [tdb] Close table 'sessions0.tdb' Apr 26 07:59:25 192.168.122.209 [57315.728996] [tdb] Close table 'cache0.tdb' Apr 26 07:59:25 192.168.122.209 [57315.980954] [tdb] Close table 'filter0.tdb' Apr 26 07:59:25 192.168.122.209 [57315.981377] [tempesta fw] modules are stopped Apr 26 07:59:25 192.168.122.209 [57316.162238] [tempesta fw] exiting... Apr 26 07:59:25 192.168.122.209 [57316.283544] [tdb] Shutdown Tempesta DB Apr 26 07:59:25 192.168.122.209 [57316.506511] End test: cache.test_purge.TestPurgeInvalidate.test_purge Apr 26 07:59:25 192.168.122.209 [57316.519878] Start test: cache.test_purge.TestPurgeInvalidate.test_purge_get_basic Apr 26 07:59:27 192.168.122.209 [57317.594322] [tdb] Start Tempesta DB Apr 26 07:59:27 192.168.122.209 [57317.734975] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:59:28 192.168.122.209 [57319.450307] [tempesta fw] Configuration processing is completed. Apr 26 07:59:28 192.168.122.209 [57319.501993] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:59:29 192.168.122.209 [57319.934762] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:59:29 192.168.122.209 [57319.962033] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:59:29 192.168.122.209 [57319.988831] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:59:29 192.168.122.209 [57320.050041] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:59:29 192.168.122.209 [57320.089974] [tempesta fw] Tempesta FW is ready Apr 26 07:59:30 192.168.122.209 [57320.857689] [tdb] Close table 'client0.tdb' Apr 26 07:59:30 192.168.122.209 [57321.064787] [tdb] Close table 'sessions0.tdb' Apr 26 07:59:33 192.168.122.209 [57324.265510] [tdb] Close table 'cache0.tdb' Apr 26 07:59:33 192.168.122.209 [57324.490807] [tdb] Close table 'filter0.tdb' Apr 26 07:59:33 192.168.122.209 [57324.491248] [tempesta fw] modules are stopped Apr 26 07:59:34 192.168.122.209 [57324.709928] [tempesta fw] exiting... Apr 26 07:59:34 192.168.122.209 [57324.873704] [tdb] Shutdown Tempesta DB Apr 26 07:59:34 192.168.122.209 [57325.080137] End test: cache.test_purge.TestPurgeInvalidate.test_purge_get_basic Apr 26 07:59:34 192.168.122.209 [57325.090399] Start test: cache.test_purge.TestPurgeInvalidate.test_purge_get_garbage Apr 26 07:59:35 192.168.122.209 [57326.169233] [tdb] Start Tempesta DB Apr 26 07:59:35 192.168.122.209 [57326.315132] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:59:37 192.168.122.209 [57328.110153] [tempesta fw] Configuration processing is completed. Apr 26 07:59:37 192.168.122.209 [57328.191030] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:59:38 192.168.122.209 [57328.658708] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:59:38 192.168.122.209 [57328.688621] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:59:38 192.168.122.209 [57328.717335] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:59:38 192.168.122.209 [57328.782193] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:59:38 192.168.122.209 [57328.830097] [tempesta fw] Tempesta FW is ready Apr 26 07:59:38 192.168.122.209 [57329.069198] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 07:59:38 192.168.122.209 [57329.182630] [tempesta fw] Warning: purge: success, status 200: 127.0.0.2 Apr 26 07:59:39 192.168.122.209 [57329.741099] [tdb] Close table 'client0.tdb' Apr 26 07:59:39 192.168.122.209 [57329.931875] [tdb] Close table 'sessions0.tdb' Apr 26 07:59:42 192.168.122.209 [57333.153873] [tdb] Close table 'cache0.tdb' Apr 26 07:59:42 192.168.122.209 [57333.373106] [tdb] Close table 'filter0.tdb' Apr 26 07:59:42 192.168.122.209 [57333.373551] [tempesta fw] modules are stopped Apr 26 07:59:43 192.168.122.209 [57333.553518] [tempesta fw] exiting... Apr 26 07:59:43 192.168.122.209 [57333.670230] [tdb] Shutdown Tempesta DB Apr 26 07:59:43 192.168.122.209 [57333.885597] End test: cache.test_purge.TestPurgeInvalidate.test_purge_get_garbage Apr 26 07:59:43 192.168.122.209 [57333.904325] Start test: cache.test_purge.TestPurgeInvalidate.test_purge_get_uncacheable Apr 26 07:59:44 192.168.122.209 [57334.966217] [tdb] Start Tempesta DB Apr 26 07:59:44 192.168.122.209 [57335.124968] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:59:46 192.168.122.209 [57336.862406] [tempesta fw] Configuration processing is completed. Apr 26 07:59:46 192.168.122.209 [57336.913508] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:59:46 192.168.122.209 [57337.348948] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:59:46 192.168.122.209 [57337.381673] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:59:46 192.168.122.209 [57337.408462] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:59:46 192.168.122.209 [57337.466255] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:59:46 192.168.122.209 [57337.510211] [tempesta fw] Tempesta FW is ready Apr 26 07:59:47 192.168.122.209 [57338.350964] [tdb] Close table 'client0.tdb' Apr 26 07:59:48 192.168.122.209 [57338.528626] [tdb] Close table 'sessions0.tdb' Apr 26 07:59:51 192.168.122.209 [57341.702302] [tdb] Close table 'cache0.tdb' Apr 26 07:59:51 192.168.122.209 [57341.944207] [tdb] Close table 'filter0.tdb' Apr 26 07:59:51 192.168.122.209 [57341.944642] [tempesta fw] modules are stopped Apr 26 07:59:51 192.168.122.209 [57342.155218] [tempesta fw] exiting... Apr 26 07:59:51 192.168.122.209 [57342.338084] [tdb] Shutdown Tempesta DB Apr 26 07:59:52 192.168.122.209 [57342.556805] End test: cache.test_purge.TestPurgeInvalidate.test_purge_get_uncacheable Apr 26 07:59:52 192.168.122.209 [57342.575207] Start test: cache.test_purge.TestPurgeInvalidate.test_purge_get_uncached Apr 26 07:59:53 192.168.122.209 [57343.617854] [tdb] Start Tempesta DB Apr 26 07:59:53 192.168.122.209 [57343.760004] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 07:59:55 192.168.122.209 [57345.554271] [tempesta fw] Configuration processing is completed. Apr 26 07:59:55 192.168.122.209 [57345.607645] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 07:59:55 192.168.122.209 [57346.028810] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 07:59:55 192.168.122.209 [57346.055881] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 07:59:55 192.168.122.209 [57346.082433] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 07:59:55 192.168.122.209 [57346.154358] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 07:59:55 192.168.122.209 [57346.194314] [tempesta fw] Tempesta FW is ready Apr 26 07:59:56 192.168.122.209 [57346.821983] [tdb] Close table 'client0.tdb' Apr 26 07:59:56 192.168.122.209 [57346.997122] [tdb] Close table 'sessions0.tdb' Apr 26 07:59:59 192.168.122.209 [57350.199920] [tdb] Close table 'cache0.tdb' Apr 26 07:59:59 192.168.122.209 [57350.437381] [tdb] Close table 'filter0.tdb' Apr 26 07:59:59 192.168.122.209 [57350.437793] [tempesta fw] modules are stopped Apr 26 08:00:00 192.168.122.209 [57350.606960] [tempesta fw] exiting... Apr 26 08:00:00 192.168.122.209 [57350.710084] [tdb] Shutdown Tempesta DB Apr 26 08:00:00 192.168.122.209 [57350.956146] End test: cache.test_purge.TestPurgeInvalidate.test_purge_get_uncached Apr 26 08:00:00 192.168.122.209 [57350.975956] Start test: cache.test_purge.TestPurgeInvalidate.test_purge_get_update Apr 26 08:00:01 192.168.122.209 [57351.996889] [tdb] Start Tempesta DB Apr 26 08:00:01 192.168.122.209 [57352.157312] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:00:03 192.168.122.209 [57353.994757] [tempesta fw] Configuration processing is completed. Apr 26 08:00:03 192.168.122.209 [57354.050275] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:00:04 192.168.122.209 [57354.552093] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:00:04 192.168.122.209 [57354.581490] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:00:04 192.168.122.209 [57354.610184] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:00:04 192.168.122.209 [57354.678463] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:00:04 192.168.122.209 [57354.722434] [tempesta fw] Tempesta FW is ready Apr 26 08:00:04 192.168.122.209 [57355.424473] [tdb] Close table 'client0.tdb' Apr 26 08:00:05 192.168.122.209 [57355.631646] [tdb] Close table 'sessions0.tdb' Apr 26 08:00:08 192.168.122.209 [57358.861897] [tdb] Close table 'cache0.tdb' Apr 26 08:00:08 192.168.122.209 [57359.116243] [tdb] Close table 'filter0.tdb' Apr 26 08:00:08 192.168.122.209 [57359.116659] [tempesta fw] modules are stopped Apr 26 08:00:08 192.168.122.209 [57359.327835] [tempesta fw] exiting... Apr 26 08:00:08 192.168.122.209 [57359.430379] [tdb] Shutdown Tempesta DB Apr 26 08:00:09 192.168.122.209 [57359.657538] End test: cache.test_purge.TestPurgeInvalidate.test_purge_get_update Apr 26 08:00:09 192.168.122.209 [57359.693309] Start test: cache.test_purge.TestPurgeInvalidate.test_purge_get_update_cc Apr 26 08:00:10 192.168.122.209 [57360.788774] [tdb] Start Tempesta DB Apr 26 08:00:10 192.168.122.209 [57360.925195] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:00:12 192.168.122.209 [57362.738800] [tempesta fw] Configuration processing is completed. Apr 26 08:00:12 192.168.122.209 [57362.789315] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:00:12 192.168.122.209 [57363.208813] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:00:12 192.168.122.209 [57363.235724] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:00:12 192.168.122.209 [57363.262027] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:00:12 192.168.122.209 [57363.314590] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:00:12 192.168.122.209 [57363.359878] [tempesta fw] Tempesta FW is ready Apr 26 08:00:13 192.168.122.209 [57364.093504] [tdb] Close table 'client0.tdb' Apr 26 08:00:13 192.168.122.209 [57364.271507] [tdb] Close table 'sessions0.tdb' Apr 26 08:00:16 192.168.122.209 [57367.504742] [tdb] Close table 'cache0.tdb' Apr 26 08:00:17 192.168.122.209 [57367.741076] [tdb] Close table 'filter0.tdb' Apr 26 08:00:17 192.168.122.209 [57367.741545] [tempesta fw] modules are stopped Apr 26 08:00:17 192.168.122.209 [57367.898999] [tempesta fw] exiting... Apr 26 08:00:17 192.168.122.209 [57368.003488] [tdb] Shutdown Tempesta DB Apr 26 08:00:17 192.168.122.209 [57368.228492] End test: cache.test_purge.TestPurgeInvalidate.test_purge_get_update_cc Apr 26 08:00:17 192.168.122.209 [57368.252400] Start test: cache.test_purge.TestPurgeInvalidate.test_purge_get_update_hdr_del Apr 26 08:00:18 192.168.122.209 [57369.329942] [tdb] Start Tempesta DB Apr 26 08:00:18 192.168.122.209 [57369.479594] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:00:20 192.168.122.209 [57371.338667] [tempesta fw] Configuration processing is completed. Apr 26 08:00:20 192.168.122.209 [57371.389280] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:00:21 192.168.122.209 [57371.816626] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:00:21 192.168.122.209 [57371.846378] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:00:21 192.168.122.209 [57371.873905] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:00:21 192.168.122.209 [57371.918685] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:00:21 192.168.122.209 [57371.966622] [tempesta fw] Tempesta FW is ready Apr 26 08:00:22 192.168.122.209 [57372.692622] [tdb] Close table 'client0.tdb' Apr 26 08:00:22 192.168.122.209 [57372.882352] [tdb] Close table 'sessions0.tdb' Apr 26 08:00:25 192.168.122.209 [57376.084312] [tdb] Close table 'cache0.tdb' Apr 26 08:00:25 192.168.122.209 [57376.322246] [tdb] Close table 'filter0.tdb' Apr 26 08:00:25 192.168.122.209 [57376.322695] [tempesta fw] modules are stopped Apr 26 08:00:25 192.168.122.209 [57376.502546] [tempesta fw] exiting... Apr 26 08:00:26 192.168.122.209 [57376.638665] [tdb] Shutdown Tempesta DB Apr 26 08:00:26 192.168.122.209 [57376.859101] End test: cache.test_purge.TestPurgeInvalidate.test_purge_get_update_hdr_del Apr 26 08:00:26 192.168.122.209 [57376.884534] Start test: cache.test_purge.TestPurgeInvalidate.test_useless_x_tempesta_cache Apr 26 08:00:27 192.168.122.209 [57377.961550] [tdb] Start Tempesta DB Apr 26 08:00:27 192.168.122.209 [57378.109584] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:00:29 192.168.122.209 [57379.938776] [tempesta fw] Configuration processing is completed. Apr 26 08:00:29 192.168.122.209 [57379.994418] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:00:29 192.168.122.209 [57380.422702] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:00:29 192.168.122.209 [57380.449359] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:00:29 192.168.122.209 [57380.475299] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:00:29 192.168.122.209 [57380.518823] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:00:30 192.168.122.209 [57380.582730] [tempesta fw] Tempesta FW is ready Apr 26 08:00:30 192.168.122.209 [57381.269816] [tdb] Close table 'client0.tdb' Apr 26 08:00:30 192.168.122.209 [57381.476769] [tdb] Close table 'sessions0.tdb' Apr 26 08:00:34 192.168.122.209 [57384.610723] [tdb] Close table 'cache0.tdb' Apr 26 08:00:34 192.168.122.209 [57384.866171] [tdb] Close table 'filter0.tdb' Apr 26 08:00:34 192.168.122.209 [57384.866595] [tempesta fw] modules are stopped Apr 26 08:00:34 192.168.122.209 [57385.101252] [tempesta fw] exiting... Apr 26 08:00:34 192.168.122.209 [57385.228416] [tdb] Shutdown Tempesta DB Apr 26 08:00:34 192.168.122.209 [57385.435525] End test: cache.test_purge.TestPurgeInvalidate.test_useless_x_tempesta_cache Apr 26 08:00:34 192.168.122.209 [57385.448126] Start test: cache.test_purge_hch.HeavyChunkedPurgeTest.test_0_purge_non_hch Apr 26 08:00:35 192.168.122.209 [57386.492574] [tdb] Start Tempesta DB Apr 26 08:00:36 192.168.122.209 [57386.642416] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:00:37 192.168.122.209 [57388.086937] [tempesta fw] Configuration processing is completed. Apr 26 08:00:37 192.168.122.209 [57388.139584] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:00:38 192.168.122.209 [57388.552857] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:00:38 192.168.122.209 [57388.579193] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:00:38 192.168.122.209 [57388.609708] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:00:38 192.168.122.209 [57388.658889] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:00:38 192.168.122.209 [57388.698831] [tempesta fw] Tempesta FW is ready Apr 26 08:00:38 192.168.122.209 [57389.310734] [tdb] Close table 'client0.tdb' Apr 26 08:00:38 192.168.122.209 [57389.498886] [tdb] Close table 'sessions0.tdb' Apr 26 08:00:42 192.168.122.209 [57392.673988] [tdb] Close table 'cache0.tdb' Apr 26 08:00:42 192.168.122.209 [57392.883808] [tdb] Close table 'filter0.tdb' Apr 26 08:00:42 192.168.122.209 [57392.884257] [tempesta fw] modules are stopped Apr 26 08:00:42 192.168.122.209 [57393.094577] [tempesta fw] exiting... Apr 26 08:00:42 192.168.122.209 [57393.241349] [tdb] Shutdown Tempesta DB Apr 26 08:00:42 192.168.122.209 [57393.477875] End test: cache.test_purge_hch.HeavyChunkedPurgeTest.test_0_purge_non_hch Apr 26 08:00:42 192.168.122.209 [57393.490791] Start test: cache.test_purge_hch.HeavyChunkedPurgeTest.test_1_purge_hch Apr 26 08:00:44 192.168.122.209 [57394.613701] [tdb] Start Tempesta DB Apr 26 08:00:44 192.168.122.209 [57394.749364] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:00:45 192.168.122.209 [57396.211099] [tempesta fw] Configuration processing is completed. Apr 26 08:00:45 192.168.122.209 [57396.263344] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:00:46 192.168.122.209 [57396.694223] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:00:46 192.168.122.209 [57396.730025] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:00:46 192.168.122.209 [57396.756117] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:00:46 192.168.122.209 [57396.798937] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:00:46 192.168.122.209 [57396.854939] [tempesta fw] Tempesta FW is ready Apr 26 08:00:46 192.168.122.209 [57397.461757] [tdb] Close table 'client0.tdb' Apr 26 08:00:47 192.168.122.209 [57397.643174] [tdb] Close table 'sessions0.tdb' Apr 26 08:00:50 192.168.122.209 [57400.834259] [tdb] Close table 'cache0.tdb' Apr 26 08:00:50 192.168.122.209 [57401.074783] [tdb] Close table 'filter0.tdb' Apr 26 08:00:50 192.168.122.209 [57401.075241] [tempesta fw] modules are stopped Apr 26 08:00:50 192.168.122.209 [57401.238532] [tempesta fw] exiting... Apr 26 08:00:50 192.168.122.209 [57401.387670] [tdb] Shutdown Tempesta DB Apr 26 08:00:51 192.168.122.209 [57401.601334] End test: cache.test_purge_hch.HeavyChunkedPurgeTest.test_1_purge_hch Apr 26 08:00:51 192.168.122.209 [57401.624387] Start test: cache.test_purge_resp_hch.HeavyChunkedPurgeRespTest.test_0_purge_resp_non_hch Apr 26 08:00:52 192.168.122.209 [57402.637637] [tdb] Start Tempesta DB Apr 26 08:00:52 192.168.122.209 [57402.777914] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:00:53 192.168.122.209 [57404.227145] [tempesta fw] Configuration processing is completed. Apr 26 08:00:53 192.168.122.209 [57404.284460] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:00:54 192.168.122.209 [57404.703926] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:00:54 192.168.122.209 [57404.743372] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:00:54 192.168.122.209 [57404.770356] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:00:54 192.168.122.209 [57404.811029] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:00:54 192.168.122.209 [57404.851040] [tempesta fw] Tempesta FW is ready Apr 26 08:01:16 192.168.122.209 [57426.643908] [tdb] Close table 'client0.tdb' Apr 26 08:01:16 192.168.122.209 [57426.831061] [tdb] Close table 'sessions0.tdb' Apr 26 08:01:19 192.168.122.209 [57430.063086] [tdb] Close table 'cache0.tdb' Apr 26 08:01:19 192.168.122.209 [57430.298918] [tdb] Close table 'filter0.tdb' Apr 26 08:01:19 192.168.122.209 [57430.299390] [tempesta fw] modules are stopped Apr 26 08:01:19 192.168.122.209 [57430.519481] [tempesta fw] exiting... Apr 26 08:01:20 192.168.122.209 [57430.639388] [tdb] Shutdown Tempesta DB Apr 26 08:01:20 192.168.122.209 [57430.873803] End test: cache.test_purge_resp_hch.HeavyChunkedPurgeRespTest.test_0_purge_resp_non_hch Apr 26 08:01:20 192.168.122.209 [57430.884439] Start test: encoding.test_encoding.TestH1BothTEAndCE.test Apr 26 08:01:21 192.168.122.209 [57432.012694] [tdb] Start Tempesta DB Apr 26 08:01:21 192.168.122.209 [57432.154600] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:01:22 192.168.122.209 [57433.303944] [tempesta fw] Configuration processing is completed. Apr 26 08:01:22 192.168.122.209 [57433.355383] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:01:23 192.168.122.209 [57433.786165] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:01:23 192.168.122.209 [57433.820260] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:01:23 192.168.122.209 [57433.845966] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:01:23 192.168.122.209 [57433.919398] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:01:23 192.168.122.209 [57433.959361] [tempesta fw] Tempesta FW is ready Apr 26 08:01:23 192.168.122.209 [57434.153686] [tempesta fw] Warning: Content-Encoding and Transfer-Encoding other than chunked not allowed to be in same response. Apr 26 08:01:23 192.168.122.209 [57434.155085] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 08:01:24 192.168.122.209 [57434.563216] [tdb] Close table 'client0.tdb' Apr 26 08:01:24 192.168.122.209 [57434.772488] [tdb] Close table 'sessions0.tdb' Apr 26 08:01:27 192.168.122.209 [57437.964133] [tdb] Close table 'cache0.tdb' Apr 26 08:01:27 192.168.122.209 [57438.219905] [tdb] Close table 'filter0.tdb' Apr 26 08:01:27 192.168.122.209 [57438.220363] [tempesta fw] modules are stopped Apr 26 08:01:27 192.168.122.209 [57438.403498] [tempesta fw] exiting... Apr 26 08:01:27 192.168.122.209 [57438.505776] [tdb] Shutdown Tempesta DB Apr 26 08:01:28 192.168.122.209 [57438.775014] End test: encoding.test_encoding.TestH1BothTEAndCE.test Apr 26 08:01:28 192.168.122.209 [57438.803061] Start test: encoding.test_encoding.TestH1ChunkedNonCacheable.test Apr 26 08:01:29 192.168.122.209 [57439.857041] [tdb] Start Tempesta DB Apr 26 08:01:29 192.168.122.209 [57439.987754] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:01:30 192.168.122.209 [57441.095590] [tempesta fw] Configuration processing is completed. Apr 26 08:01:30 192.168.122.209 [57441.146778] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:01:30 192.168.122.209 [57441.175918] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 08:01:30 192.168.122.209 [57441.203510] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 08:01:30 192.168.122.209 [57441.255575] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:01:30 192.168.122.209 [57441.315490] [tempesta fw] Tempesta FW is ready Apr 26 08:01:31 192.168.122.209 [57442.006012] [tdb] Close table 'client0.tdb' Apr 26 08:01:31 192.168.122.209 [57442.205204] [tdb] Close table 'sessions0.tdb' Apr 26 08:01:31 192.168.122.209 [57442.438041] [tdb] Close table 'filter0.tdb' Apr 26 08:01:31 192.168.122.209 [57442.438490] [tempesta fw] modules are stopped Apr 26 08:01:32 192.168.122.209 [57442.596355] [tempesta fw] exiting... Apr 26 08:01:32 192.168.122.209 [57442.691475] [tdb] Shutdown Tempesta DB Apr 26 08:01:32 192.168.122.209 [57442.927662] End test: encoding.test_encoding.TestH1ChunkedNonCacheable.test Apr 26 08:01:32 192.168.122.209 [57442.950943] Start test: encoding.test_encoding.TestH1ChunkedWithLongBodyAndTrailer.test Apr 26 08:01:33 192.168.122.209 [57444.030996] [tdb] Start Tempesta DB Apr 26 08:01:33 192.168.122.209 [57444.159732] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:01:34 192.168.122.209 [57444.820861] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [57444.820861] Maybe that's fine, but it's worth checking the [57444.820861] config - if there is no relations between the [57444.820861] names, then host name confusion attack is possible. Apr 26 08:01:34 192.168.122.209 [57444.919604] [tempesta fw] Configuration processing is completed. Apr 26 08:01:34 192.168.122.209 [57444.970263] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:01:34 192.168.122.209 [57445.381777] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:01:34 192.168.122.209 [57445.412766] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:01:34 192.168.122.209 [57445.442380] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:01:34 192.168.122.209 [57445.511612] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:01:34 192.168.122.209 [57445.513472] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:01:35 192.168.122.209 [57445.551556] [tempesta fw] Tempesta FW is ready Apr 26 08:01:52 192.168.122.209 [57463.490006] swapper/3: page allocation failure: order:9, mode:0x40a20(GFP_ATOMIC|__GFP_COMP), nodemask=(null),cpuset=/,mems_allowed=0 Apr 26 08:01:52 192.168.122.209 [57463.491138] CPU: 3 PID: 0 Comm: swapper/3 Tainted: G OE 5.10.35.tfw-39c65d3-debug #1 Apr 26 08:01:52 192.168.122.209 [57463.491936] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 Apr 26 08:01:52 192.168.122.209 [57463.492769] Call Trace: Apr 26 08:01:52 192.168.122.209 [57463.493004] Apr 26 08:01:52 192.168.122.209 [57463.493244] dump_stack+0x96/0xc4 Apr 26 08:01:52 192.168.122.209 [57463.493558] warn_alloc.cold+0x87/0x12a Apr 26 08:01:52 192.168.122.209 [57463.493927] ? zone_watermark_ok_safe+0x140/0x140 Apr 26 08:01:52 192.168.122.209 [57463.494362] ? __kasan_check_read+0x11/0x20 Apr 26 08:01:52 192.168.122.209 [57463.494757] ? wakeup_kswapd+0xba/0x290 Apr 26 08:01:52 192.168.122.209 [57463.495104] ? __zone_watermark_ok+0x270/0x270 Apr 26 08:01:52 192.168.122.209 [57463.495509] ? wake_all_kswapds+0xf4/0x140 Apr 26 08:01:52 192.168.122.209 [57463.495895] ? __alloc_pages_slowpath.constprop.0+0x11f4/0x1390 Apr 26 08:01:52 192.168.122.209 [57463.496438] __alloc_pages_slowpath.constprop.0+0x1359/0x1390 Apr 26 08:01:52 192.168.122.209 [57463.496952] ? warn_alloc+0x120/0x120 Apr 26 08:01:52 192.168.122.209 [57463.497296] ? enqueue_to_backlog+0x430/0x430 Apr 26 08:01:52 192.168.122.209 [57463.497703] ? __zone_watermark_ok+0x270/0x270 Apr 26 08:01:52 192.168.122.209 [57463.498114] __alloc_pages_nodemask+0x509/0x540 Apr 26 08:01:52 192.168.122.209 [57463.498526] ? __alloc_pages_slowpath.constprop.0+0x1390/0x1390 Apr 26 08:01:52 192.168.122.209 [57463.499052] ? netdev_core_pick_tx+0xb0/0x120 Apr 26 08:01:52 192.168.122.209 [57463.499469] ? __flush_tlb_all+0x37/0x50 Apr 26 08:01:52 192.168.122.209 [57463.499829] ? __kernel_map_pages+0x108/0x180 Apr 26 08:01:52 192.168.122.209 [57463.500223] alloc_pages_current+0x96/0x140 Apr 26 08:01:52 192.168.122.209 [57463.500609] __get_free_pages+0x12/0x60 Apr 26 08:01:52 192.168.122.209 [57463.500997] tfw_pool_alloc_pages+0x9b/0xc0 [tempesta_fw] Apr 26 08:01:52 192.168.122.209 [57463.501512] __tfw_pool_realloc+0x123/0x1a0 [tempesta_fw] Apr 26 08:01:52 192.168.122.209 [57463.502022] __str_grow_tree+0x89/0x210 [tempesta_fw] Apr 26 08:01:52 192.168.122.209 [57463.502506] tfw_str_add_compound+0x33/0x40 [tempesta_fw] Apr 26 08:01:52 192.168.122.209 [57463.503016] __resp_parse_body+0x421/0xb50 [tempesta_fw] Apr 26 08:01:52 192.168.122.209 [57463.503521] tfw_http_parse_resp+0x15e8/0x197d0 [tempesta_fw] Apr 26 08:01:52 192.168.122.209 [57463.504062] ? __resp_parse_body+0xb50/0xb50 [tempesta_fw] Apr 26 08:01:52 192.168.122.209 [57463.504580] ss_skb_process+0x270/0x2f0 [tempesta_fw] Apr 26 08:01:52 192.168.122.209 [57463.505059] ? __resp_parse_body+0xb50/0xb50 [tempesta_fw] Apr 26 08:01:52 192.168.122.209 [57463.505587] ? tfw_sock_srv_exit+0x30/0x30 [tempesta_fw] Apr 26 08:01:52 192.168.122.209 [57463.506062] ? __alloc_pages_nodemask+0x2db/0x540 Apr 26 08:01:52 192.168.122.209 [57463.506515] tfw_http_msg_process_generic+0x282/0xc70 [tempesta_fw] Apr 26 08:01:52 192.168.122.209 [57463.507100] ? tfw_http_req_process+0x11a0/0x11a0 [tempesta_fw] Apr 26 08:01:52 192.168.122.209 [57463.507633] ? __kasan_check_write+0x14/0x20 Apr 26 08:01:52 192.168.122.209 [57463.508020] ? pg_skb_alloc+0x60e/0x680 Apr 26 08:01:52 192.168.122.209 [57463.508371] ? __kasan_check_write+0x14/0x20 Apr 26 08:01:52 192.168.122.209 [57463.508765] ? __alloc_skb+0x278/0x350 Apr 26 08:01:52 192.168.122.209 [57463.509106] ? __kasan_check_write+0x14/0x20 Apr 26 08:01:52 192.168.122.209 [57463.509523] ? __coalesce_frag+0x136/0x370 [tempesta_fw] Apr 26 08:01:52 192.168.122.209 [57463.510022] tfw_http_msg_process+0x80/0xc0 [tempesta_fw] Apr 26 08:01:52 192.168.122.209 [57463.510510] ? skb_release_data+0x8c/0x320 Apr 26 08:01:52 192.168.122.209 [57463.510904] tfw_connection_recv+0x12e/0x250 [tempesta_fw] Apr 26 08:01:52 192.168.122.209 [57463.511417] ? tfw_connection_send+0x70/0x70 [tempesta_fw] Apr 26 08:01:52 192.168.122.209 [57463.511933] ? ss_skb_unroll+0x3d6/0x540 [tempesta_fw] Apr 26 08:01:52 192.168.122.209 [57463.512435] ss_tcp_process_data+0x436/0x8b0 [tempesta_fw] Apr 26 08:01:52 192.168.122.209 [57463.512952] ? __sk_close_locked+0x100/0x100 [tempesta_fw] Apr 26 08:01:52 192.168.122.209 [57463.513459] ? mod_timer+0x10/0x20 Apr 26 08:01:52 192.168.122.209 [57463.513769] ? sk_reset_timer+0x1a/0x70 Apr 26 08:01:52 192.168.122.209 [57463.514148] ss_tcp_data_ready+0x7b/0x150 [tempesta_fw] Apr 26 08:01:52 192.168.122.209 [57463.514631] tcp_data_ready+0x73/0x210 Apr 26 08:01:52 192.168.122.209 [57463.514971] tcp_rcv_established+0x95b/0xb40 Apr 26 08:01:52 192.168.122.209 [57463.515361] ? tcp_data_queue+0x1d80/0x1d80 Apr 26 08:01:52 192.168.122.209 [57463.515741] ? __kasan_check_read+0x11/0x20 Apr 26 08:01:52 192.168.122.209 [57463.516121] tcp_v4_do_rcv+0x25f/0x360 Apr 26 08:01:52 192.168.122.209 [57463.516463] tcp_v4_rcv+0x1600/0x1770 Apr 26 08:01:52 192.168.122.209 [57463.516799] ? tcp_v4_early_demux+0x2f0/0x2f0 Apr 26 08:01:52 192.168.122.209 [57463.517200] ip_protocol_deliver_rcu+0x46/0x2e0 Apr 26 08:01:52 192.168.122.209 [57463.517613] ip_local_deliver_finish+0xc6/0xe0 Apr 26 08:01:52 192.168.122.209 [57463.518013] ip_local_deliver+0x1f5/0x210 Apr 26 08:01:52 192.168.122.209 [57463.518381] ? ip_local_deliver_finish+0xe0/0xe0 Apr 26 08:01:52 192.168.122.209 [57463.518811] ? nf_nat_inet_fn+0x2b3/0x440 [nf_nat] Apr 26 08:01:52 192.168.122.209 [57463.519242] ? ip_protocol_deliver_rcu+0x2e0/0x2e0 Apr 26 08:01:52 192.168.122.209 [57463.519677] ? ip_rcv_finish_core.constprop.0+0x17c/0x890 Apr 26 08:01:52 192.168.122.209 [57463.520162] ip_rcv_finish+0xcf/0xf0 Apr 26 08:01:52 192.168.122.209 [57463.520496] ip_rcv+0x16d/0x180 Apr 26 08:01:52 192.168.122.209 [57463.520786] ? ip_local_deliver+0x210/0x210 Apr 26 08:01:52 192.168.122.209 [57463.521168] ? pvclock_clocksource_read+0xe1/0x1a0 Apr 26 08:01:52 192.168.122.209 [57463.521602] ? ip_rcv_finish_core.constprop.0+0x890/0x890 Apr 26 08:01:52 192.168.122.209 [57463.522120] ? reweight_entity+0x1d7/0x250 Apr 26 08:01:52 192.168.122.209 [57463.522499] ? ip_local_deliver+0x210/0x210 Apr 26 08:01:52 192.168.122.209 [57463.522877] __netif_receive_skb_one_core+0x132/0x140 Apr 26 08:01:52 192.168.122.209 [57463.523335] ? napi_gro_receive+0x260/0x260 Apr 26 08:01:52 192.168.122.209 [57463.523716] ? __kasan_check_write+0x14/0x20 Apr 26 08:01:52 192.168.122.209 [57463.524121] ? _raw_spin_lock+0x7b/0xd0 Apr 26 08:01:52 192.168.122.209 [57463.524475] __netif_receive_skb+0x26/0xb0 Apr 26 08:01:52 192.168.122.209 [57463.524851] ? generic_exec_single+0xb1/0x170 Apr 26 08:01:52 192.168.122.209 [57463.525246] process_backlog+0xfe/0x290 Apr 26 08:01:52 192.168.122.209 [57463.525601] net_rx_action+0x287/0x6b0 Apr 26 08:01:52 192.168.122.209 [57463.525940] ? napi_complete_done+0x2c0/0x2c0 Apr 26 08:01:52 192.168.122.209 [57463.526344] ? switch_fpu_return+0x120/0x120 Apr 26 08:01:52 192.168.122.209 [57463.526731] __do_softirq+0xfe/0x383 Apr 26 08:01:52 192.168.122.209 [57463.527060] asm_call_irq_on_stack+0xf/0x20 Apr 26 08:01:52 192.168.122.209 [57463.527439] Apr 26 08:01:52 192.168.122.209 [57463.527644] do_softirq_own_stack+0x3d/0x50 Apr 26 08:01:52 192.168.122.209 [57463.528029] irq_exit_rcu+0xc7/0x120 Apr 26 08:01:52 192.168.122.209 [57463.528365] sysvec_call_function_single+0x3a/0x90 Apr 26 08:01:52 192.168.122.209 [57463.528795] asm_sysvec_call_function_single+0x12/0x20 Apr 26 08:01:53 192.168.122.209 [57463.529255] RIP: 0010:native_safe_halt+0xe/0x10 Apr 26 08:01:53 192.168.122.209 [57463.529670] Code: 49 8b 04 24 a8 08 0f 85 71 ff ff ff e9 0f ff ff ff cc cc cc cc cc cc cc cc cc cc cc e9 07 00 00 00 0f 00 2d d4 62 51 00 fb f4 90 e9 07 00 00 00 0f 00 2d c4 62 51 00 f4 c3 cc cc 0f 1f 44 00 Apr 26 08:01:53 192.168.122.209 [57463.531289] RSP: 0018:ffff888100f47db8 EFLAGS: 00000202 Apr 26 08:01:53 192.168.122.209 [57463.531773] RAX: ffffffffb63426a0 RBX: ffff888100f28040 RCX: ffffffffb632c475 Apr 26 08:01:53 192.168.122.209 [57463.532424] RDX: 0000000019463f06 RSI: 0000000000000004 RDI: ffff888147fb5040 Apr 26 08:01:53 192.168.122.209 [57463.533052] RBP: ffff888100f47dc0 R08: 0000000000000001 R09: ffff888147fb5043 Apr 26 08:01:53 192.168.122.209 [57463.533698] R10: ffffed1028ff6a08 R11: 0000000000000001 R12: 0000000000000003 Apr 26 08:01:53 192.168.122.209 [57463.534324] R13: ffffffffb7ae9360 R14: 0000000000000000 R15: 0000000000000000 Apr 26 08:01:53 192.168.122.209 [57463.534957] ? __cpuidle_text_start+0x8/0x8 Apr 26 08:01:53 192.168.122.209 [57463.535343] ? rcu_eqs_enter.constprop.0+0x85/0xa0 Apr 26 08:01:53 192.168.122.209 [57463.535776] ? default_idle+0xe/0x20 Apr 26 08:01:53 192.168.122.209 [57463.536101] arch_cpu_idle+0x15/0x20 Apr 26 08:01:53 192.168.122.209 [57463.536432] default_idle_call+0x66/0x160 Apr 26 08:01:53 192.168.122.209 [57463.536797] do_idle+0x36f/0x430 Apr 26 08:01:53 192.168.122.209 [57463.537095] ? asm_sysvec_call_function_single+0x12/0x20 Apr 26 08:01:53 192.168.122.209 [57463.537574] ? arch_cpu_idle_exit+0x40/0x40 Apr 26 08:01:53 192.168.122.209 [57463.537952] cpu_startup_entry+0x20/0x30 Apr 26 08:01:53 192.168.122.209 [57463.538317] start_secondary+0x1c1/0x210 Apr 26 08:01:53 192.168.122.209 [57463.538678] ? set_cpu_sibling_map+0xd70/0xd70 Apr 26 08:01:53 192.168.122.209 [57463.539082] ? set_bringup_idt_handler.constprop.0+0x84/0x90 Apr 26 08:01:53 192.168.122.209 [57463.539592] ? start_cpu0+0xc/0xc Apr 26 08:01:53 192.168.122.209 [57463.539900] secondary_startup_64_no_verify+0xb0/0xbb Apr 26 08:01:53 192.168.122.209 [57463.540390] Mem-Info: Apr 26 08:01:53 192.168.122.209 [57463.540617] active_anon:32054 inactive_anon:98386 isolated_anon:0 [57463.540617] active_file:101758 inactive_file:105508 isolated_file:0 [57463.540617] unevictable:6821 dirty:123 writeback:0 [57463.540617] slab_reclaimable:23916 slab_unreclaimable:99248 [57463.540617] mapped:37363 shmem:426 pagetables:1341 bounce:0 [57463.540617] free:68374 free_pcp:1898 free_cma:0 Apr 26 08:01:53 192.168.122.209 [57463.543509] Node 0 active_anon:128216kB inactive_anon:393544kB active_file:407032kB inactive_file:422032kB unevictable:27284kB isolated(anon):0kB isolated(file):0kB mapped:149452kB dirty:616kB writeback:0kB shmem:1704kB shmem_thp: 0kB shmem_pmdmapped: 0kB anon_thp: 0kB writeback_tmp:0kB kernel_stack:9664kB all_unreclaimable? no Apr 26 08:01:53 192.168.122.209 [57463.546160] Node 0 DMA free:11904kB min:408kB low:508kB high:608kB reserved_highatomic:4096KB active_anon:8kB inactive_anon:36kB active_file:0kB inactive_file:8kB unevictable:0kB writepending:0kB present:15992kB managed:15908kB mlocked:0kB pagetables:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB Apr 26 08:01:53 192.168.122.209 [57463.548509] lowmem_reserve[]: 0 1900 2534 2534 2534 Apr 26 08:01:53 192.168.122.209 [57463.548957] Node 0 DMA32 free:236524kB min:50364kB low:62952kB high:75540kB reserved_highatomic:0KB active_anon:122308kB inactive_anon:354792kB active_file:317944kB inactive_file:395620kB unevictable:0kB writepending:148kB present:2080624kB managed:1946020kB mlocked:0kB pagetables:672kB bounce:0kB free_pcp:4848kB local_pcp:1412kB free_cma:0kB Apr 26 08:01:53 192.168.122.209 [57463.551589] lowmem_reserve[]: 0 0 634 634 634 Apr 26 08:01:53 192.168.122.209 [57463.552000] Node 0 Normal free:25068kB min:16804kB low:21004kB high:25204kB reserved_highatomic:2048KB active_anon:5900kB inactive_anon:38716kB active_file:89088kB inactive_file:26544kB unevictable:27284kB writepending:220kB present:2097152kB managed:649288kB mlocked:27284kB pagetables:4692kB bounce:0kB free_pcp:2692kB local_pcp:644kB free_cma:0kB Apr 26 08:01:53 192.168.122.209 [57463.554676] lowmem_reserve[]: 0 0 0 0 0 Apr 26 08:01:53 192.168.122.209 [57463.555043] Node 0 DMA: 14*4kB (MH) 21*8kB (ME) 22*16kB (MEH) 18*32kB (MEH) 16*64kB (MEH) 10*128kB (MEH) 5*256kB (MEH) 4*512kB (MH) 3*1024kB (ME) 1*2048kB (U) 0*4096kB = 11904kB Apr 26 08:01:53 192.168.122.209 [57463.556476] Node 0 DMA32: 1034*4kB (UME) 1600*8kB (UME) 798*16kB (ME) 1861*32kB (UME) 1614*64kB (UME) 281*128kB (UME) 31*256kB (UE) 0*512kB 0*1024kB 0*2048kB 0*4096kB = 236456kB Apr 26 08:01:53 192.168.122.209 [57463.557899] Node 0 Normal: 1043*4kB (UMEH) 171*8kB (UMEH) 349*16kB (UMEH) 376*32kB (UMEH) 24*64kB (UM) 1*128kB (U) 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 24820kB Apr 26 08:01:53 192.168.122.209 [57463.559259] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=1048576kB Apr 26 08:01:53 192.168.122.209 [57463.560032] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=2048kB Apr 26 08:01:53 192.168.122.209 [57463.560779] 268049 total pagecache pages Apr 26 08:01:53 192.168.122.209 [57463.561147] 58140 pages in swap cache Apr 26 08:01:53 192.168.122.209 [57463.561492] Swap cache stats: add 296733, delete 238595, find 369216/420045 Apr 26 08:01:53 192.168.122.209 [57463.562109] Free swap = 3757528kB Apr 26 08:01:53 192.168.122.209 [57463.562430] Total swap = 4194300kB Apr 26 08:01:53 192.168.122.209 [57463.562748] 1048442 pages RAM Apr 26 08:01:53 192.168.122.209 [57463.563031] 0 pages HighMem/MovableOnly Apr 26 08:01:53 192.168.122.209 [57463.563389] 395638 pages reserved Apr 26 08:01:53 192.168.122.209 [57463.563699] 0 pages cma reserved Apr 26 08:01:53 192.168.122.209 [57463.564009] 0 pages hwpoisoned Apr 26 08:01:53 192.168.122.209 [57463.564301] [tempesta fw] Warning: Cannot grow HTTP data string Apr 26 08:01:53 192.168.122.209 [57463.564839] [tempesta fw] Warning: Parser error: state=RGen_BodyParse input(-0)=0xd(' ') data_len=1 off=0 Apr 26 08:01:53 192.168.122.209 [57463.670698] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 08:02:11 192.168.122.209 [57481.725785] swapper/3: page allocation failure: order:9, mode:0x40a20(GFP_ATOMIC|__GFP_COMP), nodemask=(null),cpuset=/,mems_allowed=0 Apr 26 08:02:11 192.168.122.209 [57481.726920] CPU: 3 PID: 0 Comm: swapper/3 Tainted: G OE 5.10.35.tfw-39c65d3-debug #1 Apr 26 08:02:11 192.168.122.209 [57481.727714] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 Apr 26 08:02:11 192.168.122.209 [57481.728534] Call Trace: Apr 26 08:02:11 192.168.122.209 [57481.728770] Apr 26 08:02:11 192.168.122.209 [57481.728969] dump_stack+0x96/0xc4 Apr 26 08:02:11 192.168.122.209 [57481.729276] warn_alloc.cold+0x87/0x12a Apr 26 08:02:11 192.168.122.209 [57481.729664] ? zone_watermark_ok_safe+0x140/0x140 Apr 26 08:02:11 192.168.122.209 [57481.730238] ? __kasan_check_read+0x11/0x20 Apr 26 08:02:11 192.168.122.209 [57481.730640] ? wakeup_kswapd+0xba/0x290 Apr 26 08:02:11 192.168.122.209 [57481.730986] ? __zone_watermark_ok+0x270/0x270 Apr 26 08:02:11 192.168.122.209 [57481.731382] ? wake_all_kswapds+0xf4/0x140 Apr 26 08:02:11 192.168.122.209 [57481.731759] ? __alloc_pages_slowpath.constprop.0+0x11f4/0x1390 Apr 26 08:02:11 192.168.122.209 [57481.732284] __alloc_pages_slowpath.constprop.0+0x1359/0x1390 Apr 26 08:02:11 192.168.122.209 [57481.732797] ? warn_alloc+0x120/0x120 Apr 26 08:02:11 192.168.122.209 [57481.733129] ? enqueue_to_backlog+0x430/0x430 Apr 26 08:02:11 192.168.122.209 [57481.733523] ? __zone_watermark_ok+0x270/0x270 Apr 26 08:02:11 192.168.122.209 [57481.733931] __alloc_pages_nodemask+0x509/0x540 Apr 26 08:02:11 192.168.122.209 [57481.734393] ? __alloc_pages_slowpath.constprop.0+0x1390/0x1390 Apr 26 08:02:11 192.168.122.209 [57481.734960] ? netdev_core_pick_tx+0xb0/0x120 Apr 26 08:02:11 192.168.122.209 [57481.735360] ? __flush_tlb_all+0x37/0x50 Apr 26 08:02:11 192.168.122.209 [57481.735720] ? __kernel_map_pages+0x108/0x180 Apr 26 08:02:11 192.168.122.209 [57481.736109] alloc_pages_current+0x96/0x140 Apr 26 08:02:11 192.168.122.209 [57481.736486] __get_free_pages+0x12/0x60 Apr 26 08:02:11 192.168.122.209 [57481.736879] tfw_pool_alloc_pages+0x9b/0xc0 [tempesta_fw] Apr 26 08:02:11 192.168.122.209 [57481.737390] __tfw_pool_realloc+0x123/0x1a0 [tempesta_fw] Apr 26 08:02:11 192.168.122.209 [57481.737901] __str_grow_tree+0x89/0x210 [tempesta_fw] Apr 26 08:02:11 192.168.122.209 [57481.738380] tfw_str_add_compound+0x33/0x40 [tempesta_fw] Apr 26 08:02:11 192.168.122.209 [57481.738894] __resp_parse_body+0x421/0xb50 [tempesta_fw] Apr 26 08:02:11 192.168.122.209 [57481.739392] tfw_http_parse_resp+0x15e8/0x197d0 [tempesta_fw] Apr 26 08:02:11 192.168.122.209 [57481.740024] ? __resp_parse_body+0xb50/0xb50 [tempesta_fw] Apr 26 08:02:11 192.168.122.209 [57481.740544] ss_skb_process+0x270/0x2f0 [tempesta_fw] Apr 26 08:02:11 192.168.122.209 [57481.741035] ? __resp_parse_body+0xb50/0xb50 [tempesta_fw] Apr 26 08:02:11 192.168.122.209 [57481.741550] ? tfw_sock_srv_exit+0x30/0x30 [tempesta_fw] Apr 26 08:02:11 192.168.122.209 [57481.742024] ? __alloc_pages_nodemask+0x2db/0x540 Apr 26 08:02:11 192.168.122.209 [57481.742472] tfw_http_msg_process_generic+0x282/0xc70 [tempesta_fw] Apr 26 08:02:11 192.168.122.209 [57481.743057] ? tfw_http_req_process+0x11a0/0x11a0 [tempesta_fw] Apr 26 08:02:11 192.168.122.209 [57481.743588] ? __kasan_check_write+0x14/0x20 Apr 26 08:02:11 192.168.122.209 [57481.743973] ? pg_skb_alloc+0x60e/0x680 Apr 26 08:02:11 192.168.122.209 [57481.744322] ? __kasan_check_write+0x14/0x20 Apr 26 08:02:11 192.168.122.209 [57481.744712] ? __alloc_skb+0x278/0x350 Apr 26 08:02:11 192.168.122.209 [57481.745050] ? __kasan_check_write+0x14/0x20 Apr 26 08:02:11 192.168.122.209 [57481.745461] ? __coalesce_frag+0x136/0x370 [tempesta_fw] Apr 26 08:02:11 192.168.122.209 [57481.745963] tfw_http_msg_process+0x80/0xc0 [tempesta_fw] Apr 26 08:02:11 192.168.122.209 [57481.746445] ? skb_release_data+0x8c/0x320 Apr 26 08:02:11 192.168.122.209 [57481.746931] tfw_connection_recv+0x12e/0x250 [tempesta_fw] Apr 26 08:02:11 192.168.122.209 [57481.747505] ? tfw_connection_send+0x70/0x70 [tempesta_fw] Apr 26 08:02:11 192.168.122.209 [57481.748020] ? ss_skb_unroll+0x3d6/0x540 [tempesta_fw] Apr 26 08:02:11 192.168.122.209 [57481.748508] ss_tcp_process_data+0x436/0x8b0 [tempesta_fw] Apr 26 08:02:11 192.168.122.209 [57481.749028] ? __sk_close_locked+0x100/0x100 [tempesta_fw] Apr 26 08:02:11 192.168.122.209 [57481.749513] ? mod_timer+0x10/0x20 Apr 26 08:02:11 192.168.122.209 [57481.749826] ? sk_reset_timer+0x1a/0x70 Apr 26 08:02:11 192.168.122.209 [57481.750232] ss_tcp_data_ready+0x7b/0x150 [tempesta_fw] Apr 26 08:02:11 192.168.122.209 [57481.750715] tcp_data_ready+0x73/0x210 Apr 26 08:02:11 192.168.122.209 [57481.751063] tcp_rcv_established+0x95b/0xb40 Apr 26 08:02:11 192.168.122.209 [57481.751455] ? tcp_data_queue+0x1d80/0x1d80 Apr 26 08:02:11 192.168.122.209 [57481.751857] ? __kasan_check_read+0x11/0x20 Apr 26 08:02:11 192.168.122.209 [57481.752235] tcp_v4_do_rcv+0x25f/0x360 Apr 26 08:02:11 192.168.122.209 [57481.752575] tcp_v4_rcv+0x1600/0x1770 Apr 26 08:02:11 192.168.122.209 [57481.752907] ? tcp_v4_early_demux+0x2f0/0x2f0 Apr 26 08:02:11 192.168.122.209 [57481.753302] ip_protocol_deliver_rcu+0x46/0x2e0 Apr 26 08:02:11 192.168.122.209 [57481.753717] ip_local_deliver_finish+0xc6/0xe0 Apr 26 08:02:11 192.168.122.209 [57481.754112] ip_local_deliver+0x1f5/0x210 Apr 26 08:02:11 192.168.122.209 [57481.754472] ? ip_local_deliver_finish+0xe0/0xe0 Apr 26 08:02:11 192.168.122.209 [57481.754893] ? nf_nat_inet_fn+0x2b3/0x440 [nf_nat] Apr 26 08:02:11 192.168.122.209 [57481.755321] ? ip_protocol_deliver_rcu+0x2e0/0x2e0 Apr 26 08:02:11 192.168.122.209 [57481.755763] ? ip_rcv_finish_core.constprop.0+0x17c/0x890 Apr 26 08:02:11 192.168.122.209 [57481.756261] ip_rcv_finish+0xcf/0xf0 Apr 26 08:02:11 192.168.122.209 [57481.756592] ip_rcv+0x16d/0x180 Apr 26 08:02:11 192.168.122.209 [57481.756883] ? ip_local_deliver+0x210/0x210 Apr 26 08:02:11 192.168.122.209 [57481.757268] ? ip_rcv_finish_core.constprop.0+0x890/0x890 Apr 26 08:02:11 192.168.122.209 [57481.757753] ? update_load_avg+0x132/0xa70 Apr 26 08:02:11 192.168.122.209 [57481.758129] ? sched_clock+0x9/0x10 Apr 26 08:02:11 192.168.122.209 [57481.758449] ? sched_clock_cpu+0x1b/0x110 Apr 26 08:02:11 192.168.122.209 [57481.758824] ? ip_local_deliver+0x210/0x210 Apr 26 08:02:11 192.168.122.209 [57481.759212] __netif_receive_skb_one_core+0x132/0x140 Apr 26 08:02:11 192.168.122.209 [57481.759673] ? napi_gro_receive+0x260/0x260 Apr 26 08:02:11 192.168.122.209 [57481.760054] ? __kasan_check_write+0x14/0x20 Apr 26 08:02:11 192.168.122.209 [57481.760443] ? _raw_spin_lock+0x7b/0xd0 Apr 26 08:02:11 192.168.122.209 [57481.760791] __netif_receive_skb+0x26/0xb0 Apr 26 08:02:11 192.168.122.209 [57481.761174] ? generic_exec_single+0xb1/0x170 Apr 26 08:02:11 192.168.122.209 [57481.761554] process_backlog+0xfe/0x290 Apr 26 08:02:11 192.168.122.209 [57481.761897] net_rx_action+0x287/0x6b0 Apr 26 08:02:11 192.168.122.209 [57481.762230] ? try_to_wake_up+0x41e/0xa70 Apr 26 08:02:11 192.168.122.209 [57481.762612] ? napi_complete_done+0x2c0/0x2c0 Apr 26 08:02:11 192.168.122.209 [57481.763007] ? switch_fpu_return+0x120/0x120 Apr 26 08:02:11 192.168.122.209 [57481.763392] __do_softirq+0xfe/0x383 Apr 26 08:02:11 192.168.122.209 [57481.763720] asm_call_irq_on_stack+0xf/0x20 Apr 26 08:02:11 192.168.122.209 [57481.764099] Apr 26 08:02:11 192.168.122.209 [57481.764301] do_softirq_own_stack+0x3d/0x50 Apr 26 08:02:11 192.168.122.209 [57481.764680] irq_exit_rcu+0xc7/0x120 Apr 26 08:02:11 192.168.122.209 [57481.765009] sysvec_call_function_single+0x3a/0x90 Apr 26 08:02:11 192.168.122.209 [57481.765439] asm_sysvec_call_function_single+0x12/0x20 Apr 26 08:02:11 192.168.122.209 [57481.765900] RIP: 0010:native_safe_halt+0xe/0x10 Apr 26 08:02:11 192.168.122.209 [57481.766308] Code: 49 8b 04 24 a8 08 0f 85 71 ff ff ff e9 0f ff ff ff cc cc cc cc cc cc cc cc cc cc cc e9 07 00 00 00 0f 00 2d d4 62 51 00 fb f4 90 e9 07 00 00 00 0f 00 2d c4 62 51 00 f4 c3 cc cc 0f 1f 44 00 Apr 26 08:02:11 192.168.122.209 [57481.767937] RSP: 0018:ffff888100f47db8 EFLAGS: 00000202 Apr 26 08:02:11 192.168.122.209 [57481.768406] RAX: ffffffffb63426a0 RBX: ffff888100f28040 RCX: ffffffffb632c475 Apr 26 08:02:11 192.168.122.209 [57481.769034] RDX: 00000000195511f2 RSI: 0000000000000004 RDI: ffff888147fb5040 Apr 26 08:02:11 192.168.122.209 [57481.769662] RBP: ffff888100f47dc0 R08: 0000000000000001 R09: ffff888147fb5043 Apr 26 08:02:11 192.168.122.209 [57481.770283] R10: ffffed1028ff6a08 R11: 0000000000000001 R12: 0000000000000003 Apr 26 08:02:11 192.168.122.209 [57481.770913] R13: ffffffffb7ae9360 R14: 0000000000000000 R15: 0000000000000000 Apr 26 08:02:11 192.168.122.209 [57481.771540] ? __cpuidle_text_start+0x8/0x8 Apr 26 08:02:11 192.168.122.209 [57481.771937] ? rcu_eqs_enter.constprop.0+0x85/0xa0 Apr 26 08:02:11 192.168.122.209 [57481.772368] ? default_idle+0xe/0x20 Apr 26 08:02:11 192.168.122.209 [57481.772703] arch_cpu_idle+0x15/0x20 Apr 26 08:02:11 192.168.122.209 [57481.773029] default_idle_call+0x66/0x160 Apr 26 08:02:11 192.168.122.209 [57481.773389] do_idle+0x36f/0x430 Apr 26 08:02:11 192.168.122.209 [57481.773689] ? asm_sysvec_call_function_single+0x12/0x20 Apr 26 08:02:11 192.168.122.209 [57481.774163] ? arch_cpu_idle_exit+0x40/0x40 Apr 26 08:02:11 192.168.122.209 [57481.774540] cpu_startup_entry+0x20/0x30 Apr 26 08:02:11 192.168.122.209 [57481.774897] start_secondary+0x1c1/0x210 Apr 26 08:02:11 192.168.122.209 [57481.775249] ? set_cpu_sibling_map+0xd70/0xd70 Apr 26 08:02:11 192.168.122.209 [57481.775660] ? set_bringup_idt_handler.constprop.0+0x84/0x90 Apr 26 08:02:11 192.168.122.209 [57481.776176] ? start_cpu0+0xc/0xc Apr 26 08:02:11 192.168.122.209 [57481.776477] secondary_startup_64_no_verify+0xb0/0xbb Apr 26 08:02:11 192.168.122.209 [57481.776959] Mem-Info: Apr 26 08:02:11 192.168.122.209 [57481.777181] active_anon:32110 inactive_anon:98215 isolated_anon:0 [57481.777181] active_file:99870 inactive_file:105419 isolated_file:0 [57481.777181] unevictable:6821 dirty:17 writeback:0 [57481.777181] slab_reclaimable:23892 slab_unreclaimable:99210 [57481.777181] mapped:37383 shmem:426 pagetables:1341 bounce:0 [57481.777181] free:70961 free_pcp:1359 free_cma:0 Apr 26 08:02:11 192.168.122.209 [57481.780036] Node 0 active_anon:128440kB inactive_anon:392860kB active_file:399480kB inactive_file:421676kB unevictable:27284kB isolated(anon):0kB isolated(file):0kB mapped:149532kB dirty:192kB writeback:0kB shmem:1704kB shmem_thp: 0kB shmem_pmdmapped: 0kB anon_thp: 0kB writeback_tmp:0kB kernel_stack:9664kB all_unreclaimable? no Apr 26 08:02:11 192.168.122.209 [57481.782547] Node 0 DMA free:11904kB min:408kB low:508kB high:608kB reserved_highatomic:4096KB active_anon:8kB inactive_anon:36kB active_file:0kB inactive_file:8kB unevictable:0kB writepending:0kB present:15992kB managed:15908kB mlocked:0kB pagetables:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB Apr 26 08:02:11 192.168.122.209 [57481.784864] lowmem_reserve[]: 0 1900 2534 2534 2534 Apr 26 08:02:11 192.168.122.209 [57481.785314] Node 0 DMA32 free:246408kB min:50364kB low:62952kB high:75540kB reserved_highatomic:0KB active_anon:122408kB inactive_anon:354196kB active_file:315920kB inactive_file:394524kB unevictable:0kB writepending:24kB present:2080624kB managed:1946020kB mlocked:0kB pagetables:672kB bounce:0kB free_pcp:3376kB local_pcp:52kB free_cma:0kB Apr 26 08:02:11 192.168.122.209 [57481.787914] lowmem_reserve[]: 0 0 634 634 634 Apr 26 08:02:11 192.168.122.209 [57481.788318] Node 0 Normal free:25532kB min:16804kB low:21004kB high:25204kB reserved_highatomic:2048KB active_anon:5900kB inactive_anon:38692kB active_file:84008kB inactive_file:27552kB unevictable:27284kB writepending:44kB present:2097152kB managed:649288kB mlocked:27284kB pagetables:4692kB bounce:0kB free_pcp:2064kB local_pcp:116kB free_cma:0kB Apr 26 08:02:11 192.168.122.209 [57481.791093] lowmem_reserve[]: 0 0 0 0 0 Apr 26 08:02:11 192.168.122.209 [57481.791457] Node 0 DMA: 14*4kB (MH) 21*8kB (ME) 22*16kB (MEH) 18*32kB (MEH) 16*64kB (MEH) 10*128kB (MEH) 5*256kB (MEH) 4*512kB (MH) 3*1024kB (ME) 1*2048kB (U) 0*4096kB = 11904kB Apr 26 08:02:11 192.168.122.209 [57481.792909] Node 0 DMA32: 1369*4kB (UME) 1727*8kB (UME) 927*16kB (UME) 1890*32kB (UME) 1696*64kB (UME) 282*128kB (UME) 31*256kB (UE) 0*512kB 0*1024kB 0*2048kB 0*4096kB = 247180kB Apr 26 08:02:11 192.168.122.209 [57481.794352] Node 0 Normal: 1868*4kB (UMEH) 285*8kB (UMEH) 99*16kB (UMEH) 384*32kB (UMEH) 24*64kB (UM) 1*128kB (U) 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 25288kB Apr 26 08:02:11 192.168.122.209 [57481.795696] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=1048576kB Apr 26 08:02:11 192.168.122.209 [57481.796463] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=2048kB Apr 26 08:02:11 192.168.122.209 [57481.797210] 266073 total pagecache pages Apr 26 08:02:11 192.168.122.209 [57481.797594] 58190 pages in swap cache Apr 26 08:02:11 192.168.122.209 [57481.797932] Swap cache stats: add 296844, delete 238656, find 369218/420048 Apr 26 08:02:11 192.168.122.209 [57481.798557] Free swap = 3757272kB Apr 26 08:02:11 192.168.122.209 [57481.798878] Total swap = 4194300kB Apr 26 08:02:11 192.168.122.209 [57481.799193] 1048442 pages RAM Apr 26 08:02:11 192.168.122.209 [57481.799473] 0 pages HighMem/MovableOnly Apr 26 08:02:11 192.168.122.209 [57481.799836] 395638 pages reserved Apr 26 08:02:11 192.168.122.209 [57481.800145] 0 pages cma reserved Apr 26 08:02:11 192.168.122.209 [57481.800446] 0 pages hwpoisoned Apr 26 08:02:11 192.168.122.209 [57481.800739] [tempesta fw] Warning: Cannot grow HTTP data string Apr 26 08:02:11 192.168.122.209 [57481.801275] [tempesta fw] Warning: Parser error: state=RGen_BodyParse input(-0)=0xd(' ') data_len=1 off=0 Apr 26 08:02:11 192.168.122.209 [57481.903071] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 08:02:11 192.168.122.209 [57482.360008] [tdb] Close table 'client0.tdb' Apr 26 08:02:12 192.168.122.209 [57482.630976] [tdb] Close table 'sessions0.tdb' Apr 26 08:02:15 192.168.122.209 [57485.841470] [tdb] Close table 'cache0.tdb' Apr 26 08:02:15 192.168.122.209 [57486.091934] [tdb] Close table 'filter0.tdb' Apr 26 08:02:15 192.168.122.209 [57486.092365] [tempesta fw] modules are stopped Apr 26 08:02:15 192.168.122.209 [57486.295536] [tempesta fw] exiting... Apr 26 08:02:15 192.168.122.209 [57486.410846] [tdb] Shutdown Tempesta DB Apr 26 08:02:16 192.168.122.209 [57486.688630] End test: encoding.test_encoding.TestH1ChunkedWithLongBodyAndTrailer.test Apr 26 08:02:16 192.168.122.209 [57486.698682] Start test: encoding.test_encoding.TestH1ChunkedWithTrailer.test Apr 26 08:02:17 192.168.122.209 [57487.755886] [tdb] Start Tempesta DB Apr 26 08:02:17 192.168.122.209 [57487.899248] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:02:18 192.168.122.209 [57489.277413] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [57489.277413] Maybe that's fine, but it's worth checking the [57489.277413] config - if there is no relations between the [57489.277413] names, then host name confusion attack is possible. Apr 26 08:02:18 192.168.122.209 [57489.360206] [tempesta fw] Configuration processing is completed. Apr 26 08:02:18 192.168.122.209 [57489.414313] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:02:19 192.168.122.209 [57489.831529] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:02:19 192.168.122.209 [57489.859654] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:02:19 192.168.122.209 [57489.886669] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:02:19 192.168.122.209 [57489.932166] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:02:19 192.168.122.209 [57489.933909] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:02:19 192.168.122.209 [57489.972121] [tempesta fw] Tempesta FW is ready Apr 26 08:02:20 192.168.122.209 [57490.612643] [tdb] Close table 'client0.tdb' Apr 26 08:02:20 192.168.122.209 [57490.800894] [tdb] Close table 'sessions0.tdb' Apr 26 08:02:23 192.168.122.209 [57494.026128] [tdb] Close table 'cache0.tdb' Apr 26 08:02:23 192.168.122.209 [57494.276791] [tdb] Close table 'filter0.tdb' Apr 26 08:02:23 192.168.122.209 [57494.277231] [tempesta fw] modules are stopped Apr 26 08:02:23 192.168.122.209 [57494.509362] [tempesta fw] exiting... Apr 26 08:02:24 192.168.122.209 [57494.645510] [tdb] Shutdown Tempesta DB Apr 26 08:02:24 192.168.122.209 [57494.887471] End test: encoding.test_encoding.TestH1ChunkedWithTrailer.test Apr 26 08:02:24 192.168.122.209 [57494.900919] Start test: encoding.test_encoding.TestH2BodyDechunking.test Apr 26 08:02:25 192.168.122.209 [57495.944808] [tdb] Start Tempesta DB Apr 26 08:02:25 192.168.122.209 [57496.080070] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:02:26 192.168.122.209 [57497.369566] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [57497.369566] Maybe that's fine, but it's worth checking the [57497.369566] config - if there is no relations between the [57497.369566] names, then host name confusion attack is possible. Apr 26 08:02:26 192.168.122.209 [57497.464306] [tempesta fw] Configuration processing is completed. Apr 26 08:02:26 192.168.122.209 [57497.516535] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:02:27 192.168.122.209 [57497.949032] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:02:27 192.168.122.209 [57497.976485] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:02:27 192.168.122.209 [57498.003630] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:02:27 192.168.122.209 [57498.068169] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:02:27 192.168.122.209 [57498.116271] [tempesta fw] Tempesta FW is ready Apr 26 08:02:28 192.168.122.209 [57498.783112] [tdb] Close table 'client0.tdb' Apr 26 08:02:28 192.168.122.209 [57498.963490] [tdb] Close table 'sessions0.tdb' Apr 26 08:02:31 192.168.122.209 [57502.179707] [tdb] Close table 'cache0.tdb' Apr 26 08:02:31 192.168.122.209 [57502.423772] [tdb] Close table 'filter0.tdb' Apr 26 08:02:31 192.168.122.209 [57502.424231] [tempesta fw] modules are stopped Apr 26 08:02:32 192.168.122.209 [57502.608922] [tempesta fw] exiting... Apr 26 08:02:32 192.168.122.209 [57502.737866] [tdb] Shutdown Tempesta DB Apr 26 08:02:32 192.168.122.209 [57502.958658] End test: encoding.test_encoding.TestH2BodyDechunking.test Apr 26 08:02:32 192.168.122.209 [57502.983780] Start test: encoding.test_encoding.TestH2ChunkedExtensionRemoved.test Apr 26 08:02:33 192.168.122.209 [57504.065442] [tdb] Start Tempesta DB Apr 26 08:02:33 192.168.122.209 [57504.197281] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:02:34 192.168.122.209 [57505.381706] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [57505.381706] Maybe that's fine, but it's worth checking the [57505.381706] config - if there is no relations between the [57505.381706] names, then host name confusion attack is possible. Apr 26 08:02:34 192.168.122.209 [57505.480436] [tempesta fw] Configuration processing is completed. Apr 26 08:02:35 192.168.122.209 [57505.531707] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:02:35 192.168.122.209 [57505.947298] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:02:35 192.168.122.209 [57505.982378] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:02:35 192.168.122.209 [57506.008733] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:02:35 192.168.122.209 [57506.048375] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:02:35 192.168.122.209 [57506.096302] [tempesta fw] Tempesta FW is ready Apr 26 08:02:36 192.168.122.209 [57506.700001] [tdb] Close table 'client0.tdb' Apr 26 08:02:36 192.168.122.209 [57506.909289] [tdb] Close table 'sessions0.tdb' Apr 26 08:02:39 192.168.122.209 [57510.162605] [tdb] Close table 'cache0.tdb' Apr 26 08:02:39 192.168.122.209 [57510.407110] [tdb] Close table 'filter0.tdb' Apr 26 08:02:39 192.168.122.209 [57510.407552] [tempesta fw] modules are stopped Apr 26 08:02:40 192.168.122.209 [57510.572421] [tempesta fw] exiting... Apr 26 08:02:40 192.168.122.209 [57510.674417] [tdb] Shutdown Tempesta DB Apr 26 08:02:40 192.168.122.209 [57510.882828] End test: encoding.test_encoding.TestH2ChunkedExtensionRemoved.test Apr 26 08:02:40 192.168.122.209 [57510.905401] Start test: encoding.test_encoding.TestH2ChunkedIsNotLast.test Apr 26 08:02:41 192.168.122.209 [57511.974801] [tdb] Start Tempesta DB Apr 26 08:02:41 192.168.122.209 [57512.128434] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:02:42 192.168.122.209 [57513.457716] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [57513.457716] Maybe that's fine, but it's worth checking the [57513.457716] config - if there is no relations between the [57513.457716] names, then host name confusion attack is possible. Apr 26 08:02:43 192.168.122.209 [57513.548491] [tempesta fw] Configuration processing is completed. Apr 26 08:02:43 192.168.122.209 [57513.611546] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:02:43 192.168.122.209 [57514.100934] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:02:43 192.168.122.209 [57514.131408] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:02:43 192.168.122.209 [57514.160315] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:02:43 192.168.122.209 [57514.204492] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:02:43 192.168.122.209 [57514.244442] [tempesta fw] Tempesta FW is ready Apr 26 08:02:43 192.168.122.209 [57514.478686] [tempesta fw] Warning: Parser error: state=Resp_HdrTransfer_EncodingV input(-0)=0xd(' ') data_len=1 off=0 Apr 26 08:02:43 192.168.122.209 [57514.479780] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 08:02:44 192.168.122.209 [57514.914259] [tdb] Close table 'client0.tdb' Apr 26 08:02:44 192.168.122.209 [57515.117281] [tdb] Close table 'sessions0.tdb' Apr 26 08:02:47 192.168.122.209 [57518.381407] [tdb] Close table 'cache0.tdb' Apr 26 08:02:48 192.168.122.209 [57518.627700] [tdb] Close table 'filter0.tdb' Apr 26 08:02:48 192.168.122.209 [57518.628144] [tempesta fw] modules are stopped Apr 26 08:02:48 192.168.122.209 [57518.817105] [tempesta fw] exiting... Apr 26 08:02:48 192.168.122.209 [57518.932667] [tdb] Shutdown Tempesta DB Apr 26 08:02:48 192.168.122.209 [57519.185789] End test: encoding.test_encoding.TestH2ChunkedIsNotLast.test Apr 26 08:02:48 192.168.122.209 [57519.197657] Start test: encoding.test_encoding.TestH2ChunkedWithLongBodyAndTrailer.test Apr 26 08:02:49 192.168.122.209 [57520.267743] [tdb] Start Tempesta DB Apr 26 08:02:49 192.168.122.209 [57520.416392] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:02:51 192.168.122.209 [57521.829815] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [57521.829815] Maybe that's fine, but it's worth checking the [57521.829815] config - if there is no relations between the [57521.829815] names, then host name confusion attack is possible. Apr 26 08:02:51 192.168.122.209 [57521.916578] [tempesta fw] Configuration processing is completed. Apr 26 08:02:51 192.168.122.209 [57521.971359] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:02:51 192.168.122.209 [57522.419409] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:02:51 192.168.122.209 [57522.450509] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:02:51 192.168.122.209 [57522.480468] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:02:51 192.168.122.209 [57522.524579] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:02:51 192.168.122.209 [57522.526347] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:02:52 192.168.122.209 [57522.564514] [tempesta fw] Tempesta FW is ready Apr 26 08:03:10 192.168.122.209 [57540.915471] swapper/0: page allocation failure: order:9, mode:0x40a20(GFP_ATOMIC|__GFP_COMP), nodemask=(null),cpuset=/,mems_allowed=0-1023 Apr 26 08:03:10 192.168.122.209 [57540.916665] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G OE 5.10.35.tfw-39c65d3-debug #1 Apr 26 08:03:10 192.168.122.209 [57540.917462] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 Apr 26 08:03:10 192.168.122.209 [57540.918280] Call Trace: Apr 26 08:03:10 192.168.122.209 [57540.918515] Apr 26 08:03:10 192.168.122.209 [57540.918715] dump_stack+0x96/0xc4 Apr 26 08:03:10 192.168.122.209 [57540.919023] warn_alloc.cold+0x87/0x12a Apr 26 08:03:10 192.168.122.209 [57540.919381] ? zone_watermark_ok_safe+0x140/0x140 Apr 26 08:03:10 192.168.122.209 [57540.919807] ? __kasan_check_read+0x11/0x20 Apr 26 08:03:10 192.168.122.209 [57540.920192] ? wakeup_kswapd+0xba/0x290 Apr 26 08:03:10 192.168.122.209 [57540.920545] ? __zone_watermark_ok+0x270/0x270 Apr 26 08:03:10 192.168.122.209 [57540.920946] ? wake_all_kswapds+0xf4/0x140 Apr 26 08:03:10 192.168.122.209 [57540.921323] ? __alloc_pages_slowpath.constprop.0+0x11f4/0x1390 Apr 26 08:03:10 192.168.122.209 [57540.921856] __alloc_pages_slowpath.constprop.0+0x1359/0x1390 Apr 26 08:03:10 192.168.122.209 [57540.922375] ? warn_alloc+0x120/0x120 Apr 26 08:03:10 192.168.122.209 [57540.922713] ? enqueue_to_backlog+0x430/0x430 Apr 26 08:03:10 192.168.122.209 [57540.923274] ? eth_type_trans+0x195/0x2f0 Apr 26 08:03:10 192.168.122.209 [57540.923648] ? __zone_watermark_ok+0x270/0x270 Apr 26 08:03:10 192.168.122.209 [57540.924051] __alloc_pages_nodemask+0x509/0x540 Apr 26 08:03:10 192.168.122.209 [57540.924465] ? __alloc_pages_slowpath.constprop.0+0x1390/0x1390 Apr 26 08:03:10 192.168.122.209 [57540.925088] ? netdev_core_pick_tx+0xb0/0x120 Apr 26 08:03:10 192.168.122.209 [57540.925488] ? __dev_queue_xmit+0x6e9/0xf90 Apr 26 08:03:10 192.168.122.209 [57540.925870] alloc_pages_current+0x96/0x140 Apr 26 08:03:10 192.168.122.209 [57540.926248] __get_free_pages+0x12/0x60 Apr 26 08:03:10 192.168.122.209 [57540.926642] tfw_pool_alloc_pages+0x9b/0xc0 [tempesta_fw] Apr 26 08:03:10 192.168.122.209 [57540.927157] __tfw_pool_realloc+0x123/0x1a0 [tempesta_fw] Apr 26 08:03:10 192.168.122.209 [57540.927688] __str_grow_tree+0x89/0x210 [tempesta_fw] Apr 26 08:03:10 192.168.122.209 [57540.928169] tfw_str_add_compound+0x33/0x40 [tempesta_fw] Apr 26 08:03:10 192.168.122.209 [57540.928684] __resp_parse_body+0x421/0xb50 [tempesta_fw] Apr 26 08:03:10 192.168.122.209 [57540.929192] tfw_http_parse_resp+0x15e8/0x197d0 [tempesta_fw] Apr 26 08:03:10 192.168.122.209 [57540.929736] ? __resp_parse_body+0xb50/0xb50 [tempesta_fw] Apr 26 08:03:10 192.168.122.209 [57540.930274] ss_skb_process+0x270/0x2f0 [tempesta_fw] Apr 26 08:03:10 192.168.122.209 [57540.930763] ? __resp_parse_body+0xb50/0xb50 [tempesta_fw] Apr 26 08:03:10 192.168.122.209 [57540.931290] ? tfw_sock_srv_exit+0x30/0x30 [tempesta_fw] Apr 26 08:03:10 192.168.122.209 [57540.931770] ? __ip_finish_output+0x340/0x340 Apr 26 08:03:10 192.168.122.209 [57540.932186] tfw_http_msg_process_generic+0x282/0xc70 [tempesta_fw] Apr 26 08:03:10 192.168.122.209 [57540.932772] ? tfw_http_req_process+0x11a0/0x11a0 [tempesta_fw] Apr 26 08:03:10 192.168.122.209 [57540.933314] ? pg_skb_alloc+0x60e/0x680 Apr 26 08:03:10 192.168.122.209 [57540.933666] ? __kasan_check_write+0x14/0x20 Apr 26 08:03:10 192.168.122.209 [57540.934055] ? __alloc_skb+0x278/0x350 Apr 26 08:03:10 192.168.122.209 [57540.934404] ? __kasan_check_write+0x14/0x20 Apr 26 08:03:10 192.168.122.209 [57540.934824] ? __coalesce_frag+0x136/0x370 [tempesta_fw] Apr 26 08:03:10 192.168.122.209 [57540.935356] tfw_http_msg_process+0x80/0xc0 [tempesta_fw] Apr 26 08:03:10 192.168.122.209 [57540.935840] ? skb_release_data+0x8c/0x320 Apr 26 08:03:10 192.168.122.209 [57540.936233] tfw_connection_recv+0x12e/0x250 [tempesta_fw] Apr 26 08:03:10 192.168.122.209 [57540.936755] ? tfw_connection_send+0x70/0x70 [tempesta_fw] Apr 26 08:03:10 192.168.122.209 [57540.937272] ? ss_skb_unroll+0x3d6/0x540 [tempesta_fw] Apr 26 08:03:10 192.168.122.209 [57540.937761] ss_tcp_process_data+0x436/0x8b0 [tempesta_fw] Apr 26 08:03:10 192.168.122.209 [57540.938278] ? __sk_close_locked+0x100/0x100 [tempesta_fw] Apr 26 08:03:10 192.168.122.209 [57540.938776] ? mod_timer+0x10/0x20 Apr 26 08:03:10 192.168.122.209 [57540.939086] ? sk_reset_timer+0x1a/0x70 Apr 26 08:03:10 192.168.122.209 [57540.939464] ss_tcp_data_ready+0x7b/0x150 [tempesta_fw] Apr 26 08:03:10 192.168.122.209 [57540.939931] tcp_data_ready+0x73/0x210 Apr 26 08:03:10 192.168.122.209 [57540.940274] tcp_rcv_established+0x95b/0xb40 Apr 26 08:03:10 192.168.122.209 [57540.940662] ? tcp_data_queue+0x1d80/0x1d80 Apr 26 08:03:10 192.168.122.209 [57540.941043] ? __kasan_check_read+0x11/0x20 Apr 26 08:03:10 192.168.122.209 [57540.941424] tcp_v4_do_rcv+0x25f/0x360 Apr 26 08:03:10 192.168.122.209 [57540.941768] tcp_v4_rcv+0x1600/0x1770 Apr 26 08:03:10 192.168.122.209 [57540.942102] ? tcp_v4_early_demux+0x2f0/0x2f0 Apr 26 08:03:10 192.168.122.209 [57540.942497] ip_protocol_deliver_rcu+0x46/0x2e0 Apr 26 08:03:10 192.168.122.209 [57540.942910] ip_local_deliver_finish+0xc6/0xe0 Apr 26 08:03:10 192.168.122.209 [57540.943324] ip_local_deliver+0x1f5/0x210 Apr 26 08:03:10 192.168.122.209 [57540.943686] ? ip_local_deliver_finish+0xe0/0xe0 Apr 26 08:03:10 192.168.122.209 [57540.944101] ? nf_nat_inet_fn+0x2b3/0x440 [nf_nat] Apr 26 08:03:10 192.168.122.209 [57540.944532] ? ip_protocol_deliver_rcu+0x2e0/0x2e0 Apr 26 08:03:10 192.168.122.209 [57540.944964] ? ip_rcv_finish_core.constprop.0+0x17c/0x890 Apr 26 08:03:10 192.168.122.209 [57540.945447] ip_rcv_finish+0xcf/0xf0 Apr 26 08:03:10 192.168.122.209 [57540.945772] ip_rcv+0x16d/0x180 Apr 26 08:03:10 192.168.122.209 [57540.946059] ? ip_local_deliver+0x210/0x210 Apr 26 08:03:10 192.168.122.209 [57540.946444] ? ip_rcv_finish_core.constprop.0+0x890/0x890 Apr 26 08:03:10 192.168.122.209 [57540.946926] ? run_posix_cpu_timers+0x32e/0x3a0 Apr 26 08:03:10 192.168.122.209 [57540.947335] ? posix_cpu_timers_exit_group+0x110/0x110 Apr 26 08:03:10 192.168.122.209 [57540.947793] ? ip_local_deliver+0x210/0x210 Apr 26 08:03:10 192.168.122.209 [57540.948175] __netif_receive_skb_one_core+0x132/0x140 Apr 26 08:03:10 192.168.122.209 [57540.948628] ? napi_gro_receive+0x260/0x260 Apr 26 08:03:10 192.168.122.209 [57540.949004] ? __kasan_check_write+0x14/0x20 Apr 26 08:03:10 192.168.122.209 [57540.949420] ? _raw_spin_lock+0x7b/0xd0 Apr 26 08:03:10 192.168.122.209 [57540.949771] __netif_receive_skb+0x26/0xb0 Apr 26 08:03:10 192.168.122.209 [57540.950142] ? generic_exec_single+0xb1/0x170 Apr 26 08:03:10 192.168.122.209 [57540.950550] process_backlog+0xfe/0x290 Apr 26 08:03:10 192.168.122.209 [57540.950900] net_rx_action+0x287/0x6b0 Apr 26 08:03:10 192.168.122.209 [57540.951247] ? napi_complete_done+0x2c0/0x2c0 Apr 26 08:03:10 192.168.122.209 [57540.951642] ? switch_fpu_return+0x120/0x120 Apr 26 08:03:10 192.168.122.209 [57540.952029] __do_softirq+0xfe/0x383 Apr 26 08:03:10 192.168.122.209 [57540.952356] asm_call_irq_on_stack+0xf/0x20 Apr 26 08:03:10 192.168.122.209 [57540.952735] Apr 26 08:03:10 192.168.122.209 [57540.952936] do_softirq_own_stack+0x3d/0x50 Apr 26 08:03:10 192.168.122.209 [57540.953324] irq_exit_rcu+0xc7/0x120 Apr 26 08:03:10 192.168.122.209 [57540.953652] sysvec_call_function_single+0x3a/0x90 Apr 26 08:03:10 192.168.122.209 [57540.954086] asm_sysvec_call_function_single+0x12/0x20 Apr 26 08:03:10 192.168.122.209 [57540.954550] RIP: 0010:native_safe_halt+0xe/0x10 Apr 26 08:03:10 192.168.122.209 [57540.954957] Code: 49 8b 04 24 a8 08 0f 85 71 ff ff ff e9 0f ff ff ff cc cc cc cc cc cc cc cc cc cc cc e9 07 00 00 00 0f 00 2d d4 62 51 00 fb f4 90 e9 07 00 00 00 0f 00 2d c4 62 51 00 f4 c3 cc cc 0f 1f 44 00 Apr 26 08:03:10 192.168.122.209 [57540.956596] RSP: 0018:ffffffffb7207dc8 EFLAGS: 00000202 Apr 26 08:03:10 192.168.122.209 [57540.957067] RAX: ffffffffb63426a0 RBX: ffffffffb721b100 RCX: ffffffffb632c475 Apr 26 08:03:10 192.168.122.209 [57540.957698] RDX: 000000001710ea62 RSI: 0000000000000004 RDI: ffff888147e35040 Apr 26 08:03:10 192.168.122.209 [57540.958328] RBP: ffffffffb7207dd0 R08: 0000000000000001 R09: ffff888147e35043 Apr 26 08:03:10 192.168.122.209 [57540.958953] R10: ffffed1028fc6a08 R11: 0000000000000001 R12: 0000000000000000 Apr 26 08:03:10 192.168.122.209 [57540.959591] R13: ffffffffb7ae9360 R14: 0000000000000000 R15: 0000000000000000 Apr 26 08:03:10 192.168.122.209 [57540.960215] ? __cpuidle_text_start+0x8/0x8 Apr 26 08:03:10 192.168.122.209 [57540.960598] ? rcu_eqs_enter.constprop.0+0x85/0xa0 Apr 26 08:03:10 192.168.122.209 [57540.961030] ? default_idle+0xe/0x20 Apr 26 08:03:10 192.168.122.209 [57540.961362] arch_cpu_idle+0x15/0x20 Apr 26 08:03:10 192.168.122.209 [57540.961689] default_idle_call+0x66/0x160 Apr 26 08:03:10 192.168.122.209 [57540.962054] do_idle+0x36f/0x430 Apr 26 08:03:10 192.168.122.209 [57540.962353] ? asm_sysvec_call_function_single+0x12/0x20 Apr 26 08:03:10 192.168.122.209 [57540.962830] ? arch_cpu_idle_exit+0x40/0x40 Apr 26 08:03:10 192.168.122.209 [57540.963206] cpu_startup_entry+0x20/0x30 Apr 26 08:03:10 192.168.122.209 [57540.963569] rest_init+0xc8/0xce Apr 26 08:03:10 192.168.122.209 [57540.963894] arch_call_rest_init+0xe/0x1b Apr 26 08:03:10 192.168.122.209 [57540.964261] start_kernel+0x380/0x39d Apr 26 08:03:10 192.168.122.209 [57540.964598] x86_64_start_reservations+0x24/0x26 Apr 26 08:03:10 192.168.122.209 [57540.965013] x86_64_start_kernel+0x7a/0x7e Apr 26 08:03:10 192.168.122.209 [57540.965401] secondary_startup_64_no_verify+0xb0/0xbb Apr 26 08:03:10 192.168.122.209 [57540.965870] Mem-Info: Apr 26 08:03:10 192.168.122.209 [57540.966091] active_anon:32282 inactive_anon:97986 isolated_anon:0 [57540.966091] active_file:98837 inactive_file:104501 isolated_file:0 [57540.966091] unevictable:6821 dirty:94 writeback:0 [57540.966091] slab_reclaimable:23910 slab_unreclaimable:99132 [57540.966091] mapped:37361 shmem:426 pagetables:1340 bounce:0 [57540.966091] free:60377 free_pcp:1884 free_cma:0 Apr 26 08:03:10 192.168.122.209 [57540.968950] Node 0 active_anon:129128kB inactive_anon:391944kB active_file:395348kB inactive_file:418004kB unevictable:27284kB isolated(anon):0kB isolated(file):0kB mapped:149444kB dirty:376kB writeback:0kB shmem:1704kB shmem_thp: 0kB shmem_pmdmapped: 0kB anon_thp: 0kB writeback_tmp:0kB kernel_stack:9600kB all_unreclaimable? no Apr 26 08:03:10 192.168.122.209 [57540.971462] Node 0 DMA free:11904kB min:408kB low:508kB high:608kB reserved_highatomic:4096KB active_anon:8kB inactive_anon:36kB active_file:0kB inactive_file:8kB unevictable:0kB writepending:0kB present:15992kB managed:15908kB mlocked:0kB pagetables:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB Apr 26 08:03:10 192.168.122.209 [57540.973821] lowmem_reserve[]: 0 1900 2534 2534 2534 Apr 26 08:03:10 192.168.122.209 [57540.974271] Node 0 DMA32 free:205088kB min:50364kB low:62952kB high:75540kB reserved_highatomic:0KB active_anon:123156kB inactive_anon:353144kB active_file:315060kB inactive_file:386048kB unevictable:0kB writepending:152kB present:2080624kB managed:1946020kB mlocked:0kB pagetables:668kB bounce:0kB free_pcp:4952kB local_pcp:1260kB free_cma:0kB Apr 26 08:03:10 192.168.122.209 [57540.976908] lowmem_reserve[]: 0 0 634 634 634 Apr 26 08:03:10 192.168.122.209 [57540.977317] Node 0 Normal free:24516kB min:16804kB low:21004kB high:25204kB reserved_highatomic:2048KB active_anon:5848kB inactive_anon:38808kB active_file:80244kB inactive_file:32488kB unevictable:27284kB writepending:224kB present:2097152kB managed:649288kB mlocked:27284kB pagetables:4692kB bounce:0kB free_pcp:2560kB local_pcp:664kB free_cma:0kB Apr 26 08:03:10 192.168.122.209 [57540.980001] lowmem_reserve[]: 0 0 0 0 0 Apr 26 08:03:10 192.168.122.209 [57540.980365] Node 0 DMA: 14*4kB (MH) 21*8kB (ME) 22*16kB (MEH) 18*32kB (MEH) 16*64kB (MEH) 10*128kB (MEH) 5*256kB (MEH) 4*512kB (MH) 3*1024kB (ME) 1*2048kB (U) 0*4096kB = 11904kB Apr 26 08:03:10 192.168.122.209 [57540.981794] Node 0 DMA32: 760*4kB (UME) 1853*8kB (UME) 1372*16kB (UME) 1930*32kB (UME) 1317*64kB (UME) 91*128kB (UME) 31*256kB (UE) 0*512kB 0*1024kB 0*2048kB 0*4096kB = 205448kB Apr 26 08:03:10 192.168.122.209 [57540.983218] Node 0 Normal: 955*4kB (UMEH) 370*8kB (UMEH) 264*16kB (UMEH) 371*32kB (UMEH) 24*64kB (UM) 1*128kB (U) 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 24540kB Apr 26 08:03:10 192.168.122.209 [57540.984568] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=1048576kB Apr 26 08:03:10 192.168.122.209 [57540.985334] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=2048kB Apr 26 08:03:10 192.168.122.209 [57540.986076] 264027 total pagecache pages Apr 26 08:03:10 192.168.122.209 [57540.986438] 58060 pages in swap cache Apr 26 08:03:10 192.168.122.209 [57540.986781] Swap cache stats: add 296847, delete 238789, find 369452/420283 Apr 26 08:03:10 192.168.122.209 [57540.987397] Free swap = 3757528kB Apr 26 08:03:10 192.168.122.209 [57540.987709] Total swap = 4194300kB Apr 26 08:03:10 192.168.122.209 [57540.988023] 1048442 pages RAM Apr 26 08:03:10 192.168.122.209 [57540.988307] 0 pages HighMem/MovableOnly Apr 26 08:03:10 192.168.122.209 [57540.988666] 395638 pages reserved Apr 26 08:03:10 192.168.122.209 [57540.988978] 0 pages cma reserved Apr 26 08:03:10 192.168.122.209 [57540.989277] 0 pages hwpoisoned Apr 26 08:03:10 192.168.122.209 [57540.989573] [tempesta fw] Warning: Cannot grow HTTP data string Apr 26 08:03:10 192.168.122.209 [57540.990097] [tempesta fw] Warning: Parser error: state=RGen_BodyParse input(-0)=0xa(' [57540.990097] ') data_len=1 off=0 Apr 26 08:03:10 192.168.122.209 [57541.116053] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 08:03:28 192.168.122.209 [57559.520025] swapper/3: page allocation failure: order:9, mode:0x40a20(GFP_ATOMIC|__GFP_COMP), nodemask=(null),cpuset=/,mems_allowed=0 Apr 26 08:03:28 192.168.122.209 [57559.521221] CPU: 3 PID: 0 Comm: swapper/3 Tainted: G OE 5.10.35.tfw-39c65d3-debug #1 Apr 26 08:03:28 192.168.122.209 [57559.522016] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 Apr 26 08:03:28 192.168.122.209 [57559.522835] Call Trace: Apr 26 08:03:28 192.168.122.209 [57559.523062] Apr 26 08:03:28 192.168.122.209 [57559.523297] dump_stack+0x96/0xc4 Apr 26 08:03:28 192.168.122.209 [57559.523615] warn_alloc.cold+0x87/0x12a Apr 26 08:03:28 192.168.122.209 [57559.523983] ? zone_watermark_ok_safe+0x140/0x140 Apr 26 08:03:28 192.168.122.209 [57559.524408] ? __kasan_check_read+0x11/0x20 Apr 26 08:03:28 192.168.122.209 [57559.524798] ? wakeup_kswapd+0xba/0x290 Apr 26 08:03:28 192.168.122.209 [57559.525150] ? __zone_watermark_ok+0x270/0x270 Apr 26 08:03:28 192.168.122.209 [57559.525558] ? wake_all_kswapds+0xf4/0x140 Apr 26 08:03:28 192.168.122.209 [57559.525929] ? __alloc_pages_slowpath.constprop.0+0x11f4/0x1390 Apr 26 08:03:28 192.168.122.209 [57559.526455] __alloc_pages_slowpath.constprop.0+0x1359/0x1390 Apr 26 08:03:28 192.168.122.209 [57559.526976] ? warn_alloc+0x120/0x120 Apr 26 08:03:28 192.168.122.209 [57559.527317] ? enqueue_to_backlog+0x430/0x430 Apr 26 08:03:28 192.168.122.209 [57559.527716] ? eth_type_trans+0x195/0x2f0 Apr 26 08:03:28 192.168.122.209 [57559.528077] ? __zone_watermark_ok+0x270/0x270 Apr 26 08:03:28 192.168.122.209 [57559.528478] __alloc_pages_nodemask+0x509/0x540 Apr 26 08:03:28 192.168.122.209 [57559.528890] ? __alloc_pages_slowpath.constprop.0+0x1390/0x1390 Apr 26 08:03:28 192.168.122.209 [57559.529412] ? netdev_core_pick_tx+0xb0/0x120 Apr 26 08:03:28 192.168.122.209 [57559.529806] ? __dev_queue_xmit+0x6e9/0xf90 Apr 26 08:03:29 192.168.122.209 [57559.530187] alloc_pages_current+0x96/0x140 Apr 26 08:03:29 192.168.122.209 [57559.530566] __get_free_pages+0x12/0x60 Apr 26 08:03:29 192.168.122.209 [57559.530969] tfw_pool_alloc_pages+0x9b/0xc0 [tempesta_fw] Apr 26 08:03:29 192.168.122.209 [57559.531481] __tfw_pool_realloc+0x123/0x1a0 [tempesta_fw] Apr 26 08:03:29 192.168.122.209 [57559.531993] __str_grow_tree+0x89/0x210 [tempesta_fw] Apr 26 08:03:29 192.168.122.209 [57559.532472] tfw_str_add_compound+0x33/0x40 [tempesta_fw] Apr 26 08:03:29 192.168.122.209 [57559.532980] __resp_parse_body+0x421/0xb50 [tempesta_fw] Apr 26 08:03:29 192.168.122.209 [57559.533476] tfw_http_parse_resp+0x15e8/0x197d0 [tempesta_fw] Apr 26 08:03:29 192.168.122.209 [57559.534016] ? __resp_parse_body+0xb50/0xb50 [tempesta_fw] Apr 26 08:03:29 192.168.122.209 [57559.534529] ss_skb_process+0x270/0x2f0 [tempesta_fw] Apr 26 08:03:29 192.168.122.209 [57559.535005] ? __resp_parse_body+0xb50/0xb50 [tempesta_fw] Apr 26 08:03:29 192.168.122.209 [57559.535523] ? tfw_sock_srv_exit+0x30/0x30 [tempesta_fw] Apr 26 08:03:29 192.168.122.209 [57559.536009] ? __ip_finish_output+0x340/0x340 Apr 26 08:03:29 192.168.122.209 [57559.536426] tfw_http_msg_process_generic+0x282/0xc70 [tempesta_fw] Apr 26 08:03:29 192.168.122.209 [57559.537008] ? tfw_http_req_process+0x11a0/0x11a0 [tempesta_fw] Apr 26 08:03:29 192.168.122.209 [57559.537532] ? __kasan_check_write+0x14/0x20 Apr 26 08:03:29 192.168.122.209 [57559.537928] ? pg_skb_alloc+0x60e/0x680 Apr 26 08:03:29 192.168.122.209 [57559.538276] ? __kasan_check_write+0x14/0x20 Apr 26 08:03:29 192.168.122.209 [57559.538664] ? __alloc_skb+0x278/0x350 Apr 26 08:03:29 192.168.122.209 [57559.539003] ? __kasan_check_write+0x14/0x20 Apr 26 08:03:29 192.168.122.209 [57559.539419] ? __coalesce_frag+0x136/0x370 [tempesta_fw] Apr 26 08:03:29 192.168.122.209 [57559.539918] tfw_http_msg_process+0x80/0xc0 [tempesta_fw] Apr 26 08:03:29 192.168.122.209 [57559.540394] ? skb_release_data+0x8c/0x320 Apr 26 08:03:29 192.168.122.209 [57559.540788] tfw_connection_recv+0x12e/0x250 [tempesta_fw] Apr 26 08:03:29 192.168.122.209 [57559.541301] ? tfw_connection_send+0x70/0x70 [tempesta_fw] Apr 26 08:03:29 192.168.122.209 [57559.541816] ? ss_skb_unroll+0x3d6/0x540 [tempesta_fw] Apr 26 08:03:29 192.168.122.209 [57559.542297] ss_tcp_process_data+0x436/0x8b0 [tempesta_fw] Apr 26 08:03:29 192.168.122.209 [57559.542817] ? __sk_close_locked+0x100/0x100 [tempesta_fw] Apr 26 08:03:29 192.168.122.209 [57559.543312] ? mod_timer+0x10/0x20 Apr 26 08:03:29 192.168.122.209 [57559.543626] ? sk_reset_timer+0x1a/0x70 Apr 26 08:03:29 192.168.122.209 [57559.543999] ss_tcp_data_ready+0x7b/0x150 [tempesta_fw] Apr 26 08:03:29 192.168.122.209 [57559.544466] tcp_data_ready+0x73/0x210 Apr 26 08:03:29 192.168.122.209 [57559.544810] tcp_rcv_established+0x95b/0xb40 Apr 26 08:03:29 192.168.122.209 [57559.545195] ? tcp_data_queue+0x1d80/0x1d80 Apr 26 08:03:29 192.168.122.209 [57559.545573] ? __kasan_check_read+0x11/0x20 Apr 26 08:03:29 192.168.122.209 [57559.545949] tcp_v4_do_rcv+0x25f/0x360 Apr 26 08:03:29 192.168.122.209 [57559.546286] tcp_v4_rcv+0x1600/0x1770 Apr 26 08:03:29 192.168.122.209 [57559.546626] ? tcp_v4_early_demux+0x2f0/0x2f0 Apr 26 08:03:29 192.168.122.209 [57559.547015] ip_protocol_deliver_rcu+0x46/0x2e0 Apr 26 08:03:29 192.168.122.209 [57559.547418] ip_local_deliver_finish+0xc6/0xe0 Apr 26 08:03:29 192.168.122.209 [57559.547822] ip_local_deliver+0x1f5/0x210 Apr 26 08:03:29 192.168.122.209 [57559.548184] ? ip_local_deliver_finish+0xe0/0xe0 Apr 26 08:03:29 192.168.122.209 [57559.548611] ? nf_nat_inet_fn+0x2b3/0x440 [nf_nat] Apr 26 08:03:29 192.168.122.209 [57559.549036] ? ip_protocol_deliver_rcu+0x2e0/0x2e0 Apr 26 08:03:29 192.168.122.209 [57559.549463] ? ip_rcv_finish_core.constprop.0+0x17c/0x890 Apr 26 08:03:29 192.168.122.209 [57559.549945] ip_rcv_finish+0xcf/0xf0 Apr 26 08:03:29 192.168.122.209 [57559.550267] ip_rcv+0x16d/0x180 Apr 26 08:03:29 192.168.122.209 [57559.550558] ? ip_local_deliver+0x210/0x210 Apr 26 08:03:29 192.168.122.209 [57559.551003] ? ip_rcv_finish_core.constprop.0+0x890/0x890 Apr 26 08:03:29 192.168.122.209 [57559.551497] ? try_to_wake_up+0x41e/0xa70 Apr 26 08:03:29 192.168.122.209 [57559.551861] ? ip_local_deliver+0x210/0x210 Apr 26 08:03:29 192.168.122.209 [57559.552236] __netif_receive_skb_one_core+0x132/0x140 Apr 26 08:03:29 192.168.122.209 [57559.552689] ? napi_gro_receive+0x260/0x260 Apr 26 08:03:29 192.168.122.209 [57559.553066] ? __kasan_check_write+0x14/0x20 Apr 26 08:03:29 192.168.122.209 [57559.553463] ? _raw_spin_lock+0x7b/0xd0 Apr 26 08:03:29 192.168.122.209 [57559.553810] __netif_receive_skb+0x26/0xb0 Apr 26 08:03:29 192.168.122.209 [57559.554180] process_backlog+0xfe/0x290 Apr 26 08:03:29 192.168.122.209 [57559.554526] net_rx_action+0x287/0x6b0 Apr 26 08:03:29 192.168.122.209 [57559.554868] ? napi_complete_done+0x2c0/0x2c0 Apr 26 08:03:29 192.168.122.209 [57559.555268] ? switch_fpu_return+0x120/0x120 Apr 26 08:03:29 192.168.122.209 [57559.555656] __do_softirq+0xfe/0x383 Apr 26 08:03:29 192.168.122.209 [57559.555982] asm_call_irq_on_stack+0xf/0x20 Apr 26 08:03:29 192.168.122.209 [57559.556353] Apr 26 08:03:29 192.168.122.209 [57559.556559] do_softirq_own_stack+0x3d/0x50 Apr 26 08:03:29 192.168.122.209 [57559.556940] irq_exit_rcu+0xc7/0x120 Apr 26 08:03:29 192.168.122.209 [57559.557273] sysvec_call_function_single+0x3a/0x90 Apr 26 08:03:29 192.168.122.209 [57559.557701] asm_sysvec_call_function_single+0x12/0x20 Apr 26 08:03:29 192.168.122.209 [57559.558155] RIP: 0010:native_safe_halt+0xe/0x10 Apr 26 08:03:29 192.168.122.209 [57559.558566] Code: 49 8b 04 24 a8 08 0f 85 71 ff ff ff e9 0f ff ff ff cc cc cc cc cc cc cc cc cc cc cc e9 07 00 00 00 0f 00 2d d4 62 51 00 fb f4 90 e9 07 00 00 00 0f 00 2d c4 62 51 00 f4 c3 cc cc 0f 1f 44 00 Apr 26 08:03:29 192.168.122.209 [57559.560208] RSP: 0018:ffff888100f47db8 EFLAGS: 00000206 Apr 26 08:03:29 192.168.122.209 [57559.560696] RAX: ffffffffb63426a0 RBX: ffff888100f28040 RCX: ffffffffb632c475 Apr 26 08:03:29 192.168.122.209 [57559.561323] RDX: 000000001975923a RSI: 0000000000000004 RDI: ffff888147fb5040 Apr 26 08:03:29 192.168.122.209 [57559.561953] RBP: ffff888100f47dc0 R08: 0000000000000001 R09: ffff888147fb5043 Apr 26 08:03:29 192.168.122.209 [57559.562584] R10: ffffed1028ff6a08 R11: 0000000000000001 R12: 0000000000000003 Apr 26 08:03:29 192.168.122.209 [57559.563205] R13: ffffffffb7ae9360 R14: 0000000000000000 R15: 0000000000000000 Apr 26 08:03:29 192.168.122.209 [57559.563832] ? __cpuidle_text_start+0x8/0x8 Apr 26 08:03:29 192.168.122.209 [57559.564208] ? rcu_eqs_enter.constprop.0+0x85/0xa0 Apr 26 08:03:29 192.168.122.209 [57559.564642] ? default_idle+0xe/0x20 Apr 26 08:03:29 192.168.122.209 [57559.564964] arch_cpu_idle+0x15/0x20 Apr 26 08:03:29 192.168.122.209 [57559.565288] default_idle_call+0x66/0x160 Apr 26 08:03:29 192.168.122.209 [57559.565654] do_idle+0x36f/0x430 Apr 26 08:03:29 192.168.122.209 [57559.565951] ? arch_cpu_idle_exit+0x40/0x40 Apr 26 08:03:29 192.168.122.209 [57559.566324] cpu_startup_entry+0x20/0x30 Apr 26 08:03:29 192.168.122.209 [57559.566684] start_secondary+0x1c1/0x210 Apr 26 08:03:29 192.168.122.209 [57559.567036] ? set_cpu_sibling_map+0xd70/0xd70 Apr 26 08:03:29 192.168.122.209 [57559.567439] ? set_bringup_idt_handler.constprop.0+0x84/0x90 Apr 26 08:03:29 192.168.122.209 [57559.567940] ? start_cpu0+0xc/0xc Apr 26 08:03:29 192.168.122.209 [57559.568240] secondary_startup_64_no_verify+0xb0/0xbb Apr 26 08:03:29 192.168.122.209 [57559.568736] Mem-Info: Apr 26 08:03:29 192.168.122.209 [57559.568963] active_anon:32398 inactive_anon:97870 isolated_anon:0 [57559.568963] active_file:98023 inactive_file:102656 isolated_file:0 [57559.568963] unevictable:6821 dirty:16 writeback:0 [57559.568963] slab_reclaimable:23868 slab_unreclaimable:99198 [57559.568963] mapped:37283 shmem:426 pagetables:1341 bounce:0 [57559.568963] free:69772 free_pcp:1717 free_cma:0 Apr 26 08:03:29 192.168.122.209 [57559.571805] Node 0 active_anon:129592kB inactive_anon:391480kB active_file:392092kB inactive_file:410624kB unevictable:27284kB isolated(anon):0kB isolated(file):0kB mapped:149132kB dirty:188kB writeback:0kB shmem:1704kB shmem_thp: 0kB shmem_pmdmapped: 0kB anon_thp: 0kB writeback_tmp:0kB kernel_stack:9568kB all_unreclaimable? no Apr 26 08:03:29 192.168.122.209 [57559.574318] Node 0 DMA free:11904kB min:408kB low:508kB high:608kB reserved_highatomic:4096KB active_anon:8kB inactive_anon:36kB active_file:0kB inactive_file:8kB unevictable:0kB writepending:0kB present:15992kB managed:15908kB mlocked:0kB pagetables:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB Apr 26 08:03:29 192.168.122.209 [57559.576950] lowmem_reserve[]: 0 1900 2534 2534 2534 Apr 26 08:03:29 192.168.122.209 [57559.577408] Node 0 DMA32 free:241192kB min:50364kB low:62952kB high:75540kB reserved_highatomic:0KB active_anon:123736kB inactive_anon:352696kB active_file:313768kB inactive_file:381664kB unevictable:0kB writepending:20kB present:2080624kB managed:1946020kB mlocked:0kB pagetables:672kB bounce:0kB free_pcp:4328kB local_pcp:364kB free_cma:0kB Apr 26 08:03:29 192.168.122.209 [57559.579998] lowmem_reserve[]: 0 0 634 634 634 Apr 26 08:03:29 192.168.122.209 [57559.580416] Node 0 Normal free:25992kB min:16804kB low:21004kB high:25204kB reserved_highatomic:2048KB active_anon:5848kB inactive_anon:38748kB active_file:77952kB inactive_file:29276kB unevictable:27284kB writepending:44kB present:2097152kB managed:649288kB mlocked:27284kB pagetables:4692kB bounce:0kB free_pcp:2496kB local_pcp:604kB free_cma:0kB Apr 26 08:03:29 192.168.122.209 [57559.583082] lowmem_reserve[]: 0 0 0 0 0 Apr 26 08:03:29 192.168.122.209 [57559.583443] Node 0 DMA: 14*4kB (MH) 21*8kB (ME) 22*16kB (MEH) 18*32kB (MEH) 16*64kB (MEH) 10*128kB (MEH) 5*256kB (MEH) 4*512kB (MH) 3*1024kB (ME) 1*2048kB (U) 0*4096kB = 11904kB Apr 26 08:03:29 192.168.122.209 [57559.584866] Node 0 DMA32: 1238*4kB (UME) 1996*8kB (UME) 1507*16kB (UME) 1927*32kB (UME) 1520*64kB (UME) 229*128kB (UME) 31*256kB (UE) 0*512kB 0*1024kB 0*2048kB 0*4096kB = 241224kB Apr 26 08:03:29 192.168.122.209 [57559.586302] Node 0 Normal: 1795*4kB (UMEH) 562*8kB (UMEH) 111*16kB (UMEH) 323*32kB (UMEH) 24*64kB (UM) 1*128kB (U) 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 25452kB Apr 26 08:03:29 192.168.122.209 [57559.587681] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=1048576kB Apr 26 08:03:29 192.168.122.209 [57559.588444] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=2048kB Apr 26 08:03:29 192.168.122.209 [57559.589194] 261449 total pagecache pages Apr 26 08:03:29 192.168.122.209 [57559.589561] 58097 pages in swap cache Apr 26 08:03:29 192.168.122.209 [57559.589904] Swap cache stats: add 296895, delete 238800, find 369452/420285 Apr 26 08:03:29 192.168.122.209 [57559.590523] Free swap = 3757528kB Apr 26 08:03:29 192.168.122.209 [57559.590842] Total swap = 4194300kB Apr 26 08:03:29 192.168.122.209 [57559.591157] 1048442 pages RAM Apr 26 08:03:29 192.168.122.209 [57559.591437] 0 pages HighMem/MovableOnly Apr 26 08:03:29 192.168.122.209 [57559.591795] 395638 pages reserved Apr 26 08:03:29 192.168.122.209 [57559.592101] 0 pages cma reserved Apr 26 08:03:29 192.168.122.209 [57559.592401] 0 pages hwpoisoned Apr 26 08:03:29 192.168.122.209 [57559.592701] [tempesta fw] Warning: Cannot grow HTTP data string Apr 26 08:03:29 192.168.122.209 [57559.593238] [tempesta fw] Warning: Parser error: state=RGen_BodyParse input(-0)=0x31('1') data_len=1 off=0 Apr 26 08:03:29 192.168.122.209 [57559.717654] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 08:03:29 192.168.122.209 [57560.168225] [tdb] Close table 'client0.tdb' Apr 26 08:03:29 192.168.122.209 [57560.371564] [tdb] Close table 'sessions0.tdb' Apr 26 08:03:33 192.168.122.209 [57563.669262] [tdb] Close table 'cache0.tdb' Apr 26 08:03:33 192.168.122.209 [57563.944019] [tdb] Close table 'filter0.tdb' Apr 26 08:03:33 192.168.122.209 [57563.944481] [tempesta fw] modules are stopped Apr 26 08:03:33 192.168.122.209 [57564.184377] [tempesta fw] exiting... Apr 26 08:03:33 192.168.122.209 [57564.319739] [tdb] Shutdown Tempesta DB Apr 26 08:03:34 192.168.122.209 [57564.595610] End test: encoding.test_encoding.TestH2ChunkedWithLongBodyAndTrailer.test Apr 26 08:03:34 192.168.122.209 [57564.616949] Start test: encoding.test_encoding.TestH2ChunkedWithTrailer.test Apr 26 08:03:35 192.168.122.209 [57565.692892] [tdb] Start Tempesta DB Apr 26 08:03:35 192.168.122.209 [57565.855579] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:03:36 192.168.122.209 [57567.246471] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [57567.246471] Maybe that's fine, but it's worth checking the [57567.246471] config - if there is no relations between the [57567.246471] names, then host name confusion attack is possible. Apr 26 08:03:36 192.168.122.209 [57567.333168] [tempesta fw] Configuration processing is completed. Apr 26 08:03:36 192.168.122.209 [57567.389274] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:03:37 192.168.122.209 [57567.824595] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:03:37 192.168.122.209 [57567.852515] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:03:37 192.168.122.209 [57567.881764] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:03:37 192.168.122.209 [57567.925110] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:03:37 192.168.122.209 [57567.926232] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:03:37 192.168.122.209 [57567.965084] [tempesta fw] Tempesta FW is ready Apr 26 08:03:38 192.168.122.209 [57568.656728] [tdb] Close table 'client0.tdb' Apr 26 08:03:38 192.168.122.209 [57568.852553] [tdb] Close table 'sessions0.tdb' Apr 26 08:03:41 192.168.122.209 [57572.073945] [tdb] Close table 'cache0.tdb' Apr 26 08:03:41 192.168.122.209 [57572.335822] [tdb] Close table 'filter0.tdb' Apr 26 08:03:41 192.168.122.209 [57572.336252] [tempesta fw] modules are stopped Apr 26 08:03:42 192.168.122.209 [57572.545610] [tempesta fw] exiting... Apr 26 08:03:42 192.168.122.209 [57572.664596] [tdb] Shutdown Tempesta DB Apr 26 08:03:42 192.168.122.209 [57572.881916] End test: encoding.test_encoding.TestH2ChunkedWithTrailer.test Apr 26 08:03:42 192.168.122.209 [57572.901729] Start test: encoding.test_encoding.TestH2EmptyResponseBodyDechunking.test Apr 26 08:03:43 192.168.122.209 [57573.966125] [tdb] Start Tempesta DB Apr 26 08:03:43 192.168.122.209 [57574.124581] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:03:44 192.168.122.209 [57575.458818] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [57575.458818] Maybe that's fine, but it's worth checking the [57575.458818] config - if there is no relations between the [57575.458818] names, then host name confusion attack is possible. Apr 26 08:03:45 192.168.122.209 [57575.557282] [tempesta fw] Configuration processing is completed. Apr 26 08:03:45 192.168.122.209 [57575.612320] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:03:45 192.168.122.209 [57576.114057] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:03:45 192.168.122.209 [57576.146197] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:03:45 192.168.122.209 [57576.178084] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:03:45 192.168.122.209 [57576.221187] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:03:45 192.168.122.209 [57576.261196] [tempesta fw] Tempesta FW is ready Apr 26 08:03:46 192.168.122.209 [57576.909872] [tdb] Close table 'client0.tdb' Apr 26 08:03:46 192.168.122.209 [57577.115618] [tdb] Close table 'sessions0.tdb' Apr 26 08:03:49 192.168.122.209 [57580.354288] [tdb] Close table 'cache0.tdb' Apr 26 08:03:50 192.168.122.209 [57580.600265] [tdb] Close table 'filter0.tdb' Apr 26 08:03:50 192.168.122.209 [57580.600694] [tempesta fw] modules are stopped Apr 26 08:03:50 192.168.122.209 [57580.801170] [tempesta fw] exiting... Apr 26 08:03:50 192.168.122.209 [57580.945046] [tdb] Shutdown Tempesta DB Apr 26 08:03:50 192.168.122.209 [57581.166293] End test: encoding.test_encoding.TestH2EmptyResponseBodyDechunking.test Apr 26 08:03:50 192.168.122.209 [57581.183602] Start test: encoding.test_encoding.TestH2EmptyResponseBodyDechunkingHead.test Apr 26 08:03:51 192.168.122.209 [57582.262690] [tdb] Start Tempesta DB Apr 26 08:03:51 192.168.122.209 [57582.415304] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:03:53 192.168.122.209 [57583.770687] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [57583.770687] Maybe that's fine, but it's worth checking the [57583.770687] config - if there is no relations between the [57583.770687] names, then host name confusion attack is possible. Apr 26 08:03:53 192.168.122.209 [57583.853287] [tempesta fw] Configuration processing is completed. Apr 26 08:03:53 192.168.122.209 [57583.927411] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:03:53 192.168.122.209 [57584.413100] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:03:53 192.168.122.209 [57584.443456] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:03:53 192.168.122.209 [57584.480524] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:03:54 192.168.122.209 [57584.541389] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:03:54 192.168.122.209 [57584.581290] [tempesta fw] Tempesta FW is ready Apr 26 08:03:54 192.168.122.209 [57585.319029] [tdb] Close table 'client0.tdb' Apr 26 08:03:54 192.168.122.209 [57585.512663] [tdb] Close table 'sessions0.tdb' Apr 26 08:03:58 192.168.122.209 [57588.847619] [tdb] Close table 'cache0.tdb' Apr 26 08:03:58 192.168.122.209 [57589.077926] [tdb] Close table 'filter0.tdb' Apr 26 08:03:58 192.168.122.209 [57589.078370] [tempesta fw] modules are stopped Apr 26 08:03:58 192.168.122.209 [57589.286716] [tempesta fw] exiting... Apr 26 08:03:58 192.168.122.209 [57589.419468] [tdb] Shutdown Tempesta DB Apr 26 08:03:59 192.168.122.209 [57589.683804] End test: encoding.test_encoding.TestH2EmptyResponseBodyDechunkingHead.test Apr 26 08:03:59 192.168.122.209 [57589.702794] Start test: encoding.test_encoding.TestH2LargeResponseBodyDechunking.test Apr 26 08:04:00 192.168.122.209 [57590.691483] [tdb] Start Tempesta DB Apr 26 08:04:00 192.168.122.209 [57590.839401] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:04:01 192.168.122.209 [57592.142817] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [57592.142817] Maybe that's fine, but it's worth checking the [57592.142817] config - if there is no relations between the [57592.142817] names, then host name confusion attack is possible. Apr 26 08:04:01 192.168.122.209 [57592.229449] [tempesta fw] Configuration processing is completed. Apr 26 08:04:01 192.168.122.209 [57592.279719] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:04:02 192.168.122.209 [57592.727469] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:04:02 192.168.122.209 [57592.754784] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:04:02 192.168.122.209 [57592.789210] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:04:02 192.168.122.209 [57592.837439] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:04:02 192.168.122.209 [57592.877402] [tempesta fw] Tempesta FW is ready Apr 26 08:04:19 192.168.122.209 [57610.460848] [tdb] Close table 'client0.tdb' Apr 26 08:04:20 192.168.122.209 [57610.688296] [tdb] Close table 'sessions0.tdb' Apr 26 08:04:23 192.168.122.209 [57614.076777] [tdb] Close table 'cache0.tdb' Apr 26 08:04:23 192.168.122.209 [57614.327423] [tdb] Close table 'filter0.tdb' Apr 26 08:04:23 192.168.122.209 [57614.327850] [tempesta fw] modules are stopped Apr 26 08:04:23 192.168.122.209 [57614.508045] [tempesta fw] exiting... Apr 26 08:04:24 192.168.122.209 [57614.645023] [tdb] Shutdown Tempesta DB Apr 26 08:04:24 192.168.122.209 [57614.880320] End test: encoding.test_encoding.TestH2LargeResponseBodyDechunking.test Apr 26 08:04:24 192.168.122.209 [57614.903996] Start test: encoding.test_encoding.TestH2LargeResponseBodyDechunking2.test Apr 26 08:04:25 192.168.122.209 [57616.004207] [tdb] Start Tempesta DB Apr 26 08:04:25 192.168.122.209 [57616.162631] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:04:27 192.168.122.209 [57617.679374] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [57617.679374] Maybe that's fine, but it's worth checking the [57617.679374] config - if there is no relations between the [57617.679374] names, then host name confusion attack is possible. Apr 26 08:04:27 192.168.122.209 [57617.761787] [tempesta fw] Configuration processing is completed. Apr 26 08:04:27 192.168.122.209 [57617.818961] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:04:27 192.168.122.209 [57618.255393] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:04:27 192.168.122.209 [57618.282786] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:04:27 192.168.122.209 [57618.311210] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:04:27 192.168.122.209 [57618.349771] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:04:27 192.168.122.209 [57618.397749] [tempesta fw] Tempesta FW is ready Apr 26 08:04:42 192.168.122.209 [57633.051403] swapper/3: page allocation failure: order:9, mode:0x40a20(GFP_ATOMIC|__GFP_COMP), nodemask=(null),cpuset=/,mems_allowed=0 Apr 26 08:04:42 192.168.122.209 [57633.052550] CPU: 3 PID: 0 Comm: swapper/3 Tainted: G OE 5.10.35.tfw-39c65d3-debug #1 Apr 26 08:04:42 192.168.122.209 [57633.053335] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 Apr 26 08:04:42 192.168.122.209 [57633.054163] Call Trace: Apr 26 08:04:42 192.168.122.209 [57633.054391] Apr 26 08:04:42 192.168.122.209 [57633.054636] dump_stack+0x96/0xc4 Apr 26 08:04:42 192.168.122.209 [57633.054946] warn_alloc.cold+0x87/0x12a Apr 26 08:04:42 192.168.122.209 [57633.055317] ? zone_watermark_ok_safe+0x140/0x140 Apr 26 08:04:42 192.168.122.209 [57633.055749] ? __kasan_check_read+0x11/0x20 Apr 26 08:04:42 192.168.122.209 [57633.056143] ? wakeup_kswapd+0xba/0x290 Apr 26 08:04:42 192.168.122.209 [57633.056496] ? __zone_watermark_ok+0x270/0x270 Apr 26 08:04:42 192.168.122.209 [57633.056895] ? wake_all_kswapds+0xf4/0x140 Apr 26 08:04:42 192.168.122.209 [57633.057265] ? __alloc_pages_slowpath.constprop.0+0x11f4/0x1390 Apr 26 08:04:42 192.168.122.209 [57633.057799] __alloc_pages_slowpath.constprop.0+0x1359/0x1390 Apr 26 08:04:42 192.168.122.209 [57633.058313] ? warn_alloc+0x120/0x120 Apr 26 08:04:42 192.168.122.209 [57633.058659] ? enqueue_to_backlog+0x430/0x430 Apr 26 08:04:42 192.168.122.209 [57633.059059] ? eth_type_trans+0x195/0x2f0 Apr 26 08:04:42 192.168.122.209 [57633.059424] ? __zone_watermark_ok+0x270/0x270 Apr 26 08:04:42 192.168.122.209 [57633.059830] __alloc_pages_nodemask+0x509/0x540 Apr 26 08:04:42 192.168.122.209 [57633.060236] ? __alloc_pages_slowpath.constprop.0+0x1390/0x1390 Apr 26 08:04:42 192.168.122.209 [57633.060763] ? netdev_core_pick_tx+0xb0/0x120 Apr 26 08:04:42 192.168.122.209 [57633.061171] ? __dev_queue_xmit+0x6e9/0xf90 Apr 26 08:04:42 192.168.122.209 [57633.061558] alloc_pages_current+0x96/0x140 Apr 26 08:04:42 192.168.122.209 [57633.061935] __get_free_pages+0x12/0x60 Apr 26 08:04:42 192.168.122.209 [57633.062322] tfw_pool_alloc_pages+0x9b/0xc0 [tempesta_fw] Apr 26 08:04:42 192.168.122.209 [57633.062835] __tfw_pool_realloc+0x123/0x1a0 [tempesta_fw] Apr 26 08:04:42 192.168.122.209 [57633.063347] __str_grow_tree+0x89/0x210 [tempesta_fw] Apr 26 08:04:42 192.168.122.209 [57633.063825] tfw_str_add_compound+0x33/0x40 [tempesta_fw] Apr 26 08:04:42 192.168.122.209 [57633.064331] __resp_parse_body+0x421/0xb50 [tempesta_fw] Apr 26 08:04:42 192.168.122.209 [57633.064833] tfw_http_parse_resp+0x15e8/0x197d0 [tempesta_fw] Apr 26 08:04:42 192.168.122.209 [57633.065370] ? __resp_parse_body+0xb50/0xb50 [tempesta_fw] Apr 26 08:04:42 192.168.122.209 [57633.065886] ss_skb_process+0x270/0x2f0 [tempesta_fw] Apr 26 08:04:42 192.168.122.209 [57633.066362] ? __resp_parse_body+0xb50/0xb50 [tempesta_fw] Apr 26 08:04:42 192.168.122.209 [57633.066890] ? tfw_sock_srv_exit+0x30/0x30 [tempesta_fw] Apr 26 08:04:42 192.168.122.209 [57633.067374] ? __ip_finish_output+0x340/0x340 Apr 26 08:04:42 192.168.122.209 [57633.067793] tfw_http_msg_process_generic+0x282/0xc70 [tempesta_fw] Apr 26 08:04:42 192.168.122.209 [57633.068370] ? tfw_http_req_process+0x11a0/0x11a0 [tempesta_fw] Apr 26 08:04:42 192.168.122.209 [57633.068904] ? pg_skb_alloc+0x60e/0x680 Apr 26 08:04:42 192.168.122.209 [57633.069254] ? __kasan_check_write+0x14/0x20 Apr 26 08:04:42 192.168.122.209 [57633.069639] ? __alloc_skb+0x278/0x350 Apr 26 08:04:42 192.168.122.209 [57633.069980] ? __kasan_check_write+0x14/0x20 Apr 26 08:04:42 192.168.122.209 [57633.070394] ? __coalesce_frag+0x136/0x370 [tempesta_fw] Apr 26 08:04:42 192.168.122.209 [57633.070895] tfw_http_msg_process+0x80/0xc0 [tempesta_fw] Apr 26 08:04:42 192.168.122.209 [57633.071371] ? skb_release_data+0x8c/0x320 Apr 26 08:04:42 192.168.122.209 [57633.071765] tfw_connection_recv+0x12e/0x250 [tempesta_fw] Apr 26 08:04:42 192.168.122.209 [57633.072277] ? tfw_connection_send+0x70/0x70 [tempesta_fw] Apr 26 08:04:42 192.168.122.209 [57633.072792] ? ss_skb_unroll+0x3d6/0x540 [tempesta_fw] Apr 26 08:04:42 192.168.122.209 [57633.073275] ss_tcp_process_data+0x436/0x8b0 [tempesta_fw] Apr 26 08:04:42 192.168.122.209 [57633.073791] ? __sk_close_locked+0x100/0x100 [tempesta_fw] Apr 26 08:04:42 192.168.122.209 [57633.074293] ? mod_timer+0x10/0x20 Apr 26 08:04:42 192.168.122.209 [57633.074609] ? sk_reset_timer+0x1a/0x70 Apr 26 08:04:42 192.168.122.209 [57633.074980] ss_tcp_data_ready+0x7b/0x150 [tempesta_fw] Apr 26 08:04:42 192.168.122.209 [57633.075447] tcp_data_ready+0x73/0x210 Apr 26 08:04:42 192.168.122.209 [57633.075792] tcp_rcv_established+0x95b/0xb40 Apr 26 08:04:42 192.168.122.209 [57633.076176] ? tcp_data_queue+0x1d80/0x1d80 Apr 26 08:04:42 192.168.122.209 [57633.076555] ? __kasan_check_read+0x11/0x20 Apr 26 08:04:42 192.168.122.209 [57633.076930] tcp_v4_do_rcv+0x25f/0x360 Apr 26 08:04:42 192.168.122.209 [57633.077272] tcp_v4_rcv+0x1600/0x1770 Apr 26 08:04:42 192.168.122.209 [57633.077609] ? tcp_v4_early_demux+0x2f0/0x2f0 Apr 26 08:04:42 192.168.122.209 [57633.078001] ip_protocol_deliver_rcu+0x46/0x2e0 Apr 26 08:04:42 192.168.122.209 [57633.078404] ip_local_deliver_finish+0xc6/0xe0 Apr 26 08:04:42 192.168.122.209 [57633.078806] ip_local_deliver+0x1f5/0x210 Apr 26 08:04:42 192.168.122.209 [57633.079168] ? ip_local_deliver_finish+0xe0/0xe0 Apr 26 08:04:42 192.168.122.209 [57633.079600] ? nf_nat_inet_fn+0x2b3/0x440 [nf_nat] Apr 26 08:04:42 192.168.122.209 [57633.080026] ? ip_protocol_deliver_rcu+0x2e0/0x2e0 Apr 26 08:04:42 192.168.122.209 [57633.080454] ? ip_rcv_finish_core.constprop.0+0x17c/0x890 Apr 26 08:04:42 192.168.122.209 [57633.080940] ip_rcv_finish+0xcf/0xf0 Apr 26 08:04:42 192.168.122.209 [57633.081263] ip_rcv+0x16d/0x180 Apr 26 08:04:42 192.168.122.209 [57633.081554] ? ip_local_deliver+0x210/0x210 Apr 26 08:04:42 192.168.122.209 [57633.081949] ? find_first_bit+0x2e/0x50 Apr 26 08:04:42 192.168.122.209 [57633.082298] ? ip_rcv_finish_core.constprop.0+0x890/0x890 Apr 26 08:04:42 192.168.122.209 [57633.082786] ? try_to_wake_up+0x41e/0xa70 Apr 26 08:04:42 192.168.122.209 [57633.083146] ? ip_local_deliver+0x210/0x210 Apr 26 08:04:42 192.168.122.209 [57633.083527] __netif_receive_skb_one_core+0x132/0x140 Apr 26 08:04:42 192.168.122.209 [57633.083976] ? napi_gro_receive+0x260/0x260 Apr 26 08:04:42 192.168.122.209 [57633.084354] ? find_busiest_group+0x580/0x580 Apr 26 08:04:42 192.168.122.209 [57633.084747] ? __kasan_check_write+0x14/0x20 Apr 26 08:04:42 192.168.122.209 [57633.085146] ? _raw_spin_lock+0x7b/0xd0 Apr 26 08:04:42 192.168.122.209 [57633.085498] __netif_receive_skb+0x26/0xb0 Apr 26 08:04:42 192.168.122.209 [57633.085871] ? generic_exec_single+0xb1/0x170 Apr 26 08:04:42 192.168.122.209 [57633.086259] process_backlog+0xfe/0x290 Apr 26 08:04:42 192.168.122.209 [57633.086609] net_rx_action+0x287/0x6b0 Apr 26 08:04:42 192.168.122.209 [57633.086949] ? napi_complete_done+0x2c0/0x2c0 Apr 26 08:04:42 192.168.122.209 [57633.087353] ? switch_fpu_return+0x120/0x120 Apr 26 08:04:42 192.168.122.209 [57633.087737] __do_softirq+0xfe/0x383 Apr 26 08:04:42 192.168.122.209 [57633.088063] asm_call_irq_on_stack+0xf/0x20 Apr 26 08:04:42 192.168.122.209 [57633.088439] Apr 26 08:04:42 192.168.122.209 [57633.088644] do_softirq_own_stack+0x3d/0x50 Apr 26 08:04:42 192.168.122.209 [57633.089026] irq_exit_rcu+0xc7/0x120 Apr 26 08:04:42 192.168.122.209 [57633.089358] sysvec_call_function_single+0x3a/0x90 Apr 26 08:04:42 192.168.122.209 [57633.089792] asm_sysvec_call_function_single+0x12/0x20 Apr 26 08:04:42 192.168.122.209 [57633.090247] RIP: 0010:native_safe_halt+0xe/0x10 Apr 26 08:04:42 192.168.122.209 [57633.090656] Code: 49 8b 04 24 a8 08 0f 85 71 ff ff ff e9 0f ff ff ff cc cc cc cc cc cc cc cc cc cc cc e9 07 00 00 00 0f 00 2d d4 62 51 00 fb f4 90 e9 07 00 00 00 0f 00 2d c4 62 51 00 f4 c3 cc cc 0f 1f 44 00 Apr 26 08:04:42 192.168.122.209 [57633.092276] RSP: 0018:ffff888100f47db8 EFLAGS: 00000216 Apr 26 08:04:42 192.168.122.209 [57633.092748] RAX: ffffffffb63426a0 RBX: ffff888100f28040 RCX: ffffffffb632c475 Apr 26 08:04:42 192.168.122.209 [57633.093371] RDX: 0000000019a0ab8e RSI: 0000000000000004 RDI: ffff888147fb5040 Apr 26 08:04:42 192.168.122.209 [57633.093997] RBP: ffff888100f47dc0 R08: 0000000000000001 R09: ffff888147fb5043 Apr 26 08:04:42 192.168.122.209 [57633.094625] R10: ffffed1028ff6a08 R11: 0000000000000001 R12: 0000000000000003 Apr 26 08:04:42 192.168.122.209 [57633.095252] R13: ffffffffb7ae9360 R14: 0000000000000000 R15: 0000000000000000 Apr 26 08:04:42 192.168.122.209 [57633.095879] ? __cpuidle_text_start+0x8/0x8 Apr 26 08:04:42 192.168.122.209 [57633.096254] ? rcu_eqs_enter.constprop.0+0x85/0xa0 Apr 26 08:04:42 192.168.122.209 [57633.096693] ? default_idle+0xe/0x20 Apr 26 08:04:42 192.168.122.209 [57633.097019] arch_cpu_idle+0x15/0x20 Apr 26 08:04:42 192.168.122.209 [57633.097342] default_idle_call+0x66/0x160 Apr 26 08:04:42 192.168.122.209 [57633.097707] do_idle+0x36f/0x430 Apr 26 08:04:42 192.168.122.209 [57633.098007] ? asm_sysvec_call_function_single+0x12/0x20 Apr 26 08:04:42 192.168.122.209 [57633.098491] ? arch_cpu_idle_exit+0x40/0x40 Apr 26 08:04:42 192.168.122.209 [57633.098865] cpu_startup_entry+0x20/0x30 Apr 26 08:04:42 192.168.122.209 [57633.099224] start_secondary+0x1c1/0x210 Apr 26 08:04:42 192.168.122.209 [57633.099584] ? set_cpu_sibling_map+0xd70/0xd70 Apr 26 08:04:42 192.168.122.209 [57633.099989] ? set_bringup_idt_handler.constprop.0+0x84/0x90 Apr 26 08:04:42 192.168.122.209 [57633.100493] ? start_cpu0+0xc/0xc Apr 26 08:04:42 192.168.122.209 [57633.100794] secondary_startup_64_no_verify+0xb0/0xbb Apr 26 08:04:42 192.168.122.209 [57633.101273] Mem-Info: Apr 26 08:04:42 192.168.122.209 [57633.101503] active_anon:32398 inactive_anon:97833 isolated_anon:0 [57633.101503] active_file:99468 inactive_file:98568 isolated_file:0 [57633.101503] unevictable:6821 dirty:111 writeback:0 [57633.101503] slab_reclaimable:23876 slab_unreclaimable:99034 [57633.101503] mapped:37081 shmem:426 pagetables:1340 bounce:0 [57633.101503] free:88900 free_pcp:1605 free_cma:0 Apr 26 08:04:42 192.168.122.209 [57633.104363] Node 0 active_anon:129592kB inactive_anon:391332kB active_file:397872kB inactive_file:394272kB unevictable:27284kB isolated(anon):0kB isolated(file):0kB mapped:148324kB dirty:692kB writeback:0kB shmem:1704kB shmem_thp: 0kB shmem_pmdmapped: 0kB anon_thp: 0kB writeback_tmp:0kB kernel_stack:9664kB all_unreclaimable? no Apr 26 08:04:42 192.168.122.209 [57633.106891] Node 0 DMA free:11904kB min:408kB low:508kB high:608kB reserved_highatomic:4096KB active_anon:8kB inactive_anon:36kB active_file:0kB inactive_file:8kB unevictable:0kB writepending:0kB present:15992kB managed:15908kB mlocked:0kB pagetables:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB Apr 26 08:04:42 192.168.122.209 [57633.109241] lowmem_reserve[]: 0 1900 2534 2534 2534 Apr 26 08:04:42 192.168.122.209 [57633.109699] Node 0 DMA32 free:318640kB min:50364kB low:62952kB high:75540kB reserved_highatomic:0KB active_anon:123736kB inactive_anon:352352kB active_file:315808kB inactive_file:365868kB unevictable:0kB writepending:180kB present:2080624kB managed:1946020kB mlocked:0kB pagetables:668kB bounce:0kB free_pcp:4380kB local_pcp:548kB free_cma:0kB Apr 26 08:04:42 192.168.122.209 [57633.112333] lowmem_reserve[]: 0 0 634 634 634 Apr 26 08:04:42 192.168.122.209 [57633.112746] Node 0 Normal free:24552kB min:16804kB low:21004kB high:25204kB reserved_highatomic:2048KB active_anon:5848kB inactive_anon:38944kB active_file:81568kB inactive_file:29176kB unevictable:27284kB writepending:1016kB present:2097152kB managed:649288kB mlocked:27284kB pagetables:4692kB bounce:0kB free_pcp:2012kB local_pcp:328kB free_cma:0kB Apr 26 08:04:42 192.168.122.209 [57633.115404] lowmem_reserve[]: 0 0 0 0 0 Apr 26 08:04:42 192.168.122.209 [57633.115775] Node 0 DMA: 14*4kB (MH) 21*8kB (ME) 22*16kB (MEH) 18*32kB (MEH) 16*64kB (MEH) 10*128kB (MEH) 5*256kB (MEH) 4*512kB (MH) 3*1024kB (ME) 1*2048kB (U) 0*4096kB = 11904kB Apr 26 08:04:42 192.168.122.209 [57633.117233] Node 0 DMA32: 1082*4kB (UME) 1973*8kB (UME) 2417*16kB (UME) 2019*32kB (UME) 2367*64kB (UME) 285*128kB (UME) 31*256kB (UE) 0*512kB 0*1024kB 0*2048kB 0*4096kB = 319296kB Apr 26 08:04:42 192.168.122.209 [57633.118696] Node 0 Normal: 1420*4kB (UMEH) 223*8kB (MEH) 295*16kB (UMEH) 348*32kB (UEH) 22*64kB (U) 1*128kB (U) 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 24856kB Apr 26 08:04:42 192.168.122.209 [57633.120056] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=1048576kB Apr 26 08:04:42 192.168.122.209 [57633.120852] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=2048kB Apr 26 08:04:42 192.168.122.209 [57633.121598] 258781 total pagecache pages Apr 26 08:04:42 192.168.122.209 [57633.121968] 58095 pages in swap cache Apr 26 08:04:42 192.168.122.209 [57633.122306] Swap cache stats: add 296896, delete 238803, find 369670/420504 Apr 26 08:04:42 192.168.122.209 [57633.122928] Free swap = 3757528kB Apr 26 08:04:42 192.168.122.209 [57633.123242] Total swap = 4194300kB Apr 26 08:04:42 192.168.122.209 [57633.123560] 1048442 pages RAM Apr 26 08:04:42 192.168.122.209 [57633.123840] 0 pages HighMem/MovableOnly Apr 26 08:04:42 192.168.122.209 [57633.124194] 395638 pages reserved Apr 26 08:04:42 192.168.122.209 [57633.124503] 0 pages cma reserved Apr 26 08:04:42 192.168.122.209 [57633.124803] 0 pages hwpoisoned Apr 26 08:04:42 192.168.122.209 [57633.125092] [tempesta fw] Warning: Cannot grow HTTP data string Apr 26 08:04:42 192.168.122.209 [57633.125629] [tempesta fw] Warning: Parser error: state=RGen_BodyParse input(-0)=0xd(' ') data_len=1 off=0 Apr 26 08:04:42 192.168.122.209 [57633.214429] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 08:04:43 192.168.122.209 [57633.600848] [tdb] Close table 'client0.tdb' Apr 26 08:04:43 192.168.122.209 [57633.793221] [tdb] Close table 'sessions0.tdb' Apr 26 08:04:46 192.168.122.209 [57636.988461] [tdb] Close table 'cache0.tdb' Apr 26 08:04:46 192.168.122.209 [57637.212452] [tdb] Close table 'filter0.tdb' Apr 26 08:04:46 192.168.122.209 [57637.212894] [tempesta fw] modules are stopped Apr 26 08:04:46 192.168.122.209 [57637.424144] [tempesta fw] exiting... Apr 26 08:04:47 192.168.122.209 [57637.553367] [tdb] Shutdown Tempesta DB Apr 26 08:04:47 192.168.122.209 [57637.798686] End test: encoding.test_encoding.TestH2LargeResponseBodyDechunking2.test Apr 26 08:04:47 192.168.122.209 [57637.816477] Start test: encoding.test_encoding.TestH2TEMovedToCE.test Apr 26 08:04:48 192.168.122.209 [57638.877974] [tdb] Start Tempesta DB Apr 26 08:04:48 192.168.122.209 [57639.014982] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:04:49 192.168.122.209 [57640.255381] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [57640.255381] Maybe that's fine, but it's worth checking the [57640.255381] config - if there is no relations between the [57640.255381] names, then host name confusion attack is possible. Apr 26 08:04:49 192.168.122.209 [57640.350078] [tempesta fw] Configuration processing is completed. Apr 26 08:04:49 192.168.122.209 [57640.401471] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:04:50 192.168.122.209 [57640.831871] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:04:50 192.168.122.209 [57640.859514] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:04:50 192.168.122.209 [57640.889116] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:04:50 192.168.122.209 [57640.938062] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:04:50 192.168.122.209 [57640.982007] [tempesta fw] Tempesta FW is ready Apr 26 08:04:51 192.168.122.209 [57641.610409] [tdb] Close table 'client0.tdb' Apr 26 08:04:51 192.168.122.209 [57641.808682] [tdb] Close table 'sessions0.tdb' Apr 26 08:04:54 192.168.122.209 [57645.026850] [tdb] Close table 'cache0.tdb' Apr 26 08:04:54 192.168.122.209 [57645.276455] [tdb] Close table 'filter0.tdb' Apr 26 08:04:54 192.168.122.209 [57645.276900] [tempesta fw] modules are stopped Apr 26 08:04:54 192.168.122.209 [57645.514196] [tempesta fw] exiting... Apr 26 08:04:55 192.168.122.209 [57645.654136] [tdb] Shutdown Tempesta DB Apr 26 08:04:55 192.168.122.209 [57645.871502] End test: encoding.test_encoding.TestH2TEMovedToCE.test Apr 26 08:04:55 192.168.122.209 [57645.888909] Start test: encoding.test_encoding.TestRequestChunkedNotLast.test Apr 26 08:04:56 192.168.122.209 [57647.023550] [tdb] Start Tempesta DB Apr 26 08:04:56 192.168.122.209 [57647.166721] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:04:57 192.168.122.209 [57648.294910] [tempesta fw] Configuration processing is completed. Apr 26 08:04:57 192.168.122.209 [57648.340165] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:04:58 192.168.122.209 [57648.792175] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:04:58 192.168.122.209 [57648.820165] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:04:58 192.168.122.209 [57648.847662] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:04:58 192.168.122.209 [57648.890199] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:04:58 192.168.122.209 [57648.934102] [tempesta fw] Tempesta FW is ready Apr 26 08:04:58 192.168.122.209 [57649.079845] [tempesta fw] Warning: Parser error: state=Req_HdrTransfer_EncodingV input(-0)=0xd(' ') data_len=1 off=0 Apr 26 08:04:58 192.168.122.209 [57649.513052] [tdb] Close table 'client0.tdb' Apr 26 08:04:59 192.168.122.209 [57649.699932] [tdb] Close table 'sessions0.tdb' Apr 26 08:05:02 192.168.122.209 [57652.871624] [tdb] Close table 'cache0.tdb' Apr 26 08:05:02 192.168.122.209 [57653.118736] [tdb] Close table 'filter0.tdb' Apr 26 08:05:02 192.168.122.209 [57653.119175] [tempesta fw] modules are stopped Apr 26 08:05:02 192.168.122.209 [57653.314817] [tempesta fw] exiting... Apr 26 08:05:02 192.168.122.209 [57653.430173] [tdb] Shutdown Tempesta DB Apr 26 08:05:03 192.168.122.209 [57653.626277] End test: encoding.test_encoding.TestRequestChunkedNotLast.test Apr 26 08:05:03 192.168.122.209 [57653.655311] Start test: encoding.test_encoding.TestRequestTEAndCL.test Apr 26 08:05:04 192.168.122.209 [57654.675537] [tdb] Start Tempesta DB Apr 26 08:05:04 192.168.122.209 [57654.818563] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:05:05 192.168.122.209 [57655.974512] [tempesta fw] Configuration processing is completed. Apr 26 08:05:05 192.168.122.209 [57656.023646] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:05:05 192.168.122.209 [57656.459202] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:05:05 192.168.122.209 [57656.486564] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:05:05 192.168.122.209 [57656.513548] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:05:06 192.168.122.209 [57656.570256] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:05:06 192.168.122.209 [57656.602240] [tempesta fw] Tempesta FW is ready Apr 26 08:05:06 192.168.122.209 [57656.768128] [tempesta fw] Warning: Transfer-Encoding chunked and Content-Length in same request considered as attempt to Request smuggling attack. Apr 26 08:05:06 192.168.122.209 [57657.210146] [tdb] Close table 'client0.tdb' Apr 26 08:05:06 192.168.122.209 [57657.398042] [tdb] Close table 'sessions0.tdb' Apr 26 08:05:10 192.168.122.209 [57660.635503] [tdb] Close table 'cache0.tdb' Apr 26 08:05:10 192.168.122.209 [57660.887075] [tdb] Close table 'filter0.tdb' Apr 26 08:05:10 192.168.122.209 [57660.887515] [tempesta fw] modules are stopped Apr 26 08:05:10 192.168.122.209 [57661.069960] [tempesta fw] exiting... Apr 26 08:05:10 192.168.122.209 [57661.205098] [tdb] Shutdown Tempesta DB Apr 26 08:05:10 192.168.122.209 [57661.444268] End test: encoding.test_encoding.TestRequestTEAndCL.test Apr 26 08:05:10 192.168.122.209 [57661.468547] Start test: forwarding.test_forwarded_hdr.TestForwardedBase.test_run Apr 26 08:05:10 192.168.122.209 [57661.492040] End test: forwarding.test_forwarded_hdr.TestForwardedBase.test_run Apr 26 08:05:10 192.168.122.209 [57661.511023] Start test: forwarding.test_forwarded_hdr.TestForwardedBaseDisallowed.test_run Apr 26 08:05:12 192.168.122.209 [57662.541106] [tdb] Start Tempesta DB Apr 26 08:05:12 192.168.122.209 [57662.682392] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:05:13 192.168.122.209 [57664.058372] [tempesta fw] Configuration processing is completed. Apr 26 08:05:13 192.168.122.209 [57664.103310] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:05:14 192.168.122.209 [57664.539471] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:05:14 192.168.122.209 [57664.566341] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:05:14 192.168.122.209 [57664.593016] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:05:14 192.168.122.209 [57664.638347] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:05:14 192.168.122.209 [57664.678292] [tempesta fw] Tempesta FW is ready Apr 26 08:05:14 192.168.122.209 [57664.829885] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0x30('0') data_len=1 off=0 Apr 26 08:05:14 192.168.122.209 [57664.845772] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0x36('6') data_len=1 off=0 Apr 26 08:05:14 192.168.122.209 [57664.867694] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0xd(' ') data_len=1 off=0 Apr 26 08:05:14 192.168.122.209 [57664.889925] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0xd(' ') data_len=1 off=0 Apr 26 08:05:14 192.168.122.209 [57664.907537] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0x5b('[') data_len=1 off=0 Apr 26 08:05:14 192.168.122.209 [57664.931575] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0x22('"') data_len=1 off=0 Apr 26 08:05:14 192.168.122.209 [57664.953977] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0x6b('k') data_len=1 off=0 Apr 26 08:05:14 192.168.122.209 [57664.971688] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0x5b('[') data_len=1 off=0 Apr 26 08:05:14 192.168.122.209 [57664.985147] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0x5d(']') data_len=1 off=0 Apr 26 08:05:14 192.168.122.209 [57665.006501] [tempesta fw] Warning: Parser error: state=RGen_EoL input(-0)=0x3b(';') data_len=1 off=0 Apr 26 08:05:14 192.168.122.209 [57665.028807] [tempesta fw] Warning: Parser error: state=RGen_EoL input(-0)=0x3b(';') data_len=1 off=0 Apr 26 08:05:14 192.168.122.209 [57665.046762] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0x6d('m') data_len=1 off=0 Apr 26 08:05:14 192.168.122.209 [57665.060848] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0x6d('m') data_len=1 off=0 Apr 26 08:05:14 192.168.122.209 [57665.082547] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0x24('$') data_len=1 off=0 Apr 26 08:05:14 192.168.122.209 [57665.101555] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0x22('"') data_len=1 off=0 Apr 26 08:05:14 192.168.122.209 [57665.115087] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0x24('$') data_len=1 off=0 Apr 26 08:05:14 192.168.122.209 [57665.135166] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0x22('"') data_len=1 off=0 Apr 26 08:05:14 192.168.122.209 [57665.156665] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0x22('"') data_len=1 off=0 Apr 26 08:05:14 192.168.122.209 [57665.179310] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0x2f('/') data_len=1 off=0 Apr 26 08:05:14 192.168.122.209 [57665.199354] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0x3b(';') data_len=1 off=0 Apr 26 08:05:14 192.168.122.209 [57665.209218] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0xd(' ') data_len=1 off=0 Apr 26 08:05:14 192.168.122.209 [57665.219455] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0xd(' ') data_len=1 off=0 Apr 26 08:05:15 192.168.122.209 [57665.634796] [tdb] Close table 'client0.tdb' Apr 26 08:05:15 192.168.122.209 [57665.816873] [tdb] Close table 'sessions0.tdb' Apr 26 08:05:18 192.168.122.209 [57669.054640] [tdb] Close table 'cache0.tdb' Apr 26 08:05:18 192.168.122.209 [57669.297762] [tdb] Close table 'filter0.tdb' Apr 26 08:05:18 192.168.122.209 [57669.298183] [tempesta fw] modules are stopped Apr 26 08:05:18 192.168.122.209 [57669.488985] [tempesta fw] exiting... Apr 26 08:05:19 192.168.122.209 [57669.600108] [tdb] Shutdown Tempesta DB Apr 26 08:05:19 192.168.122.209 [57669.835145] End test: forwarding.test_forwarded_hdr.TestForwardedBaseDisallowed.test_run Apr 26 08:05:19 192.168.122.209 [57669.854989] Start test: forwarding.test_forwarded_hdr.TestForwardedBaseMalicious.test_malicious Apr 26 08:05:20 192.168.122.209 [57670.890133] [tdb] Start Tempesta DB Apr 26 08:05:20 192.168.122.209 [57671.035418] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:05:21 192.168.122.209 [57672.374417] [tempesta fw] Configuration processing is completed. Apr 26 08:05:21 192.168.122.209 [57672.432998] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:05:22 192.168.122.209 [57672.858056] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:05:22 192.168.122.209 [57672.884492] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:05:22 192.168.122.209 [57672.911316] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:05:22 192.168.122.209 [57672.950462] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:05:22 192.168.122.209 [57672.998400] [tempesta fw] Tempesta FW is ready Apr 26 08:05:22 192.168.122.209 [57673.145776] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0x3c('<') data_len=1 off=0 Apr 26 08:05:22 192.168.122.209 [57673.166701] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0x3e('>') data_len=1 off=0 Apr 26 08:05:22 192.168.122.209 [57673.184951] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0x20(' ') data_len=1 off=0 Apr 26 08:05:22 192.168.122.209 [57673.198394] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0x27(''') data_len=1 off=0 Apr 26 08:05:22 192.168.122.209 [57673.209003] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0x3c('<') data_len=1 off=0 Apr 26 08:05:22 192.168.122.209 [57673.222048] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0x3e('>') data_len=1 off=0 Apr 26 08:05:22 192.168.122.209 [57673.233068] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0x20(' ') data_len=1 off=0 Apr 26 08:05:22 192.168.122.209 [57673.243441] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0x27(''') data_len=1 off=0 Apr 26 08:05:22 192.168.122.209 [57673.253824] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0x3c('<') data_len=1 off=0 Apr 26 08:05:22 192.168.122.209 [57673.264508] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0x3e('>') data_len=1 off=0 Apr 26 08:05:22 192.168.122.209 [57673.276175] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0x20(' ') data_len=1 off=0 Apr 26 08:05:22 192.168.122.209 [57673.285306] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0x27(''') data_len=1 off=0 Apr 26 08:05:22 192.168.122.209 [57673.297078] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0x3c('<') data_len=1 off=0 Apr 26 08:05:22 192.168.122.209 [57673.307636] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0x3e('>') data_len=1 off=0 Apr 26 08:05:22 192.168.122.209 [57673.320253] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0x20(' ') data_len=1 off=0 Apr 26 08:05:22 192.168.122.209 [57673.341480] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0x27(''') data_len=1 off=0 Apr 26 08:05:22 192.168.122.209 [57673.360974] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0x3c('<') data_len=1 off=0 Apr 26 08:05:22 192.168.122.209 [57673.383704] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0x3e('>') data_len=1 off=0 Apr 26 08:05:22 192.168.122.209 [57673.406969] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0x20(' ') data_len=1 off=0 Apr 26 08:05:22 192.168.122.209 [57673.416792] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0x27(''') data_len=1 off=0 Apr 26 08:05:22 192.168.122.209 [57673.430106] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0x3c('<') data_len=1 off=0 Apr 26 08:05:22 192.168.122.209 [57673.453695] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0x3e('>') data_len=1 off=0 Apr 26 08:05:22 192.168.122.209 [57673.477261] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0x20(' ') data_len=1 off=0 Apr 26 08:05:22 192.168.122.209 [57673.493460] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0x27(''') data_len=1 off=0 Apr 26 08:05:22 192.168.122.209 [57673.517001] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0x3c('<') data_len=1 off=0 Apr 26 08:05:23 192.168.122.209 [57673.539495] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0x3e('>') data_len=1 off=0 Apr 26 08:05:23 192.168.122.209 [57673.559387] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0x20(' ') data_len=1 off=0 Apr 26 08:05:23 192.168.122.209 [57673.579895] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0x27(''') data_len=1 off=0 Apr 26 08:05:23 192.168.122.209 [57673.605924] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0x3c('<') data_len=1 off=0 Apr 26 08:05:23 192.168.122.209 [57673.623608] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0x3e('>') data_len=1 off=0 Apr 26 08:05:23 192.168.122.209 [57673.644867] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0x20(' ') data_len=1 off=0 Apr 26 08:05:23 192.168.122.209 [57673.664986] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0x27(''') data_len=1 off=0 Apr 26 08:05:23 192.168.122.209 [57674.097396] [tdb] Close table 'client0.tdb' Apr 26 08:05:23 192.168.122.209 [57674.285913] [tdb] Close table 'sessions0.tdb' Apr 26 08:05:26 192.168.122.209 [57677.483424] [tdb] Close table 'cache0.tdb' Apr 26 08:05:27 192.168.122.209 [57677.719361] [tdb] Close table 'filter0.tdb' Apr 26 08:05:27 192.168.122.209 [57677.719795] [tempesta fw] modules are stopped Apr 26 08:05:27 192.168.122.209 [57677.916555] [tempesta fw] exiting... Apr 26 08:05:27 192.168.122.209 [57678.037778] [tdb] Shutdown Tempesta DB Apr 26 08:05:27 192.168.122.209 [57678.271917] End test: forwarding.test_forwarded_hdr.TestForwardedBaseMalicious.test_malicious Apr 26 08:05:27 192.168.122.209 [57678.287661] Start test: forwarding.test_forwarded_hdr.TestForwardedBaseMalicious.test_run Apr 26 08:05:28 192.168.122.209 [57679.378243] [tdb] Start Tempesta DB Apr 26 08:05:28 192.168.122.209 [57679.521797] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:05:30 192.168.122.209 [57680.958602] [tempesta fw] Configuration processing is completed. Apr 26 08:05:30 192.168.122.209 [57681.012061] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:05:30 192.168.122.209 [57681.433922] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:05:30 192.168.122.209 [57681.462225] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:05:30 192.168.122.209 [57681.489354] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:05:31 192.168.122.209 [57681.530576] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:05:31 192.168.122.209 [57681.570507] [tempesta fw] Tempesta FW is ready Apr 26 08:05:31 192.168.122.209 [57681.722228] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0x25('%') data_len=1 off=0 Apr 26 08:05:31 192.168.122.209 [57681.740538] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0x25('%') data_len=1 off=0 Apr 26 08:05:31 192.168.122.209 [57681.765030] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0x25('%') data_len=1 off=0 Apr 26 08:05:31 192.168.122.209 [57681.781205] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0x25('%') data_len=1 off=0 Apr 26 08:05:31 192.168.122.209 [57681.791533] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0x25('%') data_len=1 off=0 Apr 26 08:05:31 192.168.122.209 [57681.804815] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0x25('%') data_len=1 off=0 Apr 26 08:05:31 192.168.122.209 [57681.834793] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0x25('%') data_len=1 off=0 Apr 26 08:05:31 192.168.122.209 [57681.862754] [tempesta fw] Warning: Parser error: state=Req_HdrForwardedV input(-0)=0x25('%') data_len=1 off=0 Apr 26 08:05:31 192.168.122.209 [57682.326125] [tdb] Close table 'client0.tdb' Apr 26 08:05:31 192.168.122.209 [57682.513268] [tdb] Close table 'sessions0.tdb' Apr 26 08:05:35 192.168.122.209 [57685.685526] [tdb] Close table 'cache0.tdb' Apr 26 08:05:35 192.168.122.209 [57685.934661] [tdb] Close table 'filter0.tdb' Apr 26 08:05:35 192.168.122.209 [57685.935094] [tempesta fw] modules are stopped Apr 26 08:05:35 192.168.122.209 [57686.134691] [tempesta fw] exiting... Apr 26 08:05:35 192.168.122.209 [57686.263825] [tdb] Shutdown Tempesta DB Apr 26 08:05:35 192.168.122.209 [57686.498052] End test: forwarding.test_forwarded_hdr.TestForwardedBaseMalicious.test_run Apr 26 08:05:35 192.168.122.209 [57686.528080] Start test: forwarding.test_match_host_forwarded.TestMatchHost.test_1 Apr 26 08:05:37 192.168.122.209 [57687.540153] [tdb] Start Tempesta DB Apr 26 08:05:37 192.168.122.209 [57687.676573] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:05:39 192.168.122.209 [57689.646768] [tempesta fw] Configuration processing is completed. Apr 26 08:05:39 192.168.122.209 [57689.708408] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:05:39 192.168.122.209 [57690.122670] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:05:39 192.168.122.209 [57690.149394] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:05:39 192.168.122.209 [57690.176964] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:05:39 192.168.122.209 [57690.278669] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:05:39 192.168.122.209 [57690.330606] [tempesta fw] Tempesta FW is ready Apr 26 08:05:40 192.168.122.209 [57691.095104] [tdb] Close table 'client0.tdb' Apr 26 08:05:40 192.168.122.209 [57691.292327] [tdb] Close table 'sessions0.tdb' Apr 26 08:05:43 192.168.122.209 [57694.489217] [tdb] Close table 'cache0.tdb' Apr 26 08:05:44 192.168.122.209 [57694.717926] [tdb] Close table 'filter0.tdb' Apr 26 08:05:44 192.168.122.209 [57694.718329] [tempesta fw] modules are stopped Apr 26 08:05:44 192.168.122.209 [57694.974049] [tempesta fw] exiting... Apr 26 08:05:44 192.168.122.209 [57695.070266] [tdb] Shutdown Tempesta DB Apr 26 08:05:44 192.168.122.209 [57695.290373] End test: forwarding.test_match_host_forwarded.TestMatchHost.test_1 Apr 26 08:05:44 192.168.122.209 [57695.309366] Start test: forwarding.test_match_host_forwarded.TestMatchHost.test_2 Apr 26 08:05:45 192.168.122.209 [57696.361747] [tdb] Start Tempesta DB Apr 26 08:05:45 192.168.122.209 [57696.495703] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:05:47 192.168.122.209 [57698.466862] [tempesta fw] Configuration processing is completed. Apr 26 08:05:47 192.168.122.209 [57698.516058] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:05:48 192.168.122.209 [57698.934777] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:05:48 192.168.122.209 [57698.961636] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:05:48 192.168.122.209 [57698.987481] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:05:48 192.168.122.209 [57699.070706] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:05:48 192.168.122.209 [57699.178731] [tempesta fw] Tempesta FW is ready Apr 26 08:05:49 192.168.122.209 [57699.966377] [tdb] Close table 'client0.tdb' Apr 26 08:05:49 192.168.122.209 [57700.148643] [tdb] Close table 'sessions0.tdb' Apr 26 08:05:52 192.168.122.209 [57703.358166] [tdb] Close table 'cache0.tdb' Apr 26 08:05:53 192.168.122.209 [57703.604082] [tdb] Close table 'filter0.tdb' Apr 26 08:05:53 192.168.122.209 [57703.604508] [tempesta fw] modules are stopped Apr 26 08:05:53 192.168.122.209 [57703.874849] [tempesta fw] exiting... Apr 26 08:05:53 192.168.122.209 [57704.002161] [tdb] Shutdown Tempesta DB Apr 26 08:05:53 192.168.122.209 [57704.229163] End test: forwarding.test_match_host_forwarded.TestMatchHost.test_2 Apr 26 08:05:53 192.168.122.209 [57704.250188] Start test: forwarding.test_match_host_forwarded.TestMatchHost.test_3 Apr 26 08:05:54 192.168.122.209 [57705.329528] [tdb] Start Tempesta DB Apr 26 08:05:54 192.168.122.209 [57705.471857] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:05:56 192.168.122.209 [57707.382978] [tempesta fw] Configuration processing is completed. Apr 26 08:05:56 192.168.122.209 [57707.432547] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:05:57 192.168.122.209 [57707.849935] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:05:57 192.168.122.209 [57707.885859] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:05:57 192.168.122.209 [57707.913435] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:05:57 192.168.122.209 [57708.014907] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:05:57 192.168.122.209 [57708.054852] [tempesta fw] Tempesta FW is ready Apr 26 08:05:58 192.168.122.209 [57708.793019] [tdb] Close table 'client0.tdb' Apr 26 08:05:58 192.168.122.209 [57708.978912] [tdb] Close table 'sessions0.tdb' Apr 26 08:06:01 192.168.122.209 [57712.167261] [tdb] Close table 'cache0.tdb' Apr 26 08:06:01 192.168.122.209 [57712.437694] [tdb] Close table 'filter0.tdb' Apr 26 08:06:01 192.168.122.209 [57712.438132] [tempesta fw] modules are stopped Apr 26 08:06:02 192.168.122.209 [57712.712134] [tempesta fw] exiting... Apr 26 08:06:02 192.168.122.209 [57712.843627] [tdb] Shutdown Tempesta DB Apr 26 08:06:02 192.168.122.209 [57713.064355] End test: forwarding.test_match_host_forwarded.TestMatchHost.test_3 Apr 26 08:06:02 192.168.122.209 [57713.077028] Start test: forwarding.test_match_host_forwarded.TestMatchHost.test_4 Apr 26 08:06:03 192.168.122.209 [57714.126262] [tdb] Start Tempesta DB Apr 26 08:06:03 192.168.122.209 [57714.253325] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:06:05 192.168.122.209 [57716.207105] [tempesta fw] Configuration processing is completed. Apr 26 08:06:05 192.168.122.209 [57716.256747] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:06:06 192.168.122.209 [57716.681759] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:06:06 192.168.122.209 [57716.708968] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:06:06 192.168.122.209 [57716.735776] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:06:06 192.168.122.209 [57716.830966] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:06:06 192.168.122.209 [57716.870958] [tempesta fw] Tempesta FW is ready Apr 26 08:06:07 192.168.122.209 [57717.677635] [tdb] Close table 'client0.tdb' Apr 26 08:06:07 192.168.122.209 [57717.862312] [tdb] Close table 'sessions0.tdb' Apr 26 08:06:10 192.168.122.209 [57721.029111] [tdb] Close table 'cache0.tdb' Apr 26 08:06:10 192.168.122.209 [57721.256782] [tdb] Close table 'filter0.tdb' Apr 26 08:06:10 192.168.122.209 [57721.257216] [tempesta fw] modules are stopped Apr 26 08:06:10 192.168.122.209 [57721.500224] [tempesta fw] exiting... Apr 26 08:06:11 192.168.122.209 [57721.644975] [tdb] Shutdown Tempesta DB Apr 26 08:06:11 192.168.122.209 [57721.898123] End test: forwarding.test_match_host_forwarded.TestMatchHost.test_4 Apr 26 08:06:11 192.168.122.209 [57721.917020] Start test: forwarding.test_match_host_forwarded.TestMatchHost.test_5 Apr 26 08:06:12 192.168.122.209 [57722.959511] [tdb] Start Tempesta DB Apr 26 08:06:12 192.168.122.209 [57723.102414] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:06:14 192.168.122.209 [57725.135208] [tempesta fw] Configuration processing is completed. Apr 26 08:06:14 192.168.122.209 [57725.188025] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:06:15 192.168.122.209 [57725.610149] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:06:15 192.168.122.209 [57725.637668] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:06:15 192.168.122.209 [57725.664917] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:06:15 192.168.122.209 [57725.775118] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:06:15 192.168.122.209 [57725.823069] [tempesta fw] Tempesta FW is ready Apr 26 08:06:16 192.168.122.209 [57726.647508] [tdb] Close table 'client0.tdb' Apr 26 08:06:16 192.168.122.209 [57726.838669] [tdb] Close table 'sessions0.tdb' Apr 26 08:06:19 192.168.122.209 [57729.997977] [tdb] Close table 'cache0.tdb' Apr 26 08:06:19 192.168.122.209 [57730.242592] [tdb] Close table 'filter0.tdb' Apr 26 08:06:19 192.168.122.209 [57730.243044] [tempesta fw] modules are stopped Apr 26 08:06:19 192.168.122.209 [57730.501968] [tempesta fw] exiting... Apr 26 08:06:20 192.168.122.209 [57730.613134] [tdb] Shutdown Tempesta DB Apr 26 08:06:20 192.168.122.209 [57730.824844] End test: forwarding.test_match_host_forwarded.TestMatchHost.test_5 Apr 26 08:06:20 192.168.122.209 [57730.849945] Start test: forwarding.test_match_host_forwarded.TestMatchHost.test_6 Apr 26 08:06:21 192.168.122.209 [57731.975002] [tdb] Start Tempesta DB Apr 26 08:06:21 192.168.122.209 [57732.112844] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:06:23 192.168.122.209 [57734.103390] [tempesta fw] Configuration processing is completed. Apr 26 08:06:23 192.168.122.209 [57734.159818] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:06:24 192.168.122.209 [57734.578090] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:06:24 192.168.122.209 [57734.605178] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:06:24 192.168.122.209 [57734.632522] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:06:24 192.168.122.209 [57734.715221] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:06:24 192.168.122.209 [57734.759125] [tempesta fw] Tempesta FW is ready Apr 26 08:06:24 192.168.122.209 [57735.509681] [tdb] Close table 'client0.tdb' Apr 26 08:06:25 192.168.122.209 [57735.700555] [tdb] Close table 'sessions0.tdb' Apr 26 08:06:28 192.168.122.209 [57738.881992] [tdb] Close table 'cache0.tdb' Apr 26 08:06:28 192.168.122.209 [57739.132726] [tdb] Close table 'filter0.tdb' Apr 26 08:06:28 192.168.122.209 [57739.133169] [tempesta fw] modules are stopped Apr 26 08:06:28 192.168.122.209 [57739.379092] [tempesta fw] exiting... Apr 26 08:06:28 192.168.122.209 [57739.498551] [tdb] Shutdown Tempesta DB Apr 26 08:06:29 192.168.122.209 [57739.725134] End test: forwarding.test_match_host_forwarded.TestMatchHost.test_6 Apr 26 08:06:29 192.168.122.209 [57739.738147] Start test: forwarding.test_match_host_forwarded.TestMatchHost.test_7 Apr 26 08:06:30 192.168.122.209 [57740.781186] [tdb] Start Tempesta DB Apr 26 08:06:30 192.168.122.209 [57740.919068] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:06:32 192.168.122.209 [57742.963460] [tempesta fw] Configuration processing is completed. Apr 26 08:06:32 192.168.122.209 [57743.014849] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:06:32 192.168.122.209 [57743.450114] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:06:32 192.168.122.209 [57743.481105] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:06:32 192.168.122.209 [57743.507895] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:06:33 192.168.122.209 [57743.603368] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:06:33 192.168.122.209 [57743.643292] [tempesta fw] Tempesta FW is ready Apr 26 08:06:33 192.168.122.209 [57744.417960] [tdb] Close table 'client0.tdb' Apr 26 08:06:34 192.168.122.209 [57744.603800] [tdb] Close table 'sessions0.tdb' Apr 26 08:06:37 192.168.122.209 [57747.782009] [tdb] Close table 'cache0.tdb' Apr 26 08:06:37 192.168.122.209 [57748.040368] [tdb] Close table 'filter0.tdb' Apr 26 08:06:37 192.168.122.209 [57748.040805] [tempesta fw] modules are stopped Apr 26 08:06:37 192.168.122.209 [57748.263750] [tempesta fw] exiting... Apr 26 08:06:37 192.168.122.209 [57748.383561] [tdb] Shutdown Tempesta DB Apr 26 08:06:38 192.168.122.209 [57748.604867] End test: forwarding.test_match_host_forwarded.TestMatchHost.test_7 Apr 26 08:06:38 192.168.122.209 [57748.617959] Start test: forwarding.test_match_host_forwarded.TestMatchHost.test_8 Apr 26 08:06:39 192.168.122.209 [57749.662410] [tdb] Start Tempesta DB Apr 26 08:06:39 192.168.122.209 [57749.813086] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:06:41 192.168.122.209 [57751.691538] [tempesta fw] Configuration processing is completed. Apr 26 08:06:41 192.168.122.209 [57751.753641] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:06:41 192.168.122.209 [57752.172175] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:06:41 192.168.122.209 [57752.199249] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:06:41 192.168.122.209 [57752.226038] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:06:41 192.168.122.209 [57752.319425] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:06:41 192.168.122.209 [57752.363401] [tempesta fw] Tempesta FW is ready Apr 26 08:06:41 192.168.122.209 [57752.531090] [tempesta fw] Warning: request has been filtered out via http table: 127.0.0.2 Apr 26 08:06:42 192.168.122.209 [57753.118062] [tdb] Close table 'client0.tdb' Apr 26 08:06:42 192.168.122.209 [57753.298742] [tdb] Close table 'sessions0.tdb' Apr 26 08:06:45 192.168.122.209 [57756.501468] [tdb] Close table 'cache0.tdb' Apr 26 08:06:46 192.168.122.209 [57756.752707] [tdb] Close table 'filter0.tdb' Apr 26 08:06:46 192.168.122.209 [57756.753154] [tempesta fw] modules are stopped Apr 26 08:06:46 192.168.122.209 [57757.021431] [tempesta fw] exiting... Apr 26 08:06:46 192.168.122.209 [57757.180115] [tdb] Shutdown Tempesta DB Apr 26 08:06:46 192.168.122.209 [57757.389839] End test: forwarding.test_match_host_forwarded.TestMatchHost.test_8 Apr 26 08:06:46 192.168.122.209 [57757.406488] Start test: forwarding.test_match_host_forwarded.TestMatchHost.test_9 Apr 26 08:06:47 192.168.122.209 [57758.464465] [tdb] Start Tempesta DB Apr 26 08:06:48 192.168.122.209 [57758.596598] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:06:49 192.168.122.209 [57760.519641] [tempesta fw] Configuration processing is completed. Apr 26 08:06:50 192.168.122.209 [57760.574387] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:06:50 192.168.122.209 [57760.997725] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:06:50 192.168.122.209 [57761.024398] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:06:50 192.168.122.209 [57761.050907] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:06:50 192.168.122.209 [57761.143574] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:06:50 192.168.122.209 [57761.183526] [tempesta fw] Tempesta FW is ready Apr 26 08:06:50 192.168.122.209 [57761.346940] [tempesta fw] Warning: request has been filtered out via http table: 127.0.0.2 Apr 26 08:06:51 192.168.122.209 [57761.893922] [tdb] Close table 'client0.tdb' Apr 26 08:06:51 192.168.122.209 [57762.091758] [tdb] Close table 'sessions0.tdb' Apr 26 08:06:54 192.168.122.209 [57765.249628] [tdb] Close table 'cache0.tdb' Apr 26 08:06:54 192.168.122.209 [57765.484282] [tdb] Close table 'filter0.tdb' Apr 26 08:06:54 192.168.122.209 [57765.484734] [tempesta fw] modules are stopped Apr 26 08:06:55 192.168.122.209 [57765.695960] [tempesta fw] exiting... Apr 26 08:06:55 192.168.122.209 [57765.834326] [tdb] Shutdown Tempesta DB Apr 26 08:06:55 192.168.122.209 [57766.048593] End test: forwarding.test_match_host_forwarded.TestMatchHost.test_9 Apr 26 08:06:55 192.168.122.209 [57766.061666] Start test: http2_general.test_flow_control_window.TestFlowControl.test_not_blocked_continuation_frame Apr 26 08:06:56 192.168.122.209 [57767.106633] [tdb] Start Tempesta DB Apr 26 08:06:56 192.168.122.209 [57767.246530] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:06:58 192.168.122.209 [57768.861088] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [57768.861088] Maybe that's fine, but it's worth checking the [57768.861088] config - if there is no relations between the [57768.861088] names, then host name confusion attack is possible. Apr 26 08:06:58 192.168.122.209 [57769.027667] [tempesta fw] Configuration processing is completed. Apr 26 08:06:58 192.168.122.209 [57769.081785] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:06:58 192.168.122.209 [57769.484664] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:06:58 192.168.122.209 [57769.510442] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:06:59 192.168.122.209 [57769.536625] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:06:59 192.168.122.209 [57769.579697] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:06:59 192.168.122.209 [57769.639625] [tempesta fw] Tempesta FW is ready Apr 26 08:07:02 192.168.122.209 [57773.058022] [tdb] Close table 'client0.tdb' Apr 26 08:07:02 192.168.122.209 [57773.249918] [tdb] Close table 'sessions0.tdb' Apr 26 08:07:05 192.168.122.209 [57776.409537] [tdb] Close table 'cache0.tdb' Apr 26 08:07:06 192.168.122.209 [57776.636958] [tdb] Close table 'filter0.tdb' Apr 26 08:07:06 192.168.122.209 [57776.637424] [tempesta fw] modules are stopped Apr 26 08:07:06 192.168.122.209 [57776.864190] [tempesta fw] exiting... Apr 26 08:07:06 192.168.122.209 [57776.995827] [tdb] Shutdown Tempesta DB Apr 26 08:07:06 192.168.122.209 [57777.229745] End test: http2_general.test_flow_control_window.TestFlowControl.test_not_blocked_continuation_frame Apr 26 08:07:06 192.168.122.209 [57777.242075] Start test: http2_general.test_flow_control_window.TestFlowControl.test_not_blocked_rst_frame Apr 26 08:07:07 192.168.122.209 [57778.336444] [tdb] Start Tempesta DB Apr 26 08:07:07 192.168.122.209 [57778.477392] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:07:09 192.168.122.209 [57780.101259] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [57780.101259] Maybe that's fine, but it's worth checking the [57780.101259] config - if there is no relations between the [57780.101259] names, then host name confusion attack is possible. Apr 26 08:07:09 192.168.122.209 [57780.255821] [tempesta fw] Configuration processing is completed. Apr 26 08:07:09 192.168.122.209 [57780.311444] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:07:10 192.168.122.209 [57780.736526] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:07:10 192.168.122.209 [57780.773137] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:07:10 192.168.122.209 [57780.800212] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:07:10 192.168.122.209 [57780.883809] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:07:10 192.168.122.209 [57780.923753] [tempesta fw] Tempesta FW is ready Apr 26 08:07:11 192.168.122.209 [57781.588660] [tdb] Close table 'client0.tdb' Apr 26 08:07:11 192.168.122.209 [57781.785909] [tdb] Close table 'sessions0.tdb' Apr 26 08:07:14 192.168.122.209 [57784.977393] [tdb] Close table 'cache0.tdb' Apr 26 08:07:14 192.168.122.209 [57785.229839] [tdb] Close table 'filter0.tdb' Apr 26 08:07:14 192.168.122.209 [57785.230255] [tempesta fw] modules are stopped Apr 26 08:07:14 192.168.122.209 [57785.456541] [tempesta fw] exiting... Apr 26 08:07:15 192.168.122.209 [57785.567188] [tdb] Shutdown Tempesta DB Apr 26 08:07:15 192.168.122.209 [57785.788244] End test: http2_general.test_flow_control_window.TestFlowControl.test_not_blocked_rst_frame Apr 26 08:07:15 192.168.122.209 [57785.821357] Start test: http2_general.test_flow_control_window.TestFlowControl.test_not_blocked_settings_frame Apr 26 08:07:16 192.168.122.209 [57786.859597] [tdb] Start Tempesta DB Apr 26 08:07:16 192.168.122.209 [57787.007253] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:07:18 192.168.122.209 [57788.589334] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [57788.589334] Maybe that's fine, but it's worth checking the [57788.589334] config - if there is no relations between the [57788.589334] names, then host name confusion attack is possible. Apr 26 08:07:18 192.168.122.209 [57788.751940] [tempesta fw] Configuration processing is completed. Apr 26 08:07:18 192.168.122.209 [57788.801269] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:07:18 192.168.122.209 [57789.207418] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:07:18 192.168.122.209 [57789.234186] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:07:18 192.168.122.209 [57789.261769] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:07:18 192.168.122.209 [57789.299914] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:07:18 192.168.122.209 [57789.339891] [tempesta fw] Tempesta FW is ready Apr 26 08:07:19 192.168.122.209 [57790.064926] [tdb] Close table 'client0.tdb' Apr 26 08:07:19 192.168.122.209 [57790.255670] [tdb] Close table 'sessions0.tdb' Apr 26 08:07:22 192.168.122.209 [57793.363769] [tdb] Close table 'cache0.tdb' Apr 26 08:07:23 192.168.122.209 [57793.623532] [tdb] Close table 'filter0.tdb' Apr 26 08:07:23 192.168.122.209 [57793.623973] [tempesta fw] modules are stopped Apr 26 08:07:23 192.168.122.209 [57793.841376] [tempesta fw] exiting... Apr 26 08:07:23 192.168.122.209 [57793.939196] [tdb] Shutdown Tempesta DB Apr 26 08:07:23 192.168.122.209 [57794.160726] End test: http2_general.test_flow_control_window.TestFlowControl.test_not_blocked_settings_frame Apr 26 08:07:23 192.168.122.209 [57794.176818] Start test: http2_general.test_flow_control_window.TestFlowControl.test_request_body_greater_than_initial_window_size Apr 26 08:07:24 192.168.122.209 [57795.235763] [tdb] Start Tempesta DB Apr 26 08:07:24 192.168.122.209 [57795.377273] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:07:26 192.168.122.209 [57796.957528] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [57796.957528] Maybe that's fine, but it's worth checking the [57796.957528] config - if there is no relations between the [57796.957528] names, then host name confusion attack is possible. Apr 26 08:07:26 192.168.122.209 [57797.100435] [tempesta fw] Configuration processing is completed. Apr 26 08:07:26 192.168.122.209 [57797.149157] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:07:27 192.168.122.209 [57797.574849] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:07:27 192.168.122.209 [57797.602373] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:07:27 192.168.122.209 [57797.628814] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:07:27 192.168.122.209 [57797.676020] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:07:27 192.168.122.209 [57797.716009] [tempesta fw] Tempesta FW is ready Apr 26 08:07:33 192.168.122.209 [57804.181955] python3.10: page allocation failure: order:9, mode:0x40a20(GFP_ATOMIC|__GFP_COMP), nodemask=(null),cpuset=user.slice,mems_allowed=0 Apr 26 08:07:33 192.168.122.209 [57804.183168] CPU: 3 PID: 706523 Comm: python3.10 Tainted: G OE 5.10.35.tfw-39c65d3-debug #1 Apr 26 08:07:33 192.168.122.209 [57804.184009] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 Apr 26 08:07:33 192.168.122.209 [57804.184828] Call Trace: Apr 26 08:07:33 192.168.122.209 [57804.185063] Apr 26 08:07:33 192.168.122.209 [57804.185259] dump_stack+0x96/0xc4 Apr 26 08:07:33 192.168.122.209 [57804.185563] warn_alloc.cold+0x87/0x12a Apr 26 08:07:33 192.168.122.209 [57804.185917] ? zone_watermark_ok_safe+0x140/0x140 Apr 26 08:07:33 192.168.122.209 [57804.186343] ? __kasan_check_read+0x11/0x20 Apr 26 08:07:33 192.168.122.209 [57804.186726] ? wakeup_kswapd+0xba/0x290 Apr 26 08:07:33 192.168.122.209 [57804.187072] ? __zone_watermark_ok+0x270/0x270 Apr 26 08:07:33 192.168.122.209 [57804.187469] ? wake_all_kswapds+0xf4/0x140 Apr 26 08:07:33 192.168.122.209 [57804.187844] ? __alloc_pages_slowpath.constprop.0+0x11f4/0x1390 Apr 26 08:07:33 192.168.122.209 [57804.188371] __alloc_pages_slowpath.constprop.0+0x1359/0x1390 Apr 26 08:07:33 192.168.122.209 [57804.188891] ? lookup_address_in_pgd.part.0.constprop.0+0x215/0x280 Apr 26 08:07:33 192.168.122.209 [57804.189442] ? warn_alloc+0x120/0x120 Apr 26 08:07:33 192.168.122.209 [57804.189779] ? __change_page_attr_set_clr+0xb8d/0x14b0 Apr 26 08:07:33 192.168.122.209 [57804.190237] ? __zone_watermark_ok+0x270/0x270 Apr 26 08:07:33 192.168.122.209 [57804.190644] ? pvclock_clocksource_read+0xe1/0x1a0 Apr 26 08:07:33 192.168.122.209 [57804.191071] __alloc_pages_nodemask+0x509/0x540 Apr 26 08:07:33 192.168.122.209 [57804.191482] ? __alloc_pages_slowpath.constprop.0+0x1390/0x1390 Apr 26 08:07:33 192.168.122.209 [57804.192020] ? scatterwalk_map_and_copy+0xc0/0x110 Apr 26 08:07:33 192.168.122.209 [57804.192444] ? scatterwalk_ffwd+0x150/0x150 Apr 26 08:07:33 192.168.122.209 [57804.192833] alloc_pages_current+0x96/0x140 Apr 26 08:07:33 192.168.122.209 [57804.193214] __get_free_pages+0x12/0x60 Apr 26 08:07:33 192.168.122.209 [57804.193595] tfw_pool_alloc_pages+0x9b/0xc0 [tempesta_fw] Apr 26 08:07:33 192.168.122.209 [57804.194112] __tfw_pool_realloc+0x123/0x1a0 [tempesta_fw] Apr 26 08:07:33 192.168.122.209 [57804.194628] __str_grow_tree+0x89/0x210 [tempesta_fw] Apr 26 08:07:33 192.168.122.209 [57804.195210] tfw_str_add_compound+0x33/0x40 [tempesta_fw] Apr 26 08:07:33 192.168.122.209 [57804.195766] __tfw_http_msg_add_str_data+0x88/0x1c0 [tempesta_fw] Apr 26 08:07:33 192.168.122.209 [57804.196330] tfw_h2_parse_req+0x3ba/0x410 [tempesta_fw] Apr 26 08:07:33 192.168.122.209 [57804.196824] ? h2_set_hdr_x_method_override+0x50/0x50 [tempesta_fw] Apr 26 08:07:33 192.168.122.209 [57804.197411] ss_skb_process+0x270/0x2f0 [tempesta_fw] Apr 26 08:07:33 192.168.122.209 [57804.197986] ? h2_set_hdr_x_method_override+0x50/0x50 [tempesta_fw] Apr 26 08:07:33 192.168.122.209 [57804.198566] ? tfw_sock_srv_exit+0x30/0x30 [tempesta_fw] Apr 26 08:07:33 192.168.122.209 [57804.199047] ? stack_trace_save+0x94/0xc0 Apr 26 08:07:33 192.168.122.209 [57804.199411] ? stack_trace_consume_entry+0x90/0x90 Apr 26 08:07:33 192.168.122.209 [57804.199844] ? kasan_save_stack+0x42/0x50 Apr 26 08:07:33 192.168.122.209 [57804.200229] tfw_http_req_process+0x185/0x11a0 [tempesta_fw] Apr 26 08:07:33 192.168.122.209 [57804.200733] ? kasan_save_stack+0x42/0x50 Apr 26 08:07:33 192.168.122.209 [57804.201094] ? kasan_save_stack+0x23/0x50 Apr 26 08:07:33 192.168.122.209 [57804.201456] ? kasan_set_track+0x20/0x30 Apr 26 08:07:33 192.168.122.209 [57804.201817] ? kasan_set_free_info+0x1f/0x40 Apr 26 08:07:33 192.168.122.209 [57804.202225] ? tfw_http_extract_request_authority+0x110/0x110 [tempesta_fw] Apr 26 08:07:33 192.168.122.209 [57804.202948] ? tcp_data_ready+0x73/0x210 Apr 26 08:07:33 192.168.122.209 [57804.203303] ? tcp_rcv_established+0x95b/0xb40 Apr 26 08:07:33 192.168.122.209 [57804.203706] ? tcp_v4_do_rcv+0x25f/0x360 Apr 26 08:07:33 192.168.122.209 [57804.204063] ? ip_protocol_deliver_rcu+0x46/0x2e0 Apr 26 08:07:33 192.168.122.209 [57804.204484] ? ip_local_deliver_finish+0xc6/0xe0 Apr 26 08:07:33 192.168.122.209 [57804.204900] ? ip_local_deliver+0x1f5/0x210 Apr 26 08:07:33 192.168.122.209 [57804.205275] ? ip_rcv_finish+0xcf/0xf0 Apr 26 08:07:33 192.168.122.209 [57804.205616] ? ip_rcv+0x16d/0x180 Apr 26 08:07:33 192.168.122.209 [57804.205922] ? __netif_receive_skb_one_core+0x132/0x140 Apr 26 08:07:33 192.168.122.209 [57804.206386] ? __netif_receive_skb+0x26/0xb0 Apr 26 08:07:33 192.168.122.209 [57804.206771] ? process_backlog+0xfe/0x290 Apr 26 08:07:33 192.168.122.209 [57804.207132] ? net_rx_action+0x287/0x6b0 Apr 26 08:07:33 192.168.122.209 [57804.207490] ? __do_softirq+0xfe/0x383 Apr 26 08:07:33 192.168.122.209 [57804.207836] ? asm_call_irq_on_stack+0xf/0x20 Apr 26 08:07:33 192.168.122.209 [57804.208226] ? do_softirq_own_stack+0x3d/0x50 Apr 26 08:07:33 192.168.122.209 [57804.208620] ? do_softirq+0x72/0x90 Apr 26 08:07:33 192.168.122.209 [57804.208939] ? __local_bh_enable_ip+0x50/0x60 Apr 26 08:07:33 192.168.122.209 [57804.209331] ? ip_finish_output2+0x351/0xa80 Apr 26 08:07:33 192.168.122.209 [57804.209716] ? __ip_finish_output+0x16b/0x340 Apr 26 08:07:33 192.168.122.209 [57804.210108] ? ip_finish_output+0x2d/0xe0 Apr 26 08:07:33 192.168.122.209 [57804.210472] ? ip_output+0x133/0x210 Apr 26 08:07:33 192.168.122.209 [57804.210801] ? __ip_queue_xmit+0x356/0x7d0 Apr 26 08:07:33 192.168.122.209 [57804.211167] ? ip_queue_xmit+0x3b/0x50 Apr 26 08:07:33 192.168.122.209 [57804.211507] ? __tcp_transmit_skb+0x152f/0x1730 Apr 26 08:07:33 192.168.122.209 [57804.211919] ? tcp_write_xmit+0x796/0x2a50 Apr 26 08:07:33 192.168.122.209 [57804.212289] ? __tcp_push_pending_frames+0x5f/0x1a0 Apr 26 08:07:33 192.168.122.209 [57804.212724] ? tcp_push+0x209/0x2b0 Apr 26 08:07:33 192.168.122.209 [57804.213043] ? tcp_sendmsg_locked+0x13fa/0x15f0 Apr 26 08:07:33 192.168.122.209 [57804.213474] ? tfw_h2_frame_recv+0xff9/0x3c30 [tempesta_fw] Apr 26 08:07:33 192.168.122.209 [57804.213977] ? sock_sendmsg+0x97/0xa0 Apr 26 08:07:33 192.168.122.209 [57804.214331] tfw_http_msg_process_generic+0x385/0xc70 [tempesta_fw] Apr 26 08:07:33 192.168.122.209 [57804.214916] ? tfw_h2_send_rst_stream+0x150/0x150 [tempesta_fw] Apr 26 08:07:33 192.168.122.209 [57804.215470] ? tfw_http_req_process+0x11a0/0x11a0 [tempesta_fw] Apr 26 08:07:33 192.168.122.209 [57804.216001] ? __kasan_slab_free+0x12a/0x160 Apr 26 08:07:33 192.168.122.209 [57804.216385] ? kasan_slab_free+0xe/0x10 Apr 26 08:07:33 192.168.122.209 [57804.216764] ? ss_skb_chop_head_tail+0xfb/0x380 [tempesta_fw] Apr 26 08:07:33 192.168.122.209 [57804.217302] ? tfw_h2_send_rst_stream+0x150/0x150 [tempesta_fw] Apr 26 08:07:33 192.168.122.209 [57804.217858] ? ss_skb_get_room_w_frag+0xf0/0xf0 [tempesta_fw] Apr 26 08:07:33 192.168.122.209 [57804.218391] ? tfw_h2_send_rst_stream+0x150/0x150 [tempesta_fw] Apr 26 08:07:33 192.168.122.209 [57804.218944] ? tfw_sock_srv_exit+0x30/0x30 [tempesta_fw] Apr 26 08:07:33 192.168.122.209 [57804.219447] tfw_h2_frame_process+0x9c6/0xf20 [tempesta_fw] Apr 26 08:07:33 192.168.122.209 [57804.219975] ? tfw_h2_frame_recv+0x3c30/0x3c30 [tempesta_fw] Apr 26 08:07:33 192.168.122.209 [57804.220503] ? ss_skb_chop_head_tail+0x2a8/0x380 [tempesta_fw] Apr 26 08:07:33 192.168.122.209 [57804.221049] tfw_http_msg_process+0x9d/0xc0 [tempesta_fw] Apr 26 08:07:33 192.168.122.209 [57804.221580] tfw_connection_recv+0x12e/0x250 [tempesta_fw] Apr 26 08:07:33 192.168.122.209 [57804.222095] ? tfw_connection_send+0x70/0x70 [tempesta_fw] Apr 26 08:07:33 192.168.122.209 [57804.222610] ? ss_skb_list_chop_head_tail+0x6e/0x1d0 [tempesta_fw] Apr 26 08:07:33 192.168.122.209 [57804.223184] tfw_tls_connection_recv+0x4f6/0x730 [tempesta_fw] Apr 26 08:07:33 192.168.122.209 [57804.223711] ? __kasan_check_write+0x14/0x20 Apr 26 08:07:33 192.168.122.209 [57804.224150] ? tfw_tls_connection_lost+0x40/0x40 [tempesta_fw] Apr 26 08:07:33 192.168.122.209 [57804.224695] ? ss_skb_unroll+0x3d6/0x540 [tempesta_fw] Apr 26 08:07:33 192.168.122.209 [57804.225181] ss_tcp_process_data+0x436/0x8b0 [tempesta_fw] Apr 26 08:07:33 192.168.122.209 [57804.225701] ? __sk_close_locked+0x100/0x100 [tempesta_fw] Apr 26 08:07:33 192.168.122.209 [57804.226175] ? mod_timer+0x10/0x20 Apr 26 08:07:33 192.168.122.209 [57804.226478] ? sk_reset_timer+0x1a/0x70 Apr 26 08:07:33 192.168.122.209 [57804.226845] ss_tcp_data_ready+0x7b/0x150 [tempesta_fw] Apr 26 08:07:33 192.168.122.209 [57804.227325] tcp_data_ready+0x73/0x210 Apr 26 08:07:33 192.168.122.209 [57804.227669] tcp_rcv_established+0x95b/0xb40 Apr 26 08:07:33 192.168.122.209 [57804.228050] ? tcp_data_queue+0x1d80/0x1d80 Apr 26 08:07:33 192.168.122.209 [57804.228429] ? __kasan_check_read+0x11/0x20 Apr 26 08:07:33 192.168.122.209 [57804.228812] tcp_v4_do_rcv+0x25f/0x360 Apr 26 08:07:33 192.168.122.209 [57804.229152] tcp_v4_rcv+0x1600/0x1770 Apr 26 08:07:33 192.168.122.209 [57804.229483] ? tcp_v4_early_demux+0x2f0/0x2f0 Apr 26 08:07:33 192.168.122.209 [57804.229888] ip_protocol_deliver_rcu+0x46/0x2e0 Apr 26 08:07:33 192.168.122.209 [57804.230310] ip_local_deliver_finish+0xc6/0xe0 Apr 26 08:07:33 192.168.122.209 [57804.230712] ip_local_deliver+0x1f5/0x210 Apr 26 08:07:33 192.168.122.209 [57804.231072] ? ip_local_deliver_finish+0xe0/0xe0 Apr 26 08:07:33 192.168.122.209 [57804.231496] ? nf_nat_inet_fn+0x2b3/0x440 [nf_nat] Apr 26 08:07:33 192.168.122.209 [57804.231941] ? ip_protocol_deliver_rcu+0x2e0/0x2e0 Apr 26 08:07:33 192.168.122.209 [57804.232369] ? ip_rcv_finish_core.constprop.0+0x17c/0x890 Apr 26 08:07:33 192.168.122.209 [57804.232850] ip_rcv_finish+0xcf/0xf0 Apr 26 08:07:33 192.168.122.209 [57804.233173] ip_rcv+0x16d/0x180 Apr 26 08:07:33 192.168.122.209 [57804.233463] ? ip_local_deliver+0x210/0x210 Apr 26 08:07:33 192.168.122.209 [57804.233847] ? ip_rcv_finish_core.constprop.0+0x890/0x890 Apr 26 08:07:33 192.168.122.209 [57804.234325] ? ttwu_do_activate+0xa4/0x170 Apr 26 08:07:33 192.168.122.209 [57804.234709] ? ip_local_deliver+0x210/0x210 Apr 26 08:07:33 192.168.122.209 [57804.235088] __netif_receive_skb_one_core+0x132/0x140 Apr 26 08:07:33 192.168.122.209 [57804.235540] ? napi_gro_receive+0x260/0x260 Apr 26 08:07:33 192.168.122.209 [57804.235949] ? __kasan_check_write+0x14/0x20 Apr 26 08:07:33 192.168.122.209 [57804.236332] ? _raw_spin_lock+0x7b/0xd0 Apr 26 08:07:33 192.168.122.209 [57804.236686] __netif_receive_skb+0x26/0xb0 Apr 26 08:07:33 192.168.122.209 [57804.237054] process_backlog+0xfe/0x290 Apr 26 08:07:33 192.168.122.209 [57804.237399] net_rx_action+0x287/0x6b0 Apr 26 08:07:33 192.168.122.209 [57804.237743] ? napi_complete_done+0x2c0/0x2c0 Apr 26 08:07:33 192.168.122.209 [57804.238137] ? switch_fpu_return+0x120/0x120 Apr 26 08:07:33 192.168.122.209 [57804.238532] __do_softirq+0xfe/0x383 Apr 26 08:07:33 192.168.122.209 [57804.238851] asm_call_irq_on_stack+0xf/0x20 Apr 26 08:07:33 192.168.122.209 [57804.239216] Apr 26 08:07:33 192.168.122.209 [57804.239413] do_softirq_own_stack+0x3d/0x50 Apr 26 08:07:33 192.168.122.209 [57804.239783] do_softirq+0x72/0x90 Apr 26 08:07:33 192.168.122.209 [57804.240097] __local_bh_enable_ip+0x50/0x60 Apr 26 08:07:33 192.168.122.209 [57804.240473] ip_finish_output2+0x351/0xa80 Apr 26 08:07:33 192.168.122.209 [57804.240849] ? __ip_flush_pending_frames.constprop.0+0x130/0x130 Apr 26 08:07:33 192.168.122.209 [57804.241390] ? cgroup_bpf_release+0x400/0x400 Apr 26 08:07:33 192.168.122.209 [57804.241793] __ip_finish_output+0x16b/0x340 Apr 26 08:07:33 192.168.122.209 [57804.242181] ip_finish_output+0x2d/0xe0 Apr 26 08:07:33 192.168.122.209 [57804.242528] ip_output+0x133/0x210 Apr 26 08:07:33 192.168.122.209 [57804.242844] ? ip_mc_output+0x4e0/0x4e0 Apr 26 08:07:33 192.168.122.209 [57804.243190] ? __ip_finish_output+0x340/0x340 Apr 26 08:07:33 192.168.122.209 [57804.243580] ? ipv4_dst_check+0x6d/0xa0 Apr 26 08:07:33 192.168.122.209 [57804.243936] __ip_queue_xmit+0x356/0x7d0 Apr 26 08:07:33 192.168.122.209 [57804.244294] ip_queue_xmit+0x3b/0x50 Apr 26 08:07:33 192.168.122.209 [57804.244619] __tcp_transmit_skb+0x152f/0x1730 Apr 26 08:07:33 192.168.122.209 [57804.245011] ? __kmalloc+0x178/0x2d0 Apr 26 08:07:33 192.168.122.209 [57804.245340] ? __tcp_select_window+0x370/0x370 Apr 26 08:07:33 192.168.122.209 [57804.245746] ? pvclock_clocksource_read+0xe1/0x1a0 Apr 26 08:07:33 192.168.122.209 [57804.246172] ? __kasan_check_read+0x11/0x20 Apr 26 08:07:33 192.168.122.209 [57804.246553] tcp_write_xmit+0x796/0x2a50 Apr 26 08:07:33 192.168.122.209 [57804.246908] ? iov_iter_advance+0x12b/0x5f0 Apr 26 08:07:33 192.168.122.209 [57804.247276] ? bpf_skops_hdr_opt_len+0x210/0x210 Apr 26 08:07:33 192.168.122.209 [57804.247709] ? kfree+0xbe/0x470 Apr 26 08:07:33 192.168.122.209 [57804.247999] __tcp_push_pending_frames+0x5f/0x1a0 Apr 26 08:07:33 192.168.122.209 [57804.248425] tcp_push+0x209/0x2b0 Apr 26 08:07:33 192.168.122.209 [57804.248732] tcp_sendmsg_locked+0x13fa/0x15f0 Apr 26 08:07:33 192.168.122.209 [57804.249121] ? skb_do_copy_data_nocache+0x1b0/0x1b0 Apr 26 08:07:33 192.168.122.209 [57804.249560] ? __kasan_check_write+0x14/0x20 Apr 26 08:07:33 192.168.122.209 [57804.249943] ? _raw_spin_lock_bh+0x86/0xe0 Apr 26 08:07:33 192.168.122.209 [57804.250305] tcp_sendmsg+0x2d/0x50 Apr 26 08:07:33 192.168.122.209 [57804.250641] inet_sendmsg+0x64/0xa0 Apr 26 08:07:33 192.168.122.209 [57804.250958] ? inet_send_prepare+0x120/0x120 Apr 26 08:07:33 192.168.122.209 [57804.251345] sock_sendmsg+0x97/0xa0 Apr 26 08:07:33 192.168.122.209 [57804.251671] sock_write_iter+0x14c/0x200 Apr 26 08:07:33 192.168.122.209 [57804.252046] ? sock_sendmsg+0xa0/0xa0 Apr 26 08:07:33 192.168.122.209 [57804.252376] ? __cgroup_bpf_run_filter_sock_ops+0x190/0x190 Apr 26 08:07:33 192.168.122.209 [57804.252876] ? __kasan_check_read+0x11/0x20 Apr 26 08:07:33 192.168.122.209 [57804.253258] new_sync_write+0x3aa/0x3c0 Apr 26 08:07:33 192.168.122.209 [57804.253606] ? new_sync_read+0x3c0/0x3c0 Apr 26 08:07:33 192.168.122.209 [57804.253959] ? _raw_spin_lock+0xd0/0xd0 Apr 26 08:07:33 192.168.122.209 [57804.254316] ? __kasan_check_read+0x11/0x20 Apr 26 08:07:33 192.168.122.209 [57804.254688] ? rw_verify_area+0x7c/0x150 Apr 26 08:07:33 192.168.122.209 [57804.255031] vfs_write+0x311/0x3d0 Apr 26 08:07:33 192.168.122.209 [57804.255353] ksys_write+0x138/0x170 Apr 26 08:07:33 192.168.122.209 [57804.255677] ? __ia32_sys_read+0x50/0x50 Apr 26 08:07:33 192.168.122.209 [57804.256032] ? __kasan_check_read+0x11/0x20 Apr 26 08:07:33 192.168.122.209 [57804.256405] ? fpregs_assert_state_consistent+0x5a/0x70 Apr 26 08:07:33 192.168.122.209 [57804.256871] __x64_sys_write+0x42/0x50 Apr 26 08:07:33 192.168.122.209 [57804.257215] do_syscall_64+0x38/0x90 Apr 26 08:07:33 192.168.122.209 [57804.257540] entry_SYSCALL_64_after_hwframe+0x44/0xa9 Apr 26 08:07:33 192.168.122.209 [57804.257992] RIP: 0033:0x7f7ff82c95ad Apr 26 08:07:33 192.168.122.209 [57804.258316] Code: e5 48 83 ec 20 48 89 55 e8 48 89 75 f0 89 7d f8 e8 b8 bf f7 ff 48 8b 55 e8 48 8b 75 f0 41 89 c0 8b 7d f8 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 33 44 89 c7 48 89 45 f8 e8 0f c0 f7 ff 48 8b Apr 26 08:07:33 192.168.122.209 [57804.259947] RSP: 002b:00007f7ff3a7b350 EFLAGS: 00000293 ORIG_RAX: 0000000000000001 Apr 26 08:07:33 192.168.122.209 [57804.260632] RAX: ffffffffffffffda RBX: 00007f7fec0c6ad0 RCX: 00007f7ff82c95ad Apr 26 08:07:33 192.168.122.209 [57804.261255] RDX: 000000000000001e RSI: 00007f7fec061be3 RDI: 0000000000000005 Apr 26 08:07:33 192.168.122.209 [57804.261894] RBP: 00007f7ff3a7b370 R08: 0000000000000000 R09: 0000000000000000 Apr 26 08:07:33 192.168.122.209 [57804.262523] R10: 00007f7fec026f90 R11: 0000000000000293 R12: 000000000000001e Apr 26 08:07:33 192.168.122.209 [57804.263151] R13: 00007f7fec061be3 R14: 00007f7ff3a7b490 R15: 00007f7ff3a7b440 Apr 26 08:07:33 192.168.122.209 [57804.263810] Mem-Info: Apr 26 08:07:33 192.168.122.209 [57804.264041] active_anon:32784 inactive_anon:97482 isolated_anon:0 [57804.264041] active_file:97823 inactive_file:97971 isolated_file:0 [57804.264041] unevictable:6821 dirty:84 writeback:0 [57804.264041] slab_reclaimable:23962 slab_unreclaimable:99420 [57804.264041] mapped:36829 shmem:426 pagetables:1339 bounce:0 [57804.264041] free:117041 free_pcp:1957 free_cma:0 Apr 26 08:07:33 192.168.122.209 [57804.266998] Node 0 active_anon:131136kB inactive_anon:389928kB active_file:391292kB inactive_file:391884kB unevictable:27284kB isolated(anon):0kB isolated(file):0kB mapped:147316kB dirty:460kB writeback:0kB shmem:1704kB shmem_thp: 0kB shmem_pmdmapped: 0kB anon_thp: 0kB writeback_tmp:0kB kernel_stack:9632kB all_unreclaimable? no Apr 26 08:07:33 192.168.122.209 [57804.269659] Node 0 DMA free:11904kB min:408kB low:508kB high:608kB reserved_highatomic:4096KB active_anon:8kB inactive_anon:36kB active_file:4kB inactive_file:4kB unevictable:0kB writepending:0kB present:15992kB managed:15908kB mlocked:0kB pagetables:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB Apr 26 08:07:33 192.168.122.209 [57804.272241] lowmem_reserve[]: 0 1900 2534 2534 2534 Apr 26 08:07:33 192.168.122.209 [57804.272738] Node 0 DMA32 free:429716kB min:50364kB low:62952kB high:75540kB reserved_highatomic:0KB active_anon:124916kB inactive_anon:350364kB active_file:312076kB inactive_file:363408kB unevictable:0kB writepending:116kB present:2080624kB managed:1946020kB mlocked:0kB pagetables:664kB bounce:0kB free_pcp:5384kB local_pcp:1480kB free_cma:0kB Apr 26 08:07:33 192.168.122.209 [57804.275379] lowmem_reserve[]: 0 0 634 634 634 Apr 26 08:07:33 192.168.122.209 [57804.275803] Node 0 Normal free:26544kB min:16804kB low:21004kB high:25204kB reserved_highatomic:2048KB active_anon:5848kB inactive_anon:39956kB active_file:79676kB inactive_file:28656kB unevictable:27284kB writepending:220kB present:2097152kB managed:649288kB mlocked:27284kB pagetables:4692kB bounce:0kB free_pcp:2364kB local_pcp:708kB free_cma:0kB Apr 26 08:07:33 192.168.122.209 [57804.278451] lowmem_reserve[]: 0 0 0 0 0 Apr 26 08:07:33 192.168.122.209 [57804.278823] Node 0 DMA: 14*4kB (MH) 21*8kB (ME) 22*16kB (MEH) 18*32kB (MEH) 16*64kB (MEH) 10*128kB (MEH) 5*256kB (MEH) 4*512kB (MH) 3*1024kB (ME) 1*2048kB (U) 0*4096kB = 11904kB Apr 26 08:07:33 192.168.122.209 [57804.280239] Node 0 DMA32: 247*4kB (UME) 1873*8kB (UME) 5841*16kB (UME) 3879*32kB (UME) 2369*64kB (UME) 286*128kB (UME) 32*256kB (UE) 0*512kB 0*1024kB 0*2048kB 0*4096kB = 429972kB Apr 26 08:07:33 192.168.122.209 [57804.281650] Node 0 Normal: 1577*4kB (UMEH) 228*8kB (UMEH) 326*16kB (UMEH) 347*32kB (UMEH) 25*64kB (U) 1*128kB (U) 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 26180kB Apr 26 08:07:33 192.168.122.209 [57804.282956] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=1048576kB Apr 26 08:07:33 192.168.122.209 [57804.283718] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=2048kB Apr 26 08:07:33 192.168.122.209 [57804.284478] 256483 total pagecache pages Apr 26 08:07:33 192.168.122.209 [57804.284842] 58098 pages in swap cache Apr 26 08:07:33 192.168.122.209 [57804.285173] Swap cache stats: add 297164, delete 239068, find 370528/421369 Apr 26 08:07:33 192.168.122.209 [57804.285790] Free swap = 3756760kB Apr 26 08:07:33 192.168.122.209 [57804.286102] Total swap = 4194300kB Apr 26 08:07:33 192.168.122.209 [57804.286413] 1048442 pages RAM Apr 26 08:07:33 192.168.122.209 [57804.286693] 0 pages HighMem/MovableOnly Apr 26 08:07:33 192.168.122.209 [57804.287039] 395638 pages reserved Apr 26 08:07:33 192.168.122.209 [57804.287344] 0 pages cma reserved Apr 26 08:07:33 192.168.122.209 [57804.287644] 0 pages hwpoisoned Apr 26 08:07:33 192.168.122.209 [57804.287938] [tempesta fw] Warning: Cannot grow HTTP data string Apr 26 08:07:34 192.168.122.209 [57804.755341] [tdb] Close table 'client0.tdb' Apr 26 08:07:34 192.168.122.209 [57804.937905] [tdb] Close table 'sessions0.tdb' Apr 26 08:07:37 192.168.122.209 [57808.129896] [tdb] Close table 'cache0.tdb' Apr 26 08:07:37 192.168.122.209 [57808.361431] [tdb] Close table 'filter0.tdb' Apr 26 08:07:37 192.168.122.209 [57808.361883] [tempesta fw] modules are stopped Apr 26 08:07:38 192.168.122.209 [57808.570272] [tempesta fw] exiting... Apr 26 08:07:38 192.168.122.209 [57808.683560] [tdb] Shutdown Tempesta DB Apr 26 08:07:38 192.168.122.209 [57808.915509] End test: http2_general.test_flow_control_window.TestFlowControl.test_request_body_greater_than_initial_window_size Apr 26 08:07:38 192.168.122.209 [57808.949201] Start test: http2_general.test_flow_control_window.TestFlowControl.test_several_stream Apr 26 08:07:39 192.168.122.209 [57810.040591] [tdb] Start Tempesta DB Apr 26 08:07:39 192.168.122.209 [57810.168308] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:07:41 192.168.122.209 [57811.665706] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [57811.665706] Maybe that's fine, but it's worth checking the [57811.665706] config - if there is no relations between the [57811.665706] names, then host name confusion attack is possible. Apr 26 08:07:41 192.168.122.209 [57811.816212] [tempesta fw] Configuration processing is completed. Apr 26 08:07:41 192.168.122.209 [57811.866413] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:07:41 192.168.122.209 [57812.281384] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:07:41 192.168.122.209 [57812.308607] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:07:41 192.168.122.209 [57812.344603] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:07:41 192.168.122.209 [57812.388195] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:07:41 192.168.122.209 [57812.440143] [tempesta fw] Tempesta FW is ready Apr 26 08:07:42 192.168.122.209 [57813.176828] [tdb] Close table 'client0.tdb' Apr 26 08:07:42 192.168.122.209 [57813.388594] [tdb] Close table 'sessions0.tdb' Apr 26 08:07:46 192.168.122.209 [57816.587983] [tdb] Close table 'cache0.tdb' Apr 26 08:07:46 192.168.122.209 [57816.827101] [tdb] Close table 'filter0.tdb' Apr 26 08:07:46 192.168.122.209 [57816.827532] [tempesta fw] modules are stopped Apr 26 08:07:46 192.168.122.209 [57817.076296] [tempesta fw] exiting... Apr 26 08:07:46 192.168.122.209 [57817.197273] [tdb] Shutdown Tempesta DB Apr 26 08:07:46 192.168.122.209 [57817.411001] End test: http2_general.test_flow_control_window.TestFlowControl.test_several_stream Apr 26 08:07:46 192.168.122.209 [57817.426588] Start test: http2_general.test_flow_control_window.TestFlowControl.test_single_stream_no_trailer_in_response Apr 26 08:07:47 192.168.122.209 [57818.510086] [tdb] Start Tempesta DB Apr 26 08:07:48 192.168.122.209 [57818.649302] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:07:49 192.168.122.209 [57820.217876] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [57820.217876] Maybe that's fine, but it's worth checking the [57820.217876] config - if there is no relations between the [57820.217876] names, then host name confusion attack is possible. Apr 26 08:07:49 192.168.122.209 [57820.364343] [tempesta fw] Configuration processing is completed. Apr 26 08:07:49 192.168.122.209 [57820.413575] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:07:50 192.168.122.209 [57820.835230] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:07:50 192.168.122.209 [57820.861146] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:07:50 192.168.122.209 [57820.888510] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:07:50 192.168.122.209 [57820.956306] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:07:50 192.168.122.209 [57821.008251] [tempesta fw] Tempesta FW is ready Apr 26 08:07:51 192.168.122.209 [57821.966572] [tdb] Close table 'client0.tdb' Apr 26 08:07:51 192.168.122.209 [57822.147900] [tdb] Close table 'sessions0.tdb' Apr 26 08:07:54 192.168.122.209 [57825.367164] [tdb] Close table 'cache0.tdb' Apr 26 08:07:55 192.168.122.209 [57825.596211] [tdb] Close table 'filter0.tdb' Apr 26 08:07:55 192.168.122.209 [57825.596642] [tempesta fw] modules are stopped Apr 26 08:07:55 192.168.122.209 [57825.821614] [tempesta fw] exiting... Apr 26 08:07:55 192.168.122.209 [57825.925713] [tdb] Shutdown Tempesta DB Apr 26 08:07:55 192.168.122.209 [57826.131006] End test: http2_general.test_flow_control_window.TestFlowControl.test_single_stream_no_trailer_in_response Apr 26 08:07:55 192.168.122.209 [57826.148177] Start test: http2_general.test_flow_control_window.TestFlowControl.test_single_stream_trailer_in_response Apr 26 08:07:56 192.168.122.209 [57827.223893] [tdb] Start Tempesta DB Apr 26 08:07:56 192.168.122.209 [57827.373378] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:07:58 192.168.122.209 [57828.917764] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [57828.917764] Maybe that's fine, but it's worth checking the [57828.917764] config - if there is no relations between the [57828.917764] names, then host name confusion attack is possible. Apr 26 08:07:58 192.168.122.209 [57829.084743] [tempesta fw] Configuration processing is completed. Apr 26 08:07:58 192.168.122.209 [57829.137951] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:07:59 192.168.122.209 [57829.559129] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:07:59 192.168.122.209 [57829.586017] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:07:59 192.168.122.209 [57829.612625] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:07:59 192.168.122.209 [57829.656496] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:07:59 192.168.122.209 [57829.700287] [tempesta fw] Tempesta FW is ready Apr 26 08:08:00 192.168.122.209 [57830.867690] [tdb] Close table 'client0.tdb' Apr 26 08:08:00 192.168.122.209 [57831.050393] [tdb] Close table 'sessions0.tdb' Apr 26 08:08:03 192.168.122.209 [57834.264759] [tdb] Close table 'cache0.tdb' Apr 26 08:08:03 192.168.122.209 [57834.503237] [tdb] Close table 'filter0.tdb' Apr 26 08:08:03 192.168.122.209 [57834.503665] [tempesta fw] modules are stopped Apr 26 08:08:04 192.168.122.209 [57834.740182] [tempesta fw] exiting... Apr 26 08:08:04 192.168.122.209 [57834.871196] [tdb] Shutdown Tempesta DB Apr 26 08:08:04 192.168.122.209 [57835.090726] End test: http2_general.test_flow_control_window.TestFlowControl.test_single_stream_trailer_in_response Apr 26 08:08:04 192.168.122.209 [57835.111764] Start test: http2_general.test_h2_frame.TestH2Frame.test_continuation_frame Apr 26 08:08:05 192.168.122.209 [57836.131638] [tdb] Start Tempesta DB Apr 26 08:08:05 192.168.122.209 [57836.257738] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:08:07 192.168.122.209 [57837.897948] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [57837.897948] Maybe that's fine, but it's worth checking the [57837.897948] config - if there is no relations between the [57837.897948] names, then host name confusion attack is possible. Apr 26 08:08:07 192.168.122.209 [57838.040545] [tempesta fw] Configuration processing is completed. Apr 26 08:08:07 192.168.122.209 [57838.094047] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:08:07 192.168.122.209 [57838.515764] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:08:08 192.168.122.209 [57838.542965] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:08:08 192.168.122.209 [57838.569863] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:08:08 192.168.122.209 [57838.632529] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:08:08 192.168.122.209 [57838.676477] [tempesta fw] Tempesta FW is ready Apr 26 08:08:12 192.168.122.209 [57843.480204] [tdb] Close table 'client0.tdb' Apr 26 08:08:13 192.168.122.209 [57843.665705] [tdb] Close table 'sessions0.tdb' Apr 26 08:08:16 192.168.122.209 [57846.882039] [tdb] Close table 'cache0.tdb' Apr 26 08:08:16 192.168.122.209 [57847.119716] [tdb] Close table 'filter0.tdb' Apr 26 08:08:16 192.168.122.209 [57847.120155] [tempesta fw] modules are stopped Apr 26 08:08:16 192.168.122.209 [57847.373381] [tempesta fw] exiting... Apr 26 08:08:16 192.168.122.209 [57847.474004] [tdb] Shutdown Tempesta DB Apr 26 08:08:17 192.168.122.209 [57847.681970] End test: http2_general.test_h2_frame.TestH2Frame.test_continuation_frame Apr 26 08:08:17 192.168.122.209 [57847.698505] Start test: http2_general.test_h2_frame.TestH2Frame.test_data_framing Apr 26 08:08:18 192.168.122.209 [57848.812181] [tdb] Start Tempesta DB Apr 26 08:08:18 192.168.122.209 [57848.944341] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:08:20 192.168.122.209 [57850.530128] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [57850.530128] Maybe that's fine, but it's worth checking the [57850.530128] config - if there is no relations between the [57850.530128] names, then host name confusion attack is possible. Apr 26 08:08:20 192.168.122.209 [57850.672709] [tempesta fw] Configuration processing is completed. Apr 26 08:08:20 192.168.122.209 [57850.722838] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:08:20 192.168.122.209 [57851.145132] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:08:20 192.168.122.209 [57851.172833] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:08:20 192.168.122.209 [57851.199850] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:08:20 192.168.122.209 [57851.244687] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:08:20 192.168.122.209 [57851.284658] [tempesta fw] Tempesta FW is ready Apr 26 08:08:21 192.168.122.209 [57852.122290] [tdb] Close table 'client0.tdb' Apr 26 08:08:21 192.168.122.209 [57852.316979] [tdb] Close table 'sessions0.tdb' Apr 26 08:08:24 192.168.122.209 [57855.526053] [tdb] Close table 'cache0.tdb' Apr 26 08:08:25 192.168.122.209 [57855.764085] [tdb] Close table 'filter0.tdb' Apr 26 08:08:25 192.168.122.209 [57855.764505] [tempesta fw] modules are stopped Apr 26 08:08:25 192.168.122.209 [57856.030046] [tempesta fw] exiting... Apr 26 08:08:25 192.168.122.209 [57856.174930] [tdb] Shutdown Tempesta DB Apr 26 08:08:25 192.168.122.209 [57856.380159] End test: http2_general.test_h2_frame.TestH2Frame.test_data_framing Apr 26 08:08:25 192.168.122.209 [57856.409307] Start test: http2_general.test_h2_frame.TestH2Frame.test_empty_continuation_end_headers Apr 26 08:08:26 192.168.122.209 [57857.472544] [tdb] Start Tempesta DB Apr 26 08:08:27 192.168.122.209 [57857.600962] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:08:28 192.168.122.209 [57859.262751] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [57859.262751] Maybe that's fine, but it's worth checking the [57859.262751] config - if there is no relations between the [57859.262751] names, then host name confusion attack is possible. Apr 26 08:08:28 192.168.122.209 [57859.444809] [tempesta fw] Configuration processing is completed. Apr 26 08:08:28 192.168.122.209 [57859.502653] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:08:29 192.168.122.209 [57859.924179] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:08:29 192.168.122.209 [57859.951289] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:08:29 192.168.122.209 [57859.978576] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:08:29 192.168.122.209 [57860.036801] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:08:29 192.168.122.209 [57860.076761] [tempesta fw] Tempesta FW is ready Apr 26 08:08:30 192.168.122.209 [57860.703495] [tdb] Close table 'client0.tdb' Apr 26 08:08:30 192.168.122.209 [57860.900489] [tdb] Close table 'sessions0.tdb' Apr 26 08:08:33 192.168.122.209 [57864.165131] [tdb] Close table 'cache0.tdb' Apr 26 08:08:33 192.168.122.209 [57864.392543] [tdb] Close table 'filter0.tdb' Apr 26 08:08:33 192.168.122.209 [57864.393008] [tempesta fw] modules are stopped Apr 26 08:08:34 192.168.122.209 [57864.617275] [tempesta fw] exiting... Apr 26 08:08:34 192.168.122.209 [57864.773616] [tdb] Shutdown Tempesta DB Apr 26 08:08:34 192.168.122.209 [57864.976062] End test: http2_general.test_h2_frame.TestH2Frame.test_empty_continuation_end_headers Apr 26 08:08:34 192.168.122.209 [57864.997853] Start test: http2_general.test_h2_frame.TestH2Frame.test_empty_continuation_frame Apr 26 08:08:35 192.168.122.209 [57866.023860] [tdb] Start Tempesta DB Apr 26 08:08:35 192.168.122.209 [57866.172411] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:08:37 192.168.122.209 [57867.786455] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [57867.786455] Maybe that's fine, but it's worth checking the [57867.786455] config - if there is no relations between the [57867.786455] names, then host name confusion attack is possible. Apr 26 08:08:37 192.168.122.209 [57867.941226] [tempesta fw] Configuration processing is completed. Apr 26 08:08:37 192.168.122.209 [57867.997656] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:08:37 192.168.122.209 [57868.456818] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:08:37 192.168.122.209 [57868.486546] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:08:37 192.168.122.209 [57868.515898] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:08:38 192.168.122.209 [57868.564911] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:08:38 192.168.122.209 [57868.608864] [tempesta fw] Tempesta FW is ready Apr 26 08:08:38 192.168.122.209 [57868.838998] [tempesta fw] Empty CONTINUATION frame without END_HEADERS Apr 26 08:08:38 192.168.122.209 [57869.268882] [tdb] Close table 'client0.tdb' Apr 26 08:08:38 192.168.122.209 [57869.467321] [tdb] Close table 'sessions0.tdb' Apr 26 08:08:42 192.168.122.209 [57872.790541] [tdb] Close table 'cache0.tdb' Apr 26 08:08:42 192.168.122.209 [57873.058961] [tdb] Close table 'filter0.tdb' Apr 26 08:08:42 192.168.122.209 [57873.059406] [tempesta fw] modules are stopped Apr 26 08:08:42 192.168.122.209 [57873.282102] [tempesta fw] exiting... Apr 26 08:08:42 192.168.122.209 [57873.435051] [tdb] Shutdown Tempesta DB Apr 26 08:08:43 192.168.122.209 [57873.677789] End test: http2_general.test_h2_frame.TestH2Frame.test_empty_continuation_frame Apr 26 08:08:43 192.168.122.209 [57873.698588] Start test: http2_general.test_h2_frame.TestH2Frame.test_empty_data_frame Apr 26 08:08:44 192.168.122.209 [57874.783687] [tdb] Start Tempesta DB Apr 26 08:08:44 192.168.122.209 [57874.935206] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:08:46 192.168.122.209 [57876.574612] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [57876.574612] Maybe that's fine, but it's worth checking the [57876.574612] config - if there is no relations between the [57876.574612] names, then host name confusion attack is possible. Apr 26 08:08:46 192.168.122.209 [57876.725055] [tempesta fw] Configuration processing is completed. Apr 26 08:08:46 192.168.122.209 [57876.779351] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:08:46 192.168.122.209 [57877.238307] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:08:46 192.168.122.209 [57877.270875] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:08:46 192.168.122.209 [57877.300533] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:08:46 192.168.122.209 [57877.405080] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:08:46 192.168.122.209 [57877.448967] [tempesta fw] Tempesta FW is ready Apr 26 08:08:47 192.168.122.209 [57877.665460] [tempesta fw] Empty DATA frame without END_STREAM Apr 26 08:08:47 192.168.122.209 [57878.078036] [tdb] Close table 'client0.tdb' Apr 26 08:08:47 192.168.122.209 [57878.272323] [tdb] Close table 'sessions0.tdb' Apr 26 08:08:50 192.168.122.209 [57881.503856] [tdb] Close table 'cache0.tdb' Apr 26 08:08:51 192.168.122.209 [57881.729914] [tdb] Close table 'filter0.tdb' Apr 26 08:08:51 192.168.122.209 [57881.730358] [tempesta fw] modules are stopped Apr 26 08:08:51 192.168.122.209 [57881.955085] [tempesta fw] exiting... Apr 26 08:08:51 192.168.122.209 [57882.061068] [tdb] Shutdown Tempesta DB Apr 26 08:08:51 192.168.122.209 [57882.275854] End test: http2_general.test_h2_frame.TestH2Frame.test_empty_data_frame Apr 26 08:08:51 192.168.122.209 [57882.293467] Start test: http2_general.test_h2_frame.TestH2Frame.test_empty_data_frame_mixed Apr 26 08:08:52 192.168.122.209 [57883.362562] [tdb] Start Tempesta DB Apr 26 08:08:52 192.168.122.209 [57883.521174] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:08:54 192.168.122.209 [57885.182663] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [57885.182663] Maybe that's fine, but it's worth checking the [57885.182663] config - if there is no relations between the [57885.182663] names, then host name confusion attack is possible. Apr 26 08:08:54 192.168.122.209 [57885.329144] [tempesta fw] Configuration processing is completed. Apr 26 08:08:54 192.168.122.209 [57885.379521] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:08:55 192.168.122.209 [57885.807188] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:08:55 192.168.122.209 [57885.834341] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:08:55 192.168.122.209 [57885.861769] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:08:55 192.168.122.209 [57885.909129] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:08:55 192.168.122.209 [57885.949080] [tempesta fw] Tempesta FW is ready Apr 26 08:08:56 192.168.122.209 [57886.152285] [tempesta fw] Empty DATA frame without END_STREAM Apr 26 08:08:56 192.168.122.209 [57886.564485] [tdb] Close table 'client0.tdb' Apr 26 08:08:56 192.168.122.209 [57886.758405] [tdb] Close table 'sessions0.tdb' Apr 26 08:08:59 192.168.122.209 [57889.917912] [tdb] Close table 'cache0.tdb' Apr 26 08:08:59 192.168.122.209 [57890.164231] [tdb] Close table 'filter0.tdb' Apr 26 08:08:59 192.168.122.209 [57890.164666] [tempesta fw] modules are stopped Apr 26 08:08:59 192.168.122.209 [57890.372590] [tempesta fw] exiting... Apr 26 08:08:59 192.168.122.209 [57890.497227] [tdb] Shutdown Tempesta DB Apr 26 08:09:00 192.168.122.209 [57890.734723] End test: http2_general.test_h2_frame.TestH2Frame.test_empty_data_frame_mixed Apr 26 08:09:00 192.168.122.209 [57890.754819] Start test: http2_general.test_h2_frame.TestH2Frame.test_empty_headers_empty_continuation_multiple Apr 26 08:09:01 192.168.122.209 [57891.858474] [tdb] Start Tempesta DB Apr 26 08:09:01 192.168.122.209 [57892.019936] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:09:03 192.168.122.209 [57893.714680] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [57893.714680] Maybe that's fine, but it's worth checking the [57893.714680] config - if there is no relations between the [57893.714680] names, then host name confusion attack is possible. Apr 26 08:09:03 192.168.122.209 [57893.861253] [tempesta fw] Configuration processing is completed. Apr 26 08:09:03 192.168.122.209 [57893.911154] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:09:03 192.168.122.209 [57894.456532] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:09:03 192.168.122.209 [57894.492467] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:09:03 192.168.122.209 [57894.527053] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:09:04 192.168.122.209 [57894.565213] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:09:04 192.168.122.209 [57894.605184] [tempesta fw] Tempesta FW is ready Apr 26 08:09:04 192.168.122.209 [57895.245298] [tdb] Close table 'client0.tdb' Apr 26 08:09:04 192.168.122.209 [57895.425392] [tdb] Close table 'sessions0.tdb' Apr 26 08:09:08 192.168.122.209 [57898.660219] [tdb] Close table 'cache0.tdb' Apr 26 08:09:08 192.168.122.209 [57898.906126] [tdb] Close table 'filter0.tdb' Apr 26 08:09:08 192.168.122.209 [57898.906571] [tempesta fw] modules are stopped Apr 26 08:09:08 192.168.122.209 [57899.119112] [tempesta fw] exiting... Apr 26 08:09:08 192.168.122.209 [57899.273211] [tdb] Shutdown Tempesta DB Apr 26 08:09:08 192.168.122.209 [57899.527117] End test: http2_general.test_h2_frame.TestH2Frame.test_empty_headers_empty_continuation_multiple Apr 26 08:09:09 192.168.122.209 [57899.539132] Start test: http2_general.test_h2_frame.TestH2Frame.test_empty_headers_frame_end_headers Apr 26 08:09:10 192.168.122.209 [57900.622008] [tdb] Start Tempesta DB Apr 26 08:09:10 192.168.122.209 [57900.760221] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:09:11 192.168.122.209 [57902.374204] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [57902.374204] Maybe that's fine, but it's worth checking the [57902.374204] config - if there is no relations between the [57902.374204] names, then host name confusion attack is possible. Apr 26 08:09:11 192.168.122.209 [57902.529316] [tempesta fw] Configuration processing is completed. Apr 26 08:09:12 192.168.122.209 [57902.585919] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:09:12 192.168.122.209 [57903.005847] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:09:12 192.168.122.209 [57903.032730] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:09:12 192.168.122.209 [57903.061498] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:09:12 192.168.122.209 [57903.117337] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:09:12 192.168.122.209 [57903.157296] [tempesta fw] Tempesta FW is ready Apr 26 08:09:13 192.168.122.209 [57903.822824] [tdb] Close table 'client0.tdb' Apr 26 08:09:13 192.168.122.209 [57904.022009] [tdb] Close table 'sessions0.tdb' Apr 26 08:09:16 192.168.122.209 [57907.320375] [tdb] Close table 'cache0.tdb' Apr 26 08:09:17 192.168.122.209 [57907.594093] [tdb] Close table 'filter0.tdb' Apr 26 08:09:17 192.168.122.209 [57907.594506] [tempesta fw] modules are stopped Apr 26 08:09:17 192.168.122.209 [57907.889492] [tempesta fw] exiting... Apr 26 08:09:17 192.168.122.209 [57908.006546] [tdb] Shutdown Tempesta DB Apr 26 08:09:17 192.168.122.209 [57908.224968] End test: http2_general.test_h2_frame.TestH2Frame.test_empty_headers_frame_end_headers Apr 26 08:09:17 192.168.122.209 [57908.252493] Start test: http2_general.test_h2_frame.TestH2Frame.test_empty_headers_frame_no_end_headers Apr 26 08:09:18 192.168.122.209 [57909.290757] [tdb] Start Tempesta DB Apr 26 08:09:18 192.168.122.209 [57909.422964] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:09:20 192.168.122.209 [57910.982926] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [57910.982926] Maybe that's fine, but it's worth checking the [57910.982926] config - if there is no relations between the [57910.982926] names, then host name confusion attack is possible. Apr 26 08:09:20 192.168.122.209 [57911.141452] [tempesta fw] Configuration processing is completed. Apr 26 08:09:20 192.168.122.209 [57911.208350] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:09:21 192.168.122.209 [57911.764315] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:09:21 192.168.122.209 [57911.798318] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:09:21 192.168.122.209 [57911.832390] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:09:21 192.168.122.209 [57911.877447] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:09:21 192.168.122.209 [57911.917408] [tempesta fw] Tempesta FW is ready Apr 26 08:09:21 192.168.122.209 [57912.521543] [tdb] Close table 'client0.tdb' Apr 26 08:09:22 192.168.122.209 [57912.725825] [tdb] Close table 'sessions0.tdb' Apr 26 08:09:25 192.168.122.209 [57916.025097] [tdb] Close table 'cache0.tdb' Apr 26 08:09:25 192.168.122.209 [57916.278738] [tdb] Close table 'filter0.tdb' Apr 26 08:09:25 192.168.122.209 [57916.279193] [tempesta fw] modules are stopped Apr 26 08:09:25 192.168.122.209 [57916.476799] [tempesta fw] exiting... Apr 26 08:09:26 192.168.122.209 [57916.605683] [tdb] Shutdown Tempesta DB Apr 26 08:09:26 192.168.122.209 [57916.822603] End test: http2_general.test_h2_frame.TestH2Frame.test_empty_headers_frame_no_end_headers Apr 26 08:09:26 192.168.122.209 [57916.841777] Start test: http2_general.test_h2_frame.TestH2Frame.test_empty_last_data_frame Apr 26 08:09:27 192.168.122.209 [57917.872065] [tdb] Start Tempesta DB Apr 26 08:09:27 192.168.122.209 [57918.024689] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:09:29 192.168.122.209 [57919.699023] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [57919.699023] Maybe that's fine, but it's worth checking the [57919.699023] config - if there is no relations between the [57919.699023] names, then host name confusion attack is possible. Apr 26 08:09:29 192.168.122.209 [57919.857577] [tempesta fw] Configuration processing is completed. Apr 26 08:09:29 192.168.122.209 [57919.907901] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:09:29 192.168.122.209 [57920.323436] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:09:29 192.168.122.209 [57920.351784] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:09:29 192.168.122.209 [57920.380027] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:09:29 192.168.122.209 [57920.421556] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:09:29 192.168.122.209 [57920.461519] [tempesta fw] Tempesta FW is ready Apr 26 08:09:30 192.168.122.209 [57921.054651] [tdb] Close table 'client0.tdb' Apr 26 08:09:30 192.168.122.209 [57921.245789] [tdb] Close table 'sessions0.tdb' Apr 26 08:09:33 192.168.122.209 [57924.432924] [tdb] Close table 'cache0.tdb' Apr 26 08:09:34 192.168.122.209 [57924.684986] [tdb] Close table 'filter0.tdb' Apr 26 08:09:34 192.168.122.209 [57924.685431] [tempesta fw] modules are stopped Apr 26 08:09:34 192.168.122.209 [57924.913335] [tempesta fw] exiting... Apr 26 08:09:34 192.168.122.209 [57925.042179] [tdb] Shutdown Tempesta DB Apr 26 08:09:34 192.168.122.209 [57925.275378] End test: http2_general.test_h2_frame.TestH2Frame.test_empty_last_data_frame Apr 26 08:09:34 192.168.122.209 [57925.291307] Start test: http2_general.test_h2_frame.TestH2Frame.test_goaway_frame_in_request Apr 26 08:09:35 192.168.122.209 [57926.379401] [tdb] Start Tempesta DB Apr 26 08:09:35 192.168.122.209 [57926.522480] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:09:37 192.168.122.209 [57928.047081] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [57928.047081] Maybe that's fine, but it's worth checking the [57928.047081] config - if there is no relations between the [57928.047081] names, then host name confusion attack is possible. Apr 26 08:09:37 192.168.122.209 [57928.197839] [tempesta fw] Configuration processing is completed. Apr 26 08:09:37 192.168.122.209 [57928.248935] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:09:38 192.168.122.209 [57928.664504] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:09:38 192.168.122.209 [57928.690936] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:09:38 192.168.122.209 [57928.718696] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:09:38 192.168.122.209 [57928.773718] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:09:38 192.168.122.209 [57928.821629] [tempesta fw] Tempesta FW is ready Apr 26 08:09:38 192.168.122.209 [57929.040403] [tempesta fw] HTTP/2 connection is closed by client with error code: 1, ID of last processed stream: 4 Apr 26 08:09:38 192.168.122.209 [57929.476873] [tdb] Close table 'client0.tdb' Apr 26 08:09:39 192.168.122.209 [57929.672228] [tdb] Close table 'sessions0.tdb' Apr 26 08:09:42 192.168.122.209 [57932.887896] [tdb] Close table 'cache0.tdb' Apr 26 08:09:42 192.168.122.209 [57933.141422] [tdb] Close table 'filter0.tdb' Apr 26 08:09:42 192.168.122.209 [57933.141868] [tempesta fw] modules are stopped Apr 26 08:09:42 192.168.122.209 [57933.349166] [tempesta fw] exiting... Apr 26 08:09:42 192.168.122.209 [57933.449740] [tdb] Shutdown Tempesta DB Apr 26 08:09:43 192.168.122.209 [57933.645020] End test: http2_general.test_h2_frame.TestH2Frame.test_goaway_frame_in_request Apr 26 08:09:43 192.168.122.209 [57933.680520] Start test: http2_general.test_h2_frame.TestH2Frame.test_goaway_frame_in_response Apr 26 08:09:44 192.168.122.209 [57934.693849] [tdb] Start Tempesta DB Apr 26 08:09:44 192.168.122.209 [57934.832014] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:09:45 192.168.122.209 [57936.527234] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [57936.527234] Maybe that's fine, but it's worth checking the [57936.527234] config - if there is no relations between the [57936.527234] names, then host name confusion attack is possible. Apr 26 08:09:46 192.168.122.209 [57936.694082] [tempesta fw] Configuration processing is completed. Apr 26 08:09:46 192.168.122.209 [57936.747298] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:09:46 192.168.122.209 [57937.165965] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:09:46 192.168.122.209 [57937.193313] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:09:46 192.168.122.209 [57937.220406] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:09:46 192.168.122.209 [57937.265774] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:09:46 192.168.122.209 [57937.317750] [tempesta fw] Tempesta FW is ready Apr 26 08:09:47 192.168.122.209 [57937.951935] [tdb] Close table 'client0.tdb' Apr 26 08:09:47 192.168.122.209 [57938.147104] [tdb] Close table 'sessions0.tdb' Apr 26 08:09:50 192.168.122.209 [57941.310975] [tdb] Close table 'cache0.tdb' Apr 26 08:09:51 192.168.122.209 [57941.564266] [tdb] Close table 'filter0.tdb' Apr 26 08:09:51 192.168.122.209 [57941.564702] [tempesta fw] modules are stopped Apr 26 08:09:51 192.168.122.209 [57941.774934] [tempesta fw] exiting... Apr 26 08:09:51 192.168.122.209 [57941.919569] [tdb] Shutdown Tempesta DB Apr 26 08:09:51 192.168.122.209 [57942.138304] End test: http2_general.test_h2_frame.TestH2Frame.test_goaway_frame_in_response Apr 26 08:09:51 192.168.122.209 [57942.155167] Start test: http2_general.test_h2_frame.TestH2Frame.test_multiple_empty_headers_frames Apr 26 08:09:52 192.168.122.209 [57943.222466] [tdb] Start Tempesta DB Apr 26 08:09:52 192.168.122.209 [57943.355936] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:09:54 192.168.122.209 [57944.943314] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [57944.943314] Maybe that's fine, but it's worth checking the [57944.943314] config - if there is no relations between the [57944.943314] names, then host name confusion attack is possible. Apr 26 08:09:54 192.168.122.209 [57945.101880] [tempesta fw] Configuration processing is completed. Apr 26 08:09:54 192.168.122.209 [57945.162017] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:09:55 192.168.122.209 [57945.593442] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:09:55 192.168.122.209 [57945.622002] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:09:55 192.168.122.209 [57945.650163] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:09:55 192.168.122.209 [57945.705897] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:09:55 192.168.122.209 [57945.745836] [tempesta fw] Tempesta FW is ready Apr 26 08:09:55 192.168.122.209 [57946.409955] [tdb] Close table 'client0.tdb' Apr 26 08:09:56 192.168.122.209 [57946.598587] [tdb] Close table 'sessions0.tdb' Apr 26 08:09:59 192.168.122.209 [57949.806486] [tdb] Close table 'cache0.tdb' Apr 26 08:09:59 192.168.122.209 [57950.047178] [tdb] Close table 'filter0.tdb' Apr 26 08:09:59 192.168.122.209 [57950.047615] [tempesta fw] modules are stopped Apr 26 08:09:59 192.168.122.209 [57950.307945] [tempesta fw] exiting... Apr 26 08:09:59 192.168.122.209 [57950.446291] [tdb] Shutdown Tempesta DB Apr 26 08:10:00 192.168.122.209 [57950.688022] End test: http2_general.test_h2_frame.TestH2Frame.test_multiple_empty_headers_frames Apr 26 08:10:00 192.168.122.209 [57950.705410] Start test: http2_general.test_h2_frame.TestH2Frame.test_opening_same_stream_after_invalid Apr 26 08:10:01 192.168.122.209 [57951.791822] [tdb] Start Tempesta DB Apr 26 08:10:01 192.168.122.209 [57951.930502] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:10:02 192.168.122.209 [57953.527430] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [57953.527430] Maybe that's fine, but it's worth checking the [57953.527430] config - if there is no relations between the [57953.527430] names, then host name confusion attack is possible. Apr 26 08:10:03 192.168.122.209 [57953.726182] [tempesta fw] Configuration processing is completed. Apr 26 08:10:03 192.168.122.209 [57953.776861] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:10:03 192.168.122.209 [57954.208454] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:10:03 192.168.122.209 [57954.235357] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:10:03 192.168.122.209 [57954.274896] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:10:03 192.168.122.209 [57954.345983] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:10:03 192.168.122.209 [57954.385899] [tempesta fw] Tempesta FW is ready Apr 26 08:10:04 192.168.122.209 [57955.014678] [tdb] Close table 'client0.tdb' Apr 26 08:10:04 192.168.122.209 [57955.198640] [tdb] Close table 'sessions0.tdb' Apr 26 08:10:07 192.168.122.209 [57958.373903] [tdb] Close table 'cache0.tdb' Apr 26 08:10:08 192.168.122.209 [57958.622216] [tdb] Close table 'filter0.tdb' Apr 26 08:10:08 192.168.122.209 [57958.622658] [tempesta fw] modules are stopped Apr 26 08:10:08 192.168.122.209 [57958.847257] [tempesta fw] exiting... Apr 26 08:10:08 192.168.122.209 [57958.950192] [tdb] Shutdown Tempesta DB Apr 26 08:10:08 192.168.122.209 [57959.195416] End test: http2_general.test_h2_frame.TestH2Frame.test_opening_same_stream_after_invalid Apr 26 08:10:08 192.168.122.209 [57959.210780] Start test: http2_general.test_h2_frame.TestH2Frame.test_rst_frame_in_request Apr 26 08:10:09 192.168.122.209 [57960.258587] [tdb] Start Tempesta DB Apr 26 08:10:09 192.168.122.209 [57960.397842] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:10:11 192.168.122.209 [57962.007509] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [57962.007509] Maybe that's fine, but it's worth checking the [57962.007509] config - if there is no relations between the [57962.007509] names, then host name confusion attack is possible. Apr 26 08:10:11 192.168.122.209 [57962.182094] [tempesta fw] Configuration processing is completed. Apr 26 08:10:11 192.168.122.209 [57962.232319] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:10:12 192.168.122.209 [57962.643744] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:10:12 192.168.122.209 [57962.670502] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:10:12 192.168.122.209 [57962.697585] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:10:12 192.168.122.209 [57962.758085] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:10:12 192.168.122.209 [57962.798042] [tempesta fw] Tempesta FW is ready Apr 26 08:10:12 192.168.122.209 [57963.450412] [tdb] Close table 'client0.tdb' Apr 26 08:10:13 192.168.122.209 [57963.654036] [tdb] Close table 'sessions0.tdb' Apr 26 08:10:16 192.168.122.209 [57966.852696] [tdb] Close table 'cache0.tdb' Apr 26 08:10:16 192.168.122.209 [57967.107521] [tdb] Close table 'filter0.tdb' Apr 26 08:10:16 192.168.122.209 [57967.107967] [tempesta fw] modules are stopped Apr 26 08:10:16 192.168.122.209 [57967.318558] [tempesta fw] exiting... Apr 26 08:10:16 192.168.122.209 [57967.430421] [tdb] Shutdown Tempesta DB Apr 26 08:10:17 192.168.122.209 [57967.658633] End test: http2_general.test_h2_frame.TestH2Frame.test_rst_frame_in_request Apr 26 08:10:17 192.168.122.209 [57967.685168] Start test: http2_general.test_h2_frame.TestH2Frame.test_rst_frame_in_response Apr 26 08:10:18 192.168.122.209 [57968.741781] [tdb] Start Tempesta DB Apr 26 08:10:18 192.168.122.209 [57968.891889] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:10:19 192.168.122.209 [57970.467657] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [57970.467657] Maybe that's fine, but it's worth checking the [57970.467657] config - if there is no relations between the [57970.467657] names, then host name confusion attack is possible. Apr 26 08:10:20 192.168.122.209 [57970.630202] [tempesta fw] Configuration processing is completed. Apr 26 08:10:20 192.168.122.209 [57970.680501] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:10:20 192.168.122.209 [57971.146929] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:10:20 192.168.122.209 [57971.176807] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:10:20 192.168.122.209 [57971.206388] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:10:20 192.168.122.209 [57971.270131] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:10:20 192.168.122.209 [57971.322142] [tempesta fw] Tempesta FW is ready Apr 26 08:10:21 192.168.122.209 [57971.540317] [tempesta fw] Warning: request dropped: incorrect X-Forwarded-For header: 127.0.0.2 Apr 26 08:10:21 192.168.122.209 [57972.011281] [tdb] Close table 'client0.tdb' Apr 26 08:10:21 192.168.122.209 [57972.203437] [tdb] Close table 'sessions0.tdb' Apr 26 08:10:24 192.168.122.209 [57975.396047] [tdb] Close table 'cache0.tdb' Apr 26 08:10:25 192.168.122.209 [57975.646686] [tdb] Close table 'filter0.tdb' Apr 26 08:10:25 192.168.122.209 [57975.647111] [tempesta fw] modules are stopped Apr 26 08:10:25 192.168.122.209 [57975.889937] [tempesta fw] exiting... Apr 26 08:10:25 192.168.122.209 [57976.011752] [tdb] Shutdown Tempesta DB Apr 26 08:10:25 192.168.122.209 [57976.240140] End test: http2_general.test_h2_frame.TestH2Frame.test_rst_frame_in_response Apr 26 08:10:25 192.168.122.209 [57976.264523] Start test: http2_general.test_h2_frame.TestH2Frame.test_rst_stream_with_id_0 Apr 26 08:10:26 192.168.122.209 [57977.380045] [tdb] Start Tempesta DB Apr 26 08:10:27 192.168.122.209 [57977.535196] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:10:28 192.168.122.209 [57979.203839] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [57979.203839] Maybe that's fine, but it's worth checking the [57979.203839] config - if there is no relations between the [57979.203839] names, then host name confusion attack is possible. Apr 26 08:10:28 192.168.122.209 [57979.350368] [tempesta fw] Configuration processing is completed. Apr 26 08:10:28 192.168.122.209 [57979.403952] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:10:29 192.168.122.209 [57979.864656] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:10:29 192.168.122.209 [57979.902793] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:10:29 192.168.122.209 [57979.931958] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:10:29 192.168.122.209 [57979.974247] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:10:29 192.168.122.209 [57980.018267] [tempesta fw] Tempesta FW is ready Apr 26 08:10:30 192.168.122.209 [57980.689866] [tdb] Close table 'client0.tdb' Apr 26 08:10:30 192.168.122.209 [57980.886877] [tdb] Close table 'sessions0.tdb' Apr 26 08:10:33 192.168.122.209 [57984.118708] [tdb] Close table 'cache0.tdb' Apr 26 08:10:33 192.168.122.209 [57984.376874] [tdb] Close table 'filter0.tdb' Apr 26 08:10:33 192.168.122.209 [57984.377304] [tempesta fw] modules are stopped Apr 26 08:10:34 192.168.122.209 [57984.605415] [tempesta fw] exiting... Apr 26 08:10:34 192.168.122.209 [57984.710107] [tdb] Shutdown Tempesta DB Apr 26 08:10:34 192.168.122.209 [57984.945209] End test: http2_general.test_h2_frame.TestH2Frame.test_rst_stream_with_id_0 Apr 26 08:10:34 192.168.122.209 [57984.959392] Start test: http2_general.test_h2_frame.TestH2Frame.test_settings_frame Apr 26 08:10:35 192.168.122.209 [57986.070379] [tdb] Start Tempesta DB Apr 26 08:10:35 192.168.122.209 [57986.221799] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:10:37 192.168.122.209 [57987.847875] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [57987.847875] Maybe that's fine, but it's worth checking the [57987.847875] config - if there is no relations between the [57987.847875] names, then host name confusion attack is possible. Apr 26 08:10:37 192.168.122.209 [57987.998430] [tempesta fw] Configuration processing is completed. Apr 26 08:10:37 192.168.122.209 [57988.053881] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:10:37 192.168.122.209 [57988.512611] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:10:38 192.168.122.209 [57988.541921] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:10:38 192.168.122.209 [57988.572603] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:10:38 192.168.122.209 [57988.614385] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:10:38 192.168.122.209 [57988.658368] [tempesta fw] Tempesta FW is ready Apr 26 08:10:38 192.168.122.209 [57989.332720] [tdb] Close table 'client0.tdb' Apr 26 08:10:38 192.168.122.209 [57989.527330] [tdb] Close table 'sessions0.tdb' Apr 26 08:10:42 192.168.122.209 [57992.795246] [tdb] Close table 'cache0.tdb' Apr 26 08:10:42 192.168.122.209 [57993.066689] [tdb] Close table 'filter0.tdb' Apr 26 08:10:42 192.168.122.209 [57993.067115] [tempesta fw] modules are stopped Apr 26 08:10:42 192.168.122.209 [57993.282684] [tempesta fw] exiting... Apr 26 08:10:42 192.168.122.209 [57993.440199] [tdb] Shutdown Tempesta DB Apr 26 08:10:43 192.168.122.209 [57993.680890] End test: http2_general.test_h2_frame.TestH2Frame.test_settings_frame Apr 26 08:10:43 192.168.122.209 [57993.692616] Start test: http2_general.test_h2_frame.TestH2Frame.test_trailer_header_frame_without_end_stream Apr 26 08:10:44 192.168.122.209 [57994.777481] [tdb] Start Tempesta DB Apr 26 08:10:44 192.168.122.209 [57994.916226] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:10:45 192.168.122.209 [57996.507912] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [57996.507912] Maybe that's fine, but it's worth checking the [57996.507912] config - if there is no relations between the [57996.507912] names, then host name confusion attack is possible. Apr 26 08:10:46 192.168.122.209 [57996.654539] [tempesta fw] Configuration processing is completed. Apr 26 08:10:46 192.168.122.209 [57996.712786] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:10:46 192.168.122.209 [57997.212684] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:10:46 192.168.122.209 [57997.247702] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:10:46 192.168.122.209 [57997.282594] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:10:46 192.168.122.209 [57997.326509] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:10:46 192.168.122.209 [57997.370471] [tempesta fw] Tempesta FW is ready Apr 26 08:10:47 192.168.122.209 [57997.997586] [tdb] Close table 'client0.tdb' Apr 26 08:10:47 192.168.122.209 [57998.191374] [tdb] Close table 'sessions0.tdb' Apr 26 08:10:50 192.168.122.209 [58001.414255] [tdb] Close table 'cache0.tdb' Apr 26 08:10:51 192.168.122.209 [58001.673641] [tdb] Close table 'filter0.tdb' Apr 26 08:10:51 192.168.122.209 [58001.674113] [tempesta fw] modules are stopped Apr 26 08:10:51 192.168.122.209 [58001.898690] [tempesta fw] exiting... Apr 26 08:10:51 192.168.122.209 [58002.058421] [tdb] Shutdown Tempesta DB Apr 26 08:10:51 192.168.122.209 [58002.284918] End test: http2_general.test_h2_frame.TestH2Frame.test_trailer_header_frame_without_end_stream Apr 26 08:10:51 192.168.122.209 [58002.294866] Start test: http2_general.test_h2_frame.TestH2Frame.test_window_update_frame Apr 26 08:10:52 192.168.122.209 [58003.411410] [tdb] Start Tempesta DB Apr 26 08:10:53 192.168.122.209 [58003.543311] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:10:54 192.168.122.209 [58005.116068] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58005.116068] Maybe that's fine, but it's worth checking the [58005.116068] config - if there is no relations between the [58005.116068] names, then host name confusion attack is possible. Apr 26 08:10:54 192.168.122.209 [58005.254663] [tempesta fw] Configuration processing is completed. Apr 26 08:10:54 192.168.122.209 [58005.307190] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:10:55 192.168.122.209 [58005.735986] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:10:55 192.168.122.209 [58005.762665] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:10:55 192.168.122.209 [58005.792969] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:10:55 192.168.122.209 [58005.866630] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:10:55 192.168.122.209 [58005.918577] [tempesta fw] Tempesta FW is ready Apr 26 08:10:56 192.168.122.209 [58006.569388] [tdb] Close table 'client0.tdb' Apr 26 08:10:56 192.168.122.209 [58006.763757] [tdb] Close table 'sessions0.tdb' Apr 26 08:10:59 192.168.122.209 [58009.983314] [tdb] Close table 'cache0.tdb' Apr 26 08:10:59 192.168.122.209 [58010.247321] [tdb] Close table 'filter0.tdb' Apr 26 08:10:59 192.168.122.209 [58010.247753] [tempesta fw] modules are stopped Apr 26 08:10:59 192.168.122.209 [58010.508623] [tempesta fw] exiting... Apr 26 08:11:00 192.168.122.209 [58010.638878] [tdb] Shutdown Tempesta DB Apr 26 08:11:00 192.168.122.209 [58010.839798] End test: http2_general.test_h2_frame.TestH2Frame.test_window_update_frame Apr 26 08:11:00 192.168.122.209 [58010.863895] Start test: http2_general.test_h2_frame.TestH2FrameEnabledDisabledTsoGroGso.test_data_frame Apr 26 08:11:01 192.168.122.209 [58011.934516] [tdb] Start Tempesta DB Apr 26 08:11:01 192.168.122.209 [58012.071685] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:11:03 192.168.122.209 [58013.624082] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58013.624082] Maybe that's fine, but it's worth checking the [58013.624082] config - if there is no relations between the [58013.624082] names, then host name confusion attack is possible. Apr 26 08:11:03 192.168.122.209 [58013.782669] [tempesta fw] Configuration processing is completed. Apr 26 08:11:03 192.168.122.209 [58013.835980] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:11:03 192.168.122.209 [58014.248953] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:11:03 192.168.122.209 [58014.276391] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:11:03 192.168.122.209 [58014.304420] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:11:03 192.168.122.209 [58014.342682] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:11:03 192.168.122.209 [58014.382688] [tempesta fw] Tempesta FW is ready Apr 26 08:11:09 192.168.122.209 [58019.713895] swapper/1: page allocation failure: order:9, mode:0x40a20(GFP_ATOMIC|__GFP_COMP), nodemask=(null),cpuset=/,mems_allowed=0 Apr 26 08:11:09 192.168.122.209 [58019.715059] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G OE 5.10.35.tfw-39c65d3-debug #1 Apr 26 08:11:09 192.168.122.209 [58019.715845] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 Apr 26 08:11:09 192.168.122.209 [58019.716664] Call Trace: Apr 26 08:11:09 192.168.122.209 [58019.716897] Apr 26 08:11:09 192.168.122.209 [58019.717142] dump_stack+0x96/0xc4 Apr 26 08:11:09 192.168.122.209 [58019.717456] warn_alloc.cold+0x87/0x12a Apr 26 08:11:09 192.168.122.209 [58019.717823] ? zone_watermark_ok_safe+0x140/0x140 Apr 26 08:11:09 192.168.122.209 [58019.718254] ? __kasan_check_read+0x11/0x20 Apr 26 08:11:09 192.168.122.209 [58019.718648] ? wakeup_kswapd+0xba/0x290 Apr 26 08:11:09 192.168.122.209 [58019.718995] ? __zone_watermark_ok+0x270/0x270 Apr 26 08:11:09 192.168.122.209 [58019.719400] ? wake_all_kswapds+0xf4/0x140 Apr 26 08:11:09 192.168.122.209 [58019.719772] ? __alloc_pages_slowpath.constprop.0+0x11f4/0x1390 Apr 26 08:11:09 192.168.122.209 [58019.720295] __alloc_pages_slowpath.constprop.0+0x1359/0x1390 Apr 26 08:11:09 192.168.122.209 [58019.720806] ? warn_alloc+0x120/0x120 Apr 26 08:11:09 192.168.122.209 [58019.721156] ? __cpa_process_fault+0x800/0x800 Apr 26 08:11:09 192.168.122.209 [58019.721573] ? eth_get_headlen+0x140/0x140 Apr 26 08:11:09 192.168.122.209 [58019.721941] ? __zone_watermark_ok+0x270/0x270 Apr 26 08:11:09 192.168.122.209 [58019.722352] ? netif_rx+0x1c/0xf0 Apr 26 08:11:09 192.168.122.209 [58019.722654] __alloc_pages_nodemask+0x509/0x540 Apr 26 08:11:09 192.168.122.209 [58019.723064] ? __alloc_pages_slowpath.constprop.0+0x1390/0x1390 Apr 26 08:11:09 192.168.122.209 [58019.723591] ? __kernel_map_pages+0x108/0x180 Apr 26 08:11:09 192.168.122.209 [58019.723979] ? set_direct_map_default_noflush+0x130/0x130 Apr 26 08:11:09 192.168.122.209 [58019.724465] alloc_pages_current+0x96/0x140 Apr 26 08:11:09 192.168.122.209 [58019.724843] __get_free_pages+0x12/0x60 Apr 26 08:11:09 192.168.122.209 [58019.725232] tfw_pool_alloc_pages+0x9b/0xc0 [tempesta_fw] Apr 26 08:11:09 192.168.122.209 [58019.725745] __tfw_pool_realloc+0x123/0x1a0 [tempesta_fw] Apr 26 08:11:09 192.168.122.209 [58019.726254] __str_grow_tree+0x89/0x210 [tempesta_fw] Apr 26 08:11:09 192.168.122.209 [58019.726739] tfw_str_add_compound+0x33/0x40 [tempesta_fw] Apr 26 08:11:09 192.168.122.209 [58019.727243] __tfw_http_msg_add_str_data+0x88/0x1c0 [tempesta_fw] Apr 26 08:11:09 192.168.122.209 [58019.727808] tfw_http_parse_resp+0x11376/0x197d0 [tempesta_fw] Apr 26 08:11:09 192.168.122.209 [58019.728351] ? __resp_parse_body+0xb50/0xb50 [tempesta_fw] Apr 26 08:11:09 192.168.122.209 [58019.729011] ss_skb_process+0x270/0x2f0 [tempesta_fw] Apr 26 08:11:09 192.168.122.209 [58019.729493] ? __resp_parse_body+0xb50/0xb50 [tempesta_fw] Apr 26 08:11:09 192.168.122.209 [58019.730018] ? tfw_sock_srv_exit+0x30/0x30 [tempesta_fw] Apr 26 08:11:09 192.168.122.209 [58019.730494] ? __alloc_pages_nodemask+0x2db/0x540 Apr 26 08:11:09 192.168.122.209 [58019.731031] tfw_http_msg_process_generic+0x282/0xc70 [tempesta_fw] Apr 26 08:11:09 192.168.122.209 [58019.731615] ? tfw_http_req_process+0x11a0/0x11a0 [tempesta_fw] Apr 26 08:11:09 192.168.122.209 [58019.732138] ? __kasan_check_write+0x14/0x20 Apr 26 08:11:09 192.168.122.209 [58019.732532] ? pg_skb_alloc+0x60e/0x680 Apr 26 08:11:09 192.168.122.209 [58019.732883] ? __kasan_check_write+0x14/0x20 Apr 26 08:11:09 192.168.122.209 [58019.733264] ? __alloc_skb+0x278/0x350 Apr 26 08:11:09 192.168.122.209 [58019.733607] ? __kasan_check_write+0x14/0x20 Apr 26 08:11:09 192.168.122.209 [58019.734017] ? __coalesce_frag+0x136/0x370 [tempesta_fw] Apr 26 08:11:09 192.168.122.209 [58019.734519] tfw_http_msg_process+0x80/0xc0 [tempesta_fw] Apr 26 08:11:09 192.168.122.209 [58019.734998] ? skb_release_data+0x8c/0x320 Apr 26 08:11:09 192.168.122.209 [58019.735395] tfw_connection_recv+0x12e/0x250 [tempesta_fw] Apr 26 08:11:09 192.168.122.209 [58019.735906] ? tfw_connection_send+0x70/0x70 [tempesta_fw] Apr 26 08:11:09 192.168.122.209 [58019.736427] ? ss_skb_unroll+0x3d6/0x540 [tempesta_fw] Apr 26 08:11:09 192.168.122.209 [58019.736911] ss_tcp_process_data+0x436/0x8b0 [tempesta_fw] Apr 26 08:11:09 192.168.122.209 [58019.737427] ? __sk_close_locked+0x100/0x100 [tempesta_fw] Apr 26 08:11:09 192.168.122.209 [58019.737924] ? mod_timer+0x10/0x20 Apr 26 08:11:09 192.168.122.209 [58019.738236] ? sk_reset_timer+0x1a/0x70 Apr 26 08:11:09 192.168.122.209 [58019.738613] ss_tcp_data_ready+0x7b/0x150 [tempesta_fw] Apr 26 08:11:09 192.168.122.209 [58019.739086] tcp_data_ready+0x73/0x210 Apr 26 08:11:09 192.168.122.209 [58019.739435] tcp_rcv_established+0x95b/0xb40 Apr 26 08:11:09 192.168.122.209 [58019.739825] ? tcp_data_queue+0x1d80/0x1d80 Apr 26 08:11:09 192.168.122.209 [58019.740201] ? __kasan_check_read+0x11/0x20 Apr 26 08:11:09 192.168.122.209 [58019.740585] tcp_v4_do_rcv+0x25f/0x360 Apr 26 08:11:09 192.168.122.209 [58019.740925] tcp_v4_rcv+0x1600/0x1770 Apr 26 08:11:09 192.168.122.209 [58019.741260] ? tcp_v4_early_demux+0x2f0/0x2f0 Apr 26 08:11:09 192.168.122.209 [58019.741667] ip_protocol_deliver_rcu+0x46/0x2e0 Apr 26 08:11:09 192.168.122.209 [58019.742076] ip_local_deliver_finish+0xc6/0xe0 Apr 26 08:11:09 192.168.122.209 [58019.742480] ip_local_deliver+0x1f5/0x210 Apr 26 08:11:09 192.168.122.209 [58019.742848] ? ip_local_deliver_finish+0xe0/0xe0 Apr 26 08:11:09 192.168.122.209 [58019.743269] ? nf_nat_inet_fn+0x2b3/0x440 [nf_nat] Apr 26 08:11:09 192.168.122.209 [58019.743715] ? ip_protocol_deliver_rcu+0x2e0/0x2e0 Apr 26 08:11:09 192.168.122.209 [58019.744141] ? ip_rcv_finish_core.constprop.0+0x17c/0x890 Apr 26 08:11:09 192.168.122.209 [58019.744628] ip_rcv_finish+0xcf/0xf0 Apr 26 08:11:09 192.168.122.209 [58019.744953] ip_rcv+0x16d/0x180 Apr 26 08:11:09 192.168.122.209 [58019.745245] ? ip_local_deliver+0x210/0x210 Apr 26 08:11:09 192.168.122.209 [58019.745628] ? ip_rcv_finish_core.constprop.0+0x890/0x890 Apr 26 08:11:09 192.168.122.209 [58019.746121] ? update_load_avg+0x132/0xa70 Apr 26 08:11:09 192.168.122.209 [58019.746500] ? sched_clock+0x9/0x10 Apr 26 08:11:09 192.168.122.209 [58019.746818] ? sched_clock_cpu+0x1b/0x110 Apr 26 08:11:09 192.168.122.209 [58019.747179] ? ip_local_deliver+0x210/0x210 Apr 26 08:11:09 192.168.122.209 [58019.747564] __netif_receive_skb_one_core+0x132/0x140 Apr 26 08:11:09 192.168.122.209 [58019.748016] ? napi_gro_receive+0x260/0x260 Apr 26 08:11:09 192.168.122.209 [58019.748395] ? __kasan_check_write+0x14/0x20 Apr 26 08:11:09 192.168.122.209 [58019.748797] ? _raw_spin_lock+0x7b/0xd0 Apr 26 08:11:09 192.168.122.209 [58019.749151] __netif_receive_skb+0x26/0xb0 Apr 26 08:11:09 192.168.122.209 [58019.749527] ? generic_exec_single+0xb1/0x170 Apr 26 08:11:09 192.168.122.209 [58019.749918] process_backlog+0xfe/0x290 Apr 26 08:11:09 192.168.122.209 [58019.750263] net_rx_action+0x287/0x6b0 Apr 26 08:11:09 192.168.122.209 [58019.750613] ? try_to_wake_up+0x41e/0xa70 Apr 26 08:11:09 192.168.122.209 [58019.750978] ? napi_complete_done+0x2c0/0x2c0 Apr 26 08:11:09 192.168.122.209 [58019.751381] ? switch_fpu_return+0x120/0x120 Apr 26 08:11:09 192.168.122.209 [58019.751765] __do_softirq+0xfe/0x383 Apr 26 08:11:09 192.168.122.209 [58019.752097] asm_call_irq_on_stack+0xf/0x20 Apr 26 08:11:09 192.168.122.209 [58019.752475] Apr 26 08:11:09 192.168.122.209 [58019.752674] do_softirq_own_stack+0x3d/0x50 Apr 26 08:11:09 192.168.122.209 [58019.753053] irq_exit_rcu+0xc7/0x120 Apr 26 08:11:09 192.168.122.209 [58019.753392] sysvec_call_function_single+0x3a/0x90 Apr 26 08:11:09 192.168.122.209 [58019.753818] asm_sysvec_call_function_single+0x12/0x20 Apr 26 08:11:09 192.168.122.209 [58019.754277] RIP: 0010:native_safe_halt+0xe/0x10 Apr 26 08:11:09 192.168.122.209 [58019.754689] Code: 49 8b 04 24 a8 08 0f 85 71 ff ff ff e9 0f ff ff ff cc cc cc cc cc cc cc cc cc cc cc e9 07 00 00 00 0f 00 2d d4 62 51 00 fb f4 90 e9 07 00 00 00 0f 00 2d c4 62 51 00 f4 c3 cc cc 0f 1f 44 00 Apr 26 08:11:09 192.168.122.209 [58019.756317] RSP: 0018:ffff888100f37db8 EFLAGS: 00000206 Apr 26 08:11:09 192.168.122.209 [58019.756786] RAX: ffffffffb63426a0 RBX: ffff888100f2c0c0 RCX: ffffffffb632c475 Apr 26 08:11:09 192.168.122.209 [58019.757413] RDX: 00000000185d3812 RSI: 0000000000000004 RDI: ffff888147eb5040 Apr 26 08:11:09 192.168.122.209 [58019.758033] RBP: ffff888100f37dc0 R08: 0000000000000001 R09: ffff888147eb5043 Apr 26 08:11:09 192.168.122.209 [58019.758663] R10: ffffed1028fd6a08 R11: 0000000000000001 R12: 0000000000000001 Apr 26 08:11:09 192.168.122.209 [58019.759286] R13: ffffffffb7ae9360 R14: 0000000000000000 R15: 0000000000000000 Apr 26 08:11:09 192.168.122.209 [58019.759917] ? __cpuidle_text_start+0x8/0x8 Apr 26 08:11:09 192.168.122.209 [58019.760289] ? rcu_eqs_enter.constprop.0+0x85/0xa0 Apr 26 08:11:09 192.168.122.209 [58019.760727] ? default_idle+0xe/0x20 Apr 26 08:11:09 192.168.122.209 [58019.761053] arch_cpu_idle+0x15/0x20 Apr 26 08:11:09 192.168.122.209 [58019.761379] default_idle_call+0x66/0x160 Apr 26 08:11:09 192.168.122.209 [58019.761739] do_idle+0x36f/0x430 Apr 26 08:11:09 192.168.122.209 [58019.762036] ? arch_cpu_idle_exit+0x40/0x40 Apr 26 08:11:09 192.168.122.209 [58019.762416] cpu_startup_entry+0x20/0x30 Apr 26 08:11:09 192.168.122.209 [58019.762774] start_secondary+0x1c1/0x210 Apr 26 08:11:09 192.168.122.209 [58019.763124] ? set_cpu_sibling_map+0xd70/0xd70 Apr 26 08:11:09 192.168.122.209 [58019.763533] ? set_bringup_idt_handler.constprop.0+0x84/0x90 Apr 26 08:11:09 192.168.122.209 [58019.764032] ? start_cpu0+0xc/0xc Apr 26 08:11:09 192.168.122.209 [58019.764339] secondary_startup_64_no_verify+0xb0/0xbb Apr 26 08:11:09 192.168.122.209 [58019.764810] Mem-Info: Apr 26 08:11:09 192.168.122.209 [58019.765038] active_anon:33182 inactive_anon:97071 isolated_anon:0 [58019.765038] active_file:97924 inactive_file:97763 isolated_file:0 [58019.765038] unevictable:6821 dirty:71 writeback:0 [58019.765038] slab_reclaimable:24126 slab_unreclaimable:99056 [58019.765038] mapped:36758 shmem:426 pagetables:1340 bounce:0 [58019.765038] free:123993 free_pcp:1752 free_cma:0 Apr 26 08:11:09 192.168.122.209 [58019.767917] Node 0 active_anon:132728kB inactive_anon:388284kB active_file:391696kB inactive_file:391052kB unevictable:27284kB isolated(anon):0kB isolated(file):0kB mapped:147032kB dirty:408kB writeback:0kB shmem:1704kB shmem_thp: 0kB shmem_pmdmapped: 0kB anon_thp: 0kB writeback_tmp:0kB kernel_stack:9632kB all_unreclaimable? no Apr 26 08:11:09 192.168.122.209 [58019.770419] Node 0 DMA free:11904kB min:408kB low:508kB high:608kB reserved_highatomic:4096KB active_anon:8kB inactive_anon:36kB active_file:4kB inactive_file:4kB unevictable:0kB writepending:0kB present:15992kB managed:15908kB mlocked:0kB pagetables:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB Apr 26 08:11:09 192.168.122.209 [58019.772749] lowmem_reserve[]: 0 1900 2534 2534 2534 Apr 26 08:11:09 192.168.122.209 [58019.773205] Node 0 DMA32 free:457540kB min:50364kB low:62952kB high:75540kB reserved_highatomic:0KB active_anon:126888kB inactive_anon:348668kB active_file:313292kB inactive_file:361612kB unevictable:0kB writepending:80kB present:2080624kB managed:1946020kB mlocked:0kB pagetables:668kB bounce:0kB free_pcp:4408kB local_pcp:1424kB free_cma:0kB Apr 26 08:11:09 192.168.122.209 [58019.775805] lowmem_reserve[]: 0 0 634 634 634 Apr 26 08:11:09 192.168.122.209 [58019.776209] Node 0 Normal free:26528kB min:16804kB low:21004kB high:25204kB reserved_highatomic:2048KB active_anon:5856kB inactive_anon:39972kB active_file:78856kB inactive_file:29592kB unevictable:27284kB writepending:204kB present:2097152kB managed:649288kB mlocked:27284kB pagetables:4692kB bounce:0kB free_pcp:2572kB local_pcp:472kB free_cma:0kB Apr 26 08:11:09 192.168.122.209 [58019.778887] lowmem_reserve[]: 0 0 0 0 0 Apr 26 08:11:09 192.168.122.209 [58019.779253] Node 0 DMA: 14*4kB (MH) 21*8kB (ME) 22*16kB (MEH) 18*32kB (MEH) 16*64kB (MEH) 10*128kB (MEH) 5*256kB (MEH) 4*512kB (MH) 3*1024kB (ME) 1*2048kB (U) 0*4096kB = 11904kB Apr 26 08:11:09 192.168.122.209 [58019.780683] Node 0 DMA32: 365*4kB (UME) 1967*8kB (UME) 7408*16kB (UME) 3929*32kB (UME) 2371*64kB (UME) 286*128kB (UME) 32*256kB (UE) 0*512kB 0*1024kB 0*2048kB 0*4096kB = 457996kB Apr 26 08:11:09 192.168.122.209 [58019.782103] Node 0 Normal: 1541*4kB (UMEH) 250*8kB (MEH) 360*16kB (UMEH) 338*32kB (UMEH) 25*64kB (U) 1*128kB (U) 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 26468kB Apr 26 08:11:09 192.168.122.209 [58019.783512] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=1048576kB Apr 26 08:11:09 192.168.122.209 [58019.784297] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=2048kB Apr 26 08:11:09 192.168.122.209 [58019.785041] 256366 total pagecache pages Apr 26 08:11:09 192.168.122.209 [58019.785411] 58055 pages in swap cache Apr 26 08:11:09 192.168.122.209 [58019.785747] Swap cache stats: add 297166, delete 239113, find 371601/422442 Apr 26 08:11:09 192.168.122.209 [58019.786371] Free swap = 3756760kB Apr 26 08:11:09 192.168.122.209 [58019.786684] Total swap = 4194300kB Apr 26 08:11:09 192.168.122.209 [58019.787000] 1048442 pages RAM Apr 26 08:11:09 192.168.122.209 [58019.787280] 0 pages HighMem/MovableOnly Apr 26 08:11:09 192.168.122.209 [58019.787642] 395638 pages reserved Apr 26 08:11:09 192.168.122.209 [58019.787948] 0 pages cma reserved Apr 26 08:11:09 192.168.122.209 [58019.788247] 0 pages hwpoisoned Apr 26 08:11:09 192.168.122.209 [58019.788546] [tempesta fw] Warning: Cannot grow HTTP data string Apr 26 08:11:09 192.168.122.209 [58019.820798] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 08:11:09 192.168.122.209 [58020.380865] [tdb] Close table 'client0.tdb' Apr 26 08:11:10 192.168.122.209 [58020.572210] [tdb] Close table 'sessions0.tdb' Apr 26 08:11:13 192.168.122.209 [58023.810096] [tdb] Close table 'cache0.tdb' Apr 26 08:11:13 192.168.122.209 [58024.058828] [tdb] Close table 'filter0.tdb' Apr 26 08:11:13 192.168.122.209 [58024.059256] [tempesta fw] modules are stopped Apr 26 08:11:13 192.168.122.209 [58024.322868] [tempesta fw] exiting... Apr 26 08:11:13 192.168.122.209 [58024.479970] [tdb] Shutdown Tempesta DB Apr 26 08:11:14 192.168.122.209 [58024.708311] End test: http2_general.test_h2_frame.TestH2FrameEnabledDisabledTsoGroGso.test_data_frame Apr 26 08:11:14 192.168.122.209 [58024.725675] Start test: http2_general.test_h2_frame.TestH2FrameEnabledDisabledTsoGroGso.test_headers_frame_for_local_resp_invalid_req_d Apr 26 08:11:15 192.168.122.209 [58025.863343] [tdb] Start Tempesta DB Apr 26 08:11:15 192.168.122.209 [58026.000535] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:11:17 192.168.122.209 [58027.700354] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58027.700354] Maybe that's fine, but it's worth checking the [58027.700354] config - if there is no relations between the [58027.700354] names, then host name confusion attack is possible. Apr 26 08:11:17 192.168.122.209 [58027.874931] [tempesta fw] Configuration processing is completed. Apr 26 08:11:17 192.168.122.209 [58027.928144] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:11:17 192.168.122.209 [58028.355568] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:11:17 192.168.122.209 [58028.382290] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:11:17 192.168.122.209 [58028.410104] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:11:17 192.168.122.209 [58028.450907] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:11:17 192.168.122.209 [58028.490853] [tempesta fw] Tempesta FW is ready Apr 26 08:11:18 192.168.122.209 [58028.900119] [tempesta fw] Warning: request has been filtered out via http table: 127.0.0.2 Apr 26 08:11:18 192.168.122.209 [58029.431714] [tdb] Close table 'client0.tdb' Apr 26 08:11:19 192.168.122.209 [58029.634767] [tdb] Close table 'sessions0.tdb' Apr 26 08:11:22 192.168.122.209 [58032.795096] [tdb] Close table 'cache0.tdb' Apr 26 08:11:22 192.168.122.209 [58033.047054] [tdb] Close table 'filter0.tdb' Apr 26 08:11:22 192.168.122.209 [58033.047494] [tempesta fw] modules are stopped Apr 26 08:11:22 192.168.122.209 [58033.266920] [tempesta fw] exiting... Apr 26 08:11:22 192.168.122.209 [58033.395746] [tdb] Shutdown Tempesta DB Apr 26 08:11:23 192.168.122.209 [58033.612312] End test: http2_general.test_h2_frame.TestH2FrameEnabledDisabledTsoGroGso.test_headers_frame_for_local_resp_invalid_req_d Apr 26 08:11:23 192.168.122.209 [58033.625004] Start test: http2_general.test_h2_frame.TestH2FrameEnabledDisabledTsoGroGso.test_headers_frame_for_local_resp_invalid_req_e Apr 26 08:11:24 192.168.122.209 [58034.693211] [tdb] Start Tempesta DB Apr 26 08:11:24 192.168.122.209 [58034.854644] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:11:26 192.168.122.209 [58036.536494] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58036.536494] Maybe that's fine, but it's worth checking the [58036.536494] config - if there is no relations between the [58036.536494] names, then host name confusion attack is possible. Apr 26 08:11:26 192.168.122.209 [58036.691067] [tempesta fw] Configuration processing is completed. Apr 26 08:11:26 192.168.122.209 [58036.749479] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:11:26 192.168.122.209 [58037.168527] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:11:26 192.168.122.209 [58037.195040] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:11:26 192.168.122.209 [58037.231284] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:11:26 192.168.122.209 [58037.290974] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:11:26 192.168.122.209 [58037.342993] [tempesta fw] Tempesta FW is ready Apr 26 08:11:27 192.168.122.209 [58037.753614] [tempesta fw] Warning: request has been filtered out via http table: 127.0.0.2 Apr 26 08:11:27 192.168.122.209 [58038.254947] [tdb] Close table 'client0.tdb' Apr 26 08:11:27 192.168.122.209 [58038.469520] [tdb] Close table 'sessions0.tdb' Apr 26 08:11:31 192.168.122.209 [58041.619741] [tdb] Close table 'cache0.tdb' Apr 26 08:11:31 192.168.122.209 [58041.883766] [tdb] Close table 'filter0.tdb' Apr 26 08:11:31 192.168.122.209 [58041.884164] [tempesta fw] modules are stopped Apr 26 08:11:31 192.168.122.209 [58042.084964] [tempesta fw] exiting... Apr 26 08:11:31 192.168.122.209 [58042.187005] [tdb] Shutdown Tempesta DB Apr 26 08:11:31 192.168.122.209 [58042.378421] End test: http2_general.test_h2_frame.TestH2FrameEnabledDisabledTsoGroGso.test_headers_frame_for_local_resp_invalid_req_e Apr 26 08:11:31 192.168.122.209 [58042.400792] Start test: http2_general.test_h2_frame.TestH2FrameEnabledDisabledTsoGroGso.test_headers_frame_with_continuation Apr 26 08:11:32 192.168.122.209 [58043.480570] [tdb] Start Tempesta DB Apr 26 08:11:33 192.168.122.209 [58043.618269] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:11:34 192.168.122.209 [58045.224555] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58045.224555] Maybe that's fine, but it's worth checking the [58045.224555] config - if there is no relations between the [58045.224555] names, then host name confusion attack is possible. Apr 26 08:11:34 192.168.122.209 [58045.387125] [tempesta fw] Configuration processing is completed. Apr 26 08:11:34 192.168.122.209 [58045.436094] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:11:35 192.168.122.209 [58045.850233] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:11:35 192.168.122.209 [58045.878419] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:11:35 192.168.122.209 [58045.905987] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:11:35 192.168.122.209 [58045.955146] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:11:35 192.168.122.209 [58046.003089] [tempesta fw] Tempesta FW is ready Apr 26 08:11:40 192.168.122.209 [58051.083820] swapper/0: page allocation failure: order:9, mode:0x40a20(GFP_ATOMIC|__GFP_COMP), nodemask=(null),cpuset=/,mems_allowed=0-1023 Apr 26 08:11:40 192.168.122.209 [58051.084996] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G OE 5.10.35.tfw-39c65d3-debug #1 Apr 26 08:11:40 192.168.122.209 [58051.085797] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 Apr 26 08:11:40 192.168.122.209 [58051.086719] Call Trace: Apr 26 08:11:40 192.168.122.209 [58051.086951] Apr 26 08:11:40 192.168.122.209 [58051.087152] dump_stack+0x96/0xc4 Apr 26 08:11:40 192.168.122.209 [58051.087458] warn_alloc.cold+0x87/0x12a Apr 26 08:11:40 192.168.122.209 [58051.087816] ? zone_watermark_ok_safe+0x140/0x140 Apr 26 08:11:40 192.168.122.209 [58051.088243] ? __kasan_check_read+0x11/0x20 Apr 26 08:11:40 192.168.122.209 [58051.088756] ? wakeup_kswapd+0xba/0x290 Apr 26 08:11:40 192.168.122.209 [58051.089107] ? __zone_watermark_ok+0x270/0x270 Apr 26 08:11:40 192.168.122.209 [58051.089510] ? wake_all_kswapds+0xf4/0x140 Apr 26 08:11:40 192.168.122.209 [58051.089890] ? __alloc_pages_slowpath.constprop.0+0x11f4/0x1390 Apr 26 08:11:40 192.168.122.209 [58051.090424] __alloc_pages_slowpath.constprop.0+0x1359/0x1390 Apr 26 08:11:40 192.168.122.209 [58051.090941] ? netif_rx_internal+0x1c8/0x1f0 Apr 26 08:11:40 192.168.122.209 [58051.091329] ? warn_alloc+0x120/0x120 Apr 26 08:11:40 192.168.122.209 [58051.091664] ? eth_type_trans+0x195/0x2f0 Apr 26 08:11:40 192.168.122.209 [58051.092035] ? eth_get_headlen+0x140/0x140 Apr 26 08:11:40 192.168.122.209 [58051.092406] ? __zone_watermark_ok+0x270/0x270 Apr 26 08:11:40 192.168.122.209 [58051.092810] ? netif_rx+0x1c/0xf0 Apr 26 08:11:40 192.168.122.209 [58051.093114] __alloc_pages_nodemask+0x509/0x540 Apr 26 08:11:40 192.168.122.209 [58051.093525] ? __alloc_pages_slowpath.constprop.0+0x1390/0x1390 Apr 26 08:11:40 192.168.122.209 [58051.094057] alloc_pages_current+0x96/0x140 Apr 26 08:11:40 192.168.122.209 [58051.094435] __get_free_pages+0x12/0x60 Apr 26 08:11:40 192.168.122.209 [58051.094824] tfw_pool_alloc_pages+0x9b/0xc0 [tempesta_fw] Apr 26 08:11:40 192.168.122.209 [58051.095340] __tfw_pool_realloc+0x123/0x1a0 [tempesta_fw] Apr 26 08:11:40 192.168.122.209 [58051.095915] __str_grow_tree+0x89/0x210 [tempesta_fw] Apr 26 08:11:40 192.168.122.209 [58051.096438] tfw_str_add_compound+0x33/0x40 [tempesta_fw] Apr 26 08:11:40 192.168.122.209 [58051.096952] __tfw_http_msg_add_str_data+0x88/0x1c0 [tempesta_fw] Apr 26 08:11:40 192.168.122.209 [58051.097527] tfw_http_parse_resp+0x11376/0x197d0 [tempesta_fw] Apr 26 08:11:40 192.168.122.209 [58051.098074] ? __resp_parse_body+0xb50/0xb50 [tempesta_fw] Apr 26 08:11:40 192.168.122.209 [58051.098589] ss_skb_process+0x270/0x2f0 [tempesta_fw] Apr 26 08:11:40 192.168.122.209 [58051.099070] ? __resp_parse_body+0xb50/0xb50 [tempesta_fw] Apr 26 08:11:40 192.168.122.209 [58051.099590] ? tfw_sock_srv_exit+0x30/0x30 [tempesta_fw] Apr 26 08:11:40 192.168.122.209 [58051.100163] ? __ip_finish_output+0x340/0x340 Apr 26 08:11:40 192.168.122.209 [58051.100579] tfw_http_msg_process_generic+0x282/0xc70 [tempesta_fw] Apr 26 08:11:40 192.168.122.209 [58051.101213] ? tfw_http_req_process+0x11a0/0x11a0 [tempesta_fw] Apr 26 08:11:40 192.168.122.209 [58051.101768] ? pg_skb_alloc+0x60e/0x680 Apr 26 08:11:40 192.168.122.209 [58051.102129] ? __kasan_check_write+0x14/0x20 Apr 26 08:11:40 192.168.122.209 [58051.102522] ? __alloc_skb+0x278/0x350 Apr 26 08:11:40 192.168.122.209 [58051.102874] ? __kasan_check_write+0x14/0x20 Apr 26 08:11:40 192.168.122.209 [58051.103304] ? __coalesce_frag+0x136/0x370 [tempesta_fw] Apr 26 08:11:40 192.168.122.209 [58051.103805] tfw_http_msg_process+0x80/0xc0 [tempesta_fw] Apr 26 08:11:40 192.168.122.209 [58051.104284] ? skb_release_data+0x8c/0x320 Apr 26 08:11:40 192.168.122.209 [58051.104677] tfw_connection_recv+0x12e/0x250 [tempesta_fw] Apr 26 08:11:40 192.168.122.209 [58051.105194] ? tfw_connection_send+0x70/0x70 [tempesta_fw] Apr 26 08:11:40 192.168.122.209 [58051.105715] ? ss_skb_unroll+0x3d6/0x540 [tempesta_fw] Apr 26 08:11:40 192.168.122.209 [58051.106205] ss_tcp_process_data+0x436/0x8b0 [tempesta_fw] Apr 26 08:11:40 192.168.122.209 [58051.106727] ? __sk_close_locked+0x100/0x100 [tempesta_fw] Apr 26 08:11:40 192.168.122.209 [58051.107223] ? mod_timer+0x10/0x20 Apr 26 08:11:40 192.168.122.209 [58051.107597] ? sk_reset_timer+0x1a/0x70 Apr 26 08:11:40 192.168.122.209 [58051.107988] ss_tcp_data_ready+0x7b/0x150 [tempesta_fw] Apr 26 08:11:40 192.168.122.209 [58051.108461] tcp_data_ready+0x73/0x210 Apr 26 08:11:40 192.168.122.209 [58051.108811] tcp_rcv_established+0x95b/0xb40 Apr 26 08:11:40 192.168.122.209 [58051.109198] ? tcp_data_queue+0x1d80/0x1d80 Apr 26 08:11:40 192.168.122.209 [58051.109575] ? __kasan_check_read+0x11/0x20 Apr 26 08:11:40 192.168.122.209 [58051.109957] tcp_v4_do_rcv+0x25f/0x360 Apr 26 08:11:40 192.168.122.209 [58051.110299] tcp_v4_rcv+0x1600/0x1770 Apr 26 08:11:40 192.168.122.209 [58051.110633] ? tcp_v4_early_demux+0x2f0/0x2f0 Apr 26 08:11:40 192.168.122.209 [58051.111034] ip_protocol_deliver_rcu+0x46/0x2e0 Apr 26 08:11:40 192.168.122.209 [58051.111442] ip_local_deliver_finish+0xc6/0xe0 Apr 26 08:11:40 192.168.122.209 [58051.111850] ip_local_deliver+0x1f5/0x210 Apr 26 08:11:40 192.168.122.209 [58051.112211] ? ip_local_deliver_finish+0xe0/0xe0 Apr 26 08:11:40 192.168.122.209 [58051.112626] ? nf_nat_inet_fn+0x2b3/0x440 [nf_nat] Apr 26 08:11:40 192.168.122.209 [58051.113057] ? ip_protocol_deliver_rcu+0x2e0/0x2e0 Apr 26 08:11:40 192.168.122.209 [58051.113488] ? ip_rcv_finish_core.constprop.0+0x17c/0x890 Apr 26 08:11:40 192.168.122.209 [58051.113975] ip_rcv_finish+0xcf/0xf0 Apr 26 08:11:40 192.168.122.209 [58051.114301] ip_rcv+0x16d/0x180 Apr 26 08:11:40 192.168.122.209 [58051.114590] ? ip_local_deliver+0x210/0x210 Apr 26 08:11:40 192.168.122.209 [58051.114982] ? ip_rcv_finish_core.constprop.0+0x890/0x890 Apr 26 08:11:40 192.168.122.209 [58051.115461] ? try_to_wake_up+0x41e/0xa70 Apr 26 08:11:40 192.168.122.209 [58051.115826] ? ip_local_deliver+0x210/0x210 Apr 26 08:11:40 192.168.122.209 [58051.116204] __netif_receive_skb_one_core+0x132/0x140 Apr 26 08:11:40 192.168.122.209 [58051.116656] ? napi_gro_receive+0x260/0x260 Apr 26 08:11:40 192.168.122.209 [58051.117046] ? __kasan_check_write+0x14/0x20 Apr 26 08:11:40 192.168.122.209 [58051.117431] ? _raw_spin_lock+0x7b/0xd0 Apr 26 08:11:40 192.168.122.209 [58051.117783] __netif_receive_skb+0x26/0xb0 Apr 26 08:11:40 192.168.122.209 [58051.118156] ? generic_exec_single+0xb1/0x170 Apr 26 08:11:40 192.168.122.209 [58051.118547] process_backlog+0xfe/0x290 Apr 26 08:11:40 192.168.122.209 [58051.118904] net_rx_action+0x287/0x6b0 Apr 26 08:11:40 192.168.122.209 [58051.119244] ? napi_complete_done+0x2c0/0x2c0 Apr 26 08:11:40 192.168.122.209 [58051.119639] ? switch_fpu_return+0x120/0x120 Apr 26 08:11:40 192.168.122.209 [58051.120028] __do_softirq+0xfe/0x383 Apr 26 08:11:40 192.168.122.209 [58051.120356] asm_call_irq_on_stack+0xf/0x20 Apr 26 08:11:40 192.168.122.209 [58051.120736] Apr 26 08:11:40 192.168.122.209 [58051.120939] do_softirq_own_stack+0x3d/0x50 Apr 26 08:11:40 192.168.122.209 [58051.121318] irq_exit_rcu+0xc7/0x120 Apr 26 08:11:40 192.168.122.209 [58051.121644] sysvec_call_function_single+0x3a/0x90 Apr 26 08:11:40 192.168.122.209 [58051.122077] asm_sysvec_call_function_single+0x12/0x20 Apr 26 08:11:40 192.168.122.209 [58051.122536] RIP: 0010:native_safe_halt+0xe/0x10 Apr 26 08:11:40 192.168.122.209 [58051.122951] Code: 49 8b 04 24 a8 08 0f 85 71 ff ff ff e9 0f ff ff ff cc cc cc cc cc cc cc cc cc cc cc e9 07 00 00 00 0f 00 2d d4 62 51 00 fb f4 90 e9 07 00 00 00 0f 00 2d c4 62 51 00 f4 c3 cc cc 0f 1f 44 00 Apr 26 08:11:40 192.168.122.209 [58051.124605] RSP: 0018:ffffffffb7207dc8 EFLAGS: 00000202 Apr 26 08:11:40 192.168.122.209 [58051.125077] RAX: ffffffffb63426a0 RBX: ffffffffb721b100 RCX: ffffffffb632c475 Apr 26 08:11:40 192.168.122.209 [58051.125715] RDX: 0000000017cb4996 RSI: 0000000000000004 RDI: ffff888147e35040 Apr 26 08:11:40 192.168.122.209 [58051.126340] RBP: ffffffffb7207dd0 R08: 0000000000000001 R09: ffff888147e35043 Apr 26 08:11:40 192.168.122.209 [58051.126966] R10: ffffed1028fc6a08 R11: 0000000000000001 R12: 0000000000000000 Apr 26 08:11:40 192.168.122.209 [58051.127591] R13: ffffffffb7ae9360 R14: 0000000000000000 R15: 0000000000000000 Apr 26 08:11:40 192.168.122.209 [58051.128225] ? __cpuidle_text_start+0x8/0x8 Apr 26 08:11:40 192.168.122.209 [58051.128601] ? rcu_eqs_enter.constprop.0+0x85/0xa0 Apr 26 08:11:40 192.168.122.209 [58051.129033] ? default_idle+0xe/0x20 Apr 26 08:11:40 192.168.122.209 [58051.129358] arch_cpu_idle+0x15/0x20 Apr 26 08:11:40 192.168.122.209 [58051.129686] default_idle_call+0x66/0x160 Apr 26 08:11:40 192.168.122.209 [58051.130051] do_idle+0x36f/0x430 Apr 26 08:11:40 192.168.122.209 [58051.130345] ? arch_cpu_idle_exit+0x40/0x40 Apr 26 08:11:40 192.168.122.209 [58051.130726] ? do_idle+0x2e/0x430 Apr 26 08:11:40 192.168.122.209 [58051.131031] cpu_startup_entry+0x20/0x30 Apr 26 08:11:40 192.168.122.209 [58051.131386] rest_init+0xc8/0xce Apr 26 08:11:40 192.168.122.209 [58051.131711] arch_call_rest_init+0xe/0x1b Apr 26 08:11:40 192.168.122.209 [58051.132075] start_kernel+0x380/0x39d Apr 26 08:11:40 192.168.122.209 [58051.132412] x86_64_start_reservations+0x24/0x26 Apr 26 08:11:40 192.168.122.209 [58051.132827] x86_64_start_kernel+0x7a/0x7e Apr 26 08:11:40 192.168.122.209 [58051.133200] secondary_startup_64_no_verify+0xb0/0xbb Apr 26 08:11:40 192.168.122.209 [58051.133672] Mem-Info: Apr 26 08:11:40 192.168.122.209 [58051.133901] active_anon:34139 inactive_anon:95974 isolated_anon:0 [58051.133901] active_file:96446 inactive_file:97775 isolated_file:0 [58051.133901] unevictable:6821 dirty:67 writeback:0 [58051.133901] slab_reclaimable:24126 slab_unreclaimable:99132 [58051.133901] mapped:36723 shmem:426 pagetables:1341 bounce:0 [58051.133901] free:124753 free_pcp:1946 free_cma:0 Apr 26 08:11:40 192.168.122.209 [58051.136788] Node 0 active_anon:136556kB inactive_anon:383896kB active_file:385784kB inactive_file:391100kB unevictable:27284kB isolated(anon):0kB isolated(file):0kB mapped:146892kB dirty:640kB writeback:0kB shmem:1704kB shmem_thp: 0kB shmem_pmdmapped: 0kB anon_thp: 0kB writeback_tmp:0kB kernel_stack:9632kB all_unreclaimable? no Apr 26 08:11:40 192.168.122.209 [58051.139316] Node 0 DMA free:11904kB min:408kB low:508kB high:608kB reserved_highatomic:4096KB active_anon:8kB inactive_anon:36kB active_file:4kB inactive_file:4kB unevictable:0kB writepending:0kB present:15992kB managed:15908kB mlocked:0kB pagetables:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB Apr 26 08:11:40 192.168.122.209 [58051.141675] lowmem_reserve[]: 0 1900 2534 2534 2534 Apr 26 08:11:40 192.168.122.209 [58051.142141] Node 0 DMA32 free:458532kB min:50364kB low:62952kB high:75540kB reserved_highatomic:0KB active_anon:130352kB inactive_anon:343996kB active_file:309068kB inactive_file:362692kB unevictable:0kB writepending:72kB present:2080624kB managed:1946020kB mlocked:0kB pagetables:672kB bounce:0kB free_pcp:5392kB local_pcp:1452kB free_cma:0kB Apr 26 08:11:40 192.168.122.209 [58051.144763] lowmem_reserve[]: 0 0 634 634 634 Apr 26 08:11:40 192.168.122.209 [58051.145177] Node 0 Normal free:28028kB min:16804kB low:21004kB high:25204kB reserved_highatomic:2048KB active_anon:5864kB inactive_anon:40080kB active_file:76752kB inactive_file:28224kB unevictable:27284kB writepending:948kB present:2097152kB managed:649288kB mlocked:27284kB pagetables:4692kB bounce:0kB free_pcp:2364kB local_pcp:544kB free_cma:0kB Apr 26 08:11:40 192.168.122.209 [58051.147828] lowmem_reserve[]: 0 0 0 0 0 Apr 26 08:11:40 192.168.122.209 [58051.148193] Node 0 DMA: 14*4kB (MH) 21*8kB (ME) 22*16kB (MEH) 18*32kB (MEH) 16*64kB (MEH) 10*128kB (MEH) 5*256kB (MEH) 4*512kB (MH) 3*1024kB (ME) 1*2048kB (U) 0*4096kB = 11904kB Apr 26 08:11:40 192.168.122.209 [58051.149629] Node 0 DMA32: 388*4kB (UME) 1935*8kB (UME) 7469*16kB (UME) 3938*32kB (UME) 2373*64kB (UME) 286*128kB (UME) 32*256kB (UE) 0*512kB 0*1024kB 0*2048kB 0*4096kB = 459224kB Apr 26 08:11:40 192.168.122.209 [58051.151078] Node 0 Normal: 2340*4kB (UMEH) 260*8kB (MEH) 265*16kB (UMEH) 337*32kB (UMEH) 25*64kB (U) 1*128kB (U) 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 28192kB Apr 26 08:11:40 192.168.122.209 [58051.152431] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=1048576kB Apr 26 08:11:40 192.168.122.209 [58051.153227] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=2048kB Apr 26 08:11:40 192.168.122.209 [58051.153974] 255009 total pagecache pages Apr 26 08:11:40 192.168.122.209 [58051.154332] 58176 pages in swap cache Apr 26 08:11:40 192.168.122.209 [58051.154666] Swap cache stats: add 297461, delete 239287, find 371730/422571 Apr 26 08:11:40 192.168.122.209 [58051.155289] Free swap = 3755480kB Apr 26 08:11:40 192.168.122.209 [58051.155599] Total swap = 4194300kB Apr 26 08:11:40 192.168.122.209 [58051.155916] 1048442 pages RAM Apr 26 08:11:40 192.168.122.209 [58051.156190] 0 pages HighMem/MovableOnly Apr 26 08:11:40 192.168.122.209 [58051.156542] 395638 pages reserved Apr 26 08:11:40 192.168.122.209 [58051.156847] 0 pages cma reserved Apr 26 08:11:40 192.168.122.209 [58051.157143] 0 pages hwpoisoned Apr 26 08:11:40 192.168.122.209 [58051.157426] [tempesta fw] Warning: Cannot grow HTTP data string Apr 26 08:11:40 192.168.122.209 [58051.189276] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 08:11:41 192.168.122.209 [58051.755170] [tdb] Close table 'client0.tdb' Apr 26 08:11:41 192.168.122.209 [58051.946351] [tdb] Close table 'sessions0.tdb' Apr 26 08:11:44 192.168.122.209 [58055.106307] [tdb] Close table 'cache0.tdb' Apr 26 08:11:44 192.168.122.209 [58055.341017] [tdb] Close table 'filter0.tdb' Apr 26 08:11:44 192.168.122.209 [58055.341451] [tempesta fw] modules are stopped Apr 26 08:11:45 192.168.122.209 [58055.573945] [tempesta fw] exiting... Apr 26 08:11:45 192.168.122.209 [58055.713286] [tdb] Shutdown Tempesta DB Apr 26 08:11:45 192.168.122.209 [58055.958163] End test: http2_general.test_h2_frame.TestH2FrameEnabledDisabledTsoGroGso.test_headers_frame_with_continuation Apr 26 08:11:45 192.168.122.209 [58055.968659] Start test: http2_general.test_h2_frame.TestH2FrameEnabledDisabledTsoGroGso.test_headers_frame_without_continuation Apr 26 08:11:46 192.168.122.209 [58057.024489] [tdb] Start Tempesta DB Apr 26 08:11:46 192.168.122.209 [58057.156375] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:11:48 192.168.122.209 [58058.780721] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58058.780721] Maybe that's fine, but it's worth checking the [58058.780721] config - if there is no relations between the [58058.780721] names, then host name confusion attack is possible. Apr 26 08:11:48 192.168.122.209 [58058.927267] [tempesta fw] Configuration processing is completed. Apr 26 08:11:48 192.168.122.209 [58058.977598] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:11:48 192.168.122.209 [58059.396424] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:11:48 192.168.122.209 [58059.423734] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:11:48 192.168.122.209 [58059.450480] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:11:48 192.168.122.209 [58059.499287] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:11:49 192.168.122.209 [58059.543245] [tempesta fw] Tempesta FW is ready Apr 26 08:11:50 192.168.122.209 [58061.141497] [tdb] Close table 'client0.tdb' Apr 26 08:11:50 192.168.122.209 [58061.331632] [tdb] Close table 'sessions0.tdb' Apr 26 08:11:53 192.168.122.209 [58064.478204] [tdb] Close table 'cache0.tdb' Apr 26 08:11:54 192.168.122.209 [58064.719772] [tdb] Close table 'filter0.tdb' Apr 26 08:11:54 192.168.122.209 [58064.720202] [tempesta fw] modules are stopped Apr 26 08:11:54 192.168.122.209 [58064.969488] [tempesta fw] exiting... Apr 26 08:11:54 192.168.122.209 [58065.130343] [tdb] Shutdown Tempesta DB Apr 26 08:11:54 192.168.122.209 [58065.358163] End test: http2_general.test_h2_frame.TestH2FrameEnabledDisabledTsoGroGso.test_headers_frame_without_continuation Apr 26 08:11:54 192.168.122.209 [58065.377483] Start test: http2_general.test_h2_frame.TestH2FrameEnabledDisabledTsoGroGso.test_mixed_frames_long_headers_disabled Apr 26 08:11:55 192.168.122.209 [58066.404191] [tdb] Start Tempesta DB Apr 26 08:11:56 192.168.122.209 [58066.539865] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:11:57 192.168.122.209 [58068.156827] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58068.156827] Maybe that's fine, but it's worth checking the [58068.156827] config - if there is no relations between the [58068.156827] names, then host name confusion attack is possible. Apr 26 08:11:57 192.168.122.209 [58068.327438] [tempesta fw] Configuration processing is completed. Apr 26 08:11:57 192.168.122.209 [58068.378292] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:11:58 192.168.122.209 [58068.798383] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:11:58 192.168.122.209 [58068.826056] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:11:58 192.168.122.209 [58068.853721] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:11:58 192.168.122.209 [58068.907428] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:11:58 192.168.122.209 [58068.947319] [tempesta fw] Tempesta FW is ready Apr 26 08:12:02 192.168.122.209 [58072.855526] swapper/1: page allocation failure: order:8, mode:0x40a20(GFP_ATOMIC|__GFP_COMP), nodemask=(null),cpuset=/,mems_allowed=0 Apr 26 08:12:02 192.168.122.209 [58072.856668] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G OE 5.10.35.tfw-39c65d3-debug #1 Apr 26 08:12:02 192.168.122.209 [58072.857466] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 Apr 26 08:12:02 192.168.122.209 [58072.858288] Call Trace: Apr 26 08:12:02 192.168.122.209 [58072.858522] Apr 26 08:12:02 192.168.122.209 [58072.858720] dump_stack+0x96/0xc4 Apr 26 08:12:02 192.168.122.209 [58072.859029] warn_alloc.cold+0x87/0x12a Apr 26 08:12:02 192.168.122.209 [58072.859379] ? zone_watermark_ok_safe+0x140/0x140 Apr 26 08:12:02 192.168.122.209 [58072.859806] ? __kasan_check_read+0x11/0x20 Apr 26 08:12:02 192.168.122.209 [58072.860189] ? wakeup_kswapd+0xba/0x290 Apr 26 08:12:02 192.168.122.209 [58072.860533] ? __zone_watermark_ok+0x270/0x270 Apr 26 08:12:02 192.168.122.209 [58072.860934] ? wake_all_kswapds+0xf4/0x140 Apr 26 08:12:02 192.168.122.209 [58072.861311] ? __alloc_pages_slowpath.constprop.0+0x11f4/0x1390 Apr 26 08:12:02 192.168.122.209 [58072.861836] __alloc_pages_slowpath.constprop.0+0x1359/0x1390 Apr 26 08:12:02 192.168.122.209 [58072.862350] ? warn_alloc+0x120/0x120 Apr 26 08:12:02 192.168.122.209 [58072.862683] ? __cpa_process_fault+0x800/0x800 Apr 26 08:12:02 192.168.122.209 [58072.863091] ? eth_get_headlen+0x140/0x140 Apr 26 08:12:02 192.168.122.209 [58072.863460] ? __zone_watermark_ok+0x270/0x270 Apr 26 08:12:02 192.168.122.209 [58072.863862] ? netif_rx+0x1c/0xf0 Apr 26 08:12:02 192.168.122.209 [58072.864168] __alloc_pages_nodemask+0x509/0x540 Apr 26 08:12:02 192.168.122.209 [58072.864581] ? __alloc_pages_slowpath.constprop.0+0x1390/0x1390 Apr 26 08:12:02 192.168.122.209 [58072.865107] ? __kernel_map_pages+0x108/0x180 Apr 26 08:12:02 192.168.122.209 [58072.865499] ? set_direct_map_default_noflush+0x130/0x130 Apr 26 08:12:02 192.168.122.209 [58072.865983] alloc_pages_current+0x96/0x140 Apr 26 08:12:02 192.168.122.209 [58072.866366] __get_free_pages+0x12/0x60 Apr 26 08:12:02 192.168.122.209 [58072.866749] tfw_pool_alloc_pages+0x9b/0xc0 [tempesta_fw] Apr 26 08:12:02 192.168.122.209 [58072.867258] __tfw_pool_realloc+0x123/0x1a0 [tempesta_fw] Apr 26 08:12:02 192.168.122.209 [58072.867764] __str_grow_tree+0x89/0x210 [tempesta_fw] Apr 26 08:12:02 192.168.122.209 [58072.868252] tfw_str_add_compound+0x33/0x40 [tempesta_fw] Apr 26 08:12:02 192.168.122.209 [58072.868756] __tfw_http_msg_add_str_data+0x88/0x1c0 [tempesta_fw] Apr 26 08:12:02 192.168.122.209 [58072.869325] tfw_http_parse_resp+0x11376/0x197d0 [tempesta_fw] Apr 26 08:12:02 192.168.122.209 [58072.869866] ? __resp_parse_body+0xb50/0xb50 [tempesta_fw] Apr 26 08:12:02 192.168.122.209 [58072.870388] ss_skb_process+0x270/0x2f0 [tempesta_fw] Apr 26 08:12:02 192.168.122.209 [58072.870859] ? __resp_parse_body+0xb50/0xb50 [tempesta_fw] Apr 26 08:12:02 192.168.122.209 [58072.871378] ? tfw_sock_srv_exit+0x30/0x30 [tempesta_fw] Apr 26 08:12:02 192.168.122.209 [58072.871847] ? __alloc_pages_nodemask+0x2db/0x540 Apr 26 08:12:02 192.168.122.209 [58072.872299] tfw_http_msg_process_generic+0x282/0xc70 [tempesta_fw] Apr 26 08:12:02 192.168.122.209 [58072.872875] ? tfw_http_req_process+0x11a0/0x11a0 [tempesta_fw] Apr 26 08:12:02 192.168.122.209 [58072.873401] ? __kasan_check_write+0x14/0x20 Apr 26 08:12:02 192.168.122.209 [58072.873784] ? pg_skb_alloc+0x60e/0x680 Apr 26 08:12:02 192.168.122.209 [58072.874137] ? __kasan_check_write+0x14/0x20 Apr 26 08:12:02 192.168.122.209 [58072.874517] ? __alloc_skb+0x278/0x350 Apr 26 08:12:02 192.168.122.209 [58072.874856] ? __kasan_check_write+0x14/0x20 Apr 26 08:12:02 192.168.122.209 [58072.875274] ? __coalesce_frag+0x136/0x370 [tempesta_fw] Apr 26 08:12:02 192.168.122.209 [58072.875777] tfw_http_msg_process+0x80/0xc0 [tempesta_fw] Apr 26 08:12:02 192.168.122.209 [58072.876263] ? skb_release_data+0x8c/0x320 Apr 26 08:12:02 192.168.122.209 [58072.876654] tfw_connection_recv+0x12e/0x250 [tempesta_fw] Apr 26 08:12:02 192.168.122.209 [58072.877169] ? tfw_connection_send+0x70/0x70 [tempesta_fw] Apr 26 08:12:02 192.168.122.209 [58072.877691] ? ss_skb_unroll+0x3d6/0x540 [tempesta_fw] Apr 26 08:12:02 192.168.122.209 [58072.878183] ss_tcp_process_data+0x436/0x8b0 [tempesta_fw] Apr 26 08:12:02 192.168.122.209 [58072.878697] ? __sk_close_locked+0x100/0x100 [tempesta_fw] Apr 26 08:12:02 192.168.122.209 [58072.879189] ? mod_timer+0x10/0x20 Apr 26 08:12:02 192.168.122.209 [58072.879500] ? sk_reset_timer+0x1a/0x70 Apr 26 08:12:02 192.168.122.209 [58072.879871] ss_tcp_data_ready+0x7b/0x150 [tempesta_fw] Apr 26 08:12:02 192.168.122.209 [58072.880339] tcp_data_ready+0x73/0x210 Apr 26 08:12:02 192.168.122.209 [58072.880677] tcp_rcv_established+0x95b/0xb40 Apr 26 08:12:02 192.168.122.209 [58072.881065] ? tcp_data_queue+0x1d80/0x1d80 Apr 26 08:12:02 192.168.122.209 [58072.881439] ? __kasan_check_read+0x11/0x20 Apr 26 08:12:02 192.168.122.209 [58072.881815] tcp_v4_do_rcv+0x25f/0x360 Apr 26 08:12:02 192.168.122.209 [58072.882155] tcp_v4_rcv+0x1600/0x1770 Apr 26 08:12:02 192.168.122.209 [58072.882491] ? tcp_v4_early_demux+0x2f0/0x2f0 Apr 26 08:12:02 192.168.122.209 [58072.882882] ip_protocol_deliver_rcu+0x46/0x2e0 Apr 26 08:12:02 192.168.122.209 [58072.883288] ip_local_deliver_finish+0xc6/0xe0 Apr 26 08:12:02 192.168.122.209 [58072.883684] ip_local_deliver+0x1f5/0x210 Apr 26 08:12:02 192.168.122.209 [58072.884053] ? ip_local_deliver_finish+0xe0/0xe0 Apr 26 08:12:02 192.168.122.209 [58072.884468] ? nf_nat_inet_fn+0x2b3/0x440 [nf_nat] Apr 26 08:12:02 192.168.122.209 [58072.884893] ? ip_protocol_deliver_rcu+0x2e0/0x2e0 Apr 26 08:12:02 192.168.122.209 [58072.885323] ? ip_rcv_finish_core.constprop.0+0x17c/0x890 Apr 26 08:12:02 192.168.122.209 [58072.885806] ip_rcv_finish+0xcf/0xf0 Apr 26 08:12:02 192.168.122.209 [58072.886132] ip_rcv+0x16d/0x180 Apr 26 08:12:02 192.168.122.209 [58072.886419] ? ip_local_deliver+0x210/0x210 Apr 26 08:12:02 192.168.122.209 [58072.886791] ? ip_rcv_finish_core.constprop.0+0x890/0x890 Apr 26 08:12:02 192.168.122.209 [58072.887276] ? ip_local_deliver+0x210/0x210 Apr 26 08:12:02 192.168.122.209 [58072.887652] __netif_receive_skb_one_core+0x132/0x140 Apr 26 08:12:02 192.168.122.209 [58072.888103] ? napi_gro_receive+0x260/0x260 Apr 26 08:12:02 192.168.122.209 [58072.888485] ? pv_hash+0xe0/0xe0 Apr 26 08:12:02 192.168.122.209 [58072.888783] ? __kasan_check_write+0x14/0x20 Apr 26 08:12:02 192.168.122.209 [58072.889174] ? _raw_spin_lock+0x7b/0xd0 Apr 26 08:12:02 192.168.122.209 [58072.889519] __netif_receive_skb+0x26/0xb0 Apr 26 08:12:02 192.168.122.209 [58072.889884] process_backlog+0xfe/0x290 Apr 26 08:12:02 192.168.122.209 [58072.890234] net_rx_action+0x287/0x6b0 Apr 26 08:12:02 192.168.122.209 [58072.890570] ? napi_complete_done+0x2c0/0x2c0 Apr 26 08:12:02 192.168.122.209 [58072.890962] ? switch_fpu_return+0x120/0x120 Apr 26 08:12:02 192.168.122.209 [58072.891346] __do_softirq+0xfe/0x383 Apr 26 08:12:02 192.168.122.209 [58072.891674] asm_call_irq_on_stack+0xf/0x20 Apr 26 08:12:02 192.168.122.209 [58072.892049] Apr 26 08:12:02 192.168.122.209 [58072.892246] do_softirq_own_stack+0x3d/0x50 Apr 26 08:12:02 192.168.122.209 [58072.892621] irq_exit_rcu+0xc7/0x120 Apr 26 08:12:02 192.168.122.209 [58072.892948] sysvec_call_function_single+0x3a/0x90 Apr 26 08:12:02 192.168.122.209 [58072.893375] asm_sysvec_call_function_single+0x12/0x20 Apr 26 08:12:02 192.168.122.209 [58072.893830] RIP: 0010:native_safe_halt+0xe/0x10 Apr 26 08:12:02 192.168.122.209 [58072.894239] Code: 49 8b 04 24 a8 08 0f 85 71 ff ff ff e9 0f ff ff ff cc cc cc cc cc cc cc cc cc cc cc e9 07 00 00 00 0f 00 2d d4 62 51 00 fb f4 90 e9 07 00 00 00 0f 00 2d c4 62 51 00 f4 c3 cc cc 0f 1f 44 00 Apr 26 08:12:02 192.168.122.209 [58072.895849] RSP: 0018:ffff888100f37db8 EFLAGS: 00000202 Apr 26 08:12:02 192.168.122.209 [58072.896314] RAX: ffffffffb63426a0 RBX: ffff888100f2c0c0 RCX: ffffffffb632c475 Apr 26 08:12:02 192.168.122.209 [58072.896935] RDX: 0000000018709562 RSI: 0000000000000004 RDI: ffff888147eb5040 Apr 26 08:12:02 192.168.122.209 [58072.897560] RBP: ffff888100f37dc0 R08: 0000000000000001 R09: ffff888147eb5043 Apr 26 08:12:02 192.168.122.209 [58072.898194] R10: ffffed1028fd6a08 R11: 0000000000000001 R12: 0000000000000001 Apr 26 08:12:02 192.168.122.209 [58072.898817] R13: ffffffffb7ae9360 R14: 0000000000000000 R15: 0000000000000000 Apr 26 08:12:02 192.168.122.209 [58072.899448] ? __cpuidle_text_start+0x8/0x8 Apr 26 08:12:02 192.168.122.209 [58072.899821] ? rcu_eqs_enter.constprop.0+0x85/0xa0 Apr 26 08:12:02 192.168.122.209 [58072.900260] ? default_idle+0xe/0x20 Apr 26 08:12:02 192.168.122.209 [58072.900582] arch_cpu_idle+0x15/0x20 Apr 26 08:12:02 192.168.122.209 [58072.900903] default_idle_call+0x66/0x160 Apr 26 08:12:02 192.168.122.209 [58072.901267] do_idle+0x36f/0x430 Apr 26 08:12:02 192.168.122.209 [58072.901567] ? arch_cpu_idle_exit+0x40/0x40 Apr 26 08:12:02 192.168.122.209 [58072.901942] cpu_startup_entry+0x20/0x30 Apr 26 08:12:02 192.168.122.209 [58072.902300] start_secondary+0x1c1/0x210 Apr 26 08:12:02 192.168.122.209 [58072.902651] ? set_cpu_sibling_map+0xd70/0xd70 Apr 26 08:12:02 192.168.122.209 [58072.903056] ? set_bringup_idt_handler.constprop.0+0x84/0x90 Apr 26 08:12:02 192.168.122.209 [58072.903555] ? start_cpu0+0xc/0xc Apr 26 08:12:02 192.168.122.209 [58072.903855] secondary_startup_64_no_verify+0xb0/0xbb Apr 26 08:12:02 192.168.122.209 [58072.904317] Mem-Info: Apr 26 08:12:02 192.168.122.209 [58072.904540] active_anon:34147 inactive_anon:95964 isolated_anon:0 [58072.904540] active_file:97495 inactive_file:97645 isolated_file:5 [58072.904540] unevictable:6821 dirty:159 writeback:0 [58072.904540] slab_reclaimable:24166 slab_unreclaimable:99136 [58072.904540] mapped:36723 shmem:426 pagetables:1341 bounce:0 [58072.904540] free:107677 free_pcp:1649 free_cma:0 Apr 26 08:12:02 192.168.122.209 [58072.907386] Node 0 active_anon:136588kB inactive_anon:383856kB active_file:389980kB inactive_file:390580kB unevictable:27284kB isolated(anon):0kB isolated(file):20kB mapped:146892kB dirty:636kB writeback:0kB shmem:1704kB shmem_thp: 0kB shmem_pmdmapped: 0kB anon_thp: 0kB writeback_tmp:0kB kernel_stack:9632kB all_unreclaimable? no Apr 26 08:12:02 192.168.122.209 [58072.909912] Node 0 DMA free:10880kB min:408kB low:508kB high:608kB reserved_highatomic:4096KB active_anon:8kB inactive_anon:36kB active_file:4kB inactive_file:4kB unevictable:0kB writepending:0kB present:15992kB managed:15908kB mlocked:0kB pagetables:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB Apr 26 08:12:02 192.168.122.209 [58072.912242] lowmem_reserve[]: 0 1900 2534 2534 2534 Apr 26 08:12:02 192.168.122.209 [58072.912693] Node 0 DMA32 free:394648kB min:50364kB low:62952kB high:75540kB reserved_highatomic:0KB active_anon:130632kB inactive_anon:343852kB active_file:313152kB inactive_file:357684kB unevictable:0kB writepending:256kB present:2080624kB managed:1946020kB mlocked:0kB pagetables:672kB bounce:0kB free_pcp:4028kB local_pcp:892kB free_cma:0kB Apr 26 08:12:02 192.168.122.209 [58072.915264] lowmem_reserve[]: 0 0 634 634 634 Apr 26 08:12:02 192.168.122.209 [58072.915697] Node 0 Normal free:25180kB min:16804kB low:21004kB high:25204kB reserved_highatomic:2048KB active_anon:5948kB inactive_anon:39968kB active_file:76824kB inactive_file:33092kB unevictable:27284kB writepending:380kB present:2097152kB managed:649288kB mlocked:27284kB pagetables:4692kB bounce:0kB free_pcp:2568kB local_pcp:616kB free_cma:0kB Apr 26 08:12:02 192.168.122.209 [58072.918346] lowmem_reserve[]: 0 0 0 0 0 Apr 26 08:12:02 192.168.122.209 [58072.918711] Node 0 DMA: 14*4kB (MH) 21*8kB (ME) 22*16kB (MEH) 18*32kB (MEH) 16*64kB (MEH) 10*128kB (MEH) 5*256kB (MEH) 4*512kB (MH) 4*1024kB (UME) 0*2048kB 0*4096kB = 10880kB Apr 26 08:12:02 192.168.122.209 [58072.920107] Node 0 DMA32: 214*4kB (UME) 1940*8kB (UME) 3484*16kB (UME) 3953*32kB (UME) 2373*64kB (UME) 285*128kB (UME) 30*256kB (UE) 0*512kB 0*1024kB 0*2048kB 0*4096kB = 394648kB Apr 26 08:12:02 192.168.122.209 [58072.921524] Node 0 Normal: 957*4kB (UMEH) 390*8kB (UMEH) 389*16kB (UMEH) 318*32kB (UMEH) 25*64kB (U) 1*128kB (U) 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 25076kB Apr 26 08:12:02 192.168.122.209 [58072.922855] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=1048576kB Apr 26 08:12:02 192.168.122.209 [58072.923628] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=2048kB Apr 26 08:12:02 192.168.122.209 [58072.924370] 255950 total pagecache pages Apr 26 08:12:02 192.168.122.209 [58072.924727] 58176 pages in swap cache Apr 26 08:12:02 192.168.122.209 [58072.925069] Swap cache stats: add 297461, delete 239287, find 371816/422657 Apr 26 08:12:02 192.168.122.209 [58072.925691] Free swap = 3755480kB Apr 26 08:12:02 192.168.122.209 [58072.926007] Total swap = 4194300kB Apr 26 08:12:02 192.168.122.209 [58072.926318] 1048442 pages RAM Apr 26 08:12:02 192.168.122.209 [58072.926594] 0 pages HighMem/MovableOnly Apr 26 08:12:02 192.168.122.209 [58072.926946] 395638 pages reserved Apr 26 08:12:02 192.168.122.209 [58072.927254] 0 pages cma reserved Apr 26 08:12:02 192.168.122.209 [58072.927552] 0 pages hwpoisoned Apr 26 08:12:02 192.168.122.209 [58072.927834] [tempesta fw] Warning: Cannot grow HTTP data string Apr 26 08:12:02 192.168.122.209 [58072.936267] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 08:12:05 192.168.122.209 [58075.996939] [tempesta fw] Warning: Cannot grow HTTP data string Apr 26 08:12:05 192.168.122.209 [58076.050036] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 08:12:05 192.168.122.209 [58076.051935] [tempesta fw] Warning: Cannot grow HTTP data string Apr 26 08:12:05 192.168.122.209 [58076.103363] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 08:12:06 192.168.122.209 [58076.675795] [tdb] Close table 'client0.tdb' Apr 26 08:12:06 192.168.122.209 [58076.870070] [tdb] Close table 'sessions0.tdb' Apr 26 08:12:09 192.168.122.209 [58080.073497] [tdb] Close table 'cache0.tdb' Apr 26 08:12:09 192.168.122.209 [58080.337863] [tdb] Close table 'filter0.tdb' Apr 26 08:12:09 192.168.122.209 [58080.338317] [tempesta fw] modules are stopped Apr 26 08:12:10 192.168.122.209 [58080.594300] [tempesta fw] exiting... Apr 26 08:12:10 192.168.122.209 [58080.736889] [tdb] Shutdown Tempesta DB Apr 26 08:12:10 192.168.122.209 [58080.950589] End test: http2_general.test_h2_frame.TestH2FrameEnabledDisabledTsoGroGso.test_mixed_frames_long_headers_disabled Apr 26 08:12:10 192.168.122.209 [58080.972271] Start test: http2_general.test_h2_frame.TestH2FrameEnabledDisabledTsoGroGso.test_mixed_frames_long_headers_enabled Apr 26 08:12:11 192.168.122.209 [58082.065363] [tdb] Start Tempesta DB Apr 26 08:12:11 192.168.122.209 [58082.204266] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:12:13 192.168.122.209 [58083.677024] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58083.677024] Maybe that's fine, but it's worth checking the [58083.677024] config - if there is no relations between the [58083.677024] names, then host name confusion attack is possible. Apr 26 08:12:13 192.168.122.209 [58083.839666] [tempesta fw] Configuration processing is completed. Apr 26 08:12:13 192.168.122.209 [58083.897680] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:12:13 192.168.122.209 [58084.314168] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:12:13 192.168.122.209 [58084.340793] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:12:13 192.168.122.209 [58084.366989] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:12:13 192.168.122.209 [58084.411613] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:12:13 192.168.122.209 [58084.459558] [tempesta fw] Tempesta FW is ready Apr 26 08:12:17 192.168.122.209 [58087.853799] warn_alloc: 2 callbacks suppressed Apr 26 08:12:17 192.168.122.209 [58087.854254] swapper/3: page allocation failure: order:8, mode:0x40a20(GFP_ATOMIC|__GFP_COMP), nodemask=(null),cpuset=/,mems_allowed=0 Apr 26 08:12:17 192.168.122.209 [58087.855332] CPU: 3 PID: 0 Comm: swapper/3 Tainted: G OE 5.10.35.tfw-39c65d3-debug #1 Apr 26 08:12:17 192.168.122.209 [58087.856118] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 Apr 26 08:12:17 192.168.122.209 [58087.856939] Call Trace: Apr 26 08:12:17 192.168.122.209 [58087.857172] Apr 26 08:12:17 192.168.122.209 [58087.857370] dump_stack+0x96/0xc4 Apr 26 08:12:17 192.168.122.209 [58087.857676] warn_alloc.cold+0x87/0x12a Apr 26 08:12:17 192.168.122.209 [58087.858031] ? zone_watermark_ok_safe+0x140/0x140 Apr 26 08:12:17 192.168.122.209 [58087.858462] ? __kasan_check_read+0x11/0x20 Apr 26 08:12:17 192.168.122.209 [58087.858840] ? wakeup_kswapd+0xba/0x290 Apr 26 08:12:17 192.168.122.209 [58087.859191] ? __zone_watermark_ok+0x270/0x270 Apr 26 08:12:17 192.168.122.209 [58087.859595] ? wake_all_kswapds+0xf4/0x140 Apr 26 08:12:17 192.168.122.209 [58087.859966] ? __alloc_pages_slowpath.constprop.0+0x11f4/0x1390 Apr 26 08:12:17 192.168.122.209 [58087.860495] __alloc_pages_slowpath.constprop.0+0x1359/0x1390 Apr 26 08:12:17 192.168.122.209 [58087.861007] ? warn_alloc+0x120/0x120 Apr 26 08:12:17 192.168.122.209 [58087.861347] ? __cpa_process_fault+0x800/0x800 Apr 26 08:12:17 192.168.122.209 [58087.861748] ? eth_get_headlen+0x140/0x140 Apr 26 08:12:17 192.168.122.209 [58087.862116] ? __zone_watermark_ok+0x270/0x270 Apr 26 08:12:17 192.168.122.209 [58087.862521] ? netif_rx+0x1c/0xf0 Apr 26 08:12:17 192.168.122.209 [58087.862832] __alloc_pages_nodemask+0x509/0x540 Apr 26 08:12:17 192.168.122.209 [58087.863244] ? __alloc_pages_slowpath.constprop.0+0x1390/0x1390 Apr 26 08:12:17 192.168.122.209 [58087.863766] ? __kernel_map_pages+0x108/0x180 Apr 26 08:12:17 192.168.122.209 [58087.864163] ? set_direct_map_default_noflush+0x130/0x130 Apr 26 08:12:17 192.168.122.209 [58087.864650] alloc_pages_current+0x96/0x140 Apr 26 08:12:17 192.168.122.209 [58087.865027] __get_free_pages+0x12/0x60 Apr 26 08:12:17 192.168.122.209 [58087.865415] tfw_pool_alloc_pages+0x9b/0xc0 [tempesta_fw] Apr 26 08:12:17 192.168.122.209 [58087.865926] __tfw_pool_realloc+0x123/0x1a0 [tempesta_fw] Apr 26 08:12:17 192.168.122.209 [58087.866443] __str_grow_tree+0x89/0x210 [tempesta_fw] Apr 26 08:12:17 192.168.122.209 [58087.866922] tfw_str_add_compound+0x33/0x40 [tempesta_fw] Apr 26 08:12:17 192.168.122.209 [58087.867430] __tfw_http_msg_add_str_data+0x88/0x1c0 [tempesta_fw] Apr 26 08:12:17 192.168.122.209 [58087.867999] tfw_http_parse_resp+0x11376/0x197d0 [tempesta_fw] Apr 26 08:12:17 192.168.122.209 [58087.868551] ? __resp_parse_body+0xb50/0xb50 [tempesta_fw] Apr 26 08:12:17 192.168.122.209 [58087.869067] ss_skb_process+0x270/0x2f0 [tempesta_fw] Apr 26 08:12:17 192.168.122.209 [58087.869546] ? __resp_parse_body+0xb50/0xb50 [tempesta_fw] Apr 26 08:12:17 192.168.122.209 [58087.870066] ? tfw_sock_srv_exit+0x30/0x30 [tempesta_fw] Apr 26 08:12:17 192.168.122.209 [58087.870546] ? __alloc_pages_nodemask+0x2db/0x540 Apr 26 08:12:17 192.168.122.209 [58087.870996] tfw_http_msg_process_generic+0x282/0xc70 [tempesta_fw] Apr 26 08:12:17 192.168.122.209 [58087.871579] ? tfw_http_req_process+0x11a0/0x11a0 [tempesta_fw] Apr 26 08:12:17 192.168.122.209 [58087.872105] ? __kasan_check_write+0x14/0x20 Apr 26 08:12:17 192.168.122.209 [58087.872496] ? pg_skb_alloc+0x60e/0x680 Apr 26 08:12:17 192.168.122.209 [58087.872845] ? __kasan_check_write+0x14/0x20 Apr 26 08:12:17 192.168.122.209 [58087.873232] ? __alloc_skb+0x278/0x350 Apr 26 08:12:17 192.168.122.209 [58087.873574] ? __kasan_check_write+0x14/0x20 Apr 26 08:12:17 192.168.122.209 [58087.873987] ? __coalesce_frag+0x136/0x370 [tempesta_fw] Apr 26 08:12:17 192.168.122.209 [58087.874488] tfw_http_msg_process+0x80/0xc0 [tempesta_fw] Apr 26 08:12:17 192.168.122.209 [58087.874969] ? skb_release_data+0x8c/0x320 Apr 26 08:12:17 192.168.122.209 [58087.875368] tfw_connection_recv+0x12e/0x250 [tempesta_fw] Apr 26 08:12:17 192.168.122.209 [58087.875884] ? tfw_connection_send+0x70/0x70 [tempesta_fw] Apr 26 08:12:17 192.168.122.209 [58087.876402] ? ss_skb_unroll+0x3d6/0x540 [tempesta_fw] Apr 26 08:12:17 192.168.122.209 [58087.876887] ss_tcp_process_data+0x436/0x8b0 [tempesta_fw] Apr 26 08:12:17 192.168.122.209 [58087.877405] ? __sk_close_locked+0x100/0x100 [tempesta_fw] Apr 26 08:12:17 192.168.122.209 [58087.877894] ? mod_timer+0x10/0x20 Apr 26 08:12:17 192.168.122.209 [58087.878210] ? sk_reset_timer+0x1a/0x70 Apr 26 08:12:17 192.168.122.209 [58087.878615] ss_tcp_data_ready+0x7b/0x150 [tempesta_fw] Apr 26 08:12:17 192.168.122.209 [58087.879082] tcp_data_ready+0x73/0x210 Apr 26 08:12:17 192.168.122.209 [58087.879431] tcp_rcv_established+0x95b/0xb40 Apr 26 08:12:17 192.168.122.209 [58087.879815] ? tcp_data_queue+0x1d80/0x1d80 Apr 26 08:12:17 192.168.122.209 [58087.880196] ? __kasan_check_read+0x11/0x20 Apr 26 08:12:17 192.168.122.209 [58087.880572] tcp_v4_do_rcv+0x25f/0x360 Apr 26 08:12:17 192.168.122.209 [58087.880912] tcp_v4_rcv+0x1600/0x1770 Apr 26 08:12:17 192.168.122.209 [58087.881255] ? tcp_v4_early_demux+0x2f0/0x2f0 Apr 26 08:12:17 192.168.122.209 [58087.881662] ip_protocol_deliver_rcu+0x46/0x2e0 Apr 26 08:12:17 192.168.122.209 [58087.882069] ip_local_deliver_finish+0xc6/0xe0 Apr 26 08:12:17 192.168.122.209 [58087.882477] ip_local_deliver+0x1f5/0x210 Apr 26 08:12:17 192.168.122.209 [58087.882840] ? ip_local_deliver_finish+0xe0/0xe0 Apr 26 08:12:17 192.168.122.209 [58087.883257] ? nf_nat_inet_fn+0x2b3/0x440 [nf_nat] Apr 26 08:12:17 192.168.122.209 [58087.883684] ? ip_protocol_deliver_rcu+0x2e0/0x2e0 Apr 26 08:12:17 192.168.122.209 [58087.884116] ? ip_rcv_finish_core.constprop.0+0x17c/0x890 Apr 26 08:12:17 192.168.122.209 [58087.884600] ip_rcv_finish+0xcf/0xf0 Apr 26 08:12:17 192.168.122.209 [58087.884930] ip_rcv+0x16d/0x180 Apr 26 08:12:17 192.168.122.209 [58087.885222] ? ip_local_deliver+0x210/0x210 Apr 26 08:12:17 192.168.122.209 [58087.885600] ? ip_rcv_finish_core.constprop.0+0x890/0x890 Apr 26 08:12:17 192.168.122.209 [58087.886086] ? update_load_avg+0x59d/0xa70 Apr 26 08:12:17 192.168.122.209 [58087.886458] ? sched_clock+0x9/0x10 Apr 26 08:12:17 192.168.122.209 [58087.886777] ? sched_clock_cpu+0x1b/0x110 Apr 26 08:12:17 192.168.122.209 [58087.887140] ? ip_local_deliver+0x210/0x210 Apr 26 08:12:17 192.168.122.209 [58087.887522] __netif_receive_skb_one_core+0x132/0x140 Apr 26 08:12:17 192.168.122.209 [58087.887970] ? napi_gro_receive+0x260/0x260 Apr 26 08:12:17 192.168.122.209 [58087.888350] ? __kasan_check_write+0x14/0x20 Apr 26 08:12:17 192.168.122.209 [58087.888735] ? _raw_spin_lock+0x7b/0xd0 Apr 26 08:12:17 192.168.122.209 [58087.889082] __netif_receive_skb+0x26/0xb0 Apr 26 08:12:17 192.168.122.209 [58087.889452] ? generic_exec_single+0xb1/0x170 Apr 26 08:12:17 192.168.122.209 [58087.889843] process_backlog+0xfe/0x290 Apr 26 08:12:17 192.168.122.209 [58087.890196] net_rx_action+0x287/0x6b0 Apr 26 08:12:17 192.168.122.209 [58087.890536] ? try_to_wake_up+0x41e/0xa70 Apr 26 08:12:17 192.168.122.209 [58087.890895] ? napi_complete_done+0x2c0/0x2c0 Apr 26 08:12:17 192.168.122.209 [58087.891291] ? switch_fpu_return+0x120/0x120 Apr 26 08:12:17 192.168.122.209 [58087.891678] __do_softirq+0xfe/0x383 Apr 26 08:12:17 192.168.122.209 [58087.892003] asm_call_irq_on_stack+0xf/0x20 Apr 26 08:12:17 192.168.122.209 [58087.892379] Apr 26 08:12:17 192.168.122.209 [58087.892581] do_softirq_own_stack+0x3d/0x50 Apr 26 08:12:17 192.168.122.209 [58087.892960] irq_exit_rcu+0xc7/0x120 Apr 26 08:12:17 192.168.122.209 [58087.893289] sysvec_call_function_single+0x3a/0x90 Apr 26 08:12:17 192.168.122.209 [58087.893720] asm_sysvec_call_function_single+0x12/0x20 Apr 26 08:12:17 192.168.122.209 [58087.894179] RIP: 0010:native_safe_halt+0xe/0x10 Apr 26 08:12:17 192.168.122.209 [58087.894590] Code: 49 8b 04 24 a8 08 0f 85 71 ff ff ff e9 0f ff ff ff cc cc cc cc cc cc cc cc cc cc cc e9 07 00 00 00 0f 00 2d d4 62 51 00 fb f4 90 e9 07 00 00 00 0f 00 2d c4 62 51 00 f4 c3 cc cc 0f 1f 44 00 Apr 26 08:12:17 192.168.122.209 [58087.896210] RSP: 0018:ffff888100f47db8 EFLAGS: 00000202 Apr 26 08:12:17 192.168.122.209 [58087.896676] RAX: ffffffffb63426a0 RBX: ffff888100f28040 RCX: ffffffffb632c475 Apr 26 08:12:17 192.168.122.209 [58087.897307] RDX: 0000000019f954da RSI: 0000000000000004 RDI: ffff888147fb5040 Apr 26 08:12:17 192.168.122.209 [58087.897935] RBP: ffff888100f47dc0 R08: 0000000000000001 R09: ffff888147fb5043 Apr 26 08:12:17 192.168.122.209 [58087.898564] R10: ffffed1028ff6a08 R11: 0000000000000001 R12: 0000000000000003 Apr 26 08:12:17 192.168.122.209 [58087.899220] R13: ffffffffb7ae9360 R14: 0000000000000000 R15: 0000000000000000 Apr 26 08:12:17 192.168.122.209 [58087.899851] ? __cpuidle_text_start+0x8/0x8 Apr 26 08:12:17 192.168.122.209 [58087.900239] ? rcu_eqs_enter.constprop.0+0x85/0xa0 Apr 26 08:12:17 192.168.122.209 [58087.900669] ? default_idle+0xe/0x20 Apr 26 08:12:17 192.168.122.209 [58087.900993] arch_cpu_idle+0x15/0x20 Apr 26 08:12:17 192.168.122.209 [58087.901321] default_idle_call+0x66/0x160 Apr 26 08:12:17 192.168.122.209 [58087.901685] do_idle+0x36f/0x430 Apr 26 08:12:17 192.168.122.209 [58087.901980] ? arch_cpu_idle_exit+0x40/0x40 Apr 26 08:12:17 192.168.122.209 [58087.902361] ? do_idle+0x12/0x430 Apr 26 08:12:17 192.168.122.209 [58087.902663] cpu_startup_entry+0x20/0x30 Apr 26 08:12:17 192.168.122.209 [58087.903022] start_secondary+0x1c1/0x210 Apr 26 08:12:17 192.168.122.209 [58087.903380] ? set_cpu_sibling_map+0xd70/0xd70 Apr 26 08:12:17 192.168.122.209 [58087.903778] ? set_bringup_idt_handler.constprop.0+0x84/0x90 Apr 26 08:12:17 192.168.122.209 [58087.904288] ? start_cpu0+0xc/0xc Apr 26 08:12:17 192.168.122.209 [58087.904597] secondary_startup_64_no_verify+0xb0/0xbb Apr 26 08:12:17 192.168.122.209 [58087.905067] Mem-Info: Apr 26 08:12:17 192.168.122.209 [58087.905302] active_anon:34766 inactive_anon:95168 isolated_anon:0 [58087.905302] active_file:96977 inactive_file:96973 isolated_file:0 [58087.905302] unevictable:6821 dirty:111 writeback:0 [58087.905302] slab_reclaimable:24132 slab_unreclaimable:99126 [58087.905302] mapped:36561 shmem:426 pagetables:1340 bounce:0 [58087.905302] free:117387 free_pcp:1642 free_cma:0 Apr 26 08:12:17 192.168.122.209 [58087.908191] Node 0 active_anon:139064kB inactive_anon:380672kB active_file:387908kB inactive_file:387892kB unevictable:27284kB isolated(anon):0kB isolated(file):0kB mapped:146244kB dirty:444kB writeback:0kB shmem:1704kB shmem_thp: 0kB shmem_pmdmapped: 0kB anon_thp: 0kB writeback_tmp:0kB kernel_stack:9664kB all_unreclaimable? no Apr 26 08:12:17 192.168.122.209 [58087.910700] Node 0 DMA free:10880kB min:408kB low:508kB high:608kB reserved_highatomic:4096KB active_anon:8kB inactive_anon:36kB active_file:8kB inactive_file:0kB unevictable:0kB writepending:0kB present:15992kB managed:15908kB mlocked:0kB pagetables:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB Apr 26 08:12:17 192.168.122.209 [58087.913042] lowmem_reserve[]: 0 1900 2534 2534 2534 Apr 26 08:12:17 192.168.122.209 [58087.913498] Node 0 DMA32 free:433452kB min:50364kB low:62952kB high:75540kB reserved_highatomic:0KB active_anon:133108kB inactive_anon:340604kB active_file:312960kB inactive_file:353604kB unevictable:0kB writepending:152kB present:2080624kB managed:1946020kB mlocked:0kB pagetables:668kB bounce:0kB free_pcp:4208kB local_pcp:1416kB free_cma:0kB Apr 26 08:12:17 192.168.122.209 [58087.916118] lowmem_reserve[]: 0 0 634 634 634 Apr 26 08:12:17 192.168.122.209 [58087.916532] Node 0 Normal free:25216kB min:16804kB low:21004kB high:25204kB reserved_highatomic:2048KB active_anon:5948kB inactive_anon:40032kB active_file:74940kB inactive_file:34288kB unevictable:27284kB writepending:292kB present:2097152kB managed:649288kB mlocked:27284kB pagetables:4692kB bounce:0kB free_pcp:2324kB local_pcp:600kB free_cma:0kB Apr 26 08:12:17 192.168.122.209 [58087.919217] lowmem_reserve[]: 0 0 0 0 0 Apr 26 08:12:17 192.168.122.209 [58087.919597] Node 0 DMA: 14*4kB (MH) 21*8kB (ME) 22*16kB (MEH) 18*32kB (MEH) 16*64kB (MEH) 10*128kB (MEH) 5*256kB (MEH) 4*512kB (MH) 4*1024kB (UME) 0*2048kB 0*4096kB = 10880kB Apr 26 08:12:17 192.168.122.209 [58087.920999] Node 0 DMA32: 399*4kB (UME) 2336*8kB (UME) 5631*16kB (UME) 3983*32kB (UME) 2365*64kB (UME) 287*128kB (UME) 31*256kB (UME) 0*512kB 0*1024kB 0*2048kB 0*4096kB = 433868kB Apr 26 08:12:17 192.168.122.209 [58087.922614] Node 0 Normal: 1081*4kB (UMEH) 302*8kB (UMEH) 373*16kB (UMEH) 330*32kB (UMEH) 25*64kB (U) 1*128kB (U) 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 24996kB Apr 26 08:12:17 192.168.122.209 [58087.924009] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=1048576kB Apr 26 08:12:17 192.168.122.209 [58087.924901] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=2048kB Apr 26 08:12:17 192.168.122.209 [58087.925649] 254716 total pagecache pages Apr 26 08:12:17 192.168.122.209 [58087.926013] 58152 pages in swap cache Apr 26 08:12:17 192.168.122.209 [58087.926357] Swap cache stats: add 297611, delete 239461, find 371861/422703 Apr 26 08:12:17 192.168.122.209 [58087.926971] Free swap = 3754968kB Apr 26 08:12:17 192.168.122.209 [58087.927289] Total swap = 4194300kB Apr 26 08:12:17 192.168.122.209 [58087.927606] 1048442 pages RAM Apr 26 08:12:17 192.168.122.209 [58087.927885] 0 pages HighMem/MovableOnly Apr 26 08:12:17 192.168.122.209 [58087.928242] 395638 pages reserved Apr 26 08:12:17 192.168.122.209 [58087.928548] 0 pages cma reserved Apr 26 08:12:17 192.168.122.209 [58087.928849] 0 pages hwpoisoned Apr 26 08:12:17 192.168.122.209 [58087.929135] [tempesta fw] Warning: Cannot grow HTTP data string Apr 26 08:12:17 192.168.122.209 [58087.936952] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 08:12:19 192.168.122.209 [58090.485979] [tempesta fw] Warning: Cannot grow HTTP data string Apr 26 08:12:19 192.168.122.209 [58090.485992] [tempesta fw] Warning: Cannot grow HTTP data string Apr 26 08:12:19 192.168.122.209 [58090.516087] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 08:12:19 192.168.122.209 [58090.529243] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 08:12:20 192.168.122.209 [58091.063958] [tdb] Close table 'client0.tdb' Apr 26 08:12:20 192.168.122.209 [58091.258371] [tdb] Close table 'sessions0.tdb' Apr 26 08:12:23 192.168.122.209 [58094.459385] [tdb] Close table 'cache0.tdb' Apr 26 08:12:24 192.168.122.209 [58094.706376] [tdb] Close table 'filter0.tdb' Apr 26 08:12:24 192.168.122.209 [58094.706809] [tempesta fw] modules are stopped Apr 26 08:12:24 192.168.122.209 [58094.952647] [tempesta fw] exiting... Apr 26 08:12:24 192.168.122.209 [58095.091077] [tdb] Shutdown Tempesta DB Apr 26 08:12:24 192.168.122.209 [58095.318207] End test: http2_general.test_h2_frame.TestH2FrameEnabledDisabledTsoGroGso.test_mixed_frames_long_headers_enabled Apr 26 08:12:24 192.168.122.209 [58095.342751] Start test: http2_general.test_h2_frame.TestH2FrameEnabledDisabledTsoGroGsoCache.test_headers_frame_for_local_resp_cache_200_long Apr 26 08:12:25 192.168.122.209 [58096.428545] [tdb] Start Tempesta DB Apr 26 08:12:26 192.168.122.209 [58096.575825] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:12:27 192.168.122.209 [58098.261501] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58098.261501] Maybe that's fine, but it's worth checking the [58098.261501] config - if there is no relations between the [58098.261501] names, then host name confusion attack is possible. Apr 26 08:12:27 192.168.122.209 [58098.451804] [tempesta fw] Configuration processing is completed. Apr 26 08:12:27 192.168.122.209 [58098.501293] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:12:28 192.168.122.209 [58098.914002] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:12:28 192.168.122.209 [58098.940512] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:12:28 192.168.122.209 [58098.967288] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:12:28 192.168.122.209 [58099.027801] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:12:28 192.168.122.209 [58099.071761] [tempesta fw] Tempesta FW is ready Apr 26 08:12:33 192.168.122.209 [58104.532201] warn_alloc: 2 callbacks suppressed Apr 26 08:12:33 192.168.122.209 [58104.532669] swapper/2: page allocation failure: order:9, mode:0x40a20(GFP_ATOMIC|__GFP_COMP), nodemask=(null),cpuset=/,mems_allowed=0 Apr 26 08:12:33 192.168.122.209 [58104.533751] CPU: 2 PID: 0 Comm: swapper/2 Tainted: G OE 5.10.35.tfw-39c65d3-debug #1 Apr 26 08:12:33 192.168.122.209 [58104.534549] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 Apr 26 08:12:33 192.168.122.209 [58104.535362] Call Trace: Apr 26 08:12:33 192.168.122.209 [58104.535593] Apr 26 08:12:33 192.168.122.209 [58104.535792] dump_stack+0x96/0xc4 Apr 26 08:12:33 192.168.122.209 [58104.536103] warn_alloc.cold+0x87/0x12a Apr 26 08:12:33 192.168.122.209 [58104.536455] ? zone_watermark_ok_safe+0x140/0x140 Apr 26 08:12:33 192.168.122.209 [58104.536879] ? __kasan_check_read+0x11/0x20 Apr 26 08:12:34 192.168.122.209 [58104.537259] ? wakeup_kswapd+0xba/0x290 Apr 26 08:12:34 192.168.122.209 [58104.537614] ? __zone_watermark_ok+0x270/0x270 Apr 26 08:12:34 192.168.122.209 [58104.538012] ? wake_all_kswapds+0xf4/0x140 Apr 26 08:12:34 192.168.122.209 [58104.538386] ? __alloc_pages_slowpath.constprop.0+0x11f4/0x1390 Apr 26 08:12:34 192.168.122.209 [58104.538912] __alloc_pages_slowpath.constprop.0+0x1359/0x1390 Apr 26 08:12:34 192.168.122.209 [58104.539432] ? netif_rx_internal+0x1c8/0x1f0 Apr 26 08:12:34 192.168.122.209 [58104.539815] ? warn_alloc+0x120/0x120 Apr 26 08:12:34 192.168.122.209 [58104.540150] ? eth_type_trans+0x195/0x2f0 Apr 26 08:12:34 192.168.122.209 [58104.540515] ? eth_get_headlen+0x140/0x140 Apr 26 08:12:34 192.168.122.209 [58104.540887] ? __zone_watermark_ok+0x270/0x270 Apr 26 08:12:34 192.168.122.209 [58104.541286] ? netif_rx+0x1c/0xf0 Apr 26 08:12:34 192.168.122.209 [58104.541641] __alloc_pages_nodemask+0x509/0x540 Apr 26 08:12:34 192.168.122.209 [58104.542046] ? __alloc_pages_slowpath.constprop.0+0x1390/0x1390 Apr 26 08:12:34 192.168.122.209 [58104.542580] alloc_pages_current+0x96/0x140 Apr 26 08:12:34 192.168.122.209 [58104.542955] __get_free_pages+0x12/0x60 Apr 26 08:12:34 192.168.122.209 [58104.543339] tfw_pool_alloc_pages+0x9b/0xc0 [tempesta_fw] Apr 26 08:12:34 192.168.122.209 [58104.543854] __tfw_pool_realloc+0x123/0x1a0 [tempesta_fw] Apr 26 08:12:34 192.168.122.209 [58104.544371] __str_grow_tree+0x89/0x210 [tempesta_fw] Apr 26 08:12:34 192.168.122.209 [58104.544849] tfw_str_add_compound+0x33/0x40 [tempesta_fw] Apr 26 08:12:34 192.168.122.209 [58104.545354] __tfw_http_msg_add_str_data+0x88/0x1c0 [tempesta_fw] Apr 26 08:12:34 192.168.122.209 [58104.545925] tfw_http_parse_resp+0x11376/0x197d0 [tempesta_fw] Apr 26 08:12:34 192.168.122.209 [58104.546475] ? __resp_parse_body+0xb50/0xb50 [tempesta_fw] Apr 26 08:12:34 192.168.122.209 [58104.546993] ss_skb_process+0x270/0x2f0 [tempesta_fw] Apr 26 08:12:34 192.168.122.209 [58104.547471] ? __resp_parse_body+0xb50/0xb50 [tempesta_fw] Apr 26 08:12:34 192.168.122.209 [58104.547988] ? tfw_sock_srv_exit+0x30/0x30 [tempesta_fw] Apr 26 08:12:34 192.168.122.209 [58104.548471] ? __ip_finish_output+0x340/0x340 Apr 26 08:12:34 192.168.122.209 [58104.548887] tfw_http_msg_process_generic+0x282/0xc70 [tempesta_fw] Apr 26 08:12:34 192.168.122.209 [58104.549470] ? tfw_http_req_process+0x11a0/0x11a0 [tempesta_fw] Apr 26 08:12:34 192.168.122.209 [58104.549994] ? pg_skb_alloc+0x60e/0x680 Apr 26 08:12:34 192.168.122.209 [58104.550346] ? __kasan_check_write+0x14/0x20 Apr 26 08:12:34 192.168.122.209 [58104.550733] ? __alloc_skb+0x278/0x350 Apr 26 08:12:34 192.168.122.209 [58104.551075] ? __kasan_check_write+0x14/0x20 Apr 26 08:12:34 192.168.122.209 [58104.551492] ? __coalesce_frag+0x136/0x370 [tempesta_fw] Apr 26 08:12:34 192.168.122.209 [58104.551994] tfw_http_msg_process+0x80/0xc0 [tempesta_fw] Apr 26 08:12:34 192.168.122.209 [58104.552477] ? skb_release_data+0x8c/0x320 Apr 26 08:12:34 192.168.122.209 [58104.552870] tfw_connection_recv+0x12e/0x250 [tempesta_fw] Apr 26 08:12:34 192.168.122.209 [58104.553384] ? tfw_connection_send+0x70/0x70 [tempesta_fw] Apr 26 08:12:34 192.168.122.209 [58104.553907] ? ss_skb_unroll+0x3d6/0x540 [tempesta_fw] Apr 26 08:12:34 192.168.122.209 [58104.554394] ss_tcp_process_data+0x436/0x8b0 [tempesta_fw] Apr 26 08:12:34 192.168.122.209 [58104.554910] ? __sk_close_locked+0x100/0x100 [tempesta_fw] Apr 26 08:12:34 192.168.122.209 [58104.555403] ? mod_timer+0x10/0x20 Apr 26 08:12:34 192.168.122.209 [58104.555717] ? sk_reset_timer+0x1a/0x70 Apr 26 08:12:34 192.168.122.209 [58104.556093] ss_tcp_data_ready+0x7b/0x150 [tempesta_fw] Apr 26 08:12:34 192.168.122.209 [58104.556568] tcp_data_ready+0x73/0x210 Apr 26 08:12:34 192.168.122.209 [58104.556908] tcp_rcv_established+0x95b/0xb40 Apr 26 08:12:34 192.168.122.209 [58104.557297] ? tcp_data_queue+0x1d80/0x1d80 Apr 26 08:12:34 192.168.122.209 [58104.557676] ? __kasan_check_read+0x11/0x20 Apr 26 08:12:34 192.168.122.209 [58104.558054] tcp_v4_do_rcv+0x25f/0x360 Apr 26 08:12:34 192.168.122.209 [58104.558396] tcp_v4_rcv+0x1600/0x1770 Apr 26 08:12:34 192.168.122.209 [58104.558733] ? tcp_v4_early_demux+0x2f0/0x2f0 Apr 26 08:12:34 192.168.122.209 [58104.559124] ip_protocol_deliver_rcu+0x46/0x2e0 Apr 26 08:12:34 192.168.122.209 [58104.559537] ip_local_deliver_finish+0xc6/0xe0 Apr 26 08:12:34 192.168.122.209 [58104.559940] ip_local_deliver+0x1f5/0x210 Apr 26 08:12:34 192.168.122.209 [58104.560307] ? ip_local_deliver_finish+0xe0/0xe0 Apr 26 08:12:34 192.168.122.209 [58104.560726] ? nf_nat_inet_fn+0x2b3/0x440 [nf_nat] Apr 26 08:12:34 192.168.122.209 [58104.561153] ? ip_protocol_deliver_rcu+0x2e0/0x2e0 Apr 26 08:12:34 192.168.122.209 [58104.561585] ? ip_rcv_finish_core.constprop.0+0x17c/0x890 Apr 26 08:12:34 192.168.122.209 [58104.562068] ip_rcv_finish+0xcf/0xf0 Apr 26 08:12:34 192.168.122.209 [58104.562400] ip_rcv+0x16d/0x180 Apr 26 08:12:34 192.168.122.209 [58104.562689] ? ip_local_deliver+0x210/0x210 Apr 26 08:12:34 192.168.122.209 [58104.563076] ? pvclock_clocksource_read+0xe1/0x1a0 Apr 26 08:12:34 192.168.122.209 [58104.563517] ? ip_rcv_finish_core.constprop.0+0x890/0x890 Apr 26 08:12:34 192.168.122.209 [58104.563998] ? update_load_avg+0x132/0xa70 Apr 26 08:12:34 192.168.122.209 [58104.564372] ? sched_clock+0x9/0x10 Apr 26 08:12:34 192.168.122.209 [58104.564690] ? ip_local_deliver+0x210/0x210 Apr 26 08:12:34 192.168.122.209 [58104.565078] __netif_receive_skb_one_core+0x132/0x140 Apr 26 08:12:34 192.168.122.209 [58104.565531] ? napi_gro_receive+0x260/0x260 Apr 26 08:12:34 192.168.122.209 [58104.565910] ? __kasan_check_write+0x14/0x20 Apr 26 08:12:34 192.168.122.209 [58104.566300] ? _raw_spin_lock+0x7b/0xd0 Apr 26 08:12:34 192.168.122.209 [58104.566656] __netif_receive_skb+0x26/0xb0 Apr 26 08:12:34 192.168.122.209 [58104.567026] ? generic_exec_single+0xb1/0x170 Apr 26 08:12:34 192.168.122.209 [58104.567421] process_backlog+0xfe/0x290 Apr 26 08:12:34 192.168.122.209 [58104.567771] net_rx_action+0x287/0x6b0 Apr 26 08:12:34 192.168.122.209 [58104.568115] ? napi_complete_done+0x2c0/0x2c0 Apr 26 08:12:34 192.168.122.209 [58104.568510] ? switch_fpu_return+0x120/0x120 Apr 26 08:12:34 192.168.122.209 [58104.568896] __do_softirq+0xfe/0x383 Apr 26 08:12:34 192.168.122.209 [58104.569220] asm_call_irq_on_stack+0xf/0x20 Apr 26 08:12:34 192.168.122.209 [58104.569602] Apr 26 08:12:34 192.168.122.209 [58104.569807] do_softirq_own_stack+0x3d/0x50 Apr 26 08:12:34 192.168.122.209 [58104.570184] irq_exit_rcu+0xc7/0x120 Apr 26 08:12:34 192.168.122.209 [58104.570514] sysvec_call_function_single+0x3a/0x90 Apr 26 08:12:34 192.168.122.209 [58104.570949] asm_sysvec_call_function_single+0x12/0x20 Apr 26 08:12:34 192.168.122.209 [58104.571409] RIP: 0010:native_safe_halt+0xe/0x10 Apr 26 08:12:34 192.168.122.209 [58104.571822] Code: 49 8b 04 24 a8 08 0f 85 71 ff ff ff e9 0f ff ff ff cc cc cc cc cc cc cc cc cc cc cc e9 07 00 00 00 0f 00 2d d4 62 51 00 fb f4 90 e9 07 00 00 00 0f 00 2d c4 62 51 00 f4 c3 cc cc 0f 1f 44 00 Apr 26 08:12:34 192.168.122.209 [58104.573459] RSP: 0018:ffff888100f3fdb8 EFLAGS: 00000206 Apr 26 08:12:34 192.168.122.209 [58104.573930] RAX: ffffffffb63426a0 RBX: ffff888100f2a080 RCX: ffffffffb632c475 Apr 26 08:12:34 192.168.122.209 [58104.574560] RDX: 000000001976c5d2 RSI: 0000000000000004 RDI: ffff888147f35040 Apr 26 08:12:34 192.168.122.209 [58104.575188] RBP: ffff888100f3fdc0 R08: 0000000000000001 R09: ffff888147f35043 Apr 26 08:12:34 192.168.122.209 [58104.575816] R10: ffffed1028fe6a08 R11: 0000000000000001 R12: 0000000000000002 Apr 26 08:12:34 192.168.122.209 [58104.576447] R13: ffffffffb7ae9360 R14: 0000000000000000 R15: 0000000000000000 Apr 26 08:12:34 192.168.122.209 [58104.577074] ? __cpuidle_text_start+0x8/0x8 Apr 26 08:12:34 192.168.122.209 [58104.577456] ? rcu_eqs_enter.constprop.0+0x85/0xa0 Apr 26 08:12:34 192.168.122.209 [58104.577886] ? default_idle+0xe/0x20 Apr 26 08:12:34 192.168.122.209 [58104.578214] arch_cpu_idle+0x15/0x20 Apr 26 08:12:34 192.168.122.209 [58104.578542] default_idle_call+0x66/0x160 Apr 26 08:12:34 192.168.122.209 [58104.578911] do_idle+0x36f/0x430 Apr 26 08:12:34 192.168.122.209 [58104.579206] ? arch_cpu_idle_exit+0x40/0x40 Apr 26 08:12:34 192.168.122.209 [58104.579596] ? do_idle+0x2ab/0x430 Apr 26 08:12:34 192.168.122.209 [58104.579905] cpu_startup_entry+0x20/0x30 Apr 26 08:12:34 192.168.122.209 [58104.580257] start_secondary+0x1c1/0x210 Apr 26 08:12:34 192.168.122.209 [58104.580614] ? set_cpu_sibling_map+0xd70/0xd70 Apr 26 08:12:34 192.168.122.209 [58104.581013] ? set_bringup_idt_handler.constprop.0+0x84/0x90 Apr 26 08:12:34 192.168.122.209 [58104.581518] ? start_cpu0+0xc/0xc Apr 26 08:12:34 192.168.122.209 [58104.581819] secondary_startup_64_no_verify+0xb0/0xbb Apr 26 08:12:34 192.168.122.209 [58104.582295] Mem-Info: Apr 26 08:12:34 192.168.122.209 [58104.582525] active_anon:35232 inactive_anon:94476 isolated_anon:0 [58104.582525] active_file:96095 inactive_file:96169 isolated_file:0 [58104.582525] unevictable:6821 dirty:157 writeback:0 [58104.582525] slab_reclaimable:24126 slab_unreclaimable:99056 [58104.582525] mapped:36467 shmem:426 pagetables:1350 bounce:0 [58104.582525] free:127706 free_pcp:2105 free_cma:0 Apr 26 08:12:34 192.168.122.209 [58104.585383] Node 0 active_anon:140928kB inactive_anon:377904kB active_file:384380kB inactive_file:383988kB unevictable:27284kB isolated(anon):0kB isolated(file):128kB mapped:145868kB dirty:628kB writeback:0kB shmem:1704kB shmem_thp: 0kB shmem_pmdmapped: 0kB anon_thp: 0kB writeback_tmp:0kB kernel_stack:9664kB all_unreclaimable? no Apr 26 08:12:34 192.168.122.209 [58104.587921] Node 0 DMA free:11904kB min:408kB low:508kB high:608kB reserved_highatomic:4096KB active_anon:8kB inactive_anon:36kB active_file:8kB inactive_file:0kB unevictable:0kB writepending:0kB present:15992kB managed:15908kB mlocked:0kB pagetables:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB Apr 26 08:12:34 192.168.122.209 [58104.590411] lowmem_reserve[]: 0 1900 2534 2534 2534 Apr 26 08:12:34 192.168.122.209 [58104.590875] Node 0 DMA32 free:476492kB min:50364kB low:62952kB high:75540kB reserved_highatomic:0KB active_anon:134968kB inactive_anon:337852kB active_file:311660kB inactive_file:351272kB unevictable:0kB writepending:228kB present:2080624kB managed:1946020kB mlocked:0kB pagetables:668kB bounce:0kB free_pcp:5500kB local_pcp:1424kB free_cma:0kB Apr 26 08:12:34 192.168.122.209 [58104.593569] lowmem_reserve[]: 0 0 634 634 634 Apr 26 08:12:34 192.168.122.209 [58104.593999] Node 0 Normal free:24948kB min:16804kB low:21004kB high:25204kB reserved_highatomic:2048KB active_anon:5952kB inactive_anon:39916kB active_file:72712kB inactive_file:31252kB unevictable:27284kB writepending:400kB present:2097152kB managed:649288kB mlocked:27284kB pagetables:4732kB bounce:0kB free_pcp:2764kB local_pcp:768kB free_cma:0kB Apr 26 08:12:34 192.168.122.209 [58104.596635] lowmem_reserve[]: 0 0 0 0 0 Apr 26 08:12:34 192.168.122.209 [58104.597016] Node 0 DMA: 14*4kB (MH) 21*8kB (ME) 22*16kB (MEH) 18*32kB (MEH) 16*64kB (MEH) 10*128kB (MEH) 5*256kB (MEH) 4*512kB (MH) 3*1024kB (ME) 1*2048kB (U) 0*4096kB = 11904kB Apr 26 08:12:34 192.168.122.209 [58104.598601] Node 0 DMA32: 321*4kB (UME) 2822*8kB (UME) 8003*16kB (UME) 3966*32kB (UME) 2383*64kB (UME) 290*128kB (UME) 33*256kB (UME) 0*512kB 0*1024kB 0*2048kB 0*4096kB = 476900kB Apr 26 08:12:34 192.168.122.209 [58104.600038] Node 0 Normal: 2538*4kB (UMEH) 317*8kB (UMEH) 108*16kB (MEH) 302*32kB (UMEH) 24*64kB (U) 1*128kB (U) 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 25744kB Apr 26 08:12:34 192.168.122.209 [58104.601376] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=1048576kB Apr 26 08:12:34 192.168.122.209 [58104.602156] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=2048kB Apr 26 08:12:34 192.168.122.209 [58104.602996] 251814 total pagecache pages Apr 26 08:12:34 192.168.122.209 [58104.603352] 58041 pages in swap cache Apr 26 08:12:34 192.168.122.209 [58104.603691] Swap cache stats: add 297852, delete 239813, find 371904/422746 Apr 26 08:12:34 192.168.122.209 [58104.604327] Free swap = 3754456kB Apr 26 08:12:34 192.168.122.209 [58104.604645] Total swap = 4194300kB Apr 26 08:12:34 192.168.122.209 [58104.604958] 1048442 pages RAM Apr 26 08:12:34 192.168.122.209 [58104.605245] 0 pages HighMem/MovableOnly Apr 26 08:12:34 192.168.122.209 [58104.605672] 395638 pages reserved Apr 26 08:12:34 192.168.122.209 [58104.605989] 0 pages cma reserved Apr 26 08:12:34 192.168.122.209 [58104.606300] 0 pages hwpoisoned Apr 26 08:12:34 192.168.122.209 [58104.606600] [tempesta fw] Warning: Cannot grow HTTP data string Apr 26 08:12:34 192.168.122.209 [58104.638509] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 08:12:34 192.168.122.209 [58105.170841] [tdb] Close table 'client0.tdb' Apr 26 08:12:34 192.168.122.209 [58105.342963] [tdb] Close table 'sessions0.tdb' Apr 26 08:12:38 192.168.122.209 [58108.577913] [tdb] Close table 'cache0.tdb' Apr 26 08:12:38 192.168.122.209 [58108.839631] [tdb] Close table 'filter0.tdb' Apr 26 08:12:38 192.168.122.209 [58108.840076] [tempesta fw] modules are stopped Apr 26 08:12:38 192.168.122.209 [58109.056002] [tempesta fw] exiting... Apr 26 08:12:38 192.168.122.209 [58109.168008] [tdb] Shutdown Tempesta DB Apr 26 08:12:38 192.168.122.209 [58109.397257] End test: http2_general.test_h2_frame.TestH2FrameEnabledDisabledTsoGroGsoCache.test_headers_frame_for_local_resp_cache_200_long Apr 26 08:12:38 192.168.122.209 [58109.420935] Start test: http2_general.test_h2_frame.TestH2FrameEnabledDisabledTsoGroGsoCache.test_headers_frame_for_local_resp_cache_200_short Apr 26 08:12:39 192.168.122.209 [58110.502853] [tdb] Start Tempesta DB Apr 26 08:12:40 192.168.122.209 [58110.642421] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:12:41 192.168.122.209 [58112.193437] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58112.193437] Maybe that's fine, but it's worth checking the [58112.193437] config - if there is no relations between the [58112.193437] names, then host name confusion attack is possible. Apr 26 08:12:41 192.168.122.209 [58112.375978] [tempesta fw] Configuration processing is completed. Apr 26 08:12:41 192.168.122.209 [58112.427643] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:12:42 192.168.122.209 [58112.862358] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:12:42 192.168.122.209 [58112.889345] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:12:42 192.168.122.209 [58112.916690] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:12:42 192.168.122.209 [58112.983912] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:12:42 192.168.122.209 [58113.027872] [tempesta fw] Tempesta FW is ready Apr 26 08:12:43 192.168.122.209 [58114.520821] [tdb] Close table 'client0.tdb' Apr 26 08:12:44 192.168.122.209 [58114.731406] [tdb] Close table 'sessions0.tdb' Apr 26 08:12:47 192.168.122.209 [58117.904879] [tdb] Close table 'cache0.tdb' Apr 26 08:12:47 192.168.122.209 [58118.157243] [tdb] Close table 'filter0.tdb' Apr 26 08:12:47 192.168.122.209 [58118.157659] [tempesta fw] modules are stopped Apr 26 08:12:47 192.168.122.209 [58118.355703] [tempesta fw] exiting... Apr 26 08:12:47 192.168.122.209 [58118.489935] [tdb] Shutdown Tempesta DB Apr 26 08:12:48 192.168.122.209 [58118.709298] End test: http2_general.test_h2_frame.TestH2FrameEnabledDisabledTsoGroGsoCache.test_headers_frame_for_local_resp_cache_200_short Apr 26 08:12:48 192.168.122.209 [58118.733615] Start test: http2_general.test_h2_frame.TestH2FrameEnabledDisabledTsoGroGsoCache.test_headers_frame_for_local_resp_cache_304_long Apr 26 08:12:49 192.168.122.209 [58119.756840] [tdb] Start Tempesta DB Apr 26 08:12:49 192.168.122.209 [58119.897786] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:12:51 192.168.122.209 [58121.545510] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58121.545510] Maybe that's fine, but it's worth checking the [58121.545510] config - if there is no relations between the [58121.545510] names, then host name confusion attack is possible. Apr 26 08:12:51 192.168.122.209 [58121.724084] [tempesta fw] Configuration processing is completed. Apr 26 08:12:51 192.168.122.209 [58121.772223] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:12:51 192.168.122.209 [58122.189479] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:12:51 192.168.122.209 [58122.220883] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:12:51 192.168.122.209 [58122.247872] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:12:51 192.168.122.209 [58122.324091] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:12:51 192.168.122.209 [58122.364028] [tempesta fw] Tempesta FW is ready Apr 26 08:12:57 192.168.122.209 [58128.079798] python3.10: page allocation failure: order:9, mode:0x40a20(GFP_ATOMIC|__GFP_COMP), nodemask=(null),cpuset=user.slice,mems_allowed=0 Apr 26 08:12:57 192.168.122.209 [58128.081029] CPU: 3 PID: 715106 Comm: python3.10 Tainted: G OE 5.10.35.tfw-39c65d3-debug #1 Apr 26 08:12:57 192.168.122.209 [58128.081865] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 Apr 26 08:12:57 192.168.122.209 [58128.082679] Call Trace: Apr 26 08:12:57 192.168.122.209 [58128.082907] Apr 26 08:12:57 192.168.122.209 [58128.083108] dump_stack+0x96/0xc4 Apr 26 08:12:57 192.168.122.209 [58128.083416] warn_alloc.cold+0x87/0x12a Apr 26 08:12:57 192.168.122.209 [58128.083773] ? zone_watermark_ok_safe+0x140/0x140 Apr 26 08:12:57 192.168.122.209 [58128.084198] ? __kasan_check_read+0x11/0x20 Apr 26 08:12:57 192.168.122.209 [58128.084578] ? wakeup_kswapd+0xba/0x290 Apr 26 08:12:57 192.168.122.209 [58128.084934] ? __zone_watermark_ok+0x270/0x270 Apr 26 08:12:57 192.168.122.209 [58128.085331] ? wake_all_kswapds+0xf4/0x140 Apr 26 08:12:57 192.168.122.209 [58128.085704] ? __alloc_pages_slowpath.constprop.0+0x11f4/0x1390 Apr 26 08:12:57 192.168.122.209 [58128.086232] __alloc_pages_slowpath.constprop.0+0x1359/0x1390 Apr 26 08:12:57 192.168.122.209 [58128.086747] ? netif_rx_internal+0x1c8/0x1f0 Apr 26 08:12:57 192.168.122.209 [58128.087128] ? warn_alloc+0x120/0x120 Apr 26 08:12:57 192.168.122.209 [58128.087458] ? eth_type_trans+0x195/0x2f0 Apr 26 08:12:57 192.168.122.209 [58128.087828] ? eth_get_headlen+0x140/0x140 Apr 26 08:12:57 192.168.122.209 [58128.088196] ? __zone_watermark_ok+0x270/0x270 Apr 26 08:12:57 192.168.122.209 [58128.088591] ? netif_rx+0x1c/0xf0 Apr 26 08:12:57 192.168.122.209 [58128.088897] __alloc_pages_nodemask+0x509/0x540 Apr 26 08:12:57 192.168.122.209 [58128.089322] ? __alloc_pages_slowpath.constprop.0+0x1390/0x1390 Apr 26 08:12:57 192.168.122.209 [58128.089853] alloc_pages_current+0x96/0x140 Apr 26 08:12:57 192.168.122.209 [58128.090228] __get_free_pages+0x12/0x60 Apr 26 08:12:57 192.168.122.209 [58128.090611] tfw_pool_alloc_pages+0x9b/0xc0 [tempesta_fw] Apr 26 08:12:57 192.168.122.209 [58128.091126] __tfw_pool_realloc+0x123/0x1a0 [tempesta_fw] Apr 26 08:12:57 192.168.122.209 [58128.091805] __str_grow_tree+0x89/0x210 [tempesta_fw] Apr 26 08:12:57 192.168.122.209 [58128.092282] tfw_str_add_compound+0x33/0x40 [tempesta_fw] Apr 26 08:12:57 192.168.122.209 [58128.092793] __tfw_http_msg_add_str_data+0x88/0x1c0 [tempesta_fw] Apr 26 08:12:57 192.168.122.209 [58128.093362] tfw_http_parse_resp+0x11376/0x197d0 [tempesta_fw] Apr 26 08:12:57 192.168.122.209 [58128.093909] ? __resp_parse_body+0xb50/0xb50 [tempesta_fw] Apr 26 08:12:57 192.168.122.209 [58128.094423] ss_skb_process+0x270/0x2f0 [tempesta_fw] Apr 26 08:12:57 192.168.122.209 [58128.094902] ? __resp_parse_body+0xb50/0xb50 [tempesta_fw] Apr 26 08:12:57 192.168.122.209 [58128.095418] ? tfw_sock_srv_exit+0x30/0x30 [tempesta_fw] Apr 26 08:12:57 192.168.122.209 [58128.095896] ? __ip_finish_output+0x340/0x340 Apr 26 08:12:57 192.168.122.209 [58128.096311] tfw_http_msg_process_generic+0x282/0xc70 [tempesta_fw] Apr 26 08:12:57 192.168.122.209 [58128.096894] ? tfw_http_req_process+0x11a0/0x11a0 [tempesta_fw] Apr 26 08:12:57 192.168.122.209 [58128.097419] ? pg_skb_alloc+0x60e/0x680 Apr 26 08:12:57 192.168.122.209 [58128.097773] ? __kasan_check_write+0x14/0x20 Apr 26 08:12:57 192.168.122.209 [58128.098154] ? __alloc_skb+0x278/0x350 Apr 26 08:12:57 192.168.122.209 [58128.098493] ? __kasan_check_write+0x14/0x20 Apr 26 08:12:57 192.168.122.209 [58128.098910] ? __coalesce_frag+0x136/0x370 [tempesta_fw] Apr 26 08:12:57 192.168.122.209 [58128.099423] tfw_http_msg_process+0x80/0xc0 [tempesta_fw] Apr 26 08:12:57 192.168.122.209 [58128.099903] ? skb_release_data+0x8c/0x320 Apr 26 08:12:57 192.168.122.209 [58128.100296] tfw_connection_recv+0x12e/0x250 [tempesta_fw] Apr 26 08:12:57 192.168.122.209 [58128.100814] ? tfw_connection_send+0x70/0x70 [tempesta_fw] Apr 26 08:12:57 192.168.122.209 [58128.101328] ? ss_skb_unroll+0x3d6/0x540 [tempesta_fw] Apr 26 08:12:57 192.168.122.209 [58128.101814] ss_tcp_process_data+0x436/0x8b0 [tempesta_fw] Apr 26 08:12:57 192.168.122.209 [58128.102326] ? __sk_close_locked+0x100/0x100 [tempesta_fw] Apr 26 08:12:57 192.168.122.209 [58128.102822] ? mod_timer+0x10/0x20 Apr 26 08:12:57 192.168.122.209 [58128.103131] ? sk_reset_timer+0x1a/0x70 Apr 26 08:12:57 192.168.122.209 [58128.103504] ss_tcp_data_ready+0x7b/0x150 [tempesta_fw] Apr 26 08:12:57 192.168.122.209 [58128.104001] tcp_data_ready+0x73/0x210 Apr 26 08:12:57 192.168.122.209 [58128.104345] tcp_rcv_established+0x95b/0xb40 Apr 26 08:12:57 192.168.122.209 [58128.104734] ? tcp_data_queue+0x1d80/0x1d80 Apr 26 08:12:57 192.168.122.209 [58128.105106] ? __kasan_check_read+0x11/0x20 Apr 26 08:12:57 192.168.122.209 [58128.105487] tcp_v4_do_rcv+0x25f/0x360 Apr 26 08:12:57 192.168.122.209 [58128.105844] tcp_v4_rcv+0x1600/0x1770 Apr 26 08:12:57 192.168.122.209 [58128.106179] ? tcp_v4_early_demux+0x2f0/0x2f0 Apr 26 08:12:57 192.168.122.209 [58128.106566] ip_protocol_deliver_rcu+0x46/0x2e0 Apr 26 08:12:57 192.168.122.209 [58128.106976] ip_local_deliver_finish+0xc6/0xe0 Apr 26 08:12:57 192.168.122.209 [58128.107375] ip_local_deliver+0x1f5/0x210 Apr 26 08:12:57 192.168.122.209 [58128.107741] ? ip_local_deliver_finish+0xe0/0xe0 Apr 26 08:12:57 192.168.122.209 [58128.108156] ? nf_nat_inet_fn+0x2b3/0x440 [nf_nat] Apr 26 08:12:57 192.168.122.209 [58128.108580] ? ip_protocol_deliver_rcu+0x2e0/0x2e0 Apr 26 08:12:57 192.168.122.209 [58128.109016] ? ip_rcv_finish_core.constprop.0+0x17c/0x890 Apr 26 08:12:57 192.168.122.209 [58128.109505] ip_rcv_finish+0xcf/0xf0 Apr 26 08:12:57 192.168.122.209 [58128.109836] ip_rcv+0x16d/0x180 Apr 26 08:12:57 192.168.122.209 [58128.110122] ? ip_local_deliver+0x210/0x210 Apr 26 08:12:57 192.168.122.209 [58128.110500] ? ip_rcv_finish_core.constprop.0+0x890/0x890 Apr 26 08:12:57 192.168.122.209 [58128.110984] ? ttwu_do_activate+0xa4/0x170 Apr 26 08:12:57 192.168.122.209 [58128.111350] ? ip_local_deliver+0x210/0x210 Apr 26 08:12:57 192.168.122.209 [58128.111731] __netif_receive_skb_one_core+0x132/0x140 Apr 26 08:12:57 192.168.122.209 [58128.112182] ? napi_gro_receive+0x260/0x260 Apr 26 08:12:57 192.168.122.209 [58128.112557] ? __kasan_check_write+0x14/0x20 Apr 26 08:12:57 192.168.122.209 [58128.112944] ? _raw_spin_lock+0x7b/0xd0 Apr 26 08:12:57 192.168.122.209 [58128.113289] __netif_receive_skb+0x26/0xb0 Apr 26 08:12:57 192.168.122.209 [58128.113664] process_backlog+0xfe/0x290 Apr 26 08:12:57 192.168.122.209 [58128.114013] net_rx_action+0x287/0x6b0 Apr 26 08:12:57 192.168.122.209 [58128.114349] ? napi_complete_done+0x2c0/0x2c0 Apr 26 08:12:57 192.168.122.209 [58128.114746] ? switch_fpu_return+0x120/0x120 Apr 26 08:12:57 192.168.122.209 [58128.115132] __do_softirq+0xfe/0x383 Apr 26 08:12:57 192.168.122.209 [58128.115459] asm_call_irq_on_stack+0xf/0x20 Apr 26 08:12:57 192.168.122.209 [58128.115835] Apr 26 08:12:57 192.168.122.209 [58128.116034] do_softirq_own_stack+0x3d/0x50 Apr 26 08:12:57 192.168.122.209 [58128.116417] do_softirq+0x72/0x90 Apr 26 08:12:57 192.168.122.209 [58128.116726] __local_bh_enable_ip+0x50/0x60 Apr 26 08:12:57 192.168.122.209 [58128.117101] ip_finish_output2+0x351/0xa80 Apr 26 08:12:57 192.168.122.209 [58128.117468] ? __ip_flush_pending_frames.constprop.0+0x130/0x130 Apr 26 08:12:57 192.168.122.209 [58128.118015] ? cgroup_bpf_release+0x400/0x400 Apr 26 08:12:57 192.168.122.209 [58128.118408] __ip_finish_output+0x16b/0x340 Apr 26 08:12:57 192.168.122.209 [58128.118787] ip_finish_output+0x2d/0xe0 Apr 26 08:12:57 192.168.122.209 [58128.119134] ip_output+0x133/0x210 Apr 26 08:12:57 192.168.122.209 [58128.119455] ? ip_mc_output+0x4e0/0x4e0 Apr 26 08:12:57 192.168.122.209 [58128.119814] ? kasan_save_stack+0x23/0x50 Apr 26 08:12:57 192.168.122.209 [58128.120174] ? __kasan_kmalloc.constprop.0+0xcf/0xe0 Apr 26 08:12:57 192.168.122.209 [58128.120616] ? kasan_kmalloc+0x9/0x10 Apr 26 08:12:57 192.168.122.209 [58128.120956] ? __ip_finish_output+0x340/0x340 Apr 26 08:12:57 192.168.122.209 [58128.121348] ? ipv4_dst_check+0x6d/0xa0 Apr 26 08:12:57 192.168.122.209 [58128.121698] __ip_queue_xmit+0x356/0x7d0 Apr 26 08:12:57 192.168.122.209 [58128.122074] ip_queue_xmit+0x3b/0x50 Apr 26 08:12:57 192.168.122.209 [58128.122401] __tcp_transmit_skb+0x152f/0x1730 Apr 26 08:12:57 192.168.122.209 [58128.122795] ? __tcp_select_window+0x370/0x370 Apr 26 08:12:57 192.168.122.209 [58128.123194] ? pvclock_clocksource_read+0xe1/0x1a0 Apr 26 08:12:57 192.168.122.209 [58128.123620] ? __kasan_check_read+0x11/0x20 Apr 26 08:12:57 192.168.122.209 [58128.124028] tcp_write_xmit+0x796/0x2a50 Apr 26 08:12:57 192.168.122.209 [58128.124401] ? iov_iter_advance+0x12b/0x5f0 Apr 26 08:12:57 192.168.122.209 [58128.124778] ? bpf_skops_hdr_opt_len+0x210/0x210 Apr 26 08:12:57 192.168.122.209 [58128.125190] __tcp_push_pending_frames+0x5f/0x1a0 Apr 26 08:12:57 192.168.122.209 [58128.125610] tcp_push+0x209/0x2b0 Apr 26 08:12:57 192.168.122.209 [58128.125927] tcp_sendmsg_locked+0x13fa/0x15f0 Apr 26 08:12:57 192.168.122.209 [58128.126334] ? skb_do_copy_data_nocache+0x1b0/0x1b0 Apr 26 08:12:57 192.168.122.209 [58128.126774] ? __kasan_check_write+0x14/0x20 Apr 26 08:12:57 192.168.122.209 [58128.127162] ? _raw_spin_lock_bh+0x86/0xe0 Apr 26 08:12:57 192.168.122.209 [58128.127538] ? __x64_sys_poll+0x250/0x250 Apr 26 08:12:57 192.168.122.209 [58128.127902] ? __kasan_check_write+0x14/0x20 Apr 26 08:12:57 192.168.122.209 [58128.128285] tcp_sendmsg+0x2d/0x50 Apr 26 08:12:57 192.168.122.209 [58128.128599] inet_sendmsg+0x64/0xa0 Apr 26 08:12:57 192.168.122.209 [58128.128921] ? inet_send_prepare+0x120/0x120 Apr 26 08:12:57 192.168.122.209 [58128.129320] sock_sendmsg+0x97/0xa0 Apr 26 08:12:57 192.168.122.209 [58128.129637] __sys_sendto+0x1ab/0x260 Apr 26 08:12:57 192.168.122.209 [58128.129978] ? __ia32_sys_getpeername+0x50/0x50 Apr 26 08:12:57 192.168.122.209 [58128.130422] ? clear_user+0x25/0x30 Apr 26 08:12:57 192.168.122.209 [58128.130748] ? __x64_sys_rseq+0x260/0x260 Apr 26 08:12:57 192.168.122.209 [58128.131113] ? mem_cgroup_handle_over_high+0x87/0x430 Apr 26 08:12:57 192.168.122.209 [58128.131568] ? __blkcg_punt_bio_submit+0xe0/0xe0 Apr 26 08:12:57 192.168.122.209 [58128.131987] __x64_sys_sendto+0x7f/0x90 Apr 26 08:12:57 192.168.122.209 [58128.132333] do_syscall_64+0x38/0x90 Apr 26 08:12:57 192.168.122.209 [58128.132656] entry_SYSCALL_64_after_hwframe+0x44/0xa9 Apr 26 08:12:57 192.168.122.209 [58128.133112] RIP: 0033:0x7f7ff82d8efa Apr 26 08:12:57 192.168.122.209 [58128.133437] Code: e0 89 7d e8 89 4d d4 e8 74 c6 f6 ff 44 8b 55 d4 48 8b 55 d8 45 31 c9 89 c3 48 8b 75 e0 8b 7d e8 45 31 c0 b8 2c 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 36 89 df 48 89 45 e8 e8 c3 c6 f6 ff 48 8b 45 Apr 26 08:12:57 192.168.122.209 [58128.135053] RSP: 002b:00007f7ff3a7cd80 EFLAGS: 00000246 ORIG_RAX: 000000000000002c Apr 26 08:12:57 192.168.122.209 [58128.135777] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f7ff82d8efa Apr 26 08:12:57 192.168.122.209 [58128.136421] RDX: 0000000000000001 RSI: 00007f7ff725dd60 RDI: 000000000000001f Apr 26 08:12:57 192.168.122.209 [58128.137053] RBP: 00007f7ff3a7cdb0 R08: 0000000000000000 R09: 0000000000000000 Apr 26 08:12:57 192.168.122.209 [58128.137683] R10: 0000000000000000 R11: 0000000000000246 R12: 00007f7ff1f546a0 Apr 26 08:12:57 192.168.122.209 [58128.138308] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 Apr 26 08:12:57 192.168.122.209 [58128.138960] Mem-Info: Apr 26 08:12:57 192.168.122.209 [58128.139180] active_anon:35355 inactive_anon:94131 isolated_anon:0 [58128.139180] active_file:95934 inactive_file:95123 isolated_file:0 [58128.139180] unevictable:6821 dirty:93 writeback:0 [58128.139180] slab_reclaimable:24122 slab_unreclaimable:99016 [58128.139180] mapped:36429 shmem:426 pagetables:1341 bounce:0 [58128.139180] free:120696 free_pcp:1594 free_cma:0 Apr 26 08:12:57 192.168.122.209 [58128.142085] Node 0 active_anon:141420kB inactive_anon:376524kB active_file:383736kB inactive_file:380492kB unevictable:27284kB isolated(anon):0kB isolated(file):0kB mapped:145716kB dirty:496kB writeback:0kB shmem:1704kB shmem_thp: 0kB shmem_pmdmapped: 0kB anon_thp: 0kB writeback_tmp:0kB kernel_stack:9664kB all_unreclaimable? no Apr 26 08:12:57 192.168.122.209 [58128.144656] Node 0 DMA free:11904kB min:408kB low:508kB high:608kB reserved_highatomic:4096KB active_anon:8kB inactive_anon:36kB active_file:8kB inactive_file:0kB unevictable:0kB writepending:0kB present:15992kB managed:15908kB mlocked:0kB pagetables:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB Apr 26 08:12:57 192.168.122.209 [58128.147034] lowmem_reserve[]: 0 1900 2534 2534 2534 Apr 26 08:12:57 192.168.122.209 [58128.147484] Node 0 DMA32 free:443876kB min:50364kB low:62952kB high:75540kB reserved_highatomic:0KB active_anon:135464kB inactive_anon:336496kB active_file:311668kB inactive_file:348240kB unevictable:0kB writepending:128kB present:2080624kB managed:1946020kB mlocked:0kB pagetables:672kB bounce:0kB free_pcp:3880kB local_pcp:432kB free_cma:0kB Apr 26 08:12:57 192.168.122.209 [58128.150104] lowmem_reserve[]: 0 0 634 634 634 Apr 26 08:12:57 192.168.122.209 [58128.150505] Node 0 Normal free:27004kB min:16804kB low:21004kB high:25204kB reserved_highatomic:2048KB active_anon:5948kB inactive_anon:39928kB active_file:72896kB inactive_file:32612kB unevictable:27284kB writepending:244kB present:2097152kB managed:649288kB mlocked:27284kB pagetables:4692kB bounce:0kB free_pcp:2496kB local_pcp:576kB free_cma:0kB Apr 26 08:12:57 192.168.122.209 [58128.153189] lowmem_reserve[]: 0 0 0 0 0 Apr 26 08:12:57 192.168.122.209 [58128.153547] Node 0 DMA: 14*4kB (MH) 21*8kB (ME) 22*16kB (MEH) 18*32kB (MEH) 16*64kB (MEH) 10*128kB (MEH) 5*256kB (MEH) 4*512kB (MH) 3*1024kB (ME) 1*2048kB (U) 0*4096kB = 11904kB Apr 26 08:12:57 192.168.122.209 [58128.154947] Node 0 DMA32: 252*4kB (UME) 2641*8kB (UME) 6013*16kB (UME) 3986*32kB (UME) 2383*64kB (UME) 289*128kB (UME) 34*256kB (UME) 0*512kB 0*1024kB 0*2048kB 0*4096kB = 444104kB Apr 26 08:12:57 192.168.122.209 [58128.156362] Node 0 Normal: 2161*4kB (MEH) 210*8kB (UMEH) 277*16kB (UMEH) 330*32kB (UMEH) 24*64kB (U) 1*128kB (U) 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 26980kB Apr 26 08:12:57 192.168.122.209 [58128.157677] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=1048576kB Apr 26 08:12:57 192.168.122.209 [58128.158440] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=2048kB Apr 26 08:12:57 192.168.122.209 [58128.159177] 251714 total pagecache pages Apr 26 08:12:57 192.168.122.209 [58128.159537] 58003 pages in swap cache Apr 26 08:12:57 192.168.122.209 [58128.159894] Swap cache stats: add 297900, delete 239896, find 371992/422836 Apr 26 08:12:57 192.168.122.209 [58128.160625] Free swap = 3754200kB Apr 26 08:12:57 192.168.122.209 [58128.160940] Total swap = 4194300kB Apr 26 08:12:57 192.168.122.209 [58128.161249] 1048442 pages RAM Apr 26 08:12:57 192.168.122.209 [58128.161524] 0 pages HighMem/MovableOnly Apr 26 08:12:57 192.168.122.209 [58128.161876] 395638 pages reserved Apr 26 08:12:57 192.168.122.209 [58128.162178] 0 pages cma reserved Apr 26 08:12:57 192.168.122.209 [58128.162474] 0 pages hwpoisoned Apr 26 08:12:57 192.168.122.209 [58128.162764] [tempesta fw] Warning: Cannot grow HTTP data string Apr 26 08:12:57 192.168.122.209 [58128.207113] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 08:12:58 192.168.122.209 [58128.772632] [tdb] Close table 'client0.tdb' Apr 26 08:12:58 192.168.122.209 [58128.959779] [tdb] Close table 'sessions0.tdb' Apr 26 08:13:01 192.168.122.209 [58132.132298] [tdb] Close table 'cache0.tdb' Apr 26 08:13:01 192.168.122.209 [58132.379040] [tdb] Close table 'filter0.tdb' Apr 26 08:13:01 192.168.122.209 [58132.379482] [tempesta fw] modules are stopped Apr 26 08:13:02 192.168.122.209 [58132.603015] [tempesta fw] exiting... Apr 26 08:13:02 192.168.122.209 [58132.731536] [tdb] Shutdown Tempesta DB Apr 26 08:13:02 192.168.122.209 [58132.974347] End test: http2_general.test_h2_frame.TestH2FrameEnabledDisabledTsoGroGsoCache.test_headers_frame_for_local_resp_cache_304_long Apr 26 08:13:02 192.168.122.209 [58132.999124] Start test: http2_general.test_h2_frame.TestH2FrameEnabledDisabledTsoGroGsoCache.test_headers_frame_for_local_resp_cache_304_short Apr 26 08:13:03 192.168.122.209 [58134.050374] [tdb] Start Tempesta DB Apr 26 08:13:03 192.168.122.209 [58134.198557] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:13:05 192.168.122.209 [58135.837688] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58135.837688] Maybe that's fine, but it's worth checking the [58135.837688] config - if there is no relations between the [58135.837688] names, then host name confusion attack is possible. Apr 26 08:13:05 192.168.122.209 [58136.016295] [tempesta fw] Configuration processing is completed. Apr 26 08:13:05 192.168.122.209 [58136.067189] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:13:05 192.168.122.209 [58136.484411] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:13:05 192.168.122.209 [58136.511212] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:13:06 192.168.122.209 [58136.538455] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:13:06 192.168.122.209 [58136.572271] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:13:06 192.168.122.209 [58136.620193] [tempesta fw] Tempesta FW is ready Apr 26 08:13:07 192.168.122.209 [58138.082950] [tdb] Close table 'client0.tdb' Apr 26 08:13:07 192.168.122.209 [58138.284831] [tdb] Close table 'sessions0.tdb' Apr 26 08:13:10 192.168.122.209 [58141.439445] [tdb] Close table 'cache0.tdb' Apr 26 08:13:11 192.168.122.209 [58141.678216] [tdb] Close table 'filter0.tdb' Apr 26 08:13:11 192.168.122.209 [58141.678645] [tempesta fw] modules are stopped Apr 26 08:13:11 192.168.122.209 [58141.910304] [tempesta fw] exiting... Apr 26 08:13:11 192.168.122.209 [58142.016708] [tdb] Shutdown Tempesta DB Apr 26 08:13:11 192.168.122.209 [58142.249327] End test: http2_general.test_h2_frame.TestH2FrameEnabledDisabledTsoGroGsoCache.test_headers_frame_for_local_resp_cache_304_short Apr 26 08:13:11 192.168.122.209 [58142.260772] Start test: http2_general.test_h2_frame.TestH2FrameEnabledDisabledTsoGroGsoStickyCookie.test_headers_frame_for_local_resp_sticky_cookie_long Apr 26 08:13:12 192.168.122.209 [58143.390795] [tdb] Start Tempesta DB Apr 26 08:13:13 192.168.122.209 [58143.537439] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:13:14 192.168.122.209 [58145.313636] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58145.313636] Maybe that's fine, but it's worth checking the [58145.313636] config - if there is no relations between the [58145.313636] names, then host name confusion attack is possible. Apr 26 08:13:14 192.168.122.209 [58145.496308] [tempesta fw] Configuration processing is completed. Apr 26 08:13:15 192.168.122.209 [58145.548313] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:13:15 192.168.122.209 [58145.976649] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:13:15 192.168.122.209 [58146.003928] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:13:15 192.168.122.209 [58146.040378] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:13:15 192.168.122.209 [58146.092412] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:13:15 192.168.122.209 [58146.136330] [tempesta fw] Tempesta FW is ready Apr 26 08:13:49 192.168.122.209 [58180.385282] [tdb] Close table 'client0.tdb' Apr 26 08:13:50 192.168.122.209 [58180.596361] [tdb] Close table 'sessions0.tdb' Apr 26 08:13:53 192.168.122.209 [58183.803307] [tdb] Close table 'cache0.tdb' Apr 26 08:13:53 192.168.122.209 [58184.047739] [tdb] Close table 'filter0.tdb' Apr 26 08:13:53 192.168.122.209 [58184.048139] [tempesta fw] modules are stopped Apr 26 08:13:53 192.168.122.209 [58184.268870] [tempesta fw] exiting... Apr 26 08:13:53 192.168.122.209 [58184.384302] [tdb] Shutdown Tempesta DB Apr 26 08:13:54 192.168.122.209 [58184.634858] End test: http2_general.test_h2_frame.TestH2FrameEnabledDisabledTsoGroGsoStickyCookie.test_headers_frame_for_local_resp_sticky_cookie_long Apr 26 08:13:54 192.168.122.209 [58184.649482] Start test: http2_general.test_h2_frame.TestH2FrameEnabledDisabledTsoGroGsoStickyCookie.test_headers_frame_for_local_resp_sticky_cookie_short Apr 26 08:13:55 192.168.122.209 [58185.733459] [tdb] Start Tempesta DB Apr 26 08:13:55 192.168.122.209 [58185.874549] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:13:57 192.168.122.209 [58187.666509] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58187.666509] Maybe that's fine, but it's worth checking the [58187.666509] config - if there is no relations between the [58187.666509] names, then host name confusion attack is possible. Apr 26 08:13:57 192.168.122.209 [58187.844904] [tempesta fw] Configuration processing is completed. Apr 26 08:13:57 192.168.122.209 [58187.895970] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:13:57 192.168.122.209 [58188.321284] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:13:57 192.168.122.209 [58188.349000] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:13:57 192.168.122.209 [58188.377581] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:13:57 192.168.122.209 [58188.428942] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:13:57 192.168.122.209 [58188.476867] [tempesta fw] Tempesta FW is ready Apr 26 08:13:59 192.168.122.209 [58190.166520] [tdb] Close table 'client0.tdb' Apr 26 08:13:59 192.168.122.209 [58190.374183] [tdb] Close table 'sessions0.tdb' Apr 26 08:14:02 192.168.122.209 [58193.532264] [tdb] Close table 'cache0.tdb' Apr 26 08:14:03 192.168.122.209 [58193.768246] [tdb] Close table 'filter0.tdb' Apr 26 08:14:03 192.168.122.209 [58193.768672] [tempesta fw] modules are stopped Apr 26 08:14:03 192.168.122.209 [58194.014824] [tempesta fw] exiting... Apr 26 08:14:03 192.168.122.209 [58194.142963] [tdb] Shutdown Tempesta DB Apr 26 08:14:03 192.168.122.209 [58194.382384] End test: http2_general.test_h2_frame.TestH2FrameEnabledDisabledTsoGroGsoStickyCookie.test_headers_frame_for_local_resp_sticky_cookie_short Apr 26 08:14:03 192.168.122.209 [58194.408178] Start test: http2_general.test_h2_frame.TestPostponedFrames.test_headers Apr 26 08:14:04 192.168.122.209 [58195.505172] [tdb] Start Tempesta DB Apr 26 08:14:05 192.168.122.209 [58195.649003] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:14:06 192.168.122.209 [58197.234441] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58197.234441] Maybe that's fine, but it's worth checking the [58197.234441] config - if there is no relations between the [58197.234441] names, then host name confusion attack is possible. Apr 26 08:14:06 192.168.122.209 [58197.393079] [tempesta fw] Configuration processing is completed. Apr 26 08:14:06 192.168.122.209 [58197.445183] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:14:07 192.168.122.209 [58197.865482] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:14:07 192.168.122.209 [58197.892758] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:14:07 192.168.122.209 [58197.919117] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:14:07 192.168.122.209 [58197.973050] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:14:07 192.168.122.209 [58198.021009] [tempesta fw] Tempesta FW is ready Apr 26 08:14:14 192.168.122.209 [58205.273196] [tdb] Close table 'client0.tdb' Apr 26 08:14:14 192.168.122.209 [58205.462949] [tdb] Close table 'sessions0.tdb' Apr 26 08:14:18 192.168.122.209 [58208.679849] [tdb] Close table 'cache0.tdb' Apr 26 08:14:18 192.168.122.209 [58208.920397] [tdb] Close table 'filter0.tdb' Apr 26 08:14:18 192.168.122.209 [58208.920817] [tempesta fw] modules are stopped Apr 26 08:14:18 192.168.122.209 [58209.133493] [tempesta fw] exiting... Apr 26 08:14:18 192.168.122.209 [58209.265308] [tdb] Shutdown Tempesta DB Apr 26 08:14:18 192.168.122.209 [58209.503381] End test: http2_general.test_h2_frame.TestPostponedFrames.test_headers Apr 26 08:14:18 192.168.122.209 [58209.514066] Start test: http2_general.test_h2_frame.TestPostponedFrames.test_trailers Apr 26 08:14:20 192.168.122.209 [58210.602233] [tdb] Start Tempesta DB Apr 26 08:14:20 192.168.122.209 [58210.744782] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:14:21 192.168.122.209 [58212.318572] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58212.318572] Maybe that's fine, but it's worth checking the [58212.318572] config - if there is no relations between the [58212.318572] names, then host name confusion attack is possible. Apr 26 08:14:21 192.168.122.209 [58212.469250] [tempesta fw] Configuration processing is completed. Apr 26 08:14:21 192.168.122.209 [58212.521002] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:14:22 192.168.122.209 [58212.946989] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:14:22 192.168.122.209 [58212.974677] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:14:22 192.168.122.209 [58213.001587] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:14:22 192.168.122.209 [58213.041231] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:14:22 192.168.122.209 [58213.089131] [tempesta fw] Tempesta FW is ready Apr 26 08:14:28 192.168.122.209 [58219.098855] [tdb] Close table 'client0.tdb' Apr 26 08:14:28 192.168.122.209 [58219.311022] [tdb] Close table 'sessions0.tdb' Apr 26 08:14:31 192.168.122.209 [58222.425903] [tdb] Close table 'cache0.tdb' Apr 26 08:14:32 192.168.122.209 [58222.679944] [tdb] Close table 'filter0.tdb' Apr 26 08:14:32 192.168.122.209 [58222.680373] [tempesta fw] modules are stopped Apr 26 08:14:32 192.168.122.209 [58222.922174] [tempesta fw] exiting... Apr 26 08:14:32 192.168.122.209 [58223.052184] [tdb] Shutdown Tempesta DB Apr 26 08:14:32 192.168.122.209 [58223.267577] End test: http2_general.test_h2_frame.TestPostponedFrames.test_trailers Apr 26 08:14:32 192.168.122.209 [58223.287051] Start test: http2_general.test_h2_headers.AddBackendLongHeaders.test Apr 26 08:14:34 192.168.122.209 [58224.591068] [tdb] Start Tempesta DB Apr 26 08:14:34 192.168.122.209 [58224.741825] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:14:35 192.168.122.209 [58226.107148] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58226.107148] Maybe that's fine, but it's worth checking the [58226.107148] config - if there is no relations between the [58226.107148] names, then host name confusion attack is possible. Apr 26 08:14:35 192.168.122.209 [58226.157397] [tempesta fw] Configuration processing is completed. Apr 26 08:14:35 192.168.122.209 [58226.211917] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:14:36 192.168.122.209 [58226.626602] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:14:36 192.168.122.209 [58226.653080] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:14:36 192.168.122.209 [58226.685426] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:14:36 192.168.122.209 [58226.773422] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:14:36 192.168.122.209 [58226.829360] [tempesta fw] Tempesta FW is ready Apr 26 08:14:37 192.168.122.209 [58227.555185] [tdb] Close table 'client0.tdb' Apr 26 08:14:37 192.168.122.209 [58227.748755] [tdb] Close table 'sessions0.tdb' Apr 26 08:14:40 192.168.122.209 [58230.958422] [tdb] Close table 'cache0.tdb' Apr 26 08:14:40 192.168.122.209 [58231.227409] [tdb] Close table 'filter0.tdb' Apr 26 08:14:40 192.168.122.209 [58231.227820] [tempesta fw] modules are stopped Apr 26 08:14:40 192.168.122.209 [58231.457447] [tempesta fw] exiting... Apr 26 08:14:41 192.168.122.209 [58231.589844] [tdb] Shutdown Tempesta DB Apr 26 08:14:41 192.168.122.209 [58231.855641] End test: http2_general.test_h2_headers.AddBackendLongHeaders.test Apr 26 08:14:41 192.168.122.209 [58231.876465] Start test: http2_general.test_h2_headers.AddBackendLongHeadersCache.test Apr 26 08:14:42 192.168.122.209 [58232.845496] [tdb] Start Tempesta DB Apr 26 08:14:42 192.168.122.209 [58232.977710] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:14:43 192.168.122.209 [58234.375249] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58234.375249] Maybe that's fine, but it's worth checking the [58234.375249] config - if there is no relations between the [58234.375249] names, then host name confusion attack is possible. Apr 26 08:14:43 192.168.122.209 [58234.445791] [tempesta fw] Configuration processing is completed. Apr 26 08:14:43 192.168.122.209 [58234.495256] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:14:44 192.168.122.209 [58234.926035] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:14:44 192.168.122.209 [58234.952673] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:14:44 192.168.122.209 [58234.978965] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:14:44 192.168.122.209 [58235.065505] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:14:44 192.168.122.209 [58235.113466] [tempesta fw] Tempesta FW is ready Apr 26 08:14:45 192.168.122.209 [58235.886686] [tdb] Close table 'client0.tdb' Apr 26 08:14:45 192.168.122.209 [58236.074563] [tdb] Close table 'sessions0.tdb' Apr 26 08:14:48 192.168.122.209 [58239.217233] [tdb] Close table 'cache0.tdb' Apr 26 08:14:48 192.168.122.209 [58239.494670] [tdb] Close table 'filter0.tdb' Apr 26 08:14:48 192.168.122.209 [58239.495100] [tempesta fw] modules are stopped Apr 26 08:14:49 192.168.122.209 [58239.710885] [tempesta fw] exiting... Apr 26 08:14:49 192.168.122.209 [58239.843423] [tdb] Shutdown Tempesta DB Apr 26 08:14:49 192.168.122.209 [58240.112364] End test: http2_general.test_h2_headers.AddBackendLongHeadersCache.test Apr 26 08:14:49 192.168.122.209 [58240.129284] Start test: http2_general.test_h2_headers.AddBackendShortHeaders.test Apr 26 08:14:50 192.168.122.209 [58241.167148] [tdb] Start Tempesta DB Apr 26 08:14:50 192.168.122.209 [58241.305122] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:14:52 192.168.122.209 [58242.799298] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58242.799298] Maybe that's fine, but it's worth checking the [58242.799298] config - if there is no relations between the [58242.799298] names, then host name confusion attack is possible. Apr 26 08:14:52 192.168.122.209 [58242.849676] [tempesta fw] Configuration processing is completed. Apr 26 08:14:52 192.168.122.209 [58242.903083] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:14:52 192.168.122.209 [58243.361760] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:14:52 192.168.122.209 [58243.391366] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:14:52 192.168.122.209 [58243.420389] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:14:52 192.168.122.209 [58243.497647] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:14:53 192.168.122.209 [58243.541557] [tempesta fw] Tempesta FW is ready Apr 26 08:14:53 192.168.122.209 [58244.327662] [tdb] Close table 'client0.tdb' Apr 26 08:14:53 192.168.122.209 [58244.512247] [tdb] Close table 'sessions0.tdb' Apr 26 08:14:57 192.168.122.209 [58247.721804] [tdb] Close table 'cache0.tdb' Apr 26 08:14:57 192.168.122.209 [58247.984481] [tdb] Close table 'filter0.tdb' Apr 26 08:14:57 192.168.122.209 [58247.984905] [tempesta fw] modules are stopped Apr 26 08:14:57 192.168.122.209 [58248.182657] [tempesta fw] exiting... Apr 26 08:14:57 192.168.122.209 [58248.313732] [tdb] Shutdown Tempesta DB Apr 26 08:14:58 192.168.122.209 [58248.590868] End test: http2_general.test_h2_headers.AddBackendShortHeaders.test Apr 26 08:14:58 192.168.122.209 [58248.603651] Start test: http2_general.test_h2_headers.AddBackendShortHeadersCache.test Apr 26 08:14:59 192.168.122.209 [58249.832090] [tdb] Start Tempesta DB Apr 26 08:14:59 192.168.122.209 [58249.966438] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:15:00 192.168.122.209 [58251.335336] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58251.335336] Maybe that's fine, but it's worth checking the [58251.335336] config - if there is no relations between the [58251.335336] names, then host name confusion attack is possible. Apr 26 08:15:00 192.168.122.209 [58251.421742] [tempesta fw] Configuration processing is completed. Apr 26 08:15:00 192.168.122.209 [58251.476313] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:15:01 192.168.122.209 [58251.901247] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:15:01 192.168.122.209 [58251.948376] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:15:01 192.168.122.209 [58251.976845] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:15:01 192.168.122.209 [58252.045729] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:15:01 192.168.122.209 [58252.089659] [tempesta fw] Tempesta FW is ready Apr 26 08:15:02 192.168.122.209 [58252.886293] [tdb] Close table 'client0.tdb' Apr 26 08:15:02 192.168.122.209 [58253.080624] [tdb] Close table 'sessions0.tdb' Apr 26 08:15:05 192.168.122.209 [58256.234445] [tdb] Close table 'cache0.tdb' Apr 26 08:15:05 192.168.122.209 [58256.455049] [tdb] Close table 'filter0.tdb' Apr 26 08:15:05 192.168.122.209 [58256.455490] [tempesta fw] modules are stopped Apr 26 08:15:06 192.168.122.209 [58256.674293] [tempesta fw] exiting... Apr 26 08:15:06 192.168.122.209 [58256.788290] [tdb] Shutdown Tempesta DB Apr 26 08:15:06 192.168.122.209 [58257.061177] End test: http2_general.test_h2_headers.AddBackendShortHeadersCache.test Apr 26 08:15:06 192.168.122.209 [58257.090048] Start test: http2_general.test_h2_headers.BackendSetCoookieH2.test Apr 26 08:15:07 192.168.122.209 [58258.269181] [tdb] Start Tempesta DB Apr 26 08:15:07 192.168.122.209 [58258.412986] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:15:09 192.168.122.209 [58259.827350] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58259.827350] Maybe that's fine, but it's worth checking the [58259.827350] config - if there is no relations between the [58259.827350] names, then host name confusion attack is possible. Apr 26 08:15:09 192.168.122.209 [58259.901969] [tempesta fw] Configuration processing is completed. Apr 26 08:15:09 192.168.122.209 [58259.950953] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:15:09 192.168.122.209 [58260.371125] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:15:09 192.168.122.209 [58260.397913] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:15:09 192.168.122.209 [58260.424508] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:15:09 192.168.122.209 [58260.513859] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:15:10 192.168.122.209 [58260.565775] [tempesta fw] Tempesta FW is ready Apr 26 08:15:10 192.168.122.209 [58261.328113] [tdb] Close table 'client0.tdb' Apr 26 08:15:10 192.168.122.209 [58261.517882] [tdb] Close table 'sessions0.tdb' Apr 26 08:15:14 192.168.122.209 [58264.764232] [tdb] Close table 'cache0.tdb' Apr 26 08:15:14 192.168.122.209 [58265.022942] [tdb] Close table 'filter0.tdb' Apr 26 08:15:14 192.168.122.209 [58265.023347] [tempesta fw] modules are stopped Apr 26 08:15:14 192.168.122.209 [58265.199829] [tempesta fw] exiting... Apr 26 08:15:14 192.168.122.209 [58265.330139] [tdb] Shutdown Tempesta DB Apr 26 08:15:15 192.168.122.209 [58265.609059] End test: http2_general.test_h2_headers.BackendSetCoookieH2.test Apr 26 08:15:15 192.168.122.209 [58265.627278] Start test: http2_general.test_h2_headers.CookieParsingH2.test_duplicate_cookie Apr 26 08:15:16 192.168.122.209 [58266.697825] [tdb] Start Tempesta DB Apr 26 08:15:16 192.168.122.209 [58266.836848] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:15:17 192.168.122.209 [58268.355182] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58268.355182] Maybe that's fine, but it's worth checking the [58268.355182] config - if there is no relations between the [58268.355182] names, then host name confusion attack is possible. Apr 26 08:15:17 192.168.122.209 [58268.485948] [tempesta fw] Configuration processing is completed. Apr 26 08:15:17 192.168.122.209 [58268.536547] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:15:18 192.168.122.209 [58268.970017] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:15:18 192.168.122.209 [58269.006086] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:15:18 192.168.122.209 [58269.033647] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:15:18 192.168.122.209 [58269.077876] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:15:18 192.168.122.209 [58269.079039] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:15:18 192.168.122.209 [58269.117871] [tempesta fw] Tempesta FW is ready Apr 26 08:15:18 192.168.122.209 [58269.340228] [tempesta fw] Warning: Multiple Tempesta sticky cookies found in request: 2 Apr 26 08:15:18 192.168.122.209 [58269.341143] [tempesta fw] Warning: request dropped: internal error in Sticky module: 127.0.0.2 Apr 26 08:15:19 192.168.122.209 [58269.756712] [tdb] Close table 'client0.tdb' Apr 26 08:15:19 192.168.122.209 [58269.948449] [tdb] Close table 'sessions0.tdb' Apr 26 08:15:22 192.168.122.209 [58273.102292] [tdb] Close table 'cache0.tdb' Apr 26 08:15:22 192.168.122.209 [58273.364215] [tdb] Close table 'filter0.tdb' Apr 26 08:15:22 192.168.122.209 [58273.364650] [tempesta fw] modules are stopped Apr 26 08:15:23 192.168.122.209 [58273.557508] [tempesta fw] exiting... Apr 26 08:15:23 192.168.122.209 [58273.684032] [tdb] Shutdown Tempesta DB Apr 26 08:15:23 192.168.122.209 [58273.919527] End test: http2_general.test_h2_headers.CookieParsingH2.test_duplicate_cookie Apr 26 08:15:23 192.168.122.209 [58273.936250] Start test: http2_general.test_h2_headers.CookieParsingH2.test_many_cookie_and_name_as_substring_other_name_1 Apr 26 08:15:24 192.168.122.209 [58274.961062] [tdb] Start Tempesta DB Apr 26 08:15:24 192.168.122.209 [58275.100803] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:15:26 192.168.122.209 [58276.547323] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58276.547323] Maybe that's fine, but it's worth checking the [58276.547323] config - if there is no relations between the [58276.547323] names, then host name confusion attack is possible. Apr 26 08:15:26 192.168.122.209 [58276.678060] [tempesta fw] Configuration processing is completed. Apr 26 08:15:26 192.168.122.209 [58276.727974] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:15:26 192.168.122.209 [58277.148852] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:15:26 192.168.122.209 [58277.177009] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:15:26 192.168.122.209 [58277.204267] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:15:26 192.168.122.209 [58277.245984] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:15:26 192.168.122.209 [58277.247098] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:15:26 192.168.122.209 [58277.289973] [tempesta fw] Tempesta FW is ready Apr 26 08:15:27 192.168.122.209 [58277.952549] [tdb] Close table 'client0.tdb' Apr 26 08:15:27 192.168.122.209 [58278.161929] [tdb] Close table 'sessions0.tdb' Apr 26 08:15:30 192.168.122.209 [58281.386313] [tdb] Close table 'cache0.tdb' Apr 26 08:15:31 192.168.122.209 [58281.612509] [tdb] Close table 'filter0.tdb' Apr 26 08:15:31 192.168.122.209 [58281.612955] [tempesta fw] modules are stopped Apr 26 08:15:31 192.168.122.209 [58281.817500] [tempesta fw] exiting... Apr 26 08:15:31 192.168.122.209 [58281.953508] [tdb] Shutdown Tempesta DB Apr 26 08:15:31 192.168.122.209 [58282.175193] End test: http2_general.test_h2_headers.CookieParsingH2.test_many_cookie_and_name_as_substring_other_name_1 Apr 26 08:15:31 192.168.122.209 [58282.188785] Start test: http2_general.test_h2_headers.CookieParsingH2.test_many_cookie_and_name_as_substring_other_name_2 Apr 26 08:15:32 192.168.122.209 [58283.315635] [tdb] Start Tempesta DB Apr 26 08:15:32 192.168.122.209 [58283.466445] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:15:34 192.168.122.209 [58284.991399] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58284.991399] Maybe that's fine, but it's worth checking the [58284.991399] config - if there is no relations between the [58284.991399] names, then host name confusion attack is possible. Apr 26 08:15:34 192.168.122.209 [58285.154227] [tempesta fw] Configuration processing is completed. Apr 26 08:15:34 192.168.122.209 [58285.204736] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:15:35 192.168.122.209 [58285.634958] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:15:35 192.168.122.209 [58285.662386] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:15:35 192.168.122.209 [58285.690581] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:15:35 192.168.122.209 [58285.746134] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:15:35 192.168.122.209 [58285.747746] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:15:35 192.168.122.209 [58285.794095] [tempesta fw] Tempesta FW is ready Apr 26 08:15:35 192.168.122.209 [58286.453684] [tdb] Close table 'client0.tdb' Apr 26 08:15:36 192.168.122.209 [58286.642459] [tdb] Close table 'sessions0.tdb' Apr 26 08:15:39 192.168.122.209 [58289.907196] [tdb] Close table 'cache0.tdb' Apr 26 08:15:39 192.168.122.209 [58290.175703] [tdb] Close table 'filter0.tdb' Apr 26 08:15:39 192.168.122.209 [58290.176130] [tempesta fw] modules are stopped Apr 26 08:15:39 192.168.122.209 [58290.359735] [tempesta fw] exiting... Apr 26 08:15:39 192.168.122.209 [58290.503865] [tdb] Shutdown Tempesta DB Apr 26 08:15:40 192.168.122.209 [58290.716245] End test: http2_general.test_h2_headers.CookieParsingH2.test_many_cookie_and_name_as_substring_other_name_2 Apr 26 08:15:40 192.168.122.209 [58290.737649] Start test: http2_general.test_h2_headers.CookieParsingH2.test_many_cookie_and_name_as_substring_other_value_1 Apr 26 08:15:41 192.168.122.209 [58291.787797] [tdb] Start Tempesta DB Apr 26 08:15:41 192.168.122.209 [58291.944886] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:15:42 192.168.122.209 [58293.386896] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58293.386896] Maybe that's fine, but it's worth checking the [58293.386896] config - if there is no relations between the [58293.386896] names, then host name confusion attack is possible. Apr 26 08:15:42 192.168.122.209 [58293.522461] [tempesta fw] Configuration processing is completed. Apr 26 08:15:43 192.168.122.209 [58293.577387] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:15:43 192.168.122.209 [58294.076585] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:15:43 192.168.122.209 [58294.109485] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:15:43 192.168.122.209 [58294.143782] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:15:43 192.168.122.209 [58294.194250] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:15:43 192.168.122.209 [58294.195689] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:15:43 192.168.122.209 [58294.234202] [tempesta fw] Tempesta FW is ready Apr 26 08:15:44 192.168.122.209 [58294.866345] [tdb] Close table 'client0.tdb' Apr 26 08:15:44 192.168.122.209 [58295.052661] [tdb] Close table 'sessions0.tdb' Apr 26 08:15:47 192.168.122.209 [58298.364953] [tdb] Close table 'cache0.tdb' Apr 26 08:15:48 192.168.122.209 [58298.636987] [tdb] Close table 'filter0.tdb' Apr 26 08:15:48 192.168.122.209 [58298.637416] [tempesta fw] modules are stopped Apr 26 08:15:48 192.168.122.209 [58298.819081] [tempesta fw] exiting... Apr 26 08:15:48 192.168.122.209 [58298.945535] [tdb] Shutdown Tempesta DB Apr 26 08:15:48 192.168.122.209 [58299.193894] End test: http2_general.test_h2_headers.CookieParsingH2.test_many_cookie_and_name_as_substring_other_value_1 Apr 26 08:15:48 192.168.122.209 [58299.205680] Start test: http2_general.test_h2_headers.CookieParsingH2.test_many_cookie_and_name_as_substring_other_value_2 Apr 26 08:15:49 192.168.122.209 [58300.316825] [tdb] Start Tempesta DB Apr 26 08:15:49 192.168.122.209 [58300.460099] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:15:51 192.168.122.209 [58301.927707] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58301.927707] Maybe that's fine, but it's worth checking the [58301.927707] config - if there is no relations between the [58301.927707] names, then host name confusion attack is possible. Apr 26 08:15:51 192.168.122.209 [58302.086411] [tempesta fw] Configuration processing is completed. Apr 26 08:15:51 192.168.122.209 [58302.148743] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:15:52 192.168.122.209 [58302.645841] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:15:52 192.168.122.209 [58302.680705] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:15:52 192.168.122.209 [58302.718603] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:15:52 192.168.122.209 [58302.762354] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:15:52 192.168.122.209 [58302.764097] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:15:52 192.168.122.209 [58302.806297] [tempesta fw] Tempesta FW is ready Apr 26 08:15:52 192.168.122.209 [58303.470985] [tdb] Close table 'client0.tdb' Apr 26 08:15:53 192.168.122.209 [58303.682915] [tdb] Close table 'sessions0.tdb' Apr 26 08:15:56 192.168.122.209 [58306.985234] [tdb] Close table 'cache0.tdb' Apr 26 08:15:56 192.168.122.209 [58307.246805] [tdb] Close table 'filter0.tdb' Apr 26 08:15:56 192.168.122.209 [58307.247243] [tempesta fw] modules are stopped Apr 26 08:15:56 192.168.122.209 [58307.448309] [tempesta fw] exiting... Apr 26 08:15:57 192.168.122.209 [58307.593402] [tdb] Shutdown Tempesta DB Apr 26 08:15:57 192.168.122.209 [58307.807264] End test: http2_general.test_h2_headers.CookieParsingH2.test_many_cookie_and_name_as_substring_other_value_2 Apr 26 08:15:57 192.168.122.209 [58307.823847] Start test: http2_general.test_h2_headers.CookieParsingH2.test_many_cookie_between Apr 26 08:15:58 192.168.122.209 [58308.836133] [tdb] Start Tempesta DB Apr 26 08:15:58 192.168.122.209 [58308.987042] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:15:59 192.168.122.209 [58310.499352] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58310.499352] Maybe that's fine, but it's worth checking the [58310.499352] config - if there is no relations between the [58310.499352] names, then host name confusion attack is possible. Apr 26 08:16:00 192.168.122.209 [58310.630502] [tempesta fw] Configuration processing is completed. Apr 26 08:16:00 192.168.122.209 [58310.680764] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:16:00 192.168.122.209 [58311.115401] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:16:00 192.168.122.209 [58311.143849] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:16:00 192.168.122.209 [58311.173109] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:16:00 192.168.122.209 [58311.214474] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:16:00 192.168.122.209 [58311.216194] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:16:00 192.168.122.209 [58311.262399] [tempesta fw] Tempesta FW is ready Apr 26 08:16:01 192.168.122.209 [58311.917308] [tdb] Close table 'client0.tdb' Apr 26 08:16:01 192.168.122.209 [58312.110688] [tdb] Close table 'sessions0.tdb' Apr 26 08:16:04 192.168.122.209 [58315.333607] [tdb] Close table 'cache0.tdb' Apr 26 08:16:05 192.168.122.209 [58315.575471] [tdb] Close table 'filter0.tdb' Apr 26 08:16:05 192.168.122.209 [58315.575925] [tempesta fw] modules are stopped Apr 26 08:16:05 192.168.122.209 [58315.763761] [tempesta fw] exiting... Apr 26 08:16:05 192.168.122.209 [58315.886989] [tdb] Shutdown Tempesta DB Apr 26 08:16:05 192.168.122.209 [58316.092122] End test: http2_general.test_h2_headers.CookieParsingH2.test_many_cookie_between Apr 26 08:16:05 192.168.122.209 [58316.104565] Start test: http2_general.test_h2_headers.CookieParsingH2.test_many_cookie_first Apr 26 08:16:06 192.168.122.209 [58317.164447] [tdb] Start Tempesta DB Apr 26 08:16:06 192.168.122.209 [58317.312100] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:16:08 192.168.122.209 [58318.795842] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58318.795842] Maybe that's fine, but it's worth checking the [58318.795842] config - if there is no relations between the [58318.795842] names, then host name confusion attack is possible. Apr 26 08:16:08 192.168.122.209 [58318.934619] [tempesta fw] Configuration processing is completed. Apr 26 08:16:08 192.168.122.209 [58318.989975] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:16:08 192.168.122.209 [58319.430171] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:16:08 192.168.122.209 [58319.458004] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:16:08 192.168.122.209 [58319.485205] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:16:08 192.168.122.209 [58319.534557] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:16:08 192.168.122.209 [58319.536226] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:16:09 192.168.122.209 [58319.582521] [tempesta fw] Tempesta FW is ready Apr 26 08:16:09 192.168.122.209 [58320.217640] [tdb] Close table 'client0.tdb' Apr 26 08:16:09 192.168.122.209 [58320.406734] [tdb] Close table 'sessions0.tdb' Apr 26 08:16:13 192.168.122.209 [58323.611107] [tdb] Close table 'cache0.tdb' Apr 26 08:16:13 192.168.122.209 [58323.846573] [tdb] Close table 'filter0.tdb' Apr 26 08:16:13 192.168.122.209 [58323.847007] [tempesta fw] modules are stopped Apr 26 08:16:13 192.168.122.209 [58324.035122] [tempesta fw] exiting... Apr 26 08:16:13 192.168.122.209 [58324.153363] [tdb] Shutdown Tempesta DB Apr 26 08:16:13 192.168.122.209 [58324.378581] End test: http2_general.test_h2_headers.CookieParsingH2.test_many_cookie_first Apr 26 08:16:13 192.168.122.209 [58324.398284] Start test: http2_general.test_h2_headers.CookieParsingH2.test_many_cookie_last Apr 26 08:16:14 192.168.122.209 [58325.446900] [tdb] Start Tempesta DB Apr 26 08:16:15 192.168.122.209 [58325.596273] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:16:16 192.168.122.209 [58327.067930] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58327.067930] Maybe that's fine, but it's worth checking the [58327.067930] config - if there is no relations between the [58327.067930] names, then host name confusion attack is possible. Apr 26 08:16:16 192.168.122.209 [58327.222692] [tempesta fw] Configuration processing is completed. Apr 26 08:16:16 192.168.122.209 [58327.272957] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:16:17 192.168.122.209 [58327.696457] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:16:17 192.168.122.209 [58327.725244] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:16:17 192.168.122.209 [58327.753305] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:16:17 192.168.122.209 [58327.798676] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:16:17 192.168.122.209 [58327.800378] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:16:17 192.168.122.209 [58327.854610] [tempesta fw] Tempesta FW is ready Apr 26 08:16:18 192.168.122.209 [58328.547714] [tdb] Close table 'client0.tdb' Apr 26 08:16:18 192.168.122.209 [58328.745228] [tdb] Close table 'sessions0.tdb' Apr 26 08:16:21 192.168.122.209 [58331.905095] [tdb] Close table 'cache0.tdb' Apr 26 08:16:21 192.168.122.209 [58332.141966] [tdb] Close table 'filter0.tdb' Apr 26 08:16:21 192.168.122.209 [58332.142391] [tempesta fw] modules are stopped Apr 26 08:16:21 192.168.122.209 [58332.377727] [tempesta fw] exiting... Apr 26 08:16:21 192.168.122.209 [58332.498859] [tdb] Shutdown Tempesta DB Apr 26 08:16:22 192.168.122.209 [58332.694675] End test: http2_general.test_h2_headers.CookieParsingH2.test_many_cookie_last Apr 26 08:16:22 192.168.122.209 [58332.724990] Start test: http2_general.test_h2_headers.CookieParsingH2.test_single_cookie Apr 26 08:16:23 192.168.122.209 [58333.795973] [tdb] Start Tempesta DB Apr 26 08:16:23 192.168.122.209 [58333.937821] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:16:24 192.168.122.209 [58335.436052] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58335.436052] Maybe that's fine, but it's worth checking the [58335.436052] config - if there is no relations between the [58335.436052] names, then host name confusion attack is possible. Apr 26 08:16:25 192.168.122.209 [58335.578786] [tempesta fw] Configuration processing is completed. Apr 26 08:16:25 192.168.122.209 [58335.628646] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:16:25 192.168.122.209 [58336.043535] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:16:25 192.168.122.209 [58336.070602] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:16:25 192.168.122.209 [58336.097811] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:16:25 192.168.122.209 [58336.146799] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:16:25 192.168.122.209 [58336.148519] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:16:25 192.168.122.209 [58336.190734] [tempesta fw] Tempesta FW is ready Apr 26 08:16:26 192.168.122.209 [58336.863428] [tdb] Close table 'client0.tdb' Apr 26 08:16:26 192.168.122.209 [58337.070527] [tdb] Close table 'sessions0.tdb' Apr 26 08:16:29 192.168.122.209 [58340.251471] [tdb] Close table 'cache0.tdb' Apr 26 08:16:29 192.168.122.209 [58340.506848] [tdb] Close table 'filter0.tdb' Apr 26 08:16:29 192.168.122.209 [58340.507298] [tempesta fw] modules are stopped Apr 26 08:16:30 192.168.122.209 [58340.712297] [tempesta fw] exiting... Apr 26 08:16:30 192.168.122.209 [58340.836195] [tdb] Shutdown Tempesta DB Apr 26 08:16:30 192.168.122.209 [58341.053361] End test: http2_general.test_h2_headers.CookieParsingH2.test_single_cookie Apr 26 08:16:30 192.168.122.209 [58341.064426] Start test: http2_general.test_h2_headers.CookieParsingHttp.test_duplicate_cookie Apr 26 08:16:31 192.168.122.209 [58342.038145] [tdb] Start Tempesta DB Apr 26 08:16:31 192.168.122.209 [58342.183807] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:16:33 192.168.122.209 [58343.692214] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58343.692214] Maybe that's fine, but it's worth checking the [58343.692214] config - if there is no relations between the [58343.692214] names, then host name confusion attack is possible. Apr 26 08:16:33 192.168.122.209 [58343.831044] [tempesta fw] Configuration processing is completed. Apr 26 08:16:33 192.168.122.209 [58343.881585] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:16:33 192.168.122.209 [58344.298000] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:16:33 192.168.122.209 [58344.324696] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:16:33 192.168.122.209 [58344.351433] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:16:33 192.168.122.209 [58344.390876] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:16:33 192.168.122.209 [58344.392631] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:16:33 192.168.122.209 [58344.438816] [tempesta fw] Tempesta FW is ready Apr 26 08:16:34 192.168.122.209 [58344.606109] [tempesta fw] Warning: Multiple Tempesta sticky cookies found in request: 2 Apr 26 08:16:34 192.168.122.209 [58344.606855] [tempesta fw] Warning: request dropped: internal error in Sticky module: 127.0.0.2 Apr 26 08:16:34 192.168.122.209 [58345.032490] [tdb] Close table 'client0.tdb' Apr 26 08:16:34 192.168.122.209 [58345.225440] [tdb] Close table 'sessions0.tdb' Apr 26 08:16:37 192.168.122.209 [58348.409235] [tdb] Close table 'cache0.tdb' Apr 26 08:16:38 192.168.122.209 [58348.650702] [tdb] Close table 'filter0.tdb' Apr 26 08:16:38 192.168.122.209 [58348.651153] [tempesta fw] modules are stopped Apr 26 08:16:38 192.168.122.209 [58348.851338] [tempesta fw] exiting... Apr 26 08:16:38 192.168.122.209 [58348.976926] [tdb] Shutdown Tempesta DB Apr 26 08:16:38 192.168.122.209 [58349.186540] End test: http2_general.test_h2_headers.CookieParsingHttp.test_duplicate_cookie Apr 26 08:16:38 192.168.122.209 [58349.204625] Start test: http2_general.test_h2_headers.CookieParsingHttp.test_many_cookie_and_name_as_substring_other_name_1 Apr 26 08:16:39 192.168.122.209 [58350.246564] [tdb] Start Tempesta DB Apr 26 08:16:39 192.168.122.209 [58350.386115] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:16:41 192.168.122.209 [58351.860235] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58351.860235] Maybe that's fine, but it's worth checking the [58351.860235] config - if there is no relations between the [58351.860235] names, then host name confusion attack is possible. Apr 26 08:16:41 192.168.122.209 [58352.011314] [tempesta fw] Configuration processing is completed. Apr 26 08:16:41 192.168.122.209 [58352.065814] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:16:41 192.168.122.209 [58352.486092] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:16:41 192.168.122.209 [58352.513792] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:16:42 192.168.122.209 [58352.540525] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:16:42 192.168.122.209 [58352.591001] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:16:42 192.168.122.209 [58352.591122] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:16:42 192.168.122.209 [58352.638926] [tempesta fw] Tempesta FW is ready Apr 26 08:16:42 192.168.122.209 [58353.253478] [tdb] Close table 'client0.tdb' Apr 26 08:16:42 192.168.122.209 [58353.439533] [tdb] Close table 'sessions0.tdb' Apr 26 08:16:46 192.168.122.209 [58356.683568] [tdb] Close table 'cache0.tdb' Apr 26 08:16:46 192.168.122.209 [58356.942512] [tdb] Close table 'filter0.tdb' Apr 26 08:16:46 192.168.122.209 [58356.943567] [tempesta fw] modules are stopped Apr 26 08:16:46 192.168.122.209 [58357.132439] [tempesta fw] exiting... Apr 26 08:16:46 192.168.122.209 [58357.264468] [tdb] Shutdown Tempesta DB Apr 26 08:16:46 192.168.122.209 [58357.475969] End test: http2_general.test_h2_headers.CookieParsingHttp.test_many_cookie_and_name_as_substring_other_name_1 Apr 26 08:16:46 192.168.122.209 [58357.495176] Start test: http2_general.test_h2_headers.CookieParsingHttp.test_many_cookie_and_name_as_substring_other_name_2 Apr 26 08:16:48 192.168.122.209 [58358.546164] [tdb] Start Tempesta DB Apr 26 08:16:48 192.168.122.209 [58358.699722] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:16:49 192.168.122.209 [58360.184475] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58360.184475] Maybe that's fine, but it's worth checking the [58360.184475] config - if there is no relations between the [58360.184475] names, then host name confusion attack is possible. Apr 26 08:16:49 192.168.122.209 [58360.311160] [tempesta fw] Configuration processing is completed. Apr 26 08:16:49 192.168.122.209 [58360.363286] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:16:50 192.168.122.209 [58360.785224] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:16:50 192.168.122.209 [58360.812348] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:16:50 192.168.122.209 [58360.838990] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:16:50 192.168.122.209 [58360.927087] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:16:50 192.168.122.209 [58360.928855] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:16:50 192.168.122.209 [58360.967051] [tempesta fw] Tempesta FW is ready Apr 26 08:16:51 192.168.122.209 [58361.610192] [tdb] Close table 'client0.tdb' Apr 26 08:16:51 192.168.122.209 [58361.794073] [tdb] Close table 'sessions0.tdb' Apr 26 08:16:54 192.168.122.209 [58364.943908] [tdb] Close table 'cache0.tdb' Apr 26 08:16:54 192.168.122.209 [58365.193985] [tdb] Close table 'filter0.tdb' Apr 26 08:16:54 192.168.122.209 [58365.194424] [tempesta fw] modules are stopped Apr 26 08:16:54 192.168.122.209 [58365.375322] [tempesta fw] exiting... Apr 26 08:16:54 192.168.122.209 [58365.506998] [tdb] Shutdown Tempesta DB Apr 26 08:16:55 192.168.122.209 [58365.749092] End test: http2_general.test_h2_headers.CookieParsingHttp.test_many_cookie_and_name_as_substring_other_name_2 Apr 26 08:16:55 192.168.122.209 [58365.764451] Start test: http2_general.test_h2_headers.CookieParsingHttp.test_many_cookie_and_name_as_substring_other_value_1 Apr 26 08:16:56 192.168.122.209 [58366.882465] [tdb] Start Tempesta DB Apr 26 08:16:56 192.168.122.209 [58367.018932] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:16:57 192.168.122.209 [58368.508463] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58368.508463] Maybe that's fine, but it's worth checking the [58368.508463] config - if there is no relations between the [58368.508463] names, then host name confusion attack is possible. Apr 26 08:16:58 192.168.122.209 [58368.655207] [tempesta fw] Configuration processing is completed. Apr 26 08:16:58 192.168.122.209 [58368.706151] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:16:58 192.168.122.209 [58369.128122] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:16:58 192.168.122.209 [58369.155167] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:16:58 192.168.122.209 [58369.182207] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:16:58 192.168.122.209 [58369.231215] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:16:58 192.168.122.209 [58369.232929] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:16:58 192.168.122.209 [58369.279144] [tempesta fw] Tempesta FW is ready Apr 26 08:16:59 192.168.122.209 [58369.915714] [tdb] Close table 'client0.tdb' Apr 26 08:16:59 192.168.122.209 [58370.103836] [tdb] Close table 'sessions0.tdb' Apr 26 08:17:02 192.168.122.209 [58373.322728] [tdb] Close table 'cache0.tdb' Apr 26 08:17:03 192.168.122.209 [58373.569233] [tdb] Close table 'filter0.tdb' Apr 26 08:17:03 192.168.122.209 [58373.569654] [tempesta fw] modules are stopped Apr 26 08:17:03 192.168.122.209 [58373.763103] [tempesta fw] exiting... Apr 26 08:17:03 192.168.122.209 [58373.873935] [tdb] Shutdown Tempesta DB Apr 26 08:17:03 192.168.122.209 [58374.085633] End test: http2_general.test_h2_headers.CookieParsingHttp.test_many_cookie_and_name_as_substring_other_value_1 Apr 26 08:17:03 192.168.122.209 [58374.109053] Start test: http2_general.test_h2_headers.CookieParsingHttp.test_many_cookie_and_name_as_substring_other_value_2 Apr 26 08:17:04 192.168.122.209 [58375.194453] [tdb] Start Tempesta DB Apr 26 08:17:04 192.168.122.209 [58375.339895] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:17:06 192.168.122.209 [58376.820554] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58376.820554] Maybe that's fine, but it's worth checking the [58376.820554] config - if there is no relations between the [58376.820554] names, then host name confusion attack is possible. Apr 26 08:17:06 192.168.122.209 [58376.955311] [tempesta fw] Configuration processing is completed. Apr 26 08:17:06 192.168.122.209 [58377.009265] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:17:06 192.168.122.209 [58377.432731] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:17:06 192.168.122.209 [58377.459941] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:17:06 192.168.122.209 [58377.487379] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:17:07 192.168.122.209 [58377.543277] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:17:07 192.168.122.209 [58377.544659] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:17:07 192.168.122.209 [58377.591254] [tempesta fw] Tempesta FW is ready Apr 26 08:17:07 192.168.122.209 [58378.191569] [tdb] Close table 'client0.tdb' Apr 26 08:17:07 192.168.122.209 [58378.377092] [tdb] Close table 'sessions0.tdb' Apr 26 08:17:11 192.168.122.209 [58381.540006] [tdb] Close table 'cache0.tdb' Apr 26 08:17:11 192.168.122.209 [58381.762589] [tdb] Close table 'filter0.tdb' Apr 26 08:17:11 192.168.122.209 [58381.763019] [tempesta fw] modules are stopped Apr 26 08:17:11 192.168.122.209 [58382.015781] [tempesta fw] exiting... Apr 26 08:17:11 192.168.122.209 [58382.122624] [tdb] Shutdown Tempesta DB Apr 26 08:17:11 192.168.122.209 [58382.331991] End test: http2_general.test_h2_headers.CookieParsingHttp.test_many_cookie_and_name_as_substring_other_value_2 Apr 26 08:17:11 192.168.122.209 [58382.352707] Start test: http2_general.test_h2_headers.CookieParsingHttp.test_many_cookie_between Apr 26 08:17:12 192.168.122.209 [58383.468942] [tdb] Start Tempesta DB Apr 26 08:17:13 192.168.122.209 [58383.598098] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:17:14 192.168.122.209 [58385.091874] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58385.091874] Maybe that's fine, but it's worth checking the [58385.091874] config - if there is no relations between the [58385.091874] names, then host name confusion attack is possible. Apr 26 08:17:14 192.168.122.209 [58385.211736] [tempesta fw] Configuration processing is completed. Apr 26 08:17:14 192.168.122.209 [58385.262052] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:17:15 192.168.122.209 [58385.679005] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:17:15 192.168.122.209 [58385.705724] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:17:15 192.168.122.209 [58385.732446] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:17:15 192.168.122.209 [58385.775337] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:17:15 192.168.122.209 [58385.776450] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:17:15 192.168.122.209 [58385.819335] [tempesta fw] Tempesta FW is ready Apr 26 08:17:15 192.168.122.209 [58386.452942] [tdb] Close table 'client0.tdb' Apr 26 08:17:16 192.168.122.209 [58386.637814] [tdb] Close table 'sessions0.tdb' Apr 26 08:17:19 192.168.122.209 [58389.807658] [tdb] Close table 'cache0.tdb' Apr 26 08:17:19 192.168.122.209 [58390.058642] [tdb] Close table 'filter0.tdb' Apr 26 08:17:19 192.168.122.209 [58390.059094] [tempesta fw] modules are stopped Apr 26 08:17:19 192.168.122.209 [58390.293408] [tempesta fw] exiting... Apr 26 08:17:19 192.168.122.209 [58390.410984] [tdb] Shutdown Tempesta DB Apr 26 08:17:20 192.168.122.209 [58390.644644] End test: http2_general.test_h2_headers.CookieParsingHttp.test_many_cookie_between Apr 26 08:17:20 192.168.122.209 [58390.658152] Start test: http2_general.test_h2_headers.CookieParsingHttp.test_many_cookie_first Apr 26 08:17:21 192.168.122.209 [58391.735401] [tdb] Start Tempesta DB Apr 26 08:17:21 192.168.122.209 [58391.892212] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:17:22 192.168.122.209 [58393.328751] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58393.328751] Maybe that's fine, but it's worth checking the [58393.328751] config - if there is no relations between the [58393.328751] names, then host name confusion attack is possible. Apr 26 08:17:22 192.168.122.209 [58393.459474] [tempesta fw] Configuration processing is completed. Apr 26 08:17:22 192.168.122.209 [58393.517204] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:17:23 192.168.122.209 [58393.943204] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:17:23 192.168.122.209 [58393.970797] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:17:23 192.168.122.209 [58393.999444] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:17:23 192.168.122.209 [58394.083526] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:17:23 192.168.122.209 [58394.085307] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:17:23 192.168.122.209 [58394.123442] [tempesta fw] Tempesta FW is ready Apr 26 08:17:24 192.168.122.209 [58394.741063] [tdb] Close table 'client0.tdb' Apr 26 08:17:24 192.168.122.209 [58394.929625] [tdb] Close table 'sessions0.tdb' Apr 26 08:17:27 192.168.122.209 [58398.099971] [tdb] Close table 'cache0.tdb' Apr 26 08:17:27 192.168.122.209 [58398.321494] [tdb] Close table 'filter0.tdb' Apr 26 08:17:27 192.168.122.209 [58398.321915] [tempesta fw] modules are stopped Apr 26 08:17:27 192.168.122.209 [58398.533242] [tempesta fw] exiting... Apr 26 08:17:28 192.168.122.209 [58398.642411] [tdb] Shutdown Tempesta DB Apr 26 08:17:28 192.168.122.209 [58398.862750] End test: http2_general.test_h2_headers.CookieParsingHttp.test_many_cookie_first Apr 26 08:17:28 192.168.122.209 [58398.873544] Start test: http2_general.test_h2_headers.CookieParsingHttp.test_many_cookie_last Apr 26 08:17:29 192.168.122.209 [58399.912422] [tdb] Start Tempesta DB Apr 26 08:17:29 192.168.122.209 [58400.051338] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:17:30 192.168.122.209 [58401.480886] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58401.480886] Maybe that's fine, but it's worth checking the [58401.480886] config - if there is no relations between the [58401.480886] names, then host name confusion attack is possible. Apr 26 08:17:31 192.168.122.209 [58401.611656] [tempesta fw] Configuration processing is completed. Apr 26 08:17:31 192.168.122.209 [58401.662310] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:17:31 192.168.122.209 [58402.076541] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:17:31 192.168.122.209 [58402.103104] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:17:31 192.168.122.209 [58402.130560] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:17:31 192.168.122.209 [58402.171610] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:17:31 192.168.122.209 [58402.173332] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:17:31 192.168.122.209 [58402.219559] [tempesta fw] Tempesta FW is ready Apr 26 08:17:32 192.168.122.209 [58402.828620] [tdb] Close table 'client0.tdb' Apr 26 08:17:32 192.168.122.209 [58403.032656] [tdb] Close table 'sessions0.tdb' Apr 26 08:17:35 192.168.122.209 [58406.255692] [tdb] Close table 'cache0.tdb' Apr 26 08:17:35 192.168.122.209 [58406.498352] [tdb] Close table 'filter0.tdb' Apr 26 08:17:35 192.168.122.209 [58406.498789] [tempesta fw] modules are stopped Apr 26 08:17:36 192.168.122.209 [58406.681557] [tempesta fw] exiting... Apr 26 08:17:36 192.168.122.209 [58406.805990] [tdb] Shutdown Tempesta DB Apr 26 08:17:36 192.168.122.209 [58407.015000] End test: http2_general.test_h2_headers.CookieParsingHttp.test_many_cookie_last Apr 26 08:17:36 192.168.122.209 [58407.038662] Start test: http2_general.test_h2_headers.CookieParsingHttp.test_single_cookie Apr 26 08:17:37 192.168.122.209 [58408.143008] [tdb] Start Tempesta DB Apr 26 08:17:37 192.168.122.209 [58408.273428] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:17:39 192.168.122.209 [58409.664707] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58409.664707] Maybe that's fine, but it's worth checking the [58409.664707] config - if there is no relations between the [58409.664707] names, then host name confusion attack is possible. Apr 26 08:17:39 192.168.122.209 [58409.803678] [tempesta fw] Configuration processing is completed. Apr 26 08:17:39 192.168.122.209 [58409.853533] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:17:39 192.168.122.209 [58410.298108] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:17:39 192.168.122.209 [58410.324899] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:17:39 192.168.122.209 [58410.351842] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:17:39 192.168.122.209 [58410.391649] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:17:39 192.168.122.209 [58410.392674] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:17:39 192.168.122.209 [58410.435644] [tempesta fw] Tempesta FW is ready Apr 26 08:17:40 192.168.122.209 [58411.073644] [tdb] Close table 'client0.tdb' Apr 26 08:17:40 192.168.122.209 [58411.265296] [tdb] Close table 'sessions0.tdb' Apr 26 08:17:43 192.168.122.209 [58414.456014] [tdb] Close table 'cache0.tdb' Apr 26 08:17:44 192.168.122.209 [58414.681711] [tdb] Close table 'filter0.tdb' Apr 26 08:17:44 192.168.122.209 [58414.682139] [tempesta fw] modules are stopped Apr 26 08:17:44 192.168.122.209 [58414.907295] [tempesta fw] exiting... Apr 26 08:17:44 192.168.122.209 [58415.013968] [tdb] Shutdown Tempesta DB Apr 26 08:17:44 192.168.122.209 [58415.253281] End test: http2_general.test_h2_headers.CookieParsingHttp.test_single_cookie Apr 26 08:17:44 192.168.122.209 [58415.268764] Start test: http2_general.test_h2_headers.DuplicateSingularHeader.test_header_as_string_value Apr 26 08:17:45 192.168.122.209 [58416.367878] [tdb] Start Tempesta DB Apr 26 08:17:45 192.168.122.209 [58416.494917] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:17:47 192.168.122.209 [58418.121225] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58418.121225] Maybe that's fine, but it's worth checking the [58418.121225] config - if there is no relations between the [58418.121225] names, then host name confusion attack is possible. Apr 26 08:17:47 192.168.122.209 [58418.283813] [tempesta fw] Configuration processing is completed. Apr 26 08:17:47 192.168.122.209 [58418.334260] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:17:48 192.168.122.209 [58418.749726] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:17:48 192.168.122.209 [58418.777007] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:17:48 192.168.122.209 [58418.803909] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:17:48 192.168.122.209 [58418.859715] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:17:48 192.168.122.209 [58418.907775] [tempesta fw] Tempesta FW is ready Apr 26 08:17:48 192.168.122.209 [58419.117832] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrRefererV input=0x74('t'), len=1, off=0 Apr 26 08:17:49 192.168.122.209 [58419.571093] [tdb] Close table 'client0.tdb' Apr 26 08:17:49 192.168.122.209 [58419.772265] [tdb] Close table 'sessions0.tdb' Apr 26 08:17:52 192.168.122.209 [58422.953114] [tdb] Close table 'cache0.tdb' Apr 26 08:17:52 192.168.122.209 [58423.180786] [tdb] Close table 'filter0.tdb' Apr 26 08:17:52 192.168.122.209 [58423.181216] [tempesta fw] modules are stopped Apr 26 08:17:52 192.168.122.209 [58423.455731] [tempesta fw] exiting... Apr 26 08:17:53 192.168.122.209 [58423.580323] [tdb] Shutdown Tempesta DB Apr 26 08:17:53 192.168.122.209 [58423.805527] End test: http2_general.test_h2_headers.DuplicateSingularHeader.test_header_as_string_value Apr 26 08:17:53 192.168.122.209 [58423.827432] Start test: http2_general.test_h2_headers.DuplicateSingularHeader.test_header_from_static_table_and_dynamic_table Apr 26 08:17:54 192.168.122.209 [58424.868996] [tdb] Start Tempesta DB Apr 26 08:17:54 192.168.122.209 [58425.010296] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:17:56 192.168.122.209 [58426.597332] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58426.597332] Maybe that's fine, but it's worth checking the [58426.597332] config - if there is no relations between the [58426.597332] names, then host name confusion attack is possible. Apr 26 08:17:56 192.168.122.209 [58426.747937] [tempesta fw] Configuration processing is completed. Apr 26 08:17:56 192.168.122.209 [58426.801981] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:17:56 192.168.122.209 [58427.222472] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:17:56 192.168.122.209 [58427.249778] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:17:56 192.168.122.209 [58427.276819] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:17:56 192.168.122.209 [58427.395951] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:17:56 192.168.122.209 [58427.443864] [tempesta fw] Tempesta FW is ready Apr 26 08:17:57 192.168.122.209 [58428.037423] [tdb] Close table 'client0.tdb' Apr 26 08:17:57 192.168.122.209 [58428.243900] [tdb] Close table 'sessions0.tdb' Apr 26 08:18:00 192.168.122.209 [58431.437667] [tdb] Close table 'cache0.tdb' Apr 26 08:18:01 192.168.122.209 [58431.685775] [tdb] Close table 'filter0.tdb' Apr 26 08:18:01 192.168.122.209 [58431.686195] [tempesta fw] modules are stopped Apr 26 08:18:01 192.168.122.209 [58431.920576] [tempesta fw] exiting... Apr 26 08:18:01 192.168.122.209 [58432.042585] [tdb] Shutdown Tempesta DB Apr 26 08:18:01 192.168.122.209 [58432.259846] End test: http2_general.test_h2_headers.DuplicateSingularHeader.test_header_from_static_table_and_dynamic_table Apr 26 08:18:01 192.168.122.209 [58432.272825] Start test: http2_general.test_h2_headers.DuplicateSingularHeader.test_two_header_as_bytes_from_dynamic_table Apr 26 08:18:02 192.168.122.209 [58433.330678] [tdb] Start Tempesta DB Apr 26 08:18:02 192.168.122.209 [58433.463028] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:18:04 192.168.122.209 [58435.101459] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58435.101459] Maybe that's fine, but it's worth checking the [58435.101459] config - if there is no relations between the [58435.101459] names, then host name confusion attack is possible. Apr 26 08:18:04 192.168.122.209 [58435.280383] [tempesta fw] Configuration processing is completed. Apr 26 08:18:04 192.168.122.209 [58435.340274] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:18:05 192.168.122.209 [58435.758575] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:18:05 192.168.122.209 [58435.785370] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:18:05 192.168.122.209 [58435.811514] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:18:05 192.168.122.209 [58435.863986] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:18:05 192.168.122.209 [58435.907971] [tempesta fw] Tempesta FW is ready Apr 26 08:18:06 192.168.122.209 [58436.562708] [tdb] Close table 'client0.tdb' Apr 26 08:18:06 192.168.122.209 [58436.754817] [tdb] Close table 'sessions0.tdb' Apr 26 08:18:09 192.168.122.209 [58439.950992] [tdb] Close table 'cache0.tdb' Apr 26 08:18:09 192.168.122.209 [58440.167154] [tdb] Close table 'filter0.tdb' Apr 26 08:18:09 192.168.122.209 [58440.167590] [tempesta fw] modules are stopped Apr 26 08:18:09 192.168.122.209 [58440.413431] [tempesta fw] exiting... Apr 26 08:18:09 192.168.122.209 [58440.529988] [tdb] Shutdown Tempesta DB Apr 26 08:18:10 192.168.122.209 [58440.725667] End test: http2_general.test_h2_headers.DuplicateSingularHeader.test_two_header_as_bytes_from_dynamic_table Apr 26 08:18:10 192.168.122.209 [58440.749823] Start test: http2_general.test_h2_headers.HeadersEmptyCache.test Apr 26 08:18:11 192.168.122.209 [58441.846638] [tdb] Start Tempesta DB Apr 26 08:18:11 192.168.122.209 [58441.979844] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:18:12 192.168.122.209 [58443.477821] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58443.477821] Maybe that's fine, but it's worth checking the [58443.477821] config - if there is no relations between the [58443.477821] names, then host name confusion attack is possible. Apr 26 08:18:13 192.168.122.209 [58443.548114] [tempesta fw] Configuration processing is completed. Apr 26 08:18:13 192.168.122.209 [58443.598507] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:18:13 192.168.122.209 [58444.021568] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:18:13 192.168.122.209 [58444.048054] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:18:13 192.168.122.209 [58444.074323] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:18:13 192.168.122.209 [58444.128176] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:18:13 192.168.122.209 [58444.168083] [tempesta fw] Tempesta FW is ready Apr 26 08:18:14 192.168.122.209 [58444.866388] [tdb] Close table 'client0.tdb' Apr 26 08:18:14 192.168.122.209 [58445.065654] [tdb] Close table 'sessions0.tdb' Apr 26 08:18:17 192.168.122.209 [58448.205996] [tdb] Close table 'cache0.tdb' Apr 26 08:18:17 192.168.122.209 [58448.455801] [tdb] Close table 'filter0.tdb' Apr 26 08:18:17 192.168.122.209 [58448.456266] [tempesta fw] modules are stopped Apr 26 08:18:18 192.168.122.209 [58448.672443] [tempesta fw] exiting... Apr 26 08:18:18 192.168.122.209 [58448.783485] [tdb] Shutdown Tempesta DB Apr 26 08:18:18 192.168.122.209 [58448.991489] End test: http2_general.test_h2_headers.HeadersEmptyCache.test Apr 26 08:18:18 192.168.122.209 [58449.017032] Start test: http2_general.test_h2_headers.HeadersSpacedCache.test Apr 26 08:18:19 192.168.122.209 [58450.089571] [tdb] Start Tempesta DB Apr 26 08:18:19 192.168.122.209 [58450.230202] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:18:21 192.168.122.209 [58451.665853] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58451.665853] Maybe that's fine, but it's worth checking the [58451.665853] config - if there is no relations between the [58451.665853] names, then host name confusion attack is possible. Apr 26 08:18:21 192.168.122.209 [58451.744202] [tempesta fw] Configuration processing is completed. Apr 26 08:18:21 192.168.122.209 [58451.801090] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:18:21 192.168.122.209 [58452.218632] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:18:21 192.168.122.209 [58452.248134] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:18:21 192.168.122.209 [58452.274925] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:18:21 192.168.122.209 [58452.316171] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:18:21 192.168.122.209 [58452.360171] [tempesta fw] Tempesta FW is ready Apr 26 08:18:22 192.168.122.209 [58453.084628] [tdb] Close table 'client0.tdb' Apr 26 08:18:22 192.168.122.209 [58453.259218] [tdb] Close table 'sessions0.tdb' Apr 26 08:18:25 192.168.122.209 [58456.508694] [tdb] Close table 'cache0.tdb' Apr 26 08:18:26 192.168.122.209 [58456.761172] [tdb] Close table 'filter0.tdb' Apr 26 08:18:26 192.168.122.209 [58456.761606] [tempesta fw] modules are stopped Apr 26 08:18:26 192.168.122.209 [58456.958208] [tempesta fw] exiting... Apr 26 08:18:26 192.168.122.209 [58457.083964] [tdb] Shutdown Tempesta DB Apr 26 08:18:26 192.168.122.209 [58457.329582] End test: http2_general.test_h2_headers.HeadersSpacedCache.test Apr 26 08:18:26 192.168.122.209 [58457.354972] Start test: http2_general.test_h2_headers.LowercaseAddBackendHeaders.test Apr 26 08:18:27 192.168.122.209 [58458.483384] [tdb] Start Tempesta DB Apr 26 08:18:28 192.168.122.209 [58458.616946] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:18:29 192.168.122.209 [58460.053961] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58460.053961] Maybe that's fine, but it's worth checking the [58460.053961] config - if there is no relations between the [58460.053961] names, then host name confusion attack is possible. Apr 26 08:18:29 192.168.122.209 [58460.104254] [tempesta fw] Configuration processing is completed. Apr 26 08:18:29 192.168.122.209 [58460.162324] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:18:30 192.168.122.209 [58460.588533] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:18:30 192.168.122.209 [58460.615797] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:18:30 192.168.122.209 [58460.642991] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:18:30 192.168.122.209 [58460.716342] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:18:30 192.168.122.209 [58460.760285] [tempesta fw] Tempesta FW is ready Apr 26 08:18:31 192.168.122.209 [58461.543656] [tdb] Close table 'client0.tdb' Apr 26 08:18:31 192.168.122.209 [58461.732739] [tdb] Close table 'sessions0.tdb' Apr 26 08:18:34 192.168.122.209 [58464.908771] [tdb] Close table 'cache0.tdb' Apr 26 08:18:34 192.168.122.209 [58465.159074] [tdb] Close table 'filter0.tdb' Apr 26 08:18:34 192.168.122.209 [58465.159495] [tempesta fw] modules are stopped Apr 26 08:18:34 192.168.122.209 [58465.357199] [tempesta fw] exiting... Apr 26 08:18:34 192.168.122.209 [58465.521027] [tdb] Shutdown Tempesta DB Apr 26 08:18:35 192.168.122.209 [58465.778187] End test: http2_general.test_h2_headers.LowercaseAddBackendHeaders.test Apr 26 08:18:35 192.168.122.209 [58465.801069] Start test: http2_general.test_h2_headers.LowercaseAddBackendHeadersCache.test Apr 26 08:18:36 192.168.122.209 [58466.935821] [tdb] Start Tempesta DB Apr 26 08:18:36 192.168.122.209 [58467.085784] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:18:38 192.168.122.209 [58468.542062] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58468.542062] Maybe that's fine, but it's worth checking the [58468.542062] config - if there is no relations between the [58468.542062] names, then host name confusion attack is possible. Apr 26 08:18:38 192.168.122.209 [58468.608513] [tempesta fw] Configuration processing is completed. Apr 26 08:18:38 192.168.122.209 [58468.666430] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:18:38 192.168.122.209 [58469.089859] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:18:38 192.168.122.209 [58469.117456] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:18:38 192.168.122.209 [58469.144651] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:18:38 192.168.122.209 [58469.220442] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:18:38 192.168.122.209 [58469.264443] [tempesta fw] Tempesta FW is ready Apr 26 08:18:39 192.168.122.209 [58470.016403] [tdb] Close table 'client0.tdb' Apr 26 08:18:39 192.168.122.209 [58470.193721] [tdb] Close table 'sessions0.tdb' Apr 26 08:18:42 192.168.122.209 [58473.395156] [tdb] Close table 'cache0.tdb' Apr 26 08:18:43 192.168.122.209 [58473.623351] [tdb] Close table 'filter0.tdb' Apr 26 08:18:43 192.168.122.209 [58473.623799] [tempesta fw] modules are stopped Apr 26 08:18:43 192.168.122.209 [58473.836552] [tempesta fw] exiting... Apr 26 08:18:43 192.168.122.209 [58473.960240] [tdb] Shutdown Tempesta DB Apr 26 08:18:43 192.168.122.209 [58474.251658] End test: http2_general.test_h2_headers.LowercaseAddBackendHeadersCache.test Apr 26 08:18:43 192.168.122.209 [58474.270748] Start test: http2_general.test_h2_headers.MissingDateServerWithBodyTest.test Apr 26 08:18:44 192.168.122.209 [58475.284530] [tdb] Start Tempesta DB Apr 26 08:18:44 192.168.122.209 [58475.418141] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:18:46 192.168.122.209 [58476.661765] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58476.661765] Maybe that's fine, but it's worth checking the [58476.661765] config - if there is no relations between the [58476.661765] names, then host name confusion attack is possible. Apr 26 08:18:46 192.168.122.209 [58476.740567] [tempesta fw] Configuration processing is completed. Apr 26 08:18:46 192.168.122.209 [58476.790523] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:18:46 192.168.122.209 [58477.215290] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:18:46 192.168.122.209 [58477.243131] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:18:46 192.168.122.209 [58477.270229] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:18:46 192.168.122.209 [58477.316537] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:18:46 192.168.122.209 [58477.372528] [tempesta fw] Tempesta FW is ready Apr 26 08:18:47 192.168.122.209 [58478.012542] [tdb] Close table 'client0.tdb' Apr 26 08:18:47 192.168.122.209 [58478.197832] [tdb] Close table 'sessions0.tdb' Apr 26 08:18:50 192.168.122.209 [58481.390650] [tdb] Close table 'cache0.tdb' Apr 26 08:18:51 192.168.122.209 [58481.618324] [tdb] Close table 'filter0.tdb' Apr 26 08:18:51 192.168.122.209 [58481.618756] [tempesta fw] modules are stopped Apr 26 08:18:51 192.168.122.209 [58481.867816] [tempesta fw] exiting... Apr 26 08:18:51 192.168.122.209 [58481.963931] [tdb] Shutdown Tempesta DB Apr 26 08:18:51 192.168.122.209 [58482.167036] End test: http2_general.test_h2_headers.MissingDateServerWithBodyTest.test Apr 26 08:18:51 192.168.122.209 [58482.191777] Start test: http2_general.test_h2_headers.MissingDateServerWithLargeBodyTest.test Apr 26 08:18:52 192.168.122.209 [58483.223886] [tdb] Start Tempesta DB Apr 26 08:18:52 192.168.122.209 [58483.356649] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:18:54 192.168.122.209 [58484.661192] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58484.661192] Maybe that's fine, but it's worth checking the [58484.661192] config - if there is no relations between the [58484.661192] names, then host name confusion attack is possible. Apr 26 08:18:54 192.168.122.209 [58484.748661] [tempesta fw] Configuration processing is completed. Apr 26 08:18:54 192.168.122.209 [58484.799494] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:18:54 192.168.122.209 [58485.225171] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:18:54 192.168.122.209 [58485.253273] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:18:54 192.168.122.209 [58485.279490] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:18:54 192.168.122.209 [58485.316608] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:18:54 192.168.122.209 [58485.356595] [tempesta fw] Tempesta FW is ready Apr 26 08:18:57 192.168.122.209 [58487.625031] [tdb] Close table 'client0.tdb' Apr 26 08:18:57 192.168.122.209 [58487.825809] [tdb] Close table 'sessions0.tdb' Apr 26 08:19:00 192.168.122.209 [58491.090090] [tdb] Close table 'cache0.tdb' Apr 26 08:19:00 192.168.122.209 [58491.346415] [tdb] Close table 'filter0.tdb' Apr 26 08:19:00 192.168.122.209 [58491.346855] [tempesta fw] modules are stopped Apr 26 08:19:00 192.168.122.209 [58491.508687] [tempesta fw] exiting... Apr 26 08:19:01 192.168.122.209 [58491.646902] [tdb] Shutdown Tempesta DB Apr 26 08:19:01 192.168.122.209 [58491.875809] End test: http2_general.test_h2_headers.MissingDateServerWithLargeBodyTest.test Apr 26 08:19:01 192.168.122.209 [58491.887239] Start test: http2_general.test_h2_headers.TestContentTypeWithEmptyBodyDELETE.test_request_success Apr 26 08:19:02 192.168.122.209 [58492.957847] [tdb] Start Tempesta DB Apr 26 08:19:02 192.168.122.209 [58493.107211] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:19:03 192.168.122.209 [58494.502006] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58494.502006] Maybe that's fine, but it's worth checking the [58494.502006] config - if there is no relations between the [58494.502006] names, then host name confusion attack is possible. Apr 26 08:19:04 192.168.122.209 [58494.624800] [tempesta fw] Configuration processing is completed. Apr 26 08:19:04 192.168.122.209 [58494.673528] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:19:04 192.168.122.209 [58495.122608] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:19:04 192.168.122.209 [58495.150819] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:19:04 192.168.122.209 [58495.181645] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:19:04 192.168.122.209 [58495.232788] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:19:04 192.168.122.209 [58495.280739] [tempesta fw] Tempesta FW is ready Apr 26 08:19:04 192.168.122.209 [58495.476089] [tempesta fw] 127.0.0.2 "default" "DELETE / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800880200" Apr 26 08:19:04 192.168.122.209 [58495.478127] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 08:19:05 192.168.122.209 [58495.886570] [tdb] Close table 'client0.tdb' Apr 26 08:19:05 192.168.122.209 [58496.091882] [tdb] Close table 'sessions0.tdb' Apr 26 08:19:08 192.168.122.209 [58499.296392] [tdb] Close table 'cache0.tdb' Apr 26 08:19:08 192.168.122.209 [58499.518251] [tdb] Close table 'filter0.tdb' Apr 26 08:19:08 192.168.122.209 [58499.518666] [tempesta fw] modules are stopped Apr 26 08:19:09 192.168.122.209 [58499.788116] [tempesta fw] exiting... Apr 26 08:19:09 192.168.122.209 [58499.922968] [tdb] Shutdown Tempesta DB Apr 26 08:19:09 192.168.122.209 [58500.132939] End test: http2_general.test_h2_headers.TestContentTypeWithEmptyBodyDELETE.test_request_success Apr 26 08:19:09 192.168.122.209 [58500.148623] Start test: http2_general.test_h2_headers.TestContentTypeWithEmptyBodyPATCH.test_request_success Apr 26 08:19:10 192.168.122.209 [58501.192067] [tdb] Start Tempesta DB Apr 26 08:19:10 192.168.122.209 [58501.341731] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:19:12 192.168.122.209 [58502.657803] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58502.657803] Maybe that's fine, but it's worth checking the [58502.657803] config - if there is no relations between the [58502.657803] names, then host name confusion attack is possible. Apr 26 08:19:12 192.168.122.209 [58502.785350] [tempesta fw] Configuration processing is completed. Apr 26 08:19:12 192.168.122.209 [58502.841622] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:19:12 192.168.122.209 [58503.256415] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:19:12 192.168.122.209 [58503.283570] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:19:12 192.168.122.209 [58503.312246] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:19:12 192.168.122.209 [58503.364898] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:19:12 192.168.122.209 [58503.404826] [tempesta fw] Tempesta FW is ready Apr 26 08:19:13 192.168.122.209 [58503.609532] [tempesta fw] 127.0.0.2 "default" "PATCH / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800a40200" Apr 26 08:19:13 192.168.122.209 [58503.612597] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 08:19:13 192.168.122.209 [58504.054579] [tdb] Close table 'client0.tdb' Apr 26 08:19:13 192.168.122.209 [58504.245705] [tdb] Close table 'sessions0.tdb' Apr 26 08:19:16 192.168.122.209 [58507.466105] [tdb] Close table 'cache0.tdb' Apr 26 08:19:17 192.168.122.209 [58507.713948] [tdb] Close table 'filter0.tdb' Apr 26 08:19:17 192.168.122.209 [58507.714388] [tempesta fw] modules are stopped Apr 26 08:19:17 192.168.122.209 [58507.929481] [tempesta fw] exiting... Apr 26 08:19:17 192.168.122.209 [58508.053447] [tdb] Shutdown Tempesta DB Apr 26 08:19:17 192.168.122.209 [58508.283721] End test: http2_general.test_h2_headers.TestContentTypeWithEmptyBodyPATCH.test_request_success Apr 26 08:19:17 192.168.122.209 [58508.308373] Start test: http2_general.test_h2_headers.TestContentTypeWithEmptyBodyPOST.test_request_success Apr 26 08:19:18 192.168.122.209 [58509.433644] [tdb] Start Tempesta DB Apr 26 08:19:19 192.168.122.209 [58509.573810] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:19:20 192.168.122.209 [58510.913586] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58510.913586] Maybe that's fine, but it's worth checking the [58510.913586] config - if there is no relations between the [58510.913586] names, then host name confusion attack is possible. Apr 26 08:19:20 192.168.122.209 [58511.033007] [tempesta fw] Configuration processing is completed. Apr 26 08:19:20 192.168.122.209 [58511.094429] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:19:20 192.168.122.209 [58511.525212] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:19:21 192.168.122.209 [58511.552017] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:19:21 192.168.122.209 [58511.578444] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:19:21 192.168.122.209 [58511.624944] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:19:21 192.168.122.209 [58511.668976] [tempesta fw] Tempesta FW is ready Apr 26 08:19:21 192.168.122.209 [58511.891055] [tempesta fw] 127.0.0.2 "default" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800a80200" Apr 26 08:19:21 192.168.122.209 [58511.893011] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 08:19:21 192.168.122.209 [58512.307658] [tdb] Close table 'client0.tdb' Apr 26 08:19:21 192.168.122.209 [58512.498874] [tdb] Close table 'sessions0.tdb' Apr 26 08:19:25 192.168.122.209 [58515.720626] [tdb] Close table 'cache0.tdb' Apr 26 08:19:25 192.168.122.209 [58515.958117] [tdb] Close table 'filter0.tdb' Apr 26 08:19:25 192.168.122.209 [58515.958543] [tempesta fw] modules are stopped Apr 26 08:19:25 192.168.122.209 [58516.147694] [tempesta fw] exiting... Apr 26 08:19:25 192.168.122.209 [58516.274579] [tdb] Shutdown Tempesta DB Apr 26 08:19:25 192.168.122.209 [58516.493109] End test: http2_general.test_h2_headers.TestContentTypeWithEmptyBodyPOST.test_request_success Apr 26 08:19:25 192.168.122.209 [58516.518888] Start test: http2_general.test_h2_headers.TestContentTypeWithEmptyBodyPUT.test_request_success Apr 26 08:19:27 192.168.122.209 [58517.561645] [tdb] Start Tempesta DB Apr 26 08:19:27 192.168.122.209 [58517.701359] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:19:28 192.168.122.209 [58519.105394] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58519.105394] Maybe that's fine, but it's worth checking the [58519.105394] config - if there is no relations between the [58519.105394] names, then host name confusion attack is possible. Apr 26 08:19:28 192.168.122.209 [58519.229107] [tempesta fw] Configuration processing is completed. Apr 26 08:19:28 192.168.122.209 [58519.285133] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:19:29 192.168.122.209 [58519.699265] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:19:29 192.168.122.209 [58519.725409] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:19:29 192.168.122.209 [58519.752169] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:19:29 192.168.122.209 [58519.797013] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:19:29 192.168.122.209 [58519.837011] [tempesta fw] Tempesta FW is ready Apr 26 08:19:29 192.168.122.209 [58520.046641] [tempesta fw] 127.0.0.2 "default" "PUT / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800b40200" Apr 26 08:19:29 192.168.122.209 [58520.048136] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 08:19:29 192.168.122.209 [58520.448434] [tdb] Close table 'client0.tdb' Apr 26 08:19:30 192.168.122.209 [58520.642131] [tdb] Close table 'sessions0.tdb' Apr 26 08:19:33 192.168.122.209 [58523.922876] [tdb] Close table 'cache0.tdb' Apr 26 08:19:33 192.168.122.209 [58524.164015] [tdb] Close table 'filter0.tdb' Apr 26 08:19:33 192.168.122.209 [58524.164453] [tempesta fw] modules are stopped Apr 26 08:19:33 192.168.122.209 [58524.342801] [tempesta fw] exiting... Apr 26 08:19:33 192.168.122.209 [58524.500430] [tdb] Shutdown Tempesta DB Apr 26 08:19:34 192.168.122.209 [58524.777477] End test: http2_general.test_h2_headers.TestContentTypeWithEmptyBodyPUT.test_request_success Apr 26 08:19:34 192.168.122.209 [58524.804993] Start test: http2_general.test_h2_headers.TestH2Host.test_different_host_and_authority_headers Apr 26 08:19:35 192.168.122.209 [58525.886922] [tdb] Start Tempesta DB Apr 26 08:19:35 192.168.122.209 [58526.037120] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:19:37 192.168.122.209 [58527.669993] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58527.669993] Maybe that's fine, but it's worth checking the [58527.669993] config - if there is no relations between the [58527.669993] names, then host name confusion attack is possible. Apr 26 08:19:37 192.168.122.209 [58527.797240] [tempesta fw] Configuration processing is completed. Apr 26 08:19:37 192.168.122.209 [58527.856196] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:19:37 192.168.122.209 [58528.274325] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:19:37 192.168.122.209 [58528.300904] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:19:37 192.168.122.209 [58528.332211] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:19:37 192.168.122.209 [58528.385190] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:19:37 192.168.122.209 [58528.433139] [tempesta fw] Tempesta FW is ready Apr 26 08:19:38 192.168.122.209 [58529.071552] [tdb] Close table 'client0.tdb' Apr 26 08:19:38 192.168.122.209 [58529.260114] [tdb] Close table 'sessions0.tdb' Apr 26 08:19:41 192.168.122.209 [58532.481298] [tdb] Close table 'cache0.tdb' Apr 26 08:19:42 192.168.122.209 [58532.725679] [tdb] Close table 'filter0.tdb' Apr 26 08:19:42 192.168.122.209 [58532.726137] [tempesta fw] modules are stopped Apr 26 08:19:42 192.168.122.209 [58532.943058] [tempesta fw] exiting... Apr 26 08:19:42 192.168.122.209 [58533.083455] [tdb] Shutdown Tempesta DB Apr 26 08:19:42 192.168.122.209 [58533.319166] End test: http2_general.test_h2_headers.TestH2Host.test_different_host_and_authority_headers Apr 26 08:19:42 192.168.122.209 [58533.338320] Start test: http2_general.test_h2_headers.TestH2Host.test_empty_authority_header Apr 26 08:19:43 192.168.122.209 [58534.413293] [tdb] Start Tempesta DB Apr 26 08:19:44 192.168.122.209 [58534.575908] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:19:45 192.168.122.209 [58536.162755] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58536.162755] Maybe that's fine, but it's worth checking the [58536.162755] config - if there is no relations between the [58536.162755] names, then host name confusion attack is possible. Apr 26 08:19:45 192.168.122.209 [58536.329310] [tempesta fw] Configuration processing is completed. Apr 26 08:19:45 192.168.122.209 [58536.391595] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:19:46 192.168.122.209 [58536.901632] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:19:46 192.168.122.209 [58536.931830] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:19:46 192.168.122.209 [58536.961290] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:19:46 192.168.122.209 [58537.041237] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:19:46 192.168.122.209 [58537.101194] [tempesta fw] Tempesta FW is ready Apr 26 08:19:47 192.168.122.209 [58537.754030] [tdb] Close table 'client0.tdb' Apr 26 08:19:47 192.168.122.209 [58537.953003] [tdb] Close table 'sessions0.tdb' Apr 26 08:19:50 192.168.122.209 [58541.212043] [tdb] Close table 'cache0.tdb' Apr 26 08:19:50 192.168.122.209 [58541.449941] [tdb] Close table 'filter0.tdb' Apr 26 08:19:50 192.168.122.209 [58541.450378] [tempesta fw] modules are stopped Apr 26 08:19:51 192.168.122.209 [58541.688615] [tempesta fw] exiting... Apr 26 08:19:51 192.168.122.209 [58541.813468] [tdb] Shutdown Tempesta DB Apr 26 08:19:51 192.168.122.209 [58542.005739] End test: http2_general.test_h2_headers.TestH2Host.test_empty_authority_header Apr 26 08:19:51 192.168.122.209 [58542.038664] Start test: http2_general.test_h2_headers.TestH2Host.test_empty_host_header Apr 26 08:19:52 192.168.122.209 [58543.086326] [tdb] Start Tempesta DB Apr 26 08:19:52 192.168.122.209 [58543.251229] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:19:54 192.168.122.209 [58544.770906] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58544.770906] Maybe that's fine, but it's worth checking the [58544.770906] config - if there is no relations between the [58544.770906] names, then host name confusion attack is possible. Apr 26 08:19:54 192.168.122.209 [58544.925463] [tempesta fw] Configuration processing is completed. Apr 26 08:19:54 192.168.122.209 [58544.975532] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:19:54 192.168.122.209 [58545.460886] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:19:54 192.168.122.209 [58545.501825] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:19:54 192.168.122.209 [58545.534975] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:19:55 192.168.122.209 [58545.585430] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:19:55 192.168.122.209 [58545.625355] [tempesta fw] Tempesta FW is ready Apr 26 08:19:55 192.168.122.209 [58546.259781] [tdb] Close table 'client0.tdb' Apr 26 08:19:55 192.168.122.209 [58546.453581] [tdb] Close table 'sessions0.tdb' Apr 26 08:19:59 192.168.122.209 [58549.749436] [tdb] Close table 'cache0.tdb' Apr 26 08:19:59 192.168.122.209 [58549.995717] [tdb] Close table 'filter0.tdb' Apr 26 08:19:59 192.168.122.209 [58549.996150] [tempesta fw] modules are stopped Apr 26 08:19:59 192.168.122.209 [58550.224936] [tempesta fw] exiting... Apr 26 08:19:59 192.168.122.209 [58550.331179] [tdb] Shutdown Tempesta DB Apr 26 08:20:00 192.168.122.209 [58550.547510] End test: http2_general.test_h2_headers.TestH2Host.test_empty_host_header Apr 26 08:20:00 192.168.122.209 [58550.568966] Start test: http2_general.test_h2_headers.TestH2Host.test_host_authority_ok Apr 26 08:20:01 192.168.122.209 [58551.655153] [tdb] Start Tempesta DB Apr 26 08:20:01 192.168.122.209 [58551.798886] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:20:02 192.168.122.209 [58553.387008] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58553.387008] Maybe that's fine, but it's worth checking the [58553.387008] config - if there is no relations between the [58553.387008] names, then host name confusion attack is possible. Apr 26 08:20:03 192.168.122.209 [58553.541578] [tempesta fw] Configuration processing is completed. Apr 26 08:20:03 192.168.122.209 [58553.596839] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:20:03 192.168.122.209 [58554.058268] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:20:03 192.168.122.209 [58554.096840] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:20:03 192.168.122.209 [58554.132097] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:20:03 192.168.122.209 [58554.217502] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:20:03 192.168.122.209 [58554.281479] [tempesta fw] Tempesta FW is ready Apr 26 08:20:04 192.168.122.209 [58554.905108] [tdb] Close table 'client0.tdb' Apr 26 08:20:04 192.168.122.209 [58555.104466] [tdb] Close table 'sessions0.tdb' Apr 26 08:20:07 192.168.122.209 [58558.397003] [tdb] Close table 'cache0.tdb' Apr 26 08:20:08 192.168.122.209 [58558.655416] [tdb] Close table 'filter0.tdb' Apr 26 08:20:08 192.168.122.209 [58558.655856] [tempesta fw] modules are stopped Apr 26 08:20:08 192.168.122.209 [58558.875160] [tempesta fw] exiting... Apr 26 08:20:08 192.168.122.209 [58559.031574] [tdb] Shutdown Tempesta DB Apr 26 08:20:08 192.168.122.209 [58559.270933] End test: http2_general.test_h2_headers.TestH2Host.test_host_authority_ok Apr 26 08:20:08 192.168.122.209 [58559.294021] Start test: http2_general.test_h2_headers.TestH2Host.test_host_header_ok Apr 26 08:20:09 192.168.122.209 [58560.380600] [tdb] Start Tempesta DB Apr 26 08:20:09 192.168.122.209 [58560.526632] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:20:11 192.168.122.209 [58562.123072] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58562.123072] Maybe that's fine, but it's worth checking the [58562.123072] config - if there is no relations between the [58562.123072] names, then host name confusion attack is possible. Apr 26 08:20:11 192.168.122.209 [58562.281710] [tempesta fw] Configuration processing is completed. Apr 26 08:20:11 192.168.122.209 [58562.352583] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:20:12 192.168.122.209 [58562.849140] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:20:12 192.168.122.209 [58562.879024] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:20:12 192.168.122.209 [58562.909055] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:20:12 192.168.122.209 [58562.961680] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:20:12 192.168.122.209 [58563.021557] [tempesta fw] Tempesta FW is ready Apr 26 08:20:13 192.168.122.209 [58563.694092] [tdb] Close table 'client0.tdb' Apr 26 08:20:13 192.168.122.209 [58563.872482] [tdb] Close table 'sessions0.tdb' Apr 26 08:20:16 192.168.122.209 [58567.125698] [tdb] Close table 'cache0.tdb' Apr 26 08:20:16 192.168.122.209 [58567.352131] [tdb] Close table 'filter0.tdb' Apr 26 08:20:16 192.168.122.209 [58567.352571] [tempesta fw] modules are stopped Apr 26 08:20:17 192.168.122.209 [58567.560257] [tempesta fw] exiting... Apr 26 08:20:17 192.168.122.209 [58567.667284] [tdb] Shutdown Tempesta DB Apr 26 08:20:17 192.168.122.209 [58567.873461] End test: http2_general.test_h2_headers.TestH2Host.test_host_header_ok Apr 26 08:20:17 192.168.122.209 [58567.904628] Start test: http2_general.test_h2_headers.TestH2Host.test_host_missing Apr 26 08:20:18 192.168.122.209 [58568.959357] [tdb] Start Tempesta DB Apr 26 08:20:18 192.168.122.209 [58569.110081] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:20:20 192.168.122.209 [58570.662589] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58570.662589] Maybe that's fine, but it's worth checking the [58570.662589] config - if there is no relations between the [58570.662589] names, then host name confusion attack is possible. Apr 26 08:20:20 192.168.122.209 [58570.814145] [tempesta fw] Configuration processing is completed. Apr 26 08:20:20 192.168.122.209 [58570.867839] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:20:20 192.168.122.209 [58571.287684] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:20:20 192.168.122.209 [58571.315050] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:20:20 192.168.122.209 [58571.342280] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:20:20 192.168.122.209 [58571.409721] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:20:20 192.168.122.209 [58571.453668] [tempesta fw] Tempesta FW is ready Apr 26 08:20:21 192.168.122.209 [58571.640403] [tempesta fw] Warning: Invalid authority: 127.0.0.2 Apr 26 08:20:21 192.168.122.209 [58572.083781] [tdb] Close table 'client0.tdb' Apr 26 08:20:21 192.168.122.209 [58572.271731] [tdb] Close table 'sessions0.tdb' Apr 26 08:20:24 192.168.122.209 [58575.429154] [tdb] Close table 'cache0.tdb' Apr 26 08:20:25 192.168.122.209 [58575.730323] [tdb] Close table 'filter0.tdb' Apr 26 08:20:25 192.168.122.209 [58575.730745] [tempesta fw] modules are stopped Apr 26 08:20:25 192.168.122.209 [58575.945543] [tempesta fw] exiting... Apr 26 08:20:25 192.168.122.209 [58576.084767] [tdb] Shutdown Tempesta DB Apr 26 08:20:25 192.168.122.209 [58576.316490] End test: http2_general.test_h2_headers.TestH2Host.test_host_missing Apr 26 08:20:25 192.168.122.209 [58576.334494] Start test: http2_general.test_h2_headers.TestHeadersBlockedByMaxHeaderListSize.test_blocked_by_max_headers_count_huffman Apr 26 08:20:26 192.168.122.209 [58577.386502] [tdb] Start Tempesta DB Apr 26 08:20:26 192.168.122.209 [58577.534760] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:20:28 192.168.122.209 [58578.943054] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58578.943054] Maybe that's fine, but it's worth checking the [58578.943054] config - if there is no relations between the [58578.943054] names, then host name confusion attack is possible. Apr 26 08:20:28 192.168.122.209 [58579.033838] [tempesta fw] Configuration processing is completed. Apr 26 08:20:28 192.168.122.209 [58579.083303] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:20:28 192.168.122.209 [58579.498421] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:20:28 192.168.122.209 [58579.525598] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:20:29 192.168.122.209 [58579.556799] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:20:29 192.168.122.209 [58579.605770] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:20:29 192.168.122.209 [58579.645783] [tempesta fw] Tempesta FW is ready Apr 26 08:20:29 192.168.122.209 [58579.850983] [tempesta fw] Warning: frang: HTTP header list size exceeded for 127.0.0.2: 251 (lim=250) Apr 26 08:20:29 192.168.122.209 [58580.277168] [tdb] Close table 'client0.tdb' Apr 26 08:20:29 192.168.122.209 [58580.447982] [tdb] Close table 'sessions0.tdb' Apr 26 08:20:33 192.168.122.209 [58583.663954] [tdb] Close table 'cache0.tdb' Apr 26 08:20:33 192.168.122.209 [58583.926155] [tdb] Close table 'filter0.tdb' Apr 26 08:20:33 192.168.122.209 [58583.926594] [tempesta fw] modules are stopped Apr 26 08:20:33 192.168.122.209 [58584.094457] [tempesta fw] exiting... Apr 26 08:20:33 192.168.122.209 [58584.198851] [tdb] Shutdown Tempesta DB Apr 26 08:20:33 192.168.122.209 [58584.400114] End test: http2_general.test_h2_headers.TestHeadersBlockedByMaxHeaderListSize.test_blocked_by_max_headers_count_huffman Apr 26 08:20:33 192.168.122.209 [58584.415233] Start test: http2_general.test_h2_headers.TestHeadersBlockedByMaxHeaderListSize.test_blocked_by_max_headers_count_no_huffman Apr 26 08:20:34 192.168.122.209 [58585.482730] [tdb] Start Tempesta DB Apr 26 08:20:35 192.168.122.209 [58585.634360] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:20:36 192.168.122.209 [58587.095213] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58587.095213] Maybe that's fine, but it's worth checking the [58587.095213] config - if there is no relations between the [58587.095213] names, then host name confusion attack is possible. Apr 26 08:20:36 192.168.122.209 [58587.173957] [tempesta fw] Configuration processing is completed. Apr 26 08:20:36 192.168.122.209 [58587.224380] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:20:37 192.168.122.209 [58587.651186] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:20:37 192.168.122.209 [58587.678561] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:20:37 192.168.122.209 [58587.705917] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:20:37 192.168.122.209 [58587.745888] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:20:37 192.168.122.209 [58587.789873] [tempesta fw] Tempesta FW is ready Apr 26 08:20:37 192.168.122.209 [58587.991382] [tempesta fw] Warning: frang: HTTP header list size exceeded for 127.0.0.2: 251 (lim=250) Apr 26 08:20:37 192.168.122.209 [58588.404071] [tdb] Close table 'client0.tdb' Apr 26 08:20:38 192.168.122.209 [58588.582283] [tdb] Close table 'sessions0.tdb' Apr 26 08:20:41 192.168.122.209 [58591.823179] [tdb] Close table 'cache0.tdb' Apr 26 08:20:41 192.168.122.209 [58592.065192] [tdb] Close table 'filter0.tdb' Apr 26 08:20:41 192.168.122.209 [58592.065652] [tempesta fw] modules are stopped Apr 26 08:20:41 192.168.122.209 [58592.260513] [tempesta fw] exiting... Apr 26 08:20:41 192.168.122.209 [58592.365976] [tdb] Shutdown Tempesta DB Apr 26 08:20:42 192.168.122.209 [58592.607338] End test: http2_general.test_h2_headers.TestHeadersBlockedByMaxHeaderListSize.test_blocked_by_max_headers_count_no_huffman Apr 26 08:20:42 192.168.122.209 [58592.624636] Start test: http2_general.test_h2_headers.TestHeadersBlockedByMaxHeaderListSize.test_not_blocked_by_max_headers_count_huffman Apr 26 08:20:43 192.168.122.209 [58593.654882] [tdb] Start Tempesta DB Apr 26 08:20:43 192.168.122.209 [58593.808434] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:20:44 192.168.122.209 [58595.271338] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58595.271338] Maybe that's fine, but it's worth checking the [58595.271338] config - if there is no relations between the [58595.271338] names, then host name confusion attack is possible. Apr 26 08:20:44 192.168.122.209 [58595.350054] [tempesta fw] Configuration processing is completed. Apr 26 08:20:44 192.168.122.209 [58595.399675] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:20:45 192.168.122.209 [58595.816824] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:20:45 192.168.122.209 [58595.843647] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:20:45 192.168.122.209 [58595.879467] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:20:45 192.168.122.209 [58595.922003] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:20:45 192.168.122.209 [58595.961970] [tempesta fw] Tempesta FW is ready Apr 26 08:20:46 192.168.122.209 [58596.587293] [tdb] Close table 'client0.tdb' Apr 26 08:20:46 192.168.122.209 [58596.801013] [tdb] Close table 'sessions0.tdb' Apr 26 08:20:49 192.168.122.209 [58599.992720] [tdb] Close table 'cache0.tdb' Apr 26 08:20:49 192.168.122.209 [58600.233007] [tdb] Close table 'filter0.tdb' Apr 26 08:20:49 192.168.122.209 [58600.233445] [tempesta fw] modules are stopped Apr 26 08:20:49 192.168.122.209 [58600.418032] [tempesta fw] exiting... Apr 26 08:20:50 192.168.122.209 [58600.560708] [tdb] Shutdown Tempesta DB Apr 26 08:20:50 192.168.122.209 [58600.790378] End test: http2_general.test_h2_headers.TestHeadersBlockedByMaxHeaderListSize.test_not_blocked_by_max_headers_count_huffman Apr 26 08:20:50 192.168.122.209 [58600.817280] Start test: http2_general.test_h2_headers.TestHeadersBlockedByMaxHeaderListSize.test_not_blocked_by_max_headers_count_no_huffman Apr 26 08:20:51 192.168.122.209 [58601.891291] [tdb] Start Tempesta DB Apr 26 08:20:51 192.168.122.209 [58602.024339] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:20:52 192.168.122.209 [58603.442545] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58603.442545] Maybe that's fine, but it's worth checking the [58603.442545] config - if there is no relations between the [58603.442545] names, then host name confusion attack is possible. Apr 26 08:20:52 192.168.122.209 [58603.514153] [tempesta fw] Configuration processing is completed. Apr 26 08:20:53 192.168.122.209 [58603.571386] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:20:53 192.168.122.209 [58604.024643] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:20:53 192.168.122.209 [58604.051597] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:20:53 192.168.122.209 [58604.078753] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:20:53 192.168.122.209 [58604.122130] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:20:53 192.168.122.209 [58604.166078] [tempesta fw] Tempesta FW is ready Apr 26 08:20:54 192.168.122.209 [58604.809351] [tdb] Close table 'client0.tdb' Apr 26 08:20:54 192.168.122.209 [58604.989256] [tdb] Close table 'sessions0.tdb' Apr 26 08:20:57 192.168.122.209 [58608.207964] [tdb] Close table 'cache0.tdb' Apr 26 08:20:57 192.168.122.209 [58608.445863] [tdb] Close table 'filter0.tdb' Apr 26 08:20:57 192.168.122.209 [58608.446311] [tempesta fw] modules are stopped Apr 26 08:20:58 192.168.122.209 [58608.643500] [tempesta fw] exiting... Apr 26 08:20:58 192.168.122.209 [58608.748935] [tdb] Shutdown Tempesta DB Apr 26 08:20:58 192.168.122.209 [58608.990336] End test: http2_general.test_h2_headers.TestHeadersBlockedByMaxHeaderListSize.test_not_blocked_by_max_headers_count_no_huffman Apr 26 08:20:58 192.168.122.209 [58609.008679] Start test: http2_general.test_h2_headers.TestNoContentLengthInMethodMethodDELETE.test_request_success Apr 26 08:20:59 192.168.122.209 [58609.967531] [tdb] Start Tempesta DB Apr 26 08:20:59 192.168.122.209 [58610.110724] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:21:00 192.168.122.209 [58611.447804] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58611.447804] Maybe that's fine, but it's worth checking the [58611.447804] config - if there is no relations between the [58611.447804] names, then host name confusion attack is possible. Apr 26 08:21:01 192.168.122.209 [58611.566246] [tempesta fw] Configuration processing is completed. Apr 26 08:21:01 192.168.122.209 [58611.622713] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:21:01 192.168.122.209 [58612.052410] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:21:01 192.168.122.209 [58612.092228] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:21:01 192.168.122.209 [58612.120522] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:21:01 192.168.122.209 [58612.178120] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:21:01 192.168.122.209 [58612.226130] [tempesta fw] Tempesta FW is ready Apr 26 08:21:01 192.168.122.209 [58612.424811] [tempesta fw] 127.0.0.2 "default" "DELETE / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800880200" Apr 26 08:21:01 192.168.122.209 [58612.427295] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 08:21:01 192.168.122.209 [58612.441844] [tempesta fw] 127.0.0.2 "default" "DELETE / HTTP/2.0" 201 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800880200" Apr 26 08:21:01 192.168.122.209 [58612.443564] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 08:21:01 192.168.122.209 [58612.463374] [tempesta fw] 127.0.0.2 "default" "DELETE / HTTP/2.0" 302 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800880200" Apr 26 08:21:01 192.168.122.209 [58612.464405] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 08:21:01 192.168.122.209 [58612.524158] [tempesta fw] 127.0.0.2 "default" "DELETE / HTTP/2.0" 304 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800880200" Apr 26 08:21:01 192.168.122.209 [58612.525971] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 08:21:02 192.168.122.209 [58612.543580] [tempesta fw] 127.0.0.2 "default" "DELETE / HTTP/2.0" 400 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800880200" Apr 26 08:21:02 192.168.122.209 [58612.546023] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 08:21:02 192.168.122.209 [58612.567772] [tempesta fw] 127.0.0.2 "default" "DELETE / HTTP/2.0" 401 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800880200" Apr 26 08:21:02 192.168.122.209 [58612.570452] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 08:21:02 192.168.122.209 [58612.628809] [tempesta fw] 127.0.0.2 "default" "DELETE / HTTP/2.0" 404 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800880200" Apr 26 08:21:02 192.168.122.209 [58612.631956] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 08:21:02 192.168.122.209 [58612.648222] [tempesta fw] 127.0.0.2 "default" "DELETE / HTTP/2.0" 500 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800880200" Apr 26 08:21:02 192.168.122.209 [58612.650477] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 08:21:02 192.168.122.209 [58613.055966] [tdb] Close table 'client0.tdb' Apr 26 08:21:02 192.168.122.209 [58613.246709] [tdb] Close table 'sessions0.tdb' Apr 26 08:21:05 192.168.122.209 [58616.468772] [tdb] Close table 'cache0.tdb' Apr 26 08:21:06 192.168.122.209 [58616.713732] [tdb] Close table 'filter0.tdb' Apr 26 08:21:06 192.168.122.209 [58616.714205] [tempesta fw] modules are stopped Apr 26 08:21:06 192.168.122.209 [58616.902896] [tempesta fw] exiting... Apr 26 08:21:06 192.168.122.209 [58617.021244] [tdb] Shutdown Tempesta DB Apr 26 08:21:06 192.168.122.209 [58617.265645] End test: http2_general.test_h2_headers.TestNoContentLengthInMethodMethodDELETE.test_request_success Apr 26 08:21:06 192.168.122.209 [58617.284998] Start test: http2_general.test_h2_headers.TestNoContentLengthInMethodMethodGET.test_request_success Apr 26 08:21:07 192.168.122.209 [58618.376732] [tdb] Start Tempesta DB Apr 26 08:21:07 192.168.122.209 [58618.524474] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:21:09 192.168.122.209 [58619.819016] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58619.819016] Maybe that's fine, but it's worth checking the [58619.819016] config - if there is no relations between the [58619.819016] names, then host name confusion attack is possible. Apr 26 08:21:09 192.168.122.209 [58619.942470] [tempesta fw] Configuration processing is completed. Apr 26 08:21:09 192.168.122.209 [58619.997070] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:21:09 192.168.122.209 [58620.426399] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:21:09 192.168.122.209 [58620.454636] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:21:09 192.168.122.209 [58620.483442] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:21:09 192.168.122.209 [58620.530267] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:21:10 192.168.122.209 [58620.570290] [tempesta fw] Tempesta FW is ready Apr 26 08:21:10 192.168.122.209 [58620.775699] [tempesta fw] 127.0.0.2 "default" "GET / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=178008c0200" Apr 26 08:21:10 192.168.122.209 [58620.777180] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 08:21:10 192.168.122.209 [58620.794524] [tempesta fw] 127.0.0.2 "default" "GET / HTTP/2.0" 302 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=178008c0200" Apr 26 08:21:10 192.168.122.209 [58620.796429] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 08:21:10 192.168.122.209 [58620.814299] [tempesta fw] 127.0.0.2 "default" "GET / HTTP/2.0" 304 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=178008c0200" Apr 26 08:21:10 192.168.122.209 [58620.815578] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 08:21:10 192.168.122.209 [58620.877006] [tempesta fw] 127.0.0.2 "default" "GET / HTTP/2.0" 400 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=178008c0200" Apr 26 08:21:10 192.168.122.209 [58620.878777] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 08:21:10 192.168.122.209 [58620.898368] [tempesta fw] 127.0.0.2 "default" "GET / HTTP/2.0" 401 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=178008c0200" Apr 26 08:21:10 192.168.122.209 [58620.899529] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 08:21:10 192.168.122.209 [58620.917243] [tempesta fw] 127.0.0.2 "default" "GET / HTTP/2.0" 404 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=178008c0200" Apr 26 08:21:10 192.168.122.209 [58620.919307] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 08:21:10 192.168.122.209 [58620.982431] [tempesta fw] 127.0.0.2 "default" "GET / HTTP/2.0" 500 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=178008c0200" Apr 26 08:21:10 192.168.122.209 [58620.984360] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 08:21:10 192.168.122.209 [58621.363331] [tdb] Close table 'client0.tdb' Apr 26 08:21:11 192.168.122.209 [58621.558115] [tdb] Close table 'sessions0.tdb' Apr 26 08:21:14 192.168.122.209 [58624.728389] [tdb] Close table 'cache0.tdb' Apr 26 08:21:14 192.168.122.209 [58624.988981] [tdb] Close table 'filter0.tdb' Apr 26 08:21:14 192.168.122.209 [58624.989435] [tempesta fw] modules are stopped Apr 26 08:21:14 192.168.122.209 [58625.189207] [tempesta fw] exiting... Apr 26 08:21:14 192.168.122.209 [58625.301954] [tdb] Shutdown Tempesta DB Apr 26 08:21:14 192.168.122.209 [58625.520527] End test: http2_general.test_h2_headers.TestNoContentLengthInMethodMethodGET.test_request_success Apr 26 08:21:15 192.168.122.209 [58625.544960] Start test: http2_general.test_h2_headers.TestNoContentLengthInMethodMethodHEAD.test_request_success Apr 26 08:21:16 192.168.122.209 [58626.676161] [tdb] Start Tempesta DB Apr 26 08:21:16 192.168.122.209 [58626.824725] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:21:17 192.168.122.209 [58628.255712] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58628.255712] Maybe that's fine, but it's worth checking the [58628.255712] config - if there is no relations between the [58628.255712] names, then host name confusion attack is possible. Apr 26 08:21:17 192.168.122.209 [58628.386349] [tempesta fw] Configuration processing is completed. Apr 26 08:21:17 192.168.122.209 [58628.432490] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:21:18 192.168.122.209 [58628.877519] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:21:18 192.168.122.209 [58628.906280] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:21:18 192.168.122.209 [58628.942790] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:21:18 192.168.122.209 [58628.986386] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:21:18 192.168.122.209 [58629.026385] [tempesta fw] Tempesta FW is ready Apr 26 08:21:18 192.168.122.209 [58629.238683] [tempesta fw] 127.0.0.2 "default" "HEAD / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800900200" Apr 26 08:21:18 192.168.122.209 [58629.240322] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 08:21:19 192.168.122.209 [58629.704278] [tdb] Close table 'client0.tdb' Apr 26 08:21:19 192.168.122.209 [58629.895717] [tdb] Close table 'sessions0.tdb' Apr 26 08:21:22 192.168.122.209 [58633.104926] [tdb] Close table 'cache0.tdb' Apr 26 08:21:22 192.168.122.209 [58633.335646] [tdb] Close table 'filter0.tdb' Apr 26 08:21:22 192.168.122.209 [58633.336085] [tempesta fw] modules are stopped Apr 26 08:21:22 192.168.122.209 [58633.519871] [tempesta fw] exiting... Apr 26 08:21:23 192.168.122.209 [58633.648496] [tdb] Shutdown Tempesta DB Apr 26 08:21:23 192.168.122.209 [58633.851795] End test: http2_general.test_h2_headers.TestNoContentLengthInMethodMethodHEAD.test_request_success Apr 26 08:21:23 192.168.122.209 [58633.882270] Start test: http2_general.test_h2_headers.TestNoContentLengthInMethodMethodPATCH.test_request_success Apr 26 08:21:24 192.168.122.209 [58635.032794] [tdb] Start Tempesta DB Apr 26 08:21:24 192.168.122.209 [58635.174444] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:21:26 192.168.122.209 [58636.575973] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58636.575973] Maybe that's fine, but it's worth checking the [58636.575973] config - if there is no relations between the [58636.575973] names, then host name confusion attack is possible. Apr 26 08:21:26 192.168.122.209 [58636.710617] [tempesta fw] Configuration processing is completed. Apr 26 08:21:26 192.168.122.209 [58636.767316] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:21:26 192.168.122.209 [58637.209412] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:21:26 192.168.122.209 [58637.237596] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:21:26 192.168.122.209 [58637.265640] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:21:26 192.168.122.209 [58637.314560] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:21:26 192.168.122.209 [58637.354410] [tempesta fw] Tempesta FW is ready Apr 26 08:21:27 192.168.122.209 [58637.573034] [tempesta fw] 127.0.0.2 "default" "PATCH / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800a40200" Apr 26 08:21:27 192.168.122.209 [58637.576185] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 08:21:27 192.168.122.209 [58637.591356] [tempesta fw] 127.0.0.2 "default" "PATCH / HTTP/2.0" 201 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800a40200" Apr 26 08:21:27 192.168.122.209 [58637.592549] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 08:21:27 192.168.122.209 [58637.616729] [tempesta fw] 127.0.0.2 "default" "PATCH / HTTP/2.0" 302 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800a40200" Apr 26 08:21:27 192.168.122.209 [58637.619840] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 08:21:27 192.168.122.209 [58637.680902] [tempesta fw] 127.0.0.2 "default" "PATCH / HTTP/2.0" 304 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800a40200" Apr 26 08:21:27 192.168.122.209 [58637.682917] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 08:21:27 192.168.122.209 [58637.706428] [tempesta fw] 127.0.0.2 "default" "PATCH / HTTP/2.0" 400 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800a40200" Apr 26 08:21:27 192.168.122.209 [58637.707542] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 08:21:27 192.168.122.209 [58637.721218] [tempesta fw] 127.0.0.2 "default" "PATCH / HTTP/2.0" 401 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800a40200" Apr 26 08:21:27 192.168.122.209 [58637.722734] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 08:21:27 192.168.122.209 [58637.781022] [tempesta fw] 127.0.0.2 "default" "PATCH / HTTP/2.0" 404 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800a40200" Apr 26 08:21:27 192.168.122.209 [58637.782183] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 08:21:27 192.168.122.209 [58637.802989] [tempesta fw] 127.0.0.2 "default" "PATCH / HTTP/2.0" 500 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800a40200" Apr 26 08:21:27 192.168.122.209 [58637.804883] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 08:21:27 192.168.122.209 [58638.246411] [tdb] Close table 'client0.tdb' Apr 26 08:21:27 192.168.122.209 [58638.432309] [tdb] Close table 'sessions0.tdb' Apr 26 08:21:31 192.168.122.209 [58641.657940] [tdb] Close table 'cache0.tdb' Apr 26 08:21:31 192.168.122.209 [58641.924123] [tdb] Close table 'filter0.tdb' Apr 26 08:21:31 192.168.122.209 [58641.924547] [tempesta fw] modules are stopped Apr 26 08:21:31 192.168.122.209 [58642.112115] [tempesta fw] exiting... Apr 26 08:21:31 192.168.122.209 [58642.240650] [tdb] Shutdown Tempesta DB Apr 26 08:21:31 192.168.122.209 [58642.465048] End test: http2_general.test_h2_headers.TestNoContentLengthInMethodMethodPATCH.test_request_success Apr 26 08:21:31 192.168.122.209 [58642.476445] Start test: http2_general.test_h2_headers.TestNoContentLengthInMethodMethodPOST.test_request_success Apr 26 08:21:33 192.168.122.209 [58643.583644] [tdb] Start Tempesta DB Apr 26 08:21:33 192.168.122.209 [58643.745132] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:21:34 192.168.122.209 [58645.088027] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58645.088027] Maybe that's fine, but it's worth checking the [58645.088027] config - if there is no relations between the [58645.088027] names, then host name confusion attack is possible. Apr 26 08:21:34 192.168.122.209 [58645.210599] [tempesta fw] Configuration processing is completed. Apr 26 08:21:34 192.168.122.209 [58645.265191] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:21:35 192.168.122.209 [58645.708036] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:21:35 192.168.122.209 [58645.736376] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:21:35 192.168.122.209 [58645.764569] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:21:35 192.168.122.209 [58645.814683] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:21:35 192.168.122.209 [58645.854614] [tempesta fw] Tempesta FW is ready Apr 26 08:21:35 192.168.122.209 [58646.058087] [tempesta fw] 127.0.0.2 "default" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800a80200" Apr 26 08:21:35 192.168.122.209 [58646.060012] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 08:21:35 192.168.122.209 [58646.076972] [tempesta fw] 127.0.0.2 "default" "POST / HTTP/2.0" 201 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800a80200" Apr 26 08:21:35 192.168.122.209 [58646.078137] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 08:21:35 192.168.122.209 [58646.095606] [tempesta fw] 127.0.0.2 "default" "POST / HTTP/2.0" 302 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800a80200" Apr 26 08:21:35 192.168.122.209 [58646.097770] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 08:21:35 192.168.122.209 [58646.157703] [tempesta fw] 127.0.0.2 "default" "POST / HTTP/2.0" 304 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800a80200" Apr 26 08:21:35 192.168.122.209 [58646.158935] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 08:21:35 192.168.122.209 [58646.184780] [tempesta fw] 127.0.0.2 "default" "POST / HTTP/2.0" 400 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800a80200" Apr 26 08:21:35 192.168.122.209 [58646.185940] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 08:21:35 192.168.122.209 [58646.202307] [tempesta fw] 127.0.0.2 "default" "POST / HTTP/2.0" 401 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800a80200" Apr 26 08:21:35 192.168.122.209 [58646.203496] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 08:21:35 192.168.122.209 [58646.260363] [tempesta fw] 127.0.0.2 "default" "POST / HTTP/2.0" 404 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800a80200" Apr 26 08:21:35 192.168.122.209 [58646.263861] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 08:21:35 192.168.122.209 [58646.277175] [tempesta fw] 127.0.0.2 "default" "POST / HTTP/2.0" 500 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800a80200" Apr 26 08:21:35 192.168.122.209 [58646.278189] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 08:21:36 192.168.122.209 [58646.702830] [tdb] Close table 'client0.tdb' Apr 26 08:21:36 192.168.122.209 [58646.909357] [tdb] Close table 'sessions0.tdb' Apr 26 08:21:39 192.168.122.209 [58650.143902] [tdb] Close table 'cache0.tdb' Apr 26 08:21:39 192.168.122.209 [58650.420127] [tdb] Close table 'filter0.tdb' Apr 26 08:21:39 192.168.122.209 [58650.420567] [tempesta fw] modules are stopped Apr 26 08:21:40 192.168.122.209 [58650.609293] [tempesta fw] exiting... Apr 26 08:21:40 192.168.122.209 [58650.721917] [tdb] Shutdown Tempesta DB Apr 26 08:21:40 192.168.122.209 [58650.941362] End test: http2_general.test_h2_headers.TestNoContentLengthInMethodMethodPOST.test_request_success Apr 26 08:21:40 192.168.122.209 [58650.961143] Start test: http2_general.test_h2_headers.TestNoContentLengthInMethodMethodPUT.test_request_success Apr 26 08:21:41 192.168.122.209 [58651.913442] [tdb] Start Tempesta DB Apr 26 08:21:41 192.168.122.209 [58652.058709] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:21:42 192.168.122.209 [58653.449263] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58653.449263] Maybe that's fine, but it's worth checking the [58653.449263] config - if there is no relations between the [58653.449263] names, then host name confusion attack is possible. Apr 26 08:21:43 192.168.122.209 [58653.578820] [tempesta fw] Configuration processing is completed. Apr 26 08:21:43 192.168.122.209 [58653.628947] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:21:43 192.168.122.209 [58654.094921] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:21:43 192.168.122.209 [58654.125672] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:21:43 192.168.122.209 [58654.156408] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:21:43 192.168.122.209 [58654.210724] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:21:43 192.168.122.209 [58654.254702] [tempesta fw] Tempesta FW is ready Apr 26 08:21:43 192.168.122.209 [58654.462512] [tempesta fw] 127.0.0.2 "default" "PUT / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800b40200" Apr 26 08:21:43 192.168.122.209 [58654.464082] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 08:21:43 192.168.122.209 [58654.481347] [tempesta fw] 127.0.0.2 "default" "PUT / HTTP/2.0" 201 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800b40200" Apr 26 08:21:43 192.168.122.209 [58654.482631] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 08:21:43 192.168.122.209 [58654.500885] [tempesta fw] 127.0.0.2 "default" "PUT / HTTP/2.0" 302 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800b40200" Apr 26 08:21:43 192.168.122.209 [58654.503518] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 08:21:44 192.168.122.209 [58654.564629] [tempesta fw] 127.0.0.2 "default" "PUT / HTTP/2.0" 304 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800b40200" Apr 26 08:21:44 192.168.122.209 [58654.567757] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 08:21:44 192.168.122.209 [58654.582153] [tempesta fw] 127.0.0.2 "default" "PUT / HTTP/2.0" 400 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800b40200" Apr 26 08:21:44 192.168.122.209 [58654.583828] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 08:21:44 192.168.122.209 [58654.602438] [tempesta fw] 127.0.0.2 "default" "PUT / HTTP/2.0" 401 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800b40200" Apr 26 08:21:44 192.168.122.209 [58654.604208] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 08:21:44 192.168.122.209 [58654.664405] [tempesta fw] 127.0.0.2 "default" "PUT / HTTP/2.0" 404 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800b40200" Apr 26 08:21:44 192.168.122.209 [58654.667787] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 08:21:44 192.168.122.209 [58654.685599] [tempesta fw] 127.0.0.2 "default" "PUT / HTTP/2.0" 500 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=17800b40200" Apr 26 08:21:44 192.168.122.209 [58654.688236] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 08:21:44 192.168.122.209 [58655.132254] [tdb] Close table 'client0.tdb' Apr 26 08:21:44 192.168.122.209 [58655.322512] [tdb] Close table 'sessions0.tdb' Apr 26 08:21:48 192.168.122.209 [58658.561969] [tdb] Close table 'cache0.tdb' Apr 26 08:21:48 192.168.122.209 [58658.827229] [tdb] Close table 'filter0.tdb' Apr 26 08:21:48 192.168.122.209 [58658.827678] [tempesta fw] modules are stopped Apr 26 08:21:48 192.168.122.209 [58659.023207] [tempesta fw] exiting... Apr 26 08:21:48 192.168.122.209 [58659.163670] [tdb] Shutdown Tempesta DB Apr 26 08:21:48 192.168.122.209 [58659.382557] End test: http2_general.test_h2_headers.TestNoContentLengthInMethodMethodPUT.test_request_success Apr 26 08:21:48 192.168.122.209 [58659.406808] Start test: http2_general.test_h2_headers.TestPseudoHeaders.test_authority_with_scheme_and_path Apr 26 08:21:49 192.168.122.209 [58660.486596] [tdb] Start Tempesta DB Apr 26 08:21:50 192.168.122.209 [58660.658684] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:21:51 192.168.122.209 [58662.336591] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58662.336591] Maybe that's fine, but it's worth checking the [58662.336591] config - if there is no relations between the [58662.336591] names, then host name confusion attack is possible. Apr 26 08:21:51 192.168.122.209 [58662.498913] [tempesta fw] Configuration processing is completed. Apr 26 08:21:52 192.168.122.209 [58662.567749] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:21:52 192.168.122.209 [58663.030697] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:21:52 192.168.122.209 [58663.059402] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:21:52 192.168.122.209 [58663.090603] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:21:52 192.168.122.209 [58663.170902] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:21:52 192.168.122.209 [58663.210828] [tempesta fw] Tempesta FW is ready Apr 26 08:21:52 192.168.122.209 [58663.424427] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrPsAuthorityV input=0x68('https://example.'), len=30, off=0 Apr 26 08:21:53 192.168.122.209 [58663.839614] [tdb] Close table 'client0.tdb' Apr 26 08:21:53 192.168.122.209 [58664.050630] [tdb] Close table 'sessions0.tdb' Apr 26 08:21:56 192.168.122.209 [58667.314632] [tdb] Close table 'cache0.tdb' Apr 26 08:21:57 192.168.122.209 [58667.556092] [tdb] Close table 'filter0.tdb' Apr 26 08:21:57 192.168.122.209 [58667.556533] [tempesta fw] modules are stopped Apr 26 08:21:57 192.168.122.209 [58667.830568] [tempesta fw] exiting... Apr 26 08:21:57 192.168.122.209 [58667.962569] [tdb] Shutdown Tempesta DB Apr 26 08:21:57 192.168.122.209 [58668.181243] End test: http2_general.test_h2_headers.TestPseudoHeaders.test_authority_with_scheme_and_path Apr 26 08:21:57 192.168.122.209 [58668.203646] Start test: http2_general.test_h2_headers.TestPseudoHeaders.test_duplicate_pseudo_header Apr 26 08:21:58 192.168.122.209 [58669.311350] [tdb] Start Tempesta DB Apr 26 08:21:58 192.168.122.209 [58669.462523] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:22:00 192.168.122.209 [58671.084405] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58671.084405] Maybe that's fine, but it's worth checking the [58671.084405] config - if there is no relations between the [58671.084405] names, then host name confusion attack is possible. Apr 26 08:22:00 192.168.122.209 [58671.251027] [tempesta fw] Configuration processing is completed. Apr 26 08:22:00 192.168.122.209 [58671.301937] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:22:01 192.168.122.209 [58671.730037] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:22:01 192.168.122.209 [58671.757590] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:22:01 192.168.122.209 [58671.784791] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:22:01 192.168.122.209 [58671.834993] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:22:01 192.168.122.209 [58671.878977] [tempesta fw] Tempesta FW is ready Apr 26 08:22:01 192.168.122.209 [58672.511119] [tdb] Close table 'client0.tdb' Apr 26 08:22:02 192.168.122.209 [58672.785087] [tdb] Close table 'sessions0.tdb' Apr 26 08:22:05 192.168.122.209 [58675.989065] [tdb] Close table 'cache0.tdb' Apr 26 08:22:05 192.168.122.209 [58676.259515] [tdb] Close table 'filter0.tdb' Apr 26 08:22:05 192.168.122.209 [58676.259950] [tempesta fw] modules are stopped Apr 26 08:22:05 192.168.122.209 [58676.469898] [tempesta fw] exiting... Apr 26 08:22:06 192.168.122.209 [58676.612351] [tdb] Shutdown Tempesta DB Apr 26 08:22:06 192.168.122.209 [58676.849761] End test: http2_general.test_h2_headers.TestPseudoHeaders.test_duplicate_pseudo_header Apr 26 08:22:06 192.168.122.209 [58676.870492] Start test: http2_general.test_h2_headers.TestPseudoHeaders.test_invalid_pseudo_header Apr 26 08:22:07 192.168.122.209 [58677.919989] [tdb] Start Tempesta DB Apr 26 08:22:07 192.168.122.209 [58678.052998] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:22:09 192.168.122.209 [58679.724629] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58679.724629] Maybe that's fine, but it's worth checking the [58679.724629] config - if there is no relations between the [58679.724629] names, then host name confusion attack is possible. Apr 26 08:22:09 192.168.122.209 [58679.887130] [tempesta fw] Configuration processing is completed. Apr 26 08:22:09 192.168.122.209 [58679.940890] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:22:09 192.168.122.209 [58680.375945] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:22:09 192.168.122.209 [58680.404460] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:22:09 192.168.122.209 [58680.431367] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:22:09 192.168.122.209 [58680.487100] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:22:09 192.168.122.209 [58680.527050] [tempesta fw] Tempesta FW is ready Apr 26 08:22:10 192.168.122.209 [58680.732305] [tempesta fw] Warning: HTTP/2 request dropped: state=RGen_HdrOtherN input=0x3a(':content-length'), len=15, off=0 Apr 26 08:22:10 192.168.122.209 [58681.166784] [tdb] Close table 'client0.tdb' Apr 26 08:22:10 192.168.122.209 [58681.354836] [tdb] Close table 'sessions0.tdb' Apr 26 08:22:13 192.168.122.209 [58684.526026] [tdb] Close table 'cache0.tdb' Apr 26 08:22:14 192.168.122.209 [58684.801576] [tdb] Close table 'filter0.tdb' Apr 26 08:22:14 192.168.122.209 [58684.802006] [tempesta fw] modules are stopped Apr 26 08:22:14 192.168.122.209 [58684.999466] [tempesta fw] exiting... Apr 26 08:22:14 192.168.122.209 [58685.131467] [tdb] Shutdown Tempesta DB Apr 26 08:22:14 192.168.122.209 [58685.359103] End test: http2_general.test_h2_headers.TestPseudoHeaders.test_invalid_pseudo_header Apr 26 08:22:14 192.168.122.209 [58685.376136] Start test: http2_general.test_h2_headers.TestPseudoHeaders.test_regular_header_before_pseudo_header Apr 26 08:22:15 192.168.122.209 [58686.399740] [tdb] Start Tempesta DB Apr 26 08:22:16 192.168.122.209 [58686.546537] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:22:17 192.168.122.209 [58688.152731] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58688.152731] Maybe that's fine, but it's worth checking the [58688.152731] config - if there is no relations between the [58688.152731] names, then host name confusion attack is possible. Apr 26 08:22:17 192.168.122.209 [58688.303441] [tempesta fw] Configuration processing is completed. Apr 26 08:22:17 192.168.122.209 [58688.359951] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:22:18 192.168.122.209 [58688.783882] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:22:18 192.168.122.209 [58688.810726] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:22:18 192.168.122.209 [58688.837551] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:22:18 192.168.122.209 [58688.879198] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:22:18 192.168.122.209 [58688.923153] [tempesta fw] Tempesta FW is ready Apr 26 08:22:18 192.168.122.209 [58689.133274] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrContent_LengthV input=0x30('0'), len=1, off=0 Apr 26 08:22:19 192.168.122.209 [58689.564472] [tdb] Close table 'client0.tdb' Apr 26 08:22:19 192.168.122.209 [58689.754731] [tdb] Close table 'sessions0.tdb' Apr 26 08:22:22 192.168.122.209 [58692.972064] [tdb] Close table 'cache0.tdb' Apr 26 08:22:22 192.168.122.209 [58693.224290] [tdb] Close table 'filter0.tdb' Apr 26 08:22:22 192.168.122.209 [58693.224719] [tempesta fw] modules are stopped Apr 26 08:22:22 192.168.122.209 [58693.479692] [tempesta fw] exiting... Apr 26 08:22:23 192.168.122.209 [58693.611594] [tdb] Shutdown Tempesta DB Apr 26 08:22:23 192.168.122.209 [58693.860530] End test: http2_general.test_h2_headers.TestPseudoHeaders.test_regular_header_before_pseudo_header Apr 26 08:22:23 192.168.122.209 [58693.884452] Start test: http2_general.test_h2_headers.TestPseudoHeaders.test_status_header_in_request Apr 26 08:22:24 192.168.122.209 [58694.914548] [tdb] Start Tempesta DB Apr 26 08:22:24 192.168.122.209 [58695.047754] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:22:26 192.168.122.209 [58696.624708] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58696.624708] Maybe that's fine, but it's worth checking the [58696.624708] config - if there is no relations between the [58696.624708] names, then host name confusion attack is possible. Apr 26 08:22:26 192.168.122.209 [58696.775323] [tempesta fw] Configuration processing is completed. Apr 26 08:22:26 192.168.122.209 [58696.838003] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:22:26 192.168.122.209 [58697.259622] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:22:26 192.168.122.209 [58697.286236] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:22:26 192.168.122.209 [58697.312666] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:22:26 192.168.122.209 [58697.359307] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:22:26 192.168.122.209 [58697.403250] [tempesta fw] Tempesta FW is ready Apr 26 08:22:27 192.168.122.209 [58698.036651] [tdb] Close table 'client0.tdb' Apr 26 08:22:27 192.168.122.209 [58698.237266] [tdb] Close table 'sessions0.tdb' Apr 26 08:22:30 192.168.122.209 [58701.404785] [tdb] Close table 'cache0.tdb' Apr 26 08:22:31 192.168.122.209 [58701.647251] [tdb] Close table 'filter0.tdb' Apr 26 08:22:31 192.168.122.209 [58701.647677] [tempesta fw] modules are stopped Apr 26 08:22:31 192.168.122.209 [58701.852555] [tempesta fw] exiting... Apr 26 08:22:31 192.168.122.209 [58701.976637] [tdb] Shutdown Tempesta DB Apr 26 08:22:31 192.168.122.209 [58702.189105] End test: http2_general.test_h2_headers.TestPseudoHeaders.test_status_header_in_request Apr 26 08:22:31 192.168.122.209 [58702.213357] Start test: http2_general.test_h2_headers.TestSplitCookies.test_split_cookies Apr 26 08:22:32 192.168.122.209 [58703.274689] [tdb] Start Tempesta DB Apr 26 08:22:32 192.168.122.209 [58703.405467] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:22:34 192.168.122.209 [58705.044839] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58705.044839] Maybe that's fine, but it's worth checking the [58705.044839] config - if there is no relations between the [58705.044839] names, then host name confusion attack is possible. Apr 26 08:22:34 192.168.122.209 [58705.199412] [tempesta fw] Configuration processing is completed. Apr 26 08:22:34 192.168.122.209 [58705.258061] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:22:35 192.168.122.209 [58705.689358] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:22:35 192.168.122.209 [58705.726982] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:22:35 192.168.122.209 [58705.754132] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:22:35 192.168.122.209 [58705.795401] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:22:35 192.168.122.209 [58705.843378] [tempesta fw] Tempesta FW is ready Apr 26 08:22:35 192.168.122.209 [58706.455495] [tdb] Close table 'client0.tdb' Apr 26 08:22:36 192.168.122.209 [58706.642840] [tdb] Close table 'sessions0.tdb' Apr 26 08:22:39 192.168.122.209 [58709.848306] [tdb] Close table 'cache0.tdb' Apr 26 08:22:39 192.168.122.209 [58710.079430] [tdb] Close table 'filter0.tdb' Apr 26 08:22:39 192.168.122.209 [58710.079868] [tempesta fw] modules are stopped Apr 26 08:22:39 192.168.122.209 [58710.315990] [tempesta fw] exiting... Apr 26 08:22:39 192.168.122.209 [58710.434265] [tdb] Shutdown Tempesta DB Apr 26 08:22:40 192.168.122.209 [58710.627480] End test: http2_general.test_h2_headers.TestSplitCookies.test_split_cookies Apr 26 08:22:40 192.168.122.209 [58710.652073] Start test: http2_general.test_h2_headers.TestTrailers.test_trailers_in_request_trailer Apr 26 08:22:41 192.168.122.209 [58711.738452] [tdb] Start Tempesta DB Apr 26 08:22:41 192.168.122.209 [58711.877018] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:22:43 192.168.122.209 [58713.564952] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58713.564952] Maybe that's fine, but it's worth checking the [58713.564952] config - if there is no relations between the [58713.564952] names, then host name confusion attack is possible. Apr 26 08:22:43 192.168.122.209 [58713.743523] [tempesta fw] Configuration processing is completed. Apr 26 08:22:43 192.168.122.209 [58713.800707] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:22:43 192.168.122.209 [58714.215383] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:22:43 192.168.122.209 [58714.242212] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:22:43 192.168.122.209 [58714.268927] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:22:43 192.168.122.209 [58714.323566] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:22:43 192.168.122.209 [58714.367464] [tempesta fw] Tempesta FW is ready Apr 26 08:22:44 192.168.122.209 [58715.024444] [tdb] Close table 'client0.tdb' Apr 26 08:22:44 192.168.122.209 [58715.211093] [tdb] Close table 'sessions0.tdb' Apr 26 08:22:47 192.168.122.209 [58718.490702] [tdb] Close table 'cache0.tdb' Apr 26 08:22:48 192.168.122.209 [58718.736388] [tdb] Close table 'filter0.tdb' Apr 26 08:22:48 192.168.122.209 [58718.736841] [tempesta fw] modules are stopped Apr 26 08:22:48 192.168.122.209 [58718.960103] [tempesta fw] exiting... Apr 26 08:22:48 192.168.122.209 [58719.073780] [tdb] Shutdown Tempesta DB Apr 26 08:22:48 192.168.122.209 [58719.277912] End test: http2_general.test_h2_headers.TestTrailers.test_trailers_in_request_trailer Apr 26 08:22:48 192.168.122.209 [58719.296448] Start test: http2_general.test_h2_headers.TestTrailers.test_trailers_in_request_trailer_mix_1 Apr 26 08:22:49 192.168.122.209 [58720.333592] [tdb] Start Tempesta DB Apr 26 08:22:49 192.168.122.209 [58720.466606] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:22:51 192.168.122.209 [58722.101022] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58722.101022] Maybe that's fine, but it's worth checking the [58722.101022] config - if there is no relations between the [58722.101022] names, then host name confusion attack is possible. Apr 26 08:22:51 192.168.122.209 [58722.255719] [tempesta fw] Configuration processing is completed. Apr 26 08:22:51 192.168.122.209 [58722.310885] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:22:52 192.168.122.209 [58722.797673] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:22:52 192.168.122.209 [58722.836348] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:22:52 192.168.122.209 [58722.870237] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:22:52 192.168.122.209 [58722.907624] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:22:52 192.168.122.209 [58722.951566] [tempesta fw] Tempesta FW is ready Apr 26 08:22:52 192.168.122.209 [58723.167127] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrConnection input=0x63('connection'), len=10, off=0 Apr 26 08:22:53 192.168.122.209 [58723.609581] [tdb] Close table 'client0.tdb' Apr 26 08:22:53 192.168.122.209 [58723.801615] [tdb] Close table 'sessions0.tdb' Apr 26 08:22:56 192.168.122.209 [58727.034763] [tdb] Close table 'cache0.tdb' Apr 26 08:22:56 192.168.122.209 [58727.271735] [tdb] Close table 'filter0.tdb' Apr 26 08:22:56 192.168.122.209 [58727.272159] [tempesta fw] modules are stopped Apr 26 08:22:56 192.168.122.209 [58727.516006] [tempesta fw] exiting... Apr 26 08:22:57 192.168.122.209 [58727.654826] [tdb] Shutdown Tempesta DB Apr 26 08:22:57 192.168.122.209 [58727.902433] End test: http2_general.test_h2_headers.TestTrailers.test_trailers_in_request_trailer_mix_1 Apr 26 08:22:57 192.168.122.209 [58727.914898] Start test: http2_general.test_h2_headers.TestTrailers.test_trailers_in_request_trailer_mix_2 Apr 26 08:22:58 192.168.122.209 [58728.989711] [tdb] Start Tempesta DB Apr 26 08:22:58 192.168.122.209 [58729.134264] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:23:00 192.168.122.209 [58730.833421] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58730.833421] Maybe that's fine, but it's worth checking the [58730.833421] config - if there is no relations between the [58730.833421] names, then host name confusion attack is possible. Apr 26 08:23:00 192.168.122.209 [58730.999756] [tempesta fw] Configuration processing is completed. Apr 26 08:23:00 192.168.122.209 [58731.066722] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:23:01 192.168.122.209 [58731.558394] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:23:01 192.168.122.209 [58731.589776] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:23:01 192.168.122.209 [58731.619993] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:23:01 192.168.122.209 [58731.671758] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:23:01 192.168.122.209 [58731.711705] [tempesta fw] Tempesta FW is ready Apr 26 08:23:01 192.168.122.209 [58731.930908] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrKeep_Alive input=0x6b('keep-alive'), len=10, off=0 Apr 26 08:23:01 192.168.122.209 [58732.362555] [tdb] Close table 'client0.tdb' Apr 26 08:23:02 192.168.122.209 [58732.551027] [tdb] Close table 'sessions0.tdb' Apr 26 08:23:05 192.168.122.209 [58735.775477] [tdb] Close table 'cache0.tdb' Apr 26 08:23:05 192.168.122.209 [58736.014190] [tdb] Close table 'filter0.tdb' Apr 26 08:23:05 192.168.122.209 [58736.014620] [tempesta fw] modules are stopped Apr 26 08:23:05 192.168.122.209 [58736.233258] [tempesta fw] exiting... Apr 26 08:23:05 192.168.122.209 [58736.366077] [tdb] Shutdown Tempesta DB Apr 26 08:23:06 192.168.122.209 [58736.599112] End test: http2_general.test_h2_headers.TestTrailers.test_trailers_in_request_trailer_mix_2 Apr 26 08:23:06 192.168.122.209 [58736.624184] Start test: http2_general.test_h2_headers.TestTrailers.test_trailers_in_request_trailer_mix_3 Apr 26 08:23:07 192.168.122.209 [58737.737427] [tdb] Start Tempesta DB Apr 26 08:23:07 192.168.122.209 [58737.894552] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:23:08 192.168.122.209 [58739.521955] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58739.521955] Maybe that's fine, but it's worth checking the [58739.521955] config - if there is no relations between the [58739.521955] names, then host name confusion attack is possible. Apr 26 08:23:09 192.168.122.209 [58739.683748] [tempesta fw] Configuration processing is completed. Apr 26 08:23:09 192.168.122.209 [58739.733978] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:23:09 192.168.122.209 [58740.154239] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:23:09 192.168.122.209 [58740.180917] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:23:09 192.168.122.209 [58740.207748] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:23:09 192.168.122.209 [58740.251787] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:23:09 192.168.122.209 [58740.291819] [tempesta fw] Tempesta FW is ready Apr 26 08:23:09 192.168.122.209 [58740.514184] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrUpgrade input=0x75('upgrade'), len=7, off=0 Apr 26 08:23:10 192.168.122.209 [58740.939605] [tdb] Close table 'client0.tdb' Apr 26 08:23:10 192.168.122.209 [58741.131217] [tdb] Close table 'sessions0.tdb' Apr 26 08:23:13 192.168.122.209 [58744.296251] [tdb] Close table 'cache0.tdb' Apr 26 08:23:13 192.168.122.209 [58744.527284] [tdb] Close table 'filter0.tdb' Apr 26 08:23:13 192.168.122.209 [58744.527752] [tempesta fw] modules are stopped Apr 26 08:23:14 192.168.122.209 [58744.770675] [tempesta fw] exiting... Apr 26 08:23:14 192.168.122.209 [58744.906933] [tdb] Shutdown Tempesta DB Apr 26 08:23:14 192.168.122.209 [58745.128183] End test: http2_general.test_h2_headers.TestTrailers.test_trailers_in_request_trailer_mix_3 Apr 26 08:23:14 192.168.122.209 [58745.155466] Start test: http2_general.test_h2_headers.TestTrailers.test_trailers_in_request_trailer_mix_4 Apr 26 08:23:15 192.168.122.209 [58746.158412] [tdb] Start Tempesta DB Apr 26 08:23:15 192.168.122.209 [58746.301350] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:23:17 192.168.122.209 [58747.873383] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58747.873383] Maybe that's fine, but it's worth checking the [58747.873383] config - if there is no relations between the [58747.873383] names, then host name confusion attack is possible. Apr 26 08:23:17 192.168.122.209 [58748.027977] [tempesta fw] Configuration processing is completed. Apr 26 08:23:17 192.168.122.209 [58748.077962] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:23:17 192.168.122.209 [58748.509384] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:23:17 192.168.122.209 [58748.536646] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:23:18 192.168.122.209 [58748.563673] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:23:18 192.168.122.209 [58748.615942] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:23:18 192.168.122.209 [58748.663905] [tempesta fw] Tempesta FW is ready Apr 26 08:23:18 192.168.122.209 [58748.872772] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrTeV input=0x63('chunked'), len=7, off=0 Apr 26 08:23:18 192.168.122.209 [58749.291851] [tdb] Close table 'client0.tdb' Apr 26 08:23:18 192.168.122.209 [58749.483588] [tdb] Close table 'sessions0.tdb' Apr 26 08:23:22 192.168.122.209 [58752.667919] [tdb] Close table 'cache0.tdb' Apr 26 08:23:22 192.168.122.209 [58752.926286] [tdb] Close table 'filter0.tdb' Apr 26 08:23:22 192.168.122.209 [58752.926708] [tempesta fw] modules are stopped Apr 26 08:23:22 192.168.122.209 [58753.161678] [tempesta fw] exiting... Apr 26 08:23:22 192.168.122.209 [58753.293987] [tdb] Shutdown Tempesta DB Apr 26 08:23:22 192.168.122.209 [58753.519254] End test: http2_general.test_h2_headers.TestTrailers.test_trailers_in_request_trailer_mix_4 Apr 26 08:23:22 192.168.122.209 [58753.542901] Start test: http2_general.test_h2_headers.TestTrailers.test_trailers_in_request_trailer_with_hbp Apr 26 08:23:24 192.168.122.209 [58754.631103] [tdb] Start Tempesta DB Apr 26 08:23:24 192.168.122.209 [58754.767819] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:23:25 192.168.122.209 [58756.349504] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58756.349504] Maybe that's fine, but it's worth checking the [58756.349504] config - if there is no relations between the [58756.349504] names, then host name confusion attack is possible. Apr 26 08:23:25 192.168.122.209 [58756.516073] [tempesta fw] Configuration processing is completed. Apr 26 08:23:26 192.168.122.209 [58756.566603] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:23:26 192.168.122.209 [58756.994185] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:23:26 192.168.122.209 [58757.022651] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:23:26 192.168.122.209 [58757.049716] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:23:26 192.168.122.209 [58757.092050] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:23:26 192.168.122.209 [58757.132010] [tempesta fw] Tempesta FW is ready Apr 26 08:23:26 192.168.122.209 [58757.357474] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrConnection input=0x63('connection'), len=10, off=0 Apr 26 08:23:27 192.168.122.209 [58757.770416] [tdb] Close table 'client0.tdb' Apr 26 08:23:27 192.168.122.209 [58757.977383] [tdb] Close table 'sessions0.tdb' Apr 26 08:23:30 192.168.122.209 [58761.223505] [tdb] Close table 'cache0.tdb' Apr 26 08:23:30 192.168.122.209 [58761.457848] [tdb] Close table 'filter0.tdb' Apr 26 08:23:30 192.168.122.209 [58761.458321] [tempesta fw] modules are stopped Apr 26 08:23:31 192.168.122.209 [58761.653140] [tempesta fw] exiting... Apr 26 08:23:31 192.168.122.209 [58761.785131] [tdb] Shutdown Tempesta DB Apr 26 08:23:31 192.168.122.209 [58762.017640] End test: http2_general.test_h2_headers.TestTrailers.test_trailers_in_request_trailer_with_hbp Apr 26 08:23:31 192.168.122.209 [58762.039540] Start test: http2_general.test_h2_headers.TestTrailers.test_trailers_in_response_empty_body Apr 26 08:23:32 192.168.122.209 [58763.138585] [tdb] Start Tempesta DB Apr 26 08:23:32 192.168.122.209 [58763.279521] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:23:34 192.168.122.209 [58764.848953] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58764.848953] Maybe that's fine, but it's worth checking the [58764.848953] config - if there is no relations between the [58764.848953] names, then host name confusion attack is possible. Apr 26 08:23:34 192.168.122.209 [58765.004178] [tempesta fw] Configuration processing is completed. Apr 26 08:23:34 192.168.122.209 [58765.055375] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:23:34 192.168.122.209 [58765.470466] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:23:34 192.168.122.209 [58765.497212] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:23:34 192.168.122.209 [58765.524214] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:23:35 192.168.122.209 [58765.572168] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:23:35 192.168.122.209 [58765.628111] [tempesta fw] Tempesta FW is ready Apr 26 08:23:35 192.168.122.209 [58766.276604] [tdb] Close table 'client0.tdb' Apr 26 08:23:35 192.168.122.209 [58766.461421] [tdb] Close table 'sessions0.tdb' Apr 26 08:23:39 192.168.122.209 [58769.633581] [tdb] Close table 'cache0.tdb' Apr 26 08:23:39 192.168.122.209 [58769.866903] [tdb] Close table 'filter0.tdb' Apr 26 08:23:39 192.168.122.209 [58769.867330] [tempesta fw] modules are stopped Apr 26 08:23:39 192.168.122.209 [58770.076950] [tempesta fw] exiting... Apr 26 08:23:39 192.168.122.209 [58770.249050] [tdb] Shutdown Tempesta DB Apr 26 08:23:39 192.168.122.209 [58770.437036] End test: http2_general.test_h2_headers.TestTrailers.test_trailers_in_response_empty_body Apr 26 08:23:39 192.168.122.209 [58770.456874] Start test: http2_general.test_h2_headers.TestTrailers.test_trailers_in_response_not_empty_body Apr 26 08:23:40 192.168.122.209 [58771.492137] [tdb] Start Tempesta DB Apr 26 08:23:41 192.168.122.209 [58771.627617] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:23:42 192.168.122.209 [58773.285091] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58773.285091] Maybe that's fine, but it's worth checking the [58773.285091] config - if there is no relations between the [58773.285091] names, then host name confusion attack is possible. Apr 26 08:23:42 192.168.122.209 [58773.436263] [tempesta fw] Configuration processing is completed. Apr 26 08:23:42 192.168.122.209 [58773.486639] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:23:43 192.168.122.209 [58773.907372] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:23:43 192.168.122.209 [58773.934212] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:23:43 192.168.122.209 [58773.960751] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:23:43 192.168.122.209 [58774.004289] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:23:43 192.168.122.209 [58774.068215] [tempesta fw] Tempesta FW is ready Apr 26 08:23:44 192.168.122.209 [58774.694598] [tdb] Close table 'client0.tdb' Apr 26 08:23:44 192.168.122.209 [58774.916905] [tdb] Close table 'sessions0.tdb' Apr 26 08:23:47 192.168.122.209 [58778.130052] [tdb] Close table 'cache0.tdb' Apr 26 08:23:47 192.168.122.209 [58778.371046] [tdb] Close table 'filter0.tdb' Apr 26 08:23:47 192.168.122.209 [58778.371513] [tempesta fw] modules are stopped Apr 26 08:23:48 192.168.122.209 [58778.593571] [tempesta fw] exiting... Apr 26 08:23:48 192.168.122.209 [58778.737693] [tdb] Shutdown Tempesta DB Apr 26 08:23:48 192.168.122.209 [58778.941579] End test: http2_general.test_h2_headers.TestTrailers.test_trailers_in_response_not_empty_body Apr 26 08:23:48 192.168.122.209 [58778.960685] Start test: http2_general.test_h2_headers.TestTrailers.test_trailers_invalid_header_in_request Apr 26 08:23:49 192.168.122.209 [58779.970701] [tdb] Start Tempesta DB Apr 26 08:23:49 192.168.122.209 [58780.105761] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:23:51 192.168.122.209 [58781.761811] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58781.761811] Maybe that's fine, but it's worth checking the [58781.761811] config - if there is no relations between the [58781.761811] names, then host name confusion attack is possible. Apr 26 08:23:51 192.168.122.209 [58781.916372] [tempesta fw] Configuration processing is completed. Apr 26 08:23:51 192.168.122.209 [58781.966502] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:23:51 192.168.122.209 [58782.393386] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:23:51 192.168.122.209 [58782.428523] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:23:51 192.168.122.209 [58782.455444] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:23:51 192.168.122.209 [58782.516381] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:23:52 192.168.122.209 [58782.556316] [tempesta fw] Tempesta FW is ready Apr 26 08:23:53 192.168.122.209 [58783.780109] [tdb] Close table 'client0.tdb' Apr 26 08:23:53 192.168.122.209 [58783.982041] [tdb] Close table 'sessions0.tdb' Apr 26 08:23:56 192.168.122.209 [58787.164733] [tdb] Close table 'cache0.tdb' Apr 26 08:23:56 192.168.122.209 [58787.406935] [tdb] Close table 'filter0.tdb' Apr 26 08:23:56 192.168.122.209 [58787.407364] [tempesta fw] modules are stopped Apr 26 08:23:57 192.168.122.209 [58787.625006] [tempesta fw] exiting... Apr 26 08:23:57 192.168.122.209 [58787.775834] [tdb] Shutdown Tempesta DB Apr 26 08:23:57 192.168.122.209 [58787.998964] End test: http2_general.test_h2_headers.TestTrailers.test_trailers_invalid_header_in_request Apr 26 08:23:57 192.168.122.209 [58788.022558] Start test: http2_general.test_h2_headers.TestTrailers.test_trailers_with_continuation_frame_in_request Apr 26 08:23:58 192.168.122.209 [58789.038150] [tdb] Start Tempesta DB Apr 26 08:23:58 192.168.122.209 [58789.177318] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:24:00 192.168.122.209 [58790.821885] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58790.821885] Maybe that's fine, but it's worth checking the [58790.821885] config - if there is no relations between the [58790.821885] names, then host name confusion attack is possible. Apr 26 08:24:00 192.168.122.209 [58790.976513] [tempesta fw] Configuration processing is completed. Apr 26 08:24:00 192.168.122.209 [58791.035386] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:24:00 192.168.122.209 [58791.454086] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:24:00 192.168.122.209 [58791.488488] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:24:00 192.168.122.209 [58791.515373] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:24:01 192.168.122.209 [58791.564486] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:24:01 192.168.122.209 [58791.612428] [tempesta fw] Tempesta FW is ready Apr 26 08:24:01 192.168.122.209 [58792.280418] [tdb] Close table 'client0.tdb' Apr 26 08:24:01 192.168.122.209 [58792.465483] [tdb] Close table 'sessions0.tdb' Apr 26 08:24:06 192.168.122.209 [58796.945720] [tdb] Close table 'cache0.tdb' Apr 26 08:24:07 192.168.122.209 [58797.716968] [tdb] Close table 'filter0.tdb' Apr 26 08:24:07 192.168.122.209 [58797.717412] [tempesta fw] modules are stopped Apr 26 08:24:08 192.168.122.209 [58799.303633] [tempesta fw] exiting... Apr 26 08:24:09 192.168.122.209 [58799.855732] [tdb] Shutdown Tempesta DB Apr 26 08:24:09 192.168.122.209 [58800.076616] End test: http2_general.test_h2_headers.TestTrailers.test_trailers_with_continuation_frame_in_request Apr 26 08:24:09 192.168.122.209 [58800.091489] Start test: http2_general.test_h2_headers.TestTrailers.test_trailers_with_empty_continuation_frame_in_request_end_headers Apr 26 08:24:10 192.168.122.209 [58801.184902] [tdb] Start Tempesta DB Apr 26 08:24:10 192.168.122.209 [58801.322251] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:24:12 192.168.122.209 [58802.817460] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58802.817460] Maybe that's fine, but it's worth checking the [58802.817460] config - if there is no relations between the [58802.817460] names, then host name confusion attack is possible. Apr 26 08:24:12 192.168.122.209 [58802.976683] [tempesta fw] Configuration processing is completed. Apr 26 08:24:12 192.168.122.209 [58803.029282] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:24:12 192.168.122.209 [58803.459791] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:24:12 192.168.122.209 [58803.486998] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:24:12 192.168.122.209 [58803.515537] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:24:13 192.168.122.209 [58803.560621] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:24:13 192.168.122.209 [58803.616591] [tempesta fw] Tempesta FW is ready Apr 26 08:24:13 192.168.122.209 [58804.229876] [tdb] Close table 'client0.tdb' Apr 26 08:24:13 192.168.122.209 [58804.434956] [tdb] Close table 'sessions0.tdb' Apr 26 08:24:17 192.168.122.209 [58807.591609] [tdb] Close table 'cache0.tdb' Apr 26 08:24:17 192.168.122.209 [58807.833524] [tdb] Close table 'filter0.tdb' Apr 26 08:24:17 192.168.122.209 [58807.833961] [tempesta fw] modules are stopped Apr 26 08:24:17 192.168.122.209 [58808.057027] [tempesta fw] exiting... Apr 26 08:24:17 192.168.122.209 [58808.175635] [tdb] Shutdown Tempesta DB Apr 26 08:24:17 192.168.122.209 [58808.405713] End test: http2_general.test_h2_headers.TestTrailers.test_trailers_with_empty_continuation_frame_in_request_end_headers Apr 26 08:24:17 192.168.122.209 [58808.418527] Start test: http2_general.test_h2_headers.TestTrailers.test_trailers_with_empty_continuation_frame_in_request_no_end_headers Apr 26 08:24:18 192.168.122.209 [58809.474447] [tdb] Start Tempesta DB Apr 26 08:24:19 192.168.122.209 [58809.622318] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:24:20 192.168.122.209 [58811.222210] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58811.222210] Maybe that's fine, but it's worth checking the [58811.222210] config - if there is no relations between the [58811.222210] names, then host name confusion attack is possible. Apr 26 08:24:20 192.168.122.209 [58811.380802] [tempesta fw] Configuration processing is completed. Apr 26 08:24:20 192.168.122.209 [58811.430748] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:24:21 192.168.122.209 [58811.856052] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:24:21 192.168.122.209 [58811.883299] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:24:21 192.168.122.209 [58811.910592] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:24:21 192.168.122.209 [58811.960755] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:24:21 192.168.122.209 [58812.000697] [tempesta fw] Tempesta FW is ready Apr 26 08:24:22 192.168.122.209 [58812.218403] [tempesta fw] Empty CONTINUATION frame without END_HEADERS Apr 26 08:24:22 192.168.122.209 [58812.621425] [tdb] Close table 'client0.tdb' Apr 26 08:24:22 192.168.122.209 [58812.810899] [tdb] Close table 'sessions0.tdb' Apr 26 08:24:25 192.168.122.209 [58816.013113] [tdb] Close table 'cache0.tdb' Apr 26 08:24:25 192.168.122.209 [58816.252198] [tdb] Close table 'filter0.tdb' Apr 26 08:24:25 192.168.122.209 [58816.252663] [tempesta fw] modules are stopped Apr 26 08:24:25 192.168.122.209 [58816.486330] [tempesta fw] exiting... Apr 26 08:24:26 192.168.122.209 [58816.617011] [tdb] Shutdown Tempesta DB Apr 26 08:24:26 192.168.122.209 [58816.827432] End test: http2_general.test_h2_headers.TestTrailers.test_trailers_with_empty_continuation_frame_in_request_no_end_headers Apr 26 08:24:26 192.168.122.209 [58816.856451] Start test: http2_general.test_h2_headers.TestTrailers.test_trailers_with_pseudo_headers_in_request Apr 26 08:24:27 192.168.122.209 [58817.912649] [tdb] Start Tempesta DB Apr 26 08:24:27 192.168.122.209 [58818.062090] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:24:29 192.168.122.209 [58819.698439] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58819.698439] Maybe that's fine, but it's worth checking the [58819.698439] config - if there is no relations between the [58819.698439] names, then host name confusion attack is possible. Apr 26 08:24:29 192.168.122.209 [58819.852871] [tempesta fw] Configuration processing is completed. Apr 26 08:24:29 192.168.122.209 [58819.902997] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:24:29 192.168.122.209 [58820.323645] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:24:29 192.168.122.209 [58820.354864] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:24:29 192.168.122.209 [58820.381742] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:24:29 192.168.122.209 [58820.436844] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:24:29 192.168.122.209 [58820.480812] [tempesta fw] Tempesta FW is ready Apr 26 08:24:30 192.168.122.209 [58821.129780] [tdb] Close table 'client0.tdb' Apr 26 08:24:30 192.168.122.209 [58821.316252] [tdb] Close table 'sessions0.tdb' Apr 26 08:24:34 192.168.122.209 [58824.552954] [tdb] Close table 'cache0.tdb' Apr 26 08:24:34 192.168.122.209 [58824.796307] [tdb] Close table 'filter0.tdb' Apr 26 08:24:34 192.168.122.209 [58824.796761] [tempesta fw] modules are stopped Apr 26 08:24:34 192.168.122.209 [58825.023699] [tempesta fw] exiting... Apr 26 08:24:34 192.168.122.209 [58825.136136] [tdb] Shutdown Tempesta DB Apr 26 08:24:34 192.168.122.209 [58825.341063] End test: http2_general.test_h2_headers.TestTrailers.test_trailers_with_pseudo_headers_in_request Apr 26 08:24:34 192.168.122.209 [58825.371546] Start test: http2_general.test_h2_headers.TestTrailers.test_trailers_without_end_stream_in_request Apr 26 08:24:35 192.168.122.209 [58826.444641] [tdb] Start Tempesta DB Apr 26 08:24:36 192.168.122.209 [58826.589221] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:24:37 192.168.122.209 [58828.182364] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58828.182364] Maybe that's fine, but it's worth checking the [58828.182364] config - if there is no relations between the [58828.182364] names, then host name confusion attack is possible. Apr 26 08:24:37 192.168.122.209 [58828.332958] [tempesta fw] Configuration processing is completed. Apr 26 08:24:37 192.168.122.209 [58828.384797] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:24:38 192.168.122.209 [58828.808585] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:24:38 192.168.122.209 [58828.836703] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:24:38 192.168.122.209 [58828.872521] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:24:38 192.168.122.209 [58828.920936] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:24:38 192.168.122.209 [58828.968854] [tempesta fw] Tempesta FW is ready Apr 26 08:24:39 192.168.122.209 [58829.579333] [tdb] Close table 'client0.tdb' Apr 26 08:24:39 192.168.122.209 [58829.778431] [tdb] Close table 'sessions0.tdb' Apr 26 08:24:42 192.168.122.209 [58832.982278] [tdb] Close table 'cache0.tdb' Apr 26 08:24:42 192.168.122.209 [58833.233794] [tdb] Close table 'filter0.tdb' Apr 26 08:24:42 192.168.122.209 [58833.234226] [tempesta fw] modules are stopped Apr 26 08:24:42 192.168.122.209 [58833.458095] [tempesta fw] exiting... Apr 26 08:24:43 192.168.122.209 [58833.573810] [tdb] Shutdown Tempesta DB Apr 26 08:24:43 192.168.122.209 [58833.810531] End test: http2_general.test_h2_headers.TestTrailers.test_trailers_without_end_stream_in_request Apr 26 08:24:43 192.168.122.209 [58833.832016] Start test: http2_general.test_h2_hpack.TestFramePayloadLength.test_invalid_data Apr 26 08:24:44 192.168.122.209 [58834.892107] [tdb] Start Tempesta DB Apr 26 08:24:44 192.168.122.209 [58835.029074] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:24:46 192.168.122.209 [58836.662465] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58836.662465] Maybe that's fine, but it's worth checking the [58836.662465] config - if there is no relations between the [58836.662465] names, then host name confusion attack is possible. Apr 26 08:24:46 192.168.122.209 [58836.809009] [tempesta fw] Configuration processing is completed. Apr 26 08:24:46 192.168.122.209 [58836.862230] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:24:46 192.168.122.209 [58837.279555] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:24:46 192.168.122.209 [58837.306157] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:24:46 192.168.122.209 [58837.332391] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:24:46 192.168.122.209 [58837.381021] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:24:46 192.168.122.209 [58837.425024] [tempesta fw] Tempesta FW is ready Apr 26 08:24:47 192.168.122.209 [58838.046037] [tdb] Close table 'client0.tdb' Apr 26 08:24:47 192.168.122.209 [58838.249577] [tdb] Close table 'sessions0.tdb' Apr 26 08:24:50 192.168.122.209 [58841.421312] [tdb] Close table 'cache0.tdb' Apr 26 08:24:51 192.168.122.209 [58841.652244] [tdb] Close table 'filter0.tdb' Apr 26 08:24:51 192.168.122.209 [58841.652664] [tempesta fw] modules are stopped Apr 26 08:24:51 192.168.122.209 [58841.889245] [tempesta fw] exiting... Apr 26 08:24:51 192.168.122.209 [58841.999523] [tdb] Shutdown Tempesta DB Apr 26 08:24:51 192.168.122.209 [58842.223974] End test: http2_general.test_h2_hpack.TestFramePayloadLength.test_invalid_data Apr 26 08:24:51 192.168.122.209 [58842.257328] Start test: http2_general.test_h2_hpack.TestFramePayloadLength.test_large_frame_payload_length Apr 26 08:24:52 192.168.122.209 [58843.284736] [tdb] Start Tempesta DB Apr 26 08:24:52 192.168.122.209 [58843.406469] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:24:54 192.168.122.209 [58845.014568] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58845.014568] Maybe that's fine, but it's worth checking the [58845.014568] config - if there is no relations between the [58845.014568] names, then host name confusion attack is possible. Apr 26 08:24:54 192.168.122.209 [58845.161183] [tempesta fw] Configuration processing is completed. Apr 26 08:24:54 192.168.122.209 [58845.212563] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:24:55 192.168.122.209 [58845.636533] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:24:55 192.168.122.209 [58845.663318] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:24:55 192.168.122.209 [58845.689911] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:24:55 192.168.122.209 [58845.745156] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:24:55 192.168.122.209 [58845.781148] [tempesta fw] Tempesta FW is ready Apr 26 08:24:55 192.168.122.209 [58846.385037] [tdb] Close table 'client0.tdb' Apr 26 08:24:56 192.168.122.209 [58846.576510] [tdb] Close table 'sessions0.tdb' Apr 26 08:24:59 192.168.122.209 [58849.778590] [tdb] Close table 'cache0.tdb' Apr 26 08:24:59 192.168.122.209 [58850.033527] [tdb] Close table 'filter0.tdb' Apr 26 08:24:59 192.168.122.209 [58850.033975] [tempesta fw] modules are stopped Apr 26 08:24:59 192.168.122.209 [58850.237879] [tempesta fw] exiting... Apr 26 08:24:59 192.168.122.209 [58850.388022] [tdb] Shutdown Tempesta DB Apr 26 08:25:00 192.168.122.209 [58850.625790] End test: http2_general.test_h2_hpack.TestFramePayloadLength.test_large_frame_payload_length Apr 26 08:25:00 192.168.122.209 [58850.642259] Start test: http2_general.test_h2_hpack.TestFramePayloadLength.test_small_frame_payload_length Apr 26 08:25:01 192.168.122.209 [58851.677205] [tdb] Start Tempesta DB Apr 26 08:25:01 192.168.122.209 [58851.811002] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:25:02 192.168.122.209 [58853.354710] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58853.354710] Maybe that's fine, but it's worth checking the [58853.354710] config - if there is no relations between the [58853.354710] names, then host name confusion attack is possible. Apr 26 08:25:02 192.168.122.209 [58853.517272] [tempesta fw] Configuration processing is completed. Apr 26 08:25:03 192.168.122.209 [58853.566359] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:25:03 192.168.122.209 [58853.976790] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:25:03 192.168.122.209 [58854.014001] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:25:03 192.168.122.209 [58854.046403] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:25:03 192.168.122.209 [58854.093278] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:25:03 192.168.122.209 [58854.137160] [tempesta fw] Tempesta FW is ready Apr 26 08:25:04 192.168.122.209 [58854.835233] [tdb] Close table 'client0.tdb' Apr 26 08:25:04 192.168.122.209 [58855.022768] [tdb] Close table 'sessions0.tdb' Apr 26 08:25:07 192.168.122.209 [58858.250992] [tdb] Close table 'cache0.tdb' Apr 26 08:25:07 192.168.122.209 [58858.482211] [tdb] Close table 'filter0.tdb' Apr 26 08:25:07 192.168.122.209 [58858.482652] [tempesta fw] modules are stopped Apr 26 08:25:08 192.168.122.209 [58858.774502] [tempesta fw] exiting... Apr 26 08:25:08 192.168.122.209 [58858.867285] [tdb] Shutdown Tempesta DB Apr 26 08:25:08 192.168.122.209 [58859.094209] End test: http2_general.test_h2_hpack.TestFramePayloadLength.test_small_frame_payload_length Apr 26 08:25:08 192.168.122.209 [58859.107847] Start test: http2_general.test_h2_hpack.TestHpack.test_big_header_after_setting_header_table_size Apr 26 08:25:09 192.168.122.209 [58860.163264] [tdb] Start Tempesta DB Apr 26 08:25:09 192.168.122.209 [58860.306651] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:25:11 192.168.122.209 [58861.886791] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58861.886791] Maybe that's fine, but it's worth checking the [58861.886791] config - if there is no relations between the [58861.886791] names, then host name confusion attack is possible. Apr 26 08:25:11 192.168.122.209 [58862.045401] [tempesta fw] Configuration processing is completed. Apr 26 08:25:11 192.168.122.209 [58862.097038] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:25:11 192.168.122.209 [58862.522912] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:25:12 192.168.122.209 [58862.549542] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:25:12 192.168.122.209 [58862.576304] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:25:12 192.168.122.209 [58862.621392] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:25:12 192.168.122.209 [58862.665359] [tempesta fw] Tempesta FW is ready Apr 26 08:25:19 192.168.122.209 [58870.335628] [tdb] Close table 'client0.tdb' Apr 26 08:25:19 192.168.122.209 [58870.527045] [tdb] Close table 'sessions0.tdb' Apr 26 08:25:23 192.168.122.209 [58873.778615] [tdb] Close table 'cache0.tdb' Apr 26 08:25:23 192.168.122.209 [58874.014674] [tdb] Close table 'filter0.tdb' Apr 26 08:25:23 192.168.122.209 [58874.015122] [tempesta fw] modules are stopped Apr 26 08:25:23 192.168.122.209 [58874.251174] [tempesta fw] exiting... Apr 26 08:25:23 192.168.122.209 [58874.372939] [tdb] Shutdown Tempesta DB Apr 26 08:25:24 192.168.122.209 [58874.588862] End test: http2_general.test_h2_hpack.TestHpack.test_big_header_after_setting_header_table_size Apr 26 08:25:24 192.168.122.209 [58874.609124] Start test: http2_general.test_h2_hpack.TestHpack.test_bytes_of_table_size_in_header_frame_1 Apr 26 08:25:25 192.168.122.209 [58875.675673] [tdb] Start Tempesta DB Apr 26 08:25:25 192.168.122.209 [58875.813819] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:25:26 192.168.122.209 [58877.398944] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58877.398944] Maybe that's fine, but it's worth checking the [58877.398944] config - if there is no relations between the [58877.398944] names, then host name confusion attack is possible. Apr 26 08:25:27 192.168.122.209 [58877.557735] [tempesta fw] Configuration processing is completed. Apr 26 08:25:27 192.168.122.209 [58877.620416] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:25:27 192.168.122.209 [58878.051618] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:25:27 192.168.122.209 [58878.091291] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:25:27 192.168.122.209 [58878.119435] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:25:27 192.168.122.209 [58878.181577] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:25:27 192.168.122.209 [58878.225517] [tempesta fw] Tempesta FW is ready Apr 26 08:25:28 192.168.122.209 [58878.882599] [tdb] Close table 'client0.tdb' Apr 26 08:25:28 192.168.122.209 [58879.075207] [tdb] Close table 'sessions0.tdb' Apr 26 08:25:31 192.168.122.209 [58882.292552] [tdb] Close table 'cache0.tdb' Apr 26 08:25:31 192.168.122.209 [58882.543696] [tdb] Close table 'filter0.tdb' Apr 26 08:25:31 192.168.122.209 [58882.544128] [tempesta fw] modules are stopped Apr 26 08:25:32 192.168.122.209 [58882.769583] [tempesta fw] exiting... Apr 26 08:25:32 192.168.122.209 [58882.882273] [tdb] Shutdown Tempesta DB Apr 26 08:25:32 192.168.122.209 [58883.128749] End test: http2_general.test_h2_hpack.TestHpack.test_bytes_of_table_size_in_header_frame_1 Apr 26 08:25:32 192.168.122.209 [58883.149104] Start test: http2_general.test_h2_hpack.TestHpack.test_bytes_of_table_size_in_header_frame_2 Apr 26 08:25:33 192.168.122.209 [58884.221675] [tdb] Start Tempesta DB Apr 26 08:25:33 192.168.122.209 [58884.355761] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:25:35 192.168.122.209 [58885.915986] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58885.915986] Maybe that's fine, but it's worth checking the [58885.915986] config - if there is no relations between the [58885.915986] names, then host name confusion attack is possible. Apr 26 08:25:35 192.168.122.209 [58886.069736] [tempesta fw] Configuration processing is completed. Apr 26 08:25:35 192.168.122.209 [58886.120850] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:25:35 192.168.122.209 [58886.544686] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:25:36 192.168.122.209 [58886.572473] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:25:36 192.168.122.209 [58886.600830] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:25:36 192.168.122.209 [58886.649638] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:25:36 192.168.122.209 [58886.689629] [tempesta fw] Tempesta FW is ready Apr 26 08:25:36 192.168.122.209 [58887.348359] [tdb] Close table 'client0.tdb' Apr 26 08:25:36 192.168.122.209 [58887.537848] [tdb] Close table 'sessions0.tdb' Apr 26 08:25:40 192.168.122.209 [58890.743103] [tdb] Close table 'cache0.tdb' Apr 26 08:25:40 192.168.122.209 [58890.975247] [tdb] Close table 'filter0.tdb' Apr 26 08:25:40 192.168.122.209 [58890.975679] [tempesta fw] modules are stopped Apr 26 08:25:40 192.168.122.209 [58891.224697] [tempesta fw] exiting... Apr 26 08:25:40 192.168.122.209 [58891.364037] [tdb] Shutdown Tempesta DB Apr 26 08:25:41 192.168.122.209 [58891.574209] End test: http2_general.test_h2_hpack.TestHpack.test_bytes_of_table_size_in_header_frame_2 Apr 26 08:25:41 192.168.122.209 [58891.591104] Start test: http2_general.test_h2_hpack.TestHpack.test_clearing_dynamic_table Apr 26 08:25:42 192.168.122.209 [58892.602548] [tdb] Start Tempesta DB Apr 26 08:25:42 192.168.122.209 [58892.739165] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:25:43 192.168.122.209 [58894.315219] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58894.315219] Maybe that's fine, but it's worth checking the [58894.315219] config - if there is no relations between the [58894.315219] names, then host name confusion attack is possible. Apr 26 08:25:43 192.168.122.209 [58894.470077] [tempesta fw] Configuration processing is completed. Apr 26 08:25:43 192.168.122.209 [58894.525160] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:25:44 192.168.122.209 [58894.952529] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:25:44 192.168.122.209 [58894.987915] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:25:44 192.168.122.209 [58895.015133] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:25:44 192.168.122.209 [58895.061746] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:25:44 192.168.122.209 [58895.105678] [tempesta fw] Tempesta FW is ready Apr 26 08:25:46 192.168.122.209 [58896.771578] [tdb] Close table 'client0.tdb' Apr 26 08:25:46 192.168.122.209 [58896.991384] [tdb] Close table 'sessions0.tdb' Apr 26 08:25:49 192.168.122.209 [58900.182524] [tdb] Close table 'cache0.tdb' Apr 26 08:25:49 192.168.122.209 [58900.428327] [tdb] Close table 'filter0.tdb' Apr 26 08:25:49 192.168.122.209 [58900.428772] [tempesta fw] modules are stopped Apr 26 08:25:50 192.168.122.209 [58900.647368] [tempesta fw] exiting... Apr 26 08:25:50 192.168.122.209 [58900.766578] [tdb] Shutdown Tempesta DB Apr 26 08:25:50 192.168.122.209 [58900.982338] End test: http2_general.test_h2_hpack.TestHpack.test_clearing_dynamic_table Apr 26 08:25:50 192.168.122.209 [58901.002774] Start test: http2_general.test_h2_hpack.TestHpack.test_clearing_dynamic_table_with_settings_frame Apr 26 08:25:51 192.168.122.209 [58902.068001] [tdb] Start Tempesta DB Apr 26 08:25:51 192.168.122.209 [58902.206887] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:25:53 192.168.122.209 [58903.743439] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58903.743439] Maybe that's fine, but it's worth checking the [58903.743439] config - if there is no relations between the [58903.743439] names, then host name confusion attack is possible. Apr 26 08:25:53 192.168.122.209 [58903.901905] [tempesta fw] Configuration processing is completed. Apr 26 08:25:53 192.168.122.209 [58903.953956] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:25:53 192.168.122.209 [58904.374108] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:25:53 192.168.122.209 [58904.400915] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:25:53 192.168.122.209 [58904.427602] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:25:53 192.168.122.209 [58904.477876] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:25:53 192.168.122.209 [58904.525841] [tempesta fw] Tempesta FW is ready Apr 26 08:25:54 192.168.122.209 [58905.255825] [tdb] Close table 'client0.tdb' Apr 26 08:25:54 192.168.122.209 [58905.466361] [tdb] Close table 'sessions0.tdb' Apr 26 08:25:58 192.168.122.209 [58908.652891] [tdb] Close table 'cache0.tdb' Apr 26 08:25:58 192.168.122.209 [58908.859767] [tdb] Close table 'filter0.tdb' Apr 26 08:25:58 192.168.122.209 [58908.860197] [tempesta fw] modules are stopped Apr 26 08:25:58 192.168.122.209 [58909.075733] [tempesta fw] exiting... Apr 26 08:25:58 192.168.122.209 [58909.181537] [tdb] Shutdown Tempesta DB Apr 26 08:25:58 192.168.122.209 [58909.420169] End test: http2_general.test_h2_hpack.TestHpack.test_clearing_dynamic_table_with_settings_frame Apr 26 08:25:58 192.168.122.209 [58909.434252] Start test: http2_general.test_h2_hpack.TestHpack.test_disable_huffman Apr 26 08:25:59 192.168.122.209 [58910.434549] [tdb] Start Tempesta DB Apr 26 08:26:00 192.168.122.209 [58910.570099] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:26:01 192.168.122.209 [58912.187507] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58912.187507] Maybe that's fine, but it's worth checking the [58912.187507] config - if there is no relations between the [58912.187507] names, then host name confusion attack is possible. Apr 26 08:26:01 192.168.122.209 [58912.350051] [tempesta fw] Configuration processing is completed. Apr 26 08:26:01 192.168.122.209 [58912.407097] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:26:02 192.168.122.209 [58912.830960] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:26:02 192.168.122.209 [58912.858554] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:26:02 192.168.122.209 [58912.885944] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:26:02 192.168.122.209 [58912.942006] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:26:02 192.168.122.209 [58912.985962] [tempesta fw] Tempesta FW is ready Apr 26 08:26:03 192.168.122.209 [58913.648115] [tdb] Close table 'client0.tdb' Apr 26 08:26:03 192.168.122.209 [58913.825620] [tdb] Close table 'sessions0.tdb' Apr 26 08:26:06 192.168.122.209 [58917.061646] [tdb] Close table 'cache0.tdb' Apr 26 08:26:06 192.168.122.209 [58917.293270] [tdb] Close table 'filter0.tdb' Apr 26 08:26:06 192.168.122.209 [58917.293720] [tempesta fw] modules are stopped Apr 26 08:26:07 192.168.122.209 [58917.559951] [tempesta fw] exiting... Apr 26 08:26:07 192.168.122.209 [58917.695122] [tdb] Shutdown Tempesta DB Apr 26 08:26:07 192.168.122.209 [58917.908795] End test: http2_general.test_h2_hpack.TestHpack.test_disable_huffman Apr 26 08:26:07 192.168.122.209 [58917.929428] Start test: http2_general.test_h2_hpack.TestHpack.test_get_method_as_string Apr 26 08:26:08 192.168.122.209 [58918.997013] [tdb] Start Tempesta DB Apr 26 08:26:08 192.168.122.209 [58919.141650] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:26:10 192.168.122.209 [58920.727559] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58920.727559] Maybe that's fine, but it's worth checking the [58920.727559] config - if there is no relations between the [58920.727559] names, then host name confusion attack is possible. Apr 26 08:26:10 192.168.122.209 [58920.870124] [tempesta fw] Configuration processing is completed. Apr 26 08:26:10 192.168.122.209 [58920.919765] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:26:10 192.168.122.209 [58921.346979] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:26:10 192.168.122.209 [58921.376861] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:26:10 192.168.122.209 [58921.403812] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:26:10 192.168.122.209 [58921.446105] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:26:10 192.168.122.209 [58921.498060] [tempesta fw] Tempesta FW is ready Apr 26 08:26:11 192.168.122.209 [58922.143809] [tdb] Close table 'client0.tdb' Apr 26 08:26:11 192.168.122.209 [58922.332535] [tdb] Close table 'sessions0.tdb' Apr 26 08:26:14 192.168.122.209 [58925.504993] [tdb] Close table 'cache0.tdb' Apr 26 08:26:15 192.168.122.209 [58925.737324] [tdb] Close table 'filter0.tdb' Apr 26 08:26:15 192.168.122.209 [58925.737755] [tempesta fw] modules are stopped Apr 26 08:26:15 192.168.122.209 [58926.003456] [tempesta fw] exiting... Apr 26 08:26:15 192.168.122.209 [58926.151053] [tdb] Shutdown Tempesta DB Apr 26 08:26:15 192.168.122.209 [58926.390021] End test: http2_general.test_h2_hpack.TestHpack.test_get_method_as_string Apr 26 08:26:15 192.168.122.209 [58926.412762] Start test: http2_general.test_h2_hpack.TestHpack.test_http_headers_code_charater_is_invalid_in_header Apr 26 08:26:16 192.168.122.209 [58927.539165] [tdb] Start Tempesta DB Apr 26 08:26:17 192.168.122.209 [58927.687169] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:26:18 192.168.122.209 [58929.187650] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58929.187650] Maybe that's fine, but it's worth checking the [58929.187650] config - if there is no relations between the [58929.187650] names, then host name confusion attack is possible. Apr 26 08:26:18 192.168.122.209 [58929.338228] [tempesta fw] Configuration processing is completed. Apr 26 08:26:18 192.168.122.209 [58929.390626] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:26:19 192.168.122.209 [58929.816032] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:26:19 192.168.122.209 [58929.842507] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:26:19 192.168.122.209 [58929.869068] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:26:19 192.168.122.209 [58929.918219] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:26:19 192.168.122.209 [58929.958165] [tempesta fw] Tempesta FW is ready Apr 26 08:26:19 192.168.122.209 [58930.194217] [tempesta fw] Warning: Parser error: state=RGen_HdrOtherV input(-0)=0x1('') data_len=1 off=0 Apr 26 08:26:19 192.168.122.209 [58930.195680] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 08:26:20 192.168.122.209 [58930.593936] [tdb] Close table 'client0.tdb' Apr 26 08:26:20 192.168.122.209 [58930.790735] [tdb] Close table 'sessions0.tdb' Apr 26 08:26:23 192.168.122.209 [58933.972312] [tdb] Close table 'cache0.tdb' Apr 26 08:26:23 192.168.122.209 [58934.233515] [tdb] Close table 'filter0.tdb' Apr 26 08:26:23 192.168.122.209 [58934.233966] [tempesta fw] modules are stopped Apr 26 08:26:23 192.168.122.209 [58934.471285] [tempesta fw] exiting... Apr 26 08:26:24 192.168.122.209 [58934.629824] [tdb] Shutdown Tempesta DB Apr 26 08:26:24 192.168.122.209 [58934.865332] End test: http2_general.test_h2_hpack.TestHpack.test_http_headers_code_charater_is_invalid_in_header Apr 26 08:26:24 192.168.122.209 [58934.879216] Start test: http2_general.test_h2_hpack.TestHpack.test_never_indexed Apr 26 08:26:25 192.168.122.209 [58935.921101] [tdb] Start Tempesta DB Apr 26 08:26:25 192.168.122.209 [58936.065251] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:26:27 192.168.122.209 [58937.711745] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58937.711745] Maybe that's fine, but it's worth checking the [58937.711745] config - if there is no relations between the [58937.711745] names, then host name confusion attack is possible. Apr 26 08:26:27 192.168.122.209 [58937.878910] [tempesta fw] Configuration processing is completed. Apr 26 08:26:27 192.168.122.209 [58937.936628] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:26:27 192.168.122.209 [58938.374290] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:26:27 192.168.122.209 [58938.401117] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:26:27 192.168.122.209 [58938.428103] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:26:27 192.168.122.209 [58938.478343] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:26:27 192.168.122.209 [58938.518287] [tempesta fw] Tempesta FW is ready Apr 26 08:26:28 192.168.122.209 [58939.153471] [tdb] Close table 'client0.tdb' Apr 26 08:26:28 192.168.122.209 [58939.341124] [tdb] Close table 'sessions0.tdb' Apr 26 08:26:31 192.168.122.209 [58942.544882] [tdb] Close table 'cache0.tdb' Apr 26 08:26:32 192.168.122.209 [58942.794139] [tdb] Close table 'filter0.tdb' Apr 26 08:26:32 192.168.122.209 [58942.794582] [tempesta fw] modules are stopped Apr 26 08:26:32 192.168.122.209 [58943.042108] [tempesta fw] exiting... Apr 26 08:26:32 192.168.122.209 [58943.161217] [tdb] Shutdown Tempesta DB Apr 26 08:26:32 192.168.122.209 [58943.387251] End test: http2_general.test_h2_hpack.TestHpack.test_never_indexed Apr 26 08:26:32 192.168.122.209 [58943.413682] Start test: http2_general.test_h2_hpack.TestHpack.test_relloc_hpack_table Apr 26 08:26:33 192.168.122.209 [58944.458242] [tdb] Start Tempesta DB Apr 26 08:26:34 192.168.122.209 [58944.597767] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:26:35 192.168.122.209 [58946.215590] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [58946.215590] Maybe that's fine, but it's worth checking the [58946.215590] config - if there is no relations between the [58946.215590] names, then host name confusion attack is possible. Apr 26 08:26:35 192.168.122.209 [58946.366498] [tempesta fw] Configuration processing is completed. Apr 26 08:26:35 192.168.122.209 [58946.426626] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:26:36 192.168.122.209 [58946.852542] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:26:36 192.168.122.209 [58946.881446] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:26:36 192.168.122.209 [58946.908598] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:26:36 192.168.122.209 [58946.974440] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:26:36 192.168.122.209 [58947.014425] [tempesta fw] Tempesta FW is ready Apr 26 08:29:22 192.168.122.209 [59113.521635] [tdb] Close table 'client0.tdb' Apr 26 08:29:23 192.168.122.209 [59113.692282] [tdb] Close table 'sessions0.tdb' Apr 26 08:29:26 192.168.122.209 [59116.926527] [tdb] Close table 'cache0.tdb' Apr 26 08:29:26 192.168.122.209 [59117.179200] [tdb] Close table 'filter0.tdb' Apr 26 08:29:26 192.168.122.209 [59117.179640] [tempesta fw] modules are stopped Apr 26 08:29:26 192.168.122.209 [59117.437258] [tempesta fw] exiting... Apr 26 08:29:27 192.168.122.209 [59117.554306] [tdb] Shutdown Tempesta DB Apr 26 08:29:27 192.168.122.209 [59117.756646] End test: http2_general.test_h2_hpack.TestHpack.test_relloc_hpack_table Apr 26 08:29:27 192.168.122.209 [59117.769355] Start test: http2_general.test_h2_hpack.TestHpack.test_rewrite_dynamic_table_for_request Apr 26 08:29:28 192.168.122.209 [59118.828007] [tdb] Start Tempesta DB Apr 26 08:29:28 192.168.122.209 [59118.967560] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:29:30 192.168.122.209 [59120.590063] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [59120.590063] Maybe that's fine, but it's worth checking the [59120.590063] config - if there is no relations between the [59120.590063] names, then host name confusion attack is possible. Apr 26 08:29:30 192.168.122.209 [59120.760623] [tempesta fw] Configuration processing is completed. Apr 26 08:29:30 192.168.122.209 [59120.810682] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:29:30 192.168.122.209 [59121.232918] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:29:30 192.168.122.209 [59121.261075] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:29:30 192.168.122.209 [59121.291261] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:29:30 192.168.122.209 [59121.340628] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:29:30 192.168.122.209 [59121.380589] [tempesta fw] Tempesta FW is ready Apr 26 08:29:31 192.168.122.209 [59122.520203] [tdb] Close table 'client0.tdb' Apr 26 08:29:32 192.168.122.209 [59122.704889] [tdb] Close table 'sessions0.tdb' Apr 26 08:29:35 192.168.122.209 [59125.923882] [tdb] Close table 'cache0.tdb' Apr 26 08:29:35 192.168.122.209 [59126.173871] [tdb] Close table 'filter0.tdb' Apr 26 08:29:35 192.168.122.209 [59126.174303] [tempesta fw] modules are stopped Apr 26 08:29:35 192.168.122.209 [59126.368681] [tempesta fw] exiting... Apr 26 08:29:35 192.168.122.209 [59126.489304] [tdb] Shutdown Tempesta DB Apr 26 08:29:36 192.168.122.209 [59126.686751] End test: http2_general.test_h2_hpack.TestHpack.test_rewrite_dynamic_table_for_request Apr 26 08:29:36 192.168.122.209 [59126.694700] Start test: http2_general.test_h2_hpack.TestHpack.test_rewrite_dynamic_table_for_response Apr 26 08:29:37 192.168.122.209 [59127.724060] [tdb] Start Tempesta DB Apr 26 08:29:37 192.168.122.209 [59127.883871] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:29:38 192.168.122.209 [59129.466146] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [59129.466146] Maybe that's fine, but it's worth checking the [59129.466146] config - if there is no relations between the [59129.466146] names, then host name confusion attack is possible. Apr 26 08:29:39 192.168.122.209 [59129.624752] [tempesta fw] Configuration processing is completed. Apr 26 08:29:39 192.168.122.209 [59129.690875] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:29:39 192.168.122.209 [59130.121011] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:29:39 192.168.122.209 [59130.147853] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:29:39 192.168.122.209 [59130.183383] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:29:39 192.168.122.209 [59130.248663] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:29:39 192.168.122.209 [59130.288694] [tempesta fw] Tempesta FW is ready Apr 26 08:29:41 192.168.122.209 [59132.057801] [tdb] Close table 'client0.tdb' Apr 26 08:29:41 192.168.122.209 [59132.242070] [tdb] Close table 'sessions0.tdb' Apr 26 08:29:44 192.168.122.209 [59135.408119] [tdb] Close table 'cache0.tdb' Apr 26 08:29:45 192.168.122.209 [59135.646927] [tdb] Close table 'filter0.tdb' Apr 26 08:29:45 192.168.122.209 [59135.647370] [tempesta fw] modules are stopped Apr 26 08:29:45 192.168.122.209 [59135.877537] [tempesta fw] exiting... Apr 26 08:29:45 192.168.122.209 [59136.000642] [tdb] Shutdown Tempesta DB Apr 26 08:29:45 192.168.122.209 [59136.223184] End test: http2_general.test_h2_hpack.TestHpack.test_rewrite_dynamic_table_for_response Apr 26 08:29:45 192.168.122.209 [59136.232362] Start test: http2_general.test_h2_hpack.TestHpack.test_send_invalid_request_after_setting_header_table_size Apr 26 08:29:46 192.168.122.209 [59137.235645] [tdb] Start Tempesta DB Apr 26 08:29:46 192.168.122.209 [59137.383138] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:29:48 192.168.122.209 [59138.937672] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [59138.937672] Maybe that's fine, but it's worth checking the [59138.937672] config - if there is no relations between the [59138.937672] names, then host name confusion attack is possible. Apr 26 08:29:48 192.168.122.209 [59139.080988] [tempesta fw] Configuration processing is completed. Apr 26 08:29:48 192.168.122.209 [59139.131830] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:29:49 192.168.122.209 [59139.597293] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:29:49 192.168.122.209 [59139.624436] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:29:49 192.168.122.209 [59139.650993] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:29:49 192.168.122.209 [59139.700821] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:29:49 192.168.122.209 [59139.744791] [tempesta fw] Tempesta FW is ready Apr 26 08:29:49 192.168.122.209 [59139.953854] [tempesta fw] Warning: request has been filtered out via http table: 127.0.0.2 Apr 26 08:29:49 192.168.122.209 [59140.377434] [tdb] Close table 'client0.tdb' Apr 26 08:29:50 192.168.122.209 [59140.563958] [tdb] Close table 'sessions0.tdb' Apr 26 08:29:53 192.168.122.209 [59143.759010] [tdb] Close table 'cache0.tdb' Apr 26 08:29:53 192.168.122.209 [59143.983635] [tdb] Close table 'filter0.tdb' Apr 26 08:29:53 192.168.122.209 [59143.984089] [tempesta fw] modules are stopped Apr 26 08:29:53 192.168.122.209 [59144.250157] [tempesta fw] exiting... Apr 26 08:29:53 192.168.122.209 [59144.410357] [tdb] Shutdown Tempesta DB Apr 26 08:29:54 192.168.122.209 [59144.594197] End test: http2_general.test_h2_hpack.TestHpack.test_send_invalid_request_after_setting_header_table_size Apr 26 08:29:54 192.168.122.209 [59144.611643] Start test: http2_general.test_h2_hpack.TestHpack.test_settings_header_table_size Apr 26 08:29:55 192.168.122.209 [59145.707050] [tdb] Start Tempesta DB Apr 26 08:29:55 192.168.122.209 [59145.846575] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:29:56 192.168.122.209 [59147.462352] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [59147.462352] Maybe that's fine, but it's worth checking the [59147.462352] config - if there is no relations between the [59147.462352] names, then host name confusion attack is possible. Apr 26 08:29:57 192.168.122.209 [59147.616985] [tempesta fw] Configuration processing is completed. Apr 26 08:29:57 192.168.122.209 [59147.677116] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:29:57 192.168.122.209 [59148.109040] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:29:57 192.168.122.209 [59148.135886] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:29:57 192.168.122.209 [59148.163430] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:29:57 192.168.122.209 [59148.220964] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:29:57 192.168.122.209 [59148.272911] [tempesta fw] Tempesta FW is ready Apr 26 08:29:58 192.168.122.209 [59149.192185] [tdb] Close table 'client0.tdb' Apr 26 08:29:58 192.168.122.209 [59149.371748] [tdb] Close table 'sessions0.tdb' Apr 26 08:30:02 192.168.122.209 [59152.593620] [tdb] Close table 'cache0.tdb' Apr 26 08:30:02 192.168.122.209 [59152.856294] [tdb] Close table 'filter0.tdb' Apr 26 08:30:02 192.168.122.209 [59152.856738] [tempesta fw] modules are stopped Apr 26 08:30:02 192.168.122.209 [59153.057335] [tempesta fw] exiting... Apr 26 08:30:02 192.168.122.209 [59153.170887] [tdb] Shutdown Tempesta DB Apr 26 08:30:02 192.168.122.209 [59153.381844] End test: http2_general.test_h2_hpack.TestHpack.test_settings_header_table_size Apr 26 08:30:02 192.168.122.209 [59153.396428] Start test: http2_general.test_h2_hpack.TestHpack.test_settings_header_table_stress Apr 26 08:30:03 192.168.122.209 [59154.364755] [tdb] Start Tempesta DB Apr 26 08:30:03 192.168.122.209 [59154.513682] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:30:05 192.168.122.209 [59156.142479] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [59156.142479] Maybe that's fine, but it's worth checking the [59156.142479] config - if there is no relations between the [59156.142479] names, then host name confusion attack is possible. Apr 26 08:30:05 192.168.122.209 [59156.289063] [tempesta fw] Configuration processing is completed. Apr 26 08:30:05 192.168.122.209 [59156.339250] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:30:06 192.168.122.209 [59156.758294] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:30:06 192.168.122.209 [59156.796430] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:30:06 192.168.122.209 [59156.822586] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:30:06 192.168.122.209 [59156.865063] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:30:06 192.168.122.209 [59156.909008] [tempesta fw] Tempesta FW is ready Apr 26 08:30:38 192.168.122.209 [59189.417904] [tdb] Close table 'client0.tdb' Apr 26 08:30:39 192.168.122.209 [59189.606712] [tdb] Close table 'sessions0.tdb' Apr 26 08:30:42 192.168.122.209 [59192.784256] [tdb] Close table 'cache0.tdb' Apr 26 08:30:42 192.168.122.209 [59193.031576] [tdb] Close table 'filter0.tdb' Apr 26 08:30:42 192.168.122.209 [59193.032026] [tempesta fw] modules are stopped Apr 26 08:30:42 192.168.122.209 [59193.259630] [tempesta fw] exiting... Apr 26 08:30:42 192.168.122.209 [59193.383901] [tdb] Shutdown Tempesta DB Apr 26 08:30:43 192.168.122.209 [59193.600693] End test: http2_general.test_h2_hpack.TestHpack.test_settings_header_table_stress Apr 26 08:30:43 192.168.122.209 [59193.610174] Start test: http2_general.test_h2_hpack.TestHpack.test_static_table Apr 26 08:30:44 192.168.122.209 [59194.635238] [tdb] Start Tempesta DB Apr 26 08:30:44 192.168.122.209 [59194.774188] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:30:45 192.168.122.209 [59196.347085] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [59196.347085] Maybe that's fine, but it's worth checking the [59196.347085] config - if there is no relations between the [59196.347085] names, then host name confusion attack is possible. Apr 26 08:30:45 192.168.122.209 [59196.497613] [tempesta fw] Configuration processing is completed. Apr 26 08:30:45 192.168.122.209 [59196.549590] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:30:46 192.168.122.209 [59196.982743] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:30:46 192.168.122.209 [59197.010104] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:30:46 192.168.122.209 [59197.036656] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:30:46 192.168.122.209 [59197.121598] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:30:46 192.168.122.209 [59197.161524] [tempesta fw] Tempesta FW is ready Apr 26 08:30:47 192.168.122.209 [59197.775615] [tdb] Close table 'client0.tdb' Apr 26 08:30:47 192.168.122.209 [59197.976216] [tdb] Close table 'sessions0.tdb' Apr 26 08:30:50 192.168.122.209 [59201.169912] [tdb] Close table 'cache0.tdb' Apr 26 08:30:50 192.168.122.209 [59201.392206] [tdb] Close table 'filter0.tdb' Apr 26 08:30:50 192.168.122.209 [59201.392638] [tempesta fw] modules are stopped Apr 26 08:30:51 192.168.122.209 [59201.607111] [tempesta fw] exiting... Apr 26 08:30:51 192.168.122.209 [59201.759732] [tdb] Shutdown Tempesta DB Apr 26 08:30:51 192.168.122.209 [59201.974454] End test: http2_general.test_h2_hpack.TestHpack.test_static_table Apr 26 08:30:51 192.168.122.209 [59201.996726] Start test: http2_general.test_h2_hpack.TestHpackCache.test_h2_cache_200_after_setting_header_table_size Apr 26 08:30:52 192.168.122.209 [59203.006537] [tdb] Start Tempesta DB Apr 26 08:30:52 192.168.122.209 [59203.139704] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:30:54 192.168.122.209 [59204.859211] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [59204.859211] Maybe that's fine, but it's worth checking the [59204.859211] config - if there is no relations between the [59204.859211] names, then host name confusion attack is possible. Apr 26 08:30:54 192.168.122.209 [59205.050078] [tempesta fw] Configuration processing is completed. Apr 26 08:30:54 192.168.122.209 [59205.099546] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:30:54 192.168.122.209 [59205.525798] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:30:55 192.168.122.209 [59205.553460] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:30:55 192.168.122.209 [59205.581840] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:30:55 192.168.122.209 [59205.625676] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:30:55 192.168.122.209 [59205.673664] [tempesta fw] Tempesta FW is ready Apr 26 08:30:55 192.168.122.209 [59206.265649] [tdb] Close table 'client0.tdb' Apr 26 08:30:55 192.168.122.209 [59206.463816] [tdb] Close table 'sessions0.tdb' Apr 26 08:30:59 192.168.122.209 [59209.711504] [tdb] Close table 'cache0.tdb' Apr 26 08:30:59 192.168.122.209 [59209.976848] [tdb] Close table 'filter0.tdb' Apr 26 08:30:59 192.168.122.209 [59209.977279] [tempesta fw] modules are stopped Apr 26 08:30:59 192.168.122.209 [59210.214026] [tempesta fw] exiting... Apr 26 08:30:59 192.168.122.209 [59210.322620] [tdb] Shutdown Tempesta DB Apr 26 08:30:59 192.168.122.209 [59210.514686] End test: http2_general.test_h2_hpack.TestHpackCache.test_h2_cache_200_after_setting_header_table_size Apr 26 08:30:59 192.168.122.209 [59210.536507] Start test: http2_general.test_h2_hpack.TestHpackCache.test_h2_cache_304_after_setting_header_table_size Apr 26 08:31:00 192.168.122.209 [59211.549314] [tdb] Start Tempesta DB Apr 26 08:31:01 192.168.122.209 [59211.685755] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:31:02 192.168.122.209 [59213.379300] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [59213.379300] Maybe that's fine, but it's worth checking the [59213.379300] config - if there is no relations between the [59213.379300] names, then host name confusion attack is possible. Apr 26 08:31:03 192.168.122.209 [59213.565805] [tempesta fw] Configuration processing is completed. Apr 26 08:31:03 192.168.122.209 [59213.615146] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:31:03 192.168.122.209 [59214.039963] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:31:03 192.168.122.209 [59214.066871] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:31:03 192.168.122.209 [59214.093744] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:31:03 192.168.122.209 [59214.169794] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:31:03 192.168.122.209 [59214.209738] [tempesta fw] Tempesta FW is ready Apr 26 08:31:04 192.168.122.209 [59214.817944] [tdb] Close table 'client0.tdb' Apr 26 08:31:04 192.168.122.209 [59214.998147] [tdb] Close table 'sessions0.tdb' Apr 26 08:31:07 192.168.122.209 [59218.211586] [tdb] Close table 'cache0.tdb' Apr 26 08:31:07 192.168.122.209 [59218.462281] [tdb] Close table 'filter0.tdb' Apr 26 08:31:07 192.168.122.209 [59218.462721] [tempesta fw] modules are stopped Apr 26 08:31:08 192.168.122.209 [59218.694755] [tempesta fw] exiting... Apr 26 08:31:08 192.168.122.209 [59218.843802] [tdb] Shutdown Tempesta DB Apr 26 08:31:08 192.168.122.209 [59219.026536] End test: http2_general.test_h2_hpack.TestHpackCache.test_h2_cache_304_after_setting_header_table_size Apr 26 08:31:08 192.168.122.209 [59219.039174] Start test: http2_general.test_h2_hpack.TestHpackStickyCookie.test_h2_cookie_after_setting_header_table_size Apr 26 08:31:09 192.168.122.209 [59220.045634] [tdb] Start Tempesta DB Apr 26 08:31:09 192.168.122.209 [59220.182571] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:31:11 192.168.122.209 [59221.996945] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [59221.996945] Maybe that's fine, but it's worth checking the [59221.996945] config - if there is no relations between the [59221.996945] names, then host name confusion attack is possible. Apr 26 08:31:11 192.168.122.209 [59222.149903] [tempesta fw] Configuration processing is completed. Apr 26 08:31:11 192.168.122.209 [59222.200937] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:31:12 192.168.122.209 [59222.622400] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:31:12 192.168.122.209 [59222.653595] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:31:12 192.168.122.209 [59222.680263] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:31:12 192.168.122.209 [59222.725902] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:31:12 192.168.122.209 [59222.769853] [tempesta fw] Tempesta FW is ready Apr 26 08:31:12 192.168.122.209 [59223.422372] [tdb] Close table 'client0.tdb' Apr 26 08:31:13 192.168.122.209 [59223.601416] [tdb] Close table 'sessions0.tdb' Apr 26 08:31:16 192.168.122.209 [59226.841027] [tdb] Close table 'cache0.tdb' Apr 26 08:31:16 192.168.122.209 [59227.064705] [tdb] Close table 'filter0.tdb' Apr 26 08:31:16 192.168.122.209 [59227.065137] [tempesta fw] modules are stopped Apr 26 08:31:16 192.168.122.209 [59227.307748] [tempesta fw] exiting... Apr 26 08:31:16 192.168.122.209 [59227.467573] [tdb] Shutdown Tempesta DB Apr 26 08:31:17 192.168.122.209 [59227.680996] End test: http2_general.test_h2_hpack.TestHpackStickyCookie.test_h2_cookie_after_setting_header_table_size Apr 26 08:31:17 192.168.122.209 [59227.693932] Start test: http2_general.test_h2_hpack.TestHpackTableSizeEncodedInInvalidPlace.test_begin Apr 26 08:31:18 192.168.122.209 [59228.755142] [tdb] Start Tempesta DB Apr 26 08:31:18 192.168.122.209 [59228.903697] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:31:19 192.168.122.209 [59230.523481] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [59230.523481] Maybe that's fine, but it's worth checking the [59230.523481] config - if there is no relations between the [59230.523481] names, then host name confusion attack is possible. Apr 26 08:31:20 192.168.122.209 [59230.670023] [tempesta fw] Configuration processing is completed. Apr 26 08:31:20 192.168.122.209 [59230.720408] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:31:20 192.168.122.209 [59231.137840] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:31:20 192.168.122.209 [59231.164571] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:31:20 192.168.122.209 [59231.192020] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:31:20 192.168.122.209 [59231.294024] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:31:20 192.168.122.209 [59231.337943] [tempesta fw] Tempesta FW is ready Apr 26 08:31:21 192.168.122.209 [59231.968138] [tdb] Close table 'client0.tdb' Apr 26 08:31:21 192.168.122.209 [59232.161489] [tdb] Close table 'sessions0.tdb' Apr 26 08:31:24 192.168.122.209 [59235.366661] [tdb] Close table 'cache0.tdb' Apr 26 08:31:25 192.168.122.209 [59235.627126] [tdb] Close table 'filter0.tdb' Apr 26 08:31:25 192.168.122.209 [59235.627575] [tempesta fw] modules are stopped Apr 26 08:31:25 192.168.122.209 [59235.831561] [tempesta fw] exiting... Apr 26 08:31:25 192.168.122.209 [59235.951434] [tdb] Shutdown Tempesta DB Apr 26 08:31:25 192.168.122.209 [59236.149767] End test: http2_general.test_h2_hpack.TestHpackTableSizeEncodedInInvalidPlace.test_begin Apr 26 08:31:25 192.168.122.209 [59236.160921] Start test: http2_general.test_h2_hpack.TestHpackTableSizeEncodedInInvalidPlace.test_end Apr 26 08:31:26 192.168.122.209 [59237.205133] [tdb] Start Tempesta DB Apr 26 08:31:26 192.168.122.209 [59237.354261] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:31:28 192.168.122.209 [59238.871651] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [59238.871651] Maybe that's fine, but it's worth checking the [59238.871651] config - if there is no relations between the [59238.871651] names, then host name confusion attack is possible. Apr 26 08:31:28 192.168.122.209 [59239.034523] [tempesta fw] Configuration processing is completed. Apr 26 08:31:28 192.168.122.209 [59239.086077] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:31:28 192.168.122.209 [59239.512930] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:31:28 192.168.122.209 [59239.539968] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:31:29 192.168.122.209 [59239.566949] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:31:29 192.168.122.209 [59239.610058] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:31:29 192.168.122.209 [59239.658055] [tempesta fw] Tempesta FW is ready Apr 26 08:31:29 192.168.122.209 [59240.287863] [tdb] Close table 'client0.tdb' Apr 26 08:31:29 192.168.122.209 [59240.492942] [tdb] Close table 'sessions0.tdb' Apr 26 08:31:33 192.168.122.209 [59243.658669] [tdb] Close table 'cache0.tdb' Apr 26 08:31:33 192.168.122.209 [59243.915569] [tdb] Close table 'filter0.tdb' Apr 26 08:31:33 192.168.122.209 [59243.916024] [tempesta fw] modules are stopped Apr 26 08:31:33 192.168.122.209 [59244.130941] [tempesta fw] exiting... Apr 26 08:31:33 192.168.122.209 [59244.278168] [tdb] Shutdown Tempesta DB Apr 26 08:31:33 192.168.122.209 [59244.474499] End test: http2_general.test_h2_hpack.TestHpackTableSizeEncodedInInvalidPlace.test_end Apr 26 08:31:33 192.168.122.209 [59244.493414] Start test: http2_general.test_h2_hpack.TestHpackTableSizeEncodedInInvalidPlace.test_middle Apr 26 08:31:34 192.168.122.209 [59245.527082] [tdb] Start Tempesta DB Apr 26 08:31:35 192.168.122.209 [59245.665170] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:31:36 192.168.122.209 [59247.279647] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [59247.279647] Maybe that's fine, but it's worth checking the [59247.279647] config - if there is no relations between the [59247.279647] names, then host name confusion attack is possible. Apr 26 08:31:36 192.168.122.209 [59247.442228] [tempesta fw] Configuration processing is completed. Apr 26 08:31:36 192.168.122.209 [59247.490058] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:31:37 192.168.122.209 [59247.908550] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:31:37 192.168.122.209 [59247.948260] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:31:37 192.168.122.209 [59247.974440] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:31:37 192.168.122.209 [59248.034213] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:31:37 192.168.122.209 [59248.074150] [tempesta fw] Tempesta FW is ready Apr 26 08:31:38 192.168.122.209 [59248.675628] [tdb] Close table 'client0.tdb' Apr 26 08:31:38 192.168.122.209 [59248.855142] [tdb] Close table 'sessions0.tdb' Apr 26 08:31:41 192.168.122.209 [59252.064242] [tdb] Close table 'cache0.tdb' Apr 26 08:31:41 192.168.122.209 [59252.314358] [tdb] Close table 'filter0.tdb' Apr 26 08:31:41 192.168.122.209 [59252.314798] [tempesta fw] modules are stopped Apr 26 08:31:42 192.168.122.209 [59252.562678] [tempesta fw] exiting... Apr 26 08:31:42 192.168.122.209 [59252.714907] [tdb] Shutdown Tempesta DB Apr 26 08:31:42 192.168.122.209 [59252.911309] End test: http2_general.test_h2_hpack.TestHpackTableSizeEncodedInInvalidPlace.test_middle Apr 26 08:31:42 192.168.122.209 [59252.926332] Start test: http2_general.test_h2_hpack.TestHpackUnknownMethod.test_unknown_method_dynamic_table Apr 26 08:31:43 192.168.122.209 [59253.982322] [tdb] Start Tempesta DB Apr 26 08:31:43 192.168.122.209 [59254.123749] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:31:45 192.168.122.209 [59255.587913] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [59255.587913] Maybe that's fine, but it's worth checking the [59255.587913] config - if there is no relations between the [59255.587913] names, then host name confusion attack is possible. Apr 26 08:31:45 192.168.122.209 [59255.702347] [tempesta fw] Configuration processing is completed. Apr 26 08:31:45 192.168.122.209 [59255.760519] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:31:45 192.168.122.209 [59256.177245] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:31:45 192.168.122.209 [59256.203942] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:31:45 192.168.122.209 [59256.231189] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:31:45 192.168.122.209 [59256.274305] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:31:45 192.168.122.209 [59256.314268] [tempesta fw] Tempesta FW is ready Apr 26 08:31:46 192.168.122.209 [59256.955858] [tdb] Close table 'client0.tdb' Apr 26 08:31:46 192.168.122.209 [59257.138945] [tdb] Close table 'sessions0.tdb' Apr 26 08:31:49 192.168.122.209 [59260.298701] [tdb] Close table 'cache0.tdb' Apr 26 08:31:50 192.168.122.209 [59260.554889] [tdb] Close table 'filter0.tdb' Apr 26 08:31:50 192.168.122.209 [59260.555339] [tempesta fw] modules are stopped Apr 26 08:31:50 192.168.122.209 [59260.806280] [tempesta fw] exiting... Apr 26 08:31:50 192.168.122.209 [59260.948985] [tdb] Shutdown Tempesta DB Apr 26 08:31:50 192.168.122.209 [59261.139396] End test: http2_general.test_h2_hpack.TestHpackUnknownMethod.test_unknown_method_dynamic_table Apr 26 08:31:50 192.168.122.209 [59261.151079] Start test: http2_general.test_h2_hpack.TestLoadingHeadersFromHpackDynamicTable.test_content_length_field_from_hpack_table Apr 26 08:31:51 192.168.122.209 [59262.233660] [tdb] Start Tempesta DB Apr 26 08:31:51 192.168.122.209 [59262.370750] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:31:53 192.168.122.209 [59264.127920] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [59264.127920] Maybe that's fine, but it's worth checking the [59264.127920] config - if there is no relations between the [59264.127920] names, then host name confusion attack is possible. Apr 26 08:31:53 192.168.122.209 [59264.262470] [tempesta fw] Configuration processing is completed. Apr 26 08:31:53 192.168.122.209 [59264.312130] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:31:54 192.168.122.209 [59264.735397] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:31:54 192.168.122.209 [59264.762445] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:31:54 192.168.122.209 [59264.789202] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:31:54 192.168.122.209 [59264.834363] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:31:54 192.168.122.209 [59264.874389] [tempesta fw] Tempesta FW is ready Apr 26 08:31:54 192.168.122.209 [59265.073369] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102d00a80280" Apr 26 08:31:54 192.168.122.209 [59265.101571] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102d00a80280" Apr 26 08:31:54 192.168.122.209 [59265.528884] [tdb] Close table 'client0.tdb' Apr 26 08:31:55 192.168.122.209 [59265.714303] [tdb] Close table 'sessions0.tdb' Apr 26 08:31:58 192.168.122.209 [59268.906956] [tdb] Close table 'cache0.tdb' Apr 26 08:31:58 192.168.122.209 [59269.132706] [tdb] Close table 'filter0.tdb' Apr 26 08:31:58 192.168.122.209 [59269.133130] [tempesta fw] modules are stopped Apr 26 08:31:58 192.168.122.209 [59269.366935] [tempesta fw] exiting... Apr 26 08:31:58 192.168.122.209 [59269.494821] [tdb] Shutdown Tempesta DB Apr 26 08:31:59 192.168.122.209 [59269.697445] End test: http2_general.test_h2_hpack.TestLoadingHeadersFromHpackDynamicTable.test_content_length_field_from_hpack_table Apr 26 08:31:59 192.168.122.209 [59269.711689] Start test: http2_general.test_h2_hpack.TestLoadingHeadersFromHpackDynamicTable.test_content_type_from_hpack_table Apr 26 08:32:00 192.168.122.209 [59270.718151] [tdb] Start Tempesta DB Apr 26 08:32:00 192.168.122.209 [59270.848849] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:32:02 192.168.122.209 [59272.651964] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [59272.651964] Maybe that's fine, but it's worth checking the [59272.651964] config - if there is no relations between the [59272.651964] names, then host name confusion attack is possible. Apr 26 08:32:02 192.168.122.209 [59272.794489] [tempesta fw] Configuration processing is completed. Apr 26 08:32:02 192.168.122.209 [59272.844912] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:32:02 192.168.122.209 [59273.262597] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:32:02 192.168.122.209 [59273.290082] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:32:02 192.168.122.209 [59273.316550] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:32:02 192.168.122.209 [59273.358551] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:32:02 192.168.122.209 [59273.398489] [tempesta fw] Tempesta FW is ready Apr 26 08:32:03 192.168.122.209 [59273.599141] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:03 192.168.122.209 [59273.627828] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:03 192.168.122.209 [59273.657861] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:03 192.168.122.209 [59273.731462] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:03 192.168.122.209 [59273.765227] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:03 192.168.122.209 [59273.790568] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:03 192.168.122.209 [59273.857600] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:03 192.168.122.209 [59273.883799] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:03 192.168.122.209 [59273.908152] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:03 192.168.122.209 [59273.975821] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:03 192.168.122.209 [59274.003709] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:03 192.168.122.209 [59274.025259] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:03 192.168.122.209 [59274.092687] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:03 192.168.122.209 [59274.117736] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:03 192.168.122.209 [59274.145276] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:03 192.168.122.209 [59274.210152] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:03 192.168.122.209 [59274.236236] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:03 192.168.122.209 [59274.262560] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:03 192.168.122.209 [59274.329040] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:03 192.168.122.209 [59274.352981] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:03 192.168.122.209 [59274.380530] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:03 192.168.122.209 [59274.448193] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:03 192.168.122.209 [59274.473334] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:03 192.168.122.209 [59274.497363] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:04 192.168.122.209 [59274.563131] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:04 192.168.122.209 [59274.580441] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:04 192.168.122.209 [59274.612404] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:04 192.168.122.209 [59274.686324] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:04 192.168.122.209 [59274.710388] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:04 192.168.122.209 [59274.734903] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:04 192.168.122.209 [59274.802646] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:04 192.168.122.209 [59274.827636] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:04 192.168.122.209 [59274.855653] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:04 192.168.122.209 [59274.920200] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:04 192.168.122.209 [59274.947289] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:04 192.168.122.209 [59274.971454] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:04 192.168.122.209 [59275.037607] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:04 192.168.122.209 [59275.063833] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:04 192.168.122.209 [59275.091309] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:04 192.168.122.209 [59275.160553] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:04 192.168.122.209 [59275.192992] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:04 192.168.122.209 [59275.218134] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:04 192.168.122.209 [59275.286332] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:04 192.168.122.209 [59275.310619] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:04 192.168.122.209 [59275.340010] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:04 192.168.122.209 [59275.404276] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:04 192.168.122.209 [59275.433784] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:04 192.168.122.209 [59275.453947] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:04 192.168.122.209 [59275.522213] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:05 192.168.122.209 [59275.554143] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:05 192.168.122.209 [59275.583716] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:05 192.168.122.209 [59275.655201] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:05 192.168.122.209 [59275.687112] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:05 192.168.122.209 [59275.714073] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:05 192.168.122.209 [59275.778749] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:05 192.168.122.209 [59275.806800] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:05 192.168.122.209 [59275.832814] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:05 192.168.122.209 [59275.899807] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:05 192.168.122.209 [59275.937613] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:05 192.168.122.209 [59275.961275] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:05 192.168.122.209 [59276.028795] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:05 192.168.122.209 [59276.052720] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:05 192.168.122.209 [59276.081134] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:05 192.168.122.209 [59276.144203] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:05 192.168.122.209 [59276.173835] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:05 192.168.122.209 [59276.196824] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:05 192.168.122.209 [59276.265728] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:05 192.168.122.209 [59276.292278] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:05 192.168.122.209 [59276.319144] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:05 192.168.122.209 [59276.384149] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:05 192.168.122.209 [59276.410443] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:05 192.168.122.209 [59276.437118] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:05 192.168.122.209 [59276.504839] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:05 192.168.122.209 [59276.530221] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:06 192.168.122.209 [59276.562035] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:06 192.168.122.209 [59276.624466] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:06 192.168.122.209 [59276.651221] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:06 192.168.122.209 [59276.676815] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:06 192.168.122.209 [59276.741195] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:06 192.168.122.209 [59276.766290] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:06 192.168.122.209 [59276.794419] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:06 192.168.122.209 [59276.861642] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:06 192.168.122.209 [59276.890664] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:06 192.168.122.209 [59276.912926] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:06 192.168.122.209 [59276.977645] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:06 192.168.122.209 [59277.009200] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:06 192.168.122.209 [59277.043987] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:06 192.168.122.209 [59277.113908] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:06 192.168.122.209 [59277.146103] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:06 192.168.122.209 [59277.168928] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:06 192.168.122.209 [59277.240981] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:06 192.168.122.209 [59277.264196] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:06 192.168.122.209 [59277.290264] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:06 192.168.122.209 [59277.357883] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:06 192.168.122.209 [59277.384808] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:06 192.168.122.209 [59277.407337] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:06 192.168.122.209 [59277.479050] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:06 192.168.122.209 [59277.500990] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:06 192.168.122.209 [59277.529479] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:07 192.168.122.209 [59277.596100] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:07 192.168.122.209 [59277.621743] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:07 192.168.122.209 [59277.645621] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:07 192.168.122.209 [59277.712604] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:07 192.168.122.209 [59277.740214] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:07 192.168.122.209 [59277.770933] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:07 192.168.122.209 [59277.837062] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:07 192.168.122.209 [59277.864294] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:07 192.168.122.209 [59277.887072] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:07 192.168.122.209 [59277.955286] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:07 192.168.122.209 [59277.976852] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:07 192.168.122.209 [59278.004478] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:07 192.168.122.209 [59278.072161] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:07 192.168.122.209 [59278.097654] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:07 192.168.122.209 [59278.123526] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:07 192.168.122.209 [59278.194869] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:07 192.168.122.209 [59278.219188] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:07 192.168.122.209 [59278.248654] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:07 192.168.122.209 [59278.314142] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:07 192.168.122.209 [59278.343792] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:07 192.168.122.209 [59278.366675] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:07 192.168.122.209 [59278.433503] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:07 192.168.122.209 [59278.456730] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:07 192.168.122.209 [59278.491314] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:08 192.168.122.209 [59278.554239] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:08 192.168.122.209 [59278.578775] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:08 192.168.122.209 [59278.610049] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:08 192.168.122.209 [59278.683380] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:08 192.168.122.209 [59278.705459] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:08 192.168.122.209 [59278.734184] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:08 192.168.122.209 [59278.796202] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:08 192.168.122.209 [59278.829235] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:08 192.168.122.209 [59278.859592] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:08 192.168.122.209 [59278.929438] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:08 192.168.122.209 [59278.953669] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:08 192.168.122.209 [59278.982124] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:08 192.168.122.209 [59279.052950] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:08 192.168.122.209 [59279.083775] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:08 192.168.122.209 [59279.113190] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:08 192.168.122.209 [59279.191885] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:08 192.168.122.209 [59279.212996] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:08 192.168.122.209 [59279.243033] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:08 192.168.122.209 [59279.308235] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:08 192.168.122.209 [59279.337703] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:08 192.168.122.209 [59279.358258] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:08 192.168.122.209 [59279.426220] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:08 192.168.122.209 [59279.451931] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:08 192.168.122.209 [59279.479387] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:08 192.168.122.209 [59279.546063] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:09 192.168.122.209 [59279.573545] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:09 192.168.122.209 [59279.599853] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:09 192.168.122.209 [59279.666627] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:09 192.168.122.209 [59279.693020] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:09 192.168.122.209 [59279.720044] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:09 192.168.122.209 [59279.783991] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:09 192.168.122.209 [59279.815028] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:09 192.168.122.209 [59279.840076] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:09 192.168.122.209 [59279.904968] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:09 192.168.122.209 [59279.935810] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:09 192.168.122.209 [59279.961110] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:09 192.168.122.209 [59280.024166] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:09 192.168.122.209 [59280.054202] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:09 192.168.122.209 [59280.077445] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:09 192.168.122.209 [59280.146016] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:09 192.168.122.209 [59280.171880] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:09 192.168.122.209 [59280.202326] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:09 192.168.122.209 [59280.264415] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:09 192.168.122.209 [59280.290845] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:09 192.168.122.209 [59280.316528] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:09 192.168.122.209 [59280.385896] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:09 192.168.122.209 [59280.409688] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:09 192.168.122.209 [59280.435500] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:09 192.168.122.209 [59280.504369] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:09 192.168.122.209 [59280.539254] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:10 192.168.122.209 [59280.564544] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:10 192.168.122.209 [59280.636152] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:10 192.168.122.209 [59280.661666] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:10 192.168.122.209 [59280.687025] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:10 192.168.122.209 [59280.752591] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:10 192.168.122.209 [59280.783159] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:10 192.168.122.209 [59280.806261] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:10 192.168.122.209 [59280.873866] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:10 192.168.122.209 [59280.907501] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:10 192.168.122.209 [59280.937300] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:10 192.168.122.209 [59281.004654] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:10 192.168.122.209 [59281.031202] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:10 192.168.122.209 [59281.054927] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:10 192.168.122.209 [59281.129009] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:10 192.168.122.209 [59281.151066] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:10 192.168.122.209 [59281.177787] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:10 192.168.122.209 [59281.244383] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:10 192.168.122.209 [59281.274009] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:10 192.168.122.209 [59281.295129] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:10 192.168.122.209 [59281.367223] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:10 192.168.122.209 [59281.388164] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:10 192.168.122.209 [59281.417858] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:10 192.168.122.209 [59281.487903] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:10 192.168.122.209 [59281.524786] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:10 192.168.122.209 [59281.545600] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:11 192.168.122.209 [59281.611796] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:11 192.168.122.209 [59281.637959] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:11 192.168.122.209 [59281.664573] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:11 192.168.122.209 [59281.734014] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:11 192.168.122.209 [59281.759159] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:11 192.168.122.209 [59281.786196] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:11 192.168.122.209 [59281.850017] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:11 192.168.122.209 [59281.877125] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:11 192.168.122.209 [59281.902434] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:11 192.168.122.209 [59281.969573] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:11 192.168.122.209 [59281.995659] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:11 192.168.122.209 [59282.017943] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:11 192.168.122.209 [59282.084990] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:11 192.168.122.209 [59282.112243] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:11 192.168.122.209 [59282.139322] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:11 192.168.122.209 [59282.201381] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:11 192.168.122.209 [59282.227548] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:11 192.168.122.209 [59282.251679] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:11 192.168.122.209 [59282.317672] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:11 192.168.122.209 [59282.345589] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:11 192.168.122.209 [59282.371582] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:11 192.168.122.209 [59282.436330] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:11 192.168.122.209 [59282.462975] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:11 192.168.122.209 [59282.486701] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:12 192.168.122.209 [59282.562745] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:12 192.168.122.209 [59282.581790] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:12 192.168.122.209 [59282.608191] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:12 192.168.122.209 [59282.672285] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:12 192.168.122.209 [59282.705944] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:12 192.168.122.209 [59282.726330] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:12 192.168.122.209 [59282.790885] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:12 192.168.122.209 [59282.819522] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:12 192.168.122.209 [59282.854599] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:12 192.168.122.209 [59282.923363] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:12 192.168.122.209 [59282.961557] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:12 192.168.122.209 [59282.985825] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:12 192.168.122.209 [59283.052808] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:12 192.168.122.209 [59283.079536] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:12 192.168.122.209 [59283.112286] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:12 192.168.122.209 [59283.170833] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:12 192.168.122.209 [59283.206457] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:12 192.168.122.209 [59283.235046] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:12 192.168.122.209 [59283.296550] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:12 192.168.122.209 [59283.317820] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:12 192.168.122.209 [59283.355976] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:12 192.168.122.209 [59283.426886] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:12 192.168.122.209 [59283.461350] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:12 192.168.122.209 [59283.482895] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:13 192.168.122.209 [59283.553403] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:13 192.168.122.209 [59283.574370] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:13 192.168.122.209 [59283.606620] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:13 192.168.122.209 [59283.671509] [tempesta fw] 127.0.0.2 "good" "POST / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=102f00a80280" Apr 26 08:32:13 192.168.122.209 [59284.097333] [tdb] Close table 'client0.tdb' Apr 26 08:32:13 192.168.122.209 [59284.295533] [tdb] Close table 'sessions0.tdb' Apr 26 08:32:16 192.168.122.209 [59287.459785] [tdb] Close table 'cache0.tdb' Apr 26 08:32:17 192.168.122.209 [59287.691042] [tdb] Close table 'filter0.tdb' Apr 26 08:32:17 192.168.122.209 [59287.691473] [tempesta fw] modules are stopped Apr 26 08:32:17 192.168.122.209 [59287.931447] [tempesta fw] exiting... Apr 26 08:32:17 192.168.122.209 [59288.043257] [tdb] Shutdown Tempesta DB Apr 26 08:32:17 192.168.122.209 [59288.250464] End test: http2_general.test_h2_hpack.TestLoadingHeadersFromHpackDynamicTable.test_content_type_from_hpack_table Apr 26 08:32:17 192.168.122.209 [59288.259626] Start test: http2_general.test_h2_hpack.TestLoadingHeadersFromHpackDynamicTable.test_cookie_from_hpack_table_huffman_1 Apr 26 08:32:18 192.168.122.209 [59289.364902] [tdb] Start Tempesta DB Apr 26 08:32:18 192.168.122.209 [59289.513115] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:32:20 192.168.122.209 [59291.288196] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [59291.288196] Maybe that's fine, but it's worth checking the [59291.288196] config - if there is no relations between the [59291.288196] names, then host name confusion attack is possible. Apr 26 08:32:20 192.168.122.209 [59291.434805] [tempesta fw] Configuration processing is completed. Apr 26 08:32:20 192.168.122.209 [59291.486802] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:32:21 192.168.122.209 [59291.906865] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:32:21 192.168.122.209 [59291.941951] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:32:21 192.168.122.209 [59291.969541] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:32:21 192.168.122.209 [59292.020062] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:32:21 192.168.122.209 [59292.058711] [tempesta fw] Tempesta FW is ready Apr 26 08:32:21 192.168.122.209 [59292.280052] [tempesta fw] 127.0.0.2 "good" "GET / HTTP/2.0" 200 0 "http://tempesta-tech.com:8080" "-" "ja5t=66cb8f00d4250002" "ja5h=2a67f7f008cc440" Apr 26 08:32:21 192.168.122.209 [59292.380395] [tempesta fw] 127.0.0.2 "good" "GET / HTTP/2.0" 200 0 "http://tempesta-tech.com:8080" "-" "ja5t=66cb8f00d4250002" "ja5h=3dae7f008c83c0" Apr 26 08:32:22 192.168.122.209 [59292.999129] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 08:32:22 192.168.122.209 [59293.127960] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [59293.127960] Maybe that's fine, but it's worth checking the [59293.127960] config - if there is no relations between the [59293.127960] names, then host name confusion attack is possible. Apr 26 08:32:22 192.168.122.209 [59293.346824] [tempesta fw] Configuration processing is completed. Apr 26 08:32:22 192.168.122.209 [59293.547710] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000004da5e5e5 Apr 26 08:32:23 192.168.122.209 [59293.754820] [tempesta fw] Tempesta FW is ready Apr 26 08:32:23 192.168.122.209 [59293.790665] [tempesta fw] Warning: parsed request exceeded ja5h limit: 127.0.0.2 Apr 26 08:32:23 192.168.122.209 [59293.791362] [tempesta fw] 127.0.0.2 "-" "GET / HTTP/2.0" 403 0 "http://tempesta-tech.com:8080" "-" "ja5t=66cb8f00d4250002" "ja5h=2a67f7f008cc440" Apr 26 08:32:23 192.168.122.209 [59293.877836] [tempesta fw] Warning: parsed request exceeded ja5h limit: 127.0.0.2 Apr 26 08:32:23 192.168.122.209 [59293.878711] [tempesta fw] 127.0.0.2 "-" "GET / HTTP/2.0" 403 0 "http://tempesta-tech.com:8080" "-" "ja5t=66cb8f00d4250002" "ja5h=2a67f7f008cc440" Apr 26 08:32:23 192.168.122.209 [59294.309786] [tdb] Close table 'client0.tdb' Apr 26 08:32:23 192.168.122.209 [59294.501801] [tdb] Close table 'sessions0.tdb' Apr 26 08:32:27 192.168.122.209 [59297.782192] [tdb] Close table 'cache0.tdb' Apr 26 08:32:27 192.168.122.209 [59298.042541] [tdb] Close table 'filter0.tdb' Apr 26 08:32:28 192.168.122.209 [59298.679126] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 08:32:28 192.168.122.209 [59298.679593] [tempesta fw] modules are stopped Apr 26 08:32:28 192.168.122.209 [59298.931205] [tempesta fw] exiting... Apr 26 08:32:28 192.168.122.209 [59299.112251] [tdb] Shutdown Tempesta DB Apr 26 08:32:28 192.168.122.209 [59299.322827] End test: http2_general.test_h2_hpack.TestLoadingHeadersFromHpackDynamicTable.test_cookie_from_hpack_table_huffman_1 Apr 26 08:32:28 192.168.122.209 [59299.337249] Start test: http2_general.test_h2_hpack.TestLoadingHeadersFromHpackDynamicTable.test_cookie_from_hpack_table_huffman_2 Apr 26 08:32:29 192.168.122.209 [59300.325764] [tdb] Start Tempesta DB Apr 26 08:32:29 192.168.122.209 [59300.451120] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:32:31 192.168.122.209 [59302.416289] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [59302.416289] Maybe that's fine, but it's worth checking the [59302.416289] config - if there is no relations between the [59302.416289] names, then host name confusion attack is possible. Apr 26 08:32:31 192.168.122.209 [59302.546913] [tempesta fw] Configuration processing is completed. Apr 26 08:32:32 192.168.122.209 [59302.607456] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:32:32 192.168.122.209 [59303.039295] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:32:32 192.168.122.209 [59303.079932] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:32:32 192.168.122.209 [59303.108510] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:32:32 192.168.122.209 [59303.150931] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:32:32 192.168.122.209 [59303.194846] [tempesta fw] Tempesta FW is ready Apr 26 08:32:32 192.168.122.209 [59303.472101] [tempesta fw] 127.0.0.2 "good" "GET / HTTP/2.0" 200 0 "http://tempesta-tech.com:8080" "-" "ja5t=66cb8f00d4250002" "ja5h=62f91f7f008fec40" Apr 26 08:32:33 192.168.122.209 [59303.558134] [tempesta fw] 127.0.0.2 "good" "GET / HTTP/2.0" 200 0 "http://tempesta-tech.com:8080" "-" "ja5t=66cb8f00d4250002" "ja5h=3dae7f008c83c0" Apr 26 08:32:33 192.168.122.209 [59304.203591] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 08:32:33 192.168.122.209 [59304.335963] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [59304.335963] Maybe that's fine, but it's worth checking the [59304.335963] config - if there is no relations between the [59304.335963] names, then host name confusion attack is possible. Apr 26 08:32:34 192.168.122.209 [59304.554869] [tempesta fw] Configuration processing is completed. Apr 26 08:32:34 192.168.122.209 [59304.734720] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000004da5e5e5 Apr 26 08:32:34 192.168.122.209 [59304.942967] [tempesta fw] Tempesta FW is ready Apr 26 08:32:34 192.168.122.209 [59305.000970] [tempesta fw] Warning: parsed request exceeded ja5h limit: 127.0.0.2 Apr 26 08:32:34 192.168.122.209 [59305.002172] [tempesta fw] 127.0.0.2 "-" "GET / HTTP/2.0" 403 0 "http://tempesta-tech.com:8080" "-" "ja5t=66cb8f00d4250002" "ja5h=62f91f7f008fec40" Apr 26 08:32:34 192.168.122.209 [59305.148475] [tempesta fw] Warning: parsed request exceeded ja5h limit: 127.0.0.2 Apr 26 08:32:34 192.168.122.209 [59305.150564] [tempesta fw] 127.0.0.2 "-" "GET / HTTP/2.0" 403 0 "http://tempesta-tech.com:8080" "-" "ja5t=66cb8f00d4250002" "ja5h=62f91f7f008fec40" Apr 26 08:32:35 192.168.122.209 [59305.583575] [tdb] Close table 'client0.tdb' Apr 26 08:32:35 192.168.122.209 [59305.785500] [tdb] Close table 'sessions0.tdb' Apr 26 08:32:38 192.168.122.209 [59309.069435] [tdb] Close table 'cache0.tdb' Apr 26 08:32:38 192.168.122.209 [59309.285899] [tdb] Close table 'filter0.tdb' Apr 26 08:32:39 192.168.122.209 [59309.971891] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 08:32:39 192.168.122.209 [59309.972339] [tempesta fw] modules are stopped Apr 26 08:32:39 192.168.122.209 [59310.275283] [tempesta fw] exiting... Apr 26 08:32:39 192.168.122.209 [59310.403422] [tdb] Shutdown Tempesta DB Apr 26 08:32:40 192.168.122.209 [59310.588451] End test: http2_general.test_h2_hpack.TestLoadingHeadersFromHpackDynamicTable.test_cookie_from_hpack_table_huffman_2 Apr 26 08:32:40 192.168.122.209 [59310.607531] Start test: http2_general.test_h2_hpack.TestLoadingHeadersFromHpackDynamicTable.test_cookie_from_hpack_table_no_huffman_1 Apr 26 08:32:41 192.168.122.209 [59311.748050] [tdb] Start Tempesta DB Apr 26 08:32:41 192.168.122.209 [59311.894857] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:32:43 192.168.122.209 [59313.936607] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [59313.936607] Maybe that's fine, but it's worth checking the [59313.936607] config - if there is no relations between the [59313.936607] names, then host name confusion attack is possible. Apr 26 08:32:43 192.168.122.209 [59314.071112] [tempesta fw] Configuration processing is completed. Apr 26 08:32:43 192.168.122.209 [59314.123300] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:32:43 192.168.122.209 [59314.550585] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:32:44 192.168.122.209 [59314.577991] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:32:44 192.168.122.209 [59314.605800] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:32:44 192.168.122.209 [59314.651050] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:32:44 192.168.122.209 [59314.698997] [tempesta fw] Tempesta FW is ready Apr 26 08:32:44 192.168.122.209 [59314.921916] [tempesta fw] 127.0.0.2 "good" "GET / HTTP/2.0" 200 0 "http://tempesta-tech.com:8080" "-" "ja5t=66cb8f00d4250002" "ja5h=2a67f7f008cc440" Apr 26 08:32:44 192.168.122.209 [59315.008634] [tempesta fw] 127.0.0.2 "good" "GET / HTTP/2.0" 200 0 "http://tempesta-tech.com:8080" "-" "ja5t=66cb8f00d4250002" "ja5h=3dae7f008c83c0" Apr 26 08:32:45 192.168.122.209 [59315.646021] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 08:32:45 192.168.122.209 [59315.795139] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [59315.795139] Maybe that's fine, but it's worth checking the [59315.795139] config - if there is no relations between the [59315.795139] names, then host name confusion attack is possible. Apr 26 08:32:45 192.168.122.209 [59316.003182] [tempesta fw] Configuration processing is completed. Apr 26 08:32:45 192.168.122.209 [59316.187745] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000004da5e5e5 Apr 26 08:32:45 192.168.122.209 [59316.395100] [tempesta fw] Tempesta FW is ready Apr 26 08:32:45 192.168.122.209 [59316.440398] [tempesta fw] Warning: parsed request exceeded ja5h limit: 127.0.0.2 Apr 26 08:32:45 192.168.122.209 [59316.441523] [tempesta fw] 127.0.0.2 "-" "GET / HTTP/2.0" 403 0 "http://tempesta-tech.com:8080" "-" "ja5t=66cb8f00d4250002" "ja5h=2a67f7f008cc440" Apr 26 08:32:45 192.168.122.209 [59316.522303] [tempesta fw] Warning: parsed request exceeded ja5h limit: 127.0.0.2 Apr 26 08:32:45 192.168.122.209 [59316.523003] [tempesta fw] 127.0.0.2 "-" "GET / HTTP/2.0" 403 0 "http://tempesta-tech.com:8080" "-" "ja5t=66cb8f00d4250002" "ja5h=2a67f7f008cc440" Apr 26 08:32:46 192.168.122.209 [59316.957502] [tdb] Close table 'client0.tdb' Apr 26 08:32:46 192.168.122.209 [59317.145522] [tdb] Close table 'sessions0.tdb' Apr 26 08:32:49 192.168.122.209 [59320.351903] [tdb] Close table 'cache0.tdb' Apr 26 08:32:50 192.168.122.209 [59320.601891] [tdb] Close table 'filter0.tdb' Apr 26 08:32:50 192.168.122.209 [59321.239617] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 08:32:50 192.168.122.209 [59321.240082] [tempesta fw] modules are stopped Apr 26 08:32:50 192.168.122.209 [59321.489185] [tempesta fw] exiting... Apr 26 08:32:51 192.168.122.209 [59321.627746] [tdb] Shutdown Tempesta DB Apr 26 08:32:51 192.168.122.209 [59321.859388] End test: http2_general.test_h2_hpack.TestLoadingHeadersFromHpackDynamicTable.test_cookie_from_hpack_table_no_huffman_1 Apr 26 08:32:51 192.168.122.209 [59321.874010] Start test: http2_general.test_h2_hpack.TestLoadingHeadersFromHpackDynamicTable.test_cookie_from_hpack_table_no_huffman_2 Apr 26 08:32:52 192.168.122.209 [59323.076430] [tdb] Start Tempesta DB Apr 26 08:32:52 192.168.122.209 [59323.219872] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:32:54 192.168.122.209 [59325.228710] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [59325.228710] Maybe that's fine, but it's worth checking the [59325.228710] config - if there is no relations between the [59325.228710] names, then host name confusion attack is possible. Apr 26 08:32:54 192.168.122.209 [59325.375597] [tempesta fw] Configuration processing is completed. Apr 26 08:32:54 192.168.122.209 [59325.439605] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:32:55 192.168.122.209 [59325.858669] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:32:55 192.168.122.209 [59325.906627] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:32:55 192.168.122.209 [59325.945428] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:32:55 192.168.122.209 [59325.995199] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:32:55 192.168.122.209 [59326.039133] [tempesta fw] Tempesta FW is ready Apr 26 08:32:55 192.168.122.209 [59326.300698] [tempesta fw] 127.0.0.2 "good" "GET / HTTP/2.0" 200 0 "http://tempesta-tech.com:8080" "-" "ja5t=66cb8f00d4250002" "ja5h=62f91f7f008fec40" Apr 26 08:32:55 192.168.122.209 [59326.393657] [tempesta fw] 127.0.0.2 "good" "GET / HTTP/2.0" 200 0 "http://tempesta-tech.com:8080" "-" "ja5t=66cb8f00d4250002" "ja5h=3dae7f008c83c0" Apr 26 08:32:56 192.168.122.209 [59327.122199] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 08:32:56 192.168.122.209 [59327.244360] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [59327.244360] Maybe that's fine, but it's worth checking the [59327.244360] config - if there is no relations between the [59327.244360] names, then host name confusion attack is possible. Apr 26 08:32:56 192.168.122.209 [59327.435249] [tempesta fw] Configuration processing is completed. Apr 26 08:32:57 192.168.122.209 [59327.600757] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000004da5e5e5 Apr 26 08:32:57 192.168.122.209 [59327.807204] [tempesta fw] Tempesta FW is ready Apr 26 08:32:57 192.168.122.209 [59327.900152] [tempesta fw] Warning: parsed request exceeded ja5h limit: 127.0.0.2 Apr 26 08:32:57 192.168.122.209 [59327.902041] [tempesta fw] 127.0.0.2 "-" "GET / HTTP/2.0" 403 0 "http://tempesta-tech.com:8080" "-" "ja5t=66cb8f00d4250002" "ja5h=62f91f7f008fec40" Apr 26 08:32:57 192.168.122.209 [59328.009224] [tempesta fw] Warning: parsed request exceeded ja5h limit: 127.0.0.2 Apr 26 08:32:57 192.168.122.209 [59328.009907] [tempesta fw] 127.0.0.2 "-" "GET / HTTP/2.0" 403 0 "http://tempesta-tech.com:8080" "-" "ja5t=66cb8f00d4250002" "ja5h=62f91f7f008fec40" Apr 26 08:32:57 192.168.122.209 [59328.405209] [tdb] Close table 'client0.tdb' Apr 26 08:32:58 192.168.122.209 [59328.600694] [tdb] Close table 'sessions0.tdb' Apr 26 08:33:01 192.168.122.209 [59331.780140] [tdb] Close table 'cache0.tdb' Apr 26 08:33:01 192.168.122.209 [59332.018465] [tdb] Close table 'filter0.tdb' Apr 26 08:33:02 192.168.122.209 [59332.685752] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 08:33:02 192.168.122.209 [59332.686299] [tempesta fw] modules are stopped Apr 26 08:33:02 192.168.122.209 [59332.955312] [tempesta fw] exiting... Apr 26 08:33:02 192.168.122.209 [59333.098739] [tdb] Shutdown Tempesta DB Apr 26 08:33:02 192.168.122.209 [59333.339289] End test: http2_general.test_h2_hpack.TestLoadingHeadersFromHpackDynamicTable.test_cookie_from_hpack_table_no_huffman_2 Apr 26 08:33:02 192.168.122.209 [59333.362273] Start test: http2_general.test_h2_hpack.TestLoadingHeadersFromHpackDynamicTable.test_method_override_from_hpack_table Apr 26 08:33:03 192.168.122.209 [59334.482751] [tdb] Start Tempesta DB Apr 26 08:33:04 192.168.122.209 [59334.622842] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:33:05 192.168.122.209 [59336.512803] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [59336.512803] Maybe that's fine, but it's worth checking the [59336.512803] config - if there is no relations between the [59336.512803] names, then host name confusion attack is possible. Apr 26 08:33:06 192.168.122.209 [59336.659383] [tempesta fw] Configuration processing is completed. Apr 26 08:33:06 192.168.122.209 [59336.717573] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:33:06 192.168.122.209 [59337.138609] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:33:06 192.168.122.209 [59337.170136] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:33:06 192.168.122.209 [59337.196974] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:33:06 192.168.122.209 [59337.271325] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:33:06 192.168.122.209 [59337.315235] [tempesta fw] Tempesta FW is ready Apr 26 08:33:07 192.168.122.209 [59337.937618] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 08:33:07 192.168.122.209 [59338.040791] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [59338.040791] Maybe that's fine, but it's worth checking the [59338.040791] config - if there is no relations between the [59338.040791] names, then host name confusion attack is possible. Apr 26 08:33:07 192.168.122.209 [59338.216517] [tempesta fw] Configuration processing is completed. Apr 26 08:33:07 192.168.122.209 [59338.500078] [tempesta fw] Tempesta FW is ready Apr 26 08:33:08 192.168.122.209 [59338.628585] [tempesta fw] 127.0.0.2 "good" "GET / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=74683da0008c0280" Apr 26 08:33:08 192.168.122.209 [59339.237660] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 08:33:08 192.168.122.209 [59339.364657] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [59339.364657] Maybe that's fine, but it's worth checking the [59339.364657] config - if there is no relations between the [59339.364657] names, then host name confusion attack is possible. Apr 26 08:33:09 192.168.122.209 [59339.555308] [tempesta fw] Configuration processing is completed. Apr 26 08:33:09 192.168.122.209 [59339.827310] [tempesta fw] Tempesta FW is ready Apr 26 08:33:09 192.168.122.209 [59339.881906] [tempesta fw] Warning: frang: restricted overridden HTTP method for 127.0.0.2: 4 (0x10u) Apr 26 08:33:09 192.168.122.209 [59339.884456] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 08:33:09 192.168.122.209 [59339.886599] [tempesta fw] 127.0.0.2 "good" "GET / HTTP/2.0" 403 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=74683da0008c0280" Apr 26 08:33:09 192.168.122.209 [59340.303048] [tdb] Close table 'client0.tdb' Apr 26 08:33:09 192.168.122.209 [59340.499665] [tdb] Close table 'sessions0.tdb' Apr 26 08:33:13 192.168.122.209 [59343.738838] [tdb] Close table 'cache0.tdb' Apr 26 08:33:13 192.168.122.209 [59343.992043] [tdb] Close table 'filter0.tdb' Apr 26 08:33:13 192.168.122.209 [59343.992495] [tempesta fw] modules are stopped Apr 26 08:33:13 192.168.122.209 [59344.250435] [tempesta fw] exiting... Apr 26 08:33:13 192.168.122.209 [59344.362285] [tdb] Shutdown Tempesta DB Apr 26 08:33:14 192.168.122.209 [59344.571585] End test: http2_general.test_h2_hpack.TestLoadingHeadersFromHpackDynamicTable.test_method_override_from_hpack_table Apr 26 08:33:14 192.168.122.209 [59344.592963] Start test: http2_general.test_h2_hpack.TestLoadingHeadersFromHpackDynamicTable.test_pragma_from_hpack_table Apr 26 08:33:15 192.168.122.209 [59345.618306] [tdb] Start Tempesta DB Apr 26 08:33:15 192.168.122.209 [59345.776105] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:33:16 192.168.122.209 [59347.500942] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [59347.500942] Maybe that's fine, but it's worth checking the [59347.500942] config - if there is no relations between the [59347.500942] names, then host name confusion attack is possible. Apr 26 08:33:17 192.168.122.209 [59347.631525] [tempesta fw] Configuration processing is completed. Apr 26 08:33:17 192.168.122.209 [59347.685661] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:33:17 192.168.122.209 [59348.134615] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:33:17 192.168.122.209 [59348.164703] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:33:17 192.168.122.209 [59348.193840] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:33:17 192.168.122.209 [59348.267496] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:33:17 192.168.122.209 [59348.307422] [tempesta fw] Tempesta FW is ready Apr 26 08:33:18 192.168.122.209 [59349.067338] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 08:33:18 192.168.122.209 [59349.220785] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [59349.220785] Maybe that's fine, but it's worth checking the [59349.220785] config - if there is no relations between the [59349.220785] names, then host name confusion attack is possible. Apr 26 08:33:18 192.168.122.209 [59349.435472] [tempesta fw] Configuration processing is completed. Apr 26 08:33:19 192.168.122.209 [59349.772009] [tempesta fw] Tempesta FW is ready Apr 26 08:33:19 192.168.122.209 [59349.896901] [tempesta fw] 127.0.0.2 "good" "GET / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=67618298008c0280" Apr 26 08:33:19 192.168.122.209 [59349.921375] [tempesta fw] 127.0.0.2 "good" "GET / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=67618298008c0280" Apr 26 08:33:19 192.168.122.209 [59349.950950] [tempesta fw] 127.0.0.2 "good" "GET / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=178008c0200" Apr 26 08:33:19 192.168.122.209 [59349.995975] [tempesta fw] 127.0.0.2 "good" "GET / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=178008c0200" Apr 26 08:33:19 192.168.122.209 [59350.408277] [tdb] Close table 'client0.tdb' Apr 26 08:33:20 192.168.122.209 [59350.610300] [tdb] Close table 'sessions0.tdb' Apr 26 08:33:23 192.168.122.209 [59353.935003] [tdb] Close table 'cache0.tdb' Apr 26 08:33:23 192.168.122.209 [59354.178726] [tdb] Close table 'filter0.tdb' Apr 26 08:33:23 192.168.122.209 [59354.179164] [tempesta fw] modules are stopped Apr 26 08:33:23 192.168.122.209 [59354.400734] [tempesta fw] exiting... Apr 26 08:33:23 192.168.122.209 [59354.536835] [tdb] Shutdown Tempesta DB Apr 26 08:33:24 192.168.122.209 [59354.765747] End test: http2_general.test_h2_hpack.TestLoadingHeadersFromHpackDynamicTable.test_pragma_from_hpack_table Apr 26 08:33:24 192.168.122.209 [59354.778797] Start test: http2_general.test_h2_hpack.TestLoadingHeadersFromHpackDynamicTable.test_referer_from_hpack_table Apr 26 08:33:25 192.168.122.209 [59355.909855] [tdb] Start Tempesta DB Apr 26 08:33:25 192.168.122.209 [59356.078904] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:33:27 192.168.122.209 [59357.885278] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [59357.885278] Maybe that's fine, but it's worth checking the [59357.885278] config - if there is no relations between the [59357.885278] names, then host name confusion attack is possible. Apr 26 08:33:27 192.168.122.209 [59358.015676] [tempesta fw] Configuration processing is completed. Apr 26 08:33:27 192.168.122.209 [59358.078190] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:33:28 192.168.122.209 [59358.560900] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:33:28 192.168.122.209 [59358.592881] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:33:28 192.168.122.209 [59358.628095] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:33:28 192.168.122.209 [59358.675627] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:33:28 192.168.122.209 [59358.715554] [tempesta fw] Tempesta FW is ready Apr 26 08:33:28 192.168.122.209 [59358.935886] [tempesta fw] 127.0.0.2 "good" "GET / HTTP/2.0" 200 0 "http://tempesta-tech.com:8080" "-" "ja5t=66cb8f00d4250002" "ja5h=1033008c02c0" Apr 26 08:33:29 192.168.122.209 [59359.655375] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 08:33:29 192.168.122.209 [59359.769042] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [59359.769042] Maybe that's fine, but it's worth checking the [59359.769042] config - if there is no relations between the [59359.769042] names, then host name confusion attack is possible. Apr 26 08:33:29 192.168.122.209 [59359.991680] [tempesta fw] Configuration processing is completed. Apr 26 08:33:29 192.168.122.209 [59360.193761] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000004da5e5e5 Apr 26 08:33:29 192.168.122.209 [59360.423691] [tempesta fw] Tempesta FW is ready Apr 26 08:33:29 192.168.122.209 [59360.485391] [tempesta fw] 127.0.0.2 "good" "GET / HTTP/2.0" 200 0 "-" "-" "ja5t=66cb8f00d4250002" "ja5h=178008c0200" Apr 26 08:33:29 192.168.122.209 [59360.499194] [tempesta fw] Warning: parsed request exceeded ja5h limit: 127.0.0.2 Apr 26 08:33:29 192.168.122.209 [59360.499884] [tempesta fw] 127.0.0.2 "-" "GET / HTTP/2.0" 403 0 "http://tempesta-tech.com:8080" "-" "ja5t=66cb8f00d4250002" "ja5h=1033008c02c0" Apr 26 08:33:30 192.168.122.209 [59360.960983] [tdb] Close table 'client0.tdb' Apr 26 08:33:30 192.168.122.209 [59361.160624] [tdb] Close table 'sessions0.tdb' Apr 26 08:33:34 192.168.122.209 [59364.639784] [tdb] Close table 'cache0.tdb' Apr 26 08:33:34 192.168.122.209 [59364.888813] [tdb] Close table 'filter0.tdb' Apr 26 08:33:35 192.168.122.209 [59365.618801] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 08:33:35 192.168.122.209 [59365.619292] [tempesta fw] modules are stopped Apr 26 08:33:35 192.168.122.209 [59365.901280] [tempesta fw] exiting... Apr 26 08:33:35 192.168.122.209 [59366.044541] [tdb] Shutdown Tempesta DB Apr 26 08:33:35 192.168.122.209 [59366.246277] End test: http2_general.test_h2_hpack.TestLoadingHeadersFromHpackDynamicTable.test_referer_from_hpack_table Apr 26 08:33:35 192.168.122.209 [59366.260402] Start test: http2_general.test_h2_max_frame_size.TestMaxFrameSize.test_data_frame_is_large_than_max_frame_size Apr 26 08:33:36 192.168.122.209 [59367.347686] [tdb] Start Tempesta DB Apr 26 08:33:36 192.168.122.209 [59367.505269] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:33:38 192.168.122.209 [59369.357155] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [59369.357155] Maybe that's fine, but it's worth checking the [59369.357155] config - if there is no relations between the [59369.357155] names, then host name confusion attack is possible. Apr 26 08:33:38 192.168.122.209 [59369.523746] [tempesta fw] Configuration processing is completed. Apr 26 08:33:39 192.168.122.209 [59369.580247] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:33:39 192.168.122.209 [59370.020490] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:33:39 192.168.122.209 [59370.058672] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:33:39 192.168.122.209 [59370.086118] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:33:39 192.168.122.209 [59370.155735] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:33:39 192.168.122.209 [59370.195681] [tempesta fw] Tempesta FW is ready Apr 26 08:33:40 192.168.122.209 [59370.758638] [tdb] Close table 'client0.tdb' Apr 26 08:33:40 192.168.122.209 [59370.957728] [tdb] Close table 'sessions0.tdb' Apr 26 08:33:43 192.168.122.209 [59374.141865] [tdb] Close table 'cache0.tdb' Apr 26 08:33:43 192.168.122.209 [59374.355962] [tdb] Close table 'filter0.tdb' Apr 26 08:33:43 192.168.122.209 [59374.356415] [tempesta fw] modules are stopped Apr 26 08:33:44 192.168.122.209 [59374.593455] [tempesta fw] exiting... Apr 26 08:33:44 192.168.122.209 [59374.710316] [tdb] Shutdown Tempesta DB Apr 26 08:33:44 192.168.122.209 [59374.923237] End test: http2_general.test_h2_max_frame_size.TestMaxFrameSize.test_data_frame_is_large_than_max_frame_size Apr 26 08:33:44 192.168.122.209 [59374.933289] Start test: http2_general.test_h2_max_frame_size.TestMaxFrameSize.test_headers_frame_is_large_than_max_frame_size Apr 26 08:33:45 192.168.122.209 [59375.995332] [tdb] Start Tempesta DB Apr 26 08:33:45 192.168.122.209 [59376.149307] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:33:47 192.168.122.209 [59377.825346] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [59377.825346] Maybe that's fine, but it's worth checking the [59377.825346] config - if there is no relations between the [59377.825346] names, then host name confusion attack is possible. Apr 26 08:33:47 192.168.122.209 [59377.971872] [tempesta fw] Configuration processing is completed. Apr 26 08:33:47 192.168.122.209 [59378.022043] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:33:47 192.168.122.209 [59378.458574] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:33:47 192.168.122.209 [59378.485520] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:33:47 192.168.122.209 [59378.512388] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:33:48 192.168.122.209 [59378.555842] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:33:48 192.168.122.209 [59378.603748] [tempesta fw] Tempesta FW is ready Apr 26 08:33:48 192.168.122.209 [59379.146728] [tdb] Close table 'client0.tdb' Apr 26 08:33:48 192.168.122.209 [59379.334172] [tdb] Close table 'sessions0.tdb' Apr 26 08:33:51 192.168.122.209 [59382.522800] [tdb] Close table 'cache0.tdb' Apr 26 08:33:52 192.168.122.209 [59382.766547] [tdb] Close table 'filter0.tdb' Apr 26 08:33:52 192.168.122.209 [59382.766987] [tempesta fw] modules are stopped Apr 26 08:33:52 192.168.122.209 [59383.005855] [tempesta fw] exiting... Apr 26 08:33:52 192.168.122.209 [59383.107151] [tdb] Shutdown Tempesta DB Apr 26 08:33:52 192.168.122.209 [59383.313179] End test: http2_general.test_h2_max_frame_size.TestMaxFrameSize.test_headers_frame_is_large_than_max_frame_size Apr 26 08:33:52 192.168.122.209 [59383.323338] Start test: http2_general.test_h2_max_frame_size.TestMaxFrameSize.test_large_data_frame_in_response Apr 26 08:33:53 192.168.122.209 [59384.383349] [tdb] Start Tempesta DB Apr 26 08:33:53 192.168.122.209 [59384.527739] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:33:55 192.168.122.209 [59386.053415] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [59386.053415] Maybe that's fine, but it's worth checking the [59386.053415] config - if there is no relations between the [59386.053415] names, then host name confusion attack is possible. Apr 26 08:33:55 192.168.122.209 [59386.199934] [tempesta fw] Configuration processing is completed. Apr 26 08:33:55 192.168.122.209 [59386.252451] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:33:56 192.168.122.209 [59386.693991] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:33:56 192.168.122.209 [59386.721359] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:33:56 192.168.122.209 [59386.749126] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:33:56 192.168.122.209 [59386.799948] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:33:56 192.168.122.209 [59386.839908] [tempesta fw] Tempesta FW is ready Apr 26 08:34:00 192.168.122.209 [59390.990265] [tdb] Close table 'client0.tdb' Apr 26 08:34:00 192.168.122.209 [59391.179175] [tdb] Close table 'sessions0.tdb' Apr 26 08:34:03 192.168.122.209 [59394.404963] [tdb] Close table 'cache0.tdb' Apr 26 08:34:04 192.168.122.209 [59394.638645] [tdb] Close table 'filter0.tdb' Apr 26 08:34:04 192.168.122.209 [59394.639084] [tempesta fw] modules are stopped Apr 26 08:34:04 192.168.122.209 [59394.841933] [tempesta fw] exiting... Apr 26 08:34:04 192.168.122.209 [59394.945049] [tdb] Shutdown Tempesta DB Apr 26 08:34:04 192.168.122.209 [59395.168156] End test: http2_general.test_h2_max_frame_size.TestMaxFrameSize.test_large_data_frame_in_response Apr 26 08:34:04 192.168.122.209 [59395.181156] Start test: http2_general.test_h2_max_frame_size.TestMaxFrameSize.test_large_headers_frame_in_response Apr 26 08:34:05 192.168.122.209 [59396.173929] [tdb] Start Tempesta DB Apr 26 08:34:05 192.168.122.209 [59396.327194] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:34:07 192.168.122.209 [59397.929449] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [59397.929449] Maybe that's fine, but it's worth checking the [59397.929449] config - if there is no relations between the [59397.929449] names, then host name confusion attack is possible. Apr 26 08:34:07 192.168.122.209 [59398.096111] [tempesta fw] Configuration processing is completed. Apr 26 08:34:07 192.168.122.209 [59398.146093] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:34:08 192.168.122.209 [59398.567190] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:34:08 192.168.122.209 [59398.594041] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:34:08 192.168.122.209 [59398.621896] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:34:08 192.168.122.209 [59398.668061] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:34:08 192.168.122.209 [59398.708053] [tempesta fw] Tempesta FW is ready Apr 26 08:34:11 192.168.122.209 [59401.780887] [tdb] Close table 'client0.tdb' Apr 26 08:34:11 192.168.122.209 [59401.969987] [tdb] Close table 'sessions0.tdb' Apr 26 08:34:14 192.168.122.209 [59405.235705] [tdb] Close table 'cache0.tdb' Apr 26 08:34:14 192.168.122.209 [59405.498458] [tdb] Close table 'filter0.tdb' Apr 26 08:34:14 192.168.122.209 [59405.498897] [tempesta fw] modules are stopped Apr 26 08:34:15 192.168.122.209 [59405.751013] [tempesta fw] exiting... Apr 26 08:34:15 192.168.122.209 [59405.909032] [tdb] Shutdown Tempesta DB Apr 26 08:34:15 192.168.122.209 [59406.130660] End test: http2_general.test_h2_max_frame_size.TestMaxFrameSize.test_large_headers_frame_in_response Apr 26 08:34:15 192.168.122.209 [59406.142758] Start test: http2_general.test_h2_perf.TLSPerf.test Apr 26 08:34:16 192.168.122.209 [59407.372452] [tdb] Start Tempesta DB Apr 26 08:34:16 192.168.122.209 [59407.524016] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:34:18 192.168.122.209 [59408.813648] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [59408.813648] Maybe that's fine, but it's worth checking the [59408.813648] config - if there is no relations between the [59408.813648] names, then host name confusion attack is possible. Apr 26 08:34:18 192.168.122.209 [59408.896275] [tempesta fw] Configuration processing is completed. Apr 26 08:34:18 192.168.122.209 [59408.946642] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:34:18 192.168.122.209 [59409.445798] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:34:18 192.168.122.209 [59409.479328] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:34:18 192.168.122.209 [59409.513028] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:34:19 192.168.122.209 [59409.584247] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:34:19 192.168.122.209 [59409.624195] [tempesta fw] Tempesta FW is ready Apr 26 08:34:30 192.168.122.209 [59421.298995] [tdb] Close table 'client0.tdb' Apr 26 08:34:31 192.168.122.209 [59421.611214] [tdb] Close table 'sessions0.tdb' Apr 26 08:34:34 192.168.122.209 [59425.543182] [tdb] Close table 'cache0.tdb' Apr 26 08:34:35 192.168.122.209 [59425.813855] [tdb] Close table 'filter0.tdb' Apr 26 08:34:35 192.168.122.209 [59425.814312] [tempesta fw] modules are stopped Apr 26 08:34:35 192.168.122.209 [59426.080962] [tempesta fw] exiting... Apr 26 08:34:35 192.168.122.209 [59426.213177] [tdb] Shutdown Tempesta DB Apr 26 08:34:35 192.168.122.209 [59426.461126] End test: http2_general.test_h2_perf.TLSPerf.test Apr 26 08:34:35 192.168.122.209 [59426.471398] Start test: http2_general.test_h2_ping.TestH2Ping.test Apr 26 08:34:36 192.168.122.209 [59427.500738] [tdb] Start Tempesta DB Apr 26 08:34:37 192.168.122.209 [59427.649342] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:34:38 192.168.122.209 [59429.158531] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [59429.158531] Maybe that's fine, but it's worth checking the [59429.158531] config - if there is no relations between the [59429.158531] names, then host name confusion attack is possible. Apr 26 08:34:38 192.168.122.209 [59429.216533] [tempesta fw] Configuration processing is completed. Apr 26 08:34:38 192.168.122.209 [59429.277898] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:34:39 192.168.122.209 [59429.699906] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:34:39 192.168.122.209 [59429.726709] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:34:39 192.168.122.209 [59429.753586] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:34:39 192.168.122.209 [59429.844482] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:34:39 192.168.122.209 [59429.912434] [tempesta fw] Tempesta FW is ready Apr 26 08:34:39 192.168.122.209 [59430.496536] [tdb] Close table 'client0.tdb' Apr 26 08:34:40 192.168.122.209 [59430.693505] [tdb] Close table 'sessions0.tdb' Apr 26 08:34:43 192.168.122.209 [59433.864721] [tdb] Close table 'cache0.tdb' Apr 26 08:34:43 192.168.122.209 [59434.083544] [tdb] Close table 'filter0.tdb' Apr 26 08:34:43 192.168.122.209 [59434.083962] [tempesta fw] modules are stopped Apr 26 08:34:43 192.168.122.209 [59434.304956] [tempesta fw] exiting... Apr 26 08:34:43 192.168.122.209 [59434.430765] [tdb] Shutdown Tempesta DB Apr 26 08:34:44 192.168.122.209 [59434.637985] End test: http2_general.test_h2_ping.TestH2Ping.test Apr 26 08:34:44 192.168.122.209 [59434.644248] Start test: http2_general.test_h2_responses.TestH2Responses.test_h2_bad_forwarded_for_ip Apr 26 08:34:45 192.168.122.209 [59435.734672] [tdb] Start Tempesta DB Apr 26 08:34:45 192.168.122.209 [59435.879904] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:34:46 192.168.122.209 [59437.521934] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [59437.521934] Maybe that's fine, but it's worth checking the [59437.521934] config - if there is no relations between the [59437.521934] names, then host name confusion attack is possible. Apr 26 08:34:47 192.168.122.209 [59437.680817] [tempesta fw] Configuration processing is completed. Apr 26 08:34:47 192.168.122.209 [59437.729404] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:34:47 192.168.122.209 [59437.757128] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 08:34:47 192.168.122.209 [59437.785126] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 08:34:47 192.168.122.209 [59437.860586] [tempesta fw] Open listen socket on: 127.0.0.1:8765 Apr 26 08:34:47 192.168.122.209 [59437.904531] [tempesta fw] Tempesta FW is ready Apr 26 08:34:47 192.168.122.209 [59438.062862] [tempesta fw] Warning: request dropped: incorrect X-Forwarded-For header: 127.0.0.2 Apr 26 08:34:47 192.168.122.209 [59438.513436] [tdb] Close table 'client0.tdb' Apr 26 08:34:48 192.168.122.209 [59438.701506] [tdb] Close table 'sessions0.tdb' Apr 26 08:34:48 192.168.122.209 [59438.956327] [tdb] Close table 'filter0.tdb' Apr 26 08:34:48 192.168.122.209 [59438.956775] [tempesta fw] modules are stopped Apr 26 08:34:48 192.168.122.209 [59439.185113] [tempesta fw] exiting... Apr 26 08:34:48 192.168.122.209 [59439.312942] [tdb] Shutdown Tempesta DB Apr 26 08:34:49 192.168.122.209 [59439.580159] End test: http2_general.test_h2_responses.TestH2Responses.test_h2_bad_forwarded_for_ip Apr 26 08:34:49 192.168.122.209 [59439.591786] Start test: http2_general.test_h2_responses.TestH2Responses.test_h2_bad_header Apr 26 08:34:50 192.168.122.209 [59440.647615] [tdb] Start Tempesta DB Apr 26 08:34:50 192.168.122.209 [59440.774854] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:34:51 192.168.122.209 [59441.601899] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [59441.601899] Maybe that's fine, but it's worth checking the [59441.601899] config - if there is no relations between the [59441.601899] names, then host name confusion attack is possible. Apr 26 08:34:51 192.168.122.209 [59441.752666] [tempesta fw] Configuration processing is completed. Apr 26 08:34:51 192.168.122.209 [59441.808948] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:34:51 192.168.122.209 [59441.839053] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 08:34:51 192.168.122.209 [59441.868464] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 08:34:51 192.168.122.209 [59441.956634] [tempesta fw] Open listen socket on: 127.0.0.1:8765 Apr 26 08:34:51 192.168.122.209 [59442.004596] [tempesta fw] Tempesta FW is ready Apr 26 08:34:51 192.168.122.209 [59442.249859] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrCookieV input=0x41('AAAAAA//dfsdf'), len=13, off=0 Apr 26 08:34:52 192.168.122.209 [59442.719703] [tdb] Close table 'client0.tdb' Apr 26 08:34:52 192.168.122.209 [59442.905741] [tdb] Close table 'sessions0.tdb' Apr 26 08:34:52 192.168.122.209 [59443.130048] [tdb] Close table 'filter0.tdb' Apr 26 08:34:52 192.168.122.209 [59443.130493] [tempesta fw] modules are stopped Apr 26 08:34:52 192.168.122.209 [59443.342128] [tempesta fw] exiting... Apr 26 08:34:52 192.168.122.209 [59443.488559] [tdb] Shutdown Tempesta DB Apr 26 08:34:53 192.168.122.209 [59443.713851] End test: http2_general.test_h2_responses.TestH2Responses.test_h2_bad_header Apr 26 08:34:53 192.168.122.209 [59443.719920] Start test: http2_general.test_h2_responses.TestH2Responses.test_h2_bad_host Apr 26 08:34:54 192.168.122.209 [59444.779749] [tdb] Start Tempesta DB Apr 26 08:34:54 192.168.122.209 [59444.908621] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:34:55 192.168.122.209 [59445.809948] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [59445.809948] Maybe that's fine, but it's worth checking the [59445.809948] config - if there is no relations between the [59445.809948] names, then host name confusion attack is possible. Apr 26 08:34:55 192.168.122.209 [59445.960731] [tempesta fw] Configuration processing is completed. Apr 26 08:34:55 192.168.122.209 [59446.015317] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:34:55 192.168.122.209 [59446.043111] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 08:34:55 192.168.122.209 [59446.070700] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 08:34:55 192.168.122.209 [59446.152704] [tempesta fw] Open listen socket on: 127.0.0.1:8765 Apr 26 08:34:55 192.168.122.209 [59446.192650] [tempesta fw] Tempesta FW is ready Apr 26 08:34:55 192.168.122.209 [59446.367165] [tempesta fw] Warning: request has been filtered out via http table: 127.0.0.2 Apr 26 08:34:56 192.168.122.209 [59446.827434] [tdb] Close table 'client0.tdb' Apr 26 08:34:56 192.168.122.209 [59447.023651] [tdb] Close table 'sessions0.tdb' Apr 26 08:34:56 192.168.122.209 [59447.245848] [tdb] Close table 'filter0.tdb' Apr 26 08:34:56 192.168.122.209 [59447.246269] [tempesta fw] modules are stopped Apr 26 08:34:56 192.168.122.209 [59447.492725] [tempesta fw] exiting... Apr 26 08:34:57 192.168.122.209 [59447.613911] [tdb] Shutdown Tempesta DB Apr 26 08:34:57 192.168.122.209 [59447.852230] End test: http2_general.test_h2_responses.TestH2Responses.test_h2_bad_host Apr 26 08:34:57 192.168.122.209 [59447.865516] Start test: http2_general.test_h2_sticky_cookie.H2StickyCookieBaseTestCase.test_h2_cookie_default Apr 26 08:34:58 192.168.122.209 [59448.918472] [tdb] Start Tempesta DB Apr 26 08:34:58 192.168.122.209 [59449.059121] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:34:59 192.168.122.209 [59449.961876] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [59449.961876] Maybe that's fine, but it's worth checking the [59449.961876] config - if there is no relations between the [59449.961876] names, then host name confusion attack is possible. Apr 26 08:34:59 192.168.122.209 [59450.076881] [tempesta fw] Configuration processing is completed. Apr 26 08:34:59 192.168.122.209 [59450.126350] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:34:59 192.168.122.209 [59450.153978] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 08:34:59 192.168.122.209 [59450.182538] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 08:34:59 192.168.122.209 [59450.252759] [tempesta fw] Open listen socket on: 127.0.0.1:8765 Apr 26 08:34:59 192.168.122.209 [59450.296693] [tempesta fw] Tempesta FW is ready Apr 26 08:35:00 192.168.122.209 [59450.980764] [tdb] Close table 'client0.tdb' Apr 26 08:35:00 192.168.122.209 [59451.151475] [tdb] Close table 'sessions0.tdb' Apr 26 08:35:00 192.168.122.209 [59451.391587] [tdb] Close table 'filter0.tdb' Apr 26 08:35:00 192.168.122.209 [59451.392013] [tempesta fw] modules are stopped Apr 26 08:35:01 192.168.122.209 [59451.597349] [tempesta fw] exiting... Apr 26 08:35:01 192.168.122.209 [59451.732451] [tdb] Shutdown Tempesta DB Apr 26 08:35:01 192.168.122.209 [59451.993877] End test: http2_general.test_h2_sticky_cookie.H2StickyCookieBaseTestCase.test_h2_cookie_default Apr 26 08:35:01 192.168.122.209 [59452.010484] Start test: http2_general.test_h2_sticky_cookie.H2StickyCookieTestCase.test_h2_many_cookie_enforce Apr 26 08:35:02 192.168.122.209 [59453.085028] [tdb] Start Tempesta DB Apr 26 08:35:02 192.168.122.209 [59453.229684] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:35:03 192.168.122.209 [59454.122107] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [59454.122107] Maybe that's fine, but it's worth checking the [59454.122107] config - if there is no relations between the [59454.122107] names, then host name confusion attack is possible. Apr 26 08:35:03 192.168.122.209 [59454.244835] [tempesta fw] Configuration processing is completed. Apr 26 08:35:03 192.168.122.209 [59454.302454] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:35:03 192.168.122.209 [59454.334508] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 08:35:03 192.168.122.209 [59454.365092] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 08:35:03 192.168.122.209 [59454.444706] [tempesta fw] Open listen socket on: 127.0.0.1:8765 Apr 26 08:35:03 192.168.122.209 [59454.488744] [tempesta fw] Tempesta FW is ready Apr 26 08:35:04 192.168.122.209 [59455.121295] [tdb] Close table 'client0.tdb' Apr 26 08:35:04 192.168.122.209 [59455.305066] [tdb] Close table 'sessions0.tdb' Apr 26 08:35:04 192.168.122.209 [59455.545386] [tdb] Close table 'filter0.tdb' Apr 26 08:35:04 192.168.122.209 [59455.545813] [tempesta fw] modules are stopped Apr 26 08:35:05 192.168.122.209 [59455.761863] [tempesta fw] exiting... Apr 26 08:35:05 192.168.122.209 [59455.868339] [tdb] Shutdown Tempesta DB Apr 26 08:35:05 192.168.122.209 [59456.128434] End test: http2_general.test_h2_sticky_cookie.H2StickyCookieTestCase.test_h2_many_cookie_enforce Apr 26 08:35:05 192.168.122.209 [59456.141568] Start test: http2_general.test_h2_sticky_cookie.H2StickyCookieTestCase.test_h2_no_cookie_enforce Apr 26 08:35:06 192.168.122.209 [59457.182687] [tdb] Start Tempesta DB Apr 26 08:35:06 192.168.122.209 [59457.312940] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:35:07 192.168.122.209 [59458.110116] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [59458.110116] Maybe that's fine, but it's worth checking the [59458.110116] config - if there is no relations between the [59458.110116] names, then host name confusion attack is possible. Apr 26 08:35:07 192.168.122.209 [59458.232914] [tempesta fw] Configuration processing is completed. Apr 26 08:35:07 192.168.122.209 [59458.303187] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:35:07 192.168.122.209 [59458.334927] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 08:35:07 192.168.122.209 [59458.365098] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 08:35:07 192.168.122.209 [59458.436860] [tempesta fw] Open listen socket on: 127.0.0.1:8765 Apr 26 08:35:07 192.168.122.209 [59458.476796] [tempesta fw] Tempesta FW is ready Apr 26 08:35:08 192.168.122.209 [59459.071249] [tdb] Close table 'client0.tdb' Apr 26 08:35:08 192.168.122.209 [59459.287357] [tdb] Close table 'sessions0.tdb' Apr 26 08:35:08 192.168.122.209 [59459.525418] [tdb] Close table 'filter0.tdb' Apr 26 08:35:08 192.168.122.209 [59459.525847] [tempesta fw] modules are stopped Apr 26 08:35:09 192.168.122.209 [59459.789938] [tempesta fw] exiting... Apr 26 08:35:09 192.168.122.209 [59459.921370] [tdb] Shutdown Tempesta DB Apr 26 08:35:09 192.168.122.209 [59460.174795] End test: http2_general.test_h2_sticky_cookie.H2StickyCookieTestCase.test_h2_no_cookie_enforce Apr 26 08:35:09 192.168.122.209 [59460.186319] Start test: http2_general.test_h2_stream_priority.TestMaxConcurrentStreams.test_max_concurent_stream_exceed_by_priority_frame Apr 26 08:35:10 192.168.122.209 [59461.179129] [tdb] Start Tempesta DB Apr 26 08:35:10 192.168.122.209 [59461.303312] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:35:11 192.168.122.209 [59462.282445] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [59462.282445] Maybe that's fine, but it's worth checking the [59462.282445] config - if there is no relations between the [59462.282445] names, then host name confusion attack is possible. Apr 26 08:35:11 192.168.122.209 [59462.444938] [tempesta fw] Configuration processing is completed. Apr 26 08:35:11 192.168.122.209 [59462.497132] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:35:12 192.168.122.209 [59462.921094] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:35:12 192.168.122.209 [59462.948925] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:35:12 192.168.122.209 [59462.976638] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:35:12 192.168.122.209 [59463.020861] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:35:12 192.168.122.209 [59463.060864] [tempesta fw] Tempesta FW is ready Apr 26 08:35:13 192.168.122.209 [59463.671369] [tdb] Close table 'client0.tdb' Apr 26 08:35:13 192.168.122.209 [59463.856875] [tdb] Close table 'sessions0.tdb' Apr 26 08:35:16 192.168.122.209 [59467.104183] [tdb] Close table 'cache0.tdb' Apr 26 08:35:16 192.168.122.209 [59467.337480] [tdb] Close table 'filter0.tdb' Apr 26 08:35:16 192.168.122.209 [59467.337919] [tempesta fw] modules are stopped Apr 26 08:35:17 192.168.122.209 [59467.612238] [tempesta fw] exiting... Apr 26 08:35:17 192.168.122.209 [59467.767907] [tdb] Shutdown Tempesta DB Apr 26 08:35:17 192.168.122.209 [59467.949578] End test: http2_general.test_h2_stream_priority.TestMaxConcurrentStreams.test_max_concurent_stream_exceed_by_priority_frame Apr 26 08:35:17 192.168.122.209 [59467.962283] Start test: http2_general.test_h2_stream_priority.TestMaxConcurrentStreams.test_max_concurent_stream_exceed_by_stream Apr 26 08:35:18 192.168.122.209 [59469.000495] [tdb] Start Tempesta DB Apr 26 08:35:18 192.168.122.209 [59469.139733] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:35:20 192.168.122.209 [59470.966574] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [59470.966574] Maybe that's fine, but it's worth checking the [59470.966574] config - if there is no relations between the [59470.966574] names, then host name confusion attack is possible. Apr 26 08:35:20 192.168.122.209 [59471.113046] [tempesta fw] Configuration processing is completed. Apr 26 08:35:20 192.168.122.209 [59471.163961] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:35:21 192.168.122.209 [59471.586392] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:35:21 192.168.122.209 [59471.614514] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:35:21 192.168.122.209 [59471.641650] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:35:21 192.168.122.209 [59471.684995] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:35:21 192.168.122.209 [59471.741006] [tempesta fw] Tempesta FW is ready Apr 26 08:35:22 192.168.122.209 [59472.570744] [tdb] Close table 'client0.tdb' Apr 26 08:35:22 192.168.122.209 [59472.780871] [tdb] Close table 'sessions0.tdb' Apr 26 08:35:25 192.168.122.209 [59475.935977] [tdb] Close table 'cache0.tdb' Apr 26 08:35:25 192.168.122.209 [59476.178819] [tdb] Close table 'filter0.tdb' Apr 26 08:35:25 192.168.122.209 [59476.179283] [tempesta fw] modules are stopped Apr 26 08:35:25 192.168.122.209 [59476.468054] [tempesta fw] exiting... Apr 26 08:35:26 192.168.122.209 [59476.585484] [tdb] Shutdown Tempesta DB Apr 26 08:35:26 192.168.122.209 [59476.785838] End test: http2_general.test_h2_stream_priority.TestMaxConcurrentStreams.test_max_concurent_stream_exceed_by_stream Apr 26 08:35:26 192.168.122.209 [59476.797608] Start test: http2_general.test_h2_stream_priority.TestMaxConcurrentStreams.test_opening_created_idle_streams_after_exceed_max_concurrent_streams_limit Apr 26 08:35:27 192.168.122.209 [59477.818805] [tdb] Start Tempesta DB Apr 26 08:35:27 192.168.122.209 [59477.957226] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:35:29 192.168.122.209 [59479.738430] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [59479.738430] Maybe that's fine, but it's worth checking the [59479.738430] config - if there is no relations between the [59479.738430] names, then host name confusion attack is possible. Apr 26 08:35:29 192.168.122.209 [59479.893151] [tempesta fw] Configuration processing is completed. Apr 26 08:35:29 192.168.122.209 [59479.952527] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:35:29 192.168.122.209 [59480.378402] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:35:29 192.168.122.209 [59480.406003] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:35:29 192.168.122.209 [59480.432853] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:35:29 192.168.122.209 [59480.485173] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:35:29 192.168.122.209 [59480.525106] [tempesta fw] Tempesta FW is ready Apr 26 08:35:55 192.168.122.209 [59505.563328] [tdb] Close table 'client0.tdb' Apr 26 08:35:55 192.168.122.209 [59505.772583] [tdb] Close table 'sessions0.tdb' Apr 26 08:35:58 192.168.122.209 [59509.476615] [tdb] Close table 'cache0.tdb' Apr 26 08:35:59 192.168.122.209 [59509.750316] [tdb] Close table 'filter0.tdb' Apr 26 08:35:59 192.168.122.209 [59509.750752] [tempesta fw] modules are stopped Apr 26 08:35:59 192.168.122.209 [59510.071286] [tempesta fw] exiting... Apr 26 08:35:59 192.168.122.209 [59510.191356] [tdb] Shutdown Tempesta DB Apr 26 08:36:00 192.168.122.209 [59511.011162] End test: http2_general.test_h2_stream_priority.TestMaxConcurrentStreams.test_opening_created_idle_streams_after_exceed_max_concurrent_streams_limit Apr 26 08:36:00 192.168.122.209 [59511.023613] Start test: http2_general.test_h2_stream_priority.TestMaxConcurrentStreams.test_opening_not_created_idle_streams_after_exceed_max_concurrent_streams_limit Apr 26 08:36:01 192.168.122.209 [59512.075954] [tdb] Start Tempesta DB Apr 26 08:36:01 192.168.122.209 [59512.236225] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:36:02 192.168.122.209 [59513.523073] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [59513.523073] Maybe that's fine, but it's worth checking the [59513.523073] config - if there is no relations between the [59513.523073] names, then host name confusion attack is possible. Apr 26 08:36:03 192.168.122.209 [59513.701592] [tempesta fw] Configuration processing is completed. Apr 26 08:36:03 192.168.122.209 [59513.762683] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:36:03 192.168.122.209 [59514.183641] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:36:03 192.168.122.209 [59514.210924] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:36:03 192.168.122.209 [59514.238246] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:36:03 192.168.122.209 [59514.305638] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:36:03 192.168.122.209 [59514.353565] [tempesta fw] Tempesta FW is ready Apr 26 08:36:22 192.168.122.209 [59532.571581] [tdb] Close table 'client0.tdb' Apr 26 08:36:22 192.168.122.209 [59532.755270] [tdb] Close table 'sessions0.tdb' Apr 26 08:36:25 192.168.122.209 [59536.375090] [tdb] Close table 'cache0.tdb' Apr 26 08:36:26 192.168.122.209 [59536.663138] [tdb] Close table 'filter0.tdb' Apr 26 08:36:26 192.168.122.209 [59536.663583] [tempesta fw] modules are stopped Apr 26 08:36:26 192.168.122.209 [59536.877129] [tempesta fw] exiting... Apr 26 08:36:26 192.168.122.209 [59536.979115] [tdb] Shutdown Tempesta DB Apr 26 08:36:26 192.168.122.209 [59537.339176] End test: http2_general.test_h2_stream_priority.TestMaxConcurrentStreams.test_opening_not_created_idle_streams_after_exceed_max_concurrent_streams_limit Apr 26 08:36:26 192.168.122.209 [59537.349937] Start test: http2_general.test_h2_stream_priority.TestStreamPriorityInHeaders.test_stream_priority_from_existing_stream Apr 26 08:36:27 192.168.122.209 [59538.489462] [tdb] Start Tempesta DB Apr 26 08:36:28 192.168.122.209 [59538.666908] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:36:29 192.168.122.209 [59539.855469] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [59539.855469] Maybe that's fine, but it's worth checking the [59539.855469] config - if there is no relations between the [59539.855469] names, then host name confusion attack is possible. Apr 26 08:36:29 192.168.122.209 [59540.025917] [tempesta fw] Configuration processing is completed. Apr 26 08:36:29 192.168.122.209 [59540.085988] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:36:29 192.168.122.209 [59540.494100] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:36:29 192.168.122.209 [59540.527203] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:36:30 192.168.122.209 [59540.566034] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:36:30 192.168.122.209 [59540.641983] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:36:30 192.168.122.209 [59540.693989] [tempesta fw] Tempesta FW is ready Apr 26 08:37:04 192.168.122.209 [59574.585294] [tdb] Close table 'client0.tdb' Apr 26 08:37:04 192.168.122.209 [59574.790105] [tdb] Close table 'sessions0.tdb' Apr 26 08:37:07 192.168.122.209 [59578.190811] [tdb] Close table 'cache0.tdb' Apr 26 08:37:07 192.168.122.209 [59578.482914] [tdb] Close table 'filter0.tdb' Apr 26 08:37:07 192.168.122.209 [59578.483361] [tempesta fw] modules are stopped Apr 26 08:37:08 192.168.122.209 [59578.680829] [tempesta fw] exiting... Apr 26 08:37:08 192.168.122.209 [59578.821602] [tdb] Shutdown Tempesta DB Apr 26 08:37:08 192.168.122.209 [59579.068115] End test: http2_general.test_h2_stream_priority.TestStreamPriorityInHeaders.test_stream_priority_from_existing_stream Apr 26 08:37:08 192.168.122.209 [59579.089307] Start test: http2_general.test_h2_stream_priority.TestStreamPriorityInHeaders.test_stream_priority_from_existing_stream_complex Apr 26 08:37:09 192.168.122.209 [59580.202239] [tdb] Start Tempesta DB Apr 26 08:37:09 192.168.122.209 [59580.396979] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:37:11 192.168.122.209 [59581.984095] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [59581.984095] Maybe that's fine, but it's worth checking the [59581.984095] config - if there is no relations between the [59581.984095] names, then host name confusion attack is possible. Apr 26 08:37:11 192.168.122.209 [59582.154600] [tempesta fw] Configuration processing is completed. Apr 26 08:37:11 192.168.122.209 [59582.210360] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:37:12 192.168.122.209 [59582.629508] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:37:12 192.168.122.209 [59582.660653] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:37:12 192.168.122.209 [59582.694716] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:37:12 192.168.122.209 [59582.746567] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:37:12 192.168.122.209 [59582.786509] [tempesta fw] Tempesta FW is ready Apr 26 08:37:39 192.168.122.209 [59610.302373] [tdb] Close table 'client0.tdb' Apr 26 08:37:39 192.168.122.209 [59610.518392] [tdb] Close table 'sessions0.tdb' Apr 26 08:37:43 192.168.122.209 [59614.248532] [tdb] Close table 'cache0.tdb' Apr 26 08:37:43 192.168.122.209 [59614.521677] [tdb] Close table 'filter0.tdb' Apr 26 08:37:43 192.168.122.209 [59614.522103] [tempesta fw] modules are stopped Apr 26 08:37:44 192.168.122.209 [59614.753000] [tempesta fw] exiting... Apr 26 08:37:44 192.168.122.209 [59614.866123] [tdb] Shutdown Tempesta DB Apr 26 08:37:45 192.168.122.209 [59615.826299] End test: http2_general.test_h2_stream_priority.TestStreamPriorityInHeaders.test_stream_priority_from_existing_stream_complex Apr 26 08:37:45 192.168.122.209 [59615.842597] Start test: http2_general.test_h2_stream_priority.TestStreamPriorityInHeaders.test_stream_priority_from_existing_stream_complex_exclusive Apr 26 08:37:46 192.168.122.209 [59616.990940] [tdb] Start Tempesta DB Apr 26 08:37:46 192.168.122.209 [59617.164358] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:37:47 192.168.122.209 [59618.236545] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [59618.236545] Maybe that's fine, but it's worth checking the [59618.236545] config - if there is no relations between the [59618.236545] names, then host name confusion attack is possible. Apr 26 08:37:47 192.168.122.209 [59618.386986] [tempesta fw] Configuration processing is completed. Apr 26 08:37:47 192.168.122.209 [59618.440991] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:37:48 192.168.122.209 [59618.910749] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:37:48 192.168.122.209 [59618.943691] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:37:48 192.168.122.209 [59618.973076] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:37:48 192.168.122.209 [59619.014998] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:37:48 192.168.122.209 [59619.055030] [tempesta fw] Tempesta FW is ready Apr 26 08:38:18 192.168.122.209 [59649.165564] [tdb] Close table 'client0.tdb' Apr 26 08:38:18 192.168.122.209 [59649.399330] [tdb] Close table 'sessions0.tdb' Apr 26 08:38:24 192.168.122.209 [59655.508254] [tdb] Close table 'cache0.tdb' Apr 26 08:38:25 192.168.122.209 [59655.777422] [tdb] Close table 'filter0.tdb' Apr 26 08:38:25 192.168.122.209 [59655.777849] [tempesta fw] modules are stopped Apr 26 08:38:25 192.168.122.209 [59656.078377] [tempesta fw] exiting... Apr 26 08:38:25 192.168.122.209 [59656.233055] [tdb] Shutdown Tempesta DB Apr 26 08:38:26 192.168.122.209 [59657.124158] End test: http2_general.test_h2_stream_priority.TestStreamPriorityInHeaders.test_stream_priority_from_existing_stream_complex_exclusive Apr 26 08:38:26 192.168.122.209 [59657.144018] Start test: http2_general.test_h2_stream_priority.TestStreamPriorityInHeaders.test_stream_priority_from_existing_stream_with_removal Apr 26 08:38:27 192.168.122.209 [59658.173932] [tdb] Start Tempesta DB Apr 26 08:38:27 192.168.122.209 [59658.339250] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:38:28 192.168.122.209 [59659.101016] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [59659.101016] Maybe that's fine, but it's worth checking the [59659.101016] config - if there is no relations between the [59659.101016] names, then host name confusion attack is possible. Apr 26 08:38:28 192.168.122.209 [59659.299531] [tempesta fw] Configuration processing is completed. Apr 26 08:38:28 192.168.122.209 [59659.348452] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:38:29 192.168.122.209 [59659.753016] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:38:29 192.168.122.209 [59659.779276] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:38:29 192.168.122.209 [59659.805616] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:38:29 192.168.122.209 [59659.883605] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:38:29 192.168.122.209 [59659.951471] [tempesta fw] Tempesta FW is ready Apr 26 08:39:45 192.168.122.209 [59735.862046] [tdb] Close table 'client0.tdb' Apr 26 08:39:45 192.168.122.209 [59736.083208] [tdb] Close table 'sessions0.tdb' Apr 26 08:39:49 192.168.122.209 [59739.911117] [tdb] Close table 'cache0.tdb' Apr 26 08:39:49 192.168.122.209 [59740.204573] [tdb] Close table 'filter0.tdb' Apr 26 08:39:49 192.168.122.209 [59740.204985] [tempesta fw] modules are stopped Apr 26 08:39:49 192.168.122.209 [59740.450750] [tempesta fw] exiting... Apr 26 08:39:50 192.168.122.209 [59740.566814] [tdb] Shutdown Tempesta DB Apr 26 08:39:51 192.168.122.209 [59741.614341] End test: http2_general.test_h2_stream_priority.TestStreamPriorityInHeaders.test_stream_priority_from_existing_stream_with_removal Apr 26 08:39:51 192.168.122.209 [59741.632982] Start test: http2_general.test_h2_stream_priority.TestStreamPriorityInHeaders.test_stream_priority_from_non_existing_stream Apr 26 08:39:52 192.168.122.209 [59742.752289] [tdb] Start Tempesta DB Apr 26 08:39:52 192.168.122.209 [59742.942080] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:39:53 192.168.122.209 [59743.846181] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [59743.846181] Maybe that's fine, but it's worth checking the [59743.846181] config - if there is no relations between the [59743.846181] names, then host name confusion attack is possible. Apr 26 08:39:53 192.168.122.209 [59744.008797] [tempesta fw] Configuration processing is completed. Apr 26 08:39:53 192.168.122.209 [59744.069263] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:39:53 192.168.122.209 [59744.506774] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:39:53 192.168.122.209 [59744.533784] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:39:54 192.168.122.209 [59744.561988] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:39:54 192.168.122.209 [59744.612741] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:39:54 192.168.122.209 [59744.660688] [tempesta fw] Tempesta FW is ready Apr 26 08:40:27 192.168.122.209 [59777.749135] [tdb] Close table 'client0.tdb' Apr 26 08:40:27 192.168.122.209 [59777.950384] [tdb] Close table 'sessions0.tdb' Apr 26 08:40:31 192.168.122.209 [59781.569972] [tdb] Close table 'cache0.tdb' Apr 26 08:40:31 192.168.122.209 [59781.866784] [tdb] Close table 'filter0.tdb' Apr 26 08:40:31 192.168.122.209 [59781.867213] [tempesta fw] modules are stopped Apr 26 08:40:31 192.168.122.209 [59782.109744] [tempesta fw] exiting... Apr 26 08:40:31 192.168.122.209 [59782.253187] [tdb] Shutdown Tempesta DB Apr 26 08:40:32 192.168.122.209 [59782.785433] End test: http2_general.test_h2_stream_priority.TestStreamPriorityInHeaders.test_stream_priority_from_non_existing_stream Apr 26 08:40:32 192.168.122.209 [59782.799937] Start test: http2_general.test_h2_stream_priority.TestStreamPriorityInPriorityFrames.test_stream_priority_from_existing_stream Apr 26 08:40:33 192.168.122.209 [59783.965303] [tdb] Start Tempesta DB Apr 26 08:40:33 192.168.122.209 [59784.172002] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:40:35 192.168.122.209 [59785.586898] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [59785.586898] Maybe that's fine, but it's worth checking the [59785.586898] config - if there is no relations between the [59785.586898] names, then host name confusion attack is possible. Apr 26 08:40:35 192.168.122.209 [59785.753347] [tempesta fw] Configuration processing is completed. Apr 26 08:40:35 192.168.122.209 [59785.814796] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:40:35 192.168.122.209 [59786.314228] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:40:35 192.168.122.209 [59786.349388] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:40:35 192.168.122.209 [59786.383716] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:40:35 192.168.122.209 [59786.425247] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:40:35 192.168.122.209 [59786.485228] [tempesta fw] Tempesta FW is ready Apr 26 08:41:08 192.168.122.209 [59819.552117] [tdb] Close table 'client0.tdb' Apr 26 08:41:09 192.168.122.209 [59819.739727] [tdb] Close table 'sessions0.tdb' Apr 26 08:41:12 192.168.122.209 [59823.381607] [tdb] Close table 'cache0.tdb' Apr 26 08:41:13 192.168.122.209 [59823.650764] [tdb] Close table 'filter0.tdb' Apr 26 08:41:13 192.168.122.209 [59823.651236] [tempesta fw] modules are stopped Apr 26 08:41:13 192.168.122.209 [59823.903074] [tempesta fw] exiting... Apr 26 08:41:13 192.168.122.209 [59824.043474] [tdb] Shutdown Tempesta DB Apr 26 08:41:13 192.168.122.209 [59824.267925] End test: http2_general.test_h2_stream_priority.TestStreamPriorityInPriorityFrames.test_stream_priority_from_existing_stream Apr 26 08:41:13 192.168.122.209 [59824.276447] Start test: http2_general.test_h2_stream_priority.TestStreamPriorityInPriorityFrames.test_stream_priority_from_existing_stream_complex Apr 26 08:41:14 192.168.122.209 [59825.356760] [tdb] Start Tempesta DB Apr 26 08:41:14 192.168.122.209 [59825.553170] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:41:16 192.168.122.209 [59827.267309] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [59827.267309] Maybe that's fine, but it's worth checking the [59827.267309] config - if there is no relations between the [59827.267309] names, then host name confusion attack is possible. Apr 26 08:41:16 192.168.122.209 [59827.433853] [tempesta fw] Configuration processing is completed. Apr 26 08:41:16 192.168.122.209 [59827.497368] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:41:17 192.168.122.209 [59827.916202] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:41:17 192.168.122.209 [59827.941528] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:41:17 192.168.122.209 [59827.967338] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:41:17 192.168.122.209 [59828.021839] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:41:17 192.168.122.209 [59828.073791] [tempesta fw] Tempesta FW is ready Apr 26 08:42:07 192.168.122.209 [59877.773900] [tdb] Close table 'client0.tdb' Apr 26 08:42:07 192.168.122.209 [59877.999408] [tdb] Close table 'sessions0.tdb' Apr 26 08:42:11 192.168.122.209 [59881.847698] [tdb] Close table 'cache0.tdb' Apr 26 08:42:11 192.168.122.209 [59882.141523] [tdb] Close table 'filter0.tdb' Apr 26 08:42:11 192.168.122.209 [59882.141969] [tempesta fw] modules are stopped Apr 26 08:42:11 192.168.122.209 [59882.348233] [tempesta fw] exiting... Apr 26 08:42:11 192.168.122.209 [59882.447533] [tdb] Shutdown Tempesta DB Apr 26 08:42:12 192.168.122.209 [59883.512612] End test: http2_general.test_h2_stream_priority.TestStreamPriorityInPriorityFrames.test_stream_priority_from_existing_stream_complex Apr 26 08:42:12 192.168.122.209 [59883.527132] Start test: http2_general.test_h2_stream_priority.TestStreamPriorityInPriorityFrames.test_stream_priority_from_non_existing_stream Apr 26 08:42:14 192.168.122.209 [59884.759239] [tdb] Start Tempesta DB Apr 26 08:42:14 192.168.122.209 [59884.937096] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:42:15 192.168.122.209 [59885.828042] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [59885.828042] Maybe that's fine, but it's worth checking the [59885.828042] config - if there is no relations between the [59885.828042] names, then host name confusion attack is possible. Apr 26 08:42:15 192.168.122.209 [59885.990625] [tempesta fw] Configuration processing is completed. Apr 26 08:42:15 192.168.122.209 [59886.040487] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:42:15 192.168.122.209 [59886.438806] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:42:15 192.168.122.209 [59886.466001] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:42:15 192.168.122.209 [59886.497701] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:42:15 192.168.122.209 [59886.542610] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:42:16 192.168.122.209 [59886.586558] [tempesta fw] Tempesta FW is ready Apr 26 08:42:50 192.168.122.209 [59921.520953] [tdb] Close table 'client0.tdb' Apr 26 08:42:51 192.168.122.209 [59921.711852] [tdb] Close table 'sessions0.tdb' Apr 26 08:42:54 192.168.122.209 [59925.380860] [tdb] Close table 'cache0.tdb' Apr 26 08:42:55 192.168.122.209 [59925.634540] [tdb] Close table 'filter0.tdb' Apr 26 08:42:55 192.168.122.209 [59925.634985] [tempesta fw] modules are stopped Apr 26 08:42:55 192.168.122.209 [59925.853017] [tempesta fw] exiting... Apr 26 08:42:55 192.168.122.209 [59926.002214] [tdb] Shutdown Tempesta DB Apr 26 08:42:55 192.168.122.209 [59926.441200] End test: http2_general.test_h2_stream_priority.TestStreamPriorityInPriorityFrames.test_stream_priority_from_non_existing_stream Apr 26 08:42:55 192.168.122.209 [59926.487299] Start test: http2_general.test_h2_stream_priority.TestStreamPriorityTreeRebuild.test_stream_change_parent_stream_exlusive Apr 26 08:42:56 192.168.122.209 [59927.507737] [tdb] Start Tempesta DB Apr 26 08:42:57 192.168.122.209 [59927.678945] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:42:58 192.168.122.209 [59928.980419] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [59928.980419] Maybe that's fine, but it's worth checking the [59928.980419] config - if there is no relations between the [59928.980419] names, then host name confusion attack is possible. Apr 26 08:42:58 192.168.122.209 [59929.131194] [tempesta fw] Configuration processing is completed. Apr 26 08:42:58 192.168.122.209 [59929.180330] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:42:59 192.168.122.209 [59929.638206] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:42:59 192.168.122.209 [59929.668703] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:42:59 192.168.122.209 [59929.697231] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:42:59 192.168.122.209 [59929.739209] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:42:59 192.168.122.209 [59929.779165] [tempesta fw] Tempesta FW is ready Apr 26 08:43:48 192.168.122.209 [59979.472653] [tdb] Close table 'client0.tdb' Apr 26 08:43:49 192.168.122.209 [59979.708335] [tdb] Close table 'sessions0.tdb' Apr 26 08:43:54 192.168.122.209 [59984.900152] [tdb] Close table 'cache0.tdb' Apr 26 08:43:54 192.168.122.209 [59985.166382] [tdb] Close table 'filter0.tdb' Apr 26 08:43:54 192.168.122.209 [59985.166833] [tempesta fw] modules are stopped Apr 26 08:43:54 192.168.122.209 [59985.401916] [tempesta fw] exiting... Apr 26 08:43:54 192.168.122.209 [59985.532474] [tdb] Shutdown Tempesta DB Apr 26 08:43:55 192.168.122.209 [59986.282894] End test: http2_general.test_h2_stream_priority.TestStreamPriorityTreeRebuild.test_stream_change_parent_stream_exlusive Apr 26 08:43:55 192.168.122.209 [59986.296490] Start test: http2_general.test_h2_stream_priority.TestStreamPriorityTreeRebuild.test_stream_change_parent_stream_exlusive_with_rebuild Apr 26 08:43:56 192.168.122.209 [59987.405836] [tdb] Start Tempesta DB Apr 26 08:43:57 192.168.122.209 [59987.586254] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:43:58 192.168.122.209 [59989.421459] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [59989.421459] Maybe that's fine, but it's worth checking the [59989.421459] config - if there is no relations between the [59989.421459] names, then host name confusion attack is possible. Apr 26 08:43:59 192.168.122.209 [59989.571998] [tempesta fw] Configuration processing is completed. Apr 26 08:43:59 192.168.122.209 [59989.630359] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:43:59 192.168.122.209 [59990.071105] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:43:59 192.168.122.209 [59990.099624] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:43:59 192.168.122.209 [59990.128165] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:43:59 192.168.122.209 [59990.179979] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:43:59 192.168.122.209 [59990.223923] [tempesta fw] Tempesta FW is ready Apr 26 08:46:15 192.168.122.209 [60125.781627] [tdb] Close table 'client0.tdb' Apr 26 08:46:15 192.168.122.209 [60126.201275] [tdb] Close table 'sessions0.tdb' Apr 26 08:46:20 192.168.122.209 [60130.671102] [tdb] Close table 'cache0.tdb' Apr 26 08:46:20 192.168.122.209 [60130.958512] [tdb] Close table 'filter0.tdb' Apr 26 08:46:20 192.168.122.209 [60130.958972] [tempesta fw] modules are stopped Apr 26 08:46:20 192.168.122.209 [60131.431282] [tempesta fw] exiting... Apr 26 08:46:20 192.168.122.209 [60131.554511] [tdb] Shutdown Tempesta DB Apr 26 08:46:22 192.168.122.209 [60132.759822] End test: http2_general.test_h2_stream_priority.TestStreamPriorityTreeRebuild.test_stream_change_parent_stream_exlusive_with_rebuild Apr 26 08:46:22 192.168.122.209 [60132.776452] Start test: http2_general.test_h2_stream_priority.TestStreamPriorityTreeRebuild.test_stream_change_parent_stream_not_exlusive Apr 26 08:46:23 192.168.122.209 [60134.103504] [tdb] Start Tempesta DB Apr 26 08:46:23 192.168.122.209 [60134.283973] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:46:24 192.168.122.209 [60135.071258] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [60135.071258] Maybe that's fine, but it's worth checking the [60135.071258] config - if there is no relations between the [60135.071258] names, then host name confusion attack is possible. Apr 26 08:46:24 192.168.122.209 [60135.261945] [tempesta fw] Configuration processing is completed. Apr 26 08:46:24 192.168.122.209 [60135.319525] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:46:25 192.168.122.209 [60135.808102] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:46:25 192.168.122.209 [60135.837324] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:46:25 192.168.122.209 [60135.871682] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:46:25 192.168.122.209 [60135.961933] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:46:25 192.168.122.209 [60136.033886] [tempesta fw] Tempesta FW is ready Apr 26 08:46:58 192.168.122.209 [60168.649056] [tdb] Close table 'client0.tdb' Apr 26 08:46:58 192.168.122.209 [60168.880676] [tdb] Close table 'sessions0.tdb' Apr 26 08:47:02 192.168.122.209 [60172.647282] [tdb] Close table 'cache0.tdb' Apr 26 08:47:02 192.168.122.209 [60172.892306] [tdb] Close table 'filter0.tdb' Apr 26 08:47:02 192.168.122.209 [60172.892737] [tempesta fw] modules are stopped Apr 26 08:47:02 192.168.122.209 [60173.284734] [tempesta fw] exiting... Apr 26 08:47:02 192.168.122.209 [60173.412230] [tdb] Shutdown Tempesta DB Apr 26 08:47:03 192.168.122.209 [60174.436874] End test: http2_general.test_h2_stream_priority.TestStreamPriorityTreeRebuild.test_stream_change_parent_stream_not_exlusive Apr 26 08:47:03 192.168.122.209 [60174.455867] Start test: http2_general.test_h2_stream_priority.TestStreamPriorityTreeRebuild.test_stream_change_parent_stream_not_exlusive_with_rebuild Apr 26 08:47:05 192.168.122.209 [60175.855096] [tdb] Start Tempesta DB Apr 26 08:47:05 192.168.122.209 [60176.060268] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:47:06 192.168.122.209 [60176.931903] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [60176.931903] Maybe that's fine, but it's worth checking the [60176.931903] config - if there is no relations between the [60176.931903] names, then host name confusion attack is possible. Apr 26 08:47:06 192.168.122.209 [60177.102460] [tempesta fw] Configuration processing is completed. Apr 26 08:47:06 192.168.122.209 [60177.157152] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:47:07 192.168.122.209 [60177.566778] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:47:07 192.168.122.209 [60177.594733] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:47:07 192.168.122.209 [60177.622726] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:47:07 192.168.122.209 [60177.666420] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:47:07 192.168.122.209 [60177.710386] [tempesta fw] Tempesta FW is ready Apr 26 08:49:32 192.168.122.209 [60323.340594] [tdb] Close table 'client0.tdb' Apr 26 08:49:33 192.168.122.209 [60323.615191] [tdb] Close table 'sessions0.tdb' Apr 26 08:49:37 192.168.122.209 [60328.155543] [tdb] Close table 'cache0.tdb' Apr 26 08:49:37 192.168.122.209 [60328.434519] [tdb] Close table 'filter0.tdb' Apr 26 08:49:37 192.168.122.209 [60328.434968] [tempesta fw] modules are stopped Apr 26 08:49:38 192.168.122.209 [60328.886103] [tempesta fw] exiting... Apr 26 08:49:38 192.168.122.209 [60329.022948] [tdb] Shutdown Tempesta DB Apr 26 08:49:39 192.168.122.209 [60330.202421] End test: http2_general.test_h2_stream_priority.TestStreamPriorityTreeRebuild.test_stream_change_parent_stream_not_exlusive_with_rebuild Apr 26 08:49:39 192.168.122.209 [60330.234582] Start test: http2_general.test_h2_stream_states.TestClosedStreamState.test_priority_frame_in_closed_state Apr 26 08:49:40 192.168.122.209 [60331.530866] [tdb] Start Tempesta DB Apr 26 08:49:41 192.168.122.209 [60331.712414] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:49:41 192.168.122.209 [60332.357978] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [60332.357978] Maybe that's fine, but it's worth checking the [60332.357978] config - if there is no relations between the [60332.357978] names, then host name confusion attack is possible. Apr 26 08:49:41 192.168.122.209 [60332.540417] [tempesta fw] Configuration processing is completed. Apr 26 08:49:42 192.168.122.209 [60332.613089] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:49:42 192.168.122.209 [60333.035094] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:49:42 192.168.122.209 [60333.062902] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:49:42 192.168.122.209 [60333.090834] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:49:42 192.168.122.209 [60333.180464] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:49:42 192.168.122.209 [60333.232408] [tempesta fw] Tempesta FW is ready Apr 26 08:49:43 192.168.122.209 [60334.030797] [tempesta fw] Warning: tfw_h2_stream_fsm, stream fully closed: stream->id=1, type=2, flags=0x0 Apr 26 08:49:43 192.168.122.209 [60334.478925] [tdb] Close table 'client0.tdb' Apr 26 08:49:44 192.168.122.209 [60334.666946] [tdb] Close table 'sessions0.tdb' Apr 26 08:49:47 192.168.122.209 [60338.168666] [tdb] Close table 'cache0.tdb' Apr 26 08:49:47 192.168.122.209 [60338.419056] [tdb] Close table 'filter0.tdb' Apr 26 08:49:47 192.168.122.209 [60338.419501] [tempesta fw] modules are stopped Apr 26 08:49:48 192.168.122.209 [60338.834125] [tempesta fw] exiting... Apr 26 08:49:48 192.168.122.209 [60338.980283] [tdb] Shutdown Tempesta DB Apr 26 08:49:49 192.168.122.209 [60339.580198] End test: http2_general.test_h2_stream_states.TestClosedStreamState.test_priority_frame_in_closed_state Apr 26 08:49:49 192.168.122.209 [60339.587888] Start test: http2_general.test_h2_stream_states.TestClosedStreamState.test_rst_stream_frame_in_closed_state Apr 26 08:49:49 192.168.122.209 [60340.456752] [tdb] Start Tempesta DB Apr 26 08:49:50 192.168.122.209 [60340.611620] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:49:51 192.168.122.209 [60341.629832] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [60341.629832] Maybe that's fine, but it's worth checking the [60341.629832] config - if there is no relations between the [60341.629832] names, then host name confusion attack is possible. Apr 26 08:49:51 192.168.122.209 [60341.848840] [tempesta fw] Configuration processing is completed. Apr 26 08:49:51 192.168.122.209 [60341.897137] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:49:51 192.168.122.209 [60342.294257] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:49:51 192.168.122.209 [60342.322047] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:49:51 192.168.122.209 [60342.361570] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:49:51 192.168.122.209 [60342.428525] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:49:51 192.168.122.209 [60342.496404] [tempesta fw] Tempesta FW is ready Apr 26 08:49:52 192.168.122.209 [60343.151230] [tdb] Close table 'client0.tdb' Apr 26 08:49:52 192.168.122.209 [60343.348043] [tdb] Close table 'sessions0.tdb' Apr 26 08:49:55 192.168.122.209 [60346.520415] [tdb] Close table 'cache0.tdb' Apr 26 08:49:56 192.168.122.209 [60346.833394] [tdb] Close table 'filter0.tdb' Apr 26 08:49:56 192.168.122.209 [60346.833827] [tempesta fw] modules are stopped Apr 26 08:49:56 192.168.122.209 [60347.086536] [tempesta fw] exiting... Apr 26 08:49:56 192.168.122.209 [60347.193432] [tdb] Shutdown Tempesta DB Apr 26 08:49:56 192.168.122.209 [60347.418716] End test: http2_general.test_h2_stream_states.TestClosedStreamState.test_rst_stream_frame_in_closed_state Apr 26 08:49:56 192.168.122.209 [60347.432935] Start test: http2_general.test_h2_stream_states.TestClosedStreamState.test_window_update_frame_in_closed_state Apr 26 08:49:57 192.168.122.209 [60348.487574] [tdb] Start Tempesta DB Apr 26 08:49:58 192.168.122.209 [60348.671675] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:49:59 192.168.122.209 [60350.130084] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [60350.130084] Maybe that's fine, but it's worth checking the [60350.130084] config - if there is no relations between the [60350.130084] names, then host name confusion attack is possible. Apr 26 08:49:59 192.168.122.209 [60350.280693] [tempesta fw] Configuration processing is completed. Apr 26 08:49:59 192.168.122.209 [60350.328794] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:50:00 192.168.122.209 [60350.774386] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:50:00 192.168.122.209 [60350.812637] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:50:00 192.168.122.209 [60350.850783] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:50:00 192.168.122.209 [60350.908508] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:50:00 192.168.122.209 [60350.948502] [tempesta fw] Tempesta FW is ready Apr 26 08:50:01 192.168.122.209 [60351.656220] [tdb] Close table 'client0.tdb' Apr 26 08:50:01 192.168.122.209 [60351.831741] [tdb] Close table 'sessions0.tdb' Apr 26 08:50:04 192.168.122.209 [60355.180242] [tdb] Close table 'cache0.tdb' Apr 26 08:50:04 192.168.122.209 [60355.465685] [tdb] Close table 'filter0.tdb' Apr 26 08:50:04 192.168.122.209 [60355.466133] [tempesta fw] modules are stopped Apr 26 08:50:05 192.168.122.209 [60355.679940] [tempesta fw] exiting... Apr 26 08:50:05 192.168.122.209 [60355.768573] [tdb] Shutdown Tempesta DB Apr 26 08:50:05 192.168.122.209 [60355.977359] End test: http2_general.test_h2_stream_states.TestClosedStreamState.test_window_update_frame_in_closed_state Apr 26 08:50:05 192.168.122.209 [60355.990451] Start test: http2_general.test_h2_stream_states.TestHalfClosedStreamStateWindowUpdate.test_window_update_frame_in_half_closed_state Apr 26 08:50:06 192.168.122.209 [60356.988546] [tdb] Start Tempesta DB Apr 26 08:50:06 192.168.122.209 [60357.121765] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:50:08 192.168.122.209 [60358.730054] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [60358.730054] Maybe that's fine, but it's worth checking the [60358.730054] config - if there is no relations between the [60358.730054] names, then host name confusion attack is possible. Apr 26 08:50:08 192.168.122.209 [60358.876813] [tempesta fw] Configuration processing is completed. Apr 26 08:50:08 192.168.122.209 [60358.926562] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:50:08 192.168.122.209 [60359.332049] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:50:08 192.168.122.209 [60359.358369] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:50:08 192.168.122.209 [60359.385342] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:50:08 192.168.122.209 [60359.456778] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:50:08 192.168.122.209 [60359.496774] [tempesta fw] Tempesta FW is ready Apr 26 08:51:09 192.168.122.209 [60420.192854] [tdb] Close table 'client0.tdb' Apr 26 08:51:09 192.168.122.209 [60420.420574] [tdb] Close table 'sessions0.tdb' Apr 26 08:51:13 192.168.122.209 [60423.995150] [tdb] Close table 'cache0.tdb' Apr 26 08:51:13 192.168.122.209 [60424.319214] [tdb] Close table 'filter0.tdb' Apr 26 08:51:13 192.168.122.209 [60424.319673] [tempesta fw] modules are stopped Apr 26 08:51:13 192.168.122.209 [60424.533673] [tempesta fw] exiting... Apr 26 08:51:14 192.168.122.209 [60424.688661] [tdb] Shutdown Tempesta DB Apr 26 08:51:14 192.168.122.209 [60424.914851] End test: http2_general.test_h2_stream_states.TestHalfClosedStreamStateWindowUpdate.test_window_update_frame_in_half_closed_state Apr 26 08:51:14 192.168.122.209 [60424.931477] Start test: http2_general.test_h2_stream_states.TestIdleState.test_closing_idle_stream Apr 26 08:51:15 192.168.122.209 [60426.038572] [tdb] Start Tempesta DB Apr 26 08:51:15 192.168.122.209 [60426.212830] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:51:17 192.168.122.209 [60427.787162] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [60427.787162] Maybe that's fine, but it's worth checking the [60427.787162] config - if there is no relations between the [60427.787162] names, then host name confusion attack is possible. Apr 26 08:51:17 192.168.122.209 [60427.941685] [tempesta fw] Configuration processing is completed. Apr 26 08:51:17 192.168.122.209 [60427.998170] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:51:17 192.168.122.209 [60428.439656] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:51:17 192.168.122.209 [60428.467737] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:51:17 192.168.122.209 [60428.501108] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:51:18 192.168.122.209 [60428.593751] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:51:18 192.168.122.209 [60428.661741] [tempesta fw] Tempesta FW is ready Apr 26 08:51:18 192.168.122.209 [60429.327450] [tdb] Close table 'client0.tdb' Apr 26 08:51:18 192.168.122.209 [60429.516939] [tdb] Close table 'sessions0.tdb' Apr 26 08:51:22 192.168.122.209 [60432.817466] [tdb] Close table 'cache0.tdb' Apr 26 08:51:22 192.168.122.209 [60433.107020] [tdb] Close table 'filter0.tdb' Apr 26 08:51:22 192.168.122.209 [60433.107466] [tempesta fw] modules are stopped Apr 26 08:51:22 192.168.122.209 [60433.348886] [tempesta fw] exiting... Apr 26 08:51:22 192.168.122.209 [60433.464339] [tdb] Shutdown Tempesta DB Apr 26 08:51:23 192.168.122.209 [60433.699717] End test: http2_general.test_h2_stream_states.TestIdleState.test_closing_idle_stream Apr 26 08:51:23 192.168.122.209 [60433.710191] Start test: http2_general.test_h2_stream_states.TestIdleState.test_not_closing_idle_stream Apr 26 08:51:24 192.168.122.209 [60434.701248] [tdb] Start Tempesta DB Apr 26 08:51:24 192.168.122.209 [60434.859466] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:51:25 192.168.122.209 [60436.438930] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [60436.438930] Maybe that's fine, but it's worth checking the [60436.438930] config - if there is no relations between the [60436.438930] names, then host name confusion attack is possible. Apr 26 08:51:26 192.168.122.209 [60436.585796] [tempesta fw] Configuration processing is completed. Apr 26 08:51:26 192.168.122.209 [60436.635467] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:51:26 192.168.122.209 [60437.025967] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:51:26 192.168.122.209 [60437.055525] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:51:26 192.168.122.209 [60437.089463] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:51:26 192.168.122.209 [60437.145768] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:51:26 192.168.122.209 [60437.201727] [tempesta fw] Tempesta FW is ready Apr 26 08:51:27 192.168.122.209 [60437.882816] [tdb] Close table 'client0.tdb' Apr 26 08:51:27 192.168.122.209 [60438.072013] [tdb] Close table 'sessions0.tdb' Apr 26 08:51:30 192.168.122.209 [60441.266176] [tdb] Close table 'cache0.tdb' Apr 26 08:51:31 192.168.122.209 [60441.584197] [tdb] Close table 'filter0.tdb' Apr 26 08:51:31 192.168.122.209 [60441.584628] [tempesta fw] modules are stopped Apr 26 08:51:31 192.168.122.209 [60441.786427] [tempesta fw] exiting... Apr 26 08:51:31 192.168.122.209 [60441.899085] [tdb] Shutdown Tempesta DB Apr 26 08:51:31 192.168.122.209 [60442.133019] End test: http2_general.test_h2_stream_states.TestIdleState.test_not_closing_idle_stream Apr 26 08:51:31 192.168.122.209 [60442.147523] Start test: http2_general.test_h2_stream_states.TestIdleState.test_priority_frame_in_idle_state Apr 26 08:51:32 192.168.122.209 [60443.237756] [tdb] Start Tempesta DB Apr 26 08:51:32 192.168.122.209 [60443.374450] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:51:34 192.168.122.209 [60444.927307] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [60444.927307] Maybe that's fine, but it's worth checking the [60444.927307] config - if there is no relations between the [60444.927307] names, then host name confusion attack is possible. Apr 26 08:51:34 192.168.122.209 [60445.089890] [tempesta fw] Configuration processing is completed. Apr 26 08:51:34 192.168.122.209 [60445.142439] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:51:34 192.168.122.209 [60445.552341] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:51:35 192.168.122.209 [60445.578018] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:51:35 192.168.122.209 [60445.603781] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:51:35 192.168.122.209 [60445.685891] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:51:35 192.168.122.209 [60445.729846] [tempesta fw] Tempesta FW is ready Apr 26 08:51:35 192.168.122.209 [60446.382289] [tdb] Close table 'client0.tdb' Apr 26 08:51:36 192.168.122.209 [60446.574387] [tdb] Close table 'sessions0.tdb' Apr 26 08:51:39 192.168.122.209 [60449.766124] [tdb] Close table 'cache0.tdb' Apr 26 08:51:39 192.168.122.209 [60450.033331] [tdb] Close table 'filter0.tdb' Apr 26 08:51:39 192.168.122.209 [60450.034263] [tempesta fw] modules are stopped Apr 26 08:51:39 192.168.122.209 [60450.282178] [tempesta fw] exiting... Apr 26 08:51:39 192.168.122.209 [60450.399221] [tdb] Shutdown Tempesta DB Apr 26 08:51:40 192.168.122.209 [60450.588249] End test: http2_general.test_h2_stream_states.TestIdleState.test_priority_frame_in_idle_state Apr 26 08:51:40 192.168.122.209 [60450.604133] Start test: http2_general.test_h2_stream_states.TestIdleState.test_rst_frame_for_idle_stream Apr 26 08:51:41 192.168.122.209 [60451.643513] [tdb] Start Tempesta DB Apr 26 08:51:41 192.168.122.209 [60451.784060] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:51:42 192.168.122.209 [60453.422715] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [60453.422715] Maybe that's fine, but it's worth checking the [60453.422715] config - if there is no relations between the [60453.422715] names, then host name confusion attack is possible. Apr 26 08:51:42 192.168.122.209 [60453.561997] [tempesta fw] Configuration processing is completed. Apr 26 08:51:43 192.168.122.209 [60453.612581] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:51:43 192.168.122.209 [60454.006890] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:51:43 192.168.122.209 [60454.032447] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:51:43 192.168.122.209 [60454.061960] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:51:43 192.168.122.209 [60454.142001] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:51:43 192.168.122.209 [60454.181874] [tempesta fw] Tempesta FW is ready Apr 26 08:52:44 192.168.122.209 [60514.804743] [tdb] Close table 'client0.tdb' Apr 26 08:52:44 192.168.122.209 [60514.993718] [tdb] Close table 'sessions0.tdb' Apr 26 08:52:47 192.168.122.209 [60518.227218] [tdb] Close table 'cache0.tdb' Apr 26 08:52:47 192.168.122.209 [60518.492337] [tdb] Close table 'filter0.tdb' Apr 26 08:52:47 192.168.122.209 [60518.492774] [tempesta fw] modules are stopped Apr 26 08:52:48 192.168.122.209 [60518.735514] [tempesta fw] exiting... Apr 26 08:52:48 192.168.122.209 [60518.869111] [tdb] Shutdown Tempesta DB Apr 26 08:52:48 192.168.122.209 [60519.081351] End test: http2_general.test_h2_stream_states.TestIdleState.test_rst_frame_for_idle_stream Apr 26 08:52:48 192.168.122.209 [60519.101627] Start test: http2_general.test_h2_stream_states.TestLocHalfClosedStreamState.test_headers Apr 26 08:52:49 192.168.122.209 [60520.180675] [tdb] Start Tempesta DB Apr 26 08:52:49 192.168.122.209 [60520.329357] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:52:51 192.168.122.209 [60521.948314] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [60521.948314] Maybe that's fine, but it's worth checking the [60521.948314] config - if there is no relations between the [60521.948314] names, then host name confusion attack is possible. Apr 26 08:52:51 192.168.122.209 [60522.111129] [tempesta fw] Configuration processing is completed. Apr 26 08:52:51 192.168.122.209 [60522.169289] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:52:52 192.168.122.209 [60522.571204] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:52:52 192.168.122.209 [60522.596394] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:52:52 192.168.122.209 [60522.623394] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:52:52 192.168.122.209 [60522.718876] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:52:52 192.168.122.209 [60522.774765] [tempesta fw] Tempesta FW is ready Apr 26 08:52:55 192.168.122.209 [60525.754388] [tdb] Close table 'client0.tdb' Apr 26 08:52:55 192.168.122.209 [60525.949565] [tdb] Close table 'sessions0.tdb' Apr 26 08:52:58 192.168.122.209 [60529.281034] [tdb] Close table 'cache0.tdb' Apr 26 08:52:58 192.168.122.209 [60529.501284] [tdb] Close table 'filter0.tdb' Apr 26 08:52:58 192.168.122.209 [60529.501709] [tempesta fw] modules are stopped Apr 26 08:52:59 192.168.122.209 [60529.714989] [tempesta fw] exiting... Apr 26 08:52:59 192.168.122.209 [60529.838143] [tdb] Shutdown Tempesta DB Apr 26 08:52:59 192.168.122.209 [60530.046583] End test: http2_general.test_h2_stream_states.TestLocHalfClosedStreamState.test_headers Apr 26 08:52:59 192.168.122.209 [60530.060157] Start test: http2_general.test_h2_stream_states.TestStreamStateCont.test_any_frame_between_header_blocks Apr 26 08:53:00 192.168.122.209 [60531.163180] [tdb] Start Tempesta DB Apr 26 08:53:00 192.168.122.209 [60531.294663] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:53:02 192.168.122.209 [60532.852340] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [60532.852340] Maybe that's fine, but it's worth checking the [60532.852340] config - if there is no relations between the [60532.852340] names, then host name confusion attack is possible. Apr 26 08:53:02 192.168.122.209 [60533.015320] [tempesta fw] Configuration processing is completed. Apr 26 08:53:02 192.168.122.209 [60533.066362] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:53:02 192.168.122.209 [60533.460275] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:53:02 192.168.122.209 [60533.485839] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:53:02 192.168.122.209 [60533.512400] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:53:02 192.168.122.209 [60533.563038] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:53:03 192.168.122.209 [60533.610899] [tempesta fw] Tempesta FW is ready Apr 26 08:53:03 192.168.122.209 [60534.242192] [tdb] Close table 'client0.tdb' Apr 26 08:53:03 192.168.122.209 [60534.437351] [tdb] Close table 'sessions0.tdb' Apr 26 08:53:07 192.168.122.209 [60537.623604] [tdb] Close table 'cache0.tdb' Apr 26 08:53:07 192.168.122.209 [60537.881126] [tdb] Close table 'filter0.tdb' Apr 26 08:53:07 192.168.122.209 [60537.881575] [tempesta fw] modules are stopped Apr 26 08:53:07 192.168.122.209 [60538.159445] [tempesta fw] exiting... Apr 26 08:53:07 192.168.122.209 [60538.274546] [tdb] Shutdown Tempesta DB Apr 26 08:53:07 192.168.122.209 [60538.487065] End test: http2_general.test_h2_stream_states.TestStreamStateCont.test_any_frame_between_header_blocks Apr 26 08:53:07 192.168.122.209 [60538.502286] Start test: http2_general.test_h2_stream_states.TestStreamStateCont.test_error_request_between_header_blocks Apr 26 08:53:08 192.168.122.209 [60539.563711] [tdb] Start Tempesta DB Apr 26 08:53:09 192.168.122.209 [60539.698683] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:53:10 192.168.122.209 [60541.272548] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [60541.272548] Maybe that's fine, but it's worth checking the [60541.272548] config - if there is no relations between the [60541.272548] names, then host name confusion attack is possible. Apr 26 08:53:10 192.168.122.209 [60541.435119] [tempesta fw] Configuration processing is completed. Apr 26 08:53:10 192.168.122.209 [60541.485349] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:53:11 192.168.122.209 [60541.931758] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:53:11 192.168.122.209 [60541.964244] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:53:11 192.168.122.209 [60541.993811] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:53:11 192.168.122.209 [60542.039110] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:53:11 192.168.122.209 [60542.083078] [tempesta fw] Tempesta FW is ready Apr 26 08:53:11 192.168.122.209 [60542.286347] [tempesta fw] Warning: HTTP/2 request dropped: state=RGen_HdrOtherN input=0x42('BAD'), len=3, off=0 Apr 26 08:53:12 192.168.122.209 [60542.715300] [tdb] Close table 'client0.tdb' Apr 26 08:53:12 192.168.122.209 [60542.939723] [tdb] Close table 'sessions0.tdb' Apr 26 08:53:15 192.168.122.209 [60546.175097] [tdb] Close table 'cache0.tdb' Apr 26 08:53:15 192.168.122.209 [60546.422717] [tdb] Close table 'filter0.tdb' Apr 26 08:53:15 192.168.122.209 [60546.423163] [tempesta fw] modules are stopped Apr 26 08:53:16 192.168.122.209 [60546.658239] [tempesta fw] exiting... Apr 26 08:53:16 192.168.122.209 [60546.828183] [tdb] Shutdown Tempesta DB Apr 26 08:53:16 192.168.122.209 [60547.024713] End test: http2_general.test_h2_stream_states.TestStreamStateCont.test_error_request_between_header_blocks Apr 26 08:53:16 192.168.122.209 [60547.038252] Start test: http2_general.test_h2_stream_states.TestStreamStateCont.test_headers_frame_for_other_stream_after_rst Apr 26 08:53:17 192.168.122.209 [60548.091344] [tdb] Start Tempesta DB Apr 26 08:53:17 192.168.122.209 [60548.237520] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:53:19 192.168.122.209 [60549.756733] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [60549.756733] Maybe that's fine, but it's worth checking the [60549.756733] config - if there is no relations between the [60549.756733] names, then host name confusion attack is possible. Apr 26 08:53:19 192.168.122.209 [60549.907215] [tempesta fw] Configuration processing is completed. Apr 26 08:53:19 192.168.122.209 [60549.966094] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:53:19 192.168.122.209 [60550.385760] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:53:19 192.168.122.209 [60550.412527] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:53:19 192.168.122.209 [60550.440515] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:53:19 192.168.122.209 [60550.527217] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:53:20 192.168.122.209 [60550.611197] [tempesta fw] Tempesta FW is ready Apr 26 08:53:21 192.168.122.209 [60551.584391] [tdb] Close table 'client0.tdb' Apr 26 08:53:21 192.168.122.209 [60551.780420] [tdb] Close table 'sessions0.tdb' Apr 26 08:53:24 192.168.122.209 [60555.023996] [tdb] Close table 'cache0.tdb' Apr 26 08:53:24 192.168.122.209 [60555.259457] [tdb] Close table 'filter0.tdb' Apr 26 08:53:24 192.168.122.209 [60555.259876] [tempesta fw] modules are stopped Apr 26 08:53:24 192.168.122.209 [60555.466196] [tempesta fw] exiting... Apr 26 08:53:25 192.168.122.209 [60555.589121] [tdb] Shutdown Tempesta DB Apr 26 08:53:25 192.168.122.209 [60555.804203] End test: http2_general.test_h2_stream_states.TestStreamStateCont.test_headers_frame_for_other_stream_after_rst Apr 26 08:53:25 192.168.122.209 [60555.812564] Start test: http2_general.test_h2_stream_states.TestStreamStateCont.test_headers_frame_for_other_stream_between_header_blocks Apr 26 08:53:26 192.168.122.209 [60556.863317] [tdb] Start Tempesta DB Apr 26 08:53:26 192.168.122.209 [60557.011285] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:53:28 192.168.122.209 [60558.568762] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [60558.568762] Maybe that's fine, but it's worth checking the [60558.568762] config - if there is no relations between the [60558.568762] names, then host name confusion attack is possible. Apr 26 08:53:28 192.168.122.209 [60558.723507] [tempesta fw] Configuration processing is completed. Apr 26 08:53:28 192.168.122.209 [60558.791282] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:53:28 192.168.122.209 [60559.256249] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:53:28 192.168.122.209 [60559.287133] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:53:28 192.168.122.209 [60559.324257] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:53:28 192.168.122.209 [60559.403359] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:53:28 192.168.122.209 [60559.443342] [tempesta fw] Tempesta FW is ready Apr 26 08:53:29 192.168.122.209 [60560.076128] [tdb] Close table 'client0.tdb' Apr 26 08:53:29 192.168.122.209 [60560.268752] [tdb] Close table 'sessions0.tdb' Apr 26 08:53:32 192.168.122.209 [60563.558537] [tdb] Close table 'cache0.tdb' Apr 26 08:53:33 192.168.122.209 [60563.805056] [tdb] Close table 'filter0.tdb' Apr 26 08:53:33 192.168.122.209 [60563.805462] [tempesta fw] modules are stopped Apr 26 08:53:33 192.168.122.209 [60564.012275] [tempesta fw] exiting... Apr 26 08:53:33 192.168.122.209 [60564.107762] [tdb] Shutdown Tempesta DB Apr 26 08:53:33 192.168.122.209 [60564.332417] End test: http2_general.test_h2_stream_states.TestStreamStateCont.test_headers_frame_for_other_stream_between_header_blocks Apr 26 08:53:33 192.168.122.209 [60564.340328] Start test: http2_general.test_h2_stream_states.TestStreamStateContClosed.test_any_frame_between_header_blocks Apr 26 08:53:34 192.168.122.209 [60565.413216] [tdb] Start Tempesta DB Apr 26 08:53:34 192.168.122.209 [60565.546522] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:53:36 192.168.122.209 [60567.077121] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [60567.077121] Maybe that's fine, but it's worth checking the [60567.077121] config - if there is no relations between the [60567.077121] names, then host name confusion attack is possible. Apr 26 08:53:36 192.168.122.209 [60567.235493] [tempesta fw] Configuration processing is completed. Apr 26 08:53:36 192.168.122.209 [60567.293643] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:53:37 192.168.122.209 [60567.753447] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:53:37 192.168.122.209 [60567.783314] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:53:37 192.168.122.209 [60567.812804] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:53:37 192.168.122.209 [60567.863460] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:53:37 192.168.122.209 [60567.915393] [tempesta fw] Tempesta FW is ready Apr 26 08:53:37 192.168.122.209 [60568.538916] [tdb] Close table 'client0.tdb' Apr 26 08:53:38 192.168.122.209 [60568.736550] [tdb] Close table 'sessions0.tdb' Apr 26 08:53:41 192.168.122.209 [60571.985096] [tdb] Close table 'cache0.tdb' Apr 26 08:53:41 192.168.122.209 [60572.222280] [tdb] Close table 'filter0.tdb' Apr 26 08:53:41 192.168.122.209 [60572.222738] [tempesta fw] modules are stopped Apr 26 08:53:41 192.168.122.209 [60572.454781] [tempesta fw] exiting... Apr 26 08:53:42 192.168.122.209 [60572.586830] [tdb] Shutdown Tempesta DB Apr 26 08:53:42 192.168.122.209 [60572.843196] End test: http2_general.test_h2_stream_states.TestStreamStateContClosed.test_any_frame_between_header_blocks Apr 26 08:53:42 192.168.122.209 [60572.849575] Start test: http2_general.test_h2_stream_states.TestStreamStateContClosed.test_error_request_between_header_blocks Apr 26 08:53:43 192.168.122.209 [60573.824174] [tdb] Start Tempesta DB Apr 26 08:53:43 192.168.122.209 [60573.956741] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:53:44 192.168.122.209 [60575.516997] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [60575.516997] Maybe that's fine, but it's worth checking the [60575.516997] config - if there is no relations between the [60575.516997] names, then host name confusion attack is possible. Apr 26 08:53:45 192.168.122.209 [60575.675581] [tempesta fw] Configuration processing is completed. Apr 26 08:53:45 192.168.122.209 [60575.727884] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:53:45 192.168.122.209 [60576.159432] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:53:45 192.168.122.209 [60576.188194] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:53:45 192.168.122.209 [60576.219501] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:53:45 192.168.122.209 [60576.303553] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:53:45 192.168.122.209 [60576.343496] [tempesta fw] Tempesta FW is ready Apr 26 08:53:45 192.168.122.209 [60576.500401] [tempesta fw] Warning: HTTP/2 request dropped: state=RGen_HdrOtherN input=0x42('BAD'), len=3, off=0 Apr 26 08:53:46 192.168.122.209 [60576.928986] [tdb] Close table 'client0.tdb' Apr 26 08:53:46 192.168.122.209 [60577.164805] [tdb] Close table 'sessions0.tdb' Apr 26 08:53:49 192.168.122.209 [60580.351450] [tdb] Close table 'cache0.tdb' Apr 26 08:53:50 192.168.122.209 [60580.641658] [tdb] Close table 'filter0.tdb' Apr 26 08:53:50 192.168.122.209 [60580.642079] [tempesta fw] modules are stopped Apr 26 08:53:50 192.168.122.209 [60580.869341] [tempesta fw] exiting... Apr 26 08:53:50 192.168.122.209 [60580.988867] [tdb] Shutdown Tempesta DB Apr 26 08:53:50 192.168.122.209 [60581.201229] End test: http2_general.test_h2_stream_states.TestStreamStateContClosed.test_error_request_between_header_blocks Apr 26 08:53:50 192.168.122.209 [60581.217646] Start test: http2_general.test_h2_stream_states.TestStreamStateContClosed.test_headers_frame_for_other_stream_after_rst Apr 26 08:53:51 192.168.122.209 [60582.290383] [tdb] Start Tempesta DB Apr 26 08:53:51 192.168.122.209 [60582.434117] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:53:53 192.168.122.209 [60584.061269] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [60584.061269] Maybe that's fine, but it's worth checking the [60584.061269] config - if there is no relations between the [60584.061269] names, then host name confusion attack is possible. Apr 26 08:53:53 192.168.122.209 [60584.207707] [tempesta fw] Configuration processing is completed. Apr 26 08:53:53 192.168.122.209 [60584.266493] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:53:54 192.168.122.209 [60584.666715] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:53:54 192.168.122.209 [60584.692814] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:53:54 192.168.122.209 [60584.729574] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:53:54 192.168.122.209 [60584.803660] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:53:54 192.168.122.209 [60584.863654] [tempesta fw] Tempesta FW is ready Apr 26 08:53:55 192.168.122.209 [60585.893357] [tdb] Close table 'client0.tdb' Apr 26 08:53:55 192.168.122.209 [60586.099836] [tdb] Close table 'sessions0.tdb' Apr 26 08:53:58 192.168.122.209 [60589.306616] [tdb] Close table 'cache0.tdb' Apr 26 08:53:59 192.168.122.209 [60589.572427] [tdb] Close table 'filter0.tdb' Apr 26 08:53:59 192.168.122.209 [60589.572859] [tempesta fw] modules are stopped Apr 26 08:53:59 192.168.122.209 [60589.795934] [tempesta fw] exiting... Apr 26 08:53:59 192.168.122.209 [60589.912596] [tdb] Shutdown Tempesta DB Apr 26 08:53:59 192.168.122.209 [60590.118399] End test: http2_general.test_h2_stream_states.TestStreamStateContClosed.test_headers_frame_for_other_stream_after_rst Apr 26 08:53:59 192.168.122.209 [60590.128589] Start test: http2_general.test_h2_stream_states.TestStreamStateContClosed.test_headers_frame_for_other_stream_between_header_blocks Apr 26 08:54:00 192.168.122.209 [60591.239897] [tdb] Start Tempesta DB Apr 26 08:54:00 192.168.122.209 [60591.380765] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:54:02 192.168.122.209 [60592.997255] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [60592.997255] Maybe that's fine, but it's worth checking the [60592.997255] config - if there is no relations between the [60592.997255] names, then host name confusion attack is possible. Apr 26 08:54:02 192.168.122.209 [60593.155782] [tempesta fw] Configuration processing is completed. Apr 26 08:54:02 192.168.122.209 [60593.215396] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:54:03 192.168.122.209 [60593.734109] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:54:03 192.168.122.209 [60593.766560] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:54:03 192.168.122.209 [60593.800951] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:54:03 192.168.122.209 [60593.843780] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:54:03 192.168.122.209 [60593.899784] [tempesta fw] Tempesta FW is ready Apr 26 08:54:03 192.168.122.209 [60594.528982] [tdb] Close table 'client0.tdb' Apr 26 08:54:04 192.168.122.209 [60594.719039] [tdb] Close table 'sessions0.tdb' Apr 26 08:54:07 192.168.122.209 [60597.933452] [tdb] Close table 'cache0.tdb' Apr 26 08:54:07 192.168.122.209 [60598.185012] [tdb] Close table 'filter0.tdb' Apr 26 08:54:07 192.168.122.209 [60598.185441] [tempesta fw] modules are stopped Apr 26 08:54:07 192.168.122.209 [60598.399528] [tempesta fw] exiting... Apr 26 08:54:07 192.168.122.209 [60598.567894] [tdb] Shutdown Tempesta DB Apr 26 08:54:08 192.168.122.209 [60598.767681] End test: http2_general.test_h2_stream_states.TestStreamStateContClosed.test_headers_frame_for_other_stream_between_header_blocks Apr 26 08:54:08 192.168.122.209 [60598.785204] Start test: http2_general.test_h2_stream_states.TestTwoHeadersFramesFirstWithoutEndStream.test Apr 26 08:54:09 192.168.122.209 [60599.820448] [tdb] Start Tempesta DB Apr 26 08:54:09 192.168.122.209 [60599.953547] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:54:10 192.168.122.209 [60601.537099] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [60601.537099] Maybe that's fine, but it's worth checking the [60601.537099] config - if there is no relations between the [60601.537099] names, then host name confusion attack is possible. Apr 26 08:54:11 192.168.122.209 [60601.691948] [tempesta fw] Configuration processing is completed. Apr 26 08:54:11 192.168.122.209 [60601.746572] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:54:11 192.168.122.209 [60602.154959] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:54:11 192.168.122.209 [60602.180613] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:54:11 192.168.122.209 [60602.206322] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:54:11 192.168.122.209 [60602.295856] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:54:11 192.168.122.209 [60602.343841] [tempesta fw] Tempesta FW is ready Apr 26 08:54:13 192.168.122.209 [60604.184937] [tdb] Close table 'client0.tdb' Apr 26 08:54:13 192.168.122.209 [60604.391415] [tdb] Close table 'sessions0.tdb' Apr 26 08:54:17 192.168.122.209 [60607.633295] [tdb] Close table 'cache0.tdb' Apr 26 08:54:17 192.168.122.209 [60607.899478] [tdb] Close table 'filter0.tdb' Apr 26 08:54:17 192.168.122.209 [60607.899938] [tempesta fw] modules are stopped Apr 26 08:54:17 192.168.122.209 [60608.150365] [tempesta fw] exiting... Apr 26 08:54:17 192.168.122.209 [60608.283907] [tdb] Shutdown Tempesta DB Apr 26 08:54:17 192.168.122.209 [60608.503282] End test: http2_general.test_h2_stream_states.TestTwoHeadersFramesFirstWithoutEndStream.test Apr 26 08:54:17 192.168.122.209 [60608.521173] Start test: http2_general.test_h2_streams.TestH2Stream.test_headers_frame_with_zero_stream_id Apr 26 08:54:19 192.168.122.209 [60609.659446] [tdb] Start Tempesta DB Apr 26 08:54:19 192.168.122.209 [60609.803565] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:54:20 192.168.122.209 [60611.373462] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [60611.373462] Maybe that's fine, but it's worth checking the [60611.373462] config - if there is no relations between the [60611.373462] names, then host name confusion attack is possible. Apr 26 08:54:20 192.168.122.209 [60611.524047] [tempesta fw] Configuration processing is completed. Apr 26 08:54:21 192.168.122.209 [60611.575661] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:54:21 192.168.122.209 [60612.008665] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:54:21 192.168.122.209 [60612.035342] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:54:21 192.168.122.209 [60612.061421] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:54:21 192.168.122.209 [60612.104012] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:54:21 192.168.122.209 [60612.143958] [tempesta fw] Tempesta FW is ready Apr 26 08:54:22 192.168.122.209 [60612.771030] [tdb] Close table 'client0.tdb' Apr 26 08:54:22 192.168.122.209 [60612.978662] [tdb] Close table 'sessions0.tdb' Apr 26 08:54:25 192.168.122.209 [60616.125768] [tdb] Close table 'cache0.tdb' Apr 26 08:54:25 192.168.122.209 [60616.409956] [tdb] Close table 'filter0.tdb' Apr 26 08:54:25 192.168.122.209 [60616.410368] [tempesta fw] modules are stopped Apr 26 08:54:26 192.168.122.209 [60616.638211] [tempesta fw] exiting... Apr 26 08:54:26 192.168.122.209 [60616.806237] [tdb] Shutdown Tempesta DB Apr 26 08:54:26 192.168.122.209 [60616.996679] End test: http2_general.test_h2_streams.TestH2Stream.test_headers_frame_with_zero_stream_id Apr 26 08:54:26 192.168.122.209 [60617.007797] Start test: http2_general.test_h2_streams.TestH2Stream.test_max_concurrent_stream_not_exceeded Apr 26 08:54:27 192.168.122.209 [60618.028125] [tdb] Start Tempesta DB Apr 26 08:54:27 192.168.122.209 [60618.165941] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:54:29 192.168.122.209 [60619.817456] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [60619.817456] Maybe that's fine, but it's worth checking the [60619.817456] config - if there is no relations between the [60619.817456] names, then host name confusion attack is possible. Apr 26 08:54:29 192.168.122.209 [60619.996111] [tempesta fw] Configuration processing is completed. Apr 26 08:54:29 192.168.122.209 [60620.062757] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:54:29 192.168.122.209 [60620.484299] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:54:29 192.168.122.209 [60620.515543] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:54:29 192.168.122.209 [60620.563422] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:54:30 192.168.122.209 [60620.636131] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:54:30 192.168.122.209 [60620.676075] [tempesta fw] Tempesta FW is ready Apr 26 08:54:30 192.168.122.209 [60621.437162] [tdb] Close table 'client0.tdb' Apr 26 08:54:31 192.168.122.209 [60621.654987] [tdb] Close table 'sessions0.tdb' Apr 26 08:54:34 192.168.122.209 [60624.854359] [tdb] Close table 'cache0.tdb' Apr 26 08:54:34 192.168.122.209 [60625.140187] [tdb] Close table 'filter0.tdb' Apr 26 08:54:34 192.168.122.209 [60625.140625] [tempesta fw] modules are stopped Apr 26 08:54:34 192.168.122.209 [60625.377405] [tempesta fw] exiting... Apr 26 08:54:34 192.168.122.209 [60625.494107] [tdb] Shutdown Tempesta DB Apr 26 08:54:35 192.168.122.209 [60625.689705] End test: http2_general.test_h2_streams.TestH2Stream.test_max_concurrent_stream_not_exceeded Apr 26 08:54:35 192.168.122.209 [60625.697835] Start test: http2_general.test_h2_streams.TestH2Stream.test_request_with_even_numbered_stream_id Apr 26 08:54:36 192.168.122.209 [60626.742688] [tdb] Start Tempesta DB Apr 26 08:54:36 192.168.122.209 [60626.887681] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:54:37 192.168.122.209 [60628.469359] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [60628.469359] Maybe that's fine, but it's worth checking the [60628.469359] config - if there is no relations between the [60628.469359] names, then host name confusion attack is possible. Apr 26 08:54:38 192.168.122.209 [60628.620252] [tempesta fw] Configuration processing is completed. Apr 26 08:54:38 192.168.122.209 [60628.671512] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:54:38 192.168.122.209 [60629.071573] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:54:38 192.168.122.209 [60629.097996] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:54:38 192.168.122.209 [60629.126603] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:54:38 192.168.122.209 [60629.208222] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:54:38 192.168.122.209 [60629.252175] [tempesta fw] Tempesta FW is ready Apr 26 08:54:39 192.168.122.209 [60629.836574] [tdb] Close table 'client0.tdb' Apr 26 08:54:39 192.168.122.209 [60630.038627] [tdb] Close table 'sessions0.tdb' Apr 26 08:54:42 192.168.122.209 [60633.248046] [tdb] Close table 'cache0.tdb' Apr 26 08:54:42 192.168.122.209 [60633.563263] [tdb] Close table 'filter0.tdb' Apr 26 08:54:42 192.168.122.209 [60633.563697] [tempesta fw] modules are stopped Apr 26 08:54:43 192.168.122.209 [60633.861396] [tempesta fw] exiting... Apr 26 08:54:43 192.168.122.209 [60633.989788] [tdb] Shutdown Tempesta DB Apr 26 08:54:43 192.168.122.209 [60634.227663] End test: http2_general.test_h2_streams.TestH2Stream.test_request_with_even_numbered_stream_id Apr 26 08:54:43 192.168.122.209 [60634.252558] Start test: http2_general.test_h2_streams.TestH2Stream.test_request_with_large_stream_id Apr 26 08:54:44 192.168.122.209 [60635.297971] [tdb] Start Tempesta DB Apr 26 08:54:44 192.168.122.209 [60635.437086] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:54:46 192.168.122.209 [60637.025754] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [60637.025754] Maybe that's fine, but it's worth checking the [60637.025754] config - if there is no relations between the [60637.025754] names, then host name confusion attack is possible. Apr 26 08:54:46 192.168.122.209 [60637.176397] [tempesta fw] Configuration processing is completed. Apr 26 08:54:46 192.168.122.209 [60637.227699] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:54:47 192.168.122.209 [60637.644102] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:54:47 192.168.122.209 [60637.671459] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:54:47 192.168.122.209 [60637.698612] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:54:47 192.168.122.209 [60637.800372] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:54:47 192.168.122.209 [60637.840323] [tempesta fw] Tempesta FW is ready Apr 26 08:54:47 192.168.122.209 [60638.513657] [tdb] Close table 'client0.tdb' Apr 26 08:54:48 192.168.122.209 [60638.708041] [tdb] Close table 'sessions0.tdb' Apr 26 08:54:51 192.168.122.209 [60641.900662] [tdb] Close table 'cache0.tdb' Apr 26 08:54:51 192.168.122.209 [60642.146264] [tdb] Close table 'filter0.tdb' Apr 26 08:54:51 192.168.122.209 [60642.146683] [tempesta fw] modules are stopped Apr 26 08:54:51 192.168.122.209 [60642.337042] [tempesta fw] exiting... Apr 26 08:54:51 192.168.122.209 [60642.454160] [tdb] Shutdown Tempesta DB Apr 26 08:54:52 192.168.122.209 [60642.637997] End test: http2_general.test_h2_streams.TestH2Stream.test_request_with_large_stream_id Apr 26 08:54:52 192.168.122.209 [60642.660921] Start test: http2_general.test_h2_streams.TestH2Stream.test_reuse_stream_id Apr 26 08:54:53 192.168.122.209 [60643.717936] [tdb] Start Tempesta DB Apr 26 08:54:53 192.168.122.209 [60643.855786] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:54:54 192.168.122.209 [60645.501914] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [60645.501914] Maybe that's fine, but it's worth checking the [60645.501914] config - if there is no relations between the [60645.501914] names, then host name confusion attack is possible. Apr 26 08:54:55 192.168.122.209 [60645.660490] [tempesta fw] Configuration processing is completed. Apr 26 08:54:55 192.168.122.209 [60645.711005] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:54:55 192.168.122.209 [60646.109003] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:54:55 192.168.122.209 [60646.134685] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:54:55 192.168.122.209 [60646.161971] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:54:55 192.168.122.209 [60646.200450] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:54:55 192.168.122.209 [60646.244406] [tempesta fw] Tempesta FW is ready Apr 26 08:54:56 192.168.122.209 [60646.863403] [tdb] Close table 'client0.tdb' Apr 26 08:54:56 192.168.122.209 [60647.060486] [tdb] Close table 'sessions0.tdb' Apr 26 08:54:59 192.168.122.209 [60650.242434] [tdb] Close table 'cache0.tdb' Apr 26 08:54:59 192.168.122.209 [60650.475140] [tdb] Close table 'filter0.tdb' Apr 26 08:54:59 192.168.122.209 [60650.475567] [tempesta fw] modules are stopped Apr 26 08:55:00 192.168.122.209 [60650.712804] [tempesta fw] exiting... Apr 26 08:55:00 192.168.122.209 [60650.809823] [tdb] Shutdown Tempesta DB Apr 26 08:55:00 192.168.122.209 [60651.009227] End test: http2_general.test_h2_streams.TestH2Stream.test_reuse_stream_id Apr 26 08:55:00 192.168.122.209 [60651.034871] Start test: http_general.test_expect_100_continue.TestExpect100ContinueBehavior.test_regular_behaviour Apr 26 08:55:01 192.168.122.209 [60652.103382] [tdb] Start Tempesta DB Apr 26 08:55:01 192.168.122.209 [60652.240066] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:55:02 192.168.122.209 [60653.508588] [tempesta fw] Configuration processing is completed. Apr 26 08:55:02 192.168.122.209 [60653.560993] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:55:03 192.168.122.209 [60653.976046] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:55:03 192.168.122.209 [60654.017773] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:55:03 192.168.122.209 [60654.044710] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:55:03 192.168.122.209 [60654.112542] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:55:03 192.168.122.209 [60654.160491] [tempesta fw] Tempesta FW is ready Apr 26 08:55:03 192.168.122.209 [60654.323546] [tempesta fw] 127.0.0.2 "default" "PUT /test_100 HTTP/1.1" 200 0 "-" "-" "ja5t=0" "ja5h=18d200340200" Apr 26 08:55:04 192.168.122.209 [60654.716142] [tdb] Close table 'client0.tdb' Apr 26 08:55:04 192.168.122.209 [60654.906429] [tdb] Close table 'sessions0.tdb' Apr 26 08:55:07 192.168.122.209 [60658.083546] [tdb] Close table 'cache0.tdb' Apr 26 08:55:07 192.168.122.209 [60658.321992] [tdb] Close table 'filter0.tdb' Apr 26 08:55:07 192.168.122.209 [60658.322704] [tempesta fw] modules are stopped Apr 26 08:55:07 192.168.122.209 [60658.513839] [tempesta fw] exiting... Apr 26 08:55:08 192.168.122.209 [60658.615628] [tdb] Shutdown Tempesta DB Apr 26 08:55:08 192.168.122.209 [60658.852276] End test: http_general.test_expect_100_continue.TestExpect100ContinueBehavior.test_regular_behaviour Apr 26 08:55:08 192.168.122.209 [60658.870349] Start test: http_general.test_expect_100_continue.TestExpect100ContinueBehavior.test_request_pipeline_3_requests_empty_body Apr 26 08:55:09 192.168.122.209 [60659.963997] [tdb] Start Tempesta DB Apr 26 08:55:09 192.168.122.209 [60660.105081] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:55:11 192.168.122.209 [60661.928714] [tempesta fw] Configuration processing is completed. Apr 26 08:55:11 192.168.122.209 [60662.060051] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:55:11 192.168.122.209 [60662.477849] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:55:11 192.168.122.209 [60662.505793] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:55:11 192.168.122.209 [60662.537942] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:55:12 192.168.122.209 [60662.984664] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:55:12 192.168.122.209 [60663.420609] [tempesta fw] Tempesta FW is ready Apr 26 08:55:15 192.168.122.209 [60665.606951] [tempesta fw] 127.0.0.2 "default" "PUT /test HTTP/1.1" 200 0 "-" "-" "ja5t=0" "ja5h=22200340180" Apr 26 08:55:15 192.168.122.209 [60665.623877] [tempesta fw] 127.0.0.2 "default" "PUT /expect HTTP/1.1" 200 0 "-" "-" "ja5t=0" "ja5h=18d200340200" Apr 26 08:55:15 192.168.122.209 [60665.633795] [tempesta fw] 127.0.0.2 "default" "GET /test HTTP/1.1" 200 0 "-" "-" "ja5t=0" "ja5h=4000c0080" Apr 26 08:55:15 192.168.122.209 [60666.423809] [tdb] Close table 'client0.tdb' Apr 26 08:55:16 192.168.122.209 [60666.666616] [tdb] Close table 'sessions0.tdb' Apr 26 08:55:19 192.168.122.209 [60669.852694] [tdb] Close table 'cache0.tdb' Apr 26 08:55:19 192.168.122.209 [60670.095406] [tdb] Close table 'filter0.tdb' Apr 26 08:55:19 192.168.122.209 [60670.095853] [tempesta fw] modules are stopped Apr 26 08:55:19 192.168.122.209 [60670.258378] [tempesta fw] exiting... Apr 26 08:55:19 192.168.122.209 [60670.356832] [tdb] Shutdown Tempesta DB Apr 26 08:55:20 192.168.122.209 [60670.579883] End test: http_general.test_expect_100_continue.TestExpect100ContinueBehavior.test_request_pipeline_3_requests_empty_body Apr 26 08:55:20 192.168.122.209 [60670.588816] Start test: http_general.test_expect_100_continue.TestExpect100ContinueBehavior.test_request_pipeline_delay Apr 26 08:55:21 192.168.122.209 [60671.660529] [tdb] Start Tempesta DB Apr 26 08:55:21 192.168.122.209 [60671.811958] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:55:22 192.168.122.209 [60673.052832] [tempesta fw] Configuration processing is completed. Apr 26 08:55:22 192.168.122.209 [60673.104931] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:55:22 192.168.122.209 [60673.508503] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:55:22 192.168.122.209 [60673.534442] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:55:22 192.168.122.209 [60673.560227] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:55:23 192.168.122.209 [60673.652813] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:55:23 192.168.122.209 [60673.700745] [tempesta fw] Tempesta FW is ready Apr 26 08:55:25 192.168.122.209 [60675.860584] [tempesta fw] 127.0.0.2 "default" "PUT /test HTTP/1.1" 200 0 "-" "-" "ja5t=0" "ja5h=22200340180" Apr 26 08:55:27 192.168.122.209 [60677.879184] [tempesta fw] 127.0.0.2 "default" "PUT /expect HTTP/1.1" 200 0 "-" "-" "ja5t=0" "ja5h=18d200340200" Apr 26 08:55:27 192.168.122.209 [60678.298569] [tdb] Close table 'client0.tdb' Apr 26 08:55:27 192.168.122.209 [60678.494642] [tdb] Close table 'sessions0.tdb' Apr 26 08:55:31 192.168.122.209 [60681.731520] [tdb] Close table 'cache0.tdb' Apr 26 08:55:31 192.168.122.209 [60681.962799] [tdb] Close table 'filter0.tdb' Apr 26 08:55:31 192.168.122.209 [60681.963231] [tempesta fw] modules are stopped Apr 26 08:55:31 192.168.122.209 [60682.130714] [tempesta fw] exiting... Apr 26 08:55:31 192.168.122.209 [60682.242838] [tdb] Shutdown Tempesta DB Apr 26 08:55:31 192.168.122.209 [60682.479682] End test: http_general.test_expect_100_continue.TestExpect100ContinueBehavior.test_request_pipeline_delay Apr 26 08:55:31 192.168.122.209 [60682.495320] Start test: http_general.test_expect_100_continue.TestExpect100ContinueBehavior.test_request_pipeline_delay_3_requests Apr 26 08:55:33 192.168.122.209 [60683.587969] [tdb] Start Tempesta DB Apr 26 08:55:33 192.168.122.209 [60683.742084] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:55:34 192.168.122.209 [60685.085004] [tempesta fw] Configuration processing is completed. Apr 26 08:55:34 192.168.122.209 [60685.135211] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:55:34 192.168.122.209 [60685.525755] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:55:34 192.168.122.209 [60685.550842] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:55:35 192.168.122.209 [60685.576847] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:55:35 192.168.122.209 [60685.628898] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:55:35 192.168.122.209 [60685.672909] [tempesta fw] Tempesta FW is ready Apr 26 08:55:37 192.168.122.209 [60687.837339] [tempesta fw] 127.0.0.2 "default" "PUT /test HTTP/1.1" 200 0 "-" "-" "ja5t=0" "ja5h=22200340180" Apr 26 08:55:39 192.168.122.209 [60689.855969] [tempesta fw] 127.0.0.2 "default" "PUT /expect HTTP/1.1" 200 0 "-" "-" "ja5t=0" "ja5h=18d200340200" Apr 26 08:55:39 192.168.122.209 [60689.863726] [tempesta fw] 127.0.0.2 "default" "GET /test HTTP/1.1" 200 0 "-" "-" "ja5t=0" "ja5h=4000c0080" Apr 26 08:55:39 192.168.122.209 [60690.310699] [tdb] Close table 'client0.tdb' Apr 26 08:55:39 192.168.122.209 [60690.504502] [tdb] Close table 'sessions0.tdb' Apr 26 08:55:43 192.168.122.209 [60693.761591] [tdb] Close table 'cache0.tdb' Apr 26 08:55:43 192.168.122.209 [60694.018572] [tdb] Close table 'filter0.tdb' Apr 26 08:55:43 192.168.122.209 [60694.019008] [tempesta fw] modules are stopped Apr 26 08:55:43 192.168.122.209 [60694.173013] [tempesta fw] exiting... Apr 26 08:55:43 192.168.122.209 [60694.294763] [tdb] Shutdown Tempesta DB Apr 26 08:55:43 192.168.122.209 [60694.525287] End test: http_general.test_expect_100_continue.TestExpect100ContinueBehavior.test_request_pipeline_delay_3_requests Apr 26 08:55:43 192.168.122.209 [60694.534820] Start test: http_general.test_expect_100_continue.TestExpect100ContinueBehavior.test_request_pipeline_delay_no_wait Apr 26 08:55:45 192.168.122.209 [60695.646591] [tdb] Start Tempesta DB Apr 26 08:55:45 192.168.122.209 [60695.787060] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:55:46 192.168.122.209 [60697.033219] [tempesta fw] Configuration processing is completed. Apr 26 08:55:46 192.168.122.209 [60697.085197] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:55:46 192.168.122.209 [60697.500938] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:55:46 192.168.122.209 [60697.527426] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:55:46 192.168.122.209 [60697.553713] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:55:47 192.168.122.209 [60697.605118] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:55:47 192.168.122.209 [60697.653063] [tempesta fw] Tempesta FW is ready Apr 26 08:55:49 192.168.122.209 [60699.824513] [tempesta fw] 127.0.0.2 "default" "PUT /test HTTP/1.1" 200 0 "-" "-" "ja5t=0" "ja5h=22200340180" Apr 26 08:55:49 192.168.122.209 [60699.999281] [tempesta fw] 127.0.0.2 "default" "PUT /expect HTTP/1.1" 200 0 "-" "-" "ja5t=0" "ja5h=18d200340200" Apr 26 08:55:49 192.168.122.209 [60700.427628] [tdb] Close table 'client0.tdb' Apr 26 08:55:50 192.168.122.209 [60700.625687] [tdb] Close table 'sessions0.tdb' Apr 26 08:55:53 192.168.122.209 [60703.825734] [tdb] Close table 'cache0.tdb' Apr 26 08:55:53 192.168.122.209 [60704.093223] [tdb] Close table 'filter0.tdb' Apr 26 08:55:53 192.168.122.209 [60704.093647] [tempesta fw] modules are stopped Apr 26 08:55:53 192.168.122.209 [60704.363494] [tempesta fw] exiting... Apr 26 08:55:53 192.168.122.209 [60704.504411] [tdb] Shutdown Tempesta DB Apr 26 08:55:54 192.168.122.209 [60704.781383] End test: http_general.test_expect_100_continue.TestExpect100ContinueBehavior.test_request_pipeline_delay_no_wait Apr 26 08:55:54 192.168.122.209 [60704.792869] Start test: http_general.test_headers.BackendSetCoookie.test_request_success Apr 26 08:55:55 192.168.122.209 [60705.802739] [tdb] Start Tempesta DB Apr 26 08:55:55 192.168.122.209 [60705.953099] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:55:57 192.168.122.209 [60707.617304] [tempesta fw] Configuration processing is completed. Apr 26 08:55:57 192.168.122.209 [60707.670036] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:55:57 192.168.122.209 [60708.075926] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:55:57 192.168.122.209 [60708.102528] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:55:57 192.168.122.209 [60708.129903] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:55:57 192.168.122.209 [60708.225305] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:55:57 192.168.122.209 [60708.269190] [tempesta fw] Tempesta FW is ready Apr 26 08:55:58 192.168.122.209 [60709.353527] [tdb] Close table 'client0.tdb' Apr 26 08:55:58 192.168.122.209 [60709.546882] [tdb] Close table 'sessions0.tdb' Apr 26 08:56:02 192.168.122.209 [60712.758761] [tdb] Close table 'cache0.tdb' Apr 26 08:56:02 192.168.122.209 [60713.007316] [tdb] Close table 'filter0.tdb' Apr 26 08:56:02 192.168.122.209 [60713.007748] [tempesta fw] modules are stopped Apr 26 08:56:02 192.168.122.209 [60713.249845] [tempesta fw] exiting... Apr 26 08:56:02 192.168.122.209 [60713.379248] [tdb] Shutdown Tempesta DB Apr 26 08:56:03 192.168.122.209 [60713.590043] End test: http_general.test_headers.BackendSetCoookie.test_request_success Apr 26 08:56:03 192.168.122.209 [60713.603828] Start test: http_general.test_headers.RepeatedHeaderCache.test_request_cache_del_dup_success Apr 26 08:56:04 192.168.122.209 [60714.595931] [tdb] Start Tempesta DB Apr 26 08:56:04 192.168.122.209 [60714.730769] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:56:05 192.168.122.209 [60716.073409] [tempesta fw] Configuration processing is completed. Apr 26 08:56:05 192.168.122.209 [60716.124395] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:56:05 192.168.122.209 [60716.535723] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:56:05 192.168.122.209 [60716.561621] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:56:06 192.168.122.209 [60716.587666] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:56:06 192.168.122.209 [60716.629346] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:56:06 192.168.122.209 [60716.681296] [tempesta fw] Tempesta FW is ready Apr 26 08:56:06 192.168.122.209 [60717.248973] [tdb] Close table 'client0.tdb' Apr 26 08:56:06 192.168.122.209 [60717.445342] [tdb] Close table 'sessions0.tdb' Apr 26 08:56:10 192.168.122.209 [60720.655779] [tdb] Close table 'cache0.tdb' Apr 26 08:56:10 192.168.122.209 [60720.901751] [tdb] Close table 'filter0.tdb' Apr 26 08:56:10 192.168.122.209 [60720.902193] [tempesta fw] modules are stopped Apr 26 08:56:10 192.168.122.209 [60721.081227] [tempesta fw] exiting... Apr 26 08:56:10 192.168.122.209 [60721.224516] [tdb] Shutdown Tempesta DB Apr 26 08:56:10 192.168.122.209 [60721.428654] End test: http_general.test_headers.RepeatedHeaderCache.test_request_cache_del_dup_success Apr 26 08:56:10 192.168.122.209 [60721.449832] Start test: http_general.test_headers.TestContentTypeWithEmptyBodyDELETE.test_request_success Apr 26 08:56:11 192.168.122.209 [60722.513899] [tdb] Start Tempesta DB Apr 26 08:56:12 192.168.122.209 [60722.644462] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:56:13 192.168.122.209 [60724.014721] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [60724.014721] Maybe that's fine, but it's worth checking the [60724.014721] config - if there is no relations between the [60724.014721] names, then host name confusion attack is possible. Apr 26 08:56:13 192.168.122.209 [60724.149518] [tempesta fw] Configuration processing is completed. Apr 26 08:56:13 192.168.122.209 [60724.210773] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:56:14 192.168.122.209 [60724.622729] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:56:14 192.168.122.209 [60724.658154] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:56:14 192.168.122.209 [60724.683508] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:56:14 192.168.122.209 [60724.729458] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:56:14 192.168.122.209 [60724.777405] [tempesta fw] Tempesta FW is ready Apr 26 08:56:14 192.168.122.209 [60724.941349] [tempesta fw] 127.0.0.2 "default" "DELETE / HTTP/1.1" 200 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400080080" Apr 26 08:56:14 192.168.122.209 [60724.942455] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 08:56:14 192.168.122.209 [60725.327422] [tdb] Close table 'client0.tdb' Apr 26 08:56:14 192.168.122.209 [60725.536830] [tdb] Close table 'sessions0.tdb' Apr 26 08:56:18 192.168.122.209 [60728.717074] [tdb] Close table 'cache0.tdb' Apr 26 08:56:18 192.168.122.209 [60728.974760] [tdb] Close table 'filter0.tdb' Apr 26 08:56:18 192.168.122.209 [60728.975178] [tempesta fw] modules are stopped Apr 26 08:56:18 192.168.122.209 [60729.157713] [tempesta fw] exiting... Apr 26 08:56:18 192.168.122.209 [60729.297570] [tdb] Shutdown Tempesta DB Apr 26 08:56:18 192.168.122.209 [60729.501019] End test: http_general.test_headers.TestContentTypeWithEmptyBodyDELETE.test_request_success Apr 26 08:56:18 192.168.122.209 [60729.510343] Start test: http_general.test_headers.TestContentTypeWithEmptyBodyPATCH.test_request_success Apr 26 08:56:19 192.168.122.209 [60730.514021] [tdb] Start Tempesta DB Apr 26 08:56:20 192.168.122.209 [60730.641918] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:56:21 192.168.122.209 [60731.974864] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [60731.974864] Maybe that's fine, but it's worth checking the [60731.974864] config - if there is no relations between the [60731.974864] names, then host name confusion attack is possible. Apr 26 08:56:21 192.168.122.209 [60732.097610] [tempesta fw] Configuration processing is completed. Apr 26 08:56:21 192.168.122.209 [60732.148684] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:56:21 192.168.122.209 [60732.561563] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:56:22 192.168.122.209 [60732.587121] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:56:22 192.168.122.209 [60732.613700] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:56:22 192.168.122.209 [60732.681567] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:56:22 192.168.122.209 [60732.721498] [tempesta fw] Tempesta FW is ready Apr 26 08:56:22 192.168.122.209 [60732.859630] [tempesta fw] 127.0.0.2 "default" "PATCH / HTTP/1.1" 200 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400240080" Apr 26 08:56:22 192.168.122.209 [60732.861018] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 08:56:22 192.168.122.209 [60733.279762] [tdb] Close table 'client0.tdb' Apr 26 08:56:22 192.168.122.209 [60733.472002] [tdb] Close table 'sessions0.tdb' Apr 26 08:56:26 192.168.122.209 [60736.650456] [tdb] Close table 'cache0.tdb' Apr 26 08:56:26 192.168.122.209 [60736.875544] [tdb] Close table 'filter0.tdb' Apr 26 08:56:26 192.168.122.209 [60736.876014] [tempesta fw] modules are stopped Apr 26 08:56:26 192.168.122.209 [60737.091790] [tempesta fw] exiting... Apr 26 08:56:26 192.168.122.209 [60737.225681] [tdb] Shutdown Tempesta DB Apr 26 08:56:26 192.168.122.209 [60737.431976] End test: http_general.test_headers.TestContentTypeWithEmptyBodyPATCH.test_request_success Apr 26 08:56:26 192.168.122.209 [60737.454085] Start test: http_general.test_headers.TestContentTypeWithEmptyBodyPOST.test_request_success Apr 26 08:56:27 192.168.122.209 [60738.488777] [tdb] Start Tempesta DB Apr 26 08:56:28 192.168.122.209 [60738.616069] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:56:29 192.168.122.209 [60740.035046] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [60740.035046] Maybe that's fine, but it's worth checking the [60740.035046] config - if there is no relations between the [60740.035046] names, then host name confusion attack is possible. Apr 26 08:56:29 192.168.122.209 [60740.185669] [tempesta fw] Configuration processing is completed. Apr 26 08:56:29 192.168.122.209 [60740.236781] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:56:30 192.168.122.209 [60740.652961] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:56:30 192.168.122.209 [60740.679760] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:56:30 192.168.122.209 [60740.707316] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:56:30 192.168.122.209 [60740.745680] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:56:30 192.168.122.209 [60740.781606] [tempesta fw] Tempesta FW is ready Apr 26 08:56:30 192.168.122.209 [60740.931406] [tempesta fw] 127.0.0.2 "default" "POST / HTTP/1.1" 200 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400280080" Apr 26 08:56:30 192.168.122.209 [60740.932628] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 08:56:30 192.168.122.209 [60741.334613] [tdb] Close table 'client0.tdb' Apr 26 08:56:30 192.168.122.209 [60741.539056] [tdb] Close table 'sessions0.tdb' Apr 26 08:56:34 192.168.122.209 [60744.766011] [tdb] Close table 'cache0.tdb' Apr 26 08:56:34 192.168.122.209 [60745.006451] [tdb] Close table 'filter0.tdb' Apr 26 08:56:34 192.168.122.209 [60745.006893] [tempesta fw] modules are stopped Apr 26 08:56:34 192.168.122.209 [60745.225225] [tempesta fw] exiting... Apr 26 08:56:34 192.168.122.209 [60745.347538] [tdb] Shutdown Tempesta DB Apr 26 08:56:34 192.168.122.209 [60745.567335] End test: http_general.test_headers.TestContentTypeWithEmptyBodyPOST.test_request_success Apr 26 08:56:35 192.168.122.209 [60745.579534] Start test: http_general.test_headers.TestContentTypeWithEmptyBodyPUT.test_request_success Apr 26 08:56:35 192.168.122.209 [60746.564076] [tdb] Start Tempesta DB Apr 26 08:56:36 192.168.122.209 [60746.693904] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:56:37 192.168.122.209 [60748.135039] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [60748.135039] Maybe that's fine, but it's worth checking the [60748.135039] config - if there is no relations between the [60748.135039] names, then host name confusion attack is possible. Apr 26 08:56:37 192.168.122.209 [60748.269715] [tempesta fw] Configuration processing is completed. Apr 26 08:56:37 192.168.122.209 [60748.320712] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:56:38 192.168.122.209 [60748.731203] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:56:38 192.168.122.209 [60748.757181] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:56:38 192.168.122.209 [60748.784226] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:56:38 192.168.122.209 [60748.833755] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 08:56:38 192.168.122.209 [60748.881719] [tempesta fw] Tempesta FW is ready Apr 26 08:56:38 192.168.122.209 [60749.031066] [tempesta fw] 127.0.0.2 "default" "PUT / HTTP/1.1" 200 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400340080" Apr 26 08:56:38 192.168.122.209 [60749.032244] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 08:56:38 192.168.122.209 [60749.443627] [tdb] Close table 'client0.tdb' Apr 26 08:56:39 192.168.122.209 [60749.640846] [tdb] Close table 'sessions0.tdb' Apr 26 08:56:42 192.168.122.209 [60752.891657] [tdb] Close table 'cache0.tdb' Apr 26 08:56:42 192.168.122.209 [60753.155444] [tdb] Close table 'filter0.tdb' Apr 26 08:56:42 192.168.122.209 [60753.155887] [tempesta fw] modules are stopped Apr 26 08:56:42 192.168.122.209 [60753.342046] [tempesta fw] exiting... Apr 26 08:56:42 192.168.122.209 [60753.520460] [tdb] Shutdown Tempesta DB Apr 26 08:56:43 192.168.122.209 [60753.718008] End test: http_general.test_headers.TestContentTypeWithEmptyBodyPUT.test_request_success Apr 26 08:56:43 192.168.122.209 [60753.741776] Start test: http_general.test_headers.TestHeadersBlockedByMaxHeaderListSize.test_blocked_by_max_headers_count Apr 26 08:56:44 192.168.122.209 [60754.769484] [tdb] Start Tempesta DB Apr 26 08:56:44 192.168.122.209 [60754.907557] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:56:45 192.168.122.209 [60756.201888] [tempesta fw] Configuration processing is completed. Apr 26 08:56:45 192.168.122.209 [60756.252984] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:56:46 192.168.122.209 [60756.659881] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:56:46 192.168.122.209 [60756.687517] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:56:46 192.168.122.209 [60756.714982] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:56:46 192.168.122.209 [60756.770103] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:56:46 192.168.122.209 [60756.809831] [tempesta fw] Tempesta FW is ready Apr 26 08:56:46 192.168.122.209 [60756.949375] [tempesta fw] Warning: frang: HTTP header list size exceeded for 127.0.0.2: 24 (lim=23) Apr 26 08:56:46 192.168.122.209 [60757.381123] [tdb] Close table 'client0.tdb' Apr 26 08:56:47 192.168.122.209 [60757.571436] [tdb] Close table 'sessions0.tdb' Apr 26 08:56:50 192.168.122.209 [60760.798605] [tdb] Close table 'cache0.tdb' Apr 26 08:56:50 192.168.122.209 [60761.045437] [tdb] Close table 'filter0.tdb' Apr 26 08:56:50 192.168.122.209 [60761.045897] [tempesta fw] modules are stopped Apr 26 08:56:50 192.168.122.209 [60761.199858] [tempesta fw] exiting... Apr 26 08:56:50 192.168.122.209 [60761.344368] [tdb] Shutdown Tempesta DB Apr 26 08:56:51 192.168.122.209 [60761.571446] End test: http_general.test_headers.TestHeadersBlockedByMaxHeaderListSize.test_blocked_by_max_headers_count Apr 26 08:56:51 192.168.122.209 [60761.584712] Start test: http_general.test_headers.TestHeadersBlockedByMaxHeaderListSize.test_not_blocked_by_max_headers_count Apr 26 08:56:51 192.168.122.209 [60762.557302] [tdb] Start Tempesta DB Apr 26 08:56:52 192.168.122.209 [60762.698415] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:56:53 192.168.122.209 [60764.106008] [tempesta fw] Configuration processing is completed. Apr 26 08:56:53 192.168.122.209 [60764.157203] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:56:54 192.168.122.209 [60764.570211] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:56:54 192.168.122.209 [60764.596083] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:56:54 192.168.122.209 [60764.621742] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:56:54 192.168.122.209 [60764.702005] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:56:54 192.168.122.209 [60764.753924] [tempesta fw] Tempesta FW is ready Apr 26 08:56:54 192.168.122.209 [60765.305348] [tdb] Close table 'client0.tdb' Apr 26 08:56:54 192.168.122.209 [60765.498636] [tdb] Close table 'sessions0.tdb' Apr 26 08:56:58 192.168.122.209 [60768.742097] [tdb] Close table 'cache0.tdb' Apr 26 08:56:58 192.168.122.209 [60768.980778] [tdb] Close table 'filter0.tdb' Apr 26 08:56:58 192.168.122.209 [60768.981205] [tempesta fw] modules are stopped Apr 26 08:56:58 192.168.122.209 [60769.136104] [tempesta fw] exiting... Apr 26 08:56:58 192.168.122.209 [60769.244561] [tdb] Shutdown Tempesta DB Apr 26 08:56:58 192.168.122.209 [60769.454294] End test: http_general.test_headers.TestHeadersBlockedByMaxHeaderListSize.test_not_blocked_by_max_headers_count Apr 26 08:56:58 192.168.122.209 [60769.466937] Start test: http_general.test_headers.TestHeadersParsing.test_invalid_trailers_in_request Apr 26 08:56:59 192.168.122.209 [60770.501194] [tdb] Start Tempesta DB Apr 26 08:57:00 192.168.122.209 [60770.638069] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:57:01 192.168.122.209 [60772.058335] [tempesta fw] Configuration processing is completed. Apr 26 08:57:01 192.168.122.209 [60772.113115] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:57:01 192.168.122.209 [60772.140311] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 08:57:01 192.168.122.209 [60772.167432] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 08:57:01 192.168.122.209 [60772.210064] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:57:01 192.168.122.209 [60772.258018] [tempesta fw] Tempesta FW is ready Apr 26 08:57:01 192.168.122.209 [60772.428779] [tempesta fw] Warning: Parser error: state=Req_HdrCache_ControlV input(-0)=0x6e('n') data_len=1 off=0 Apr 26 08:57:02 192.168.122.209 [60772.846427] [tdb] Close table 'client0.tdb' Apr 26 08:57:02 192.168.122.209 [60773.033644] [tdb] Close table 'sessions0.tdb' Apr 26 08:57:02 192.168.122.209 [60773.252244] [tdb] Close table 'filter0.tdb' Apr 26 08:57:02 192.168.122.209 [60773.252679] [tempesta fw] modules are stopped Apr 26 08:57:02 192.168.122.209 [60773.439234] [tempesta fw] exiting... Apr 26 08:57:03 192.168.122.209 [60773.588723] [tdb] Shutdown Tempesta DB Apr 26 08:57:03 192.168.122.209 [60773.806892] End test: http_general.test_headers.TestHeadersParsing.test_invalid_trailers_in_request Apr 26 08:57:03 192.168.122.209 [60773.816307] Start test: http_general.test_headers.TestHeadersParsing.test_invalid_trailers_in_response_cache_control Apr 26 08:57:04 192.168.122.209 [60774.857078] [tdb] Start Tempesta DB Apr 26 08:57:04 192.168.122.209 [60774.995177] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:57:05 192.168.122.209 [60775.614159] [tempesta fw] Configuration processing is completed. Apr 26 08:57:05 192.168.122.209 [60775.665513] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:57:05 192.168.122.209 [60775.693120] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 08:57:05 192.168.122.209 [60775.720390] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 08:57:05 192.168.122.209 [60775.778142] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:57:05 192.168.122.209 [60775.822051] [tempesta fw] Tempesta FW is ready Apr 26 08:57:05 192.168.122.209 [60775.971179] [tempesta fw] Warning: Parser error: state=Resp_HdrCache_CtrlV input(-0)=0x6e('n') data_len=1 off=0 Apr 26 08:57:05 192.168.122.209 [60775.972212] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 08:57:05 192.168.122.209 [60776.405339] [tdb] Close table 'client0.tdb' Apr 26 08:57:06 192.168.122.209 [60776.606603] [tdb] Close table 'sessions0.tdb' Apr 26 08:57:06 192.168.122.209 [60776.855419] [tdb] Close table 'filter0.tdb' Apr 26 08:57:06 192.168.122.209 [60776.855858] [tempesta fw] modules are stopped Apr 26 08:57:06 192.168.122.209 [60777.039329] [tempesta fw] exiting... Apr 26 08:57:06 192.168.122.209 [60777.166554] [tdb] Shutdown Tempesta DB Apr 26 08:57:06 192.168.122.209 [60777.413041] End test: http_general.test_headers.TestHeadersParsing.test_invalid_trailers_in_response_cache_control Apr 26 08:57:06 192.168.122.209 [60777.422787] Start test: http_general.test_headers.TestHeadersParsing.test_invalid_trailers_in_response_date Apr 26 08:57:07 192.168.122.209 [60778.467102] [tdb] Start Tempesta DB Apr 26 08:57:08 192.168.122.209 [60778.591874] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:57:08 192.168.122.209 [60779.162201] [tempesta fw] Configuration processing is completed. Apr 26 08:57:08 192.168.122.209 [60779.220162] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:57:08 192.168.122.209 [60779.247666] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 08:57:08 192.168.122.209 [60779.274304] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 08:57:08 192.168.122.209 [60779.330098] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:57:08 192.168.122.209 [60779.370096] [tempesta fw] Tempesta FW is ready Apr 26 08:57:08 192.168.122.209 [60779.513785] [tempesta fw] Warning: Parser error: state=Resp_HdrDateV input(-0)=0x4d('M') data_len=1 off=0 Apr 26 08:57:08 192.168.122.209 [60779.514820] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 08:57:09 192.168.122.209 [60779.961731] [tdb] Close table 'client0.tdb' Apr 26 08:57:09 192.168.122.209 [60780.149069] [tdb] Close table 'sessions0.tdb' Apr 26 08:57:09 192.168.122.209 [60780.369991] [tdb] Close table 'filter0.tdb' Apr 26 08:57:09 192.168.122.209 [60780.370440] [tempesta fw] modules are stopped Apr 26 08:57:09 192.168.122.209 [60780.550162] [tempesta fw] exiting... Apr 26 08:57:10 192.168.122.209 [60780.681320] [tdb] Shutdown Tempesta DB Apr 26 08:57:10 192.168.122.209 [60780.877379] End test: http_general.test_headers.TestHeadersParsing.test_invalid_trailers_in_response_date Apr 26 08:57:10 192.168.122.209 [60780.898376] Start test: http_general.test_headers.TestHeadersParsing.test_invalid_trailers_in_response_expires Apr 26 08:57:11 192.168.122.209 [60781.962235] [tdb] Start Tempesta DB Apr 26 08:57:11 192.168.122.209 [60782.101162] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:57:12 192.168.122.209 [60782.682236] [tempesta fw] Configuration processing is completed. Apr 26 08:57:12 192.168.122.209 [60782.732828] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:57:12 192.168.122.209 [60782.759372] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 08:57:12 192.168.122.209 [60782.785626] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 08:57:12 192.168.122.209 [60782.870193] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:57:12 192.168.122.209 [60782.914186] [tempesta fw] Tempesta FW is ready Apr 26 08:57:12 192.168.122.209 [60783.078614] [tempesta fw] Warning: Parser error: state=Resp_HdrExpiresV input(-0)=0x54('T') data_len=1 off=0 Apr 26 08:57:12 192.168.122.209 [60783.079634] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 08:57:12 192.168.122.209 [60783.490565] [tdb] Close table 'client0.tdb' Apr 26 08:57:13 192.168.122.209 [60783.682408] [tdb] Close table 'sessions0.tdb' Apr 26 08:57:13 192.168.122.209 [60783.945543] [tdb] Close table 'filter0.tdb' Apr 26 08:57:13 192.168.122.209 [60783.946055] [tempesta fw] modules are stopped Apr 26 08:57:13 192.168.122.209 [60784.130141] [tempesta fw] exiting... Apr 26 08:57:13 192.168.122.209 [60784.258532] [tdb] Shutdown Tempesta DB Apr 26 08:57:13 192.168.122.209 [60784.455644] End test: http_general.test_headers.TestHeadersParsing.test_invalid_trailers_in_response_expires Apr 26 08:57:13 192.168.122.209 [60784.465493] Start test: http_general.test_headers.TestHeadersParsing.test_invalid_trailers_in_response_last_modified Apr 26 08:57:14 192.168.122.209 [60785.472355] [tdb] Start Tempesta DB Apr 26 08:57:15 192.168.122.209 [60785.614234] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:57:15 192.168.122.209 [60786.170281] [tempesta fw] Configuration processing is completed. Apr 26 08:57:15 192.168.122.209 [60786.225568] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:57:15 192.168.122.209 [60786.253830] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 08:57:15 192.168.122.209 [60786.281395] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 08:57:15 192.168.122.209 [60786.338264] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:57:15 192.168.122.209 [60786.386211] [tempesta fw] Tempesta FW is ready Apr 26 08:57:15 192.168.122.209 [60786.543852] [tempesta fw] Warning: Parser error: state=Resp_HdrLast_ModifiedV input(-0)=0x4d('M') data_len=1 off=0 Apr 26 08:57:15 192.168.122.209 [60786.544951] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 08:57:16 192.168.122.209 [60786.957623] [tdb] Close table 'client0.tdb' Apr 26 08:57:16 192.168.122.209 [60787.146799] [tdb] Close table 'sessions0.tdb' Apr 26 08:57:16 192.168.122.209 [60787.385501] [tdb] Close table 'filter0.tdb' Apr 26 08:57:16 192.168.122.209 [60787.385940] [tempesta fw] modules are stopped Apr 26 08:57:16 192.168.122.209 [60787.552740] [tempesta fw] exiting... Apr 26 08:57:17 192.168.122.209 [60787.642577] [tdb] Shutdown Tempesta DB Apr 26 08:57:17 192.168.122.209 [60787.878161] End test: http_general.test_headers.TestHeadersParsing.test_invalid_trailers_in_response_last_modified Apr 26 08:57:17 192.168.122.209 [60787.890580] Start test: http_general.test_headers.TestHeadersParsing.test_invalid_trailers_in_response_vary Apr 26 08:57:18 192.168.122.209 [60788.889462] [tdb] Start Tempesta DB Apr 26 08:57:18 192.168.122.209 [60789.029256] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:57:19 192.168.122.209 [60789.606427] [tempesta fw] Configuration processing is completed. Apr 26 08:57:19 192.168.122.209 [60789.658547] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:57:19 192.168.122.209 [60789.688132] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 08:57:19 192.168.122.209 [60789.714825] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 08:57:19 192.168.122.209 [60789.758287] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:57:19 192.168.122.209 [60789.798254] [tempesta fw] Tempesta FW is ready Apr 26 08:57:19 192.168.122.209 [60789.968732] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 08:57:19 192.168.122.209 [60790.394373] [tdb] Close table 'client0.tdb' Apr 26 08:57:19 192.168.122.209 [60790.568565] [tdb] Close table 'sessions0.tdb' Apr 26 08:57:20 192.168.122.209 [60790.814667] [tdb] Close table 'filter0.tdb' Apr 26 08:57:20 192.168.122.209 [60790.815109] [tempesta fw] modules are stopped Apr 26 08:57:20 192.168.122.209 [60791.009680] [tempesta fw] exiting... Apr 26 08:57:20 192.168.122.209 [60791.134241] [tdb] Shutdown Tempesta DB Apr 26 08:57:20 192.168.122.209 [60791.332965] End test: http_general.test_headers.TestHeadersParsing.test_invalid_trailers_in_response_vary Apr 26 08:57:20 192.168.122.209 [60791.345467] Start test: http_general.test_headers.TestHeadersParsing.test_long_header_name_in_request Apr 26 08:57:21 192.168.122.209 [60792.339384] [tdb] Start Tempesta DB Apr 26 08:57:21 192.168.122.209 [60792.488354] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:57:22 192.168.122.209 [60793.082384] [tempesta fw] Configuration processing is completed. Apr 26 08:57:22 192.168.122.209 [60793.134108] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:57:22 192.168.122.209 [60793.162015] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 08:57:22 192.168.122.209 [60793.189142] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 08:57:22 192.168.122.209 [60793.226268] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:57:22 192.168.122.209 [60793.266300] [tempesta fw] Tempesta FW is ready Apr 26 08:57:32 192.168.122.209 [60802.877695] [tempesta fw] Warning: Max header name length 1024 exceeded. Apr 26 08:57:32 192.168.122.209 [60803.319976] [tdb] Close table 'client0.tdb' Apr 26 08:57:32 192.168.122.209 [60803.514591] [tdb] Close table 'sessions0.tdb' Apr 26 08:57:33 192.168.122.209 [60803.759254] [tdb] Close table 'filter0.tdb' Apr 26 08:57:33 192.168.122.209 [60803.759693] [tempesta fw] modules are stopped Apr 26 08:57:33 192.168.122.209 [60803.998323] [tempesta fw] exiting... Apr 26 08:57:33 192.168.122.209 [60804.118799] [tdb] Shutdown Tempesta DB Apr 26 08:57:33 192.168.122.209 [60804.297087] End test: http_general.test_headers.TestHeadersParsing.test_long_header_name_in_request Apr 26 08:57:33 192.168.122.209 [60804.319265] Start test: http_general.test_headers.TestHeadersParsing.test_long_header_name_in_response Apr 26 08:57:34 192.168.122.209 [60805.317036] [tdb] Start Tempesta DB Apr 26 08:57:34 192.168.122.209 [60805.459253] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:57:35 192.168.122.209 [60806.050571] [tempesta fw] Configuration processing is completed. Apr 26 08:57:35 192.168.122.209 [60806.103863] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:57:35 192.168.122.209 [60806.130925] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 08:57:35 192.168.122.209 [60806.157310] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 08:57:35 192.168.122.209 [60806.206468] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:57:35 192.168.122.209 [60806.258482] [tempesta fw] Tempesta FW is ready Apr 26 08:57:45 192.168.122.209 [60815.883479] [tempesta fw] Warning: Max header name length 1024 exceeded. Apr 26 08:57:45 192.168.122.209 [60815.884403] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 08:57:45 192.168.122.209 [60816.291486] [tdb] Close table 'client0.tdb' Apr 26 08:57:45 192.168.122.209 [60816.477776] [tdb] Close table 'sessions0.tdb' Apr 26 08:57:46 192.168.122.209 [60816.712673] [tdb] Close table 'filter0.tdb' Apr 26 08:57:46 192.168.122.209 [60816.713104] [tempesta fw] modules are stopped Apr 26 08:57:46 192.168.122.209 [60816.912267] [tempesta fw] exiting... Apr 26 08:57:46 192.168.122.209 [60817.062036] [tdb] Shutdown Tempesta DB Apr 26 08:57:46 192.168.122.209 [60817.264823] End test: http_general.test_headers.TestHeadersParsing.test_long_header_name_in_response Apr 26 08:57:46 192.168.122.209 [60817.281353] Start test: http_general.test_headers.TestHeadersParsing.test_server_in_trailers_response_empty_body Apr 26 08:57:47 192.168.122.209 [60818.324958] [tdb] Start Tempesta DB Apr 26 08:57:47 192.168.122.209 [60818.465009] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:57:48 192.168.122.209 [60819.078701] [tempesta fw] Configuration processing is completed. Apr 26 08:57:48 192.168.122.209 [60819.129208] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:57:48 192.168.122.209 [60819.155932] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 08:57:48 192.168.122.209 [60819.182606] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 08:57:48 192.168.122.209 [60819.226607] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:57:48 192.168.122.209 [60819.266629] [tempesta fw] Tempesta FW is ready Apr 26 08:57:48 192.168.122.209 [60819.414382] [tempesta fw] Warning: There is a hop-by-hop header in trailers, drop response Apr 26 08:57:48 192.168.122.209 [60819.414388] [tempesta fw] Warning: Parser error: state=Resp_HdrServerV input(-0)=0xd(' ') data_len=1 off=0 Apr 26 08:57:48 192.168.122.209 [60819.416578] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 08:57:49 192.168.122.209 [60819.816145] [tdb] Close table 'client0.tdb' Apr 26 08:57:49 192.168.122.209 [60820.031225] [tdb] Close table 'sessions0.tdb' Apr 26 08:57:49 192.168.122.209 [60820.263469] [tdb] Close table 'filter0.tdb' Apr 26 08:57:49 192.168.122.209 [60820.263910] [tempesta fw] modules are stopped Apr 26 08:57:49 192.168.122.209 [60820.436942] [tempesta fw] exiting... Apr 26 08:57:50 192.168.122.209 [60820.578863] [tdb] Shutdown Tempesta DB Apr 26 08:57:50 192.168.122.209 [60820.827865] End test: http_general.test_headers.TestHeadersParsing.test_server_in_trailers_response_empty_body Apr 26 08:57:50 192.168.122.209 [60820.842679] Start test: http_general.test_headers.TestHeadersParsing.test_server_in_trailers_response_not_empty_body Apr 26 08:57:51 192.168.122.209 [60821.889185] [tdb] Start Tempesta DB Apr 26 08:57:51 192.168.122.209 [60822.019415] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:57:52 192.168.122.209 [60822.638726] [tempesta fw] Configuration processing is completed. Apr 26 08:57:52 192.168.122.209 [60822.693191] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:57:52 192.168.122.209 [60822.721242] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 08:57:52 192.168.122.209 [60822.747863] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 08:57:52 192.168.122.209 [60822.790656] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:57:52 192.168.122.209 [60822.834678] [tempesta fw] Tempesta FW is ready Apr 26 08:57:52 192.168.122.209 [60822.996991] [tempesta fw] Warning: There is a hop-by-hop header in trailers, drop response Apr 26 08:57:52 192.168.122.209 [60822.996996] [tempesta fw] Warning: Parser error: state=Resp_HdrServerV input(-0)=0xd(' ') data_len=1 off=0 Apr 26 08:57:52 192.168.122.209 [60822.998714] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 08:57:52 192.168.122.209 [60823.405306] [tdb] Close table 'client0.tdb' Apr 26 08:57:53 192.168.122.209 [60823.600294] [tdb] Close table 'sessions0.tdb' Apr 26 08:57:53 192.168.122.209 [60823.832121] [tdb] Close table 'filter0.tdb' Apr 26 08:57:53 192.168.122.209 [60823.832565] [tempesta fw] modules are stopped Apr 26 08:57:53 192.168.122.209 [60824.013831] [tempesta fw] exiting... Apr 26 08:57:53 192.168.122.209 [60824.140860] [tdb] Shutdown Tempesta DB Apr 26 08:57:53 192.168.122.209 [60824.336042] End test: http_general.test_headers.TestHeadersParsing.test_server_in_trailers_response_not_empty_body Apr 26 08:57:53 192.168.122.209 [60824.343998] Start test: http_general.test_headers.TestHeadersParsing.test_trailers_in_request_trailer_GET Apr 26 08:57:54 192.168.122.209 [60825.344456] [tdb] Start Tempesta DB Apr 26 08:57:54 192.168.122.209 [60825.494435] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:57:55 192.168.122.209 [60826.122809] [tempesta fw] Configuration processing is completed. Apr 26 08:57:55 192.168.122.209 [60826.176917] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:57:55 192.168.122.209 [60826.205872] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 08:57:55 192.168.122.209 [60826.232357] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 08:57:55 192.168.122.209 [60826.302756] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:57:55 192.168.122.209 [60826.342711] [tempesta fw] Tempesta FW is ready Apr 26 08:57:55 192.168.122.209 [60826.492376] [tempesta fw] Warning: Content-Length or Content-Type not allowed to be used with such (overridden) method Apr 26 08:57:55 192.168.122.209 [60826.493340] [tempesta fw] Warning: Parser error: state=RGen_BodyParse input(-0)=0xd(' ') data_len=1 off=0 Apr 26 08:57:56 192.168.122.209 [60826.907563] [tdb] Close table 'client0.tdb' Apr 26 08:57:56 192.168.122.209 [60827.088312] [tdb] Close table 'sessions0.tdb' Apr 26 08:57:56 192.168.122.209 [60827.316514] [tdb] Close table 'filter0.tdb' Apr 26 08:57:56 192.168.122.209 [60827.316945] [tempesta fw] modules are stopped Apr 26 08:57:56 192.168.122.209 [60827.500824] [tempesta fw] exiting... Apr 26 08:57:57 192.168.122.209 [60827.612245] [tdb] Shutdown Tempesta DB Apr 26 08:57:57 192.168.122.209 [60827.842867] End test: http_general.test_headers.TestHeadersParsing.test_trailers_in_request_trailer_GET Apr 26 08:57:57 192.168.122.209 [60827.850292] Start test: http_general.test_headers.TestHeadersParsing.test_trailers_in_request_trailer_HEAD Apr 26 08:57:58 192.168.122.209 [60828.886836] [tdb] Start Tempesta DB Apr 26 08:57:58 192.168.122.209 [60829.022217] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:57:59 192.168.122.209 [60829.610832] [tempesta fw] Configuration processing is completed. Apr 26 08:57:59 192.168.122.209 [60829.661315] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:57:59 192.168.122.209 [60829.688652] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 08:57:59 192.168.122.209 [60829.715796] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 08:57:59 192.168.122.209 [60829.750731] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:57:59 192.168.122.209 [60829.790753] [tempesta fw] Tempesta FW is ready Apr 26 08:57:59 192.168.122.209 [60829.945551] [tempesta fw] Warning: Content-Length or Content-Type not allowed to be used with such (overridden) method Apr 26 08:57:59 192.168.122.209 [60829.946520] [tempesta fw] Warning: Parser error: state=RGen_BodyParse input(-0)=0xd(' ') data_len=1 off=0 Apr 26 08:57:59 192.168.122.209 [60830.360602] [tdb] Close table 'client0.tdb' Apr 26 08:57:59 192.168.122.209 [60830.552888] [tdb] Close table 'sessions0.tdb' Apr 26 08:58:00 192.168.122.209 [60830.787393] [tdb] Close table 'filter0.tdb' Apr 26 08:58:00 192.168.122.209 [60830.787841] [tempesta fw] modules are stopped Apr 26 08:58:00 192.168.122.209 [60830.977945] [tempesta fw] exiting... Apr 26 08:58:00 192.168.122.209 [60831.118789] [tdb] Shutdown Tempesta DB Apr 26 08:58:00 192.168.122.209 [60831.348675] End test: http_general.test_headers.TestHeadersParsing.test_trailers_in_request_trailer_HEAD Apr 26 08:58:00 192.168.122.209 [60831.355197] Start test: http_general.test_headers.TestHeadersParsing.test_trailers_in_request_trailer_POST Apr 26 08:58:01 192.168.122.209 [60832.396477] [tdb] Start Tempesta DB Apr 26 08:58:01 192.168.122.209 [60832.537481] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:58:02 192.168.122.209 [60833.126872] [tempesta fw] Configuration processing is completed. Apr 26 08:58:02 192.168.122.209 [60833.179128] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:58:02 192.168.122.209 [60833.206484] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 08:58:02 192.168.122.209 [60833.233295] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 08:58:02 192.168.122.209 [60833.278806] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:58:02 192.168.122.209 [60833.346783] [tempesta fw] Tempesta FW is ready Apr 26 08:58:03 192.168.122.209 [60833.940273] [tdb] Close table 'client0.tdb' Apr 26 08:58:03 192.168.122.209 [60834.133642] [tdb] Close table 'sessions0.tdb' Apr 26 08:58:03 192.168.122.209 [60834.367821] [tdb] Close table 'filter0.tdb' Apr 26 08:58:03 192.168.122.209 [60834.368280] [tempesta fw] modules are stopped Apr 26 08:58:03 192.168.122.209 [60834.547628] [tempesta fw] exiting... Apr 26 08:58:04 192.168.122.209 [60834.669993] [tdb] Shutdown Tempesta DB Apr 26 08:58:04 192.168.122.209 [60834.885255] End test: http_general.test_headers.TestHeadersParsing.test_trailers_in_request_trailer_POST Apr 26 08:58:04 192.168.122.209 [60834.897349] Start test: http_general.test_headers.TestHeadersParsing.test_trailers_in_request_trailer_hbp_from_connection_POST Apr 26 08:58:05 192.168.122.209 [60835.929335] [tdb] Start Tempesta DB Apr 26 08:58:05 192.168.122.209 [60836.071046] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:58:06 192.168.122.209 [60836.723249] [tempesta fw] Configuration processing is completed. Apr 26 08:58:06 192.168.122.209 [60836.776737] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:58:06 192.168.122.209 [60836.805248] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 08:58:06 192.168.122.209 [60836.832182] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 08:58:06 192.168.122.209 [60836.878976] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:58:06 192.168.122.209 [60836.918833] [tempesta fw] Tempesta FW is ready Apr 26 08:58:06 192.168.122.209 [60837.075546] [tempesta fw] Warning: There is a hop-by-hop header in trailers, drop request Apr 26 08:58:06 192.168.122.209 [60837.075552] [tempesta fw] Warning: Parser error: state=st_curr input(-0)=0xd(' ') data_len=1 off=0 Apr 26 08:58:06 192.168.122.209 [60837.481113] [tdb] Close table 'client0.tdb' Apr 26 08:58:07 192.168.122.209 [60837.692562] [tdb] Close table 'sessions0.tdb' Apr 26 08:58:07 192.168.122.209 [60837.918593] [tdb] Close table 'filter0.tdb' Apr 26 08:58:07 192.168.122.209 [60837.919042] [tempesta fw] modules are stopped Apr 26 08:58:07 192.168.122.209 [60838.115776] [tempesta fw] exiting... Apr 26 08:58:07 192.168.122.209 [60838.252142] [tdb] Shutdown Tempesta DB Apr 26 08:58:07 192.168.122.209 [60838.446353] End test: http_general.test_headers.TestHeadersParsing.test_trailers_in_request_trailer_hbp_from_connection_POST Apr 26 08:58:07 192.168.122.209 [60838.465720] Start test: http_general.test_headers.TestHeadersParsing.test_trailers_in_request_trailer_mix_POST_keep_alive Apr 26 08:58:08 192.168.122.209 [60839.484576] [tdb] Start Tempesta DB Apr 26 08:58:09 192.168.122.209 [60839.634142] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:58:09 192.168.122.209 [60840.254968] [tempesta fw] Configuration processing is completed. Apr 26 08:58:09 192.168.122.209 [60840.308466] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:58:09 192.168.122.209 [60840.341012] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 08:58:09 192.168.122.209 [60840.368008] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 08:58:09 192.168.122.209 [60840.414934] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:58:09 192.168.122.209 [60840.462894] [tempesta fw] Tempesta FW is ready Apr 26 08:58:10 192.168.122.209 [60840.612734] [tempesta fw] Warning: There is a hop-by-hop header in trailers, drop request Apr 26 08:58:10 192.168.122.209 [60840.612738] [tempesta fw] Warning: Parser error: state=Req_HdrKeep_AliveV input(-0)=0xd(' ') data_len=1 off=0 Apr 26 08:58:10 192.168.122.209 [60841.010652] [tdb] Close table 'client0.tdb' Apr 26 08:58:10 192.168.122.209 [60841.206265] [tdb] Close table 'sessions0.tdb' Apr 26 08:58:10 192.168.122.209 [60841.414139] [tdb] Close table 'filter0.tdb' Apr 26 08:58:10 192.168.122.209 [60841.414572] [tempesta fw] modules are stopped Apr 26 08:58:11 192.168.122.209 [60841.611622] [tempesta fw] exiting... Apr 26 08:58:11 192.168.122.209 [60841.710009] [tdb] Shutdown Tempesta DB Apr 26 08:58:11 192.168.122.209 [60841.965069] End test: http_general.test_headers.TestHeadersParsing.test_trailers_in_request_trailer_mix_POST_keep_alive Apr 26 08:58:11 192.168.122.209 [60841.976060] Start test: http_general.test_headers.TestHeadersParsing.test_trailers_in_request_trailer_mix_POST_transfer_encoding Apr 26 08:58:12 192.168.122.209 [60843.008089] [tdb] Start Tempesta DB Apr 26 08:58:12 192.168.122.209 [60843.155355] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:58:13 192.168.122.209 [60843.750992] [tempesta fw] Configuration processing is completed. Apr 26 08:58:13 192.168.122.209 [60843.803595] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:58:13 192.168.122.209 [60843.832584] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 08:58:13 192.168.122.209 [60843.859373] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 08:58:13 192.168.122.209 [60843.914990] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:58:13 192.168.122.209 [60843.966922] [tempesta fw] Tempesta FW is ready Apr 26 08:58:13 192.168.122.209 [60844.149862] [tempesta fw] Warning: Parser error: state=Req_HdrTransfer_EncodingV input(-0)=0xd(' ') data_len=1 off=0 Apr 26 08:58:14 192.168.122.209 [60844.574670] [tdb] Close table 'client0.tdb' Apr 26 08:58:14 192.168.122.209 [60844.765518] [tdb] Close table 'sessions0.tdb' Apr 26 08:58:14 192.168.122.209 [60844.995970] [tdb] Close table 'filter0.tdb' Apr 26 08:58:14 192.168.122.209 [60844.996405] [tempesta fw] modules are stopped Apr 26 08:58:14 192.168.122.209 [60845.182510] [tempesta fw] exiting... Apr 26 08:58:14 192.168.122.209 [60845.285134] [tdb] Shutdown Tempesta DB Apr 26 08:58:14 192.168.122.209 [60845.489486] End test: http_general.test_headers.TestHeadersParsing.test_trailers_in_request_trailer_mix_POST_transfer_encoding Apr 26 08:58:14 192.168.122.209 [60845.505220] Start test: http_general.test_headers.TestHeadersParsing.test_trailers_in_request_trailer_mix_POST_upgrade Apr 26 08:58:16 192.168.122.209 [60846.581238] [tdb] Start Tempesta DB Apr 26 08:58:16 192.168.122.209 [60846.715794] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:58:16 192.168.122.209 [60847.343037] [tempesta fw] Configuration processing is completed. Apr 26 08:58:16 192.168.122.209 [60847.393795] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:58:16 192.168.122.209 [60847.420835] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 08:58:16 192.168.122.209 [60847.448944] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 08:58:16 192.168.122.209 [60847.515036] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:58:16 192.168.122.209 [60847.566974] [tempesta fw] Tempesta FW is ready Apr 26 08:58:17 192.168.122.209 [60847.727995] [tempesta fw] Warning: Parser error: state=Req_HdrUpgradeV input(-0)=0xd(' ') data_len=1 off=0 Apr 26 08:58:17 192.168.122.209 [60848.170002] [tdb] Close table 'client0.tdb' Apr 26 08:58:17 192.168.122.209 [60848.368926] [tdb] Close table 'sessions0.tdb' Apr 26 08:58:18 192.168.122.209 [60848.610150] [tdb] Close table 'filter0.tdb' Apr 26 08:58:18 192.168.122.209 [60848.610587] [tempesta fw] modules are stopped Apr 26 08:58:18 192.168.122.209 [60848.788489] [tempesta fw] exiting... Apr 26 08:58:18 192.168.122.209 [60848.920224] [tdb] Shutdown Tempesta DB Apr 26 08:58:18 192.168.122.209 [60849.132574] End test: http_general.test_headers.TestHeadersParsing.test_trailers_in_request_trailer_mix_POST_upgrade Apr 26 08:58:18 192.168.122.209 [60849.146038] Start test: http_general.test_headers.TestHeadersParsing.test_trailers_in_response_get_hbp_GET Apr 26 08:58:19 192.168.122.209 [60850.193994] [tdb] Start Tempesta DB Apr 26 08:58:19 192.168.122.209 [60850.321019] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:58:20 192.168.122.209 [60850.931101] [tempesta fw] Configuration processing is completed. Apr 26 08:58:20 192.168.122.209 [60850.982950] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:58:20 192.168.122.209 [60851.010481] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 08:58:20 192.168.122.209 [60851.037055] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 08:58:20 192.168.122.209 [60851.079004] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:58:20 192.168.122.209 [60851.126937] [tempesta fw] Tempesta FW is ready Apr 26 08:58:20 192.168.122.209 [60851.314472] [tempesta fw] Warning: Parser error: state=Resp_HdrConnectionV input(-0)=0xd(' ') data_len=1 off=0 Apr 26 08:58:20 192.168.122.209 [60851.315750] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 08:58:21 192.168.122.209 [60851.769685] [tdb] Close table 'client0.tdb' Apr 26 08:58:21 192.168.122.209 [60851.959542] [tdb] Close table 'sessions0.tdb' Apr 26 08:58:21 192.168.122.209 [60852.211172] [tdb] Close table 'filter0.tdb' Apr 26 08:58:21 192.168.122.209 [60852.211618] [tempesta fw] modules are stopped Apr 26 08:58:21 192.168.122.209 [60852.391378] [tempesta fw] exiting... Apr 26 08:58:21 192.168.122.209 [60852.524891] [tdb] Shutdown Tempesta DB Apr 26 08:58:22 192.168.122.209 [60852.726271] End test: http_general.test_headers.TestHeadersParsing.test_trailers_in_response_get_hbp_GET Apr 26 08:58:22 192.168.122.209 [60852.749030] Start test: http_general.test_headers.TestHeadersParsing.test_trailers_in_response_get_hbp_from_connection_GET Apr 26 08:58:23 192.168.122.209 [60853.790437] [tdb] Start Tempesta DB Apr 26 08:58:23 192.168.122.209 [60853.916063] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:58:23 192.168.122.209 [60854.495169] [tempesta fw] Configuration processing is completed. Apr 26 08:58:23 192.168.122.209 [60854.547383] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:58:24 192.168.122.209 [60854.574595] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 08:58:24 192.168.122.209 [60854.601536] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 08:58:24 192.168.122.209 [60854.639090] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:58:24 192.168.122.209 [60854.695061] [tempesta fw] Tempesta FW is ready Apr 26 08:58:24 192.168.122.209 [60854.867370] [tempesta fw] Warning: There is a hop-by-hop header in trailers, drop response Apr 26 08:58:24 192.168.122.209 [60854.867375] [tempesta fw] Warning: Parser error: state=st_curr input(-0)=0xd(' ') data_len=1 off=0 Apr 26 08:58:24 192.168.122.209 [60854.869256] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 08:58:24 192.168.122.209 [60855.277198] [tdb] Close table 'client0.tdb' Apr 26 08:58:24 192.168.122.209 [60855.473771] [tdb] Close table 'sessions0.tdb' Apr 26 08:58:25 192.168.122.209 [60855.718384] [tdb] Close table 'filter0.tdb' Apr 26 08:58:25 192.168.122.209 [60855.718814] [tempesta fw] modules are stopped Apr 26 08:58:25 192.168.122.209 [60855.945427] [tempesta fw] exiting... Apr 26 08:58:25 192.168.122.209 [60856.048476] [tdb] Shutdown Tempesta DB Apr 26 08:58:25 192.168.122.209 [60856.264638] End test: http_general.test_headers.TestHeadersParsing.test_trailers_in_response_get_hbp_from_connection_GET Apr 26 08:58:25 192.168.122.209 [60856.280837] Start test: http_general.test_headers.TestHeadersParsing.test_trailers_in_response_get_mix_GET_keep_alive Apr 26 08:58:26 192.168.122.209 [60857.334563] [tdb] Start Tempesta DB Apr 26 08:58:26 192.168.122.209 [60857.472486] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:58:27 192.168.122.209 [60858.023196] [tempesta fw] Configuration processing is completed. Apr 26 08:58:27 192.168.122.209 [60858.074195] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:58:27 192.168.122.209 [60858.102388] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 08:58:27 192.168.122.209 [60858.130118] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 08:58:27 192.168.122.209 [60858.207095] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:58:27 192.168.122.209 [60858.251108] [tempesta fw] Tempesta FW is ready Apr 26 08:58:27 192.168.122.209 [60858.441348] [tempesta fw] Warning: Parser error: state=Resp_HdrConnectionV input(-0)=0xd(' ') data_len=1 off=0 Apr 26 08:58:27 192.168.122.209 [60858.442489] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 08:58:28 192.168.122.209 [60858.880637] [tdb] Close table 'client0.tdb' Apr 26 08:58:28 192.168.122.209 [60859.058003] [tdb] Close table 'sessions0.tdb' Apr 26 08:58:28 192.168.122.209 [60859.287143] [tdb] Close table 'filter0.tdb' Apr 26 08:58:28 192.168.122.209 [60859.287578] [tempesta fw] modules are stopped Apr 26 08:58:28 192.168.122.209 [60859.443852] [tempesta fw] exiting... Apr 26 08:58:29 192.168.122.209 [60859.600965] [tdb] Shutdown Tempesta DB Apr 26 08:58:29 192.168.122.209 [60859.823245] End test: http_general.test_headers.TestHeadersParsing.test_trailers_in_response_get_mix_GET_keep_alive Apr 26 08:58:29 192.168.122.209 [60859.832690] Start test: http_general.test_headers.TestHeadersParsing.test_trailers_in_response_get_mix_GET_proxy_connection Apr 26 08:58:30 192.168.122.209 [60860.846643] [tdb] Start Tempesta DB Apr 26 08:58:30 192.168.122.209 [60860.990031] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:58:31 192.168.122.209 [60861.599231] [tempesta fw] Configuration processing is completed. Apr 26 08:58:31 192.168.122.209 [60861.647134] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:58:31 192.168.122.209 [60861.676889] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 08:58:31 192.168.122.209 [60861.704777] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 08:58:31 192.168.122.209 [60861.739141] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:58:31 192.168.122.209 [60861.779164] [tempesta fw] Tempesta FW is ready Apr 26 08:58:31 192.168.122.209 [60861.959862] [tempesta fw] Warning: There is a hop-by-hop header in trailers, drop response Apr 26 08:58:31 192.168.122.209 [60861.959867] [tempesta fw] Warning: Parser error: state=st_curr input(-0)=0xd(' ') data_len=1 off=0 Apr 26 08:58:31 192.168.122.209 [60861.961616] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 08:58:31 192.168.122.209 [60862.412390] [tdb] Close table 'client0.tdb' Apr 26 08:58:32 192.168.122.209 [60862.605900] [tdb] Close table 'sessions0.tdb' Apr 26 08:58:32 192.168.122.209 [60862.836341] [tdb] Close table 'filter0.tdb' Apr 26 08:58:32 192.168.122.209 [60862.836781] [tempesta fw] modules are stopped Apr 26 08:58:32 192.168.122.209 [60863.030695] [tempesta fw] exiting... Apr 26 08:58:32 192.168.122.209 [60863.146145] [tdb] Shutdown Tempesta DB Apr 26 08:58:32 192.168.122.209 [60863.354682] End test: http_general.test_headers.TestHeadersParsing.test_trailers_in_response_get_mix_GET_proxy_connection Apr 26 08:58:32 192.168.122.209 [60863.372281] Start test: http_general.test_headers.TestHeadersParsing.test_trailers_in_response_get_mix_GET_transfer_encoding Apr 26 08:58:33 192.168.122.209 [60864.457256] [tdb] Start Tempesta DB Apr 26 08:58:34 192.168.122.209 [60864.579263] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:58:34 192.168.122.209 [60865.215281] [tempesta fw] Configuration processing is completed. Apr 26 08:58:34 192.168.122.209 [60865.270590] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:58:34 192.168.122.209 [60865.297531] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 08:58:34 192.168.122.209 [60865.324503] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 08:58:34 192.168.122.209 [60865.371245] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:58:34 192.168.122.209 [60865.411197] [tempesta fw] Tempesta FW is ready Apr 26 08:58:35 192.168.122.209 [60865.604869] [tempesta fw] Warning: Parser error: state=Resp_HdrTransfer_EncodingV input(-0)=0xd(' ') data_len=1 off=0 Apr 26 08:58:35 192.168.122.209 [60865.606091] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 08:58:35 192.168.122.209 [60866.010008] [tdb] Close table 'client0.tdb' Apr 26 08:58:35 192.168.122.209 [60866.204441] [tdb] Close table 'sessions0.tdb' Apr 26 08:58:35 192.168.122.209 [60866.429466] [tdb] Close table 'filter0.tdb' Apr 26 08:58:35 192.168.122.209 [60866.429891] [tempesta fw] modules are stopped Apr 26 08:58:36 192.168.122.209 [60866.613934] [tempesta fw] exiting... Apr 26 08:58:36 192.168.122.209 [60866.743890] [tdb] Shutdown Tempesta DB Apr 26 08:58:36 192.168.122.209 [60866.940041] End test: http_general.test_headers.TestHeadersParsing.test_trailers_in_response_get_mix_GET_transfer_encoding Apr 26 08:58:36 192.168.122.209 [60866.946182] Start test: http_general.test_headers.TestHeadersParsing.test_trailers_in_response_get_mix_GET_upgrade Apr 26 08:58:37 192.168.122.209 [60867.947694] [tdb] Start Tempesta DB Apr 26 08:58:37 192.168.122.209 [60868.077391] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:58:38 192.168.122.209 [60868.667323] [tempesta fw] Configuration processing is completed. Apr 26 08:58:38 192.168.122.209 [60868.719922] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:58:38 192.168.122.209 [60868.746943] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 08:58:38 192.168.122.209 [60868.773323] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 08:58:38 192.168.122.209 [60868.823302] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:58:38 192.168.122.209 [60868.867284] [tempesta fw] Tempesta FW is ready Apr 26 08:58:38 192.168.122.209 [60869.057809] [tempesta fw] Warning: Parser error: state=Resp_HdrUpgradeV input(-0)=0xd(' ') data_len=1 off=0 Apr 26 08:58:38 192.168.122.209 [60869.058936] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 08:58:38 192.168.122.209 [60869.487929] [tdb] Close table 'client0.tdb' Apr 26 08:58:39 192.168.122.209 [60869.680564] [tdb] Close table 'sessions0.tdb' Apr 26 08:58:39 192.168.122.209 [60869.918618] [tdb] Close table 'filter0.tdb' Apr 26 08:58:39 192.168.122.209 [60869.919041] [tempesta fw] modules are stopped Apr 26 08:58:39 192.168.122.209 [60870.109408] [tempesta fw] exiting... Apr 26 08:58:39 192.168.122.209 [60870.232853] [tdb] Shutdown Tempesta DB Apr 26 08:58:39 192.168.122.209 [60870.473424] End test: http_general.test_headers.TestHeadersParsing.test_trailers_in_response_get_mix_GET_upgrade Apr 26 08:58:39 192.168.122.209 [60870.482791] Start test: http_general.test_headers.TestHeadersParsing.test_trailers_in_response_get_no_hbp_GET Apr 26 08:58:40 192.168.122.209 [60871.551346] [tdb] Start Tempesta DB Apr 26 08:58:41 192.168.122.209 [60871.691352] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:58:41 192.168.122.209 [60872.299372] [tempesta fw] Configuration processing is completed. Apr 26 08:58:41 192.168.122.209 [60872.349268] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:58:41 192.168.122.209 [60872.376107] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 08:58:41 192.168.122.209 [60872.402706] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 08:58:41 192.168.122.209 [60872.451383] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:58:41 192.168.122.209 [60872.495232] [tempesta fw] Tempesta FW is ready Apr 26 08:58:42 192.168.122.209 [60873.095832] [tdb] Close table 'client0.tdb' Apr 26 08:58:42 192.168.122.209 [60873.287769] [tdb] Close table 'sessions0.tdb' Apr 26 08:58:42 192.168.122.209 [60873.517825] [tdb] Close table 'filter0.tdb' Apr 26 08:58:42 192.168.122.209 [60873.518287] [tempesta fw] modules are stopped Apr 26 08:58:43 192.168.122.209 [60873.691897] [tempesta fw] exiting... Apr 26 08:58:43 192.168.122.209 [60873.814917] [tdb] Shutdown Tempesta DB Apr 26 08:58:43 192.168.122.209 [60874.059850] End test: http_general.test_headers.TestHeadersParsing.test_trailers_in_response_get_no_hbp_GET Apr 26 08:58:43 192.168.122.209 [60874.078904] Start test: http_general.test_headers.TestHeadersParsing.test_trailers_in_response_head_hbp_HEAD Apr 26 08:58:44 192.168.122.209 [60875.121027] [tdb] Start Tempesta DB Apr 26 08:58:44 192.168.122.209 [60875.262098] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:58:45 192.168.122.209 [60875.827668] [tempesta fw] Configuration processing is completed. Apr 26 08:58:45 192.168.122.209 [60875.878571] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:58:45 192.168.122.209 [60875.907010] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 08:58:45 192.168.122.209 [60875.934143] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 08:58:45 192.168.122.209 [60875.979290] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:58:45 192.168.122.209 [60876.023348] [tempesta fw] Tempesta FW is ready Apr 26 08:58:46 192.168.122.209 [60876.617666] [tdb] Close table 'client0.tdb' Apr 26 08:58:46 192.168.122.209 [60876.809167] [tdb] Close table 'sessions0.tdb' Apr 26 08:58:46 192.168.122.209 [60877.045453] [tdb] Close table 'filter0.tdb' Apr 26 08:58:46 192.168.122.209 [60877.045891] [tempesta fw] modules are stopped Apr 26 08:58:46 192.168.122.209 [60877.213495] [tempesta fw] exiting... Apr 26 08:58:46 192.168.122.209 [60877.316541] [tdb] Shutdown Tempesta DB Apr 26 08:58:46 192.168.122.209 [60877.541549] End test: http_general.test_headers.TestHeadersParsing.test_trailers_in_response_head_hbp_HEAD Apr 26 08:58:46 192.168.122.209 [60877.558566] Start test: http_general.test_headers.TestHeadersParsing.test_trailers_in_response_head_hbp_from_connection_HEAD Apr 26 08:58:48 192.168.122.209 [60878.628730] [tdb] Start Tempesta DB Apr 26 08:58:48 192.168.122.209 [60878.758826] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:58:48 192.168.122.209 [60879.347723] [tempesta fw] Configuration processing is completed. Apr 26 08:58:48 192.168.122.209 [60879.399531] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:58:48 192.168.122.209 [60879.428608] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 08:58:48 192.168.122.209 [60879.455076] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 08:58:48 192.168.122.209 [60879.511446] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:58:48 192.168.122.209 [60879.551393] [tempesta fw] Tempesta FW is ready Apr 26 08:58:49 192.168.122.209 [60880.150873] [tdb] Close table 'client0.tdb' Apr 26 08:58:49 192.168.122.209 [60880.345186] [tdb] Close table 'sessions0.tdb' Apr 26 08:58:50 192.168.122.209 [60880.581350] [tdb] Close table 'filter0.tdb' Apr 26 08:58:50 192.168.122.209 [60880.581786] [tempesta fw] modules are stopped Apr 26 08:58:50 192.168.122.209 [60880.762014] [tempesta fw] exiting... Apr 26 08:58:50 192.168.122.209 [60880.888954] [tdb] Shutdown Tempesta DB Apr 26 08:58:50 192.168.122.209 [60881.086025] End test: http_general.test_headers.TestHeadersParsing.test_trailers_in_response_head_hbp_from_connection_HEAD Apr 26 08:58:50 192.168.122.209 [60881.103423] Start test: http_general.test_headers.TestHeadersParsing.test_trailers_in_response_head_mix_HEAD Apr 26 08:58:51 192.168.122.209 [60882.148820] [tdb] Start Tempesta DB Apr 26 08:58:51 192.168.122.209 [60882.290868] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:58:52 192.168.122.209 [60882.923495] [tempesta fw] Configuration processing is completed. Apr 26 08:58:52 192.168.122.209 [60882.978577] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:58:52 192.168.122.209 [60883.005536] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 08:58:52 192.168.122.209 [60883.032406] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 08:58:52 192.168.122.209 [60883.103434] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:58:52 192.168.122.209 [60883.151438] [tempesta fw] Tempesta FW is ready Apr 26 08:58:53 192.168.122.209 [60883.742263] [tdb] Close table 'client0.tdb' Apr 26 08:58:53 192.168.122.209 [60883.936814] [tdb] Close table 'sessions0.tdb' Apr 26 08:58:53 192.168.122.209 [60884.188766] [tdb] Close table 'filter0.tdb' Apr 26 08:58:53 192.168.122.209 [60884.189199] [tempesta fw] modules are stopped Apr 26 08:58:53 192.168.122.209 [60884.355315] [tempesta fw] exiting... Apr 26 08:58:53 192.168.122.209 [60884.523412] [tdb] Shutdown Tempesta DB Apr 26 08:58:54 192.168.122.209 [60884.741570] End test: http_general.test_headers.TestHeadersParsing.test_trailers_in_response_head_mix_HEAD Apr 26 08:58:54 192.168.122.209 [60884.756788] Start test: http_general.test_headers.TestHeadersParsing.test_trailers_in_response_head_no_hbp_HEAD Apr 26 08:58:55 192.168.122.209 [60885.676744] [tdb] Start Tempesta DB Apr 26 08:58:55 192.168.122.209 [60885.804785] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:58:55 192.168.122.209 [60886.375580] [tempesta fw] Configuration processing is completed. Apr 26 08:58:55 192.168.122.209 [60886.440006] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:58:55 192.168.122.209 [60886.468892] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 08:58:55 192.168.122.209 [60886.495783] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 08:58:55 192.168.122.209 [60886.543520] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:58:56 192.168.122.209 [60886.587467] [tempesta fw] Tempesta FW is ready Apr 26 08:58:56 192.168.122.209 [60887.130076] [tdb] Close table 'client0.tdb' Apr 26 08:58:56 192.168.122.209 [60887.332355] [tdb] Close table 'sessions0.tdb' Apr 26 08:58:56 192.168.122.209 [60887.552310] [tdb] Close table 'filter0.tdb' Apr 26 08:58:56 192.168.122.209 [60887.552748] [tempesta fw] modules are stopped Apr 26 08:58:57 192.168.122.209 [60887.762741] [tempesta fw] exiting... Apr 26 08:58:57 192.168.122.209 [60887.897004] [tdb] Shutdown Tempesta DB Apr 26 08:58:57 192.168.122.209 [60888.091730] End test: http_general.test_headers.TestHeadersParsing.test_trailers_in_response_head_no_hbp_HEAD Apr 26 08:58:57 192.168.122.209 [60888.097317] Start test: http_general.test_headers.TestHeadersParsing.test_trailers_in_response_simple_empty_body Apr 26 08:58:58 192.168.122.209 [60889.023263] [tdb] Start Tempesta DB Apr 26 08:58:58 192.168.122.209 [60889.152070] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:58:59 192.168.122.209 [60889.687680] [tempesta fw] Configuration processing is completed. Apr 26 08:58:59 192.168.122.209 [60889.751700] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:58:59 192.168.122.209 [60889.778323] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 08:58:59 192.168.122.209 [60889.804601] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 08:58:59 192.168.122.209 [60889.851523] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:58:59 192.168.122.209 [60889.899529] [tempesta fw] Tempesta FW is ready Apr 26 08:58:59 192.168.122.209 [60890.424589] [tdb] Close table 'client0.tdb' Apr 26 08:59:00 192.168.122.209 [60890.640590] [tdb] Close table 'sessions0.tdb' Apr 26 08:59:00 192.168.122.209 [60890.889572] [tdb] Close table 'filter0.tdb' Apr 26 08:59:00 192.168.122.209 [60890.890000] [tempesta fw] modules are stopped Apr 26 08:59:00 192.168.122.209 [60891.050880] [tempesta fw] exiting... Apr 26 08:59:00 192.168.122.209 [60891.179891] [tdb] Shutdown Tempesta DB Apr 26 08:59:00 192.168.122.209 [60891.404828] End test: http_general.test_headers.TestHeadersParsing.test_trailers_in_response_simple_empty_body Apr 26 08:59:00 192.168.122.209 [60891.418257] Start test: http_general.test_headers.TestHeadersParsing.test_trailers_in_response_simple_not_empty_body Apr 26 08:59:01 192.168.122.209 [60892.475480] [tdb] Start Tempesta DB Apr 26 08:59:02 192.168.122.209 [60892.614434] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:59:02 192.168.122.209 [60893.203648] [tempesta fw] Configuration processing is completed. Apr 26 08:59:02 192.168.122.209 [60893.272988] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:59:02 192.168.122.209 [60893.303181] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 08:59:02 192.168.122.209 [60893.332090] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 08:59:02 192.168.122.209 [60893.383599] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:59:02 192.168.122.209 [60893.431571] [tempesta fw] Tempesta FW is ready Apr 26 08:59:03 192.168.122.209 [60893.989653] [tdb] Close table 'client0.tdb' Apr 26 08:59:03 192.168.122.209 [60894.185089] [tdb] Close table 'sessions0.tdb' Apr 26 08:59:03 192.168.122.209 [60894.401547] [tdb] Close table 'filter0.tdb' Apr 26 08:59:03 192.168.122.209 [60894.401990] [tempesta fw] modules are stopped Apr 26 08:59:04 192.168.122.209 [60894.641250] [tempesta fw] exiting... Apr 26 08:59:04 192.168.122.209 [60894.764537] [tdb] Shutdown Tempesta DB Apr 26 08:59:04 192.168.122.209 [60894.982019] End test: http_general.test_headers.TestHeadersParsing.test_trailers_in_response_simple_not_empty_body Apr 26 08:59:04 192.168.122.209 [60894.996536] Start test: http_general.test_headers.TestHeadersParsing.test_without_trailers_in_request Apr 26 08:59:05 192.168.122.209 [60896.013584] [tdb] Start Tempesta DB Apr 26 08:59:05 192.168.122.209 [60896.145801] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:59:06 192.168.122.209 [60896.723684] [tempesta fw] Configuration processing is completed. Apr 26 08:59:06 192.168.122.209 [60896.780640] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:59:06 192.168.122.209 [60896.811268] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 08:59:06 192.168.122.209 [60896.839672] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 08:59:06 192.168.122.209 [60896.891643] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:59:06 192.168.122.209 [60896.943622] [tempesta fw] Tempesta FW is ready Apr 26 08:59:06 192.168.122.209 [60897.519380] [tdb] Close table 'client0.tdb' Apr 26 08:59:07 192.168.122.209 [60897.713547] [tdb] Close table 'sessions0.tdb' Apr 26 08:59:07 192.168.122.209 [60897.955231] [tdb] Close table 'filter0.tdb' Apr 26 08:59:07 192.168.122.209 [60897.955712] [tempesta fw] modules are stopped Apr 26 08:59:07 192.168.122.209 [60898.214759] [tempesta fw] exiting... Apr 26 08:59:07 192.168.122.209 [60898.326513] [tdb] Shutdown Tempesta DB Apr 26 08:59:07 192.168.122.209 [60898.543309] End test: http_general.test_headers.TestHeadersParsing.test_without_trailers_in_request Apr 26 08:59:07 192.168.122.209 [60898.558835] Start test: http_general.test_headers.TestHost.test_forward_absolute_uri_default_path Apr 26 08:59:09 192.168.122.209 [60899.595131] [tdb] Start Tempesta DB Apr 26 08:59:09 192.168.122.209 [60899.737463] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:59:09 192.168.122.209 [60900.339772] [tempesta fw] Configuration processing is completed. Apr 26 08:59:09 192.168.122.209 [60900.390904] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:59:10 192.168.122.209 [60900.867883] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:59:10 192.168.122.209 [60900.898441] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:59:10 192.168.122.209 [60900.928604] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:59:10 192.168.122.209 [60901.015724] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:59:10 192.168.122.209 [60901.051668] [tempesta fw] Tempesta FW is ready Apr 26 08:59:11 192.168.122.209 [60901.686217] [tdb] Close table 'client0.tdb' Apr 26 08:59:11 192.168.122.209 [60901.874875] [tdb] Close table 'sessions0.tdb' Apr 26 08:59:14 192.168.122.209 [60905.151286] [tdb] Close table 'cache0.tdb' Apr 26 08:59:14 192.168.122.209 [60905.421168] [tdb] Close table 'filter0.tdb' Apr 26 08:59:14 192.168.122.209 [60905.421568] [tempesta fw] modules are stopped Apr 26 08:59:14 192.168.122.209 [60905.571420] [tempesta fw] exiting... Apr 26 08:59:15 192.168.122.209 [60905.688246] [tdb] Shutdown Tempesta DB Apr 26 08:59:15 192.168.122.209 [60905.939382] End test: http_general.test_headers.TestHost.test_forward_absolute_uri_default_path Apr 26 08:59:15 192.168.122.209 [60905.952939] Start test: http_general.test_headers.TestHost.test_forward_absolute_uri_empty_path Apr 26 08:59:16 192.168.122.209 [60907.070338] [tdb] Start Tempesta DB Apr 26 08:59:16 192.168.122.209 [60907.207886] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:59:17 192.168.122.209 [60908.535848] [tempesta fw] Configuration processing is completed. Apr 26 08:59:18 192.168.122.209 [60908.593428] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:59:18 192.168.122.209 [60909.022034] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:59:18 192.168.122.209 [60909.049016] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:59:18 192.168.122.209 [60909.077224] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:59:18 192.168.122.209 [60909.127860] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:59:18 192.168.122.209 [60909.171758] [tempesta fw] Tempesta FW is ready Apr 26 08:59:19 192.168.122.209 [60909.770373] [tdb] Close table 'client0.tdb' Apr 26 08:59:19 192.168.122.209 [60909.962069] [tdb] Close table 'sessions0.tdb' Apr 26 08:59:22 192.168.122.209 [60913.239212] [tdb] Close table 'cache0.tdb' Apr 26 08:59:22 192.168.122.209 [60913.481061] [tdb] Close table 'filter0.tdb' Apr 26 08:59:22 192.168.122.209 [60913.481535] [tempesta fw] modules are stopped Apr 26 08:59:23 192.168.122.209 [60913.639574] [tempesta fw] exiting... Apr 26 08:59:23 192.168.122.209 [60913.778247] [tdb] Shutdown Tempesta DB Apr 26 08:59:23 192.168.122.209 [60913.978144] End test: http_general.test_headers.TestHost.test_forward_absolute_uri_empty_path Apr 26 08:59:23 192.168.122.209 [60914.003726] Start test: http_general.test_headers.TestHost.test_forward_absolute_uri_full_path Apr 26 08:59:24 192.168.122.209 [60915.068094] [tdb] Start Tempesta DB Apr 26 08:59:24 192.168.122.209 [60915.224821] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:59:26 192.168.122.209 [60916.584008] [tempesta fw] Configuration processing is completed. Apr 26 08:59:26 192.168.122.209 [60916.635863] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:59:26 192.168.122.209 [60917.093203] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:59:26 192.168.122.209 [60917.121383] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:59:26 192.168.122.209 [60917.152983] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:59:26 192.168.122.209 [60917.191917] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:59:26 192.168.122.209 [60917.239902] [tempesta fw] Tempesta FW is ready Apr 26 08:59:27 192.168.122.209 [60917.826171] [tdb] Close table 'client0.tdb' Apr 26 08:59:27 192.168.122.209 [60918.018737] [tdb] Close table 'sessions0.tdb' Apr 26 08:59:30 192.168.122.209 [60921.237984] [tdb] Close table 'cache0.tdb' Apr 26 08:59:30 192.168.122.209 [60921.495311] [tdb] Close table 'filter0.tdb' Apr 26 08:59:30 192.168.122.209 [60921.495748] [tempesta fw] modules are stopped Apr 26 08:59:31 192.168.122.209 [60921.733266] [tempesta fw] exiting... Apr 26 08:59:31 192.168.122.209 [60921.875806] [tdb] Shutdown Tempesta DB Apr 26 08:59:31 192.168.122.209 [60922.103762] End test: http_general.test_headers.TestHost.test_forward_absolute_uri_full_path Apr 26 08:59:31 192.168.122.209 [60922.113319] Start test: http_general.test_headers.TestHost.test_forwarded_and_empty_host_header Apr 26 08:59:32 192.168.122.209 [60923.206190] [tdb] Start Tempesta DB Apr 26 08:59:32 192.168.122.209 [60923.366516] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:59:34 192.168.122.209 [60924.712059] [tempesta fw] Configuration processing is completed. Apr 26 08:59:34 192.168.122.209 [60924.766287] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:59:34 192.168.122.209 [60925.189153] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:59:34 192.168.122.209 [60925.216263] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:59:34 192.168.122.209 [60925.243158] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:59:34 192.168.122.209 [60925.296066] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:59:34 192.168.122.209 [60925.343964] [tempesta fw] Tempesta FW is ready Apr 26 08:59:34 192.168.122.209 [60925.496682] [tempesta fw] Warning: Invalid authority: 127.0.0.2 Apr 26 08:59:35 192.168.122.209 [60925.879520] [tdb] Close table 'client0.tdb' Apr 26 08:59:35 192.168.122.209 [60926.096394] [tdb] Close table 'sessions0.tdb' Apr 26 08:59:38 192.168.122.209 [60929.333078] [tdb] Close table 'cache0.tdb' Apr 26 08:59:38 192.168.122.209 [60929.559639] [tdb] Close table 'filter0.tdb' Apr 26 08:59:38 192.168.122.209 [60929.560086] [tempesta fw] modules are stopped Apr 26 08:59:39 192.168.122.209 [60929.752996] [tempesta fw] exiting... Apr 26 08:59:39 192.168.122.209 [60929.878404] [tdb] Shutdown Tempesta DB Apr 26 08:59:39 192.168.122.209 [60930.125323] End test: http_general.test_headers.TestHost.test_forwarded_and_empty_host_header Apr 26 08:59:39 192.168.122.209 [60930.142920] Start test: http_general.test_headers.TestHost.test_host_header_empty Apr 26 08:59:40 192.168.122.209 [60931.198143] [tdb] Start Tempesta DB Apr 26 08:59:40 192.168.122.209 [60931.324092] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:59:42 192.168.122.209 [60932.748218] [tempesta fw] Configuration processing is completed. Apr 26 08:59:42 192.168.122.209 [60932.803873] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:59:42 192.168.122.209 [60933.261457] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:59:42 192.168.122.209 [60933.290276] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:59:42 192.168.122.209 [60933.319713] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:59:42 192.168.122.209 [60933.360132] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:59:42 192.168.122.209 [60933.404077] [tempesta fw] Tempesta FW is ready Apr 26 08:59:42 192.168.122.209 [60933.535195] [tempesta fw] Warning: Invalid authority: 127.0.0.2 Apr 26 08:59:43 192.168.122.209 [60933.960113] [tdb] Close table 'client0.tdb' Apr 26 08:59:43 192.168.122.209 [60934.169396] [tdb] Close table 'sessions0.tdb' Apr 26 08:59:46 192.168.122.209 [60937.447290] [tdb] Close table 'cache0.tdb' Apr 26 08:59:47 192.168.122.209 [60937.677577] [tdb] Close table 'filter0.tdb' Apr 26 08:59:47 192.168.122.209 [60937.678013] [tempesta fw] modules are stopped Apr 26 08:59:47 192.168.122.209 [60937.892036] [tempesta fw] exiting... Apr 26 08:59:47 192.168.122.209 [60938.024130] [tdb] Shutdown Tempesta DB Apr 26 08:59:47 192.168.122.209 [60938.240476] End test: http_general.test_headers.TestHost.test_host_header_empty Apr 26 08:59:47 192.168.122.209 [60938.249839] Start test: http_general.test_headers.TestHost.test_host_header_ok Apr 26 08:59:48 192.168.122.209 [60939.320690] [tdb] Start Tempesta DB Apr 26 08:59:48 192.168.122.209 [60939.459257] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:59:50 192.168.122.209 [60940.792281] [tempesta fw] Configuration processing is completed. Apr 26 08:59:50 192.168.122.209 [60940.856319] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:59:50 192.168.122.209 [60941.270918] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:59:50 192.168.122.209 [60941.297848] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:59:50 192.168.122.209 [60941.326539] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:59:50 192.168.122.209 [60941.372238] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:59:50 192.168.122.209 [60941.412176] [tempesta fw] Tempesta FW is ready Apr 26 08:59:51 192.168.122.209 [60941.958103] [tdb] Close table 'client0.tdb' Apr 26 08:59:51 192.168.122.209 [60942.162001] [tdb] Close table 'sessions0.tdb' Apr 26 08:59:54 192.168.122.209 [60945.384847] [tdb] Close table 'cache0.tdb' Apr 26 08:59:55 192.168.122.209 [60945.669251] [tdb] Close table 'filter0.tdb' Apr 26 08:59:55 192.168.122.209 [60945.669727] [tempesta fw] modules are stopped Apr 26 08:59:55 192.168.122.209 [60945.854926] [tempesta fw] exiting... Apr 26 08:59:55 192.168.122.209 [60945.962888] [tdb] Shutdown Tempesta DB Apr 26 08:59:55 192.168.122.209 [60946.163140] End test: http_general.test_headers.TestHost.test_host_header_ok Apr 26 08:59:55 192.168.122.209 [60946.181583] Start test: http_general.test_headers.TestHost.test_host_in_uri_without_host_header Apr 26 08:59:56 192.168.122.209 [60947.204060] [tdb] Start Tempesta DB Apr 26 08:59:56 192.168.122.209 [60947.342076] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 08:59:58 192.168.122.209 [60948.788399] [tempesta fw] Configuration processing is completed. Apr 26 08:59:58 192.168.122.209 [60948.845067] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 08:59:58 192.168.122.209 [60949.303385] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 08:59:58 192.168.122.209 [60949.333224] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 08:59:58 192.168.122.209 [60949.368658] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 08:59:58 192.168.122.209 [60949.424338] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 08:59:58 192.168.122.209 [60949.464284] [tempesta fw] Tempesta FW is ready Apr 26 08:59:59 192.168.122.209 [60949.609176] [tempesta fw] Warning: Parser error: state=Req_UriAuthority input(-0)=0x40('@') data_len=1 off=0 Apr 26 08:59:59 192.168.122.209 [60950.011764] [tdb] Close table 'client0.tdb' Apr 26 08:59:59 192.168.122.209 [60950.202888] [tdb] Close table 'sessions0.tdb' Apr 26 09:00:02 192.168.122.209 [60953.384449] [tdb] Close table 'cache0.tdb' Apr 26 09:00:03 192.168.122.209 [60953.643524] [tdb] Close table 'filter0.tdb' Apr 26 09:00:03 192.168.122.209 [60953.643988] [tempesta fw] modules are stopped Apr 26 09:00:03 192.168.122.209 [60953.823634] [tempesta fw] exiting... Apr 26 09:00:03 192.168.122.209 [60953.937718] [tdb] Shutdown Tempesta DB Apr 26 09:00:03 192.168.122.209 [60954.178572] End test: http_general.test_headers.TestHost.test_host_in_uri_without_host_header Apr 26 09:00:03 192.168.122.209 [60954.189300] Start test: http_general.test_headers.TestHost.test_host_missing Apr 26 09:00:04 192.168.122.209 [60955.167163] [tdb] Start Tempesta DB Apr 26 09:00:04 192.168.122.209 [60955.312691] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:00:06 192.168.122.209 [60956.636465] [tempesta fw] Configuration processing is completed. Apr 26 09:00:06 192.168.122.209 [60956.687452] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:00:06 192.168.122.209 [60957.103737] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:00:06 192.168.122.209 [60957.129729] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:00:06 192.168.122.209 [60957.155707] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:00:06 192.168.122.209 [60957.244431] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:00:06 192.168.122.209 [60957.288391] [tempesta fw] Tempesta FW is ready Apr 26 09:00:06 192.168.122.209 [60957.402946] [tempesta fw] Warning: Invalid authority: 127.0.0.2 Apr 26 09:00:07 192.168.122.209 [60957.841393] [tdb] Close table 'client0.tdb' Apr 26 09:00:07 192.168.122.209 [60958.018133] [tdb] Close table 'sessions0.tdb' Apr 26 09:00:10 192.168.122.209 [60961.292564] [tdb] Close table 'cache0.tdb' Apr 26 09:00:10 192.168.122.209 [60961.527175] [tdb] Close table 'filter0.tdb' Apr 26 09:00:10 192.168.122.209 [60961.527610] [tempesta fw] modules are stopped Apr 26 09:00:11 192.168.122.209 [60961.744147] [tempesta fw] exiting... Apr 26 09:00:11 192.168.122.209 [60961.845878] [tdb] Shutdown Tempesta DB Apr 26 09:00:11 192.168.122.209 [60962.076711] End test: http_general.test_headers.TestHost.test_host_missing Apr 26 09:00:11 192.168.122.209 [60962.087447] Start test: http_general.test_headers.TestHostWithCache.test_different_host_in_uri_and_headers_1 Apr 26 09:00:12 192.168.122.209 [60963.116843] [tdb] Start Tempesta DB Apr 26 09:00:12 192.168.122.209 [60963.248235] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:00:14 192.168.122.209 [60965.024571] [tempesta fw] Configuration processing is completed. Apr 26 09:00:14 192.168.122.209 [60965.076135] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:00:15 192.168.122.209 [60965.586337] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:00:15 192.168.122.209 [60965.619897] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:00:15 192.168.122.209 [60965.653207] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:00:15 192.168.122.209 [60965.708549] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:00:15 192.168.122.209 [60965.760483] [tempesta fw] Tempesta FW is ready Apr 26 09:00:15 192.168.122.209 [60965.900771] [tempesta fw] Warning: Parser error: state=Req_UriAuthority input(-0)=0x40('@') data_len=1 off=0 Apr 26 09:00:15 192.168.122.209 [60966.328034] [tdb] Close table 'client0.tdb' Apr 26 09:00:15 192.168.122.209 [60966.520157] [tdb] Close table 'sessions0.tdb' Apr 26 09:00:19 192.168.122.209 [60969.784677] [tdb] Close table 'cache0.tdb' Apr 26 09:00:19 192.168.122.209 [60970.022073] [tdb] Close table 'filter0.tdb' Apr 26 09:00:19 192.168.122.209 [60970.022490] [tempesta fw] modules are stopped Apr 26 09:00:19 192.168.122.209 [60970.221914] [tempesta fw] exiting... Apr 26 09:00:19 192.168.122.209 [60970.336708] [tdb] Shutdown Tempesta DB Apr 26 09:00:20 192.168.122.209 [60970.583782] End test: http_general.test_headers.TestHostWithCache.test_different_host_in_uri_and_headers_1 Apr 26 09:00:20 192.168.122.209 [60970.595245] Start test: http_general.test_headers.TestHostWithCache.test_different_host_in_uri_and_headers_10 Apr 26 09:00:21 192.168.122.209 [60971.613380] [tdb] Start Tempesta DB Apr 26 09:00:21 192.168.122.209 [60971.744648] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:00:22 192.168.122.209 [60973.516730] [tempesta fw] Configuration processing is completed. Apr 26 09:00:23 192.168.122.209 [60973.577716] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:00:23 192.168.122.209 [60974.006725] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:00:23 192.168.122.209 [60974.032685] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:00:23 192.168.122.209 [60974.059267] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:00:23 192.168.122.209 [60974.120674] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:00:23 192.168.122.209 [60974.160608] [tempesta fw] Tempesta FW is ready Apr 26 09:00:23 192.168.122.209 [60974.290847] [tempesta fw] Warning: Parser error: state=Req_UriAuthorityStart input(-0)=0x2f('/') data_len=1 off=0 Apr 26 09:00:24 192.168.122.209 [60974.674246] [tdb] Close table 'client0.tdb' Apr 26 09:00:24 192.168.122.209 [60974.882579] [tdb] Close table 'sessions0.tdb' Apr 26 09:00:27 192.168.122.209 [60978.098869] [tdb] Close table 'cache0.tdb' Apr 26 09:00:27 192.168.122.209 [60978.342287] [tdb] Close table 'filter0.tdb' Apr 26 09:00:27 192.168.122.209 [60978.342714] [tempesta fw] modules are stopped Apr 26 09:00:28 192.168.122.209 [60978.593349] [tempesta fw] exiting... Apr 26 09:00:28 192.168.122.209 [60978.714004] [tdb] Shutdown Tempesta DB Apr 26 09:00:28 192.168.122.209 [60978.949790] End test: http_general.test_headers.TestHostWithCache.test_different_host_in_uri_and_headers_10 Apr 26 09:00:28 192.168.122.209 [60978.970460] Start test: http_general.test_headers.TestHostWithCache.test_different_host_in_uri_and_headers_11 Apr 26 09:00:29 192.168.122.209 [60980.030551] [tdb] Start Tempesta DB Apr 26 09:00:29 192.168.122.209 [60980.161077] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:00:31 192.168.122.209 [60981.904787] [tempesta fw] Configuration processing is completed. Apr 26 09:00:31 192.168.122.209 [60981.959709] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:00:31 192.168.122.209 [60982.386195] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:00:31 192.168.122.209 [60982.424754] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:00:31 192.168.122.209 [60982.452229] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:00:31 192.168.122.209 [60982.496765] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:00:31 192.168.122.209 [60982.544705] [tempesta fw] Tempesta FW is ready Apr 26 09:00:32 192.168.122.209 [60982.659053] [tempesta fw] Warning: Parser error: state=Req_UriAuthority input(-0)=0x40('@') data_len=1 off=0 Apr 26 09:00:32 192.168.122.209 [60983.108383] [tdb] Close table 'client0.tdb' Apr 26 09:00:32 192.168.122.209 [60983.294079] [tdb] Close table 'sessions0.tdb' Apr 26 09:00:35 192.168.122.209 [60986.506225] [tdb] Close table 'cache0.tdb' Apr 26 09:00:36 192.168.122.209 [60986.756852] [tdb] Close table 'filter0.tdb' Apr 26 09:00:36 192.168.122.209 [60986.757283] [tempesta fw] modules are stopped Apr 26 09:00:36 192.168.122.209 [60986.953021] [tempesta fw] exiting... Apr 26 09:00:36 192.168.122.209 [60987.062864] [tdb] Shutdown Tempesta DB Apr 26 09:00:36 192.168.122.209 [60987.243273] End test: http_general.test_headers.TestHostWithCache.test_different_host_in_uri_and_headers_11 Apr 26 09:00:36 192.168.122.209 [60987.257442] Start test: http_general.test_headers.TestHostWithCache.test_different_host_in_uri_and_headers_12 Apr 26 09:00:37 192.168.122.209 [60988.186019] [tdb] Start Tempesta DB Apr 26 09:00:37 192.168.122.209 [60988.322313] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:00:39 192.168.122.209 [60990.148889] [tempesta fw] Configuration processing is completed. Apr 26 09:00:39 192.168.122.209 [60990.205281] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:00:40 192.168.122.209 [60990.621441] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:00:40 192.168.122.209 [60990.647285] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:00:40 192.168.122.209 [60990.673315] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:00:40 192.168.122.209 [60990.716856] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:00:40 192.168.122.209 [60990.768813] [tempesta fw] Tempesta FW is ready Apr 26 09:00:40 192.168.122.209 [60990.896063] [tempesta fw] Warning: Parser error: state=Req_UriAuthorityStart input(-0)=0x3a(':') data_len=1 off=0 Apr 26 09:00:40 192.168.122.209 [60991.303658] [tdb] Close table 'client0.tdb' Apr 26 09:00:40 192.168.122.209 [60991.510484] [tdb] Close table 'sessions0.tdb' Apr 26 09:00:44 192.168.122.209 [60994.861494] [tdb] Close table 'cache0.tdb' Apr 26 09:00:44 192.168.122.209 [60995.108505] [tdb] Close table 'filter0.tdb' Apr 26 09:00:44 192.168.122.209 [60995.108985] [tempesta fw] modules are stopped Apr 26 09:00:44 192.168.122.209 [60995.330763] [tempesta fw] exiting... Apr 26 09:00:44 192.168.122.209 [60995.477705] [tdb] Shutdown Tempesta DB Apr 26 09:00:45 192.168.122.209 [60995.715159] End test: http_general.test_headers.TestHostWithCache.test_different_host_in_uri_and_headers_12 Apr 26 09:00:45 192.168.122.209 [60995.723072] Start test: http_general.test_headers.TestHostWithCache.test_different_host_in_uri_and_headers_13 Apr 26 09:00:46 192.168.122.209 [60996.655633] [tdb] Start Tempesta DB Apr 26 09:00:46 192.168.122.209 [60996.798359] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:00:48 192.168.122.209 [60998.605024] [tempesta fw] Configuration processing is completed. Apr 26 09:00:48 192.168.122.209 [60998.677735] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:00:48 192.168.122.209 [60999.097100] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:00:48 192.168.122.209 [60999.124060] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:00:48 192.168.122.209 [60999.150925] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:00:48 192.168.122.209 [60999.200976] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:00:48 192.168.122.209 [60999.240943] [tempesta fw] Tempesta FW is ready Apr 26 09:00:48 192.168.122.209 [60999.384157] [tempesta fw] Warning: Parser error: state=Req_UriAuthorityStart input(-0)=0x2f('/') data_len=1 off=0 Apr 26 09:00:49 192.168.122.209 [60999.802350] [tdb] Close table 'client0.tdb' Apr 26 09:00:49 192.168.122.209 [60999.996561] [tdb] Close table 'sessions0.tdb' Apr 26 09:00:52 192.168.122.209 [61003.245950] [tdb] Close table 'cache0.tdb' Apr 26 09:00:52 192.168.122.209 [61003.460224] [tdb] Close table 'filter0.tdb' Apr 26 09:00:52 192.168.122.209 [61003.460650] [tempesta fw] modules are stopped Apr 26 09:00:53 192.168.122.209 [61003.666560] [tempesta fw] exiting... Apr 26 09:00:53 192.168.122.209 [61003.764976] [tdb] Shutdown Tempesta DB Apr 26 09:00:53 192.168.122.209 [61003.969282] End test: http_general.test_headers.TestHostWithCache.test_different_host_in_uri_and_headers_13 Apr 26 09:00:53 192.168.122.209 [61003.989857] Start test: http_general.test_headers.TestHostWithCache.test_different_host_in_uri_and_headers_2 Apr 26 09:00:54 192.168.122.209 [61004.993017] [tdb] Start Tempesta DB Apr 26 09:00:54 192.168.122.209 [61005.125887] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:00:56 192.168.122.209 [61006.897145] [tempesta fw] Configuration processing is completed. Apr 26 09:00:56 192.168.122.209 [61006.966276] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:00:56 192.168.122.209 [61007.376252] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:00:56 192.168.122.209 [61007.402732] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:00:56 192.168.122.209 [61007.429221] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:00:56 192.168.122.209 [61007.477078] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:00:56 192.168.122.209 [61007.540954] [tempesta fw] Tempesta FW is ready Apr 26 09:00:57 192.168.122.209 [61007.661942] [tempesta fw] Warning: Parser error: state=Req_UriAuthority input(-0)=0x40('@') data_len=1 off=0 Apr 26 09:00:57 192.168.122.209 [61008.070647] [tdb] Close table 'client0.tdb' Apr 26 09:00:57 192.168.122.209 [61008.259503] [tdb] Close table 'sessions0.tdb' Apr 26 09:01:00 192.168.122.209 [61011.550521] [tdb] Close table 'cache0.tdb' Apr 26 09:01:01 192.168.122.209 [61011.806864] [tdb] Close table 'filter0.tdb' Apr 26 09:01:01 192.168.122.209 [61011.807294] [tempesta fw] modules are stopped Apr 26 09:01:01 192.168.122.209 [61012.035723] [tempesta fw] exiting... Apr 26 09:01:01 192.168.122.209 [61012.130175] [tdb] Shutdown Tempesta DB Apr 26 09:01:01 192.168.122.209 [61012.349360] End test: http_general.test_headers.TestHostWithCache.test_different_host_in_uri_and_headers_2 Apr 26 09:01:01 192.168.122.209 [61012.358376] Start test: http_general.test_headers.TestHostWithCache.test_different_host_in_uri_and_headers_3 Apr 26 09:01:02 192.168.122.209 [61013.380867] [tdb] Start Tempesta DB Apr 26 09:01:02 192.168.122.209 [61013.527596] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:01:04 192.168.122.209 [61015.317215] [tempesta fw] Configuration processing is completed. Apr 26 09:01:04 192.168.122.209 [61015.371040] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:01:05 192.168.122.209 [61015.781008] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:01:05 192.168.122.209 [61015.806374] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:01:05 192.168.122.209 [61015.831853] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:01:05 192.168.122.209 [61015.873073] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:01:05 192.168.122.209 [61015.921128] [tempesta fw] Tempesta FW is ready Apr 26 09:01:05 192.168.122.209 [61016.041688] [tempesta fw] Warning: Parser error: state=Req_UriAuthority input(-0)=0x40('@') data_len=1 off=0 Apr 26 09:01:05 192.168.122.209 [61016.430297] [tdb] Close table 'client0.tdb' Apr 26 09:01:06 192.168.122.209 [61016.643879] [tdb] Close table 'sessions0.tdb' Apr 26 09:01:09 192.168.122.209 [61019.876615] [tdb] Close table 'cache0.tdb' Apr 26 09:01:09 192.168.122.209 [61020.136272] [tdb] Close table 'filter0.tdb' Apr 26 09:01:09 192.168.122.209 [61020.136725] [tempesta fw] modules are stopped Apr 26 09:01:09 192.168.122.209 [61020.335954] [tempesta fw] exiting... Apr 26 09:01:09 192.168.122.209 [61020.452907] [tdb] Shutdown Tempesta DB Apr 26 09:01:10 192.168.122.209 [61020.690480] End test: http_general.test_headers.TestHostWithCache.test_different_host_in_uri_and_headers_3 Apr 26 09:01:10 192.168.122.209 [61020.716366] Start test: http_general.test_headers.TestHostWithCache.test_different_host_in_uri_and_headers_4 Apr 26 09:01:11 192.168.122.209 [61021.683823] [tdb] Start Tempesta DB Apr 26 09:01:11 192.168.122.209 [61021.819184] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:01:13 192.168.122.209 [61023.681323] [tempesta fw] Configuration processing is completed. Apr 26 09:01:13 192.168.122.209 [61023.736118] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:01:13 192.168.122.209 [61024.145329] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:01:13 192.168.122.209 [61024.172725] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:01:13 192.168.122.209 [61024.200634] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:01:13 192.168.122.209 [61024.265286] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:01:13 192.168.122.209 [61024.305239] [tempesta fw] Tempesta FW is ready Apr 26 09:01:14 192.168.122.209 [61024.918459] [tdb] Close table 'client0.tdb' Apr 26 09:01:14 192.168.122.209 [61025.107216] [tdb] Close table 'sessions0.tdb' Apr 26 09:01:17 192.168.122.209 [61028.337695] [tdb] Close table 'cache0.tdb' Apr 26 09:01:18 192.168.122.209 [61028.584753] [tdb] Close table 'filter0.tdb' Apr 26 09:01:18 192.168.122.209 [61028.585208] [tempesta fw] modules are stopped Apr 26 09:01:18 192.168.122.209 [61028.805042] [tempesta fw] exiting... Apr 26 09:01:18 192.168.122.209 [61028.924990] [tdb] Shutdown Tempesta DB Apr 26 09:01:18 192.168.122.209 [61029.112472] End test: http_general.test_headers.TestHostWithCache.test_different_host_in_uri_and_headers_4 Apr 26 09:01:18 192.168.122.209 [61029.131450] Start test: http_general.test_headers.TestHostWithCache.test_different_host_in_uri_and_headers_5 Apr 26 09:01:19 192.168.122.209 [61030.165264] [tdb] Start Tempesta DB Apr 26 09:01:19 192.168.122.209 [61030.308684] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:01:21 192.168.122.209 [61032.117418] [tempesta fw] Configuration processing is completed. Apr 26 09:01:21 192.168.122.209 [61032.174470] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:01:22 192.168.122.209 [61032.579993] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:01:22 192.168.122.209 [61032.615886] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:01:22 192.168.122.209 [61032.641345] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:01:22 192.168.122.209 [61032.689390] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:01:22 192.168.122.209 [61032.737334] [tempesta fw] Tempesta FW is ready Apr 26 09:01:22 192.168.122.209 [61032.880153] [tempesta fw] Warning: Parser error: state=Req_UriAuthority input(-0)=0x40('@') data_len=1 off=0 Apr 26 09:01:22 192.168.122.209 [61033.290402] [tdb] Close table 'client0.tdb' Apr 26 09:01:22 192.168.122.209 [61033.496339] [tdb] Close table 'sessions0.tdb' Apr 26 09:01:26 192.168.122.209 [61036.731551] [tdb] Close table 'cache0.tdb' Apr 26 09:01:26 192.168.122.209 [61036.963932] [tdb] Close table 'filter0.tdb' Apr 26 09:01:26 192.168.122.209 [61036.964392] [tempesta fw] modules are stopped Apr 26 09:01:26 192.168.122.209 [61037.153537] [tempesta fw] exiting... Apr 26 09:01:26 192.168.122.209 [61037.264876] [tdb] Shutdown Tempesta DB Apr 26 09:01:26 192.168.122.209 [61037.435949] End test: http_general.test_headers.TestHostWithCache.test_different_host_in_uri_and_headers_5 Apr 26 09:01:26 192.168.122.209 [61037.448902] Start test: http_general.test_headers.TestHostWithCache.test_different_host_in_uri_and_headers_6 Apr 26 09:01:27 192.168.122.209 [61038.458682] [tdb] Start Tempesta DB Apr 26 09:01:28 192.168.122.209 [61038.584771] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:01:29 192.168.122.209 [61040.433520] [tempesta fw] Configuration processing is completed. Apr 26 09:01:29 192.168.122.209 [61040.485572] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:01:30 192.168.122.209 [61040.894705] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:01:30 192.168.122.209 [61040.931444] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:01:30 192.168.122.209 [61040.957111] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:01:30 192.168.122.209 [61040.997494] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:01:30 192.168.122.209 [61041.041408] [tempesta fw] Tempesta FW is ready Apr 26 09:01:30 192.168.122.209 [61041.173803] [tempesta fw] Warning: Parser error: state=Req_UriAuthority input(-8)=0x40('p://user@:/url/ HTTP/1.1') data_len=27 off=11 Apr 26 09:01:30 192.168.122.209 [61041.572678] [tdb] Close table 'client0.tdb' Apr 26 09:01:31 192.168.122.209 [61041.774770] [tdb] Close table 'sessions0.tdb' Apr 26 09:01:34 192.168.122.209 [61045.023954] [tdb] Close table 'cache0.tdb' Apr 26 09:01:34 192.168.122.209 [61045.262875] [tdb] Close table 'filter0.tdb' Apr 26 09:01:34 192.168.122.209 [61045.263306] [tempesta fw] modules are stopped Apr 26 09:01:34 192.168.122.209 [61045.497097] [tempesta fw] exiting... Apr 26 09:01:35 192.168.122.209 [61045.612347] [tdb] Shutdown Tempesta DB Apr 26 09:01:35 192.168.122.209 [61045.841034] End test: http_general.test_headers.TestHostWithCache.test_different_host_in_uri_and_headers_6 Apr 26 09:01:35 192.168.122.209 [61045.851917] Start test: http_general.test_headers.TestHostWithCache.test_different_host_in_uri_and_headers_7 Apr 26 09:01:36 192.168.122.209 [61046.895477] [tdb] Start Tempesta DB Apr 26 09:01:36 192.168.122.209 [61047.041991] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:01:38 192.168.122.209 [61048.749634] [tempesta fw] Configuration processing is completed. Apr 26 09:01:38 192.168.122.209 [61048.801594] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:01:38 192.168.122.209 [61049.206214] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:01:38 192.168.122.209 [61049.232095] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:01:38 192.168.122.209 [61049.259633] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:01:38 192.168.122.209 [61049.313604] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:01:38 192.168.122.209 [61049.357550] [tempesta fw] Tempesta FW is ready Apr 26 09:01:38 192.168.122.209 [61049.491759] [tempesta fw] Warning: Parser error: state=Req_UriAuthority input(-0)=0x40('@') data_len=1 off=0 Apr 26 09:01:39 192.168.122.209 [61049.912991] [tdb] Close table 'client0.tdb' Apr 26 09:01:39 192.168.122.209 [61050.104204] [tdb] Close table 'sessions0.tdb' Apr 26 09:01:42 192.168.122.209 [61053.385662] [tdb] Close table 'cache0.tdb' Apr 26 09:01:43 192.168.122.209 [61053.638693] [tdb] Close table 'filter0.tdb' Apr 26 09:01:43 192.168.122.209 [61053.639122] [tempesta fw] modules are stopped Apr 26 09:01:43 192.168.122.209 [61053.830002] [tempesta fw] exiting... Apr 26 09:01:43 192.168.122.209 [61053.974571] [tdb] Shutdown Tempesta DB Apr 26 09:01:43 192.168.122.209 [61054.193234] End test: http_general.test_headers.TestHostWithCache.test_different_host_in_uri_and_headers_7 Apr 26 09:01:43 192.168.122.209 [61054.214256] Start test: http_general.test_headers.TestHostWithCache.test_different_host_in_uri_and_headers_8 Apr 26 09:01:44 192.168.122.209 [61055.185270] [tdb] Start Tempesta DB Apr 26 09:01:44 192.168.122.209 [61055.326234] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:01:46 192.168.122.209 [61057.105714] [tempesta fw] Configuration processing is completed. Apr 26 09:01:46 192.168.122.209 [61057.160523] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:01:46 192.168.122.209 [61057.571454] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:01:47 192.168.122.209 [61057.597486] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:01:47 192.168.122.209 [61057.623915] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:01:47 192.168.122.209 [61057.681752] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:01:47 192.168.122.209 [61057.725590] [tempesta fw] Tempesta FW is ready Apr 26 09:01:47 192.168.122.209 [61057.858797] [tempesta fw] Warning: Parser error: state=Req_UriPort input(-0)=0x20(' ') data_len=1 off=0 Apr 26 09:01:47 192.168.122.209 [61058.292256] [tdb] Close table 'client0.tdb' Apr 26 09:01:47 192.168.122.209 [61058.478902] [tdb] Close table 'sessions0.tdb' Apr 26 09:01:51 192.168.122.209 [61061.654617] [tdb] Close table 'cache0.tdb' Apr 26 09:01:51 192.168.122.209 [61061.922153] [tdb] Close table 'filter0.tdb' Apr 26 09:01:51 192.168.122.209 [61061.922598] [tempesta fw] modules are stopped Apr 26 09:01:51 192.168.122.209 [61062.154346] [tempesta fw] exiting... Apr 26 09:01:51 192.168.122.209 [61062.289813] [tdb] Shutdown Tempesta DB Apr 26 09:01:51 192.168.122.209 [61062.479224] End test: http_general.test_headers.TestHostWithCache.test_different_host_in_uri_and_headers_8 Apr 26 09:01:51 192.168.122.209 [61062.500124] Start test: http_general.test_headers.TestHostWithCache.test_different_host_in_uri_and_headers_9 Apr 26 09:01:53 192.168.122.209 [61063.578617] [tdb] Start Tempesta DB Apr 26 09:01:53 192.168.122.209 [61063.712337] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:01:54 192.168.122.209 [61065.473837] [tempesta fw] Configuration processing is completed. Apr 26 09:01:54 192.168.122.209 [61065.526380] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:01:55 192.168.122.209 [61065.936556] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:01:55 192.168.122.209 [61065.962786] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:01:55 192.168.122.209 [61065.988743] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:01:55 192.168.122.209 [61066.045813] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:01:55 192.168.122.209 [61066.089763] [tempesta fw] Tempesta FW is ready Apr 26 09:01:55 192.168.122.209 [61066.226199] [tempesta fw] Warning: Parser error: state=Req_UriPort input(-0)=0x2f('/') data_len=1 off=0 Apr 26 09:01:56 192.168.122.209 [61066.626566] [tdb] Close table 'client0.tdb' Apr 26 09:01:56 192.168.122.209 [61066.823680] [tdb] Close table 'sessions0.tdb' Apr 26 09:01:59 192.168.122.209 [61070.053611] [tdb] Close table 'cache0.tdb' Apr 26 09:01:59 192.168.122.209 [61070.280211] [tdb] Close table 'filter0.tdb' Apr 26 09:01:59 192.168.122.209 [61070.280646] [tempesta fw] modules are stopped Apr 26 09:01:59 192.168.122.209 [61070.494818] [tempesta fw] exiting... Apr 26 09:02:00 192.168.122.209 [61070.649611] [tdb] Shutdown Tempesta DB Apr 26 09:02:00 192.168.122.209 [61070.840985] End test: http_general.test_headers.TestHostWithCache.test_different_host_in_uri_and_headers_9 Apr 26 09:02:00 192.168.122.209 [61070.854230] Start test: http_general.test_headers.TestMethods.test_known_methods Apr 26 09:02:01 192.168.122.209 [61071.860535] [tdb] Start Tempesta DB Apr 26 09:02:01 192.168.122.209 [61072.001820] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:02:02 192.168.122.209 [61073.377991] [tempesta fw] Configuration processing is completed. Apr 26 09:02:02 192.168.122.209 [61073.433672] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:02:03 192.168.122.209 [61073.843549] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:02:03 192.168.122.209 [61073.871039] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:02:03 192.168.122.209 [61073.897775] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:02:03 192.168.122.209 [61073.973940] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:02:03 192.168.122.209 [61074.013859] [tempesta fw] Tempesta FW is ready Apr 26 09:02:04 192.168.122.209 [61075.047836] [tdb] Close table 'client0.tdb' Apr 26 09:02:04 192.168.122.209 [61075.265603] [tdb] Close table 'sessions0.tdb' Apr 26 09:02:08 192.168.122.209 [61078.596160] [tdb] Close table 'cache0.tdb' Apr 26 09:02:08 192.168.122.209 [61078.815800] [tdb] Close table 'filter0.tdb' Apr 26 09:02:08 192.168.122.209 [61078.816240] [tempesta fw] modules are stopped Apr 26 09:02:08 192.168.122.209 [61079.017805] [tempesta fw] exiting... Apr 26 09:02:08 192.168.122.209 [61079.143638] [tdb] Shutdown Tempesta DB Apr 26 09:02:08 192.168.122.209 [61079.357885] End test: http_general.test_headers.TestMethods.test_known_methods Apr 26 09:02:08 192.168.122.209 [61079.371293] Start test: http_general.test_headers.TestMethods.test_known_methods_leading_crlf Apr 26 09:02:09 192.168.122.209 [61080.433733] [tdb] Start Tempesta DB Apr 26 09:02:10 192.168.122.209 [61080.579006] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:02:11 192.168.122.209 [61081.990022] [tempesta fw] Configuration processing is completed. Apr 26 09:02:11 192.168.122.209 [61082.043945] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:02:11 192.168.122.209 [61082.464445] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:02:11 192.168.122.209 [61082.509681] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:02:11 192.168.122.209 [61082.535454] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:02:12 192.168.122.209 [61082.573974] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:02:12 192.168.122.209 [61082.613980] [tempesta fw] Tempesta FW is ready Apr 26 09:02:13 192.168.122.209 [61083.675366] [tdb] Close table 'client0.tdb' Apr 26 09:02:13 192.168.122.209 [61083.872006] [tdb] Close table 'sessions0.tdb' Apr 26 09:02:16 192.168.122.209 [61087.095818] [tdb] Close table 'cache0.tdb' Apr 26 09:02:16 192.168.122.209 [61087.342575] [tdb] Close table 'filter0.tdb' Apr 26 09:02:16 192.168.122.209 [61087.343008] [tempesta fw] modules are stopped Apr 26 09:02:17 192.168.122.209 [61087.580926] [tempesta fw] exiting... Apr 26 09:02:17 192.168.122.209 [61087.734173] [tdb] Shutdown Tempesta DB Apr 26 09:02:17 192.168.122.209 [61087.964767] End test: http_general.test_headers.TestMethods.test_known_methods_leading_crlf Apr 26 09:02:17 192.168.122.209 [61087.978780] Start test: http_general.test_headers.TestMethods.test_unknown_methods Apr 26 09:02:18 192.168.122.209 [61089.032647] [tdb] Start Tempesta DB Apr 26 09:02:18 192.168.122.209 [61089.165500] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:02:20 192.168.122.209 [61090.610181] [tempesta fw] Configuration processing is completed. Apr 26 09:02:20 192.168.122.209 [61090.661442] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:02:20 192.168.122.209 [61091.065425] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:02:20 192.168.122.209 [61091.091652] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:02:20 192.168.122.209 [61091.117946] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:02:20 192.168.122.209 [61091.162165] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:02:20 192.168.122.209 [61091.210078] [tempesta fw] Tempesta FW is ready Apr 26 09:02:21 192.168.122.209 [61091.803221] [tdb] Close table 'client0.tdb' Apr 26 09:02:21 192.168.122.209 [61091.994950] [tdb] Close table 'sessions0.tdb' Apr 26 09:02:24 192.168.122.209 [61095.219242] [tdb] Close table 'cache0.tdb' Apr 26 09:02:24 192.168.122.209 [61095.470759] [tdb] Close table 'filter0.tdb' Apr 26 09:02:24 192.168.122.209 [61095.471199] [tempesta fw] modules are stopped Apr 26 09:02:25 192.168.122.209 [61095.670674] [tempesta fw] exiting... Apr 26 09:02:25 192.168.122.209 [61095.807877] [tdb] Shutdown Tempesta DB Apr 26 09:02:25 192.168.122.209 [61095.993515] End test: http_general.test_headers.TestMethods.test_unknown_methods Apr 26 09:02:25 192.168.122.209 [61096.015168] Start test: http_general.test_headers.TestMethods.test_unknown_methods_leading_crlf Apr 26 09:02:26 192.168.122.209 [61097.035664] [tdb] Start Tempesta DB Apr 26 09:02:26 192.168.122.209 [61097.174226] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:02:27 192.168.122.209 [61098.550651] [tempesta fw] Configuration processing is completed. Apr 26 09:02:28 192.168.122.209 [61098.608158] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:02:28 192.168.122.209 [61099.031595] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:02:28 192.168.122.209 [61099.058799] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:02:28 192.168.122.209 [61099.086204] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:02:28 192.168.122.209 [61099.130232] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:02:28 192.168.122.209 [61099.170185] [tempesta fw] Tempesta FW is ready Apr 26 09:02:29 192.168.122.209 [61099.763009] [tdb] Close table 'client0.tdb' Apr 26 09:02:29 192.168.122.209 [61099.951823] [tdb] Close table 'sessions0.tdb' Apr 26 09:02:32 192.168.122.209 [61103.116454] [tdb] Close table 'cache0.tdb' Apr 26 09:02:32 192.168.122.209 [61103.378572] [tdb] Close table 'filter0.tdb' Apr 26 09:02:32 192.168.122.209 [61103.379028] [tempesta fw] modules are stopped Apr 26 09:02:32 192.168.122.209 [61103.559524] [tempesta fw] exiting... Apr 26 09:02:33 192.168.122.209 [61103.721594] [tdb] Shutdown Tempesta DB Apr 26 09:02:33 192.168.122.209 [61103.946977] End test: http_general.test_headers.TestMethods.test_unknown_methods_leading_crlf Apr 26 09:02:33 192.168.122.209 [61103.962268] Start test: http_general.test_headers.TestNoContentLengthInMethodMethodDELETE.test_request_success Apr 26 09:02:34 192.168.122.209 [61104.989274] [tdb] Start Tempesta DB Apr 26 09:02:34 192.168.122.209 [61105.127311] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:02:35 192.168.122.209 [61106.459564] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61106.459564] Maybe that's fine, but it's worth checking the [61106.459564] config - if there is no relations between the [61106.459564] names, then host name confusion attack is possible. Apr 26 09:02:36 192.168.122.209 [61106.590386] [tempesta fw] Configuration processing is completed. Apr 26 09:02:36 192.168.122.209 [61106.646345] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:02:36 192.168.122.209 [61107.062076] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:02:36 192.168.122.209 [61107.087980] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:02:36 192.168.122.209 [61107.114851] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:02:36 192.168.122.209 [61107.162351] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:02:36 192.168.122.209 [61107.202296] [tempesta fw] Tempesta FW is ready Apr 26 09:02:36 192.168.122.209 [61107.358113] [tempesta fw] 127.0.0.2 "default" "DELETE / HTTP/1.1" 200 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400080080" Apr 26 09:02:36 192.168.122.209 [61107.359509] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 09:02:36 192.168.122.209 [61107.384471] [tempesta fw] 127.0.0.2 "default" "DELETE / HTTP/1.1" 201 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400080080" Apr 26 09:02:36 192.168.122.209 [61107.386164] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 09:02:36 192.168.122.209 [61107.441811] [tempesta fw] 127.0.0.2 "default" "DELETE / HTTP/1.1" 302 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400080080" Apr 26 09:02:36 192.168.122.209 [61107.443457] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 09:02:36 192.168.122.209 [61107.466662] [tempesta fw] 127.0.0.2 "default" "DELETE / HTTP/1.1" 304 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400080080" Apr 26 09:02:36 192.168.122.209 [61107.467972] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 09:02:36 192.168.122.209 [61107.484396] [tempesta fw] 127.0.0.2 "default" "DELETE / HTTP/1.1" 400 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400080080" Apr 26 09:02:36 192.168.122.209 [61107.485458] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 09:02:36 192.168.122.209 [61107.548468] [tempesta fw] 127.0.0.2 "default" "DELETE / HTTP/1.1" 401 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400080080" Apr 26 09:02:36 192.168.122.209 [61107.549658] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 09:02:36 192.168.122.209 [61107.565677] [tempesta fw] 127.0.0.2 "default" "DELETE / HTTP/1.1" 404 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400080080" Apr 26 09:02:36 192.168.122.209 [61107.568820] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 09:02:37 192.168.122.209 [61107.587316] [tempesta fw] 127.0.0.2 "default" "DELETE / HTTP/1.1" 500 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400080080" Apr 26 09:02:37 192.168.122.209 [61107.589424] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 09:02:37 192.168.122.209 [61108.037458] [tdb] Close table 'client0.tdb' Apr 26 09:02:37 192.168.122.209 [61108.226178] [tdb] Close table 'sessions0.tdb' Apr 26 09:02:40 192.168.122.209 [61111.422488] [tdb] Close table 'cache0.tdb' Apr 26 09:02:41 192.168.122.209 [61111.665261] [tdb] Close table 'filter0.tdb' Apr 26 09:02:41 192.168.122.209 [61111.665710] [tempesta fw] modules are stopped Apr 26 09:02:41 192.168.122.209 [61111.894622] [tempesta fw] exiting... Apr 26 09:02:41 192.168.122.209 [61112.013487] [tdb] Shutdown Tempesta DB Apr 26 09:02:41 192.168.122.209 [61112.223972] End test: http_general.test_headers.TestNoContentLengthInMethodMethodDELETE.test_request_success Apr 26 09:02:41 192.168.122.209 [61112.235299] Start test: http_general.test_headers.TestNoContentLengthInMethodMethodGET.test_request_success Apr 26 09:02:42 192.168.122.209 [61113.328420] [tdb] Start Tempesta DB Apr 26 09:02:42 192.168.122.209 [61113.454901] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:02:44 192.168.122.209 [61114.783722] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61114.783722] Maybe that's fine, but it's worth checking the [61114.783722] config - if there is no relations between the [61114.783722] names, then host name confusion attack is possible. Apr 26 09:02:44 192.168.122.209 [61114.910710] [tempesta fw] Configuration processing is completed. Apr 26 09:02:44 192.168.122.209 [61114.987134] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:02:44 192.168.122.209 [61115.406517] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:02:44 192.168.122.209 [61115.440088] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:02:44 192.168.122.209 [61115.464921] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:02:44 192.168.122.209 [61115.510416] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:02:44 192.168.122.209 [61115.550388] [tempesta fw] Tempesta FW is ready Apr 26 09:02:45 192.168.122.209 [61115.699570] [tempesta fw] 127.0.0.2 "default" "GET / HTTP/1.1" 200 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=4000c0080" Apr 26 09:02:45 192.168.122.209 [61115.701438] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 09:02:45 192.168.122.209 [61115.720850] [tempesta fw] 127.0.0.2 "default" "GET / HTTP/1.1" 302 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=4000c0080" Apr 26 09:02:45 192.168.122.209 [61115.722437] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 09:02:45 192.168.122.209 [61115.782941] [tempesta fw] 127.0.0.2 "default" "GET / HTTP/1.1" 304 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=4000c0080" Apr 26 09:02:45 192.168.122.209 [61115.785926] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 09:02:45 192.168.122.209 [61115.803787] [tempesta fw] 127.0.0.2 "default" "GET / HTTP/1.1" 400 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=4000c0080" Apr 26 09:02:45 192.168.122.209 [61115.805217] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 09:02:45 192.168.122.209 [61115.826074] [tempesta fw] 127.0.0.2 "default" "GET / HTTP/1.1" 401 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=4000c0080" Apr 26 09:02:45 192.168.122.209 [61115.827276] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 09:02:45 192.168.122.209 [61115.886496] [tempesta fw] 127.0.0.2 "default" "GET / HTTP/1.1" 404 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=4000c0080" Apr 26 09:02:45 192.168.122.209 [61115.888738] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 09:02:45 192.168.122.209 [61115.907614] [tempesta fw] 127.0.0.2 "default" "GET / HTTP/1.1" 500 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=4000c0080" Apr 26 09:02:45 192.168.122.209 [61115.909342] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 09:02:45 192.168.122.209 [61116.312619] [tdb] Close table 'client0.tdb' Apr 26 09:02:45 192.168.122.209 [61116.502447] [tdb] Close table 'sessions0.tdb' Apr 26 09:02:49 192.168.122.209 [61119.686672] [tdb] Close table 'cache0.tdb' Apr 26 09:02:49 192.168.122.209 [61119.933947] [tdb] Close table 'filter0.tdb' Apr 26 09:02:49 192.168.122.209 [61119.934411] [tempesta fw] modules are stopped Apr 26 09:02:49 192.168.122.209 [61120.148670] [tempesta fw] exiting... Apr 26 09:02:49 192.168.122.209 [61120.258757] [tdb] Shutdown Tempesta DB Apr 26 09:02:49 192.168.122.209 [61120.485605] End test: http_general.test_headers.TestNoContentLengthInMethodMethodGET.test_request_success Apr 26 09:02:49 192.168.122.209 [61120.500665] Start test: http_general.test_headers.TestNoContentLengthInMethodMethodHEAD.test_request_success Apr 26 09:02:50 192.168.122.209 [61121.524451] [tdb] Start Tempesta DB Apr 26 09:02:51 192.168.122.209 [61121.659485] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:02:52 192.168.122.209 [61123.003052] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61123.003052] Maybe that's fine, but it's worth checking the [61123.003052] config - if there is no relations between the [61123.003052] names, then host name confusion attack is possible. Apr 26 09:02:52 192.168.122.209 [61123.122576] [tempesta fw] Configuration processing is completed. Apr 26 09:02:52 192.168.122.209 [61123.177192] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:02:53 192.168.122.209 [61123.584249] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:02:53 192.168.122.209 [61123.610492] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:02:53 192.168.122.209 [61123.637404] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:02:53 192.168.122.209 [61123.714568] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:02:53 192.168.122.209 [61123.770508] [tempesta fw] Tempesta FW is ready Apr 26 09:02:53 192.168.122.209 [61123.917029] [tempesta fw] 127.0.0.2 "default" "HEAD / HTTP/1.1" 200 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400100080" Apr 26 09:02:53 192.168.122.209 [61123.920150] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 09:02:53 192.168.122.209 [61124.351824] [tdb] Close table 'client0.tdb' Apr 26 09:02:53 192.168.122.209 [61124.535475] [tdb] Close table 'sessions0.tdb' Apr 26 09:02:57 192.168.122.209 [61127.760779] [tdb] Close table 'cache0.tdb' Apr 26 09:02:57 192.168.122.209 [61128.034297] [tdb] Close table 'filter0.tdb' Apr 26 09:02:57 192.168.122.209 [61128.034740] [tempesta fw] modules are stopped Apr 26 09:02:57 192.168.122.209 [61128.227789] [tempesta fw] exiting... Apr 26 09:02:57 192.168.122.209 [61128.401783] [tdb] Shutdown Tempesta DB Apr 26 09:02:58 192.168.122.209 [61128.659651] End test: http_general.test_headers.TestNoContentLengthInMethodMethodHEAD.test_request_success Apr 26 09:02:58 192.168.122.209 [61128.671025] Start test: http_general.test_headers.TestNoContentLengthInMethodMethodPATCH.test_request_success Apr 26 09:02:59 192.168.122.209 [61129.791908] [tdb] Start Tempesta DB Apr 26 09:02:59 192.168.122.209 [61129.931572] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:03:00 192.168.122.209 [61131.243137] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61131.243137] Maybe that's fine, but it's worth checking the [61131.243137] config - if there is no relations between the [61131.243137] names, then host name confusion attack is possible. Apr 26 09:03:00 192.168.122.209 [61131.370619] [tempesta fw] Configuration processing is completed. Apr 26 09:03:00 192.168.122.209 [61131.417524] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:03:01 192.168.122.209 [61131.835300] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:03:01 192.168.122.209 [61131.861782] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:03:01 192.168.122.209 [61131.888124] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:03:01 192.168.122.209 [61131.934621] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:03:01 192.168.122.209 [61131.974636] [tempesta fw] Tempesta FW is ready Apr 26 09:03:01 192.168.122.209 [61132.135301] [tempesta fw] 127.0.0.2 "default" "PATCH / HTTP/1.1" 200 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400240080" Apr 26 09:03:01 192.168.122.209 [61132.136783] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 09:03:01 192.168.122.209 [61132.194920] [tempesta fw] 127.0.0.2 "default" "PATCH / HTTP/1.1" 201 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400240080" Apr 26 09:03:01 192.168.122.209 [61132.197024] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 09:03:01 192.168.122.209 [61132.216476] [tempesta fw] 127.0.0.2 "default" "PATCH / HTTP/1.1" 302 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400240080" Apr 26 09:03:01 192.168.122.209 [61132.217763] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 09:03:01 192.168.122.209 [61132.238213] [tempesta fw] 127.0.0.2 "default" "PATCH / HTTP/1.1" 304 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400240080" Apr 26 09:03:01 192.168.122.209 [61132.239301] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 09:03:01 192.168.122.209 [61132.300832] [tempesta fw] 127.0.0.2 "default" "PATCH / HTTP/1.1" 400 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400240080" Apr 26 09:03:01 192.168.122.209 [61132.302023] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 09:03:01 192.168.122.209 [61132.320605] [tempesta fw] 127.0.0.2 "default" "PATCH / HTTP/1.1" 401 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400240080" Apr 26 09:03:01 192.168.122.209 [61132.321660] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 09:03:01 192.168.122.209 [61132.340614] [tempesta fw] 127.0.0.2 "default" "PATCH / HTTP/1.1" 404 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400240080" Apr 26 09:03:01 192.168.122.209 [61132.342171] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 09:03:01 192.168.122.209 [61132.405208] [tempesta fw] 127.0.0.2 "default" "PATCH / HTTP/1.1" 500 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400240080" Apr 26 09:03:01 192.168.122.209 [61132.407386] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 09:03:02 192.168.122.209 [61132.856216] [tdb] Close table 'client0.tdb' Apr 26 09:03:02 192.168.122.209 [61133.043208] [tdb] Close table 'sessions0.tdb' Apr 26 09:03:05 192.168.122.209 [61136.270332] [tdb] Close table 'cache0.tdb' Apr 26 09:03:05 192.168.122.209 [61136.500503] [tdb] Close table 'filter0.tdb' Apr 26 09:03:05 192.168.122.209 [61136.500951] [tempesta fw] modules are stopped Apr 26 09:03:06 192.168.122.209 [61136.717927] [tempesta fw] exiting... Apr 26 09:03:06 192.168.122.209 [61136.830295] [tdb] Shutdown Tempesta DB Apr 26 09:03:06 192.168.122.209 [61137.084116] End test: http_general.test_headers.TestNoContentLengthInMethodMethodPATCH.test_request_success Apr 26 09:03:06 192.168.122.209 [61137.104568] Start test: http_general.test_headers.TestNoContentLengthInMethodMethodPOST.test_request_success Apr 26 09:03:07 192.168.122.209 [61138.189429] [tdb] Start Tempesta DB Apr 26 09:03:07 192.168.122.209 [61138.326794] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:03:09 192.168.122.209 [61139.739962] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61139.739962] Maybe that's fine, but it's worth checking the [61139.739962] config - if there is no relations between the [61139.739962] names, then host name confusion attack is possible. Apr 26 09:03:09 192.168.122.209 [61139.863045] [tempesta fw] Configuration processing is completed. Apr 26 09:03:09 192.168.122.209 [61139.914427] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:03:09 192.168.122.209 [61140.324566] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:03:09 192.168.122.209 [61140.351814] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:03:09 192.168.122.209 [61140.378353] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:03:09 192.168.122.209 [61140.430776] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:03:09 192.168.122.209 [61140.482752] [tempesta fw] Tempesta FW is ready Apr 26 09:03:10 192.168.122.209 [61140.632399] [tempesta fw] 127.0.0.2 "default" "POST / HTTP/1.1" 200 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400280080" Apr 26 09:03:10 192.168.122.209 [61140.633804] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 09:03:10 192.168.122.209 [61140.662325] [tempesta fw] 127.0.0.2 "default" "POST / HTTP/1.1" 201 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400280080" Apr 26 09:03:10 192.168.122.209 [61140.664597] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 09:03:10 192.168.122.209 [61140.727201] [tempesta fw] 127.0.0.2 "default" "POST / HTTP/1.1" 302 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400280080" Apr 26 09:03:10 192.168.122.209 [61140.730401] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 09:03:10 192.168.122.209 [61140.751709] [tempesta fw] 127.0.0.2 "default" "POST / HTTP/1.1" 304 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400280080" Apr 26 09:03:10 192.168.122.209 [61140.753777] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 09:03:10 192.168.122.209 [61140.773064] [tempesta fw] 127.0.0.2 "default" "POST / HTTP/1.1" 400 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400280080" Apr 26 09:03:10 192.168.122.209 [61140.774397] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 09:03:10 192.168.122.209 [61140.833434] [tempesta fw] 127.0.0.2 "default" "POST / HTTP/1.1" 401 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400280080" Apr 26 09:03:10 192.168.122.209 [61140.834784] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 09:03:10 192.168.122.209 [61140.853594] [tempesta fw] 127.0.0.2 "default" "POST / HTTP/1.1" 404 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400280080" Apr 26 09:03:10 192.168.122.209 [61140.855418] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 09:03:10 192.168.122.209 [61140.881568] [tempesta fw] 127.0.0.2 "default" "POST / HTTP/1.1" 500 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400280080" Apr 26 09:03:10 192.168.122.209 [61140.884725] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 09:03:10 192.168.122.209 [61141.304177] [tdb] Close table 'client0.tdb' Apr 26 09:03:10 192.168.122.209 [61141.500473] [tdb] Close table 'sessions0.tdb' Apr 26 09:03:14 192.168.122.209 [61144.714105] [tdb] Close table 'cache0.tdb' Apr 26 09:03:14 192.168.122.209 [61144.945340] [tdb] Close table 'filter0.tdb' Apr 26 09:03:14 192.168.122.209 [61144.945794] [tempesta fw] modules are stopped Apr 26 09:03:14 192.168.122.209 [61145.118412] [tempesta fw] exiting... Apr 26 09:03:14 192.168.122.209 [61145.234595] [tdb] Shutdown Tempesta DB Apr 26 09:03:14 192.168.122.209 [61145.473888] End test: http_general.test_headers.TestNoContentLengthInMethodMethodPOST.test_request_success Apr 26 09:03:14 192.168.122.209 [61145.489586] Start test: http_general.test_headers.TestNoContentLengthInMethodMethodPUT.test_request_success Apr 26 09:03:15 192.168.122.209 [61146.543426] [tdb] Start Tempesta DB Apr 26 09:03:16 192.168.122.209 [61146.673617] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:03:17 192.168.122.209 [61148.043461] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61148.043461] Maybe that's fine, but it's worth checking the [61148.043461] config - if there is no relations between the [61148.043461] names, then host name confusion attack is possible. Apr 26 09:03:17 192.168.122.209 [61148.170866] [tempesta fw] Configuration processing is completed. Apr 26 09:03:17 192.168.122.209 [61148.222072] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:03:18 192.168.122.209 [61148.635679] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:03:18 192.168.122.209 [61148.662452] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:03:18 192.168.122.209 [61148.689387] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:03:18 192.168.122.209 [61148.742898] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:03:18 192.168.122.209 [61148.786815] [tempesta fw] Tempesta FW is ready Apr 26 09:03:18 192.168.122.209 [61148.936220] [tempesta fw] 127.0.0.2 "default" "PUT / HTTP/1.1" 200 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400340080" Apr 26 09:03:18 192.168.122.209 [61148.938579] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 09:03:18 192.168.122.209 [61148.960313] [tempesta fw] 127.0.0.2 "default" "PUT / HTTP/1.1" 201 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400340080" Apr 26 09:03:18 192.168.122.209 [61148.961854] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 09:03:18 192.168.122.209 [61149.019430] [tempesta fw] 127.0.0.2 "default" "PUT / HTTP/1.1" 302 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400340080" Apr 26 09:03:18 192.168.122.209 [61149.020616] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 09:03:18 192.168.122.209 [61149.044623] [tempesta fw] 127.0.0.2 "default" "PUT / HTTP/1.1" 304 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400340080" Apr 26 09:03:18 192.168.122.209 [61149.045886] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 09:03:18 192.168.122.209 [61149.061687] [tempesta fw] 127.0.0.2 "default" "PUT / HTTP/1.1" 400 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400340080" Apr 26 09:03:18 192.168.122.209 [61149.064312] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 09:03:18 192.168.122.209 [61149.124718] [tempesta fw] 127.0.0.2 "default" "PUT / HTTP/1.1" 401 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400340080" Apr 26 09:03:18 192.168.122.209 [61149.125905] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 09:03:18 192.168.122.209 [61149.143124] [tempesta fw] 127.0.0.2 "default" "PUT / HTTP/1.1" 404 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400340080" Apr 26 09:03:18 192.168.122.209 [61149.146057] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 09:03:18 192.168.122.209 [61149.165241] [tempesta fw] 127.0.0.2 "default" "PUT / HTTP/1.1" 500 0 "-" "-" "ja5t=66cb9fd8d4250000" "ja5h=400340080" Apr 26 09:03:18 192.168.122.209 [61149.166751] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 09:03:19 192.168.122.209 [61149.576383] [tdb] Close table 'client0.tdb' Apr 26 09:03:19 192.168.122.209 [61149.833346] [tdb] Close table 'sessions0.tdb' Apr 26 09:03:22 192.168.122.209 [61153.082484] [tdb] Close table 'cache0.tdb' Apr 26 09:03:22 192.168.122.209 [61153.340002] [tdb] Close table 'filter0.tdb' Apr 26 09:03:22 192.168.122.209 [61153.340480] [tempesta fw] modules are stopped Apr 26 09:03:22 192.168.122.209 [61153.530313] [tempesta fw] exiting... Apr 26 09:03:23 192.168.122.209 [61153.638261] [tdb] Shutdown Tempesta DB Apr 26 09:03:23 192.168.122.209 [61153.870980] End test: http_general.test_headers.TestNoContentLengthInMethodMethodPUT.test_request_success Apr 26 09:03:23 192.168.122.209 [61153.887669] Start test: http_general.test_headers.TestSmallHeader.test_small_header_name_accepted Apr 26 09:03:24 192.168.122.209 [61154.905191] [tdb] Start Tempesta DB Apr 26 09:03:24 192.168.122.209 [61155.036500] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:03:25 192.168.122.209 [61156.367008] [tempesta fw] Configuration processing is completed. Apr 26 09:03:25 192.168.122.209 [61156.415865] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:03:25 192.168.122.209 [61156.442777] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:03:25 192.168.122.209 [61156.469366] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:03:25 192.168.122.209 [61156.530986] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:03:25 192.168.122.209 [61156.570952] [tempesta fw] Tempesta FW is ready Apr 26 09:03:26 192.168.122.209 [61157.202289] [tdb] Close table 'client0.tdb' Apr 26 09:03:26 192.168.122.209 [61157.393956] [tdb] Close table 'sessions0.tdb' Apr 26 09:03:27 192.168.122.209 [61157.607878] [tdb] Close table 'filter0.tdb' Apr 26 09:03:27 192.168.122.209 [61157.608306] [tempesta fw] modules are stopped Apr 26 09:03:27 192.168.122.209 [61157.792441] [tempesta fw] exiting... Apr 26 09:03:27 192.168.122.209 [61157.897956] [tdb] Shutdown Tempesta DB Apr 26 09:03:27 192.168.122.209 [61158.121965] End test: http_general.test_headers.TestSmallHeader.test_small_header_name_accepted Apr 26 09:03:27 192.168.122.209 [61158.130197] Start test: msg_sequence.test_pairing.PairingTestH2.test_disconnect_client Apr 26 09:03:28 192.168.122.209 [61159.188066] [tdb] Start Tempesta DB Apr 26 09:03:28 192.168.122.209 [61159.310467] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:03:29 192.168.122.209 [61159.896017] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61159.896017] Maybe that's fine, but it's worth checking the [61159.896017] config - if there is no relations between the [61159.896017] names, then host name confusion attack is possible. Apr 26 09:03:29 192.168.122.209 [61159.975064] [tempesta fw] Configuration processing is completed. Apr 26 09:03:29 192.168.122.209 [61160.030214] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:03:29 192.168.122.209 [61160.444337] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:03:29 192.168.122.209 [61160.471283] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:03:29 192.168.122.209 [61160.497532] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:03:29 192.168.122.209 [61160.543005] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:03:29 192.168.122.209 [61160.544386] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:03:30 192.168.122.209 [61160.586992] [tempesta fw] Tempesta FW is ready Apr 26 09:03:30 192.168.122.209 [61161.312738] [tdb] Close table 'client0.tdb' Apr 26 09:03:30 192.168.122.209 [61161.497019] [tdb] Close table 'sessions0.tdb' Apr 26 09:03:34 192.168.122.209 [61164.778627] [tdb] Close table 'cache0.tdb' Apr 26 09:03:34 192.168.122.209 [61165.044878] [tdb] Close table 'filter0.tdb' Apr 26 09:03:34 192.168.122.209 [61165.045312] [tempesta fw] modules are stopped Apr 26 09:03:34 192.168.122.209 [61165.233979] [tempesta fw] exiting... Apr 26 09:03:34 192.168.122.209 [61165.338372] [tdb] Shutdown Tempesta DB Apr 26 09:03:34 192.168.122.209 [61165.551820] End test: msg_sequence.test_pairing.PairingTestH2.test_disconnect_client Apr 26 09:03:34 192.168.122.209 [61165.560309] Start test: msg_sequence.test_pairing.PairingTestHttp.test_disconnect_client Apr 26 09:03:36 192.168.122.209 [61166.665152] [tdb] Start Tempesta DB Apr 26 09:03:36 192.168.122.209 [61166.803432] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:03:37 192.168.122.209 [61168.108384] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61168.108384] Maybe that's fine, but it's worth checking the [61168.108384] config - if there is no relations between the [61168.108384] names, then host name confusion attack is possible. Apr 26 09:03:37 192.168.122.209 [61168.211146] [tempesta fw] Configuration processing is completed. Apr 26 09:03:37 192.168.122.209 [61168.268085] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:03:38 192.168.122.209 [61168.680857] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:03:38 192.168.122.209 [61168.706648] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:03:38 192.168.122.209 [61168.732905] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:03:38 192.168.122.209 [61168.779113] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:03:38 192.168.122.209 [61168.780506] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:03:38 192.168.122.209 [61168.835113] [tempesta fw] Tempesta FW is ready Apr 26 09:03:38 192.168.122.209 [61169.504783] [tdb] Close table 'client0.tdb' Apr 26 09:03:39 192.168.122.209 [61169.710255] [tdb] Close table 'sessions0.tdb' Apr 26 09:03:42 192.168.122.209 [61173.023409] [tdb] Close table 'cache0.tdb' Apr 26 09:03:42 192.168.122.209 [61173.260757] [tdb] Close table 'filter0.tdb' Apr 26 09:03:42 192.168.122.209 [61173.261203] [tempesta fw] modules are stopped Apr 26 09:03:42 192.168.122.209 [61173.465697] [tempesta fw] exiting... Apr 26 09:03:43 192.168.122.209 [61173.623367] [tdb] Shutdown Tempesta DB Apr 26 09:03:43 192.168.122.209 [61173.856282] End test: msg_sequence.test_pairing.PairingTestHttp.test_disconnect_client Apr 26 09:03:43 192.168.122.209 [61173.870038] Start test: nonidempotent.test_nonidempotent.NonIdempotentH1SchedTest.test Apr 26 09:03:44 192.168.122.209 [61175.160006] [tdb] Start Tempesta DB Apr 26 09:03:44 192.168.122.209 [61175.308896] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:03:46 192.168.122.209 [61176.703253] [tempesta fw] Configuration processing is completed. Apr 26 09:03:46 192.168.122.209 [61176.760057] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:03:46 192.168.122.209 [61176.794528] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:03:46 192.168.122.209 [61176.829293] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:03:46 192.168.122.209 [61176.911228] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:03:46 192.168.122.209 [61176.959198] [tempesta fw] Tempesta FW is ready Apr 26 09:03:49 192.168.122.209 [61180.572584] [tdb] Close table 'client0.tdb' Apr 26 09:03:50 192.168.122.209 [61180.768179] [tdb] Close table 'sessions0.tdb' Apr 26 09:03:50 192.168.122.209 [61181.032669] [tdb] Close table 'filter0.tdb' Apr 26 09:03:50 192.168.122.209 [61181.033292] [tempesta fw] modules are stopped Apr 26 09:03:50 192.168.122.209 [61181.244224] [tempesta fw] exiting... Apr 26 09:03:50 192.168.122.209 [61181.396556] [tdb] Shutdown Tempesta DB Apr 26 09:03:51 192.168.122.209 [61181.622052] End test: nonidempotent.test_nonidempotent.NonIdempotentH1SchedTest.test Apr 26 09:03:51 192.168.122.209 [61181.649623] Start test: nonidempotent.test_nonidempotent.NonIdempotentH2SchedTest.test Apr 26 09:03:52 192.168.122.209 [61182.825850] [tdb] Start Tempesta DB Apr 26 09:03:52 192.168.122.209 [61182.965253] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:03:53 192.168.122.209 [61183.696714] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61183.696714] Maybe that's fine, but it's worth checking the [61183.696714] config - if there is no relations between the [61183.696714] names, then host name confusion attack is possible. Apr 26 09:03:53 192.168.122.209 [61183.843353] [tempesta fw] Configuration processing is completed. Apr 26 09:03:53 192.168.122.209 [61183.894837] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:03:53 192.168.122.209 [61183.922684] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:03:53 192.168.122.209 [61183.951794] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:03:53 192.168.122.209 [61184.031290] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:03:53 192.168.122.209 [61184.071265] [tempesta fw] Tempesta FW is ready Apr 26 09:03:57 192.168.122.209 [61187.741635] [tdb] Close table 'client0.tdb' Apr 26 09:03:57 192.168.122.209 [61187.948833] [tdb] Close table 'sessions0.tdb' Apr 26 09:03:57 192.168.122.209 [61188.197524] [tdb] Close table 'filter0.tdb' Apr 26 09:03:57 192.168.122.209 [61188.197967] [tempesta fw] modules are stopped Apr 26 09:03:57 192.168.122.209 [61188.398462] [tempesta fw] exiting... Apr 26 09:03:57 192.168.122.209 [61188.534348] [tdb] Shutdown Tempesta DB Apr 26 09:03:58 192.168.122.209 [61188.776144] End test: nonidempotent.test_nonidempotent.NonIdempotentH2SchedTest.test Apr 26 09:03:58 192.168.122.209 [61188.785571] Start test: nonidempotent.test_nonidempotent.NotRetryNonIdempotentH1Test.test Apr 26 09:03:59 192.168.122.209 [61189.769153] [tdb] Start Tempesta DB Apr 26 09:03:59 192.168.122.209 [61189.906544] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:03:59 192.168.122.209 [61190.407879] [tempesta fw] Configuration processing is completed. Apr 26 09:03:59 192.168.122.209 [61190.468719] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:03:59 192.168.122.209 [61190.499722] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:03:59 192.168.122.209 [61190.527560] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:04:00 192.168.122.209 [61190.575288] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:04:00 192.168.122.209 [61190.627372] [tempesta fw] Tempesta FW is ready Apr 26 09:04:00 192.168.122.209 [61190.775609] [tempesta fw] Warning: request dropped: non-idempotent requests aren't re-forwarded or re-scheduled, status 504: 127.0.0.2 Apr 26 09:04:00 192.168.122.209 [61191.207016] [tdb] Close table 'client0.tdb' Apr 26 09:04:00 192.168.122.209 [61191.408565] [tdb] Close table 'sessions0.tdb' Apr 26 09:04:01 192.168.122.209 [61191.652795] [tdb] Close table 'filter0.tdb' Apr 26 09:04:01 192.168.122.209 [61191.653234] [tempesta fw] modules are stopped Apr 26 09:04:01 192.168.122.209 [61191.839762] [tempesta fw] exiting... Apr 26 09:04:01 192.168.122.209 [61191.957665] [tdb] Shutdown Tempesta DB Apr 26 09:04:01 192.168.122.209 [61192.142547] End test: nonidempotent.test_nonidempotent.NotRetryNonIdempotentH1Test.test Apr 26 09:04:01 192.168.122.209 [61192.161140] Start test: nonidempotent.test_nonidempotent.NotRetryNonIdempotentH2Test.test Apr 26 09:04:02 192.168.122.209 [61193.191938] [tdb] Start Tempesta DB Apr 26 09:04:02 192.168.122.209 [61193.314800] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:04:03 192.168.122.209 [61193.916725] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61193.916725] Maybe that's fine, but it's worth checking the [61193.916725] config - if there is no relations between the [61193.916725] names, then host name confusion attack is possible. Apr 26 09:04:03 192.168.122.209 [61194.031549] [tempesta fw] Configuration processing is completed. Apr 26 09:04:03 192.168.122.209 [61194.092548] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:04:03 192.168.122.209 [61194.128597] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:04:03 192.168.122.209 [61194.173994] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:04:03 192.168.122.209 [61194.215382] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:04:03 192.168.122.209 [61194.255359] [tempesta fw] Tempesta FW is ready Apr 26 09:04:03 192.168.122.209 [61194.463550] [tempesta fw] Warning: request dropped: non-idempotent requests aren't re-forwarded or re-scheduled, status 504: 127.0.0.2 Apr 26 09:04:04 192.168.122.209 [61194.901889] [tdb] Close table 'client0.tdb' Apr 26 09:04:04 192.168.122.209 [61195.091702] [tdb] Close table 'sessions0.tdb' Apr 26 09:04:04 192.168.122.209 [61195.340933] [tdb] Close table 'filter0.tdb' Apr 26 09:04:04 192.168.122.209 [61195.341360] [tempesta fw] modules are stopped Apr 26 09:04:04 192.168.122.209 [61195.528164] [tempesta fw] exiting... Apr 26 09:04:05 192.168.122.209 [61195.656293] [tdb] Shutdown Tempesta DB Apr 26 09:04:05 192.168.122.209 [61195.852846] End test: nonidempotent.test_nonidempotent.NotRetryNonIdempotentH2Test.test Apr 26 09:04:05 192.168.122.209 [61195.868346] Start test: nonidempotent.test_nonidempotent.NotRetryNonIdempotentPostH2Test.test Apr 26 09:04:06 192.168.122.209 [61196.787458] [tdb] Start Tempesta DB Apr 26 09:04:06 192.168.122.209 [61196.924342] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:04:06 192.168.122.209 [61197.488717] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61197.488717] Maybe that's fine, but it's worth checking the [61197.488717] config - if there is no relations between the [61197.488717] names, then host name confusion attack is possible. Apr 26 09:04:07 192.168.122.209 [61197.599545] [tempesta fw] Configuration processing is completed. Apr 26 09:04:07 192.168.122.209 [61197.650777] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:04:07 192.168.122.209 [61197.679538] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:04:07 192.168.122.209 [61197.707224] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:04:07 192.168.122.209 [61197.747373] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:04:07 192.168.122.209 [61197.811470] [tempesta fw] Tempesta FW is ready Apr 26 09:04:07 192.168.122.209 [61198.003639] [tempesta fw] Warning: request dropped: non-idempotent requests aren't re-forwarded or re-scheduled, status 504: 127.0.0.2 Apr 26 09:04:07 192.168.122.209 [61198.474212] [tdb] Close table 'client0.tdb' Apr 26 09:04:08 192.168.122.209 [61198.668563] [tdb] Close table 'sessions0.tdb' Apr 26 09:04:08 192.168.122.209 [61198.913809] [tdb] Close table 'filter0.tdb' Apr 26 09:04:08 192.168.122.209 [61198.914259] [tempesta fw] modules are stopped Apr 26 09:04:08 192.168.122.209 [61199.118158] [tempesta fw] exiting... Apr 26 09:04:08 192.168.122.209 [61199.258465] [tdb] Shutdown Tempesta DB Apr 26 09:04:08 192.168.122.209 [61199.469734] End test: nonidempotent.test_nonidempotent.NotRetryNonIdempotentPostH2Test.test Apr 26 09:04:08 192.168.122.209 [61199.485111] Start test: nonidempotent.test_nonidempotent.RetryNonIdempotenRevOrderH1Test.test Apr 26 09:04:09 192.168.122.209 [61200.268067] [tdb] Start Tempesta DB Apr 26 09:04:09 192.168.122.209 [61200.411166] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:04:10 192.168.122.209 [61200.995634] [tempesta fw] Configuration processing is completed. Apr 26 09:04:10 192.168.122.209 [61201.052404] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:04:10 192.168.122.209 [61201.082831] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:04:10 192.168.122.209 [61201.111601] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:04:10 192.168.122.209 [61201.163541] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:04:10 192.168.122.209 [61201.211430] [tempesta fw] Tempesta FW is ready Apr 26 09:04:11 192.168.122.209 [61201.829566] [tdb] Close table 'client0.tdb' Apr 26 09:04:11 192.168.122.209 [61202.026335] [tdb] Close table 'sessions0.tdb' Apr 26 09:04:11 192.168.122.209 [61202.254671] [tdb] Close table 'filter0.tdb' Apr 26 09:04:11 192.168.122.209 [61202.255119] [tempesta fw] modules are stopped Apr 26 09:04:11 192.168.122.209 [61202.413203] [tempesta fw] exiting... Apr 26 09:04:11 192.168.122.209 [61202.555044] [tdb] Shutdown Tempesta DB Apr 26 09:04:12 192.168.122.209 [61202.749916] End test: nonidempotent.test_nonidempotent.RetryNonIdempotenRevOrderH1Test.test Apr 26 09:04:12 192.168.122.209 [61202.787397] Start test: nonidempotent.test_nonidempotent.RetryNonIdempotentH1Test.test Apr 26 09:04:13 192.168.122.209 [61203.766322] [tdb] Start Tempesta DB Apr 26 09:04:13 192.168.122.209 [61203.903513] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:04:13 192.168.122.209 [61204.495605] [tempesta fw] Configuration processing is completed. Apr 26 09:04:13 192.168.122.209 [61204.548458] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:04:14 192.168.122.209 [61204.576382] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:04:14 192.168.122.209 [61204.604160] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:04:14 192.168.122.209 [61204.651550] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:04:14 192.168.122.209 [61204.695471] [tempesta fw] Tempesta FW is ready Apr 26 09:04:14 192.168.122.209 [61205.255773] [tdb] Close table 'client0.tdb' Apr 26 09:04:14 192.168.122.209 [61205.457841] [tdb] Close table 'sessions0.tdb' Apr 26 09:04:15 192.168.122.209 [61205.696561] [tdb] Close table 'filter0.tdb' Apr 26 09:04:15 192.168.122.209 [61205.696996] [tempesta fw] modules are stopped Apr 26 09:04:15 192.168.122.209 [61205.875429] [tempesta fw] exiting... Apr 26 09:04:15 192.168.122.209 [61206.004021] [tdb] Shutdown Tempesta DB Apr 26 09:04:15 192.168.122.209 [61206.216720] End test: nonidempotent.test_nonidempotent.RetryNonIdempotentH1Test.test Apr 26 09:04:15 192.168.122.209 [61206.238439] Start test: nonidempotent.test_nonidempotent.RetryNonIdempotentH2Test.test Apr 26 09:04:16 192.168.122.209 [61207.257972] [tdb] Start Tempesta DB Apr 26 09:04:16 192.168.122.209 [61207.398350] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:04:17 192.168.122.209 [61208.032477] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61208.032477] Maybe that's fine, but it's worth checking the [61208.032477] config - if there is no relations between the [61208.032477] names, then host name confusion attack is possible. Apr 26 09:04:17 192.168.122.209 [61208.163674] [tempesta fw] Configuration processing is completed. Apr 26 09:04:17 192.168.122.209 [61208.221619] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:04:17 192.168.122.209 [61208.256903] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:04:17 192.168.122.209 [61208.286506] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:04:17 192.168.122.209 [61208.335629] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:04:17 192.168.122.209 [61208.375583] [tempesta fw] Tempesta FW is ready Apr 26 09:04:18 192.168.122.209 [61208.964388] [tdb] Close table 'client0.tdb' Apr 26 09:04:18 192.168.122.209 [61209.150004] [tdb] Close table 'sessions0.tdb' Apr 26 09:04:18 192.168.122.209 [61209.390741] [tdb] Close table 'filter0.tdb' Apr 26 09:04:18 192.168.122.209 [61209.391191] [tempesta fw] modules are stopped Apr 26 09:04:19 192.168.122.209 [61209.577094] [tempesta fw] exiting... Apr 26 09:04:19 192.168.122.209 [61209.683894] [tdb] Shutdown Tempesta DB Apr 26 09:04:19 192.168.122.209 [61209.891354] End test: nonidempotent.test_nonidempotent.RetryNonIdempotentH2Test.test Apr 26 09:04:19 192.168.122.209 [61209.912823] Start test: nonidempotent.test_nonidempotent.RetryNonIdempotentPostH1Test.test Apr 26 09:04:20 192.168.122.209 [61210.922639] [tdb] Start Tempesta DB Apr 26 09:04:20 192.168.122.209 [61211.059134] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:04:21 192.168.122.209 [61211.591754] [tempesta fw] Configuration processing is completed. Apr 26 09:04:21 192.168.122.209 [61211.643146] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:04:21 192.168.122.209 [61211.670835] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:04:21 192.168.122.209 [61211.697732] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:04:21 192.168.122.209 [61211.743684] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:04:21 192.168.122.209 [61211.791655] [tempesta fw] Tempesta FW is ready Apr 26 09:04:21 192.168.122.209 [61212.367046] [tdb] Close table 'client0.tdb' Apr 26 09:04:22 192.168.122.209 [61212.579502] [tdb] Close table 'sessions0.tdb' Apr 26 09:04:22 192.168.122.209 [61212.823705] [tdb] Close table 'filter0.tdb' Apr 26 09:04:22 192.168.122.209 [61212.824150] [tempesta fw] modules are stopped Apr 26 09:04:22 192.168.122.209 [61213.018746] [tempesta fw] exiting... Apr 26 09:04:22 192.168.122.209 [61213.133692] [tdb] Shutdown Tempesta DB Apr 26 09:04:22 192.168.122.209 [61213.365549] End test: nonidempotent.test_nonidempotent.RetryNonIdempotentPostH1Test.test Apr 26 09:04:22 192.168.122.209 [61213.376774] Start test: nonidempotent.test_nonidempotent.RetryNonIdempotentPostH2Test.test Apr 26 09:04:23 192.168.122.209 [61214.486326] [tdb] Start Tempesta DB Apr 26 09:04:24 192.168.122.209 [61214.620882] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:04:24 192.168.122.209 [61215.208978] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61215.208978] Maybe that's fine, but it's worth checking the [61215.208978] config - if there is no relations between the [61215.208978] names, then host name confusion attack is possible. Apr 26 09:04:24 192.168.122.209 [61215.343731] [tempesta fw] Configuration processing is completed. Apr 26 09:04:24 192.168.122.209 [61215.394999] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:04:24 192.168.122.209 [61215.422847] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:04:24 192.168.122.209 [61215.451184] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:04:24 192.168.122.209 [61215.503725] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:04:24 192.168.122.209 [61215.543679] [tempesta fw] Tempesta FW is ready Apr 26 09:04:25 192.168.122.209 [61216.180011] [tdb] Close table 'client0.tdb' Apr 26 09:04:25 192.168.122.209 [61216.367820] [tdb] Close table 'sessions0.tdb' Apr 26 09:04:26 192.168.122.209 [61216.600950] [tdb] Close table 'filter0.tdb' Apr 26 09:04:26 192.168.122.209 [61216.601386] [tempesta fw] modules are stopped Apr 26 09:04:26 192.168.122.209 [61216.831233] [tempesta fw] exiting... Apr 26 09:04:26 192.168.122.209 [61216.954925] [tdb] Shutdown Tempesta DB Apr 26 09:04:26 192.168.122.209 [61217.159042] End test: nonidempotent.test_nonidempotent.RetryNonIdempotentPostH2Test.test Apr 26 09:04:26 192.168.122.209 [61217.173838] Start test: normalization.test_http_multipart.ConfigParameterAbsent.test Apr 26 09:04:27 192.168.122.209 [61218.218008] [tdb] Start Tempesta DB Apr 26 09:04:27 192.168.122.209 [61218.355782] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:04:28 192.168.122.209 [61218.999770] [tempesta fw] Configuration processing is completed. Apr 26 09:04:28 192.168.122.209 [61219.052320] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:04:29 192.168.122.209 [61219.704824] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:04:29 192.168.122.209 [61219.753984] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:04:29 192.168.122.209 [61219.795924] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:04:29 192.168.122.209 [61219.871751] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:04:29 192.168.122.209 [61219.911669] [tempesta fw] Tempesta FW is ready Apr 26 09:04:29 192.168.122.209 [61220.461675] [tdb] Close table 'client0.tdb' Apr 26 09:04:30 192.168.122.209 [61220.652407] [tdb] Close table 'sessions0.tdb' Apr 26 09:04:33 192.168.122.209 [61223.920169] [tdb] Close table 'cache0.tdb' Apr 26 09:04:33 192.168.122.209 [61224.177731] [tdb] Close table 'filter0.tdb' Apr 26 09:04:33 192.168.122.209 [61224.178165] [tempesta fw] modules are stopped Apr 26 09:04:33 192.168.122.209 [61224.378821] [tempesta fw] exiting... Apr 26 09:04:33 192.168.122.209 [61224.482826] [tdb] Shutdown Tempesta DB Apr 26 09:04:34 192.168.122.209 [61224.733597] End test: normalization.test_http_multipart.ConfigParameterAbsent.test Apr 26 09:04:34 192.168.122.209 [61224.744628] Start test: normalization.test_http_multipart.ConfigParameterAtLocation.test Apr 26 09:04:35 192.168.122.209 [61225.806398] [tdb] Start Tempesta DB Apr 26 09:04:35 192.168.122.209 [61225.964472] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:04:36 192.168.122.209 [61227.323823] [tempesta fw] Configuration processing is completed. Apr 26 09:04:36 192.168.122.209 [61227.376508] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:04:37 192.168.122.209 [61227.794849] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:04:37 192.168.122.209 [61227.821209] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:04:37 192.168.122.209 [61227.849879] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:04:37 192.168.122.209 [61227.959883] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:04:37 192.168.122.209 [61228.015855] [tempesta fw] Tempesta FW is ready Apr 26 09:04:37 192.168.122.209 [61228.554863] [tdb] Close table 'client0.tdb' Apr 26 09:04:38 192.168.122.209 [61228.746518] [tdb] Close table 'sessions0.tdb' Apr 26 09:04:41 192.168.122.209 [61231.987163] [tdb] Close table 'cache0.tdb' Apr 26 09:04:41 192.168.122.209 [61232.245734] [tdb] Close table 'filter0.tdb' Apr 26 09:04:41 192.168.122.209 [61232.246175] [tempesta fw] modules are stopped Apr 26 09:04:41 192.168.122.209 [61232.422920] [tempesta fw] exiting... Apr 26 09:04:41 192.168.122.209 [61232.568864] [tdb] Shutdown Tempesta DB Apr 26 09:04:42 192.168.122.209 [61232.779126] End test: normalization.test_http_multipart.ConfigParameterAtLocation.test Apr 26 09:04:42 192.168.122.209 [61232.800592] Start test: normalization.test_http_multipart.ConfigParameterAtTopLevel.test Apr 26 09:04:43 192.168.122.209 [61233.912749] [tdb] Start Tempesta DB Apr 26 09:04:43 192.168.122.209 [61234.054725] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:04:44 192.168.122.209 [61235.451977] [tempesta fw] Configuration processing is completed. Apr 26 09:04:44 192.168.122.209 [61235.502920] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:04:45 192.168.122.209 [61235.918245] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:04:45 192.168.122.209 [61235.953916] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:04:45 192.168.122.209 [61235.986661] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:04:45 192.168.122.209 [61236.035970] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:04:45 192.168.122.209 [61236.079848] [tempesta fw] Tempesta FW is ready Apr 26 09:04:46 192.168.122.209 [61236.657804] [tdb] Close table 'client0.tdb' Apr 26 09:04:46 192.168.122.209 [61236.868783] [tdb] Close table 'sessions0.tdb' Apr 26 09:04:49 192.168.122.209 [61240.111346] [tdb] Close table 'cache0.tdb' Apr 26 09:04:49 192.168.122.209 [61240.355692] [tdb] Close table 'filter0.tdb' Apr 26 09:04:49 192.168.122.209 [61240.356151] [tempesta fw] modules are stopped Apr 26 09:04:49 192.168.122.209 [61240.524035] [tempesta fw] exiting... Apr 26 09:04:50 192.168.122.209 [61240.633513] [tdb] Shutdown Tempesta DB Apr 26 09:04:50 192.168.122.209 [61240.883426] End test: normalization.test_http_multipart.ConfigParameterAtTopLevel.test Apr 26 09:04:50 192.168.122.209 [61240.894509] Start test: normalization.test_http_multipart.ConfigParameterAtVhost.test Apr 26 09:04:51 192.168.122.209 [61241.873867] [tdb] Start Tempesta DB Apr 26 09:04:51 192.168.122.209 [61242.005146] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:04:52 192.168.122.209 [61243.412028] [tempesta fw] Configuration processing is completed. Apr 26 09:04:52 192.168.122.209 [61243.462592] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:04:53 192.168.122.209 [61243.877497] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:04:53 192.168.122.209 [61243.903294] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:04:53 192.168.122.209 [61243.928983] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:04:53 192.168.122.209 [61243.976049] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:04:53 192.168.122.209 [61244.015984] [tempesta fw] Tempesta FW is ready Apr 26 09:04:54 192.168.122.209 [61244.590649] [tdb] Close table 'client0.tdb' Apr 26 09:04:54 192.168.122.209 [61244.783655] [tdb] Close table 'sessions0.tdb' Apr 26 09:04:57 192.168.122.209 [61248.000547] [tdb] Close table 'cache0.tdb' Apr 26 09:04:57 192.168.122.209 [61248.243120] [tdb] Close table 'filter0.tdb' Apr 26 09:04:57 192.168.122.209 [61248.243566] [tempesta fw] modules are stopped Apr 26 09:04:57 192.168.122.209 [61248.411862] [tempesta fw] exiting... Apr 26 09:04:57 192.168.122.209 [61248.536527] [tdb] Shutdown Tempesta DB Apr 26 09:04:58 192.168.122.209 [61248.760159] End test: normalization.test_http_multipart.ConfigParameterAtVhost.test Apr 26 09:04:58 192.168.122.209 [61248.772453] Start test: normalization.test_http_multipart.ContentTypeHeaderReconstructTest.test_replacement_escaped Apr 26 09:04:59 192.168.122.209 [61249.812775] [tdb] Start Tempesta DB Apr 26 09:04:59 192.168.122.209 [61249.947216] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:05:00 192.168.122.209 [61251.344197] [tempesta fw] Configuration processing is completed. Apr 26 09:05:00 192.168.122.209 [61251.396159] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:05:01 192.168.122.209 [61251.803363] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:05:01 192.168.122.209 [61251.829103] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:05:01 192.168.122.209 [61251.860629] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:05:01 192.168.122.209 [61251.964201] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:05:01 192.168.122.209 [61252.004147] [tempesta fw] Tempesta FW is ready Apr 26 09:05:01 192.168.122.209 [61252.559852] [tdb] Close table 'client0.tdb' Apr 26 09:05:02 192.168.122.209 [61252.733973] [tdb] Close table 'sessions0.tdb' Apr 26 09:05:05 192.168.122.209 [61255.968404] [tdb] Close table 'cache0.tdb' Apr 26 09:05:05 192.168.122.209 [61256.232821] [tdb] Close table 'filter0.tdb' Apr 26 09:05:05 192.168.122.209 [61256.233273] [tempesta fw] modules are stopped Apr 26 09:05:05 192.168.122.209 [61256.390168] [tempesta fw] exiting... Apr 26 09:05:05 192.168.122.209 [61256.494591] [tdb] Shutdown Tempesta DB Apr 26 09:05:06 192.168.122.209 [61256.693806] End test: normalization.test_http_multipart.ContentTypeHeaderReconstructTest.test_replacement_escaped Apr 26 09:05:06 192.168.122.209 [61256.705713] Start test: normalization.test_http_multipart.ContentTypeHeaderReconstructTest.test_replacement_quoted Apr 26 09:05:07 192.168.122.209 [61257.760828] [tdb] Start Tempesta DB Apr 26 09:05:07 192.168.122.209 [61257.923884] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:05:08 192.168.122.209 [61259.356227] [tempesta fw] Configuration processing is completed. Apr 26 09:05:08 192.168.122.209 [61259.411093] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:05:09 192.168.122.209 [61259.829548] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:05:09 192.168.122.209 [61259.859414] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:05:09 192.168.122.209 [61259.889631] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:05:09 192.168.122.209 [61259.976296] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:05:09 192.168.122.209 [61260.016234] [tempesta fw] Tempesta FW is ready Apr 26 09:05:14 192.168.122.209 [61265.329664] [tdb] Close table 'client0.tdb' Apr 26 09:05:14 192.168.122.209 [61265.521276] [tdb] Close table 'sessions0.tdb' Apr 26 09:05:19 192.168.122.209 [61269.592147] [tdb] Close table 'cache0.tdb' Apr 26 09:05:19 192.168.122.209 [61270.178291] [tdb] Close table 'filter0.tdb' Apr 26 09:05:19 192.168.122.209 [61270.178745] [tempesta fw] modules are stopped Apr 26 09:05:20 192.168.122.209 [61271.407205] [tempesta fw] exiting... Apr 26 09:05:21 192.168.122.209 [61271.938053] [tdb] Shutdown Tempesta DB Apr 26 09:05:21 192.168.122.209 [61272.458985] End test: normalization.test_http_multipart.ContentTypeHeaderReconstructTest.test_replacement_quoted Apr 26 09:05:21 192.168.122.209 [61272.467885] Start test: normalization.test_http_multipart.ContentTypeHeaderReconstructTest.test_replacement_unquoted_1 Apr 26 09:05:22 192.168.122.209 [61273.443075] [tdb] Start Tempesta DB Apr 26 09:05:23 192.168.122.209 [61273.586309] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:05:24 192.168.122.209 [61275.088756] [tempesta fw] Configuration processing is completed. Apr 26 09:05:24 192.168.122.209 [61275.160647] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:05:25 192.168.122.209 [61275.589891] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:05:25 192.168.122.209 [61275.624425] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:05:25 192.168.122.209 [61275.660809] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:05:25 192.168.122.209 [61275.704473] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:05:25 192.168.122.209 [61275.748470] [tempesta fw] Tempesta FW is ready Apr 26 09:05:30 192.168.122.209 [61281.179094] [tdb] Close table 'client0.tdb' Apr 26 09:05:30 192.168.122.209 [61281.385741] [tdb] Close table 'sessions0.tdb' Apr 26 09:05:34 192.168.122.209 [61284.696609] [tdb] Close table 'cache0.tdb' Apr 26 09:05:34 192.168.122.209 [61284.955859] [tdb] Close table 'filter0.tdb' Apr 26 09:05:34 192.168.122.209 [61284.956309] [tempesta fw] modules are stopped Apr 26 09:05:34 192.168.122.209 [61285.133306] [tempesta fw] exiting... Apr 26 09:05:34 192.168.122.209 [61285.334284] [tdb] Shutdown Tempesta DB Apr 26 09:05:34 192.168.122.209 [61285.521218] End test: normalization.test_http_multipart.ContentTypeHeaderReconstructTest.test_replacement_unquoted_1 Apr 26 09:05:34 192.168.122.209 [61285.535646] Start test: normalization.test_http_multipart.ContentTypeHeaderReconstructTest.test_replacement_unquoted_2 Apr 26 09:05:35 192.168.122.209 [61286.569260] [tdb] Start Tempesta DB Apr 26 09:05:36 192.168.122.209 [61286.711537] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:05:37 192.168.122.209 [61288.064667] [tempesta fw] Configuration processing is completed. Apr 26 09:05:37 192.168.122.209 [61288.118294] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:05:38 192.168.122.209 [61288.587863] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:05:38 192.168.122.209 [61288.617276] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:05:38 192.168.122.209 [61288.646573] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:05:38 192.168.122.209 [61288.696685] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:05:38 192.168.122.209 [61288.744562] [tempesta fw] Tempesta FW is ready Apr 26 09:05:43 192.168.122.209 [61294.151469] [tdb] Close table 'client0.tdb' Apr 26 09:05:43 192.168.122.209 [61294.344086] [tdb] Close table 'sessions0.tdb' Apr 26 09:05:47 192.168.122.209 [61297.739959] [tdb] Close table 'cache0.tdb' Apr 26 09:05:47 192.168.122.209 [61297.967174] [tdb] Close table 'filter0.tdb' Apr 26 09:05:47 192.168.122.209 [61297.967623] [tempesta fw] modules are stopped Apr 26 09:05:47 192.168.122.209 [61298.147989] [tempesta fw] exiting... Apr 26 09:05:47 192.168.122.209 [61298.278061] [tdb] Shutdown Tempesta DB Apr 26 09:05:47 192.168.122.209 [61298.475953] End test: normalization.test_http_multipart.ContentTypeHeaderReconstructTest.test_replacement_unquoted_2 Apr 26 09:05:47 192.168.122.209 [61298.491407] Start test: sessions.test_cookies.CookieLifetime.test_cookie Apr 26 09:05:48 192.168.122.209 [61299.526359] [tdb] Start Tempesta DB Apr 26 09:05:49 192.168.122.209 [61299.670910] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:05:50 192.168.122.209 [61301.172783] [tempesta fw] Configuration processing is completed. Apr 26 09:05:50 192.168.122.209 [61301.226187] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:05:51 192.168.122.209 [61301.664293] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:05:51 192.168.122.209 [61301.694230] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:05:51 192.168.122.209 [61301.725872] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:05:51 192.168.122.209 [61301.812744] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:05:51 192.168.122.209 [61301.852812] [tempesta fw] Tempesta FW is ready Apr 26 09:05:56 192.168.122.209 [61307.080697] [tempesta fw] Warning: http_sess: sticky cookie value expired for 127.0.0.2 (issued=4310217274 lifetime=500 now=4310218544) Apr 26 09:05:56 192.168.122.209 [61307.575482] [tdb] Close table 'client0.tdb' Apr 26 09:05:57 192.168.122.209 [61307.749744] [tdb] Close table 'sessions0.tdb' Apr 26 09:06:00 192.168.122.209 [61311.065102] [tdb] Close table 'cache0.tdb' Apr 26 09:06:00 192.168.122.209 [61311.320612] [tdb] Close table 'filter0.tdb' Apr 26 09:06:00 192.168.122.209 [61311.321078] [tempesta fw] modules are stopped Apr 26 09:06:00 192.168.122.209 [61311.511479] [tempesta fw] exiting... Apr 26 09:06:01 192.168.122.209 [61311.639913] [tdb] Shutdown Tempesta DB Apr 26 09:06:01 192.168.122.209 [61311.862167] End test: sessions.test_cookies.CookieLifetime.test_cookie Apr 26 09:06:01 192.168.122.209 [61311.876255] Start test: sessions.test_cookies.CookiesEnabled.test_cookie Apr 26 09:06:02 192.168.122.209 [61312.975170] [tdb] Start Tempesta DB Apr 26 09:06:02 192.168.122.209 [61313.141481] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:06:04 192.168.122.209 [61314.589040] [tempesta fw] Configuration processing is completed. Apr 26 09:06:04 192.168.122.209 [61314.649173] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:06:04 192.168.122.209 [61315.095586] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:06:04 192.168.122.209 [61315.122865] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:06:04 192.168.122.209 [61315.149886] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:06:04 192.168.122.209 [61315.196869] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:06:04 192.168.122.209 [61315.240946] [tempesta fw] Tempesta FW is ready Apr 26 09:06:05 192.168.122.209 [61315.904228] [tdb] Close table 'client0.tdb' Apr 26 09:06:05 192.168.122.209 [61316.090736] [tdb] Close table 'sessions0.tdb' Apr 26 09:06:08 192.168.122.209 [61319.427685] [tdb] Close table 'cache0.tdb' Apr 26 09:06:09 192.168.122.209 [61319.670196] [tdb] Close table 'filter0.tdb' Apr 26 09:06:09 192.168.122.209 [61319.670642] [tempesta fw] modules are stopped Apr 26 09:06:09 192.168.122.209 [61319.911173] [tempesta fw] exiting... Apr 26 09:06:09 192.168.122.209 [61320.049203] [tdb] Shutdown Tempesta DB Apr 26 09:06:09 192.168.122.209 [61320.241838] End test: sessions.test_cookies.CookiesEnabled.test_cookie Apr 26 09:06:09 192.168.122.209 [61320.251975] Start test: sessions.test_cookies.CookiesEnforced.test_cookie Apr 26 09:06:10 192.168.122.209 [61321.339677] [tdb] Start Tempesta DB Apr 26 09:06:10 192.168.122.209 [61321.476972] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:06:12 192.168.122.209 [61322.937156] [tempesta fw] Configuration processing is completed. Apr 26 09:06:12 192.168.122.209 [61322.991048] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:06:12 192.168.122.209 [61323.411890] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:06:12 192.168.122.209 [61323.438840] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:06:12 192.168.122.209 [61323.473139] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:06:12 192.168.122.209 [61323.537015] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:06:13 192.168.122.209 [61323.605057] [tempesta fw] Tempesta FW is ready Apr 26 09:06:13 192.168.122.209 [61324.353685] [tdb] Close table 'client0.tdb' Apr 26 09:06:13 192.168.122.209 [61324.543033] [tdb] Close table 'sessions0.tdb' Apr 26 09:06:17 192.168.122.209 [61327.966078] [tdb] Close table 'cache0.tdb' Apr 26 09:06:17 192.168.122.209 [61328.229451] [tdb] Close table 'filter0.tdb' Apr 26 09:06:17 192.168.122.209 [61328.229899] [tempesta fw] modules are stopped Apr 26 09:06:17 192.168.122.209 [61328.412796] [tempesta fw] exiting... Apr 26 09:06:17 192.168.122.209 [61328.540407] [tdb] Shutdown Tempesta DB Apr 26 09:06:18 192.168.122.209 [61328.733971] End test: sessions.test_cookies.CookiesEnforced.test_cookie Apr 26 09:06:18 192.168.122.209 [61328.752749] Start test: sessions.test_cookies.CookiesInherit.test_cookie Apr 26 09:06:19 192.168.122.209 [61329.814884] [tdb] Start Tempesta DB Apr 26 09:06:19 192.168.122.209 [61329.955500] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:06:21 192.168.122.209 [61332.485372] [tempesta fw] Configuration processing is completed. Apr 26 09:06:21 192.168.122.209 [61332.537971] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:06:22 192.168.122.209 [61333.012081] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:06:22 192.168.122.209 [61333.048072] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:06:22 192.168.122.209 [61333.076669] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:06:22 192.168.122.209 [61333.161219] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:06:22 192.168.122.209 [61333.213166] [tempesta fw] Tempesta FW is ready Apr 26 09:06:23 192.168.122.209 [61334.456883] [tdb] Close table 'client0.tdb' Apr 26 09:06:24 192.168.122.209 [61334.664621] [tdb] Close table 'sessions0.tdb' Apr 26 09:06:27 192.168.122.209 [61338.084013] [tdb] Close table 'cache0.tdb' Apr 26 09:06:27 192.168.122.209 [61338.342021] [tdb] Close table 'filter0.tdb' Apr 26 09:06:27 192.168.122.209 [61338.342461] [tempesta fw] modules are stopped Apr 26 09:06:28 192.168.122.209 [61338.586497] [tempesta fw] exiting... Apr 26 09:06:28 192.168.122.209 [61338.729304] [tdb] Shutdown Tempesta DB Apr 26 09:06:28 192.168.122.209 [61338.954969] End test: sessions.test_cookies.CookiesInherit.test_cookie Apr 26 09:06:28 192.168.122.209 [61338.973731] Start test: sessions.test_cookies.CookiesMaxMisses.test_max_misses__no_cookie Apr 26 09:06:29 192.168.122.209 [61340.006829] [tdb] Start Tempesta DB Apr 26 09:06:29 192.168.122.209 [61340.138828] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:06:30 192.168.122.209 [61341.533387] [tempesta fw] Configuration processing is completed. Apr 26 09:06:31 192.168.122.209 [61341.588385] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:06:31 192.168.122.209 [61342.002205] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:06:31 192.168.122.209 [61342.031962] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:06:31 192.168.122.209 [61342.058793] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:06:31 192.168.122.209 [61342.105358] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:06:31 192.168.122.209 [61342.153291] [tempesta fw] Tempesta FW is ready Apr 26 09:06:31 192.168.122.209 [61342.318864] [tempesta fw] Warning: frang: max rmisses exceeded for 127.0.0.2: 3 (lim=2) Apr 26 09:06:32 192.168.122.209 [61342.758945] [tdb] Close table 'client0.tdb' Apr 26 09:06:32 192.168.122.209 [61342.946453] [tdb] Close table 'sessions0.tdb' Apr 26 09:06:35 192.168.122.209 [61346.241879] [tdb] Close table 'cache0.tdb' Apr 26 09:06:35 192.168.122.209 [61346.492472] [tdb] Close table 'filter0.tdb' Apr 26 09:06:35 192.168.122.209 [61346.492916] [tempesta fw] modules are stopped Apr 26 09:06:36 192.168.122.209 [61346.645945] [tempesta fw] exiting... Apr 26 09:06:36 192.168.122.209 [61346.782734] [tdb] Shutdown Tempesta DB Apr 26 09:06:36 192.168.122.209 [61346.990612] End test: sessions.test_cookies.CookiesMaxMisses.test_max_misses__no_cookie Apr 26 09:06:36 192.168.122.209 [61347.000555] Start test: sessions.test_cookies.CookiesMaxMisses.test_max_misses__with_invalid_cookie Apr 26 09:06:37 192.168.122.209 [61348.075304] [tdb] Start Tempesta DB Apr 26 09:06:37 192.168.122.209 [61348.216232] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:06:39 192.168.122.209 [61349.617446] [tempesta fw] Configuration processing is completed. Apr 26 09:06:39 192.168.122.209 [61349.668817] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:06:39 192.168.122.209 [61350.101527] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:06:39 192.168.122.209 [61350.128569] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:06:39 192.168.122.209 [61350.162454] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:06:39 192.168.122.209 [61350.241436] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:06:39 192.168.122.209 [61350.305343] [tempesta fw] Tempesta FW is ready Apr 26 09:06:39 192.168.122.209 [61350.445021] [tempesta fw] Warning: http_sess: bad sticky cookie length for 127.0.0.2 22(56) Apr 26 09:06:39 192.168.122.209 [61350.470081] [tempesta fw] Warning: http_sess: bad sticky cookie length for 127.0.0.2 22(56) Apr 26 09:06:39 192.168.122.209 [61350.484741] [tempesta fw] Warning: http_sess: bad sticky cookie length for 127.0.0.2 22(56) Apr 26 09:06:39 192.168.122.209 [61350.485521] [tempesta fw] Warning: frang: max rmisses exceeded for 127.0.0.2: 3 (lim=2) Apr 26 09:06:40 192.168.122.209 [61350.931521] [tdb] Close table 'client0.tdb' Apr 26 09:06:40 192.168.122.209 [61351.120523] [tdb] Close table 'sessions0.tdb' Apr 26 09:06:43 192.168.122.209 [61354.395092] [tdb] Close table 'cache0.tdb' Apr 26 09:06:44 192.168.122.209 [61354.640833] [tdb] Close table 'filter0.tdb' Apr 26 09:06:44 192.168.122.209 [61354.641316] [tempesta fw] modules are stopped Apr 26 09:06:44 192.168.122.209 [61354.815617] [tempesta fw] exiting... Apr 26 09:06:44 192.168.122.209 [61354.924625] [tdb] Shutdown Tempesta DB Apr 26 09:06:44 192.168.122.209 [61355.158112] End test: sessions.test_cookies.CookiesMaxMisses.test_max_misses__with_invalid_cookie Apr 26 09:06:44 192.168.122.209 [61355.172088] Start test: sessions.test_cookies.CookiesNotEnabled.test_cookie Apr 26 09:06:45 192.168.122.209 [61356.219386] [tdb] Start Tempesta DB Apr 26 09:06:45 192.168.122.209 [61356.354440] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:06:47 192.168.122.209 [61357.737549] [tempesta fw] Configuration processing is completed. Apr 26 09:06:47 192.168.122.209 [61357.794987] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:06:47 192.168.122.209 [61358.279612] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:06:47 192.168.122.209 [61358.311654] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:06:47 192.168.122.209 [61358.346337] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:06:47 192.168.122.209 [61358.409484] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:06:47 192.168.122.209 [61358.449529] [tempesta fw] Tempesta FW is ready Apr 26 09:06:48 192.168.122.209 [61359.165025] [tdb] Close table 'client0.tdb' Apr 26 09:06:48 192.168.122.209 [61359.350426] [tdb] Close table 'sessions0.tdb' Apr 26 09:06:51 192.168.122.209 [61362.565367] [tdb] Close table 'cache0.tdb' Apr 26 09:06:52 192.168.122.209 [61362.823090] [tdb] Close table 'filter0.tdb' Apr 26 09:06:52 192.168.122.209 [61362.823529] [tempesta fw] modules are stopped Apr 26 09:06:52 192.168.122.209 [61362.981611] [tempesta fw] exiting... Apr 26 09:06:52 192.168.122.209 [61363.083526] [tdb] Shutdown Tempesta DB Apr 26 09:06:52 192.168.122.209 [61363.293004] End test: sessions.test_cookies.CookiesNotEnabled.test_cookie Apr 26 09:06:52 192.168.122.209 [61363.309934] Start test: sessions.test_cookies.StickyCookieOptions.test_cookie_options_all_in_one Apr 26 09:06:53 192.168.122.209 [61364.363190] [tdb] Start Tempesta DB Apr 26 09:06:53 192.168.122.209 [61364.515793] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:06:56 192.168.122.209 [61366.605544] [tempesta fw] Configuration processing is completed. Apr 26 09:06:56 192.168.122.209 [61366.663869] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:06:56 192.168.122.209 [61367.105657] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:06:56 192.168.122.209 [61367.132961] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:06:56 192.168.122.209 [61367.161298] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:06:56 192.168.122.209 [61367.249724] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:06:56 192.168.122.209 [61367.313651] [tempesta fw] Tempesta FW is ready Apr 26 09:06:57 192.168.122.209 [61367.944108] [tdb] Close table 'client0.tdb' Apr 26 09:06:57 192.168.122.209 [61368.126280] [tdb] Close table 'sessions0.tdb' Apr 26 09:07:00 192.168.122.209 [61371.529841] [tdb] Close table 'cache0.tdb' Apr 26 09:07:01 192.168.122.209 [61371.790950] [tdb] Close table 'filter0.tdb' Apr 26 09:07:01 192.168.122.209 [61371.791405] [tempesta fw] modules are stopped Apr 26 09:07:01 192.168.122.209 [61372.034229] [tempesta fw] exiting... Apr 26 09:07:01 192.168.122.209 [61372.189944] [tdb] Shutdown Tempesta DB Apr 26 09:07:01 192.168.122.209 [61372.411016] End test: sessions.test_cookies.StickyCookieOptions.test_cookie_options_all_in_one Apr 26 09:07:01 192.168.122.209 [61372.433264] Start test: sessions.test_cookies.StickyCookieOptions.test_empty_options Apr 26 09:07:02 192.168.122.209 [61373.501903] [tdb] Start Tempesta DB Apr 26 09:07:03 192.168.122.209 [61373.630189] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:07:05 192.168.122.209 [61375.673817] [tempesta fw] Configuration processing is completed. Apr 26 09:07:05 192.168.122.209 [61375.725538] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:07:05 192.168.122.209 [61376.226877] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:07:05 192.168.122.209 [61376.263405] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:07:05 192.168.122.209 [61376.300787] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:07:05 192.168.122.209 [61376.381778] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:07:05 192.168.122.209 [61376.421758] [tempesta fw] Tempesta FW is ready Apr 26 09:07:06 192.168.122.209 [61377.013530] [tdb] Close table 'client0.tdb' Apr 26 09:07:06 192.168.122.209 [61377.217899] [tdb] Close table 'sessions0.tdb' Apr 26 09:07:09 192.168.122.209 [61380.493968] [tdb] Close table 'cache0.tdb' Apr 26 09:07:10 192.168.122.209 [61380.750095] [tdb] Close table 'filter0.tdb' Apr 26 09:07:10 192.168.122.209 [61380.750547] [tempesta fw] modules are stopped Apr 26 09:07:10 192.168.122.209 [61380.973816] [tempesta fw] exiting... Apr 26 09:07:10 192.168.122.209 [61381.094320] [tdb] Shutdown Tempesta DB Apr 26 09:07:10 192.168.122.209 [61381.318789] End test: sessions.test_cookies.StickyCookieOptions.test_empty_options Apr 26 09:07:10 192.168.122.209 [61381.327730] Start test: sessions.test_cookies.StickyCookieOptions.test_empty_options_1 Apr 26 09:07:11 192.168.122.209 [61382.333858] [tdb] Start Tempesta DB Apr 26 09:07:11 192.168.122.209 [61382.482965] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:07:13 192.168.122.209 [61384.377902] [tempesta fw] Configuration processing is completed. Apr 26 09:07:13 192.168.122.209 [61384.435454] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:07:14 192.168.122.209 [61384.857834] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:07:14 192.168.122.209 [61384.884092] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:07:14 192.168.122.209 [61384.910067] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:07:14 192.168.122.209 [61384.997879] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:07:14 192.168.122.209 [61385.039142] [tempesta fw] Tempesta FW is ready Apr 26 09:07:15 192.168.122.209 [61385.645245] [tdb] Close table 'client0.tdb' Apr 26 09:07:15 192.168.122.209 [61385.856841] [tdb] Close table 'sessions0.tdb' Apr 26 09:07:18 192.168.122.209 [61389.050365] [tdb] Close table 'cache0.tdb' Apr 26 09:07:18 192.168.122.209 [61389.310683] [tdb] Close table 'filter0.tdb' Apr 26 09:07:18 192.168.122.209 [61389.311148] [tempesta fw] modules are stopped Apr 26 09:07:18 192.168.122.209 [61389.502143] [tempesta fw] exiting... Apr 26 09:07:19 192.168.122.209 [61389.646424] [tdb] Shutdown Tempesta DB Apr 26 09:07:19 192.168.122.209 [61389.846839] End test: sessions.test_cookies.StickyCookieOptions.test_empty_options_1 Apr 26 09:07:19 192.168.122.209 [61389.859460] Start test: sessions.test_cookies.StickyCookieOptions.test_empty_vhost_global_expires_and_sess_lifetime_are_set Apr 26 09:07:20 192.168.122.209 [61390.962941] [tdb] Start Tempesta DB Apr 26 09:07:20 192.168.122.209 [61391.097922] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:07:22 192.168.122.209 [61392.994079] [tempesta fw] Configuration processing is completed. Apr 26 09:07:22 192.168.122.209 [61393.050064] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:07:22 192.168.122.209 [61393.463980] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:07:22 192.168.122.209 [61393.490645] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:07:22 192.168.122.209 [61393.517144] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:07:23 192.168.122.209 [61393.605994] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:07:23 192.168.122.209 [61393.693975] [tempesta fw] Tempesta FW is ready Apr 26 09:07:23 192.168.122.209 [61394.340949] [tdb] Close table 'client0.tdb' Apr 26 09:07:23 192.168.122.209 [61394.532484] [tdb] Close table 'sessions0.tdb' Apr 26 09:07:27 192.168.122.209 [61397.714893] [tdb] Close table 'cache0.tdb' Apr 26 09:07:27 192.168.122.209 [61397.971415] [tdb] Close table 'filter0.tdb' Apr 26 09:07:27 192.168.122.209 [61397.971863] [tempesta fw] modules are stopped Apr 26 09:07:27 192.168.122.209 [61398.212496] [tempesta fw] exiting... Apr 26 09:07:27 192.168.122.209 [61398.353637] [tdb] Shutdown Tempesta DB Apr 26 09:07:27 192.168.122.209 [61398.527797] End test: sessions.test_cookies.StickyCookieOptions.test_empty_vhost_global_expires_and_sess_lifetime_are_set Apr 26 09:07:27 192.168.122.209 [61398.534459] Start test: sessions.test_cookies.StickyCookieOptions.test_empty_vhost_global_sess_lifetime_is_set Apr 26 09:07:29 192.168.122.209 [61399.594535] [tdb] Start Tempesta DB Apr 26 09:07:29 192.168.122.209 [61399.729284] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:07:31 192.168.122.209 [61401.742115] [tempesta fw] Configuration processing is completed. Apr 26 09:07:31 192.168.122.209 [61401.794266] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:07:31 192.168.122.209 [61402.207128] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:07:31 192.168.122.209 [61402.233669] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:07:31 192.168.122.209 [61402.261104] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:07:31 192.168.122.209 [61402.350084] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:07:31 192.168.122.209 [61402.390617] [tempesta fw] Tempesta FW is ready Apr 26 09:07:32 192.168.122.209 [61402.982848] [tdb] Close table 'client0.tdb' Apr 26 09:07:32 192.168.122.209 [61403.169542] [tdb] Close table 'sessions0.tdb' Apr 26 09:07:35 192.168.122.209 [61406.484868] [tdb] Close table 'cache0.tdb' Apr 26 09:07:36 192.168.122.209 [61406.699978] [tdb] Close table 'filter0.tdb' Apr 26 09:07:36 192.168.122.209 [61406.700422] [tempesta fw] modules are stopped Apr 26 09:07:36 192.168.122.209 [61406.932332] [tempesta fw] exiting... Apr 26 09:07:36 192.168.122.209 [61407.054831] [tdb] Shutdown Tempesta DB Apr 26 09:07:36 192.168.122.209 [61407.251468] End test: sessions.test_cookies.StickyCookieOptions.test_empty_vhost_global_sess_lifetime_is_set Apr 26 09:07:36 192.168.122.209 [61407.270996] Start test: sessions.test_cookies.StickyCookieOptions.test_vhost_and_global_options_other Apr 26 09:07:37 192.168.122.209 [61408.255150] [tdb] Start Tempesta DB Apr 26 09:07:37 192.168.122.209 [61408.385579] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:07:39 192.168.122.209 [61410.178233] [tempesta fw] Configuration processing is completed. Apr 26 09:07:39 192.168.122.209 [61410.233963] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:07:40 192.168.122.209 [61410.650722] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:07:40 192.168.122.209 [61410.676646] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:07:40 192.168.122.209 [61410.702336] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:07:40 192.168.122.209 [61410.790051] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:07:40 192.168.122.209 [61410.830045] [tempesta fw] Tempesta FW is ready Apr 26 09:07:40 192.168.122.209 [61411.409958] [tdb] Close table 'client0.tdb' Apr 26 09:07:41 192.168.122.209 [61411.602417] [tdb] Close table 'sessions0.tdb' Apr 26 09:07:44 192.168.122.209 [61414.895758] [tdb] Close table 'cache0.tdb' Apr 26 09:07:44 192.168.122.209 [61415.162341] [tdb] Close table 'filter0.tdb' Apr 26 09:07:44 192.168.122.209 [61415.162781] [tempesta fw] modules are stopped Apr 26 09:07:44 192.168.122.209 [61415.365711] [tempesta fw] exiting... Apr 26 09:07:44 192.168.122.209 [61415.507651] [tdb] Shutdown Tempesta DB Apr 26 09:07:45 192.168.122.209 [61415.729719] End test: sessions.test_cookies.StickyCookieOptions.test_vhost_and_global_options_other Apr 26 09:07:45 192.168.122.209 [61415.741922] Start test: sessions.test_cookies.StickyCookieOptions.test_vhost_expires_is_set Apr 26 09:07:46 192.168.122.209 [61416.820332] [tdb] Start Tempesta DB Apr 26 09:07:46 192.168.122.209 [61416.948194] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:07:48 192.168.122.209 [61418.814194] [tempesta fw] Configuration processing is completed. Apr 26 09:07:48 192.168.122.209 [61418.869619] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:07:48 192.168.122.209 [61419.277977] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:07:48 192.168.122.209 [61419.314684] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:07:48 192.168.122.209 [61419.341229] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:07:48 192.168.122.209 [61419.434331] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:07:48 192.168.122.209 [61419.482277] [tempesta fw] Tempesta FW is ready Apr 26 09:07:49 192.168.122.209 [61420.099577] [tdb] Close table 'client0.tdb' Apr 26 09:07:49 192.168.122.209 [61420.307284] [tdb] Close table 'sessions0.tdb' Apr 26 09:07:52 192.168.122.209 [61423.542065] [tdb] Close table 'cache0.tdb' Apr 26 09:07:53 192.168.122.209 [61423.783149] [tdb] Close table 'filter0.tdb' Apr 26 09:07:53 192.168.122.209 [61423.783598] [tempesta fw] modules are stopped Apr 26 09:07:53 192.168.122.209 [61423.978621] [tempesta fw] exiting... Apr 26 09:07:53 192.168.122.209 [61424.102461] [tdb] Shutdown Tempesta DB Apr 26 09:07:53 192.168.122.209 [61424.298095] End test: sessions.test_cookies.StickyCookieOptions.test_vhost_expires_is_set Apr 26 09:07:53 192.168.122.209 [61424.310059] Start test: sessions.test_cookies.StickyCookieOptions.test_vhost_max_age_is_set Apr 26 09:07:54 192.168.122.209 [61425.360314] [tdb] Start Tempesta DB Apr 26 09:07:54 192.168.122.209 [61425.497594] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:07:56 192.168.122.209 [61427.418423] [tempesta fw] Configuration processing is completed. Apr 26 09:07:56 192.168.122.209 [61427.470567] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:07:57 192.168.122.209 [61427.888055] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:07:57 192.168.122.209 [61427.923301] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:07:57 192.168.122.209 [61427.948961] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:07:57 192.168.122.209 [61428.074455] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:07:57 192.168.122.209 [61428.154376] [tempesta fw] Tempesta FW is ready Apr 26 09:07:58 192.168.122.209 [61428.783372] [tdb] Close table 'client0.tdb' Apr 26 09:07:58 192.168.122.209 [61428.972246] [tdb] Close table 'sessions0.tdb' Apr 26 09:08:01 192.168.122.209 [61432.173663] [tdb] Close table 'cache0.tdb' Apr 26 09:08:01 192.168.122.209 [61432.437097] [tdb] Close table 'filter0.tdb' Apr 26 09:08:01 192.168.122.209 [61432.437524] [tempesta fw] modules are stopped Apr 26 09:08:02 192.168.122.209 [61432.631495] [tempesta fw] exiting... Apr 26 09:08:02 192.168.122.209 [61432.735112] [tdb] Shutdown Tempesta DB Apr 26 09:08:02 192.168.122.209 [61432.940100] End test: sessions.test_cookies.StickyCookieOptions.test_vhost_max_age_is_set Apr 26 09:08:02 192.168.122.209 [61432.967499] Start test: sessions.test_cookies.StickyCookieOptions.test_vhost_sess_lifetime_and_global_sess_lifetime_and_max_age_are_set Apr 26 09:08:03 192.168.122.209 [61433.959753] [tdb] Start Tempesta DB Apr 26 09:08:03 192.168.122.209 [61434.096395] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:08:05 192.168.122.209 [61436.102472] [tempesta fw] Configuration processing is completed. Apr 26 09:08:05 192.168.122.209 [61436.153477] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:08:05 192.168.122.209 [61436.564585] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:08:06 192.168.122.209 [61436.591040] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:08:06 192.168.122.209 [61436.616881] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:08:06 192.168.122.209 [61436.714579] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:08:06 192.168.122.209 [61436.762995] [tempesta fw] Tempesta FW is ready Apr 26 09:08:06 192.168.122.209 [61437.311272] [tdb] Close table 'client0.tdb' Apr 26 09:08:06 192.168.122.209 [61437.516411] [tdb] Close table 'sessions0.tdb' Apr 26 09:08:10 192.168.122.209 [61440.695031] [tdb] Close table 'cache0.tdb' Apr 26 09:08:10 192.168.122.209 [61440.949903] [tdb] Close table 'filter0.tdb' Apr 26 09:08:10 192.168.122.209 [61440.950340] [tempesta fw] modules are stopped Apr 26 09:08:10 192.168.122.209 [61441.160753] [tempesta fw] exiting... Apr 26 09:08:10 192.168.122.209 [61441.282318] [tdb] Shutdown Tempesta DB Apr 26 09:08:10 192.168.122.209 [61441.483378] End test: sessions.test_cookies.StickyCookieOptions.test_vhost_sess_lifetime_and_global_sess_lifetime_and_max_age_are_set Apr 26 09:08:10 192.168.122.209 [61441.496856] Start test: sessions.test_cookies.TestCookieDockerH2.test Apr 26 09:08:14 192.168.122.209 [61444.994334] docker0: port 1(vethbd79900) entered blocking state Apr 26 09:08:14 192.168.122.209 [61444.994991] docker0: port 1(vethbd79900) entered disabled state Apr 26 09:08:14 192.168.122.209 [61444.996925] device vethbd79900 entered promiscuous mode Apr 26 09:08:15 192.168.122.209 [61445.993490] eth0: renamed from veth33f303d Apr 26 09:08:15 192.168.122.209 [61446.020915] IPv6: ADDRCONF(NETDEV_CHANGE): vethbd79900: link becomes ready Apr 26 09:08:15 192.168.122.209 [61446.021960] docker0: port 1(vethbd79900) entered blocking state Apr 26 09:08:15 192.168.122.209 [61446.022556] docker0: port 1(vethbd79900) entered forwarding state Apr 26 09:08:16 192.168.122.209 [61447.098556] [tdb] Start Tempesta DB Apr 26 09:08:16 192.168.122.209 [61447.245681] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:08:17 192.168.122.209 [61448.200192] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61448.200192] Maybe that's fine, but it's worth checking the [61448.200192] config - if there is no relations between the [61448.200192] names, then host name confusion attack is possible. Apr 26 09:08:17 192.168.122.209 [61448.362838] [tempesta fw] Configuration processing is completed. Apr 26 09:08:17 192.168.122.209 [61448.411819] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:08:18 192.168.122.209 [61448.895663] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:08:18 192.168.122.209 [61448.924182] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:08:18 192.168.122.209 [61448.953523] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:08:18 192.168.122.209 [61449.034952] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:08:18 192.168.122.209 [61449.035755] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:08:18 192.168.122.209 [61449.086659] [tempesta fw] Tempesta FW is ready Apr 26 09:08:19 192.168.122.209 [61450.299224] [tdb] Close table 'client0.tdb' Apr 26 09:08:19 192.168.122.209 [61450.492495] [tdb] Close table 'sessions0.tdb' Apr 26 09:08:23 192.168.122.209 [61454.227590] [tdb] Close table 'cache0.tdb' Apr 26 09:08:23 192.168.122.209 [61454.508179] [tdb] Close table 'filter0.tdb' Apr 26 09:08:23 192.168.122.209 [61454.508627] [tempesta fw] modules are stopped Apr 26 09:08:24 192.168.122.209 [61454.744985] [tempesta fw] exiting... Apr 26 09:08:24 192.168.122.209 [61454.871877] [tdb] Shutdown Tempesta DB Apr 26 09:08:24 192.168.122.209 [61455.416081] docker0: port 1(vethbd79900) entered disabled state Apr 26 09:08:24 192.168.122.209 [61455.416818] veth33f303d: renamed from eth0 Apr 26 09:08:24 192.168.122.209 [61455.506639] docker0: port 1(vethbd79900) entered disabled state Apr 26 09:08:24 192.168.122.209 [61455.516562] device vethbd79900 left promiscuous mode Apr 26 09:08:24 192.168.122.209 [61455.517052] docker0: port 1(vethbd79900) entered disabled state Apr 26 09:08:25 192.168.122.209 [61455.897966] End test: sessions.test_cookies.TestCookieDockerH2.test Apr 26 09:08:25 192.168.122.209 [61455.911113] Start test: sessions.test_cookies.TestCookieDockerHttp.test Apr 26 09:08:26 192.168.122.209 [61457.499567] docker0: port 1(veth4cf6add) entered blocking state Apr 26 09:08:26 192.168.122.209 [61457.500164] docker0: port 1(veth4cf6add) entered disabled state Apr 26 09:08:26 192.168.122.209 [61457.502003] device veth4cf6add entered promiscuous mode Apr 26 09:08:27 192.168.122.209 [61458.276830] eth0: renamed from veth1b28efa Apr 26 09:08:27 192.168.122.209 [61458.301177] IPv6: ADDRCONF(NETDEV_CHANGE): veth4cf6add: link becomes ready Apr 26 09:08:27 192.168.122.209 [61458.303430] docker0: port 1(veth4cf6add) entered blocking state Apr 26 09:08:27 192.168.122.209 [61458.304117] docker0: port 1(veth4cf6add) entered forwarding state Apr 26 09:08:28 192.168.122.209 [61459.466404] [tdb] Start Tempesta DB Apr 26 09:08:29 192.168.122.209 [61459.603966] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:08:30 192.168.122.209 [61460.959807] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61460.959807] Maybe that's fine, but it's worth checking the [61460.959807] config - if there is no relations between the [61460.959807] names, then host name confusion attack is possible. Apr 26 09:08:30 192.168.122.209 [61461.115216] [tempesta fw] Configuration processing is completed. Apr 26 09:08:30 192.168.122.209 [61461.174374] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:08:31 192.168.122.209 [61461.610230] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:08:31 192.168.122.209 [61461.640219] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:08:31 192.168.122.209 [61461.675014] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:08:31 192.168.122.209 [61461.790937] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:08:31 192.168.122.209 [61461.792716] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:08:31 192.168.122.209 [61461.846817] [tempesta fw] Tempesta FW is ready Apr 26 09:08:32 192.168.122.209 [61462.585991] [tdb] Close table 'client0.tdb' Apr 26 09:08:32 192.168.122.209 [61462.791027] [tdb] Close table 'sessions0.tdb' Apr 26 09:08:35 192.168.122.209 [61466.101805] [tdb] Close table 'cache0.tdb' Apr 26 09:08:35 192.168.122.209 [61466.361291] [tdb] Close table 'filter0.tdb' Apr 26 09:08:35 192.168.122.209 [61466.361732] [tempesta fw] modules are stopped Apr 26 09:08:36 192.168.122.209 [61466.674531] [tempesta fw] exiting... Apr 26 09:08:36 192.168.122.209 [61466.791784] [tdb] Shutdown Tempesta DB Apr 26 09:08:36 192.168.122.209 [61467.344677] docker0: port 1(veth4cf6add) entered disabled state Apr 26 09:08:36 192.168.122.209 [61467.345505] veth1b28efa: renamed from eth0 Apr 26 09:08:36 192.168.122.209 [61467.417137] docker0: port 1(veth4cf6add) entered disabled state Apr 26 09:08:36 192.168.122.209 [61467.421023] device veth4cf6add left promiscuous mode Apr 26 09:08:36 192.168.122.209 [61467.421525] docker0: port 1(veth4cf6add) entered disabled state Apr 26 09:08:37 192.168.122.209 [61467.723845] End test: sessions.test_cookies.TestCookieDockerHttp.test Apr 26 09:08:37 192.168.122.209 [61467.731496] Start test: sessions.test_cookies.TestCookieDockerHttps.test Apr 26 09:08:38 192.168.122.209 [61469.418901] docker0: port 1(vethfb865e0) entered blocking state Apr 26 09:08:38 192.168.122.209 [61469.420679] docker0: port 1(vethfb865e0) entered disabled state Apr 26 09:08:38 192.168.122.209 [61469.423871] device vethfb865e0 entered promiscuous mode Apr 26 09:08:39 192.168.122.209 [61469.949951] eth0: renamed from veth668c250 Apr 26 09:08:39 192.168.122.209 [61469.976661] IPv6: ADDRCONF(NETDEV_CHANGE): vethfb865e0: link becomes ready Apr 26 09:08:39 192.168.122.209 [61469.979885] docker0: port 1(vethfb865e0) entered blocking state Apr 26 09:08:39 192.168.122.209 [61469.981242] docker0: port 1(vethfb865e0) entered forwarding state Apr 26 09:08:40 192.168.122.209 [61471.015529] [tdb] Start Tempesta DB Apr 26 09:08:40 192.168.122.209 [61471.145949] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:08:41 192.168.122.209 [61472.516357] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61472.516357] Maybe that's fine, but it's worth checking the [61472.516357] config - if there is no relations between the [61472.516357] names, then host name confusion attack is possible. Apr 26 09:08:42 192.168.122.209 [61472.663350] [tempesta fw] Configuration processing is completed. Apr 26 09:08:42 192.168.122.209 [61472.713640] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:08:42 192.168.122.209 [61473.150562] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:08:42 192.168.122.209 [61473.181725] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:08:42 192.168.122.209 [61473.211993] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:08:42 192.168.122.209 [61473.295015] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:08:42 192.168.122.209 [61473.296783] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:08:42 192.168.122.209 [61473.362980] [tempesta fw] Tempesta FW is ready Apr 26 09:08:43 192.168.122.209 [61474.118433] [tdb] Close table 'client0.tdb' Apr 26 09:08:43 192.168.122.209 [61474.311635] [tdb] Close table 'sessions0.tdb' Apr 26 09:08:47 192.168.122.209 [61477.723178] [tdb] Close table 'cache0.tdb' Apr 26 09:08:47 192.168.122.209 [61478.035750] [tdb] Close table 'filter0.tdb' Apr 26 09:08:47 192.168.122.209 [61478.036169] [tempesta fw] modules are stopped Apr 26 09:08:47 192.168.122.209 [61478.338129] [tempesta fw] exiting... Apr 26 09:08:47 192.168.122.209 [61478.492952] [tdb] Shutdown Tempesta DB Apr 26 09:08:48 192.168.122.209 [61479.008177] docker0: port 1(vethfb865e0) entered disabled state Apr 26 09:08:48 192.168.122.209 [61479.009036] veth668c250: renamed from eth0 Apr 26 09:08:48 192.168.122.209 [61479.069307] docker0: port 1(vethfb865e0) entered disabled state Apr 26 09:08:48 192.168.122.209 [61479.077512] device vethfb865e0 left promiscuous mode Apr 26 09:08:48 192.168.122.209 [61479.078162] docker0: port 1(vethfb865e0) entered disabled state Apr 26 09:08:48 192.168.122.209 [61479.356204] End test: sessions.test_cookies.TestCookieDockerHttps.test Apr 26 09:08:48 192.168.122.209 [61479.369135] Start test: sessions.test_cookies.VhostCookies.test_cookie Apr 26 09:08:49 192.168.122.209 [61480.382459] [tdb] Start Tempesta DB Apr 26 09:08:49 192.168.122.209 [61480.534381] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:08:52 192.168.122.209 [61482.783212] [tempesta fw] Configuration processing is completed. Apr 26 09:08:52 192.168.122.209 [61482.848534] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:08:52 192.168.122.209 [61483.300992] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:08:52 192.168.122.209 [61483.330524] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:08:52 192.168.122.209 [61483.358863] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:08:52 192.168.122.209 [61483.463079] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:08:52 192.168.122.209 [61483.515132] [tempesta fw] Tempesta FW is ready Apr 26 09:08:54 192.168.122.209 [61484.846406] [tdb] Close table 'client0.tdb' Apr 26 09:08:54 192.168.122.209 [61485.036756] [tdb] Close table 'sessions0.tdb' Apr 26 09:08:57 192.168.122.209 [61488.290255] [tdb] Close table 'cache0.tdb' Apr 26 09:08:57 192.168.122.209 [61488.517042] [tdb] Close table 'filter0.tdb' Apr 26 09:08:57 192.168.122.209 [61488.517488] [tempesta fw] modules are stopped Apr 26 09:08:58 192.168.122.209 [61488.760011] [tempesta fw] exiting... Apr 26 09:08:58 192.168.122.209 [61488.880249] [tdb] Shutdown Tempesta DB Apr 26 09:08:58 192.168.122.209 [61489.085878] End test: sessions.test_cookies.VhostCookies.test_cookie Apr 26 09:08:58 192.168.122.209 [61489.104125] Start test: sessions.test_h2_sticky_scheduler.H2StickySchedulerTestCase.test_h2_cookie_scheduler Apr 26 09:08:59 192.168.122.209 [61490.426105] [tdb] Start Tempesta DB Apr 26 09:08:59 192.168.122.209 [61490.570217] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:09:01 192.168.122.209 [61492.368517] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61492.368517] Maybe that's fine, but it's worth checking the [61492.368517] config - if there is no relations between the [61492.368517] names, then host name confusion attack is possible. Apr 26 09:09:01 192.168.122.209 [61492.499265] [tempesta fw] Configuration processing is completed. Apr 26 09:09:01 192.168.122.209 [61492.549488] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:09:02 192.168.122.209 [61492.948976] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:09:02 192.168.122.209 [61492.974569] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:09:02 192.168.122.209 [61493.000789] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:09:02 192.168.122.209 [61493.071270] [tempesta fw] Open listen socket on: 127.0.0.1:8765 Apr 26 09:09:02 192.168.122.209 [61493.115205] [tempesta fw] Tempesta FW is ready Apr 26 09:09:02 192.168.122.209 [61493.546562] [tempesta fw] Warning: request has been filtered out via http table: 127.0.0.2 Apr 26 09:09:03 192.168.122.209 [61494.050863] [tdb] Close table 'client0.tdb' Apr 26 09:09:03 192.168.122.209 [61494.254746] [tdb] Close table 'sessions0.tdb' Apr 26 09:09:06 192.168.122.209 [61497.521186] [tdb] Close table 'cache0.tdb' Apr 26 09:09:07 192.168.122.209 [61497.803262] [tdb] Close table 'filter0.tdb' Apr 26 09:09:07 192.168.122.209 [61497.803695] [tempesta fw] modules are stopped Apr 26 09:09:07 192.168.122.209 [61498.048247] [tempesta fw] exiting... Apr 26 09:09:07 192.168.122.209 [61498.185055] [tdb] Shutdown Tempesta DB Apr 26 09:09:07 192.168.122.209 [61498.430818] End test: sessions.test_h2_sticky_scheduler.H2StickySchedulerTestCase.test_h2_cookie_scheduler Apr 26 09:09:07 192.168.122.209 [61498.517764] Start test: sessions.test_js_challenge.JSChallengeCookieExpiresAndMethodOverrideH2.test_cookie_expires Apr 26 09:09:09 192.168.122.209 [61499.647482] [tdb] Start Tempesta DB Apr 26 09:09:09 192.168.122.209 [61499.805700] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:09:11 192.168.122.209 [61501.728414] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61501.728414] Maybe that's fine, but it's worth checking the [61501.728414] config - if there is no relations between the [61501.728414] names, then host name confusion attack is possible. Apr 26 09:09:11 192.168.122.209 [61501.857552] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:09:11 192.168.122.209 [61501.899386] [tempesta fw] Configuration processing is completed. Apr 26 09:09:11 192.168.122.209 [61501.954467] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:09:11 192.168.122.209 [61502.374446] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:09:11 192.168.122.209 [61502.400492] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:09:11 192.168.122.209 [61502.426837] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:09:11 192.168.122.209 [61502.484680] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:09:11 192.168.122.209 [61502.486411] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:09:11 192.168.122.209 [61502.531322] [tempesta fw] Tempesta FW is ready Apr 26 09:09:15 192.168.122.209 [61505.857771] [tempesta fw] Warning: http_sess: sticky cookie value expired for 127.0.0.2 (issued=4310267455 lifetime=750 now=4310268237) Apr 26 09:09:15 192.168.122.209 [61506.360403] [tdb] Close table 'client0.tdb' Apr 26 09:09:15 192.168.122.209 [61506.545608] [tdb] Close table 'sessions0.tdb' Apr 26 09:09:19 192.168.122.209 [61509.748825] [tdb] Close table 'cache0.tdb' Apr 26 09:09:19 192.168.122.209 [61509.981279] [tdb] Close table 'filter0.tdb' Apr 26 09:09:19 192.168.122.209 [61509.981707] [tempesta fw] modules are stopped Apr 26 09:09:19 192.168.122.209 [61510.201880] [tempesta fw] exiting... Apr 26 09:09:19 192.168.122.209 [61510.339229] [tdb] Shutdown Tempesta DB Apr 26 09:09:19 192.168.122.209 [61510.521286] End test: sessions.test_js_challenge.JSChallengeCookieExpiresAndMethodOverrideH2.test_cookie_expires Apr 26 09:09:19 192.168.122.209 [61510.567790] Start test: sessions.test_js_challenge.JSChallengeCookieExpiresAndMethodOverrideHttp.test_cookie_expires Apr 26 09:09:21 192.168.122.209 [61511.654348] [tdb] Start Tempesta DB Apr 26 09:09:21 192.168.122.209 [61511.798784] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:09:23 192.168.122.209 [61513.688782] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61513.688782] Maybe that's fine, but it's worth checking the [61513.688782] config - if there is no relations between the [61513.688782] names, then host name confusion attack is possible. Apr 26 09:09:23 192.168.122.209 [61513.833429] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:09:23 192.168.122.209 [61513.863859] [tempesta fw] Configuration processing is completed. Apr 26 09:09:23 192.168.122.209 [61513.917966] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:09:23 192.168.122.209 [61514.326240] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:09:23 192.168.122.209 [61514.351533] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:09:23 192.168.122.209 [61514.377469] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:09:23 192.168.122.209 [61514.423536] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:09:23 192.168.122.209 [61514.425290] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:09:23 192.168.122.209 [61514.463474] [tempesta fw] Tempesta FW is ready Apr 26 09:09:27 192.168.122.209 [61517.733959] [tempesta fw] Warning: http_sess: sticky cookie value expired for 127.0.0.2 (issued=4310270424 lifetime=750 now=4310271206) Apr 26 09:09:27 192.168.122.209 [61518.204902] [tdb] Close table 'client0.tdb' Apr 26 09:09:27 192.168.122.209 [61518.392835] [tdb] Close table 'sessions0.tdb' Apr 26 09:09:30 192.168.122.209 [61521.578530] [tdb] Close table 'cache0.tdb' Apr 26 09:09:31 192.168.122.209 [61521.827361] [tdb] Close table 'filter0.tdb' Apr 26 09:09:31 192.168.122.209 [61521.827805] [tempesta fw] modules are stopped Apr 26 09:09:31 192.168.122.209 [61522.031439] [tempesta fw] exiting... Apr 26 09:09:31 192.168.122.209 [61522.174677] [tdb] Shutdown Tempesta DB Apr 26 09:09:31 192.168.122.209 [61522.367327] End test: sessions.test_js_challenge.JSChallengeCookieExpiresAndMethodOverrideHttp.test_cookie_expires Apr 26 09:09:31 192.168.122.209 [61522.405734] Start test: sessions.test_js_challenge.JSChallengeH2.test_cookies_in_request_multiple_in_one Apr 26 09:09:32 192.168.122.209 [61523.438704] [tdb] Start Tempesta DB Apr 26 09:09:32 192.168.122.209 [61523.578441] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:09:35 192.168.122.209 [61525.580961] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61525.580961] Maybe that's fine, but it's worth checking the [61525.580961] config - if there is no relations between the [61525.580961] names, then host name confusion attack is possible. Apr 26 09:09:35 192.168.122.209 [61525.753782] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:09:35 192.168.122.209 [61525.791699] [tempesta fw] Configuration processing is completed. Apr 26 09:09:35 192.168.122.209 [61525.845840] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:09:35 192.168.122.209 [61526.259212] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:09:35 192.168.122.209 [61526.285062] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:09:35 192.168.122.209 [61526.310512] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:09:35 192.168.122.209 [61526.363610] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:09:35 192.168.122.209 [61526.365419] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:09:35 192.168.122.209 [61526.407673] [tempesta fw] Tempesta FW is ready Apr 26 09:09:40 192.168.122.209 [61530.972911] [tempesta fw] Warning: Multiple Tempesta sticky cookies found in request: 2 Apr 26 09:09:40 192.168.122.209 [61530.973665] [tempesta fw] Warning: request dropped: internal error in Sticky module: 127.0.0.2 Apr 26 09:09:40 192.168.122.209 [61531.400310] [tdb] Close table 'client0.tdb' Apr 26 09:09:41 192.168.122.209 [61531.593788] [tdb] Close table 'sessions0.tdb' Apr 26 09:09:44 192.168.122.209 [61534.801301] [tdb] Close table 'cache0.tdb' Apr 26 09:09:44 192.168.122.209 [61535.056604] [tdb] Close table 'filter0.tdb' Apr 26 09:09:44 192.168.122.209 [61535.057062] [tempesta fw] modules are stopped Apr 26 09:09:44 192.168.122.209 [61535.244551] [tempesta fw] exiting... Apr 26 09:09:44 192.168.122.209 [61535.374922] [tdb] Shutdown Tempesta DB Apr 26 09:09:45 192.168.122.209 [61535.593518] End test: sessions.test_js_challenge.JSChallengeH2.test_cookies_in_request_multiple_in_one Apr 26 09:09:45 192.168.122.209 [61535.605370] Start test: sessions.test_js_challenge.JSChallengeH2.test_cookies_in_request_multiple_in_two Apr 26 09:09:46 192.168.122.209 [61536.722368] [tdb] Start Tempesta DB Apr 26 09:09:46 192.168.122.209 [61536.873033] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:09:48 192.168.122.209 [61538.793120] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61538.793120] Maybe that's fine, but it's worth checking the [61538.793120] config - if there is no relations between the [61538.793120] names, then host name confusion attack is possible. Apr 26 09:09:48 192.168.122.209 [61538.965863] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:09:48 192.168.122.209 [61539.011849] [tempesta fw] Configuration processing is completed. Apr 26 09:09:48 192.168.122.209 [61539.062232] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:09:48 192.168.122.209 [61539.461129] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:09:48 192.168.122.209 [61539.496583] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:09:48 192.168.122.209 [61539.523609] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:09:49 192.168.122.209 [61539.579846] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:09:49 192.168.122.209 [61539.581539] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:09:49 192.168.122.209 [61539.619796] [tempesta fw] Tempesta FW is ready Apr 26 09:09:52 192.168.122.209 [61543.360942] [tempesta fw] Warning: Multiple Tempesta sticky cookies found in request: 2 Apr 26 09:09:52 192.168.122.209 [61543.361927] [tempesta fw] Warning: request dropped: internal error in Sticky module: 127.0.0.2 Apr 26 09:09:53 192.168.122.209 [61543.801465] [tdb] Close table 'client0.tdb' Apr 26 09:09:53 192.168.122.209 [61543.992723] [tdb] Close table 'sessions0.tdb' Apr 26 09:09:56 192.168.122.209 [61547.172702] [tdb] Close table 'cache0.tdb' Apr 26 09:09:56 192.168.122.209 [61547.413763] [tdb] Close table 'filter0.tdb' Apr 26 09:09:56 192.168.122.209 [61547.414186] [tempesta fw] modules are stopped Apr 26 09:09:57 192.168.122.209 [61547.618328] [tempesta fw] exiting... Apr 26 09:09:57 192.168.122.209 [61547.731715] [tdb] Shutdown Tempesta DB Apr 26 09:09:57 192.168.122.209 [61547.970082] End test: sessions.test_js_challenge.JSChallengeH2.test_cookies_in_request_multiple_in_two Apr 26 09:09:57 192.168.122.209 [61547.982438] Start test: sessions.test_js_challenge.JSChallengeH2.test_delay_pass Apr 26 09:09:58 192.168.122.209 [61549.013899] [tdb] Start Tempesta DB Apr 26 09:09:58 192.168.122.209 [61549.153288] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:10:00 192.168.122.209 [61551.080494] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61551.080494] Maybe that's fine, but it's worth checking the [61551.080494] config - if there is no relations between the [61551.080494] names, then host name confusion attack is possible. Apr 26 09:10:00 192.168.122.209 [61551.238113] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:10:00 192.168.122.209 [61551.276030] [tempesta fw] Configuration processing is completed. Apr 26 09:10:00 192.168.122.209 [61551.325990] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:10:01 192.168.122.209 [61551.737635] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:10:01 192.168.122.209 [61551.763220] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:10:01 192.168.122.209 [61551.788814] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:10:01 192.168.122.209 [61551.836034] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:10:01 192.168.122.209 [61551.837715] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:10:01 192.168.122.209 [61551.887960] [tempesta fw] Tempesta FW is ready Apr 26 09:10:04 192.168.122.209 [61554.796108] [tdb] Close table 'client0.tdb' Apr 26 09:10:04 192.168.122.209 [61554.994115] [tdb] Close table 'sessions0.tdb' Apr 26 09:10:07 192.168.122.209 [61558.198715] [tdb] Close table 'cache0.tdb' Apr 26 09:10:07 192.168.122.209 [61558.437397] [tdb] Close table 'filter0.tdb' Apr 26 09:10:07 192.168.122.209 [61558.437844] [tempesta fw] modules are stopped Apr 26 09:10:08 192.168.122.209 [61558.664657] [tempesta fw] exiting... Apr 26 09:10:08 192.168.122.209 [61558.784961] [tdb] Shutdown Tempesta DB Apr 26 09:10:08 192.168.122.209 [61558.976781] End test: sessions.test_js_challenge.JSChallengeH2.test_delay_pass Apr 26 09:10:08 192.168.122.209 [61558.987377] Start test: sessions.test_js_challenge.JSChallengeH2.test_delay_pipelined_pass Apr 26 09:10:09 192.168.122.209 [61560.104487] [tdb] Start Tempesta DB Apr 26 09:10:09 192.168.122.209 [61560.242046] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:10:11 192.168.122.209 [61562.253495] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61562.253495] Maybe that's fine, but it's worth checking the [61562.253495] config - if there is no relations between the [61562.253495] names, then host name confusion attack is possible. Apr 26 09:10:11 192.168.122.209 [61562.422222] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:10:11 192.168.122.209 [61562.460160] [tempesta fw] Configuration processing is completed. Apr 26 09:10:11 192.168.122.209 [61562.517307] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:10:12 192.168.122.209 [61562.930142] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:10:12 192.168.122.209 [61562.964198] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:10:12 192.168.122.209 [61562.993276] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:10:12 192.168.122.209 [61563.060157] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:10:12 192.168.122.209 [61563.061847] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:10:12 192.168.122.209 [61563.112100] [tempesta fw] Tempesta FW is ready Apr 26 09:10:15 192.168.122.209 [61565.839683] [tdb] Close table 'client0.tdb' Apr 26 09:10:15 192.168.122.209 [61566.025142] [tdb] Close table 'sessions0.tdb' Apr 26 09:10:18 192.168.122.209 [61569.282346] [tdb] Close table 'cache0.tdb' Apr 26 09:10:18 192.168.122.209 [61569.531914] [tdb] Close table 'filter0.tdb' Apr 26 09:10:18 192.168.122.209 [61569.532723] [tempesta fw] modules are stopped Apr 26 09:10:19 192.168.122.209 [61569.750880] [tempesta fw] exiting... Apr 26 09:10:19 192.168.122.209 [61569.863600] [tdb] Shutdown Tempesta DB Apr 26 09:10:19 192.168.122.209 [61570.077604] End test: sessions.test_js_challenge.JSChallengeH2.test_delay_pipelined_pass Apr 26 09:10:19 192.168.122.209 [61570.088979] Start test: sessions.test_js_challenge.JSChallengeH2.test_delay_pipelined_too_early Apr 26 09:10:20 192.168.122.209 [61571.080444] [tdb] Start Tempesta DB Apr 26 09:10:20 192.168.122.209 [61571.221203] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:10:22 192.168.122.209 [61573.185547] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61573.185547] Maybe that's fine, but it's worth checking the [61573.185547] config - if there is no relations between the [61573.185547] names, then host name confusion attack is possible. Apr 26 09:10:22 192.168.122.209 [61573.350312] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:10:22 192.168.122.209 [61573.400302] [tempesta fw] Configuration processing is completed. Apr 26 09:10:22 192.168.122.209 [61573.450275] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:10:23 192.168.122.209 [61573.849895] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:10:23 192.168.122.209 [61573.875948] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:10:23 192.168.122.209 [61573.903623] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:10:23 192.168.122.209 [61573.976281] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:10:23 192.168.122.209 [61573.977983] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:10:23 192.168.122.209 [61574.024246] [tempesta fw] Tempesta FW is ready Apr 26 09:10:23 192.168.122.209 [61574.240689] [tempesta fw] Warning: http_sess: jsch redirect received too early for 127.0.0.2 (4310285333 is not after 4310285784) Apr 26 09:10:23 192.168.122.209 [61574.241734] [tempesta fw] Warning: frang: max rmisses exceeded for 127.0.0.2: 3 (lim=2) Apr 26 09:10:24 192.168.122.209 [61574.668901] [tdb] Close table 'client0.tdb' Apr 26 09:10:24 192.168.122.209 [61574.874072] [tdb] Close table 'sessions0.tdb' Apr 26 09:10:27 192.168.122.209 [61578.087097] [tdb] Close table 'cache0.tdb' Apr 26 09:10:27 192.168.122.209 [61578.312085] [tdb] Close table 'filter0.tdb' Apr 26 09:10:27 192.168.122.209 [61578.312534] [tempesta fw] modules are stopped Apr 26 09:10:27 192.168.122.209 [61578.535933] [tempesta fw] exiting... Apr 26 09:10:28 192.168.122.209 [61578.654582] [tdb] Shutdown Tempesta DB Apr 26 09:10:28 192.168.122.209 [61578.851336] End test: sessions.test_js_challenge.JSChallengeH2.test_delay_pipelined_too_early Apr 26 09:10:28 192.168.122.209 [61578.865319] Start test: sessions.test_js_challenge.JSChallengeH2.test_delay_too_small Apr 26 09:10:29 192.168.122.209 [61579.911812] [tdb] Start Tempesta DB Apr 26 09:10:29 192.168.122.209 [61580.052563] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:10:31 192.168.122.209 [61582.033735] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61582.033735] Maybe that's fine, but it's worth checking the [61582.033735] config - if there is no relations between the [61582.033735] names, then host name confusion attack is possible. Apr 26 09:10:31 192.168.122.209 [61582.190479] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:10:31 192.168.122.209 [61582.236573] [tempesta fw] Configuration processing is completed. Apr 26 09:10:31 192.168.122.209 [61582.290331] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:10:32 192.168.122.209 [61582.708157] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:10:32 192.168.122.209 [61582.734939] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:10:32 192.168.122.209 [61582.763644] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:10:32 192.168.122.209 [61582.804403] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:10:32 192.168.122.209 [61582.805425] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:10:32 192.168.122.209 [61582.844362] [tempesta fw] Tempesta FW is ready Apr 26 09:10:32 192.168.122.209 [61583.045853] [tempesta fw] Warning: http_sess: jsch redirect received too early for 127.0.0.2 (4310287534 is not after 4310287788) Apr 26 09:10:32 192.168.122.209 [61583.462262] [tdb] Close table 'client0.tdb' Apr 26 09:10:33 192.168.122.209 [61583.634828] [tdb] Close table 'sessions0.tdb' Apr 26 09:10:36 192.168.122.209 [61586.927814] [tdb] Close table 'cache0.tdb' Apr 26 09:10:36 192.168.122.209 [61587.177860] [tdb] Close table 'filter0.tdb' Apr 26 09:10:36 192.168.122.209 [61587.178317] [tempesta fw] modules are stopped Apr 26 09:10:36 192.168.122.209 [61587.344217] [tempesta fw] exiting... Apr 26 09:10:36 192.168.122.209 [61587.434378] [tdb] Shutdown Tempesta DB Apr 26 09:10:37 192.168.122.209 [61587.627504] End test: sessions.test_js_challenge.JSChallengeH2.test_delay_too_small Apr 26 09:10:37 192.168.122.209 [61587.647983] Start test: sessions.test_js_challenge.JSChallengeH2.test_disable_challenge_on_reload Apr 26 09:10:38 192.168.122.209 [61588.667504] [tdb] Start Tempesta DB Apr 26 09:10:38 192.168.122.209 [61588.812398] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:10:40 192.168.122.209 [61590.825758] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61590.825758] Maybe that's fine, but it's worth checking the [61590.825758] config - if there is no relations between the [61590.825758] names, then host name confusion attack is possible. Apr 26 09:10:40 192.168.122.209 [61590.974552] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:10:40 192.168.122.209 [61591.016533] [tempesta fw] Configuration processing is completed. Apr 26 09:10:40 192.168.122.209 [61591.067547] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:10:40 192.168.122.209 [61591.493304] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:10:40 192.168.122.209 [61591.518842] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:10:40 192.168.122.209 [61591.546083] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:10:41 192.168.122.209 [61591.612488] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:10:41 192.168.122.209 [61591.613769] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:10:41 192.168.122.209 [61591.652479] [tempesta fw] Tempesta FW is ready Apr 26 09:10:41 192.168.122.209 [61592.464792] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 09:10:41 192.168.122.209 [61592.531382] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61592.531382] Maybe that's fine, but it's worth checking the [61592.531382] config - if there is no relations between the [61592.531382] names, then host name confusion attack is possible. Apr 26 09:10:42 192.168.122.209 [61592.784561] [tempesta fw] Configuration processing is completed. Apr 26 09:10:42 192.168.122.209 [61593.105047] [tempesta fw] Tempesta FW is ready Apr 26 09:10:43 192.168.122.209 [61593.635078] [tdb] Close table 'client0.tdb' Apr 26 09:10:43 192.168.122.209 [61593.840744] [tdb] Close table 'sessions0.tdb' Apr 26 09:10:46 192.168.122.209 [61597.069730] [tdb] Close table 'cache0.tdb' Apr 26 09:10:46 192.168.122.209 [61597.317420] [tdb] Close table 'filter0.tdb' Apr 26 09:10:46 192.168.122.209 [61597.317875] [tempesta fw] modules are stopped Apr 26 09:10:46 192.168.122.209 [61597.540835] [tempesta fw] exiting... Apr 26 09:10:47 192.168.122.209 [61597.670855] [tdb] Shutdown Tempesta DB Apr 26 09:10:47 192.168.122.209 [61597.860103] End test: sessions.test_js_challenge.JSChallengeH2.test_disable_challenge_on_reload Apr 26 09:10:47 192.168.122.209 [61597.890325] Start test: sessions.test_js_challenge.JSChallengeH2.test_enable_challenge_on_reload Apr 26 09:10:48 192.168.122.209 [61598.889639] [tdb] Start Tempesta DB Apr 26 09:10:48 192.168.122.209 [61599.058027] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:10:50 192.168.122.209 [61600.725928] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61600.725928] Maybe that's fine, but it's worth checking the [61600.725928] config - if there is no relations between the [61600.725928] names, then host name confusion attack is possible. Apr 26 09:10:50 192.168.122.209 [61600.928649] [tempesta fw] Configuration processing is completed. Apr 26 09:10:50 192.168.122.209 [61600.981589] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:10:50 192.168.122.209 [61601.410553] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:10:50 192.168.122.209 [61601.438409] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:10:50 192.168.122.209 [61601.466441] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:10:50 192.168.122.209 [61601.512746] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:10:50 192.168.122.209 [61601.514501] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:10:50 192.168.122.209 [61601.556585] [tempesta fw] Tempesta FW is ready Apr 26 09:10:51 192.168.122.209 [61602.512843] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 09:10:52 192.168.122.209 [61602.593944] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61602.593944] Maybe that's fine, but it's worth checking the [61602.593944] config - if there is no relations between the [61602.593944] names, then host name confusion attack is possible. Apr 26 09:10:52 192.168.122.209 [61602.818751] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:10:52 192.168.122.209 [61602.868696] [tempesta fw] Configuration processing is completed. Apr 26 09:10:52 192.168.122.209 [61603.133105] [tempesta fw] Tempesta FW is ready Apr 26 09:10:54 192.168.122.209 [61605.288464] [tdb] Close table 'client0.tdb' Apr 26 09:10:54 192.168.122.209 [61605.471467] [tdb] Close table 'sessions0.tdb' Apr 26 09:10:58 192.168.122.209 [61608.795026] [tdb] Close table 'cache0.tdb' Apr 26 09:10:58 192.168.122.209 [61609.043385] [tdb] Close table 'filter0.tdb' Apr 26 09:10:58 192.168.122.209 [61609.043823] [tempesta fw] modules are stopped Apr 26 09:10:58 192.168.122.209 [61609.227477] [tempesta fw] exiting... Apr 26 09:10:58 192.168.122.209 [61609.359985] [tdb] Shutdown Tempesta DB Apr 26 09:10:59 192.168.122.209 [61609.578872] End test: sessions.test_js_challenge.JSChallengeH2.test_enable_challenge_on_reload Apr 26 09:10:59 192.168.122.209 [61609.595925] Start test: sessions.test_js_challenge.JSChallengeH2.test_first_post_request_pipelined Apr 26 09:11:00 192.168.122.209 [61610.708449] [tdb] Start Tempesta DB Apr 26 09:11:00 192.168.122.209 [61610.884923] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:11:02 192.168.122.209 [61612.974154] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61612.974154] Maybe that's fine, but it's worth checking the [61612.974154] config - if there is no relations between the [61612.974154] names, then host name confusion attack is possible. Apr 26 09:11:02 192.168.122.209 [61613.155037] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:11:02 192.168.122.209 [61613.200818] [tempesta fw] Configuration processing is completed. Apr 26 09:11:02 192.168.122.209 [61613.257185] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:11:03 192.168.122.209 [61613.721047] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:11:03 192.168.122.209 [61613.759312] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:11:03 192.168.122.209 [61613.791884] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:11:03 192.168.122.209 [61613.840764] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:11:03 192.168.122.209 [61613.842632] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:11:03 192.168.122.209 [61613.888752] [tempesta fw] Tempesta FW is ready Apr 26 09:11:05 192.168.122.209 [61615.854901] [tdb] Close table 'client0.tdb' Apr 26 09:11:05 192.168.122.209 [61616.062127] [tdb] Close table 'sessions0.tdb' Apr 26 09:11:08 192.168.122.209 [61619.465052] [tdb] Close table 'cache0.tdb' Apr 26 09:11:09 192.168.122.209 [61619.743503] [tdb] Close table 'filter0.tdb' Apr 26 09:11:09 192.168.122.209 [61619.743949] [tempesta fw] modules are stopped Apr 26 09:11:09 192.168.122.209 [61619.929088] [tempesta fw] exiting... Apr 26 09:11:09 192.168.122.209 [61620.060947] [tdb] Shutdown Tempesta DB Apr 26 09:11:09 192.168.122.209 [61620.288400] End test: sessions.test_js_challenge.JSChallengeH2.test_first_post_request_pipelined Apr 26 09:11:09 192.168.122.209 [61620.309135] Start test: sessions.test_js_challenge.JSChallengeH2.test_first_request_GET_and_accept_all Apr 26 09:11:10 192.168.122.209 [61621.450957] [tdb] Start Tempesta DB Apr 26 09:11:11 192.168.122.209 [61621.586755] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:11:13 192.168.122.209 [61623.654384] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61623.654384] Maybe that's fine, but it's worth checking the [61623.654384] config - if there is no relations between the [61623.654384] names, then host name confusion attack is possible. Apr 26 09:11:13 192.168.122.209 [61623.831028] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:11:13 192.168.122.209 [61623.872997] [tempesta fw] Configuration processing is completed. Apr 26 09:11:13 192.168.122.209 [61623.932114] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:11:13 192.168.122.209 [61624.398763] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:11:13 192.168.122.209 [61624.433262] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:11:13 192.168.122.209 [61624.468346] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:11:13 192.168.122.209 [61624.520959] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:11:13 192.168.122.209 [61624.522768] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:11:13 192.168.122.209 [61624.576899] [tempesta fw] Tempesta FW is ready Apr 26 09:11:14 192.168.122.209 [61625.218464] [tdb] Close table 'client0.tdb' Apr 26 09:11:14 192.168.122.209 [61625.386314] [tdb] Close table 'sessions0.tdb' Apr 26 09:11:18 192.168.122.209 [61628.662665] [tdb] Close table 'cache0.tdb' Apr 26 09:11:18 192.168.122.209 [61628.900912] [tdb] Close table 'filter0.tdb' Apr 26 09:11:18 192.168.122.209 [61628.901332] [tempesta fw] modules are stopped Apr 26 09:11:18 192.168.122.209 [61629.134361] [tempesta fw] exiting... Apr 26 09:11:18 192.168.122.209 [61629.244608] [tdb] Shutdown Tempesta DB Apr 26 09:11:18 192.168.122.209 [61629.461923] End test: sessions.test_js_challenge.JSChallengeH2.test_first_request_GET_and_accept_all Apr 26 09:11:18 192.168.122.209 [61629.470228] Start test: sessions.test_js_challenge.JSChallengeH2.test_first_request_GET_and_accept_html Apr 26 09:11:19 192.168.122.209 [61630.479429] [tdb] Start Tempesta DB Apr 26 09:11:20 192.168.122.209 [61630.620126] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:11:22 192.168.122.209 [61632.602289] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61632.602289] Maybe that's fine, but it's worth checking the [61632.602289] config - if there is no relations between the [61632.602289] names, then host name confusion attack is possible. Apr 26 09:11:22 192.168.122.209 [61632.767115] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:11:22 192.168.122.209 [61632.805051] [tempesta fw] Configuration processing is completed. Apr 26 09:11:22 192.168.122.209 [61632.858931] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:11:22 192.168.122.209 [61633.260796] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:11:22 192.168.122.209 [61633.286684] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:11:22 192.168.122.209 [61633.312289] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:11:22 192.168.122.209 [61633.373066] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:11:22 192.168.122.209 [61633.374806] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:11:22 192.168.122.209 [61633.416994] [tempesta fw] Tempesta FW is ready Apr 26 09:11:23 192.168.122.209 [61634.038362] [tdb] Close table 'client0.tdb' Apr 26 09:11:23 192.168.122.209 [61634.230281] [tdb] Close table 'sessions0.tdb' Apr 26 09:11:26 192.168.122.209 [61637.493313] [tdb] Close table 'cache0.tdb' Apr 26 09:11:27 192.168.122.209 [61637.719323] [tdb] Close table 'filter0.tdb' Apr 26 09:11:27 192.168.122.209 [61637.719754] [tempesta fw] modules are stopped Apr 26 09:11:27 192.168.122.209 [61637.917997] [tempesta fw] exiting... Apr 26 09:11:27 192.168.122.209 [61638.034906] [tdb] Shutdown Tempesta DB Apr 26 09:11:27 192.168.122.209 [61638.240663] End test: sessions.test_js_challenge.JSChallengeH2.test_first_request_GET_and_accept_html Apr 26 09:11:27 192.168.122.209 [61638.251995] Start test: sessions.test_js_challenge.JSChallengeH2.test_first_request_GET_and_accept_image Apr 26 09:11:28 192.168.122.209 [61639.308432] [tdb] Start Tempesta DB Apr 26 09:11:28 192.168.122.209 [61639.445621] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:11:30 192.168.122.209 [61641.394446] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61641.394446] Maybe that's fine, but it's worth checking the [61641.394446] config - if there is no relations between the [61641.394446] names, then host name confusion attack is possible. Apr 26 09:11:30 192.168.122.209 [61641.559235] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:11:31 192.168.122.209 [61641.593377] [tempesta fw] Configuration processing is completed. Apr 26 09:11:31 192.168.122.209 [61641.649352] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:11:31 192.168.122.209 [61642.055052] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:11:31 192.168.122.209 [61642.081005] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:11:31 192.168.122.209 [61642.107910] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:11:31 192.168.122.209 [61642.169167] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:11:31 192.168.122.209 [61642.170660] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:11:31 192.168.122.209 [61642.225118] [tempesta fw] Tempesta FW is ready Apr 26 09:11:32 192.168.122.209 [61642.834942] [tdb] Close table 'client0.tdb' Apr 26 09:11:32 192.168.122.209 [61643.023067] [tdb] Close table 'sessions0.tdb' Apr 26 09:11:35 192.168.122.209 [61646.224583] [tdb] Close table 'cache0.tdb' Apr 26 09:11:35 192.168.122.209 [61646.474116] [tdb] Close table 'filter0.tdb' Apr 26 09:11:35 192.168.122.209 [61646.474543] [tempesta fw] modules are stopped Apr 26 09:11:36 192.168.122.209 [61646.766656] [tempesta fw] exiting... Apr 26 09:11:36 192.168.122.209 [61646.868564] [tdb] Shutdown Tempesta DB Apr 26 09:11:36 192.168.122.209 [61647.092414] End test: sessions.test_js_challenge.JSChallengeH2.test_first_request_GET_and_accept_image Apr 26 09:11:36 192.168.122.209 [61647.101071] Start test: sessions.test_js_challenge.JSChallengeH2.test_first_request_GET_and_accept_plain Apr 26 09:11:37 192.168.122.209 [61648.175447] [tdb] Start Tempesta DB Apr 26 09:11:37 192.168.122.209 [61648.309861] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:11:39 192.168.122.209 [61650.274526] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61650.274526] Maybe that's fine, but it's worth checking the [61650.274526] config - if there is no relations between the [61650.274526] names, then host name confusion attack is possible. Apr 26 09:11:39 192.168.122.209 [61650.443332] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:11:39 192.168.122.209 [61650.489228] [tempesta fw] Configuration processing is completed. Apr 26 09:11:39 192.168.122.209 [61650.547667] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:11:40 192.168.122.209 [61650.964584] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:11:40 192.168.122.209 [61650.997596] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:11:40 192.168.122.209 [61651.022432] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:11:40 192.168.122.209 [61651.081276] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:11:40 192.168.122.209 [61651.083026] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:11:40 192.168.122.209 [61651.137223] [tempesta fw] Tempesta FW is ready Apr 26 09:11:41 192.168.122.209 [61651.734840] [tdb] Close table 'client0.tdb' Apr 26 09:11:41 192.168.122.209 [61651.933332] [tdb] Close table 'sessions0.tdb' Apr 26 09:11:44 192.168.122.209 [61655.171165] [tdb] Close table 'cache0.tdb' Apr 26 09:11:44 192.168.122.209 [61655.413021] [tdb] Close table 'filter0.tdb' Apr 26 09:11:44 192.168.122.209 [61655.413467] [tempesta fw] modules are stopped Apr 26 09:11:45 192.168.122.209 [61655.672008] [tempesta fw] exiting... Apr 26 09:11:45 192.168.122.209 [61655.797603] [tdb] Shutdown Tempesta DB Apr 26 09:11:45 192.168.122.209 [61656.009714] End test: sessions.test_js_challenge.JSChallengeH2.test_first_request_GET_and_accept_plain Apr 26 09:11:45 192.168.122.209 [61656.021355] Start test: sessions.test_js_challenge.JSChallengeH2.test_first_request_GET_and_accept_text_all Apr 26 09:11:46 192.168.122.209 [61657.053645] [tdb] Start Tempesta DB Apr 26 09:11:46 192.168.122.209 [61657.200527] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:11:48 192.168.122.209 [61659.194640] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61659.194640] Maybe that's fine, but it's worth checking the [61659.194640] config - if there is no relations between the [61659.194640] names, then host name confusion attack is possible. Apr 26 09:11:48 192.168.122.209 [61659.359430] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:11:48 192.168.122.209 [61659.405436] [tempesta fw] Configuration processing is completed. Apr 26 09:11:48 192.168.122.209 [61659.456799] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:11:49 192.168.122.209 [61659.897253] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:11:49 192.168.122.209 [61659.925517] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:11:49 192.168.122.209 [61659.953153] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:11:49 192.168.122.209 [61660.005398] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:11:49 192.168.122.209 [61660.007206] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:11:49 192.168.122.209 [61660.045330] [tempesta fw] Tempesta FW is ready Apr 26 09:11:50 192.168.122.209 [61660.675611] [tdb] Close table 'client0.tdb' Apr 26 09:11:50 192.168.122.209 [61660.870890] [tdb] Close table 'sessions0.tdb' Apr 26 09:11:53 192.168.122.209 [61664.126338] [tdb] Close table 'cache0.tdb' Apr 26 09:11:53 192.168.122.209 [61664.360273] [tdb] Close table 'filter0.tdb' Apr 26 09:11:53 192.168.122.209 [61664.360680] [tempesta fw] modules are stopped Apr 26 09:11:53 192.168.122.209 [61664.563638] [tempesta fw] exiting... Apr 26 09:11:54 192.168.122.209 [61664.686646] [tdb] Shutdown Tempesta DB Apr 26 09:11:54 192.168.122.209 [61664.879299] End test: sessions.test_js_challenge.JSChallengeH2.test_first_request_GET_and_accept_text_all Apr 26 09:11:54 192.168.122.209 [61664.893168] Start test: sessions.test_js_challenge.JSChallengeH2.test_first_request_POST Apr 26 09:11:55 192.168.122.209 [61665.883818] [tdb] Start Tempesta DB Apr 26 09:11:55 192.168.122.209 [61666.037198] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:11:57 192.168.122.209 [61668.070772] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61668.070772] Maybe that's fine, but it's worth checking the [61668.070772] config - if there is no relations between the [61668.070772] names, then host name confusion attack is possible. Apr 26 09:11:57 192.168.122.209 [61668.235510] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:11:57 192.168.122.209 [61668.277514] [tempesta fw] Configuration processing is completed. Apr 26 09:11:57 192.168.122.209 [61668.337414] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:11:58 192.168.122.209 [61668.766315] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:11:58 192.168.122.209 [61668.794258] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:11:58 192.168.122.209 [61668.821416] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:11:58 192.168.122.209 [61668.881524] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:11:58 192.168.122.209 [61668.883260] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:11:58 192.168.122.209 [61668.921471] [tempesta fw] Tempesta FW is ready Apr 26 09:11:58 192.168.122.209 [61669.523601] [tdb] Close table 'client0.tdb' Apr 26 09:11:59 192.168.122.209 [61669.720539] [tdb] Close table 'sessions0.tdb' Apr 26 09:12:02 192.168.122.209 [61673.032737] [tdb] Close table 'cache0.tdb' Apr 26 09:12:02 192.168.122.209 [61673.276280] [tdb] Close table 'filter0.tdb' Apr 26 09:12:02 192.168.122.209 [61673.276719] [tempesta fw] modules are stopped Apr 26 09:12:02 192.168.122.209 [61673.449786] [tempesta fw] exiting... Apr 26 09:12:03 192.168.122.209 [61673.595747] [tdb] Shutdown Tempesta DB Apr 26 09:12:03 192.168.122.209 [61673.814371] End test: sessions.test_js_challenge.JSChallengeH2.test_first_request_POST Apr 26 09:12:03 192.168.122.209 [61673.825836] Start test: sessions.test_js_challenge.JSChallengeH2.test_method_override_GET_HEAD Apr 26 09:12:04 192.168.122.209 [61674.898819] [tdb] Start Tempesta DB Apr 26 09:12:04 192.168.122.209 [61675.047101] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:12:06 192.168.122.209 [61677.030964] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61677.030964] Maybe that's fine, but it's worth checking the [61677.030964] config - if there is no relations between the [61677.030964] names, then host name confusion attack is possible. Apr 26 09:12:06 192.168.122.209 [61677.211692] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:12:06 192.168.122.209 [61677.241924] [tempesta fw] Configuration processing is completed. Apr 26 09:12:06 192.168.122.209 [61677.293347] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:12:07 192.168.122.209 [61677.770748] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:12:07 192.168.122.209 [61677.800405] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:12:07 192.168.122.209 [61677.832404] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:12:07 192.168.122.209 [61677.885653] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:12:07 192.168.122.209 [61677.887412] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:12:07 192.168.122.209 [61677.925568] [tempesta fw] Tempesta FW is ready Apr 26 09:12:07 192.168.122.209 [61678.558745] [tdb] Close table 'client0.tdb' Apr 26 09:12:08 192.168.122.209 [61678.764600] [tdb] Close table 'sessions0.tdb' Apr 26 09:12:11 192.168.122.209 [61682.024284] [tdb] Close table 'cache0.tdb' Apr 26 09:12:11 192.168.122.209 [61682.268388] [tdb] Close table 'filter0.tdb' Apr 26 09:12:11 192.168.122.209 [61682.268838] [tempesta fw] modules are stopped Apr 26 09:12:11 192.168.122.209 [61682.474409] [tempesta fw] exiting... Apr 26 09:12:12 192.168.122.209 [61682.606785] [tdb] Shutdown Tempesta DB Apr 26 09:12:12 192.168.122.209 [61682.842248] End test: sessions.test_js_challenge.JSChallengeH2.test_method_override_GET_HEAD Apr 26 09:12:12 192.168.122.209 [61682.853589] Start test: sessions.test_js_challenge.JSChallengeH2.test_method_override_GET_POST Apr 26 09:12:13 192.168.122.209 [61683.884139] [tdb] Start Tempesta DB Apr 26 09:12:13 192.168.122.209 [61684.017745] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:12:15 192.168.122.209 [61685.967058] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61685.967058] Maybe that's fine, but it's worth checking the [61685.967058] config - if there is no relations between the [61685.967058] names, then host name confusion attack is possible. Apr 26 09:12:15 192.168.122.209 [61686.135820] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:12:15 192.168.122.209 [61686.173745] [tempesta fw] Configuration processing is completed. Apr 26 09:12:15 192.168.122.209 [61686.230379] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:12:16 192.168.122.209 [61686.646279] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:12:16 192.168.122.209 [61686.671756] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:12:16 192.168.122.209 [61686.698038] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:12:16 192.168.122.209 [61686.741733] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:12:16 192.168.122.209 [61686.743472] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:12:16 192.168.122.209 [61686.777692] [tempesta fw] Tempesta FW is ready Apr 26 09:12:16 192.168.122.209 [61686.966292] [tempesta fw] Warning: request dropped: unsafe method override: 127.0.0.2 Apr 26 09:12:16 192.168.122.209 [61687.385204] [tdb] Close table 'client0.tdb' Apr 26 09:12:16 192.168.122.209 [61687.579158] [tdb] Close table 'sessions0.tdb' Apr 26 09:12:20 192.168.122.209 [61690.795584] [tdb] Close table 'cache0.tdb' Apr 26 09:12:20 192.168.122.209 [61691.047470] [tdb] Close table 'filter0.tdb' Apr 26 09:12:20 192.168.122.209 [61691.047881] [tempesta fw] modules are stopped Apr 26 09:12:20 192.168.122.209 [61691.280342] [tempesta fw] exiting... Apr 26 09:12:20 192.168.122.209 [61691.429283] [tdb] Shutdown Tempesta DB Apr 26 09:12:21 192.168.122.209 [61691.650895] End test: sessions.test_js_challenge.JSChallengeH2.test_method_override_GET_POST Apr 26 09:12:21 192.168.122.209 [61691.666192] Start test: sessions.test_js_challenge.JSChallengeH2.test_method_override_HEAD_POST Apr 26 09:12:22 192.168.122.209 [61692.704303] [tdb] Start Tempesta DB Apr 26 09:12:22 192.168.122.209 [61692.850706] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:12:24 192.168.122.209 [61694.891164] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61694.891164] Maybe that's fine, but it's worth checking the [61694.891164] config - if there is no relations between the [61694.891164] names, then host name confusion attack is possible. Apr 26 09:12:24 192.168.122.209 [61695.055844] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:12:24 192.168.122.209 [61695.097847] [tempesta fw] Configuration processing is completed. Apr 26 09:12:24 192.168.122.209 [61695.148216] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:12:24 192.168.122.209 [61695.576342] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:12:25 192.168.122.209 [61695.602021] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:12:25 192.168.122.209 [61695.628552] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:12:25 192.168.122.209 [61695.677834] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:12:25 192.168.122.209 [61695.679538] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:12:25 192.168.122.209 [61695.717792] [tempesta fw] Tempesta FW is ready Apr 26 09:12:25 192.168.122.209 [61695.923792] [tempesta fw] Warning: request dropped: unsafe method override: 127.0.0.2 Apr 26 09:12:25 192.168.122.209 [61696.355803] [tdb] Close table 'client0.tdb' Apr 26 09:12:25 192.168.122.209 [61696.565855] [tdb] Close table 'sessions0.tdb' Apr 26 09:12:29 192.168.122.209 [61699.798787] [tdb] Close table 'cache0.tdb' Apr 26 09:12:29 192.168.122.209 [61700.040170] [tdb] Close table 'filter0.tdb' Apr 26 09:12:29 192.168.122.209 [61700.040601] [tempesta fw] modules are stopped Apr 26 09:12:29 192.168.122.209 [61700.263120] [tempesta fw] exiting... Apr 26 09:12:29 192.168.122.209 [61700.403895] [tdb] Shutdown Tempesta DB Apr 26 09:12:30 192.168.122.209 [61700.620165] End test: sessions.test_js_challenge.JSChallengeH2.test_method_override_HEAD_POST Apr 26 09:12:30 192.168.122.209 [61700.633442] Start test: sessions.test_js_challenge.JSChallengeH2.test_method_override_POST_GET Apr 26 09:12:31 192.168.122.209 [61701.645293] [tdb] Start Tempesta DB Apr 26 09:12:31 192.168.122.209 [61701.787674] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:12:33 192.168.122.209 [61703.843290] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61703.843290] Maybe that's fine, but it's worth checking the [61703.843290] config - if there is no relations between the [61703.843290] names, then host name confusion attack is possible. Apr 26 09:12:33 192.168.122.209 [61703.999946] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:12:33 192.168.122.209 [61704.038265] [tempesta fw] Configuration processing is completed. Apr 26 09:12:33 192.168.122.209 [61704.096797] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:12:33 192.168.122.209 [61704.501652] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:12:33 192.168.122.209 [61704.528231] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:12:33 192.168.122.209 [61704.556379] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:12:34 192.168.122.209 [61704.613961] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:12:34 192.168.122.209 [61704.615660] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:12:34 192.168.122.209 [61704.661900] [tempesta fw] Tempesta FW is ready Apr 26 09:12:34 192.168.122.209 [61705.284057] [tdb] Close table 'client0.tdb' Apr 26 09:12:34 192.168.122.209 [61705.449586] [tdb] Close table 'sessions0.tdb' Apr 26 09:12:38 192.168.122.209 [61708.719771] [tdb] Close table 'cache0.tdb' Apr 26 09:12:38 192.168.122.209 [61708.990527] [tdb] Close table 'filter0.tdb' Apr 26 09:12:38 192.168.122.209 [61708.990971] [tempesta fw] modules are stopped Apr 26 09:12:38 192.168.122.209 [61709.175521] [tempesta fw] exiting... Apr 26 09:12:38 192.168.122.209 [61709.284095] [tdb] Shutdown Tempesta DB Apr 26 09:12:38 192.168.122.209 [61709.492846] End test: sessions.test_js_challenge.JSChallengeH2.test_method_override_POST_GET Apr 26 09:12:38 192.168.122.209 [61709.504504] Start test: sessions.test_js_challenge.JSChallengeH2.test_method_override_POST_HEAD Apr 26 09:12:39 192.168.122.209 [61710.533710] [tdb] Start Tempesta DB Apr 26 09:12:40 192.168.122.209 [61710.675130] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:12:42 192.168.122.209 [61712.619459] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61712.619459] Maybe that's fine, but it's worth checking the [61712.619459] config - if there is no relations between the [61712.619459] names, then host name confusion attack is possible. Apr 26 09:12:42 192.168.122.209 [61712.792338] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:12:42 192.168.122.209 [61712.846151] [tempesta fw] Configuration processing is completed. Apr 26 09:12:42 192.168.122.209 [61712.909168] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:12:42 192.168.122.209 [61713.443827] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:12:42 192.168.122.209 [61713.478210] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:12:42 192.168.122.209 [61713.513975] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:12:42 192.168.122.209 [61713.578063] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:12:42 192.168.122.209 [61713.579774] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:12:43 192.168.122.209 [61713.626025] [tempesta fw] Tempesta FW is ready Apr 26 09:12:43 192.168.122.209 [61714.275616] [tdb] Close table 'client0.tdb' Apr 26 09:12:43 192.168.122.209 [61714.462353] [tdb] Close table 'sessions0.tdb' Apr 26 09:12:47 192.168.122.209 [61717.757797] [tdb] Close table 'cache0.tdb' Apr 26 09:12:47 192.168.122.209 [61718.009501] [tdb] Close table 'filter0.tdb' Apr 26 09:12:47 192.168.122.209 [61718.009947] [tempesta fw] modules are stopped Apr 26 09:12:47 192.168.122.209 [61718.220781] [tempesta fw] exiting... Apr 26 09:12:47 192.168.122.209 [61718.345230] [tdb] Shutdown Tempesta DB Apr 26 09:12:47 192.168.122.209 [61718.543044] End test: sessions.test_js_challenge.JSChallengeH2.test_method_override_POST_HEAD Apr 26 09:12:47 192.168.122.209 [61718.552313] Start test: sessions.test_js_challenge.JSChallengeH2.test_method_override_with_cache_GET_HEAD Apr 26 09:12:48 192.168.122.209 [61719.563020] [tdb] Start Tempesta DB Apr 26 09:12:49 192.168.122.209 [61719.697692] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:12:51 192.168.122.209 [61721.691449] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61721.691449] Maybe that's fine, but it's worth checking the [61721.691449] config - if there is no relations between the [61721.691449] names, then host name confusion attack is possible. Apr 26 09:12:51 192.168.122.209 [61721.872356] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:12:51 192.168.122.209 [61721.922223] [tempesta fw] Configuration processing is completed. Apr 26 09:12:51 192.168.122.209 [61721.983258] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:12:51 192.168.122.209 [61722.402382] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:12:51 192.168.122.209 [61722.428315] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:12:51 192.168.122.209 [61722.454678] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:12:51 192.168.122.209 [61722.498177] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:12:51 192.168.122.209 [61722.499892] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:12:51 192.168.122.209 [61722.542140] [tempesta fw] Tempesta FW is ready Apr 26 09:12:54 192.168.122.209 [61724.699436] [tdb] Close table 'client0.tdb' Apr 26 09:12:54 192.168.122.209 [61724.879072] [tdb] Close table 'sessions0.tdb' Apr 26 09:12:57 192.168.122.209 [61728.084764] [tdb] Close table 'cache0.tdb' Apr 26 09:12:57 192.168.122.209 [61728.306741] [tdb] Close table 'filter0.tdb' Apr 26 09:12:57 192.168.122.209 [61728.307170] [tempesta fw] modules are stopped Apr 26 09:12:57 192.168.122.209 [61728.510580] [tempesta fw] exiting... Apr 26 09:12:58 192.168.122.209 [61728.633679] [tdb] Shutdown Tempesta DB Apr 26 09:12:58 192.168.122.209 [61728.842949] End test: sessions.test_js_challenge.JSChallengeH2.test_method_override_with_cache_GET_HEAD Apr 26 09:12:58 192.168.122.209 [61728.864786] Start test: sessions.test_js_challenge.JSChallengeH2.test_method_override_with_cache_GET_POST Apr 26 09:12:59 192.168.122.209 [61729.900075] [tdb] Start Tempesta DB Apr 26 09:12:59 192.168.122.209 [61730.023996] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:13:01 192.168.122.209 [61731.947586] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61731.947586] Maybe that's fine, but it's worth checking the [61731.947586] config - if there is no relations between the [61731.947586] names, then host name confusion attack is possible. Apr 26 09:13:01 192.168.122.209 [61732.108335] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:13:01 192.168.122.209 [61732.146636] [tempesta fw] Configuration processing is completed. Apr 26 09:13:01 192.168.122.209 [61732.197600] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:13:02 192.168.122.209 [61732.600997] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:13:02 192.168.122.209 [61732.626686] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:13:02 192.168.122.209 [61732.653877] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:13:02 192.168.122.209 [61732.702308] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:13:02 192.168.122.209 [61732.704014] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:13:02 192.168.122.209 [61732.750272] [tempesta fw] Tempesta FW is ready Apr 26 09:13:03 192.168.122.209 [61733.999435] [tempesta fw] Warning: request dropped: unsafe method override: 127.0.0.2 Apr 26 09:13:03 192.168.122.209 [61734.405525] [tdb] Close table 'client0.tdb' Apr 26 09:13:04 192.168.122.209 [61734.602904] [tdb] Close table 'sessions0.tdb' Apr 26 09:13:07 192.168.122.209 [61737.754827] [tdb] Close table 'cache0.tdb' Apr 26 09:13:07 192.168.122.209 [61737.997370] [tdb] Close table 'filter0.tdb' Apr 26 09:13:07 192.168.122.209 [61737.997783] [tempesta fw] modules are stopped Apr 26 09:13:07 192.168.122.209 [61738.186439] [tempesta fw] exiting... Apr 26 09:13:07 192.168.122.209 [61738.340266] [tdb] Shutdown Tempesta DB Apr 26 09:13:07 192.168.122.209 [61738.560595] End test: sessions.test_js_challenge.JSChallengeH2.test_method_override_with_cache_GET_POST Apr 26 09:13:07 192.168.122.209 [61738.573429] Start test: sessions.test_js_challenge.JSChallengeH2.test_method_override_with_cache_HEAD_GET Apr 26 09:13:09 192.168.122.209 [61739.601292] [tdb] Start Tempesta DB Apr 26 09:13:09 192.168.122.209 [61739.730965] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:13:11 192.168.122.209 [61741.675687] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61741.675687] Maybe that's fine, but it's worth checking the [61741.675687] config - if there is no relations between the [61741.675687] names, then host name confusion attack is possible. Apr 26 09:13:11 192.168.122.209 [61741.856509] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:13:11 192.168.122.209 [61741.898453] [tempesta fw] Configuration processing is completed. Apr 26 09:13:11 192.168.122.209 [61741.956698] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:13:11 192.168.122.209 [61742.381632] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:13:11 192.168.122.209 [61742.407812] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:13:11 192.168.122.209 [61742.433937] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:13:11 192.168.122.209 [61742.478440] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:13:11 192.168.122.209 [61742.480116] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:13:11 192.168.122.209 [61742.518381] [tempesta fw] Tempesta FW is ready Apr 26 09:13:14 192.168.122.209 [61745.154779] [tdb] Close table 'client0.tdb' Apr 26 09:13:14 192.168.122.209 [61745.348607] [tdb] Close table 'sessions0.tdb' Apr 26 09:13:17 192.168.122.209 [61748.551979] [tdb] Close table 'cache0.tdb' Apr 26 09:13:18 192.168.122.209 [61748.785294] [tdb] Close table 'filter0.tdb' Apr 26 09:13:18 192.168.122.209 [61748.785719] [tempesta fw] modules are stopped Apr 26 09:13:18 192.168.122.209 [61748.980155] [tempesta fw] exiting... Apr 26 09:13:18 192.168.122.209 [61749.127889] [tdb] Shutdown Tempesta DB Apr 26 09:13:18 192.168.122.209 [61749.313303] End test: sessions.test_js_challenge.JSChallengeH2.test_method_override_with_cache_HEAD_GET Apr 26 09:13:18 192.168.122.209 [61749.325250] Start test: sessions.test_js_challenge.JSChallengeH2.test_method_override_with_cache_HEAD_POST Apr 26 09:13:19 192.168.122.209 [61750.383552] [tdb] Start Tempesta DB Apr 26 09:13:19 192.168.122.209 [61750.519210] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:13:21 192.168.122.209 [61752.511840] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61752.511840] Maybe that's fine, but it's worth checking the [61752.511840] config - if there is no relations between the [61752.511840] names, then host name confusion attack is possible. Apr 26 09:13:22 192.168.122.209 [61752.668651] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:13:22 192.168.122.209 [61752.706602] [tempesta fw] Configuration processing is completed. Apr 26 09:13:22 192.168.122.209 [61752.762461] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:13:22 192.168.122.209 [61753.171630] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:13:22 192.168.122.209 [61753.196843] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:13:22 192.168.122.209 [61753.222301] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:13:22 192.168.122.209 [61753.266579] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:13:22 192.168.122.209 [61753.268332] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:13:22 192.168.122.209 [61753.318513] [tempesta fw] Tempesta FW is ready Apr 26 09:13:24 192.168.122.209 [61755.198745] [tempesta fw] Warning: request dropped: unsafe method override: 127.0.0.2 Apr 26 09:13:25 192.168.122.209 [61755.610865] [tdb] Close table 'client0.tdb' Apr 26 09:13:25 192.168.122.209 [61755.799784] [tdb] Close table 'sessions0.tdb' Apr 26 09:13:28 192.168.122.209 [61758.996640] [tdb] Close table 'cache0.tdb' Apr 26 09:13:28 192.168.122.209 [61759.231910] [tdb] Close table 'filter0.tdb' Apr 26 09:13:28 192.168.122.209 [61759.232341] [tempesta fw] modules are stopped Apr 26 09:13:28 192.168.122.209 [61759.462470] [tempesta fw] exiting... Apr 26 09:13:28 192.168.122.209 [61759.573351] [tdb] Shutdown Tempesta DB Apr 26 09:13:29 192.168.122.209 [61759.777400] End test: sessions.test_js_challenge.JSChallengeH2.test_method_override_with_cache_HEAD_POST Apr 26 09:13:29 192.168.122.209 [61759.794131] Start test: sessions.test_js_challenge.JSChallengeH2.test_method_override_with_cache_POST_GET Apr 26 09:13:30 192.168.122.209 [61760.825431] [tdb] Start Tempesta DB Apr 26 09:13:30 192.168.122.209 [61760.953304] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:13:32 192.168.122.209 [61762.871993] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61762.871993] Maybe that's fine, but it's worth checking the [61762.871993] config - if there is no relations between the [61762.871993] names, then host name confusion attack is possible. Apr 26 09:13:32 192.168.122.209 [61763.032754] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:13:32 192.168.122.209 [61763.071062] [tempesta fw] Configuration processing is completed. Apr 26 09:13:32 192.168.122.209 [61763.127638] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:13:32 192.168.122.209 [61763.524426] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:13:32 192.168.122.209 [61763.549768] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:13:33 192.168.122.209 [61763.583407] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:13:33 192.168.122.209 [61763.626708] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:13:33 192.168.122.209 [61763.628455] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:13:33 192.168.122.209 [61763.674660] [tempesta fw] Tempesta FW is ready Apr 26 09:13:34 192.168.122.209 [61765.574853] [tdb] Close table 'client0.tdb' Apr 26 09:13:35 192.168.122.209 [61765.767155] [tdb] Close table 'sessions0.tdb' Apr 26 09:13:38 192.168.122.209 [61768.977163] [tdb] Close table 'cache0.tdb' Apr 26 09:13:38 192.168.122.209 [61769.217804] [tdb] Close table 'filter0.tdb' Apr 26 09:13:38 192.168.122.209 [61769.218226] [tempesta fw] modules are stopped Apr 26 09:13:38 192.168.122.209 [61769.411506] [tempesta fw] exiting... Apr 26 09:13:38 192.168.122.209 [61769.537426] [tdb] Shutdown Tempesta DB Apr 26 09:13:39 192.168.122.209 [61769.736977] End test: sessions.test_js_challenge.JSChallengeH2.test_method_override_with_cache_POST_GET Apr 26 09:13:39 192.168.122.209 [61769.764182] Start test: sessions.test_js_challenge.JSChallengeH2.test_method_override_with_cache_POST_HEAD Apr 26 09:13:40 192.168.122.209 [61770.820957] [tdb] Start Tempesta DB Apr 26 09:13:40 192.168.122.209 [61770.955785] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:13:42 192.168.122.209 [61772.876138] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61772.876138] Maybe that's fine, but it's worth checking the [61772.876138] config - if there is no relations between the [61772.876138] names, then host name confusion attack is possible. Apr 26 09:13:42 192.168.122.209 [61773.036896] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:13:42 192.168.122.209 [61773.074884] [tempesta fw] Configuration processing is completed. Apr 26 09:13:42 192.168.122.209 [61773.135691] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:13:42 192.168.122.209 [61773.547468] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:13:42 192.168.122.209 [61773.573136] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:13:43 192.168.122.209 [61773.600362] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:13:43 192.168.122.209 [61773.646812] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:13:43 192.168.122.209 [61773.648205] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:13:43 192.168.122.209 [61773.698784] [tempesta fw] Tempesta FW is ready Apr 26 09:13:46 192.168.122.209 [61776.651633] [tdb] Close table 'client0.tdb' Apr 26 09:13:46 192.168.122.209 [61776.835178] [tdb] Close table 'sessions0.tdb' Apr 26 09:13:49 192.168.122.209 [61780.018066] [tdb] Close table 'cache0.tdb' Apr 26 09:13:49 192.168.122.209 [61780.257720] [tdb] Close table 'filter0.tdb' Apr 26 09:13:49 192.168.122.209 [61780.258153] [tempesta fw] modules are stopped Apr 26 09:13:49 192.168.122.209 [61780.436937] [tempesta fw] exiting... Apr 26 09:13:49 192.168.122.209 [61780.559239] [tdb] Shutdown Tempesta DB Apr 26 09:13:50 192.168.122.209 [61780.772604] End test: sessions.test_js_challenge.JSChallengeH2.test_method_override_with_cache_POST_HEAD Apr 26 09:13:50 192.168.122.209 [61780.787672] Start test: sessions.test_js_challenge.JSChallengeH2.test_new_client_session_with_exist_cookie Apr 26 09:13:51 192.168.122.209 [61781.813228] [tdb] Start Tempesta DB Apr 26 09:13:51 192.168.122.209 [61781.938106] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:13:53 192.168.122.209 [61783.904239] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61783.904239] Maybe that's fine, but it's worth checking the [61783.904239] config - if there is no relations between the [61783.904239] names, then host name confusion attack is possible. Apr 26 09:13:53 192.168.122.209 [61784.092998] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:13:53 192.168.122.209 [61784.131287] [tempesta fw] Configuration processing is completed. Apr 26 09:13:53 192.168.122.209 [61784.181274] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:13:53 192.168.122.209 [61784.582308] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:13:54 192.168.122.209 [61784.608677] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:13:54 192.168.122.209 [61784.634948] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:13:54 192.168.122.209 [61784.682904] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:13:54 192.168.122.209 [61784.684250] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:13:54 192.168.122.209 [61784.726937] [tempesta fw] Tempesta FW is ready Apr 26 09:13:56 192.168.122.209 [61787.369355] [tdb] Close table 'client0.tdb' Apr 26 09:13:56 192.168.122.209 [61787.554833] [tdb] Close table 'sessions0.tdb' Apr 26 09:14:00 192.168.122.209 [61790.834825] [tdb] Close table 'cache0.tdb' Apr 26 09:14:00 192.168.122.209 [61791.081255] [tdb] Close table 'filter0.tdb' Apr 26 09:14:00 192.168.122.209 [61791.081687] [tempesta fw] modules are stopped Apr 26 09:14:00 192.168.122.209 [61791.269905] [tempesta fw] exiting... Apr 26 09:14:00 192.168.122.209 [61791.395751] [tdb] Shutdown Tempesta DB Apr 26 09:14:01 192.168.122.209 [61791.600888] End test: sessions.test_js_challenge.JSChallengeH2.test_new_client_session_with_exist_cookie Apr 26 09:14:01 192.168.122.209 [61791.610517] Start test: sessions.test_js_challenge.JSChallengeH2.test_not_block_after_tempesta_restart Apr 26 09:14:02 192.168.122.209 [61792.665680] [tdb] Start Tempesta DB Apr 26 09:14:02 192.168.122.209 [61792.806020] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:14:04 192.168.122.209 [61794.780404] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61794.780404] Maybe that's fine, but it's worth checking the [61794.780404] config - if there is no relations between the [61794.780404] names, then host name confusion attack is possible. Apr 26 09:14:04 192.168.122.209 [61794.953171] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:14:04 192.168.122.209 [61794.999133] [tempesta fw] Configuration processing is completed. Apr 26 09:14:04 192.168.122.209 [61795.055763] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:14:04 192.168.122.209 [61795.468601] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:14:04 192.168.122.209 [61795.495199] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:14:04 192.168.122.209 [61795.522386] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:14:05 192.168.122.209 [61795.591113] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:14:05 192.168.122.209 [61795.592789] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:14:05 192.168.122.209 [61795.639076] [tempesta fw] Tempesta FW is ready Apr 26 09:14:07 192.168.122.209 [61797.989438] [tdb] Close table 'client0.tdb' Apr 26 09:14:07 192.168.122.209 [61798.174606] [tdb] Close table 'sessions0.tdb' Apr 26 09:14:10 192.168.122.209 [61801.348170] [tdb] Close table 'cache0.tdb' Apr 26 09:14:10 192.168.122.209 [61801.582372] [tdb] Close table 'filter0.tdb' Apr 26 09:14:10 192.168.122.209 [61801.582806] [tempesta fw] modules are stopped Apr 26 09:14:11 192.168.122.209 [61801.754372] [tempesta fw] exiting... Apr 26 09:14:11 192.168.122.209 [61801.892533] [tdb] Shutdown Tempesta DB Apr 26 09:14:12 192.168.122.209 [61802.910921] [tdb] Start Tempesta DB Apr 26 09:14:12 192.168.122.209 [61803.048347] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:14:14 192.168.122.209 [61804.912408] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61804.912408] Maybe that's fine, but it's worth checking the [61804.912408] config - if there is no relations between the [61804.912408] names, then host name confusion attack is possible. Apr 26 09:14:14 192.168.122.209 [61805.098211] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:14:14 192.168.122.209 [61805.127423] [tempesta fw] Configuration processing is completed. Apr 26 09:14:14 192.168.122.209 [61805.179059] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:14:14 192.168.122.209 [61805.581701] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:14:15 192.168.122.209 [61805.607555] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:14:15 192.168.122.209 [61805.633666] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:14:15 192.168.122.209 [61805.723227] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:14:15 192.168.122.209 [61805.724916] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:14:15 192.168.122.209 [61805.791183] [tempesta fw] Tempesta FW is ready Apr 26 09:14:15 192.168.122.209 [61805.901465] [tempesta fw] Warning: http_sess: bad received HMAC value for 127.0.0.2 0(pos=0), ts=0x100ea9478 orig_hmac=[1176eb7305389d56a4cc708efc443e0d6906f029] Apr 26 09:14:17 192.168.122.209 [61807.605641] [tdb] Close table 'client0.tdb' Apr 26 09:14:17 192.168.122.209 [61807.787090] [tdb] Close table 'sessions0.tdb' Apr 26 09:14:20 192.168.122.209 [61810.989281] [tdb] Close table 'cache0.tdb' Apr 26 09:14:20 192.168.122.209 [61811.204272] [tdb] Close table 'filter0.tdb' Apr 26 09:14:20 192.168.122.209 [61811.204695] [tempesta fw] modules are stopped Apr 26 09:14:20 192.168.122.209 [61811.398848] [tempesta fw] exiting... Apr 26 09:14:20 192.168.122.209 [61811.510382] [tdb] Shutdown Tempesta DB Apr 26 09:14:21 192.168.122.209 [61811.718622] End test: sessions.test_js_challenge.JSChallengeH2.test_not_block_after_tempesta_restart Apr 26 09:14:21 192.168.122.209 [61811.733248] Start test: sessions.test_js_challenge.JSChallengeH2.test_number_of_requests_is_greater_than_max_misses Apr 26 09:14:22 192.168.122.209 [61812.817354] [tdb] Start Tempesta DB Apr 26 09:14:22 192.168.122.209 [61812.945337] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:14:24 192.168.122.209 [61814.972661] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61814.972661] Maybe that's fine, but it's worth checking the [61814.972661] config - if there is no relations between the [61814.972661] names, then host name confusion attack is possible. Apr 26 09:14:24 192.168.122.209 [61815.133460] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:14:24 192.168.122.209 [61815.179396] [tempesta fw] Configuration processing is completed. Apr 26 09:14:24 192.168.122.209 [61815.245018] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:14:25 192.168.122.209 [61815.655587] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:14:25 192.168.122.209 [61815.681444] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:14:25 192.168.122.209 [61815.707092] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:14:25 192.168.122.209 [61815.759393] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:14:25 192.168.122.209 [61815.761053] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:14:25 192.168.122.209 [61815.807323] [tempesta fw] Tempesta FW is ready Apr 26 09:14:25 192.168.122.209 [61816.021529] [tempesta fw] Warning: frang: max rmisses exceeded for 127.0.0.2: 3 (lim=2) Apr 26 09:14:25 192.168.122.209 [61816.438667] [tdb] Close table 'client0.tdb' Apr 26 09:14:26 192.168.122.209 [61816.626377] [tdb] Close table 'sessions0.tdb' Apr 26 09:14:29 192.168.122.209 [61819.809002] [tdb] Close table 'cache0.tdb' Apr 26 09:14:29 192.168.122.209 [61820.028838] [tdb] Close table 'filter0.tdb' Apr 26 09:14:29 192.168.122.209 [61820.029259] [tempesta fw] modules are stopped Apr 26 09:14:29 192.168.122.209 [61820.233222] [tempesta fw] exiting... Apr 26 09:14:29 192.168.122.209 [61820.364153] [tdb] Shutdown Tempesta DB Apr 26 09:14:29 192.168.122.209 [61820.568363] End test: sessions.test_js_challenge.JSChallengeH2.test_number_of_requests_is_greater_than_max_misses Apr 26 09:14:29 192.168.122.209 [61820.581931] Start test: sessions.test_js_challenge.JSChallengeH2.test_resp_code_302 Apr 26 09:14:31 192.168.122.209 [61821.636590] [tdb] Start Tempesta DB Apr 26 09:14:31 192.168.122.209 [61821.772123] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:14:33 192.168.122.209 [61823.736764] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61823.736764] Maybe that's fine, but it's worth checking the [61823.736764] config - if there is no relations between the [61823.736764] names, then host name confusion attack is possible. Apr 26 09:14:33 192.168.122.209 [61823.933543] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:14:33 192.168.122.209 [61823.975521] [tempesta fw] Configuration processing is completed. Apr 26 09:14:33 192.168.122.209 [61824.030667] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:14:33 192.168.122.209 [61824.435354] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:14:33 192.168.122.209 [61824.461906] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:14:33 192.168.122.209 [61824.489697] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:14:33 192.168.122.209 [61824.543514] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:14:33 192.168.122.209 [61824.545192] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:14:34 192.168.122.209 [61824.583429] [tempesta fw] Tempesta FW is ready Apr 26 09:14:34 192.168.122.209 [61825.189105] [tdb] Close table 'client0.tdb' Apr 26 09:14:34 192.168.122.209 [61825.379028] [tdb] Close table 'sessions0.tdb' Apr 26 09:14:37 192.168.122.209 [61828.553183] [tdb] Close table 'cache0.tdb' Apr 26 09:14:38 192.168.122.209 [61828.778779] [tdb] Close table 'filter0.tdb' Apr 26 09:14:38 192.168.122.209 [61828.779224] [tempesta fw] modules are stopped Apr 26 09:14:38 192.168.122.209 [61828.977437] [tempesta fw] exiting... Apr 26 09:14:38 192.168.122.209 [61829.088578] [tdb] Shutdown Tempesta DB Apr 26 09:14:38 192.168.122.209 [61829.277463] End test: sessions.test_js_challenge.JSChallengeH2.test_resp_code_302 Apr 26 09:14:38 192.168.122.209 [61829.295559] Start test: sessions.test_js_challenge.JSChallengeH2.test_resp_code_403 Apr 26 09:14:39 192.168.122.209 [61830.317247] [tdb] Start Tempesta DB Apr 26 09:14:39 192.168.122.209 [61830.444603] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:14:41 192.168.122.209 [61832.472854] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61832.472854] Maybe that's fine, but it's worth checking the [61832.472854] config - if there is no relations between the [61832.472854] names, then host name confusion attack is possible. Apr 26 09:14:42 192.168.122.209 [61832.637692] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:14:42 192.168.122.209 [61832.679821] [tempesta fw] Configuration processing is completed. Apr 26 09:14:42 192.168.122.209 [61832.736123] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:14:42 192.168.122.209 [61833.156134] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:14:42 192.168.122.209 [61833.181260] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:14:42 192.168.122.209 [61833.207675] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:14:42 192.168.122.209 [61833.247584] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:14:42 192.168.122.209 [61833.249293] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:14:42 192.168.122.209 [61833.287533] [tempesta fw] Tempesta FW is ready Apr 26 09:14:43 192.168.122.209 [61833.882906] [tdb] Close table 'client0.tdb' Apr 26 09:14:43 192.168.122.209 [61834.063941] [tdb] Close table 'sessions0.tdb' Apr 26 09:14:46 192.168.122.209 [61837.233318] [tdb] Close table 'cache0.tdb' Apr 26 09:14:46 192.168.122.209 [61837.470891] [tdb] Close table 'filter0.tdb' Apr 26 09:14:46 192.168.122.209 [61837.471311] [tempesta fw] modules are stopped Apr 26 09:14:47 192.168.122.209 [61837.681132] [tempesta fw] exiting... Apr 26 09:14:47 192.168.122.209 [61837.843757] [tdb] Shutdown Tempesta DB Apr 26 09:14:47 192.168.122.209 [61838.061373] End test: sessions.test_js_challenge.JSChallengeH2.test_resp_code_403 Apr 26 09:14:47 192.168.122.209 [61838.081785] Start test: sessions.test_js_challenge.JSChallengeH2.test_resp_code_default Apr 26 09:14:48 192.168.122.209 [61839.132833] [tdb] Start Tempesta DB Apr 26 09:14:48 192.168.122.209 [61839.281243] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:14:50 192.168.122.209 [61841.272672] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61841.272672] Maybe that's fine, but it's worth checking the [61841.272672] config - if there is no relations between the [61841.272672] names, then host name confusion attack is possible. Apr 26 09:14:50 192.168.122.209 [61841.441604] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:14:50 192.168.122.209 [61841.483791] [tempesta fw] Configuration processing is completed. Apr 26 09:14:50 192.168.122.209 [61841.534328] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:14:51 192.168.122.209 [61841.936597] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:14:51 192.168.122.209 [61841.973059] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:14:51 192.168.122.209 [61841.999285] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:14:51 192.168.122.209 [61842.043702] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:14:51 192.168.122.209 [61842.045411] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:14:51 192.168.122.209 [61842.087655] [tempesta fw] Tempesta FW is ready Apr 26 09:14:52 192.168.122.209 [61842.716979] [tdb] Close table 'client0.tdb' Apr 26 09:14:52 192.168.122.209 [61842.922141] [tdb] Close table 'sessions0.tdb' Apr 26 09:14:55 192.168.122.209 [61846.122631] [tdb] Close table 'cache0.tdb' Apr 26 09:14:55 192.168.122.209 [61846.370976] [tdb] Close table 'filter0.tdb' Apr 26 09:14:55 192.168.122.209 [61846.371412] [tempesta fw] modules are stopped Apr 26 09:14:56 192.168.122.209 [61846.599690] [tempesta fw] exiting... Apr 26 09:14:56 192.168.122.209 [61846.720897] [tdb] Shutdown Tempesta DB Apr 26 09:14:56 192.168.122.209 [61846.901750] End test: sessions.test_js_challenge.JSChallengeH2.test_resp_code_default Apr 26 09:14:56 192.168.122.209 [61846.913885] Start test: sessions.test_js_challenge.JSChallengeH2.test_restart_js_challenge Apr 26 09:14:57 192.168.122.209 [61847.998455] [tdb] Start Tempesta DB Apr 26 09:14:57 192.168.122.209 [61848.127048] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:14:59 192.168.122.209 [61850.197081] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61850.197081] Maybe that's fine, but it's worth checking the [61850.197081] config - if there is no relations between the [61850.197081] names, then host name confusion attack is possible. Apr 26 09:14:59 192.168.122.209 [61850.373937] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:14:59 192.168.122.209 [61850.423846] [tempesta fw] Configuration processing is completed. Apr 26 09:14:59 192.168.122.209 [61850.479224] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:15:00 192.168.122.209 [61850.884951] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:15:00 192.168.122.209 [61850.910587] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:15:00 192.168.122.209 [61850.936141] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:15:00 192.168.122.209 [61850.983839] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:15:00 192.168.122.209 [61850.985578] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:15:00 192.168.122.209 [61851.027760] [tempesta fw] Tempesta FW is ready Apr 26 09:15:00 192.168.122.209 [61851.221261] [tempesta fw] Warning: http_sess: bad received HMAC value for 127.0.0.2 f(pos=0), ts=0x100116a72 orig_hmac=[dbe9a313ab8d0a5ffa2fbfa7c0ba189d877f9b81] Apr 26 09:15:03 192.168.122.209 [61853.807485] [tdb] Close table 'client0.tdb' Apr 26 09:15:03 192.168.122.209 [61853.992107] [tdb] Close table 'sessions0.tdb' Apr 26 09:15:06 192.168.122.209 [61857.140949] [tdb] Close table 'cache0.tdb' Apr 26 09:15:06 192.168.122.209 [61857.360105] [tdb] Close table 'filter0.tdb' Apr 26 09:15:06 192.168.122.209 [61857.360529] [tempesta fw] modules are stopped Apr 26 09:15:06 192.168.122.209 [61857.545902] [tempesta fw] exiting... Apr 26 09:15:07 192.168.122.209 [61857.658930] [tdb] Shutdown Tempesta DB Apr 26 09:15:07 192.168.122.209 [61857.847114] End test: sessions.test_js_challenge.JSChallengeH2.test_restart_js_challenge Apr 26 09:15:07 192.168.122.209 [61857.861403] Start test: sessions.test_js_challenge.JSChallengeH2.test_second_request_GET_and_accept_all Apr 26 09:15:08 192.168.122.209 [61858.950541] [tdb] Start Tempesta DB Apr 26 09:15:08 192.168.122.209 [61859.078651] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:15:10 192.168.122.209 [61861.013198] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61861.013198] Maybe that's fine, but it's worth checking the [61861.013198] config - if there is no relations between the [61861.013198] names, then host name confusion attack is possible. Apr 26 09:15:10 192.168.122.209 [61861.181978] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:15:10 192.168.122.209 [61861.223958] [tempesta fw] Configuration processing is completed. Apr 26 09:15:10 192.168.122.209 [61861.274771] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:15:11 192.168.122.209 [61861.681069] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:15:11 192.168.122.209 [61861.706530] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:15:11 192.168.122.209 [61861.732411] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:15:11 192.168.122.209 [61861.779970] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:15:11 192.168.122.209 [61861.781662] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:15:11 192.168.122.209 [61861.819860] [tempesta fw] Tempesta FW is ready Apr 26 09:15:13 192.168.122.209 [61864.300563] [tdb] Close table 'client0.tdb' Apr 26 09:15:13 192.168.122.209 [61864.487321] [tdb] Close table 'sessions0.tdb' Apr 26 09:15:17 192.168.122.209 [61867.687732] [tdb] Close table 'cache0.tdb' Apr 26 09:15:17 192.168.122.209 [61867.949627] [tdb] Close table 'filter0.tdb' Apr 26 09:15:17 192.168.122.209 [61867.950053] [tempesta fw] modules are stopped Apr 26 09:15:17 192.168.122.209 [61868.128495] [tempesta fw] exiting... Apr 26 09:15:17 192.168.122.209 [61868.256905] [tdb] Shutdown Tempesta DB Apr 26 09:15:17 192.168.122.209 [61868.489283] End test: sessions.test_js_challenge.JSChallengeH2.test_second_request_GET_and_accept_all Apr 26 09:15:17 192.168.122.209 [61868.509506] Start test: sessions.test_js_challenge.JSChallengeH2.test_second_request_POST Apr 26 09:15:18 192.168.122.209 [61869.578531] [tdb] Start Tempesta DB Apr 26 09:15:19 192.168.122.209 [61869.712688] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:15:21 192.168.122.209 [61871.777289] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61871.777289] Maybe that's fine, but it's worth checking the [61871.777289] config - if there is no relations between the [61871.777289] names, then host name confusion attack is possible. Apr 26 09:15:21 192.168.122.209 [61871.942136] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:15:21 192.168.122.209 [61871.984189] [tempesta fw] Configuration processing is completed. Apr 26 09:15:21 192.168.122.209 [61872.042977] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:15:21 192.168.122.209 [61872.456575] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:15:21 192.168.122.209 [61872.482938] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:15:21 192.168.122.209 [61872.508880] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:15:21 192.168.122.209 [61872.564101] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:15:21 192.168.122.209 [61872.565820] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:15:22 192.168.122.209 [61872.604055] [tempesta fw] Tempesta FW is ready Apr 26 09:15:24 192.168.122.209 [61874.708603] [tdb] Close table 'client0.tdb' Apr 26 09:15:24 192.168.122.209 [61874.891591] [tdb] Close table 'sessions0.tdb' Apr 26 09:15:27 192.168.122.209 [61878.081318] [tdb] Close table 'cache0.tdb' Apr 26 09:15:27 192.168.122.209 [61878.335360] [tdb] Close table 'filter0.tdb' Apr 26 09:15:27 192.168.122.209 [61878.335765] [tempesta fw] modules are stopped Apr 26 09:15:27 192.168.122.209 [61878.559247] [tempesta fw] exiting... Apr 26 09:15:28 192.168.122.209 [61878.675850] [tdb] Shutdown Tempesta DB Apr 26 09:15:28 192.168.122.209 [61878.855073] End test: sessions.test_js_challenge.JSChallengeH2.test_second_request_POST Apr 26 09:15:28 192.168.122.209 [61878.866628] Start test: sessions.test_js_challenge.JSChallengeH2.test_servicing_non_challengeble_request_from_cache_GET Apr 26 09:15:29 192.168.122.209 [61879.913539] [tdb] Start Tempesta DB Apr 26 09:15:29 192.168.122.209 [61880.042053] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:15:31 192.168.122.209 [61882.013489] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61882.013489] Maybe that's fine, but it's worth checking the [61882.013489] config - if there is no relations between the [61882.013489] names, then host name confusion attack is possible. Apr 26 09:15:31 192.168.122.209 [61882.198383] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:15:31 192.168.122.209 [61882.244244] [tempesta fw] Configuration processing is completed. Apr 26 09:15:31 192.168.122.209 [61882.300301] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:15:32 192.168.122.209 [61882.704057] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:15:32 192.168.122.209 [61882.729640] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:15:32 192.168.122.209 [61882.755889] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:15:32 192.168.122.209 [61882.804233] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:15:32 192.168.122.209 [61882.805975] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:15:32 192.168.122.209 [61882.852174] [tempesta fw] Tempesta FW is ready Apr 26 09:15:34 192.168.122.209 [61884.626209] [tdb] Close table 'client0.tdb' Apr 26 09:15:34 192.168.122.209 [61884.809687] [tdb] Close table 'sessions0.tdb' Apr 26 09:15:37 192.168.122.209 [61887.967524] [tdb] Close table 'cache0.tdb' Apr 26 09:15:37 192.168.122.209 [61888.197010] [tdb] Close table 'filter0.tdb' Apr 26 09:15:37 192.168.122.209 [61888.197438] [tempesta fw] modules are stopped Apr 26 09:15:37 192.168.122.209 [61888.418432] [tempesta fw] exiting... Apr 26 09:15:37 192.168.122.209 [61888.540745] [tdb] Shutdown Tempesta DB Apr 26 09:15:38 192.168.122.209 [61888.738583] End test: sessions.test_js_challenge.JSChallengeH2.test_servicing_non_challengeble_request_from_cache_GET Apr 26 09:15:38 192.168.122.209 [61888.762108] Start test: sessions.test_js_challenge.JSChallengeH2.test_servicing_non_challengeble_request_from_cache_HEAD Apr 26 09:15:39 192.168.122.209 [61889.769528] [tdb] Start Tempesta DB Apr 26 09:15:39 192.168.122.209 [61889.909566] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:15:42 192.168.122.209 [61892.689825] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61892.689825] Maybe that's fine, but it's worth checking the [61892.689825] config - if there is no relations between the [61892.689825] names, then host name confusion attack is possible. Apr 26 09:15:43 192.168.122.209 [61894.455233] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:15:44 192.168.122.209 [61894.692797] [tempesta fw] Configuration processing is completed. Apr 26 09:15:44 192.168.122.209 [61894.781310] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:15:44 192.168.122.209 [61895.250803] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:15:44 192.168.122.209 [61895.354457] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:15:44 192.168.122.209 [61895.481776] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:15:45 192.168.122.209 [61895.900437] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:15:45 192.168.122.209 [61895.902438] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:15:45 192.168.122.209 [61896.132346] [tempesta fw] Tempesta FW is ready Apr 26 09:15:47 192.168.122.209 [61898.219059] [tdb] Close table 'client0.tdb' Apr 26 09:15:47 192.168.122.209 [61898.409676] [tdb] Close table 'sessions0.tdb' Apr 26 09:15:50 192.168.122.209 [61901.553966] [tdb] Close table 'cache0.tdb' Apr 26 09:15:51 192.168.122.209 [61901.781636] [tdb] Close table 'filter0.tdb' Apr 26 09:15:51 192.168.122.209 [61901.782092] [tempesta fw] modules are stopped Apr 26 09:15:51 192.168.122.209 [61901.966891] [tempesta fw] exiting... Apr 26 09:15:51 192.168.122.209 [61902.115718] [tdb] Shutdown Tempesta DB Apr 26 09:15:51 192.168.122.209 [61902.324600] End test: sessions.test_js_challenge.JSChallengeH2.test_servicing_non_challengeble_request_from_cache_HEAD Apr 26 09:15:51 192.168.122.209 [61902.336835] Start test: sessions.test_js_challenge.JSChallengeH2.test_servicing_non_challengeble_request_from_cache_POST Apr 26 09:15:52 192.168.122.209 [61903.379288] [tdb] Start Tempesta DB Apr 26 09:15:52 192.168.122.209 [61903.511778] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:15:54 192.168.122.209 [61905.421794] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61905.421794] Maybe that's fine, but it's worth checking the [61905.421794] config - if there is no relations between the [61905.421794] names, then host name confusion attack is possible. Apr 26 09:15:55 192.168.122.209 [61905.586550] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:15:55 192.168.122.209 [61905.622043] [tempesta fw] Configuration processing is completed. Apr 26 09:15:55 192.168.122.209 [61905.676060] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:15:55 192.168.122.209 [61906.085120] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:15:55 192.168.122.209 [61906.122162] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:15:55 192.168.122.209 [61906.147118] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:15:55 192.168.122.209 [61906.188510] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:15:55 192.168.122.209 [61906.190246] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:15:55 192.168.122.209 [61906.236457] [tempesta fw] Tempesta FW is ready Apr 26 09:15:58 192.168.122.209 [61909.355409] [tdb] Close table 'client0.tdb' Apr 26 09:15:58 192.168.122.209 [61909.529793] [tdb] Close table 'sessions0.tdb' Apr 26 09:16:02 192.168.122.209 [61912.752957] [tdb] Close table 'cache0.tdb' Apr 26 09:16:02 192.168.122.209 [61913.008363] [tdb] Close table 'filter0.tdb' Apr 26 09:16:02 192.168.122.209 [61913.009144] [tempesta fw] modules are stopped Apr 26 09:16:02 192.168.122.209 [61913.208468] [tempesta fw] exiting... Apr 26 09:16:02 192.168.122.209 [61913.321899] [tdb] Shutdown Tempesta DB Apr 26 09:16:02 192.168.122.209 [61913.506713] End test: sessions.test_js_challenge.JSChallengeH2.test_servicing_non_challengeble_request_from_cache_POST Apr 26 09:16:02 192.168.122.209 [61913.571670] Start test: sessions.test_js_challenge.JSChallengeHttp.test_cookies_in_request_multiple_in_one Apr 26 09:16:04 192.168.122.209 [61914.588370] [tdb] Start Tempesta DB Apr 26 09:16:04 192.168.122.209 [61914.734852] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:16:06 192.168.122.209 [61916.746001] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61916.746001] Maybe that's fine, but it's worth checking the [61916.746001] config - if there is no relations between the [61916.746001] names, then host name confusion attack is possible. Apr 26 09:16:06 192.168.122.209 [61916.922620] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:16:06 192.168.122.209 [61916.980586] [tempesta fw] Configuration processing is completed. Apr 26 09:16:06 192.168.122.209 [61917.034728] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:16:06 192.168.122.209 [61917.482485] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:16:06 192.168.122.209 [61917.511988] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:16:06 192.168.122.209 [61917.540184] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:16:07 192.168.122.209 [61917.584607] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:16:07 192.168.122.209 [61917.585677] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:16:07 192.168.122.209 [61917.628642] [tempesta fw] Tempesta FW is ready Apr 26 09:16:10 192.168.122.209 [61921.292863] [tempesta fw] Warning: Multiple Tempesta sticky cookies found in request: 2 Apr 26 09:16:10 192.168.122.209 [61921.293609] [tempesta fw] Warning: request dropped: internal error in Sticky module: 127.0.0.2 Apr 26 09:16:11 192.168.122.209 [61921.710859] [tdb] Close table 'client0.tdb' Apr 26 09:16:11 192.168.122.209 [61921.889157] [tdb] Close table 'sessions0.tdb' Apr 26 09:16:14 192.168.122.209 [61925.089151] [tdb] Close table 'cache0.tdb' Apr 26 09:16:14 192.168.122.209 [61925.338969] [tdb] Close table 'filter0.tdb' Apr 26 09:16:14 192.168.122.209 [61925.339433] [tempesta fw] modules are stopped Apr 26 09:16:14 192.168.122.209 [61925.547166] [tempesta fw] exiting... Apr 26 09:16:15 192.168.122.209 [61925.650116] [tdb] Shutdown Tempesta DB Apr 26 09:16:15 192.168.122.209 [61925.826989] End test: sessions.test_js_challenge.JSChallengeHttp.test_cookies_in_request_multiple_in_one Apr 26 09:16:15 192.168.122.209 [61925.839719] Start test: sessions.test_js_challenge.JSChallengeHttp.test_cookies_in_request_multiple_in_two Apr 26 09:16:15 192.168.122.209 [61925.946654] End test: sessions.test_js_challenge.JSChallengeHttp.test_cookies_in_request_multiple_in_two Apr 26 09:16:15 192.168.122.209 [61925.960084] Start test: sessions.test_js_challenge.JSChallengeHttp.test_delay_pass Apr 26 09:16:16 192.168.122.209 [61927.019722] [tdb] Start Tempesta DB Apr 26 09:16:16 192.168.122.209 [61927.145691] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:16:18 192.168.122.209 [61929.086085] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61929.086085] Maybe that's fine, but it's worth checking the [61929.086085] config - if there is no relations between the [61929.086085] names, then host name confusion attack is possible. Apr 26 09:16:18 192.168.122.209 [61929.270063] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:16:18 192.168.122.209 [61929.308796] [tempesta fw] Configuration processing is completed. Apr 26 09:16:18 192.168.122.209 [61929.358277] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:16:19 192.168.122.209 [61929.759301] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:16:19 192.168.122.209 [61929.784587] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:16:19 192.168.122.209 [61929.818766] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:16:19 192.168.122.209 [61929.860810] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:16:19 192.168.122.209 [61929.862544] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:16:19 192.168.122.209 [61929.908767] [tempesta fw] Tempesta FW is ready Apr 26 09:16:22 192.168.122.209 [61932.771798] [tdb] Close table 'client0.tdb' Apr 26 09:16:22 192.168.122.209 [61932.957460] [tdb] Close table 'sessions0.tdb' Apr 26 09:16:25 192.168.122.209 [61936.148274] [tdb] Close table 'cache0.tdb' Apr 26 09:16:25 192.168.122.209 [61936.389771] [tdb] Close table 'filter0.tdb' Apr 26 09:16:25 192.168.122.209 [61936.390169] [tempesta fw] modules are stopped Apr 26 09:16:25 192.168.122.209 [61936.573227] [tempesta fw] exiting... Apr 26 09:16:26 192.168.122.209 [61936.705318] [tdb] Shutdown Tempesta DB Apr 26 09:16:26 192.168.122.209 [61936.915310] End test: sessions.test_js_challenge.JSChallengeHttp.test_delay_pass Apr 26 09:16:26 192.168.122.209 [61936.923960] Start test: sessions.test_js_challenge.JSChallengeHttp.test_delay_pipelined_pass Apr 26 09:16:27 192.168.122.209 [61937.972049] [tdb] Start Tempesta DB Apr 26 09:16:27 192.168.122.209 [61938.104726] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:16:29 192.168.122.209 [61940.082237] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61940.082237] Maybe that's fine, but it's worth checking the [61940.082237] config - if there is no relations between the [61940.082237] names, then host name confusion attack is possible. Apr 26 09:16:29 192.168.122.209 [61940.258965] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:16:29 192.168.122.209 [61940.313003] [tempesta fw] Configuration processing is completed. Apr 26 09:16:29 192.168.122.209 [61940.363975] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:16:30 192.168.122.209 [61940.761283] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:16:30 192.168.122.209 [61940.787252] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:16:30 192.168.122.209 [61940.812592] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:16:30 192.168.122.209 [61940.860962] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:16:30 192.168.122.209 [61940.862697] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:16:30 192.168.122.209 [61940.900899] [tempesta fw] Tempesta FW is ready Apr 26 09:16:32 192.168.122.209 [61943.559023] [tdb] Close table 'client0.tdb' Apr 26 09:16:33 192.168.122.209 [61943.763076] [tdb] Close table 'sessions0.tdb' Apr 26 09:16:36 192.168.122.209 [61946.961594] [tdb] Close table 'cache0.tdb' Apr 26 09:16:36 192.168.122.209 [61947.214913] [tdb] Close table 'filter0.tdb' Apr 26 09:16:36 192.168.122.209 [61947.215348] [tempesta fw] modules are stopped Apr 26 09:16:36 192.168.122.209 [61947.393272] [tempesta fw] exiting... Apr 26 09:16:36 192.168.122.209 [61947.516310] [tdb] Shutdown Tempesta DB Apr 26 09:16:37 192.168.122.209 [61947.745753] End test: sessions.test_js_challenge.JSChallengeHttp.test_delay_pipelined_pass Apr 26 09:16:37 192.168.122.209 [61947.754535] Start test: sessions.test_js_challenge.JSChallengeHttp.test_delay_pipelined_too_early Apr 26 09:16:38 192.168.122.209 [61948.800506] [tdb] Start Tempesta DB Apr 26 09:16:38 192.168.122.209 [61948.954218] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:16:40 192.168.122.209 [61950.934415] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61950.934415] Maybe that's fine, but it's worth checking the [61950.934415] config - if there is no relations between the [61950.934415] names, then host name confusion attack is possible. Apr 26 09:16:40 192.168.122.209 [61951.091192] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:16:40 192.168.122.209 [61951.137144] [tempesta fw] Configuration processing is completed. Apr 26 09:16:40 192.168.122.209 [61951.195402] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:16:41 192.168.122.209 [61951.642894] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:16:41 192.168.122.209 [61951.671149] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:16:41 192.168.122.209 [61951.700404] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:16:41 192.168.122.209 [61951.745107] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:16:41 192.168.122.209 [61951.746882] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:16:41 192.168.122.209 [61951.785048] [tempesta fw] Tempesta FW is ready Apr 26 09:16:41 192.168.122.209 [61951.965817] [tempesta fw] Warning: http_sess: jsch redirect received too early for 127.0.0.2 (4310379763 is not after 4310380192) Apr 26 09:16:41 192.168.122.209 [61951.966861] [tempesta fw] Warning: frang: max rmisses exceeded for 127.0.0.2: 3 (lim=2) Apr 26 09:16:41 192.168.122.209 [61952.366315] [tdb] Close table 'client0.tdb' Apr 26 09:16:41 192.168.122.209 [61952.576411] [tdb] Close table 'sessions0.tdb' Apr 26 09:16:45 192.168.122.209 [61955.719150] [tdb] Close table 'cache0.tdb' Apr 26 09:16:45 192.168.122.209 [61955.965923] [tdb] Close table 'filter0.tdb' Apr 26 09:16:45 192.168.122.209 [61955.966360] [tempesta fw] modules are stopped Apr 26 09:16:45 192.168.122.209 [61956.175676] [tempesta fw] exiting... Apr 26 09:16:45 192.168.122.209 [61956.281241] [tdb] Shutdown Tempesta DB Apr 26 09:16:45 192.168.122.209 [61956.507103] End test: sessions.test_js_challenge.JSChallengeHttp.test_delay_pipelined_too_early Apr 26 09:16:45 192.168.122.209 [61956.518519] Start test: sessions.test_js_challenge.JSChallengeHttp.test_delay_too_small Apr 26 09:16:46 192.168.122.209 [61957.542478] [tdb] Start Tempesta DB Apr 26 09:16:47 192.168.122.209 [61957.665286] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:16:49 192.168.122.209 [61959.714438] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61959.714438] Maybe that's fine, but it's worth checking the [61959.714438] config - if there is no relations between the [61959.714438] names, then host name confusion attack is possible. Apr 26 09:16:49 192.168.122.209 [61959.911352] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:16:49 192.168.122.209 [61959.953197] [tempesta fw] Configuration processing is completed. Apr 26 09:16:49 192.168.122.209 [61960.013176] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:16:49 192.168.122.209 [61960.418560] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:16:49 192.168.122.209 [61960.456859] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:16:49 192.168.122.209 [61960.482647] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:16:49 192.168.122.209 [61960.545261] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:16:49 192.168.122.209 [61960.547018] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:16:50 192.168.122.209 [61960.585160] [tempesta fw] Tempesta FW is ready Apr 26 09:16:50 192.168.122.209 [61960.741532] [tempesta fw] Warning: http_sess: jsch redirect received too early for 127.0.0.2 (4310381957 is not after 4310382563) Apr 26 09:16:50 192.168.122.209 [61961.172660] [tdb] Close table 'client0.tdb' Apr 26 09:16:50 192.168.122.209 [61961.359659] [tdb] Close table 'sessions0.tdb' Apr 26 09:16:53 192.168.122.209 [61964.500264] [tdb] Close table 'cache0.tdb' Apr 26 09:16:54 192.168.122.209 [61964.720824] [tdb] Close table 'filter0.tdb' Apr 26 09:16:54 192.168.122.209 [61964.721269] [tempesta fw] modules are stopped Apr 26 09:16:54 192.168.122.209 [61964.954643] [tempesta fw] exiting... Apr 26 09:16:54 192.168.122.209 [61965.072527] [tdb] Shutdown Tempesta DB Apr 26 09:16:54 192.168.122.209 [61965.271169] End test: sessions.test_js_challenge.JSChallengeHttp.test_delay_too_small Apr 26 09:16:54 192.168.122.209 [61965.290743] Start test: sessions.test_js_challenge.JSChallengeHttp.test_disable_challenge_on_reload Apr 26 09:16:55 192.168.122.209 [61966.292331] [tdb] Start Tempesta DB Apr 26 09:16:55 192.168.122.209 [61966.424791] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:16:57 192.168.122.209 [61968.366580] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61968.366580] Maybe that's fine, but it's worth checking the [61968.366580] config - if there is no relations between the [61968.366580] names, then host name confusion attack is possible. Apr 26 09:16:57 192.168.122.209 [61968.523419] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:16:57 192.168.122.209 [61968.569377] [tempesta fw] Configuration processing is completed. Apr 26 09:16:58 192.168.122.209 [61968.625582] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:16:58 192.168.122.209 [61969.045448] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:16:58 192.168.122.209 [61969.070748] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:16:58 192.168.122.209 [61969.095806] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:16:58 192.168.122.209 [61969.137346] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:16:58 192.168.122.209 [61969.139077] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:16:58 192.168.122.209 [61969.177220] [tempesta fw] Tempesta FW is ready Apr 26 09:16:59 192.168.122.209 [61969.867368] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 09:16:59 192.168.122.209 [61969.934606] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61969.934606] Maybe that's fine, but it's worth checking the [61969.934606] config - if there is no relations between the [61969.934606] names, then host name confusion attack is possible. Apr 26 09:16:59 192.168.122.209 [61970.213675] [tempesta fw] Configuration processing is completed. Apr 26 09:16:59 192.168.122.209 [61970.485834] [tempesta fw] Tempesta FW is ready Apr 26 09:17:00 192.168.122.209 [61971.010486] [tdb] Close table 'client0.tdb' Apr 26 09:17:00 192.168.122.209 [61971.191206] [tdb] Close table 'sessions0.tdb' Apr 26 09:17:03 192.168.122.209 [61974.342486] [tdb] Close table 'cache0.tdb' Apr 26 09:17:04 192.168.122.209 [61974.598880] [tdb] Close table 'filter0.tdb' Apr 26 09:17:04 192.168.122.209 [61974.599324] [tempesta fw] modules are stopped Apr 26 09:17:04 192.168.122.209 [61974.783422] [tempesta fw] exiting... Apr 26 09:17:04 192.168.122.209 [61974.885532] [tdb] Shutdown Tempesta DB Apr 26 09:17:04 192.168.122.209 [61975.114052] End test: sessions.test_js_challenge.JSChallengeHttp.test_disable_challenge_on_reload Apr 26 09:17:04 192.168.122.209 [61975.140213] Start test: sessions.test_js_challenge.JSChallengeHttp.test_enable_challenge_on_reload Apr 26 09:17:05 192.168.122.209 [61976.239759] [tdb] Start Tempesta DB Apr 26 09:17:05 192.168.122.209 [61976.379316] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:17:07 192.168.122.209 [61978.130743] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61978.130743] Maybe that's fine, but it's worth checking the [61978.130743] config - if there is no relations between the [61978.130743] names, then host name confusion attack is possible. Apr 26 09:17:07 192.168.122.209 [61978.341483] [tempesta fw] Configuration processing is completed. Apr 26 09:17:07 192.168.122.209 [61978.408823] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:17:08 192.168.122.209 [61978.815844] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:17:08 192.168.122.209 [61978.841270] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:17:08 192.168.122.209 [61978.866441] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:17:08 192.168.122.209 [61978.913479] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:17:08 192.168.122.209 [61978.915194] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:17:08 192.168.122.209 [61978.957389] [tempesta fw] Tempesta FW is ready Apr 26 09:17:09 192.168.122.209 [61979.971654] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 09:17:09 192.168.122.209 [61980.054732] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61980.054732] Maybe that's fine, but it's worth checking the [61980.054732] config - if there is no relations between the [61980.054732] names, then host name confusion attack is possible. Apr 26 09:17:09 192.168.122.209 [61980.295525] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:17:09 192.168.122.209 [61980.341434] [tempesta fw] Configuration processing is completed. Apr 26 09:17:10 192.168.122.209 [61980.637557] [tempesta fw] Tempesta FW is ready Apr 26 09:17:12 192.168.122.209 [61982.593552] [tdb] Close table 'client0.tdb' Apr 26 09:17:12 192.168.122.209 [61982.801387] [tdb] Close table 'sessions0.tdb' Apr 26 09:17:15 192.168.122.209 [61986.089221] [tdb] Close table 'cache0.tdb' Apr 26 09:17:15 192.168.122.209 [61986.336285] [tdb] Close table 'filter0.tdb' Apr 26 09:17:15 192.168.122.209 [61986.336732] [tempesta fw] modules are stopped Apr 26 09:17:15 192.168.122.209 [61986.520424] [tempesta fw] exiting... Apr 26 09:17:16 192.168.122.209 [61986.650466] [tdb] Shutdown Tempesta DB Apr 26 09:17:16 192.168.122.209 [61986.840803] End test: sessions.test_js_challenge.JSChallengeHttp.test_enable_challenge_on_reload Apr 26 09:17:16 192.168.122.209 [61986.852735] Start test: sessions.test_js_challenge.JSChallengeHttp.test_first_post_request_pipelined Apr 26 09:17:17 192.168.122.209 [61987.889512] [tdb] Start Tempesta DB Apr 26 09:17:17 192.168.122.209 [61988.044389] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:17:19 192.168.122.209 [61990.006878] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61990.006878] Maybe that's fine, but it's worth checking the [61990.006878] config - if there is no relations between the [61990.006878] names, then host name confusion attack is possible. Apr 26 09:17:19 192.168.122.209 [61990.175699] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:17:19 192.168.122.209 [61990.213793] [tempesta fw] Configuration processing is completed. Apr 26 09:17:19 192.168.122.209 [61990.278527] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:17:20 192.168.122.209 [61990.721444] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:17:20 192.168.122.209 [61990.747814] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:17:20 192.168.122.209 [61990.777252] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:17:20 192.168.122.209 [61990.817605] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:17:20 192.168.122.209 [61990.819394] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:17:20 192.168.122.209 [61990.857554] [tempesta fw] Tempesta FW is ready Apr 26 09:17:21 192.168.122.209 [61992.558074] [tdb] Close table 'client0.tdb' Apr 26 09:17:22 192.168.122.209 [61992.734379] [tdb] Close table 'sessions0.tdb' Apr 26 09:17:25 192.168.122.209 [61996.010241] [tdb] Close table 'cache0.tdb' Apr 26 09:17:25 192.168.122.209 [61996.266804] [tdb] Close table 'filter0.tdb' Apr 26 09:17:25 192.168.122.209 [61996.267241] [tempesta fw] modules are stopped Apr 26 09:17:25 192.168.122.209 [61996.490540] [tempesta fw] exiting... Apr 26 09:17:26 192.168.122.209 [61996.609203] [tdb] Shutdown Tempesta DB Apr 26 09:17:26 192.168.122.209 [61996.801648] End test: sessions.test_js_challenge.JSChallengeHttp.test_first_post_request_pipelined Apr 26 09:17:26 192.168.122.209 [61996.814610] Start test: sessions.test_js_challenge.JSChallengeHttp.test_first_request_GET_and_accept_all Apr 26 09:17:27 192.168.122.209 [61997.849707] [tdb] Start Tempesta DB Apr 26 09:17:27 192.168.122.209 [61997.991620] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:17:29 192.168.122.209 [61999.975077] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [61999.975077] Maybe that's fine, but it's worth checking the [61999.975077] config - if there is no relations between the [61999.975077] names, then host name confusion attack is possible. Apr 26 09:17:29 192.168.122.209 [62000.139786] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:17:29 192.168.122.209 [62000.174030] [tempesta fw] Configuration processing is completed. Apr 26 09:17:29 192.168.122.209 [62000.227339] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:17:30 192.168.122.209 [62000.686661] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:17:30 192.168.122.209 [62000.714906] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:17:30 192.168.122.209 [62000.744151] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:17:30 192.168.122.209 [62000.797752] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:17:30 192.168.122.209 [62000.799505] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:17:30 192.168.122.209 [62000.853696] [tempesta fw] Tempesta FW is ready Apr 26 09:17:30 192.168.122.209 [62001.379848] [tdb] Close table 'client0.tdb' Apr 26 09:17:30 192.168.122.209 [62001.569557] [tdb] Close table 'sessions0.tdb' Apr 26 09:17:34 192.168.122.209 [62004.744316] [tdb] Close table 'cache0.tdb' Apr 26 09:17:34 192.168.122.209 [62004.984592] [tdb] Close table 'filter0.tdb' Apr 26 09:17:34 192.168.122.209 [62004.985008] [tempesta fw] modules are stopped Apr 26 09:17:34 192.168.122.209 [62005.200828] [tempesta fw] exiting... Apr 26 09:17:34 192.168.122.209 [62005.362432] [tdb] Shutdown Tempesta DB Apr 26 09:17:35 192.168.122.209 [62005.599389] End test: sessions.test_js_challenge.JSChallengeHttp.test_first_request_GET_and_accept_all Apr 26 09:17:35 192.168.122.209 [62005.613886] Start test: sessions.test_js_challenge.JSChallengeHttp.test_first_request_GET_and_accept_html Apr 26 09:17:36 192.168.122.209 [62006.613144] [tdb] Start Tempesta DB Apr 26 09:17:36 192.168.122.209 [62006.753788] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:17:38 192.168.122.209 [62008.731143] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62008.731143] Maybe that's fine, but it's worth checking the [62008.731143] config - if there is no relations between the [62008.731143] names, then host name confusion attack is possible. Apr 26 09:17:38 192.168.122.209 [62008.895855] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:17:38 192.168.122.209 [62008.934133] [tempesta fw] Configuration processing is completed. Apr 26 09:17:38 192.168.122.209 [62008.984666] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:17:38 192.168.122.209 [62009.453492] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:17:38 192.168.122.209 [62009.482830] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:17:38 192.168.122.209 [62009.514107] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:17:38 192.168.122.209 [62009.569846] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:17:38 192.168.122.209 [62009.571613] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:17:39 192.168.122.209 [62009.613811] [tempesta fw] Tempesta FW is ready Apr 26 09:17:39 192.168.122.209 [62010.197001] [tdb] Close table 'client0.tdb' Apr 26 09:17:39 192.168.122.209 [62010.373163] [tdb] Close table 'sessions0.tdb' Apr 26 09:17:43 192.168.122.209 [62013.617314] [tdb] Close table 'cache0.tdb' Apr 26 09:17:43 192.168.122.209 [62013.859722] [tdb] Close table 'filter0.tdb' Apr 26 09:17:43 192.168.122.209 [62013.860134] [tempesta fw] modules are stopped Apr 26 09:17:43 192.168.122.209 [62014.089482] [tempesta fw] exiting... Apr 26 09:17:43 192.168.122.209 [62014.238214] [tdb] Shutdown Tempesta DB Apr 26 09:17:43 192.168.122.209 [62014.493211] End test: sessions.test_js_challenge.JSChallengeHttp.test_first_request_GET_and_accept_html Apr 26 09:17:43 192.168.122.209 [62014.509184] Start test: sessions.test_js_challenge.JSChallengeHttp.test_first_request_GET_and_accept_image Apr 26 09:17:44 192.168.122.209 [62015.581355] [tdb] Start Tempesta DB Apr 26 09:17:45 192.168.122.209 [62015.726021] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:17:47 192.168.122.209 [62017.779259] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62017.779259] Maybe that's fine, but it's worth checking the [62017.779259] config - if there is no relations between the [62017.779259] names, then host name confusion attack is possible. Apr 26 09:17:47 192.168.122.209 [62017.939989] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:17:47 192.168.122.209 [62017.985928] [tempesta fw] Configuration processing is completed. Apr 26 09:17:47 192.168.122.209 [62018.040096] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:17:47 192.168.122.209 [62018.440925] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:17:47 192.168.122.209 [62018.466780] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:17:47 192.168.122.209 [62018.493254] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:17:47 192.168.122.209 [62018.553938] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:17:47 192.168.122.209 [62018.555695] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:17:48 192.168.122.209 [62018.593918] [tempesta fw] Tempesta FW is ready Apr 26 09:17:48 192.168.122.209 [62019.152821] [tdb] Close table 'client0.tdb' Apr 26 09:17:48 192.168.122.209 [62019.357324] [tdb] Close table 'sessions0.tdb' Apr 26 09:17:52 192.168.122.209 [62022.620338] [tdb] Close table 'cache0.tdb' Apr 26 09:17:52 192.168.122.209 [62022.863038] [tdb] Close table 'filter0.tdb' Apr 26 09:17:52 192.168.122.209 [62022.863486] [tempesta fw] modules are stopped Apr 26 09:17:52 192.168.122.209 [62023.084026] [tempesta fw] exiting... Apr 26 09:17:52 192.168.122.209 [62023.218673] [tdb] Shutdown Tempesta DB Apr 26 09:17:52 192.168.122.209 [62023.434923] End test: sessions.test_js_challenge.JSChallengeHttp.test_first_request_GET_and_accept_image Apr 26 09:17:52 192.168.122.209 [62023.456421] Start test: sessions.test_js_challenge.JSChallengeHttp.test_first_request_GET_and_accept_plain Apr 26 09:17:54 192.168.122.209 [62024.662937] [tdb] Start Tempesta DB Apr 26 09:17:54 192.168.122.209 [62024.845865] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:17:56 192.168.122.209 [62027.047509] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62027.047509] Maybe that's fine, but it's worth checking the [62027.047509] config - if there is no relations between the [62027.047509] names, then host name confusion attack is possible. Apr 26 09:17:56 192.168.122.209 [62027.212274] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:17:56 192.168.122.209 [62027.246383] [tempesta fw] Configuration processing is completed. Apr 26 09:17:56 192.168.122.209 [62027.297496] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:17:57 192.168.122.209 [62027.833565] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:17:57 192.168.122.209 [62027.868405] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:17:57 192.168.122.209 [62027.904478] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:17:57 192.168.122.209 [62027.958097] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:17:57 192.168.122.209 [62027.959875] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:17:57 192.168.122.209 [62027.998029] [tempesta fw] Tempesta FW is ready Apr 26 09:17:57 192.168.122.209 [62028.582331] [tdb] Close table 'client0.tdb' Apr 26 09:17:58 192.168.122.209 [62028.801997] [tdb] Close table 'sessions0.tdb' Apr 26 09:18:01 192.168.122.209 [62032.112581] [tdb] Close table 'cache0.tdb' Apr 26 09:18:01 192.168.122.209 [62032.354557] [tdb] Close table 'filter0.tdb' Apr 26 09:18:01 192.168.122.209 [62032.354991] [tempesta fw] modules are stopped Apr 26 09:18:01 192.168.122.209 [62032.532476] [tempesta fw] exiting... Apr 26 09:18:02 192.168.122.209 [62032.657422] [tdb] Shutdown Tempesta DB Apr 26 09:18:02 192.168.122.209 [62032.857210] End test: sessions.test_js_challenge.JSChallengeHttp.test_first_request_GET_and_accept_plain Apr 26 09:18:02 192.168.122.209 [62032.865003] Start test: sessions.test_js_challenge.JSChallengeHttp.test_first_request_GET_and_accept_text_all Apr 26 09:18:03 192.168.122.209 [62034.127596] [tdb] Start Tempesta DB Apr 26 09:18:03 192.168.122.209 [62034.282349] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:18:05 192.168.122.209 [62036.387441] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62036.387441] Maybe that's fine, but it's worth checking the [62036.387441] config - if there is no relations between the [62036.387441] names, then host name confusion attack is possible. Apr 26 09:18:05 192.168.122.209 [62036.572277] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:18:06 192.168.122.209 [62036.610199] [tempesta fw] Configuration processing is completed. Apr 26 09:18:06 192.168.122.209 [62036.668287] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:18:06 192.168.122.209 [62037.076724] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:18:06 192.168.122.209 [62037.102890] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:18:06 192.168.122.209 [62037.130861] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:18:06 192.168.122.209 [62037.186252] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:18:06 192.168.122.209 [62037.188041] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:18:06 192.168.122.209 [62037.227661] [tempesta fw] Tempesta FW is ready Apr 26 09:18:07 192.168.122.209 [62037.842096] [tdb] Close table 'client0.tdb' Apr 26 09:18:07 192.168.122.209 [62038.032363] [tdb] Close table 'sessions0.tdb' Apr 26 09:18:10 192.168.122.209 [62041.283545] [tdb] Close table 'cache0.tdb' Apr 26 09:18:10 192.168.122.209 [62041.532434] [tdb] Close table 'filter0.tdb' Apr 26 09:18:10 192.168.122.209 [62041.532898] [tempesta fw] modules are stopped Apr 26 09:18:11 192.168.122.209 [62041.742667] [tempesta fw] exiting... Apr 26 09:18:11 192.168.122.209 [62041.865244] [tdb] Shutdown Tempesta DB Apr 26 09:18:11 192.168.122.209 [62042.067668] End test: sessions.test_js_challenge.JSChallengeHttp.test_first_request_GET_and_accept_text_all Apr 26 09:18:11 192.168.122.209 [62042.075908] Start test: sessions.test_js_challenge.JSChallengeHttp.test_first_request_POST Apr 26 09:18:12 192.168.122.209 [62043.207724] [tdb] Start Tempesta DB Apr 26 09:18:12 192.168.122.209 [62043.355591] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:18:14 192.168.122.209 [62045.547629] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62045.547629] Maybe that's fine, but it's worth checking the [62045.547629] config - if there is no relations between the [62045.547629] names, then host name confusion attack is possible. Apr 26 09:18:15 192.168.122.209 [62045.708345] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:18:15 192.168.122.209 [62045.750322] [tempesta fw] Configuration processing is completed. Apr 26 09:18:15 192.168.122.209 [62045.802553] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:18:15 192.168.122.209 [62046.209670] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:18:15 192.168.122.209 [62046.235351] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:18:15 192.168.122.209 [62046.262886] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:18:15 192.168.122.209 [62046.306317] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:18:15 192.168.122.209 [62046.308083] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:18:15 192.168.122.209 [62046.350259] [tempesta fw] Tempesta FW is ready Apr 26 09:18:16 192.168.122.209 [62046.984760] [tdb] Close table 'client0.tdb' Apr 26 09:18:16 192.168.122.209 [62047.176111] [tdb] Close table 'sessions0.tdb' Apr 26 09:18:19 192.168.122.209 [62050.400031] [tdb] Close table 'cache0.tdb' Apr 26 09:18:20 192.168.122.209 [62050.637708] [tdb] Close table 'filter0.tdb' Apr 26 09:18:20 192.168.122.209 [62050.638182] [tempesta fw] modules are stopped Apr 26 09:18:20 192.168.122.209 [62050.820777] [tempesta fw] exiting... Apr 26 09:18:20 192.168.122.209 [62050.920071] [tdb] Shutdown Tempesta DB Apr 26 09:18:20 192.168.122.209 [62051.109009] End test: sessions.test_js_challenge.JSChallengeHttp.test_first_request_POST Apr 26 09:18:20 192.168.122.209 [62051.122394] Start test: sessions.test_js_challenge.JSChallengeHttp.test_method_override_GET_HEAD Apr 26 09:18:21 192.168.122.209 [62052.168833] [tdb] Start Tempesta DB Apr 26 09:18:21 192.168.122.209 [62052.322729] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:18:23 192.168.122.209 [62054.311713] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62054.311713] Maybe that's fine, but it's worth checking the [62054.311713] config - if there is no relations between the [62054.311713] names, then host name confusion attack is possible. Apr 26 09:18:23 192.168.122.209 [62054.480464] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:18:23 192.168.122.209 [62054.518502] [tempesta fw] Configuration processing is completed. Apr 26 09:18:23 192.168.122.209 [62054.570083] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:18:24 192.168.122.209 [62055.024032] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:18:24 192.168.122.209 [62055.051684] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:18:24 192.168.122.209 [62055.082635] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:18:24 192.168.122.209 [62055.122427] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:18:24 192.168.122.209 [62055.124233] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:18:24 192.168.122.209 [62055.158366] [tempesta fw] Tempesta FW is ready Apr 26 09:18:25 192.168.122.209 [62055.720084] [tdb] Close table 'client0.tdb' Apr 26 09:18:25 192.168.122.209 [62055.905945] [tdb] Close table 'sessions0.tdb' Apr 26 09:18:28 192.168.122.209 [62059.111478] [tdb] Close table 'cache0.tdb' Apr 26 09:18:28 192.168.122.209 [62059.370661] [tdb] Close table 'filter0.tdb' Apr 26 09:18:28 192.168.122.209 [62059.371099] [tempesta fw] modules are stopped Apr 26 09:18:28 192.168.122.209 [62059.550761] [tempesta fw] exiting... Apr 26 09:18:29 192.168.122.209 [62059.689193] [tdb] Shutdown Tempesta DB Apr 26 09:18:29 192.168.122.209 [62059.883713] End test: sessions.test_js_challenge.JSChallengeHttp.test_method_override_GET_HEAD Apr 26 09:18:29 192.168.122.209 [62059.896619] Start test: sessions.test_js_challenge.JSChallengeHttp.test_method_override_GET_POST Apr 26 09:18:30 192.168.122.209 [62060.881060] [tdb] Start Tempesta DB Apr 26 09:18:30 192.168.122.209 [62061.030120] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:18:32 192.168.122.209 [62063.032024] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62063.032024] Maybe that's fine, but it's worth checking the [62063.032024] config - if there is no relations between the [62063.032024] names, then host name confusion attack is possible. Apr 26 09:18:32 192.168.122.209 [62063.192531] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:18:32 192.168.122.209 [62063.242551] [tempesta fw] Configuration processing is completed. Apr 26 09:18:32 192.168.122.209 [62063.293218] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:18:33 192.168.122.209 [62063.703971] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:18:33 192.168.122.209 [62063.730442] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:18:33 192.168.122.209 [62063.756222] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:18:33 192.168.122.209 [62063.814476] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:18:33 192.168.122.209 [62063.816192] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:18:33 192.168.122.209 [62063.862493] [tempesta fw] Tempesta FW is ready Apr 26 09:18:33 192.168.122.209 [62064.010172] [tempesta fw] Warning: request dropped: unsafe method override: 127.0.0.2 Apr 26 09:18:33 192.168.122.209 [62064.419526] [tdb] Close table 'client0.tdb' Apr 26 09:18:34 192.168.122.209 [62064.593906] [tdb] Close table 'sessions0.tdb' Apr 26 09:18:37 192.168.122.209 [62067.813614] [tdb] Close table 'cache0.tdb' Apr 26 09:18:37 192.168.122.209 [62068.055395] [tdb] Close table 'filter0.tdb' Apr 26 09:18:37 192.168.122.209 [62068.055815] [tempesta fw] modules are stopped Apr 26 09:18:37 192.168.122.209 [62068.241472] [tempesta fw] exiting... Apr 26 09:18:37 192.168.122.209 [62068.382209] [tdb] Shutdown Tempesta DB Apr 26 09:18:37 192.168.122.209 [62068.573961] End test: sessions.test_js_challenge.JSChallengeHttp.test_method_override_GET_POST Apr 26 09:18:38 192.168.122.209 [62068.595990] Start test: sessions.test_js_challenge.JSChallengeHttp.test_method_override_HEAD_POST Apr 26 09:18:39 192.168.122.209 [62069.604531] [tdb] Start Tempesta DB Apr 26 09:18:39 192.168.122.209 [62069.736826] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:18:41 192.168.122.209 [62071.771898] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62071.771898] Maybe that's fine, but it's worth checking the [62071.771898] config - if there is no relations between the [62071.771898] names, then host name confusion attack is possible. Apr 26 09:18:41 192.168.122.209 [62071.972235] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:18:41 192.168.122.209 [62072.014660] [tempesta fw] Configuration processing is completed. Apr 26 09:18:41 192.168.122.209 [62072.082735] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:18:41 192.168.122.209 [62072.480909] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:18:41 192.168.122.209 [62072.505942] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:18:41 192.168.122.209 [62072.532057] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:18:41 192.168.122.209 [62072.570631] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:18:41 192.168.122.209 [62072.572357] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:18:42 192.168.122.209 [62072.614575] [tempesta fw] Tempesta FW is ready Apr 26 09:18:42 192.168.122.209 [62072.749704] [tempesta fw] Warning: request dropped: unsafe method override: 127.0.0.2 Apr 26 09:18:42 192.168.122.209 [62073.179457] [tdb] Close table 'client0.tdb' Apr 26 09:18:42 192.168.122.209 [62073.370529] [tdb] Close table 'sessions0.tdb' Apr 26 09:18:45 192.168.122.209 [62076.540169] [tdb] Close table 'cache0.tdb' Apr 26 09:18:46 192.168.122.209 [62076.778003] [tdb] Close table 'filter0.tdb' Apr 26 09:18:46 192.168.122.209 [62076.778455] [tempesta fw] modules are stopped Apr 26 09:18:46 192.168.122.209 [62076.980171] [tempesta fw] exiting... Apr 26 09:18:46 192.168.122.209 [62077.130232] [tdb] Shutdown Tempesta DB Apr 26 09:18:46 192.168.122.209 [62077.306215] End test: sessions.test_js_challenge.JSChallengeHttp.test_method_override_HEAD_POST Apr 26 09:18:46 192.168.122.209 [62077.326784] Start test: sessions.test_js_challenge.JSChallengeHttp.test_method_override_POST_GET Apr 26 09:18:47 192.168.122.209 [62078.303789] [tdb] Start Tempesta DB Apr 26 09:18:47 192.168.122.209 [62078.451948] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:18:49 192.168.122.209 [62080.455999] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62080.455999] Maybe that's fine, but it's worth checking the [62080.455999] config - if there is no relations between the [62080.455999] names, then host name confusion attack is possible. Apr 26 09:18:50 192.168.122.209 [62080.624802] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:18:50 192.168.122.209 [62080.670772] [tempesta fw] Configuration processing is completed. Apr 26 09:18:50 192.168.122.209 [62080.737385] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:18:50 192.168.122.209 [62081.195698] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:18:50 192.168.122.209 [62081.224386] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:18:50 192.168.122.209 [62081.252093] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:18:50 192.168.122.209 [62081.294746] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:18:50 192.168.122.209 [62081.296483] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:18:50 192.168.122.209 [62081.342694] [tempesta fw] Tempesta FW is ready Apr 26 09:18:51 192.168.122.209 [62081.920715] [tdb] Close table 'client0.tdb' Apr 26 09:18:51 192.168.122.209 [62082.109555] [tdb] Close table 'sessions0.tdb' Apr 26 09:18:54 192.168.122.209 [62085.360205] [tdb] Close table 'cache0.tdb' Apr 26 09:18:54 192.168.122.209 [62085.586407] [tdb] Close table 'filter0.tdb' Apr 26 09:18:54 192.168.122.209 [62085.586839] [tempesta fw] modules are stopped Apr 26 09:18:55 192.168.122.209 [62085.827908] [tempesta fw] exiting... Apr 26 09:18:55 192.168.122.209 [62085.929933] [tdb] Shutdown Tempesta DB Apr 26 09:18:55 192.168.122.209 [62086.124178] End test: sessions.test_js_challenge.JSChallengeHttp.test_method_override_POST_GET Apr 26 09:18:55 192.168.122.209 [62086.137727] Start test: sessions.test_js_challenge.JSChallengeHttp.test_method_override_POST_HEAD Apr 26 09:18:56 192.168.122.209 [62087.152193] [tdb] Start Tempesta DB Apr 26 09:18:56 192.168.122.209 [62087.297327] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:18:58 192.168.122.209 [62089.236119] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62089.236119] Maybe that's fine, but it's worth checking the [62089.236119] config - if there is no relations between the [62089.236119] names, then host name confusion attack is possible. Apr 26 09:18:58 192.168.122.209 [62089.412854] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:18:58 192.168.122.209 [62089.454880] [tempesta fw] Configuration processing is completed. Apr 26 09:18:58 192.168.122.209 [62089.504667] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:18:59 192.168.122.209 [62089.915135] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:18:59 192.168.122.209 [62089.940809] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:18:59 192.168.122.209 [62089.967563] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:18:59 192.168.122.209 [62090.018878] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:18:59 192.168.122.209 [62090.020599] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:18:59 192.168.122.209 [62090.078803] [tempesta fw] Tempesta FW is ready Apr 26 09:19:00 192.168.122.209 [62090.593845] [tdb] Close table 'client0.tdb' Apr 26 09:19:00 192.168.122.209 [62090.783887] [tdb] Close table 'sessions0.tdb' Apr 26 09:19:03 192.168.122.209 [62094.037996] [tdb] Close table 'cache0.tdb' Apr 26 09:19:03 192.168.122.209 [62094.281994] [tdb] Close table 'filter0.tdb' Apr 26 09:19:03 192.168.122.209 [62094.282439] [tempesta fw] modules are stopped Apr 26 09:19:03 192.168.122.209 [62094.499324] [tempesta fw] exiting... Apr 26 09:19:04 192.168.122.209 [62094.613219] [tdb] Shutdown Tempesta DB Apr 26 09:19:04 192.168.122.209 [62094.814725] End test: sessions.test_js_challenge.JSChallengeHttp.test_method_override_POST_HEAD Apr 26 09:19:04 192.168.122.209 [62094.834479] Start test: sessions.test_js_challenge.JSChallengeHttp.test_method_override_with_cache_GET_HEAD Apr 26 09:19:05 192.168.122.209 [62095.908102] [tdb] Start Tempesta DB Apr 26 09:19:05 192.168.122.209 [62096.048792] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:19:07 192.168.122.209 [62098.052302] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62098.052302] Maybe that's fine, but it's worth checking the [62098.052302] config - if there is no relations between the [62098.052302] names, then host name confusion attack is possible. Apr 26 09:19:07 192.168.122.209 [62098.217130] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:19:07 192.168.122.209 [62098.259019] [tempesta fw] Configuration processing is completed. Apr 26 09:19:07 192.168.122.209 [62098.315594] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:19:08 192.168.122.209 [62098.748201] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:19:08 192.168.122.209 [62098.776086] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:19:08 192.168.122.209 [62098.806662] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:19:08 192.168.122.209 [62098.846982] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:19:08 192.168.122.209 [62098.848717] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:19:08 192.168.122.209 [62098.886907] [tempesta fw] Tempesta FW is ready Apr 26 09:19:09 192.168.122.209 [62100.569952] [tdb] Close table 'client0.tdb' Apr 26 09:19:10 192.168.122.209 [62100.734587] [tdb] Close table 'sessions0.tdb' Apr 26 09:19:13 192.168.122.209 [62104.086632] [tdb] Close table 'cache0.tdb' Apr 26 09:19:13 192.168.122.209 [62104.329129] [tdb] Close table 'filter0.tdb' Apr 26 09:19:13 192.168.122.209 [62104.329543] [tempesta fw] modules are stopped Apr 26 09:19:13 192.168.122.209 [62104.515184] [tempesta fw] exiting... Apr 26 09:19:14 192.168.122.209 [62104.650812] [tdb] Shutdown Tempesta DB Apr 26 09:19:14 192.168.122.209 [62104.876713] End test: sessions.test_js_challenge.JSChallengeHttp.test_method_override_with_cache_GET_HEAD Apr 26 09:19:14 192.168.122.209 [62104.893685] Start test: sessions.test_js_challenge.JSChallengeHttp.test_method_override_with_cache_GET_POST Apr 26 09:19:15 192.168.122.209 [62106.099642] [tdb] Start Tempesta DB Apr 26 09:19:15 192.168.122.209 [62106.226366] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:19:17 192.168.122.209 [62108.460471] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62108.460471] Maybe that's fine, but it's worth checking the [62108.460471] config - if there is no relations between the [62108.460471] names, then host name confusion attack is possible. Apr 26 09:19:18 192.168.122.209 [62108.629339] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:19:18 192.168.122.209 [62108.671130] [tempesta fw] Configuration processing is completed. Apr 26 09:19:18 192.168.122.209 [62108.728219] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:19:18 192.168.122.209 [62109.133657] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:19:18 192.168.122.209 [62109.159006] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:19:18 192.168.122.209 [62109.185307] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:19:18 192.168.122.209 [62109.251111] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:19:18 192.168.122.209 [62109.252860] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:19:18 192.168.122.209 [62109.291089] [tempesta fw] Tempesta FW is ready Apr 26 09:19:21 192.168.122.209 [62111.663376] [tempesta fw] Warning: request dropped: unsafe method override: 127.0.0.2 Apr 26 09:19:21 192.168.122.209 [62112.121791] [tdb] Close table 'client0.tdb' Apr 26 09:19:21 192.168.122.209 [62112.306488] [tdb] Close table 'sessions0.tdb' Apr 26 09:19:25 192.168.122.209 [62115.689479] [tdb] Close table 'cache0.tdb' Apr 26 09:19:25 192.168.122.209 [62115.942471] [tdb] Close table 'filter0.tdb' Apr 26 09:19:25 192.168.122.209 [62115.942897] [tempesta fw] modules are stopped Apr 26 09:19:25 192.168.122.209 [62116.112000] [tempesta fw] exiting... Apr 26 09:19:25 192.168.122.209 [62116.257104] [tdb] Shutdown Tempesta DB Apr 26 09:19:25 192.168.122.209 [62116.478755] End test: sessions.test_js_challenge.JSChallengeHttp.test_method_override_with_cache_GET_POST Apr 26 09:19:25 192.168.122.209 [62116.493641] Start test: sessions.test_js_challenge.JSChallengeHttp.test_method_override_with_cache_HEAD_GET Apr 26 09:19:27 192.168.122.209 [62117.734387] [tdb] Start Tempesta DB Apr 26 09:19:27 192.168.122.209 [62117.892035] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:19:29 192.168.122.209 [62120.105014] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62120.105014] Maybe that's fine, but it's worth checking the [62120.105014] config - if there is no relations between the [62120.105014] names, then host name confusion attack is possible. Apr 26 09:19:29 192.168.122.209 [62120.289723] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:19:29 192.168.122.209 [62120.331406] [tempesta fw] Configuration processing is completed. Apr 26 09:19:29 192.168.122.209 [62120.399770] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:19:30 192.168.122.209 [62121.033302] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:19:30 192.168.122.209 [62121.069468] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:19:30 192.168.122.209 [62121.095974] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:19:30 192.168.122.209 [62121.155276] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:19:30 192.168.122.209 [62121.156515] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:19:30 192.168.122.209 [62121.195240] [tempesta fw] Tempesta FW is ready Apr 26 09:19:33 192.168.122.209 [62123.986351] [tdb] Close table 'client0.tdb' Apr 26 09:19:33 192.168.122.209 [62124.177664] [tdb] Close table 'sessions0.tdb' Apr 26 09:19:36 192.168.122.209 [62127.381645] [tdb] Close table 'cache0.tdb' Apr 26 09:19:37 192.168.122.209 [62127.620906] [tdb] Close table 'filter0.tdb' Apr 26 09:19:37 192.168.122.209 [62127.621340] [tempesta fw] modules are stopped Apr 26 09:19:37 192.168.122.209 [62127.828425] [tempesta fw] exiting... Apr 26 09:19:37 192.168.122.209 [62127.958752] [tdb] Shutdown Tempesta DB Apr 26 09:19:37 192.168.122.209 [62128.175416] End test: sessions.test_js_challenge.JSChallengeHttp.test_method_override_with_cache_HEAD_GET Apr 26 09:19:37 192.168.122.209 [62128.182544] Start test: sessions.test_js_challenge.JSChallengeHttp.test_method_override_with_cache_HEAD_POST Apr 26 09:19:38 192.168.122.209 [62129.460530] [tdb] Start Tempesta DB Apr 26 09:19:39 192.168.122.209 [62129.601260] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:19:41 192.168.122.209 [62131.696696] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62131.696696] Maybe that's fine, but it's worth checking the [62131.696696] config - if there is no relations between the [62131.696696] names, then host name confusion attack is possible. Apr 26 09:19:41 192.168.122.209 [62131.869430] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:19:41 192.168.122.209 [62131.907417] [tempesta fw] Configuration processing is completed. Apr 26 09:19:41 192.168.122.209 [62131.962700] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:19:41 192.168.122.209 [62132.424362] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:19:41 192.168.122.209 [62132.450275] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:19:41 192.168.122.209 [62132.476827] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:19:41 192.168.122.209 [62132.539399] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:19:41 192.168.122.209 [62132.541131] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:19:42 192.168.122.209 [62132.587370] [tempesta fw] Tempesta FW is ready Apr 26 09:19:44 192.168.122.209 [62134.736270] [tempesta fw] Warning: request dropped: unsafe method override: 127.0.0.2 Apr 26 09:19:44 192.168.122.209 [62135.143630] [tdb] Close table 'client0.tdb' Apr 26 09:19:44 192.168.122.209 [62135.320531] [tdb] Close table 'sessions0.tdb' Apr 26 09:19:47 192.168.122.209 [62138.479185] [tdb] Close table 'cache0.tdb' Apr 26 09:19:48 192.168.122.209 [62138.723716] [tdb] Close table 'filter0.tdb' Apr 26 09:19:48 192.168.122.209 [62138.724151] [tempesta fw] modules are stopped Apr 26 09:19:48 192.168.122.209 [62138.912517] [tempesta fw] exiting... Apr 26 09:19:48 192.168.122.209 [62139.052215] [tdb] Shutdown Tempesta DB Apr 26 09:19:48 192.168.122.209 [62139.258665] End test: sessions.test_js_challenge.JSChallengeHttp.test_method_override_with_cache_HEAD_POST Apr 26 09:19:48 192.168.122.209 [62139.271732] Start test: sessions.test_js_challenge.JSChallengeHttp.test_method_override_with_cache_POST_GET Apr 26 09:19:50 192.168.122.209 [62140.618339] [tdb] Start Tempesta DB Apr 26 09:19:50 192.168.122.209 [62140.769647] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:19:52 192.168.122.209 [62142.912902] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62142.912902] Maybe that's fine, but it's worth checking the [62142.912902] config - if there is no relations between the [62142.912902] names, then host name confusion attack is possible. Apr 26 09:19:52 192.168.122.209 [62143.077753] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:19:52 192.168.122.209 [62143.119629] [tempesta fw] Configuration processing is completed. Apr 26 09:19:52 192.168.122.209 [62143.188474] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:19:53 192.168.122.209 [62143.612575] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:19:53 192.168.122.209 [62143.638512] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:19:53 192.168.122.209 [62143.664558] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:19:53 192.168.122.209 [62143.711552] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:19:53 192.168.122.209 [62143.713308] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:19:53 192.168.122.209 [62143.751520] [tempesta fw] Tempesta FW is ready Apr 26 09:19:55 192.168.122.209 [62146.145057] [tdb] Close table 'client0.tdb' Apr 26 09:19:55 192.168.122.209 [62146.341773] [tdb] Close table 'sessions0.tdb' Apr 26 09:19:59 192.168.122.209 [62149.601534] [tdb] Close table 'cache0.tdb' Apr 26 09:19:59 192.168.122.209 [62149.841061] [tdb] Close table 'filter0.tdb' Apr 26 09:19:59 192.168.122.209 [62149.841518] [tempesta fw] modules are stopped Apr 26 09:19:59 192.168.122.209 [62150.076399] [tempesta fw] exiting... Apr 26 09:19:59 192.168.122.209 [62150.191985] [tdb] Shutdown Tempesta DB Apr 26 09:19:59 192.168.122.209 [62150.399657] End test: sessions.test_js_challenge.JSChallengeHttp.test_method_override_with_cache_POST_GET Apr 26 09:19:59 192.168.122.209 [62150.427104] Start test: sessions.test_js_challenge.JSChallengeHttp.test_method_override_with_cache_POST_HEAD Apr 26 09:20:01 192.168.122.209 [62151.605647] [tdb] Start Tempesta DB Apr 26 09:20:01 192.168.122.209 [62151.731537] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:20:03 192.168.122.209 [62153.808973] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62153.808973] Maybe that's fine, but it's worth checking the [62153.808973] config - if there is no relations between the [62153.808973] names, then host name confusion attack is possible. Apr 26 09:20:03 192.168.122.209 [62153.977793] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:20:03 192.168.122.209 [62154.015706] [tempesta fw] Configuration processing is completed. Apr 26 09:20:03 192.168.122.209 [62154.071910] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:20:03 192.168.122.209 [62154.516848] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:20:03 192.168.122.209 [62154.542295] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:20:03 192.168.122.209 [62154.568785] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:20:04 192.168.122.209 [62154.691721] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:20:04 192.168.122.209 [62154.693492] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:20:04 192.168.122.209 [62154.759640] [tempesta fw] Tempesta FW is ready Apr 26 09:20:06 192.168.122.209 [62156.880848] [tdb] Close table 'client0.tdb' Apr 26 09:20:06 192.168.122.209 [62157.057878] [tdb] Close table 'sessions0.tdb' Apr 26 09:20:09 192.168.122.209 [62160.211083] [tdb] Close table 'cache0.tdb' Apr 26 09:20:09 192.168.122.209 [62160.441454] [tdb] Close table 'filter0.tdb' Apr 26 09:20:09 192.168.122.209 [62160.441874] [tempesta fw] modules are stopped Apr 26 09:20:10 192.168.122.209 [62160.682800] [tempesta fw] exiting... Apr 26 09:20:10 192.168.122.209 [62160.809139] [tdb] Shutdown Tempesta DB Apr 26 09:20:10 192.168.122.209 [62161.007934] End test: sessions.test_js_challenge.JSChallengeHttp.test_method_override_with_cache_POST_HEAD Apr 26 09:20:10 192.168.122.209 [62161.017370] Start test: sessions.test_js_challenge.JSChallengeHttp.test_new_client_session_with_exist_cookie Apr 26 09:20:11 192.168.122.209 [62162.105321] [tdb] Start Tempesta DB Apr 26 09:20:11 192.168.122.209 [62162.263738] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:20:13 192.168.122.209 [62164.421092] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62164.421092] Maybe that's fine, but it's worth checking the [62164.421092] config - if there is no relations between the [62164.421092] names, then host name confusion attack is possible. Apr 26 09:20:14 192.168.122.209 [62164.605840] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:20:14 192.168.122.209 [62164.643828] [tempesta fw] Configuration processing is completed. Apr 26 09:20:14 192.168.122.209 [62164.695281] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:20:14 192.168.122.209 [62165.110002] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:20:14 192.168.122.209 [62165.135987] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:20:14 192.168.122.209 [62165.161906] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:20:14 192.168.122.209 [62165.215805] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:20:14 192.168.122.209 [62165.217561] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:20:14 192.168.122.209 [62165.255791] [tempesta fw] Tempesta FW is ready Apr 26 09:20:16 192.168.122.209 [62167.062921] [tdb] Close table 'client0.tdb' Apr 26 09:20:16 192.168.122.209 [62167.239009] [tdb] Close table 'sessions0.tdb' Apr 26 09:20:19 192.168.122.209 [62170.443526] [tdb] Close table 'cache0.tdb' Apr 26 09:20:20 192.168.122.209 [62170.686985] [tdb] Close table 'filter0.tdb' Apr 26 09:20:20 192.168.122.209 [62170.687422] [tempesta fw] modules are stopped Apr 26 09:20:20 192.168.122.209 [62170.878961] [tempesta fw] exiting... Apr 26 09:20:20 192.168.122.209 [62171.005818] [tdb] Shutdown Tempesta DB Apr 26 09:20:20 192.168.122.209 [62171.205825] End test: sessions.test_js_challenge.JSChallengeHttp.test_new_client_session_with_exist_cookie Apr 26 09:20:20 192.168.122.209 [62171.226725] Start test: sessions.test_js_challenge.JSChallengeHttp.test_not_block_after_tempesta_restart Apr 26 09:20:21 192.168.122.209 [62172.476704] [tdb] Start Tempesta DB Apr 26 09:20:22 192.168.122.209 [62172.640185] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:20:24 192.168.122.209 [62174.749265] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62174.749265] Maybe that's fine, but it's worth checking the [62174.749265] config - if there is no relations between the [62174.749265] names, then host name confusion attack is possible. Apr 26 09:20:24 192.168.122.209 [62174.918116] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:20:24 192.168.122.209 [62174.952218] [tempesta fw] Configuration processing is completed. Apr 26 09:20:24 192.168.122.209 [62175.012501] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:20:24 192.168.122.209 [62175.573654] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:20:25 192.168.122.209 [62175.612196] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:20:25 192.168.122.209 [62175.638935] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:20:25 192.168.122.209 [62175.721438] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:20:25 192.168.122.209 [62175.723206] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:20:25 192.168.122.209 [62175.767908] [tempesta fw] Tempesta FW is ready Apr 26 09:20:28 192.168.122.209 [62178.652408] [tdb] Close table 'client0.tdb' Apr 26 09:20:28 192.168.122.209 [62178.845335] [tdb] Close table 'sessions0.tdb' Apr 26 09:20:31 192.168.122.209 [62182.073636] [tdb] Close table 'cache0.tdb' Apr 26 09:20:31 192.168.122.209 [62182.310978] [tdb] Close table 'filter0.tdb' Apr 26 09:20:31 192.168.122.209 [62182.311401] [tempesta fw] modules are stopped Apr 26 09:20:31 192.168.122.209 [62182.487462] [tempesta fw] exiting... Apr 26 09:20:32 192.168.122.209 [62182.666829] [tdb] Shutdown Tempesta DB Apr 26 09:20:33 192.168.122.209 [62183.856024] [tdb] Start Tempesta DB Apr 26 09:20:33 192.168.122.209 [62183.993113] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:20:35 192.168.122.209 [62185.949271] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62185.949271] Maybe that's fine, but it's worth checking the [62185.949271] config - if there is no relations between the [62185.949271] names, then host name confusion attack is possible. Apr 26 09:20:35 192.168.122.209 [62186.114145] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:20:35 192.168.122.209 [62186.152096] [tempesta fw] Configuration processing is completed. Apr 26 09:20:35 192.168.122.209 [62186.201256] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:20:36 192.168.122.209 [62186.625587] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:20:36 192.168.122.209 [62186.651174] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:20:36 192.168.122.209 [62186.680279] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:20:36 192.168.122.209 [62186.760092] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:20:36 192.168.122.209 [62186.761827] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:20:36 192.168.122.209 [62186.812035] [tempesta fw] Tempesta FW is ready Apr 26 09:20:36 192.168.122.209 [62186.887464] [tempesta fw] Warning: http_sess: bad received HMAC value for 127.0.0.2 c(pos=0), ts=0x100ec07a5 orig_hmac=[a40b4a6234bc56e63cd44def289047632ea4e7d4] Apr 26 09:20:38 192.168.122.209 [62189.336928] [tdb] Close table 'client0.tdb' Apr 26 09:20:38 192.168.122.209 [62189.522935] [tdb] Close table 'sessions0.tdb' Apr 26 09:20:42 192.168.122.209 [62192.792619] [tdb] Close table 'cache0.tdb' Apr 26 09:20:42 192.168.122.209 [62193.058680] [tdb] Close table 'filter0.tdb' Apr 26 09:20:42 192.168.122.209 [62193.059142] [tempesta fw] modules are stopped Apr 26 09:20:42 192.168.122.209 [62193.233643] [tempesta fw] exiting... Apr 26 09:20:42 192.168.122.209 [62193.356325] [tdb] Shutdown Tempesta DB Apr 26 09:20:43 192.168.122.209 [62193.595960] End test: sessions.test_js_challenge.JSChallengeHttp.test_not_block_after_tempesta_restart Apr 26 09:20:43 192.168.122.209 [62193.620008] Start test: sessions.test_js_challenge.JSChallengeHttp.test_number_of_requests_is_greater_than_max_misses Apr 26 09:20:44 192.168.122.209 [62194.842042] [tdb] Start Tempesta DB Apr 26 09:20:44 192.168.122.209 [62195.007029] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:20:46 192.168.122.209 [62197.197659] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62197.197659] Maybe that's fine, but it's worth checking the [62197.197659] config - if there is no relations between the [62197.197659] names, then host name confusion attack is possible. Apr 26 09:20:46 192.168.122.209 [62197.358241] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:20:46 192.168.122.209 [62197.400241] [tempesta fw] Configuration processing is completed. Apr 26 09:20:46 192.168.122.209 [62197.451256] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:20:47 192.168.122.209 [62197.855656] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:20:47 192.168.122.209 [62197.889592] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:20:47 192.168.122.209 [62197.916520] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:20:47 192.168.122.209 [62197.988250] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:20:47 192.168.122.209 [62197.990006] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:20:47 192.168.122.209 [62198.032176] [tempesta fw] Tempesta FW is ready Apr 26 09:20:47 192.168.122.209 [62198.227771] [tempesta fw] Warning: frang: max rmisses exceeded for 127.0.0.2: 3 (lim=2) Apr 26 09:20:48 192.168.122.209 [62198.663038] [tdb] Close table 'client0.tdb' Apr 26 09:20:48 192.168.122.209 [62198.867961] [tdb] Close table 'sessions0.tdb' Apr 26 09:20:51 192.168.122.209 [62202.135972] [tdb] Close table 'cache0.tdb' Apr 26 09:20:51 192.168.122.209 [62202.375012] [tdb] Close table 'filter0.tdb' Apr 26 09:20:51 192.168.122.209 [62202.375411] [tempesta fw] modules are stopped Apr 26 09:20:51 192.168.122.209 [62202.567789] [tempesta fw] exiting... Apr 26 09:20:52 192.168.122.209 [62202.693059] [tdb] Shutdown Tempesta DB Apr 26 09:20:52 192.168.122.209 [62202.912317] End test: sessions.test_js_challenge.JSChallengeHttp.test_number_of_requests_is_greater_than_max_misses Apr 26 09:20:52 192.168.122.209 [62202.922502] Start test: sessions.test_js_challenge.JSChallengeHttp.test_resp_code_302 Apr 26 09:20:53 192.168.122.209 [62204.004416] [tdb] Start Tempesta DB Apr 26 09:20:53 192.168.122.209 [62204.159007] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:20:55 192.168.122.209 [62206.301617] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62206.301617] Maybe that's fine, but it's worth checking the [62206.301617] config - if there is no relations between the [62206.301617] names, then host name confusion attack is possible. Apr 26 09:20:55 192.168.122.209 [62206.458393] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:20:55 192.168.122.209 [62206.508357] [tempesta fw] Configuration processing is completed. Apr 26 09:20:55 192.168.122.209 [62206.562769] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:20:56 192.168.122.209 [62206.967286] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:20:56 192.168.122.209 [62207.007130] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:20:56 192.168.122.209 [62207.032917] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:20:56 192.168.122.209 [62207.088371] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:20:56 192.168.122.209 [62207.090116] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:20:56 192.168.122.209 [62207.132309] [tempesta fw] Tempesta FW is ready Apr 26 09:20:57 192.168.122.209 [62207.730809] [tdb] Close table 'client0.tdb' Apr 26 09:20:57 192.168.122.209 [62207.929465] [tdb] Close table 'sessions0.tdb' Apr 26 09:21:00 192.168.122.209 [62211.078354] [tdb] Close table 'cache0.tdb' Apr 26 09:21:00 192.168.122.209 [62211.312634] [tdb] Close table 'filter0.tdb' Apr 26 09:21:00 192.168.122.209 [62211.313052] [tempesta fw] modules are stopped Apr 26 09:21:00 192.168.122.209 [62211.529269] [tempesta fw] exiting... Apr 26 09:21:01 192.168.122.209 [62211.624426] [tdb] Shutdown Tempesta DB Apr 26 09:21:01 192.168.122.209 [62211.854441] End test: sessions.test_js_challenge.JSChallengeHttp.test_resp_code_302 Apr 26 09:21:01 192.168.122.209 [62211.865559] Start test: sessions.test_js_challenge.JSChallengeHttp.test_resp_code_403 Apr 26 09:21:02 192.168.122.209 [62213.029295] [tdb] Start Tempesta DB Apr 26 09:21:02 192.168.122.209 [62213.160091] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:21:04 192.168.122.209 [62215.397767] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62215.397767] Maybe that's fine, but it's worth checking the [62215.397767] config - if there is no relations between the [62215.397767] names, then host name confusion attack is possible. Apr 26 09:21:04 192.168.122.209 [62215.554558] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:21:05 192.168.122.209 [62215.592488] [tempesta fw] Configuration processing is completed. Apr 26 09:21:05 192.168.122.209 [62215.653643] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:21:05 192.168.122.209 [62216.081782] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:21:05 192.168.122.209 [62216.107556] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:21:05 192.168.122.209 [62216.133507] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:21:05 192.168.122.209 [62216.176457] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:21:05 192.168.122.209 [62216.178207] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:21:05 192.168.122.209 [62216.220412] [tempesta fw] Tempesta FW is ready Apr 26 09:21:06 192.168.122.209 [62216.802720] [tdb] Close table 'client0.tdb' Apr 26 09:21:06 192.168.122.209 [62216.990754] [tdb] Close table 'sessions0.tdb' Apr 26 09:21:09 192.168.122.209 [62220.200096] [tdb] Close table 'cache0.tdb' Apr 26 09:21:09 192.168.122.209 [62220.445489] [tdb] Close table 'filter0.tdb' Apr 26 09:21:09 192.168.122.209 [62220.445918] [tempesta fw] modules are stopped Apr 26 09:21:10 192.168.122.209 [62220.643127] [tempesta fw] exiting... Apr 26 09:21:10 192.168.122.209 [62220.800134] [tdb] Shutdown Tempesta DB Apr 26 09:21:10 192.168.122.209 [62221.035430] End test: sessions.test_js_challenge.JSChallengeHttp.test_resp_code_403 Apr 26 09:21:10 192.168.122.209 [62221.047063] Start test: sessions.test_js_challenge.JSChallengeHttp.test_resp_code_default Apr 26 09:21:11 192.168.122.209 [62222.281993] [tdb] Start Tempesta DB Apr 26 09:21:11 192.168.122.209 [62222.410725] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:21:13 192.168.122.209 [62224.373824] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62224.373824] Maybe that's fine, but it's worth checking the [62224.373824] config - if there is no relations between the [62224.373824] names, then host name confusion attack is possible. Apr 26 09:21:13 192.168.122.209 [62224.542457] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:21:14 192.168.122.209 [62224.592582] [tempesta fw] Configuration processing is completed. Apr 26 09:21:14 192.168.122.209 [62224.643976] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:21:14 192.168.122.209 [62225.062029] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:21:14 192.168.122.209 [62225.087824] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:21:14 192.168.122.209 [62225.114240] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:21:14 192.168.122.209 [62225.160572] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:21:14 192.168.122.209 [62225.162316] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:21:14 192.168.122.209 [62225.212518] [tempesta fw] Tempesta FW is ready Apr 26 09:21:15 192.168.122.209 [62225.799225] [tdb] Close table 'client0.tdb' Apr 26 09:21:15 192.168.122.209 [62225.996913] [tdb] Close table 'sessions0.tdb' Apr 26 09:21:18 192.168.122.209 [62229.169645] [tdb] Close table 'cache0.tdb' Apr 26 09:21:18 192.168.122.209 [62229.426610] [tdb] Close table 'filter0.tdb' Apr 26 09:21:18 192.168.122.209 [62229.427043] [tempesta fw] modules are stopped Apr 26 09:21:19 192.168.122.209 [62229.602970] [tempesta fw] exiting... Apr 26 09:21:19 192.168.122.209 [62229.741070] [tdb] Shutdown Tempesta DB Apr 26 09:21:19 192.168.122.209 [62229.946048] End test: sessions.test_js_challenge.JSChallengeHttp.test_resp_code_default Apr 26 09:21:19 192.168.122.209 [62229.956444] Start test: sessions.test_js_challenge.JSChallengeHttp.test_restart_js_challenge Apr 26 09:21:20 192.168.122.209 [62231.011861] [tdb] Start Tempesta DB Apr 26 09:21:20 192.168.122.209 [62231.140791] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:21:22 192.168.122.209 [62233.205948] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62233.205948] Maybe that's fine, but it's worth checking the [62233.205948] config - if there is no relations between the [62233.205948] names, then host name confusion attack is possible. Apr 26 09:21:22 192.168.122.209 [62233.378735] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:21:22 192.168.122.209 [62233.420711] [tempesta fw] Configuration processing is completed. Apr 26 09:21:22 192.168.122.209 [62233.472543] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:21:23 192.168.122.209 [62233.877414] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:21:23 192.168.122.209 [62233.903293] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:21:23 192.168.122.209 [62233.929672] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:21:23 192.168.122.209 [62233.972728] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:21:23 192.168.122.209 [62233.974537] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:21:23 192.168.122.209 [62234.024657] [tempesta fw] Tempesta FW is ready Apr 26 09:21:23 192.168.122.209 [62234.168777] [tempesta fw] Warning: http_sess: bad received HMAC value for 127.0.0.2 d(pos=0), ts=0x100116a72 orig_hmac=[f09bb24062ffafbf338ad29fc05c55e9da3c910b] Apr 26 09:21:25 192.168.122.209 [62236.442676] [tdb] Close table 'client0.tdb' Apr 26 09:21:26 192.168.122.209 [62236.626875] [tdb] Close table 'sessions0.tdb' Apr 26 09:21:29 192.168.122.209 [62239.829147] [tdb] Close table 'cache0.tdb' Apr 26 09:21:29 192.168.122.209 [62240.085627] [tdb] Close table 'filter0.tdb' Apr 26 09:21:29 192.168.122.209 [62240.086049] [tempesta fw] modules are stopped Apr 26 09:21:29 192.168.122.209 [62240.277621] [tempesta fw] exiting... Apr 26 09:21:29 192.168.122.209 [62240.417423] [tdb] Shutdown Tempesta DB Apr 26 09:21:30 192.168.122.209 [62240.648078] End test: sessions.test_js_challenge.JSChallengeHttp.test_restart_js_challenge Apr 26 09:21:30 192.168.122.209 [62240.659883] Start test: sessions.test_js_challenge.JSChallengeHttp.test_second_request_GET_and_accept_all Apr 26 09:21:31 192.168.122.209 [62241.714090] [tdb] Start Tempesta DB Apr 26 09:21:31 192.168.122.209 [62241.860896] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:21:33 192.168.122.209 [62243.834152] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62243.834152] Maybe that's fine, but it's worth checking the [62243.834152] config - if there is no relations between the [62243.834152] names, then host name confusion attack is possible. Apr 26 09:21:33 192.168.122.209 [62243.998861] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:21:33 192.168.122.209 [62244.040859] [tempesta fw] Configuration processing is completed. Apr 26 09:21:33 192.168.122.209 [62244.105309] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:21:33 192.168.122.209 [62244.529192] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:21:33 192.168.122.209 [62244.555371] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:21:33 192.168.122.209 [62244.581275] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:21:34 192.168.122.209 [62244.624821] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:21:34 192.168.122.209 [62244.626541] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:21:34 192.168.122.209 [62244.664768] [tempesta fw] Tempesta FW is ready Apr 26 09:21:36 192.168.122.209 [62246.723575] [tdb] Close table 'client0.tdb' Apr 26 09:21:36 192.168.122.209 [62246.942283] [tdb] Close table 'sessions0.tdb' Apr 26 09:21:39 192.168.122.209 [62250.149816] [tdb] Close table 'cache0.tdb' Apr 26 09:21:39 192.168.122.209 [62250.407734] [tdb] Close table 'filter0.tdb' Apr 26 09:21:39 192.168.122.209 [62250.408133] [tempesta fw] modules are stopped Apr 26 09:21:39 192.168.122.209 [62250.581991] [tempesta fw] exiting... Apr 26 09:21:40 192.168.122.209 [62250.698425] [tdb] Shutdown Tempesta DB Apr 26 09:21:40 192.168.122.209 [62250.887222] End test: sessions.test_js_challenge.JSChallengeHttp.test_second_request_GET_and_accept_all Apr 26 09:21:40 192.168.122.209 [62250.899819] Start test: sessions.test_js_challenge.JSChallengeHttp.test_second_request_POST Apr 26 09:21:41 192.168.122.209 [62251.927804] [tdb] Start Tempesta DB Apr 26 09:21:41 192.168.122.209 [62252.079290] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:21:43 192.168.122.209 [62254.054192] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62254.054192] Maybe that's fine, but it's worth checking the [62254.054192] config - if there is no relations between the [62254.054192] names, then host name confusion attack is possible. Apr 26 09:21:43 192.168.122.209 [62254.227079] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:21:43 192.168.122.209 [62254.268983] [tempesta fw] Configuration processing is completed. Apr 26 09:21:43 192.168.122.209 [62254.325498] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:21:44 192.168.122.209 [62254.735770] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:21:44 192.168.122.209 [62254.761345] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:21:44 192.168.122.209 [62254.787251] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:21:44 192.168.122.209 [62254.832945] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:21:44 192.168.122.209 [62254.834711] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:21:44 192.168.122.209 [62254.872927] [tempesta fw] Tempesta FW is ready Apr 26 09:21:45 192.168.122.209 [62256.490743] [tdb] Close table 'client0.tdb' Apr 26 09:21:46 192.168.122.209 [62256.678683] [tdb] Close table 'sessions0.tdb' Apr 26 09:21:49 192.168.122.209 [62259.833714] [tdb] Close table 'cache0.tdb' Apr 26 09:21:49 192.168.122.209 [62260.085118] [tdb] Close table 'filter0.tdb' Apr 26 09:21:49 192.168.122.209 [62260.085542] [tempesta fw] modules are stopped Apr 26 09:21:49 192.168.122.209 [62260.337035] [tempesta fw] exiting... Apr 26 09:21:49 192.168.122.209 [62260.495464] [tdb] Shutdown Tempesta DB Apr 26 09:21:50 192.168.122.209 [62260.684584] End test: sessions.test_js_challenge.JSChallengeHttp.test_second_request_POST Apr 26 09:21:50 192.168.122.209 [62260.698222] Start test: sessions.test_js_challenge.JSChallengeHttp.test_servicing_non_challengeble_request_from_cache_GET Apr 26 09:21:51 192.168.122.209 [62261.666964] [tdb] Start Tempesta DB Apr 26 09:21:51 192.168.122.209 [62261.792489] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:21:53 192.168.122.209 [62263.822390] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62263.822390] Maybe that's fine, but it's worth checking the [62263.822390] config - if there is no relations between the [62263.822390] names, then host name confusion attack is possible. Apr 26 09:21:53 192.168.122.209 [62263.983173] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:21:53 192.168.122.209 [62264.021513] [tempesta fw] Configuration processing is completed. Apr 26 09:21:53 192.168.122.209 [62264.080849] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:21:53 192.168.122.209 [62264.498573] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:21:53 192.168.122.209 [62264.524188] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:21:53 192.168.122.209 [62264.550959] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:21:54 192.168.122.209 [62264.589078] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:21:54 192.168.122.209 [62264.590826] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:21:54 192.168.122.209 [62264.633023] [tempesta fw] Tempesta FW is ready Apr 26 09:21:56 192.168.122.209 [62267.262071] [tdb] Close table 'client0.tdb' Apr 26 09:21:56 192.168.122.209 [62267.443781] [tdb] Close table 'sessions0.tdb' Apr 26 09:22:00 192.168.122.209 [62270.639610] [tdb] Close table 'cache0.tdb' Apr 26 09:22:00 192.168.122.209 [62270.872212] [tdb] Close table 'filter0.tdb' Apr 26 09:22:00 192.168.122.209 [62270.872669] [tempesta fw] modules are stopped Apr 26 09:22:00 192.168.122.209 [62271.053385] [tempesta fw] exiting... Apr 26 09:22:00 192.168.122.209 [62271.161813] [tdb] Shutdown Tempesta DB Apr 26 09:22:00 192.168.122.209 [62271.395092] End test: sessions.test_js_challenge.JSChallengeHttp.test_servicing_non_challengeble_request_from_cache_GET Apr 26 09:22:00 192.168.122.209 [62271.422739] Start test: sessions.test_js_challenge.JSChallengeHttp.test_servicing_non_challengeble_request_from_cache_HEAD Apr 26 09:22:01 192.168.122.209 [62272.456098] [tdb] Start Tempesta DB Apr 26 09:22:01 192.168.122.209 [62272.586594] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:22:04 192.168.122.209 [62274.622483] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62274.622483] Maybe that's fine, but it's worth checking the [62274.622483] config - if there is no relations between the [62274.622483] names, then host name confusion attack is possible. Apr 26 09:22:04 192.168.122.209 [62274.783230] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:22:04 192.168.122.209 [62274.829210] [tempesta fw] Configuration processing is completed. Apr 26 09:22:04 192.168.122.209 [62274.881083] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:22:04 192.168.122.209 [62275.282200] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:22:04 192.168.122.209 [62275.309110] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:22:04 192.168.122.209 [62275.336865] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:22:04 192.168.122.209 [62275.413287] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:22:04 192.168.122.209 [62275.415010] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:22:04 192.168.122.209 [62275.461152] [tempesta fw] Tempesta FW is ready Apr 26 09:22:07 192.168.122.209 [62277.817224] [tdb] Close table 'client0.tdb' Apr 26 09:22:07 192.168.122.209 [62278.002182] [tdb] Close table 'sessions0.tdb' Apr 26 09:22:10 192.168.122.209 [62281.214930] [tdb] Close table 'cache0.tdb' Apr 26 09:22:10 192.168.122.209 [62281.464143] [tdb] Close table 'filter0.tdb' Apr 26 09:22:10 192.168.122.209 [62281.464571] [tempesta fw] modules are stopped Apr 26 09:22:11 192.168.122.209 [62281.669449] [tempesta fw] exiting... Apr 26 09:22:11 192.168.122.209 [62281.783836] [tdb] Shutdown Tempesta DB Apr 26 09:22:11 192.168.122.209 [62281.999038] End test: sessions.test_js_challenge.JSChallengeHttp.test_servicing_non_challengeble_request_from_cache_HEAD Apr 26 09:22:11 192.168.122.209 [62282.007358] Start test: sessions.test_js_challenge.JSChallengeHttp.test_servicing_non_challengeble_request_from_cache_POST Apr 26 09:22:12 192.168.122.209 [62283.085345] [tdb] Start Tempesta DB Apr 26 09:22:12 192.168.122.209 [62283.217693] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:22:14 192.168.122.209 [62285.234615] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62285.234615] Maybe that's fine, but it's worth checking the [62285.234615] config - if there is no relations between the [62285.234615] names, then host name confusion attack is possible. Apr 26 09:22:14 192.168.122.209 [62285.391417] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:22:14 192.168.122.209 [62285.433438] [tempesta fw] Configuration processing is completed. Apr 26 09:22:14 192.168.122.209 [62285.489963] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:22:15 192.168.122.209 [62285.898076] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:22:15 192.168.122.209 [62285.923442] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:22:15 192.168.122.209 [62285.949767] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:22:15 192.168.122.209 [62286.001361] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:22:15 192.168.122.209 [62286.003109] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:22:15 192.168.122.209 [62286.053311] [tempesta fw] Tempesta FW is ready Apr 26 09:22:17 192.168.122.209 [62288.090505] [tdb] Close table 'client0.tdb' Apr 26 09:22:17 192.168.122.209 [62288.276304] [tdb] Close table 'sessions0.tdb' Apr 26 09:22:20 192.168.122.209 [62291.467343] [tdb] Close table 'cache0.tdb' Apr 26 09:22:21 192.168.122.209 [62291.694696] [tdb] Close table 'filter0.tdb' Apr 26 09:22:21 192.168.122.209 [62291.695121] [tempesta fw] modules are stopped Apr 26 09:22:21 192.168.122.209 [62291.898089] [tempesta fw] exiting... Apr 26 09:22:21 192.168.122.209 [62292.032201] [tdb] Shutdown Tempesta DB Apr 26 09:22:21 192.168.122.209 [62292.233071] End test: sessions.test_js_challenge.JSChallengeHttp.test_servicing_non_challengeble_request_from_cache_POST Apr 26 09:22:21 192.168.122.209 [62292.246193] Start test: sessions.test_learn.LearnSessions.test_backend_fail Apr 26 09:22:22 192.168.122.209 [62293.275868] [tdb] Start Tempesta DB Apr 26 09:22:22 192.168.122.209 [62293.410403] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:22:24 192.168.122.209 [62294.845577] [tempesta fw] Configuration processing is completed. Apr 26 09:22:24 192.168.122.209 [62294.908141] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:22:24 192.168.122.209 [62295.338176] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:22:24 192.168.122.209 [62295.372520] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:22:24 192.168.122.209 [62295.406820] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:22:24 192.168.122.209 [62295.457487] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:22:24 192.168.122.209 [62295.501409] [tempesta fw] Tempesta FW is ready Apr 26 09:22:26 192.168.122.209 [62296.712097] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:26 192.168.122.209 [62296.729852] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:26 192.168.122.209 [62296.773516] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:26 192.168.122.209 [62296.775610] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:26 192.168.122.209 [62296.777826] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:26 192.168.122.209 [62296.790360] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:26 192.168.122.209 [62296.807304] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:26 192.168.122.209 [62296.849668] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:26 192.168.122.209 [62296.852274] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:26 192.168.122.209 [62296.855183] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:26 192.168.122.209 [62296.867427] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:26 192.168.122.209 [62296.884540] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:26 192.168.122.209 [62296.929496] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:26 192.168.122.209 [62296.931846] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:26 192.168.122.209 [62296.934594] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:26 192.168.122.209 [62296.945482] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:26 192.168.122.209 [62296.962265] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:26 192.168.122.209 [62297.005517] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:26 192.168.122.209 [62297.007698] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:26 192.168.122.209 [62297.009927] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:26 192.168.122.209 [62297.022627] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:26 192.168.122.209 [62297.039426] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:26 192.168.122.209 [62297.081545] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:26 192.168.122.209 [62297.083760] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:26 192.168.122.209 [62297.086552] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:26 192.168.122.209 [62297.099651] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:26 192.168.122.209 [62297.116738] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:26 192.168.122.209 [62297.161515] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:26 192.168.122.209 [62297.163694] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:26 192.168.122.209 [62297.166156] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:26 192.168.122.209 [62297.178106] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:26 192.168.122.209 [62297.194962] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:26 192.168.122.209 [62297.237553] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:26 192.168.122.209 [62297.239506] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:26 192.168.122.209 [62297.241712] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:26 192.168.122.209 [62297.255443] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:26 192.168.122.209 [62297.272328] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:26 192.168.122.209 [62297.317565] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:26 192.168.122.209 [62297.320290] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:26 192.168.122.209 [62297.322919] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:26 192.168.122.209 [62297.332440] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:26 192.168.122.209 [62297.348977] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:26 192.168.122.209 [62297.393512] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:26 192.168.122.209 [62297.395642] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:26 192.168.122.209 [62297.397756] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:26 192.168.122.209 [62297.408075] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:26 192.168.122.209 [62297.424637] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:26 192.168.122.209 [62297.469549] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:26 192.168.122.209 [62297.472271] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:26 192.168.122.209 [62297.474913] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:26 192.168.122.209 [62297.483547] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:26 192.168.122.209 [62297.500213] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:26 192.168.122.209 [62297.545640] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:26 192.168.122.209 [62297.547826] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:26 192.168.122.209 [62297.549951] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:26 192.168.122.209 [62297.559114] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:26 192.168.122.209 [62297.575665] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:27 192.168.122.209 [62297.589575] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:27 192.168.122.209 [62297.589637] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:27 192.168.122.209 [62297.590255] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:27 192.168.122.209 [62297.590572] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:27 192.168.122.209 [62297.591660] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:27 192.168.122.209 [62297.617509] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:27 192.168.122.209 [62297.618834] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:27 192.168.122.209 [62297.623440] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:27 192.168.122.209 [62297.623454] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:27 192.168.122.209 [62297.623543] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:27 192.168.122.209 [62297.623632] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:27 192.168.122.209 [62297.623656] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:27 192.168.122.209 [62297.623766] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:27 192.168.122.209 [62297.623773] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:27 192.168.122.209 [62297.623866] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:27 192.168.122.209 [62297.623904] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:27 192.168.122.209 [62297.623976] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:27 192.168.122.209 [62297.624057] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:27 192.168.122.209 [62297.624417] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:27 192.168.122.209 [62297.626376] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:27 192.168.122.209 [62297.627068] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:27 192.168.122.209 [62297.628813] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:27 192.168.122.209 [62297.629712] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:27 192.168.122.209 [62297.631460] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:27 192.168.122.209 [62297.632325] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:27 192.168.122.209 [62297.633256] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:27 192.168.122.209 [62297.634172] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:27 192.168.122.209 [62297.635108] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:27 192.168.122.209 [62297.636013] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:27 192.168.122.209 [62297.636942] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:27 192.168.122.209 [62297.647136] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:27 192.168.122.209 [62297.648084] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:27 192.168.122.209 [62297.648257] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:27 192.168.122.209 [62297.649186] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:27 192.168.122.209 [62297.652181] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:27 192.168.122.209 [62297.656526] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:27 192.168.122.209 [62297.701466] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:27 192.168.122.209 [62297.703257] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:27 192.168.122.209 [62297.705385] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:32 192.168.122.209 [62302.863759] [tdb] Close table 'client0.tdb' Apr 26 09:22:32 192.168.122.209 [62303.062059] [tdb] Close table 'sessions0.tdb' Apr 26 09:22:35 192.168.122.209 [62306.238869] [tdb] Close table 'cache0.tdb' Apr 26 09:22:35 192.168.122.209 [62306.470043] [tdb] Close table 'filter0.tdb' Apr 26 09:22:35 192.168.122.209 [62306.470467] [tempesta fw] modules are stopped Apr 26 09:22:36 192.168.122.209 [62306.641833] [tempesta fw] exiting... Apr 26 09:22:36 192.168.122.209 [62306.762575] [tdb] Shutdown Tempesta DB Apr 26 09:22:36 192.168.122.209 [62306.993240] End test: sessions.test_learn.LearnSessions.test_backend_fail Apr 26 09:22:36 192.168.122.209 [62307.010172] Start test: sessions.test_learn.LearnSessions.test_sessions Apr 26 09:22:37 192.168.122.209 [62308.059964] [tdb] Start Tempesta DB Apr 26 09:22:37 192.168.122.209 [62308.187730] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:22:38 192.168.122.209 [62309.577773] [tempesta fw] Configuration processing is completed. Apr 26 09:22:39 192.168.122.209 [62309.638970] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:22:39 192.168.122.209 [62310.057831] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:22:39 192.168.122.209 [62310.083853] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:22:39 192.168.122.209 [62310.111689] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:22:39 192.168.122.209 [62310.157576] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:22:39 192.168.122.209 [62310.197617] [tempesta fw] Tempesta FW is ready Apr 26 09:22:43 192.168.122.209 [62314.356599] [tdb] Close table 'client0.tdb' Apr 26 09:22:43 192.168.122.209 [62314.523041] [tdb] Close table 'sessions0.tdb' Apr 26 09:22:47 192.168.122.209 [62317.739074] [tdb] Close table 'cache0.tdb' Apr 26 09:22:47 192.168.122.209 [62317.988538] [tdb] Close table 'filter0.tdb' Apr 26 09:22:47 192.168.122.209 [62317.988964] [tempesta fw] modules are stopped Apr 26 09:22:47 192.168.122.209 [62318.171034] [tempesta fw] exiting... Apr 26 09:22:47 192.168.122.209 [62318.347570] [tdb] Shutdown Tempesta DB Apr 26 09:22:47 192.168.122.209 [62318.531702] End test: sessions.test_learn.LearnSessions.test_sessions Apr 26 09:22:47 192.168.122.209 [62318.548803] Start test: sessions.test_learn.LearnSessionsMultipleDiffSetCookie.test_backend_fail Apr 26 09:22:49 192.168.122.209 [62319.590827] [tdb] Start Tempesta DB Apr 26 09:22:49 192.168.122.209 [62319.731869] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:22:50 192.168.122.209 [62321.102152] [tempesta fw] Configuration processing is completed. Apr 26 09:22:50 192.168.122.209 [62321.166589] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:22:51 192.168.122.209 [62321.601955] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:22:51 192.168.122.209 [62321.627566] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:22:51 192.168.122.209 [62321.653192] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:22:51 192.168.122.209 [62321.709810] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:22:51 192.168.122.209 [62321.749751] [tempesta fw] Tempesta FW is ready Apr 26 09:22:52 192.168.122.209 [62322.975162] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:52 192.168.122.209 [62322.992435] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:52 192.168.122.209 [62323.033857] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:52 192.168.122.209 [62323.036474] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:52 192.168.122.209 [62323.039424] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:52 192.168.122.209 [62323.052486] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:52 192.168.122.209 [62323.069683] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:52 192.168.122.209 [62323.113923] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:52 192.168.122.209 [62323.116622] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:52 192.168.122.209 [62323.119263] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:52 192.168.122.209 [62323.128724] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:52 192.168.122.209 [62323.146541] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:52 192.168.122.209 [62323.189800] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:52 192.168.122.209 [62323.191446] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:52 192.168.122.209 [62323.193192] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:52 192.168.122.209 [62323.207071] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:52 192.168.122.209 [62323.224589] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:52 192.168.122.209 [62323.265842] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:52 192.168.122.209 [62323.268388] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:52 192.168.122.209 [62323.271416] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:52 192.168.122.209 [62323.284872] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:52 192.168.122.209 [62323.302254] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:52 192.168.122.209 [62323.345798] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:52 192.168.122.209 [62323.347438] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:52 192.168.122.209 [62323.349564] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:52 192.168.122.209 [62323.364109] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:52 192.168.122.209 [62323.381489] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:52 192.168.122.209 [62323.425878] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:52 192.168.122.209 [62323.428020] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:52 192.168.122.209 [62323.430350] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:52 192.168.122.209 [62323.441957] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:52 192.168.122.209 [62323.459392] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:52 192.168.122.209 [62323.501841] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:52 192.168.122.209 [62323.503844] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:52 192.168.122.209 [62323.506159] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:52 192.168.122.209 [62323.519522] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:52 192.168.122.209 [62323.536843] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:52 192.168.122.209 [62323.581869] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:52 192.168.122.209 [62323.584573] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:52 192.168.122.209 [62323.587224] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:53 192.168.122.209 [62323.596505] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:53 192.168.122.209 [62323.614019] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:53 192.168.122.209 [62323.657815] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:53 192.168.122.209 [62323.659938] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:53 192.168.122.209 [62323.662393] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:53 192.168.122.209 [62323.676492] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:53 192.168.122.209 [62323.694919] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:53 192.168.122.209 [62323.737990] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:53 192.168.122.209 [62323.740264] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:53 192.168.122.209 [62323.743199] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:53 192.168.122.209 [62323.758174] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:53 192.168.122.209 [62323.775335] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:53 192.168.122.209 [62323.817815] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:53 192.168.122.209 [62323.819439] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:53 192.168.122.209 [62323.821194] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:53 192.168.122.209 [62323.835898] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:53 192.168.122.209 [62323.853211] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:53 192.168.122.209 [62323.864287] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:53 192.168.122.209 [62323.864410] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:53 192.168.122.209 [62323.864432] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:53 192.168.122.209 [62323.864574] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:53 192.168.122.209 [62323.864910] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:53 192.168.122.209 [62323.865026] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:53 192.168.122.209 [62323.865145] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:53 192.168.122.209 [62323.865339] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:53 192.168.122.209 [62323.865465] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:53 192.168.122.209 [62323.865818] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:53 192.168.122.209 [62323.868675] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:53 192.168.122.209 [62323.869840] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:53 192.168.122.209 [62323.872750] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:53 192.168.122.209 [62323.873896] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:53 192.168.122.209 [62323.875268] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:53 192.168.122.209 [62323.876171] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:53 192.168.122.209 [62323.877569] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:53 192.168.122.209 [62323.878476] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:53 192.168.122.209 [62323.879855] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:53 192.168.122.209 [62323.880754] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:53 192.168.122.209 [62323.881720] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:53 192.168.122.209 [62323.882640] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:53 192.168.122.209 [62323.883568] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:53 192.168.122.209 [62323.884502] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:53 192.168.122.209 [62323.885414] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:53 192.168.122.209 [62323.886344] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:53 192.168.122.209 [62323.887273] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:53 192.168.122.209 [62323.888346] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:53 192.168.122.209 [62323.889116] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:53 192.168.122.209 [62323.892133] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:53 192.168.122.209 [62323.897823] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:53 192.168.122.209 [62323.898805] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:53 192.168.122.209 [62323.899741] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:53 192.168.122.209 [62323.901650] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:22:53 192.168.122.209 [62323.915652] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:53 192.168.122.209 [62323.957840] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:53 192.168.122.209 [62323.959459] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:53 192.168.122.209 [62323.961570] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:53 192.168.122.209 [62323.976733] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'default' is down Apr 26 09:22:59 192.168.122.209 [62329.635010] [tdb] Close table 'client0.tdb' Apr 26 09:22:59 192.168.122.209 [62329.833244] [tdb] Close table 'sessions0.tdb' Apr 26 09:23:02 192.168.122.209 [62333.042480] [tdb] Close table 'cache0.tdb' Apr 26 09:23:02 192.168.122.209 [62333.293533] [tdb] Close table 'filter0.tdb' Apr 26 09:23:02 192.168.122.209 [62333.293977] [tempesta fw] modules are stopped Apr 26 09:23:02 192.168.122.209 [62333.485704] [tempesta fw] exiting... Apr 26 09:23:03 192.168.122.209 [62333.642965] [tdb] Shutdown Tempesta DB Apr 26 09:23:03 192.168.122.209 [62333.856967] End test: sessions.test_learn.LearnSessionsMultipleDiffSetCookie.test_backend_fail Apr 26 09:23:03 192.168.122.209 [62333.876918] Start test: sessions.test_learn.LearnSessionsMultipleDiffSetCookie.test_sessions Apr 26 09:23:04 192.168.122.209 [62334.949246] [tdb] Start Tempesta DB Apr 26 09:23:04 192.168.122.209 [62335.085830] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:23:05 192.168.122.209 [62336.446081] [tempesta fw] Configuration processing is completed. Apr 26 09:23:05 192.168.122.209 [62336.511421] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:23:06 192.168.122.209 [62336.923749] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:23:06 192.168.122.209 [62336.950052] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:23:06 192.168.122.209 [62336.976738] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:23:06 192.168.122.209 [62337.037942] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:23:06 192.168.122.209 [62337.077962] [tempesta fw] Tempesta FW is ready Apr 26 09:23:10 192.168.122.209 [62341.191361] [tdb] Close table 'client0.tdb' Apr 26 09:23:10 192.168.122.209 [62341.369031] [tdb] Close table 'sessions0.tdb' Apr 26 09:23:13 192.168.122.209 [62344.553001] [tdb] Close table 'cache0.tdb' Apr 26 09:23:14 192.168.122.209 [62344.798691] [tdb] Close table 'filter0.tdb' Apr 26 09:23:14 192.168.122.209 [62344.799140] [tempesta fw] modules are stopped Apr 26 09:23:14 192.168.122.209 [62344.998577] [tempesta fw] exiting... Apr 26 09:23:14 192.168.122.209 [62345.116847] [tdb] Shutdown Tempesta DB Apr 26 09:23:14 192.168.122.209 [62345.330145] End test: sessions.test_learn.LearnSessionsMultipleDiffSetCookie.test_sessions Apr 26 09:23:14 192.168.122.209 [62345.339599] Start test: sessions.test_learn.LearnSessionsMultipleSameSetCookie.test Apr 26 09:23:15 192.168.122.209 [62346.486356] [tdb] Start Tempesta DB Apr 26 09:23:16 192.168.122.209 [62346.620062] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:23:17 192.168.122.209 [62347.882202] [tempesta fw] Configuration processing is completed. Apr 26 09:23:17 192.168.122.209 [62347.938538] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:23:17 192.168.122.209 [62348.358661] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:23:17 192.168.122.209 [62348.384379] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:23:17 192.168.122.209 [62348.410657] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:23:17 192.168.122.209 [62348.462161] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:23:17 192.168.122.209 [62348.510093] [tempesta fw] Tempesta FW is ready Apr 26 09:23:18 192.168.122.209 [62348.691974] [tempesta fw] Warning: Multiple sticky cookies found in response: 2 Apr 26 09:23:18 192.168.122.209 [62349.197505] [tdb] Close table 'client0.tdb' Apr 26 09:23:18 192.168.122.209 [62349.388559] [tdb] Close table 'sessions0.tdb' Apr 26 09:23:22 192.168.122.209 [62352.616286] [tdb] Close table 'cache0.tdb' Apr 26 09:23:22 192.168.122.209 [62352.863573] [tdb] Close table 'filter0.tdb' Apr 26 09:23:22 192.168.122.209 [62352.863998] [tempesta fw] modules are stopped Apr 26 09:23:22 192.168.122.209 [62353.065858] [tempesta fw] exiting... Apr 26 09:23:22 192.168.122.209 [62353.199944] [tdb] Shutdown Tempesta DB Apr 26 09:23:22 192.168.122.209 [62353.403102] End test: sessions.test_learn.LearnSessionsMultipleSameSetCookie.test Apr 26 09:23:22 192.168.122.209 [62353.416602] Start test: sessions.test_learn.LearnSessionsVhost.test_backend_fail Apr 26 09:23:23 192.168.122.209 [62354.540399] [tdb] Start Tempesta DB Apr 26 09:23:24 192.168.122.209 [62354.682868] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:23:25 192.168.122.209 [62356.466322] [tempesta fw] Configuration processing is completed. Apr 26 09:23:25 192.168.122.209 [62356.523647] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:23:26 192.168.122.209 [62356.936994] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:23:26 192.168.122.209 [62356.962653] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:23:26 192.168.122.209 [62356.988994] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:23:26 192.168.122.209 [62357.058263] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:23:26 192.168.122.209 [62357.110225] [tempesta fw] Tempesta FW is ready Apr 26 09:23:27 192.168.122.209 [62358.327398] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:27 192.168.122.209 [62358.347774] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:27 192.168.122.209 [62358.390298] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:27 192.168.122.209 [62358.391171] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:27 192.168.122.209 [62358.396233] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:27 192.168.122.209 [62358.416550] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:27 192.168.122.209 [62358.458296] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:27 192.168.122.209 [62358.459167] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:27 192.168.122.209 [62358.465208] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:27 192.168.122.209 [62358.485796] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:27 192.168.122.209 [62358.530246] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:27 192.168.122.209 [62358.531146] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:27 192.168.122.209 [62358.533321] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:27 192.168.122.209 [62358.556442] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:27 192.168.122.209 [62358.577032] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:28 192.168.122.209 [62358.622305] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:28 192.168.122.209 [62358.623228] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:28 192.168.122.209 [62358.624131] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:28 192.168.122.209 [62358.645110] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:28 192.168.122.209 [62358.665500] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:28 192.168.122.209 [62358.710281] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:28 192.168.122.209 [62358.711186] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:28 192.168.122.209 [62358.712063] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:28 192.168.122.209 [62358.729060] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:28 192.168.122.209 [62358.748718] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:28 192.168.122.209 [62358.790404] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:28 192.168.122.209 [62358.792609] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:28 192.168.122.209 [62358.795340] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:28 192.168.122.209 [62358.806274] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:28 192.168.122.209 [62358.825060] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:28 192.168.122.209 [62358.866423] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:28 192.168.122.209 [62358.869003] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:28 192.168.122.209 [62358.871705] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:28 192.168.122.209 [62358.882160] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:28 192.168.122.209 [62358.900711] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:28 192.168.122.209 [62358.942391] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:28 192.168.122.209 [62358.944592] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:28 192.168.122.209 [62358.947144] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:28 192.168.122.209 [62358.957305] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:28 192.168.122.209 [62358.977586] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:28 192.168.122.209 [62359.022364] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:28 192.168.122.209 [62359.024561] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:28 192.168.122.209 [62359.026767] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:28 192.168.122.209 [62359.034365] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:28 192.168.122.209 [62359.053340] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:28 192.168.122.209 [62359.098408] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:28 192.168.122.209 [62359.101179] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:28 192.168.122.209 [62359.103881] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:28 192.168.122.209 [62359.111585] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:28 192.168.122.209 [62359.130295] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:28 192.168.122.209 [62359.174357] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:28 192.168.122.209 [62359.176556] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:28 192.168.122.209 [62359.178865] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:28 192.168.122.209 [62359.186676] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:28 192.168.122.209 [62359.205131] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:28 192.168.122.209 [62359.222495] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:23:28 192.168.122.209 [62359.223581] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:23:28 192.168.122.209 [62359.223682] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:23:28 192.168.122.209 [62359.224555] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:23:28 192.168.122.209 [62359.224718] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:23:28 192.168.122.209 [62359.224791] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:23:28 192.168.122.209 [62359.227555] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:23:28 192.168.122.209 [62359.228369] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:23:28 192.168.122.209 [62359.230540] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:23:28 192.168.122.209 [62359.231505] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:23:28 192.168.122.209 [62359.233736] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:23:28 192.168.122.209 [62359.234537] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:23:28 192.168.122.209 [62359.236729] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:23:28 192.168.122.209 [62359.237642] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:23:28 192.168.122.209 [62359.241911] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:23:28 192.168.122.209 [62359.242882] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:23:28 192.168.122.209 [62359.243876] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:23:28 192.168.122.209 [62359.244873] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:23:28 192.168.122.209 [62359.245888] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:23:28 192.168.122.209 [62359.246890] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:23:28 192.168.122.209 [62359.247868] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:23:28 192.168.122.209 [62359.248870] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:23:28 192.168.122.209 [62359.249856] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:23:28 192.168.122.209 [62359.250848] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:23:28 192.168.122.209 [62359.251822] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:23:28 192.168.122.209 [62359.252785] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:23:28 192.168.122.209 [62359.253819] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:23:28 192.168.122.209 [62359.254803] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:23:28 192.168.122.209 [62359.255772] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:23:28 192.168.122.209 [62359.256753] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:23:28 192.168.122.209 [62359.256940] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:23:28 192.168.122.209 [62359.257767] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8002: 1 tries, keep trying... Apr 26 09:23:28 192.168.122.209 [62359.260784] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:28 192.168.122.209 [62359.262767] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:28 192.168.122.209 [62359.267039] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:28 192.168.122.209 [62359.287655] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:28 192.168.122.209 [62359.330278] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:28 192.168.122.209 [62359.331150] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:28 192.168.122.209 [62359.336327] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:28 192.168.122.209 [62359.356678] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:28 192.168.122.209 [62359.398294] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8002 in group 'vh_1_srvs' is down Apr 26 09:23:33 192.168.122.209 [62364.498963] [tdb] Close table 'client0.tdb' Apr 26 09:23:34 192.168.122.209 [62364.678741] [tdb] Close table 'sessions0.tdb' Apr 26 09:23:37 192.168.122.209 [62367.911673] [tdb] Close table 'cache0.tdb' Apr 26 09:23:37 192.168.122.209 [62368.152709] [tdb] Close table 'filter0.tdb' Apr 26 09:23:37 192.168.122.209 [62368.153131] [tempesta fw] modules are stopped Apr 26 09:23:37 192.168.122.209 [62368.399417] [tempesta fw] exiting... Apr 26 09:23:37 192.168.122.209 [62368.512460] [tdb] Shutdown Tempesta DB Apr 26 09:23:38 192.168.122.209 [62368.752967] End test: sessions.test_learn.LearnSessionsVhost.test_backend_fail Apr 26 09:23:38 192.168.122.209 [62368.765001] Start test: sessions.test_learn.LearnSessionsVhost.test_sessions Apr 26 09:23:39 192.168.122.209 [62369.833100] [tdb] Start Tempesta DB Apr 26 09:23:39 192.168.122.209 [62369.972980] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:23:41 192.168.122.209 [62371.818592] [tempesta fw] Configuration processing is completed. Apr 26 09:23:41 192.168.122.209 [62371.887618] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:23:41 192.168.122.209 [62372.323889] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:23:41 192.168.122.209 [62372.350301] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:23:41 192.168.122.209 [62372.376263] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:23:41 192.168.122.209 [62372.438451] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:23:41 192.168.122.209 [62372.478422] [tempesta fw] Tempesta FW is ready Apr 26 09:23:45 192.168.122.209 [62376.550179] [tdb] Close table 'client0.tdb' Apr 26 09:23:46 192.168.122.209 [62376.744204] [tdb] Close table 'sessions0.tdb' Apr 26 09:23:49 192.168.122.209 [62379.942131] [tdb] Close table 'cache0.tdb' Apr 26 09:23:49 192.168.122.209 [62380.184614] [tdb] Close table 'filter0.tdb' Apr 26 09:23:49 192.168.122.209 [62380.185054] [tempesta fw] modules are stopped Apr 26 09:23:49 192.168.122.209 [62380.390786] [tempesta fw] exiting... Apr 26 09:23:49 192.168.122.209 [62380.539818] [tdb] Shutdown Tempesta DB Apr 26 09:23:50 192.168.122.209 [62380.750582] End test: sessions.test_learn.LearnSessionsVhost.test_sessions Apr 26 09:23:50 192.168.122.209 [62380.768098] Start test: sessions.test_sessions.StickySessions.test_sessions Apr 26 09:23:51 192.168.122.209 [62381.797024] [tdb] Start Tempesta DB Apr 26 09:23:51 192.168.122.209 [62381.952002] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:23:52 192.168.122.209 [62383.310707] [tempesta fw] Configuration processing is completed. Apr 26 09:23:52 192.168.122.209 [62383.371309] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:23:53 192.168.122.209 [62383.788612] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:23:53 192.168.122.209 [62383.814361] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:23:53 192.168.122.209 [62383.841072] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:23:53 192.168.122.209 [62383.906590] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:23:53 192.168.122.209 [62383.946559] [tempesta fw] Tempesta FW is ready Apr 26 09:23:57 192.168.122.209 [62388.123572] [tdb] Close table 'client0.tdb' Apr 26 09:23:57 192.168.122.209 [62388.312220] [tdb] Close table 'sessions0.tdb' Apr 26 09:24:01 192.168.122.209 [62391.602427] [tdb] Close table 'cache0.tdb' Apr 26 09:24:01 192.168.122.209 [62391.874062] [tdb] Close table 'filter0.tdb' Apr 26 09:24:01 192.168.122.209 [62391.874519] [tempesta fw] modules are stopped Apr 26 09:24:01 192.168.122.209 [62392.068780] [tempesta fw] exiting... Apr 26 09:24:01 192.168.122.209 [62392.195496] [tdb] Shutdown Tempesta DB Apr 26 09:24:01 192.168.122.209 [62392.417664] End test: sessions.test_sessions.StickySessions.test_sessions Apr 26 09:24:01 192.168.122.209 [62392.440052] Start test: sessions.test_sessions.StickySessionsFailover.test_sessions Apr 26 09:24:02 192.168.122.209 [62393.434728] [tdb] Start Tempesta DB Apr 26 09:24:02 192.168.122.209 [62393.569845] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:24:04 192.168.122.209 [62395.334842] [tempesta fw] Configuration processing is completed. Apr 26 09:24:04 192.168.122.209 [62395.391653] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:24:05 192.168.122.209 [62395.817485] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:24:05 192.168.122.209 [62395.843434] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:24:05 192.168.122.209 [62395.869336] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:24:05 192.168.122.209 [62395.934738] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:24:05 192.168.122.209 [62395.978647] [tempesta fw] Tempesta FW is ready Apr 26 09:24:06 192.168.122.209 [62397.207832] [tempesta fw] sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down, try find other server Apr 26 09:24:11 192.168.122.209 [62402.470139] [tdb] Close table 'client0.tdb' Apr 26 09:24:12 192.168.122.209 [62402.661383] [tdb] Close table 'sessions0.tdb' Apr 26 09:24:15 192.168.122.209 [62405.856751] [tdb] Close table 'cache0.tdb' Apr 26 09:24:15 192.168.122.209 [62406.083944] [tdb] Close table 'filter0.tdb' Apr 26 09:24:15 192.168.122.209 [62406.084365] [tempesta fw] modules are stopped Apr 26 09:24:15 192.168.122.209 [62406.290341] [tempesta fw] exiting... Apr 26 09:24:15 192.168.122.209 [62406.435524] [tdb] Shutdown Tempesta DB Apr 26 09:24:16 192.168.122.209 [62406.643152] End test: sessions.test_sessions.StickySessionsFailover.test_sessions Apr 26 09:24:16 192.168.122.209 [62406.651530] Start test: sessions.test_sessions.StickySessionsFailover.test_sessions_reserved_server Apr 26 09:24:17 192.168.122.209 [62407.661465] [tdb] Start Tempesta DB Apr 26 09:24:17 192.168.122.209 [62407.795468] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:24:19 192.168.122.209 [62409.610992] [tempesta fw] Configuration processing is completed. Apr 26 09:24:19 192.168.122.209 [62409.665726] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:24:19 192.168.122.209 [62410.068128] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:24:19 192.168.122.209 [62410.093186] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:24:19 192.168.122.209 [62410.119788] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:24:19 192.168.122.209 [62410.210967] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:24:19 192.168.122.209 [62410.250887] [tempesta fw] Tempesta FW is ready Apr 26 09:24:20 192.168.122.209 [62411.499378] [tempesta fw] sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down, try find other server Apr 26 09:24:26 192.168.122.209 [62416.809155] [tdb] Close table 'client0.tdb' Apr 26 09:24:26 192.168.122.209 [62416.994397] [tdb] Close table 'sessions0.tdb' Apr 26 09:24:29 192.168.122.209 [62420.220342] [tdb] Close table 'cache0.tdb' Apr 26 09:24:29 192.168.122.209 [62420.459931] [tdb] Close table 'filter0.tdb' Apr 26 09:24:29 192.168.122.209 [62420.460365] [tempesta fw] modules are stopped Apr 26 09:24:30 192.168.122.209 [62420.672682] [tempesta fw] exiting... Apr 26 09:24:30 192.168.122.209 [62420.779304] [tdb] Shutdown Tempesta DB Apr 26 09:24:30 192.168.122.209 [62421.012525] End test: sessions.test_sessions.StickySessionsFailover.test_sessions_reserved_server Apr 26 09:24:30 192.168.122.209 [62421.032025] Start test: sessions.test_sessions.StickySessionsFailoverVhost.test_sessions Apr 26 09:24:31 192.168.122.209 [62422.117474] [tdb] Start Tempesta DB Apr 26 09:24:31 192.168.122.209 [62422.263726] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:24:33 192.168.122.209 [62424.195180] [tempesta fw] Configuration processing is completed. Apr 26 09:24:33 192.168.122.209 [62424.248782] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:24:34 192.168.122.209 [62424.713074] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:24:34 192.168.122.209 [62424.750713] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:24:34 192.168.122.209 [62424.779505] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:24:34 192.168.122.209 [62424.891133] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:24:34 192.168.122.209 [62424.931073] [tempesta fw] Tempesta FW is ready Apr 26 09:24:35 192.168.122.209 [62426.175824] [tempesta fw] sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down, try find other server Apr 26 09:24:40 192.168.122.209 [62431.441563] [tdb] Close table 'client0.tdb' Apr 26 09:24:41 192.168.122.209 [62431.619199] [tdb] Close table 'sessions0.tdb' Apr 26 09:24:44 192.168.122.209 [62434.945822] [tdb] Close table 'cache0.tdb' Apr 26 09:24:44 192.168.122.209 [62435.193676] [tdb] Close table 'filter0.tdb' Apr 26 09:24:44 192.168.122.209 [62435.194129] [tempesta fw] modules are stopped Apr 26 09:24:44 192.168.122.209 [62435.482603] [tempesta fw] exiting... Apr 26 09:24:45 192.168.122.209 [62435.604541] [tdb] Shutdown Tempesta DB Apr 26 09:24:45 192.168.122.209 [62435.814308] End test: sessions.test_sessions.StickySessionsFailoverVhost.test_sessions Apr 26 09:24:45 192.168.122.209 [62435.833890] Start test: sessions.test_sessions.StickySessionsFailoverVhost.test_sessions_reserved_server Apr 26 09:24:46 192.168.122.209 [62436.863440] [tdb] Start Tempesta DB Apr 26 09:24:46 192.168.122.209 [62437.018504] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:24:48 192.168.122.209 [62438.919382] [tempesta fw] Configuration processing is completed. Apr 26 09:24:48 192.168.122.209 [62438.970699] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:24:48 192.168.122.209 [62439.402330] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:24:48 192.168.122.209 [62439.428759] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:24:48 192.168.122.209 [62439.456355] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:24:48 192.168.122.209 [62439.531314] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:24:48 192.168.122.209 [62439.571257] [tempesta fw] Tempesta FW is ready Apr 26 09:24:50 192.168.122.209 [62440.820518] [tempesta fw] sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down, try find other server Apr 26 09:24:55 192.168.122.209 [62445.999086] [tdb] Close table 'client0.tdb' Apr 26 09:24:55 192.168.122.209 [62446.181778] [tdb] Close table 'sessions0.tdb' Apr 26 09:24:58 192.168.122.209 [62449.456546] [tdb] Close table 'cache0.tdb' Apr 26 09:24:59 192.168.122.209 [62449.700355] [tdb] Close table 'filter0.tdb' Apr 26 09:24:59 192.168.122.209 [62449.700785] [tempesta fw] modules are stopped Apr 26 09:24:59 192.168.122.209 [62449.934742] [tempesta fw] exiting... Apr 26 09:24:59 192.168.122.209 [62450.081300] [tdb] Shutdown Tempesta DB Apr 26 09:24:59 192.168.122.209 [62450.306405] End test: sessions.test_sessions.StickySessionsFailoverVhost.test_sessions_reserved_server Apr 26 09:24:59 192.168.122.209 [62450.320554] Start test: sessions.test_sessions.StickySessionsPersistense.test_sessions Apr 26 09:25:00 192.168.122.209 [62451.355096] [tdb] Start Tempesta DB Apr 26 09:25:00 192.168.122.209 [62451.492303] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:25:02 192.168.122.209 [62453.211861] [tempesta fw] Configuration processing is completed. Apr 26 09:25:02 192.168.122.209 [62453.264014] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:25:03 192.168.122.209 [62453.676520] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:25:03 192.168.122.209 [62453.702549] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:25:03 192.168.122.209 [62453.728435] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:25:03 192.168.122.209 [62453.811507] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:25:03 192.168.122.209 [62453.895437] [tempesta fw] Tempesta FW is ready Apr 26 09:25:04 192.168.122.209 [62455.129514] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:04 192.168.122.209 [62455.179536] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:04 192.168.122.209 [62455.215073] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:04 192.168.122.209 [62455.243039] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:04 192.168.122.209 [62455.295569] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:04 192.168.122.209 [62455.327027] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:04 192.168.122.209 [62455.356478] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:04 192.168.122.209 [62455.407557] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:04 192.168.122.209 [62455.439099] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:04 192.168.122.209 [62455.471005] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:04 192.168.122.209 [62455.519602] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:04 192.168.122.209 [62455.552656] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:04 192.168.122.209 [62455.585090] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:05 192.168.122.209 [62455.635524] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:05 192.168.122.209 [62455.667359] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:05 192.168.122.209 [62455.698954] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:05 192.168.122.209 [62455.747483] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:05 192.168.122.209 [62455.788803] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:05 192.168.122.209 [62455.821627] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:05 192.168.122.209 [62455.871737] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:05 192.168.122.209 [62455.905150] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:05 192.168.122.209 [62455.934350] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:05 192.168.122.209 [62455.983572] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:05 192.168.122.209 [62456.016426] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:05 192.168.122.209 [62456.024902] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:05 192.168.122.209 [62456.024941] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:05 192.168.122.209 [62456.025234] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:05 192.168.122.209 [62456.025394] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:05 192.168.122.209 [62456.025571] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:05 192.168.122.209 [62456.025954] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:05 192.168.122.209 [62456.026840] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:05 192.168.122.209 [62456.027245] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:05 192.168.122.209 [62456.027370] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:05 192.168.122.209 [62456.027390] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:05 192.168.122.209 [62456.027497] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:05 192.168.122.209 [62456.027612] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:05 192.168.122.209 [62456.027723] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:05 192.168.122.209 [62456.027775] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:05 192.168.122.209 [62456.027881] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:05 192.168.122.209 [62456.028034] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:05 192.168.122.209 [62456.028165] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:05 192.168.122.209 [62456.028376] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:05 192.168.122.209 [62456.028525] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:05 192.168.122.209 [62456.028649] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:05 192.168.122.209 [62456.028756] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:05 192.168.122.209 [62456.028809] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:05 192.168.122.209 [62456.028941] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:05 192.168.122.209 [62456.029084] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:05 192.168.122.209 [62456.029242] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:05 192.168.122.209 [62456.029353] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:05 192.168.122.209 [62456.029469] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:05 192.168.122.209 [62456.029628] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:05 192.168.122.209 [62456.050900] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:05 192.168.122.209 [62456.051909] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:05 192.168.122.209 [62456.052872] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:05 192.168.122.209 [62456.053939] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:05 192.168.122.209 [62456.074439] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:05 192.168.122.209 [62456.127471] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:05 192.168.122.209 [62456.160067] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:05 192.168.122.209 [62456.189731] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:05 192.168.122.209 [62456.239589] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:05 192.168.122.209 [62456.273723] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:05 192.168.122.209 [62456.303105] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:05 192.168.122.209 [62456.355634] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:05 192.168.122.209 [62456.385565] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:05 192.168.122.209 [62456.418322] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:05 192.168.122.209 [62456.467550] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:05 192.168.122.209 [62456.514214] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:05 192.168.122.209 [62456.549077] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:06 192.168.122.209 [62456.599572] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:06 192.168.122.209 [62456.629320] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:06 192.168.122.209 [62456.661668] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:06 192.168.122.209 [62456.711569] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:06 192.168.122.209 [62456.742937] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:06 192.168.122.209 [62456.774623] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:06 192.168.122.209 [62456.823592] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:06 192.168.122.209 [62456.856762] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:06 192.168.122.209 [62456.887687] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:06 192.168.122.209 [62456.939620] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:06 192.168.122.209 [62456.972471] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:06 192.168.122.209 [62457.001453] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:06 192.168.122.209 [62457.054202] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:06 192.168.122.209 [62457.086516] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:06 192.168.122.209 [62457.115060] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:06 192.168.122.209 [62457.167570] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:06 192.168.122.209 [62457.199077] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:06 192.168.122.209 [62457.229295] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:06 192.168.122.209 [62457.279539] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:06 192.168.122.209 [62457.311673] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:06 192.168.122.209 [62457.344469] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:06 192.168.122.209 [62457.395559] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:06 192.168.122.209 [62457.426200] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:06 192.168.122.209 [62457.458780] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:06 192.168.122.209 [62457.507603] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:06 192.168.122.209 [62457.539589] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:06 192.168.122.209 [62457.570947] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:11 192.168.122.209 [62462.051459] [tdb] Close table 'client0.tdb' Apr 26 09:25:11 192.168.122.209 [62462.262980] [tdb] Close table 'sessions0.tdb' Apr 26 09:25:14 192.168.122.209 [62465.473335] [tdb] Close table 'cache0.tdb' Apr 26 09:25:15 192.168.122.209 [62465.715311] [tdb] Close table 'filter0.tdb' Apr 26 09:25:15 192.168.122.209 [62465.715761] [tempesta fw] modules are stopped Apr 26 09:25:15 192.168.122.209 [62465.929108] [tempesta fw] exiting... Apr 26 09:25:15 192.168.122.209 [62466.053268] [tdb] Shutdown Tempesta DB Apr 26 09:25:15 192.168.122.209 [62466.310613] End test: sessions.test_sessions.StickySessionsPersistense.test_sessions Apr 26 09:25:15 192.168.122.209 [62466.320325] Start test: sessions.test_sessions.StickySessionsPersistenseVhost.test_sessions Apr 26 09:25:16 192.168.122.209 [62467.354780] [tdb] Start Tempesta DB Apr 26 09:25:16 192.168.122.209 [62467.496176] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:25:18 192.168.122.209 [62469.423758] [tempesta fw] Configuration processing is completed. Apr 26 09:25:18 192.168.122.209 [62469.475245] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:25:19 192.168.122.209 [62469.957496] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:25:19 192.168.122.209 [62469.990446] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:25:19 192.168.122.209 [62470.025238] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:25:19 192.168.122.209 [62470.135742] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:25:19 192.168.122.209 [62470.187636] [tempesta fw] Tempesta FW is ready Apr 26 09:25:20 192.168.122.209 [62471.439938] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:20 192.168.122.209 [62471.491705] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:20 192.168.122.209 [62471.524111] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:20 192.168.122.209 [62471.553925] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:21 192.168.122.209 [62471.607760] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:21 192.168.122.209 [62471.639372] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:21 192.168.122.209 [62471.671865] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:21 192.168.122.209 [62471.719726] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:21 192.168.122.209 [62471.753020] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:21 192.168.122.209 [62471.785609] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:21 192.168.122.209 [62471.835732] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:21 192.168.122.209 [62471.867236] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:21 192.168.122.209 [62471.899486] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:21 192.168.122.209 [62471.947711] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:21 192.168.122.209 [62471.981238] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:21 192.168.122.209 [62472.012134] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:21 192.168.122.209 [62472.063734] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:21 192.168.122.209 [62472.096263] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:21 192.168.122.209 [62472.125780] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:21 192.168.122.209 [62472.175631] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:21 192.168.122.209 [62472.209872] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:21 192.168.122.209 [62472.240920] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:21 192.168.122.209 [62472.291776] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:21 192.168.122.209 [62472.324373] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:21 192.168.122.209 [62472.344899] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:21 192.168.122.209 [62472.345402] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:21 192.168.122.209 [62472.345408] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:21 192.168.122.209 [62472.345446] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:21 192.168.122.209 [62472.345607] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:21 192.168.122.209 [62472.345733] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:21 192.168.122.209 [62472.345887] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:21 192.168.122.209 [62472.346012] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:21 192.168.122.209 [62472.346243] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:21 192.168.122.209 [62472.346382] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:21 192.168.122.209 [62472.346518] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:21 192.168.122.209 [62472.346657] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:21 192.168.122.209 [62472.346783] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:21 192.168.122.209 [62472.346923] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:21 192.168.122.209 [62472.347057] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:21 192.168.122.209 [62472.347197] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:21 192.168.122.209 [62472.347277] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:21 192.168.122.209 [62472.347968] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:21 192.168.122.209 [62472.348820] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:21 192.168.122.209 [62472.351738] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:21 192.168.122.209 [62472.352598] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:21 192.168.122.209 [62472.355512] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:21 192.168.122.209 [62472.356393] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:21 192.168.122.209 [62472.358296] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:21 192.168.122.209 [62472.359225] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:21 192.168.122.209 [62472.360436] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:21 192.168.122.209 [62472.361357] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:21 192.168.122.209 [62472.362581] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:21 192.168.122.209 [62472.363482] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:21 192.168.122.209 [62472.364824] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:21 192.168.122.209 [62472.365644] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:21 192.168.122.209 [62472.368712] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 09:25:21 192.168.122.209 [62472.369681] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:21 192.168.122.209 [62472.435725] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:21 192.168.122.209 [62472.469945] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:21 192.168.122.209 [62472.499143] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:21 192.168.122.209 [62472.551686] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:21 192.168.122.209 [62472.583699] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:22 192.168.122.209 [62472.613397] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:22 192.168.122.209 [62472.663713] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:22 192.168.122.209 [62472.696268] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:22 192.168.122.209 [62472.728539] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:22 192.168.122.209 [62472.775910] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:22 192.168.122.209 [62472.809972] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:22 192.168.122.209 [62472.841314] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:22 192.168.122.209 [62472.887873] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:22 192.168.122.209 [62472.924234] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:22 192.168.122.209 [62472.956144] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:22 192.168.122.209 [62473.003742] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:22 192.168.122.209 [62473.037336] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:22 192.168.122.209 [62473.068303] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:22 192.168.122.209 [62473.115721] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:22 192.168.122.209 [62473.149148] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:22 192.168.122.209 [62473.179380] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:22 192.168.122.209 [62473.227750] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:22 192.168.122.209 [62473.265698] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:22 192.168.122.209 [62473.294669] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:22 192.168.122.209 [62473.343716] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:22 192.168.122.209 [62473.391080] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:22 192.168.122.209 [62473.418083] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:22 192.168.122.209 [62473.467820] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:22 192.168.122.209 [62473.501184] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:22 192.168.122.209 [62473.530215] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:22 192.168.122.209 [62473.579807] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:23 192.168.122.209 [62473.613432] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:23 192.168.122.209 [62473.642581] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:23 192.168.122.209 [62473.691751] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:23 192.168.122.209 [62473.724725] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:23 192.168.122.209 [62473.754730] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:23 192.168.122.209 [62473.803742] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:23 192.168.122.209 [62473.836943] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:23 192.168.122.209 [62473.868377] [tempesta fw] Warning: sticky sched: pinned server 127.0.0.3:8001 in group 'primary' is down Apr 26 09:25:27 192.168.122.209 [62478.488956] [tdb] Close table 'client0.tdb' Apr 26 09:25:28 192.168.122.209 [62478.675927] [tdb] Close table 'sessions0.tdb' Apr 26 09:25:31 192.168.122.209 [62481.950651] [tdb] Close table 'cache0.tdb' Apr 26 09:25:31 192.168.122.209 [62482.202613] [tdb] Close table 'filter0.tdb' Apr 26 09:25:31 192.168.122.209 [62482.203015] [tempesta fw] modules are stopped Apr 26 09:25:31 192.168.122.209 [62482.404114] [tempesta fw] exiting... Apr 26 09:25:31 192.168.122.209 [62482.539438] [tdb] Shutdown Tempesta DB Apr 26 09:25:32 192.168.122.209 [62482.745587] End test: sessions.test_sessions.StickySessionsPersistenseVhost.test_sessions Apr 26 09:25:32 192.168.122.209 [62482.756902] Start test: sessions.test_sessions.StickySessionsVhost.test_sessions Apr 26 09:25:33 192.168.122.209 [62483.825410] [tdb] Start Tempesta DB Apr 26 09:25:33 192.168.122.209 [62483.960657] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:25:35 192.168.122.209 [62485.871979] [tempesta fw] Configuration processing is completed. Apr 26 09:25:35 192.168.122.209 [62485.936185] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:25:35 192.168.122.209 [62486.352044] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:25:35 192.168.122.209 [62486.377343] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:25:35 192.168.122.209 [62486.402292] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:25:35 192.168.122.209 [62486.463916] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:25:35 192.168.122.209 [62486.507857] [tempesta fw] Tempesta FW is ready Apr 26 09:25:40 192.168.122.209 [62490.620821] [tdb] Close table 'client0.tdb' Apr 26 09:25:40 192.168.122.209 [62490.805235] [tdb] Close table 'sessions0.tdb' Apr 26 09:25:43 192.168.122.209 [62494.083358] [tdb] Close table 'cache0.tdb' Apr 26 09:25:43 192.168.122.209 [62494.335877] [tdb] Close table 'filter0.tdb' Apr 26 09:25:43 192.168.122.209 [62494.336275] [tempesta fw] modules are stopped Apr 26 09:25:43 192.168.122.209 [62494.542090] [tempesta fw] exiting... Apr 26 09:25:44 192.168.122.209 [62494.709056] [tdb] Shutdown Tempesta DB Apr 26 09:25:44 192.168.122.209 [62494.896947] End test: sessions.test_sessions.StickySessionsVhost.test_sessions Apr 26 09:25:44 192.168.122.209 [62494.930173] Start test: sessions.test_sticky_sess_stress.LotOfClients.test Apr 26 09:25:46 192.168.122.209 [62497.281187] [tdb] Start Tempesta DB Apr 26 09:25:46 192.168.122.209 [62497.439668] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:25:49 192.168.122.209 [62500.184547] [tempesta fw] Configuration processing is completed. Apr 26 09:25:49 192.168.122.209 [62500.237213] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:25:49 192.168.122.209 [62500.265623] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:25:49 192.168.122.209 [62500.292784] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:25:50 192.168.122.209 [62500.996082] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:25:50 192.168.122.209 [62501.096019] [tempesta fw] Tempesta FW is ready Apr 26 09:26:04 192.168.122.209 [62515.334869] [tdb] Close table 'client0.tdb' Apr 26 09:26:05 192.168.122.209 [62515.684890] [tdb] Close table 'sessions0.tdb' Apr 26 09:26:05 192.168.122.209 [62516.207144] [tdb] Close table 'filter0.tdb' Apr 26 09:26:05 192.168.122.209 [62516.207557] [tempesta fw] modules are stopped Apr 26 09:26:07 192.168.122.209 [62517.847656] [tempesta fw] exiting... Apr 26 09:26:07 192.168.122.209 [62518.288922] [tdb] Shutdown Tempesta DB Apr 26 09:26:08 192.168.122.209 [62519.347917] End test: sessions.test_sticky_sess_stress.LotOfClients.test Apr 26 09:26:08 192.168.122.209 [62519.359242] Start test: sessions.test_sticky_sess_stress.OneClient.test Apr 26 09:26:11 192.168.122.209 [62521.780707] [tdb] Start Tempesta DB Apr 26 09:26:11 192.168.122.209 [62521.946787] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:26:13 192.168.122.209 [62524.228403] [tempesta fw] Configuration processing is completed. Apr 26 09:26:13 192.168.122.209 [62524.298034] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:26:13 192.168.122.209 [62524.340104] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:26:13 192.168.122.209 [62524.377421] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:26:14 192.168.122.209 [62525.096425] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:26:14 192.168.122.209 [62525.148340] [tempesta fw] Tempesta FW is ready Apr 26 09:26:27 192.168.122.209 [62537.719366] [tdb] Close table 'client0.tdb' Apr 26 09:26:27 192.168.122.209 [62537.915761] [tdb] Close table 'sessions0.tdb' Apr 26 09:26:27 192.168.122.209 [62538.155732] [tdb] Close table 'filter0.tdb' Apr 26 09:26:27 192.168.122.209 [62538.156142] [tempesta fw] modules are stopped Apr 26 09:26:27 192.168.122.209 [62538.326951] [tempesta fw] exiting... Apr 26 09:26:27 192.168.122.209 [62538.472319] [tdb] Shutdown Tempesta DB Apr 26 09:26:28 192.168.122.209 [62539.445394] End test: sessions.test_sticky_sess_stress.OneClient.test Apr 26 09:26:28 192.168.122.209 [62539.458846] Start test: t_access_log.test_access_log.AccessLogTest.test_success_path_http1x Apr 26 09:26:30 192.168.122.209 [62540.699625] [tdb] Start Tempesta DB Apr 26 09:26:30 192.168.122.209 [62540.868626] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:26:31 192.168.122.209 [62541.732719] [tempesta fw] Configuration processing is completed. Apr 26 09:26:31 192.168.122.209 [62541.789928] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:26:31 192.168.122.209 [62541.823616] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:26:31 192.168.122.209 [62541.853973] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:26:31 192.168.122.209 [62541.896605] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:26:31 192.168.122.209 [62541.936570] [tempesta fw] Tempesta FW is ready Apr 26 09:26:31 192.168.122.209 [62542.130170] [tempesta fw] 127.0.0.2 "localhost" "GET /expect-status-200 HTTP/1.1" 200 12 "referer-code-string-200" "ua-code-string-200" "ja5t=0" "ja5h=266000c01c0" Apr 26 09:26:31 192.168.122.209 [62542.223030] [tempesta fw] 127.0.0.2 "localhost" "GET /expect-status-204 HTTP/1.1" 204 0 "referer-code-string-204" "ua-code-string-204" "ja5t=0" "ja5h=266000c01c0" Apr 26 09:26:31 192.168.122.209 [62542.309656] [tempesta fw] 127.0.0.2 "localhost" "GET /expect-status-302 HTTP/1.1" 302 13 "referer-code-string-302" "ua-code-string-302" "ja5t=0" "ja5h=266000c01c0" Apr 26 09:26:31 192.168.122.209 [62542.421164] [tempesta fw] 127.0.0.2 "localhost" "GET /expect-status-404 HTTP/1.1" 404 14 "referer-code-string-404" "ua-code-string-404" "ja5t=0" "ja5h=266000c01c0" Apr 26 09:26:31 192.168.122.209 [62542.524880] [tempesta fw] 127.0.0.2 "localhost" "GET /expect-status-500 HTTP/1.1" 500 26 "referer-code-string-500" "ua-code-string-500" "ja5t=0" "ja5h=266000c01c0" Apr 26 09:26:32 192.168.122.209 [62543.032915] [tdb] Close table 'client0.tdb' Apr 26 09:26:32 192.168.122.209 [62543.235129] [tdb] Close table 'sessions0.tdb' Apr 26 09:26:32 192.168.122.209 [62543.487144] [tdb] Close table 'filter0.tdb' Apr 26 09:26:32 192.168.122.209 [62543.487606] [tempesta fw] modules are stopped Apr 26 09:26:33 192.168.122.209 [62543.695744] [tempesta fw] exiting... Apr 26 09:26:33 192.168.122.209 [62543.838522] [tdb] Shutdown Tempesta DB Apr 26 09:26:33 192.168.122.209 [62544.040547] End test: t_access_log.test_access_log.AccessLogTest.test_success_path_http1x Apr 26 09:26:33 192.168.122.209 [62544.053204] Start test: t_access_log.test_access_log.AccessLogTest.test_uri_truncate Apr 26 09:26:34 192.168.122.209 [62545.342026] [tdb] Start Tempesta DB Apr 26 09:26:34 192.168.122.209 [62545.493122] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:26:35 192.168.122.209 [62546.376742] [tempesta fw] Configuration processing is completed. Apr 26 09:26:35 192.168.122.209 [62546.435169] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:26:35 192.168.122.209 [62546.470462] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:26:35 192.168.122.209 [62546.500876] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:26:35 192.168.122.209 [62546.544667] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:26:35 192.168.122.209 [62546.584627] [tempesta fw] Tempesta FW is ready Apr 26 09:26:36 192.168.122.209 [62547.379074] [tempesta fw] 127.0.0.2 "localhost" "GET /too-long-uri_111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111... HTTP/1.1" 200 0 "referer" "user-agent" "ja5t=0" "ja5h=252000c01c0" Apr 26 09:26:37 192.168.122.209 [62547.891532] [tdb] Close table 'client0.tdb' Apr 26 09:26:37 192.168.122.209 [62548.076138] [tdb] Close table 'sessions0.tdb' Apr 26 09:26:37 192.168.122.209 [62548.306088] [tdb] Close table 'filter0.tdb' Apr 26 09:26:37 192.168.122.209 [62548.306505] [tempesta fw] modules are stopped Apr 26 09:26:37 192.168.122.209 [62548.497668] [tempesta fw] exiting... Apr 26 09:26:38 192.168.122.209 [62548.632973] [tdb] Shutdown Tempesta DB Apr 26 09:26:38 192.168.122.209 [62548.849668] End test: t_access_log.test_access_log.AccessLogTest.test_uri_truncate Apr 26 09:26:38 192.168.122.209 [62548.869572] Start test: t_access_log.test_access_log_h2.FrangTest.test_tempesta Apr 26 09:26:39 192.168.122.209 [62550.278932] [tdb] Start Tempesta DB Apr 26 09:26:39 192.168.122.209 [62550.418413] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:26:40 192.168.122.209 [62551.198142] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62551.198142] Maybe that's fine, but it's worth checking the [62551.198142] config - if there is no relations between the [62551.198142] names, then host name confusion attack is possible. Apr 26 09:26:40 192.168.122.209 [62551.264785] [tempesta fw] Configuration processing is completed. Apr 26 09:26:40 192.168.122.209 [62551.315327] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:26:41 192.168.122.209 [62551.720369] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:26:41 192.168.122.209 [62551.746458] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:26:41 192.168.122.209 [62551.772686] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:26:41 192.168.122.209 [62551.860737] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:26:41 192.168.122.209 [62551.900671] [tempesta fw] Tempesta FW is ready Apr 26 09:26:41 192.168.122.209 [62552.086848] [tempesta fw] Warning: frang: HTTP URI length exceeded for 127.0.0.1: 32 (lim=10) Apr 26 09:26:41 192.168.122.209 [62552.087667] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.1 Apr 26 09:26:41 192.168.122.209 [62552.088348] [tempesta fw] 127.0.0.1 "default" "GET /some-uri-longer-than-10-symbols HTTP/2.0" 403 0 "http2-referer-403" "http2-user-agent-403" "ja5t=66cbf8ccef17001a" "ja5h=5b4cec5f008c03c0" Apr 26 09:26:42 192.168.122.209 [62552.694925] [tdb] Close table 'client0.tdb' Apr 26 09:26:42 192.168.122.209 [62552.888027] [tdb] Close table 'sessions0.tdb' Apr 26 09:26:45 192.168.122.209 [62556.138477] [tdb] Close table 'cache0.tdb' Apr 26 09:26:45 192.168.122.209 [62556.387169] [tdb] Close table 'filter0.tdb' Apr 26 09:26:45 192.168.122.209 [62556.387609] [tempesta fw] modules are stopped Apr 26 09:26:46 192.168.122.209 [62556.602807] [tempesta fw] exiting... Apr 26 09:26:46 192.168.122.209 [62556.751737] [tdb] Shutdown Tempesta DB Apr 26 09:26:46 192.168.122.209 [62557.053000] End test: t_access_log.test_access_log_h2.FrangTest.test_tempesta Apr 26 09:26:46 192.168.122.209 [62557.066037] Start test: t_access_log.test_access_log_h2.Response200Test.test_tempesta Apr 26 09:26:47 192.168.122.209 [62558.408927] [tdb] Start Tempesta DB Apr 26 09:26:47 192.168.122.209 [62558.533291] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:26:49 192.168.122.209 [62559.878133] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62559.878133] Maybe that's fine, but it's worth checking the [62559.878133] config - if there is no relations between the [62559.878133] names, then host name confusion attack is possible. Apr 26 09:26:49 192.168.122.209 [62559.944891] [tempesta fw] Configuration processing is completed. Apr 26 09:26:49 192.168.122.209 [62560.004668] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:26:49 192.168.122.209 [62560.438400] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:26:49 192.168.122.209 [62560.466182] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:26:49 192.168.122.209 [62560.492880] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:26:49 192.168.122.209 [62560.566136] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:26:50 192.168.122.209 [62560.604804] [tempesta fw] Tempesta FW is ready Apr 26 09:26:50 192.168.122.209 [62560.781739] [tempesta fw] 127.0.0.1 "default" "GET / HTTP/2.0" 200 0 "http2-referer-200" "http2-user-agent-200" "ja5t=66cbf8ccef17001a" "ja5h=5b4cec5f008c03c0" Apr 26 09:26:50 192.168.122.209 [62561.375645] [tdb] Close table 'client0.tdb' Apr 26 09:26:50 192.168.122.209 [62561.581720] [tdb] Close table 'sessions0.tdb' Apr 26 09:26:54 192.168.122.209 [62564.869371] [tdb] Close table 'cache0.tdb' Apr 26 09:26:54 192.168.122.209 [62565.124445] [tdb] Close table 'filter0.tdb' Apr 26 09:26:54 192.168.122.209 [62565.124906] [tempesta fw] modules are stopped Apr 26 09:26:54 192.168.122.209 [62565.389551] [tempesta fw] exiting... Apr 26 09:26:54 192.168.122.209 [62565.506770] [tdb] Shutdown Tempesta DB Apr 26 09:26:55 192.168.122.209 [62565.803200] End test: t_access_log.test_access_log_h2.Response200Test.test_tempesta Apr 26 09:26:55 192.168.122.209 [62565.817828] Start test: t_access_log.test_access_log_h2.Response204Test.test_tempesta Apr 26 09:26:56 192.168.122.209 [62567.193314] [tdb] Start Tempesta DB Apr 26 09:26:56 192.168.122.209 [62567.336853] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:26:58 192.168.122.209 [62568.750252] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62568.750252] Maybe that's fine, but it's worth checking the [62568.750252] config - if there is no relations between the [62568.750252] names, then host name confusion attack is possible. Apr 26 09:26:58 192.168.122.209 [62568.809037] [tempesta fw] Configuration processing is completed. Apr 26 09:26:58 192.168.122.209 [62568.866871] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:26:58 192.168.122.209 [62569.274004] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:26:58 192.168.122.209 [62569.300957] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:26:58 192.168.122.209 [62569.326646] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:26:58 192.168.122.209 [62569.388909] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:26:58 192.168.122.209 [62569.428915] [tempesta fw] Tempesta FW is ready Apr 26 09:26:59 192.168.122.209 [62569.615559] [tempesta fw] 127.0.0.1 "default" "GET / HTTP/2.0" 204 0 "http2-referer-204" "http2-user-agent-204" "ja5t=66cbf8ccef17001a" "ja5h=5b4cec5f008c03c0" Apr 26 09:26:59 192.168.122.209 [62570.216036] [tdb] Close table 'client0.tdb' Apr 26 09:26:59 192.168.122.209 [62570.410611] [tdb] Close table 'sessions0.tdb' Apr 26 09:27:03 192.168.122.209 [62573.741889] [tdb] Close table 'cache0.tdb' Apr 26 09:27:03 192.168.122.209 [62574.009531] [tdb] Close table 'filter0.tdb' Apr 26 09:27:03 192.168.122.209 [62574.009969] [tempesta fw] modules are stopped Apr 26 09:27:03 192.168.122.209 [62574.205963] [tempesta fw] exiting... Apr 26 09:27:03 192.168.122.209 [62574.324766] [tdb] Shutdown Tempesta DB Apr 26 09:27:04 192.168.122.209 [62574.625414] End test: t_access_log.test_access_log_h2.Response204Test.test_tempesta Apr 26 09:27:04 192.168.122.209 [62574.644346] Start test: t_access_log.test_access_log_h2.Response302Test.test_tempesta Apr 26 09:27:05 192.168.122.209 [62576.044700] [tdb] Start Tempesta DB Apr 26 09:27:05 192.168.122.209 [62576.179789] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:27:07 192.168.122.209 [62577.618235] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62577.618235] Maybe that's fine, but it's worth checking the [62577.618235] config - if there is no relations between the [62577.618235] names, then host name confusion attack is possible. Apr 26 09:27:07 192.168.122.209 [62577.685141] [tempesta fw] Configuration processing is completed. Apr 26 09:27:07 192.168.122.209 [62577.747818] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:27:07 192.168.122.209 [62578.166523] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:27:07 192.168.122.209 [62578.192961] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:27:07 192.168.122.209 [62578.219087] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:27:07 192.168.122.209 [62578.289075] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:27:07 192.168.122.209 [62578.329078] [tempesta fw] Tempesta FW is ready Apr 26 09:27:07 192.168.122.209 [62578.530910] [tempesta fw] 127.0.0.1 "default" "GET / HTTP/2.0" 302 154 "http2-referer-302" "http2-user-agent-302" "ja5t=66cbf8ccef17001a" "ja5h=5b4cec5f008c03c0" Apr 26 09:27:08 192.168.122.209 [62579.100068] [tdb] Close table 'client0.tdb' Apr 26 09:27:08 192.168.122.209 [62579.287651] [tdb] Close table 'sessions0.tdb' Apr 26 09:27:11 192.168.122.209 [62582.588580] [tdb] Close table 'cache0.tdb' Apr 26 09:27:12 192.168.122.209 [62582.819743] [tdb] Close table 'filter0.tdb' Apr 26 09:27:12 192.168.122.209 [62582.820476] [tempesta fw] modules are stopped Apr 26 09:27:12 192.168.122.209 [62583.031062] [tempesta fw] exiting... Apr 26 09:27:12 192.168.122.209 [62583.194211] [tdb] Shutdown Tempesta DB Apr 26 09:27:12 192.168.122.209 [62583.495561] End test: t_access_log.test_access_log_h2.Response302Test.test_tempesta Apr 26 09:27:12 192.168.122.209 [62583.517932] Start test: t_access_log.test_access_log_h2.Response404Test.test_tempesta Apr 26 09:27:14 192.168.122.209 [62584.881519] [tdb] Start Tempesta DB Apr 26 09:27:14 192.168.122.209 [62585.015729] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:27:15 192.168.122.209 [62586.446883] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62586.446883] Maybe that's fine, but it's worth checking the [62586.446883] config - if there is no relations between the [62586.446883] names, then host name confusion attack is possible. Apr 26 09:27:15 192.168.122.209 [62586.505243] [tempesta fw] Configuration processing is completed. Apr 26 09:27:15 192.168.122.209 [62586.563153] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:27:16 192.168.122.209 [62586.980280] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:27:16 192.168.122.209 [62587.007206] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:27:16 192.168.122.209 [62587.033957] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:27:16 192.168.122.209 [62587.125226] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:27:16 192.168.122.209 [62587.169130] [tempesta fw] Tempesta FW is ready Apr 26 09:27:16 192.168.122.209 [62587.363701] [tempesta fw] 127.0.0.1 "default" "GET / HTTP/2.0" 404 162 "http2-referer-404" "http2-user-agent-404" "ja5t=66cbf8ccef17001a" "ja5h=5b4cec5f008c03c0" Apr 26 09:27:17 192.168.122.209 [62587.907792] [tdb] Close table 'client0.tdb' Apr 26 09:27:17 192.168.122.209 [62588.122093] [tdb] Close table 'sessions0.tdb' Apr 26 09:27:20 192.168.122.209 [62591.402286] [tdb] Close table 'cache0.tdb' Apr 26 09:27:21 192.168.122.209 [62591.645339] [tdb] Close table 'filter0.tdb' Apr 26 09:27:21 192.168.122.209 [62591.645800] [tempesta fw] modules are stopped Apr 26 09:27:21 192.168.122.209 [62591.890940] [tempesta fw] exiting... Apr 26 09:27:21 192.168.122.209 [62592.023842] [tdb] Shutdown Tempesta DB Apr 26 09:27:21 192.168.122.209 [62592.320886] End test: t_access_log.test_access_log_h2.Response404Test.test_tempesta Apr 26 09:27:21 192.168.122.209 [62592.336856] Start test: t_access_log.test_access_log_h2.Response500Test.test_tempesta Apr 26 09:27:23 192.168.122.209 [62593.729567] [tdb] Start Tempesta DB Apr 26 09:27:23 192.168.122.209 [62593.888543] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:27:24 192.168.122.209 [62595.386632] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62595.386632] Maybe that's fine, but it's worth checking the [62595.386632] config - if there is no relations between the [62595.386632] names, then host name confusion attack is possible. Apr 26 09:27:24 192.168.122.209 [62595.461468] [tempesta fw] Configuration processing is completed. Apr 26 09:27:24 192.168.122.209 [62595.544184] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:27:25 192.168.122.209 [62595.967403] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:27:25 192.168.122.209 [62596.010616] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:27:25 192.168.122.209 [62596.047423] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:27:25 192.168.122.209 [62596.125298] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:27:25 192.168.122.209 [62596.173289] [tempesta fw] Tempesta FW is ready Apr 26 09:27:25 192.168.122.209 [62596.366536] [tempesta fw] 127.0.0.1 "default" "GET / HTTP/2.0" 500 186 "http2-referer-500" "http2-user-agent-500" "ja5t=66cbf8ccef17001a" "ja5h=5b4cec5f008c03c0" Apr 26 09:27:26 192.168.122.209 [62596.964344] [tdb] Close table 'client0.tdb' Apr 26 09:27:26 192.168.122.209 [62597.148977] [tdb] Close table 'sessions0.tdb' Apr 26 09:27:29 192.168.122.209 [62600.489167] [tdb] Close table 'cache0.tdb' Apr 26 09:27:30 192.168.122.209 [62600.735910] [tdb] Close table 'filter0.tdb' Apr 26 09:27:30 192.168.122.209 [62600.736358] [tempesta fw] modules are stopped Apr 26 09:27:30 192.168.122.209 [62600.916257] [tempesta fw] exiting... Apr 26 09:27:30 192.168.122.209 [62601.039896] [tdb] Shutdown Tempesta DB Apr 26 09:27:30 192.168.122.209 [62601.285265] End test: t_access_log.test_access_log_h2.Response500Test.test_tempesta Apr 26 09:27:30 192.168.122.209 [62601.303887] Start test: t_access_log.test_access_log_h2.TruncateUriTest.test_tempesta Apr 26 09:27:32 192.168.122.209 [62602.760465] [tdb] Start Tempesta DB Apr 26 09:27:32 192.168.122.209 [62602.905705] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:27:33 192.168.122.209 [62604.278751] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62604.278751] Maybe that's fine, but it's worth checking the [62604.278751] config - if there is no relations between the [62604.278751] names, then host name confusion attack is possible. Apr 26 09:27:33 192.168.122.209 [62604.353780] [tempesta fw] Configuration processing is completed. Apr 26 09:27:33 192.168.122.209 [62604.421749] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:27:34 192.168.122.209 [62604.992393] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:27:34 192.168.122.209 [62605.028156] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:27:34 192.168.122.209 [62605.063810] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:27:34 192.168.122.209 [62605.141410] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:27:34 192.168.122.209 [62605.181288] [tempesta fw] Tempesta FW is ready Apr 26 09:27:34 192.168.122.209 [62605.362983] [tempesta fw] 127.0.0.1 "default" "GET /truncated-uri_____________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________... HTTP/2.0" 200 0 "http2-referer-200" "http2-user-agent-200" "ja5t=66cbf8ccef17001a" "ja5h=5b4cec5f008c03c0" Apr 26 09:27:35 192.168.122.209 [62605.942839] [tdb] Close table 'client0.tdb' Apr 26 09:27:35 192.168.122.209 [62606.172101] [tdb] Close table 'sessions0.tdb' Apr 26 09:27:38 192.168.122.209 [62609.377092] [tdb] Close table 'cache0.tdb' Apr 26 09:27:39 192.168.122.209 [62609.630448] [tdb] Close table 'filter0.tdb' Apr 26 09:27:39 192.168.122.209 [62609.630871] [tempesta fw] modules are stopped Apr 26 09:27:39 192.168.122.209 [62609.817692] [tempesta fw] exiting... Apr 26 09:27:39 192.168.122.209 [62609.968677] [tdb] Shutdown Tempesta DB Apr 26 09:27:39 192.168.122.209 [62610.250733] End test: t_access_log.test_access_log_h2.TruncateUriTest.test_tempesta Apr 26 09:27:39 192.168.122.209 [62610.267416] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_boundary_values_0x40_from_0x41_to_0x7e Apr 26 09:27:40 192.168.122.209 [62611.416743] [tdb] Start Tempesta DB Apr 26 09:27:40 192.168.122.209 [62611.554304] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:27:42 192.168.122.209 [62613.023756] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62613.023756] Maybe that's fine, but it's worth checking the [62613.023756] config - if there is no relations between the [62613.023756] names, then host name confusion attack is possible. Apr 26 09:27:42 192.168.122.209 [62613.133554] [tempesta fw] Configuration processing is completed. Apr 26 09:27:42 192.168.122.209 [62613.191165] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:27:43 192.168.122.209 [62613.622702] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:27:43 192.168.122.209 [62613.649004] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:27:43 192.168.122.209 [62613.675105] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:27:43 192.168.122.209 [62613.769518] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:27:43 192.168.122.209 [62613.771328] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:27:43 192.168.122.209 [62613.813489] [tempesta fw] Tempesta FW is ready Apr 26 09:27:43 192.168.122.209 [62614.026239] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_Path input=0x65('example@'), len=9, off=1 Apr 26 09:27:43 192.168.122.209 [62614.453576] [tdb] Close table 'client0.tdb' Apr 26 09:27:44 192.168.122.209 [62614.667267] [tdb] Close table 'sessions0.tdb' Apr 26 09:27:47 192.168.122.209 [62618.020542] [tdb] Close table 'cache0.tdb' Apr 26 09:27:47 192.168.122.209 [62618.264316] [tdb] Close table 'filter0.tdb' Apr 26 09:27:47 192.168.122.209 [62618.264880] [tempesta fw] modules are stopped Apr 26 09:27:47 192.168.122.209 [62618.466556] [tempesta fw] exiting... Apr 26 09:27:47 192.168.122.209 [62618.580749] [tdb] Shutdown Tempesta DB Apr 26 09:27:48 192.168.122.209 [62618.812095] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_boundary_values_0x40_from_0x41_to_0x7e Apr 26 09:27:48 192.168.122.209 [62618.823550] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_boundary_values_0x41_from_0x41_to_0x7e Apr 26 09:27:49 192.168.122.209 [62620.051702] [tdb] Start Tempesta DB Apr 26 09:27:49 192.168.122.209 [62620.181867] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:27:50 192.168.122.209 [62621.546452] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62621.546452] Maybe that's fine, but it's worth checking the [62621.546452] config - if there is no relations between the [62621.546452] names, then host name confusion attack is possible. Apr 26 09:27:51 192.168.122.209 [62621.649662] [tempesta fw] Configuration processing is completed. Apr 26 09:27:51 192.168.122.209 [62621.715559] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:27:51 192.168.122.209 [62622.291474] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:27:51 192.168.122.209 [62622.326449] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:27:51 192.168.122.209 [62622.361666] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:27:51 192.168.122.209 [62622.405628] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:27:51 192.168.122.209 [62622.407321] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:27:51 192.168.122.209 [62622.453599] [tempesta fw] Tempesta FW is ready Apr 26 09:27:52 192.168.122.209 [62623.080114] [tdb] Close table 'client0.tdb' Apr 26 09:27:52 192.168.122.209 [62623.264786] [tdb] Close table 'sessions0.tdb' Apr 26 09:27:55 192.168.122.209 [62626.526525] [tdb] Close table 'cache0.tdb' Apr 26 09:27:56 192.168.122.209 [62626.759528] [tdb] Close table 'filter0.tdb' Apr 26 09:27:56 192.168.122.209 [62626.759967] [tempesta fw] modules are stopped Apr 26 09:27:56 192.168.122.209 [62626.942053] [tempesta fw] exiting... Apr 26 09:27:56 192.168.122.209 [62627.065190] [tdb] Shutdown Tempesta DB Apr 26 09:27:56 192.168.122.209 [62627.262597] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_boundary_values_0x41_from_0x41_to_0x7e Apr 26 09:27:56 192.168.122.209 [62627.291944] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_boundary_values_0x7e_from_0x41_to_0x7e Apr 26 09:27:57 192.168.122.209 [62628.466972] [tdb] Start Tempesta DB Apr 26 09:27:58 192.168.122.209 [62628.622772] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:27:59 192.168.122.209 [62630.006547] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62630.006547] Maybe that's fine, but it's worth checking the [62630.006547] config - if there is no relations between the [62630.006547] names, then host name confusion attack is possible. Apr 26 09:27:59 192.168.122.209 [62630.105753] [tempesta fw] Configuration processing is completed. Apr 26 09:27:59 192.168.122.209 [62630.166046] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:28:00 192.168.122.209 [62630.730953] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:28:00 192.168.122.209 [62630.766240] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:28:00 192.168.122.209 [62630.801593] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:28:00 192.168.122.209 [62630.853745] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:28:00 192.168.122.209 [62630.855421] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:28:00 192.168.122.209 [62630.901698] [tempesta fw] Tempesta FW is ready Apr 26 09:28:00 192.168.122.209 [62631.551548] [tdb] Close table 'client0.tdb' Apr 26 09:28:01 192.168.122.209 [62631.752135] [tdb] Close table 'sessions0.tdb' Apr 26 09:28:04 192.168.122.209 [62635.073851] [tdb] Close table 'cache0.tdb' Apr 26 09:28:04 192.168.122.209 [62635.323136] [tdb] Close table 'filter0.tdb' Apr 26 09:28:04 192.168.122.209 [62635.323615] [tempesta fw] modules are stopped Apr 26 09:28:04 192.168.122.209 [62635.554623] [tempesta fw] exiting... Apr 26 09:28:05 192.168.122.209 [62635.665620] [tdb] Shutdown Tempesta DB Apr 26 09:28:05 192.168.122.209 [62635.891475] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_boundary_values_0x7e_from_0x41_to_0x7e Apr 26 09:28:05 192.168.122.209 [62635.907790] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_boundary_values_0x7f_from_0x41_to_0x7e Apr 26 09:28:06 192.168.122.209 [62637.204337] [tdb] Start Tempesta DB Apr 26 09:28:06 192.168.122.209 [62637.366766] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:28:08 192.168.122.209 [62638.847169] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62638.847169] Maybe that's fine, but it's worth checking the [62638.847169] config - if there is no relations between the [62638.847169] names, then host name confusion attack is possible. Apr 26 09:28:08 192.168.122.209 [62638.937937] [tempesta fw] Configuration processing is completed. Apr 26 09:28:08 192.168.122.209 [62638.997055] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:28:08 192.168.122.209 [62639.427780] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:28:08 192.168.122.209 [62639.454065] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:28:08 192.168.122.209 [62639.480357] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:28:08 192.168.122.209 [62639.545869] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:28:08 192.168.122.209 [62639.547587] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:28:09 192.168.122.209 [62639.597792] [tempesta fw] Tempesta FW is ready Apr 26 09:28:09 192.168.122.209 [62639.801212] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_Path input=0x65('example'), len=10, off=1 Apr 26 09:28:09 192.168.122.209 [62640.248244] [tdb] Close table 'client0.tdb' Apr 26 09:28:09 192.168.122.209 [62640.413741] [tdb] Close table 'sessions0.tdb' Apr 26 09:28:12 192.168.122.209 [62643.592413] [tdb] Close table 'cache0.tdb' Apr 26 09:28:13 192.168.122.209 [62643.826744] [tdb] Close table 'filter0.tdb' Apr 26 09:28:13 192.168.122.209 [62643.827172] [tempesta fw] modules are stopped Apr 26 09:28:13 192.168.122.209 [62644.058348] [tempesta fw] exiting... Apr 26 09:28:13 192.168.122.209 [62644.176873] [tdb] Shutdown Tempesta DB Apr 26 09:28:13 192.168.122.209 [62644.405717] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_boundary_values_0x7f_from_0x41_to_0x7e Apr 26 09:28:13 192.168.122.209 [62644.417510] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_boundary_values_disallowed_0x5f Apr 26 09:28:15 192.168.122.209 [62645.718767] [tdb] Start Tempesta DB Apr 26 09:28:15 192.168.122.209 [62645.858824] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:28:16 192.168.122.209 [62647.395205] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62647.395205] Maybe that's fine, but it's worth checking the [62647.395205] config - if there is no relations between the [62647.395205] names, then host name confusion attack is possible. Apr 26 09:28:16 192.168.122.209 [62647.497992] [tempesta fw] Configuration processing is completed. Apr 26 09:28:16 192.168.122.209 [62647.558442] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:28:17 192.168.122.209 [62648.046977] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:28:17 192.168.122.209 [62648.082141] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:28:17 192.168.122.209 [62648.116634] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:28:17 192.168.122.209 [62648.169969] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:28:17 192.168.122.209 [62648.171663] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:28:17 192.168.122.209 [62648.209908] [tempesta fw] Tempesta FW is ready Apr 26 09:28:17 192.168.122.209 [62648.395422] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_Path input=0x65('example_'), len=9, off=1 Apr 26 09:28:18 192.168.122.209 [62648.839375] [tdb] Close table 'client0.tdb' Apr 26 09:28:18 192.168.122.209 [62649.035787] [tdb] Close table 'sessions0.tdb' Apr 26 09:28:21 192.168.122.209 [62652.446489] [tdb] Close table 'cache0.tdb' Apr 26 09:28:22 192.168.122.209 [62652.692093] [tdb] Close table 'filter0.tdb' Apr 26 09:28:22 192.168.122.209 [62652.692543] [tempesta fw] modules are stopped Apr 26 09:28:22 192.168.122.209 [62652.923691] [tempesta fw] exiting... Apr 26 09:28:22 192.168.122.209 [62653.038330] [tdb] Shutdown Tempesta DB Apr 26 09:28:22 192.168.122.209 [62653.265119] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_boundary_values_disallowed_0x5f Apr 26 09:28:22 192.168.122.209 [62653.275964] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_cookie_brange_allow_many_cookie Apr 26 09:28:23 192.168.122.209 [62654.354365] [tdb] Start Tempesta DB Apr 26 09:28:23 192.168.122.209 [62654.490168] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:28:25 192.168.122.209 [62655.935480] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62655.935480] Maybe that's fine, but it's worth checking the [62655.935480] config - if there is no relations between the [62655.935480] names, then host name confusion attack is possible. Apr 26 09:28:25 192.168.122.209 [62656.054169] [tempesta fw] Configuration processing is completed. Apr 26 09:28:25 192.168.122.209 [62656.106145] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:28:25 192.168.122.209 [62656.571190] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:28:26 192.168.122.209 [62656.602718] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:28:26 192.168.122.209 [62656.633917] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:28:26 192.168.122.209 [62656.686124] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:28:26 192.168.122.209 [62656.687785] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:28:26 192.168.122.209 [62656.734605] [tempesta fw] Tempesta FW is ready Apr 26 09:28:26 192.168.122.209 [62657.391003] [tdb] Close table 'client0.tdb' Apr 26 09:28:26 192.168.122.209 [62657.577380] [tdb] Close table 'sessions0.tdb' Apr 26 09:28:30 192.168.122.209 [62660.812856] [tdb] Close table 'cache0.tdb' Apr 26 09:28:30 192.168.122.209 [62661.037649] [tdb] Close table 'filter0.tdb' Apr 26 09:28:30 192.168.122.209 [62661.038080] [tempesta fw] modules are stopped Apr 26 09:28:30 192.168.122.209 [62661.255117] [tempesta fw] exiting... Apr 26 09:28:30 192.168.122.209 [62661.406327] [tdb] Shutdown Tempesta DB Apr 26 09:28:31 192.168.122.209 [62661.637701] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_cookie_brange_allow_many_cookie Apr 26 09:28:31 192.168.122.209 [62661.664642] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_cookie_brange_check_value Apr 26 09:28:32 192.168.122.209 [62662.730552] [tdb] Start Tempesta DB Apr 26 09:28:32 192.168.122.209 [62662.873220] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:28:33 192.168.122.209 [62664.331489] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62664.331489] Maybe that's fine, but it's worth checking the [62664.331489] config - if there is no relations between the [62664.331489] names, then host name confusion attack is possible. Apr 26 09:28:33 192.168.122.209 [62664.430218] [tempesta fw] Configuration processing is completed. Apr 26 09:28:33 192.168.122.209 [62664.497176] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:28:34 192.168.122.209 [62664.948215] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:28:34 192.168.122.209 [62664.976880] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:28:34 192.168.122.209 [62665.006958] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:28:34 192.168.122.209 [62665.066175] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:28:34 192.168.122.209 [62665.067889] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:28:34 192.168.122.209 [62665.110139] [tempesta fw] Tempesta FW is ready Apr 26 09:28:34 192.168.122.209 [62665.288858] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrCookieV input=0x69('id=QWErty'), len=9, off=0 Apr 26 09:28:35 192.168.122.209 [62665.708215] [tdb] Close table 'client0.tdb' Apr 26 09:28:35 192.168.122.209 [62665.892014] [tdb] Close table 'sessions0.tdb' Apr 26 09:28:38 192.168.122.209 [62669.108149] [tdb] Close table 'cache0.tdb' Apr 26 09:28:38 192.168.122.209 [62669.335076] [tdb] Close table 'filter0.tdb' Apr 26 09:28:38 192.168.122.209 [62669.335502] [tempesta fw] modules are stopped Apr 26 09:28:38 192.168.122.209 [62669.532277] [tempesta fw] exiting... Apr 26 09:28:39 192.168.122.209 [62669.661925] [tdb] Shutdown Tempesta DB Apr 26 09:28:39 192.168.122.209 [62669.885695] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_cookie_brange_check_value Apr 26 09:28:39 192.168.122.209 [62669.910067] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_cookie_brange_not_check_name Apr 26 09:28:40 192.168.122.209 [62670.960891] [tdb] Start Tempesta DB Apr 26 09:28:40 192.168.122.209 [62671.110465] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:28:41 192.168.122.209 [62672.479583] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62672.479583] Maybe that's fine, but it's worth checking the [62672.479583] config - if there is no relations between the [62672.479583] names, then host name confusion attack is possible. Apr 26 09:28:41 192.168.122.209 [62672.582293] [tempesta fw] Configuration processing is completed. Apr 26 09:28:42 192.168.122.209 [62672.638212] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:28:42 192.168.122.209 [62673.064550] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:28:42 192.168.122.209 [62673.102320] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:28:42 192.168.122.209 [62673.129313] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:28:42 192.168.122.209 [62673.170271] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:28:42 192.168.122.209 [62673.171949] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:28:42 192.168.122.209 [62673.210237] [tempesta fw] Tempesta FW is ready Apr 26 09:28:43 192.168.122.209 [62673.799127] [tdb] Close table 'client0.tdb' Apr 26 09:28:43 192.168.122.209 [62673.984957] [tdb] Close table 'sessions0.tdb' Apr 26 09:28:46 192.168.122.209 [62677.186779] [tdb] Close table 'cache0.tdb' Apr 26 09:28:46 192.168.122.209 [62677.430566] [tdb] Close table 'filter0.tdb' Apr 26 09:28:46 192.168.122.209 [62677.430986] [tempesta fw] modules are stopped Apr 26 09:28:47 192.168.122.209 [62677.624597] [tempesta fw] exiting... Apr 26 09:28:47 192.168.122.209 [62677.746650] [tdb] Shutdown Tempesta DB Apr 26 09:28:47 192.168.122.209 [62677.950899] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_cookie_brange_not_check_name Apr 26 09:28:47 192.168.122.209 [62677.967264] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_ctext_vchar_brange_allow Apr 26 09:28:48 192.168.122.209 [62679.104302] [tdb] Start Tempesta DB Apr 26 09:28:48 192.168.122.209 [62679.243223] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:28:50 192.168.122.209 [62680.603814] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62680.603814] Maybe that's fine, but it's worth checking the [62680.603814] config - if there is no relations between the [62680.603814] names, then host name confusion attack is possible. Apr 26 09:28:50 192.168.122.209 [62680.710443] [tempesta fw] Configuration processing is completed. Apr 26 09:28:50 192.168.122.209 [62680.770626] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:28:50 192.168.122.209 [62681.243589] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:28:50 192.168.122.209 [62681.273310] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:28:50 192.168.122.209 [62681.303489] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:28:50 192.168.122.209 [62681.370431] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:28:50 192.168.122.209 [62681.372164] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:28:50 192.168.122.209 [62681.430338] [tempesta fw] Tempesta FW is ready Apr 26 09:28:51 192.168.122.209 [62682.084011] [tdb] Close table 'client0.tdb' Apr 26 09:28:51 192.168.122.209 [62682.274835] [tdb] Close table 'sessions0.tdb' Apr 26 09:28:54 192.168.122.209 [62685.494971] [tdb] Close table 'cache0.tdb' Apr 26 09:28:55 192.168.122.209 [62685.744564] [tdb] Close table 'filter0.tdb' Apr 26 09:28:55 192.168.122.209 [62685.745018] [tempesta fw] modules are stopped Apr 26 09:28:55 192.168.122.209 [62685.948294] [tempesta fw] exiting... Apr 26 09:28:55 192.168.122.209 [62686.092455] [tdb] Shutdown Tempesta DB Apr 26 09:28:55 192.168.122.209 [62686.317762] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_ctext_vchar_brange_allow Apr 26 09:28:55 192.168.122.209 [62686.331573] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_ctext_vchar_brange_disallow Apr 26 09:28:56 192.168.122.209 [62687.424598] [tdb] Start Tempesta DB Apr 26 09:28:56 192.168.122.209 [62687.548340] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:28:58 192.168.122.209 [62688.887773] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62688.887773] Maybe that's fine, but it's worth checking the [62688.887773] config - if there is no relations between the [62688.887773] names, then host name confusion attack is possible. Apr 26 09:28:58 192.168.122.209 [62688.990523] [tempesta fw] Configuration processing is completed. Apr 26 09:28:58 192.168.122.209 [62689.052337] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:28:58 192.168.122.209 [62689.550318] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:28:58 192.168.122.209 [62689.592993] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:28:59 192.168.122.209 [62689.626819] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:28:59 192.168.122.209 [62689.678491] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:28:59 192.168.122.209 [62689.680191] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:28:59 192.168.122.209 [62689.718427] [tempesta fw] Tempesta FW is ready Apr 26 09:28:59 192.168.122.209 [62689.879398] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrUser_AgentV input=0x4d('Mozilla/5.0 %'), len=13, off=0 Apr 26 09:28:59 192.168.122.209 [62690.330900] [tdb] Close table 'client0.tdb' Apr 26 09:28:59 192.168.122.209 [62690.498323] [tdb] Close table 'sessions0.tdb' Apr 26 09:29:03 192.168.122.209 [62693.905632] [tdb] Close table 'cache0.tdb' Apr 26 09:29:03 192.168.122.209 [62694.163438] [tdb] Close table 'filter0.tdb' Apr 26 09:29:03 192.168.122.209 [62694.163874] [tempesta fw] modules are stopped Apr 26 09:29:03 192.168.122.209 [62694.356372] [tempesta fw] exiting... Apr 26 09:29:03 192.168.122.209 [62694.482664] [tdb] Shutdown Tempesta DB Apr 26 09:29:04 192.168.122.209 [62694.701700] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_ctext_vchar_brange_disallow Apr 26 09:29:04 192.168.122.209 [62694.712730] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_etag_brange_if_none_match_allow Apr 26 09:29:05 192.168.122.209 [62695.792488] [tdb] Start Tempesta DB Apr 26 09:29:05 192.168.122.209 [62695.944154] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:29:06 192.168.122.209 [62697.371930] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62697.371930] Maybe that's fine, but it's worth checking the [62697.371930] config - if there is no relations between the [62697.371930] names, then host name confusion attack is possible. Apr 26 09:29:06 192.168.122.209 [62697.470638] [tempesta fw] Configuration processing is completed. Apr 26 09:29:06 192.168.122.209 [62697.527322] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:29:07 192.168.122.209 [62698.002474] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:29:07 192.168.122.209 [62698.032931] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:29:07 192.168.122.209 [62698.064566] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:29:07 192.168.122.209 [62698.106606] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:29:07 192.168.122.209 [62698.108389] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:29:07 192.168.122.209 [62698.146486] [tempesta fw] Tempesta FW is ready Apr 26 09:29:08 192.168.122.209 [62698.801004] [tdb] Close table 'client0.tdb' Apr 26 09:29:08 192.168.122.209 [62698.986912] [tdb] Close table 'sessions0.tdb' Apr 26 09:29:11 192.168.122.209 [62702.219200] [tdb] Close table 'cache0.tdb' Apr 26 09:29:11 192.168.122.209 [62702.443579] [tdb] Close table 'filter0.tdb' Apr 26 09:29:11 192.168.122.209 [62702.443998] [tempesta fw] modules are stopped Apr 26 09:29:12 192.168.122.209 [62702.646000] [tempesta fw] exiting... Apr 26 09:29:12 192.168.122.209 [62702.770615] [tdb] Shutdown Tempesta DB Apr 26 09:29:12 192.168.122.209 [62702.979725] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_etag_brange_if_none_match_allow Apr 26 09:29:12 192.168.122.209 [62702.988927] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_etag_brange_if_none_match_allow_all Apr 26 09:29:13 192.168.122.209 [62704.044681] [tdb] Start Tempesta DB Apr 26 09:29:13 192.168.122.209 [62704.181569] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:29:14 192.168.122.209 [62705.571971] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62705.571971] Maybe that's fine, but it's worth checking the [62705.571971] config - if there is no relations between the [62705.571971] names, then host name confusion attack is possible. Apr 26 09:29:15 192.168.122.209 [62705.682720] [tempesta fw] Configuration processing is completed. Apr 26 09:29:15 192.168.122.209 [62705.745587] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:29:15 192.168.122.209 [62706.238805] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:29:15 192.168.122.209 [62706.269955] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:29:15 192.168.122.209 [62706.301183] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:29:15 192.168.122.209 [62706.346696] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:29:15 192.168.122.209 [62706.348401] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:29:15 192.168.122.209 [62706.390694] [tempesta fw] Tempesta FW is ready Apr 26 09:29:16 192.168.122.209 [62707.042734] [tdb] Close table 'client0.tdb' Apr 26 09:29:16 192.168.122.209 [62707.240359] [tdb] Close table 'sessions0.tdb' Apr 26 09:29:19 192.168.122.209 [62710.487266] [tdb] Close table 'cache0.tdb' Apr 26 09:29:20 192.168.122.209 [62710.715101] [tdb] Close table 'filter0.tdb' Apr 26 09:29:20 192.168.122.209 [62710.715534] [tempesta fw] modules are stopped Apr 26 09:29:20 192.168.122.209 [62710.928923] [tempesta fw] exiting... Apr 26 09:29:20 192.168.122.209 [62711.075917] [tdb] Shutdown Tempesta DB Apr 26 09:29:20 192.168.122.209 [62711.283075] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_etag_brange_if_none_match_allow_all Apr 26 09:29:20 192.168.122.209 [62711.303855] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_etag_brange_if_none_match_allow_weak Apr 26 09:29:21 192.168.122.209 [62712.493849] [tdb] Start Tempesta DB Apr 26 09:29:22 192.168.122.209 [62712.646371] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:29:23 192.168.122.209 [62714.064102] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62714.064102] Maybe that's fine, but it's worth checking the [62714.064102] config - if there is no relations between the [62714.064102] names, then host name confusion attack is possible. Apr 26 09:29:23 192.168.122.209 [62714.170844] [tempesta fw] Configuration processing is completed. Apr 26 09:29:23 192.168.122.209 [62714.232343] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:29:24 192.168.122.209 [62714.780859] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:29:24 192.168.122.209 [62714.816399] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:29:24 192.168.122.209 [62714.851942] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:29:24 192.168.122.209 [62714.890826] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:29:24 192.168.122.209 [62714.892589] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:29:24 192.168.122.209 [62714.930772] [tempesta fw] Tempesta FW is ready Apr 26 09:29:24 192.168.122.209 [62715.567104] [tdb] Close table 'client0.tdb' Apr 26 09:29:25 192.168.122.209 [62715.772969] [tdb] Close table 'sessions0.tdb' Apr 26 09:29:28 192.168.122.209 [62719.034852] [tdb] Close table 'cache0.tdb' Apr 26 09:29:28 192.168.122.209 [62719.283889] [tdb] Close table 'filter0.tdb' Apr 26 09:29:28 192.168.122.209 [62719.284317] [tempesta fw] modules are stopped Apr 26 09:29:28 192.168.122.209 [62719.526049] [tempesta fw] exiting... Apr 26 09:29:29 192.168.122.209 [62719.644512] [tdb] Shutdown Tempesta DB Apr 26 09:29:29 192.168.122.209 [62719.840682] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_etag_brange_if_none_match_allow_weak Apr 26 09:29:29 192.168.122.209 [62719.850500] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_etag_brange_if_none_match_disallow Apr 26 09:29:30 192.168.122.209 [62720.929035] [tdb] Start Tempesta DB Apr 26 09:29:30 192.168.122.209 [62721.085352] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:29:31 192.168.122.209 [62722.492241] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62722.492241] Maybe that's fine, but it's worth checking the [62722.492241] config - if there is no relations between the [62722.492241] names, then host name confusion attack is possible. Apr 26 09:29:32 192.168.122.209 [62722.598961] [tempesta fw] Configuration processing is completed. Apr 26 09:29:32 192.168.122.209 [62722.655694] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:29:32 192.168.122.209 [62723.080281] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:29:32 192.168.122.209 [62723.106607] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:29:32 192.168.122.209 [62723.132725] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:29:32 192.168.122.209 [62723.174954] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:29:32 192.168.122.209 [62723.176656] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:29:32 192.168.122.209 [62723.218854] [tempesta fw] Tempesta FW is ready Apr 26 09:29:32 192.168.122.209 [62723.397657] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrIf_None_MatchV input=0x22('"asdfQWErty"'), len=12, off=0 Apr 26 09:29:33 192.168.122.209 [62723.817403] [tdb] Close table 'client0.tdb' Apr 26 09:29:33 192.168.122.209 [62724.006465] [tdb] Close table 'sessions0.tdb' Apr 26 09:29:36 192.168.122.209 [62727.351103] [tdb] Close table 'cache0.tdb' Apr 26 09:29:36 192.168.122.209 [62727.588585] [tdb] Close table 'filter0.tdb' Apr 26 09:29:36 192.168.122.209 [62727.588990] [tempesta fw] modules are stopped Apr 26 09:29:37 192.168.122.209 [62727.807249] [tempesta fw] exiting... Apr 26 09:29:37 192.168.122.209 [62727.918687] [tdb] Shutdown Tempesta DB Apr 26 09:29:37 192.168.122.209 [62728.135632] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_etag_brange_if_none_match_disallow Apr 26 09:29:37 192.168.122.209 [62728.163470] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_etag_brange_if_none_match_many_values Apr 26 09:29:38 192.168.122.209 [62729.438053] [tdb] Start Tempesta DB Apr 26 09:29:38 192.168.122.209 [62729.592888] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:29:40 192.168.122.209 [62731.100388] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62731.100388] Maybe that's fine, but it's worth checking the [62731.100388] config - if there is no relations between the [62731.100388] names, then host name confusion attack is possible. Apr 26 09:29:40 192.168.122.209 [62731.207074] [tempesta fw] Configuration processing is completed. Apr 26 09:29:40 192.168.122.209 [62731.269537] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:29:41 192.168.122.209 [62731.773799] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:29:41 192.168.122.209 [62731.800312] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:29:41 192.168.122.209 [62731.826641] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:29:41 192.168.122.209 [62731.867060] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:29:41 192.168.122.209 [62731.868758] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:29:41 192.168.122.209 [62731.906967] [tempesta fw] Tempesta FW is ready Apr 26 09:29:41 192.168.122.209 [62732.584148] [tdb] Close table 'client0.tdb' Apr 26 09:29:42 192.168.122.209 [62732.812584] [tdb] Close table 'sessions0.tdb' Apr 26 09:29:45 192.168.122.209 [62736.440941] [tdb] Close table 'cache0.tdb' Apr 26 09:29:46 192.168.122.209 [62736.730000] [tdb] Close table 'filter0.tdb' Apr 26 09:29:46 192.168.122.209 [62736.730471] [tempesta fw] modules are stopped Apr 26 09:29:46 192.168.122.209 [62736.924692] [tempesta fw] exiting... Apr 26 09:29:46 192.168.122.209 [62737.026491] [tdb] Shutdown Tempesta DB Apr 26 09:29:46 192.168.122.209 [62737.246084] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_etag_brange_if_none_match_many_values Apr 26 09:29:46 192.168.122.209 [62737.267017] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_nctl_brange_request_negative Apr 26 09:29:47 192.168.122.209 [62738.464581] [tdb] Start Tempesta DB Apr 26 09:29:48 192.168.122.209 [62738.620674] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:29:49 192.168.122.209 [62740.168464] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62740.168464] Maybe that's fine, but it's worth checking the [62740.168464] config - if there is no relations between the [62740.168464] names, then host name confusion attack is possible. Apr 26 09:29:49 192.168.122.209 [62740.275162] [tempesta fw] Configuration processing is completed. Apr 26 09:29:49 192.168.122.209 [62740.339565] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:29:50 192.168.122.209 [62740.783480] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:29:50 192.168.122.209 [62740.811698] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:29:50 192.168.122.209 [62740.846553] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:29:50 192.168.122.209 [62740.895132] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:29:50 192.168.122.209 [62740.896539] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:29:50 192.168.122.209 [62740.947076] [tempesta fw] Tempesta FW is ready Apr 26 09:29:50 192.168.122.209 [62741.142896] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrIf_Modified_SinceV input=0x4d('Mon, 12 Dec 2016'), len=30, off=0 Apr 26 09:29:50 192.168.122.209 [62741.540864] [tdb] Close table 'client0.tdb' Apr 26 09:29:51 192.168.122.209 [62741.765969] [tdb] Close table 'sessions0.tdb' Apr 26 09:29:54 192.168.122.209 [62744.982823] [tdb] Close table 'cache0.tdb' Apr 26 09:29:54 192.168.122.209 [62745.222296] [tdb] Close table 'filter0.tdb' Apr 26 09:29:54 192.168.122.209 [62745.222719] [tempesta fw] modules are stopped Apr 26 09:29:54 192.168.122.209 [62745.422708] [tempesta fw] exiting... Apr 26 09:29:54 192.168.122.209 [62745.589732] [tdb] Shutdown Tempesta DB Apr 26 09:29:55 192.168.122.209 [62745.808575] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_nctl_brange_request_negative Apr 26 09:29:55 192.168.122.209 [62745.818896] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_nctl_brange_request_positive Apr 26 09:29:56 192.168.122.209 [62747.093787] [tdb] Start Tempesta DB Apr 26 09:29:56 192.168.122.209 [62747.240235] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:29:58 192.168.122.209 [62748.676520] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62748.676520] Maybe that's fine, but it's worth checking the [62748.676520] config - if there is no relations between the [62748.676520] names, then host name confusion attack is possible. Apr 26 09:29:58 192.168.122.209 [62748.775320] [tempesta fw] Configuration processing is completed. Apr 26 09:29:58 192.168.122.209 [62748.834498] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:29:58 192.168.122.209 [62749.258962] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:29:58 192.168.122.209 [62749.285660] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:29:58 192.168.122.209 [62749.312941] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:29:58 192.168.122.209 [62749.351181] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:29:58 192.168.122.209 [62749.352856] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:29:58 192.168.122.209 [62749.391209] [tempesta fw] Tempesta FW is ready Apr 26 09:29:59 192.168.122.209 [62750.053646] [tdb] Close table 'client0.tdb' Apr 26 09:29:59 192.168.122.209 [62750.240099] [tdb] Close table 'sessions0.tdb' Apr 26 09:30:02 192.168.122.209 [62753.439917] [tdb] Close table 'cache0.tdb' Apr 26 09:30:03 192.168.122.209 [62753.686907] [tdb] Close table 'filter0.tdb' Apr 26 09:30:03 192.168.122.209 [62753.687711] [tempesta fw] modules are stopped Apr 26 09:30:03 192.168.122.209 [62753.928246] [tempesta fw] exiting... Apr 26 09:30:03 192.168.122.209 [62754.067834] [tdb] Shutdown Tempesta DB Apr 26 09:30:03 192.168.122.209 [62754.271799] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_nctl_brange_request_positive Apr 26 09:30:03 192.168.122.209 [62754.287008] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_nctl_brange_response_negative Apr 26 09:30:04 192.168.122.209 [62755.554620] [tdb] Start Tempesta DB Apr 26 09:30:05 192.168.122.209 [62755.714975] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:30:06 192.168.122.209 [62757.124699] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62757.124699] Maybe that's fine, but it's worth checking the [62757.124699] config - if there is no relations between the [62757.124699] names, then host name confusion attack is possible. Apr 26 09:30:06 192.168.122.209 [62757.227421] [tempesta fw] Configuration processing is completed. Apr 26 09:30:06 192.168.122.209 [62757.287607] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:30:07 192.168.122.209 [62757.754077] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:30:07 192.168.122.209 [62757.782017] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:30:07 192.168.122.209 [62757.810406] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:30:07 192.168.122.209 [62757.859343] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:30:07 192.168.122.209 [62757.861047] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:30:07 192.168.122.209 [62757.899304] [tempesta fw] Tempesta FW is ready Apr 26 09:30:07 192.168.122.209 [62758.118790] [tempesta fw] Warning: Parser error: state=Resp_HdrDateV input(-0)=0x25('%') data_len=1 off=0 Apr 26 09:30:07 192.168.122.209 [62758.121555] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 09:30:07 192.168.122.209 [62758.139752] [tempesta fw] Warning: Parser error: state=Resp_HdrExpiresV input(-0)=0x25('%') data_len=1 off=0 Apr 26 09:30:07 192.168.122.209 [62758.141601] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 09:30:07 192.168.122.209 [62758.163939] [tempesta fw] Warning: Parser error: state=Resp_HdrLast_ModifiedV input(-0)=0x25('%') data_len=1 off=0 Apr 26 09:30:07 192.168.122.209 [62758.164928] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 09:30:07 192.168.122.209 [62758.577825] [tdb] Close table 'client0.tdb' Apr 26 09:30:08 192.168.122.209 [62758.778905] [tdb] Close table 'sessions0.tdb' Apr 26 09:30:11 192.168.122.209 [62762.054145] [tdb] Close table 'cache0.tdb' Apr 26 09:30:11 192.168.122.209 [62762.299310] [tdb] Close table 'filter0.tdb' Apr 26 09:30:11 192.168.122.209 [62762.299771] [tempesta fw] modules are stopped Apr 26 09:30:11 192.168.122.209 [62762.489341] [tempesta fw] exiting... Apr 26 09:30:12 192.168.122.209 [62762.596594] [tdb] Shutdown Tempesta DB Apr 26 09:30:12 192.168.122.209 [62762.810462] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_nctl_brange_response_negative Apr 26 09:30:12 192.168.122.209 [62762.827806] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_nctl_brange_response_positive Apr 26 09:30:13 192.168.122.209 [62763.918475] [tdb] Start Tempesta DB Apr 26 09:30:13 192.168.122.209 [62764.078690] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:30:14 192.168.122.209 [62765.444587] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62765.444587] Maybe that's fine, but it's worth checking the [62765.444587] config - if there is no relations between the [62765.444587] names, then host name confusion attack is possible. Apr 26 09:30:14 192.168.122.209 [62765.547473] [tempesta fw] Configuration processing is completed. Apr 26 09:30:15 192.168.122.209 [62765.611763] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:30:15 192.168.122.209 [62766.171496] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:30:15 192.168.122.209 [62766.209291] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:30:15 192.168.122.209 [62766.244931] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:30:15 192.168.122.209 [62766.287464] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:30:15 192.168.122.209 [62766.289179] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:30:15 192.168.122.209 [62766.331420] [tempesta fw] Tempesta FW is ready Apr 26 09:30:16 192.168.122.209 [62767.000731] [tdb] Close table 'client0.tdb' Apr 26 09:30:16 192.168.122.209 [62767.189446] [tdb] Close table 'sessions0.tdb' Apr 26 09:30:19 192.168.122.209 [62770.503634] [tdb] Close table 'cache0.tdb' Apr 26 09:30:20 192.168.122.209 [62770.739039] [tdb] Close table 'filter0.tdb' Apr 26 09:30:20 192.168.122.209 [62770.739479] [tempesta fw] modules are stopped Apr 26 09:30:20 192.168.122.209 [62770.985332] [tempesta fw] exiting... Apr 26 09:30:20 192.168.122.209 [62771.118434] [tdb] Shutdown Tempesta DB Apr 26 09:30:20 192.168.122.209 [62771.335300] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_nctl_brange_response_positive Apr 26 09:30:20 192.168.122.209 [62771.344995] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_qetoken_brange_disallow_equal Apr 26 09:30:21 192.168.122.209 [62772.461768] [tdb] Start Tempesta DB Apr 26 09:30:22 192.168.122.209 [62772.613621] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:30:23 192.168.122.209 [62774.032830] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62774.032830] Maybe that's fine, but it's worth checking the [62774.032830] config - if there is no relations between the [62774.032830] names, then host name confusion attack is possible. Apr 26 09:30:23 192.168.122.209 [62774.151597] [tempesta fw] Configuration processing is completed. Apr 26 09:30:23 192.168.122.209 [62774.204584] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:30:24 192.168.122.209 [62774.645977] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:30:24 192.168.122.209 [62774.675902] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:30:24 192.168.122.209 [62774.706108] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:30:24 192.168.122.209 [62774.755589] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:30:24 192.168.122.209 [62774.757292] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:30:24 192.168.122.209 [62774.795526] [tempesta fw] Tempesta FW is ready Apr 26 09:30:24 192.168.122.209 [62774.983678] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrCache_ControlV input=0x75('unknown=value'), len=13, off=0 Apr 26 09:30:24 192.168.122.209 [62775.402171] [tdb] Close table 'client0.tdb' Apr 26 09:30:25 192.168.122.209 [62775.609601] [tdb] Close table 'sessions0.tdb' Apr 26 09:30:28 192.168.122.209 [62778.847357] [tdb] Close table 'cache0.tdb' Apr 26 09:30:28 192.168.122.209 [62779.095639] [tdb] Close table 'filter0.tdb' Apr 26 09:30:28 192.168.122.209 [62779.096076] [tempesta fw] modules are stopped Apr 26 09:30:28 192.168.122.209 [62779.259647] [tempesta fw] exiting... Apr 26 09:30:28 192.168.122.209 [62779.374008] [tdb] Shutdown Tempesta DB Apr 26 09:30:29 192.168.122.209 [62779.596766] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_qetoken_brange_disallow_equal Apr 26 09:30:29 192.168.122.209 [62779.610244] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_qetoken_brange_negative Apr 26 09:30:30 192.168.122.209 [62780.628345] [tdb] Start Tempesta DB Apr 26 09:30:30 192.168.122.209 [62780.769720] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:30:31 192.168.122.209 [62782.205028] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62782.205028] Maybe that's fine, but it's worth checking the [62782.205028] config - if there is no relations between the [62782.205028] names, then host name confusion attack is possible. Apr 26 09:30:31 192.168.122.209 [62782.311714] [tempesta fw] Configuration processing is completed. Apr 26 09:30:31 192.168.122.209 [62782.385513] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:30:32 192.168.122.209 [62782.934791] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:30:32 192.168.122.209 [62782.977191] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:30:32 192.168.122.209 [62783.012047] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:30:32 192.168.122.209 [62783.055664] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:30:32 192.168.122.209 [62783.057391] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:30:32 192.168.122.209 [62783.111614] [tempesta fw] Tempesta FW is ready Apr 26 09:30:32 192.168.122.209 [62783.292994] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrCache_ControlV input=0x75('unkno%wn=value%'), len=15, off=0 Apr 26 09:30:33 192.168.122.209 [62783.736891] [tdb] Close table 'client0.tdb' Apr 26 09:30:33 192.168.122.209 [62783.921547] [tdb] Close table 'sessions0.tdb' Apr 26 09:30:36 192.168.122.209 [62787.224637] [tdb] Close table 'cache0.tdb' Apr 26 09:30:36 192.168.122.209 [62787.452962] [tdb] Close table 'filter0.tdb' Apr 26 09:30:36 192.168.122.209 [62787.453411] [tempesta fw] modules are stopped Apr 26 09:30:37 192.168.122.209 [62787.649949] [tempesta fw] exiting... Apr 26 09:30:37 192.168.122.209 [62787.771630] [tdb] Shutdown Tempesta DB Apr 26 09:30:37 192.168.122.209 [62787.993329] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_qetoken_brange_negative Apr 26 09:30:37 192.168.122.209 [62788.000863] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_qetoken_brange_positive Apr 26 09:30:38 192.168.122.209 [62789.079522] [tdb] Start Tempesta DB Apr 26 09:30:38 192.168.122.209 [62789.222807] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:30:39 192.168.122.209 [62790.581135] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62790.581135] Maybe that's fine, but it's worth checking the [62790.581135] config - if there is no relations between the [62790.581135] names, then host name confusion attack is possible. Apr 26 09:30:40 192.168.122.209 [62790.687845] [tempesta fw] Configuration processing is completed. Apr 26 09:30:40 192.168.122.209 [62790.745932] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:30:40 192.168.122.209 [62791.177541] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:30:40 192.168.122.209 [62791.204975] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:30:40 192.168.122.209 [62791.241292] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:30:40 192.168.122.209 [62791.283765] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:30:40 192.168.122.209 [62791.285472] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:30:40 192.168.122.209 [62791.327651] [tempesta fw] Tempesta FW is ready Apr 26 09:30:41 192.168.122.209 [62791.930234] [tdb] Close table 'client0.tdb' Apr 26 09:30:41 192.168.122.209 [62792.122497] [tdb] Close table 'sessions0.tdb' Apr 26 09:30:44 192.168.122.209 [62795.310531] [tdb] Close table 'cache0.tdb' Apr 26 09:30:44 192.168.122.209 [62795.522463] [tdb] Close table 'filter0.tdb' Apr 26 09:30:44 192.168.122.209 [62795.522892] [tempesta fw] modules are stopped Apr 26 09:30:45 192.168.122.209 [62795.713923] [tempesta fw] exiting... Apr 26 09:30:45 192.168.122.209 [62795.810985] [tdb] Shutdown Tempesta DB Apr 26 09:30:45 192.168.122.209 [62796.007442] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_qetoken_brange_positive Apr 26 09:30:45 192.168.122.209 [62796.036736] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_token_brange_negative Apr 26 09:30:46 192.168.122.209 [62797.116786] [tdb] Start Tempesta DB Apr 26 09:30:46 192.168.122.209 [62797.263008] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:30:48 192.168.122.209 [62798.640780] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62798.640780] Maybe that's fine, but it's worth checking the [62798.640780] config - if there is no relations between the [62798.640780] names, then host name confusion attack is possible. Apr 26 09:30:48 192.168.122.209 [62798.767894] [tempesta fw] Configuration processing is completed. Apr 26 09:30:48 192.168.122.209 [62798.825735] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:30:48 192.168.122.209 [62799.257297] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:30:48 192.168.122.209 [62799.285343] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:30:48 192.168.122.209 [62799.311496] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:30:48 192.168.122.209 [62799.351870] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:30:48 192.168.122.209 [62799.353559] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:30:48 192.168.122.209 [62799.395819] [tempesta fw] Tempesta FW is ready Apr 26 09:30:48 192.168.122.209 [62799.578664] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrCookieV input=0x75('unknown%=value'), len=14, off=0 Apr 26 09:30:49 192.168.122.209 [62800.012797] [tdb] Close table 'client0.tdb' Apr 26 09:30:49 192.168.122.209 [62800.200598] [tdb] Close table 'sessions0.tdb' Apr 26 09:30:52 192.168.122.209 [62803.379954] [tdb] Close table 'cache0.tdb' Apr 26 09:30:53 192.168.122.209 [62803.623172] [tdb] Close table 'filter0.tdb' Apr 26 09:30:53 192.168.122.209 [62803.623614] [tempesta fw] modules are stopped Apr 26 09:30:53 192.168.122.209 [62803.818136] [tempesta fw] exiting... Apr 26 09:30:53 192.168.122.209 [62803.933952] [tdb] Shutdown Tempesta DB Apr 26 09:30:53 192.168.122.209 [62804.129177] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_token_brange_negative Apr 26 09:30:53 192.168.122.209 [62804.150748] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_token_brange_positive Apr 26 09:30:54 192.168.122.209 [62805.162723] [tdb] Start Tempesta DB Apr 26 09:30:54 192.168.122.209 [62805.297350] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:30:56 192.168.122.209 [62806.677239] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62806.677239] Maybe that's fine, but it's worth checking the [62806.677239] config - if there is no relations between the [62806.677239] names, then host name confusion attack is possible. Apr 26 09:30:56 192.168.122.209 [62806.792010] [tempesta fw] Configuration processing is completed. Apr 26 09:30:56 192.168.122.209 [62806.849188] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:30:56 192.168.122.209 [62807.306725] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:30:56 192.168.122.209 [62807.336070] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:30:56 192.168.122.209 [62807.366315] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:30:56 192.168.122.209 [62807.399987] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:30:56 192.168.122.209 [62807.401698] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:30:56 192.168.122.209 [62807.447966] [tempesta fw] Tempesta FW is ready Apr 26 09:30:57 192.168.122.209 [62808.113996] [tdb] Close table 'client0.tdb' Apr 26 09:30:57 192.168.122.209 [62808.307883] [tdb] Close table 'sessions0.tdb' Apr 26 09:31:00 192.168.122.209 [62811.537230] [tdb] Close table 'cache0.tdb' Apr 26 09:31:01 192.168.122.209 [62811.764490] [tdb] Close table 'filter0.tdb' Apr 26 09:31:01 192.168.122.209 [62811.764883] [tempesta fw] modules are stopped Apr 26 09:31:01 192.168.122.209 [62811.941082] [tempesta fw] exiting... Apr 26 09:31:01 192.168.122.209 [62812.061810] [tdb] Shutdown Tempesta DB Apr 26 09:31:01 192.168.122.209 [62812.288187] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_token_brange_positive Apr 26 09:31:01 192.168.122.209 [62812.298036] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_uri_brange_blocked_percent Apr 26 09:31:02 192.168.122.209 [62813.350810] [tdb] Start Tempesta DB Apr 26 09:31:02 192.168.122.209 [62813.497652] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:31:04 192.168.122.209 [62814.885374] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62814.885374] Maybe that's fine, but it's worth checking the [62814.885374] config - if there is no relations between the [62814.885374] names, then host name confusion attack is possible. Apr 26 09:31:04 192.168.122.209 [62814.984113] [tempesta fw] Configuration processing is completed. Apr 26 09:31:04 192.168.122.209 [62815.042072] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:31:04 192.168.122.209 [62815.471106] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:31:04 192.168.122.209 [62815.497534] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:31:04 192.168.122.209 [62815.523676] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:31:04 192.168.122.209 [62815.576092] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:31:04 192.168.122.209 [62815.577818] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:31:05 192.168.122.209 [62815.623987] [tempesta fw] Tempesta FW is ready Apr 26 09:31:05 192.168.122.209 [62815.806327] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrPsPathV input=0x6a('js%a'), len=4, off=0 Apr 26 09:31:05 192.168.122.209 [62816.225079] [tdb] Close table 'client0.tdb' Apr 26 09:31:05 192.168.122.209 [62816.411124] [tdb] Close table 'sessions0.tdb' Apr 26 09:31:09 192.168.122.209 [62819.608396] [tdb] Close table 'cache0.tdb' Apr 26 09:31:09 192.168.122.209 [62819.849700] [tdb] Close table 'filter0.tdb' Apr 26 09:31:09 192.168.122.209 [62819.850128] [tempesta fw] modules are stopped Apr 26 09:31:09 192.168.122.209 [62820.036731] [tempesta fw] exiting... Apr 26 09:31:09 192.168.122.209 [62820.169295] [tdb] Shutdown Tempesta DB Apr 26 09:31:09 192.168.122.209 [62820.361271] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_uri_brange_blocked_percent Apr 26 09:31:09 192.168.122.209 [62820.376300] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_uri_brange_issue_2030 Apr 26 09:31:10 192.168.122.209 [62821.397857] [tdb] Start Tempesta DB Apr 26 09:31:10 192.168.122.209 [62821.525987] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:31:12 192.168.122.209 [62822.861449] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62822.861449] Maybe that's fine, but it's worth checking the [62822.861449] config - if there is no relations between the [62822.861449] names, then host name confusion attack is possible. Apr 26 09:31:12 192.168.122.209 [62822.972247] [tempesta fw] Configuration processing is completed. Apr 26 09:31:12 192.168.122.209 [62823.029840] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:31:12 192.168.122.209 [62823.466223] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:31:12 192.168.122.209 [62823.494726] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:31:12 192.168.122.209 [62823.521311] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:31:12 192.168.122.209 [62823.564182] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:31:12 192.168.122.209 [62823.565871] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:31:13 192.168.122.209 [62823.612128] [tempesta fw] Tempesta FW is ready Apr 26 09:31:13 192.168.122.209 [62824.228210] [tdb] Close table 'client0.tdb' Apr 26 09:31:13 192.168.122.209 [62824.441628] [tdb] Close table 'sessions0.tdb' Apr 26 09:31:17 192.168.122.209 [62827.684804] [tdb] Close table 'cache0.tdb' Apr 26 09:31:17 192.168.122.209 [62827.903689] [tdb] Close table 'filter0.tdb' Apr 26 09:31:17 192.168.122.209 [62827.904159] [tempesta fw] modules are stopped Apr 26 09:31:17 192.168.122.209 [62828.081326] [tempesta fw] exiting... Apr 26 09:31:17 192.168.122.209 [62828.227554] [tdb] Shutdown Tempesta DB Apr 26 09:31:17 192.168.122.209 [62828.442464] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_uri_brange_issue_2030 Apr 26 09:31:17 192.168.122.209 [62828.457888] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_uri_brange_not_blocked_percent Apr 26 09:31:18 192.168.122.209 [62829.504933] [tdb] Start Tempesta DB Apr 26 09:31:19 192.168.122.209 [62829.637615] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:31:20 192.168.122.209 [62831.041335] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62831.041335] Maybe that's fine, but it's worth checking the [62831.041335] config - if there is no relations between the [62831.041335] names, then host name confusion attack is possible. Apr 26 09:31:20 192.168.122.209 [62831.144308] [tempesta fw] Configuration processing is completed. Apr 26 09:31:20 192.168.122.209 [62831.197160] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:31:21 192.168.122.209 [62831.610359] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:31:21 192.168.122.209 [62831.637207] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:31:21 192.168.122.209 [62831.665444] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:31:21 192.168.122.209 [62831.708280] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:31:21 192.168.122.209 [62831.709965] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:31:21 192.168.122.209 [62831.748267] [tempesta fw] Tempesta FW is ready Apr 26 09:31:21 192.168.122.209 [62832.394690] [tdb] Close table 'client0.tdb' Apr 26 09:31:21 192.168.122.209 [62832.585534] [tdb] Close table 'sessions0.tdb' Apr 26 09:31:25 192.168.122.209 [62835.785293] [tdb] Close table 'cache0.tdb' Apr 26 09:31:25 192.168.122.209 [62836.031010] [tdb] Close table 'filter0.tdb' Apr 26 09:31:25 192.168.122.209 [62836.031409] [tempesta fw] modules are stopped Apr 26 09:31:25 192.168.122.209 [62836.217369] [tempesta fw] exiting... Apr 26 09:31:25 192.168.122.209 [62836.319593] [tdb] Shutdown Tempesta DB Apr 26 09:31:25 192.168.122.209 [62836.540775] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_uri_brange_not_blocked_percent Apr 26 09:31:25 192.168.122.209 [62836.551838] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_uri_brange_referer_header_allowed_character Apr 26 09:31:26 192.168.122.209 [62837.522794] [tdb] Start Tempesta DB Apr 26 09:31:27 192.168.122.209 [62837.648861] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:31:28 192.168.122.209 [62839.097670] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62839.097670] Maybe that's fine, but it's worth checking the [62839.097670] config - if there is no relations between the [62839.097670] names, then host name confusion attack is possible. Apr 26 09:31:28 192.168.122.209 [62839.192439] [tempesta fw] Configuration processing is completed. Apr 26 09:31:28 192.168.122.209 [62839.247154] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:31:29 192.168.122.209 [62839.664603] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:31:29 192.168.122.209 [62839.691533] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:31:29 192.168.122.209 [62839.718623] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:31:29 192.168.122.209 [62839.760302] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:31:29 192.168.122.209 [62839.761033] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:31:29 192.168.122.209 [62839.800346] [tempesta fw] Tempesta FW is ready Apr 26 09:31:29 192.168.122.209 [62840.378498] [tdb] Close table 'client0.tdb' Apr 26 09:31:29 192.168.122.209 [62840.561918] [tdb] Close table 'sessions0.tdb' Apr 26 09:31:33 192.168.122.209 [62843.745564] [tdb] Close table 'cache0.tdb' Apr 26 09:31:33 192.168.122.209 [62843.992996] [tdb] Close table 'filter0.tdb' Apr 26 09:31:33 192.168.122.209 [62843.993422] [tempesta fw] modules are stopped Apr 26 09:31:33 192.168.122.209 [62844.200624] [tempesta fw] exiting... Apr 26 09:31:33 192.168.122.209 [62844.351665] [tdb] Shutdown Tempesta DB Apr 26 09:31:33 192.168.122.209 [62844.554095] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_uri_brange_referer_header_allowed_character Apr 26 09:31:33 192.168.122.209 [62844.566513] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_uri_brange_referer_header_disallowed_character Apr 26 09:31:35 192.168.122.209 [62845.603965] [tdb] Start Tempesta DB Apr 26 09:31:35 192.168.122.209 [62845.751267] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:31:36 192.168.122.209 [62847.133890] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62847.133890] Maybe that's fine, but it's worth checking the [62847.133890] config - if there is no relations between the [62847.133890] names, then host name confusion attack is possible. Apr 26 09:31:36 192.168.122.209 [62847.232832] [tempesta fw] Configuration processing is completed. Apr 26 09:31:36 192.168.122.209 [62847.290323] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:31:37 192.168.122.209 [62847.714206] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:31:37 192.168.122.209 [62847.740873] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:31:37 192.168.122.209 [62847.768957] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:31:37 192.168.122.209 [62847.820500] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:31:37 192.168.122.209 [62847.822220] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:31:37 192.168.122.209 [62847.864443] [tempesta fw] Tempesta FW is ready Apr 26 09:31:37 192.168.122.209 [62848.052613] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrRefererV input=0x2f('/example+'), len=9, off=0 Apr 26 09:31:37 192.168.122.209 [62848.480081] [tdb] Close table 'client0.tdb' Apr 26 09:31:38 192.168.122.209 [62848.670053] [tdb] Close table 'sessions0.tdb' Apr 26 09:31:41 192.168.122.209 [62851.862084] [tdb] Close table 'cache0.tdb' Apr 26 09:31:41 192.168.122.209 [62852.104914] [tdb] Close table 'filter0.tdb' Apr 26 09:31:41 192.168.122.209 [62852.105342] [tempesta fw] modules are stopped Apr 26 09:31:41 192.168.122.209 [62852.309262] [tempesta fw] exiting... Apr 26 09:31:41 192.168.122.209 [62852.446713] [tdb] Shutdown Tempesta DB Apr 26 09:31:42 192.168.122.209 [62852.636013] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_uri_brange_referer_header_disallowed_character Apr 26 09:31:42 192.168.122.209 [62852.649839] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_xff_brange_allow_ipv4 Apr 26 09:31:43 192.168.122.209 [62853.748459] [tdb] Start Tempesta DB Apr 26 09:31:43 192.168.122.209 [62853.874115] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:31:44 192.168.122.209 [62855.205843] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62855.205843] Maybe that's fine, but it's worth checking the [62855.205843] config - if there is no relations between the [62855.205843] names, then host name confusion attack is possible. Apr 26 09:31:44 192.168.122.209 [62855.308600] [tempesta fw] Configuration processing is completed. Apr 26 09:31:44 192.168.122.209 [62855.359749] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:31:45 192.168.122.209 [62855.775908] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:31:45 192.168.122.209 [62855.802350] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:31:45 192.168.122.209 [62855.829660] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:31:45 192.168.122.209 [62855.876592] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:31:45 192.168.122.209 [62855.878259] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:31:45 192.168.122.209 [62855.932627] [tempesta fw] Tempesta FW is ready Apr 26 09:31:45 192.168.122.209 [62856.555245] [tdb] Close table 'client0.tdb' Apr 26 09:31:46 192.168.122.209 [62856.742180] [tdb] Close table 'sessions0.tdb' Apr 26 09:31:49 192.168.122.209 [62859.966158] [tdb] Close table 'cache0.tdb' Apr 26 09:31:49 192.168.122.209 [62860.175157] [tdb] Close table 'filter0.tdb' Apr 26 09:31:49 192.168.122.209 [62860.175568] [tempesta fw] modules are stopped Apr 26 09:31:49 192.168.122.209 [62860.381126] [tempesta fw] exiting... Apr 26 09:31:49 192.168.122.209 [62860.514872] [tdb] Shutdown Tempesta DB Apr 26 09:31:50 192.168.122.209 [62860.704929] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_xff_brange_allow_ipv4 Apr 26 09:31:50 192.168.122.209 [62860.714388] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_xff_brange_allow_ipv6 Apr 26 09:31:51 192.168.122.209 [62861.760740] [tdb] Start Tempesta DB Apr 26 09:31:51 192.168.122.209 [62861.889580] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:31:52 192.168.122.209 [62863.293967] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62863.293967] Maybe that's fine, but it's worth checking the [62863.293967] config - if there is no relations between the [62863.293967] names, then host name confusion attack is possible. Apr 26 09:31:52 192.168.122.209 [62863.396712] [tempesta fw] Configuration processing is completed. Apr 26 09:31:52 192.168.122.209 [62863.448446] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:31:53 192.168.122.209 [62863.871995] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:31:53 192.168.122.209 [62863.898378] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:31:53 192.168.122.209 [62863.924821] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:31:53 192.168.122.209 [62863.972706] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:31:53 192.168.122.209 [62863.974378] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:31:53 192.168.122.209 [62864.012653] [tempesta fw] Tempesta FW is ready Apr 26 09:31:54 192.168.122.209 [62864.646783] [tdb] Close table 'client0.tdb' Apr 26 09:31:54 192.168.122.209 [62864.824854] [tdb] Close table 'sessions0.tdb' Apr 26 09:31:57 192.168.122.209 [62868.054968] [tdb] Close table 'cache0.tdb' Apr 26 09:31:57 192.168.122.209 [62868.267494] [tdb] Close table 'filter0.tdb' Apr 26 09:31:57 192.168.122.209 [62868.267921] [tempesta fw] modules are stopped Apr 26 09:31:57 192.168.122.209 [62868.468361] [tempesta fw] exiting... Apr 26 09:31:58 192.168.122.209 [62868.606651] [tdb] Shutdown Tempesta DB Apr 26 09:31:58 192.168.122.209 [62868.803964] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_xff_brange_allow_ipv6 Apr 26 09:31:58 192.168.122.209 [62868.820814] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_xff_brange_allow_many_ip Apr 26 09:31:59 192.168.122.209 [62869.868686] [tdb] Start Tempesta DB Apr 26 09:31:59 192.168.122.209 [62870.006337] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:32:00 192.168.122.209 [62871.374080] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62871.374080] Maybe that's fine, but it's worth checking the [62871.374080] config - if there is no relations between the [62871.374080] names, then host name confusion attack is possible. Apr 26 09:32:00 192.168.122.209 [62871.468853] [tempesta fw] Configuration processing is completed. Apr 26 09:32:00 192.168.122.209 [62871.529825] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:32:01 192.168.122.209 [62871.962811] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:32:01 192.168.122.209 [62871.989678] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:32:01 192.168.122.209 [62872.015929] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:32:01 192.168.122.209 [62872.064793] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:32:01 192.168.122.209 [62872.066476] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:32:01 192.168.122.209 [62872.104759] [tempesta fw] Tempesta FW is ready Apr 26 09:32:02 192.168.122.209 [62872.724914] [tdb] Close table 'client0.tdb' Apr 26 09:32:02 192.168.122.209 [62872.935785] [tdb] Close table 'sessions0.tdb' Apr 26 09:32:05 192.168.122.209 [62876.116557] [tdb] Close table 'cache0.tdb' Apr 26 09:32:05 192.168.122.209 [62876.348837] [tdb] Close table 'filter0.tdb' Apr 26 09:32:05 192.168.122.209 [62876.349282] [tempesta fw] modules are stopped Apr 26 09:32:05 192.168.122.209 [62876.558257] [tempesta fw] exiting... Apr 26 09:32:06 192.168.122.209 [62876.692583] [tdb] Shutdown Tempesta DB Apr 26 09:32:06 192.168.122.209 [62876.907512] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_xff_brange_allow_many_ip Apr 26 09:32:06 192.168.122.209 [62876.923092] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_xff_brange_disallow_ipv4 Apr 26 09:32:07 192.168.122.209 [62877.915203] [tdb] Start Tempesta DB Apr 26 09:32:07 192.168.122.209 [62878.045484] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:32:08 192.168.122.209 [62879.430191] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62879.430191] Maybe that's fine, but it's worth checking the [62879.430191] config - if there is no relations between the [62879.430191] names, then host name confusion attack is possible. Apr 26 09:32:08 192.168.122.209 [62879.532921] [tempesta fw] Configuration processing is completed. Apr 26 09:32:08 192.168.122.209 [62879.586000] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:32:09 192.168.122.209 [62880.007994] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:32:09 192.168.122.209 [62880.034509] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:32:09 192.168.122.209 [62880.062449] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:32:09 192.168.122.209 [62880.108899] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:32:09 192.168.122.209 [62880.110601] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:32:09 192.168.122.209 [62880.156884] [tempesta fw] Tempesta FW is ready Apr 26 09:32:09 192.168.122.209 [62880.364525] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrX_Forwarded_ForV input=0x35('5.10.50.6'), len=9, off=0 Apr 26 09:32:10 192.168.122.209 [62880.794835] [tdb] Close table 'client0.tdb' Apr 26 09:32:10 192.168.122.209 [62880.986280] [tdb] Close table 'sessions0.tdb' Apr 26 09:32:13 192.168.122.209 [62884.173006] [tdb] Close table 'cache0.tdb' Apr 26 09:32:13 192.168.122.209 [62884.404556] [tdb] Close table 'filter0.tdb' Apr 26 09:32:13 192.168.122.209 [62884.404970] [tempesta fw] modules are stopped Apr 26 09:32:14 192.168.122.209 [62884.604807] [tempesta fw] exiting... Apr 26 09:32:14 192.168.122.209 [62884.729702] [tdb] Shutdown Tempesta DB Apr 26 09:32:14 192.168.122.209 [62884.958595] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_xff_brange_disallow_ipv4 Apr 26 09:32:14 192.168.122.209 [62884.984468] Start test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_xff_brange_disallow_ipv6 Apr 26 09:32:15 192.168.122.209 [62885.930646] [tdb] Start Tempesta DB Apr 26 09:32:15 192.168.122.209 [62886.047949] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:32:16 192.168.122.209 [62887.434255] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62887.434255] Maybe that's fine, but it's worth checking the [62887.434255] config - if there is no relations between the [62887.434255] names, then host name confusion attack is possible. Apr 26 09:32:16 192.168.122.209 [62887.537021] [tempesta fw] Configuration processing is completed. Apr 26 09:32:16 192.168.122.209 [62887.588426] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:32:17 192.168.122.209 [62888.001112] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:32:17 192.168.122.209 [62888.027685] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:32:17 192.168.122.209 [62888.054230] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:32:17 192.168.122.209 [62888.109510] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:32:17 192.168.122.209 [62888.111187] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:32:17 192.168.122.209 [62888.152950] [tempesta fw] Tempesta FW is ready Apr 26 09:32:17 192.168.122.209 [62888.351263] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrX_Forwarded_ForV input=0x32('2001:db8:85a3:8d'), len=36, off=0 Apr 26 09:32:18 192.168.122.209 [62888.787077] [tdb] Close table 'client0.tdb' Apr 26 09:32:18 192.168.122.209 [62888.975418] [tdb] Close table 'sessions0.tdb' Apr 26 09:32:21 192.168.122.209 [62892.147627] [tdb] Close table 'cache0.tdb' Apr 26 09:32:21 192.168.122.209 [62892.376330] [tdb] Close table 'filter0.tdb' Apr 26 09:32:21 192.168.122.209 [62892.376763] [tempesta fw] modules are stopped Apr 26 09:32:21 192.168.122.209 [62892.557444] [tempesta fw] exiting... Apr 26 09:32:22 192.168.122.209 [62892.722403] [tdb] Shutdown Tempesta DB Apr 26 09:32:22 192.168.122.209 [62892.923372] End test: t_custom_branges.test_http_brange.TestBrangeH2.test_http_xff_brange_disallow_ipv6 Apr 26 09:32:22 192.168.122.209 [62892.937211] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_boundary_values_0x40_from_0x41_to_0x7e Apr 26 09:32:23 192.168.122.209 [62893.959382] [tdb] Start Tempesta DB Apr 26 09:32:23 192.168.122.209 [62894.088455] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:32:24 192.168.122.209 [62895.482430] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62895.482430] Maybe that's fine, but it's worth checking the [62895.482430] config - if there is no relations between the [62895.482430] names, then host name confusion attack is possible. Apr 26 09:32:24 192.168.122.209 [62895.585215] [tempesta fw] Configuration processing is completed. Apr 26 09:32:25 192.168.122.209 [62895.643187] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:32:25 192.168.122.209 [62896.067870] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:32:25 192.168.122.209 [62896.094442] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:32:25 192.168.122.209 [62896.121164] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:32:25 192.168.122.209 [62896.185123] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:32:25 192.168.122.209 [62896.186832] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:32:25 192.168.122.209 [62896.229060] [tempesta fw] Tempesta FW is ready Apr 26 09:32:25 192.168.122.209 [62896.371740] [tempesta fw] Warning: Parser error: state=Req_UriAbsPath input(-0)=0x40('@') data_len=1 off=0 Apr 26 09:32:26 192.168.122.209 [62896.798836] [tdb] Close table 'client0.tdb' Apr 26 09:32:26 192.168.122.209 [62896.985845] [tdb] Close table 'sessions0.tdb' Apr 26 09:32:29 192.168.122.209 [62900.191439] [tdb] Close table 'cache0.tdb' Apr 26 09:32:29 192.168.122.209 [62900.437221] [tdb] Close table 'filter0.tdb' Apr 26 09:32:29 192.168.122.209 [62900.437651] [tempesta fw] modules are stopped Apr 26 09:32:30 192.168.122.209 [62900.609206] [tempesta fw] exiting... Apr 26 09:32:30 192.168.122.209 [62900.753890] [tdb] Shutdown Tempesta DB Apr 26 09:32:30 192.168.122.209 [62900.976341] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_boundary_values_0x40_from_0x41_to_0x7e Apr 26 09:32:30 192.168.122.209 [62900.990568] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_boundary_values_0x41_from_0x41_to_0x7e Apr 26 09:32:31 192.168.122.209 [62902.002170] [tdb] Start Tempesta DB Apr 26 09:32:31 192.168.122.209 [62902.141949] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:32:32 192.168.122.209 [62903.522446] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62903.522446] Maybe that's fine, but it's worth checking the [62903.522446] config - if there is no relations between the [62903.522446] names, then host name confusion attack is possible. Apr 26 09:32:33 192.168.122.209 [62903.625553] [tempesta fw] Configuration processing is completed. Apr 26 09:32:33 192.168.122.209 [62903.677519] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:32:33 192.168.122.209 [62904.105824] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:32:33 192.168.122.209 [62904.132658] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:32:33 192.168.122.209 [62904.159109] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:32:33 192.168.122.209 [62904.205215] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:32:33 192.168.122.209 [62904.207098] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:32:33 192.168.122.209 [62904.277166] [tempesta fw] Tempesta FW is ready Apr 26 09:32:34 192.168.122.209 [62904.816739] [tdb] Close table 'client0.tdb' Apr 26 09:32:34 192.168.122.209 [62904.998669] [tdb] Close table 'sessions0.tdb' Apr 26 09:32:37 192.168.122.209 [62908.193103] [tdb] Close table 'cache0.tdb' Apr 26 09:32:37 192.168.122.209 [62908.435250] [tdb] Close table 'filter0.tdb' Apr 26 09:32:37 192.168.122.209 [62908.435665] [tempesta fw] modules are stopped Apr 26 09:32:38 192.168.122.209 [62908.618565] [tempesta fw] exiting... Apr 26 09:32:38 192.168.122.209 [62908.744137] [tdb] Shutdown Tempesta DB Apr 26 09:32:38 192.168.122.209 [62908.958601] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_boundary_values_0x41_from_0x41_to_0x7e Apr 26 09:32:38 192.168.122.209 [62908.977055] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_boundary_values_0x7e_from_0x41_to_0x7e Apr 26 09:32:39 192.168.122.209 [62909.947390] [tdb] Start Tempesta DB Apr 26 09:32:39 192.168.122.209 [62910.086872] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:32:40 192.168.122.209 [62911.514564] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62911.514564] Maybe that's fine, but it's worth checking the [62911.514564] config - if there is no relations between the [62911.514564] names, then host name confusion attack is possible. Apr 26 09:32:41 192.168.122.209 [62911.617347] [tempesta fw] Configuration processing is completed. Apr 26 09:32:41 192.168.122.209 [62911.668088] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:32:41 192.168.122.209 [62912.093992] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:32:41 192.168.122.209 [62912.131866] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:32:41 192.168.122.209 [62912.159165] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:32:41 192.168.122.209 [62912.205308] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:32:41 192.168.122.209 [62912.207001] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:32:41 192.168.122.209 [62912.249257] [tempesta fw] Tempesta FW is ready Apr 26 09:32:42 192.168.122.209 [62912.813616] [tdb] Close table 'client0.tdb' Apr 26 09:32:42 192.168.122.209 [62913.002032] [tdb] Close table 'sessions0.tdb' Apr 26 09:32:45 192.168.122.209 [62916.205672] [tdb] Close table 'cache0.tdb' Apr 26 09:32:45 192.168.122.209 [62916.450709] [tdb] Close table 'filter0.tdb' Apr 26 09:32:45 192.168.122.209 [62916.451141] [tempesta fw] modules are stopped Apr 26 09:32:46 192.168.122.209 [62916.658651] [tempesta fw] exiting... Apr 26 09:32:46 192.168.122.209 [62916.767361] [tdb] Shutdown Tempesta DB Apr 26 09:32:46 192.168.122.209 [62916.961714] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_boundary_values_0x7e_from_0x41_to_0x7e Apr 26 09:32:46 192.168.122.209 [62916.988512] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_boundary_values_0x7f_from_0x41_to_0x7e Apr 26 09:32:47 192.168.122.209 [62918.073551] [tdb] Start Tempesta DB Apr 26 09:32:47 192.168.122.209 [62918.200388] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:32:49 192.168.122.209 [62919.630703] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62919.630703] Maybe that's fine, but it's worth checking the [62919.630703] config - if there is no relations between the [62919.630703] names, then host name confusion attack is possible. Apr 26 09:32:49 192.168.122.209 [62919.745447] [tempesta fw] Configuration processing is completed. Apr 26 09:32:49 192.168.122.209 [62919.805019] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:32:49 192.168.122.209 [62920.237786] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:32:49 192.168.122.209 [62920.263394] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:32:49 192.168.122.209 [62920.288835] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:32:49 192.168.122.209 [62920.333407] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:32:49 192.168.122.209 [62920.335107] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:32:49 192.168.122.209 [62920.381356] [tempesta fw] Tempesta FW is ready Apr 26 09:32:49 192.168.122.209 [62920.517609] [tempesta fw] Warning: Parser error: state=Req_UriAbsPath input(-0)=0x7f('') data_len=1 off=0 Apr 26 09:32:50 192.168.122.209 [62920.940534] [tdb] Close table 'client0.tdb' Apr 26 09:32:50 192.168.122.209 [62921.119362] [tdb] Close table 'sessions0.tdb' Apr 26 09:32:53 192.168.122.209 [62924.261772] [tdb] Close table 'cache0.tdb' Apr 26 09:32:53 192.168.122.209 [62924.488300] [tdb] Close table 'filter0.tdb' Apr 26 09:32:53 192.168.122.209 [62924.488730] [tempesta fw] modules are stopped Apr 26 09:32:54 192.168.122.209 [62924.689735] [tempesta fw] exiting... Apr 26 09:32:54 192.168.122.209 [62924.808462] [tdb] Shutdown Tempesta DB Apr 26 09:32:54 192.168.122.209 [62925.025137] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_boundary_values_0x7f_from_0x41_to_0x7e Apr 26 09:32:54 192.168.122.209 [62925.040709] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_boundary_values_disallowed_0x5f Apr 26 09:32:55 192.168.122.209 [62926.103314] [tdb] Start Tempesta DB Apr 26 09:32:55 192.168.122.209 [62926.240951] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:32:56 192.168.122.209 [62927.586822] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62927.586822] Maybe that's fine, but it's worth checking the [62927.586822] config - if there is no relations between the [62927.586822] names, then host name confusion attack is possible. Apr 26 09:32:57 192.168.122.209 [62927.689567] [tempesta fw] Configuration processing is completed. Apr 26 09:32:57 192.168.122.209 [62927.743824] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:32:57 192.168.122.209 [62928.167179] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:32:57 192.168.122.209 [62928.193029] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:32:57 192.168.122.209 [62928.219556] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:32:57 192.168.122.209 [62928.317544] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:32:57 192.168.122.209 [62928.319245] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:32:57 192.168.122.209 [62928.361462] [tempesta fw] Tempesta FW is ready Apr 26 09:32:57 192.168.122.209 [62928.505578] [tempesta fw] Warning: Parser error: state=Req_UriAbsPath input(-0)=0x5f('_') data_len=1 off=0 Apr 26 09:32:58 192.168.122.209 [62928.908906] [tdb] Close table 'client0.tdb' Apr 26 09:32:58 192.168.122.209 [62929.114057] [tdb] Close table 'sessions0.tdb' Apr 26 09:33:01 192.168.122.209 [62932.298876] [tdb] Close table 'cache0.tdb' Apr 26 09:33:01 192.168.122.209 [62932.512407] [tdb] Close table 'filter0.tdb' Apr 26 09:33:01 192.168.122.209 [62932.512822] [tempesta fw] modules are stopped Apr 26 09:33:02 192.168.122.209 [62932.694627] [tempesta fw] exiting... Apr 26 09:33:02 192.168.122.209 [62932.777665] [tdb] Shutdown Tempesta DB Apr 26 09:33:02 192.168.122.209 [62932.987552] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_boundary_values_disallowed_0x5f Apr 26 09:33:02 192.168.122.209 [62933.001192] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_cookie_brange_allow_many_cookie Apr 26 09:33:03 192.168.122.209 [62934.100240] [tdb] Start Tempesta DB Apr 26 09:33:03 192.168.122.209 [62934.232803] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:33:04 192.168.122.209 [62935.518862] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62935.518862] Maybe that's fine, but it's worth checking the [62935.518862] config - if there is no relations between the [62935.518862] names, then host name confusion attack is possible. Apr 26 09:33:05 192.168.122.209 [62935.613720] [tempesta fw] Configuration processing is completed. Apr 26 09:33:05 192.168.122.209 [62935.664695] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:33:05 192.168.122.209 [62936.085335] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:33:05 192.168.122.209 [62936.111492] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:33:05 192.168.122.209 [62936.146240] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:33:05 192.168.122.209 [62936.193611] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:33:05 192.168.122.209 [62936.195294] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:33:05 192.168.122.209 [62936.253572] [tempesta fw] Tempesta FW is ready Apr 26 09:33:06 192.168.122.209 [62936.766517] [tdb] Close table 'client0.tdb' Apr 26 09:33:06 192.168.122.209 [62936.981823] [tdb] Close table 'sessions0.tdb' Apr 26 09:33:09 192.168.122.209 [62940.200515] [tdb] Close table 'cache0.tdb' Apr 26 09:33:09 192.168.122.209 [62940.452892] [tdb] Close table 'filter0.tdb' Apr 26 09:33:09 192.168.122.209 [62940.453318] [tempesta fw] modules are stopped Apr 26 09:33:10 192.168.122.209 [62940.631577] [tempesta fw] exiting... Apr 26 09:33:10 192.168.122.209 [62940.751959] [tdb] Shutdown Tempesta DB Apr 26 09:33:10 192.168.122.209 [62940.934097] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_cookie_brange_allow_many_cookie Apr 26 09:33:10 192.168.122.209 [62940.955874] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_cookie_brange_check_value Apr 26 09:33:11 192.168.122.209 [62942.004320] [tdb] Start Tempesta DB Apr 26 09:33:11 192.168.122.209 [62942.146528] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:33:12 192.168.122.209 [62943.514999] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62943.514999] Maybe that's fine, but it's worth checking the [62943.514999] config - if there is no relations between the [62943.514999] names, then host name confusion attack is possible. Apr 26 09:33:13 192.168.122.209 [62943.613769] [tempesta fw] Configuration processing is completed. Apr 26 09:33:13 192.168.122.209 [62943.671470] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:33:13 192.168.122.209 [62944.093842] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:33:13 192.168.122.209 [62944.120152] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:33:13 192.168.122.209 [62944.154834] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:33:13 192.168.122.209 [62944.193723] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:33:13 192.168.122.209 [62944.195433] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:33:13 192.168.122.209 [62944.233672] [tempesta fw] Tempesta FW is ready Apr 26 09:33:13 192.168.122.209 [62944.366255] [tempesta fw] Warning: Parser error: state=Req_HdrCookieV input(-0)=0x51('Q') data_len=1 off=0 Apr 26 09:33:14 192.168.122.209 [62944.797163] [tdb] Close table 'client0.tdb' Apr 26 09:33:14 192.168.122.209 [62944.984287] [tdb] Close table 'sessions0.tdb' Apr 26 09:33:17 192.168.122.209 [62948.165707] [tdb] Close table 'cache0.tdb' Apr 26 09:33:17 192.168.122.209 [62948.424232] [tdb] Close table 'filter0.tdb' Apr 26 09:33:17 192.168.122.209 [62948.424644] [tempesta fw] modules are stopped Apr 26 09:33:18 192.168.122.209 [62948.613917] [tempesta fw] exiting... Apr 26 09:33:18 192.168.122.209 [62948.765203] [tdb] Shutdown Tempesta DB Apr 26 09:33:18 192.168.122.209 [62948.963106] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_cookie_brange_check_value Apr 26 09:33:18 192.168.122.209 [62948.978025] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_cookie_brange_not_check_name Apr 26 09:33:19 192.168.122.209 [62950.025527] [tdb] Start Tempesta DB Apr 26 09:33:19 192.168.122.209 [62950.154245] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:33:21 192.168.122.209 [62951.611074] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62951.611074] Maybe that's fine, but it's worth checking the [62951.611074] config - if there is no relations between the [62951.611074] names, then host name confusion attack is possible. Apr 26 09:33:21 192.168.122.209 [62951.709901] [tempesta fw] Configuration processing is completed. Apr 26 09:33:21 192.168.122.209 [62951.764187] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:33:21 192.168.122.209 [62952.178043] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:33:21 192.168.122.209 [62952.204392] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:33:21 192.168.122.209 [62952.230721] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:33:21 192.168.122.209 [62952.301823] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:33:21 192.168.122.209 [62952.303557] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:33:21 192.168.122.209 [62952.341782] [tempesta fw] Tempesta FW is ready Apr 26 09:33:22 192.168.122.209 [62952.901488] [tdb] Close table 'client0.tdb' Apr 26 09:33:22 192.168.122.209 [62953.096888] [tdb] Close table 'sessions0.tdb' Apr 26 09:33:25 192.168.122.209 [62956.274740] [tdb] Close table 'cache0.tdb' Apr 26 09:33:25 192.168.122.209 [62956.556436] [tdb] Close table 'filter0.tdb' Apr 26 09:33:25 192.168.122.209 [62956.556873] [tempesta fw] modules are stopped Apr 26 09:33:26 192.168.122.209 [62956.772715] [tempesta fw] exiting... Apr 26 09:33:26 192.168.122.209 [62956.893925] [tdb] Shutdown Tempesta DB Apr 26 09:33:26 192.168.122.209 [62957.130308] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_cookie_brange_not_check_name Apr 26 09:33:26 192.168.122.209 [62957.140330] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_ctext_vchar_brange_allow Apr 26 09:33:27 192.168.122.209 [62958.129462] [tdb] Start Tempesta DB Apr 26 09:33:27 192.168.122.209 [62958.262009] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:33:29 192.168.122.209 [62959.715189] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62959.715189] Maybe that's fine, but it's worth checking the [62959.715189] config - if there is no relations between the [62959.715189] names, then host name confusion attack is possible. Apr 26 09:33:29 192.168.122.209 [62959.817970] [tempesta fw] Configuration processing is completed. Apr 26 09:33:29 192.168.122.209 [62959.869378] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:33:29 192.168.122.209 [62960.324302] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:33:29 192.168.122.209 [62960.352563] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:33:29 192.168.122.209 [62960.381141] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:33:29 192.168.122.209 [62960.441921] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:33:29 192.168.122.209 [62960.443673] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:33:29 192.168.122.209 [62960.485877] [tempesta fw] Tempesta FW is ready Apr 26 09:33:30 192.168.122.209 [62961.071507] [tdb] Close table 'client0.tdb' Apr 26 09:33:30 192.168.122.209 [62961.253341] [tdb] Close table 'sessions0.tdb' Apr 26 09:33:33 192.168.122.209 [62964.512400] [tdb] Close table 'cache0.tdb' Apr 26 09:33:34 192.168.122.209 [62964.730578] [tdb] Close table 'filter0.tdb' Apr 26 09:33:34 192.168.122.209 [62964.731006] [tempesta fw] modules are stopped Apr 26 09:33:34 192.168.122.209 [62964.935882] [tempesta fw] exiting... Apr 26 09:33:34 192.168.122.209 [62965.060398] [tdb] Shutdown Tempesta DB Apr 26 09:33:34 192.168.122.209 [62965.264067] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_ctext_vchar_brange_allow Apr 26 09:33:34 192.168.122.209 [62965.279480] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_ctext_vchar_brange_disallow Apr 26 09:33:35 192.168.122.209 [62966.319131] [tdb] Start Tempesta DB Apr 26 09:33:35 192.168.122.209 [62966.479808] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:33:37 192.168.122.209 [62967.815346] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62967.815346] Maybe that's fine, but it's worth checking the [62967.815346] config - if there is no relations between the [62967.815346] names, then host name confusion attack is possible. Apr 26 09:33:37 192.168.122.209 [62967.914074] [tempesta fw] Configuration processing is completed. Apr 26 09:33:37 192.168.122.209 [62967.974556] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:33:37 192.168.122.209 [62968.451530] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:33:37 192.168.122.209 [62968.482790] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:33:37 192.168.122.209 [62968.517245] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:33:37 192.168.122.209 [62968.565945] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:33:37 192.168.122.209 [62968.567963] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:33:38 192.168.122.209 [62968.625972] [tempesta fw] Tempesta FW is ready Apr 26 09:33:38 192.168.122.209 [62968.784906] [tempesta fw] Warning: Parser error: state=Req_HdrUser_AgentV input(-0)=0x25('%') data_len=1 off=0 Apr 26 09:33:38 192.168.122.209 [62969.185290] [tdb] Close table 'client0.tdb' Apr 26 09:33:38 192.168.122.209 [62969.369373] [tdb] Close table 'sessions0.tdb' Apr 26 09:33:42 192.168.122.209 [62972.759261] [tdb] Close table 'cache0.tdb' Apr 26 09:33:42 192.168.122.209 [62973.017456] [tdb] Close table 'filter0.tdb' Apr 26 09:33:42 192.168.122.209 [62973.017903] [tempesta fw] modules are stopped Apr 26 09:33:42 192.168.122.209 [62973.221720] [tempesta fw] exiting... Apr 26 09:33:42 192.168.122.209 [62973.370783] [tdb] Shutdown Tempesta DB Apr 26 09:33:42 192.168.122.209 [62973.569317] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_ctext_vchar_brange_disallow Apr 26 09:33:42 192.168.122.209 [62973.592985] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_etag_brange_if_none_match_allow Apr 26 09:33:43 192.168.122.209 [62974.540014] [tdb] Start Tempesta DB Apr 26 09:33:44 192.168.122.209 [62974.682669] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:33:45 192.168.122.209 [62976.087403] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62976.087403] Maybe that's fine, but it's worth checking the [62976.087403] config - if there is no relations between the [62976.087403] names, then host name confusion attack is possible. Apr 26 09:33:45 192.168.122.209 [62976.194165] [tempesta fw] Configuration processing is completed. Apr 26 09:33:45 192.168.122.209 [62976.249812] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:33:46 192.168.122.209 [62976.672968] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:33:46 192.168.122.209 [62976.698943] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:33:46 192.168.122.209 [62976.724697] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:33:46 192.168.122.209 [62976.766138] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:33:46 192.168.122.209 [62976.767895] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:33:46 192.168.122.209 [62976.810097] [tempesta fw] Tempesta FW is ready Apr 26 09:33:46 192.168.122.209 [62977.374510] [tdb] Close table 'client0.tdb' Apr 26 09:33:46 192.168.122.209 [62977.539746] [tdb] Close table 'sessions0.tdb' Apr 26 09:33:50 192.168.122.209 [62980.805230] [tdb] Close table 'cache0.tdb' Apr 26 09:33:50 192.168.122.209 [62981.056922] [tdb] Close table 'filter0.tdb' Apr 26 09:33:50 192.168.122.209 [62981.057347] [tempesta fw] modules are stopped Apr 26 09:33:50 192.168.122.209 [62981.252505] [tempesta fw] exiting... Apr 26 09:33:50 192.168.122.209 [62981.353830] [tdb] Shutdown Tempesta DB Apr 26 09:33:50 192.168.122.209 [62981.571068] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_etag_brange_if_none_match_allow Apr 26 09:33:50 192.168.122.209 [62981.585969] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_etag_brange_if_none_match_allow_all Apr 26 09:33:52 192.168.122.209 [62982.608376] [tdb] Start Tempesta DB Apr 26 09:33:52 192.168.122.209 [62982.745917] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:33:53 192.168.122.209 [62984.195793] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62984.195793] Maybe that's fine, but it's worth checking the [62984.195793] config - if there is no relations between the [62984.195793] names, then host name confusion attack is possible. Apr 26 09:33:53 192.168.122.209 [62984.294275] [tempesta fw] Configuration processing is completed. Apr 26 09:33:53 192.168.122.209 [62984.346063] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:33:54 192.168.122.209 [62984.782423] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:33:54 192.168.122.209 [62984.811222] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:33:54 192.168.122.209 [62984.839630] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:33:54 192.168.122.209 [62984.894275] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:33:54 192.168.122.209 [62984.896057] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:33:54 192.168.122.209 [62984.934193] [tempesta fw] Tempesta FW is ready Apr 26 09:33:54 192.168.122.209 [62985.529864] [tdb] Close table 'client0.tdb' Apr 26 09:33:55 192.168.122.209 [62985.698357] [tdb] Close table 'sessions0.tdb' Apr 26 09:33:58 192.168.122.209 [62988.943683] [tdb] Close table 'cache0.tdb' Apr 26 09:33:58 192.168.122.209 [62989.181252] [tdb] Close table 'filter0.tdb' Apr 26 09:33:58 192.168.122.209 [62989.181688] [tempesta fw] modules are stopped Apr 26 09:33:58 192.168.122.209 [62989.374881] [tempesta fw] exiting... Apr 26 09:33:58 192.168.122.209 [62989.498125] [tdb] Shutdown Tempesta DB Apr 26 09:33:59 192.168.122.209 [62989.702101] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_etag_brange_if_none_match_allow_all Apr 26 09:33:59 192.168.122.209 [62989.712435] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_etag_brange_if_none_match_allow_weak Apr 26 09:34:00 192.168.122.209 [62990.716553] [tdb] Start Tempesta DB Apr 26 09:34:00 192.168.122.209 [62990.850236] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:34:01 192.168.122.209 [62992.191684] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [62992.191684] Maybe that's fine, but it's worth checking the [62992.191684] config - if there is no relations between the [62992.191684] names, then host name confusion attack is possible. Apr 26 09:34:01 192.168.122.209 [62992.294417] [tempesta fw] Configuration processing is completed. Apr 26 09:34:01 192.168.122.209 [62992.353196] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:34:02 192.168.122.209 [62992.765261] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:34:02 192.168.122.209 [62992.801149] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:34:02 192.168.122.209 [62992.827172] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:34:02 192.168.122.209 [62992.874254] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:34:02 192.168.122.209 [62992.875996] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:34:02 192.168.122.209 [62992.914231] [tempesta fw] Tempesta FW is ready Apr 26 09:34:02 192.168.122.209 [62993.506551] [tdb] Close table 'client0.tdb' Apr 26 09:34:03 192.168.122.209 [62993.728619] [tdb] Close table 'sessions0.tdb' Apr 26 09:34:06 192.168.122.209 [62997.079056] [tdb] Close table 'cache0.tdb' Apr 26 09:34:06 192.168.122.209 [62997.341786] [tdb] Close table 'filter0.tdb' Apr 26 09:34:06 192.168.122.209 [62997.342213] [tempesta fw] modules are stopped Apr 26 09:34:06 192.168.122.209 [62997.571953] [tempesta fw] exiting... Apr 26 09:34:07 192.168.122.209 [62997.734529] [tdb] Shutdown Tempesta DB Apr 26 09:34:07 192.168.122.209 [62997.950674] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_etag_brange_if_none_match_allow_weak Apr 26 09:34:07 192.168.122.209 [62997.963185] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_etag_brange_if_none_match_disallow Apr 26 09:34:08 192.168.122.209 [62999.059445] [tdb] Start Tempesta DB Apr 26 09:34:08 192.168.122.209 [62999.196706] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:34:10 192.168.122.209 [63000.635874] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63000.635874] Maybe that's fine, but it's worth checking the [63000.635874] config - if there is no relations between the [63000.635874] names, then host name confusion attack is possible. Apr 26 09:34:10 192.168.122.209 [63000.738489] [tempesta fw] Configuration processing is completed. Apr 26 09:34:10 192.168.122.209 [63000.791053] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:34:10 192.168.122.209 [63001.244491] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:34:10 192.168.122.209 [63001.271852] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:34:10 192.168.122.209 [63001.299824] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:34:10 192.168.122.209 [63001.354442] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:34:10 192.168.122.209 [63001.356187] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:34:10 192.168.122.209 [63001.398389] [tempesta fw] Tempesta FW is ready Apr 26 09:34:10 192.168.122.209 [63001.532975] [tempesta fw] Warning: Parser error: state=Req_HdrIf_None_MatchV input(-0)=0x51('Q') data_len=1 off=0 Apr 26 09:34:11 192.168.122.209 [63001.957106] [tdb] Close table 'client0.tdb' Apr 26 09:34:11 192.168.122.209 [63002.157825] [tdb] Close table 'sessions0.tdb' Apr 26 09:34:14 192.168.122.209 [63005.381589] [tdb] Close table 'cache0.tdb' Apr 26 09:34:15 192.168.122.209 [63005.619072] [tdb] Close table 'filter0.tdb' Apr 26 09:34:15 192.168.122.209 [63005.619507] [tempesta fw] modules are stopped Apr 26 09:34:15 192.168.122.209 [63005.824057] [tempesta fw] exiting... Apr 26 09:34:15 192.168.122.209 [63005.944387] [tdb] Shutdown Tempesta DB Apr 26 09:34:15 192.168.122.209 [63006.173583] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_etag_brange_if_none_match_disallow Apr 26 09:34:15 192.168.122.209 [63006.183226] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_etag_brange_if_none_match_many_values Apr 26 09:34:16 192.168.122.209 [63007.304722] [tdb] Start Tempesta DB Apr 26 09:34:16 192.168.122.209 [63007.457857] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:34:18 192.168.122.209 [63008.819914] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63008.819914] Maybe that's fine, but it's worth checking the [63008.819914] config - if there is no relations between the [63008.819914] names, then host name confusion attack is possible. Apr 26 09:34:18 192.168.122.209 [63008.927029] [tempesta fw] Configuration processing is completed. Apr 26 09:34:18 192.168.122.209 [63008.985418] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:34:18 192.168.122.209 [63009.403586] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:34:18 192.168.122.209 [63009.430129] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:34:18 192.168.122.209 [63009.459172] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:34:18 192.168.122.209 [63009.522545] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:34:18 192.168.122.209 [63009.524301] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:34:18 192.168.122.209 [63009.574494] [tempesta fw] Tempesta FW is ready Apr 26 09:34:19 192.168.122.209 [63010.135114] [tdb] Close table 'client0.tdb' Apr 26 09:34:19 192.168.122.209 [63010.317290] [tdb] Close table 'sessions0.tdb' Apr 26 09:34:23 192.168.122.209 [63013.602030] [tdb] Close table 'cache0.tdb' Apr 26 09:34:23 192.168.122.209 [63013.864982] [tdb] Close table 'filter0.tdb' Apr 26 09:34:23 192.168.122.209 [63013.865406] [tempesta fw] modules are stopped Apr 26 09:34:23 192.168.122.209 [63014.067484] [tempesta fw] exiting... Apr 26 09:34:23 192.168.122.209 [63014.201115] [tdb] Shutdown Tempesta DB Apr 26 09:34:23 192.168.122.209 [63014.453503] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_etag_brange_if_none_match_many_values Apr 26 09:34:23 192.168.122.209 [63014.480893] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_nctl_brange_request_negative Apr 26 09:34:25 192.168.122.209 [63015.765787] [tdb] Start Tempesta DB Apr 26 09:34:25 192.168.122.209 [63015.901500] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:34:26 192.168.122.209 [63017.491837] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63017.491837] Maybe that's fine, but it's worth checking the [63017.491837] config - if there is no relations between the [63017.491837] names, then host name confusion attack is possible. Apr 26 09:34:26 192.168.122.209 [63017.590724] [tempesta fw] Configuration processing is completed. Apr 26 09:34:27 192.168.122.209 [63017.660041] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:34:27 192.168.122.209 [63018.238251] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:34:27 192.168.122.209 [63018.273593] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:34:27 192.168.122.209 [63018.309296] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:34:27 192.168.122.209 [63018.350698] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:34:27 192.168.122.209 [63018.352454] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:34:27 192.168.122.209 [63018.390640] [tempesta fw] Tempesta FW is ready Apr 26 09:34:27 192.168.122.209 [63018.543258] [tempesta fw] Warning: Parser error: state=Req_HdrIf_Modified_SinceV input(-0)=0x25('%') data_len=1 off=0 Apr 26 09:34:28 192.168.122.209 [63018.988332] [tdb] Close table 'client0.tdb' Apr 26 09:34:28 192.168.122.209 [63019.169419] [tdb] Close table 'sessions0.tdb' Apr 26 09:34:31 192.168.122.209 [63022.472879] [tdb] Close table 'cache0.tdb' Apr 26 09:34:32 192.168.122.209 [63022.750139] [tdb] Close table 'filter0.tdb' Apr 26 09:34:32 192.168.122.209 [63022.750608] [tempesta fw] modules are stopped Apr 26 09:34:32 192.168.122.209 [63022.973593] [tempesta fw] exiting... Apr 26 09:34:32 192.168.122.209 [63023.107735] [tdb] Shutdown Tempesta DB Apr 26 09:34:32 192.168.122.209 [63023.289022] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_nctl_brange_request_negative Apr 26 09:34:32 192.168.122.209 [63023.300410] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_nctl_brange_request_positive Apr 26 09:34:34 192.168.122.209 [63024.611034] [tdb] Start Tempesta DB Apr 26 09:34:34 192.168.122.209 [63024.760735] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:34:35 192.168.122.209 [63026.208226] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63026.208226] Maybe that's fine, but it's worth checking the [63026.208226] config - if there is no relations between the [63026.208226] names, then host name confusion attack is possible. Apr 26 09:34:35 192.168.122.209 [63026.314838] [tempesta fw] Configuration processing is completed. Apr 26 09:34:35 192.168.122.209 [63026.364262] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:34:36 192.168.122.209 [63026.796541] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:34:36 192.168.122.209 [63026.838945] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:34:36 192.168.122.209 [63026.866241] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:34:36 192.168.122.209 [63026.918999] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:34:36 192.168.122.209 [63026.920771] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:34:36 192.168.122.209 [63026.958759] [tempesta fw] Tempesta FW is ready Apr 26 09:34:36 192.168.122.209 [63027.557045] [tdb] Close table 'client0.tdb' Apr 26 09:34:37 192.168.122.209 [63027.764618] [tdb] Close table 'sessions0.tdb' Apr 26 09:34:40 192.168.122.209 [63030.989055] [tdb] Close table 'cache0.tdb' Apr 26 09:34:40 192.168.122.209 [63031.239327] [tdb] Close table 'filter0.tdb' Apr 26 09:34:40 192.168.122.209 [63031.239770] [tempesta fw] modules are stopped Apr 26 09:34:40 192.168.122.209 [63031.415331] [tempesta fw] exiting... Apr 26 09:34:40 192.168.122.209 [63031.556723] [tdb] Shutdown Tempesta DB Apr 26 09:34:41 192.168.122.209 [63031.779247] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_nctl_brange_request_positive Apr 26 09:34:41 192.168.122.209 [63031.794426] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_nctl_brange_response_negative Apr 26 09:34:42 192.168.122.209 [63033.021798] [tdb] Start Tempesta DB Apr 26 09:34:42 192.168.122.209 [63033.175228] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:34:44 192.168.122.209 [63034.596200] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63034.596200] Maybe that's fine, but it's worth checking the [63034.596200] config - if there is no relations between the [63034.596200] names, then host name confusion attack is possible. Apr 26 09:34:44 192.168.122.209 [63034.694923] [tempesta fw] Configuration processing is completed. Apr 26 09:34:44 192.168.122.209 [63034.767750] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:34:44 192.168.122.209 [63035.282298] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:34:44 192.168.122.209 [63035.325677] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:34:44 192.168.122.209 [63035.361758] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:34:44 192.168.122.209 [63035.406883] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:34:44 192.168.122.209 [63035.408630] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:34:44 192.168.122.209 [63035.450832] [tempesta fw] Tempesta FW is ready Apr 26 09:34:45 192.168.122.209 [63035.598443] [tempesta fw] Warning: Parser error: state=Resp_HdrDateV input(-0)=0x25('%') data_len=1 off=0 Apr 26 09:34:45 192.168.122.209 [63035.600092] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 09:34:45 192.168.122.209 [63035.627689] [tempesta fw] Warning: Parser error: state=Resp_HdrExpiresV input(-0)=0x25('%') data_len=1 off=0 Apr 26 09:34:45 192.168.122.209 [63035.630142] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 09:34:45 192.168.122.209 [63035.646050] [tempesta fw] Warning: Parser error: state=Resp_HdrLast_ModifiedV input(-0)=0x25('%') data_len=1 off=0 Apr 26 09:34:45 192.168.122.209 [63035.647026] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 09:34:45 192.168.122.209 [63036.111842] [tdb] Close table 'client0.tdb' Apr 26 09:34:45 192.168.122.209 [63036.309616] [tdb] Close table 'sessions0.tdb' Apr 26 09:34:49 192.168.122.209 [63039.691023] [tdb] Close table 'cache0.tdb' Apr 26 09:34:49 192.168.122.209 [63039.952328] [tdb] Close table 'filter0.tdb' Apr 26 09:34:49 192.168.122.209 [63039.952732] [tempesta fw] modules are stopped Apr 26 09:34:49 192.168.122.209 [63040.204310] [tempesta fw] exiting... Apr 26 09:34:49 192.168.122.209 [63040.331709] [tdb] Shutdown Tempesta DB Apr 26 09:34:49 192.168.122.209 [63040.546471] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_nctl_brange_response_negative Apr 26 09:34:49 192.168.122.209 [63040.564865] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_nctl_brange_response_positive Apr 26 09:34:51 192.168.122.209 [63041.994206] [tdb] Start Tempesta DB Apr 26 09:34:51 192.168.122.209 [63042.146244] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:34:52 192.168.122.209 [63043.576232] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63043.576232] Maybe that's fine, but it's worth checking the [63043.576232] config - if there is no relations between the [63043.576232] names, then host name confusion attack is possible. Apr 26 09:34:53 192.168.122.209 [63043.675044] [tempesta fw] Configuration processing is completed. Apr 26 09:34:53 192.168.122.209 [63043.735395] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:34:53 192.168.122.209 [63044.157161] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:34:53 192.168.122.209 [63044.189304] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:34:53 192.168.122.209 [63044.215893] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:34:53 192.168.122.209 [63044.259005] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:34:53 192.168.122.209 [63044.260734] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:34:53 192.168.122.209 [63044.314937] [tempesta fw] Tempesta FW is ready Apr 26 09:34:54 192.168.122.209 [63044.962268] [tdb] Close table 'client0.tdb' Apr 26 09:34:54 192.168.122.209 [63045.155982] [tdb] Close table 'sessions0.tdb' Apr 26 09:34:57 192.168.122.209 [63048.358952] [tdb] Close table 'cache0.tdb' Apr 26 09:34:58 192.168.122.209 [63048.605017] [tdb] Close table 'filter0.tdb' Apr 26 09:34:58 192.168.122.209 [63048.605450] [tempesta fw] modules are stopped Apr 26 09:34:58 192.168.122.209 [63048.817332] [tempesta fw] exiting... Apr 26 09:34:58 192.168.122.209 [63048.923838] [tdb] Shutdown Tempesta DB Apr 26 09:34:58 192.168.122.209 [63049.201297] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_nctl_brange_response_positive Apr 26 09:34:58 192.168.122.209 [63049.212029] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_qetoken_brange_disallow_equal Apr 26 09:34:59 192.168.122.209 [63050.309477] [tdb] Start Tempesta DB Apr 26 09:34:59 192.168.122.209 [63050.466532] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:35:01 192.168.122.209 [63051.944338] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63051.944338] Maybe that's fine, but it's worth checking the [63051.944338] config - if there is no relations between the [63051.944338] names, then host name confusion attack is possible. Apr 26 09:35:01 192.168.122.209 [63052.055181] [tempesta fw] Configuration processing is completed. Apr 26 09:35:01 192.168.122.209 [63052.113943] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:35:01 192.168.122.209 [63052.546121] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:35:01 192.168.122.209 [63052.592069] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:35:02 192.168.122.209 [63052.627215] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:35:02 192.168.122.209 [63052.679109] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:35:02 192.168.122.209 [63052.680862] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:35:02 192.168.122.209 [63052.719044] [tempesta fw] Tempesta FW is ready Apr 26 09:35:02 192.168.122.209 [63052.851842] [tempesta fw] Warning: Parser error: state=Req_HdrCache_ControlV input(-0)=0x3d('=') data_len=1 off=0 Apr 26 09:35:02 192.168.122.209 [63053.261569] [tdb] Close table 'client0.tdb' Apr 26 09:35:02 192.168.122.209 [63053.435072] [tdb] Close table 'sessions0.tdb' Apr 26 09:35:06 192.168.122.209 [63056.754274] [tdb] Close table 'cache0.tdb' Apr 26 09:35:06 192.168.122.209 [63057.007934] [tdb] Close table 'filter0.tdb' Apr 26 09:35:06 192.168.122.209 [63057.008357] [tempesta fw] modules are stopped Apr 26 09:35:06 192.168.122.209 [63057.185340] [tempesta fw] exiting... Apr 26 09:35:06 192.168.122.209 [63057.303947] [tdb] Shutdown Tempesta DB Apr 26 09:35:06 192.168.122.209 [63057.518504] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_qetoken_brange_disallow_equal Apr 26 09:35:06 192.168.122.209 [63057.530892] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_qetoken_brange_negative Apr 26 09:35:07 192.168.122.209 [63058.562057] [tdb] Start Tempesta DB Apr 26 09:35:08 192.168.122.209 [63058.705688] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:35:09 192.168.122.209 [63060.080540] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63060.080540] Maybe that's fine, but it's worth checking the [63060.080540] config - if there is no relations between the [63060.080540] names, then host name confusion attack is possible. Apr 26 09:35:09 192.168.122.209 [63060.175257] [tempesta fw] Configuration processing is completed. Apr 26 09:35:09 192.168.122.209 [63060.239112] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:35:10 192.168.122.209 [63060.687827] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:35:10 192.168.122.209 [63060.716218] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:35:10 192.168.122.209 [63060.745469] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:35:10 192.168.122.209 [63060.799209] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:35:10 192.168.122.209 [63060.800946] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:35:10 192.168.122.209 [63060.843143] [tempesta fw] Tempesta FW is ready Apr 26 09:35:10 192.168.122.209 [63060.987614] [tempesta fw] Warning: Parser error: state=Req_HdrCache_ControlV input(-0)=0x25('%') data_len=1 off=0 Apr 26 09:35:10 192.168.122.209 [63061.375577] [tdb] Close table 'client0.tdb' Apr 26 09:35:10 192.168.122.209 [63061.580408] [tdb] Close table 'sessions0.tdb' Apr 26 09:35:14 192.168.122.209 [63064.816199] [tdb] Close table 'cache0.tdb' Apr 26 09:35:14 192.168.122.209 [63065.069990] [tdb] Close table 'filter0.tdb' Apr 26 09:35:14 192.168.122.209 [63065.070398] [tempesta fw] modules are stopped Apr 26 09:35:14 192.168.122.209 [63065.252261] [tempesta fw] exiting... Apr 26 09:35:14 192.168.122.209 [63065.361572] [tdb] Shutdown Tempesta DB Apr 26 09:35:15 192.168.122.209 [63065.601097] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_qetoken_brange_negative Apr 26 09:35:15 192.168.122.209 [63065.610574] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_qetoken_brange_positive Apr 26 09:35:16 192.168.122.209 [63066.688623] [tdb] Start Tempesta DB Apr 26 09:35:16 192.168.122.209 [63066.827917] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:35:17 192.168.122.209 [63068.212601] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63068.212601] Maybe that's fine, but it's worth checking the [63068.212601] config - if there is no relations between the [63068.212601] names, then host name confusion attack is possible. Apr 26 09:35:17 192.168.122.209 [63068.335352] [tempesta fw] Configuration processing is completed. Apr 26 09:35:17 192.168.122.209 [63068.395702] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:35:18 192.168.122.209 [63068.847336] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:35:18 192.168.122.209 [63068.876202] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:35:18 192.168.122.209 [63068.905255] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:35:18 192.168.122.209 [63068.955333] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:35:18 192.168.122.209 [63068.957085] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:35:18 192.168.122.209 [63069.007267] [tempesta fw] Tempesta FW is ready Apr 26 09:35:19 192.168.122.209 [63069.603942] [tdb] Close table 'client0.tdb' Apr 26 09:35:19 192.168.122.209 [63069.793201] [tdb] Close table 'sessions0.tdb' Apr 26 09:35:22 192.168.122.209 [63072.991828] [tdb] Close table 'cache0.tdb' Apr 26 09:35:22 192.168.122.209 [63073.241356] [tdb] Close table 'filter0.tdb' Apr 26 09:35:22 192.168.122.209 [63073.241764] [tempesta fw] modules are stopped Apr 26 09:35:22 192.168.122.209 [63073.430678] [tempesta fw] exiting... Apr 26 09:35:22 192.168.122.209 [63073.569826] [tdb] Shutdown Tempesta DB Apr 26 09:35:23 192.168.122.209 [63073.769294] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_qetoken_brange_positive Apr 26 09:35:23 192.168.122.209 [63073.790434] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_token_brange_negative Apr 26 09:35:24 192.168.122.209 [63074.868633] [tdb] Start Tempesta DB Apr 26 09:35:24 192.168.122.209 [63075.016406] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:35:25 192.168.122.209 [63076.424698] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63076.424698] Maybe that's fine, but it's worth checking the [63076.424698] config - if there is no relations between the [63076.424698] names, then host name confusion attack is possible. Apr 26 09:35:25 192.168.122.209 [63076.539444] [tempesta fw] Configuration processing is completed. Apr 26 09:35:25 192.168.122.209 [63076.591579] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:35:26 192.168.122.209 [63077.010207] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:35:26 192.168.122.209 [63077.042076] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:35:26 192.168.122.209 [63077.072447] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:35:26 192.168.122.209 [63077.115426] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:35:26 192.168.122.209 [63077.117160] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:35:26 192.168.122.209 [63077.163401] [tempesta fw] Tempesta FW is ready Apr 26 09:35:26 192.168.122.209 [63077.321503] [tempesta fw] Warning: Parser error: state=Req_HdrCookieV input(-0)=0x25('%') data_len=1 off=0 Apr 26 09:35:27 192.168.122.209 [63077.740966] [tdb] Close table 'client0.tdb' Apr 26 09:35:27 192.168.122.209 [63077.926329] [tdb] Close table 'sessions0.tdb' Apr 26 09:35:30 192.168.122.209 [63081.151036] [tdb] Close table 'cache0.tdb' Apr 26 09:35:30 192.168.122.209 [63081.396950] [tdb] Close table 'filter0.tdb' Apr 26 09:35:30 192.168.122.209 [63081.397344] [tempesta fw] modules are stopped Apr 26 09:35:30 192.168.122.209 [63081.572172] [tempesta fw] exiting... Apr 26 09:35:31 192.168.122.209 [63081.695463] [tdb] Shutdown Tempesta DB Apr 26 09:35:31 192.168.122.209 [63081.927791] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_token_brange_negative Apr 26 09:35:31 192.168.122.209 [63081.940318] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_token_brange_positive Apr 26 09:35:32 192.168.122.209 [63083.022743] [tdb] Start Tempesta DB Apr 26 09:35:32 192.168.122.209 [63083.187632] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:35:33 192.168.122.209 [63084.580949] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63084.580949] Maybe that's fine, but it's worth checking the [63084.580949] config - if there is no relations between the [63084.580949] names, then host name confusion attack is possible. Apr 26 09:35:34 192.168.122.209 [63084.679554] [tempesta fw] Configuration processing is completed. Apr 26 09:35:34 192.168.122.209 [63084.732382] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:35:34 192.168.122.209 [63085.180581] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:35:34 192.168.122.209 [63085.209925] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:35:34 192.168.122.209 [63085.238308] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:35:34 192.168.122.209 [63085.335541] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:35:34 192.168.122.209 [63085.337320] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:35:34 192.168.122.209 [63085.379458] [tempesta fw] Tempesta FW is ready Apr 26 09:35:35 192.168.122.209 [63085.938952] [tdb] Close table 'client0.tdb' Apr 26 09:35:35 192.168.122.209 [63086.126628] [tdb] Close table 'sessions0.tdb' Apr 26 09:35:38 192.168.122.209 [63089.456062] [tdb] Close table 'cache0.tdb' Apr 26 09:35:39 192.168.122.209 [63089.717426] [tdb] Close table 'filter0.tdb' Apr 26 09:35:39 192.168.122.209 [63089.717872] [tempesta fw] modules are stopped Apr 26 09:35:39 192.168.122.209 [63089.902565] [tempesta fw] exiting... Apr 26 09:35:39 192.168.122.209 [63090.043883] [tdb] Shutdown Tempesta DB Apr 26 09:35:39 192.168.122.209 [63090.267199] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_token_brange_positive Apr 26 09:35:39 192.168.122.209 [63090.279283] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_uri_brange_blocked_percent Apr 26 09:35:40 192.168.122.209 [63091.429734] [tdb] Start Tempesta DB Apr 26 09:35:40 192.168.122.209 [63091.573560] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:35:42 192.168.122.209 [63092.908913] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63092.908913] Maybe that's fine, but it's worth checking the [63092.908913] config - if there is no relations between the [63092.908913] names, then host name confusion attack is possible. Apr 26 09:35:42 192.168.122.209 [63093.019681] [tempesta fw] Configuration processing is completed. Apr 26 09:35:42 192.168.122.209 [63093.071287] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:35:42 192.168.122.209 [63093.569681] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:35:43 192.168.122.209 [63093.603992] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:35:43 192.168.122.209 [63093.638246] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:35:43 192.168.122.209 [63093.703620] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:35:43 192.168.122.209 [63093.705393] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:35:43 192.168.122.209 [63093.743584] [tempesta fw] Tempesta FW is ready Apr 26 09:35:43 192.168.122.209 [63093.872381] [tempesta fw] Warning: Parser error: state=Req_UriAbsoluteForm input(-0)=0x6a('j') data_len=1 off=0 Apr 26 09:35:43 192.168.122.209 [63094.330383] [tdb] Close table 'client0.tdb' Apr 26 09:35:43 192.168.122.209 [63094.527256] [tdb] Close table 'sessions0.tdb' Apr 26 09:35:47 192.168.122.209 [63097.764687] [tdb] Close table 'cache0.tdb' Apr 26 09:35:47 192.168.122.209 [63098.007107] [tdb] Close table 'filter0.tdb' Apr 26 09:35:47 192.168.122.209 [63098.007932] [tempesta fw] modules are stopped Apr 26 09:35:47 192.168.122.209 [63098.217153] [tempesta fw] exiting... Apr 26 09:35:47 192.168.122.209 [63098.348505] [tdb] Shutdown Tempesta DB Apr 26 09:35:47 192.168.122.209 [63098.581700] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_uri_brange_blocked_percent Apr 26 09:35:47 192.168.122.209 [63098.592423] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_uri_brange_issue_2030 Apr 26 09:35:48 192.168.122.209 [63099.591176] [tdb] Start Tempesta DB Apr 26 09:35:49 192.168.122.209 [63099.725297] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:35:50 192.168.122.209 [63101.145073] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63101.145073] Maybe that's fine, but it's worth checking the [63101.145073] config - if there is no relations between the [63101.145073] names, then host name confusion attack is possible. Apr 26 09:35:50 192.168.122.209 [63101.248077] [tempesta fw] Configuration processing is completed. Apr 26 09:35:50 192.168.122.209 [63101.305604] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:35:51 192.168.122.209 [63101.736073] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:35:51 192.168.122.209 [63101.764633] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:35:51 192.168.122.209 [63101.792793] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:35:51 192.168.122.209 [63101.831722] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:35:51 192.168.122.209 [63101.833475] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:35:51 192.168.122.209 [63101.871700] [tempesta fw] Tempesta FW is ready Apr 26 09:35:51 192.168.122.209 [63102.409602] [tdb] Close table 'client0.tdb' Apr 26 09:35:51 192.168.122.209 [63102.582511] [tdb] Close table 'sessions0.tdb' Apr 26 09:35:55 192.168.122.209 [63105.808493] [tdb] Close table 'cache0.tdb' Apr 26 09:35:55 192.168.122.209 [63106.055351] [tdb] Close table 'filter0.tdb' Apr 26 09:35:55 192.168.122.209 [63106.055790] [tempesta fw] modules are stopped Apr 26 09:35:55 192.168.122.209 [63106.306908] [tempesta fw] exiting... Apr 26 09:35:55 192.168.122.209 [63106.444174] [tdb] Shutdown Tempesta DB Apr 26 09:35:56 192.168.122.209 [63106.613335] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_uri_brange_issue_2030 Apr 26 09:35:56 192.168.122.209 [63106.626670] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_uri_brange_not_blocked_percent Apr 26 09:35:57 192.168.122.209 [63107.605372] [tdb] Start Tempesta DB Apr 26 09:35:57 192.168.122.209 [63107.735281] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:35:58 192.168.122.209 [63109.085124] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63109.085124] Maybe that's fine, but it's worth checking the [63109.085124] config - if there is no relations between the [63109.085124] names, then host name confusion attack is possible. Apr 26 09:35:58 192.168.122.209 [63109.192403] [tempesta fw] Configuration processing is completed. Apr 26 09:35:58 192.168.122.209 [63109.249520] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:35:59 192.168.122.209 [63109.685782] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:35:59 192.168.122.209 [63109.712417] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:35:59 192.168.122.209 [63109.738687] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:35:59 192.168.122.209 [63109.779819] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:35:59 192.168.122.209 [63109.781546] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:35:59 192.168.122.209 [63109.827769] [tempesta fw] Tempesta FW is ready Apr 26 09:35:59 192.168.122.209 [63110.354445] [tdb] Close table 'client0.tdb' Apr 26 09:35:59 192.168.122.209 [63110.538096] [tdb] Close table 'sessions0.tdb' Apr 26 09:36:03 192.168.122.209 [63113.706746] [tdb] Close table 'cache0.tdb' Apr 26 09:36:03 192.168.122.209 [63113.930542] [tdb] Close table 'filter0.tdb' Apr 26 09:36:03 192.168.122.209 [63113.930968] [tempesta fw] modules are stopped Apr 26 09:36:03 192.168.122.209 [63114.122208] [tempesta fw] exiting... Apr 26 09:36:03 192.168.122.209 [63114.232994] [tdb] Shutdown Tempesta DB Apr 26 09:36:03 192.168.122.209 [63114.425131] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_uri_brange_not_blocked_percent Apr 26 09:36:03 192.168.122.209 [63114.446297] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_uri_brange_referer_header_allowed_character Apr 26 09:36:04 192.168.122.209 [63115.470465] [tdb] Start Tempesta DB Apr 26 09:36:05 192.168.122.209 [63115.599982] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:36:06 192.168.122.209 [63117.025201] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63117.025201] Maybe that's fine, but it's worth checking the [63117.025201] config - if there is no relations between the [63117.025201] names, then host name confusion attack is possible. Apr 26 09:36:06 192.168.122.209 [63117.143949] [tempesta fw] Configuration processing is completed. Apr 26 09:36:06 192.168.122.209 [63117.195879] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:36:07 192.168.122.209 [63117.609638] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:36:07 192.168.122.209 [63117.636225] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:36:07 192.168.122.209 [63117.662955] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:36:07 192.168.122.209 [63117.703916] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:36:07 192.168.122.209 [63117.705018] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:36:07 192.168.122.209 [63117.755868] [tempesta fw] Tempesta FW is ready Apr 26 09:36:07 192.168.122.209 [63118.301468] [tdb] Close table 'client0.tdb' Apr 26 09:36:07 192.168.122.209 [63118.479965] [tdb] Close table 'sessions0.tdb' Apr 26 09:36:12 192.168.122.209 [63123.257114] [tdb] Close table 'cache0.tdb' Apr 26 09:36:13 192.168.122.209 [63123.936505] [tdb] Close table 'filter0.tdb' Apr 26 09:36:13 192.168.122.209 [63123.936937] [tempesta fw] modules are stopped Apr 26 09:36:13 192.168.122.209 [63124.452798] [tempesta fw] exiting... Apr 26 09:36:14 192.168.122.209 [63124.954480] [tdb] Shutdown Tempesta DB Apr 26 09:36:14 192.168.122.209 [63125.143362] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_uri_brange_referer_header_allowed_character Apr 26 09:36:14 192.168.122.209 [63125.162748] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_uri_brange_referer_header_disallowed_character Apr 26 09:36:15 192.168.122.209 [63126.218331] [tdb] Start Tempesta DB Apr 26 09:36:15 192.168.122.209 [63126.346574] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:36:17 192.168.122.209 [63127.745334] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63127.745334] Maybe that's fine, but it's worth checking the [63127.745334] config - if there is no relations between the [63127.745334] names, then host name confusion attack is possible. Apr 26 09:36:17 192.168.122.209 [63127.848113] [tempesta fw] Configuration processing is completed. Apr 26 09:36:17 192.168.122.209 [63127.905566] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:36:17 192.168.122.209 [63128.327724] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:36:17 192.168.122.209 [63128.353964] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:36:17 192.168.122.209 [63128.381000] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:36:17 192.168.122.209 [63128.428069] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:36:17 192.168.122.209 [63128.428878] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:36:17 192.168.122.209 [63128.468020] [tempesta fw] Tempesta FW is ready Apr 26 09:36:18 192.168.122.209 [63128.604759] [tempesta fw] Warning: Parser error: state=Req_HdrRefererV input(-0)=0x2b('+') data_len=1 off=0 Apr 26 09:36:18 192.168.122.209 [63129.021721] [tdb] Close table 'client0.tdb' Apr 26 09:36:18 192.168.122.209 [63129.206214] [tdb] Close table 'sessions0.tdb' Apr 26 09:36:21 192.168.122.209 [63132.424073] [tdb] Close table 'cache0.tdb' Apr 26 09:36:22 192.168.122.209 [63132.660492] [tdb] Close table 'filter0.tdb' Apr 26 09:36:22 192.168.122.209 [63132.660920] [tempesta fw] modules are stopped Apr 26 09:36:22 192.168.122.209 [63132.845466] [tempesta fw] exiting... Apr 26 09:36:22 192.168.122.209 [63132.969450] [tdb] Shutdown Tempesta DB Apr 26 09:36:22 192.168.122.209 [63133.178488] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_uri_brange_referer_header_disallowed_character Apr 26 09:36:22 192.168.122.209 [63133.198043] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_xff_brange_allow_ipv4 Apr 26 09:36:23 192.168.122.209 [63134.207795] [tdb] Start Tempesta DB Apr 26 09:36:23 192.168.122.209 [63134.344853] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:36:25 192.168.122.209 [63135.813392] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63135.813392] Maybe that's fine, but it's worth checking the [63135.813392] config - if there is no relations between the [63135.813392] names, then host name confusion attack is possible. Apr 26 09:36:25 192.168.122.209 [63135.916176] [tempesta fw] Configuration processing is completed. Apr 26 09:36:25 192.168.122.209 [63135.969851] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:36:25 192.168.122.209 [63136.382620] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:36:25 192.168.122.209 [63136.409256] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:36:25 192.168.122.209 [63136.435284] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:36:25 192.168.122.209 [63136.496163] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:36:25 192.168.122.209 [63136.497898] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:36:25 192.168.122.209 [63136.552124] [tempesta fw] Tempesta FW is ready Apr 26 09:36:26 192.168.122.209 [63137.142005] [tdb] Close table 'client0.tdb' Apr 26 09:36:26 192.168.122.209 [63137.335813] [tdb] Close table 'sessions0.tdb' Apr 26 09:36:29 192.168.122.209 [63140.540774] [tdb] Close table 'cache0.tdb' Apr 26 09:36:30 192.168.122.209 [63140.786837] [tdb] Close table 'filter0.tdb' Apr 26 09:36:30 192.168.122.209 [63140.787284] [tempesta fw] modules are stopped Apr 26 09:36:30 192.168.122.209 [63140.960663] [tempesta fw] exiting... Apr 26 09:36:30 192.168.122.209 [63141.110497] [tdb] Shutdown Tempesta DB Apr 26 09:36:30 192.168.122.209 [63141.338462] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_xff_brange_allow_ipv4 Apr 26 09:36:30 192.168.122.209 [63141.352666] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_xff_brange_allow_ipv6 Apr 26 09:36:31 192.168.122.209 [63142.380214] [tdb] Start Tempesta DB Apr 26 09:36:31 192.168.122.209 [63142.508161] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:36:33 192.168.122.209 [63143.869676] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63143.869676] Maybe that's fine, but it's worth checking the [63143.869676] config - if there is no relations between the [63143.869676] names, then host name confusion attack is possible. Apr 26 09:36:33 192.168.122.209 [63143.972321] [tempesta fw] Configuration processing is completed. Apr 26 09:36:33 192.168.122.209 [63144.027534] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:36:33 192.168.122.209 [63144.445087] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:36:33 192.168.122.209 [63144.474050] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:36:33 192.168.122.209 [63144.515218] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:36:33 192.168.122.209 [63144.560270] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:36:33 192.168.122.209 [63144.561983] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:36:34 192.168.122.209 [63144.608276] [tempesta fw] Tempesta FW is ready Apr 26 09:36:34 192.168.122.209 [63145.197249] [tdb] Close table 'client0.tdb' Apr 26 09:36:34 192.168.122.209 [63145.381057] [tdb] Close table 'sessions0.tdb' Apr 26 09:36:38 192.168.122.209 [63148.629135] [tdb] Close table 'cache0.tdb' Apr 26 09:36:38 192.168.122.209 [63148.866533] [tdb] Close table 'filter0.tdb' Apr 26 09:36:38 192.168.122.209 [63148.866960] [tempesta fw] modules are stopped Apr 26 09:36:38 192.168.122.209 [63149.079588] [tempesta fw] exiting... Apr 26 09:36:38 192.168.122.209 [63149.220310] [tdb] Shutdown Tempesta DB Apr 26 09:36:38 192.168.122.209 [63149.401957] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_xff_brange_allow_ipv6 Apr 26 09:36:38 192.168.122.209 [63149.425350] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_xff_brange_allow_many_ip Apr 26 09:36:39 192.168.122.209 [63150.446001] [tdb] Start Tempesta DB Apr 26 09:36:39 192.168.122.209 [63150.565865] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:36:41 192.168.122.209 [63151.937728] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63151.937728] Maybe that's fine, but it's worth checking the [63151.937728] config - if there is no relations between the [63151.937728] names, then host name confusion attack is possible. Apr 26 09:36:41 192.168.122.209 [63152.045709] [tempesta fw] Configuration processing is completed. Apr 26 09:36:41 192.168.122.209 [63152.102518] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:36:41 192.168.122.209 [63152.520473] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:36:41 192.168.122.209 [63152.546885] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:36:41 192.168.122.209 [63152.574962] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:36:42 192.168.122.209 [63152.624363] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:36:42 192.168.122.209 [63152.626114] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:36:42 192.168.122.209 [63152.672422] [tempesta fw] Tempesta FW is ready Apr 26 09:36:42 192.168.122.209 [63153.247335] [tdb] Close table 'client0.tdb' Apr 26 09:36:42 192.168.122.209 [63153.435419] [tdb] Close table 'sessions0.tdb' Apr 26 09:36:46 192.168.122.209 [63156.616171] [tdb] Close table 'cache0.tdb' Apr 26 09:36:46 192.168.122.209 [63156.872540] [tdb] Close table 'filter0.tdb' Apr 26 09:36:46 192.168.122.209 [63156.872958] [tempesta fw] modules are stopped Apr 26 09:36:46 192.168.122.209 [63157.044115] [tempesta fw] exiting... Apr 26 09:36:46 192.168.122.209 [63157.154292] [tdb] Shutdown Tempesta DB Apr 26 09:36:46 192.168.122.209 [63157.339265] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_xff_brange_allow_many_ip Apr 26 09:36:46 192.168.122.209 [63157.359866] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_xff_brange_disallow_ipv4 Apr 26 09:36:47 192.168.122.209 [63158.342997] [tdb] Start Tempesta DB Apr 26 09:36:47 192.168.122.209 [63158.485955] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:36:49 192.168.122.209 [63159.837697] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63159.837697] Maybe that's fine, but it's worth checking the [63159.837697] config - if there is no relations between the [63159.837697] names, then host name confusion attack is possible. Apr 26 09:36:49 192.168.122.209 [63159.948506] [tempesta fw] Configuration processing is completed. Apr 26 09:36:49 192.168.122.209 [63160.005622] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:36:49 192.168.122.209 [63160.454379] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:36:49 192.168.122.209 [63160.480203] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:36:49 192.168.122.209 [63160.506452] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:36:49 192.168.122.209 [63160.556509] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:36:49 192.168.122.209 [63160.558266] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:36:50 192.168.122.209 [63160.600429] [tempesta fw] Tempesta FW is ready Apr 26 09:36:50 192.168.122.209 [63160.740648] [tempesta fw] Warning: Parser error: state=Req_HdrX_Forwarded_ForV input(-0)=0x2e('.') data_len=1 off=0 Apr 26 09:36:50 192.168.122.209 [63161.143583] [tdb] Close table 'client0.tdb' Apr 26 09:36:50 192.168.122.209 [63161.329464] [tdb] Close table 'sessions0.tdb' Apr 26 09:36:53 192.168.122.209 [63164.503933] [tdb] Close table 'cache0.tdb' Apr 26 09:36:54 192.168.122.209 [63164.753585] [tdb] Close table 'filter0.tdb' Apr 26 09:36:54 192.168.122.209 [63164.754019] [tempesta fw] modules are stopped Apr 26 09:36:54 192.168.122.209 [63164.930411] [tempesta fw] exiting... Apr 26 09:36:54 192.168.122.209 [63165.041005] [tdb] Shutdown Tempesta DB Apr 26 09:36:54 192.168.122.209 [63165.264392] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_xff_brange_disallow_ipv4 Apr 26 09:36:54 192.168.122.209 [63165.277888] Start test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_xff_brange_disallow_ipv6 Apr 26 09:36:55 192.168.122.209 [63166.353957] [tdb] Start Tempesta DB Apr 26 09:36:55 192.168.122.209 [63166.488185] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:36:57 192.168.122.209 [63167.865864] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63167.865864] Maybe that's fine, but it's worth checking the [63167.865864] config - if there is no relations between the [63167.865864] names, then host name confusion attack is possible. Apr 26 09:36:57 192.168.122.209 [63167.980575] [tempesta fw] Configuration processing is completed. Apr 26 09:36:57 192.168.122.209 [63168.035702] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:36:57 192.168.122.209 [63168.441532] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:36:57 192.168.122.209 [63168.466865] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:36:57 192.168.122.209 [63168.492921] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:36:57 192.168.122.209 [63168.536580] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:36:57 192.168.122.209 [63168.538319] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:36:57 192.168.122.209 [63168.572517] [tempesta fw] Tempesta FW is ready Apr 26 09:36:58 192.168.122.209 [63168.709584] [tempesta fw] Warning: Parser error: state=Req_HdrX_Forwarded_ForV input(-0)=0x3a(':') data_len=1 off=0 Apr 26 09:36:58 192.168.122.209 [63169.108234] [tdb] Close table 'client0.tdb' Apr 26 09:36:58 192.168.122.209 [63169.299624] [tdb] Close table 'sessions0.tdb' Apr 26 09:37:01 192.168.122.209 [63172.481607] [tdb] Close table 'cache0.tdb' Apr 26 09:37:02 192.168.122.209 [63172.726812] [tdb] Close table 'filter0.tdb' Apr 26 09:37:02 192.168.122.209 [63172.727338] [tempesta fw] modules are stopped Apr 26 09:37:02 192.168.122.209 [63172.950290] [tempesta fw] exiting... Apr 26 09:37:02 192.168.122.209 [63173.072807] [tdb] Shutdown Tempesta DB Apr 26 09:37:02 192.168.122.209 [63173.282350] End test: t_custom_branges.test_http_brange.TestBrangeHttp.test_http_xff_brange_disallow_ipv6 Apr 26 09:37:02 192.168.122.209 [63173.305797] Start test: t_frang.test_header_cnt.FrangHttpHeaderCountH2.test_default_http_header_cnt_huffman Apr 26 09:37:03 192.168.122.209 [63174.396383] [tdb] Start Tempesta DB Apr 26 09:37:03 192.168.122.209 [63174.537326] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:37:05 192.168.122.209 [63176.098137] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63176.098137] Maybe that's fine, but it's worth checking the [63176.098137] config - if there is no relations between the [63176.098137] names, then host name confusion attack is possible. Apr 26 09:37:05 192.168.122.209 [63176.204696] [tempesta fw] Configuration processing is completed. Apr 26 09:37:05 192.168.122.209 [63176.269798] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:37:05 192.168.122.209 [63176.302046] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:37:05 192.168.122.209 [63176.332114] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:37:05 192.168.122.209 [63176.376673] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:37:05 192.168.122.209 [63176.378428] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:37:05 192.168.122.209 [63176.380129] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:37:05 192.168.122.209 [63176.424618] [tempesta fw] Tempesta FW is ready Apr 26 09:37:06 192.168.122.209 [63177.137362] [tdb] Close table 'client0.tdb' Apr 26 09:37:06 192.168.122.209 [63177.326793] [tdb] Close table 'sessions0.tdb' Apr 26 09:37:06 192.168.122.209 [63177.561552] [tdb] Close table 'filter0.tdb' Apr 26 09:37:06 192.168.122.209 [63177.561968] [tempesta fw] modules are stopped Apr 26 09:37:07 192.168.122.209 [63177.796342] [tempesta fw] exiting... Apr 26 09:37:07 192.168.122.209 [63177.920058] [tdb] Shutdown Tempesta DB Apr 26 09:37:07 192.168.122.209 [63178.121726] End test: t_frang.test_header_cnt.FrangHttpHeaderCountH2.test_default_http_header_cnt_huffman Apr 26 09:37:07 192.168.122.209 [63178.128978] Start test: t_frang.test_header_cnt.FrangHttpHeaderCountH2.test_default_http_header_cnt_no_huffman Apr 26 09:37:08 192.168.122.209 [63179.188872] [tdb] Start Tempesta DB Apr 26 09:37:08 192.168.122.209 [63179.315783] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:37:09 192.168.122.209 [63180.121897] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63180.121897] Maybe that's fine, but it's worth checking the [63180.121897] config - if there is no relations between the [63180.121897] names, then host name confusion attack is possible. Apr 26 09:37:09 192.168.122.209 [63180.240734] [tempesta fw] Configuration processing is completed. Apr 26 09:37:09 192.168.122.209 [63180.291251] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:37:09 192.168.122.209 [63180.318478] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:37:09 192.168.122.209 [63180.345996] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:37:09 192.168.122.209 [63180.404724] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:37:09 192.168.122.209 [63180.406463] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:37:09 192.168.122.209 [63180.408123] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:37:09 192.168.122.209 [63180.456661] [tempesta fw] Tempesta FW is ready Apr 26 09:37:10 192.168.122.209 [63181.123646] [tdb] Close table 'client0.tdb' Apr 26 09:37:10 192.168.122.209 [63181.327052] [tdb] Close table 'sessions0.tdb' Apr 26 09:37:10 192.168.122.209 [63181.550372] [tdb] Close table 'filter0.tdb' Apr 26 09:37:10 192.168.122.209 [63181.550797] [tempesta fw] modules are stopped Apr 26 09:37:11 192.168.122.209 [63181.757834] [tempesta fw] exiting... Apr 26 09:37:11 192.168.122.209 [63181.899613] [tdb] Shutdown Tempesta DB Apr 26 09:37:11 192.168.122.209 [63182.113471] End test: t_frang.test_header_cnt.FrangHttpHeaderCountH2.test_default_http_header_cnt_no_huffman Apr 26 09:37:11 192.168.122.209 [63182.122916] Start test: t_frang.test_header_cnt.FrangHttpHeaderCountH2.test_hpack_bomb_huffman Apr 26 09:37:12 192.168.122.209 [63183.168477] [tdb] Start Tempesta DB Apr 26 09:37:12 192.168.122.209 [63183.306940] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:37:13 192.168.122.209 [63184.130082] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63184.130082] Maybe that's fine, but it's worth checking the [63184.130082] config - if there is no relations between the [63184.130082] names, then host name confusion attack is possible. Apr 26 09:37:13 192.168.122.209 [63184.244810] [tempesta fw] Configuration processing is completed. Apr 26 09:37:13 192.168.122.209 [63184.302120] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:37:13 192.168.122.209 [63184.334646] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:37:13 192.168.122.209 [63184.367703] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:37:13 192.168.122.209 [63184.424771] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:37:13 192.168.122.209 [63184.426504] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:37:13 192.168.122.209 [63184.428177] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:37:13 192.168.122.209 [63184.464724] [tempesta fw] Tempesta FW is ready Apr 26 09:37:14 192.168.122.209 [63185.199329] [tempesta fw] Warning: frang: HTTP headers count exceeded for 127.0.0.2: 7 (lim=6) Apr 26 09:37:16 192.168.122.209 [63187.594974] [tdb] Close table 'client0.tdb' Apr 26 09:37:17 192.168.122.209 [63187.808556] [tdb] Close table 'sessions0.tdb' Apr 26 09:37:17 192.168.122.209 [63188.059610] [tdb] Close table 'filter0.tdb' Apr 26 09:37:17 192.168.122.209 [63188.060034] [tempesta fw] modules are stopped Apr 26 09:37:17 192.168.122.209 [63188.244641] [tempesta fw] exiting... Apr 26 09:37:17 192.168.122.209 [63188.368801] [tdb] Shutdown Tempesta DB Apr 26 09:37:17 192.168.122.209 [63188.555323] End test: t_frang.test_header_cnt.FrangHttpHeaderCountH2.test_hpack_bomb_huffman Apr 26 09:37:17 192.168.122.209 [63188.567955] Start test: t_frang.test_header_cnt.FrangHttpHeaderCountH2.test_hpack_bomb_no_huffman Apr 26 09:37:19 192.168.122.209 [63189.673299] [tdb] Start Tempesta DB Apr 26 09:37:19 192.168.122.209 [63189.802918] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:37:19 192.168.122.209 [63190.586114] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63190.586114] Maybe that's fine, but it's worth checking the [63190.586114] config - if there is no relations between the [63190.586114] names, then host name confusion attack is possible. Apr 26 09:37:20 192.168.122.209 [63190.688897] [tempesta fw] Configuration processing is completed. Apr 26 09:37:20 192.168.122.209 [63190.748927] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:37:20 192.168.122.209 [63190.781805] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:37:20 192.168.122.209 [63190.811581] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:37:20 192.168.122.209 [63190.860863] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:37:20 192.168.122.209 [63190.862565] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:37:20 192.168.122.209 [63190.864201] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:37:20 192.168.122.209 [63190.920811] [tempesta fw] Tempesta FW is ready Apr 26 09:37:21 192.168.122.209 [63191.657091] [tempesta fw] Warning: HTTP/2 request dropped: state=RGen_HdrOtherV input=0x0(''), len=77, off=0 Apr 26 09:37:25 192.168.122.209 [63196.273154] [tdb] Close table 'client0.tdb' Apr 26 09:37:25 192.168.122.209 [63196.459585] [tdb] Close table 'sessions0.tdb' Apr 26 09:37:26 192.168.122.209 [63196.684494] [tdb] Close table 'filter0.tdb' Apr 26 09:37:26 192.168.122.209 [63196.684931] [tempesta fw] modules are stopped Apr 26 09:37:26 192.168.122.209 [63196.868528] [tempesta fw] exiting... Apr 26 09:37:26 192.168.122.209 [63196.986913] [tdb] Shutdown Tempesta DB Apr 26 09:37:26 192.168.122.209 [63197.227010] End test: t_frang.test_header_cnt.FrangHttpHeaderCountH2.test_hpack_bomb_no_huffman Apr 26 09:37:26 192.168.122.209 [63197.232645] Start test: t_frang.test_header_cnt.FrangHttpHeaderCountH2.test_not_reaching_limit_headers_as_bytes_huffman Apr 26 09:37:27 192.168.122.209 [63198.298789] [tdb] Start Tempesta DB Apr 26 09:37:27 192.168.122.209 [63198.435403] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:37:28 192.168.122.209 [63199.262282] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63199.262282] Maybe that's fine, but it's worth checking the [63199.262282] config - if there is no relations between the [63199.262282] names, then host name confusion attack is possible. Apr 26 09:37:28 192.168.122.209 [63199.356990] [tempesta fw] Configuration processing is completed. Apr 26 09:37:28 192.168.122.209 [63199.414567] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:37:28 192.168.122.209 [63199.447299] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:37:28 192.168.122.209 [63199.478527] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:37:28 192.168.122.209 [63199.520903] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:37:28 192.168.122.209 [63199.522575] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:37:28 192.168.122.209 [63199.524273] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:37:28 192.168.122.209 [63199.560915] [tempesta fw] Tempesta FW is ready Apr 26 09:37:29 192.168.122.209 [63200.303220] [tdb] Close table 'client0.tdb' Apr 26 09:37:29 192.168.122.209 [63200.490724] [tdb] Close table 'sessions0.tdb' Apr 26 09:37:30 192.168.122.209 [63200.714025] [tdb] Close table 'filter0.tdb' Apr 26 09:37:30 192.168.122.209 [63200.714449] [tempesta fw] modules are stopped Apr 26 09:37:30 192.168.122.209 [63200.935431] [tempesta fw] exiting... Apr 26 09:37:30 192.168.122.209 [63201.040118] [tdb] Shutdown Tempesta DB Apr 26 09:37:30 192.168.122.209 [63201.221327] End test: t_frang.test_header_cnt.FrangHttpHeaderCountH2.test_not_reaching_limit_headers_as_bytes_huffman Apr 26 09:37:30 192.168.122.209 [63201.228148] Start test: t_frang.test_header_cnt.FrangHttpHeaderCountH2.test_not_reaching_limit_headers_as_bytes_no_huffman Apr 26 09:37:31 192.168.122.209 [63202.287352] [tdb] Start Tempesta DB Apr 26 09:37:31 192.168.122.209 [63202.425849] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:37:32 192.168.122.209 [63203.298314] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63203.298314] Maybe that's fine, but it's worth checking the [63203.298314] config - if there is no relations between the [63203.298314] names, then host name confusion attack is possible. Apr 26 09:37:32 192.168.122.209 [63203.405091] [tempesta fw] Configuration processing is completed. Apr 26 09:37:32 192.168.122.209 [63203.463417] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:37:32 192.168.122.209 [63203.499186] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:37:32 192.168.122.209 [63203.528631] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:37:32 192.168.122.209 [63203.581029] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:37:32 192.168.122.209 [63203.582750] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:37:32 192.168.122.209 [63203.584464] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:37:33 192.168.122.209 [63203.620962] [tempesta fw] Tempesta FW is ready Apr 26 09:37:33 192.168.122.209 [63204.320958] [tdb] Close table 'client0.tdb' Apr 26 09:37:33 192.168.122.209 [63204.511274] [tdb] Close table 'sessions0.tdb' Apr 26 09:37:34 192.168.122.209 [63204.743484] [tdb] Close table 'filter0.tdb' Apr 26 09:37:34 192.168.122.209 [63204.743907] [tempesta fw] modules are stopped Apr 26 09:37:34 192.168.122.209 [63204.956497] [tempesta fw] exiting... Apr 26 09:37:34 192.168.122.209 [63205.074580] [tdb] Shutdown Tempesta DB Apr 26 09:37:34 192.168.122.209 [63205.294208] End test: t_frang.test_header_cnt.FrangHttpHeaderCountH2.test_not_reaching_limit_headers_as_bytes_no_huffman Apr 26 09:37:34 192.168.122.209 [63205.304579] Start test: t_frang.test_header_cnt.FrangHttpHeaderCountH2.test_not_reaching_the_limit Apr 26 09:37:35 192.168.122.209 [63206.456623] [tdb] Start Tempesta DB Apr 26 09:37:35 192.168.122.209 [63206.594831] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:37:36 192.168.122.209 [63207.406392] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63207.406392] Maybe that's fine, but it's worth checking the [63207.406392] config - if there is no relations between the [63207.406392] names, then host name confusion attack is possible. Apr 26 09:37:36 192.168.122.209 [63207.521080] [tempesta fw] Configuration processing is completed. Apr 26 09:37:36 192.168.122.209 [63207.572483] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:37:37 192.168.122.209 [63207.600807] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:37:37 192.168.122.209 [63207.631395] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:37:37 192.168.122.209 [63207.673061] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:37:37 192.168.122.209 [63207.674738] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:37:37 192.168.122.209 [63207.676394] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:37:37 192.168.122.209 [63207.721017] [tempesta fw] Tempesta FW is ready Apr 26 09:37:37 192.168.122.209 [63208.431773] [tdb] Close table 'client0.tdb' Apr 26 09:37:38 192.168.122.209 [63208.646883] [tdb] Close table 'sessions0.tdb' Apr 26 09:37:38 192.168.122.209 [63208.855418] [tdb] Close table 'filter0.tdb' Apr 26 09:37:38 192.168.122.209 [63208.855843] [tempesta fw] modules are stopped Apr 26 09:37:38 192.168.122.209 [63209.051885] [tempesta fw] exiting... Apr 26 09:37:38 192.168.122.209 [63209.208780] [tdb] Shutdown Tempesta DB Apr 26 09:37:38 192.168.122.209 [63209.407004] End test: t_frang.test_header_cnt.FrangHttpHeaderCountH2.test_not_reaching_the_limit Apr 26 09:37:38 192.168.122.209 [63209.422021] Start test: t_frang.test_header_cnt.FrangHttpHeaderCountH2.test_not_reaching_the_limit_2_huffman Apr 26 09:37:39 192.168.122.209 [63210.470225] [tdb] Start Tempesta DB Apr 26 09:37:40 192.168.122.209 [63210.607079] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:37:40 192.168.122.209 [63211.446997] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63211.446997] Maybe that's fine, but it's worth checking the [63211.446997] config - if there is no relations between the [63211.446997] names, then host name confusion attack is possible. Apr 26 09:37:40 192.168.122.209 [63211.545181] [tempesta fw] Configuration processing is completed. Apr 26 09:37:41 192.168.122.209 [63211.602376] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:37:41 192.168.122.209 [63211.634629] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:37:41 192.168.122.209 [63211.664956] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:37:41 192.168.122.209 [63211.705148] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:37:41 192.168.122.209 [63211.706464] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:37:41 192.168.122.209 [63211.708099] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:37:41 192.168.122.209 [63211.745066] [tempesta fw] Tempesta FW is ready Apr 26 09:37:41 192.168.122.209 [63212.439497] [tdb] Close table 'client0.tdb' Apr 26 09:37:42 192.168.122.209 [63212.642432] [tdb] Close table 'sessions0.tdb' Apr 26 09:37:42 192.168.122.209 [63212.892024] [tdb] Close table 'filter0.tdb' Apr 26 09:37:42 192.168.122.209 [63212.892446] [tempesta fw] modules are stopped Apr 26 09:37:42 192.168.122.209 [63213.085187] [tempesta fw] exiting... Apr 26 09:37:42 192.168.122.209 [63213.218218] [tdb] Shutdown Tempesta DB Apr 26 09:37:42 192.168.122.209 [63213.438301] End test: t_frang.test_header_cnt.FrangHttpHeaderCountH2.test_not_reaching_the_limit_2_huffman Apr 26 09:37:42 192.168.122.209 [63213.456878] Start test: t_frang.test_header_cnt.FrangHttpHeaderCountH2.test_not_reaching_the_limit_2_no_huffman Apr 26 09:37:43 192.168.122.209 [63214.539848] [tdb] Start Tempesta DB Apr 26 09:37:44 192.168.122.209 [63214.678553] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:37:44 192.168.122.209 [63215.546472] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63215.546472] Maybe that's fine, but it's worth checking the [63215.546472] config - if there is no relations between the [63215.546472] names, then host name confusion attack is possible. Apr 26 09:37:45 192.168.122.209 [63215.641182] [tempesta fw] Configuration processing is completed. Apr 26 09:37:45 192.168.122.209 [63215.696229] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:37:45 192.168.122.209 [63215.725740] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:37:45 192.168.122.209 [63215.754396] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:37:45 192.168.122.209 [63215.809182] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:37:45 192.168.122.209 [63215.810967] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:37:45 192.168.122.209 [63215.812638] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:37:45 192.168.122.209 [63215.865111] [tempesta fw] Tempesta FW is ready Apr 26 09:37:45 192.168.122.209 [63216.596022] [tdb] Close table 'client0.tdb' Apr 26 09:37:46 192.168.122.209 [63216.789116] [tdb] Close table 'sessions0.tdb' Apr 26 09:37:46 192.168.122.209 [63217.034118] [tdb] Close table 'filter0.tdb' Apr 26 09:37:46 192.168.122.209 [63217.034567] [tempesta fw] modules are stopped Apr 26 09:37:46 192.168.122.209 [63217.253877] [tempesta fw] exiting... Apr 26 09:37:46 192.168.122.209 [63217.371856] [tdb] Shutdown Tempesta DB Apr 26 09:37:46 192.168.122.209 [63217.558131] End test: t_frang.test_header_cnt.FrangHttpHeaderCountH2.test_not_reaching_the_limit_2_no_huffman Apr 26 09:37:46 192.168.122.209 [63217.569306] Start test: t_frang.test_header_cnt.FrangHttpHeaderCountH2.test_reaching_limit_headers_as_bytes_huffman Apr 26 09:37:47 192.168.122.209 [63218.597362] [tdb] Start Tempesta DB Apr 26 09:37:48 192.168.122.209 [63218.731702] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:37:48 192.168.122.209 [63219.522479] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63219.522479] Maybe that's fine, but it's worth checking the [63219.522479] config - if there is no relations between the [63219.522479] names, then host name confusion attack is possible. Apr 26 09:37:49 192.168.122.209 [63219.637259] [tempesta fw] Configuration processing is completed. Apr 26 09:37:49 192.168.122.209 [63219.690476] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:37:49 192.168.122.209 [63219.718051] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:37:49 192.168.122.209 [63219.745204] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:37:49 192.168.122.209 [63219.789230] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:37:49 192.168.122.209 [63219.790900] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:37:49 192.168.122.209 [63219.792557] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:37:49 192.168.122.209 [63219.841171] [tempesta fw] Tempesta FW is ready Apr 26 09:37:49 192.168.122.209 [63220.048302] [tempesta fw] Warning: frang: HTTP headers count exceeded for 127.0.0.2: 6 (lim=5) Apr 26 09:37:49 192.168.122.209 [63220.528371] [tdb] Close table 'client0.tdb' Apr 26 09:37:50 192.168.122.209 [63220.718438] [tdb] Close table 'sessions0.tdb' Apr 26 09:37:50 192.168.122.209 [63220.980535] [tdb] Close table 'filter0.tdb' Apr 26 09:37:50 192.168.122.209 [63220.980946] [tempesta fw] modules are stopped Apr 26 09:37:50 192.168.122.209 [63221.154897] [tempesta fw] exiting... Apr 26 09:37:50 192.168.122.209 [63221.283398] [tdb] Shutdown Tempesta DB Apr 26 09:37:50 192.168.122.209 [63221.473509] End test: t_frang.test_header_cnt.FrangHttpHeaderCountH2.test_reaching_limit_headers_as_bytes_huffman Apr 26 09:37:50 192.168.122.209 [63221.494193] Start test: t_frang.test_header_cnt.FrangHttpHeaderCountH2.test_reaching_limit_headers_as_bytes_no_huffman Apr 26 09:37:51 192.168.122.209 [63222.591582] [tdb] Start Tempesta DB Apr 26 09:37:52 192.168.122.209 [63222.728230] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:37:52 192.168.122.209 [63223.570604] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63223.570604] Maybe that's fine, but it's worth checking the [63223.570604] config - if there is no relations between the [63223.570604] names, then host name confusion attack is possible. Apr 26 09:37:53 192.168.122.209 [63223.693313] [tempesta fw] Configuration processing is completed. Apr 26 09:37:53 192.168.122.209 [63223.749549] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:37:53 192.168.122.209 [63223.781300] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:37:53 192.168.122.209 [63223.810874] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:37:53 192.168.122.209 [63223.861296] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:37:53 192.168.122.209 [63223.863059] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:37:53 192.168.122.209 [63223.864687] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:37:53 192.168.122.209 [63223.913234] [tempesta fw] Tempesta FW is ready Apr 26 09:37:53 192.168.122.209 [63224.115898] [tempesta fw] Warning: frang: HTTP headers count exceeded for 127.0.0.2: 6 (lim=5) Apr 26 09:37:53 192.168.122.209 [63224.592217] [tdb] Close table 'client0.tdb' Apr 26 09:37:54 192.168.122.209 [63224.784690] [tdb] Close table 'sessions0.tdb' Apr 26 09:37:54 192.168.122.209 [63225.023327] [tdb] Close table 'filter0.tdb' Apr 26 09:37:54 192.168.122.209 [63225.023770] [tempesta fw] modules are stopped Apr 26 09:37:54 192.168.122.209 [63225.205298] [tempesta fw] exiting... Apr 26 09:37:54 192.168.122.209 [63225.331736] [tdb] Shutdown Tempesta DB Apr 26 09:37:54 192.168.122.209 [63225.535392] End test: t_frang.test_header_cnt.FrangHttpHeaderCountH2.test_reaching_limit_headers_as_bytes_no_huffman Apr 26 09:37:54 192.168.122.209 [63225.548300] Start test: t_frang.test_header_cnt.FrangHttpHeaderCountH2.test_reaching_the_limit Apr 26 09:37:56 192.168.122.209 [63226.651850] [tdb] Start Tempesta DB Apr 26 09:37:56 192.168.122.209 [63226.790710] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:37:57 192.168.122.209 [63227.614619] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63227.614619] Maybe that's fine, but it's worth checking the [63227.614619] config - if there is no relations between the [63227.614619] names, then host name confusion attack is possible. Apr 26 09:37:57 192.168.122.209 [63227.713421] [tempesta fw] Configuration processing is completed. Apr 26 09:37:57 192.168.122.209 [63227.770979] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:37:57 192.168.122.209 [63227.804136] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:37:57 192.168.122.209 [63227.834614] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:37:57 192.168.122.209 [63227.881339] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:37:57 192.168.122.209 [63227.883032] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:37:57 192.168.122.209 [63227.884667] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:37:57 192.168.122.209 [63227.921266] [tempesta fw] Tempesta FW is ready Apr 26 09:37:57 192.168.122.209 [63228.107795] [tempesta fw] Warning: frang: HTTP headers count exceeded for 127.0.0.2: 3 (lim=2) Apr 26 09:37:58 192.168.122.209 [63228.621791] [tdb] Close table 'client0.tdb' Apr 26 09:37:58 192.168.122.209 [63228.814260] [tdb] Close table 'sessions0.tdb' Apr 26 09:37:58 192.168.122.209 [63229.064879] [tdb] Close table 'filter0.tdb' Apr 26 09:37:58 192.168.122.209 [63229.065691] [tempesta fw] modules are stopped Apr 26 09:37:58 192.168.122.209 [63229.265186] [tempesta fw] exiting... Apr 26 09:37:58 192.168.122.209 [63229.386116] [tdb] Shutdown Tempesta DB Apr 26 09:37:59 192.168.122.209 [63229.633692] End test: t_frang.test_header_cnt.FrangHttpHeaderCountH2.test_reaching_the_limit Apr 26 09:37:59 192.168.122.209 [63229.648455] Start test: t_frang.test_header_cnt.FrangHttpHeaderCountTestCase.test_default_http_header_cnt Apr 26 09:38:00 192.168.122.209 [63230.699292] [tdb] Start Tempesta DB Apr 26 09:38:00 192.168.122.209 [63230.832016] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:38:01 192.168.122.209 [63231.634565] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63231.634565] Maybe that's fine, but it's worth checking the [63231.634565] config - if there is no relations between the [63231.634565] names, then host name confusion attack is possible. Apr 26 09:38:01 192.168.122.209 [63231.749387] [tempesta fw] Configuration processing is completed. Apr 26 09:38:01 192.168.122.209 [63231.804087] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:38:01 192.168.122.209 [63231.834325] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:38:01 192.168.122.209 [63231.862883] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:38:01 192.168.122.209 [63231.901370] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:38:01 192.168.122.209 [63231.903046] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:38:01 192.168.122.209 [63231.904757] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:38:01 192.168.122.209 [63231.941326] [tempesta fw] Tempesta FW is ready Apr 26 09:38:01 192.168.122.209 [63232.571868] [tdb] Close table 'client0.tdb' Apr 26 09:38:02 192.168.122.209 [63232.758746] [tdb] Close table 'sessions0.tdb' Apr 26 09:38:02 192.168.122.209 [63233.009721] [tdb] Close table 'filter0.tdb' Apr 26 09:38:02 192.168.122.209 [63233.010133] [tempesta fw] modules are stopped Apr 26 09:38:02 192.168.122.209 [63233.215771] [tempesta fw] exiting... Apr 26 09:38:02 192.168.122.209 [63233.345081] [tdb] Shutdown Tempesta DB Apr 26 09:38:02 192.168.122.209 [63233.513821] End test: t_frang.test_header_cnt.FrangHttpHeaderCountTestCase.test_default_http_header_cnt Apr 26 09:38:02 192.168.122.209 [63233.524174] Start test: t_frang.test_header_cnt.FrangHttpHeaderCountTestCase.test_not_reaching_the_limit Apr 26 09:38:03 192.168.122.209 [63234.558289] [tdb] Start Tempesta DB Apr 26 09:38:04 192.168.122.209 [63234.695794] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:38:04 192.168.122.209 [63235.542678] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63235.542678] Maybe that's fine, but it's worth checking the [63235.542678] config - if there is no relations between the [63235.542678] names, then host name confusion attack is possible. Apr 26 09:38:05 192.168.122.209 [63235.665775] [tempesta fw] Configuration processing is completed. Apr 26 09:38:05 192.168.122.209 [63235.726516] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:38:05 192.168.122.209 [63235.756516] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:38:05 192.168.122.209 [63235.786342] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:38:05 192.168.122.209 [63235.865374] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:38:05 192.168.122.209 [63235.867056] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:38:05 192.168.122.209 [63235.868718] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:38:05 192.168.122.209 [63235.913376] [tempesta fw] Tempesta FW is ready Apr 26 09:38:05 192.168.122.209 [63236.554541] [tdb] Close table 'client0.tdb' Apr 26 09:38:06 192.168.122.209 [63236.741818] [tdb] Close table 'sessions0.tdb' Apr 26 09:38:06 192.168.122.209 [63236.972193] [tdb] Close table 'filter0.tdb' Apr 26 09:38:06 192.168.122.209 [63236.972601] [tempesta fw] modules are stopped Apr 26 09:38:06 192.168.122.209 [63237.218768] [tempesta fw] exiting... Apr 26 09:38:06 192.168.122.209 [63237.334664] [tdb] Shutdown Tempesta DB Apr 26 09:38:06 192.168.122.209 [63237.553654] End test: t_frang.test_header_cnt.FrangHttpHeaderCountTestCase.test_not_reaching_the_limit Apr 26 09:38:06 192.168.122.209 [63237.565593] Start test: t_frang.test_header_cnt.FrangHttpHeaderCountTestCase.test_not_reaching_the_limit_2 Apr 26 09:38:07 192.168.122.209 [63238.580224] [tdb] Start Tempesta DB Apr 26 09:38:08 192.168.122.209 [63238.702541] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:38:08 192.168.122.209 [63239.494785] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63239.494785] Maybe that's fine, but it's worth checking the [63239.494785] config - if there is no relations between the [63239.494785] names, then host name confusion attack is possible. Apr 26 09:38:08 192.168.122.209 [63239.597480] [tempesta fw] Configuration processing is completed. Apr 26 09:38:09 192.168.122.209 [63239.651805] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:38:09 192.168.122.209 [63239.684549] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:38:09 192.168.122.209 [63239.715285] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:38:09 192.168.122.209 [63239.761484] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:38:09 192.168.122.209 [63239.763159] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:38:09 192.168.122.209 [63239.764808] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:38:09 192.168.122.209 [63239.801421] [tempesta fw] Tempesta FW is ready Apr 26 09:38:09 192.168.122.209 [63240.425044] [tdb] Close table 'client0.tdb' Apr 26 09:38:10 192.168.122.209 [63240.613856] [tdb] Close table 'sessions0.tdb' Apr 26 09:38:10 192.168.122.209 [63240.836045] [tdb] Close table 'filter0.tdb' Apr 26 09:38:10 192.168.122.209 [63240.836465] [tempesta fw] modules are stopped Apr 26 09:38:10 192.168.122.209 [63241.005633] [tempesta fw] exiting... Apr 26 09:38:10 192.168.122.209 [63241.126043] [tdb] Shutdown Tempesta DB Apr 26 09:38:10 192.168.122.209 [63241.344566] End test: t_frang.test_header_cnt.FrangHttpHeaderCountTestCase.test_not_reaching_the_limit_2 Apr 26 09:38:10 192.168.122.209 [63241.358203] Start test: t_frang.test_header_cnt.FrangHttpHeaderCountTestCase.test_reaching_the_limit Apr 26 09:38:11 192.168.122.209 [63242.441944] [tdb] Start Tempesta DB Apr 26 09:38:11 192.168.122.209 [63242.574885] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:38:12 192.168.122.209 [63243.422856] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63243.422856] Maybe that's fine, but it's worth checking the [63243.422856] config - if there is no relations between the [63243.422856] names, then host name confusion attack is possible. Apr 26 09:38:12 192.168.122.209 [63243.533550] [tempesta fw] Configuration processing is completed. Apr 26 09:38:12 192.168.122.209 [63243.590780] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:38:13 192.168.122.209 [63243.618686] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:38:13 192.168.122.209 [63243.646329] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:38:13 192.168.122.209 [63243.685524] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:38:13 192.168.122.209 [63243.687199] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:38:13 192.168.122.209 [63243.688841] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:38:13 192.168.122.209 [63243.729466] [tempesta fw] Tempesta FW is ready Apr 26 09:38:13 192.168.122.209 [63243.868276] [tempesta fw] Warning: frang: HTTP headers count exceeded for 127.0.0.2: 3 (lim=2) Apr 26 09:38:13 192.168.122.209 [63244.366454] [tdb] Close table 'client0.tdb' Apr 26 09:38:13 192.168.122.209 [63244.552418] [tdb] Close table 'sessions0.tdb' Apr 26 09:38:14 192.168.122.209 [63244.778793] [tdb] Close table 'filter0.tdb' Apr 26 09:38:14 192.168.122.209 [63244.779216] [tempesta fw] modules are stopped Apr 26 09:38:14 192.168.122.209 [63244.941741] [tempesta fw] exiting... Apr 26 09:38:14 192.168.122.209 [63245.074013] [tdb] Shutdown Tempesta DB Apr 26 09:38:14 192.168.122.209 [63245.284479] End test: t_frang.test_header_cnt.FrangHttpHeaderCountTestCase.test_reaching_the_limit Apr 26 09:38:14 192.168.122.209 [63245.294397] Start test: t_frang.test_http_ct_required.FrangHttpCtRequiredH2.test_content_type_set_ok Apr 26 09:38:15 192.168.122.209 [63246.354806] [tdb] Start Tempesta DB Apr 26 09:38:15 192.168.122.209 [63246.482169] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:38:16 192.168.122.209 [63247.378814] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63247.378814] Maybe that's fine, but it's worth checking the [63247.378814] config - if there is no relations between the [63247.378814] names, then host name confusion attack is possible. Apr 26 09:38:16 192.168.122.209 [63247.481614] [tempesta fw] Configuration processing is completed. Apr 26 09:38:16 192.168.122.209 [63247.538508] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:38:16 192.168.122.209 [63247.570046] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:38:16 192.168.122.209 [63247.600305] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:38:17 192.168.122.209 [63247.649680] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:38:17 192.168.122.209 [63247.651408] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:38:17 192.168.122.209 [63247.653173] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:38:17 192.168.122.209 [63247.689521] [tempesta fw] Tempesta FW is ready Apr 26 09:38:17 192.168.122.209 [63248.475034] [tdb] Close table 'client0.tdb' Apr 26 09:38:18 192.168.122.209 [63248.678326] [tdb] Close table 'sessions0.tdb' Apr 26 09:38:18 192.168.122.209 [63248.889175] [tdb] Close table 'filter0.tdb' Apr 26 09:38:18 192.168.122.209 [63248.889633] [tempesta fw] modules are stopped Apr 26 09:38:18 192.168.122.209 [63249.078430] [tempesta fw] exiting... Apr 26 09:38:18 192.168.122.209 [63249.217021] [tdb] Shutdown Tempesta DB Apr 26 09:38:18 192.168.122.209 [63249.430030] End test: t_frang.test_http_ct_required.FrangHttpCtRequiredH2.test_content_type_set_ok Apr 26 09:38:18 192.168.122.209 [63249.446400] Start test: t_frang.test_http_ct_required.FrangHttpCtRequiredH2.test_default_http_ct_required Apr 26 09:38:19 192.168.122.209 [63250.508689] [tdb] Start Tempesta DB Apr 26 09:38:20 192.168.122.209 [63250.640929] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:38:20 192.168.122.209 [63251.450962] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63251.450962] Maybe that's fine, but it's worth checking the [63251.450962] config - if there is no relations between the [63251.450962] names, then host name confusion attack is possible. Apr 26 09:38:20 192.168.122.209 [63251.557658] [tempesta fw] Configuration processing is completed. Apr 26 09:38:21 192.168.122.209 [63251.615337] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:38:21 192.168.122.209 [63251.647793] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:38:21 192.168.122.209 [63251.679711] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:38:21 192.168.122.209 [63251.729628] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:38:21 192.168.122.209 [63251.731296] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:38:21 192.168.122.209 [63251.733039] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:38:21 192.168.122.209 [63251.769573] [tempesta fw] Tempesta FW is ready Apr 26 09:38:21 192.168.122.209 [63252.386627] [tdb] Close table 'client0.tdb' Apr 26 09:38:21 192.168.122.209 [63252.582920] [tdb] Close table 'sessions0.tdb' Apr 26 09:38:22 192.168.122.209 [63252.822043] [tdb] Close table 'filter0.tdb' Apr 26 09:38:22 192.168.122.209 [63252.822464] [tempesta fw] modules are stopped Apr 26 09:38:22 192.168.122.209 [63253.014945] [tempesta fw] exiting... Apr 26 09:38:22 192.168.122.209 [63253.161123] [tdb] Shutdown Tempesta DB Apr 26 09:38:22 192.168.122.209 [63253.368613] End test: t_frang.test_http_ct_required.FrangHttpCtRequiredH2.test_default_http_ct_required Apr 26 09:38:22 192.168.122.209 [63253.383325] Start test: t_frang.test_http_ct_required.FrangHttpCtRequiredH2.test_missing_content_type Apr 26 09:38:23 192.168.122.209 [63254.421036] [tdb] Start Tempesta DB Apr 26 09:38:23 192.168.122.209 [63254.552925] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:38:24 192.168.122.209 [63255.338936] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63255.338936] Maybe that's fine, but it's worth checking the [63255.338936] config - if there is no relations between the [63255.338936] names, then host name confusion attack is possible. Apr 26 09:38:24 192.168.122.209 [63255.445716] [tempesta fw] Configuration processing is completed. Apr 26 09:38:24 192.168.122.209 [63255.497388] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:38:24 192.168.122.209 [63255.525652] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:38:24 192.168.122.209 [63255.564495] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:38:25 192.168.122.209 [63255.609682] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:38:25 192.168.122.209 [63255.611349] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:38:25 192.168.122.209 [63255.613005] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:38:25 192.168.122.209 [63255.649621] [tempesta fw] Tempesta FW is ready Apr 26 09:38:25 192.168.122.209 [63255.839592] [tempesta fw] Warning: frang: Content-Type header field for 127.0.0.2 is missed Apr 26 09:38:25 192.168.122.209 [63255.841456] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 09:38:25 192.168.122.209 [63256.345872] [tdb] Close table 'client0.tdb' Apr 26 09:38:25 192.168.122.209 [63256.534328] [tdb] Close table 'sessions0.tdb' Apr 26 09:38:26 192.168.122.209 [63256.772565] [tdb] Close table 'filter0.tdb' Apr 26 09:38:26 192.168.122.209 [63256.772995] [tempesta fw] modules are stopped Apr 26 09:38:26 192.168.122.209 [63256.951150] [tempesta fw] exiting... Apr 26 09:38:26 192.168.122.209 [63257.095537] [tdb] Shutdown Tempesta DB Apr 26 09:38:26 192.168.122.209 [63257.320528] End test: t_frang.test_http_ct_required.FrangHttpCtRequiredH2.test_missing_content_type Apr 26 09:38:26 192.168.122.209 [63257.329648] Start test: t_frang.test_http_ct_required.FrangHttpCtRequiredTestCase.test_content_type_set_ok Apr 26 09:38:27 192.168.122.209 [63258.381204] [tdb] Start Tempesta DB Apr 26 09:38:27 192.168.122.209 [63258.514943] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:38:28 192.168.122.209 [63259.307041] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63259.307041] Maybe that's fine, but it's worth checking the [63259.307041] config - if there is no relations between the [63259.307041] names, then host name confusion attack is possible. Apr 26 09:38:28 192.168.122.209 [63259.409782] [tempesta fw] Configuration processing is completed. Apr 26 09:38:28 192.168.122.209 [63259.469463] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:38:28 192.168.122.209 [63259.502213] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:38:28 192.168.122.209 [63259.532705] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:38:28 192.168.122.209 [63259.593738] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:38:28 192.168.122.209 [63259.595465] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:38:28 192.168.122.209 [63259.597104] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:38:29 192.168.122.209 [63259.641684] [tempesta fw] Tempesta FW is ready Apr 26 09:38:29 192.168.122.209 [63260.312291] [tdb] Close table 'client0.tdb' Apr 26 09:38:29 192.168.122.209 [63260.513289] [tdb] Close table 'sessions0.tdb' Apr 26 09:38:30 192.168.122.209 [63260.748079] [tdb] Close table 'filter0.tdb' Apr 26 09:38:30 192.168.122.209 [63260.748524] [tempesta fw] modules are stopped Apr 26 09:38:30 192.168.122.209 [63260.979348] [tempesta fw] exiting... Apr 26 09:38:30 192.168.122.209 [63261.124897] [tdb] Shutdown Tempesta DB Apr 26 09:38:30 192.168.122.209 [63261.328770] End test: t_frang.test_http_ct_required.FrangHttpCtRequiredTestCase.test_content_type_set_ok Apr 26 09:38:30 192.168.122.209 [63261.350455] Start test: t_frang.test_http_ct_required.FrangHttpCtRequiredTestCase.test_default_http_ct_required Apr 26 09:38:31 192.168.122.209 [63262.396160] [tdb] Start Tempesta DB Apr 26 09:38:31 192.168.122.209 [63262.520792] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:38:32 192.168.122.209 [63263.351076] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63263.351076] Maybe that's fine, but it's worth checking the [63263.351076] config - if there is no relations between the [63263.351076] names, then host name confusion attack is possible. Apr 26 09:38:32 192.168.122.209 [63263.469820] [tempesta fw] Configuration processing is completed. Apr 26 09:38:32 192.168.122.209 [63263.532281] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:38:32 192.168.122.209 [63263.563939] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:38:32 192.168.122.209 [63263.593719] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:38:33 192.168.122.209 [63263.661808] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:38:33 192.168.122.209 [63263.663514] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:38:33 192.168.122.209 [63263.665183] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:38:33 192.168.122.209 [63263.701742] [tempesta fw] Tempesta FW is ready Apr 26 09:38:33 192.168.122.209 [63264.376170] [tdb] Close table 'client0.tdb' Apr 26 09:38:33 192.168.122.209 [63264.574311] [tdb] Close table 'sessions0.tdb' Apr 26 09:38:34 192.168.122.209 [63264.809104] [tdb] Close table 'filter0.tdb' Apr 26 09:38:34 192.168.122.209 [63264.809548] [tempesta fw] modules are stopped Apr 26 09:38:34 192.168.122.209 [63265.023264] [tempesta fw] exiting... Apr 26 09:38:34 192.168.122.209 [63265.134950] [tdb] Shutdown Tempesta DB Apr 26 09:38:34 192.168.122.209 [63265.361084] End test: t_frang.test_http_ct_required.FrangHttpCtRequiredTestCase.test_default_http_ct_required Apr 26 09:38:34 192.168.122.209 [63265.376751] Start test: t_frang.test_http_ct_required.FrangHttpCtRequiredTestCase.test_missing_content_type Apr 26 09:38:35 192.168.122.209 [63266.410247] [tdb] Start Tempesta DB Apr 26 09:38:35 192.168.122.209 [63266.540063] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:38:36 192.168.122.209 [63267.291098] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63267.291098] Maybe that's fine, but it's worth checking the [63267.291098] config - if there is no relations between the [63267.291098] names, then host name confusion attack is possible. Apr 26 09:38:36 192.168.122.209 [63267.397840] [tempesta fw] Configuration processing is completed. Apr 26 09:38:36 192.168.122.209 [63267.454009] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:38:36 192.168.122.209 [63267.481837] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:38:36 192.168.122.209 [63267.510512] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:38:36 192.168.122.209 [63267.573820] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:38:36 192.168.122.209 [63267.575496] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:38:36 192.168.122.209 [63267.577200] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:38:37 192.168.122.209 [63267.629771] [tempesta fw] Tempesta FW is ready Apr 26 09:38:37 192.168.122.209 [63267.754816] [tempesta fw] Warning: frang: Content-Type header field for 127.0.0.2 is missed Apr 26 09:38:37 192.168.122.209 [63267.755581] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 09:38:37 192.168.122.209 [63268.231395] [tdb] Close table 'client0.tdb' Apr 26 09:38:37 192.168.122.209 [63268.432822] [tdb] Close table 'sessions0.tdb' Apr 26 09:38:38 192.168.122.209 [63268.667090] [tdb] Close table 'filter0.tdb' Apr 26 09:38:38 192.168.122.209 [63268.667512] [tempesta fw] modules are stopped Apr 26 09:38:38 192.168.122.209 [63268.865509] [tempesta fw] exiting... Apr 26 09:38:38 192.168.122.209 [63268.991002] [tdb] Shutdown Tempesta DB Apr 26 09:38:38 192.168.122.209 [63269.222150] End test: t_frang.test_http_ct_required.FrangHttpCtRequiredTestCase.test_missing_content_type Apr 26 09:38:38 192.168.122.209 [63269.237104] Start test: t_frang.test_http_ct_vals.FrangHttpCtValsH2.test_content_vals_set_ok Apr 26 09:38:39 192.168.122.209 [63270.301231] [tdb] Start Tempesta DB Apr 26 09:38:39 192.168.122.209 [63270.436661] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:38:40 192.168.122.209 [63271.215216] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63271.215216] Maybe that's fine, but it's worth checking the [63271.215216] config - if there is no relations between the [63271.215216] names, then host name confusion attack is possible. Apr 26 09:38:40 192.168.122.209 [63271.317917] [tempesta fw] Configuration processing is completed. Apr 26 09:38:40 192.168.122.209 [63271.375611] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:38:40 192.168.122.209 [63271.408219] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:38:40 192.168.122.209 [63271.440609] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:38:40 192.168.122.209 [63271.497887] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:38:40 192.168.122.209 [63271.499605] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:38:40 192.168.122.209 [63271.501248] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:38:40 192.168.122.209 [63271.553827] [tempesta fw] Tempesta FW is ready Apr 26 09:38:41 192.168.122.209 [63272.315708] [tdb] Close table 'client0.tdb' Apr 26 09:38:41 192.168.122.209 [63272.505519] [tdb] Close table 'sessions0.tdb' Apr 26 09:38:42 192.168.122.209 [63272.759420] [tdb] Close table 'filter0.tdb' Apr 26 09:38:42 192.168.122.209 [63272.759858] [tempesta fw] modules are stopped Apr 26 09:38:42 192.168.122.209 [63272.956053] [tempesta fw] exiting... Apr 26 09:38:42 192.168.122.209 [63273.092360] [tdb] Shutdown Tempesta DB Apr 26 09:38:42 192.168.122.209 [63273.337632] End test: t_frang.test_http_ct_vals.FrangHttpCtValsH2.test_content_vals_set_ok Apr 26 09:38:42 192.168.122.209 [63273.349572] Start test: t_frang.test_http_ct_vals.FrangHttpCtValsH2.test_content_vals_set_ok_conf2 Apr 26 09:38:43 192.168.122.209 [63274.327625] [tdb] Start Tempesta DB Apr 26 09:38:43 192.168.122.209 [63274.461559] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:38:44 192.168.122.209 [63275.331241] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63275.331241] Maybe that's fine, but it's worth checking the [63275.331241] config - if there is no relations between the [63275.331241] names, then host name confusion attack is possible. Apr 26 09:38:44 192.168.122.209 [63275.442020] [tempesta fw] Configuration processing is completed. Apr 26 09:38:44 192.168.122.209 [63275.508094] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:38:44 192.168.122.209 [63275.540846] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:38:44 192.168.122.209 [63275.571442] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:38:45 192.168.122.209 [63275.629932] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:38:45 192.168.122.209 [63275.631599] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:38:45 192.168.122.209 [63275.633233] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:38:45 192.168.122.209 [63275.669875] [tempesta fw] Tempesta FW is ready Apr 26 09:38:45 192.168.122.209 [63276.439231] [tdb] Close table 'client0.tdb' Apr 26 09:38:46 192.168.122.209 [63276.628585] [tdb] Close table 'sessions0.tdb' Apr 26 09:38:46 192.168.122.209 [63276.861103] [tdb] Close table 'filter0.tdb' Apr 26 09:38:46 192.168.122.209 [63276.861553] [tempesta fw] modules are stopped Apr 26 09:38:46 192.168.122.209 [63277.044453] [tempesta fw] exiting... Apr 26 09:38:46 192.168.122.209 [63277.178169] [tdb] Shutdown Tempesta DB Apr 26 09:38:46 192.168.122.209 [63277.374024] End test: t_frang.test_http_ct_vals.FrangHttpCtValsH2.test_content_vals_set_ok_conf2 Apr 26 09:38:46 192.168.122.209 [63277.392607] Start test: t_frang.test_http_ct_vals.FrangHttpCtValsH2.test_default_http_ct_vals Apr 26 09:38:47 192.168.122.209 [63278.517047] [tdb] Start Tempesta DB Apr 26 09:38:48 192.168.122.209 [63278.660384] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:38:48 192.168.122.209 [63279.487229] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63279.487229] Maybe that's fine, but it's worth checking the [63279.487229] config - if there is no relations between the [63279.487229] names, then host name confusion attack is possible. Apr 26 09:38:48 192.168.122.209 [63279.585996] [tempesta fw] Configuration processing is completed. Apr 26 09:38:49 192.168.122.209 [63279.640700] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:38:49 192.168.122.209 [63279.671502] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:38:49 192.168.122.209 [63279.702365] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:38:49 192.168.122.209 [63279.741997] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:38:49 192.168.122.209 [63279.743675] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:38:49 192.168.122.209 [63279.745464] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:38:49 192.168.122.209 [63279.785938] [tempesta fw] Tempesta FW is ready Apr 26 09:38:49 192.168.122.209 [63280.518938] [tdb] Close table 'client0.tdb' Apr 26 09:38:50 192.168.122.209 [63280.687201] [tdb] Close table 'sessions0.tdb' Apr 26 09:38:50 192.168.122.209 [63280.924314] [tdb] Close table 'filter0.tdb' Apr 26 09:38:50 192.168.122.209 [63280.924747] [tempesta fw] modules are stopped Apr 26 09:38:50 192.168.122.209 [63281.093847] [tempesta fw] exiting... Apr 26 09:38:50 192.168.122.209 [63281.227450] [tdb] Shutdown Tempesta DB Apr 26 09:38:50 192.168.122.209 [63281.449272] End test: t_frang.test_http_ct_vals.FrangHttpCtValsH2.test_default_http_ct_vals Apr 26 09:38:50 192.168.122.209 [63281.463236] Start test: t_frang.test_http_ct_vals.FrangHttpCtValsH2.test_error_content_type Apr 26 09:38:51 192.168.122.209 [63282.510542] [tdb] Start Tempesta DB Apr 26 09:38:52 192.168.122.209 [63282.649744] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:38:52 192.168.122.209 [63283.467305] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63283.467305] Maybe that's fine, but it's worth checking the [63283.467305] config - if there is no relations between the [63283.467305] names, then host name confusion attack is possible. Apr 26 09:38:52 192.168.122.209 [63283.570078] [tempesta fw] Configuration processing is completed. Apr 26 09:38:53 192.168.122.209 [63283.629228] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:38:53 192.168.122.209 [63283.661567] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:38:53 192.168.122.209 [63283.692042] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:38:53 192.168.122.209 [63283.750045] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:38:53 192.168.122.209 [63283.751742] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:38:53 192.168.122.209 [63283.753410] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:38:53 192.168.122.209 [63283.789979] [tempesta fw] Tempesta FW is ready Apr 26 09:38:53 192.168.122.209 [63283.987195] [tempesta fw] Warning: frang: restricted Content-Type for 127.0.0.2: text/ Apr 26 09:38:53 192.168.122.209 [63283.987920] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 09:38:53 192.168.122.209 [63284.479927] [tdb] Close table 'client0.tdb' Apr 26 09:38:54 192.168.122.209 [63284.671161] [tdb] Close table 'sessions0.tdb' Apr 26 09:38:54 192.168.122.209 [63284.902061] [tdb] Close table 'filter0.tdb' Apr 26 09:38:54 192.168.122.209 [63284.902491] [tempesta fw] modules are stopped Apr 26 09:38:54 192.168.122.209 [63285.174719] [tempesta fw] exiting... Apr 26 09:38:54 192.168.122.209 [63285.278986] [tdb] Shutdown Tempesta DB Apr 26 09:38:54 192.168.122.209 [63285.521226] End test: t_frang.test_http_ct_vals.FrangHttpCtValsH2.test_error_content_type Apr 26 09:38:54 192.168.122.209 [63285.543349] Start test: t_frang.test_http_ct_vals.FrangHttpCtValsH2.test_error_content_type2 Apr 26 09:38:56 192.168.122.209 [63286.635761] [tdb] Start Tempesta DB Apr 26 09:38:56 192.168.122.209 [63286.767930] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:38:57 192.168.122.209 [63287.623066] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63287.623066] Maybe that's fine, but it's worth checking the [63287.623066] config - if there is no relations between the [63287.623066] names, then host name confusion attack is possible. Apr 26 09:38:57 192.168.122.209 [63287.714068] [tempesta fw] Configuration processing is completed. Apr 26 09:38:57 192.168.122.209 [63287.769516] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:38:57 192.168.122.209 [63287.801117] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:38:57 192.168.122.209 [63287.831335] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:38:57 192.168.122.209 [63287.882102] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:38:57 192.168.122.209 [63287.883802] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:38:57 192.168.122.209 [63287.885440] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:38:57 192.168.122.209 [63287.921983] [tempesta fw] Tempesta FW is ready Apr 26 09:38:57 192.168.122.209 [63288.100121] [tempesta fw] Warning: frang: restricted Content-Type for 127.0.0.2: text/ Apr 26 09:38:57 192.168.122.209 [63288.101552] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 09:38:58 192.168.122.209 [63288.602144] [tdb] Close table 'client0.tdb' Apr 26 09:38:58 192.168.122.209 [63288.815518] [tdb] Close table 'sessions0.tdb' Apr 26 09:38:58 192.168.122.209 [63289.045199] [tdb] Close table 'filter0.tdb' Apr 26 09:38:58 192.168.122.209 [63289.045628] [tempesta fw] modules are stopped Apr 26 09:38:58 192.168.122.209 [63289.259367] [tempesta fw] exiting... Apr 26 09:38:58 192.168.122.209 [63289.366772] [tdb] Shutdown Tempesta DB Apr 26 09:38:58 192.168.122.209 [63289.584996] End test: t_frang.test_http_ct_vals.FrangHttpCtValsH2.test_error_content_type2 Apr 26 09:38:59 192.168.122.209 [63289.607177] Start test: t_frang.test_http_ct_vals.FrangHttpCtValsH2.test_missing_content_type Apr 26 09:39:00 192.168.122.209 [63290.715168] [tdb] Start Tempesta DB Apr 26 09:39:00 192.168.122.209 [63290.849491] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:39:01 192.168.122.209 [63291.651420] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63291.651420] Maybe that's fine, but it's worth checking the [63291.651420] config - if there is no relations between the [63291.651420] names, then host name confusion attack is possible. Apr 26 09:39:01 192.168.122.209 [63291.754422] [tempesta fw] Configuration processing is completed. Apr 26 09:39:01 192.168.122.209 [63291.810870] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:39:01 192.168.122.209 [63291.841052] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:39:01 192.168.122.209 [63291.872644] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:39:01 192.168.122.209 [63291.926141] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:39:01 192.168.122.209 [63291.927500] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:39:01 192.168.122.209 [63291.928976] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:39:01 192.168.122.209 [63291.970123] [tempesta fw] Tempesta FW is ready Apr 26 09:39:01 192.168.122.209 [63292.166914] [tempesta fw] Warning: frang: Content-Type header field for 127.0.0.2 is missed Apr 26 09:39:01 192.168.122.209 [63292.167709] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 09:39:02 192.168.122.209 [63292.692499] [tdb] Close table 'client0.tdb' Apr 26 09:39:02 192.168.122.209 [63292.872719] [tdb] Close table 'sessions0.tdb' Apr 26 09:39:02 192.168.122.209 [63293.108037] [tdb] Close table 'filter0.tdb' Apr 26 09:39:02 192.168.122.209 [63293.108460] [tempesta fw] modules are stopped Apr 26 09:39:02 192.168.122.209 [63293.273854] [tempesta fw] exiting... Apr 26 09:39:02 192.168.122.209 [63293.386971] [tdb] Shutdown Tempesta DB Apr 26 09:39:03 192.168.122.209 [63293.615685] End test: t_frang.test_http_ct_vals.FrangHttpCtValsH2.test_missing_content_type Apr 26 09:39:03 192.168.122.209 [63293.630783] Start test: t_frang.test_http_ct_vals.FrangHttpCtValsTestCase.test_content_vals_set_ok Apr 26 09:39:04 192.168.122.209 [63294.649281] [tdb] Start Tempesta DB Apr 26 09:39:04 192.168.122.209 [63294.788024] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:39:04 192.168.122.209 [63295.587487] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63295.587487] Maybe that's fine, but it's worth checking the [63295.587487] config - if there is no relations between the [63295.587487] names, then host name confusion attack is possible. Apr 26 09:39:05 192.168.122.209 [63295.686309] [tempesta fw] Configuration processing is completed. Apr 26 09:39:05 192.168.122.209 [63295.741484] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:39:05 192.168.122.209 [63295.772240] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:39:05 192.168.122.209 [63295.802204] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:39:05 192.168.122.209 [63295.866209] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:39:05 192.168.122.209 [63295.867926] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:39:05 192.168.122.209 [63295.869570] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:39:05 192.168.122.209 [63295.918155] [tempesta fw] Tempesta FW is ready Apr 26 09:39:05 192.168.122.209 [63296.580536] [tdb] Close table 'client0.tdb' Apr 26 09:39:06 192.168.122.209 [63296.767732] [tdb] Close table 'sessions0.tdb' Apr 26 09:39:06 192.168.122.209 [63297.004167] [tdb] Close table 'filter0.tdb' Apr 26 09:39:06 192.168.122.209 [63297.004605] [tempesta fw] modules are stopped Apr 26 09:39:06 192.168.122.209 [63297.221478] [tempesta fw] exiting... Apr 26 09:39:06 192.168.122.209 [63297.339083] [tdb] Shutdown Tempesta DB Apr 26 09:39:06 192.168.122.209 [63297.547497] End test: t_frang.test_http_ct_vals.FrangHttpCtValsTestCase.test_content_vals_set_ok Apr 26 09:39:06 192.168.122.209 [63297.559595] Start test: t_frang.test_http_ct_vals.FrangHttpCtValsTestCase.test_content_vals_set_ok_conf2 Apr 26 09:39:08 192.168.122.209 [63298.692028] [tdb] Start Tempesta DB Apr 26 09:39:08 192.168.122.209 [63298.812331] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:39:09 192.168.122.209 [63299.647481] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63299.647481] Maybe that's fine, but it's worth checking the [63299.647481] config - if there is no relations between the [63299.647481] names, then host name confusion attack is possible. Apr 26 09:39:09 192.168.122.209 [63299.758260] [tempesta fw] Configuration processing is completed. Apr 26 09:39:09 192.168.122.209 [63299.809969] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:39:09 192.168.122.209 [63299.838416] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:39:09 192.168.122.209 [63299.866514] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:39:09 192.168.122.209 [63299.922239] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:39:09 192.168.122.209 [63299.923919] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:39:09 192.168.122.209 [63299.925722] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:39:09 192.168.122.209 [63299.966182] [tempesta fw] Tempesta FW is ready Apr 26 09:39:10 192.168.122.209 [63300.622856] [tdb] Close table 'client0.tdb' Apr 26 09:39:10 192.168.122.209 [63300.811610] [tdb] Close table 'sessions0.tdb' Apr 26 09:39:10 192.168.122.209 [63301.060229] [tdb] Close table 'filter0.tdb' Apr 26 09:39:10 192.168.122.209 [63301.060662] [tempesta fw] modules are stopped Apr 26 09:39:10 192.168.122.209 [63301.255645] [tempesta fw] exiting... Apr 26 09:39:10 192.168.122.209 [63301.378429] [tdb] Shutdown Tempesta DB Apr 26 09:39:10 192.168.122.209 [63301.588574] End test: t_frang.test_http_ct_vals.FrangHttpCtValsTestCase.test_content_vals_set_ok_conf2 Apr 26 09:39:11 192.168.122.209 [63301.601510] Start test: t_frang.test_http_ct_vals.FrangHttpCtValsTestCase.test_default_http_ct_vals Apr 26 09:39:12 192.168.122.209 [63302.623281] [tdb] Start Tempesta DB Apr 26 09:39:12 192.168.122.209 [63302.760878] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:39:12 192.168.122.209 [63303.567574] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63303.567574] Maybe that's fine, but it's worth checking the [63303.567574] config - if there is no relations between the [63303.567574] names, then host name confusion attack is possible. Apr 26 09:39:13 192.168.122.209 [63303.670334] [tempesta fw] Configuration processing is completed. Apr 26 09:39:13 192.168.122.209 [63303.741060] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:39:13 192.168.122.209 [63303.772058] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:39:13 192.168.122.209 [63303.802531] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:39:13 192.168.122.209 [63303.862301] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:39:13 192.168.122.209 [63303.863988] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:39:13 192.168.122.209 [63303.865636] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:39:13 192.168.122.209 [63303.914231] [tempesta fw] Tempesta FW is ready Apr 26 09:39:13 192.168.122.209 [63304.567097] [tdb] Close table 'client0.tdb' Apr 26 09:39:14 192.168.122.209 [63304.743247] [tdb] Close table 'sessions0.tdb' Apr 26 09:39:14 192.168.122.209 [63304.957141] [tdb] Close table 'filter0.tdb' Apr 26 09:39:14 192.168.122.209 [63304.957566] [tempesta fw] modules are stopped Apr 26 09:39:14 192.168.122.209 [63305.143825] [tempesta fw] exiting... Apr 26 09:39:14 192.168.122.209 [63305.250436] [tdb] Shutdown Tempesta DB Apr 26 09:39:14 192.168.122.209 [63305.457850] End test: t_frang.test_http_ct_vals.FrangHttpCtValsTestCase.test_default_http_ct_vals Apr 26 09:39:14 192.168.122.209 [63305.471540] Start test: t_frang.test_http_ct_vals.FrangHttpCtValsTestCase.test_error_content_type Apr 26 09:39:15 192.168.122.209 [63306.578778] [tdb] Start Tempesta DB Apr 26 09:39:16 192.168.122.209 [63306.725550] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:39:16 192.168.122.209 [63307.535644] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63307.535644] Maybe that's fine, but it's worth checking the [63307.535644] config - if there is no relations between the [63307.535644] names, then host name confusion attack is possible. Apr 26 09:39:17 192.168.122.209 [63307.638386] [tempesta fw] Configuration processing is completed. Apr 26 09:39:17 192.168.122.209 [63307.696050] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:39:17 192.168.122.209 [63307.728719] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:39:17 192.168.122.209 [63307.759776] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:39:17 192.168.122.209 [63307.834354] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:39:17 192.168.122.209 [63307.836055] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:39:17 192.168.122.209 [63307.837684] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:39:17 192.168.122.209 [63307.894325] [tempesta fw] Tempesta FW is ready Apr 26 09:39:17 192.168.122.209 [63308.040408] [tempesta fw] Warning: frang: restricted Content-Type for 127.0.0.2: t Apr 26 09:39:17 192.168.122.209 [63308.042523] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 09:39:17 192.168.122.209 [63308.550787] [tdb] Close table 'client0.tdb' Apr 26 09:39:18 192.168.122.209 [63308.741016] [tdb] Close table 'sessions0.tdb' Apr 26 09:39:18 192.168.122.209 [63308.957388] [tdb] Close table 'filter0.tdb' Apr 26 09:39:18 192.168.122.209 [63308.957828] [tempesta fw] modules are stopped Apr 26 09:39:18 192.168.122.209 [63309.154043] [tempesta fw] exiting... Apr 26 09:39:18 192.168.122.209 [63309.301397] [tdb] Shutdown Tempesta DB Apr 26 09:39:18 192.168.122.209 [63309.508835] End test: t_frang.test_http_ct_vals.FrangHttpCtValsTestCase.test_error_content_type Apr 26 09:39:18 192.168.122.209 [63309.521546] Start test: t_frang.test_http_ct_vals.FrangHttpCtValsTestCase.test_error_content_type2 Apr 26 09:39:19 192.168.122.209 [63310.564747] [tdb] Start Tempesta DB Apr 26 09:39:20 192.168.122.209 [63310.712129] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:39:20 192.168.122.209 [63311.567677] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63311.567677] Maybe that's fine, but it's worth checking the [63311.567677] config - if there is no relations between the [63311.567677] names, then host name confusion attack is possible. Apr 26 09:39:21 192.168.122.209 [63311.686441] [tempesta fw] Configuration processing is completed. Apr 26 09:39:21 192.168.122.209 [63311.739450] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:39:21 192.168.122.209 [63311.772624] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:39:21 192.168.122.209 [63311.803819] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:39:21 192.168.122.209 [63311.866388] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:39:21 192.168.122.209 [63311.868090] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:39:21 192.168.122.209 [63311.869755] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:39:21 192.168.122.209 [63311.906365] [tempesta fw] Tempesta FW is ready Apr 26 09:39:21 192.168.122.209 [63312.045395] [tempesta fw] Warning: frang: restricted Content-Type for 127.0.0.2: t Apr 26 09:39:21 192.168.122.209 [63312.046813] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 09:39:21 192.168.122.209 [63312.527990] [tdb] Close table 'client0.tdb' Apr 26 09:39:22 192.168.122.209 [63312.714557] [tdb] Close table 'sessions0.tdb' Apr 26 09:39:22 192.168.122.209 [63312.953991] [tdb] Close table 'filter0.tdb' Apr 26 09:39:22 192.168.122.209 [63312.954445] [tempesta fw] modules are stopped Apr 26 09:39:22 192.168.122.209 [63313.151819] [tempesta fw] exiting... Apr 26 09:39:22 192.168.122.209 [63313.265880] [tdb] Shutdown Tempesta DB Apr 26 09:39:22 192.168.122.209 [63313.488950] End test: t_frang.test_http_ct_vals.FrangHttpCtValsTestCase.test_error_content_type2 Apr 26 09:39:22 192.168.122.209 [63313.517066] Start test: t_frang.test_http_ct_vals.FrangHttpCtValsTestCase.test_missing_content_type Apr 26 09:39:23 192.168.122.209 [63314.534163] [tdb] Start Tempesta DB Apr 26 09:39:24 192.168.122.209 [63314.662567] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:39:24 192.168.122.209 [63315.491681] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63315.491681] Maybe that's fine, but it's worth checking the [63315.491681] config - if there is no relations between the [63315.491681] names, then host name confusion attack is possible. Apr 26 09:39:24 192.168.122.209 [63315.590502] [tempesta fw] Configuration processing is completed. Apr 26 09:39:25 192.168.122.209 [63315.664723] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:39:25 192.168.122.209 [63315.692519] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:39:25 192.168.122.209 [63315.720199] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:39:25 192.168.122.209 [63315.778439] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:39:25 192.168.122.209 [63315.780153] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:39:25 192.168.122.209 [63315.781823] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:39:25 192.168.122.209 [63315.826426] [tempesta fw] Tempesta FW is ready Apr 26 09:39:25 192.168.122.209 [63315.981744] [tempesta fw] Warning: frang: Content-Type header field for 127.0.0.2 is missed Apr 26 09:39:25 192.168.122.209 [63315.983028] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 09:39:25 192.168.122.209 [63316.441825] [tdb] Close table 'client0.tdb' Apr 26 09:39:26 192.168.122.209 [63316.627855] [tdb] Close table 'sessions0.tdb' Apr 26 09:39:26 192.168.122.209 [63316.855116] [tdb] Close table 'filter0.tdb' Apr 26 09:39:26 192.168.122.209 [63316.855527] [tempesta fw] modules are stopped Apr 26 09:39:26 192.168.122.209 [63317.069700] [tempesta fw] exiting... Apr 26 09:39:26 192.168.122.209 [63317.177066] [tdb] Shutdown Tempesta DB Apr 26 09:39:26 192.168.122.209 [63317.422767] End test: t_frang.test_http_ct_vals.FrangHttpCtValsTestCase.test_missing_content_type Apr 26 09:39:26 192.168.122.209 [63317.437196] Start test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideH2.test_accepted_request Apr 26 09:39:27 192.168.122.209 [63318.473686] [tdb] Start Tempesta DB Apr 26 09:39:27 192.168.122.209 [63318.600824] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:39:28 192.168.122.209 [63319.359784] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63319.359784] Maybe that's fine, but it's worth checking the [63319.359784] config - if there is no relations between the [63319.359784] names, then host name confusion attack is possible. Apr 26 09:39:28 192.168.122.209 [63319.466655] [tempesta fw] Configuration processing is completed. Apr 26 09:39:28 192.168.122.209 [63319.523846] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:39:28 192.168.122.209 [63319.556267] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:39:28 192.168.122.209 [63319.586514] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:39:29 192.168.122.209 [63319.630486] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:39:29 192.168.122.209 [63319.632180] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:39:29 192.168.122.209 [63319.633846] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:39:29 192.168.122.209 [63319.670444] [tempesta fw] Tempesta FW is ready Apr 26 09:39:30 192.168.122.209 [63320.616967] [tdb] Close table 'client0.tdb' Apr 26 09:39:30 192.168.122.209 [63320.795096] [tdb] Close table 'sessions0.tdb' Apr 26 09:39:30 192.168.122.209 [63321.025778] [tdb] Close table 'filter0.tdb' Apr 26 09:39:30 192.168.122.209 [63321.026169] [tempesta fw] modules are stopped Apr 26 09:39:30 192.168.122.209 [63321.238416] [tempesta fw] exiting... Apr 26 09:39:30 192.168.122.209 [63321.375682] [tdb] Shutdown Tempesta DB Apr 26 09:39:30 192.168.122.209 [63321.566394] End test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideH2.test_accepted_request Apr 26 09:39:30 192.168.122.209 [63321.578814] Start test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideH2.test_default_http_method_override_allowed Apr 26 09:39:31 192.168.122.209 [63322.529777] [tdb] Start Tempesta DB Apr 26 09:39:32 192.168.122.209 [63322.660246] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:39:32 192.168.122.209 [63323.395803] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63323.395803] Maybe that's fine, but it's worth checking the [63323.395803] config - if there is no relations between the [63323.395803] names, then host name confusion attack is possible. Apr 26 09:39:32 192.168.122.209 [63323.506578] [tempesta fw] Configuration processing is completed. Apr 26 09:39:32 192.168.122.209 [63323.572962] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:39:32 192.168.122.209 [63323.599477] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:39:33 192.168.122.209 [63323.628693] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:39:33 192.168.122.209 [63323.674531] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:39:33 192.168.122.209 [63323.676214] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:39:33 192.168.122.209 [63323.677928] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:39:33 192.168.122.209 [63323.742521] [tempesta fw] Tempesta FW is ready Apr 26 09:39:33 192.168.122.209 [63323.888399] [tempesta fw] Warning: frang: restricted overridden HTTP method for 127.0.0.2: 13 (0x2000u) Apr 26 09:39:33 192.168.122.209 [63323.889247] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 09:39:33 192.168.122.209 [63324.347499] [tdb] Close table 'client0.tdb' Apr 26 09:39:33 192.168.122.209 [63324.583510] [tdb] Close table 'sessions0.tdb' Apr 26 09:39:34 192.168.122.209 [63324.815296] [tdb] Close table 'filter0.tdb' Apr 26 09:39:34 192.168.122.209 [63324.815737] [tempesta fw] modules are stopped Apr 26 09:39:34 192.168.122.209 [63325.009236] [tempesta fw] exiting... Apr 26 09:39:34 192.168.122.209 [63325.127267] [tdb] Shutdown Tempesta DB Apr 26 09:39:34 192.168.122.209 [63325.306548] End test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideH2.test_default_http_method_override_allowed Apr 26 09:39:34 192.168.122.209 [63325.321878] Start test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideH2.test_not_accepted_request_x_http_method Apr 26 09:39:35 192.168.122.209 [63326.405888] [tdb] Start Tempesta DB Apr 26 09:39:35 192.168.122.209 [63326.552203] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:39:36 192.168.122.209 [63327.407876] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63327.407876] Maybe that's fine, but it's worth checking the [63327.407876] config - if there is no relations between the [63327.407876] names, then host name confusion attack is possible. Apr 26 09:39:36 192.168.122.209 [63327.510967] [tempesta fw] Configuration processing is completed. Apr 26 09:39:36 192.168.122.209 [63327.569314] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:39:36 192.168.122.209 [63327.596920] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:39:37 192.168.122.209 [63327.624521] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:39:37 192.168.122.209 [63327.662593] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:39:37 192.168.122.209 [63327.664271] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:39:37 192.168.122.209 [63327.665901] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:39:37 192.168.122.209 [63327.706580] [tempesta fw] Tempesta FW is ready Apr 26 09:39:37 192.168.122.209 [63327.898103] [tempesta fw] Warning: frang: restricted overridden HTTP method for 127.0.0.2: 8 (0x100u) Apr 26 09:39:37 192.168.122.209 [63327.900551] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 09:39:37 192.168.122.209 [63328.380205] [tdb] Close table 'client0.tdb' Apr 26 09:39:37 192.168.122.209 [63328.569932] [tdb] Close table 'sessions0.tdb' Apr 26 09:39:38 192.168.122.209 [63328.807060] [tdb] Close table 'filter0.tdb' Apr 26 09:39:38 192.168.122.209 [63328.807494] [tempesta fw] modules are stopped Apr 26 09:39:38 192.168.122.209 [63329.023954] [tempesta fw] exiting... Apr 26 09:39:38 192.168.122.209 [63329.147791] [tdb] Shutdown Tempesta DB Apr 26 09:39:38 192.168.122.209 [63329.339535] End test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideH2.test_not_accepted_request_x_http_method Apr 26 09:39:38 192.168.122.209 [63329.349785] Start test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideH2.test_not_accepted_request_x_http_method_override Apr 26 09:39:39 192.168.122.209 [63330.408468] [tdb] Start Tempesta DB Apr 26 09:39:39 192.168.122.209 [63330.544337] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:39:40 192.168.122.209 [63331.375966] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63331.375966] Maybe that's fine, but it's worth checking the [63331.375966] config - if there is no relations between the [63331.375966] names, then host name confusion attack is possible. Apr 26 09:39:40 192.168.122.209 [63331.470686] [tempesta fw] Configuration processing is completed. Apr 26 09:39:40 192.168.122.209 [63331.535806] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:39:40 192.168.122.209 [63331.568326] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:39:40 192.168.122.209 [63331.597358] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:39:41 192.168.122.209 [63331.642660] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:39:41 192.168.122.209 [63331.644346] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:39:41 192.168.122.209 [63331.646058] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:39:41 192.168.122.209 [63331.690502] [tempesta fw] Tempesta FW is ready Apr 26 09:39:41 192.168.122.209 [63331.891044] [tempesta fw] Warning: frang: restricted overridden HTTP method for 127.0.0.2: 8 (0x100u) Apr 26 09:39:41 192.168.122.209 [63331.893117] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 09:39:41 192.168.122.209 [63332.369832] [tdb] Close table 'client0.tdb' Apr 26 09:39:41 192.168.122.209 [63332.580761] [tdb] Close table 'sessions0.tdb' Apr 26 09:39:42 192.168.122.209 [63332.810163] [tdb] Close table 'filter0.tdb' Apr 26 09:39:42 192.168.122.209 [63332.810619] [tempesta fw] modules are stopped Apr 26 09:39:42 192.168.122.209 [63333.072987] [tempesta fw] exiting... Apr 26 09:39:42 192.168.122.209 [63333.186338] [tdb] Shutdown Tempesta DB Apr 26 09:39:42 192.168.122.209 [63333.393804] End test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideH2.test_not_accepted_request_x_http_method_override Apr 26 09:39:42 192.168.122.209 [63333.407925] Start test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideH2.test_not_accepted_request_x_method_override Apr 26 09:39:43 192.168.122.209 [63334.470783] [tdb] Start Tempesta DB Apr 26 09:39:44 192.168.122.209 [63334.613368] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:39:44 192.168.122.209 [63335.467960] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63335.467960] Maybe that's fine, but it's worth checking the [63335.467960] config - if there is no relations between the [63335.467960] names, then host name confusion attack is possible. Apr 26 09:39:44 192.168.122.209 [63335.570706] [tempesta fw] Configuration processing is completed. Apr 26 09:39:45 192.168.122.209 [63335.623971] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:39:45 192.168.122.209 [63335.653315] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:39:45 192.168.122.209 [63335.681797] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:39:45 192.168.122.209 [63335.754764] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:39:45 192.168.122.209 [63335.756425] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:39:45 192.168.122.209 [63335.758067] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:39:45 192.168.122.209 [63335.822652] [tempesta fw] Tempesta FW is ready Apr 26 09:39:45 192.168.122.209 [63335.985665] [tempesta fw] Warning: frang: restricted overridden HTTP method for 127.0.0.2: 8 (0x100u) Apr 26 09:39:45 192.168.122.209 [63335.986523] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 09:39:45 192.168.122.209 [63336.494699] [tdb] Close table 'client0.tdb' Apr 26 09:39:46 192.168.122.209 [63336.671112] [tdb] Close table 'sessions0.tdb' Apr 26 09:39:46 192.168.122.209 [63336.880481] [tdb] Close table 'filter0.tdb' Apr 26 09:39:46 192.168.122.209 [63336.880895] [tempesta fw] modules are stopped Apr 26 09:39:46 192.168.122.209 [63337.098588] [tempesta fw] exiting... Apr 26 09:39:46 192.168.122.209 [63337.223961] [tdb] Shutdown Tempesta DB Apr 26 09:39:46 192.168.122.209 [63337.459393] End test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideH2.test_not_accepted_request_x_method_override Apr 26 09:39:46 192.168.122.209 [63337.475586] Start test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideH2.test_unsafe_override_x_http_method Apr 26 09:39:47 192.168.122.209 [63338.492340] [tdb] Start Tempesta DB Apr 26 09:39:48 192.168.122.209 [63338.616558] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:39:48 192.168.122.209 [63339.472000] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63339.472000] Maybe that's fine, but it's worth checking the [63339.472000] config - if there is no relations between the [63339.472000] names, then host name confusion attack is possible. Apr 26 09:39:48 192.168.122.209 [63339.570789] [tempesta fw] Configuration processing is completed. Apr 26 09:39:49 192.168.122.209 [63339.628185] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:39:49 192.168.122.209 [63339.656991] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:39:49 192.168.122.209 [63339.685929] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:39:49 192.168.122.209 [63339.722819] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:39:49 192.168.122.209 [63339.724502] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:39:49 192.168.122.209 [63339.726142] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:39:49 192.168.122.209 [63339.766694] [tempesta fw] Tempesta FW is ready Apr 26 09:39:49 192.168.122.209 [63339.963713] [tempesta fw] Warning: request dropped: unsafe method override: 127.0.0.2 Apr 26 09:39:49 192.168.122.209 [63340.464365] [tdb] Close table 'client0.tdb' Apr 26 09:39:50 192.168.122.209 [63340.656580] [tdb] Close table 'sessions0.tdb' Apr 26 09:39:50 192.168.122.209 [63340.872890] [tdb] Close table 'filter0.tdb' Apr 26 09:39:50 192.168.122.209 [63340.873322] [tempesta fw] modules are stopped Apr 26 09:39:50 192.168.122.209 [63341.055377] [tempesta fw] exiting... Apr 26 09:39:50 192.168.122.209 [63341.178738] [tdb] Shutdown Tempesta DB Apr 26 09:39:50 192.168.122.209 [63341.402106] End test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideH2.test_unsafe_override_x_http_method Apr 26 09:39:50 192.168.122.209 [63341.422864] Start test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideH2.test_unsafe_override_x_http_method_override Apr 26 09:39:51 192.168.122.209 [63342.469442] [tdb] Start Tempesta DB Apr 26 09:39:52 192.168.122.209 [63342.603003] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:39:52 192.168.122.209 [63343.488103] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63343.488103] Maybe that's fine, but it's worth checking the [63343.488103] config - if there is no relations between the [63343.488103] names, then host name confusion attack is possible. Apr 26 09:39:52 192.168.122.209 [63343.587220] [tempesta fw] Configuration processing is completed. Apr 26 09:39:53 192.168.122.209 [63343.657434] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:39:53 192.168.122.209 [63343.690132] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:39:53 192.168.122.209 [63343.720897] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:39:53 192.168.122.209 [63343.762788] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:39:53 192.168.122.209 [63343.764464] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:39:53 192.168.122.209 [63343.766135] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:39:53 192.168.122.209 [63343.814776] [tempesta fw] Tempesta FW is ready Apr 26 09:39:53 192.168.122.209 [63344.007393] [tempesta fw] Warning: request dropped: unsafe method override: 127.0.0.2 Apr 26 09:39:53 192.168.122.209 [63344.519110] [tdb] Close table 'client0.tdb' Apr 26 09:39:54 192.168.122.209 [63344.707319] [tdb] Close table 'sessions0.tdb' Apr 26 09:39:54 192.168.122.209 [63344.965853] [tdb] Close table 'filter0.tdb' Apr 26 09:39:54 192.168.122.209 [63344.966272] [tempesta fw] modules are stopped Apr 26 09:39:54 192.168.122.209 [63345.140615] [tempesta fw] exiting... Apr 26 09:39:54 192.168.122.209 [63345.284669] [tdb] Shutdown Tempesta DB Apr 26 09:39:54 192.168.122.209 [63345.496739] End test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideH2.test_unsafe_override_x_http_method_override Apr 26 09:39:54 192.168.122.209 [63345.518169] Start test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideH2.test_unsafe_override_x_method_override Apr 26 09:39:56 192.168.122.209 [63346.610520] [tdb] Start Tempesta DB Apr 26 09:39:56 192.168.122.209 [63346.755656] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:39:57 192.168.122.209 [63347.632113] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63347.632113] Maybe that's fine, but it's worth checking the [63347.632113] config - if there is no relations between the [63347.632113] names, then host name confusion attack is possible. Apr 26 09:39:57 192.168.122.209 [63347.738935] [tempesta fw] Configuration processing is completed. Apr 26 09:39:57 192.168.122.209 [63347.791505] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:39:57 192.168.122.209 [63347.819481] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:39:57 192.168.122.209 [63347.847468] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:39:57 192.168.122.209 [63347.906858] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:39:57 192.168.122.209 [63347.908532] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:39:57 192.168.122.209 [63347.910168] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:39:57 192.168.122.209 [63347.946795] [tempesta fw] Tempesta FW is ready Apr 26 09:39:57 192.168.122.209 [63348.100258] [tempesta fw] Warning: request dropped: unsafe method override: 127.0.0.2 Apr 26 09:39:58 192.168.122.209 [63348.633150] [tdb] Close table 'client0.tdb' Apr 26 09:39:58 192.168.122.209 [63348.819730] [tdb] Close table 'sessions0.tdb' Apr 26 09:39:58 192.168.122.209 [63349.070069] [tdb] Close table 'filter0.tdb' Apr 26 09:39:58 192.168.122.209 [63349.070536] [tempesta fw] modules are stopped Apr 26 09:39:58 192.168.122.209 [63349.261697] [tempesta fw] exiting... Apr 26 09:39:58 192.168.122.209 [63349.392956] [tdb] Shutdown Tempesta DB Apr 26 09:39:59 192.168.122.209 [63349.623903] End test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideH2.test_unsafe_override_x_method_override Apr 26 09:39:59 192.168.122.209 [63349.637308] Start test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideTestCase.test_accepted_request Apr 26 09:40:00 192.168.122.209 [63350.749152] [tdb] Start Tempesta DB Apr 26 09:40:00 192.168.122.209 [63350.893893] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:40:01 192.168.122.209 [63351.712210] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63351.712210] Maybe that's fine, but it's worth checking the [63351.712210] config - if there is no relations between the [63351.712210] names, then host name confusion attack is possible. Apr 26 09:40:01 192.168.122.209 [63351.818983] [tempesta fw] Configuration processing is completed. Apr 26 09:40:01 192.168.122.209 [63351.875946] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:40:01 192.168.122.209 [63351.910098] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:40:01 192.168.122.209 [63351.939988] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:40:01 192.168.122.209 [63351.974898] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:40:01 192.168.122.209 [63351.976634] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:40:01 192.168.122.209 [63351.978287] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:40:01 192.168.122.209 [63352.014846] [tempesta fw] Tempesta FW is ready Apr 26 09:40:02 192.168.122.209 [63352.826787] [tdb] Close table 'client0.tdb' Apr 26 09:40:02 192.168.122.209 [63353.024144] [tdb] Close table 'sessions0.tdb' Apr 26 09:40:02 192.168.122.209 [63353.267201] [tdb] Close table 'filter0.tdb' Apr 26 09:40:02 192.168.122.209 [63353.267629] [tempesta fw] modules are stopped Apr 26 09:40:02 192.168.122.209 [63353.439468] [tempesta fw] exiting... Apr 26 09:40:02 192.168.122.209 [63353.590611] [tdb] Shutdown Tempesta DB Apr 26 09:40:03 192.168.122.209 [63353.835832] End test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideTestCase.test_accepted_request Apr 26 09:40:03 192.168.122.209 [63353.844343] Start test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideTestCase.test_default_http_method_override_allowed Apr 26 09:40:04 192.168.122.209 [63354.840304] [tdb] Start Tempesta DB Apr 26 09:40:04 192.168.122.209 [63354.970120] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:40:05 192.168.122.209 [63355.768202] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63355.768202] Maybe that's fine, but it's worth checking the [63355.768202] config - if there is no relations between the [63355.768202] names, then host name confusion attack is possible. Apr 26 09:40:05 192.168.122.209 [63355.866992] [tempesta fw] Configuration processing is completed. Apr 26 09:40:05 192.168.122.209 [63355.924282] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:40:05 192.168.122.209 [63355.957940] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:40:05 192.168.122.209 [63355.987523] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:40:05 192.168.122.209 [63356.030964] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:40:05 192.168.122.209 [63356.032671] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:40:05 192.168.122.209 [63356.034307] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:40:05 192.168.122.209 [63356.070904] [tempesta fw] Tempesta FW is ready Apr 26 09:40:05 192.168.122.209 [63356.224094] [tempesta fw] Warning: frang: restricted overridden HTTP method for 127.0.0.2: 13 (0x2000u) Apr 26 09:40:05 192.168.122.209 [63356.224928] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 09:40:06 192.168.122.209 [63356.690465] [tdb] Close table 'client0.tdb' Apr 26 09:40:06 192.168.122.209 [63356.879968] [tdb] Close table 'sessions0.tdb' Apr 26 09:40:06 192.168.122.209 [63357.125826] [tdb] Close table 'filter0.tdb' Apr 26 09:40:06 192.168.122.209 [63357.126285] [tempesta fw] modules are stopped Apr 26 09:40:06 192.168.122.209 [63357.340425] [tempesta fw] exiting... Apr 26 09:40:06 192.168.122.209 [63357.469686] [tdb] Shutdown Tempesta DB Apr 26 09:40:07 192.168.122.209 [63357.696477] End test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideTestCase.test_default_http_method_override_allowed Apr 26 09:40:07 192.168.122.209 [63357.704139] Start test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideTestCase.test_not_accepted_request_x_http_method Apr 26 09:40:08 192.168.122.209 [63358.788001] [tdb] Start Tempesta DB Apr 26 09:40:08 192.168.122.209 [63358.919793] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:40:09 192.168.122.209 [63359.748323] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63359.748323] Maybe that's fine, but it's worth checking the [63359.748323] config - if there is no relations between the [63359.748323] names, then host name confusion attack is possible. Apr 26 09:40:09 192.168.122.209 [63359.851468] [tempesta fw] Configuration processing is completed. Apr 26 09:40:09 192.168.122.209 [63359.916974] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:40:09 192.168.122.209 [63359.945681] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:40:09 192.168.122.209 [63359.974116] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:40:09 192.168.122.209 [63360.015003] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:40:09 192.168.122.209 [63360.016709] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:40:09 192.168.122.209 [63360.018339] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:40:09 192.168.122.209 [63360.078964] [tempesta fw] Tempesta FW is ready Apr 26 09:40:09 192.168.122.209 [63360.220125] [tempesta fw] Warning: frang: restricted overridden HTTP method for 127.0.0.2: 8 (0x100u) Apr 26 09:40:09 192.168.122.209 [63360.220969] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 09:40:10 192.168.122.209 [63360.681775] [tdb] Close table 'client0.tdb' Apr 26 09:40:10 192.168.122.209 [63360.872246] [tdb] Close table 'sessions0.tdb' Apr 26 09:40:10 192.168.122.209 [63361.106814] [tdb] Close table 'filter0.tdb' Apr 26 09:40:10 192.168.122.209 [63361.107232] [tempesta fw] modules are stopped Apr 26 09:40:10 192.168.122.209 [63361.294480] [tempesta fw] exiting... Apr 26 09:40:10 192.168.122.209 [63361.413294] [tdb] Shutdown Tempesta DB Apr 26 09:40:11 192.168.122.209 [63361.622347] End test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideTestCase.test_not_accepted_request_x_http_method Apr 26 09:40:11 192.168.122.209 [63361.634265] Start test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideTestCase.test_not_accepted_request_x_http_method_override Apr 26 09:40:12 192.168.122.209 [63362.729093] [tdb] Start Tempesta DB Apr 26 09:40:12 192.168.122.209 [63362.855064] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:40:13 192.168.122.209 [63363.688339] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63363.688339] Maybe that's fine, but it's worth checking the [63363.688339] config - if there is no relations between the [63363.688339] names, then host name confusion attack is possible. Apr 26 09:40:13 192.168.122.209 [63363.795087] [tempesta fw] Configuration processing is completed. Apr 26 09:40:13 192.168.122.209 [63363.852754] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:40:13 192.168.122.209 [63363.884400] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:40:13 192.168.122.209 [63363.913219] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:40:13 192.168.122.209 [63363.947055] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:40:13 192.168.122.209 [63363.948749] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:40:13 192.168.122.209 [63363.950416] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:40:13 192.168.122.209 [63363.987001] [tempesta fw] Tempesta FW is ready Apr 26 09:40:13 192.168.122.209 [63364.126357] [tempesta fw] Warning: frang: restricted overridden HTTP method for 127.0.0.2: 8 (0x100u) Apr 26 09:40:13 192.168.122.209 [63364.127225] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 09:40:14 192.168.122.209 [63364.611002] [tdb] Close table 'client0.tdb' Apr 26 09:40:14 192.168.122.209 [63364.797744] [tdb] Close table 'sessions0.tdb' Apr 26 09:40:14 192.168.122.209 [63365.056990] [tdb] Close table 'filter0.tdb' Apr 26 09:40:14 192.168.122.209 [63365.057440] [tempesta fw] modules are stopped Apr 26 09:40:14 192.168.122.209 [63365.250415] [tempesta fw] exiting... Apr 26 09:40:14 192.168.122.209 [63365.349213] [tdb] Shutdown Tempesta DB Apr 26 09:40:14 192.168.122.209 [63365.558396] End test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideTestCase.test_not_accepted_request_x_http_method_override Apr 26 09:40:14 192.168.122.209 [63365.573645] Start test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideTestCase.test_not_accepted_request_x_method_override Apr 26 09:40:16 192.168.122.209 [63366.665630] [tdb] Start Tempesta DB Apr 26 09:40:16 192.168.122.209 [63366.786324] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:40:17 192.168.122.209 [63367.612391] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63367.612391] Maybe that's fine, but it's worth checking the [63367.612391] config - if there is no relations between the [63367.612391] names, then host name confusion attack is possible. Apr 26 09:40:17 192.168.122.209 [63367.715169] [tempesta fw] Configuration processing is completed. Apr 26 09:40:17 192.168.122.209 [63367.799733] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:40:17 192.168.122.209 [63367.830524] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:40:17 192.168.122.209 [63367.859549] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:40:17 192.168.122.209 [63367.903106] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:40:17 192.168.122.209 [63367.904817] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:40:17 192.168.122.209 [63367.906472] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:40:17 192.168.122.209 [63367.943048] [tempesta fw] Tempesta FW is ready Apr 26 09:40:17 192.168.122.209 [63368.086730] [tempesta fw] Warning: frang: restricted overridden HTTP method for 127.0.0.2: 8 (0x100u) Apr 26 09:40:17 192.168.122.209 [63368.087624] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 09:40:17 192.168.122.209 [63368.550016] [tdb] Close table 'client0.tdb' Apr 26 09:40:18 192.168.122.209 [63368.739615] [tdb] Close table 'sessions0.tdb' Apr 26 09:40:18 192.168.122.209 [63368.967347] [tdb] Close table 'filter0.tdb' Apr 26 09:40:18 192.168.122.209 [63368.967768] [tempesta fw] modules are stopped Apr 26 09:40:18 192.168.122.209 [63369.188066] [tempesta fw] exiting... Apr 26 09:40:18 192.168.122.209 [63369.297645] [tdb] Shutdown Tempesta DB Apr 26 09:40:18 192.168.122.209 [63369.478876] End test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideTestCase.test_not_accepted_request_x_method_override Apr 26 09:40:18 192.168.122.209 [63369.493742] Start test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideTestCase.test_unsafe_override_x_http_method Apr 26 09:40:19 192.168.122.209 [63370.531592] [tdb] Start Tempesta DB Apr 26 09:40:20 192.168.122.209 [63370.665864] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:40:20 192.168.122.209 [63371.524412] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63371.524412] Maybe that's fine, but it's worth checking the [63371.524412] config - if there is no relations between the [63371.524412] names, then host name confusion attack is possible. Apr 26 09:40:21 192.168.122.209 [63371.623194] [tempesta fw] Configuration processing is completed. Apr 26 09:40:21 192.168.122.209 [63371.674344] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:40:21 192.168.122.209 [63371.703733] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:40:21 192.168.122.209 [63371.732112] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:40:21 192.168.122.209 [63371.775149] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:40:21 192.168.122.209 [63371.776835] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:40:21 192.168.122.209 [63371.778504] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:40:21 192.168.122.209 [63371.815094] [tempesta fw] Tempesta FW is ready Apr 26 09:40:21 192.168.122.209 [63371.950644] [tempesta fw] Warning: request dropped: unsafe method override: 127.0.0.2 Apr 26 09:40:21 192.168.122.209 [63372.461143] [tdb] Close table 'client0.tdb' Apr 26 09:40:22 192.168.122.209 [63372.648420] [tdb] Close table 'sessions0.tdb' Apr 26 09:40:22 192.168.122.209 [63372.885594] [tdb] Close table 'filter0.tdb' Apr 26 09:40:22 192.168.122.209 [63372.886005] [tempesta fw] modules are stopped Apr 26 09:40:22 192.168.122.209 [63373.107236] [tempesta fw] exiting... Apr 26 09:40:22 192.168.122.209 [63373.215220] [tdb] Shutdown Tempesta DB Apr 26 09:40:22 192.168.122.209 [63373.443133] End test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideTestCase.test_unsafe_override_x_http_method Apr 26 09:40:22 192.168.122.209 [63373.457327] Start test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideTestCase.test_unsafe_override_x_http_method_override Apr 26 09:40:23 192.168.122.209 [63374.550251] [tdb] Start Tempesta DB Apr 26 09:40:24 192.168.122.209 [63374.675626] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:40:24 192.168.122.209 [63375.536441] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63375.536441] Maybe that's fine, but it's worth checking the [63375.536441] config - if there is no relations between the [63375.536441] names, then host name confusion attack is possible. Apr 26 09:40:25 192.168.122.209 [63375.643225] [tempesta fw] Configuration processing is completed. Apr 26 09:40:25 192.168.122.209 [63375.703796] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:40:25 192.168.122.209 [63375.741341] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:40:25 192.168.122.209 [63375.776340] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:40:25 192.168.122.209 [63375.831227] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:40:25 192.168.122.209 [63375.832921] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:40:25 192.168.122.209 [63375.834616] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:40:25 192.168.122.209 [63375.871162] [tempesta fw] Tempesta FW is ready Apr 26 09:40:25 192.168.122.209 [63376.004033] [tempesta fw] Warning: request dropped: unsafe method override: 127.0.0.2 Apr 26 09:40:25 192.168.122.209 [63376.485633] [tdb] Close table 'client0.tdb' Apr 26 09:40:26 192.168.122.209 [63376.674562] [tdb] Close table 'sessions0.tdb' Apr 26 09:40:26 192.168.122.209 [63376.915167] [tdb] Close table 'filter0.tdb' Apr 26 09:40:26 192.168.122.209 [63376.915585] [tempesta fw] modules are stopped Apr 26 09:40:26 192.168.122.209 [63377.127339] [tempesta fw] exiting... Apr 26 09:40:26 192.168.122.209 [63377.274855] [tdb] Shutdown Tempesta DB Apr 26 09:40:26 192.168.122.209 [63377.474546] End test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideTestCase.test_unsafe_override_x_http_method_override Apr 26 09:40:26 192.168.122.209 [63377.508864] Start test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideTestCase.test_unsafe_override_x_method_override Apr 26 09:40:27 192.168.122.209 [63378.567819] [tdb] Start Tempesta DB Apr 26 09:40:28 192.168.122.209 [63378.710617] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:40:28 192.168.122.209 [63379.516563] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63379.516563] Maybe that's fine, but it's worth checking the [63379.516563] config - if there is no relations between the [63379.516563] names, then host name confusion attack is possible. Apr 26 09:40:29 192.168.122.209 [63379.615265] [tempesta fw] Configuration processing is completed. Apr 26 09:40:29 192.168.122.209 [63379.671371] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:40:29 192.168.122.209 [63379.700230] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:40:29 192.168.122.209 [63379.729374] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:40:29 192.168.122.209 [63379.763248] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:40:29 192.168.122.209 [63379.764958] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:40:29 192.168.122.209 [63379.766642] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:40:29 192.168.122.209 [63379.807213] [tempesta fw] Tempesta FW is ready Apr 26 09:40:29 192.168.122.209 [63379.946604] [tempesta fw] Warning: request dropped: unsafe method override: 127.0.0.2 Apr 26 09:40:29 192.168.122.209 [63380.448610] [tdb] Close table 'client0.tdb' Apr 26 09:40:30 192.168.122.209 [63380.652222] [tdb] Close table 'sessions0.tdb' Apr 26 09:40:30 192.168.122.209 [63380.895426] [tdb] Close table 'filter0.tdb' Apr 26 09:40:30 192.168.122.209 [63380.895864] [tempesta fw] modules are stopped Apr 26 09:40:30 192.168.122.209 [63381.116662] [tempesta fw] exiting... Apr 26 09:40:30 192.168.122.209 [63381.216062] [tdb] Shutdown Tempesta DB Apr 26 09:40:30 192.168.122.209 [63381.428287] End test: t_frang.test_http_method_override_allowed.FrangHttpMethodsOverrideTestCase.test_unsafe_override_x_method_override Apr 26 09:40:30 192.168.122.209 [63381.448597] Start test: t_frang.test_http_methods.FrangHttpMethodsH2.test_accepted_request Apr 26 09:40:31 192.168.122.209 [63382.439613] [tdb] Start Tempesta DB Apr 26 09:40:31 192.168.122.209 [63382.562874] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:40:32 192.168.122.209 [63383.389507] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63383.389507] Maybe that's fine, but it's worth checking the [63383.389507] config - if there is no relations between the [63383.389507] names, then host name confusion attack is possible. Apr 26 09:40:32 192.168.122.209 [63383.503328] [tempesta fw] Configuration processing is completed. Apr 26 09:40:32 192.168.122.209 [63383.555305] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:40:32 192.168.122.209 [63383.584339] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:40:33 192.168.122.209 [63383.614758] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:40:33 192.168.122.209 [63383.667323] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:40:33 192.168.122.209 [63383.669054] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:40:33 192.168.122.209 [63383.670688] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:40:33 192.168.122.209 [63383.715250] [tempesta fw] Tempesta FW is ready Apr 26 09:40:33 192.168.122.209 [63384.365040] [tdb] Close table 'client0.tdb' Apr 26 09:40:33 192.168.122.209 [63384.550583] [tdb] Close table 'sessions0.tdb' Apr 26 09:40:34 192.168.122.209 [63384.795257] [tdb] Close table 'filter0.tdb' Apr 26 09:40:34 192.168.122.209 [63384.795675] [tempesta fw] modules are stopped Apr 26 09:40:34 192.168.122.209 [63385.000877] [tempesta fw] exiting... Apr 26 09:40:34 192.168.122.209 [63385.117748] [tdb] Shutdown Tempesta DB Apr 26 09:40:34 192.168.122.209 [63385.311252] End test: t_frang.test_http_methods.FrangHttpMethodsH2.test_accepted_request Apr 26 09:40:34 192.168.122.209 [63385.336452] Start test: t_frang.test_http_methods.FrangHttpMethodsH2.test_accepted_request_shipping_cfg Apr 26 09:40:35 192.168.122.209 [63386.460174] [tdb] Start Tempesta DB Apr 26 09:40:35 192.168.122.209 [63386.580053] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:40:36 192.168.122.209 [63387.360648] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63387.360648] Maybe that's fine, but it's worth checking the [63387.360648] config - if there is no relations between the [63387.360648] names, then host name confusion attack is possible. Apr 26 09:40:36 192.168.122.209 [63387.463371] [tempesta fw] Configuration processing is completed. Apr 26 09:40:36 192.168.122.209 [63387.520928] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:40:36 192.168.122.209 [63387.552970] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:40:36 192.168.122.209 [63387.582649] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:40:37 192.168.122.209 [63387.623361] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:40:37 192.168.122.209 [63387.625041] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:40:37 192.168.122.209 [63387.626708] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:40:37 192.168.122.209 [63387.667260] [tempesta fw] Tempesta FW is ready Apr 26 09:40:37 192.168.122.209 [63388.394355] [tdb] Close table 'client0.tdb' Apr 26 09:40:37 192.168.122.209 [63388.582958] [tdb] Close table 'sessions0.tdb' Apr 26 09:40:38 192.168.122.209 [63388.820083] [tdb] Close table 'filter0.tdb' Apr 26 09:40:38 192.168.122.209 [63388.820479] [tempesta fw] modules are stopped Apr 26 09:40:38 192.168.122.209 [63389.006927] [tempesta fw] exiting... Apr 26 09:40:38 192.168.122.209 [63389.110069] [tdb] Shutdown Tempesta DB Apr 26 09:40:38 192.168.122.209 [63389.324982] End test: t_frang.test_http_methods.FrangHttpMethodsH2.test_accepted_request_shipping_cfg Apr 26 09:40:38 192.168.122.209 [63389.337216] Start test: t_frang.test_http_methods.FrangHttpMethodsH2.test_accepted_request_with_unknown_method Apr 26 09:40:39 192.168.122.209 [63390.426121] [tdb] Start Tempesta DB Apr 26 09:40:39 192.168.122.209 [63390.568193] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:40:40 192.168.122.209 [63391.400690] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63391.400690] Maybe that's fine, but it's worth checking the [63391.400690] config - if there is no relations between the [63391.400690] names, then host name confusion attack is possible. Apr 26 09:40:40 192.168.122.209 [63391.503441] [tempesta fw] Configuration processing is completed. Apr 26 09:40:40 192.168.122.209 [63391.561521] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:40:40 192.168.122.209 [63391.593745] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:40:41 192.168.122.209 [63391.624786] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:40:41 192.168.122.209 [63391.671414] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:40:41 192.168.122.209 [63391.673112] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:40:41 192.168.122.209 [63391.674897] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:40:41 192.168.122.209 [63391.715357] [tempesta fw] Tempesta FW is ready Apr 26 09:40:41 192.168.122.209 [63392.378004] [tdb] Close table 'client0.tdb' Apr 26 09:40:41 192.168.122.209 [63392.588682] [tdb] Close table 'sessions0.tdb' Apr 26 09:40:42 192.168.122.209 [63392.832448] [tdb] Close table 'filter0.tdb' Apr 26 09:40:42 192.168.122.209 [63392.832874] [tempesta fw] modules are stopped Apr 26 09:40:42 192.168.122.209 [63393.039109] [tempesta fw] exiting... Apr 26 09:40:42 192.168.122.209 [63393.149692] [tdb] Shutdown Tempesta DB Apr 26 09:40:42 192.168.122.209 [63393.360933] End test: t_frang.test_http_methods.FrangHttpMethodsH2.test_accepted_request_with_unknown_method Apr 26 09:40:42 192.168.122.209 [63393.386658] Start test: t_frang.test_http_methods.FrangHttpMethodsH2.test_not_accepted_request Apr 26 09:40:43 192.168.122.209 [63394.441769] [tdb] Start Tempesta DB Apr 26 09:40:43 192.168.122.209 [63394.568404] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:40:44 192.168.122.209 [63395.408892] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63395.408892] Maybe that's fine, but it's worth checking the [63395.408892] config - if there is no relations between the [63395.408892] names, then host name confusion attack is possible. Apr 26 09:40:44 192.168.122.209 [63395.515517] [tempesta fw] Configuration processing is completed. Apr 26 09:40:44 192.168.122.209 [63395.573411] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:40:45 192.168.122.209 [63395.604965] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:40:45 192.168.122.209 [63395.639072] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:40:45 192.168.122.209 [63395.687472] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:40:45 192.168.122.209 [63395.689199] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:40:45 192.168.122.209 [63395.690851] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:40:45 192.168.122.209 [63395.727428] [tempesta fw] Tempesta FW is ready Apr 26 09:40:45 192.168.122.209 [63395.898843] [tempesta fw] Warning: frang: restricted HTTP method for 127.0.0.2: 10 (0x400u) Apr 26 09:40:45 192.168.122.209 [63395.899609] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 09:40:45 192.168.122.209 [63396.404892] [tdb] Close table 'client0.tdb' Apr 26 09:40:45 192.168.122.209 [63396.589221] [tdb] Close table 'sessions0.tdb' Apr 26 09:40:46 192.168.122.209 [63396.819738] [tdb] Close table 'filter0.tdb' Apr 26 09:40:46 192.168.122.209 [63396.820152] [tempesta fw] modules are stopped Apr 26 09:40:46 192.168.122.209 [63397.020907] [tempesta fw] exiting... Apr 26 09:40:46 192.168.122.209 [63397.161907] [tdb] Shutdown Tempesta DB Apr 26 09:40:46 192.168.122.209 [63397.359742] End test: t_frang.test_http_methods.FrangHttpMethodsH2.test_not_accepted_request Apr 26 09:40:46 192.168.122.209 [63397.379140] Start test: t_frang.test_http_methods.FrangHttpMethodsH2.test_not_accepted_request_owerride Apr 26 09:40:47 192.168.122.209 [63398.437647] [tdb] Start Tempesta DB Apr 26 09:40:47 192.168.122.209 [63398.563902] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:40:48 192.168.122.209 [63399.444825] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63399.444825] Maybe that's fine, but it's worth checking the [63399.444825] config - if there is no relations between the [63399.444825] names, then host name confusion attack is possible. Apr 26 09:40:48 192.168.122.209 [63399.567553] [tempesta fw] Configuration processing is completed. Apr 26 09:40:49 192.168.122.209 [63399.628884] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:40:49 192.168.122.209 [63399.660916] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:40:49 192.168.122.209 [63399.691686] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:40:49 192.168.122.209 [63399.755527] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:40:49 192.168.122.209 [63399.757229] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:40:49 192.168.122.209 [63399.758892] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:40:49 192.168.122.209 [63399.803458] [tempesta fw] Tempesta FW is ready Apr 26 09:40:49 192.168.122.209 [63399.965958] [tempesta fw] Warning: frang: restricted HTTP method for 127.0.0.2: 17 (0x20000u) Apr 26 09:40:49 192.168.122.209 [63399.966753] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 09:40:49 192.168.122.209 [63400.450045] [tdb] Close table 'client0.tdb' Apr 26 09:40:50 192.168.122.209 [63400.640720] [tdb] Close table 'sessions0.tdb' Apr 26 09:40:50 192.168.122.209 [63400.880485] [tdb] Close table 'filter0.tdb' Apr 26 09:40:50 192.168.122.209 [63400.880910] [tempesta fw] modules are stopped Apr 26 09:40:50 192.168.122.209 [63401.100945] [tempesta fw] exiting... Apr 26 09:40:50 192.168.122.209 [63401.266504] [tdb] Shutdown Tempesta DB Apr 26 09:40:50 192.168.122.209 [63401.517739] End test: t_frang.test_http_methods.FrangHttpMethodsH2.test_not_accepted_request_owerride Apr 26 09:40:50 192.168.122.209 [63401.525686] Start test: t_frang.test_http_methods.FrangHttpMethodsH2.test_not_accepted_request_register Apr 26 09:40:51 192.168.122.209 [63402.565356] [tdb] Start Tempesta DB Apr 26 09:40:52 192.168.122.209 [63402.702048] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:40:52 192.168.122.209 [63403.555724] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63403.555724] Maybe that's fine, but it's worth checking the [63403.555724] config - if there is no relations between the [63403.555724] names, then host name confusion attack is possible. Apr 26 09:40:53 192.168.122.209 [63403.667592] [tempesta fw] Configuration processing is completed. Apr 26 09:40:53 192.168.122.209 [63403.717047] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:40:53 192.168.122.209 [63403.747344] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:40:53 192.168.122.209 [63403.776068] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:40:53 192.168.122.209 [63403.823564] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:40:53 192.168.122.209 [63403.825028] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:40:53 192.168.122.209 [63403.826645] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:40:53 192.168.122.209 [63403.867516] [tempesta fw] Tempesta FW is ready Apr 26 09:40:53 192.168.122.209 [63404.050446] [tempesta fw] Warning: frang: restricted HTTP method for 127.0.0.2: 17 (0x20000u) Apr 26 09:40:53 192.168.122.209 [63404.051233] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 09:40:53 192.168.122.209 [63404.551102] [tdb] Close table 'client0.tdb' Apr 26 09:40:54 192.168.122.209 [63404.737652] [tdb] Close table 'sessions0.tdb' Apr 26 09:40:54 192.168.122.209 [63404.989457] [tdb] Close table 'filter0.tdb' Apr 26 09:40:54 192.168.122.209 [63404.989868] [tempesta fw] modules are stopped Apr 26 09:40:54 192.168.122.209 [63405.222315] [tempesta fw] exiting... Apr 26 09:40:54 192.168.122.209 [63405.368801] [tdb] Shutdown Tempesta DB Apr 26 09:40:55 192.168.122.209 [63405.611198] End test: t_frang.test_http_methods.FrangHttpMethodsH2.test_not_accepted_request_register Apr 26 09:40:55 192.168.122.209 [63405.624220] Start test: t_frang.test_http_methods.FrangHttpMethodsH2.test_not_accepted_request_shipping_cfg_CONNECT Apr 26 09:40:56 192.168.122.209 [63406.708830] [tdb] Start Tempesta DB Apr 26 09:40:56 192.168.122.209 [63406.840382] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:40:57 192.168.122.209 [63407.704813] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63407.704813] Maybe that's fine, but it's worth checking the [63407.704813] config - if there is no relations between the [63407.704813] names, then host name confusion attack is possible. Apr 26 09:40:57 192.168.122.209 [63407.812582] [tempesta fw] Configuration processing is completed. Apr 26 09:40:57 192.168.122.209 [63407.871678] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:40:57 192.168.122.209 [63407.899948] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:40:57 192.168.122.209 [63407.927563] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:40:57 192.168.122.209 [63407.983609] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:40:57 192.168.122.209 [63407.985307] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:40:57 192.168.122.209 [63407.986955] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:40:57 192.168.122.209 [63408.031581] [tempesta fw] Tempesta FW is ready Apr 26 09:40:57 192.168.122.209 [63408.220393] [tempesta fw] Warning: frang: restricted HTTP method for 127.0.0.2: 17 (0x20000u) Apr 26 09:40:57 192.168.122.209 [63408.221167] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 09:40:58 192.168.122.209 [63408.748342] [tdb] Close table 'client0.tdb' Apr 26 09:40:58 192.168.122.209 [63408.935876] [tdb] Close table 'sessions0.tdb' Apr 26 09:40:58 192.168.122.209 [63409.195026] [tdb] Close table 'filter0.tdb' Apr 26 09:40:58 192.168.122.209 [63409.195852] [tempesta fw] modules are stopped Apr 26 09:40:58 192.168.122.209 [63409.373351] [tempesta fw] exiting... Apr 26 09:40:58 192.168.122.209 [63409.488793] [tdb] Shutdown Tempesta DB Apr 26 09:40:59 192.168.122.209 [63409.685060] End test: t_frang.test_http_methods.FrangHttpMethodsH2.test_not_accepted_request_shipping_cfg_CONNECT Apr 26 09:40:59 192.168.122.209 [63409.703188] Start test: t_frang.test_http_methods.FrangHttpMethodsH2.test_not_accepted_request_shipping_cfg_DELETE Apr 26 09:41:00 192.168.122.209 [63410.780631] [tdb] Start Tempesta DB Apr 26 09:41:00 192.168.122.209 [63410.911926] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:41:01 192.168.122.209 [63411.732980] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63411.732980] Maybe that's fine, but it's worth checking the [63411.732980] config - if there is no relations between the [63411.732980] names, then host name confusion attack is possible. Apr 26 09:41:01 192.168.122.209 [63411.839684] [tempesta fw] Configuration processing is completed. Apr 26 09:41:01 192.168.122.209 [63411.893540] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:41:01 192.168.122.209 [63411.921341] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:41:01 192.168.122.209 [63411.950274] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:41:01 192.168.122.209 [63411.995696] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:41:01 192.168.122.209 [63411.997381] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:41:01 192.168.122.209 [63411.999208] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:41:01 192.168.122.209 [63412.047622] [tempesta fw] Tempesta FW is ready Apr 26 09:41:01 192.168.122.209 [63412.233823] [tempesta fw] Warning: frang: restricted HTTP method for 127.0.0.2: 2 (0x4u) Apr 26 09:41:01 192.168.122.209 [63412.235976] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 09:41:02 192.168.122.209 [63412.787568] [tdb] Close table 'client0.tdb' Apr 26 09:41:02 192.168.122.209 [63412.980560] [tdb] Close table 'sessions0.tdb' Apr 26 09:41:02 192.168.122.209 [63413.242283] [tdb] Close table 'filter0.tdb' Apr 26 09:41:02 192.168.122.209 [63413.242797] [tempesta fw] modules are stopped Apr 26 09:41:02 192.168.122.209 [63413.432583] [tempesta fw] exiting... Apr 26 09:41:02 192.168.122.209 [63413.557176] [tdb] Shutdown Tempesta DB Apr 26 09:41:03 192.168.122.209 [63413.739610] End test: t_frang.test_http_methods.FrangHttpMethodsH2.test_not_accepted_request_shipping_cfg_DELETE Apr 26 09:41:03 192.168.122.209 [63413.758688] Start test: t_frang.test_http_methods.FrangHttpMethodsH2.test_not_accepted_request_shipping_cfg_OPTIONS Apr 26 09:41:04 192.168.122.209 [63414.836635] [tdb] Start Tempesta DB Apr 26 09:41:04 192.168.122.209 [63414.973847] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:41:05 192.168.122.209 [63415.829274] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63415.829274] Maybe that's fine, but it's worth checking the [63415.829274] config - if there is no relations between the [63415.829274] names, then host name confusion attack is possible. Apr 26 09:41:05 192.168.122.209 [63415.939780] [tempesta fw] Configuration processing is completed. Apr 26 09:41:05 192.168.122.209 [63415.990456] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:41:05 192.168.122.209 [63416.018108] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:41:05 192.168.122.209 [63416.047045] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:41:05 192.168.122.209 [63416.091730] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:41:05 192.168.122.209 [63416.093418] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:41:05 192.168.122.209 [63416.095056] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:41:05 192.168.122.209 [63416.131683] [tempesta fw] Tempesta FW is ready Apr 26 09:41:05 192.168.122.209 [63416.293054] [tempesta fw] Warning: frang: restricted HTTP method for 127.0.0.2: 8 (0x100u) Apr 26 09:41:05 192.168.122.209 [63416.293802] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 09:41:06 192.168.122.209 [63416.771275] [tdb] Close table 'client0.tdb' Apr 26 09:41:06 192.168.122.209 [63416.968075] [tdb] Close table 'sessions0.tdb' Apr 26 09:41:06 192.168.122.209 [63417.193159] [tdb] Close table 'filter0.tdb' Apr 26 09:41:06 192.168.122.209 [63417.193577] [tempesta fw] modules are stopped Apr 26 09:41:06 192.168.122.209 [63417.379649] [tempesta fw] exiting... Apr 26 09:41:06 192.168.122.209 [63417.500490] [tdb] Shutdown Tempesta DB Apr 26 09:41:07 192.168.122.209 [63417.728435] End test: t_frang.test_http_methods.FrangHttpMethodsH2.test_not_accepted_request_shipping_cfg_OPTIONS Apr 26 09:41:07 192.168.122.209 [63417.742616] Start test: t_frang.test_http_methods.FrangHttpMethodsH2.test_not_accepted_request_shipping_cfg_PATCH Apr 26 09:41:08 192.168.122.209 [63418.806533] [tdb] Start Tempesta DB Apr 26 09:41:08 192.168.122.209 [63418.929725] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:41:09 192.168.122.209 [63419.716974] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63419.716974] Maybe that's fine, but it's worth checking the [63419.716974] config - if there is no relations between the [63419.716974] names, then host name confusion attack is possible. Apr 26 09:41:09 192.168.122.209 [63419.823805] [tempesta fw] Configuration processing is completed. Apr 26 09:41:09 192.168.122.209 [63419.881896] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:41:09 192.168.122.209 [63419.913300] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:41:09 192.168.122.209 [63419.943798] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:41:09 192.168.122.209 [63419.999772] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:41:09 192.168.122.209 [63420.001492] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:41:09 192.168.122.209 [63420.003166] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:41:09 192.168.122.209 [63420.055721] [tempesta fw] Tempesta FW is ready Apr 26 09:41:09 192.168.122.209 [63420.216330] [tempesta fw] Warning: frang: restricted HTTP method for 127.0.0.2: 9 (0x200u) Apr 26 09:41:09 192.168.122.209 [63420.217110] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 09:41:10 192.168.122.209 [63420.705769] [tdb] Close table 'client0.tdb' Apr 26 09:41:10 192.168.122.209 [63420.890821] [tdb] Close table 'sessions0.tdb' Apr 26 09:41:10 192.168.122.209 [63421.141447] [tdb] Close table 'filter0.tdb' Apr 26 09:41:10 192.168.122.209 [63421.141872] [tempesta fw] modules are stopped Apr 26 09:41:10 192.168.122.209 [63421.358992] [tempesta fw] exiting... Apr 26 09:41:10 192.168.122.209 [63421.486235] [tdb] Shutdown Tempesta DB Apr 26 09:41:11 192.168.122.209 [63421.687963] End test: t_frang.test_http_methods.FrangHttpMethodsH2.test_not_accepted_request_shipping_cfg_PATCH Apr 26 09:41:11 192.168.122.209 [63421.705968] Start test: t_frang.test_http_methods.FrangHttpMethodsH2.test_not_accepted_request_shipping_cfg_PUT Apr 26 09:41:12 192.168.122.209 [63422.784171] [tdb] Start Tempesta DB Apr 26 09:41:12 192.168.122.209 [63422.914133] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:41:13 192.168.122.209 [63423.778764] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63423.778764] Maybe that's fine, but it's worth checking the [63423.778764] config - if there is no relations between the [63423.778764] names, then host name confusion attack is possible. Apr 26 09:41:13 192.168.122.209 [63423.871847] [tempesta fw] Configuration processing is completed. Apr 26 09:41:13 192.168.122.209 [63423.929659] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:41:13 192.168.122.209 [63423.962491] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:41:13 192.168.122.209 [63423.992025] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:41:13 192.168.122.209 [63424.035842] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:41:13 192.168.122.209 [63424.037543] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:41:13 192.168.122.209 [63424.039419] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:41:13 192.168.122.209 [63424.079774] [tempesta fw] Tempesta FW is ready Apr 26 09:41:13 192.168.122.209 [63424.281819] [tempesta fw] Warning: frang: restricted HTTP method for 127.0.0.2: 13 (0x2000u) Apr 26 09:41:13 192.168.122.209 [63424.284097] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 09:41:14 192.168.122.209 [63424.774889] [tdb] Close table 'client0.tdb' Apr 26 09:41:14 192.168.122.209 [63424.960710] [tdb] Close table 'sessions0.tdb' Apr 26 09:41:14 192.168.122.209 [63425.166142] [tdb] Close table 'filter0.tdb' Apr 26 09:41:14 192.168.122.209 [63425.166565] [tempesta fw] modules are stopped Apr 26 09:41:14 192.168.122.209 [63425.395505] [tempesta fw] exiting... Apr 26 09:41:14 192.168.122.209 [63425.552603] [tdb] Shutdown Tempesta DB Apr 26 09:41:15 192.168.122.209 [63425.790262] End test: t_frang.test_http_methods.FrangHttpMethodsH2.test_not_accepted_request_shipping_cfg_PUT Apr 26 09:41:15 192.168.122.209 [63425.801903] Start test: t_frang.test_http_methods.FrangHttpMethodsH2.test_not_accepted_request_shipping_cfg_TRACE Apr 26 09:41:16 192.168.122.209 [63426.939328] [tdb] Start Tempesta DB Apr 26 09:41:16 192.168.122.209 [63427.080294] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:41:17 192.168.122.209 [63427.933124] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63427.933124] Maybe that's fine, but it's worth checking the [63427.933124] config - if there is no relations between the [63427.933124] names, then host name confusion attack is possible. Apr 26 09:41:17 192.168.122.209 [63428.035887] [tempesta fw] Configuration processing is completed. Apr 26 09:41:17 192.168.122.209 [63428.086976] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:41:17 192.168.122.209 [63428.114386] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:41:17 192.168.122.209 [63428.141583] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:41:17 192.168.122.209 [63428.187881] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:41:17 192.168.122.209 [63428.189572] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:41:17 192.168.122.209 [63428.191211] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:41:17 192.168.122.209 [63428.247818] [tempesta fw] Tempesta FW is ready Apr 26 09:41:17 192.168.122.209 [63428.442795] [tempesta fw] Warning: frang: restricted HTTP method for 127.0.0.2: 14 (0x4000u) Apr 26 09:41:17 192.168.122.209 [63428.445170] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 09:41:18 192.168.122.209 [63428.973772] [tdb] Close table 'client0.tdb' Apr 26 09:41:18 192.168.122.209 [63429.158522] [tdb] Close table 'sessions0.tdb' Apr 26 09:41:18 192.168.122.209 [63429.411945] [tdb] Close table 'filter0.tdb' Apr 26 09:41:18 192.168.122.209 [63429.412366] [tempesta fw] modules are stopped Apr 26 09:41:19 192.168.122.209 [63429.624819] [tempesta fw] exiting... Apr 26 09:41:19 192.168.122.209 [63429.772815] [tdb] Shutdown Tempesta DB Apr 26 09:41:19 192.168.122.209 [63429.986823] End test: t_frang.test_http_methods.FrangHttpMethodsH2.test_not_accepted_request_shipping_cfg_TRACE Apr 26 09:41:19 192.168.122.209 [63429.999331] Start test: t_frang.test_http_methods.FrangHttpMethodsH2.test_not_accepted_request_with_unknown_method Apr 26 09:41:20 192.168.122.209 [63431.143440] [tdb] Start Tempesta DB Apr 26 09:41:20 192.168.122.209 [63431.270761] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:41:21 192.168.122.209 [63432.121239] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63432.121239] Maybe that's fine, but it's worth checking the [63432.121239] config - if there is no relations between the [63432.121239] names, then host name confusion attack is possible. Apr 26 09:41:21 192.168.122.209 [63432.236337] [tempesta fw] Configuration processing is completed. Apr 26 09:41:21 192.168.122.209 [63432.304306] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:41:21 192.168.122.209 [63432.335936] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:41:21 192.168.122.209 [63432.366078] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:41:21 192.168.122.209 [63432.419886] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:41:21 192.168.122.209 [63432.421598] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:41:21 192.168.122.209 [63432.423252] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:41:21 192.168.122.209 [63432.459875] [tempesta fw] Tempesta FW is ready Apr 26 09:41:22 192.168.122.209 [63432.650944] [tempesta fw] Warning: frang: restricted HTTP method for 127.0.0.2: 17 (0x20000u) Apr 26 09:41:22 192.168.122.209 [63432.653428] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 09:41:22 192.168.122.209 [63433.148669] [tdb] Close table 'client0.tdb' Apr 26 09:41:22 192.168.122.209 [63433.334938] [tdb] Close table 'sessions0.tdb' Apr 26 09:41:22 192.168.122.209 [63433.568360] [tdb] Close table 'filter0.tdb' Apr 26 09:41:22 192.168.122.209 [63433.568806] [tempesta fw] modules are stopped Apr 26 09:41:23 192.168.122.209 [63433.760928] [tempesta fw] exiting... Apr 26 09:41:23 192.168.122.209 [63433.907043] [tdb] Shutdown Tempesta DB Apr 26 09:41:23 192.168.122.209 [63434.109825] End test: t_frang.test_http_methods.FrangHttpMethodsH2.test_not_accepted_request_with_unknown_method Apr 26 09:41:23 192.168.122.209 [63434.124684] Start test: t_frang.test_http_methods.FrangHttpMethodsH2.test_not_accepted_request_zero_byte Apr 26 09:41:24 192.168.122.209 [63435.233301] [tdb] Start Tempesta DB Apr 26 09:41:24 192.168.122.209 [63435.362636] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:41:25 192.168.122.209 [63436.177273] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63436.177273] Maybe that's fine, but it's worth checking the [63436.177273] config - if there is no relations between the [63436.177273] names, then host name confusion attack is possible. Apr 26 09:41:25 192.168.122.209 [63436.287997] [tempesta fw] Configuration processing is completed. Apr 26 09:41:25 192.168.122.209 [63436.347359] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:41:25 192.168.122.209 [63436.379688] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:41:25 192.168.122.209 [63436.411255] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:41:25 192.168.122.209 [63436.447988] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:41:25 192.168.122.209 [63436.449710] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:41:25 192.168.122.209 [63436.451365] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:41:25 192.168.122.209 [63436.495921] [tempesta fw] Tempesta FW is ready Apr 26 09:41:26 192.168.122.209 [63436.649928] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_MethodUnknown input=0x0(''), len=2, off=0 Apr 26 09:41:26 192.168.122.209 [63437.141499] [tdb] Close table 'client0.tdb' Apr 26 09:41:26 192.168.122.209 [63437.327454] [tdb] Close table 'sessions0.tdb' Apr 26 09:41:26 192.168.122.209 [63437.584193] [tdb] Close table 'filter0.tdb' Apr 26 09:41:26 192.168.122.209 [63437.584613] [tempesta fw] modules are stopped Apr 26 09:41:27 192.168.122.209 [63437.803885] [tempesta fw] exiting... Apr 26 09:41:27 192.168.122.209 [63437.958309] [tdb] Shutdown Tempesta DB Apr 26 09:41:27 192.168.122.209 [63438.167930] End test: t_frang.test_http_methods.FrangHttpMethodsH2.test_not_accepted_request_zero_byte Apr 26 09:41:27 192.168.122.209 [63438.188199] Start test: t_frang.test_http_methods.FrangHttpMethodsTestCase.test_accepted_request Apr 26 09:41:28 192.168.122.209 [63439.245917] [tdb] Start Tempesta DB Apr 26 09:41:28 192.168.122.209 [63439.380853] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:41:29 192.168.122.209 [63440.210542] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63440.210542] Maybe that's fine, but it's worth checking the [63440.210542] config - if there is no relations between the [63440.210542] names, then host name confusion attack is possible. Apr 26 09:41:29 192.168.122.209 [63440.308038] [tempesta fw] Configuration processing is completed. Apr 26 09:41:29 192.168.122.209 [63440.360014] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:41:29 192.168.122.209 [63440.387971] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:41:29 192.168.122.209 [63440.415984] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:41:29 192.168.122.209 [63440.464042] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:41:29 192.168.122.209 [63440.465728] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:41:29 192.168.122.209 [63440.467381] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:41:29 192.168.122.209 [63440.511881] [tempesta fw] Tempesta FW is ready Apr 26 09:41:30 192.168.122.209 [63441.111149] [tdb] Close table 'client0.tdb' Apr 26 09:41:30 192.168.122.209 [63441.307013] [tdb] Close table 'sessions0.tdb' Apr 26 09:41:30 192.168.122.209 [63441.523933] [tdb] Close table 'filter0.tdb' Apr 26 09:41:30 192.168.122.209 [63441.524359] [tempesta fw] modules are stopped Apr 26 09:41:31 192.168.122.209 [63441.720240] [tempesta fw] exiting... Apr 26 09:41:31 192.168.122.209 [63441.839746] [tdb] Shutdown Tempesta DB Apr 26 09:41:31 192.168.122.209 [63442.047676] End test: t_frang.test_http_methods.FrangHttpMethodsTestCase.test_accepted_request Apr 26 09:41:31 192.168.122.209 [63442.060349] Start test: t_frang.test_http_methods.FrangHttpMethodsTestCase.test_accepted_request_shipping_cfg Apr 26 09:41:32 192.168.122.209 [63443.142961] [tdb] Start Tempesta DB Apr 26 09:41:32 192.168.122.209 [63443.284242] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:41:33 192.168.122.209 [63444.049370] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63444.049370] Maybe that's fine, but it's worth checking the [63444.049370] config - if there is no relations between the [63444.049370] names, then host name confusion attack is possible. Apr 26 09:41:33 192.168.122.209 [63444.148106] [tempesta fw] Configuration processing is completed. Apr 26 09:41:33 192.168.122.209 [63444.209868] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:41:33 192.168.122.209 [63444.243281] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:41:33 192.168.122.209 [63444.273697] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:41:33 192.168.122.209 [63444.332253] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:41:33 192.168.122.209 [63444.333929] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:41:33 192.168.122.209 [63444.335567] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:41:33 192.168.122.209 [63444.372042] [tempesta fw] Tempesta FW is ready Apr 26 09:41:34 192.168.122.209 [63445.030062] [tdb] Close table 'client0.tdb' Apr 26 09:41:34 192.168.122.209 [63445.226776] [tdb] Close table 'sessions0.tdb' Apr 26 09:41:34 192.168.122.209 [63445.442573] [tdb] Close table 'filter0.tdb' Apr 26 09:41:34 192.168.122.209 [63445.442982] [tempesta fw] modules are stopped Apr 26 09:41:35 192.168.122.209 [63445.627950] [tempesta fw] exiting... Apr 26 09:41:35 192.168.122.209 [63445.786010] [tdb] Shutdown Tempesta DB Apr 26 09:41:35 192.168.122.209 [63446.002030] End test: t_frang.test_http_methods.FrangHttpMethodsTestCase.test_accepted_request_shipping_cfg Apr 26 09:41:35 192.168.122.209 [63446.014619] Start test: t_frang.test_http_methods.FrangHttpMethodsTestCase.test_accepted_request_with_unknown_method Apr 26 09:41:36 192.168.122.209 [63447.030958] [tdb] Start Tempesta DB Apr 26 09:41:36 192.168.122.209 [63447.162286] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:41:37 192.168.122.209 [63447.901403] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63447.901403] Maybe that's fine, but it's worth checking the [63447.901403] config - if there is no relations between the [63447.901403] names, then host name confusion attack is possible. Apr 26 09:41:37 192.168.122.209 [63448.008142] [tempesta fw] Configuration processing is completed. Apr 26 09:41:37 192.168.122.209 [63448.060291] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:41:37 192.168.122.209 [63448.087879] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:41:37 192.168.122.209 [63448.114803] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:41:37 192.168.122.209 [63448.156127] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:41:37 192.168.122.209 [63448.157826] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:41:37 192.168.122.209 [63448.159482] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:41:37 192.168.122.209 [63448.196082] [tempesta fw] Tempesta FW is ready Apr 26 09:41:38 192.168.122.209 [63448.827845] [tdb] Close table 'client0.tdb' Apr 26 09:41:38 192.168.122.209 [63449.043585] [tdb] Close table 'sessions0.tdb' Apr 26 09:41:38 192.168.122.209 [63449.288934] [tdb] Close table 'filter0.tdb' Apr 26 09:41:38 192.168.122.209 [63449.289345] [tempesta fw] modules are stopped Apr 26 09:41:38 192.168.122.209 [63449.508207] [tempesta fw] exiting... Apr 26 09:41:39 192.168.122.209 [63449.650639] [tdb] Shutdown Tempesta DB Apr 26 09:41:39 192.168.122.209 [63449.838989] End test: t_frang.test_http_methods.FrangHttpMethodsTestCase.test_accepted_request_with_unknown_method Apr 26 09:41:39 192.168.122.209 [63449.847929] Start test: t_frang.test_http_methods.FrangHttpMethodsTestCase.test_not_accepted_request Apr 26 09:41:40 192.168.122.209 [63450.936722] [tdb] Start Tempesta DB Apr 26 09:41:40 192.168.122.209 [63451.065143] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:41:41 192.168.122.209 [63451.849413] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63451.849413] Maybe that's fine, but it's worth checking the [63451.849413] config - if there is no relations between the [63451.849413] names, then host name confusion attack is possible. Apr 26 09:41:41 192.168.122.209 [63451.948200] [tempesta fw] Configuration processing is completed. Apr 26 09:41:41 192.168.122.209 [63452.006942] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:41:41 192.168.122.209 [63452.034360] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:41:41 192.168.122.209 [63452.061579] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:41:41 192.168.122.209 [63452.112182] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:41:41 192.168.122.209 [63452.113865] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:41:41 192.168.122.209 [63452.115510] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:41:41 192.168.122.209 [63452.160118] [tempesta fw] Tempesta FW is ready Apr 26 09:41:41 192.168.122.209 [63452.280259] [tempesta fw] Warning: frang: restricted HTTP method for 127.0.0.2: 10 (0x400u) Apr 26 09:41:41 192.168.122.209 [63452.281303] [tempesta fw] Warning: postponed request has been filtered out: 127.0.0.2 Apr 26 09:41:42 192.168.122.209 [63452.766774] [tdb] Close table 'client0.tdb' Apr 26 09:41:42 192.168.122.209 [63452.954437] [tdb] Close table 'sessions0.tdb' Apr 26 09:41:42 192.168.122.209 [63453.186580] [tdb] Close table 'filter0.tdb' Apr 26 09:41:42 192.168.122.209 [63453.187007] [tempesta fw] modules are stopped Apr 26 09:41:42 192.168.122.209 [63453.423200] [tempesta fw] exiting... Apr 26 09:41:42 192.168.122.209 [63453.547774] [tdb] Shutdown Tempesta DB Apr 26 09:41:43 192.168.122.209 [63453.773964] End test: t_frang.test_http_methods.FrangHttpMethodsTestCase.test_not_accepted_request Apr 26 09:41:43 192.168.122.209 [63453.780542] Start test: t_frang.test_http_methods.FrangHttpMethodsTestCase.test_not_accepted_request_owerride Apr 26 09:41:44 192.168.122.209 [63454.787797] [tdb] Start Tempesta DB Apr 26 09:41:44 192.168.122.209 [63454.913526] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:41:45 192.168.122.209 [63455.729480] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63455.729480] Maybe that's fine, but it's worth checking the [63455.729480] config - if there is no relations between the [63455.729480] names, then host name confusion attack is possible. Apr 26 09:41:45 192.168.122.209 [63455.836249] [tempesta fw] Configuration processing is completed. Apr 26 09:41:45 192.168.122.209 [63455.901836] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:41:45 192.168.122.209 [63455.934821] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:41:45 192.168.122.209 [63455.964172] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:41:45 192.168.122.209 [63456.020235] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:41:45 192.168.122.209 [63456.021925] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:41:45 192.168.122.209 [63456.023589] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:41:45 192.168.122.209 [63456.064174] [tempesta fw] Tempesta FW is ready Apr 26 09:41:45 192.168.122.209 [63456.188580] [tempesta fw] Warning: frang: restricted HTTP method for 127.0.0.2: 17 (0x20000u) Apr 26 09:41:45 192.168.122.209 [63456.190926] [tempesta fw] Warning: postponed request has been filtered out: 127.0.0.2 Apr 26 09:41:46 192.168.122.209 [63456.689768] [tdb] Close table 'client0.tdb' Apr 26 09:41:46 192.168.122.209 [63456.870279] [tdb] Close table 'sessions0.tdb' Apr 26 09:41:46 192.168.122.209 [63457.098490] [tdb] Close table 'filter0.tdb' Apr 26 09:41:46 192.168.122.209 [63457.098925] [tempesta fw] modules are stopped Apr 26 09:41:46 192.168.122.209 [63457.304726] [tempesta fw] exiting... Apr 26 09:41:46 192.168.122.209 [63457.442027] [tdb] Shutdown Tempesta DB Apr 26 09:41:47 192.168.122.209 [63457.668774] End test: t_frang.test_http_methods.FrangHttpMethodsTestCase.test_not_accepted_request_owerride Apr 26 09:41:47 192.168.122.209 [63457.679897] Start test: t_frang.test_http_methods.FrangHttpMethodsTestCase.test_not_accepted_request_register Apr 26 09:41:48 192.168.122.209 [63458.723915] [tdb] Start Tempesta DB Apr 26 09:41:48 192.168.122.209 [63458.861004] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:41:49 192.168.122.209 [63459.681588] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63459.681588] Maybe that's fine, but it's worth checking the [63459.681588] config - if there is no relations between the [63459.681588] names, then host name confusion attack is possible. Apr 26 09:41:49 192.168.122.209 [63459.792306] [tempesta fw] Configuration processing is completed. Apr 26 09:41:49 192.168.122.209 [63459.851236] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:41:49 192.168.122.209 [63459.893813] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:41:49 192.168.122.209 [63459.924318] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:41:49 192.168.122.209 [63459.968303] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:41:49 192.168.122.209 [63459.969995] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:41:49 192.168.122.209 [63459.971654] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:41:49 192.168.122.209 [63460.008235] [tempesta fw] Tempesta FW is ready Apr 26 09:41:49 192.168.122.209 [63460.148721] [tempesta fw] Warning: frang: restricted HTTP method for 127.0.0.2: 17 (0x20000u) Apr 26 09:41:49 192.168.122.209 [63460.149871] [tempesta fw] Warning: postponed request has been filtered out: 127.0.0.2 Apr 26 09:41:50 192.168.122.209 [63460.630256] [tdb] Close table 'client0.tdb' Apr 26 09:41:50 192.168.122.209 [63460.819817] [tdb] Close table 'sessions0.tdb' Apr 26 09:41:50 192.168.122.209 [63461.071449] [tdb] Close table 'filter0.tdb' Apr 26 09:41:50 192.168.122.209 [63461.071845] [tempesta fw] modules are stopped Apr 26 09:41:50 192.168.122.209 [63461.261634] [tempesta fw] exiting... Apr 26 09:41:50 192.168.122.209 [63461.385967] [tdb] Shutdown Tempesta DB Apr 26 09:41:50 192.168.122.209 [63461.592245] End test: t_frang.test_http_methods.FrangHttpMethodsTestCase.test_not_accepted_request_register Apr 26 09:41:51 192.168.122.209 [63461.617012] Start test: t_frang.test_http_methods.FrangHttpMethodsTestCase.test_not_accepted_request_shipping_cfg_CONNECT Apr 26 09:41:52 192.168.122.209 [63462.653165] [tdb] Start Tempesta DB Apr 26 09:41:52 192.168.122.209 [63462.808571] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:41:52 192.168.122.209 [63463.577586] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63463.577586] Maybe that's fine, but it's worth checking the [63463.577586] config - if there is no relations between the [63463.577586] names, then host name confusion attack is possible. Apr 26 09:41:53 192.168.122.209 [63463.680349] [tempesta fw] Configuration processing is completed. Apr 26 09:41:53 192.168.122.209 [63463.731350] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:41:53 192.168.122.209 [63463.759247] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:41:53 192.168.122.209 [63463.786958] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:41:53 192.168.122.209 [63463.836322] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:41:53 192.168.122.209 [63463.837998] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:41:53 192.168.122.209 [63463.839664] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:41:53 192.168.122.209 [63463.884280] [tempesta fw] Tempesta FW is ready Apr 26 09:41:53 192.168.122.209 [63464.007161] [tempesta fw] Warning: frang: restricted HTTP method for 127.0.0.2: 17 (0x20000u) Apr 26 09:41:53 192.168.122.209 [63464.009556] [tempesta fw] Warning: postponed request has been filtered out: 127.0.0.2 Apr 26 09:41:53 192.168.122.209 [63464.489445] [tdb] Close table 'client0.tdb' Apr 26 09:41:54 192.168.122.209 [63464.678746] [tdb] Close table 'sessions0.tdb' Apr 26 09:41:54 192.168.122.209 [63464.915624] [tdb] Close table 'filter0.tdb' Apr 26 09:41:54 192.168.122.209 [63464.916054] [tempesta fw] modules are stopped Apr 26 09:41:54 192.168.122.209 [63465.100087] [tempesta fw] exiting... Apr 26 09:41:54 192.168.122.209 [63465.216375] [tdb] Shutdown Tempesta DB Apr 26 09:41:54 192.168.122.209 [63465.417786] End test: t_frang.test_http_methods.FrangHttpMethodsTestCase.test_not_accepted_request_shipping_cfg_CONNECT Apr 26 09:41:54 192.168.122.209 [63465.439364] Start test: t_frang.test_http_methods.FrangHttpMethodsTestCase.test_not_accepted_request_shipping_cfg_DELETE Apr 26 09:41:55 192.168.122.209 [63466.464101] [tdb] Start Tempesta DB Apr 26 09:41:55 192.168.122.209 [63466.598771] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:41:56 192.168.122.209 [63467.409649] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63467.409649] Maybe that's fine, but it's worth checking the [63467.409649] config - if there is no relations between the [63467.409649] names, then host name confusion attack is possible. Apr 26 09:41:56 192.168.122.209 [63467.508400] [tempesta fw] Configuration processing is completed. Apr 26 09:41:56 192.168.122.209 [63467.560517] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:41:56 192.168.122.209 [63467.589127] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:41:57 192.168.122.209 [63467.618730] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:41:57 192.168.122.209 [63467.704368] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:41:57 192.168.122.209 [63467.706088] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:41:57 192.168.122.209 [63467.707785] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:41:57 192.168.122.209 [63467.752308] [tempesta fw] Tempesta FW is ready Apr 26 09:41:57 192.168.122.209 [63467.888354] [tempesta fw] Warning: frang: restricted HTTP method for 127.0.0.2: 2 (0x4u) Apr 26 09:41:57 192.168.122.209 [63467.889579] [tempesta fw] Warning: postponed request has been filtered out: 127.0.0.2 Apr 26 09:41:57 192.168.122.209 [63468.368251] [tdb] Close table 'client0.tdb' Apr 26 09:41:57 192.168.122.209 [63468.545712] [tdb] Close table 'sessions0.tdb' Apr 26 09:41:58 192.168.122.209 [63468.772801] [tdb] Close table 'filter0.tdb' Apr 26 09:41:58 192.168.122.209 [63468.773228] [tempesta fw] modules are stopped Apr 26 09:41:58 192.168.122.209 [63468.968767] [tempesta fw] exiting... Apr 26 09:41:58 192.168.122.209 [63469.082771] [tdb] Shutdown Tempesta DB Apr 26 09:41:58 192.168.122.209 [63469.276370] End test: t_frang.test_http_methods.FrangHttpMethodsTestCase.test_not_accepted_request_shipping_cfg_DELETE Apr 26 09:41:58 192.168.122.209 [63469.298852] Start test: t_frang.test_http_methods.FrangHttpMethodsTestCase.test_not_accepted_request_shipping_cfg_OPTIONS Apr 26 09:41:59 192.168.122.209 [63470.376472] [tdb] Start Tempesta DB Apr 26 09:41:59 192.168.122.209 [63470.499588] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:42:00 192.168.122.209 [63471.341741] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63471.341741] Maybe that's fine, but it's worth checking the [63471.341741] config - if there is no relations between the [63471.341741] names, then host name confusion attack is possible. Apr 26 09:42:00 192.168.122.209 [63471.448598] [tempesta fw] Configuration processing is completed. Apr 26 09:42:00 192.168.122.209 [63471.510273] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:42:00 192.168.122.209 [63471.542902] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:42:00 192.168.122.209 [63471.573145] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:42:01 192.168.122.209 [63471.612441] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:42:01 192.168.122.209 [63471.614159] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:42:01 192.168.122.209 [63471.615819] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:42:01 192.168.122.209 [63471.660315] [tempesta fw] Tempesta FW is ready Apr 26 09:42:01 192.168.122.209 [63471.796086] [tempesta fw] Warning: frang: restricted HTTP method for 127.0.0.2: 8 (0x100u) Apr 26 09:42:01 192.168.122.209 [63471.798435] [tempesta fw] Warning: postponed request has been filtered out: 127.0.0.2 Apr 26 09:42:01 192.168.122.209 [63472.259181] [tdb] Close table 'client0.tdb' Apr 26 09:42:01 192.168.122.209 [63472.436770] [tdb] Close table 'sessions0.tdb' Apr 26 09:42:02 192.168.122.209 [63472.676947] [tdb] Close table 'filter0.tdb' Apr 26 09:42:02 192.168.122.209 [63472.677373] [tempesta fw] modules are stopped Apr 26 09:42:02 192.168.122.209 [63472.888538] [tempesta fw] exiting... Apr 26 09:42:02 192.168.122.209 [63473.026087] [tdb] Shutdown Tempesta DB Apr 26 09:42:02 192.168.122.209 [63473.237222] End test: t_frang.test_http_methods.FrangHttpMethodsTestCase.test_not_accepted_request_shipping_cfg_OPTIONS Apr 26 09:42:02 192.168.122.209 [63473.257341] Start test: t_frang.test_http_methods.FrangHttpMethodsTestCase.test_not_accepted_request_shipping_cfg_PATCH Apr 26 09:42:03 192.168.122.209 [63474.295020] [tdb] Start Tempesta DB Apr 26 09:42:03 192.168.122.209 [63474.427287] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:42:04 192.168.122.209 [63475.269719] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63475.269719] Maybe that's fine, but it's worth checking the [63475.269719] config - if there is no relations between the [63475.269719] names, then host name confusion attack is possible. Apr 26 09:42:04 192.168.122.209 [63475.384514] [tempesta fw] Configuration processing is completed. Apr 26 09:42:04 192.168.122.209 [63475.439395] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:42:04 192.168.122.209 [63475.467219] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:42:04 192.168.122.209 [63475.495483] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:42:04 192.168.122.209 [63475.540466] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:42:04 192.168.122.209 [63475.542152] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:42:04 192.168.122.209 [63475.543792] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:42:04 192.168.122.209 [63475.596417] [tempesta fw] Tempesta FW is ready Apr 26 09:42:05 192.168.122.209 [63475.727377] [tempesta fw] Warning: frang: restricted HTTP method for 127.0.0.2: 9 (0x200u) Apr 26 09:42:05 192.168.122.209 [63475.729722] [tempesta fw] Warning: postponed request has been filtered out: 127.0.0.2 Apr 26 09:42:05 192.168.122.209 [63476.214070] [tdb] Close table 'client0.tdb' Apr 26 09:42:05 192.168.122.209 [63476.391080] [tdb] Close table 'sessions0.tdb' Apr 26 09:42:05 192.168.122.209 [63476.599074] [tdb] Close table 'filter0.tdb' Apr 26 09:42:05 192.168.122.209 [63476.599495] [tempesta fw] modules are stopped Apr 26 09:42:06 192.168.122.209 [63476.815494] [tempesta fw] exiting... Apr 26 09:42:06 192.168.122.209 [63476.938908] [tdb] Shutdown Tempesta DB Apr 26 09:42:06 192.168.122.209 [63477.127391] End test: t_frang.test_http_methods.FrangHttpMethodsTestCase.test_not_accepted_request_shipping_cfg_PATCH Apr 26 09:42:06 192.168.122.209 [63477.153694] Start test: t_frang.test_http_methods.FrangHttpMethodsTestCase.test_not_accepted_request_shipping_cfg_PUT Apr 26 09:42:07 192.168.122.209 [63478.175360] [tdb] Start Tempesta DB Apr 26 09:42:07 192.168.122.209 [63478.311808] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:42:08 192.168.122.209 [63479.137799] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63479.137799] Maybe that's fine, but it's worth checking the [63479.137799] config - if there is no relations between the [63479.137799] names, then host name confusion attack is possible. Apr 26 09:42:08 192.168.122.209 [63479.252587] [tempesta fw] Configuration processing is completed. Apr 26 09:42:08 192.168.122.209 [63479.314893] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:42:08 192.168.122.209 [63479.347458] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:42:08 192.168.122.209 [63479.378819] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:42:08 192.168.122.209 [63479.440533] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:42:08 192.168.122.209 [63479.442234] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:42:08 192.168.122.209 [63479.443874] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:42:08 192.168.122.209 [63479.484505] [tempesta fw] Tempesta FW is ready Apr 26 09:42:09 192.168.122.209 [63479.620028] [tempesta fw] Warning: frang: restricted HTTP method for 127.0.0.2: 13 (0x2000u) Apr 26 09:42:09 192.168.122.209 [63479.621115] [tempesta fw] Warning: postponed request has been filtered out: 127.0.0.2 Apr 26 09:42:09 192.168.122.209 [63480.107771] [tdb] Close table 'client0.tdb' Apr 26 09:42:09 192.168.122.209 [63480.289699] [tdb] Close table 'sessions0.tdb' Apr 26 09:42:09 192.168.122.209 [63480.523746] [tdb] Close table 'filter0.tdb' Apr 26 09:42:09 192.168.122.209 [63480.524162] [tempesta fw] modules are stopped Apr 26 09:42:10 192.168.122.209 [63480.759612] [tempesta fw] exiting... Apr 26 09:42:10 192.168.122.209 [63480.884585] [tdb] Shutdown Tempesta DB Apr 26 09:42:10 192.168.122.209 [63481.093223] End test: t_frang.test_http_methods.FrangHttpMethodsTestCase.test_not_accepted_request_shipping_cfg_PUT Apr 26 09:42:10 192.168.122.209 [63481.106598] Start test: t_frang.test_http_methods.FrangHttpMethodsTestCase.test_not_accepted_request_shipping_cfg_TRACE Apr 26 09:42:11 192.168.122.209 [63482.245362] [tdb] Start Tempesta DB Apr 26 09:42:11 192.168.122.209 [63482.386761] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:42:12 192.168.122.209 [63483.173878] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63483.173878] Maybe that's fine, but it's worth checking the [63483.173878] config - if there is no relations between the [63483.173878] names, then host name confusion attack is possible. Apr 26 09:42:12 192.168.122.209 [63483.284586] [tempesta fw] Configuration processing is completed. Apr 26 09:42:12 192.168.122.209 [63483.336252] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:42:12 192.168.122.209 [63483.363800] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:42:12 192.168.122.209 [63483.391339] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:42:12 192.168.122.209 [63483.432572] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:42:12 192.168.122.209 [63483.434258] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:42:12 192.168.122.209 [63483.435911] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:42:12 192.168.122.209 [63483.476523] [tempesta fw] Tempesta FW is ready Apr 26 09:42:12 192.168.122.209 [63483.599515] [tempesta fw] Warning: frang: restricted HTTP method for 127.0.0.2: 14 (0x4000u) Apr 26 09:42:12 192.168.122.209 [63483.601689] [tempesta fw] Warning: postponed request has been filtered out: 127.0.0.2 Apr 26 09:42:13 192.168.122.209 [63484.079352] [tdb] Close table 'client0.tdb' Apr 26 09:42:13 192.168.122.209 [63484.286205] [tdb] Close table 'sessions0.tdb' Apr 26 09:42:13 192.168.122.209 [63484.523695] [tdb] Close table 'filter0.tdb' Apr 26 09:42:13 192.168.122.209 [63484.524098] [tempesta fw] modules are stopped Apr 26 09:42:14 192.168.122.209 [63484.699930] [tempesta fw] exiting... Apr 26 09:42:14 192.168.122.209 [63484.827953] [tdb] Shutdown Tempesta DB Apr 26 09:42:14 192.168.122.209 [63485.058694] End test: t_frang.test_http_methods.FrangHttpMethodsTestCase.test_not_accepted_request_shipping_cfg_TRACE Apr 26 09:42:14 192.168.122.209 [63485.069673] Start test: t_frang.test_http_methods.FrangHttpMethodsTestCase.test_not_accepted_request_with_unknown_method Apr 26 09:42:15 192.168.122.209 [63486.114529] [tdb] Start Tempesta DB Apr 26 09:42:15 192.168.122.209 [63486.259763] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:42:16 192.168.122.209 [63487.041866] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63487.041866] Maybe that's fine, but it's worth checking the [63487.041866] config - if there is no relations between the [63487.041866] names, then host name confusion attack is possible. Apr 26 09:42:16 192.168.122.209 [63487.144649] [tempesta fw] Configuration processing is completed. Apr 26 09:42:16 192.168.122.209 [63487.195839] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:42:16 192.168.122.209 [63487.224220] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:42:16 192.168.122.209 [63487.253063] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:42:16 192.168.122.209 [63487.312619] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:42:16 192.168.122.209 [63487.314302] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:42:16 192.168.122.209 [63487.315941] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:42:16 192.168.122.209 [63487.372580] [tempesta fw] Tempesta FW is ready Apr 26 09:42:16 192.168.122.209 [63487.493352] [tempesta fw] Warning: frang: restricted HTTP method for 127.0.0.2: 17 (0x20000u) Apr 26 09:42:16 192.168.122.209 [63487.495725] [tempesta fw] Warning: postponed request has been filtered out: 127.0.0.2 Apr 26 09:42:17 192.168.122.209 [63488.001359] [tdb] Close table 'client0.tdb' Apr 26 09:42:17 192.168.122.209 [63488.193728] [tdb] Close table 'sessions0.tdb' Apr 26 09:42:17 192.168.122.209 [63488.430759] [tdb] Close table 'filter0.tdb' Apr 26 09:42:17 192.168.122.209 [63488.431200] [tempesta fw] modules are stopped Apr 26 09:42:18 192.168.122.209 [63488.618180] [tempesta fw] exiting... Apr 26 09:42:18 192.168.122.209 [63488.715289] [tdb] Shutdown Tempesta DB Apr 26 09:42:18 192.168.122.209 [63488.923543] End test: t_frang.test_http_methods.FrangHttpMethodsTestCase.test_not_accepted_request_with_unknown_method Apr 26 09:42:18 192.168.122.209 [63488.938471] Start test: t_frang.test_http_resp_code_block.HttpRespCodeBlockOneClientH2.test_not_reaching_the_limit Apr 26 09:42:19 192.168.122.209 [63490.134123] [tdb] Start Tempesta DB Apr 26 09:42:19 192.168.122.209 [63490.260997] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:42:20 192.168.122.209 [63491.082006] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63491.082006] Maybe that's fine, but it's worth checking the [63491.082006] config - if there is no relations between the [63491.082006] names, then host name confusion attack is possible. Apr 26 09:42:20 192.168.122.209 [63491.188761] [tempesta fw] Configuration processing is completed. Apr 26 09:42:20 192.168.122.209 [63491.246283] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:42:20 192.168.122.209 [63491.278788] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:42:20 192.168.122.209 [63491.310784] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:42:20 192.168.122.209 [63491.372679] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:42:20 192.168.122.209 [63491.374398] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:42:20 192.168.122.209 [63491.376665] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:42:20 192.168.122.209 [63491.412630] [tempesta fw] Tempesta FW is ready Apr 26 09:42:23 192.168.122.209 [63494.384287] [tdb] Close table 'client0.tdb' Apr 26 09:42:23 192.168.122.209 [63494.565340] [tdb] Close table 'sessions0.tdb' Apr 26 09:42:24 192.168.122.209 [63494.790745] [tdb] Close table 'filter0.tdb' Apr 26 09:42:24 192.168.122.209 [63494.791172] [tempesta fw] modules are stopped Apr 26 09:42:24 192.168.122.209 [63495.009885] [tempesta fw] exiting... Apr 26 09:42:24 192.168.122.209 [63495.144922] [tdb] Shutdown Tempesta DB Apr 26 09:42:24 192.168.122.209 [63495.370748] End test: t_frang.test_http_resp_code_block.HttpRespCodeBlockOneClientH2.test_not_reaching_the_limit Apr 26 09:42:24 192.168.122.209 [63495.381986] Start test: t_frang.test_http_resp_code_block.HttpRespCodeBlockOneClientH2.test_reaching_the_limit Apr 26 09:42:25 192.168.122.209 [63496.501183] [tdb] Start Tempesta DB Apr 26 09:42:26 192.168.122.209 [63496.641016] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:42:26 192.168.122.209 [63497.438030] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63497.438030] Maybe that's fine, but it's worth checking the [63497.438030] config - if there is no relations between the [63497.438030] names, then host name confusion attack is possible. Apr 26 09:42:26 192.168.122.209 [63497.544788] [tempesta fw] Configuration processing is completed. Apr 26 09:42:26 192.168.122.209 [63497.602194] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:42:27 192.168.122.209 [63497.644366] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:42:27 192.168.122.209 [63497.675718] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:42:27 192.168.122.209 [63497.752778] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:42:27 192.168.122.209 [63497.754531] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:42:27 192.168.122.209 [63497.756183] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:42:27 192.168.122.209 [63497.792708] [tempesta fw] Tempesta FW is ready Apr 26 09:42:27 192.168.122.209 [63498.012827] [tempesta fw] Warning: frang: http_resp_code_block limit exceeded for 127.0.0.2: 7 (lim=6) Apr 26 09:42:27 192.168.122.209 [63498.013881] [tempesta fw] Warning: response blocked: filtered out: 127.0.0.2 Apr 26 09:42:27 192.168.122.209 [63498.486983] [tdb] Close table 'client0.tdb' Apr 26 09:42:28 192.168.122.209 [63498.682283] [tdb] Close table 'sessions0.tdb' Apr 26 09:42:28 192.168.122.209 [63498.906130] [tdb] Close table 'filter0.tdb' Apr 26 09:42:28 192.168.122.209 [63498.906573] [tempesta fw] modules are stopped Apr 26 09:42:28 192.168.122.209 [63499.095324] [tempesta fw] exiting... Apr 26 09:42:28 192.168.122.209 [63499.205500] [tdb] Shutdown Tempesta DB Apr 26 09:42:28 192.168.122.209 [63499.491533] End test: t_frang.test_http_resp_code_block.HttpRespCodeBlockOneClientH2.test_reaching_the_limit Apr 26 09:42:28 192.168.122.209 [63499.504931] Start test: t_frang.test_http_resp_code_block.HttpRespCodeBlockOneClientH2.test_reaching_the_limit_2 Apr 26 09:42:30 192.168.122.209 [63500.660126] [tdb] Start Tempesta DB Apr 26 09:42:30 192.168.122.209 [63500.799300] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:42:30 192.168.122.209 [63501.558046] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63501.558046] Maybe that's fine, but it's worth checking the [63501.558046] config - if there is no relations between the [63501.558046] names, then host name confusion attack is possible. Apr 26 09:42:31 192.168.122.209 [63501.656824] [tempesta fw] Configuration processing is completed. Apr 26 09:42:31 192.168.122.209 [63501.707779] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:42:31 192.168.122.209 [63501.736009] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:42:31 192.168.122.209 [63501.763787] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:42:31 192.168.122.209 [63501.836797] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:42:31 192.168.122.209 [63501.838535] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:42:31 192.168.122.209 [63501.840183] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:42:31 192.168.122.209 [63501.876750] [tempesta fw] Tempesta FW is ready Apr 26 09:42:31 192.168.122.209 [63502.091029] [tempesta fw] Warning: frang: http_resp_code_block limit exceeded for 127.0.0.2: 6 (lim=5) Apr 26 09:42:31 192.168.122.209 [63502.092508] [tempesta fw] Warning: response blocked: filtered out: 127.0.0.2 Apr 26 09:42:31 192.168.122.209 [63502.586970] [tdb] Close table 'client0.tdb' Apr 26 09:42:32 192.168.122.209 [63502.778956] [tdb] Close table 'sessions0.tdb' Apr 26 09:42:32 192.168.122.209 [63503.017280] [tdb] Close table 'filter0.tdb' Apr 26 09:42:32 192.168.122.209 [63503.017705] [tempesta fw] modules are stopped Apr 26 09:42:32 192.168.122.209 [63503.208246] [tempesta fw] exiting... Apr 26 09:42:32 192.168.122.209 [63503.326949] [tdb] Shutdown Tempesta DB Apr 26 09:42:32 192.168.122.209 [63503.600082] End test: t_frang.test_http_resp_code_block.HttpRespCodeBlockOneClientH2.test_reaching_the_limit_2 Apr 26 09:42:33 192.168.122.209 [63503.609543] Start test: t_frang.test_http_resp_code_block.HttpRespCodeBlockOneClientHttp.test_not_reaching_the_limit Apr 26 09:42:34 192.168.122.209 [63504.686454] [tdb] Start Tempesta DB Apr 26 09:42:34 192.168.122.209 [63504.823782] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:42:34 192.168.122.209 [63505.586109] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63505.586109] Maybe that's fine, but it's worth checking the [63505.586109] config - if there is no relations between the [63505.586109] names, then host name confusion attack is possible. Apr 26 09:42:35 192.168.122.209 [63505.704838] [tempesta fw] Configuration processing is completed. Apr 26 09:42:35 192.168.122.209 [63505.780706] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:42:35 192.168.122.209 [63505.809181] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:42:35 192.168.122.209 [63505.836503] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:42:35 192.168.122.209 [63505.912854] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:42:35 192.168.122.209 [63505.914585] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:42:35 192.168.122.209 [63505.916257] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:42:35 192.168.122.209 [63505.952825] [tempesta fw] Tempesta FW is ready Apr 26 09:42:38 192.168.122.209 [63508.888884] [tdb] Close table 'client0.tdb' Apr 26 09:42:38 192.168.122.209 [63509.064833] [tdb] Close table 'sessions0.tdb' Apr 26 09:42:38 192.168.122.209 [63509.292943] [tdb] Close table 'filter0.tdb' Apr 26 09:42:38 192.168.122.209 [63509.293365] [tempesta fw] modules are stopped Apr 26 09:42:38 192.168.122.209 [63509.467519] [tempesta fw] exiting... Apr 26 09:42:38 192.168.122.209 [63509.586082] [tdb] Shutdown Tempesta DB Apr 26 09:42:39 192.168.122.209 [63509.810365] End test: t_frang.test_http_resp_code_block.HttpRespCodeBlockOneClientHttp.test_not_reaching_the_limit Apr 26 09:42:39 192.168.122.209 [63509.823179] Start test: t_frang.test_http_resp_code_block.HttpRespCodeBlockOneClientHttp.test_reaching_the_limit Apr 26 09:42:40 192.168.122.209 [63510.887497] [tdb] Start Tempesta DB Apr 26 09:42:40 192.168.122.209 [63511.028210] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:42:41 192.168.122.209 [63511.810260] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63511.810260] Maybe that's fine, but it's worth checking the [63511.810260] config - if there is no relations between the [63511.810260] names, then host name confusion attack is possible. Apr 26 09:42:41 192.168.122.209 [63511.900984] [tempesta fw] Configuration processing is completed. Apr 26 09:42:41 192.168.122.209 [63511.959305] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:42:41 192.168.122.209 [63511.991370] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:42:41 192.168.122.209 [63512.023212] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:42:41 192.168.122.209 [63512.100957] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:42:41 192.168.122.209 [63512.102717] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:42:41 192.168.122.209 [63512.104378] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:42:41 192.168.122.209 [63512.168894] [tempesta fw] Tempesta FW is ready Apr 26 09:42:41 192.168.122.209 [63512.361909] [tempesta fw] Warning: frang: http_resp_code_block limit exceeded for 127.0.0.2: 7 (lim=6) Apr 26 09:42:41 192.168.122.209 [63512.364475] [tempesta fw] Warning: response blocked: filtered out: 127.0.0.2 Apr 26 09:42:42 192.168.122.209 [63512.886595] [tdb] Close table 'client0.tdb' Apr 26 09:42:42 192.168.122.209 [63513.074156] [tdb] Close table 'sessions0.tdb' Apr 26 09:42:42 192.168.122.209 [63513.323447] [tdb] Close table 'filter0.tdb' Apr 26 09:42:42 192.168.122.209 [63513.324037] [tempesta fw] modules are stopped Apr 26 09:42:42 192.168.122.209 [63513.545872] [tempesta fw] exiting... Apr 26 09:42:43 192.168.122.209 [63513.670661] [tdb] Shutdown Tempesta DB Apr 26 09:42:43 192.168.122.209 [63513.923968] End test: t_frang.test_http_resp_code_block.HttpRespCodeBlockOneClientHttp.test_reaching_the_limit Apr 26 09:42:43 192.168.122.209 [63513.934064] Start test: t_frang.test_http_resp_code_block.HttpRespCodeBlockOneClientHttp.test_reaching_the_limit_2 Apr 26 09:42:44 192.168.122.209 [63515.045398] [tdb] Start Tempesta DB Apr 26 09:42:44 192.168.122.209 [63515.174998] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:42:45 192.168.122.209 [63515.994258] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63515.994258] Maybe that's fine, but it's worth checking the [63515.994258] config - if there is no relations between the [63515.994258] names, then host name confusion attack is possible. Apr 26 09:42:45 192.168.122.209 [63516.093038] [tempesta fw] Configuration processing is completed. Apr 26 09:42:45 192.168.122.209 [63516.150967] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:42:45 192.168.122.209 [63516.183036] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:42:45 192.168.122.209 [63516.214876] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:42:45 192.168.122.209 [63516.293033] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:42:45 192.168.122.209 [63516.294785] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:42:45 192.168.122.209 [63516.296454] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:42:45 192.168.122.209 [63516.344945] [tempesta fw] Tempesta FW is ready Apr 26 09:42:45 192.168.122.209 [63516.549663] [tempesta fw] Warning: frang: http_resp_code_block limit exceeded for 127.0.0.2: 6 (lim=5) Apr 26 09:42:45 192.168.122.209 [63516.551155] [tempesta fw] Warning: response blocked: filtered out: 127.0.0.2 Apr 26 09:42:46 192.168.122.209 [63517.014867] [tdb] Close table 'client0.tdb' Apr 26 09:42:46 192.168.122.209 [63517.220034] [tdb] Close table 'sessions0.tdb' Apr 26 09:42:46 192.168.122.209 [63517.437756] [tdb] Close table 'filter0.tdb' Apr 26 09:42:46 192.168.122.209 [63517.438185] [tempesta fw] modules are stopped Apr 26 09:42:47 192.168.122.209 [63517.636676] [tempesta fw] exiting... Apr 26 09:42:47 192.168.122.209 [63517.753017] [tdb] Shutdown Tempesta DB Apr 26 09:42:47 192.168.122.209 [63517.980940] End test: t_frang.test_http_resp_code_block.HttpRespCodeBlockOneClientHttp.test_reaching_the_limit_2 Apr 26 09:42:47 192.168.122.209 [63517.991517] Start test: t_frang.test_http_strict_host_checking.FrangHostRequiredH2TestCase.test_auto_port_mismatch Apr 26 09:42:48 192.168.122.209 [63519.061772] [tdb] Start Tempesta DB Apr 26 09:42:48 192.168.122.209 [63519.192260] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:42:49 192.168.122.209 [63519.954332] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63519.954332] Maybe that's fine, but it's worth checking the [63519.954332] config - if there is no relations between the [63519.954332] names, then host name confusion attack is possible. Apr 26 09:42:49 192.168.122.209 [63520.105056] [tempesta fw] Configuration processing is completed. Apr 26 09:42:49 192.168.122.209 [63520.158494] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:42:49 192.168.122.209 [63520.186756] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:42:49 192.168.122.209 [63520.215524] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:42:49 192.168.122.209 [63520.257040] [tempesta fw] Open listen socket on: 0.0.0.0:444 Apr 26 09:42:49 192.168.122.209 [63520.258774] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:42:49 192.168.122.209 [63520.305240] [tempesta fw] Tempesta FW is ready Apr 26 09:42:49 192.168.122.209 [63520.515214] [tempesta fw] Warning: frang: port from host header doesn't match real port for 127.0.0.2: 443 (444) Apr 26 09:42:49 192.168.122.209 [63520.517760] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 09:42:50 192.168.122.209 [63520.972478] [tdb] Close table 'client0.tdb' Apr 26 09:42:50 192.168.122.209 [63521.156057] [tdb] Close table 'sessions0.tdb' Apr 26 09:42:50 192.168.122.209 [63521.399085] [tdb] Close table 'filter0.tdb' Apr 26 09:42:50 192.168.122.209 [63521.399503] [tempesta fw] modules are stopped Apr 26 09:42:50 192.168.122.209 [63521.582309] [tempesta fw] exiting... Apr 26 09:42:51 192.168.122.209 [63521.722006] [tdb] Shutdown Tempesta DB Apr 26 09:42:51 192.168.122.209 [63521.949122] End test: t_frang.test_http_strict_host_checking.FrangHostRequiredH2TestCase.test_auto_port_mismatch Apr 26 09:42:51 192.168.122.209 [63521.962321] Start test: t_frang.test_http_strict_host_checking.FrangHostRequiredH2TestCase.test_disabled_host_http_required Apr 26 09:42:52 192.168.122.209 [63523.095714] [tdb] Start Tempesta DB Apr 26 09:42:52 192.168.122.209 [63523.231002] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:42:53 192.168.122.209 [63524.034396] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63524.034396] Maybe that's fine, but it's worth checking the [63524.034396] config - if there is no relations between the [63524.034396] names, then host name confusion attack is possible. Apr 26 09:42:53 192.168.122.209 [63524.181138] [tempesta fw] Configuration processing is completed. Apr 26 09:42:53 192.168.122.209 [63524.239486] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:42:53 192.168.122.209 [63524.273979] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:42:53 192.168.122.209 [63524.304864] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:42:53 192.168.122.209 [63524.349089] [tempesta fw] Open listen socket on: 0.0.0.0:444 Apr 26 09:42:53 192.168.122.209 [63524.350777] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:42:53 192.168.122.209 [63524.401040] [tempesta fw] Tempesta FW is ready Apr 26 09:42:54 192.168.122.209 [63525.100654] [tdb] Close table 'client0.tdb' Apr 26 09:42:54 192.168.122.209 [63525.287983] [tdb] Close table 'sessions0.tdb' Apr 26 09:42:54 192.168.122.209 [63525.530351] [tdb] Close table 'filter0.tdb' Apr 26 09:42:54 192.168.122.209 [63525.530769] [tempesta fw] modules are stopped Apr 26 09:42:55 192.168.122.209 [63525.754107] [tempesta fw] exiting... Apr 26 09:42:55 192.168.122.209 [63525.886496] [tdb] Shutdown Tempesta DB Apr 26 09:42:55 192.168.122.209 [63526.063198] End test: t_frang.test_http_strict_host_checking.FrangHostRequiredH2TestCase.test_disabled_host_http_required Apr 26 09:42:55 192.168.122.209 [63526.083465] Start test: t_frang.test_http_strict_host_checking.FrangHostRequiredH2TestCase.test_h2_authority_header_as_ip Apr 26 09:42:56 192.168.122.209 [63527.174683] [tdb] Start Tempesta DB Apr 26 09:42:56 192.168.122.209 [63527.313179] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:42:57 192.168.122.209 [63528.138408] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63528.138408] Maybe that's fine, but it's worth checking the [63528.138408] config - if there is no relations between the [63528.138408] names, then host name confusion attack is possible. Apr 26 09:42:57 192.168.122.209 [63528.293145] [tempesta fw] Configuration processing is completed. Apr 26 09:42:57 192.168.122.209 [63528.346310] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:42:57 192.168.122.209 [63528.374802] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:42:57 192.168.122.209 [63528.402291] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:42:57 192.168.122.209 [63528.461138] [tempesta fw] Open listen socket on: 0.0.0.0:444 Apr 26 09:42:57 192.168.122.209 [63528.462849] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:42:57 192.168.122.209 [63528.501090] [tempesta fw] Tempesta FW is ready Apr 26 09:42:58 192.168.122.209 [63528.697861] [tempesta fw] Warning: frang: Host header field contains IP address for 127.0.0.2 Apr 26 09:42:58 192.168.122.209 [63528.698647] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 09:42:58 192.168.122.209 [63529.198593] [tdb] Close table 'client0.tdb' Apr 26 09:42:58 192.168.122.209 [63529.387832] [tdb] Close table 'sessions0.tdb' Apr 26 09:42:59 192.168.122.209 [63529.624276] [tdb] Close table 'filter0.tdb' Apr 26 09:42:59 192.168.122.209 [63529.624690] [tempesta fw] modules are stopped Apr 26 09:42:59 192.168.122.209 [63529.803269] [tempesta fw] exiting... Apr 26 09:42:59 192.168.122.209 [63529.959530] [tdb] Shutdown Tempesta DB Apr 26 09:42:59 192.168.122.209 [63530.189348] End test: t_frang.test_http_strict_host_checking.FrangHostRequiredH2TestCase.test_h2_authority_header_as_ip Apr 26 09:42:59 192.168.122.209 [63530.200723] Start test: t_frang.test_http_strict_host_checking.FrangHostRequiredH2TestCase.test_h2_authority_header_as_ipv6 Apr 26 09:43:00 192.168.122.209 [63531.310058] [tdb] Start Tempesta DB Apr 26 09:43:00 192.168.122.209 [63531.437690] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:43:01 192.168.122.209 [63532.270486] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63532.270486] Maybe that's fine, but it's worth checking the [63532.270486] config - if there is no relations between the [63532.270486] names, then host name confusion attack is possible. Apr 26 09:43:01 192.168.122.209 [63532.409241] [tempesta fw] Configuration processing is completed. Apr 26 09:43:01 192.168.122.209 [63532.470644] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:43:01 192.168.122.209 [63532.506727] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:43:01 192.168.122.209 [63532.537997] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:43:01 192.168.122.209 [63532.593236] [tempesta fw] Open listen socket on: 0.0.0.0:444 Apr 26 09:43:01 192.168.122.209 [63532.594941] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:43:02 192.168.122.209 [63532.629149] [tempesta fw] Tempesta FW is ready Apr 26 09:43:02 192.168.122.209 [63532.769838] [tempesta fw] Warning: frang: Host header field contains IP address for 127.0.0.2 Apr 26 09:43:02 192.168.122.209 [63532.770636] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 09:43:02 192.168.122.209 [63533.219424] [tdb] Close table 'client0.tdb' Apr 26 09:43:02 192.168.122.209 [63533.430696] [tdb] Close table 'sessions0.tdb' Apr 26 09:43:03 192.168.122.209 [63533.671609] [tdb] Close table 'filter0.tdb' Apr 26 09:43:03 192.168.122.209 [63533.672031] [tempesta fw] modules are stopped Apr 26 09:43:03 192.168.122.209 [63533.909609] [tempesta fw] exiting... Apr 26 09:43:03 192.168.122.209 [63534.026137] [tdb] Shutdown Tempesta DB Apr 26 09:43:03 192.168.122.209 [63534.227147] End test: t_frang.test_http_strict_host_checking.FrangHostRequiredH2TestCase.test_h2_authority_header_as_ipv6 Apr 26 09:43:03 192.168.122.209 [63534.258925] Start test: t_frang.test_http_strict_host_checking.FrangHostRequiredH2TestCase.test_h2_different_host_and_authority_header Apr 26 09:43:04 192.168.122.209 [63535.281598] [tdb] Start Tempesta DB Apr 26 09:43:04 192.168.122.209 [63535.427141] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:43:05 192.168.122.209 [63536.226517] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63536.226517] Maybe that's fine, but it's worth checking the [63536.226517] config - if there is no relations between the [63536.226517] names, then host name confusion attack is possible. Apr 26 09:43:05 192.168.122.209 [63536.377288] [tempesta fw] Configuration processing is completed. Apr 26 09:43:05 192.168.122.209 [63536.433994] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:43:05 192.168.122.209 [63536.465716] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:43:05 192.168.122.209 [63536.497102] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:43:05 192.168.122.209 [63536.537158] [tempesta fw] Open listen socket on: 0.0.0.0:444 Apr 26 09:43:05 192.168.122.209 [63536.538940] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:43:05 192.168.122.209 [63536.577207] [tempesta fw] Tempesta FW is ready Apr 26 09:43:06 192.168.122.209 [63536.779487] [tempesta fw] Warning: frang: Request :authority differs from Host for 127.0.0.2 Apr 26 09:43:06 192.168.122.209 [63536.781744] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 09:43:06 192.168.122.209 [63537.289958] [tdb] Close table 'client0.tdb' Apr 26 09:43:06 192.168.122.209 [63537.478606] [tdb] Close table 'sessions0.tdb' Apr 26 09:43:07 192.168.122.209 [63537.719622] [tdb] Close table 'filter0.tdb' Apr 26 09:43:07 192.168.122.209 [63537.720046] [tempesta fw] modules are stopped Apr 26 09:43:07 192.168.122.209 [63537.985560] [tempesta fw] exiting... Apr 26 09:43:07 192.168.122.209 [63538.096187] [tdb] Shutdown Tempesta DB Apr 26 09:43:07 192.168.122.209 [63538.322977] End test: t_frang.test_http_strict_host_checking.FrangHostRequiredH2TestCase.test_h2_different_host_and_authority_header Apr 26 09:43:07 192.168.122.209 [63538.338677] Start test: t_frang.test_http_strict_host_checking.FrangHostRequiredH2TestCase.test_h2_header_ok Apr 26 09:43:08 192.168.122.209 [63539.442127] [tdb] Start Tempesta DB Apr 26 09:43:08 192.168.122.209 [63539.584476] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:43:09 192.168.122.209 [63540.410557] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63540.410557] Maybe that's fine, but it's worth checking the [63540.410557] config - if there is no relations between the [63540.410557] names, then host name confusion attack is possible. Apr 26 09:43:09 192.168.122.209 [63540.545338] [tempesta fw] Configuration processing is completed. Apr 26 09:43:09 192.168.122.209 [63540.592117] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:43:10 192.168.122.209 [63540.620171] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:43:10 192.168.122.209 [63540.648396] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:43:10 192.168.122.209 [63540.689295] [tempesta fw] Open listen socket on: 0.0.0.0:444 Apr 26 09:43:10 192.168.122.209 [63540.690968] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:43:10 192.168.122.209 [63540.733252] [tempesta fw] Tempesta FW is ready Apr 26 09:43:11 192.168.122.209 [63541.652955] [tdb] Close table 'client0.tdb' Apr 26 09:43:11 192.168.122.209 [63541.833229] [tdb] Close table 'sessions0.tdb' Apr 26 09:43:11 192.168.122.209 [63542.042801] [tdb] Close table 'filter0.tdb' Apr 26 09:43:11 192.168.122.209 [63542.043235] [tempesta fw] modules are stopped Apr 26 09:43:11 192.168.122.209 [63542.266669] [tempesta fw] exiting... Apr 26 09:43:11 192.168.122.209 [63542.408468] [tdb] Shutdown Tempesta DB Apr 26 09:43:12 192.168.122.209 [63542.620650] End test: t_frang.test_http_strict_host_checking.FrangHostRequiredH2TestCase.test_h2_header_ok Apr 26 09:43:12 192.168.122.209 [63542.633261] Start test: t_frang.test_http_strict_host_checking.FrangHostRequiredH2TestCase.test_h2_host_header_as_ip Apr 26 09:43:13 192.168.122.209 [63543.707424] [tdb] Start Tempesta DB Apr 26 09:43:13 192.168.122.209 [63543.845654] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:43:14 192.168.122.209 [63544.682651] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63544.682651] Maybe that's fine, but it's worth checking the [63544.682651] config - if there is no relations between the [63544.682651] names, then host name confusion attack is possible. Apr 26 09:43:14 192.168.122.209 [63544.817392] [tempesta fw] Configuration processing is completed. Apr 26 09:43:14 192.168.122.209 [63544.872602] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:43:14 192.168.122.209 [63544.902793] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:43:14 192.168.122.209 [63544.931664] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:43:14 192.168.122.209 [63544.969316] [tempesta fw] Open listen socket on: 0.0.0.0:444 Apr 26 09:43:14 192.168.122.209 [63544.970988] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:43:14 192.168.122.209 [63545.009301] [tempesta fw] Tempesta FW is ready Apr 26 09:43:14 192.168.122.209 [63545.171472] [tempesta fw] Warning: frang: Host header field contains IP address for 127.0.0.2 Apr 26 09:43:14 192.168.122.209 [63545.172264] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 09:43:15 192.168.122.209 [63545.664170] [tdb] Close table 'client0.tdb' Apr 26 09:43:15 192.168.122.209 [63545.853413] [tdb] Close table 'sessions0.tdb' Apr 26 09:43:15 192.168.122.209 [63546.067183] [tdb] Close table 'filter0.tdb' Apr 26 09:43:15 192.168.122.209 [63546.067613] [tempesta fw] modules are stopped Apr 26 09:43:15 192.168.122.209 [63546.302681] [tempesta fw] exiting... Apr 26 09:43:15 192.168.122.209 [63546.425529] [tdb] Shutdown Tempesta DB Apr 26 09:43:16 192.168.122.209 [63546.650098] End test: t_frang.test_http_strict_host_checking.FrangHostRequiredH2TestCase.test_h2_host_header_as_ip Apr 26 09:43:16 192.168.122.209 [63546.658087] Start test: t_frang.test_http_strict_host_checking.FrangHostRequiredH2TestCase.test_h2_host_header_as_ipv6 Apr 26 09:43:17 192.168.122.209 [63547.719968] [tdb] Start Tempesta DB Apr 26 09:43:17 192.168.122.209 [63547.847789] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:43:18 192.168.122.209 [63548.698795] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63548.698795] Maybe that's fine, but it's worth checking the [63548.698795] config - if there is no relations between the [63548.698795] names, then host name confusion attack is possible. Apr 26 09:43:18 192.168.122.209 [63548.837431] [tempesta fw] Configuration processing is completed. Apr 26 09:43:18 192.168.122.209 [63548.902409] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:43:18 192.168.122.209 [63548.933171] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:43:18 192.168.122.209 [63548.961937] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:43:18 192.168.122.209 [63549.009397] [tempesta fw] Open listen socket on: 0.0.0.0:444 Apr 26 09:43:18 192.168.122.209 [63549.011091] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:43:18 192.168.122.209 [63549.049344] [tempesta fw] Tempesta FW is ready Apr 26 09:43:18 192.168.122.209 [63549.244323] [tempesta fw] Warning: frang: Host header field contains IP address for 127.0.0.2 Apr 26 09:43:18 192.168.122.209 [63549.246521] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 09:43:19 192.168.122.209 [63549.740082] [tdb] Close table 'client0.tdb' Apr 26 09:43:19 192.168.122.209 [63549.935670] [tdb] Close table 'sessions0.tdb' Apr 26 09:43:19 192.168.122.209 [63550.165361] [tdb] Close table 'filter0.tdb' Apr 26 09:43:19 192.168.122.209 [63550.165787] [tempesta fw] modules are stopped Apr 26 09:43:19 192.168.122.209 [63550.370163] [tempesta fw] exiting... Apr 26 09:43:19 192.168.122.209 [63550.535575] [tdb] Shutdown Tempesta DB Apr 26 09:43:20 192.168.122.209 [63550.770111] End test: t_frang.test_http_strict_host_checking.FrangHostRequiredH2TestCase.test_h2_host_header_as_ipv6 Apr 26 09:43:20 192.168.122.209 [63550.785942] Start test: t_frang.test_http_strict_host_checking.FrangHostRequiredTestCase.test_auto_port_mismatch Apr 26 09:43:21 192.168.122.209 [63551.820659] [tdb] Start Tempesta DB Apr 26 09:43:21 192.168.122.209 [63551.952178] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:43:22 192.168.122.209 [63552.742773] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63552.742773] Maybe that's fine, but it's worth checking the [63552.742773] config - if there is no relations between the [63552.742773] names, then host name confusion attack is possible. Apr 26 09:43:22 192.168.122.209 [63552.853479] [tempesta fw] Configuration processing is completed. Apr 26 09:43:22 192.168.122.209 [63552.908912] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:43:22 192.168.122.209 [63552.939411] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:43:22 192.168.122.209 [63552.968954] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:43:22 192.168.122.209 [63553.029444] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:43:22 192.168.122.209 [63553.031128] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:43:22 192.168.122.209 [63553.032769] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:43:22 192.168.122.209 [63553.069389] [tempesta fw] Tempesta FW is ready Apr 26 09:43:22 192.168.122.209 [63553.208530] [tempesta fw] Warning: frang: port from host header doesn't match real port for 127.0.0.2: 80 (81) Apr 26 09:43:22 192.168.122.209 [63553.209721] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 09:43:23 192.168.122.209 [63553.711296] [tdb] Close table 'client0.tdb' Apr 26 09:43:23 192.168.122.209 [63553.899087] [tdb] Close table 'sessions0.tdb' Apr 26 09:43:23 192.168.122.209 [63554.123737] [tdb] Close table 'filter0.tdb' Apr 26 09:43:23 192.168.122.209 [63554.124130] [tempesta fw] modules are stopped Apr 26 09:43:23 192.168.122.209 [63554.317302] [tempesta fw] exiting... Apr 26 09:43:23 192.168.122.209 [63554.449668] [tdb] Shutdown Tempesta DB Apr 26 09:43:24 192.168.122.209 [63554.651904] End test: t_frang.test_http_strict_host_checking.FrangHostRequiredTestCase.test_auto_port_mismatch Apr 26 09:43:24 192.168.122.209 [63554.663576] Start test: t_frang.test_http_strict_host_checking.FrangHostRequiredTestCase.test_auto_port_mismatch_uri Apr 26 09:43:25 192.168.122.209 [63555.699979] [tdb] Start Tempesta DB Apr 26 09:43:25 192.168.122.209 [63555.843609] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:43:26 192.168.122.209 [63556.674841] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63556.674841] Maybe that's fine, but it's worth checking the [63556.674841] config - if there is no relations between the [63556.674841] names, then host name confusion attack is possible. Apr 26 09:43:26 192.168.122.209 [63556.785591] [tempesta fw] Configuration processing is completed. Apr 26 09:43:26 192.168.122.209 [63556.848095] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:43:26 192.168.122.209 [63556.880739] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:43:26 192.168.122.209 [63556.912055] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:43:26 192.168.122.209 [63556.965509] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:43:26 192.168.122.209 [63556.967399] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:43:26 192.168.122.209 [63556.969143] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:43:26 192.168.122.209 [63557.017459] [tempesta fw] Tempesta FW is ready Apr 26 09:43:26 192.168.122.209 [63557.162752] [tempesta fw] Warning: frang: port from host header doesn't match real port for 127.0.0.2: 80 (81) Apr 26 09:43:26 192.168.122.209 [63557.165368] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 09:43:27 192.168.122.209 [63557.651885] [tdb] Close table 'client0.tdb' Apr 26 09:43:27 192.168.122.209 [63557.832566] [tdb] Close table 'sessions0.tdb' Apr 26 09:43:27 192.168.122.209 [63558.056362] [tdb] Close table 'filter0.tdb' Apr 26 09:43:27 192.168.122.209 [63558.056780] [tempesta fw] modules are stopped Apr 26 09:43:27 192.168.122.209 [63558.283153] [tempesta fw] exiting... Apr 26 09:43:27 192.168.122.209 [63558.406698] [tdb] Shutdown Tempesta DB Apr 26 09:43:28 192.168.122.209 [63558.635979] End test: t_frang.test_http_strict_host_checking.FrangHostRequiredTestCase.test_auto_port_mismatch_uri Apr 26 09:43:28 192.168.122.209 [63558.647936] Start test: t_frang.test_http_strict_host_checking.FrangHostRequiredTestCase.test_default_host_http_required Apr 26 09:43:29 192.168.122.209 [63559.725448] [tdb] Start Tempesta DB Apr 26 09:43:29 192.168.122.209 [63559.859387] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:43:30 192.168.122.209 [63560.715096] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63560.715096] Maybe that's fine, but it's worth checking the [63560.715096] config - if there is no relations between the [63560.715096] names, then host name confusion attack is possible. Apr 26 09:43:30 192.168.122.209 [63560.825560] [tempesta fw] Configuration processing is completed. Apr 26 09:43:30 192.168.122.209 [63560.882465] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:43:30 192.168.122.209 [63560.916057] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:43:30 192.168.122.209 [63560.946198] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:43:30 192.168.122.209 [63560.989531] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:43:30 192.168.122.209 [63560.991225] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:43:30 192.168.122.209 [63560.992818] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:43:30 192.168.122.209 [63561.045484] [tempesta fw] Tempesta FW is ready Apr 26 09:43:30 192.168.122.209 [63561.180305] [tempesta fw] Warning: frang: Host header field contains IP address for 127.0.0.2 Apr 26 09:43:30 192.168.122.209 [63561.182658] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 09:43:31 192.168.122.209 [63561.667848] [tdb] Close table 'client0.tdb' Apr 26 09:43:31 192.168.122.209 [63561.855758] [tdb] Close table 'sessions0.tdb' Apr 26 09:43:31 192.168.122.209 [63562.079056] [tdb] Close table 'filter0.tdb' Apr 26 09:43:31 192.168.122.209 [63562.079470] [tempesta fw] modules are stopped Apr 26 09:43:31 192.168.122.209 [63562.293511] [tempesta fw] exiting... Apr 26 09:43:31 192.168.122.209 [63562.413101] [tdb] Shutdown Tempesta DB Apr 26 09:43:32 192.168.122.209 [63562.619669] End test: t_frang.test_http_strict_host_checking.FrangHostRequiredTestCase.test_default_host_http_required Apr 26 09:43:32 192.168.122.209 [63562.631827] Start test: t_frang.test_http_strict_host_checking.FrangHostRequiredTestCase.test_disabled_host_http_required Apr 26 09:43:33 192.168.122.209 [63563.691734] [tdb] Start Tempesta DB Apr 26 09:43:33 192.168.122.209 [63563.826602] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:43:34 192.168.122.209 [63564.650838] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63564.650838] Maybe that's fine, but it's worth checking the [63564.650838] config - if there is no relations between the [63564.650838] names, then host name confusion attack is possible. Apr 26 09:43:34 192.168.122.209 [63564.749603] [tempesta fw] Configuration processing is completed. Apr 26 09:43:34 192.168.122.209 [63564.802316] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:43:34 192.168.122.209 [63564.831798] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:43:34 192.168.122.209 [63564.869215] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:43:34 192.168.122.209 [63564.945599] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:43:34 192.168.122.209 [63564.947276] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:43:34 192.168.122.209 [63564.948888] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:43:34 192.168.122.209 [63564.985521] [tempesta fw] Tempesta FW is ready Apr 26 09:43:35 192.168.122.209 [63565.611101] [tdb] Close table 'client0.tdb' Apr 26 09:43:35 192.168.122.209 [63565.803103] [tdb] Close table 'sessions0.tdb' Apr 26 09:43:35 192.168.122.209 [63566.023670] [tdb] Close table 'filter0.tdb' Apr 26 09:43:35 192.168.122.209 [63566.024111] [tempesta fw] modules are stopped Apr 26 09:43:35 192.168.122.209 [63566.207651] [tempesta fw] exiting... Apr 26 09:43:35 192.168.122.209 [63566.306933] [tdb] Shutdown Tempesta DB Apr 26 09:43:35 192.168.122.209 [63566.494643] End test: t_frang.test_http_strict_host_checking.FrangHostRequiredTestCase.test_disabled_host_http_required Apr 26 09:43:35 192.168.122.209 [63566.508574] Start test: t_frang.test_http_strict_host_checking.FrangHostRequiredTestCase.test_host_header_as_ip Apr 26 09:43:36 192.168.122.209 [63567.595023] [tdb] Start Tempesta DB Apr 26 09:43:37 192.168.122.209 [63567.730146] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:43:37 192.168.122.209 [63568.482868] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63568.482868] Maybe that's fine, but it's worth checking the [63568.482868] config - if there is no relations between the [63568.482868] names, then host name confusion attack is possible. Apr 26 09:43:37 192.168.122.209 [63568.585602] [tempesta fw] Configuration processing is completed. Apr 26 09:43:38 192.168.122.209 [63568.637758] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:43:38 192.168.122.209 [63568.675177] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:43:38 192.168.122.209 [63568.702690] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:43:38 192.168.122.209 [63568.737590] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:43:38 192.168.122.209 [63568.739288] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:43:38 192.168.122.209 [63568.740892] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:43:38 192.168.122.209 [63568.793567] [tempesta fw] Tempesta FW is ready Apr 26 09:43:38 192.168.122.209 [63568.925374] [tempesta fw] Warning: frang: Host header field contains IP address for 127.0.0.2 Apr 26 09:43:38 192.168.122.209 [63568.927824] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 09:43:38 192.168.122.209 [63569.397797] [tdb] Close table 'client0.tdb' Apr 26 09:43:38 192.168.122.209 [63569.584396] [tdb] Close table 'sessions0.tdb' Apr 26 09:43:39 192.168.122.209 [63569.806972] [tdb] Close table 'filter0.tdb' Apr 26 09:43:39 192.168.122.209 [63569.807400] [tempesta fw] modules are stopped Apr 26 09:43:39 192.168.122.209 [63570.006918] [tempesta fw] exiting... Apr 26 09:43:39 192.168.122.209 [63570.144533] [tdb] Shutdown Tempesta DB Apr 26 09:43:39 192.168.122.209 [63570.356835] End test: t_frang.test_http_strict_host_checking.FrangHostRequiredTestCase.test_host_header_as_ip Apr 26 09:43:39 192.168.122.209 [63570.367139] Start test: t_frang.test_http_strict_host_checking.FrangHostRequiredTestCase.test_host_header_as_ip6 Apr 26 09:43:40 192.168.122.209 [63571.415397] [tdb] Start Tempesta DB Apr 26 09:43:40 192.168.122.209 [63571.546155] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:43:41 192.168.122.209 [63572.318880] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63572.318880] Maybe that's fine, but it's worth checking the [63572.318880] config - if there is no relations between the [63572.318880] names, then host name confusion attack is possible. Apr 26 09:43:41 192.168.122.209 [63572.425758] [tempesta fw] Configuration processing is completed. Apr 26 09:43:41 192.168.122.209 [63572.484411] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:43:41 192.168.122.209 [63572.512242] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:43:41 192.168.122.209 [63572.540536] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:43:41 192.168.122.209 [63572.585647] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:43:41 192.168.122.209 [63572.587307] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:43:41 192.168.122.209 [63572.588910] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:43:42 192.168.122.209 [63572.641581] [tempesta fw] Tempesta FW is ready Apr 26 09:43:42 192.168.122.209 [63572.775145] [tempesta fw] Warning: frang: Host header field contains IP address for 127.0.0.2 Apr 26 09:43:42 192.168.122.209 [63572.775932] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 09:43:42 192.168.122.209 [63573.246437] [tdb] Close table 'client0.tdb' Apr 26 09:43:42 192.168.122.209 [63573.435237] [tdb] Close table 'sessions0.tdb' Apr 26 09:43:43 192.168.122.209 [63573.678902] [tdb] Close table 'filter0.tdb' Apr 26 09:43:43 192.168.122.209 [63573.679332] [tempesta fw] modules are stopped Apr 26 09:43:43 192.168.122.209 [63573.893880] [tempesta fw] exiting... Apr 26 09:43:43 192.168.122.209 [63574.003867] [tdb] Shutdown Tempesta DB Apr 26 09:43:43 192.168.122.209 [63574.227841] End test: t_frang.test_http_strict_host_checking.FrangHostRequiredTestCase.test_host_header_as_ip6 Apr 26 09:43:43 192.168.122.209 [63574.243897] Start test: t_frang.test_http_strict_host_checking.FrangHostRequiredTestCase.test_host_header_mismatch Apr 26 09:43:44 192.168.122.209 [63575.340778] [tdb] Start Tempesta DB Apr 26 09:43:44 192.168.122.209 [63575.458729] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:43:45 192.168.122.209 [63576.274883] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63576.274883] Maybe that's fine, but it's worth checking the [63576.274883] config - if there is no relations between the [63576.274883] names, then host name confusion attack is possible. Apr 26 09:43:45 192.168.122.209 [63576.381693] [tempesta fw] Configuration processing is completed. Apr 26 09:43:45 192.168.122.209 [63576.439097] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:43:45 192.168.122.209 [63576.471158] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:43:45 192.168.122.209 [63576.502636] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:43:45 192.168.122.209 [63576.545681] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:43:45 192.168.122.209 [63576.547405] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:43:45 192.168.122.209 [63576.549146] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:43:45 192.168.122.209 [63576.589660] [tempesta fw] Tempesta FW is ready Apr 26 09:43:46 192.168.122.209 [63576.731805] [tempesta fw] Warning: frang: Request host from absolute URI differs from Host header for 127.0.0.2 Apr 26 09:43:46 192.168.122.209 [63576.733203] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 09:43:46 192.168.122.209 [63577.216518] [tdb] Close table 'client0.tdb' Apr 26 09:43:46 192.168.122.209 [63577.404813] [tdb] Close table 'sessions0.tdb' Apr 26 09:43:47 192.168.122.209 [63577.624843] [tdb] Close table 'filter0.tdb' Apr 26 09:43:47 192.168.122.209 [63577.625267] [tempesta fw] modules are stopped Apr 26 09:43:47 192.168.122.209 [63577.810539] [tempesta fw] exiting... Apr 26 09:43:47 192.168.122.209 [63577.927018] [tdb] Shutdown Tempesta DB Apr 26 09:43:47 192.168.122.209 [63578.126458] End test: t_frang.test_http_strict_host_checking.FrangHostRequiredTestCase.test_host_header_mismatch Apr 26 09:43:47 192.168.122.209 [63578.136243] Start test: t_frang.test_http_strict_host_checking.FrangHostRequiredTestCase.test_host_header_mismatch_empty Apr 26 09:43:48 192.168.122.209 [63579.159671] [tdb] Start Tempesta DB Apr 26 09:43:48 192.168.122.209 [63579.287855] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:43:49 192.168.122.209 [63580.082952] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63580.082952] Maybe that's fine, but it's worth checking the [63580.082952] config - if there is no relations between the [63580.082952] names, then host name confusion attack is possible. Apr 26 09:43:49 192.168.122.209 [63580.205718] [tempesta fw] Configuration processing is completed. Apr 26 09:43:49 192.168.122.209 [63580.263480] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:43:49 192.168.122.209 [63580.295574] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:43:49 192.168.122.209 [63580.325583] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:43:49 192.168.122.209 [63580.369698] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:43:49 192.168.122.209 [63580.371417] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:43:49 192.168.122.209 [63580.373045] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:43:49 192.168.122.209 [63580.417662] [tempesta fw] Tempesta FW is ready Apr 26 09:43:49 192.168.122.209 [63580.556695] [tempesta fw] Warning: frang: Request host from absolute URI differs from Host header for 127.0.0.2 Apr 26 09:43:49 192.168.122.209 [63580.557914] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 09:43:50 192.168.122.209 [63581.058033] [tdb] Close table 'client0.tdb' Apr 26 09:43:50 192.168.122.209 [63581.247693] [tdb] Close table 'sessions0.tdb' Apr 26 09:43:50 192.168.122.209 [63581.494507] [tdb] Close table 'filter0.tdb' Apr 26 09:43:50 192.168.122.209 [63581.494952] [tempesta fw] modules are stopped Apr 26 09:43:51 192.168.122.209 [63581.734771] [tempesta fw] exiting... Apr 26 09:43:51 192.168.122.209 [63581.864539] [tdb] Shutdown Tempesta DB Apr 26 09:43:51 192.168.122.209 [63582.076867] End test: t_frang.test_http_strict_host_checking.FrangHostRequiredTestCase.test_host_header_mismatch_empty Apr 26 09:43:51 192.168.122.209 [63582.091136] Start test: t_frang.test_http_strict_host_checking.FrangHostRequiredTestCase.test_host_header_mismatch_port_in_host Apr 26 09:43:52 192.168.122.209 [63583.124922] [tdb] Start Tempesta DB Apr 26 09:43:52 192.168.122.209 [63583.254201] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:43:53 192.168.122.209 [63584.047036] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63584.047036] Maybe that's fine, but it's worth checking the [63584.047036] config - if there is no relations between the [63584.047036] names, then host name confusion attack is possible. Apr 26 09:43:53 192.168.122.209 [63584.153767] [tempesta fw] Configuration processing is completed. Apr 26 09:43:53 192.168.122.209 [63584.208698] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:43:53 192.168.122.209 [63584.241300] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:43:53 192.168.122.209 [63584.271541] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:43:53 192.168.122.209 [63584.329659] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:43:53 192.168.122.209 [63584.331876] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:43:53 192.168.122.209 [63584.333509] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:43:53 192.168.122.209 [63584.377725] [tempesta fw] Tempesta FW is ready Apr 26 09:43:53 192.168.122.209 [63584.537095] [tempesta fw] Warning: frang: port from host header doesn't match port from uri for 127.0.0.2: 80 (81) Apr 26 09:43:53 192.168.122.209 [63584.538286] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 09:43:54 192.168.122.209 [63585.015859] [tdb] Close table 'client0.tdb' Apr 26 09:43:54 192.168.122.209 [63585.203883] [tdb] Close table 'sessions0.tdb' Apr 26 09:43:54 192.168.122.209 [63585.442101] [tdb] Close table 'filter0.tdb' Apr 26 09:43:54 192.168.122.209 [63585.442521] [tempesta fw] modules are stopped Apr 26 09:43:55 192.168.122.209 [63585.631511] [tempesta fw] exiting... Apr 26 09:43:55 192.168.122.209 [63585.777658] [tdb] Shutdown Tempesta DB Apr 26 09:43:55 192.168.122.209 [63585.998574] End test: t_frang.test_http_strict_host_checking.FrangHostRequiredTestCase.test_host_header_mismatch_port_in_host Apr 26 09:43:55 192.168.122.209 [63586.021229] Start test: t_frang.test_http_strict_host_checking.FrangHostRequiredTestCase.test_host_header_no_port_in_host Apr 26 09:43:56 192.168.122.209 [63587.088794] [tdb] Start Tempesta DB Apr 26 09:43:56 192.168.122.209 [63587.212113] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:43:57 192.168.122.209 [63588.030998] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63588.030998] Maybe that's fine, but it's worth checking the [63588.030998] config - if there is no relations between the [63588.030998] names, then host name confusion attack is possible. Apr 26 09:43:57 192.168.122.209 [63588.130129] [tempesta fw] Configuration processing is completed. Apr 26 09:43:57 192.168.122.209 [63588.182196] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:43:57 192.168.122.209 [63588.210341] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:43:57 192.168.122.209 [63588.237766] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:43:57 192.168.122.209 [63588.301773] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:43:57 192.168.122.209 [63588.303454] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:43:57 192.168.122.209 [63588.305050] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:43:57 192.168.122.209 [63588.341732] [tempesta fw] Tempesta FW is ready Apr 26 09:43:58 192.168.122.209 [63588.991440] [tdb] Close table 'client0.tdb' Apr 26 09:43:58 192.168.122.209 [63589.185070] [tdb] Close table 'sessions0.tdb' Apr 26 09:43:58 192.168.122.209 [63589.433361] [tdb] Close table 'filter0.tdb' Apr 26 09:43:58 192.168.122.209 [63589.434210] [tempesta fw] modules are stopped Apr 26 09:43:59 192.168.122.209 [63589.650631] [tempesta fw] exiting... Apr 26 09:43:59 192.168.122.209 [63589.769237] [tdb] Shutdown Tempesta DB Apr 26 09:43:59 192.168.122.209 [63589.959349] End test: t_frang.test_http_strict_host_checking.FrangHostRequiredTestCase.test_host_header_no_port_in_host Apr 26 09:43:59 192.168.122.209 [63589.972767] Start test: t_frang.test_http_strict_host_checking.FrangHostRequiredTestCase.test_host_header_no_port_in_uri Apr 26 09:44:00 192.168.122.209 [63590.989565] [tdb] Start Tempesta DB Apr 26 09:44:00 192.168.122.209 [63591.122802] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:44:01 192.168.122.209 [63591.903083] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63591.903083] Maybe that's fine, but it's worth checking the [63591.903083] config - if there is no relations between the [63591.903083] names, then host name confusion attack is possible. Apr 26 09:44:01 192.168.122.209 [63592.001874] [tempesta fw] Configuration processing is completed. Apr 26 09:44:01 192.168.122.209 [63592.066744] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:44:01 192.168.122.209 [63592.098905] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:44:01 192.168.122.209 [63592.129363] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:44:01 192.168.122.209 [63592.173811] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:44:01 192.168.122.209 [63592.175505] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:44:01 192.168.122.209 [63592.177113] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:44:01 192.168.122.209 [63592.229732] [tempesta fw] Tempesta FW is ready Apr 26 09:44:02 192.168.122.209 [63592.856064] [tdb] Close table 'client0.tdb' Apr 26 09:44:02 192.168.122.209 [63593.035007] [tdb] Close table 'sessions0.tdb' Apr 26 09:44:02 192.168.122.209 [63593.264806] [tdb] Close table 'filter0.tdb' Apr 26 09:44:02 192.168.122.209 [63593.265268] [tempesta fw] modules are stopped Apr 26 09:44:02 192.168.122.209 [63593.449166] [tempesta fw] exiting... Apr 26 09:44:02 192.168.122.209 [63593.567912] [tdb] Shutdown Tempesta DB Apr 26 09:44:03 192.168.122.209 [63593.770007] End test: t_frang.test_http_strict_host_checking.FrangHostRequiredTestCase.test_host_header_no_port_in_uri Apr 26 09:44:03 192.168.122.209 [63593.794860] Start test: t_frang.test_http_strict_host_checking.FrangHostRequiredTestCase.test_host_header_set_ok Apr 26 09:44:04 192.168.122.209 [63594.896207] [tdb] Start Tempesta DB Apr 26 09:44:04 192.168.122.209 [63595.031587] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:44:05 192.168.122.209 [63595.818752] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63595.818752] Maybe that's fine, but it's worth checking the [63595.818752] config - if there is no relations between the [63595.818752] names, then host name confusion attack is possible. Apr 26 09:44:05 192.168.122.209 [63595.917902] [tempesta fw] Configuration processing is completed. Apr 26 09:44:05 192.168.122.209 [63595.972933] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:44:05 192.168.122.209 [63596.003841] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:44:05 192.168.122.209 [63596.034499] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:44:05 192.168.122.209 [63596.081855] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:44:05 192.168.122.209 [63596.083560] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:44:05 192.168.122.209 [63596.085164] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:44:05 192.168.122.209 [63596.121812] [tempesta fw] Tempesta FW is ready Apr 26 09:44:06 192.168.122.209 [63596.880064] [tdb] Close table 'client0.tdb' Apr 26 09:44:06 192.168.122.209 [63597.075434] [tdb] Close table 'sessions0.tdb' Apr 26 09:44:06 192.168.122.209 [63597.320984] [tdb] Close table 'filter0.tdb' Apr 26 09:44:06 192.168.122.209 [63597.321408] [tempesta fw] modules are stopped Apr 26 09:44:06 192.168.122.209 [63597.547480] [tempesta fw] exiting... Apr 26 09:44:07 192.168.122.209 [63597.664533] [tdb] Shutdown Tempesta DB Apr 26 09:44:07 192.168.122.209 [63597.842354] End test: t_frang.test_http_strict_host_checking.FrangHostRequiredTestCase.test_host_header_set_ok Apr 26 09:44:07 192.168.122.209 [63597.858522] Start test: t_frang.test_http_strict_host_checking.FrangHostRequiredTestCase.test_host_header_with_old_proto Apr 26 09:44:08 192.168.122.209 [63598.975846] [tdb] Start Tempesta DB Apr 26 09:44:08 192.168.122.209 [63599.108819] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:44:09 192.168.122.209 [63599.891147] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63599.891147] Maybe that's fine, but it's worth checking the [63599.891147] config - if there is no relations between the [63599.891147] names, then host name confusion attack is possible. Apr 26 09:44:09 192.168.122.209 [63599.993916] [tempesta fw] Configuration processing is completed. Apr 26 09:44:09 192.168.122.209 [63600.051323] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:44:09 192.168.122.209 [63600.079676] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:44:09 192.168.122.209 [63600.107709] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:44:09 192.168.122.209 [63600.157903] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:44:09 192.168.122.209 [63600.159595] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:44:09 192.168.122.209 [63600.161185] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:44:09 192.168.122.209 [63600.197840] [tempesta fw] Tempesta FW is ready Apr 26 09:44:09 192.168.122.209 [63600.326816] [tempesta fw] Warning: frang: Host header field in protocol prior to HTTP/1.1 for 127.0.0.2 Apr 26 09:44:09 192.168.122.209 [63600.329400] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 09:44:10 192.168.122.209 [63600.813389] [tdb] Close table 'client0.tdb' Apr 26 09:44:10 192.168.122.209 [63601.010668] [tdb] Close table 'sessions0.tdb' Apr 26 09:44:10 192.168.122.209 [63601.258154] [tdb] Close table 'filter0.tdb' Apr 26 09:44:10 192.168.122.209 [63601.258652] [tempesta fw] modules are stopped Apr 26 09:44:10 192.168.122.209 [63601.433994] [tempesta fw] exiting... Apr 26 09:44:10 192.168.122.209 [63601.551708] [tdb] Shutdown Tempesta DB Apr 26 09:44:11 192.168.122.209 [63601.787495] End test: t_frang.test_http_strict_host_checking.FrangHostRequiredTestCase.test_host_header_with_old_proto Apr 26 09:44:11 192.168.122.209 [63601.798998] Start test: t_frang.test_ip_block.FrangIpBlockConn.test_off Apr 26 09:44:12 192.168.122.209 [63603.497684] [tdb] Start Tempesta DB Apr 26 09:44:13 192.168.122.209 [63603.625194] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:44:13 192.168.122.209 [63604.249954] [tempesta fw] Configuration processing is completed. Apr 26 09:44:13 192.168.122.209 [63604.317859] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:44:14 192.168.122.209 [63605.026447] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:44:14 192.168.122.209 [63605.073469] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:44:14 192.168.122.209 [63605.118976] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:44:14 192.168.122.209 [63605.225948] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:44:14 192.168.122.209 [63605.277889] [tempesta fw] Tempesta FW is ready Apr 26 09:44:14 192.168.122.209 [63605.411063] [tempesta fw] Warning: frang: new connections rate exceeded for 127.0.0.2: 2 (lim=1) Apr 26 09:44:17 192.168.122.209 [63607.686981] [tdb] Close table 'client0.tdb' Apr 26 09:44:17 192.168.122.209 [63607.875489] [tdb] Close table 'sessions0.tdb' Apr 26 09:44:20 192.168.122.209 [63611.111329] [tdb] Close table 'cache0.tdb' Apr 26 09:44:20 192.168.122.209 [63611.364559] [tdb] Close table 'filter0.tdb' Apr 26 09:44:20 192.168.122.209 [63611.364982] [tempesta fw] modules are stopped Apr 26 09:44:20 192.168.122.209 [63611.557534] [tempesta fw] exiting... Apr 26 09:44:21 192.168.122.209 [63611.692124] [tdb] Shutdown Tempesta DB Apr 26 09:44:21 192.168.122.209 [63611.912774] End test: t_frang.test_ip_block.FrangIpBlockConn.test_off Apr 26 09:44:21 192.168.122.209 [63611.924881] Start test: t_frang.test_ip_block.FrangIpBlockConn.test_on Apr 26 09:44:22 192.168.122.209 [63613.072468] [tdb] Start Tempesta DB Apr 26 09:44:22 192.168.122.209 [63613.193793] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:44:23 192.168.122.209 [63614.562130] [tempesta fw] Configuration processing is completed. Apr 26 09:44:24 192.168.122.209 [63614.617795] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:44:24 192.168.122.209 [63615.033358] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:44:24 192.168.122.209 [63615.064144] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:44:24 192.168.122.209 [63615.092154] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:44:24 192.168.122.209 [63615.158034] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:44:24 192.168.122.209 [63615.209996] [tempesta fw] Tempesta FW is ready Apr 26 09:44:24 192.168.122.209 [63615.340902] [tempesta fw] Warning: frang: new connections rate exceeded for 127.0.0.2: 3 (lim=2) Apr 26 09:44:24 192.168.122.209 [63615.342397] [tempesta fw] Warning: block client: 127.0.0.2 Apr 26 09:45:25 192.168.122.209 [63675.988521] [tdb] Close table 'client0.tdb' Apr 26 09:45:25 192.168.122.209 [63676.178277] [tdb] Close table 'sessions0.tdb' Apr 26 09:45:28 192.168.122.209 [63679.395636] [tdb] Close table 'cache0.tdb' Apr 26 09:45:29 192.168.122.209 [63679.639752] [tdb] Close table 'filter0.tdb' Apr 26 09:45:29 192.168.122.209 [63679.640175] [tempesta fw] modules are stopped Apr 26 09:45:29 192.168.122.209 [63679.802970] [tempesta fw] exiting... Apr 26 09:45:29 192.168.122.209 [63679.954265] [tdb] Shutdown Tempesta DB Apr 26 09:45:29 192.168.122.209 [63680.183960] End test: t_frang.test_ip_block.FrangIpBlockConn.test_on Apr 26 09:45:29 192.168.122.209 [63680.204112] Start test: t_frang.test_ip_block.FrangIpBlockMsg.test_off Apr 26 09:45:30 192.168.122.209 [63681.327556] [tdb] Start Tempesta DB Apr 26 09:45:30 192.168.122.209 [63681.464536] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:45:32 192.168.122.209 [63682.778692] [tempesta fw] Configuration processing is completed. Apr 26 09:45:32 192.168.122.209 [63682.833719] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:45:32 192.168.122.209 [63683.243101] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:45:32 192.168.122.209 [63683.273104] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:45:32 192.168.122.209 [63683.298371] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:45:32 192.168.122.209 [63683.350728] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:45:32 192.168.122.209 [63683.390650] [tempesta fw] Tempesta FW is ready Apr 26 09:45:32 192.168.122.209 [63683.522428] [tempesta fw] Warning: frang: Host header field contains IP address for 127.0.0.2 Apr 26 09:45:32 192.168.122.209 [63683.524674] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 09:45:37 192.168.122.209 [63687.694778] [tdb] Close table 'client0.tdb' Apr 26 09:45:37 192.168.122.209 [63687.884998] [tdb] Close table 'sessions0.tdb' Apr 26 09:45:40 192.168.122.209 [63691.549493] [tdb] Close table 'cache0.tdb' Apr 26 09:45:41 192.168.122.209 [63691.823273] [tdb] Close table 'filter0.tdb' Apr 26 09:45:41 192.168.122.209 [63691.823705] [tempesta fw] modules are stopped Apr 26 09:45:41 192.168.122.209 [63692.048217] [tempesta fw] exiting... Apr 26 09:45:41 192.168.122.209 [63692.197647] [tdb] Shutdown Tempesta DB Apr 26 09:45:41 192.168.122.209 [63692.416987] End test: t_frang.test_ip_block.FrangIpBlockMsg.test_off Apr 26 09:45:41 192.168.122.209 [63692.432862] Start test: t_frang.test_ip_block.FrangIpBlockMsg.test_on Apr 26 09:45:42 192.168.122.209 [63693.513922] [tdb] Start Tempesta DB Apr 26 09:45:43 192.168.122.209 [63693.651901] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:45:44 192.168.122.209 [63695.014902] [tempesta fw] Configuration processing is completed. Apr 26 09:45:44 192.168.122.209 [63695.071294] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:45:44 192.168.122.209 [63695.492946] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:45:44 192.168.122.209 [63695.519388] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:45:44 192.168.122.209 [63695.568965] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:45:45 192.168.122.209 [63695.622858] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:45:45 192.168.122.209 [63695.662783] [tempesta fw] Tempesta FW is ready Apr 26 09:45:45 192.168.122.209 [63695.897778] [tempesta fw] Warning: frang: Host header field contains IP address for 127.0.0.2 Apr 26 09:45:45 192.168.122.209 [63695.899670] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 09:45:45 192.168.122.209 [63695.901332] [tempesta fw] Warning: block client: 127.0.0.2 Apr 26 09:46:45 192.168.122.209 [63756.602012] [tdb] Close table 'client0.tdb' Apr 26 09:46:46 192.168.122.209 [63756.786818] [tdb] Close table 'sessions0.tdb' Apr 26 09:46:49 192.168.122.209 [63759.962043] [tdb] Close table 'cache0.tdb' Apr 26 09:46:49 192.168.122.209 [63760.223710] [tdb] Close table 'filter0.tdb' Apr 26 09:46:49 192.168.122.209 [63760.224148] [tempesta fw] modules are stopped Apr 26 09:46:49 192.168.122.209 [63760.403865] [tempesta fw] exiting... Apr 26 09:46:49 192.168.122.209 [63760.528941] [tdb] Shutdown Tempesta DB Apr 26 09:46:50 192.168.122.209 [63760.740404] End test: t_frang.test_ip_block.FrangIpBlockMsg.test_on Apr 26 09:46:50 192.168.122.209 [63760.764402] Start test: t_frang.test_length.FrangLengthH2.test_body_len Apr 26 09:46:51 192.168.122.209 [63761.829264] [tdb] Start Tempesta DB Apr 26 09:46:51 192.168.122.209 [63761.967838] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:46:52 192.168.122.209 [63763.512840] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63763.512840] Maybe that's fine, but it's worth checking the [63763.512840] config - if there is no relations between the [63763.512840] names, then host name confusion attack is possible. Apr 26 09:46:53 192.168.122.209 [63763.615587] [tempesta fw] Configuration processing is completed. Apr 26 09:46:53 192.168.122.209 [63763.673176] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:46:53 192.168.122.209 [63763.704470] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:46:53 192.168.122.209 [63763.734851] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:46:53 192.168.122.209 [63763.783542] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:46:53 192.168.122.209 [63763.785287] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:46:53 192.168.122.209 [63763.787019] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:46:53 192.168.122.209 [63763.823476] [tempesta fw] Tempesta FW is ready Apr 26 09:46:53 192.168.122.209 [63763.980498] [tempesta fw] Warning: frang: HTTP body length exceeded for 127.0.0.2: 20 (lim=10) Apr 26 09:46:53 192.168.122.209 [63763.981253] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 09:46:53 192.168.122.209 [63764.450640] [tdb] Close table 'client0.tdb' Apr 26 09:46:54 192.168.122.209 [63764.638817] [tdb] Close table 'sessions0.tdb' Apr 26 09:46:54 192.168.122.209 [63764.868698] [tdb] Close table 'filter0.tdb' Apr 26 09:46:54 192.168.122.209 [63764.869105] [tempesta fw] modules are stopped Apr 26 09:46:54 192.168.122.209 [63765.063358] [tempesta fw] exiting... Apr 26 09:46:54 192.168.122.209 [63765.176182] [tdb] Shutdown Tempesta DB Apr 26 09:46:54 192.168.122.209 [63765.386826] End test: t_frang.test_length.FrangLengthH2.test_body_len Apr 26 09:46:54 192.168.122.209 [63765.413157] Start test: t_frang.test_length.FrangLengthH2.test_body_len_without_reaching_the_limit Apr 26 09:46:55 192.168.122.209 [63766.467754] [tdb] Start Tempesta DB Apr 26 09:46:55 192.168.122.209 [63766.599403] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:46:56 192.168.122.209 [63767.376803] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63767.376803] Maybe that's fine, but it's worth checking the [63767.376803] config - if there is no relations between the [63767.376803] names, then host name confusion attack is possible. Apr 26 09:46:56 192.168.122.209 [63767.475615] [tempesta fw] Configuration processing is completed. Apr 26 09:46:56 192.168.122.209 [63767.527145] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:46:56 192.168.122.209 [63767.554942] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:46:56 192.168.122.209 [63767.582026] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:46:57 192.168.122.209 [63767.623567] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:46:57 192.168.122.209 [63767.625232] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:46:57 192.168.122.209 [63767.626877] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:46:57 192.168.122.209 [63767.663523] [tempesta fw] Tempesta FW is ready Apr 26 09:46:57 192.168.122.209 [63768.355392] [tdb] Close table 'client0.tdb' Apr 26 09:46:57 192.168.122.209 [63768.548303] [tdb] Close table 'sessions0.tdb' Apr 26 09:46:58 192.168.122.209 [63768.759806] [tdb] Close table 'filter0.tdb' Apr 26 09:46:58 192.168.122.209 [63768.760226] [tempesta fw] modules are stopped Apr 26 09:46:58 192.168.122.209 [63768.968409] [tempesta fw] exiting... Apr 26 09:46:58 192.168.122.209 [63769.078884] [tdb] Shutdown Tempesta DB Apr 26 09:46:58 192.168.122.209 [63769.299714] End test: t_frang.test_length.FrangLengthH2.test_body_len_without_reaching_the_limit Apr 26 09:46:58 192.168.122.209 [63769.312395] Start test: t_frang.test_length.FrangLengthH2.test_body_len_without_reaching_the_limit_zero_len Apr 26 09:46:59 192.168.122.209 [63770.296295] [tdb] Start Tempesta DB Apr 26 09:46:59 192.168.122.209 [63770.420738] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:47:00 192.168.122.209 [63771.148866] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63771.148866] Maybe that's fine, but it's worth checking the [63771.148866] config - if there is no relations between the [63771.148866] names, then host name confusion attack is possible. Apr 26 09:47:00 192.168.122.209 [63771.247652] [tempesta fw] Configuration processing is completed. Apr 26 09:47:00 192.168.122.209 [63771.309547] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:47:00 192.168.122.209 [63771.339770] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:47:00 192.168.122.209 [63771.368993] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:47:00 192.168.122.209 [63771.415626] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:47:00 192.168.122.209 [63771.417376] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:47:00 192.168.122.209 [63771.419039] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:47:00 192.168.122.209 [63771.455577] [tempesta fw] Tempesta FW is ready Apr 26 09:47:01 192.168.122.209 [63772.106199] [tdb] Close table 'client0.tdb' Apr 26 09:47:01 192.168.122.209 [63772.305081] [tdb] Close table 'sessions0.tdb' Apr 26 09:47:01 192.168.122.209 [63772.545832] [tdb] Close table 'filter0.tdb' Apr 26 09:47:01 192.168.122.209 [63772.546251] [tempesta fw] modules are stopped Apr 26 09:47:02 192.168.122.209 [63772.711739] [tempesta fw] exiting... Apr 26 09:47:02 192.168.122.209 [63772.829167] [tdb] Shutdown Tempesta DB Apr 26 09:47:02 192.168.122.209 [63773.011002] End test: t_frang.test_length.FrangLengthH2.test_body_len_without_reaching_the_limit_zero_len Apr 26 09:47:02 192.168.122.209 [63773.026757] Start test: t_frang.test_length.FrangLengthH2.test_http_hdr_len_huffman Apr 26 09:47:03 192.168.122.209 [63774.003120] [tdb] Start Tempesta DB Apr 26 09:47:03 192.168.122.209 [63774.130391] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:47:04 192.168.122.209 [63774.885499] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63774.885499] Maybe that's fine, but it's worth checking the [63774.885499] config - if there is no relations between the [63774.885499] names, then host name confusion attack is possible. Apr 26 09:47:04 192.168.122.209 [63774.991679] [tempesta fw] Configuration processing is completed. Apr 26 09:47:04 192.168.122.209 [63775.048591] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:47:04 192.168.122.209 [63775.079071] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:47:04 192.168.122.209 [63775.110344] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:47:04 192.168.122.209 [63775.159663] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:47:04 192.168.122.209 [63775.161333] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:47:04 192.168.122.209 [63775.162968] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:47:04 192.168.122.209 [63775.235608] [tempesta fw] Tempesta FW is ready Apr 26 09:47:04 192.168.122.209 [63775.438418] [tempesta fw] Warning: frang: HTTP header length exceeded for 127.0.0.2: 358 (lim=300) Apr 26 09:47:05 192.168.122.209 [63775.913286] [tdb] Close table 'client0.tdb' Apr 26 09:47:05 192.168.122.209 [63776.100337] [tdb] Close table 'sessions0.tdb' Apr 26 09:47:05 192.168.122.209 [63776.340833] [tdb] Close table 'filter0.tdb' Apr 26 09:47:05 192.168.122.209 [63776.341359] [tempesta fw] modules are stopped Apr 26 09:47:05 192.168.122.209 [63776.569536] [tempesta fw] exiting... Apr 26 09:47:06 192.168.122.209 [63776.694692] [tdb] Shutdown Tempesta DB Apr 26 09:47:06 192.168.122.209 [63776.941085] End test: t_frang.test_length.FrangLengthH2.test_http_hdr_len_huffman Apr 26 09:47:06 192.168.122.209 [63776.962818] Start test: t_frang.test_length.FrangLengthH2.test_http_hdr_len_no_huffman Apr 26 09:47:07 192.168.122.209 [63777.998706] [tdb] Start Tempesta DB Apr 26 09:47:07 192.168.122.209 [63778.132542] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:47:08 192.168.122.209 [63778.972921] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63778.972921] Maybe that's fine, but it's worth checking the [63778.972921] config - if there is no relations between the [63778.972921] names, then host name confusion attack is possible. Apr 26 09:47:08 192.168.122.209 [63779.091874] [tempesta fw] Configuration processing is completed. Apr 26 09:47:08 192.168.122.209 [63779.147418] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:47:08 192.168.122.209 [63779.173828] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:47:08 192.168.122.209 [63779.202241] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:47:08 192.168.122.209 [63779.243706] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:47:08 192.168.122.209 [63779.245378] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:47:08 192.168.122.209 [63779.247049] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:47:08 192.168.122.209 [63779.307644] [tempesta fw] Tempesta FW is ready Apr 26 09:47:08 192.168.122.209 [63779.564211] [tempesta fw] Warning: frang: HTTP header length exceeded for 127.0.0.2: 358 (lim=300) Apr 26 09:47:09 192.168.122.209 [63780.072812] [tdb] Close table 'client0.tdb' Apr 26 09:47:09 192.168.122.209 [63780.248326] [tdb] Close table 'sessions0.tdb' Apr 26 09:47:09 192.168.122.209 [63780.466495] [tdb] Close table 'filter0.tdb' Apr 26 09:47:09 192.168.122.209 [63780.466940] [tempesta fw] modules are stopped Apr 26 09:47:10 192.168.122.209 [63780.647830] [tempesta fw] exiting... Apr 26 09:47:10 192.168.122.209 [63780.771096] [tdb] Shutdown Tempesta DB Apr 26 09:47:10 192.168.122.209 [63780.985682] End test: t_frang.test_length.FrangLengthH2.test_http_hdr_len_no_huffman Apr 26 09:47:10 192.168.122.209 [63780.999951] Start test: t_frang.test_length.FrangLengthH2.test_http_hdr_len_without_reaching_the_limit_2_huffman Apr 26 09:47:11 192.168.122.209 [63782.080020] [tdb] Start Tempesta DB Apr 26 09:47:11 192.168.122.209 [63782.225080] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:47:12 192.168.122.209 [63783.073019] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63783.073019] Maybe that's fine, but it's worth checking the [63783.073019] config - if there is no relations between the [63783.073019] names, then host name confusion attack is possible. Apr 26 09:47:12 192.168.122.209 [63783.175763] [tempesta fw] Configuration processing is completed. Apr 26 09:47:12 192.168.122.209 [63783.232530] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:47:12 192.168.122.209 [63783.259105] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:47:12 192.168.122.209 [63783.285513] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:47:12 192.168.122.209 [63783.335744] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:47:12 192.168.122.209 [63783.337418] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:47:12 192.168.122.209 [63783.339059] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:47:12 192.168.122.209 [63783.379699] [tempesta fw] Tempesta FW is ready Apr 26 09:47:13 192.168.122.209 [63784.098638] [tdb] Close table 'client0.tdb' Apr 26 09:47:13 192.168.122.209 [63784.301236] [tdb] Close table 'sessions0.tdb' Apr 26 09:47:13 192.168.122.209 [63784.525406] [tdb] Close table 'filter0.tdb' Apr 26 09:47:13 192.168.122.209 [63784.525842] [tempesta fw] modules are stopped Apr 26 09:47:14 192.168.122.209 [63784.692894] [tempesta fw] exiting... Apr 26 09:47:14 192.168.122.209 [63784.834801] [tdb] Shutdown Tempesta DB Apr 26 09:47:14 192.168.122.209 [63785.053894] End test: t_frang.test_length.FrangLengthH2.test_http_hdr_len_without_reaching_the_limit_2_huffman Apr 26 09:47:14 192.168.122.209 [63785.077084] Start test: t_frang.test_length.FrangLengthH2.test_http_hdr_len_without_reaching_the_limit_2_no_huffman Apr 26 09:47:15 192.168.122.209 [63786.119297] [tdb] Start Tempesta DB Apr 26 09:47:15 192.168.122.209 [63786.259643] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:47:16 192.168.122.209 [63787.105123] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63787.105123] Maybe that's fine, but it's worth checking the [63787.105123] config - if there is no relations between the [63787.105123] names, then host name confusion attack is possible. Apr 26 09:47:16 192.168.122.209 [63787.207819] [tempesta fw] Configuration processing is completed. Apr 26 09:47:16 192.168.122.209 [63787.264937] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:47:16 192.168.122.209 [63787.296380] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:47:16 192.168.122.209 [63787.325618] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:47:16 192.168.122.209 [63787.379794] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:47:16 192.168.122.209 [63787.381468] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:47:16 192.168.122.209 [63787.383144] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:47:16 192.168.122.209 [63787.423726] [tempesta fw] Tempesta FW is ready Apr 26 09:47:17 192.168.122.209 [63788.127889] [tdb] Close table 'client0.tdb' Apr 26 09:47:17 192.168.122.209 [63788.313347] [tdb] Close table 'sessions0.tdb' Apr 26 09:47:17 192.168.122.209 [63788.553833] [tdb] Close table 'filter0.tdb' Apr 26 09:47:17 192.168.122.209 [63788.554251] [tempesta fw] modules are stopped Apr 26 09:47:18 192.168.122.209 [63788.727543] [tempesta fw] exiting... Apr 26 09:47:18 192.168.122.209 [63788.832864] [tdb] Shutdown Tempesta DB Apr 26 09:47:18 192.168.122.209 [63789.033881] End test: t_frang.test_length.FrangLengthH2.test_http_hdr_len_without_reaching_the_limit_2_no_huffman Apr 26 09:47:18 192.168.122.209 [63789.055336] Start test: t_frang.test_length.FrangLengthH2.test_http_hdr_len_without_reaching_the_limit_huffman Apr 26 09:47:19 192.168.122.209 [63790.099471] [tdb] Start Tempesta DB Apr 26 09:47:19 192.168.122.209 [63790.242997] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:47:20 192.168.122.209 [63791.057062] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63791.057062] Maybe that's fine, but it's worth checking the [63791.057062] config - if there is no relations between the [63791.057062] names, then host name confusion attack is possible. Apr 26 09:47:20 192.168.122.209 [63791.187848] [tempesta fw] Configuration processing is completed. Apr 26 09:47:20 192.168.122.209 [63791.238958] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:47:20 192.168.122.209 [63791.265326] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:47:20 192.168.122.209 [63791.291602] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:47:20 192.168.122.209 [63791.335812] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:47:20 192.168.122.209 [63791.337495] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:47:20 192.168.122.209 [63791.339210] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:47:20 192.168.122.209 [63791.375766] [tempesta fw] Tempesta FW is ready Apr 26 09:47:21 192.168.122.209 [63792.087258] [tdb] Close table 'client0.tdb' Apr 26 09:47:21 192.168.122.209 [63792.273798] [tdb] Close table 'sessions0.tdb' Apr 26 09:47:21 192.168.122.209 [63792.502490] [tdb] Close table 'filter0.tdb' Apr 26 09:47:21 192.168.122.209 [63792.503046] [tempesta fw] modules are stopped Apr 26 09:47:22 192.168.122.209 [63792.695958] [tempesta fw] exiting... Apr 26 09:47:22 192.168.122.209 [63792.799603] [tdb] Shutdown Tempesta DB Apr 26 09:47:22 192.168.122.209 [63792.996229] End test: t_frang.test_length.FrangLengthH2.test_http_hdr_len_without_reaching_the_limit_huffman Apr 26 09:47:22 192.168.122.209 [63793.026014] Start test: t_frang.test_length.FrangLengthH2.test_http_hdr_len_without_reaching_the_limit_no_huffman Apr 26 09:47:23 192.168.122.209 [63794.090177] [tdb] Start Tempesta DB Apr 26 09:47:23 192.168.122.209 [63794.235253] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:47:24 192.168.122.209 [63795.041156] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63795.041156] Maybe that's fine, but it's worth checking the [63795.041156] config - if there is no relations between the [63795.041156] names, then host name confusion attack is possible. Apr 26 09:47:24 192.168.122.209 [63795.139919] [tempesta fw] Configuration processing is completed. Apr 26 09:47:24 192.168.122.209 [63795.197312] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:47:24 192.168.122.209 [63795.228115] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:47:24 192.168.122.209 [63795.258290] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:47:24 192.168.122.209 [63795.307862] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:47:24 192.168.122.209 [63795.309566] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:47:24 192.168.122.209 [63795.311276] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:47:24 192.168.122.209 [63795.351807] [tempesta fw] Tempesta FW is ready Apr 26 09:47:25 192.168.122.209 [63796.055313] [tdb] Close table 'client0.tdb' Apr 26 09:47:25 192.168.122.209 [63796.248329] [tdb] Close table 'sessions0.tdb' Apr 26 09:47:25 192.168.122.209 [63796.488921] [tdb] Close table 'filter0.tdb' Apr 26 09:47:25 192.168.122.209 [63796.489335] [tempesta fw] modules are stopped Apr 26 09:47:26 192.168.122.209 [63796.686700] [tempesta fw] exiting... Apr 26 09:47:26 192.168.122.209 [63796.795612] [tdb] Shutdown Tempesta DB Apr 26 09:47:26 192.168.122.209 [63797.004781] End test: t_frang.test_length.FrangLengthH2.test_http_hdr_len_without_reaching_the_limit_no_huffman Apr 26 09:47:26 192.168.122.209 [63797.028245] Start test: t_frang.test_length.FrangLengthH2.test_uri_len Apr 26 09:47:27 192.168.122.209 [63798.129516] [tdb] Start Tempesta DB Apr 26 09:47:27 192.168.122.209 [63798.262534] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:47:28 192.168.122.209 [63799.109174] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63799.109174] Maybe that's fine, but it's worth checking the [63799.109174] config - if there is no relations between the [63799.109174] names, then host name confusion attack is possible. Apr 26 09:47:28 192.168.122.209 [63799.219945] [tempesta fw] Configuration processing is completed. Apr 26 09:47:28 192.168.122.209 [63799.276365] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:47:28 192.168.122.209 [63799.307316] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:47:28 192.168.122.209 [63799.339107] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:47:28 192.168.122.209 [63799.395919] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:47:28 192.168.122.209 [63799.397622] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:47:28 192.168.122.209 [63799.399278] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:47:28 192.168.122.209 [63799.443875] [tempesta fw] Tempesta FW is ready Apr 26 09:47:28 192.168.122.209 [63799.603354] [tempesta fw] Warning: frang: HTTP URI length exceeded for 127.0.0.2: 10 (lim=5) Apr 26 09:47:28 192.168.122.209 [63799.604156] [tempesta fw] Warning: parsed request has been filtered out: 127.0.0.2 Apr 26 09:47:29 192.168.122.209 [63800.082232] [tdb] Close table 'client0.tdb' Apr 26 09:47:29 192.168.122.209 [63800.281928] [tdb] Close table 'sessions0.tdb' Apr 26 09:47:29 192.168.122.209 [63800.526938] [tdb] Close table 'filter0.tdb' Apr 26 09:47:29 192.168.122.209 [63800.527365] [tempesta fw] modules are stopped Apr 26 09:47:30 192.168.122.209 [63800.728936] [tempesta fw] exiting... Apr 26 09:47:30 192.168.122.209 [63800.879999] [tdb] Shutdown Tempesta DB Apr 26 09:47:30 192.168.122.209 [63801.117529] End test: t_frang.test_length.FrangLengthH2.test_uri_len Apr 26 09:47:30 192.168.122.209 [63801.130327] Start test: t_frang.test_length.FrangLengthH2.test_uri_len_on_the_limit Apr 26 09:47:31 192.168.122.209 [63802.191681] [tdb] Start Tempesta DB Apr 26 09:47:31 192.168.122.209 [63802.335023] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:47:32 192.168.122.209 [63803.233209] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63803.233209] Maybe that's fine, but it's worth checking the [63803.233209] config - if there is no relations between the [63803.233209] names, then host name confusion attack is possible. Apr 26 09:47:32 192.168.122.209 [63803.339991] [tempesta fw] Configuration processing is completed. Apr 26 09:47:32 192.168.122.209 [63803.398673] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:47:32 192.168.122.209 [63803.425126] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:47:32 192.168.122.209 [63803.452085] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:47:32 192.168.122.209 [63803.491943] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:47:32 192.168.122.209 [63803.493614] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:47:32 192.168.122.209 [63803.495249] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:47:32 192.168.122.209 [63803.539888] [tempesta fw] Tempesta FW is ready Apr 26 09:47:33 192.168.122.209 [63804.264978] [tdb] Close table 'client0.tdb' Apr 26 09:47:33 192.168.122.209 [63804.450453] [tdb] Close table 'sessions0.tdb' Apr 26 09:47:34 192.168.122.209 [63804.686571] [tdb] Close table 'filter0.tdb' Apr 26 09:47:34 192.168.122.209 [63804.686999] [tempesta fw] modules are stopped Apr 26 09:47:34 192.168.122.209 [63804.886492] [tempesta fw] exiting... Apr 26 09:47:34 192.168.122.209 [63804.989378] [tdb] Shutdown Tempesta DB Apr 26 09:47:34 192.168.122.209 [63805.192569] End test: t_frang.test_length.FrangLengthH2.test_uri_len_on_the_limit Apr 26 09:47:34 192.168.122.209 [63805.207978] Start test: t_frang.test_length.FrangLengthH2.test_uri_len_without_reaching_the_limit Apr 26 09:47:35 192.168.122.209 [63806.283520] [tdb] Start Tempesta DB Apr 26 09:47:35 192.168.122.209 [63806.426406] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:47:36 192.168.122.209 [63807.269330] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63807.269330] Maybe that's fine, but it's worth checking the [63807.269330] config - if there is no relations between the [63807.269330] names, then host name confusion attack is possible. Apr 26 09:47:36 192.168.122.209 [63807.388112] [tempesta fw] Configuration processing is completed. Apr 26 09:47:36 192.168.122.209 [63807.444437] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:47:36 192.168.122.209 [63807.475056] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:47:36 192.168.122.209 [63807.503741] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:47:36 192.168.122.209 [63807.548003] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:47:36 192.168.122.209 [63807.549684] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:47:36 192.168.122.209 [63807.551336] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:47:36 192.168.122.209 [63807.587956] [tempesta fw] Tempesta FW is ready Apr 26 09:47:37 192.168.122.209 [63808.269270] [tdb] Close table 'client0.tdb' Apr 26 09:47:37 192.168.122.209 [63808.465167] [tdb] Close table 'sessions0.tdb' Apr 26 09:47:38 192.168.122.209 [63808.684495] [tdb] Close table 'filter0.tdb' Apr 26 09:47:38 192.168.122.209 [63808.684920] [tempesta fw] modules are stopped Apr 26 09:47:38 192.168.122.209 [63808.961240] [tempesta fw] exiting... Apr 26 09:47:38 192.168.122.209 [63809.061142] [tdb] Shutdown Tempesta DB Apr 26 09:47:38 192.168.122.209 [63809.260620] End test: t_frang.test_length.FrangLengthH2.test_uri_len_without_reaching_the_limit Apr 26 09:47:38 192.168.122.209 [63809.270195] Start test: t_frang.test_length.FrangLengthTestCase.test_body_len Apr 26 09:47:39 192.168.122.209 [63810.332124] [tdb] Start Tempesta DB Apr 26 09:47:39 192.168.122.209 [63810.472630] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:47:40 192.168.122.209 [63811.301326] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63811.301326] Maybe that's fine, but it's worth checking the [63811.301326] config - if there is no relations between the [63811.301326] names, then host name confusion attack is possible. Apr 26 09:47:40 192.168.122.209 [63811.412051] [tempesta fw] Configuration processing is completed. Apr 26 09:47:40 192.168.122.209 [63811.463655] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:47:40 192.168.122.209 [63811.489805] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:47:40 192.168.122.209 [63811.516655] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:47:40 192.168.122.209 [63811.559984] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:47:40 192.168.122.209 [63811.561679] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:47:40 192.168.122.209 [63811.563448] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:47:41 192.168.122.209 [63811.607990] [tempesta fw] Tempesta FW is ready Apr 26 09:47:41 192.168.122.209 [63811.760379] [tempesta fw] Warning: frang: HTTP body length exceeded for 127.0.0.2: 11 (lim=10) Apr 26 09:47:41 192.168.122.209 [63811.761621] [tempesta fw] Warning: postponed request has been filtered out: 127.0.0.2 Apr 26 09:47:41 192.168.122.209 [63812.246191] [tdb] Close table 'client0.tdb' Apr 26 09:47:41 192.168.122.209 [63812.438237] [tdb] Close table 'sessions0.tdb' Apr 26 09:47:42 192.168.122.209 [63812.680678] [tdb] Close table 'filter0.tdb' Apr 26 09:47:42 192.168.122.209 [63812.681108] [tempesta fw] modules are stopped Apr 26 09:47:42 192.168.122.209 [63812.895803] [tempesta fw] exiting... Apr 26 09:47:42 192.168.122.209 [63813.036574] [tdb] Shutdown Tempesta DB Apr 26 09:47:42 192.168.122.209 [63813.230171] End test: t_frang.test_length.FrangLengthTestCase.test_body_len Apr 26 09:47:42 192.168.122.209 [63813.241358] Start test: t_frang.test_length.FrangLengthTestCase.test_body_len_without_reaching_the_limit Apr 26 09:47:43 192.168.122.209 [63814.309859] [tdb] Start Tempesta DB Apr 26 09:47:43 192.168.122.209 [63814.456431] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:47:44 192.168.122.209 [63815.277405] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63815.277405] Maybe that's fine, but it's worth checking the [63815.277405] config - if there is no relations between the [63815.277405] names, then host name confusion attack is possible. Apr 26 09:47:44 192.168.122.209 [63815.372124] [tempesta fw] Configuration processing is completed. Apr 26 09:47:44 192.168.122.209 [63815.422166] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:47:44 192.168.122.209 [63815.449279] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:47:44 192.168.122.209 [63815.477169] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:47:44 192.168.122.209 [63815.524087] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:47:44 192.168.122.209 [63815.525762] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:47:44 192.168.122.209 [63815.527418] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:47:44 192.168.122.209 [63815.572016] [tempesta fw] Tempesta FW is ready Apr 26 09:47:45 192.168.122.209 [63816.180284] [tdb] Close table 'client0.tdb' Apr 26 09:47:45 192.168.122.209 [63816.364675] [tdb] Close table 'sessions0.tdb' Apr 26 09:47:45 192.168.122.209 [63816.586912] [tdb] Close table 'filter0.tdb' Apr 26 09:47:45 192.168.122.209 [63816.587341] [tempesta fw] modules are stopped Apr 26 09:47:46 192.168.122.209 [63816.788830] [tempesta fw] exiting... Apr 26 09:47:46 192.168.122.209 [63816.920224] [tdb] Shutdown Tempesta DB Apr 26 09:47:46 192.168.122.209 [63817.106837] End test: t_frang.test_length.FrangLengthTestCase.test_body_len_without_reaching_the_limit Apr 26 09:47:46 192.168.122.209 [63817.123728] Start test: t_frang.test_length.FrangLengthTestCase.test_body_len_without_reaching_the_limit_zero_len Apr 26 09:47:47 192.168.122.209 [63818.167977] [tdb] Start Tempesta DB Apr 26 09:47:47 192.168.122.209 [63818.303553] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:47:48 192.168.122.209 [63819.097368] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63819.097368] Maybe that's fine, but it's worth checking the [63819.097368] config - if there is no relations between the [63819.097368] names, then host name confusion attack is possible. Apr 26 09:47:48 192.168.122.209 [63819.204135] [tempesta fw] Configuration processing is completed. Apr 26 09:47:48 192.168.122.209 [63819.258986] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:47:48 192.168.122.209 [63819.287778] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:47:48 192.168.122.209 [63819.317112] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:47:48 192.168.122.209 [63819.368138] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:47:48 192.168.122.209 [63819.369875] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:47:48 192.168.122.209 [63819.371537] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:47:48 192.168.122.209 [63819.408091] [tempesta fw] Tempesta FW is ready Apr 26 09:47:49 192.168.122.209 [63820.043359] [tdb] Close table 'client0.tdb' Apr 26 09:47:49 192.168.122.209 [63820.236851] [tdb] Close table 'sessions0.tdb' Apr 26 09:47:49 192.168.122.209 [63820.471151] [tdb] Close table 'filter0.tdb' Apr 26 09:47:49 192.168.122.209 [63820.471566] [tempesta fw] modules are stopped Apr 26 09:47:50 192.168.122.209 [63820.705373] [tempesta fw] exiting... Apr 26 09:47:50 192.168.122.209 [63820.825940] [tdb] Shutdown Tempesta DB Apr 26 09:47:50 192.168.122.209 [63821.010131] End test: t_frang.test_length.FrangLengthTestCase.test_body_len_without_reaching_the_limit_zero_len Apr 26 09:47:50 192.168.122.209 [63821.022127] Start test: t_frang.test_length.FrangLengthTestCase.test_http_hdr_len Apr 26 09:47:51 192.168.122.209 [63822.022446] [tdb] Start Tempesta DB Apr 26 09:47:51 192.168.122.209 [63822.166354] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:47:52 192.168.122.209 [63822.973430] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63822.973430] Maybe that's fine, but it's worth checking the [63822.973430] config - if there is no relations between the [63822.973430] names, then host name confusion attack is possible. Apr 26 09:47:52 192.168.122.209 [63823.088187] [tempesta fw] Configuration processing is completed. Apr 26 09:47:52 192.168.122.209 [63823.145054] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:47:52 192.168.122.209 [63823.175934] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:47:52 192.168.122.209 [63823.204323] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:47:52 192.168.122.209 [63823.260158] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:47:52 192.168.122.209 [63823.261862] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:47:52 192.168.122.209 [63823.263527] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:47:52 192.168.122.209 [63823.312095] [tempesta fw] Tempesta FW is ready Apr 26 09:47:52 192.168.122.209 [63823.492173] [tempesta fw] Warning: frang: HTTP header length exceeded for 127.0.0.2: 328 (lim=300) Apr 26 09:47:53 192.168.122.209 [63823.988589] [tdb] Close table 'client0.tdb' Apr 26 09:47:53 192.168.122.209 [63824.169109] [tdb] Close table 'sessions0.tdb' Apr 26 09:47:53 192.168.122.209 [63824.394970] [tdb] Close table 'filter0.tdb' Apr 26 09:47:53 192.168.122.209 [63824.395393] [tempesta fw] modules are stopped Apr 26 09:47:53 192.168.122.209 [63824.592284] [tempesta fw] exiting... Apr 26 09:47:54 192.168.122.209 [63824.751400] [tdb] Shutdown Tempesta DB Apr 26 09:47:54 192.168.122.209 [63824.959277] End test: t_frang.test_length.FrangLengthTestCase.test_http_hdr_len Apr 26 09:47:54 192.168.122.209 [63824.971334] Start test: t_frang.test_length.FrangLengthTestCase.test_http_hdr_len_without_reaching_the_limit Apr 26 09:47:55 192.168.122.209 [63826.009263] [tdb] Start Tempesta DB Apr 26 09:47:55 192.168.122.209 [63826.139940] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:47:56 192.168.122.209 [63826.989439] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63826.989439] Maybe that's fine, but it's worth checking the [63826.989439] config - if there is no relations between the [63826.989439] names, then host name confusion attack is possible. Apr 26 09:47:56 192.168.122.209 [63827.088210] [tempesta fw] Configuration processing is completed. Apr 26 09:47:56 192.168.122.209 [63827.139225] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:47:56 192.168.122.209 [63827.166634] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:47:56 192.168.122.209 [63827.193614] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:47:56 192.168.122.209 [63827.236179] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:47:56 192.168.122.209 [63827.237515] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:47:56 192.168.122.209 [63827.238861] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:47:56 192.168.122.209 [63827.284157] [tempesta fw] Tempesta FW is ready Apr 26 09:47:57 192.168.122.209 [63827.923891] [tdb] Close table 'client0.tdb' Apr 26 09:47:57 192.168.122.209 [63828.110011] [tdb] Close table 'sessions0.tdb' Apr 26 09:47:57 192.168.122.209 [63828.324875] [tdb] Close table 'filter0.tdb' Apr 26 09:47:57 192.168.122.209 [63828.325302] [tempesta fw] modules are stopped Apr 26 09:47:57 192.168.122.209 [63828.533557] [tempesta fw] exiting... Apr 26 09:47:58 192.168.122.209 [63828.671877] [tdb] Shutdown Tempesta DB Apr 26 09:47:58 192.168.122.209 [63828.862164] End test: t_frang.test_length.FrangLengthTestCase.test_http_hdr_len_without_reaching_the_limit Apr 26 09:47:58 192.168.122.209 [63828.877323] Start test: t_frang.test_length.FrangLengthTestCase.test_http_hdr_len_without_reaching_the_limit_2 Apr 26 09:47:59 192.168.122.209 [63829.969258] [tdb] Start Tempesta DB Apr 26 09:47:59 192.168.122.209 [63830.103240] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:48:00 192.168.122.209 [63830.869527] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63830.869527] Maybe that's fine, but it's worth checking the [63830.869527] config - if there is no relations between the [63830.869527] names, then host name confusion attack is possible. Apr 26 09:48:00 192.168.122.209 [63830.972282] [tempesta fw] Configuration processing is completed. Apr 26 09:48:00 192.168.122.209 [63831.028582] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:48:00 192.168.122.209 [63831.059163] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:48:00 192.168.122.209 [63831.087192] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:48:00 192.168.122.209 [63831.144273] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:48:00 192.168.122.209 [63831.145946] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:48:00 192.168.122.209 [63831.147597] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:48:00 192.168.122.209 [63831.204201] [tempesta fw] Tempesta FW is ready Apr 26 09:48:01 192.168.122.209 [63831.894275] [tdb] Close table 'client0.tdb' Apr 26 09:48:01 192.168.122.209 [63832.076840] [tdb] Close table 'sessions0.tdb' Apr 26 09:48:01 192.168.122.209 [63832.301407] [tdb] Close table 'filter0.tdb' Apr 26 09:48:01 192.168.122.209 [63832.301827] [tempesta fw] modules are stopped Apr 26 09:48:01 192.168.122.209 [63832.505193] [tempesta fw] exiting... Apr 26 09:48:02 192.168.122.209 [63832.631021] [tdb] Shutdown Tempesta DB Apr 26 09:48:02 192.168.122.209 [63832.845800] End test: t_frang.test_length.FrangLengthTestCase.test_http_hdr_len_without_reaching_the_limit_2 Apr 26 09:48:02 192.168.122.209 [63832.860917] Start test: t_frang.test_length.FrangLengthTestCase.test_uri_len Apr 26 09:48:03 192.168.122.209 [63833.935324] [tdb] Start Tempesta DB Apr 26 09:48:03 192.168.122.209 [63834.069735] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:48:04 192.168.122.209 [63834.869566] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63834.869566] Maybe that's fine, but it's worth checking the [63834.869566] config - if there is no relations between the [63834.869566] names, then host name confusion attack is possible. Apr 26 09:48:04 192.168.122.209 [63834.972328] [tempesta fw] Configuration processing is completed. Apr 26 09:48:04 192.168.122.209 [63835.030805] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:48:04 192.168.122.209 [63835.061104] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:48:04 192.168.122.209 [63835.091103] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:48:04 192.168.122.209 [63835.136294] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:48:04 192.168.122.209 [63835.137972] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:48:04 192.168.122.209 [63835.139644] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:48:04 192.168.122.209 [63835.176228] [tempesta fw] Tempesta FW is ready Apr 26 09:48:04 192.168.122.209 [63835.302246] [tempesta fw] Warning: frang: HTTP URI length exceeded for 127.0.0.2: 6 (lim=5) Apr 26 09:48:04 192.168.122.209 [63835.304569] [tempesta fw] Warning: postponed request has been filtered out: 127.0.0.2 Apr 26 09:48:05 192.168.122.209 [63835.810190] [tdb] Close table 'client0.tdb' Apr 26 09:48:05 192.168.122.209 [63835.999926] [tdb] Close table 'sessions0.tdb' Apr 26 09:48:05 192.168.122.209 [63836.245492] [tdb] Close table 'filter0.tdb' Apr 26 09:48:05 192.168.122.209 [63836.246036] [tempesta fw] modules are stopped Apr 26 09:48:05 192.168.122.209 [63836.473149] [tempesta fw] exiting... Apr 26 09:48:06 192.168.122.209 [63836.614371] [tdb] Shutdown Tempesta DB Apr 26 09:48:06 192.168.122.209 [63836.811199] End test: t_frang.test_length.FrangLengthTestCase.test_uri_len Apr 26 09:48:06 192.168.122.209 [63836.822208] Start test: t_frang.test_length.FrangLengthTestCase.test_uri_len_on_the_limit Apr 26 09:48:07 192.168.122.209 [63837.908759] [tdb] Start Tempesta DB Apr 26 09:48:07 192.168.122.209 [63838.056779] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:48:08 192.168.122.209 [63838.849575] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63838.849575] Maybe that's fine, but it's worth checking the [63838.849575] config - if there is no relations between the [63838.849575] names, then host name confusion attack is possible. Apr 26 09:48:08 192.168.122.209 [63838.964343] [tempesta fw] Configuration processing is completed. Apr 26 09:48:08 192.168.122.209 [63839.014624] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:48:08 192.168.122.209 [63839.041186] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:48:08 192.168.122.209 [63839.069597] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:48:08 192.168.122.209 [63839.128322] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:48:08 192.168.122.209 [63839.129992] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:48:08 192.168.122.209 [63839.131641] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:48:08 192.168.122.209 [63839.176262] [tempesta fw] Tempesta FW is ready Apr 26 09:48:09 192.168.122.209 [63839.775864] [tdb] Close table 'client0.tdb' Apr 26 09:48:09 192.168.122.209 [63839.974499] [tdb] Close table 'sessions0.tdb' Apr 26 09:48:09 192.168.122.209 [63840.214065] [tdb] Close table 'filter0.tdb' Apr 26 09:48:09 192.168.122.209 [63840.214520] [tempesta fw] modules are stopped Apr 26 09:48:09 192.168.122.209 [63840.435912] [tempesta fw] exiting... Apr 26 09:48:09 192.168.122.209 [63840.570221] [tdb] Shutdown Tempesta DB Apr 26 09:48:10 192.168.122.209 [63840.769671] End test: t_frang.test_length.FrangLengthTestCase.test_uri_len_on_the_limit Apr 26 09:48:10 192.168.122.209 [63840.775924] Start test: t_frang.test_length.FrangLengthTestCase.test_uri_len_without_reaching_the_limit Apr 26 09:48:11 192.168.122.209 [63841.893739] [tdb] Start Tempesta DB Apr 26 09:48:11 192.168.122.209 [63842.018148] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:48:12 192.168.122.209 [63842.821533] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63842.821533] Maybe that's fine, but it's worth checking the [63842.821533] config - if there is no relations between the [63842.821533] names, then host name confusion attack is possible. Apr 26 09:48:12 192.168.122.209 [63842.924496] [tempesta fw] Configuration processing is completed. Apr 26 09:48:12 192.168.122.209 [63842.981836] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:48:12 192.168.122.209 [63843.012852] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:48:12 192.168.122.209 [63843.041611] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:48:12 192.168.122.209 [63843.084359] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:48:12 192.168.122.209 [63843.086028] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 09:48:12 192.168.122.209 [63843.087689] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:48:12 192.168.122.209 [63843.128329] [tempesta fw] Tempesta FW is ready Apr 26 09:48:13 192.168.122.209 [63843.754566] [tdb] Close table 'client0.tdb' Apr 26 09:48:13 192.168.122.209 [63843.947276] [tdb] Close table 'sessions0.tdb' Apr 26 09:48:13 192.168.122.209 [63844.169735] [tdb] Close table 'filter0.tdb' Apr 26 09:48:13 192.168.122.209 [63844.170153] [tempesta fw] modules are stopped Apr 26 09:48:13 192.168.122.209 [63844.364796] [tempesta fw] exiting... Apr 26 09:48:13 192.168.122.209 [63844.475656] [tdb] Shutdown Tempesta DB Apr 26 09:48:14 192.168.122.209 [63844.663119] End test: t_frang.test_length.FrangLengthTestCase.test_uri_len_without_reaching_the_limit Apr 26 09:48:14 192.168.122.209 [63844.679171] Start test: t_frang.test_tls_incomplete.FrangTlsIncompleteTestCase.test_tls_incomplete_connection_rate Apr 26 09:48:15 192.168.122.209 [63845.755106] [tdb] Start Tempesta DB Apr 26 09:48:15 192.168.122.209 [63845.882029] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:48:16 192.168.122.209 [63846.649718] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63846.649718] Maybe that's fine, but it's worth checking the [63846.649718] config - if there is no relations between the [63846.649718] names, then host name confusion attack is possible. Apr 26 09:48:16 192.168.122.209 [63846.768469] [tempesta fw] Configuration processing is completed. Apr 26 09:48:16 192.168.122.209 [63846.825775] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:48:16 192.168.122.209 [63846.857805] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:48:16 192.168.122.209 [63846.887186] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:48:16 192.168.122.209 [63846.932426] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:48:16 192.168.122.209 [63846.980364] [tempesta fw] Tempesta FW is ready Apr 26 09:48:16 192.168.122.209 [63847.316310] [tempesta fw] Warning: frang: incomplete TLS connections rate exceeded for 127.0.0.2: 5 (lim=4) Apr 26 09:48:17 192.168.122.209 [63848.286170] [tdb] Close table 'client0.tdb' Apr 26 09:48:17 192.168.122.209 [63848.456177] [tdb] Close table 'sessions0.tdb' Apr 26 09:48:18 192.168.122.209 [63848.721020] [tdb] Close table 'filter0.tdb' Apr 26 09:48:18 192.168.122.209 [63848.721450] [tempesta fw] modules are stopped Apr 26 09:48:18 192.168.122.209 [63848.888186] [tempesta fw] exiting... Apr 26 09:48:18 192.168.122.209 [63848.993568] [tdb] Shutdown Tempesta DB Apr 26 09:48:18 192.168.122.209 [63849.187067] End test: t_frang.test_tls_incomplete.FrangTlsIncompleteTestCase.test_tls_incomplete_connection_rate Apr 26 09:48:18 192.168.122.209 [63849.202444] Start test: t_frang.test_tls_incomplete.FrangTlsIncompleteTestCase.test_tls_incomplete_connection_rate_on_the_limit Apr 26 09:48:19 192.168.122.209 [63850.287047] [tdb] Start Tempesta DB Apr 26 09:48:19 192.168.122.209 [63850.424092] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:48:20 192.168.122.209 [63851.229703] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63851.229703] Maybe that's fine, but it's worth checking the [63851.229703] config - if there is no relations between the [63851.229703] names, then host name confusion attack is possible. Apr 26 09:48:20 192.168.122.209 [63851.348483] [tempesta fw] Configuration processing is completed. Apr 26 09:48:20 192.168.122.209 [63851.399399] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:48:20 192.168.122.209 [63851.426398] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:48:20 192.168.122.209 [63851.454704] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:48:20 192.168.122.209 [63851.520485] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:48:20 192.168.122.209 [63851.560409] [tempesta fw] Tempesta FW is ready Apr 26 09:48:22 192.168.122.209 [63852.913166] [tdb] Close table 'client0.tdb' Apr 26 09:48:22 192.168.122.209 [63853.098142] [tdb] Close table 'sessions0.tdb' Apr 26 09:48:22 192.168.122.209 [63853.327141] [tdb] Close table 'filter0.tdb' Apr 26 09:48:22 192.168.122.209 [63853.327570] [tempesta fw] modules are stopped Apr 26 09:48:22 192.168.122.209 [63853.505782] [tempesta fw] exiting... Apr 26 09:48:23 192.168.122.209 [63853.621066] [tdb] Shutdown Tempesta DB Apr 26 09:48:23 192.168.122.209 [63853.836872] End test: t_frang.test_tls_incomplete.FrangTlsIncompleteTestCase.test_tls_incomplete_connection_rate_on_the_limit Apr 26 09:48:23 192.168.122.209 [63853.846407] Start test: t_frang.test_tls_incomplete.FrangTlsIncompleteTestCase.test_tls_incomplete_connection_without_reaching_the_limit Apr 26 09:48:24 192.168.122.209 [63854.892907] [tdb] Start Tempesta DB Apr 26 09:48:24 192.168.122.209 [63855.028264] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:48:25 192.168.122.209 [63855.805771] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63855.805771] Maybe that's fine, but it's worth checking the [63855.805771] config - if there is no relations between the [63855.805771] names, then host name confusion attack is possible. Apr 26 09:48:25 192.168.122.209 [63855.908551] [tempesta fw] Configuration processing is completed. Apr 26 09:48:25 192.168.122.209 [63855.966643] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:48:25 192.168.122.209 [63855.997217] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:48:25 192.168.122.209 [63856.027662] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:48:25 192.168.122.209 [63856.072516] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:48:25 192.168.122.209 [63856.112482] [tempesta fw] Tempesta FW is ready Apr 26 09:48:26 192.168.122.209 [63857.415667] [tdb] Close table 'client0.tdb' Apr 26 09:48:26 192.168.122.209 [63857.607737] [tdb] Close table 'sessions0.tdb' Apr 26 09:48:27 192.168.122.209 [63857.873764] [tdb] Close table 'filter0.tdb' Apr 26 09:48:27 192.168.122.209 [63857.874192] [tempesta fw] modules are stopped Apr 26 09:48:27 192.168.122.209 [63858.061176] [tempesta fw] exiting... Apr 26 09:48:27 192.168.122.209 [63858.170540] [tdb] Shutdown Tempesta DB Apr 26 09:48:27 192.168.122.209 [63858.355664] End test: t_frang.test_tls_incomplete.FrangTlsIncompleteTestCase.test_tls_incomplete_connection_without_reaching_the_limit Apr 26 09:48:27 192.168.122.209 [63858.372616] Start test: t_frang.test_whitelist_mark.FrangWhitelistMarkTestCase.test_non_whitelisted_request_are_js_challenged Apr 26 09:48:28 192.168.122.209 [63859.455777] [tdb] Start Tempesta DB Apr 26 09:48:28 192.168.122.209 [63859.598484] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:48:30 192.168.122.209 [63860.967382] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:48:30 192.168.122.209 [63861.036651] [tempesta fw] Configuration processing is completed. Apr 26 09:48:30 192.168.122.209 [63861.102746] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:48:30 192.168.122.209 [63861.524083] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:48:30 192.168.122.209 [63861.550129] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:48:30 192.168.122.209 [63861.576839] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:48:31 192.168.122.209 [63861.624587] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:48:31 192.168.122.209 [63861.664546] [tempesta fw] Tempesta FW is ready Apr 26 09:48:31 192.168.122.209 [63862.225844] [tdb] Close table 'client0.tdb' Apr 26 09:48:31 192.168.122.209 [63862.425913] [tdb] Close table 'sessions0.tdb' Apr 26 09:48:35 192.168.122.209 [63865.644642] [tdb] Close table 'cache0.tdb' Apr 26 09:48:35 192.168.122.209 [63865.904298] [tdb] Close table 'filter0.tdb' Apr 26 09:48:35 192.168.122.209 [63865.904765] [tempesta fw] modules are stopped Apr 26 09:48:35 192.168.122.209 [63866.099091] [tempesta fw] exiting... Apr 26 09:48:35 192.168.122.209 [63866.207743] [tdb] Shutdown Tempesta DB Apr 26 09:48:35 192.168.122.209 [63866.382221] End test: t_frang.test_whitelist_mark.FrangWhitelistMarkTestCase.test_non_whitelisted_request_are_js_challenged Apr 26 09:48:35 192.168.122.209 [63866.408807] Start test: t_frang.test_whitelist_mark.FrangWhitelistMarkTestCase.test_whitelisted_basic_request Apr 26 09:48:36 192.168.122.209 [63867.461867] [tdb] Start Tempesta DB Apr 26 09:48:36 192.168.122.209 [63867.602409] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:48:39 192.168.122.209 [63869.751346] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:48:39 192.168.122.209 [63869.824748] [tempesta fw] Configuration processing is completed. Apr 26 09:48:39 192.168.122.209 [63869.883984] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:48:39 192.168.122.209 [63870.292372] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:48:39 192.168.122.209 [63870.318181] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:48:39 192.168.122.209 [63870.343619] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:48:39 192.168.122.209 [63870.408676] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:48:39 192.168.122.209 [63870.448627] [tempesta fw] Tempesta FW is ready Apr 26 09:48:40 192.168.122.209 [63871.014823] [tdb] Close table 'client0.tdb' Apr 26 09:48:40 192.168.122.209 [63871.203887] [tdb] Close table 'sessions0.tdb' Apr 26 09:48:43 192.168.122.209 [63874.429732] [tdb] Close table 'cache0.tdb' Apr 26 09:48:44 192.168.122.209 [63874.686349] [tdb] Close table 'filter0.tdb' Apr 26 09:48:44 192.168.122.209 [63874.686792] [tempesta fw] modules are stopped Apr 26 09:48:44 192.168.122.209 [63874.920631] [tempesta fw] exiting... Apr 26 09:48:44 192.168.122.209 [63875.037880] [tdb] Shutdown Tempesta DB Apr 26 09:48:44 192.168.122.209 [63875.253673] End test: t_frang.test_whitelist_mark.FrangWhitelistMarkTestCase.test_whitelisted_basic_request Apr 26 09:48:44 192.168.122.209 [63875.263996] Start test: t_frang.test_whitelist_mark.FrangWhitelistMarkTestCase.test_whitelisted_basic_request_xforwarded_for Apr 26 09:48:45 192.168.122.209 [63876.365670] [tdb] Start Tempesta DB Apr 26 09:48:45 192.168.122.209 [63876.506468] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:48:47 192.168.122.209 [63878.599458] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:48:48 192.168.122.209 [63878.672820] [tempesta fw] Configuration processing is completed. Apr 26 09:48:48 192.168.122.209 [63878.737656] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:48:48 192.168.122.209 [63879.182579] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:48:48 192.168.122.209 [63879.209133] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:48:48 192.168.122.209 [63879.235107] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:48:48 192.168.122.209 [63879.280763] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:48:48 192.168.122.209 [63879.328639] [tempesta fw] Tempesta FW is ready Apr 26 09:48:49 192.168.122.209 [63879.914929] [tdb] Close table 'client0.tdb' Apr 26 09:48:49 192.168.122.209 [63880.104435] [tdb] Close table 'sessions0.tdb' Apr 26 09:48:52 192.168.122.209 [63883.394345] [tdb] Close table 'cache0.tdb' Apr 26 09:48:53 192.168.122.209 [63883.616649] [tdb] Close table 'filter0.tdb' Apr 26 09:48:53 192.168.122.209 [63883.617083] [tempesta fw] modules are stopped Apr 26 09:48:53 192.168.122.209 [63883.837413] [tempesta fw] exiting... Apr 26 09:48:53 192.168.122.209 [63883.989836] [tdb] Shutdown Tempesta DB Apr 26 09:48:53 192.168.122.209 [63884.189096] End test: t_frang.test_whitelist_mark.FrangWhitelistMarkTestCase.test_whitelisted_basic_request_xforwarded_for Apr 26 09:48:53 192.168.122.209 [63884.211599] Start test: t_frang.test_whitelist_mark.FrangWhitelistMarkTestCase.test_whitelisted_frang_connection_rate Apr 26 09:48:54 192.168.122.209 [63885.257223] [tdb] Start Tempesta DB Apr 26 09:48:54 192.168.122.209 [63885.405889] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:48:56 192.168.122.209 [63887.475560] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:48:56 192.168.122.209 [63887.544919] [tempesta fw] Configuration processing is completed. Apr 26 09:48:56 192.168.122.209 [63887.593781] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:48:57 192.168.122.209 [63888.001679] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:48:57 192.168.122.209 [63888.026906] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:48:57 192.168.122.209 [63888.053897] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:48:57 192.168.122.209 [63888.088866] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:48:57 192.168.122.209 [63888.128807] [tempesta fw] Tempesta FW is ready Apr 26 09:48:58 192.168.122.209 [63888.797296] [tdb] Close table 'client0.tdb' Apr 26 09:48:58 192.168.122.209 [63889.037417] [tdb] Close table 'sessions0.tdb' Apr 26 09:49:01 192.168.122.209 [63892.298480] [tdb] Close table 'cache0.tdb' Apr 26 09:49:01 192.168.122.209 [63892.551380] [tdb] Close table 'filter0.tdb' Apr 26 09:49:01 192.168.122.209 [63892.551845] [tempesta fw] modules are stopped Apr 26 09:49:02 192.168.122.209 [63892.783972] [tempesta fw] exiting... Apr 26 09:49:02 192.168.122.209 [63892.919392] [tdb] Shutdown Tempesta DB Apr 26 09:49:02 192.168.122.209 [63893.125486] End test: t_frang.test_whitelist_mark.FrangWhitelistMarkTestCase.test_whitelisted_frang_connection_rate Apr 26 09:49:02 192.168.122.209 [63893.139900] Start test: t_frang.test_whitelist_mark.FrangWhitelistMarkTestCase.test_whitelisted_frang_http_uri_len Apr 26 09:49:03 192.168.122.209 [63894.148250] [tdb] Start Tempesta DB Apr 26 09:49:03 192.168.122.209 [63894.278322] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:49:05 192.168.122.209 [63896.167710] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:49:05 192.168.122.209 [63896.237309] [tempesta fw] Configuration processing is completed. Apr 26 09:49:05 192.168.122.209 [63896.287269] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:49:06 192.168.122.209 [63896.733530] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:49:06 192.168.122.209 [63896.761914] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:49:06 192.168.122.209 [63896.789883] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:49:06 192.168.122.209 [63896.860963] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:49:06 192.168.122.209 [63896.896965] [tempesta fw] Tempesta FW is ready Apr 26 09:49:06 192.168.122.209 [63897.473351] [tdb] Close table 'client0.tdb' Apr 26 09:49:07 192.168.122.209 [63897.667922] [tdb] Close table 'sessions0.tdb' Apr 26 09:49:10 192.168.122.209 [63900.851258] [tdb] Close table 'cache0.tdb' Apr 26 09:49:10 192.168.122.209 [63901.079261] [tdb] Close table 'filter0.tdb' Apr 26 09:49:10 192.168.122.209 [63901.079680] [tempesta fw] modules are stopped Apr 26 09:49:10 192.168.122.209 [63901.328703] [tempesta fw] exiting... Apr 26 09:49:10 192.168.122.209 [63901.489405] [tdb] Shutdown Tempesta DB Apr 26 09:49:11 192.168.122.209 [63901.695094] End test: t_frang.test_whitelist_mark.FrangWhitelistMarkTestCase.test_whitelisted_frang_http_uri_len Apr 26 09:49:11 192.168.122.209 [63901.722879] Start test: t_frang.test_whitelist_mark.FrangWhitelistMarkTestCase.test_whitelisted_frang_http_uri_len_xforwarded_for Apr 26 09:49:12 192.168.122.209 [63902.826233] [tdb] Start Tempesta DB Apr 26 09:49:12 192.168.122.209 [63902.957479] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:49:14 192.168.122.209 [63905.047711] [tempesta fw] http_sess: JavaScript challenge requires enforced sticky cookie mode Apr 26 09:49:14 192.168.122.209 [63905.117113] [tempesta fw] Configuration processing is completed. Apr 26 09:49:14 192.168.122.209 [63905.166427] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:49:14 192.168.122.209 [63905.579033] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:49:14 192.168.122.209 [63905.604742] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:49:15 192.168.122.209 [63905.631515] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:49:15 192.168.122.209 [63905.717057] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:49:15 192.168.122.209 [63905.760992] [tempesta fw] Tempesta FW is ready Apr 26 09:49:15 192.168.122.209 [63906.360150] [tdb] Close table 'client0.tdb' Apr 26 09:49:15 192.168.122.209 [63906.570160] [tdb] Close table 'sessions0.tdb' Apr 26 09:49:19 192.168.122.209 [63909.820941] [tdb] Close table 'cache0.tdb' Apr 26 09:49:19 192.168.122.209 [63910.076821] [tdb] Close table 'filter0.tdb' Apr 26 09:49:19 192.168.122.209 [63910.077363] [tempesta fw] modules are stopped Apr 26 09:49:19 192.168.122.209 [63910.337393] [tempesta fw] exiting... Apr 26 09:49:19 192.168.122.209 [63910.436973] [tdb] Shutdown Tempesta DB Apr 26 09:49:20 192.168.122.209 [63910.660531] End test: t_frang.test_whitelist_mark.FrangWhitelistMarkTestCase.test_whitelisted_frang_http_uri_len_xforwarded_for Apr 26 09:49:20 192.168.122.209 [63910.671103] Start test: t_health_monitoring.test_health_monitor.TestHealthMonitor.test Apr 26 09:49:21 192.168.122.209 [63911.728385] [tdb] Start Tempesta DB Apr 26 09:49:21 192.168.122.209 [63911.878379] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:49:23 192.168.122.209 [63914.049197] [tempesta fw] Configuration processing is completed. Apr 26 09:49:23 192.168.122.209 [63914.104604] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:49:23 192.168.122.209 [63914.131359] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:49:23 192.168.122.209 [63914.157760] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:49:23 192.168.122.209 [63914.289208] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:49:23 192.168.122.209 [63914.381105] [tempesta fw] Tempesta FW is ready Apr 26 09:49:24 192.168.122.209 [63915.177025] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8082 Apr 26 09:49:24 192.168.122.209 [63915.213013] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8080 Apr 26 09:49:24 192.168.122.209 [63915.214418] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8081 Apr 26 09:49:25 192.168.122.209 [63916.106000] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8082: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.106084] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8082: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.106143] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8081: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.106244] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8081: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.111181] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8082: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.111265] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8082: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.111293] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8082: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.111323] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8082: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.111371] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8081: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.111420] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8082: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.111533] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8082: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.112081] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8082: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.113634] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8082: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.115875] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8082: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.125558] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8082: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.126676] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8082: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.128318] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8082: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.128383] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8082: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.128452] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8082: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.128490] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8082: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.128502] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8082: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.128551] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8082: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.128557] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8082: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.128612] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8082: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.128615] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8082: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.129946] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8081: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.130591] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8081: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.133549] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8082: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.134432] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8082: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.136960] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8082: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.137875] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8082: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.139297] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8082: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.140210] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8082: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.141609] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8082: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.142593] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8080: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.143903] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8082: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.144534] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8080: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.144625] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8081: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.144663] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8080: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.144822] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8080: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.146303] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8080: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.147207] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8081: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.148066] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8081: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.149012] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8081: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.150271] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8081: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.151153] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8081: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.152087] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8081: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.153026] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8080: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.153962] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8081: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.154884] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8081: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.155831] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8080: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.156749] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8081: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.157697] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8081: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.158627] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8080: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.159581] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8081: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.171840] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8080: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.172813] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8080: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.173805] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8081: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.174253] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8080: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.174778] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8081: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.175730] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8080: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.176660] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8081: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.178660] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8081: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.179690] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8080: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.180787] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8080: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.180798] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8082: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.182638] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8081: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.183902] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8081: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.185746] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8080: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.186886] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8082: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.188139] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8080: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.189099] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8081: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.190443] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8080: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.191229] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8080: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.192635] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8080: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.193629] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8080: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.194947] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8081: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.195848] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8081: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.197208] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8080: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.198136] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8081: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.199069] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8080: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.199999] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8080: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.202075] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8081: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.203053] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8081: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.204078] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8080: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.205067] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8080: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.206032] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8080: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.207000] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8080: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.207966] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8081: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.208967] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8080: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.209958] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8082 Apr 26 09:49:25 192.168.122.209 [63916.209992] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8080: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.210028] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8080: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.210033] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8081: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.210127] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8081: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.210133] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8080: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.215571] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8080: 1 tries, keep trying... Apr 26 09:49:25 192.168.122.209 [63916.233072] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8081 Apr 26 09:49:25 192.168.122.209 [63916.234393] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8080 Apr 26 09:49:26 192.168.122.209 [63917.225004] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8082 Apr 26 09:49:26 192.168.122.209 [63917.257050] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8080 Apr 26 09:49:26 192.168.122.209 [63917.258363] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8081 Apr 26 09:49:27 192.168.122.209 [63918.250625] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8082 Apr 26 09:49:27 192.168.122.209 [63918.280990] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8081 Apr 26 09:49:27 192.168.122.209 [63918.282658] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8080 Apr 26 09:49:28 192.168.122.209 [63919.278253] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8082 Apr 26 09:49:28 192.168.122.209 [63919.305090] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8080 Apr 26 09:49:28 192.168.122.209 [63919.307455] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8081 Apr 26 09:49:29 192.168.122.209 [63920.297798] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8082 Apr 26 09:49:29 192.168.122.209 [63920.329069] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8081 Apr 26 09:49:29 192.168.122.209 [63920.330017] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8080 Apr 26 09:49:30 192.168.122.209 [63921.321285] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8082 Apr 26 09:49:30 192.168.122.209 [63921.353017] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8080 Apr 26 09:49:30 192.168.122.209 [63921.354015] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8081 Apr 26 09:49:31 192.168.122.209 [63922.345043] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8082 Apr 26 09:49:31 192.168.122.209 [63922.381038] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8081 Apr 26 09:49:31 192.168.122.209 [63922.382801] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8080 Apr 26 09:49:32 192.168.122.209 [63923.369172] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8082 Apr 26 09:49:32 192.168.122.209 [63923.405085] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8081 Apr 26 09:49:32 192.168.122.209 [63923.405425] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '400' mismatched Apr 26 09:49:33 192.168.122.209 [63924.393825] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8082 Apr 26 09:49:33 192.168.122.209 [63924.425515] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '400' mismatched Apr 26 09:49:33 192.168.122.209 [63924.428253] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '400' mismatched Apr 26 09:49:33 192.168.122.209 [63924.464491] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:33 192.168.122.209 [63924.540448] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:34 192.168.122.209 [63924.621326] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:34 192.168.122.209 [63924.700346] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:34 192.168.122.209 [63924.779094] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:34 192.168.122.209 [63924.856955] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:34 192.168.122.209 [63924.933505] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:34 192.168.122.209 [63925.014892] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:34 192.168.122.209 [63925.091389] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:34 192.168.122.209 [63925.172285] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:34 192.168.122.209 [63925.257628] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:34 192.168.122.209 [63925.335492] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:34 192.168.122.209 [63925.411910] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:34 192.168.122.209 [63925.417097] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8082 Apr 26 09:49:34 192.168.122.209 [63925.488429] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:34 192.168.122.209 [63925.568244] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:35 192.168.122.209 [63925.648246] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:35 192.168.122.209 [63925.723445] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:35 192.168.122.209 [63925.806057] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:35 192.168.122.209 [63925.891528] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:35 192.168.122.209 [63925.973880] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:35 192.168.122.209 [63926.045936] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:35 192.168.122.209 [63926.130802] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:35 192.168.122.209 [63926.208166] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:35 192.168.122.209 [63926.288650] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:35 192.168.122.209 [63926.370835] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:35 192.168.122.209 [63926.445189] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8082 Apr 26 09:49:35 192.168.122.209 [63926.448301] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:35 192.168.122.209 [63926.528414] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:36 192.168.122.209 [63926.613137] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:36 192.168.122.209 [63926.693593] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:36 192.168.122.209 [63926.774335] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:36 192.168.122.209 [63926.860779] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:36 192.168.122.209 [63926.930542] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:36 192.168.122.209 [63927.008291] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:36 192.168.122.209 [63927.066872] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:36 192.168.122.209 [63927.142109] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:36 192.168.122.209 [63927.231632] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:36 192.168.122.209 [63927.314917] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:36 192.168.122.209 [63927.393666] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:36 192.168.122.209 [63927.465164] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8082 Apr 26 09:49:36 192.168.122.209 [63927.466828] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:36 192.168.122.209 [63927.546208] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:37 192.168.122.209 [63927.626499] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:37 192.168.122.209 [63927.701521] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:37 192.168.122.209 [63927.791469] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:37 192.168.122.209 [63927.881485] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:37 192.168.122.209 [63927.964506] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:37 192.168.122.209 [63928.044949] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:37 192.168.122.209 [63928.138615] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:37 192.168.122.209 [63928.216652] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:37 192.168.122.209 [63928.290838] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:37 192.168.122.209 [63928.372593] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:37 192.168.122.209 [63928.454097] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:37 192.168.122.209 [63928.493095] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8082 Apr 26 09:49:37 192.168.122.209 [63928.532096] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:38 192.168.122.209 [63928.615310] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:38 192.168.122.209 [63928.696797] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:38 192.168.122.209 [63928.771956] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:38 192.168.122.209 [63928.849343] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:38 192.168.122.209 [63928.936405] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:38 192.168.122.209 [63929.012642] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:38 192.168.122.209 [63929.094184] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:38 192.168.122.209 [63929.176435] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:38 192.168.122.209 [63929.253035] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:38 192.168.122.209 [63929.329045] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:38 192.168.122.209 [63929.404116] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:38 192.168.122.209 [63929.482647] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:38 192.168.122.209 [63929.517107] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8082 Apr 26 09:49:38 192.168.122.209 [63929.556191] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:39 192.168.122.209 [63929.632370] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:39 192.168.122.209 [63929.708507] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:39 192.168.122.209 [63929.776237] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:39 192.168.122.209 [63929.859134] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:39 192.168.122.209 [63929.938341] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:39 192.168.122.209 [63930.014022] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:39 192.168.122.209 [63930.094021] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:39 192.168.122.209 [63930.179873] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:39 192.168.122.209 [63930.266661] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:39 192.168.122.209 [63930.348160] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:39 192.168.122.209 [63930.424244] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:39 192.168.122.209 [63930.501622] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:39 192.168.122.209 [63930.541117] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8082 Apr 26 09:49:39 192.168.122.209 [63930.580640] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:40 192.168.122.209 [63930.658240] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:40 192.168.122.209 [63930.735805] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:40 192.168.122.209 [63930.825498] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:40 192.168.122.209 [63930.907491] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:40 192.168.122.209 [63930.996795] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:40 192.168.122.209 [63931.077322] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:40 192.168.122.209 [63931.159597] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:40 192.168.122.209 [63931.235394] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:40 192.168.122.209 [63931.317457] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:40 192.168.122.209 [63931.391942] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:40 192.168.122.209 [63931.471822] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:40 192.168.122.209 [63931.554862] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:40 192.168.122.209 [63931.561233] [tempesta fw] Warning: Unable to find connection for health monitoring of backend server: 127.0.0.3:8082 Apr 26 09:49:41 192.168.122.209 [63931.627806] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:41 192.168.122.209 [63931.697884] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:41 192.168.122.209 [63931.779409] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:41 192.168.122.209 [63931.868275] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:41 192.168.122.209 [63931.947073] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:41 192.168.122.209 [63932.024264] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:41 192.168.122.209 [63932.102233] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:41 192.168.122.209 [63932.185276] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:41 192.168.122.209 [63932.258074] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:41 192.168.122.209 [63932.336260] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:41 192.168.122.209 [63932.585454] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '400' mismatched Apr 26 09:49:43 192.168.122.209 [63933.641451] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '400' mismatched Apr 26 09:49:43 192.168.122.209 [63933.642414] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '400' mismatched Apr 26 09:49:43 192.168.122.209 [63933.650593] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:43 192.168.122.209 [63933.724489] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:43 192.168.122.209 [63933.803434] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:43 192.168.122.209 [63933.881519] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:43 192.168.122.209 [63933.964946] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:43 192.168.122.209 [63934.046545] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:43 192.168.122.209 [63934.131172] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:43 192.168.122.209 [63934.213425] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:43 192.168.122.209 [63934.388127] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:43 192.168.122.209 [63934.547843] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:44 192.168.122.209 [63934.632138] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:44 192.168.122.209 [63934.792917] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:44 192.168.122.209 [63934.967539] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:44 192.168.122.209 [63935.052548] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:44 192.168.122.209 [63935.210815] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:44 192.168.122.209 [63935.368011] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:44 192.168.122.209 [63935.451651] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:45 192.168.122.209 [63935.613117] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:45 192.168.122.209 [63935.765196] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:45 192.168.122.209 [63935.826231] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:45 192.168.122.209 [63935.968049] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:45 192.168.122.209 [63936.130588] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:45 192.168.122.209 [63936.210312] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:45 192.168.122.209 [63936.368407] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:45 192.168.122.209 [63936.518396] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:45 192.168.122.209 [63936.607016] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:46 192.168.122.209 [63936.757096] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:46 192.168.122.209 [63936.824300] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:46 192.168.122.209 [63936.979597] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:46 192.168.122.209 [63937.059350] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:46 192.168.122.209 [63937.230874] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:46 192.168.122.209 [63937.315044] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:46 192.168.122.209 [63937.475419] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:46 192.168.122.209 [63937.558082] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:47 192.168.122.209 [63937.697215] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:47 192.168.122.209 [63937.773975] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:47 192.168.122.209 [63937.837547] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:47 192.168.122.209 [63937.919930] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:47 192.168.122.209 [63938.001610] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:47 192.168.122.209 [63938.082337] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:47 192.168.122.209 [63938.165488] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:47 192.168.122.209 [63938.244923] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:47 192.168.122.209 [63938.391803] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:47 192.168.122.209 [63938.559178] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:48 192.168.122.209 [63938.644256] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:48 192.168.122.209 [63938.793723] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:48 192.168.122.209 [63938.943948] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:48 192.168.122.209 [63939.021983] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:48 192.168.122.209 [63939.186244] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:48 192.168.122.209 [63939.346429] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:48 192.168.122.209 [63939.427613] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:48 192.168.122.209 [63939.595743] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:49 192.168.122.209 [63939.771136] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:49 192.168.122.209 [63939.855136] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:49 192.168.122.209 [63940.008598] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:49 192.168.122.209 [63940.164660] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:49 192.168.122.209 [63940.243610] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:49 192.168.122.209 [63940.409621] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:49 192.168.122.209 [63940.568022] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:50 192.168.122.209 [63940.648028] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:50 192.168.122.209 [63940.818526] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:50 192.168.122.209 [63940.901689] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:50 192.168.122.209 [63941.044446] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:50 192.168.122.209 [63941.114879] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:50 192.168.122.209 [63941.278813] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:50 192.168.122.209 [63941.362443] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:50 192.168.122.209 [63941.529654] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:51 192.168.122.209 [63941.615613] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:51 192.168.122.209 [63941.763702] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:51 192.168.122.209 [63941.835232] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:51 192.168.122.209 [63941.924164] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:51 192.168.122.209 [63942.006420] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:51 192.168.122.209 [63942.094962] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:51 192.168.122.209 [63942.173511] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:51 192.168.122.209 [63942.251138] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:51 192.168.122.209 [63942.336687] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:51 192.168.122.209 [63942.503409] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:52 192.168.122.209 [63942.658062] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:52 192.168.122.209 [63942.735862] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:52 192.168.122.209 [63942.889108] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:52 192.168.122.209 [63943.051578] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:52 192.168.122.209 [63943.122105] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:52 192.168.122.209 [63943.288471] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:52 192.168.122.209 [63943.452836] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:52 192.168.122.209 [63943.530434] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:53 192.168.122.209 [63943.682618] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:53 192.168.122.209 [63943.840320] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:53 192.168.122.209 [63943.920882] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:53 192.168.122.209 [63944.061822] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:53 192.168.122.209 [63944.219697] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:53 192.168.122.209 [63944.299676] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:53 192.168.122.209 [63944.455239] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:54 192.168.122.209 [63944.617455] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:54 192.168.122.209 [63944.703725] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:54 192.168.122.209 [63944.869905] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:54 192.168.122.209 [63944.950882] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:54 192.168.122.209 [63945.087881] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:54 192.168.122.209 [63945.168311] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:54 192.168.122.209 [63945.328232] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:54 192.168.122.209 [63945.409622] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:54 192.168.122.209 [63945.561148] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:55 192.168.122.209 [63945.636406] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:55 192.168.122.209 [63945.795807] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:55 192.168.122.209 [63945.875125] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:55 192.168.122.209 [63945.965403] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:55 192.168.122.209 [63946.047310] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:55 192.168.122.209 [63946.130236] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:55 192.168.122.209 [63946.210232] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:55 192.168.122.209 [63946.292159] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:55 192.168.122.209 [63946.390545] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:55 192.168.122.209 [63946.547008] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:56 192.168.122.209 [63946.699184] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:56 192.168.122.209 [63946.776713] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:56 192.168.122.209 [63946.933481] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:56 192.168.122.209 [63947.094559] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:56 192.168.122.209 [63947.176536] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:56 192.168.122.209 [63947.319235] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:56 192.168.122.209 [63947.474987] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:56 192.168.122.209 [63947.551415] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:57 192.168.122.209 [63947.701861] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:57 192.168.122.209 [63947.860994] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:57 192.168.122.209 [63947.936269] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:57 192.168.122.209 [63948.087262] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:57 192.168.122.209 [63948.245908] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:57 192.168.122.209 [63948.328969] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:57 192.168.122.209 [63948.476444] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:58 192.168.122.209 [63948.641362] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:58 192.168.122.209 [63948.726505] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:58 192.168.122.209 [63948.895656] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:58 192.168.122.209 [63948.970712] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:58 192.168.122.209 [63949.141092] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:58 192.168.122.209 [63949.224108] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '403' mismatched Apr 26 09:49:58 192.168.122.209 [63949.391045] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '404' mismatched Apr 26 09:49:59 192.168.122.209 [63949.944535] [tdb] Close table 'client0.tdb' Apr 26 09:49:59 192.168.122.209 [63950.117916] [tdb] Close table 'sessions0.tdb' Apr 26 09:49:59 192.168.122.209 [63950.343336] [tdb] Close table 'filter0.tdb' Apr 26 09:49:59 192.168.122.209 [63950.343735] [tempesta fw] modules are stopped Apr 26 09:49:59 192.168.122.209 [63950.554718] [tempesta fw] exiting... Apr 26 09:50:00 192.168.122.209 [63950.698490] [tdb] Shutdown Tempesta DB Apr 26 09:50:00 192.168.122.209 [63950.977084] End test: t_health_monitoring.test_health_monitor.TestHealthMonitor.test Apr 26 09:50:00 192.168.122.209 [63950.986950] Start test: t_health_monitoring.test_health_monitor.TestHealthMonitorForDisabledServer.test Apr 26 09:50:01 192.168.122.209 [63952.039051] [tdb] Start Tempesta DB Apr 26 09:50:01 192.168.122.209 [63952.189222] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:50:02 192.168.122.209 [63953.165499] [tempesta fw] Configuration processing is completed. Apr 26 09:50:02 192.168.122.209 [63953.209865] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:50:03 192.168.122.209 [63953.679855] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:50:03 192.168.122.209 [63953.713163] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:50:03 192.168.122.209 [63953.751022] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:50:03 192.168.122.209 [63953.797572] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:50:03 192.168.122.209 [63953.837518] [tempesta fw] Tempesta FW is ready Apr 26 09:50:04 192.168.122.209 [63955.399848] [tdb] Close table 'client0.tdb' Apr 26 09:50:04 192.168.122.209 [63955.571941] [tdb] Close table 'sessions0.tdb' Apr 26 09:50:08 192.168.122.209 [63958.821072] [tdb] Close table 'cache0.tdb' Apr 26 09:50:08 192.168.122.209 [63959.077104] [tdb] Close table 'filter0.tdb' Apr 26 09:50:08 192.168.122.209 [63959.077535] [tempesta fw] modules are stopped Apr 26 09:50:08 192.168.122.209 [63959.300126] [tempesta fw] exiting... Apr 26 09:50:08 192.168.122.209 [63959.415054] [tdb] Shutdown Tempesta DB Apr 26 09:50:08 192.168.122.209 [63959.606933] End test: t_health_monitoring.test_health_monitor.TestHealthMonitorForDisabledServer.test Apr 26 09:50:09 192.168.122.209 [63959.620136] Start test: t_health_monitoring.test_health_monitor.TestHealthStatH2.test_cached_responses_included Apr 26 09:50:10 192.168.122.209 [63960.690504] [tdb] Start Tempesta DB Apr 26 09:50:10 192.168.122.209 [63960.832360] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:50:11 192.168.122.209 [63962.191012] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63962.191012] Maybe that's fine, but it's worth checking the [63962.191012] config - if there is no relations between the [63962.191012] names, then host name confusion attack is possible. Apr 26 09:50:11 192.168.122.209 [63962.321722] [tempesta fw] Configuration processing is completed. Apr 26 09:50:11 192.168.122.209 [63962.373812] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:50:12 192.168.122.209 [63962.786965] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:50:12 192.168.122.209 [63962.813172] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:50:12 192.168.122.209 [63962.840315] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:50:12 192.168.122.209 [63962.889719] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:50:12 192.168.122.209 [63962.891569] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:50:12 192.168.122.209 [63962.957634] [tempesta fw] Tempesta FW is ready Apr 26 09:50:13 192.168.122.209 [63963.612795] [tdb] Close table 'client0.tdb' Apr 26 09:50:13 192.168.122.209 [63963.813164] [tdb] Close table 'sessions0.tdb' Apr 26 09:50:16 192.168.122.209 [63967.013727] [tdb] Close table 'cache0.tdb' Apr 26 09:50:16 192.168.122.209 [63967.245624] [tdb] Close table 'filter0.tdb' Apr 26 09:50:16 192.168.122.209 [63967.246080] [tempesta fw] modules are stopped Apr 26 09:50:16 192.168.122.209 [63967.467303] [tempesta fw] exiting... Apr 26 09:50:16 192.168.122.209 [63967.573262] [tdb] Shutdown Tempesta DB Apr 26 09:50:17 192.168.122.209 [63967.780413] End test: t_health_monitoring.test_health_monitor.TestHealthStatH2.test_cached_responses_included Apr 26 09:50:17 192.168.122.209 [63967.796567] Start test: t_health_monitoring.test_health_monitor.TestHealthStatH2.test_smoke Apr 26 09:50:18 192.168.122.209 [63968.798505] [tdb] Start Tempesta DB Apr 26 09:50:18 192.168.122.209 [63968.935405] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:50:19 192.168.122.209 [63970.211087] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63970.211087] Maybe that's fine, but it's worth checking the [63970.211087] config - if there is no relations between the [63970.211087] names, then host name confusion attack is possible. Apr 26 09:50:19 192.168.122.209 [63970.309717] [tempesta fw] Configuration processing is completed. Apr 26 09:50:19 192.168.122.209 [63970.369988] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:50:20 192.168.122.209 [63970.774760] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:50:20 192.168.122.209 [63970.799996] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:50:20 192.168.122.209 [63970.825166] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:50:20 192.168.122.209 [63970.877772] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:50:20 192.168.122.209 [63970.879555] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:50:20 192.168.122.209 [63970.917689] [tempesta fw] Tempesta FW is ready Apr 26 09:50:21 192.168.122.209 [63971.721437] [tdb] Close table 'client0.tdb' Apr 26 09:50:21 192.168.122.209 [63971.906925] [tdb] Close table 'sessions0.tdb' Apr 26 09:50:24 192.168.122.209 [63975.083812] [tdb] Close table 'cache0.tdb' Apr 26 09:50:24 192.168.122.209 [63975.321614] [tdb] Close table 'filter0.tdb' Apr 26 09:50:24 192.168.122.209 [63975.322033] [tempesta fw] modules are stopped Apr 26 09:50:24 192.168.122.209 [63975.526582] [tempesta fw] exiting... Apr 26 09:50:25 192.168.122.209 [63975.643346] [tdb] Shutdown Tempesta DB Apr 26 09:50:25 192.168.122.209 [63975.843318] End test: t_health_monitoring.test_health_monitor.TestHealthStatH2.test_smoke Apr 26 09:50:25 192.168.122.209 [63975.867311] Start test: t_health_monitoring.test_health_monitor.TestHealthStatHttp.test_cached_responses_included Apr 26 09:50:26 192.168.122.209 [63976.914208] [tdb] Start Tempesta DB Apr 26 09:50:26 192.168.122.209 [63977.042583] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:50:27 192.168.122.209 [63978.451104] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63978.451104] Maybe that's fine, but it's worth checking the [63978.451104] config - if there is no relations between the [63978.451104] names, then host name confusion attack is possible. Apr 26 09:50:27 192.168.122.209 [63978.593853] [tempesta fw] Configuration processing is completed. Apr 26 09:50:28 192.168.122.209 [63978.651987] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:50:28 192.168.122.209 [63979.056091] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:50:28 192.168.122.209 [63979.081200] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:50:28 192.168.122.209 [63979.106122] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:50:28 192.168.122.209 [63979.157851] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:50:28 192.168.122.209 [63979.159598] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:50:28 192.168.122.209 [63979.221809] [tempesta fw] Tempesta FW is ready Apr 26 09:50:29 192.168.122.209 [63979.802596] [tdb] Close table 'client0.tdb' Apr 26 09:50:29 192.168.122.209 [63979.992661] [tdb] Close table 'sessions0.tdb' Apr 26 09:50:32 192.168.122.209 [63983.190679] [tdb] Close table 'cache0.tdb' Apr 26 09:50:32 192.168.122.209 [63983.448533] [tdb] Close table 'filter0.tdb' Apr 26 09:50:32 192.168.122.209 [63983.448981] [tempesta fw] modules are stopped Apr 26 09:50:33 192.168.122.209 [63983.672678] [tempesta fw] exiting... Apr 26 09:50:33 192.168.122.209 [63983.796201] [tdb] Shutdown Tempesta DB Apr 26 09:50:33 192.168.122.209 [63984.011249] End test: t_health_monitoring.test_health_monitor.TestHealthStatHttp.test_cached_responses_included Apr 26 09:50:33 192.168.122.209 [63984.021771] Start test: t_health_monitoring.test_health_monitor.TestHealthStatHttp.test_smoke Apr 26 09:50:34 192.168.122.209 [63985.042106] [tdb] Start Tempesta DB Apr 26 09:50:34 192.168.122.209 [63985.191809] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:50:35 192.168.122.209 [63986.551187] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63986.551187] Maybe that's fine, but it's worth checking the [63986.551187] config - if there is no relations between the [63986.551187] names, then host name confusion attack is possible. Apr 26 09:50:36 192.168.122.209 [63986.650025] [tempesta fw] Configuration processing is completed. Apr 26 09:50:36 192.168.122.209 [63986.713404] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:50:36 192.168.122.209 [63987.119126] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:50:36 192.168.122.209 [63987.152213] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:50:36 192.168.122.209 [63987.176935] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:50:36 192.168.122.209 [63987.221926] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:50:36 192.168.122.209 [63987.223676] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:50:36 192.168.122.209 [63987.269884] [tempesta fw] Tempesta FW is ready Apr 26 09:50:37 192.168.122.209 [63988.029897] [tdb] Close table 'client0.tdb' Apr 26 09:50:37 192.168.122.209 [63988.225622] [tdb] Close table 'sessions0.tdb' Apr 26 09:50:40 192.168.122.209 [63991.419641] [tdb] Close table 'cache0.tdb' Apr 26 09:50:41 192.168.122.209 [63991.654690] [tdb] Close table 'filter0.tdb' Apr 26 09:50:41 192.168.122.209 [63991.655123] [tempesta fw] modules are stopped Apr 26 09:50:41 192.168.122.209 [63991.921818] [tempesta fw] exiting... Apr 26 09:50:41 192.168.122.209 [63992.074677] [tdb] Shutdown Tempesta DB Apr 26 09:50:41 192.168.122.209 [63992.322552] End test: t_health_monitoring.test_health_monitor.TestHealthStatHttp.test_smoke Apr 26 09:50:41 192.168.122.209 [63992.343309] Start test: t_health_monitoring.test_health_monitor.TestHealthStatServerH2.test_smoke Apr 26 09:50:42 192.168.122.209 [63993.441669] [tdb] Start Tempesta DB Apr 26 09:50:42 192.168.122.209 [63993.567096] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:50:44 192.168.122.209 [63994.911294] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [63994.911294] Maybe that's fine, but it's worth checking the [63994.911294] config - if there is no relations between the [63994.911294] names, then host name confusion attack is possible. Apr 26 09:50:44 192.168.122.209 [63995.034065] [tempesta fw] Configuration processing is completed. Apr 26 09:50:44 192.168.122.209 [63995.088509] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:50:44 192.168.122.209 [63995.562541] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:50:44 192.168.122.209 [63995.594589] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:50:45 192.168.122.209 [63995.626893] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:50:45 192.168.122.209 [63995.686016] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:50:45 192.168.122.209 [63995.687742] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:50:45 192.168.122.209 [63995.725962] [tempesta fw] Tempesta FW is ready Apr 26 09:50:45 192.168.122.209 [63996.537232] [tdb] Close table 'client0.tdb' Apr 26 09:50:46 192.168.122.209 [63996.741471] [tdb] Close table 'sessions0.tdb' Apr 26 09:50:49 192.168.122.209 [63999.932744] [tdb] Close table 'cache0.tdb' Apr 26 09:50:49 192.168.122.209 [64000.188376] [tdb] Close table 'filter0.tdb' Apr 26 09:50:49 192.168.122.209 [64000.188820] [tempesta fw] modules are stopped Apr 26 09:50:49 192.168.122.209 [64000.409066] [tempesta fw] exiting... Apr 26 09:50:49 192.168.122.209 [64000.538088] [tdb] Shutdown Tempesta DB Apr 26 09:50:50 192.168.122.209 [64000.735582] End test: t_health_monitoring.test_health_monitor.TestHealthStatServerH2.test_smoke Apr 26 09:50:50 192.168.122.209 [64000.750431] Start test: t_health_monitoring.test_health_monitor.TestHealthStatServerHttp.test_smoke Apr 26 09:50:51 192.168.122.209 [64001.760317] [tdb] Start Tempesta DB Apr 26 09:50:51 192.168.122.209 [64001.900046] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:50:52 192.168.122.209 [64003.254944] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64003.254944] Maybe that's fine, but it's worth checking the [64003.254944] config - if there is no relations between the [64003.254944] names, then host name confusion attack is possible. Apr 26 09:50:52 192.168.122.209 [64003.370158] [tempesta fw] Configuration processing is completed. Apr 26 09:50:52 192.168.122.209 [64003.420651] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:50:53 192.168.122.209 [64003.869747] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:50:53 192.168.122.209 [64003.894934] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:50:53 192.168.122.209 [64003.921095] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:50:53 192.168.122.209 [64003.966076] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:50:53 192.168.122.209 [64003.967480] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:50:53 192.168.122.209 [64004.006056] [tempesta fw] Tempesta FW is ready Apr 26 09:50:54 192.168.122.209 [64004.811015] [tdb] Close table 'client0.tdb' Apr 26 09:50:54 192.168.122.209 [64005.006329] [tdb] Close table 'sessions0.tdb' Apr 26 09:50:57 192.168.122.209 [64008.243767] [tdb] Close table 'cache0.tdb' Apr 26 09:50:57 192.168.122.209 [64008.485907] [tdb] Close table 'filter0.tdb' Apr 26 09:50:57 192.168.122.209 [64008.486357] [tempesta fw] modules are stopped Apr 26 09:50:58 192.168.122.209 [64008.654401] [tempesta fw] exiting... Apr 26 09:50:58 192.168.122.209 [64008.768040] [tdb] Shutdown Tempesta DB Apr 26 09:50:58 192.168.122.209 [64008.957580] End test: t_health_monitoring.test_health_monitor.TestHealthStatServerHttp.test_smoke Apr 26 09:50:58 192.168.122.209 [64008.975384] Start test: t_health_monitoring.test_health_monitor.TestHmCrcExplicitCRC.test Apr 26 09:50:59 192.168.122.209 [64010.023880] [tdb] Start Tempesta DB Apr 26 09:50:59 192.168.122.209 [64010.173103] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:51:01 192.168.122.209 [64011.762279] [tempesta fw] Configuration processing is completed. Apr 26 09:51:01 192.168.122.209 [64011.821784] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:51:01 192.168.122.209 [64012.225469] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:51:01 192.168.122.209 [64012.251501] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:51:01 192.168.122.209 [64012.276378] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:51:01 192.168.122.209 [64012.318206] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:51:01 192.168.122.209 [64012.366162] [tempesta fw] Tempesta FW is ready Apr 26 09:51:10 192.168.122.209 [64021.558788] [tempesta fw] Warning: Response for health monitor 'auto': crc32 value '3332881455' mismatched (expected value: '838041247') Apr 26 09:51:11 192.168.122.209 [64022.046943] [tdb] Close table 'client0.tdb' Apr 26 09:51:11 192.168.122.209 [64022.231210] [tdb] Close table 'sessions0.tdb' Apr 26 09:51:14 192.168.122.209 [64025.519139] [tdb] Close table 'cache0.tdb' Apr 26 09:51:15 192.168.122.209 [64025.729811] [tdb] Close table 'filter0.tdb' Apr 26 09:51:15 192.168.122.209 [64025.730249] [tempesta fw] modules are stopped Apr 26 09:51:15 192.168.122.209 [64025.929431] [tempesta fw] exiting... Apr 26 09:51:15 192.168.122.209 [64026.050181] [tdb] Shutdown Tempesta DB Apr 26 09:51:15 192.168.122.209 [64026.258310] End test: t_health_monitoring.test_health_monitor.TestHmCrcExplicitCRC.test Apr 26 09:51:15 192.168.122.209 [64026.291588] Start test: t_health_monitoring.test_health_monitor.TestHmCrcImplicitCRC.test Apr 26 09:51:16 192.168.122.209 [64027.344576] [tdb] Start Tempesta DB Apr 26 09:51:16 192.168.122.209 [64027.473419] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:51:18 192.168.122.209 [64028.882483] [tempesta fw] Configuration processing is completed. Apr 26 09:51:18 192.168.122.209 [64028.941204] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:51:18 192.168.122.209 [64029.353739] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:51:18 192.168.122.209 [64029.393590] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:51:18 192.168.122.209 [64029.423927] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:51:18 192.168.122.209 [64029.470319] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:51:18 192.168.122.209 [64029.506361] [tempesta fw] Tempesta FW is ready Apr 26 09:51:49 192.168.122.209 [64059.952927] [tempesta fw] Warning: Response for health monitor 'auto': crc32 value '3332881455' mismatched (expected value: '838041247') Apr 26 09:51:49 192.168.122.209 [64060.444977] [tdb] Close table 'client0.tdb' Apr 26 09:51:50 192.168.122.209 [64060.630109] [tdb] Close table 'sessions0.tdb' Apr 26 09:51:53 192.168.122.209 [64063.873002] [tdb] Close table 'cache0.tdb' Apr 26 09:51:53 192.168.122.209 [64064.125650] [tdb] Close table 'filter0.tdb' Apr 26 09:51:53 192.168.122.209 [64064.126083] [tempesta fw] modules are stopped Apr 26 09:51:53 192.168.122.209 [64064.287865] [tempesta fw] exiting... Apr 26 09:51:53 192.168.122.209 [64064.410518] [tdb] Shutdown Tempesta DB Apr 26 09:51:54 192.168.122.209 [64064.629856] End test: t_health_monitoring.test_health_monitor.TestHmCrcImplicitCRC.test Apr 26 09:51:54 192.168.122.209 [64064.643946] Start test: t_health_monitoring.test_health_monitor.TestHmCrcPredefinedCRC.test Apr 26 09:51:55 192.168.122.209 [64065.776885] [tdb] Start Tempesta DB Apr 26 09:51:55 192.168.122.209 [64065.916603] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:51:56 192.168.122.209 [64067.563211] [tempesta fw] Configuration processing is completed. Apr 26 09:51:57 192.168.122.209 [64067.615788] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:51:57 192.168.122.209 [64068.031243] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:51:57 192.168.122.209 [64068.057683] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:51:57 192.168.122.209 [64068.083551] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:51:57 192.168.122.209 [64068.130832] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:51:57 192.168.122.209 [64068.170774] [tempesta fw] Tempesta FW is ready Apr 26 09:52:03 192.168.122.209 [64074.289316] [tempesta fw] Warning: Response for health monitor 'hm0': crc32 value '3332881455' mismatched (expected value: '838041247') Apr 26 09:52:04 192.168.122.209 [64074.772166] [tdb] Close table 'client0.tdb' Apr 26 09:52:04 192.168.122.209 [64074.977328] [tdb] Close table 'sessions0.tdb' Apr 26 09:52:07 192.168.122.209 [64078.203043] [tdb] Close table 'cache0.tdb' Apr 26 09:52:07 192.168.122.209 [64078.439455] [tdb] Close table 'filter0.tdb' Apr 26 09:52:07 192.168.122.209 [64078.439892] [tempesta fw] modules are stopped Apr 26 09:52:08 192.168.122.209 [64078.642874] [tempesta fw] exiting... Apr 26 09:52:08 192.168.122.209 [64078.794572] [tdb] Shutdown Tempesta DB Apr 26 09:52:08 192.168.122.209 [64079.008467] End test: t_health_monitoring.test_health_monitor.TestHmCrcPredefinedCRC.test Apr 26 09:52:08 192.168.122.209 [64079.018123] Start test: t_health_monitoring.test_health_monitor.TestHmMalformedResponse.test Apr 26 09:52:09 192.168.122.209 [64080.120631] [tdb] Start Tempesta DB Apr 26 09:52:09 192.168.122.209 [64080.262129] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:52:11 192.168.122.209 [64081.839026] [tempesta fw] Configuration processing is completed. Apr 26 09:52:11 192.168.122.209 [64081.893075] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:52:11 192.168.122.209 [64082.287848] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:52:11 192.168.122.209 [64082.313790] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:52:11 192.168.122.209 [64082.338606] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:52:11 192.168.122.209 [64082.386995] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:52:11 192.168.122.209 [64082.426933] [tempesta fw] Tempesta FW is ready Apr 26 09:52:12 192.168.122.209 [64083.374583] [tempesta fw] Warning: Parser error: state=RGen_HdrOtherN input(-0)=0x20(' ') data_len=1 off=0 Apr 26 09:52:12 192.168.122.209 [64083.375464] [tempesta fw] Warning: Health Monitor response malformed Apr 26 09:52:12 192.168.122.209 [64083.375718] [tempesta fw] Warning: Paired request missing, HTTP Response Splitting attack? Apr 26 09:52:13 192.168.122.209 [64083.868798] [tdb] Close table 'client0.tdb' Apr 26 09:52:13 192.168.122.209 [64084.051814] [tdb] Close table 'sessions0.tdb' Apr 26 09:52:16 192.168.122.209 [64087.208477] [tdb] Close table 'cache0.tdb' Apr 26 09:52:16 192.168.122.209 [64087.453908] [tdb] Close table 'filter0.tdb' Apr 26 09:52:16 192.168.122.209 [64087.454349] [tempesta fw] modules are stopped Apr 26 09:52:17 192.168.122.209 [64087.621625] [tempesta fw] exiting... Apr 26 09:52:17 192.168.122.209 [64087.739846] [tdb] Shutdown Tempesta DB Apr 26 09:52:17 192.168.122.209 [64087.954289] End test: t_health_monitoring.test_health_monitor.TestHmMalformedResponse.test Apr 26 09:52:17 192.168.122.209 [64087.968724] Start test: t_http_rules.test_backup_servers.HttpRulesBackupServers.test_scheduler Apr 26 09:52:18 192.168.122.209 [64089.025925] [tdb] Start Tempesta DB Apr 26 09:52:18 192.168.122.209 [64089.164106] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:52:19 192.168.122.209 [64090.580411] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64090.580411] Maybe that's fine, but it's worth checking the [64090.580411] config - if there is no relations between the [64090.580411] names, then host name confusion attack is possible. Apr 26 09:52:20 192.168.122.209 [64090.767132] [tempesta fw] Configuration processing is completed. Apr 26 09:52:20 192.168.122.209 [64090.822406] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:52:20 192.168.122.209 [64090.849957] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:52:20 192.168.122.209 [64090.877982] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:52:20 192.168.122.209 [64090.943091] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:52:20 192.168.122.209 [64090.944905] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:52:20 192.168.122.209 [64090.983057] [tempesta fw] Tempesta FW is ready Apr 26 09:52:23 192.168.122.209 [64093.682177] [tdb] Close table 'client0.tdb' Apr 26 09:52:23 192.168.122.209 [64093.871818] [tdb] Close table 'sessions0.tdb' Apr 26 09:52:23 192.168.122.209 [64094.086131] [tdb] Close table 'filter0.tdb' Apr 26 09:52:23 192.168.122.209 [64094.086588] [tempesta fw] modules are stopped Apr 26 09:52:23 192.168.122.209 [64094.306149] [tempesta fw] exiting... Apr 26 09:52:23 192.168.122.209 [64094.419095] [tdb] Shutdown Tempesta DB Apr 26 09:52:24 192.168.122.209 [64094.643977] End test: t_http_rules.test_backup_servers.HttpRulesBackupServers.test_scheduler Apr 26 09:52:24 192.168.122.209 [64094.664138] Start test: t_http_rules.test_h2_backup_servers.HttpRulesBackupServersH2.test_scheduler Apr 26 09:52:25 192.168.122.209 [64095.722853] [tdb] Start Tempesta DB Apr 26 09:52:25 192.168.122.209 [64095.855758] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:52:26 192.168.122.209 [64096.644456] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64096.644456] Maybe that's fine, but it's worth checking the [64096.644456] config - if there is no relations between the [64096.644456] names, then host name confusion attack is possible. Apr 26 09:52:26 192.168.122.209 [64096.827182] [tempesta fw] Configuration processing is completed. Apr 26 09:52:26 192.168.122.209 [64096.893656] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:52:26 192.168.122.209 [64096.920129] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 09:52:26 192.168.122.209 [64096.957985] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 09:52:26 192.168.122.209 [64097.023151] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:52:26 192.168.122.209 [64097.024947] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:52:26 192.168.122.209 [64097.079108] [tempesta fw] Tempesta FW is ready Apr 26 09:52:29 192.168.122.209 [64099.772219] [tdb] Close table 'client0.tdb' Apr 26 09:52:29 192.168.122.209 [64099.960184] [tdb] Close table 'sessions0.tdb' Apr 26 09:52:29 192.168.122.209 [64100.220157] [tdb] Close table 'filter0.tdb' Apr 26 09:52:29 192.168.122.209 [64100.220598] [tempesta fw] modules are stopped Apr 26 09:52:29 192.168.122.209 [64100.436358] [tempesta fw] exiting... Apr 26 09:52:29 192.168.122.209 [64100.555298] [tdb] Shutdown Tempesta DB Apr 26 09:52:30 192.168.122.209 [64100.766313] End test: t_http_rules.test_h2_backup_servers.HttpRulesBackupServersH2.test_scheduler Apr 26 09:52:30 192.168.122.209 [64100.778523] Start test: t_http_rules.test_h2_http_rules.HttpRulesH2.test_scheduler Apr 26 09:52:31 192.168.122.209 [64101.846965] [tdb] Start Tempesta DB Apr 26 09:52:31 192.168.122.209 [64101.971969] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:52:33 192.168.122.209 [64103.620679] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64103.620679] Maybe that's fine, but it's worth checking the [64103.620679] config - if there is no relations between the [64103.620679] names, then host name confusion attack is possible. Apr 26 09:52:33 192.168.122.209 [64104.247592] [tempesta fw] Configuration processing is completed. Apr 26 09:52:33 192.168.122.209 [64104.303588] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:52:34 192.168.122.209 [64104.713960] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:52:34 192.168.122.209 [64104.740228] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:52:34 192.168.122.209 [64104.765225] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:52:34 192.168.122.209 [64105.151259] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:52:34 192.168.122.209 [64105.153129] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:52:34 192.168.122.209 [64105.191215] [tempesta fw] Tempesta FW is ready Apr 26 09:52:39 192.168.122.209 [64109.807996] [tdb] Close table 'client0.tdb' Apr 26 09:52:39 192.168.122.209 [64109.990414] [tdb] Close table 'sessions0.tdb' Apr 26 09:52:42 192.168.122.209 [64113.202320] [tdb] Close table 'cache0.tdb' Apr 26 09:52:42 192.168.122.209 [64113.450216] [tdb] Close table 'filter0.tdb' Apr 26 09:52:42 192.168.122.209 [64113.450661] [tempesta fw] modules are stopped Apr 26 09:52:43 192.168.122.209 [64113.910854] [tempesta fw] exiting... Apr 26 09:52:43 192.168.122.209 [64114.056208] [tdb] Shutdown Tempesta DB Apr 26 09:52:43 192.168.122.209 [64114.250078] End test: t_http_rules.test_h2_http_rules.HttpRulesH2.test_scheduler Apr 26 09:52:43 192.168.122.209 [64114.274626] Start test: t_http_rules.test_h2_http_rules.TestH2Host.test_different_authority_and_host_headers Apr 26 09:52:44 192.168.122.209 [64115.291010] [tdb] Start Tempesta DB Apr 26 09:52:44 192.168.122.209 [64115.440404] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:52:46 192.168.122.209 [64117.104909] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64117.104909] Maybe that's fine, but it's worth checking the [64117.104909] config - if there is no relations between the [64117.104909] names, then host name confusion attack is possible. Apr 26 09:52:46 192.168.122.209 [64117.367541] [tempesta fw] Configuration processing is completed. Apr 26 09:52:46 192.168.122.209 [64117.417722] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:52:47 192.168.122.209 [64117.827717] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:52:47 192.168.122.209 [64117.854877] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:52:47 192.168.122.209 [64117.880388] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:52:47 192.168.122.209 [64117.995396] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:52:47 192.168.122.209 [64117.997224] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:52:47 192.168.122.209 [64118.043333] [tempesta fw] Tempesta FW is ready Apr 26 09:52:48 192.168.122.209 [64118.858984] [tdb] Close table 'client0.tdb' Apr 26 09:52:48 192.168.122.209 [64119.045543] [tdb] Close table 'sessions0.tdb' Apr 26 09:52:51 192.168.122.209 [64122.242914] [tdb] Close table 'cache0.tdb' Apr 26 09:52:51 192.168.122.209 [64122.466956] [tdb] Close table 'filter0.tdb' Apr 26 09:52:51 192.168.122.209 [64122.467383] [tempesta fw] modules are stopped Apr 26 09:52:52 192.168.122.209 [64122.715579] [tempesta fw] exiting... Apr 26 09:52:52 192.168.122.209 [64122.852010] [tdb] Shutdown Tempesta DB Apr 26 09:52:52 192.168.122.209 [64123.055581] End test: t_http_rules.test_h2_http_rules.TestH2Host.test_different_authority_and_host_headers Apr 26 09:52:52 192.168.122.209 [64123.077083] Start test: t_http_rules.test_h2_http_rules.TestH2Host.test_hdr_host_in_authority_header Apr 26 09:52:53 192.168.122.209 [64124.068356] [tdb] Start Tempesta DB Apr 26 09:52:53 192.168.122.209 [64124.201229] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:52:55 192.168.122.209 [64125.864831] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64125.864831] Maybe that's fine, but it's worth checking the [64125.864831] config - if there is no relations between the [64125.864831] names, then host name confusion attack is possible. Apr 26 09:52:55 192.168.122.209 [64126.127464] [tempesta fw] Configuration processing is completed. Apr 26 09:52:55 192.168.122.209 [64126.194314] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:52:55 192.168.122.209 [64126.599979] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:52:56 192.168.122.209 [64126.625522] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:52:56 192.168.122.209 [64126.650952] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:52:56 192.168.122.209 [64126.755507] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:52:56 192.168.122.209 [64126.757309] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:52:56 192.168.122.209 [64126.799435] [tempesta fw] Tempesta FW is ready Apr 26 09:52:56 192.168.122.209 [64127.590532] [tdb] Close table 'client0.tdb' Apr 26 09:52:57 192.168.122.209 [64127.776049] [tdb] Close table 'sessions0.tdb' Apr 26 09:53:00 192.168.122.209 [64130.954095] [tdb] Close table 'cache0.tdb' Apr 26 09:53:00 192.168.122.209 [64131.204990] [tdb] Close table 'filter0.tdb' Apr 26 09:53:00 192.168.122.209 [64131.205427] [tempesta fw] modules are stopped Apr 26 09:53:00 192.168.122.209 [64131.494631] [tempesta fw] exiting... Apr 26 09:53:00 192.168.122.209 [64131.606061] [tdb] Shutdown Tempesta DB Apr 26 09:53:01 192.168.122.209 [64131.810016] End test: t_http_rules.test_h2_http_rules.TestH2Host.test_hdr_host_in_authority_header Apr 26 09:53:01 192.168.122.209 [64131.831703] Start test: t_http_rules.test_h2_http_rules.TestH2Host.test_hdr_host_in_forwarded_header Apr 26 09:53:02 192.168.122.209 [64132.830578] [tdb] Start Tempesta DB Apr 26 09:53:02 192.168.122.209 [64132.965098] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:53:04 192.168.122.209 [64134.632897] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64134.632897] Maybe that's fine, but it's worth checking the [64134.632897] config - if there is no relations between the [64134.632897] names, then host name confusion attack is possible. Apr 26 09:53:04 192.168.122.209 [64134.847656] [tempesta fw] Configuration processing is completed. Apr 26 09:53:04 192.168.122.209 [64134.908065] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:53:04 192.168.122.209 [64135.335261] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:53:04 192.168.122.209 [64135.362055] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:53:04 192.168.122.209 [64135.387370] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:53:04 192.168.122.209 [64135.467582] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:53:04 192.168.122.209 [64135.469418] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:53:04 192.168.122.209 [64135.515548] [tempesta fw] Tempesta FW is ready Apr 26 09:53:05 192.168.122.209 [64136.378751] [tdb] Close table 'client0.tdb' Apr 26 09:53:05 192.168.122.209 [64136.559744] [tdb] Close table 'sessions0.tdb' Apr 26 09:53:09 192.168.122.209 [64139.702108] [tdb] Close table 'cache0.tdb' Apr 26 09:53:09 192.168.122.209 [64139.945847] [tdb] Close table 'filter0.tdb' Apr 26 09:53:09 192.168.122.209 [64139.946281] [tempesta fw] modules are stopped Apr 26 09:53:09 192.168.122.209 [64140.210661] [tempesta fw] exiting... Apr 26 09:53:09 192.168.122.209 [64140.330191] [tdb] Shutdown Tempesta DB Apr 26 09:53:09 192.168.122.209 [64140.539257] End test: t_http_rules.test_h2_http_rules.TestH2Host.test_hdr_host_in_forwarded_header Apr 26 09:53:09 192.168.122.209 [64140.558184] Start test: t_http_rules.test_h2_http_rules.TestH2Host.test_host_in_authority_header Apr 26 09:53:10 192.168.122.209 [64141.598132] [tdb] Start Tempesta DB Apr 26 09:53:11 192.168.122.209 [64141.734416] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:53:12 192.168.122.209 [64143.414558] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64143.414558] Maybe that's fine, but it's worth checking the [64143.414558] config - if there is no relations between the [64143.414558] names, then host name confusion attack is possible. Apr 26 09:53:13 192.168.122.209 [64143.643734] [tempesta fw] Configuration processing is completed. Apr 26 09:53:13 192.168.122.209 [64143.697529] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:53:13 192.168.122.209 [64144.139917] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:53:13 192.168.122.209 [64144.167975] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:53:13 192.168.122.209 [64144.195812] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:53:13 192.168.122.209 [64144.315711] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:53:13 192.168.122.209 [64144.317597] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:53:13 192.168.122.209 [64144.355678] [tempesta fw] Tempesta FW is ready Apr 26 09:53:14 192.168.122.209 [64145.141710] [tdb] Close table 'client0.tdb' Apr 26 09:53:14 192.168.122.209 [64145.328478] [tdb] Close table 'sessions0.tdb' Apr 26 09:53:17 192.168.122.209 [64148.525316] [tdb] Close table 'cache0.tdb' Apr 26 09:53:18 192.168.122.209 [64148.778597] [tdb] Close table 'filter0.tdb' Apr 26 09:53:18 192.168.122.209 [64148.779000] [tempesta fw] modules are stopped Apr 26 09:53:18 192.168.122.209 [64149.049747] [tempesta fw] exiting... Apr 26 09:53:18 192.168.122.209 [64149.173768] [tdb] Shutdown Tempesta DB Apr 26 09:53:18 192.168.122.209 [64149.376551] End test: t_http_rules.test_h2_http_rules.TestH2Host.test_host_in_authority_header Apr 26 09:53:18 192.168.122.209 [64149.395836] Start test: t_http_rules.test_h2_http_rules.TestH2Host.test_host_in_forwarded_header Apr 26 09:53:19 192.168.122.209 [64150.488018] [tdb] Start Tempesta DB Apr 26 09:53:20 192.168.122.209 [64150.620612] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:53:21 192.168.122.209 [64152.249129] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64152.249129] Maybe that's fine, but it's worth checking the [64152.249129] config - if there is no relations between the [64152.249129] names, then host name confusion attack is possible. Apr 26 09:53:21 192.168.122.209 [64152.479874] [tempesta fw] Configuration processing is completed. Apr 26 09:53:21 192.168.122.209 [64152.533098] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:53:22 192.168.122.209 [64152.934714] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:53:22 192.168.122.209 [64152.959785] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:53:22 192.168.122.209 [64152.984677] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:53:22 192.168.122.209 [64153.139817] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:53:22 192.168.122.209 [64153.141641] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:53:22 192.168.122.209 [64153.195767] [tempesta fw] Tempesta FW is ready Apr 26 09:53:23 192.168.122.209 [64154.036578] [tdb] Close table 'client0.tdb' Apr 26 09:53:23 192.168.122.209 [64154.234561] [tdb] Close table 'sessions0.tdb' Apr 26 09:53:26 192.168.122.209 [64157.433508] [tdb] Close table 'cache0.tdb' Apr 26 09:53:27 192.168.122.209 [64157.657633] [tdb] Close table 'filter0.tdb' Apr 26 09:53:27 192.168.122.209 [64157.658044] [tempesta fw] modules are stopped Apr 26 09:53:27 192.168.122.209 [64157.919549] [tempesta fw] exiting... Apr 26 09:53:27 192.168.122.209 [64158.039823] [tdb] Shutdown Tempesta DB Apr 26 09:53:27 192.168.122.209 [64158.249557] End test: t_http_rules.test_h2_http_rules.TestH2Host.test_host_in_forwarded_header Apr 26 09:53:27 192.168.122.209 [64158.261686] Start test: t_http_rules.test_h2_http_rules.TestH2Host.test_host_in_host_header Apr 26 09:53:28 192.168.122.209 [64159.307720] [tdb] Start Tempesta DB Apr 26 09:53:28 192.168.122.209 [64159.459776] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:53:30 192.168.122.209 [64161.137289] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64161.137289] Maybe that's fine, but it's worth checking the [64161.137289] config - if there is no relations between the [64161.137289] names, then host name confusion attack is possible. Apr 26 09:53:30 192.168.122.209 [64161.359951] [tempesta fw] Configuration processing is completed. Apr 26 09:53:30 192.168.122.209 [64161.415030] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:53:31 192.168.122.209 [64161.820442] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:53:31 192.168.122.209 [64161.847250] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:53:31 192.168.122.209 [64161.872729] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:53:31 192.168.122.209 [64161.963901] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:53:31 192.168.122.209 [64161.965726] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:53:31 192.168.122.209 [64162.003862] [tempesta fw] Tempesta FW is ready Apr 26 09:53:32 192.168.122.209 [64162.835310] [tdb] Close table 'client0.tdb' Apr 26 09:53:32 192.168.122.209 [64163.022894] [tdb] Close table 'sessions0.tdb' Apr 26 09:53:35 192.168.122.209 [64166.229498] [tdb] Close table 'cache0.tdb' Apr 26 09:53:35 192.168.122.209 [64166.490288] [tdb] Close table 'filter0.tdb' Apr 26 09:53:35 192.168.122.209 [64166.490718] [tempesta fw] modules are stopped Apr 26 09:53:36 192.168.122.209 [64166.726361] [tempesta fw] exiting... Apr 26 09:53:36 192.168.122.209 [64166.867526] [tdb] Shutdown Tempesta DB Apr 26 09:53:36 192.168.122.209 [64167.069121] End test: t_http_rules.test_h2_http_rules.TestH2Host.test_host_in_host_header Apr 26 09:53:36 192.168.122.209 [64167.081543] Start test: t_http_rules.test_h2_http_tables.H2Redirects.test Apr 26 09:53:37 192.168.122.209 [64168.071461] [tdb] Start Tempesta DB Apr 26 09:53:37 192.168.122.209 [64168.217787] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:53:39 192.168.122.209 [64169.821825] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [64169.821825] Maybe that's fine, but it's worth checking the [64169.821825] config - if there is no relations between the [64169.821825] names, then host name confusion attack is possible. Apr 26 09:53:39 192.168.122.209 [64169.912008] [tempesta fw] Configuration processing is completed. Apr 26 09:53:39 192.168.122.209 [64169.969379] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:53:39 192.168.122.209 [64170.378129] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:53:39 192.168.122.209 [64170.403427] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:53:39 192.168.122.209 [64170.428294] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:53:39 192.168.122.209 [64170.476017] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:53:39 192.168.122.209 [64170.519934] [tempesta fw] Tempesta FW is ready Apr 26 09:53:40 192.168.122.209 [64171.126953] [tdb] Close table 'client0.tdb' Apr 26 09:53:40 192.168.122.209 [64171.313979] [tdb] Close table 'sessions0.tdb' Apr 26 09:53:43 192.168.122.209 [64174.506480] [tdb] Close table 'cache0.tdb' Apr 26 09:53:44 192.168.122.209 [64174.750254] [tdb] Close table 'filter0.tdb' Apr 26 09:53:44 192.168.122.209 [64174.750681] [tempesta fw] modules are stopped Apr 26 09:53:44 192.168.122.209 [64174.953374] [tempesta fw] exiting... Apr 26 09:53:44 192.168.122.209 [64175.088998] [tdb] Shutdown Tempesta DB Apr 26 09:53:44 192.168.122.209 [64175.296618] End test: t_http_rules.test_h2_http_tables.H2Redirects.test Apr 26 09:53:44 192.168.122.209 [64175.308374] Start test: t_http_rules.test_h2_http_tables.HttpTablesTestCustomRedirectCorrectVariablesAuthorityH2.test Apr 26 09:53:45 192.168.122.209 [64176.359814] [tdb] Start Tempesta DB Apr 26 09:53:45 192.168.122.209 [64176.498657] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:53:47 192.168.122.209 [64178.201316] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64178.201316] Maybe that's fine, but it's worth checking the [64178.201316] config - if there is no relations between the [64178.201316] names, then host name confusion attack is possible. Apr 26 09:53:47 192.168.122.209 [64178.352010] [tempesta fw] Configuration processing is completed. Apr 26 09:53:47 192.168.122.209 [64178.410858] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:53:48 192.168.122.209 [64178.814633] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:53:48 192.168.122.209 [64178.840053] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:53:48 192.168.122.209 [64178.864758] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:53:48 192.168.122.209 [64178.904086] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:53:48 192.168.122.209 [64178.905809] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:53:48 192.168.122.209 [64178.948028] [tempesta fw] Tempesta FW is ready Apr 26 09:53:48 192.168.122.209 [64179.545965] [tdb] Close table 'client0.tdb' Apr 26 09:53:49 192.168.122.209 [64179.729044] [tdb] Close table 'sessions0.tdb' Apr 26 09:53:52 192.168.122.209 [64182.957882] [tdb] Close table 'cache0.tdb' Apr 26 09:53:52 192.168.122.209 [64183.189198] [tdb] Close table 'filter0.tdb' Apr 26 09:53:52 192.168.122.209 [64183.189603] [tempesta fw] modules are stopped Apr 26 09:53:52 192.168.122.209 [64183.422526] [tempesta fw] exiting... Apr 26 09:53:52 192.168.122.209 [64183.535909] [tdb] Shutdown Tempesta DB Apr 26 09:53:53 192.168.122.209 [64183.749882] End test: t_http_rules.test_h2_http_tables.HttpTablesTestCustomRedirectCorrectVariablesAuthorityH2.test Apr 26 09:53:53 192.168.122.209 [64183.762352] Start test: t_http_rules.test_h2_http_tables.HttpTablesTestCustomRedirectCorrectVariablesHostH2.test Apr 26 09:53:54 192.168.122.209 [64184.847386] [tdb] Start Tempesta DB Apr 26 09:53:54 192.168.122.209 [64184.995479] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:53:56 192.168.122.209 [64186.673446] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64186.673446] Maybe that's fine, but it's worth checking the [64186.673446] config - if there is no relations between the [64186.673446] names, then host name confusion attack is possible. Apr 26 09:53:56 192.168.122.209 [64186.828130] [tempesta fw] Configuration processing is completed. Apr 26 09:53:56 192.168.122.209 [64186.883200] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:53:56 192.168.122.209 [64187.281246] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:53:56 192.168.122.209 [64187.306396] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:53:56 192.168.122.209 [64187.331216] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:53:56 192.168.122.209 [64187.380131] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:53:56 192.168.122.209 [64187.381849] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:53:56 192.168.122.209 [64187.428127] [tempesta fw] Tempesta FW is ready Apr 26 09:53:57 192.168.122.209 [64188.084590] [tdb] Close table 'client0.tdb' Apr 26 09:53:57 192.168.122.209 [64188.255730] [tdb] Close table 'sessions0.tdb' Apr 26 09:54:00 192.168.122.209 [64191.442905] [tdb] Close table 'cache0.tdb' Apr 26 09:54:01 192.168.122.209 [64191.694968] [tdb] Close table 'filter0.tdb' Apr 26 09:54:01 192.168.122.209 [64191.695390] [tempesta fw] modules are stopped Apr 26 09:54:01 192.168.122.209 [64191.892114] [tempesta fw] exiting... Apr 26 09:54:01 192.168.122.209 [64192.039052] [tdb] Shutdown Tempesta DB Apr 26 09:54:01 192.168.122.209 [64192.257615] End test: t_http_rules.test_h2_http_tables.HttpTablesTestCustomRedirectCorrectVariablesHostH2.test Apr 26 09:54:01 192.168.122.209 [64192.271184] Start test: t_http_rules.test_h2_http_tables.HttpTablesTestCustomRedirectDifferentResponseStatusH2.test Apr 26 09:54:02 192.168.122.209 [64193.336540] [tdb] Start Tempesta DB Apr 26 09:54:02 192.168.122.209 [64193.463609] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:54:04 192.168.122.209 [64195.162212] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64195.162212] Maybe that's fine, but it's worth checking the [64195.162212] config - if there is no relations between the [64195.162212] names, then host name confusion attack is possible. Apr 26 09:54:04 192.168.122.209 [64195.308304] [tempesta fw] Configuration processing is completed. Apr 26 09:54:04 192.168.122.209 [64195.360389] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:54:05 192.168.122.209 [64195.759753] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:54:05 192.168.122.209 [64195.784664] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:54:05 192.168.122.209 [64195.809543] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:54:05 192.168.122.209 [64195.876268] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:54:05 192.168.122.209 [64195.877996] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:54:05 192.168.122.209 [64195.920231] [tempesta fw] Tempesta FW is ready Apr 26 09:54:05 192.168.122.209 [64196.545627] [tdb] Close table 'client0.tdb' Apr 26 09:54:06 192.168.122.209 [64196.741876] [tdb] Close table 'sessions0.tdb' Apr 26 09:54:09 192.168.122.209 [64199.895283] [tdb] Close table 'cache0.tdb' Apr 26 09:54:09 192.168.122.209 [64200.141300] [tdb] Close table 'filter0.tdb' Apr 26 09:54:09 192.168.122.209 [64200.141754] [tempesta fw] modules are stopped Apr 26 09:54:09 192.168.122.209 [64200.315051] [tempesta fw] exiting... Apr 26 09:54:09 192.168.122.209 [64200.455659] [tdb] Shutdown Tempesta DB Apr 26 09:54:10 192.168.122.209 [64200.688458] End test: t_http_rules.test_h2_http_tables.HttpTablesTestCustomRedirectDifferentResponseStatusH2.test Apr 26 09:54:10 192.168.122.209 [64200.707980] Start test: t_http_rules.test_h2_http_tables.HttpTablesTestCustomRedirectNonExistentVariablesH2.test Apr 26 09:54:11 192.168.122.209 [64201.784930] [tdb] Start Tempesta DB Apr 26 09:54:11 192.168.122.209 [64201.916836] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:54:13 192.168.122.209 [64203.641632] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64203.641632] Maybe that's fine, but it's worth checking the [64203.641632] config - if there is no relations between the [64203.641632] names, then host name confusion attack is possible. Apr 26 09:54:13 192.168.122.209 [64203.788346] [tempesta fw] Configuration processing is completed. Apr 26 09:54:13 192.168.122.209 [64203.842770] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:54:13 192.168.122.209 [64204.251865] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:54:13 192.168.122.209 [64204.277278] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:54:13 192.168.122.209 [64204.304220] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:54:13 192.168.122.209 [64204.364368] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:54:13 192.168.122.209 [64204.366092] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:54:13 192.168.122.209 [64204.436379] [tempesta fw] Tempesta FW is ready Apr 26 09:54:14 192.168.122.209 [64205.054253] [tdb] Close table 'client0.tdb' Apr 26 09:54:14 192.168.122.209 [64205.241445] [tdb] Close table 'sessions0.tdb' Apr 26 09:54:17 192.168.122.209 [64208.401665] [tdb] Close table 'cache0.tdb' Apr 26 09:54:18 192.168.122.209 [64208.651859] [tdb] Close table 'filter0.tdb' Apr 26 09:54:18 192.168.122.209 [64208.652299] [tempesta fw] modules are stopped Apr 26 09:54:18 192.168.122.209 [64208.845860] [tempesta fw] exiting... Apr 26 09:54:18 192.168.122.209 [64208.967674] [tdb] Shutdown Tempesta DB Apr 26 09:54:18 192.168.122.209 [64209.165177] End test: t_http_rules.test_h2_http_tables.HttpTablesTestCustomRedirectNonExistentVariablesH2.test Apr 26 09:54:18 192.168.122.209 [64209.194320] Start test: t_http_rules.test_h2_http_tables.HttpTablesTestEmptyChainDefaultH2.test Apr 26 09:54:19 192.168.122.209 [64210.299437] [tdb] Start Tempesta DB Apr 26 09:54:19 192.168.122.209 [64210.437250] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:54:21 192.168.122.209 [64211.994018] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64211.994018] Maybe that's fine, but it's worth checking the [64211.994018] config - if there is no relations between the [64211.994018] names, then host name confusion attack is possible. Apr 26 09:54:21 192.168.122.209 [64212.148447] [tempesta fw] Configuration processing is completed. Apr 26 09:54:21 192.168.122.209 [64212.204224] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:54:21 192.168.122.209 [64212.606865] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:54:22 192.168.122.209 [64212.632443] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:54:22 192.168.122.209 [64212.662279] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:54:22 192.168.122.209 [64212.704463] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:54:22 192.168.122.209 [64212.706180] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:54:22 192.168.122.209 [64212.748416] [tempesta fw] Tempesta FW is ready Apr 26 09:54:22 192.168.122.209 [64212.937285] [tempesta fw] Warning: request dropped: cannot find appropriate virtual host, status 403: 127.0.0.2 Apr 26 09:54:22 192.168.122.209 [64213.370710] [tdb] Close table 'client0.tdb' Apr 26 09:54:22 192.168.122.209 [64213.565080] [tdb] Close table 'sessions0.tdb' Apr 26 09:54:26 192.168.122.209 [64216.747410] [tdb] Close table 'cache0.tdb' Apr 26 09:54:26 192.168.122.209 [64216.997678] [tdb] Close table 'filter0.tdb' Apr 26 09:54:26 192.168.122.209 [64216.998111] [tempesta fw] modules are stopped Apr 26 09:54:26 192.168.122.209 [64217.207151] [tempesta fw] exiting... Apr 26 09:54:26 192.168.122.209 [64217.375408] [tdb] Shutdown Tempesta DB Apr 26 09:54:26 192.168.122.209 [64217.589111] End test: t_http_rules.test_h2_http_tables.HttpTablesTestEmptyChainDefaultH2.test Apr 26 09:54:26 192.168.122.209 [64217.602886] Start test: t_http_rules.test_h2_http_tables.HttpTablesTestEmptyChainDropH2.test Apr 26 09:54:27 192.168.122.209 [64218.559352] [tdb] Start Tempesta DB Apr 26 09:54:28 192.168.122.209 [64218.703623] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:54:29 192.168.122.209 [64220.369869] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64220.369869] Maybe that's fine, but it's worth checking the [64220.369869] config - if there is no relations between the [64220.369869] names, then host name confusion attack is possible. Apr 26 09:54:29 192.168.122.209 [64220.516544] [tempesta fw] Configuration processing is completed. Apr 26 09:54:29 192.168.122.209 [64220.573863] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:54:30 192.168.122.209 [64220.985897] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:54:30 192.168.122.209 [64221.011649] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:54:30 192.168.122.209 [64221.037218] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:54:30 192.168.122.209 [64221.092574] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:54:30 192.168.122.209 [64221.094336] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:54:30 192.168.122.209 [64221.152458] [tempesta fw] Tempesta FW is ready Apr 26 09:54:30 192.168.122.209 [64221.312712] [tempesta fw] Warning: request dropped: cannot find appropriate virtual host, status 403: 127.0.0.2 Apr 26 09:54:31 192.168.122.209 [64221.716623] [tdb] Close table 'client0.tdb' Apr 26 09:54:31 192.168.122.209 [64221.928111] [tdb] Close table 'sessions0.tdb' Apr 26 09:54:34 192.168.122.209 [64225.096122] [tdb] Close table 'cache0.tdb' Apr 26 09:54:34 192.168.122.209 [64225.345994] [tdb] Close table 'filter0.tdb' Apr 26 09:54:34 192.168.122.209 [64225.346428] [tempesta fw] modules are stopped Apr 26 09:54:34 192.168.122.209 [64225.590179] [tempesta fw] exiting... Apr 26 09:54:35 192.168.122.209 [64225.729411] [tdb] Shutdown Tempesta DB Apr 26 09:54:35 192.168.122.209 [64225.961255] End test: t_http_rules.test_h2_http_tables.HttpTablesTestEmptyChainDropH2.test Apr 26 09:54:35 192.168.122.209 [64225.985548] Start test: t_http_rules.test_h2_http_tables.HttpTablesTestEmptyChainReplyH2.test Apr 26 09:54:36 192.168.122.209 [64227.113974] [tdb] Start Tempesta DB Apr 26 09:54:36 192.168.122.209 [64227.244659] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:54:38 192.168.122.209 [64228.965936] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64228.965936] Maybe that's fine, but it's worth checking the [64228.965936] config - if there is no relations between the [64228.965936] names, then host name confusion attack is possible. Apr 26 09:54:38 192.168.122.209 [64229.132559] [tempesta fw] Configuration processing is completed. Apr 26 09:54:38 192.168.122.209 [64229.187790] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:54:38 192.168.122.209 [64229.592678] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:54:39 192.168.122.209 [64229.617923] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:54:39 192.168.122.209 [64229.643013] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:54:39 192.168.122.209 [64229.688643] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:54:39 192.168.122.209 [64229.690240] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:54:39 192.168.122.209 [64229.728615] [tempesta fw] Tempesta FW is ready Apr 26 09:54:39 192.168.122.209 [64229.913323] [tempesta fw] Warning: request dropped: cannot find appropriate virtual host, status 403: 127.0.0.2 Apr 26 09:54:39 192.168.122.209 [64230.334643] [tdb] Close table 'client0.tdb' Apr 26 09:54:39 192.168.122.209 [64230.509126] [tdb] Close table 'sessions0.tdb' Apr 26 09:54:43 192.168.122.209 [64233.651899] [tdb] Close table 'cache0.tdb' Apr 26 09:54:43 192.168.122.209 [64233.902957] [tdb] Close table 'filter0.tdb' Apr 26 09:54:43 192.168.122.209 [64233.903391] [tempesta fw] modules are stopped Apr 26 09:54:43 192.168.122.209 [64234.107194] [tempesta fw] exiting... Apr 26 09:54:43 192.168.122.209 [64234.239172] [tdb] Shutdown Tempesta DB Apr 26 09:54:43 192.168.122.209 [64234.451622] End test: t_http_rules.test_h2_http_tables.HttpTablesTestEmptyChainReplyH2.test Apr 26 09:54:43 192.168.122.209 [64234.480585] Start test: t_http_rules.test_h2_http_tables.HttpTablesTestEmptyMainChainDefaultH2.test Apr 26 09:54:44 192.168.122.209 [64235.474066] [tdb] Start Tempesta DB Apr 26 09:54:45 192.168.122.209 [64235.619055] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:54:46 192.168.122.209 [64237.158098] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64237.158098] Maybe that's fine, but it's worth checking the [64237.158098] config - if there is no relations between the [64237.158098] names, then host name confusion attack is possible. Apr 26 09:54:46 192.168.122.209 [64237.296741] [tempesta fw] Configuration processing is completed. Apr 26 09:54:46 192.168.122.209 [64237.348785] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:54:47 192.168.122.209 [64237.741485] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:54:47 192.168.122.209 [64237.766407] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:54:47 192.168.122.209 [64237.790549] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:54:47 192.168.122.209 [64237.828701] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:54:47 192.168.122.209 [64237.830414] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:54:47 192.168.122.209 [64237.868697] [tempesta fw] Tempesta FW is ready Apr 26 09:54:47 192.168.122.209 [64238.071695] [tempesta fw] Warning: request dropped: cannot find appropriate virtual host, status 403: 127.0.0.2 Apr 26 09:54:47 192.168.122.209 [64238.488049] [tdb] Close table 'client0.tdb' Apr 26 09:54:48 192.168.122.209 [64238.677087] [tdb] Close table 'sessions0.tdb' Apr 26 09:54:51 192.168.122.209 [64241.826362] [tdb] Close table 'cache0.tdb' Apr 26 09:54:51 192.168.122.209 [64242.071219] [tdb] Close table 'filter0.tdb' Apr 26 09:54:51 192.168.122.209 [64242.071642] [tempesta fw] modules are stopped Apr 26 09:54:51 192.168.122.209 [64242.283672] [tempesta fw] exiting... Apr 26 09:54:51 192.168.122.209 [64242.399982] [tdb] Shutdown Tempesta DB Apr 26 09:54:52 192.168.122.209 [64242.628231] End test: t_http_rules.test_h2_http_tables.HttpTablesTestEmptyMainChainDefaultH2.test Apr 26 09:54:52 192.168.122.209 [64242.640011] Start test: t_http_rules.test_h2_http_tables.HttpTablesTestEmptyMainChainDropH2.test Apr 26 09:54:53 192.168.122.209 [64243.680414] [tdb] Start Tempesta DB Apr 26 09:54:53 192.168.122.209 [64243.821999] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:54:54 192.168.122.209 [64245.382128] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64245.382128] Maybe that's fine, but it's worth checking the [64245.382128] config - if there is no relations between the [64245.382128] names, then host name confusion attack is possible. Apr 26 09:54:54 192.168.122.209 [64245.540845] [tempesta fw] Configuration processing is completed. Apr 26 09:54:54 192.168.122.209 [64245.592762] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:54:55 192.168.122.209 [64245.993646] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:54:55 192.168.122.209 [64246.018718] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:54:55 192.168.122.209 [64246.043665] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:54:55 192.168.122.209 [64246.088849] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:54:55 192.168.122.209 [64246.090605] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:54:55 192.168.122.209 [64246.128836] [tempesta fw] Tempesta FW is ready Apr 26 09:54:55 192.168.122.209 [64246.331539] [tempesta fw] Warning: request dropped: cannot find appropriate virtual host, status 403: 127.0.0.2 Apr 26 09:54:56 192.168.122.209 [64246.750428] [tdb] Close table 'client0.tdb' Apr 26 09:54:56 192.168.122.209 [64246.937771] [tdb] Close table 'sessions0.tdb' Apr 26 09:54:59 192.168.122.209 [64250.130669] [tdb] Close table 'cache0.tdb' Apr 26 09:54:59 192.168.122.209 [64250.395021] [tdb] Close table 'filter0.tdb' Apr 26 09:54:59 192.168.122.209 [64250.395439] [tempesta fw] modules are stopped Apr 26 09:55:00 192.168.122.209 [64250.632605] [tempesta fw] exiting... Apr 26 09:55:00 192.168.122.209 [64250.763073] [tdb] Shutdown Tempesta DB Apr 26 09:55:00 192.168.122.209 [64250.974816] End test: t_http_rules.test_h2_http_tables.HttpTablesTestEmptyMainChainDropH2.test Apr 26 09:55:00 192.168.122.209 [64250.988746] Start test: t_http_rules.test_h2_http_tables.HttpTablesTestEmptyMainChainReplyH2.test Apr 26 09:55:01 192.168.122.209 [64252.047173] [tdb] Start Tempesta DB Apr 26 09:55:01 192.168.122.209 [64252.180835] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:55:03 192.168.122.209 [64253.822311] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64253.822311] Maybe that's fine, but it's worth checking the [64253.822311] config - if there is no relations between the [64253.822311] names, then host name confusion attack is possible. Apr 26 09:55:03 192.168.122.209 [64253.968920] [tempesta fw] Configuration processing is completed. Apr 26 09:55:03 192.168.122.209 [64254.018785] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:55:03 192.168.122.209 [64254.415651] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:55:03 192.168.122.209 [64254.441256] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:55:03 192.168.122.209 [64254.468028] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:55:03 192.168.122.209 [64254.544951] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:55:03 192.168.122.209 [64254.546708] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:55:03 192.168.122.209 [64254.588896] [tempesta fw] Tempesta FW is ready Apr 26 09:55:04 192.168.122.209 [64254.781875] [tempesta fw] Warning: request dropped: cannot find appropriate virtual host, status 403: 127.0.0.2 Apr 26 09:55:04 192.168.122.209 [64255.209387] [tdb] Close table 'client0.tdb' Apr 26 09:55:04 192.168.122.209 [64255.391580] [tdb] Close table 'sessions0.tdb' Apr 26 09:55:07 192.168.122.209 [64258.583076] [tdb] Close table 'cache0.tdb' Apr 26 09:55:08 192.168.122.209 [64258.833168] [tdb] Close table 'filter0.tdb' Apr 26 09:55:08 192.168.122.209 [64258.833619] [tempesta fw] modules are stopped Apr 26 09:55:08 192.168.122.209 [64259.021362] [tempesta fw] exiting... Apr 26 09:55:08 192.168.122.209 [64259.157806] [tdb] Shutdown Tempesta DB Apr 26 09:55:08 192.168.122.209 [64259.377662] End test: t_http_rules.test_h2_http_tables.HttpTablesTestEmptyMainChainReplyH2.test Apr 26 09:55:08 192.168.122.209 [64259.390281] Start test: t_http_rules.test_h2_http_tables.HttpTablesTestMarkRuleH2.test_reject_by_mark_disable_tso_gro_gso Apr 26 09:55:09 192.168.122.209 [64260.409288] [tdb] Start Tempesta DB Apr 26 09:55:09 192.168.122.209 [64260.535149] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:55:11 192.168.122.209 [64262.194333] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64262.194333] Maybe that's fine, but it's worth checking the [64262.194333] config - if there is no relations between the [64262.194333] names, then host name confusion attack is possible. Apr 26 09:55:11 192.168.122.209 [64262.360996] [tempesta fw] Configuration processing is completed. Apr 26 09:55:11 192.168.122.209 [64262.414487] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:55:12 192.168.122.209 [64262.819193] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:55:12 192.168.122.209 [64262.845108] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:55:12 192.168.122.209 [64262.870354] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:55:12 192.168.122.209 [64262.913058] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:55:12 192.168.122.209 [64262.914800] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:55:12 192.168.122.209 [64262.953009] [tempesta fw] Tempesta FW is ready Apr 26 09:55:16 192.168.122.209 [64266.945036] [tdb] Close table 'client0.tdb' Apr 26 09:55:16 192.168.122.209 [64267.148137] [tdb] Close table 'sessions0.tdb' Apr 26 09:55:19 192.168.122.209 [64270.310311] [tdb] Close table 'cache0.tdb' Apr 26 09:55:19 192.168.122.209 [64270.532475] [tdb] Close table 'filter0.tdb' Apr 26 09:55:19 192.168.122.209 [64270.532895] [tempesta fw] modules are stopped Apr 26 09:55:20 192.168.122.209 [64270.748667] [tempesta fw] exiting... Apr 26 09:55:20 192.168.122.209 [64270.872244] [tdb] Shutdown Tempesta DB Apr 26 09:55:20 192.168.122.209 [64271.095564] End test: t_http_rules.test_h2_http_tables.HttpTablesTestMarkRuleH2.test_reject_by_mark_disable_tso_gro_gso Apr 26 09:55:20 192.168.122.209 [64271.120041] Start test: t_http_rules.test_h2_http_tables.HttpTablesTestMarkRuleH2.test_reject_by_mark_enable_tso_gro_gso Apr 26 09:55:21 192.168.122.209 [64272.131415] [tdb] Start Tempesta DB Apr 26 09:55:21 192.168.122.209 [64272.270054] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:55:23 192.168.122.209 [64273.826436] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64273.826436] Maybe that's fine, but it's worth checking the [64273.826436] config - if there is no relations between the [64273.826436] names, then host name confusion attack is possible. Apr 26 09:55:23 192.168.122.209 [64273.981153] [tempesta fw] Configuration processing is completed. Apr 26 09:55:23 192.168.122.209 [64274.033617] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:55:23 192.168.122.209 [64274.444228] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:55:23 192.168.122.209 [64274.470391] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:55:23 192.168.122.209 [64274.497340] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:55:23 192.168.122.209 [64274.561195] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:55:23 192.168.122.209 [64274.562927] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:55:23 192.168.122.209 [64274.601153] [tempesta fw] Tempesta FW is ready Apr 26 09:55:27 192.168.122.209 [64278.568893] [tdb] Close table 'client0.tdb' Apr 26 09:55:28 192.168.122.209 [64278.753075] [tdb] Close table 'sessions0.tdb' Apr 26 09:55:31 192.168.122.209 [64281.980750] [tdb] Close table 'cache0.tdb' Apr 26 09:55:31 192.168.122.209 [64282.213717] [tdb] Close table 'filter0.tdb' Apr 26 09:55:31 192.168.122.209 [64282.214144] [tempesta fw] modules are stopped Apr 26 09:55:31 192.168.122.209 [64282.405317] [tempesta fw] exiting... Apr 26 09:55:31 192.168.122.209 [64282.528143] [tdb] Shutdown Tempesta DB Apr 26 09:55:32 192.168.122.209 [64282.740149] End test: t_http_rules.test_h2_http_tables.HttpTablesTestMarkRuleH2.test_reject_by_mark_enable_tso_gro_gso Apr 26 09:55:32 192.168.122.209 [64282.753033] Start test: t_http_rules.test_h2_http_tables.HttpTablesTestMarkRulesH2.test_chains Apr 26 09:55:33 192.168.122.209 [64283.797908] [tdb] Start Tempesta DB Apr 26 09:55:33 192.168.122.209 [64283.954676] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:55:36 192.168.122.209 [64287.058846] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64287.058846] Maybe that's fine, but it's worth checking the [64287.058846] config - if there is no relations between the [64287.058846] names, then host name confusion attack is possible. Apr 26 09:55:36 192.168.122.209 [64287.549362] [tempesta fw] Configuration processing is completed. Apr 26 09:55:36 192.168.122.209 [64287.608413] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:55:37 192.168.122.209 [64288.080203] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:55:37 192.168.122.209 [64288.115209] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:55:37 192.168.122.209 [64288.143673] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:55:37 192.168.122.209 [64288.373405] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:55:37 192.168.122.209 [64288.375254] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:55:37 192.168.122.209 [64288.409319] [tempesta fw] Tempesta FW is ready Apr 26 09:55:40 192.168.122.209 [64290.939247] [tdb] Close table 'client0.tdb' Apr 26 09:55:40 192.168.122.209 [64291.120257] [tdb] Close table 'sessions0.tdb' Apr 26 09:55:43 192.168.122.209 [64294.328899] [tdb] Close table 'cache0.tdb' Apr 26 09:55:43 192.168.122.209 [64294.569157] [tdb] Close table 'filter0.tdb' Apr 26 09:55:43 192.168.122.209 [64294.569611] [tempesta fw] modules are stopped Apr 26 09:55:44 192.168.122.209 [64294.959221] [tempesta fw] exiting... Apr 26 09:55:44 192.168.122.209 [64295.075927] [tdb] Shutdown Tempesta DB Apr 26 09:55:44 192.168.122.209 [64295.299854] End test: t_http_rules.test_h2_http_tables.HttpTablesTestMarkRulesH2.test_chains Apr 26 09:55:44 192.168.122.209 [64295.312252] Start test: t_http_rules.test_h2_http_tables.HttpTablesTestMixedChainDefaultH2.test Apr 26 09:55:45 192.168.122.209 [64296.378968] [tdb] Start Tempesta DB Apr 26 09:55:45 192.168.122.209 [64296.529873] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:55:47 192.168.122.209 [64298.218816] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64298.218816] Maybe that's fine, but it's worth checking the [64298.218816] config - if there is no relations between the [64298.218816] names, then host name confusion attack is possible. Apr 26 09:55:47 192.168.122.209 [64298.369740] [tempesta fw] Configuration processing is completed. Apr 26 09:55:47 192.168.122.209 [64298.427617] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:55:48 192.168.122.209 [64298.903107] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:55:48 192.168.122.209 [64298.934131] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:55:48 192.168.122.209 [64298.964714] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:55:48 192.168.122.209 [64299.005482] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:55:48 192.168.122.209 [64299.007262] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:55:48 192.168.122.209 [64299.053422] [tempesta fw] Tempesta FW is ready Apr 26 09:55:48 192.168.122.209 [64299.245577] [tempesta fw] Warning: request dropped: cannot find appropriate virtual host, status 403: 127.0.0.2 Apr 26 09:55:49 192.168.122.209 [64299.645609] [tdb] Close table 'client0.tdb' Apr 26 09:55:49 192.168.122.209 [64299.847413] [tdb] Close table 'sessions0.tdb' Apr 26 09:55:52 192.168.122.209 [64303.032609] [tdb] Close table 'cache0.tdb' Apr 26 09:55:52 192.168.122.209 [64303.316556] [tdb] Close table 'filter0.tdb' Apr 26 09:55:52 192.168.122.209 [64303.317007] [tempesta fw] modules are stopped Apr 26 09:55:52 192.168.122.209 [64303.536178] [tempesta fw] exiting... Apr 26 09:55:53 192.168.122.209 [64303.670847] [tdb] Shutdown Tempesta DB Apr 26 09:55:53 192.168.122.209 [64303.854191] End test: t_http_rules.test_h2_http_tables.HttpTablesTestMixedChainDefaultH2.test Apr 26 09:55:53 192.168.122.209 [64303.865357] Start test: t_http_rules.test_h2_http_tables.HttpTablesTestMixedChainDropH2.test Apr 26 09:55:54 192.168.122.209 [64304.914459] [tdb] Start Tempesta DB Apr 26 09:55:54 192.168.122.209 [64305.052480] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:55:56 192.168.122.209 [64306.746792] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64306.746792] Maybe that's fine, but it's worth checking the [64306.746792] config - if there is no relations between the [64306.746792] names, then host name confusion attack is possible. Apr 26 09:55:56 192.168.122.209 [64306.893523] [tempesta fw] Configuration processing is completed. Apr 26 09:55:56 192.168.122.209 [64306.944430] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:55:56 192.168.122.209 [64307.344557] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:55:56 192.168.122.209 [64307.369794] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:55:56 192.168.122.209 [64307.396900] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:55:56 192.168.122.209 [64307.453556] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:55:56 192.168.122.209 [64307.455340] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:55:56 192.168.122.209 [64307.493601] [tempesta fw] Tempesta FW is ready Apr 26 09:55:57 192.168.122.209 [64307.700261] [tempesta fw] Warning: request dropped: cannot find appropriate virtual host, status 403: 127.0.0.2 Apr 26 09:55:57 192.168.122.209 [64308.143801] [tdb] Close table 'client0.tdb' Apr 26 09:55:57 192.168.122.209 [64308.346148] [tdb] Close table 'sessions0.tdb' Apr 26 09:56:00 192.168.122.209 [64311.587250] [tdb] Close table 'cache0.tdb' Apr 26 09:56:01 192.168.122.209 [64311.857815] [tdb] Close table 'filter0.tdb' Apr 26 09:56:01 192.168.122.209 [64311.858262] [tempesta fw] modules are stopped Apr 26 09:56:01 192.168.122.209 [64312.083169] [tempesta fw] exiting... Apr 26 09:56:01 192.168.122.209 [64312.186681] [tdb] Shutdown Tempesta DB Apr 26 09:56:01 192.168.122.209 [64312.452421] End test: t_http_rules.test_h2_http_tables.HttpTablesTestMixedChainDropH2.test Apr 26 09:56:01 192.168.122.209 [64312.473905] Start test: t_http_rules.test_h2_http_tables.HttpTablesTestMixedChainReplyH2.test Apr 26 09:56:02 192.168.122.209 [64313.518398] [tdb] Start Tempesta DB Apr 26 09:56:03 192.168.122.209 [64313.669663] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:56:04 192.168.122.209 [64315.406898] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64315.406898] Maybe that's fine, but it's worth checking the [64315.406898] config - if there is no relations between the [64315.406898] names, then host name confusion attack is possible. Apr 26 09:56:04 192.168.122.209 [64315.561967] [tempesta fw] Configuration processing is completed. Apr 26 09:56:04 192.168.122.209 [64315.612411] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:56:05 192.168.122.209 [64316.022086] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:56:05 192.168.122.209 [64316.049496] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:56:05 192.168.122.209 [64316.076546] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:56:05 192.168.122.209 [64316.129668] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:56:05 192.168.122.209 [64316.131173] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:56:05 192.168.122.209 [64316.169636] [tempesta fw] Tempesta FW is ready Apr 26 09:56:05 192.168.122.209 [64316.368416] [tempesta fw] Warning: request dropped: cannot find appropriate virtual host, status 403: 127.0.0.2 Apr 26 09:56:06 192.168.122.209 [64316.835260] [tdb] Close table 'client0.tdb' Apr 26 09:56:06 192.168.122.209 [64317.022408] [tdb] Close table 'sessions0.tdb' Apr 26 09:56:09 192.168.122.209 [64320.294623] [tdb] Close table 'cache0.tdb' Apr 26 09:56:09 192.168.122.209 [64320.581725] [tdb] Close table 'filter0.tdb' Apr 26 09:56:09 192.168.122.209 [64320.582146] [tempesta fw] modules are stopped Apr 26 09:56:10 192.168.122.209 [64320.791438] [tempesta fw] exiting... Apr 26 09:56:10 192.168.122.209 [64320.959175] [tdb] Shutdown Tempesta DB Apr 26 09:56:10 192.168.122.209 [64321.186557] End test: t_http_rules.test_h2_http_tables.HttpTablesTestMixedChainReplyH2.test Apr 26 09:56:10 192.168.122.209 [64321.201252] Start test: t_http_rules.test_h2_http_tables.HttpTablesTestMixedChainRespH2.test Apr 26 09:56:11 192.168.122.209 [64322.277516] [tdb] Start Tempesta DB Apr 26 09:56:11 192.168.122.209 [64322.416185] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:56:13 192.168.122.209 [64324.159162] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64324.159162] Maybe that's fine, but it's worth checking the [64324.159162] config - if there is no relations between the [64324.159162] names, then host name confusion attack is possible. Apr 26 09:56:13 192.168.122.209 [64324.309773] [tempesta fw] Configuration processing is completed. Apr 26 09:56:13 192.168.122.209 [64324.366251] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:56:14 192.168.122.209 [64324.772048] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:56:14 192.168.122.209 [64324.798646] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:56:14 192.168.122.209 [64324.824098] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:56:14 192.168.122.209 [64324.877793] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:56:14 192.168.122.209 [64324.879530] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:56:14 192.168.122.209 [64324.925722] [tempesta fw] Tempesta FW is ready Apr 26 09:56:14 192.168.122.209 [64325.531255] [tdb] Close table 'client0.tdb' Apr 26 09:56:15 192.168.122.209 [64325.720002] [tdb] Close table 'sessions0.tdb' Apr 26 09:56:18 192.168.122.209 [64329.038974] [tdb] Close table 'cache0.tdb' Apr 26 09:56:18 192.168.122.209 [64329.299401] [tdb] Close table 'filter0.tdb' Apr 26 09:56:18 192.168.122.209 [64329.299855] [tempesta fw] modules are stopped Apr 26 09:56:18 192.168.122.209 [64329.529555] [tempesta fw] exiting... Apr 26 09:56:19 192.168.122.209 [64329.677658] [tdb] Shutdown Tempesta DB Apr 26 09:56:19 192.168.122.209 [64329.909578] End test: t_http_rules.test_h2_http_tables.HttpTablesTestMixedChainRespH2.test Apr 26 09:56:19 192.168.122.209 [64329.919234] Start test: t_http_rules.test_h2_http_tables.TestHttpTablesH2.test_chains Apr 26 09:56:20 192.168.122.209 [64330.962461] [tdb] Start Tempesta DB Apr 26 09:56:20 192.168.122.209 [64331.113187] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:56:23 192.168.122.209 [64334.247281] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64334.247281] Maybe that's fine, but it's worth checking the [64334.247281] config - if there is no relations between the [64334.247281] names, then host name confusion attack is possible. Apr 26 09:56:24 192.168.122.209 [64334.781958] [tempesta fw] Configuration processing is completed. Apr 26 09:56:24 192.168.122.209 [64334.837065] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:56:24 192.168.122.209 [64335.264940] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:56:24 192.168.122.209 [64335.291147] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:56:24 192.168.122.209 [64335.317278] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:56:24 192.168.122.209 [64335.537945] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:56:24 192.168.122.209 [64335.539864] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:56:24 192.168.122.209 [64335.577848] [tempesta fw] Tempesta FW is ready Apr 26 09:56:25 192.168.122.209 [64336.298818] [tempesta fw] Warning: request has been filtered out via http table: 127.0.0.2 Apr 26 09:56:25 192.168.122.209 [64336.397361] [tempesta fw] Warning: request has been filtered out via http table: 127.0.0.2 Apr 26 09:56:26 192.168.122.209 [64337.506172] [tdb] Close table 'client0.tdb' Apr 26 09:56:27 192.168.122.209 [64337.687030] [tdb] Close table 'sessions0.tdb' Apr 26 09:56:30 192.168.122.209 [64340.883647] [tdb] Close table 'cache0.tdb' Apr 26 09:56:30 192.168.122.209 [64341.141354] [tdb] Close table 'filter0.tdb' Apr 26 09:56:30 192.168.122.209 [64341.141918] [tempesta fw] modules are stopped Apr 26 09:56:30 192.168.122.209 [64341.501218] [tempesta fw] exiting... Apr 26 09:56:31 192.168.122.209 [64341.646157] [tdb] Shutdown Tempesta DB Apr 26 09:56:31 192.168.122.209 [64341.851634] End test: t_http_rules.test_h2_http_tables.TestHttpTablesH2.test_chains Apr 26 09:56:31 192.168.122.209 [64341.867489] Start test: t_http_rules.test_h2_match_duplicated_headers.DuplicatedHeadersMatchH2Test.test_match_fail Apr 26 09:56:32 192.168.122.209 [64342.901984] [tdb] Start Tempesta DB Apr 26 09:56:32 192.168.122.209 [64343.037005] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:56:33 192.168.122.209 [64344.607273] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64344.607273] Maybe that's fine, but it's worth checking the [64344.607273] config - if there is no relations between the [64344.607273] names, then host name confusion attack is possible. Apr 26 09:56:34 192.168.122.209 [64344.790071] [tempesta fw] Configuration processing is completed. Apr 26 09:56:34 192.168.122.209 [64344.855267] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:56:34 192.168.122.209 [64345.271809] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:56:34 192.168.122.209 [64345.297113] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:56:34 192.168.122.209 [64345.323110] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:56:34 192.168.122.209 [64345.369999] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:56:34 192.168.122.209 [64345.371758] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:56:34 192.168.122.209 [64345.413945] [tempesta fw] Tempesta FW is ready Apr 26 09:56:35 192.168.122.209 [64345.613821] [tempesta fw] Warning: request has been filtered out via http table: 127.0.0.2 Apr 26 09:56:35 192.168.122.209 [64346.029775] [tdb] Close table 'client0.tdb' Apr 26 09:56:35 192.168.122.209 [64346.215104] [tdb] Close table 'sessions0.tdb' Apr 26 09:56:39 192.168.122.209 [64350.361106] [tdb] Close table 'cache0.tdb' Apr 26 09:56:40 192.168.122.209 [64351.219620] [tdb] Close table 'filter0.tdb' Apr 26 09:56:40 192.168.122.209 [64351.220061] [tempesta fw] modules are stopped Apr 26 09:56:43 192.168.122.209 [64353.685935] [tempesta fw] exiting... Apr 26 09:56:43 192.168.122.209 [64353.802174] [tdb] Shutdown Tempesta DB Apr 26 09:56:43 192.168.122.209 [64353.975867] End test: t_http_rules.test_h2_match_duplicated_headers.DuplicatedHeadersMatchH2Test.test_match_fail Apr 26 09:56:43 192.168.122.209 [64353.993469] Start test: t_http_rules.test_h2_match_duplicated_headers.DuplicatedHeadersMatchH2Test.test_match_success Apr 26 09:56:44 192.168.122.209 [64355.027544] [tdb] Start Tempesta DB Apr 26 09:56:44 192.168.122.209 [64355.164774] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:56:46 192.168.122.209 [64356.659587] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64356.659587] Maybe that's fine, but it's worth checking the [64356.659587] config - if there is no relations between the [64356.659587] names, then host name confusion attack is possible. Apr 26 09:56:46 192.168.122.209 [64356.818193] [tempesta fw] Configuration processing is completed. Apr 26 09:56:46 192.168.122.209 [64356.874110] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:56:46 192.168.122.209 [64357.291208] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:56:46 192.168.122.209 [64357.317389] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:56:46 192.168.122.209 [64357.342972] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:56:46 192.168.122.209 [64357.414157] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:56:46 192.168.122.209 [64357.415908] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:56:46 192.168.122.209 [64357.462102] [tempesta fw] Tempesta FW is ready Apr 26 09:56:47 192.168.122.209 [64358.101394] [tdb] Close table 'client0.tdb' Apr 26 09:56:47 192.168.122.209 [64358.286174] [tdb] Close table 'sessions0.tdb' Apr 26 09:56:50 192.168.122.209 [64361.427157] [tdb] Close table 'cache0.tdb' Apr 26 09:56:51 192.168.122.209 [64361.673071] [tdb] Close table 'filter0.tdb' Apr 26 09:56:51 192.168.122.209 [64361.673484] [tempesta fw] modules are stopped Apr 26 09:56:51 192.168.122.209 [64361.867393] [tempesta fw] exiting... Apr 26 09:56:51 192.168.122.209 [64362.021125] [tdb] Shutdown Tempesta DB Apr 26 09:56:51 192.168.122.209 [64362.208954] End test: t_http_rules.test_h2_match_duplicated_headers.DuplicatedHeadersMatchH2Test.test_match_success Apr 26 09:56:51 192.168.122.209 [64362.220646] Start test: t_http_rules.test_http_rules.TestHost.test_different_host_in_uri_and_host_header Apr 26 09:56:52 192.168.122.209 [64363.270798] [tdb] Start Tempesta DB Apr 26 09:56:52 192.168.122.209 [64363.398240] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:56:54 192.168.122.209 [64364.999550] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64364.999550] Maybe that's fine, but it's worth checking the [64364.999550] config - if there is no relations between the [64364.999550] names, then host name confusion attack is possible. Apr 26 09:56:54 192.168.122.209 [64365.250306] [tempesta fw] Configuration processing is completed. Apr 26 09:56:54 192.168.122.209 [64365.305140] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:56:55 192.168.122.209 [64365.705670] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:56:55 192.168.122.209 [64365.731123] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:56:55 192.168.122.209 [64365.757231] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:56:55 192.168.122.209 [64365.858262] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:56:55 192.168.122.209 [64365.860047] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:56:55 192.168.122.209 [64365.906208] [tempesta fw] Tempesta FW is ready Apr 26 09:56:56 192.168.122.209 [64366.664252] [tdb] Close table 'client0.tdb' Apr 26 09:56:56 192.168.122.209 [64366.849608] [tdb] Close table 'sessions0.tdb' Apr 26 09:56:59 192.168.122.209 [64370.000246] [tdb] Close table 'cache0.tdb' Apr 26 09:56:59 192.168.122.209 [64370.242892] [tdb] Close table 'filter0.tdb' Apr 26 09:56:59 192.168.122.209 [64370.243317] [tempesta fw] modules are stopped Apr 26 09:56:59 192.168.122.209 [64370.520026] [tempesta fw] exiting... Apr 26 09:57:00 192.168.122.209 [64370.649235] [tdb] Shutdown Tempesta DB Apr 26 09:57:00 192.168.122.209 [64370.828867] End test: t_http_rules.test_http_rules.TestHost.test_different_host_in_uri_and_host_header Apr 26 09:57:00 192.168.122.209 [64370.853107] Start test: t_http_rules.test_http_rules.TestHost.test_forwarded_header_first Apr 26 09:57:01 192.168.122.209 [64371.913593] [tdb] Start Tempesta DB Apr 26 09:57:01 192.168.122.209 [64372.046515] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:57:03 192.168.122.209 [64373.643636] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64373.643636] Maybe that's fine, but it's worth checking the [64373.643636] config - if there is no relations between the [64373.643636] names, then host name confusion attack is possible. Apr 26 09:57:03 192.168.122.209 [64373.854402] [tempesta fw] Configuration processing is completed. Apr 26 09:57:03 192.168.122.209 [64373.910955] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:57:03 192.168.122.209 [64374.315518] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:57:03 192.168.122.209 [64374.341081] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:57:03 192.168.122.209 [64374.367027] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:57:03 192.168.122.209 [64374.470352] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:57:03 192.168.122.209 [64374.472174] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:57:03 192.168.122.209 [64374.534300] [tempesta fw] Tempesta FW is ready Apr 26 09:57:04 192.168.122.209 [64375.324277] [tdb] Close table 'client0.tdb' Apr 26 09:57:04 192.168.122.209 [64375.504527] [tdb] Close table 'sessions0.tdb' Apr 26 09:57:08 192.168.122.209 [64378.689129] [tdb] Close table 'cache0.tdb' Apr 26 09:57:08 192.168.122.209 [64378.924736] [tdb] Close table 'filter0.tdb' Apr 26 09:57:08 192.168.122.209 [64378.925175] [tempesta fw] modules are stopped Apr 26 09:57:08 192.168.122.209 [64379.231052] [tempesta fw] exiting... Apr 26 09:57:08 192.168.122.209 [64379.386318] [tdb] Shutdown Tempesta DB Apr 26 09:57:09 192.168.122.209 [64379.622181] End test: t_http_rules.test_http_rules.TestHost.test_forwarded_header_first Apr 26 09:57:09 192.168.122.209 [64379.632931] Start test: t_http_rules.test_http_rules.TestHost.test_forwarded_header_first_2 Apr 26 09:57:10 192.168.122.209 [64380.663913] [tdb] Start Tempesta DB Apr 26 09:57:10 192.168.122.209 [64380.796838] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:57:11 192.168.122.209 [64382.459853] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64382.459853] Maybe that's fine, but it's worth checking the [64382.459853] config - if there is no relations between the [64382.459853] names, then host name confusion attack is possible. Apr 26 09:57:12 192.168.122.209 [64382.670511] [tempesta fw] Configuration processing is completed. Apr 26 09:57:12 192.168.122.209 [64382.725798] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:57:12 192.168.122.209 [64383.129039] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:57:12 192.168.122.209 [64383.153987] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:57:12 192.168.122.209 [64383.178764] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:57:12 192.168.122.209 [64383.274461] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:57:12 192.168.122.209 [64383.276266] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:57:12 192.168.122.209 [64383.314362] [tempesta fw] Tempesta FW is ready Apr 26 09:57:13 192.168.122.209 [64384.063908] [tdb] Close table 'client0.tdb' Apr 26 09:57:13 192.168.122.209 [64384.239231] [tdb] Close table 'sessions0.tdb' Apr 26 09:57:16 192.168.122.209 [64387.516487] [tdb] Close table 'cache0.tdb' Apr 26 09:57:17 192.168.122.209 [64387.729724] [tdb] Close table 'filter0.tdb' Apr 26 09:57:17 192.168.122.209 [64387.730174] [tempesta fw] modules are stopped Apr 26 09:57:17 192.168.122.209 [64388.023543] [tempesta fw] exiting... Apr 26 09:57:17 192.168.122.209 [64388.148344] [tdb] Shutdown Tempesta DB Apr 26 09:57:17 192.168.122.209 [64388.334971] End test: t_http_rules.test_http_rules.TestHost.test_forwarded_header_first_2 Apr 26 09:57:17 192.168.122.209 [64388.356012] Start test: t_http_rules.test_http_rules.TestHost.test_hdr_host_in_forwarded_header Apr 26 09:57:18 192.168.122.209 [64389.356190] [tdb] Start Tempesta DB Apr 26 09:57:18 192.168.122.209 [64389.492183] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:57:20 192.168.122.209 [64391.175680] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64391.175680] Maybe that's fine, but it's worth checking the [64391.175680] config - if there is no relations between the [64391.175680] names, then host name confusion attack is possible. Apr 26 09:57:20 192.168.122.209 [64391.438602] [tempesta fw] Configuration processing is completed. Apr 26 09:57:20 192.168.122.209 [64391.495590] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:57:21 192.168.122.209 [64391.907257] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:57:21 192.168.122.209 [64391.935083] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:57:21 192.168.122.209 [64391.960259] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:57:21 192.168.122.209 [64392.042547] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:57:21 192.168.122.209 [64392.044324] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:57:21 192.168.122.209 [64392.110501] [tempesta fw] Tempesta FW is ready Apr 26 09:57:22 192.168.122.209 [64392.900373] [tdb] Close table 'client0.tdb' Apr 26 09:57:22 192.168.122.209 [64393.081537] [tdb] Close table 'sessions0.tdb' Apr 26 09:57:25 192.168.122.209 [64396.240473] [tdb] Close table 'cache0.tdb' Apr 26 09:57:25 192.168.122.209 [64396.472646] [tdb] Close table 'filter0.tdb' Apr 26 09:57:25 192.168.122.209 [64396.473081] [tempesta fw] modules are stopped Apr 26 09:57:26 192.168.122.209 [64396.729991] [tempesta fw] exiting... Apr 26 09:57:26 192.168.122.209 [64396.867414] [tdb] Shutdown Tempesta DB Apr 26 09:57:26 192.168.122.209 [64397.061410] End test: t_http_rules.test_http_rules.TestHost.test_hdr_host_in_forwarded_header Apr 26 09:57:26 192.168.122.209 [64397.072428] Start test: t_http_rules.test_http_rules.TestHost.test_hdr_host_in_uri Apr 26 09:57:27 192.168.122.209 [64398.097026] [tdb] Start Tempesta DB Apr 26 09:57:27 192.168.122.209 [64398.233424] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:57:29 192.168.122.209 [64399.879937] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64399.879937] Maybe that's fine, but it's worth checking the [64399.879937] config - if there is no relations between the [64399.879937] names, then host name confusion attack is possible. Apr 26 09:57:29 192.168.122.209 [64400.102729] [tempesta fw] Configuration processing is completed. Apr 26 09:57:29 192.168.122.209 [64400.161820] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:57:29 192.168.122.209 [64400.572087] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:57:29 192.168.122.209 [64400.598009] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:57:30 192.168.122.209 [64400.623578] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:57:30 192.168.122.209 [64400.718647] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:57:30 192.168.122.209 [64400.720420] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:57:30 192.168.122.209 [64400.758607] [tempesta fw] Tempesta FW is ready Apr 26 09:57:30 192.168.122.209 [64401.589210] [tdb] Close table 'client0.tdb' Apr 26 09:57:31 192.168.122.209 [64401.778678] [tdb] Close table 'sessions0.tdb' Apr 26 09:57:34 192.168.122.209 [64404.971033] [tdb] Close table 'cache0.tdb' Apr 26 09:57:34 192.168.122.209 [64405.217404] [tdb] Close table 'filter0.tdb' Apr 26 09:57:34 192.168.122.209 [64405.217835] [tempesta fw] modules are stopped Apr 26 09:57:34 192.168.122.209 [64405.447178] [tempesta fw] exiting... Apr 26 09:57:34 192.168.122.209 [64405.562394] [tdb] Shutdown Tempesta DB Apr 26 09:57:35 192.168.122.209 [64405.744110] End test: t_http_rules.test_http_rules.TestHost.test_hdr_host_in_uri Apr 26 09:57:35 192.168.122.209 [64405.765768] Start test: t_http_rules.test_http_rules.TestHost.test_host_in_forwarded_header Apr 26 09:57:36 192.168.122.209 [64406.785991] [tdb] Start Tempesta DB Apr 26 09:57:36 192.168.122.209 [64406.926853] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:57:38 192.168.122.209 [64408.613869] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64408.613869] Maybe that's fine, but it's worth checking the [64408.613869] config - if there is no relations between the [64408.613869] names, then host name confusion attack is possible. Apr 26 09:57:38 192.168.122.209 [64408.818830] [tempesta fw] Configuration processing is completed. Apr 26 09:57:38 192.168.122.209 [64408.870700] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:57:38 192.168.122.209 [64409.275929] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:57:38 192.168.122.209 [64409.306135] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:57:38 192.168.122.209 [64409.331963] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:57:38 192.168.122.209 [64409.422752] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:57:38 192.168.122.209 [64409.424578] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:57:38 192.168.122.209 [64409.462716] [tempesta fw] Tempesta FW is ready Apr 26 09:57:39 192.168.122.209 [64410.169276] [tdb] Close table 'client0.tdb' Apr 26 09:57:39 192.168.122.209 [64410.341962] [tdb] Close table 'sessions0.tdb' Apr 26 09:57:42 192.168.122.209 [64413.546441] [tdb] Close table 'cache0.tdb' Apr 26 09:57:43 192.168.122.209 [64413.798774] [tdb] Close table 'filter0.tdb' Apr 26 09:57:43 192.168.122.209 [64413.799211] [tempesta fw] modules are stopped Apr 26 09:57:43 192.168.122.209 [64414.042730] [tempesta fw] exiting... Apr 26 09:57:43 192.168.122.209 [64414.161215] [tdb] Shutdown Tempesta DB Apr 26 09:57:43 192.168.122.209 [64414.396287] End test: t_http_rules.test_http_rules.TestHost.test_host_in_forwarded_header Apr 26 09:57:43 192.168.122.209 [64414.407301] Start test: t_http_rules.test_http_rules.TestHost.test_host_in_host_header Apr 26 09:57:44 192.168.122.209 [64415.462872] [tdb] Start Tempesta DB Apr 26 09:57:44 192.168.122.209 [64415.591292] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:57:46 192.168.122.209 [64417.200186] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64417.200186] Maybe that's fine, but it's worth checking the [64417.200186] config - if there is no relations between the [64417.200186] names, then host name confusion attack is possible. Apr 26 09:57:46 192.168.122.209 [64417.414933] [tempesta fw] Configuration processing is completed. Apr 26 09:57:46 192.168.122.209 [64417.465016] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:57:47 192.168.122.209 [64417.870720] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:57:47 192.168.122.209 [64417.896064] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:57:47 192.168.122.209 [64417.921012] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:57:47 192.168.122.209 [64418.010852] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:57:47 192.168.122.209 [64418.012681] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:57:47 192.168.122.209 [64418.050821] [tempesta fw] Tempesta FW is ready Apr 26 09:57:48 192.168.122.209 [64418.844206] [tdb] Close table 'client0.tdb' Apr 26 09:57:48 192.168.122.209 [64419.031483] [tdb] Close table 'sessions0.tdb' Apr 26 09:57:51 192.168.122.209 [64422.195597] [tdb] Close table 'cache0.tdb' Apr 26 09:57:51 192.168.122.209 [64422.413539] [tdb] Close table 'filter0.tdb' Apr 26 09:57:51 192.168.122.209 [64422.413958] [tempesta fw] modules are stopped Apr 26 09:57:52 192.168.122.209 [64422.690144] [tempesta fw] exiting... Apr 26 09:57:52 192.168.122.209 [64422.841310] [tdb] Shutdown Tempesta DB Apr 26 09:57:52 192.168.122.209 [64423.034608] End test: t_http_rules.test_http_rules.TestHost.test_host_in_host_header Apr 26 09:57:52 192.168.122.209 [64423.043701] Start test: t_http_rules.test_http_rules.TestHost.test_host_in_uri Apr 26 09:57:53 192.168.122.209 [64424.062174] [tdb] Start Tempesta DB Apr 26 09:57:53 192.168.122.209 [64424.198028] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:57:55 192.168.122.209 [64425.824215] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64425.824215] Maybe that's fine, but it's worth checking the [64425.824215] config - if there is no relations between the [64425.824215] names, then host name confusion attack is possible. Apr 26 09:57:55 192.168.122.209 [64426.079020] [tempesta fw] Configuration processing is completed. Apr 26 09:57:55 192.168.122.209 [64426.135467] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:57:55 192.168.122.209 [64426.532559] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:57:55 192.168.122.209 [64426.557198] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:57:55 192.168.122.209 [64426.581868] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:57:56 192.168.122.209 [64426.698980] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:57:56 192.168.122.209 [64426.700792] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:57:56 192.168.122.209 [64426.742898] [tempesta fw] Tempesta FW is ready Apr 26 09:57:56 192.168.122.209 [64427.491686] [tdb] Close table 'client0.tdb' Apr 26 09:57:57 192.168.122.209 [64427.669698] [tdb] Close table 'sessions0.tdb' Apr 26 09:58:00 192.168.122.209 [64430.838653] [tdb] Close table 'cache0.tdb' Apr 26 09:58:00 192.168.122.209 [64431.081046] [tdb] Close table 'filter0.tdb' Apr 26 09:58:00 192.168.122.209 [64431.081451] [tempesta fw] modules are stopped Apr 26 09:58:00 192.168.122.209 [64431.318062] [tempesta fw] exiting... Apr 26 09:58:00 192.168.122.209 [64431.452710] [tdb] Shutdown Tempesta DB Apr 26 09:58:01 192.168.122.209 [64431.657355] End test: t_http_rules.test_http_rules.TestHost.test_host_in_uri Apr 26 09:58:01 192.168.122.209 [64431.669222] Start test: t_http_rules.test_http_tables.HttpTablesTestBase.test Apr 26 09:58:01 192.168.122.209 [64431.690510] End test: t_http_rules.test_http_tables.HttpTablesTestBase.test Apr 26 09:58:01 192.168.122.209 [64431.698011] Start test: t_http_rules.test_http_tables.HttpTablesTestCustomRedirectCorrectVariables.test Apr 26 09:58:02 192.168.122.209 [64432.795712] [tdb] Start Tempesta DB Apr 26 09:58:02 192.168.122.209 [64432.923746] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:58:04 192.168.122.209 [64434.637753] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64434.637753] Maybe that's fine, but it's worth checking the [64434.637753] config - if there is no relations between the [64434.637753] names, then host name confusion attack is possible. Apr 26 09:58:04 192.168.122.209 [64434.787033] [tempesta fw] Configuration processing is completed. Apr 26 09:58:04 192.168.122.209 [64434.837764] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:58:04 192.168.122.209 [64435.236958] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:58:04 192.168.122.209 [64435.272434] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:58:04 192.168.122.209 [64435.301911] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:58:04 192.168.122.209 [64435.351083] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:58:04 192.168.122.209 [64435.352792] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:58:04 192.168.122.209 [64435.387002] [tempesta fw] Tempesta FW is ready Apr 26 09:58:05 192.168.122.209 [64435.920753] [tdb] Close table 'client0.tdb' Apr 26 09:58:05 192.168.122.209 [64436.120751] [tdb] Close table 'sessions0.tdb' Apr 26 09:58:08 192.168.122.209 [64439.298192] [tdb] Close table 'cache0.tdb' Apr 26 09:58:08 192.168.122.209 [64439.539422] [tdb] Close table 'filter0.tdb' Apr 26 09:58:08 192.168.122.209 [64439.539866] [tempesta fw] modules are stopped Apr 26 09:58:09 192.168.122.209 [64439.731765] [tempesta fw] exiting... Apr 26 09:58:09 192.168.122.209 [64439.849791] [tdb] Shutdown Tempesta DB Apr 26 09:58:09 192.168.122.209 [64440.061707] End test: t_http_rules.test_http_tables.HttpTablesTestCustomRedirectCorrectVariables.test Apr 26 09:58:09 192.168.122.209 [64440.081632] Start test: t_http_rules.test_http_tables.HttpTablesTestCustomRedirectDifferentResponseStatus.test Apr 26 09:58:10 192.168.122.209 [64441.133300] [tdb] Start Tempesta DB Apr 26 09:58:10 192.168.122.209 [64441.269505] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:58:12 192.168.122.209 [64443.027992] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64443.027992] Maybe that's fine, but it's worth checking the [64443.027992] config - if there is no relations between the [64443.027992] names, then host name confusion attack is possible. Apr 26 09:58:12 192.168.122.209 [64443.179147] [tempesta fw] Configuration processing is completed. Apr 26 09:58:12 192.168.122.209 [64443.235671] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:58:13 192.168.122.209 [64443.650852] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:58:13 192.168.122.209 [64443.676127] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:58:13 192.168.122.209 [64443.701495] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:58:13 192.168.122.209 [64443.747167] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:58:13 192.168.122.209 [64443.748896] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:58:13 192.168.122.209 [64443.799120] [tempesta fw] Tempesta FW is ready Apr 26 09:58:13 192.168.122.209 [64444.375781] [tdb] Close table 'client0.tdb' Apr 26 09:58:13 192.168.122.209 [64444.568425] [tdb] Close table 'sessions0.tdb' Apr 26 09:58:17 192.168.122.209 [64447.700569] [tdb] Close table 'cache0.tdb' Apr 26 09:58:17 192.168.122.209 [64447.949319] [tdb] Close table 'filter0.tdb' Apr 26 09:58:17 192.168.122.209 [64447.949755] [tempesta fw] modules are stopped Apr 26 09:58:17 192.168.122.209 [64448.128848] [tempesta fw] exiting... Apr 26 09:58:17 192.168.122.209 [64448.260484] [tdb] Shutdown Tempesta DB Apr 26 09:58:17 192.168.122.209 [64448.438043] End test: t_http_rules.test_http_tables.HttpTablesTestCustomRedirectDifferentResponseStatus.test Apr 26 09:58:17 192.168.122.209 [64448.460327] Start test: t_http_rules.test_http_tables.HttpTablesTestCustomRedirectNonExistentVariables.test Apr 26 09:58:18 192.168.122.209 [64449.482231] [tdb] Start Tempesta DB Apr 26 09:58:19 192.168.122.209 [64449.619125] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:58:20 192.168.122.209 [64451.328740] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64451.328740] Maybe that's fine, but it's worth checking the [64451.328740] config - if there is no relations between the [64451.328740] names, then host name confusion attack is possible. Apr 26 09:58:20 192.168.122.209 [64451.471130] [tempesta fw] Configuration processing is completed. Apr 26 09:58:20 192.168.122.209 [64451.527484] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:58:21 192.168.122.209 [64451.939301] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:58:21 192.168.122.209 [64451.965504] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:58:21 192.168.122.209 [64451.992783] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:58:21 192.168.122.209 [64452.059252] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:58:21 192.168.122.209 [64452.060976] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:58:21 192.168.122.209 [64452.103218] [tempesta fw] Tempesta FW is ready Apr 26 09:58:22 192.168.122.209 [64452.656056] [tdb] Close table 'client0.tdb' Apr 26 09:58:22 192.168.122.209 [64452.837292] [tdb] Close table 'sessions0.tdb' Apr 26 09:58:25 192.168.122.209 [64456.047314] [tdb] Close table 'cache0.tdb' Apr 26 09:58:25 192.168.122.209 [64456.294524] [tdb] Close table 'filter0.tdb' Apr 26 09:58:25 192.168.122.209 [64456.294949] [tempesta fw] modules are stopped Apr 26 09:58:25 192.168.122.209 [64456.514575] [tempesta fw] exiting... Apr 26 09:58:26 192.168.122.209 [64456.625410] [tdb] Shutdown Tempesta DB Apr 26 09:58:26 192.168.122.209 [64456.850475] End test: t_http_rules.test_http_tables.HttpTablesTestCustomRedirectNonExistentVariables.test Apr 26 09:58:26 192.168.122.209 [64456.872732] Start test: t_http_rules.test_http_tables.HttpTablesTestCustomRedirectTooManyVariables.test Apr 26 09:58:27 192.168.122.209 [64457.905048] [tdb] Start Tempesta DB Apr 26 09:58:27 192.168.122.209 [64458.054862] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:58:29 192.168.122.209 [64459.648736] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64459.648736] Maybe that's fine, but it's worth checking the [64459.648736] config - if there is no relations between the [64459.648736] names, then host name confusion attack is possible. Apr 26 09:58:29 192.168.122.209 [64459.744466] [tempesta fw] ERROR: http_tbl: too many vars (more 8) in redirection url: 'https://$host$request_uri/$host$request_uri/$host$request_uri/$host$request_uri/$host' Apr 26 09:58:29 192.168.122.209 [64459.748698] [tempesta fw] ERROR: configuration parsing error: [64459.748698] 21: uri == "/static*" -> 301 = https://$host$request_uri/$host$request_uri/$host [64459.748698] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 09:58:29 192.168.122.209 [64459.755225] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 09:58:29 192.168.122.209 [64459.957745] [tempesta fw] exiting... Apr 26 09:58:29 192.168.122.209 [64460.103819] [tdb] Shutdown Tempesta DB Apr 26 09:58:32 192.168.122.209 [64462.775516] End test: t_http_rules.test_http_tables.HttpTablesTestCustomRedirectTooManyVariables.test Apr 26 09:58:32 192.168.122.209 [64462.785569] Start test: t_http_rules.test_http_tables.HttpTablesTestEmptyChainDefault.test Apr 26 09:58:33 192.168.122.209 [64463.778197] [tdb] Start Tempesta DB Apr 26 09:58:33 192.168.122.209 [64463.921788] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:58:33 192.168.122.209 [64464.580811] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64464.580811] Maybe that's fine, but it's worth checking the [64464.580811] config - if there is no relations between the [64464.580811] names, then host name confusion attack is possible. Apr 26 09:58:34 192.168.122.209 [64464.728735] [tempesta fw] Configuration processing is completed. Apr 26 09:58:34 192.168.122.209 [64464.785212] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:58:34 192.168.122.209 [64465.195242] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:58:34 192.168.122.209 [64465.221268] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:58:34 192.168.122.209 [64465.247951] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:58:34 192.168.122.209 [64465.299415] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:58:34 192.168.122.209 [64465.301139] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:58:34 192.168.122.209 [64465.340664] [tempesta fw] Tempesta FW is ready Apr 26 09:58:34 192.168.122.209 [64465.474786] [tempesta fw] Warning: request dropped: cannot find appropriate virtual host, status 403: 127.0.0.2 Apr 26 09:58:35 192.168.122.209 [64465.902125] [tdb] Close table 'client0.tdb' Apr 26 09:58:35 192.168.122.209 [64466.094579] [tdb] Close table 'sessions0.tdb' Apr 26 09:58:38 192.168.122.209 [64469.314611] [tdb] Close table 'cache0.tdb' Apr 26 09:58:38 192.168.122.209 [64469.547377] [tdb] Close table 'filter0.tdb' Apr 26 09:58:38 192.168.122.209 [64469.547816] [tempesta fw] modules are stopped Apr 26 09:58:39 192.168.122.209 [64469.764400] [tempesta fw] exiting... Apr 26 09:58:39 192.168.122.209 [64469.895796] [tdb] Shutdown Tempesta DB Apr 26 09:58:39 192.168.122.209 [64470.113057] End test: t_http_rules.test_http_tables.HttpTablesTestEmptyChainDefault.test Apr 26 09:58:39 192.168.122.209 [64470.126803] Start test: t_http_rules.test_http_tables.HttpTablesTestEmptyChainDrop.test Apr 26 09:58:40 192.168.122.209 [64471.179358] [tdb] Start Tempesta DB Apr 26 09:58:40 192.168.122.209 [64471.319999] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:58:42 192.168.122.209 [64473.004810] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64473.004810] Maybe that's fine, but it's worth checking the [64473.004810] config - if there is no relations between the [64473.004810] names, then host name confusion attack is possible. Apr 26 09:58:42 192.168.122.209 [64473.175497] [tempesta fw] Configuration processing is completed. Apr 26 09:58:42 192.168.122.209 [64473.232953] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:58:43 192.168.122.209 [64473.652101] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:58:43 192.168.122.209 [64473.679481] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:58:43 192.168.122.209 [64473.705050] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:58:43 192.168.122.209 [64473.755541] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:58:43 192.168.122.209 [64473.757279] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:58:43 192.168.122.209 [64473.795479] [tempesta fw] Tempesta FW is ready Apr 26 09:58:43 192.168.122.209 [64473.931120] [tempesta fw] Warning: request dropped: cannot find appropriate virtual host, status 403: 127.0.0.2 Apr 26 09:58:43 192.168.122.209 [64474.351944] [tdb] Close table 'client0.tdb' Apr 26 09:58:43 192.168.122.209 [64474.536902] [tdb] Close table 'sessions0.tdb' Apr 26 09:58:47 192.168.122.209 [64477.719535] [tdb] Close table 'cache0.tdb' Apr 26 09:58:47 192.168.122.209 [64477.993288] [tdb] Close table 'filter0.tdb' Apr 26 09:58:47 192.168.122.209 [64477.993723] [tempesta fw] modules are stopped Apr 26 09:58:47 192.168.122.209 [64478.172041] [tempesta fw] exiting... Apr 26 09:58:47 192.168.122.209 [64478.265762] [tdb] Shutdown Tempesta DB Apr 26 09:58:47 192.168.122.209 [64478.459609] End test: t_http_rules.test_http_tables.HttpTablesTestEmptyChainDrop.test Apr 26 09:58:47 192.168.122.209 [64478.477287] Start test: t_http_rules.test_http_tables.HttpTablesTestEmptyChainReply.test Apr 26 09:58:48 192.168.122.209 [64479.500784] [tdb] Start Tempesta DB Apr 26 09:58:49 192.168.122.209 [64479.649056] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:58:50 192.168.122.209 [64481.377007] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64481.377007] Maybe that's fine, but it's worth checking the [64481.377007] config - if there is no relations between the [64481.377007] names, then host name confusion attack is possible. Apr 26 09:58:50 192.168.122.209 [64481.531575] [tempesta fw] Configuration processing is completed. Apr 26 09:58:50 192.168.122.209 [64481.586960] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:58:51 192.168.122.209 [64481.994304] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:58:51 192.168.122.209 [64482.020759] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:58:51 192.168.122.209 [64482.045907] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:58:51 192.168.122.209 [64482.091594] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:58:51 192.168.122.209 [64482.092838] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:58:51 192.168.122.209 [64482.155478] [tempesta fw] Tempesta FW is ready Apr 26 09:58:51 192.168.122.209 [64482.285466] [tempesta fw] Warning: request dropped: cannot find appropriate virtual host, status 403: 127.0.0.2 Apr 26 09:58:52 192.168.122.209 [64482.684103] [tdb] Close table 'client0.tdb' Apr 26 09:58:52 192.168.122.209 [64482.891294] [tdb] Close table 'sessions0.tdb' Apr 26 09:58:55 192.168.122.209 [64486.051796] [tdb] Close table 'cache0.tdb' Apr 26 09:58:55 192.168.122.209 [64486.289579] [tdb] Close table 'filter0.tdb' Apr 26 09:58:55 192.168.122.209 [64486.290004] [tempesta fw] modules are stopped Apr 26 09:58:55 192.168.122.209 [64486.486143] [tempesta fw] exiting... Apr 26 09:58:55 192.168.122.209 [64486.592623] [tdb] Shutdown Tempesta DB Apr 26 09:58:56 192.168.122.209 [64486.798241] End test: t_http_rules.test_http_tables.HttpTablesTestEmptyChainReply.test Apr 26 09:58:56 192.168.122.209 [64486.815393] Start test: t_http_rules.test_http_tables.HttpTablesTestEmptyMainChainDefault.test Apr 26 09:58:57 192.168.122.209 [64487.863808] [tdb] Start Tempesta DB Apr 26 09:58:57 192.168.122.209 [64487.989997] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:58:58 192.168.122.209 [64489.513781] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64489.513781] Maybe that's fine, but it's worth checking the [64489.513781] config - if there is no relations between the [64489.513781] names, then host name confusion attack is possible. Apr 26 09:58:59 192.168.122.209 [64489.643669] [tempesta fw] Configuration processing is completed. Apr 26 09:58:59 192.168.122.209 [64489.695309] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:58:59 192.168.122.209 [64490.103161] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:58:59 192.168.122.209 [64490.128141] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:58:59 192.168.122.209 [64490.153284] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:58:59 192.168.122.209 [64490.203720] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:58:59 192.168.122.209 [64490.205476] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:58:59 192.168.122.209 [64490.263668] [tempesta fw] Tempesta FW is ready Apr 26 09:58:59 192.168.122.209 [64490.393959] [tempesta fw] Warning: request dropped: cannot find appropriate virtual host, status 403: 127.0.0.2 Apr 26 09:59:00 192.168.122.209 [64490.840828] [tdb] Close table 'client0.tdb' Apr 26 09:59:00 192.168.122.209 [64491.050021] [tdb] Close table 'sessions0.tdb' Apr 26 09:59:03 192.168.122.209 [64494.256886] [tdb] Close table 'cache0.tdb' Apr 26 09:59:03 192.168.122.209 [64494.494101] [tdb] Close table 'filter0.tdb' Apr 26 09:59:03 192.168.122.209 [64494.494528] [tempesta fw] modules are stopped Apr 26 09:59:04 192.168.122.209 [64494.695840] [tempesta fw] exiting... Apr 26 09:59:04 192.168.122.209 [64494.851389] [tdb] Shutdown Tempesta DB Apr 26 09:59:04 192.168.122.209 [64495.064807] End test: t_http_rules.test_http_tables.HttpTablesTestEmptyMainChainDefault.test Apr 26 09:59:04 192.168.122.209 [64495.078225] Start test: t_http_rules.test_http_tables.HttpTablesTestEmptyMainChainDrop.test Apr 26 09:59:05 192.168.122.209 [64496.108172] [tdb] Start Tempesta DB Apr 26 09:59:05 192.168.122.209 [64496.245543] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:59:07 192.168.122.209 [64497.865108] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64497.865108] Maybe that's fine, but it's worth checking the [64497.865108] config - if there is no relations between the [64497.865108] names, then host name confusion attack is possible. Apr 26 09:59:07 192.168.122.209 [64497.987773] [tempesta fw] Configuration processing is completed. Apr 26 09:59:07 192.168.122.209 [64498.046017] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:59:07 192.168.122.209 [64498.448860] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:59:07 192.168.122.209 [64498.476029] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:59:07 192.168.122.209 [64498.501170] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:59:07 192.168.122.209 [64498.543811] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:59:07 192.168.122.209 [64498.545532] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:59:07 192.168.122.209 [64498.583747] [tempesta fw] Tempesta FW is ready Apr 26 09:59:08 192.168.122.209 [64498.724813] [tempesta fw] Warning: request dropped: cannot find appropriate virtual host, status 403: 127.0.0.2 Apr 26 09:59:08 192.168.122.209 [64499.122463] [tdb] Close table 'client0.tdb' Apr 26 09:59:08 192.168.122.209 [64499.289082] [tdb] Close table 'sessions0.tdb' Apr 26 09:59:11 192.168.122.209 [64502.506364] [tdb] Close table 'cache0.tdb' Apr 26 09:59:12 192.168.122.209 [64502.734991] [tdb] Close table 'filter0.tdb' Apr 26 09:59:12 192.168.122.209 [64502.735420] [tempesta fw] modules are stopped Apr 26 09:59:12 192.168.122.209 [64502.955848] [tempesta fw] exiting... Apr 26 09:59:12 192.168.122.209 [64503.086561] [tdb] Shutdown Tempesta DB Apr 26 09:59:12 192.168.122.209 [64503.312937] End test: t_http_rules.test_http_tables.HttpTablesTestEmptyMainChainDrop.test Apr 26 09:59:12 192.168.122.209 [64503.330815] Start test: t_http_rules.test_http_tables.HttpTablesTestEmptyMainChainReply.test Apr 26 09:59:13 192.168.122.209 [64504.395377] [tdb] Start Tempesta DB Apr 26 09:59:13 192.168.122.209 [64504.529179] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:59:15 192.168.122.209 [64506.149275] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64506.149275] Maybe that's fine, but it's worth checking the [64506.149275] config - if there is no relations between the [64506.149275] names, then host name confusion attack is possible. Apr 26 09:59:15 192.168.122.209 [64506.304130] [tempesta fw] Configuration processing is completed. Apr 26 09:59:15 192.168.122.209 [64506.357729] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:59:16 192.168.122.209 [64506.769607] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:59:16 192.168.122.209 [64506.794954] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:59:16 192.168.122.209 [64506.820798] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:59:16 192.168.122.209 [64506.863913] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:59:16 192.168.122.209 [64506.865265] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:59:16 192.168.122.209 [64506.903864] [tempesta fw] Tempesta FW is ready Apr 26 09:59:16 192.168.122.209 [64507.046684] [tempesta fw] Warning: request dropped: cannot find appropriate virtual host, status 403: 127.0.0.2 Apr 26 09:59:16 192.168.122.209 [64507.475513] [tdb] Close table 'client0.tdb' Apr 26 09:59:17 192.168.122.209 [64507.685295] [tdb] Close table 'sessions0.tdb' Apr 26 09:59:20 192.168.122.209 [64510.847040] [tdb] Close table 'cache0.tdb' Apr 26 09:59:20 192.168.122.209 [64511.110988] [tdb] Close table 'filter0.tdb' Apr 26 09:59:20 192.168.122.209 [64511.111430] [tempesta fw] modules are stopped Apr 26 09:59:20 192.168.122.209 [64511.361267] [tempesta fw] exiting... Apr 26 09:59:20 192.168.122.209 [64511.468787] [tdb] Shutdown Tempesta DB Apr 26 09:59:21 192.168.122.209 [64511.693174] End test: t_http_rules.test_http_tables.HttpTablesTestEmptyMainChainReply.test Apr 26 09:59:21 192.168.122.209 [64511.704890] Start test: t_http_rules.test_http_tables.HttpTablesTestMarkRule.test_reject_by_mark_disable_tso_gro_gso Apr 26 09:59:22 192.168.122.209 [64512.731121] [tdb] Start Tempesta DB Apr 26 09:59:22 192.168.122.209 [64512.865080] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:59:23 192.168.122.209 [64514.461305] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64514.461305] Maybe that's fine, but it's worth checking the [64514.461305] config - if there is no relations between the [64514.461305] names, then host name confusion attack is possible. Apr 26 09:59:23 192.168.122.209 [64514.611978] [tempesta fw] Configuration processing is completed. Apr 26 09:59:24 192.168.122.209 [64514.669252] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:59:24 192.168.122.209 [64515.086917] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:59:24 192.168.122.209 [64515.112611] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:59:24 192.168.122.209 [64515.138034] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:59:24 192.168.122.209 [64515.183947] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:59:24 192.168.122.209 [64515.185097] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:59:24 192.168.122.209 [64515.223950] [tempesta fw] Tempesta FW is ready Apr 26 09:59:28 192.168.122.209 [64519.189015] [tdb] Close table 'client0.tdb' Apr 26 09:59:28 192.168.122.209 [64519.378172] [tdb] Close table 'sessions0.tdb' Apr 26 09:59:31 192.168.122.209 [64522.574668] [tdb] Close table 'cache0.tdb' Apr 26 09:59:32 192.168.122.209 [64522.823433] [tdb] Close table 'filter0.tdb' Apr 26 09:59:32 192.168.122.209 [64522.823860] [tempesta fw] modules are stopped Apr 26 09:59:32 192.168.122.209 [64523.035989] [tempesta fw] exiting... Apr 26 09:59:32 192.168.122.209 [64523.150068] [tdb] Shutdown Tempesta DB Apr 26 09:59:32 192.168.122.209 [64523.351913] End test: t_http_rules.test_http_tables.HttpTablesTestMarkRule.test_reject_by_mark_disable_tso_gro_gso Apr 26 09:59:32 192.168.122.209 [64523.374677] Start test: t_http_rules.test_http_tables.HttpTablesTestMarkRule.test_reject_by_mark_enable_tso_gro_gso Apr 26 09:59:33 192.168.122.209 [64524.435671] [tdb] Start Tempesta DB Apr 26 09:59:33 192.168.122.209 [64524.566491] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:59:35 192.168.122.209 [64526.181411] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64526.181411] Maybe that's fine, but it's worth checking the [64526.181411] config - if there is no relations between the [64526.181411] names, then host name confusion attack is possible. Apr 26 09:59:35 192.168.122.209 [64526.344105] [tempesta fw] Configuration processing is completed. Apr 26 09:59:35 192.168.122.209 [64526.395053] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:59:36 192.168.122.209 [64526.802944] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:59:36 192.168.122.209 [64526.829414] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:59:36 192.168.122.209 [64526.856076] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:59:36 192.168.122.209 [64526.912148] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:59:36 192.168.122.209 [64526.913897] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:59:36 192.168.122.209 [64526.952088] [tempesta fw] Tempesta FW is ready Apr 26 09:59:40 192.168.122.209 [64530.804974] [tdb] Close table 'client0.tdb' Apr 26 09:59:40 192.168.122.209 [64531.005401] [tdb] Close table 'sessions0.tdb' Apr 26 09:59:43 192.168.122.209 [64534.183269] [tdb] Close table 'cache0.tdb' Apr 26 09:59:43 192.168.122.209 [64534.430094] [tdb] Close table 'filter0.tdb' Apr 26 09:59:43 192.168.122.209 [64534.430519] [tempesta fw] modules are stopped Apr 26 09:59:44 192.168.122.209 [64534.647348] [tempesta fw] exiting... Apr 26 09:59:44 192.168.122.209 [64534.735044] [tdb] Shutdown Tempesta DB Apr 26 09:59:44 192.168.122.209 [64534.923107] End test: t_http_rules.test_http_tables.HttpTablesTestMarkRule.test_reject_by_mark_enable_tso_gro_gso Apr 26 09:59:44 192.168.122.209 [64534.933296] Start test: t_http_rules.test_http_tables.HttpTablesTestMarkRules.test_chains Apr 26 09:59:45 192.168.122.209 [64536.133558] [tdb] Start Tempesta DB Apr 26 09:59:45 192.168.122.209 [64536.292910] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 09:59:48 192.168.122.209 [64539.481937] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64539.481937] Maybe that's fine, but it's worth checking the [64539.481937] config - if there is no relations between the [64539.481937] names, then host name confusion attack is possible. Apr 26 09:59:49 192.168.122.209 [64539.960361] [tempesta fw] Configuration processing is completed. Apr 26 09:59:49 192.168.122.209 [64540.012464] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 09:59:49 192.168.122.209 [64540.427505] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 09:59:49 192.168.122.209 [64540.453166] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 09:59:49 192.168.122.209 [64540.479945] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 09:59:50 192.168.122.209 [64540.668305] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 09:59:50 192.168.122.209 [64540.670125] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 09:59:50 192.168.122.209 [64540.716266] [tempesta fw] Tempesta FW is ready Apr 26 09:59:52 192.168.122.209 [64543.568201] [tdb] Close table 'client0.tdb' Apr 26 09:59:53 192.168.122.209 [64543.748447] [tdb] Close table 'sessions0.tdb' Apr 26 09:59:56 192.168.122.209 [64546.986367] [tdb] Close table 'cache0.tdb' Apr 26 09:59:56 192.168.122.209 [64547.228049] [tdb] Close table 'filter0.tdb' Apr 26 09:59:56 192.168.122.209 [64547.228491] [tempesta fw] modules are stopped Apr 26 09:59:57 192.168.122.209 [64547.652757] [tempesta fw] exiting... Apr 26 09:59:57 192.168.122.209 [64547.825126] [tdb] Shutdown Tempesta DB Apr 26 09:59:57 192.168.122.209 [64548.038813] End test: t_http_rules.test_http_tables.HttpTablesTestMarkRules.test_chains Apr 26 09:59:57 192.168.122.209 [64548.050666] Start test: t_http_rules.test_http_tables.HttpTablesTestMixedChainDefault.test Apr 26 09:59:58 192.168.122.209 [64549.038659] [tdb] Start Tempesta DB Apr 26 09:59:58 192.168.122.209 [64549.166733] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:00:00 192.168.122.209 [64550.877736] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64550.877736] Maybe that's fine, but it's worth checking the [64550.877736] config - if there is no relations between the [64550.877736] names, then host name confusion attack is possible. Apr 26 10:00:00 192.168.122.209 [64551.040444] [tempesta fw] Configuration processing is completed. Apr 26 10:00:00 192.168.122.209 [64551.101965] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:00:00 192.168.122.209 [64551.509197] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:00:00 192.168.122.209 [64551.536076] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:00:00 192.168.122.209 [64551.561638] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:00:00 192.168.122.209 [64551.600437] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:00:00 192.168.122.209 [64551.602346] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:00:01 192.168.122.209 [64551.640408] [tempesta fw] Tempesta FW is ready Apr 26 10:00:01 192.168.122.209 [64551.781630] [tempesta fw] Warning: request dropped: cannot find appropriate virtual host, status 403: 127.0.0.2 Apr 26 10:00:01 192.168.122.209 [64552.171566] [tdb] Close table 'client0.tdb' Apr 26 10:00:01 192.168.122.209 [64552.357885] [tdb] Close table 'sessions0.tdb' Apr 26 10:00:04 192.168.122.209 [64555.564706] [tdb] Close table 'cache0.tdb' Apr 26 10:00:05 192.168.122.209 [64555.808342] [tdb] Close table 'filter0.tdb' Apr 26 10:00:05 192.168.122.209 [64555.808779] [tempesta fw] modules are stopped Apr 26 10:00:05 192.168.122.209 [64556.044328] [tempesta fw] exiting... Apr 26 10:00:05 192.168.122.209 [64556.174580] [tdb] Shutdown Tempesta DB Apr 26 10:00:05 192.168.122.209 [64556.408173] End test: t_http_rules.test_http_tables.HttpTablesTestMixedChainDefault.test Apr 26 10:00:05 192.168.122.209 [64556.421448] Start test: t_http_rules.test_http_tables.HttpTablesTestMixedChainDrop.test Apr 26 10:00:06 192.168.122.209 [64557.410036] [tdb] Start Tempesta DB Apr 26 10:00:06 192.168.122.209 [64557.546856] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:00:08 192.168.122.209 [64559.266068] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64559.266068] Maybe that's fine, but it's worth checking the [64559.266068] config - if there is no relations between the [64559.266068] names, then host name confusion attack is possible. Apr 26 10:00:08 192.168.122.209 [64559.436521] [tempesta fw] Configuration processing is completed. Apr 26 10:00:08 192.168.122.209 [64559.497218] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:00:09 192.168.122.209 [64559.900624] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:00:09 192.168.122.209 [64559.926980] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:00:09 192.168.122.209 [64559.951476] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:00:09 192.168.122.209 [64560.008540] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:00:09 192.168.122.209 [64560.010355] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:00:09 192.168.122.209 [64560.056500] [tempesta fw] Tempesta FW is ready Apr 26 10:00:09 192.168.122.209 [64560.201668] [tempesta fw] Warning: request dropped: cannot find appropriate virtual host, status 403: 127.0.0.2 Apr 26 10:00:10 192.168.122.209 [64560.619548] [tdb] Close table 'client0.tdb' Apr 26 10:00:10 192.168.122.209 [64560.810318] [tdb] Close table 'sessions0.tdb' Apr 26 10:00:13 192.168.122.209 [64564.055429] [tdb] Close table 'cache0.tdb' Apr 26 10:00:13 192.168.122.209 [64564.300958] [tdb] Close table 'filter0.tdb' Apr 26 10:00:13 192.168.122.209 [64564.301367] [tempesta fw] modules are stopped Apr 26 10:00:13 192.168.122.209 [64564.492992] [tempesta fw] exiting... Apr 26 10:00:14 192.168.122.209 [64564.635381] [tdb] Shutdown Tempesta DB Apr 26 10:00:14 192.168.122.209 [64564.849972] End test: t_http_rules.test_http_tables.HttpTablesTestMixedChainDrop.test Apr 26 10:00:14 192.168.122.209 [64564.863656] Start test: t_http_rules.test_http_tables.HttpTablesTestMixedChainReply.test Apr 26 10:00:15 192.168.122.209 [64565.979101] [tdb] Start Tempesta DB Apr 26 10:00:15 192.168.122.209 [64566.126041] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:00:17 192.168.122.209 [64567.945897] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64567.945897] Maybe that's fine, but it's worth checking the [64567.945897] config - if there is no relations between the [64567.945897] names, then host name confusion attack is possible. Apr 26 10:00:17 192.168.122.209 [64568.100610] [tempesta fw] Configuration processing is completed. Apr 26 10:00:17 192.168.122.209 [64568.151961] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:00:17 192.168.122.209 [64568.594962] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:00:18 192.168.122.209 [64568.621922] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:00:18 192.168.122.209 [64568.649976] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:00:18 192.168.122.209 [64568.688629] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:00:18 192.168.122.209 [64568.690366] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:00:18 192.168.122.209 [64568.728521] [tempesta fw] Tempesta FW is ready Apr 26 10:00:18 192.168.122.209 [64568.866036] [tempesta fw] Warning: request dropped: cannot find appropriate virtual host, status 403: 127.0.0.2 Apr 26 10:00:18 192.168.122.209 [64569.329090] [tdb] Close table 'client0.tdb' Apr 26 10:00:18 192.168.122.209 [64569.519960] [tdb] Close table 'sessions0.tdb' Apr 26 10:00:22 192.168.122.209 [64572.697578] [tdb] Close table 'cache0.tdb' Apr 26 10:00:22 192.168.122.209 [64572.964322] [tdb] Close table 'filter0.tdb' Apr 26 10:00:22 192.168.122.209 [64572.964781] [tempesta fw] modules are stopped Apr 26 10:00:22 192.168.122.209 [64573.149130] [tempesta fw] exiting... Apr 26 10:00:22 192.168.122.209 [64573.254136] [tdb] Shutdown Tempesta DB Apr 26 10:00:22 192.168.122.209 [64573.480822] End test: t_http_rules.test_http_tables.HttpTablesTestMixedChainReply.test Apr 26 10:00:22 192.168.122.209 [64573.489698] Start test: t_http_rules.test_http_tables.HttpTablesTestMixedChainResp.test Apr 26 10:00:23 192.168.122.209 [64574.503176] [tdb] Start Tempesta DB Apr 26 10:00:24 192.168.122.209 [64574.635926] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:00:25 192.168.122.209 [64576.265995] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64576.265995] Maybe that's fine, but it's worth checking the [64576.265995] config - if there is no relations between the [64576.265995] names, then host name confusion attack is possible. Apr 26 10:00:25 192.168.122.209 [64576.424683] [tempesta fw] Configuration processing is completed. Apr 26 10:00:25 192.168.122.209 [64576.477563] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:00:26 192.168.122.209 [64576.875122] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:00:26 192.168.122.209 [64576.901598] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:00:26 192.168.122.209 [64576.926998] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:00:26 192.168.122.209 [64576.972680] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:00:26 192.168.122.209 [64576.974455] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:00:26 192.168.122.209 [64577.020704] [tempesta fw] Tempesta FW is ready Apr 26 10:00:26 192.168.122.209 [64577.590068] [tdb] Close table 'client0.tdb' Apr 26 10:00:27 192.168.122.209 [64577.782932] [tdb] Close table 'sessions0.tdb' Apr 26 10:00:30 192.168.122.209 [64581.068833] [tdb] Close table 'cache0.tdb' Apr 26 10:00:30 192.168.122.209 [64581.322830] [tdb] Close table 'filter0.tdb' Apr 26 10:00:30 192.168.122.209 [64581.323301] [tempesta fw] modules are stopped Apr 26 10:00:30 192.168.122.209 [64581.512168] [tempesta fw] exiting... Apr 26 10:00:31 192.168.122.209 [64581.639224] [tdb] Shutdown Tempesta DB Apr 26 10:00:31 192.168.122.209 [64581.839494] End test: t_http_rules.test_http_tables.HttpTablesTestMixedChainResp.test Apr 26 10:00:31 192.168.122.209 [64581.862754] Start test: t_http_rules.test_http_tables.HttpTablesTestMultipleCookiesH2.test_cookie_good_prefix Apr 26 10:00:32 192.168.122.209 [64582.956300] [tdb] Start Tempesta DB Apr 26 10:00:32 192.168.122.209 [64583.134902] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:00:34 192.168.122.209 [64584.990245] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64584.990245] Maybe that's fine, but it's worth checking the [64584.990245] config - if there is no relations between the [64584.990245] names, then host name confusion attack is possible. Apr 26 10:00:34 192.168.122.209 [64585.232895] [tempesta fw] Configuration processing is completed. Apr 26 10:00:34 192.168.122.209 [64585.286928] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:00:35 192.168.122.209 [64585.767927] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:00:35 192.168.122.209 [64585.801135] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:00:35 192.168.122.209 [64585.833495] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:00:35 192.168.122.209 [64585.948875] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:00:35 192.168.122.209 [64585.950722] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:00:35 192.168.122.209 [64585.988808] [tempesta fw] Tempesta FW is ready Apr 26 10:00:36 192.168.122.209 [64586.854363] [tdb] Close table 'client0.tdb' Apr 26 10:00:36 192.168.122.209 [64587.035138] [tdb] Close table 'sessions0.tdb' Apr 26 10:00:39 192.168.122.209 [64590.284623] [tdb] Close table 'cache0.tdb' Apr 26 10:00:39 192.168.122.209 [64590.532191] [tdb] Close table 'filter0.tdb' Apr 26 10:00:39 192.168.122.209 [64590.532634] [tempesta fw] modules are stopped Apr 26 10:00:40 192.168.122.209 [64590.792625] [tempesta fw] exiting... Apr 26 10:00:40 192.168.122.209 [64590.912556] [tdb] Shutdown Tempesta DB Apr 26 10:00:40 192.168.122.209 [64591.128980] End test: t_http_rules.test_http_tables.HttpTablesTestMultipleCookiesH2.test_cookie_good_prefix Apr 26 10:00:40 192.168.122.209 [64591.144547] Start test: t_http_rules.test_http_tables.HttpTablesTestMultipleCookiesH2.test_cookie_good_suffix Apr 26 10:00:41 192.168.122.209 [64592.238665] [tdb] Start Tempesta DB Apr 26 10:00:41 192.168.122.209 [64592.369240] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:00:43 192.168.122.209 [64594.326326] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64594.326326] Maybe that's fine, but it's worth checking the [64594.326326] config - if there is no relations between the [64594.326326] names, then host name confusion attack is possible. Apr 26 10:00:43 192.168.122.209 [64594.581086] [tempesta fw] Configuration processing is completed. Apr 26 10:00:44 192.168.122.209 [64594.645906] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:00:44 192.168.122.209 [64595.182684] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:00:44 192.168.122.209 [64595.215396] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:00:44 192.168.122.209 [64595.248454] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:00:44 192.168.122.209 [64595.333050] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:00:44 192.168.122.209 [64595.334901] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:00:44 192.168.122.209 [64595.384913] [tempesta fw] Tempesta FW is ready Apr 26 10:00:45 192.168.122.209 [64596.167983] [tdb] Close table 'client0.tdb' Apr 26 10:00:45 192.168.122.209 [64596.340157] [tdb] Close table 'sessions0.tdb' Apr 26 10:00:48 192.168.122.209 [64599.549201] [tdb] Close table 'cache0.tdb' Apr 26 10:00:49 192.168.122.209 [64599.811537] [tdb] Close table 'filter0.tdb' Apr 26 10:00:49 192.168.122.209 [64599.812010] [tempesta fw] modules are stopped Apr 26 10:00:49 192.168.122.209 [64600.074820] [tempesta fw] exiting... Apr 26 10:00:49 192.168.122.209 [64600.204705] [tdb] Shutdown Tempesta DB Apr 26 10:00:49 192.168.122.209 [64600.423788] End test: t_http_rules.test_http_tables.HttpTablesTestMultipleCookiesH2.test_cookie_good_suffix Apr 26 10:00:49 192.168.122.209 [64600.436600] Start test: t_http_rules.test_http_tables.HttpTablesTestMultipleCookiesH2.test_cookie_no_rules_matched Apr 26 10:00:50 192.168.122.209 [64601.497323] [tdb] Start Tempesta DB Apr 26 10:00:51 192.168.122.209 [64601.638290] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:00:53 192.168.122.209 [64603.638362] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64603.638362] Maybe that's fine, but it's worth checking the [64603.638362] config - if there is no relations between the [64603.638362] names, then host name confusion attack is possible. Apr 26 10:00:53 192.168.122.209 [64603.885131] [tempesta fw] Configuration processing is completed. Apr 26 10:00:53 192.168.122.209 [64603.941233] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:00:53 192.168.122.209 [64604.357016] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:00:53 192.168.122.209 [64604.384449] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:00:53 192.168.122.209 [64604.410941] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:00:53 192.168.122.209 [64604.525100] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:00:53 192.168.122.209 [64604.526983] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:00:53 192.168.122.209 [64604.573016] [tempesta fw] Tempesta FW is ready Apr 26 10:00:54 192.168.122.209 [64605.407224] [tdb] Close table 'client0.tdb' Apr 26 10:00:54 192.168.122.209 [64605.588050] [tdb] Close table 'sessions0.tdb' Apr 26 10:00:58 192.168.122.209 [64608.767533] [tdb] Close table 'cache0.tdb' Apr 26 10:00:58 192.168.122.209 [64609.027292] [tdb] Close table 'filter0.tdb' Apr 26 10:00:58 192.168.122.209 [64609.027742] [tempesta fw] modules are stopped Apr 26 10:00:58 192.168.122.209 [64609.306321] [tempesta fw] exiting... Apr 26 10:00:58 192.168.122.209 [64609.427127] [tdb] Shutdown Tempesta DB Apr 26 10:00:59 192.168.122.209 [64609.636324] End test: t_http_rules.test_http_tables.HttpTablesTestMultipleCookiesH2.test_cookie_no_rules_matched Apr 26 10:00:59 192.168.122.209 [64609.650112] Start test: t_http_rules.test_http_tables.HttpTablesTestMultipleCookiesH2.test_cookie_tempesta_bad Apr 26 10:01:00 192.168.122.209 [64610.697308] [tdb] Start Tempesta DB Apr 26 10:01:00 192.168.122.209 [64610.842686] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:01:02 192.168.122.209 [64612.746449] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64612.746449] Maybe that's fine, but it's worth checking the [64612.746449] config - if there is no relations between the [64612.746449] names, then host name confusion attack is possible. Apr 26 10:01:02 192.168.122.209 [64613.005249] [tempesta fw] Configuration processing is completed. Apr 26 10:01:02 192.168.122.209 [64613.065433] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:01:02 192.168.122.209 [64613.473859] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:01:02 192.168.122.209 [64613.499156] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:01:02 192.168.122.209 [64613.526352] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:01:03 192.168.122.209 [64613.617176] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:01:03 192.168.122.209 [64613.619016] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:01:03 192.168.122.209 [64613.697123] [tempesta fw] Tempesta FW is ready Apr 26 10:01:03 192.168.122.209 [64613.908482] [tempesta fw] Warning: request has been filtered out via http table: 127.0.0.2 Apr 26 10:01:03 192.168.122.209 [64614.523797] [tdb] Close table 'client0.tdb' Apr 26 10:01:04 192.168.122.209 [64614.705127] [tdb] Close table 'sessions0.tdb' Apr 26 10:01:07 192.168.122.209 [64617.837201] [tdb] Close table 'cache0.tdb' Apr 26 10:01:07 192.168.122.209 [64618.082441] [tdb] Close table 'filter0.tdb' Apr 26 10:01:07 192.168.122.209 [64618.082839] [tempesta fw] modules are stopped Apr 26 10:01:07 192.168.122.209 [64618.364858] [tempesta fw] exiting... Apr 26 10:01:07 192.168.122.209 [64618.517360] [tdb] Shutdown Tempesta DB Apr 26 10:01:08 192.168.122.209 [64618.720526] End test: t_http_rules.test_http_tables.HttpTablesTestMultipleCookiesH2.test_cookie_tempesta_bad Apr 26 10:01:08 192.168.122.209 [64618.744444] Start test: t_http_rules.test_http_tables.HttpTablesTestMultipleCookiesH2.test_cookie_tempesta_bad_2 Apr 26 10:01:09 192.168.122.209 [64619.762460] [tdb] Start Tempesta DB Apr 26 10:01:09 192.168.122.209 [64619.894049] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:01:11 192.168.122.209 [64621.818517] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64621.818517] Maybe that's fine, but it's worth checking the [64621.818517] config - if there is no relations between the [64621.818517] names, then host name confusion attack is possible. Apr 26 10:01:11 192.168.122.209 [64622.065360] [tempesta fw] Configuration processing is completed. Apr 26 10:01:11 192.168.122.209 [64622.121118] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:01:11 192.168.122.209 [64622.527985] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:01:11 192.168.122.209 [64622.553390] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:01:11 192.168.122.209 [64622.583567] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:01:12 192.168.122.209 [64622.673287] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:01:12 192.168.122.209 [64622.675093] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:01:12 192.168.122.209 [64622.713236] [tempesta fw] Tempesta FW is ready Apr 26 10:01:12 192.168.122.209 [64622.916484] [tempesta fw] Warning: request has been filtered out via http table: 127.0.0.2 Apr 26 10:01:12 192.168.122.209 [64623.463466] [tdb] Close table 'client0.tdb' Apr 26 10:01:13 192.168.122.209 [64623.656109] [tdb] Close table 'sessions0.tdb' Apr 26 10:01:16 192.168.122.209 [64626.811100] [tdb] Close table 'cache0.tdb' Apr 26 10:01:16 192.168.122.209 [64627.047889] [tdb] Close table 'filter0.tdb' Apr 26 10:01:16 192.168.122.209 [64627.048319] [tempesta fw] modules are stopped Apr 26 10:01:16 192.168.122.209 [64627.286533] [tempesta fw] exiting... Apr 26 10:01:16 192.168.122.209 [64627.406839] [tdb] Shutdown Tempesta DB Apr 26 10:01:17 192.168.122.209 [64627.618222] End test: t_http_rules.test_http_tables.HttpTablesTestMultipleCookiesH2.test_cookie_tempesta_bad_2 Apr 26 10:01:17 192.168.122.209 [64627.630101] Start test: t_http_rules.test_http_tables.HttpTablesTestMultipleCookiesH2.test_cookie_tempesta_good Apr 26 10:01:18 192.168.122.209 [64628.651900] [tdb] Start Tempesta DB Apr 26 10:01:18 192.168.122.209 [64628.793172] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:01:20 192.168.122.209 [64630.650268] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64630.650268] Maybe that's fine, but it's worth checking the [64630.650268] config - if there is no relations between the [64630.650268] names, then host name confusion attack is possible. Apr 26 10:01:20 192.168.122.209 [64630.873469] [tempesta fw] Configuration processing is completed. Apr 26 10:01:20 192.168.122.209 [64630.925957] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:01:20 192.168.122.209 [64631.332148] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:01:20 192.168.122.209 [64631.357644] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:01:20 192.168.122.209 [64631.385288] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:01:20 192.168.122.209 [64631.481393] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:01:20 192.168.122.209 [64631.483188] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:01:20 192.168.122.209 [64631.521335] [tempesta fw] Tempesta FW is ready Apr 26 10:01:21 192.168.122.209 [64632.347230] [tdb] Close table 'client0.tdb' Apr 26 10:01:21 192.168.122.209 [64632.526399] [tdb] Close table 'sessions0.tdb' Apr 26 10:01:25 192.168.122.209 [64635.689962] [tdb] Close table 'cache0.tdb' Apr 26 10:01:25 192.168.122.209 [64635.936472] [tdb] Close table 'filter0.tdb' Apr 26 10:01:25 192.168.122.209 [64635.936892] [tempesta fw] modules are stopped Apr 26 10:01:25 192.168.122.209 [64636.218329] [tempesta fw] exiting... Apr 26 10:01:25 192.168.122.209 [64636.337320] [tdb] Shutdown Tempesta DB Apr 26 10:01:25 192.168.122.209 [64636.559779] End test: t_http_rules.test_http_tables.HttpTablesTestMultipleCookiesH2.test_cookie_tempesta_good Apr 26 10:01:25 192.168.122.209 [64636.569439] Start test: t_http_rules.test_http_tables.HttpTablesTestMultipleCookiesH2.test_cookie_tempesta_good_is_last Apr 26 10:01:26 192.168.122.209 [64637.591799] [tdb] Start Tempesta DB Apr 26 10:01:27 192.168.122.209 [64637.730596] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:01:29 192.168.122.209 [64639.658764] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64639.658764] Maybe that's fine, but it's worth checking the [64639.658764] config - if there is no relations between the [64639.658764] names, then host name confusion attack is possible. Apr 26 10:01:29 192.168.122.209 [64639.897557] [tempesta fw] Configuration processing is completed. Apr 26 10:01:29 192.168.122.209 [64639.958677] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:01:29 192.168.122.209 [64640.365534] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:01:29 192.168.122.209 [64640.391145] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:01:29 192.168.122.209 [64640.415962] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:01:29 192.168.122.209 [64640.553511] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:01:29 192.168.122.209 [64640.555315] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:01:29 192.168.122.209 [64640.593444] [tempesta fw] Tempesta FW is ready Apr 26 10:01:30 192.168.122.209 [64641.402390] [tdb] Close table 'client0.tdb' Apr 26 10:01:30 192.168.122.209 [64641.586513] [tdb] Close table 'sessions0.tdb' Apr 26 10:01:34 192.168.122.209 [64644.755028] [tdb] Close table 'cache0.tdb' Apr 26 10:01:34 192.168.122.209 [64645.004774] [tdb] Close table 'filter0.tdb' Apr 26 10:01:34 192.168.122.209 [64645.005212] [tempesta fw] modules are stopped Apr 26 10:01:34 192.168.122.209 [64645.306093] [tempesta fw] exiting... Apr 26 10:01:34 192.168.122.209 [64645.427916] [tdb] Shutdown Tempesta DB Apr 26 10:01:35 192.168.122.209 [64645.639417] End test: t_http_rules.test_http_tables.HttpTablesTestMultipleCookiesH2.test_cookie_tempesta_good_is_last Apr 26 10:01:35 192.168.122.209 [64645.651296] Start test: t_http_rules.test_http_tables.HttpTablesTestMultipleCookiesHttp.test_cookie_good_prefix Apr 26 10:01:36 192.168.122.209 [64646.725396] [tdb] Start Tempesta DB Apr 26 10:01:36 192.168.122.209 [64646.854932] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:01:38 192.168.122.209 [64648.778985] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64648.778985] Maybe that's fine, but it's worth checking the [64648.778985] config - if there is no relations between the [64648.778985] names, then host name confusion attack is possible. Apr 26 10:01:38 192.168.122.209 [64649.009974] [tempesta fw] Configuration processing is completed. Apr 26 10:01:38 192.168.122.209 [64649.068934] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:01:38 192.168.122.209 [64649.474733] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:01:38 192.168.122.209 [64649.500113] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:01:38 192.168.122.209 [64649.525558] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:01:39 192.168.122.209 [64649.621605] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:01:39 192.168.122.209 [64649.623423] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:01:39 192.168.122.209 [64649.665567] [tempesta fw] Tempesta FW is ready Apr 26 10:01:39 192.168.122.209 [64650.449550] [tdb] Close table 'client0.tdb' Apr 26 10:01:40 192.168.122.209 [64650.627772] [tdb] Close table 'sessions0.tdb' Apr 26 10:01:43 192.168.122.209 [64653.807086] [tdb] Close table 'cache0.tdb' Apr 26 10:01:43 192.168.122.209 [64654.031667] [tdb] Close table 'filter0.tdb' Apr 26 10:01:43 192.168.122.209 [64654.032067] [tempesta fw] modules are stopped Apr 26 10:01:43 192.168.122.209 [64654.321532] [tempesta fw] exiting... Apr 26 10:01:43 192.168.122.209 [64654.458808] [tdb] Shutdown Tempesta DB Apr 26 10:01:44 192.168.122.209 [64654.695880] End test: t_http_rules.test_http_tables.HttpTablesTestMultipleCookiesHttp.test_cookie_good_prefix Apr 26 10:01:44 192.168.122.209 [64654.710091] Start test: t_http_rules.test_http_tables.HttpTablesTestMultipleCookiesHttp.test_cookie_good_suffix Apr 26 10:01:45 192.168.122.209 [64655.734184] [tdb] Start Tempesta DB Apr 26 10:01:45 192.168.122.209 [64655.867693] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:01:47 192.168.122.209 [64657.762891] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64657.762891] Maybe that's fine, but it's worth checking the [64657.762891] config - if there is no relations between the [64657.762891] names, then host name confusion attack is possible. Apr 26 10:01:47 192.168.122.209 [64658.001732] [tempesta fw] Configuration processing is completed. Apr 26 10:01:47 192.168.122.209 [64658.060560] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:01:47 192.168.122.209 [64658.464763] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:01:47 192.168.122.209 [64658.490459] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:01:47 192.168.122.209 [64658.516346] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:01:48 192.168.122.209 [64658.633699] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:01:48 192.168.122.209 [64658.635505] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:01:48 192.168.122.209 [64658.677651] [tempesta fw] Tempesta FW is ready Apr 26 10:01:48 192.168.122.209 [64659.479033] [tdb] Close table 'client0.tdb' Apr 26 10:01:49 192.168.122.209 [64659.661186] [tdb] Close table 'sessions0.tdb' Apr 26 10:01:52 192.168.122.209 [64662.795535] [tdb] Close table 'cache0.tdb' Apr 26 10:01:52 192.168.122.209 [64663.034331] [tdb] Close table 'filter0.tdb' Apr 26 10:01:52 192.168.122.209 [64663.034771] [tempesta fw] modules are stopped Apr 26 10:01:52 192.168.122.209 [64663.334869] [tempesta fw] exiting... Apr 26 10:01:52 192.168.122.209 [64663.492121] [tdb] Shutdown Tempesta DB Apr 26 10:01:53 192.168.122.209 [64663.681638] End test: t_http_rules.test_http_tables.HttpTablesTestMultipleCookiesHttp.test_cookie_good_suffix Apr 26 10:01:53 192.168.122.209 [64663.703068] Start test: t_http_rules.test_http_tables.HttpTablesTestMultipleCookiesHttp.test_cookie_no_rules_matched Apr 26 10:01:54 192.168.122.209 [64664.678198] [tdb] Start Tempesta DB Apr 26 10:01:54 192.168.122.209 [64664.810920] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:01:56 192.168.122.209 [64666.707124] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64666.707124] Maybe that's fine, but it's worth checking the [64666.707124] config - if there is no relations between the [64666.707124] names, then host name confusion attack is possible. Apr 26 10:01:56 192.168.122.209 [64666.949882] [tempesta fw] Configuration processing is completed. Apr 26 10:01:56 192.168.122.209 [64667.018555] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:01:56 192.168.122.209 [64667.426090] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:01:56 192.168.122.209 [64667.451755] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:01:56 192.168.122.209 [64667.476631] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:01:56 192.168.122.209 [64667.577825] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:01:56 192.168.122.209 [64667.579607] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:01:56 192.168.122.209 [64667.617767] [tempesta fw] Tempesta FW is ready Apr 26 10:01:57 192.168.122.209 [64668.400216] [tdb] Close table 'client0.tdb' Apr 26 10:01:57 192.168.122.209 [64668.571741] [tdb] Close table 'sessions0.tdb' Apr 26 10:02:01 192.168.122.209 [64671.753068] [tdb] Close table 'cache0.tdb' Apr 26 10:02:01 192.168.122.209 [64671.990517] [tdb] Close table 'filter0.tdb' Apr 26 10:02:01 192.168.122.209 [64671.990944] [tempesta fw] modules are stopped Apr 26 10:02:01 192.168.122.209 [64672.268705] [tempesta fw] exiting... Apr 26 10:02:01 192.168.122.209 [64672.361528] [tdb] Shutdown Tempesta DB Apr 26 10:02:01 192.168.122.209 [64672.550225] End test: t_http_rules.test_http_tables.HttpTablesTestMultipleCookiesHttp.test_cookie_no_rules_matched Apr 26 10:02:01 192.168.122.209 [64672.563034] Start test: t_http_rules.test_http_tables.HttpTablesTestMultipleCookiesHttp.test_cookie_tempesta_bad Apr 26 10:02:02 192.168.122.209 [64673.563278] [tdb] Start Tempesta DB Apr 26 10:02:03 192.168.122.209 [64673.700922] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:02:04 192.168.122.209 [64675.559194] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64675.559194] Maybe that's fine, but it's worth checking the [64675.559194] config - if there is no relations between the [64675.559194] names, then host name confusion attack is possible. Apr 26 10:02:05 192.168.122.209 [64675.786015] [tempesta fw] Configuration processing is completed. Apr 26 10:02:05 192.168.122.209 [64675.840457] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:02:05 192.168.122.209 [64676.238233] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:02:05 192.168.122.209 [64676.263849] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:02:05 192.168.122.209 [64676.289642] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:02:05 192.168.122.209 [64676.381925] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:02:05 192.168.122.209 [64676.383700] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:02:05 192.168.122.209 [64676.429855] [tempesta fw] Tempesta FW is ready Apr 26 10:02:05 192.168.122.209 [64676.587874] [tempesta fw] Warning: request has been filtered out via http table: 127.0.0.2 Apr 26 10:02:06 192.168.122.209 [64677.142560] [tdb] Close table 'client0.tdb' Apr 26 10:02:06 192.168.122.209 [64677.329248] [tdb] Close table 'sessions0.tdb' Apr 26 10:02:09 192.168.122.209 [64680.467435] [tdb] Close table 'cache0.tdb' Apr 26 10:02:10 192.168.122.209 [64680.740302] [tdb] Close table 'filter0.tdb' Apr 26 10:02:10 192.168.122.209 [64680.740905] [tempesta fw] modules are stopped Apr 26 10:02:10 192.168.122.209 [64681.014736] [tempesta fw] exiting... Apr 26 10:02:10 192.168.122.209 [64681.110984] [tdb] Shutdown Tempesta DB Apr 26 10:02:10 192.168.122.209 [64681.327592] End test: t_http_rules.test_http_tables.HttpTablesTestMultipleCookiesHttp.test_cookie_tempesta_bad Apr 26 10:02:10 192.168.122.209 [64681.341498] Start test: t_http_rules.test_http_tables.HttpTablesTestMultipleCookiesHttp.test_cookie_tempesta_bad_2 Apr 26 10:02:11 192.168.122.209 [64682.366918] [tdb] Start Tempesta DB Apr 26 10:02:11 192.168.122.209 [64682.513507] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:02:13 192.168.122.209 [64684.535318] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64684.535318] Maybe that's fine, but it's worth checking the [64684.535318] config - if there is no relations between the [64684.535318] names, then host name confusion attack is possible. Apr 26 10:02:14 192.168.122.209 [64684.770091] [tempesta fw] Configuration processing is completed. Apr 26 10:02:14 192.168.122.209 [64684.826561] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:02:14 192.168.122.209 [64685.246131] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:02:14 192.168.122.209 [64685.273305] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:02:14 192.168.122.209 [64685.305442] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:02:14 192.168.122.209 [64685.386035] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:02:14 192.168.122.209 [64685.387896] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:02:14 192.168.122.209 [64685.437978] [tempesta fw] Tempesta FW is ready Apr 26 10:02:14 192.168.122.209 [64685.599564] [tempesta fw] Warning: request has been filtered out via http table: 127.0.0.2 Apr 26 10:02:15 192.168.122.209 [64686.185847] [tdb] Close table 'client0.tdb' Apr 26 10:02:15 192.168.122.209 [64686.371382] [tdb] Close table 'sessions0.tdb' Apr 26 10:02:18 192.168.122.209 [64689.593512] [tdb] Close table 'cache0.tdb' Apr 26 10:02:19 192.168.122.209 [64689.844339] [tdb] Close table 'filter0.tdb' Apr 26 10:02:19 192.168.122.209 [64689.844779] [tempesta fw] modules are stopped Apr 26 10:02:19 192.168.122.209 [64690.132709] [tempesta fw] exiting... Apr 26 10:02:19 192.168.122.209 [64690.229820] [tdb] Shutdown Tempesta DB Apr 26 10:02:19 192.168.122.209 [64690.416713] End test: t_http_rules.test_http_tables.HttpTablesTestMultipleCookiesHttp.test_cookie_tempesta_bad_2 Apr 26 10:02:19 192.168.122.209 [64690.428440] Start test: t_http_rules.test_http_tables.HttpTablesTestMultipleCookiesHttp.test_cookie_tempesta_good Apr 26 10:02:20 192.168.122.209 [64691.514573] [tdb] Start Tempesta DB Apr 26 10:02:21 192.168.122.209 [64691.636328] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:02:22 192.168.122.209 [64693.479387] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64693.479387] Maybe that's fine, but it's worth checking the [64693.479387] config - if there is no relations between the [64693.479387] names, then host name confusion attack is possible. Apr 26 10:02:23 192.168.122.209 [64693.730173] [tempesta fw] Configuration processing is completed. Apr 26 10:02:23 192.168.122.209 [64693.781297] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:02:23 192.168.122.209 [64694.194502] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:02:23 192.168.122.209 [64694.220413] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:02:23 192.168.122.209 [64694.247717] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:02:23 192.168.122.209 [64694.370159] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:02:23 192.168.122.209 [64694.372020] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:02:23 192.168.122.209 [64694.410090] [tempesta fw] Tempesta FW is ready Apr 26 10:02:24 192.168.122.209 [64695.189106] [tdb] Close table 'client0.tdb' Apr 26 10:02:24 192.168.122.209 [64695.371992] [tdb] Close table 'sessions0.tdb' Apr 26 10:02:27 192.168.122.209 [64698.544652] [tdb] Close table 'cache0.tdb' Apr 26 10:02:28 192.168.122.209 [64698.773281] [tdb] Close table 'filter0.tdb' Apr 26 10:02:28 192.168.122.209 [64698.773708] [tempesta fw] modules are stopped Apr 26 10:02:28 192.168.122.209 [64699.022431] [tempesta fw] exiting... Apr 26 10:02:28 192.168.122.209 [64699.154823] [tdb] Shutdown Tempesta DB Apr 26 10:02:28 192.168.122.209 [64699.376072] End test: t_http_rules.test_http_tables.HttpTablesTestMultipleCookiesHttp.test_cookie_tempesta_good Apr 26 10:02:28 192.168.122.209 [64699.385336] Start test: t_http_rules.test_http_tables.HttpTablesTestMultipleCookiesHttp.test_cookie_tempesta_good_is_last Apr 26 10:02:29 192.168.122.209 [64700.424990] [tdb] Start Tempesta DB Apr 26 10:02:29 192.168.122.209 [64700.559561] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:02:31 192.168.122.209 [64702.419490] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64702.419490] Maybe that's fine, but it's worth checking the [64702.419490] config - if there is no relations between the [64702.419490] names, then host name confusion attack is possible. Apr 26 10:02:32 192.168.122.209 [64702.674309] [tempesta fw] Configuration processing is completed. Apr 26 10:02:32 192.168.122.209 [64702.730131] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:02:32 192.168.122.209 [64703.130640] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:02:32 192.168.122.209 [64703.156275] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:02:32 192.168.122.209 [64703.181984] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:02:32 192.168.122.209 [64703.290243] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:02:32 192.168.122.209 [64703.292081] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:02:32 192.168.122.209 [64703.330191] [tempesta fw] Tempesta FW is ready Apr 26 10:02:33 192.168.122.209 [64704.130068] [tdb] Close table 'client0.tdb' Apr 26 10:02:33 192.168.122.209 [64704.330427] [tdb] Close table 'sessions0.tdb' Apr 26 10:02:36 192.168.122.209 [64707.535166] [tdb] Close table 'cache0.tdb' Apr 26 10:02:37 192.168.122.209 [64707.777247] [tdb] Close table 'filter0.tdb' Apr 26 10:02:37 192.168.122.209 [64707.777678] [tempesta fw] modules are stopped Apr 26 10:02:37 192.168.122.209 [64708.050817] [tempesta fw] exiting... Apr 26 10:02:37 192.168.122.209 [64708.167652] [tdb] Shutdown Tempesta DB Apr 26 10:02:37 192.168.122.209 [64708.378178] End test: t_http_rules.test_http_tables.HttpTablesTestMultipleCookiesHttp.test_cookie_tempesta_good_is_last Apr 26 10:02:37 192.168.122.209 [64708.390695] Start test: t_http_rules.test_match_duplicated_headers.DuplicatedHeadersMatchTest.test_match_fail Apr 26 10:02:38 192.168.122.209 [64709.418603] [tdb] Start Tempesta DB Apr 26 10:02:38 192.168.122.209 [64709.544127] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:02:40 192.168.122.209 [64711.183604] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64711.183604] Maybe that's fine, but it's worth checking the [64711.183604] config - if there is no relations between the [64711.183604] names, then host name confusion attack is possible. Apr 26 10:02:40 192.168.122.209 [64711.390682] [tempesta fw] Configuration processing is completed. Apr 26 10:02:40 192.168.122.209 [64711.440546] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:02:41 192.168.122.209 [64711.841641] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:02:41 192.168.122.209 [64711.868016] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:02:41 192.168.122.209 [64711.894518] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:02:41 192.168.122.209 [64711.938386] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:02:41 192.168.122.209 [64711.940141] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:02:41 192.168.122.209 [64711.994242] [tempesta fw] Tempesta FW is ready Apr 26 10:02:41 192.168.122.209 [64712.160447] [tempesta fw] Warning: request has been filtered out via http table: 127.0.0.2 Apr 26 10:02:41 192.168.122.209 [64712.585003] [tdb] Close table 'client0.tdb' Apr 26 10:02:42 192.168.122.209 [64712.764659] [tdb] Close table 'sessions0.tdb' Apr 26 10:02:45 192.168.122.209 [64715.974384] [tdb] Close table 'cache0.tdb' Apr 26 10:02:45 192.168.122.209 [64716.209826] [tdb] Close table 'filter0.tdb' Apr 26 10:02:45 192.168.122.209 [64716.210284] [tempesta fw] modules are stopped Apr 26 10:02:45 192.168.122.209 [64716.459143] [tempesta fw] exiting... Apr 26 10:02:45 192.168.122.209 [64716.611279] [tdb] Shutdown Tempesta DB Apr 26 10:02:46 192.168.122.209 [64716.793091] End test: t_http_rules.test_match_duplicated_headers.DuplicatedHeadersMatchTest.test_match_fail Apr 26 10:02:46 192.168.122.209 [64716.810745] Start test: t_http_rules.test_match_duplicated_headers.DuplicatedHeadersMatchTest.test_match_success Apr 26 10:02:47 192.168.122.209 [64717.861422] [tdb] Start Tempesta DB Apr 26 10:02:47 192.168.122.209 [64718.000800] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:02:48 192.168.122.209 [64719.567952] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64719.567952] Maybe that's fine, but it's worth checking the [64719.567952] config - if there is no relations between the [64719.567952] names, then host name confusion attack is possible. Apr 26 10:02:49 192.168.122.209 [64719.746471] [tempesta fw] Configuration processing is completed. Apr 26 10:02:49 192.168.122.209 [64719.797999] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:02:49 192.168.122.209 [64720.197142] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:02:49 192.168.122.209 [64720.222733] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:02:49 192.168.122.209 [64720.248245] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:02:49 192.168.122.209 [64720.294445] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:02:49 192.168.122.209 [64720.296177] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:02:49 192.168.122.209 [64720.334396] [tempesta fw] Tempesta FW is ready Apr 26 10:02:50 192.168.122.209 [64720.968604] [tdb] Close table 'client0.tdb' Apr 26 10:02:50 192.168.122.209 [64721.152997] [tdb] Close table 'sessions0.tdb' Apr 26 10:02:53 192.168.122.209 [64724.333569] [tdb] Close table 'cache0.tdb' Apr 26 10:02:53 192.168.122.209 [64724.550645] [tdb] Close table 'filter0.tdb' Apr 26 10:02:53 192.168.122.209 [64724.551073] [tempesta fw] modules are stopped Apr 26 10:02:54 192.168.122.209 [64724.787296] [tempesta fw] exiting... Apr 26 10:02:54 192.168.122.209 [64724.892189] [tdb] Shutdown Tempesta DB Apr 26 10:02:54 192.168.122.209 [64725.125605] End test: t_http_rules.test_match_duplicated_headers.DuplicatedHeadersMatchTest.test_match_success Apr 26 10:02:54 192.168.122.209 [64725.135795] Start test: t_ipv6.test_ipv6.TestIPv6H2.test_ipv4_to_ipv6 Apr 26 10:02:55 192.168.122.209 [64726.202506] [tdb] Start Tempesta DB Apr 26 10:02:55 192.168.122.209 [64726.334031] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:02:57 192.168.122.209 [64728.047891] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64728.047891] Maybe that's fine, but it's worth checking the [64728.047891] config - if there is no relations between the [64728.047891] names, then host name confusion attack is possible. Apr 26 10:02:57 192.168.122.209 [64728.178604] [tempesta fw] Configuration processing is completed. Apr 26 10:02:57 192.168.122.209 [64728.235274] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:02:58 192.168.122.209 [64728.639659] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:02:58 192.168.122.209 [64728.665280] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:02:58 192.168.122.209 [64728.690407] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:02:58 192.168.122.209 [64728.750548] [tempesta fw] Open listen socket on: [::1]:443 Apr 26 10:02:58 192.168.122.209 [64728.751895] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 10:02:58 192.168.122.209 [64728.806485] [tempesta fw] Tempesta FW is ready Apr 26 10:03:02 192.168.122.209 [64733.204762] [tdb] Close table 'client0.tdb' Apr 26 10:03:02 192.168.122.209 [64733.394276] [tdb] Close table 'sessions0.tdb' Apr 26 10:03:06 192.168.122.209 [64736.627227] [tdb] Close table 'cache0.tdb' Apr 26 10:03:06 192.168.122.209 [64736.864332] [tdb] Close table 'filter0.tdb' Apr 26 10:03:06 192.168.122.209 [64736.864769] [tempesta fw] modules are stopped Apr 26 10:03:06 192.168.122.209 [64737.151155] [tempesta fw] exiting... Apr 26 10:03:06 192.168.122.209 [64737.299559] [tdb] Shutdown Tempesta DB Apr 26 10:03:06 192.168.122.209 [64737.516049] End test: t_ipv6.test_ipv6.TestIPv6H2.test_ipv4_to_ipv6 Apr 26 10:03:06 192.168.122.209 [64737.524545] Start test: t_ipv6.test_ipv6.TestIPv6H2.test_ipv6_to_ipv4 Apr 26 10:03:08 192.168.122.209 [64738.646372] [tdb] Start Tempesta DB Apr 26 10:03:08 192.168.122.209 [64738.777029] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:03:09 192.168.122.209 [64740.504056] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64740.504056] Maybe that's fine, but it's worth checking the [64740.504056] config - if there is no relations between the [64740.504056] names, then host name confusion attack is possible. Apr 26 10:03:10 192.168.122.209 [64740.618746] [tempesta fw] Configuration processing is completed. Apr 26 10:03:10 192.168.122.209 [64740.678192] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:03:10 192.168.122.209 [64741.125913] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:03:10 192.168.122.209 [64741.154367] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:03:10 192.168.122.209 [64741.182742] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:03:10 192.168.122.209 [64741.246713] [tempesta fw] Open listen socket on: [::1]:443 Apr 26 10:03:10 192.168.122.209 [64741.248437] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 10:03:10 192.168.122.209 [64741.290640] [tempesta fw] Tempesta FW is ready Apr 26 10:03:15 192.168.122.209 [64746.428260] [tdb] Close table 'client0.tdb' Apr 26 10:03:16 192.168.122.209 [64746.621163] [tdb] Close table 'sessions0.tdb' Apr 26 10:03:19 192.168.122.209 [64749.805928] [tdb] Close table 'cache0.tdb' Apr 26 10:03:19 192.168.122.209 [64750.043846] [tdb] Close table 'filter0.tdb' Apr 26 10:03:19 192.168.122.209 [64750.044260] [tempesta fw] modules are stopped Apr 26 10:03:19 192.168.122.209 [64750.271499] [tempesta fw] exiting... Apr 26 10:03:19 192.168.122.209 [64750.380683] [tdb] Shutdown Tempesta DB Apr 26 10:03:19 192.168.122.209 [64750.566840] End test: t_ipv6.test_ipv6.TestIPv6H2.test_ipv6_to_ipv4 Apr 26 10:03:19 192.168.122.209 [64750.575914] Start test: t_ipv6.test_ipv6.TestIPv6H2.test_ipv6_to_ipv6 Apr 26 10:03:20 192.168.122.209 [64751.616286] [tdb] Start Tempesta DB Apr 26 10:03:21 192.168.122.209 [64751.751951] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:03:22 192.168.122.209 [64753.468147] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64753.468147] Maybe that's fine, but it's worth checking the [64753.468147] config - if there is no relations between the [64753.468147] names, then host name confusion attack is possible. Apr 26 10:03:22 192.168.122.209 [64753.606847] [tempesta fw] Configuration processing is completed. Apr 26 10:03:23 192.168.122.209 [64753.669330] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:03:23 192.168.122.209 [64754.072633] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:03:23 192.168.122.209 [64754.098769] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:03:23 192.168.122.209 [64754.126228] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:03:23 192.168.122.209 [64754.202855] [tempesta fw] Open listen socket on: [::1]:443 Apr 26 10:03:23 192.168.122.209 [64754.204608] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 10:03:23 192.168.122.209 [64754.242795] [tempesta fw] Tempesta FW is ready Apr 26 10:03:28 192.168.122.209 [64758.692524] [tdb] Close table 'client0.tdb' Apr 26 10:03:28 192.168.122.209 [64758.899674] [tdb] Close table 'sessions0.tdb' Apr 26 10:03:31 192.168.122.209 [64762.044852] [tdb] Close table 'cache0.tdb' Apr 26 10:03:31 192.168.122.209 [64762.272432] [tdb] Close table 'filter0.tdb' Apr 26 10:03:31 192.168.122.209 [64762.272889] [tempesta fw] modules are stopped Apr 26 10:03:31 192.168.122.209 [64762.491947] [tempesta fw] exiting... Apr 26 10:03:32 192.168.122.209 [64762.626270] [tdb] Shutdown Tempesta DB Apr 26 10:03:32 192.168.122.209 [64762.852477] End test: t_ipv6.test_ipv6.TestIPv6H2.test_ipv6_to_ipv6 Apr 26 10:03:32 192.168.122.209 [64762.868959] Start test: t_ipv6.test_ipv6.TestIPv6Https.test_ipv4_to_ipv6 Apr 26 10:03:33 192.168.122.209 [64763.896398] [tdb] Start Tempesta DB Apr 26 10:03:33 192.168.122.209 [64764.025727] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:03:35 192.168.122.209 [64765.700312] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64765.700312] Maybe that's fine, but it's worth checking the [64765.700312] config - if there is no relations between the [64765.700312] names, then host name confusion attack is possible. Apr 26 10:03:35 192.168.122.209 [64765.811045] [tempesta fw] Configuration processing is completed. Apr 26 10:03:35 192.168.122.209 [64765.863030] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:03:35 192.168.122.209 [64766.267991] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:03:35 192.168.122.209 [64766.298700] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:03:35 192.168.122.209 [64766.326073] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:03:35 192.168.122.209 [64766.407000] [tempesta fw] Open listen socket on: [::1]:443 Apr 26 10:03:35 192.168.122.209 [64766.408716] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 10:03:35 192.168.122.209 [64766.462933] [tempesta fw] Tempesta FW is ready Apr 26 10:03:40 192.168.122.209 [64771.004341] [tdb] Close table 'client0.tdb' Apr 26 10:03:40 192.168.122.209 [64771.183680] [tdb] Close table 'sessions0.tdb' Apr 26 10:03:43 192.168.122.209 [64774.339227] [tdb] Close table 'cache0.tdb' Apr 26 10:03:43 192.168.122.209 [64774.572907] [tdb] Close table 'filter0.tdb' Apr 26 10:03:43 192.168.122.209 [64774.573319] [tempesta fw] modules are stopped Apr 26 10:03:44 192.168.122.209 [64774.866416] [tempesta fw] exiting... Apr 26 10:03:44 192.168.122.209 [64775.017243] [tdb] Shutdown Tempesta DB Apr 26 10:03:44 192.168.122.209 [64775.239794] End test: t_ipv6.test_ipv6.TestIPv6Https.test_ipv4_to_ipv6 Apr 26 10:03:44 192.168.122.209 [64775.252390] Start test: t_ipv6.test_ipv6.TestIPv6Https.test_ipv6_to_ipv4 Apr 26 10:03:45 192.168.122.209 [64776.334646] [tdb] Start Tempesta DB Apr 26 10:03:45 192.168.122.209 [64776.468039] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:03:47 192.168.122.209 [64778.168427] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64778.168427] Maybe that's fine, but it's worth checking the [64778.168427] config - if there is no relations between the [64778.168427] names, then host name confusion attack is possible. Apr 26 10:03:47 192.168.122.209 [64778.303272] [tempesta fw] Configuration processing is completed. Apr 26 10:03:47 192.168.122.209 [64778.353952] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:03:48 192.168.122.209 [64778.755367] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:03:48 192.168.122.209 [64778.794666] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:03:48 192.168.122.209 [64778.820546] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:03:48 192.168.122.209 [64778.879140] [tempesta fw] Open listen socket on: [::1]:443 Apr 26 10:03:48 192.168.122.209 [64778.880890] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 10:03:48 192.168.122.209 [64778.931040] [tempesta fw] Tempesta FW is ready Apr 26 10:03:52 192.168.122.209 [64783.521923] [tdb] Close table 'client0.tdb' Apr 26 10:03:53 192.168.122.209 [64783.705594] [tdb] Close table 'sessions0.tdb' Apr 26 10:03:56 192.168.122.209 [64786.903906] [tdb] Close table 'cache0.tdb' Apr 26 10:03:56 192.168.122.209 [64787.131228] [tdb] Close table 'filter0.tdb' Apr 26 10:03:56 192.168.122.209 [64787.131641] [tempesta fw] modules are stopped Apr 26 10:03:56 192.168.122.209 [64787.354835] [tempesta fw] exiting... Apr 26 10:03:56 192.168.122.209 [64787.460679] [tdb] Shutdown Tempesta DB Apr 26 10:03:57 192.168.122.209 [64787.673251] End test: t_ipv6.test_ipv6.TestIPv6Https.test_ipv6_to_ipv4 Apr 26 10:03:57 192.168.122.209 [64787.698685] Start test: t_ipv6.test_ipv6.TestIPv6Https.test_ipv6_to_ipv6 Apr 26 10:03:58 192.168.122.209 [64788.750500] [tdb] Start Tempesta DB Apr 26 10:03:58 192.168.122.209 [64788.884405] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:04:00 192.168.122.209 [64790.736638] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64790.736638] Maybe that's fine, but it's worth checking the [64790.736638] config - if there is no relations between the [64790.736638] names, then host name confusion attack is possible. Apr 26 10:04:00 192.168.122.209 [64790.875349] [tempesta fw] Configuration processing is completed. Apr 26 10:04:00 192.168.122.209 [64790.933305] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:04:00 192.168.122.209 [64791.345817] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:04:00 192.168.122.209 [64791.371501] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:04:00 192.168.122.209 [64791.397728] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:04:00 192.168.122.209 [64791.459316] [tempesta fw] Open listen socket on: [::1]:443 Apr 26 10:04:00 192.168.122.209 [64791.461067] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 10:04:00 192.168.122.209 [64791.507233] [tempesta fw] Tempesta FW is ready Apr 26 10:04:05 192.168.122.209 [64796.227148] [tdb] Close table 'client0.tdb' Apr 26 10:04:05 192.168.122.209 [64796.429219] [tdb] Close table 'sessions0.tdb' Apr 26 10:04:09 192.168.122.209 [64799.654524] [tdb] Close table 'cache0.tdb' Apr 26 10:04:09 192.168.122.209 [64799.908002] [tdb] Close table 'filter0.tdb' Apr 26 10:04:09 192.168.122.209 [64799.908455] [tempesta fw] modules are stopped Apr 26 10:04:09 192.168.122.209 [64800.188917] [tempesta fw] exiting... Apr 26 10:04:09 192.168.122.209 [64800.313630] [tdb] Shutdown Tempesta DB Apr 26 10:04:09 192.168.122.209 [64800.525288] End test: t_ipv6.test_ipv6.TestIPv6Https.test_ipv6_to_ipv6 Apr 26 10:04:09 192.168.122.209 [64800.539682] Start test: t_ja5.test_ja5_filters.TestConfigJa5hInvalidTableSize.test_config Apr 26 10:04:11 192.168.122.209 [64801.629119] [tdb] Start Tempesta DB Apr 26 10:04:11 192.168.122.209 [64801.761999] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:04:12 192.168.122.209 [64803.428694] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64803.428694] Maybe that's fine, but it's worth checking the [64803.428694] config - if there is no relations between the [64803.428694] names, then host name confusion attack is possible. Apr 26 10:04:12 192.168.122.209 [64803.571484] [tempesta fw] Configuration processing is completed. Apr 26 10:04:12 192.168.122.209 [64803.591372] [tdb] ERROR: Bad table size: 500 Apr 26 10:04:12 192.168.122.209 [64803.592624] [tempesta fw] ERROR: Unable to start module 'http': -12 Apr 26 10:04:12 192.168.122.209 [64803.594332] [tempesta fw] modules are stopped Apr 26 10:04:12 192.168.122.209 [64803.595597] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 10:04:13 192.168.122.209 [64803.973573] [tempesta fw] exiting... Apr 26 10:04:13 192.168.122.209 [64804.109091] [tdb] Shutdown Tempesta DB Apr 26 10:04:13 192.168.122.209 [64804.516834] End test: t_ja5.test_ja5_filters.TestConfigJa5hInvalidTableSize.test_config Apr 26 10:04:13 192.168.122.209 [64804.526955] Start test: t_ja5.test_ja5_filters.TestConfigJa5hInvalidValue.test_config Apr 26 10:04:14 192.168.122.209 [64805.508329] [tdb] Start Tempesta DB Apr 26 10:04:15 192.168.122.209 [64805.644165] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:04:15 192.168.122.209 [64806.304699] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64806.304699] Maybe that's fine, but it's worth checking the [64806.304699] config - if there is no relations between the [64806.304699] names, then host name confusion attack is possible. Apr 26 10:04:15 192.168.122.209 [64806.363763] [tempesta fw] ERROR: Failed to parse hash entry in ja5 section: invalid hash value invalid_hash Apr 26 10:04:15 192.168.122.209 [64806.363774] [tempesta fw] ERROR: configuration parsing error: [64806.363774] 10: ja5h {hash invalid_hash 5 5;} [64806.363774] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 10:04:15 192.168.122.209 [64806.370933] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 10:04:15 192.168.122.209 [64806.590756] [tempesta fw] exiting... Apr 26 10:04:16 192.168.122.209 [64806.692121] [tdb] Shutdown Tempesta DB Apr 26 10:04:16 192.168.122.209 [64807.130215] End test: t_ja5.test_ja5_filters.TestConfigJa5hInvalidValue.test_config Apr 26 10:04:16 192.168.122.209 [64807.143374] Start test: t_ja5.test_ja5_filters.TestConfigJa5tInvalidTableSize.test_config Apr 26 10:04:17 192.168.122.209 [64808.191649] [tdb] Start Tempesta DB Apr 26 10:04:17 192.168.122.209 [64808.313178] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:04:18 192.168.122.209 [64808.996798] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64808.996798] Maybe that's fine, but it's worth checking the [64808.996798] config - if there is no relations between the [64808.996798] names, then host name confusion attack is possible. Apr 26 10:04:18 192.168.122.209 [64809.155539] [tempesta fw] Configuration processing is completed. Apr 26 10:04:18 192.168.122.209 [64809.175455] [tdb] ERROR: Bad table size: 500 Apr 26 10:04:18 192.168.122.209 [64809.176701] [tempesta fw] ERROR: Unable to start module 'tls': -12 Apr 26 10:04:18 192.168.122.209 [64809.178430] [tempesta fw] modules are stopped Apr 26 10:04:18 192.168.122.209 [64809.179708] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 10:04:18 192.168.122.209 [64809.572526] [tempesta fw] exiting... Apr 26 10:04:19 192.168.122.209 [64809.691904] [tdb] Shutdown Tempesta DB Apr 26 10:04:19 192.168.122.209 [64810.118085] End test: t_ja5.test_ja5_filters.TestConfigJa5tInvalidTableSize.test_config Apr 26 10:04:19 192.168.122.209 [64810.131933] Start test: t_ja5.test_ja5_filters.TestConfigJa5tInvalidValue.test_config Apr 26 10:04:20 192.168.122.209 [64811.089789] [tdb] Start Tempesta DB Apr 26 10:04:20 192.168.122.209 [64811.209733] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:04:21 192.168.122.209 [64811.904868] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64811.904868] Maybe that's fine, but it's worth checking the [64811.904868] config - if there is no relations between the [64811.904868] names, then host name confusion attack is possible. Apr 26 10:04:21 192.168.122.209 [64811.963862] [tempesta fw] ERROR: Failed to parse hash entry in ja5 section: invalid hash value invalid_hash Apr 26 10:04:21 192.168.122.209 [64811.963874] [tempesta fw] ERROR: configuration parsing error: [64811.963874] 10: ja5t {hash invalid_hash 5 5;} [64811.963874] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 10:04:21 192.168.122.209 [64811.971082] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 10:04:21 192.168.122.209 [64812.137022] [tempesta fw] exiting... Apr 26 10:04:21 192.168.122.209 [64812.266107] [tdb] Shutdown Tempesta DB Apr 26 10:04:22 192.168.122.209 [64812.713070] End test: t_ja5.test_ja5_filters.TestConfigJa5tInvalidValue.test_config Apr 26 10:04:22 192.168.122.209 [64812.725509] Start test: t_ja5.test_ja5_filters.TestJa5FiltersTestSuiteCiphers.test_ja5_hash_difference Apr 26 10:04:23 192.168.122.209 [64813.750058] [tdb] Start Tempesta DB Apr 26 10:04:23 192.168.122.209 [64813.885174] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:04:24 192.168.122.209 [64814.748885] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64814.748885] Maybe that's fine, but it's worth checking the [64814.748885] config - if there is no relations between the [64814.748885] names, then host name confusion attack is possible. Apr 26 10:04:24 192.168.122.209 [64815.027546] [tempesta fw] Configuration processing is completed. Apr 26 10:04:24 192.168.122.209 [64815.135352] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 10:04:24 192.168.122.209 [64815.216754] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000003038fc3d Apr 26 10:04:24 192.168.122.209 [64815.243852] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000d11db51e Apr 26 10:04:25 192.168.122.209 [64815.751657] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6070ba4 Apr 26 10:04:25 192.168.122.209 [64815.790820] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000a968d47d Apr 26 10:04:25 192.168.122.209 [64815.827671] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000007aec66b3 Apr 26 10:04:25 192.168.122.209 [64815.947596] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:04:25 192.168.122.209 [64815.991537] [tempesta fw] Tempesta FW is ready Apr 26 10:04:30 192.168.122.209 [64820.679276] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=1271f8cc2c4c0011" "ja5h=65636588000c0180" Apr 26 10:04:30 192.168.122.209 [64820.824367] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=1271f8cc2c4c0011" "ja5h=65636588000c0180" Apr 26 10:04:30 192.168.122.209 [64820.982353] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=1271f8cc2c570011" "ja5h=65636588000c0180" Apr 26 10:04:30 192.168.122.209 [64821.128722] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=1271f8cc2c570011" "ja5h=65636588000c0180" Apr 26 10:04:31 192.168.122.209 [64821.698269] [tdb] Close table 'client0.tdb' Apr 26 10:04:31 192.168.122.209 [64821.880619] [tdb] Close table 'sessions0.tdb' Apr 26 10:04:34 192.168.122.209 [64825.022132] [tdb] Close table 'cache0.tdb' Apr 26 10:04:34 192.168.122.209 [64825.272097] [tdb] Close table 'filter0.tdb' Apr 26 10:04:35 192.168.122.209 [64826.036510] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 10:04:35 192.168.122.209 [64826.036963] [tempesta fw] modules are stopped Apr 26 10:04:35 192.168.122.209 [64826.368401] [tempesta fw] exiting... Apr 26 10:04:36 192.168.122.209 [64827.178014] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 10:04:36 192.168.122.209 [64827.269948] [tdb] Shutdown Tempesta DB Apr 26 10:04:37 192.168.122.209 [64828.298143] [tdb] Start Tempesta DB Apr 26 10:04:37 192.168.122.209 [64828.435099] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:04:39 192.168.122.209 [64830.248219] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64830.248219] Maybe that's fine, but it's worth checking the [64830.248219] config - if there is no relations between the [64830.248219] names, then host name confusion attack is possible. Apr 26 10:04:39 192.168.122.209 [64830.459736] [tempesta fw] Configuration processing is completed. Apr 26 10:04:39 192.168.122.209 [64830.572144] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 10:04:40 192.168.122.209 [64830.657971] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000003038fc3d Apr 26 10:04:40 192.168.122.209 [64830.685034] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000d11db51e Apr 26 10:04:40 192.168.122.209 [64831.114809] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6070ba4 Apr 26 10:04:40 192.168.122.209 [64831.143491] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000a968d47d Apr 26 10:04:40 192.168.122.209 [64831.177603] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000007aec66b3 Apr 26 10:04:40 192.168.122.209 [64831.339831] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:04:40 192.168.122.209 [64831.439696] [tempesta fw] Tempesta FW is ready Apr 26 10:04:40 192.168.122.209 [64831.555896] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=1271f8cc2c4c0011" "ja5h=65636588000c0180" Apr 26 10:04:40 192.168.122.209 [64831.581223] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=1271f8cc2c570011" "ja5h=65636588000c0180" Apr 26 10:04:40 192.168.122.209 [64831.582520] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=1271f8cc2c570011" "ja5h=65636588000c0180" Apr 26 10:04:41 192.168.122.209 [64832.098489] [tdb] Close table 'client0.tdb' Apr 26 10:04:41 192.168.122.209 [64832.282163] [tdb] Close table 'sessions0.tdb' Apr 26 10:04:44 192.168.122.209 [64835.446927] [tdb] Close table 'cache0.tdb' Apr 26 10:04:45 192.168.122.209 [64835.678499] [tdb] Close table 'filter0.tdb' Apr 26 10:04:45 192.168.122.209 [64836.350592] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 10:04:45 192.168.122.209 [64836.351031] [tempesta fw] modules are stopped Apr 26 10:04:46 192.168.122.209 [64836.658795] [tempesta fw] exiting... Apr 26 10:04:46 192.168.122.209 [64837.466424] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 10:04:46 192.168.122.209 [64837.525095] [tdb] Shutdown Tempesta DB Apr 26 10:04:47 192.168.122.209 [64837.746270] End test: t_ja5.test_ja5_filters.TestJa5FiltersTestSuiteCiphers.test_ja5_hash_difference Apr 26 10:04:47 192.168.122.209 [64837.756531] Start test: t_ja5.test_ja5_filters.TestJa5FiltersTestSuiteCookies.test_ja5_hash_difference Apr 26 10:04:48 192.168.122.209 [64838.780792] [tdb] Start Tempesta DB Apr 26 10:04:48 192.168.122.209 [64838.926273] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:04:50 192.168.122.209 [64840.965543] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64840.965543] Maybe that's fine, but it's worth checking the [64840.965543] config - if there is no relations between the [64840.965543] names, then host name confusion attack is possible. Apr 26 10:04:50 192.168.122.209 [64841.187881] [tempesta fw] Configuration processing is completed. Apr 26 10:04:50 192.168.122.209 [64841.295800] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 10:04:50 192.168.122.209 [64841.377663] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000003038fc3d Apr 26 10:04:50 192.168.122.209 [64841.414160] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000d11db51e Apr 26 10:04:51 192.168.122.209 [64841.831522] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6070ba4 Apr 26 10:04:51 192.168.122.209 [64841.857255] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000a968d47d Apr 26 10:04:51 192.168.122.209 [64841.897075] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000007aec66b3 Apr 26 10:04:51 192.168.122.209 [64841.983907] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:04:51 192.168.122.209 [64842.023873] [tempesta fw] Tempesta FW is ready Apr 26 10:04:56 192.168.122.209 [64846.733570] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=5b455ce2000c2200" Apr 26 10:04:56 192.168.122.209 [64846.881104] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=5b455ce2000c2200" Apr 26 10:04:56 192.168.122.209 [64847.028457] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=5b455ce2000c4200" Apr 26 10:04:56 192.168.122.209 [64847.180053] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=5b455ce2000c4200" Apr 26 10:04:57 192.168.122.209 [64847.777632] [tdb] Close table 'client0.tdb' Apr 26 10:04:57 192.168.122.209 [64847.959113] [tdb] Close table 'sessions0.tdb' Apr 26 10:05:00 192.168.122.209 [64851.079189] [tdb] Close table 'cache0.tdb' Apr 26 10:05:00 192.168.122.209 [64851.329414] [tdb] Close table 'filter0.tdb' Apr 26 10:05:01 192.168.122.209 [64851.993197] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 10:05:01 192.168.122.209 [64851.993627] [tempesta fw] modules are stopped Apr 26 10:05:01 192.168.122.209 [64852.322261] [tempesta fw] exiting... Apr 26 10:05:02 192.168.122.209 [64853.098068] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 10:05:02 192.168.122.209 [64853.162488] [tdb] Shutdown Tempesta DB Apr 26 10:05:03 192.168.122.209 [64854.195547] [tdb] Start Tempesta DB Apr 26 10:05:03 192.168.122.209 [64854.358142] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:05:05 192.168.122.209 [64856.332697] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64856.332697] Maybe that's fine, but it's worth checking the [64856.332697] config - if there is no relations between the [64856.332697] names, then host name confusion attack is possible. Apr 26 10:05:05 192.168.122.209 [64856.540072] [tempesta fw] Configuration processing is completed. Apr 26 10:05:06 192.168.122.209 [64856.662196] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 10:05:06 192.168.122.209 [64856.766251] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000003038fc3d Apr 26 10:05:06 192.168.122.209 [64856.801030] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000d11db51e Apr 26 10:05:06 192.168.122.209 [64857.304871] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6070ba4 Apr 26 10:05:06 192.168.122.209 [64857.338720] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000a968d47d Apr 26 10:05:06 192.168.122.209 [64857.368706] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000007aec66b3 Apr 26 10:05:06 192.168.122.209 [64857.524127] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:05:06 192.168.122.209 [64857.620051] [tempesta fw] Tempesta FW is ready Apr 26 10:05:07 192.168.122.209 [64857.748568] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=5b455ce2000c2200" Apr 26 10:05:07 192.168.122.209 [64857.754317] [tempesta fw] Warning: parsed request exceeded ja5h limit: 127.0.0.1 Apr 26 10:05:07 192.168.122.209 [64857.755003] [tempesta fw] 127.0.0.1 "-" "GET / HTTP/1.1" 403 0 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=5b455ce2000c2200" Apr 26 10:05:07 192.168.122.209 [64857.773960] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=5b455ce2000c4200" Apr 26 10:05:07 192.168.122.209 [64857.776310] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=5b455ce2000c4200" Apr 26 10:05:07 192.168.122.209 [64858.259111] [tdb] Close table 'client0.tdb' Apr 26 10:05:07 192.168.122.209 [64858.445519] [tdb] Close table 'sessions0.tdb' Apr 26 10:05:11 192.168.122.209 [64861.685112] [tdb] Close table 'cache0.tdb' Apr 26 10:05:11 192.168.122.209 [64861.948611] [tdb] Close table 'filter0.tdb' Apr 26 10:05:12 192.168.122.209 [64862.622827] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 10:05:12 192.168.122.209 [64862.623274] [tempesta fw] modules are stopped Apr 26 10:05:12 192.168.122.209 [64862.902387] [tempesta fw] exiting... Apr 26 10:05:13 192.168.122.209 [64863.624758] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 10:05:13 192.168.122.209 [64863.670036] [tdb] Shutdown Tempesta DB Apr 26 10:05:13 192.168.122.209 [64863.920850] End test: t_ja5.test_ja5_filters.TestJa5FiltersTestSuiteCookies.test_ja5_hash_difference Apr 26 10:05:13 192.168.122.209 [64863.937024] Start test: t_ja5.test_ja5_filters.TestJa5FiltersTestSuiteCookies_2.test_ja5_hash_difference Apr 26 10:05:14 192.168.122.209 [64865.059810] [tdb] Start Tempesta DB Apr 26 10:05:14 192.168.122.209 [64865.216768] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:05:16 192.168.122.209 [64867.257534] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64867.257534] Maybe that's fine, but it's worth checking the [64867.257534] config - if there is no relations between the [64867.257534] names, then host name confusion attack is possible. Apr 26 10:05:16 192.168.122.209 [64867.464908] [tempesta fw] Configuration processing is completed. Apr 26 10:05:16 192.168.122.209 [64867.583205] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 10:05:17 192.168.122.209 [64867.703381] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000003038fc3d Apr 26 10:05:17 192.168.122.209 [64867.735248] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000d11db51e Apr 26 10:05:17 192.168.122.209 [64868.271174] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6070ba4 Apr 26 10:05:17 192.168.122.209 [64868.313607] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000a968d47d Apr 26 10:05:17 192.168.122.209 [64868.349759] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000007aec66b3 Apr 26 10:05:17 192.168.122.209 [64868.460220] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:05:17 192.168.122.209 [64868.512161] [tempesta fw] Tempesta FW is ready Apr 26 10:05:22 192.168.122.209 [64873.242481] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=5b455ce2000c6200" Apr 26 10:05:22 192.168.122.209 [64873.397460] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=5b455ce2000c6200" Apr 26 10:05:22 192.168.122.209 [64873.556230] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=5b455ce2000c8200" Apr 26 10:05:23 192.168.122.209 [64873.724262] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=5b455ce2000c8200" Apr 26 10:05:23 192.168.122.209 [64874.318750] [tdb] Close table 'client0.tdb' Apr 26 10:05:23 192.168.122.209 [64874.510685] [tdb] Close table 'sessions0.tdb' Apr 26 10:05:27 192.168.122.209 [64877.784035] [tdb] Close table 'cache0.tdb' Apr 26 10:05:27 192.168.122.209 [64878.028008] [tdb] Close table 'filter0.tdb' Apr 26 10:05:28 192.168.122.209 [64878.699435] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 10:05:28 192.168.122.209 [64878.699893] [tempesta fw] modules are stopped Apr 26 10:05:28 192.168.122.209 [64879.161256] [tempesta fw] exiting... Apr 26 10:05:29 192.168.122.209 [64879.892467] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 10:05:29 192.168.122.209 [64879.957872] [tdb] Shutdown Tempesta DB Apr 26 10:05:30 192.168.122.209 [64880.998055] [tdb] Start Tempesta DB Apr 26 10:05:30 192.168.122.209 [64881.143507] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:05:32 192.168.122.209 [64883.208835] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64883.208835] Maybe that's fine, but it's worth checking the [64883.208835] config - if there is no relations between the [64883.208835] names, then host name confusion attack is possible. Apr 26 10:05:32 192.168.122.209 [64883.416379] [tempesta fw] Configuration processing is completed. Apr 26 10:05:32 192.168.122.209 [64883.520934] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 10:05:32 192.168.122.209 [64883.602012] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000003038fc3d Apr 26 10:05:33 192.168.122.209 [64883.629926] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000d11db51e Apr 26 10:05:33 192.168.122.209 [64884.048735] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6070ba4 Apr 26 10:05:33 192.168.122.209 [64884.083450] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000a968d47d Apr 26 10:05:33 192.168.122.209 [64884.109954] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000007aec66b3 Apr 26 10:05:33 192.168.122.209 [64884.280421] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:05:33 192.168.122.209 [64884.368345] [tempesta fw] Tempesta FW is ready Apr 26 10:05:33 192.168.122.209 [64884.490870] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=5b455ce2000c6200" Apr 26 10:05:33 192.168.122.209 [64884.495685] [tempesta fw] Warning: parsed request exceeded ja5h limit: 127.0.0.1 Apr 26 10:05:33 192.168.122.209 [64884.496388] [tempesta fw] 127.0.0.1 "-" "GET / HTTP/1.1" 403 0 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=5b455ce2000c6200" Apr 26 10:05:33 192.168.122.209 [64884.519988] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=5b455ce2000c8200" Apr 26 10:05:33 192.168.122.209 [64884.546619] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=5b455ce2000c8200" Apr 26 10:05:34 192.168.122.209 [64885.018495] [tdb] Close table 'client0.tdb' Apr 26 10:05:34 192.168.122.209 [64885.203667] [tdb] Close table 'sessions0.tdb' Apr 26 10:05:37 192.168.122.209 [64888.386972] [tdb] Close table 'cache0.tdb' Apr 26 10:05:37 192.168.122.209 [64888.617051] [tdb] Close table 'filter0.tdb' Apr 26 10:05:38 192.168.122.209 [64889.258311] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 10:05:38 192.168.122.209 [64889.258766] [tempesta fw] modules are stopped Apr 26 10:05:38 192.168.122.209 [64889.612568] [tempesta fw] exiting... Apr 26 10:05:39 192.168.122.209 [64890.369678] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 10:05:39 192.168.122.209 [64890.429824] [tdb] Shutdown Tempesta DB Apr 26 10:05:40 192.168.122.209 [64890.677558] End test: t_ja5.test_ja5_filters.TestJa5FiltersTestSuiteCookies_2.test_ja5_hash_difference Apr 26 10:05:40 192.168.122.209 [64890.699317] Start test: t_ja5.test_ja5_filters.TestJa5FiltersTestSuiteHeaders.test_ja5_hash_difference Apr 26 10:05:41 192.168.122.209 [64891.762518] [tdb] Start Tempesta DB Apr 26 10:05:41 192.168.122.209 [64891.904783] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:05:43 192.168.122.209 [64894.077863] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64894.077863] Maybe that's fine, but it's worth checking the [64894.077863] config - if there is no relations between the [64894.077863] names, then host name confusion attack is possible. Apr 26 10:05:43 192.168.122.209 [64894.308516] [tempesta fw] Configuration processing is completed. Apr 26 10:05:43 192.168.122.209 [64894.431372] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 10:05:43 192.168.122.209 [64894.513913] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000003038fc3d Apr 26 10:05:43 192.168.122.209 [64894.539738] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000d11db51e Apr 26 10:05:44 192.168.122.209 [64894.936602] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6070ba4 Apr 26 10:05:44 192.168.122.209 [64894.961940] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000a968d47d Apr 26 10:05:44 192.168.122.209 [64894.987012] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000007aec66b3 Apr 26 10:05:44 192.168.122.209 [64895.088542] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:05:44 192.168.122.209 [64895.136500] [tempesta fw] Tempesta FW is ready Apr 26 10:05:49 192.168.122.209 [64899.854440] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=c3b9d219000c0200" Apr 26 10:05:49 192.168.122.209 [64900.025811] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=c3b9d219000c0200" Apr 26 10:05:49 192.168.122.209 [64900.178930] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=b93d346b000c0280" Apr 26 10:05:49 192.168.122.209 [64900.327664] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=b93d346b000c0280" Apr 26 10:05:50 192.168.122.209 [64900.912921] [tdb] Close table 'client0.tdb' Apr 26 10:05:50 192.168.122.209 [64901.085892] [tdb] Close table 'sessions0.tdb' Apr 26 10:05:53 192.168.122.209 [64904.232360] [tdb] Close table 'cache0.tdb' Apr 26 10:05:53 192.168.122.209 [64904.488503] [tdb] Close table 'filter0.tdb' Apr 26 10:05:54 192.168.122.209 [64905.160381] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 10:05:54 192.168.122.209 [64905.160861] [tempesta fw] modules are stopped Apr 26 10:05:54 192.168.122.209 [64905.505610] [tempesta fw] exiting... Apr 26 10:05:55 192.168.122.209 [64906.170252] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 10:05:55 192.168.122.209 [64906.246797] [tdb] Shutdown Tempesta DB Apr 26 10:05:56 192.168.122.209 [64907.326079] [tdb] Start Tempesta DB Apr 26 10:05:56 192.168.122.209 [64907.445872] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:05:58 192.168.122.209 [64909.337682] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64909.337682] Maybe that's fine, but it's worth checking the [64909.337682] config - if there is no relations between the [64909.337682] names, then host name confusion attack is possible. Apr 26 10:05:58 192.168.122.209 [64909.544788] [tempesta fw] Configuration processing is completed. Apr 26 10:05:59 192.168.122.209 [64909.651608] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 10:05:59 192.168.122.209 [64909.738907] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000003038fc3d Apr 26 10:05:59 192.168.122.209 [64909.767167] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000d11db51e Apr 26 10:05:59 192.168.122.209 [64910.187928] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6070ba4 Apr 26 10:05:59 192.168.122.209 [64910.213732] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000a968d47d Apr 26 10:05:59 192.168.122.209 [64910.240484] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000007aec66b3 Apr 26 10:05:59 192.168.122.209 [64910.428668] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:05:59 192.168.122.209 [64910.516622] [tempesta fw] Tempesta FW is ready Apr 26 10:05:59 192.168.122.209 [64910.611008] [tempesta fw] Warning: parsed request exceeded ja5h limit: 127.0.0.1 Apr 26 10:05:59 192.168.122.209 [64910.611705] [tempesta fw] 127.0.0.1 "-" "GET / HTTP/1.1" 403 0 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=c3b9d219000c0200" Apr 26 10:06:00 192.168.122.209 [64910.633185] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=c3b9d219000c0200" Apr 26 10:06:00 192.168.122.209 [64910.655320] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=b93d346b000c0280" Apr 26 10:06:00 192.168.122.209 [64910.655380] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=b93d346b000c0280" Apr 26 10:06:00 192.168.122.209 [64911.154224] [tdb] Close table 'client0.tdb' Apr 26 10:06:00 192.168.122.209 [64911.338366] [tdb] Close table 'sessions0.tdb' Apr 26 10:06:03 192.168.122.209 [64914.517714] [tdb] Close table 'cache0.tdb' Apr 26 10:06:04 192.168.122.209 [64914.759364] [tdb] Close table 'filter0.tdb' Apr 26 10:06:04 192.168.122.209 [64915.416013] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 10:06:04 192.168.122.209 [64915.416457] [tempesta fw] modules are stopped Apr 26 10:06:05 192.168.122.209 [64915.710291] [tempesta fw] exiting... Apr 26 10:06:05 192.168.122.209 [64916.441470] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 10:06:05 192.168.122.209 [64916.484946] [tdb] Shutdown Tempesta DB Apr 26 10:06:06 192.168.122.209 [64916.734230] End test: t_ja5.test_ja5_filters.TestJa5FiltersTestSuiteHeaders.test_ja5_hash_difference Apr 26 10:06:06 192.168.122.209 [64916.745805] Start test: t_ja5.test_ja5_filters.TestJa5FiltersTestSuiteHttp.test_ja5_hash_difference Apr 26 10:06:07 192.168.122.209 [64917.823758] [tdb] Start Tempesta DB Apr 26 10:06:07 192.168.122.209 [64917.952489] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:06:09 192.168.122.209 [64920.190169] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64920.190169] Maybe that's fine, but it's worth checking the [64920.190169] config - if there is no relations between the [64920.190169] names, then host name confusion attack is possible. Apr 26 10:06:09 192.168.122.209 [64920.392891] [tempesta fw] Configuration processing is completed. Apr 26 10:06:09 192.168.122.209 [64920.511236] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 10:06:09 192.168.122.209 [64920.600563] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000003038fc3d Apr 26 10:06:10 192.168.122.209 [64920.628345] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000d11db51e Apr 26 10:06:10 192.168.122.209 [64921.022779] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6070ba4 Apr 26 10:06:10 192.168.122.209 [64921.058450] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000a968d47d Apr 26 10:06:10 192.168.122.209 [64921.084567] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000007aec66b3 Apr 26 10:06:10 192.168.122.209 [64921.148864] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:06:10 192.168.122.209 [64921.190156] [tempesta fw] Tempesta FW is ready Apr 26 10:06:15 192.168.122.209 [64925.919319] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=65636588000c0180" Apr 26 10:06:15 192.168.122.209 [64926.068027] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=65636588000c0180" Apr 26 10:06:15 192.168.122.209 [64926.232586] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/2.0" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170015" "ja5h=6564157c008c0300" Apr 26 10:06:15 192.168.122.209 [64926.402740] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/2.0" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170015" "ja5h=6564157c008c0300" Apr 26 10:06:16 192.168.122.209 [64926.975150] [tdb] Close table 'client0.tdb' Apr 26 10:06:16 192.168.122.209 [64927.157550] [tdb] Close table 'sessions0.tdb' Apr 26 10:06:19 192.168.122.209 [64930.310301] [tdb] Close table 'cache0.tdb' Apr 26 10:06:19 192.168.122.209 [64930.552564] [tdb] Close table 'filter0.tdb' Apr 26 10:06:20 192.168.122.209 [64931.192110] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 10:06:20 192.168.122.209 [64931.192540] [tempesta fw] modules are stopped Apr 26 10:06:20 192.168.122.209 [64931.485997] [tempesta fw] exiting... Apr 26 10:06:21 192.168.122.209 [64932.138132] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 10:06:21 192.168.122.209 [64932.195109] [tdb] Shutdown Tempesta DB Apr 26 10:06:22 192.168.122.209 [64933.273672] [tdb] Start Tempesta DB Apr 26 10:06:22 192.168.122.209 [64933.401432] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:06:24 192.168.122.209 [64935.437494] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64935.437494] Maybe that's fine, but it's worth checking the [64935.437494] config - if there is no relations between the [64935.437494] names, then host name confusion attack is possible. Apr 26 10:06:25 192.168.122.209 [64935.645012] [tempesta fw] Configuration processing is completed. Apr 26 10:06:25 192.168.122.209 [64935.768804] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 10:06:25 192.168.122.209 [64935.853574] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000003038fc3d Apr 26 10:06:25 192.168.122.209 [64935.880733] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000d11db51e Apr 26 10:06:25 192.168.122.209 [64936.304163] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6070ba4 Apr 26 10:06:25 192.168.122.209 [64936.332118] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000a968d47d Apr 26 10:06:25 192.168.122.209 [64936.363256] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000007aec66b3 Apr 26 10:06:25 192.168.122.209 [64936.517071] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:06:26 192.168.122.209 [64936.629001] [tempesta fw] Tempesta FW is ready Apr 26 10:06:26 192.168.122.209 [64936.750836] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=65636588000c0180" Apr 26 10:06:26 192.168.122.209 [64936.753290] [tempesta fw] Warning: parsed request exceeded ja5h limit: 127.0.0.1 Apr 26 10:06:26 192.168.122.209 [64936.753993] [tempesta fw] 127.0.0.1 "-" "GET / HTTP/1.1" 403 0 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=65636588000c0180" Apr 26 10:06:26 192.168.122.209 [64936.786128] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/2.0" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170015" "ja5h=6564157c008c0300" Apr 26 10:06:26 192.168.122.209 [64936.786240] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/2.0" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170015" "ja5h=6564157c008c0300" Apr 26 10:06:26 192.168.122.209 [64937.284112] [tdb] Close table 'client0.tdb' Apr 26 10:06:26 192.168.122.209 [64937.451146] [tdb] Close table 'sessions0.tdb' Apr 26 10:06:29 192.168.122.209 [64940.598014] [tdb] Close table 'cache0.tdb' Apr 26 10:06:30 192.168.122.209 [64940.865285] [tdb] Close table 'filter0.tdb' Apr 26 10:06:30 192.168.122.209 [64941.526614] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 10:06:30 192.168.122.209 [64941.527060] [tempesta fw] modules are stopped Apr 26 10:06:31 192.168.122.209 [64941.812700] [tempesta fw] exiting... Apr 26 10:06:31 192.168.122.209 [64942.489996] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 10:06:31 192.168.122.209 [64942.558358] [tdb] Shutdown Tempesta DB Apr 26 10:06:32 192.168.122.209 [64942.755267] End test: t_ja5.test_ja5_filters.TestJa5FiltersTestSuiteHttp.test_ja5_hash_difference Apr 26 10:06:32 192.168.122.209 [64942.771863] Start test: t_ja5.test_ja5_filters.TestJa5FiltersTestSuiteMethod.test_ja5_hash_difference Apr 26 10:06:33 192.168.122.209 [64943.787966] [tdb] Start Tempesta DB Apr 26 10:06:33 192.168.122.209 [64943.921682] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:06:35 192.168.122.209 [64945.942433] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64945.942433] Maybe that's fine, but it's worth checking the [64945.942433] config - if there is no relations between the [64945.942433] names, then host name confusion attack is possible. Apr 26 10:06:35 192.168.122.209 [64946.149206] [tempesta fw] Configuration processing is completed. Apr 26 10:06:35 192.168.122.209 [64946.255301] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 10:06:35 192.168.122.209 [64946.338323] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000003038fc3d Apr 26 10:06:35 192.168.122.209 [64946.375691] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000d11db51e Apr 26 10:06:36 192.168.122.209 [64946.832486] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6070ba4 Apr 26 10:06:36 192.168.122.209 [64946.861293] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000a968d47d Apr 26 10:06:36 192.168.122.209 [64946.895200] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000007aec66b3 Apr 26 10:06:36 192.168.122.209 [64946.961193] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:06:36 192.168.122.209 [64947.017146] [tempesta fw] Tempesta FW is ready Apr 26 10:06:41 192.168.122.209 [64951.796860] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=65636588000c0180" Apr 26 10:06:41 192.168.122.209 [64951.973153] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=65636588000c0180" Apr 26 10:06:41 192.168.122.209 [64952.128025] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "POST / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=6563658800280180" Apr 26 10:06:41 192.168.122.209 [64952.298741] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "POST / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=6563658800280180" Apr 26 10:06:42 192.168.122.209 [64952.895610] [tdb] Close table 'client0.tdb' Apr 26 10:06:42 192.168.122.209 [64953.080145] [tdb] Close table 'sessions0.tdb' Apr 26 10:06:45 192.168.122.209 [64956.241295] [tdb] Close table 'cache0.tdb' Apr 26 10:06:45 192.168.122.209 [64956.511239] [tdb] Close table 'filter0.tdb' Apr 26 10:06:46 192.168.122.209 [64957.149918] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 10:06:46 192.168.122.209 [64957.150347] [tempesta fw] modules are stopped Apr 26 10:06:46 192.168.122.209 [64957.435371] [tempesta fw] exiting... Apr 26 10:06:47 192.168.122.209 [64958.127853] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 10:06:47 192.168.122.209 [64958.177741] [tdb] Shutdown Tempesta DB Apr 26 10:06:48 192.168.122.209 [64959.283832] [tdb] Start Tempesta DB Apr 26 10:06:48 192.168.122.209 [64959.446106] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:06:50 192.168.122.209 [64961.518614] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64961.518614] Maybe that's fine, but it's worth checking the [64961.518614] config - if there is no relations between the [64961.518614] names, then host name confusion attack is possible. Apr 26 10:06:51 192.168.122.209 [64961.733331] [tempesta fw] Configuration processing is completed. Apr 26 10:06:51 192.168.122.209 [64961.840658] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 10:06:51 192.168.122.209 [64961.924696] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000003038fc3d Apr 26 10:06:51 192.168.122.209 [64961.952040] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000d11db51e Apr 26 10:06:51 192.168.122.209 [64962.395531] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6070ba4 Apr 26 10:06:51 192.168.122.209 [64962.424229] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000a968d47d Apr 26 10:06:51 192.168.122.209 [64962.452637] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000007aec66b3 Apr 26 10:06:52 192.168.122.209 [64962.625360] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:06:52 192.168.122.209 [64962.721318] [tempesta fw] Tempesta FW is ready Apr 26 10:06:52 192.168.122.209 [64962.820743] [tempesta fw] Warning: parsed request exceeded ja5h limit: 127.0.0.1 Apr 26 10:06:52 192.168.122.209 [64962.821429] [tempesta fw] 127.0.0.1 "-" "GET / HTTP/1.1" 403 0 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=65636588000c0180" Apr 26 10:06:52 192.168.122.209 [64962.838314] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=65636588000c0180" Apr 26 10:06:52 192.168.122.209 [64962.848715] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "POST / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=6563658800280180" Apr 26 10:06:52 192.168.122.209 [64962.870490] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "POST / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=6563658800280180" Apr 26 10:06:52 192.168.122.209 [64963.380006] [tdb] Close table 'client0.tdb' Apr 26 10:06:52 192.168.122.209 [64963.560183] [tdb] Close table 'sessions0.tdb' Apr 26 10:06:56 192.168.122.209 [64966.737095] [tdb] Close table 'cache0.tdb' Apr 26 10:06:56 192.168.122.209 [64966.974209] [tdb] Close table 'filter0.tdb' Apr 26 10:06:56 192.168.122.209 [64967.602128] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 10:06:56 192.168.122.209 [64967.602576] [tempesta fw] modules are stopped Apr 26 10:06:57 192.168.122.209 [64967.926905] [tempesta fw] exiting... Apr 26 10:06:57 192.168.122.209 [64968.577854] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 10:06:58 192.168.122.209 [64968.630912] [tdb] Shutdown Tempesta DB Apr 26 10:06:58 192.168.122.209 [64968.874377] End test: t_ja5.test_ja5_filters.TestJa5FiltersTestSuiteMethod.test_ja5_hash_difference Apr 26 10:06:58 192.168.122.209 [64968.901397] Start test: t_ja5.test_ja5_filters.TestJa5FiltersTestSuiteNoAlpn.test_ja5_hash_difference Apr 26 10:06:59 192.168.122.209 [64970.038388] [tdb] Start Tempesta DB Apr 26 10:06:59 192.168.122.209 [64970.204256] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:07:02 192.168.122.209 [64972.959195] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64972.959195] Maybe that's fine, but it's worth checking the [64972.959195] config - if there is no relations between the [64972.959195] names, then host name confusion attack is possible. Apr 26 10:07:04 192.168.122.209 [64975.259329] [tempesta fw] Configuration processing is completed. Apr 26 10:07:04 192.168.122.209 [64975.503545] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 10:07:05 192.168.122.209 [64975.703791] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000003038fc3d Apr 26 10:07:05 192.168.122.209 [64975.760120] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000d11db51e Apr 26 10:07:05 192.168.122.209 [64976.314391] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6070ba4 Apr 26 10:07:05 192.168.122.209 [64976.349479] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000a968d47d Apr 26 10:07:05 192.168.122.209 [64976.383295] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000007aec66b3 Apr 26 10:07:05 192.168.122.209 [64976.449495] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:07:05 192.168.122.209 [64976.497519] [tempesta fw] Tempesta FW is ready Apr 26 10:07:10 192.168.122.209 [64981.395848] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=1271f8cc2c4c0011" "ja5h=65636588000c0180" Apr 26 10:07:10 192.168.122.209 [64981.571241] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=1271f8cc2c4c0011" "ja5h=65636588000c0180" Apr 26 10:07:11 192.168.122.209 [64981.748555] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=1271532a2c4c0010" "ja5h=65636588000c0180" Apr 26 10:07:11 192.168.122.209 [64981.927070] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=1271532a2c4c0010" "ja5h=65636588000c0180" Apr 26 10:07:11 192.168.122.209 [64982.526893] [tdb] Close table 'client0.tdb' Apr 26 10:07:12 192.168.122.209 [64982.698801] [tdb] Close table 'sessions0.tdb' Apr 26 10:07:15 192.168.122.209 [64985.824838] [tdb] Close table 'cache0.tdb' Apr 26 10:07:15 192.168.122.209 [64986.072778] [tdb] Close table 'filter0.tdb' Apr 26 10:07:16 192.168.122.209 [64986.728088] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 10:07:16 192.168.122.209 [64986.728574] [tempesta fw] modules are stopped Apr 26 10:07:16 192.168.122.209 [64987.006710] [tempesta fw] exiting... Apr 26 10:07:17 192.168.122.209 [64987.747949] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 10:07:17 192.168.122.209 [64987.792472] [tdb] Shutdown Tempesta DB Apr 26 10:07:18 192.168.122.209 [64988.939350] [tdb] Start Tempesta DB Apr 26 10:07:18 192.168.122.209 [64989.080910] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:07:20 192.168.122.209 [64991.139324] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [64991.139324] Maybe that's fine, but it's worth checking the [64991.139324] config - if there is no relations between the [64991.139324] names, then host name confusion attack is possible. Apr 26 10:07:20 192.168.122.209 [64991.377756] [tempesta fw] Configuration processing is completed. Apr 26 10:07:20 192.168.122.209 [64991.532415] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 10:07:21 192.168.122.209 [64991.682170] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000003038fc3d Apr 26 10:07:21 192.168.122.209 [64991.730338] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000d11db51e Apr 26 10:07:21 192.168.122.209 [64992.470820] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6070ba4 Apr 26 10:07:21 192.168.122.209 [64992.515402] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000a968d47d Apr 26 10:07:21 192.168.122.209 [64992.560335] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000007aec66b3 Apr 26 10:07:22 192.168.122.209 [64992.717702] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:07:22 192.168.122.209 [64992.817698] [tempesta fw] Tempesta FW is ready Apr 26 10:07:22 192.168.122.209 [64992.944526] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=1271f8cc2c4c0011" "ja5h=65636588000c0180" Apr 26 10:07:22 192.168.122.209 [64992.971280] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=1271532a2c4c0010" "ja5h=65636588000c0180" Apr 26 10:07:22 192.168.122.209 [64992.986909] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=1271532a2c4c0010" "ja5h=65636588000c0180" Apr 26 10:07:22 192.168.122.209 [64993.497181] [tdb] Close table 'client0.tdb' Apr 26 10:07:23 192.168.122.209 [64993.704802] [tdb] Close table 'sessions0.tdb' Apr 26 10:07:26 192.168.122.209 [64997.095105] [tdb] Close table 'cache0.tdb' Apr 26 10:07:26 192.168.122.209 [64997.337035] [tdb] Close table 'filter0.tdb' Apr 26 10:07:27 192.168.122.209 [64998.017765] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 10:07:27 192.168.122.209 [64998.018246] [tempesta fw] modules are stopped Apr 26 10:07:27 192.168.122.209 [64998.344932] [tempesta fw] exiting... Apr 26 10:07:28 192.168.122.209 [64999.036411] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 10:07:28 192.168.122.209 [64999.072106] [tdb] Shutdown Tempesta DB Apr 26 10:07:28 192.168.122.209 [64999.297853] End test: t_ja5.test_ja5_filters.TestJa5FiltersTestSuiteNoAlpn.test_ja5_hash_difference Apr 26 10:07:28 192.168.122.209 [64999.310880] Start test: t_ja5.test_ja5_filters.TestJa5FiltersTestSuiteReferer.test_ja5_hash_difference Apr 26 10:07:29 192.168.122.209 [65000.544145] [tdb] Start Tempesta DB Apr 26 10:07:30 192.168.122.209 [65000.766523] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:07:32 192.168.122.209 [65003.091390] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65003.091390] Maybe that's fine, but it's worth checking the [65003.091390] config - if there is no relations between the [65003.091390] names, then host name confusion attack is possible. Apr 26 10:07:32 192.168.122.209 [65003.285898] [tempesta fw] Configuration processing is completed. Apr 26 10:07:32 192.168.122.209 [65003.462701] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 10:07:32 192.168.122.209 [65003.603390] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000003038fc3d Apr 26 10:07:33 192.168.122.209 [65003.664760] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000d11db51e Apr 26 10:07:33 192.168.122.209 [65004.244572] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6070ba4 Apr 26 10:07:33 192.168.122.209 [65004.282380] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000a968d47d Apr 26 10:07:33 192.168.122.209 [65004.318689] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000007aec66b3 Apr 26 10:07:33 192.168.122.209 [65004.425910] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:07:33 192.168.122.209 [65004.469866] [tempesta fw] Tempesta FW is ready Apr 26 10:07:38 192.168.122.209 [65009.128126] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "tempesta-tech.com" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=5b455ce3000c0240" Apr 26 10:07:38 192.168.122.209 [65009.342843] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "tempesta-tech.com" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=5b455ce3000c0240" Apr 26 10:07:38 192.168.122.209 [65009.529178] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=65636588000c0180" Apr 26 10:07:39 192.168.122.209 [65009.711302] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=65636588000c0180" Apr 26 10:07:39 192.168.122.209 [65010.381259] [tdb] Close table 'client0.tdb' Apr 26 10:07:39 192.168.122.209 [65010.560477] [tdb] Close table 'sessions0.tdb' Apr 26 10:07:43 192.168.122.209 [65013.843543] [tdb] Close table 'cache0.tdb' Apr 26 10:07:43 192.168.122.209 [65014.094439] [tdb] Close table 'filter0.tdb' Apr 26 10:07:44 192.168.122.209 [65014.744564] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 10:07:44 192.168.122.209 [65014.744995] [tempesta fw] modules are stopped Apr 26 10:07:44 192.168.122.209 [65015.044790] [tempesta fw] exiting... Apr 26 10:07:45 192.168.122.209 [65015.765204] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 10:07:45 192.168.122.209 [65015.821314] [tdb] Shutdown Tempesta DB Apr 26 10:07:46 192.168.122.209 [65017.025000] [tdb] Start Tempesta DB Apr 26 10:07:46 192.168.122.209 [65017.165820] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:07:48 192.168.122.209 [65019.454272] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65019.454272] Maybe that's fine, but it's worth checking the [65019.454272] config - if there is no relations between the [65019.454272] names, then host name confusion attack is possible. Apr 26 10:07:49 192.168.122.209 [65019.690071] [tempesta fw] Configuration processing is completed. Apr 26 10:07:49 192.168.122.209 [65019.808725] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 10:07:49 192.168.122.209 [65019.901019] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000003038fc3d Apr 26 10:07:49 192.168.122.209 [65019.929018] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000d11db51e Apr 26 10:07:49 192.168.122.209 [65020.366550] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6070ba4 Apr 26 10:07:49 192.168.122.209 [65020.394648] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000a968d47d Apr 26 10:07:49 192.168.122.209 [65020.422189] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000007aec66b3 Apr 26 10:07:49 192.168.122.209 [65020.582084] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:07:50 192.168.122.209 [65020.682023] [tempesta fw] Tempesta FW is ready Apr 26 10:07:50 192.168.122.209 [65020.802647] [tempesta fw] Warning: parsed request exceeded ja5h limit: 127.0.0.1 Apr 26 10:07:50 192.168.122.209 [65020.803375] [tempesta fw] 127.0.0.1 "-" "GET / HTTP/1.1" 403 0 "tempesta-tech.com" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=5b455ce3000c0240" Apr 26 10:07:50 192.168.122.209 [65020.816197] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "tempesta-tech.com" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=5b455ce3000c0240" Apr 26 10:07:50 192.168.122.209 [65020.834652] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=65636588000c0180" Apr 26 10:07:50 192.168.122.209 [65020.862437] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=66cbf8ccef170011" "ja5h=65636588000c0180" Apr 26 10:07:50 192.168.122.209 [65021.359458] [tdb] Close table 'client0.tdb' Apr 26 10:07:50 192.168.122.209 [65021.542458] [tdb] Close table 'sessions0.tdb' Apr 26 10:07:54 192.168.122.209 [65024.656299] [tdb] Close table 'cache0.tdb' Apr 26 10:07:54 192.168.122.209 [65024.889634] [tdb] Close table 'filter0.tdb' Apr 26 10:07:54 192.168.122.209 [65025.550238] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 10:07:54 192.168.122.209 [65025.550664] [tempesta fw] modules are stopped Apr 26 10:07:55 192.168.122.209 [65025.863692] [tempesta fw] exiting... Apr 26 10:07:55 192.168.122.209 [65026.558215] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 10:07:55 192.168.122.209 [65026.623266] [tdb] Shutdown Tempesta DB Apr 26 10:07:56 192.168.122.209 [65026.873008] End test: t_ja5.test_ja5_filters.TestJa5FiltersTestSuiteReferer.test_ja5_hash_difference Apr 26 10:07:56 192.168.122.209 [65026.889878] Start test: t_ja5.test_ja5_filters.TestJa5FiltersTestSuiteVhost.test_ja5_hash_difference Apr 26 10:07:57 192.168.122.209 [65027.948844] [tdb] Start Tempesta DB Apr 26 10:07:57 192.168.122.209 [65028.094556] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:07:59 192.168.122.209 [65030.255465] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65030.255465] Maybe that's fine, but it's worth checking the [65030.255465] config - if there is no relations between the [65030.255465] names, then host name confusion attack is possible. Apr 26 10:07:59 192.168.122.209 [65030.478153] [tempesta fw] Configuration processing is completed. Apr 26 10:07:59 192.168.122.209 [65030.599032] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 10:08:00 192.168.122.209 [65030.685556] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000003038fc3d Apr 26 10:08:00 192.168.122.209 [65030.713932] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000d11db51e Apr 26 10:08:00 192.168.122.209 [65031.134912] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6070ba4 Apr 26 10:08:00 192.168.122.209 [65031.167361] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000a968d47d Apr 26 10:08:00 192.168.122.209 [65031.200780] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000007aec66b3 Apr 26 10:08:00 192.168.122.209 [65031.282299] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:08:00 192.168.122.209 [65031.330167] [tempesta fw] Tempesta FW is ready Apr 26 10:08:05 192.168.122.209 [65036.083521] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=1271f8cc2c4c0011" "ja5h=65636588000c0180" Apr 26 10:08:05 192.168.122.209 [65036.243633] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=1271f8cc2c4c0011" "ja5h=65636588000c0180" Apr 26 10:08:05 192.168.122.209 [65036.390488] [tempesta fw] 127.0.0.1 "default" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=1471f8cc2c4c0001" "ja5h=65636588000c0180" Apr 26 10:08:05 192.168.122.209 [65036.550324] [tempesta fw] 127.0.0.1 "default" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=1471f8cc2c4c0001" "ja5h=65636588000c0180" Apr 26 10:08:06 192.168.122.209 [65037.127318] [tdb] Close table 'client0.tdb' Apr 26 10:08:06 192.168.122.209 [65037.311170] [tdb] Close table 'sessions0.tdb' Apr 26 10:08:10 192.168.122.209 [65040.693041] [tdb] Close table 'cache0.tdb' Apr 26 10:08:10 192.168.122.209 [65040.972850] [tdb] Close table 'filter0.tdb' Apr 26 10:08:11 192.168.122.209 [65041.646206] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 10:08:11 192.168.122.209 [65041.646674] [tempesta fw] modules are stopped Apr 26 10:08:11 192.168.122.209 [65041.971283] [tempesta fw] exiting... Apr 26 10:08:12 192.168.122.209 [65042.695039] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 10:08:12 192.168.122.209 [65042.735556] [tdb] Shutdown Tempesta DB Apr 26 10:08:13 192.168.122.209 [65043.799117] [tdb] Start Tempesta DB Apr 26 10:08:13 192.168.122.209 [65043.948246] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:08:15 192.168.122.209 [65045.995697] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65045.995697] Maybe that's fine, but it's worth checking the [65045.995697] config - if there is no relations between the [65045.995697] names, then host name confusion attack is possible. Apr 26 10:08:15 192.168.122.209 [65046.234396] [tempesta fw] Configuration processing is completed. Apr 26 10:08:15 192.168.122.209 [65046.349264] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 10:08:15 192.168.122.209 [65046.439730] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000003038fc3d Apr 26 10:08:15 192.168.122.209 [65046.466958] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000d11db51e Apr 26 10:08:16 192.168.122.209 [65046.893051] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6070ba4 Apr 26 10:08:16 192.168.122.209 [65046.920517] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000a968d47d Apr 26 10:08:16 192.168.122.209 [65046.947662] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000007aec66b3 Apr 26 10:08:16 192.168.122.209 [65047.082392] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:08:16 192.168.122.209 [65047.178308] [tempesta fw] Tempesta FW is ready Apr 26 10:08:16 192.168.122.209 [65047.304707] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=1271f8cc2c4c0011" "ja5h=65636588000c0180" Apr 26 10:08:16 192.168.122.209 [65047.311957] [tempesta fw] 127.0.0.1 "default" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=1471f8cc2c4c0001" "ja5h=65636588000c0180" Apr 26 10:08:16 192.168.122.209 [65047.341108] [tempesta fw] 127.0.0.1 "default" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=1471f8cc2c4c0001" "ja5h=65636588000c0180" Apr 26 10:08:17 192.168.122.209 [65047.843863] [tdb] Close table 'client0.tdb' Apr 26 10:08:17 192.168.122.209 [65048.037423] [tdb] Close table 'sessions0.tdb' Apr 26 10:08:20 192.168.122.209 [65051.197861] [tdb] Close table 'cache0.tdb' Apr 26 10:08:20 192.168.122.209 [65051.447553] [tdb] Close table 'filter0.tdb' Apr 26 10:08:21 192.168.122.209 [65052.099747] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 10:08:21 192.168.122.209 [65052.100207] [tempesta fw] modules are stopped Apr 26 10:08:21 192.168.122.209 [65052.371132] [tempesta fw] exiting... Apr 26 10:08:22 192.168.122.209 [65053.055597] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 10:08:22 192.168.122.209 [65053.092539] [tdb] Shutdown Tempesta DB Apr 26 10:08:22 192.168.122.209 [65053.325701] End test: t_ja5.test_ja5_filters.TestJa5FiltersTestSuiteVhost.test_ja5_hash_difference Apr 26 10:08:22 192.168.122.209 [65053.343445] Start test: t_ja5.test_ja5_filters.TestJa5HashDoesNotMatchedWithFiltered.test_default_values Apr 26 10:08:23 192.168.122.209 [65054.417537] [tdb] Start Tempesta DB Apr 26 10:08:23 192.168.122.209 [65054.557251] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:08:26 192.168.122.209 [65056.687807] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65056.687807] Maybe that's fine, but it's worth checking the [65056.687807] config - if there is no relations between the [65056.687807] names, then host name confusion attack is possible. Apr 26 10:08:26 192.168.122.209 [65056.898485] [tempesta fw] Configuration processing is completed. Apr 26 10:08:26 192.168.122.209 [65057.007322] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 10:08:26 192.168.122.209 [65057.102017] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000003038fc3d Apr 26 10:08:26 192.168.122.209 [65057.131145] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000d11db51e Apr 26 10:08:26 192.168.122.209 [65057.553474] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6070ba4 Apr 26 10:08:26 192.168.122.209 [65057.580534] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000a968d47d Apr 26 10:08:26 192.168.122.209 [65057.606921] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000007aec66b3 Apr 26 10:08:27 192.168.122.209 [65057.670462] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:08:27 192.168.122.209 [65057.710496] [tempesta fw] Tempesta FW is ready Apr 26 10:08:27 192.168.122.209 [65057.896434] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=1271f8cc2c4c0011" "ja5h=65636588000c0180" Apr 26 10:08:27 192.168.122.209 [65057.927017] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=1271f8cc2c4c0011" "ja5h=65636588000c0180" Apr 26 10:08:27 192.168.122.209 [65058.472053] [tdb] Close table 'client0.tdb' Apr 26 10:08:28 192.168.122.209 [65058.654068] [tdb] Close table 'sessions0.tdb' Apr 26 10:08:31 192.168.122.209 [65061.839200] [tdb] Close table 'cache0.tdb' Apr 26 10:08:31 192.168.122.209 [65062.084799] [tdb] Close table 'filter0.tdb' Apr 26 10:08:32 192.168.122.209 [65062.736722] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 10:08:32 192.168.122.209 [65062.737156] [tempesta fw] modules are stopped Apr 26 10:08:32 192.168.122.209 [65063.035628] [tempesta fw] exiting... Apr 26 10:08:33 192.168.122.209 [65063.704023] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 10:08:33 192.168.122.209 [65063.750594] [tdb] Shutdown Tempesta DB Apr 26 10:08:33 192.168.122.209 [65063.989385] End test: t_ja5.test_ja5_filters.TestJa5HashDoesNotMatchedWithFiltered.test_default_values Apr 26 10:08:33 192.168.122.209 [65063.998713] Start test: t_ja5.test_ja5_filters.TestRestartAppWithUpdatedHashJa5h.test_hot_reload Apr 26 10:08:34 192.168.122.209 [65065.023806] [tdb] Start Tempesta DB Apr 26 10:08:34 192.168.122.209 [65065.170959] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:08:36 192.168.122.209 [65067.259226] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65067.259226] Maybe that's fine, but it's worth checking the [65067.259226] config - if there is no relations between the [65067.259226] names, then host name confusion attack is possible. Apr 26 10:08:36 192.168.122.209 [65067.506642] [tempesta fw] Configuration processing is completed. Apr 26 10:08:37 192.168.122.209 [65067.641846] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 10:08:37 192.168.122.209 [65067.740814] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000003038fc3d Apr 26 10:08:37 192.168.122.209 [65067.771330] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000d11db51e Apr 26 10:08:37 192.168.122.209 [65068.235858] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6070ba4 Apr 26 10:08:37 192.168.122.209 [65068.265505] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000a968d47d Apr 26 10:08:37 192.168.122.209 [65068.295799] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000007aec66b3 Apr 26 10:08:37 192.168.122.209 [65068.358666] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:08:37 192.168.122.209 [65068.398590] [tempesta fw] Tempesta FW is ready Apr 26 10:08:37 192.168.122.209 [65068.607196] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=1271f8cc2c4c0011" "ja5h=65636588000c0180" Apr 26 10:08:38 192.168.122.209 [65068.700848] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=1271f8cc2c4c0011" "ja5h=65636588000c0180" Apr 26 10:08:38 192.168.122.209 [65069.284857] [tdb] Close table 'client0.tdb' Apr 26 10:08:38 192.168.122.209 [65069.468522] [tdb] Close table 'sessions0.tdb' Apr 26 10:08:42 192.168.122.209 [65072.631944] [tdb] Close table 'cache0.tdb' Apr 26 10:08:42 192.168.122.209 [65072.888483] [tdb] Close table 'filter0.tdb' Apr 26 10:08:42 192.168.122.209 [65073.559292] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 10:08:42 192.168.122.209 [65073.559741] [tempesta fw] modules are stopped Apr 26 10:08:43 192.168.122.209 [65073.842203] [tempesta fw] exiting... Apr 26 10:08:43 192.168.122.209 [65074.517626] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 10:08:43 192.168.122.209 [65074.566370] [tdb] Shutdown Tempesta DB Apr 26 10:08:45 192.168.122.209 [65075.647037] [tdb] Start Tempesta DB Apr 26 10:08:45 192.168.122.209 [65075.786305] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:08:47 192.168.122.209 [65077.771942] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65077.771942] Maybe that's fine, but it's worth checking the [65077.771942] config - if there is no relations between the [65077.771942] names, then host name confusion attack is possible. Apr 26 10:08:47 192.168.122.209 [65077.998721] [tempesta fw] Configuration processing is completed. Apr 26 10:08:47 192.168.122.209 [65078.114843] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 10:08:47 192.168.122.209 [65078.203174] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000003038fc3d Apr 26 10:08:47 192.168.122.209 [65078.231204] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000d11db51e Apr 26 10:08:48 192.168.122.209 [65078.664582] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6070ba4 Apr 26 10:08:48 192.168.122.209 [65078.691085] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000a968d47d Apr 26 10:08:48 192.168.122.209 [65078.717384] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000007aec66b3 Apr 26 10:08:48 192.168.122.209 [65078.886780] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:08:48 192.168.122.209 [65078.987648] [tempesta fw] Tempesta FW is ready Apr 26 10:08:48 192.168.122.209 [65079.116756] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=1271f8cc2c4c0011" "ja5h=65636588000c0180" Apr 26 10:08:49 192.168.122.209 [65079.639329] [tdb] Close table 'client0.tdb' Apr 26 10:08:49 192.168.122.209 [65079.829106] [tdb] Close table 'sessions0.tdb' Apr 26 10:08:52 192.168.122.209 [65082.995376] [tdb] Close table 'cache0.tdb' Apr 26 10:08:52 192.168.122.209 [65083.261412] [tdb] Close table 'filter0.tdb' Apr 26 10:08:53 192.168.122.209 [65083.902646] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 10:08:53 192.168.122.209 [65083.903114] [tempesta fw] modules are stopped Apr 26 10:08:53 192.168.122.209 [65084.191260] [tempesta fw] exiting... Apr 26 10:08:54 192.168.122.209 [65084.874815] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 10:08:54 192.168.122.209 [65084.945238] [tdb] Shutdown Tempesta DB Apr 26 10:08:54 192.168.122.209 [65085.183728] End test: t_ja5.test_ja5_filters.TestRestartAppWithUpdatedHashJa5h.test_hot_reload Apr 26 10:08:54 192.168.122.209 [65085.197230] Start test: t_ja5.test_ja5_filters.TestRestartAppWithUpdatedHashJa5h.test_restart_ok Apr 26 10:08:55 192.168.122.209 [65086.238404] [tdb] Start Tempesta DB Apr 26 10:08:55 192.168.122.209 [65086.380852] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:08:58 192.168.122.209 [65088.676408] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65088.676408] Maybe that's fine, but it's worth checking the [65088.676408] config - if there is no relations between the [65088.676408] names, then host name confusion attack is possible. Apr 26 10:08:58 192.168.122.209 [65088.871196] [tempesta fw] Configuration processing is completed. Apr 26 10:08:58 192.168.122.209 [65088.985742] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 10:08:58 192.168.122.209 [65089.073663] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000003038fc3d Apr 26 10:08:58 192.168.122.209 [65089.101980] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000d11db51e Apr 26 10:08:58 192.168.122.209 [65089.523111] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6070ba4 Apr 26 10:08:58 192.168.122.209 [65089.550827] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000a968d47d Apr 26 10:08:58 192.168.122.209 [65089.577699] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000007aec66b3 Apr 26 10:08:59 192.168.122.209 [65089.638936] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:08:59 192.168.122.209 [65089.678839] [tempesta fw] Tempesta FW is ready Apr 26 10:08:59 192.168.122.209 [65090.277645] [tdb] Close table 'client0.tdb' Apr 26 10:08:59 192.168.122.209 [65090.462053] [tdb] Close table 'sessions0.tdb' Apr 26 10:09:03 192.168.122.209 [65093.652521] [tdb] Close table 'cache0.tdb' Apr 26 10:09:03 192.168.122.209 [65093.880747] [tdb] Close table 'filter0.tdb' Apr 26 10:09:03 192.168.122.209 [65094.516664] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 10:09:03 192.168.122.209 [65094.517133] [tempesta fw] modules are stopped Apr 26 10:09:04 192.168.122.209 [65094.859537] [tempesta fw] exiting... Apr 26 10:09:04 192.168.122.209 [65095.515365] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 10:09:04 192.168.122.209 [65095.555569] [tdb] Shutdown Tempesta DB Apr 26 10:09:06 192.168.122.209 [65096.663888] [tdb] Start Tempesta DB Apr 26 10:09:06 192.168.122.209 [65096.810015] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:09:08 192.168.122.209 [65099.068071] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65099.068071] Maybe that's fine, but it's worth checking the [65099.068071] config - if there is no relations between the [65099.068071] names, then host name confusion attack is possible. Apr 26 10:09:08 192.168.122.209 [65099.283032] [tempesta fw] Configuration processing is completed. Apr 26 10:09:08 192.168.122.209 [65099.409072] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 10:09:08 192.168.122.209 [65099.499414] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000003038fc3d Apr 26 10:09:08 192.168.122.209 [65099.529078] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000d11db51e Apr 26 10:09:09 192.168.122.209 [65099.955903] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6070ba4 Apr 26 10:09:09 192.168.122.209 [65099.990959] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000a968d47d Apr 26 10:09:09 192.168.122.209 [65100.016524] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000007aec66b3 Apr 26 10:09:09 192.168.122.209 [65100.082941] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:09:09 192.168.122.209 [65100.122963] [tempesta fw] Tempesta FW is ready Apr 26 10:09:09 192.168.122.209 [65100.622415] [tdb] Close table 'client0.tdb' Apr 26 10:09:10 192.168.122.209 [65100.841512] [tdb] Close table 'sessions0.tdb' Apr 26 10:09:13 192.168.122.209 [65104.034298] [tdb] Close table 'cache0.tdb' Apr 26 10:09:13 192.168.122.209 [65104.281308] [tdb] Close table 'filter0.tdb' Apr 26 10:09:14 192.168.122.209 [65104.932581] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 10:09:14 192.168.122.209 [65104.933055] [tempesta fw] modules are stopped Apr 26 10:09:14 192.168.122.209 [65105.215823] [tempesta fw] exiting... Apr 26 10:09:15 192.168.122.209 [65105.900863] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 10:09:15 192.168.122.209 [65105.932186] [tdb] Shutdown Tempesta DB Apr 26 10:09:15 192.168.122.209 [65106.158491] End test: t_ja5.test_ja5_filters.TestRestartAppWithUpdatedHashJa5h.test_restart_ok Apr 26 10:09:15 192.168.122.209 [65106.170389] Start test: t_ja5.test_ja5_filters.TestRestartAppWithUpdatedHashJa5t.test_hot_reload Apr 26 10:09:16 192.168.122.209 [65107.209620] [tdb] Start Tempesta DB Apr 26 10:09:16 192.168.122.209 [65107.341374] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:09:18 192.168.122.209 [65109.524433] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65109.524433] Maybe that's fine, but it's worth checking the [65109.524433] config - if there is no relations between the [65109.524433] names, then host name confusion attack is possible. Apr 26 10:09:19 192.168.122.209 [65109.803696] [tempesta fw] Configuration processing is completed. Apr 26 10:09:19 192.168.122.209 [65109.921024] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 10:09:19 192.168.122.209 [65110.007239] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000003038fc3d Apr 26 10:09:19 192.168.122.209 [65110.035273] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000d11db51e Apr 26 10:09:19 192.168.122.209 [65110.471206] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6070ba4 Apr 26 10:09:19 192.168.122.209 [65110.498409] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000a968d47d Apr 26 10:09:19 192.168.122.209 [65110.525406] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000007aec66b3 Apr 26 10:09:20 192.168.122.209 [65110.655185] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:09:20 192.168.122.209 [65110.699120] [tempesta fw] Tempesta FW is ready Apr 26 10:09:20 192.168.122.209 [65110.895409] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=1271f8cc2c4c0011" "ja5h=65636588000c0180" Apr 26 10:09:20 192.168.122.209 [65110.986809] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=1271f8cc2c4c0011" "ja5h=65636588000c0180" Apr 26 10:09:20 192.168.122.209 [65111.591917] [tdb] Close table 'client0.tdb' Apr 26 10:09:21 192.168.122.209 [65111.780418] [tdb] Close table 'sessions0.tdb' Apr 26 10:09:24 192.168.122.209 [65114.960591] [tdb] Close table 'cache0.tdb' Apr 26 10:09:24 192.168.122.209 [65115.189623] [tdb] Close table 'filter0.tdb' Apr 26 10:09:25 192.168.122.209 [65115.840728] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 10:09:25 192.168.122.209 [65115.841162] [tempesta fw] modules are stopped Apr 26 10:09:25 192.168.122.209 [65116.161557] [tempesta fw] exiting... Apr 26 10:09:26 192.168.122.209 [65116.853700] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 10:09:26 192.168.122.209 [65116.891167] [tdb] Shutdown Tempesta DB Apr 26 10:09:27 192.168.122.209 [65117.944643] [tdb] Start Tempesta DB Apr 26 10:09:27 192.168.122.209 [65118.078801] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:09:29 192.168.122.209 [65120.216131] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65120.216131] Maybe that's fine, but it's worth checking the [65120.216131] config - if there is no relations between the [65120.216131] names, then host name confusion attack is possible. Apr 26 10:09:29 192.168.122.209 [65120.455235] [tempesta fw] Configuration processing is completed. Apr 26 10:09:29 192.168.122.209 [65120.569620] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 10:09:30 192.168.122.209 [65120.658565] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000003038fc3d Apr 26 10:09:30 192.168.122.209 [65120.687522] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000d11db51e Apr 26 10:09:30 192.168.122.209 [65121.129471] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6070ba4 Apr 26 10:09:30 192.168.122.209 [65121.156848] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000a968d47d Apr 26 10:09:30 192.168.122.209 [65121.183318] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000007aec66b3 Apr 26 10:09:30 192.168.122.209 [65121.371259] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:09:30 192.168.122.209 [65121.471223] [tempesta fw] Tempesta FW is ready Apr 26 10:09:30 192.168.122.209 [65121.574038] [tempesta fw] 127.0.0.1 "tempesta-tech.com" "GET / HTTP/1.1" 200 10 "-" "curl/7.85.0-DEV" "ja5t=1271f8cc2c4c0011" "ja5h=65636588000c0180" Apr 26 10:09:31 192.168.122.209 [65122.123252] [tdb] Close table 'client0.tdb' Apr 26 10:09:31 192.168.122.209 [65122.298988] [tdb] Close table 'sessions0.tdb' Apr 26 10:09:34 192.168.122.209 [65125.494824] [tdb] Close table 'cache0.tdb' Apr 26 10:09:35 192.168.122.209 [65125.719155] [tdb] Close table 'filter0.tdb' Apr 26 10:09:35 192.168.122.209 [65126.401099] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 10:09:35 192.168.122.209 [65126.401540] [tempesta fw] modules are stopped Apr 26 10:09:36 192.168.122.209 [65126.752726] [tempesta fw] exiting... Apr 26 10:09:36 192.168.122.209 [65127.420376] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 10:09:36 192.168.122.209 [65127.454921] [tdb] Shutdown Tempesta DB Apr 26 10:09:37 192.168.122.209 [65127.681503] End test: t_ja5.test_ja5_filters.TestRestartAppWithUpdatedHashJa5t.test_hot_reload Apr 26 10:09:37 192.168.122.209 [65127.702802] Start test: t_ja5.test_ja5_filters.TestRestartAppWithUpdatedHashJa5t.test_restart_ok Apr 26 10:09:38 192.168.122.209 [65128.796480] [tdb] Start Tempesta DB Apr 26 10:09:38 192.168.122.209 [65128.935717] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:09:40 192.168.122.209 [65131.080699] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65131.080699] Maybe that's fine, but it's worth checking the [65131.080699] config - if there is no relations between the [65131.080699] names, then host name confusion attack is possible. Apr 26 10:09:40 192.168.122.209 [65131.283385] [tempesta fw] Configuration processing is completed. Apr 26 10:09:40 192.168.122.209 [65131.419151] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 10:09:40 192.168.122.209 [65131.505788] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000003038fc3d Apr 26 10:09:40 192.168.122.209 [65131.532975] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000d11db51e Apr 26 10:09:41 192.168.122.209 [65131.950713] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6070ba4 Apr 26 10:09:41 192.168.122.209 [65131.976775] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000a968d47d Apr 26 10:09:41 192.168.122.209 [65132.002650] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000007aec66b3 Apr 26 10:09:41 192.168.122.209 [65132.103404] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:09:41 192.168.122.209 [65132.143343] [tempesta fw] Tempesta FW is ready Apr 26 10:09:42 192.168.122.209 [65132.751403] [tdb] Close table 'client0.tdb' Apr 26 10:09:42 192.168.122.209 [65132.944541] [tdb] Close table 'sessions0.tdb' Apr 26 10:09:45 192.168.122.209 [65136.142822] [tdb] Close table 'cache0.tdb' Apr 26 10:09:45 192.168.122.209 [65136.417892] [tdb] Close table 'filter0.tdb' Apr 26 10:09:46 192.168.122.209 [65137.073663] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 10:09:46 192.168.122.209 [65137.074115] [tempesta fw] modules are stopped Apr 26 10:09:46 192.168.122.209 [65137.345069] [tempesta fw] exiting... Apr 26 10:09:47 192.168.122.209 [65138.016549] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 10:09:47 192.168.122.209 [65138.066961] [tdb] Shutdown Tempesta DB Apr 26 10:09:48 192.168.122.209 [65139.156891] [tdb] Start Tempesta DB Apr 26 10:09:48 192.168.122.209 [65139.295284] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:09:50 192.168.122.209 [65141.520838] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65141.520838] Maybe that's fine, but it's worth checking the [65141.520838] config - if there is no relations between the [65141.520838] names, then host name confusion attack is possible. Apr 26 10:09:51 192.168.122.209 [65141.735494] [tempesta fw] Configuration processing is completed. Apr 26 10:09:51 192.168.122.209 [65141.850551] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 10:09:51 192.168.122.209 [65141.936763] [tdb] Opened table /opt/tempesta/db/ja5h_flt0.tdb: size=52428800 rec_size=152 base=000000003038fc3d Apr 26 10:09:51 192.168.122.209 [65141.965021] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000d11db51e Apr 26 10:09:51 192.168.122.209 [65142.386801] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6070ba4 Apr 26 10:09:51 192.168.122.209 [65142.413101] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000a968d47d Apr 26 10:09:51 192.168.122.209 [65142.438921] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000007aec66b3 Apr 26 10:09:51 192.168.122.209 [65142.511632] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:09:51 192.168.122.209 [65142.551487] [tempesta fw] Tempesta FW is ready Apr 26 10:09:52 192.168.122.209 [65143.097864] [tdb] Close table 'client0.tdb' Apr 26 10:09:52 192.168.122.209 [65143.284941] [tdb] Close table 'sessions0.tdb' Apr 26 10:09:55 192.168.122.209 [65146.460517] [tdb] Close table 'cache0.tdb' Apr 26 10:09:56 192.168.122.209 [65146.698856] [tdb] Close table 'filter0.tdb' Apr 26 10:09:56 192.168.122.209 [65147.347924] [tdb] Close table 'ja5h_flt0.tdb' Apr 26 10:09:56 192.168.122.209 [65147.348363] [tempesta fw] modules are stopped Apr 26 10:09:56 192.168.122.209 [65147.624172] [tempesta fw] exiting... Apr 26 10:09:57 192.168.122.209 [65148.311655] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 10:09:57 192.168.122.209 [65148.367063] [tdb] Shutdown Tempesta DB Apr 26 10:09:57 192.168.122.209 [65148.616053] End test: t_ja5.test_ja5_filters.TestRestartAppWithUpdatedHashJa5t.test_restart_ok Apr 26 10:09:58 192.168.122.209 [65148.625963] Start test: t_ja5.test_ja5t.TestJa5tH2.test_hash_for_client_block_by_conn Apr 26 10:09:59 192.168.122.209 [65149.666438] [tdb] Start Tempesta DB Apr 26 10:09:59 192.168.122.209 [65149.810870] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:10:01 192.168.122.209 [65151.741156] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65151.741156] Maybe that's fine, but it's worth checking the [65151.741156] config - if there is no relations between the [65151.741156] names, then host name confusion attack is possible. Apr 26 10:10:01 192.168.122.209 [65151.843776] [tempesta fw] Configuration processing is completed. Apr 26 10:10:01 192.168.122.209 [65151.974733] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 10:10:01 192.168.122.209 [65152.002595] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=000000004552ac63 Apr 26 10:10:01 192.168.122.209 [65152.431595] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=000000002cb2aedf Apr 26 10:10:01 192.168.122.209 [65152.463539] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000f7dd6c76 Apr 26 10:10:01 192.168.122.209 [65152.490942] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000004da5e5e5 Apr 26 10:10:01 192.168.122.209 [65152.535661] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:10:01 192.168.122.209 [65152.575620] [tempesta fw] Tempesta FW is ready Apr 26 10:10:02 192.168.122.209 [65153.107392] [tdb] Close table 'client0.tdb' Apr 26 10:10:02 192.168.122.209 [65153.282523] [tdb] Close table 'sessions0.tdb' Apr 26 10:10:05 192.168.122.209 [65156.443582] [tdb] Close table 'cache0.tdb' Apr 26 10:10:06 192.168.122.209 [65156.695205] [tdb] Close table 'filter0.tdb' Apr 26 10:10:06 192.168.122.209 [65156.695633] [tempesta fw] modules are stopped Apr 26 10:10:06 192.168.122.209 [65156.911718] [tempesta fw] exiting... Apr 26 10:10:06 192.168.122.209 [65157.574586] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 10:10:06 192.168.122.209 [65157.611131] [tdb] Shutdown Tempesta DB Apr 26 10:10:07 192.168.122.209 [65157.818326] End test: t_ja5.test_ja5t.TestJa5tH2.test_hash_for_client_block_by_conn Apr 26 10:10:07 192.168.122.209 [65157.842167] Start test: t_ja5.test_ja5t.TestJa5tH2.test_hash_for_client_block_by_rate Apr 26 10:10:08 192.168.122.209 [65158.951097] [tdb] Start Tempesta DB Apr 26 10:10:08 192.168.122.209 [65159.105680] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:10:10 192.168.122.209 [65160.865507] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65160.865507] Maybe that's fine, but it's worth checking the [65160.865507] config - if there is no relations between the [65160.865507] names, then host name confusion attack is possible. Apr 26 10:10:10 192.168.122.209 [65160.971830] [tempesta fw] Configuration processing is completed. Apr 26 10:10:10 192.168.122.209 [65161.102873] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 10:10:10 192.168.122.209 [65161.139505] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=000000004552ac63 Apr 26 10:10:10 192.168.122.209 [65161.562325] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=000000002cb2aedf Apr 26 10:10:10 192.168.122.209 [65161.588550] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000f7dd6c76 Apr 26 10:10:10 192.168.122.209 [65161.614691] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000004da5e5e5 Apr 26 10:10:11 192.168.122.209 [65161.655760] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:10:11 192.168.122.209 [65161.699704] [tempesta fw] Tempesta FW is ready Apr 26 10:10:11 192.168.122.209 [65162.244120] [tdb] Close table 'client0.tdb' Apr 26 10:10:11 192.168.122.209 [65162.432604] [tdb] Close table 'sessions0.tdb' Apr 26 10:10:15 192.168.122.209 [65165.678420] [tdb] Close table 'cache0.tdb' Apr 26 10:10:15 192.168.122.209 [65165.936491] [tdb] Close table 'filter0.tdb' Apr 26 10:10:15 192.168.122.209 [65165.936914] [tempesta fw] modules are stopped Apr 26 10:10:15 192.168.122.209 [65166.197348] [tempesta fw] exiting... Apr 26 10:10:16 192.168.122.209 [65166.885056] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 10:10:16 192.168.122.209 [65166.930743] [tdb] Shutdown Tempesta DB Apr 26 10:10:16 192.168.122.209 [65167.135228] End test: t_ja5.test_ja5t.TestJa5tH2.test_hash_for_client_block_by_rate Apr 26 10:10:16 192.168.122.209 [65167.153654] Start test: t_ja5.test_ja5t.TestJa5tH2.test_hash_for_client_not_block Apr 26 10:10:17 192.168.122.209 [65168.204843] [tdb] Start Tempesta DB Apr 26 10:10:17 192.168.122.209 [65168.338474] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:10:19 192.168.122.209 [65170.021456] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65170.021456] Maybe that's fine, but it's worth checking the [65170.021456] config - if there is no relations between the [65170.021456] names, then host name confusion attack is possible. Apr 26 10:10:19 192.168.122.209 [65170.132260] [tempesta fw] Configuration processing is completed. Apr 26 10:10:19 192.168.122.209 [65170.263605] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 10:10:19 192.168.122.209 [65170.291568] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=000000004552ac63 Apr 26 10:10:20 192.168.122.209 [65170.713019] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=000000002cb2aedf Apr 26 10:10:20 192.168.122.209 [65170.739637] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000f7dd6c76 Apr 26 10:10:20 192.168.122.209 [65170.767145] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000004da5e5e5 Apr 26 10:10:20 192.168.122.209 [65170.811885] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:10:20 192.168.122.209 [65170.851850] [tempesta fw] Tempesta FW is ready Apr 26 10:10:20 192.168.122.209 [65171.476661] [tdb] Close table 'client0.tdb' Apr 26 10:10:21 192.168.122.209 [65171.677731] [tdb] Close table 'sessions0.tdb' Apr 26 10:10:24 192.168.122.209 [65174.855640] [tdb] Close table 'cache0.tdb' Apr 26 10:10:24 192.168.122.209 [65175.102630] [tdb] Close table 'filter0.tdb' Apr 26 10:10:24 192.168.122.209 [65175.103067] [tempesta fw] modules are stopped Apr 26 10:10:24 192.168.122.209 [65175.314979] [tempesta fw] exiting... Apr 26 10:10:25 192.168.122.209 [65176.002117] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 10:10:25 192.168.122.209 [65176.067601] [tdb] Shutdown Tempesta DB Apr 26 10:10:25 192.168.122.209 [65176.289187] End test: t_ja5.test_ja5t.TestJa5tH2.test_hash_for_client_not_block Apr 26 10:10:25 192.168.122.209 [65176.301407] Start test: t_ja5.test_ja5t.TestJa5tH2.test_hash_not_for_client Apr 26 10:10:26 192.168.122.209 [65177.374435] [tdb] Start Tempesta DB Apr 26 10:10:26 192.168.122.209 [65177.529790] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:10:28 192.168.122.209 [65179.213660] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65179.213660] Maybe that's fine, but it's worth checking the [65179.213660] config - if there is no relations between the [65179.213660] names, then host name confusion attack is possible. Apr 26 10:10:28 192.168.122.209 [65179.332443] [tempesta fw] Configuration processing is completed. Apr 26 10:10:28 192.168.122.209 [65179.445934] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 10:10:28 192.168.122.209 [65179.473886] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=000000004552ac63 Apr 26 10:10:29 192.168.122.209 [65179.893932] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=000000002cb2aedf Apr 26 10:10:29 192.168.122.209 [65179.920345] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000f7dd6c76 Apr 26 10:10:29 192.168.122.209 [65179.946792] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000004da5e5e5 Apr 26 10:10:29 192.168.122.209 [65179.992009] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:10:29 192.168.122.209 [65180.035932] [tempesta fw] Tempesta FW is ready Apr 26 10:10:30 192.168.122.209 [65180.697139] [tdb] Close table 'client0.tdb' Apr 26 10:10:30 192.168.122.209 [65180.884946] [tdb] Close table 'sessions0.tdb' Apr 26 10:10:33 192.168.122.209 [65184.085029] [tdb] Close table 'cache0.tdb' Apr 26 10:10:33 192.168.122.209 [65184.302960] [tdb] Close table 'filter0.tdb' Apr 26 10:10:33 192.168.122.209 [65184.303361] [tempesta fw] modules are stopped Apr 26 10:10:33 192.168.122.209 [65184.560465] [tempesta fw] exiting... Apr 26 10:10:34 192.168.122.209 [65185.217877] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 10:10:34 192.168.122.209 [65185.247704] [tdb] Shutdown Tempesta DB Apr 26 10:10:34 192.168.122.209 [65185.443220] End test: t_ja5.test_ja5t.TestJa5tH2.test_hash_not_for_client Apr 26 10:10:34 192.168.122.209 [65185.469459] Start test: t_ja5.test_ja5t.TestJa5tH2.test_no_hash Apr 26 10:10:35 192.168.122.209 [65186.487201] [tdb] Start Tempesta DB Apr 26 10:10:36 192.168.122.209 [65186.636684] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:10:37 192.168.122.209 [65188.205467] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65188.205467] Maybe that's fine, but it's worth checking the [65188.205467] config - if there is no relations between the [65188.205467] names, then host name confusion attack is possible. Apr 26 10:10:37 192.168.122.209 [65188.292182] [tempesta fw] Configuration processing is completed. Apr 26 10:10:37 192.168.122.209 [65188.360974] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:10:38 192.168.122.209 [65188.790545] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:10:38 192.168.122.209 [65188.826916] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:10:38 192.168.122.209 [65188.853466] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:10:38 192.168.122.209 [65188.900103] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:10:38 192.168.122.209 [65188.944041] [tempesta fw] Tempesta FW is ready Apr 26 10:10:38 192.168.122.209 [65189.544765] [tdb] Close table 'client0.tdb' Apr 26 10:10:39 192.168.122.209 [65189.725424] [tdb] Close table 'sessions0.tdb' Apr 26 10:10:42 192.168.122.209 [65192.923829] [tdb] Close table 'cache0.tdb' Apr 26 10:10:42 192.168.122.209 [65193.153933] [tdb] Close table 'filter0.tdb' Apr 26 10:10:42 192.168.122.209 [65193.154368] [tempesta fw] modules are stopped Apr 26 10:10:42 192.168.122.209 [65193.332367] [tempesta fw] exiting... Apr 26 10:10:42 192.168.122.209 [65193.483625] [tdb] Shutdown Tempesta DB Apr 26 10:10:43 192.168.122.209 [65193.698457] End test: t_ja5.test_ja5t.TestJa5tH2.test_no_hash Apr 26 10:10:43 192.168.122.209 [65193.710859] Start test: t_ja5.test_ja5t.TestJa5tHttp.test_hash_for_client_block_by_conn Apr 26 10:10:44 192.168.122.209 [65194.728830] [tdb] Start Tempesta DB Apr 26 10:10:44 192.168.122.209 [65194.874165] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:10:45 192.168.122.209 [65196.413782] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65196.413782] Maybe that's fine, but it's worth checking the [65196.413782] config - if there is no relations between the [65196.413782] names, then host name confusion attack is possible. Apr 26 10:10:45 192.168.122.209 [65196.528242] [tempesta fw] Configuration processing is completed. Apr 26 10:10:46 192.168.122.209 [65196.655890] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 10:10:46 192.168.122.209 [65196.685757] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=000000004552ac63 Apr 26 10:10:46 192.168.122.209 [65197.115566] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=000000002cb2aedf Apr 26 10:10:46 192.168.122.209 [65197.142990] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000f7dd6c76 Apr 26 10:10:46 192.168.122.209 [65197.170021] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000004da5e5e5 Apr 26 10:10:46 192.168.122.209 [65197.212191] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:10:46 192.168.122.209 [65197.256144] [tempesta fw] Tempesta FW is ready Apr 26 10:10:47 192.168.122.209 [65197.805608] [tdb] Close table 'client0.tdb' Apr 26 10:10:47 192.168.122.209 [65197.991736] [tdb] Close table 'sessions0.tdb' Apr 26 10:10:50 192.168.122.209 [65201.169365] [tdb] Close table 'cache0.tdb' Apr 26 10:10:50 192.168.122.209 [65201.401469] [tdb] Close table 'filter0.tdb' Apr 26 10:10:50 192.168.122.209 [65201.401885] [tempesta fw] modules are stopped Apr 26 10:10:51 192.168.122.209 [65201.633108] [tempesta fw] exiting... Apr 26 10:10:51 192.168.122.209 [65202.289566] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 10:10:51 192.168.122.209 [65202.345219] [tdb] Shutdown Tempesta DB Apr 26 10:10:51 192.168.122.209 [65202.560916] End test: t_ja5.test_ja5t.TestJa5tHttp.test_hash_for_client_block_by_conn Apr 26 10:10:51 192.168.122.209 [65202.572575] Start test: t_ja5.test_ja5t.TestJa5tHttp.test_hash_for_client_block_by_rate Apr 26 10:10:53 192.168.122.209 [65203.638930] [tdb] Start Tempesta DB Apr 26 10:10:53 192.168.122.209 [65203.778416] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:10:54 192.168.122.209 [65205.493202] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65205.493202] Maybe that's fine, but it's worth checking the [65205.493202] config - if there is no relations between the [65205.493202] names, then host name confusion attack is possible. Apr 26 10:10:54 192.168.122.209 [65205.604361] [tempesta fw] Configuration processing is completed. Apr 26 10:10:55 192.168.122.209 [65205.721878] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 10:10:55 192.168.122.209 [65205.748767] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=000000004552ac63 Apr 26 10:10:55 192.168.122.209 [65206.168941] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=000000002cb2aedf Apr 26 10:10:55 192.168.122.209 [65206.195730] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000f7dd6c76 Apr 26 10:10:55 192.168.122.209 [65206.222106] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000004da5e5e5 Apr 26 10:10:55 192.168.122.209 [65206.276304] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:10:55 192.168.122.209 [65206.320269] [tempesta fw] Tempesta FW is ready Apr 26 10:10:56 192.168.122.209 [65206.895308] [tdb] Close table 'client0.tdb' Apr 26 10:10:56 192.168.122.209 [65207.093029] [tdb] Close table 'sessions0.tdb' Apr 26 10:10:59 192.168.122.209 [65210.252052] [tdb] Close table 'cache0.tdb' Apr 26 10:10:59 192.168.122.209 [65210.534557] [tdb] Close table 'filter0.tdb' Apr 26 10:10:59 192.168.122.209 [65210.534972] [tempesta fw] modules are stopped Apr 26 10:11:00 192.168.122.209 [65210.781302] [tempesta fw] exiting... Apr 26 10:11:00 192.168.122.209 [65211.498901] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 10:11:00 192.168.122.209 [65211.551678] [tdb] Shutdown Tempesta DB Apr 26 10:11:01 192.168.122.209 [65211.783661] End test: t_ja5.test_ja5t.TestJa5tHttp.test_hash_for_client_block_by_rate Apr 26 10:11:01 192.168.122.209 [65211.794804] Start test: t_ja5.test_ja5t.TestJa5tHttp.test_hash_for_client_not_block Apr 26 10:11:02 192.168.122.209 [65212.828773] [tdb] Start Tempesta DB Apr 26 10:11:02 192.168.122.209 [65212.979209] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:11:04 192.168.122.209 [65214.678000] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65214.678000] Maybe that's fine, but it's worth checking the [65214.678000] config - if there is no relations between the [65214.678000] names, then host name confusion attack is possible. Apr 26 10:11:04 192.168.122.209 [65214.776453] [tempesta fw] Configuration processing is completed. Apr 26 10:11:04 192.168.122.209 [65214.902932] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 10:11:04 192.168.122.209 [65214.931987] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=000000004552ac63 Apr 26 10:11:04 192.168.122.209 [65215.355065] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=000000002cb2aedf Apr 26 10:11:04 192.168.122.209 [65215.382768] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000f7dd6c76 Apr 26 10:11:04 192.168.122.209 [65215.409783] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000004da5e5e5 Apr 26 10:11:04 192.168.122.209 [65215.492440] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:11:04 192.168.122.209 [65215.532357] [tempesta fw] Tempesta FW is ready Apr 26 10:11:05 192.168.122.209 [65216.108952] [tdb] Close table 'client0.tdb' Apr 26 10:11:05 192.168.122.209 [65216.300405] [tdb] Close table 'sessions0.tdb' Apr 26 10:11:08 192.168.122.209 [65219.515234] [tdb] Close table 'cache0.tdb' Apr 26 10:11:09 192.168.122.209 [65219.744537] [tdb] Close table 'filter0.tdb' Apr 26 10:11:09 192.168.122.209 [65219.744978] [tempesta fw] modules are stopped Apr 26 10:11:09 192.168.122.209 [65219.976703] [tempesta fw] exiting... Apr 26 10:11:10 192.168.122.209 [65220.655563] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 10:11:10 192.168.122.209 [65220.700740] [tdb] Shutdown Tempesta DB Apr 26 10:11:10 192.168.122.209 [65220.931776] End test: t_ja5.test_ja5t.TestJa5tHttp.test_hash_for_client_not_block Apr 26 10:11:10 192.168.122.209 [65220.941937] Start test: t_ja5.test_ja5t.TestJa5tHttp.test_hash_not_for_client Apr 26 10:11:11 192.168.122.209 [65222.018428] [tdb] Start Tempesta DB Apr 26 10:11:11 192.168.122.209 [65222.153851] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:11:13 192.168.122.209 [65223.842160] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65223.842160] Maybe that's fine, but it's worth checking the [65223.842160] config - if there is no relations between the [65223.842160] names, then host name confusion attack is possible. Apr 26 10:11:13 192.168.122.209 [65223.952584] [tempesta fw] Configuration processing is completed. Apr 26 10:11:13 192.168.122.209 [65224.082368] [tdb] Opened table /opt/tempesta/db/ja5t_flt0.tdb: size=52428800 rec_size=152 base=00000000096d5130 Apr 26 10:11:13 192.168.122.209 [65224.110504] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=000000004552ac63 Apr 26 10:11:13 192.168.122.209 [65224.533011] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=000000002cb2aedf Apr 26 10:11:13 192.168.122.209 [65224.560484] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000f7dd6c76 Apr 26 10:11:13 192.168.122.209 [65224.587582] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=000000004da5e5e5 Apr 26 10:11:14 192.168.122.209 [65224.648543] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:11:14 192.168.122.209 [65224.688491] [tempesta fw] Tempesta FW is ready Apr 26 10:11:14 192.168.122.209 [65225.259547] [tdb] Close table 'client0.tdb' Apr 26 10:11:14 192.168.122.209 [65225.458389] [tdb] Close table 'sessions0.tdb' Apr 26 10:11:17 192.168.122.209 [65228.614633] [tdb] Close table 'cache0.tdb' Apr 26 10:11:18 192.168.122.209 [65228.842024] [tdb] Close table 'filter0.tdb' Apr 26 10:11:18 192.168.122.209 [65228.842434] [tempesta fw] modules are stopped Apr 26 10:11:18 192.168.122.209 [65229.085961] [tempesta fw] exiting... Apr 26 10:11:19 192.168.122.209 [65229.806624] [tdb] Close table 'ja5t_flt0.tdb' Apr 26 10:11:19 192.168.122.209 [65229.869884] [tdb] Shutdown Tempesta DB Apr 26 10:11:19 192.168.122.209 [65230.070632] End test: t_ja5.test_ja5t.TestJa5tHttp.test_hash_not_for_client Apr 26 10:11:19 192.168.122.209 [65230.084993] Start test: t_ja5.test_ja5t.TestJa5tHttp.test_no_hash Apr 26 10:11:20 192.168.122.209 [65231.130651] [tdb] Start Tempesta DB Apr 26 10:11:20 192.168.122.209 [65231.264942] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:11:22 192.168.122.209 [65232.858155] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65232.858155] Maybe that's fine, but it's worth checking the [65232.858155] config - if there is no relations between the [65232.858155] names, then host name confusion attack is possible. Apr 26 10:11:22 192.168.122.209 [65232.956724] [tempesta fw] Configuration processing is completed. Apr 26 10:11:22 192.168.122.209 [65233.037133] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:11:22 192.168.122.209 [65233.475344] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:11:22 192.168.122.209 [65233.502066] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:11:22 192.168.122.209 [65233.528989] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:11:22 192.168.122.209 [65233.612582] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:11:23 192.168.122.209 [65233.668599] [tempesta fw] Tempesta FW is ready Apr 26 10:11:23 192.168.122.209 [65234.235339] [tdb] Close table 'client0.tdb' Apr 26 10:11:23 192.168.122.209 [65234.422962] [tdb] Close table 'sessions0.tdb' Apr 26 10:11:26 192.168.122.209 [65237.608177] [tdb] Close table 'cache0.tdb' Apr 26 10:11:27 192.168.122.209 [65237.828417] [tdb] Close table 'filter0.tdb' Apr 26 10:11:27 192.168.122.209 [65237.828888] [tempesta fw] modules are stopped Apr 26 10:11:27 192.168.122.209 [65238.037425] [tempesta fw] exiting... Apr 26 10:11:27 192.168.122.209 [65238.174566] [tdb] Shutdown Tempesta DB Apr 26 10:11:27 192.168.122.209 [65238.375835] End test: t_ja5.test_ja5t.TestJa5tHttp.test_no_hash Apr 26 10:11:27 192.168.122.209 [65238.390780] Start test: t_malformed.test_h2_field_validity.TestH2HeaderFieldResponse.test_ascii_0x00_0x0a_0x0d_in_header_value Apr 26 10:11:28 192.168.122.209 [65239.443708] [tdb] Start Tempesta DB Apr 26 10:11:28 192.168.122.209 [65239.581694] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:11:30 192.168.122.209 [65240.958232] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65240.958232] Maybe that's fine, but it's worth checking the [65240.958232] config - if there is no relations between the [65240.958232] names, then host name confusion attack is possible. Apr 26 10:11:30 192.168.122.209 [65241.080882] [tempesta fw] Configuration processing is completed. Apr 26 10:11:30 192.168.122.209 [65241.142070] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:11:30 192.168.122.209 [65241.582304] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:11:30 192.168.122.209 [65241.610874] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:11:31 192.168.122.209 [65241.638190] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:11:31 192.168.122.209 [65241.684745] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:11:31 192.168.122.209 [65241.736687] [tempesta fw] Tempesta FW is ready Apr 26 10:11:31 192.168.122.209 [65241.945844] [tempesta fw] Warning: Parser error: state=RGen_HdrOtherV input(-0)=0x0('') data_len=1 off=0 Apr 26 10:11:31 192.168.122.209 [65241.948454] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 10:11:35 192.168.122.209 [65246.497294] [tempesta fw] Warning: Parser error: state=RGen_HdrOtherN input(-0)=0xd(' ') data_len=1 off=0 Apr 26 10:11:35 192.168.122.209 [65246.498282] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 10:11:40 192.168.122.209 [65251.015756] [tempesta fw] Warning: Parser error: state=RGen_CR input(-0)=0x75('u') data_len=1 off=0 Apr 26 10:11:40 192.168.122.209 [65251.016690] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 10:11:40 192.168.122.209 [65251.430377] [tdb] Close table 'client0.tdb' Apr 26 10:11:40 192.168.122.209 [65251.621224] [tdb] Close table 'sessions0.tdb' Apr 26 10:11:44 192.168.122.209 [65254.866268] [tdb] Close table 'cache0.tdb' Apr 26 10:11:44 192.168.122.209 [65255.104977] [tdb] Close table 'filter0.tdb' Apr 26 10:11:44 192.168.122.209 [65255.105413] [tempesta fw] modules are stopped Apr 26 10:11:44 192.168.122.209 [65255.300067] [tempesta fw] exiting... Apr 26 10:11:44 192.168.122.209 [65255.412791] [tdb] Shutdown Tempesta DB Apr 26 10:11:45 192.168.122.209 [65255.630589] End test: t_malformed.test_h2_field_validity.TestH2HeaderFieldResponse.test_ascii_0x00_0x0a_0x0d_in_header_value Apr 26 10:11:45 192.168.122.209 [65255.654827] Start test: t_malformed.test_h2_field_validity.TestH2HeaderFieldResponse.test_ascii_from_0x00_to_0x20_in_header_name Apr 26 10:11:46 192.168.122.209 [65256.688200] [tdb] Start Tempesta DB Apr 26 10:11:46 192.168.122.209 [65256.844144] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:11:47 192.168.122.209 [65258.142312] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65258.142312] Maybe that's fine, but it's worth checking the [65258.142312] config - if there is no relations between the [65258.142312] names, then host name confusion attack is possible. Apr 26 10:11:47 192.168.122.209 [65258.276985] [tempesta fw] Configuration processing is completed. Apr 26 10:11:47 192.168.122.209 [65258.341084] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:11:48 192.168.122.209 [65258.844019] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:11:48 192.168.122.209 [65258.874011] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:11:48 192.168.122.209 [65258.904977] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:11:48 192.168.122.209 [65258.944936] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:11:48 192.168.122.209 [65258.984906] [tempesta fw] Tempesta FW is ready Apr 26 10:11:48 192.168.122.209 [65259.198329] [tempesta fw] Warning: Parser error: state=RGen_HdrOtherN input(-0)=0xb(' ') data_len=1 off=0 Apr 26 10:11:48 192.168.122.209 [65259.199320] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 10:11:53 192.168.122.209 [65263.727284] [tempesta fw] Warning: Parser error: state=RGen_HdrOtherN input(-0)=0x64('dr') data_len=19 off=0 Apr 26 10:11:53 192.168.122.209 [65263.728256] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 10:11:53 192.168.122.209 [65264.141256] [tdb] Close table 'client0.tdb' Apr 26 10:11:53 192.168.122.209 [65264.336086] [tdb] Close table 'sessions0.tdb' Apr 26 10:11:56 192.168.122.209 [65267.521704] [tdb] Close table 'cache0.tdb' Apr 26 10:11:57 192.168.122.209 [65267.753067] [tdb] Close table 'filter0.tdb' Apr 26 10:11:57 192.168.122.209 [65267.753488] [tempesta fw] modules are stopped Apr 26 10:11:57 192.168.122.209 [65267.940683] [tempesta fw] exiting... Apr 26 10:11:57 192.168.122.209 [65268.092008] [tdb] Shutdown Tempesta DB Apr 26 10:11:57 192.168.122.209 [65268.306590] End test: t_malformed.test_h2_field_validity.TestH2HeaderFieldResponse.test_ascii_from_0x00_to_0x20_in_header_name Apr 26 10:11:57 192.168.122.209 [65268.320747] Start test: t_malformed.test_h2_field_validity.TestH2HeaderFieldResponse.test_ascii_from_0x7f_to_0xff_in_header_name Apr 26 10:11:58 192.168.122.209 [65269.353967] [tdb] Start Tempesta DB Apr 26 10:11:58 192.168.122.209 [65269.490152] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:12:00 192.168.122.209 [65270.798449] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65270.798449] Maybe that's fine, but it's worth checking the [65270.798449] config - if there is no relations between the [65270.798449] names, then host name confusion attack is possible. Apr 26 10:12:00 192.168.122.209 [65270.925154] [tempesta fw] Configuration processing is completed. Apr 26 10:12:00 192.168.122.209 [65270.998645] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:12:00 192.168.122.209 [65271.487388] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:12:00 192.168.122.209 [65271.517073] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:12:00 192.168.122.209 [65271.547459] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:12:00 192.168.122.209 [65271.597094] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:12:01 192.168.122.209 [65271.645053] [tempesta fw] Tempesta FW is ready Apr 26 10:12:01 192.168.122.209 [65271.858334] [tempesta fw] Warning: Parser error: state=RGen_HdrOtherN input(-0)=0xffffff98('Ш') data_len=1 off=0 Apr 26 10:12:01 192.168.122.209 [65271.859338] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 10:12:05 192.168.122.209 [65276.363846] [tempesta fw] Warning: Parser error: state=RGen_HdrOtherN input(-0)=0x7f('') data_len=1 off=0 Apr 26 10:12:05 192.168.122.209 [65276.366484] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 10:12:06 192.168.122.209 [65276.786564] [tdb] Close table 'client0.tdb' Apr 26 10:12:06 192.168.122.209 [65276.974282] [tdb] Close table 'sessions0.tdb' Apr 26 10:12:09 192.168.122.209 [65280.258737] [tdb] Close table 'cache0.tdb' Apr 26 10:12:09 192.168.122.209 [65280.510394] [tdb] Close table 'filter0.tdb' Apr 26 10:12:09 192.168.122.209 [65280.510877] [tempesta fw] modules are stopped Apr 26 10:12:10 192.168.122.209 [65280.753203] [tempesta fw] exiting... Apr 26 10:12:10 192.168.122.209 [65280.906648] [tdb] Shutdown Tempesta DB Apr 26 10:12:10 192.168.122.209 [65281.132824] End test: t_malformed.test_h2_field_validity.TestH2HeaderFieldResponse.test_ascii_from_0x7f_to_0xff_in_header_name Apr 26 10:12:10 192.168.122.209 [65281.154691] Start test: t_malformed.test_h2_field_validity.TestH2HeaderFieldResponse.test_ascii_uppercase_in_header_name Apr 26 10:12:10 192.168.122.209 [65281.282710] End test: t_malformed.test_h2_field_validity.TestH2HeaderFieldResponse.test_ascii_uppercase_in_header_name Apr 26 10:12:10 192.168.122.209 [65281.299273] Start test: t_malformed.test_h2_malformed_headers.H2EtagAlphabetTest.test_etag_with_x21 Apr 26 10:12:11 192.168.122.209 [65282.538070] [tdb] Start Tempesta DB Apr 26 10:12:12 192.168.122.209 [65282.710215] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:12:13 192.168.122.209 [65284.226595] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65284.226595] Maybe that's fine, but it's worth checking the [65284.226595] config - if there is no relations between the [65284.226595] names, then host name confusion attack is possible. Apr 26 10:12:13 192.168.122.209 [65284.373278] [tempesta fw] Configuration processing is completed. Apr 26 10:12:13 192.168.122.209 [65284.442024] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:12:13 192.168.122.209 [65284.507616] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:12:13 192.168.122.209 [65284.557242] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:12:13 192.168.122.209 [65284.613358] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:12:13 192.168.122.209 [65284.615133] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:12:14 192.168.122.209 [65284.653273] [tempesta fw] Tempesta FW is ready Apr 26 10:12:14 192.168.122.209 [65285.338645] [tdb] Close table 'client0.tdb' Apr 26 10:12:14 192.168.122.209 [65285.565148] [tdb] Close table 'sessions0.tdb' Apr 26 10:12:15 192.168.122.209 [65285.824308] [tdb] Close table 'filter0.tdb' Apr 26 10:12:15 192.168.122.209 [65285.824741] [tempesta fw] modules are stopped Apr 26 10:12:15 192.168.122.209 [65286.037546] [tempesta fw] exiting... Apr 26 10:12:15 192.168.122.209 [65286.182575] [tdb] Shutdown Tempesta DB Apr 26 10:12:15 192.168.122.209 [65286.412466] End test: t_malformed.test_h2_malformed_headers.H2EtagAlphabetTest.test_etag_with_x21 Apr 26 10:12:15 192.168.122.209 [65286.429725] Start test: t_malformed.test_h2_malformed_headers.H2EtagAlphabetTest.test_etag_with_x23 Apr 26 10:12:17 192.168.122.209 [65287.740492] [tdb] Start Tempesta DB Apr 26 10:12:17 192.168.122.209 [65287.892666] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:12:18 192.168.122.209 [65288.686740] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65288.686740] Maybe that's fine, but it's worth checking the [65288.686740] config - if there is no relations between the [65288.686740] names, then host name confusion attack is possible. Apr 26 10:12:18 192.168.122.209 [65288.833388] [tempesta fw] Configuration processing is completed. Apr 26 10:12:18 192.168.122.209 [65288.893031] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:12:18 192.168.122.209 [65288.927419] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:12:18 192.168.122.209 [65288.969853] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:12:18 192.168.122.209 [65289.017333] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:12:18 192.168.122.209 [65289.019097] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:12:18 192.168.122.209 [65289.069279] [tempesta fw] Tempesta FW is ready Apr 26 10:12:19 192.168.122.209 [65289.741005] [tdb] Close table 'client0.tdb' Apr 26 10:12:19 192.168.122.209 [65289.932637] [tdb] Close table 'sessions0.tdb' Apr 26 10:12:19 192.168.122.209 [65290.160275] [tdb] Close table 'filter0.tdb' Apr 26 10:12:19 192.168.122.209 [65290.160694] [tempesta fw] modules are stopped Apr 26 10:12:19 192.168.122.209 [65290.358371] [tempesta fw] exiting... Apr 26 10:12:19 192.168.122.209 [65290.516132] [tdb] Shutdown Tempesta DB Apr 26 10:12:20 192.168.122.209 [65290.778790] End test: t_malformed.test_h2_malformed_headers.H2EtagAlphabetTest.test_etag_with_x23 Apr 26 10:12:20 192.168.122.209 [65290.797820] Start test: t_malformed.test_h2_malformed_headers.H2EtagAlphabetTest.test_etag_with_x7f Apr 26 10:12:21 192.168.122.209 [65292.140860] [tdb] Start Tempesta DB Apr 26 10:12:21 192.168.122.209 [65292.275805] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:12:22 192.168.122.209 [65293.074936] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65293.074936] Maybe that's fine, but it's worth checking the [65293.074936] config - if there is no relations between the [65293.074936] names, then host name confusion attack is possible. Apr 26 10:12:22 192.168.122.209 [65293.257444] [tempesta fw] Configuration processing is completed. Apr 26 10:12:22 192.168.122.209 [65293.309646] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:12:22 192.168.122.209 [65293.338176] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:12:22 192.168.122.209 [65293.369968] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:12:22 192.168.122.209 [65293.417379] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:12:22 192.168.122.209 [65293.419195] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:12:22 192.168.122.209 [65293.457323] [tempesta fw] Tempesta FW is ready Apr 26 10:12:23 192.168.122.209 [65293.668901] [tempesta fw] Warning: Parser error: state=Resp_HdrEtagV input(-0)=0x7f('') data_len=1 off=0 Apr 26 10:12:23 192.168.122.209 [65293.669865] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 10:12:23 192.168.122.209 [65294.134637] [tdb] Close table 'client0.tdb' Apr 26 10:12:23 192.168.122.209 [65294.312891] [tdb] Close table 'sessions0.tdb' Apr 26 10:12:23 192.168.122.209 [65294.587274] [tdb] Close table 'filter0.tdb' Apr 26 10:12:23 192.168.122.209 [65294.587692] [tempesta fw] modules are stopped Apr 26 10:12:24 192.168.122.209 [65294.802720] [tempesta fw] exiting... Apr 26 10:12:24 192.168.122.209 [65294.960180] [tdb] Shutdown Tempesta DB Apr 26 10:12:24 192.168.122.209 [65295.199548] End test: t_malformed.test_h2_malformed_headers.H2EtagAlphabetTest.test_etag_with_x7f Apr 26 10:12:24 192.168.122.209 [65295.216027] Start test: t_malformed.test_h2_malformed_headers.H2EtagAlphabetTest.test_etag_with_xf7 Apr 26 10:12:25 192.168.122.209 [65296.418069] [tdb] Start Tempesta DB Apr 26 10:12:25 192.168.122.209 [65296.565819] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:12:26 192.168.122.209 [65297.330770] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65297.330770] Maybe that's fine, but it's worth checking the [65297.330770] config - if there is no relations between the [65297.330770] names, then host name confusion attack is possible. Apr 26 10:12:26 192.168.122.209 [65297.489484] [tempesta fw] Configuration processing is completed. Apr 26 10:12:26 192.168.122.209 [65297.552060] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:12:26 192.168.122.209 [65297.585400] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:12:26 192.168.122.209 [65297.616576] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:12:27 192.168.122.209 [65297.665429] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:12:27 192.168.122.209 [65297.667175] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:12:27 192.168.122.209 [65297.705382] [tempesta fw] Tempesta FW is ready Apr 26 10:12:27 192.168.122.209 [65298.397750] [tdb] Close table 'client0.tdb' Apr 26 10:12:27 192.168.122.209 [65298.603529] [tdb] Close table 'sessions0.tdb' Apr 26 10:12:28 192.168.122.209 [65298.868988] [tdb] Close table 'filter0.tdb' Apr 26 10:12:28 192.168.122.209 [65298.869799] [tempesta fw] modules are stopped Apr 26 10:12:28 192.168.122.209 [65299.102098] [tempesta fw] exiting... Apr 26 10:12:28 192.168.122.209 [65299.221143] [tdb] Shutdown Tempesta DB Apr 26 10:12:28 192.168.122.209 [65299.433279] End test: t_malformed.test_h2_malformed_headers.H2EtagAlphabetTest.test_etag_with_xf7 Apr 26 10:12:28 192.168.122.209 [65299.447629] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsTest.test_accept Apr 26 10:12:30 192.168.122.209 [65300.627167] [tdb] Start Tempesta DB Apr 26 10:12:30 192.168.122.209 [65300.781069] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:12:30 192.168.122.209 [65301.522837] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65301.522837] Maybe that's fine, but it's worth checking the [65301.522837] config - if there is no relations between the [65301.522837] names, then host name confusion attack is possible. Apr 26 10:12:31 192.168.122.209 [65301.677512] [tempesta fw] Configuration processing is completed. Apr 26 10:12:31 192.168.122.209 [65301.735584] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:12:31 192.168.122.209 [65301.772392] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:12:31 192.168.122.209 [65301.809432] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:12:31 192.168.122.209 [65301.861478] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:12:31 192.168.122.209 [65301.863203] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:12:31 192.168.122.209 [65301.909357] [tempesta fw] Tempesta FW is ready Apr 26 10:12:31 192.168.122.209 [65302.108435] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrAcceptV input=0x69('invalid'), len=7, off=0 Apr 26 10:12:31 192.168.122.209 [65302.530862] [tdb] Close table 'client0.tdb' Apr 26 10:12:32 192.168.122.209 [65302.718907] [tdb] Close table 'sessions0.tdb' Apr 26 10:12:32 192.168.122.209 [65302.970363] [tdb] Close table 'filter0.tdb' Apr 26 10:12:32 192.168.122.209 [65302.970806] [tempesta fw] modules are stopped Apr 26 10:12:32 192.168.122.209 [65303.186374] [tempesta fw] exiting... Apr 26 10:12:32 192.168.122.209 [65303.307063] [tdb] Shutdown Tempesta DB Apr 26 10:12:32 192.168.122.209 [65303.542872] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsTest.test_accept Apr 26 10:12:32 192.168.122.209 [65303.559012] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsTest.test_expect Apr 26 10:12:34 192.168.122.209 [65304.786604] [tdb] Start Tempesta DB Apr 26 10:12:34 192.168.122.209 [65304.927172] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:12:35 192.168.122.209 [65305.678805] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65305.678805] Maybe that's fine, but it's worth checking the [65305.678805] config - if there is no relations between the [65305.678805] names, then host name confusion attack is possible. Apr 26 10:12:35 192.168.122.209 [65305.845706] [tempesta fw] Configuration processing is completed. Apr 26 10:12:35 192.168.122.209 [65305.903384] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:12:35 192.168.122.209 [65305.938708] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:12:35 192.168.122.209 [65305.974795] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:12:35 192.168.122.209 [65306.021523] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:12:35 192.168.122.209 [65306.023231] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:12:35 192.168.122.209 [65306.085469] [tempesta fw] Tempesta FW is ready Apr 26 10:12:35 192.168.122.209 [65306.287114] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrExpectV input=0x31('100-continue'), len=12, off=0 Apr 26 10:12:36 192.168.122.209 [65306.719793] [tdb] Close table 'client0.tdb' Apr 26 10:12:36 192.168.122.209 [65306.923875] [tdb] Close table 'sessions0.tdb' Apr 26 10:12:36 192.168.122.209 [65307.144734] [tdb] Close table 'filter0.tdb' Apr 26 10:12:36 192.168.122.209 [65307.145194] [tempesta fw] modules are stopped Apr 26 10:12:36 192.168.122.209 [65307.403156] [tempesta fw] exiting... Apr 26 10:12:36 192.168.122.209 [65307.523063] [tdb] Shutdown Tempesta DB Apr 26 10:12:37 192.168.122.209 [65307.770096] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsTest.test_expect Apr 26 10:12:37 192.168.122.209 [65307.787588] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsTest.test_expect_invalid Apr 26 10:12:38 192.168.122.209 [65309.059606] [tdb] Start Tempesta DB Apr 26 10:12:38 192.168.122.209 [65309.204753] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:12:39 192.168.122.209 [65310.082912] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65310.082912] Maybe that's fine, but it's worth checking the [65310.082912] config - if there is no relations between the [65310.082912] names, then host name confusion attack is possible. Apr 26 10:12:39 192.168.122.209 [65310.221532] [tempesta fw] Configuration processing is completed. Apr 26 10:12:39 192.168.122.209 [65310.280247] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:12:39 192.168.122.209 [65310.314826] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:12:39 192.168.122.209 [65310.349000] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:12:39 192.168.122.209 [65310.401595] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:12:39 192.168.122.209 [65310.403277] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:12:39 192.168.122.209 [65310.449526] [tempesta fw] Tempesta FW is ready Apr 26 10:12:40 192.168.122.209 [65310.652667] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrExpectV input=0x69('invalid'), len=7, off=0 Apr 26 10:12:40 192.168.122.209 [65311.111435] [tdb] Close table 'client0.tdb' Apr 26 10:12:40 192.168.122.209 [65311.308821] [tdb] Close table 'sessions0.tdb' Apr 26 10:12:40 192.168.122.209 [65311.584846] [tdb] Close table 'filter0.tdb' Apr 26 10:12:40 192.168.122.209 [65311.585449] [tempesta fw] modules are stopped Apr 26 10:12:41 192.168.122.209 [65311.815931] [tempesta fw] exiting... Apr 26 10:12:41 192.168.122.209 [65311.933665] [tdb] Shutdown Tempesta DB Apr 26 10:12:41 192.168.122.209 [65312.147003] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsTest.test_expect_invalid Apr 26 10:12:41 192.168.122.209 [65312.163019] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsTest.test_host Apr 26 10:12:42 192.168.122.209 [65313.509462] [tdb] Start Tempesta DB Apr 26 10:12:43 192.168.122.209 [65313.658367] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:12:43 192.168.122.209 [65314.422932] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65314.422932] Maybe that's fine, but it's worth checking the [65314.422932] config - if there is no relations between the [65314.422932] names, then host name confusion attack is possible. Apr 26 10:12:43 192.168.122.209 [65314.557678] [tempesta fw] Configuration processing is completed. Apr 26 10:12:43 192.168.122.209 [65314.613395] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:12:44 192.168.122.209 [65314.646552] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:12:44 192.168.122.209 [65314.677043] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:12:44 192.168.122.209 [65314.725654] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:12:44 192.168.122.209 [65314.727356] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:12:44 192.168.122.209 [65314.773575] [tempesta fw] Tempesta FW is ready Apr 26 10:12:44 192.168.122.209 [65314.979894] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrPsAuthorityV input=0x68('http://'), len=7, off=0 Apr 26 10:12:44 192.168.122.209 [65315.446415] [tdb] Close table 'client0.tdb' Apr 26 10:12:45 192.168.122.209 [65315.631989] [tdb] Close table 'sessions0.tdb' Apr 26 10:12:45 192.168.122.209 [65315.873912] [tdb] Close table 'filter0.tdb' Apr 26 10:12:45 192.168.122.209 [65315.874327] [tempesta fw] modules are stopped Apr 26 10:12:45 192.168.122.209 [65316.121077] [tempesta fw] exiting... Apr 26 10:12:45 192.168.122.209 [65316.264816] [tdb] Shutdown Tempesta DB Apr 26 10:12:45 192.168.122.209 [65316.497592] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsTest.test_host Apr 26 10:12:45 192.168.122.209 [65316.508532] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsTest.test_if_none_match Apr 26 10:12:47 192.168.122.209 [65317.714989] [tdb] Start Tempesta DB Apr 26 10:12:47 192.168.122.209 [65317.859530] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:12:48 192.168.122.209 [65318.675051] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65318.675051] Maybe that's fine, but it's worth checking the [65318.675051] config - if there is no relations between the [65318.675051] names, then host name confusion attack is possible. Apr 26 10:12:48 192.168.122.209 [65318.817657] [tempesta fw] Configuration processing is completed. Apr 26 10:12:48 192.168.122.209 [65318.883724] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:12:48 192.168.122.209 [65318.925082] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:12:48 192.168.122.209 [65318.962353] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:12:48 192.168.122.209 [65319.009672] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:12:48 192.168.122.209 [65319.011367] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:12:48 192.168.122.209 [65319.049643] [tempesta fw] Tempesta FW is ready Apr 26 10:12:48 192.168.122.209 [65319.258748] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrIf_None_MatchV input=0x71('quotes'), len=6, off=0 Apr 26 10:12:49 192.168.122.209 [65319.682955] [tdb] Close table 'client0.tdb' Apr 26 10:12:49 192.168.122.209 [65319.870104] [tdb] Close table 'sessions0.tdb' Apr 26 10:12:49 192.168.122.209 [65320.123370] [tdb] Close table 'filter0.tdb' Apr 26 10:12:49 192.168.122.209 [65320.123808] [tempesta fw] modules are stopped Apr 26 10:12:49 192.168.122.209 [65320.316646] [tempesta fw] exiting... Apr 26 10:12:49 192.168.122.209 [65320.440844] [tdb] Shutdown Tempesta DB Apr 26 10:12:50 192.168.122.209 [65320.674149] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsTest.test_if_none_match Apr 26 10:12:50 192.168.122.209 [65320.683884] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsTest.test_missing_name Apr 26 10:12:51 192.168.122.209 [65321.936349] [tdb] Start Tempesta DB Apr 26 10:12:51 192.168.122.209 [65322.081230] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:12:52 192.168.122.209 [65322.863027] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65322.863027] Maybe that's fine, but it's worth checking the [65322.863027] config - if there is no relations between the [65322.863027] names, then host name confusion attack is possible. Apr 26 10:12:52 192.168.122.209 [65322.993765] [tempesta fw] Configuration processing is completed. Apr 26 10:12:52 192.168.122.209 [65323.047029] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:12:52 192.168.122.209 [65323.076287] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:12:52 192.168.122.209 [65323.105474] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:12:52 192.168.122.209 [65323.153738] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:12:52 192.168.122.209 [65323.155434] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:12:52 192.168.122.209 [65323.193631] [tempesta fw] Tempesta FW is ready Apr 26 10:12:53 192.168.122.209 [65323.813319] [tdb] Close table 'client0.tdb' Apr 26 10:12:53 192.168.122.209 [65324.008489] [tdb] Close table 'sessions0.tdb' Apr 26 10:12:53 192.168.122.209 [65324.253101] [tdb] Close table 'filter0.tdb' Apr 26 10:12:53 192.168.122.209 [65324.253561] [tempesta fw] modules are stopped Apr 26 10:12:53 192.168.122.209 [65324.469987] [tempesta fw] exiting... Apr 26 10:12:54 192.168.122.209 [65324.630321] [tdb] Shutdown Tempesta DB Apr 26 10:12:54 192.168.122.209 [65324.850888] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsTest.test_missing_name Apr 26 10:12:54 192.168.122.209 [65324.874763] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsTest.test_te Apr 26 10:12:55 192.168.122.209 [65326.116271] [tdb] Start Tempesta DB Apr 26 10:12:55 192.168.122.209 [65326.252834] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:12:56 192.168.122.209 [65327.007121] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65327.007121] Maybe that's fine, but it's worth checking the [65327.007121] config - if there is no relations between the [65327.007121] names, then host name confusion attack is possible. Apr 26 10:12:56 192.168.122.209 [65327.138085] [tempesta fw] Configuration processing is completed. Apr 26 10:12:56 192.168.122.209 [65327.205694] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:12:56 192.168.122.209 [65327.240621] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:12:56 192.168.122.209 [65327.272502] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:12:56 192.168.122.209 [65327.313790] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:12:56 192.168.122.209 [65327.315484] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:12:56 192.168.122.209 [65327.361779] [tempesta fw] Tempesta FW is ready Apr 26 10:12:56 192.168.122.209 [65327.574646] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrTeV input=0x69('invalid'), len=7, off=0 Apr 26 10:12:57 192.168.122.209 [65328.034093] [tdb] Close table 'client0.tdb' Apr 26 10:12:57 192.168.122.209 [65328.228433] [tdb] Close table 'sessions0.tdb' Apr 26 10:12:57 192.168.122.209 [65328.468345] [tdb] Close table 'filter0.tdb' Apr 26 10:12:57 192.168.122.209 [65328.468765] [tempesta fw] modules are stopped Apr 26 10:12:58 192.168.122.209 [65328.681223] [tempesta fw] exiting... Apr 26 10:12:58 192.168.122.209 [65328.828451] [tdb] Shutdown Tempesta DB Apr 26 10:12:58 192.168.122.209 [65329.027659] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsTest.test_te Apr 26 10:12:58 192.168.122.209 [65329.049725] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsTest.test_transfer_encoding Apr 26 10:12:59 192.168.122.209 [65330.277232] [tdb] Start Tempesta DB Apr 26 10:12:59 192.168.122.209 [65330.412183] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:13:00 192.168.122.209 [65331.207151] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65331.207151] Maybe that's fine, but it's worth checking the [65331.207151] config - if there is no relations between the [65331.207151] names, then host name confusion attack is possible. Apr 26 10:13:00 192.168.122.209 [65331.353892] [tempesta fw] Configuration processing is completed. Apr 26 10:13:00 192.168.122.209 [65331.413356] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:13:00 192.168.122.209 [65331.447022] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:13:00 192.168.122.209 [65331.478375] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:13:00 192.168.122.209 [65331.517823] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:13:00 192.168.122.209 [65331.519558] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:13:00 192.168.122.209 [65331.557791] [tempesta fw] Tempesta FW is ready Apr 26 10:13:01 192.168.122.209 [65331.746537] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrTeV input=0x6e('nottoken'), len=8, off=0 Apr 26 10:13:01 192.168.122.209 [65332.206104] [tdb] Close table 'client0.tdb' Apr 26 10:13:01 192.168.122.209 [65332.393305] [tdb] Close table 'sessions0.tdb' Apr 26 10:13:02 192.168.122.209 [65332.629451] [tdb] Close table 'filter0.tdb' Apr 26 10:13:02 192.168.122.209 [65332.630106] [tempesta fw] modules are stopped Apr 26 10:13:02 192.168.122.209 [65332.814479] [tempesta fw] exiting... Apr 26 10:13:02 192.168.122.209 [65332.954704] [tdb] Shutdown Tempesta DB Apr 26 10:13:02 192.168.122.209 [65333.163432] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsTest.test_transfer_encoding Apr 26 10:13:02 192.168.122.209 [65333.178753] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsTest.test_upgrade Apr 26 10:13:03 192.168.122.209 [65334.455210] [tdb] Start Tempesta DB Apr 26 10:13:03 192.168.122.209 [65334.602355] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:13:04 192.168.122.209 [65335.359238] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65335.359238] Maybe that's fine, but it's worth checking the [65335.359238] config - if there is no relations between the [65335.359238] names, then host name confusion attack is possible. Apr 26 10:13:04 192.168.122.209 [65335.489984] [tempesta fw] Configuration processing is completed. Apr 26 10:13:04 192.168.122.209 [65335.541001] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:13:04 192.168.122.209 [65335.568825] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:13:04 192.168.122.209 [65335.596538] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:13:05 192.168.122.209 [65335.637870] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:13:05 192.168.122.209 [65335.639583] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:13:05 192.168.122.209 [65335.677830] [tempesta fw] Tempesta FW is ready Apr 26 10:13:05 192.168.122.209 [65335.882219] [tempesta fw] Warning: HTTP/2 request dropped: state=Req_HdrUpgrade input=0x75('upgrade'), len=7, off=0 Apr 26 10:13:05 192.168.122.209 [65336.315090] [tdb] Close table 'client0.tdb' Apr 26 10:13:05 192.168.122.209 [65336.513774] [tdb] Close table 'sessions0.tdb' Apr 26 10:13:06 192.168.122.209 [65336.769618] [tdb] Close table 'filter0.tdb' Apr 26 10:13:06 192.168.122.209 [65336.770061] [tempesta fw] modules are stopped Apr 26 10:13:06 192.168.122.209 [65336.967101] [tempesta fw] exiting... Apr 26 10:13:06 192.168.122.209 [65337.117257] [tdb] Shutdown Tempesta DB Apr 26 10:13:06 192.168.122.209 [65337.389891] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsTest.test_upgrade Apr 26 10:13:06 192.168.122.209 [65337.400004] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_accept_charset Apr 26 10:13:07 192.168.122.209 [65338.489856] [tdb] Start Tempesta DB Apr 26 10:13:08 192.168.122.209 [65338.630311] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:13:08 192.168.122.209 [65339.411299] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65339.411299] Maybe that's fine, but it's worth checking the [65339.411299] config - if there is no relations between the [65339.411299] names, then host name confusion attack is possible. Apr 26 10:13:08 192.168.122.209 [65339.546423] [tempesta fw] Configuration processing is completed. Apr 26 10:13:08 192.168.122.209 [65339.611234] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:13:09 192.168.122.209 [65339.650867] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:13:09 192.168.122.209 [65339.686825] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:13:09 192.168.122.209 [65339.749860] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:13:09 192.168.122.209 [65339.751549] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:13:09 192.168.122.209 [65339.793898] [tempesta fw] Tempesta FW is ready Apr 26 10:13:09 192.168.122.209 [65340.396881] [tdb] Close table 'client0.tdb' Apr 26 10:13:09 192.168.122.209 [65340.588564] [tdb] Close table 'sessions0.tdb' Apr 26 10:13:10 192.168.122.209 [65340.811002] [tdb] Close table 'filter0.tdb' Apr 26 10:13:10 192.168.122.209 [65340.811426] [tempesta fw] modules are stopped Apr 26 10:13:10 192.168.122.209 [65340.990569] [tempesta fw] exiting... Apr 26 10:13:10 192.168.122.209 [65341.120961] [tdb] Shutdown Tempesta DB Apr 26 10:13:10 192.168.122.209 [65341.366115] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_accept_charset Apr 26 10:13:10 192.168.122.209 [65341.378205] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_accept_encoding Apr 26 10:13:11 192.168.122.209 [65342.534434] [tdb] Start Tempesta DB Apr 26 10:13:12 192.168.122.209 [65342.690050] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:13:12 192.168.122.209 [65343.447332] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65343.447332] Maybe that's fine, but it's worth checking the [65343.447332] config - if there is no relations between the [65343.447332] names, then host name confusion attack is possible. Apr 26 10:13:12 192.168.122.209 [65343.578035] [tempesta fw] Configuration processing is completed. Apr 26 10:13:13 192.168.122.209 [65343.630390] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:13:13 192.168.122.209 [65343.661378] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:13:13 192.168.122.209 [65343.695480] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:13:13 192.168.122.209 [65343.734018] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:13:13 192.168.122.209 [65343.736656] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:13:13 192.168.122.209 [65343.773931] [tempesta fw] Tempesta FW is ready Apr 26 10:13:13 192.168.122.209 [65344.399108] [tdb] Close table 'client0.tdb' Apr 26 10:13:13 192.168.122.209 [65344.589697] [tdb] Close table 'sessions0.tdb' Apr 26 10:13:14 192.168.122.209 [65344.827445] [tdb] Close table 'filter0.tdb' Apr 26 10:13:14 192.168.122.209 [65344.827873] [tempesta fw] modules are stopped Apr 26 10:13:14 192.168.122.209 [65345.042722] [tempesta fw] exiting... Apr 26 10:13:14 192.168.122.209 [65345.174485] [tdb] Shutdown Tempesta DB Apr 26 10:13:14 192.168.122.209 [65345.447259] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_accept_encoding Apr 26 10:13:14 192.168.122.209 [65345.461543] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_accept_language Apr 26 10:13:16 192.168.122.209 [65346.687942] [tdb] Start Tempesta DB Apr 26 10:13:16 192.168.122.209 [65346.837438] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:13:16 192.168.122.209 [65347.571305] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65347.571305] Maybe that's fine, but it's worth checking the [65347.571305] config - if there is no relations between the [65347.571305] names, then host name confusion attack is possible. Apr 26 10:13:17 192.168.122.209 [65347.714049] [tempesta fw] Configuration processing is completed. Apr 26 10:13:17 192.168.122.209 [65347.775513] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:13:17 192.168.122.209 [65347.810832] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:13:17 192.168.122.209 [65347.848550] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:13:17 192.168.122.209 [65347.889973] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:13:17 192.168.122.209 [65347.891665] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:13:17 192.168.122.209 [65347.929905] [tempesta fw] Tempesta FW is ready Apr 26 10:13:17 192.168.122.209 [65348.576573] [tdb] Close table 'client0.tdb' Apr 26 10:13:18 192.168.122.209 [65348.770129] [tdb] Close table 'sessions0.tdb' Apr 26 10:13:18 192.168.122.209 [65349.002710] [tdb] Close table 'filter0.tdb' Apr 26 10:13:18 192.168.122.209 [65349.003149] [tempesta fw] modules are stopped Apr 26 10:13:18 192.168.122.209 [65349.194564] [tempesta fw] exiting... Apr 26 10:13:18 192.168.122.209 [65349.326951] [tdb] Shutdown Tempesta DB Apr 26 10:13:18 192.168.122.209 [65349.546437] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_accept_language Apr 26 10:13:18 192.168.122.209 [65349.571887] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_content_encoding Apr 26 10:13:20 192.168.122.209 [65350.664707] [tdb] Start Tempesta DB Apr 26 10:13:20 192.168.122.209 [65350.822775] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:13:20 192.168.122.209 [65351.591437] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65351.591437] Maybe that's fine, but it's worth checking the [65351.591437] config - if there is no relations between the [65351.591437] names, then host name confusion attack is possible. Apr 26 10:13:21 192.168.122.209 [65351.758115] [tempesta fw] Configuration processing is completed. Apr 26 10:13:21 192.168.122.209 [65351.813114] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:13:21 192.168.122.209 [65351.845285] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:13:21 192.168.122.209 [65351.875793] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:13:21 192.168.122.209 [65351.918069] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:13:21 192.168.122.209 [65351.919753] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:13:21 192.168.122.209 [65351.966040] [tempesta fw] Tempesta FW is ready Apr 26 10:13:21 192.168.122.209 [65352.602326] [tdb] Close table 'client0.tdb' Apr 26 10:13:22 192.168.122.209 [65352.801621] [tdb] Close table 'sessions0.tdb' Apr 26 10:13:22 192.168.122.209 [65353.042513] [tdb] Close table 'filter0.tdb' Apr 26 10:13:22 192.168.122.209 [65353.042951] [tempesta fw] modules are stopped Apr 26 10:13:22 192.168.122.209 [65353.222438] [tempesta fw] exiting... Apr 26 10:13:22 192.168.122.209 [65353.346944] [tdb] Shutdown Tempesta DB Apr 26 10:13:22 192.168.122.209 [65353.556762] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_content_encoding Apr 26 10:13:22 192.168.122.209 [65353.568895] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_content_language Apr 26 10:13:24 192.168.122.209 [65354.796368] [tdb] Start Tempesta DB Apr 26 10:13:24 192.168.122.209 [65354.952000] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:13:25 192.168.122.209 [65355.707091] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65355.707091] Maybe that's fine, but it's worth checking the [65355.707091] config - if there is no relations between the [65355.707091] names, then host name confusion attack is possible. Apr 26 10:13:25 192.168.122.209 [65355.838139] [tempesta fw] Configuration processing is completed. Apr 26 10:13:25 192.168.122.209 [65355.900167] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:13:25 192.168.122.209 [65355.934034] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:13:25 192.168.122.209 [65355.968090] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:13:25 192.168.122.209 [65356.006065] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:13:25 192.168.122.209 [65356.007082] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:13:25 192.168.122.209 [65356.050071] [tempesta fw] Tempesta FW is ready Apr 26 10:13:26 192.168.122.209 [65356.663417] [tdb] Close table 'client0.tdb' Apr 26 10:13:26 192.168.122.209 [65356.852730] [tdb] Close table 'sessions0.tdb' Apr 26 10:13:26 192.168.122.209 [65357.082329] [tdb] Close table 'filter0.tdb' Apr 26 10:13:26 192.168.122.209 [65357.082728] [tempesta fw] modules are stopped Apr 26 10:13:26 192.168.122.209 [65357.300548] [tempesta fw] exiting... Apr 26 10:13:26 192.168.122.209 [65357.448599] [tdb] Shutdown Tempesta DB Apr 26 10:13:27 192.168.122.209 [65357.674975] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_content_language Apr 26 10:13:27 192.168.122.209 [65357.691227] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_content_location Apr 26 10:13:28 192.168.122.209 [65358.960939] [tdb] Start Tempesta DB Apr 26 10:13:28 192.168.122.209 [65359.104987] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:13:29 192.168.122.209 [65359.839474] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65359.839474] Maybe that's fine, but it's worth checking the [65359.839474] config - if there is no relations between the [65359.839474] names, then host name confusion attack is possible. Apr 26 10:13:29 192.168.122.209 [65359.994336] [tempesta fw] Configuration processing is completed. Apr 26 10:13:29 192.168.122.209 [65360.053993] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:13:29 192.168.122.209 [65360.085689] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:13:29 192.168.122.209 [65360.115486] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:13:29 192.168.122.209 [65360.166194] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:13:29 192.168.122.209 [65360.167902] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:13:29 192.168.122.209 [65360.206129] [tempesta fw] Tempesta FW is ready Apr 26 10:13:30 192.168.122.209 [65360.827949] [tdb] Close table 'client0.tdb' Apr 26 10:13:30 192.168.122.209 [65361.040703] [tdb] Close table 'sessions0.tdb' Apr 26 10:13:30 192.168.122.209 [65361.311000] [tdb] Close table 'filter0.tdb' Apr 26 10:13:30 192.168.122.209 [65361.311439] [tempesta fw] modules are stopped Apr 26 10:13:30 192.168.122.209 [65361.502459] [tempesta fw] exiting... Apr 26 10:13:31 192.168.122.209 [65361.633808] [tdb] Shutdown Tempesta DB Apr 26 10:13:31 192.168.122.209 [65361.841831] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_content_location Apr 26 10:13:31 192.168.122.209 [65361.853161] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_content_range Apr 26 10:13:32 192.168.122.209 [65362.988488] [tdb] Start Tempesta DB Apr 26 10:13:32 192.168.122.209 [65363.140987] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:13:33 192.168.122.209 [65363.915555] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65363.915555] Maybe that's fine, but it's worth checking the [65363.915555] config - if there is no relations between the [65363.915555] names, then host name confusion attack is possible. Apr 26 10:13:33 192.168.122.209 [65364.054282] [tempesta fw] Configuration processing is completed. Apr 26 10:13:33 192.168.122.209 [65364.118791] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:13:33 192.168.122.209 [65364.159097] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:13:33 192.168.122.209 [65364.195362] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:13:33 192.168.122.209 [65364.246241] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:13:33 192.168.122.209 [65364.247968] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:13:33 192.168.122.209 [65364.286235] [tempesta fw] Tempesta FW is ready Apr 26 10:13:34 192.168.122.209 [65364.956941] [tdb] Close table 'client0.tdb' Apr 26 10:13:34 192.168.122.209 [65365.164078] [tdb] Close table 'sessions0.tdb' Apr 26 10:13:34 192.168.122.209 [65365.424214] [tdb] Close table 'filter0.tdb' Apr 26 10:13:34 192.168.122.209 [65365.424625] [tempesta fw] modules are stopped Apr 26 10:13:34 192.168.122.209 [65365.622359] [tempesta fw] exiting... Apr 26 10:13:35 192.168.122.209 [65365.745332] [tdb] Shutdown Tempesta DB Apr 26 10:13:35 192.168.122.209 [65365.985404] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_content_range Apr 26 10:13:35 192.168.122.209 [65366.020136] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_content_type Apr 26 10:13:36 192.168.122.209 [65367.340261] [tdb] Start Tempesta DB Apr 26 10:13:36 192.168.122.209 [65367.491682] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:13:37 192.168.122.209 [65368.227542] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65368.227542] Maybe that's fine, but it's worth checking the [65368.227542] config - if there is no relations between the [65368.227542] names, then host name confusion attack is possible. Apr 26 10:13:37 192.168.122.209 [65368.370304] [tempesta fw] Configuration processing is completed. Apr 26 10:13:37 192.168.122.209 [65368.421122] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:13:37 192.168.122.209 [65368.449488] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:13:37 192.168.122.209 [65368.482884] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:13:37 192.168.122.209 [65368.534320] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:13:37 192.168.122.209 [65368.536009] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:13:37 192.168.122.209 [65368.582243] [tempesta fw] Tempesta FW is ready Apr 26 10:13:38 192.168.122.209 [65369.219612] [tdb] Close table 'client0.tdb' Apr 26 10:13:38 192.168.122.209 [65369.421630] [tdb] Close table 'sessions0.tdb' Apr 26 10:13:39 192.168.122.209 [65369.655523] [tdb] Close table 'filter0.tdb' Apr 26 10:13:39 192.168.122.209 [65369.655925] [tempesta fw] modules are stopped Apr 26 10:13:39 192.168.122.209 [65369.879224] [tempesta fw] exiting... Apr 26 10:13:39 192.168.122.209 [65370.001799] [tdb] Shutdown Tempesta DB Apr 26 10:13:39 192.168.122.209 [65370.219589] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_content_type Apr 26 10:13:39 192.168.122.209 [65370.233456] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_date Apr 26 10:13:40 192.168.122.209 [65371.430472] [tdb] Start Tempesta DB Apr 26 10:13:40 192.168.122.209 [65371.562605] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:13:41 192.168.122.209 [65372.303716] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65372.303716] Maybe that's fine, but it's worth checking the [65372.303716] config - if there is no relations between the [65372.303716] names, then host name confusion attack is possible. Apr 26 10:13:41 192.168.122.209 [65372.450371] [tempesta fw] Configuration processing is completed. Apr 26 10:13:41 192.168.122.209 [65372.518390] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:13:41 192.168.122.209 [65372.558544] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:13:41 192.168.122.209 [65372.595994] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:13:42 192.168.122.209 [65372.642331] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:13:42 192.168.122.209 [65372.644022] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:13:42 192.168.122.209 [65372.690311] [tempesta fw] Tempesta FW is ready Apr 26 10:13:42 192.168.122.209 [65373.321951] [tdb] Close table 'client0.tdb' Apr 26 10:13:42 192.168.122.209 [65373.533883] [tdb] Close table 'sessions0.tdb' Apr 26 10:13:43 192.168.122.209 [65373.774425] [tdb] Close table 'filter0.tdb' Apr 26 10:13:43 192.168.122.209 [65373.774875] [tempesta fw] modules are stopped Apr 26 10:13:43 192.168.122.209 [65373.955404] [tempesta fw] exiting... Apr 26 10:13:43 192.168.122.209 [65374.082766] [tdb] Shutdown Tempesta DB Apr 26 10:13:43 192.168.122.209 [65374.329115] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_date Apr 26 10:13:43 192.168.122.209 [65374.341668] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_from Apr 26 10:13:44 192.168.122.209 [65375.608169] [tdb] Start Tempesta DB Apr 26 10:13:45 192.168.122.209 [65375.749355] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:13:45 192.168.122.209 [65376.519783] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65376.519783] Maybe that's fine, but it's worth checking the [65376.519783] config - if there is no relations between the [65376.519783] names, then host name confusion attack is possible. Apr 26 10:13:46 192.168.122.209 [65376.654844] [tempesta fw] Configuration processing is completed. Apr 26 10:13:46 192.168.122.209 [65376.715210] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:13:46 192.168.122.209 [65376.749489] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:13:46 192.168.122.209 [65376.781906] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:13:46 192.168.122.209 [65376.818390] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:13:46 192.168.122.209 [65376.820093] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:13:46 192.168.122.209 [65376.874346] [tempesta fw] Tempesta FW is ready Apr 26 10:13:46 192.168.122.209 [65377.549149] [tdb] Close table 'client0.tdb' Apr 26 10:13:47 192.168.122.209 [65377.731490] [tdb] Close table 'sessions0.tdb' Apr 26 10:13:47 192.168.122.209 [65377.948980] [tdb] Close table 'filter0.tdb' Apr 26 10:13:47 192.168.122.209 [65377.949403] [tempesta fw] modules are stopped Apr 26 10:13:47 192.168.122.209 [65378.204132] [tempesta fw] exiting... Apr 26 10:13:47 192.168.122.209 [65378.368904] [tdb] Shutdown Tempesta DB Apr 26 10:13:47 192.168.122.209 [65378.582967] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_from Apr 26 10:13:47 192.168.122.209 [65378.604887] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_if_match Apr 26 10:13:49 192.168.122.209 [65379.820997] [tdb] Start Tempesta DB Apr 26 10:13:49 192.168.122.209 [65379.969627] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:13:50 192.168.122.209 [65380.707762] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65380.707762] Maybe that's fine, but it's worth checking the [65380.707762] config - if there is no relations between the [65380.707762] names, then host name confusion attack is possible. Apr 26 10:13:50 192.168.122.209 [65380.846479] [tempesta fw] Configuration processing is completed. Apr 26 10:13:50 192.168.122.209 [65380.897353] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:13:50 192.168.122.209 [65380.927458] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:13:50 192.168.122.209 [65380.956123] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:13:50 192.168.122.209 [65381.018490] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:13:50 192.168.122.209 [65381.020194] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:13:50 192.168.122.209 [65381.058338] [tempesta fw] Tempesta FW is ready Apr 26 10:13:51 192.168.122.209 [65381.676701] [tdb] Close table 'client0.tdb' Apr 26 10:13:51 192.168.122.209 [65381.867310] [tdb] Close table 'sessions0.tdb' Apr 26 10:13:51 192.168.122.209 [65382.102895] [tdb] Close table 'filter0.tdb' Apr 26 10:13:51 192.168.122.209 [65382.103330] [tempesta fw] modules are stopped Apr 26 10:13:51 192.168.122.209 [65382.295066] [tempesta fw] exiting... Apr 26 10:13:51 192.168.122.209 [65382.434819] [tdb] Shutdown Tempesta DB Apr 26 10:13:52 192.168.122.209 [65382.674540] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_if_match Apr 26 10:13:52 192.168.122.209 [65382.689722] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_if_modified_since Apr 26 10:13:53 192.168.122.209 [65383.862153] [tdb] Start Tempesta DB Apr 26 10:13:53 192.168.122.209 [65384.010380] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:13:54 192.168.122.209 [65384.743848] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65384.743848] Maybe that's fine, but it's worth checking the [65384.743848] config - if there is no relations between the [65384.743848] names, then host name confusion attack is possible. Apr 26 10:13:54 192.168.122.209 [65384.882522] [tempesta fw] Configuration processing is completed. Apr 26 10:13:54 192.168.122.209 [65384.947256] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:13:54 192.168.122.209 [65384.986974] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:13:54 192.168.122.209 [65385.026860] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:13:54 192.168.122.209 [65385.078496] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:13:54 192.168.122.209 [65385.080172] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:13:54 192.168.122.209 [65385.126445] [tempesta fw] Tempesta FW is ready Apr 26 10:13:55 192.168.122.209 [65385.766302] [tdb] Close table 'client0.tdb' Apr 26 10:13:55 192.168.122.209 [65385.957370] [tdb] Close table 'sessions0.tdb' Apr 26 10:13:55 192.168.122.209 [65386.176542] [tdb] Close table 'filter0.tdb' Apr 26 10:13:55 192.168.122.209 [65386.176980] [tempesta fw] modules are stopped Apr 26 10:13:55 192.168.122.209 [65386.390995] [tempesta fw] exiting... Apr 26 10:13:55 192.168.122.209 [65386.514074] [tdb] Shutdown Tempesta DB Apr 26 10:13:56 192.168.122.209 [65386.726803] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_if_modified_since Apr 26 10:13:56 192.168.122.209 [65386.752976] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_if_range Apr 26 10:13:57 192.168.122.209 [65387.940217] [tdb] Start Tempesta DB Apr 26 10:13:57 192.168.122.209 [65388.082553] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:13:58 192.168.122.209 [65388.847851] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65388.847851] Maybe that's fine, but it's worth checking the [65388.847851] config - if there is no relations between the [65388.847851] names, then host name confusion attack is possible. Apr 26 10:13:58 192.168.122.209 [65388.990563] [tempesta fw] Configuration processing is completed. Apr 26 10:13:58 192.168.122.209 [65389.042271] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:13:58 192.168.122.209 [65389.071775] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:13:58 192.168.122.209 [65389.101901] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:13:58 192.168.122.209 [65389.158534] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:13:58 192.168.122.209 [65389.160234] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:13:58 192.168.122.209 [65389.206496] [tempesta fw] Tempesta FW is ready Apr 26 10:13:59 192.168.122.209 [65389.831275] [tdb] Close table 'client0.tdb' Apr 26 10:13:59 192.168.122.209 [65390.024520] [tdb] Close table 'sessions0.tdb' Apr 26 10:13:59 192.168.122.209 [65390.243046] [tdb] Close table 'filter0.tdb' Apr 26 10:13:59 192.168.122.209 [65390.243461] [tempesta fw] modules are stopped Apr 26 10:13:59 192.168.122.209 [65390.487028] [tempesta fw] exiting... Apr 26 10:13:59 192.168.122.209 [65390.613994] [tdb] Shutdown Tempesta DB Apr 26 10:14:00 192.168.122.209 [65390.828267] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_if_range Apr 26 10:14:00 192.168.122.209 [65390.841431] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_if_unmodified_since Apr 26 10:14:01 192.168.122.209 [65391.933544] [tdb] Start Tempesta DB Apr 26 10:14:01 192.168.122.209 [65392.077757] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:14:02 192.168.122.209 [65392.847905] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65392.847905] Maybe that's fine, but it's worth checking the [65392.847905] config - if there is no relations between the [65392.847905] names, then host name confusion attack is possible. Apr 26 10:14:02 192.168.122.209 [65392.978596] [tempesta fw] Configuration processing is completed. Apr 26 10:14:02 192.168.122.209 [65393.038854] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:14:02 192.168.122.209 [65393.072577] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:14:02 192.168.122.209 [65393.104296] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:14:02 192.168.122.209 [65393.142597] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:14:02 192.168.122.209 [65393.144272] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:14:02 192.168.122.209 [65393.182554] [tempesta fw] Tempesta FW is ready Apr 26 10:14:03 192.168.122.209 [65393.841334] [tdb] Close table 'client0.tdb' Apr 26 10:14:03 192.168.122.209 [65394.025057] [tdb] Close table 'sessions0.tdb' Apr 26 10:14:03 192.168.122.209 [65394.267573] [tdb] Close table 'filter0.tdb' Apr 26 10:14:03 192.168.122.209 [65394.268005] [tempesta fw] modules are stopped Apr 26 10:14:03 192.168.122.209 [65394.439515] [tempesta fw] exiting... Apr 26 10:14:03 192.168.122.209 [65394.560100] [tdb] Shutdown Tempesta DB Apr 26 10:14:04 192.168.122.209 [65394.769585] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_if_unmodified_since Apr 26 10:14:04 192.168.122.209 [65394.793638] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_last_modified Apr 26 10:14:05 192.168.122.209 [65395.811252] [tdb] Start Tempesta DB Apr 26 10:14:05 192.168.122.209 [65395.947136] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:14:06 192.168.122.209 [65396.751543] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65396.751543] Maybe that's fine, but it's worth checking the [65396.751543] config - if there is no relations between the [65396.751543] names, then host name confusion attack is possible. Apr 26 10:14:06 192.168.122.209 [65396.883061] [tempesta fw] Configuration processing is completed. Apr 26 10:14:06 192.168.122.209 [65396.938807] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:14:06 192.168.122.209 [65396.975230] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:14:06 192.168.122.209 [65397.005405] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:14:06 192.168.122.209 [65397.038629] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:14:06 192.168.122.209 [65397.040310] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:14:06 192.168.122.209 [65397.078593] [tempesta fw] Tempesta FW is ready Apr 26 10:14:07 192.168.122.209 [65397.734280] [tdb] Close table 'client0.tdb' Apr 26 10:14:07 192.168.122.209 [65397.930090] [tdb] Close table 'sessions0.tdb' Apr 26 10:14:07 192.168.122.209 [65398.178154] [tdb] Close table 'filter0.tdb' Apr 26 10:14:07 192.168.122.209 [65398.178591] [tempesta fw] modules are stopped Apr 26 10:14:07 192.168.122.209 [65398.362521] [tempesta fw] exiting... Apr 26 10:14:07 192.168.122.209 [65398.481322] [tdb] Shutdown Tempesta DB Apr 26 10:14:08 192.168.122.209 [65398.716235] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_last_modified Apr 26 10:14:08 192.168.122.209 [65398.729792] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_max_forwards Apr 26 10:14:09 192.168.122.209 [65400.087895] [tdb] Start Tempesta DB Apr 26 10:14:09 192.168.122.209 [65400.236259] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:14:10 192.168.122.209 [65401.027964] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65401.027964] Maybe that's fine, but it's worth checking the [65401.027964] config - if there is no relations between the [65401.027964] names, then host name confusion attack is possible. Apr 26 10:14:10 192.168.122.209 [65401.155750] [tempesta fw] Configuration processing is completed. Apr 26 10:14:10 192.168.122.209 [65401.235881] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:14:10 192.168.122.209 [65401.265636] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:14:10 192.168.122.209 [65401.294706] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:14:10 192.168.122.209 [65401.338676] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:14:10 192.168.122.209 [65401.340414] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:14:10 192.168.122.209 [65401.378642] [tempesta fw] Tempesta FW is ready Apr 26 10:14:11 192.168.122.209 [65402.037174] [tdb] Close table 'client0.tdb' Apr 26 10:14:11 192.168.122.209 [65402.225378] [tdb] Close table 'sessions0.tdb' Apr 26 10:14:11 192.168.122.209 [65402.442280] [tdb] Close table 'filter0.tdb' Apr 26 10:14:11 192.168.122.209 [65402.442737] [tempesta fw] modules are stopped Apr 26 10:14:12 192.168.122.209 [65402.679418] [tempesta fw] exiting... Apr 26 10:14:12 192.168.122.209 [65402.800247] [tdb] Shutdown Tempesta DB Apr 26 10:14:12 192.168.122.209 [65403.038774] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_max_forwards Apr 26 10:14:12 192.168.122.209 [65403.047609] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_pragma Apr 26 10:14:13 192.168.122.209 [65404.207728] [tdb] Start Tempesta DB Apr 26 10:14:13 192.168.122.209 [65404.351192] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:14:14 192.168.122.209 [65405.096062] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65405.096062] Maybe that's fine, but it's worth checking the [65405.096062] config - if there is no relations between the [65405.096062] names, then host name confusion attack is possible. Apr 26 10:14:14 192.168.122.209 [65405.250663] [tempesta fw] Configuration processing is completed. Apr 26 10:14:14 192.168.122.209 [65405.314282] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:14:14 192.168.122.209 [65405.351527] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:14:14 192.168.122.209 [65405.384134] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:14:14 192.168.122.209 [65405.426743] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:14:14 192.168.122.209 [65405.428459] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:14:14 192.168.122.209 [65405.466693] [tempesta fw] Tempesta FW is ready Apr 26 10:14:15 192.168.122.209 [65406.135870] [tdb] Close table 'client0.tdb' Apr 26 10:14:15 192.168.122.209 [65406.330229] [tdb] Close table 'sessions0.tdb' Apr 26 10:14:15 192.168.122.209 [65406.573200] [tdb] Close table 'filter0.tdb' Apr 26 10:14:15 192.168.122.209 [65406.573643] [tempesta fw] modules are stopped Apr 26 10:14:16 192.168.122.209 [65406.779083] [tempesta fw] exiting... Apr 26 10:14:16 192.168.122.209 [65406.924089] [tdb] Shutdown Tempesta DB Apr 26 10:14:16 192.168.122.209 [65407.134089] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_pragma Apr 26 10:14:16 192.168.122.209 [65407.146857] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_range Apr 26 10:14:17 192.168.122.209 [65408.313564] [tdb] Start Tempesta DB Apr 26 10:14:17 192.168.122.209 [65408.477066] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:14:18 192.168.122.209 [65409.244144] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65409.244144] Maybe that's fine, but it's worth checking the [65409.244144] config - if there is no relations between the [65409.244144] names, then host name confusion attack is possible. Apr 26 10:14:18 192.168.122.209 [65409.382848] [tempesta fw] Configuration processing is completed. Apr 26 10:14:18 192.168.122.209 [65409.442191] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:14:18 192.168.122.209 [65409.476069] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:14:18 192.168.122.209 [65409.508187] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:14:18 192.168.122.209 [65409.554785] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:14:18 192.168.122.209 [65409.556567] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:14:18 192.168.122.209 [65409.602722] [tempesta fw] Tempesta FW is ready Apr 26 10:14:19 192.168.122.209 [65410.270848] [tdb] Close table 'client0.tdb' Apr 26 10:14:19 192.168.122.209 [65410.466794] [tdb] Close table 'sessions0.tdb' Apr 26 10:14:20 192.168.122.209 [65410.699550] [tdb] Close table 'filter0.tdb' Apr 26 10:14:20 192.168.122.209 [65410.700002] [tempesta fw] modules are stopped Apr 26 10:14:20 192.168.122.209 [65410.931167] [tempesta fw] exiting... Apr 26 10:14:20 192.168.122.209 [65411.046417] [tdb] Shutdown Tempesta DB Apr 26 10:14:20 192.168.122.209 [65411.256312] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_range Apr 26 10:14:20 192.168.122.209 [65411.271799] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_referer Apr 26 10:14:21 192.168.122.209 [65412.560549] [tdb] Start Tempesta DB Apr 26 10:14:22 192.168.122.209 [65412.723817] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:14:22 192.168.122.209 [65413.488217] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65413.488217] Maybe that's fine, but it's worth checking the [65413.488217] config - if there is no relations between the [65413.488217] names, then host name confusion attack is possible. Apr 26 10:14:22 192.168.122.209 [65413.618845] [tempesta fw] Configuration processing is completed. Apr 26 10:14:23 192.168.122.209 [65413.680813] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:14:23 192.168.122.209 [65413.716099] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:14:23 192.168.122.209 [65413.746866] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:14:23 192.168.122.209 [65413.794874] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:14:23 192.168.122.209 [65413.796625] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:14:23 192.168.122.209 [65413.842776] [tempesta fw] Tempesta FW is ready Apr 26 10:14:23 192.168.122.209 [65414.475062] [tdb] Close table 'client0.tdb' Apr 26 10:14:24 192.168.122.209 [65414.674700] [tdb] Close table 'sessions0.tdb' Apr 26 10:14:24 192.168.122.209 [65414.930210] [tdb] Close table 'filter0.tdb' Apr 26 10:14:24 192.168.122.209 [65414.930612] [tempesta fw] modules are stopped Apr 26 10:14:24 192.168.122.209 [65415.130712] [tempesta fw] exiting... Apr 26 10:14:24 192.168.122.209 [65415.259824] [tdb] Shutdown Tempesta DB Apr 26 10:14:24 192.168.122.209 [65415.477255] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_referer Apr 26 10:14:24 192.168.122.209 [65415.485929] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_trailer Apr 26 10:14:26 192.168.122.209 [65416.666685] [tdb] Start Tempesta DB Apr 26 10:14:26 192.168.122.209 [65416.820239] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:14:26 192.168.122.209 [65417.572295] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65417.572295] Maybe that's fine, but it's worth checking the [65417.572295] config - if there is no relations between the [65417.572295] names, then host name confusion attack is possible. Apr 26 10:14:27 192.168.122.209 [65417.710906] [tempesta fw] Configuration processing is completed. Apr 26 10:14:27 192.168.122.209 [65417.768533] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:14:27 192.168.122.209 [65417.801020] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:14:27 192.168.122.209 [65417.831462] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:14:27 192.168.122.209 [65417.878872] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:14:27 192.168.122.209 [65417.880612] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:14:27 192.168.122.209 [65417.922824] [tempesta fw] Tempesta FW is ready Apr 26 10:14:27 192.168.122.209 [65418.570147] [tdb] Close table 'client0.tdb' Apr 26 10:14:28 192.168.122.209 [65418.774465] [tdb] Close table 'sessions0.tdb' Apr 26 10:14:28 192.168.122.209 [65419.026072] [tdb] Close table 'filter0.tdb' Apr 26 10:14:28 192.168.122.209 [65419.026487] [tempesta fw] modules are stopped Apr 26 10:14:28 192.168.122.209 [65419.224821] [tempesta fw] exiting... Apr 26 10:14:28 192.168.122.209 [65419.352454] [tdb] Shutdown Tempesta DB Apr 26 10:14:28 192.168.122.209 [65419.549003] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_trailer Apr 26 10:14:28 192.168.122.209 [65419.561567] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_user_agent Apr 26 10:14:30 192.168.122.209 [65420.745762] [tdb] Start Tempesta DB Apr 26 10:14:30 192.168.122.209 [65420.893801] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:14:31 192.168.122.209 [65421.680270] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65421.680270] Maybe that's fine, but it's worth checking the [65421.680270] config - if there is no relations between the [65421.680270] names, then host name confusion attack is possible. Apr 26 10:14:31 192.168.122.209 [65421.818908] [tempesta fw] Configuration processing is completed. Apr 26 10:14:31 192.168.122.209 [65421.876476] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:14:31 192.168.122.209 [65421.911871] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:14:31 192.168.122.209 [65421.946128] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:14:31 192.168.122.209 [65421.994845] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:14:31 192.168.122.209 [65421.996252] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:14:31 192.168.122.209 [65422.038875] [tempesta fw] Tempesta FW is ready Apr 26 10:14:32 192.168.122.209 [65422.703647] [tdb] Close table 'client0.tdb' Apr 26 10:14:32 192.168.122.209 [65422.885220] [tdb] Close table 'sessions0.tdb' Apr 26 10:14:32 192.168.122.209 [65423.106850] [tdb] Close table 'filter0.tdb' Apr 26 10:14:32 192.168.122.209 [65423.107292] [tempesta fw] modules are stopped Apr 26 10:14:32 192.168.122.209 [65423.303506] [tempesta fw] exiting... Apr 26 10:14:32 192.168.122.209 [65423.468662] [tdb] Shutdown Tempesta DB Apr 26 10:14:33 192.168.122.209 [65423.721148] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_user_agent Apr 26 10:14:33 192.168.122.209 [65423.738738] Start test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_via Apr 26 10:14:34 192.168.122.209 [65425.023820] [tdb] Start Tempesta DB Apr 26 10:14:34 192.168.122.209 [65425.154962] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:14:35 192.168.122.209 [65425.908268] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65425.908268] Maybe that's fine, but it's worth checking the [65425.908268] config - if there is no relations between the [65425.908268] names, then host name confusion attack is possible. Apr 26 10:14:35 192.168.122.209 [65426.043006] [tempesta fw] Configuration processing is completed. Apr 26 10:14:35 192.168.122.209 [65426.101197] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:14:35 192.168.122.209 [65426.135646] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:14:35 192.168.122.209 [65426.166577] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:14:35 192.168.122.209 [65426.218993] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:14:35 192.168.122.209 [65426.220747] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:14:35 192.168.122.209 [65426.270963] [tempesta fw] Tempesta FW is ready Apr 26 10:14:36 192.168.122.209 [65426.925997] [tdb] Close table 'client0.tdb' Apr 26 10:14:36 192.168.122.209 [65427.108978] [tdb] Close table 'sessions0.tdb' Apr 26 10:14:36 192.168.122.209 [65427.343768] [tdb] Close table 'filter0.tdb' Apr 26 10:14:36 192.168.122.209 [65427.344204] [tempesta fw] modules are stopped Apr 26 10:14:36 192.168.122.209 [65427.555353] [tempesta fw] exiting... Apr 26 10:14:37 192.168.122.209 [65427.651196] [tdb] Shutdown Tempesta DB Apr 26 10:14:37 192.168.122.209 [65427.832048] End test: t_malformed.test_h2_malformed_headers.H2MalformedRequestsWithoutStrictParsingTest.test_via Apr 26 10:14:37 192.168.122.209 [65427.847461] Start test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_accept_ranges Apr 26 10:14:38 192.168.122.209 [65429.124319] [tdb] Start Tempesta DB Apr 26 10:14:38 192.168.122.209 [65429.263433] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:14:39 192.168.122.209 [65429.980351] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65429.980351] Maybe that's fine, but it's worth checking the [65429.980351] config - if there is no relations between the [65429.980351] names, then host name confusion attack is possible. Apr 26 10:14:39 192.168.122.209 [65430.139053] [tempesta fw] Configuration processing is completed. Apr 26 10:14:39 192.168.122.209 [65430.200735] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:14:39 192.168.122.209 [65430.237680] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:14:39 192.168.122.209 [65430.272492] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:14:39 192.168.122.209 [65430.319057] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:14:39 192.168.122.209 [65430.320835] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:14:39 192.168.122.209 [65430.358999] [tempesta fw] Tempesta FW is ready Apr 26 10:14:40 192.168.122.209 [65431.006777] [tdb] Close table 'client0.tdb' Apr 26 10:14:40 192.168.122.209 [65431.203571] [tdb] Close table 'sessions0.tdb' Apr 26 10:14:40 192.168.122.209 [65431.427897] [tdb] Close table 'filter0.tdb' Apr 26 10:14:40 192.168.122.209 [65431.428341] [tempesta fw] modules are stopped Apr 26 10:14:41 192.168.122.209 [65431.647071] [tempesta fw] exiting... Apr 26 10:14:41 192.168.122.209 [65431.770466] [tdb] Shutdown Tempesta DB Apr 26 10:14:41 192.168.122.209 [65431.989018] End test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_accept_ranges Apr 26 10:14:41 192.168.122.209 [65432.001020] Start test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_allow Apr 26 10:14:42 192.168.122.209 [65433.222379] [tdb] Start Tempesta DB Apr 26 10:14:42 192.168.122.209 [65433.387582] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:14:43 192.168.122.209 [65434.164632] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65434.164632] Maybe that's fine, but it's worth checking the [65434.164632] config - if there is no relations between the [65434.164632] names, then host name confusion attack is possible. Apr 26 10:14:43 192.168.122.209 [65434.319120] [tempesta fw] Configuration processing is completed. Apr 26 10:14:43 192.168.122.209 [65434.390662] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:14:43 192.168.122.209 [65434.423680] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:14:43 192.168.122.209 [65434.455845] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:14:43 192.168.122.209 [65434.507099] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:14:43 192.168.122.209 [65434.508870] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:14:43 192.168.122.209 [65434.555053] [tempesta fw] Tempesta FW is ready Apr 26 10:14:44 192.168.122.209 [65435.185672] [tdb] Close table 'client0.tdb' Apr 26 10:14:44 192.168.122.209 [65435.380081] [tdb] Close table 'sessions0.tdb' Apr 26 10:14:45 192.168.122.209 [65435.629536] [tdb] Close table 'filter0.tdb' Apr 26 10:14:45 192.168.122.209 [65435.629975] [tempesta fw] modules are stopped Apr 26 10:14:45 192.168.122.209 [65435.907937] [tempesta fw] exiting... Apr 26 10:14:45 192.168.122.209 [65436.046429] [tdb] Shutdown Tempesta DB Apr 26 10:14:45 192.168.122.209 [65436.262401] End test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_allow Apr 26 10:14:45 192.168.122.209 [65436.284676] Start test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_connection Apr 26 10:14:46 192.168.122.209 [65437.508375] [tdb] Start Tempesta DB Apr 26 10:14:47 192.168.122.209 [65437.648337] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:14:47 192.168.122.209 [65438.376492] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65438.376492] Maybe that's fine, but it's worth checking the [65438.376492] config - if there is no relations between the [65438.376492] names, then host name confusion attack is possible. Apr 26 10:14:47 192.168.122.209 [65438.527185] [tempesta fw] Configuration processing is completed. Apr 26 10:14:47 192.168.122.209 [65438.586126] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:14:47 192.168.122.209 [65438.620354] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:14:48 192.168.122.209 [65438.651423] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:14:48 192.168.122.209 [65438.691151] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:14:48 192.168.122.209 [65438.692882] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:14:48 192.168.122.209 [65438.739084] [tempesta fw] Tempesta FW is ready Apr 26 10:14:48 192.168.122.209 [65439.359732] [tdb] Close table 'client0.tdb' Apr 26 10:14:48 192.168.122.209 [65439.576038] [tdb] Close table 'sessions0.tdb' Apr 26 10:14:49 192.168.122.209 [65439.816812] [tdb] Close table 'filter0.tdb' Apr 26 10:14:49 192.168.122.209 [65439.817246] [tempesta fw] modules are stopped Apr 26 10:14:49 192.168.122.209 [65439.999637] [tempesta fw] exiting... Apr 26 10:14:49 192.168.122.209 [65440.151690] [tdb] Shutdown Tempesta DB Apr 26 10:14:49 192.168.122.209 [65440.351397] End test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_connection Apr 26 10:14:49 192.168.122.209 [65440.373151] Start test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_content_encoding Apr 26 10:14:51 192.168.122.209 [65441.686645] [tdb] Start Tempesta DB Apr 26 10:14:51 192.168.122.209 [65441.844028] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:14:51 192.168.122.209 [65442.616588] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65442.616588] Maybe that's fine, but it's worth checking the [65442.616588] config - if there is no relations between the [65442.616588] names, then host name confusion attack is possible. Apr 26 10:14:52 192.168.122.209 [65442.767283] [tempesta fw] Configuration processing is completed. Apr 26 10:14:52 192.168.122.209 [65442.827843] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:14:52 192.168.122.209 [65442.861561] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:14:52 192.168.122.209 [65442.891941] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:14:52 192.168.122.209 [65442.959221] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:14:52 192.168.122.209 [65442.960968] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:14:52 192.168.122.209 [65442.999138] [tempesta fw] Tempesta FW is ready Apr 26 10:14:53 192.168.122.209 [65443.637889] [tdb] Close table 'client0.tdb' Apr 26 10:14:53 192.168.122.209 [65443.834292] [tdb] Close table 'sessions0.tdb' Apr 26 10:14:53 192.168.122.209 [65444.091280] [tdb] Close table 'filter0.tdb' Apr 26 10:14:53 192.168.122.209 [65444.091728] [tempesta fw] modules are stopped Apr 26 10:14:53 192.168.122.209 [65444.321157] [tempesta fw] exiting... Apr 26 10:14:53 192.168.122.209 [65444.484514] [tdb] Shutdown Tempesta DB Apr 26 10:14:54 192.168.122.209 [65444.702427] End test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_content_encoding Apr 26 10:14:54 192.168.122.209 [65444.714210] Start test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_content_language Apr 26 10:14:55 192.168.122.209 [65445.878746] [tdb] Start Tempesta DB Apr 26 10:14:55 192.168.122.209 [65446.027448] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:14:56 192.168.122.209 [65446.736599] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65446.736599] Maybe that's fine, but it's worth checking the [65446.736599] config - if there is no relations between the [65446.736599] names, then host name confusion attack is possible. Apr 26 10:14:56 192.168.122.209 [65446.911277] [tempesta fw] Configuration processing is completed. Apr 26 10:14:56 192.168.122.209 [65446.983758] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:14:56 192.168.122.209 [65447.023780] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:14:56 192.168.122.209 [65447.059233] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:14:56 192.168.122.209 [65447.107243] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:14:56 192.168.122.209 [65447.108975] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:14:56 192.168.122.209 [65447.147214] [tempesta fw] Tempesta FW is ready Apr 26 10:14:57 192.168.122.209 [65447.797526] [tdb] Close table 'client0.tdb' Apr 26 10:14:57 192.168.122.209 [65447.989028] [tdb] Close table 'sessions0.tdb' Apr 26 10:14:57 192.168.122.209 [65448.243294] [tdb] Close table 'filter0.tdb' Apr 26 10:14:57 192.168.122.209 [65448.243738] [tempesta fw] modules are stopped Apr 26 10:14:57 192.168.122.209 [65448.464845] [tempesta fw] exiting... Apr 26 10:14:57 192.168.122.209 [65448.577088] [tdb] Shutdown Tempesta DB Apr 26 10:14:58 192.168.122.209 [65448.792290] End test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_content_language Apr 26 10:14:58 192.168.122.209 [65448.805778] Start test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_content_location Apr 26 10:14:59 192.168.122.209 [65450.001259] [tdb] Start Tempesta DB Apr 26 10:14:59 192.168.122.209 [65450.139037] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:15:00 192.168.122.209 [65450.908575] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65450.908575] Maybe that's fine, but it's worth checking the [65450.908575] config - if there is no relations between the [65450.908575] names, then host name confusion attack is possible. Apr 26 10:15:00 192.168.122.209 [65451.059313] [tempesta fw] Configuration processing is completed. Apr 26 10:15:00 192.168.122.209 [65451.115583] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:15:00 192.168.122.209 [65451.145744] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:15:00 192.168.122.209 [65451.174805] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:15:00 192.168.122.209 [65451.215287] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:15:00 192.168.122.209 [65451.217004] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:15:00 192.168.122.209 [65451.263245] [tempesta fw] Tempesta FW is ready Apr 26 10:15:01 192.168.122.209 [65451.909969] [tdb] Close table 'client0.tdb' Apr 26 10:15:01 192.168.122.209 [65452.098805] [tdb] Close table 'sessions0.tdb' Apr 26 10:15:01 192.168.122.209 [65452.328653] [tdb] Close table 'filter0.tdb' Apr 26 10:15:01 192.168.122.209 [65452.329065] [tempesta fw] modules are stopped Apr 26 10:15:01 192.168.122.209 [65452.594249] [tempesta fw] exiting... Apr 26 10:15:02 192.168.122.209 [65452.701252] [tdb] Shutdown Tempesta DB Apr 26 10:15:02 192.168.122.209 [65452.940662] End test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_content_location Apr 26 10:15:02 192.168.122.209 [65452.954312] Start test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_content_range Apr 26 10:15:03 192.168.122.209 [65454.197658] [tdb] Start Tempesta DB Apr 26 10:15:03 192.168.122.209 [65454.340247] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:15:04 192.168.122.209 [65455.056640] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65455.056640] Maybe that's fine, but it's worth checking the [65455.056640] config - if there is no relations between the [65455.056640] names, then host name confusion attack is possible. Apr 26 10:15:04 192.168.122.209 [65455.223414] [tempesta fw] Configuration processing is completed. Apr 26 10:15:04 192.168.122.209 [65455.275782] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:15:04 192.168.122.209 [65455.305803] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:15:04 192.168.122.209 [65455.334697] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:15:04 192.168.122.209 [65455.379349] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:15:04 192.168.122.209 [65455.381099] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:15:04 192.168.122.209 [65455.419307] [tempesta fw] Tempesta FW is ready Apr 26 10:15:05 192.168.122.209 [65456.031615] [tdb] Close table 'client0.tdb' Apr 26 10:15:05 192.168.122.209 [65456.230834] [tdb] Close table 'sessions0.tdb' Apr 26 10:15:05 192.168.122.209 [65456.473436] [tdb] Close table 'filter0.tdb' Apr 26 10:15:05 192.168.122.209 [65456.473871] [tempesta fw] modules are stopped Apr 26 10:15:06 192.168.122.209 [65456.649314] [tempesta fw] exiting... Apr 26 10:15:06 192.168.122.209 [65456.788743] [tdb] Shutdown Tempesta DB Apr 26 10:15:06 192.168.122.209 [65457.033647] End test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_content_range Apr 26 10:15:06 192.168.122.209 [65457.048652] Start test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_content_type Apr 26 10:15:07 192.168.122.209 [65458.233395] [tdb] Start Tempesta DB Apr 26 10:15:07 192.168.122.209 [65458.389642] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:15:08 192.168.122.209 [65458.976869] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65458.976869] Maybe that's fine, but it's worth checking the [65458.976869] config - if there is no relations between the [65458.976869] names, then host name confusion attack is possible. Apr 26 10:15:08 192.168.122.209 [65459.139495] [tempesta fw] Configuration processing is completed. Apr 26 10:15:08 192.168.122.209 [65459.202034] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:15:08 192.168.122.209 [65459.238544] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:15:08 192.168.122.209 [65459.273015] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:15:08 192.168.122.209 [65459.335411] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:15:08 192.168.122.209 [65459.337131] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:15:08 192.168.122.209 [65459.383344] [tempesta fw] Tempesta FW is ready Apr 26 10:15:09 192.168.122.209 [65460.021359] [tdb] Close table 'client0.tdb' Apr 26 10:15:09 192.168.122.209 [65460.235900] [tdb] Close table 'sessions0.tdb' Apr 26 10:15:09 192.168.122.209 [65460.529288] [tdb] Close table 'filter0.tdb' Apr 26 10:15:09 192.168.122.209 [65460.529927] [tempesta fw] modules are stopped Apr 26 10:15:10 192.168.122.209 [65460.748181] [tempesta fw] exiting... Apr 26 10:15:10 192.168.122.209 [65460.889133] [tdb] Shutdown Tempesta DB Apr 26 10:15:10 192.168.122.209 [65461.113640] End test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_content_type Apr 26 10:15:10 192.168.122.209 [65461.128608] Start test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_date Apr 26 10:15:11 192.168.122.209 [65462.139902] [tdb] Start Tempesta DB Apr 26 10:15:11 192.168.122.209 [65462.292155] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:15:12 192.168.122.209 [65463.048813] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65463.048813] Maybe that's fine, but it's worth checking the [65463.048813] config - if there is no relations between the [65463.048813] names, then host name confusion attack is possible. Apr 26 10:15:12 192.168.122.209 [65463.203468] [tempesta fw] Configuration processing is completed. Apr 26 10:15:12 192.168.122.209 [65463.263207] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:15:12 192.168.122.209 [65463.297572] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:15:12 192.168.122.209 [65463.329978] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:15:12 192.168.122.209 [65463.391447] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:15:12 192.168.122.209 [65463.393202] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:15:12 192.168.122.209 [65463.435384] [tempesta fw] Tempesta FW is ready Apr 26 10:15:13 192.168.122.209 [65464.090129] [tdb] Close table 'client0.tdb' Apr 26 10:15:13 192.168.122.209 [65464.281414] [tdb] Close table 'sessions0.tdb' Apr 26 10:15:13 192.168.122.209 [65464.514892] [tdb] Close table 'filter0.tdb' Apr 26 10:15:13 192.168.122.209 [65464.515334] [tempesta fw] modules are stopped Apr 26 10:15:14 192.168.122.209 [65464.724335] [tempesta fw] exiting... Apr 26 10:15:14 192.168.122.209 [65464.860782] [tdb] Shutdown Tempesta DB Apr 26 10:15:14 192.168.122.209 [65465.121157] End test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_date Apr 26 10:15:14 192.168.122.209 [65465.136472] Start test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_expires Apr 26 10:15:15 192.168.122.209 [65466.249331] [tdb] Start Tempesta DB Apr 26 10:15:15 192.168.122.209 [65466.391709] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:15:16 192.168.122.209 [65467.040778] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65467.040778] Maybe that's fine, but it's worth checking the [65467.040778] config - if there is no relations between the [65467.040778] names, then host name confusion attack is possible. Apr 26 10:15:16 192.168.122.209 [65467.195513] [tempesta fw] Configuration processing is completed. Apr 26 10:15:16 192.168.122.209 [65467.247804] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:15:16 192.168.122.209 [65467.279365] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:15:16 192.168.122.209 [65467.309207] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:15:16 192.168.122.209 [65467.363477] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:15:16 192.168.122.209 [65467.365205] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:15:16 192.168.122.209 [65467.407431] [tempesta fw] Tempesta FW is ready Apr 26 10:15:17 192.168.122.209 [65468.030800] [tdb] Close table 'client0.tdb' Apr 26 10:15:17 192.168.122.209 [65468.218719] [tdb] Close table 'sessions0.tdb' Apr 26 10:15:17 192.168.122.209 [65468.437361] [tdb] Close table 'filter0.tdb' Apr 26 10:15:17 192.168.122.209 [65468.437820] [tempesta fw] modules are stopped Apr 26 10:15:18 192.168.122.209 [65468.664725] [tempesta fw] exiting... Apr 26 10:15:18 192.168.122.209 [65468.805814] [tdb] Shutdown Tempesta DB Apr 26 10:15:18 192.168.122.209 [65469.001251] End test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_expires Apr 26 10:15:18 192.168.122.209 [65469.009154] Start test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_last_modified Apr 26 10:15:19 192.168.122.209 [65470.055426] [tdb] Start Tempesta DB Apr 26 10:15:19 192.168.122.209 [65470.205143] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:15:20 192.168.122.209 [65470.868896] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65470.868896] Maybe that's fine, but it's worth checking the [65470.868896] config - if there is no relations between the [65470.868896] names, then host name confusion attack is possible. Apr 26 10:15:20 192.168.122.209 [65471.027573] [tempesta fw] Configuration processing is completed. Apr 26 10:15:20 192.168.122.209 [65471.086509] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:15:20 192.168.122.209 [65471.120448] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:15:20 192.168.122.209 [65471.153350] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:15:20 192.168.122.209 [65471.195465] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:15:20 192.168.122.209 [65471.197221] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:15:20 192.168.122.209 [65471.247476] [tempesta fw] Tempesta FW is ready Apr 26 10:15:21 192.168.122.209 [65471.883815] [tdb] Close table 'client0.tdb' Apr 26 10:15:21 192.168.122.209 [65472.093139] [tdb] Close table 'sessions0.tdb' Apr 26 10:15:21 192.168.122.209 [65472.340363] [tdb] Close table 'filter0.tdb' Apr 26 10:15:21 192.168.122.209 [65472.340794] [tempesta fw] modules are stopped Apr 26 10:15:21 192.168.122.209 [65472.530481] [tempesta fw] exiting... Apr 26 10:15:22 192.168.122.209 [65472.646502] [tdb] Shutdown Tempesta DB Apr 26 10:15:22 192.168.122.209 [65472.862092] End test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_last_modified Apr 26 10:15:22 192.168.122.209 [65472.874169] Start test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_location Apr 26 10:15:23 192.168.122.209 [65473.967159] [tdb] Start Tempesta DB Apr 26 10:15:23 192.168.122.209 [65474.119121] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:15:24 192.168.122.209 [65474.896985] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65474.896985] Maybe that's fine, but it's worth checking the [65474.896985] config - if there is no relations between the [65474.896985] names, then host name confusion attack is possible. Apr 26 10:15:24 192.168.122.209 [65475.051620] [tempesta fw] Configuration processing is completed. Apr 26 10:15:24 192.168.122.209 [65475.112600] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:15:24 192.168.122.209 [65475.147985] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:15:24 192.168.122.209 [65475.182493] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:15:24 192.168.122.209 [65475.227609] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:15:24 192.168.122.209 [65475.229334] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:15:24 192.168.122.209 [65475.267550] [tempesta fw] Tempesta FW is ready Apr 26 10:15:25 192.168.122.209 [65475.923271] [tdb] Close table 'client0.tdb' Apr 26 10:15:25 192.168.122.209 [65476.110598] [tdb] Close table 'sessions0.tdb' Apr 26 10:15:25 192.168.122.209 [65476.363348] [tdb] Close table 'filter0.tdb' Apr 26 10:15:25 192.168.122.209 [65476.363801] [tempesta fw] modules are stopped Apr 26 10:15:25 192.168.122.209 [65476.553518] [tempesta fw] exiting... Apr 26 10:15:26 192.168.122.209 [65476.672147] [tdb] Shutdown Tempesta DB Apr 26 10:15:26 192.168.122.209 [65476.867841] End test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_location Apr 26 10:15:26 192.168.122.209 [65476.883499] Start test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_retry_after Apr 26 10:15:27 192.168.122.209 [65477.919934] [tdb] Start Tempesta DB Apr 26 10:15:27 192.168.122.209 [65478.067969] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:15:28 192.168.122.209 [65478.760966] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65478.760966] Maybe that's fine, but it's worth checking the [65478.760966] config - if there is no relations between the [65478.760966] names, then host name confusion attack is possible. Apr 26 10:15:28 192.168.122.209 [65478.927658] [tempesta fw] Configuration processing is completed. Apr 26 10:15:28 192.168.122.209 [65478.981730] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:15:28 192.168.122.209 [65479.012331] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:15:28 192.168.122.209 [65479.046078] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:15:28 192.168.122.209 [65479.087620] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:15:28 192.168.122.209 [65479.089340] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:15:28 192.168.122.209 [65479.135570] [tempesta fw] Tempesta FW is ready Apr 26 10:15:29 192.168.122.209 [65479.784219] [tdb] Close table 'client0.tdb' Apr 26 10:15:29 192.168.122.209 [65479.983117] [tdb] Close table 'sessions0.tdb' Apr 26 10:15:29 192.168.122.209 [65480.240043] [tdb] Close table 'filter0.tdb' Apr 26 10:15:29 192.168.122.209 [65480.240472] [tempesta fw] modules are stopped Apr 26 10:15:29 192.168.122.209 [65480.437718] [tempesta fw] exiting... Apr 26 10:15:29 192.168.122.209 [65480.535279] [tdb] Shutdown Tempesta DB Apr 26 10:15:30 192.168.122.209 [65480.769297] End test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_retry_after Apr 26 10:15:30 192.168.122.209 [65480.781291] Start test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_server Apr 26 10:15:31 192.168.122.209 [65481.802223] [tdb] Start Tempesta DB Apr 26 10:15:31 192.168.122.209 [65481.950588] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:15:32 192.168.122.209 [65482.697093] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65482.697093] Maybe that's fine, but it's worth checking the [65482.697093] config - if there is no relations between the [65482.697093] names, then host name confusion attack is possible. Apr 26 10:15:32 192.168.122.209 [65482.843776] [tempesta fw] Configuration processing is completed. Apr 26 10:15:32 192.168.122.209 [65482.910622] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:15:32 192.168.122.209 [65482.948681] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:15:32 192.168.122.209 [65482.983018] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:15:32 192.168.122.209 [65483.027683] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:15:32 192.168.122.209 [65483.029519] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:15:32 192.168.122.209 [65483.067669] [tempesta fw] Tempesta FW is ready Apr 26 10:15:33 192.168.122.209 [65483.718958] [tdb] Close table 'client0.tdb' Apr 26 10:15:33 192.168.122.209 [65483.910403] [tdb] Close table 'sessions0.tdb' Apr 26 10:15:33 192.168.122.209 [65484.144784] [tdb] Close table 'filter0.tdb' Apr 26 10:15:33 192.168.122.209 [65484.145184] [tempesta fw] modules are stopped Apr 26 10:15:33 192.168.122.209 [65484.360593] [tempesta fw] exiting... Apr 26 10:15:33 192.168.122.209 [65484.498455] [tdb] Shutdown Tempesta DB Apr 26 10:15:34 192.168.122.209 [65484.715841] End test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_server Apr 26 10:15:34 192.168.122.209 [65484.727926] Start test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_vary Apr 26 10:15:35 192.168.122.209 [65485.799361] [tdb] Start Tempesta DB Apr 26 10:15:35 192.168.122.209 [65485.945673] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:15:36 192.168.122.209 [65486.653155] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65486.653155] Maybe that's fine, but it's worth checking the [65486.653155] config - if there is no relations between the [65486.653155] names, then host name confusion attack is possible. Apr 26 10:15:36 192.168.122.209 [65486.799760] [tempesta fw] Configuration processing is completed. Apr 26 10:15:36 192.168.122.209 [65486.865965] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:15:36 192.168.122.209 [65486.899339] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:15:36 192.168.122.209 [65486.932828] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:15:36 192.168.122.209 [65487.007714] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:15:36 192.168.122.209 [65487.009447] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:15:36 192.168.122.209 [65487.047699] [tempesta fw] Tempesta FW is ready Apr 26 10:15:37 192.168.122.209 [65487.707924] [tdb] Close table 'client0.tdb' Apr 26 10:15:37 192.168.122.209 [65487.915817] [tdb] Close table 'sessions0.tdb' Apr 26 10:15:37 192.168.122.209 [65488.160597] [tdb] Close table 'filter0.tdb' Apr 26 10:15:37 192.168.122.209 [65488.161042] [tempesta fw] modules are stopped Apr 26 10:15:37 192.168.122.209 [65488.351995] [tempesta fw] exiting... Apr 26 10:15:37 192.168.122.209 [65488.498863] [tdb] Shutdown Tempesta DB Apr 26 10:15:38 192.168.122.209 [65488.703104] End test: t_malformed.test_h2_malformed_headers.H2MalformedResponseWithoutStrictParsingTest.test_vary Apr 26 10:15:38 192.168.122.209 [65488.720769] Start test: t_malformed.test_h2_malformed_headers.H2MalformedResponsesTest.test_age Apr 26 10:15:39 192.168.122.209 [65489.745503] [tdb] Start Tempesta DB Apr 26 10:15:39 192.168.122.209 [65489.891017] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:15:39 192.168.122.209 [65490.604628] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65490.604628] Maybe that's fine, but it's worth checking the [65490.604628] config - if there is no relations between the [65490.604628] names, then host name confusion attack is possible. Apr 26 10:15:40 192.168.122.209 [65490.767824] [tempesta fw] Configuration processing is completed. Apr 26 10:15:40 192.168.122.209 [65490.845576] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:15:40 192.168.122.209 [65490.888170] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:15:40 192.168.122.209 [65490.927692] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:15:40 192.168.122.209 [65490.987788] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:15:40 192.168.122.209 [65490.989566] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:15:40 192.168.122.209 [65491.035730] [tempesta fw] Tempesta FW is ready Apr 26 10:15:40 192.168.122.209 [65491.244444] [tempesta fw] Warning: Parser error: state=Resp_HdrAgeV input(-0)=0x69('i') data_len=1 off=0 Apr 26 10:15:40 192.168.122.209 [65491.245382] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 10:15:41 192.168.122.209 [65491.689839] [tdb] Close table 'client0.tdb' Apr 26 10:15:41 192.168.122.209 [65491.878534] [tdb] Close table 'sessions0.tdb' Apr 26 10:15:41 192.168.122.209 [65492.128259] [tdb] Close table 'filter0.tdb' Apr 26 10:15:41 192.168.122.209 [65492.128698] [tempesta fw] modules are stopped Apr 26 10:15:41 192.168.122.209 [65492.320470] [tempesta fw] exiting... Apr 26 10:15:41 192.168.122.209 [65492.440676] [tdb] Shutdown Tempesta DB Apr 26 10:15:42 192.168.122.209 [65492.662702] End test: t_malformed.test_h2_malformed_headers.H2MalformedResponsesTest.test_age Apr 26 10:15:42 192.168.122.209 [65492.675721] Start test: t_malformed.test_h2_malformed_headers.H2MalformedResponsesTest.test_cache_control1 Apr 26 10:15:43 192.168.122.209 [65493.734764] [tdb] Start Tempesta DB Apr 26 10:15:43 192.168.122.209 [65493.897600] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:15:43 192.168.122.209 [65494.593107] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65494.593107] Maybe that's fine, but it's worth checking the [65494.593107] config - if there is no relations between the [65494.593107] names, then host name confusion attack is possible. Apr 26 10:15:44 192.168.122.209 [65494.759863] [tempesta fw] Configuration processing is completed. Apr 26 10:15:44 192.168.122.209 [65494.818222] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:15:44 192.168.122.209 [65494.851826] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:15:44 192.168.122.209 [65494.882450] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:15:44 192.168.122.209 [65494.931819] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:15:44 192.168.122.209 [65494.933565] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:15:44 192.168.122.209 [65494.975778] [tempesta fw] Tempesta FW is ready Apr 26 10:15:44 192.168.122.209 [65495.172237] [tempesta fw] Warning: Parser error: state=Resp_HdrCache_CtrlV input(-0)=0x61('a') data_len=1 off=0 Apr 26 10:15:44 192.168.122.209 [65495.175074] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 10:15:44 192.168.122.209 [65495.596531] [tdb] Close table 'client0.tdb' Apr 26 10:15:45 192.168.122.209 [65495.805305] [tdb] Close table 'sessions0.tdb' Apr 26 10:15:45 192.168.122.209 [65496.065074] [tdb] Close table 'filter0.tdb' Apr 26 10:15:45 192.168.122.209 [65496.065502] [tempesta fw] modules are stopped Apr 26 10:15:45 192.168.122.209 [65496.289107] [tempesta fw] exiting... Apr 26 10:15:45 192.168.122.209 [65496.418043] [tdb] Shutdown Tempesta DB Apr 26 10:15:46 192.168.122.209 [65496.632899] End test: t_malformed.test_h2_malformed_headers.H2MalformedResponsesTest.test_cache_control1 Apr 26 10:15:46 192.168.122.209 [65496.651814] Start test: t_malformed.test_h2_malformed_headers.H2MalformedResponsesTest.test_cache_control2 Apr 26 10:15:47 192.168.122.209 [65497.715811] [tdb] Start Tempesta DB Apr 26 10:15:47 192.168.122.209 [65497.886216] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:15:48 192.168.122.209 [65498.637429] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65498.637429] Maybe that's fine, but it's worth checking the [65498.637429] config - if there is no relations between the [65498.637429] names, then host name confusion attack is possible. Apr 26 10:15:48 192.168.122.209 [65498.819905] [tempesta fw] Configuration processing is completed. Apr 26 10:15:48 192.168.122.209 [65498.889996] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:15:48 192.168.122.209 [65498.931487] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:15:48 192.168.122.209 [65498.969438] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:15:48 192.168.122.209 [65499.035986] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:15:48 192.168.122.209 [65499.037811] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:15:48 192.168.122.209 [65499.087845] [tempesta fw] Tempesta FW is ready Apr 26 10:15:48 192.168.122.209 [65499.288029] [tempesta fw] Warning: Parser error: state=Resp_HdrCache_CtrlV input(-0)=0x74('t') data_len=1 off=0 Apr 26 10:15:48 192.168.122.209 [65499.290806] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 10:15:49 192.168.122.209 [65499.695164] [tdb] Close table 'client0.tdb' Apr 26 10:15:49 192.168.122.209 [65499.898357] [tdb] Close table 'sessions0.tdb' Apr 26 10:15:49 192.168.122.209 [65500.123167] [tdb] Close table 'filter0.tdb' Apr 26 10:15:49 192.168.122.209 [65500.123583] [tempesta fw] modules are stopped Apr 26 10:15:49 192.168.122.209 [65500.342055] [tempesta fw] exiting... Apr 26 10:15:49 192.168.122.209 [65500.461098] [tdb] Shutdown Tempesta DB Apr 26 10:15:50 192.168.122.209 [65500.683068] End test: t_malformed.test_h2_malformed_headers.H2MalformedResponsesTest.test_cache_control2 Apr 26 10:15:50 192.168.122.209 [65500.699568] Start test: t_malformed.test_h2_malformed_headers.H2MalformedResponsesTest.test_missing_name Apr 26 10:15:51 192.168.122.209 [65501.754057] [tdb] Start Tempesta DB Apr 26 10:15:51 192.168.122.209 [65501.909037] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:15:51 192.168.122.209 [65502.597250] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65502.597250] Maybe that's fine, but it's worth checking the [65502.597250] config - if there is no relations between the [65502.597250] names, then host name confusion attack is possible. Apr 26 10:15:52 192.168.122.209 [65502.767952] [tempesta fw] Configuration processing is completed. Apr 26 10:15:52 192.168.122.209 [65502.827723] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:15:52 192.168.122.209 [65502.862370] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:15:52 192.168.122.209 [65502.894106] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:15:52 192.168.122.209 [65502.939925] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:15:52 192.168.122.209 [65502.941657] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:15:52 192.168.122.209 [65502.983864] [tempesta fw] Tempesta FW is ready Apr 26 10:15:52 192.168.122.209 [65503.173567] [tempesta fw] Warning: Parser error: state=RGen_HdrOtherN input(-0)=0x3a(':') data_len=1 off=0 Apr 26 10:15:52 192.168.122.209 [65503.176287] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 10:15:52 192.168.122.209 [65503.592041] [tdb] Close table 'client0.tdb' Apr 26 10:15:53 192.168.122.209 [65503.788126] [tdb] Close table 'sessions0.tdb' Apr 26 10:15:53 192.168.122.209 [65504.016024] [tdb] Close table 'filter0.tdb' Apr 26 10:15:53 192.168.122.209 [65504.016459] [tempesta fw] modules are stopped Apr 26 10:15:53 192.168.122.209 [65504.212075] [tempesta fw] exiting... Apr 26 10:15:53 192.168.122.209 [65504.305919] [tdb] Shutdown Tempesta DB Apr 26 10:15:53 192.168.122.209 [65504.494861] End test: t_malformed.test_h2_malformed_headers.H2MalformedResponsesTest.test_missing_name Apr 26 10:15:53 192.168.122.209 [65504.523119] Start test: t_malformed.test_malformed_crlfs.MalformedCrlfTest.test_02_no_crlf_pipeline Apr 26 10:15:54 192.168.122.209 [65505.529639] [tdb] Start Tempesta DB Apr 26 10:15:55 192.168.122.209 [65505.669005] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:15:55 192.168.122.209 [65506.268045] [tempesta fw] Configuration processing is completed. Apr 26 10:15:55 192.168.122.209 [65506.321325] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:15:55 192.168.122.209 [65506.350407] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:15:55 192.168.122.209 [65506.381539] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:15:55 192.168.122.209 [65506.451959] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:15:55 192.168.122.209 [65506.491901] [tempesta fw] Tempesta FW is ready Apr 26 10:15:56 192.168.122.209 [65507.072368] [tdb] Close table 'client0.tdb' Apr 26 10:15:56 192.168.122.209 [65507.258951] [tdb] Close table 'sessions0.tdb' Apr 26 10:15:56 192.168.122.209 [65507.502449] [tdb] Close table 'filter0.tdb' Apr 26 10:15:56 192.168.122.209 [65507.502884] [tempesta fw] modules are stopped Apr 26 10:15:57 192.168.122.209 [65507.708880] [tempesta fw] exiting... Apr 26 10:15:57 192.168.122.209 [65507.817254] [tdb] Shutdown Tempesta DB Apr 26 10:15:57 192.168.122.209 [65508.050771] End test: t_malformed.test_malformed_crlfs.MalformedCrlfTest.test_02_no_crlf_pipeline Apr 26 10:15:57 192.168.122.209 [65508.070035] Start test: t_malformed.test_malformed_crlfs.MalformedCrlfTest.test_03_single_crlf Apr 26 10:15:58 192.168.122.209 [65509.165640] [tdb] Start Tempesta DB Apr 26 10:15:58 192.168.122.209 [65509.308107] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:15:59 192.168.122.209 [65509.888039] [tempesta fw] Configuration processing is completed. Apr 26 10:15:59 192.168.122.209 [65509.940838] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:15:59 192.168.122.209 [65509.970947] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:15:59 192.168.122.209 [65510.000379] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:15:59 192.168.122.209 [65510.056021] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:15:59 192.168.122.209 [65510.103956] [tempesta fw] Tempesta FW is ready Apr 26 10:16:00 192.168.122.209 [65510.681971] [tdb] Close table 'client0.tdb' Apr 26 10:16:00 192.168.122.209 [65510.872865] [tdb] Close table 'sessions0.tdb' Apr 26 10:16:00 192.168.122.209 [65511.118983] [tdb] Close table 'filter0.tdb' Apr 26 10:16:00 192.168.122.209 [65511.119408] [tempesta fw] modules are stopped Apr 26 10:16:00 192.168.122.209 [65511.340589] [tempesta fw] exiting... Apr 26 10:16:00 192.168.122.209 [65511.458311] [tdb] Shutdown Tempesta DB Apr 26 10:16:01 192.168.122.209 [65511.660157] End test: t_malformed.test_malformed_crlfs.MalformedCrlfTest.test_03_single_crlf Apr 26 10:16:01 192.168.122.209 [65511.668600] Start test: t_malformed.test_malformed_crlfs.MalformedCrlfTest.test_04_single_crlf_pipeline Apr 26 10:16:02 192.168.122.209 [65512.745696] [tdb] Start Tempesta DB Apr 26 10:16:02 192.168.122.209 [65512.888062] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:16:02 192.168.122.209 [65513.484114] [tempesta fw] Configuration processing is completed. Apr 26 10:16:02 192.168.122.209 [65513.545199] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:16:02 192.168.122.209 [65513.580845] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:16:02 192.168.122.209 [65513.612700] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:16:03 192.168.122.209 [65513.652045] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:16:03 192.168.122.209 [65513.691998] [tempesta fw] Tempesta FW is ready Apr 26 10:16:03 192.168.122.209 [65514.256876] [tdb] Close table 'client0.tdb' Apr 26 10:16:03 192.168.122.209 [65514.458995] [tdb] Close table 'sessions0.tdb' Apr 26 10:16:04 192.168.122.209 [65514.719334] [tdb] Close table 'filter0.tdb' Apr 26 10:16:04 192.168.122.209 [65514.719773] [tempesta fw] modules are stopped Apr 26 10:16:04 192.168.122.209 [65514.892393] [tempesta fw] exiting... Apr 26 10:16:04 192.168.122.209 [65515.005058] [tdb] Shutdown Tempesta DB Apr 26 10:16:04 192.168.122.209 [65515.247204] End test: t_malformed.test_malformed_crlfs.MalformedCrlfTest.test_04_single_crlf_pipeline Apr 26 10:16:04 192.168.122.209 [65515.261468] Start test: t_malformed.test_malformed_crlfs.MalformedCrlfTest.test_05_single_lf Apr 26 10:16:05 192.168.122.209 [65516.302094] [tdb] Start Tempesta DB Apr 26 10:16:05 192.168.122.209 [65516.440846] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:16:06 192.168.122.209 [65517.064134] [tempesta fw] Configuration processing is completed. Apr 26 10:16:06 192.168.122.209 [65517.120299] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:16:06 192.168.122.209 [65517.151937] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:16:06 192.168.122.209 [65517.181647] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:16:06 192.168.122.209 [65517.224009] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:16:06 192.168.122.209 [65517.260034] [tempesta fw] Tempesta FW is ready Apr 26 10:16:07 192.168.122.209 [65517.794203] [tdb] Close table 'client0.tdb' Apr 26 10:16:07 192.168.122.209 [65518.007100] [tdb] Close table 'sessions0.tdb' Apr 26 10:16:07 192.168.122.209 [65518.238007] [tdb] Close table 'filter0.tdb' Apr 26 10:16:07 192.168.122.209 [65518.238440] [tempesta fw] modules are stopped Apr 26 10:16:07 192.168.122.209 [65518.400618] [tempesta fw] exiting... Apr 26 10:16:07 192.168.122.209 [65518.556721] [tdb] Shutdown Tempesta DB Apr 26 10:16:08 192.168.122.209 [65518.789641] End test: t_malformed.test_malformed_crlfs.MalformedCrlfTest.test_05_single_lf Apr 26 10:16:08 192.168.122.209 [65518.802059] Start test: t_malformed.test_malformed_crlfs.MalformedCrlfTest.test_06_single_lf_pipeline Apr 26 10:16:09 192.168.122.209 [65519.850658] [tdb] Start Tempesta DB Apr 26 10:16:09 192.168.122.209 [65520.004065] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:16:09 192.168.122.209 [65520.592210] [tempesta fw] Configuration processing is completed. Apr 26 10:16:10 192.168.122.209 [65520.650958] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:16:10 192.168.122.209 [65520.684640] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:16:10 192.168.122.209 [65520.716806] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:16:10 192.168.122.209 [65520.756670] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:16:10 192.168.122.209 [65520.800086] [tempesta fw] Tempesta FW is ready Apr 26 10:16:10 192.168.122.209 [65521.394597] [tdb] Close table 'client0.tdb' Apr 26 10:16:10 192.168.122.209 [65521.582543] [tdb] Close table 'sessions0.tdb' Apr 26 10:16:11 192.168.122.209 [65521.820718] [tdb] Close table 'filter0.tdb' Apr 26 10:16:11 192.168.122.209 [65521.821148] [tempesta fw] modules are stopped Apr 26 10:16:11 192.168.122.209 [65521.977712] [tempesta fw] exiting... Apr 26 10:16:11 192.168.122.209 [65522.089027] [tdb] Shutdown Tempesta DB Apr 26 10:16:11 192.168.122.209 [65522.297669] End test: t_malformed.test_malformed_crlfs.MalformedCrlfTest.test_06_single_lf_pipeline Apr 26 10:16:11 192.168.122.209 [65522.317630] Start test: t_malformed.test_malformed_crlfs.MalformedCrlfTest.test_07_double_crlf Apr 26 10:16:12 192.168.122.209 [65523.377233] [tdb] Start Tempesta DB Apr 26 10:16:12 192.168.122.209 [65523.524881] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:16:13 192.168.122.209 [65524.144216] [tempesta fw] Configuration processing is completed. Apr 26 10:16:13 192.168.122.209 [65524.201601] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:16:13 192.168.122.209 [65524.231489] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:16:13 192.168.122.209 [65524.262293] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:16:13 192.168.122.209 [65524.304175] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:16:13 192.168.122.209 [65524.344126] [tempesta fw] Tempesta FW is ready Apr 26 10:16:13 192.168.122.209 [65524.454498] [tempesta fw] Warning: Parser error: state=Req_MethodUnknown input(-0)=0xd(' ') data_len=1 off=0 Apr 26 10:16:14 192.168.122.209 [65524.894490] [tdb] Close table 'client0.tdb' Apr 26 10:16:14 192.168.122.209 [65525.088843] [tdb] Close table 'sessions0.tdb' Apr 26 10:16:14 192.168.122.209 [65525.332031] [tdb] Close table 'filter0.tdb' Apr 26 10:16:14 192.168.122.209 [65525.332443] [tempesta fw] modules are stopped Apr 26 10:16:14 192.168.122.209 [65525.530553] [tempesta fw] exiting... Apr 26 10:16:15 192.168.122.209 [65525.658979] [tdb] Shutdown Tempesta DB Apr 26 10:16:15 192.168.122.209 [65525.872236] End test: t_malformed.test_malformed_crlfs.MalformedCrlfTest.test_07_double_crlf Apr 26 10:16:15 192.168.122.209 [65525.895620] Start test: t_malformed.test_malformed_crlfs.MalformedCrlfTest.test_08_double_crlf_pipeline Apr 26 10:16:16 192.168.122.209 [65527.019066] [tdb] Start Tempesta DB Apr 26 10:16:16 192.168.122.209 [65527.159323] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:16:17 192.168.122.209 [65527.772262] [tempesta fw] Configuration processing is completed. Apr 26 10:16:17 192.168.122.209 [65527.825748] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:16:17 192.168.122.209 [65527.855835] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:16:17 192.168.122.209 [65527.885264] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:16:17 192.168.122.209 [65527.924237] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:16:17 192.168.122.209 [65527.964207] [tempesta fw] Tempesta FW is ready Apr 26 10:16:17 192.168.122.209 [65528.095735] [tempesta fw] Warning: Parser error: state=Req_MethodUnknown input(-0)=0xd(' ') data_len=1 off=0 Apr 26 10:16:17 192.168.122.209 [65528.502740] [tdb] Close table 'client0.tdb' Apr 26 10:16:18 192.168.122.209 [65528.690988] [tdb] Close table 'sessions0.tdb' Apr 26 10:16:18 192.168.122.209 [65528.916814] [tdb] Close table 'filter0.tdb' Apr 26 10:16:18 192.168.122.209 [65528.917224] [tempesta fw] modules are stopped Apr 26 10:16:18 192.168.122.209 [65529.092174] [tempesta fw] exiting... Apr 26 10:16:18 192.168.122.209 [65529.209785] [tdb] Shutdown Tempesta DB Apr 26 10:16:18 192.168.122.209 [65529.417511] End test: t_malformed.test_malformed_crlfs.MalformedCrlfTest.test_08_double_crlf_pipeline Apr 26 10:16:18 192.168.122.209 [65529.431577] Start test: t_malformed.test_malformed_crlfs.MalformedCrlfTest.test_09_double_lf Apr 26 10:16:19 192.168.122.209 [65530.424085] [tdb] Start Tempesta DB Apr 26 10:16:19 192.168.122.209 [65530.573951] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:16:20 192.168.122.209 [65531.148360] [tempesta fw] Configuration processing is completed. Apr 26 10:16:20 192.168.122.209 [65531.218792] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:16:20 192.168.122.209 [65531.255722] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:16:20 192.168.122.209 [65531.289178] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:16:20 192.168.122.209 [65531.336312] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:16:20 192.168.122.209 [65531.380240] [tempesta fw] Tempesta FW is ready Apr 26 10:16:20 192.168.122.209 [65531.492766] [tempesta fw] Warning: Parser error: state=Req_MethodUnknown input(-0)=0xa(' [65531.492766] ') data_len=1 off=0 Apr 26 10:16:21 192.168.122.209 [65531.931181] [tdb] Close table 'client0.tdb' Apr 26 10:16:21 192.168.122.209 [65532.118221] [tdb] Close table 'sessions0.tdb' Apr 26 10:16:21 192.168.122.209 [65532.361095] [tdb] Close table 'filter0.tdb' Apr 26 10:16:21 192.168.122.209 [65532.361537] [tempesta fw] modules are stopped Apr 26 10:16:21 192.168.122.209 [65532.533864] [tempesta fw] exiting... Apr 26 10:16:22 192.168.122.209 [65532.662712] [tdb] Shutdown Tempesta DB Apr 26 10:16:22 192.168.122.209 [65532.847109] End test: t_malformed.test_malformed_crlfs.MalformedCrlfTest.test_09_double_lf Apr 26 10:16:22 192.168.122.209 [65532.857319] Start test: t_malformed.test_malformed_crlfs.MalformedCrlfTest.test_10_double_lf_pipeline Apr 26 10:16:23 192.168.122.209 [65533.882144] [tdb] Start Tempesta DB Apr 26 10:16:23 192.168.122.209 [65534.026972] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:16:23 192.168.122.209 [65534.628369] [tempesta fw] Configuration processing is completed. Apr 26 10:16:24 192.168.122.209 [65534.702005] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:16:24 192.168.122.209 [65534.735759] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:16:24 192.168.122.209 [65534.767129] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:16:24 192.168.122.209 [65534.808298] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:16:24 192.168.122.209 [65534.856248] [tempesta fw] Tempesta FW is ready Apr 26 10:16:24 192.168.122.209 [65534.988351] [tempesta fw] Warning: Parser error: state=Req_MethodUnknown input(-0)=0xa(' [65534.988351] ') data_len=1 off=0 Apr 26 10:16:24 192.168.122.209 [65535.425061] [tdb] Close table 'client0.tdb' Apr 26 10:16:24 192.168.122.209 [65535.612581] [tdb] Close table 'sessions0.tdb' Apr 26 10:16:25 192.168.122.209 [65535.863983] [tdb] Close table 'filter0.tdb' Apr 26 10:16:25 192.168.122.209 [65535.864418] [tempesta fw] modules are stopped Apr 26 10:16:25 192.168.122.209 [65536.039462] [tempesta fw] exiting... Apr 26 10:16:25 192.168.122.209 [65536.151324] [tdb] Shutdown Tempesta DB Apr 26 10:16:25 192.168.122.209 [65536.367025] End test: t_malformed.test_malformed_crlfs.MalformedCrlfTest.test_10_double_lf_pipeline Apr 26 10:16:25 192.168.122.209 [65536.384100] Start test: t_malformed.test_malformed_headers.EtagAlphabetTest.test_etag_with_x21 Apr 26 10:16:26 192.168.122.209 [65537.462554] [tdb] Start Tempesta DB Apr 26 10:16:26 192.168.122.209 [65537.610894] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:16:27 192.168.122.209 [65538.361681] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65538.361681] Maybe that's fine, but it's worth checking the [65538.361681] config - if there is no relations between the [65538.361681] names, then host name confusion attack is possible. Apr 26 10:16:27 192.168.122.209 [65538.516414] [tempesta fw] Configuration processing is completed. Apr 26 10:16:27 192.168.122.209 [65538.574295] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:16:27 192.168.122.209 [65538.607628] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:16:28 192.168.122.209 [65538.639566] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:16:28 192.168.122.209 [65538.696345] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:16:28 192.168.122.209 [65538.698091] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:16:28 192.168.122.209 [65538.760307] [tempesta fw] Tempesta FW is ready Apr 26 10:16:28 192.168.122.209 [65539.336662] [tdb] Close table 'client0.tdb' Apr 26 10:16:28 192.168.122.209 [65539.525659] [tdb] Close table 'sessions0.tdb' Apr 26 10:16:29 192.168.122.209 [65539.775928] [tdb] Close table 'filter0.tdb' Apr 26 10:16:29 192.168.122.209 [65539.776371] [tempesta fw] modules are stopped Apr 26 10:16:29 192.168.122.209 [65539.982775] [tempesta fw] exiting... Apr 26 10:16:29 192.168.122.209 [65540.092566] [tdb] Shutdown Tempesta DB Apr 26 10:16:29 192.168.122.209 [65540.307094] End test: t_malformed.test_malformed_headers.EtagAlphabetTest.test_etag_with_x21 Apr 26 10:16:29 192.168.122.209 [65540.322843] Start test: t_malformed.test_malformed_headers.EtagAlphabetTest.test_etag_with_x23 Apr 26 10:16:30 192.168.122.209 [65541.332025] [tdb] Start Tempesta DB Apr 26 10:16:30 192.168.122.209 [65541.465631] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:16:31 192.168.122.209 [65542.173718] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65542.173718] Maybe that's fine, but it's worth checking the [65542.173718] config - if there is no relations between the [65542.173718] names, then host name confusion attack is possible. Apr 26 10:16:31 192.168.122.209 [65542.344410] [tempesta fw] Configuration processing is completed. Apr 26 10:16:31 192.168.122.209 [65542.396829] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:16:31 192.168.122.209 [65542.426526] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:16:31 192.168.122.209 [65542.457491] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:16:31 192.168.122.209 [65542.496391] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:16:31 192.168.122.209 [65542.497886] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:16:31 192.168.122.209 [65542.536339] [tempesta fw] Tempesta FW is ready Apr 26 10:16:32 192.168.122.209 [65543.120494] [tdb] Close table 'client0.tdb' Apr 26 10:16:32 192.168.122.209 [65543.309682] [tdb] Close table 'sessions0.tdb' Apr 26 10:16:32 192.168.122.209 [65543.542151] [tdb] Close table 'filter0.tdb' Apr 26 10:16:32 192.168.122.209 [65543.542573] [tempesta fw] modules are stopped Apr 26 10:16:33 192.168.122.209 [65543.761318] [tempesta fw] exiting... Apr 26 10:16:33 192.168.122.209 [65543.875906] [tdb] Shutdown Tempesta DB Apr 26 10:16:33 192.168.122.209 [65544.064442] End test: t_malformed.test_malformed_headers.EtagAlphabetTest.test_etag_with_x23 Apr 26 10:16:33 192.168.122.209 [65544.086221] Start test: t_malformed.test_malformed_headers.EtagAlphabetTest.test_etag_with_x7f Apr 26 10:16:34 192.168.122.209 [65545.095047] [tdb] Start Tempesta DB Apr 26 10:16:34 192.168.122.209 [65545.240878] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:16:35 192.168.122.209 [65545.921788] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65545.921788] Maybe that's fine, but it's worth checking the [65545.921788] config - if there is no relations between the [65545.921788] names, then host name confusion attack is possible. Apr 26 10:16:35 192.168.122.209 [65546.072496] [tempesta fw] Configuration processing is completed. Apr 26 10:16:35 192.168.122.209 [65546.143131] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:16:35 192.168.122.209 [65546.177577] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:16:35 192.168.122.209 [65546.208894] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:16:35 192.168.122.209 [65546.248454] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:16:35 192.168.122.209 [65546.250212] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:16:35 192.168.122.209 [65546.296404] [tempesta fw] Tempesta FW is ready Apr 26 10:16:35 192.168.122.209 [65546.433313] [tempesta fw] Warning: Parser error: state=Resp_HdrEtagV input(-0)=0x7f('') data_len=1 off=0 Apr 26 10:16:35 192.168.122.209 [65546.434703] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 10:16:36 192.168.122.209 [65546.816543] [tdb] Close table 'client0.tdb' Apr 26 10:16:36 192.168.122.209 [65547.020567] [tdb] Close table 'sessions0.tdb' Apr 26 10:16:36 192.168.122.209 [65547.254611] [tdb] Close table 'filter0.tdb' Apr 26 10:16:36 192.168.122.209 [65547.255029] [tempesta fw] modules are stopped Apr 26 10:16:36 192.168.122.209 [65547.451434] [tempesta fw] exiting... Apr 26 10:16:36 192.168.122.209 [65547.547445] [tdb] Shutdown Tempesta DB Apr 26 10:16:37 192.168.122.209 [65547.751227] End test: t_malformed.test_malformed_headers.EtagAlphabetTest.test_etag_with_x7f Apr 26 10:16:37 192.168.122.209 [65547.763872] Start test: t_malformed.test_malformed_headers.EtagAlphabetTest.test_etag_with_xf7 Apr 26 10:16:38 192.168.122.209 [65548.824053] [tdb] Start Tempesta DB Apr 26 10:16:38 192.168.122.209 [65548.977859] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:16:39 192.168.122.209 [65549.653808] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65549.653808] Maybe that's fine, but it's worth checking the [65549.653808] config - if there is no relations between the [65549.653808] names, then host name confusion attack is possible. Apr 26 10:16:39 192.168.122.209 [65549.808521] [tempesta fw] Configuration processing is completed. Apr 26 10:16:39 192.168.122.209 [65549.866086] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:16:39 192.168.122.209 [65549.899393] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:16:39 192.168.122.209 [65549.929677] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:16:39 192.168.122.209 [65549.988484] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:16:39 192.168.122.209 [65549.990209] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:16:39 192.168.122.209 [65550.028432] [tempesta fw] Tempesta FW is ready Apr 26 10:16:39 192.168.122.209 [65550.603457] [tdb] Close table 'client0.tdb' Apr 26 10:16:40 192.168.122.209 [65550.806364] [tdb] Close table 'sessions0.tdb' Apr 26 10:16:40 192.168.122.209 [65551.050421] [tdb] Close table 'filter0.tdb' Apr 26 10:16:40 192.168.122.209 [65551.050851] [tempesta fw] modules are stopped Apr 26 10:16:40 192.168.122.209 [65551.249196] [tempesta fw] exiting... Apr 26 10:16:40 192.168.122.209 [65551.395648] [tdb] Shutdown Tempesta DB Apr 26 10:16:40 192.168.122.209 [65551.606908] End test: t_malformed.test_malformed_headers.EtagAlphabetTest.test_etag_with_xf7 Apr 26 10:16:41 192.168.122.209 [65551.629307] Start test: t_malformed.test_malformed_headers.MalformedRequestsTest.test_accept Apr 26 10:16:42 192.168.122.209 [65552.699911] [tdb] Start Tempesta DB Apr 26 10:16:42 192.168.122.209 [65552.846832] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:16:42 192.168.122.209 [65553.557802] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65553.557802] Maybe that's fine, but it's worth checking the [65553.557802] config - if there is no relations between the [65553.557802] names, then host name confusion attack is possible. Apr 26 10:16:43 192.168.122.209 [65553.700551] [tempesta fw] Configuration processing is completed. Apr 26 10:16:43 192.168.122.209 [65553.754226] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:16:43 192.168.122.209 [65553.783495] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:16:43 192.168.122.209 [65553.811708] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:16:43 192.168.122.209 [65553.852490] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:16:43 192.168.122.209 [65553.853812] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:16:43 192.168.122.209 [65553.892503] [tempesta fw] Tempesta FW is ready Apr 26 10:16:43 192.168.122.209 [65554.029263] [tempesta fw] Warning: Parser error: state=Req_HdrAcceptV input(-0)=0xd(' ') data_len=1 off=0 Apr 26 10:16:43 192.168.122.209 [65554.439869] [tdb] Close table 'client0.tdb' Apr 26 10:16:44 192.168.122.209 [65554.632216] [tdb] Close table 'sessions0.tdb' Apr 26 10:16:44 192.168.122.209 [65554.882449] [tdb] Close table 'filter0.tdb' Apr 26 10:16:44 192.168.122.209 [65554.882873] [tempesta fw] modules are stopped Apr 26 10:16:44 192.168.122.209 [65555.102091] [tempesta fw] exiting... Apr 26 10:16:44 192.168.122.209 [65555.229658] [tdb] Shutdown Tempesta DB Apr 26 10:16:44 192.168.122.209 [65555.409665] End test: t_malformed.test_malformed_headers.MalformedRequestsTest.test_accept Apr 26 10:16:44 192.168.122.209 [65555.426554] Start test: t_malformed.test_malformed_headers.MalformedRequestsTest.test_expect_invalid Apr 26 10:16:45 192.168.122.209 [65556.441665] [tdb] Start Tempesta DB Apr 26 10:16:45 192.168.122.209 [65556.579851] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:16:46 192.168.122.209 [65557.253918] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65557.253918] Maybe that's fine, but it's worth checking the [65557.253918] config - if there is no relations between the [65557.253918] names, then host name confusion attack is possible. Apr 26 10:16:46 192.168.122.209 [65557.396644] [tempesta fw] Configuration processing is completed. Apr 26 10:16:46 192.168.122.209 [65557.454299] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:16:46 192.168.122.209 [65557.495306] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:16:46 192.168.122.209 [65557.527287] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:16:46 192.168.122.209 [65557.576589] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:16:46 192.168.122.209 [65557.578357] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:16:46 192.168.122.209 [65557.620548] [tempesta fw] Tempesta FW is ready Apr 26 10:16:47 192.168.122.209 [65557.768157] [tempesta fw] Warning: Parser error: state=Req_HdrExpectV input(-0)=0x69('i') data_len=1 off=0 Apr 26 10:16:47 192.168.122.209 [65558.186369] [tdb] Close table 'client0.tdb' Apr 26 10:16:47 192.168.122.209 [65558.374834] [tdb] Close table 'sessions0.tdb' Apr 26 10:16:47 192.168.122.209 [65558.609343] [tdb] Close table 'filter0.tdb' Apr 26 10:16:47 192.168.122.209 [65558.609783] [tempesta fw] modules are stopped Apr 26 10:16:48 192.168.122.209 [65558.799909] [tempesta fw] exiting... Apr 26 10:16:48 192.168.122.209 [65558.924332] [tdb] Shutdown Tempesta DB Apr 26 10:16:48 192.168.122.209 [65559.148203] End test: t_malformed.test_malformed_headers.MalformedRequestsTest.test_expect_invalid Apr 26 10:16:48 192.168.122.209 [65559.169784] Start test: t_malformed.test_malformed_headers.MalformedRequestsTest.test_host Apr 26 10:16:49 192.168.122.209 [65560.219343] [tdb] Start Tempesta DB Apr 26 10:16:49 192.168.122.209 [65560.360080] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:16:50 192.168.122.209 [65561.037957] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65561.037957] Maybe that's fine, but it's worth checking the [65561.037957] config - if there is no relations between the [65561.037957] names, then host name confusion attack is possible. Apr 26 10:16:50 192.168.122.209 [65561.168662] [tempesta fw] Configuration processing is completed. Apr 26 10:16:50 192.168.122.209 [65561.226781] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:16:50 192.168.122.209 [65561.260087] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:16:50 192.168.122.209 [65561.295935] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:16:50 192.168.122.209 [65561.332637] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:16:50 192.168.122.209 [65561.334365] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:16:50 192.168.122.209 [65561.380574] [tempesta fw] Tempesta FW is ready Apr 26 10:16:50 192.168.122.209 [65561.519209] [tempesta fw] Warning: Parser error: state=Req_HdrHostV input(-0)=0x2f('/') data_len=1 off=0 Apr 26 10:16:51 192.168.122.209 [65561.964951] [tdb] Close table 'client0.tdb' Apr 26 10:16:51 192.168.122.209 [65562.149874] [tdb] Close table 'sessions0.tdb' Apr 26 10:16:51 192.168.122.209 [65562.372467] [tdb] Close table 'filter0.tdb' Apr 26 10:16:51 192.168.122.209 [65562.372894] [tempesta fw] modules are stopped Apr 26 10:16:51 192.168.122.209 [65562.555053] [tempesta fw] exiting... Apr 26 10:16:52 192.168.122.209 [65562.660813] [tdb] Shutdown Tempesta DB Apr 26 10:16:52 192.168.122.209 [65562.886354] End test: t_malformed.test_malformed_headers.MalformedRequestsTest.test_host Apr 26 10:16:52 192.168.122.209 [65562.905874] Start test: t_malformed.test_malformed_headers.MalformedRequestsTest.test_if_none_match Apr 26 10:16:53 192.168.122.209 [65563.914408] [tdb] Start Tempesta DB Apr 26 10:16:53 192.168.122.209 [65564.050888] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:16:54 192.168.122.209 [65564.749998] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65564.749998] Maybe that's fine, but it's worth checking the [65564.749998] config - if there is no relations between the [65564.749998] names, then host name confusion attack is possible. Apr 26 10:16:54 192.168.122.209 [65564.884720] [tempesta fw] Configuration processing is completed. Apr 26 10:16:54 192.168.122.209 [65564.960813] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:16:54 192.168.122.209 [65564.994324] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:16:54 192.168.122.209 [65565.025330] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:16:54 192.168.122.209 [65565.068689] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:16:54 192.168.122.209 [65565.070433] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:16:54 192.168.122.209 [65565.108615] [tempesta fw] Tempesta FW is ready Apr 26 10:16:54 192.168.122.209 [65565.235354] [tempesta fw] Warning: Parser error: state=Req_HdrIf_None_MatchV input(-0)=0x71('q') data_len=1 off=0 Apr 26 10:16:55 192.168.122.209 [65565.660255] [tdb] Close table 'client0.tdb' Apr 26 10:16:55 192.168.122.209 [65565.852358] [tdb] Close table 'sessions0.tdb' Apr 26 10:16:55 192.168.122.209 [65566.086253] [tdb] Close table 'filter0.tdb' Apr 26 10:16:55 192.168.122.209 [65566.086687] [tempesta fw] modules are stopped Apr 26 10:16:55 192.168.122.209 [65566.284176] [tempesta fw] exiting... Apr 26 10:16:55 192.168.122.209 [65566.417886] [tdb] Shutdown Tempesta DB Apr 26 10:16:55 192.168.122.209 [65566.626588] End test: t_malformed.test_malformed_headers.MalformedRequestsTest.test_if_none_match Apr 26 10:16:56 192.168.122.209 [65566.649575] Start test: t_malformed.test_malformed_headers.MalformedRequestsTest.test_missing_name Apr 26 10:16:57 192.168.122.209 [65567.708245] [tdb] Start Tempesta DB Apr 26 10:16:57 192.168.122.209 [65567.850467] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:16:57 192.168.122.209 [65568.542010] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65568.542010] Maybe that's fine, but it's worth checking the [65568.542010] config - if there is no relations between the [65568.542010] names, then host name confusion attack is possible. Apr 26 10:16:58 192.168.122.209 [65568.680732] [tempesta fw] Configuration processing is completed. Apr 26 10:16:58 192.168.122.209 [65568.733098] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:16:58 192.168.122.209 [65568.763393] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:16:58 192.168.122.209 [65568.793468] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:16:58 192.168.122.209 [65568.848732] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:16:58 192.168.122.209 [65568.850491] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:16:58 192.168.122.209 [65568.908664] [tempesta fw] Tempesta FW is ready Apr 26 10:16:58 192.168.122.209 [65569.040493] [tempesta fw] Warning: Parser error: state=RGen_HdrOtherN input(-0)=0x3a(':') data_len=1 off=0 Apr 26 10:16:58 192.168.122.209 [65569.490895] [tdb] Close table 'client0.tdb' Apr 26 10:16:59 192.168.122.209 [65569.686306] [tdb] Close table 'sessions0.tdb' Apr 26 10:16:59 192.168.122.209 [65569.922495] [tdb] Close table 'filter0.tdb' Apr 26 10:16:59 192.168.122.209 [65569.922909] [tempesta fw] modules are stopped Apr 26 10:16:59 192.168.122.209 [65570.126103] [tempesta fw] exiting... Apr 26 10:16:59 192.168.122.209 [65570.232926] [tdb] Shutdown Tempesta DB Apr 26 10:16:59 192.168.122.209 [65570.444934] End test: t_malformed.test_malformed_headers.MalformedRequestsTest.test_missing_name Apr 26 10:16:59 192.168.122.209 [65570.454882] Start test: t_malformed.test_malformed_headers.MalformedRequestsTest.test_transfer_encoding Apr 26 10:17:00 192.168.122.209 [65571.515079] [tdb] Start Tempesta DB Apr 26 10:17:01 192.168.122.209 [65571.655159] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:17:01 192.168.122.209 [65572.326058] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65572.326058] Maybe that's fine, but it's worth checking the [65572.326058] config - if there is no relations between the [65572.326058] names, then host name confusion attack is possible. Apr 26 10:17:01 192.168.122.209 [65572.484825] [tempesta fw] Configuration processing is completed. Apr 26 10:17:01 192.168.122.209 [65572.552121] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:17:01 192.168.122.209 [65572.586050] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:17:01 192.168.122.209 [65572.616573] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:17:02 192.168.122.209 [65572.688802] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:17:02 192.168.122.209 [65572.690562] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:17:02 192.168.122.209 [65572.740742] [tempesta fw] Tempesta FW is ready Apr 26 10:17:02 192.168.122.209 [65572.894968] [tempesta fw] Warning: Parser error: state=RGen_BodyInit input(-0)=0xa(' [65572.894968] ') data_len=1 off=0 Apr 26 10:17:02 192.168.122.209 [65573.331957] [tdb] Close table 'client0.tdb' Apr 26 10:17:02 192.168.122.209 [65573.519555] [tdb] Close table 'sessions0.tdb' Apr 26 10:17:03 192.168.122.209 [65573.753780] [tdb] Close table 'filter0.tdb' Apr 26 10:17:03 192.168.122.209 [65573.754193] [tempesta fw] modules are stopped Apr 26 10:17:03 192.168.122.209 [65573.994269] [tempesta fw] exiting... Apr 26 10:17:03 192.168.122.209 [65574.121113] [tdb] Shutdown Tempesta DB Apr 26 10:17:03 192.168.122.209 [65574.339628] End test: t_malformed.test_malformed_headers.MalformedRequestsTest.test_transfer_encoding Apr 26 10:17:03 192.168.122.209 [65574.358304] Start test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_accept_charset Apr 26 10:17:04 192.168.122.209 [65575.400911] [tdb] Start Tempesta DB Apr 26 10:17:04 192.168.122.209 [65575.538453] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:17:05 192.168.122.209 [65576.242171] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65576.242171] Maybe that's fine, but it's worth checking the [65576.242171] config - if there is no relations between the [65576.242171] names, then host name confusion attack is possible. Apr 26 10:17:05 192.168.122.209 [65576.388864] [tempesta fw] Configuration processing is completed. Apr 26 10:17:05 192.168.122.209 [65576.451209] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:17:05 192.168.122.209 [65576.484547] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:17:05 192.168.122.209 [65576.516894] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:17:05 192.168.122.209 [65576.592820] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:17:05 192.168.122.209 [65576.594584] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:17:06 192.168.122.209 [65576.640768] [tempesta fw] Tempesta FW is ready Apr 26 10:17:06 192.168.122.209 [65577.220441] [tdb] Close table 'client0.tdb' Apr 26 10:17:06 192.168.122.209 [65577.420811] [tdb] Close table 'sessions0.tdb' Apr 26 10:17:07 192.168.122.209 [65577.655011] [tdb] Close table 'filter0.tdb' Apr 26 10:17:07 192.168.122.209 [65577.655406] [tempesta fw] modules are stopped Apr 26 10:17:07 192.168.122.209 [65577.850554] [tempesta fw] exiting... Apr 26 10:17:07 192.168.122.209 [65577.981182] [tdb] Shutdown Tempesta DB Apr 26 10:17:07 192.168.122.209 [65578.203116] End test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_accept_charset Apr 26 10:17:07 192.168.122.209 [65578.216180] Start test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_accept_encoding Apr 26 10:17:08 192.168.122.209 [65579.312270] [tdb] Start Tempesta DB Apr 26 10:17:08 192.168.122.209 [65579.451941] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:17:09 192.168.122.209 [65580.170162] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65580.170162] Maybe that's fine, but it's worth checking the [65580.170162] config - if there is no relations between the [65580.170162] names, then host name confusion attack is possible. Apr 26 10:17:09 192.168.122.209 [65580.300878] [tempesta fw] Configuration processing is completed. Apr 26 10:17:09 192.168.122.209 [65580.353320] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:17:09 192.168.122.209 [65580.383351] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:17:09 192.168.122.209 [65580.414048] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:17:09 192.168.122.209 [65580.460857] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:17:09 192.168.122.209 [65580.462574] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:17:09 192.168.122.209 [65580.500820] [tempesta fw] Tempesta FW is ready Apr 26 10:17:10 192.168.122.209 [65581.071094] [tdb] Close table 'client0.tdb' Apr 26 10:17:10 192.168.122.209 [65581.250200] [tdb] Close table 'sessions0.tdb' Apr 26 10:17:10 192.168.122.209 [65581.475010] [tdb] Close table 'filter0.tdb' Apr 26 10:17:10 192.168.122.209 [65581.475455] [tempesta fw] modules are stopped Apr 26 10:17:11 192.168.122.209 [65581.693131] [tempesta fw] exiting... Apr 26 10:17:11 192.168.122.209 [65581.806084] [tdb] Shutdown Tempesta DB Apr 26 10:17:11 192.168.122.209 [65581.999230] End test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_accept_encoding Apr 26 10:17:11 192.168.122.209 [65582.009839] Start test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_accept_language Apr 26 10:17:12 192.168.122.209 [65583.109426] [tdb] Start Tempesta DB Apr 26 10:17:12 192.168.122.209 [65583.254218] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:17:13 192.168.122.209 [65583.946184] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65583.946184] Maybe that's fine, but it's worth checking the [65583.946184] config - if there is no relations between the [65583.946184] names, then host name confusion attack is possible. Apr 26 10:17:13 192.168.122.209 [65584.080844] [tempesta fw] Configuration processing is completed. Apr 26 10:17:13 192.168.122.209 [65584.134482] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:17:13 192.168.122.209 [65584.164527] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:17:13 192.168.122.209 [65584.201873] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:17:13 192.168.122.209 [65584.244904] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:17:13 192.168.122.209 [65584.246658] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:17:13 192.168.122.209 [65584.288868] [tempesta fw] Tempesta FW is ready Apr 26 10:17:14 192.168.122.209 [65584.855205] [tdb] Close table 'client0.tdb' Apr 26 10:17:14 192.168.122.209 [65585.040512] [tdb] Close table 'sessions0.tdb' Apr 26 10:17:14 192.168.122.209 [65585.276841] [tdb] Close table 'filter0.tdb' Apr 26 10:17:14 192.168.122.209 [65585.277282] [tempesta fw] modules are stopped Apr 26 10:17:14 192.168.122.209 [65585.493637] [tempesta fw] exiting... Apr 26 10:17:14 192.168.122.209 [65585.625184] [tdb] Shutdown Tempesta DB Apr 26 10:17:15 192.168.122.209 [65585.849276] End test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_accept_language Apr 26 10:17:15 192.168.122.209 [65585.862450] Start test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_content_encoding Apr 26 10:17:16 192.168.122.209 [65586.918762] [tdb] Start Tempesta DB Apr 26 10:17:16 192.168.122.209 [65587.053516] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:17:17 192.168.122.209 [65587.730261] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65587.730261] Maybe that's fine, but it's worth checking the [65587.730261] config - if there is no relations between the [65587.730261] names, then host name confusion attack is possible. Apr 26 10:17:17 192.168.122.209 [65587.888996] [tempesta fw] Configuration processing is completed. Apr 26 10:17:17 192.168.122.209 [65587.948013] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:17:17 192.168.122.209 [65587.981744] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:17:17 192.168.122.209 [65588.012622] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:17:17 192.168.122.209 [65588.068969] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:17:17 192.168.122.209 [65588.070755] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:17:17 192.168.122.209 [65588.108919] [tempesta fw] Tempesta FW is ready Apr 26 10:17:18 192.168.122.209 [65588.691446] [tdb] Close table 'client0.tdb' Apr 26 10:17:18 192.168.122.209 [65588.882260] [tdb] Close table 'sessions0.tdb' Apr 26 10:17:18 192.168.122.209 [65589.121149] [tdb] Close table 'filter0.tdb' Apr 26 10:17:18 192.168.122.209 [65589.121583] [tempesta fw] modules are stopped Apr 26 10:17:18 192.168.122.209 [65589.335559] [tempesta fw] exiting... Apr 26 10:17:18 192.168.122.209 [65589.444655] [tdb] Shutdown Tempesta DB Apr 26 10:17:19 192.168.122.209 [65589.690369] End test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_content_encoding Apr 26 10:17:19 192.168.122.209 [65589.706548] Start test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_content_language Apr 26 10:17:20 192.168.122.209 [65590.707994] [tdb] Start Tempesta DB Apr 26 10:17:20 192.168.122.209 [65590.865091] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:17:20 192.168.122.209 [65591.582369] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65591.582369] Maybe that's fine, but it's worth checking the [65591.582369] config - if there is no relations between the [65591.582369] names, then host name confusion attack is possible. Apr 26 10:17:21 192.168.122.209 [65591.745036] [tempesta fw] Configuration processing is completed. Apr 26 10:17:21 192.168.122.209 [65591.804896] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:17:21 192.168.122.209 [65591.839125] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:17:21 192.168.122.209 [65591.870228] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:17:21 192.168.122.209 [65591.945014] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:17:21 192.168.122.209 [65591.946804] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:17:21 192.168.122.209 [65591.992971] [tempesta fw] Tempesta FW is ready Apr 26 10:17:21 192.168.122.209 [65592.566424] [tdb] Close table 'client0.tdb' Apr 26 10:17:22 192.168.122.209 [65592.750691] [tdb] Close table 'sessions0.tdb' Apr 26 10:17:22 192.168.122.209 [65593.516889] [tdb] Close table 'filter0.tdb' Apr 26 10:17:22 192.168.122.209 [65593.517328] [tempesta fw] modules are stopped Apr 26 10:17:25 192.168.122.209 [65595.959383] [tempesta fw] exiting... Apr 26 10:17:26 192.168.122.209 [65596.880194] [tdb] Shutdown Tempesta DB Apr 26 10:17:27 192.168.122.209 [65597.792144] End test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_content_language Apr 26 10:17:27 192.168.122.209 [65597.800192] Start test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_content_location Apr 26 10:17:28 192.168.122.209 [65598.805907] [tdb] Start Tempesta DB Apr 26 10:17:28 192.168.122.209 [65598.960662] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:17:29 192.168.122.209 [65599.662389] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65599.662389] Maybe that's fine, but it's worth checking the [65599.662389] config - if there is no relations between the [65599.662389] names, then host name confusion attack is possible. Apr 26 10:17:29 192.168.122.209 [65599.809138] [tempesta fw] Configuration processing is completed. Apr 26 10:17:29 192.168.122.209 [65599.865354] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:17:29 192.168.122.209 [65599.897783] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:17:29 192.168.122.209 [65599.928727] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:17:29 192.168.122.209 [65599.993039] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:17:29 192.168.122.209 [65599.994780] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:17:29 192.168.122.209 [65600.045050] [tempesta fw] Tempesta FW is ready Apr 26 10:17:30 192.168.122.209 [65600.661612] [tdb] Close table 'client0.tdb' Apr 26 10:17:30 192.168.122.209 [65600.850605] [tdb] Close table 'sessions0.tdb' Apr 26 10:17:30 192.168.122.209 [65601.075851] [tdb] Close table 'filter0.tdb' Apr 26 10:17:30 192.168.122.209 [65601.076288] [tempesta fw] modules are stopped Apr 26 10:17:30 192.168.122.209 [65601.315543] [tempesta fw] exiting... Apr 26 10:17:30 192.168.122.209 [65601.418501] [tdb] Shutdown Tempesta DB Apr 26 10:17:31 192.168.122.209 [65601.644269] End test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_content_location Apr 26 10:17:31 192.168.122.209 [65601.655748] Start test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_content_range Apr 26 10:17:32 192.168.122.209 [65602.711433] [tdb] Start Tempesta DB Apr 26 10:17:32 192.168.122.209 [65602.858742] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:17:32 192.168.122.209 [65603.594489] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65603.594489] Maybe that's fine, but it's worth checking the [65603.594489] config - if there is no relations between the [65603.594489] names, then host name confusion attack is possible. Apr 26 10:17:33 192.168.122.209 [65603.745176] [tempesta fw] Configuration processing is completed. Apr 26 10:17:33 192.168.122.209 [65603.807002] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:17:33 192.168.122.209 [65603.843521] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:17:33 192.168.122.209 [65603.875297] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:17:33 192.168.122.209 [65603.921147] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:17:33 192.168.122.209 [65603.922899] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:17:33 192.168.122.209 [65603.969111] [tempesta fw] Tempesta FW is ready Apr 26 10:17:33 192.168.122.209 [65604.527411] [tdb] Close table 'client0.tdb' Apr 26 10:17:34 192.168.122.209 [65604.715404] [tdb] Close table 'sessions0.tdb' Apr 26 10:17:34 192.168.122.209 [65604.943573] [tdb] Close table 'filter0.tdb' Apr 26 10:17:34 192.168.122.209 [65604.943985] [tempesta fw] modules are stopped Apr 26 10:17:34 192.168.122.209 [65605.133259] [tempesta fw] exiting... Apr 26 10:17:34 192.168.122.209 [65605.246131] [tdb] Shutdown Tempesta DB Apr 26 10:17:34 192.168.122.209 [65605.505731] End test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_content_range Apr 26 10:17:34 192.168.122.209 [65605.534716] Start test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_content_type Apr 26 10:17:35 192.168.122.209 [65606.551677] [tdb] Start Tempesta DB Apr 26 10:17:36 192.168.122.209 [65606.699287] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:17:36 192.168.122.209 [65607.418491] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65607.418491] Maybe that's fine, but it's worth checking the [65607.418491] config - if there is no relations between the [65607.418491] names, then host name confusion attack is possible. Apr 26 10:17:36 192.168.122.209 [65607.561258] [tempesta fw] Configuration processing is completed. Apr 26 10:17:36 192.168.122.209 [65607.616738] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:17:37 192.168.122.209 [65607.650258] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:17:37 192.168.122.209 [65607.682147] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:17:37 192.168.122.209 [65607.729153] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:17:37 192.168.122.209 [65607.730926] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:17:37 192.168.122.209 [65607.781141] [tempesta fw] Tempesta FW is ready Apr 26 10:17:37 192.168.122.209 [65608.354557] [tdb] Close table 'client0.tdb' Apr 26 10:17:37 192.168.122.209 [65608.544570] [tdb] Close table 'sessions0.tdb' Apr 26 10:17:38 192.168.122.209 [65608.811809] [tdb] Close table 'filter0.tdb' Apr 26 10:17:38 192.168.122.209 [65608.812246] [tempesta fw] modules are stopped Apr 26 10:17:38 192.168.122.209 [65609.001241] [tempesta fw] exiting... Apr 26 10:17:38 192.168.122.209 [65609.134084] [tdb] Shutdown Tempesta DB Apr 26 10:17:38 192.168.122.209 [65609.378832] End test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_content_type Apr 26 10:17:38 192.168.122.209 [65609.394367] Start test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_date Apr 26 10:17:39 192.168.122.209 [65610.422906] [tdb] Start Tempesta DB Apr 26 10:17:39 192.168.122.209 [65610.571141] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:17:40 192.168.122.209 [65611.262584] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65611.262584] Maybe that's fine, but it's worth checking the [65611.262584] config - if there is no relations between the [65611.262584] names, then host name confusion attack is possible. Apr 26 10:17:40 192.168.122.209 [65611.413303] [tempesta fw] Configuration processing is completed. Apr 26 10:17:40 192.168.122.209 [65611.473672] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:17:40 192.168.122.209 [65611.508978] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:17:40 192.168.122.209 [65611.540948] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:17:40 192.168.122.209 [65611.605251] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:17:40 192.168.122.209 [65611.606984] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:17:41 192.168.122.209 [65611.645253] [tempesta fw] Tempesta FW is ready Apr 26 10:17:41 192.168.122.209 [65612.240770] [tdb] Close table 'client0.tdb' Apr 26 10:17:41 192.168.122.209 [65612.433296] [tdb] Close table 'sessions0.tdb' Apr 26 10:17:42 192.168.122.209 [65612.665854] [tdb] Close table 'filter0.tdb' Apr 26 10:17:42 192.168.122.209 [65612.666288] [tempesta fw] modules are stopped Apr 26 10:17:42 192.168.122.209 [65612.890468] [tempesta fw] exiting... Apr 26 10:17:42 192.168.122.209 [65613.004209] [tdb] Shutdown Tempesta DB Apr 26 10:17:42 192.168.122.209 [65613.270270] End test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_date Apr 26 10:17:42 192.168.122.209 [65613.283946] Start test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_expect Apr 26 10:17:43 192.168.122.209 [65614.305480] [tdb] Start Tempesta DB Apr 26 10:17:43 192.168.122.209 [65614.440182] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:17:44 192.168.122.209 [65615.142605] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65615.142605] Maybe that's fine, but it's worth checking the [65615.142605] config - if there is no relations between the [65615.142605] names, then host name confusion attack is possible. Apr 26 10:17:44 192.168.122.209 [65615.281315] [tempesta fw] Configuration processing is completed. Apr 26 10:17:44 192.168.122.209 [65615.341345] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:17:44 192.168.122.209 [65615.376014] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:17:44 192.168.122.209 [65615.407723] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:17:44 192.168.122.209 [65615.453308] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:17:44 192.168.122.209 [65615.454936] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:17:44 192.168.122.209 [65615.497262] [tempesta fw] Tempesta FW is ready Apr 26 10:17:45 192.168.122.209 [65616.053630] [tdb] Close table 'client0.tdb' Apr 26 10:17:45 192.168.122.209 [65616.236016] [tdb] Close table 'sessions0.tdb' Apr 26 10:17:45 192.168.122.209 [65616.476963] [tdb] Close table 'filter0.tdb' Apr 26 10:17:45 192.168.122.209 [65616.477427] [tempesta fw] modules are stopped Apr 26 10:17:46 192.168.122.209 [65616.706040] [tempesta fw] exiting... Apr 26 10:17:46 192.168.122.209 [65616.839253] [tdb] Shutdown Tempesta DB Apr 26 10:17:46 192.168.122.209 [65617.054274] End test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_expect Apr 26 10:17:46 192.168.122.209 [65617.066375] Start test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_from Apr 26 10:17:47 192.168.122.209 [65618.105273] [tdb] Start Tempesta DB Apr 26 10:17:47 192.168.122.209 [65618.237226] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:17:48 192.168.122.209 [65618.938647] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65618.938647] Maybe that's fine, but it's worth checking the [65618.938647] config - if there is no relations between the [65618.938647] names, then host name confusion attack is possible. Apr 26 10:17:48 192.168.122.209 [65619.077346] [tempesta fw] Configuration processing is completed. Apr 26 10:17:48 192.168.122.209 [65619.131889] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:17:48 192.168.122.209 [65619.161680] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:17:48 192.168.122.209 [65619.192673] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:17:48 192.168.122.209 [65619.249346] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:17:48 192.168.122.209 [65619.251094] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:17:48 192.168.122.209 [65619.297300] [tempesta fw] Tempesta FW is ready Apr 26 10:17:49 192.168.122.209 [65619.876712] [tdb] Close table 'client0.tdb' Apr 26 10:17:49 192.168.122.209 [65620.068962] [tdb] Close table 'sessions0.tdb' Apr 26 10:17:49 192.168.122.209 [65620.293678] [tdb] Close table 'filter0.tdb' Apr 26 10:17:49 192.168.122.209 [65620.294157] [tempesta fw] modules are stopped Apr 26 10:17:49 192.168.122.209 [65620.464484] [tempesta fw] exiting... Apr 26 10:17:49 192.168.122.209 [65620.568526] [tdb] Shutdown Tempesta DB Apr 26 10:17:50 192.168.122.209 [65620.823015] End test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_from Apr 26 10:17:50 192.168.122.209 [65620.843415] Start test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_if_match Apr 26 10:17:51 192.168.122.209 [65621.900826] [tdb] Start Tempesta DB Apr 26 10:17:51 192.168.122.209 [65622.043914] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:17:52 192.168.122.209 [65622.778618] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65622.778618] Maybe that's fine, but it's worth checking the [65622.778618] config - if there is no relations between the [65622.778618] names, then host name confusion attack is possible. Apr 26 10:17:52 192.168.122.209 [65622.906475] [tempesta fw] Configuration processing is completed. Apr 26 10:17:52 192.168.122.209 [65622.964249] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:17:52 192.168.122.209 [65622.997496] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:17:52 192.168.122.209 [65623.029542] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:17:52 192.168.122.209 [65623.085384] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:17:52 192.168.122.209 [65623.087134] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:17:52 192.168.122.209 [65623.133335] [tempesta fw] Tempesta FW is ready Apr 26 10:17:53 192.168.122.209 [65623.688424] [tdb] Close table 'client0.tdb' Apr 26 10:17:53 192.168.122.209 [65623.883252] [tdb] Close table 'sessions0.tdb' Apr 26 10:17:53 192.168.122.209 [65624.129160] [tdb] Close table 'filter0.tdb' Apr 26 10:17:53 192.168.122.209 [65624.129628] [tempesta fw] modules are stopped Apr 26 10:17:53 192.168.122.209 [65624.333535] [tempesta fw] exiting... Apr 26 10:17:53 192.168.122.209 [65624.439151] [tdb] Shutdown Tempesta DB Apr 26 10:17:54 192.168.122.209 [65624.637845] End test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_if_match Apr 26 10:17:54 192.168.122.209 [65624.653689] Start test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_if_modified_since Apr 26 10:17:55 192.168.122.209 [65625.646322] [tdb] Start Tempesta DB Apr 26 10:17:55 192.168.122.209 [65625.775236] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:17:55 192.168.122.209 [65626.430739] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65626.430739] Maybe that's fine, but it's worth checking the [65626.430739] config - if there is no relations between the [65626.430739] names, then host name confusion attack is possible. Apr 26 10:17:55 192.168.122.209 [65626.573466] [tempesta fw] Configuration processing is completed. Apr 26 10:17:56 192.168.122.209 [65626.635445] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:17:56 192.168.122.209 [65626.670283] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:17:56 192.168.122.209 [65626.701831] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:17:56 192.168.122.209 [65626.745423] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:17:56 192.168.122.209 [65626.747167] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:17:56 192.168.122.209 [65626.789377] [tempesta fw] Tempesta FW is ready Apr 26 10:17:56 192.168.122.209 [65627.383441] [tdb] Close table 'client0.tdb' Apr 26 10:17:56 192.168.122.209 [65627.562883] [tdb] Close table 'sessions0.tdb' Apr 26 10:17:57 192.168.122.209 [65627.794912] [tdb] Close table 'filter0.tdb' Apr 26 10:17:57 192.168.122.209 [65627.795320] [tempesta fw] modules are stopped Apr 26 10:17:57 192.168.122.209 [65628.037945] [tempesta fw] exiting... Apr 26 10:17:57 192.168.122.209 [65628.140587] [tdb] Shutdown Tempesta DB Apr 26 10:17:57 192.168.122.209 [65628.330832] End test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_if_modified_since Apr 26 10:17:57 192.168.122.209 [65628.342870] Start test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_if_range Apr 26 10:17:58 192.168.122.209 [65629.385236] [tdb] Start Tempesta DB Apr 26 10:17:58 192.168.122.209 [65629.531010] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:17:59 192.168.122.209 [65630.278903] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65630.278903] Maybe that's fine, but it's worth checking the [65630.278903] config - if there is no relations between the [65630.278903] names, then host name confusion attack is possible. Apr 26 10:17:59 192.168.122.209 [65630.421507] [tempesta fw] Configuration processing is completed. Apr 26 10:17:59 192.168.122.209 [65630.501092] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:17:59 192.168.122.209 [65630.536192] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:17:59 192.168.122.209 [65630.568019] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:17:59 192.168.122.209 [65630.614800] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:17:59 192.168.122.209 [65630.616542] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:18:00 192.168.122.209 [65630.665441] [tempesta fw] Tempesta FW is ready Apr 26 10:18:00 192.168.122.209 [65631.229769] [tdb] Close table 'client0.tdb' Apr 26 10:18:00 192.168.122.209 [65631.415129] [tdb] Close table 'sessions0.tdb' Apr 26 10:18:01 192.168.122.209 [65631.653208] [tdb] Close table 'filter0.tdb' Apr 26 10:18:01 192.168.122.209 [65631.653647] [tempesta fw] modules are stopped Apr 26 10:18:01 192.168.122.209 [65631.883948] [tempesta fw] exiting... Apr 26 10:18:01 192.168.122.209 [65632.020287] [tdb] Shutdown Tempesta DB Apr 26 10:18:01 192.168.122.209 [65632.227804] End test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_if_range Apr 26 10:18:01 192.168.122.209 [65632.241801] Start test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_if_unmodified_since Apr 26 10:18:02 192.168.122.209 [65633.216738] [tdb] Start Tempesta DB Apr 26 10:18:02 192.168.122.209 [65633.372134] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:18:03 192.168.122.209 [65634.086731] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65634.086731] Maybe that's fine, but it's worth checking the [65634.086731] config - if there is no relations between the [65634.086731] names, then host name confusion attack is possible. Apr 26 10:18:03 192.168.122.209 [65634.233538] [tempesta fw] Configuration processing is completed. Apr 26 10:18:03 192.168.122.209 [65634.285799] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:18:03 192.168.122.209 [65634.315198] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:18:03 192.168.122.209 [65634.343400] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:18:03 192.168.122.209 [65634.389516] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:18:03 192.168.122.209 [65634.391254] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:18:03 192.168.122.209 [65634.429464] [tempesta fw] Tempesta FW is ready Apr 26 10:18:04 192.168.122.209 [65635.005227] [tdb] Close table 'client0.tdb' Apr 26 10:18:04 192.168.122.209 [65635.186207] [tdb] Close table 'sessions0.tdb' Apr 26 10:18:04 192.168.122.209 [65635.403971] [tdb] Close table 'filter0.tdb' Apr 26 10:18:04 192.168.122.209 [65635.404367] [tempesta fw] modules are stopped Apr 26 10:18:04 192.168.122.209 [65635.628929] [tempesta fw] exiting... Apr 26 10:18:05 192.168.122.209 [65635.747997] [tdb] Shutdown Tempesta DB Apr 26 10:18:05 192.168.122.209 [65635.948478] End test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_if_unmodified_since Apr 26 10:18:05 192.168.122.209 [65635.957752] Start test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_last_modified Apr 26 10:18:06 192.168.122.209 [65636.994464] [tdb] Start Tempesta DB Apr 26 10:18:06 192.168.122.209 [65637.129715] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:18:07 192.168.122.209 [65637.830963] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65637.830963] Maybe that's fine, but it's worth checking the [65637.830963] config - if there is no relations between the [65637.830963] names, then host name confusion attack is possible. Apr 26 10:18:07 192.168.122.209 [65637.965571] [tempesta fw] Configuration processing is completed. Apr 26 10:18:07 192.168.122.209 [65638.028765] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:18:07 192.168.122.209 [65638.059070] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:18:07 192.168.122.209 [65638.088844] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:18:07 192.168.122.209 [65638.133567] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:18:07 192.168.122.209 [65638.134918] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:18:07 192.168.122.209 [65638.173512] [tempesta fw] Tempesta FW is ready Apr 26 10:18:08 192.168.122.209 [65638.749098] [tdb] Close table 'client0.tdb' Apr 26 10:18:08 192.168.122.209 [65638.936991] [tdb] Close table 'sessions0.tdb' Apr 26 10:18:08 192.168.122.209 [65639.160415] [tdb] Close table 'filter0.tdb' Apr 26 10:18:08 192.168.122.209 [65639.160813] [tempesta fw] modules are stopped Apr 26 10:18:08 192.168.122.209 [65639.362449] [tempesta fw] exiting... Apr 26 10:18:08 192.168.122.209 [65639.470316] [tdb] Shutdown Tempesta DB Apr 26 10:18:09 192.168.122.209 [65639.677449] End test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_last_modified Apr 26 10:18:09 192.168.122.209 [65639.692692] Start test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_max_forwards Apr 26 10:18:10 192.168.122.209 [65640.731627] [tdb] Start Tempesta DB Apr 26 10:18:10 192.168.122.209 [65640.891149] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:18:11 192.168.122.209 [65641.647136] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65641.647136] Maybe that's fine, but it's worth checking the [65641.647136] config - if there is no relations between the [65641.647136] names, then host name confusion attack is possible. Apr 26 10:18:11 192.168.122.209 [65641.773662] [tempesta fw] Configuration processing is completed. Apr 26 10:18:11 192.168.122.209 [65641.836091] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:18:11 192.168.122.209 [65641.869841] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:18:11 192.168.122.209 [65641.902203] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:18:11 192.168.122.209 [65641.965620] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:18:11 192.168.122.209 [65641.967114] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:18:11 192.168.122.209 [65642.005578] [tempesta fw] Tempesta FW is ready Apr 26 10:18:11 192.168.122.209 [65642.576466] [tdb] Close table 'client0.tdb' Apr 26 10:18:12 192.168.122.209 [65642.769078] [tdb] Close table 'sessions0.tdb' Apr 26 10:18:12 192.168.122.209 [65643.021676] [tdb] Close table 'filter0.tdb' Apr 26 10:18:12 192.168.122.209 [65643.022109] [tempesta fw] modules are stopped Apr 26 10:18:12 192.168.122.209 [65643.237908] [tempesta fw] exiting... Apr 26 10:18:12 192.168.122.209 [65643.354247] [tdb] Shutdown Tempesta DB Apr 26 10:18:12 192.168.122.209 [65643.548414] End test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_max_forwards Apr 26 10:18:12 192.168.122.209 [65643.563741] Start test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_pragma Apr 26 10:18:13 192.168.122.209 [65644.604188] [tdb] Start Tempesta DB Apr 26 10:18:14 192.168.122.209 [65644.743118] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:18:14 192.168.122.209 [65645.486933] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65645.486933] Maybe that's fine, but it's worth checking the [65645.486933] config - if there is no relations between the [65645.486933] names, then host name confusion attack is possible. Apr 26 10:18:14 192.168.122.209 [65645.625709] [tempesta fw] Configuration processing is completed. Apr 26 10:18:15 192.168.122.209 [65645.682161] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:18:15 192.168.122.209 [65645.711273] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:18:15 192.168.122.209 [65645.739795] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:18:15 192.168.122.209 [65645.797578] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:18:15 192.168.122.209 [65645.799294] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:18:15 192.168.122.209 [65645.853564] [tempesta fw] Tempesta FW is ready Apr 26 10:18:15 192.168.122.209 [65646.414499] [tdb] Close table 'client0.tdb' Apr 26 10:18:15 192.168.122.209 [65646.613311] [tdb] Close table 'sessions0.tdb' Apr 26 10:18:16 192.168.122.209 [65646.840840] [tdb] Close table 'filter0.tdb' Apr 26 10:18:16 192.168.122.209 [65646.841279] [tempesta fw] modules are stopped Apr 26 10:18:16 192.168.122.209 [65647.050910] [tempesta fw] exiting... Apr 26 10:18:16 192.168.122.209 [65647.171688] [tdb] Shutdown Tempesta DB Apr 26 10:18:16 192.168.122.209 [65647.404063] End test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_pragma Apr 26 10:18:16 192.168.122.209 [65647.420628] Start test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_range Apr 26 10:18:17 192.168.122.209 [65648.475466] [tdb] Start Tempesta DB Apr 26 10:18:18 192.168.122.209 [65648.639243] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:18:18 192.168.122.209 [65649.366960] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65649.366960] Maybe that's fine, but it's worth checking the [65649.366960] config - if there is no relations between the [65649.366960] names, then host name confusion attack is possible. Apr 26 10:18:18 192.168.122.209 [65649.517706] [tempesta fw] Configuration processing is completed. Apr 26 10:18:18 192.168.122.209 [65649.572008] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:18:18 192.168.122.209 [65649.602275] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:18:19 192.168.122.209 [65649.632675] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:18:19 192.168.122.209 [65649.689709] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:18:19 192.168.122.209 [65649.691451] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:18:19 192.168.122.209 [65649.745827] [tempesta fw] Tempesta FW is ready Apr 26 10:18:19 192.168.122.209 [65650.346744] [tdb] Close table 'client0.tdb' Apr 26 10:18:19 192.168.122.209 [65650.533647] [tdb] Close table 'sessions0.tdb' Apr 26 10:18:20 192.168.122.209 [65650.754296] [tdb] Close table 'filter0.tdb' Apr 26 10:18:20 192.168.122.209 [65650.754720] [tempesta fw] modules are stopped Apr 26 10:18:20 192.168.122.209 [65650.958612] [tempesta fw] exiting... Apr 26 10:18:20 192.168.122.209 [65651.119055] [tdb] Shutdown Tempesta DB Apr 26 10:18:20 192.168.122.209 [65651.336109] End test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_range Apr 26 10:18:20 192.168.122.209 [65651.352648] Start test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_referer Apr 26 10:18:21 192.168.122.209 [65652.391593] [tdb] Start Tempesta DB Apr 26 10:18:21 192.168.122.209 [65652.527794] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:18:22 192.168.122.209 [65653.239055] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65653.239055] Maybe that's fine, but it's worth checking the [65653.239055] config - if there is no relations between the [65653.239055] names, then host name confusion attack is possible. Apr 26 10:18:22 192.168.122.209 [65653.373742] [tempesta fw] Configuration processing is completed. Apr 26 10:18:22 192.168.122.209 [65653.433977] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:18:22 192.168.122.209 [65653.468149] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:18:22 192.168.122.209 [65653.499425] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:18:22 192.168.122.209 [65653.541755] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:18:22 192.168.122.209 [65653.543558] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:18:22 192.168.122.209 [65653.577703] [tempesta fw] Tempesta FW is ready Apr 26 10:18:23 192.168.122.209 [65654.148685] [tdb] Close table 'client0.tdb' Apr 26 10:18:23 192.168.122.209 [65654.351760] [tdb] Close table 'sessions0.tdb' Apr 26 10:18:23 192.168.122.209 [65654.574319] [tdb] Close table 'filter0.tdb' Apr 26 10:18:23 192.168.122.209 [65654.574744] [tempesta fw] modules are stopped Apr 26 10:18:24 192.168.122.209 [65654.788984] [tempesta fw] exiting... Apr 26 10:18:24 192.168.122.209 [65654.938650] [tdb] Shutdown Tempesta DB Apr 26 10:18:24 192.168.122.209 [65655.221466] End test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_referer Apr 26 10:18:24 192.168.122.209 [65655.235472] Start test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_te Apr 26 10:18:25 192.168.122.209 [65656.360212] [tdb] Start Tempesta DB Apr 26 10:18:25 192.168.122.209 [65656.504600] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:18:26 192.168.122.209 [65657.203178] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65657.203178] Maybe that's fine, but it's worth checking the [65657.203178] config - if there is no relations between the [65657.203178] names, then host name confusion attack is possible. Apr 26 10:18:26 192.168.122.209 [65657.337871] [tempesta fw] Configuration processing is completed. Apr 26 10:18:26 192.168.122.209 [65657.400220] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:18:26 192.168.122.209 [65657.438025] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:18:26 192.168.122.209 [65657.472279] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:18:26 192.168.122.209 [65657.517741] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:18:26 192.168.122.209 [65657.518952] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:18:26 192.168.122.209 [65657.573754] [tempesta fw] Tempesta FW is ready Apr 26 10:18:27 192.168.122.209 [65658.111774] [tdb] Close table 'client0.tdb' Apr 26 10:18:27 192.168.122.209 [65658.302362] [tdb] Close table 'sessions0.tdb' Apr 26 10:18:27 192.168.122.209 [65658.521658] [tdb] Close table 'filter0.tdb' Apr 26 10:18:27 192.168.122.209 [65658.522089] [tempesta fw] modules are stopped Apr 26 10:18:28 192.168.122.209 [65658.754631] [tempesta fw] exiting... Apr 26 10:18:28 192.168.122.209 [65658.921633] [tdb] Shutdown Tempesta DB Apr 26 10:18:28 192.168.122.209 [65659.127670] End test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_te Apr 26 10:18:28 192.168.122.209 [65659.147726] Start test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_trailer Apr 26 10:18:29 192.168.122.209 [65660.463501] [tdb] Start Tempesta DB Apr 26 10:18:29 192.168.122.209 [65660.602189] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:18:30 192.168.122.209 [65661.291122] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65661.291122] Maybe that's fine, but it's worth checking the [65661.291122] config - if there is no relations between the [65661.291122] names, then host name confusion attack is possible. Apr 26 10:18:30 192.168.122.209 [65661.425864] [tempesta fw] Configuration processing is completed. Apr 26 10:18:30 192.168.122.209 [65661.478135] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:18:30 192.168.122.209 [65661.507236] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:18:30 192.168.122.209 [65661.537387] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:18:30 192.168.122.209 [65661.577863] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:18:30 192.168.122.209 [65661.579663] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:18:30 192.168.122.209 [65661.629856] [tempesta fw] Tempesta FW is ready Apr 26 10:18:31 192.168.122.209 [65662.184177] [tdb] Close table 'client0.tdb' Apr 26 10:18:31 192.168.122.209 [65662.377293] [tdb] Close table 'sessions0.tdb' Apr 26 10:18:32 192.168.122.209 [65662.631954] [tdb] Close table 'filter0.tdb' Apr 26 10:18:32 192.168.122.209 [65662.632384] [tempesta fw] modules are stopped Apr 26 10:18:32 192.168.122.209 [65662.849144] [tempesta fw] exiting... Apr 26 10:18:32 192.168.122.209 [65662.977769] [tdb] Shutdown Tempesta DB Apr 26 10:18:32 192.168.122.209 [65663.174845] End test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_trailer Apr 26 10:18:32 192.168.122.209 [65663.184548] Start test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_upgrade Apr 26 10:18:33 192.168.122.209 [65664.260915] [tdb] Start Tempesta DB Apr 26 10:18:33 192.168.122.209 [65664.396681] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:18:34 192.168.122.209 [65665.147206] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65665.147206] Maybe that's fine, but it's worth checking the [65665.147206] config - if there is no relations between the [65665.147206] names, then host name confusion attack is possible. Apr 26 10:18:34 192.168.122.209 [65665.277937] [tempesta fw] Configuration processing is completed. Apr 26 10:18:34 192.168.122.209 [65665.341044] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:18:34 192.168.122.209 [65665.374737] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:18:34 192.168.122.209 [65665.408954] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:18:34 192.168.122.209 [65665.461950] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:18:34 192.168.122.209 [65665.463722] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:18:34 192.168.122.209 [65665.501855] [tempesta fw] Tempesta FW is ready Apr 26 10:18:35 192.168.122.209 [65666.051640] [tdb] Close table 'client0.tdb' Apr 26 10:18:35 192.168.122.209 [65666.254257] [tdb] Close table 'sessions0.tdb' Apr 26 10:18:35 192.168.122.209 [65666.492302] [tdb] Close table 'filter0.tdb' Apr 26 10:18:35 192.168.122.209 [65666.492694] [tempesta fw] modules are stopped Apr 26 10:18:36 192.168.122.209 [65666.719539] [tempesta fw] exiting... Apr 26 10:18:36 192.168.122.209 [65666.828092] [tdb] Shutdown Tempesta DB Apr 26 10:18:36 192.168.122.209 [65667.036543] End test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_upgrade Apr 26 10:18:36 192.168.122.209 [65667.051648] Start test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_user_agent Apr 26 10:18:37 192.168.122.209 [65668.121657] [tdb] Start Tempesta DB Apr 26 10:18:37 192.168.122.209 [65668.259398] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:18:38 192.168.122.209 [65668.951280] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65668.951280] Maybe that's fine, but it's worth checking the [65668.951280] config - if there is no relations between the [65668.951280] names, then host name confusion attack is possible. Apr 26 10:18:38 192.168.122.209 [65669.094033] [tempesta fw] Configuration processing is completed. Apr 26 10:18:38 192.168.122.209 [65669.166582] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:18:38 192.168.122.209 [65669.201518] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:18:38 192.168.122.209 [65669.234079] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:18:38 192.168.122.209 [65669.281922] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:18:38 192.168.122.209 [65669.283653] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:18:38 192.168.122.209 [65669.329905] [tempesta fw] Tempesta FW is ready Apr 26 10:18:39 192.168.122.209 [65669.908564] [tdb] Close table 'client0.tdb' Apr 26 10:18:39 192.168.122.209 [65670.105270] [tdb] Close table 'sessions0.tdb' Apr 26 10:18:39 192.168.122.209 [65670.342566] [tdb] Close table 'filter0.tdb' Apr 26 10:18:39 192.168.122.209 [65670.342993] [tempesta fw] modules are stopped Apr 26 10:18:39 192.168.122.209 [65670.550268] [tempesta fw] exiting... Apr 26 10:18:40 192.168.122.209 [65670.660315] [tdb] Shutdown Tempesta DB Apr 26 10:18:40 192.168.122.209 [65670.885162] End test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_user_agent Apr 26 10:18:40 192.168.122.209 [65670.901658] Start test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_via Apr 26 10:18:41 192.168.122.209 [65672.038780] [tdb] Start Tempesta DB Apr 26 10:18:41 192.168.122.209 [65672.173015] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:18:42 192.168.122.209 [65672.879298] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65672.879298] Maybe that's fine, but it's worth checking the [65672.879298] config - if there is no relations between the [65672.879298] names, then host name confusion attack is possible. Apr 26 10:18:42 192.168.122.209 [65673.026113] [tempesta fw] Configuration processing is completed. Apr 26 10:18:42 192.168.122.209 [65673.078132] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:18:42 192.168.122.209 [65673.106663] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:18:42 192.168.122.209 [65673.134356] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:18:42 192.168.122.209 [65673.177991] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:18:42 192.168.122.209 [65673.179722] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:18:42 192.168.122.209 [65673.217939] [tempesta fw] Tempesta FW is ready Apr 26 10:18:43 192.168.122.209 [65673.814377] [tdb] Close table 'client0.tdb' Apr 26 10:18:43 192.168.122.209 [65674.012186] [tdb] Close table 'sessions0.tdb' Apr 26 10:18:43 192.168.122.209 [65674.242985] [tdb] Close table 'filter0.tdb' Apr 26 10:18:43 192.168.122.209 [65674.243427] [tempesta fw] modules are stopped Apr 26 10:18:43 192.168.122.209 [65674.451718] [tempesta fw] exiting... Apr 26 10:18:43 192.168.122.209 [65674.605495] [tdb] Shutdown Tempesta DB Apr 26 10:18:44 192.168.122.209 [65674.820329] End test: t_malformed.test_malformed_headers.MalformedRequestsWithoutStrictParsingTest.test_via Apr 26 10:18:44 192.168.122.209 [65674.841837] Start test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_accept_ranges Apr 26 10:18:45 192.168.122.209 [65675.852791] [tdb] Start Tempesta DB Apr 26 10:18:45 192.168.122.209 [65676.008976] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:18:46 192.168.122.209 [65676.691339] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65676.691339] Maybe that's fine, but it's worth checking the [65676.691339] config - if there is no relations between the [65676.691339] names, then host name confusion attack is possible. Apr 26 10:18:46 192.168.122.209 [65676.850434] [tempesta fw] Configuration processing is completed. Apr 26 10:18:46 192.168.122.209 [65676.914536] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:18:46 192.168.122.209 [65676.949353] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:18:46 192.168.122.209 [65676.982103] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:18:46 192.168.122.209 [65677.034054] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:18:46 192.168.122.209 [65677.035802] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:18:46 192.168.122.209 [65677.082001] [tempesta fw] Tempesta FW is ready Apr 26 10:18:47 192.168.122.209 [65677.672214] [tdb] Close table 'client0.tdb' Apr 26 10:18:47 192.168.122.209 [65677.871157] [tdb] Close table 'sessions0.tdb' Apr 26 10:18:47 192.168.122.209 [65678.111037] [tdb] Close table 'filter0.tdb' Apr 26 10:18:47 192.168.122.209 [65678.111477] [tempesta fw] modules are stopped Apr 26 10:18:47 192.168.122.209 [65678.311102] [tempesta fw] exiting... Apr 26 10:18:47 192.168.122.209 [65678.417305] [tdb] Shutdown Tempesta DB Apr 26 10:18:47 192.168.122.209 [65678.628007] End test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_accept_ranges Apr 26 10:18:48 192.168.122.209 [65678.643740] Start test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_allow Apr 26 10:18:49 192.168.122.209 [65679.690943] [tdb] Start Tempesta DB Apr 26 10:18:49 192.168.122.209 [65679.848532] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:18:49 192.168.122.209 [65680.539584] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65680.539584] Maybe that's fine, but it's worth checking the [65680.539584] config - if there is no relations between the [65680.539584] names, then host name confusion attack is possible. Apr 26 10:18:50 192.168.122.209 [65680.694138] [tempesta fw] Configuration processing is completed. Apr 26 10:18:50 192.168.122.209 [65680.757884] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:18:50 192.168.122.209 [65680.795684] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:18:50 192.168.122.209 [65680.832465] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:18:50 192.168.122.209 [65680.882116] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:18:50 192.168.122.209 [65680.883894] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:18:50 192.168.122.209 [65680.922061] [tempesta fw] Tempesta FW is ready Apr 26 10:18:50 192.168.122.209 [65681.508250] [tdb] Close table 'client0.tdb' Apr 26 10:18:51 192.168.122.209 [65681.684246] [tdb] Close table 'sessions0.tdb' Apr 26 10:18:51 192.168.122.209 [65681.918686] [tdb] Close table 'filter0.tdb' Apr 26 10:18:51 192.168.122.209 [65681.919123] [tempesta fw] modules are stopped Apr 26 10:18:51 192.168.122.209 [65682.120914] [tempesta fw] exiting... Apr 26 10:18:51 192.168.122.209 [65682.230547] [tdb] Shutdown Tempesta DB Apr 26 10:18:51 192.168.122.209 [65682.431582] End test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_allow Apr 26 10:18:51 192.168.122.209 [65682.443110] Start test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_connection Apr 26 10:18:52 192.168.122.209 [65683.501869] [tdb] Start Tempesta DB Apr 26 10:18:53 192.168.122.209 [65683.659008] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:18:53 192.168.122.209 [65684.379583] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65684.379583] Maybe that's fine, but it's worth checking the [65684.379583] config - if there is no relations between the [65684.379583] names, then host name confusion attack is possible. Apr 26 10:18:53 192.168.122.209 [65684.558240] [tempesta fw] Configuration processing is completed. Apr 26 10:18:54 192.168.122.209 [65684.651476] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:18:54 192.168.122.209 [65684.689655] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:18:54 192.168.122.209 [65684.723892] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:18:54 192.168.122.209 [65684.758131] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:18:54 192.168.122.209 [65684.759871] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:18:54 192.168.122.209 [65684.798145] [tempesta fw] Tempesta FW is ready Apr 26 10:18:54 192.168.122.209 [65685.425501] [tdb] Close table 'client0.tdb' Apr 26 10:18:54 192.168.122.209 [65685.613766] [tdb] Close table 'sessions0.tdb' Apr 26 10:18:55 192.168.122.209 [65685.844839] [tdb] Close table 'filter0.tdb' Apr 26 10:18:55 192.168.122.209 [65685.845255] [tempesta fw] modules are stopped Apr 26 10:18:55 192.168.122.209 [65686.105491] [tempesta fw] exiting... Apr 26 10:18:55 192.168.122.209 [65686.244293] [tdb] Shutdown Tempesta DB Apr 26 10:18:55 192.168.122.209 [65686.453595] End test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_connection Apr 26 10:18:55 192.168.122.209 [65686.465181] Start test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_content_encoding Apr 26 10:18:56 192.168.122.209 [65687.544324] [tdb] Start Tempesta DB Apr 26 10:18:57 192.168.122.209 [65687.693818] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:18:57 192.168.122.209 [65688.463530] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65688.463530] Maybe that's fine, but it's worth checking the [65688.463530] config - if there is no relations between the [65688.463530] names, then host name confusion attack is possible. Apr 26 10:18:57 192.168.122.209 [65688.614148] [tempesta fw] Configuration processing is completed. Apr 26 10:18:58 192.168.122.209 [65688.675011] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:18:58 192.168.122.209 [65688.709099] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:18:58 192.168.122.209 [65688.740560] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:18:58 192.168.122.209 [65688.790161] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:18:58 192.168.122.209 [65688.791940] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:18:58 192.168.122.209 [65688.830131] [tempesta fw] Tempesta FW is ready Apr 26 10:18:58 192.168.122.209 [65689.394015] [tdb] Close table 'client0.tdb' Apr 26 10:18:58 192.168.122.209 [65689.593206] [tdb] Close table 'sessions0.tdb' Apr 26 10:18:59 192.168.122.209 [65689.844967] [tdb] Close table 'filter0.tdb' Apr 26 10:18:59 192.168.122.209 [65689.845398] [tempesta fw] modules are stopped Apr 26 10:18:59 192.168.122.209 [65690.047938] [tempesta fw] exiting... Apr 26 10:18:59 192.168.122.209 [65690.190752] [tdb] Shutdown Tempesta DB Apr 26 10:18:59 192.168.122.209 [65690.388202] End test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_content_encoding Apr 26 10:18:59 192.168.122.209 [65690.402813] Start test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_content_language Apr 26 10:19:00 192.168.122.209 [65691.484062] [tdb] Start Tempesta DB Apr 26 10:19:01 192.168.122.209 [65691.638788] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:19:01 192.168.122.209 [65692.339744] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65692.339744] Maybe that's fine, but it's worth checking the [65692.339744] config - if there is no relations between the [65692.339744] names, then host name confusion attack is possible. Apr 26 10:19:01 192.168.122.209 [65692.498572] [tempesta fw] Configuration processing is completed. Apr 26 10:19:01 192.168.122.209 [65692.560505] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:19:01 192.168.122.209 [65692.595544] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:19:01 192.168.122.209 [65692.628103] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:19:02 192.168.122.209 [65692.690243] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:19:02 192.168.122.209 [65692.691993] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:19:02 192.168.122.209 [65692.730205] [tempesta fw] Tempesta FW is ready Apr 26 10:19:02 192.168.122.209 [65693.258176] [tdb] Close table 'client0.tdb' Apr 26 10:19:02 192.168.122.209 [65693.449286] [tdb] Close table 'sessions0.tdb' Apr 26 10:19:03 192.168.122.209 [65693.670320] [tdb] Close table 'filter0.tdb' Apr 26 10:19:03 192.168.122.209 [65693.670735] [tempesta fw] modules are stopped Apr 26 10:19:03 192.168.122.209 [65693.872697] [tempesta fw] exiting... Apr 26 10:19:03 192.168.122.209 [65694.024388] [tdb] Shutdown Tempesta DB Apr 26 10:19:03 192.168.122.209 [65694.265185] End test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_content_language Apr 26 10:19:03 192.168.122.209 [65694.273548] Start test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_content_location Apr 26 10:19:04 192.168.122.209 [65695.346769] [tdb] Start Tempesta DB Apr 26 10:19:04 192.168.122.209 [65695.497491] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:19:05 192.168.122.209 [65696.191388] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65696.191388] Maybe that's fine, but it's worth checking the [65696.191388] config - if there is no relations between the [65696.191388] names, then host name confusion attack is possible. Apr 26 10:19:05 192.168.122.209 [65696.338338] [tempesta fw] Configuration processing is completed. Apr 26 10:19:05 192.168.122.209 [65696.397076] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:19:05 192.168.122.209 [65696.430881] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:19:05 192.168.122.209 [65696.461728] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:19:05 192.168.122.209 [65696.510319] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:19:05 192.168.122.209 [65696.512018] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:19:05 192.168.122.209 [65696.558227] [tempesta fw] Tempesta FW is ready Apr 26 10:19:06 192.168.122.209 [65697.110856] [tdb] Close table 'client0.tdb' Apr 26 10:19:06 192.168.122.209 [65697.316185] [tdb] Close table 'sessions0.tdb' Apr 26 10:19:06 192.168.122.209 [65697.555448] [tdb] Close table 'filter0.tdb' Apr 26 10:19:06 192.168.122.209 [65697.555865] [tempesta fw] modules are stopped Apr 26 10:19:07 192.168.122.209 [65697.786790] [tempesta fw] exiting... Apr 26 10:19:07 192.168.122.209 [65697.923156] [tdb] Shutdown Tempesta DB Apr 26 10:19:07 192.168.122.209 [65698.157073] End test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_content_location Apr 26 10:19:07 192.168.122.209 [65698.167343] Start test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_content_range Apr 26 10:19:08 192.168.122.209 [65699.278917] [tdb] Start Tempesta DB Apr 26 10:19:08 192.168.122.209 [65699.421339] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:19:09 192.168.122.209 [65700.159811] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65700.159811] Maybe that's fine, but it's worth checking the [65700.159811] config - if there is no relations between the [65700.159811] names, then host name confusion attack is possible. Apr 26 10:19:09 192.168.122.209 [65700.314375] [tempesta fw] Configuration processing is completed. Apr 26 10:19:09 192.168.122.209 [65700.373854] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:19:09 192.168.122.209 [65700.406420] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:19:09 192.168.122.209 [65700.434740] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:19:09 192.168.122.209 [65700.494412] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:19:09 192.168.122.209 [65700.496315] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:19:09 192.168.122.209 [65700.534269] [tempesta fw] Tempesta FW is ready Apr 26 10:19:10 192.168.122.209 [65701.078681] [tdb] Close table 'client0.tdb' Apr 26 10:19:10 192.168.122.209 [65701.274699] [tdb] Close table 'sessions0.tdb' Apr 26 10:19:10 192.168.122.209 [65701.508255] [tdb] Close table 'filter0.tdb' Apr 26 10:19:10 192.168.122.209 [65701.508669] [tempesta fw] modules are stopped Apr 26 10:19:11 192.168.122.209 [65701.698694] [tempesta fw] exiting... Apr 26 10:19:11 192.168.122.209 [65701.821700] [tdb] Shutdown Tempesta DB Apr 26 10:19:11 192.168.122.209 [65702.022652] End test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_content_range Apr 26 10:19:11 192.168.122.209 [65702.035515] Start test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_content_type Apr 26 10:19:12 192.168.122.209 [65703.107514] [tdb] Start Tempesta DB Apr 26 10:19:12 192.168.122.209 [65703.243665] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:19:13 192.168.122.209 [65703.971707] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65703.971707] Maybe that's fine, but it's worth checking the [65703.971707] config - if there is no relations between the [65703.971707] names, then host name confusion attack is possible. Apr 26 10:19:13 192.168.122.209 [65704.142646] [tempesta fw] Configuration processing is completed. Apr 26 10:19:13 192.168.122.209 [65704.211037] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:19:13 192.168.122.209 [65704.247080] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:19:13 192.168.122.209 [65704.277620] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:19:13 192.168.122.209 [65704.326375] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:19:13 192.168.122.209 [65704.328129] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:19:13 192.168.122.209 [65704.370327] [tempesta fw] Tempesta FW is ready Apr 26 10:19:14 192.168.122.209 [65704.965128] [tdb] Close table 'client0.tdb' Apr 26 10:19:14 192.168.122.209 [65705.154555] [tdb] Close table 'sessions0.tdb' Apr 26 10:19:14 192.168.122.209 [65705.389121] [tdb] Close table 'filter0.tdb' Apr 26 10:19:14 192.168.122.209 [65705.389549] [tempesta fw] modules are stopped Apr 26 10:19:14 192.168.122.209 [65705.566777] [tempesta fw] exiting... Apr 26 10:19:15 192.168.122.209 [65705.699425] [tdb] Shutdown Tempesta DB Apr 26 10:19:15 192.168.122.209 [65705.892830] End test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_content_type Apr 26 10:19:15 192.168.122.209 [65705.904151] Start test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_date Apr 26 10:19:16 192.168.122.209 [65706.985187] [tdb] Start Tempesta DB Apr 26 10:19:16 192.168.122.209 [65707.126128] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:19:17 192.168.122.209 [65707.830972] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65707.830972] Maybe that's fine, but it's worth checking the [65707.830972] config - if there is no relations between the [65707.830972] names, then host name confusion attack is possible. Apr 26 10:19:17 192.168.122.209 [65707.970431] [tempesta fw] Configuration processing is completed. Apr 26 10:19:17 192.168.122.209 [65708.053247] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:19:17 192.168.122.209 [65708.093634] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:19:17 192.168.122.209 [65708.131249] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:19:17 192.168.122.209 [65708.166417] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:19:17 192.168.122.209 [65708.168139] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:19:17 192.168.122.209 [65708.210377] [tempesta fw] Tempesta FW is ready Apr 26 10:19:18 192.168.122.209 [65708.760421] [tdb] Close table 'client0.tdb' Apr 26 10:19:18 192.168.122.209 [65708.977178] [tdb] Close table 'sessions0.tdb' Apr 26 10:19:18 192.168.122.209 [65709.219845] [tdb] Close table 'filter0.tdb' Apr 26 10:19:18 192.168.122.209 [65709.220269] [tempesta fw] modules are stopped Apr 26 10:19:18 192.168.122.209 [65709.421083] [tempesta fw] exiting... Apr 26 10:19:18 192.168.122.209 [65709.551578] [tdb] Shutdown Tempesta DB Apr 26 10:19:19 192.168.122.209 [65709.794624] End test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_date Apr 26 10:19:19 192.168.122.209 [65709.804907] Start test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_expires Apr 26 10:19:20 192.168.122.209 [65710.848008] [tdb] Start Tempesta DB Apr 26 10:19:20 192.168.122.209 [65710.978470] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:19:21 192.168.122.209 [65711.675748] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65711.675748] Maybe that's fine, but it's worth checking the [65711.675748] config - if there is no relations between the [65711.675748] names, then host name confusion attack is possible. Apr 26 10:19:21 192.168.122.209 [65711.826494] [tempesta fw] Configuration processing is completed. Apr 26 10:19:21 192.168.122.209 [65711.880019] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:19:21 192.168.122.209 [65711.910141] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:19:21 192.168.122.209 [65711.939633] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:19:21 192.168.122.209 [65711.974466] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:19:21 192.168.122.209 [65711.976195] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:19:21 192.168.122.209 [65712.022446] [tempesta fw] Tempesta FW is ready Apr 26 10:19:21 192.168.122.209 [65712.613042] [tdb] Close table 'client0.tdb' Apr 26 10:19:22 192.168.122.209 [65712.825281] [tdb] Close table 'sessions0.tdb' Apr 26 10:19:22 192.168.122.209 [65713.061470] [tdb] Close table 'filter0.tdb' Apr 26 10:19:22 192.168.122.209 [65713.061886] [tempesta fw] modules are stopped Apr 26 10:19:22 192.168.122.209 [65713.275185] [tempesta fw] exiting... Apr 26 10:19:22 192.168.122.209 [65713.415328] [tdb] Shutdown Tempesta DB Apr 26 10:19:22 192.168.122.209 [65713.609416] End test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_expires Apr 26 10:19:22 192.168.122.209 [65713.619860] Start test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_last_modified Apr 26 10:19:24 192.168.122.209 [65714.674580] [tdb] Start Tempesta DB Apr 26 10:19:24 192.168.122.209 [65714.840298] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:19:24 192.168.122.209 [65715.539839] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65715.539839] Maybe that's fine, but it's worth checking the [65715.539839] config - if there is no relations between the [65715.539839] names, then host name confusion attack is possible. Apr 26 10:19:25 192.168.122.209 [65715.690968] [tempesta fw] Configuration processing is completed. Apr 26 10:19:25 192.168.122.209 [65715.743125] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:19:25 192.168.122.209 [65715.772526] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:19:25 192.168.122.209 [65715.801506] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:19:25 192.168.122.209 [65715.850549] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:19:25 192.168.122.209 [65715.852312] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:19:25 192.168.122.209 [65715.890481] [tempesta fw] Tempesta FW is ready Apr 26 10:19:25 192.168.122.209 [65716.431464] [tdb] Close table 'client0.tdb' Apr 26 10:19:25 192.168.122.209 [65716.619890] [tdb] Close table 'sessions0.tdb' Apr 26 10:19:26 192.168.122.209 [65716.840822] [tdb] Close table 'filter0.tdb' Apr 26 10:19:26 192.168.122.209 [65716.841239] [tempesta fw] modules are stopped Apr 26 10:19:26 192.168.122.209 [65717.066607] [tempesta fw] exiting... Apr 26 10:19:26 192.168.122.209 [65717.203245] [tdb] Shutdown Tempesta DB Apr 26 10:19:26 192.168.122.209 [65717.438093] End test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_last_modified Apr 26 10:19:26 192.168.122.209 [65717.450782] Start test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_location Apr 26 10:19:27 192.168.122.209 [65718.472235] [tdb] Start Tempesta DB Apr 26 10:19:27 192.168.122.209 [65718.620394] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:19:28 192.168.122.209 [65719.340155] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65719.340155] Maybe that's fine, but it's worth checking the [65719.340155] config - if there is no relations between the [65719.340155] names, then host name confusion attack is possible. Apr 26 10:19:28 192.168.122.209 [65719.510624] [tempesta fw] Configuration processing is completed. Apr 26 10:19:28 192.168.122.209 [65719.566281] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:19:28 192.168.122.209 [65719.597148] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:19:28 192.168.122.209 [65719.625802] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:19:29 192.168.122.209 [65719.674562] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:19:29 192.168.122.209 [65719.676281] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:19:29 192.168.122.209 [65719.714518] [tempesta fw] Tempesta FW is ready Apr 26 10:19:29 192.168.122.209 [65720.293876] [tdb] Close table 'client0.tdb' Apr 26 10:19:29 192.168.122.209 [65720.479631] [tdb] Close table 'sessions0.tdb' Apr 26 10:19:30 192.168.122.209 [65720.712190] [tdb] Close table 'filter0.tdb' Apr 26 10:19:30 192.168.122.209 [65720.712595] [tempesta fw] modules are stopped Apr 26 10:19:30 192.168.122.209 [65720.909834] [tempesta fw] exiting... Apr 26 10:19:30 192.168.122.209 [65721.033473] [tdb] Shutdown Tempesta DB Apr 26 10:19:30 192.168.122.209 [65721.251219] End test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_location Apr 26 10:19:30 192.168.122.209 [65721.259333] Start test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_retry_after Apr 26 10:19:31 192.168.122.209 [65722.240415] [tdb] Start Tempesta DB Apr 26 10:19:31 192.168.122.209 [65722.388615] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:19:32 192.168.122.209 [65723.079884] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65723.079884] Maybe that's fine, but it's worth checking the [65723.079884] config - if there is no relations between the [65723.079884] names, then host name confusion attack is possible. Apr 26 10:19:32 192.168.122.209 [65723.230643] [tempesta fw] Configuration processing is completed. Apr 26 10:19:32 192.168.122.209 [65723.289211] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:19:32 192.168.122.209 [65723.324236] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:19:32 192.168.122.209 [65723.354486] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:19:32 192.168.122.209 [65723.398608] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:19:32 192.168.122.209 [65723.400352] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:19:32 192.168.122.209 [65723.446573] [tempesta fw] Tempesta FW is ready Apr 26 10:19:33 192.168.122.209 [65724.023146] [tdb] Close table 'client0.tdb' Apr 26 10:19:33 192.168.122.209 [65724.197420] [tdb] Close table 'sessions0.tdb' Apr 26 10:19:33 192.168.122.209 [65724.447955] [tdb] Close table 'filter0.tdb' Apr 26 10:19:33 192.168.122.209 [65724.448377] [tempesta fw] modules are stopped Apr 26 10:19:34 192.168.122.209 [65724.642825] [tempesta fw] exiting... Apr 26 10:19:34 192.168.122.209 [65724.779114] [tdb] Shutdown Tempesta DB Apr 26 10:19:34 192.168.122.209 [65725.001877] End test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_retry_after Apr 26 10:19:34 192.168.122.209 [65725.014671] Start test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_server Apr 26 10:19:35 192.168.122.209 [65726.021315] [tdb] Start Tempesta DB Apr 26 10:19:35 192.168.122.209 [65726.160649] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:19:36 192.168.122.209 [65726.851965] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65726.851965] Maybe that's fine, but it's worth checking the [65726.851965] config - if there is no relations between the [65726.851965] names, then host name confusion attack is possible. Apr 26 10:19:36 192.168.122.209 [65727.034663] [tempesta fw] Configuration processing is completed. Apr 26 10:19:36 192.168.122.209 [65727.086765] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:19:36 192.168.122.209 [65727.115342] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:19:36 192.168.122.209 [65727.144253] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:19:36 192.168.122.209 [65727.190657] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:19:36 192.168.122.209 [65727.192381] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:19:36 192.168.122.209 [65727.238628] [tempesta fw] Tempesta FW is ready Apr 26 10:19:37 192.168.122.209 [65727.796877] [tdb] Close table 'client0.tdb' Apr 26 10:19:37 192.168.122.209 [65727.986030] [tdb] Close table 'sessions0.tdb' Apr 26 10:19:37 192.168.122.209 [65728.220247] [tdb] Close table 'filter0.tdb' Apr 26 10:19:37 192.168.122.209 [65728.220674] [tempesta fw] modules are stopped Apr 26 10:19:37 192.168.122.209 [65728.427372] [tempesta fw] exiting... Apr 26 10:19:37 192.168.122.209 [65728.539748] [tdb] Shutdown Tempesta DB Apr 26 10:19:38 192.168.122.209 [65728.754965] End test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_server Apr 26 10:19:38 192.168.122.209 [65728.778676] Start test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_vary Apr 26 10:19:39 192.168.122.209 [65729.826943] [tdb] Start Tempesta DB Apr 26 10:19:39 192.168.122.209 [65729.958359] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:19:40 192.168.122.209 [65730.681063] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65730.681063] Maybe that's fine, but it's worth checking the [65730.681063] config - if there is no relations between the [65730.681063] names, then host name confusion attack is possible. Apr 26 10:19:40 192.168.122.209 [65730.830763] [tempesta fw] Configuration processing is completed. Apr 26 10:19:40 192.168.122.209 [65730.903027] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:19:40 192.168.122.209 [65730.937618] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:19:40 192.168.122.209 [65730.969606] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:19:40 192.168.122.209 [65731.026633] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:19:40 192.168.122.209 [65731.028378] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:19:40 192.168.122.209 [65731.068065] [tempesta fw] Tempesta FW is ready Apr 26 10:19:40 192.168.122.209 [65731.621280] [tdb] Close table 'client0.tdb' Apr 26 10:19:41 192.168.122.209 [65731.835025] [tdb] Close table 'sessions0.tdb' Apr 26 10:19:41 192.168.122.209 [65732.061983] [tdb] Close table 'filter0.tdb' Apr 26 10:19:41 192.168.122.209 [65732.062401] [tempesta fw] modules are stopped Apr 26 10:19:41 192.168.122.209 [65732.263327] [tempesta fw] exiting... Apr 26 10:19:41 192.168.122.209 [65732.359171] [tdb] Shutdown Tempesta DB Apr 26 10:19:41 192.168.122.209 [65732.544261] End test: t_malformed.test_malformed_headers.MalformedResponseWithoutStrictParsingTest.test_vary Apr 26 10:19:41 192.168.122.209 [65732.558287] Start test: t_malformed.test_malformed_headers.MalformedResponsesTest.test_age Apr 26 10:19:42 192.168.122.209 [65733.568347] [tdb] Start Tempesta DB Apr 26 10:19:43 192.168.122.209 [65733.706836] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:19:43 192.168.122.209 [65734.444064] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65734.444064] Maybe that's fine, but it's worth checking the [65734.444064] config - if there is no relations between the [65734.444064] names, then host name confusion attack is possible. Apr 26 10:19:43 192.168.122.209 [65734.598762] [tempesta fw] Configuration processing is completed. Apr 26 10:19:44 192.168.122.209 [65734.650446] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:19:44 192.168.122.209 [65734.679262] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:19:44 192.168.122.209 [65734.707662] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:19:44 192.168.122.209 [65734.758781] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:19:44 192.168.122.209 [65734.760537] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:19:44 192.168.122.209 [65734.810705] [tempesta fw] Tempesta FW is ready Apr 26 10:19:44 192.168.122.209 [65734.957933] [tempesta fw] Warning: Parser error: state=Resp_HdrAgeV input(-0)=0x69('i') data_len=1 off=0 Apr 26 10:19:44 192.168.122.209 [65734.959533] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 10:19:44 192.168.122.209 [65735.377420] [tdb] Close table 'client0.tdb' Apr 26 10:19:44 192.168.122.209 [65735.570689] [tdb] Close table 'sessions0.tdb' Apr 26 10:19:45 192.168.122.209 [65735.817327] [tdb] Close table 'filter0.tdb' Apr 26 10:19:45 192.168.122.209 [65735.817739] [tempesta fw] modules are stopped Apr 26 10:19:45 192.168.122.209 [65736.034485] [tempesta fw] exiting... Apr 26 10:19:45 192.168.122.209 [65736.194173] [tdb] Shutdown Tempesta DB Apr 26 10:19:45 192.168.122.209 [65736.406914] End test: t_malformed.test_malformed_headers.MalformedResponsesTest.test_age Apr 26 10:19:45 192.168.122.209 [65736.417609] Start test: t_malformed.test_malformed_headers.MalformedResponsesTest.test_cache_control1 Apr 26 10:19:46 192.168.122.209 [65737.484913] [tdb] Start Tempesta DB Apr 26 10:19:46 192.168.122.209 [65737.627061] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:19:47 192.168.122.209 [65738.328034] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65738.328034] Maybe that's fine, but it's worth checking the [65738.328034] config - if there is no relations between the [65738.328034] names, then host name confusion attack is possible. Apr 26 10:19:47 192.168.122.209 [65738.478847] [tempesta fw] Configuration processing is completed. Apr 26 10:19:47 192.168.122.209 [65738.539425] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:19:47 192.168.122.209 [65738.572606] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:19:47 192.168.122.209 [65738.604259] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:19:48 192.168.122.209 [65738.650832] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:19:48 192.168.122.209 [65738.652560] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:19:48 192.168.122.209 [65738.702772] [tempesta fw] Tempesta FW is ready Apr 26 10:19:48 192.168.122.209 [65738.851415] [tempesta fw] Warning: Parser error: state=Resp_HdrCache_CtrlV input(-0)=0x61('a') data_len=1 off=0 Apr 26 10:19:48 192.168.122.209 [65738.853695] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 10:19:48 192.168.122.209 [65739.236316] [tdb] Close table 'client0.tdb' Apr 26 10:19:48 192.168.122.209 [65739.421889] [tdb] Close table 'sessions0.tdb' Apr 26 10:19:49 192.168.122.209 [65739.638827] [tdb] Close table 'filter0.tdb' Apr 26 10:19:49 192.168.122.209 [65739.639298] [tempesta fw] modules are stopped Apr 26 10:19:49 192.168.122.209 [65739.856883] [tempesta fw] exiting... Apr 26 10:19:49 192.168.122.209 [65739.964473] [tdb] Shutdown Tempesta DB Apr 26 10:19:49 192.168.122.209 [65740.186363] End test: t_malformed.test_malformed_headers.MalformedResponsesTest.test_cache_control1 Apr 26 10:19:49 192.168.122.209 [65740.199882] Start test: t_malformed.test_malformed_headers.MalformedResponsesTest.test_cache_control2 Apr 26 10:19:50 192.168.122.209 [65741.290864] [tdb] Start Tempesta DB Apr 26 10:19:50 192.168.122.209 [65741.429618] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:19:51 192.168.122.209 [65742.117395] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65742.117395] Maybe that's fine, but it's worth checking the [65742.117395] config - if there is no relations between the [65742.117395] names, then host name confusion attack is possible. Apr 26 10:19:51 192.168.122.209 [65742.279043] [tempesta fw] Configuration processing is completed. Apr 26 10:19:51 192.168.122.209 [65742.331299] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:19:51 192.168.122.209 [65742.360093] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:19:51 192.168.122.209 [65742.394968] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:19:51 192.168.122.209 [65742.430835] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:19:51 192.168.122.209 [65742.432559] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:19:51 192.168.122.209 [65742.470786] [tempesta fw] Tempesta FW is ready Apr 26 10:19:51 192.168.122.209 [65742.614449] [tempesta fw] Warning: Parser error: state=Resp_HdrCache_CtrlV input(-0)=0x74('t') data_len=1 off=0 Apr 26 10:19:51 192.168.122.209 [65742.616823] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 10:19:52 192.168.122.209 [65743.057762] [tdb] Close table 'client0.tdb' Apr 26 10:19:52 192.168.122.209 [65743.248443] [tdb] Close table 'sessions0.tdb' Apr 26 10:19:52 192.168.122.209 [65743.469333] [tdb] Close table 'filter0.tdb' Apr 26 10:19:52 192.168.122.209 [65743.469746] [tempesta fw] modules are stopped Apr 26 10:19:53 192.168.122.209 [65743.674793] [tempesta fw] exiting... Apr 26 10:19:53 192.168.122.209 [65743.772984] [tdb] Shutdown Tempesta DB Apr 26 10:19:53 192.168.122.209 [65744.010182] End test: t_malformed.test_malformed_headers.MalformedResponsesTest.test_cache_control2 Apr 26 10:19:53 192.168.122.209 [65744.025104] Start test: t_malformed.test_malformed_headers.MalformedResponsesTest.test_missing_name Apr 26 10:19:54 192.168.122.209 [65745.073594] [tdb] Start Tempesta DB Apr 26 10:19:54 192.168.122.209 [65745.210580] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:19:55 192.168.122.209 [65745.900268] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65745.900268] Maybe that's fine, but it's worth checking the [65745.900268] config - if there is no relations between the [65745.900268] names, then host name confusion attack is possible. Apr 26 10:19:55 192.168.122.209 [65746.066905] [tempesta fw] Configuration processing is completed. Apr 26 10:19:55 192.168.122.209 [65746.124803] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:19:55 192.168.122.209 [65746.158045] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:19:55 192.168.122.209 [65746.193519] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:19:55 192.168.122.209 [65746.250848] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:19:55 192.168.122.209 [65746.252081] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:19:55 192.168.122.209 [65746.322831] [tempesta fw] Tempesta FW is ready Apr 26 10:19:55 192.168.122.209 [65746.463223] [tempesta fw] Warning: Parser error: state=RGen_HdrOtherN input(-0)=0x3a(': i') data_len=3 off=0 Apr 26 10:19:55 192.168.122.209 [65746.464452] [tempesta fw] Warning: response dropped: processing error: 127.0.0.2 Apr 26 10:19:56 192.168.122.209 [65746.909238] [tdb] Close table 'client0.tdb' Apr 26 10:19:56 192.168.122.209 [65747.077342] [tdb] Close table 'sessions0.tdb' Apr 26 10:19:56 192.168.122.209 [65747.314511] [tdb] Close table 'filter0.tdb' Apr 26 10:19:56 192.168.122.209 [65747.315330] [tempesta fw] modules are stopped Apr 26 10:19:56 192.168.122.209 [65747.512236] [tempesta fw] exiting... Apr 26 10:19:56 192.168.122.209 [65747.608443] [tdb] Shutdown Tempesta DB Apr 26 10:19:57 192.168.122.209 [65747.824520] End test: t_malformed.test_malformed_headers.MalformedResponsesTest.test_missing_name Apr 26 10:19:57 192.168.122.209 [65747.844591] Start test: t_malformed.test_malformed_structure.MalformedStructureTest.test_crSPlf Apr 26 10:19:58 192.168.122.209 [65748.917818] [tdb] Start Tempesta DB Apr 26 10:19:58 192.168.122.209 [65749.051410] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:19:59 192.168.122.209 [65749.642968] [tempesta fw] Configuration processing is completed. Apr 26 10:19:59 192.168.122.209 [65749.702262] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:19:59 192.168.122.209 [65749.732408] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:19:59 192.168.122.209 [65749.762758] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:19:59 192.168.122.209 [65749.814854] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:19:59 192.168.122.209 [65749.854891] [tempesta fw] Tempesta FW is ready Apr 26 10:19:59 192.168.122.209 [65749.990116] [tempesta fw] Warning: Parser error: state=RGen_CR input(-0)=0x20(' ') data_len=1 off=0 Apr 26 10:19:59 192.168.122.209 [65750.426972] [tdb] Close table 'client0.tdb' Apr 26 10:19:59 192.168.122.209 [65750.628956] [tdb] Close table 'sessions0.tdb' Apr 26 10:20:00 192.168.122.209 [65750.870525] [tdb] Close table 'filter0.tdb' Apr 26 10:20:00 192.168.122.209 [65750.870967] [tempesta fw] modules are stopped Apr 26 10:20:00 192.168.122.209 [65751.050241] [tempesta fw] exiting... Apr 26 10:20:00 192.168.122.209 [65751.161582] [tdb] Shutdown Tempesta DB Apr 26 10:20:00 192.168.122.209 [65751.407253] End test: t_malformed.test_malformed_structure.MalformedStructureTest.test_crSPlf Apr 26 10:20:00 192.168.122.209 [65751.421893] Start test: t_malformed.test_malformed_structure.MalformedStructureTest.test_lfcr Apr 26 10:20:01 192.168.122.209 [65752.396121] [tdb] Start Tempesta DB Apr 26 10:20:01 192.168.122.209 [65752.529703] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:20:02 192.168.122.209 [65753.143013] [tempesta fw] Configuration processing is completed. Apr 26 10:20:02 192.168.122.209 [65753.200903] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:20:02 192.168.122.209 [65753.234246] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:20:02 192.168.122.209 [65753.265305] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:20:02 192.168.122.209 [65753.318999] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:20:02 192.168.122.209 [65753.370931] [tempesta fw] Tempesta FW is ready Apr 26 10:20:02 192.168.122.209 [65753.508300] [tempesta fw] Warning: Parser error: state=RGen_CRLFCR input(-0)=0x48('H') data_len=1 off=0 Apr 26 10:20:03 192.168.122.209 [65753.929847] [tdb] Close table 'client0.tdb' Apr 26 10:20:03 192.168.122.209 [65754.106607] [tdb] Close table 'sessions0.tdb' Apr 26 10:20:03 192.168.122.209 [65754.364053] [tdb] Close table 'filter0.tdb' Apr 26 10:20:03 192.168.122.209 [65754.364494] [tempesta fw] modules are stopped Apr 26 10:20:03 192.168.122.209 [65754.524377] [tempesta fw] exiting... Apr 26 10:20:03 192.168.122.209 [65754.631644] [tdb] Shutdown Tempesta DB Apr 26 10:20:04 192.168.122.209 [65754.851727] End test: t_malformed.test_malformed_structure.MalformedStructureTest.test_lfcr Apr 26 10:20:04 192.168.122.209 [65754.861909] Start test: t_malformed.test_malformed_structure.MalformedStructureTest.test_space Apr 26 10:20:05 192.168.122.209 [65755.910438] [tdb] Start Tempesta DB Apr 26 10:20:05 192.168.122.209 [65756.061075] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:20:06 192.168.122.209 [65756.639096] [tempesta fw] Configuration processing is completed. Apr 26 10:20:06 192.168.122.209 [65756.701129] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:20:06 192.168.122.209 [65756.739676] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:20:06 192.168.122.209 [65756.770721] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:20:06 192.168.122.209 [65756.831018] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:20:06 192.168.122.209 [65756.878953] [tempesta fw] Tempesta FW is ready Apr 26 10:20:06 192.168.122.209 [65756.993546] [tempesta fw] Warning: Parser error: state=RGen_HdrOtherN input(-0)=0x20(' ') data_len=1 off=0 Apr 26 10:20:06 192.168.122.209 [65757.405365] [tdb] Close table 'client0.tdb' Apr 26 10:20:06 192.168.122.209 [65757.593959] [tdb] Close table 'sessions0.tdb' Apr 26 10:20:07 192.168.122.209 [65757.823907] [tdb] Close table 'filter0.tdb' Apr 26 10:20:07 192.168.122.209 [65757.824337] [tempesta fw] modules are stopped Apr 26 10:20:07 192.168.122.209 [65757.988634] [tempesta fw] exiting... Apr 26 10:20:07 192.168.122.209 [65758.115700] [tdb] Shutdown Tempesta DB Apr 26 10:20:07 192.168.122.209 [65758.319173] End test: t_malformed.test_malformed_structure.MalformedStructureTest.test_space Apr 26 10:20:07 192.168.122.209 [65758.335355] Start test: t_modify_http_headers.test_common_config.TestCachedRespAddHeader.test_add_hdrs_derive_config Apr 26 10:20:08 192.168.122.209 [65759.376619] [tdb] Start Tempesta DB Apr 26 10:20:08 192.168.122.209 [65759.520605] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:20:09 192.168.122.209 [65760.204321] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65760.204321] Maybe that's fine, but it's worth checking the [65760.204321] config - if there is no relations between the [65760.204321] names, then host name confusion attack is possible. Apr 26 10:20:09 192.168.122.209 [65760.363043] [tempesta fw] Configuration processing is completed. Apr 26 10:20:09 192.168.122.209 [65760.416667] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:20:10 192.168.122.209 [65761.185450] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:20:10 192.168.122.209 [65761.239540] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:20:10 192.168.122.209 [65761.289859] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:20:10 192.168.122.209 [65761.355082] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:20:10 192.168.122.209 [65761.356847] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:20:10 192.168.122.209 [65761.395026] [tempesta fw] Tempesta FW is ready Apr 26 10:20:11 192.168.122.209 [65761.991844] [tdb] Close table 'client0.tdb' Apr 26 10:20:11 192.168.122.209 [65762.184159] [tdb] Close table 'sessions0.tdb' Apr 26 10:20:14 192.168.122.209 [65765.467446] [tdb] Close table 'cache0.tdb' Apr 26 10:20:15 192.168.122.209 [65765.688775] [tdb] Close table 'filter0.tdb' Apr 26 10:20:15 192.168.122.209 [65765.689192] [tempesta fw] modules are stopped Apr 26 10:20:15 192.168.122.209 [65765.897247] [tempesta fw] exiting... Apr 26 10:20:15 192.168.122.209 [65766.029704] [tdb] Shutdown Tempesta DB Apr 26 10:20:15 192.168.122.209 [65766.235968] End test: t_modify_http_headers.test_common_config.TestCachedRespAddHeader.test_add_hdrs_derive_config Apr 26 10:20:15 192.168.122.209 [65766.259500] Start test: t_modify_http_headers.test_common_config.TestCachedRespAddHeader.test_add_hdrs_override_config Apr 26 10:20:16 192.168.122.209 [65767.326404] [tdb] Start Tempesta DB Apr 26 10:20:16 192.168.122.209 [65767.466073] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:20:18 192.168.122.209 [65768.972490] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65768.972490] Maybe that's fine, but it's worth checking the [65768.972490] config - if there is no relations between the [65768.972490] names, then host name confusion attack is possible. Apr 26 10:20:18 192.168.122.209 [65769.119127] [tempesta fw] Configuration processing is completed. Apr 26 10:20:18 192.168.122.209 [65769.175462] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:20:18 192.168.122.209 [65769.596544] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:20:18 192.168.122.209 [65769.621524] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:20:19 192.168.122.209 [65769.646768] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:20:19 192.168.122.209 [65769.699182] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:20:19 192.168.122.209 [65769.700920] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:20:19 192.168.122.209 [65769.739136] [tempesta fw] Tempesta FW is ready Apr 26 10:20:19 192.168.122.209 [65770.331926] [tdb] Close table 'client0.tdb' Apr 26 10:20:19 192.168.122.209 [65770.518383] [tdb] Close table 'sessions0.tdb' Apr 26 10:20:23 192.168.122.209 [65773.739112] [tdb] Close table 'cache0.tdb' Apr 26 10:20:23 192.168.122.209 [65773.965366] [tdb] Close table 'filter0.tdb' Apr 26 10:20:23 192.168.122.209 [65773.965791] [tempesta fw] modules are stopped Apr 26 10:20:23 192.168.122.209 [65774.171650] [tempesta fw] exiting... Apr 26 10:20:23 192.168.122.209 [65774.294680] [tdb] Shutdown Tempesta DB Apr 26 10:20:23 192.168.122.209 [65774.499579] End test: t_modify_http_headers.test_common_config.TestCachedRespAddHeader.test_add_hdrs_override_config Apr 26 10:20:23 192.168.122.209 [65774.510410] Start test: t_modify_http_headers.test_common_config.TestCachedRespAddHeader.test_add_some_hdrs Apr 26 10:20:24 192.168.122.209 [65775.594678] [tdb] Start Tempesta DB Apr 26 10:20:25 192.168.122.209 [65775.745501] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:20:26 192.168.122.209 [65777.204579] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65777.204579] Maybe that's fine, but it's worth checking the [65777.204579] config - if there is no relations between the [65777.204579] names, then host name confusion attack is possible. Apr 26 10:20:26 192.168.122.209 [65777.351320] [tempesta fw] Configuration processing is completed. Apr 26 10:20:26 192.168.122.209 [65777.409415] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:20:27 192.168.122.209 [65777.841304] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:20:27 192.168.122.209 [65777.868734] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:20:27 192.168.122.209 [65777.896694] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:20:27 192.168.122.209 [65777.943283] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:20:27 192.168.122.209 [65777.945074] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:20:27 192.168.122.209 [65777.987217] [tempesta fw] Tempesta FW is ready Apr 26 10:20:27 192.168.122.209 [65778.574541] [tdb] Close table 'client0.tdb' Apr 26 10:20:28 192.168.122.209 [65778.762382] [tdb] Close table 'sessions0.tdb' Apr 26 10:20:31 192.168.122.209 [65781.957788] [tdb] Close table 'cache0.tdb' Apr 26 10:20:31 192.168.122.209 [65782.200759] [tdb] Close table 'filter0.tdb' Apr 26 10:20:31 192.168.122.209 [65782.201207] [tempesta fw] modules are stopped Apr 26 10:20:31 192.168.122.209 [65782.414885] [tempesta fw] exiting... Apr 26 10:20:31 192.168.122.209 [65782.546186] [tdb] Shutdown Tempesta DB Apr 26 10:20:32 192.168.122.209 [65782.760961] End test: t_modify_http_headers.test_common_config.TestCachedRespAddHeader.test_add_some_hdrs Apr 26 10:20:32 192.168.122.209 [65782.775609] Start test: t_modify_http_headers.test_common_config.TestCachedRespAddHeader.test_add_some_hdrs_custom_location Apr 26 10:20:33 192.168.122.209 [65783.825881] [tdb] Start Tempesta DB Apr 26 10:20:33 192.168.122.209 [65783.961345] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:20:34 192.168.122.209 [65785.576695] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65785.576695] Maybe that's fine, but it's worth checking the [65785.576695] config - if there is no relations between the [65785.576695] names, then host name confusion attack is possible. Apr 26 10:20:35 192.168.122.209 [65785.727405] [tempesta fw] Configuration processing is completed. Apr 26 10:20:35 192.168.122.209 [65785.790593] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:20:35 192.168.122.209 [65786.275448] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:20:35 192.168.122.209 [65786.305719] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:20:35 192.168.122.209 [65786.336676] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:20:35 192.168.122.209 [65786.383407] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:20:35 192.168.122.209 [65786.385158] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:20:35 192.168.122.209 [65786.423271] [tempesta fw] Tempesta FW is ready Apr 26 10:20:36 192.168.122.209 [65787.044321] [tdb] Close table 'client0.tdb' Apr 26 10:20:36 192.168.122.209 [65787.233866] [tdb] Close table 'sessions0.tdb' Apr 26 10:20:39 192.168.122.209 [65790.449988] [tdb] Close table 'cache0.tdb' Apr 26 10:20:40 192.168.122.209 [65790.673040] [tdb] Close table 'filter0.tdb' Apr 26 10:20:40 192.168.122.209 [65790.673469] [tempesta fw] modules are stopped Apr 26 10:20:40 192.168.122.209 [65790.863284] [tempesta fw] exiting... Apr 26 10:20:40 192.168.122.209 [65791.003882] [tdb] Shutdown Tempesta DB Apr 26 10:20:40 192.168.122.209 [65791.257695] End test: t_modify_http_headers.test_common_config.TestCachedRespAddHeader.test_add_some_hdrs_custom_location Apr 26 10:20:40 192.168.122.209 [65791.270558] Start test: t_modify_http_headers.test_common_config.TestCachedRespSetHeader.test_add_hdrs_derive_config Apr 26 10:20:41 192.168.122.209 [65792.361539] [tdb] Start Tempesta DB Apr 26 10:20:41 192.168.122.209 [65792.508106] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:20:43 192.168.122.209 [65794.028738] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65794.028738] Maybe that's fine, but it's worth checking the [65794.028738] config - if there is no relations between the [65794.028738] names, then host name confusion attack is possible. Apr 26 10:20:43 192.168.122.209 [65794.187520] [tempesta fw] Configuration processing is completed. Apr 26 10:20:43 192.168.122.209 [65794.245862] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:20:44 192.168.122.209 [65794.679514] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:20:44 192.168.122.209 [65794.705841] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:20:44 192.168.122.209 [65794.731891] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:20:44 192.168.122.209 [65794.783499] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:20:44 192.168.122.209 [65794.785248] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:20:44 192.168.122.209 [65794.823433] [tempesta fw] Tempesta FW is ready Apr 26 10:20:44 192.168.122.209 [65795.438617] [tdb] Close table 'client0.tdb' Apr 26 10:20:44 192.168.122.209 [65795.625661] [tdb] Close table 'sessions0.tdb' Apr 26 10:20:48 192.168.122.209 [65798.838169] [tdb] Close table 'cache0.tdb' Apr 26 10:20:48 192.168.122.209 [65799.065490] [tdb] Close table 'filter0.tdb' Apr 26 10:20:48 192.168.122.209 [65799.065900] [tempesta fw] modules are stopped Apr 26 10:20:48 192.168.122.209 [65799.250928] [tempesta fw] exiting... Apr 26 10:20:48 192.168.122.209 [65799.351063] [tdb] Shutdown Tempesta DB Apr 26 10:20:48 192.168.122.209 [65799.585101] End test: t_modify_http_headers.test_common_config.TestCachedRespSetHeader.test_add_hdrs_derive_config Apr 26 10:20:48 192.168.122.209 [65799.605923] Start test: t_modify_http_headers.test_common_config.TestCachedRespSetHeader.test_add_hdrs_override_config Apr 26 10:20:50 192.168.122.209 [65800.686845] [tdb] Start Tempesta DB Apr 26 10:20:50 192.168.122.209 [65800.828046] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:20:51 192.168.122.209 [65802.368471] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65802.368471] Maybe that's fine, but it's worth checking the [65802.368471] config - if there is no relations between the [65802.368471] names, then host name confusion attack is possible. Apr 26 10:20:51 192.168.122.209 [65802.519613] [tempesta fw] Configuration processing is completed. Apr 26 10:20:51 192.168.122.209 [65802.574890] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:20:52 192.168.122.209 [65803.048553] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:20:52 192.168.122.209 [65803.077632] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:20:52 192.168.122.209 [65803.114214] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:20:52 192.168.122.209 [65803.163584] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:20:52 192.168.122.209 [65803.165322] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:20:52 192.168.122.209 [65803.211530] [tempesta fw] Tempesta FW is ready Apr 26 10:20:53 192.168.122.209 [65803.826559] [tdb] Close table 'client0.tdb' Apr 26 10:20:53 192.168.122.209 [65804.013246] [tdb] Close table 'sessions0.tdb' Apr 26 10:20:56 192.168.122.209 [65807.246760] [tdb] Close table 'cache0.tdb' Apr 26 10:20:56 192.168.122.209 [65807.503291] [tdb] Close table 'filter0.tdb' Apr 26 10:20:56 192.168.122.209 [65807.503723] [tempesta fw] modules are stopped Apr 26 10:20:57 192.168.122.209 [65807.713804] [tempesta fw] exiting... Apr 26 10:20:57 192.168.122.209 [65807.826815] [tdb] Shutdown Tempesta DB Apr 26 10:20:57 192.168.122.209 [65808.018614] End test: t_modify_http_headers.test_common_config.TestCachedRespSetHeader.test_add_hdrs_override_config Apr 26 10:20:57 192.168.122.209 [65808.036764] Start test: t_modify_http_headers.test_common_config.TestCachedRespSetHeader.test_add_some_hdrs Apr 26 10:20:58 192.168.122.209 [65809.048394] [tdb] Start Tempesta DB Apr 26 10:20:58 192.168.122.209 [65809.201342] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:21:00 192.168.122.209 [65810.752988] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65810.752988] Maybe that's fine, but it's worth checking the [65810.752988] config - if there is no relations between the [65810.752988] names, then host name confusion attack is possible. Apr 26 10:21:00 192.168.122.209 [65810.915736] [tempesta fw] Configuration processing is completed. Apr 26 10:21:00 192.168.122.209 [65810.971020] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:21:00 192.168.122.209 [65811.403413] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:21:00 192.168.122.209 [65811.430260] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:21:00 192.168.122.209 [65811.458446] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:21:00 192.168.122.209 [65811.503696] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:21:00 192.168.122.209 [65811.505430] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:21:00 192.168.122.209 [65811.551635] [tempesta fw] Tempesta FW is ready Apr 26 10:21:01 192.168.122.209 [65812.137051] [tdb] Close table 'client0.tdb' Apr 26 10:21:01 192.168.122.209 [65812.342853] [tdb] Close table 'sessions0.tdb' Apr 26 10:21:04 192.168.122.209 [65815.548214] [tdb] Close table 'cache0.tdb' Apr 26 10:21:05 192.168.122.209 [65815.786125] [tdb] Close table 'filter0.tdb' Apr 26 10:21:05 192.168.122.209 [65815.786549] [tempesta fw] modules are stopped Apr 26 10:21:05 192.168.122.209 [65816.041130] [tempesta fw] exiting... Apr 26 10:21:05 192.168.122.209 [65816.164904] [tdb] Shutdown Tempesta DB Apr 26 10:21:05 192.168.122.209 [65816.367186] End test: t_modify_http_headers.test_common_config.TestCachedRespSetHeader.test_add_some_hdrs Apr 26 10:21:05 192.168.122.209 [65816.380242] Start test: t_modify_http_headers.test_common_config.TestCachedRespSetHeader.test_add_some_hdrs_custom_location Apr 26 10:21:06 192.168.122.209 [65817.384742] [tdb] Start Tempesta DB Apr 26 10:21:06 192.168.122.209 [65817.520918] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:21:08 192.168.122.209 [65819.041064] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65819.041064] Maybe that's fine, but it's worth checking the [65819.041064] config - if there is no relations between the [65819.041064] names, then host name confusion attack is possible. Apr 26 10:21:08 192.168.122.209 [65819.179805] [tempesta fw] Configuration processing is completed. Apr 26 10:21:08 192.168.122.209 [65819.239060] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:21:09 192.168.122.209 [65819.665973] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:21:09 192.168.122.209 [65819.692443] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:21:09 192.168.122.209 [65819.719789] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:21:09 192.168.122.209 [65819.771794] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:21:09 192.168.122.209 [65819.773528] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:21:09 192.168.122.209 [65819.815755] [tempesta fw] Tempesta FW is ready Apr 26 10:21:09 192.168.122.209 [65820.421863] [tdb] Close table 'client0.tdb' Apr 26 10:21:09 192.168.122.209 [65820.602820] [tdb] Close table 'sessions0.tdb' Apr 26 10:21:13 192.168.122.209 [65823.840887] [tdb] Close table 'cache0.tdb' Apr 26 10:21:13 192.168.122.209 [65824.090278] [tdb] Close table 'filter0.tdb' Apr 26 10:21:13 192.168.122.209 [65824.090700] [tempesta fw] modules are stopped Apr 26 10:21:13 192.168.122.209 [65824.275388] [tempesta fw] exiting... Apr 26 10:21:13 192.168.122.209 [65824.381947] [tdb] Shutdown Tempesta DB Apr 26 10:21:13 192.168.122.209 [65824.601062] End test: t_modify_http_headers.test_common_config.TestCachedRespSetHeader.test_add_some_hdrs_custom_location Apr 26 10:21:13 192.168.122.209 [65824.620477] Start test: t_modify_http_headers.test_common_config.TestReqAddHeader.test_add_hdrs_derive_config Apr 26 10:21:15 192.168.122.209 [65825.705514] [tdb] Start Tempesta DB Apr 26 10:21:15 192.168.122.209 [65825.843420] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:21:16 192.168.122.209 [65827.261134] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65827.261134] Maybe that's fine, but it's worth checking the [65827.261134] config - if there is no relations between the [65827.261134] names, then host name confusion attack is possible. Apr 26 10:21:16 192.168.122.209 [65827.375880] [tempesta fw] Configuration processing is completed. Apr 26 10:21:16 192.168.122.209 [65827.447035] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:21:17 192.168.122.209 [65827.884184] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:21:17 192.168.122.209 [65827.918939] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:21:17 192.168.122.209 [65827.945398] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:21:17 192.168.122.209 [65827.999897] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:21:17 192.168.122.209 [65828.001626] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:21:17 192.168.122.209 [65828.043847] [tempesta fw] Tempesta FW is ready Apr 26 10:21:17 192.168.122.209 [65828.624665] [tdb] Close table 'client0.tdb' Apr 26 10:21:18 192.168.122.209 [65828.808697] [tdb] Close table 'sessions0.tdb' Apr 26 10:21:21 192.168.122.209 [65831.990018] [tdb] Close table 'cache0.tdb' Apr 26 10:21:21 192.168.122.209 [65832.224381] [tdb] Close table 'filter0.tdb' Apr 26 10:21:21 192.168.122.209 [65832.224801] [tempesta fw] modules are stopped Apr 26 10:21:21 192.168.122.209 [65832.433438] [tempesta fw] exiting... Apr 26 10:21:21 192.168.122.209 [65832.567415] [tdb] Shutdown Tempesta DB Apr 26 10:21:22 192.168.122.209 [65832.790325] End test: t_modify_http_headers.test_common_config.TestReqAddHeader.test_add_hdrs_derive_config Apr 26 10:21:22 192.168.122.209 [65832.813443] Start test: t_modify_http_headers.test_common_config.TestReqAddHeader.test_add_hdrs_override_config Apr 26 10:21:23 192.168.122.209 [65833.832423] [tdb] Start Tempesta DB Apr 26 10:21:23 192.168.122.209 [65833.992288] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:21:24 192.168.122.209 [65835.501238] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65835.501238] Maybe that's fine, but it's worth checking the [65835.501238] config - if there is no relations between the [65835.501238] names, then host name confusion attack is possible. Apr 26 10:21:24 192.168.122.209 [65835.624047] [tempesta fw] Configuration processing is completed. Apr 26 10:21:25 192.168.122.209 [65835.681596] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:21:25 192.168.122.209 [65836.122199] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:21:25 192.168.122.209 [65836.148842] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:21:25 192.168.122.209 [65836.175976] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:21:25 192.168.122.209 [65836.215999] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:21:25 192.168.122.209 [65836.217746] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:21:25 192.168.122.209 [65836.255962] [tempesta fw] Tempesta FW is ready Apr 26 10:21:26 192.168.122.209 [65836.811921] [tdb] Close table 'client0.tdb' Apr 26 10:21:26 192.168.122.209 [65836.996909] [tdb] Close table 'sessions0.tdb' Apr 26 10:21:29 192.168.122.209 [65840.214387] [tdb] Close table 'cache0.tdb' Apr 26 10:21:29 192.168.122.209 [65840.441528] [tdb] Close table 'filter0.tdb' Apr 26 10:21:29 192.168.122.209 [65840.441979] [tempesta fw] modules are stopped Apr 26 10:21:30 192.168.122.209 [65840.640655] [tempesta fw] exiting... Apr 26 10:21:30 192.168.122.209 [65840.738073] [tdb] Shutdown Tempesta DB Apr 26 10:21:30 192.168.122.209 [65840.927798] End test: t_modify_http_headers.test_common_config.TestReqAddHeader.test_add_hdrs_override_config Apr 26 10:21:30 192.168.122.209 [65840.941818] Start test: t_modify_http_headers.test_common_config.TestReqAddHeader.test_add_some_hdrs Apr 26 10:21:31 192.168.122.209 [65842.004688] [tdb] Start Tempesta DB Apr 26 10:21:31 192.168.122.209 [65842.143119] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:21:32 192.168.122.209 [65843.605351] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65843.605351] Maybe that's fine, but it's worth checking the [65843.605351] config - if there is no relations between the [65843.605351] names, then host name confusion attack is possible. Apr 26 10:21:33 192.168.122.209 [65843.732111] [tempesta fw] Configuration processing is completed. Apr 26 10:21:33 192.168.122.209 [65843.796082] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:21:33 192.168.122.209 [65844.219422] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:21:33 192.168.122.209 [65844.255582] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:21:33 192.168.122.209 [65844.282463] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:21:33 192.168.122.209 [65844.332086] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:21:33 192.168.122.209 [65844.333814] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:21:33 192.168.122.209 [65844.372068] [tempesta fw] Tempesta FW is ready Apr 26 10:21:34 192.168.122.209 [65844.931962] [tdb] Close table 'client0.tdb' Apr 26 10:21:34 192.168.122.209 [65845.117992] [tdb] Close table 'sessions0.tdb' Apr 26 10:21:37 192.168.122.209 [65848.292823] [tdb] Close table 'cache0.tdb' Apr 26 10:21:37 192.168.122.209 [65848.512971] [tdb] Close table 'filter0.tdb' Apr 26 10:21:37 192.168.122.209 [65848.513409] [tempesta fw] modules are stopped Apr 26 10:21:38 192.168.122.209 [65848.738682] [tempesta fw] exiting... Apr 26 10:21:38 192.168.122.209 [65848.877322] [tdb] Shutdown Tempesta DB Apr 26 10:21:38 192.168.122.209 [65849.063208] End test: t_modify_http_headers.test_common_config.TestReqAddHeader.test_add_some_hdrs Apr 26 10:21:38 192.168.122.209 [65849.072774] Start test: t_modify_http_headers.test_common_config.TestReqAddHeader.test_add_some_hdrs_custom_location Apr 26 10:21:39 192.168.122.209 [65850.179525] [tdb] Start Tempesta DB Apr 26 10:21:39 192.168.122.209 [65850.329897] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:21:41 192.168.122.209 [65851.817418] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65851.817418] Maybe that's fine, but it's worth checking the [65851.817418] config - if there is no relations between the [65851.817418] names, then host name confusion attack is possible. Apr 26 10:21:41 192.168.122.209 [65851.948273] [tempesta fw] Configuration processing is completed. Apr 26 10:21:41 192.168.122.209 [65852.009846] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:21:41 192.168.122.209 [65852.459109] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:21:41 192.168.122.209 [65852.485680] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:21:41 192.168.122.209 [65852.512087] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:21:41 192.168.122.209 [65852.552197] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:21:41 192.168.122.209 [65852.553931] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:21:41 192.168.122.209 [65852.592128] [tempesta fw] Tempesta FW is ready Apr 26 10:21:42 192.168.122.209 [65853.183381] [tdb] Close table 'client0.tdb' Apr 26 10:21:42 192.168.122.209 [65853.370316] [tdb] Close table 'sessions0.tdb' Apr 26 10:21:45 192.168.122.209 [65856.566712] [tdb] Close table 'cache0.tdb' Apr 26 10:21:46 192.168.122.209 [65856.813108] [tdb] Close table 'filter0.tdb' Apr 26 10:21:46 192.168.122.209 [65856.813534] [tempesta fw] modules are stopped Apr 26 10:21:46 192.168.122.209 [65857.033638] [tempesta fw] exiting... Apr 26 10:21:46 192.168.122.209 [65857.161457] [tdb] Shutdown Tempesta DB Apr 26 10:21:46 192.168.122.209 [65857.383495] End test: t_modify_http_headers.test_common_config.TestReqAddHeader.test_add_some_hdrs_custom_location Apr 26 10:21:46 192.168.122.209 [65857.402883] Start test: t_modify_http_headers.test_common_config.TestReqSetHeader.test_add_hdrs_derive_config Apr 26 10:21:47 192.168.122.209 [65858.459491] [tdb] Start Tempesta DB Apr 26 10:21:47 192.168.122.209 [65858.587696] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:21:49 192.168.122.209 [65860.093574] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65860.093574] Maybe that's fine, but it's worth checking the [65860.093574] config - if there is no relations between the [65860.093574] names, then host name confusion attack is possible. Apr 26 10:21:49 192.168.122.209 [65860.224246] [tempesta fw] Configuration processing is completed. Apr 26 10:21:49 192.168.122.209 [65860.285622] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:21:50 192.168.122.209 [65860.727629] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:21:50 192.168.122.209 [65860.753115] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:21:50 192.168.122.209 [65860.779081] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:21:50 192.168.122.209 [65860.828282] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:21:50 192.168.122.209 [65860.830036] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:21:50 192.168.122.209 [65860.872255] [tempesta fw] Tempesta FW is ready Apr 26 10:21:50 192.168.122.209 [65861.482372] [tdb] Close table 'client0.tdb' Apr 26 10:21:51 192.168.122.209 [65861.781254] [tdb] Close table 'sessions0.tdb' Apr 26 10:21:54 192.168.122.209 [65865.033407] [tdb] Close table 'cache0.tdb' Apr 26 10:21:54 192.168.122.209 [65865.303459] [tdb] Close table 'filter0.tdb' Apr 26 10:21:54 192.168.122.209 [65865.303883] [tempesta fw] modules are stopped Apr 26 10:21:54 192.168.122.209 [65865.526859] [tempesta fw] exiting... Apr 26 10:21:55 192.168.122.209 [65865.659748] [tdb] Shutdown Tempesta DB Apr 26 10:21:55 192.168.122.209 [65865.867927] End test: t_modify_http_headers.test_common_config.TestReqSetHeader.test_add_hdrs_derive_config Apr 26 10:21:55 192.168.122.209 [65865.890048] Start test: t_modify_http_headers.test_common_config.TestReqSetHeader.test_add_hdrs_override_config Apr 26 10:21:56 192.168.122.209 [65866.938503] [tdb] Start Tempesta DB Apr 26 10:21:56 192.168.122.209 [65867.074583] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:21:57 192.168.122.209 [65868.509688] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65868.509688] Maybe that's fine, but it's worth checking the [65868.509688] config - if there is no relations between the [65868.509688] names, then host name confusion attack is possible. Apr 26 10:21:58 192.168.122.209 [65868.636447] [tempesta fw] Configuration processing is completed. Apr 26 10:21:58 192.168.122.209 [65868.695854] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:21:58 192.168.122.209 [65869.126248] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:21:58 192.168.122.209 [65869.152060] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:21:58 192.168.122.209 [65869.178598] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:21:58 192.168.122.209 [65869.224401] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:21:58 192.168.122.209 [65869.226127] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:21:58 192.168.122.209 [65869.264344] [tempesta fw] Tempesta FW is ready Apr 26 10:21:59 192.168.122.209 [65869.834918] [tdb] Close table 'client0.tdb' Apr 26 10:21:59 192.168.122.209 [65870.037731] [tdb] Close table 'sessions0.tdb' Apr 26 10:22:02 192.168.122.209 [65873.248632] [tdb] Close table 'cache0.tdb' Apr 26 10:22:02 192.168.122.209 [65873.534105] [tdb] Close table 'filter0.tdb' Apr 26 10:22:02 192.168.122.209 [65873.534535] [tempesta fw] modules are stopped Apr 26 10:22:03 192.168.122.209 [65873.728997] [tempesta fw] exiting... Apr 26 10:22:03 192.168.122.209 [65873.823532] [tdb] Shutdown Tempesta DB Apr 26 10:22:03 192.168.122.209 [65874.047803] End test: t_modify_http_headers.test_common_config.TestReqSetHeader.test_add_hdrs_override_config Apr 26 10:22:03 192.168.122.209 [65874.061037] Start test: t_modify_http_headers.test_common_config.TestReqSetHeader.test_add_some_hdrs Apr 26 10:22:04 192.168.122.209 [65875.101060] [tdb] Start Tempesta DB Apr 26 10:22:04 192.168.122.209 [65875.235330] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:22:06 192.168.122.209 [65876.705854] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65876.705854] Maybe that's fine, but it's worth checking the [65876.705854] config - if there is no relations between the [65876.705854] names, then host name confusion attack is possible. Apr 26 10:22:06 192.168.122.209 [65876.828563] [tempesta fw] Configuration processing is completed. Apr 26 10:22:06 192.168.122.209 [65876.887357] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:22:06 192.168.122.209 [65877.328097] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:22:06 192.168.122.209 [65877.354339] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:22:06 192.168.122.209 [65877.381573] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:22:06 192.168.122.209 [65877.432506] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:22:06 192.168.122.209 [65877.434241] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:22:06 192.168.122.209 [65877.476438] [tempesta fw] Tempesta FW is ready Apr 26 10:22:07 192.168.122.209 [65878.039188] [tdb] Close table 'client0.tdb' Apr 26 10:22:07 192.168.122.209 [65878.222745] [tdb] Close table 'sessions0.tdb' Apr 26 10:22:10 192.168.122.209 [65881.475697] [tdb] Close table 'cache0.tdb' Apr 26 10:22:11 192.168.122.209 [65881.692576] [tdb] Close table 'filter0.tdb' Apr 26 10:22:11 192.168.122.209 [65881.693041] [tempesta fw] modules are stopped Apr 26 10:22:11 192.168.122.209 [65881.891541] [tempesta fw] exiting... Apr 26 10:22:11 192.168.122.209 [65882.021677] [tdb] Shutdown Tempesta DB Apr 26 10:22:11 192.168.122.209 [65882.207708] End test: t_modify_http_headers.test_common_config.TestReqSetHeader.test_add_some_hdrs Apr 26 10:22:11 192.168.122.209 [65882.219794] Start test: t_modify_http_headers.test_common_config.TestReqSetHeader.test_add_some_hdrs_custom_location Apr 26 10:22:12 192.168.122.209 [65883.273157] [tdb] Start Tempesta DB Apr 26 10:22:12 192.168.122.209 [65883.427885] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:22:14 192.168.122.209 [65884.925854] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65884.925854] Maybe that's fine, but it's worth checking the [65884.925854] config - if there is no relations between the [65884.925854] names, then host name confusion attack is possible. Apr 26 10:22:14 192.168.122.209 [65885.049027] [tempesta fw] Configuration processing is completed. Apr 26 10:22:14 192.168.122.209 [65885.120747] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:22:14 192.168.122.209 [65885.560887] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:22:14 192.168.122.209 [65885.587195] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:22:14 192.168.122.209 [65885.613592] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:22:15 192.168.122.209 [65885.652612] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:22:15 192.168.122.209 [65885.654347] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:22:15 192.168.122.209 [65885.692574] [tempesta fw] Tempesta FW is ready Apr 26 10:22:15 192.168.122.209 [65886.255824] [tdb] Close table 'client0.tdb' Apr 26 10:22:15 192.168.122.209 [65886.459770] [tdb] Close table 'sessions0.tdb' Apr 26 10:22:18 192.168.122.209 [65889.623747] [tdb] Close table 'cache0.tdb' Apr 26 10:22:19 192.168.122.209 [65889.863790] [tdb] Close table 'filter0.tdb' Apr 26 10:22:19 192.168.122.209 [65889.864221] [tempesta fw] modules are stopped Apr 26 10:22:19 192.168.122.209 [65890.153247] [tempesta fw] exiting... Apr 26 10:22:19 192.168.122.209 [65890.280583] [tdb] Shutdown Tempesta DB Apr 26 10:22:19 192.168.122.209 [65890.499760] End test: t_modify_http_headers.test_common_config.TestReqSetHeader.test_add_some_hdrs_custom_location Apr 26 10:22:19 192.168.122.209 [65890.514744] Start test: t_modify_http_headers.test_common_config.TestRespAddHeader.test_add_hdrs_derive_config Apr 26 10:22:20 192.168.122.209 [65891.575414] [tdb] Start Tempesta DB Apr 26 10:22:21 192.168.122.209 [65891.706873] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:22:22 192.168.122.209 [65893.110065] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65893.110065] Maybe that's fine, but it's worth checking the [65893.110065] config - if there is no relations between the [65893.110065] names, then host name confusion attack is possible. Apr 26 10:22:22 192.168.122.209 [65893.224753] [tempesta fw] Configuration processing is completed. Apr 26 10:22:22 192.168.122.209 [65893.293630] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:22:23 192.168.122.209 [65893.770622] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:22:23 192.168.122.209 [65893.801878] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:22:23 192.168.122.209 [65893.831535] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:22:23 192.168.122.209 [65893.880698] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:22:23 192.168.122.209 [65893.882465] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:22:23 192.168.122.209 [65893.920661] [tempesta fw] Tempesta FW is ready Apr 26 10:22:23 192.168.122.209 [65894.498356] [tdb] Close table 'client0.tdb' Apr 26 10:22:24 192.168.122.209 [65894.680850] [tdb] Close table 'sessions0.tdb' Apr 26 10:22:27 192.168.122.209 [65897.925261] [tdb] Close table 'cache0.tdb' Apr 26 10:22:27 192.168.122.209 [65898.194252] [tdb] Close table 'filter0.tdb' Apr 26 10:22:27 192.168.122.209 [65898.194683] [tempesta fw] modules are stopped Apr 26 10:22:27 192.168.122.209 [65898.393095] [tempesta fw] exiting... Apr 26 10:22:27 192.168.122.209 [65898.537129] [tdb] Shutdown Tempesta DB Apr 26 10:22:28 192.168.122.209 [65898.752986] End test: t_modify_http_headers.test_common_config.TestRespAddHeader.test_add_hdrs_derive_config Apr 26 10:22:28 192.168.122.209 [65898.775111] Start test: t_modify_http_headers.test_common_config.TestRespAddHeader.test_add_hdrs_override_config Apr 26 10:22:29 192.168.122.209 [65899.858142] [tdb] Start Tempesta DB Apr 26 10:22:29 192.168.122.209 [65900.030847] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:22:30 192.168.122.209 [65901.491481] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65901.491481] Maybe that's fine, but it's worth checking the [65901.491481] config - if there is no relations between the [65901.491481] names, then host name confusion attack is possible. Apr 26 10:22:30 192.168.122.209 [65901.608891] [tempesta fw] Configuration processing is completed. Apr 26 10:22:31 192.168.122.209 [65901.662996] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:22:31 192.168.122.209 [65902.102433] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:22:31 192.168.122.209 [65902.130455] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:22:31 192.168.122.209 [65902.159165] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:22:31 192.168.122.209 [65902.208788] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:22:31 192.168.122.209 [65902.210501] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:22:31 192.168.122.209 [65902.248745] [tempesta fw] Tempesta FW is ready Apr 26 10:22:32 192.168.122.209 [65902.860963] [tdb] Close table 'client0.tdb' Apr 26 10:22:32 192.168.122.209 [65903.050402] [tdb] Close table 'sessions0.tdb' Apr 26 10:22:35 192.168.122.209 [65906.351034] [tdb] Close table 'cache0.tdb' Apr 26 10:22:35 192.168.122.209 [65906.619292] [tdb] Close table 'filter0.tdb' Apr 26 10:22:35 192.168.122.209 [65906.619736] [tempesta fw] modules are stopped Apr 26 10:22:36 192.168.122.209 [65906.853826] [tempesta fw] exiting... Apr 26 10:22:36 192.168.122.209 [65906.988435] [tdb] Shutdown Tempesta DB Apr 26 10:22:36 192.168.122.209 [65907.216334] End test: t_modify_http_headers.test_common_config.TestRespAddHeader.test_add_hdrs_override_config Apr 26 10:22:36 192.168.122.209 [65907.227745] Start test: t_modify_http_headers.test_common_config.TestRespAddHeader.test_add_some_hdrs Apr 26 10:22:37 192.168.122.209 [65908.212721] [tdb] Start Tempesta DB Apr 26 10:22:37 192.168.122.209 [65908.358765] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:22:39 192.168.122.209 [65909.722226] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65909.722226] Maybe that's fine, but it's worth checking the [65909.722226] config - if there is no relations between the [65909.722226] names, then host name confusion attack is possible. Apr 26 10:22:39 192.168.122.209 [65909.840933] [tempesta fw] Configuration processing is completed. Apr 26 10:22:39 192.168.122.209 [65909.895480] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:22:39 192.168.122.209 [65910.357637] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:22:39 192.168.122.209 [65910.387658] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:22:39 192.168.122.209 [65910.424796] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:22:39 192.168.122.209 [65910.472927] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:22:39 192.168.122.209 [65910.474656] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:22:39 192.168.122.209 [65910.524848] [tempesta fw] Tempesta FW is ready Apr 26 10:22:40 192.168.122.209 [65911.100170] [tdb] Close table 'client0.tdb' Apr 26 10:22:40 192.168.122.209 [65911.288264] [tdb] Close table 'sessions0.tdb' Apr 26 10:22:44 192.168.122.209 [65914.662525] [tdb] Close table 'cache0.tdb' Apr 26 10:22:44 192.168.122.209 [65914.922306] [tdb] Close table 'filter0.tdb' Apr 26 10:22:44 192.168.122.209 [65914.922736] [tempesta fw] modules are stopped Apr 26 10:22:44 192.168.122.209 [65915.099935] [tempesta fw] exiting... Apr 26 10:22:44 192.168.122.209 [65915.232659] [tdb] Shutdown Tempesta DB Apr 26 10:22:44 192.168.122.209 [65915.461314] End test: t_modify_http_headers.test_common_config.TestRespAddHeader.test_add_some_hdrs Apr 26 10:22:44 192.168.122.209 [65915.495223] Start test: t_modify_http_headers.test_common_config.TestRespAddHeader.test_add_some_hdrs_custom_location Apr 26 10:22:46 192.168.122.209 [65916.643741] [tdb] Start Tempesta DB Apr 26 10:22:46 192.168.122.209 [65916.802212] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:22:47 192.168.122.209 [65918.298558] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65918.298558] Maybe that's fine, but it's worth checking the [65918.298558] config - if there is no relations between the [65918.298558] names, then host name confusion attack is possible. Apr 26 10:22:47 192.168.122.209 [65918.401105] [tempesta fw] Configuration processing is completed. Apr 26 10:22:47 192.168.122.209 [65918.459375] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:22:48 192.168.122.209 [65918.882542] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:22:48 192.168.122.209 [65918.908417] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:22:48 192.168.122.209 [65918.934392] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:22:48 192.168.122.209 [65918.977046] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:22:48 192.168.122.209 [65918.980174] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:22:48 192.168.122.209 [65919.032953] [tempesta fw] Tempesta FW is ready Apr 26 10:22:48 192.168.122.209 [65919.610756] [tdb] Close table 'client0.tdb' Apr 26 10:22:49 192.168.122.209 [65919.797196] [tdb] Close table 'sessions0.tdb' Apr 26 10:22:52 192.168.122.209 [65922.970017] [tdb] Close table 'cache0.tdb' Apr 26 10:22:52 192.168.122.209 [65923.232461] [tdb] Close table 'filter0.tdb' Apr 26 10:22:52 192.168.122.209 [65923.232932] [tempesta fw] modules are stopped Apr 26 10:22:52 192.168.122.209 [65923.429711] [tempesta fw] exiting... Apr 26 10:22:52 192.168.122.209 [65923.552502] [tdb] Shutdown Tempesta DB Apr 26 10:22:53 192.168.122.209 [65923.755485] End test: t_modify_http_headers.test_common_config.TestRespAddHeader.test_add_some_hdrs_custom_location Apr 26 10:22:53 192.168.122.209 [65923.775771] Start test: t_modify_http_headers.test_common_config.TestRespSetHeader.test_add_hdrs_derive_config Apr 26 10:22:54 192.168.122.209 [65924.771776] [tdb] Start Tempesta DB Apr 26 10:22:54 192.168.122.209 [65924.910470] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:22:55 192.168.122.209 [65926.370401] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65926.370401] Maybe that's fine, but it's worth checking the [65926.370401] config - if there is no relations between the [65926.370401] names, then host name confusion attack is possible. Apr 26 10:22:55 192.168.122.209 [65926.489121] [tempesta fw] Configuration processing is completed. Apr 26 10:22:55 192.168.122.209 [65926.564140] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:22:56 192.168.122.209 [65927.063181] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:22:56 192.168.122.209 [65927.097536] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:22:56 192.168.122.209 [65927.131393] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:22:56 192.168.122.209 [65927.181100] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:22:56 192.168.122.209 [65927.182817] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:22:56 192.168.122.209 [65927.221059] [tempesta fw] Tempesta FW is ready Apr 26 10:22:57 192.168.122.209 [65927.789479] [tdb] Close table 'client0.tdb' Apr 26 10:22:57 192.168.122.209 [65927.990766] [tdb] Close table 'sessions0.tdb' Apr 26 10:23:00 192.168.122.209 [65931.267321] [tdb] Close table 'cache0.tdb' Apr 26 10:23:00 192.168.122.209 [65931.510120] [tdb] Close table 'filter0.tdb' Apr 26 10:23:00 192.168.122.209 [65931.510542] [tempesta fw] modules are stopped Apr 26 10:23:01 192.168.122.209 [65931.718443] [tempesta fw] exiting... Apr 26 10:23:01 192.168.122.209 [65931.848165] [tdb] Shutdown Tempesta DB Apr 26 10:23:01 192.168.122.209 [65932.043543] End test: t_modify_http_headers.test_common_config.TestRespSetHeader.test_add_hdrs_derive_config Apr 26 10:23:01 192.168.122.209 [65932.056682] Start test: t_modify_http_headers.test_common_config.TestRespSetHeader.test_add_hdrs_override_config Apr 26 10:23:02 192.168.122.209 [65932.989395] [tdb] Start Tempesta DB Apr 26 10:23:02 192.168.122.209 [65933.121816] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:23:03 192.168.122.209 [65934.486445] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65934.486445] Maybe that's fine, but it's worth checking the [65934.486445] config - if there is no relations between the [65934.486445] names, then host name confusion attack is possible. Apr 26 10:23:03 192.168.122.209 [65934.605249] [tempesta fw] Configuration processing is completed. Apr 26 10:23:04 192.168.122.209 [65934.659583] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:23:04 192.168.122.209 [65935.078057] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:23:04 192.168.122.209 [65935.113295] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:23:04 192.168.122.209 [65935.138693] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:23:04 192.168.122.209 [65935.185203] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:23:04 192.168.122.209 [65935.186957] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:23:04 192.168.122.209 [65935.233149] [tempesta fw] Tempesta FW is ready Apr 26 10:23:05 192.168.122.209 [65935.837339] [tdb] Close table 'client0.tdb' Apr 26 10:23:05 192.168.122.209 [65936.013403] [tdb] Close table 'sessions0.tdb' Apr 26 10:23:08 192.168.122.209 [65939.294836] [tdb] Close table 'cache0.tdb' Apr 26 10:23:08 192.168.122.209 [65939.552193] [tdb] Close table 'filter0.tdb' Apr 26 10:23:08 192.168.122.209 [65939.552600] [tempesta fw] modules are stopped Apr 26 10:23:09 192.168.122.209 [65939.750427] [tempesta fw] exiting... Apr 26 10:23:09 192.168.122.209 [65939.847214] [tdb] Shutdown Tempesta DB Apr 26 10:23:09 192.168.122.209 [65940.083756] End test: t_modify_http_headers.test_common_config.TestRespSetHeader.test_add_hdrs_override_config Apr 26 10:23:09 192.168.122.209 [65940.094457] Start test: t_modify_http_headers.test_common_config.TestRespSetHeader.test_add_some_hdrs Apr 26 10:23:10 192.168.122.209 [65941.184856] [tdb] Start Tempesta DB Apr 26 10:23:10 192.168.122.209 [65941.320194] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:23:12 192.168.122.209 [65942.742820] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65942.742820] Maybe that's fine, but it's worth checking the [65942.742820] config - if there is no relations between the [65942.742820] names, then host name confusion attack is possible. Apr 26 10:23:12 192.168.122.209 [65942.865360] [tempesta fw] Configuration processing is completed. Apr 26 10:23:12 192.168.122.209 [65942.923166] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:23:12 192.168.122.209 [65943.362057] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:23:12 192.168.122.209 [65943.390142] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:23:12 192.168.122.209 [65943.417700] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:23:12 192.168.122.209 [65943.485268] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:23:12 192.168.122.209 [65943.487224] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:23:12 192.168.122.209 [65943.529244] [tempesta fw] Tempesta FW is ready Apr 26 10:23:13 192.168.122.209 [65944.109405] [tdb] Close table 'client0.tdb' Apr 26 10:23:13 192.168.122.209 [65944.303446] [tdb] Close table 'sessions0.tdb' Apr 26 10:23:16 192.168.122.209 [65947.463361] [tdb] Close table 'cache0.tdb' Apr 26 10:23:17 192.168.122.209 [65947.686240] [tdb] Close table 'filter0.tdb' Apr 26 10:23:17 192.168.122.209 [65947.686681] [tempesta fw] modules are stopped Apr 26 10:23:17 192.168.122.209 [65947.898778] [tempesta fw] exiting... Apr 26 10:23:17 192.168.122.209 [65948.002382] [tdb] Shutdown Tempesta DB Apr 26 10:23:17 192.168.122.209 [65948.223092] End test: t_modify_http_headers.test_common_config.TestRespSetHeader.test_add_some_hdrs Apr 26 10:23:17 192.168.122.209 [65948.243288] Start test: t_modify_http_headers.test_common_config.TestRespSetHeader.test_add_some_hdrs_custom_location Apr 26 10:23:18 192.168.122.209 [65949.277470] [tdb] Start Tempesta DB Apr 26 10:23:18 192.168.122.209 [65949.423303] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:23:20 192.168.122.209 [65950.894679] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65950.894679] Maybe that's fine, but it's worth checking the [65950.894679] config - if there is no relations between the [65950.894679] names, then host name confusion attack is possible. Apr 26 10:23:20 192.168.122.209 [65951.001467] [tempesta fw] Configuration processing is completed. Apr 26 10:23:20 192.168.122.209 [65951.059878] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:23:20 192.168.122.209 [65951.480282] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:23:20 192.168.122.209 [65951.507759] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:23:20 192.168.122.209 [65951.533813] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:23:20 192.168.122.209 [65951.625391] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:23:20 192.168.122.209 [65951.627144] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:23:21 192.168.122.209 [65951.673350] [tempesta fw] Tempesta FW is ready Apr 26 10:23:21 192.168.122.209 [65952.220972] [tdb] Close table 'client0.tdb' Apr 26 10:23:21 192.168.122.209 [65952.404867] [tdb] Close table 'sessions0.tdb' Apr 26 10:23:24 192.168.122.209 [65955.548778] [tdb] Close table 'cache0.tdb' Apr 26 10:23:25 192.168.122.209 [65955.804477] [tdb] Close table 'filter0.tdb' Apr 26 10:23:25 192.168.122.209 [65955.804930] [tempesta fw] modules are stopped Apr 26 10:23:25 192.168.122.209 [65955.999664] [tempesta fw] exiting... Apr 26 10:23:25 192.168.122.209 [65956.129211] [tdb] Shutdown Tempesta DB Apr 26 10:23:25 192.168.122.209 [65956.356970] End test: t_modify_http_headers.test_common_config.TestRespSetHeader.test_add_some_hdrs_custom_location Apr 26 10:23:25 192.168.122.209 [65956.370359] Start test: t_modify_http_headers.test_common_config_h2.TestCachedRespAddHeaderH2.test_add_hdrs_derive_config Apr 26 10:23:26 192.168.122.209 [65957.372979] [tdb] Start Tempesta DB Apr 26 10:23:26 192.168.122.209 [65957.500025] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:23:28 192.168.122.209 [65958.998791] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65958.998791] Maybe that's fine, but it's worth checking the [65958.998791] config - if there is no relations between the [65958.998791] names, then host name confusion attack is possible. Apr 26 10:23:28 192.168.122.209 [65959.165528] [tempesta fw] Configuration processing is completed. Apr 26 10:23:28 192.168.122.209 [65959.221007] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:23:28 192.168.122.209 [65959.633846] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:23:29 192.168.122.209 [65959.659525] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:23:29 192.168.122.209 [65959.685638] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:23:29 192.168.122.209 [65959.745493] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:23:29 192.168.122.209 [65959.747232] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:23:29 192.168.122.209 [65959.793450] [tempesta fw] Tempesta FW is ready Apr 26 10:23:29 192.168.122.209 [65960.433088] [tdb] Close table 'client0.tdb' Apr 26 10:23:29 192.168.122.209 [65960.617401] [tdb] Close table 'sessions0.tdb' Apr 26 10:23:33 192.168.122.209 [65963.824535] [tdb] Close table 'cache0.tdb' Apr 26 10:23:33 192.168.122.209 [65964.034455] [tdb] Close table 'filter0.tdb' Apr 26 10:23:33 192.168.122.209 [65964.034886] [tempesta fw] modules are stopped Apr 26 10:23:33 192.168.122.209 [65964.229684] [tempesta fw] exiting... Apr 26 10:23:33 192.168.122.209 [65964.371650] [tdb] Shutdown Tempesta DB Apr 26 10:23:33 192.168.122.209 [65964.603262] End test: t_modify_http_headers.test_common_config_h2.TestCachedRespAddHeaderH2.test_add_hdrs_derive_config Apr 26 10:23:33 192.168.122.209 [65964.619586] Start test: t_modify_http_headers.test_common_config_h2.TestCachedRespAddHeaderH2.test_add_hdrs_override_config Apr 26 10:23:34 192.168.122.209 [65965.612038] [tdb] Start Tempesta DB Apr 26 10:23:35 192.168.122.209 [65965.751118] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:23:36 192.168.122.209 [65967.214853] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65967.214853] Maybe that's fine, but it's worth checking the [65967.214853] config - if there is no relations between the [65967.214853] names, then host name confusion attack is possible. Apr 26 10:23:36 192.168.122.209 [65967.361610] [tempesta fw] Configuration processing is completed. Apr 26 10:23:36 192.168.122.209 [65967.412540] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:23:37 192.168.122.209 [65967.812396] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:23:37 192.168.122.209 [65967.838017] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:23:37 192.168.122.209 [65967.863570] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:23:37 192.168.122.209 [65967.913621] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:23:37 192.168.122.209 [65967.915349] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:23:37 192.168.122.209 [65967.953542] [tempesta fw] Tempesta FW is ready Apr 26 10:23:37 192.168.122.209 [65968.596291] [tdb] Close table 'client0.tdb' Apr 26 10:23:38 192.168.122.209 [65968.780564] [tdb] Close table 'sessions0.tdb' Apr 26 10:23:41 192.168.122.209 [65971.954748] [tdb] Close table 'cache0.tdb' Apr 26 10:23:41 192.168.122.209 [65972.204856] [tdb] Close table 'filter0.tdb' Apr 26 10:23:41 192.168.122.209 [65972.205275] [tempesta fw] modules are stopped Apr 26 10:23:41 192.168.122.209 [65972.413796] [tempesta fw] exiting... Apr 26 10:23:41 192.168.122.209 [65972.533494] [tdb] Shutdown Tempesta DB Apr 26 10:23:42 192.168.122.209 [65972.735978] End test: t_modify_http_headers.test_common_config_h2.TestCachedRespAddHeaderH2.test_add_hdrs_override_config Apr 26 10:23:42 192.168.122.209 [65972.753615] Start test: t_modify_http_headers.test_common_config_h2.TestCachedRespAddHeaderH2.test_add_some_hdrs Apr 26 10:23:43 192.168.122.209 [65973.790944] [tdb] Start Tempesta DB Apr 26 10:23:43 192.168.122.209 [65973.932538] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:23:44 192.168.122.209 [65975.318983] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65975.318983] Maybe that's fine, but it's worth checking the [65975.318983] config - if there is no relations between the [65975.318983] names, then host name confusion attack is possible. Apr 26 10:23:44 192.168.122.209 [65975.465714] [tempesta fw] Configuration processing is completed. Apr 26 10:23:44 192.168.122.209 [65975.518421] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:23:45 192.168.122.209 [65975.930354] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:23:45 192.168.122.209 [65975.956304] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:23:45 192.168.122.209 [65975.984052] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:23:45 192.168.122.209 [65976.025704] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:23:45 192.168.122.209 [65976.027435] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:23:45 192.168.122.209 [65976.065649] [tempesta fw] Tempesta FW is ready Apr 26 10:23:46 192.168.122.209 [65976.701367] [tdb] Close table 'client0.tdb' Apr 26 10:23:46 192.168.122.209 [65976.885234] [tdb] Close table 'sessions0.tdb' Apr 26 10:23:49 192.168.122.209 [65980.064450] [tdb] Close table 'cache0.tdb' Apr 26 10:23:49 192.168.122.209 [65980.284409] [tdb] Close table 'filter0.tdb' Apr 26 10:23:49 192.168.122.209 [65980.284812] [tempesta fw] modules are stopped Apr 26 10:23:49 192.168.122.209 [65980.488598] [tempesta fw] exiting... Apr 26 10:23:49 192.168.122.209 [65980.598920] [tdb] Shutdown Tempesta DB Apr 26 10:23:50 192.168.122.209 [65980.838586] End test: t_modify_http_headers.test_common_config_h2.TestCachedRespAddHeaderH2.test_add_some_hdrs Apr 26 10:23:50 192.168.122.209 [65980.852133] Start test: t_modify_http_headers.test_common_config_h2.TestCachedRespAddHeaderH2.test_add_some_hdrs_custom_location Apr 26 10:23:51 192.168.122.209 [65981.794877] [tdb] Start Tempesta DB Apr 26 10:23:51 192.168.122.209 [65981.923806] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:23:52 192.168.122.209 [65983.431093] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65983.431093] Maybe that's fine, but it's worth checking the [65983.431093] config - if there is no relations between the [65983.431093] names, then host name confusion attack is possible. Apr 26 10:23:52 192.168.122.209 [65983.569840] [tempesta fw] Configuration processing is completed. Apr 26 10:23:52 192.168.122.209 [65983.631517] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:23:53 192.168.122.209 [65984.058138] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:23:53 192.168.122.209 [65984.084443] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:23:53 192.168.122.209 [65984.111232] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:23:53 192.168.122.209 [65984.165826] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:23:53 192.168.122.209 [65984.167578] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:23:53 192.168.122.209 [65984.205762] [tempesta fw] Tempesta FW is ready Apr 26 10:23:54 192.168.122.209 [65984.855447] [tdb] Close table 'client0.tdb' Apr 26 10:23:54 192.168.122.209 [65985.038112] [tdb] Close table 'sessions0.tdb' Apr 26 10:23:57 192.168.122.209 [65988.208069] [tdb] Close table 'cache0.tdb' Apr 26 10:23:57 192.168.122.209 [65988.446146] [tdb] Close table 'filter0.tdb' Apr 26 10:23:57 192.168.122.209 [65988.446552] [tempesta fw] modules are stopped Apr 26 10:23:57 192.168.122.209 [65988.631311] [tempesta fw] exiting... Apr 26 10:23:58 192.168.122.209 [65988.740862] [tdb] Shutdown Tempesta DB Apr 26 10:23:58 192.168.122.209 [65988.944337] End test: t_modify_http_headers.test_common_config_h2.TestCachedRespAddHeaderH2.test_add_some_hdrs_custom_location Apr 26 10:23:58 192.168.122.209 [65988.974698] Start test: t_modify_http_headers.test_common_config_h2.TestCachedRespSetHeaderH2.test_add_hdrs_derive_config Apr 26 10:23:59 192.168.122.209 [65990.021302] [tdb] Start Tempesta DB Apr 26 10:23:59 192.168.122.209 [65990.155008] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:24:00 192.168.122.209 [65991.519154] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65991.519154] Maybe that's fine, but it's worth checking the [65991.519154] config - if there is no relations between the [65991.519154] names, then host name confusion attack is possible. Apr 26 10:24:01 192.168.122.209 [65991.683155] [tempesta fw] Configuration processing is completed. Apr 26 10:24:01 192.168.122.209 [65991.732689] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:24:01 192.168.122.209 [65992.140982] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:24:01 192.168.122.209 [65992.167737] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:24:01 192.168.122.209 [65992.195600] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:24:01 192.168.122.209 [65992.237895] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:24:01 192.168.122.209 [65992.239625] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:24:01 192.168.122.209 [65992.281856] [tempesta fw] Tempesta FW is ready Apr 26 10:24:02 192.168.122.209 [65992.934481] [tdb] Close table 'client0.tdb' Apr 26 10:24:02 192.168.122.209 [65993.123332] [tdb] Close table 'sessions0.tdb' Apr 26 10:24:05 192.168.122.209 [65996.275911] [tdb] Close table 'cache0.tdb' Apr 26 10:24:05 192.168.122.209 [65996.515139] [tdb] Close table 'filter0.tdb' Apr 26 10:24:05 192.168.122.209 [65996.515568] [tempesta fw] modules are stopped Apr 26 10:24:06 192.168.122.209 [65996.702009] [tempesta fw] exiting... Apr 26 10:24:06 192.168.122.209 [65996.795059] [tdb] Shutdown Tempesta DB Apr 26 10:24:06 192.168.122.209 [65997.006763] End test: t_modify_http_headers.test_common_config_h2.TestCachedRespSetHeaderH2.test_add_hdrs_derive_config Apr 26 10:24:06 192.168.122.209 [65997.018811] Start test: t_modify_http_headers.test_common_config_h2.TestCachedRespSetHeaderH2.test_add_hdrs_override_config Apr 26 10:24:07 192.168.122.209 [65998.052143] [tdb] Start Tempesta DB Apr 26 10:24:07 192.168.122.209 [65998.197532] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:24:09 192.168.122.209 [65999.775279] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [65999.775279] Maybe that's fine, but it's worth checking the [65999.775279] config - if there is no relations between the [65999.775279] names, then host name confusion attack is possible. Apr 26 10:24:09 192.168.122.209 [65999.938456] [tempesta fw] Configuration processing is completed. Apr 26 10:24:09 192.168.122.209 [65999.994451] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:24:09 192.168.122.209 [66000.404213] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:24:09 192.168.122.209 [66000.438632] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:24:09 192.168.122.209 [66000.463942] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:24:09 192.168.122.209 [66000.513998] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:24:09 192.168.122.209 [66000.515749] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:24:09 192.168.122.209 [66000.557962] [tempesta fw] Tempesta FW is ready Apr 26 10:24:10 192.168.122.209 [66001.205984] [tdb] Close table 'client0.tdb' Apr 26 10:24:10 192.168.122.209 [66001.383350] [tdb] Close table 'sessions0.tdb' Apr 26 10:24:13 192.168.122.209 [66004.590511] [tdb] Close table 'cache0.tdb' Apr 26 10:24:14 192.168.122.209 [66004.825892] [tdb] Close table 'filter0.tdb' Apr 26 10:24:14 192.168.122.209 [66004.826324] [tempesta fw] modules are stopped Apr 26 10:24:14 192.168.122.209 [66005.041928] [tempesta fw] exiting... Apr 26 10:24:14 192.168.122.209 [66005.164728] [tdb] Shutdown Tempesta DB Apr 26 10:24:14 192.168.122.209 [66005.393270] End test: t_modify_http_headers.test_common_config_h2.TestCachedRespSetHeaderH2.test_add_hdrs_override_config Apr 26 10:24:14 192.168.122.209 [66005.415240] Start test: t_modify_http_headers.test_common_config_h2.TestCachedRespSetHeaderH2.test_add_some_hdrs Apr 26 10:24:15 192.168.122.209 [66006.432722] [tdb] Start Tempesta DB Apr 26 10:24:15 192.168.122.209 [66006.567033] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:24:17 192.168.122.209 [66007.979404] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66007.979404] Maybe that's fine, but it's worth checking the [66007.979404] config - if there is no relations between the [66007.979404] names, then host name confusion attack is possible. Apr 26 10:24:17 192.168.122.209 [66008.134140] [tempesta fw] Configuration processing is completed. Apr 26 10:24:17 192.168.122.209 [66008.194752] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:24:17 192.168.122.209 [66008.618578] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:24:18 192.168.122.209 [66008.644933] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:24:18 192.168.122.209 [66008.670965] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:24:18 192.168.122.209 [66008.718097] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:24:18 192.168.122.209 [66008.720032] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:24:18 192.168.122.209 [66008.758048] [tempesta fw] Tempesta FW is ready Apr 26 10:24:18 192.168.122.209 [66009.387840] [tdb] Close table 'client0.tdb' Apr 26 10:24:18 192.168.122.209 [66009.635835] [tdb] Close table 'sessions0.tdb' Apr 26 10:24:22 192.168.122.209 [66012.788843] [tdb] Close table 'cache0.tdb' Apr 26 10:24:22 192.168.122.209 [66013.040089] [tdb] Close table 'filter0.tdb' Apr 26 10:24:22 192.168.122.209 [66013.040493] [tempesta fw] modules are stopped Apr 26 10:24:22 192.168.122.209 [66013.216997] [tempesta fw] exiting... Apr 26 10:24:22 192.168.122.209 [66013.333802] [tdb] Shutdown Tempesta DB Apr 26 10:24:22 192.168.122.209 [66013.542298] End test: t_modify_http_headers.test_common_config_h2.TestCachedRespSetHeaderH2.test_add_some_hdrs Apr 26 10:24:22 192.168.122.209 [66013.559971] Start test: t_modify_http_headers.test_common_config_h2.TestCachedRespSetHeaderH2.test_add_some_hdrs_custom_location Apr 26 10:24:23 192.168.122.209 [66014.561414] [tdb] Start Tempesta DB Apr 26 10:24:24 192.168.122.209 [66014.687333] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:24:25 192.168.122.209 [66016.123436] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66016.123436] Maybe that's fine, but it's worth checking the [66016.123436] config - if there is no relations between the [66016.123436] names, then host name confusion attack is possible. Apr 26 10:24:25 192.168.122.209 [66016.270625] [tempesta fw] Configuration processing is completed. Apr 26 10:24:25 192.168.122.209 [66016.329824] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:24:26 192.168.122.209 [66016.754471] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:24:26 192.168.122.209 [66016.781056] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:24:26 192.168.122.209 [66016.807834] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:24:26 192.168.122.209 [66016.862160] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:24:26 192.168.122.209 [66016.863910] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:24:26 192.168.122.209 [66016.906158] [tempesta fw] Tempesta FW is ready Apr 26 10:24:26 192.168.122.209 [66017.545917] [tdb] Close table 'client0.tdb' Apr 26 10:24:27 192.168.122.209 [66017.727127] [tdb] Close table 'sessions0.tdb' Apr 26 10:24:30 192.168.122.209 [66020.856459] [tdb] Close table 'cache0.tdb' Apr 26 10:24:30 192.168.122.209 [66021.102930] [tdb] Close table 'filter0.tdb' Apr 26 10:24:30 192.168.122.209 [66021.103373] [tempesta fw] modules are stopped Apr 26 10:24:30 192.168.122.209 [66021.314354] [tempesta fw] exiting... Apr 26 10:24:30 192.168.122.209 [66021.426422] [tdb] Shutdown Tempesta DB Apr 26 10:24:30 192.168.122.209 [66021.629317] End test: t_modify_http_headers.test_common_config_h2.TestCachedRespSetHeaderH2.test_add_some_hdrs_custom_location Apr 26 10:24:31 192.168.122.209 [66021.639426] Start test: t_modify_http_headers.test_common_config_h2.TestReqAddHeaderH2.test_add_hdrs_derive_config Apr 26 10:24:32 192.168.122.209 [66022.705901] [tdb] Start Tempesta DB Apr 26 10:24:32 192.168.122.209 [66022.826753] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:24:33 192.168.122.209 [66024.251605] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66024.251605] Maybe that's fine, but it's worth checking the [66024.251605] config - if there is no relations between the [66024.251605] names, then host name confusion attack is possible. Apr 26 10:24:33 192.168.122.209 [66024.374386] [tempesta fw] Configuration processing is completed. Apr 26 10:24:33 192.168.122.209 [66024.424829] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:24:34 192.168.122.209 [66024.835205] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:24:34 192.168.122.209 [66024.861546] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:24:34 192.168.122.209 [66024.889107] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:24:34 192.168.122.209 [66024.926296] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:24:34 192.168.122.209 [66024.928038] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:24:34 192.168.122.209 [66024.970180] [tempesta fw] Tempesta FW is ready Apr 26 10:24:34 192.168.122.209 [66025.546548] [tdb] Close table 'client0.tdb' Apr 26 10:24:35 192.168.122.209 [66025.728724] [tdb] Close table 'sessions0.tdb' Apr 26 10:24:38 192.168.122.209 [66028.853246] [tdb] Close table 'cache0.tdb' Apr 26 10:24:38 192.168.122.209 [66029.094472] [tdb] Close table 'filter0.tdb' Apr 26 10:24:38 192.168.122.209 [66029.094906] [tempesta fw] modules are stopped Apr 26 10:24:38 192.168.122.209 [66029.286703] [tempesta fw] exiting... Apr 26 10:24:38 192.168.122.209 [66029.407562] [tdb] Shutdown Tempesta DB Apr 26 10:24:38 192.168.122.209 [66029.615510] End test: t_modify_http_headers.test_common_config_h2.TestReqAddHeaderH2.test_add_hdrs_derive_config Apr 26 10:24:38 192.168.122.209 [66029.630812] Start test: t_modify_http_headers.test_common_config_h2.TestReqAddHeaderH2.test_add_hdrs_override_config Apr 26 10:24:40 192.168.122.209 [66030.704984] [tdb] Start Tempesta DB Apr 26 10:24:40 192.168.122.209 [66030.850620] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:24:41 192.168.122.209 [66032.359586] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66032.359586] Maybe that's fine, but it's worth checking the [66032.359586] config - if there is no relations between the [66032.359586] names, then host name confusion attack is possible. Apr 26 10:24:41 192.168.122.209 [66032.490389] [tempesta fw] Configuration processing is completed. Apr 26 10:24:41 192.168.122.209 [66032.547064] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:24:42 192.168.122.209 [66032.981694] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:24:42 192.168.122.209 [66033.017073] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:24:42 192.168.122.209 [66033.043743] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:24:42 192.168.122.209 [66033.090407] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:24:42 192.168.122.209 [66033.092172] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:24:42 192.168.122.209 [66033.130338] [tempesta fw] Tempesta FW is ready Apr 26 10:24:43 192.168.122.209 [66033.743824] [tdb] Close table 'client0.tdb' Apr 26 10:24:43 192.168.122.209 [66033.930626] [tdb] Close table 'sessions0.tdb' Apr 26 10:24:46 192.168.122.209 [66037.106314] [tdb] Close table 'cache0.tdb' Apr 26 10:24:46 192.168.122.209 [66037.354978] [tdb] Close table 'filter0.tdb' Apr 26 10:24:46 192.168.122.209 [66037.355404] [tempesta fw] modules are stopped Apr 26 10:24:46 192.168.122.209 [66037.533015] [tempesta fw] exiting... Apr 26 10:24:47 192.168.122.209 [66037.679894] [tdb] Shutdown Tempesta DB Apr 26 10:24:47 192.168.122.209 [66037.898027] End test: t_modify_http_headers.test_common_config_h2.TestReqAddHeaderH2.test_add_hdrs_override_config Apr 26 10:24:47 192.168.122.209 [66037.913545] Start test: t_modify_http_headers.test_common_config_h2.TestReqAddHeaderH2.test_add_some_hdrs Apr 26 10:24:48 192.168.122.209 [66038.948840] [tdb] Start Tempesta DB Apr 26 10:24:48 192.168.122.209 [66039.090400] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:24:49 192.168.122.209 [66040.547796] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66040.547796] Maybe that's fine, but it's worth checking the [66040.547796] config - if there is no relations between the [66040.547796] names, then host name confusion attack is possible. Apr 26 10:24:50 192.168.122.209 [66040.662453] [tempesta fw] Configuration processing is completed. Apr 26 10:24:50 192.168.122.209 [66040.716448] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:24:50 192.168.122.209 [66041.135161] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:24:50 192.168.122.209 [66041.160881] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:24:50 192.168.122.209 [66041.187101] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:24:50 192.168.122.209 [66041.234499] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:24:50 192.168.122.209 [66041.236251] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:24:50 192.168.122.209 [66041.294450] [tempesta fw] Tempesta FW is ready Apr 26 10:24:51 192.168.122.209 [66041.911172] [tdb] Close table 'client0.tdb' Apr 26 10:24:51 192.168.122.209 [66042.105079] [tdb] Close table 'sessions0.tdb' Apr 26 10:24:54 192.168.122.209 [66045.256000] [tdb] Close table 'cache0.tdb' Apr 26 10:24:54 192.168.122.209 [66045.488530] [tdb] Close table 'filter0.tdb' Apr 26 10:24:54 192.168.122.209 [66045.488933] [tempesta fw] modules are stopped Apr 26 10:24:55 192.168.122.209 [66045.706078] [tempesta fw] exiting... Apr 26 10:24:55 192.168.122.209 [66045.842979] [tdb] Shutdown Tempesta DB Apr 26 10:24:55 192.168.122.209 [66046.046533] End test: t_modify_http_headers.test_common_config_h2.TestReqAddHeaderH2.test_add_some_hdrs Apr 26 10:24:55 192.168.122.209 [66046.060705] Start test: t_modify_http_headers.test_common_config_h2.TestReqAddHeaderH2.test_add_some_hdrs_custom_location Apr 26 10:24:56 192.168.122.209 [66047.101123] [tdb] Start Tempesta DB Apr 26 10:24:56 192.168.122.209 [66047.230776] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:24:58 192.168.122.209 [66048.679907] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66048.679907] Maybe that's fine, but it's worth checking the [66048.679907] config - if there is no relations between the [66048.679907] names, then host name confusion attack is possible. Apr 26 10:24:58 192.168.122.209 [66048.778681] [tempesta fw] Configuration processing is completed. Apr 26 10:24:58 192.168.122.209 [66048.834977] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:24:58 192.168.122.209 [66049.264282] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:24:58 192.168.122.209 [66049.298740] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:24:58 192.168.122.209 [66049.325429] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:24:58 192.168.122.209 [66049.370627] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:24:58 192.168.122.209 [66049.372447] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:24:58 192.168.122.209 [66049.410551] [tempesta fw] Tempesta FW is ready Apr 26 10:24:59 192.168.122.209 [66050.045376] [tdb] Close table 'client0.tdb' Apr 26 10:24:59 192.168.122.209 [66050.228382] [tdb] Close table 'sessions0.tdb' Apr 26 10:25:02 192.168.122.209 [66053.441787] [tdb] Close table 'cache0.tdb' Apr 26 10:25:03 192.168.122.209 [66053.651370] [tdb] Close table 'filter0.tdb' Apr 26 10:25:03 192.168.122.209 [66053.651803] [tempesta fw] modules are stopped Apr 26 10:25:03 192.168.122.209 [66053.878856] [tempesta fw] exiting... Apr 26 10:25:03 192.168.122.209 [66054.012578] [tdb] Shutdown Tempesta DB Apr 26 10:25:03 192.168.122.209 [66054.225387] End test: t_modify_http_headers.test_common_config_h2.TestReqAddHeaderH2.test_add_some_hdrs_custom_location Apr 26 10:25:03 192.168.122.209 [66054.242402] Start test: t_modify_http_headers.test_common_config_h2.TestReqSetHeaderH2.test_add_hdrs_derive_config Apr 26 10:25:04 192.168.122.209 [66055.313958] [tdb] Start Tempesta DB Apr 26 10:25:04 192.168.122.209 [66055.444954] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:25:06 192.168.122.209 [66056.896093] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66056.896093] Maybe that's fine, but it's worth checking the [66056.896093] config - if there is no relations between the [66056.896093] names, then host name confusion attack is possible. Apr 26 10:25:06 192.168.122.209 [66057.018734] [tempesta fw] Configuration processing is completed. Apr 26 10:25:06 192.168.122.209 [66057.065137] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:25:06 192.168.122.209 [66057.462114] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:25:06 192.168.122.209 [66057.490304] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:25:06 192.168.122.209 [66057.516940] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:25:06 192.168.122.209 [66057.562714] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:25:06 192.168.122.209 [66057.564437] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:25:06 192.168.122.209 [66057.602651] [tempesta fw] Tempesta FW is ready Apr 26 10:25:07 192.168.122.209 [66058.226431] [tdb] Close table 'client0.tdb' Apr 26 10:25:07 192.168.122.209 [66058.408096] [tdb] Close table 'sessions0.tdb' Apr 26 10:25:10 192.168.122.209 [66061.629379] [tdb] Close table 'cache0.tdb' Apr 26 10:25:11 192.168.122.209 [66061.853153] [tdb] Close table 'filter0.tdb' Apr 26 10:25:11 192.168.122.209 [66061.853595] [tempesta fw] modules are stopped Apr 26 10:25:11 192.168.122.209 [66062.091840] [tempesta fw] exiting... Apr 26 10:25:11 192.168.122.209 [66062.222850] [tdb] Shutdown Tempesta DB Apr 26 10:25:11 192.168.122.209 [66062.448110] End test: t_modify_http_headers.test_common_config_h2.TestReqSetHeaderH2.test_add_hdrs_derive_config Apr 26 10:25:11 192.168.122.209 [66062.461109] Start test: t_modify_http_headers.test_common_config_h2.TestReqSetHeaderH2.test_add_hdrs_override_config Apr 26 10:25:12 192.168.122.209 [66063.512806] [tdb] Start Tempesta DB Apr 26 10:25:13 192.168.122.209 [66063.655182] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:25:14 192.168.122.209 [66065.136077] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66065.136077] Maybe that's fine, but it's worth checking the [66065.136077] config - if there is no relations between the [66065.136077] names, then host name confusion attack is possible. Apr 26 10:25:14 192.168.122.209 [66065.254847] [tempesta fw] Configuration processing is completed. Apr 26 10:25:14 192.168.122.209 [66065.312050] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:25:15 192.168.122.209 [66065.727895] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:25:15 192.168.122.209 [66065.755459] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:25:15 192.168.122.209 [66065.781303] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:25:15 192.168.122.209 [66065.822799] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:25:15 192.168.122.209 [66065.824492] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:25:15 192.168.122.209 [66065.870733] [tempesta fw] Tempesta FW is ready Apr 26 10:25:15 192.168.122.209 [66066.525139] [tdb] Close table 'client0.tdb' Apr 26 10:25:16 192.168.122.209 [66066.710906] [tdb] Close table 'sessions0.tdb' Apr 26 10:25:19 192.168.122.209 [66069.879967] [tdb] Close table 'cache0.tdb' Apr 26 10:25:19 192.168.122.209 [66070.121241] [tdb] Close table 'filter0.tdb' Apr 26 10:25:19 192.168.122.209 [66070.121669] [tempesta fw] modules are stopped Apr 26 10:25:19 192.168.122.209 [66070.348018] [tempesta fw] exiting... Apr 26 10:25:19 192.168.122.209 [66070.452343] [tdb] Shutdown Tempesta DB Apr 26 10:25:20 192.168.122.209 [66070.649467] End test: t_modify_http_headers.test_common_config_h2.TestReqSetHeaderH2.test_add_hdrs_override_config Apr 26 10:25:20 192.168.122.209 [66070.677041] Start test: t_modify_http_headers.test_common_config_h2.TestReqSetHeaderH2.test_add_some_hdrs Apr 26 10:25:21 192.168.122.209 [66071.760980] [tdb] Start Tempesta DB Apr 26 10:25:21 192.168.122.209 [66071.901816] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:25:22 192.168.122.209 [66073.368190] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66073.368190] Maybe that's fine, but it's worth checking the [66073.368190] config - if there is no relations between the [66073.368190] names, then host name confusion attack is possible. Apr 26 10:25:22 192.168.122.209 [66073.494946] [tempesta fw] Configuration processing is completed. Apr 26 10:25:22 192.168.122.209 [66073.556869] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:25:23 192.168.122.209 [66073.985015] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:25:23 192.168.122.209 [66074.022851] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:25:23 192.168.122.209 [66074.048823] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:25:23 192.168.122.209 [66074.090896] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:25:23 192.168.122.209 [66074.092649] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:25:23 192.168.122.209 [66074.134841] [tempesta fw] Tempesta FW is ready Apr 26 10:25:24 192.168.122.209 [66074.733150] [tdb] Close table 'client0.tdb' Apr 26 10:25:24 192.168.122.209 [66074.922242] [tdb] Close table 'sessions0.tdb' Apr 26 10:25:27 192.168.122.209 [66078.056338] [tdb] Close table 'cache0.tdb' Apr 26 10:25:27 192.168.122.209 [66078.269401] [tdb] Close table 'filter0.tdb' Apr 26 10:25:27 192.168.122.209 [66078.269817] [tempesta fw] modules are stopped Apr 26 10:25:27 192.168.122.209 [66078.481684] [tempesta fw] exiting... Apr 26 10:25:27 192.168.122.209 [66078.613596] [tdb] Shutdown Tempesta DB Apr 26 10:25:28 192.168.122.209 [66078.835995] End test: t_modify_http_headers.test_common_config_h2.TestReqSetHeaderH2.test_add_some_hdrs Apr 26 10:25:28 192.168.122.209 [66078.857641] Start test: t_modify_http_headers.test_common_config_h2.TestReqSetHeaderH2.test_add_some_hdrs_custom_location Apr 26 10:25:29 192.168.122.209 [66079.880182] [tdb] Start Tempesta DB Apr 26 10:25:29 192.168.122.209 [66080.011500] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:25:30 192.168.122.209 [66081.424247] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66081.424247] Maybe that's fine, but it's worth checking the [66081.424247] config - if there is no relations between the [66081.424247] names, then host name confusion attack is possible. Apr 26 10:25:30 192.168.122.209 [66081.547437] [tempesta fw] Configuration processing is completed. Apr 26 10:25:30 192.168.122.209 [66081.600120] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:25:31 192.168.122.209 [66082.011074] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:25:31 192.168.122.209 [66082.046054] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:25:31 192.168.122.209 [66082.072951] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:25:31 192.168.122.209 [66082.111021] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:25:31 192.168.122.209 [66082.112734] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:25:31 192.168.122.209 [66082.150961] [tempesta fw] Tempesta FW is ready Apr 26 10:25:32 192.168.122.209 [66082.776820] [tdb] Close table 'client0.tdb' Apr 26 10:25:32 192.168.122.209 [66082.964799] [tdb] Close table 'sessions0.tdb' Apr 26 10:25:35 192.168.122.209 [66086.107626] [tdb] Close table 'cache0.tdb' Apr 26 10:25:35 192.168.122.209 [66086.346734] [tdb] Close table 'filter0.tdb' Apr 26 10:25:35 192.168.122.209 [66086.347163] [tempesta fw] modules are stopped Apr 26 10:25:35 192.168.122.209 [66086.549471] [tempesta fw] exiting... Apr 26 10:25:36 192.168.122.209 [66086.682531] [tdb] Shutdown Tempesta DB Apr 26 10:25:36 192.168.122.209 [66086.918571] End test: t_modify_http_headers.test_common_config_h2.TestReqSetHeaderH2.test_add_some_hdrs_custom_location Apr 26 10:25:36 192.168.122.209 [66086.928525] Start test: t_modify_http_headers.test_common_config_h2.TestRespAddHeaderH2.test_add_hdrs_derive_config Apr 26 10:25:37 192.168.122.209 [66087.976506] [tdb] Start Tempesta DB Apr 26 10:25:37 192.168.122.209 [66088.112184] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:25:38 192.168.122.209 [66089.468339] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66089.468339] Maybe that's fine, but it's worth checking the [66089.468339] config - if there is no relations between the [66089.468339] names, then host name confusion attack is possible. Apr 26 10:25:38 192.168.122.209 [66089.591125] [tempesta fw] Configuration processing is completed. Apr 26 10:25:39 192.168.122.209 [66089.655033] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:25:39 192.168.122.209 [66090.068050] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:25:39 192.168.122.209 [66090.093373] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:25:39 192.168.122.209 [66090.119120] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:25:39 192.168.122.209 [66090.159101] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:25:39 192.168.122.209 [66090.160837] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:25:39 192.168.122.209 [66090.207039] [tempesta fw] Tempesta FW is ready Apr 26 10:25:40 192.168.122.209 [66090.846885] [tdb] Close table 'client0.tdb' Apr 26 10:25:40 192.168.122.209 [66091.035274] [tdb] Close table 'sessions0.tdb' Apr 26 10:25:43 192.168.122.209 [66094.246435] [tdb] Close table 'cache0.tdb' Apr 26 10:25:43 192.168.122.209 [66094.487176] [tdb] Close table 'filter0.tdb' Apr 26 10:25:43 192.168.122.209 [66094.487610] [tempesta fw] modules are stopped Apr 26 10:25:44 192.168.122.209 [66094.695766] [tempesta fw] exiting... Apr 26 10:25:44 192.168.122.209 [66094.841212] [tdb] Shutdown Tempesta DB Apr 26 10:25:44 192.168.122.209 [66095.066161] End test: t_modify_http_headers.test_common_config_h2.TestRespAddHeaderH2.test_add_hdrs_derive_config Apr 26 10:25:44 192.168.122.209 [66095.079372] Start test: t_modify_http_headers.test_common_config_h2.TestRespAddHeaderH2.test_add_hdrs_override_config Apr 26 10:25:45 192.168.122.209 [66096.126632] [tdb] Start Tempesta DB Apr 26 10:25:45 192.168.122.209 [66096.270816] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:25:47 192.168.122.209 [66097.732461] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66097.732461] Maybe that's fine, but it's worth checking the [66097.732461] config - if there is no relations between the [66097.732461] names, then host name confusion attack is possible. Apr 26 10:25:47 192.168.122.209 [66097.851241] [tempesta fw] Configuration processing is completed. Apr 26 10:25:47 192.168.122.209 [66097.911421] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:25:47 192.168.122.209 [66098.332495] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:25:47 192.168.122.209 [66098.359190] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:25:47 192.168.122.209 [66098.395282] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:25:47 192.168.122.209 [66098.435213] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:25:47 192.168.122.209 [66098.436941] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:25:47 192.168.122.209 [66098.479150] [tempesta fw] Tempesta FW is ready Apr 26 10:25:48 192.168.122.209 [66099.086426] [tdb] Close table 'client0.tdb' Apr 26 10:25:48 192.168.122.209 [66099.300208] [tdb] Close table 'sessions0.tdb' Apr 26 10:25:51 192.168.122.209 [66102.433516] [tdb] Close table 'cache0.tdb' Apr 26 10:25:52 192.168.122.209 [66102.690576] [tdb] Close table 'filter0.tdb' Apr 26 10:25:52 192.168.122.209 [66102.691005] [tempesta fw] modules are stopped Apr 26 10:25:52 192.168.122.209 [66102.875631] [tempesta fw] exiting... Apr 26 10:25:52 192.168.122.209 [66102.978433] [tdb] Shutdown Tempesta DB Apr 26 10:25:52 192.168.122.209 [66103.196498] End test: t_modify_http_headers.test_common_config_h2.TestRespAddHeaderH2.test_add_hdrs_override_config Apr 26 10:25:52 192.168.122.209 [66103.217387] Start test: t_modify_http_headers.test_common_config_h2.TestRespAddHeaderH2.test_add_some_hdrs Apr 26 10:25:53 192.168.122.209 [66104.278755] [tdb] Start Tempesta DB Apr 26 10:25:53 192.168.122.209 [66104.417121] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:25:55 192.168.122.209 [66105.788539] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66105.788539] Maybe that's fine, but it's worth checking the [66105.788539] config - if there is no relations between the [66105.788539] names, then host name confusion attack is possible. Apr 26 10:25:55 192.168.122.209 [66105.907281] [tempesta fw] Configuration processing is completed. Apr 26 10:25:55 192.168.122.209 [66105.963753] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:25:55 192.168.122.209 [66106.378401] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:25:55 192.168.122.209 [66106.406103] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:25:55 192.168.122.209 [66106.432913] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:25:55 192.168.122.209 [66106.479303] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:25:55 192.168.122.209 [66106.481043] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:25:55 192.168.122.209 [66106.527198] [tempesta fw] Tempesta FW is ready Apr 26 10:25:56 192.168.122.209 [66107.140754] [tdb] Close table 'client0.tdb' Apr 26 10:25:56 192.168.122.209 [66107.347503] [tdb] Close table 'sessions0.tdb' Apr 26 10:25:59 192.168.122.209 [66110.557844] [tdb] Close table 'cache0.tdb' Apr 26 10:26:00 192.168.122.209 [66110.802494] [tdb] Close table 'filter0.tdb' Apr 26 10:26:00 192.168.122.209 [66110.803307] [tempesta fw] modules are stopped Apr 26 10:26:00 192.168.122.209 [66110.999517] [tempesta fw] exiting... Apr 26 10:26:00 192.168.122.209 [66111.122216] [tdb] Shutdown Tempesta DB Apr 26 10:26:00 192.168.122.209 [66111.359525] End test: t_modify_http_headers.test_common_config_h2.TestRespAddHeaderH2.test_add_some_hdrs Apr 26 10:26:00 192.168.122.209 [66111.376977] Start test: t_modify_http_headers.test_common_config_h2.TestRespAddHeaderH2.test_add_some_hdrs_custom_location Apr 26 10:26:01 192.168.122.209 [66112.407249] [tdb] Start Tempesta DB Apr 26 10:26:01 192.168.122.209 [66112.539424] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:26:03 192.168.122.209 [66113.972652] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66113.972652] Maybe that's fine, but it's worth checking the [66113.972652] config - if there is no relations between the [66113.972652] names, then host name confusion attack is possible. Apr 26 10:26:03 192.168.122.209 [66114.071455] [tempesta fw] Configuration processing is completed. Apr 26 10:26:03 192.168.122.209 [66114.123219] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:26:03 192.168.122.209 [66114.542545] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:26:03 192.168.122.209 [66114.569001] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:26:03 192.168.122.209 [66114.595041] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:26:04 192.168.122.209 [66114.647427] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:26:04 192.168.122.209 [66114.649182] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:26:04 192.168.122.209 [66114.695400] [tempesta fw] Tempesta FW is ready Apr 26 10:26:04 192.168.122.209 [66115.330779] [tdb] Close table 'client0.tdb' Apr 26 10:26:04 192.168.122.209 [66115.531962] [tdb] Close table 'sessions0.tdb' Apr 26 10:26:08 192.168.122.209 [66118.676404] [tdb] Close table 'cache0.tdb' Apr 26 10:26:08 192.168.122.209 [66118.904593] [tdb] Close table 'filter0.tdb' Apr 26 10:26:08 192.168.122.209 [66118.905030] [tempesta fw] modules are stopped Apr 26 10:26:08 192.168.122.209 [66119.108800] [tempesta fw] exiting... Apr 26 10:26:08 192.168.122.209 [66119.253274] [tdb] Shutdown Tempesta DB Apr 26 10:26:08 192.168.122.209 [66119.475895] End test: t_modify_http_headers.test_common_config_h2.TestRespAddHeaderH2.test_add_some_hdrs_custom_location Apr 26 10:26:08 192.168.122.209 [66119.485522] Start test: t_modify_http_headers.test_common_config_h2.TestRespSetHeaderH2.test_add_hdrs_derive_config Apr 26 10:26:09 192.168.122.209 [66120.505557] [tdb] Start Tempesta DB Apr 26 10:26:09 192.168.122.209 [66120.627765] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:26:11 192.168.122.209 [66122.104728] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66122.104728] Maybe that's fine, but it's worth checking the [66122.104728] config - if there is no relations between the [66122.104728] names, then host name confusion attack is possible. Apr 26 10:26:11 192.168.122.209 [66122.231521] [tempesta fw] Configuration processing is completed. Apr 26 10:26:11 192.168.122.209 [66122.287552] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:26:12 192.168.122.209 [66122.694691] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:26:12 192.168.122.209 [66122.728985] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:26:12 192.168.122.209 [66122.755291] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:26:12 192.168.122.209 [66122.799494] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:26:12 192.168.122.209 [66122.801241] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:26:12 192.168.122.209 [66122.851457] [tempesta fw] Tempesta FW is ready Apr 26 10:26:12 192.168.122.209 [66123.482280] [tdb] Close table 'client0.tdb' Apr 26 10:26:13 192.168.122.209 [66123.688988] [tdb] Close table 'sessions0.tdb' Apr 26 10:26:16 192.168.122.209 [66126.855128] [tdb] Close table 'cache0.tdb' Apr 26 10:26:16 192.168.122.209 [66127.089234] [tdb] Close table 'filter0.tdb' Apr 26 10:26:16 192.168.122.209 [66127.089680] [tempesta fw] modules are stopped Apr 26 10:26:16 192.168.122.209 [66127.273800] [tempesta fw] exiting... Apr 26 10:26:16 192.168.122.209 [66127.417773] [tdb] Shutdown Tempesta DB Apr 26 10:26:16 192.168.122.209 [66127.614571] End test: t_modify_http_headers.test_common_config_h2.TestRespSetHeaderH2.test_add_hdrs_derive_config Apr 26 10:26:16 192.168.122.209 [66127.628085] Start test: t_modify_http_headers.test_common_config_h2.TestRespSetHeaderH2.test_add_hdrs_override_config Apr 26 10:26:17 192.168.122.209 [66128.626578] [tdb] Start Tempesta DB Apr 26 10:26:18 192.168.122.209 [66128.763061] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:26:19 192.168.122.209 [66130.272852] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66130.272852] Maybe that's fine, but it's worth checking the [66130.272852] config - if there is no relations between the [66130.272852] names, then host name confusion attack is possible. Apr 26 10:26:19 192.168.122.209 [66130.403684] [tempesta fw] Configuration processing is completed. Apr 26 10:26:19 192.168.122.209 [66130.460422] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:26:20 192.168.122.209 [66130.885988] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:26:20 192.168.122.209 [66130.911781] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:26:20 192.168.122.209 [66130.937097] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:26:20 192.168.122.209 [66130.979644] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:26:20 192.168.122.209 [66130.981380] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:26:20 192.168.122.209 [66131.023548] [tempesta fw] Tempesta FW is ready Apr 26 10:26:20 192.168.122.209 [66131.631214] [tdb] Close table 'client0.tdb' Apr 26 10:26:21 192.168.122.209 [66131.831336] [tdb] Close table 'sessions0.tdb' Apr 26 10:26:24 192.168.122.209 [66135.019819] [tdb] Close table 'cache0.tdb' Apr 26 10:26:24 192.168.122.209 [66135.253616] [tdb] Close table 'filter0.tdb' Apr 26 10:26:24 192.168.122.209 [66135.254031] [tempesta fw] modules are stopped Apr 26 10:26:24 192.168.122.209 [66135.431649] [tempesta fw] exiting... Apr 26 10:26:24 192.168.122.209 [66135.565068] [tdb] Shutdown Tempesta DB Apr 26 10:26:25 192.168.122.209 [66135.808365] End test: t_modify_http_headers.test_common_config_h2.TestRespSetHeaderH2.test_add_hdrs_override_config Apr 26 10:26:25 192.168.122.209 [66135.822407] Start test: t_modify_http_headers.test_common_config_h2.TestRespSetHeaderH2.test_add_some_hdrs Apr 26 10:26:26 192.168.122.209 [66136.858441] [tdb] Start Tempesta DB Apr 26 10:26:26 192.168.122.209 [66136.998369] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:26:27 192.168.122.209 [66138.364964] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66138.364964] Maybe that's fine, but it's worth checking the [66138.364964] config - if there is no relations between the [66138.364964] names, then host name confusion attack is possible. Apr 26 10:26:27 192.168.122.209 [66138.499746] [tempesta fw] Configuration processing is completed. Apr 26 10:26:27 192.168.122.209 [66138.565096] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:26:28 192.168.122.209 [66138.986941] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:26:28 192.168.122.209 [66139.013804] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:26:28 192.168.122.209 [66139.040033] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:26:28 192.168.122.209 [66139.087605] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:26:28 192.168.122.209 [66139.089313] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:26:28 192.168.122.209 [66139.139655] [tempesta fw] Tempesta FW is ready Apr 26 10:26:29 192.168.122.209 [66139.739326] [tdb] Close table 'client0.tdb' Apr 26 10:26:29 192.168.122.209 [66139.935242] [tdb] Close table 'sessions0.tdb' Apr 26 10:26:32 192.168.122.209 [66143.084140] [tdb] Close table 'cache0.tdb' Apr 26 10:26:32 192.168.122.209 [66143.297667] [tdb] Close table 'filter0.tdb' Apr 26 10:26:32 192.168.122.209 [66143.298094] [tempesta fw] modules are stopped Apr 26 10:26:32 192.168.122.209 [66143.508504] [tempesta fw] exiting... Apr 26 10:26:32 192.168.122.209 [66143.620859] [tdb] Shutdown Tempesta DB Apr 26 10:26:33 192.168.122.209 [66143.825842] End test: t_modify_http_headers.test_common_config_h2.TestRespSetHeaderH2.test_add_some_hdrs Apr 26 10:26:33 192.168.122.209 [66143.838397] Start test: t_modify_http_headers.test_common_config_h2.TestRespSetHeaderH2.test_add_some_hdrs_custom_location Apr 26 10:26:34 192.168.122.209 [66144.902251] [tdb] Start Tempesta DB Apr 26 10:26:34 192.168.122.209 [66145.030512] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:26:35 192.168.122.209 [66146.413028] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66146.413028] Maybe that's fine, but it's worth checking the [66146.413028] config - if there is no relations between the [66146.413028] names, then host name confusion attack is possible. Apr 26 10:26:35 192.168.122.209 [66146.515826] [tempesta fw] Configuration processing is completed. Apr 26 10:26:35 192.168.122.209 [66146.567814] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:26:36 192.168.122.209 [66146.979882] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:26:36 192.168.122.209 [66147.005992] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:26:36 192.168.122.209 [66147.032981] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:26:36 192.168.122.209 [66147.087800] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:26:36 192.168.122.209 [66147.089527] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:26:36 192.168.122.209 [66147.131775] [tempesta fw] Tempesta FW is ready Apr 26 10:26:37 192.168.122.209 [66147.770221] [tdb] Close table 'client0.tdb' Apr 26 10:26:37 192.168.122.209 [66147.961788] [tdb] Close table 'sessions0.tdb' Apr 26 10:26:40 192.168.122.209 [66151.147370] [tdb] Close table 'cache0.tdb' Apr 26 10:26:40 192.168.122.209 [66151.385314] [tdb] Close table 'filter0.tdb' Apr 26 10:26:40 192.168.122.209 [66151.385730] [tempesta fw] modules are stopped Apr 26 10:26:40 192.168.122.209 [66151.611477] [tempesta fw] exiting... Apr 26 10:26:41 192.168.122.209 [66151.733808] [tdb] Shutdown Tempesta DB Apr 26 10:26:41 192.168.122.209 [66151.937127] End test: t_modify_http_headers.test_common_config_h2.TestRespSetHeaderH2.test_add_some_hdrs_custom_location Apr 26 10:26:41 192.168.122.209 [66151.961777] Start test: t_modify_http_headers.test_logic.TestCachedRespHeader.test_add_non_exist_header Apr 26 10:26:42 192.168.122.209 [66152.947419] [tdb] Start Tempesta DB Apr 26 10:26:42 192.168.122.209 [66153.094130] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:26:43 192.168.122.209 [66154.445211] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66154.445211] Maybe that's fine, but it's worth checking the [66154.445211] config - if there is no relations between the [66154.445211] names, then host name confusion attack is possible. Apr 26 10:26:43 192.168.122.209 [66154.583920] [tempesta fw] Configuration processing is completed. Apr 26 10:26:44 192.168.122.209 [66154.644515] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:26:44 192.168.122.209 [66155.082656] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:26:44 192.168.122.209 [66155.108789] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:26:44 192.168.122.209 [66155.134536] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:26:44 192.168.122.209 [66155.183888] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:26:44 192.168.122.209 [66155.185616] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:26:44 192.168.122.209 [66155.223848] [tempesta fw] Tempesta FW is ready Apr 26 10:26:45 192.168.122.209 [66155.811016] [tdb] Close table 'client0.tdb' Apr 26 10:26:45 192.168.122.209 [66156.011362] [tdb] Close table 'sessions0.tdb' Apr 26 10:26:48 192.168.122.209 [66159.196897] [tdb] Close table 'cache0.tdb' Apr 26 10:26:48 192.168.122.209 [66159.460036] [tdb] Close table 'filter0.tdb' Apr 26 10:26:48 192.168.122.209 [66159.460447] [tempesta fw] modules are stopped Apr 26 10:26:49 192.168.122.209 [66159.644718] [tempesta fw] exiting... Apr 26 10:26:49 192.168.122.209 [66159.768335] [tdb] Shutdown Tempesta DB Apr 26 10:26:49 192.168.122.209 [66159.960184] End test: t_modify_http_headers.test_logic.TestCachedRespHeader.test_add_non_exist_header Apr 26 10:26:49 192.168.122.209 [66159.993348] Start test: t_modify_http_headers.test_logic.TestCachedRespHeader.test_delete_headers Apr 26 10:26:50 192.168.122.209 [66161.016338] [tdb] Start Tempesta DB Apr 26 10:26:50 192.168.122.209 [66161.145180] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:26:51 192.168.122.209 [66162.621285] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66162.621285] Maybe that's fine, but it's worth checking the [66162.621285] config - if there is no relations between the [66162.621285] names, then host name confusion attack is possible. Apr 26 10:26:52 192.168.122.209 [66162.768024] [tempesta fw] Configuration processing is completed. Apr 26 10:26:52 192.168.122.209 [66162.832875] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:26:52 192.168.122.209 [66163.251443] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:26:52 192.168.122.209 [66163.277047] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:26:52 192.168.122.209 [66163.303225] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:26:52 192.168.122.209 [66163.348013] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:26:52 192.168.122.209 [66163.349755] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:26:52 192.168.122.209 [66163.391954] [tempesta fw] Tempesta FW is ready Apr 26 10:26:53 192.168.122.209 [66164.025605] [tdb] Close table 'client0.tdb' Apr 26 10:26:53 192.168.122.209 [66164.206593] [tdb] Close table 'sessions0.tdb' Apr 26 10:26:56 192.168.122.209 [66167.459333] [tdb] Close table 'cache0.tdb' Apr 26 10:26:57 192.168.122.209 [66167.698196] [tdb] Close table 'filter0.tdb' Apr 26 10:26:57 192.168.122.209 [66167.698651] [tempesta fw] modules are stopped Apr 26 10:26:57 192.168.122.209 [66167.924953] [tempesta fw] exiting... Apr 26 10:26:57 192.168.122.209 [66168.084795] [tdb] Shutdown Tempesta DB Apr 26 10:26:57 192.168.122.209 [66168.306444] End test: t_modify_http_headers.test_logic.TestCachedRespHeader.test_delete_headers Apr 26 10:26:57 192.168.122.209 [66168.329708] Start test: t_modify_http_headers.test_logic.TestCachedRespHeader.test_delete_many_headers Apr 26 10:26:58 192.168.122.209 [66169.333984] [tdb] Start Tempesta DB Apr 26 10:26:58 192.168.122.209 [66169.468314] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:27:00 192.168.122.209 [66170.865371] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66170.865371] Maybe that's fine, but it's worth checking the [66170.865371] config - if there is no relations between the [66170.865371] names, then host name confusion attack is possible. Apr 26 10:27:00 192.168.122.209 [66170.996134] [tempesta fw] Configuration processing is completed. Apr 26 10:27:00 192.168.122.209 [66171.060755] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:27:00 192.168.122.209 [66171.489390] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:27:00 192.168.122.209 [66171.515629] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:27:00 192.168.122.209 [66171.542186] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:27:00 192.168.122.209 [66171.580041] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:27:00 192.168.122.209 [66171.581772] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:27:00 192.168.122.209 [66171.620054] [tempesta fw] Tempesta FW is ready Apr 26 10:27:01 192.168.122.209 [66172.213982] [tdb] Close table 'client0.tdb' Apr 26 10:27:01 192.168.122.209 [66172.401706] [tdb] Close table 'sessions0.tdb' Apr 26 10:27:04 192.168.122.209 [66175.529768] [tdb] Close table 'cache0.tdb' Apr 26 10:27:05 192.168.122.209 [66175.752837] [tdb] Close table 'filter0.tdb' Apr 26 10:27:05 192.168.122.209 [66175.753274] [tempesta fw] modules are stopped Apr 26 10:27:05 192.168.122.209 [66175.960645] [tempesta fw] exiting... Apr 26 10:27:05 192.168.122.209 [66176.108764] [tdb] Shutdown Tempesta DB Apr 26 10:27:05 192.168.122.209 [66176.313633] End test: t_modify_http_headers.test_logic.TestCachedRespHeader.test_delete_many_headers Apr 26 10:27:05 192.168.122.209 [66176.327185] Start test: t_modify_http_headers.test_logic.TestCachedRespHeader.test_delete_many_special_headers Apr 26 10:27:06 192.168.122.209 [66177.344961] [tdb] Start Tempesta DB Apr 26 10:27:06 192.168.122.209 [66177.472491] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:27:08 192.168.122.209 [66178.833483] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66178.833483] Maybe that's fine, but it's worth checking the [66178.833483] config - if there is no relations between the [66178.833483] names, then host name confusion attack is possible. Apr 26 10:27:08 192.168.122.209 [66178.972234] [tempesta fw] Configuration processing is completed. Apr 26 10:27:08 192.168.122.209 [66179.028096] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:27:08 192.168.122.209 [66179.443362] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:27:08 192.168.122.209 [66179.468909] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:27:08 192.168.122.209 [66179.495145] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:27:08 192.168.122.209 [66179.540203] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:27:08 192.168.122.209 [66179.541948] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:27:08 192.168.122.209 [66179.592133] [tempesta fw] Tempesta FW is ready Apr 26 10:27:09 192.168.122.209 [66180.184463] [tdb] Close table 'client0.tdb' Apr 26 10:27:09 192.168.122.209 [66180.379978] [tdb] Close table 'sessions0.tdb' Apr 26 10:27:12 192.168.122.209 [66183.542473] [tdb] Close table 'cache0.tdb' Apr 26 10:27:13 192.168.122.209 [66183.790629] [tdb] Close table 'filter0.tdb' Apr 26 10:27:13 192.168.122.209 [66183.791077] [tempesta fw] modules are stopped Apr 26 10:27:13 192.168.122.209 [66184.025709] [tempesta fw] exiting... Apr 26 10:27:13 192.168.122.209 [66184.142933] [tdb] Shutdown Tempesta DB Apr 26 10:27:13 192.168.122.209 [66184.358259] End test: t_modify_http_headers.test_logic.TestCachedRespHeader.test_delete_many_special_headers Apr 26 10:27:13 192.168.122.209 [66184.383374] Start test: t_modify_http_headers.test_logic.TestCachedRespHeader.test_delete_non_exist_header Apr 26 10:27:14 192.168.122.209 [66185.434776] [tdb] Start Tempesta DB Apr 26 10:27:14 192.168.122.209 [66185.578917] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:27:16 192.168.122.209 [66186.993586] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66186.993586] Maybe that's fine, but it's worth checking the [66186.993586] config - if there is no relations between the [66186.993586] names, then host name confusion attack is possible. Apr 26 10:27:16 192.168.122.209 [66187.128340] [tempesta fw] Configuration processing is completed. Apr 26 10:27:16 192.168.122.209 [66187.184994] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:27:16 192.168.122.209 [66187.612759] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:27:17 192.168.122.209 [66187.638818] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:27:17 192.168.122.209 [66187.664070] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:27:17 192.168.122.209 [66187.704300] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:27:17 192.168.122.209 [66187.706069] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:27:17 192.168.122.209 [66187.744236] [tempesta fw] Tempesta FW is ready Apr 26 10:27:17 192.168.122.209 [66188.326436] [tdb] Close table 'client0.tdb' Apr 26 10:27:17 192.168.122.209 [66188.522589] [tdb] Close table 'sessions0.tdb' Apr 26 10:27:21 192.168.122.209 [66191.750104] [tdb] Close table 'cache0.tdb' Apr 26 10:27:21 192.168.122.209 [66192.019108] [tdb] Close table 'filter0.tdb' Apr 26 10:27:21 192.168.122.209 [66192.019558] [tempesta fw] modules are stopped Apr 26 10:27:21 192.168.122.209 [66192.280229] [tempesta fw] exiting... Apr 26 10:27:21 192.168.122.209 [66192.381372] [tdb] Shutdown Tempesta DB Apr 26 10:27:21 192.168.122.209 [66192.595899] End test: t_modify_http_headers.test_logic.TestCachedRespHeader.test_delete_non_exist_header Apr 26 10:27:21 192.168.122.209 [66192.610165] Start test: t_modify_http_headers.test_logic.TestCachedRespHeader.test_delete_special_headers Apr 26 10:27:23 192.168.122.209 [66193.690350] [tdb] Start Tempesta DB Apr 26 10:27:23 192.168.122.209 [66193.833792] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:27:24 192.168.122.209 [66195.265770] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66195.265770] Maybe that's fine, but it's worth checking the [66195.265770] config - if there is no relations between the [66195.265770] names, then host name confusion attack is possible. Apr 26 10:27:24 192.168.122.209 [66195.396465] [tempesta fw] Configuration processing is completed. Apr 26 10:27:24 192.168.122.209 [66195.455375] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:27:25 192.168.122.209 [66195.918385] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:27:25 192.168.122.209 [66195.948839] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:27:25 192.168.122.209 [66195.977660] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:27:25 192.168.122.209 [66196.020387] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:27:25 192.168.122.209 [66196.022121] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:27:25 192.168.122.209 [66196.064340] [tempesta fw] Tempesta FW is ready Apr 26 10:27:25 192.168.122.209 [66196.625360] [tdb] Close table 'client0.tdb' Apr 26 10:27:26 192.168.122.209 [66196.817847] [tdb] Close table 'sessions0.tdb' Apr 26 10:27:29 192.168.122.209 [66200.078921] [tdb] Close table 'cache0.tdb' Apr 26 10:27:29 192.168.122.209 [66200.326093] [tdb] Close table 'filter0.tdb' Apr 26 10:27:29 192.168.122.209 [66200.326521] [tempesta fw] modules are stopped Apr 26 10:27:29 192.168.122.209 [66200.531277] [tempesta fw] exiting... Apr 26 10:27:29 192.168.122.209 [66200.629387] [tdb] Shutdown Tempesta DB Apr 26 10:27:30 192.168.122.209 [66200.850851] End test: t_modify_http_headers.test_logic.TestCachedRespHeader.test_delete_special_headers Apr 26 10:27:30 192.168.122.209 [66200.871008] Start test: t_modify_http_headers.test_logic.TestCachedRespHeader.test_long_header_name Apr 26 10:27:31 192.168.122.209 [66201.890713] [tdb] Start Tempesta DB Apr 26 10:27:31 192.168.122.209 [66202.053473] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:27:32 192.168.122.209 [66203.581787] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66203.581787] Maybe that's fine, but it's worth checking the [66203.581787] config - if there is no relations between the [66203.581787] names, then host name confusion attack is possible. Apr 26 10:27:33 192.168.122.209 [66203.720622] [tempesta fw] Configuration processing is completed. Apr 26 10:27:33 192.168.122.209 [66203.775226] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:27:33 192.168.122.209 [66204.285959] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:27:33 192.168.122.209 [66204.319787] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:27:33 192.168.122.209 [66204.351629] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:27:33 192.168.122.209 [66204.404529] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:27:33 192.168.122.209 [66204.406274] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:27:33 192.168.122.209 [66204.448413] [tempesta fw] Tempesta FW is ready Apr 26 10:27:36 192.168.122.209 [66206.932762] [tdb] Close table 'client0.tdb' Apr 26 10:27:36 192.168.122.209 [66207.130856] [tdb] Close table 'sessions0.tdb' Apr 26 10:27:39 192.168.122.209 [66210.419472] [tdb] Close table 'cache0.tdb' Apr 26 10:27:40 192.168.122.209 [66210.686070] [tdb] Close table 'filter0.tdb' Apr 26 10:27:40 192.168.122.209 [66210.686517] [tempesta fw] modules are stopped Apr 26 10:27:40 192.168.122.209 [66210.868961] [tempesta fw] exiting... Apr 26 10:27:40 192.168.122.209 [66211.010507] [tdb] Shutdown Tempesta DB Apr 26 10:27:40 192.168.122.209 [66211.197551] End test: t_modify_http_headers.test_logic.TestCachedRespHeader.test_long_header_name Apr 26 10:27:40 192.168.122.209 [66211.208052] Start test: t_modify_http_headers.test_logic.TestCachedRespHeader.test_set_exist_header Apr 26 10:27:41 192.168.122.209 [66212.245108] [tdb] Start Tempesta DB Apr 26 10:27:41 192.168.122.209 [66212.380044] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:27:43 192.168.122.209 [66213.877957] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66213.877957] Maybe that's fine, but it's worth checking the [66213.877957] config - if there is no relations between the [66213.877957] names, then host name confusion attack is possible. Apr 26 10:27:43 192.168.122.209 [66214.012654] [tempesta fw] Configuration processing is completed. Apr 26 10:27:43 192.168.122.209 [66214.075830] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:27:43 192.168.122.209 [66214.621310] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:27:44 192.168.122.209 [66214.654661] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:27:44 192.168.122.209 [66214.688486] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:27:44 192.168.122.209 [66214.740638] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:27:44 192.168.122.209 [66214.742372] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:27:44 192.168.122.209 [66214.788580] [tempesta fw] Tempesta FW is ready Apr 26 10:27:45 192.168.122.209 [66216.036535] [tdb] Close table 'client0.tdb' Apr 26 10:27:45 192.168.122.209 [66216.341698] [tdb] Close table 'sessions0.tdb' Apr 26 10:27:50 192.168.122.209 [66221.406249] [tdb] Close table 'cache0.tdb' Apr 26 10:27:51 192.168.122.209 [66221.872016] [tdb] Close table 'filter0.tdb' Apr 26 10:27:51 192.168.122.209 [66221.872471] [tempesta fw] modules are stopped Apr 26 10:27:51 192.168.122.209 [66222.341692] [tempesta fw] exiting... Apr 26 10:27:51 192.168.122.209 [66222.459256] [tdb] Shutdown Tempesta DB Apr 26 10:27:52 192.168.122.209 [66222.692642] End test: t_modify_http_headers.test_logic.TestCachedRespHeader.test_set_exist_header Apr 26 10:27:52 192.168.122.209 [66222.703516] Start test: t_modify_http_headers.test_logic.TestCachedRespHeader.test_set_exist_special_header Apr 26 10:27:53 192.168.122.209 [66223.874337] [tdb] Start Tempesta DB Apr 26 10:27:53 192.168.122.209 [66224.030299] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:27:54 192.168.122.209 [66225.518173] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66225.518173] Maybe that's fine, but it's worth checking the [66225.518173] config - if there is no relations between the [66225.518173] names, then host name confusion attack is possible. Apr 26 10:27:55 192.168.122.209 [66225.656831] [tempesta fw] Configuration processing is completed. Apr 26 10:27:55 192.168.122.209 [66225.716735] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:27:55 192.168.122.209 [66226.151726] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:27:55 192.168.122.209 [66226.179220] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:27:55 192.168.122.209 [66226.207087] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:27:55 192.168.122.209 [66226.252780] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:27:55 192.168.122.209 [66226.254568] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:27:55 192.168.122.209 [66226.292718] [tempesta fw] Tempesta FW is ready Apr 26 10:27:56 192.168.122.209 [66226.881239] [tdb] Close table 'client0.tdb' Apr 26 10:27:56 192.168.122.209 [66227.073883] [tdb] Close table 'sessions0.tdb' Apr 26 10:27:59 192.168.122.209 [66230.324617] [tdb] Close table 'cache0.tdb' Apr 26 10:27:59 192.168.122.209 [66230.554082] [tdb] Close table 'filter0.tdb' Apr 26 10:27:59 192.168.122.209 [66230.554488] [tempesta fw] modules are stopped Apr 26 10:28:00 192.168.122.209 [66230.801598] [tempesta fw] exiting... Apr 26 10:28:00 192.168.122.209 [66230.919039] [tdb] Shutdown Tempesta DB Apr 26 10:28:00 192.168.122.209 [66231.120466] End test: t_modify_http_headers.test_logic.TestCachedRespHeader.test_set_exist_special_header Apr 26 10:28:00 192.168.122.209 [66231.136476] Start test: t_modify_http_headers.test_logic.TestCachedRespHeader.test_set_header_name_greater_than_1024 Apr 26 10:28:01 192.168.122.209 [66232.516838] [tdb] Start Tempesta DB Apr 26 10:28:02 192.168.122.209 [66232.642049] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:28:03 192.168.122.209 [66234.218132] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66234.218132] Maybe that's fine, but it's worth checking the [66234.218132] config - if there is no relations between the [66234.218132] names, then host name confusion attack is possible. Apr 26 10:28:03 192.168.122.209 [66234.348900] [tempesta fw] Configuration processing is completed. Apr 26 10:28:03 192.168.122.209 [66234.410392] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:28:04 192.168.122.209 [66234.836731] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:28:04 192.168.122.209 [66234.864750] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:28:04 192.168.122.209 [66234.890920] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:28:04 192.168.122.209 [66234.932892] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:28:04 192.168.122.209 [66234.934625] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:28:04 192.168.122.209 [66234.972826] [tempesta fw] Tempesta FW is ready Apr 26 10:28:04 192.168.122.209 [66235.581513] [tdb] Close table 'client0.tdb' Apr 26 10:28:05 192.168.122.209 [66235.766090] [tdb] Close table 'sessions0.tdb' Apr 26 10:28:08 192.168.122.209 [66239.021784] [tdb] Close table 'cache0.tdb' Apr 26 10:28:08 192.168.122.209 [66239.260797] [tdb] Close table 'filter0.tdb' Apr 26 10:28:08 192.168.122.209 [66239.261227] [tempesta fw] modules are stopped Apr 26 10:28:08 192.168.122.209 [66239.452316] [tempesta fw] exiting... Apr 26 10:28:08 192.168.122.209 [66239.570077] [tdb] Shutdown Tempesta DB Apr 26 10:28:09 192.168.122.209 [66239.779090] End test: t_modify_http_headers.test_logic.TestCachedRespHeader.test_set_header_name_greater_than_1024 Apr 26 10:28:09 192.168.122.209 [66239.791924] Start test: t_modify_http_headers.test_logic.TestCachedRespHeader.test_set_large_header Apr 26 10:28:10 192.168.122.209 [66241.041417] [tdb] Start Tempesta DB Apr 26 10:28:10 192.168.122.209 [66241.170373] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:28:12 192.168.122.209 [66242.654213] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66242.654213] Maybe that's fine, but it's worth checking the [66242.654213] config - if there is no relations between the [66242.654213] names, then host name confusion attack is possible. Apr 26 10:28:12 192.168.122.209 [66242.805003] [tempesta fw] Configuration processing is completed. Apr 26 10:28:12 192.168.122.209 [66242.868933] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:28:12 192.168.122.209 [66243.298760] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:28:12 192.168.122.209 [66243.324905] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:28:12 192.168.122.209 [66243.351106] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:28:12 192.168.122.209 [66243.424999] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:28:12 192.168.122.209 [66243.426741] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:28:12 192.168.122.209 [66243.464920] [tempesta fw] Tempesta FW is ready Apr 26 10:28:13 192.168.122.209 [66244.054044] [tdb] Close table 'client0.tdb' Apr 26 10:28:13 192.168.122.209 [66244.264184] [tdb] Close table 'sessions0.tdb' Apr 26 10:28:16 192.168.122.209 [66247.436912] [tdb] Close table 'cache0.tdb' Apr 26 10:28:17 192.168.122.209 [66247.686326] [tdb] Close table 'filter0.tdb' Apr 26 10:28:17 192.168.122.209 [66247.686726] [tempesta fw] modules are stopped Apr 26 10:28:17 192.168.122.209 [66247.865904] [tempesta fw] exiting... Apr 26 10:28:17 192.168.122.209 [66247.993725] [tdb] Shutdown Tempesta DB Apr 26 10:28:17 192.168.122.209 [66248.216126] End test: t_modify_http_headers.test_logic.TestCachedRespHeader.test_set_large_header Apr 26 10:28:17 192.168.122.209 [66248.236953] Start test: t_modify_http_headers.test_logic.TestCachedRespHeader.test_set_long_header_name Apr 26 10:28:18 192.168.122.209 [66249.515154] [tdb] Start Tempesta DB Apr 26 10:28:19 192.168.122.209 [66249.659272] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:28:20 192.168.122.209 [66251.201704] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66251.201704] Maybe that's fine, but it's worth checking the [66251.201704] config - if there is no relations between the [66251.201704] names, then host name confusion attack is possible. Apr 26 10:28:20 192.168.122.209 [66251.393120] [tempesta fw] Configuration processing is completed. Apr 26 10:28:20 192.168.122.209 [66251.451339] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:28:21 192.168.122.209 [66252.021142] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:28:21 192.168.122.209 [66252.058349] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:28:21 192.168.122.209 [66252.085062] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:28:21 192.168.122.209 [66252.145085] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:28:21 192.168.122.209 [66252.146826] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:28:21 192.168.122.209 [66252.189041] [tempesta fw] Tempesta FW is ready Apr 26 10:28:22 192.168.122.209 [66252.794534] [tdb] Close table 'client0.tdb' Apr 26 10:28:22 192.168.122.209 [66252.978434] [tdb] Close table 'sessions0.tdb' Apr 26 10:28:25 192.168.122.209 [66256.177004] [tdb] Close table 'cache0.tdb' Apr 26 10:28:25 192.168.122.209 [66256.438530] [tdb] Close table 'filter0.tdb' Apr 26 10:28:25 192.168.122.209 [66256.438955] [tempesta fw] modules are stopped Apr 26 10:28:25 192.168.122.209 [66256.634386] [tempesta fw] exiting... Apr 26 10:28:26 192.168.122.209 [66256.771651] [tdb] Shutdown Tempesta DB Apr 26 10:28:26 192.168.122.209 [66257.023423] End test: t_modify_http_headers.test_logic.TestCachedRespHeader.test_set_long_header_name Apr 26 10:28:26 192.168.122.209 [66257.037097] Start test: t_modify_http_headers.test_logic.TestCachedRespHeader.test_set_non_exist_header Apr 26 10:28:27 192.168.122.209 [66258.222634] [tdb] Start Tempesta DB Apr 26 10:28:27 192.168.122.209 [66258.365399] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:28:29 192.168.122.209 [66259.846421] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66259.846421] Maybe that's fine, but it's worth checking the [66259.846421] config - if there is no relations between the [66259.846421] names, then host name confusion attack is possible. Apr 26 10:28:29 192.168.122.209 [66260.001199] [tempesta fw] Configuration processing is completed. Apr 26 10:28:29 192.168.122.209 [66260.055849] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:28:29 192.168.122.209 [66260.470575] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:28:29 192.168.122.209 [66260.496536] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:28:29 192.168.122.209 [66260.522352] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:28:29 192.168.122.209 [66260.577205] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:28:29 192.168.122.209 [66260.578952] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:28:29 192.168.122.209 [66260.625131] [tempesta fw] Tempesta FW is ready Apr 26 10:28:30 192.168.122.209 [66261.202098] [tdb] Close table 'client0.tdb' Apr 26 10:28:30 192.168.122.209 [66261.420221] [tdb] Close table 'sessions0.tdb' Apr 26 10:28:34 192.168.122.209 [66264.695891] [tdb] Close table 'cache0.tdb' Apr 26 10:28:34 192.168.122.209 [66264.951231] [tdb] Close table 'filter0.tdb' Apr 26 10:28:34 192.168.122.209 [66264.951654] [tempesta fw] modules are stopped Apr 26 10:28:34 192.168.122.209 [66265.130193] [tempesta fw] exiting... Apr 26 10:28:34 192.168.122.209 [66265.268653] [tdb] Shutdown Tempesta DB Apr 26 10:28:34 192.168.122.209 [66265.476224] End test: t_modify_http_headers.test_logic.TestCachedRespHeader.test_set_non_exist_header Apr 26 10:28:34 192.168.122.209 [66265.488920] Start test: t_modify_http_headers.test_logic.TestCachedRespHeaderH2.test_add_header_from_static_table Apr 26 10:28:36 192.168.122.209 [66266.754928] [tdb] Start Tempesta DB Apr 26 10:28:36 192.168.122.209 [66266.914308] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:28:37 192.168.122.209 [66268.442580] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66268.442580] Maybe that's fine, but it's worth checking the [66268.442580] config - if there is no relations between the [66268.442580] names, then host name confusion attack is possible. Apr 26 10:28:37 192.168.122.209 [66268.581318] [tempesta fw] Configuration processing is completed. Apr 26 10:28:37 192.168.122.209 [66268.638337] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:28:38 192.168.122.209 [66269.053047] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:28:38 192.168.122.209 [66269.079333] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:28:38 192.168.122.209 [66269.106137] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:28:38 192.168.122.209 [66269.161280] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:28:38 192.168.122.209 [66269.163054] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:28:38 192.168.122.209 [66269.205240] [tempesta fw] Tempesta FW is ready Apr 26 10:28:39 192.168.122.209 [66269.873842] [tdb] Close table 'client0.tdb' Apr 26 10:28:39 192.168.122.209 [66270.084206] [tdb] Close table 'sessions0.tdb' Apr 26 10:28:42 192.168.122.209 [66273.263454] [tdb] Close table 'cache0.tdb' Apr 26 10:28:42 192.168.122.209 [66273.485648] [tdb] Close table 'filter0.tdb' Apr 26 10:28:42 192.168.122.209 [66273.486075] [tempesta fw] modules are stopped Apr 26 10:28:43 192.168.122.209 [66273.680544] [tempesta fw] exiting... Apr 26 10:28:43 192.168.122.209 [66273.814872] [tdb] Shutdown Tempesta DB Apr 26 10:28:43 192.168.122.209 [66274.017305] End test: t_modify_http_headers.test_logic.TestCachedRespHeaderH2.test_add_header_from_static_table Apr 26 10:28:43 192.168.122.209 [66274.046236] Start test: t_modify_http_headers.test_logic.TestCachedRespHeaderH2.test_add_non_exist_header Apr 26 10:28:44 192.168.122.209 [66275.371836] [tdb] Start Tempesta DB Apr 26 10:28:44 192.168.122.209 [66275.498309] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:28:46 192.168.122.209 [66277.006748] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66277.006748] Maybe that's fine, but it's worth checking the [66277.006748] config - if there is no relations between the [66277.006748] names, then host name confusion attack is possible. Apr 26 10:28:46 192.168.122.209 [66277.145479] [tempesta fw] Configuration processing is completed. Apr 26 10:28:46 192.168.122.209 [66277.217210] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:28:47 192.168.122.209 [66277.722202] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:28:47 192.168.122.209 [66277.756746] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:28:47 192.168.122.209 [66277.791714] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:28:47 192.168.122.209 [66277.897398] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:28:47 192.168.122.209 [66277.899146] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:28:47 192.168.122.209 [66277.945338] [tempesta fw] Tempesta FW is ready Apr 26 10:28:47 192.168.122.209 [66278.580922] [tdb] Close table 'client0.tdb' Apr 26 10:28:48 192.168.122.209 [66278.783648] [tdb] Close table 'sessions0.tdb' Apr 26 10:28:51 192.168.122.209 [66281.972976] [tdb] Close table 'cache0.tdb' Apr 26 10:28:51 192.168.122.209 [66282.219503] [tdb] Close table 'filter0.tdb' Apr 26 10:28:51 192.168.122.209 [66282.219923] [tempesta fw] modules are stopped Apr 26 10:28:51 192.168.122.209 [66282.415364] [tempesta fw] exiting... Apr 26 10:28:51 192.168.122.209 [66282.577114] [tdb] Shutdown Tempesta DB Apr 26 10:28:52 192.168.122.209 [66282.785363] End test: t_modify_http_headers.test_logic.TestCachedRespHeaderH2.test_add_non_exist_header Apr 26 10:28:52 192.168.122.209 [66282.796147] Start test: t_modify_http_headers.test_logic.TestCachedRespHeaderH2.test_delete_headers Apr 26 10:28:53 192.168.122.209 [66283.821437] [tdb] Start Tempesta DB Apr 26 10:28:53 192.168.122.209 [66283.949730] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:28:54 192.168.122.209 [66285.406819] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66285.406819] Maybe that's fine, but it's worth checking the [66285.406819] config - if there is no relations between the [66285.406819] names, then host name confusion attack is possible. Apr 26 10:28:54 192.168.122.209 [66285.537554] [tempesta fw] Configuration processing is completed. Apr 26 10:28:54 192.168.122.209 [66285.598288] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:28:55 192.168.122.209 [66286.038511] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:28:55 192.168.122.209 [66286.067795] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:28:55 192.168.122.209 [66286.096686] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:28:55 192.168.122.209 [66286.141521] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:28:55 192.168.122.209 [66286.143254] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:28:55 192.168.122.209 [66286.193458] [tempesta fw] Tempesta FW is ready Apr 26 10:28:56 192.168.122.209 [66286.826508] [tdb] Close table 'client0.tdb' Apr 26 10:28:56 192.168.122.209 [66287.021805] [tdb] Close table 'sessions0.tdb' Apr 26 10:28:59 192.168.122.209 [66290.192522] [tdb] Close table 'cache0.tdb' Apr 26 10:28:59 192.168.122.209 [66290.412631] [tdb] Close table 'filter0.tdb' Apr 26 10:28:59 192.168.122.209 [66290.413056] [tempesta fw] modules are stopped Apr 26 10:28:59 192.168.122.209 [66290.637773] [tempesta fw] exiting... Apr 26 10:29:00 192.168.122.209 [66290.754464] [tdb] Shutdown Tempesta DB Apr 26 10:29:00 192.168.122.209 [66291.005498] End test: t_modify_http_headers.test_logic.TestCachedRespHeaderH2.test_delete_headers Apr 26 10:29:00 192.168.122.209 [66291.017577] Start test: t_modify_http_headers.test_logic.TestCachedRespHeaderH2.test_delete_many_headers Apr 26 10:29:01 192.168.122.209 [66291.987561] [tdb] Start Tempesta DB Apr 26 10:29:01 192.168.122.209 [66292.130548] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:29:02 192.168.122.209 [66293.554849] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66293.554849] Maybe that's fine, but it's worth checking the [66293.554849] config - if there is no relations between the [66293.554849] names, then host name confusion attack is possible. Apr 26 10:29:03 192.168.122.209 [66293.681949] [tempesta fw] Configuration processing is completed. Apr 26 10:29:03 192.168.122.209 [66293.738089] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:29:03 192.168.122.209 [66294.160323] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:29:03 192.168.122.209 [66294.186299] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:29:03 192.168.122.209 [66294.212010] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:29:03 192.168.122.209 [66294.261512] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:29:03 192.168.122.209 [66294.263229] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:29:03 192.168.122.209 [66294.309561] [tempesta fw] Tempesta FW is ready Apr 26 10:29:04 192.168.122.209 [66294.983564] [tdb] Close table 'client0.tdb' Apr 26 10:29:04 192.168.122.209 [66295.193021] [tdb] Close table 'sessions0.tdb' Apr 26 10:29:07 192.168.122.209 [66298.444822] [tdb] Close table 'cache0.tdb' Apr 26 10:29:08 192.168.122.209 [66298.663614] [tdb] Close table 'filter0.tdb' Apr 26 10:29:08 192.168.122.209 [66298.664030] [tempesta fw] modules are stopped Apr 26 10:29:08 192.168.122.209 [66298.874979] [tempesta fw] exiting... Apr 26 10:29:08 192.168.122.209 [66299.017798] [tdb] Shutdown Tempesta DB Apr 26 10:29:08 192.168.122.209 [66299.232627] End test: t_modify_http_headers.test_logic.TestCachedRespHeaderH2.test_delete_many_headers Apr 26 10:29:08 192.168.122.209 [66299.255843] Start test: t_modify_http_headers.test_logic.TestCachedRespHeaderH2.test_delete_many_special_headers Apr 26 10:29:09 192.168.122.209 [66300.345314] [tdb] Start Tempesta DB Apr 26 10:29:09 192.168.122.209 [66300.481911] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:29:11 192.168.122.209 [66301.939615] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66301.939615] Maybe that's fine, but it's worth checking the [66301.939615] config - if there is no relations between the [66301.939615] names, then host name confusion attack is possible. Apr 26 10:29:11 192.168.122.209 [66302.101656] [tempesta fw] Configuration processing is completed. Apr 26 10:29:11 192.168.122.209 [66302.152827] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:29:11 192.168.122.209 [66302.573627] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:29:11 192.168.122.209 [66302.600885] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:29:11 192.168.122.209 [66302.627057] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:29:12 192.168.122.209 [66302.677647] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:29:12 192.168.122.209 [66302.679401] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:29:12 192.168.122.209 [66302.721660] [tempesta fw] Tempesta FW is ready Apr 26 10:29:12 192.168.122.209 [66303.385915] [tdb] Close table 'client0.tdb' Apr 26 10:29:12 192.168.122.209 [66303.570150] [tdb] Close table 'sessions0.tdb' Apr 26 10:29:16 192.168.122.209 [66306.733371] [tdb] Close table 'cache0.tdb' Apr 26 10:29:16 192.168.122.209 [66306.950362] [tdb] Close table 'filter0.tdb' Apr 26 10:29:16 192.168.122.209 [66306.950788] [tempesta fw] modules are stopped Apr 26 10:29:16 192.168.122.209 [66307.169610] [tempesta fw] exiting... Apr 26 10:29:16 192.168.122.209 [66307.295852] [tdb] Shutdown Tempesta DB Apr 26 10:29:16 192.168.122.209 [66307.501688] End test: t_modify_http_headers.test_logic.TestCachedRespHeaderH2.test_delete_many_special_headers Apr 26 10:29:16 192.168.122.209 [66307.522106] Start test: t_modify_http_headers.test_logic.TestCachedRespHeaderH2.test_delete_non_exist_header Apr 26 10:29:17 192.168.122.209 [66308.536608] [tdb] Start Tempesta DB Apr 26 10:29:18 192.168.122.209 [66308.665965] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:29:19 192.168.122.209 [66310.111039] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66310.111039] Maybe that's fine, but it's worth checking the [66310.111039] config - if there is no relations between the [66310.111039] names, then host name confusion attack is possible. Apr 26 10:29:19 192.168.122.209 [66310.257798] [tempesta fw] Configuration processing is completed. Apr 26 10:29:19 192.168.122.209 [66310.309176] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:29:20 192.168.122.209 [66310.723358] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:29:20 192.168.122.209 [66310.750302] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:29:20 192.168.122.209 [66310.779221] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:29:20 192.168.122.209 [66310.865793] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:29:20 192.168.122.209 [66310.867534] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:29:20 192.168.122.209 [66310.905748] [tempesta fw] Tempesta FW is ready Apr 26 10:29:20 192.168.122.209 [66311.563623] [tdb] Close table 'client0.tdb' Apr 26 10:29:21 192.168.122.209 [66311.749724] [tdb] Close table 'sessions0.tdb' Apr 26 10:29:24 192.168.122.209 [66314.977583] [tdb] Close table 'cache0.tdb' Apr 26 10:29:24 192.168.122.209 [66315.230777] [tdb] Close table 'filter0.tdb' Apr 26 10:29:24 192.168.122.209 [66315.231210] [tempesta fw] modules are stopped Apr 26 10:29:24 192.168.122.209 [66315.455360] [tempesta fw] exiting... Apr 26 10:29:24 192.168.122.209 [66315.571269] [tdb] Shutdown Tempesta DB Apr 26 10:29:25 192.168.122.209 [66315.808563] End test: t_modify_http_headers.test_logic.TestCachedRespHeaderH2.test_delete_non_exist_header Apr 26 10:29:25 192.168.122.209 [66315.821042] Start test: t_modify_http_headers.test_logic.TestCachedRespHeaderH2.test_delete_special_headers Apr 26 10:29:26 192.168.122.209 [66316.912409] [tdb] Start Tempesta DB Apr 26 10:29:26 192.168.122.209 [66317.054632] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:29:27 192.168.122.209 [66318.463181] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66318.463181] Maybe that's fine, but it's worth checking the [66318.463181] config - if there is no relations between the [66318.463181] names, then host name confusion attack is possible. Apr 26 10:29:27 192.168.122.209 [66318.605925] [tempesta fw] Configuration processing is completed. Apr 26 10:29:28 192.168.122.209 [66318.664031] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:29:28 192.168.122.209 [66319.145259] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:29:28 192.168.122.209 [66319.175218] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:29:28 192.168.122.209 [66319.204891] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:29:28 192.168.122.209 [66319.249855] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:29:28 192.168.122.209 [66319.251023] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:29:28 192.168.122.209 [66319.285792] [tempesta fw] Tempesta FW is ready Apr 26 10:29:29 192.168.122.209 [66319.935257] [tdb] Close table 'client0.tdb' Apr 26 10:29:29 192.168.122.209 [66320.124071] [tdb] Close table 'sessions0.tdb' Apr 26 10:29:32 192.168.122.209 [66323.330131] [tdb] Close table 'cache0.tdb' Apr 26 10:29:32 192.168.122.209 [66323.577398] [tdb] Close table 'filter0.tdb' Apr 26 10:29:32 192.168.122.209 [66323.577833] [tempesta fw] modules are stopped Apr 26 10:29:33 192.168.122.209 [66323.783706] [tempesta fw] exiting... Apr 26 10:29:33 192.168.122.209 [66323.914397] [tdb] Shutdown Tempesta DB Apr 26 10:29:33 192.168.122.209 [66324.119961] End test: t_modify_http_headers.test_logic.TestCachedRespHeaderH2.test_delete_special_headers Apr 26 10:29:33 192.168.122.209 [66324.128454] Start test: t_modify_http_headers.test_logic.TestCachedRespHeaderH2.test_long_header_name Apr 26 10:29:34 192.168.122.209 [66325.189823] [tdb] Start Tempesta DB Apr 26 10:29:34 192.168.122.209 [66325.320354] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:29:36 192.168.122.209 [66326.803302] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66326.803302] Maybe that's fine, but it's worth checking the [66326.803302] config - if there is no relations between the [66326.803302] names, then host name confusion attack is possible. Apr 26 10:29:36 192.168.122.209 [66326.950082] [tempesta fw] Configuration processing is completed. Apr 26 10:29:36 192.168.122.209 [66327.004132] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:29:36 192.168.122.209 [66327.429868] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:29:36 192.168.122.209 [66327.456612] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:29:36 192.168.122.209 [66327.482603] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:29:36 192.168.122.209 [66327.525994] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:29:36 192.168.122.209 [66327.527752] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:29:36 192.168.122.209 [66327.565950] [tempesta fw] Tempesta FW is ready Apr 26 10:29:38 192.168.122.209 [66328.841896] [tdb] Close table 'client0.tdb' Apr 26 10:29:38 192.168.122.209 [66329.047569] [tdb] Close table 'sessions0.tdb' Apr 26 10:29:41 192.168.122.209 [66332.219785] [tdb] Close table 'cache0.tdb' Apr 26 10:29:41 192.168.122.209 [66332.452634] [tdb] Close table 'filter0.tdb' Apr 26 10:29:41 192.168.122.209 [66332.453033] [tempesta fw] modules are stopped Apr 26 10:29:42 192.168.122.209 [66332.657298] [tempesta fw] exiting... Apr 26 10:29:42 192.168.122.209 [66332.783952] [tdb] Shutdown Tempesta DB Apr 26 10:29:42 192.168.122.209 [66333.008089] End test: t_modify_http_headers.test_logic.TestCachedRespHeaderH2.test_long_header_name Apr 26 10:29:42 192.168.122.209 [66333.033303] Start test: t_modify_http_headers.test_logic.TestCachedRespHeaderH2.test_set_exist_header Apr 26 10:29:43 192.168.122.209 [66334.142836] [tdb] Start Tempesta DB Apr 26 10:29:43 192.168.122.209 [66334.280827] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:29:45 192.168.122.209 [66335.687439] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66335.687439] Maybe that's fine, but it's worth checking the [66335.687439] config - if there is no relations between the [66335.687439] names, then host name confusion attack is possible. Apr 26 10:29:45 192.168.122.209 [66335.806440] [tempesta fw] Configuration processing is completed. Apr 26 10:29:45 192.168.122.209 [66335.862891] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:29:45 192.168.122.209 [66336.283734] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:29:45 192.168.122.209 [66336.310924] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:29:45 192.168.122.209 [66336.336849] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:29:45 192.168.122.209 [66336.382126] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:29:45 192.168.122.209 [66336.383874] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:29:45 192.168.122.209 [66336.430085] [tempesta fw] Tempesta FW is ready Apr 26 10:29:46 192.168.122.209 [66337.094964] [tdb] Close table 'client0.tdb' Apr 26 10:29:46 192.168.122.209 [66337.265076] [tdb] Close table 'sessions0.tdb' Apr 26 10:29:49 192.168.122.209 [66340.488296] [tdb] Close table 'cache0.tdb' Apr 26 10:29:50 192.168.122.209 [66340.705594] [tdb] Close table 'filter0.tdb' Apr 26 10:29:50 192.168.122.209 [66340.706031] [tempesta fw] modules are stopped Apr 26 10:29:50 192.168.122.209 [66340.943235] [tempesta fw] exiting... Apr 26 10:29:50 192.168.122.209 [66341.058511] [tdb] Shutdown Tempesta DB Apr 26 10:29:50 192.168.122.209 [66341.267042] End test: t_modify_http_headers.test_logic.TestCachedRespHeaderH2.test_set_exist_header Apr 26 10:29:50 192.168.122.209 [66341.281304] Start test: t_modify_http_headers.test_logic.TestCachedRespHeaderH2.test_set_exist_special_header Apr 26 10:29:51 192.168.122.209 [66342.288522] [tdb] Start Tempesta DB Apr 26 10:29:51 192.168.122.209 [66342.436681] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:29:53 192.168.122.209 [66343.915440] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66343.915440] Maybe that's fine, but it's worth checking the [66343.915440] config - if there is no relations between the [66343.915440] names, then host name confusion attack is possible. Apr 26 10:29:53 192.168.122.209 [66344.058135] [tempesta fw] Configuration processing is completed. Apr 26 10:29:53 192.168.122.209 [66344.112139] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:29:53 192.168.122.209 [66344.545135] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:29:53 192.168.122.209 [66344.570945] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:29:53 192.168.122.209 [66344.596746] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:29:54 192.168.122.209 [66344.654228] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:29:54 192.168.122.209 [66344.655977] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:29:54 192.168.122.209 [66344.702178] [tempesta fw] Tempesta FW is ready Apr 26 10:29:54 192.168.122.209 [66345.366354] [tdb] Close table 'client0.tdb' Apr 26 10:29:54 192.168.122.209 [66345.554923] [tdb] Close table 'sessions0.tdb' Apr 26 10:29:58 192.168.122.209 [66348.693115] [tdb] Close table 'cache0.tdb' Apr 26 10:29:58 192.168.122.209 [66348.938591] [tdb] Close table 'filter0.tdb' Apr 26 10:29:58 192.168.122.209 [66348.939041] [tempesta fw] modules are stopped Apr 26 10:29:58 192.168.122.209 [66349.126867] [tempesta fw] exiting... Apr 26 10:29:58 192.168.122.209 [66349.258204] [tdb] Shutdown Tempesta DB Apr 26 10:29:58 192.168.122.209 [66349.463789] End test: t_modify_http_headers.test_logic.TestCachedRespHeaderH2.test_set_exist_special_header Apr 26 10:29:58 192.168.122.209 [66349.474010] Start test: t_modify_http_headers.test_logic.TestCachedRespHeaderH2.test_set_header_name_greater_than_1024 Apr 26 10:29:59 192.168.122.209 [66350.476581] [tdb] Start Tempesta DB Apr 26 10:29:59 192.168.122.209 [66350.619610] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:30:01 192.168.122.209 [66352.075559] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66352.075559] Maybe that's fine, but it's worth checking the [66352.075559] config - if there is no relations between the [66352.075559] names, then host name confusion attack is possible. Apr 26 10:30:01 192.168.122.209 [66352.206336] [tempesta fw] Configuration processing is completed. Apr 26 10:30:01 192.168.122.209 [66352.258724] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:30:02 192.168.122.209 [66352.685750] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:30:02 192.168.122.209 [66352.712469] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:30:02 192.168.122.209 [66352.738813] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:30:02 192.168.122.209 [66352.778311] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:30:02 192.168.122.209 [66352.779697] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:30:02 192.168.122.209 [66352.818258] [tempesta fw] Tempesta FW is ready Apr 26 10:30:02 192.168.122.209 [66353.485237] [tdb] Close table 'client0.tdb' Apr 26 10:30:03 192.168.122.209 [66353.679024] [tdb] Close table 'sessions0.tdb' Apr 26 10:30:06 192.168.122.209 [66356.870081] [tdb] Close table 'cache0.tdb' Apr 26 10:30:06 192.168.122.209 [66357.095898] [tdb] Close table 'filter0.tdb' Apr 26 10:30:06 192.168.122.209 [66357.096341] [tempesta fw] modules are stopped Apr 26 10:30:06 192.168.122.209 [66357.303611] [tempesta fw] exiting... Apr 26 10:30:06 192.168.122.209 [66357.414903] [tdb] Shutdown Tempesta DB Apr 26 10:30:06 192.168.122.209 [66357.632795] End test: t_modify_http_headers.test_logic.TestCachedRespHeaderH2.test_set_header_name_greater_than_1024 Apr 26 10:30:07 192.168.122.209 [66357.648992] Start test: t_modify_http_headers.test_logic.TestCachedRespHeaderH2.test_set_large_header Apr 26 10:30:08 192.168.122.209 [66358.664452] [tdb] Start Tempesta DB Apr 26 10:30:08 192.168.122.209 [66358.786119] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:30:09 192.168.122.209 [66360.203714] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66360.203714] Maybe that's fine, but it's worth checking the [66360.203714] config - if there is no relations between the [66360.203714] names, then host name confusion attack is possible. Apr 26 10:30:09 192.168.122.209 [66360.334464] [tempesta fw] Configuration processing is completed. Apr 26 10:30:09 192.168.122.209 [66360.394736] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:30:10 192.168.122.209 [66360.821361] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:30:10 192.168.122.209 [66360.847862] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:30:10 192.168.122.209 [66360.877430] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:30:10 192.168.122.209 [66360.926432] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:30:10 192.168.122.209 [66360.928214] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:30:10 192.168.122.209 [66360.978358] [tempesta fw] Tempesta FW is ready Apr 26 10:30:11 192.168.122.209 [66361.653598] [tdb] Close table 'client0.tdb' Apr 26 10:30:11 192.168.122.209 [66361.838962] [tdb] Close table 'sessions0.tdb' Apr 26 10:30:14 192.168.122.209 [66365.040310] [tdb] Close table 'cache0.tdb' Apr 26 10:30:14 192.168.122.209 [66365.247359] [tdb] Close table 'filter0.tdb' Apr 26 10:30:14 192.168.122.209 [66365.247877] [tempesta fw] modules are stopped Apr 26 10:30:14 192.168.122.209 [66365.438947] [tempesta fw] exiting... Apr 26 10:30:14 192.168.122.209 [66365.585378] [tdb] Shutdown Tempesta DB Apr 26 10:30:15 192.168.122.209 [66365.807769] End test: t_modify_http_headers.test_logic.TestCachedRespHeaderH2.test_set_large_header Apr 26 10:30:15 192.168.122.209 [66365.822138] Start test: t_modify_http_headers.test_logic.TestCachedRespHeaderH2.test_set_long_header_name Apr 26 10:30:16 192.168.122.209 [66366.809212] [tdb] Start Tempesta DB Apr 26 10:30:16 192.168.122.209 [66366.946086] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:30:17 192.168.122.209 [66368.532344] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66368.532344] Maybe that's fine, but it's worth checking the [66368.532344] config - if there is no relations between the [66368.532344] names, then host name confusion attack is possible. Apr 26 10:30:18 192.168.122.209 [66368.730567] [tempesta fw] Configuration processing is completed. Apr 26 10:30:18 192.168.122.209 [66368.790763] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:30:18 192.168.122.209 [66369.214187] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:30:18 192.168.122.209 [66369.239692] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:30:18 192.168.122.209 [66369.265447] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:30:18 192.168.122.209 [66369.314508] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:30:18 192.168.122.209 [66369.316241] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:30:18 192.168.122.209 [66369.358466] [tempesta fw] Tempesta FW is ready Apr 26 10:30:19 192.168.122.209 [66370.006731] [tdb] Close table 'client0.tdb' Apr 26 10:30:19 192.168.122.209 [66370.191355] [tdb] Close table 'sessions0.tdb' Apr 26 10:30:22 192.168.122.209 [66373.345658] [tdb] Close table 'cache0.tdb' Apr 26 10:30:22 192.168.122.209 [66373.579799] [tdb] Close table 'filter0.tdb' Apr 26 10:30:22 192.168.122.209 [66373.580187] [tempesta fw] modules are stopped Apr 26 10:30:23 192.168.122.209 [66373.797220] [tempesta fw] exiting... Apr 26 10:30:23 192.168.122.209 [66373.936229] [tdb] Shutdown Tempesta DB Apr 26 10:30:23 192.168.122.209 [66374.139230] End test: t_modify_http_headers.test_logic.TestCachedRespHeaderH2.test_set_long_header_name Apr 26 10:30:23 192.168.122.209 [66374.165189] Start test: t_modify_http_headers.test_logic.TestCachedRespHeaderH2.test_set_non_exist_header Apr 26 10:30:24 192.168.122.209 [66375.107913] [tdb] Start Tempesta DB Apr 26 10:30:24 192.168.122.209 [66375.239001] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:30:26 192.168.122.209 [66376.635843] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66376.635843] Maybe that's fine, but it's worth checking the [66376.635843] config - if there is no relations between the [66376.635843] names, then host name confusion attack is possible. Apr 26 10:30:26 192.168.122.209 [66376.770643] [tempesta fw] Configuration processing is completed. Apr 26 10:30:26 192.168.122.209 [66376.821528] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:30:26 192.168.122.209 [66377.245806] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:30:26 192.168.122.209 [66377.272973] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:30:26 192.168.122.209 [66377.300234] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:30:26 192.168.122.209 [66377.354648] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:30:26 192.168.122.209 [66377.356395] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:30:26 192.168.122.209 [66377.394584] [tempesta fw] Tempesta FW is ready Apr 26 10:30:27 192.168.122.209 [66378.056147] [tdb] Close table 'client0.tdb' Apr 26 10:30:27 192.168.122.209 [66378.233081] [tdb] Close table 'sessions0.tdb' Apr 26 10:30:30 192.168.122.209 [66381.503025] [tdb] Close table 'cache0.tdb' Apr 26 10:30:31 192.168.122.209 [66381.772729] [tdb] Close table 'filter0.tdb' Apr 26 10:30:31 192.168.122.209 [66381.773172] [tempesta fw] modules are stopped Apr 26 10:30:31 192.168.122.209 [66382.001855] [tempesta fw] exiting... Apr 26 10:30:31 192.168.122.209 [66382.133980] [tdb] Shutdown Tempesta DB Apr 26 10:30:31 192.168.122.209 [66382.367022] End test: t_modify_http_headers.test_logic.TestCachedRespHeaderH2.test_set_non_exist_header Apr 26 10:30:31 192.168.122.209 [66382.377754] Start test: t_modify_http_headers.test_logic.TestLogicBase.test_add_non_exist_header Apr 26 10:30:31 192.168.122.209 [66382.391567] End test: t_modify_http_headers.test_logic.TestLogicBase.test_add_non_exist_header Apr 26 10:30:31 192.168.122.209 [66382.412633] Start test: t_modify_http_headers.test_logic.TestLogicBase.test_delete_headers Apr 26 10:30:31 192.168.122.209 [66382.436326] End test: t_modify_http_headers.test_logic.TestLogicBase.test_delete_headers Apr 26 10:30:31 192.168.122.209 [66382.445022] Start test: t_modify_http_headers.test_logic.TestLogicBase.test_delete_many_headers Apr 26 10:30:31 192.168.122.209 [66382.456893] End test: t_modify_http_headers.test_logic.TestLogicBase.test_delete_many_headers Apr 26 10:30:31 192.168.122.209 [66382.468052] Start test: t_modify_http_headers.test_logic.TestLogicBase.test_delete_many_special_headers Apr 26 10:30:31 192.168.122.209 [66382.476908] End test: t_modify_http_headers.test_logic.TestLogicBase.test_delete_many_special_headers Apr 26 10:30:31 192.168.122.209 [66382.485796] Start test: t_modify_http_headers.test_logic.TestLogicBase.test_delete_non_exist_header Apr 26 10:30:31 192.168.122.209 [66382.498658] End test: t_modify_http_headers.test_logic.TestLogicBase.test_delete_non_exist_header Apr 26 10:30:31 192.168.122.209 [66382.509663] Start test: t_modify_http_headers.test_logic.TestLogicBase.test_delete_special_headers Apr 26 10:30:31 192.168.122.209 [66382.523809] End test: t_modify_http_headers.test_logic.TestLogicBase.test_delete_special_headers Apr 26 10:30:31 192.168.122.209 [66382.533207] Start test: t_modify_http_headers.test_logic.TestLogicBase.test_long_header_name Apr 26 10:30:31 192.168.122.209 [66382.551711] End test: t_modify_http_headers.test_logic.TestLogicBase.test_long_header_name Apr 26 10:30:31 192.168.122.209 [66382.561174] Start test: t_modify_http_headers.test_logic.TestLogicBase.test_set_exist_header Apr 26 10:30:31 192.168.122.209 [66382.570631] End test: t_modify_http_headers.test_logic.TestLogicBase.test_set_exist_header Apr 26 10:30:31 192.168.122.209 [66382.581258] Start test: t_modify_http_headers.test_logic.TestLogicBase.test_set_exist_special_header Apr 26 10:30:31 192.168.122.209 [66382.596247] End test: t_modify_http_headers.test_logic.TestLogicBase.test_set_exist_special_header Apr 26 10:30:31 192.168.122.209 [66382.614571] Start test: t_modify_http_headers.test_logic.TestLogicBase.test_set_header_name_greater_than_1024 Apr 26 10:30:31 192.168.122.209 [66382.624072] End test: t_modify_http_headers.test_logic.TestLogicBase.test_set_header_name_greater_than_1024 Apr 26 10:30:31 192.168.122.209 [66382.636690] Start test: t_modify_http_headers.test_logic.TestLogicBase.test_set_large_header Apr 26 10:30:32 192.168.122.209 [66382.647277] End test: t_modify_http_headers.test_logic.TestLogicBase.test_set_large_header Apr 26 10:30:32 192.168.122.209 [66382.656735] Start test: t_modify_http_headers.test_logic.TestLogicBase.test_set_long_header_name Apr 26 10:30:32 192.168.122.209 [66382.665946] End test: t_modify_http_headers.test_logic.TestLogicBase.test_set_long_header_name Apr 26 10:30:32 192.168.122.209 [66382.677459] Start test: t_modify_http_headers.test_logic.TestLogicBase.test_set_non_exist_header Apr 26 10:30:32 192.168.122.209 [66382.692464] End test: t_modify_http_headers.test_logic.TestLogicBase.test_set_non_exist_header Apr 26 10:30:32 192.168.122.209 [66382.707766] Start test: t_modify_http_headers.test_logic.TestManyCachedResponseHeaders.test_many_headers Apr 26 10:30:33 192.168.122.209 [66384.022769] [tdb] Start Tempesta DB Apr 26 10:30:33 192.168.122.209 [66384.199140] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:30:36 192.168.122.209 [66387.388189] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66387.388189] Maybe that's fine, but it's worth checking the [66387.388189] config - if there is no relations between the [66387.388189] names, then host name confusion attack is possible. Apr 26 10:30:37 192.168.122.209 [66388.442744] [tempesta fw] Configuration processing is completed. Apr 26 10:30:37 192.168.122.209 [66388.498494] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:30:38 192.168.122.209 [66388.998270] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:30:38 192.168.122.209 [66389.047077] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:30:38 192.168.122.209 [66389.086627] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:30:38 192.168.122.209 [66389.130642] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:30:38 192.168.122.209 [66389.131709] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:30:38 192.168.122.209 [66389.170707] [tempesta fw] Tempesta FW is ready Apr 26 10:30:44 192.168.122.209 [66395.065161] [tdb] Close table 'client0.tdb' Apr 26 10:30:44 192.168.122.209 [66395.308877] [tdb] Close table 'sessions0.tdb' Apr 26 10:30:48 192.168.122.209 [66398.908252] [tdb] Close table 'cache0.tdb' Apr 26 10:30:48 192.168.122.209 [66399.186211] [tdb] Close table 'filter0.tdb' Apr 26 10:30:48 192.168.122.209 [66399.187110] [tempesta fw] modules are stopped Apr 26 10:30:48 192.168.122.209 [66399.390712] [tempesta fw] exiting... Apr 26 10:30:48 192.168.122.209 [66399.559963] [tdb] Shutdown Tempesta DB Apr 26 10:30:49 192.168.122.209 [66399.788265] End test: t_modify_http_headers.test_logic.TestManyCachedResponseHeaders.test_many_headers Apr 26 10:30:49 192.168.122.209 [66399.835968] Start test: t_modify_http_headers.test_logic.TestManyCachedResponseHeadersH2.test_many_headers Apr 26 10:30:50 192.168.122.209 [66401.072787] [tdb] Start Tempesta DB Apr 26 10:30:50 192.168.122.209 [66401.233081] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:30:53 192.168.122.209 [66404.436314] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66404.436314] Maybe that's fine, but it's worth checking the [66404.436314] config - if there is no relations between the [66404.436314] names, then host name confusion attack is possible. Apr 26 10:30:55 192.168.122.209 [66405.679279] [tempesta fw] Configuration processing is completed. Apr 26 10:30:55 192.168.122.209 [66405.747655] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:30:55 192.168.122.209 [66406.330651] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:30:55 192.168.122.209 [66406.367885] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:30:55 192.168.122.209 [66406.406461] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:30:55 192.168.122.209 [66406.466979] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:30:55 192.168.122.209 [66406.468829] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:30:55 192.168.122.209 [66406.510933] [tempesta fw] Tempesta FW is ready Apr 26 10:31:00 192.168.122.209 [66411.282734] [tdb] Close table 'client0.tdb' Apr 26 10:31:00 192.168.122.209 [66411.463797] [tdb] Close table 'sessions0.tdb' Apr 26 10:31:04 192.168.122.209 [66414.690494] [tdb] Close table 'cache0.tdb' Apr 26 10:31:04 192.168.122.209 [66414.909470] [tdb] Close table 'filter0.tdb' Apr 26 10:31:04 192.168.122.209 [66414.909901] [tempesta fw] modules are stopped Apr 26 10:31:04 192.168.122.209 [66415.107183] [tempesta fw] exiting... Apr 26 10:31:04 192.168.122.209 [66415.256235] [tdb] Shutdown Tempesta DB Apr 26 10:31:04 192.168.122.209 [66415.490762] End test: t_modify_http_headers.test_logic.TestManyCachedResponseHeadersH2.test_many_headers Apr 26 10:31:04 192.168.122.209 [66415.514694] Start test: t_modify_http_headers.test_logic.TestManyRequestHeadersH2.test_many_headers Apr 26 10:31:06 192.168.122.209 [66416.788006] [tdb] Start Tempesta DB Apr 26 10:31:06 192.168.122.209 [66416.930605] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:31:09 192.168.122.209 [66420.032432] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66420.032432] Maybe that's fine, but it's worth checking the [66420.032432] config - if there is no relations between the [66420.032432] names, then host name confusion attack is possible. Apr 26 10:31:10 192.168.122.209 [66421.223175] [tempesta fw] Configuration processing is completed. Apr 26 10:31:10 192.168.122.209 [66421.275212] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:31:11 192.168.122.209 [66421.694122] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:31:11 192.168.122.209 [66421.719594] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:31:11 192.168.122.209 [66421.745371] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:31:11 192.168.122.209 [66421.807100] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:31:11 192.168.122.209 [66421.808829] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:31:11 192.168.122.209 [66421.875101] [tempesta fw] Tempesta FW is ready Apr 26 10:31:17 192.168.122.209 [66428.500980] [tdb] Close table 'client0.tdb' Apr 26 10:31:18 192.168.122.209 [66428.684170] [tdb] Close table 'sessions0.tdb' Apr 26 10:31:21 192.168.122.209 [66431.936611] [tdb] Close table 'cache0.tdb' Apr 26 10:31:21 192.168.122.209 [66432.178810] [tdb] Close table 'filter0.tdb' Apr 26 10:31:21 192.168.122.209 [66432.179277] [tempesta fw] modules are stopped Apr 26 10:31:21 192.168.122.209 [66432.380723] [tempesta fw] exiting... Apr 26 10:31:21 192.168.122.209 [66432.506061] [tdb] Shutdown Tempesta DB Apr 26 10:31:22 192.168.122.209 [66432.729095] End test: t_modify_http_headers.test_logic.TestManyRequestHeadersH2.test_many_headers Apr 26 10:31:22 192.168.122.209 [66432.742044] Start test: t_modify_http_headers.test_logic.TestManyResponseHeaders.test_many_headers Apr 26 10:31:23 192.168.122.209 [66433.969589] [tdb] Start Tempesta DB Apr 26 10:31:23 192.168.122.209 [66434.111829] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:31:26 192.168.122.209 [66437.192755] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66437.192755] Maybe that's fine, but it's worth checking the [66437.192755] config - if there is no relations between the [66437.192755] names, then host name confusion attack is possible. Apr 26 10:31:27 192.168.122.209 [66438.435474] [tempesta fw] Configuration processing is completed. Apr 26 10:31:27 192.168.122.209 [66438.496948] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:31:28 192.168.122.209 [66438.961821] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:31:28 192.168.122.209 [66438.989771] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:31:28 192.168.122.209 [66439.025734] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:31:28 192.168.122.209 [66439.075381] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:31:28 192.168.122.209 [66439.077142] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:31:28 192.168.122.209 [66439.119317] [tempesta fw] Tempesta FW is ready Apr 26 10:31:32 192.168.122.209 [66443.108275] [tdb] Close table 'client0.tdb' Apr 26 10:31:32 192.168.122.209 [66443.300965] [tdb] Close table 'sessions0.tdb' Apr 26 10:31:35 192.168.122.209 [66446.505839] [tdb] Close table 'cache0.tdb' Apr 26 10:31:36 192.168.122.209 [66446.727856] [tdb] Close table 'filter0.tdb' Apr 26 10:31:36 192.168.122.209 [66446.728282] [tempesta fw] modules are stopped Apr 26 10:31:36 192.168.122.209 [66446.979597] [tempesta fw] exiting... Apr 26 10:31:36 192.168.122.209 [66447.112240] [tdb] Shutdown Tempesta DB Apr 26 10:31:36 192.168.122.209 [66447.315645] End test: t_modify_http_headers.test_logic.TestManyResponseHeaders.test_many_headers Apr 26 10:31:36 192.168.122.209 [66447.331394] Start test: t_modify_http_headers.test_logic.TestManyResponseHeadersH2.test_many_headers Apr 26 10:31:37 192.168.122.209 [66448.550946] [tdb] Start Tempesta DB Apr 26 10:31:38 192.168.122.209 [66448.691249] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:31:41 192.168.122.209 [66451.828856] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66451.828856] Maybe that's fine, but it's worth checking the [66451.828856] config - if there is no relations between the [66451.828856] names, then host name confusion attack is possible. Apr 26 10:31:42 192.168.122.209 [66453.011586] [tempesta fw] Configuration processing is completed. Apr 26 10:31:42 192.168.122.209 [66453.075226] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:31:42 192.168.122.209 [66453.540529] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:31:42 192.168.122.209 [66453.570631] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:31:42 192.168.122.209 [66453.600139] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:31:42 192.168.122.209 [66453.639545] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:31:43 192.168.122.209 [66453.641308] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:31:43 192.168.122.209 [66453.691497] [tempesta fw] Tempesta FW is ready Apr 26 10:31:50 192.168.122.209 [66461.615807] [tdb] Close table 'client0.tdb' Apr 26 10:31:51 192.168.122.209 [66461.814338] [tdb] Close table 'sessions0.tdb' Apr 26 10:31:54 192.168.122.209 [66465.066824] [tdb] Close table 'cache0.tdb' Apr 26 10:31:54 192.168.122.209 [66465.327557] [tdb] Close table 'filter0.tdb' Apr 26 10:31:54 192.168.122.209 [66465.328007] [tempesta fw] modules are stopped Apr 26 10:31:54 192.168.122.209 [66465.548512] [tempesta fw] exiting... Apr 26 10:31:55 192.168.122.209 [66465.685923] [tdb] Shutdown Tempesta DB Apr 26 10:31:55 192.168.122.209 [66465.901466] End test: t_modify_http_headers.test_logic.TestManyResponseHeadersH2.test_many_headers Apr 26 10:31:55 192.168.122.209 [66465.912043] Start test: t_modify_http_headers.test_logic.TestReqHdrSetHost.test_req_hdr_set_host Apr 26 10:31:56 192.168.122.209 [66467.067033] [tdb] Start Tempesta DB Apr 26 10:31:56 192.168.122.209 [66467.192453] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:31:58 192.168.122.209 [66468.653004] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66468.653004] Maybe that's fine, but it's worth checking the [66468.653004] config - if there is no relations between the [66468.653004] names, then host name confusion attack is possible. Apr 26 10:31:58 192.168.122.209 [66468.763781] [tempesta fw] Configuration processing is completed. Apr 26 10:31:58 192.168.122.209 [66468.821007] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:31:58 192.168.122.209 [66469.239953] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:31:58 192.168.122.209 [66469.266368] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:31:58 192.168.122.209 [66469.292948] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:31:58 192.168.122.209 [66469.339752] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:31:58 192.168.122.209 [66469.341480] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:31:58 192.168.122.209 [66469.379713] [tempesta fw] Tempesta FW is ready Apr 26 10:31:59 192.168.122.209 [66469.923134] [tdb] Close table 'client0.tdb' Apr 26 10:31:59 192.168.122.209 [66470.111264] [tdb] Close table 'sessions0.tdb' Apr 26 10:32:02 192.168.122.209 [66473.394461] [tdb] Close table 'cache0.tdb' Apr 26 10:32:03 192.168.122.209 [66473.644722] [tdb] Close table 'filter0.tdb' Apr 26 10:32:03 192.168.122.209 [66473.645146] [tempesta fw] modules are stopped Apr 26 10:32:03 192.168.122.209 [66473.824504] [tempesta fw] exiting... Apr 26 10:32:03 192.168.122.209 [66473.936304] [tdb] Shutdown Tempesta DB Apr 26 10:32:03 192.168.122.209 [66474.141950] End test: t_modify_http_headers.test_logic.TestReqHdrSetHost.test_req_hdr_set_host Apr 26 10:32:03 192.168.122.209 [66474.166452] Start test: t_modify_http_headers.test_logic.TestReqHdrSetHostH2.test_req_hdr_set_host Apr 26 10:32:04 192.168.122.209 [66475.511877] [tdb] Start Tempesta DB Apr 26 10:32:05 192.168.122.209 [66475.666708] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:32:06 192.168.122.209 [66477.081117] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66477.081117] Maybe that's fine, but it's worth checking the [66477.081117] config - if there is no relations between the [66477.081117] names, then host name confusion attack is possible. Apr 26 10:32:06 192.168.122.209 [66477.203902] [tempesta fw] Configuration processing is completed. Apr 26 10:32:06 192.168.122.209 [66477.277744] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:32:07 192.168.122.209 [66477.854477] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:32:07 192.168.122.209 [66477.890441] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:32:07 192.168.122.209 [66477.925075] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:32:07 192.168.122.209 [66477.967782] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:32:07 192.168.122.209 [66477.968825] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:32:07 192.168.122.209 [66478.007799] [tempesta fw] Tempesta FW is ready Apr 26 10:32:07 192.168.122.209 [66478.638361] [tdb] Close table 'client0.tdb' Apr 26 10:32:08 192.168.122.209 [66478.822802] [tdb] Close table 'sessions0.tdb' Apr 26 10:32:11 192.168.122.209 [66481.945923] [tdb] Close table 'cache0.tdb' Apr 26 10:32:11 192.168.122.209 [66482.205217] [tdb] Close table 'filter0.tdb' Apr 26 10:32:11 192.168.122.209 [66482.205630] [tempesta fw] modules are stopped Apr 26 10:32:11 192.168.122.209 [66482.408308] [tempesta fw] exiting... Apr 26 10:32:11 192.168.122.209 [66482.525447] [tdb] Shutdown Tempesta DB Apr 26 10:32:12 192.168.122.209 [66482.745799] End test: t_modify_http_headers.test_logic.TestReqHdrSetHostH2.test_req_hdr_set_host Apr 26 10:32:12 192.168.122.209 [66482.756785] Start test: t_modify_http_headers.test_logic.TestReqHeader.test_add_non_exist_header Apr 26 10:32:13 192.168.122.209 [66484.054161] [tdb] Start Tempesta DB Apr 26 10:32:13 192.168.122.209 [66484.206263] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:32:15 192.168.122.209 [66485.653225] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66485.653225] Maybe that's fine, but it's worth checking the [66485.653225] config - if there is no relations between the [66485.653225] names, then host name confusion attack is possible. Apr 26 10:32:15 192.168.122.209 [66485.752003] [tempesta fw] Configuration processing is completed. Apr 26 10:32:15 192.168.122.209 [66485.808773] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:32:15 192.168.122.209 [66486.216652] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:32:15 192.168.122.209 [66486.242082] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:32:15 192.168.122.209 [66486.267642] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:32:15 192.168.122.209 [66486.311906] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:32:15 192.168.122.209 [66486.313749] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:32:15 192.168.122.209 [66486.363906] [tempesta fw] Tempesta FW is ready Apr 26 10:32:16 192.168.122.209 [66486.991855] [tdb] Close table 'client0.tdb' Apr 26 10:32:16 192.168.122.209 [66487.158049] [tdb] Close table 'sessions0.tdb' Apr 26 10:32:19 192.168.122.209 [66490.428853] [tdb] Close table 'cache0.tdb' Apr 26 10:32:20 192.168.122.209 [66490.674818] [tdb] Close table 'filter0.tdb' Apr 26 10:32:20 192.168.122.209 [66490.675268] [tempesta fw] modules are stopped Apr 26 10:32:20 192.168.122.209 [66490.862052] [tempesta fw] exiting... Apr 26 10:32:20 192.168.122.209 [66490.997551] [tdb] Shutdown Tempesta DB Apr 26 10:32:20 192.168.122.209 [66491.220500] End test: t_modify_http_headers.test_logic.TestReqHeader.test_add_non_exist_header Apr 26 10:32:20 192.168.122.209 [66491.233227] Start test: t_modify_http_headers.test_logic.TestReqHeader.test_delete_headers Apr 26 10:32:21 192.168.122.209 [66492.557135] [tdb] Start Tempesta DB Apr 26 10:32:22 192.168.122.209 [66492.698239] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:32:23 192.168.122.209 [66494.136243] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66494.136243] Maybe that's fine, but it's worth checking the [66494.136243] config - if there is no relations between the [66494.136243] names, then host name confusion attack is possible. Apr 26 10:32:23 192.168.122.209 [66494.236106] [tempesta fw] Configuration processing is completed. Apr 26 10:32:23 192.168.122.209 [66494.301528] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:32:24 192.168.122.209 [66494.760076] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:32:24 192.168.122.209 [66494.788230] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:32:24 192.168.122.209 [66494.817259] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:32:24 192.168.122.209 [66494.896088] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:32:24 192.168.122.209 [66494.896865] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:32:24 192.168.122.209 [66494.944015] [tempesta fw] Tempesta FW is ready Apr 26 10:32:24 192.168.122.209 [66495.499428] [tdb] Close table 'client0.tdb' Apr 26 10:32:25 192.168.122.209 [66495.686968] [tdb] Close table 'sessions0.tdb' Apr 26 10:32:28 192.168.122.209 [66498.992807] [tdb] Close table 'cache0.tdb' Apr 26 10:32:28 192.168.122.209 [66499.277924] [tdb] Close table 'filter0.tdb' Apr 26 10:32:28 192.168.122.209 [66499.278371] [tempesta fw] modules are stopped Apr 26 10:32:28 192.168.122.209 [66499.447281] [tempesta fw] exiting... Apr 26 10:32:28 192.168.122.209 [66499.554905] [tdb] Shutdown Tempesta DB Apr 26 10:32:29 192.168.122.209 [66499.769398] End test: t_modify_http_headers.test_logic.TestReqHeader.test_delete_headers Apr 26 10:32:29 192.168.122.209 [66499.783822] Start test: t_modify_http_headers.test_logic.TestReqHeader.test_delete_many_headers Apr 26 10:32:30 192.168.122.209 [66501.002766] [tdb] Start Tempesta DB Apr 26 10:32:30 192.168.122.209 [66501.131999] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:32:32 192.168.122.209 [66502.661084] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66502.661084] Maybe that's fine, but it's worth checking the [66502.661084] config - if there is no relations between the [66502.661084] names, then host name confusion attack is possible. Apr 26 10:32:32 192.168.122.209 [66502.776205] [tempesta fw] Configuration processing is completed. Apr 26 10:32:32 192.168.122.209 [66502.834992] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:32:32 192.168.122.209 [66503.395071] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:32:32 192.168.122.209 [66503.430124] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:32:32 192.168.122.209 [66503.456104] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:32:32 192.168.122.209 [66503.492152] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:32:32 192.168.122.209 [66503.493882] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:32:32 192.168.122.209 [66503.532107] [tempesta fw] Tempesta FW is ready Apr 26 10:32:33 192.168.122.209 [66504.169862] [tdb] Close table 'client0.tdb' Apr 26 10:32:33 192.168.122.209 [66504.352733] [tdb] Close table 'sessions0.tdb' Apr 26 10:32:36 192.168.122.209 [66507.613314] [tdb] Close table 'cache0.tdb' Apr 26 10:32:37 192.168.122.209 [66507.857359] [tdb] Close table 'filter0.tdb' Apr 26 10:32:37 192.168.122.209 [66507.857806] [tempesta fw] modules are stopped Apr 26 10:32:37 192.168.122.209 [66508.055133] [tempesta fw] exiting... Apr 26 10:32:37 192.168.122.209 [66508.196343] [tdb] Shutdown Tempesta DB Apr 26 10:32:37 192.168.122.209 [66508.419746] End test: t_modify_http_headers.test_logic.TestReqHeader.test_delete_many_headers Apr 26 10:32:37 192.168.122.209 [66508.439810] Start test: t_modify_http_headers.test_logic.TestReqHeader.test_delete_many_special_headers Apr 26 10:32:39 192.168.122.209 [66509.718987] [tdb] Start Tempesta DB Apr 26 10:32:39 192.168.122.209 [66509.866649] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:32:40 192.168.122.209 [66511.281569] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66511.281569] Maybe that's fine, but it's worth checking the [66511.281569] config - if there is no relations between the [66511.281569] names, then host name confusion attack is possible. Apr 26 10:32:40 192.168.122.209 [66511.384282] [tempesta fw] Configuration processing is completed. Apr 26 10:32:40 192.168.122.209 [66511.444642] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:32:41 192.168.122.209 [66511.890385] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:32:41 192.168.122.209 [66511.916586] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:32:41 192.168.122.209 [66511.942967] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:32:41 192.168.122.209 [66511.988268] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:32:41 192.168.122.209 [66511.990051] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:32:41 192.168.122.209 [66512.032202] [tempesta fw] Tempesta FW is ready Apr 26 10:32:41 192.168.122.209 [66512.617682] [tdb] Close table 'client0.tdb' Apr 26 10:32:42 192.168.122.209 [66512.805686] [tdb] Close table 'sessions0.tdb' Apr 26 10:32:45 192.168.122.209 [66516.017679] [tdb] Close table 'cache0.tdb' Apr 26 10:32:45 192.168.122.209 [66516.273084] [tdb] Close table 'filter0.tdb' Apr 26 10:32:45 192.168.122.209 [66516.273528] [tempesta fw] modules are stopped Apr 26 10:32:45 192.168.122.209 [66516.449529] [tempesta fw] exiting... Apr 26 10:32:45 192.168.122.209 [66516.598580] [tdb] Shutdown Tempesta DB Apr 26 10:32:46 192.168.122.209 [66516.822585] End test: t_modify_http_headers.test_logic.TestReqHeader.test_delete_many_special_headers Apr 26 10:32:46 192.168.122.209 [66516.835792] Start test: t_modify_http_headers.test_logic.TestReqHeader.test_delete_non_exist_header Apr 26 10:32:47 192.168.122.209 [66518.017104] [tdb] Start Tempesta DB Apr 26 10:32:47 192.168.122.209 [66518.154633] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:32:49 192.168.122.209 [66519.721704] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66519.721704] Maybe that's fine, but it's worth checking the [66519.721704] config - if there is no relations between the [66519.721704] names, then host name confusion attack is possible. Apr 26 10:32:49 192.168.122.209 [66519.832438] [tempesta fw] Configuration processing is completed. Apr 26 10:32:49 192.168.122.209 [66519.918741] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:32:49 192.168.122.209 [66520.333931] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:32:49 192.168.122.209 [66520.363945] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:32:49 192.168.122.209 [66520.391863] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:32:49 192.168.122.209 [66520.436387] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:32:49 192.168.122.209 [66520.438114] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:32:49 192.168.122.209 [66520.476347] [tempesta fw] Tempesta FW is ready Apr 26 10:32:50 192.168.122.209 [66521.054000] [tdb] Close table 'client0.tdb' Apr 26 10:32:50 192.168.122.209 [66521.232083] [tdb] Close table 'sessions0.tdb' Apr 26 10:32:53 192.168.122.209 [66524.413477] [tdb] Close table 'cache0.tdb' Apr 26 10:32:54 192.168.122.209 [66524.677554] [tdb] Close table 'filter0.tdb' Apr 26 10:32:54 192.168.122.209 [66524.678046] [tempesta fw] modules are stopped Apr 26 10:32:54 192.168.122.209 [66524.864964] [tempesta fw] exiting... Apr 26 10:32:54 192.168.122.209 [66525.001758] [tdb] Shutdown Tempesta DB Apr 26 10:32:54 192.168.122.209 [66525.200179] End test: t_modify_http_headers.test_logic.TestReqHeader.test_delete_non_exist_header Apr 26 10:32:54 192.168.122.209 [66525.215563] Start test: t_modify_http_headers.test_logic.TestReqHeader.test_delete_special_headers Apr 26 10:32:55 192.168.122.209 [66526.494754] [tdb] Start Tempesta DB Apr 26 10:32:55 192.168.122.209 [66526.640703] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:32:57 192.168.122.209 [66528.137763] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66528.137763] Maybe that's fine, but it's worth checking the [66528.137763] config - if there is no relations between the [66528.137763] names, then host name confusion attack is possible. Apr 26 10:32:57 192.168.122.209 [66528.244535] [tempesta fw] Configuration processing is completed. Apr 26 10:32:57 192.168.122.209 [66528.303046] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:32:58 192.168.122.209 [66528.729838] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:32:58 192.168.122.209 [66528.756389] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:32:58 192.168.122.209 [66528.784106] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:32:58 192.168.122.209 [66528.860475] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:32:58 192.168.122.209 [66528.862242] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:32:58 192.168.122.209 [66528.908416] [tempesta fw] Tempesta FW is ready Apr 26 10:32:58 192.168.122.209 [66529.538277] [tdb] Close table 'client0.tdb' Apr 26 10:32:59 192.168.122.209 [66529.713015] [tdb] Close table 'sessions0.tdb' Apr 26 10:33:02 192.168.122.209 [66532.898453] [tdb] Close table 'cache0.tdb' Apr 26 10:33:02 192.168.122.209 [66533.142835] [tdb] Close table 'filter0.tdb' Apr 26 10:33:02 192.168.122.209 [66533.143241] [tempesta fw] modules are stopped Apr 26 10:33:02 192.168.122.209 [66533.341452] [tempesta fw] exiting... Apr 26 10:33:02 192.168.122.209 [66533.477106] [tdb] Shutdown Tempesta DB Apr 26 10:33:03 192.168.122.209 [66533.667451] End test: t_modify_http_headers.test_logic.TestReqHeader.test_delete_special_headers Apr 26 10:33:03 192.168.122.209 [66533.682667] Start test: t_modify_http_headers.test_logic.TestReqHeader.test_long_header_name Apr 26 10:33:04 192.168.122.209 [66534.987656] [tdb] Start Tempesta DB Apr 26 10:33:04 192.168.122.209 [66535.138212] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:33:05 192.168.122.209 [66536.601892] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66536.601892] Maybe that's fine, but it's worth checking the [66536.601892] config - if there is no relations between the [66536.601892] names, then host name confusion attack is possible. Apr 26 10:33:06 192.168.122.209 [66536.712859] [tempesta fw] Configuration processing is completed. Apr 26 10:33:06 192.168.122.209 [66536.772895] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:33:06 192.168.122.209 [66537.195770] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:33:06 192.168.122.209 [66537.222156] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:33:06 192.168.122.209 [66537.248618] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:33:06 192.168.122.209 [66537.300588] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:33:06 192.168.122.209 [66537.302314] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:33:06 192.168.122.209 [66537.352551] [tempesta fw] Tempesta FW is ready Apr 26 10:33:08 192.168.122.209 [66539.113102] [tdb] Close table 'client0.tdb' Apr 26 10:33:08 192.168.122.209 [66539.300960] [tdb] Close table 'sessions0.tdb' Apr 26 10:33:11 192.168.122.209 [66542.517980] [tdb] Close table 'cache0.tdb' Apr 26 10:33:12 192.168.122.209 [66542.755219] [tdb] Close table 'filter0.tdb' Apr 26 10:33:12 192.168.122.209 [66542.755630] [tempesta fw] modules are stopped Apr 26 10:33:12 192.168.122.209 [66542.931072] [tempesta fw] exiting... Apr 26 10:33:12 192.168.122.209 [66543.072022] [tdb] Shutdown Tempesta DB Apr 26 10:33:12 192.168.122.209 [66543.297145] End test: t_modify_http_headers.test_logic.TestReqHeader.test_long_header_name Apr 26 10:33:12 192.168.122.209 [66543.317099] Start test: t_modify_http_headers.test_logic.TestReqHeader.test_set_exist_header Apr 26 10:33:13 192.168.122.209 [66544.524623] [tdb] Start Tempesta DB Apr 26 10:33:14 192.168.122.209 [66544.658671] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:33:15 192.168.122.209 [66546.093980] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66546.093980] Maybe that's fine, but it's worth checking the [66546.093980] config - if there is no relations between the [66546.093980] names, then host name confusion attack is possible. Apr 26 10:33:15 192.168.122.209 [66546.192649] [tempesta fw] Configuration processing is completed. Apr 26 10:33:15 192.168.122.209 [66546.249395] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:33:16 192.168.122.209 [66546.680762] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:33:16 192.168.122.209 [66546.707479] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:33:16 192.168.122.209 [66546.732934] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:33:16 192.168.122.209 [66546.800976] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:33:16 192.168.122.209 [66546.802713] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:33:16 192.168.122.209 [66546.872654] [tempesta fw] Tempesta FW is ready Apr 26 10:33:16 192.168.122.209 [66547.427730] [tdb] Close table 'client0.tdb' Apr 26 10:33:16 192.168.122.209 [66547.611799] [tdb] Close table 'sessions0.tdb' Apr 26 10:33:20 192.168.122.209 [66550.821379] [tdb] Close table 'cache0.tdb' Apr 26 10:33:20 192.168.122.209 [66551.083065] [tdb] Close table 'filter0.tdb' Apr 26 10:33:20 192.168.122.209 [66551.083513] [tempesta fw] modules are stopped Apr 26 10:33:20 192.168.122.209 [66551.281836] [tempesta fw] exiting... Apr 26 10:33:20 192.168.122.209 [66551.425993] [tdb] Shutdown Tempesta DB Apr 26 10:33:21 192.168.122.209 [66551.650142] End test: t_modify_http_headers.test_logic.TestReqHeader.test_set_exist_header Apr 26 10:33:21 192.168.122.209 [66551.679359] Start test: t_modify_http_headers.test_logic.TestReqHeader.test_set_exist_special_header Apr 26 10:33:22 192.168.122.209 [66552.978617] [tdb] Start Tempesta DB Apr 26 10:33:22 192.168.122.209 [66553.108861] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:33:24 192.168.122.209 [66554.638046] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66554.638046] Maybe that's fine, but it's worth checking the [66554.638046] config - if there is no relations between the [66554.638046] names, then host name confusion attack is possible. Apr 26 10:33:24 192.168.122.209 [66554.748839] [tempesta fw] Configuration processing is completed. Apr 26 10:33:24 192.168.122.209 [66554.804701] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:33:24 192.168.122.209 [66555.221141] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:33:24 192.168.122.209 [66555.246409] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:33:24 192.168.122.209 [66555.272281] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:33:24 192.168.122.209 [66555.320802] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:33:24 192.168.122.209 [66555.322497] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:33:24 192.168.122.209 [66555.368751] [tempesta fw] Tempesta FW is ready Apr 26 10:33:25 192.168.122.209 [66555.974907] [tdb] Close table 'client0.tdb' Apr 26 10:33:25 192.168.122.209 [66556.174883] [tdb] Close table 'sessions0.tdb' Apr 26 10:33:28 192.168.122.209 [66559.524729] [tdb] Close table 'cache0.tdb' Apr 26 10:33:29 192.168.122.209 [66559.802999] [tdb] Close table 'filter0.tdb' Apr 26 10:33:29 192.168.122.209 [66559.803424] [tempesta fw] modules are stopped Apr 26 10:33:29 192.168.122.209 [66560.023478] [tempesta fw] exiting... Apr 26 10:33:29 192.168.122.209 [66560.145999] [tdb] Shutdown Tempesta DB Apr 26 10:33:29 192.168.122.209 [66560.382486] End test: t_modify_http_headers.test_logic.TestReqHeader.test_set_exist_special_header Apr 26 10:33:29 192.168.122.209 [66560.394856] Start test: t_modify_http_headers.test_logic.TestReqHeader.test_set_header_name_greater_than_1024 Apr 26 10:33:31 192.168.122.209 [66561.735474] [tdb] Start Tempesta DB Apr 26 10:33:31 192.168.122.209 [66561.941469] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:33:32 192.168.122.209 [66563.382341] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66563.382341] Maybe that's fine, but it's worth checking the [66563.382341] config - if there is no relations between the [66563.382341] names, then host name confusion attack is possible. Apr 26 10:33:32 192.168.122.209 [66563.484959] [tempesta fw] Configuration processing is completed. Apr 26 10:33:32 192.168.122.209 [66563.566247] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:33:33 192.168.122.209 [66564.222674] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:33:33 192.168.122.209 [66564.253371] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:33:33 192.168.122.209 [66564.283402] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:33:33 192.168.122.209 [66564.344952] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:33:33 192.168.122.209 [66564.346675] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:33:33 192.168.122.209 [66564.384889] [tempesta fw] Tempesta FW is ready Apr 26 10:33:34 192.168.122.209 [66565.025619] [tdb] Close table 'client0.tdb' Apr 26 10:33:34 192.168.122.209 [66565.226545] [tdb] Close table 'sessions0.tdb' Apr 26 10:33:37 192.168.122.209 [66568.528720] [tdb] Close table 'cache0.tdb' Apr 26 10:33:38 192.168.122.209 [66568.786021] [tdb] Close table 'filter0.tdb' Apr 26 10:33:38 192.168.122.209 [66568.786471] [tempesta fw] modules are stopped Apr 26 10:33:38 192.168.122.209 [66568.984258] [tempesta fw] exiting... Apr 26 10:33:38 192.168.122.209 [66569.101335] [tdb] Shutdown Tempesta DB Apr 26 10:33:38 192.168.122.209 [66569.321272] End test: t_modify_http_headers.test_logic.TestReqHeader.test_set_header_name_greater_than_1024 Apr 26 10:33:38 192.168.122.209 [66569.334642] Start test: t_modify_http_headers.test_logic.TestReqHeader.test_set_large_header Apr 26 10:33:40 192.168.122.209 [66570.687841] [tdb] Start Tempesta DB Apr 26 10:33:40 192.168.122.209 [66570.875911] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:33:41 192.168.122.209 [66572.378289] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66572.378289] Maybe that's fine, but it's worth checking the [66572.378289] config - if there is no relations between the [66572.378289] names, then host name confusion attack is possible. Apr 26 10:33:41 192.168.122.209 [66572.493073] [tempesta fw] Configuration processing is completed. Apr 26 10:33:41 192.168.122.209 [66572.559319] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:33:42 192.168.122.209 [66573.050328] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:33:42 192.168.122.209 [66573.082981] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:33:42 192.168.122.209 [66573.112943] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:33:42 192.168.122.209 [66573.165110] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:33:42 192.168.122.209 [66573.166896] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:33:42 192.168.122.209 [66573.204975] [tempesta fw] Tempesta FW is ready Apr 26 10:33:43 192.168.122.209 [66573.906101] [tdb] Close table 'client0.tdb' Apr 26 10:33:43 192.168.122.209 [66574.116619] [tdb] Close table 'sessions0.tdb' Apr 26 10:33:46 192.168.122.209 [66577.569554] [tdb] Close table 'cache0.tdb' Apr 26 10:33:47 192.168.122.209 [66577.841101] [tdb] Close table 'filter0.tdb' Apr 26 10:33:47 192.168.122.209 [66577.841541] [tempesta fw] modules are stopped Apr 26 10:33:47 192.168.122.209 [66578.029012] [tempesta fw] exiting... Apr 26 10:33:47 192.168.122.209 [66578.173728] [tdb] Shutdown Tempesta DB Apr 26 10:33:47 192.168.122.209 [66578.427192] End test: t_modify_http_headers.test_logic.TestReqHeader.test_set_large_header Apr 26 10:33:47 192.168.122.209 [66578.460131] Start test: t_modify_http_headers.test_logic.TestReqHeader.test_set_long_header_name Apr 26 10:33:49 192.168.122.209 [66579.645434] [tdb] Start Tempesta DB Apr 26 10:33:49 192.168.122.209 [66579.814138] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:33:50 192.168.122.209 [66581.358532] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66581.358532] Maybe that's fine, but it's worth checking the [66581.358532] config - if there is no relations between the [66581.358532] names, then host name confusion attack is possible. Apr 26 10:33:50 192.168.122.209 [66581.517163] [tempesta fw] Configuration processing is completed. Apr 26 10:33:50 192.168.122.209 [66581.591500] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:33:51 192.168.122.209 [66582.187329] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:33:51 192.168.122.209 [66582.223054] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:33:51 192.168.122.209 [66582.258775] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:33:51 192.168.122.209 [66582.301132] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:33:51 192.168.122.209 [66582.302891] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:33:51 192.168.122.209 [66582.341075] [tempesta fw] Tempesta FW is ready Apr 26 10:33:52 192.168.122.209 [66582.955028] [tdb] Close table 'client0.tdb' Apr 26 10:33:52 192.168.122.209 [66583.135105] [tdb] Close table 'sessions0.tdb' Apr 26 10:33:55 192.168.122.209 [66586.410685] [tdb] Close table 'cache0.tdb' Apr 26 10:33:56 192.168.122.209 [66586.660242] [tdb] Close table 'filter0.tdb' Apr 26 10:33:56 192.168.122.209 [66586.660935] [tempesta fw] modules are stopped Apr 26 10:33:56 192.168.122.209 [66586.852195] [tempesta fw] exiting... Apr 26 10:33:56 192.168.122.209 [66586.986077] [tdb] Shutdown Tempesta DB Apr 26 10:33:56 192.168.122.209 [66587.204034] End test: t_modify_http_headers.test_logic.TestReqHeader.test_set_long_header_name Apr 26 10:33:56 192.168.122.209 [66587.224424] Start test: t_modify_http_headers.test_logic.TestReqHeader.test_set_non_exist_header Apr 26 10:33:57 192.168.122.209 [66588.477005] [tdb] Start Tempesta DB Apr 26 10:33:58 192.168.122.209 [66588.658092] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:33:59 192.168.122.209 [66590.146549] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66590.146549] Maybe that's fine, but it's worth checking the [66590.146549] config - if there is no relations between the [66590.146549] names, then host name confusion attack is possible. Apr 26 10:33:59 192.168.122.209 [66590.257283] [tempesta fw] Configuration processing is completed. Apr 26 10:33:59 192.168.122.209 [66590.318498] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:34:00 192.168.122.209 [66590.765055] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:34:00 192.168.122.209 [66590.791518] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:34:00 192.168.122.209 [66590.829185] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:34:00 192.168.122.209 [66590.881250] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:34:00 192.168.122.209 [66590.883006] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:34:00 192.168.122.209 [66590.925188] [tempesta fw] Tempesta FW is ready Apr 26 10:34:00 192.168.122.209 [66591.539238] [tdb] Close table 'client0.tdb' Apr 26 10:34:01 192.168.122.209 [66591.726320] [tdb] Close table 'sessions0.tdb' Apr 26 10:34:04 192.168.122.209 [66594.980579] [tdb] Close table 'cache0.tdb' Apr 26 10:34:04 192.168.122.209 [66595.277260] [tdb] Close table 'filter0.tdb' Apr 26 10:34:04 192.168.122.209 [66595.277677] [tempesta fw] modules are stopped Apr 26 10:34:04 192.168.122.209 [66595.481155] [tempesta fw] exiting... Apr 26 10:34:04 192.168.122.209 [66595.598904] [tdb] Shutdown Tempesta DB Apr 26 10:34:05 192.168.122.209 [66595.793366] End test: t_modify_http_headers.test_logic.TestReqHeader.test_set_non_exist_header Apr 26 10:34:05 192.168.122.209 [66595.806424] Start test: t_modify_http_headers.test_logic.TestReqHeaderH2.test_add_non_exist_header Apr 26 10:34:06 192.168.122.209 [66596.925926] [tdb] Start Tempesta DB Apr 26 10:34:06 192.168.122.209 [66597.071493] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:34:07 192.168.122.209 [66598.590563] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66598.590563] Maybe that's fine, but it's worth checking the [66598.590563] config - if there is no relations between the [66598.590563] names, then host name confusion attack is possible. Apr 26 10:34:08 192.168.122.209 [66598.697353] [tempesta fw] Configuration processing is completed. Apr 26 10:34:08 192.168.122.209 [66598.761364] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:34:08 192.168.122.209 [66599.193661] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:34:08 192.168.122.209 [66599.220423] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:34:08 192.168.122.209 [66599.246680] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:34:08 192.168.122.209 [66599.285331] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:34:08 192.168.122.209 [66599.287077] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:34:08 192.168.122.209 [66599.337270] [tempesta fw] Tempesta FW is ready Apr 26 10:34:09 192.168.122.209 [66600.061240] [tdb] Close table 'client0.tdb' Apr 26 10:34:09 192.168.122.209 [66600.244889] [tdb] Close table 'sessions0.tdb' Apr 26 10:34:13 192.168.122.209 [66603.658766] [tdb] Close table 'cache0.tdb' Apr 26 10:34:13 192.168.122.209 [66603.912771] [tdb] Close table 'filter0.tdb' Apr 26 10:34:13 192.168.122.209 [66603.913271] [tempesta fw] modules are stopped Apr 26 10:34:13 192.168.122.209 [66604.120082] [tempesta fw] exiting... Apr 26 10:34:13 192.168.122.209 [66604.255580] [tdb] Shutdown Tempesta DB Apr 26 10:34:13 192.168.122.209 [66604.515961] End test: t_modify_http_headers.test_logic.TestReqHeaderH2.test_add_non_exist_header Apr 26 10:34:13 192.168.122.209 [66604.532821] Start test: t_modify_http_headers.test_logic.TestReqHeaderH2.test_delete_headers Apr 26 10:34:15 192.168.122.209 [66605.864837] [tdb] Start Tempesta DB Apr 26 10:34:15 192.168.122.209 [66606.056504] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:34:16 192.168.122.209 [66607.522834] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66607.522834] Maybe that's fine, but it's worth checking the [66607.522834] config - if there is no relations between the [66607.522834] names, then host name confusion attack is possible. Apr 26 10:34:16 192.168.122.209 [66607.625506] [tempesta fw] Configuration processing is completed. Apr 26 10:34:17 192.168.122.209 [66607.681910] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:34:17 192.168.122.209 [66608.280849] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:34:17 192.168.122.209 [66608.315778] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:34:17 192.168.122.209 [66608.350720] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:34:17 192.168.122.209 [66608.393446] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:34:17 192.168.122.209 [66608.395218] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:34:17 192.168.122.209 [66608.433402] [tempesta fw] Tempesta FW is ready Apr 26 10:34:18 192.168.122.209 [66609.129397] [tdb] Close table 'client0.tdb' Apr 26 10:34:18 192.168.122.209 [66609.313191] [tdb] Close table 'sessions0.tdb' Apr 26 10:34:21 192.168.122.209 [66612.604248] [tdb] Close table 'cache0.tdb' Apr 26 10:34:22 192.168.122.209 [66612.859302] [tdb] Close table 'filter0.tdb' Apr 26 10:34:22 192.168.122.209 [66612.859732] [tempesta fw] modules are stopped Apr 26 10:34:22 192.168.122.209 [66613.064139] [tempesta fw] exiting... Apr 26 10:34:22 192.168.122.209 [66613.191971] [tdb] Shutdown Tempesta DB Apr 26 10:34:22 192.168.122.209 [66613.443407] End test: t_modify_http_headers.test_logic.TestReqHeaderH2.test_delete_headers Apr 26 10:34:22 192.168.122.209 [66613.457341] Start test: t_modify_http_headers.test_logic.TestReqHeaderH2.test_delete_many_headers Apr 26 10:34:24 192.168.122.209 [66614.767122] [tdb] Start Tempesta DB Apr 26 10:34:24 192.168.122.209 [66614.957675] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:34:25 192.168.122.209 [66616.422241] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66616.422241] Maybe that's fine, but it's worth checking the [66616.422241] config - if there is no relations between the [66616.422241] names, then host name confusion attack is possible. Apr 26 10:34:25 192.168.122.209 [66616.517656] [tempesta fw] Configuration processing is completed. Apr 26 10:34:25 192.168.122.209 [66616.579746] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:34:26 192.168.122.209 [66617.147033] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:34:26 192.168.122.209 [66617.181980] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:34:26 192.168.122.209 [66617.216182] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:34:26 192.168.122.209 [66617.261613] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:34:26 192.168.122.209 [66617.263401] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:34:26 192.168.122.209 [66617.317524] [tempesta fw] Tempesta FW is ready Apr 26 10:34:27 192.168.122.209 [66618.018354] [tdb] Close table 'client0.tdb' Apr 26 10:34:27 192.168.122.209 [66618.228282] [tdb] Close table 'sessions0.tdb' Apr 26 10:34:30 192.168.122.209 [66621.607593] [tdb] Close table 'cache0.tdb' Apr 26 10:34:31 192.168.122.209 [66621.862722] [tdb] Close table 'filter0.tdb' Apr 26 10:34:31 192.168.122.209 [66621.863148] [tempesta fw] modules are stopped Apr 26 10:34:31 192.168.122.209 [66622.093922] [tempesta fw] exiting... Apr 26 10:34:31 192.168.122.209 [66622.237417] [tdb] Shutdown Tempesta DB Apr 26 10:34:31 192.168.122.209 [66622.517239] End test: t_modify_http_headers.test_logic.TestReqHeaderH2.test_delete_many_headers Apr 26 10:34:31 192.168.122.209 [66622.529177] Start test: t_modify_http_headers.test_logic.TestReqHeaderH2.test_delete_many_special_headers Apr 26 10:34:33 192.168.122.209 [66623.895467] [tdb] Start Tempesta DB Apr 26 10:34:33 192.168.122.209 [66624.049321] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:34:34 192.168.122.209 [66625.495060] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66625.495060] Maybe that's fine, but it's worth checking the [66625.495060] config - if there is no relations between the [66625.495060] names, then host name confusion attack is possible. Apr 26 10:34:34 192.168.122.209 [66625.601720] [tempesta fw] Configuration processing is completed. Apr 26 10:34:35 192.168.122.209 [66625.657079] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:34:35 192.168.122.209 [66626.201964] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:34:35 192.168.122.209 [66626.235485] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:34:35 192.168.122.209 [66626.270422] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:34:35 192.168.122.209 [66626.325680] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:34:35 192.168.122.209 [66626.327480] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:34:35 192.168.122.209 [66626.365626] [tempesta fw] Tempesta FW is ready Apr 26 10:34:36 192.168.122.209 [66627.082011] [tdb] Close table 'client0.tdb' Apr 26 10:34:36 192.168.122.209 [66627.260112] [tdb] Close table 'sessions0.tdb' Apr 26 10:34:40 192.168.122.209 [66631.024192] [tdb] Close table 'cache0.tdb' Apr 26 10:34:40 192.168.122.209 [66631.336660] [tdb] Close table 'filter0.tdb' Apr 26 10:34:40 192.168.122.209 [66631.337106] [tempesta fw] modules are stopped Apr 26 10:34:40 192.168.122.209 [66631.524779] [tempesta fw] exiting... Apr 26 10:34:41 192.168.122.209 [66631.693047] [tdb] Shutdown Tempesta DB Apr 26 10:34:41 192.168.122.209 [66631.954284] End test: t_modify_http_headers.test_logic.TestReqHeaderH2.test_delete_many_special_headers Apr 26 10:34:41 192.168.122.209 [66631.968495] Start test: t_modify_http_headers.test_logic.TestReqHeaderH2.test_delete_non_exist_header Apr 26 10:34:42 192.168.122.209 [66633.259651] [tdb] Start Tempesta DB Apr 26 10:34:42 192.168.122.209 [66633.424346] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:34:44 192.168.122.209 [66635.003111] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66635.003111] Maybe that's fine, but it's worth checking the [66635.003111] config - if there is no relations between the [66635.003111] names, then host name confusion attack is possible. Apr 26 10:34:44 192.168.122.209 [66635.101850] [tempesta fw] Configuration processing is completed. Apr 26 10:34:44 192.168.122.209 [66635.168615] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:34:45 192.168.122.209 [66635.782019] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:34:45 192.168.122.209 [66635.838460] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:34:45 192.168.122.209 [66635.893783] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:34:45 192.168.122.209 [66635.949794] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:34:45 192.168.122.209 [66635.951618] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:34:45 192.168.122.209 [66635.989745] [tempesta fw] Tempesta FW is ready Apr 26 10:34:46 192.168.122.209 [66636.652389] [tdb] Close table 'client0.tdb' Apr 26 10:34:46 192.168.122.209 [66636.850618] [tdb] Close table 'sessions0.tdb' Apr 26 10:34:49 192.168.122.209 [66640.020638] [tdb] Close table 'cache0.tdb' Apr 26 10:34:49 192.168.122.209 [66640.260456] [tdb] Close table 'filter0.tdb' Apr 26 10:34:49 192.168.122.209 [66640.260933] [tempesta fw] modules are stopped Apr 26 10:34:49 192.168.122.209 [66640.486300] [tempesta fw] exiting... Apr 26 10:34:49 192.168.122.209 [66640.612884] [tdb] Shutdown Tempesta DB Apr 26 10:34:50 192.168.122.209 [66640.840313] End test: t_modify_http_headers.test_logic.TestReqHeaderH2.test_delete_non_exist_header Apr 26 10:34:50 192.168.122.209 [66640.857665] Start test: t_modify_http_headers.test_logic.TestReqHeaderH2.test_delete_special_headers Apr 26 10:34:51 192.168.122.209 [66642.150922] [tdb] Start Tempesta DB Apr 26 10:34:51 192.168.122.209 [66642.311917] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:34:53 192.168.122.209 [66643.743133] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66643.743133] Maybe that's fine, but it's worth checking the [66643.743133] config - if there is no relations between the [66643.743133] names, then host name confusion attack is possible. Apr 26 10:34:53 192.168.122.209 [66643.841926] [tempesta fw] Configuration processing is completed. Apr 26 10:34:53 192.168.122.209 [66643.905796] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:34:53 192.168.122.209 [66644.421514] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:34:53 192.168.122.209 [66644.453318] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:34:53 192.168.122.209 [66644.485578] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:34:53 192.168.122.209 [66644.545908] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:34:53 192.168.122.209 [66644.547707] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:34:53 192.168.122.209 [66644.585844] [tempesta fw] Tempesta FW is ready Apr 26 10:34:54 192.168.122.209 [66645.259861] [tdb] Close table 'client0.tdb' Apr 26 10:34:54 192.168.122.209 [66645.437190] [tdb] Close table 'sessions0.tdb' Apr 26 10:34:57 192.168.122.209 [66648.591031] [tdb] Close table 'cache0.tdb' Apr 26 10:34:58 192.168.122.209 [66648.815448] [tdb] Close table 'filter0.tdb' Apr 26 10:34:58 192.168.122.209 [66648.815874] [tempesta fw] modules are stopped Apr 26 10:34:58 192.168.122.209 [66649.049600] [tempesta fw] exiting... Apr 26 10:34:58 192.168.122.209 [66649.183766] [tdb] Shutdown Tempesta DB Apr 26 10:34:58 192.168.122.209 [66649.410503] End test: t_modify_http_headers.test_logic.TestReqHeaderH2.test_delete_special_headers Apr 26 10:34:58 192.168.122.209 [66649.417979] Start test: t_modify_http_headers.test_logic.TestReqHeaderH2.test_long_header_name Apr 26 10:34:59 192.168.122.209 [66650.621326] [tdb] Start Tempesta DB Apr 26 10:35:00 192.168.122.209 [66650.774989] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:35:01 192.168.122.209 [66652.259264] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66652.259264] Maybe that's fine, but it's worth checking the [66652.259264] config - if there is no relations between the [66652.259264] names, then host name confusion attack is possible. Apr 26 10:35:01 192.168.122.209 [66652.362026] [tempesta fw] Configuration processing is completed. Apr 26 10:35:01 192.168.122.209 [66652.425406] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:35:02 192.168.122.209 [66652.946641] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:35:02 192.168.122.209 [66652.978671] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:35:02 192.168.122.209 [66653.011500] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:35:02 192.168.122.209 [66653.066015] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:35:02 192.168.122.209 [66653.067798] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:35:02 192.168.122.209 [66653.113948] [tempesta fw] Tempesta FW is ready Apr 26 10:35:04 192.168.122.209 [66655.194406] [tdb] Close table 'client0.tdb' Apr 26 10:35:04 192.168.122.209 [66655.411991] [tdb] Close table 'sessions0.tdb' Apr 26 10:35:08 192.168.122.209 [66658.646065] [tdb] Close table 'cache0.tdb' Apr 26 10:35:08 192.168.122.209 [66658.896882] [tdb] Close table 'filter0.tdb' Apr 26 10:35:08 192.168.122.209 [66658.897417] [tempesta fw] modules are stopped Apr 26 10:35:08 192.168.122.209 [66659.096240] [tempesta fw] exiting... Apr 26 10:35:08 192.168.122.209 [66659.212954] [tdb] Shutdown Tempesta DB Apr 26 10:35:08 192.168.122.209 [66659.434818] End test: t_modify_http_headers.test_logic.TestReqHeaderH2.test_long_header_name Apr 26 10:35:08 192.168.122.209 [66659.458243] Start test: t_modify_http_headers.test_logic.TestReqHeaderH2.test_set_exist_header Apr 26 10:35:10 192.168.122.209 [66660.665571] [tdb] Start Tempesta DB Apr 26 10:35:10 192.168.122.209 [66660.813031] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:35:11 192.168.122.209 [66662.435407] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66662.435407] Maybe that's fine, but it's worth checking the [66662.435407] config - if there is no relations between the [66662.435407] names, then host name confusion attack is possible. Apr 26 10:35:11 192.168.122.209 [66662.530154] [tempesta fw] Configuration processing is completed. Apr 26 10:35:11 192.168.122.209 [66662.599385] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:35:12 192.168.122.209 [66663.057817] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:35:12 192.168.122.209 [66663.087785] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:35:12 192.168.122.209 [66663.133250] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:35:12 192.168.122.209 [66663.190121] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:35:12 192.168.122.209 [66663.191846] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:35:12 192.168.122.209 [66663.230071] [tempesta fw] Tempesta FW is ready Apr 26 10:35:13 192.168.122.209 [66663.884948] [tdb] Close table 'client0.tdb' Apr 26 10:35:13 192.168.122.209 [66664.166185] [tdb] Close table 'sessions0.tdb' Apr 26 10:35:16 192.168.122.209 [66667.557446] [tdb] Close table 'cache0.tdb' Apr 26 10:35:17 192.168.122.209 [66667.795498] [tdb] Close table 'filter0.tdb' Apr 26 10:35:17 192.168.122.209 [66667.795933] [tempesta fw] modules are stopped Apr 26 10:35:17 192.168.122.209 [66668.034055] [tempesta fw] exiting... Apr 26 10:35:17 192.168.122.209 [66668.148805] [tdb] Shutdown Tempesta DB Apr 26 10:35:17 192.168.122.209 [66668.378527] End test: t_modify_http_headers.test_logic.TestReqHeaderH2.test_set_exist_header Apr 26 10:35:17 192.168.122.209 [66668.393690] Start test: t_modify_http_headers.test_logic.TestReqHeaderH2.test_set_exist_special_header Apr 26 10:35:18 192.168.122.209 [66669.610517] [tdb] Start Tempesta DB Apr 26 10:35:19 192.168.122.209 [66669.764829] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:35:20 192.168.122.209 [66671.175561] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66671.175561] Maybe that's fine, but it's worth checking the [66671.175561] config - if there is no relations between the [66671.175561] names, then host name confusion attack is possible. Apr 26 10:35:20 192.168.122.209 [66671.278301] [tempesta fw] Configuration processing is completed. Apr 26 10:35:20 192.168.122.209 [66671.341373] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:35:21 192.168.122.209 [66671.806253] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:35:21 192.168.122.209 [66671.852127] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:35:21 192.168.122.209 [66671.886686] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:35:21 192.168.122.209 [66671.946271] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:35:21 192.168.122.209 [66671.948071] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:35:21 192.168.122.209 [66671.986165] [tempesta fw] Tempesta FW is ready Apr 26 10:35:22 192.168.122.209 [66672.681333] [tdb] Close table 'client0.tdb' Apr 26 10:35:22 192.168.122.209 [66672.868697] [tdb] Close table 'sessions0.tdb' Apr 26 10:35:25 192.168.122.209 [66676.120070] [tdb] Close table 'cache0.tdb' Apr 26 10:35:25 192.168.122.209 [66676.358600] [tdb] Close table 'filter0.tdb' Apr 26 10:35:25 192.168.122.209 [66676.359066] [tempesta fw] modules are stopped Apr 26 10:35:25 192.168.122.209 [66676.575977] [tempesta fw] exiting... Apr 26 10:35:26 192.168.122.209 [66676.708317] [tdb] Shutdown Tempesta DB Apr 26 10:35:26 192.168.122.209 [66676.919896] End test: t_modify_http_headers.test_logic.TestReqHeaderH2.test_set_exist_special_header Apr 26 10:35:26 192.168.122.209 [66676.953040] Start test: t_modify_http_headers.test_logic.TestReqHeaderH2.test_set_header_name_greater_than_1024 Apr 26 10:35:27 192.168.122.209 [66678.220538] [tdb] Start Tempesta DB Apr 26 10:35:27 192.168.122.209 [66678.364159] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:35:29 192.168.122.209 [66679.779564] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66679.779564] Maybe that's fine, but it's worth checking the [66679.779564] config - if there is no relations between the [66679.779564] names, then host name confusion attack is possible. Apr 26 10:35:29 192.168.122.209 [66679.898671] [tempesta fw] Configuration processing is completed. Apr 26 10:35:29 192.168.122.209 [66679.953350] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:35:29 192.168.122.209 [66680.404701] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:35:29 192.168.122.209 [66680.434839] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:35:29 192.168.122.209 [66680.466001] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:35:29 192.168.122.209 [66680.510322] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:35:29 192.168.122.209 [66680.512065] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:35:29 192.168.122.209 [66680.550273] [tempesta fw] Tempesta FW is ready Apr 26 10:35:30 192.168.122.209 [66681.218961] [tdb] Close table 'client0.tdb' Apr 26 10:35:30 192.168.122.209 [66681.407157] [tdb] Close table 'sessions0.tdb' Apr 26 10:35:33 192.168.122.209 [66684.641678] [tdb] Close table 'cache0.tdb' Apr 26 10:35:34 192.168.122.209 [66684.863521] [tdb] Close table 'filter0.tdb' Apr 26 10:35:34 192.168.122.209 [66684.863950] [tempesta fw] modules are stopped Apr 26 10:35:34 192.168.122.209 [66685.078477] [tempesta fw] exiting... Apr 26 10:35:34 192.168.122.209 [66685.196312] [tdb] Shutdown Tempesta DB Apr 26 10:35:34 192.168.122.209 [66685.430274] End test: t_modify_http_headers.test_logic.TestReqHeaderH2.test_set_header_name_greater_than_1024 Apr 26 10:35:34 192.168.122.209 [66685.442602] Start test: t_modify_http_headers.test_logic.TestReqHeaderH2.test_set_large_header Apr 26 10:35:36 192.168.122.209 [66686.710710] [tdb] Start Tempesta DB Apr 26 10:35:36 192.168.122.209 [66686.876423] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:35:37 192.168.122.209 [66688.411757] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66688.411757] Maybe that's fine, but it's worth checking the [66688.411757] config - if there is no relations between the [66688.411757] names, then host name confusion attack is possible. Apr 26 10:35:37 192.168.122.209 [66688.522433] [tempesta fw] Configuration processing is completed. Apr 26 10:35:37 192.168.122.209 [66688.582492] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:35:38 192.168.122.209 [66689.102052] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:35:38 192.168.122.209 [66689.143400] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:35:38 192.168.122.209 [66689.176587] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:35:38 192.168.122.209 [66689.230462] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:35:38 192.168.122.209 [66689.232258] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:35:38 192.168.122.209 [66689.274405] [tempesta fw] Tempesta FW is ready Apr 26 10:35:39 192.168.122.209 [66689.981852] [tdb] Close table 'client0.tdb' Apr 26 10:35:39 192.168.122.209 [66690.167650] [tdb] Close table 'sessions0.tdb' Apr 26 10:35:42 192.168.122.209 [66693.428632] [tdb] Close table 'cache0.tdb' Apr 26 10:35:43 192.168.122.209 [66693.688206] [tdb] Close table 'filter0.tdb' Apr 26 10:35:43 192.168.122.209 [66693.688654] [tempesta fw] modules are stopped Apr 26 10:35:43 192.168.122.209 [66693.908548] [tempesta fw] exiting... Apr 26 10:35:43 192.168.122.209 [66693.999564] [tdb] Shutdown Tempesta DB Apr 26 10:35:43 192.168.122.209 [66694.232118] End test: t_modify_http_headers.test_logic.TestReqHeaderH2.test_set_large_header Apr 26 10:35:43 192.168.122.209 [66694.253056] Start test: t_modify_http_headers.test_logic.TestReqHeaderH2.test_set_long_header_name Apr 26 10:35:44 192.168.122.209 [66695.437797] [tdb] Start Tempesta DB Apr 26 10:35:44 192.168.122.209 [66695.583504] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:35:46 192.168.122.209 [66697.135793] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66697.135793] Maybe that's fine, but it's worth checking the [66697.135793] config - if there is no relations between the [66697.135793] names, then host name confusion attack is possible. Apr 26 10:35:46 192.168.122.209 [66697.310867] [tempesta fw] Configuration processing is completed. Apr 26 10:35:46 192.168.122.209 [66697.367702] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:35:47 192.168.122.209 [66697.841515] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:35:47 192.168.122.209 [66697.872590] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:35:47 192.168.122.209 [66697.905850] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:35:47 192.168.122.209 [66697.982593] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:35:47 192.168.122.209 [66697.984384] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:35:47 192.168.122.209 [66698.022500] [tempesta fw] Tempesta FW is ready Apr 26 10:35:48 192.168.122.209 [66698.707538] [tdb] Close table 'client0.tdb' Apr 26 10:35:48 192.168.122.209 [66698.925936] [tdb] Close table 'sessions0.tdb' Apr 26 10:35:51 192.168.122.209 [66702.182924] [tdb] Close table 'cache0.tdb' Apr 26 10:35:51 192.168.122.209 [66702.438647] [tdb] Close table 'filter0.tdb' Apr 26 10:35:51 192.168.122.209 [66702.439090] [tempesta fw] modules are stopped Apr 26 10:35:52 192.168.122.209 [66702.662920] [tempesta fw] exiting... Apr 26 10:35:52 192.168.122.209 [66702.804673] [tdb] Shutdown Tempesta DB Apr 26 10:35:52 192.168.122.209 [66703.032065] End test: t_modify_http_headers.test_logic.TestReqHeaderH2.test_set_long_header_name Apr 26 10:35:52 192.168.122.209 [66703.047462] Start test: t_modify_http_headers.test_logic.TestReqHeaderH2.test_set_non_exist_header Apr 26 10:35:53 192.168.122.209 [66704.200114] [tdb] Start Tempesta DB Apr 26 10:35:53 192.168.122.209 [66704.342174] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:35:55 192.168.122.209 [66705.871957] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66705.871957] Maybe that's fine, but it's worth checking the [66705.871957] config - if there is no relations between the [66705.871957] names, then host name confusion attack is possible. Apr 26 10:35:55 192.168.122.209 [66705.978696] [tempesta fw] Configuration processing is completed. Apr 26 10:35:55 192.168.122.209 [66706.034347] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:35:55 192.168.122.209 [66706.485826] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:35:55 192.168.122.209 [66706.514676] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:35:55 192.168.122.209 [66706.543117] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:35:55 192.168.122.209 [66706.590592] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:35:55 192.168.122.209 [66706.592306] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:35:55 192.168.122.209 [66706.630586] [tempesta fw] Tempesta FW is ready Apr 26 10:35:56 192.168.122.209 [66707.286338] [tdb] Close table 'client0.tdb' Apr 26 10:35:56 192.168.122.209 [66707.493751] [tdb] Close table 'sessions0.tdb' Apr 26 10:36:00 192.168.122.209 [66710.748369] [tdb] Close table 'cache0.tdb' Apr 26 10:36:00 192.168.122.209 [66710.974379] [tdb] Close table 'filter0.tdb' Apr 26 10:36:00 192.168.122.209 [66710.974824] [tempesta fw] modules are stopped Apr 26 10:36:00 192.168.122.209 [66711.177390] [tempesta fw] exiting... Apr 26 10:36:00 192.168.122.209 [66711.310134] [tdb] Shutdown Tempesta DB Apr 26 10:36:00 192.168.122.209 [66711.522641] End test: t_modify_http_headers.test_logic.TestReqHeaderH2.test_set_non_exist_header Apr 26 10:36:00 192.168.122.209 [66711.534951] Start test: t_modify_http_headers.test_logic.TestRespHeader.test_add_non_exist_header Apr 26 10:36:02 192.168.122.209 [66712.700507] [tdb] Start Tempesta DB Apr 26 10:36:02 192.168.122.209 [66712.848849] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:36:03 192.168.122.209 [66714.400079] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66714.400079] Maybe that's fine, but it's worth checking the [66714.400079] config - if there is no relations between the [66714.400079] names, then host name confusion attack is possible. Apr 26 10:36:03 192.168.122.209 [66714.506745] [tempesta fw] Configuration processing is completed. Apr 26 10:36:03 192.168.122.209 [66714.576706] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:36:04 192.168.122.209 [66715.053557] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:36:04 192.168.122.209 [66715.084317] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:36:04 192.168.122.209 [66715.113847] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:36:04 192.168.122.209 [66715.158751] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:36:04 192.168.122.209 [66715.160468] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:36:04 192.168.122.209 [66715.198707] [tempesta fw] Tempesta FW is ready Apr 26 10:36:05 192.168.122.209 [66715.782754] [tdb] Close table 'client0.tdb' Apr 26 10:36:05 192.168.122.209 [66715.992666] [tdb] Close table 'sessions0.tdb' Apr 26 10:36:08 192.168.122.209 [66719.214801] [tdb] Close table 'cache0.tdb' Apr 26 10:36:08 192.168.122.209 [66719.463287] [tdb] Close table 'filter0.tdb' Apr 26 10:36:08 192.168.122.209 [66719.463737] [tempesta fw] modules are stopped Apr 26 10:36:09 192.168.122.209 [66719.665166] [tempesta fw] exiting... Apr 26 10:36:09 192.168.122.209 [66719.758815] [tdb] Shutdown Tempesta DB Apr 26 10:36:09 192.168.122.209 [66719.981127] End test: t_modify_http_headers.test_logic.TestRespHeader.test_add_non_exist_header Apr 26 10:36:09 192.168.122.209 [66719.991387] Start test: t_modify_http_headers.test_logic.TestRespHeader.test_delete_headers Apr 26 10:36:10 192.168.122.209 [66721.313105] [tdb] Start Tempesta DB Apr 26 10:36:10 192.168.122.209 [66721.465954] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:36:12 192.168.122.209 [66722.896142] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66722.896142] Maybe that's fine, but it's worth checking the [66722.896142] config - if there is no relations between the [66722.896142] names, then host name confusion attack is possible. Apr 26 10:36:12 192.168.122.209 [66722.998930] [tempesta fw] Configuration processing is completed. Apr 26 10:36:12 192.168.122.209 [66723.065750] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:36:12 192.168.122.209 [66723.547980] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:36:12 192.168.122.209 [66723.579317] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:36:12 192.168.122.209 [66723.610601] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:36:13 192.168.122.209 [66723.662876] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:36:13 192.168.122.209 [66723.664594] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:36:13 192.168.122.209 [66723.714808] [tempesta fw] Tempesta FW is ready Apr 26 10:36:13 192.168.122.209 [66724.300609] [tdb] Close table 'client0.tdb' Apr 26 10:36:13 192.168.122.209 [66724.502880] [tdb] Close table 'sessions0.tdb' Apr 26 10:36:17 192.168.122.209 [66727.744847] [tdb] Close table 'cache0.tdb' Apr 26 10:36:17 192.168.122.209 [66727.993437] [tdb] Close table 'filter0.tdb' Apr 26 10:36:17 192.168.122.209 [66727.993910] [tempesta fw] modules are stopped Apr 26 10:36:17 192.168.122.209 [66728.170856] [tempesta fw] exiting... Apr 26 10:36:17 192.168.122.209 [66728.314865] [tdb] Shutdown Tempesta DB Apr 26 10:36:17 192.168.122.209 [66728.515134] End test: t_modify_http_headers.test_logic.TestRespHeader.test_delete_headers Apr 26 10:36:17 192.168.122.209 [66728.538160] Start test: t_modify_http_headers.test_logic.TestRespHeader.test_delete_many_headers Apr 26 10:36:19 192.168.122.209 [66729.791405] [tdb] Start Tempesta DB Apr 26 10:36:19 192.168.122.209 [66729.951450] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:36:20 192.168.122.209 [66731.368303] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66731.368303] Maybe that's fine, but it's worth checking the [66731.368303] config - if there is no relations between the [66731.368303] names, then host name confusion attack is possible. Apr 26 10:36:20 192.168.122.209 [66731.471054] [tempesta fw] Configuration processing is completed. Apr 26 10:36:20 192.168.122.209 [66731.536243] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:36:21 192.168.122.209 [66732.043349] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:36:21 192.168.122.209 [66732.074849] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:36:21 192.168.122.209 [66732.104661] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:36:21 192.168.122.209 [66732.142978] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:36:21 192.168.122.209 [66732.144716] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:36:21 192.168.122.209 [66732.182929] [tempesta fw] Tempesta FW is ready Apr 26 10:36:22 192.168.122.209 [66732.810589] [tdb] Close table 'client0.tdb' Apr 26 10:36:22 192.168.122.209 [66732.996672] [tdb] Close table 'sessions0.tdb' Apr 26 10:36:25 192.168.122.209 [66736.256321] [tdb] Close table 'cache0.tdb' Apr 26 10:36:25 192.168.122.209 [66736.485996] [tdb] Close table 'filter0.tdb' Apr 26 10:36:25 192.168.122.209 [66736.486422] [tempesta fw] modules are stopped Apr 26 10:36:26 192.168.122.209 [66736.676446] [tempesta fw] exiting... Apr 26 10:36:26 192.168.122.209 [66736.805000] [tdb] Shutdown Tempesta DB Apr 26 10:36:26 192.168.122.209 [66737.020528] End test: t_modify_http_headers.test_logic.TestRespHeader.test_delete_many_headers Apr 26 10:36:26 192.168.122.209 [66737.040559] Start test: t_modify_http_headers.test_logic.TestRespHeader.test_delete_many_special_headers Apr 26 10:36:27 192.168.122.209 [66738.323629] [tdb] Start Tempesta DB Apr 26 10:36:27 192.168.122.209 [66738.468511] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:36:29 192.168.122.209 [66739.827940] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66739.827940] Maybe that's fine, but it's worth checking the [66739.827940] config - if there is no relations between the [66739.827940] names, then host name confusion attack is possible. Apr 26 10:36:29 192.168.122.209 [66739.927106] [tempesta fw] Configuration processing is completed. Apr 26 10:36:29 192.168.122.209 [66739.981382] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:36:29 192.168.122.209 [66740.436904] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:36:29 192.168.122.209 [66740.466777] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:36:29 192.168.122.209 [66740.496209] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:36:29 192.168.122.209 [66740.535100] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:36:29 192.168.122.209 [66740.536855] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:36:29 192.168.122.209 [66740.575020] [tempesta fw] Tempesta FW is ready Apr 26 10:36:30 192.168.122.209 [66741.216103] [tdb] Close table 'client0.tdb' Apr 26 10:36:30 192.168.122.209 [66741.414534] [tdb] Close table 'sessions0.tdb' Apr 26 10:36:33 192.168.122.209 [66744.596414] [tdb] Close table 'cache0.tdb' Apr 26 10:36:34 192.168.122.209 [66744.830129] [tdb] Close table 'filter0.tdb' Apr 26 10:36:34 192.168.122.209 [66744.830557] [tempesta fw] modules are stopped Apr 26 10:36:34 192.168.122.209 [66745.060390] [tempesta fw] exiting... Apr 26 10:36:34 192.168.122.209 [66745.189328] [tdb] Shutdown Tempesta DB Apr 26 10:36:34 192.168.122.209 [66745.406192] End test: t_modify_http_headers.test_logic.TestRespHeader.test_delete_many_special_headers Apr 26 10:36:34 192.168.122.209 [66745.418361] Start test: t_modify_http_headers.test_logic.TestRespHeader.test_delete_non_exist_header Apr 26 10:36:35 192.168.122.209 [66746.595471] [tdb] Start Tempesta DB Apr 26 10:36:36 192.168.122.209 [66746.743890] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:36:37 192.168.122.209 [66748.200012] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66748.200012] Maybe that's fine, but it's worth checking the [66748.200012] config - if there is no relations between the [66748.200012] names, then host name confusion attack is possible. Apr 26 10:36:37 192.168.122.209 [66748.303207] [tempesta fw] Configuration processing is completed. Apr 26 10:36:37 192.168.122.209 [66748.365577] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:36:38 192.168.122.209 [66748.832051] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:36:38 192.168.122.209 [66748.861410] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:36:38 192.168.122.209 [66748.890656] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:36:38 192.168.122.209 [66748.947159] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:36:38 192.168.122.209 [66748.948891] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:36:38 192.168.122.209 [66748.987121] [tempesta fw] Tempesta FW is ready Apr 26 10:36:38 192.168.122.209 [66749.582757] [tdb] Close table 'client0.tdb' Apr 26 10:36:39 192.168.122.209 [66749.765770] [tdb] Close table 'sessions0.tdb' Apr 26 10:36:42 192.168.122.209 [66753.043717] [tdb] Close table 'cache0.tdb' Apr 26 10:36:42 192.168.122.209 [66753.281589] [tdb] Close table 'filter0.tdb' Apr 26 10:36:42 192.168.122.209 [66753.282033] [tempesta fw] modules are stopped Apr 26 10:36:42 192.168.122.209 [66753.493784] [tempesta fw] exiting... Apr 26 10:36:42 192.168.122.209 [66753.640941] [tdb] Shutdown Tempesta DB Apr 26 10:36:43 192.168.122.209 [66753.869826] End test: t_modify_http_headers.test_logic.TestRespHeader.test_delete_non_exist_header Apr 26 10:36:43 192.168.122.209 [66753.884225] Start test: t_modify_http_headers.test_logic.TestRespHeader.test_delete_special_headers Apr 26 10:36:44 192.168.122.209 [66755.058321] [tdb] Start Tempesta DB Apr 26 10:36:44 192.168.122.209 [66755.237536] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:36:46 192.168.122.209 [66756.712593] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66756.712593] Maybe that's fine, but it's worth checking the [66756.712593] config - if there is no relations between the [66756.712593] names, then host name confusion attack is possible. Apr 26 10:36:46 192.168.122.209 [66756.819386] [tempesta fw] Configuration processing is completed. Apr 26 10:36:46 192.168.122.209 [66756.883541] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:36:46 192.168.122.209 [66757.392117] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:36:46 192.168.122.209 [66757.423223] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:36:46 192.168.122.209 [66757.454490] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:36:46 192.168.122.209 [66757.499274] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:36:46 192.168.122.209 [66757.500995] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:36:46 192.168.122.209 [66757.539242] [tempesta fw] Tempesta FW is ready Apr 26 10:36:47 192.168.122.209 [66758.117521] [tdb] Close table 'client0.tdb' Apr 26 10:36:47 192.168.122.209 [66758.299831] [tdb] Close table 'sessions0.tdb' Apr 26 10:36:50 192.168.122.209 [66761.643678] [tdb] Close table 'cache0.tdb' Apr 26 10:36:51 192.168.122.209 [66761.892476] [tdb] Close table 'filter0.tdb' Apr 26 10:36:51 192.168.122.209 [66761.892933] [tempesta fw] modules are stopped Apr 26 10:36:51 192.168.122.209 [66762.120324] [tempesta fw] exiting... Apr 26 10:36:51 192.168.122.209 [66762.236948] [tdb] Shutdown Tempesta DB Apr 26 10:36:51 192.168.122.209 [66762.473840] End test: t_modify_http_headers.test_logic.TestRespHeader.test_delete_special_headers Apr 26 10:36:51 192.168.122.209 [66762.495783] Start test: t_modify_http_headers.test_logic.TestRespHeader.test_long_header_name Apr 26 10:36:53 192.168.122.209 [66763.715827] [tdb] Start Tempesta DB Apr 26 10:36:53 192.168.122.209 [66763.881319] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:36:54 192.168.122.209 [66765.388760] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66765.388760] Maybe that's fine, but it's worth checking the [66765.388760] config - if there is no relations between the [66765.388760] names, then host name confusion attack is possible. Apr 26 10:36:54 192.168.122.209 [66765.495423] [tempesta fw] Configuration processing is completed. Apr 26 10:36:54 192.168.122.209 [66765.571484] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:36:55 192.168.122.209 [66766.165833] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:36:55 192.168.122.209 [66766.203491] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:36:55 192.168.122.209 [66766.238728] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:36:55 192.168.122.209 [66766.279345] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:36:55 192.168.122.209 [66766.280353] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:36:55 192.168.122.209 [66766.319358] [tempesta fw] Tempesta FW is ready Apr 26 10:36:57 192.168.122.209 [66768.165021] [tdb] Close table 'client0.tdb' Apr 26 10:36:57 192.168.122.209 [66768.351749] [tdb] Close table 'sessions0.tdb' Apr 26 10:37:01 192.168.122.209 [66771.855063] [tdb] Close table 'cache0.tdb' Apr 26 10:37:01 192.168.122.209 [66772.128949] [tdb] Close table 'filter0.tdb' Apr 26 10:37:01 192.168.122.209 [66772.129456] [tempesta fw] modules are stopped Apr 26 10:37:01 192.168.122.209 [66772.325319] [tempesta fw] exiting... Apr 26 10:37:01 192.168.122.209 [66772.466082] [tdb] Shutdown Tempesta DB Apr 26 10:37:02 192.168.122.209 [66772.717329] End test: t_modify_http_headers.test_logic.TestRespHeader.test_long_header_name Apr 26 10:37:02 192.168.122.209 [66772.728289] Start test: t_modify_http_headers.test_logic.TestRespHeader.test_set_exist_header Apr 26 10:37:03 192.168.122.209 [66774.116559] [tdb] Start Tempesta DB Apr 26 10:37:03 192.168.122.209 [66774.268611] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:37:05 192.168.122.209 [66775.744897] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66775.744897] Maybe that's fine, but it's worth checking the [66775.744897] config - if there is no relations between the [66775.744897] names, then host name confusion attack is possible. Apr 26 10:37:05 192.168.122.209 [66775.843559] [tempesta fw] Configuration processing is completed. Apr 26 10:37:05 192.168.122.209 [66775.920770] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:37:05 192.168.122.209 [66776.635911] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:37:06 192.168.122.209 [66776.687660] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:37:06 192.168.122.209 [66776.737519] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:37:06 192.168.122.209 [66776.787560] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:37:06 192.168.122.209 [66776.789392] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:37:06 192.168.122.209 [66776.827462] [tempesta fw] Tempesta FW is ready Apr 26 10:37:06 192.168.122.209 [66777.437575] [tdb] Close table 'client0.tdb' Apr 26 10:37:06 192.168.122.209 [66777.622875] [tdb] Close table 'sessions0.tdb' Apr 26 10:37:10 192.168.122.209 [66780.895949] [tdb] Close table 'cache0.tdb' Apr 26 10:37:10 192.168.122.209 [66781.156546] [tdb] Close table 'filter0.tdb' Apr 26 10:37:10 192.168.122.209 [66781.156967] [tempesta fw] modules are stopped Apr 26 10:37:10 192.168.122.209 [66781.350662] [tempesta fw] exiting... Apr 26 10:37:10 192.168.122.209 [66781.466150] [tdb] Shutdown Tempesta DB Apr 26 10:37:11 192.168.122.209 [66781.675804] End test: t_modify_http_headers.test_logic.TestRespHeader.test_set_exist_header Apr 26 10:37:11 192.168.122.209 [66781.686761] Start test: t_modify_http_headers.test_logic.TestRespHeader.test_set_exist_special_header Apr 26 10:37:12 192.168.122.209 [66782.949666] [tdb] Start Tempesta DB Apr 26 10:37:12 192.168.122.209 [66783.097855] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:37:14 192.168.122.209 [66784.664987] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66784.664987] Maybe that's fine, but it's worth checking the [66784.664987] config - if there is no relations between the [66784.664987] names, then host name confusion attack is possible. Apr 26 10:37:14 192.168.122.209 [66784.779945] [tempesta fw] Configuration processing is completed. Apr 26 10:37:14 192.168.122.209 [66784.844955] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:37:14 192.168.122.209 [66785.404974] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:37:14 192.168.122.209 [66785.439527] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:37:14 192.168.122.209 [66785.478816] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:37:14 192.168.122.209 [66785.559812] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:37:14 192.168.122.209 [66785.561617] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:37:14 192.168.122.209 [66785.611587] [tempesta fw] Tempesta FW is ready Apr 26 10:37:15 192.168.122.209 [66786.239121] [tdb] Close table 'client0.tdb' Apr 26 10:37:15 192.168.122.209 [66786.447198] [tdb] Close table 'sessions0.tdb' Apr 26 10:37:19 192.168.122.209 [66789.678554] [tdb] Close table 'cache0.tdb' Apr 26 10:37:19 192.168.122.209 [66789.901271] [tdb] Close table 'filter0.tdb' Apr 26 10:37:19 192.168.122.209 [66789.901733] [tempesta fw] modules are stopped Apr 26 10:37:19 192.168.122.209 [66790.080492] [tempesta fw] exiting... Apr 26 10:37:19 192.168.122.209 [66790.216362] [tdb] Shutdown Tempesta DB Apr 26 10:37:19 192.168.122.209 [66790.433243] End test: t_modify_http_headers.test_logic.TestRespHeader.test_set_exist_special_header Apr 26 10:37:19 192.168.122.209 [66790.442742] Start test: t_modify_http_headers.test_logic.TestRespHeader.test_set_header_name_greater_than_1024 Apr 26 10:37:20 192.168.122.209 [66791.610892] [tdb] Start Tempesta DB Apr 26 10:37:21 192.168.122.209 [66791.780992] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:37:22 192.168.122.209 [66793.228958] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66793.228958] Maybe that's fine, but it's worth checking the [66793.228958] config - if there is no relations between the [66793.228958] names, then host name confusion attack is possible. Apr 26 10:37:22 192.168.122.209 [66793.347765] [tempesta fw] Configuration processing is completed. Apr 26 10:37:22 192.168.122.209 [66793.399193] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:37:23 192.168.122.209 [66793.825938] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:37:23 192.168.122.209 [66793.864358] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:37:23 192.168.122.209 [66793.893266] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:37:23 192.168.122.209 [66793.947756] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:37:23 192.168.122.209 [66793.949486] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:37:23 192.168.122.209 [66793.999664] [tempesta fw] Tempesta FW is ready Apr 26 10:37:23 192.168.122.209 [66794.628764] [tdb] Close table 'client0.tdb' Apr 26 10:37:24 192.168.122.209 [66794.835210] [tdb] Close table 'sessions0.tdb' Apr 26 10:37:27 192.168.122.209 [66798.096055] [tdb] Close table 'cache0.tdb' Apr 26 10:37:27 192.168.122.209 [66798.358627] [tdb] Close table 'filter0.tdb' Apr 26 10:37:27 192.168.122.209 [66798.359064] [tempesta fw] modules are stopped Apr 26 10:37:27 192.168.122.209 [66798.545447] [tempesta fw] exiting... Apr 26 10:37:28 192.168.122.209 [66798.661108] [tdb] Shutdown Tempesta DB Apr 26 10:37:28 192.168.122.209 [66798.881705] End test: t_modify_http_headers.test_logic.TestRespHeader.test_set_header_name_greater_than_1024 Apr 26 10:37:28 192.168.122.209 [66798.893799] Start test: t_modify_http_headers.test_logic.TestRespHeader.test_set_large_header Apr 26 10:37:29 192.168.122.209 [66800.053406] [tdb] Start Tempesta DB Apr 26 10:37:29 192.168.122.209 [66800.200313] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:37:31 192.168.122.209 [66801.713166] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66801.713166] Maybe that's fine, but it's worth checking the [66801.713166] config - if there is no relations between the [66801.713166] names, then host name confusion attack is possible. Apr 26 10:37:31 192.168.122.209 [66801.823984] [tempesta fw] Configuration processing is completed. Apr 26 10:37:31 192.168.122.209 [66801.889762] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:37:31 192.168.122.209 [66802.312472] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:37:31 192.168.122.209 [66802.338923] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:37:31 192.168.122.209 [66802.366864] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:37:31 192.168.122.209 [66802.411846] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:37:31 192.168.122.209 [66802.413581] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:37:31 192.168.122.209 [66802.451763] [tempesta fw] Tempesta FW is ready Apr 26 10:37:32 192.168.122.209 [66803.031537] [tdb] Close table 'client0.tdb' Apr 26 10:37:32 192.168.122.209 [66803.210250] [tdb] Close table 'sessions0.tdb' Apr 26 10:37:35 192.168.122.209 [66806.472441] [tdb] Close table 'cache0.tdb' Apr 26 10:37:36 192.168.122.209 [66806.710048] [tdb] Close table 'filter0.tdb' Apr 26 10:37:36 192.168.122.209 [66806.710486] [tempesta fw] modules are stopped Apr 26 10:37:36 192.168.122.209 [66806.920366] [tempesta fw] exiting... Apr 26 10:37:36 192.168.122.209 [66807.039379] [tdb] Shutdown Tempesta DB Apr 26 10:37:36 192.168.122.209 [66807.281620] End test: t_modify_http_headers.test_logic.TestRespHeader.test_set_large_header Apr 26 10:37:36 192.168.122.209 [66807.293047] Start test: t_modify_http_headers.test_logic.TestRespHeader.test_set_long_header_name Apr 26 10:37:37 192.168.122.209 [66808.575604] [tdb] Start Tempesta DB Apr 26 10:37:38 192.168.122.209 [66808.730895] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:37:39 192.168.122.209 [66810.321229] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66810.321229] Maybe that's fine, but it's worth checking the [66810.321229] config - if there is no relations between the [66810.321229] names, then host name confusion attack is possible. Apr 26 10:37:39 192.168.122.209 [66810.476075] [tempesta fw] Configuration processing is completed. Apr 26 10:37:39 192.168.122.209 [66810.549665] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:37:40 192.168.122.209 [66811.117089] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:37:40 192.168.122.209 [66811.151608] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:37:40 192.168.122.209 [66811.186176] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:37:40 192.168.122.209 [66811.227846] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:37:40 192.168.122.209 [66811.228918] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:37:40 192.168.122.209 [66811.267825] [tempesta fw] Tempesta FW is ready Apr 26 10:37:41 192.168.122.209 [66811.838853] [tdb] Close table 'client0.tdb' Apr 26 10:37:41 192.168.122.209 [66812.027408] [tdb] Close table 'sessions0.tdb' Apr 26 10:37:44 192.168.122.209 [66815.320713] [tdb] Close table 'cache0.tdb' Apr 26 10:37:44 192.168.122.209 [66815.595497] [tdb] Close table 'filter0.tdb' Apr 26 10:37:44 192.168.122.209 [66815.595980] [tempesta fw] modules are stopped Apr 26 10:37:45 192.168.122.209 [66815.797959] [tempesta fw] exiting... Apr 26 10:37:45 192.168.122.209 [66815.940625] [tdb] Shutdown Tempesta DB Apr 26 10:37:45 192.168.122.209 [66816.155542] End test: t_modify_http_headers.test_logic.TestRespHeader.test_set_long_header_name Apr 26 10:37:45 192.168.122.209 [66816.168723] Start test: t_modify_http_headers.test_logic.TestRespHeader.test_set_non_exist_header Apr 26 10:37:46 192.168.122.209 [66817.468114] [tdb] Start Tempesta DB Apr 26 10:37:46 192.168.122.209 [66817.622691] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:37:48 192.168.122.209 [66819.053571] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66819.053571] Maybe that's fine, but it's worth checking the [66819.053571] config - if there is no relations between the [66819.053571] names, then host name confusion attack is possible. Apr 26 10:37:48 192.168.122.209 [66819.156178] [tempesta fw] Configuration processing is completed. Apr 26 10:37:48 192.168.122.209 [66819.248395] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:37:49 192.168.122.209 [66819.724740] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:37:49 192.168.122.209 [66819.754238] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:37:49 192.168.122.209 [66819.782860] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:37:49 192.168.122.209 [66819.828084] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:37:49 192.168.122.209 [66819.829802] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:37:49 192.168.122.209 [66819.871980] [tempesta fw] Tempesta FW is ready Apr 26 10:37:49 192.168.122.209 [66820.474098] [tdb] Close table 'client0.tdb' Apr 26 10:37:50 192.168.122.209 [66820.675907] [tdb] Close table 'sessions0.tdb' Apr 26 10:37:53 192.168.122.209 [66824.029296] [tdb] Close table 'cache0.tdb' Apr 26 10:37:53 192.168.122.209 [66824.279027] [tdb] Close table 'filter0.tdb' Apr 26 10:37:53 192.168.122.209 [66824.279515] [tempesta fw] modules are stopped Apr 26 10:37:53 192.168.122.209 [66824.459219] [tempesta fw] exiting... Apr 26 10:37:53 192.168.122.209 [66824.631774] [tdb] Shutdown Tempesta DB Apr 26 10:37:54 192.168.122.209 [66824.854916] End test: t_modify_http_headers.test_logic.TestRespHeader.test_set_non_exist_header Apr 26 10:37:54 192.168.122.209 [66824.864662] Start test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_add_header_from_dynamic_table Apr 26 10:37:55 192.168.122.209 [66826.205298] [tdb] Start Tempesta DB Apr 26 10:37:55 192.168.122.209 [66826.368412] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:37:57 192.168.122.209 [66827.841698] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66827.841698] Maybe that's fine, but it's worth checking the [66827.841698] config - if there is no relations between the [66827.841698] names, then host name confusion attack is possible. Apr 26 10:37:57 192.168.122.209 [66827.960292] [tempesta fw] Configuration processing is completed. Apr 26 10:37:57 192.168.122.209 [66828.019324] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:37:57 192.168.122.209 [66828.489022] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:37:57 192.168.122.209 [66828.518319] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:37:57 192.168.122.209 [66828.547437] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:37:57 192.168.122.209 [66828.600160] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:37:57 192.168.122.209 [66828.601939] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:37:57 192.168.122.209 [66828.640100] [tempesta fw] Tempesta FW is ready Apr 26 10:37:58 192.168.122.209 [66829.329656] [tdb] Close table 'client0.tdb' Apr 26 10:37:58 192.168.122.209 [66829.520496] [tdb] Close table 'sessions0.tdb' Apr 26 10:38:02 192.168.122.209 [66832.876422] [tdb] Close table 'cache0.tdb' Apr 26 10:38:02 192.168.122.209 [66833.154751] [tdb] Close table 'filter0.tdb' Apr 26 10:38:02 192.168.122.209 [66833.155202] [tempesta fw] modules are stopped Apr 26 10:38:02 192.168.122.209 [66833.387348] [tempesta fw] exiting... Apr 26 10:38:02 192.168.122.209 [66833.550210] [tdb] Shutdown Tempesta DB Apr 26 10:38:03 192.168.122.209 [66833.806108] End test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_add_header_from_dynamic_table Apr 26 10:38:03 192.168.122.209 [66833.819323] Start test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_add_header_from_static_table Apr 26 10:38:04 192.168.122.209 [66835.134577] [tdb] Start Tempesta DB Apr 26 10:38:04 192.168.122.209 [66835.300149] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:38:06 192.168.122.209 [66836.869831] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66836.869831] Maybe that's fine, but it's worth checking the [66836.869831] config - if there is no relations between the [66836.869831] names, then host name confusion attack is possible. Apr 26 10:38:06 192.168.122.209 [66836.980297] [tempesta fw] Configuration processing is completed. Apr 26 10:38:06 192.168.122.209 [66837.038629] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:38:06 192.168.122.209 [66837.509372] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:38:06 192.168.122.209 [66837.540124] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:38:06 192.168.122.209 [66837.569337] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:38:07 192.168.122.209 [66837.944275] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:38:07 192.168.122.209 [66837.946028] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:38:07 192.168.122.209 [66838.308136] [tempesta fw] Tempesta FW is ready Apr 26 10:38:08 192.168.122.209 [66839.578097] [tdb] Close table 'client0.tdb' Apr 26 10:38:09 192.168.122.209 [66839.843035] [tdb] Close table 'sessions0.tdb' Apr 26 10:38:13 192.168.122.209 [66844.338352] [tdb] Close table 'cache0.tdb' Apr 26 10:38:13 192.168.122.209 [66844.563074] [tdb] Close table 'filter0.tdb' Apr 26 10:38:13 192.168.122.209 [66844.563542] [tempesta fw] modules are stopped Apr 26 10:38:14 192.168.122.209 [66844.763539] [tempesta fw] exiting... Apr 26 10:38:14 192.168.122.209 [66844.890946] [tdb] Shutdown Tempesta DB Apr 26 10:38:14 192.168.122.209 [66845.117000] End test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_add_header_from_static_table Apr 26 10:38:14 192.168.122.209 [66845.134745] Start test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_add_non_exist_header Apr 26 10:38:15 192.168.122.209 [66846.440605] [tdb] Start Tempesta DB Apr 26 10:38:15 192.168.122.209 [66846.585201] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:38:17 192.168.122.209 [66848.081679] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66848.081679] Maybe that's fine, but it's worth checking the [66848.081679] config - if there is no relations between the [66848.081679] names, then host name confusion attack is possible. Apr 26 10:38:17 192.168.122.209 [66848.180409] [tempesta fw] Configuration processing is completed. Apr 26 10:38:17 192.168.122.209 [66848.237481] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:38:18 192.168.122.209 [66848.687163] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:38:18 192.168.122.209 [66848.715169] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:38:18 192.168.122.209 [66848.744062] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:38:18 192.168.122.209 [66848.788394] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:38:18 192.168.122.209 [66848.790166] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:38:18 192.168.122.209 [66848.840350] [tempesta fw] Tempesta FW is ready Apr 26 10:38:18 192.168.122.209 [66849.538449] [tdb] Close table 'client0.tdb' Apr 26 10:38:19 192.168.122.209 [66849.714221] [tdb] Close table 'sessions0.tdb' Apr 26 10:38:22 192.168.122.209 [66853.016349] [tdb] Close table 'cache0.tdb' Apr 26 10:38:22 192.168.122.209 [66853.254081] [tdb] Close table 'filter0.tdb' Apr 26 10:38:22 192.168.122.209 [66853.254505] [tempesta fw] modules are stopped Apr 26 10:38:22 192.168.122.209 [66853.442345] [tempesta fw] exiting... Apr 26 10:38:22 192.168.122.209 [66853.532554] [tdb] Shutdown Tempesta DB Apr 26 10:38:23 192.168.122.209 [66853.720881] End test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_add_non_exist_header Apr 26 10:38:23 192.168.122.209 [66853.731392] Start test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_delete_headers Apr 26 10:38:24 192.168.122.209 [66855.010751] [tdb] Start Tempesta DB Apr 26 10:38:24 192.168.122.209 [66855.146560] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:38:25 192.168.122.209 [66856.601866] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66856.601866] Maybe that's fine, but it's worth checking the [66856.601866] config - if there is no relations between the [66856.601866] names, then host name confusion attack is possible. Apr 26 10:38:26 192.168.122.209 [66856.720513] [tempesta fw] Configuration processing is completed. Apr 26 10:38:26 192.168.122.209 [66856.805064] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:38:26 192.168.122.209 [66857.543396] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:38:26 192.168.122.209 [66857.598605] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:38:27 192.168.122.209 [66857.653891] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:38:27 192.168.122.209 [66857.700473] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:38:27 192.168.122.209 [66857.701903] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:38:27 192.168.122.209 [66857.744451] [tempesta fw] Tempesta FW is ready Apr 26 10:38:27 192.168.122.209 [66858.438274] [tdb] Close table 'client0.tdb' Apr 26 10:38:27 192.168.122.209 [66858.636746] [tdb] Close table 'sessions0.tdb' Apr 26 10:38:31 192.168.122.209 [66862.049633] [tdb] Close table 'cache0.tdb' Apr 26 10:38:31 192.168.122.209 [66862.323245] [tdb] Close table 'filter0.tdb' Apr 26 10:38:31 192.168.122.209 [66862.323726] [tempesta fw] modules are stopped Apr 26 10:38:31 192.168.122.209 [66862.512557] [tempesta fw] exiting... Apr 26 10:38:32 192.168.122.209 [66862.669760] [tdb] Shutdown Tempesta DB Apr 26 10:38:32 192.168.122.209 [66862.911784] End test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_delete_headers Apr 26 10:38:32 192.168.122.209 [66862.947266] Start test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_delete_many_headers Apr 26 10:38:33 192.168.122.209 [66864.052308] [tdb] Start Tempesta DB Apr 26 10:38:33 192.168.122.209 [66864.219860] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:38:34 192.168.122.209 [66865.605961] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66865.605961] Maybe that's fine, but it's worth checking the [66865.605961] config - if there is no relations between the [66865.605961] names, then host name confusion attack is possible. Apr 26 10:38:35 192.168.122.209 [66865.704660] [tempesta fw] Configuration processing is completed. Apr 26 10:38:35 192.168.122.209 [66865.768518] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:38:35 192.168.122.209 [66866.309739] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:38:35 192.168.122.209 [66866.346609] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:38:35 192.168.122.209 [66866.384662] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:38:35 192.168.122.209 [66866.424621] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:38:35 192.168.122.209 [66866.426394] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:38:35 192.168.122.209 [66866.472568] [tempesta fw] Tempesta FW is ready Apr 26 10:38:36 192.168.122.209 [66867.148250] [tdb] Close table 'client0.tdb' Apr 26 10:38:36 192.168.122.209 [66867.337473] [tdb] Close table 'sessions0.tdb' Apr 26 10:38:39 192.168.122.209 [66870.531806] [tdb] Close table 'cache0.tdb' Apr 26 10:38:40 192.168.122.209 [66870.770993] [tdb] Close table 'filter0.tdb' Apr 26 10:38:40 192.168.122.209 [66870.771409] [tempesta fw] modules are stopped Apr 26 10:38:40 192.168.122.209 [66870.938332] [tempesta fw] exiting... Apr 26 10:38:40 192.168.122.209 [66871.081021] [tdb] Shutdown Tempesta DB Apr 26 10:38:40 192.168.122.209 [66871.315307] End test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_delete_many_headers Apr 26 10:38:40 192.168.122.209 [66871.331510] Start test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_delete_many_special_headers Apr 26 10:38:41 192.168.122.209 [66872.362202] [tdb] Start Tempesta DB Apr 26 10:38:41 192.168.122.209 [66872.501201] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:38:43 192.168.122.209 [66873.873970] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66873.873970] Maybe that's fine, but it's worth checking the [66873.873970] config - if there is no relations between the [66873.873970] names, then host name confusion attack is possible. Apr 26 10:38:43 192.168.122.209 [66873.980719] [tempesta fw] Configuration processing is completed. Apr 26 10:38:43 192.168.122.209 [66874.038703] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:38:43 192.168.122.209 [66874.481033] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:38:43 192.168.122.209 [66874.521753] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:38:43 192.168.122.209 [66874.553171] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:38:43 192.168.122.209 [66874.604737] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:38:43 192.168.122.209 [66874.606493] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:38:44 192.168.122.209 [66874.652667] [tempesta fw] Tempesta FW is ready Apr 26 10:38:44 192.168.122.209 [66875.260669] [tdb] Close table 'client0.tdb' Apr 26 10:38:44 192.168.122.209 [66875.480927] [tdb] Close table 'sessions0.tdb' Apr 26 10:38:48 192.168.122.209 [66878.710684] [tdb] Close table 'cache0.tdb' Apr 26 10:38:48 192.168.122.209 [66878.957395] [tdb] Close table 'filter0.tdb' Apr 26 10:38:48 192.168.122.209 [66878.957837] [tempesta fw] modules are stopped Apr 26 10:38:48 192.168.122.209 [66879.140767] [tempesta fw] exiting... Apr 26 10:38:48 192.168.122.209 [66879.263095] [tdb] Shutdown Tempesta DB Apr 26 10:38:48 192.168.122.209 [66879.473909] End test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_delete_many_special_headers Apr 26 10:38:48 192.168.122.209 [66879.482468] Start test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_delete_non_exist_header Apr 26 10:38:49 192.168.122.209 [66880.549258] [tdb] Start Tempesta DB Apr 26 10:38:50 192.168.122.209 [66880.681051] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:38:51 192.168.122.209 [66882.046083] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66882.046083] Maybe that's fine, but it's worth checking the [66882.046083] config - if there is no relations between the [66882.046083] names, then host name confusion attack is possible. Apr 26 10:38:51 192.168.122.209 [66882.152838] [tempesta fw] Configuration processing is completed. Apr 26 10:38:51 192.168.122.209 [66882.214321] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:38:52 192.168.122.209 [66882.674708] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:38:52 192.168.122.209 [66882.703687] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:38:52 192.168.122.209 [66882.733250] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:38:52 192.168.122.209 [66882.780798] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:38:52 192.168.122.209 [66882.782541] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:38:52 192.168.122.209 [66882.824749] [tempesta fw] Tempesta FW is ready Apr 26 10:38:52 192.168.122.209 [66883.456237] [tdb] Close table 'client0.tdb' Apr 26 10:38:52 192.168.122.209 [66883.645930] [tdb] Close table 'sessions0.tdb' Apr 26 10:38:56 192.168.122.209 [66886.946679] [tdb] Close table 'cache0.tdb' Apr 26 10:38:56 192.168.122.209 [66887.204039] [tdb] Close table 'filter0.tdb' Apr 26 10:38:56 192.168.122.209 [66887.204493] [tempesta fw] modules are stopped Apr 26 10:38:56 192.168.122.209 [66887.417759] [tempesta fw] exiting... Apr 26 10:38:56 192.168.122.209 [66887.574238] [tdb] Shutdown Tempesta DB Apr 26 10:38:57 192.168.122.209 [66887.827312] End test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_delete_non_exist_header Apr 26 10:38:57 192.168.122.209 [66887.843049] Start test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_delete_special_headers Apr 26 10:38:58 192.168.122.209 [66889.205626] [tdb] Start Tempesta DB Apr 26 10:38:58 192.168.122.209 [66889.388136] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:39:00 192.168.122.209 [66890.954306] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66890.954306] Maybe that's fine, but it's worth checking the [66890.954306] config - if there is no relations between the [66890.954306] names, then host name confusion attack is possible. Apr 26 10:39:00 192.168.122.209 [66891.060995] [tempesta fw] Configuration processing is completed. Apr 26 10:39:00 192.168.122.209 [66891.132844] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:39:01 192.168.122.209 [66891.715299] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:39:01 192.168.122.209 [66891.759698] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:39:01 192.168.122.209 [66891.793888] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:39:01 192.168.122.209 [66891.840919] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:39:01 192.168.122.209 [66891.842689] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:39:01 192.168.122.209 [66891.888885] [tempesta fw] Tempesta FW is ready Apr 26 10:39:01 192.168.122.209 [66892.574902] [tdb] Close table 'client0.tdb' Apr 26 10:39:02 192.168.122.209 [66892.756936] [tdb] Close table 'sessions0.tdb' Apr 26 10:39:05 192.168.122.209 [66896.100598] [tdb] Close table 'cache0.tdb' Apr 26 10:39:05 192.168.122.209 [66896.356113] [tdb] Close table 'filter0.tdb' Apr 26 10:39:05 192.168.122.209 [66896.356566] [tempesta fw] modules are stopped Apr 26 10:39:05 192.168.122.209 [66896.540435] [tempesta fw] exiting... Apr 26 10:39:06 192.168.122.209 [66896.670281] [tdb] Shutdown Tempesta DB Apr 26 10:39:06 192.168.122.209 [66896.919404] End test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_delete_special_headers Apr 26 10:39:06 192.168.122.209 [66896.938249] Start test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_long_header_name Apr 26 10:39:07 192.168.122.209 [66898.295574] [tdb] Start Tempesta DB Apr 26 10:39:07 192.168.122.209 [66898.461743] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:39:09 192.168.122.209 [66899.966352] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66899.966352] Maybe that's fine, but it's worth checking the [66899.966352] config - if there is no relations between the [66899.966352] names, then host name confusion attack is possible. Apr 26 10:39:09 192.168.122.209 [66900.065208] [tempesta fw] Configuration processing is completed. Apr 26 10:39:09 192.168.122.209 [66900.132196] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:39:09 192.168.122.209 [66900.615123] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:39:10 192.168.122.209 [66900.648010] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:39:10 192.168.122.209 [66900.680220] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:39:10 192.168.122.209 [66900.737092] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:39:10 192.168.122.209 [66900.738799] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:39:10 192.168.122.209 [66900.788981] [tempesta fw] Tempesta FW is ready Apr 26 10:39:11 192.168.122.209 [66902.054364] [tdb] Close table 'client0.tdb' Apr 26 10:39:11 192.168.122.209 [66902.265718] [tdb] Close table 'sessions0.tdb' Apr 26 10:39:15 192.168.122.209 [66905.713786] [tdb] Close table 'cache0.tdb' Apr 26 10:39:15 192.168.122.209 [66905.991398] [tdb] Close table 'filter0.tdb' Apr 26 10:39:15 192.168.122.209 [66905.991853] [tempesta fw] modules are stopped Apr 26 10:39:15 192.168.122.209 [66906.209427] [tempesta fw] exiting... Apr 26 10:39:15 192.168.122.209 [66906.347475] [tdb] Shutdown Tempesta DB Apr 26 10:39:15 192.168.122.209 [66906.612012] End test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_long_header_name Apr 26 10:39:16 192.168.122.209 [66906.651095] Start test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_set_exist_header Apr 26 10:39:17 192.168.122.209 [66907.964511] [tdb] Start Tempesta DB Apr 26 10:39:17 192.168.122.209 [66908.107963] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:39:18 192.168.122.209 [66909.594509] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66909.594509] Maybe that's fine, but it's worth checking the [66909.594509] config - if there is no relations between the [66909.594509] names, then host name confusion attack is possible. Apr 26 10:39:19 192.168.122.209 [66909.693230] [tempesta fw] Configuration processing is completed. Apr 26 10:39:19 192.168.122.209 [66909.755455] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:39:19 192.168.122.209 [66910.244587] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:39:19 192.168.122.209 [66910.283640] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:39:19 192.168.122.209 [66910.314209] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:39:19 192.168.122.209 [66910.377153] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:39:19 192.168.122.209 [66910.379014] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:39:19 192.168.122.209 [66910.417104] [tempesta fw] Tempesta FW is ready Apr 26 10:39:20 192.168.122.209 [66911.079773] [tdb] Close table 'client0.tdb' Apr 26 10:39:20 192.168.122.209 [66911.276671] [tdb] Close table 'sessions0.tdb' Apr 26 10:39:23 192.168.122.209 [66914.546799] [tdb] Close table 'cache0.tdb' Apr 26 10:39:24 192.168.122.209 [66914.785855] [tdb] Close table 'filter0.tdb' Apr 26 10:39:24 192.168.122.209 [66914.786265] [tempesta fw] modules are stopped Apr 26 10:39:24 192.168.122.209 [66915.001686] [tempesta fw] exiting... Apr 26 10:39:24 192.168.122.209 [66915.140224] [tdb] Shutdown Tempesta DB Apr 26 10:39:24 192.168.122.209 [66915.370054] End test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_set_exist_header Apr 26 10:39:24 192.168.122.209 [66915.391515] Start test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_set_exist_special_header Apr 26 10:39:26 192.168.122.209 [66916.723022] [tdb] Start Tempesta DB Apr 26 10:39:26 192.168.122.209 [66916.889797] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:39:27 192.168.122.209 [66918.422644] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66918.422644] Maybe that's fine, but it's worth checking the [66918.422644] config - if there is no relations between the [66918.422644] names, then host name confusion attack is possible. Apr 26 10:39:27 192.168.122.209 [66918.541305] [tempesta fw] Configuration processing is completed. Apr 26 10:39:27 192.168.122.209 [66918.609848] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:39:28 192.168.122.209 [66919.162416] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:39:28 192.168.122.209 [66919.218930] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:39:28 192.168.122.209 [66919.270574] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:39:28 192.168.122.209 [66919.317283] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:39:28 192.168.122.209 [66919.319026] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:39:28 192.168.122.209 [66919.369203] [tempesta fw] Tempesta FW is ready Apr 26 10:39:29 192.168.122.209 [66920.022589] [tdb] Close table 'client0.tdb' Apr 26 10:39:29 192.168.122.209 [66920.208159] [tdb] Close table 'sessions0.tdb' Apr 26 10:39:33 192.168.122.209 [66923.671227] [tdb] Close table 'cache0.tdb' Apr 26 10:39:33 192.168.122.209 [66923.984798] [tdb] Close table 'filter0.tdb' Apr 26 10:39:33 192.168.122.209 [66923.985270] [tempesta fw] modules are stopped Apr 26 10:39:33 192.168.122.209 [66924.155660] [tempesta fw] exiting... Apr 26 10:39:33 192.168.122.209 [66924.295276] [tdb] Shutdown Tempesta DB Apr 26 10:39:33 192.168.122.209 [66924.532293] End test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_set_exist_special_header Apr 26 10:39:33 192.168.122.209 [66924.552694] Start test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_set_header_name_greater_than_1024 Apr 26 10:39:35 192.168.122.209 [66925.729526] [tdb] Start Tempesta DB Apr 26 10:39:35 192.168.122.209 [66925.897704] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:39:36 192.168.122.209 [66927.438918] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66927.438918] Maybe that's fine, but it's worth checking the [66927.438918] config - if there is no relations between the [66927.438918] names, then host name confusion attack is possible. Apr 26 10:39:36 192.168.122.209 [66927.541460] [tempesta fw] Configuration processing is completed. Apr 26 10:39:36 192.168.122.209 [66927.606084] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:39:37 192.168.122.209 [66928.076809] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:39:37 192.168.122.209 [66928.104930] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:39:37 192.168.122.209 [66928.131730] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:39:37 192.168.122.209 [66928.217370] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:39:37 192.168.122.209 [66928.219212] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:39:37 192.168.122.209 [66928.257308] [tempesta fw] Tempesta FW is ready Apr 26 10:39:38 192.168.122.209 [66928.932847] [tdb] Close table 'client0.tdb' Apr 26 10:39:38 192.168.122.209 [66929.117257] [tdb] Close table 'sessions0.tdb' Apr 26 10:39:41 192.168.122.209 [66932.205778] [tdb] Close table 'cache0.tdb' Apr 26 10:39:41 192.168.122.209 [66932.457022] [tdb] Close table 'filter0.tdb' Apr 26 10:39:41 192.168.122.209 [66932.457470] [tempesta fw] modules are stopped Apr 26 10:39:42 192.168.122.209 [66932.670774] [tempesta fw] exiting... Apr 26 10:39:42 192.168.122.209 [66932.800958] [tdb] Shutdown Tempesta DB Apr 26 10:39:42 192.168.122.209 [66933.044717] End test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_set_header_name_greater_than_1024 Apr 26 10:39:42 192.168.122.209 [66933.062699] Start test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_set_large_header Apr 26 10:39:43 192.168.122.209 [66934.328152] [tdb] Start Tempesta DB Apr 26 10:39:43 192.168.122.209 [66934.470861] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:39:45 192.168.122.209 [66935.998766] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66935.998766] Maybe that's fine, but it's worth checking the [66935.998766] config - if there is no relations between the [66935.998766] names, then host name confusion attack is possible. Apr 26 10:39:45 192.168.122.209 [66936.097581] [tempesta fw] Configuration processing is completed. Apr 26 10:39:45 192.168.122.209 [66936.159808] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:39:45 192.168.122.209 [66936.594416] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:39:45 192.168.122.209 [66936.619843] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:39:45 192.168.122.209 [66936.646476] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:39:46 192.168.122.209 [66936.705473] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:39:46 192.168.122.209 [66936.707199] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:39:46 192.168.122.209 [66936.753430] [tempesta fw] Tempesta FW is ready Apr 26 10:39:46 192.168.122.209 [66937.405257] [tdb] Close table 'client0.tdb' Apr 26 10:39:46 192.168.122.209 [66937.627343] [tdb] Close table 'sessions0.tdb' Apr 26 10:39:50 192.168.122.209 [66940.811505] [tdb] Close table 'cache0.tdb' Apr 26 10:39:50 192.168.122.209 [66941.039612] [tdb] Close table 'filter0.tdb' Apr 26 10:39:50 192.168.122.209 [66941.040042] [tempesta fw] modules are stopped Apr 26 10:39:50 192.168.122.209 [66941.227837] [tempesta fw] exiting... Apr 26 10:39:50 192.168.122.209 [66941.342181] [tdb] Shutdown Tempesta DB Apr 26 10:39:50 192.168.122.209 [66941.588700] End test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_set_large_header Apr 26 10:39:50 192.168.122.209 [66941.601615] Start test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_set_long_header_name Apr 26 10:39:52 192.168.122.209 [66942.842897] [tdb] Start Tempesta DB Apr 26 10:39:52 192.168.122.209 [66942.998794] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:39:53 192.168.122.209 [66944.622852] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66944.622852] Maybe that's fine, but it's worth checking the [66944.622852] config - if there is no relations between the [66944.622852] names, then host name confusion attack is possible. Apr 26 10:39:54 192.168.122.209 [66944.785634] [tempesta fw] Configuration processing is completed. Apr 26 10:39:54 192.168.122.209 [66944.847697] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:39:54 192.168.122.209 [66945.397163] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:39:54 192.168.122.209 [66945.431849] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:39:54 192.168.122.209 [66945.465661] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:39:54 192.168.122.209 [66945.509563] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:39:54 192.168.122.209 [66945.510955] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:39:54 192.168.122.209 [66945.553545] [tempesta fw] Tempesta FW is ready Apr 26 10:39:55 192.168.122.209 [66946.185609] [tdb] Close table 'client0.tdb' Apr 26 10:39:55 192.168.122.209 [66946.356232] [tdb] Close table 'sessions0.tdb' Apr 26 10:39:59 192.168.122.209 [66949.686509] [tdb] Close table 'cache0.tdb' Apr 26 10:39:59 192.168.122.209 [66949.937241] [tdb] Close table 'filter0.tdb' Apr 26 10:39:59 192.168.122.209 [66949.937709] [tempesta fw] modules are stopped Apr 26 10:39:59 192.168.122.209 [66950.110608] [tempesta fw] exiting... Apr 26 10:39:59 192.168.122.209 [66950.258420] [tdb] Shutdown Tempesta DB Apr 26 10:39:59 192.168.122.209 [66950.457858] End test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_set_long_header_name Apr 26 10:39:59 192.168.122.209 [66950.470288] Start test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_set_non_exist_header Apr 26 10:40:01 192.168.122.209 [66951.824824] [tdb] Start Tempesta DB Apr 26 10:40:01 192.168.122.209 [66951.987782] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:40:02 192.168.122.209 [66953.475068] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [66953.475068] Maybe that's fine, but it's worth checking the [66953.475068] config - if there is no relations between the [66953.475068] names, then host name confusion attack is possible. Apr 26 10:40:02 192.168.122.209 [66953.593683] [tempesta fw] Configuration processing is completed. Apr 26 10:40:03 192.168.122.209 [66953.661832] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:40:03 192.168.122.209 [66954.212100] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:40:03 192.168.122.209 [66954.248690] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:40:03 192.168.122.209 [66954.276993] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:40:03 192.168.122.209 [66954.442970] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:40:03 192.168.122.209 [66954.444714] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:40:03 192.168.122.209 [66954.517717] [tempesta fw] Tempesta FW is ready Apr 26 10:40:04 192.168.122.209 [66955.144115] [tdb] Close table 'client0.tdb' Apr 26 10:40:04 192.168.122.209 [66955.328791] [tdb] Close table 'sessions0.tdb' Apr 26 10:40:08 192.168.122.209 [66958.666859] [tdb] Close table 'cache0.tdb' Apr 26 10:40:08 192.168.122.209 [66958.915291] [tdb] Close table 'filter0.tdb' Apr 26 10:40:08 192.168.122.209 [66958.915734] [tempesta fw] modules are stopped Apr 26 10:40:08 192.168.122.209 [66959.098291] [tempesta fw] exiting... Apr 26 10:40:08 192.168.122.209 [66959.223128] [tdb] Shutdown Tempesta DB Apr 26 10:40:08 192.168.122.209 [66959.479720] End test: t_modify_http_headers.test_logic.TestRespHeaderH2.test_set_non_exist_header Apr 26 10:40:08 192.168.122.209 [66959.488747] Start test: t_reconf.test_reconf_base.TestHttpTablesReconf.test_add_rule Apr 26 10:40:10 192.168.122.209 [66960.884460] [tdb] Start Tempesta DB Apr 26 10:40:10 192.168.122.209 [66961.041182] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:40:12 192.168.122.209 [66962.833909] [tempesta fw] Configuration processing is completed. Apr 26 10:40:12 192.168.122.209 [66962.906286] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:40:12 192.168.122.209 [66963.448618] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:40:12 192.168.122.209 [66963.484570] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:40:12 192.168.122.209 [66963.519310] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:40:12 192.168.122.209 [66963.593837] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:40:12 192.168.122.209 [66963.637718] [tempesta fw] Tempesta FW is ready Apr 26 10:40:13 192.168.122.209 [66964.490260] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:40:14 192.168.122.209 [66964.693755] [tempesta fw] Configuration processing is completed. Apr 26 10:40:14 192.168.122.209 [66965.062017] [tempesta fw] Tempesta FW is ready Apr 26 10:40:14 192.168.122.209 [66965.127625] [tempesta fw] Warning: request has been filtered out via http table: 127.0.0.2 Apr 26 10:40:14 192.168.122.209 [66965.630678] [tdb] Close table 'client0.tdb' Apr 26 10:40:15 192.168.122.209 [66965.813474] [tdb] Close table 'sessions0.tdb' Apr 26 10:40:18 192.168.122.209 [66969.052845] [tdb] Close table 'cache0.tdb' Apr 26 10:40:18 192.168.122.209 [66969.278746] [tdb] Close table 'filter0.tdb' Apr 26 10:40:18 192.168.122.209 [66969.279194] [tempesta fw] modules are stopped Apr 26 10:40:18 192.168.122.209 [66969.578845] [tempesta fw] exiting... Apr 26 10:40:19 192.168.122.209 [66969.702962] [tdb] Shutdown Tempesta DB Apr 26 10:40:19 192.168.122.209 [66969.941912] End test: t_reconf.test_reconf_base.TestHttpTablesReconf.test_add_rule Apr 26 10:40:19 192.168.122.209 [66969.952716] Start test: t_reconf.test_reconf_base.TestHttpTablesReconf.test_reconf_action Apr 26 10:40:20 192.168.122.209 [66971.104563] [tdb] Start Tempesta DB Apr 26 10:40:20 192.168.122.209 [66971.247442] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:40:22 192.168.122.209 [66973.022007] [tempesta fw] Configuration processing is completed. Apr 26 10:40:22 192.168.122.209 [66973.080605] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:40:22 192.168.122.209 [66973.517033] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:40:22 192.168.122.209 [66973.543108] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:40:22 192.168.122.209 [66973.569378] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:40:22 192.168.122.209 [66973.633943] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:40:23 192.168.122.209 [66973.673885] [tempesta fw] Tempesta FW is ready Apr 26 10:40:23 192.168.122.209 [66974.434870] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:40:23 192.168.122.209 [66974.637906] [tempesta fw] Configuration processing is completed. Apr 26 10:40:24 192.168.122.209 [66975.014181] [tempesta fw] Tempesta FW is ready Apr 26 10:40:24 192.168.122.209 [66975.090289] [tempesta fw] Warning: request has been filtered out via http table: 127.0.0.2 Apr 26 10:40:24 192.168.122.209 [66975.599210] [tdb] Close table 'client0.tdb' Apr 26 10:40:25 192.168.122.209 [66975.790466] [tdb] Close table 'sessions0.tdb' Apr 26 10:40:28 192.168.122.209 [66979.044573] [tdb] Close table 'cache0.tdb' Apr 26 10:40:28 192.168.122.209 [66979.319275] [tdb] Close table 'filter0.tdb' Apr 26 10:40:28 192.168.122.209 [66979.319718] [tempesta fw] modules are stopped Apr 26 10:40:28 192.168.122.209 [66979.534996] [tempesta fw] exiting... Apr 26 10:40:29 192.168.122.209 [66979.683649] [tdb] Shutdown Tempesta DB Apr 26 10:40:29 192.168.122.209 [66979.908588] End test: t_reconf.test_reconf_base.TestHttpTablesReconf.test_reconf_action Apr 26 10:40:29 192.168.122.209 [66979.924259] Start test: t_reconf.test_reconf_base.TestHttpTablesReconf.test_reconf_condition Apr 26 10:40:30 192.168.122.209 [66981.258584] [tdb] Start Tempesta DB Apr 26 10:40:30 192.168.122.209 [66981.416643] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:40:32 192.168.122.209 [66983.270146] [tempesta fw] Configuration processing is completed. Apr 26 10:40:32 192.168.122.209 [66983.335481] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:40:33 192.168.122.209 [66983.771588] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:40:33 192.168.122.209 [66983.798855] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:40:33 192.168.122.209 [66983.826165] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:40:33 192.168.122.209 [66983.885983] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:40:33 192.168.122.209 [66983.926031] [tempesta fw] Tempesta FW is ready Apr 26 10:40:34 192.168.122.209 [66984.787124] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:40:34 192.168.122.209 [66984.978196] [tempesta fw] Configuration processing is completed. Apr 26 10:40:34 192.168.122.209 [66985.318267] [tempesta fw] Tempesta FW is ready Apr 26 10:40:35 192.168.122.209 [66985.900039] [tdb] Close table 'client0.tdb' Apr 26 10:40:35 192.168.122.209 [66986.092343] [tdb] Close table 'sessions0.tdb' Apr 26 10:40:38 192.168.122.209 [66989.510953] [tdb] Close table 'cache0.tdb' Apr 26 10:40:39 192.168.122.209 [66989.784399] [tdb] Close table 'filter0.tdb' Apr 26 10:40:39 192.168.122.209 [66989.784842] [tempesta fw] modules are stopped Apr 26 10:40:39 192.168.122.209 [66990.008504] [tempesta fw] exiting... Apr 26 10:40:39 192.168.122.209 [66990.143241] [tdb] Shutdown Tempesta DB Apr 26 10:40:39 192.168.122.209 [66990.350506] End test: t_reconf.test_reconf_base.TestHttpTablesReconf.test_reconf_condition Apr 26 10:40:39 192.168.122.209 [66990.373845] Start test: t_reconf.test_reconf_base.TestHttpTablesReconf.test_reconf_field_arg Apr 26 10:40:41 192.168.122.209 [66991.724606] [tdb] Start Tempesta DB Apr 26 10:40:41 192.168.122.209 [66991.889470] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:40:43 192.168.122.209 [66993.746354] [tempesta fw] Configuration processing is completed. Apr 26 10:40:43 192.168.122.209 [66993.815890] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:40:43 192.168.122.209 [66994.274744] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:40:43 192.168.122.209 [66994.302888] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:40:43 192.168.122.209 [66994.329743] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:40:43 192.168.122.209 [66994.390074] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:40:43 192.168.122.209 [66994.430029] [tempesta fw] Tempesta FW is ready Apr 26 10:40:44 192.168.122.209 [66995.265157] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:40:44 192.168.122.209 [66995.510206] [tempesta fw] Configuration processing is completed. Apr 26 10:40:45 192.168.122.209 [66995.894392] [tempesta fw] Tempesta FW is ready Apr 26 10:40:45 192.168.122.209 [66996.547889] [tdb] Close table 'client0.tdb' Apr 26 10:40:46 192.168.122.209 [66996.731076] [tdb] Close table 'sessions0.tdb' Apr 26 10:40:49 192.168.122.209 [66999.982866] [tdb] Close table 'cache0.tdb' Apr 26 10:40:49 192.168.122.209 [67000.238163] [tdb] Close table 'filter0.tdb' Apr 26 10:40:49 192.168.122.209 [67000.238615] [tempesta fw] modules are stopped Apr 26 10:40:49 192.168.122.209 [67000.510920] [tempesta fw] exiting... Apr 26 10:40:49 192.168.122.209 [67000.628801] [tdb] Shutdown Tempesta DB Apr 26 10:40:50 192.168.122.209 [67000.849587] End test: t_reconf.test_reconf_base.TestHttpTablesReconf.test_reconf_field_arg Apr 26 10:40:50 192.168.122.209 [67000.864151] Start test: t_reconf.test_reconf_base.TestHttpTablesReconf.test_reconf_field_name Apr 26 10:40:51 192.168.122.209 [67002.308632] [tdb] Start Tempesta DB Apr 26 10:40:51 192.168.122.209 [67002.466306] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:40:53 192.168.122.209 [67004.354401] [tempesta fw] Configuration processing is completed. Apr 26 10:40:53 192.168.122.209 [67004.419665] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:40:54 192.168.122.209 [67004.915034] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:40:54 192.168.122.209 [67004.956549] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:40:54 192.168.122.209 [67004.990885] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:40:54 192.168.122.209 [67005.058338] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:40:54 192.168.122.209 [67005.094295] [tempesta fw] Tempesta FW is ready Apr 26 10:40:55 192.168.122.209 [67005.828940] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:40:55 192.168.122.209 [67006.050284] [tempesta fw] Configuration processing is completed. Apr 26 10:40:55 192.168.122.209 [67006.410523] [tempesta fw] Tempesta FW is ready Apr 26 10:40:56 192.168.122.209 [67007.000888] [tdb] Close table 'client0.tdb' Apr 26 10:40:56 192.168.122.209 [67007.185554] [tdb] Close table 'sessions0.tdb' Apr 26 10:40:59 192.168.122.209 [67010.345801] [tdb] Close table 'cache0.tdb' Apr 26 10:40:59 192.168.122.209 [67010.630591] [tdb] Close table 'filter0.tdb' Apr 26 10:40:59 192.168.122.209 [67010.631019] [tempesta fw] modules are stopped Apr 26 10:41:00 192.168.122.209 [67010.850871] [tempesta fw] exiting... Apr 26 10:41:00 192.168.122.209 [67010.961582] [tdb] Shutdown Tempesta DB Apr 26 10:41:00 192.168.122.209 [67011.168684] End test: t_reconf.test_reconf_base.TestHttpTablesReconf.test_reconf_field_name Apr 26 10:41:00 192.168.122.209 [67011.179989] Start test: t_reconf.test_reconf_base.TestHttpTablesReconf.test_reconf_val Apr 26 10:41:01 192.168.122.209 [67012.302847] [tdb] Start Tempesta DB Apr 26 10:41:01 192.168.122.209 [67012.454919] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:41:03 192.168.122.209 [67014.286455] [tempesta fw] Configuration processing is completed. Apr 26 10:41:03 192.168.122.209 [67014.346722] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:41:04 192.168.122.209 [67014.880359] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:41:04 192.168.122.209 [67014.924080] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:41:04 192.168.122.209 [67014.959894] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:41:04 192.168.122.209 [67015.026383] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:41:04 192.168.122.209 [67015.070394] [tempesta fw] Tempesta FW is ready Apr 26 10:41:05 192.168.122.209 [67015.847193] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:41:05 192.168.122.209 [67016.062395] [tempesta fw] Configuration processing is completed. Apr 26 10:41:05 192.168.122.209 [67016.426595] [tempesta fw] Tempesta FW is ready Apr 26 10:41:06 192.168.122.209 [67016.979322] [tdb] Close table 'client0.tdb' Apr 26 10:41:06 192.168.122.209 [67017.176412] [tdb] Close table 'sessions0.tdb' Apr 26 10:41:09 192.168.122.209 [67020.457065] [tdb] Close table 'cache0.tdb' Apr 26 10:41:10 192.168.122.209 [67020.706241] [tdb] Close table 'filter0.tdb' Apr 26 10:41:10 192.168.122.209 [67020.706716] [tempesta fw] modules are stopped Apr 26 10:41:10 192.168.122.209 [67020.951263] [tempesta fw] exiting... Apr 26 10:41:10 192.168.122.209 [67021.104310] [tdb] Shutdown Tempesta DB Apr 26 10:41:10 192.168.122.209 [67021.320846] End test: t_reconf.test_reconf_base.TestHttpTablesReconf.test_reconf_val Apr 26 10:41:10 192.168.122.209 [67021.331129] Start test: t_reconf.test_reconf_base.TestHttpTablesReconf.test_remove_rule Apr 26 10:41:11 192.168.122.209 [67022.568577] [tdb] Start Tempesta DB Apr 26 10:41:12 192.168.122.209 [67022.714575] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:41:13 192.168.122.209 [67024.602665] [tempesta fw] Configuration processing is completed. Apr 26 10:41:14 192.168.122.209 [67024.660194] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:41:14 192.168.122.209 [67025.097491] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:41:14 192.168.122.209 [67025.124250] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:41:14 192.168.122.209 [67025.151554] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:41:14 192.168.122.209 [67025.242568] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:41:14 192.168.122.209 [67025.286511] [tempesta fw] Tempesta FW is ready Apr 26 10:41:15 192.168.122.209 [67025.929192] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:41:15 192.168.122.209 [67026.142516] [tempesta fw] Configuration processing is completed. Apr 26 10:41:15 192.168.122.209 [67026.534714] [tempesta fw] Tempesta FW is ready Apr 26 10:41:16 192.168.122.209 [67027.140854] [tdb] Close table 'client0.tdb' Apr 26 10:41:16 192.168.122.209 [67027.329630] [tdb] Close table 'sessions0.tdb' Apr 26 10:41:19 192.168.122.209 [67030.582678] [tdb] Close table 'cache0.tdb' Apr 26 10:41:20 192.168.122.209 [67030.854253] [tdb] Close table 'filter0.tdb' Apr 26 10:41:20 192.168.122.209 [67030.854846] [tempesta fw] modules are stopped Apr 26 10:41:20 192.168.122.209 [67031.096393] [tempesta fw] exiting... Apr 26 10:41:20 192.168.122.209 [67031.210155] [tdb] Shutdown Tempesta DB Apr 26 10:41:20 192.168.122.209 [67031.429639] End test: t_reconf.test_reconf_base.TestHttpTablesReconf.test_remove_rule Apr 26 10:41:20 192.168.122.209 [67031.440838] Start test: t_reconf.test_reconf_base.TestListenCommonReconf.test_reconf_busy_socks Apr 26 10:41:22 192.168.122.209 [67032.733732] [tdb] Start Tempesta DB Apr 26 10:41:22 192.168.122.209 [67032.891390] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:41:23 192.168.122.209 [67034.086917] [tempesta fw] Configuration processing is completed. Apr 26 10:41:23 192.168.122.209 [67034.150287] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:41:24 192.168.122.209 [67034.690706] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:41:24 192.168.122.209 [67034.724995] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:41:24 192.168.122.209 [67034.759328] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:41:24 192.168.122.209 [67034.760474] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:41:24 192.168.122.209 [67034.774586] [tempesta fw] Tempesta FW is ready Apr 26 10:41:24 192.168.122.209 [67035.285196] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:41:24 192.168.122.209 [67035.359707] [tempesta fw] Configuration processing is completed. Apr 26 10:41:24 192.168.122.209 [67035.379075] [tempesta fw] Open listen socket on: 0.0.0.0:4433 Apr 26 10:41:24 192.168.122.209 [67035.380876] [tempesta fw] Open listen socket on: 0.0.0.0:8000 Apr 26 10:41:24 192.168.122.209 [67035.383383] [tempesta fw] ERROR: can't bind to: 0.0.0.0:8000 Apr 26 10:41:24 192.168.122.209 [67035.385071] [tempesta fw] ERROR: can't start listening on: 0.0.0.0:8000 Apr 26 10:41:24 192.168.122.209 [67035.387059] [tempesta fw] ERROR: Unable to start module 'sock_clnt': -98 Apr 26 10:41:24 192.168.122.209 [67035.572604] [tdb] Close table 'client0.tdb' Apr 26 10:41:25 192.168.122.209 [67035.755746] [tdb] Close table 'sessions0.tdb' Apr 26 10:41:28 192.168.122.209 [67038.941894] [tdb] Close table 'cache0.tdb' Apr 26 10:41:28 192.168.122.209 [67039.213901] [tdb] Close table 'filter0.tdb' Apr 26 10:41:28 192.168.122.209 [67039.214300] [tempesta fw] modules are stopped Apr 26 10:41:28 192.168.122.209 [67039.214756] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 10:41:28 192.168.122.209 [67039.407257] [tempesta fw] exiting... Apr 26 10:41:28 192.168.122.209 [67039.540770] [tdb] Shutdown Tempesta DB Apr 26 10:41:29 192.168.122.209 [67040.132080] End test: t_reconf.test_reconf_base.TestListenCommonReconf.test_reconf_busy_socks Apr 26 10:41:29 192.168.122.209 [67040.147360] Start test: t_reconf.test_reconf_base.TestListenCommonReconf.test_stop Apr 26 10:41:30 192.168.122.209 [67041.376657] [tdb] Start Tempesta DB Apr 26 10:41:30 192.168.122.209 [67041.536045] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:41:32 192.168.122.209 [67042.731714] [tempesta fw] Configuration processing is completed. Apr 26 10:41:32 192.168.122.209 [67042.802554] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:41:32 192.168.122.209 [67043.246970] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:41:32 192.168.122.209 [67043.280991] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:41:32 192.168.122.209 [67043.306464] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:41:32 192.168.122.209 [67043.307586] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:41:32 192.168.122.209 [67043.326746] [tempesta fw] Tempesta FW is ready Apr 26 10:41:33 192.168.122.209 [67043.655434] [tdb] Close table 'client0.tdb' Apr 26 10:41:33 192.168.122.209 [67043.849251] [tdb] Close table 'sessions0.tdb' Apr 26 10:41:36 192.168.122.209 [67047.056722] [tdb] Close table 'cache0.tdb' Apr 26 10:41:36 192.168.122.209 [67047.311768] [tdb] Close table 'filter0.tdb' Apr 26 10:41:36 192.168.122.209 [67047.312167] [tempesta fw] modules are stopped Apr 26 10:41:38 192.168.122.209 [67048.777976] [tempesta fw] Configuration processing is completed. Apr 26 10:41:38 192.168.122.209 [67048.833012] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:41:38 192.168.122.209 [67049.268251] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:41:38 192.168.122.209 [67049.295745] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:41:38 192.168.122.209 [67049.322054] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:41:38 192.168.122.209 [67049.323188] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:41:38 192.168.122.209 [67049.350861] [tempesta fw] Tempesta FW is ready Apr 26 10:41:39 192.168.122.209 [67049.756242] [tdb] Close table 'client0.tdb' Apr 26 10:41:39 192.168.122.209 [67049.929419] [tdb] Close table 'sessions0.tdb' Apr 26 10:41:42 192.168.122.209 [67053.083786] [tdb] Close table 'cache0.tdb' Apr 26 10:41:42 192.168.122.209 [67053.345601] [tdb] Close table 'filter0.tdb' Apr 26 10:41:42 192.168.122.209 [67053.346011] [tempesta fw] modules are stopped Apr 26 10:41:42 192.168.122.209 [67053.540230] [tempesta fw] exiting... Apr 26 10:41:43 192.168.122.209 [67053.695225] [tdb] Shutdown Tempesta DB Apr 26 10:41:43 192.168.122.209 [67053.937522] End test: t_reconf.test_reconf_base.TestListenCommonReconf.test_stop Apr 26 10:41:43 192.168.122.209 [67053.956373] Start test: t_reconf.test_reconf_base.TestListenReconfH2.test_reconf_add_listen Apr 26 10:41:44 192.168.122.209 [67055.029017] [tdb] Start Tempesta DB Apr 26 10:41:44 192.168.122.209 [67055.167218] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:41:45 192.168.122.209 [67056.452255] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67056.452255] Maybe that's fine, but it's worth checking the [67056.452255] config - if there is no relations between the [67056.452255] names, then host name confusion attack is possible. Apr 26 10:41:45 192.168.122.209 [67056.551027] [tempesta fw] Configuration processing is completed. Apr 26 10:41:45 192.168.122.209 [67056.604750] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:41:46 192.168.122.209 [67057.054099] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:41:46 192.168.122.209 [67057.081207] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:41:46 192.168.122.209 [67057.108524] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:41:46 192.168.122.209 [67057.150970] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:41:46 192.168.122.209 [67057.194908] [tempesta fw] Tempesta FW is ready Apr 26 10:41:47 192.168.122.209 [67057.656537] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:41:47 192.168.122.209 [67057.732310] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67057.732310] Maybe that's fine, but it's worth checking the [67057.732310] config - if there is no relations between the [67057.732310] names, then host name confusion attack is possible. Apr 26 10:41:47 192.168.122.209 [67057.846927] [tempesta fw] Configuration processing is completed. Apr 26 10:41:47 192.168.122.209 [67058.075116] [tempesta fw] Open listen socket on: 0.0.0.0:444 Apr 26 10:41:47 192.168.122.209 [67058.139347] [tempesta fw] Tempesta FW is ready Apr 26 10:41:48 192.168.122.209 [67058.708300] [tdb] Close table 'client0.tdb' Apr 26 10:41:48 192.168.122.209 [67058.915636] [tdb] Close table 'sessions0.tdb' Apr 26 10:41:51 192.168.122.209 [67062.080541] [tdb] Close table 'cache0.tdb' Apr 26 10:41:51 192.168.122.209 [67062.332524] [tdb] Close table 'filter0.tdb' Apr 26 10:41:51 192.168.122.209 [67062.333139] [tempesta fw] modules are stopped Apr 26 10:41:51 192.168.122.209 [67062.510647] [tempesta fw] exiting... Apr 26 10:41:52 192.168.122.209 [67062.673250] [tdb] Shutdown Tempesta DB Apr 26 10:41:52 192.168.122.209 [67062.891484] End test: t_reconf.test_reconf_base.TestListenReconfH2.test_reconf_add_listen Apr 26 10:41:52 192.168.122.209 [67062.906370] Start test: t_reconf.test_reconf_base.TestListenReconfH2.test_reconf_ip_default_to_ipv4_port_default Apr 26 10:41:53 192.168.122.209 [67063.986965] [tdb] Start Tempesta DB Apr 26 10:41:53 192.168.122.209 [67064.124634] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:41:54 192.168.122.209 [67065.357756] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67065.357756] Maybe that's fine, but it's worth checking the [67065.357756] config - if there is no relations between the [67065.357756] names, then host name confusion attack is possible. Apr 26 10:41:54 192.168.122.209 [67065.440632] [tempesta fw] Warning: TLS: no HTTPS listener set, configuration is ignored. Apr 26 10:41:54 192.168.122.209 [67065.459159] [tempesta fw] Configuration processing is completed. Apr 26 10:41:54 192.168.122.209 [67065.517823] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:41:55 192.168.122.209 [67065.960093] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:41:55 192.168.122.209 [67065.986633] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:41:55 192.168.122.209 [67066.012831] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:41:55 192.168.122.209 [67066.059079] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:41:55 192.168.122.209 [67066.099033] [tempesta fw] Tempesta FW is ready Apr 26 10:41:55 192.168.122.209 [67066.546185] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:41:55 192.168.122.209 [67066.595442] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67066.595442] Maybe that's fine, but it's worth checking the [67066.595442] config - if there is no relations between the [67066.595442] names, then host name confusion attack is possible. Apr 26 10:41:56 192.168.122.209 [67066.723065] [tempesta fw] Configuration processing is completed. Apr 26 10:41:56 192.168.122.209 [67066.951313] [tempesta fw] Open listen socket on: 127.0.0.1 Apr 26 10:41:56 192.168.122.209 [67067.023420] [tempesta fw] Tempesta FW is ready Apr 26 10:41:56 192.168.122.209 [67067.570284] [tdb] Close table 'client0.tdb' Apr 26 10:41:57 192.168.122.209 [67067.759343] [tdb] Close table 'sessions0.tdb' Apr 26 10:42:00 192.168.122.209 [67070.901577] [tdb] Close table 'cache0.tdb' Apr 26 10:42:00 192.168.122.209 [67071.126944] [tdb] Close table 'filter0.tdb' Apr 26 10:42:00 192.168.122.209 [67071.127361] [tempesta fw] modules are stopped Apr 26 10:42:00 192.168.122.209 [67071.363275] [tempesta fw] exiting... Apr 26 10:42:00 192.168.122.209 [67071.492791] [tdb] Shutdown Tempesta DB Apr 26 10:42:01 192.168.122.209 [67071.711895] End test: t_reconf.test_reconf_base.TestListenReconfH2.test_reconf_ip_default_to_ipv4_port_default Apr 26 10:42:01 192.168.122.209 [67071.724643] Start test: t_reconf.test_reconf_base.TestListenReconfH2.test_reconf_ip_ipv4_to_ipv4_port_443 Apr 26 10:42:02 192.168.122.209 [67072.757677] [tdb] Start Tempesta DB Apr 26 10:42:02 192.168.122.209 [67072.895697] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:42:03 192.168.122.209 [67074.184472] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67074.184472] Maybe that's fine, but it's worth checking the [67074.184472] config - if there is no relations between the [67074.184472] names, then host name confusion attack is possible. Apr 26 10:42:03 192.168.122.209 [67074.283230] [tempesta fw] Configuration processing is completed. Apr 26 10:42:03 192.168.122.209 [67074.341100] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:42:04 192.168.122.209 [67074.808030] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:42:04 192.168.122.209 [67074.836201] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:42:04 192.168.122.209 [67074.862469] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:42:04 192.168.122.209 [67074.907186] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 10:42:04 192.168.122.209 [67074.975128] [tempesta fw] Tempesta FW is ready Apr 26 10:42:04 192.168.122.209 [67075.421339] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:42:04 192.168.122.209 [67075.472449] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67075.472449] Maybe that's fine, but it's worth checking the [67075.472449] config - if there is no relations between the [67075.472449] names, then host name confusion attack is possible. Apr 26 10:42:04 192.168.122.209 [67075.595559] [tempesta fw] Configuration processing is completed. Apr 26 10:42:05 192.168.122.209 [67075.827334] [tempesta fw] Open listen socket on: 127.0.1.100:443 Apr 26 10:42:05 192.168.122.209 [67075.891539] [tempesta fw] Tempesta FW is ready Apr 26 10:42:05 192.168.122.209 [67076.461310] [tdb] Close table 'client0.tdb' Apr 26 10:42:05 192.168.122.209 [67076.647939] [tdb] Close table 'sessions0.tdb' Apr 26 10:42:09 192.168.122.209 [67079.942373] [tdb] Close table 'cache0.tdb' Apr 26 10:42:09 192.168.122.209 [67080.198246] [tdb] Close table 'filter0.tdb' Apr 26 10:42:09 192.168.122.209 [67080.198685] [tempesta fw] modules are stopped Apr 26 10:42:09 192.168.122.209 [67080.370643] [tempesta fw] exiting... Apr 26 10:42:09 192.168.122.209 [67080.485840] [tdb] Shutdown Tempesta DB Apr 26 10:42:10 192.168.122.209 [67080.691006] End test: t_reconf.test_reconf_base.TestListenReconfH2.test_reconf_ip_ipv4_to_ipv4_port_443 Apr 26 10:42:10 192.168.122.209 [67080.709765] Start test: t_reconf.test_reconf_base.TestListenReconfH2.test_reconf_ip_ipv4_to_ipv4_port_default Apr 26 10:42:11 192.168.122.209 [67081.744707] [tdb] Start Tempesta DB Apr 26 10:42:11 192.168.122.209 [67081.876348] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:42:12 192.168.122.209 [67083.168611] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67083.168611] Maybe that's fine, but it's worth checking the [67083.168611] config - if there is no relations between the [67083.168611] names, then host name confusion attack is possible. Apr 26 10:42:12 192.168.122.209 [67083.275352] [tempesta fw] Configuration processing is completed. Apr 26 10:42:12 192.168.122.209 [67083.348905] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:42:13 192.168.122.209 [67083.802114] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:42:13 192.168.122.209 [67083.829986] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:42:13 192.168.122.209 [67083.856266] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:42:13 192.168.122.209 [67083.919248] [tempesta fw] Open listen socket on: 127.0.0.1 Apr 26 10:42:13 192.168.122.209 [67083.967259] [tempesta fw] Tempesta FW is ready Apr 26 10:42:13 192.168.122.209 [67084.414492] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:42:13 192.168.122.209 [67084.464259] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67084.464259] Maybe that's fine, but it's worth checking the [67084.464259] config - if there is no relations between the [67084.464259] names, then host name confusion attack is possible. Apr 26 10:42:13 192.168.122.209 [67084.599268] [tempesta fw] Configuration processing is completed. Apr 26 10:42:14 192.168.122.209 [67084.839545] [tempesta fw] Open listen socket on: 127.0.1.100 Apr 26 10:42:14 192.168.122.209 [67084.907665] [tempesta fw] Tempesta FW is ready Apr 26 10:42:14 192.168.122.209 [67085.492514] [tdb] Close table 'client0.tdb' Apr 26 10:42:15 192.168.122.209 [67085.678394] [tdb] Close table 'sessions0.tdb' Apr 26 10:42:18 192.168.122.209 [67088.850518] [tdb] Close table 'cache0.tdb' Apr 26 10:42:18 192.168.122.209 [67089.058606] [tdb] Close table 'filter0.tdb' Apr 26 10:42:18 192.168.122.209 [67089.059045] [tempesta fw] modules are stopped Apr 26 10:42:18 192.168.122.209 [67089.259995] [tempesta fw] exiting... Apr 26 10:42:18 192.168.122.209 [67089.389482] [tdb] Shutdown Tempesta DB Apr 26 10:42:18 192.168.122.209 [67089.577522] End test: t_reconf.test_reconf_base.TestListenReconfH2.test_reconf_ip_ipv4_to_ipv4_port_default Apr 26 10:42:18 192.168.122.209 [67089.596884] Start test: t_reconf.test_reconf_base.TestListenReconfH2.test_reconf_port Apr 26 10:42:19 192.168.122.209 [67090.646385] [tdb] Start Tempesta DB Apr 26 10:42:20 192.168.122.209 [67090.779766] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:42:21 192.168.122.209 [67092.068826] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67092.068826] Maybe that's fine, but it's worth checking the [67092.068826] config - if there is no relations between the [67092.068826] names, then host name confusion attack is possible. Apr 26 10:42:21 192.168.122.209 [67092.203472] [tempesta fw] Configuration processing is completed. Apr 26 10:42:21 192.168.122.209 [67092.257592] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:42:22 192.168.122.209 [67092.700394] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:42:22 192.168.122.209 [67092.735775] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:42:22 192.168.122.209 [67092.761894] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:42:22 192.168.122.209 [67092.823396] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:42:22 192.168.122.209 [67092.879349] [tempesta fw] Tempesta FW is ready Apr 26 10:42:22 192.168.122.209 [67093.321294] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:42:22 192.168.122.209 [67093.372666] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67093.372666] Maybe that's fine, but it's worth checking the [67093.372666] config - if there is no relations between the [67093.372666] names, then host name confusion attack is possible. Apr 26 10:42:22 192.168.122.209 [67093.511400] [tempesta fw] Configuration processing is completed. Apr 26 10:42:23 192.168.122.209 [67093.719547] [tempesta fw] Open listen socket on: 0.0.0.0:4433 Apr 26 10:42:23 192.168.122.209 [67093.779764] [tempesta fw] Tempesta FW is ready Apr 26 10:42:23 192.168.122.209 [67094.283537] [tdb] Close table 'client0.tdb' Apr 26 10:42:23 192.168.122.209 [67094.473336] [tdb] Close table 'sessions0.tdb' Apr 26 10:42:26 192.168.122.209 [67097.640050] [tdb] Close table 'cache0.tdb' Apr 26 10:42:27 192.168.122.209 [67097.890842] [tdb] Close table 'filter0.tdb' Apr 26 10:42:27 192.168.122.209 [67097.891284] [tempesta fw] modules are stopped Apr 26 10:42:27 192.168.122.209 [67098.087757] [tempesta fw] exiting... Apr 26 10:42:27 192.168.122.209 [67098.203999] [tdb] Shutdown Tempesta DB Apr 26 10:42:27 192.168.122.209 [67098.402746] End test: t_reconf.test_reconf_base.TestListenReconfH2.test_reconf_port Apr 26 10:42:27 192.168.122.209 [67098.413476] Start test: t_reconf.test_reconf_base.TestListenReconfH2.test_reconf_proto_h2 Apr 26 10:42:28 192.168.122.209 [67099.510701] [tdb] Start Tempesta DB Apr 26 10:42:29 192.168.122.209 [67099.652792] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:42:30 192.168.122.209 [67101.000795] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67101.000795] Maybe that's fine, but it's worth checking the [67101.000795] config - if there is no relations between the [67101.000795] names, then host name confusion attack is possible. Apr 26 10:42:30 192.168.122.209 [67101.111631] [tempesta fw] Configuration processing is completed. Apr 26 10:42:30 192.168.122.209 [67101.169792] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:42:30 192.168.122.209 [67101.614241] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:42:30 192.168.122.209 [67101.641162] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:42:31 192.168.122.209 [67101.668509] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:42:31 192.168.122.209 [67101.715520] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:42:31 192.168.122.209 [67101.763466] [tempesta fw] Tempesta FW is ready Apr 26 10:42:31 192.168.122.209 [67102.205397] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:42:31 192.168.122.209 [67102.252805] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67102.252805] Maybe that's fine, but it's worth checking the [67102.252805] config - if there is no relations between the [67102.252805] names, then host name confusion attack is possible. Apr 26 10:42:31 192.168.122.209 [67102.371587] [tempesta fw] Configuration processing is completed. Apr 26 10:42:31 192.168.122.209 [67102.623867] [tempesta fw] Tempesta FW is ready Apr 26 10:42:32 192.168.122.209 [67103.149250] [tdb] Close table 'client0.tdb' Apr 26 10:42:32 192.168.122.209 [67103.336830] [tdb] Close table 'sessions0.tdb' Apr 26 10:42:35 192.168.122.209 [67106.559064] [tdb] Close table 'cache0.tdb' Apr 26 10:42:36 192.168.122.209 [67106.799414] [tdb] Close table 'filter0.tdb' Apr 26 10:42:36 192.168.122.209 [67106.799864] [tempesta fw] modules are stopped Apr 26 10:42:36 192.168.122.209 [67107.045350] [tempesta fw] exiting... Apr 26 10:42:36 192.168.122.209 [67107.182853] [tdb] Shutdown Tempesta DB Apr 26 10:42:36 192.168.122.209 [67107.409978] End test: t_reconf.test_reconf_base.TestListenReconfH2.test_reconf_proto_h2 Apr 26 10:42:36 192.168.122.209 [67107.417718] Start test: t_reconf.test_reconf_base.TestListenReconfH2.test_reconf_proto_h2_https Apr 26 10:42:37 192.168.122.209 [67108.572701] [tdb] Start Tempesta DB Apr 26 10:42:38 192.168.122.209 [67108.738308] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:42:39 192.168.122.209 [67110.036298] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67110.036298] Maybe that's fine, but it's worth checking the [67110.036298] config - if there is no relations between the [67110.036298] names, then host name confusion attack is possible. Apr 26 10:42:39 192.168.122.209 [67110.139714] [tempesta fw] Configuration processing is completed. Apr 26 10:42:39 192.168.122.209 [67110.193827] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:42:40 192.168.122.209 [67110.688148] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:42:40 192.168.122.209 [67110.720101] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:42:40 192.168.122.209 [67110.752049] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:42:40 192.168.122.209 [67110.795634] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:42:40 192.168.122.209 [67110.835581] [tempesta fw] Tempesta FW is ready Apr 26 10:42:40 192.168.122.209 [67111.297824] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:42:40 192.168.122.209 [67111.348241] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67111.348241] Maybe that's fine, but it's worth checking the [67111.348241] config - if there is no relations between the [67111.348241] names, then host name confusion attack is possible. Apr 26 10:42:40 192.168.122.209 [67111.459662] [tempesta fw] Configuration processing is completed. Apr 26 10:42:41 192.168.122.209 [67111.659774] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:42:41 192.168.122.209 [67111.719685] [tempesta fw] Tempesta FW is ready Apr 26 10:42:41 192.168.122.209 [67112.239041] [tdb] Close table 'client0.tdb' Apr 26 10:42:41 192.168.122.209 [67112.424659] [tdb] Close table 'sessions0.tdb' Apr 26 10:42:45 192.168.122.209 [67115.672518] [tdb] Close table 'cache0.tdb' Apr 26 10:42:45 192.168.122.209 [67115.935436] [tdb] Close table 'filter0.tdb' Apr 26 10:42:45 192.168.122.209 [67115.935899] [tempesta fw] modules are stopped Apr 26 10:42:45 192.168.122.209 [67116.144259] [tempesta fw] exiting... Apr 26 10:42:45 192.168.122.209 [67116.262228] [tdb] Shutdown Tempesta DB Apr 26 10:42:45 192.168.122.209 [67116.505402] End test: t_reconf.test_reconf_base.TestListenReconfH2.test_reconf_proto_h2_https Apr 26 10:42:45 192.168.122.209 [67116.517840] Start test: t_reconf.test_reconf_base.TestListenReconfH2.test_reconf_proto_http Apr 26 10:42:46 192.168.122.209 [67117.583817] [tdb] Start Tempesta DB Apr 26 10:42:47 192.168.122.209 [67117.751598] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:42:48 192.168.122.209 [67119.073083] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67119.073083] Maybe that's fine, but it's worth checking the [67119.073083] config - if there is no relations between the [67119.073083] names, then host name confusion attack is possible. Apr 26 10:42:48 192.168.122.209 [67119.175825] [tempesta fw] Configuration processing is completed. Apr 26 10:42:48 192.168.122.209 [67119.233793] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:42:49 192.168.122.209 [67119.732882] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:42:49 192.168.122.209 [67119.776549] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:42:49 192.168.122.209 [67119.809191] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:42:49 192.168.122.209 [67119.859764] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:42:49 192.168.122.209 [67119.907677] [tempesta fw] Tempesta FW is ready Apr 26 10:42:49 192.168.122.209 [67120.363417] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:42:49 192.168.122.209 [67120.412914] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67120.412914] Maybe that's fine, but it's worth checking the [67120.412914] config - if there is no relations between the [67120.412914] names, then host name confusion attack is possible. Apr 26 10:42:49 192.168.122.209 [67120.539763] [tempesta fw] Configuration processing is completed. Apr 26 10:42:50 192.168.122.209 [67120.751975] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:42:50 192.168.122.209 [67120.816137] [tempesta fw] Tempesta FW is ready Apr 26 10:42:50 192.168.122.209 [67121.238523] [tdb] Close table 'client0.tdb' Apr 26 10:42:50 192.168.122.209 [67121.423286] [tdb] Close table 'sessions0.tdb' Apr 26 10:42:54 192.168.122.209 [67124.727160] [tdb] Close table 'cache0.tdb' Apr 26 10:42:54 192.168.122.209 [67124.972534] [tdb] Close table 'filter0.tdb' Apr 26 10:42:54 192.168.122.209 [67124.972956] [tempesta fw] modules are stopped Apr 26 10:42:54 192.168.122.209 [67125.207157] [tempesta fw] exiting... Apr 26 10:42:54 192.168.122.209 [67125.357469] [tdb] Shutdown Tempesta DB Apr 26 10:42:54 192.168.122.209 [67125.566479] End test: t_reconf.test_reconf_base.TestListenReconfH2.test_reconf_proto_http Apr 26 10:42:54 192.168.122.209 [67125.583259] Start test: t_reconf.test_reconf_base.TestListenReconfH2.test_reconf_proto_https Apr 26 10:42:56 192.168.122.209 [67126.680893] [tdb] Start Tempesta DB Apr 26 10:42:56 192.168.122.209 [67126.835546] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:42:57 192.168.122.209 [67128.077232] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67128.077232] Maybe that's fine, but it's worth checking the [67128.077232] config - if there is no relations between the [67128.077232] names, then host name confusion attack is possible. Apr 26 10:42:57 192.168.122.209 [67128.175921] [tempesta fw] Configuration processing is completed. Apr 26 10:42:57 192.168.122.209 [67128.232107] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:42:58 192.168.122.209 [67128.674038] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:42:58 192.168.122.209 [67128.721572] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:42:58 192.168.122.209 [67128.750587] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:42:58 192.168.122.209 [67128.791852] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:42:58 192.168.122.209 [67128.839811] [tempesta fw] Tempesta FW is ready Apr 26 10:42:58 192.168.122.209 [67129.328926] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:42:58 192.168.122.209 [67129.360354] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67129.360354] Maybe that's fine, but it's worth checking the [67129.360354] config - if there is no relations between the [67129.360354] names, then host name confusion attack is possible. Apr 26 10:42:58 192.168.122.209 [67129.471918] [tempesta fw] Configuration processing is completed. Apr 26 10:42:59 192.168.122.209 [67129.676022] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:42:59 192.168.122.209 [67129.744191] [tempesta fw] Tempesta FW is ready Apr 26 10:42:59 192.168.122.209 [67130.243415] [tdb] Close table 'client0.tdb' Apr 26 10:42:59 192.168.122.209 [67130.431307] [tdb] Close table 'sessions0.tdb' Apr 26 10:43:03 192.168.122.209 [67133.833985] [tdb] Close table 'cache0.tdb' Apr 26 10:43:03 192.168.122.209 [67134.100381] [tdb] Close table 'filter0.tdb' Apr 26 10:43:03 192.168.122.209 [67134.100803] [tempesta fw] modules are stopped Apr 26 10:43:03 192.168.122.209 [67134.304565] [tempesta fw] exiting... Apr 26 10:43:03 192.168.122.209 [67134.424536] [tdb] Shutdown Tempesta DB Apr 26 10:43:03 192.168.122.209 [67134.636106] End test: t_reconf.test_reconf_base.TestListenReconfH2.test_reconf_proto_https Apr 26 10:43:03 192.168.122.209 [67134.643619] Start test: t_reconf.test_reconf_base.TestListenReconfH2.test_reconf_remove_listen Apr 26 10:43:05 192.168.122.209 [67135.751563] [tdb] Start Tempesta DB Apr 26 10:43:05 192.168.122.209 [67135.893176] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:43:06 192.168.122.209 [67137.257314] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67137.257314] Maybe that's fine, but it's worth checking the [67137.257314] config - if there is no relations between the [67137.257314] names, then host name confusion attack is possible. Apr 26 10:43:06 192.168.122.209 [67137.356095] [tempesta fw] Configuration processing is completed. Apr 26 10:43:06 192.168.122.209 [67137.416369] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:43:07 192.168.122.209 [67137.973098] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:43:07 192.168.122.209 [67138.014666] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:43:07 192.168.122.209 [67138.052295] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:43:07 192.168.122.209 [67138.095997] [tempesta fw] Open listen socket on: 0.0.0.0:444 Apr 26 10:43:07 192.168.122.209 [67138.097762] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:43:07 192.168.122.209 [67138.135908] [tempesta fw] Tempesta FW is ready Apr 26 10:43:07 192.168.122.209 [67138.609808] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:43:08 192.168.122.209 [67138.657254] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67138.657254] Maybe that's fine, but it's worth checking the [67138.657254] config - if there is no relations between the [67138.657254] names, then host name confusion attack is possible. Apr 26 10:43:08 192.168.122.209 [67138.791977] [tempesta fw] Configuration processing is completed. Apr 26 10:43:08 192.168.122.209 [67139.084319] [tempesta fw] Tempesta FW is ready Apr 26 10:43:08 192.168.122.209 [67139.644825] [tdb] Close table 'client0.tdb' Apr 26 10:43:09 192.168.122.209 [67139.832777] [tdb] Close table 'sessions0.tdb' Apr 26 10:43:12 192.168.122.209 [67142.989731] [tdb] Close table 'cache0.tdb' Apr 26 10:43:12 192.168.122.209 [67143.241901] [tdb] Close table 'filter0.tdb' Apr 26 10:43:12 192.168.122.209 [67143.242360] [tempesta fw] modules are stopped Apr 26 10:43:12 192.168.122.209 [67143.436281] [tempesta fw] exiting... Apr 26 10:43:12 192.168.122.209 [67143.581399] [tdb] Shutdown Tempesta DB Apr 26 10:43:13 192.168.122.209 [67143.772904] End test: t_reconf.test_reconf_base.TestListenReconfH2.test_reconf_remove_listen Apr 26 10:43:13 192.168.122.209 [67143.791432] Start test: t_reconf.test_reconf_base.TestListenReconfH2AndHttps.test_reconf_add_listen Apr 26 10:43:14 192.168.122.209 [67144.817239] [tdb] Start Tempesta DB Apr 26 10:43:14 192.168.122.209 [67144.950352] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:43:15 192.168.122.209 [67146.229335] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67146.229335] Maybe that's fine, but it's worth checking the [67146.229335] config - if there is no relations between the [67146.229335] names, then host name confusion attack is possible. Apr 26 10:43:15 192.168.122.209 [67146.328144] [tempesta fw] Configuration processing is completed. Apr 26 10:43:15 192.168.122.209 [67146.385519] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:43:16 192.168.122.209 [67146.931680] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:43:16 192.168.122.209 [67146.966856] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:43:16 192.168.122.209 [67146.993020] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:43:16 192.168.122.209 [67147.044087] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:43:16 192.168.122.209 [67147.092028] [tempesta fw] Tempesta FW is ready Apr 26 10:43:16 192.168.122.209 [67147.540912] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:43:16 192.168.122.209 [67147.621266] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67147.621266] Maybe that's fine, but it's worth checking the [67147.621266] config - if there is no relations between the [67147.621266] names, then host name confusion attack is possible. Apr 26 10:43:17 192.168.122.209 [67147.740168] [tempesta fw] Configuration processing is completed. Apr 26 10:43:17 192.168.122.209 [67147.948210] [tempesta fw] Open listen socket on: 0.0.0.0:444 Apr 26 10:43:17 192.168.122.209 [67148.004494] [tempesta fw] Tempesta FW is ready Apr 26 10:43:18 192.168.122.209 [67148.673140] [tdb] Close table 'client0.tdb' Apr 26 10:43:18 192.168.122.209 [67148.884902] [tdb] Close table 'sessions0.tdb' Apr 26 10:43:21 192.168.122.209 [67152.074002] [tdb] Close table 'cache0.tdb' Apr 26 10:43:21 192.168.122.209 [67152.355157] [tdb] Close table 'filter0.tdb' Apr 26 10:43:21 192.168.122.209 [67152.355568] [tempesta fw] modules are stopped Apr 26 10:43:21 192.168.122.209 [67152.543233] [tempesta fw] exiting... Apr 26 10:43:22 192.168.122.209 [67152.708915] [tdb] Shutdown Tempesta DB Apr 26 10:43:22 192.168.122.209 [67152.931848] End test: t_reconf.test_reconf_base.TestListenReconfH2AndHttps.test_reconf_add_listen Apr 26 10:43:22 192.168.122.209 [67152.947795] Start test: t_reconf.test_reconf_base.TestListenReconfH2AndHttps.test_reconf_ip_default_to_ipv4_port_default Apr 26 10:43:23 192.168.122.209 [67154.231382] [tdb] Start Tempesta DB Apr 26 10:43:23 192.168.122.209 [67154.372249] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:43:25 192.168.122.209 [67155.740487] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67155.740487] Maybe that's fine, but it's worth checking the [67155.740487] config - if there is no relations between the [67155.740487] names, then host name confusion attack is possible. Apr 26 10:43:25 192.168.122.209 [67155.833235] [tempesta fw] Warning: TLS: no HTTPS listener set, configuration is ignored. Apr 26 10:43:25 192.168.122.209 [67155.852265] [tempesta fw] Configuration processing is completed. Apr 26 10:43:25 192.168.122.209 [67155.921918] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:43:25 192.168.122.209 [67156.499224] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:43:25 192.168.122.209 [67156.533635] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:43:25 192.168.122.209 [67156.571763] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:43:25 192.168.122.209 [67156.624103] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:43:26 192.168.122.209 [67156.664126] [tempesta fw] Tempesta FW is ready Apr 26 10:43:26 192.168.122.209 [67157.129761] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:43:26 192.168.122.209 [67157.173161] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67157.173161] Maybe that's fine, but it's worth checking the [67157.173161] config - if there is no relations between the [67157.173161] names, then host name confusion attack is possible. Apr 26 10:43:26 192.168.122.209 [67157.300182] [tempesta fw] Configuration processing is completed. Apr 26 10:43:26 192.168.122.209 [67157.488331] [tempesta fw] Open listen socket on: 127.0.0.1 Apr 26 10:43:26 192.168.122.209 [67157.544534] [tempesta fw] Tempesta FW is ready Apr 26 10:43:27 192.168.122.209 [67158.068713] [tdb] Close table 'client0.tdb' Apr 26 10:43:27 192.168.122.209 [67158.263937] [tdb] Close table 'sessions0.tdb' Apr 26 10:43:30 192.168.122.209 [67161.572846] [tdb] Close table 'cache0.tdb' Apr 26 10:43:31 192.168.122.209 [67161.816731] [tdb] Close table 'filter0.tdb' Apr 26 10:43:31 192.168.122.209 [67161.817178] [tempesta fw] modules are stopped Apr 26 10:43:31 192.168.122.209 [67162.053483] [tempesta fw] exiting... Apr 26 10:43:31 192.168.122.209 [67162.178930] [tdb] Shutdown Tempesta DB Apr 26 10:43:31 192.168.122.209 [67162.406687] End test: t_reconf.test_reconf_base.TestListenReconfH2AndHttps.test_reconf_ip_default_to_ipv4_port_default Apr 26 10:43:31 192.168.122.209 [67162.431724] Start test: t_reconf.test_reconf_base.TestListenReconfH2AndHttps.test_reconf_ip_ipv4_to_ipv4_port_443 Apr 26 10:43:33 192.168.122.209 [67163.650615] [tdb] Start Tempesta DB Apr 26 10:43:33 192.168.122.209 [67163.801942] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:43:34 192.168.122.209 [67165.189779] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67165.189779] Maybe that's fine, but it's worth checking the [67165.189779] config - if there is no relations between the [67165.189779] names, then host name confusion attack is possible. Apr 26 10:43:34 192.168.122.209 [67165.304354] [tempesta fw] Configuration processing is completed. Apr 26 10:43:34 192.168.122.209 [67165.366941] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:43:35 192.168.122.209 [67165.796782] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:43:35 192.168.122.209 [67165.823078] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:43:35 192.168.122.209 [67165.849307] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:43:35 192.168.122.209 [67165.892295] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 10:43:35 192.168.122.209 [67165.936256] [tempesta fw] Tempesta FW is ready Apr 26 10:43:35 192.168.122.209 [67166.388951] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:43:35 192.168.122.209 [67166.445521] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67166.445521] Maybe that's fine, but it's worth checking the [67166.445521] config - if there is no relations between the [67166.445521] names, then host name confusion attack is possible. Apr 26 10:43:35 192.168.122.209 [67166.564221] [tempesta fw] Configuration processing is completed. Apr 26 10:43:36 192.168.122.209 [67166.780483] [tempesta fw] Open listen socket on: 127.0.1.100:443 Apr 26 10:43:36 192.168.122.209 [67166.848634] [tempesta fw] Tempesta FW is ready Apr 26 10:43:36 192.168.122.209 [67167.441366] [tdb] Close table 'client0.tdb' Apr 26 10:43:36 192.168.122.209 [67167.631983] [tdb] Close table 'sessions0.tdb' Apr 26 10:43:40 192.168.122.209 [67170.845306] [tdb] Close table 'cache0.tdb' Apr 26 10:43:40 192.168.122.209 [67171.084914] [tdb] Close table 'filter0.tdb' Apr 26 10:43:40 192.168.122.209 [67171.085354] [tempesta fw] modules are stopped Apr 26 10:43:40 192.168.122.209 [67171.290494] [tempesta fw] exiting... Apr 26 10:43:40 192.168.122.209 [67171.426526] [tdb] Shutdown Tempesta DB Apr 26 10:43:41 192.168.122.209 [67171.661329] End test: t_reconf.test_reconf_base.TestListenReconfH2AndHttps.test_reconf_ip_ipv4_to_ipv4_port_443 Apr 26 10:43:41 192.168.122.209 [67171.672243] Start test: t_reconf.test_reconf_base.TestListenReconfH2AndHttps.test_reconf_ip_ipv4_to_ipv4_port_default Apr 26 10:43:42 192.168.122.209 [67172.834271] [tdb] Start Tempesta DB Apr 26 10:43:42 192.168.122.209 [67172.993079] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:43:43 192.168.122.209 [67174.405736] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67174.405736] Maybe that's fine, but it's worth checking the [67174.405736] config - if there is no relations between the [67174.405736] names, then host name confusion attack is possible. Apr 26 10:43:43 192.168.122.209 [67174.528517] [tempesta fw] Configuration processing is completed. Apr 26 10:43:43 192.168.122.209 [67174.597396] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:43:44 192.168.122.209 [67175.166912] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:43:44 192.168.122.209 [67175.200485] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:43:44 192.168.122.209 [67175.234723] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:43:44 192.168.122.209 [67175.300417] [tempesta fw] Open listen socket on: 127.0.0.1 Apr 26 10:43:44 192.168.122.209 [67175.352384] [tempesta fw] Tempesta FW is ready Apr 26 10:43:45 192.168.122.209 [67175.831319] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:43:45 192.168.122.209 [67175.881011] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67175.881011] Maybe that's fine, but it's worth checking the [67175.881011] config - if there is no relations between the [67175.881011] names, then host name confusion attack is possible. Apr 26 10:43:45 192.168.122.209 [67176.028437] [tempesta fw] Configuration processing is completed. Apr 26 10:43:45 192.168.122.209 [67176.224597] [tempesta fw] Open listen socket on: 127.0.1.100 Apr 26 10:43:45 192.168.122.209 [67176.280808] [tempesta fw] Tempesta FW is ready Apr 26 10:43:46 192.168.122.209 [67176.880066] [tdb] Close table 'client0.tdb' Apr 26 10:43:46 192.168.122.209 [67177.072064] [tdb] Close table 'sessions0.tdb' Apr 26 10:43:49 192.168.122.209 [67180.347351] [tdb] Close table 'cache0.tdb' Apr 26 10:43:49 192.168.122.209 [67180.588100] [tdb] Close table 'filter0.tdb' Apr 26 10:43:49 192.168.122.209 [67180.588569] [tempesta fw] modules are stopped Apr 26 10:43:50 192.168.122.209 [67180.812060] [tempesta fw] exiting... Apr 26 10:43:50 192.168.122.209 [67180.946542] [tdb] Shutdown Tempesta DB Apr 26 10:43:50 192.168.122.209 [67181.131993] End test: t_reconf.test_reconf_base.TestListenReconfH2AndHttps.test_reconf_ip_ipv4_to_ipv4_port_default Apr 26 10:43:50 192.168.122.209 [67181.149272] Start test: t_reconf.test_reconf_base.TestListenReconfH2AndHttps.test_reconf_port Apr 26 10:43:51 192.168.122.209 [67182.281165] [tdb] Start Tempesta DB Apr 26 10:43:51 192.168.122.209 [67182.438763] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:43:53 192.168.122.209 [67183.809763] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67183.809763] Maybe that's fine, but it's worth checking the [67183.809763] config - if there is no relations between the [67183.809763] names, then host name confusion attack is possible. Apr 26 10:43:53 192.168.122.209 [67183.904846] [tempesta fw] Configuration processing is completed. Apr 26 10:43:53 192.168.122.209 [67183.955715] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:43:53 192.168.122.209 [67184.371734] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:43:53 192.168.122.209 [67184.397258] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:43:53 192.168.122.209 [67184.422924] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:43:53 192.168.122.209 [67184.468517] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:43:53 192.168.122.209 [67184.512454] [tempesta fw] Tempesta FW is ready Apr 26 10:43:54 192.168.122.209 [67185.015022] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:43:54 192.168.122.209 [67185.062184] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67185.062184] Maybe that's fine, but it's worth checking the [67185.062184] config - if there is no relations between the [67185.062184] names, then host name confusion attack is possible. Apr 26 10:43:54 192.168.122.209 [67185.200526] [tempesta fw] Configuration processing is completed. Apr 26 10:43:54 192.168.122.209 [67185.408695] [tempesta fw] Open listen socket on: 0.0.0.0:4433 Apr 26 10:43:54 192.168.122.209 [67185.464880] [tempesta fw] Tempesta FW is ready Apr 26 10:43:55 192.168.122.209 [67186.026442] [tdb] Close table 'client0.tdb' Apr 26 10:43:55 192.168.122.209 [67186.226605] [tdb] Close table 'sessions0.tdb' Apr 26 10:43:58 192.168.122.209 [67189.417922] [tdb] Close table 'cache0.tdb' Apr 26 10:43:59 192.168.122.209 [67189.677840] [tdb] Close table 'filter0.tdb' Apr 26 10:43:59 192.168.122.209 [67189.678269] [tempesta fw] modules are stopped Apr 26 10:43:59 192.168.122.209 [67189.851374] [tempesta fw] exiting... Apr 26 10:43:59 192.168.122.209 [67190.004339] [tdb] Shutdown Tempesta DB Apr 26 10:43:59 192.168.122.209 [67190.234100] End test: t_reconf.test_reconf_base.TestListenReconfH2AndHttps.test_reconf_port Apr 26 10:43:59 192.168.122.209 [67190.255310] Start test: t_reconf.test_reconf_base.TestListenReconfH2AndHttps.test_reconf_proto_h2 Apr 26 10:44:00 192.168.122.209 [67191.475545] [tdb] Start Tempesta DB Apr 26 10:44:00 192.168.122.209 [67191.620581] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:44:02 192.168.122.209 [67192.945973] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67192.945973] Maybe that's fine, but it's worth checking the [67192.945973] config - if there is no relations between the [67192.945973] names, then host name confusion attack is possible. Apr 26 10:44:02 192.168.122.209 [67193.048688] [tempesta fw] Configuration processing is completed. Apr 26 10:44:02 192.168.122.209 [67193.100412] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:44:02 192.168.122.209 [67193.506472] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:44:02 192.168.122.209 [67193.532725] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:44:02 192.168.122.209 [67193.559449] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:44:02 192.168.122.209 [67193.612641] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:44:03 192.168.122.209 [67193.652560] [tempesta fw] Tempesta FW is ready Apr 26 10:44:03 192.168.122.209 [67194.143063] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:44:03 192.168.122.209 [67194.194151] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67194.194151] Maybe that's fine, but it's worth checking the [67194.194151] config - if there is no relations between the [67194.194151] names, then host name confusion attack is possible. Apr 26 10:44:03 192.168.122.209 [67194.348627] [tempesta fw] Configuration processing is completed. Apr 26 10:44:03 192.168.122.209 [67194.584894] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:44:03 192.168.122.209 [67194.648984] [tempesta fw] Tempesta FW is ready Apr 26 10:44:04 192.168.122.209 [67195.208619] [tdb] Close table 'client0.tdb' Apr 26 10:44:04 192.168.122.209 [67195.400736] [tdb] Close table 'sessions0.tdb' Apr 26 10:44:07 192.168.122.209 [67198.519752] [tdb] Close table 'cache0.tdb' Apr 26 10:44:08 192.168.122.209 [67198.780664] [tdb] Close table 'filter0.tdb' Apr 26 10:44:08 192.168.122.209 [67198.781098] [tempesta fw] modules are stopped Apr 26 10:44:08 192.168.122.209 [67199.010805] [tempesta fw] exiting... Apr 26 10:44:08 192.168.122.209 [67199.146776] [tdb] Shutdown Tempesta DB Apr 26 10:44:08 192.168.122.209 [67199.374806] End test: t_reconf.test_reconf_base.TestListenReconfH2AndHttps.test_reconf_proto_h2 Apr 26 10:44:08 192.168.122.209 [67199.389144] Start test: t_reconf.test_reconf_base.TestListenReconfH2AndHttps.test_reconf_proto_h2_https Apr 26 10:44:09 192.168.122.209 [67200.645732] [tdb] Start Tempesta DB Apr 26 10:44:10 192.168.122.209 [67200.781382] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:44:11 192.168.122.209 [67202.122065] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67202.122065] Maybe that's fine, but it's worth checking the [67202.122065] config - if there is no relations between the [67202.122065] names, then host name confusion attack is possible. Apr 26 10:44:11 192.168.122.209 [67202.240842] [tempesta fw] Configuration processing is completed. Apr 26 10:44:11 192.168.122.209 [67202.327344] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:44:12 192.168.122.209 [67202.889311] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:44:12 192.168.122.209 [67202.923957] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:44:12 192.168.122.209 [67202.958024] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:44:12 192.168.122.209 [67202.996762] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:44:12 192.168.122.209 [67203.044690] [tempesta fw] Tempesta FW is ready Apr 26 10:44:12 192.168.122.209 [67203.553022] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:44:12 192.168.122.209 [67203.609616] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67203.609616] Maybe that's fine, but it's worth checking the [67203.609616] config - if there is no relations between the [67203.609616] names, then host name confusion attack is possible. Apr 26 10:44:13 192.168.122.209 [67203.721084] [tempesta fw] Configuration processing is completed. Apr 26 10:44:13 192.168.122.209 [67203.973114] [tempesta fw] Tempesta FW is ready Apr 26 10:44:13 192.168.122.209 [67204.515884] [tdb] Close table 'client0.tdb' Apr 26 10:44:14 192.168.122.209 [67204.724320] [tdb] Close table 'sessions0.tdb' Apr 26 10:44:17 192.168.122.209 [67208.028560] [tdb] Close table 'cache0.tdb' Apr 26 10:44:17 192.168.122.209 [67208.259093] [tdb] Close table 'filter0.tdb' Apr 26 10:44:17 192.168.122.209 [67208.259583] [tempesta fw] modules are stopped Apr 26 10:44:17 192.168.122.209 [67208.477457] [tempesta fw] exiting... Apr 26 10:44:17 192.168.122.209 [67208.609830] [tdb] Shutdown Tempesta DB Apr 26 10:44:18 192.168.122.209 [67208.809322] End test: t_reconf.test_reconf_base.TestListenReconfH2AndHttps.test_reconf_proto_h2_https Apr 26 10:44:18 192.168.122.209 [67208.841760] Start test: t_reconf.test_reconf_base.TestListenReconfH2AndHttps.test_reconf_proto_http Apr 26 10:44:19 192.168.122.209 [67210.162262] [tdb] Start Tempesta DB Apr 26 10:44:19 192.168.122.209 [67210.302640] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:44:20 192.168.122.209 [67211.590081] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67211.590081] Maybe that's fine, but it's worth checking the [67211.590081] config - if there is no relations between the [67211.590081] names, then host name confusion attack is possible. Apr 26 10:44:21 192.168.122.209 [67211.700913] [tempesta fw] Configuration processing is completed. Apr 26 10:44:21 192.168.122.209 [67211.752584] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:44:21 192.168.122.209 [67212.160440] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:44:21 192.168.122.209 [67212.187010] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:44:21 192.168.122.209 [67212.213971] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:44:21 192.168.122.209 [67212.256863] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:44:21 192.168.122.209 [67212.304808] [tempesta fw] Tempesta FW is ready Apr 26 10:44:22 192.168.122.209 [67212.789777] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:44:22 192.168.122.209 [67212.826557] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67212.826557] Maybe that's fine, but it's worth checking the [67212.826557] config - if there is no relations between the [67212.826557] names, then host name confusion attack is possible. Apr 26 10:44:22 192.168.122.209 [67212.952919] [tempesta fw] Configuration processing is completed. Apr 26 10:44:22 192.168.122.209 [67213.185037] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:44:22 192.168.122.209 [67213.249250] [tempesta fw] Tempesta FW is ready Apr 26 10:44:23 192.168.122.209 [67213.806397] [tdb] Close table 'client0.tdb' Apr 26 10:44:23 192.168.122.209 [67214.000990] [tdb] Close table 'sessions0.tdb' Apr 26 10:44:26 192.168.122.209 [67217.287541] [tdb] Close table 'cache0.tdb' Apr 26 10:44:26 192.168.122.209 [67217.533216] [tdb] Close table 'filter0.tdb' Apr 26 10:44:26 192.168.122.209 [67217.533641] [tempesta fw] modules are stopped Apr 26 10:44:27 192.168.122.209 [67217.760537] [tempesta fw] exiting... Apr 26 10:44:27 192.168.122.209 [67217.893319] [tdb] Shutdown Tempesta DB Apr 26 10:44:27 192.168.122.209 [67218.114808] End test: t_reconf.test_reconf_base.TestListenReconfH2AndHttps.test_reconf_proto_http Apr 26 10:44:27 192.168.122.209 [67218.125903] Start test: t_reconf.test_reconf_base.TestListenReconfH2AndHttps.test_reconf_proto_https Apr 26 10:44:28 192.168.122.209 [67219.446972] [tdb] Start Tempesta DB Apr 26 10:44:28 192.168.122.209 [67219.610553] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:44:30 192.168.122.209 [67220.922338] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67220.922338] Maybe that's fine, but it's worth checking the [67220.922338] config - if there is no relations between the [67220.922338] names, then host name confusion attack is possible. Apr 26 10:44:30 192.168.122.209 [67221.037087] [tempesta fw] Configuration processing is completed. Apr 26 10:44:30 192.168.122.209 [67221.105672] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:44:31 192.168.122.209 [67221.666969] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:44:31 192.168.122.209 [67221.703517] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:44:31 192.168.122.209 [67221.729362] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:44:31 192.168.122.209 [67221.772982] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:44:31 192.168.122.209 [67221.824909] [tempesta fw] Tempesta FW is ready Apr 26 10:44:31 192.168.122.209 [67222.370694] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:44:31 192.168.122.209 [67222.409957] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67222.409957] Maybe that's fine, but it's worth checking the [67222.409957] config - if there is no relations between the [67222.409957] names, then host name confusion attack is possible. Apr 26 10:44:31 192.168.122.209 [67222.544993] [tempesta fw] Configuration processing is completed. Apr 26 10:44:32 192.168.122.209 [67222.777755] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:44:32 192.168.122.209 [67222.833342] [tempesta fw] Tempesta FW is ready Apr 26 10:44:32 192.168.122.209 [67223.362348] [tdb] Close table 'client0.tdb' Apr 26 10:44:32 192.168.122.209 [67223.545342] [tdb] Close table 'sessions0.tdb' Apr 26 10:44:36 192.168.122.209 [67226.697873] [tdb] Close table 'cache0.tdb' Apr 26 10:44:36 192.168.122.209 [67226.958449] [tdb] Close table 'filter0.tdb' Apr 26 10:44:36 192.168.122.209 [67226.958876] [tempesta fw] modules are stopped Apr 26 10:44:36 192.168.122.209 [67227.154565] [tempesta fw] exiting... Apr 26 10:44:36 192.168.122.209 [67227.329411] [tdb] Shutdown Tempesta DB Apr 26 10:44:36 192.168.122.209 [67227.573707] End test: t_reconf.test_reconf_base.TestListenReconfH2AndHttps.test_reconf_proto_https Apr 26 10:44:36 192.168.122.209 [67227.583889] Start test: t_reconf.test_reconf_base.TestListenReconfH2AndHttps.test_reconf_remove_listen Apr 26 10:44:38 192.168.122.209 [67228.696831] [tdb] Start Tempesta DB Apr 26 10:44:38 192.168.122.209 [67228.856723] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:44:39 192.168.122.209 [67230.254411] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67230.254411] Maybe that's fine, but it's worth checking the [67230.254411] config - if there is no relations between the [67230.254411] names, then host name confusion attack is possible. Apr 26 10:44:39 192.168.122.209 [67230.357222] [tempesta fw] Configuration processing is completed. Apr 26 10:44:39 192.168.122.209 [67230.427473] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:44:40 192.168.122.209 [67230.993202] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:44:40 192.168.122.209 [67231.030475] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:44:40 192.168.122.209 [67231.056563] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:44:40 192.168.122.209 [67231.097105] [tempesta fw] Open listen socket on: 0.0.0.0:444 Apr 26 10:44:40 192.168.122.209 [67231.098818] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:44:40 192.168.122.209 [67231.149083] [tempesta fw] Tempesta FW is ready Apr 26 10:44:41 192.168.122.209 [67231.712808] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:44:41 192.168.122.209 [67231.754382] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67231.754382] Maybe that's fine, but it's worth checking the [67231.754382] config - if there is no relations between the [67231.754382] names, then host name confusion attack is possible. Apr 26 10:44:41 192.168.122.209 [67231.861036] [tempesta fw] Configuration processing is completed. Apr 26 10:44:41 192.168.122.209 [67232.149452] [tempesta fw] Tempesta FW is ready Apr 26 10:44:42 192.168.122.209 [67232.731542] [tdb] Close table 'client0.tdb' Apr 26 10:44:42 192.168.122.209 [67232.928512] [tdb] Close table 'sessions0.tdb' Apr 26 10:44:45 192.168.122.209 [67236.052238] [tdb] Close table 'cache0.tdb' Apr 26 10:44:45 192.168.122.209 [67236.294875] [tdb] Close table 'filter0.tdb' Apr 26 10:44:45 192.168.122.209 [67236.295299] [tempesta fw] modules are stopped Apr 26 10:44:45 192.168.122.209 [67236.511048] [tempesta fw] exiting... Apr 26 10:44:45 192.168.122.209 [67236.636731] [tdb] Shutdown Tempesta DB Apr 26 10:44:46 192.168.122.209 [67236.871819] End test: t_reconf.test_reconf_base.TestListenReconfH2AndHttps.test_reconf_remove_listen Apr 26 10:44:46 192.168.122.209 [67236.887692] Start test: t_reconf.test_reconf_base.TestListenReconfHttp.test_reconf_add_listen Apr 26 10:44:47 192.168.122.209 [67238.189359] [tdb] Start Tempesta DB Apr 26 10:44:47 192.168.122.209 [67238.343697] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:44:48 192.168.122.209 [67239.622675] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67239.622675] Maybe that's fine, but it's worth checking the [67239.622675] config - if there is no relations between the [67239.622675] names, then host name confusion attack is possible. Apr 26 10:44:49 192.168.122.209 [67239.710660] [tempesta fw] Warning: TLS: no HTTPS listener set, configuration is ignored. Apr 26 10:44:49 192.168.122.209 [67239.733328] [tempesta fw] Configuration processing is completed. Apr 26 10:44:49 192.168.122.209 [67239.792352] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:44:49 192.168.122.209 [67240.217925] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:44:49 192.168.122.209 [67240.244058] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:44:49 192.168.122.209 [67240.270102] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:44:49 192.168.122.209 [67240.321133] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:44:49 192.168.122.209 [67240.361148] [tempesta fw] Tempesta FW is ready Apr 26 10:44:50 192.168.122.209 [67240.900490] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:44:50 192.168.122.209 [67240.958456] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67240.958456] Maybe that's fine, but it's worth checking the [67240.958456] config - if there is no relations between the [67240.958456] names, then host name confusion attack is possible. Apr 26 10:44:50 192.168.122.209 [67241.053963] [tempesta fw] Warning: TLS: no HTTPS listener set, configuration is ignored. Apr 26 10:44:50 192.168.122.209 [67241.073272] [tempesta fw] Configuration processing is completed. Apr 26 10:44:50 192.168.122.209 [67241.286715] [tempesta fw] Open listen socket on: 0.0.0.0:444 Apr 26 10:44:50 192.168.122.209 [67241.337606] [tempesta fw] Tempesta FW is ready Apr 26 10:44:51 192.168.122.209 [67241.838208] [tdb] Close table 'client0.tdb' Apr 26 10:44:51 192.168.122.209 [67242.027769] [tdb] Close table 'sessions0.tdb' Apr 26 10:44:54 192.168.122.209 [67245.148506] [tdb] Close table 'cache0.tdb' Apr 26 10:44:54 192.168.122.209 [67245.415934] [tdb] Close table 'filter0.tdb' Apr 26 10:44:54 192.168.122.209 [67245.416371] [tempesta fw] modules are stopped Apr 26 10:44:54 192.168.122.209 [67245.593647] [tempesta fw] exiting... Apr 26 10:44:55 192.168.122.209 [67245.726403] [tdb] Shutdown Tempesta DB Apr 26 10:44:55 192.168.122.209 [67245.935361] End test: t_reconf.test_reconf_base.TestListenReconfHttp.test_reconf_add_listen Apr 26 10:44:55 192.168.122.209 [67245.945683] Start test: t_reconf.test_reconf_base.TestListenReconfHttp.test_reconf_ip_default_to_ipv4_port_default Apr 26 10:44:56 192.168.122.209 [67247.272508] [tdb] Start Tempesta DB Apr 26 10:44:56 192.168.122.209 [67247.423618] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:44:58 192.168.122.209 [67248.742993] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67248.742993] Maybe that's fine, but it's worth checking the [67248.742993] config - if there is no relations between the [67248.742993] names, then host name confusion attack is possible. Apr 26 10:44:58 192.168.122.209 [67248.825564] [tempesta fw] Warning: TLS: no HTTPS listener set, configuration is ignored. Apr 26 10:44:58 192.168.122.209 [67248.845313] [tempesta fw] Configuration processing is completed. Apr 26 10:44:58 192.168.122.209 [67248.902453] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:44:58 192.168.122.209 [67249.310710] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:44:58 192.168.122.209 [67249.336003] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:44:58 192.168.122.209 [67249.361385] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:44:58 192.168.122.209 [67249.405332] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:44:58 192.168.122.209 [67249.449250] [tempesta fw] Tempesta FW is ready Apr 26 10:44:59 192.168.122.209 [67249.945365] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:44:59 192.168.122.209 [67250.006555] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67250.006555] Maybe that's fine, but it's worth checking the [67250.006555] config - if there is no relations between the [67250.006555] names, then host name confusion attack is possible. Apr 26 10:44:59 192.168.122.209 [67250.123337] [tempesta fw] Warning: TLS: no HTTPS listener set, configuration is ignored. Apr 26 10:44:59 192.168.122.209 [67250.149285] [tempesta fw] Configuration processing is completed. Apr 26 10:44:59 192.168.122.209 [67250.369471] [tempesta fw] Open listen socket on: 127.0.0.1 Apr 26 10:44:59 192.168.122.209 [67250.433682] [tempesta fw] Tempesta FW is ready Apr 26 10:45:00 192.168.122.209 [67250.923598] [tdb] Close table 'client0.tdb' Apr 26 10:45:00 192.168.122.209 [67251.105042] [tdb] Close table 'sessions0.tdb' Apr 26 10:45:03 192.168.122.209 [67254.216286] [tdb] Close table 'cache0.tdb' Apr 26 10:45:03 192.168.122.209 [67254.479338] [tdb] Close table 'filter0.tdb' Apr 26 10:45:03 192.168.122.209 [67254.479774] [tempesta fw] modules are stopped Apr 26 10:45:04 192.168.122.209 [67254.682347] [tempesta fw] exiting... Apr 26 10:45:04 192.168.122.209 [67254.794580] [tdb] Shutdown Tempesta DB Apr 26 10:45:04 192.168.122.209 [67254.999553] End test: t_reconf.test_reconf_base.TestListenReconfHttp.test_reconf_ip_default_to_ipv4_port_default Apr 26 10:45:04 192.168.122.209 [67255.010826] Start test: t_reconf.test_reconf_base.TestListenReconfHttp.test_reconf_ip_ipv4_to_ipv4_port_443 Apr 26 10:45:05 192.168.122.209 [67256.210985] [tdb] Start Tempesta DB Apr 26 10:45:05 192.168.122.209 [67256.372723] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:45:07 192.168.122.209 [67257.690626] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67257.690626] Maybe that's fine, but it's worth checking the [67257.690626] config - if there is no relations between the [67257.690626] names, then host name confusion attack is possible. Apr 26 10:45:07 192.168.122.209 [67257.771086] [tempesta fw] Warning: TLS: no HTTPS listener set, configuration is ignored. Apr 26 10:45:07 192.168.122.209 [67257.789535] [tempesta fw] Configuration processing is completed. Apr 26 10:45:07 192.168.122.209 [67257.848264] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:45:07 192.168.122.209 [67258.263780] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:45:07 192.168.122.209 [67258.289738] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:45:07 192.168.122.209 [67258.315537] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:45:07 192.168.122.209 [67258.373431] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 10:45:07 192.168.122.209 [67258.413286] [tempesta fw] Tempesta FW is ready Apr 26 10:45:08 192.168.122.209 [67258.867482] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:45:08 192.168.122.209 [67258.918640] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67258.918640] Maybe that's fine, but it's worth checking the [67258.918640] config - if there is no relations between the [67258.918640] names, then host name confusion attack is possible. Apr 26 10:45:08 192.168.122.209 [67259.022159] [tempesta fw] Warning: TLS: no HTTPS listener set, configuration is ignored. Apr 26 10:45:08 192.168.122.209 [67259.049486] [tempesta fw] Configuration processing is completed. Apr 26 10:45:08 192.168.122.209 [67259.297643] [tempesta fw] Open listen socket on: 127.0.1.100:443 Apr 26 10:45:08 192.168.122.209 [67259.353777] [tempesta fw] Tempesta FW is ready Apr 26 10:45:09 192.168.122.209 [67259.863556] [tdb] Close table 'client0.tdb' Apr 26 10:45:09 192.168.122.209 [67260.055759] [tdb] Close table 'sessions0.tdb' Apr 26 10:45:12 192.168.122.209 [67263.125932] [tdb] Close table 'cache0.tdb' Apr 26 10:45:12 192.168.122.209 [67263.369411] [tdb] Close table 'filter0.tdb' Apr 26 10:45:12 192.168.122.209 [67263.369850] [tempesta fw] modules are stopped Apr 26 10:45:13 192.168.122.209 [67263.665894] [tempesta fw] exiting... Apr 26 10:45:13 192.168.122.209 [67263.833438] [tdb] Shutdown Tempesta DB Apr 26 10:45:13 192.168.122.209 [67264.119988] End test: t_reconf.test_reconf_base.TestListenReconfHttp.test_reconf_ip_ipv4_to_ipv4_port_443 Apr 26 10:45:13 192.168.122.209 [67264.135347] Start test: t_reconf.test_reconf_base.TestListenReconfHttp.test_reconf_ip_ipv4_to_ipv4_port_default Apr 26 10:45:14 192.168.122.209 [67265.346915] [tdb] Start Tempesta DB Apr 26 10:45:14 192.168.122.209 [67265.483911] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:45:16 192.168.122.209 [67266.830464] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67266.830464] Maybe that's fine, but it's worth checking the [67266.830464] config - if there is no relations between the [67266.830464] names, then host name confusion attack is possible. Apr 26 10:45:16 192.168.122.209 [67266.914904] [tempesta fw] Warning: TLS: no HTTPS listener set, configuration is ignored. Apr 26 10:45:16 192.168.122.209 [67266.941672] [tempesta fw] Configuration processing is completed. Apr 26 10:45:16 192.168.122.209 [67267.002094] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:45:16 192.168.122.209 [67267.415550] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:45:16 192.168.122.209 [67267.440968] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:45:16 192.168.122.209 [67267.466107] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:45:16 192.168.122.209 [67267.509542] [tempesta fw] Open listen socket on: 127.0.0.1 Apr 26 10:45:16 192.168.122.209 [67267.553494] [tempesta fw] Tempesta FW is ready Apr 26 10:45:17 192.168.122.209 [67268.001156] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:45:17 192.168.122.209 [67268.054728] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67268.054728] Maybe that's fine, but it's worth checking the [67268.054728] config - if there is no relations between the [67268.054728] names, then host name confusion attack is possible. Apr 26 10:45:17 192.168.122.209 [67268.166146] [tempesta fw] Warning: TLS: no HTTPS listener set, configuration is ignored. Apr 26 10:45:17 192.168.122.209 [67268.205599] [tempesta fw] Configuration processing is completed. Apr 26 10:45:17 192.168.122.209 [67268.401681] [tempesta fw] Open listen socket on: 127.0.1.100 Apr 26 10:45:17 192.168.122.209 [67268.457889] [tempesta fw] Tempesta FW is ready Apr 26 10:45:18 192.168.122.209 [67268.997926] [tdb] Close table 'client0.tdb' Apr 26 10:45:18 192.168.122.209 [67269.191541] [tdb] Close table 'sessions0.tdb' Apr 26 10:45:21 192.168.122.209 [67272.591766] [tdb] Close table 'cache0.tdb' Apr 26 10:45:22 192.168.122.209 [67272.857586] [tdb] Close table 'filter0.tdb' Apr 26 10:45:22 192.168.122.209 [67272.858024] [tempesta fw] modules are stopped Apr 26 10:45:22 192.168.122.209 [67273.107913] [tempesta fw] exiting... Apr 26 10:45:22 192.168.122.209 [67273.251690] [tdb] Shutdown Tempesta DB Apr 26 10:45:22 192.168.122.209 [67273.490241] End test: t_reconf.test_reconf_base.TestListenReconfHttp.test_reconf_ip_ipv4_to_ipv4_port_default Apr 26 10:45:22 192.168.122.209 [67273.515670] Start test: t_reconf.test_reconf_base.TestListenReconfHttp.test_reconf_port Apr 26 10:45:24 192.168.122.209 [67274.698117] [tdb] Start Tempesta DB Apr 26 10:45:24 192.168.122.209 [67274.843187] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:45:25 192.168.122.209 [67276.210875] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67276.210875] Maybe that's fine, but it's worth checking the [67276.210875] config - if there is no relations between the [67276.210875] names, then host name confusion attack is possible. Apr 26 10:45:25 192.168.122.209 [67276.291269] [tempesta fw] Warning: TLS: no HTTPS listener set, configuration is ignored. Apr 26 10:45:25 192.168.122.209 [67276.317836] [tempesta fw] Configuration processing is completed. Apr 26 10:45:25 192.168.122.209 [67276.381752] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:45:26 192.168.122.209 [67276.948992] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:45:26 192.168.122.209 [67276.984334] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:45:26 192.168.122.209 [67277.018952] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:45:26 192.168.122.209 [67277.069628] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:45:26 192.168.122.209 [67277.113529] [tempesta fw] Tempesta FW is ready Apr 26 10:45:26 192.168.122.209 [67277.591120] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:45:27 192.168.122.209 [67277.650899] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67277.650899] Maybe that's fine, but it's worth checking the [67277.650899] config - if there is no relations between the [67277.650899] names, then host name confusion attack is possible. Apr 26 10:45:27 192.168.122.209 [67277.746091] [tempesta fw] Warning: TLS: no HTTPS listener set, configuration is ignored. Apr 26 10:45:27 192.168.122.209 [67277.765695] [tempesta fw] Configuration processing is completed. Apr 26 10:45:27 192.168.122.209 [67277.953810] [tempesta fw] Open listen socket on: 0.0.0.0:4433 Apr 26 10:45:27 192.168.122.209 [67278.014017] [tempesta fw] Tempesta FW is ready Apr 26 10:45:27 192.168.122.209 [67278.510791] [tdb] Close table 'client0.tdb' Apr 26 10:45:28 192.168.122.209 [67278.702232] [tdb] Close table 'sessions0.tdb' Apr 26 10:45:31 192.168.122.209 [67281.831163] [tdb] Close table 'cache0.tdb' Apr 26 10:45:31 192.168.122.209 [67282.088451] [tdb] Close table 'filter0.tdb' Apr 26 10:45:31 192.168.122.209 [67282.088875] [tempesta fw] modules are stopped Apr 26 10:45:31 192.168.122.209 [67282.324946] [tempesta fw] exiting... Apr 26 10:45:31 192.168.122.209 [67282.474380] [tdb] Shutdown Tempesta DB Apr 26 10:45:32 192.168.122.209 [67282.680733] End test: t_reconf.test_reconf_base.TestListenReconfHttp.test_reconf_port Apr 26 10:45:32 192.168.122.209 [67282.692262] Start test: t_reconf.test_reconf_base.TestListenReconfHttp.test_reconf_proto_h2 Apr 26 10:45:33 192.168.122.209 [67283.736987] [tdb] Start Tempesta DB Apr 26 10:45:33 192.168.122.209 [67283.871663] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:45:34 192.168.122.209 [67285.215286] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67285.215286] Maybe that's fine, but it's worth checking the [67285.215286] config - if there is no relations between the [67285.215286] names, then host name confusion attack is possible. Apr 26 10:45:34 192.168.122.209 [67285.295265] [tempesta fw] Warning: TLS: no HTTPS listener set, configuration is ignored. Apr 26 10:45:34 192.168.122.209 [67285.321876] [tempesta fw] Configuration processing is completed. Apr 26 10:45:34 192.168.122.209 [67285.382573] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:45:35 192.168.122.209 [67285.863827] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:45:35 192.168.122.209 [67285.894427] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:45:35 192.168.122.209 [67285.926032] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:45:35 192.168.122.209 [67285.965692] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:45:35 192.168.122.209 [67286.009690] [tempesta fw] Tempesta FW is ready Apr 26 10:45:35 192.168.122.209 [67286.431039] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:45:35 192.168.122.209 [67286.470183] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67286.470183] Maybe that's fine, but it's worth checking the [67286.470183] config - if there is no relations between the [67286.470183] names, then host name confusion attack is possible. Apr 26 10:45:35 192.168.122.209 [67286.581841] [tempesta fw] Configuration processing is completed. Apr 26 10:45:36 192.168.122.209 [67286.797925] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:45:36 192.168.122.209 [67286.862117] [tempesta fw] Tempesta FW is ready Apr 26 10:45:36 192.168.122.209 [67287.354340] [tdb] Close table 'client0.tdb' Apr 26 10:45:36 192.168.122.209 [67287.532898] [tdb] Close table 'sessions0.tdb' Apr 26 10:45:40 192.168.122.209 [67290.752750] [tdb] Close table 'cache0.tdb' Apr 26 10:45:40 192.168.122.209 [67291.005222] [tdb] Close table 'filter0.tdb' Apr 26 10:45:40 192.168.122.209 [67291.005690] [tempesta fw] modules are stopped Apr 26 10:45:40 192.168.122.209 [67291.226514] [tempesta fw] exiting... Apr 26 10:45:40 192.168.122.209 [67291.363435] [tdb] Shutdown Tempesta DB Apr 26 10:45:40 192.168.122.209 [67291.600897] End test: t_reconf.test_reconf_base.TestListenReconfHttp.test_reconf_proto_h2 Apr 26 10:45:40 192.168.122.209 [67291.616974] Start test: t_reconf.test_reconf_base.TestListenReconfHttp.test_reconf_proto_h2_https Apr 26 10:45:42 192.168.122.209 [67292.684981] [tdb] Start Tempesta DB Apr 26 10:45:42 192.168.122.209 [67292.835252] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:45:43 192.168.122.209 [67294.083039] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67294.083039] Maybe that's fine, but it's worth checking the [67294.083039] config - if there is no relations between the [67294.083039] names, then host name confusion attack is possible. Apr 26 10:45:43 192.168.122.209 [67294.167216] [tempesta fw] Warning: TLS: no HTTPS listener set, configuration is ignored. Apr 26 10:45:43 192.168.122.209 [67294.193976] [tempesta fw] Configuration processing is completed. Apr 26 10:45:43 192.168.122.209 [67294.263082] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:45:44 192.168.122.209 [67294.699304] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:45:44 192.168.122.209 [67294.726687] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:45:44 192.168.122.209 [67294.754411] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:45:44 192.168.122.209 [67294.813887] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:45:44 192.168.122.209 [67294.857809] [tempesta fw] Tempesta FW is ready Apr 26 10:45:44 192.168.122.209 [67295.343045] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:45:44 192.168.122.209 [67295.390783] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67295.390783] Maybe that's fine, but it's worth checking the [67295.390783] config - if there is no relations between the [67295.390783] names, then host name confusion attack is possible. Apr 26 10:45:44 192.168.122.209 [67295.497974] [tempesta fw] Configuration processing is completed. Apr 26 10:45:45 192.168.122.209 [67295.710031] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:45:45 192.168.122.209 [67295.778269] [tempesta fw] Tempesta FW is ready Apr 26 10:45:45 192.168.122.209 [67296.291064] [tdb] Close table 'client0.tdb' Apr 26 10:45:45 192.168.122.209 [67296.477821] [tdb] Close table 'sessions0.tdb' Apr 26 10:45:49 192.168.122.209 [67299.659969] [tdb] Close table 'cache0.tdb' Apr 26 10:45:49 192.168.122.209 [67299.921605] [tdb] Close table 'filter0.tdb' Apr 26 10:45:49 192.168.122.209 [67299.922073] [tempesta fw] modules are stopped Apr 26 10:45:49 192.168.122.209 [67300.125185] [tempesta fw] exiting... Apr 26 10:45:49 192.168.122.209 [67300.258960] [tdb] Shutdown Tempesta DB Apr 26 10:45:49 192.168.122.209 [67300.491873] End test: t_reconf.test_reconf_base.TestListenReconfHttp.test_reconf_proto_h2_https Apr 26 10:45:49 192.168.122.209 [67300.505658] Start test: t_reconf.test_reconf_base.TestListenReconfHttp.test_reconf_proto_http Apr 26 10:45:50 192.168.122.209 [67301.600026] [tdb] Start Tempesta DB Apr 26 10:45:51 192.168.122.209 [67301.762900] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:45:52 192.168.122.209 [67303.087188] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67303.087188] Maybe that's fine, but it's worth checking the [67303.087188] config - if there is no relations between the [67303.087188] names, then host name confusion attack is possible. Apr 26 10:45:52 192.168.122.209 [67303.179476] [tempesta fw] Warning: TLS: no HTTPS listener set, configuration is ignored. Apr 26 10:45:52 192.168.122.209 [67303.198052] [tempesta fw] Configuration processing is completed. Apr 26 10:45:52 192.168.122.209 [67303.257077] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:45:53 192.168.122.209 [67303.724742] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:45:53 192.168.122.209 [67303.756510] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:45:53 192.168.122.209 [67303.788447] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:45:53 192.168.122.209 [67303.821999] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:45:53 192.168.122.209 [67303.869916] [tempesta fw] Tempesta FW is ready Apr 26 10:45:53 192.168.122.209 [67304.312123] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:45:53 192.168.122.209 [67304.346899] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67304.346899] Maybe that's fine, but it's worth checking the [67304.346899] config - if there is no relations between the [67304.346899] names, then host name confusion attack is possible. Apr 26 10:45:53 192.168.122.209 [67304.444674] [tempesta fw] Warning: TLS: no HTTPS listener set, configuration is ignored. Apr 26 10:45:53 192.168.122.209 [67304.458347] [tempesta fw] Configuration processing is completed. Apr 26 10:45:54 192.168.122.209 [67304.727580] [tempesta fw] Tempesta FW is ready Apr 26 10:45:54 192.168.122.209 [67305.245116] [tdb] Close table 'client0.tdb' Apr 26 10:45:54 192.168.122.209 [67305.412334] [tdb] Close table 'sessions0.tdb' Apr 26 10:45:57 192.168.122.209 [67308.599037] [tdb] Close table 'cache0.tdb' Apr 26 10:45:58 192.168.122.209 [67308.821674] [tdb] Close table 'filter0.tdb' Apr 26 10:45:58 192.168.122.209 [67308.822140] [tempesta fw] modules are stopped Apr 26 10:45:58 192.168.122.209 [67309.027221] [tempesta fw] exiting... Apr 26 10:45:58 192.168.122.209 [67309.141770] [tdb] Shutdown Tempesta DB Apr 26 10:45:58 192.168.122.209 [67309.346716] End test: t_reconf.test_reconf_base.TestListenReconfHttp.test_reconf_proto_http Apr 26 10:45:58 192.168.122.209 [67309.368468] Start test: t_reconf.test_reconf_base.TestListenReconfHttp.test_reconf_proto_https Apr 26 10:45:59 192.168.122.209 [67310.429811] [tdb] Start Tempesta DB Apr 26 10:45:59 192.168.122.209 [67310.571056] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:46:01 192.168.122.209 [67311.859152] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67311.859152] Maybe that's fine, but it's worth checking the [67311.859152] config - if there is no relations between the [67311.859152] names, then host name confusion attack is possible. Apr 26 10:46:01 192.168.122.209 [67311.955476] [tempesta fw] Warning: TLS: no HTTPS listener set, configuration is ignored. Apr 26 10:46:01 192.168.122.209 [67311.974111] [tempesta fw] Configuration processing is completed. Apr 26 10:46:01 192.168.122.209 [67312.030606] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:46:01 192.168.122.209 [67312.555612] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:46:01 192.168.122.209 [67312.588797] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:46:01 192.168.122.209 [67312.622314] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:46:02 192.168.122.209 [67312.666104] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:46:02 192.168.122.209 [67312.710022] [tempesta fw] Tempesta FW is ready Apr 26 10:46:02 192.168.122.209 [67313.140184] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:46:02 192.168.122.209 [67313.187476] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67313.187476] Maybe that's fine, but it's worth checking the [67313.187476] config - if there is no relations between the [67313.187476] names, then host name confusion attack is possible. Apr 26 10:46:02 192.168.122.209 [67313.326148] [tempesta fw] Configuration processing is completed. Apr 26 10:46:02 192.168.122.209 [67313.554285] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:46:02 192.168.122.209 [67313.610430] [tempesta fw] Tempesta FW is ready Apr 26 10:46:03 192.168.122.209 [67314.072852] [tdb] Close table 'client0.tdb' Apr 26 10:46:03 192.168.122.209 [67314.280850] [tdb] Close table 'sessions0.tdb' Apr 26 10:46:06 192.168.122.209 [67317.507204] [tdb] Close table 'cache0.tdb' Apr 26 10:46:07 192.168.122.209 [67317.768038] [tdb] Close table 'filter0.tdb' Apr 26 10:46:07 192.168.122.209 [67317.768442] [tempesta fw] modules are stopped Apr 26 10:46:07 192.168.122.209 [67317.994584] [tempesta fw] exiting... Apr 26 10:46:07 192.168.122.209 [67318.119645] [tdb] Shutdown Tempesta DB Apr 26 10:46:07 192.168.122.209 [67318.350516] End test: t_reconf.test_reconf_base.TestListenReconfHttp.test_reconf_proto_https Apr 26 10:46:07 192.168.122.209 [67318.364673] Start test: t_reconf.test_reconf_base.TestListenReconfHttp.test_reconf_remove_listen Apr 26 10:46:08 192.168.122.209 [67319.484267] [tdb] Start Tempesta DB Apr 26 10:46:08 192.168.122.209 [67319.629357] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:46:10 192.168.122.209 [67320.983447] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67320.983447] Maybe that's fine, but it's worth checking the [67320.983447] config - if there is no relations between the [67320.983447] names, then host name confusion attack is possible. Apr 26 10:46:10 192.168.122.209 [67321.070507] [tempesta fw] Warning: TLS: no HTTPS listener set, configuration is ignored. Apr 26 10:46:10 192.168.122.209 [67321.086345] [tempesta fw] Configuration processing is completed. Apr 26 10:46:10 192.168.122.209 [67321.160680] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:46:10 192.168.122.209 [67321.595939] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:46:10 192.168.122.209 [67321.622797] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:46:10 192.168.122.209 [67321.649540] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:46:11 192.168.122.209 [67321.698240] [tempesta fw] Open listen socket on: 0.0.0.0:444 Apr 26 10:46:11 192.168.122.209 [67321.700009] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:46:11 192.168.122.209 [67321.746137] [tempesta fw] Tempesta FW is ready Apr 26 10:46:11 192.168.122.209 [67322.213097] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:46:11 192.168.122.209 [67322.263318] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67322.263318] Maybe that's fine, but it's worth checking the [67322.263318] config - if there is no relations between the [67322.263318] names, then host name confusion attack is possible. Apr 26 10:46:11 192.168.122.209 [67322.358790] [tempesta fw] Warning: TLS: no HTTPS listener set, configuration is ignored. Apr 26 10:46:11 192.168.122.209 [67322.382174] [tempesta fw] Configuration processing is completed. Apr 26 10:46:12 192.168.122.209 [67322.670601] [tempesta fw] Tempesta FW is ready Apr 26 10:46:12 192.168.122.209 [67323.159666] [tdb] Close table 'client0.tdb' Apr 26 10:46:12 192.168.122.209 [67323.343142] [tdb] Close table 'sessions0.tdb' Apr 26 10:46:15 192.168.122.209 [67326.523544] [tdb] Close table 'cache0.tdb' Apr 26 10:46:16 192.168.122.209 [67326.743564] [tdb] Close table 'filter0.tdb' Apr 26 10:46:16 192.168.122.209 [67326.743986] [tempesta fw] modules are stopped Apr 26 10:46:16 192.168.122.209 [67327.013669] [tempesta fw] exiting... Apr 26 10:46:16 192.168.122.209 [67327.152184] [tdb] Shutdown Tempesta DB Apr 26 10:46:16 192.168.122.209 [67327.364078] End test: t_reconf.test_reconf_base.TestListenReconfHttp.test_reconf_remove_listen Apr 26 10:46:16 192.168.122.209 [67327.389185] Start test: t_reconf.test_reconf_base.TestListenReconfHttps.test_reconf_add_listen Apr 26 10:46:17 192.168.122.209 [67328.437558] [tdb] Start Tempesta DB Apr 26 10:46:17 192.168.122.209 [67328.581571] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:46:19 192.168.122.209 [67329.867623] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67329.867623] Maybe that's fine, but it's worth checking the [67329.867623] config - if there is no relations between the [67329.867623] names, then host name confusion attack is possible. Apr 26 10:46:19 192.168.122.209 [67329.966395] [tempesta fw] Configuration processing is completed. Apr 26 10:46:19 192.168.122.209 [67330.025890] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:46:19 192.168.122.209 [67330.452439] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:46:19 192.168.122.209 [67330.477979] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:46:19 192.168.122.209 [67330.503688] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:46:19 192.168.122.209 [67330.558290] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:46:19 192.168.122.209 [67330.606267] [tempesta fw] Tempesta FW is ready Apr 26 10:46:20 192.168.122.209 [67331.053669] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:46:20 192.168.122.209 [67331.127571] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67331.127571] Maybe that's fine, but it's worth checking the [67331.127571] config - if there is no relations between the [67331.127571] names, then host name confusion attack is possible. Apr 26 10:46:20 192.168.122.209 [67331.270373] [tempesta fw] Configuration processing is completed. Apr 26 10:46:20 192.168.122.209 [67331.486442] [tempesta fw] Open listen socket on: 0.0.0.0:444 Apr 26 10:46:20 192.168.122.209 [67331.550662] [tempesta fw] Tempesta FW is ready Apr 26 10:46:21 192.168.122.209 [67332.068101] [tdb] Close table 'client0.tdb' Apr 26 10:46:21 192.168.122.209 [67332.253401] [tdb] Close table 'sessions0.tdb' Apr 26 10:46:24 192.168.122.209 [67335.404111] [tdb] Close table 'cache0.tdb' Apr 26 10:46:24 192.168.122.209 [67335.621503] [tdb] Close table 'filter0.tdb' Apr 26 10:46:24 192.168.122.209 [67335.621920] [tempesta fw] modules are stopped Apr 26 10:46:25 192.168.122.209 [67335.838515] [tempesta fw] exiting... Apr 26 10:46:25 192.168.122.209 [67335.974528] [tdb] Shutdown Tempesta DB Apr 26 10:46:25 192.168.122.209 [67336.188567] End test: t_reconf.test_reconf_base.TestListenReconfHttps.test_reconf_add_listen Apr 26 10:46:25 192.168.122.209 [67336.197630] Start test: t_reconf.test_reconf_base.TestListenReconfHttps.test_reconf_ip_default_to_ipv4_port_default Apr 26 10:46:26 192.168.122.209 [67337.240806] [tdb] Start Tempesta DB Apr 26 10:46:26 192.168.122.209 [67337.387951] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:46:27 192.168.122.209 [67338.609243] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67338.609243] Maybe that's fine, but it's worth checking the [67338.609243] config - if there is no relations between the [67338.609243] names, then host name confusion attack is possible. Apr 26 10:46:28 192.168.122.209 [67338.704083] [tempesta fw] Warning: TLS: no HTTPS listener set, configuration is ignored. Apr 26 10:46:28 192.168.122.209 [67338.730553] [tempesta fw] Configuration processing is completed. Apr 26 10:46:28 192.168.122.209 [67338.792005] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:46:28 192.168.122.209 [67339.216267] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:46:28 192.168.122.209 [67339.241724] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:46:28 192.168.122.209 [67339.267282] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:46:28 192.168.122.209 [67339.326403] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:46:28 192.168.122.209 [67339.378355] [tempesta fw] Tempesta FW is ready Apr 26 10:46:29 192.168.122.209 [67339.814718] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:46:29 192.168.122.209 [67339.867692] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67339.867692] Maybe that's fine, but it's worth checking the [67339.867692] config - if there is no relations between the [67339.867692] names, then host name confusion attack is possible. Apr 26 10:46:29 192.168.122.209 [67340.002424] [tempesta fw] Configuration processing is completed. Apr 26 10:46:29 192.168.122.209 [67340.194607] [tempesta fw] Open listen socket on: 127.0.0.1 Apr 26 10:46:29 192.168.122.209 [67340.250790] [tempesta fw] Tempesta FW is ready Apr 26 10:46:30 192.168.122.209 [67340.749524] [tdb] Close table 'client0.tdb' Apr 26 10:46:30 192.168.122.209 [67340.938358] [tdb] Close table 'sessions0.tdb' Apr 26 10:46:33 192.168.122.209 [67344.152001] [tdb] Close table 'cache0.tdb' Apr 26 10:46:33 192.168.122.209 [67344.374016] [tdb] Close table 'filter0.tdb' Apr 26 10:46:33 192.168.122.209 [67344.374452] [tempesta fw] modules are stopped Apr 26 10:46:33 192.168.122.209 [67344.566936] [tempesta fw] exiting... Apr 26 10:46:34 192.168.122.209 [67344.682284] [tdb] Shutdown Tempesta DB Apr 26 10:46:34 192.168.122.209 [67344.897840] End test: t_reconf.test_reconf_base.TestListenReconfHttps.test_reconf_ip_default_to_ipv4_port_default Apr 26 10:46:34 192.168.122.209 [67344.913339] Start test: t_reconf.test_reconf_base.TestListenReconfHttps.test_reconf_ip_ipv4_to_ipv4_port_443 Apr 26 10:46:35 192.168.122.209 [67345.954727] [tdb] Start Tempesta DB Apr 26 10:46:35 192.168.122.209 [67346.084889] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:46:36 192.168.122.209 [67347.415805] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67347.415805] Maybe that's fine, but it's worth checking the [67347.415805] config - if there is no relations between the [67347.415805] names, then host name confusion attack is possible. Apr 26 10:46:36 192.168.122.209 [67347.522589] [tempesta fw] Configuration processing is completed. Apr 26 10:46:36 192.168.122.209 [67347.580309] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:46:37 192.168.122.209 [67347.996865] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:46:37 192.168.122.209 [67348.021891] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:46:37 192.168.122.209 [67348.046812] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:46:37 192.168.122.209 [67348.114514] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 10:46:37 192.168.122.209 [67348.154455] [tempesta fw] Tempesta FW is ready Apr 26 10:46:37 192.168.122.209 [67348.568492] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:46:37 192.168.122.209 [67348.623790] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67348.623790] Maybe that's fine, but it's worth checking the [67348.623790] config - if there is no relations between the [67348.623790] names, then host name confusion attack is possible. Apr 26 10:46:38 192.168.122.209 [67348.730582] [tempesta fw] Configuration processing is completed. Apr 26 10:46:38 192.168.122.209 [67348.942734] [tempesta fw] Open listen socket on: 127.0.1.100:443 Apr 26 10:46:38 192.168.122.209 [67349.006884] [tempesta fw] Tempesta FW is ready Apr 26 10:46:38 192.168.122.209 [67349.472907] [tdb] Close table 'client0.tdb' Apr 26 10:46:39 192.168.122.209 [67349.662134] [tdb] Close table 'sessions0.tdb' Apr 26 10:46:42 192.168.122.209 [67352.860626] [tdb] Close table 'cache0.tdb' Apr 26 10:46:42 192.168.122.209 [67353.113091] [tdb] Close table 'filter0.tdb' Apr 26 10:46:42 192.168.122.209 [67353.113512] [tempesta fw] modules are stopped Apr 26 10:46:42 192.168.122.209 [67353.316303] [tempesta fw] exiting... Apr 26 10:46:42 192.168.122.209 [67353.417203] [tdb] Shutdown Tempesta DB Apr 26 10:46:42 192.168.122.209 [67353.639200] End test: t_reconf.test_reconf_base.TestListenReconfHttps.test_reconf_ip_ipv4_to_ipv4_port_443 Apr 26 10:46:42 192.168.122.209 [67353.648848] Start test: t_reconf.test_reconf_base.TestListenReconfHttps.test_reconf_ip_ipv4_to_ipv4_port_default Apr 26 10:46:44 192.168.122.209 [67354.716712] [tdb] Start Tempesta DB Apr 26 10:46:44 192.168.122.209 [67354.849971] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:46:45 192.168.122.209 [67356.071870] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67356.071870] Maybe that's fine, but it's worth checking the [67356.071870] config - if there is no relations between the [67356.071870] names, then host name confusion attack is possible. Apr 26 10:46:45 192.168.122.209 [67356.187087] [tempesta fw] Configuration processing is completed. Apr 26 10:46:45 192.168.122.209 [67356.250647] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:46:46 192.168.122.209 [67356.662658] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:46:46 192.168.122.209 [67356.689446] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:46:46 192.168.122.209 [67356.714384] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:46:46 192.168.122.209 [67356.758627] [tempesta fw] Open listen socket on: 127.0.0.1 Apr 26 10:46:46 192.168.122.209 [67356.798557] [tempesta fw] Tempesta FW is ready Apr 26 10:46:46 192.168.122.209 [67357.233261] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:46:46 192.168.122.209 [67357.283407] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67357.283407] Maybe that's fine, but it's worth checking the [67357.283407] config - if there is no relations between the [67357.283407] names, then host name confusion attack is possible. Apr 26 10:46:46 192.168.122.209 [67357.414577] [tempesta fw] Configuration processing is completed. Apr 26 10:46:46 192.168.122.209 [67357.634795] [tempesta fw] Open listen socket on: 127.0.1.100 Apr 26 10:46:47 192.168.122.209 [67357.682997] [tempesta fw] Tempesta FW is ready Apr 26 10:46:47 192.168.122.209 [67358.192494] [tdb] Close table 'client0.tdb' Apr 26 10:46:47 192.168.122.209 [67358.376090] [tdb] Close table 'sessions0.tdb' Apr 26 10:46:50 192.168.122.209 [67361.581722] [tdb] Close table 'cache0.tdb' Apr 26 10:46:51 192.168.122.209 [67361.799791] [tdb] Close table 'filter0.tdb' Apr 26 10:46:51 192.168.122.209 [67361.800226] [tempesta fw] modules are stopped Apr 26 10:46:51 192.168.122.209 [67361.999456] [tempesta fw] exiting... Apr 26 10:46:51 192.168.122.209 [67362.105505] [tdb] Shutdown Tempesta DB Apr 26 10:46:51 192.168.122.209 [67362.340224] End test: t_reconf.test_reconf_base.TestListenReconfHttps.test_reconf_ip_ipv4_to_ipv4_port_default Apr 26 10:46:51 192.168.122.209 [67362.355608] Start test: t_reconf.test_reconf_base.TestListenReconfHttps.test_reconf_port Apr 26 10:46:52 192.168.122.209 [67363.381949] [tdb] Start Tempesta DB Apr 26 10:46:52 192.168.122.209 [67363.511032] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:46:54 192.168.122.209 [67364.840111] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67364.840111] Maybe that's fine, but it's worth checking the [67364.840111] config - if there is no relations between the [67364.840111] names, then host name confusion attack is possible. Apr 26 10:46:54 192.168.122.209 [67364.954834] [tempesta fw] Configuration processing is completed. Apr 26 10:46:54 192.168.122.209 [67365.013379] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:46:54 192.168.122.209 [67365.430584] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:46:54 192.168.122.209 [67365.456537] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:46:54 192.168.122.209 [67365.484006] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:46:54 192.168.122.209 [67365.530717] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:46:54 192.168.122.209 [67365.574748] [tempesta fw] Tempesta FW is ready Apr 26 10:46:55 192.168.122.209 [67366.057377] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:46:55 192.168.122.209 [67366.103859] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67366.103859] Maybe that's fine, but it's worth checking the [67366.103859] config - if there is no relations between the [67366.103859] names, then host name confusion attack is possible. Apr 26 10:46:55 192.168.122.209 [67366.226699] [tempesta fw] Configuration processing is completed. Apr 26 10:46:55 192.168.122.209 [67366.450993] [tempesta fw] Open listen socket on: 0.0.0.0:4433 Apr 26 10:46:55 192.168.122.209 [67366.507093] [tempesta fw] Tempesta FW is ready Apr 26 10:46:56 192.168.122.209 [67367.046479] [tdb] Close table 'client0.tdb' Apr 26 10:46:56 192.168.122.209 [67367.235700] [tdb] Close table 'sessions0.tdb' Apr 26 10:46:59 192.168.122.209 [67370.393428] [tdb] Close table 'cache0.tdb' Apr 26 10:46:59 192.168.122.209 [67370.638335] [tdb] Close table 'filter0.tdb' Apr 26 10:46:59 192.168.122.209 [67370.638770] [tempesta fw] modules are stopped Apr 26 10:47:00 192.168.122.209 [67370.836299] [tempesta fw] exiting... Apr 26 10:47:00 192.168.122.209 [67370.967086] [tdb] Shutdown Tempesta DB Apr 26 10:47:00 192.168.122.209 [67371.167704] End test: t_reconf.test_reconf_base.TestListenReconfHttps.test_reconf_port Apr 26 10:47:00 192.168.122.209 [67371.177574] Start test: t_reconf.test_reconf_base.TestListenReconfHttps.test_reconf_proto_h2 Apr 26 10:47:01 192.168.122.209 [67372.200989] [tdb] Start Tempesta DB Apr 26 10:47:01 192.168.122.209 [67372.334305] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:47:02 192.168.122.209 [67373.576130] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67373.576130] Maybe that's fine, but it's worth checking the [67373.576130] config - if there is no relations between the [67373.576130] names, then host name confusion attack is possible. Apr 26 10:47:03 192.168.122.209 [67373.686925] [tempesta fw] Configuration processing is completed. Apr 26 10:47:03 192.168.122.209 [67373.744234] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:47:03 192.168.122.209 [67374.173128] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:47:03 192.168.122.209 [67374.199911] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:47:03 192.168.122.209 [67374.226919] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:47:03 192.168.122.209 [67374.290831] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:47:03 192.168.122.209 [67374.330744] [tempesta fw] Tempesta FW is ready Apr 26 10:47:04 192.168.122.209 [67374.759305] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:47:04 192.168.122.209 [67374.800089] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67374.800089] Maybe that's fine, but it's worth checking the [67374.800089] config - if there is no relations between the [67374.800089] names, then host name confusion attack is possible. Apr 26 10:47:04 192.168.122.209 [67374.934971] [tempesta fw] Configuration processing is completed. Apr 26 10:47:04 192.168.122.209 [67375.159050] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:47:04 192.168.122.209 [67375.207205] [tempesta fw] Tempesta FW is ready Apr 26 10:47:05 192.168.122.209 [67375.753979] [tdb] Close table 'client0.tdb' Apr 26 10:47:05 192.168.122.209 [67375.938928] [tdb] Close table 'sessions0.tdb' Apr 26 10:47:08 192.168.122.209 [67379.149804] [tdb] Close table 'cache0.tdb' Apr 26 10:47:08 192.168.122.209 [67379.388235] [tdb] Close table 'filter0.tdb' Apr 26 10:47:08 192.168.122.209 [67379.388655] [tempesta fw] modules are stopped Apr 26 10:47:08 192.168.122.209 [67379.632147] [tempesta fw] exiting... Apr 26 10:47:09 192.168.122.209 [67379.766991] [tdb] Shutdown Tempesta DB Apr 26 10:47:09 192.168.122.209 [67379.954669] End test: t_reconf.test_reconf_base.TestListenReconfHttps.test_reconf_proto_h2 Apr 26 10:47:09 192.168.122.209 [67379.967762] Start test: t_reconf.test_reconf_base.TestListenReconfHttps.test_reconf_proto_h2_https Apr 26 10:47:10 192.168.122.209 [67381.001860] [tdb] Start Tempesta DB Apr 26 10:47:10 192.168.122.209 [67381.133785] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:47:11 192.168.122.209 [67382.412172] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67382.412172] Maybe that's fine, but it's worth checking the [67382.412172] config - if there is no relations between the [67382.412172] names, then host name confusion attack is possible. Apr 26 10:47:11 192.168.122.209 [67382.511332] [tempesta fw] Configuration processing is completed. Apr 26 10:47:11 192.168.122.209 [67382.564742] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:47:12 192.168.122.209 [67382.982675] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:47:12 192.168.122.209 [67383.022789] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:47:12 192.168.122.209 [67383.055551] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:47:12 192.168.122.209 [67383.102946] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:47:12 192.168.122.209 [67383.146884] [tempesta fw] Tempesta FW is ready Apr 26 10:47:12 192.168.122.209 [67383.610113] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:47:13 192.168.122.209 [67383.676189] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67383.676189] Maybe that's fine, but it's worth checking the [67383.676189] config - if there is no relations between the [67383.676189] names, then host name confusion attack is possible. Apr 26 10:47:13 192.168.122.209 [67383.795327] [tempesta fw] Configuration processing is completed. Apr 26 10:47:13 192.168.122.209 [67384.019120] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:47:13 192.168.122.209 [67384.087308] [tempesta fw] Tempesta FW is ready Apr 26 10:47:13 192.168.122.209 [67384.631887] [tdb] Close table 'client0.tdb' Apr 26 10:47:14 192.168.122.209 [67384.823443] [tdb] Close table 'sessions0.tdb' Apr 26 10:47:17 192.168.122.209 [67388.016157] [tdb] Close table 'cache0.tdb' Apr 26 10:47:17 192.168.122.209 [67388.263532] [tdb] Close table 'filter0.tdb' Apr 26 10:47:17 192.168.122.209 [67388.263954] [tempesta fw] modules are stopped Apr 26 10:47:17 192.168.122.209 [67388.456527] [tempesta fw] exiting... Apr 26 10:47:17 192.168.122.209 [67388.575634] [tdb] Shutdown Tempesta DB Apr 26 10:47:18 192.168.122.209 [67388.774831] End test: t_reconf.test_reconf_base.TestListenReconfHttps.test_reconf_proto_h2_https Apr 26 10:47:18 192.168.122.209 [67388.792683] Start test: t_reconf.test_reconf_base.TestListenReconfHttps.test_reconf_proto_http Apr 26 10:47:19 192.168.122.209 [67389.834992] [tdb] Start Tempesta DB Apr 26 10:47:19 192.168.122.209 [67389.968578] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:47:20 192.168.122.209 [67391.204373] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67391.204373] Maybe that's fine, but it's worth checking the [67391.204373] config - if there is no relations between the [67391.204373] names, then host name confusion attack is possible. Apr 26 10:47:20 192.168.122.209 [67391.319133] [tempesta fw] Configuration processing is completed. Apr 26 10:47:20 192.168.122.209 [67391.377830] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:47:21 192.168.122.209 [67391.796670] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:47:21 192.168.122.209 [67391.822419] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:47:21 192.168.122.209 [67391.847934] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:47:21 192.168.122.209 [67391.915041] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:47:21 192.168.122.209 [67391.962995] [tempesta fw] Tempesta FW is ready Apr 26 10:47:21 192.168.122.209 [67392.384628] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:47:21 192.168.122.209 [67392.440225] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67392.440225] Maybe that's fine, but it's worth checking the [67392.440225] config - if there is no relations between the [67392.440225] names, then host name confusion attack is possible. Apr 26 10:47:21 192.168.122.209 [67392.567016] [tempesta fw] Configuration processing is completed. Apr 26 10:47:22 192.168.122.209 [67392.795269] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:47:22 192.168.122.209 [67392.851333] [tempesta fw] Tempesta FW is ready Apr 26 10:47:22 192.168.122.209 [67393.314308] [tdb] Close table 'client0.tdb' Apr 26 10:47:22 192.168.122.209 [67393.484744] [tdb] Close table 'sessions0.tdb' Apr 26 10:47:26 192.168.122.209 [67396.681232] [tdb] Close table 'cache0.tdb' Apr 26 10:47:26 192.168.122.209 [67396.933913] [tdb] Close table 'filter0.tdb' Apr 26 10:47:26 192.168.122.209 [67396.934319] [tempesta fw] modules are stopped Apr 26 10:47:26 192.168.122.209 [67397.123262] [tempesta fw] exiting... Apr 26 10:47:26 192.168.122.209 [67397.260093] [tdb] Shutdown Tempesta DB Apr 26 10:47:26 192.168.122.209 [67397.436967] End test: t_reconf.test_reconf_base.TestListenReconfHttps.test_reconf_proto_http Apr 26 10:47:26 192.168.122.209 [67397.450057] Start test: t_reconf.test_reconf_base.TestListenReconfHttps.test_reconf_proto_https Apr 26 10:47:27 192.168.122.209 [67398.487696] [tdb] Start Tempesta DB Apr 26 10:47:27 192.168.122.209 [67398.610110] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:47:29 192.168.122.209 [67399.924347] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67399.924347] Maybe that's fine, but it's worth checking the [67399.924347] config - if there is no relations between the [67399.924347] names, then host name confusion attack is possible. Apr 26 10:47:29 192.168.122.209 [67400.019605] [tempesta fw] Configuration processing is completed. Apr 26 10:47:29 192.168.122.209 [67400.078238] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:47:29 192.168.122.209 [67400.512227] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:47:29 192.168.122.209 [67400.538870] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:47:29 192.168.122.209 [67400.564985] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:47:29 192.168.122.209 [67400.623158] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:47:30 192.168.122.209 [67400.663062] [tempesta fw] Tempesta FW is ready Apr 26 10:47:30 192.168.122.209 [67401.105164] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:47:30 192.168.122.209 [67401.160407] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67401.160407] Maybe that's fine, but it's worth checking the [67401.160407] config - if there is no relations between the [67401.160407] names, then host name confusion attack is possible. Apr 26 10:47:30 192.168.122.209 [67401.311232] [tempesta fw] Configuration processing is completed. Apr 26 10:47:30 192.168.122.209 [67401.571433] [tempesta fw] Tempesta FW is ready Apr 26 10:47:31 192.168.122.209 [67402.062105] [tdb] Close table 'client0.tdb' Apr 26 10:47:31 192.168.122.209 [67402.252638] [tdb] Close table 'sessions0.tdb' Apr 26 10:47:34 192.168.122.209 [67405.427576] [tdb] Close table 'cache0.tdb' Apr 26 10:47:35 192.168.122.209 [67405.657060] [tdb] Close table 'filter0.tdb' Apr 26 10:47:35 192.168.122.209 [67405.657488] [tempesta fw] modules are stopped Apr 26 10:47:35 192.168.122.209 [67405.859737] [tempesta fw] exiting... Apr 26 10:47:35 192.168.122.209 [67405.994128] [tdb] Shutdown Tempesta DB Apr 26 10:47:35 192.168.122.209 [67406.186436] End test: t_reconf.test_reconf_base.TestListenReconfHttps.test_reconf_proto_https Apr 26 10:47:35 192.168.122.209 [67406.203324] Start test: t_reconf.test_reconf_base.TestListenReconfHttps.test_reconf_remove_listen Apr 26 10:47:36 192.168.122.209 [67407.256172] [tdb] Start Tempesta DB Apr 26 10:47:36 192.168.122.209 [67407.392645] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:47:38 192.168.122.209 [67408.680184] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67408.680184] Maybe that's fine, but it's worth checking the [67408.680184] config - if there is no relations between the [67408.680184] names, then host name confusion attack is possible. Apr 26 10:47:38 192.168.122.209 [67408.787255] [tempesta fw] Configuration processing is completed. Apr 26 10:47:38 192.168.122.209 [67408.837088] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:47:38 192.168.122.209 [67409.241363] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:47:38 192.168.122.209 [67409.281539] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:47:38 192.168.122.209 [67409.307995] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:47:38 192.168.122.209 [67409.359268] [tempesta fw] Open listen socket on: 0.0.0.0:444 Apr 26 10:47:38 192.168.122.209 [67409.361020] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:47:38 192.168.122.209 [67409.403217] [tempesta fw] Tempesta FW is ready Apr 26 10:47:39 192.168.122.209 [67409.844328] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:47:39 192.168.122.209 [67409.896563] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67409.896563] Maybe that's fine, but it's worth checking the [67409.896563] config - if there is no relations between the [67409.896563] names, then host name confusion attack is possible. Apr 26 10:47:39 192.168.122.209 [67410.011386] [tempesta fw] Configuration processing is completed. Apr 26 10:47:39 192.168.122.209 [67410.284353] [tempesta fw] Tempesta FW is ready Apr 26 10:47:40 192.168.122.209 [67410.789233] [tdb] Close table 'client0.tdb' Apr 26 10:47:40 192.168.122.209 [67410.970031] [tdb] Close table 'sessions0.tdb' Apr 26 10:47:43 192.168.122.209 [67414.146851] [tdb] Close table 'cache0.tdb' Apr 26 10:47:43 192.168.122.209 [67414.398246] [tdb] Close table 'filter0.tdb' Apr 26 10:47:43 192.168.122.209 [67414.398675] [tempesta fw] modules are stopped Apr 26 10:47:43 192.168.122.209 [67414.593736] [tempesta fw] exiting... Apr 26 10:47:44 192.168.122.209 [67414.689299] [tdb] Shutdown Tempesta DB Apr 26 10:47:44 192.168.122.209 [67414.913502] End test: t_reconf.test_reconf_base.TestListenReconfHttps.test_reconf_remove_listen Apr 26 10:47:44 192.168.122.209 [67414.932324] Start test: t_reconf.test_reconf_base.TestLocationReconf.test_add_location Apr 26 10:47:45 192.168.122.209 [67415.946466] [tdb] Start Tempesta DB Apr 26 10:47:45 192.168.122.209 [67416.097564] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:47:46 192.168.122.209 [67417.513858] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67417.513858] Maybe that's fine, but it's worth checking the [67417.513858] config - if there is no relations between the [67417.513858] names, then host name confusion attack is possible. Apr 26 10:47:46 192.168.122.209 [67417.651397] [tempesta fw] Configuration processing is completed. Apr 26 10:47:47 192.168.122.209 [67417.702440] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:47:47 192.168.122.209 [67418.110606] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:47:47 192.168.122.209 [67418.135445] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:47:47 192.168.122.209 [67418.160135] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:47:47 192.168.122.209 [67418.203374] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:47:47 192.168.122.209 [67418.251310] [tempesta fw] Tempesta FW is ready Apr 26 10:47:48 192.168.122.209 [67418.815934] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:47:48 192.168.122.209 [67418.844145] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67418.844145] Maybe that's fine, but it's worth checking the [67418.844145] config - if there is no relations between the [67418.844145] names, then host name confusion attack is possible. Apr 26 10:47:48 192.168.122.209 [67419.011498] [tempesta fw] Configuration processing is completed. Apr 26 10:47:48 192.168.122.209 [67419.295817] [tempesta fw] Tempesta FW is ready Apr 26 10:47:49 192.168.122.209 [67419.898563] [tdb] Close table 'client0.tdb' Apr 26 10:47:49 192.168.122.209 [67420.082980] [tdb] Close table 'sessions0.tdb' Apr 26 10:47:52 192.168.122.209 [67423.253180] [tdb] Close table 'cache0.tdb' Apr 26 10:47:52 192.168.122.209 [67423.469035] [tdb] Close table 'filter0.tdb' Apr 26 10:47:52 192.168.122.209 [67423.469445] [tempesta fw] modules are stopped Apr 26 10:47:53 192.168.122.209 [67423.676490] [tempesta fw] exiting... Apr 26 10:47:53 192.168.122.209 [67423.784714] [tdb] Shutdown Tempesta DB Apr 26 10:47:53 192.168.122.209 [67423.975108] End test: t_reconf.test_reconf_base.TestLocationReconf.test_add_location Apr 26 10:47:53 192.168.122.209 [67423.990390] Start test: t_reconf.test_reconf_base.TestLocationReconf.test_remove_location Apr 26 10:47:54 192.168.122.209 [67425.011425] [tdb] Start Tempesta DB Apr 26 10:47:54 192.168.122.209 [67425.138374] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:47:55 192.168.122.209 [67426.632664] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67426.632664] Maybe that's fine, but it's worth checking the [67426.632664] config - if there is no relations between the [67426.632664] names, then host name confusion attack is possible. Apr 26 10:47:56 192.168.122.209 [67426.803560] [tempesta fw] Configuration processing is completed. Apr 26 10:47:56 192.168.122.209 [67426.856569] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:47:56 192.168.122.209 [67427.266641] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:47:56 192.168.122.209 [67427.292758] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:47:56 192.168.122.209 [67427.318684] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:47:56 192.168.122.209 [67427.383497] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:47:56 192.168.122.209 [67427.431680] [tempesta fw] Tempesta FW is ready Apr 26 10:47:57 192.168.122.209 [67428.043846] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:47:57 192.168.122.209 [67428.068098] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67428.068098] Maybe that's fine, but it's worth checking the [67428.068098] config - if there is no relations between the [67428.068098] names, then host name confusion attack is possible. Apr 26 10:47:57 192.168.122.209 [67428.227501] [tempesta fw] Configuration processing is completed. Apr 26 10:47:57 192.168.122.209 [67428.507949] [tempesta fw] Tempesta FW is ready Apr 26 10:47:58 192.168.122.209 [67429.094255] [tdb] Close table 'client0.tdb' Apr 26 10:47:58 192.168.122.209 [67429.278405] [tdb] Close table 'sessions0.tdb' Apr 26 10:48:01 192.168.122.209 [67432.441964] [tdb] Close table 'cache0.tdb' Apr 26 10:48:02 192.168.122.209 [67432.668289] [tdb] Close table 'filter0.tdb' Apr 26 10:48:02 192.168.122.209 [67432.668715] [tempesta fw] modules are stopped Apr 26 10:48:02 192.168.122.209 [67432.873250] [tempesta fw] exiting... Apr 26 10:48:02 192.168.122.209 [67432.974684] [tdb] Shutdown Tempesta DB Apr 26 10:48:02 192.168.122.209 [67433.193512] End test: t_reconf.test_reconf_base.TestLocationReconf.test_remove_location Apr 26 10:48:02 192.168.122.209 [67433.211451] Start test: t_reconf.test_reconf_base.TestNegativeReconf.test_negative_reconf_http_chain Apr 26 10:48:03 192.168.122.209 [67434.230723] [tdb] Start Tempesta DB Apr 26 10:48:03 192.168.122.209 [67434.361483] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:48:05 192.168.122.209 [67435.851594] [tempesta fw] Configuration processing is completed. Apr 26 10:48:05 192.168.122.209 [67435.903476] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:48:05 192.168.122.209 [67436.322331] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:48:05 192.168.122.209 [67436.348169] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:48:05 192.168.122.209 [67436.373394] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:48:05 192.168.122.209 [67436.515510] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:48:05 192.168.122.209 [67436.595564] [tempesta fw] Tempesta FW is ready Apr 26 10:48:06 192.168.122.209 [67437.250792] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:48:06 192.168.122.209 [67437.307933] [tempesta fw] ERROR: parser error Apr 26 10:48:06 192.168.122.209 [67437.308937] [tempesta fw] ERROR: configuration parsing error: [67437.308937] 12: cookie "__cookie" == "value_1"; [67437.308937] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 10:48:06 192.168.122.209 [67437.312503] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 10:48:07 192.168.122.209 [67438.325869] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:07 192.168.122.209 [67438.326669] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:07 192.168.122.209 [67438.326713] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:07 192.168.122.209 [67438.326835] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:07 192.168.122.209 [67438.327012] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:07 192.168.122.209 [67438.327179] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:07 192.168.122.209 [67438.327284] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:07 192.168.122.209 [67438.327389] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:07 192.168.122.209 [67438.327534] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:07 192.168.122.209 [67438.327632] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:07 192.168.122.209 [67438.327741] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:07 192.168.122.209 [67438.327837] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:07 192.168.122.209 [67438.328938] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:07 192.168.122.209 [67438.330011] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:07 192.168.122.209 [67438.330051] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:07 192.168.122.209 [67438.330177] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:07 192.168.122.209 [67438.330287] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:07 192.168.122.209 [67438.331553] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:07 192.168.122.209 [67438.333778] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:07 192.168.122.209 [67438.336189] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:07 192.168.122.209 [67438.338178] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:07 192.168.122.209 [67438.340714] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:07 192.168.122.209 [67438.341713] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:07 192.168.122.209 [67438.342742] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:07 192.168.122.209 [67438.343669] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:07 192.168.122.209 [67438.358729] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:07 192.168.122.209 [67438.359716] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:07 192.168.122.209 [67438.360690] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:07 192.168.122.209 [67438.361648] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:07 192.168.122.209 [67438.362592] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:07 192.168.122.209 [67438.363560] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:07 192.168.122.209 [67438.364832] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:12 192.168.122.209 [67442.691758] [tdb] Close table 'client0.tdb' Apr 26 10:48:12 192.168.122.209 [67442.878203] [tdb] Close table 'sessions0.tdb' Apr 26 10:48:15 192.168.122.209 [67446.026058] [tdb] Close table 'cache0.tdb' Apr 26 10:48:15 192.168.122.209 [67446.243106] [tdb] Close table 'filter0.tdb' Apr 26 10:48:15 192.168.122.209 [67446.243543] [tempesta fw] modules are stopped Apr 26 10:48:15 192.168.122.209 [67446.442759] [tempesta fw] exiting... Apr 26 10:48:15 192.168.122.209 [67446.583155] [tdb] Shutdown Tempesta DB Apr 26 10:48:16 192.168.122.209 [67446.780022] End test: t_reconf.test_reconf_base.TestNegativeReconf.test_negative_reconf_http_chain Apr 26 10:48:16 192.168.122.209 [67446.794738] Start test: t_reconf.test_reconf_base.TestNegativeReconf.test_negative_reconf_location Apr 26 10:48:17 192.168.122.209 [67447.892079] [tdb] Start Tempesta DB Apr 26 10:48:17 192.168.122.209 [67448.021284] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:48:18 192.168.122.209 [67449.243884] [tempesta fw] Configuration processing is completed. Apr 26 10:48:18 192.168.122.209 [67449.292954] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:48:19 192.168.122.209 [67449.703078] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:48:19 192.168.122.209 [67449.728620] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:48:19 192.168.122.209 [67449.754499] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:48:19 192.168.122.209 [67449.831777] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:48:19 192.168.122.209 [67449.875620] [tempesta fw] Tempesta FW is ready Apr 26 10:48:19 192.168.122.209 [67450.317517] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:48:19 192.168.122.209 [67450.352021] [tempesta fw] ERROR: location: Invalid number of arguments: 0, must be == 2 Apr 26 10:48:19 192.168.122.209 [67450.353059] [tempesta fw] ERROR: configuration parsing error: [67450.353059] 3: location { [67450.353059] ^^^^^^^^^^ Apr 26 10:48:19 192.168.122.209 [67450.354520] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 10:48:24 192.168.122.209 [67455.611076] [tdb] Close table 'client0.tdb' Apr 26 10:48:25 192.168.122.209 [67455.797156] [tdb] Close table 'sessions0.tdb' Apr 26 10:48:28 192.168.122.209 [67458.982860] [tdb] Close table 'cache0.tdb' Apr 26 10:48:28 192.168.122.209 [67459.236526] [tdb] Close table 'filter0.tdb' Apr 26 10:48:28 192.168.122.209 [67459.236952] [tempesta fw] modules are stopped Apr 26 10:48:28 192.168.122.209 [67459.418157] [tempesta fw] exiting... Apr 26 10:48:28 192.168.122.209 [67459.571905] [tdb] Shutdown Tempesta DB Apr 26 10:48:29 192.168.122.209 [67459.788978] End test: t_reconf.test_reconf_base.TestNegativeReconf.test_negative_reconf_location Apr 26 10:48:29 192.168.122.209 [67459.797478] Start test: t_reconf.test_reconf_base.TestNegativeReconf.test_negative_reconf_proxy_pass Apr 26 10:48:30 192.168.122.209 [67460.793600] [tdb] Start Tempesta DB Apr 26 10:48:30 192.168.122.209 [67461.037518] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:48:33 192.168.122.209 [67464.299993] [tempesta fw] Configuration processing is completed. Apr 26 10:48:34 192.168.122.209 [67464.656449] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:48:34 192.168.122.209 [67465.084112] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:48:34 192.168.122.209 [67465.110964] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:48:34 192.168.122.209 [67465.137327] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:48:35 192.168.122.209 [67465.848005] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:48:35 192.168.122.209 [67466.191835] [tempesta fw] Tempesta FW is ready Apr 26 10:48:36 192.168.122.209 [67466.697925] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:48:36 192.168.122.209 [67467.024629] [tempesta fw] ERROR: parser error Apr 26 10:48:36 192.168.122.209 [67467.025908] [tempesta fw] ERROR: configuration parsing error: [67467.025908] 7: proxy_pass grp1 backup=; [67467.025908] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 10:48:36 192.168.122.209 [67467.029944] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 10:48:36 192.168.122.209 [67467.061881] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.061916] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.062196] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.062375] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.062519] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.062664] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.062793] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.062922] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.063202] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.064946] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.065990] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.066031] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.067825] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.070506] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.071793] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.073075] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.074265] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.077239] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.078461] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.090294] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.093301] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.093307] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.093377] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.093560] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.093707] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.093845] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.093944] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.094312] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.097073] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.097556] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.105865] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.107260] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8001: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.348532] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.348590] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.351598] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.353492] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.353592] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.353684] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.354361] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.355713] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.357915] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.359207] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.361959] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.362172] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.362275] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.362333] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.362389] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.362447] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.364232] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.365564] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.366456] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.367819] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.368691] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.370020] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.370931] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.372277] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.373184] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.374394] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.375328] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.376266] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.377229] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.377250] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.386457] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 10:48:36 192.168.122.209 [67467.387414] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 10:48:41 192.168.122.209 [67472.394616] [tdb] Close table 'client0.tdb' Apr 26 10:48:41 192.168.122.209 [67472.579212] [tdb] Close table 'sessions0.tdb' Apr 26 10:48:45 192.168.122.209 [67475.731616] [tdb] Close table 'cache0.tdb' Apr 26 10:48:45 192.168.122.209 [67475.988268] [tdb] Close table 'filter0.tdb' Apr 26 10:48:45 192.168.122.209 [67475.988690] [tempesta fw] modules are stopped Apr 26 10:48:45 192.168.122.209 [67476.189350] [tempesta fw] exiting... Apr 26 10:48:45 192.168.122.209 [67476.301283] [tdb] Shutdown Tempesta DB Apr 26 10:48:45 192.168.122.209 [67476.518074] End test: t_reconf.test_reconf_base.TestNegativeReconf.test_negative_reconf_proxy_pass Apr 26 10:48:45 192.168.122.209 [67476.534028] Start test: t_reconf.test_reconf_base.TestNegativeReconf.test_negative_reconf_server Apr 26 10:48:46 192.168.122.209 [67477.495185] [tdb] Start Tempesta DB Apr 26 10:48:46 192.168.122.209 [67477.621749] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:48:48 192.168.122.209 [67478.756150] [tempesta fw] Configuration processing is completed. Apr 26 10:48:48 192.168.122.209 [67478.809473] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:48:48 192.168.122.209 [67479.228897] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:48:48 192.168.122.209 [67479.255481] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:48:48 192.168.122.209 [67479.281348] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:48:48 192.168.122.209 [67479.340134] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:48:48 192.168.122.209 [67479.388000] [tempesta fw] Tempesta FW is ready Apr 26 10:48:49 192.168.122.209 [67479.706336] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:48:49 192.168.122.209 [67479.709804] [tempesta fw] ERROR: Invalid IP address: '127.0.0.3:8000:443' Apr 26 10:48:49 192.168.122.209 [67479.710422] [tempesta fw] ERROR: configuration parsing error: [67479.710422] 1: server 127.0.0.3:8000:443; [67479.710422] ^^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 10:48:49 192.168.122.209 [67479.711678] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 10:48:54 192.168.122.209 [67484.867290] [tdb] Close table 'client0.tdb' Apr 26 10:48:54 192.168.122.209 [67485.059001] [tdb] Close table 'sessions0.tdb' Apr 26 10:48:57 192.168.122.209 [67488.211724] [tdb] Close table 'cache0.tdb' Apr 26 10:48:57 192.168.122.209 [67488.462962] [tdb] Close table 'filter0.tdb' Apr 26 10:48:57 192.168.122.209 [67488.463388] [tempesta fw] modules are stopped Apr 26 10:48:58 192.168.122.209 [67488.680952] [tempesta fw] exiting... Apr 26 10:48:58 192.168.122.209 [67488.783137] [tdb] Shutdown Tempesta DB Apr 26 10:48:58 192.168.122.209 [67488.987929] End test: t_reconf.test_reconf_base.TestNegativeReconf.test_negative_reconf_server Apr 26 10:48:58 192.168.122.209 [67489.010162] Start test: t_reconf.test_reconf_base.TestNegativeReconf.test_negative_reconf_srv_group Apr 26 10:48:59 192.168.122.209 [67489.946426] [tdb] Start Tempesta DB Apr 26 10:48:59 192.168.122.209 [67490.083722] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:49:00 192.168.122.209 [67491.200427] [tempesta fw] Configuration processing is completed. Apr 26 10:49:00 192.168.122.209 [67491.250681] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:49:01 192.168.122.209 [67491.663456] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:49:01 192.168.122.209 [67491.689716] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:49:01 192.168.122.209 [67491.715830] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:49:01 192.168.122.209 [67491.788294] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:49:01 192.168.122.209 [67491.828211] [tempesta fw] Tempesta FW is ready Apr 26 10:49:01 192.168.122.209 [67492.198606] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:49:01 192.168.122.209 [67492.200882] [tempesta fw] ERROR: srv_group: Invalid number of arguments: 2, must be == 1 Apr 26 10:49:01 192.168.122.209 [67492.201751] [tempesta fw] ERROR: configuration parsing error: [67492.201751] 1: srv_group default grp2 { [67492.201751] ^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 10:49:01 192.168.122.209 [67492.203241] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 10:49:06 192.168.122.209 [67497.357727] [tdb] Close table 'client0.tdb' Apr 26 10:49:06 192.168.122.209 [67497.557469] [tdb] Close table 'sessions0.tdb' Apr 26 10:49:10 192.168.122.209 [67500.726175] [tdb] Close table 'cache0.tdb' Apr 26 10:49:10 192.168.122.209 [67500.971275] [tdb] Close table 'filter0.tdb' Apr 26 10:49:10 192.168.122.209 [67500.971719] [tempesta fw] modules are stopped Apr 26 10:49:10 192.168.122.209 [67501.154690] [tempesta fw] exiting... Apr 26 10:49:10 192.168.122.209 [67501.270940] [tdb] Shutdown Tempesta DB Apr 26 10:49:10 192.168.122.209 [67501.476606] End test: t_reconf.test_reconf_base.TestNegativeReconf.test_negative_reconf_srv_group Apr 26 10:49:10 192.168.122.209 [67501.488880] Start test: t_reconf.test_reconf_base.TestNegativeReconf.test_negative_reconf_srv_group_options Apr 26 10:49:11 192.168.122.209 [67502.486023] [tdb] Start Tempesta DB Apr 26 10:49:11 192.168.122.209 [67502.630689] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:49:13 192.168.122.209 [67503.868854] [tempesta fw] Configuration processing is completed. Apr 26 10:49:13 192.168.122.209 [67503.920358] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:49:13 192.168.122.209 [67504.354070] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:49:13 192.168.122.209 [67504.380023] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:49:13 192.168.122.209 [67504.405789] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:49:13 192.168.122.209 [67504.476433] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:49:13 192.168.122.209 [67504.516387] [tempesta fw] Tempesta FW is ready Apr 26 10:49:14 192.168.122.209 [67504.902105] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:49:14 192.168.122.209 [67504.905778] [tempesta fw] ERROR: server_forward_retries: Invalid number of arguments: 2, must be == 1 Apr 26 10:49:14 192.168.122.209 [67504.907072] [tempesta fw] ERROR: configuration parsing error: [67504.907072] 4: server_forward_retries 1000 100; [67504.907072] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 10:49:14 192.168.122.209 [67504.908909] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 10:49:19 192.168.122.209 [67510.127266] [tdb] Close table 'client0.tdb' Apr 26 10:49:19 192.168.122.209 [67510.315576] [tdb] Close table 'sessions0.tdb' Apr 26 10:49:22 192.168.122.209 [67513.534419] [tdb] Close table 'cache0.tdb' Apr 26 10:49:23 192.168.122.209 [67513.803720] [tdb] Close table 'filter0.tdb' Apr 26 10:49:23 192.168.122.209 [67513.804123] [tempesta fw] modules are stopped Apr 26 10:49:23 192.168.122.209 [67513.961040] [tempesta fw] exiting... Apr 26 10:49:23 192.168.122.209 [67514.086283] [tdb] Shutdown Tempesta DB Apr 26 10:49:23 192.168.122.209 [67514.292157] End test: t_reconf.test_reconf_base.TestNegativeReconf.test_negative_reconf_srv_group_options Apr 26 10:49:23 192.168.122.209 [67514.305519] Start test: t_reconf.test_reconf_base.TestNegativeReconf.test_negative_reconf_vhost Apr 26 10:49:24 192.168.122.209 [67515.344739] [tdb] Start Tempesta DB Apr 26 10:49:24 192.168.122.209 [67515.469965] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:49:26 192.168.122.209 [67516.892555] [tempesta fw] Configuration processing is completed. Apr 26 10:49:26 192.168.122.209 [67516.950280] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:49:26 192.168.122.209 [67517.374266] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:49:26 192.168.122.209 [67517.400717] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:49:26 192.168.122.209 [67517.426887] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:49:26 192.168.122.209 [67517.496599] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:49:26 192.168.122.209 [67517.536553] [tempesta fw] Tempesta FW is ready Apr 26 10:49:27 192.168.122.209 [67518.137300] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:49:27 192.168.122.209 [67518.168762] [tempesta fw] ERROR: vhost: Invalid number of arguments: 2, must be == 1 Apr 26 10:49:27 192.168.122.209 [67518.170901] [tempesta fw] ERROR: configuration parsing error: [67518.170901] 6: vhost prefix "/" { [67518.170901] ^^^^^^^^^^^^^^^^^^ Apr 26 10:49:27 192.168.122.209 [67518.174478] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 10:49:32 192.168.122.209 [67523.424886] [tdb] Close table 'client0.tdb' Apr 26 10:49:32 192.168.122.209 [67523.606884] [tdb] Close table 'sessions0.tdb' Apr 26 10:49:36 192.168.122.209 [67526.727264] [tdb] Close table 'cache0.tdb' Apr 26 10:49:36 192.168.122.209 [67526.970757] [tdb] Close table 'filter0.tdb' Apr 26 10:49:36 192.168.122.209 [67526.971187] [tempesta fw] modules are stopped Apr 26 10:49:36 192.168.122.209 [67527.195465] [tempesta fw] exiting... Apr 26 10:49:36 192.168.122.209 [67527.308150] [tdb] Shutdown Tempesta DB Apr 26 10:49:36 192.168.122.209 [67527.519049] End test: t_reconf.test_reconf_base.TestNegativeReconf.test_negative_reconf_vhost Apr 26 10:49:36 192.168.122.209 [67527.534659] Start test: t_reconf.test_reconf_base.TestProxyPassReconf.test_reconf_backup_group Apr 26 10:49:37 192.168.122.209 [67528.646072] [tdb] Start Tempesta DB Apr 26 10:49:38 192.168.122.209 [67528.779913] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:49:39 192.168.122.209 [67530.510088] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67530.510088] Maybe that's fine, but it's worth checking the [67530.510088] config - if there is no relations between the [67530.510088] names, then host name confusion attack is possible. Apr 26 10:49:40 192.168.122.209 [67530.716800] [tempesta fw] Configuration processing is completed. Apr 26 10:49:40 192.168.122.209 [67530.771467] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:49:40 192.168.122.209 [67531.184368] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:49:40 192.168.122.209 [67531.210502] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:49:40 192.168.122.209 [67531.237141] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:49:40 192.168.122.209 [67531.344758] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:49:40 192.168.122.209 [67531.392735] [tempesta fw] Tempesta FW is ready Apr 26 10:49:41 192.168.122.209 [67532.102918] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:49:41 192.168.122.209 [67532.129505] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67532.129505] Maybe that's fine, but it's worth checking the [67532.129505] config - if there is no relations between the [67532.129505] names, then host name confusion attack is possible. Apr 26 10:49:41 192.168.122.209 [67532.400759] [tempesta fw] Configuration processing is completed. Apr 26 10:49:42 192.168.122.209 [67532.925264] [tempesta fw] Tempesta FW is ready Apr 26 10:49:43 192.168.122.209 [67534.548759] [tdb] Close table 'client0.tdb' Apr 26 10:49:44 192.168.122.209 [67534.739431] [tdb] Close table 'sessions0.tdb' Apr 26 10:49:47 192.168.122.209 [67537.927246] [tdb] Close table 'cache0.tdb' Apr 26 10:49:47 192.168.122.209 [67538.169662] [tdb] Close table 'filter0.tdb' Apr 26 10:49:47 192.168.122.209 [67538.170112] [tempesta fw] modules are stopped Apr 26 10:49:47 192.168.122.209 [67538.404906] [tempesta fw] exiting... Apr 26 10:49:47 192.168.122.209 [67538.553271] [tdb] Shutdown Tempesta DB Apr 26 10:49:48 192.168.122.209 [67538.764878] End test: t_reconf.test_reconf_base.TestProxyPassReconf.test_reconf_backup_group Apr 26 10:49:48 192.168.122.209 [67538.777256] Start test: t_reconf.test_reconf_base.TestProxyPassReconf.test_reconf_group Apr 26 10:49:49 192.168.122.209 [67539.785235] [tdb] Start Tempesta DB Apr 26 10:49:49 192.168.122.209 [67539.928702] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:49:50 192.168.122.209 [67541.518853] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67541.518853] Maybe that's fine, but it's worth checking the [67541.518853] config - if there is no relations between the [67541.518853] names, then host name confusion attack is possible. Apr 26 10:49:51 192.168.122.209 [67541.709366] [tempesta fw] Configuration processing is completed. Apr 26 10:49:51 192.168.122.209 [67541.766185] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:49:51 192.168.122.209 [67542.183410] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:49:51 192.168.122.209 [67542.208848] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:49:51 192.168.122.209 [67542.234061] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:49:51 192.168.122.209 [67542.304887] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:49:51 192.168.122.209 [67542.348831] [tempesta fw] Tempesta FW is ready Apr 26 10:49:52 192.168.122.209 [67543.046057] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:49:52 192.168.122.209 [67543.062344] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67543.062344] Maybe that's fine, but it's worth checking the [67543.062344] config - if there is no relations between the [67543.062344] names, then host name confusion attack is possible. Apr 26 10:49:52 192.168.122.209 [67543.300884] [tempesta fw] Configuration processing is completed. Apr 26 10:49:53 192.168.122.209 [67543.717352] [tempesta fw] Tempesta FW is ready Apr 26 10:49:53 192.168.122.209 [67543.853637] [tempesta fw] Warning: request has been filtered out via http table: 127.0.0.2 Apr 26 10:49:53 192.168.122.209 [67544.329416] [tdb] Close table 'client0.tdb' Apr 26 10:49:53 192.168.122.209 [67544.508610] [tdb] Close table 'sessions0.tdb' Apr 26 10:49:57 192.168.122.209 [67547.670786] [tdb] Close table 'cache0.tdb' Apr 26 10:49:57 192.168.122.209 [67547.911442] [tdb] Close table 'filter0.tdb' Apr 26 10:49:57 192.168.122.209 [67547.911864] [tempesta fw] modules are stopped Apr 26 10:49:57 192.168.122.209 [67548.146450] [tempesta fw] exiting... Apr 26 10:49:57 192.168.122.209 [67548.279900] [tdb] Shutdown Tempesta DB Apr 26 10:49:57 192.168.122.209 [67548.522864] End test: t_reconf.test_reconf_base.TestProxyPassReconf.test_reconf_group Apr 26 10:49:57 192.168.122.209 [67548.534262] Start test: t_reconf.test_reconf_base.TestServerOptionsReconf.test_reconf_health_disabled Apr 26 10:49:59 192.168.122.209 [67549.741568] [tdb] Start Tempesta DB Apr 26 10:49:59 192.168.122.209 [67549.864645] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:50:00 192.168.122.209 [67551.392183] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67551.392183] Maybe that's fine, but it's worth checking the [67551.392183] config - if there is no relations between the [67551.392183] names, then host name confusion attack is possible. Apr 26 10:50:00 192.168.122.209 [67551.521070] [tempesta fw] Configuration processing is completed. Apr 26 10:50:00 192.168.122.209 [67551.574220] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:50:01 192.168.122.209 [67552.023528] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:50:01 192.168.122.209 [67552.064006] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:50:01 192.168.122.209 [67552.092419] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:50:01 192.168.122.209 [67552.136997] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:50:01 192.168.122.209 [67552.184950] [tempesta fw] Tempesta FW is ready Apr 26 10:50:02 192.168.122.209 [67552.835535] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:50:02 192.168.122.209 [67552.861729] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67552.861729] Maybe that's fine, but it's worth checking the [67552.861729] config - if there is no relations between the [67552.861729] names, then host name confusion attack is possible. Apr 26 10:50:02 192.168.122.209 [67553.048973] [tempesta fw] Configuration processing is completed. Apr 26 10:50:02 192.168.122.209 [67553.317393] [tempesta fw] Tempesta FW is ready Apr 26 10:50:03 192.168.122.209 [67553.922869] [tdb] Close table 'client0.tdb' Apr 26 10:50:03 192.168.122.209 [67554.115905] [tdb] Close table 'sessions0.tdb' Apr 26 10:50:06 192.168.122.209 [67557.383070] [tdb] Close table 'cache0.tdb' Apr 26 10:50:06 192.168.122.209 [67557.627401] [tdb] Close table 'filter0.tdb' Apr 26 10:50:06 192.168.122.209 [67557.627835] [tempesta fw] modules are stopped Apr 26 10:50:07 192.168.122.209 [67557.842032] [tempesta fw] exiting... Apr 26 10:50:07 192.168.122.209 [67558.009305] [tdb] Shutdown Tempesta DB Apr 26 10:50:07 192.168.122.209 [67558.264477] End test: t_reconf.test_reconf_base.TestServerOptionsReconf.test_reconf_health_disabled Apr 26 10:50:07 192.168.122.209 [67558.276261] Start test: t_reconf.test_reconf_base.TestServerOptionsReconf.test_reconf_health_enabled Apr 26 10:50:08 192.168.122.209 [67559.618924] [tdb] Start Tempesta DB Apr 26 10:50:09 192.168.122.209 [67559.803507] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:50:10 192.168.122.209 [67561.488270] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67561.488270] Maybe that's fine, but it's worth checking the [67561.488270] config - if there is no relations between the [67561.488270] names, then host name confusion attack is possible. Apr 26 10:50:10 192.168.122.209 [67561.613215] [tempesta fw] Configuration processing is completed. Apr 26 10:50:11 192.168.122.209 [67561.670956] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:50:11 192.168.122.209 [67562.108325] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:50:11 192.168.122.209 [67562.137066] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:50:11 192.168.122.209 [67562.167502] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:50:11 192.168.122.209 [67562.225128] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:50:11 192.168.122.209 [67562.273100] [tempesta fw] Tempesta FW is ready Apr 26 10:50:12 192.168.122.209 [67563.020835] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:50:12 192.168.122.209 [67563.042894] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67563.042894] Maybe that's fine, but it's worth checking the [67563.042894] config - if there is no relations between the [67563.042894] names, then host name confusion attack is possible. Apr 26 10:50:12 192.168.122.209 [67563.213221] [tempesta fw] Configuration processing is completed. Apr 26 10:50:12 192.168.122.209 [67563.493559] [tempesta fw] Tempesta FW is ready Apr 26 10:50:12 192.168.122.209 [67563.612054] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '502' mismatched Apr 26 10:50:12 192.168.122.209 [67563.616024] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '502' mismatched Apr 26 10:50:12 192.168.122.209 [67563.617804] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '502' mismatched Apr 26 10:50:12 192.168.122.209 [67563.619029] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '502' mismatched Apr 26 10:50:12 192.168.122.209 [67563.619945] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '502' mismatched Apr 26 10:50:12 192.168.122.209 [67563.620786] [tempesta fw] Warning: Error limit exceeded for server: 127.0.0.3:8000 Apr 26 10:50:12 192.168.122.209 [67563.621489] [tempesta fw] Warning: server has been suspended: limit for bad responses is exceeded, status 502: 127.0.0.3:8000 Apr 26 10:50:12 192.168.122.209 [67563.622483] [tempesta fw] Warning: Response for health monitor 'h_monitor1': status '502' mismatched Apr 26 10:50:13 192.168.122.209 [67564.148944] [tdb] Close table 'client0.tdb' Apr 26 10:50:13 192.168.122.209 [67564.337066] [tdb] Close table 'sessions0.tdb' Apr 26 10:50:17 192.168.122.209 [67567.766873] [tdb] Close table 'cache0.tdb' Apr 26 10:50:17 192.168.122.209 [67568.024860] [tdb] Close table 'filter0.tdb' Apr 26 10:50:17 192.168.122.209 [67568.025364] [tempesta fw] modules are stopped Apr 26 10:50:17 192.168.122.209 [67568.223800] [tempesta fw] exiting... Apr 26 10:50:17 192.168.122.209 [67568.335744] [tdb] Shutdown Tempesta DB Apr 26 10:50:17 192.168.122.209 [67568.558181] End test: t_reconf.test_reconf_base.TestServerOptionsReconf.test_reconf_health_enabled Apr 26 10:50:17 192.168.122.209 [67568.576234] Start test: t_reconf.test_reconf_base.TestServerOptionsReconf.test_reconf_server_connect_retries_from_0 Apr 26 10:50:19 192.168.122.209 [67569.905443] [tdb] Start Tempesta DB Apr 26 10:50:19 192.168.122.209 [67570.097326] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:50:20 192.168.122.209 [67571.646293] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67571.646293] Maybe that's fine, but it's worth checking the [67571.646293] config - if there is no relations between the [67571.646293] names, then host name confusion attack is possible. Apr 26 10:50:21 192.168.122.209 [67571.745354] [tempesta fw] Configuration processing is completed. Apr 26 10:50:21 192.168.122.209 [67571.802326] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:50:21 192.168.122.209 [67572.420949] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:50:21 192.168.122.209 [67572.462482] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:50:21 192.168.122.209 [67572.494262] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:50:21 192.168.122.209 [67572.545285] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:50:21 192.168.122.209 [67572.585219] [tempesta fw] Tempesta FW is ready Apr 26 10:50:22 192.168.122.209 [67573.153128] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:50:22 192.168.122.209 [67573.170699] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67573.170699] Maybe that's fine, but it's worth checking the [67573.170699] config - if there is no relations between the [67573.170699] names, then host name confusion attack is possible. Apr 26 10:50:22 192.168.122.209 [67573.273252] [tempesta fw] Configuration processing is completed. Apr 26 10:50:22 192.168.122.209 [67573.445707] [tempesta fw] Tempesta FW is ready Apr 26 10:50:24 192.168.122.209 [67575.509447] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 10:50:34 192.168.122.209 [67585.240315] [tdb] Close table 'client0.tdb' Apr 26 10:50:34 192.168.122.209 [67585.447148] [tdb] Close table 'sessions0.tdb' Apr 26 10:50:38 192.168.122.209 [67588.893234] [tdb] Close table 'cache0.tdb' Apr 26 10:50:38 192.168.122.209 [67589.157628] [tdb] Close table 'filter0.tdb' Apr 26 10:50:38 192.168.122.209 [67589.158260] [tempesta fw] modules are stopped Apr 26 10:50:38 192.168.122.209 [67589.363606] [tempesta fw] exiting... Apr 26 10:50:38 192.168.122.209 [67589.486031] [tdb] Shutdown Tempesta DB Apr 26 10:50:39 192.168.122.209 [67589.758611] End test: t_reconf.test_reconf_base.TestServerOptionsReconf.test_reconf_server_connect_retries_from_0 Apr 26 10:50:39 192.168.122.209 [67589.773578] Start test: t_reconf.test_reconf_base.TestServerOptionsReconf.test_reconf_server_connect_retries_from_10 Apr 26 10:50:40 192.168.122.209 [67591.006383] [tdb] Start Tempesta DB Apr 26 10:50:40 192.168.122.209 [67591.136660] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:50:41 192.168.122.209 [67592.567233] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67592.567233] Maybe that's fine, but it's worth checking the [67592.567233] config - if there is no relations between the [67592.567233] names, then host name confusion attack is possible. Apr 26 10:50:42 192.168.122.209 [67592.681563] [tempesta fw] Configuration processing is completed. Apr 26 10:50:42 192.168.122.209 [67592.746895] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:50:42 192.168.122.209 [67593.206053] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:50:42 192.168.122.209 [67593.241019] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:50:42 192.168.122.209 [67593.275809] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:50:42 192.168.122.209 [67593.313676] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:50:42 192.168.122.209 [67593.361387] [tempesta fw] Tempesta FW is ready Apr 26 10:50:43 192.168.122.209 [67593.950920] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:50:43 192.168.122.209 [67593.982762] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67593.982762] Maybe that's fine, but it's worth checking the [67593.982762] config - if there is no relations between the [67593.982762] names, then host name confusion attack is possible. Apr 26 10:50:43 192.168.122.209 [67594.093608] [tempesta fw] Configuration processing is completed. Apr 26 10:50:43 192.168.122.209 [67594.310014] [tempesta fw] Tempesta FW is ready Apr 26 10:50:45 192.168.122.209 [67596.341906] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 10:50:55 192.168.122.209 [67606.054831] [tdb] Close table 'client0.tdb' Apr 26 10:50:55 192.168.122.209 [67606.241583] [tdb] Close table 'sessions0.tdb' Apr 26 10:50:58 192.168.122.209 [67609.549526] [tdb] Close table 'cache0.tdb' Apr 26 10:50:59 192.168.122.209 [67609.783061] [tdb] Close table 'filter0.tdb' Apr 26 10:50:59 192.168.122.209 [67609.783498] [tempesta fw] modules are stopped Apr 26 10:50:59 192.168.122.209 [67609.970257] [tempesta fw] exiting... Apr 26 10:50:59 192.168.122.209 [67610.124942] [tdb] Shutdown Tempesta DB Apr 26 10:50:59 192.168.122.209 [67610.345462] End test: t_reconf.test_reconf_base.TestServerOptionsReconf.test_reconf_server_connect_retries_from_10 Apr 26 10:50:59 192.168.122.209 [67610.364801] Start test: t_reconf.test_reconf_base.TestServerOptionsReconf.test_reconf_server_connect_retries_from_default Apr 26 10:51:01 192.168.122.209 [67611.702533] [tdb] Start Tempesta DB Apr 26 10:51:01 192.168.122.209 [67611.848034] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:51:02 192.168.122.209 [67613.274510] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67613.274510] Maybe that's fine, but it's worth checking the [67613.274510] config - if there is no relations between the [67613.274510] names, then host name confusion attack is possible. Apr 26 10:51:02 192.168.122.209 [67613.385822] [tempesta fw] Configuration processing is completed. Apr 26 10:51:02 192.168.122.209 [67613.457052] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:51:03 192.168.122.209 [67613.898162] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:51:03 192.168.122.209 [67613.925206] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:51:03 192.168.122.209 [67613.952446] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:51:03 192.168.122.209 [67614.029761] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:51:03 192.168.122.209 [67614.069732] [tempesta fw] Tempesta FW is ready Apr 26 10:51:03 192.168.122.209 [67614.584719] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:51:03 192.168.122.209 [67614.614404] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67614.614404] Maybe that's fine, but it's worth checking the [67614.614404] config - if there is no relations between the [67614.614404] names, then host name confusion attack is possible. Apr 26 10:51:04 192.168.122.209 [67614.721860] [tempesta fw] Configuration processing is completed. Apr 26 10:51:04 192.168.122.209 [67614.950161] [tempesta fw] Tempesta FW is ready Apr 26 10:51:06 192.168.122.209 [67616.982338] [tempesta fw] Warning: sock_srv: cannot establish connection for 127.0.0.3:8000: 1 tries, keep trying... Apr 26 10:51:16 192.168.122.209 [67626.677759] [tdb] Close table 'client0.tdb' Apr 26 10:51:16 192.168.122.209 [67626.875137] [tdb] Close table 'sessions0.tdb' Apr 26 10:51:19 192.168.122.209 [67630.123937] [tdb] Close table 'cache0.tdb' Apr 26 10:51:19 192.168.122.209 [67630.384253] [tdb] Close table 'filter0.tdb' Apr 26 10:51:19 192.168.122.209 [67630.384687] [tempesta fw] modules are stopped Apr 26 10:51:19 192.168.122.209 [67630.571940] [tempesta fw] exiting... Apr 26 10:51:20 192.168.122.209 [67630.716840] [tdb] Shutdown Tempesta DB Apr 26 10:51:20 192.168.122.209 [67630.962313] End test: t_reconf.test_reconf_base.TestServerOptionsReconf.test_reconf_server_connect_retries_from_default Apr 26 10:51:20 192.168.122.209 [67630.979864] Start test: t_reconf.test_reconf_base.TestServerOptionsReconf.test_reconf_server_forward_retries_from_0 Apr 26 10:51:21 192.168.122.209 [67632.294526] [tdb] Start Tempesta DB Apr 26 10:51:21 192.168.122.209 [67632.457588] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:51:23 192.168.122.209 [67633.846500] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67633.846500] Maybe that's fine, but it's worth checking the [67633.846500] config - if there is no relations between the [67633.846500] names, then host name confusion attack is possible. Apr 26 10:51:23 192.168.122.209 [67633.946119] [tempesta fw] Configuration processing is completed. Apr 26 10:51:23 192.168.122.209 [67634.001494] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:51:23 192.168.122.209 [67634.442088] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:51:23 192.168.122.209 [67634.473495] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:51:23 192.168.122.209 [67634.500558] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:51:23 192.168.122.209 [67634.594040] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:51:23 192.168.122.209 [67634.633998] [tempesta fw] Tempesta FW is ready Apr 26 10:51:24 192.168.122.209 [67635.170667] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:51:24 192.168.122.209 [67635.194787] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67635.194787] Maybe that's fine, but it's worth checking the [67635.194787] config - if there is no relations between the [67635.194787] names, then host name confusion attack is possible. Apr 26 10:51:24 192.168.122.209 [67635.318064] [tempesta fw] Configuration processing is completed. Apr 26 10:51:24 192.168.122.209 [67635.566390] [tempesta fw] Tempesta FW is ready Apr 26 10:51:25 192.168.122.209 [67635.698615] [tempesta fw] Warning: request evicted: the number of retries exceeded, status 504: 127.0.0.2 Apr 26 10:51:29 192.168.122.209 [67640.375925] [tdb] Close table 'client0.tdb' Apr 26 10:51:29 192.168.122.209 [67640.559234] [tdb] Close table 'sessions0.tdb' Apr 26 10:51:33 192.168.122.209 [67643.766641] [tdb] Close table 'cache0.tdb' Apr 26 10:51:33 192.168.122.209 [67644.026853] [tdb] Close table 'filter0.tdb' Apr 26 10:51:33 192.168.122.209 [67644.027301] [tempesta fw] modules are stopped Apr 26 10:51:33 192.168.122.209 [67644.256578] [tempesta fw] exiting... Apr 26 10:51:33 192.168.122.209 [67644.366595] [tdb] Shutdown Tempesta DB Apr 26 10:51:33 192.168.122.209 [67644.612456] End test: t_reconf.test_reconf_base.TestServerOptionsReconf.test_reconf_server_forward_retries_from_0 Apr 26 10:51:33 192.168.122.209 [67644.623011] Start test: t_reconf.test_reconf_base.TestServerOptionsReconf.test_reconf_server_forward_retries_from_1 Apr 26 10:51:35 192.168.122.209 [67645.881613] [tdb] Start Tempesta DB Apr 26 10:51:35 192.168.122.209 [67646.025931] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:51:36 192.168.122.209 [67647.409473] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67647.409473] Maybe that's fine, but it's worth checking the [67647.409473] config - if there is no relations between the [67647.409473] names, then host name confusion attack is possible. Apr 26 10:51:36 192.168.122.209 [67647.498238] [tempesta fw] Configuration processing is completed. Apr 26 10:51:36 192.168.122.209 [67647.553419] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:51:37 192.168.122.209 [67647.965855] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:51:37 192.168.122.209 [67647.993052] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:51:37 192.168.122.209 [67648.020534] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:51:37 192.168.122.209 [67648.078194] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:51:37 192.168.122.209 [67648.122152] [tempesta fw] Tempesta FW is ready Apr 26 10:51:37 192.168.122.209 [67648.606293] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:51:37 192.168.122.209 [67648.623470] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67648.623470] Maybe that's fine, but it's worth checking the [67648.623470] config - if there is no relations between the [67648.623470] names, then host name confusion attack is possible. Apr 26 10:51:38 192.168.122.209 [67648.730241] [tempesta fw] Configuration processing is completed. Apr 26 10:51:38 192.168.122.209 [67648.978592] [tempesta fw] Tempesta FW is ready Apr 26 10:51:38 192.168.122.209 [67649.122444] [tempesta fw] Warning: request evicted: the number of retries exceeded, status 504: 127.0.0.2 Apr 26 10:51:43 192.168.122.209 [67653.878670] [tdb] Close table 'client0.tdb' Apr 26 10:51:43 192.168.122.209 [67654.069616] [tdb] Close table 'sessions0.tdb' Apr 26 10:51:46 192.168.122.209 [67657.344434] [tdb] Close table 'cache0.tdb' Apr 26 10:51:46 192.168.122.209 [67657.586319] [tdb] Close table 'filter0.tdb' Apr 26 10:51:46 192.168.122.209 [67657.586779] [tempesta fw] modules are stopped Apr 26 10:51:47 192.168.122.209 [67657.783862] [tempesta fw] exiting... Apr 26 10:51:47 192.168.122.209 [67657.908933] [tdb] Shutdown Tempesta DB Apr 26 10:51:47 192.168.122.209 [67658.155751] End test: t_reconf.test_reconf_base.TestServerOptionsReconf.test_reconf_server_forward_retries_from_1 Apr 26 10:51:47 192.168.122.209 [67658.168226] Start test: t_reconf.test_reconf_base.TestServerOptionsReconf.test_reconf_server_forward_retries_from_default Apr 26 10:51:48 192.168.122.209 [67659.506193] [tdb] Start Tempesta DB Apr 26 10:51:48 192.168.122.209 [67659.645683] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:51:50 192.168.122.209 [67661.084393] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67661.084393] Maybe that's fine, but it's worth checking the [67661.084393] config - if there is no relations between the [67661.084393] names, then host name confusion attack is possible. Apr 26 10:51:50 192.168.122.209 [67661.198484] [tempesta fw] Configuration processing is completed. Apr 26 10:51:50 192.168.122.209 [67661.255662] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:51:51 192.168.122.209 [67661.709298] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:51:51 192.168.122.209 [67661.744841] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:51:51 192.168.122.209 [67661.772033] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:51:51 192.168.122.209 [67661.830408] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:51:51 192.168.122.209 [67661.870407] [tempesta fw] Tempesta FW is ready Apr 26 10:51:51 192.168.122.209 [67662.360853] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:51:51 192.168.122.209 [67662.383002] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67662.383002] Maybe that's fine, but it's worth checking the [67662.383002] config - if there is no relations between the [67662.383002] names, then host name confusion attack is possible. Apr 26 10:51:51 192.168.122.209 [67662.498377] [tempesta fw] Configuration processing is completed. Apr 26 10:51:52 192.168.122.209 [67662.778589] [tempesta fw] Tempesta FW is ready Apr 26 10:51:52 192.168.122.209 [67662.914727] [tempesta fw] Warning: request evicted: the number of retries exceeded, status 504: 127.0.0.2 Apr 26 10:51:56 192.168.122.209 [67667.573011] [tdb] Close table 'client0.tdb' Apr 26 10:51:57 192.168.122.209 [67667.875195] [tdb] Close table 'sessions0.tdb' Apr 26 10:52:00 192.168.122.209 [67671.169408] [tdb] Close table 'cache0.tdb' Apr 26 10:52:00 192.168.122.209 [67671.399602] [tdb] Close table 'filter0.tdb' Apr 26 10:52:00 192.168.122.209 [67671.400043] [tempesta fw] modules are stopped Apr 26 10:52:00 192.168.122.209 [67671.594673] [tempesta fw] exiting... Apr 26 10:52:01 192.168.122.209 [67671.735242] [tdb] Shutdown Tempesta DB Apr 26 10:52:01 192.168.122.209 [67671.941595] End test: t_reconf.test_reconf_base.TestServerOptionsReconf.test_reconf_server_forward_retries_from_default Apr 26 10:52:01 192.168.122.209 [67671.955535] Start test: t_reconf.test_reconf_base.TestServerOptionsReconf.test_reconf_server_forward_retries_from_x Apr 26 10:52:02 192.168.122.209 [67673.012941] [tdb] Start Tempesta DB Apr 26 10:52:02 192.168.122.209 [67673.165260] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:52:03 192.168.122.209 [67674.504237] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67674.504237] Maybe that's fine, but it's worth checking the [67674.504237] config - if there is no relations between the [67674.504237] names, then host name confusion attack is possible. Apr 26 10:52:03 192.168.122.209 [67674.634708] [tempesta fw] Configuration processing is completed. Apr 26 10:52:04 192.168.122.209 [67674.689249] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:52:04 192.168.122.209 [67675.109759] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:52:04 192.168.122.209 [67675.135639] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:52:04 192.168.122.209 [67675.161522] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:52:04 192.168.122.209 [67675.202653] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:52:04 192.168.122.209 [67675.254599] [tempesta fw] Tempesta FW is ready Apr 26 10:52:05 192.168.122.209 [67675.707663] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:52:05 192.168.122.209 [67675.731393] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67675.731393] Maybe that's fine, but it's worth checking the [67675.731393] config - if there is no relations between the [67675.731393] names, then host name confusion attack is possible. Apr 26 10:52:05 192.168.122.209 [67675.842701] [tempesta fw] Configuration processing is completed. Apr 26 10:52:05 192.168.122.209 [67676.126996] [tempesta fw] Tempesta FW is ready Apr 26 10:52:05 192.168.122.209 [67676.222919] [tempesta fw] Warning: request evicted: the number of retries exceeded, status 504: 127.0.0.2 Apr 26 10:52:10 192.168.122.209 [67680.997758] [tdb] Close table 'client0.tdb' Apr 26 10:52:10 192.168.122.209 [67681.163453] [tdb] Close table 'sessions0.tdb' Apr 26 10:52:13 192.168.122.209 [67684.376883] [tdb] Close table 'cache0.tdb' Apr 26 10:52:13 192.168.122.209 [67684.634057] [tdb] Close table 'filter0.tdb' Apr 26 10:52:13 192.168.122.209 [67684.634478] [tempesta fw] modules are stopped Apr 26 10:52:14 192.168.122.209 [67684.818225] [tempesta fw] exiting... Apr 26 10:52:14 192.168.122.209 [67684.956098] [tdb] Shutdown Tempesta DB Apr 26 10:52:14 192.168.122.209 [67685.148918] End test: t_reconf.test_reconf_base.TestServerOptionsReconf.test_reconf_server_forward_retries_from_x Apr 26 10:52:14 192.168.122.209 [67685.171772] Start test: t_reconf.test_reconf_base.TestServerOptionsReconf.test_reconf_server_forward_timeout_disabled Apr 26 10:52:15 192.168.122.209 [67686.258404] [tdb] Start Tempesta DB Apr 26 10:52:15 192.168.122.209 [67686.419094] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:52:17 192.168.122.209 [67687.831038] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67687.831038] Maybe that's fine, but it's worth checking the [67687.831038] config - if there is no relations between the [67687.831038] names, then host name confusion attack is possible. Apr 26 10:52:17 192.168.122.209 [67687.934893] [tempesta fw] Configuration processing is completed. Apr 26 10:52:17 192.168.122.209 [67687.992097] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:52:17 192.168.122.209 [67688.449989] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:52:17 192.168.122.209 [67688.478735] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:52:17 192.168.122.209 [67688.505570] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:52:17 192.168.122.209 [67688.554827] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:52:17 192.168.122.209 [67688.598794] [tempesta fw] Tempesta FW is ready Apr 26 10:52:18 192.168.122.209 [67689.118586] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:52:18 192.168.122.209 [67689.144078] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67689.144078] Maybe that's fine, but it's worth checking the [67689.144078] config - if there is no relations between the [67689.144078] names, then host name confusion attack is possible. Apr 26 10:52:18 192.168.122.209 [67689.246905] [tempesta fw] Configuration processing is completed. Apr 26 10:52:18 192.168.122.209 [67689.487214] [tempesta fw] Tempesta FW is ready Apr 26 10:52:27 192.168.122.209 [67697.883062] [tempesta fw] Warning: request evicted: the number of retries exceeded, status 504: 127.0.0.2 Apr 26 10:52:27 192.168.122.209 [67698.379068] [tdb] Close table 'client0.tdb' Apr 26 10:52:27 192.168.122.209 [67698.552666] [tdb] Close table 'sessions0.tdb' Apr 26 10:52:31 192.168.122.209 [67701.775226] [tdb] Close table 'cache0.tdb' Apr 26 10:52:31 192.168.122.209 [67702.026641] [tdb] Close table 'filter0.tdb' Apr 26 10:52:31 192.168.122.209 [67702.027086] [tempesta fw] modules are stopped Apr 26 10:52:31 192.168.122.209 [67702.226732] [tempesta fw] exiting... Apr 26 10:52:31 192.168.122.209 [67702.350555] [tdb] Shutdown Tempesta DB Apr 26 10:52:31 192.168.122.209 [67702.560301] End test: t_reconf.test_reconf_base.TestServerOptionsReconf.test_reconf_server_forward_timeout_disabled Apr 26 10:52:31 192.168.122.209 [67702.582849] Start test: t_reconf.test_reconf_base.TestServerOptionsReconf.test_reconf_server_forward_timeout_enabled Apr 26 10:52:33 192.168.122.209 [67703.697824] [tdb] Start Tempesta DB Apr 26 10:52:33 192.168.122.209 [67703.850987] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:52:34 192.168.122.209 [67705.225097] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67705.225097] Maybe that's fine, but it's worth checking the [67705.225097] config - if there is no relations between the [67705.225097] names, then host name confusion attack is possible. Apr 26 10:52:34 192.168.122.209 [67705.323234] [tempesta fw] Configuration processing is completed. Apr 26 10:52:34 192.168.122.209 [67705.386519] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:52:35 192.168.122.209 [67705.826258] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:52:35 192.168.122.209 [67705.853291] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:52:35 192.168.122.209 [67705.888256] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:52:35 192.168.122.209 [67705.931121] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:52:35 192.168.122.209 [67705.971099] [tempesta fw] Tempesta FW is ready Apr 26 10:52:35 192.168.122.209 [67706.478950] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:52:35 192.168.122.209 [67706.495810] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67706.495810] Maybe that's fine, but it's worth checking the [67706.495810] config - if there is no relations between the [67706.495810] names, then host name confusion attack is possible. Apr 26 10:52:35 192.168.122.209 [67706.615138] [tempesta fw] Configuration processing is completed. Apr 26 10:52:36 192.168.122.209 [67706.887484] [tempesta fw] Tempesta FW is ready Apr 26 10:52:37 192.168.122.209 [67707.999251] [tempesta fw] Warning: request evicted: timed out, status 504: 127.0.0.2 Apr 26 10:52:37 192.168.122.209 [67708.452180] [tdb] Close table 'client0.tdb' Apr 26 10:52:37 192.168.122.209 [67708.655091] [tdb] Close table 'sessions0.tdb' Apr 26 10:52:41 192.168.122.209 [67711.874415] [tdb] Close table 'cache0.tdb' Apr 26 10:52:41 192.168.122.209 [67712.141767] [tdb] Close table 'filter0.tdb' Apr 26 10:52:41 192.168.122.209 [67712.142224] [tempesta fw] modules are stopped Apr 26 10:52:41 192.168.122.209 [67712.315996] [tempesta fw] exiting... Apr 26 10:52:41 192.168.122.209 [67712.436817] [tdb] Shutdown Tempesta DB Apr 26 10:52:42 192.168.122.209 [67712.660565] End test: t_reconf.test_reconf_base.TestServerOptionsReconf.test_reconf_server_forward_timeout_enabled Apr 26 10:52:42 192.168.122.209 [67712.677387] Start test: t_reconf.test_reconf_base.TestServerOptionsReconf.test_reconf_server_queue_size_disabled Apr 26 10:52:43 192.168.122.209 [67713.807550] [tdb] Start Tempesta DB Apr 26 10:52:43 192.168.122.209 [67713.946571] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:52:44 192.168.122.209 [67715.400639] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67715.400639] Maybe that's fine, but it's worth checking the [67715.400639] config - if there is no relations between the [67715.400639] names, then host name confusion attack is possible. Apr 26 10:52:44 192.168.122.209 [67715.499341] [tempesta fw] Configuration processing is completed. Apr 26 10:52:44 192.168.122.209 [67715.560561] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:52:45 192.168.122.209 [67715.991568] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:52:45 192.168.122.209 [67716.017069] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:52:45 192.168.122.209 [67716.042023] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:52:45 192.168.122.209 [67716.103272] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:52:45 192.168.122.209 [67716.155226] [tempesta fw] Tempesta FW is ready Apr 26 10:52:46 192.168.122.209 [67716.697032] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:52:46 192.168.122.209 [67716.730893] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67716.730893] Maybe that's fine, but it's worth checking the [67716.730893] config - if there is no relations between the [67716.730893] names, then host name confusion attack is possible. Apr 26 10:52:46 192.168.122.209 [67716.843302] [tempesta fw] Configuration processing is completed. Apr 26 10:52:46 192.168.122.209 [67717.011637] [tempesta fw] Tempesta FW is ready Apr 26 10:52:47 192.168.122.209 [67718.526833] [tdb] Close table 'client0.tdb' Apr 26 10:52:48 192.168.122.209 [67718.712848] [tdb] Close table 'sessions0.tdb' Apr 26 10:52:51 192.168.122.209 [67721.926865] [tdb] Close table 'cache0.tdb' Apr 26 10:52:51 192.168.122.209 [67722.173910] [tdb] Close table 'filter0.tdb' Apr 26 10:52:51 192.168.122.209 [67722.174336] [tempesta fw] modules are stopped Apr 26 10:52:51 192.168.122.209 [67722.373217] [tempesta fw] exiting... Apr 26 10:52:51 192.168.122.209 [67722.480151] [tdb] Shutdown Tempesta DB Apr 26 10:52:52 192.168.122.209 [67722.708672] End test: t_reconf.test_reconf_base.TestServerOptionsReconf.test_reconf_server_queue_size_disabled Apr 26 10:52:52 192.168.122.209 [67722.721697] Start test: t_reconf.test_reconf_base.TestServerOptionsReconf.test_reconf_server_retry_nonidempotent_disabled Apr 26 10:52:53 192.168.122.209 [67723.841552] [tdb] Start Tempesta DB Apr 26 10:52:53 192.168.122.209 [67723.988254] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:52:54 192.168.122.209 [67725.477172] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67725.477172] Maybe that's fine, but it's worth checking the [67725.477172] config - if there is no relations between the [67725.477172] names, then host name confusion attack is possible. Apr 26 10:52:54 192.168.122.209 [67725.635448] [tempesta fw] Configuration processing is completed. Apr 26 10:52:55 192.168.122.209 [67725.687288] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:52:55 192.168.122.209 [67726.129528] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:52:55 192.168.122.209 [67726.155433] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:52:55 192.168.122.209 [67726.182506] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:52:55 192.168.122.209 [67726.231390] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:52:55 192.168.122.209 [67726.271393] [tempesta fw] Tempesta FW is ready Apr 26 10:52:56 192.168.122.209 [67726.973956] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:52:56 192.168.122.209 [67726.992119] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67726.992119] Maybe that's fine, but it's worth checking the [67726.992119] config - if there is no relations between the [67726.992119] names, then host name confusion attack is possible. Apr 26 10:52:56 192.168.122.209 [67727.147514] [tempesta fw] Configuration processing is completed. Apr 26 10:52:56 192.168.122.209 [67727.455909] [tempesta fw] Tempesta FW is ready Apr 26 10:52:56 192.168.122.209 [67727.567765] [tempesta fw] Warning: request dropped: non-idempotent requests aren't re-forwarded or re-scheduled, status 504: 127.0.0.2 Apr 26 10:52:57 192.168.122.209 [67728.055229] [tdb] Close table 'client0.tdb' Apr 26 10:52:57 192.168.122.209 [67728.266383] [tdb] Close table 'sessions0.tdb' Apr 26 10:53:00 192.168.122.209 [67731.450975] [tdb] Close table 'cache0.tdb' Apr 26 10:53:01 192.168.122.209 [67731.676548] [tdb] Close table 'filter0.tdb' Apr 26 10:53:01 192.168.122.209 [67731.676981] [tempesta fw] modules are stopped Apr 26 10:53:01 192.168.122.209 [67731.883010] [tempesta fw] exiting... Apr 26 10:53:01 192.168.122.209 [67732.012976] [tdb] Shutdown Tempesta DB Apr 26 10:53:01 192.168.122.209 [67732.216814] End test: t_reconf.test_reconf_base.TestServerOptionsReconf.test_reconf_server_retry_nonidempotent_disabled Apr 26 10:53:01 192.168.122.209 [67732.230149] Start test: t_reconf.test_reconf_base.TestServerOptionsReconf.test_reconf_server_retry_nonidempotent_enabled Apr 26 10:53:02 192.168.122.209 [67733.334433] [tdb] Start Tempesta DB Apr 26 10:53:02 192.168.122.209 [67733.478086] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:53:04 192.168.122.209 [67734.980872] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67734.980872] Maybe that's fine, but it's worth checking the [67734.980872] config - if there is no relations between the [67734.980872] names, then host name confusion attack is possible. Apr 26 10:53:04 192.168.122.209 [67735.115597] [tempesta fw] Configuration processing is completed. Apr 26 10:53:04 192.168.122.209 [67735.169596] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:53:04 192.168.122.209 [67735.644035] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:53:05 192.168.122.209 [67735.672876] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:53:05 192.168.122.209 [67735.700753] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:53:05 192.168.122.209 [67735.751589] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:53:05 192.168.122.209 [67735.795540] [tempesta fw] Tempesta FW is ready Apr 26 10:53:05 192.168.122.209 [67736.444195] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:53:05 192.168.122.209 [67736.468575] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67736.468575] Maybe that's fine, but it's worth checking the [67736.468575] config - if there is no relations between the [67736.468575] names, then host name confusion attack is possible. Apr 26 10:53:05 192.168.122.209 [67736.635633] [tempesta fw] Configuration processing is completed. Apr 26 10:53:06 192.168.122.209 [67736.916001] [tempesta fw] Tempesta FW is ready Apr 26 10:53:06 192.168.122.209 [67737.047550] [tempesta fw] Warning: request evicted: the number of retries exceeded, status 504: 127.0.0.2 Apr 26 10:53:06 192.168.122.209 [67737.515546] [tdb] Close table 'client0.tdb' Apr 26 10:53:07 192.168.122.209 [67737.724602] [tdb] Close table 'sessions0.tdb' Apr 26 10:53:10 192.168.122.209 [67740.950686] [tdb] Close table 'cache0.tdb' Apr 26 10:53:10 192.168.122.209 [67741.204731] [tdb] Close table 'filter0.tdb' Apr 26 10:53:10 192.168.122.209 [67741.205163] [tempesta fw] modules are stopped Apr 26 10:53:10 192.168.122.209 [67741.430428] [tempesta fw] exiting... Apr 26 10:53:10 192.168.122.209 [67741.544699] [tdb] Shutdown Tempesta DB Apr 26 10:53:11 192.168.122.209 [67741.774148] End test: t_reconf.test_reconf_base.TestServerOptionsReconf.test_reconf_server_retry_nonidempotent_enabled Apr 26 10:53:11 192.168.122.209 [67741.791180] Start test: t_reconf.test_reconf_base.TestServerReconf.test_add_new_server_group Apr 26 10:53:12 192.168.122.209 [67742.820792] [tdb] Start Tempesta DB Apr 26 10:53:12 192.168.122.209 [67742.979685] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:53:13 192.168.122.209 [67744.467822] [tempesta fw] Configuration processing is completed. Apr 26 10:53:13 192.168.122.209 [67744.524160] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:53:14 192.168.122.209 [67745.007285] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:53:14 192.168.122.209 [67745.036578] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:53:14 192.168.122.209 [67745.065888] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:53:14 192.168.122.209 [67745.111728] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:53:14 192.168.122.209 [67745.159672] [tempesta fw] Tempesta FW is ready Apr 26 10:53:15 192.168.122.209 [67745.859280] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:53:15 192.168.122.209 [67746.063724] [tempesta fw] Configuration processing is completed. Apr 26 10:53:15 192.168.122.209 [67746.415783] [tempesta fw] Tempesta FW is ready Apr 26 10:53:16 192.168.122.209 [67747.229994] [tdb] Close table 'client0.tdb' Apr 26 10:53:16 192.168.122.209 [67747.425555] [tdb] Close table 'sessions0.tdb' Apr 26 10:53:19 192.168.122.209 [67750.612046] [tdb] Close table 'cache0.tdb' Apr 26 10:53:20 192.168.122.209 [67750.843830] [tdb] Close table 'filter0.tdb' Apr 26 10:53:20 192.168.122.209 [67750.844274] [tempesta fw] modules are stopped Apr 26 10:53:20 192.168.122.209 [67751.080198] [tempesta fw] exiting... Apr 26 10:53:20 192.168.122.209 [67751.215203] [tdb] Shutdown Tempesta DB Apr 26 10:53:20 192.168.122.209 [67751.431495] End test: t_reconf.test_reconf_base.TestServerReconf.test_add_new_server_group Apr 26 10:53:20 192.168.122.209 [67751.441382] Start test: t_reconf.test_reconf_base.TestServerReconf.test_add_new_server_to_default_srv_group Apr 26 10:53:21 192.168.122.209 [67752.485590] [tdb] Start Tempesta DB Apr 26 10:53:21 192.168.122.209 [67752.652052] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:53:23 192.168.122.209 [67753.788240] [tempesta fw] Configuration processing is completed. Apr 26 10:53:23 192.168.122.209 [67753.845183] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:53:23 192.168.122.209 [67754.363063] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:53:23 192.168.122.209 [67754.402542] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:53:23 192.168.122.209 [67754.431287] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:53:23 192.168.122.209 [67754.507855] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:53:23 192.168.122.209 [67754.547801] [tempesta fw] Tempesta FW is ready Apr 26 10:53:24 192.168.122.209 [67754.925409] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:53:24 192.168.122.209 [67755.023940] [tempesta fw] Configuration processing is completed. Apr 26 10:53:24 192.168.122.209 [67755.335862] [tempesta fw] Tempesta FW is ready Apr 26 10:53:25 192.168.122.209 [67756.109917] [tdb] Close table 'client0.tdb' Apr 26 10:53:25 192.168.122.209 [67756.293352] [tdb] Close table 'sessions0.tdb' Apr 26 10:53:28 192.168.122.209 [67759.576548] [tdb] Close table 'cache0.tdb' Apr 26 10:53:29 192.168.122.209 [67759.823381] [tdb] Close table 'filter0.tdb' Apr 26 10:53:29 192.168.122.209 [67759.823864] [tempesta fw] modules are stopped Apr 26 10:53:29 192.168.122.209 [67760.005847] [tempesta fw] exiting... Apr 26 10:53:29 192.168.122.209 [67760.131919] [tdb] Shutdown Tempesta DB Apr 26 10:53:29 192.168.122.209 [67760.353610] End test: t_reconf.test_reconf_base.TestServerReconf.test_add_new_server_to_default_srv_group Apr 26 10:53:29 192.168.122.209 [67760.367242] Start test: t_reconf.test_reconf_base.TestServerReconf.test_add_new_server_to_srv_group Apr 26 10:53:30 192.168.122.209 [67761.535840] [tdb] Start Tempesta DB Apr 26 10:53:31 192.168.122.209 [67761.705508] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:53:32 192.168.122.209 [67763.280383] [tempesta fw] Configuration processing is completed. Apr 26 10:53:32 192.168.122.209 [67763.339852] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:53:33 192.168.122.209 [67763.834643] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:53:33 192.168.122.209 [67763.867731] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:53:33 192.168.122.209 [67763.898221] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:53:33 192.168.122.209 [67763.940009] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:53:33 192.168.122.209 [67763.983942] [tempesta fw] Tempesta FW is ready Apr 26 10:53:33 192.168.122.209 [67764.490300] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:53:33 192.168.122.209 [67764.648069] [tempesta fw] Configuration processing is completed. Apr 26 10:53:34 192.168.122.209 [67764.904124] [tempesta fw] Tempesta FW is ready Apr 26 10:53:35 192.168.122.209 [67765.806962] [tdb] Close table 'client0.tdb' Apr 26 10:53:35 192.168.122.209 [67766.002224] [tdb] Close table 'sessions0.tdb' Apr 26 10:53:38 192.168.122.209 [67769.217239] [tdb] Close table 'cache0.tdb' Apr 26 10:53:38 192.168.122.209 [67769.454713] [tdb] Close table 'filter0.tdb' Apr 26 10:53:38 192.168.122.209 [67769.455140] [tempesta fw] modules are stopped Apr 26 10:53:39 192.168.122.209 [67769.665289] [tempesta fw] exiting... Apr 26 10:53:39 192.168.122.209 [67769.814725] [tdb] Shutdown Tempesta DB Apr 26 10:53:39 192.168.122.209 [67770.015192] End test: t_reconf.test_reconf_base.TestServerReconf.test_add_new_server_to_srv_group Apr 26 10:53:39 192.168.122.209 [67770.029595] Start test: t_reconf.test_reconf_base.TestServerReconf.test_conns_n_decrease Apr 26 10:53:40 192.168.122.209 [67771.097854] [tdb] Start Tempesta DB Apr 26 10:53:40 192.168.122.209 [67771.228381] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:53:41 192.168.122.209 [67772.360290] [tempesta fw] Configuration processing is completed. Apr 26 10:53:41 192.168.122.209 [67772.423640] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:53:42 192.168.122.209 [67772.919954] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:53:42 192.168.122.209 [67772.953264] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:53:42 192.168.122.209 [67772.986734] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:53:42 192.168.122.209 [67773.028128] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:53:42 192.168.122.209 [67773.068094] [tempesta fw] Tempesta FW is ready Apr 26 10:53:42 192.168.122.209 [67773.426757] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:53:42 192.168.122.209 [67773.468136] [tempesta fw] Configuration processing is completed. Apr 26 10:53:43 192.168.122.209 [67773.728221] [tempesta fw] Tempesta FW is ready Apr 26 10:53:43 192.168.122.209 [67774.188157] [tdb] Close table 'client0.tdb' Apr 26 10:53:43 192.168.122.209 [67774.380448] [tdb] Close table 'sessions0.tdb' Apr 26 10:53:46 192.168.122.209 [67777.641027] [tdb] Close table 'cache0.tdb' Apr 26 10:53:47 192.168.122.209 [67777.894127] [tdb] Close table 'filter0.tdb' Apr 26 10:53:47 192.168.122.209 [67777.894557] [tempesta fw] modules are stopped Apr 26 10:53:47 192.168.122.209 [67778.082503] [tempesta fw] exiting... Apr 26 10:53:47 192.168.122.209 [67778.224504] [tdb] Shutdown Tempesta DB Apr 26 10:53:47 192.168.122.209 [67778.460054] End test: t_reconf.test_reconf_base.TestServerReconf.test_conns_n_decrease Apr 26 10:53:47 192.168.122.209 [67778.479439] Start test: t_reconf.test_reconf_base.TestServerReconf.test_conns_n_decrease_from_default Apr 26 10:53:48 192.168.122.209 [67779.519313] [tdb] Start Tempesta DB Apr 26 10:53:48 192.168.122.209 [67779.657951] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:53:50 192.168.122.209 [67780.840664] [tempesta fw] Configuration processing is completed. Apr 26 10:53:50 192.168.122.209 [67780.906287] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:53:50 192.168.122.209 [67781.375908] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:53:50 192.168.122.209 [67781.403837] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:53:50 192.168.122.209 [67781.432000] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:53:50 192.168.122.209 [67781.472304] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:53:50 192.168.122.209 [67781.512222] [tempesta fw] Tempesta FW is ready Apr 26 10:53:51 192.168.122.209 [67781.871656] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:53:51 192.168.122.209 [67781.920687] [tempesta fw] Configuration processing is completed. Apr 26 10:53:51 192.168.122.209 [67782.164378] [tempesta fw] Tempesta FW is ready Apr 26 10:53:51 192.168.122.209 [67782.612923] [tdb] Close table 'client0.tdb' Apr 26 10:53:52 192.168.122.209 [67782.801340] [tdb] Close table 'sessions0.tdb' Apr 26 10:53:55 192.168.122.209 [67785.995572] [tdb] Close table 'cache0.tdb' Apr 26 10:53:55 192.168.122.209 [67786.265052] [tdb] Close table 'filter0.tdb' Apr 26 10:53:55 192.168.122.209 [67786.265485] [tempesta fw] modules are stopped Apr 26 10:53:55 192.168.122.209 [67786.490100] [tempesta fw] exiting... Apr 26 10:53:55 192.168.122.209 [67786.595336] [tdb] Shutdown Tempesta DB Apr 26 10:53:56 192.168.122.209 [67786.791754] End test: t_reconf.test_reconf_base.TestServerReconf.test_conns_n_decrease_from_default Apr 26 10:53:56 192.168.122.209 [67786.816109] Start test: t_reconf.test_reconf_base.TestServerReconf.test_conns_n_for_srv_group_decrease Apr 26 10:53:57 192.168.122.209 [67787.862432] [tdb] Start Tempesta DB Apr 26 10:53:57 192.168.122.209 [67788.002126] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:53:58 192.168.122.209 [67789.344865] [tempesta fw] Configuration processing is completed. Apr 26 10:53:58 192.168.122.209 [67789.402074] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:53:59 192.168.122.209 [67789.827437] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:53:59 192.168.122.209 [67789.852941] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:53:59 192.168.122.209 [67789.879152] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:53:59 192.168.122.209 [67789.936391] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:53:59 192.168.122.209 [67789.976334] [tempesta fw] Tempesta FW is ready Apr 26 10:53:59 192.168.122.209 [67790.450069] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:53:59 192.168.122.209 [67790.560515] [tempesta fw] Configuration processing is completed. Apr 26 10:54:00 192.168.122.209 [67790.788490] [tempesta fw] Tempesta FW is ready Apr 26 10:54:00 192.168.122.209 [67791.281397] [tdb] Close table 'client0.tdb' Apr 26 10:54:00 192.168.122.209 [67791.450109] [tdb] Close table 'sessions0.tdb' Apr 26 10:54:04 192.168.122.209 [67794.665161] [tdb] Close table 'cache0.tdb' Apr 26 10:54:04 192.168.122.209 [67794.918094] [tdb] Close table 'filter0.tdb' Apr 26 10:54:04 192.168.122.209 [67794.918548] [tempesta fw] modules are stopped Apr 26 10:54:04 192.168.122.209 [67795.132541] [tempesta fw] exiting... Apr 26 10:54:04 192.168.122.209 [67795.255047] [tdb] Shutdown Tempesta DB Apr 26 10:54:04 192.168.122.209 [67795.440624] End test: t_reconf.test_reconf_base.TestServerReconf.test_conns_n_for_srv_group_decrease Apr 26 10:54:04 192.168.122.209 [67795.449420] Start test: t_reconf.test_reconf_base.TestServerReconf.test_conns_n_for_srv_group_increase Apr 26 10:54:05 192.168.122.209 [67796.520773] [tdb] Start Tempesta DB Apr 26 10:54:05 192.168.122.209 [67796.652132] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:54:07 192.168.122.209 [67798.064643] [tempesta fw] Configuration processing is completed. Apr 26 10:54:07 192.168.122.209 [67798.117987] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:54:07 192.168.122.209 [67798.528418] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:54:07 192.168.122.209 [67798.554513] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:54:07 192.168.122.209 [67798.581063] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:54:07 192.168.122.209 [67798.624531] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:54:08 192.168.122.209 [67798.672517] [tempesta fw] Tempesta FW is ready Apr 26 10:54:08 192.168.122.209 [67799.174105] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:54:08 192.168.122.209 [67799.272601] [tempesta fw] Configuration processing is completed. Apr 26 10:54:09 192.168.122.209 [67800.128645] [tempesta fw] Tempesta FW is ready Apr 26 10:54:09 192.168.122.209 [67800.611092] [tdb] Close table 'client0.tdb' Apr 26 10:54:10 192.168.122.209 [67800.795629] [tdb] Close table 'sessions0.tdb' Apr 26 10:54:13 192.168.122.209 [67804.002155] [tdb] Close table 'cache0.tdb' Apr 26 10:54:13 192.168.122.209 [67804.230891] [tdb] Close table 'filter0.tdb' Apr 26 10:54:13 192.168.122.209 [67804.231295] [tempesta fw] modules are stopped Apr 26 10:54:13 192.168.122.209 [67804.438038] [tempesta fw] exiting... Apr 26 10:54:13 192.168.122.209 [67804.573993] [tdb] Shutdown Tempesta DB Apr 26 10:54:14 192.168.122.209 [67804.775530] End test: t_reconf.test_reconf_base.TestServerReconf.test_conns_n_for_srv_group_increase Apr 26 10:54:14 192.168.122.209 [67804.799268] Start test: t_reconf.test_reconf_base.TestServerReconf.test_conns_n_increase Apr 26 10:54:15 192.168.122.209 [67805.873547] [tdb] Start Tempesta DB Apr 26 10:54:15 192.168.122.209 [67806.013734] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:54:16 192.168.122.209 [67807.153031] [tempesta fw] Configuration processing is completed. Apr 26 10:54:16 192.168.122.209 [67807.207630] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:54:16 192.168.122.209 [67807.617110] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:54:16 192.168.122.209 [67807.642847] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:54:17 192.168.122.209 [67807.669337] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:54:17 192.168.122.209 [67807.708699] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:54:17 192.168.122.209 [67807.748616] [tempesta fw] Tempesta FW is ready Apr 26 10:54:17 192.168.122.209 [67808.119082] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:54:17 192.168.122.209 [67808.164774] [tempesta fw] Configuration processing is completed. Apr 26 10:54:17 192.168.122.209 [67808.400704] [tempesta fw] Tempesta FW is ready Apr 26 10:54:18 192.168.122.209 [67808.891927] [tdb] Close table 'client0.tdb' Apr 26 10:54:18 192.168.122.209 [67809.082206] [tdb] Close table 'sessions0.tdb' Apr 26 10:54:21 192.168.122.209 [67812.273287] [tdb] Close table 'cache0.tdb' Apr 26 10:54:21 192.168.122.209 [67812.534861] [tdb] Close table 'filter0.tdb' Apr 26 10:54:21 192.168.122.209 [67812.535268] [tempesta fw] modules are stopped Apr 26 10:54:22 192.168.122.209 [67812.713138] [tempesta fw] exiting... Apr 26 10:54:22 192.168.122.209 [67812.839990] [tdb] Shutdown Tempesta DB Apr 26 10:54:22 192.168.122.209 [67813.027842] End test: t_reconf.test_reconf_base.TestServerReconf.test_conns_n_increase Apr 26 10:54:22 192.168.122.209 [67813.041075] Start test: t_reconf.test_reconf_base.TestServerReconf.test_conns_n_increase_from_default Apr 26 10:54:23 192.168.122.209 [67814.068491] [tdb] Start Tempesta DB Apr 26 10:54:23 192.168.122.209 [67814.214157] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:54:24 192.168.122.209 [67815.312868] [tempesta fw] Configuration processing is completed. Apr 26 10:54:24 192.168.122.209 [67815.363170] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:54:25 192.168.122.209 [67815.772260] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:54:25 192.168.122.209 [67815.797842] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:54:25 192.168.122.209 [67815.823722] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:54:25 192.168.122.209 [67815.880717] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:54:25 192.168.122.209 [67815.948724] [tempesta fw] Tempesta FW is ready Apr 26 10:54:25 192.168.122.209 [67816.289931] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:54:25 192.168.122.209 [67816.337080] [tempesta fw] Configuration processing is completed. Apr 26 10:54:25 192.168.122.209 [67816.600834] [tempesta fw] Tempesta FW is ready Apr 26 10:54:26 192.168.122.209 [67817.062489] [tdb] Close table 'client0.tdb' Apr 26 10:54:26 192.168.122.209 [67817.245822] [tdb] Close table 'sessions0.tdb' Apr 26 10:54:29 192.168.122.209 [67820.404263] [tdb] Close table 'cache0.tdb' Apr 26 10:54:29 192.168.122.209 [67820.621095] [tdb] Close table 'filter0.tdb' Apr 26 10:54:29 192.168.122.209 [67820.621535] [tempesta fw] modules are stopped Apr 26 10:54:30 192.168.122.209 [67820.840249] [tempesta fw] exiting... Apr 26 10:54:30 192.168.122.209 [67820.958903] [tdb] Shutdown Tempesta DB Apr 26 10:54:30 192.168.122.209 [67821.184277] End test: t_reconf.test_reconf_base.TestServerReconf.test_conns_n_increase_from_default Apr 26 10:54:30 192.168.122.209 [67821.195893] Start test: t_reconf.test_reconf_base.TestServerReconf.test_remove_server_from_default_srv_group Apr 26 10:54:31 192.168.122.209 [67822.203777] [tdb] Start Tempesta DB Apr 26 10:54:31 192.168.122.209 [67822.356725] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:54:32 192.168.122.209 [67823.456936] [tempesta fw] Configuration processing is completed. Apr 26 10:54:32 192.168.122.209 [67823.509060] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:54:33 192.168.122.209 [67823.922837] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:54:33 192.168.122.209 [67823.957288] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:54:33 192.168.122.209 [67823.982646] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:54:33 192.168.122.209 [67824.032900] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:54:33 192.168.122.209 [67824.084848] [tempesta fw] Tempesta FW is ready Apr 26 10:54:33 192.168.122.209 [67824.458467] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:54:33 192.168.122.209 [67824.505443] [tempesta fw] Configuration processing is completed. Apr 26 10:54:34 192.168.122.209 [67824.753066] [tempesta fw] Tempesta FW is ready Apr 26 10:54:34 192.168.122.209 [67825.446653] [tdb] Close table 'client0.tdb' Apr 26 10:54:34 192.168.122.209 [67825.630865] [tdb] Close table 'sessions0.tdb' Apr 26 10:54:38 192.168.122.209 [67828.782667] [tdb] Close table 'cache0.tdb' Apr 26 10:54:38 192.168.122.209 [67829.004685] [tdb] Close table 'filter0.tdb' Apr 26 10:54:38 192.168.122.209 [67829.005128] [tempesta fw] modules are stopped Apr 26 10:54:38 192.168.122.209 [67829.183321] [tempesta fw] exiting... Apr 26 10:54:38 192.168.122.209 [67829.316096] [tdb] Shutdown Tempesta DB Apr 26 10:54:38 192.168.122.209 [67829.529910] End test: t_reconf.test_reconf_base.TestServerReconf.test_remove_server_from_default_srv_group Apr 26 10:54:38 192.168.122.209 [67829.545790] Start test: t_reconf.test_reconf_base.TestServerReconf.test_remove_server_from_srv_group Apr 26 10:54:39 192.168.122.209 [67830.520659] [tdb] Start Tempesta DB Apr 26 10:54:39 192.168.122.209 [67830.656572] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:54:41 192.168.122.209 [67832.329098] [tempesta fw] Configuration processing is completed. Apr 26 10:54:41 192.168.122.209 [67832.380020] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:54:42 192.168.122.209 [67832.801977] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:54:42 192.168.122.209 [67832.827986] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:54:42 192.168.122.209 [67832.854728] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:54:42 192.168.122.209 [67832.953037] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 10:54:42 192.168.122.209 [67833.000950] [tempesta fw] Tempesta FW is ready Apr 26 10:54:42 192.168.122.209 [67833.512220] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:54:42 192.168.122.209 [67833.636992] [tempesta fw] Configuration processing is completed. Apr 26 10:54:43 192.168.122.209 [67833.961245] [tempesta fw] Tempesta FW is ready Apr 26 10:54:43 192.168.122.209 [67834.648739] [tdb] Close table 'client0.tdb' Apr 26 10:54:44 192.168.122.209 [67834.834749] [tdb] Close table 'sessions0.tdb' Apr 26 10:54:47 192.168.122.209 [67837.984116] [tdb] Close table 'cache0.tdb' Apr 26 10:54:47 192.168.122.209 [67838.226922] [tdb] Close table 'filter0.tdb' Apr 26 10:54:47 192.168.122.209 [67838.227317] [tempesta fw] modules are stopped Apr 26 10:54:47 192.168.122.209 [67838.454552] [tempesta fw] exiting... Apr 26 10:54:47 192.168.122.209 [67838.577655] [tdb] Shutdown Tempesta DB Apr 26 10:54:48 192.168.122.209 [67838.777028] End test: t_reconf.test_reconf_base.TestServerReconf.test_remove_server_from_srv_group Apr 26 10:54:48 192.168.122.209 [67838.786681] Start test: t_reconf.test_reconf_base.TestVhostReconf.test_add_vhost Apr 26 10:54:49 192.168.122.209 [67839.706690] [tdb] Start Tempesta DB Apr 26 10:54:49 192.168.122.209 [67839.845702] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:54:50 192.168.122.209 [67841.239280] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67841.239280] Maybe that's fine, but it's worth checking the [67841.239280] config - if there is no relations between the [67841.239280] names, then host name confusion attack is possible. Apr 26 10:54:50 192.168.122.209 [67841.413193] [tempesta fw] Configuration processing is completed. Apr 26 10:54:50 192.168.122.209 [67841.464851] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:54:51 192.168.122.209 [67841.878923] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:54:51 192.168.122.209 [67841.905135] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:54:51 192.168.122.209 [67841.935716] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:54:51 192.168.122.209 [67842.013211] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:54:51 192.168.122.209 [67842.069113] [tempesta fw] Tempesta FW is ready Apr 26 10:54:52 192.168.122.209 [67842.705301] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:54:52 192.168.122.209 [67842.725966] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67842.725966] Maybe that's fine, but it's worth checking the [67842.725966] config - if there is no relations between the [67842.725966] names, then host name confusion attack is possible. Apr 26 10:54:52 192.168.122.209 [67843.013192] [tempesta fw] Configuration processing is completed. Apr 26 10:54:52 192.168.122.209 [67843.389905] [tempesta fw] Tempesta FW is ready Apr 26 10:54:53 192.168.122.209 [67844.082583] [tdb] Close table 'client0.tdb' Apr 26 10:54:53 192.168.122.209 [67844.262187] [tdb] Close table 'sessions0.tdb' Apr 26 10:54:56 192.168.122.209 [67847.366387] [tdb] Close table 'cache0.tdb' Apr 26 10:54:56 192.168.122.209 [67847.605065] [tdb] Close table 'filter0.tdb' Apr 26 10:54:56 192.168.122.209 [67847.605495] [tempesta fw] modules are stopped Apr 26 10:54:57 192.168.122.209 [67847.872665] [tempesta fw] exiting... Apr 26 10:54:57 192.168.122.209 [67848.021055] [tdb] Shutdown Tempesta DB Apr 26 10:54:57 192.168.122.209 [67848.247264] End test: t_reconf.test_reconf_base.TestVhostReconf.test_add_vhost Apr 26 10:54:57 192.168.122.209 [67848.260515] Start test: t_reconf.test_reconf_base.TestVhostReconf.test_change_vhost_name Apr 26 10:54:58 192.168.122.209 [67849.388148] [tdb] Start Tempesta DB Apr 26 10:54:58 192.168.122.209 [67849.522169] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:55:00 192.168.122.209 [67851.042005] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67851.042005] Maybe that's fine, but it's worth checking the [67851.042005] config - if there is no relations between the [67851.042005] names, then host name confusion attack is possible. Apr 26 10:55:00 192.168.122.209 [67851.209391] [tempesta fw] Configuration processing is completed. Apr 26 10:55:00 192.168.122.209 [67851.265945] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:55:01 192.168.122.209 [67851.688045] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:55:01 192.168.122.209 [67851.714619] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:55:01 192.168.122.209 [67851.740852] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:55:01 192.168.122.209 [67851.781308] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:55:01 192.168.122.209 [67851.825260] [tempesta fw] Tempesta FW is ready Apr 26 10:55:01 192.168.122.209 [67852.344476] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:55:01 192.168.122.209 [67852.370167] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67852.370167] Maybe that's fine, but it's worth checking the [67852.370167] config - if there is no relations between the [67852.370167] names, then host name confusion attack is possible. Apr 26 10:55:01 192.168.122.209 [67852.593341] [tempesta fw] Configuration processing is completed. Apr 26 10:55:02 192.168.122.209 [67852.873732] [tempesta fw] Tempesta FW is ready Apr 26 10:55:02 192.168.122.209 [67853.417739] [tdb] Close table 'client0.tdb' Apr 26 10:55:02 192.168.122.209 [67853.615352] [tdb] Close table 'sessions0.tdb' Apr 26 10:55:06 192.168.122.209 [67856.739255] [tdb] Close table 'cache0.tdb' Apr 26 10:55:06 192.168.122.209 [67856.994378] [tdb] Close table 'filter0.tdb' Apr 26 10:55:06 192.168.122.209 [67856.994811] [tempesta fw] modules are stopped Apr 26 10:55:06 192.168.122.209 [67857.205423] [tempesta fw] exiting... Apr 26 10:55:06 192.168.122.209 [67857.338936] [tdb] Shutdown Tempesta DB Apr 26 10:55:06 192.168.122.209 [67857.524646] End test: t_reconf.test_reconf_base.TestVhostReconf.test_change_vhost_name Apr 26 10:55:06 192.168.122.209 [67857.542620] Start test: t_reconf.test_reconf_base.TestVhostReconf.test_remove_vhost Apr 26 10:55:07 192.168.122.209 [67858.492609] [tdb] Start Tempesta DB Apr 26 10:55:07 192.168.122.209 [67858.631180] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:55:09 192.168.122.209 [67860.277086] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67860.277086] Maybe that's fine, but it's worth checking the [67860.277086] config - if there is no relations between the [67860.277086] names, then host name confusion attack is possible. Apr 26 10:55:09 192.168.122.209 [67860.501475] [tempesta fw] Configuration processing is completed. Apr 26 10:55:09 192.168.122.209 [67860.552230] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:55:10 192.168.122.209 [67860.985593] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:55:10 192.168.122.209 [67861.023733] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:55:10 192.168.122.209 [67861.050034] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:55:10 192.168.122.209 [67861.193512] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:55:10 192.168.122.209 [67861.294119] [tempesta fw] Tempesta FW is ready Apr 26 10:55:11 192.168.122.209 [67861.852501] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:55:11 192.168.122.209 [67861.878098] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67861.878098] Maybe that's fine, but it's worth checking the [67861.878098] config - if there is no relations between the [67861.878098] names, then host name confusion attack is possible. Apr 26 10:55:11 192.168.122.209 [67862.069557] [tempesta fw] Configuration processing is completed. Apr 26 10:55:11 192.168.122.209 [67862.409977] [tempesta fw] Tempesta FW is ready Apr 26 10:55:17 192.168.122.209 [67868.038018] [tdb] Close table 'client0.tdb' Apr 26 10:55:17 192.168.122.209 [67868.216650] [tdb] Close table 'sessions0.tdb' Apr 26 10:55:20 192.168.122.209 [67871.356469] [tdb] Close table 'cache0.tdb' Apr 26 10:55:20 192.168.122.209 [67871.565741] [tdb] Close table 'filter0.tdb' Apr 26 10:55:20 192.168.122.209 [67871.566183] [tempesta fw] modules are stopped Apr 26 10:55:21 192.168.122.209 [67871.798289] [tempesta fw] exiting... Apr 26 10:55:21 192.168.122.209 [67871.931621] [tdb] Shutdown Tempesta DB Apr 26 10:55:21 192.168.122.209 [67872.117515] End test: t_reconf.test_reconf_base.TestVhostReconf.test_remove_vhost Apr 26 10:55:21 192.168.122.209 [67872.130069] Start test: t_reconf.test_stress_grace_shutdown.TestGraceShutdownLiveReconf.test_reconf_on_the_fly_for_grace_shutdown Apr 26 10:55:22 192.168.122.209 [67873.313439] [tdb] Start Tempesta DB Apr 26 10:55:22 192.168.122.209 [67873.442122] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:55:24 192.168.122.209 [67875.235261] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67875.235261] Maybe that's fine, but it's worth checking the [67875.235261] config - if there is no relations between the [67875.235261] names, then host name confusion attack is possible. Apr 26 10:55:24 192.168.122.209 [67875.513644] [tempesta fw] Configuration processing is completed. Apr 26 10:55:24 192.168.122.209 [67875.564077] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:55:24 192.168.122.209 [67875.591334] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:55:24 192.168.122.209 [67875.618226] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:55:25 192.168.122.209 [67875.717674] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 10:55:25 192.168.122.209 [67875.761612] [tempesta fw] Tempesta FW is ready Apr 26 10:55:25 192.168.122.209 [67876.188560] [tempesta fw] Warning: frang: max rmisses exceeded for 127.0.0.1: 2 (lim=1) Apr 26 10:55:25 192.168.122.209 [67876.190570] [tempesta fw] Warning: frang: max rmisses exceeded for 127.0.0.1: 2 (lim=1) Apr 26 10:55:25 192.168.122.209 [67876.191932] [tempesta fw] Warning: frang: max rmisses exceeded for 127.0.0.1: 2 (lim=1) Apr 26 10:55:25 192.168.122.209 [67876.192665] [tempesta fw] Warning: frang: max rmisses exceeded for 127.0.0.1: 2 (lim=1) Apr 26 10:55:25 192.168.122.209 [67876.193387] [tempesta fw] Warning: frang: max rmisses exceeded for 127.0.0.1: 2 (lim=1) Apr 26 10:55:25 192.168.122.209 [67876.194824] [tempesta fw] Warning: frang: max rmisses exceeded for 127.0.0.1: 2 (lim=1) Apr 26 10:55:25 192.168.122.209 [67876.195754] [tempesta fw] Warning: frang: max rmisses exceeded for 127.0.0.1: 2 (lim=1) Apr 26 10:55:25 192.168.122.209 [67876.197128] [tempesta fw] Warning: frang: max rmisses exceeded for 127.0.0.1: 2 (lim=1) Apr 26 10:55:25 192.168.122.209 [67876.198456] [tempesta fw] Warning: frang: max rmisses exceeded for 127.0.0.1: 2 (lim=1) Apr 26 10:55:25 192.168.122.209 [67876.199314] [tempesta fw] Warning: frang: max rmisses exceeded for 127.0.0.1: 2 (lim=1) Apr 26 10:55:26 192.168.122.209 [67876.908791] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:55:26 192.168.122.209 [67876.934355] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67876.934355] Maybe that's fine, but it's worth checking the [67876.934355] config - if there is no relations between the [67876.934355] names, then host name confusion attack is possible. Apr 26 10:55:26 192.168.122.209 [67877.169677] [tempesta fw] Configuration processing is completed. Apr 26 10:55:26 192.168.122.209 [67877.345621] [tempesta fw] Tempesta FW is ready Apr 26 10:55:36 192.168.122.209 [67886.689008] [tdb] Close table 'client0.tdb' Apr 26 10:55:36 192.168.122.209 [67886.871417] [tdb] Close table 'sessions0.tdb' Apr 26 10:55:36 192.168.122.209 [67887.111102] [tdb] Close table 'filter0.tdb' Apr 26 10:55:36 192.168.122.209 [67887.111532] [tempesta fw] modules are stopped Apr 26 10:55:36 192.168.122.209 [67887.321661] [tempesta fw] exiting... Apr 26 10:55:36 192.168.122.209 [67887.438100] [tdb] Shutdown Tempesta DB Apr 26 10:55:37 192.168.122.209 [67887.684663] End test: t_reconf.test_stress_grace_shutdown.TestGraceShutdownLiveReconf.test_reconf_on_the_fly_for_grace_shutdown Apr 26 10:55:37 192.168.122.209 [67887.694904] Start test: t_reconf.test_stress_reconf.TestLiveReconf.test_stress_reconfig_on_the_fly Apr 26 10:55:38 192.168.122.209 [67888.717947] [tdb] Start Tempesta DB Apr 26 10:55:38 192.168.122.209 [67888.848709] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:55:38 192.168.122.209 [67889.459431] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67889.459431] Maybe that's fine, but it's worth checking the [67889.459431] config - if there is no relations between the [67889.459431] names, then host name confusion attack is possible. Apr 26 10:55:38 192.168.122.209 [67889.605909] [tempesta fw] Configuration processing is completed. Apr 26 10:55:38 192.168.122.209 [67889.658544] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:55:39 192.168.122.209 [67889.688338] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:55:39 192.168.122.209 [67889.716403] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:55:39 192.168.122.209 [67889.761909] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 10:55:39 192.168.122.209 [67889.801831] [tempesta fw] Tempesta FW is ready Apr 26 10:55:39 192.168.122.209 [67890.448220] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:55:39 192.168.122.209 [67890.506275] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67890.506275] Maybe that's fine, but it's worth checking the [67890.506275] config - if there is no relations between the [67890.506275] names, then host name confusion attack is possible. Apr 26 10:55:40 192.168.122.209 [67890.669827] [tempesta fw] Configuration processing is completed. Apr 26 10:55:40 192.168.122.209 [67890.813771] [tempesta fw] Warning: request dropped: unable to find an available back end server, status 502: 127.0.0.1 Apr 26 10:55:40 192.168.122.209 [67890.813780] [tempesta fw] Warning: request dropped: unable to find an available back end server, status 502: 127.0.0.1 Apr 26 10:55:40 192.168.122.209 [67890.813809] [tempesta fw] Warning: request dropped: unable to find an available back end server, status 502: 127.0.0.1 Apr 26 10:55:40 192.168.122.209 [67891.142100] [tempesta fw] Tempesta FW is ready Apr 26 10:55:49 192.168.122.209 [67900.478039] [tdb] Close table 'client0.tdb' Apr 26 10:55:50 192.168.122.209 [67900.668305] [tdb] Close table 'sessions0.tdb' Apr 26 10:55:50 192.168.122.209 [67900.892442] [tdb] Close table 'filter0.tdb' Apr 26 10:55:50 192.168.122.209 [67900.892875] [tempesta fw] modules are stopped Apr 26 10:55:50 192.168.122.209 [67901.063439] [tempesta fw] exiting... Apr 26 10:55:50 192.168.122.209 [67901.211339] [tdb] Shutdown Tempesta DB Apr 26 10:55:50 192.168.122.209 [67901.412164] End test: t_reconf.test_stress_reconf.TestLiveReconf.test_stress_reconfig_on_the_fly Apr 26 10:55:50 192.168.122.209 [67901.424448] Start test: t_reconf.test_stress_sched_dynamic.TestSchedRatioDynamicLiveReconf.test_reconf_on_the_fly_for_dynamic_ratio_sched Apr 26 10:55:52 192.168.122.209 [67903.612521] [tdb] Start Tempesta DB Apr 26 10:55:53 192.168.122.209 [67903.752876] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:55:53 192.168.122.209 [67904.579650] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67904.579650] Maybe that's fine, but it's worth checking the [67904.579650] config - if there is no relations between the [67904.579650] names, then host name confusion attack is possible. Apr 26 10:55:54 192.168.122.209 [67904.922099] [tempesta fw] Configuration processing is completed. Apr 26 10:55:54 192.168.122.209 [67904.978972] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:55:54 192.168.122.209 [67905.017515] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:55:54 192.168.122.209 [67905.046772] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:55:54 192.168.122.209 [67905.298113] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:55:54 192.168.122.209 [67905.390060] [tempesta fw] Tempesta FW is ready Apr 26 10:56:05 192.168.122.209 [67915.839404] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:05 192.168.122.209 [67915.840252] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:06 192.168.122.209 [67916.706005] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:56:06 192.168.122.209 [67916.734871] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67916.734871] Maybe that's fine, but it's worth checking the [67916.734871] config - if there is no relations between the [67916.734871] names, then host name confusion attack is possible. Apr 26 10:56:06 192.168.122.209 [67917.258258] [tempesta fw] Configuration processing is completed. Apr 26 10:56:07 192.168.122.209 [67917.966665] [tempesta fw] Tempesta FW is ready Apr 26 10:56:18 192.168.122.209 [67929.112525] [tdb] Close table 'client0.tdb' Apr 26 10:56:18 192.168.122.209 [67929.302217] [tdb] Close table 'sessions0.tdb' Apr 26 10:56:18 192.168.122.209 [67929.552830] [tdb] Close table 'filter0.tdb' Apr 26 10:56:18 192.168.122.209 [67929.553283] [tempesta fw] modules are stopped Apr 26 10:56:19 192.168.122.209 [67929.823095] [tempesta fw] exiting... Apr 26 10:56:19 192.168.122.209 [67929.976689] [tdb] Shutdown Tempesta DB Apr 26 10:56:19 192.168.122.209 [67930.396914] End test: t_reconf.test_stress_sched_dynamic.TestSchedRatioDynamicLiveReconf.test_reconf_on_the_fly_for_dynamic_ratio_sched Apr 26 10:56:19 192.168.122.209 [67930.412305] Start test: t_reconf.test_stress_sched_hash.TestSchedHashLiveReconf.test_reconf_on_the_fly_for_hash_sched Apr 26 10:56:22 192.168.122.209 [67932.717183] [tdb] Start Tempesta DB Apr 26 10:56:22 192.168.122.209 [67932.854212] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:56:23 192.168.122.209 [67933.675335] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67933.675335] Maybe that's fine, but it's worth checking the [67933.675335] config - if there is no relations between the [67933.675335] names, then host name confusion attack is possible. Apr 26 10:56:23 192.168.122.209 [67934.002515] [tempesta fw] Configuration processing is completed. Apr 26 10:56:23 192.168.122.209 [67934.053687] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:56:23 192.168.122.209 [67934.081487] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:56:23 192.168.122.209 [67934.110014] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:56:23 192.168.122.209 [67934.406561] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 10:56:23 192.168.122.209 [67934.446404] [tempesta fw] Tempesta FW is ready Apr 26 10:56:33 192.168.122.209 [67944.633222] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:33 192.168.122.209 [67944.633817] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:33 192.168.122.209 [67944.634636] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:33 192.168.122.209 [67944.635190] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:33 192.168.122.209 [67944.635969] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:33 192.168.122.209 [67944.636517] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:33 192.168.122.209 [67944.637299] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:33 192.168.122.209 [67944.637845] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:33 192.168.122.209 [67944.638707] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:33 192.168.122.209 [67944.639261] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:33 192.168.122.209 [67944.640045] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:33 192.168.122.209 [67944.640599] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:33 192.168.122.209 [67944.641388] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:33 192.168.122.209 [67944.641935] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:33 192.168.122.209 [67944.642784] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:33 192.168.122.209 [67944.643340] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:33 192.168.122.209 [67944.644143] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:33 192.168.122.209 [67944.644697] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:33 192.168.122.209 [67944.645513] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:33 192.168.122.209 [67944.646056] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:33 192.168.122.209 [67944.646880] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:33 192.168.122.209 [67944.647435] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:33 192.168.122.209 [67944.648307] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:33 192.168.122.209 [67944.648847] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:33 192.168.122.209 [67944.649644] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:33 192.168.122.209 [67944.650196] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:33 192.168.122.209 [67944.650983] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:33 192.168.122.209 [67944.651540] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.660738] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.661347] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.662163] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.662801] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.663631] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.664192] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.664982] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.665554] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.666424] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.667031] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.667838] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.668402] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.672913] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.673487] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.674274] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.674838] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.675626] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.676186] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.676959] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.677525] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.678352] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.678918] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.679763] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.680326] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.681146] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.681692] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.682524] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.683073] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.683889] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.684445] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.685256] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.685818] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.686652] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.687205] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.687990] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.688603] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.689396] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.689941] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.690801] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.691358] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.692132] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.692678] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.693467] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.694013] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.694883] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.695453] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.696247] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.696788] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.697598] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.698170] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.698990] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.699545] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.700321] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.700862] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.701719] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.702276] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.703072] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.703648] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.704443] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.704988] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.705769] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.706330] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.707151] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.707701] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.708486] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.709033] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.709815] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.710373] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.711181] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.711735] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.712534] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.713095] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.713944] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.714535] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.715341] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.715888] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.716675] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.717223] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.718006] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.718579] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.719365] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.719917] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.720765] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.721345] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.722126] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.722695] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.723478] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.724020] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.724830] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.725388] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.726176] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.726740] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.727525] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.728067] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.728881] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.729439] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.730220] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.730781] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.731572] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.732139] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.732946] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.733498] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.734294] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.734862] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.735643] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.736211] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.736999] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.737557] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.738340] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.738905] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.739693] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.740256] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.741032] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.741583] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.742371] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.742936] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.743772] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.744323] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.745122] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.745686] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.746509] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.747064] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.747858] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.748412] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.749196] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.749738] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.750552] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.751113] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.751893] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.752497] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.753301] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.753847] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.754671] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.755251] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.756036] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.756604] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.757388] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.757935] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.758748] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.759302] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.760073] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.760621] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.761410] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.761956] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.762885] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.763525] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.764376] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.764942] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.765769] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.766327] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.767189] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.767738] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.768523] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.769071] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.769903] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.770545] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.776359] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.776918] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.777702] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.778262] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.782587] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.783175] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.783977] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.784532] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.785349] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.785895] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.786722] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.787285] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.788122] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.788674] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.789504] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.790051] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.790978] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.791531] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.792370] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.792915] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.793823] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.794380] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.795234] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.795787] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.796623] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.797195] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.798049] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.798627] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.799493] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.800044] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.800904] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.801460] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.802282] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.802853] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.803778] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.804333] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.805161] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.805706] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.806633] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.807242] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.808112] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.808667] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.809503] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.810053] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.810922] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.811526] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.812371] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.812916] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.813801] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.814356] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.815280] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.815838] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.816745] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.817310] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.818198] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.818764] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.819653] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.820216] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.821040] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.821591] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:34 192.168.122.209 [67944.822435] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:34 192.168.122.209 [67944.823012] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:35 192.168.122.209 [67945.713793] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:56:35 192.168.122.209 [67945.739896] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67945.739896] Maybe that's fine, but it's worth checking the [67945.739896] config - if there is no relations between the [67945.739896] names, then host name confusion attack is possible. Apr 26 10:56:35 192.168.122.209 [67946.124956] [tempesta fw] Configuration processing is completed. Apr 26 10:56:36 192.168.122.209 [67946.803093] [tempesta fw] Tempesta FW is ready Apr 26 10:56:46 192.168.122.209 [67956.993765] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:56:46 192.168.122.209 [67956.994392] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:56:47 192.168.122.209 [67958.172144] [tdb] Close table 'client0.tdb' Apr 26 10:56:47 192.168.122.209 [67958.414749] [tdb] Close table 'sessions0.tdb' Apr 26 10:56:48 192.168.122.209 [67958.716523] [tdb] Close table 'filter0.tdb' Apr 26 10:56:48 192.168.122.209 [67958.717004] [tempesta fw] modules are stopped Apr 26 10:56:48 192.168.122.209 [67958.893244] [tempesta fw] exiting... Apr 26 10:56:48 192.168.122.209 [67959.007287] [tdb] Shutdown Tempesta DB Apr 26 10:56:48 192.168.122.209 [67959.524756] End test: t_reconf.test_stress_sched_hash.TestSchedHashLiveReconf.test_reconf_on_the_fly_for_hash_sched Apr 26 10:56:48 192.168.122.209 [67959.538808] Start test: t_reconf.test_stress_sched_http.TestSchedHttpLiveReconf.test_reconfig_on_the_fly_for_sched_http Apr 26 10:56:50 192.168.122.209 [67960.980136] [tdb] Start Tempesta DB Apr 26 10:56:50 192.168.122.209 [67961.195822] net_ratelimit: 988 callbacks suppressed Apr 26 10:56:50 192.168.122.209 [67961.195824] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:56:51 192.168.122.209 [67962.244259] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67962.244259] Maybe that's fine, but it's worth checking the [67962.244259] config - if there is no relations between the [67962.244259] names, then host name confusion attack is possible. Apr 26 10:56:51 192.168.122.209 [67962.378987] [tempesta fw] Configuration processing is completed. Apr 26 10:56:51 192.168.122.209 [67962.450944] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:56:51 192.168.122.209 [67962.493504] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:56:51 192.168.122.209 [67962.542986] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:56:52 192.168.122.209 [67962.663107] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 10:56:52 192.168.122.209 [67962.710906] [tempesta fw] Tempesta FW is ready Apr 26 10:56:52 192.168.122.209 [67963.199095] [tempesta fw] Warning: request has been filtered out via http table: 127.0.0.1 Apr 26 10:56:53 192.168.122.209 [67963.891338] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:56:53 192.168.122.209 [67964.071758] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67964.071758] Maybe that's fine, but it's worth checking the [67964.071758] config - if there is no relations between the [67964.071758] names, then host name confusion attack is possible. Apr 26 10:56:53 192.168.122.209 [67964.310822] [tempesta fw] Configuration processing is completed. Apr 26 10:56:54 192.168.122.209 [67964.750920] [tempesta fw] Tempesta FW is ready Apr 26 10:57:02 192.168.122.209 [67973.462834] [tdb] Close table 'client0.tdb' Apr 26 10:57:03 192.168.122.209 [67973.672329] [tdb] Close table 'sessions0.tdb' Apr 26 10:57:03 192.168.122.209 [67973.894766] [tdb] Close table 'filter0.tdb' Apr 26 10:57:03 192.168.122.209 [67973.895215] [tempesta fw] modules are stopped Apr 26 10:57:03 192.168.122.209 [67974.148836] [tempesta fw] exiting... Apr 26 10:57:03 192.168.122.209 [67974.295090] [tdb] Shutdown Tempesta DB Apr 26 10:57:03 192.168.122.209 [67974.512580] End test: t_reconf.test_stress_sched_http.TestSchedHttpLiveReconf.test_reconfig_on_the_fly_for_sched_http Apr 26 10:57:03 192.168.122.209 [67974.528231] Start test: t_reconf.test_stress_sched_ratio.TestSchedRatioLiveReconf.test_reconf_on_the_fly_for_static_ratio_sched Apr 26 10:57:05 192.168.122.209 [67975.737410] [tdb] Start Tempesta DB Apr 26 10:57:05 192.168.122.209 [67975.863140] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:57:05 192.168.122.209 [67976.544717] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67976.544717] Maybe that's fine, but it's worth checking the [67976.544717] config - if there is no relations between the [67976.544717] names, then host name confusion attack is possible. Apr 26 10:57:06 192.168.122.209 [67976.719158] [tempesta fw] Configuration processing is completed. Apr 26 10:57:06 192.168.122.209 [67976.771563] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:57:06 192.168.122.209 [67976.798589] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:57:06 192.168.122.209 [67976.825601] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:57:06 192.168.122.209 [67976.947161] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 10:57:06 192.168.122.209 [67976.999121] [tempesta fw] Tempesta FW is ready Apr 26 10:57:17 192.168.122.209 [67987.765070] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:57:17 192.168.122.209 [67987.811862] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [67987.811862] Maybe that's fine, but it's worth checking the [67987.811862] config - if there is no relations between the [67987.811862] names, then host name confusion attack is possible. Apr 26 10:57:17 192.168.122.209 [67987.975285] [tempesta fw] Configuration processing is completed. Apr 26 10:57:17 192.168.122.209 [67988.235284] [tempesta fw] Tempesta FW is ready Apr 26 10:57:28 192.168.122.209 [67998.907808] [tdb] Close table 'client0.tdb' Apr 26 10:57:28 192.168.122.209 [67999.090421] [tdb] Close table 'sessions0.tdb' Apr 26 10:57:28 192.168.122.209 [67999.325531] [tdb] Close table 'filter0.tdb' Apr 26 10:57:28 192.168.122.209 [67999.325980] [tempesta fw] modules are stopped Apr 26 10:57:28 192.168.122.209 [67999.554781] [tempesta fw] exiting... Apr 26 10:57:29 192.168.122.209 [67999.680978] [tdb] Shutdown Tempesta DB Apr 26 10:57:29 192.168.122.209 [67999.937269] End test: t_reconf.test_stress_sched_ratio.TestSchedRatioLiveReconf.test_reconf_on_the_fly_for_static_ratio_sched Apr 26 10:57:29 192.168.122.209 [67999.951239] Start test: t_reconf.test_stress_sticky.TestGraceShutdownLiveReconf.test_reconf_on_the_fly_for_sticky_cookie_sched Apr 26 10:57:30 192.168.122.209 [68001.410736] [tdb] Start Tempesta DB Apr 26 10:57:30 192.168.122.209 [68001.567397] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:57:31 192.168.122.209 [68002.625236] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68002.625236] Maybe that's fine, but it's worth checking the [68002.625236] config - if there is no relations between the [68002.625236] names, then host name confusion attack is possible. Apr 26 10:57:32 192.168.122.209 [68002.855514] [tempesta fw] Configuration processing is completed. Apr 26 10:57:32 192.168.122.209 [68002.916474] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:57:32 192.168.122.209 [68002.950594] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:57:32 192.168.122.209 [68002.980895] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:57:32 192.168.122.209 [68003.087537] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 10:57:32 192.168.122.209 [68003.147465] [tempesta fw] Tempesta FW is ready Apr 26 10:57:39 192.168.122.209 [68010.052279] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 10:57:39 192.168.122.209 [68010.278608] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68010.278608] Maybe that's fine, but it's worth checking the [68010.278608] config - if there is no relations between the [68010.278608] names, then host name confusion attack is possible. Apr 26 10:57:41 192.168.122.209 [68012.139723] [tempesta fw] Configuration processing is completed. Apr 26 10:57:42 192.168.122.209 [68012.665404] [tempesta fw] Warning: request dropped: unable to find an available back end server, status 502: 127.0.0.1 Apr 26 10:57:42 192.168.122.209 [68012.665472] [tempesta fw] Warning: request dropped: unable to find an available back end server, status 502: 127.0.0.1 Apr 26 10:57:42 192.168.122.209 [68012.665658] [tempesta fw] Warning: request dropped: unable to find an available back end server, status 502: 127.0.0.1 Apr 26 10:57:42 192.168.122.209 [68013.320067] [tempesta fw] Warning: frang: max rmisses exceeded for 127.0.0.1: 2 (lim=1) Apr 26 10:57:42 192.168.122.209 [68013.322164] [tempesta fw] Warning: frang: max rmisses exceeded for 127.0.0.1: 2 (lim=1) Apr 26 10:57:42 192.168.122.209 [68013.328936] [tempesta fw] Warning: frang: max rmisses exceeded for 127.0.0.1: 2 (lim=1) Apr 26 10:57:42 192.168.122.209 [68013.331399] [tempesta fw] Warning: frang: max rmisses exceeded for 127.0.0.1: 2 (lim=1) Apr 26 10:57:42 192.168.122.209 [68013.343864] [tempesta fw] Tempesta FW is ready Apr 26 10:57:43 192.168.122.209 [68014.265513] [tdb] Close table 'client0.tdb' Apr 26 10:57:43 192.168.122.209 [68014.498869] [tdb] Close table 'sessions0.tdb' Apr 26 10:57:44 192.168.122.209 [68014.762286] [tdb] Close table 'filter0.tdb' Apr 26 10:57:44 192.168.122.209 [68014.762775] [tempesta fw] modules are stopped Apr 26 10:57:44 192.168.122.209 [68014.989657] [tempesta fw] exiting... Apr 26 10:57:44 192.168.122.209 [68015.145086] [tdb] Shutdown Tempesta DB Apr 26 10:57:44 192.168.122.209 [68015.465847] End test: t_reconf.test_stress_sticky.TestGraceShutdownLiveReconf.test_reconf_on_the_fly_for_sticky_cookie_sched Apr 26 10:57:44 192.168.122.209 [68015.483328] Start test: t_regress.test_reboot_under_load.TestRebootUnderLoadNoTimeoutTfwNoCache.test_reboot_under_load Apr 26 10:57:46 192.168.122.209 [68016.695053] [tdb] Start Tempesta DB Apr 26 10:57:46 192.168.122.209 [68016.880297] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:57:46 192.168.122.209 [68017.625256] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68017.625256] Maybe that's fine, but it's worth checking the [68017.625256] config - if there is no relations between the [68017.625256] names, then host name confusion attack is possible. Apr 26 10:57:47 192.168.122.209 [68017.791755] [tempesta fw] Configuration processing is completed. Apr 26 10:57:47 192.168.122.209 [68017.843800] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:57:47 192.168.122.209 [68017.873560] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:57:47 192.168.122.209 [68017.905219] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:57:47 192.168.122.209 [68017.951737] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 10:57:47 192.168.122.209 [68017.995675] [tempesta fw] Tempesta FW is ready Apr 26 10:57:52 192.168.122.209 [68023.631272] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:57:52 192.168.122.209 [68023.631859] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:57:52 192.168.122.209 [68023.633080] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 10:57:52 192.168.122.209 [68023.633645] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 10:57:53 192.168.122.209 [68023.917013] [tdb] Close table 'client0.tdb' Apr 26 10:57:53 192.168.122.209 [68024.104685] [tdb] Close table 'sessions0.tdb' Apr 26 10:57:53 192.168.122.209 [68024.329429] [tdb] Close table 'filter0.tdb' Apr 26 10:57:53 192.168.122.209 [68024.329845] [tempesta fw] modules are stopped Apr 26 10:57:53 192.168.122.209 [68024.535509] [tempesta fw] exiting... Apr 26 10:57:54 192.168.122.209 [68024.685432] [tdb] Shutdown Tempesta DB Apr 26 10:57:55 192.168.122.209 [68025.845722] [tdb] Start Tempesta DB Apr 26 10:57:55 192.168.122.209 [68025.975625] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:57:55 192.168.122.209 [68026.604283] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68026.604283] Maybe that's fine, but it's worth checking the [68026.604283] config - if there is no relations between the [68026.604283] names, then host name confusion attack is possible. Apr 26 10:57:56 192.168.122.209 [68026.815948] [tempesta fw] Configuration processing is completed. Apr 26 10:57:56 192.168.122.209 [68026.881381] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:57:56 192.168.122.209 [68026.917938] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:57:56 192.168.122.209 [68026.956238] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:57:56 192.168.122.209 [68027.040011] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 10:57:56 192.168.122.209 [68027.103823] [tempesta fw] Tempesta FW is ready Apr 26 10:57:56 192.168.122.209 [68027.628861] [tdb] Close table 'client0.tdb' Apr 26 10:57:57 192.168.122.209 [68027.818309] [tdb] Close table 'sessions0.tdb' Apr 26 10:57:57 192.168.122.209 [68028.039607] [tdb] Close table 'filter0.tdb' Apr 26 10:57:57 192.168.122.209 [68028.040082] [tempesta fw] modules are stopped Apr 26 10:57:57 192.168.122.209 [68028.323868] [tempesta fw] exiting... Apr 26 10:57:57 192.168.122.209 [68028.466489] [tdb] Shutdown Tempesta DB Apr 26 10:57:58 192.168.122.209 [68029.655837] [tdb] Start Tempesta DB Apr 26 10:57:59 192.168.122.209 [68029.795896] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:57:59 192.168.122.209 [68030.436193] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68030.436193] Maybe that's fine, but it's worth checking the [68030.436193] config - if there is no relations between the [68030.436193] names, then host name confusion attack is possible. Apr 26 10:57:59 192.168.122.209 [68030.615910] [tempesta fw] Configuration processing is completed. Apr 26 10:58:00 192.168.122.209 [68030.667265] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:58:00 192.168.122.209 [68030.695661] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:58:00 192.168.122.209 [68030.723932] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:58:00 192.168.122.209 [68030.800019] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 10:58:00 192.168.122.209 [68030.859853] [tempesta fw] Tempesta FW is ready Apr 26 10:58:00 192.168.122.209 [68031.431382] [tdb] Close table 'client0.tdb' Apr 26 10:58:00 192.168.122.209 [68031.608998] [tdb] Close table 'sessions0.tdb' Apr 26 10:58:01 192.168.122.209 [68031.835973] [tdb] Close table 'filter0.tdb' Apr 26 10:58:01 192.168.122.209 [68031.836392] [tempesta fw] modules are stopped Apr 26 10:58:01 192.168.122.209 [68032.078346] [tempesta fw] exiting... Apr 26 10:58:01 192.168.122.209 [68032.190028] [tdb] Shutdown Tempesta DB Apr 26 10:58:02 192.168.122.209 [68033.365146] [tdb] Start Tempesta DB Apr 26 10:58:02 192.168.122.209 [68033.504401] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:58:03 192.168.122.209 [68034.117136] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68034.117136] Maybe that's fine, but it's worth checking the [68034.117136] config - if there is no relations between the [68034.117136] names, then host name confusion attack is possible. Apr 26 10:58:03 192.168.122.209 [68034.283946] [tempesta fw] Configuration processing is completed. Apr 26 10:58:03 192.168.122.209 [68034.334204] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:58:03 192.168.122.209 [68034.361260] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:58:03 192.168.122.209 [68034.388857] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:58:03 192.168.122.209 [68034.479981] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 10:58:03 192.168.122.209 [68034.539862] [tempesta fw] Tempesta FW is ready Apr 26 10:58:04 192.168.122.209 [68035.076988] [tdb] Close table 'client0.tdb' Apr 26 10:58:04 192.168.122.209 [68035.279734] [tdb] Close table 'sessions0.tdb' Apr 26 10:58:04 192.168.122.209 [68035.530509] [tdb] Close table 'filter0.tdb' Apr 26 10:58:04 192.168.122.209 [68035.530941] [tempesta fw] modules are stopped Apr 26 10:58:05 192.168.122.209 [68035.757537] [tempesta fw] exiting... Apr 26 10:58:05 192.168.122.209 [68035.861549] [tdb] Shutdown Tempesta DB Apr 26 10:58:06 192.168.122.209 [68036.931002] [tdb] Start Tempesta DB Apr 26 10:58:06 192.168.122.209 [68037.063059] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:58:07 192.168.122.209 [68037.717344] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68037.717344] Maybe that's fine, but it's worth checking the [68037.717344] config - if there is no relations between the [68037.717344] names, then host name confusion attack is possible. Apr 26 10:58:07 192.168.122.209 [68037.904076] [tempesta fw] Configuration processing is completed. Apr 26 10:58:07 192.168.122.209 [68037.968763] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:58:07 192.168.122.209 [68038.006772] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:58:07 192.168.122.209 [68038.043709] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:58:07 192.168.122.209 [68038.108011] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 10:58:07 192.168.122.209 [68038.163927] [tempesta fw] Tempesta FW is ready Apr 26 10:58:08 192.168.122.209 [68038.674280] [tdb] Close table 'client0.tdb' Apr 26 10:58:08 192.168.122.209 [68038.882460] [tdb] Close table 'sessions0.tdb' Apr 26 10:58:08 192.168.122.209 [68039.104618] [tdb] Close table 'filter0.tdb' Apr 26 10:58:08 192.168.122.209 [68039.105063] [tempesta fw] modules are stopped Apr 26 10:58:08 192.168.122.209 [68039.303326] [tempesta fw] exiting... Apr 26 10:58:08 192.168.122.209 [68039.431829] [tdb] Shutdown Tempesta DB Apr 26 10:58:09 192.168.122.209 [68040.459384] [tdb] Start Tempesta DB Apr 26 10:58:09 192.168.122.209 [68040.595570] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:58:10 192.168.122.209 [68041.284678] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68041.284678] Maybe that's fine, but it's worth checking the [68041.284678] config - if there is no relations between the [68041.284678] names, then host name confusion attack is possible. Apr 26 10:58:10 192.168.122.209 [68041.476043] [tempesta fw] Configuration processing is completed. Apr 26 10:58:10 192.168.122.209 [68041.531991] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:58:10 192.168.122.209 [68041.561434] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:58:10 192.168.122.209 [68041.591789] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:58:10 192.168.122.209 [68041.660080] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 10:58:11 192.168.122.209 [68041.723952] [tempesta fw] Tempesta FW is ready Apr 26 10:58:11 192.168.122.209 [68042.238440] [tdb] Close table 'client0.tdb' Apr 26 10:58:11 192.168.122.209 [68042.418083] [tdb] Close table 'sessions0.tdb' Apr 26 10:58:11 192.168.122.209 [68042.630572] [tdb] Close table 'filter0.tdb' Apr 26 10:58:11 192.168.122.209 [68042.630983] [tempesta fw] modules are stopped Apr 26 10:58:12 192.168.122.209 [68042.825529] [tempesta fw] exiting... Apr 26 10:58:12 192.168.122.209 [68042.945001] [tdb] Shutdown Tempesta DB Apr 26 10:58:13 192.168.122.209 [68044.060299] [tdb] Start Tempesta DB Apr 26 10:58:13 192.168.122.209 [68044.214401] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:58:14 192.168.122.209 [68044.841304] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68044.841304] Maybe that's fine, but it's worth checking the [68044.841304] config - if there is no relations between the [68044.841304] names, then host name confusion attack is possible. Apr 26 10:58:14 192.168.122.209 [68045.036116] [tempesta fw] Configuration processing is completed. Apr 26 10:58:14 192.168.122.209 [68045.086733] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:58:14 192.168.122.209 [68045.114479] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:58:14 192.168.122.209 [68045.142983] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:58:14 192.168.122.209 [68045.236106] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 10:58:14 192.168.122.209 [68045.308058] [tempesta fw] Tempesta FW is ready Apr 26 10:58:15 192.168.122.209 [68045.814677] [tdb] Close table 'client0.tdb' Apr 26 10:58:15 192.168.122.209 [68046.010926] [tdb] Close table 'sessions0.tdb' Apr 26 10:58:15 192.168.122.209 [68046.250257] [tdb] Close table 'filter0.tdb' Apr 26 10:58:15 192.168.122.209 [68046.250694] [tempesta fw] modules are stopped Apr 26 10:58:15 192.168.122.209 [68046.452228] [tempesta fw] exiting... Apr 26 10:58:15 192.168.122.209 [68046.584161] [tdb] Shutdown Tempesta DB Apr 26 10:58:16 192.168.122.209 [68047.613134] [tdb] Start Tempesta DB Apr 26 10:58:17 192.168.122.209 [68047.746410] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:58:17 192.168.122.209 [68048.328794] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68048.328794] Maybe that's fine, but it's worth checking the [68048.328794] config - if there is no relations between the [68048.328794] names, then host name confusion attack is possible. Apr 26 10:58:17 192.168.122.209 [68048.508162] [tempesta fw] Configuration processing is completed. Apr 26 10:58:17 192.168.122.209 [68048.559557] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:58:17 192.168.122.209 [68048.587779] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:58:17 192.168.122.209 [68048.615805] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:58:18 192.168.122.209 [68048.692171] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 10:58:18 192.168.122.209 [68048.756113] [tempesta fw] Tempesta FW is ready Apr 26 10:58:18 192.168.122.209 [68049.264425] [tdb] Close table 'client0.tdb' Apr 26 10:58:18 192.168.122.209 [68049.467932] [tdb] Close table 'sessions0.tdb' Apr 26 10:58:19 192.168.122.209 [68049.709196] [tdb] Close table 'filter0.tdb' Apr 26 10:58:19 192.168.122.209 [68049.709629] [tempesta fw] modules are stopped Apr 26 10:58:19 192.168.122.209 [68049.924710] [tempesta fw] exiting... Apr 26 10:58:19 192.168.122.209 [68050.037087] [tdb] Shutdown Tempesta DB Apr 26 10:58:20 192.168.122.209 [68051.208139] [tdb] Start Tempesta DB Apr 26 10:58:20 192.168.122.209 [68051.347978] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:58:21 192.168.122.209 [68051.973394] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68051.973394] Maybe that's fine, but it's worth checking the [68051.973394] config - if there is no relations between the [68051.973394] names, then host name confusion attack is possible. Apr 26 10:58:21 192.168.122.209 [68052.140554] [tempesta fw] Configuration processing is completed. Apr 26 10:58:21 192.168.122.209 [68052.198730] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:58:21 192.168.122.209 [68052.226400] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:58:21 192.168.122.209 [68052.254070] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:58:21 192.168.122.209 [68052.332213] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 10:58:21 192.168.122.209 [68052.400174] [tempesta fw] Tempesta FW is ready Apr 26 10:58:22 192.168.122.209 [68052.940332] [tdb] Close table 'client0.tdb' Apr 26 10:58:22 192.168.122.209 [68053.145865] [tdb] Close table 'sessions0.tdb' Apr 26 10:58:22 192.168.122.209 [68053.391571] [tdb] Close table 'filter0.tdb' Apr 26 10:58:22 192.168.122.209 [68053.392010] [tempesta fw] modules are stopped Apr 26 10:58:22 192.168.122.209 [68053.599028] [tempesta fw] exiting... Apr 26 10:58:23 192.168.122.209 [68053.753547] [tdb] Shutdown Tempesta DB Apr 26 10:58:24 192.168.122.209 [68054.839111] [tdb] Start Tempesta DB Apr 26 10:58:24 192.168.122.209 [68054.973048] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:58:25 192.168.122.209 [68055.657433] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68055.657433] Maybe that's fine, but it's worth checking the [68055.657433] config - if there is no relations between the [68055.657433] names, then host name confusion attack is possible. Apr 26 10:58:25 192.168.122.209 [68055.840263] [tempesta fw] Configuration processing is completed. Apr 26 10:58:25 192.168.122.209 [68055.891813] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:58:25 192.168.122.209 [68055.920669] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:58:25 192.168.122.209 [68055.948816] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:58:25 192.168.122.209 [68056.024256] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 10:58:25 192.168.122.209 [68056.084811] [tempesta fw] Tempesta FW is ready Apr 26 10:58:26 192.168.122.209 [68056.663270] [tdb] Close table 'client0.tdb' Apr 26 10:58:26 192.168.122.209 [68056.843046] [tdb] Close table 'sessions0.tdb' Apr 26 10:58:26 192.168.122.209 [68057.083631] [tdb] Close table 'filter0.tdb' Apr 26 10:58:26 192.168.122.209 [68057.084096] [tempesta fw] modules are stopped Apr 26 10:58:26 192.168.122.209 [68057.280557] [tempesta fw] exiting... Apr 26 10:58:26 192.168.122.209 [68057.385121] [tdb] Shutdown Tempesta DB Apr 26 10:58:27 192.168.122.209 [68058.489937] [tdb] Start Tempesta DB Apr 26 10:58:27 192.168.122.209 [68058.627377] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:58:28 192.168.122.209 [68059.285487] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68059.285487] Maybe that's fine, but it's worth checking the [68059.285487] config - if there is no relations between the [68059.285487] names, then host name confusion attack is possible. Apr 26 10:58:28 192.168.122.209 [68059.476266] [tempesta fw] Configuration processing is completed. Apr 26 10:58:28 192.168.122.209 [68059.528234] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:58:28 192.168.122.209 [68059.557635] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 10:58:28 192.168.122.209 [68059.586147] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 10:58:29 192.168.122.209 [68059.672306] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 10:58:29 192.168.122.209 [68059.732265] [tempesta fw] Tempesta FW is ready Apr 26 10:58:29 192.168.122.209 [68060.337212] [tdb] Close table 'client0.tdb' Apr 26 10:58:29 192.168.122.209 [68060.525681] [tdb] Close table 'sessions0.tdb' Apr 26 10:58:30 192.168.122.209 [68060.764261] [tdb] Close table 'filter0.tdb' Apr 26 10:58:30 192.168.122.209 [68060.764706] [tempesta fw] modules are stopped Apr 26 10:58:30 192.168.122.209 [68060.941306] [tempesta fw] exiting... Apr 26 10:58:30 192.168.122.209 [68061.079840] [tdb] Shutdown Tempesta DB Apr 26 10:58:30 192.168.122.209 [68061.310289] End test: t_regress.test_reboot_under_load.TestRebootUnderLoadNoTimeoutTfwNoCache.test_reboot_under_load Apr 26 10:58:30 192.168.122.209 [68061.329253] Start test: t_regress.test_reboot_under_load.TestRebootUnderLoadNoTimeoutTfwWithCache.test_reboot_under_load Apr 26 10:58:31 192.168.122.209 [68062.580724] [tdb] Start Tempesta DB Apr 26 10:58:32 192.168.122.209 [68062.725052] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:58:32 192.168.122.209 [68063.497801] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68063.497801] Maybe that's fine, but it's worth checking the [68063.497801] config - if there is no relations between the [68063.497801] names, then host name confusion attack is possible. Apr 26 10:58:33 192.168.122.209 [68063.684952] [tempesta fw] Configuration processing is completed. Apr 26 10:58:33 192.168.122.209 [68063.736252] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:58:33 192.168.122.209 [68064.398836] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:58:33 192.168.122.209 [68064.460570] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:58:33 192.168.122.209 [68064.514850] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:58:33 192.168.122.209 [68064.552398] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 10:58:33 192.168.122.209 [68064.600337] [tempesta fw] Tempesta FW is ready Apr 26 10:58:41 192.168.122.209 [68071.737371] [tdb] Close table 'client0.tdb' Apr 26 10:58:41 192.168.122.209 [68071.940330] [tdb] Close table 'sessions0.tdb' Apr 26 10:58:44 192.168.122.209 [68075.213961] [tdb] Close table 'cache0.tdb' Apr 26 10:58:44 192.168.122.209 [68075.448292] [tdb] Close table 'filter0.tdb' Apr 26 10:58:44 192.168.122.209 [68075.449905] [tempesta fw] modules are stopped Apr 26 10:58:44 192.168.122.209 [68075.654740] [tempesta fw] exiting... Apr 26 10:58:45 192.168.122.209 [68075.770169] [tdb] Shutdown Tempesta DB Apr 26 10:58:46 192.168.122.209 [68076.975098] [tdb] Start Tempesta DB Apr 26 10:58:46 192.168.122.209 [68077.134766] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:58:47 192.168.122.209 [68078.621849] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68078.621849] Maybe that's fine, but it's worth checking the [68078.621849] config - if there is no relations between the [68078.621849] names, then host name confusion attack is possible. Apr 26 10:58:48 192.168.122.209 [68078.820912] [tempesta fw] Configuration processing is completed. Apr 26 10:58:48 192.168.122.209 [68078.876560] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:58:48 192.168.122.209 [68079.419177] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:58:48 192.168.122.209 [68079.452532] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:58:48 192.168.122.209 [68079.484841] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:58:48 192.168.122.209 [68079.556753] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 10:58:48 192.168.122.209 [68079.624592] [tempesta fw] Tempesta FW is ready Apr 26 10:58:49 192.168.122.209 [68080.227337] [tdb] Close table 'client0.tdb' Apr 26 10:58:49 192.168.122.209 [68080.416848] [tdb] Close table 'sessions0.tdb' Apr 26 10:58:53 192.168.122.209 [68084.105209] [tdb] Close table 'cache0.tdb' Apr 26 10:58:54 192.168.122.209 [68084.841756] [tdb] Close table 'filter0.tdb' Apr 26 10:58:54 192.168.122.209 [68084.842228] [tempesta fw] modules are stopped Apr 26 10:58:55 192.168.122.209 [68086.216789] [tempesta fw] exiting... Apr 26 10:58:56 192.168.122.209 [68086.838110] [tdb] Shutdown Tempesta DB Apr 26 10:58:58 192.168.122.209 [68088.664440] [tdb] Start Tempesta DB Apr 26 10:58:58 192.168.122.209 [68088.826070] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:58:59 192.168.122.209 [68090.518078] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68090.518078] Maybe that's fine, but it's worth checking the [68090.518078] config - if there is no relations between the [68090.518078] names, then host name confusion attack is possible. Apr 26 10:59:00 192.168.122.209 [68090.720780] [tempesta fw] Configuration processing is completed. Apr 26 10:59:00 192.168.122.209 [68090.773224] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:59:00 192.168.122.209 [68091.206427] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:59:00 192.168.122.209 [68091.233692] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:59:00 192.168.122.209 [68091.262681] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:59:00 192.168.122.209 [68091.336830] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 10:59:00 192.168.122.209 [68091.380737] [tempesta fw] Tempesta FW is ready Apr 26 10:59:01 192.168.122.209 [68091.917305] [tdb] Close table 'client0.tdb' Apr 26 10:59:01 192.168.122.209 [68092.118819] [tdb] Close table 'sessions0.tdb' Apr 26 10:59:04 192.168.122.209 [68095.319823] [tdb] Close table 'cache0.tdb' Apr 26 10:59:04 192.168.122.209 [68095.572365] [tdb] Close table 'filter0.tdb' Apr 26 10:59:04 192.168.122.209 [68095.572800] [tempesta fw] modules are stopped Apr 26 10:59:05 192.168.122.209 [68095.770660] [tempesta fw] exiting... Apr 26 10:59:05 192.168.122.209 [68095.918045] [tdb] Shutdown Tempesta DB Apr 26 10:59:06 192.168.122.209 [68096.987309] [tdb] Start Tempesta DB Apr 26 10:59:06 192.168.122.209 [68097.127703] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:59:07 192.168.122.209 [68098.629569] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68098.629569] Maybe that's fine, but it's worth checking the [68098.629569] config - if there is no relations between the [68098.629569] names, then host name confusion attack is possible. Apr 26 10:59:08 192.168.122.209 [68098.828874] [tempesta fw] Configuration processing is completed. Apr 26 10:59:08 192.168.122.209 [68098.879017] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:59:08 192.168.122.209 [68099.298371] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:59:08 192.168.122.209 [68099.326129] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:59:08 192.168.122.209 [68099.354158] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:59:08 192.168.122.209 [68099.448879] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 10:59:08 192.168.122.209 [68099.508828] [tempesta fw] Tempesta FW is ready Apr 26 10:59:09 192.168.122.209 [68100.035972] [tdb] Close table 'client0.tdb' Apr 26 10:59:09 192.168.122.209 [68100.200805] [tdb] Close table 'sessions0.tdb' Apr 26 10:59:12 192.168.122.209 [68103.386113] [tdb] Close table 'cache0.tdb' Apr 26 10:59:12 192.168.122.209 [68103.631481] [tdb] Close table 'filter0.tdb' Apr 26 10:59:12 192.168.122.209 [68103.631910] [tempesta fw] modules are stopped Apr 26 10:59:13 192.168.122.209 [68103.886979] [tempesta fw] exiting... Apr 26 10:59:13 192.168.122.209 [68104.027731] [tdb] Shutdown Tempesta DB Apr 26 10:59:14 192.168.122.209 [68105.157673] [tdb] Start Tempesta DB Apr 26 10:59:14 192.168.122.209 [68105.297830] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:59:16 192.168.122.209 [68106.693796] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68106.693796] Maybe that's fine, but it's worth checking the [68106.693796] config - if there is no relations between the [68106.693796] names, then host name confusion attack is possible. Apr 26 10:59:16 192.168.122.209 [68106.888969] [tempesta fw] Configuration processing is completed. Apr 26 10:59:16 192.168.122.209 [68106.940496] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:59:16 192.168.122.209 [68107.346118] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:59:16 192.168.122.209 [68107.372403] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:59:16 192.168.122.209 [68107.400972] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:59:16 192.168.122.209 [68107.489000] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 10:59:16 192.168.122.209 [68107.548895] [tempesta fw] Tempesta FW is ready Apr 26 10:59:17 192.168.122.209 [68108.078007] [tdb] Close table 'client0.tdb' Apr 26 10:59:17 192.168.122.209 [68108.253512] [tdb] Close table 'sessions0.tdb' Apr 26 10:59:20 192.168.122.209 [68111.561899] [tdb] Close table 'cache0.tdb' Apr 26 10:59:21 192.168.122.209 [68111.816606] [tdb] Close table 'filter0.tdb' Apr 26 10:59:21 192.168.122.209 [68111.817143] [tempesta fw] modules are stopped Apr 26 10:59:21 192.168.122.209 [68112.011004] [tempesta fw] exiting... Apr 26 10:59:21 192.168.122.209 [68112.139356] [tdb] Shutdown Tempesta DB Apr 26 10:59:22 192.168.122.209 [68113.316889] [tdb] Start Tempesta DB Apr 26 10:59:22 192.168.122.209 [68113.486901] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:59:24 192.168.122.209 [68114.938346] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68114.938346] Maybe that's fine, but it's worth checking the [68114.938346] config - if there is no relations between the [68114.938346] names, then host name confusion attack is possible. Apr 26 10:59:24 192.168.122.209 [68115.153131] [tempesta fw] Configuration processing is completed. Apr 26 10:59:24 192.168.122.209 [68115.210629] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:59:25 192.168.122.209 [68115.768420] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:59:25 192.168.122.209 [68115.801914] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:59:25 192.168.122.209 [68115.836782] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:59:25 192.168.122.209 [68115.921141] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 10:59:25 192.168.122.209 [68115.985055] [tempesta fw] Tempesta FW is ready Apr 26 10:59:25 192.168.122.209 [68116.518192] [tdb] Close table 'client0.tdb' Apr 26 10:59:26 192.168.122.209 [68116.702530] [tdb] Close table 'sessions0.tdb' Apr 26 10:59:29 192.168.122.209 [68120.007806] [tdb] Close table 'cache0.tdb' Apr 26 10:59:29 192.168.122.209 [68120.262307] [tdb] Close table 'filter0.tdb' Apr 26 10:59:29 192.168.122.209 [68120.262737] [tempesta fw] modules are stopped Apr 26 10:59:29 192.168.122.209 [68120.457743] [tempesta fw] exiting... Apr 26 10:59:29 192.168.122.209 [68120.589275] [tdb] Shutdown Tempesta DB Apr 26 10:59:31 192.168.122.209 [68121.743564] [tdb] Start Tempesta DB Apr 26 10:59:31 192.168.122.209 [68121.870991] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:59:32 192.168.122.209 [68123.382119] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68123.382119] Maybe that's fine, but it's worth checking the [68123.382119] config - if there is no relations between the [68123.382119] names, then host name confusion attack is possible. Apr 26 10:59:32 192.168.122.209 [68123.585368] [tempesta fw] Configuration processing is completed. Apr 26 10:59:32 192.168.122.209 [68123.641173] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:59:33 192.168.122.209 [68124.058075] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:59:33 192.168.122.209 [68124.083516] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:59:33 192.168.122.209 [68124.110309] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:59:33 192.168.122.209 [68124.197330] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 10:59:33 192.168.122.209 [68124.265170] [tempesta fw] Tempesta FW is ready Apr 26 10:59:34 192.168.122.209 [68124.810855] [tdb] Close table 'client0.tdb' Apr 26 10:59:34 192.168.122.209 [68125.002777] [tdb] Close table 'sessions0.tdb' Apr 26 10:59:37 192.168.122.209 [68128.339980] [tdb] Close table 'cache0.tdb' Apr 26 10:59:37 192.168.122.209 [68128.628906] [tdb] Close table 'filter0.tdb' Apr 26 10:59:37 192.168.122.209 [68128.629352] [tempesta fw] modules are stopped Apr 26 10:59:38 192.168.122.209 [68128.854546] [tempesta fw] exiting... Apr 26 10:59:38 192.168.122.209 [68129.001133] [tdb] Shutdown Tempesta DB Apr 26 10:59:39 192.168.122.209 [68130.229832] [tdb] Start Tempesta DB Apr 26 10:59:39 192.168.122.209 [68130.378930] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:59:41 192.168.122.209 [68131.834574] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68131.834574] Maybe that's fine, but it's worth checking the [68131.834574] config - if there is no relations between the [68131.834574] names, then host name confusion attack is possible. Apr 26 10:59:41 192.168.122.209 [68132.025271] [tempesta fw] Configuration processing is completed. Apr 26 10:59:41 192.168.122.209 [68132.084691] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:59:41 192.168.122.209 [68132.643920] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:59:42 192.168.122.209 [68132.678070] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:59:42 192.168.122.209 [68132.703457] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:59:42 192.168.122.209 [68132.777398] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 10:59:42 192.168.122.209 [68132.841199] [tempesta fw] Tempesta FW is ready Apr 26 10:59:42 192.168.122.209 [68133.350970] [tdb] Close table 'client0.tdb' Apr 26 10:59:42 192.168.122.209 [68133.556528] [tdb] Close table 'sessions0.tdb' Apr 26 10:59:46 192.168.122.209 [68136.760359] [tdb] Close table 'cache0.tdb' Apr 26 10:59:46 192.168.122.209 [68137.003337] [tdb] Close table 'filter0.tdb' Apr 26 10:59:46 192.168.122.209 [68137.003759] [tempesta fw] modules are stopped Apr 26 10:59:46 192.168.122.209 [68137.246594] [tempesta fw] exiting... Apr 26 10:59:46 192.168.122.209 [68137.377592] [tdb] Shutdown Tempesta DB Apr 26 10:59:47 192.168.122.209 [68138.427361] [tdb] Start Tempesta DB Apr 26 10:59:47 192.168.122.209 [68138.558529] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:59:49 192.168.122.209 [68140.005735] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68140.005735] Maybe that's fine, but it's worth checking the [68140.005735] config - if there is no relations between the [68140.005735] names, then host name confusion attack is possible. Apr 26 10:59:49 192.168.122.209 [68140.197414] [tempesta fw] Configuration processing is completed. Apr 26 10:59:49 192.168.122.209 [68140.248024] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:59:49 192.168.122.209 [68140.657874] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:59:50 192.168.122.209 [68140.683093] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:59:50 192.168.122.209 [68140.708691] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:59:50 192.168.122.209 [68140.785538] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 10:59:50 192.168.122.209 [68140.849399] [tempesta fw] Tempesta FW is ready Apr 26 10:59:50 192.168.122.209 [68141.445222] [tdb] Close table 'client0.tdb' Apr 26 10:59:50 192.168.122.209 [68141.627112] [tdb] Close table 'sessions0.tdb' Apr 26 10:59:54 192.168.122.209 [68144.829516] [tdb] Close table 'cache0.tdb' Apr 26 10:59:54 192.168.122.209 [68145.106309] [tdb] Close table 'filter0.tdb' Apr 26 10:59:54 192.168.122.209 [68145.106755] [tempesta fw] modules are stopped Apr 26 10:59:54 192.168.122.209 [68145.335833] [tempesta fw] exiting... Apr 26 10:59:54 192.168.122.209 [68145.482889] [tdb] Shutdown Tempesta DB Apr 26 10:59:55 192.168.122.209 [68146.603596] [tdb] Start Tempesta DB Apr 26 10:59:56 192.168.122.209 [68146.742344] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 10:59:57 192.168.122.209 [68148.169778] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68148.169778] Maybe that's fine, but it's worth checking the [68148.169778] config - if there is no relations between the [68148.169778] names, then host name confusion attack is possible. Apr 26 10:59:57 192.168.122.209 [68148.329472] [tempesta fw] Configuration processing is completed. Apr 26 10:59:57 192.168.122.209 [68148.371459] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 10:59:58 192.168.122.209 [68148.783341] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 10:59:58 192.168.122.209 [68148.809473] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 10:59:58 192.168.122.209 [68148.835856] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 10:59:58 192.168.122.209 [68148.909590] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 10:59:58 192.168.122.209 [68148.981600] [tempesta fw] Tempesta FW is ready Apr 26 10:59:58 192.168.122.209 [68149.490794] [tdb] Close table 'client0.tdb' Apr 26 10:59:59 192.168.122.209 [68149.680430] [tdb] Close table 'sessions0.tdb' Apr 26 11:00:02 192.168.122.209 [68152.852179] [tdb] Close table 'cache0.tdb' Apr 26 11:00:02 192.168.122.209 [68153.118392] [tdb] Close table 'filter0.tdb' Apr 26 11:00:02 192.168.122.209 [68153.118824] [tempesta fw] modules are stopped Apr 26 11:00:02 192.168.122.209 [68153.328515] [tempesta fw] exiting... Apr 26 11:00:02 192.168.122.209 [68153.452350] [tdb] Shutdown Tempesta DB Apr 26 11:00:03 192.168.122.209 [68154.644817] [tdb] Start Tempesta DB Apr 26 11:00:04 192.168.122.209 [68154.786195] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:00:05 192.168.122.209 [68156.238300] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68156.238300] Maybe that's fine, but it's worth checking the [68156.238300] config - if there is no relations between the [68156.238300] names, then host name confusion attack is possible. Apr 26 11:00:05 192.168.122.209 [68156.441669] [tempesta fw] Configuration processing is completed. Apr 26 11:00:05 192.168.122.209 [68156.503605] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:00:06 192.168.122.209 [68156.910892] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:00:06 192.168.122.209 [68156.936024] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:00:06 192.168.122.209 [68156.960711] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:00:06 192.168.122.209 [68157.045677] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 11:00:06 192.168.122.209 [68157.097625] [tempesta fw] Tempesta FW is ready Apr 26 11:00:07 192.168.122.209 [68157.756317] [tdb] Close table 'client0.tdb' Apr 26 11:00:07 192.168.122.209 [68157.942879] [tdb] Close table 'sessions0.tdb' Apr 26 11:00:10 192.168.122.209 [68161.054392] [tdb] Close table 'cache0.tdb' Apr 26 11:00:10 192.168.122.209 [68161.324161] [tdb] Close table 'filter0.tdb' Apr 26 11:00:10 192.168.122.209 [68161.324566] [tempesta fw] modules are stopped Apr 26 11:00:10 192.168.122.209 [68161.489494] [tempesta fw] exiting... Apr 26 11:00:10 192.168.122.209 [68161.609359] [tdb] Shutdown Tempesta DB Apr 26 11:00:11 192.168.122.209 [68161.827746] End test: t_regress.test_reboot_under_load.TestRebootUnderLoadNoTimeoutTfwWithCache.test_reboot_under_load Apr 26 11:00:11 192.168.122.209 [68161.840512] Start test: t_regress.test_reboot_under_load.TestRebootUnderLoadTfwNoCache.test_reboot_under_load Apr 26 11:00:12 192.168.122.209 [68163.087733] [tdb] Start Tempesta DB Apr 26 11:00:12 192.168.122.209 [68163.214791] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:00:14 192.168.122.209 [68164.703377] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68164.703377] Maybe that's fine, but it's worth checking the [68164.703377] config - if there is no relations between the [68164.703377] names, then host name confusion attack is possible. Apr 26 11:00:14 192.168.122.209 [68164.881852] [tempesta fw] Configuration processing is completed. Apr 26 11:00:14 192.168.122.209 [68164.954257] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:00:14 192.168.122.209 [68164.995781] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:00:14 192.168.122.209 [68165.034343] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:00:14 192.168.122.209 [68165.089798] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 11:00:14 192.168.122.209 [68165.125764] [tempesta fw] Tempesta FW is ready Apr 26 11:00:24 192.168.122.209 [68175.335505] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:00:24 192.168.122.209 [68175.336460] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:00:24 192.168.122.209 [68175.337948] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:00:24 192.168.122.209 [68175.338864] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:00:25 192.168.122.209 [68176.467027] [tdb] Close table 'client0.tdb' Apr 26 11:00:25 192.168.122.209 [68176.653815] [tdb] Close table 'sessions0.tdb' Apr 26 11:00:26 192.168.122.209 [68176.873274] [tdb] Close table 'filter0.tdb' Apr 26 11:00:26 192.168.122.209 [68176.873667] [tempesta fw] modules are stopped Apr 26 11:00:26 192.168.122.209 [68177.094880] [tempesta fw] exiting... Apr 26 11:00:26 192.168.122.209 [68177.223332] [tdb] Shutdown Tempesta DB Apr 26 11:00:27 192.168.122.209 [68178.391038] [tdb] Start Tempesta DB Apr 26 11:00:27 192.168.122.209 [68178.523447] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:00:28 192.168.122.209 [68179.162365] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68179.162365] Maybe that's fine, but it's worth checking the [68179.162365] config - if there is no relations between the [68179.162365] names, then host name confusion attack is possible. Apr 26 11:00:28 192.168.122.209 [68179.321896] [tempesta fw] Configuration processing is completed. Apr 26 11:00:28 192.168.122.209 [68179.367368] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:00:28 192.168.122.209 [68179.394812] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:00:28 192.168.122.209 [68179.422899] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:00:28 192.168.122.209 [68179.509982] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 11:00:28 192.168.122.209 [68179.569934] [tempesta fw] Tempesta FW is ready Apr 26 11:00:39 192.168.122.209 [68190.138264] [tdb] Close table 'client0.tdb' Apr 26 11:00:39 192.168.122.209 [68190.319933] [tdb] Close table 'sessions0.tdb' Apr 26 11:00:39 192.168.122.209 [68190.552887] [tdb] Close table 'filter0.tdb' Apr 26 11:00:39 192.168.122.209 [68190.553306] [tempesta fw] modules are stopped Apr 26 11:00:40 192.168.122.209 [68190.759353] [tempesta fw] exiting... Apr 26 11:00:40 192.168.122.209 [68190.897869] [tdb] Shutdown Tempesta DB Apr 26 11:00:41 192.168.122.209 [68191.989453] [tdb] Start Tempesta DB Apr 26 11:00:41 192.168.122.209 [68192.128208] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:00:42 192.168.122.209 [68192.782559] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68192.782559] Maybe that's fine, but it's worth checking the [68192.782559] config - if there is no relations between the [68192.782559] names, then host name confusion attack is possible. Apr 26 11:00:42 192.168.122.209 [68192.934089] [tempesta fw] Configuration processing is completed. Apr 26 11:00:42 192.168.122.209 [68192.977328] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:00:42 192.168.122.209 [68193.005314] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:00:42 192.168.122.209 [68193.032863] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:00:42 192.168.122.209 [68193.134180] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 11:00:42 192.168.122.209 [68193.202123] [tempesta fw] Tempesta FW is ready Apr 26 11:00:53 192.168.122.209 [68203.773331] [tdb] Close table 'client0.tdb' Apr 26 11:00:53 192.168.122.209 [68203.965976] [tdb] Close table 'sessions0.tdb' Apr 26 11:00:53 192.168.122.209 [68204.220136] [tdb] Close table 'filter0.tdb' Apr 26 11:00:53 192.168.122.209 [68204.220630] [tempesta fw] modules are stopped Apr 26 11:00:53 192.168.122.209 [68204.427276] [tempesta fw] exiting... Apr 26 11:00:53 192.168.122.209 [68204.568139] [tdb] Shutdown Tempesta DB Apr 26 11:00:55 192.168.122.209 [68205.677851] [tdb] Start Tempesta DB Apr 26 11:00:55 192.168.122.209 [68205.812387] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:00:55 192.168.122.209 [68206.399415] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68206.399415] Maybe that's fine, but it's worth checking the [68206.399415] config - if there is no relations between the [68206.399415] names, then host name confusion attack is possible. Apr 26 11:00:55 192.168.122.209 [68206.566297] [tempesta fw] Configuration processing is completed. Apr 26 11:00:55 192.168.122.209 [68206.617075] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:00:55 192.168.122.209 [68206.643950] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:00:56 192.168.122.209 [68206.670665] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:00:56 192.168.122.209 [68206.738444] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 11:00:56 192.168.122.209 [68206.794314] [tempesta fw] Tempesta FW is ready Apr 26 11:01:06 192.168.122.209 [68217.317808] [tdb] Close table 'client0.tdb' Apr 26 11:01:06 192.168.122.209 [68217.500085] [tdb] Close table 'sessions0.tdb' Apr 26 11:01:07 192.168.122.209 [68217.721210] [tdb] Close table 'filter0.tdb' Apr 26 11:01:07 192.168.122.209 [68217.721634] [tempesta fw] modules are stopped Apr 26 11:01:07 192.168.122.209 [68217.904733] [tempesta fw] exiting... Apr 26 11:01:07 192.168.122.209 [68218.029973] [tdb] Shutdown Tempesta DB Apr 26 11:01:08 192.168.122.209 [68219.220195] [tdb] Start Tempesta DB Apr 26 11:01:08 192.168.122.209 [68219.366251] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:01:09 192.168.122.209 [68220.011034] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68220.011034] Maybe that's fine, but it's worth checking the [68220.011034] config - if there is no relations between the [68220.011034] names, then host name confusion attack is possible. Apr 26 11:01:09 192.168.122.209 [68220.158573] [tempesta fw] Configuration processing is completed. Apr 26 11:01:09 192.168.122.209 [68220.216314] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:01:09 192.168.122.209 [68220.244746] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:01:09 192.168.122.209 [68220.271952] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:01:09 192.168.122.209 [68220.358586] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 11:01:09 192.168.122.209 [68220.414502] [tempesta fw] Tempesta FW is ready Apr 26 11:01:20 192.168.122.209 [68230.954177] [tdb] Close table 'client0.tdb' Apr 26 11:01:20 192.168.122.209 [68231.140971] [tdb] Close table 'sessions0.tdb' Apr 26 11:01:20 192.168.122.209 [68231.359122] [tdb] Close table 'filter0.tdb' Apr 26 11:01:20 192.168.122.209 [68231.359542] [tempesta fw] modules are stopped Apr 26 11:01:20 192.168.122.209 [68231.578992] [tempesta fw] exiting... Apr 26 11:01:21 192.168.122.209 [68231.735348] [tdb] Shutdown Tempesta DB Apr 26 11:01:22 192.168.122.209 [68232.904568] [tdb] Start Tempesta DB Apr 26 11:01:22 192.168.122.209 [68233.031318] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:01:23 192.168.122.209 [68233.663620] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68233.663620] Maybe that's fine, but it's worth checking the [68233.663620] config - if there is no relations between the [68233.663620] names, then host name confusion attack is possible. Apr 26 11:01:23 192.168.122.209 [68233.834780] [tempesta fw] Configuration processing is completed. Apr 26 11:01:23 192.168.122.209 [68233.894464] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:01:23 192.168.122.209 [68233.932800] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:01:23 192.168.122.209 [68233.969224] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:01:23 192.168.122.209 [68234.054713] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 11:01:23 192.168.122.209 [68234.114688] [tempesta fw] Tempesta FW is ready Apr 26 11:01:33 192.168.122.209 [68244.645006] [tdb] Close table 'client0.tdb' Apr 26 11:01:34 192.168.122.209 [68244.831169] [tdb] Close table 'sessions0.tdb' Apr 26 11:01:34 192.168.122.209 [68245.070027] [tdb] Close table 'filter0.tdb' Apr 26 11:01:34 192.168.122.209 [68245.070460] [tempesta fw] modules are stopped Apr 26 11:01:34 192.168.122.209 [68245.292580] [tempesta fw] exiting... Apr 26 11:01:34 192.168.122.209 [68245.443922] [tdb] Shutdown Tempesta DB Apr 26 11:01:35 192.168.122.209 [68246.412558] [tdb] Start Tempesta DB Apr 26 11:01:35 192.168.122.209 [68246.541602] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:01:36 192.168.122.209 [68247.167867] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68247.167867] Maybe that's fine, but it's worth checking the [68247.167867] config - if there is no relations between the [68247.167867] names, then host name confusion attack is possible. Apr 26 11:01:36 192.168.122.209 [68247.346943] [tempesta fw] Configuration processing is completed. Apr 26 11:01:36 192.168.122.209 [68247.397284] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:01:36 192.168.122.209 [68247.424781] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:01:36 192.168.122.209 [68247.453398] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:01:36 192.168.122.209 [68247.542998] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 11:01:36 192.168.122.209 [68247.610876] [tempesta fw] Tempesta FW is ready Apr 26 11:01:47 192.168.122.209 [68258.139238] [tdb] Close table 'client0.tdb' Apr 26 11:01:47 192.168.122.209 [68258.337616] [tdb] Close table 'sessions0.tdb' Apr 26 11:01:47 192.168.122.209 [68258.578178] [tdb] Close table 'filter0.tdb' Apr 26 11:01:47 192.168.122.209 [68258.578623] [tempesta fw] modules are stopped Apr 26 11:01:48 192.168.122.209 [68258.776367] [tempesta fw] exiting... Apr 26 11:01:48 192.168.122.209 [68258.892315] [tdb] Shutdown Tempesta DB Apr 26 11:01:49 192.168.122.209 [68260.061019] [tdb] Start Tempesta DB Apr 26 11:01:49 192.168.122.209 [68260.235008] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:01:50 192.168.122.209 [68260.855690] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68260.855690] Maybe that's fine, but it's worth checking the [68260.855690] config - if there is no relations between the [68260.855690] names, then host name confusion attack is possible. Apr 26 11:01:50 192.168.122.209 [68261.055207] [tempesta fw] Configuration processing is completed. Apr 26 11:01:50 192.168.122.209 [68261.108338] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:01:50 192.168.122.209 [68261.135954] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:01:50 192.168.122.209 [68261.167876] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:01:50 192.168.122.209 [68261.259159] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 11:01:50 192.168.122.209 [68261.311055] [tempesta fw] Tempesta FW is ready Apr 26 11:02:01 192.168.122.209 [68271.895710] [tdb] Close table 'client0.tdb' Apr 26 11:02:01 192.168.122.209 [68272.073588] [tdb] Close table 'sessions0.tdb' Apr 26 11:02:01 192.168.122.209 [68272.317746] [tdb] Close table 'filter0.tdb' Apr 26 11:02:01 192.168.122.209 [68272.318180] [tempesta fw] modules are stopped Apr 26 11:02:01 192.168.122.209 [68272.505208] [tempesta fw] exiting... Apr 26 11:02:01 192.168.122.209 [68272.657094] [tdb] Shutdown Tempesta DB Apr 26 11:02:03 192.168.122.209 [68273.681975] [tdb] Start Tempesta DB Apr 26 11:02:03 192.168.122.209 [68273.817229] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:02:03 192.168.122.209 [68274.443909] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68274.443909] Maybe that's fine, but it's worth checking the [68274.443909] config - if there is no relations between the [68274.443909] names, then host name confusion attack is possible. Apr 26 11:02:03 192.168.122.209 [68274.635316] [tempesta fw] Configuration processing is completed. Apr 26 11:02:04 192.168.122.209 [68274.693686] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:02:04 192.168.122.209 [68274.729019] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:02:04 192.168.122.209 [68274.763706] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:02:04 192.168.122.209 [68274.847305] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 11:02:04 192.168.122.209 [68274.895261] [tempesta fw] Tempesta FW is ready Apr 26 11:02:14 192.168.122.209 [68285.452000] [tdb] Close table 'client0.tdb' Apr 26 11:02:14 192.168.122.209 [68285.637156] [tdb] Close table 'sessions0.tdb' Apr 26 11:02:15 192.168.122.209 [68285.855842] [tdb] Close table 'filter0.tdb' Apr 26 11:02:15 192.168.122.209 [68285.856291] [tempesta fw] modules are stopped Apr 26 11:02:15 192.168.122.209 [68286.042113] [tempesta fw] exiting... Apr 26 11:02:15 192.168.122.209 [68286.155538] [tdb] Shutdown Tempesta DB Apr 26 11:02:16 192.168.122.209 [68287.222757] [tdb] Start Tempesta DB Apr 26 11:02:16 192.168.122.209 [68287.361928] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:02:17 192.168.122.209 [68287.944729] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68287.944729] Maybe that's fine, but it's worth checking the [68287.944729] config - if there is no relations between the [68287.944729] names, then host name confusion attack is possible. Apr 26 11:02:17 192.168.122.209 [68288.115463] [tempesta fw] Configuration processing is completed. Apr 26 11:02:17 192.168.122.209 [68288.166328] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:02:17 192.168.122.209 [68288.194771] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:02:17 192.168.122.209 [68288.226402] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:02:17 192.168.122.209 [68288.291479] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 11:02:17 192.168.122.209 [68288.347471] [tempesta fw] Tempesta FW is ready Apr 26 11:02:28 192.168.122.209 [68298.966101] [tdb] Close table 'client0.tdb' Apr 26 11:02:28 192.168.122.209 [68299.160882] [tdb] Close table 'sessions0.tdb' Apr 26 11:02:28 192.168.122.209 [68299.387113] [tdb] Close table 'filter0.tdb' Apr 26 11:02:28 192.168.122.209 [68299.387584] [tempesta fw] modules are stopped Apr 26 11:02:28 192.168.122.209 [68299.608330] [tempesta fw] exiting... Apr 26 11:02:29 192.168.122.209 [68299.711358] [tdb] Shutdown Tempesta DB Apr 26 11:02:30 192.168.122.209 [68300.729145] [tdb] Start Tempesta DB Apr 26 11:02:30 192.168.122.209 [68300.847324] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:02:30 192.168.122.209 [68301.437217] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68301.437217] Maybe that's fine, but it's worth checking the [68301.437217] config - if there is no relations between the [68301.437217] names, then host name confusion attack is possible. Apr 26 11:02:30 192.168.122.209 [68301.619685] [tempesta fw] Configuration processing is completed. Apr 26 11:02:31 192.168.122.209 [68301.673890] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:02:31 192.168.122.209 [68301.702647] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:02:31 192.168.122.209 [68301.730086] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:02:31 192.168.122.209 [68301.811672] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 11:02:31 192.168.122.209 [68301.867661] [tempesta fw] Tempesta FW is ready Apr 26 11:02:31 192.168.122.209 [68302.501128] [tdb] Close table 'client0.tdb' Apr 26 11:02:32 192.168.122.209 [68302.685906] [tdb] Close table 'sessions0.tdb' Apr 26 11:02:32 192.168.122.209 [68302.924787] [tdb] Close table 'filter0.tdb' Apr 26 11:02:32 192.168.122.209 [68302.926018] [tempesta fw] modules are stopped Apr 26 11:02:32 192.168.122.209 [68303.128253] [tempesta fw] exiting... Apr 26 11:02:32 192.168.122.209 [68303.252954] [tdb] Shutdown Tempesta DB Apr 26 11:02:32 192.168.122.209 [68303.477301] End test: t_regress.test_reboot_under_load.TestRebootUnderLoadTfwNoCache.test_reboot_under_load Apr 26 11:02:32 192.168.122.209 [68303.489959] Start test: t_regress.test_reboot_under_load.TestRebootUnderLoadTfwWithCache.test_reboot_under_load Apr 26 11:02:33 192.168.122.209 [68304.565302] [tdb] Start Tempesta DB Apr 26 11:02:34 192.168.122.209 [68304.705736] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:02:34 192.168.122.209 [68305.453011] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68305.453011] Maybe that's fine, but it's worth checking the [68305.453011] config - if there is no relations between the [68305.453011] names, then host name confusion attack is possible. Apr 26 11:02:35 192.168.122.209 [68305.663747] [tempesta fw] Configuration processing is completed. Apr 26 11:02:35 192.168.122.209 [68305.717043] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:02:35 192.168.122.209 [68306.409320] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:02:35 192.168.122.209 [68306.455237] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:02:35 192.168.122.209 [68306.501370] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:02:35 192.168.122.209 [68306.551768] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 11:02:35 192.168.122.209 [68306.611704] [tempesta fw] Tempesta FW is ready Apr 26 11:02:46 192.168.122.209 [68317.574320] [tdb] Close table 'client0.tdb' Apr 26 11:02:47 192.168.122.209 [68317.772402] [tdb] Close table 'sessions0.tdb' Apr 26 11:02:50 192.168.122.209 [68320.921818] [tdb] Close table 'cache0.tdb' Apr 26 11:02:50 192.168.122.209 [68321.150206] [tdb] Close table 'filter0.tdb' Apr 26 11:02:50 192.168.122.209 [68321.150609] [tempesta fw] modules are stopped Apr 26 11:02:50 192.168.122.209 [68321.377791] [tempesta fw] exiting... Apr 26 11:02:50 192.168.122.209 [68321.515998] [tdb] Shutdown Tempesta DB Apr 26 11:02:52 192.168.122.209 [68322.675132] [tdb] Start Tempesta DB Apr 26 11:02:52 192.168.122.209 [68322.836362] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:02:53 192.168.122.209 [68324.348834] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68324.348834] Maybe that's fine, but it's worth checking the [68324.348834] config - if there is no relations between the [68324.348834] names, then host name confusion attack is possible. Apr 26 11:02:53 192.168.122.209 [68324.536008] [tempesta fw] Configuration processing is completed. Apr 26 11:02:53 192.168.122.209 [68324.597352] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:02:54 192.168.122.209 [68325.148793] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:02:54 192.168.122.209 [68325.181916] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:02:54 192.168.122.209 [68325.214585] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:02:54 192.168.122.209 [68325.312016] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 11:02:54 192.168.122.209 [68325.383950] [tempesta fw] Tempesta FW is ready Apr 26 11:03:05 192.168.122.209 [68335.980646] [tdb] Close table 'client0.tdb' Apr 26 11:03:05 192.168.122.209 [68336.197872] [tdb] Close table 'sessions0.tdb' Apr 26 11:03:09 192.168.122.209 [68339.669560] [tdb] Close table 'cache0.tdb' Apr 26 11:03:09 192.168.122.209 [68339.941153] [tdb] Close table 'filter0.tdb' Apr 26 11:03:09 192.168.122.209 [68339.941656] [tempesta fw] modules are stopped Apr 26 11:03:09 192.168.122.209 [68340.153135] [tempesta fw] exiting... Apr 26 11:03:09 192.168.122.209 [68340.280770] [tdb] Shutdown Tempesta DB Apr 26 11:03:10 192.168.122.209 [68341.362043] [tdb] Start Tempesta DB Apr 26 11:03:10 192.168.122.209 [68341.553433] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:03:12 192.168.122.209 [68342.996649] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68342.996649] Maybe that's fine, but it's worth checking the [68342.996649] config - if there is no relations between the [68342.996649] names, then host name confusion attack is possible. Apr 26 11:03:12 192.168.122.209 [68343.160138] [tempesta fw] Configuration processing is completed. Apr 26 11:03:12 192.168.122.209 [68343.205189] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:03:13 192.168.122.209 [68343.752409] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:03:13 192.168.122.209 [68343.786296] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:03:13 192.168.122.209 [68343.821905] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:03:13 192.168.122.209 [68343.896305] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 11:03:13 192.168.122.209 [68343.960208] [tempesta fw] Tempesta FW is ready Apr 26 11:03:23 192.168.122.209 [68354.507317] [tdb] Close table 'client0.tdb' Apr 26 11:03:24 192.168.122.209 [68354.682050] [tdb] Close table 'sessions0.tdb' Apr 26 11:03:27 192.168.122.209 [68357.813605] [tdb] Close table 'cache0.tdb' Apr 26 11:03:27 192.168.122.209 [68358.067688] [tdb] Close table 'filter0.tdb' Apr 26 11:03:27 192.168.122.209 [68358.068132] [tempesta fw] modules are stopped Apr 26 11:03:27 192.168.122.209 [68358.312147] [tempesta fw] exiting... Apr 26 11:03:27 192.168.122.209 [68358.412879] [tdb] Shutdown Tempesta DB Apr 26 11:03:28 192.168.122.209 [68359.427530] [tdb] Start Tempesta DB Apr 26 11:03:28 192.168.122.209 [68359.547335] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:03:30 192.168.122.209 [68360.984851] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68360.984851] Maybe that's fine, but it's worth checking the [68360.984851] config - if there is no relations between the [68360.984851] names, then host name confusion attack is possible. Apr 26 11:03:30 192.168.122.209 [68361.144378] [tempesta fw] Configuration processing is completed. Apr 26 11:03:30 192.168.122.209 [68361.186274] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:03:30 192.168.122.209 [68361.594182] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:03:30 192.168.122.209 [68361.619723] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:03:30 192.168.122.209 [68361.645116] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:03:31 192.168.122.209 [68361.712487] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 11:03:31 192.168.122.209 [68361.768356] [tempesta fw] Tempesta FW is ready Apr 26 11:03:41 192.168.122.209 [68372.316460] [tdb] Close table 'client0.tdb' Apr 26 11:03:41 192.168.122.209 [68372.499774] [tdb] Close table 'sessions0.tdb' Apr 26 11:03:44 192.168.122.209 [68375.625159] [tdb] Close table 'cache0.tdb' Apr 26 11:03:45 192.168.122.209 [68375.863361] [tdb] Close table 'filter0.tdb' Apr 26 11:03:45 192.168.122.209 [68375.863784] [tempesta fw] modules are stopped Apr 26 11:03:45 192.168.122.209 [68376.085064] [tempesta fw] exiting... Apr 26 11:03:45 192.168.122.209 [68376.175756] [tdb] Shutdown Tempesta DB Apr 26 11:03:46 192.168.122.209 [68377.229081] [tdb] Start Tempesta DB Apr 26 11:03:46 192.168.122.209 [68377.366130] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:03:48 192.168.122.209 [68378.733854] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68378.733854] Maybe that's fine, but it's worth checking the [68378.733854] config - if there is no relations between the [68378.733854] names, then host name confusion attack is possible. Apr 26 11:03:48 192.168.122.209 [68378.932715] [tempesta fw] Configuration processing is completed. Apr 26 11:03:48 192.168.122.209 [68378.983545] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:03:48 192.168.122.209 [68379.391023] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:03:48 192.168.122.209 [68379.416409] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:03:48 192.168.122.209 [68379.441926] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:03:48 192.168.122.209 [68379.520721] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 11:03:48 192.168.122.209 [68379.584665] [tempesta fw] Tempesta FW is ready Apr 26 11:03:59 192.168.122.209 [68390.153051] [tdb] Close table 'client0.tdb' Apr 26 11:03:59 192.168.122.209 [68390.332962] [tdb] Close table 'sessions0.tdb' Apr 26 11:04:02 192.168.122.209 [68393.592609] [tdb] Close table 'cache0.tdb' Apr 26 11:04:03 192.168.122.209 [68393.852253] [tdb] Close table 'filter0.tdb' Apr 26 11:04:03 192.168.122.209 [68393.852677] [tempesta fw] modules are stopped Apr 26 11:04:03 192.168.122.209 [68394.066641] [tempesta fw] exiting... Apr 26 11:04:03 192.168.122.209 [68394.208438] [tdb] Shutdown Tempesta DB Apr 26 11:04:04 192.168.122.209 [68395.254949] [tdb] Start Tempesta DB Apr 26 11:04:04 192.168.122.209 [68395.403105] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:04:06 192.168.122.209 [68396.769777] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68396.769777] Maybe that's fine, but it's worth checking the [68396.769777] config - if there is no relations between the [68396.769777] names, then host name confusion attack is possible. Apr 26 11:04:06 192.168.122.209 [68396.980970] [tempesta fw] Configuration processing is completed. Apr 26 11:04:06 192.168.122.209 [68397.037428] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:04:06 192.168.122.209 [68397.553960] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:04:06 192.168.122.209 [68397.586367] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:04:06 192.168.122.209 [68397.619474] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:04:07 192.168.122.209 [68397.709005] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 11:04:07 192.168.122.209 [68397.768951] [tempesta fw] Tempesta FW is ready Apr 26 11:04:17 192.168.122.209 [68408.352191] [tdb] Close table 'client0.tdb' Apr 26 11:04:17 192.168.122.209 [68408.553766] [tdb] Close table 'sessions0.tdb' Apr 26 11:04:21 192.168.122.209 [68411.906728] [tdb] Close table 'cache0.tdb' Apr 26 11:04:21 192.168.122.209 [68412.162185] [tdb] Close table 'filter0.tdb' Apr 26 11:04:21 192.168.122.209 [68412.162609] [tempesta fw] modules are stopped Apr 26 11:04:21 192.168.122.209 [68412.378225] [tempesta fw] exiting... Apr 26 11:04:21 192.168.122.209 [68412.492275] [tdb] Shutdown Tempesta DB Apr 26 11:04:22 192.168.122.209 [68413.575380] [tdb] Start Tempesta DB Apr 26 11:04:23 192.168.122.209 [68413.713177] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:04:24 192.168.122.209 [68415.142066] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68415.142066] Maybe that's fine, but it's worth checking the [68415.142066] config - if there is no relations between the [68415.142066] names, then host name confusion attack is possible. Apr 26 11:04:24 192.168.122.209 [68415.333234] [tempesta fw] Configuration processing is completed. Apr 26 11:04:24 192.168.122.209 [68415.385551] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:04:25 192.168.122.209 [68415.808162] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:04:25 192.168.122.209 [68415.834674] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:04:25 192.168.122.209 [68415.861889] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:04:25 192.168.122.209 [68415.937229] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 11:04:25 192.168.122.209 [68416.005155] [tempesta fw] Tempesta FW is ready Apr 26 11:04:35 192.168.122.209 [68426.553483] [tdb] Close table 'client0.tdb' Apr 26 11:04:36 192.168.122.209 [68426.756416] [tdb] Close table 'sessions0.tdb' Apr 26 11:04:39 192.168.122.209 [68429.849130] [tdb] Close table 'cache0.tdb' Apr 26 11:04:39 192.168.122.209 [68430.096689] [tdb] Close table 'filter0.tdb' Apr 26 11:04:39 192.168.122.209 [68430.097127] [tempesta fw] modules are stopped Apr 26 11:04:39 192.168.122.209 [68430.301150] [tempesta fw] exiting... Apr 26 11:04:39 192.168.122.209 [68430.436198] [tdb] Shutdown Tempesta DB Apr 26 11:04:40 192.168.122.209 [68431.462800] [tdb] Start Tempesta DB Apr 26 11:04:40 192.168.122.209 [68431.604963] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:04:42 192.168.122.209 [68433.037938] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68433.037938] Maybe that's fine, but it's worth checking the [68433.037938] config - if there is no relations between the [68433.037938] names, then host name confusion attack is possible. Apr 26 11:04:42 192.168.122.209 [68433.225500] [tempesta fw] Configuration processing is completed. Apr 26 11:04:42 192.168.122.209 [68433.284956] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:04:43 192.168.122.209 [68433.686620] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:04:43 192.168.122.209 [68433.711087] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:04:43 192.168.122.209 [68433.735309] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:04:43 192.168.122.209 [68433.805449] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 11:04:43 192.168.122.209 [68433.861449] [tempesta fw] Tempesta FW is ready Apr 26 11:04:53 192.168.122.209 [68444.396357] [tdb] Close table 'client0.tdb' Apr 26 11:04:53 192.168.122.209 [68444.576656] [tdb] Close table 'sessions0.tdb' Apr 26 11:04:57 192.168.122.209 [68447.683919] [tdb] Close table 'cache0.tdb' Apr 26 11:04:57 192.168.122.209 [68447.921856] [tdb] Close table 'filter0.tdb' Apr 26 11:04:57 192.168.122.209 [68447.922290] [tempesta fw] modules are stopped Apr 26 11:04:57 192.168.122.209 [68448.151385] [tempesta fw] exiting... Apr 26 11:04:57 192.168.122.209 [68448.294666] [tdb] Shutdown Tempesta DB Apr 26 11:04:58 192.168.122.209 [68449.331709] [tdb] Start Tempesta DB Apr 26 11:04:58 192.168.122.209 [68449.461399] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:05:00 192.168.122.209 [68450.806653] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68450.806653] Maybe that's fine, but it's worth checking the [68450.806653] config - if there is no relations between the [68450.806653] names, then host name confusion attack is possible. Apr 26 11:05:00 192.168.122.209 [68451.025691] [tempesta fw] Configuration processing is completed. Apr 26 11:05:00 192.168.122.209 [68451.080649] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:05:00 192.168.122.209 [68451.492533] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:05:00 192.168.122.209 [68451.518082] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:05:00 192.168.122.209 [68451.544527] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:05:00 192.168.122.209 [68451.637685] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 11:05:01 192.168.122.209 [68451.701589] [tempesta fw] Tempesta FW is ready Apr 26 11:05:11 192.168.122.209 [68462.281138] [tdb] Close table 'client0.tdb' Apr 26 11:05:11 192.168.122.209 [68462.463958] [tdb] Close table 'sessions0.tdb' Apr 26 11:05:14 192.168.122.209 [68465.575034] [tdb] Close table 'cache0.tdb' Apr 26 11:05:15 192.168.122.209 [68465.809687] [tdb] Close table 'filter0.tdb' Apr 26 11:05:15 192.168.122.209 [68465.810116] [tempesta fw] modules are stopped Apr 26 11:05:15 192.168.122.209 [68466.006207] [tempesta fw] exiting... Apr 26 11:05:15 192.168.122.209 [68466.136454] [tdb] Shutdown Tempesta DB Apr 26 11:05:16 192.168.122.209 [68467.209763] [tdb] Start Tempesta DB Apr 26 11:05:16 192.168.122.209 [68467.329966] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:05:18 192.168.122.209 [68468.686818] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68468.686818] Maybe that's fine, but it's worth checking the [68468.686818] config - if there is no relations between the [68468.686818] names, then host name confusion attack is possible. Apr 26 11:05:18 192.168.122.209 [68468.873929] [tempesta fw] Configuration processing is completed. Apr 26 11:05:18 192.168.122.209 [68468.925375] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:05:18 192.168.122.209 [68469.346439] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:05:18 192.168.122.209 [68469.381071] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:05:18 192.168.122.209 [68469.406597] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:05:18 192.168.122.209 [68469.502002] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 11:05:18 192.168.122.209 [68469.565876] [tempesta fw] Tempesta FW is ready Apr 26 11:05:29 192.168.122.209 [68480.070989] [tdb] Close table 'client0.tdb' Apr 26 11:05:29 192.168.122.209 [68480.274347] [tdb] Close table 'sessions0.tdb' Apr 26 11:05:32 192.168.122.209 [68483.401655] [tdb] Close table 'cache0.tdb' Apr 26 11:05:32 192.168.122.209 [68483.648137] [tdb] Close table 'filter0.tdb' Apr 26 11:05:32 192.168.122.209 [68483.648565] [tempesta fw] modules are stopped Apr 26 11:05:33 192.168.122.209 [68483.827466] [tempesta fw] exiting... Apr 26 11:05:33 192.168.122.209 [68483.921493] [tdb] Shutdown Tempesta DB Apr 26 11:05:34 192.168.122.209 [68484.906867] [tdb] Start Tempesta DB Apr 26 11:05:34 192.168.122.209 [68485.036495] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:05:35 192.168.122.209 [68486.438593] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68486.438593] Maybe that's fine, but it's worth checking the [68486.438593] config - if there is no relations between the [68486.438593] names, then host name confusion attack is possible. Apr 26 11:05:35 192.168.122.209 [68486.622164] [tempesta fw] Configuration processing is completed. Apr 26 11:05:36 192.168.122.209 [68486.672472] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:05:36 192.168.122.209 [68487.091843] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:05:36 192.168.122.209 [68487.117621] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:05:36 192.168.122.209 [68487.143590] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:05:36 192.168.122.209 [68487.230172] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 11:05:36 192.168.122.209 [68487.290109] [tempesta fw] Tempesta FW is ready Apr 26 11:05:37 192.168.122.209 [68487.912731] [tdb] Close table 'client0.tdb' Apr 26 11:05:37 192.168.122.209 [68488.074594] [tdb] Close table 'sessions0.tdb' Apr 26 11:05:40 192.168.122.209 [68491.280824] [tdb] Close table 'cache0.tdb' Apr 26 11:05:40 192.168.122.209 [68491.549412] [tdb] Close table 'filter0.tdb' Apr 26 11:05:40 192.168.122.209 [68491.549810] [tempesta fw] modules are stopped Apr 26 11:05:41 192.168.122.209 [68491.758850] [tempesta fw] exiting... Apr 26 11:05:41 192.168.122.209 [68491.877227] [tdb] Shutdown Tempesta DB Apr 26 11:05:41 192.168.122.209 [68492.119714] End test: t_regress.test_reboot_under_load.TestRebootUnderLoadTfwWithCache.test_reboot_under_load Apr 26 11:05:41 192.168.122.209 [68492.133097] Start test: t_regress.test_srv_failovering.TestFailovering.test_on_close Apr 26 11:05:42 192.168.122.209 [68493.176130] [tdb] Start Tempesta DB Apr 26 11:05:42 192.168.122.209 [68493.310801] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:05:44 192.168.122.209 [68495.355010] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68495.355010] Maybe that's fine, but it's worth checking the [68495.355010] config - if there is no relations between the [68495.355010] names, then host name confusion attack is possible. Apr 26 11:05:45 192.168.122.209 [68496.074331] [tempesta fw] Configuration processing is completed. Apr 26 11:05:45 192.168.122.209 [68496.136400] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:05:45 192.168.122.209 [68496.170052] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:05:45 192.168.122.209 [68496.203078] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:05:45 192.168.122.209 [68496.418327] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:05:45 192.168.122.209 [68496.458268] [tempesta fw] Tempesta FW is ready Apr 26 11:05:48 192.168.122.209 [68499.060948] [tdb] Close table 'client0.tdb' Apr 26 11:05:48 192.168.122.209 [68499.260685] [tdb] Close table 'sessions0.tdb' Apr 26 11:05:48 192.168.122.209 [68499.485618] [tdb] Close table 'filter0.tdb' Apr 26 11:05:48 192.168.122.209 [68499.486056] [tempesta fw] modules are stopped Apr 26 11:05:49 192.168.122.209 [68499.845135] [tempesta fw] exiting... Apr 26 11:05:49 192.168.122.209 [68499.980514] [tdb] Shutdown Tempesta DB Apr 26 11:05:49 192.168.122.209 [68500.220582] End test: t_regress.test_srv_failovering.TestFailovering.test_on_close Apr 26 11:05:49 192.168.122.209 [68500.231251] Start test: t_regress.test_stress_failovering.TestStressFailovering.test_failovering_sched_ratio Apr 26 11:05:50 192.168.122.209 [68501.508897] [tdb] Start Tempesta DB Apr 26 11:05:50 192.168.122.209 [68501.660886] net_ratelimit: 6 callbacks suppressed Apr 26 11:05:50 192.168.122.209 [68501.660889] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:05:51 192.168.122.209 [68502.331233] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68502.331233] Maybe that's fine, but it's worth checking the [68502.331233] config - if there is no relations between the [68502.331233] names, then host name confusion attack is possible. Apr 26 11:05:51 192.168.122.209 [68502.498381] [tempesta fw] Configuration processing is completed. Apr 26 11:05:51 192.168.122.209 [68502.563301] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:05:51 192.168.122.209 [68502.597138] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:05:51 192.168.122.209 [68502.633042] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:05:52 192.168.122.209 [68502.706381] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:05:52 192.168.122.209 [68502.746332] [tempesta fw] Tempesta FW is ready Apr 26 11:05:52 192.168.122.209 [68503.150836] [tempesta fw] Warning: request evicted: the number of retries exceeded, status 504: 127.0.0.1 Apr 26 11:05:52 192.168.122.209 [68503.151762] [tempesta fw] Warning: request evicted: the number of retries exceeded, status 504: 127.0.0.1 Apr 26 11:05:52 192.168.122.209 [68503.152607] [tempesta fw] Warning: request evicted: the number of retries exceeded, status 504: 127.0.0.1 Apr 26 11:05:52 192.168.122.209 [68503.153458] [tempesta fw] Warning: request evicted: the number of retries exceeded, status 504: 127.0.0.1 Apr 26 11:05:52 192.168.122.209 [68503.154322] [tempesta fw] Warning: request evicted: the number of retries exceeded, status 504: 127.0.0.1 Apr 26 11:05:52 192.168.122.209 [68503.155161] [tempesta fw] Warning: request evicted: the number of retries exceeded, status 504: 127.0.0.1 Apr 26 11:06:02 192.168.122.209 [68513.527905] [tdb] Close table 'client0.tdb' Apr 26 11:06:03 192.168.122.209 [68513.737077] [tdb] Close table 'sessions0.tdb' Apr 26 11:06:03 192.168.122.209 [68513.978954] [tdb] Close table 'filter0.tdb' Apr 26 11:06:03 192.168.122.209 [68513.979425] [tempesta fw] modules are stopped Apr 26 11:06:03 192.168.122.209 [68514.168979] [tempesta fw] exiting... Apr 26 11:06:03 192.168.122.209 [68514.364185] [tdb] Shutdown Tempesta DB Apr 26 11:06:03 192.168.122.209 [68514.637257] End test: t_regress.test_stress_failovering.TestStressFailovering.test_failovering_sched_ratio Apr 26 11:06:03 192.168.122.209 [68514.652527] Start test: t_regress.test_stress_failovering.TestStressFailoveringWithUnlimKAReq.test_failovering_with_unlim_ka_requests Apr 26 11:06:05 192.168.122.209 [68516.055125] [tdb] Start Tempesta DB Apr 26 11:06:05 192.168.122.209 [68516.206037] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:06:06 192.168.122.209 [68516.874042] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68516.874042] Maybe that's fine, but it's worth checking the [68516.874042] config - if there is no relations between the [68516.874042] names, then host name confusion attack is possible. Apr 26 11:06:06 192.168.122.209 [68517.034665] [tempesta fw] Configuration processing is completed. Apr 26 11:06:06 192.168.122.209 [68517.095883] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:06:06 192.168.122.209 [68517.127701] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:06:06 192.168.122.209 [68517.158190] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:06:06 192.168.122.209 [68517.230596] [tempesta fw] Open listen socket on: 127.0.0.1:443 Apr 26 11:06:06 192.168.122.209 [68517.274484] [tempesta fw] Tempesta FW is ready Apr 26 11:06:16 192.168.122.209 [68527.491669] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.492260] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.497191] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.497782] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.498593] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.499132] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.499543] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.500451] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.500453] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.500459] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.501231] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.503044] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.503833] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.504387] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.505163] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.505710] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.506508] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.507056] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.507566] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.507840] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.508370] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.508918] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.508975] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.509701] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.510534] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.510564] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.511217] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.511773] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.511798] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.512573] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.513087] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.513855] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.514145] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.514148] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.514171] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.514173] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.514201] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.514202] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.514250] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.514251] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.514271] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.514273] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.514302] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.514304] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.514361] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.514363] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.514389] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.514391] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.514437] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.514439] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.514465] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.514467] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.514521] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.514523] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.514553] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.514555] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.514579] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.514581] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.514622] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.515185] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.515737] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.515743] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.515745] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.515772] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.515774] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.515807] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.515809] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.515837] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.515839] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.516013] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.516014] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.516299] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.516301] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.516333] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.516335] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.516363] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.516365] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.516394] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.516396] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.516439] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.516441] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.516477] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.516479] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.516485] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.516514] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.516516] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.516567] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.516569] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.516598] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.516599] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.516627] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.516629] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.516706] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.516708] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.516750] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.516752] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.516779] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.516781] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.517371] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.518306] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.518808] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.520273] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.520277] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.520848] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.520856] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.520859] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.520909] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.520911] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.520945] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.520947] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.520976] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.520978] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.521009] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.521011] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.521033] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.521034] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.521059] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.521061] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.521086] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.521088] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.521115] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.521117] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.521140] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.521142] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.521178] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.521179] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.521210] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.521211] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.521241] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.521243] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.521296] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.521298] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.521329] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.521331] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.521646] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.522252] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.522548] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.522551] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.522582] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.522584] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.522606] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.522608] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.522633] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.522635] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.522657] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.522659] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.522719] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.522721] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.522752] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.522753] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.522783] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.522785] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.522821] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.522823] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.522856] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.522857] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.522888] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.522890] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.522916] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.522918] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.522941] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.522947] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.522969] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.522971] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.523001] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.523003] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.523024] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.523026] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.523537] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.523540] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.523543] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.523593] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.523594] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.523637] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.523640] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.523669] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.523671] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.523692] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.523694] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.523721] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.523723] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.524005] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.524007] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.524056] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.524058] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.524300] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.524302] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.524312] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.524314] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.524316] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.524335] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.524337] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.524352] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.524354] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.524360] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.524363] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.524381] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.524383] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.524392] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.524394] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.524402] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.524404] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.524427] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.524435] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.524437] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.524439] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.524458] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.524460] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.524462] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.524464] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.524486] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.524488] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.524489] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.524491] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.524517] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.524519] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.524521] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.524523] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.524547] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.524549] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.524559] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.524561] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.524569] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.524571] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.524583] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.524584] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.524597] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.524599] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.524613] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.524614] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.524646] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.524648] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.524670] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.524677] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.524708] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.524710] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.524732] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.524733] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.524846] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.524848] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.524939] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.524967] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.524970] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.525039] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.525041] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.525100] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.525101] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.528116] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.528317] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.528328] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.528333] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.528374] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.528376] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.528398] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.528402] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.528404] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.528406] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.528445] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.528447] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.528477] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.528479] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.528497] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.528499] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:16 192.168.122.209 [68527.528528] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:16 192.168.122.209 [68527.528530] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.528557] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.528558] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.528588] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.528590] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.528608] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.528610] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.528634] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.528636] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.528660] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.528662] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.528690] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.528691] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.528710] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.528712] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.528732] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.528734] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.528760] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.528761] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.528790] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.528792] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.528810] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.528812] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.528835] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.528836] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.528861] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.528862] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.528891] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.528893] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.528903] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.528905] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.528908] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.528918] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.528919] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.528940] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.528942] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.528960] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.528962] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.528968] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.528969] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.528997] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.528999] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.529009] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.529010] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.529035] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.529036] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.529047] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.529048] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.529072] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.529074] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.529083] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.529084] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.529101] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.529103] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.529120] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.529122] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.529155] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.529157] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.529191] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.529193] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.529194] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.529196] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.529229] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.529231] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.529254] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.529256] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.529263] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.529265] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.529282] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.529284] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.529309] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.529311] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.529317] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.529319] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.529344] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.529346] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.529373] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.529374] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.529384] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.529386] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.529422] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.529423] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.529488] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.529490] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.529540] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.529542] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.529603] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.529605] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.529634] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.529636] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.529714] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.530293] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.531022] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.531034] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.531037] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.531067] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.531069] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.531098] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.531100] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.531128] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.531130] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.531159] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.531167] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.531195] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.531197] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.531223] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.531225] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.531254] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.531256] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.531287] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.531289] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.531316] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.531318] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.531344] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.531346] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.531373] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.531375] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.531403] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.531405] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.531438] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.531440] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.531466] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.531468] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.531496] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.531498] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.531526] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.531528] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.531556] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.531557] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.531572] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.531584] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.531586] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.531614] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.531615] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.531643] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.531645] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.531672] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.531673] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.531699] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.531701] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.531729] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.531731] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.531796] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.531798] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.531826] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.531828] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.531858] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.531859] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.531881] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.531882] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.531905] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.531907] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.531928] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.531930] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.531959] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.531961] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.531989] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.531991] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.532019] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.532020] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.532043] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.532045] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.532066] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.532067] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.532090] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.532092] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.532124] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.532125] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.532152] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.532153] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.532183] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.532184] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.532203] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.532204] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.532224] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.532226] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.532250] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.532252] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.532277] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.532279] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.532308] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.532309] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.532340] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.532377] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.532380] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.532407] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.532408] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.532449] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.532450] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.532966] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.533663] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.533673] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.533676] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.534202] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.534596] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.534598] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.534627] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.534628] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.534676] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.534678] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.534707] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.534709] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.534758] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.534760] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.534782] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.534783] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.534828] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.534830] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.534867] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.534869] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.534901] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.534903] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.534930] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.534932] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.534963] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.535415] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.535418] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.535459] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.535461] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.808843] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.808847] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.808854] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.808951] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.808960] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.809117] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.809123] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.809243] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.809249] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.809318] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.809324] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.809421] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.809426] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68527.809527] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:06:17 192.168.122.209 [68527.809532] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:06:17 192.168.122.209 [68528.174000] [tdb] Close table 'client0.tdb' Apr 26 11:06:17 192.168.122.209 [68528.387866] [tdb] Close table 'sessions0.tdb' Apr 26 11:06:17 192.168.122.209 [68528.650725] [tdb] Close table 'filter0.tdb' Apr 26 11:06:17 192.168.122.209 [68528.651257] [tempesta fw] modules are stopped Apr 26 11:06:18 192.168.122.209 [68528.848268] [tempesta fw] exiting... Apr 26 11:06:18 192.168.122.209 [68528.966009] [tdb] Shutdown Tempesta DB Apr 26 11:06:18 192.168.122.209 [68529.245718] End test: t_regress.test_stress_failovering.TestStressFailoveringWithUnlimKAReq.test_failovering_with_unlim_ka_requests Apr 26 11:06:18 192.168.122.209 [68529.269421] Start test: t_regress.test_stress_pipeline.TestStressPipeline.test_pipeline Apr 26 11:06:19 192.168.122.209 [68530.442858] [tdb] Start Tempesta DB Apr 26 11:06:19 192.168.122.209 [68530.575263] net_ratelimit: 896 callbacks suppressed Apr 26 11:06:19 192.168.122.209 [68530.575266] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:06:20 192.168.122.209 [68531.070883] [tempesta fw] Configuration processing is completed. Apr 26 11:06:20 192.168.122.209 [68531.127922] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:06:20 192.168.122.209 [68531.160277] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:06:20 192.168.122.209 [68531.201625] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:06:20 192.168.122.209 [68531.270802] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:06:20 192.168.122.209 [68531.310740] [tempesta fw] Tempesta FW is ready Apr 26 11:06:31 192.168.122.209 [68542.044557] [tdb] Close table 'client0.tdb' Apr 26 11:06:31 192.168.122.209 [68542.242479] [tdb] Close table 'sessions0.tdb' Apr 26 11:06:31 192.168.122.209 [68542.499801] [tdb] Close table 'filter0.tdb' Apr 26 11:06:31 192.168.122.209 [68542.500247] [tempesta fw] modules are stopped Apr 26 11:06:31 192.168.122.209 [68542.664416] [tempesta fw] exiting... Apr 26 11:06:32 192.168.122.209 [68542.792645] [tdb] Shutdown Tempesta DB Apr 26 11:06:32 192.168.122.209 [68543.048999] End test: t_regress.test_stress_pipeline.TestStressPipeline.test_pipeline Apr 26 11:06:32 192.168.122.209 [68543.069914] Start test: t_sched.test_h2_hash_func.HashSchedulerH2.test_hash_scheduler Apr 26 11:06:33 192.168.122.209 [68544.215859] [tdb] Start Tempesta DB Apr 26 11:06:33 192.168.122.209 [68544.350604] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:06:34 192.168.122.209 [68545.024265] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68545.024265] Maybe that's fine, but it's worth checking the [68545.024265] config - if there is no relations between the [68545.024265] names, then host name confusion attack is possible. Apr 26 11:06:34 192.168.122.209 [68545.242935] [tempesta fw] Configuration processing is completed. Apr 26 11:06:34 192.168.122.209 [68545.301390] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:06:34 192.168.122.209 [68545.330649] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:06:34 192.168.122.209 [68545.362489] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:06:34 192.168.122.209 [68545.518949] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:06:34 192.168.122.209 [68545.520708] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:06:34 192.168.122.209 [68545.558821] [tempesta fw] Tempesta FW is ready Apr 26 11:06:40 192.168.122.209 [68551.551593] [tdb] Close table 'client0.tdb' Apr 26 11:06:41 192.168.122.209 [68551.731802] [tdb] Close table 'sessions0.tdb' Apr 26 11:06:41 192.168.122.209 [68551.968884] [tdb] Close table 'filter0.tdb' Apr 26 11:06:41 192.168.122.209 [68551.969360] [tempesta fw] modules are stopped Apr 26 11:06:41 192.168.122.209 [68552.153130] [tempesta fw] exiting... Apr 26 11:06:41 192.168.122.209 [68552.258526] [tdb] Shutdown Tempesta DB Apr 26 11:06:41 192.168.122.209 [68552.491900] End test: t_sched.test_h2_hash_func.HashSchedulerH2.test_hash_scheduler Apr 26 11:06:41 192.168.122.209 [68552.504581] Start test: t_sched.test_h2_hash_stress.BindToServerH2.test_hash Apr 26 11:06:47 192.168.122.209 [68558.617474] [tdb] Start Tempesta DB Apr 26 11:06:48 192.168.122.209 [68558.781501] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:06:49 192.168.122.209 [68560.096497] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68560.096497] Maybe that's fine, but it's worth checking the [68560.096497] config - if there is no relations between the [68560.096497] names, then host name confusion attack is possible. Apr 26 11:06:50 192.168.122.209 [68560.875271] [tempesta fw] Configuration processing is completed. Apr 26 11:06:50 192.168.122.209 [68560.932177] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:06:50 192.168.122.209 [68560.965216] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:06:50 192.168.122.209 [68560.998245] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:06:51 192.168.122.209 [68561.775209] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:06:51 192.168.122.209 [68561.776995] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:06:51 192.168.122.209 [68561.823155] [tempesta fw] Tempesta FW is ready Apr 26 11:07:01 192.168.122.209 [68572.016784] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:07:01 192.168.122.209 [68572.017415] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:07:01 192.168.122.209 [68572.027628] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:07:01 192.168.122.209 [68572.028199] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:07:01 192.168.122.209 [68572.029832] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:07:01 192.168.122.209 [68572.030391] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:07:01 192.168.122.209 [68572.032515] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:07:01 192.168.122.209 [68572.033073] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:07:01 192.168.122.209 [68572.034222] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:07:01 192.168.122.209 [68572.034772] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:07:01 192.168.122.209 [68572.035677] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:07:01 192.168.122.209 [68572.036235] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:07:01 192.168.122.209 [68572.037023] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:07:01 192.168.122.209 [68572.037565] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:07:01 192.168.122.209 [68572.044683] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:07:01 192.168.122.209 [68572.045234] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:07:03 192.168.122.209 [68574.435255] [tdb] Close table 'client0.tdb' Apr 26 11:07:03 192.168.122.209 [68574.653082] [tdb] Close table 'sessions0.tdb' Apr 26 11:07:04 192.168.122.209 [68574.910193] [tdb] Close table 'filter0.tdb' Apr 26 11:07:04 192.168.122.209 [68574.910705] [tempesta fw] modules are stopped Apr 26 11:07:04 192.168.122.209 [68575.100983] [tempesta fw] exiting... Apr 26 11:07:04 192.168.122.209 [68575.212558] [tdb] Shutdown Tempesta DB Apr 26 11:07:05 192.168.122.209 [68576.160323] End test: t_sched.test_h2_hash_stress.BindToServerH2.test_hash Apr 26 11:07:05 192.168.122.209 [68576.171720] Start test: t_sched.test_h2_ratio_static.RatioH2.test_load_distribution Apr 26 11:07:07 192.168.122.209 [68578.460773] [tdb] Start Tempesta DB Apr 26 11:07:07 192.168.122.209 [68578.609778] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:07:08 192.168.122.209 [68579.480305] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68579.480305] Maybe that's fine, but it's worth checking the [68579.480305] config - if there is no relations between the [68579.480305] names, then host name confusion attack is possible. Apr 26 11:07:09 192.168.122.209 [68579.783707] [tempesta fw] Configuration processing is completed. Apr 26 11:07:09 192.168.122.209 [68579.845396] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:07:09 192.168.122.209 [68579.878014] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:07:09 192.168.122.209 [68579.909542] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:07:09 192.168.122.209 [68580.195511] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:07:09 192.168.122.209 [68580.197345] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:07:09 192.168.122.209 [68580.239285] [tempesta fw] Tempesta FW is ready Apr 26 11:07:19 192.168.122.209 [68590.443682] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:07:19 192.168.122.209 [68590.444287] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:07:19 192.168.122.209 [68590.444353] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:07:19 192.168.122.209 [68590.444753] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:07:19 192.168.122.209 [68590.444756] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:07:19 192.168.122.209 [68590.444785] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:07:19 192.168.122.209 [68590.444787] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:07:19 192.168.122.209 [68590.445114] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:07:19 192.168.122.209 [68590.445434] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:07:19 192.168.122.209 [68590.445438] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:07:19 192.168.122.209 [68590.445535] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:07:19 192.168.122.209 [68590.445537] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:07:19 192.168.122.209 [68590.445576] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:07:19 192.168.122.209 [68590.445578] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:07:19 192.168.122.209 [68590.445645] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:07:19 192.168.122.209 [68590.446205] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:07:19 192.168.122.209 [68590.446211] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:07:19 192.168.122.209 [68590.447012] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:07:19 192.168.122.209 [68590.447556] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:07:19 192.168.122.209 [68590.448302] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:07:19 192.168.122.209 [68590.448305] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:07:19 192.168.122.209 [68590.448307] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:07:19 192.168.122.209 [68590.448403] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:07:19 192.168.122.209 [68590.448405] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:07:19 192.168.122.209 [68590.448579] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:07:19 192.168.122.209 [68590.448581] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:07:19 192.168.122.209 [68590.448667] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:07:19 192.168.122.209 [68590.448669] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:07:19 192.168.122.209 [68590.448789] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:07:19 192.168.122.209 [68590.448792] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:07:20 192.168.122.209 [68591.573352] [tdb] Close table 'client0.tdb' Apr 26 11:07:21 192.168.122.209 [68591.780971] [tdb] Close table 'sessions0.tdb' Apr 26 11:07:21 192.168.122.209 [68592.044424] [tdb] Close table 'filter0.tdb' Apr 26 11:07:21 192.168.122.209 [68592.044859] [tempesta fw] modules are stopped Apr 26 11:07:21 192.168.122.209 [68592.213546] [tempesta fw] exiting... Apr 26 11:07:21 192.168.122.209 [68592.351352] [tdb] Shutdown Tempesta DB Apr 26 11:07:22 192.168.122.209 [68592.903853] End test: t_sched.test_h2_ratio_static.RatioH2.test_load_distribution Apr 26 11:07:22 192.168.122.209 [68592.917663] Start test: t_sched.test_h2_ratio_static.RatioVariableConnsH2.test_load_distribution Apr 26 11:07:24 192.168.122.209 [68595.569612] [tdb] Start Tempesta DB Apr 26 11:07:25 192.168.122.209 [68595.713928] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:07:25 192.168.122.209 [68596.624964] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68596.624964] Maybe that's fine, but it's worth checking the [68596.624964] config - if there is no relations between the [68596.624964] names, then host name confusion attack is possible. Apr 26 11:07:26 192.168.122.209 [68596.927692] [tempesta fw] Configuration processing is completed. Apr 26 11:07:26 192.168.122.209 [68596.997247] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:07:26 192.168.122.209 [68597.037597] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:07:26 192.168.122.209 [68597.075665] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:07:26 192.168.122.209 [68597.339681] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:07:26 192.168.122.209 [68597.341500] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:07:26 192.168.122.209 [68597.383599] [tempesta fw] Tempesta FW is ready Apr 26 11:07:36 192.168.122.209 [68607.607349] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:07:36 192.168.122.209 [68607.607962] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:07:36 192.168.122.209 [68607.607967] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:07:36 192.168.122.209 [68607.607972] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:07:36 192.168.122.209 [68607.614433] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:07:36 192.168.122.209 [68607.615009] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:07:38 192.168.122.209 [68608.705731] [tdb] Close table 'client0.tdb' Apr 26 11:07:38 192.168.122.209 [68608.898869] [tdb] Close table 'sessions0.tdb' Apr 26 11:07:38 192.168.122.209 [68609.144114] [tdb] Close table 'filter0.tdb' Apr 26 11:07:38 192.168.122.209 [68609.144575] [tempesta fw] modules are stopped Apr 26 11:07:38 192.168.122.209 [68609.373549] [tempesta fw] exiting... Apr 26 11:07:38 192.168.122.209 [68609.499097] [tdb] Shutdown Tempesta DB Apr 26 11:07:39 192.168.122.209 [68610.142542] End test: t_sched.test_h2_ratio_static.RatioVariableConnsH2.test_load_distribution Apr 26 11:07:39 192.168.122.209 [68610.155280] Start test: t_sched.test_h2_ratio_weight.RatioH2.test_load_distribution Apr 26 11:07:41 192.168.122.209 [68612.645713] [tdb] Start Tempesta DB Apr 26 11:07:42 192.168.122.209 [68612.789516] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:07:43 192.168.122.209 [68613.689181] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68613.689181] Maybe that's fine, but it's worth checking the [68613.689181] config - if there is no relations between the [68613.689181] names, then host name confusion attack is possible. Apr 26 11:07:43 192.168.122.209 [68613.988148] [tempesta fw] Configuration processing is completed. Apr 26 11:07:43 192.168.122.209 [68614.042706] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:07:43 192.168.122.209 [68614.070935] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:07:43 192.168.122.209 [68614.099982] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:07:43 192.168.122.209 [68614.387879] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:07:43 192.168.122.209 [68614.389669] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:07:43 192.168.122.209 [68614.435821] [tempesta fw] Tempesta FW is ready Apr 26 11:07:54 192.168.122.209 [68624.681087] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:07:54 192.168.122.209 [68624.681695] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:07:55 192.168.122.209 [68625.805475] [tdb] Close table 'client0.tdb' Apr 26 11:07:55 192.168.122.209 [68625.990890] [tdb] Close table 'sessions0.tdb' Apr 26 11:07:55 192.168.122.209 [68626.230097] [tdb] Close table 'filter0.tdb' Apr 26 11:07:55 192.168.122.209 [68626.230512] [tempesta fw] modules are stopped Apr 26 11:07:55 192.168.122.209 [68626.431460] [tempesta fw] exiting... Apr 26 11:07:55 192.168.122.209 [68626.567291] [tdb] Shutdown Tempesta DB Apr 26 11:07:56 192.168.122.209 [68627.148842] End test: t_sched.test_h2_ratio_weight.RatioH2.test_load_distribution Apr 26 11:07:56 192.168.122.209 [68627.166565] Start test: t_sched.test_h2_ratio_weight.RatioVariableConnsH2.test_load_distribution Apr 26 11:07:58 192.168.122.209 [68629.499782] [tdb] Start Tempesta DB Apr 26 11:07:58 192.168.122.209 [68629.643645] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:07:59 192.168.122.209 [68630.485478] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68630.485478] Maybe that's fine, but it's worth checking the [68630.485478] config - if there is no relations between the [68630.485478] names, then host name confusion attack is possible. Apr 26 11:08:00 192.168.122.209 [68630.804441] [tempesta fw] Configuration processing is completed. Apr 26 11:08:00 192.168.122.209 [68630.868043] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:08:00 192.168.122.209 [68630.902850] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:08:00 192.168.122.209 [68630.937449] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:08:00 192.168.122.209 [68631.208081] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:08:00 192.168.122.209 [68631.209937] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:08:00 192.168.122.209 [68631.252032] [tempesta fw] Tempesta FW is ready Apr 26 11:08:10 192.168.122.209 [68641.466764] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.467160] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.467452] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.468045] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.469098] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.469617] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.470150] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.470695] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.470749] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.472843] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.472847] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.472852] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.472857] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.472860] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.472863] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.472877] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.472937] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.472939] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.472986] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.472987] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.473066] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.473068] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.473121] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.473123] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.473157] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.473159] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.473604] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.473606] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.473633] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.473703] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.473706] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.473736] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.473738] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.488409] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.488420] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.490184] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.490189] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.491483] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.491490] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.492300] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.492997] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.493007] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.493127] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.493130] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.493177] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.493180] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.493312] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.493315] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.493427] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.493429] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.493544] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.495026] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.495607] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.496696] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.497365] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.497373] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.497376] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.497639] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.497641] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.497733] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.497735] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.498375] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.498439] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.500727] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.500994] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.501003] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.501008] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.501039] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.501044] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.501595] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.501597] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.501762] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.501764] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.501766] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.501799] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.501805] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.501833] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.501835] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.501853] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.501854] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.501949] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.501951] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.502000] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.502001] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.502018] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.502020] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.502194] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.502196] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.502223] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.502224] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.502248] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.502250] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.502283] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.502284] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.502316] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.502318] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.502337] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.502338] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.502358] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.502360] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.502388] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.502390] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.502421] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.502423] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.502450] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.502452] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.502477] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.502479] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.502699] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.503593] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.504029] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.504581] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.505384] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.505933] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.506747] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.507367] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.508340] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.508876] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.509554] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.509557] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.509560] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.509694] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.509696] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.509717] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.509719] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.509890] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.509893] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.510325] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.510327] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.510328] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.510355] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.510357] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.510380] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.510381] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.510906] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.511466] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.512211] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.512756] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.513539] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.514101] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.514821] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.515369] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.516198] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.519633] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.520118] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.520125] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.520127] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.520152] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.520154] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.520212] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.520214] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.520239] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.520240] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.520270] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.520272] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.520880] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.520883] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.520885] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.520911] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.520913] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.520939] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.520947] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.520976] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.520978] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.521002] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.521003] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.521040] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.521042] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.521089] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.521091] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.521120] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.521122] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.521148] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.521150] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.521193] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.521195] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.521219] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.521221] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.521265] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.521266] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.521355] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.521357] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.521382] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.521384] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.521411] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.521413] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.521436] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.521466] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.521468] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.521490] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.521492] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.521524] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.521526] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.521545] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.521547] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.522229] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.522728] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.522731] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.522733] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.523472] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.523476] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.524069] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.524786] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.524797] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.524800] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.525332] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.526117] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.526349] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.526357] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.526399] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.526401] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.526429] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.526430] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.526618] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.526622] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.526645] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.526646] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.526686] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.526688] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.526719] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.526720] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.526752] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.526753] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.526786] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.526787] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.526840] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.526842] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.527410] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.527413] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.527416] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.527449] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.527451] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.527497] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.527499] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.527524] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.527532] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.527585] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.527587] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.527617] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.527618] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.528218] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.528795] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.529295] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.530062] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.530065] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.530068] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.530167] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.530170] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.530195] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.530197] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.530225] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.530227] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.530253] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.530255] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.530289] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.530290] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.530318] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.530319] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.530348] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.530350] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.530378] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.530379] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.530411] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.530413] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.530438] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.530439] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.530472] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.530473] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.530498] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.530500] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.530532] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.530534] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.530559] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.530561] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.530588] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.530589] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.530615] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.531513] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.531949] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.532720] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.532734] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.651997] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.652127] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.652797] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.653754] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.653759] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.653765] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.654305] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.655776] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.656517] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.657525] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.658278] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.659760] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.662289] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.662364] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.663606] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.663609] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.663615] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.664425] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.666238] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.666250] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.667549] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:10 192.168.122.209 [68641.667552] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:10 192.168.122.209 [68641.667557] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:11 192.168.122.209 [68641.669087] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:11 192.168.122.209 [68641.670207] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:11 192.168.122.209 [68641.670211] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:11 192.168.122.209 [68641.671510] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:11 192.168.122.209 [68641.671512] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:11 192.168.122.209 [68641.671517] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:11 192.168.122.209 [68641.672306] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:11 192.168.122.209 [68641.674138] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:11 192.168.122.209 [68641.674148] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:11 192.168.122.209 [68641.675447] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:11 192.168.122.209 [68641.675450] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:11 192.168.122.209 [68641.675455] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:11 192.168.122.209 [68641.676255] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:11 192.168.122.209 [68641.678068] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:11 192.168.122.209 [68641.678077] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:11 192.168.122.209 [68641.679354] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:11 192.168.122.209 [68641.679356] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:11 192.168.122.209 [68641.679361] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:11 192.168.122.209 [68641.680153] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:11 192.168.122.209 [68641.681969] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:11 192.168.122.209 [68641.681981] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:11 192.168.122.209 [68641.683266] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:11 192.168.122.209 [68641.683271] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:11 192.168.122.209 [68641.684576] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:11 192.168.122.209 [68641.684578] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:11 192.168.122.209 [68641.684583] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:11 192.168.122.209 [68641.685362] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:11 192.168.122.209 [68641.686072] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:11 192.168.122.209 [68641.686634] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:11 192.168.122.209 [68641.687181] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:11 192.168.122.209 [68641.689297] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:11 192.168.122.209 [68641.689843] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:11 192.168.122.209 [68641.689847] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:11 192.168.122.209 [68641.691159] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:11 192.168.122.209 [68641.691161] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:11 192.168.122.209 [68641.691166] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:11 192.168.122.209 [68641.696127] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:11 192.168.122.209 [68641.696688] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:11 192.168.122.209 [68641.698033] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:11 192.168.122.209 [68641.698583] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:11 192.168.122.209 [68641.699382] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:11 192.168.122.209 [68641.699957] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:11 192.168.122.209 [68641.700757] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:11 192.168.122.209 [68641.701367] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:11 192.168.122.209 [68641.702174] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:11 192.168.122.209 [68641.702728] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:11 192.168.122.209 [68641.703910] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:11 192.168.122.209 [68641.704470] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:11 192.168.122.209 [68641.705258] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:11 192.168.122.209 [68641.705805] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:11 192.168.122.209 [68641.706579] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:11 192.168.122.209 [68641.707129] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:11 192.168.122.209 [68641.707908] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:11 192.168.122.209 [68641.708498] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:11 192.168.122.209 [68641.709279] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:11 192.168.122.209 [68641.709847] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:11 192.168.122.209 [68641.710623] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:11 192.168.122.209 [68641.711180] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:11 192.168.122.209 [68641.711961] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:11 192.168.122.209 [68641.712529] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:11 192.168.122.209 [68641.713305] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:11 192.168.122.209 [68641.713851] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:11 192.168.122.209 [68641.714751] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:11 192.168.122.209 [68641.715406] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:11 192.168.122.209 [68641.716206] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:11 192.168.122.209 [68641.716754] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:11 192.168.122.209 [68641.717521] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:11 192.168.122.209 [68641.718102] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:11 192.168.122.209 [68641.718913] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:11 192.168.122.209 [68641.719454] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:11 192.168.122.209 [68641.720246] [tempesta tls] Warning: Cannot send TLS alert 0:1, -9 Apr 26 11:08:11 192.168.122.209 [68641.720820] [tempesta fw] Warning: Close TCP socket w/o sending alert to the peer: 127.0.0.1 Apr 26 11:08:12 192.168.122.209 [68642.964151] [tdb] Close table 'client0.tdb' Apr 26 11:08:12 192.168.122.209 [68643.233162] [tdb] Close table 'sessions0.tdb' Apr 26 11:08:12 192.168.122.209 [68643.558879] [tdb] Close table 'filter0.tdb' Apr 26 11:08:12 192.168.122.209 [68643.559328] [tempesta fw] modules are stopped Apr 26 11:08:13 192.168.122.209 [68643.741711] [tempesta fw] exiting... Apr 26 11:08:13 192.168.122.209 [68643.884533] [tdb] Shutdown Tempesta DB Apr 26 11:08:13 192.168.122.209 [68644.448013] End test: t_sched.test_h2_ratio_weight.RatioVariableConnsH2.test_load_distribution Apr 26 11:08:13 192.168.122.209 [68644.464267] Start test: t_sched.test_hash_stress.BindToServer.test_hash Apr 26 11:08:20 192.168.122.209 [68650.929449] [tdb] Start Tempesta DB Apr 26 11:08:20 192.168.122.209 [68651.096746] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:08:21 192.168.122.209 [68652.557101] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68652.557101] Maybe that's fine, but it's worth checking the [68652.557101] config - if there is no relations between the [68652.557101] names, then host name confusion attack is possible. Apr 26 11:08:22 192.168.122.209 [68653.300343] [tempesta fw] Configuration processing is completed. Apr 26 11:08:22 192.168.122.209 [68653.364527] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:08:22 192.168.122.209 [68653.405203] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:08:22 192.168.122.209 [68653.445141] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:08:23 192.168.122.209 [68654.200429] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:08:23 192.168.122.209 [68654.202261] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:08:23 192.168.122.209 [68654.252363] [tempesta fw] Tempesta FW is ready Apr 26 11:08:36 192.168.122.209 [68666.907369] [tdb] Close table 'client0.tdb' Apr 26 11:08:36 192.168.122.209 [68667.120788] [tdb] Close table 'sessions0.tdb' Apr 26 11:08:36 192.168.122.209 [68667.375150] [tdb] Close table 'filter0.tdb' Apr 26 11:08:36 192.168.122.209 [68667.375600] [tempesta fw] modules are stopped Apr 26 11:08:36 192.168.122.209 [68667.555358] [tempesta fw] exiting... Apr 26 11:08:36 192.168.122.209 [68667.659024] [tdb] Shutdown Tempesta DB Apr 26 11:08:38 192.168.122.209 [68668.703674] End test: t_sched.test_hash_stress.BindToServer.test_hash Apr 26 11:08:38 192.168.122.209 [68668.718050] Start test: t_sched.test_ratio_static.Ratio.test_load_distribution Apr 26 11:08:40 192.168.122.209 [68671.011496] [tdb] Start Tempesta DB Apr 26 11:08:40 192.168.122.209 [68671.149215] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:08:41 192.168.122.209 [68672.017959] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68672.017959] Maybe that's fine, but it's worth checking the [68672.017959] config - if there is no relations between the [68672.017959] names, then host name confusion attack is possible. Apr 26 11:08:41 192.168.122.209 [68672.344660] [tempesta fw] Configuration processing is completed. Apr 26 11:08:41 192.168.122.209 [68672.410617] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:08:41 192.168.122.209 [68672.450587] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:08:41 192.168.122.209 [68672.487024] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:08:42 192.168.122.209 [68672.784669] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:08:42 192.168.122.209 [68672.786469] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:08:42 192.168.122.209 [68672.844616] [tempesta fw] Tempesta FW is ready Apr 26 11:08:53 192.168.122.209 [68684.214967] [tdb] Close table 'client0.tdb' Apr 26 11:08:53 192.168.122.209 [68684.432277] [tdb] Close table 'sessions0.tdb' Apr 26 11:08:54 192.168.122.209 [68684.715803] [tdb] Close table 'filter0.tdb' Apr 26 11:08:54 192.168.122.209 [68684.716253] [tempesta fw] modules are stopped Apr 26 11:08:54 192.168.122.209 [68684.952087] [tempesta fw] exiting... Apr 26 11:08:54 192.168.122.209 [68685.086897] [tdb] Shutdown Tempesta DB Apr 26 11:08:54 192.168.122.209 [68685.575158] End test: t_sched.test_ratio_static.Ratio.test_load_distribution Apr 26 11:08:54 192.168.122.209 [68685.584090] Start test: t_sched.test_ratio_static.RatioVariableConns.test_load_distribution Apr 26 11:08:57 192.168.122.209 [68688.312813] [tdb] Start Tempesta DB Apr 26 11:08:57 192.168.122.209 [68688.487409] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:08:58 192.168.122.209 [68689.385513] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68689.385513] Maybe that's fine, but it's worth checking the [68689.385513] config - if there is no relations between the [68689.385513] names, then host name confusion attack is possible. Apr 26 11:08:59 192.168.122.209 [68689.696896] [tempesta fw] Configuration processing is completed. Apr 26 11:08:59 192.168.122.209 [68689.791421] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:08:59 192.168.122.209 [68689.848415] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:08:59 192.168.122.209 [68689.903976] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:08:59 192.168.122.209 [68690.212900] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:08:59 192.168.122.209 [68690.214766] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:08:59 192.168.122.209 [68690.284847] [tempesta fw] Tempesta FW is ready Apr 26 11:09:10 192.168.122.209 [68701.548036] [tdb] Close table 'client0.tdb' Apr 26 11:09:11 192.168.122.209 [68701.765480] [tdb] Close table 'sessions0.tdb' Apr 26 11:09:11 192.168.122.209 [68702.026661] [tdb] Close table 'filter0.tdb' Apr 26 11:09:11 192.168.122.209 [68702.027098] [tempesta fw] modules are stopped Apr 26 11:09:11 192.168.122.209 [68702.204111] [tempesta fw] exiting... Apr 26 11:09:11 192.168.122.209 [68702.329449] [tdb] Shutdown Tempesta DB Apr 26 11:09:12 192.168.122.209 [68702.880154] End test: t_sched.test_ratio_static.RatioVariableConns.test_load_distribution Apr 26 11:09:12 192.168.122.209 [68702.906818] Start test: t_sched.test_ratio_weight.Ratio.test_load_distribution Apr 26 11:09:14 192.168.122.209 [68705.638467] [tdb] Start Tempesta DB Apr 26 11:09:15 192.168.122.209 [68705.819556] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:09:16 192.168.122.209 [68707.134992] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68707.134992] Maybe that's fine, but it's worth checking the [68707.134992] config - if there is no relations between the [68707.134992] names, then host name confusion attack is possible. Apr 26 11:09:21 192.168.122.209 [68711.917480] [tempesta fw] Configuration processing is completed. Apr 26 11:09:21 192.168.122.209 [68711.972373] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:09:21 192.168.122.209 [68712.001199] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:09:21 192.168.122.209 [68712.029562] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:09:21 192.168.122.209 [68712.313115] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:09:21 192.168.122.209 [68712.315001] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:09:21 192.168.122.209 [68712.361062] [tempesta fw] Tempesta FW is ready Apr 26 11:09:32 192.168.122.209 [68723.638510] [tdb] Close table 'client0.tdb' Apr 26 11:09:33 192.168.122.209 [68723.841451] [tdb] Close table 'sessions0.tdb' Apr 26 11:09:33 192.168.122.209 [68724.096443] [tdb] Close table 'filter0.tdb' Apr 26 11:09:33 192.168.122.209 [68724.096844] [tempesta fw] modules are stopped Apr 26 11:09:33 192.168.122.209 [68724.335767] [tempesta fw] exiting... Apr 26 11:09:33 192.168.122.209 [68724.467727] [tdb] Shutdown Tempesta DB Apr 26 11:09:34 192.168.122.209 [68725.116266] End test: t_sched.test_ratio_weight.Ratio.test_load_distribution Apr 26 11:09:34 192.168.122.209 [68725.131760] Start test: t_sched.test_ratio_weight.RatioVariableConns.test_load_distribution Apr 26 11:09:36 192.168.122.209 [68727.667840] [tdb] Start Tempesta DB Apr 26 11:09:37 192.168.122.209 [68727.829072] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:09:38 192.168.122.209 [68728.786704] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68728.786704] Maybe that's fine, but it's worth checking the [68728.786704] config - if there is no relations between the [68728.786704] names, then host name confusion attack is possible. Apr 26 11:09:38 192.168.122.209 [68729.165420] [tempesta fw] Configuration processing is completed. Apr 26 11:09:38 192.168.122.209 [68729.225098] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:09:38 192.168.122.209 [68729.263215] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:09:38 192.168.122.209 [68729.302999] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:09:38 192.168.122.209 [68729.529400] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:09:38 192.168.122.209 [68729.531231] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:09:38 192.168.122.209 [68729.569334] [tempesta fw] Tempesta FW is ready Apr 26 11:09:50 192.168.122.209 [68740.906743] [tdb] Close table 'client0.tdb' Apr 26 11:09:50 192.168.122.209 [68741.091659] [tdb] Close table 'sessions0.tdb' Apr 26 11:09:50 192.168.122.209 [68741.320310] [tdb] Close table 'filter0.tdb' Apr 26 11:09:50 192.168.122.209 [68741.320727] [tempesta fw] modules are stopped Apr 26 11:09:50 192.168.122.209 [68741.503790] [tempesta fw] exiting... Apr 26 11:09:50 192.168.122.209 [68741.668470] [tdb] Shutdown Tempesta DB Apr 26 11:09:51 192.168.122.209 [68742.133523] End test: t_sched.test_ratio_weight.RatioVariableConns.test_load_distribution Apr 26 11:09:51 192.168.122.209 [68742.151292] Start test: t_sched.test_reconnection_logic.ReconnectionLogic.test_reconnection_to_primary_server Apr 26 11:09:52 192.168.122.209 [68743.428755] [tdb] Start Tempesta DB Apr 26 11:09:52 192.168.122.209 [68743.594150] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:09:53 192.168.122.209 [68744.442886] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68744.442886] Maybe that's fine, but it's worth checking the [68744.442886] config - if there is no relations between the [68744.442886] names, then host name confusion attack is possible. Apr 26 11:09:53 192.168.122.209 [68744.625686] [tempesta fw] Configuration processing is completed. Apr 26 11:09:54 192.168.122.209 [68744.684825] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:09:54 192.168.122.209 [68745.405137] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:09:54 192.168.122.209 [68745.451087] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:09:54 192.168.122.209 [68745.498047] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:09:54 192.168.122.209 [68745.557546] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:09:54 192.168.122.209 [68745.559378] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:09:54 192.168.122.209 [68745.597542] [tempesta fw] Tempesta FW is ready Apr 26 11:09:55 192.168.122.209 [68746.328883] [tdb] Close table 'client0.tdb' Apr 26 11:09:55 192.168.122.209 [68746.514051] [tdb] Close table 'sessions0.tdb' Apr 26 11:09:59 192.168.122.209 [68749.691722] [tdb] Close table 'cache0.tdb' Apr 26 11:09:59 192.168.122.209 [68749.917790] [tdb] Close table 'filter0.tdb' Apr 26 11:09:59 192.168.122.209 [68749.918199] [tempesta fw] modules are stopped Apr 26 11:09:59 192.168.122.209 [68750.150738] [tempesta fw] exiting... Apr 26 11:09:59 192.168.122.209 [68750.269382] [tdb] Shutdown Tempesta DB Apr 26 11:09:59 192.168.122.209 [68750.477374] End test: t_sched.test_reconnection_logic.ReconnectionLogic.test_reconnection_to_primary_server Apr 26 11:09:59 192.168.122.209 [68750.500192] Start test: t_tcp_options.test_tcp_options.TestTcpOptionsH2.test_large_response_tcp_mtu_probing_1500 Apr 26 11:10:01 192.168.122.209 [68752.000442] [tdb] Start Tempesta DB Apr 26 11:10:01 192.168.122.209 [68752.141778] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:10:03 192.168.122.209 [68753.691058] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68753.691058] Maybe that's fine, but it's worth checking the [68753.691058] config - if there is no relations between the [68753.691058] names, then host name confusion attack is possible. Apr 26 11:10:03 192.168.122.209 [68753.789742] [tempesta fw] Configuration processing is completed. Apr 26 11:10:03 192.168.122.209 [68753.847555] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:10:03 192.168.122.209 [68754.320089] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:10:03 192.168.122.209 [68754.353711] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:10:03 192.168.122.209 [68754.383580] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:10:03 192.168.122.209 [68754.498028] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:10:03 192.168.122.209 [68754.499817] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:10:03 192.168.122.209 [68754.581699] [tempesta fw] Tempesta FW is ready Apr 26 11:10:29 192.168.122.209 [68780.142674] [tdb] Close table 'client0.tdb' Apr 26 11:10:29 192.168.122.209 [68780.334929] [tdb] Close table 'sessions0.tdb' Apr 26 11:10:33 192.168.122.209 [68784.082203] [tdb] Close table 'cache0.tdb' Apr 26 11:10:33 192.168.122.209 [68784.384035] [tdb] Close table 'filter0.tdb' Apr 26 11:10:33 192.168.122.209 [68784.384530] [tempesta fw] modules are stopped Apr 26 11:10:33 192.168.122.209 [68784.635819] [tempesta fw] exiting... Apr 26 11:10:34 192.168.122.209 [68784.777771] [tdb] Shutdown Tempesta DB Apr 26 11:10:34 192.168.122.209 [68785.040088] End test: t_tcp_options.test_tcp_options.TestTcpOptionsH2.test_large_response_tcp_mtu_probing_1500 Apr 26 11:10:34 192.168.122.209 [68785.058051] Start test: t_tcp_options.test_tcp_options.TestTcpOptionsHttp.test_large_response_tcp_mtu_probing_1500 Apr 26 11:10:35 192.168.122.209 [68786.602169] [tdb] Start Tempesta DB Apr 26 11:10:36 192.168.122.209 [68786.756159] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:10:37 192.168.122.209 [68788.187581] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68788.187581] Maybe that's fine, but it's worth checking the [68788.187581] config - if there is no relations between the [68788.187581] names, then host name confusion attack is possible. Apr 26 11:10:37 192.168.122.209 [68788.294508] [tempesta fw] Configuration processing is completed. Apr 26 11:10:37 192.168.122.209 [68788.359932] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:10:38 192.168.122.209 [68788.941767] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:10:38 192.168.122.209 [68788.977797] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:10:38 192.168.122.209 [68789.013746] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:10:38 192.168.122.209 [68789.106222] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:10:38 192.168.122.209 [68789.108240] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:10:38 192.168.122.209 [68789.154069] [tempesta fw] Tempesta FW is ready Apr 26 11:11:01 192.168.122.209 [68812.109746] [tdb] Close table 'client0.tdb' Apr 26 11:11:01 192.168.122.209 [68812.314451] [tdb] Close table 'sessions0.tdb' Apr 26 11:11:05 192.168.122.209 [68815.799371] [tdb] Close table 'cache0.tdb' Apr 26 11:11:05 192.168.122.209 [68816.065811] [tdb] Close table 'filter0.tdb' Apr 26 11:11:05 192.168.122.209 [68816.066254] [tempesta fw] modules are stopped Apr 26 11:11:05 192.168.122.209 [68816.233500] [tempesta fw] exiting... Apr 26 11:11:05 192.168.122.209 [68816.366106] [tdb] Shutdown Tempesta DB Apr 26 11:11:05 192.168.122.209 [68816.577630] End test: t_tcp_options.test_tcp_options.TestTcpOptionsHttp.test_large_response_tcp_mtu_probing_1500 Apr 26 11:11:05 192.168.122.209 [68816.594938] Start test: t_tcp_options.test_tcp_options.TestTcpOptionsHttps.test_large_response_tcp_mtu_probing_1500 Apr 26 11:11:07 192.168.122.209 [68817.888399] [tdb] Start Tempesta DB Apr 26 11:11:07 192.168.122.209 [68818.041023] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:11:08 192.168.122.209 [68819.419950] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68819.419950] Maybe that's fine, but it's worth checking the [68819.419950] config - if there is no relations between the [68819.419950] names, then host name confusion attack is possible. Apr 26 11:11:08 192.168.122.209 [68819.530663] [tempesta fw] Configuration processing is completed. Apr 26 11:11:08 192.168.122.209 [68819.599293] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:11:09 192.168.122.209 [68820.229316] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:11:09 192.168.122.209 [68820.263443] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:11:09 192.168.122.209 [68820.299089] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:11:09 192.168.122.209 [68820.374598] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:11:09 192.168.122.209 [68820.376322] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:11:09 192.168.122.209 [68820.414513] [tempesta fw] Tempesta FW is ready Apr 26 11:11:37 192.168.122.209 [68848.378824] [tdb] Close table 'client0.tdb' Apr 26 11:11:37 192.168.122.209 [68848.565507] [tdb] Close table 'sessions0.tdb' Apr 26 11:11:41 192.168.122.209 [68851.778201] [tdb] Close table 'cache0.tdb' Apr 26 11:11:41 192.168.122.209 [68852.013173] [tdb] Close table 'filter0.tdb' Apr 26 11:11:41 192.168.122.209 [68852.013608] [tempesta fw] modules are stopped Apr 26 11:11:41 192.168.122.209 [68852.215063] [tempesta fw] exiting... Apr 26 11:11:41 192.168.122.209 [68852.339547] [tdb] Shutdown Tempesta DB Apr 26 11:11:41 192.168.122.209 [68852.545035] End test: t_tcp_options.test_tcp_options.TestTcpOptionsHttps.test_large_response_tcp_mtu_probing_1500 Apr 26 11:11:41 192.168.122.209 [68852.560496] Start test: t_wrong_body_length.test_request_wrong_length.RequestCorrectBodyLength.test_post_request Apr 26 11:11:42 192.168.122.209 [68853.611786] [tdb] Start Tempesta DB Apr 26 11:11:43 192.168.122.209 [68853.745068] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:11:44 192.168.122.209 [68855.300462] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68855.300462] Maybe that's fine, but it's worth checking the [68855.300462] config - if there is no relations between the [68855.300462] names, then host name confusion attack is possible. Apr 26 11:11:44 192.168.122.209 [68855.471088] [tempesta fw] Configuration processing is completed. Apr 26 11:11:44 192.168.122.209 [68855.527458] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:11:44 192.168.122.209 [68855.559298] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:11:44 192.168.122.209 [68855.589230] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:11:44 192.168.122.209 [68855.643046] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:11:44 192.168.122.209 [68855.644825] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:11:45 192.168.122.209 [68855.698977] [tempesta fw] Tempesta FW is ready Apr 26 11:11:45 192.168.122.209 [68856.278521] [tdb] Close table 'client0.tdb' Apr 26 11:11:45 192.168.122.209 [68856.482237] [tdb] Close table 'sessions0.tdb' Apr 26 11:11:46 192.168.122.209 [68856.695293] [tdb] Close table 'filter0.tdb' Apr 26 11:11:46 192.168.122.209 [68856.695723] [tempesta fw] modules are stopped Apr 26 11:11:46 192.168.122.209 [68856.959198] [tempesta fw] exiting... Apr 26 11:11:46 192.168.122.209 [68857.069378] [tdb] Shutdown Tempesta DB Apr 26 11:11:46 192.168.122.209 [68857.257572] End test: t_wrong_body_length.test_request_wrong_length.RequestCorrectBodyLength.test_post_request Apr 26 11:11:46 192.168.122.209 [68857.273926] Start test: t_wrong_body_length.test_request_wrong_length.RequestCorrectBodyLength.test_put_request Apr 26 11:11:47 192.168.122.209 [68858.225471] [tdb] Start Tempesta DB Apr 26 11:11:47 192.168.122.209 [68858.358878] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:11:48 192.168.122.209 [68859.084173] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68859.084173] Maybe that's fine, but it's worth checking the [68859.084173] config - if there is no relations between the [68859.084173] names, then host name confusion attack is possible. Apr 26 11:11:48 192.168.122.209 [68859.267094] [tempesta fw] Configuration processing is completed. Apr 26 11:11:48 192.168.122.209 [68859.317296] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:11:48 192.168.122.209 [68859.344315] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:11:48 192.168.122.209 [68859.373240] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:11:48 192.168.122.209 [68859.443090] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:11:48 192.168.122.209 [68859.444837] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:11:48 192.168.122.209 [68859.487033] [tempesta fw] Tempesta FW is ready Apr 26 11:11:49 192.168.122.209 [68860.106045] [tdb] Close table 'client0.tdb' Apr 26 11:11:49 192.168.122.209 [68860.289873] [tdb] Close table 'sessions0.tdb' Apr 26 11:11:49 192.168.122.209 [68860.542609] [tdb] Close table 'filter0.tdb' Apr 26 11:11:49 192.168.122.209 [68860.543061] [tempesta fw] modules are stopped Apr 26 11:11:50 192.168.122.209 [68860.727918] [tempesta fw] exiting... Apr 26 11:11:50 192.168.122.209 [68860.869109] [tdb] Shutdown Tempesta DB Apr 26 11:11:50 192.168.122.209 [68861.073115] End test: t_wrong_body_length.test_request_wrong_length.RequestCorrectBodyLength.test_put_request Apr 26 11:11:50 192.168.122.209 [68861.090052] Start test: t_wrong_body_length.test_request_wrong_length.RequestDecimalBodyLength.test_post_request Apr 26 11:11:51 192.168.122.209 [68862.077135] [tdb] Start Tempesta DB Apr 26 11:11:51 192.168.122.209 [68862.214997] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:11:52 192.168.122.209 [68862.976402] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68862.976402] Maybe that's fine, but it's worth checking the [68862.976402] config - if there is no relations between the [68862.976402] names, then host name confusion attack is possible. Apr 26 11:11:52 192.168.122.209 [68863.147198] [tempesta fw] Configuration processing is completed. Apr 26 11:11:52 192.168.122.209 [68863.204099] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:11:52 192.168.122.209 [68863.236494] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:11:52 192.168.122.209 [68863.267330] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:11:52 192.168.122.209 [68863.327153] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:11:52 192.168.122.209 [68863.328907] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:11:52 192.168.122.209 [68863.371085] [tempesta fw] Tempesta FW is ready Apr 26 11:11:52 192.168.122.209 [68863.512832] [tempesta fw] Warning: Parser error: state=Req_HdrContent_LengthV input(-0)=0x2e('.') data_len=1 off=0 Apr 26 11:11:53 192.168.122.209 [68863.942442] [tdb] Close table 'client0.tdb' Apr 26 11:11:53 192.168.122.209 [68864.144012] [tdb] Close table 'sessions0.tdb' Apr 26 11:11:53 192.168.122.209 [68864.407699] [tdb] Close table 'filter0.tdb' Apr 26 11:11:53 192.168.122.209 [68864.408131] [tempesta fw] modules are stopped Apr 26 11:11:53 192.168.122.209 [68864.621268] [tempesta fw] exiting... Apr 26 11:11:54 192.168.122.209 [68864.744067] [tdb] Shutdown Tempesta DB Apr 26 11:11:54 192.168.122.209 [68864.922258] End test: t_wrong_body_length.test_request_wrong_length.RequestDecimalBodyLength.test_post_request Apr 26 11:11:54 192.168.122.209 [68864.937636] Start test: t_wrong_body_length.test_request_wrong_length.RequestDecimalBodyLength.test_put_request Apr 26 11:11:55 192.168.122.209 [68865.942272] [tdb] Start Tempesta DB Apr 26 11:11:55 192.168.122.209 [68866.077602] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:11:56 192.168.122.209 [68866.888421] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68866.888421] Maybe that's fine, but it's worth checking the [68866.888421] config - if there is no relations between the [68866.888421] names, then host name confusion attack is possible. Apr 26 11:11:56 192.168.122.209 [68867.055185] [tempesta fw] Configuration processing is completed. Apr 26 11:11:56 192.168.122.209 [68867.112482] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:11:56 192.168.122.209 [68867.145844] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:11:56 192.168.122.209 [68867.176205] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:11:56 192.168.122.209 [68867.223189] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:11:56 192.168.122.209 [68867.224914] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:11:56 192.168.122.209 [68867.283073] [tempesta fw] Tempesta FW is ready Apr 26 11:11:56 192.168.122.209 [68867.420202] [tempesta fw] Warning: Parser error: state=Req_HdrContent_LengthV input(-0)=0x2e('.') data_len=1 off=0 Apr 26 11:11:57 192.168.122.209 [68867.864007] [tdb] Close table 'client0.tdb' Apr 26 11:11:57 192.168.122.209 [68868.049696] [tdb] Close table 'sessions0.tdb' Apr 26 11:11:57 192.168.122.209 [68868.306680] [tdb] Close table 'filter0.tdb' Apr 26 11:11:57 192.168.122.209 [68868.307126] [tempesta fw] modules are stopped Apr 26 11:11:57 192.168.122.209 [68868.524269] [tempesta fw] exiting... Apr 26 11:11:57 192.168.122.209 [68868.651332] [tdb] Shutdown Tempesta DB Apr 26 11:11:58 192.168.122.209 [68868.862358] End test: t_wrong_body_length.test_request_wrong_length.RequestDecimalBodyLength.test_put_request Apr 26 11:11:58 192.168.122.209 [68868.873873] Start test: t_wrong_body_length.test_request_wrong_length.RequestDuplicateBodyLength.test_post_request Apr 26 11:11:59 192.168.122.209 [68869.850697] [tdb] Start Tempesta DB Apr 26 11:11:59 192.168.122.209 [68869.996561] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:12:00 192.168.122.209 [68870.776632] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68870.776632] Maybe that's fine, but it's worth checking the [68870.776632] config - if there is no relations between the [68870.776632] names, then host name confusion attack is possible. Apr 26 11:12:00 192.168.122.209 [68870.947340] [tempesta fw] Configuration processing is completed. Apr 26 11:12:00 192.168.122.209 [68870.998521] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:12:00 192.168.122.209 [68871.025461] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:12:00 192.168.122.209 [68871.052123] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:12:00 192.168.122.209 [68871.099240] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:12:00 192.168.122.209 [68871.101001] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:12:00 192.168.122.209 [68871.143180] [tempesta fw] Tempesta FW is ready Apr 26 11:12:00 192.168.122.209 [68871.285159] [tempesta fw] Warning: Parser error: state=Req_HdrContent_LengthV input(-0)=0x2c(',') data_len=1 off=0 Apr 26 11:12:01 192.168.122.209 [68871.723743] [tdb] Close table 'client0.tdb' Apr 26 11:12:01 192.168.122.209 [68871.891935] [tdb] Close table 'sessions0.tdb' Apr 26 11:12:01 192.168.122.209 [68872.114598] [tdb] Close table 'filter0.tdb' Apr 26 11:12:01 192.168.122.209 [68872.115016] [tempesta fw] modules are stopped Apr 26 11:12:01 192.168.122.209 [68872.326867] [tempesta fw] exiting... Apr 26 11:12:01 192.168.122.209 [68872.454683] [tdb] Shutdown Tempesta DB Apr 26 11:12:02 192.168.122.209 [68872.674968] End test: t_wrong_body_length.test_request_wrong_length.RequestDuplicateBodyLength.test_post_request Apr 26 11:12:02 192.168.122.209 [68872.686654] Start test: t_wrong_body_length.test_request_wrong_length.RequestDuplicateBodyLength.test_put_request Apr 26 11:12:03 192.168.122.209 [68873.701703] [tdb] Start Tempesta DB Apr 26 11:12:03 192.168.122.209 [68873.836663] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:12:03 192.168.122.209 [68874.628627] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68874.628627] Maybe that's fine, but it's worth checking the [68874.628627] config - if there is no relations between the [68874.628627] names, then host name confusion attack is possible. Apr 26 11:12:04 192.168.122.209 [68874.807224] [tempesta fw] Configuration processing is completed. Apr 26 11:12:04 192.168.122.209 [68874.866292] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:12:04 192.168.122.209 [68874.899673] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:12:04 192.168.122.209 [68874.930638] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:12:04 192.168.122.209 [68875.023301] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:12:04 192.168.122.209 [68875.025128] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:12:04 192.168.122.209 [68875.075255] [tempesta fw] Tempesta FW is ready Apr 26 11:12:04 192.168.122.209 [68875.223957] [tempesta fw] Warning: Parser error: state=Req_HdrContent_LengthV input(-0)=0x2c(',') data_len=1 off=0 Apr 26 11:12:04 192.168.122.209 [68875.646440] [tdb] Close table 'client0.tdb' Apr 26 11:12:05 192.168.122.209 [68875.828813] [tdb] Close table 'sessions0.tdb' Apr 26 11:12:05 192.168.122.209 [68876.061230] [tdb] Close table 'filter0.tdb' Apr 26 11:12:05 192.168.122.209 [68876.061660] [tempesta fw] modules are stopped Apr 26 11:12:05 192.168.122.209 [68876.275529] [tempesta fw] exiting... Apr 26 11:12:05 192.168.122.209 [68876.415653] [tdb] Shutdown Tempesta DB Apr 26 11:12:05 192.168.122.209 [68876.604803] End test: t_wrong_body_length.test_request_wrong_length.RequestDuplicateBodyLength.test_put_request Apr 26 11:12:05 192.168.122.209 [68876.616209] Start test: t_wrong_body_length.test_request_wrong_length.RequestEmptyBodyLength.test_post_request Apr 26 11:12:06 192.168.122.209 [68877.644236] [tdb] Start Tempesta DB Apr 26 11:12:07 192.168.122.209 [68877.774613] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:12:07 192.168.122.209 [68878.476747] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68878.476747] Maybe that's fine, but it's worth checking the [68878.476747] config - if there is no relations between the [68878.476747] names, then host name confusion attack is possible. Apr 26 11:12:07 192.168.122.209 [68878.639373] [tempesta fw] Configuration processing is completed. Apr 26 11:12:08 192.168.122.209 [68878.696646] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:12:08 192.168.122.209 [68878.729520] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:12:08 192.168.122.209 [68878.759349] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:12:08 192.168.122.209 [68878.799332] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:12:08 192.168.122.209 [68878.801113] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:12:08 192.168.122.209 [68878.843282] [tempesta fw] Tempesta FW is ready Apr 26 11:12:08 192.168.122.209 [68878.996330] [tempesta fw] Warning: Parser error: state=Req_HdrContent_LengthV input(-0)=0xd(' ') data_len=1 off=0 Apr 26 11:12:08 192.168.122.209 [68879.471863] [tdb] Close table 'client0.tdb' Apr 26 11:12:08 192.168.122.209 [68879.657618] [tdb] Close table 'sessions0.tdb' Apr 26 11:12:09 192.168.122.209 [68879.883199] [tdb] Close table 'filter0.tdb' Apr 26 11:12:09 192.168.122.209 [68879.883625] [tempesta fw] modules are stopped Apr 26 11:12:09 192.168.122.209 [68880.069109] [tempesta fw] exiting... Apr 26 11:12:09 192.168.122.209 [68880.177995] [tdb] Shutdown Tempesta DB Apr 26 11:12:09 192.168.122.209 [68880.395521] End test: t_wrong_body_length.test_request_wrong_length.RequestEmptyBodyLength.test_post_request Apr 26 11:12:09 192.168.122.209 [68880.405657] Start test: t_wrong_body_length.test_request_wrong_length.RequestEmptyBodyLength.test_put_request Apr 26 11:12:10 192.168.122.209 [68881.334251] [tdb] Start Tempesta DB Apr 26 11:12:10 192.168.122.209 [68881.466462] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:12:11 192.168.122.209 [68882.200864] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68882.200864] Maybe that's fine, but it's worth checking the [68882.200864] config - if there is no relations between the [68882.200864] names, then host name confusion attack is possible. Apr 26 11:12:11 192.168.122.209 [68882.371459] [tempesta fw] Configuration processing is completed. Apr 26 11:12:11 192.168.122.209 [68882.421767] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:12:11 192.168.122.209 [68882.450382] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:12:11 192.168.122.209 [68882.477454] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:12:11 192.168.122.209 [68882.519412] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:12:11 192.168.122.209 [68882.521136] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:12:11 192.168.122.209 [68882.579330] [tempesta fw] Tempesta FW is ready Apr 26 11:12:12 192.168.122.209 [68882.724429] [tempesta fw] Warning: Parser error: state=Req_HdrContent_LengthV input(-0)=0xd(' ') data_len=1 off=0 Apr 26 11:12:12 192.168.122.209 [68883.177556] [tdb] Close table 'client0.tdb' Apr 26 11:12:12 192.168.122.209 [68883.365694] [tdb] Close table 'sessions0.tdb' Apr 26 11:12:12 192.168.122.209 [68883.575472] [tdb] Close table 'filter0.tdb' Apr 26 11:12:12 192.168.122.209 [68883.575884] [tempesta fw] modules are stopped Apr 26 11:12:13 192.168.122.209 [68883.788519] [tempesta fw] exiting... Apr 26 11:12:13 192.168.122.209 [68883.912252] [tdb] Shutdown Tempesta DB Apr 26 11:12:13 192.168.122.209 [68884.152306] End test: t_wrong_body_length.test_request_wrong_length.RequestEmptyBodyLength.test_put_request Apr 26 11:12:13 192.168.122.209 [68884.164220] Start test: t_wrong_body_length.test_request_wrong_length.RequestInvalidBodyLength.test_post_request Apr 26 11:12:14 192.168.122.209 [68885.207169] [tdb] Start Tempesta DB Apr 26 11:12:14 192.168.122.209 [68885.348049] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:12:15 192.168.122.209 [68886.108705] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68886.108705] Maybe that's fine, but it's worth checking the [68886.108705] config - if there is no relations between the [68886.108705] names, then host name confusion attack is possible. Apr 26 11:12:15 192.168.122.209 [68886.291475] [tempesta fw] Configuration processing is completed. Apr 26 11:12:15 192.168.122.209 [68886.342773] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:12:15 192.168.122.209 [68886.371053] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:12:15 192.168.122.209 [68886.399819] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:12:15 192.168.122.209 [68886.447425] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:12:15 192.168.122.209 [68886.449178] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:12:15 192.168.122.209 [68886.491427] [tempesta fw] Tempesta FW is ready Apr 26 11:12:15 192.168.122.209 [68886.628840] [tempesta fw] Warning: Parser error: state=Req_HdrContent_LengthV input(-0)=0x69('i') data_len=1 off=0 Apr 26 11:12:16 192.168.122.209 [68887.055168] [tdb] Close table 'client0.tdb' Apr 26 11:12:16 192.168.122.209 [68887.239477] [tdb] Close table 'sessions0.tdb' Apr 26 11:12:16 192.168.122.209 [68887.467817] [tdb] Close table 'filter0.tdb' Apr 26 11:12:16 192.168.122.209 [68887.468263] [tempesta fw] modules are stopped Apr 26 11:12:16 192.168.122.209 [68887.659000] [tempesta fw] exiting... Apr 26 11:12:17 192.168.122.209 [68887.782081] [tdb] Shutdown Tempesta DB Apr 26 11:12:17 192.168.122.209 [68887.966003] End test: t_wrong_body_length.test_request_wrong_length.RequestInvalidBodyLength.test_post_request Apr 26 11:12:17 192.168.122.209 [68887.979809] Start test: t_wrong_body_length.test_request_wrong_length.RequestInvalidBodyLength.test_put_request Apr 26 11:12:18 192.168.122.209 [68888.988793] [tdb] Start Tempesta DB Apr 26 11:12:18 192.168.122.209 [68889.121716] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:12:19 192.168.122.209 [68889.892814] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68889.892814] Maybe that's fine, but it's worth checking the [68889.892814] config - if there is no relations between the [68889.892814] names, then host name confusion attack is possible. Apr 26 11:12:19 192.168.122.209 [68890.055443] [tempesta fw] Configuration processing is completed. Apr 26 11:12:19 192.168.122.209 [68890.117457] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:12:19 192.168.122.209 [68890.149350] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:12:19 192.168.122.209 [68890.178849] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:12:19 192.168.122.209 [68890.227490] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:12:19 192.168.122.209 [68890.229227] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:12:19 192.168.122.209 [68890.275451] [tempesta fw] Tempesta FW is ready Apr 26 11:12:19 192.168.122.209 [68890.427611] [tempesta fw] Warning: Parser error: state=Req_HdrContent_LengthV input(-0)=0x69('i') data_len=1 off=0 Apr 26 11:12:20 192.168.122.209 [68890.877551] [tdb] Close table 'client0.tdb' Apr 26 11:12:20 192.168.122.209 [68891.062740] [tdb] Close table 'sessions0.tdb' Apr 26 11:12:20 192.168.122.209 [68891.321357] [tdb] Close table 'filter0.tdb' Apr 26 11:12:20 192.168.122.209 [68891.321779] [tempesta fw] modules are stopped Apr 26 11:12:20 192.168.122.209 [68891.494128] [tempesta fw] exiting... Apr 26 11:12:20 192.168.122.209 [68891.600197] [tdb] Shutdown Tempesta DB Apr 26 11:12:21 192.168.122.209 [68891.830585] End test: t_wrong_body_length.test_request_wrong_length.RequestInvalidBodyLength.test_put_request Apr 26 11:12:21 192.168.122.209 [68891.841160] Start test: t_wrong_body_length.test_request_wrong_length.RequestLongBodyLength.test_post_request Apr 26 11:12:22 192.168.122.209 [68892.845508] [tdb] Start Tempesta DB Apr 26 11:12:22 192.168.122.209 [68892.976721] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:12:23 192.168.122.209 [68893.827558] [tempesta fw] Configuration processing is completed. Apr 26 11:12:23 192.168.122.209 [68893.884800] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:12:23 192.168.122.209 [68893.917753] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:12:23 192.168.122.209 [68893.947990] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:12:23 192.168.122.209 [68893.991521] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:12:23 192.168.122.209 [68894.035491] [tempesta fw] Tempesta FW is ready Apr 26 11:12:24 192.168.122.209 [68895.607981] [tdb] Close table 'client0.tdb' Apr 26 11:12:25 192.168.122.209 [68895.792181] [tdb] Close table 'sessions0.tdb' Apr 26 11:12:25 192.168.122.209 [68896.041966] [tdb] Close table 'filter0.tdb' Apr 26 11:12:25 192.168.122.209 [68896.042414] [tempesta fw] modules are stopped Apr 26 11:12:25 192.168.122.209 [68896.244590] [tempesta fw] exiting... Apr 26 11:12:25 192.168.122.209 [68896.350494] [tdb] Shutdown Tempesta DB Apr 26 11:12:25 192.168.122.209 [68896.532531] End test: t_wrong_body_length.test_request_wrong_length.RequestLongBodyLength.test_post_request Apr 26 11:12:25 192.168.122.209 [68896.541270] Start test: t_wrong_body_length.test_request_wrong_length.RequestLongBodyLength.test_put_request Apr 26 11:12:26 192.168.122.209 [68897.546161] [tdb] Start Tempesta DB Apr 26 11:12:27 192.168.122.209 [68897.672326] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:12:27 192.168.122.209 [68898.563885] [tempesta fw] Configuration processing is completed. Apr 26 11:12:27 192.168.122.209 [68898.616127] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:12:27 192.168.122.209 [68898.645246] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:12:28 192.168.122.209 [68898.672847] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:12:28 192.168.122.209 [68898.719596] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:12:28 192.168.122.209 [68898.759579] [tempesta fw] Tempesta FW is ready Apr 26 11:12:29 192.168.122.209 [68900.342666] [tdb] Close table 'client0.tdb' Apr 26 11:12:29 192.168.122.209 [68900.535370] [tdb] Close table 'sessions0.tdb' Apr 26 11:12:30 192.168.122.209 [68900.784507] [tdb] Close table 'filter0.tdb' Apr 26 11:12:30 192.168.122.209 [68900.784922] [tempesta fw] modules are stopped Apr 26 11:12:30 192.168.122.209 [68900.976339] [tempesta fw] exiting... Apr 26 11:12:30 192.168.122.209 [68901.105568] [tdb] Shutdown Tempesta DB Apr 26 11:12:30 192.168.122.209 [68901.319655] End test: t_wrong_body_length.test_request_wrong_length.RequestLongBodyLength.test_put_request Apr 26 11:12:30 192.168.122.209 [68901.331823] Start test: t_wrong_body_length.test_request_wrong_length.RequestNegativeBodyLength.test_post_request Apr 26 11:12:31 192.168.122.209 [68902.266486] [tdb] Start Tempesta DB Apr 26 11:12:31 192.168.122.209 [68902.388079] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:12:32 192.168.122.209 [68903.029230] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68903.029230] Maybe that's fine, but it's worth checking the [68903.029230] config - if there is no relations between the [68903.029230] names, then host name confusion attack is possible. Apr 26 11:12:32 192.168.122.209 [68903.211703] [tempesta fw] Configuration processing is completed. Apr 26 11:12:32 192.168.122.209 [68903.262108] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:12:32 192.168.122.209 [68903.294781] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:12:32 192.168.122.209 [68903.322548] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:12:32 192.168.122.209 [68903.371666] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:12:32 192.168.122.209 [68903.373416] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:12:32 192.168.122.209 [68903.419630] [tempesta fw] Tempesta FW is ready Apr 26 11:12:32 192.168.122.209 [68903.561855] [tempesta fw] Warning: Parser error: state=Req_HdrContent_LengthV input(-0)=0x2d('-') data_len=1 off=0 Apr 26 11:12:33 192.168.122.209 [68904.006761] [tdb] Close table 'client0.tdb' Apr 26 11:12:33 192.168.122.209 [68904.188460] [tdb] Close table 'sessions0.tdb' Apr 26 11:12:33 192.168.122.209 [68904.412369] [tdb] Close table 'filter0.tdb' Apr 26 11:12:33 192.168.122.209 [68904.412783] [tempesta fw] modules are stopped Apr 26 11:12:33 192.168.122.209 [68904.610444] [tempesta fw] exiting... Apr 26 11:12:34 192.168.122.209 [68904.728502] [tdb] Shutdown Tempesta DB Apr 26 11:12:34 192.168.122.209 [68904.902707] End test: t_wrong_body_length.test_request_wrong_length.RequestNegativeBodyLength.test_post_request Apr 26 11:12:34 192.168.122.209 [68904.913723] Start test: t_wrong_body_length.test_request_wrong_length.RequestNegativeBodyLength.test_put_request Apr 26 11:12:35 192.168.122.209 [68905.824924] [tdb] Start Tempesta DB Apr 26 11:12:35 192.168.122.209 [68905.952160] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:12:35 192.168.122.209 [68906.621223] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68906.621223] Maybe that's fine, but it's worth checking the [68906.621223] config - if there is no relations between the [68906.621223] names, then host name confusion attack is possible. Apr 26 11:12:36 192.168.122.209 [68906.795727] [tempesta fw] Configuration processing is completed. Apr 26 11:12:36 192.168.122.209 [68906.852187] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:12:36 192.168.122.209 [68906.882346] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:12:36 192.168.122.209 [68906.912296] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:12:36 192.168.122.209 [68906.951710] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:12:36 192.168.122.209 [68906.953456] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:12:36 192.168.122.209 [68906.991655] [tempesta fw] Tempesta FW is ready Apr 26 11:12:36 192.168.122.209 [68907.130697] [tempesta fw] Warning: Parser error: state=Req_HdrContent_LengthV input(-0)=0x2d('-') data_len=1 off=0 Apr 26 11:12:36 192.168.122.209 [68907.566951] [tdb] Close table 'client0.tdb' Apr 26 11:12:37 192.168.122.209 [68907.752992] [tdb] Close table 'sessions0.tdb' Apr 26 11:12:37 192.168.122.209 [68907.994378] [tdb] Close table 'filter0.tdb' Apr 26 11:12:37 192.168.122.209 [68907.994798] [tempesta fw] modules are stopped Apr 26 11:12:37 192.168.122.209 [68908.181259] [tempesta fw] exiting... Apr 26 11:12:37 192.168.122.209 [68908.294237] [tdb] Shutdown Tempesta DB Apr 26 11:12:37 192.168.122.209 [68908.502422] End test: t_wrong_body_length.test_request_wrong_length.RequestNegativeBodyLength.test_put_request Apr 26 11:12:37 192.168.122.209 [68908.510386] Start test: t_wrong_body_length.test_request_wrong_length.RequestSecondBodyLength.test_post_request Apr 26 11:12:38 192.168.122.209 [68909.548675] [tdb] Start Tempesta DB Apr 26 11:12:39 192.168.122.209 [68909.692624] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:12:39 192.168.122.209 [68910.449027] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68910.449027] Maybe that's fine, but it's worth checking the [68910.449027] config - if there is no relations between the [68910.449027] names, then host name confusion attack is possible. Apr 26 11:12:39 192.168.122.209 [68910.635785] [tempesta fw] Configuration processing is completed. Apr 26 11:12:40 192.168.122.209 [68910.697850] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:12:40 192.168.122.209 [68910.730554] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:12:40 192.168.122.209 [68910.760724] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:12:40 192.168.122.209 [68910.799754] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:12:40 192.168.122.209 [68910.801506] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:12:40 192.168.122.209 [68910.839706] [tempesta fw] Tempesta FW is ready Apr 26 11:12:40 192.168.122.209 [68910.989594] [tempesta fw] Warning: Parser error: state=Req_HdrContent_LengthV input(-0)=0x33('3') data_len=1 off=0 Apr 26 11:12:40 192.168.122.209 [68911.410475] [tdb] Close table 'client0.tdb' Apr 26 11:12:40 192.168.122.209 [68911.590378] [tdb] Close table 'sessions0.tdb' Apr 26 11:12:41 192.168.122.209 [68911.825537] [tdb] Close table 'filter0.tdb' Apr 26 11:12:41 192.168.122.209 [68911.825932] [tempesta fw] modules are stopped Apr 26 11:12:41 192.168.122.209 [68912.014885] [tempesta fw] exiting... Apr 26 11:12:41 192.168.122.209 [68912.131971] [tdb] Shutdown Tempesta DB Apr 26 11:12:41 192.168.122.209 [68912.308313] End test: t_wrong_body_length.test_request_wrong_length.RequestSecondBodyLength.test_post_request Apr 26 11:12:41 192.168.122.209 [68912.321685] Start test: t_wrong_body_length.test_request_wrong_length.RequestSecondBodyLength.test_put_request Apr 26 11:12:42 192.168.122.209 [68913.232573] [tdb] Start Tempesta DB Apr 26 11:12:42 192.168.122.209 [68913.370085] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:12:43 192.168.122.209 [68914.033220] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68914.033220] Maybe that's fine, but it's worth checking the [68914.033220] config - if there is no relations between the [68914.033220] names, then host name confusion attack is possible. Apr 26 11:12:43 192.168.122.209 [68914.203864] [tempesta fw] Configuration processing is completed. Apr 26 11:12:43 192.168.122.209 [68914.265557] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:12:43 192.168.122.209 [68914.300651] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:12:43 192.168.122.209 [68914.330342] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:12:43 192.168.122.209 [68914.371814] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:12:43 192.168.122.209 [68914.373567] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:12:43 192.168.122.209 [68914.419767] [tempesta fw] Tempesta FW is ready Apr 26 11:12:43 192.168.122.209 [68914.575226] [tempesta fw] Warning: Parser error: state=Req_HdrContent_LengthV input(-0)=0x33('3') data_len=1 off=0 Apr 26 11:12:44 192.168.122.209 [68914.998450] [tdb] Close table 'client0.tdb' Apr 26 11:12:44 192.168.122.209 [68915.199574] [tdb] Close table 'sessions0.tdb' Apr 26 11:12:44 192.168.122.209 [68915.425529] [tdb] Close table 'filter0.tdb' Apr 26 11:12:44 192.168.122.209 [68915.425994] [tempesta fw] modules are stopped Apr 26 11:12:44 192.168.122.209 [68915.632865] [tempesta fw] exiting... Apr 26 11:12:45 192.168.122.209 [68915.752889] [tdb] Shutdown Tempesta DB Apr 26 11:12:45 192.168.122.209 [68915.958703] End test: t_wrong_body_length.test_request_wrong_length.RequestSecondBodyLength.test_put_request Apr 26 11:12:45 192.168.122.209 [68915.968566] Start test: ws.test_ws_ping.WssPingMultipleListenersH2Https.test Apr 26 11:12:46 192.168.122.209 [68917.038359] [tdb] Start Tempesta DB Apr 26 11:12:46 192.168.122.209 [68917.171926] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:12:47 192.168.122.209 [68918.041436] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68918.041436] Maybe that's fine, but it's worth checking the [68918.041436] config - if there is no relations between the [68918.041436] names, then host name confusion attack is possible. Apr 26 11:12:47 192.168.122.209 [68918.159815] [tempesta fw] Configuration processing is completed. Apr 26 11:12:47 192.168.122.209 [68918.212409] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:12:47 192.168.122.209 [68918.668810] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:12:48 192.168.122.209 [68918.697409] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:12:48 192.168.122.209 [68918.733870] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:12:48 192.168.122.209 [68918.799865] [tempesta fw] Open listen socket on: 0.0.0.0:82 Apr 26 11:12:48 192.168.122.209 [68918.801582] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 11:12:48 192.168.122.209 [68918.839812] [tempesta fw] Tempesta FW is ready Apr 26 11:12:48 192.168.122.209 [68919.507099] [tdb] Close table 'client0.tdb' Apr 26 11:12:49 192.168.122.209 [68919.695205] [tdb] Close table 'sessions0.tdb' Apr 26 11:12:52 192.168.122.209 [68922.783756] [tdb] Close table 'cache0.tdb' Apr 26 11:12:52 192.168.122.209 [68923.039390] [tdb] Close table 'filter0.tdb' Apr 26 11:12:52 192.168.122.209 [68923.040190] [tempesta fw] modules are stopped Apr 26 11:12:52 192.168.122.209 [68923.257197] [tempesta fw] exiting... Apr 26 11:12:52 192.168.122.209 [68923.404608] [tdb] Shutdown Tempesta DB Apr 26 11:12:52 192.168.122.209 [68923.636753] End test: ws.test_ws_ping.WssPingMultipleListenersH2Https.test Apr 26 11:12:52 192.168.122.209 [68923.655652] Start test: ws.test_ws_ping.WssPingMultipleListenersHttpsH2.test Apr 26 11:12:54 192.168.122.209 [68924.761657] [tdb] Start Tempesta DB Apr 26 11:12:54 192.168.122.209 [68924.898796] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:12:55 192.168.122.209 [68926.497608] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68926.497608] Maybe that's fine, but it's worth checking the [68926.497608] config - if there is no relations between the [68926.497608] names, then host name confusion attack is possible. Apr 26 11:12:55 192.168.122.209 [68926.615972] [tempesta fw] Configuration processing is completed. Apr 26 11:12:55 192.168.122.209 [68926.670173] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:12:56 192.168.122.209 [68927.103607] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:12:56 192.168.122.209 [68927.140036] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:12:56 192.168.122.209 [68927.166821] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:12:56 192.168.122.209 [68927.235972] [tempesta fw] Open listen socket on: 0.0.0.0:82 Apr 26 11:12:56 192.168.122.209 [68927.237620] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 11:12:56 192.168.122.209 [68927.295908] [tempesta fw] Tempesta FW is ready Apr 26 11:12:57 192.168.122.209 [68927.984364] [tdb] Close table 'client0.tdb' Apr 26 11:12:57 192.168.122.209 [68928.176878] [tdb] Close table 'sessions0.tdb' Apr 26 11:13:00 192.168.122.209 [68931.329251] [tdb] Close table 'cache0.tdb' Apr 26 11:13:00 192.168.122.209 [68931.545963] [tdb] Close table 'filter0.tdb' Apr 26 11:13:00 192.168.122.209 [68931.546353] [tempesta fw] modules are stopped Apr 26 11:13:01 192.168.122.209 [68931.751367] [tempesta fw] exiting... Apr 26 11:13:01 192.168.122.209 [68931.911364] [tdb] Shutdown Tempesta DB Apr 26 11:13:01 192.168.122.209 [68932.136702] End test: ws.test_ws_ping.WssPingMultipleListenersHttpsH2.test Apr 26 11:13:01 192.168.122.209 [68932.149375] Start test: ws.test_ws_ping.WssPipelining.test Apr 26 11:13:02 192.168.122.209 [68933.310840] [tdb] Start Tempesta DB Apr 26 11:13:02 192.168.122.209 [68933.453581] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:13:04 192.168.122.209 [68935.065662] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68935.065662] Maybe that's fine, but it's worth checking the [68935.065662] config - if there is no relations between the [68935.065662] names, then host name confusion attack is possible. Apr 26 11:13:04 192.168.122.209 [68935.180069] [tempesta fw] Configuration processing is completed. Apr 26 11:13:04 192.168.122.209 [68935.238386] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:13:05 192.168.122.209 [68935.679666] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:13:05 192.168.122.209 [68935.708652] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:13:05 192.168.122.209 [68935.735418] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:13:05 192.168.122.209 [68935.808086] [tempesta fw] Open listen socket on: 0.0.0.0:82 Apr 26 11:13:05 192.168.122.209 [68935.809753] [tempesta fw] Open listen socket on: 0.0.0.0:81 Apr 26 11:13:05 192.168.122.209 [68935.848033] [tempesta fw] Tempesta FW is ready Apr 26 11:13:10 192.168.122.209 [68941.064149] [tempesta fw] Warning: Request dropped: Pipelined request received after UPGRADE request: 127.0.0.2 Apr 26 11:13:11 192.168.122.209 [68941.768990] [tdb] Close table 'client0.tdb' Apr 26 11:13:11 192.168.122.209 [68941.940002] [tdb] Close table 'sessions0.tdb' Apr 26 11:13:14 192.168.122.209 [68945.192144] [tdb] Close table 'cache0.tdb' Apr 26 11:13:14 192.168.122.209 [68945.449186] [tdb] Close table 'filter0.tdb' Apr 26 11:13:14 192.168.122.209 [68945.449626] [tempesta fw] modules are stopped Apr 26 11:13:14 192.168.122.209 [68945.646377] [tempesta fw] exiting... Apr 26 11:13:15 192.168.122.209 [68945.763019] [tdb] Shutdown Tempesta DB Apr 26 11:13:15 192.168.122.209 [68945.989400] End test: ws.test_ws_ping.WssPipelining.test Apr 26 11:13:16 192.168.122.209 [68947.051185] [tdb] Start Tempesta DB Apr 26 11:13:16 192.168.122.209 [68947.197727] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:13:17 192.168.122.209 [68948.286685] [tempesta fw] Configuration processing is completed. Apr 26 11:13:17 192.168.122.209 [68948.343852] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:13:18 192.168.122.209 [68948.785967] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:13:18 192.168.122.209 [68948.814290] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:13:18 192.168.122.209 [68948.843287] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:13:18 192.168.122.209 [68948.844518] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:13:18 192.168.122.209 [68948.872529] [tempesta fw] Tempesta FW is ready Apr 26 11:13:23 192.168.122.209 [68954.539228] [tdb] Close table 'client0.tdb' Apr 26 11:13:24 192.168.122.209 [68954.724715] [tdb] Close table 'sessions0.tdb' Apr 26 11:13:27 192.168.122.209 [68957.923182] [tdb] Close table 'cache0.tdb' Apr 26 11:13:27 192.168.122.209 [68958.174252] [tdb] Close table 'filter0.tdb' Apr 26 11:13:27 192.168.122.209 [68958.174654] [tempesta fw] modules are stopped Apr 26 11:13:27 192.168.122.209 [68958.345805] [tempesta fw] exiting... Apr 26 11:13:27 192.168.122.209 [68958.473879] [tdb] Shutdown Tempesta DB Apr 26 11:13:36 192.168.122.209 [68967.605728] Start test: tls.test_tls_tickets.TlsVhostConfusionDfltVhost.test Apr 26 11:13:38 192.168.122.209 [68969.161489] [tdb] Start Tempesta DB Apr 26 11:13:38 192.168.122.209 [68969.316556] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:13:40 192.168.122.209 [68971.049999] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68971.049999] Maybe that's fine, but it's worth checking the [68971.049999] config - if there is no relations between the [68971.049999] names, then host name confusion attack is possible. Apr 26 11:13:40 192.168.122.209 [68971.110492] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [68971.110492] Maybe that's fine, but it's worth checking the [68971.110492] config - if there is no relations between the [68971.110492] names, then host name confusion attack is possible. Apr 26 11:13:40 192.168.122.209 [68971.208536] [tempesta fw] Configuration processing is completed. Apr 26 11:13:40 192.168.122.209 [68971.268515] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:13:40 192.168.122.209 [68971.300110] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:13:40 192.168.122.209 [68971.330108] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:13:40 192.168.122.209 [68971.400535] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:13:40 192.168.122.209 [68971.460493] [tempesta fw] Tempesta FW is ready Apr 26 11:13:41 192.168.122.209 [68972.430861] [tdb] Close table 'client0.tdb' Apr 26 11:13:41 192.168.122.209 [68972.613222] [tdb] Close table 'sessions0.tdb' Apr 26 11:13:42 192.168.122.209 [68972.855889] [tdb] Close table 'filter0.tdb' Apr 26 11:13:42 192.168.122.209 [68972.856314] [tempesta fw] modules are stopped Apr 26 11:13:42 192.168.122.209 [68973.073583] [tempesta fw] exiting... Apr 26 11:13:42 192.168.122.209 [68973.224466] [tdb] Shutdown Tempesta DB Apr 26 11:13:42 192.168.122.209 [68973.629926] End test: tls.test_tls_tickets.TlsVhostConfusionDfltVhost.test Apr 26 11:13:42 192.168.122.209 [68973.668456] Start test: tls.test_tls_tickets.TlsVhostConfusionDfltCertsWithUnknown.test Apr 26 11:13:44 192.168.122.209 [68975.297959] [tdb] Start Tempesta DB Apr 26 11:13:44 192.168.122.209 [68975.440895] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:13:45 192.168.122.209 [68976.433860] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68976.433860] Maybe that's fine, but it's worth checking the [68976.433860] config - if there is no relations between the [68976.433860] names, then host name confusion attack is possible. Apr 26 11:13:45 192.168.122.209 [68976.560643] [tempesta fw] Configuration processing is completed. Apr 26 11:13:45 192.168.122.209 [68976.618350] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:13:45 192.168.122.209 [68976.646445] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:13:46 192.168.122.209 [68976.674576] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:13:46 192.168.122.209 [68976.744616] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:13:46 192.168.122.209 [68976.788556] [tempesta fw] Tempesta FW is ready Apr 26 11:13:47 192.168.122.209 [68977.721275] [tdb] Close table 'client0.tdb' Apr 26 11:13:47 192.168.122.209 [68977.904299] [tdb] Close table 'sessions0.tdb' Apr 26 11:13:47 192.168.122.209 [68978.139533] [tdb] Close table 'filter0.tdb' Apr 26 11:13:47 192.168.122.209 [68978.139935] [tempesta fw] modules are stopped Apr 26 11:13:47 192.168.122.209 [68978.413417] [tempesta fw] exiting... Apr 26 11:13:47 192.168.122.209 [68978.549614] [tdb] Shutdown Tempesta DB Apr 26 11:13:48 192.168.122.209 [68979.000142] End test: tls.test_tls_tickets.TlsVhostConfusionDfltCertsWithUnknown.test Apr 26 11:13:48 192.168.122.209 [68979.038964] Start test: tls.test_tls_tickets.TlsVhostConfusionDfltCerts.test Apr 26 11:13:49 192.168.122.209 [68980.603616] [tdb] Start Tempesta DB Apr 26 11:13:50 192.168.122.209 [68980.748497] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:13:51 192.168.122.209 [68981.746455] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [68981.746455] Maybe that's fine, but it's worth checking the [68981.746455] config - if there is no relations between the [68981.746455] names, then host name confusion attack is possible. Apr 26 11:13:51 192.168.122.209 [68981.790102] [tempesta fw] Warning: Vhost tempesta.com doesn't have certificate with matching SAN/CN. [68981.790102] Maybe that's fine, but it's worth checking the [68981.790102] config - if there is no relations between the [68981.790102] names, then host name confusion attack is possible. Apr 26 11:13:51 192.168.122.209 [68981.864698] [tempesta fw] Configuration processing is completed. Apr 26 11:13:51 192.168.122.209 [68981.926100] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:13:51 192.168.122.209 [68981.963413] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:13:51 192.168.122.209 [68982.000650] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:13:51 192.168.122.209 [68982.080686] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:13:51 192.168.122.209 [68982.124624] [tempesta fw] Tempesta FW is ready Apr 26 11:13:52 192.168.122.209 [68983.097403] [tdb] Close table 'client0.tdb' Apr 26 11:13:52 192.168.122.209 [68983.281861] [tdb] Close table 'sessions0.tdb' Apr 26 11:13:52 192.168.122.209 [68983.516325] [tdb] Close table 'filter0.tdb' Apr 26 11:13:52 192.168.122.209 [68983.516754] [tempesta fw] modules are stopped Apr 26 11:13:53 192.168.122.209 [68983.734999] [tempesta fw] exiting... Apr 26 11:13:53 192.168.122.209 [68983.846349] [tdb] Shutdown Tempesta DB Apr 26 11:13:53 192.168.122.209 [68984.231551] End test: tls.test_tls_tickets.TlsVhostConfusionDfltCerts.test Apr 26 11:13:53 192.168.122.209 [68984.256630] Start test: tls.test_tls_tickets.TlsVhostConfusion.test Apr 26 11:13:55 192.168.122.209 [68985.818513] [tdb] Start Tempesta DB Apr 26 11:13:55 192.168.122.209 [68985.955662] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:13:56 192.168.122.209 [68986.942726] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [68986.942726] Maybe that's fine, but it's worth checking the [68986.942726] config - if there is no relations between the [68986.942726] names, then host name confusion attack is possible. Apr 26 11:13:56 192.168.122.209 [68986.974933] [tempesta fw] Warning: Vhost tempesta.com doesn't have certificate with matching SAN/CN. [68986.974933] Maybe that's fine, but it's worth checking the [68986.974933] config - if there is no relations between the [68986.974933] names, then host name confusion attack is possible. Apr 26 11:13:56 192.168.122.209 [68987.048812] [tempesta fw] Configuration processing is completed. Apr 26 11:13:56 192.168.122.209 [68987.107157] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:13:56 192.168.122.209 [68987.139692] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:13:56 192.168.122.209 [68987.171812] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:13:56 192.168.122.209 [68987.244755] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:13:56 192.168.122.209 [68987.288717] [tempesta fw] Tempesta FW is ready Apr 26 11:13:57 192.168.122.209 [68988.215827] [tdb] Close table 'client0.tdb' Apr 26 11:13:57 192.168.122.209 [68988.405338] [tdb] Close table 'sessions0.tdb' Apr 26 11:13:57 192.168.122.209 [68988.644187] [tdb] Close table 'filter0.tdb' Apr 26 11:13:57 192.168.122.209 [68988.645007] [tempesta fw] modules are stopped Apr 26 11:13:58 192.168.122.209 [68988.856447] [tempesta fw] exiting... Apr 26 11:13:58 192.168.122.209 [68989.018170] [tdb] Shutdown Tempesta DB Apr 26 11:13:58 192.168.122.209 [68989.365023] End test: tls.test_tls_tickets.TlsVhostConfusion.test Apr 26 11:13:58 192.168.122.209 [68989.400405] Start test: tls.test_tls_tickets.TlsTicketTest.test_no_ticket_support Apr 26 11:13:59 192.168.122.209 [68990.665697] [tdb] Start Tempesta DB Apr 26 11:14:00 192.168.122.209 [68990.798596] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:14:00 192.168.122.209 [68991.432653] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68991.432653] Maybe that's fine, but it's worth checking the [68991.432653] config - if there is no relations between the [68991.432653] names, then host name confusion attack is possible. Apr 26 11:14:00 192.168.122.209 [68991.540904] [tempesta fw] Configuration processing is completed. Apr 26 11:14:00 192.168.122.209 [68991.596015] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:14:00 192.168.122.209 [68991.625275] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:14:00 192.168.122.209 [68991.657638] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:14:01 192.168.122.209 [68991.728792] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:14:01 192.168.122.209 [68991.768780] [tempesta fw] Tempesta FW is ready Apr 26 11:14:01 192.168.122.209 [68992.493690] [tdb] Close table 'client0.tdb' Apr 26 11:14:02 192.168.122.209 [68992.682260] [tdb] Close table 'sessions0.tdb' Apr 26 11:14:02 192.168.122.209 [68992.915369] [tdb] Close table 'filter0.tdb' Apr 26 11:14:02 192.168.122.209 [68992.915802] [tempesta fw] modules are stopped Apr 26 11:14:02 192.168.122.209 [68993.125345] [tempesta fw] exiting... Apr 26 11:14:02 192.168.122.209 [68993.259626] [tdb] Shutdown Tempesta DB Apr 26 11:14:03 192.168.122.209 [68993.679431] End test: tls.test_tls_tickets.TlsTicketTest.test_no_ticket_support Apr 26 11:14:03 192.168.122.209 [68993.707795] Start test: tls.test_tls_tickets.TlsTicketTest.test_invalid_ticket Apr 26 11:14:04 192.168.122.209 [68994.940490] [tdb] Start Tempesta DB Apr 26 11:14:04 192.168.122.209 [68995.070367] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:14:05 192.168.122.209 [68995.769650] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [68995.769650] Maybe that's fine, but it's worth checking the [68995.769650] config - if there is no relations between the [68995.769650] names, then host name confusion attack is possible. Apr 26 11:14:05 192.168.122.209 [68995.888918] [tempesta fw] Configuration processing is completed. Apr 26 11:14:05 192.168.122.209 [68995.945229] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:14:05 192.168.122.209 [68995.977716] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:14:05 192.168.122.209 [68996.009516] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:14:05 192.168.122.209 [68996.060894] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:14:05 192.168.122.209 [68996.100798] [tempesta fw] Tempesta FW is ready Apr 26 11:14:05 192.168.122.209 [68996.474611] [tempesta tls] Warning: AEAD decryption failed while ticket decryption: -74 Apr 26 11:14:06 192.168.122.209 [68997.003044] [tdb] Close table 'client0.tdb' Apr 26 11:14:06 192.168.122.209 [68997.188021] [tdb] Close table 'sessions0.tdb' Apr 26 11:14:06 192.168.122.209 [68997.429938] [tdb] Close table 'filter0.tdb' Apr 26 11:14:06 192.168.122.209 [68997.430374] [tempesta fw] modules are stopped Apr 26 11:14:06 192.168.122.209 [68997.646606] [tempesta fw] exiting... Apr 26 11:14:07 192.168.122.209 [68997.789096] [tdb] Shutdown Tempesta DB Apr 26 11:14:07 192.168.122.209 [68998.245605] End test: tls.test_tls_tickets.TlsTicketTest.test_invalid_ticket Apr 26 11:14:07 192.168.122.209 [68998.273104] Start test: tls.test_tls_tickets.TlsTicketTest.test_empty_ticket Apr 26 11:14:09 192.168.122.209 [68999.691343] [tdb] Start Tempesta DB Apr 26 11:14:09 192.168.122.209 [68999.820740] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:14:09 192.168.122.209 [69000.630347] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69000.630347] Maybe that's fine, but it's worth checking the [69000.630347] config - if there is no relations between the [69000.630347] names, then host name confusion attack is possible. Apr 26 11:14:10 192.168.122.209 [69000.752981] [tempesta fw] Configuration processing is completed. Apr 26 11:14:10 192.168.122.209 [69000.811802] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:14:10 192.168.122.209 [69000.844910] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:14:10 192.168.122.209 [69000.879369] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:14:10 192.168.122.209 [69000.932942] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:14:10 192.168.122.209 [69000.976895] [tempesta fw] Tempesta FW is ready Apr 26 11:14:11 192.168.122.209 [69001.825991] [tdb] Close table 'client0.tdb' Apr 26 11:14:11 192.168.122.209 [69002.016688] [tdb] Close table 'sessions0.tdb' Apr 26 11:14:11 192.168.122.209 [69002.250104] [tdb] Close table 'filter0.tdb' Apr 26 11:14:11 192.168.122.209 [69002.250530] [tempesta fw] modules are stopped Apr 26 11:14:11 192.168.122.209 [69002.490232] [tempesta fw] exiting... Apr 26 11:14:11 192.168.122.209 [69002.610767] [tdb] Shutdown Tempesta DB Apr 26 11:14:12 192.168.122.209 [69002.999019] End test: tls.test_tls_tickets.TlsTicketTest.test_empty_ticket Apr 26 11:14:12 192.168.122.209 [69003.025742] Start test: tls.test_tls_tickets.StandardTlsClient.test Apr 26 11:14:13 192.168.122.209 [69004.371283] [tdb] Start Tempesta DB Apr 26 11:14:13 192.168.122.209 [69004.505821] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:14:14 192.168.122.209 [69005.222257] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69005.222257] Maybe that's fine, but it's worth checking the [69005.222257] config - if there is no relations between the [69005.222257] names, then host name confusion attack is possible. Apr 26 11:14:14 192.168.122.209 [69005.365024] [tempesta fw] Configuration processing is completed. Apr 26 11:14:14 192.168.122.209 [69005.416811] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:14:14 192.168.122.209 [69005.444581] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:14:14 192.168.122.209 [69005.472233] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:14:14 192.168.122.209 [69005.545006] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:14:14 192.168.122.209 [69005.604963] [tempesta fw] Tempesta FW is ready Apr 26 11:14:16 192.168.122.209 [69007.268000] [tdb] Close table 'client0.tdb' Apr 26 11:14:16 192.168.122.209 [69007.454165] [tdb] Close table 'sessions0.tdb' Apr 26 11:14:17 192.168.122.209 [69007.682500] [tdb] Close table 'filter0.tdb' Apr 26 11:14:17 192.168.122.209 [69007.682905] [tempesta fw] modules are stopped Apr 26 11:14:17 192.168.122.209 [69007.959141] [tempesta fw] exiting... Apr 26 11:14:17 192.168.122.209 [69008.088540] [tdb] Shutdown Tempesta DB Apr 26 11:14:17 192.168.122.209 [69008.474690] End test: tls.test_tls_tickets.StandardTlsClient.test Apr 26 11:14:17 192.168.122.209 [69008.503519] Start test: tls.test_tls_stress.TlsHandshakeDheRsaTest.test_stress_DHE_RSA_AES256_GCM_SHA384 Apr 26 11:14:20 192.168.122.209 [69010.754334] [tdb] Start Tempesta DB Apr 26 11:14:20 192.168.122.209 [69010.894998] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:14:21 192.168.122.209 [69011.709809] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69011.709809] Maybe that's fine, but it's worth checking the [69011.709809] config - if there is no relations between the [69011.709809] names, then host name confusion attack is possible. Apr 26 11:14:21 192.168.122.209 [69011.873097] [tempesta fw] Configuration processing is completed. Apr 26 11:14:21 192.168.122.209 [69011.926505] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:14:21 192.168.122.209 [69011.953758] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:14:21 192.168.122.209 [69011.984739] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:14:21 192.168.122.209 [69012.049057] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:14:21 192.168.122.209 [69012.089010] [tempesta fw] Tempesta FW is ready Apr 26 11:14:23 192.168.122.209 [69013.994305] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:14:23 192.168.122.209 [69014.080104] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:14:23 192.168.122.209 [69014.089199] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:14:23 192.168.122.209 [69014.090246] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:14:23 192.168.122.209 [69014.091266] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:14:23 192.168.122.209 [69014.092285] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:14:25 192.168.122.209 [69016.635999] net_ratelimit: 27 callbacks suppressed Apr 26 11:14:25 192.168.122.209 [69016.636002] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69016.636002] Maybe that's fine, but it's worth checking the [69016.636002] config - if there is no relations between the [69016.636002] names, then host name confusion attack is possible. Apr 26 11:14:28 192.168.122.209 [69019.329601] [tempesta fw] Configuration processing is completed. Apr 26 11:14:32 192.168.122.209 [69023.525543] [tempesta fw] Tempesta FW is ready Apr 26 11:14:37 192.168.122.209 [69028.090575] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 11:14:38 192.168.122.209 [69029.287851] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69029.287851] Maybe that's fine, but it's worth checking the [69029.287851] config - if there is no relations between the [69029.287851] names, then host name confusion attack is possible. Apr 26 11:14:41 192.168.122.209 [69032.381769] [tempesta fw] Configuration processing is completed. Apr 26 11:14:45 192.168.122.209 [69036.392961] [tempesta fw] Tempesta FW is ready Apr 26 11:14:49 192.168.122.209 [69039.958749] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 11:14:50 192.168.122.209 [69041.033595] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69041.033595] Maybe that's fine, but it's worth checking the [69041.033595] config - if there is no relations between the [69041.033595] names, then host name confusion attack is possible. Apr 26 11:14:53 192.168.122.209 [69043.778567] [tempesta fw] Configuration processing is completed. Apr 26 11:14:57 192.168.122.209 [69048.241854] [tempesta fw] Tempesta FW is ready Apr 26 11:15:00 192.168.122.209 [69051.386821] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 11:15:01 192.168.122.209 [69052.119864] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69052.119864] Maybe that's fine, but it's worth checking the [69052.119864] config - if there is no relations between the [69052.119864] names, then host name confusion attack is possible. Apr 26 11:15:04 192.168.122.209 [69055.335741] [tempesta fw] Configuration processing is completed. Apr 26 11:15:09 192.168.122.209 [69059.726596] [tempesta fw] Tempesta FW is ready Apr 26 11:15:12 192.168.122.209 [69062.898998] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 11:15:12 192.168.122.209 [69062.994882] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69062.994882] Maybe that's fine, but it's worth checking the [69062.994882] config - if there is no relations between the [69062.994882] names, then host name confusion attack is possible. Apr 26 11:15:12 192.168.122.209 [69063.153790] [tempesta fw] Configuration processing is completed. Apr 26 11:15:12 192.168.122.209 [69063.318467] [tempesta fw] Tempesta FW is ready Apr 26 11:15:13 192.168.122.209 [69063.879887] [tdb] Close table 'client0.tdb' Apr 26 11:15:13 192.168.122.209 [69064.074445] [tdb] Close table 'sessions0.tdb' Apr 26 11:15:13 192.168.122.209 [69064.316482] [tdb] Close table 'filter0.tdb' Apr 26 11:15:13 192.168.122.209 [69064.316903] [tempesta fw] modules are stopped Apr 26 11:15:13 192.168.122.209 [69064.539311] [tempesta fw] exiting... Apr 26 11:15:13 192.168.122.209 [69064.663821] [tdb] Shutdown Tempesta DB Apr 26 11:15:14 192.168.122.209 [69065.074023] End test: tls.test_tls_stress.TlsHandshakeDheRsaTest.test_stress_DHE_RSA_AES256_GCM_SHA384 Apr 26 11:15:14 192.168.122.209 [69065.114828] Start test: tls.test_tls_stress.TlsHandshakeDheRsaTest.test_stress_DHE_RSA_AES256_CCM Apr 26 11:15:16 192.168.122.209 [69067.433987] [tdb] Start Tempesta DB Apr 26 11:15:16 192.168.122.209 [69067.558972] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:15:17 192.168.122.209 [69068.378481] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69068.378481] Maybe that's fine, but it's worth checking the [69068.378481] config - if there is no relations between the [69068.378481] names, then host name confusion attack is possible. Apr 26 11:15:17 192.168.122.209 [69068.545832] [tempesta fw] Configuration processing is completed. Apr 26 11:15:17 192.168.122.209 [69068.596884] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:15:17 192.168.122.209 [69068.624827] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:15:17 192.168.122.209 [69068.654702] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:15:18 192.168.122.209 [69068.721802] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:15:18 192.168.122.209 [69068.785763] [tempesta fw] Tempesta FW is ready Apr 26 11:15:19 192.168.122.209 [69070.664214] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:15:19 192.168.122.209 [69070.666953] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:15:20 192.168.122.209 [69070.700300] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:15:20 192.168.122.209 [69070.702203] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:15:20 192.168.122.209 [69070.713466] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:15:20 192.168.122.209 [69070.714508] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:15:20 192.168.122.209 [69070.715596] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:15:24 192.168.122.209 [69075.046754] net_ratelimit: 27 callbacks suppressed Apr 26 11:15:24 192.168.122.209 [69075.046759] [tempesta fw] Configuration processing is completed. Apr 26 11:15:29 192.168.122.209 [69079.838203] [tempesta fw] Tempesta FW is ready Apr 26 11:15:32 192.168.122.209 [69083.315491] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 11:15:33 192.168.122.209 [69083.945045] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69083.945045] Maybe that's fine, but it's worth checking the [69083.945045] config - if there is no relations between the [69083.945045] names, then host name confusion attack is possible. Apr 26 11:15:35 192.168.122.209 [69086.624850] [tempesta fw] Configuration processing is completed. Apr 26 11:15:39 192.168.122.209 [69090.567674] [tempesta fw] Tempesta FW is ready Apr 26 11:15:44 192.168.122.209 [69094.748305] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 11:15:45 192.168.122.209 [69095.695820] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69095.695820] Maybe that's fine, but it's worth checking the [69095.695820] config - if there is no relations between the [69095.695820] names, then host name confusion attack is possible. Apr 26 11:15:48 192.168.122.209 [69098.894478] [tempesta fw] Configuration processing is completed. Apr 26 11:15:51 192.168.122.209 [69102.022547] [tempesta fw] Tempesta FW is ready Apr 26 11:15:54 192.168.122.209 [69105.440259] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 11:15:55 192.168.122.209 [69106.440107] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69106.440107] Maybe that's fine, but it's worth checking the [69106.440107] config - if there is no relations between the [69106.440107] names, then host name confusion attack is possible. Apr 26 11:15:58 192.168.122.209 [69108.839739] [tempesta fw] Configuration processing is completed. Apr 26 11:16:02 192.168.122.209 [69113.262747] [tempesta fw] Tempesta FW is ready Apr 26 11:16:05 192.168.122.209 [69116.593764] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 11:16:06 192.168.122.209 [69117.352154] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69117.352154] Maybe that's fine, but it's worth checking the [69117.352154] config - if there is no relations between the [69117.352154] names, then host name confusion attack is possible. Apr 26 11:16:08 192.168.122.209 [69119.242518] [tempesta fw] Configuration processing is completed. Apr 26 11:16:08 192.168.122.209 [69119.371235] [tempesta fw] Tempesta FW is ready Apr 26 11:16:09 192.168.122.209 [69119.971511] [tdb] Close table 'client0.tdb' Apr 26 11:16:09 192.168.122.209 [69120.184908] [tdb] Close table 'sessions0.tdb' Apr 26 11:16:09 192.168.122.209 [69120.455743] [tdb] Close table 'filter0.tdb' Apr 26 11:16:09 192.168.122.209 [69120.456184] [tempesta fw] modules are stopped Apr 26 11:16:09 192.168.122.209 [69120.672735] [tempesta fw] exiting... Apr 26 11:16:10 192.168.122.209 [69120.818329] [tdb] Shutdown Tempesta DB Apr 26 11:16:10 192.168.122.209 [69121.199385] End test: tls.test_tls_stress.TlsHandshakeDheRsaTest.test_stress_DHE_RSA_AES256_CCM Apr 26 11:16:10 192.168.122.209 [69121.230054] Start test: tls.test_tls_stress.TlsHandshakeDheRsaTest.test_stress_DHE_RSA_AES128_GCM_SHA256 Apr 26 11:16:12 192.168.122.209 [69123.464544] [tdb] Start Tempesta DB Apr 26 11:16:12 192.168.122.209 [69123.623618] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:16:13 192.168.122.209 [69124.471761] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69124.471761] Maybe that's fine, but it's worth checking the [69124.471761] config - if there is no relations between the [69124.471761] names, then host name confusion attack is possible. Apr 26 11:16:13 192.168.122.209 [69124.650564] [tempesta fw] Configuration processing is completed. Apr 26 11:16:14 192.168.122.209 [69124.707268] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:16:14 192.168.122.209 [69124.739227] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:16:14 192.168.122.209 [69124.774902] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:16:14 192.168.122.209 [69124.862667] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:16:14 192.168.122.209 [69124.910397] [tempesta fw] Tempesta FW is ready Apr 26 11:16:16 192.168.122.209 [69126.763327] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:16:16 192.168.122.209 [69126.776732] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:16:16 192.168.122.209 [69126.776913] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:16:16 192.168.122.209 [69126.777179] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:16:16 192.168.122.209 [69126.777232] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:16:16 192.168.122.209 [69126.777277] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:16:18 192.168.122.209 [69129.434436] net_ratelimit: 27 callbacks suppressed Apr 26 11:16:18 192.168.122.209 [69129.434439] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69129.434439] Maybe that's fine, but it's worth checking the [69129.434439] config - if there is no relations between the [69129.434439] names, then host name confusion attack is possible. Apr 26 11:16:21 192.168.122.209 [69132.475439] [tempesta fw] Configuration processing is completed. Apr 26 11:16:26 192.168.122.209 [69136.918839] [tempesta fw] Tempesta FW is ready Apr 26 11:16:30 192.168.122.209 [69141.289872] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 11:16:31 192.168.122.209 [69141.960403] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69141.960403] Maybe that's fine, but it's worth checking the [69141.960403] config - if there is no relations between the [69141.960403] names, then host name confusion attack is possible. Apr 26 11:16:34 192.168.122.209 [69145.175565] [tempesta fw] Configuration processing is completed. Apr 26 11:16:38 192.168.122.209 [69148.911150] [tempesta fw] Tempesta FW is ready Apr 26 11:16:41 192.168.122.209 [69152.103959] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 11:16:42 192.168.122.209 [69152.953334] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69152.953334] Maybe that's fine, but it's worth checking the [69152.953334] config - if there is no relations between the [69152.953334] names, then host name confusion attack is possible. Apr 26 11:16:45 192.168.122.209 [69155.832702] [tempesta fw] Configuration processing is completed. Apr 26 11:16:49 192.168.122.209 [69160.339260] [tempesta fw] Tempesta FW is ready Apr 26 11:16:53 192.168.122.209 [69163.813181] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 11:16:54 192.168.122.209 [69164.754648] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69164.754648] Maybe that's fine, but it's worth checking the [69164.754648] config - if there is no relations between the [69164.754648] names, then host name confusion attack is possible. Apr 26 11:16:56 192.168.122.209 [69167.655271] [tempesta fw] Configuration processing is completed. Apr 26 11:17:01 192.168.122.209 [69172.223746] [tempesta fw] Tempesta FW is ready Apr 26 11:17:04 192.168.122.209 [69175.413247] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 11:17:04 192.168.122.209 [69175.503994] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69175.503994] Maybe that's fine, but it's worth checking the [69175.503994] config - if there is no relations between the [69175.503994] names, then host name confusion attack is possible. Apr 26 11:17:04 192.168.122.209 [69175.651259] [tempesta fw] Configuration processing is completed. Apr 26 11:17:05 192.168.122.209 [69175.775936] [tempesta fw] Tempesta FW is ready Apr 26 11:17:05 192.168.122.209 [69176.367751] [tdb] Close table 'client0.tdb' Apr 26 11:17:05 192.168.122.209 [69176.598167] [tdb] Close table 'sessions0.tdb' Apr 26 11:17:06 192.168.122.209 [69176.861935] [tdb] Close table 'filter0.tdb' Apr 26 11:17:06 192.168.122.209 [69176.862372] [tempesta fw] modules are stopped Apr 26 11:17:06 192.168.122.209 [69177.138049] [tempesta fw] exiting... Apr 26 11:17:06 192.168.122.209 [69177.260261] [tdb] Shutdown Tempesta DB Apr 26 11:17:07 192.168.122.209 [69177.717885] End test: tls.test_tls_stress.TlsHandshakeDheRsaTest.test_stress_DHE_RSA_AES128_GCM_SHA256 Apr 26 11:17:07 192.168.122.209 [69177.744382] Start test: tls.test_tls_stress.TlsHandshakeDheRsaTest.test_stress_DHE_RSA_AES128_CCM Apr 26 11:17:09 192.168.122.209 [69180.279154] [tdb] Start Tempesta DB Apr 26 11:17:09 192.168.122.209 [69180.454363] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:17:10 192.168.122.209 [69181.228195] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69181.228195] Maybe that's fine, but it's worth checking the [69181.228195] config - if there is no relations between the [69181.228195] names, then host name confusion attack is possible. Apr 26 11:17:10 192.168.122.209 [69181.391605] [tempesta fw] Configuration processing is completed. Apr 26 11:17:10 192.168.122.209 [69181.453700] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:17:10 192.168.122.209 [69181.486832] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:17:10 192.168.122.209 [69181.523242] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:17:10 192.168.122.209 [69181.607300] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:17:10 192.168.122.209 [69181.671398] [tempesta fw] Tempesta FW is ready Apr 26 11:17:12 192.168.122.209 [69183.562220] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:17:12 192.168.122.209 [69183.654981] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:17:12 192.168.122.209 [69183.656018] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:17:12 192.168.122.209 [69183.665151] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:17:12 192.168.122.209 [69183.666167] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:17:12 192.168.122.209 [69183.667193] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:17:17 192.168.122.209 [69188.038787] net_ratelimit: 28 callbacks suppressed Apr 26 11:17:17 192.168.122.209 [69188.038789] [tempesta fw] Configuration processing is completed. Apr 26 11:17:21 192.168.122.209 [69192.272128] [tempesta fw] Tempesta FW is ready Apr 26 11:17:25 192.168.122.209 [69195.873762] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 11:17:25 192.168.122.209 [69196.526955] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69196.526955] Maybe that's fine, but it's worth checking the [69196.526955] config - if there is no relations between the [69196.526955] names, then host name confusion attack is possible. Apr 26 11:17:29 192.168.122.209 [69199.761076] [tempesta fw] Configuration processing is completed. Apr 26 11:17:33 192.168.122.209 [69204.167987] [tempesta fw] Tempesta FW is ready Apr 26 11:17:36 192.168.122.209 [69207.347724] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 11:17:37 192.168.122.209 [69208.160863] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69208.160863] Maybe that's fine, but it's worth checking the [69208.160863] config - if there is no relations between the [69208.160863] names, then host name confusion attack is possible. Apr 26 11:17:40 192.168.122.209 [69211.083611] [tempesta fw] Configuration processing is completed. Apr 26 11:17:45 192.168.122.209 [69215.779905] [tempesta fw] Tempesta FW is ready Apr 26 11:17:49 192.168.122.209 [69219.767488] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 11:17:50 192.168.122.209 [69220.973118] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69220.973118] Maybe that's fine, but it's worth checking the [69220.973118] config - if there is no relations between the [69220.973118] names, then host name confusion attack is possible. Apr 26 11:17:53 192.168.122.209 [69223.964897] [tempesta fw] Configuration processing is completed. Apr 26 11:17:57 192.168.122.209 [69228.144226] [tempesta fw] Tempesta FW is ready Apr 26 11:18:01 192.168.122.209 [69231.704158] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 11:18:01 192.168.122.209 [69232.188924] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69232.188924] Maybe that's fine, but it's worth checking the [69232.188924] config - if there is no relations between the [69232.188924] names, then host name confusion attack is possible. Apr 26 11:18:01 192.168.122.209 [69232.364027] [tempesta fw] Configuration processing is completed. Apr 26 11:18:01 192.168.122.209 [69232.504688] [tempesta fw] Tempesta FW is ready Apr 26 11:18:02 192.168.122.209 [69233.125393] [tdb] Close table 'client0.tdb' Apr 26 11:18:02 192.168.122.209 [69233.328531] [tdb] Close table 'sessions0.tdb' Apr 26 11:18:02 192.168.122.209 [69233.572411] [tdb] Close table 'filter0.tdb' Apr 26 11:18:02 192.168.122.209 [69233.572845] [tempesta fw] modules are stopped Apr 26 11:18:03 192.168.122.209 [69233.815016] [tempesta fw] exiting... Apr 26 11:18:03 192.168.122.209 [69233.948051] [tdb] Shutdown Tempesta DB Apr 26 11:18:03 192.168.122.209 [69234.388925] End test: tls.test_tls_stress.TlsHandshakeDheRsaTest.test_stress_DHE_RSA_AES128_CCM Apr 26 11:18:03 192.168.122.209 [69234.437016] Start test: tls.test_tls_stress.TlsHandshakeDheRsaTest.test_DHE_RSA_AES256_GCM_SHA384 Apr 26 11:18:05 192.168.122.209 [69236.650735] [tdb] Start Tempesta DB Apr 26 11:18:06 192.168.122.209 [69236.816315] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:18:06 192.168.122.209 [69237.589654] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69237.589654] Maybe that's fine, but it's worth checking the [69237.589654] config - if there is no relations between the [69237.589654] names, then host name confusion attack is possible. Apr 26 11:18:07 192.168.122.209 [69237.756025] [tempesta fw] Configuration processing is completed. Apr 26 11:18:07 192.168.122.209 [69237.813908] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:18:07 192.168.122.209 [69237.845487] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:18:07 192.168.122.209 [69237.880593] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:18:07 192.168.122.209 [69237.963985] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:18:07 192.168.122.209 [69238.031993] [tempesta fw] Tempesta FW is ready Apr 26 11:18:09 192.168.122.209 [69239.961619] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:09 192.168.122.209 [69239.962719] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:09 192.168.122.209 [69239.963043] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:09 192.168.122.209 [69239.965322] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:09 192.168.122.209 [69239.982879] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:09 192.168.122.209 [69239.990880] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:09 192.168.122.209 [69239.991943] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:09 192.168.122.209 [69240.078714] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:09 192.168.122.209 [69240.078726] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:09 192.168.122.209 [69240.079109] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:09 192.168.122.209 [69240.079158] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:09 192.168.122.209 [69240.079269] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:09 192.168.122.209 [69240.079305] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:09 192.168.122.209 [69240.079340] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:09 192.168.122.209 [69240.081877] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:09 192.168.122.209 [69240.094784] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:09 192.168.122.209 [69240.112166] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:09 192.168.122.209 [69240.139403] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:09 192.168.122.209 [69240.140463] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:09 192.168.122.209 [69240.141494] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:09 192.168.122.209 [69240.164101] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:09 192.168.122.209 [69240.165142] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:09 192.168.122.209 [69240.166171] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:09 192.168.122.209 [69240.167346] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:09 192.168.122.209 [69240.168385] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:09 192.168.122.209 [69240.169405] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:09 192.168.122.209 [69240.170449] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:09 192.168.122.209 [69240.184258] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:09 192.168.122.209 [69240.338959] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:09 192.168.122.209 [69240.339849] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:09 192.168.122.209 [69240.340980] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:09 192.168.122.209 [69240.346808] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:18 192.168.122.209 [69248.757886] [tdb] Close table 'client0.tdb' Apr 26 11:18:18 192.168.122.209 [69248.970163] [tdb] Close table 'sessions0.tdb' Apr 26 11:18:18 192.168.122.209 [69249.211265] [tdb] Close table 'filter0.tdb' Apr 26 11:18:18 192.168.122.209 [69249.211716] [tempesta fw] modules are stopped Apr 26 11:18:18 192.168.122.209 [69249.488062] [tempesta fw] exiting... Apr 26 11:18:18 192.168.122.209 [69249.651387] [tdb] Shutdown Tempesta DB Apr 26 11:18:19 192.168.122.209 [69250.094755] End test: tls.test_tls_stress.TlsHandshakeDheRsaTest.test_DHE_RSA_AES256_GCM_SHA384 Apr 26 11:18:19 192.168.122.209 [69250.125298] Start test: tls.test_tls_stress.TlsHandshakeDheRsaTest.test_DHE_RSA_AES256_CCM Apr 26 11:18:22 192.168.122.209 [69253.052043] [tdb] Start Tempesta DB Apr 26 11:18:22 192.168.122.209 [69253.209994] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:18:23 192.168.122.209 [69254.058669] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69254.058669] Maybe that's fine, but it's worth checking the [69254.058669] config - if there is no relations between the [69254.058669] names, then host name confusion attack is possible. Apr 26 11:18:23 192.168.122.209 [69254.240441] [tempesta fw] Configuration processing is completed. Apr 26 11:18:23 192.168.122.209 [69254.298059] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:18:23 192.168.122.209 [69254.325930] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:18:23 192.168.122.209 [69254.359816] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:18:23 192.168.122.209 [69254.432390] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:18:23 192.168.122.209 [69254.484154] [tempesta fw] Tempesta FW is ready Apr 26 11:18:25 192.168.122.209 [69256.420792] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:25 192.168.122.209 [69256.472737] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:25 192.168.122.209 [69256.473775] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:25 192.168.122.209 [69256.473963] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:25 192.168.122.209 [69256.474806] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:25 192.168.122.209 [69256.476786] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:25 192.168.122.209 [69256.523869] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:25 192.168.122.209 [69256.524912] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:25 192.168.122.209 [69256.526423] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:25 192.168.122.209 [69256.527451] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:25 192.168.122.209 [69256.528480] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:25 192.168.122.209 [69256.529508] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:25 192.168.122.209 [69256.530532] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:25 192.168.122.209 [69256.531550] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:25 192.168.122.209 [69256.531556] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:25 192.168.122.209 [69256.532592] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:25 192.168.122.209 [69256.535460] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:25 192.168.122.209 [69256.535516] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:25 192.168.122.209 [69256.536516] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:25 192.168.122.209 [69256.538054] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:25 192.168.122.209 [69256.539424] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:25 192.168.122.209 [69256.540527] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:25 192.168.122.209 [69256.554316] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:25 192.168.122.209 [69256.560985] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:25 192.168.122.209 [69256.562020] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:25 192.168.122.209 [69256.563055] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:25 192.168.122.209 [69256.588721] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:25 192.168.122.209 [69256.627119] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:25 192.168.122.209 [69256.644979] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:25 192.168.122.209 [69256.649045] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:25 192.168.122.209 [69256.649347] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:25 192.168.122.209 [69256.651056] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:34 192.168.122.209 [69265.286154] [tdb] Close table 'client0.tdb' Apr 26 11:18:34 192.168.122.209 [69265.496417] [tdb] Close table 'sessions0.tdb' Apr 26 11:18:35 192.168.122.209 [69265.729521] [tdb] Close table 'filter0.tdb' Apr 26 11:18:35 192.168.122.209 [69265.729909] [tempesta fw] modules are stopped Apr 26 11:18:35 192.168.122.209 [69266.004282] [tempesta fw] exiting... Apr 26 11:18:35 192.168.122.209 [69266.121263] [tdb] Shutdown Tempesta DB Apr 26 11:18:35 192.168.122.209 [69266.509349] End test: tls.test_tls_stress.TlsHandshakeDheRsaTest.test_DHE_RSA_AES256_CCM Apr 26 11:18:35 192.168.122.209 [69266.544355] Start test: tls.test_tls_stress.TlsHandshakeDheRsaTest.test_DHE_RSA_AES128_GCM_SHA256 Apr 26 11:18:39 192.168.122.209 [69269.900606] [tdb] Start Tempesta DB Apr 26 11:18:39 192.168.122.209 [69270.056911] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:18:40 192.168.122.209 [69270.867808] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69270.867808] Maybe that's fine, but it's worth checking the [69270.867808] config - if there is no relations between the [69270.867808] names, then host name confusion attack is possible. Apr 26 11:18:40 192.168.122.209 [69271.020767] [tempesta fw] Configuration processing is completed. Apr 26 11:18:40 192.168.122.209 [69271.083003] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:18:40 192.168.122.209 [69271.116084] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:18:40 192.168.122.209 [69271.151726] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:18:40 192.168.122.209 [69271.240446] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:18:40 192.168.122.209 [69271.292354] [tempesta fw] Tempesta FW is ready Apr 26 11:18:42 192.168.122.209 [69273.285861] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:42 192.168.122.209 [69273.296233] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:42 192.168.122.209 [69273.296266] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:42 192.168.122.209 [69273.297294] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:42 192.168.122.209 [69273.298263] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:42 192.168.122.209 [69273.299335] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:42 192.168.122.209 [69273.328789] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:42 192.168.122.209 [69273.330695] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:42 192.168.122.209 [69273.332619] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:42 192.168.122.209 [69273.333276] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:42 192.168.122.209 [69273.333674] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:42 192.168.122.209 [69273.367317] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:42 192.168.122.209 [69273.368379] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:42 192.168.122.209 [69273.369402] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:42 192.168.122.209 [69273.370428] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:42 192.168.122.209 [69273.380989] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:42 192.168.122.209 [69273.381079] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:42 192.168.122.209 [69273.381084] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:42 192.168.122.209 [69273.381125] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:42 192.168.122.209 [69273.381359] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:42 192.168.122.209 [69273.381408] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:42 192.168.122.209 [69273.393643] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:42 192.168.122.209 [69273.394911] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:42 192.168.122.209 [69273.395924] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:42 192.168.122.209 [69273.398488] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:42 192.168.122.209 [69273.399567] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:42 192.168.122.209 [69273.443302] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:42 192.168.122.209 [69273.451602] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:42 192.168.122.209 [69273.547341] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:42 192.168.122.209 [69273.548379] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:42 192.168.122.209 [69273.598809] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:42 192.168.122.209 [69273.599873] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:18:51 192.168.122.209 [69281.981493] [tdb] Close table 'client0.tdb' Apr 26 11:18:51 192.168.122.209 [69282.192666] [tdb] Close table 'sessions0.tdb' Apr 26 11:18:51 192.168.122.209 [69282.445106] [tdb] Close table 'filter0.tdb' Apr 26 11:18:51 192.168.122.209 [69282.445565] [tempesta fw] modules are stopped Apr 26 11:18:51 192.168.122.209 [69282.655679] [tempesta fw] exiting... Apr 26 11:18:52 192.168.122.209 [69282.809490] [tdb] Shutdown Tempesta DB Apr 26 11:18:52 192.168.122.209 [69283.286418] End test: tls.test_tls_stress.TlsHandshakeDheRsaTest.test_DHE_RSA_AES128_GCM_SHA256 Apr 26 11:18:52 192.168.122.209 [69283.318021] Start test: tls.test_tls_stress.TlsHandshakeDheRsaTest.test_DHE_RSA_AES128_CCM Apr 26 11:18:56 192.168.122.209 [69287.519632] [tdb] Start Tempesta DB Apr 26 11:18:56 192.168.122.209 [69287.675648] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:18:57 192.168.122.209 [69288.461128] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69288.461128] Maybe that's fine, but it's worth checking the [69288.461128] config - if there is no relations between the [69288.461128] names, then host name confusion attack is possible. Apr 26 11:18:57 192.168.122.209 [69288.628680] [tempesta fw] Configuration processing is completed. Apr 26 11:18:58 192.168.122.209 [69288.692760] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:18:58 192.168.122.209 [69288.731217] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:18:58 192.168.122.209 [69288.770927] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:18:58 192.168.122.209 [69288.856640] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:18:58 192.168.122.209 [69288.905710] [tempesta fw] Tempesta FW is ready Apr 26 11:19:00 192.168.122.209 [69290.874719] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:19:00 192.168.122.209 [69290.911867] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:19:00 192.168.122.209 [69290.912115] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:19:00 192.168.122.209 [69290.912311] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:19:00 192.168.122.209 [69290.912451] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:19:00 192.168.122.209 [69290.913806] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:19:00 192.168.122.209 [69290.914738] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:19:00 192.168.122.209 [69290.917215] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:19:00 192.168.122.209 [69290.918096] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:19:00 192.168.122.209 [69290.923437] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:19:00 192.168.122.209 [69290.924460] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:19:00 192.168.122.209 [69290.982198] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:19:00 192.168.122.209 [69290.983242] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:19:00 192.168.122.209 [69290.984266] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:19:00 192.168.122.209 [69290.985385] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:19:00 192.168.122.209 [69290.986406] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:19:00 192.168.122.209 [69290.987425] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:19:00 192.168.122.209 [69290.988438] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:19:00 192.168.122.209 [69291.000919] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:19:00 192.168.122.209 [69291.001632] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:19:00 192.168.122.209 [69291.003110] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:19:00 192.168.122.209 [69291.004173] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:19:00 192.168.122.209 [69291.005203] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:19:00 192.168.122.209 [69291.015454] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:19:00 192.168.122.209 [69291.029675] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:19:00 192.168.122.209 [69291.030713] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:19:00 192.168.122.209 [69291.053296] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:19:00 192.168.122.209 [69291.054357] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:19:00 192.168.122.209 [69291.062497] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:19:00 192.168.122.209 [69291.063541] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:19:00 192.168.122.209 [69291.064905] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:19:00 192.168.122.209 [69291.065935] [tempesta fw] Warning: sock_srv: cannot establish connection for 192.168.122.196:8000: 1 tries, keep trying... Apr 26 11:19:08 192.168.122.209 [69299.597755] [tdb] Close table 'client0.tdb' Apr 26 11:19:09 192.168.122.209 [69299.812589] [tdb] Close table 'sessions0.tdb' Apr 26 11:19:09 192.168.122.209 [69300.068200] [tdb] Close table 'filter0.tdb' Apr 26 11:19:09 192.168.122.209 [69300.068656] [tempesta fw] modules are stopped Apr 26 11:19:09 192.168.122.209 [69300.275438] [tempesta fw] exiting... Apr 26 11:19:09 192.168.122.209 [69300.417613] [tdb] Shutdown Tempesta DB Apr 26 11:19:10 192.168.122.209 [69300.857375] End test: tls.test_tls_stress.TlsHandshakeDheRsaTest.test_DHE_RSA_AES128_CCM Apr 26 11:19:10 192.168.122.209 [69300.886283] Start test: tls.test_tls_stress.StressTls.test Apr 26 11:19:11 192.168.122.209 [69302.583868] [tdb] Start Tempesta DB Apr 26 11:19:12 192.168.122.209 [69302.723154] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:19:12 192.168.122.209 [69303.278371] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69303.278371] Maybe that's fine, but it's worth checking the [69303.278371] config - if there is no relations between the [69303.278371] names, then host name confusion attack is possible. Apr 26 11:19:12 192.168.122.209 [69303.408879] [tempesta fw] Configuration processing is completed. Apr 26 11:19:12 192.168.122.209 [69303.476032] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:19:13 192.168.122.209 [69304.167677] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:19:13 192.168.122.209 [69304.214842] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:19:13 192.168.122.209 [69304.262020] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:19:13 192.168.122.209 [69304.312846] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:19:13 192.168.122.209 [69304.368825] [tempesta fw] Tempesta FW is ready Apr 26 11:19:24 192.168.122.209 [69315.115066] [tdb] Close table 'client0.tdb' Apr 26 11:19:24 192.168.122.209 [69315.314330] [tdb] Close table 'sessions0.tdb' Apr 26 11:19:27 192.168.122.209 [69318.495407] [tdb] Close table 'cache0.tdb' Apr 26 11:19:28 192.168.122.209 [69318.755129] [tdb] Close table 'filter0.tdb' Apr 26 11:19:28 192.168.122.209 [69318.755530] [tempesta fw] modules are stopped Apr 26 11:19:28 192.168.122.209 [69318.957832] [tempesta fw] exiting... Apr 26 11:19:28 192.168.122.209 [69319.097981] [tdb] Shutdown Tempesta DB Apr 26 11:19:28 192.168.122.209 [69319.534561] End test: tls.test_tls_stress.StressTls.test Apr 26 11:19:28 192.168.122.209 [69319.561623] Start test: tls.test_tls_limits.TLSMatchHostSni.test_host_sni_mismatch Apr 26 11:19:30 192.168.122.209 [69320.915655] [tdb] Start Tempesta DB Apr 26 11:19:30 192.168.122.209 [69321.056650] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:19:32 192.168.122.209 [69322.890657] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69322.890657] Maybe that's fine, but it's worth checking the [69322.890657] config - if there is no relations between the [69322.890657] names, then host name confusion attack is possible. Apr 26 11:19:32 192.168.122.209 [69323.061159] [tempesta fw] Configuration processing is completed. Apr 26 11:19:32 192.168.122.209 [69323.117828] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:19:32 192.168.122.209 [69323.150049] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:19:32 192.168.122.209 [69323.180356] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:19:32 192.168.122.209 [69323.221075] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:19:32 192.168.122.209 [69323.261051] [tempesta fw] Tempesta FW is ready Apr 26 11:19:32 192.168.122.209 [69323.539456] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 192.168.122.196 ('default' vs 'dummy') Apr 26 11:19:32 192.168.122.209 [69323.542678] [tempesta fw] Warning: parsed request has been filtered out: 192.168.122.196 Apr 26 11:19:33 192.168.122.209 [69324.136778] [tdb] Close table 'client0.tdb' Apr 26 11:19:33 192.168.122.209 [69324.329572] [tdb] Close table 'sessions0.tdb' Apr 26 11:19:33 192.168.122.209 [69324.549299] [tdb] Close table 'filter0.tdb' Apr 26 11:19:33 192.168.122.209 [69324.549725] [tempesta fw] modules are stopped Apr 26 11:19:34 192.168.122.209 [69324.795591] [tempesta fw] exiting... Apr 26 11:19:34 192.168.122.209 [69324.931230] [tdb] Shutdown Tempesta DB Apr 26 11:19:34 192.168.122.209 [69325.281142] End test: tls.test_tls_limits.TLSMatchHostSni.test_host_sni_mismatch Apr 26 11:19:34 192.168.122.209 [69325.311380] Start test: tls.test_tls_kernel.TCrypt.test_tcrypt Apr 26 11:19:35 192.168.122.209 [69326.090488] End test: tls.test_tls_kernel.TCrypt.test_tcrypt Apr 26 11:19:35 192.168.122.209 [69326.118077] Start test: tls.test_tls_integrity.ProxyH2.test_various_req_resp_sizes Apr 26 11:19:36 192.168.122.209 [69327.493300] [tdb] Start Tempesta DB Apr 26 11:19:36 192.168.122.209 [69327.632530] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:19:37 192.168.122.209 [69328.154390] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69328.154390] Maybe that's fine, but it's worth checking the [69328.154390] config - if there is no relations between the [69328.154390] names, then host name confusion attack is possible. Apr 26 11:19:38 192.168.122.209 [69328.777558] [tempesta fw] Configuration processing is completed. Apr 26 11:19:38 192.168.122.209 [69328.963542] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:19:38 192.168.122.209 [69328.994093] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:19:38 192.168.122.209 [69329.023024] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:19:39 192.168.122.209 [69329.777204] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:19:39 192.168.122.209 [69330.121127] [tempesta fw] Tempesta FW is ready Apr 26 11:19:41 192.168.122.209 [69331.791919] [tdb] Close table 'client0.tdb' Apr 26 11:19:41 192.168.122.209 [69332.063787] [tdb] Close table 'sessions0.tdb' Apr 26 11:19:42 192.168.122.209 [69332.758331] [tdb] Close table 'filter0.tdb' Apr 26 11:19:42 192.168.122.209 [69332.758773] [tempesta fw] modules are stopped Apr 26 11:19:43 192.168.122.209 [69334.048083] [tempesta fw] exiting... Apr 26 11:19:43 192.168.122.209 [69334.374586] [tdb] Shutdown Tempesta DB Apr 26 11:19:44 192.168.122.209 [69334.751200] End test: tls.test_tls_integrity.ProxyH2.test_various_req_resp_sizes Apr 26 11:19:44 192.168.122.209 [69334.778928] Start test: tls.test_tls_integrity.Proxy.test_various_req_resp_sizes Apr 26 11:19:45 192.168.122.209 [69336.343887] [tdb] Start Tempesta DB Apr 26 11:19:45 192.168.122.209 [69336.480113] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:19:46 192.168.122.209 [69337.106561] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69337.106561] Maybe that's fine, but it's worth checking the [69337.106561] config - if there is no relations between the [69337.106561] names, then host name confusion attack is possible. Apr 26 11:19:46 192.168.122.209 [69337.213345] [tempesta fw] Configuration processing is completed. Apr 26 11:19:46 192.168.122.209 [69337.278545] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:19:46 192.168.122.209 [69337.310624] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:19:46 192.168.122.209 [69337.340547] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:19:46 192.168.122.209 [69337.389279] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:19:46 192.168.122.209 [69337.425230] [tempesta fw] Tempesta FW is ready Apr 26 11:19:47 192.168.122.209 [69338.574981] [tdb] Close table 'client0.tdb' Apr 26 11:19:48 192.168.122.209 [69338.762605] [tdb] Close table 'sessions0.tdb' Apr 26 11:19:48 192.168.122.209 [69339.003218] [tdb] Close table 'filter0.tdb' Apr 26 11:19:48 192.168.122.209 [69339.003641] [tempesta fw] modules are stopped Apr 26 11:19:48 192.168.122.209 [69339.189803] [tempesta fw] exiting... Apr 26 11:19:48 192.168.122.209 [69339.317640] [tdb] Shutdown Tempesta DB Apr 26 11:19:48 192.168.122.209 [69339.673883] End test: tls.test_tls_integrity.Proxy.test_various_req_resp_sizes Apr 26 11:19:49 192.168.122.209 [69339.754695] Start test: tls.test_tls_integrity.ManyClientsH2.test_various_req_resp_sizes Apr 26 11:19:50 192.168.122.209 [69341.084328] [tdb] Start Tempesta DB Apr 26 11:19:50 192.168.122.209 [69341.215121] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:19:51 192.168.122.209 [69341.818596] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69341.818596] Maybe that's fine, but it's worth checking the [69341.818596] config - if there is no relations between the [69341.818596] names, then host name confusion attack is possible. Apr 26 11:19:51 192.168.122.209 [69341.965359] [tempesta fw] Configuration processing is completed. Apr 26 11:19:51 192.168.122.209 [69342.016227] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:19:51 192.168.122.209 [69342.044024] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:19:51 192.168.122.209 [69342.072754] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:19:51 192.168.122.209 [69342.113349] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:19:51 192.168.122.209 [69342.149267] [tempesta fw] Tempesta FW is ready Apr 26 11:19:53 192.168.122.209 [69343.974785] [tdb] Close table 'client0.tdb' Apr 26 11:19:53 192.168.122.209 [69344.157659] [tdb] Close table 'sessions0.tdb' Apr 26 11:19:53 192.168.122.209 [69344.367393] [tdb] Close table 'filter0.tdb' Apr 26 11:19:53 192.168.122.209 [69344.367838] [tempesta fw] modules are stopped Apr 26 11:19:53 192.168.122.209 [69344.574837] [tempesta fw] exiting... Apr 26 11:19:54 192.168.122.209 [69344.720125] [tdb] Shutdown Tempesta DB Apr 26 11:19:54 192.168.122.209 [69345.088224] End test: tls.test_tls_integrity.ManyClientsH2.test_various_req_resp_sizes Apr 26 11:19:54 192.168.122.209 [69345.121615] Start test: tls.test_tls_integrity.ManyClients.test_various_req_resp_sizes Apr 26 11:19:55 192.168.122.209 [69346.577791] [tdb] Start Tempesta DB Apr 26 11:19:56 192.168.122.209 [69346.718184] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:19:56 192.168.122.209 [69347.214424] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69347.214424] Maybe that's fine, but it's worth checking the [69347.214424] config - if there is no relations between the [69347.214424] names, then host name confusion attack is possible. Apr 26 11:19:56 192.168.122.209 [69347.309466] [tempesta fw] Configuration processing is completed. Apr 26 11:19:56 192.168.122.209 [69347.363863] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:19:56 192.168.122.209 [69347.391242] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:19:56 192.168.122.209 [69347.420539] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:19:56 192.168.122.209 [69347.465385] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:19:56 192.168.122.209 [69347.509337] [tempesta fw] Tempesta FW is ready Apr 26 11:20:00 192.168.122.209 [69351.578367] [tdb] Close table 'client0.tdb' Apr 26 11:20:01 192.168.122.209 [69351.764846] [tdb] Close table 'sessions0.tdb' Apr 26 11:20:01 192.168.122.209 [69352.006847] [tdb] Close table 'filter0.tdb' Apr 26 11:20:01 192.168.122.209 [69352.007265] [tempesta fw] modules are stopped Apr 26 11:20:01 192.168.122.209 [69352.201337] [tempesta fw] exiting... Apr 26 11:20:01 192.168.122.209 [69352.302085] [tdb] Shutdown Tempesta DB Apr 26 11:20:02 192.168.122.209 [69352.703196] End test: tls.test_tls_integrity.ManyClients.test_various_req_resp_sizes Apr 26 11:20:02 192.168.122.209 [69352.733130] Start test: tls.test_tls_integrity.CloseConnection.test8 Apr 26 11:20:03 192.168.122.209 [69354.203816] [tdb] Start Tempesta DB Apr 26 11:20:03 192.168.122.209 [69354.343610] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:20:04 192.168.122.209 [69354.926928] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69354.926928] Maybe that's fine, but it's worth checking the [69354.926928] config - if there is no relations between the [69354.926928] names, then host name confusion attack is possible. Apr 26 11:20:04 192.168.122.209 [69355.021626] [tempesta fw] Configuration processing is completed. Apr 26 11:20:04 192.168.122.209 [69355.081825] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:20:04 192.168.122.209 [69355.113677] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:20:04 192.168.122.209 [69355.151988] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:20:04 192.168.122.209 [69355.193488] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:20:04 192.168.122.209 [69355.233438] [tempesta fw] Tempesta FW is ready Apr 26 11:20:05 192.168.122.209 [69356.130579] [tdb] Close table 'client0.tdb' Apr 26 11:20:05 192.168.122.209 [69356.315723] [tdb] Close table 'sessions0.tdb' Apr 26 11:20:05 192.168.122.209 [69356.539859] [tdb] Close table 'filter0.tdb' Apr 26 11:20:05 192.168.122.209 [69356.540305] [tempesta fw] modules are stopped Apr 26 11:20:06 192.168.122.209 [69356.741216] [tempesta fw] exiting... Apr 26 11:20:06 192.168.122.209 [69356.869716] [tdb] Shutdown Tempesta DB Apr 26 11:20:06 192.168.122.209 [69357.301622] End test: tls.test_tls_integrity.CloseConnection.test8 Apr 26 11:20:06 192.168.122.209 [69357.327839] Start test: tls.test_tls_integrity.CloseConnection.test7 Apr 26 11:20:08 192.168.122.209 [69358.891247] [tdb] Start Tempesta DB Apr 26 11:20:08 192.168.122.209 [69359.025046] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:20:08 192.168.122.209 [69359.598808] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69359.598808] Maybe that's fine, but it's worth checking the [69359.598808] config - if there is no relations between the [69359.598808] names, then host name confusion attack is possible. Apr 26 11:20:09 192.168.122.209 [69359.693657] [tempesta fw] Configuration processing is completed. Apr 26 11:20:09 192.168.122.209 [69359.745620] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:20:09 192.168.122.209 [69359.774346] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:20:09 192.168.122.209 [69359.802919] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:20:09 192.168.122.209 [69359.845559] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:20:09 192.168.122.209 [69359.885520] [tempesta fw] Tempesta FW is ready Apr 26 11:20:09 192.168.122.209 [69360.520914] [tdb] Close table 'client0.tdb' Apr 26 11:20:10 192.168.122.209 [69360.720835] [tdb] Close table 'sessions0.tdb' Apr 26 11:20:10 192.168.122.209 [69360.963566] [tdb] Close table 'filter0.tdb' Apr 26 11:20:10 192.168.122.209 [69360.963979] [tempesta fw] modules are stopped Apr 26 11:20:10 192.168.122.209 [69361.143417] [tempesta fw] exiting... Apr 26 11:20:10 192.168.122.209 [69361.273113] [tdb] Shutdown Tempesta DB Apr 26 11:20:11 192.168.122.209 [69361.703026] End test: tls.test_tls_integrity.CloseConnection.test7 Apr 26 11:20:11 192.168.122.209 [69361.736560] Start test: tls.test_tls_integrity.CloseConnection.test6 Apr 26 11:20:12 192.168.122.209 [69363.275356] [tdb] Start Tempesta DB Apr 26 11:20:12 192.168.122.209 [69363.394281] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:20:13 192.168.122.209 [69363.958429] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69363.958429] Maybe that's fine, but it's worth checking the [69363.958429] config - if there is no relations between the [69363.958429] names, then host name confusion attack is possible. Apr 26 11:20:13 192.168.122.209 [69364.057704] [tempesta fw] Configuration processing is completed. Apr 26 11:20:13 192.168.122.209 [69364.115467] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:20:13 192.168.122.209 [69364.147686] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:20:13 192.168.122.209 [69364.178864] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:20:13 192.168.122.209 [69364.217647] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:20:13 192.168.122.209 [69364.257573] [tempesta fw] Tempesta FW is ready Apr 26 11:20:14 192.168.122.209 [69364.885948] [tdb] Close table 'client0.tdb' Apr 26 11:20:14 192.168.122.209 [69365.087275] [tdb] Close table 'sessions0.tdb' Apr 26 11:20:14 192.168.122.209 [69365.337235] [tdb] Close table 'filter0.tdb' Apr 26 11:20:14 192.168.122.209 [69365.337676] [tempesta fw] modules are stopped Apr 26 11:20:14 192.168.122.209 [69365.530898] [tempesta fw] exiting... Apr 26 11:20:14 192.168.122.209 [69365.650564] [tdb] Shutdown Tempesta DB Apr 26 11:20:15 192.168.122.209 [69366.054152] End test: tls.test_tls_integrity.CloseConnection.test6 Apr 26 11:20:15 192.168.122.209 [69366.089282] Start test: tls.test_tls_integrity.CloseConnection.test5 Apr 26 11:20:16 192.168.122.209 [69367.539276] [tdb] Start Tempesta DB Apr 26 11:20:17 192.168.122.209 [69367.678296] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:20:17 192.168.122.209 [69368.263268] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69368.263268] Maybe that's fine, but it's worth checking the [69368.263268] config - if there is no relations between the [69368.263268] names, then host name confusion attack is possible. Apr 26 11:20:17 192.168.122.209 [69368.373757] [tempesta fw] Configuration processing is completed. Apr 26 11:20:17 192.168.122.209 [69368.425742] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:20:17 192.168.122.209 [69368.453638] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:20:17 192.168.122.209 [69368.481971] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:20:17 192.168.122.209 [69368.545661] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:20:17 192.168.122.209 [69368.585570] [tempesta fw] Tempesta FW is ready Apr 26 11:20:18 192.168.122.209 [69369.231904] [tdb] Close table 'client0.tdb' Apr 26 11:20:18 192.168.122.209 [69369.424097] [tdb] Close table 'sessions0.tdb' Apr 26 11:20:19 192.168.122.209 [69369.678668] [tdb] Close table 'filter0.tdb' Apr 26 11:20:19 192.168.122.209 [69369.679096] [tempesta fw] modules are stopped Apr 26 11:20:19 192.168.122.209 [69369.876596] [tempesta fw] exiting... Apr 26 11:20:19 192.168.122.209 [69370.017049] [tdb] Shutdown Tempesta DB Apr 26 11:20:19 192.168.122.209 [69370.381737] End test: tls.test_tls_integrity.CloseConnection.test5 Apr 26 11:20:19 192.168.122.209 [69370.416512] Start test: tls.test_tls_integrity.CloseConnection.test4 Apr 26 11:20:21 192.168.122.209 [69372.034081] [tdb] Start Tempesta DB Apr 26 11:20:21 192.168.122.209 [69372.152033] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:20:22 192.168.122.209 [69372.766500] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69372.766500] Maybe that's fine, but it's worth checking the [69372.766500] config - if there is no relations between the [69372.766500] names, then host name confusion attack is possible. Apr 26 11:20:22 192.168.122.209 [69372.861795] [tempesta fw] Configuration processing is completed. Apr 26 11:20:22 192.168.122.209 [69372.926786] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:20:22 192.168.122.209 [69372.959248] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:20:22 192.168.122.209 [69372.991194] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:20:22 192.168.122.209 [69373.033725] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:20:22 192.168.122.209 [69373.081673] [tempesta fw] Tempesta FW is ready Apr 26 11:20:23 192.168.122.209 [69373.792595] [tdb] Close table 'client0.tdb' Apr 26 11:20:23 192.168.122.209 [69373.992274] [tdb] Close table 'sessions0.tdb' Apr 26 11:20:23 192.168.122.209 [69374.229318] [tdb] Close table 'filter0.tdb' Apr 26 11:20:23 192.168.122.209 [69374.230162] [tempesta fw] modules are stopped Apr 26 11:20:23 192.168.122.209 [69374.447303] [tempesta fw] exiting... Apr 26 11:20:23 192.168.122.209 [69374.590487] [tdb] Shutdown Tempesta DB Apr 26 11:20:24 192.168.122.209 [69374.997837] End test: tls.test_tls_integrity.CloseConnection.test4 Apr 26 11:20:24 192.168.122.209 [69375.028416] Start test: tls.test_tls_integrity.CloseConnection.test3 Apr 26 11:20:25 192.168.122.209 [69376.561402] [tdb] Start Tempesta DB Apr 26 11:20:26 192.168.122.209 [69376.717235] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:20:26 192.168.122.209 [69377.274772] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69377.274772] Maybe that's fine, but it's worth checking the [69377.274772] config - if there is no relations between the [69377.274772] names, then host name confusion attack is possible. Apr 26 11:20:26 192.168.122.209 [69377.389874] [tempesta fw] Configuration processing is completed. Apr 26 11:20:26 192.168.122.209 [69377.444463] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:20:26 192.168.122.209 [69377.472413] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:20:26 192.168.122.209 [69377.500479] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:20:26 192.168.122.209 [69377.541738] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:20:26 192.168.122.209 [69377.581745] [tempesta fw] Tempesta FW is ready Apr 26 11:20:27 192.168.122.209 [69378.207779] [tdb] Close table 'client0.tdb' Apr 26 11:20:27 192.168.122.209 [69378.395617] [tdb] Close table 'sessions0.tdb' Apr 26 11:20:27 192.168.122.209 [69378.627280] [tdb] Close table 'filter0.tdb' Apr 26 11:20:27 192.168.122.209 [69378.627709] [tempesta fw] modules are stopped Apr 26 11:20:28 192.168.122.209 [69378.840681] [tempesta fw] exiting... Apr 26 11:20:28 192.168.122.209 [69378.945870] [tdb] Shutdown Tempesta DB Apr 26 11:20:28 192.168.122.209 [69379.323761] End test: tls.test_tls_integrity.CloseConnection.test3 Apr 26 11:20:28 192.168.122.209 [69379.410765] Start test: tls.test_tls_integrity.CloseConnection.test2 Apr 26 11:20:30 192.168.122.209 [69380.984106] [tdb] Start Tempesta DB Apr 26 11:20:30 192.168.122.209 [69381.123236] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:20:30 192.168.122.209 [69381.674427] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69381.674427] Maybe that's fine, but it's worth checking the [69381.674427] config - if there is no relations between the [69381.674427] names, then host name confusion attack is possible. Apr 26 11:20:31 192.168.122.209 [69381.773796] [tempesta fw] Configuration processing is completed. Apr 26 11:20:31 192.168.122.209 [69381.831685] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:20:31 192.168.122.209 [69381.860888] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:20:31 192.168.122.209 [69381.889035] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:20:31 192.168.122.209 [69381.929829] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:20:31 192.168.122.209 [69381.977805] [tempesta fw] Tempesta FW is ready Apr 26 11:20:31 192.168.122.209 [69382.612844] [tdb] Close table 'client0.tdb' Apr 26 11:20:32 192.168.122.209 [69382.819524] [tdb] Close table 'sessions0.tdb' Apr 26 11:20:32 192.168.122.209 [69383.070601] [tdb] Close table 'filter0.tdb' Apr 26 11:20:32 192.168.122.209 [69383.070997] [tempesta fw] modules are stopped Apr 26 11:20:32 192.168.122.209 [69383.253694] [tempesta fw] exiting... Apr 26 11:20:32 192.168.122.209 [69383.398028] [tdb] Shutdown Tempesta DB Apr 26 11:20:33 192.168.122.209 [69383.826779] End test: tls.test_tls_integrity.CloseConnection.test2 Apr 26 11:20:33 192.168.122.209 [69383.859237] Start test: tls.test_tls_integrity.CloseConnection.test1 Apr 26 11:20:34 192.168.122.209 [69385.302401] [tdb] Start Tempesta DB Apr 26 11:20:34 192.168.122.209 [69385.446757] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:20:35 192.168.122.209 [69386.019167] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69386.019167] Maybe that's fine, but it's worth checking the [69386.019167] config - if there is no relations between the [69386.019167] names, then host name confusion attack is possible. Apr 26 11:20:35 192.168.122.209 [69386.130242] [tempesta fw] Configuration processing is completed. Apr 26 11:20:35 192.168.122.209 [69386.184000] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:20:35 192.168.122.209 [69386.210709] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:20:35 192.168.122.209 [69386.237584] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:20:35 192.168.122.209 [69386.281898] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:20:35 192.168.122.209 [69386.333880] [tempesta fw] Tempesta FW is ready Apr 26 11:20:36 192.168.122.209 [69386.975973] [tdb] Close table 'client0.tdb' Apr 26 11:20:36 192.168.122.209 [69387.182095] [tdb] Close table 'sessions0.tdb' Apr 26 11:20:36 192.168.122.209 [69387.421403] [tdb] Close table 'filter0.tdb' Apr 26 11:20:36 192.168.122.209 [69387.422276] [tempesta fw] modules are stopped Apr 26 11:20:36 192.168.122.209 [69387.602190] [tempesta fw] exiting... Apr 26 11:20:37 192.168.122.209 [69387.718429] [tdb] Shutdown Tempesta DB Apr 26 11:20:37 192.168.122.209 [69388.159588] End test: tls.test_tls_integrity.CloseConnection.test1 Apr 26 11:20:37 192.168.122.209 [69388.185472] Start test: tls.test_tls_integrity.CacheH2.test_various_req_resp_sizes Apr 26 11:20:38 192.168.122.209 [69389.486692] [tdb] Start Tempesta DB Apr 26 11:20:38 192.168.122.209 [69389.620288] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:20:39 192.168.122.209 [69390.219213] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69390.219213] Maybe that's fine, but it's worth checking the [69390.219213] config - if there is no relations between the [69390.219213] names, then host name confusion attack is possible. Apr 26 11:20:39 192.168.122.209 [69390.297962] [tempesta fw] Configuration processing is completed. Apr 26 11:20:39 192.168.122.209 [69390.347858] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:20:40 192.168.122.209 [69390.753490] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:20:40 192.168.122.209 [69390.778921] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:20:40 192.168.122.209 [69390.805073] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:20:40 192.168.122.209 [69390.845909] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:20:40 192.168.122.209 [69390.889894] [tempesta fw] Tempesta FW is ready Apr 26 11:20:42 192.168.122.209 [69392.829637] [tdb] Close table 'client0.tdb' Apr 26 11:20:42 192.168.122.209 [69393.013024] [tdb] Close table 'sessions0.tdb' Apr 26 11:20:45 192.168.122.209 [69396.180562] [tdb] Close table 'cache0.tdb' Apr 26 11:20:45 192.168.122.209 [69396.403247] [tdb] Close table 'filter0.tdb' Apr 26 11:20:45 192.168.122.209 [69396.403670] [tempesta fw] modules are stopped Apr 26 11:20:45 192.168.122.209 [69396.589212] [tempesta fw] exiting... Apr 26 11:20:46 192.168.122.209 [69396.723150] [tdb] Shutdown Tempesta DB Apr 26 11:20:46 192.168.122.209 [69397.160757] End test: tls.test_tls_integrity.CacheH2.test_various_req_resp_sizes Apr 26 11:20:46 192.168.122.209 [69397.200079] Start test: tls.test_tls_integrity.Cache.test_various_req_resp_sizes Apr 26 11:20:48 192.168.122.209 [69398.771635] [tdb] Start Tempesta DB Apr 26 11:20:48 192.168.122.209 [69398.902512] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:20:49 192.168.122.209 [69400.279414] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69400.279414] Maybe that's fine, but it's worth checking the [69400.279414] config - if there is no relations between the [69400.279414] names, then host name confusion attack is possible. Apr 26 11:20:49 192.168.122.209 [69400.378135] [tempesta fw] Configuration processing is completed. Apr 26 11:20:49 192.168.122.209 [69400.438615] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:20:50 192.168.122.209 [69400.860265] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:20:50 192.168.122.209 [69400.886296] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:20:50 192.168.122.209 [69400.911866] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:20:50 192.168.122.209 [69400.950080] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:20:50 192.168.122.209 [69400.994032] [tempesta fw] Tempesta FW is ready Apr 26 11:20:52 192.168.122.209 [69403.469105] [tdb] Close table 'client0.tdb' Apr 26 11:20:52 192.168.122.209 [69403.633150] [tdb] Close table 'sessions0.tdb' Apr 26 11:20:56 192.168.122.209 [69406.815314] [tdb] Close table 'cache0.tdb' Apr 26 11:20:56 192.168.122.209 [69407.089664] [tdb] Close table 'filter0.tdb' Apr 26 11:20:56 192.168.122.209 [69407.090127] [tempesta fw] modules are stopped Apr 26 11:20:56 192.168.122.209 [69407.277986] [tempesta fw] exiting... Apr 26 11:20:56 192.168.122.209 [69407.399219] [tdb] Shutdown Tempesta DB Apr 26 11:20:57 192.168.122.209 [69407.782344] End test: tls.test_tls_integrity.Cache.test_various_req_resp_sizes Apr 26 11:20:57 192.168.122.209 [69408.184501] Start test: tls.test_tls_handshake.TlsVhostHandshakeTest.test_vhost_sni Apr 26 11:20:58 192.168.122.209 [69409.542358] [tdb] Start Tempesta DB Apr 26 11:20:59 192.168.122.209 [69409.683299] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:21:00 192.168.122.209 [69411.371599] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69411.371599] Maybe that's fine, but it's worth checking the [69411.371599] config - if there is no relations between the [69411.371599] names, then host name confusion attack is possible. Apr 26 11:21:00 192.168.122.209 [69411.436315] [tempesta fw] Warning: Vhost vhost2.net doesn't have certificate with matching SAN/CN. [69411.436315] Maybe that's fine, but it's worth checking the [69411.436315] config - if there is no relations between the [69411.436315] names, then host name confusion attack is possible. Apr 26 11:21:00 192.168.122.209 [69411.502304] [tempesta fw] Configuration processing is completed. Apr 26 11:21:00 192.168.122.209 [69411.558375] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:21:00 192.168.122.209 [69411.589671] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:21:00 192.168.122.209 [69411.619867] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:21:01 192.168.122.209 [69411.694239] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:21:01 192.168.122.209 [69411.750182] [tempesta fw] Tempesta FW is ready Apr 26 11:21:02 192.168.122.209 [69412.766108] [tdb] Close table 'client0.tdb' Apr 26 11:21:02 192.168.122.209 [69412.953681] [tdb] Close table 'sessions0.tdb' Apr 26 11:21:02 192.168.122.209 [69413.176844] [tdb] Close table 'filter0.tdb' Apr 26 11:21:02 192.168.122.209 [69413.177263] [tempesta fw] modules are stopped Apr 26 11:21:02 192.168.122.209 [69413.426616] [tempesta fw] exiting... Apr 26 11:21:02 192.168.122.209 [69413.537608] [tdb] Shutdown Tempesta DB Apr 26 11:21:03 192.168.122.209 [69413.935152] End test: tls.test_tls_handshake.TlsVhostHandshakeTest.test_vhost_sni Apr 26 11:21:03 192.168.122.209 [69413.975604] Start test: tls.test_tls_handshake.TlsVhostHandshakeTest.test_empty_sni_default Apr 26 11:21:04 192.168.122.209 [69415.306479] [tdb] Start Tempesta DB Apr 26 11:21:04 192.168.122.209 [69415.430822] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:21:05 192.168.122.209 [69416.419543] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69416.419543] Maybe that's fine, but it's worth checking the [69416.419543] config - if there is no relations between the [69416.419543] names, then host name confusion attack is possible. Apr 26 11:21:05 192.168.122.209 [69416.480235] [tempesta fw] Warning: Vhost vhost2.net doesn't have certificate with matching SAN/CN. [69416.480235] Maybe that's fine, but it's worth checking the [69416.480235] config - if there is no relations between the [69416.480235] names, then host name confusion attack is possible. Apr 26 11:21:05 192.168.122.209 [69416.582317] [tempesta fw] Configuration processing is completed. Apr 26 11:21:05 192.168.122.209 [69416.648329] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:21:06 192.168.122.209 [69416.680064] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:21:06 192.168.122.209 [69416.710074] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:21:06 192.168.122.209 [69416.802311] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:21:06 192.168.122.209 [69416.842241] [tempesta fw] Tempesta FW is ready Apr 26 11:21:06 192.168.122.209 [69417.063386] [tempesta fw] Warning: client 192.168.122.196 requested missing server name, reject connection. Apr 26 11:21:07 192.168.122.209 [69417.823637] [tdb] Close table 'client0.tdb' Apr 26 11:21:07 192.168.122.209 [69418.005250] [tdb] Close table 'sessions0.tdb' Apr 26 11:21:07 192.168.122.209 [69418.243000] [tdb] Close table 'filter0.tdb' Apr 26 11:21:07 192.168.122.209 [69418.243424] [tempesta fw] modules are stopped Apr 26 11:21:07 192.168.122.209 [69418.513274] [tempesta fw] exiting... Apr 26 11:21:07 192.168.122.209 [69418.630228] [tdb] Shutdown Tempesta DB Apr 26 11:21:08 192.168.122.209 [69419.001077] End test: tls.test_tls_handshake.TlsVhostHandshakeTest.test_empty_sni_default Apr 26 11:21:08 192.168.122.209 [69419.030378] Start test: tls.test_tls_handshake.TlsVhostHandshakeTest.test_bad_host Apr 26 11:21:09 192.168.122.209 [69420.269357] [tdb] Start Tempesta DB Apr 26 11:21:09 192.168.122.209 [69420.410617] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:21:10 192.168.122.209 [69421.439584] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69421.439584] Maybe that's fine, but it's worth checking the [69421.439584] config - if there is no relations between the [69421.439584] names, then host name confusion attack is possible. Apr 26 11:21:10 192.168.122.209 [69421.500240] [tempesta fw] Warning: Vhost vhost2.net doesn't have certificate with matching SAN/CN. [69421.500240] Maybe that's fine, but it's worth checking the [69421.500240] config - if there is no relations between the [69421.500240] names, then host name confusion attack is possible. Apr 26 11:21:10 192.168.122.209 [69421.566397] [tempesta fw] Configuration processing is completed. Apr 26 11:21:10 192.168.122.209 [69421.616883] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:21:10 192.168.122.209 [69421.644235] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:21:10 192.168.122.209 [69421.671743] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:21:11 192.168.122.209 [69421.726339] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:21:11 192.168.122.209 [69421.766292] [tempesta fw] Tempesta FW is ready Apr 26 11:21:11 192.168.122.209 [69422.021335] [tempesta fw] Warning: request has been filtered out via http table: 192.168.122.196 Apr 26 11:21:16 192.168.122.209 [69427.615601] [tdb] Close table 'client0.tdb' Apr 26 11:21:17 192.168.122.209 [69427.800874] [tdb] Close table 'sessions0.tdb' Apr 26 11:21:17 192.168.122.209 [69428.021899] [tdb] Close table 'filter0.tdb' Apr 26 11:21:17 192.168.122.209 [69428.022983] [tempesta fw] modules are stopped Apr 26 11:21:17 192.168.122.209 [69428.274410] [tempesta fw] exiting... Apr 26 11:21:17 192.168.122.209 [69428.409582] [tdb] Shutdown Tempesta DB Apr 26 11:21:20 192.168.122.209 [69430.688790] [tdb] Start Tempesta DB Apr 26 11:21:20 192.168.122.209 [69430.826376] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:21:21 192.168.122.209 [69431.819798] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69431.819798] Maybe that's fine, but it's worth checking the [69431.819798] config - if there is no relations between the [69431.819798] names, then host name confusion attack is possible. Apr 26 11:21:21 192.168.122.209 [69431.884492] [tempesta fw] Warning: Vhost vhost2.net doesn't have certificate with matching SAN/CN. [69431.884492] Maybe that's fine, but it's worth checking the [69431.884492] config - if there is no relations between the [69431.884492] names, then host name confusion attack is possible. Apr 26 11:21:21 192.168.122.209 [69431.958573] [tempesta fw] Configuration processing is completed. Apr 26 11:21:21 192.168.122.209 [69432.015388] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:21:21 192.168.122.209 [69432.046998] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:21:21 192.168.122.209 [69432.076542] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:21:21 192.168.122.209 [69432.146517] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:21:21 192.168.122.209 [69432.186370] [tempesta fw] Tempesta FW is ready Apr 26 11:21:21 192.168.122.209 [69432.453126] [tempesta fw] Warning: request has been filtered out via http table: 192.168.122.196 Apr 26 11:21:27 192.168.122.209 [69438.008850] [tdb] Close table 'client0.tdb' Apr 26 11:21:27 192.168.122.209 [69438.211495] [tdb] Close table 'sessions0.tdb' Apr 26 11:21:27 192.168.122.209 [69438.430819] [tdb] Close table 'filter0.tdb' Apr 26 11:21:27 192.168.122.209 [69438.431243] [tempesta fw] modules are stopped Apr 26 11:21:28 192.168.122.209 [69438.682851] [tempesta fw] exiting... Apr 26 11:21:28 192.168.122.209 [69438.829614] [tdb] Shutdown Tempesta DB Apr 26 11:21:28 192.168.122.209 [69439.231095] End test: tls.test_tls_handshake.TlsVhostHandshakeTest.test_bad_host Apr 26 11:21:28 192.168.122.209 [69439.263747] Start test: tls.test_tls_handshake.TlsMissingDefaultKey.test Apr 26 11:21:30 192.168.122.209 [69440.920415] [tdb] Start Tempesta DB Apr 26 11:21:30 192.168.122.209 [69441.053028] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:21:31 192.168.122.209 [69441.804494] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [69441.804494] Maybe that's fine, but it's worth checking the [69441.804494] config - if there is no relations between the [69441.804494] names, then host name confusion attack is possible. Apr 26 11:21:31 192.168.122.209 [69441.850970] [tempesta fw] Configuration processing is completed. Apr 26 11:21:31 192.168.122.209 [69441.906948] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:21:31 192.168.122.209 [69441.945492] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:21:31 192.168.122.209 [69441.974580] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:21:31 192.168.122.209 [69442.014602] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:21:31 192.168.122.209 [69442.054548] [tempesta fw] Tempesta FW is ready Apr 26 11:21:31 192.168.122.209 [69442.415937] [tempesta fw] Warning: client 192.168.122.196 requested unknown server name 'example.com' in TLS SNI, reject connection. Apr 26 11:21:31 192.168.122.209 [69442.522618] [tempesta fw] Warning: client 192.168.122.196 requested missing server name, reject connection. Apr 26 11:21:32 192.168.122.209 [69443.220640] [tdb] Close table 'client0.tdb' Apr 26 11:21:32 192.168.122.209 [69443.407934] [tdb] Close table 'sessions0.tdb' Apr 26 11:21:32 192.168.122.209 [69443.635463] [tdb] Close table 'filter0.tdb' Apr 26 11:21:32 192.168.122.209 [69443.635894] [tempesta fw] modules are stopped Apr 26 11:21:33 192.168.122.209 [69443.887398] [tempesta fw] exiting... Apr 26 11:21:33 192.168.122.209 [69444.030622] [tdb] Shutdown Tempesta DB Apr 26 11:21:33 192.168.122.209 [69444.435204] End test: tls.test_tls_handshake.TlsMissingDefaultKey.test Apr 26 11:21:33 192.168.122.209 [69444.470757] Start test: tls.test_tls_handshake.TlsHandshakeTest.test_tls12_synthetic Apr 26 11:21:35 192.168.122.209 [69445.993946] [tdb] Start Tempesta DB Apr 26 11:21:35 192.168.122.209 [69446.135606] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:21:36 192.168.122.209 [69446.871957] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69446.871957] Maybe that's fine, but it's worth checking the [69446.871957] config - if there is no relations between the [69446.871957] names, then host name confusion attack is possible. Apr 26 11:21:36 192.168.122.209 [69446.999032] [tempesta fw] Configuration processing is completed. Apr 26 11:21:36 192.168.122.209 [69447.060797] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:21:36 192.168.122.209 [69447.093226] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:21:36 192.168.122.209 [69447.125617] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:21:36 192.168.122.209 [69447.166688] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:21:36 192.168.122.209 [69447.210651] [tempesta fw] Tempesta FW is ready Apr 26 11:21:37 192.168.122.209 [69447.924607] [tdb] Close table 'client0.tdb' Apr 26 11:21:37 192.168.122.209 [69448.115118] [tdb] Close table 'sessions0.tdb' Apr 26 11:21:37 192.168.122.209 [69448.366449] [tdb] Close table 'filter0.tdb' Apr 26 11:21:37 192.168.122.209 [69448.366907] [tempesta fw] modules are stopped Apr 26 11:21:37 192.168.122.209 [69448.575374] [tempesta fw] exiting... Apr 26 11:21:38 192.168.122.209 [69448.716324] [tdb] Shutdown Tempesta DB Apr 26 11:21:38 192.168.122.209 [69449.050728] End test: tls.test_tls_handshake.TlsHandshakeTest.test_tls12_synthetic Apr 26 11:21:38 192.168.122.209 [69449.129534] Start test: tls.test_tls_handshake.TlsHandshakeTest.test_regression_1 Apr 26 11:21:39 192.168.122.209 [69450.591950] [tdb] Start Tempesta DB Apr 26 11:21:40 192.168.122.209 [69450.714720] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:21:40 192.168.122.209 [69451.475895] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69451.475895] Maybe that's fine, but it's worth checking the [69451.475895] config - if there is no relations between the [69451.475895] names, then host name confusion attack is possible. Apr 26 11:21:40 192.168.122.209 [69451.586801] [tempesta fw] Configuration processing is completed. Apr 26 11:21:40 192.168.122.209 [69451.642247] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:21:40 192.168.122.209 [69451.670177] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:21:41 192.168.122.209 [69451.700778] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:21:41 192.168.122.209 [69451.762745] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:21:41 192.168.122.209 [69451.802633] [tempesta fw] Tempesta FW is ready Apr 26 11:21:41 192.168.122.209 [69452.087603] [tempesta tls] Warning: [::ffff:192.168.122.196] TLS context isn't ready after handshake Apr 26 11:21:41 192.168.122.209 [69452.587558] [tdb] Close table 'client0.tdb' Apr 26 11:21:42 192.168.122.209 [69452.779220] [tdb] Close table 'sessions0.tdb' Apr 26 11:21:42 192.168.122.209 [69453.017634] [tdb] Close table 'filter0.tdb' Apr 26 11:21:42 192.168.122.209 [69453.018055] [tempesta fw] modules are stopped Apr 26 11:21:42 192.168.122.209 [69453.230675] [tempesta fw] exiting... Apr 26 11:21:42 192.168.122.209 [69453.362379] [tdb] Shutdown Tempesta DB Apr 26 11:21:43 192.168.122.209 [69453.808037] End test: tls.test_tls_handshake.TlsHandshakeTest.test_regression_1 Apr 26 11:21:43 192.168.122.209 [69453.837787] Start test: tls.test_tls_handshake.TlsHandshakeTest.test_old_handshakes Apr 26 11:21:44 192.168.122.209 [69455.347276] [tdb] Start Tempesta DB Apr 26 11:21:44 192.168.122.209 [69455.462333] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:21:45 192.168.122.209 [69456.192152] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69456.192152] Maybe that's fine, but it's worth checking the [69456.192152] config - if there is no relations between the [69456.192152] names, then host name confusion attack is possible. Apr 26 11:21:45 192.168.122.209 [69456.310888] [tempesta fw] Configuration processing is completed. Apr 26 11:21:45 192.168.122.209 [69456.368124] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:21:45 192.168.122.209 [69456.400639] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:21:45 192.168.122.209 [69456.430789] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:21:45 192.168.122.209 [69456.478804] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:21:45 192.168.122.209 [69456.522688] [tempesta fw] Tempesta FW is ready Apr 26 11:21:46 192.168.122.209 [69457.468233] [tdb] Close table 'client0.tdb' Apr 26 11:21:46 192.168.122.209 [69457.664666] [tdb] Close table 'sessions0.tdb' Apr 26 11:21:47 192.168.122.209 [69457.898108] [tdb] Close table 'filter0.tdb' Apr 26 11:21:47 192.168.122.209 [69457.898519] [tempesta fw] modules are stopped Apr 26 11:21:47 192.168.122.209 [69458.110726] [tempesta fw] exiting... Apr 26 11:21:47 192.168.122.209 [69458.223114] [tdb] Shutdown Tempesta DB Apr 26 11:21:47 192.168.122.209 [69458.600711] End test: tls.test_tls_handshake.TlsHandshakeTest.test_old_handshakes Apr 26 11:21:47 192.168.122.209 [69458.633765] Start test: tls.test_tls_handshake.TlsHandshakeTest.test_many_ciphers Apr 26 11:21:49 192.168.122.209 [69460.240930] [tdb] Start Tempesta DB Apr 26 11:21:49 192.168.122.209 [69460.366183] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:21:50 192.168.122.209 [69461.116100] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69461.116100] Maybe that's fine, but it's worth checking the [69461.116100] config - if there is no relations between the [69461.116100] names, then host name confusion attack is possible. Apr 26 11:21:50 192.168.122.209 [69461.234840] [tempesta fw] Configuration processing is completed. Apr 26 11:21:50 192.168.122.209 [69461.296425] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:21:50 192.168.122.209 [69461.323903] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:21:50 192.168.122.209 [69461.351663] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:21:50 192.168.122.209 [69461.434778] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:21:50 192.168.122.209 [69461.474803] [tempesta fw] Tempesta FW is ready Apr 26 11:21:51 192.168.122.209 [69462.360817] [tdb] Close table 'client0.tdb' Apr 26 11:21:51 192.168.122.209 [69462.545627] [tdb] Close table 'sessions0.tdb' Apr 26 11:21:52 192.168.122.209 [69462.813771] [tdb] Close table 'filter0.tdb' Apr 26 11:21:52 192.168.122.209 [69462.814192] [tempesta fw] modules are stopped Apr 26 11:21:52 192.168.122.209 [69463.028577] [tempesta fw] exiting... Apr 26 11:21:52 192.168.122.209 [69463.160120] [tdb] Shutdown Tempesta DB Apr 26 11:21:52 192.168.122.209 [69463.515126] End test: tls.test_tls_handshake.TlsHandshakeTest.test_many_ciphers Apr 26 11:21:52 192.168.122.209 [69463.599087] Start test: tls.test_tls_handshake.TlsHandshakeTest.test_long_sni Apr 26 11:21:54 192.168.122.209 [69465.205874] [tdb] Start Tempesta DB Apr 26 11:21:54 192.168.122.209 [69465.326505] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:21:55 192.168.122.209 [69466.111563] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69466.111563] Maybe that's fine, but it's worth checking the [69466.111563] config - if there is no relations between the [69466.111563] names, then host name confusion attack is possible. Apr 26 11:21:55 192.168.122.209 [69466.214959] [tempesta fw] Configuration processing is completed. Apr 26 11:21:55 192.168.122.209 [69466.265379] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:21:55 192.168.122.209 [69466.293068] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:21:55 192.168.122.209 [69466.322153] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:21:55 192.168.122.209 [69466.366871] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:21:55 192.168.122.209 [69466.422860] [tempesta fw] Tempesta FW is ready Apr 26 11:21:55 192.168.122.209 [69466.671326] [tempesta tls] Warning: [::ffff:192.168.122.196] ClientHello: bad extension size 1005 (remaining extensions size 1065) Apr 26 11:21:56 192.168.122.209 [69467.302878] [tdb] Close table 'client0.tdb' Apr 26 11:21:56 192.168.122.209 [69467.503668] [tdb] Close table 'sessions0.tdb' Apr 26 11:21:57 192.168.122.209 [69467.751744] [tdb] Close table 'filter0.tdb' Apr 26 11:21:57 192.168.122.209 [69467.752173] [tempesta fw] modules are stopped Apr 26 11:21:57 192.168.122.209 [69467.996244] [tempesta fw] exiting... Apr 26 11:21:57 192.168.122.209 [69468.109075] [tdb] Shutdown Tempesta DB Apr 26 11:21:57 192.168.122.209 [69468.487985] End test: tls.test_tls_handshake.TlsHandshakeTest.test_long_sni Apr 26 11:21:57 192.168.122.209 [69468.517676] Start test: tls.test_tls_handshake.TlsHandshakeTest.test_fuzzing Apr 26 11:21:59 192.168.122.209 [69470.072638] [tdb] Start Tempesta DB Apr 26 11:21:59 192.168.122.209 [69470.203778] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:22:00 192.168.122.209 [69470.948380] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69470.948380] Maybe that's fine, but it's worth checking the [69470.948380] config - if there is no relations between the [69470.948380] names, then host name confusion attack is possible. Apr 26 11:22:00 192.168.122.209 [69471.063053] [tempesta fw] Configuration processing is completed. Apr 26 11:22:00 192.168.122.209 [69471.128162] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:22:00 192.168.122.209 [69471.160944] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:22:00 192.168.122.209 [69471.193572] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:22:00 192.168.122.209 [69471.234984] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:22:00 192.168.122.209 [69471.278942] [tempesta fw] Tempesta FW is ready Apr 26 11:22:01 192.168.122.209 [69471.985675] [tdb] Close table 'client0.tdb' Apr 26 11:22:01 192.168.122.209 [69472.158640] [tdb] Close table 'sessions0.tdb' Apr 26 11:22:01 192.168.122.209 [69472.403150] [tdb] Close table 'filter0.tdb' Apr 26 11:22:01 192.168.122.209 [69472.403589] [tempesta fw] modules are stopped Apr 26 11:22:01 192.168.122.209 [69472.616677] [tempesta fw] exiting... Apr 26 11:22:02 192.168.122.209 [69472.738083] [tdb] Shutdown Tempesta DB Apr 26 11:22:02 192.168.122.209 [69473.109054] End test: tls.test_tls_handshake.TlsHandshakeTest.test_fuzzing Apr 26 11:22:02 192.168.122.209 [69473.137681] Start test: tls.test_tls_handshake.TlsHandshakeTest.test_empty_sni_default Apr 26 11:22:03 192.168.122.209 [69474.660228] [tdb] Start Tempesta DB Apr 26 11:22:04 192.168.122.209 [69474.793500] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:22:04 192.168.122.209 [69475.548363] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69475.548363] Maybe that's fine, but it's worth checking the [69475.548363] config - if there is no relations between the [69475.548363] names, then host name confusion attack is possible. Apr 26 11:22:04 192.168.122.209 [69475.663123] [tempesta fw] Configuration processing is completed. Apr 26 11:22:05 192.168.122.209 [69475.713838] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:22:05 192.168.122.209 [69475.741306] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:22:05 192.168.122.209 [69475.773404] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:22:05 192.168.122.209 [69475.843050] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:22:05 192.168.122.209 [69475.886982] [tempesta fw] Tempesta FW is ready Apr 26 11:22:05 192.168.122.209 [69476.116061] [tempesta fw] Warning: client 192.168.122.196 requested missing server name, reject connection. Apr 26 11:22:05 192.168.122.209 [69476.596869] [tdb] Close table 'client0.tdb' Apr 26 11:22:06 192.168.122.209 [69476.780344] [tdb] Close table 'sessions0.tdb' Apr 26 11:22:06 192.168.122.209 [69477.043465] [tdb] Close table 'filter0.tdb' Apr 26 11:22:06 192.168.122.209 [69477.043886] [tempesta fw] modules are stopped Apr 26 11:22:06 192.168.122.209 [69477.248487] [tempesta fw] exiting... Apr 26 11:22:06 192.168.122.209 [69477.366538] [tdb] Shutdown Tempesta DB Apr 26 11:22:07 192.168.122.209 [69477.726071] End test: tls.test_tls_handshake.TlsHandshakeTest.test_empty_sni_default Apr 26 11:22:07 192.168.122.209 [69477.811731] Start test: tls.test_tls_handshake.TlsHandshakeTest.test_close_notify Apr 26 11:22:08 192.168.122.209 [69479.276338] [tdb] Start Tempesta DB Apr 26 11:22:08 192.168.122.209 [69479.410991] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:22:09 192.168.122.209 [69480.136526] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69480.136526] Maybe that's fine, but it's worth checking the [69480.136526] config - if there is no relations between the [69480.136526] names, then host name confusion attack is possible. Apr 26 11:22:09 192.168.122.209 [69480.255148] [tempesta fw] Configuration processing is completed. Apr 26 11:22:09 192.168.122.209 [69480.309348] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:22:09 192.168.122.209 [69480.339782] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:22:09 192.168.122.209 [69480.368576] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:22:09 192.168.122.209 [69480.415111] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:22:09 192.168.122.209 [69480.455066] [tempesta fw] Tempesta FW is ready Apr 26 11:22:10 192.168.122.209 [69481.241917] [tdb] Close table 'client0.tdb' Apr 26 11:22:10 192.168.122.209 [69481.433666] [tdb] Close table 'sessions0.tdb' Apr 26 11:22:11 192.168.122.209 [69481.687991] [tdb] Close table 'filter0.tdb' Apr 26 11:22:11 192.168.122.209 [69481.688519] [tempesta fw] modules are stopped Apr 26 11:22:11 192.168.122.209 [69481.905307] [tempesta fw] exiting... Apr 26 11:22:11 192.168.122.209 [69482.029126] [tdb] Shutdown Tempesta DB Apr 26 11:22:11 192.168.122.209 [69482.459136] End test: tls.test_tls_handshake.TlsHandshakeTest.test_close_notify Apr 26 11:22:11 192.168.122.209 [69482.491498] Start test: tls.test_tls_handshake.TlsHandshakeTest.test_bad_sni Apr 26 11:22:13 192.168.122.209 [69484.139413] [tdb] Start Tempesta DB Apr 26 11:22:13 192.168.122.209 [69484.279196] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:22:14 192.168.122.209 [69485.056500] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69485.056500] Maybe that's fine, but it's worth checking the [69485.056500] config - if there is no relations between the [69485.056500] names, then host name confusion attack is possible. Apr 26 11:22:14 192.168.122.209 [69485.171234] [tempesta fw] Configuration processing is completed. Apr 26 11:22:14 192.168.122.209 [69485.226491] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:22:14 192.168.122.209 [69485.263681] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:22:14 192.168.122.209 [69485.295607] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:22:14 192.168.122.209 [69485.347170] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:22:14 192.168.122.209 [69485.391050] [tempesta fw] Tempesta FW is ready Apr 26 11:22:14 192.168.122.209 [69485.579923] [tempesta fw] Warning: client 192.168.122.196 requested unknown server name 'badservername' in TLS SNI, reject connection. Apr 26 11:22:15 192.168.122.209 [69486.230787] [tdb] Close table 'client0.tdb' Apr 26 11:22:15 192.168.122.209 [69486.415532] [tdb] Close table 'sessions0.tdb' Apr 26 11:22:15 192.168.122.209 [69486.658970] [tdb] Close table 'filter0.tdb' Apr 26 11:22:15 192.168.122.209 [69486.659429] [tempesta fw] modules are stopped Apr 26 11:22:16 192.168.122.209 [69486.892952] [tempesta fw] exiting... Apr 26 11:22:16 192.168.122.209 [69487.014772] [tdb] Shutdown Tempesta DB Apr 26 11:22:16 192.168.122.209 [69487.372427] End test: tls.test_tls_handshake.TlsHandshakeTest.test_bad_sni Apr 26 11:22:16 192.168.122.209 [69487.407318] Start test: tls.test_tls_handshake.TlsHandshakeTest.test_bad_sign_algs Apr 26 11:22:18 192.168.122.209 [69489.061130] [tdb] Start Tempesta DB Apr 26 11:22:18 192.168.122.209 [69489.188358] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:22:19 192.168.122.209 [69489.936721] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69489.936721] Maybe that's fine, but it's worth checking the [69489.936721] config - if there is no relations between the [69489.936721] names, then host name confusion attack is possible. Apr 26 11:22:19 192.168.122.209 [69490.059319] [tempesta fw] Configuration processing is completed. Apr 26 11:22:19 192.168.122.209 [69490.115599] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:22:19 192.168.122.209 [69490.147129] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:22:19 192.168.122.209 [69490.177720] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:22:19 192.168.122.209 [69490.223220] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:22:19 192.168.122.209 [69490.275171] [tempesta fw] Tempesta FW is ready Apr 26 11:22:19 192.168.122.209 [69490.460890] [tempesta tls] Warning: [::ffff:192.168.122.196] ClientHello: bad signature algorithm extension Apr 26 11:22:20 192.168.122.209 [69491.108372] [tdb] Close table 'client0.tdb' Apr 26 11:22:20 192.168.122.209 [69491.295815] [tdb] Close table 'sessions0.tdb' Apr 26 11:22:20 192.168.122.209 [69491.524047] [tdb] Close table 'filter0.tdb' Apr 26 11:22:20 192.168.122.209 [69491.524445] [tempesta fw] modules are stopped Apr 26 11:22:21 192.168.122.209 [69491.764106] [tempesta fw] exiting... Apr 26 11:22:21 192.168.122.209 [69491.943573] [tdb] Shutdown Tempesta DB Apr 26 11:22:21 192.168.122.209 [69492.329365] End test: tls.test_tls_handshake.TlsHandshakeTest.test_bad_sign_algs Apr 26 11:22:21 192.168.122.209 [69492.352955] Start test: tls.test_tls_handshake.TlsHandshakeTest.test_bad_renegotiation_info Apr 26 11:22:23 192.168.122.209 [69493.976923] [tdb] Start Tempesta DB Apr 26 11:22:23 192.168.122.209 [69494.102557] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:22:24 192.168.122.209 [69494.840611] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69494.840611] Maybe that's fine, but it's worth checking the [69494.840611] config - if there is no relations between the [69494.840611] names, then host name confusion attack is possible. Apr 26 11:22:24 192.168.122.209 [69494.959555] [tempesta fw] Configuration processing is completed. Apr 26 11:22:24 192.168.122.209 [69495.017207] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:22:24 192.168.122.209 [69495.050058] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:22:24 192.168.122.209 [69495.082515] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:22:24 192.168.122.209 [69495.123308] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:22:24 192.168.122.209 [69495.163258] [tempesta fw] Tempesta FW is ready Apr 26 11:22:24 192.168.122.209 [69495.412101] [tempesta tls] Warning: [::ffff:192.168.122.196] ClientHello: bad renegotiation_info extension Apr 26 11:22:25 192.168.122.209 [69496.074061] [tdb] Close table 'client0.tdb' Apr 26 11:22:25 192.168.122.209 [69496.250828] [tdb] Close table 'sessions0.tdb' Apr 26 11:22:25 192.168.122.209 [69496.482959] [tdb] Close table 'filter0.tdb' Apr 26 11:22:25 192.168.122.209 [69496.483392] [tempesta fw] modules are stopped Apr 26 11:22:26 192.168.122.209 [69496.731712] [tempesta fw] exiting... Apr 26 11:22:26 192.168.122.209 [69496.847171] [tdb] Shutdown Tempesta DB Apr 26 11:22:26 192.168.122.209 [69497.215939] End test: tls.test_tls_handshake.TlsHandshakeTest.test_bad_renegotiation_info Apr 26 11:22:26 192.168.122.209 [69497.250019] Start test: tls.test_tls_handshake.TlsHandshakeTest.test_bad_elliptic_curves Apr 26 11:22:28 192.168.122.209 [69498.912004] [tdb] Start Tempesta DB Apr 26 11:22:28 192.168.122.209 [69499.050496] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:22:29 192.168.122.209 [69499.760667] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69499.760667] Maybe that's fine, but it's worth checking the [69499.760667] config - if there is no relations between the [69499.760667] names, then host name confusion attack is possible. Apr 26 11:22:29 192.168.122.209 [69499.875448] [tempesta fw] Configuration processing is completed. Apr 26 11:22:29 192.168.122.209 [69499.926992] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:22:29 192.168.122.209 [69499.955750] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:22:29 192.168.122.209 [69499.984455] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:22:29 192.168.122.209 [69500.023294] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:22:29 192.168.122.209 [69500.071339] [tempesta fw] Tempesta FW is ready Apr 26 11:22:29 192.168.122.209 [69500.315643] [tempesta tls] Warning: [::ffff:192.168.122.196] None of the common ciphersuites is usable (e.g. no suitable certificate), like TLS-ECDHE-RSA-WITH-AES-256-GCM-SHA384 Apr 26 11:22:30 192.168.122.209 [69500.966796] [tdb] Close table 'client0.tdb' Apr 26 11:22:30 192.168.122.209 [69501.142911] [tdb] Close table 'sessions0.tdb' Apr 26 11:22:30 192.168.122.209 [69501.374166] [tdb] Close table 'filter0.tdb' Apr 26 11:22:30 192.168.122.209 [69501.374591] [tempesta fw] modules are stopped Apr 26 11:22:30 192.168.122.209 [69501.637349] [tempesta fw] exiting... Apr 26 11:22:31 192.168.122.209 [69501.758855] [tdb] Shutdown Tempesta DB Apr 26 11:22:31 192.168.122.209 [69502.141416] End test: tls.test_tls_handshake.TlsHandshakeTest.test_bad_elliptic_curves Apr 26 11:22:31 192.168.122.209 [69502.178025] Start test: tls.test_tls_handshake.TlsHandshakeTest.test_alert Apr 26 11:22:32 192.168.122.209 [69503.659659] [tdb] Start Tempesta DB Apr 26 11:22:33 192.168.122.209 [69503.781166] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:22:33 192.168.122.209 [69504.488761] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69504.488761] Maybe that's fine, but it's worth checking the [69504.488761] config - if there is no relations between the [69504.488761] names, then host name confusion attack is possible. Apr 26 11:22:33 192.168.122.209 [69504.619478] [tempesta fw] Configuration processing is completed. Apr 26 11:22:34 192.168.122.209 [69504.679625] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:22:34 192.168.122.209 [69504.711599] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:22:34 192.168.122.209 [69504.741690] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:22:34 192.168.122.209 [69504.779429] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:22:34 192.168.122.209 [69504.819376] [tempesta fw] Tempesta FW is ready Apr 26 11:22:35 192.168.122.209 [69506.496448] [tdb] Close table 'client0.tdb' Apr 26 11:22:36 192.168.122.209 [69506.695078] [tdb] Close table 'sessions0.tdb' Apr 26 11:22:36 192.168.122.209 [69506.931218] [tdb] Close table 'filter0.tdb' Apr 26 11:22:36 192.168.122.209 [69506.931663] [tempesta fw] modules are stopped Apr 26 11:22:36 192.168.122.209 [69507.210605] [tempesta fw] exiting... Apr 26 11:22:36 192.168.122.209 [69507.368373] [tdb] Shutdown Tempesta DB Apr 26 11:22:37 192.168.122.209 [69507.769650] End test: tls.test_tls_handshake.TlsHandshakeTest.test_alert Apr 26 11:22:37 192.168.122.209 [69507.802414] Start test: tls.test_tls_handshake.TlsHandshakeTest.test_9byte_transfer Apr 26 11:22:38 192.168.122.209 [69509.301529] [tdb] Start Tempesta DB Apr 26 11:22:38 192.168.122.209 [69509.424079] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:22:39 192.168.122.209 [69510.192871] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69510.192871] Maybe that's fine, but it's worth checking the [69510.192871] config - if there is no relations between the [69510.192871] names, then host name confusion attack is possible. Apr 26 11:22:39 192.168.122.209 [69510.307581] [tempesta fw] Configuration processing is completed. Apr 26 11:22:39 192.168.122.209 [69510.372726] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:22:39 192.168.122.209 [69510.405278] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:22:39 192.168.122.209 [69510.434920] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:22:39 192.168.122.209 [69510.483584] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:22:39 192.168.122.209 [69510.527444] [tempesta fw] Tempesta FW is ready Apr 26 11:22:40 192.168.122.209 [69511.312010] [tdb] Close table 'client0.tdb' Apr 26 11:22:40 192.168.122.209 [69511.507799] [tdb] Close table 'sessions0.tdb' Apr 26 11:22:41 192.168.122.209 [69511.725837] [tdb] Close table 'filter0.tdb' Apr 26 11:22:41 192.168.122.209 [69511.726290] [tempesta fw] modules are stopped Apr 26 11:22:41 192.168.122.209 [69511.935399] [tempesta fw] exiting... Apr 26 11:22:41 192.168.122.209 [69512.064990] [tdb] Shutdown Tempesta DB Apr 26 11:22:41 192.168.122.209 [69512.437261] End test: tls.test_tls_handshake.TlsHandshakeTest.test_9byte_transfer Apr 26 11:22:41 192.168.122.209 [69512.520452] Start test: tls.test_tls_handshake.TlsHandshakeTest.test_1byte_transfer Apr 26 11:22:43 192.168.122.209 [69513.996481] [tdb] Start Tempesta DB Apr 26 11:22:43 192.168.122.209 [69514.127959] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:22:44 192.168.122.209 [69514.880878] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69514.880878] Maybe that's fine, but it's worth checking the [69514.880878] config - if there is no relations between the [69514.880878] names, then host name confusion attack is possible. Apr 26 11:22:44 192.168.122.209 [69514.995526] [tempesta fw] Configuration processing is completed. Apr 26 11:22:44 192.168.122.209 [69515.046646] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:22:44 192.168.122.209 [69515.074950] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:22:44 192.168.122.209 [69515.104542] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:22:44 192.168.122.209 [69515.155556] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:22:44 192.168.122.209 [69515.195505] [tempesta fw] Tempesta FW is ready Apr 26 11:22:45 192.168.122.209 [69515.994287] [tdb] Close table 'client0.tdb' Apr 26 11:22:45 192.168.122.209 [69516.193299] [tdb] Close table 'sessions0.tdb' Apr 26 11:22:45 192.168.122.209 [69516.444249] [tdb] Close table 'filter0.tdb' Apr 26 11:22:45 192.168.122.209 [69516.444666] [tempesta fw] modules are stopped Apr 26 11:22:45 192.168.122.209 [69516.660321] [tempesta fw] exiting... Apr 26 11:22:46 192.168.122.209 [69516.790837] [tdb] Shutdown Tempesta DB Apr 26 11:22:46 192.168.122.209 [69517.216804] End test: tls.test_tls_handshake.TlsHandshakeTest.test_1byte_transfer Apr 26 11:22:46 192.168.122.209 [69517.303694] Start test: tls.test_tls_handshake.TlsHandshakeTest.test_10byte_transfer Apr 26 11:22:48 192.168.122.209 [69518.760344] [tdb] Start Tempesta DB Apr 26 11:22:48 192.168.122.209 [69518.903526] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:22:48 192.168.122.209 [69519.608898] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69519.608898] Maybe that's fine, but it's worth checking the [69519.608898] config - if there is no relations between the [69519.608898] names, then host name confusion attack is possible. Apr 26 11:22:49 192.168.122.209 [69519.727633] [tempesta fw] Configuration processing is completed. Apr 26 11:22:49 192.168.122.209 [69519.786891] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:22:49 192.168.122.209 [69519.820229] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:22:49 192.168.122.209 [69519.853544] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:22:49 192.168.122.209 [69519.939615] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:22:49 192.168.122.209 [69519.983595] [tempesta fw] Tempesta FW is ready Apr 26 11:22:50 192.168.122.209 [69520.747148] [tdb] Close table 'client0.tdb' Apr 26 11:22:50 192.168.122.209 [69520.934775] [tdb] Close table 'sessions0.tdb' Apr 26 11:22:50 192.168.122.209 [69521.184224] [tdb] Close table 'filter0.tdb' Apr 26 11:22:50 192.168.122.209 [69521.184643] [tempesta fw] modules are stopped Apr 26 11:22:50 192.168.122.209 [69521.421398] [tempesta fw] exiting... Apr 26 11:22:50 192.168.122.209 [69521.566404] [tdb] Shutdown Tempesta DB Apr 26 11:22:51 192.168.122.209 [69521.947338] End test: tls.test_tls_handshake.TlsHandshakeTest.test_10byte_transfer Apr 26 11:22:51 192.168.122.209 [69521.979767] Start test: tls.test_tls_handshake.TlsCertReconfig.test Apr 26 11:22:52 192.168.122.209 [69523.516523] [tdb] Start Tempesta DB Apr 26 11:22:52 192.168.122.209 [69523.652521] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:22:53 192.168.122.209 [69524.440930] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69524.440930] Maybe that's fine, but it's worth checking the [69524.440930] config - if there is no relations between the [69524.440930] names, then host name confusion attack is possible. Apr 26 11:22:53 192.168.122.209 [69524.563715] [tempesta fw] Configuration processing is completed. Apr 26 11:22:53 192.168.122.209 [69524.612194] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:22:53 192.168.122.209 [69524.640309] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:22:53 192.168.122.209 [69524.668411] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:22:54 192.168.122.209 [69524.715691] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:22:54 192.168.122.209 [69524.759679] [tempesta fw] Tempesta FW is ready Apr 26 11:22:55 192.168.122.209 [69525.993879] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 11:22:55 192.168.122.209 [69526.052970] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69526.052970] Maybe that's fine, but it's worth checking the [69526.052970] config - if there is no relations between the [69526.052970] names, then host name confusion attack is possible. Apr 26 11:22:55 192.168.122.209 [69526.179732] [tempesta fw] Configuration processing is completed. Apr 26 11:22:55 192.168.122.209 [69526.300208] [tempesta fw] Tempesta FW is ready Apr 26 11:22:56 192.168.122.209 [69526.979926] [tdb] Close table 'client0.tdb' Apr 26 11:22:56 192.168.122.209 [69527.178649] [tdb] Close table 'sessions0.tdb' Apr 26 11:22:56 192.168.122.209 [69527.410999] [tdb] Close table 'filter0.tdb' Apr 26 11:22:56 192.168.122.209 [69527.411402] [tempesta fw] modules are stopped Apr 26 11:22:56 192.168.122.209 [69527.625461] [tempesta fw] exiting... Apr 26 11:22:57 192.168.122.209 [69527.758162] [tdb] Shutdown Tempesta DB Apr 26 11:22:57 192.168.122.209 [69528.146776] End test: tls.test_tls_handshake.TlsCertReconfig.test Apr 26 11:22:57 192.168.122.209 [69528.172832] Start test: tls.test_tls_cert.WrkTestsMultipleVhosts.test_wrk Apr 26 11:22:59 192.168.122.209 [69530.153431] [tdb] Start Tempesta DB Apr 26 11:22:59 192.168.122.209 [69530.299003] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:23:00 192.168.122.209 [69531.233981] [tempesta fw] Warning: Vhost localhost doesn't have certificate with matching SAN/CN. [69531.233981] Maybe that's fine, but it's worth checking the [69531.233981] config - if there is no relations between the [69531.233981] names, then host name confusion attack is possible. Apr 26 11:23:00 192.168.122.209 [69531.262074] [tempesta fw] Warning: Vhost private.example.com doesn't have certificate with matching SAN/CN. [69531.262074] Maybe that's fine, but it's worth checking the [69531.262074] config - if there is no relations between the [69531.262074] names, then host name confusion attack is possible. Apr 26 11:23:00 192.168.122.209 [69531.331807] [tempesta fw] Configuration processing is completed. Apr 26 11:23:00 192.168.122.209 [69531.396609] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:23:00 192.168.122.209 [69531.431494] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:23:00 192.168.122.209 [69531.464838] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:23:00 192.168.122.209 [69531.515796] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:23:00 192.168.122.209 [69531.559702] [tempesta fw] Tempesta FW is ready Apr 26 11:23:01 192.168.122.209 [69532.646382] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 11:23:02 192.168.122.209 [69532.771821] [tempesta fw] Warning: Vhost private.example.com doesn't have certificate with matching SAN/CN. [69532.771821] Maybe that's fine, but it's worth checking the [69532.771821] config - if there is no relations between the [69532.771821] names, then host name confusion attack is possible. Apr 26 11:23:02 192.168.122.209 [69532.796815] [tempesta fw] Warning: Vhost localhost doesn't have certificate with matching SAN/CN. [69532.796815] Maybe that's fine, but it's worth checking the [69532.796815] config - if there is no relations between the [69532.796815] names, then host name confusion attack is possible. Apr 26 11:23:02 192.168.122.209 [69532.871641] [tempesta fw] Configuration processing is completed. Apr 26 11:23:02 192.168.122.209 [69533.259662] [tempesta fw] Tempesta FW is ready Apr 26 11:23:03 192.168.122.209 [69534.004408] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 11:23:03 192.168.122.209 [69534.576239] [tempesta fw] Tempesta FW is ready Apr 26 11:23:04 192.168.122.209 [69535.416985] net_ratelimit: 4 callbacks suppressed Apr 26 11:23:04 192.168.122.209 [69535.416991] [tempesta fw] Warning: Vhost private.example.com doesn't have certificate with matching SAN/CN. [69535.416991] Maybe that's fine, but it's worth checking the [69535.416991] config - if there is no relations between the [69535.416991] names, then host name confusion attack is possible. Apr 26 11:23:04 192.168.122.209 [69535.444599] [tempesta fw] Warning: Vhost localhost doesn't have certificate with matching SAN/CN. [69535.444599] Maybe that's fine, but it's worth checking the [69535.444599] config - if there is no relations between the [69535.444599] names, then host name confusion attack is possible. Apr 26 11:23:04 192.168.122.209 [69535.523989] [tempesta fw] Configuration processing is completed. Apr 26 11:23:05 192.168.122.209 [69535.872269] [tempesta fw] Tempesta FW is ready Apr 26 11:23:05 192.168.122.209 [69536.636844] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 11:23:06 192.168.122.209 [69536.748716] [tempesta fw] Warning: Vhost localhost doesn't have certificate with matching SAN/CN. [69536.748716] Maybe that's fine, but it's worth checking the [69536.748716] config - if there is no relations between the [69536.748716] names, then host name confusion attack is possible. Apr 26 11:23:06 192.168.122.209 [69536.785763] [tempesta fw] Warning: Vhost private.example.com doesn't have certificate with matching SAN/CN. [69536.785763] Maybe that's fine, but it's worth checking the [69536.785763] config - if there is no relations between the [69536.785763] names, then host name confusion attack is possible. Apr 26 11:23:06 192.168.122.209 [69536.868307] [tempesta fw] Configuration processing is completed. Apr 26 11:23:06 192.168.122.209 [69537.200282] [tempesta fw] Tempesta FW is ready Apr 26 11:23:07 192.168.122.209 [69537.951102] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 11:23:07 192.168.122.209 [69538.100268] [tempesta fw] Warning: Vhost private.example.com doesn't have certificate with matching SAN/CN. [69538.100268] Maybe that's fine, but it's worth checking the [69538.100268] config - if there is no relations between the [69538.100268] names, then host name confusion attack is possible. Apr 26 11:23:07 192.168.122.209 [69538.149605] [tempesta fw] Warning: Vhost localhost doesn't have certificate with matching SAN/CN. [69538.149605] Maybe that's fine, but it's worth checking the [69538.149605] config - if there is no relations between the [69538.149605] names, then host name confusion attack is possible. Apr 26 11:23:07 192.168.122.209 [69538.588062] [tempesta fw] Tempesta FW is ready Apr 26 11:23:09 192.168.122.209 [69539.792571] [tempesta fw] Tempesta FW is ready Apr 26 11:23:09 192.168.122.209 [69540.569898] net_ratelimit: 5 callbacks suppressed Apr 26 11:23:09 192.168.122.209 [69540.569900] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 11:23:10 192.168.122.209 [69540.681974] [tempesta fw] Warning: Vhost private.example.com doesn't have certificate with matching SAN/CN. [69540.681974] Maybe that's fine, but it's worth checking the [69540.681974] config - if there is no relations between the [69540.681974] names, then host name confusion attack is possible. Apr 26 11:23:10 192.168.122.209 [69540.713210] [tempesta fw] Warning: Vhost localhost doesn't have certificate with matching SAN/CN. [69540.713210] Maybe that's fine, but it's worth checking the [69540.713210] config - if there is no relations between the [69540.713210] names, then host name confusion attack is possible. Apr 26 11:23:10 192.168.122.209 [69540.800022] [tempesta fw] Configuration processing is completed. Apr 26 11:23:10 192.168.122.209 [69541.136243] [tempesta fw] Tempesta FW is ready Apr 26 11:23:11 192.168.122.209 [69541.812332] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 11:23:11 192.168.122.209 [69541.913719] [tempesta fw] Warning: Vhost localhost doesn't have certificate with matching SAN/CN. [69541.913719] Maybe that's fine, but it's worth checking the [69541.913719] config - if there is no relations between the [69541.913719] names, then host name confusion attack is possible. Apr 26 11:23:11 192.168.122.209 [69541.945958] [tempesta fw] Warning: Vhost private.example.com doesn't have certificate with matching SAN/CN. [69541.945958] Maybe that's fine, but it's worth checking the [69541.945958] config - if there is no relations between the [69541.945958] names, then host name confusion attack is possible. Apr 26 11:23:11 192.168.122.209 [69542.019949] [tempesta fw] Configuration processing is completed. Apr 26 11:23:11 192.168.122.209 [69542.172333] [tempesta fw] Tempesta FW is ready Apr 26 11:23:12 192.168.122.209 [69543.093566] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 11:23:12 192.168.122.209 [69543.181976] [tempesta fw] Warning: Vhost private.example.com doesn't have certificate with matching SAN/CN. [69543.181976] Maybe that's fine, but it's worth checking the [69543.181976] config - if there is no relations between the [69543.181976] names, then host name confusion attack is possible. Apr 26 11:23:12 192.168.122.209 [69543.456311] [tempesta fw] Tempesta FW is ready Apr 26 11:23:13 192.168.122.209 [69544.640389] [tempesta fw] Tempesta FW is ready Apr 26 11:23:14 192.168.122.209 [69545.168304] [tdb] Close table 'client0.tdb' Apr 26 11:23:14 192.168.122.209 [69545.366449] [tdb] Close table 'sessions0.tdb' Apr 26 11:23:14 192.168.122.209 [69545.605693] [tdb] Close table 'filter0.tdb' Apr 26 11:23:14 192.168.122.209 [69545.606109] [tempesta fw] modules are stopped Apr 26 11:23:15 192.168.122.209 [69545.828401] [tempesta fw] exiting... Apr 26 11:23:15 192.168.122.209 [69545.977907] [tdb] Shutdown Tempesta DB Apr 26 11:23:15 192.168.122.209 [69546.399480] End test: tls.test_tls_cert.WrkTestsMultipleVhosts.test_wrk Apr 26 11:23:15 192.168.122.209 [69546.436262] Start test: tls.test_tls_cert.TlsSniWithHttpTableMultiH2.test_alternating_access Apr 26 11:23:17 192.168.122.209 [69547.957574] [tdb] Start Tempesta DB Apr 26 11:23:17 192.168.122.209 [69548.096545] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:23:18 192.168.122.209 [69549.166175] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [69549.166175] Maybe that's fine, but it's worth checking the [69549.166175] config - if there is no relations between the [69549.166175] names, then host name confusion attack is possible. Apr 26 11:23:18 192.168.122.209 [69549.280097] [tempesta fw] Configuration processing is completed. Apr 26 11:23:18 192.168.122.209 [69549.343503] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:23:18 192.168.122.209 [69549.377128] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:23:18 192.168.122.209 [69549.410102] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:23:18 192.168.122.209 [69549.476010] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:23:18 192.168.122.209 [69549.535940] [tempesta fw] Tempesta FW is ready Apr 26 11:23:19 192.168.122.209 [69549.761685] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 192.168.122.196 ('example.com' vs 'localhost-vhost') Apr 26 11:23:19 192.168.122.209 [69549.765264] [tempesta fw] Warning: parsed request has been filtered out: 192.168.122.196 Apr 26 11:23:19 192.168.122.209 [69550.284718] [tdb] Close table 'client0.tdb' Apr 26 11:23:19 192.168.122.209 [69550.472666] [tdb] Close table 'sessions0.tdb' Apr 26 11:23:20 192.168.122.209 [69550.718562] [tdb] Close table 'filter0.tdb' Apr 26 11:23:20 192.168.122.209 [69550.718983] [tempesta fw] modules are stopped Apr 26 11:23:20 192.168.122.209 [69550.936579] [tempesta fw] exiting... Apr 26 11:23:20 192.168.122.209 [69551.066946] [tdb] Shutdown Tempesta DB Apr 26 11:23:20 192.168.122.209 [69551.454323] End test: tls.test_tls_cert.TlsSniWithHttpTableMultiH2.test_alternating_access Apr 26 11:23:20 192.168.122.209 [69551.486591] Start test: tls.test_tls_cert.TlsSniWithHttpTableMulti.test_alternating_access Apr 26 11:23:22 192.168.122.209 [69552.965526] [tdb] Start Tempesta DB Apr 26 11:23:22 192.168.122.209 [69553.102426] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:23:23 192.168.122.209 [69554.158123] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [69554.158123] Maybe that's fine, but it's worth checking the [69554.158123] config - if there is no relations between the [69554.158123] names, then host name confusion attack is possible. Apr 26 11:23:23 192.168.122.209 [69554.244122] [tempesta fw] Configuration processing is completed. Apr 26 11:23:23 192.168.122.209 [69554.317177] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:23:23 192.168.122.209 [69554.348578] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:23:23 192.168.122.209 [69554.377757] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:23:23 192.168.122.209 [69554.444047] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:23:23 192.168.122.209 [69554.484006] [tempesta fw] Tempesta FW is ready Apr 26 11:23:24 192.168.122.209 [69554.690011] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 192.168.122.196 ('example.com' vs 'localhost-vhost') Apr 26 11:23:24 192.168.122.209 [69554.693592] [tempesta fw] Warning: parsed request has been filtered out: 192.168.122.196 Apr 26 11:23:24 192.168.122.209 [69555.205485] [tdb] Close table 'client0.tdb' Apr 26 11:23:24 192.168.122.209 [69555.392387] [tdb] Close table 'sessions0.tdb' Apr 26 11:23:24 192.168.122.209 [69555.642050] [tdb] Close table 'filter0.tdb' Apr 26 11:23:24 192.168.122.209 [69555.642451] [tempesta fw] modules are stopped Apr 26 11:23:25 192.168.122.209 [69555.879383] [tempesta fw] exiting... Apr 26 11:23:25 192.168.122.209 [69555.991965] [tdb] Shutdown Tempesta DB Apr 26 11:23:25 192.168.122.209 [69556.366314] End test: tls.test_tls_cert.TlsSniWithHttpTableMulti.test_alternating_access Apr 26 11:23:25 192.168.122.209 [69556.395977] Start test: tls.test_tls_cert.TlsSniWithHttpTable.test_with_san Apr 26 11:23:27 192.168.122.209 [69557.915829] [tdb] Start Tempesta DB Apr 26 11:23:27 192.168.122.209 [69558.054966] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:23:28 192.168.122.209 [69559.422046] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [69559.422046] Maybe that's fine, but it's worth checking the [69559.422046] config - if there is no relations between the [69559.422046] names, then host name confusion attack is possible. Apr 26 11:23:28 192.168.122.209 [69559.478031] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [69559.478031] Maybe that's fine, but it's worth checking the [69559.478031] config - if there is no relations between the [69559.478031] names, then host name confusion attack is possible. Apr 26 11:23:28 192.168.122.209 [69559.588113] [tempesta fw] Configuration processing is completed. Apr 26 11:23:28 192.168.122.209 [69559.647363] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:23:28 192.168.122.209 [69559.676001] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:23:29 192.168.122.209 [69559.706638] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:23:29 192.168.122.209 [69559.820126] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:23:29 192.168.122.209 [69559.924100] [tempesta fw] Tempesta FW is ready Apr 26 11:23:29 192.168.122.209 [69560.088071] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 192.168.122.196 ('tempesta-tech.com' vs 'localhost-vhost') Apr 26 11:23:29 192.168.122.209 [69560.091714] [tempesta fw] Warning: parsed request has been filtered out: 192.168.122.196 Apr 26 11:23:30 192.168.122.209 [69560.691237] [tdb] Close table 'client0.tdb' Apr 26 11:23:30 192.168.122.209 [69560.875139] [tdb] Close table 'sessions0.tdb' Apr 26 11:23:30 192.168.122.209 [69561.122133] [tdb] Close table 'filter0.tdb' Apr 26 11:23:30 192.168.122.209 [69561.122557] [tempesta fw] modules are stopped Apr 26 11:23:30 192.168.122.209 [69561.400875] [tempesta fw] exiting... Apr 26 11:23:30 192.168.122.209 [69561.520999] [tdb] Shutdown Tempesta DB Apr 26 11:23:31 192.168.122.209 [69561.894450] End test: tls.test_tls_cert.TlsSniWithHttpTable.test_with_san Apr 26 11:23:31 192.168.122.209 [69561.926706] Start test: tls.test_tls_cert.TlsSniWithHttpTable.test_with_common_name Apr 26 11:23:32 192.168.122.209 [69563.375782] [tdb] Start Tempesta DB Apr 26 11:23:32 192.168.122.209 [69563.506687] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:23:34 192.168.122.209 [69564.858171] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [69564.858171] Maybe that's fine, but it's worth checking the [69564.858171] config - if there is no relations between the [69564.858171] names, then host name confusion attack is possible. Apr 26 11:23:34 192.168.122.209 [69564.890331] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [69564.890331] Maybe that's fine, but it's worth checking the [69564.890331] config - if there is no relations between the [69564.890331] names, then host name confusion attack is possible. Apr 26 11:23:34 192.168.122.209 [69564.996263] [tempesta fw] Configuration processing is completed. Apr 26 11:23:34 192.168.122.209 [69565.060297] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:23:34 192.168.122.209 [69565.092039] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:23:34 192.168.122.209 [69565.122104] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:23:34 192.168.122.209 [69565.232182] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:23:34 192.168.122.209 [69565.292132] [tempesta fw] Tempesta FW is ready Apr 26 11:23:34 192.168.122.209 [69565.437443] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 192.168.122.196 ('tempesta-tech.com' vs 'localhost-vhost') Apr 26 11:23:34 192.168.122.209 [69565.441097] [tempesta fw] Warning: parsed request has been filtered out: 192.168.122.196 Apr 26 11:23:35 192.168.122.209 [69566.035599] [tdb] Close table 'client0.tdb' Apr 26 11:23:35 192.168.122.209 [69566.207167] [tdb] Close table 'sessions0.tdb' Apr 26 11:23:35 192.168.122.209 [69566.417217] [tdb] Close table 'filter0.tdb' Apr 26 11:23:35 192.168.122.209 [69566.417649] [tempesta fw] modules are stopped Apr 26 11:23:36 192.168.122.209 [69566.708612] [tempesta fw] exiting... Apr 26 11:23:36 192.168.122.209 [69566.858456] [tdb] Shutdown Tempesta DB Apr 26 11:23:36 192.168.122.209 [69567.275947] End test: tls.test_tls_cert.TlsSniWithHttpTable.test_with_common_name Apr 26 11:23:36 192.168.122.209 [69567.302233] Start test: tls.test_tls_cert.TlsSniWithHttpTable.test_with_any_host Apr 26 11:23:38 192.168.122.209 [69568.901997] [tdb] Start Tempesta DB Apr 26 11:23:38 192.168.122.209 [69569.041815] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:23:39 192.168.122.209 [69570.442435] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [69570.442435] Maybe that's fine, but it's worth checking the [69570.442435] config - if there is no relations between the [69570.442435] names, then host name confusion attack is possible. Apr 26 11:23:39 192.168.122.209 [69570.469644] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [69570.469644] Maybe that's fine, but it's worth checking the [69570.469644] config - if there is no relations between the [69570.469644] names, then host name confusion attack is possible. Apr 26 11:23:39 192.168.122.209 [69570.588393] [tempesta fw] Configuration processing is completed. Apr 26 11:23:39 192.168.122.209 [69570.649629] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:23:40 192.168.122.209 [69570.682554] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:23:40 192.168.122.209 [69570.712855] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:23:40 192.168.122.209 [69570.868285] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:23:40 192.168.122.209 [69570.940209] [tempesta fw] Tempesta FW is ready Apr 26 11:23:40 192.168.122.209 [69571.104119] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 192.168.122.196 ('tempesta-tech.com' vs 'default-vhost') Apr 26 11:23:40 192.168.122.209 [69571.107787] [tempesta fw] Warning: parsed request has been filtered out: 192.168.122.196 Apr 26 11:23:41 192.168.122.209 [69571.777202] [tdb] Close table 'client0.tdb' Apr 26 11:23:41 192.168.122.209 [69571.981054] [tdb] Close table 'sessions0.tdb' Apr 26 11:23:41 192.168.122.209 [69572.214608] [tdb] Close table 'filter0.tdb' Apr 26 11:23:41 192.168.122.209 [69572.215035] [tempesta fw] modules are stopped Apr 26 11:23:41 192.168.122.209 [69572.481940] [tempesta fw] exiting... Apr 26 11:23:41 192.168.122.209 [69572.618316] [tdb] Shutdown Tempesta DB Apr 26 11:23:42 192.168.122.209 [69573.047329] End test: tls.test_tls_cert.TlsSniWithHttpTable.test_with_any_host Apr 26 11:23:42 192.168.122.209 [69573.085853] Start test: tls.test_tls_cert.TlsSniWithHttpTable.test_valid Apr 26 11:23:43 192.168.122.209 [69574.650930] [tdb] Start Tempesta DB Apr 26 11:23:44 192.168.122.209 [69574.785854] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:23:45 192.168.122.209 [69576.118386] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [69576.118386] Maybe that's fine, but it's worth checking the [69576.118386] config - if there is no relations between the [69576.118386] names, then host name confusion attack is possible. Apr 26 11:23:45 192.168.122.209 [69576.146020] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [69576.146020] Maybe that's fine, but it's worth checking the [69576.146020] config - if there is no relations between the [69576.146020] names, then host name confusion attack is possible. Apr 26 11:23:45 192.168.122.209 [69576.240715] [tempesta fw] Configuration processing is completed. Apr 26 11:23:45 192.168.122.209 [69576.296753] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:23:45 192.168.122.209 [69576.327789] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:23:45 192.168.122.209 [69576.357191] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:23:45 192.168.122.209 [69576.532361] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:23:45 192.168.122.209 [69576.572287] [tempesta fw] Tempesta FW is ready Apr 26 11:23:46 192.168.122.209 [69577.395488] [tdb] Close table 'client0.tdb' Apr 26 11:23:46 192.168.122.209 [69577.589846] [tdb] Close table 'sessions0.tdb' Apr 26 11:23:47 192.168.122.209 [69577.842235] [tdb] Close table 'filter0.tdb' Apr 26 11:23:47 192.168.122.209 [69577.842660] [tempesta fw] modules are stopped Apr 26 11:23:47 192.168.122.209 [69578.096426] [tempesta fw] exiting... Apr 26 11:23:47 192.168.122.209 [69578.212124] [tdb] Shutdown Tempesta DB Apr 26 11:23:47 192.168.122.209 [69578.572859] End test: tls.test_tls_cert.TlsSniWithHttpTable.test_valid Apr 26 11:23:47 192.168.122.209 [69578.608245] Start test: tls.test_tls_cert.TlsCertSelectBySanwitMultipleSections.test Apr 26 11:23:49 192.168.122.209 [69580.338716] [tdb] Start Tempesta DB Apr 26 11:23:49 192.168.122.209 [69580.462143] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:23:50 192.168.122.209 [69581.270534] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [69581.270534] Maybe that's fine, but it's worth checking the [69581.270534] config - if there is no relations between the [69581.270534] names, then host name confusion attack is possible. Apr 26 11:23:50 192.168.122.209 [69581.306523] [tempesta fw] Warning: Vhost private.example.com doesn't have certificate with matching SAN/CN. [69581.306523] Maybe that's fine, but it's worth checking the [69581.306523] config - if there is no relations between the [69581.306523] names, then host name confusion attack is possible. Apr 26 11:23:50 192.168.122.209 [69581.368453] [tempesta fw] Configuration processing is completed. Apr 26 11:23:50 192.168.122.209 [69581.420602] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:23:50 192.168.122.209 [69581.449345] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:23:50 192.168.122.209 [69581.477679] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:23:50 192.168.122.209 [69581.516396] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:23:50 192.168.122.209 [69581.560315] [tempesta fw] Tempesta FW is ready Apr 26 11:23:51 192.168.122.209 [69581.831666] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 192.168.122.196 ('private.example.com' vs 'default') Apr 26 11:23:51 192.168.122.209 [69581.835249] [tempesta fw] Warning: parsed request has been filtered out: 192.168.122.196 Apr 26 11:23:51 192.168.122.209 [69581.956419] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 192.168.122.196 ('private.example.com' vs 'default') Apr 26 11:23:51 192.168.122.209 [69581.959911] [tempesta fw] Warning: parsed request has been filtered out: 192.168.122.196 Apr 26 11:23:51 192.168.122.209 [69582.068703] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 192.168.122.196 ('example.com' vs 'default') Apr 26 11:23:51 192.168.122.209 [69582.072035] [tempesta fw] Warning: parsed request has been filtered out: 192.168.122.196 Apr 26 11:23:52 192.168.122.209 [69582.687111] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 11:23:52 192.168.122.209 [69582.770395] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [69582.770395] Maybe that's fine, but it's worth checking the [69582.770395] config - if there is no relations between the [69582.770395] names, then host name confusion attack is possible. Apr 26 11:23:52 192.168.122.209 [69582.832518] [tempesta fw] Configuration processing is completed. Apr 26 11:23:52 192.168.122.209 [69583.004447] [tempesta fw] Tempesta FW is ready Apr 26 11:23:52 192.168.122.209 [69583.124676] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 192.168.122.196 ('example.com' vs 'default') Apr 26 11:23:52 192.168.122.209 [69583.128027] [tempesta fw] Warning: parsed request has been filtered out: 192.168.122.196 Apr 26 11:23:52 192.168.122.209 [69583.245220] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 192.168.122.196 ('example.com' vs 'default') Apr 26 11:23:52 192.168.122.209 [69583.248607] [tempesta fw] Warning: parsed request has been filtered out: 192.168.122.196 Apr 26 11:23:52 192.168.122.209 [69583.352988] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 192.168.122.196 ('example.com' vs 'default') Apr 26 11:23:52 192.168.122.209 [69583.356385] [tempesta fw] Warning: parsed request has been filtered out: 192.168.122.196 Apr 26 11:23:53 192.168.122.209 [69583.910639] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 11:23:53 192.168.122.209 [69583.982462] [tempesta fw] Warning: Vhost private.example.com doesn't have certificate with matching SAN/CN. [69583.982462] Maybe that's fine, but it's worth checking the [69583.982462] config - if there is no relations between the [69583.982462] names, then host name confusion attack is possible. Apr 26 11:23:53 192.168.122.209 [69584.040443] [tempesta fw] Configuration processing is completed. Apr 26 11:23:53 192.168.122.209 [69584.188475] [tempesta fw] Tempesta FW is ready Apr 26 11:23:53 192.168.122.209 [69584.313213] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 192.168.122.196 ('private.example.com' vs 'default') Apr 26 11:23:53 192.168.122.209 [69584.316791] [tempesta fw] Warning: parsed request has been filtered out: 192.168.122.196 Apr 26 11:23:53 192.168.122.209 [69584.437569] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 192.168.122.196 ('private.example.com' vs 'default') Apr 26 11:23:53 192.168.122.209 [69584.439417] [tempesta fw] Warning: parsed request has been filtered out: 192.168.122.196 Apr 26 11:23:53 192.168.122.209 [69584.521592] [tempesta fw] Warning: client 192.168.122.196 requested unknown server name 'public.example.com' in TLS SNI, reject connection. Apr 26 11:23:54 192.168.122.209 [69585.107311] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 11:23:54 192.168.122.209 [69585.182398] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [69585.182398] Maybe that's fine, but it's worth checking the [69585.182398] config - if there is no relations between the [69585.182398] names, then host name confusion attack is possible. Apr 26 11:23:54 192.168.122.209 [69585.214376] [tempesta fw] Warning: Vhost private.example.com doesn't have certificate with matching SAN/CN. [69585.214376] Maybe that's fine, but it's worth checking the [69585.214376] config - if there is no relations between the [69585.214376] names, then host name confusion attack is possible. Apr 26 11:23:54 192.168.122.209 [69585.272626] [tempesta fw] Configuration processing is completed. Apr 26 11:23:54 192.168.122.209 [69585.448498] [tempesta fw] Tempesta FW is ready Apr 26 11:23:54 192.168.122.209 [69585.574625] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 192.168.122.196 ('private.example.com' vs 'default') Apr 26 11:23:54 192.168.122.209 [69585.578162] [tempesta fw] Warning: parsed request has been filtered out: 192.168.122.196 Apr 26 11:23:55 192.168.122.209 [69585.689516] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 192.168.122.196 ('private.example.com' vs 'default') Apr 26 11:23:55 192.168.122.209 [69585.692122] [tempesta fw] Warning: parsed request has been filtered out: 192.168.122.196 Apr 26 11:23:55 192.168.122.209 [69585.811193] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 192.168.122.196 ('example.com' vs 'default') Apr 26 11:23:55 192.168.122.209 [69585.814554] [tempesta fw] Warning: parsed request has been filtered out: 192.168.122.196 Apr 26 11:23:55 192.168.122.209 [69586.298035] [tdb] Close table 'client0.tdb' Apr 26 11:23:55 192.168.122.209 [69586.498672] [tdb] Close table 'sessions0.tdb' Apr 26 11:23:56 192.168.122.209 [69586.731735] [tdb] Close table 'filter0.tdb' Apr 26 11:23:56 192.168.122.209 [69586.732178] [tempesta fw] modules are stopped Apr 26 11:23:56 192.168.122.209 [69586.952796] [tempesta fw] exiting... Apr 26 11:23:56 192.168.122.209 [69587.087693] [tdb] Shutdown Tempesta DB Apr 26 11:23:56 192.168.122.209 [69587.514489] End test: tls.test_tls_cert.TlsCertSelectBySanwitMultipleSections.test Apr 26 11:23:56 192.168.122.209 [69587.595313] Start test: tls.test_tls_cert.TlsCertSelectBySan.test_various_san_and_sni_not_matched Apr 26 11:23:58 192.168.122.209 [69588.999954] [tdb] Start Tempesta DB Apr 26 11:23:58 192.168.122.209 [69589.128321] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:23:59 192.168.122.209 [69589.722424] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [69589.722424] Maybe that's fine, but it's worth checking the [69589.722424] config - if there is no relations between the [69589.722424] names, then host name confusion attack is possible. Apr 26 11:23:59 192.168.122.209 [69589.776460] [tempesta fw] Configuration processing is completed. Apr 26 11:23:59 192.168.122.209 [69589.832790] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:23:59 192.168.122.209 [69589.859978] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:23:59 192.168.122.209 [69589.888945] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:23:59 192.168.122.209 [69589.936469] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:23:59 192.168.122.209 [69589.976458] [tempesta fw] Tempesta FW is ready Apr 26 11:24:00 192.168.122.209 [69590.804302] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 11:24:00 192.168.122.209 [69590.874096] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [69590.874096] Maybe that's fine, but it's worth checking the [69590.874096] config - if there is no relations between the [69590.874096] names, then host name confusion attack is possible. Apr 26 11:24:00 192.168.122.209 [69590.924858] [tempesta fw] Configuration processing is completed. Apr 26 11:24:00 192.168.122.209 [69591.052558] [tempesta fw] Tempesta FW is ready Apr 26 11:24:00 192.168.122.209 [69591.165550] [tempesta fw] Warning: client 192.168.122.196 requested unknown server name 'a.b.example.com' in TLS SNI, reject connection. Apr 26 11:24:01 192.168.122.209 [69591.977136] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 11:24:01 192.168.122.209 [69592.046514] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [69592.046514] Maybe that's fine, but it's worth checking the [69592.046514] config - if there is no relations between the [69592.046514] names, then host name confusion attack is possible. Apr 26 11:24:01 192.168.122.209 [69592.100542] [tempesta fw] Configuration processing is completed. Apr 26 11:24:01 192.168.122.209 [69592.228586] [tempesta fw] Tempesta FW is ready Apr 26 11:24:01 192.168.122.209 [69592.337684] [tempesta fw] Warning: client 192.168.122.196 requested unknown server name 'www.example.com' in TLS SNI, reject connection. Apr 26 11:24:02 192.168.122.209 [69593.144409] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 11:24:02 192.168.122.209 [69593.205949] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [69593.205949] Maybe that's fine, but it's worth checking the [69593.205949] config - if there is no relations between the [69593.205949] names, then host name confusion attack is possible. Apr 26 11:24:02 192.168.122.209 [69593.244933] [tempesta fw] Configuration processing is completed. Apr 26 11:24:02 192.168.122.209 [69593.372571] [tempesta fw] Tempesta FW is ready Apr 26 11:24:02 192.168.122.209 [69593.489746] [tempesta fw] Warning: client 192.168.122.196 requested unknown server name 'b.example.com' in TLS SNI, reject connection. Apr 26 11:24:03 192.168.122.209 [69594.024820] [tdb] Close table 'client0.tdb' Apr 26 11:24:03 192.168.122.209 [69594.233691] [tdb] Close table 'sessions0.tdb' Apr 26 11:24:03 192.168.122.209 [69594.489342] [tdb] Close table 'filter0.tdb' Apr 26 11:24:03 192.168.122.209 [69594.489795] [tempesta fw] modules are stopped Apr 26 11:24:04 192.168.122.209 [69594.701729] [tempesta fw] exiting... Apr 26 11:24:04 192.168.122.209 [69594.833980] [tdb] Shutdown Tempesta DB Apr 26 11:24:04 192.168.122.209 [69595.164146] End test: tls.test_tls_cert.TlsCertSelectBySan.test_various_san_and_sni_not_matched Apr 26 11:24:04 192.168.122.209 [69595.198598] Start test: tls.test_tls_cert.TlsCertSelectBySan.test_various_san_and_sni_matched Apr 26 11:24:06 192.168.122.209 [69596.689112] [tdb] Start Tempesta DB Apr 26 11:24:06 192.168.122.209 [69596.828132] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:24:06 192.168.122.209 [69597.450578] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [69597.450578] Maybe that's fine, but it's worth checking the [69597.450578] config - if there is no relations between the [69597.450578] names, then host name confusion attack is possible. Apr 26 11:24:06 192.168.122.209 [69597.508768] [tempesta fw] Configuration processing is completed. Apr 26 11:24:06 192.168.122.209 [69597.568523] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:24:06 192.168.122.209 [69597.598602] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:24:06 192.168.122.209 [69597.630069] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:24:07 192.168.122.209 [69597.688602] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:24:07 192.168.122.209 [69597.728566] [tempesta fw] Tempesta FW is ready Apr 26 11:24:07 192.168.122.209 [69598.639409] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 11:24:08 192.168.122.209 [69598.701682] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [69598.701682] Maybe that's fine, but it's worth checking the [69598.701682] config - if there is no relations between the [69598.701682] names, then host name confusion attack is possible. Apr 26 11:24:08 192.168.122.209 [69598.740927] [tempesta fw] Configuration processing is completed. Apr 26 11:24:08 192.168.122.209 [69598.864654] [tempesta fw] Tempesta FW is ready Apr 26 11:24:08 192.168.122.209 [69599.003007] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 192.168.122.196 ('example.com' vs 'default') Apr 26 11:24:08 192.168.122.209 [69599.006384] [tempesta fw] Warning: parsed request has been filtered out: 192.168.122.196 Apr 26 11:24:09 192.168.122.209 [69599.739840] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 11:24:09 192.168.122.209 [69599.818555] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [69599.818555] Maybe that's fine, but it's worth checking the [69599.818555] config - if there is no relations between the [69599.818555] names, then host name confusion attack is possible. Apr 26 11:24:09 192.168.122.209 [69599.880678] [tempesta fw] Configuration processing is completed. Apr 26 11:24:09 192.168.122.209 [69600.000673] [tempesta fw] Tempesta FW is ready Apr 26 11:24:09 192.168.122.209 [69600.130023] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 192.168.122.196 ('example.com' vs 'default') Apr 26 11:24:09 192.168.122.209 [69600.133388] [tempesta fw] Warning: parsed request has been filtered out: 192.168.122.196 Apr 26 11:24:10 192.168.122.209 [69600.896528] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 11:24:10 192.168.122.209 [69600.974798] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [69600.974798] Maybe that's fine, but it's worth checking the [69600.974798] config - if there is no relations between the [69600.974798] names, then host name confusion attack is possible. Apr 26 11:24:10 192.168.122.209 [69601.036719] [tempesta fw] Configuration processing is completed. Apr 26 11:24:10 192.168.122.209 [69601.164726] [tempesta fw] Tempesta FW is ready Apr 26 11:24:10 192.168.122.209 [69601.308333] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 192.168.122.196 ('example.com' vs 'default') Apr 26 11:24:10 192.168.122.209 [69601.311680] [tempesta fw] Warning: parsed request has been filtered out: 192.168.122.196 Apr 26 11:24:11 192.168.122.209 [69602.072633] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 11:24:11 192.168.122.209 [69602.134756] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [69602.134756] Maybe that's fine, but it's worth checking the [69602.134756] config - if there is no relations between the [69602.134756] names, then host name confusion attack is possible. Apr 26 11:24:11 192.168.122.209 [69602.188641] [tempesta fw] Configuration processing is completed. Apr 26 11:24:11 192.168.122.209 [69602.324703] [tempesta fw] Tempesta FW is ready Apr 26 11:24:11 192.168.122.209 [69602.459646] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 192.168.122.196 ('example.com' vs 'default') Apr 26 11:24:11 192.168.122.209 [69602.463056] [tempesta fw] Warning: parsed request has been filtered out: 192.168.122.196 Apr 26 11:24:12 192.168.122.209 [69603.250010] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 11:24:12 192.168.122.209 [69603.346691] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [69603.346691] Maybe that's fine, but it's worth checking the [69603.346691] config - if there is no relations between the [69603.346691] names, then host name confusion attack is possible. Apr 26 11:24:12 192.168.122.209 [69603.408749] [tempesta fw] Configuration processing is completed. Apr 26 11:24:12 192.168.122.209 [69603.616707] [tempesta fw] Tempesta FW is ready Apr 26 11:24:13 192.168.122.209 [69603.748311] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 192.168.122.196 ('example.com' vs 'default') Apr 26 11:24:13 192.168.122.209 [69603.751633] [tempesta fw] Warning: parsed request has been filtered out: 192.168.122.196 Apr 26 11:24:13 192.168.122.209 [69604.530243] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 11:24:13 192.168.122.209 [69604.606615] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [69604.606615] Maybe that's fine, but it's worth checking the [69604.606615] config - if there is no relations between the [69604.606615] names, then host name confusion attack is possible. Apr 26 11:24:13 192.168.122.209 [69604.656775] [tempesta fw] Configuration processing is completed. Apr 26 11:24:14 192.168.122.209 [69604.796719] [tempesta fw] Tempesta FW is ready Apr 26 11:24:14 192.168.122.209 [69604.934760] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 192.168.122.196 ('example.com' vs 'default') Apr 26 11:24:14 192.168.122.209 [69604.938152] [tempesta fw] Warning: parsed request has been filtered out: 192.168.122.196 Apr 26 11:24:15 192.168.122.209 [69605.721451] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 11:24:15 192.168.122.209 [69605.794084] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [69605.794084] Maybe that's fine, but it's worth checking the [69605.794084] config - if there is no relations between the [69605.794084] names, then host name confusion attack is possible. Apr 26 11:24:15 192.168.122.209 [69605.860789] [tempesta fw] Configuration processing is completed. Apr 26 11:24:15 192.168.122.209 [69605.980750] [tempesta fw] Tempesta FW is ready Apr 26 11:24:15 192.168.122.209 [69606.144023] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 192.168.122.196 ('example.com' vs 'default') Apr 26 11:24:15 192.168.122.209 [69606.147389] [tempesta fw] Warning: parsed request has been filtered out: 192.168.122.196 Apr 26 11:24:15 192.168.122.209 [69606.675792] [tdb] Close table 'client0.tdb' Apr 26 11:24:16 192.168.122.209 [69606.867892] [tdb] Close table 'sessions0.tdb' Apr 26 11:24:16 192.168.122.209 [69607.107380] [tdb] Close table 'filter0.tdb' Apr 26 11:24:16 192.168.122.209 [69607.107827] [tempesta fw] modules are stopped Apr 26 11:24:16 192.168.122.209 [69607.328978] [tempesta fw] exiting... Apr 26 11:24:16 192.168.122.209 [69607.464687] [tdb] Shutdown Tempesta DB Apr 26 11:24:17 192.168.122.209 [69607.850828] End test: tls.test_tls_cert.TlsCertSelectBySan.test_various_san_and_sni_matched Apr 26 11:24:17 192.168.122.209 [69607.878036] Start test: tls.test_tls_cert.TlsCertSelectBySan.test_unknown_server_name_warning Apr 26 11:24:18 192.168.122.209 [69609.482090] [tdb] Start Tempesta DB Apr 26 11:24:18 192.168.122.209 [69609.620812] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:24:19 192.168.122.209 [69610.206815] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [69610.206815] Maybe that's fine, but it's worth checking the [69610.206815] config - if there is no relations between the [69610.206815] names, then host name confusion attack is possible. Apr 26 11:24:19 192.168.122.209 [69610.256822] [tempesta fw] Configuration processing is completed. Apr 26 11:24:19 192.168.122.209 [69610.308444] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:24:19 192.168.122.209 [69610.337062] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:24:19 192.168.122.209 [69610.366815] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:24:19 192.168.122.209 [69610.420775] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:24:19 192.168.122.209 [69610.480725] [tempesta fw] Tempesta FW is ready Apr 26 11:24:20 192.168.122.209 [69610.845986] [tempesta fw] Warning: client 192.168.122.196 requested unknown server name 'localhost' in TLS SNI, reject connection. Apr 26 11:24:20 192.168.122.209 [69611.169937] [tempesta fw] Warning: client 192.168.122.196 requested unknown server name 'a.localhost' in TLS SNI, reject connection. Apr 26 11:24:20 192.168.122.209 [69611.505173] [tempesta fw] Warning: client 192.168.122.196 requested unknown server name 'a.b.localhost' in TLS SNI, reject connection. Apr 26 11:24:21 192.168.122.209 [69611.816939] [tempesta fw] Warning: client 192.168.122.196 requested unknown server name 'a.b.c.localhost' in TLS SNI, reject connection. Apr 26 11:24:21 192.168.122.209 [69612.140853] [tempesta fw] Warning: client 192.168.122.196 requested unknown server name 'a.b.c.localhost.com' in TLS SNI, reject connection. Apr 26 11:24:21 192.168.122.209 [69612.461384] [tempesta fw] Warning: client 192.168.122.196 requested unknown server name 'a.b.c.example.com' in TLS SNI, reject connection. Apr 26 11:24:22 192.168.122.209 [69612.789433] [tempesta fw] Warning: client 192.168.122.196 requested unknown server name '' in TLS SNI, reject connection. Apr 26 11:24:22 192.168.122.209 [69613.117023] [tempesta fw] Warning: client 192.168.122.196 requested unknown server name ' [69613.117023] [69613.117023] [69613.117023] ' in TLS SNI, reject connection. Apr 26 11:24:23 192.168.122.209 [69613.804213] [tdb] Close table 'client0.tdb' Apr 26 11:24:23 192.168.122.209 [69613.991971] [tdb] Close table 'sessions0.tdb' Apr 26 11:24:23 192.168.122.209 [69614.226556] [tdb] Close table 'filter0.tdb' Apr 26 11:24:23 192.168.122.209 [69614.226984] [tempesta fw] modules are stopped Apr 26 11:24:23 192.168.122.209 [69614.457446] [tempesta fw] exiting... Apr 26 11:24:23 192.168.122.209 [69614.587554] [tdb] Shutdown Tempesta DB Apr 26 11:24:24 192.168.122.209 [69614.979607] End test: tls.test_tls_cert.TlsCertSelectBySan.test_unknown_server_name_warning Apr 26 11:24:24 192.168.122.209 [69615.013845] Start test: tls.test_tls_cert.TlsCertSelectBySan.test_sni_not_matched Apr 26 11:24:25 192.168.122.209 [69616.567342] [tdb] Start Tempesta DB Apr 26 11:24:26 192.168.122.209 [69616.704876] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:24:26 192.168.122.209 [69617.354996] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [69617.354996] Maybe that's fine, but it's worth checking the [69617.354996] config - if there is no relations between the [69617.354996] names, then host name confusion attack is possible. Apr 26 11:24:26 192.168.122.209 [69617.408877] [tempesta fw] Configuration processing is completed. Apr 26 11:24:26 192.168.122.209 [69617.470902] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:24:26 192.168.122.209 [69617.500812] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:24:26 192.168.122.209 [69617.529370] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:24:26 192.168.122.209 [69617.564854] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:24:26 192.168.122.209 [69617.604803] [tempesta fw] Tempesta FW is ready Apr 26 11:24:27 192.168.122.209 [69617.800916] [tempesta fw] Warning: client 192.168.122.196 requested unknown server name 'b.a.example.com' in TLS SNI, reject connection. Apr 26 11:24:27 192.168.122.209 [69617.892962] [tempesta fw] Warning: client 192.168.122.196 requested unknown server name '..example.com' in TLS SNI, reject connection. Apr 26 11:24:27 192.168.122.209 [69617.984844] [tempesta fw] Warning: client 192.168.122.196 requested unknown server name '.a.example.com' in TLS SNI, reject connection. Apr 26 11:24:27 192.168.122.209 [69618.073452] [tempesta fw] Warning: client 192.168.122.196 requested unknown server name 'www.www.example.com' in TLS SNI, reject connection. Apr 26 11:24:27 192.168.122.209 [69618.173583] [tempesta fw] Warning: client 192.168.122.196 requested unknown server name 'example.com.www' in TLS SNI, reject connection. Apr 26 11:24:27 192.168.122.209 [69618.265372] [tempesta fw] Warning: client 192.168.122.196 requested unknown server name 'example.com.' in TLS SNI, reject connection. Apr 26 11:24:27 192.168.122.209 [69618.360982] [tempesta fw] Warning: client 192.168.122.196 requested unknown server name 'a-example.com' in TLS SNI, reject connection. Apr 26 11:24:27 192.168.122.209 [69618.461454] [tempesta fw] Warning: client 192.168.122.196 requested unknown server name 'a.example.comm' in TLS SNI, reject connection. Apr 26 11:24:27 192.168.122.209 [69618.557216] [tempesta fw] Warning: client 192.168.122.196 requested unknown server name 'a.example.com-' in TLS SNI, reject connection. Apr 26 11:24:27 192.168.122.209 [69618.653719] [tempesta fw] Warning: client 192.168.122.196 requested unknown server name 'a.example.com.' in TLS SNI, reject connection. Apr 26 11:24:28 192.168.122.209 [69618.741104] [tempesta fw] Warning: client 192.168.122.196 requested unknown server name 'a.example.com.example.com' in TLS SNI, reject connection. Apr 26 11:24:28 192.168.122.209 [69618.829185] [tempesta fw] Warning: client 192.168.122.196 requested unknown server name '192.168.122.196' in TLS SNI, reject connection. Apr 26 11:24:28 192.168.122.209 [69618.929670] [tempesta fw] Warning: client 192.168.122.196 requested unknown server name 'aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa' in TLS SNI, reject connection. Apr 26 11:24:28 192.168.122.209 [69619.431265] [tdb] Close table 'client0.tdb' Apr 26 11:24:28 192.168.122.209 [69619.616458] [tdb] Close table 'sessions0.tdb' Apr 26 11:24:29 192.168.122.209 [69619.866669] [tdb] Close table 'filter0.tdb' Apr 26 11:24:29 192.168.122.209 [69619.867104] [tempesta fw] modules are stopped Apr 26 11:24:29 192.168.122.209 [69620.067894] [tempesta fw] exiting... Apr 26 11:24:29 192.168.122.209 [69620.206540] [tdb] Shutdown Tempesta DB Apr 26 11:24:29 192.168.122.209 [69620.588089] End test: tls.test_tls_cert.TlsCertSelectBySan.test_sni_not_matched Apr 26 11:24:29 192.168.122.209 [69620.621072] Start test: tls.test_tls_cert.TlsCertSelectBySan.test_sni_matched Apr 26 11:24:31 192.168.122.209 [69622.171770] [tdb] Start Tempesta DB Apr 26 11:24:31 192.168.122.209 [69622.307497] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:24:32 192.168.122.209 [69622.931011] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [69622.931011] Maybe that's fine, but it's worth checking the [69622.931011] config - if there is no relations between the [69622.931011] names, then host name confusion attack is possible. Apr 26 11:24:32 192.168.122.209 [69622.980991] [tempesta fw] Configuration processing is completed. Apr 26 11:24:32 192.168.122.209 [69623.030871] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:24:32 192.168.122.209 [69623.058607] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:24:32 192.168.122.209 [69623.087406] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:24:32 192.168.122.209 [69623.140947] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:24:32 192.168.122.209 [69623.184880] [tempesta fw] Tempesta FW is ready Apr 26 11:24:32 192.168.122.209 [69623.401833] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 192.168.122.196 ('example.com' vs 'default') Apr 26 11:24:32 192.168.122.209 [69623.405211] [tempesta fw] Warning: parsed request has been filtered out: 192.168.122.196 Apr 26 11:24:32 192.168.122.209 [69623.546263] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 192.168.122.196 ('example.com' vs 'default') Apr 26 11:24:32 192.168.122.209 [69623.549648] [tempesta fw] Warning: parsed request has been filtered out: 192.168.122.196 Apr 26 11:24:32 192.168.122.209 [69623.665135] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 192.168.122.196 ('example.com' vs 'default') Apr 26 11:24:32 192.168.122.209 [69623.668480] [tempesta fw] Warning: parsed request has been filtered out: 192.168.122.196 Apr 26 11:24:33 192.168.122.209 [69623.814607] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 192.168.122.196 ('example.com' vs 'default') Apr 26 11:24:33 192.168.122.209 [69623.817983] [tempesta fw] Warning: parsed request has been filtered out: 192.168.122.196 Apr 26 11:24:33 192.168.122.209 [69623.950880] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 192.168.122.196 ('example.com' vs 'default') Apr 26 11:24:33 192.168.122.209 [69623.954275] [tempesta fw] Warning: parsed request has been filtered out: 192.168.122.196 Apr 26 11:24:33 192.168.122.209 [69624.088857] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 192.168.122.196 ('example.com' vs 'default') Apr 26 11:24:33 192.168.122.209 [69624.092204] [tempesta fw] Warning: parsed request has been filtered out: 192.168.122.196 Apr 26 11:24:33 192.168.122.209 [69624.212666] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 192.168.122.196 ('example.com' vs 'default') Apr 26 11:24:33 192.168.122.209 [69624.216018] [tempesta fw] Warning: parsed request has been filtered out: 192.168.122.196 Apr 26 11:24:33 192.168.122.209 [69624.345656] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 192.168.122.196 ('example.com' vs 'default') Apr 26 11:24:33 192.168.122.209 [69624.348943] [tempesta fw] Warning: parsed request has been filtered out: 192.168.122.196 Apr 26 11:24:33 192.168.122.209 [69624.478879] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 192.168.122.196 ('example.com' vs 'default') Apr 26 11:24:33 192.168.122.209 [69624.482228] [tempesta fw] Warning: parsed request has been filtered out: 192.168.122.196 Apr 26 11:24:33 192.168.122.209 [69624.598183] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 192.168.122.196 ('example.com' vs 'default') Apr 26 11:24:33 192.168.122.209 [69624.601575] [tempesta fw] Warning: parsed request has been filtered out: 192.168.122.196 Apr 26 11:24:34 192.168.122.209 [69625.097358] [tdb] Close table 'client0.tdb' Apr 26 11:24:34 192.168.122.209 [69625.284652] [tdb] Close table 'sessions0.tdb' Apr 26 11:24:34 192.168.122.209 [69625.492560] [tdb] Close table 'filter0.tdb' Apr 26 11:24:34 192.168.122.209 [69625.493001] [tempesta fw] modules are stopped Apr 26 11:24:35 192.168.122.209 [69625.721963] [tempesta fw] exiting... Apr 26 11:24:35 192.168.122.209 [69625.829741] [tdb] Shutdown Tempesta DB Apr 26 11:24:35 192.168.122.209 [69626.194796] End test: tls.test_tls_cert.TlsCertSelectBySan.test_sni_matched Apr 26 11:24:35 192.168.122.209 [69626.279709] Start test: tls.test_tls_cert.TlsCertSelectBySan.test_sni_match_after_reload Apr 26 11:24:37 192.168.122.209 [69627.803426] [tdb] Start Tempesta DB Apr 26 11:24:37 192.168.122.209 [69627.940262] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:24:37 192.168.122.209 [69628.570972] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [69628.570972] Maybe that's fine, but it's worth checking the [69628.570972] config - if there is no relations between the [69628.570972] names, then host name confusion attack is possible. Apr 26 11:24:37 192.168.122.209 [69628.621346] [tempesta fw] Configuration processing is completed. Apr 26 11:24:37 192.168.122.209 [69628.673309] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:24:38 192.168.122.209 [69628.700798] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:24:38 192.168.122.209 [69628.733197] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:24:38 192.168.122.209 [69628.781010] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:24:38 192.168.122.209 [69628.828982] [tempesta fw] Tempesta FW is ready Apr 26 11:24:39 192.168.122.209 [69629.786740] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 11:24:39 192.168.122.209 [69629.870974] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [69629.870974] Maybe that's fine, but it's worth checking the [69629.870974] config - if there is no relations between the [69629.870974] names, then host name confusion attack is possible. Apr 26 11:24:39 192.168.122.209 [69629.921098] [tempesta fw] Configuration processing is completed. Apr 26 11:24:39 192.168.122.209 [69630.069042] [tempesta fw] Tempesta FW is ready Apr 26 11:24:39 192.168.122.209 [69630.197561] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 192.168.122.196 ('example.com' vs 'default') Apr 26 11:24:39 192.168.122.209 [69630.200896] [tempesta fw] Warning: parsed request has been filtered out: 192.168.122.196 Apr 26 11:24:39 192.168.122.209 [69630.321126] [tempesta fw] Warning: client 192.168.122.196 requested unknown server name 'b.tempesta-tech.com' in TLS SNI, reject connection. Apr 26 11:24:40 192.168.122.209 [69631.141395] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 11:24:40 192.168.122.209 [69631.219266] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [69631.219266] Maybe that's fine, but it's worth checking the [69631.219266] config - if there is no relations between the [69631.219266] names, then host name confusion attack is possible. Apr 26 11:24:40 192.168.122.209 [69631.269081] [tempesta fw] Configuration processing is completed. Apr 26 11:24:40 192.168.122.209 [69631.405018] [tempesta fw] Tempesta FW is ready Apr 26 11:24:40 192.168.122.209 [69631.546962] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 192.168.122.196 ('example.com' vs 'default') Apr 26 11:24:40 192.168.122.209 [69631.550307] [tempesta fw] Warning: parsed request has been filtered out: 192.168.122.196 Apr 26 11:24:41 192.168.122.209 [69631.684940] [tempesta fw] Warning: client 192.168.122.196 requested unknown server name 'a.example.com' in TLS SNI, reject connection. Apr 26 11:24:41 192.168.122.209 [69632.474974] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 11:24:41 192.168.122.209 [69632.534978] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [69632.534978] Maybe that's fine, but it's worth checking the [69632.534978] config - if there is no relations between the [69632.534978] names, then host name confusion attack is possible. Apr 26 11:24:41 192.168.122.209 [69632.585143] [tempesta fw] Configuration processing is completed. Apr 26 11:24:42 192.168.122.209 [69632.705091] [tempesta fw] Tempesta FW is ready Apr 26 11:24:42 192.168.122.209 [69632.853880] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 192.168.122.196 ('example.com' vs 'default') Apr 26 11:24:42 192.168.122.209 [69632.857242] [tempesta fw] Warning: parsed request has been filtered out: 192.168.122.196 Apr 26 11:24:42 192.168.122.209 [69632.950126] [tempesta fw] Warning: client 192.168.122.196 requested unknown server name 'b.tempesta-tech.com' in TLS SNI, reject connection. Apr 26 11:24:43 192.168.122.209 [69633.712941] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 11:24:43 192.168.122.209 [69633.787126] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [69633.787126] Maybe that's fine, but it's worth checking the [69633.787126] config - if there is no relations between the [69633.787126] names, then host name confusion attack is possible. Apr 26 11:24:43 192.168.122.209 [69633.841116] [tempesta fw] Configuration processing is completed. Apr 26 11:24:43 192.168.122.209 [69633.961100] [tempesta fw] Tempesta FW is ready Apr 26 11:24:43 192.168.122.209 [69634.110479] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 192.168.122.196 ('example.com' vs 'default') Apr 26 11:24:43 192.168.122.209 [69634.113860] [tempesta fw] Warning: parsed request has been filtered out: 192.168.122.196 Apr 26 11:24:43 192.168.122.209 [69634.205400] [tempesta fw] Warning: client 192.168.122.196 requested unknown server name 'a.example.com' in TLS SNI, reject connection. Apr 26 11:24:44 192.168.122.209 [69635.037015] [tempesta fw] Live reconfiguration of Tempesta. Apr 26 11:24:44 192.168.122.209 [69635.099033] [tempesta fw] Warning: Vhost example.com doesn't have certificate with matching SAN/CN. [69635.099033] Maybe that's fine, but it's worth checking the [69635.099033] config - if there is no relations between the [69635.099033] names, then host name confusion attack is possible. Apr 26 11:24:44 192.168.122.209 [69635.145468] [tempesta fw] Configuration processing is completed. Apr 26 11:24:44 192.168.122.209 [69635.289106] [tempesta fw] Tempesta FW is ready Apr 26 11:24:44 192.168.122.209 [69635.410377] [tempesta fw] Warning: frang: vhost by SNI doesn't match vhost by authority for 192.168.122.196 ('example.com' vs 'default') Apr 26 11:24:44 192.168.122.209 [69635.413765] [tempesta fw] Warning: parsed request has been filtered out: 192.168.122.196 Apr 26 11:24:44 192.168.122.209 [69635.501804] [tempesta fw] Warning: client 192.168.122.196 requested unknown server name 'b.tempesta-tech.com' in TLS SNI, reject connection. Apr 26 11:24:45 192.168.122.209 [69635.977213] [tdb] Close table 'client0.tdb' Apr 26 11:24:45 192.168.122.209 [69636.183225] [tdb] Close table 'sessions0.tdb' Apr 26 11:24:45 192.168.122.209 [69636.416534] [tdb] Close table 'filter0.tdb' Apr 26 11:24:45 192.168.122.209 [69636.416978] [tempesta fw] modules are stopped Apr 26 11:24:45 192.168.122.209 [69636.637266] [tempesta fw] exiting... Apr 26 11:24:46 192.168.122.209 [69636.742724] [tdb] Shutdown Tempesta DB Apr 26 11:24:46 192.168.122.209 [69637.103191] End test: tls.test_tls_cert.TlsCertSelectBySan.test_sni_match_after_reload Apr 26 11:24:46 192.168.122.209 [69637.138064] Start test: tls.test_tls_cert.TlsCertSelect.test_vhost_cert_selection Apr 26 11:24:48 192.168.122.209 [69639.611600] [tdb] Start Tempesta DB Apr 26 11:24:49 192.168.122.209 [69639.755649] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:24:50 192.168.122.209 [69640.708341] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69640.708341] Maybe that's fine, but it's worth checking the [69640.708341] config - if there is no relations between the [69640.708341] names, then host name confusion attack is possible. Apr 26 11:24:50 192.168.122.209 [69640.797548] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [69640.797548] Maybe that's fine, but it's worth checking the [69640.797548] config - if there is no relations between the [69640.797548] names, then host name confusion attack is possible. Apr 26 11:24:50 192.168.122.209 [69640.810396] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [69640.810396] Maybe that's fine, but it's worth checking the [69640.810396] config - if there is no relations between the [69640.810396] names, then host name confusion attack is possible. Apr 26 11:24:50 192.168.122.209 [69640.877163] [tempesta fw] Configuration processing is completed. Apr 26 11:24:50 192.168.122.209 [69640.928592] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:24:50 192.168.122.209 [69640.957049] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:24:50 192.168.122.209 [69640.984874] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:24:50 192.168.122.209 [69641.025046] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:24:50 192.168.122.209 [69641.069097] [tempesta fw] Tempesta FW is ready Apr 26 11:24:50 192.168.122.209 [69641.426228] [tempesta fw] Warning: client 192.168.122.196 requested unknown server name 'example.com' in TLS SNI, reject connection. Apr 26 11:24:51 192.168.122.209 [69641.862867] [tdb] Close table 'client0.tdb' Apr 26 11:24:51 192.168.122.209 [69642.062949] [tdb] Close table 'sessions0.tdb' Apr 26 11:24:51 192.168.122.209 [69642.285023] [tdb] Close table 'filter0.tdb' Apr 26 11:24:51 192.168.122.209 [69642.285442] [tempesta fw] modules are stopped Apr 26 11:24:51 192.168.122.209 [69642.534909] [tempesta fw] exiting... Apr 26 11:24:51 192.168.122.209 [69642.664212] [tdb] Shutdown Tempesta DB Apr 26 11:24:52 192.168.122.209 [69643.073447] End test: tls.test_tls_cert.TlsCertSelect.test_vhost_cert_selection Apr 26 11:24:52 192.168.122.209 [69643.110842] Start test: tls.test_tls_cert.StaleCert.test Apr 26 11:24:53 192.168.122.209 [69644.595724] [tdb] Start Tempesta DB Apr 26 11:24:54 192.168.122.209 [69644.722289] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:24:54 192.168.122.209 [69645.238491] [tempesta fw] Warning: The certificate '/tmp/host/tempesta.crt' has expired! Please renew [69645.238491] the certificate to maintain functionality. Apr 26 11:24:54 192.168.122.209 [69645.238577] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69645.238577] Maybe that's fine, but it's worth checking the [69645.238577] config - if there is no relations between the [69645.238577] names, then host name confusion attack is possible. Apr 26 11:24:54 192.168.122.209 [69645.321277] [tempesta fw] Configuration processing is completed. Apr 26 11:24:54 192.168.122.209 [69645.383129] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:24:54 192.168.122.209 [69645.416110] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:24:54 192.168.122.209 [69645.446362] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:24:54 192.168.122.209 [69645.485222] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:24:54 192.168.122.209 [69645.525176] [tempesta fw] Tempesta FW is ready Apr 26 11:24:55 192.168.122.209 [69646.143763] [tdb] Close table 'client0.tdb' Apr 26 11:24:55 192.168.122.209 [69646.335222] [tdb] Close table 'sessions0.tdb' Apr 26 11:24:55 192.168.122.209 [69646.543334] [tdb] Close table 'filter0.tdb' Apr 26 11:24:55 192.168.122.209 [69646.543736] [tempesta fw] modules are stopped Apr 26 11:24:56 192.168.122.209 [69646.779909] [tempesta fw] exiting... Apr 26 11:24:56 192.168.122.209 [69646.879968] [tdb] Shutdown Tempesta DB Apr 26 11:24:56 192.168.122.209 [69647.283271] End test: tls.test_tls_cert.StaleCert.test Apr 26 11:24:56 192.168.122.209 [69647.312854] Start test: tls.test_tls_cert.RSA512_SHA256.test Apr 26 11:24:58 192.168.122.209 [69648.978420] [tdb] Start Tempesta DB Apr 26 11:24:58 192.168.122.209 [69649.104378] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:24:58 192.168.122.209 [69649.602458] [tempesta tls] Warning: Trying to load an RSA key smaller than 1024 bits. Please use stronger keys. Apr 26 11:24:58 192.168.122.209 [69649.605539] [tempesta fw] ERROR: tls_certificate: Invalid certificate specified, err=c Apr 26 11:24:58 192.168.122.209 [69649.607752] [tempesta fw] ERROR: configuration parsing error: [69649.607752] 4: tls_certificate /tmp/host/tempesta.crt; [69649.607752] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 11:24:58 192.168.122.209 [69649.612598] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 11:24:59 192.168.122.209 [69649.739556] [tempesta fw] exiting... Apr 26 11:24:59 192.168.122.209 [69649.861130] [tdb] Shutdown Tempesta DB Apr 26 11:25:00 192.168.122.209 [69650.702496] End test: tls.test_tls_cert.RSA512_SHA256.test Apr 26 11:25:00 192.168.122.209 [69650.732762] Start test: tls.test_tls_cert.RSA4096_SHA512.test Apr 26 11:25:02 192.168.122.209 [69653.332269] [tdb] Start Tempesta DB Apr 26 11:25:02 192.168.122.209 [69653.463437] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:25:03 192.168.122.209 [69653.793074] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69653.793074] Maybe that's fine, but it's worth checking the [69653.793074] config - if there is no relations between the [69653.793074] names, then host name confusion attack is possible. Apr 26 11:25:03 192.168.122.209 [69653.897790] [tempesta fw] Configuration processing is completed. Apr 26 11:25:03 192.168.122.209 [69653.952132] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:25:03 192.168.122.209 [69653.982062] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:25:03 192.168.122.209 [69654.010700] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:25:03 192.168.122.209 [69654.069340] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:25:03 192.168.122.209 [69654.113283] [tempesta fw] Tempesta FW is ready Apr 26 11:25:04 192.168.122.209 [69654.769533] [tdb] Close table 'client0.tdb' Apr 26 11:25:04 192.168.122.209 [69654.960374] [tdb] Close table 'sessions0.tdb' Apr 26 11:25:04 192.168.122.209 [69655.187509] [tdb] Close table 'filter0.tdb' Apr 26 11:25:04 192.168.122.209 [69655.187930] [tempesta fw] modules are stopped Apr 26 11:25:04 192.168.122.209 [69655.389542] [tempesta fw] exiting... Apr 26 11:25:04 192.168.122.209 [69655.525459] [tdb] Shutdown Tempesta DB Apr 26 11:25:05 192.168.122.209 [69655.958956] End test: tls.test_tls_cert.RSA4096_SHA512.test Apr 26 11:25:05 192.168.122.209 [69655.994902] Start test: tls.test_tls_cert.RSA2048_SHA512.test Apr 26 11:25:06 192.168.122.209 [69657.583682] [tdb] Start Tempesta DB Apr 26 11:25:07 192.168.122.209 [69657.720098] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:25:07 192.168.122.209 [69658.277478] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69658.277478] Maybe that's fine, but it's worth checking the [69658.277478] config - if there is no relations between the [69658.277478] names, then host name confusion attack is possible. Apr 26 11:25:07 192.168.122.209 [69658.373433] [tempesta fw] Configuration processing is completed. Apr 26 11:25:07 192.168.122.209 [69658.423741] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:25:07 192.168.122.209 [69658.451150] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:25:07 192.168.122.209 [69658.479022] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:25:07 192.168.122.209 [69658.521307] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:25:07 192.168.122.209 [69658.573342] [tempesta fw] Tempesta FW is ready Apr 26 11:25:08 192.168.122.209 [69659.245924] [tdb] Close table 'client0.tdb' Apr 26 11:25:08 192.168.122.209 [69659.434394] [tdb] Close table 'sessions0.tdb' Apr 26 11:25:09 192.168.122.209 [69659.684207] [tdb] Close table 'filter0.tdb' Apr 26 11:25:09 192.168.122.209 [69659.684637] [tempesta fw] modules are stopped Apr 26 11:25:09 192.168.122.209 [69659.869290] [tempesta fw] exiting... Apr 26 11:25:09 192.168.122.209 [69659.966970] [tdb] Shutdown Tempesta DB Apr 26 11:25:09 192.168.122.209 [69660.387526] End test: tls.test_tls_cert.RSA2048_SHA512.test Apr 26 11:25:09 192.168.122.209 [69660.428506] Start test: tls.test_tls_cert.RSA1024_SHA384.test Apr 26 11:25:11 192.168.122.209 [69661.902303] [tdb] Start Tempesta DB Apr 26 11:25:11 192.168.122.209 [69662.036007] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:25:11 192.168.122.209 [69662.556959] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69662.556959] Maybe that's fine, but it's worth checking the [69662.556959] config - if there is no relations between the [69662.556959] names, then host name confusion attack is possible. Apr 26 11:25:11 192.168.122.209 [69662.637478] [tempesta fw] Configuration processing is completed. Apr 26 11:25:12 192.168.122.209 [69662.694829] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:25:12 192.168.122.209 [69662.726681] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:25:12 192.168.122.209 [69662.762792] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:25:12 192.168.122.209 [69662.821437] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:25:12 192.168.122.209 [69662.865392] [tempesta fw] Tempesta FW is ready Apr 26 11:25:12 192.168.122.209 [69663.521827] [tdb] Close table 'client0.tdb' Apr 26 11:25:13 192.168.122.209 [69663.705247] [tdb] Close table 'sessions0.tdb' Apr 26 11:25:13 192.168.122.209 [69663.967534] [tdb] Close table 'filter0.tdb' Apr 26 11:25:13 192.168.122.209 [69663.967965] [tempesta fw] modules are stopped Apr 26 11:25:13 192.168.122.209 [69664.169941] [tempesta fw] exiting... Apr 26 11:25:13 192.168.122.209 [69664.266083] [tdb] Shutdown Tempesta DB Apr 26 11:25:14 192.168.122.209 [69664.700425] End test: tls.test_tls_cert.RSA1024_SHA384.test Apr 26 11:25:14 192.168.122.209 [69664.728781] Start test: tls.test_tls_cert.InvalidKeyWithGoodCert.test Apr 26 11:25:15 192.168.122.209 [69666.368977] [tdb] Start Tempesta DB Apr 26 11:25:15 192.168.122.209 [69666.503563] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:25:16 192.168.122.209 [69666.998891] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69666.998891] Maybe that's fine, but it's worth checking the [69666.998891] config - if there is no relations between the [69666.998891] names, then host name confusion attack is possible. Apr 26 11:25:16 192.168.122.209 [69667.034075] [tempesta tls] Warning: PK - Elliptic curve with OID 1.2.840.10045.3.1.1 is unsupported Apr 26 11:25:16 192.168.122.209 [69667.036617] [tempesta fw] ERROR: tls_certificate_key: Invalid private key specified (16) Apr 26 11:25:16 192.168.122.209 [69667.038883] [tempesta fw] ERROR: configuration parsing error: [69667.038883] 5: tls_certificate_key /tmp/host/tempesta.key; [69667.038883] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 11:25:16 192.168.122.209 [69667.043409] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 11:25:16 192.168.122.209 [69667.185969] [tempesta fw] exiting... Apr 26 11:25:16 192.168.122.209 [69667.318939] [tdb] Shutdown Tempesta DB Apr 26 11:25:17 192.168.122.209 [69668.062534] End test: tls.test_tls_cert.InvalidKeyWithGoodCert.test Apr 26 11:25:17 192.168.122.209 [69668.097350] Start test: tls.test_tls_cert.InvalidHash.test Apr 26 11:25:19 192.168.122.209 [69669.781478] [tdb] Start Tempesta DB Apr 26 11:25:19 192.168.122.209 [69669.907824] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:25:19 192.168.122.209 [69670.218026] [tempesta tls] Warning: X509 - Signature algorithm with OID 1.2.840.10045.4.1 is unsupported Apr 26 11:25:19 192.168.122.209 [69670.218041] [tempesta fw] ERROR: tls_certificate: Invalid certificate specified, err=2600 Apr 26 11:25:19 192.168.122.209 [69670.222999] [tempesta fw] ERROR: configuration parsing error: [69670.222999] 4: tls_certificate /tmp/host/tempesta.crt; [69670.222999] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 11:25:19 192.168.122.209 [69670.227912] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 11:25:19 192.168.122.209 [69670.379937] [tempesta fw] exiting... Apr 26 11:25:19 192.168.122.209 [69670.494569] [tdb] Shutdown Tempesta DB Apr 26 11:25:20 192.168.122.209 [69671.272166] End test: tls.test_tls_cert.InvalidHash.test Apr 26 11:25:20 192.168.122.209 [69671.357770] Start test: tls.test_tls_cert.ECDSA_SHA384_SECP521.test Apr 26 11:25:22 192.168.122.209 [69673.077122] [tdb] Start Tempesta DB Apr 26 11:25:22 192.168.122.209 [69673.216660] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:25:22 192.168.122.209 [69673.510876] [tempesta tls] Warning: PK - Elliptic curve with OID 1.3.132.0.35 is unsupported Apr 26 11:25:22 192.168.122.209 [69673.513589] [tempesta fw] ERROR: tls_certificate: Invalid certificate specified, err=16 Apr 26 11:25:22 192.168.122.209 [69673.515778] [tempesta fw] ERROR: configuration parsing error: [69673.515778] 4: tls_certificate /tmp/host/tempesta.crt; [69673.515778] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 11:25:22 192.168.122.209 [69673.520653] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 11:25:23 192.168.122.209 [69673.684301] [tempesta fw] exiting... Apr 26 11:25:23 192.168.122.209 [69673.797466] [tdb] Shutdown Tempesta DB Apr 26 11:25:23 192.168.122.209 [69674.568172] End test: tls.test_tls_cert.ECDSA_SHA384_SECP521.test Apr 26 11:25:23 192.168.122.209 [69674.596795] Start test: tls.test_tls_cert.ECDSA_SHA384_SECP256.test Apr 26 11:25:25 192.168.122.209 [69676.097627] [tdb] Start Tempesta DB Apr 26 11:25:25 192.168.122.209 [69676.211674] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:25:25 192.168.122.209 [69676.542883] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69676.542883] Maybe that's fine, but it's worth checking the [69676.542883] config - if there is no relations between the [69676.542883] names, then host name confusion attack is possible. Apr 26 11:25:25 192.168.122.209 [69676.645648] [tempesta fw] Configuration processing is completed. Apr 26 11:25:26 192.168.122.209 [69676.696288] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:25:26 192.168.122.209 [69676.723585] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:25:26 192.168.122.209 [69676.751136] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:25:26 192.168.122.209 [69676.801625] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:25:26 192.168.122.209 [69676.841573] [tempesta fw] Tempesta FW is ready Apr 26 11:25:26 192.168.122.209 [69677.471821] [tdb] Close table 'client0.tdb' Apr 26 11:25:26 192.168.122.209 [69677.664606] [tdb] Close table 'sessions0.tdb' Apr 26 11:25:27 192.168.122.209 [69677.896730] [tdb] Close table 'filter0.tdb' Apr 26 11:25:27 192.168.122.209 [69677.897126] [tempesta fw] modules are stopped Apr 26 11:25:27 192.168.122.209 [69678.079088] [tempesta fw] exiting... Apr 26 11:25:27 192.168.122.209 [69678.208056] [tdb] Shutdown Tempesta DB Apr 26 11:25:27 192.168.122.209 [69678.595960] End test: tls.test_tls_cert.ECDSA_SHA384_SECP256.test Apr 26 11:25:27 192.168.122.209 [69678.623482] Start test: tls.test_tls_cert.ECDSA_SHA256_SECP256.test Apr 26 11:25:29 192.168.122.209 [69680.192634] [tdb] Start Tempesta DB Apr 26 11:25:29 192.168.122.209 [69680.330269] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:25:30 192.168.122.209 [69680.810965] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69680.810965] Maybe that's fine, but it's worth checking the [69680.810965] config - if there is no relations between the [69680.810965] names, then host name confusion attack is possible. Apr 26 11:25:30 192.168.122.209 [69680.901727] [tempesta fw] Configuration processing is completed. Apr 26 11:25:30 192.168.122.209 [69680.959012] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:25:30 192.168.122.209 [69680.991369] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:25:30 192.168.122.209 [69681.022453] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:25:30 192.168.122.209 [69681.069698] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:25:30 192.168.122.209 [69681.125653] [tempesta fw] Tempesta FW is ready Apr 26 11:25:31 192.168.122.209 [69681.786936] [tdb] Close table 'client0.tdb' Apr 26 11:25:31 192.168.122.209 [69681.977165] [tdb] Close table 'sessions0.tdb' Apr 26 11:25:31 192.168.122.209 [69682.244173] [tdb] Close table 'filter0.tdb' Apr 26 11:25:31 192.168.122.209 [69682.244573] [tempesta fw] modules are stopped Apr 26 11:25:31 192.168.122.209 [69682.422809] [tempesta fw] exiting... Apr 26 11:25:31 192.168.122.209 [69682.549129] [tdb] Shutdown Tempesta DB Apr 26 11:25:32 192.168.122.209 [69682.917270] End test: tls.test_tls_cert.ECDSA_SHA256_SECP256.test Apr 26 11:25:32 192.168.122.209 [69682.948345] Start test: tls.test_tls_cert.ECDSA_SHA256_SECP192.test Apr 26 11:25:33 192.168.122.209 [69684.659116] [tdb] Start Tempesta DB Apr 26 11:25:34 192.168.122.209 [69684.793670] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:25:34 192.168.122.209 [69685.267013] [tempesta tls] Warning: PK - Elliptic curve with OID 1.2.840.10045.3.1.1 is unsupported Apr 26 11:25:34 192.168.122.209 [69685.269876] [tempesta fw] ERROR: tls_certificate: Invalid certificate specified, err=16 Apr 26 11:25:34 192.168.122.209 [69685.272066] [tempesta fw] ERROR: configuration parsing error: [69685.272066] 4: tls_certificate /tmp/host/tempesta.crt; [69685.272066] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 11:25:34 192.168.122.209 [69685.276982] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 11:25:34 192.168.122.209 [69685.434122] [tempesta fw] exiting... Apr 26 11:25:34 192.168.122.209 [69685.550282] [tdb] Shutdown Tempesta DB Apr 26 11:25:35 192.168.122.209 [69686.415788] End test: tls.test_tls_cert.ECDSA_SHA256_SECP192.test Apr 26 11:25:35 192.168.122.209 [69686.450489] Start test: tls.test_tls_cert.BaseTlsSniWithHttpTable.test_with_san Apr 26 11:25:35 192.168.122.209 [69686.481405] End test: tls.test_tls_cert.BaseTlsSniWithHttpTable.test_with_san Apr 26 11:25:35 192.168.122.209 [69686.564732] Start test: tls.test_tls_cert.BaseTlsSniWithHttpTable.test_with_common_name Apr 26 11:25:35 192.168.122.209 [69686.593303] End test: tls.test_tls_cert.BaseTlsSniWithHttpTable.test_with_common_name Apr 26 11:25:35 192.168.122.209 [69686.624762] Start test: tls.test_tls_cert.BaseTlsSniWithHttpTable.test_with_any_host Apr 26 11:25:35 192.168.122.209 [69686.660596] End test: tls.test_tls_cert.BaseTlsSniWithHttpTable.test_with_any_host Apr 26 11:25:36 192.168.122.209 [69686.742983] Start test: tls.test_tls_cert.BaseTlsSniWithHttpTable.test_valid Apr 26 11:25:36 192.168.122.209 [69686.772111] End test: tls.test_tls_cert.BaseTlsSniWithHttpTable.test_valid Apr 26 11:25:36 192.168.122.209 [69686.810390] Start test: tls.test_tls_basic.TlsBasic.test_connection_close Apr 26 11:25:37 192.168.122.209 [69688.362034] [tdb] Start Tempesta DB Apr 26 11:25:37 192.168.122.209 [69688.498378] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:25:38 192.168.122.209 [69688.779060] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69688.779060] Maybe that's fine, but it's worth checking the [69688.779060] config - if there is no relations between the [69688.779060] names, then host name confusion attack is possible. Apr 26 11:25:38 192.168.122.209 [69688.873818] [tempesta fw] Configuration processing is completed. Apr 26 11:25:38 192.168.122.209 [69688.925115] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:25:38 192.168.122.209 [69688.952826] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:25:38 192.168.122.209 [69688.980243] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:25:38 192.168.122.209 [69689.033802] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:25:38 192.168.122.209 [69689.093711] [tempesta fw] Tempesta FW is ready Apr 26 11:25:39 192.168.122.209 [69689.739681] [tdb] Close table 'client0.tdb' Apr 26 11:25:39 192.168.122.209 [69689.924360] [tdb] Close table 'sessions0.tdb' Apr 26 11:25:39 192.168.122.209 [69690.156170] [tdb] Close table 'filter0.tdb' Apr 26 11:25:39 192.168.122.209 [69690.156597] [tempesta fw] modules are stopped Apr 26 11:25:39 192.168.122.209 [69690.365741] [tempesta fw] exiting... Apr 26 11:25:39 192.168.122.209 [69690.488054] [tdb] Shutdown Tempesta DB Apr 26 11:25:40 192.168.122.209 [69690.898368] End test: tls.test_tls_basic.TlsBasic.test_connection_close Apr 26 11:25:40 192.168.122.209 [69690.937869] Start test: tls.test_tls_basic.TlsBasic.test_bad_request Apr 26 11:25:41 192.168.122.209 [69692.414523] [tdb] Start Tempesta DB Apr 26 11:25:41 192.168.122.209 [69692.556937] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:25:42 192.168.122.209 [69693.023158] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69693.023158] Maybe that's fine, but it's worth checking the [69693.023158] config - if there is no relations between the [69693.023158] names, then host name confusion attack is possible. Apr 26 11:25:42 192.168.122.209 [69693.125892] [tempesta fw] Configuration processing is completed. Apr 26 11:25:42 192.168.122.209 [69693.187710] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:25:42 192.168.122.209 [69693.224716] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:25:42 192.168.122.209 [69693.255228] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:25:42 192.168.122.209 [69693.301850] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:25:42 192.168.122.209 [69693.341821] [tempesta fw] Tempesta FW is ready Apr 26 11:25:42 192.168.122.209 [69693.495312] [tempesta fw] Warning: Parser error: state=Req_HttpVer input(-6)=0x48('GET / HTxTP/1.1 [69693.495312] Host: localhost [69693.495312] [69693.495312] ') data_len=33 off=6 Apr 26 11:25:43 192.168.122.209 [69693.969604] [tdb] Close table 'client0.tdb' Apr 26 11:25:43 192.168.122.209 [69694.170891] [tdb] Close table 'sessions0.tdb' Apr 26 11:25:43 192.168.122.209 [69694.426303] [tdb] Close table 'filter0.tdb' Apr 26 11:25:43 192.168.122.209 [69694.426736] [tempesta fw] modules are stopped Apr 26 11:25:43 192.168.122.209 [69694.653938] [tempesta fw] exiting... Apr 26 11:25:44 192.168.122.209 [69694.783605] [tdb] Shutdown Tempesta DB Apr 26 11:25:44 192.168.122.209 [69695.191020] End test: tls.test_tls_basic.TlsBasic.test_bad_request Apr 26 11:25:44 192.168.122.209 [69695.223325] Start test: tls.test_tls_alpn_basic.TestALPN.test_proto_order_https_least_prio Apr 26 11:25:46 192.168.122.209 [69696.851012] [tdb] Start Tempesta DB Apr 26 11:25:46 192.168.122.209 [69696.978556] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:25:47 192.168.122.209 [69697.703731] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [69697.703731] Maybe that's fine, but it's worth checking the [69697.703731] config - if there is no relations between the [69697.703731] names, then host name confusion attack is possible. Apr 26 11:25:47 192.168.122.209 [69697.754047] [tempesta fw] Configuration processing is completed. Apr 26 11:25:47 192.168.122.209 [69697.811147] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:25:47 192.168.122.209 [69698.509865] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:25:47 192.168.122.209 [69698.556436] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:25:47 192.168.122.209 [69698.602245] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:25:48 192.168.122.209 [69698.685918] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:25:48 192.168.122.209 [69698.726039] [tempesta fw] Tempesta FW is ready Apr 26 11:25:48 192.168.122.209 [69699.404073] [tdb] Close table 'client0.tdb' Apr 26 11:25:48 192.168.122.209 [69699.613327] [tdb] Close table 'sessions0.tdb' Apr 26 11:25:52 192.168.122.209 [69702.836358] [tdb] Close table 'cache0.tdb' Apr 26 11:25:52 192.168.122.209 [69703.068851] [tdb] Close table 'filter0.tdb' Apr 26 11:25:52 192.168.122.209 [69703.069274] [tempesta fw] modules are stopped Apr 26 11:25:52 192.168.122.209 [69703.282330] [tempesta fw] exiting... Apr 26 11:25:52 192.168.122.209 [69703.394515] [tdb] Shutdown Tempesta DB Apr 26 11:25:53 192.168.122.209 [69703.843303] End test: tls.test_tls_alpn_basic.TestALPN.test_proto_order_https_least_prio Apr 26 11:25:53 192.168.122.209 [69703.874224] Start test: tls.test_tls_alpn_basic.TestALPN.test_proto_order_https Apr 26 11:25:54 192.168.122.209 [69705.437403] [tdb] Start Tempesta DB Apr 26 11:25:54 192.168.122.209 [69705.579551] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:25:56 192.168.122.209 [69707.059897] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [69707.059897] Maybe that's fine, but it's worth checking the [69707.059897] config - if there is no relations between the [69707.059897] names, then host name confusion attack is possible. Apr 26 11:25:56 192.168.122.209 [69707.110071] [tempesta fw] Configuration processing is completed. Apr 26 11:25:56 192.168.122.209 [69707.165422] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:25:56 192.168.122.209 [69707.593850] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:25:56 192.168.122.209 [69707.620512] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:25:56 192.168.122.209 [69707.647591] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:25:57 192.168.122.209 [69707.718015] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:25:57 192.168.122.209 [69707.761965] [tempesta fw] Tempesta FW is ready Apr 26 11:25:57 192.168.122.209 [69708.420815] [tdb] Close table 'client0.tdb' Apr 26 11:25:57 192.168.122.209 [69708.605156] [tdb] Close table 'sessions0.tdb' Apr 26 11:26:01 192.168.122.209 [69711.785426] [tdb] Close table 'cache0.tdb' Apr 26 11:26:01 192.168.122.209 [69712.046680] [tdb] Close table 'filter0.tdb' Apr 26 11:26:01 192.168.122.209 [69712.047130] [tempesta fw] modules are stopped Apr 26 11:26:01 192.168.122.209 [69712.285946] [tempesta fw] exiting... Apr 26 11:26:01 192.168.122.209 [69712.441020] [tdb] Shutdown Tempesta DB Apr 26 11:26:02 192.168.122.209 [69712.831828] End test: tls.test_tls_alpn_basic.TestALPN.test_proto_order_https Apr 26 11:26:02 192.168.122.209 [69712.861040] Start test: tls.test_tls_alpn_basic.TestALPN.test_proto_order_h2_least_prio Apr 26 11:26:03 192.168.122.209 [69714.510779] [tdb] Start Tempesta DB Apr 26 11:26:03 192.168.122.209 [69714.646221] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:26:05 192.168.122.209 [69716.139856] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [69716.139856] Maybe that's fine, but it's worth checking the [69716.139856] config - if there is no relations between the [69716.139856] names, then host name confusion attack is possible. Apr 26 11:26:05 192.168.122.209 [69716.190221] [tempesta fw] Configuration processing is completed. Apr 26 11:26:05 192.168.122.209 [69716.243335] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:26:06 192.168.122.209 [69716.772650] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:26:06 192.168.122.209 [69716.807447] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:26:06 192.168.122.209 [69716.842423] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:26:06 192.168.122.209 [69716.906143] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:26:06 192.168.122.209 [69716.946115] [tempesta fw] Tempesta FW is ready Apr 26 11:26:06 192.168.122.209 [69717.621974] [tdb] Close table 'client0.tdb' Apr 26 11:26:07 192.168.122.209 [69717.848608] [tdb] Close table 'sessions0.tdb' Apr 26 11:26:10 192.168.122.209 [69721.008343] [tdb] Close table 'cache0.tdb' Apr 26 11:26:10 192.168.122.209 [69721.246542] [tdb] Close table 'filter0.tdb' Apr 26 11:26:10 192.168.122.209 [69721.246977] [tempesta fw] modules are stopped Apr 26 11:26:10 192.168.122.209 [69721.487365] [tempesta fw] exiting... Apr 26 11:26:10 192.168.122.209 [69721.606519] [tdb] Shutdown Tempesta DB Apr 26 11:26:11 192.168.122.209 [69722.066902] End test: tls.test_tls_alpn_basic.TestALPN.test_proto_order_h2_least_prio Apr 26 11:26:11 192.168.122.209 [69722.098345] Start test: tls.test_tls_alpn_basic.TestALPN.test_proto_order_h2 Apr 26 11:26:13 192.168.122.209 [69723.753548] [tdb] Start Tempesta DB Apr 26 11:26:13 192.168.122.209 [69723.889742] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:26:14 192.168.122.209 [69725.384065] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [69725.384065] Maybe that's fine, but it's worth checking the [69725.384065] config - if there is no relations between the [69725.384065] names, then host name confusion attack is possible. Apr 26 11:26:14 192.168.122.209 [69725.438334] [tempesta fw] Configuration processing is completed. Apr 26 11:26:14 192.168.122.209 [69725.498307] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:26:15 192.168.122.209 [69725.914763] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:26:15 192.168.122.209 [69725.941781] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:26:15 192.168.122.209 [69725.968494] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:26:15 192.168.122.209 [69726.042277] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:26:15 192.168.122.209 [69726.086214] [tempesta fw] Tempesta FW is ready Apr 26 11:26:16 192.168.122.209 [69726.758869] [tdb] Close table 'client0.tdb' Apr 26 11:26:16 192.168.122.209 [69726.946180] [tdb] Close table 'sessions0.tdb' Apr 26 11:26:19 192.168.122.209 [69730.127868] [tdb] Close table 'cache0.tdb' Apr 26 11:26:19 192.168.122.209 [69730.362320] [tdb] Close table 'filter0.tdb' Apr 26 11:26:19 192.168.122.209 [69730.362753] [tempesta fw] modules are stopped Apr 26 11:26:19 192.168.122.209 [69730.590241] [tempesta fw] exiting... Apr 26 11:26:20 192.168.122.209 [69730.710142] [tdb] Shutdown Tempesta DB Apr 26 11:26:20 192.168.122.209 [69731.071047] End test: tls.test_tls_alpn_basic.TestALPN.test_proto_order_h2 Apr 26 11:26:20 192.168.122.209 [69731.102872] Start test: tls.test_tls_alpn_basic.TestALPN.test_proto_mixed_https Apr 26 11:26:22 192.168.122.209 [69732.694281] [tdb] Start Tempesta DB Apr 26 11:26:22 192.168.122.209 [69732.833821] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:26:23 192.168.122.209 [69734.248137] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [69734.248137] Maybe that's fine, but it's worth checking the [69734.248137] config - if there is no relations between the [69734.248137] names, then host name confusion attack is possible. Apr 26 11:26:23 192.168.122.209 [69734.298421] [tempesta fw] Configuration processing is completed. Apr 26 11:26:23 192.168.122.209 [69734.350210] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:26:24 192.168.122.209 [69734.772729] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:26:24 192.168.122.209 [69734.798818] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:26:24 192.168.122.209 [69734.824648] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:26:24 192.168.122.209 [69734.898377] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:26:24 192.168.122.209 [69734.946286] [tempesta fw] Tempesta FW is ready Apr 26 11:26:24 192.168.122.209 [69735.588092] [tdb] Close table 'client0.tdb' Apr 26 11:26:25 192.168.122.209 [69735.763459] [tdb] Close table 'sessions0.tdb' Apr 26 11:26:28 192.168.122.209 [69738.942215] [tdb] Close table 'cache0.tdb' Apr 26 11:26:28 192.168.122.209 [69739.199560] [tdb] Close table 'filter0.tdb' Apr 26 11:26:28 192.168.122.209 [69739.199994] [tempesta fw] modules are stopped Apr 26 11:26:28 192.168.122.209 [69739.378330] [tempesta fw] exiting... Apr 26 11:26:28 192.168.122.209 [69739.513218] [tdb] Shutdown Tempesta DB Apr 26 11:26:29 192.168.122.209 [69739.885189] End test: tls.test_tls_alpn_basic.TestALPN.test_proto_mixed_https Apr 26 11:26:29 192.168.122.209 [69739.908948] Start test: tls.test_tls_alpn_basic.TestALPN.test_proto_mixed_h2_only Apr 26 11:26:30 192.168.122.209 [69741.364931] [tdb] Start Tempesta DB Apr 26 11:26:30 192.168.122.209 [69741.486552] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:26:32 192.168.122.209 [69742.952272] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [69742.952272] Maybe that's fine, but it's worth checking the [69742.952272] config - if there is no relations between the [69742.952272] names, then host name confusion attack is possible. Apr 26 11:26:32 192.168.122.209 [69743.006544] [tempesta fw] Configuration processing is completed. Apr 26 11:26:32 192.168.122.209 [69743.061643] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:26:32 192.168.122.209 [69743.481423] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:26:32 192.168.122.209 [69743.507095] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:26:32 192.168.122.209 [69743.532863] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:26:32 192.168.122.209 [69743.606531] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:26:32 192.168.122.209 [69743.668019] [tempesta fw] Tempesta FW is ready Apr 26 11:26:33 192.168.122.209 [69744.356455] [tdb] Close table 'client0.tdb' Apr 26 11:26:33 192.168.122.209 [69744.524257] [tdb] Close table 'sessions0.tdb' Apr 26 11:26:36 192.168.122.209 [69747.676294] [tdb] Close table 'cache0.tdb' Apr 26 11:26:37 192.168.122.209 [69747.911358] [tdb] Close table 'filter0.tdb' Apr 26 11:26:37 192.168.122.209 [69747.911781] [tempesta fw] modules are stopped Apr 26 11:26:37 192.168.122.209 [69748.104279] [tempesta fw] exiting... Apr 26 11:26:37 192.168.122.209 [69748.216302] [tdb] Shutdown Tempesta DB Apr 26 11:26:37 192.168.122.209 [69748.587614] End test: tls.test_tls_alpn_basic.TestALPN.test_proto_mixed_h2_only Apr 26 11:26:37 192.168.122.209 [69748.616935] Start test: tls.test_tls_alpn_basic.TestALPN.test_proto_mixed_h2_https Apr 26 11:26:39 192.168.122.209 [69750.190955] [tdb] Start Tempesta DB Apr 26 11:26:39 192.168.122.209 [69750.314523] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:26:41 192.168.122.209 [69751.811618] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [69751.811618] Maybe that's fine, but it's worth checking the [69751.811618] config - if there is no relations between the [69751.811618] names, then host name confusion attack is possible. Apr 26 11:26:41 192.168.122.209 [69751.850790] [tempesta fw] Configuration processing is completed. Apr 26 11:26:41 192.168.122.209 [69751.901235] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:26:41 192.168.122.209 [69752.312741] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:26:41 192.168.122.209 [69752.339925] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:26:41 192.168.122.209 [69752.365298] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:26:41 192.168.122.209 [69752.434616] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:26:41 192.168.122.209 [69752.478554] [tempesta fw] Tempesta FW is ready Apr 26 11:26:42 192.168.122.209 [69753.150447] [tdb] Close table 'client0.tdb' Apr 26 11:26:42 192.168.122.209 [69753.331701] [tdb] Close table 'sessions0.tdb' Apr 26 11:26:45 192.168.122.209 [69756.492110] [tdb] Close table 'cache0.tdb' Apr 26 11:26:46 192.168.122.209 [69756.760503] [tdb] Close table 'filter0.tdb' Apr 26 11:26:46 192.168.122.209 [69756.760901] [tempesta fw] modules are stopped Apr 26 11:26:46 192.168.122.209 [69756.947012] [tempesta fw] exiting... Apr 26 11:26:46 192.168.122.209 [69757.077121] [tdb] Shutdown Tempesta DB Apr 26 11:26:46 192.168.122.209 [69757.515050] End test: tls.test_tls_alpn_basic.TestALPN.test_proto_mixed_h2_https Apr 26 11:26:46 192.168.122.209 [69757.544955] Start test: tls.test_tls_alpn_basic.TestALPN.test_negative_https Apr 26 11:26:48 192.168.122.209 [69759.133646] [tdb] Start Tempesta DB Apr 26 11:26:48 192.168.122.209 [69759.278297] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:26:49 192.168.122.209 [69760.648480] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [69760.648480] Maybe that's fine, but it's worth checking the [69760.648480] config - if there is no relations between the [69760.648480] names, then host name confusion attack is possible. Apr 26 11:26:50 192.168.122.209 [69760.695086] [tempesta fw] Configuration processing is completed. Apr 26 11:26:50 192.168.122.209 [69760.747129] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:26:50 192.168.122.209 [69761.170967] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:26:50 192.168.122.209 [69761.197558] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:26:50 192.168.122.209 [69761.225453] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:26:50 192.168.122.209 [69761.294738] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:26:50 192.168.122.209 [69761.338672] [tempesta fw] Tempesta FW is ready Apr 26 11:26:50 192.168.122.209 [69761.522240] [tempesta tls] Warning: [::ffff:192.168.122.196] ClientHello: cannot find matching ALPN for h2 Apr 26 11:26:51 192.168.122.209 [69762.152442] [tdb] Close table 'client0.tdb' Apr 26 11:26:51 192.168.122.209 [69762.347286] [tdb] Close table 'sessions0.tdb' Apr 26 11:26:54 192.168.122.209 [69765.504894] [tdb] Close table 'cache0.tdb' Apr 26 11:26:55 192.168.122.209 [69765.740721] [tdb] Close table 'filter0.tdb' Apr 26 11:26:55 192.168.122.209 [69765.741425] [tempesta fw] modules are stopped Apr 26 11:26:55 192.168.122.209 [69765.927594] [tempesta fw] exiting... Apr 26 11:26:55 192.168.122.209 [69766.073272] [tdb] Shutdown Tempesta DB Apr 26 11:26:55 192.168.122.209 [69766.449661] End test: tls.test_tls_alpn_basic.TestALPN.test_negative_https Apr 26 11:26:55 192.168.122.209 [69766.478936] Start test: tls.test_tls_alpn_basic.TestALPN.test_negative_h2 Apr 26 11:26:57 192.168.122.209 [69768.147918] [tdb] Start Tempesta DB Apr 26 11:26:57 192.168.122.209 [69768.281635] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:26:59 192.168.122.209 [69769.748626] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [69769.748626] Maybe that's fine, but it's worth checking the [69769.748626] config - if there is no relations between the [69769.748626] names, then host name confusion attack is possible. Apr 26 11:26:59 192.168.122.209 [69769.802945] [tempesta fw] Configuration processing is completed. Apr 26 11:26:59 192.168.122.209 [69769.854861] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:26:59 192.168.122.209 [69770.269282] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:26:59 192.168.122.209 [69770.294111] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:26:59 192.168.122.209 [69770.318841] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:26:59 192.168.122.209 [69770.378859] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:26:59 192.168.122.209 [69770.434789] [tempesta fw] Tempesta FW is ready Apr 26 11:26:59 192.168.122.209 [69770.555727] [tempesta tls] Warning: [::ffff:192.168.122.196] ClientHello: cannot find matching ALPN for http/1.1 Apr 26 11:27:00 192.168.122.209 [69771.199838] [tdb] Close table 'client0.tdb' Apr 26 11:27:00 192.168.122.209 [69771.384888] [tdb] Close table 'sessions0.tdb' Apr 26 11:27:03 192.168.122.209 [69774.602158] [tdb] Close table 'cache0.tdb' Apr 26 11:27:04 192.168.122.209 [69774.845652] [tdb] Close table 'filter0.tdb' Apr 26 11:27:04 192.168.122.209 [69774.846064] [tempesta fw] modules are stopped Apr 26 11:27:04 192.168.122.209 [69775.059590] [tempesta fw] exiting... Apr 26 11:27:04 192.168.122.209 [69775.193577] [tdb] Shutdown Tempesta DB Apr 26 11:27:04 192.168.122.209 [69775.568070] End test: tls.test_tls_alpn_basic.TestALPN.test_negative_h2 Apr 26 11:27:04 192.168.122.209 [69775.604410] Start test: tls.test_tls_alpn_basic.TestALPN.test_alpn_default Apr 26 11:27:06 192.168.122.209 [69777.180976] [tdb] Start Tempesta DB Apr 26 11:27:06 192.168.122.209 [69777.308037] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:27:08 192.168.122.209 [69778.760756] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [69778.760756] Maybe that's fine, but it's worth checking the [69778.760756] config - if there is no relations between the [69778.760756] names, then host name confusion attack is possible. Apr 26 11:27:08 192.168.122.209 [69778.803296] [tempesta fw] Configuration processing is completed. Apr 26 11:27:08 192.168.122.209 [69778.857577] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:27:08 192.168.122.209 [69779.271473] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:27:08 192.168.122.209 [69779.298059] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:27:08 192.168.122.209 [69779.324759] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:27:08 192.168.122.209 [69779.362960] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:27:08 192.168.122.209 [69779.402907] [tempesta fw] Tempesta FW is ready Apr 26 11:27:09 192.168.122.209 [69780.046279] [tdb] Close table 'client0.tdb' Apr 26 11:27:09 192.168.122.209 [69780.238495] [tdb] Close table 'sessions0.tdb' Apr 26 11:27:12 192.168.122.209 [69783.542474] [tdb] Close table 'cache0.tdb' Apr 26 11:27:13 192.168.122.209 [69783.781783] [tdb] Close table 'filter0.tdb' Apr 26 11:27:13 192.168.122.209 [69783.782190] [tempesta fw] modules are stopped Apr 26 11:27:13 192.168.122.209 [69783.992882] [tempesta fw] exiting... Apr 26 11:27:13 192.168.122.209 [69784.138029] [tdb] Shutdown Tempesta DB Apr 26 11:27:13 192.168.122.209 [69784.515137] End test: tls.test_tls_alpn_basic.TestALPN.test_alpn_default Apr 26 11:27:13 192.168.122.209 [69784.544400] Start test: cache.test_cache.TestCacheAgeInResponseH2.test Apr 26 11:27:15 192.168.122.209 [69785.894738] [tdb] Start Tempesta DB Apr 26 11:27:15 192.168.122.209 [69786.042248] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:27:16 192.168.122.209 [69787.468444] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69787.468444] Maybe that's fine, but it's worth checking the [69787.468444] config - if there is no relations between the [69787.468444] names, then host name confusion attack is possible. Apr 26 11:27:16 192.168.122.209 [69787.559096] [tempesta fw] Configuration processing is completed. Apr 26 11:27:16 192.168.122.209 [69787.613503] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:27:17 192.168.122.209 [69788.067758] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:27:17 192.168.122.209 [69788.103942] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:27:17 192.168.122.209 [69788.138205] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:27:17 192.168.122.209 [69788.199115] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:27:17 192.168.122.209 [69788.200815] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:27:17 192.168.122.209 [69788.243057] [tempesta fw] Tempesta FW is ready Apr 26 11:27:18 192.168.122.209 [69788.901293] [tdb] Close table 'client0.tdb' Apr 26 11:27:18 192.168.122.209 [69789.095525] [tdb] Close table 'sessions0.tdb' Apr 26 11:27:21 192.168.122.209 [69792.294015] [tdb] Close table 'cache0.tdb' Apr 26 11:27:21 192.168.122.209 [69792.566011] [tdb] Close table 'filter0.tdb' Apr 26 11:27:21 192.168.122.209 [69792.566438] [tempesta fw] modules are stopped Apr 26 11:27:22 192.168.122.209 [69792.751743] [tempesta fw] exiting... Apr 26 11:27:22 192.168.122.209 [69792.909281] [tdb] Shutdown Tempesta DB Apr 26 11:27:22 192.168.122.209 [69793.300839] End test: cache.test_cache.TestCacheAgeInResponseH2.test Apr 26 11:27:22 192.168.122.209 [69793.325853] Start test: cache.test_cache.TestCacheAgeInResponseHttp.test Apr 26 11:27:23 192.168.122.209 [69794.666936] [tdb] Start Tempesta DB Apr 26 11:27:24 192.168.122.209 [69794.811478] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:27:25 192.168.122.209 [69796.252401] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69796.252401] Maybe that's fine, but it's worth checking the [69796.252401] config - if there is no relations between the [69796.252401] names, then host name confusion attack is possible. Apr 26 11:27:25 192.168.122.209 [69796.347238] [tempesta fw] Configuration processing is completed. Apr 26 11:27:25 192.168.122.209 [69796.398284] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:27:26 192.168.122.209 [69796.811114] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:27:26 192.168.122.209 [69796.837210] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:27:26 192.168.122.209 [69796.863653] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:27:26 192.168.122.209 [69796.907196] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:27:26 192.168.122.209 [69796.908875] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:27:26 192.168.122.209 [69796.975173] [tempesta fw] Tempesta FW is ready Apr 26 11:27:26 192.168.122.209 [69797.666043] [tdb] Close table 'client0.tdb' Apr 26 11:27:27 192.168.122.209 [69797.848411] [tdb] Close table 'sessions0.tdb' Apr 26 11:27:30 192.168.122.209 [69801.008989] [tdb] Close table 'cache0.tdb' Apr 26 11:27:30 192.168.122.209 [69801.249998] [tdb] Close table 'filter0.tdb' Apr 26 11:27:30 192.168.122.209 [69801.250447] [tempesta fw] modules are stopped Apr 26 11:27:30 192.168.122.209 [69801.444974] [tempesta fw] exiting... Apr 26 11:27:30 192.168.122.209 [69801.546611] [tdb] Shutdown Tempesta DB Apr 26 11:27:31 192.168.122.209 [69801.956389] End test: cache.test_cache.TestCacheAgeInResponseHttp.test Apr 26 11:27:31 192.168.122.209 [69801.988670] Start test: cache.test_cache.TestCacheClean.test Apr 26 11:27:32 192.168.122.209 [69803.388575] [tdb] Start Tempesta DB Apr 26 11:27:32 192.168.122.209 [69803.534948] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:27:34 192.168.122.209 [69805.165192] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [69805.165192] Maybe that's fine, but it's worth checking the [69805.165192] config - if there is no relations between the [69805.165192] names, then host name confusion attack is possible. Apr 26 11:27:34 192.168.122.209 [69805.267361] [tempesta fw] Configuration processing is completed. Apr 26 11:27:34 192.168.122.209 [69805.320910] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:27:35 192.168.122.209 [69805.831858] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:27:35 192.168.122.209 [69805.863664] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:27:35 192.168.122.209 [69805.895955] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:27:35 192.168.122.209 [69805.939337] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:27:35 192.168.122.209 [69806.007321] [tempesta fw] Tempesta FW is ready Apr 26 11:27:39 192.168.122.209 [69809.740629] [tdb] Close table 'client0.tdb' Apr 26 11:27:39 192.168.122.209 [69809.928705] [tdb] Close table 'sessions0.tdb' Apr 26 11:27:42 192.168.122.209 [69813.173308] [tdb] Close table 'cache0.tdb' Apr 26 11:27:42 192.168.122.209 [69813.420750] [tdb] Close table 'filter0.tdb' Apr 26 11:27:42 192.168.122.209 [69813.421159] [tempesta fw] modules are stopped Apr 26 11:27:42 192.168.122.209 [69813.644596] [tempesta fw] exiting... Apr 26 11:27:43 192.168.122.209 [69813.768348] [tdb] Shutdown Tempesta DB Apr 26 11:27:43 192.168.122.209 [69814.156231] End test: cache.test_cache.TestCacheClean.test Apr 26 11:27:43 192.168.122.209 [69814.183569] Start test: cache.test_cache.TestCacheDockerH2Body.test Apr 26 11:27:46 192.168.122.209 [69817.522703] [tdb] Start Tempesta DB Apr 26 11:27:46 192.168.122.209 [69817.678785] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:27:48 192.168.122.209 [69819.124853] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69819.124853] Maybe that's fine, but it's worth checking the [69819.124853] config - if there is no relations between the [69819.124853] names, then host name confusion attack is possible. Apr 26 11:27:48 192.168.122.209 [69819.227592] [tempesta fw] Configuration processing is completed. Apr 26 11:27:48 192.168.122.209 [69819.285320] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:27:49 192.168.122.209 [69819.723929] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:27:49 192.168.122.209 [69819.752429] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:27:49 192.168.122.209 [69819.781806] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:27:49 192.168.122.209 [69819.823521] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:27:49 192.168.122.209 [69819.825265] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:27:49 192.168.122.209 [69819.867442] [tempesta fw] Tempesta FW is ready Apr 26 11:27:50 192.168.122.209 [69820.749597] [tdb] Close table 'client0.tdb' Apr 26 11:27:50 192.168.122.209 [69820.963841] [tdb] Close table 'sessions0.tdb' Apr 26 11:27:53 192.168.122.209 [69824.209128] [tdb] Close table 'cache0.tdb' Apr 26 11:27:53 192.168.122.209 [69824.468016] [tdb] Close table 'filter0.tdb' Apr 26 11:27:53 192.168.122.209 [69824.468429] [tempesta fw] modules are stopped Apr 26 11:27:53 192.168.122.209 [69824.666415] [tempesta fw] exiting... Apr 26 11:27:54 192.168.122.209 [69824.794610] [tdb] Shutdown Tempesta DB Apr 26 11:27:54 192.168.122.209 [69825.469583] End test: cache.test_cache.TestCacheDockerH2Body.test Apr 26 11:27:54 192.168.122.209 [69825.504916] Start test: cache.test_cache.TestCacheDockerH2Headers.test Apr 26 11:27:57 192.168.122.209 [69828.003682] [tdb] Start Tempesta DB Apr 26 11:27:57 192.168.122.209 [69828.152685] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:27:58 192.168.122.209 [69829.540967] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69829.540967] Maybe that's fine, but it's worth checking the [69829.540967] config - if there is no relations between the [69829.540967] names, then host name confusion attack is possible. Apr 26 11:27:58 192.168.122.209 [69829.640399] [tempesta fw] Configuration processing is completed. Apr 26 11:27:59 192.168.122.209 [69829.698485] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:27:59 192.168.122.209 [69830.236939] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:27:59 192.168.122.209 [69830.270973] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:27:59 192.168.122.209 [69830.304711] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:27:59 192.168.122.209 [69830.367639] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:27:59 192.168.122.209 [69830.369325] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:27:59 192.168.122.209 [69830.407587] [tempesta fw] Tempesta FW is ready Apr 26 11:28:00 192.168.122.209 [69831.271767] [tdb] Close table 'client0.tdb' Apr 26 11:28:00 192.168.122.209 [69831.480701] [tdb] Close table 'sessions0.tdb' Apr 26 11:28:03 192.168.122.209 [69834.633544] [tdb] Close table 'cache0.tdb' Apr 26 11:28:04 192.168.122.209 [69834.858030] [tdb] Close table 'filter0.tdb' Apr 26 11:28:04 192.168.122.209 [69834.858429] [tempesta fw] modules are stopped Apr 26 11:28:04 192.168.122.209 [69835.082685] [tempesta fw] exiting... Apr 26 11:28:04 192.168.122.209 [69835.223526] [tdb] Shutdown Tempesta DB Apr 26 11:28:05 192.168.122.209 [69835.944054] End test: cache.test_cache.TestCacheDockerH2Headers.test Apr 26 11:28:05 192.168.122.209 [69835.980253] Start test: cache.test_cache.TestCacheDockerHttpBody.test Apr 26 11:28:07 192.168.122.209 [69837.947650] [tdb] Start Tempesta DB Apr 26 11:28:07 192.168.122.209 [69838.081918] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:28:08 192.168.122.209 [69839.561285] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69839.561285] Maybe that's fine, but it's worth checking the [69839.561285] config - if there is no relations between the [69839.561285] names, then host name confusion attack is possible. Apr 26 11:28:08 192.168.122.209 [69839.663857] [tempesta fw] Configuration processing is completed. Apr 26 11:28:09 192.168.122.209 [69839.720301] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:28:09 192.168.122.209 [69840.151890] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:28:09 192.168.122.209 [69840.186384] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:28:09 192.168.122.209 [69840.213390] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:28:09 192.168.122.209 [69840.255789] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:28:09 192.168.122.209 [69840.257251] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:28:09 192.168.122.209 [69840.307747] [tempesta fw] Tempesta FW is ready Apr 26 11:28:10 192.168.122.209 [69841.160452] [tdb] Close table 'client0.tdb' Apr 26 11:28:10 192.168.122.209 [69841.345370] [tdb] Close table 'sessions0.tdb' Apr 26 11:28:13 192.168.122.209 [69844.555758] [tdb] Close table 'cache0.tdb' Apr 26 11:28:14 192.168.122.209 [69844.815529] [tdb] Close table 'filter0.tdb' Apr 26 11:28:14 192.168.122.209 [69844.815964] [tempesta fw] modules are stopped Apr 26 11:28:14 192.168.122.209 [69845.044856] [tempesta fw] exiting... Apr 26 11:28:14 192.168.122.209 [69845.182831] [tdb] Shutdown Tempesta DB Apr 26 11:28:15 192.168.122.209 [69845.846359] End test: cache.test_cache.TestCacheDockerHttpBody.test Apr 26 11:28:15 192.168.122.209 [69845.873248] Start test: cache.test_cache.TestCacheDockerHttpHeaders.test Apr 26 11:28:17 192.168.122.209 [69847.830469] [tdb] Start Tempesta DB Apr 26 11:28:17 192.168.122.209 [69847.974599] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:28:18 192.168.122.209 [69849.472386] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69849.472386] Maybe that's fine, but it's worth checking the [69849.472386] config - if there is no relations between the [69849.472386] names, then host name confusion attack is possible. Apr 26 11:28:18 192.168.122.209 [69849.591961] [tempesta fw] Configuration processing is completed. Apr 26 11:28:18 192.168.122.209 [69849.648019] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:28:19 192.168.122.209 [69850.058754] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:28:19 192.168.122.209 [69850.085811] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:28:19 192.168.122.209 [69850.110881] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:28:19 192.168.122.209 [69850.159873] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:28:19 192.168.122.209 [69850.161287] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:28:19 192.168.122.209 [69850.203866] [tempesta fw] Tempesta FW is ready Apr 26 11:28:20 192.168.122.209 [69851.010333] [tdb] Close table 'client0.tdb' Apr 26 11:28:20 192.168.122.209 [69851.200884] [tdb] Close table 'sessions0.tdb' Apr 26 11:28:23 192.168.122.209 [69854.343542] [tdb] Close table 'cache0.tdb' Apr 26 11:28:23 192.168.122.209 [69854.600788] [tdb] Close table 'filter0.tdb' Apr 26 11:28:23 192.168.122.209 [69854.601206] [tempesta fw] modules are stopped Apr 26 11:28:24 192.168.122.209 [69854.795715] [tempesta fw] exiting... Apr 26 11:28:24 192.168.122.209 [69854.941240] [tdb] Shutdown Tempesta DB Apr 26 11:28:24 192.168.122.209 [69855.576666] End test: cache.test_cache.TestCacheDockerHttpHeaders.test Apr 26 11:28:24 192.168.122.209 [69855.603080] Start test: cache.test_cache.TestCacheDockerHttpsBody.test Apr 26 11:28:26 192.168.122.209 [69857.638528] [tdb] Start Tempesta DB Apr 26 11:28:27 192.168.122.209 [69857.777322] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:28:28 192.168.122.209 [69859.229283] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69859.229283] Maybe that's fine, but it's worth checking the [69859.229283] config - if there is no relations between the [69859.229283] names, then host name confusion attack is possible. Apr 26 11:28:28 192.168.122.209 [69859.352059] [tempesta fw] Configuration processing is completed. Apr 26 11:28:28 192.168.122.209 [69859.403482] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:28:29 192.168.122.209 [69859.822476] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:28:29 192.168.122.209 [69859.848499] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:28:29 192.168.122.209 [69859.874035] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:28:29 192.168.122.209 [69859.932020] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:28:29 192.168.122.209 [69859.933767] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:28:29 192.168.122.209 [69859.971984] [tempesta fw] Tempesta FW is ready Apr 26 11:28:30 192.168.122.209 [69860.849488] [tdb] Close table 'client0.tdb' Apr 26 11:28:30 192.168.122.209 [69861.033191] [tdb] Close table 'sessions0.tdb' Apr 26 11:28:33 192.168.122.209 [69864.222163] [tdb] Close table 'cache0.tdb' Apr 26 11:28:33 192.168.122.209 [69864.454995] [tdb] Close table 'filter0.tdb' Apr 26 11:28:33 192.168.122.209 [69864.455397] [tempesta fw] modules are stopped Apr 26 11:28:33 192.168.122.209 [69864.668302] [tempesta fw] exiting... Apr 26 11:28:34 192.168.122.209 [69864.796588] [tdb] Shutdown Tempesta DB Apr 26 11:28:34 192.168.122.209 [69865.424818] End test: cache.test_cache.TestCacheDockerHttpsBody.test Apr 26 11:28:34 192.168.122.209 [69865.452237] Start test: cache.test_cache.TestCacheDockerHttpsHeaders.test Apr 26 11:28:36 192.168.122.209 [69867.413714] [tdb] Start Tempesta DB Apr 26 11:28:36 192.168.122.209 [69867.552333] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:28:38 192.168.122.209 [69869.029412] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69869.029412] Maybe that's fine, but it's worth checking the [69869.029412] config - if there is no relations between the [69869.029412] names, then host name confusion attack is possible. Apr 26 11:28:38 192.168.122.209 [69869.132234] [tempesta fw] Configuration processing is completed. Apr 26 11:28:38 192.168.122.209 [69869.187776] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:28:38 192.168.122.209 [69869.645311] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:28:38 192.168.122.209 [69869.674311] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:28:39 192.168.122.209 [69869.703255] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:28:39 192.168.122.209 [69869.752071] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:28:39 192.168.122.209 [69869.753770] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:28:39 192.168.122.209 [69869.792115] [tempesta fw] Tempesta FW is ready Apr 26 11:28:39 192.168.122.209 [69870.622174] [tdb] Close table 'client0.tdb' Apr 26 11:28:40 192.168.122.209 [69870.810380] [tdb] Close table 'sessions0.tdb' Apr 26 11:28:43 192.168.122.209 [69874.038616] [tdb] Close table 'cache0.tdb' Apr 26 11:28:43 192.168.122.209 [69874.288063] [tdb] Close table 'filter0.tdb' Apr 26 11:28:43 192.168.122.209 [69874.288494] [tempesta fw] modules are stopped Apr 26 11:28:43 192.168.122.209 [69874.483328] [tempesta fw] exiting... Apr 26 11:28:43 192.168.122.209 [69874.602700] [tdb] Shutdown Tempesta DB Apr 26 11:28:44 192.168.122.209 [69875.214369] End test: cache.test_cache.TestCacheDockerHttpsHeaders.test Apr 26 11:28:44 192.168.122.209 [69875.256065] Start test: cache.test_cache.TestCacheDublicateHeadersH2.test_raw Apr 26 11:28:45 192.168.122.209 [69876.594363] [tdb] Start Tempesta DB Apr 26 11:28:46 192.168.122.209 [69876.736268] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:28:47 192.168.122.209 [69878.165527] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69878.165527] Maybe that's fine, but it's worth checking the [69878.165527] config - if there is no relations between the [69878.165527] names, then host name confusion attack is possible. Apr 26 11:28:47 192.168.122.209 [69878.256295] [tempesta fw] Configuration processing is completed. Apr 26 11:28:47 192.168.122.209 [69878.312657] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:28:48 192.168.122.209 [69878.738681] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:28:48 192.168.122.209 [69878.765938] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:28:48 192.168.122.209 [69878.793222] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:28:48 192.168.122.209 [69878.852288] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:28:48 192.168.122.209 [69878.854044] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:28:48 192.168.122.209 [69878.920225] [tempesta fw] Tempesta FW is ready Apr 26 11:28:48 192.168.122.209 [69879.678549] [tdb] Close table 'client0.tdb' Apr 26 11:28:49 192.168.122.209 [69879.871175] [tdb] Close table 'sessions0.tdb' Apr 26 11:28:52 192.168.122.209 [69883.042927] [tdb] Close table 'cache0.tdb' Apr 26 11:28:52 192.168.122.209 [69883.282776] [tdb] Close table 'filter0.tdb' Apr 26 11:28:52 192.168.122.209 [69883.283181] [tempesta fw] modules are stopped Apr 26 11:28:52 192.168.122.209 [69883.484864] [tempesta fw] exiting... Apr 26 11:28:52 192.168.122.209 [69883.645689] [tdb] Shutdown Tempesta DB Apr 26 11:28:53 192.168.122.209 [69884.072549] End test: cache.test_cache.TestCacheDublicateHeadersH2.test_raw Apr 26 11:28:53 192.168.122.209 [69884.102580] Start test: cache.test_cache.TestCacheDublicateHeadersH2.test_regular Apr 26 11:28:54 192.168.122.209 [69885.538902] [tdb] Start Tempesta DB Apr 26 11:28:54 192.168.122.209 [69885.669511] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:28:56 192.168.122.209 [69887.069656] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69887.069656] Maybe that's fine, but it's worth checking the [69887.069656] config - if there is no relations between the [69887.069656] names, then host name confusion attack is possible. Apr 26 11:28:56 192.168.122.209 [69887.160412] [tempesta fw] Configuration processing is completed. Apr 26 11:28:56 192.168.122.209 [69887.229170] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:28:56 192.168.122.209 [69887.648329] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:28:56 192.168.122.209 [69887.674556] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:28:57 192.168.122.209 [69887.701554] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:28:57 192.168.122.209 [69887.760406] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:28:57 192.168.122.209 [69887.762143] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:28:57 192.168.122.209 [69887.804350] [tempesta fw] Tempesta FW is ready Apr 26 11:28:57 192.168.122.209 [69888.468718] [tdb] Close table 'client0.tdb' Apr 26 11:28:57 192.168.122.209 [69888.657921] [tdb] Close table 'sessions0.tdb' Apr 26 11:29:01 192.168.122.209 [69891.841370] [tdb] Close table 'cache0.tdb' Apr 26 11:29:01 192.168.122.209 [69892.121752] [tdb] Close table 'filter0.tdb' Apr 26 11:29:01 192.168.122.209 [69892.122189] [tempesta fw] modules are stopped Apr 26 11:29:01 192.168.122.209 [69892.321978] [tempesta fw] exiting... Apr 26 11:29:01 192.168.122.209 [69892.444748] [tdb] Shutdown Tempesta DB Apr 26 11:29:02 192.168.122.209 [69892.870970] End test: cache.test_cache.TestCacheDublicateHeadersH2.test_regular Apr 26 11:29:02 192.168.122.209 [69892.900641] Start test: cache.test_cache.TestCacheDublicateHeadersHttp.test_raw Apr 26 11:29:03 192.168.122.209 [69894.284220] [tdb] Start Tempesta DB Apr 26 11:29:03 192.168.122.209 [69894.426765] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:29:05 192.168.122.209 [69895.862760] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69895.862760] Maybe that's fine, but it's worth checking the [69895.862760] config - if there is no relations between the [69895.862760] names, then host name confusion attack is possible. Apr 26 11:29:05 192.168.122.209 [69895.964514] [tempesta fw] Configuration processing is completed. Apr 26 11:29:05 192.168.122.209 [69896.016254] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:29:05 192.168.122.209 [69896.452101] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:29:05 192.168.122.209 [69896.481712] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:29:05 192.168.122.209 [69896.511976] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:29:05 192.168.122.209 [69896.572528] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:29:05 192.168.122.209 [69896.574269] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:29:05 192.168.122.209 [69896.624462] [tempesta fw] Tempesta FW is ready Apr 26 11:29:06 192.168.122.209 [69897.315036] [tdb] Close table 'client0.tdb' Apr 26 11:29:06 192.168.122.209 [69897.495536] [tdb] Close table 'sessions0.tdb' Apr 26 11:29:10 192.168.122.209 [69900.723894] [tdb] Close table 'cache0.tdb' Apr 26 11:29:10 192.168.122.209 [69900.988445] [tdb] Close table 'filter0.tdb' Apr 26 11:29:10 192.168.122.209 [69900.988890] [tempesta fw] modules are stopped Apr 26 11:29:10 192.168.122.209 [69901.183133] [tempesta fw] exiting... Apr 26 11:29:10 192.168.122.209 [69901.302065] [tdb] Shutdown Tempesta DB Apr 26 11:29:11 192.168.122.209 [69901.724004] End test: cache.test_cache.TestCacheDublicateHeadersHttp.test_raw Apr 26 11:29:11 192.168.122.209 [69901.761368] Start test: cache.test_cache.TestCacheDublicateHeadersHttp.test_regular Apr 26 11:29:12 192.168.122.209 [69903.183889] [tdb] Start Tempesta DB Apr 26 11:29:12 192.168.122.209 [69903.325117] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:29:14 192.168.122.209 [69904.777947] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69904.777947] Maybe that's fine, but it's worth checking the [69904.777947] config - if there is no relations between the [69904.777947] names, then host name confusion attack is possible. Apr 26 11:29:14 192.168.122.209 [69904.872658] [tempesta fw] Configuration processing is completed. Apr 26 11:29:14 192.168.122.209 [69904.927653] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:29:14 192.168.122.209 [69905.434197] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:29:14 192.168.122.209 [69905.474125] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:29:14 192.168.122.209 [69905.505075] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:29:14 192.168.122.209 [69905.556656] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:29:14 192.168.122.209 [69905.558391] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:29:14 192.168.122.209 [69905.600591] [tempesta fw] Tempesta FW is ready Apr 26 11:29:15 192.168.122.209 [69906.318602] [tdb] Close table 'client0.tdb' Apr 26 11:29:15 192.168.122.209 [69906.500681] [tdb] Close table 'sessions0.tdb' Apr 26 11:29:19 192.168.122.209 [69909.860457] [tdb] Close table 'cache0.tdb' Apr 26 11:29:19 192.168.122.209 [69910.108930] [tdb] Close table 'filter0.tdb' Apr 26 11:29:19 192.168.122.209 [69910.109345] [tempesta fw] modules are stopped Apr 26 11:29:19 192.168.122.209 [69910.295705] [tempesta fw] exiting... Apr 26 11:29:19 192.168.122.209 [69910.417332] [tdb] Shutdown Tempesta DB Apr 26 11:29:20 192.168.122.209 [69910.814197] End test: cache.test_cache.TestCacheDublicateHeadersHttp.test_regular Apr 26 11:29:20 192.168.122.209 [69910.845070] Start test: cache.test_cache.TestCacheH2.test_cache_date Apr 26 11:29:21 192.168.122.209 [69912.231590] [tdb] Start Tempesta DB Apr 26 11:29:21 192.168.122.209 [69912.369104] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:29:23 192.168.122.209 [69913.810121] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69913.810121] Maybe that's fine, but it's worth checking the [69913.810121] config - if there is no relations between the [69913.810121] names, then host name confusion attack is possible. Apr 26 11:29:23 192.168.122.209 [69913.980781] [tempesta fw] Configuration processing is completed. Apr 26 11:29:23 192.168.122.209 [69914.036878] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:29:23 192.168.122.209 [69914.446712] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:29:23 192.168.122.209 [69914.473509] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:29:23 192.168.122.209 [69914.508853] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:29:23 192.168.122.209 [69914.560763] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:29:23 192.168.122.209 [69914.562507] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:29:23 192.168.122.209 [69914.600685] [tempesta fw] Tempesta FW is ready Apr 26 11:29:24 192.168.122.209 [69915.500267] [tdb] Close table 'client0.tdb' Apr 26 11:29:25 192.168.122.209 [69915.689786] [tdb] Close table 'sessions0.tdb' Apr 26 11:29:28 192.168.122.209 [69918.922239] [tdb] Close table 'cache0.tdb' Apr 26 11:29:28 192.168.122.209 [69919.196046] [tdb] Close table 'filter0.tdb' Apr 26 11:29:28 192.168.122.209 [69919.196565] [tempesta fw] modules are stopped Apr 26 11:29:28 192.168.122.209 [69919.379699] [tempesta fw] exiting... Apr 26 11:29:28 192.168.122.209 [69919.517213] [tdb] Shutdown Tempesta DB Apr 26 11:29:29 192.168.122.209 [69919.954771] End test: cache.test_cache.TestCacheH2.test_cache_date Apr 26 11:29:29 192.168.122.209 [69919.983962] Start test: cache.test_cache.TestCacheH2.test_disabled_cache_bypass_all Apr 26 11:29:30 192.168.122.209 [69921.367200] [tdb] Start Tempesta DB Apr 26 11:29:30 192.168.122.209 [69921.509204] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:29:32 192.168.122.209 [69922.898203] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69922.898203] Maybe that's fine, but it's worth checking the [69922.898203] config - if there is no relations between the [69922.898203] names, then host name confusion attack is possible. Apr 26 11:29:32 192.168.122.209 [69923.020950] [tempesta fw] Configuration processing is completed. Apr 26 11:29:32 192.168.122.209 [69923.089768] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:29:32 192.168.122.209 [69923.128259] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:29:32 192.168.122.209 [69923.164517] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:29:32 192.168.122.209 [69923.216930] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:29:32 192.168.122.209 [69923.218668] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:29:32 192.168.122.209 [69923.288825] [tempesta fw] Tempesta FW is ready Apr 26 11:29:33 192.168.122.209 [69924.182953] [tdb] Close table 'client0.tdb' Apr 26 11:29:33 192.168.122.209 [69924.375301] [tdb] Close table 'sessions0.tdb' Apr 26 11:29:33 192.168.122.209 [69924.612444] [tdb] Close table 'filter0.tdb' Apr 26 11:29:33 192.168.122.209 [69924.612869] [tempesta fw] modules are stopped Apr 26 11:29:34 192.168.122.209 [69924.864951] [tempesta fw] exiting... Apr 26 11:29:34 192.168.122.209 [69924.992599] [tdb] Shutdown Tempesta DB Apr 26 11:29:34 192.168.122.209 [69925.374029] End test: cache.test_cache.TestCacheH2.test_disabled_cache_bypass_all Apr 26 11:29:34 192.168.122.209 [69925.414135] Start test: cache.test_cache.TestCacheH2.test_disabled_cache_bypass_prefix Apr 26 11:29:36 192.168.122.209 [69926.799140] [tdb] Start Tempesta DB Apr 26 11:29:36 192.168.122.209 [69926.932712] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:29:36 192.168.122.209 [69927.642203] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69927.642203] Maybe that's fine, but it's worth checking the [69927.642203] config - if there is no relations between the [69927.642203] names, then host name confusion attack is possible. Apr 26 11:29:37 192.168.122.209 [69927.804929] [tempesta fw] Configuration processing is completed. Apr 26 11:29:37 192.168.122.209 [69927.857938] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:29:37 192.168.122.209 [69927.886519] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:29:37 192.168.122.209 [69927.914092] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:29:37 192.168.122.209 [69927.960917] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:29:37 192.168.122.209 [69927.962656] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:29:37 192.168.122.209 [69928.000874] [tempesta fw] Tempesta FW is ready Apr 26 11:29:38 192.168.122.209 [69928.857558] [tdb] Close table 'client0.tdb' Apr 26 11:29:38 192.168.122.209 [69929.056436] [tdb] Close table 'sessions0.tdb' Apr 26 11:29:38 192.168.122.209 [69929.287446] [tdb] Close table 'filter0.tdb' Apr 26 11:29:38 192.168.122.209 [69929.287866] [tempesta fw] modules are stopped Apr 26 11:29:38 192.168.122.209 [69929.491760] [tempesta fw] exiting... Apr 26 11:29:38 192.168.122.209 [69929.624618] [tdb] Shutdown Tempesta DB Apr 26 11:29:39 192.168.122.209 [69930.062118] End test: cache.test_cache.TestCacheH2.test_disabled_cache_bypass_prefix Apr 26 11:29:39 192.168.122.209 [69930.097364] Start test: cache.test_cache.TestCacheH2.test_disabled_cache_bypass_suffix Apr 26 11:29:40 192.168.122.209 [69931.432605] [tdb] Start Tempesta DB Apr 26 11:29:40 192.168.122.209 [69931.565011] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:29:41 192.168.122.209 [69932.298320] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69932.298320] Maybe that's fine, but it's worth checking the [69932.298320] config - if there is no relations between the [69932.298320] names, then host name confusion attack is possible. Apr 26 11:29:41 192.168.122.209 [69932.489034] [tempesta fw] Configuration processing is completed. Apr 26 11:29:41 192.168.122.209 [69932.548663] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:29:41 192.168.122.209 [69932.579909] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:29:41 192.168.122.209 [69932.610951] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:29:41 192.168.122.209 [69932.660991] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:29:41 192.168.122.209 [69932.662735] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:29:42 192.168.122.209 [69932.700943] [tempesta fw] Tempesta FW is ready Apr 26 11:29:42 192.168.122.209 [69933.615329] [tdb] Close table 'client0.tdb' Apr 26 11:29:43 192.168.122.209 [69933.810123] [tdb] Close table 'sessions0.tdb' Apr 26 11:29:43 192.168.122.209 [69934.051453] [tdb] Close table 'filter0.tdb' Apr 26 11:29:43 192.168.122.209 [69934.051863] [tempesta fw] modules are stopped Apr 26 11:29:43 192.168.122.209 [69934.220942] [tempesta fw] exiting... Apr 26 11:29:43 192.168.122.209 [69934.324683] [tdb] Shutdown Tempesta DB Apr 26 11:29:43 192.168.122.209 [69934.672381] End test: cache.test_cache.TestCacheH2.test_disabled_cache_bypass_suffix Apr 26 11:29:44 192.168.122.209 [69934.710929] Start test: cache.test_cache.TestCacheH2.test_disabled_cache_fulfill_all Apr 26 11:29:45 192.168.122.209 [69936.113098] [tdb] Start Tempesta DB Apr 26 11:29:45 192.168.122.209 [69936.248855] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:29:46 192.168.122.209 [69936.902469] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69936.902469] Maybe that's fine, but it's worth checking the [69936.902469] config - if there is no relations between the [69936.902469] names, then host name confusion attack is possible. Apr 26 11:29:46 192.168.122.209 [69937.033099] [tempesta fw] Configuration processing is completed. Apr 26 11:29:46 192.168.122.209 [69937.086850] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:29:46 192.168.122.209 [69937.115439] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:29:46 192.168.122.209 [69937.144622] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:29:46 192.168.122.209 [69937.185034] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:29:46 192.168.122.209 [69937.186794] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:29:46 192.168.122.209 [69937.232992] [tempesta fw] Tempesta FW is ready Apr 26 11:29:47 192.168.122.209 [69938.116532] [tdb] Close table 'client0.tdb' Apr 26 11:29:47 192.168.122.209 [69938.290961] [tdb] Close table 'sessions0.tdb' Apr 26 11:29:47 192.168.122.209 [69938.545175] [tdb] Close table 'filter0.tdb' Apr 26 11:29:47 192.168.122.209 [69938.545592] [tempesta fw] modules are stopped Apr 26 11:29:48 192.168.122.209 [69938.754929] [tempesta fw] exiting... Apr 26 11:29:48 192.168.122.209 [69938.876636] [tdb] Shutdown Tempesta DB Apr 26 11:29:48 192.168.122.209 [69939.273154] End test: cache.test_cache.TestCacheH2.test_disabled_cache_fulfill_all Apr 26 11:29:48 192.168.122.209 [69939.300074] Start test: cache.test_cache.TestCacheH2.test_disabled_cache_fulfill_prefix Apr 26 11:29:49 192.168.122.209 [69940.665353] [tdb] Start Tempesta DB Apr 26 11:29:50 192.168.122.209 [69940.796348] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:29:50 192.168.122.209 [69941.510573] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69941.510573] Maybe that's fine, but it's worth checking the [69941.510573] config - if there is no relations between the [69941.510573] names, then host name confusion attack is possible. Apr 26 11:29:50 192.168.122.209 [69941.681469] [tempesta fw] Configuration processing is completed. Apr 26 11:29:51 192.168.122.209 [69941.745203] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:29:51 192.168.122.209 [69941.781865] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:29:51 192.168.122.209 [69941.816783] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:29:51 192.168.122.209 [69941.877130] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:29:51 192.168.122.209 [69941.878941] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:29:51 192.168.122.209 [69941.917064] [tempesta fw] Tempesta FW is ready Apr 26 11:29:52 192.168.122.209 [69942.773108] [tdb] Close table 'client0.tdb' Apr 26 11:29:52 192.168.122.209 [69942.948306] [tdb] Close table 'sessions0.tdb' Apr 26 11:29:52 192.168.122.209 [69943.190762] [tdb] Close table 'filter0.tdb' Apr 26 11:29:52 192.168.122.209 [69943.191168] [tempesta fw] modules are stopped Apr 26 11:29:52 192.168.122.209 [69943.379313] [tempesta fw] exiting... Apr 26 11:29:52 192.168.122.209 [69943.507745] [tdb] Shutdown Tempesta DB Apr 26 11:29:53 192.168.122.209 [69943.957721] End test: cache.test_cache.TestCacheH2.test_disabled_cache_fulfill_prefix Apr 26 11:29:53 192.168.122.209 [69943.983968] Start test: cache.test_cache.TestCacheH2.test_disabled_cache_fulfill_suffix Apr 26 11:29:54 192.168.122.209 [69945.419295] [tdb] Start Tempesta DB Apr 26 11:29:54 192.168.122.209 [69945.568248] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:29:55 192.168.122.209 [69946.290412] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69946.290412] Maybe that's fine, but it's worth checking the [69946.290412] config - if there is no relations between the [69946.290412] names, then host name confusion attack is possible. Apr 26 11:29:55 192.168.122.209 [69946.477174] [tempesta fw] Configuration processing is completed. Apr 26 11:29:55 192.168.122.209 [69946.529262] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:29:55 192.168.122.209 [69946.556150] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:29:55 192.168.122.209 [69946.586513] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:29:55 192.168.122.209 [69946.637187] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:29:55 192.168.122.209 [69946.638916] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:29:56 192.168.122.209 [69946.685118] [tempesta fw] Tempesta FW is ready Apr 26 11:29:56 192.168.122.209 [69947.636937] [tdb] Close table 'client0.tdb' Apr 26 11:29:57 192.168.122.209 [69947.820870] [tdb] Close table 'sessions0.tdb' Apr 26 11:29:57 192.168.122.209 [69948.066603] [tdb] Close table 'filter0.tdb' Apr 26 11:29:57 192.168.122.209 [69948.067034] [tempesta fw] modules are stopped Apr 26 11:29:57 192.168.122.209 [69948.273238] [tempesta fw] exiting... Apr 26 11:29:57 192.168.122.209 [69948.408668] [tdb] Shutdown Tempesta DB Apr 26 11:29:58 192.168.122.209 [69948.778724] End test: cache.test_cache.TestCacheH2.test_disabled_cache_fulfill_suffix Apr 26 11:29:58 192.168.122.209 [69948.815269] Start test: cache.test_cache.TestCacheH2.test_disabled_cache_fulfill_suffix2 Apr 26 11:29:59 192.168.122.209 [69950.197697] [tdb] Start Tempesta DB Apr 26 11:29:59 192.168.122.209 [69950.331064] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:30:00 192.168.122.209 [69951.247069] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69951.247069] Maybe that's fine, but it's worth checking the [69951.247069] config - if there is no relations between the [69951.247069] names, then host name confusion attack is possible. Apr 26 11:30:01 192.168.122.209 [69952.373328] [tempesta fw] Configuration processing is completed. Apr 26 11:30:01 192.168.122.209 [69952.625176] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:30:01 192.168.122.209 [69952.654278] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:30:01 192.168.122.209 [69952.682694] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:30:02 192.168.122.209 [69953.281346] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:30:02 192.168.122.209 [69953.283116] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:30:03 192.168.122.209 [69953.725295] [tempesta fw] Tempesta FW is ready Apr 26 11:30:05 192.168.122.209 [69955.751954] [tdb] Close table 'client0.tdb' Apr 26 11:30:05 192.168.122.209 [69956.099677] [tdb] Close table 'sessions0.tdb' Apr 26 11:30:06 192.168.122.209 [69956.717522] [tdb] Close table 'filter0.tdb' Apr 26 11:30:06 192.168.122.209 [69956.717980] [tempesta fw] modules are stopped Apr 26 11:30:06 192.168.122.209 [69957.185581] [tempesta fw] exiting... Apr 26 11:30:06 192.168.122.209 [69957.334256] [tdb] Shutdown Tempesta DB Apr 26 11:30:07 192.168.122.209 [69957.728145] End test: cache.test_cache.TestCacheH2.test_disabled_cache_fulfill_suffix2 Apr 26 11:30:07 192.168.122.209 [69957.762711] Start test: cache.test_cache.TestCacheH2.test_replicated_cache_bypass_all Apr 26 11:30:08 192.168.122.209 [69959.130439] [tdb] Start Tempesta DB Apr 26 11:30:08 192.168.122.209 [69959.267441] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:30:09 192.168.122.209 [69959.874608] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69959.874608] Maybe that's fine, but it's worth checking the [69959.874608] config - if there is no relations between the [69959.874608] names, then host name confusion attack is possible. Apr 26 11:30:09 192.168.122.209 [69959.989373] [tempesta fw] Configuration processing is completed. Apr 26 11:30:09 192.168.122.209 [69960.042975] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:30:09 192.168.122.209 [69960.449851] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:30:09 192.168.122.209 [69960.481809] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:30:09 192.168.122.209 [69960.509664] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:30:09 192.168.122.209 [69960.553341] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:30:09 192.168.122.209 [69960.555067] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:30:09 192.168.122.209 [69960.593306] [tempesta fw] Tempesta FW is ready Apr 26 11:30:10 192.168.122.209 [69961.476696] [tdb] Close table 'client0.tdb' Apr 26 11:30:10 192.168.122.209 [69961.665283] [tdb] Close table 'sessions0.tdb' Apr 26 11:30:14 192.168.122.209 [69964.862548] [tdb] Close table 'cache0.tdb' Apr 26 11:30:14 192.168.122.209 [69965.106787] [tdb] Close table 'filter0.tdb' Apr 26 11:30:14 192.168.122.209 [69965.107222] [tempesta fw] modules are stopped Apr 26 11:30:14 192.168.122.209 [69965.299201] [tempesta fw] exiting... Apr 26 11:30:14 192.168.122.209 [69965.413561] [tdb] Shutdown Tempesta DB Apr 26 11:30:15 192.168.122.209 [69965.857833] End test: cache.test_cache.TestCacheH2.test_replicated_cache_bypass_all Apr 26 11:30:15 192.168.122.209 [69965.894627] Start test: cache.test_cache.TestCacheH2.test_replicated_cache_bypass_prefix Apr 26 11:30:16 192.168.122.209 [69967.264182] [tdb] Start Tempesta DB Apr 26 11:30:16 192.168.122.209 [69967.410853] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:30:18 192.168.122.209 [69968.918761] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69968.918761] Maybe that's fine, but it's worth checking the [69968.918761] config - if there is no relations between the [69968.918761] names, then host name confusion attack is possible. Apr 26 11:30:18 192.168.122.209 [69969.085496] [tempesta fw] Configuration processing is completed. Apr 26 11:30:18 192.168.122.209 [69969.143214] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:30:18 192.168.122.209 [69969.570872] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:30:18 192.168.122.209 [69969.596757] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:30:18 192.168.122.209 [69969.622195] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:30:18 192.168.122.209 [69969.673455] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:30:18 192.168.122.209 [69969.675000] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:30:19 192.168.122.209 [69969.713422] [tempesta fw] Tempesta FW is ready Apr 26 11:30:19 192.168.122.209 [69970.638049] [tdb] Close table 'client0.tdb' Apr 26 11:30:20 192.168.122.209 [69970.810888] [tdb] Close table 'sessions0.tdb' Apr 26 11:30:23 192.168.122.209 [69973.989137] [tdb] Close table 'cache0.tdb' Apr 26 11:30:23 192.168.122.209 [69974.265616] [tdb] Close table 'filter0.tdb' Apr 26 11:30:23 192.168.122.209 [69974.266044] [tempesta fw] modules are stopped Apr 26 11:30:23 192.168.122.209 [69974.470989] [tempesta fw] exiting... Apr 26 11:30:23 192.168.122.209 [69974.615235] [tdb] Shutdown Tempesta DB Apr 26 11:30:24 192.168.122.209 [69975.034665] End test: cache.test_cache.TestCacheH2.test_replicated_cache_bypass_prefix Apr 26 11:30:24 192.168.122.209 [69975.066348] Start test: cache.test_cache.TestCacheH2.test_replicated_cache_bypass_suffix Apr 26 11:30:25 192.168.122.209 [69976.474775] [tdb] Start Tempesta DB Apr 26 11:30:25 192.168.122.209 [69976.615699] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:30:27 192.168.122.209 [69978.106891] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69978.106891] Maybe that's fine, but it's worth checking the [69978.106891] config - if there is no relations between the [69978.106891] names, then host name confusion attack is possible. Apr 26 11:30:27 192.168.122.209 [69978.297595] [tempesta fw] Configuration processing is completed. Apr 26 11:30:27 192.168.122.209 [69978.348968] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:30:28 192.168.122.209 [69978.746676] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:30:28 192.168.122.209 [69978.771988] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:30:28 192.168.122.209 [69978.797559] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:30:28 192.168.122.209 [69978.837576] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:30:28 192.168.122.209 [69978.839288] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:30:28 192.168.122.209 [69978.877543] [tempesta fw] Tempesta FW is ready Apr 26 11:30:29 192.168.122.209 [69979.741549] [tdb] Close table 'client0.tdb' Apr 26 11:30:29 192.168.122.209 [69979.924419] [tdb] Close table 'sessions0.tdb' Apr 26 11:30:32 192.168.122.209 [69983.069108] [tdb] Close table 'cache0.tdb' Apr 26 11:30:32 192.168.122.209 [69983.356532] [tdb] Close table 'filter0.tdb' Apr 26 11:30:32 192.168.122.209 [69983.356969] [tempesta fw] modules are stopped Apr 26 11:30:32 192.168.122.209 [69983.585893] [tempesta fw] exiting... Apr 26 11:30:33 192.168.122.209 [69983.719207] [tdb] Shutdown Tempesta DB Apr 26 11:30:33 192.168.122.209 [69984.153348] End test: cache.test_cache.TestCacheH2.test_replicated_cache_bypass_suffix Apr 26 11:30:33 192.168.122.209 [69984.184911] Start test: cache.test_cache.TestCacheH2.test_replicated_cache_fulfill_all Apr 26 11:30:34 192.168.122.209 [69985.523435] [tdb] Start Tempesta DB Apr 26 11:30:34 192.168.122.209 [69985.646773] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:30:36 192.168.122.209 [69986.978676] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69986.978676] Maybe that's fine, but it's worth checking the [69986.978676] config - if there is no relations between the [69986.978676] names, then host name confusion attack is possible. Apr 26 11:30:36 192.168.122.209 [69987.105724] [tempesta fw] Configuration processing is completed. Apr 26 11:30:36 192.168.122.209 [69987.162171] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:30:36 192.168.122.209 [69987.589757] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:30:36 192.168.122.209 [69987.615225] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:30:36 192.168.122.209 [69987.640025] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:30:37 192.168.122.209 [69987.685722] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:30:37 192.168.122.209 [69987.687443] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:30:37 192.168.122.209 [69987.741658] [tempesta fw] Tempesta FW is ready Apr 26 11:30:37 192.168.122.209 [69988.610568] [tdb] Close table 'client0.tdb' Apr 26 11:30:38 192.168.122.209 [69988.788460] [tdb] Close table 'sessions0.tdb' Apr 26 11:30:41 192.168.122.209 [69991.984424] [tdb] Close table 'cache0.tdb' Apr 26 11:30:41 192.168.122.209 [69992.240959] [tdb] Close table 'filter0.tdb' Apr 26 11:30:41 192.168.122.209 [69992.241877] [tempesta fw] modules are stopped Apr 26 11:30:41 192.168.122.209 [69992.449154] [tempesta fw] exiting... Apr 26 11:30:41 192.168.122.209 [69992.618462] [tdb] Shutdown Tempesta DB Apr 26 11:30:42 192.168.122.209 [69992.954409] End test: cache.test_cache.TestCacheH2.test_replicated_cache_fulfill_all Apr 26 11:30:42 192.168.122.209 [69993.039605] Start test: cache.test_cache.TestCacheH2.test_replicated_cache_fulfill_prefix Apr 26 11:30:43 192.168.122.209 [69994.299910] [tdb] Start Tempesta DB Apr 26 11:30:43 192.168.122.209 [69994.432640] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:30:45 192.168.122.209 [69995.899297] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [69995.899297] Maybe that's fine, but it's worth checking the [69995.899297] config - if there is no relations between the [69995.899297] names, then host name confusion attack is possible. Apr 26 11:30:45 192.168.122.209 [69996.069828] [tempesta fw] Configuration processing is completed. Apr 26 11:30:45 192.168.122.209 [69996.123409] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:30:45 192.168.122.209 [69996.537463] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:30:45 192.168.122.209 [69996.578033] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:30:45 192.168.122.209 [69996.613524] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:30:45 192.168.122.209 [69996.665789] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:30:45 192.168.122.209 [69996.667196] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:30:46 192.168.122.209 [69996.713756] [tempesta fw] Tempesta FW is ready Apr 26 11:30:46 192.168.122.209 [69997.547281] [tdb] Close table 'client0.tdb' Apr 26 11:30:47 192.168.122.209 [69997.728552] [tdb] Close table 'sessions0.tdb' Apr 26 11:30:50 192.168.122.209 [70000.831531] [tdb] Close table 'cache0.tdb' Apr 26 11:30:50 192.168.122.209 [70001.110867] [tdb] Close table 'filter0.tdb' Apr 26 11:30:50 192.168.122.209 [70001.111306] [tempesta fw] modules are stopped Apr 26 11:30:50 192.168.122.209 [70001.293652] [tempesta fw] exiting... Apr 26 11:30:50 192.168.122.209 [70001.397852] [tdb] Shutdown Tempesta DB Apr 26 11:30:51 192.168.122.209 [70001.785840] End test: cache.test_cache.TestCacheH2.test_replicated_cache_fulfill_prefix Apr 26 11:30:51 192.168.122.209 [70001.823422] Start test: cache.test_cache.TestCacheH2.test_replicated_cache_fulfill_suffix Apr 26 11:30:52 192.168.122.209 [70003.207112] [tdb] Start Tempesta DB Apr 26 11:30:52 192.168.122.209 [70003.331271] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:30:54 192.168.122.209 [70004.799063] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70004.799063] Maybe that's fine, but it's worth checking the [70004.799063] config - if there is no relations between the [70004.799063] names, then host name confusion attack is possible. Apr 26 11:30:54 192.168.122.209 [70004.977958] [tempesta fw] Configuration processing is completed. Apr 26 11:30:54 192.168.122.209 [70005.045215] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:30:54 192.168.122.209 [70005.464372] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:30:54 192.168.122.209 [70005.489936] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:30:54 192.168.122.209 [70005.515611] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:30:54 192.168.122.209 [70005.557876] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:30:54 192.168.122.209 [70005.558982] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:30:54 192.168.122.209 [70005.609873] [tempesta fw] Tempesta FW is ready Apr 26 11:30:55 192.168.122.209 [70006.459314] [tdb] Close table 'client0.tdb' Apr 26 11:30:55 192.168.122.209 [70006.656815] [tdb] Close table 'sessions0.tdb' Apr 26 11:30:59 192.168.122.209 [70009.779361] [tdb] Close table 'cache0.tdb' Apr 26 11:30:59 192.168.122.209 [70010.027170] [tdb] Close table 'filter0.tdb' Apr 26 11:30:59 192.168.122.209 [70010.027675] [tempesta fw] modules are stopped Apr 26 11:30:59 192.168.122.209 [70010.234758] [tempesta fw] exiting... Apr 26 11:30:59 192.168.122.209 [70010.366890] [tdb] Shutdown Tempesta DB Apr 26 11:31:00 192.168.122.209 [70010.727084] End test: cache.test_cache.TestCacheH2.test_replicated_cache_fulfill_suffix Apr 26 11:31:00 192.168.122.209 [70010.810976] Start test: cache.test_cache.TestCacheH2.test_replicated_cache_fulfill_suffix2 Apr 26 11:31:01 192.168.122.209 [70012.172226] [tdb] Start Tempesta DB Apr 26 11:31:01 192.168.122.209 [70012.307864] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:31:03 192.168.122.209 [70013.695328] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70013.695328] Maybe that's fine, but it's worth checking the [70013.695328] config - if there is no relations between the [70013.695328] names, then host name confusion attack is possible. Apr 26 11:31:03 192.168.122.209 [70013.862057] [tempesta fw] Configuration processing is completed. Apr 26 11:31:03 192.168.122.209 [70013.912550] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:31:03 192.168.122.209 [70014.328723] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:31:03 192.168.122.209 [70014.367172] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:31:03 192.168.122.209 [70014.405444] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:31:03 192.168.122.209 [70014.482049] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:31:03 192.168.122.209 [70014.483808] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:31:03 192.168.122.209 [70014.529990] [tempesta fw] Tempesta FW is ready Apr 26 11:31:04 192.168.122.209 [70015.364875] [tdb] Close table 'client0.tdb' Apr 26 11:31:04 192.168.122.209 [70015.545991] [tdb] Close table 'sessions0.tdb' Apr 26 11:31:08 192.168.122.209 [70018.697187] [tdb] Close table 'cache0.tdb' Apr 26 11:31:08 192.168.122.209 [70018.933687] [tdb] Close table 'filter0.tdb' Apr 26 11:31:08 192.168.122.209 [70018.934150] [tempesta fw] modules are stopped Apr 26 11:31:08 192.168.122.209 [70019.167325] [tempesta fw] exiting... Apr 26 11:31:08 192.168.122.209 [70019.290444] [tdb] Shutdown Tempesta DB Apr 26 11:31:08 192.168.122.209 [70019.675047] End test: cache.test_cache.TestCacheH2.test_replicated_cache_fulfill_suffix2 Apr 26 11:31:09 192.168.122.209 [70019.759007] Start test: cache.test_cache.TestCacheH2.test_sharding_cache_bypass_all Apr 26 11:31:10 192.168.122.209 [70021.100629] [tdb] Start Tempesta DB Apr 26 11:31:10 192.168.122.209 [70021.217049] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:31:11 192.168.122.209 [70022.547529] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70022.547529] Maybe that's fine, but it's worth checking the [70022.547529] config - if there is no relations between the [70022.547529] names, then host name confusion attack is possible. Apr 26 11:31:11 192.168.122.209 [70022.662216] [tempesta fw] Configuration processing is completed. Apr 26 11:31:12 192.168.122.209 [70022.719366] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:31:12 192.168.122.209 [70023.152229] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:31:12 192.168.122.209 [70023.179660] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:31:12 192.168.122.209 [70023.206354] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:31:12 192.168.122.209 [70023.246184] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:31:12 192.168.122.209 [70023.247906] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:31:12 192.168.122.209 [70023.286155] [tempesta fw] Tempesta FW is ready Apr 26 11:31:13 192.168.122.209 [70024.208654] [tdb] Close table 'client0.tdb' Apr 26 11:31:13 192.168.122.209 [70024.393569] [tdb] Close table 'sessions0.tdb' Apr 26 11:31:16 192.168.122.209 [70027.629963] [tdb] Close table 'cache0.tdb' Apr 26 11:31:17 192.168.122.209 [70027.874866] [tdb] Close table 'filter0.tdb' Apr 26 11:31:17 192.168.122.209 [70027.875290] [tempesta fw] modules are stopped Apr 26 11:31:17 192.168.122.209 [70028.100851] [tempesta fw] exiting... Apr 26 11:31:17 192.168.122.209 [70028.223003] [tdb] Shutdown Tempesta DB Apr 26 11:31:17 192.168.122.209 [70028.619936] End test: cache.test_cache.TestCacheH2.test_sharding_cache_bypass_all Apr 26 11:31:17 192.168.122.209 [70028.656717] Start test: cache.test_cache.TestCacheH2.test_sharding_cache_bypass_prefix Apr 26 11:31:19 192.168.122.209 [70030.070025] [tdb] Start Tempesta DB Apr 26 11:31:19 192.168.122.209 [70030.210478] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:31:20 192.168.122.209 [70031.615705] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70031.615705] Maybe that's fine, but it's worth checking the [70031.615705] config - if there is no relations between the [70031.615705] names, then host name confusion attack is possible. Apr 26 11:31:21 192.168.122.209 [70031.778340] [tempesta fw] Configuration processing is completed. Apr 26 11:31:21 192.168.122.209 [70031.835785] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:31:21 192.168.122.209 [70032.237781] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:31:21 192.168.122.209 [70032.263249] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:31:21 192.168.122.209 [70032.288581] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:31:21 192.168.122.209 [70032.330304] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:31:21 192.168.122.209 [70032.332027] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:31:21 192.168.122.209 [70032.386249] [tempesta fw] Tempesta FW is ready Apr 26 11:31:22 192.168.122.209 [70033.291126] [tdb] Close table 'client0.tdb' Apr 26 11:31:22 192.168.122.209 [70033.499173] [tdb] Close table 'sessions0.tdb' Apr 26 11:31:25 192.168.122.209 [70036.636245] [tdb] Close table 'cache0.tdb' Apr 26 11:31:26 192.168.122.209 [70036.881306] [tdb] Close table 'filter0.tdb' Apr 26 11:31:26 192.168.122.209 [70036.881707] [tempesta fw] modules are stopped Apr 26 11:31:26 192.168.122.209 [70037.096052] [tempesta fw] exiting... Apr 26 11:31:26 192.168.122.209 [70037.224060] [tdb] Shutdown Tempesta DB Apr 26 11:31:26 192.168.122.209 [70037.593778] End test: cache.test_cache.TestCacheH2.test_sharding_cache_bypass_prefix Apr 26 11:31:26 192.168.122.209 [70037.628417] Start test: cache.test_cache.TestCacheH2.test_sharding_cache_bypass_suffix Apr 26 11:31:28 192.168.122.209 [70039.002560] [tdb] Start Tempesta DB Apr 26 11:31:28 192.168.122.209 [70039.139197] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:31:29 192.168.122.209 [70040.663644] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70040.663644] Maybe that's fine, but it's worth checking the [70040.663644] config - if there is no relations between the [70040.663644] names, then host name confusion attack is possible. Apr 26 11:31:30 192.168.122.209 [70040.830413] [tempesta fw] Configuration processing is completed. Apr 26 11:31:30 192.168.122.209 [70040.886995] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:31:30 192.168.122.209 [70041.308106] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:31:30 192.168.122.209 [70041.334183] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:31:30 192.168.122.209 [70041.359644] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:31:30 192.168.122.209 [70041.402397] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:31:30 192.168.122.209 [70041.404149] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:31:30 192.168.122.209 [70041.450340] [tempesta fw] Tempesta FW is ready Apr 26 11:31:31 192.168.122.209 [70042.274135] [tdb] Close table 'client0.tdb' Apr 26 11:31:31 192.168.122.209 [70042.457367] [tdb] Close table 'sessions0.tdb' Apr 26 11:31:34 192.168.122.209 [70045.591048] [tdb] Close table 'cache0.tdb' Apr 26 11:31:35 192.168.122.209 [70045.811948] [tdb] Close table 'filter0.tdb' Apr 26 11:31:35 192.168.122.209 [70045.812388] [tempesta fw] modules are stopped Apr 26 11:31:35 192.168.122.209 [70046.010031] [tempesta fw] exiting... Apr 26 11:31:35 192.168.122.209 [70046.139810] [tdb] Shutdown Tempesta DB Apr 26 11:31:35 192.168.122.209 [70046.593132] End test: cache.test_cache.TestCacheH2.test_sharding_cache_bypass_suffix Apr 26 11:31:35 192.168.122.209 [70046.622924] Start test: cache.test_cache.TestCacheH2.test_sharding_cache_fulfill_all Apr 26 11:31:37 192.168.122.209 [70048.044342] [tdb] Start Tempesta DB Apr 26 11:31:37 192.168.122.209 [70048.183440] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:31:38 192.168.122.209 [70049.555728] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70049.555728] Maybe that's fine, but it's worth checking the [70049.555728] config - if there is no relations between the [70049.555728] names, then host name confusion attack is possible. Apr 26 11:31:38 192.168.122.209 [70049.666550] [tempesta fw] Configuration processing is completed. Apr 26 11:31:39 192.168.122.209 [70049.719699] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:31:39 192.168.122.209 [70050.139869] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:31:39 192.168.122.209 [70050.167237] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:31:39 192.168.122.209 [70050.191743] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:31:39 192.168.122.209 [70050.234452] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:31:39 192.168.122.209 [70050.236168] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:31:39 192.168.122.209 [70050.274457] [tempesta fw] Tempesta FW is ready Apr 26 11:31:40 192.168.122.209 [70051.111351] [tdb] Close table 'client0.tdb' Apr 26 11:31:40 192.168.122.209 [70051.287649] [tdb] Close table 'sessions0.tdb' Apr 26 11:31:43 192.168.122.209 [70054.440312] [tdb] Close table 'cache0.tdb' Apr 26 11:31:44 192.168.122.209 [70054.710430] [tdb] Close table 'filter0.tdb' Apr 26 11:31:44 192.168.122.209 [70054.710882] [tempesta fw] modules are stopped Apr 26 11:31:44 192.168.122.209 [70054.882486] [tempesta fw] exiting... Apr 26 11:31:44 192.168.122.209 [70055.019403] [tdb] Shutdown Tempesta DB Apr 26 11:31:44 192.168.122.209 [70055.451224] End test: cache.test_cache.TestCacheH2.test_sharding_cache_fulfill_all Apr 26 11:31:44 192.168.122.209 [70055.483932] Start test: cache.test_cache.TestCacheH2.test_sharding_cache_fulfill_prefix Apr 26 11:31:46 192.168.122.209 [70056.888315] [tdb] Start Tempesta DB Apr 26 11:31:46 192.168.122.209 [70057.026802] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:31:47 192.168.122.209 [70058.483861] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70058.483861] Maybe that's fine, but it's worth checking the [70058.483861] config - if there is no relations between the [70058.483861] names, then host name confusion attack is possible. Apr 26 11:31:47 192.168.122.209 [70058.646709] [tempesta fw] Configuration processing is completed. Apr 26 11:31:48 192.168.122.209 [70058.701571] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:31:48 192.168.122.209 [70059.130070] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:31:48 192.168.122.209 [70059.156176] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:31:48 192.168.122.209 [70059.182654] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:31:48 192.168.122.209 [70059.234640] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:31:48 192.168.122.209 [70059.236393] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:31:48 192.168.122.209 [70059.286581] [tempesta fw] Tempesta FW is ready Apr 26 11:31:49 192.168.122.209 [70060.180616] [tdb] Close table 'client0.tdb' Apr 26 11:31:49 192.168.122.209 [70060.359288] [tdb] Close table 'sessions0.tdb' Apr 26 11:31:52 192.168.122.209 [70063.530520] [tdb] Close table 'cache0.tdb' Apr 26 11:31:53 192.168.122.209 [70063.759166] [tdb] Close table 'filter0.tdb' Apr 26 11:31:53 192.168.122.209 [70063.759582] [tempesta fw] modules are stopped Apr 26 11:31:53 192.168.122.209 [70063.956819] [tempesta fw] exiting... Apr 26 11:31:53 192.168.122.209 [70064.104468] [tdb] Shutdown Tempesta DB Apr 26 11:31:53 192.168.122.209 [70064.497493] End test: cache.test_cache.TestCacheH2.test_sharding_cache_fulfill_prefix Apr 26 11:31:53 192.168.122.209 [70064.530923] Start test: cache.test_cache.TestCacheH2.test_sharding_cache_fulfill_suffix Apr 26 11:31:55 192.168.122.209 [70065.943521] [tdb] Start Tempesta DB Apr 26 11:31:55 192.168.122.209 [70066.060191] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:31:56 192.168.122.209 [70067.496081] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70067.496081] Maybe that's fine, but it's worth checking the [70067.496081] config - if there is no relations between the [70067.496081] names, then host name confusion attack is possible. Apr 26 11:31:56 192.168.122.209 [70067.666802] [tempesta fw] Configuration processing is completed. Apr 26 11:31:57 192.168.122.209 [70067.727057] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:31:57 192.168.122.209 [70068.144779] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:31:57 192.168.122.209 [70068.170425] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:31:57 192.168.122.209 [70068.195601] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:31:57 192.168.122.209 [70068.234763] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:31:57 192.168.122.209 [70068.236493] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:31:57 192.168.122.209 [70068.274719] [tempesta fw] Tempesta FW is ready Apr 26 11:31:58 192.168.122.209 [70069.183694] [tdb] Close table 'client0.tdb' Apr 26 11:31:58 192.168.122.209 [70069.392525] [tdb] Close table 'sessions0.tdb' Apr 26 11:32:01 192.168.122.209 [70072.585334] [tdb] Close table 'cache0.tdb' Apr 26 11:32:02 192.168.122.209 [70072.851877] [tdb] Close table 'filter0.tdb' Apr 26 11:32:02 192.168.122.209 [70072.852293] [tempesta fw] modules are stopped Apr 26 11:32:02 192.168.122.209 [70073.023706] [tempesta fw] exiting... Apr 26 11:32:02 192.168.122.209 [70073.144958] [tdb] Shutdown Tempesta DB Apr 26 11:32:02 192.168.122.209 [70073.509011] End test: cache.test_cache.TestCacheH2.test_sharding_cache_fulfill_suffix Apr 26 11:32:02 192.168.122.209 [70073.536539] Start test: cache.test_cache.TestCacheH2.test_sharding_cache_fulfill_suffix2 Apr 26 11:32:04 192.168.122.209 [70074.853862] [tdb] Start Tempesta DB Apr 26 11:32:04 192.168.122.209 [70074.988654] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:32:05 192.168.122.209 [70076.416105] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70076.416105] Maybe that's fine, but it's worth checking the [70076.416105] config - if there is no relations between the [70076.416105] names, then host name confusion attack is possible. Apr 26 11:32:05 192.168.122.209 [70076.590890] [tempesta fw] Configuration processing is completed. Apr 26 11:32:05 192.168.122.209 [70076.647930] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:32:06 192.168.122.209 [70077.065646] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:32:06 192.168.122.209 [70077.091246] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:32:06 192.168.122.209 [70077.116449] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:32:06 192.168.122.209 [70077.158860] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:32:06 192.168.122.209 [70077.160583] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:32:06 192.168.122.209 [70077.210833] [tempesta fw] Tempesta FW is ready Apr 26 11:32:07 192.168.122.209 [70078.091334] [tdb] Close table 'client0.tdb' Apr 26 11:32:07 192.168.122.209 [70078.290535] [tdb] Close table 'sessions0.tdb' Apr 26 11:32:10 192.168.122.209 [70081.470788] [tdb] Close table 'cache0.tdb' Apr 26 11:32:11 192.168.122.209 [70081.725726] [tdb] Close table 'filter0.tdb' Apr 26 11:32:11 192.168.122.209 [70081.726128] [tempesta fw] modules are stopped Apr 26 11:32:11 192.168.122.209 [70081.918981] [tempesta fw] exiting... Apr 26 11:32:11 192.168.122.209 [70082.048400] [tdb] Shutdown Tempesta DB Apr 26 11:32:11 192.168.122.209 [70082.472786] End test: cache.test_cache.TestCacheH2.test_sharding_cache_fulfill_suffix2 Apr 26 11:32:11 192.168.122.209 [70082.501045] Start test: cache.test_cache.TestCacheHttp.test_cache_date Apr 26 11:32:13 192.168.122.209 [70083.926258] [tdb] Start Tempesta DB Apr 26 11:32:13 192.168.122.209 [70084.068048] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:32:14 192.168.122.209 [70085.604259] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70085.604259] Maybe that's fine, but it's worth checking the [70085.604259] config - if there is no relations between the [70085.604259] names, then host name confusion attack is possible. Apr 26 11:32:15 192.168.122.209 [70085.767111] [tempesta fw] Configuration processing is completed. Apr 26 11:32:15 192.168.122.209 [70085.825909] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:32:15 192.168.122.209 [70086.250650] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:32:15 192.168.122.209 [70086.276365] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:32:15 192.168.122.209 [70086.301478] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:32:15 192.168.122.209 [70086.350981] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:32:15 192.168.122.209 [70086.352727] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:32:15 192.168.122.209 [70086.390925] [tempesta fw] Tempesta FW is ready Apr 26 11:32:16 192.168.122.209 [70087.166173] [tdb] Close table 'client0.tdb' Apr 26 11:32:16 192.168.122.209 [70087.356815] [tdb] Close table 'sessions0.tdb' Apr 26 11:32:19 192.168.122.209 [70090.510321] [tdb] Close table 'cache0.tdb' Apr 26 11:32:20 192.168.122.209 [70090.740776] [tdb] Close table 'filter0.tdb' Apr 26 11:32:20 192.168.122.209 [70090.741208] [tempesta fw] modules are stopped Apr 26 11:32:20 192.168.122.209 [70090.958420] [tempesta fw] exiting... Apr 26 11:32:20 192.168.122.209 [70091.099805] [tdb] Shutdown Tempesta DB Apr 26 11:32:20 192.168.122.209 [70091.467992] End test: cache.test_cache.TestCacheHttp.test_cache_date Apr 26 11:32:20 192.168.122.209 [70091.544617] Start test: cache.test_cache.TestCacheHttp.test_disabled_cache_bypass_all Apr 26 11:32:22 192.168.122.209 [70092.917254] [tdb] Start Tempesta DB Apr 26 11:32:22 192.168.122.209 [70093.058414] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:32:23 192.168.122.209 [70094.436390] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70094.436390] Maybe that's fine, but it's worth checking the [70094.436390] config - if there is no relations between the [70094.436390] names, then host name confusion attack is possible. Apr 26 11:32:23 192.168.122.209 [70094.551190] [tempesta fw] Configuration processing is completed. Apr 26 11:32:23 192.168.122.209 [70094.607594] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:32:23 192.168.122.209 [70094.639140] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:32:23 192.168.122.209 [70094.669841] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:32:24 192.168.122.209 [70094.731094] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:32:24 192.168.122.209 [70094.732853] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:32:24 192.168.122.209 [70094.770953] [tempesta fw] Tempesta FW is ready Apr 26 11:32:24 192.168.122.209 [70095.537869] [tdb] Close table 'client0.tdb' Apr 26 11:32:25 192.168.122.209 [70095.716866] [tdb] Close table 'sessions0.tdb' Apr 26 11:32:25 192.168.122.209 [70095.972006] [tdb] Close table 'filter0.tdb' Apr 26 11:32:25 192.168.122.209 [70095.972422] [tempesta fw] modules are stopped Apr 26 11:32:25 192.168.122.209 [70096.160754] [tempesta fw] exiting... Apr 26 11:32:25 192.168.122.209 [70096.306320] [tdb] Shutdown Tempesta DB Apr 26 11:32:25 192.168.122.209 [70096.665215] End test: cache.test_cache.TestCacheHttp.test_disabled_cache_bypass_all Apr 26 11:32:26 192.168.122.209 [70096.699995] Start test: cache.test_cache.TestCacheHttp.test_disabled_cache_bypass_prefix Apr 26 11:32:27 192.168.122.209 [70098.040096] [tdb] Start Tempesta DB Apr 26 11:32:27 192.168.122.209 [70098.183979] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:32:28 192.168.122.209 [70098.901370] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70098.901370] Maybe that's fine, but it's worth checking the [70098.901370] config - if there is no relations between the [70098.901370] names, then host name confusion attack is possible. Apr 26 11:32:28 192.168.122.209 [70099.067170] [tempesta fw] Configuration processing is completed. Apr 26 11:32:28 192.168.122.209 [70099.118192] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:32:28 192.168.122.209 [70099.147108] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:32:28 192.168.122.209 [70099.177476] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:32:28 192.168.122.209 [70099.247166] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:32:28 192.168.122.209 [70099.248915] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:32:28 192.168.122.209 [70099.287123] [tempesta fw] Tempesta FW is ready Apr 26 11:32:29 192.168.122.209 [70100.113395] [tdb] Close table 'client0.tdb' Apr 26 11:32:29 192.168.122.209 [70100.310538] [tdb] Close table 'sessions0.tdb' Apr 26 11:32:29 192.168.122.209 [70100.560222] [tdb] Close table 'filter0.tdb' Apr 26 11:32:29 192.168.122.209 [70100.560688] [tempesta fw] modules are stopped Apr 26 11:32:30 192.168.122.209 [70100.739285] [tempesta fw] exiting... Apr 26 11:32:30 192.168.122.209 [70100.880016] [tdb] Shutdown Tempesta DB Apr 26 11:32:30 192.168.122.209 [70101.228487] End test: cache.test_cache.TestCacheHttp.test_disabled_cache_bypass_prefix Apr 26 11:32:30 192.168.122.209 [70101.311084] Start test: cache.test_cache.TestCacheHttp.test_disabled_cache_bypass_suffix Apr 26 11:32:32 192.168.122.209 [70102.709219] [tdb] Start Tempesta DB Apr 26 11:32:32 192.168.122.209 [70102.835033] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:32:32 192.168.122.209 [70103.564552] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70103.564552] Maybe that's fine, but it's worth checking the [70103.564552] config - if there is no relations between the [70103.564552] names, then host name confusion attack is possible. Apr 26 11:32:33 192.168.122.209 [70103.735226] [tempesta fw] Configuration processing is completed. Apr 26 11:32:33 192.168.122.209 [70103.789548] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:32:33 192.168.122.209 [70103.817212] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:32:33 192.168.122.209 [70103.844768] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:32:33 192.168.122.209 [70103.891207] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:32:33 192.168.122.209 [70103.892941] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:32:33 192.168.122.209 [70103.943169] [tempesta fw] Tempesta FW is ready Apr 26 11:32:34 192.168.122.209 [70104.714922] [tdb] Close table 'client0.tdb' Apr 26 11:32:34 192.168.122.209 [70104.902706] [tdb] Close table 'sessions0.tdb' Apr 26 11:32:34 192.168.122.209 [70105.158358] [tdb] Close table 'filter0.tdb' Apr 26 11:32:34 192.168.122.209 [70105.158796] [tempesta fw] modules are stopped Apr 26 11:32:34 192.168.122.209 [70105.352292] [tempesta fw] exiting... Apr 26 11:32:34 192.168.122.209 [70105.482003] [tdb] Shutdown Tempesta DB Apr 26 11:32:35 192.168.122.209 [70105.877117] End test: cache.test_cache.TestCacheHttp.test_disabled_cache_bypass_suffix Apr 26 11:32:35 192.168.122.209 [70105.960733] Start test: cache.test_cache.TestCacheHttp.test_disabled_cache_fulfill_all Apr 26 11:32:36 192.168.122.209 [70107.421861] [tdb] Start Tempesta DB Apr 26 11:32:36 192.168.122.209 [70107.553255] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:32:37 192.168.122.209 [70108.208614] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70108.208614] Maybe that's fine, but it's worth checking the [70108.208614] config - if there is no relations between the [70108.208614] names, then host name confusion attack is possible. Apr 26 11:32:37 192.168.122.209 [70108.335301] [tempesta fw] Configuration processing is completed. Apr 26 11:32:37 192.168.122.209 [70108.387167] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:32:37 192.168.122.209 [70108.415565] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:32:37 192.168.122.209 [70108.443685] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:32:37 192.168.122.209 [70108.495314] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:32:37 192.168.122.209 [70108.497043] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:32:37 192.168.122.209 [70108.543255] [tempesta fw] Tempesta FW is ready Apr 26 11:32:38 192.168.122.209 [70109.338432] [tdb] Close table 'client0.tdb' Apr 26 11:32:38 192.168.122.209 [70109.525794] [tdb] Close table 'sessions0.tdb' Apr 26 11:32:39 192.168.122.209 [70109.784023] [tdb] Close table 'filter0.tdb' Apr 26 11:32:39 192.168.122.209 [70109.784432] [tempesta fw] modules are stopped Apr 26 11:32:39 192.168.122.209 [70109.972077] [tempesta fw] exiting... Apr 26 11:32:39 192.168.122.209 [70110.126046] [tdb] Shutdown Tempesta DB Apr 26 11:32:39 192.168.122.209 [70110.528225] End test: cache.test_cache.TestCacheHttp.test_disabled_cache_fulfill_all Apr 26 11:32:39 192.168.122.209 [70110.565989] Start test: cache.test_cache.TestCacheHttp.test_disabled_cache_fulfill_prefix Apr 26 11:32:41 192.168.122.209 [70111.927400] [tdb] Start Tempesta DB Apr 26 11:32:41 192.168.122.209 [70112.056329] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:32:42 192.168.122.209 [70112.748620] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70112.748620] Maybe that's fine, but it's worth checking the [70112.748620] config - if there is no relations between the [70112.748620] names, then host name confusion attack is possible. Apr 26 11:32:42 192.168.122.209 [70112.923535] [tempesta fw] Configuration processing is completed. Apr 26 11:32:42 192.168.122.209 [70112.988237] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:32:42 192.168.122.209 [70113.018958] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:32:42 192.168.122.209 [70113.048943] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:32:42 192.168.122.209 [70113.091341] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:32:42 192.168.122.209 [70113.093089] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:32:42 192.168.122.209 [70113.151292] [tempesta fw] Tempesta FW is ready Apr 26 11:32:43 192.168.122.209 [70113.936509] [tdb] Close table 'client0.tdb' Apr 26 11:32:43 192.168.122.209 [70114.112706] [tdb] Close table 'sessions0.tdb' Apr 26 11:32:43 192.168.122.209 [70114.385274] [tdb] Close table 'filter0.tdb' Apr 26 11:32:43 192.168.122.209 [70114.385793] [tempesta fw] modules are stopped Apr 26 11:32:43 192.168.122.209 [70114.596414] [tempesta fw] exiting... Apr 26 11:32:44 192.168.122.209 [70114.705069] [tdb] Shutdown Tempesta DB Apr 26 11:32:44 192.168.122.209 [70115.168747] End test: cache.test_cache.TestCacheHttp.test_disabled_cache_fulfill_prefix Apr 26 11:32:44 192.168.122.209 [70115.204373] Start test: cache.test_cache.TestCacheHttp.test_disabled_cache_fulfill_suffix Apr 26 11:32:45 192.168.122.209 [70116.687885] [tdb] Start Tempesta DB Apr 26 11:32:46 192.168.122.209 [70116.820158] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:32:46 192.168.122.209 [70117.532679] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70117.532679] Maybe that's fine, but it's worth checking the [70117.532679] config - if there is no relations between the [70117.532679] names, then host name confusion attack is possible. Apr 26 11:32:47 192.168.122.209 [70117.711432] [tempesta fw] Configuration processing is completed. Apr 26 11:32:47 192.168.122.209 [70117.766243] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:32:47 192.168.122.209 [70117.793223] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:32:47 192.168.122.209 [70117.820034] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:32:47 192.168.122.209 [70117.871413] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:32:47 192.168.122.209 [70117.873158] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:32:47 192.168.122.209 [70117.915351] [tempesta fw] Tempesta FW is ready Apr 26 11:32:47 192.168.122.209 [70118.676922] [tdb] Close table 'client0.tdb' Apr 26 11:32:48 192.168.122.209 [70118.860563] [tdb] Close table 'sessions0.tdb' Apr 26 11:32:48 192.168.122.209 [70119.089391] [tdb] Close table 'filter0.tdb' Apr 26 11:32:48 192.168.122.209 [70119.089824] [tempesta fw] modules are stopped Apr 26 11:32:48 192.168.122.209 [70119.282461] [tempesta fw] exiting... Apr 26 11:32:48 192.168.122.209 [70119.400018] [tdb] Shutdown Tempesta DB Apr 26 11:32:49 192.168.122.209 [70119.842874] End test: cache.test_cache.TestCacheHttp.test_disabled_cache_fulfill_suffix Apr 26 11:32:49 192.168.122.209 [70119.878742] Start test: cache.test_cache.TestCacheHttp.test_disabled_cache_fulfill_suffix2 Apr 26 11:32:50 192.168.122.209 [70121.298905] [tdb] Start Tempesta DB Apr 26 11:32:50 192.168.122.209 [70121.432512] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:32:51 192.168.122.209 [70122.144698] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70122.144698] Maybe that's fine, but it's worth checking the [70122.144698] config - if there is no relations between the [70122.144698] names, then host name confusion attack is possible. Apr 26 11:32:51 192.168.122.209 [70122.303480] [tempesta fw] Configuration processing is completed. Apr 26 11:32:51 192.168.122.209 [70122.353761] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:32:51 192.168.122.209 [70122.382828] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 11:32:51 192.168.122.209 [70122.410264] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 11:32:51 192.168.122.209 [70122.463405] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:32:51 192.168.122.209 [70122.465129] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:32:51 192.168.122.209 [70122.511401] [tempesta fw] Tempesta FW is ready Apr 26 11:32:52 192.168.122.209 [70123.255512] [tdb] Close table 'client0.tdb' Apr 26 11:32:52 192.168.122.209 [70123.441621] [tdb] Close table 'sessions0.tdb' Apr 26 11:32:52 192.168.122.209 [70123.658340] [tdb] Close table 'filter0.tdb' Apr 26 11:32:52 192.168.122.209 [70123.658755] [tempesta fw] modules are stopped Apr 26 11:32:53 192.168.122.209 [70123.843132] [tempesta fw] exiting... Apr 26 11:32:53 192.168.122.209 [70123.995435] [tdb] Shutdown Tempesta DB Apr 26 11:32:53 192.168.122.209 [70124.393406] End test: cache.test_cache.TestCacheHttp.test_disabled_cache_fulfill_suffix2 Apr 26 11:32:53 192.168.122.209 [70124.429906] Start test: cache.test_cache.TestCacheHttp.test_replicated_cache_bypass_all Apr 26 11:32:55 192.168.122.209 [70125.837758] [tdb] Start Tempesta DB Apr 26 11:32:55 192.168.122.209 [70125.963137] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:32:55 192.168.122.209 [70126.608502] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70126.608502] Maybe that's fine, but it's worth checking the [70126.608502] config - if there is no relations between the [70126.608502] names, then host name confusion attack is possible. Apr 26 11:32:56 192.168.122.209 [70126.739583] [tempesta fw] Configuration processing is completed. Apr 26 11:32:56 192.168.122.209 [70126.797276] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:32:56 192.168.122.209 [70127.214272] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:32:56 192.168.122.209 [70127.244051] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:32:56 192.168.122.209 [70127.273328] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:32:56 192.168.122.209 [70127.311511] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:32:56 192.168.122.209 [70127.313281] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:32:56 192.168.122.209 [70127.359477] [tempesta fw] Tempesta FW is ready Apr 26 11:32:57 192.168.122.209 [70128.160064] [tdb] Close table 'client0.tdb' Apr 26 11:32:57 192.168.122.209 [70128.339236] [tdb] Close table 'sessions0.tdb' Apr 26 11:33:00 192.168.122.209 [70131.493416] [tdb] Close table 'cache0.tdb' Apr 26 11:33:01 192.168.122.209 [70131.738120] [tdb] Close table 'filter0.tdb' Apr 26 11:33:01 192.168.122.209 [70131.738549] [tempesta fw] modules are stopped Apr 26 11:33:01 192.168.122.209 [70132.037244] [tempesta fw] exiting... Apr 26 11:33:01 192.168.122.209 [70132.182658] [tdb] Shutdown Tempesta DB Apr 26 11:33:01 192.168.122.209 [70132.585992] End test: cache.test_cache.TestCacheHttp.test_replicated_cache_bypass_all Apr 26 11:33:01 192.168.122.209 [70132.611992] Start test: cache.test_cache.TestCacheHttp.test_replicated_cache_bypass_prefix Apr 26 11:33:03 192.168.122.209 [70133.895914] [tdb] Start Tempesta DB Apr 26 11:33:03 192.168.122.209 [70134.017171] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:33:04 192.168.122.209 [70135.488935] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70135.488935] Maybe that's fine, but it's worth checking the [70135.488935] config - if there is no relations between the [70135.488935] names, then host name confusion attack is possible. Apr 26 11:33:04 192.168.122.209 [70135.667746] [tempesta fw] Configuration processing is completed. Apr 26 11:33:05 192.168.122.209 [70135.724889] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:33:05 192.168.122.209 [70136.164544] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:33:05 192.168.122.209 [70136.191328] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:33:05 192.168.122.209 [70136.217419] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:33:05 192.168.122.209 [70136.275644] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:33:05 192.168.122.209 [70136.277385] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:33:05 192.168.122.209 [70136.319588] [tempesta fw] Tempesta FW is ready Apr 26 11:33:06 192.168.122.209 [70137.141299] [tdb] Close table 'client0.tdb' Apr 26 11:33:06 192.168.122.209 [70137.328458] [tdb] Close table 'sessions0.tdb' Apr 26 11:33:09 192.168.122.209 [70140.498993] [tdb] Close table 'cache0.tdb' Apr 26 11:33:10 192.168.122.209 [70140.753057] [tdb] Close table 'filter0.tdb' Apr 26 11:33:10 192.168.122.209 [70140.753460] [tempesta fw] modules are stopped Apr 26 11:33:10 192.168.122.209 [70140.945031] [tempesta fw] exiting... Apr 26 11:33:10 192.168.122.209 [70141.056816] [tdb] Shutdown Tempesta DB Apr 26 11:33:10 192.168.122.209 [70141.461486] End test: cache.test_cache.TestCacheHttp.test_replicated_cache_bypass_prefix Apr 26 11:33:10 192.168.122.209 [70141.497461] Start test: cache.test_cache.TestCacheHttp.test_replicated_cache_bypass_suffix Apr 26 11:33:12 192.168.122.209 [70142.952220] [tdb] Start Tempesta DB Apr 26 11:33:12 192.168.122.209 [70143.085974] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:33:13 192.168.122.209 [70144.597071] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70144.597071] Maybe that's fine, but it's worth checking the [70144.597071] config - if there is no relations between the [70144.597071] names, then host name confusion attack is possible. Apr 26 11:33:14 192.168.122.209 [70144.763763] [tempesta fw] Configuration processing is completed. Apr 26 11:33:14 192.168.122.209 [70144.825053] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:33:14 192.168.122.209 [70145.252155] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:33:14 192.168.122.209 [70145.280644] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:33:14 192.168.122.209 [70145.306855] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:33:14 192.168.122.209 [70145.363773] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:33:14 192.168.122.209 [70145.365509] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:33:14 192.168.122.209 [70145.407703] [tempesta fw] Tempesta FW is ready Apr 26 11:33:15 192.168.122.209 [70146.197745] [tdb] Close table 'client0.tdb' Apr 26 11:33:15 192.168.122.209 [70146.381584] [tdb] Close table 'sessions0.tdb' Apr 26 11:33:18 192.168.122.209 [70149.590585] [tdb] Close table 'cache0.tdb' Apr 26 11:33:19 192.168.122.209 [70149.847950] [tdb] Close table 'filter0.tdb' Apr 26 11:33:19 192.168.122.209 [70149.848371] [tempesta fw] modules are stopped Apr 26 11:33:19 192.168.122.209 [70150.056626] [tempesta fw] exiting... Apr 26 11:33:19 192.168.122.209 [70150.183943] [tdb] Shutdown Tempesta DB Apr 26 11:33:19 192.168.122.209 [70150.630329] End test: cache.test_cache.TestCacheHttp.test_replicated_cache_bypass_suffix Apr 26 11:33:19 192.168.122.209 [70150.663540] Start test: cache.test_cache.TestCacheHttp.test_replicated_cache_fulfill_all Apr 26 11:33:21 192.168.122.209 [70152.093326] [tdb] Start Tempesta DB Apr 26 11:33:21 192.168.122.209 [70152.224855] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:33:22 192.168.122.209 [70153.545174] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70153.545174] Maybe that's fine, but it's worth checking the [70153.545174] config - if there is no relations between the [70153.545174] names, then host name confusion attack is possible. Apr 26 11:33:22 192.168.122.209 [70153.655905] [tempesta fw] Configuration processing is completed. Apr 26 11:33:23 192.168.122.209 [70153.712185] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:33:23 192.168.122.209 [70154.127385] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:33:23 192.168.122.209 [70154.152806] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:33:23 192.168.122.209 [70154.177722] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:33:23 192.168.122.209 [70154.215873] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:33:23 192.168.122.209 [70154.217603] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:33:23 192.168.122.209 [70154.255814] [tempesta fw] Tempesta FW is ready Apr 26 11:33:24 192.168.122.209 [70155.104807] [tdb] Close table 'client0.tdb' Apr 26 11:33:24 192.168.122.209 [70155.289228] [tdb] Close table 'sessions0.tdb' Apr 26 11:33:27 192.168.122.209 [70158.434827] [tdb] Close table 'cache0.tdb' Apr 26 11:33:27 192.168.122.209 [70158.669410] [tdb] Close table 'filter0.tdb' Apr 26 11:33:27 192.168.122.209 [70158.669808] [tempesta fw] modules are stopped Apr 26 11:33:28 192.168.122.209 [70158.848367] [tempesta fw] exiting... Apr 26 11:33:28 192.168.122.209 [70158.991373] [tdb] Shutdown Tempesta DB Apr 26 11:33:28 192.168.122.209 [70159.387925] End test: cache.test_cache.TestCacheHttp.test_replicated_cache_fulfill_all Apr 26 11:33:28 192.168.122.209 [70159.419297] Start test: cache.test_cache.TestCacheHttp.test_replicated_cache_fulfill_prefix Apr 26 11:33:30 192.168.122.209 [70160.737395] [tdb] Start Tempesta DB Apr 26 11:33:30 192.168.122.209 [70160.872314] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:33:31 192.168.122.209 [70162.288786] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70162.288786] Maybe that's fine, but it's worth checking the [70162.288786] config - if there is no relations between the [70162.288786] names, then host name confusion attack is possible. Apr 26 11:33:31 192.168.122.209 [70162.460004] [tempesta fw] Configuration processing is completed. Apr 26 11:33:31 192.168.122.209 [70162.511251] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:33:32 192.168.122.209 [70162.926465] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:33:32 192.168.122.209 [70162.953957] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:33:32 192.168.122.209 [70162.979147] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:33:32 192.168.122.209 [70163.016016] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:33:32 192.168.122.209 [70163.017752] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:33:32 192.168.122.209 [70163.063936] [tempesta fw] Tempesta FW is ready Apr 26 11:33:33 192.168.122.209 [70163.843005] [tdb] Close table 'client0.tdb' Apr 26 11:33:33 192.168.122.209 [70164.025426] [tdb] Close table 'sessions0.tdb' Apr 26 11:33:36 192.168.122.209 [70167.190456] [tdb] Close table 'cache0.tdb' Apr 26 11:33:36 192.168.122.209 [70167.440896] [tdb] Close table 'filter0.tdb' Apr 26 11:33:36 192.168.122.209 [70167.441325] [tempesta fw] modules are stopped Apr 26 11:33:36 192.168.122.209 [70167.616477] [tempesta fw] exiting... Apr 26 11:33:37 192.168.122.209 [70167.740859] [tdb] Shutdown Tempesta DB Apr 26 11:33:37 192.168.122.209 [70168.143664] End test: cache.test_cache.TestCacheHttp.test_replicated_cache_fulfill_prefix Apr 26 11:33:37 192.168.122.209 [70168.181183] Start test: cache.test_cache.TestCacheHttp.test_replicated_cache_fulfill_suffix Apr 26 11:33:38 192.168.122.209 [70169.513586] [tdb] Start Tempesta DB Apr 26 11:33:38 192.168.122.209 [70169.644873] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:33:40 192.168.122.209 [70171.153358] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70171.153358] Maybe that's fine, but it's worth checking the [70171.153358] config - if there is no relations between the [70171.153358] names, then host name confusion attack is possible. Apr 26 11:33:40 192.168.122.209 [70171.336144] [tempesta fw] Configuration processing is completed. Apr 26 11:33:40 192.168.122.209 [70171.393969] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:33:41 192.168.122.209 [70171.808849] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:33:41 192.168.122.209 [70171.834309] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:33:41 192.168.122.209 [70171.861004] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:33:41 192.168.122.209 [70171.908135] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:33:41 192.168.122.209 [70171.909853] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:33:41 192.168.122.209 [70171.956056] [tempesta fw] Tempesta FW is ready Apr 26 11:33:42 192.168.122.209 [70172.784093] [tdb] Close table 'client0.tdb' Apr 26 11:33:42 192.168.122.209 [70172.979563] [tdb] Close table 'sessions0.tdb' Apr 26 11:33:45 192.168.122.209 [70176.123764] [tdb] Close table 'cache0.tdb' Apr 26 11:33:45 192.168.122.209 [70176.380857] [tdb] Close table 'filter0.tdb' Apr 26 11:33:45 192.168.122.209 [70176.381361] [tempesta fw] modules are stopped Apr 26 11:33:45 192.168.122.209 [70176.564605] [tempesta fw] exiting... Apr 26 11:33:46 192.168.122.209 [70176.696902] [tdb] Shutdown Tempesta DB Apr 26 11:33:46 192.168.122.209 [70177.074052] End test: cache.test_cache.TestCacheHttp.test_replicated_cache_fulfill_suffix Apr 26 11:33:46 192.168.122.209 [70177.113914] Start test: cache.test_cache.TestCacheHttp.test_replicated_cache_fulfill_suffix2 Apr 26 11:33:47 192.168.122.209 [70178.519185] [tdb] Start Tempesta DB Apr 26 11:33:47 192.168.122.209 [70178.641790] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:33:49 192.168.122.209 [70180.089515] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70180.089515] Maybe that's fine, but it's worth checking the [70180.089515] config - if there is no relations between the [70180.089515] names, then host name confusion attack is possible. Apr 26 11:33:49 192.168.122.209 [70180.260224] [tempesta fw] Configuration processing is completed. Apr 26 11:33:49 192.168.122.209 [70180.310513] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:33:50 192.168.122.209 [70180.734651] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:33:50 192.168.122.209 [70180.760706] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:33:50 192.168.122.209 [70180.786297] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:33:50 192.168.122.209 [70180.836237] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:33:50 192.168.122.209 [70180.837817] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:33:50 192.168.122.209 [70180.884192] [tempesta fw] Tempesta FW is ready Apr 26 11:33:50 192.168.122.209 [70181.591896] [tdb] Close table 'client0.tdb' Apr 26 11:33:51 192.168.122.209 [70181.766048] [tdb] Close table 'sessions0.tdb' Apr 26 11:33:54 192.168.122.209 [70184.892860] [tdb] Close table 'cache0.tdb' Apr 26 11:33:54 192.168.122.209 [70185.137550] [tdb] Close table 'filter0.tdb' Apr 26 11:33:54 192.168.122.209 [70185.137985] [tempesta fw] modules are stopped Apr 26 11:33:54 192.168.122.209 [70185.329862] [tempesta fw] exiting... Apr 26 11:33:54 192.168.122.209 [70185.466715] [tdb] Shutdown Tempesta DB Apr 26 11:33:55 192.168.122.209 [70185.873537] End test: cache.test_cache.TestCacheHttp.test_replicated_cache_fulfill_suffix2 Apr 26 11:33:55 192.168.122.209 [70185.900141] Start test: cache.test_cache.TestCacheHttp.test_sharding_cache_bypass_all Apr 26 11:33:56 192.168.122.209 [70187.296481] [tdb] Start Tempesta DB Apr 26 11:33:56 192.168.122.209 [70187.430896] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:33:58 192.168.122.209 [70188.785590] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70188.785590] Maybe that's fine, but it's worth checking the [70188.785590] config - if there is no relations between the [70188.785590] names, then host name confusion attack is possible. Apr 26 11:33:58 192.168.122.209 [70188.908331] [tempesta fw] Configuration processing is completed. Apr 26 11:33:58 192.168.122.209 [70188.957925] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:33:58 192.168.122.209 [70189.357232] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:33:58 192.168.122.209 [70189.383664] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:33:58 192.168.122.209 [70189.408597] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:33:58 192.168.122.209 [70189.456338] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:33:58 192.168.122.209 [70189.458085] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:33:58 192.168.122.209 [70189.504321] [tempesta fw] Tempesta FW is ready Apr 26 11:33:59 192.168.122.209 [70190.315459] [tdb] Close table 'client0.tdb' Apr 26 11:33:59 192.168.122.209 [70190.513919] [tdb] Close table 'sessions0.tdb' Apr 26 11:34:02 192.168.122.209 [70193.639971] [tdb] Close table 'cache0.tdb' Apr 26 11:34:03 192.168.122.209 [70193.916075] [tdb] Close table 'filter0.tdb' Apr 26 11:34:03 192.168.122.209 [70193.916541] [tempesta fw] modules are stopped Apr 26 11:34:03 192.168.122.209 [70194.084657] [tempesta fw] exiting... Apr 26 11:34:03 192.168.122.209 [70194.221441] [tdb] Shutdown Tempesta DB Apr 26 11:34:03 192.168.122.209 [70194.582361] End test: cache.test_cache.TestCacheHttp.test_sharding_cache_bypass_all Apr 26 11:34:03 192.168.122.209 [70194.613618] Start test: cache.test_cache.TestCacheHttp.test_sharding_cache_bypass_prefix Apr 26 11:34:05 192.168.122.209 [70195.955809] [tdb] Start Tempesta DB Apr 26 11:34:05 192.168.122.209 [70196.080963] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:34:06 192.168.122.209 [70197.501714] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70197.501714] Maybe that's fine, but it's worth checking the [70197.501714] config - if there is no relations between the [70197.501714] names, then host name confusion attack is possible. Apr 26 11:34:06 192.168.122.209 [70197.664462] [tempesta fw] Configuration processing is completed. Apr 26 11:34:07 192.168.122.209 [70197.714875] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:34:07 192.168.122.209 [70198.127428] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:34:07 192.168.122.209 [70198.153485] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:34:07 192.168.122.209 [70198.179793] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:34:07 192.168.122.209 [70198.256440] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:34:07 192.168.122.209 [70198.258184] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:34:07 192.168.122.209 [70198.296395] [tempesta fw] Tempesta FW is ready Apr 26 11:34:08 192.168.122.209 [70199.088283] [tdb] Close table 'client0.tdb' Apr 26 11:34:08 192.168.122.209 [70199.268433] [tdb] Close table 'sessions0.tdb' Apr 26 11:34:11 192.168.122.209 [70202.399205] [tdb] Close table 'cache0.tdb' Apr 26 11:34:11 192.168.122.209 [70202.623962] [tdb] Close table 'filter0.tdb' Apr 26 11:34:11 192.168.122.209 [70202.624416] [tempesta fw] modules are stopped Apr 26 11:34:12 192.168.122.209 [70202.846455] [tempesta fw] exiting... Apr 26 11:34:12 192.168.122.209 [70202.976391] [tdb] Shutdown Tempesta DB Apr 26 11:34:12 192.168.122.209 [70203.374329] End test: cache.test_cache.TestCacheHttp.test_sharding_cache_bypass_prefix Apr 26 11:34:12 192.168.122.209 [70203.410246] Start test: cache.test_cache.TestCacheHttp.test_sharding_cache_bypass_suffix Apr 26 11:34:14 192.168.122.209 [70204.785600] [tdb] Start Tempesta DB Apr 26 11:34:14 192.168.122.209 [70204.923319] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:34:15 192.168.122.209 [70206.377817] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70206.377817] Maybe that's fine, but it's worth checking the [70206.377817] config - if there is no relations between the [70206.377817] names, then host name confusion attack is possible. Apr 26 11:34:15 192.168.122.209 [70206.548581] [tempesta fw] Configuration processing is completed. Apr 26 11:34:15 192.168.122.209 [70206.600959] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:34:16 192.168.122.209 [70207.006751] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:34:16 192.168.122.209 [70207.032596] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:34:16 192.168.122.209 [70207.058310] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:34:16 192.168.122.209 [70207.100558] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:34:16 192.168.122.209 [70207.102315] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:34:16 192.168.122.209 [70207.152527] [tempesta fw] Tempesta FW is ready Apr 26 11:34:17 192.168.122.209 [70207.933521] [tdb] Close table 'client0.tdb' Apr 26 11:34:17 192.168.122.209 [70208.116191] [tdb] Close table 'sessions0.tdb' Apr 26 11:34:20 192.168.122.209 [70211.280772] [tdb] Close table 'cache0.tdb' Apr 26 11:34:20 192.168.122.209 [70211.506996] [tdb] Close table 'filter0.tdb' Apr 26 11:34:20 192.168.122.209 [70211.507403] [tempesta fw] modules are stopped Apr 26 11:34:21 192.168.122.209 [70211.721961] [tempesta fw] exiting... Apr 26 11:34:21 192.168.122.209 [70211.852440] [tdb] Shutdown Tempesta DB Apr 26 11:34:21 192.168.122.209 [70212.231581] End test: cache.test_cache.TestCacheHttp.test_sharding_cache_bypass_suffix Apr 26 11:34:21 192.168.122.209 [70212.307726] Start test: cache.test_cache.TestCacheHttp.test_sharding_cache_fulfill_all Apr 26 11:34:22 192.168.122.209 [70213.623903] [tdb] Start Tempesta DB Apr 26 11:34:23 192.168.122.209 [70213.758023] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:34:24 192.168.122.209 [70215.185959] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70215.185959] Maybe that's fine, but it's worth checking the [70215.185959] config - if there is no relations between the [70215.185959] names, then host name confusion attack is possible. Apr 26 11:34:24 192.168.122.209 [70215.312657] [tempesta fw] Configuration processing is completed. Apr 26 11:34:24 192.168.122.209 [70215.368014] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:34:25 192.168.122.209 [70215.785927] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:34:25 192.168.122.209 [70215.812250] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:34:25 192.168.122.209 [70215.837968] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:34:25 192.168.122.209 [70215.876597] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:34:25 192.168.122.209 [70215.877649] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:34:25 192.168.122.209 [70215.920619] [tempesta fw] Tempesta FW is ready Apr 26 11:34:25 192.168.122.209 [70216.643809] [tdb] Close table 'client0.tdb' Apr 26 11:34:26 192.168.122.209 [70216.822434] [tdb] Close table 'sessions0.tdb' Apr 26 11:34:29 192.168.122.209 [70219.975394] [tdb] Close table 'cache0.tdb' Apr 26 11:34:29 192.168.122.209 [70220.206528] [tdb] Close table 'filter0.tdb' Apr 26 11:34:29 192.168.122.209 [70220.206925] [tempesta fw] modules are stopped Apr 26 11:34:29 192.168.122.209 [70220.433621] [tempesta fw] exiting... Apr 26 11:34:29 192.168.122.209 [70220.572418] [tdb] Shutdown Tempesta DB Apr 26 11:34:30 192.168.122.209 [70220.894637] End test: cache.test_cache.TestCacheHttp.test_sharding_cache_fulfill_all Apr 26 11:34:30 192.168.122.209 [70220.983510] Start test: cache.test_cache.TestCacheHttp.test_sharding_cache_fulfill_prefix Apr 26 11:34:31 192.168.122.209 [70222.376316] [tdb] Start Tempesta DB Apr 26 11:34:31 192.168.122.209 [70222.521962] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:34:33 192.168.122.209 [70223.938046] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70223.938046] Maybe that's fine, but it's worth checking the [70223.938046] config - if there is no relations between the [70223.938046] names, then host name confusion attack is possible. Apr 26 11:34:33 192.168.122.209 [70224.132694] [tempesta fw] Configuration processing is completed. Apr 26 11:34:33 192.168.122.209 [70224.183952] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:34:33 192.168.122.209 [70224.608787] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:34:33 192.168.122.209 [70224.633609] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:34:33 192.168.122.209 [70224.658328] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:34:34 192.168.122.209 [70224.712773] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:34:34 192.168.122.209 [70224.714527] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:34:34 192.168.122.209 [70224.768721] [tempesta fw] Tempesta FW is ready Apr 26 11:34:34 192.168.122.209 [70225.599958] [tdb] Close table 'client0.tdb' Apr 26 11:34:35 192.168.122.209 [70225.785734] [tdb] Close table 'sessions0.tdb' Apr 26 11:34:38 192.168.122.209 [70228.926142] [tdb] Close table 'cache0.tdb' Apr 26 11:34:38 192.168.122.209 [70229.183508] [tdb] Close table 'filter0.tdb' Apr 26 11:34:38 192.168.122.209 [70229.183979] [tempesta fw] modules are stopped Apr 26 11:34:38 192.168.122.209 [70229.386027] [tempesta fw] exiting... Apr 26 11:34:38 192.168.122.209 [70229.541296] [tdb] Shutdown Tempesta DB Apr 26 11:34:39 192.168.122.209 [70229.940687] End test: cache.test_cache.TestCacheHttp.test_sharding_cache_fulfill_prefix Apr 26 11:34:39 192.168.122.209 [70229.980267] Start test: cache.test_cache.TestCacheHttp.test_sharding_cache_fulfill_suffix Apr 26 11:34:40 192.168.122.209 [70231.362648] [tdb] Start Tempesta DB Apr 26 11:34:40 192.168.122.209 [70231.508117] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:34:42 192.168.122.209 [70232.886313] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70232.886313] Maybe that's fine, but it's worth checking the [70232.886313] config - if there is no relations between the [70232.886313] names, then host name confusion attack is possible. Apr 26 11:34:42 192.168.122.209 [70233.060934] [tempesta fw] Configuration processing is completed. Apr 26 11:34:42 192.168.122.209 [70233.121544] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:34:42 192.168.122.209 [70233.582624] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:34:42 192.168.122.209 [70233.610866] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:34:42 192.168.122.209 [70233.639532] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:34:42 192.168.122.209 [70233.672914] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:34:42 192.168.122.209 [70233.674616] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:34:43 192.168.122.209 [70233.716881] [tempesta fw] Tempesta FW is ready Apr 26 11:34:43 192.168.122.209 [70234.472095] [tdb] Close table 'client0.tdb' Apr 26 11:34:43 192.168.122.209 [70234.683209] [tdb] Close table 'sessions0.tdb' Apr 26 11:34:47 192.168.122.209 [70237.849900] [tdb] Close table 'cache0.tdb' Apr 26 11:34:47 192.168.122.209 [70238.081062] [tdb] Close table 'filter0.tdb' Apr 26 11:34:47 192.168.122.209 [70238.081509] [tempesta fw] modules are stopped Apr 26 11:34:47 192.168.122.209 [70238.268811] [tempesta fw] exiting... Apr 26 11:34:47 192.168.122.209 [70238.421947] [tdb] Shutdown Tempesta DB Apr 26 11:34:48 192.168.122.209 [70238.858793] End test: cache.test_cache.TestCacheHttp.test_sharding_cache_fulfill_suffix Apr 26 11:34:48 192.168.122.209 [70238.892613] Start test: cache.test_cache.TestCacheHttp.test_sharding_cache_fulfill_suffix2 Apr 26 11:34:49 192.168.122.209 [70240.229233] [tdb] Start Tempesta DB Apr 26 11:34:49 192.168.122.209 [70240.378877] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:34:51 192.168.122.209 [70241.798281] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70241.798281] Maybe that's fine, but it's worth checking the [70241.798281] config - if there is no relations between the [70241.798281] names, then host name confusion attack is possible. Apr 26 11:34:51 192.168.122.209 [70241.969027] [tempesta fw] Configuration processing is completed. Apr 26 11:34:51 192.168.122.209 [70242.020704] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:34:51 192.168.122.209 [70242.441286] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:34:51 192.168.122.209 [70242.467092] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:34:51 192.168.122.209 [70242.492867] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:34:51 192.168.122.209 [70242.545025] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:34:51 192.168.122.209 [70242.546748] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:34:51 192.168.122.209 [70242.608955] [tempesta fw] Tempesta FW is ready Apr 26 11:34:52 192.168.122.209 [70243.410193] [tdb] Close table 'client0.tdb' Apr 26 11:34:52 192.168.122.209 [70243.592526] [tdb] Close table 'sessions0.tdb' Apr 26 11:34:56 192.168.122.209 [70246.752321] [tdb] Close table 'cache0.tdb' Apr 26 11:34:56 192.168.122.209 [70246.992101] [tdb] Close table 'filter0.tdb' Apr 26 11:34:56 192.168.122.209 [70246.992521] [tempesta fw] modules are stopped Apr 26 11:34:56 192.168.122.209 [70247.216337] [tempesta fw] exiting... Apr 26 11:34:56 192.168.122.209 [70247.357791] [tdb] Shutdown Tempesta DB Apr 26 11:34:57 192.168.122.209 [70247.728173] End test: cache.test_cache.TestCacheHttp.test_sharding_cache_fulfill_suffix2 Apr 26 11:34:57 192.168.122.209 [70247.771466] Start test: cache.test_cache.TestCacheLocationH2.test_prefix_bypassed Apr 26 11:34:58 192.168.122.209 [70249.201105] [tdb] Start Tempesta DB Apr 26 11:34:58 192.168.122.209 [70249.327617] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:35:00 192.168.122.209 [70251.258402] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70251.258402] Maybe that's fine, but it's worth checking the [70251.258402] config - if there is no relations between the [70251.258402] names, then host name confusion attack is possible. Apr 26 11:35:00 192.168.122.209 [70251.349099] [tempesta fw] Configuration processing is completed. Apr 26 11:35:00 192.168.122.209 [70251.399576] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:35:01 192.168.122.209 [70251.807359] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:35:01 192.168.122.209 [70251.832686] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:35:01 192.168.122.209 [70251.857123] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:35:01 192.168.122.209 [70251.913147] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:35:01 192.168.122.209 [70251.914870] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:35:01 192.168.122.209 [70251.957127] [tempesta fw] Tempesta FW is ready Apr 26 11:35:01 192.168.122.209 [70252.610404] [tdb] Close table 'client0.tdb' Apr 26 11:35:02 192.168.122.209 [70252.798558] [tdb] Close table 'sessions0.tdb' Apr 26 11:35:05 192.168.122.209 [70255.929167] [tdb] Close table 'cache0.tdb' Apr 26 11:35:05 192.168.122.209 [70256.196649] [tdb] Close table 'filter0.tdb' Apr 26 11:35:05 192.168.122.209 [70256.197081] [tempesta fw] modules are stopped Apr 26 11:35:05 192.168.122.209 [70256.397956] [tempesta fw] exiting... Apr 26 11:35:05 192.168.122.209 [70256.543840] [tdb] Shutdown Tempesta DB Apr 26 11:35:06 192.168.122.209 [70256.911826] End test: cache.test_cache.TestCacheLocationH2.test_prefix_bypassed Apr 26 11:35:06 192.168.122.209 [70256.949577] Start test: cache.test_cache.TestCacheLocationH2.test_suffix_cached Apr 26 11:35:07 192.168.122.209 [70258.326545] [tdb] Start Tempesta DB Apr 26 11:35:07 192.168.122.209 [70258.457586] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:35:09 192.168.122.209 [70260.306600] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70260.306600] Maybe that's fine, but it's worth checking the [70260.306600] config - if there is no relations between the [70260.306600] names, then host name confusion attack is possible. Apr 26 11:35:09 192.168.122.209 [70260.413248] [tempesta fw] Configuration processing is completed. Apr 26 11:35:09 192.168.122.209 [70260.474912] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:35:10 192.168.122.209 [70260.912351] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:35:10 192.168.122.209 [70260.940076] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:35:10 192.168.122.209 [70260.967188] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:35:10 192.168.122.209 [70261.017266] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:35:10 192.168.122.209 [70261.019043] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:35:10 192.168.122.209 [70261.057217] [tempesta fw] Tempesta FW is ready Apr 26 11:35:11 192.168.122.209 [70261.728296] [tdb] Close table 'client0.tdb' Apr 26 11:35:11 192.168.122.209 [70261.915139] [tdb] Close table 'sessions0.tdb' Apr 26 11:35:14 192.168.122.209 [70265.083633] [tdb] Close table 'cache0.tdb' Apr 26 11:35:14 192.168.122.209 [70265.322214] [tdb] Close table 'filter0.tdb' Apr 26 11:35:14 192.168.122.209 [70265.322668] [tempesta fw] modules are stopped Apr 26 11:35:14 192.168.122.209 [70265.513556] [tempesta fw] exiting... Apr 26 11:35:14 192.168.122.209 [70265.642131] [tdb] Shutdown Tempesta DB Apr 26 11:35:15 192.168.122.209 [70266.077920] End test: cache.test_cache.TestCacheLocationH2.test_suffix_cached Apr 26 11:35:15 192.168.122.209 [70266.114759] Start test: cache.test_cache.TestCacheLocationH2.test_suffix_cached_and_prefix_bypassed Apr 26 11:35:16 192.168.122.209 [70267.477499] [tdb] Start Tempesta DB Apr 26 11:35:16 192.168.122.209 [70267.612415] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:35:18 192.168.122.209 [70269.442752] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70269.442752] Maybe that's fine, but it's worth checking the [70269.442752] config - if there is no relations between the [70269.442752] names, then host name confusion attack is possible. Apr 26 11:35:18 192.168.122.209 [70269.537722] [tempesta fw] Configuration processing is completed. Apr 26 11:35:18 192.168.122.209 [70269.590611] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:35:19 192.168.122.209 [70270.042395] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:35:19 192.168.122.209 [70270.072038] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:35:19 192.168.122.209 [70270.101765] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:35:19 192.168.122.209 [70270.145324] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:35:19 192.168.122.209 [70270.146630] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:35:19 192.168.122.209 [70270.193328] [tempesta fw] Tempesta FW is ready Apr 26 11:35:20 192.168.122.209 [70270.841247] [tdb] Close table 'client0.tdb' Apr 26 11:35:20 192.168.122.209 [70271.025937] [tdb] Close table 'sessions0.tdb' Apr 26 11:35:23 192.168.122.209 [70274.246427] [tdb] Close table 'cache0.tdb' Apr 26 11:35:23 192.168.122.209 [70274.506368] [tdb] Close table 'filter0.tdb' Apr 26 11:35:23 192.168.122.209 [70274.506829] [tempesta fw] modules are stopped Apr 26 11:35:23 192.168.122.209 [70274.682011] [tempesta fw] exiting... Apr 26 11:35:24 192.168.122.209 [70274.812461] [tdb] Shutdown Tempesta DB Apr 26 11:35:24 192.168.122.209 [70275.204686] End test: cache.test_cache.TestCacheLocationH2.test_suffix_cached_and_prefix_bypassed Apr 26 11:35:24 192.168.122.209 [70275.242072] Start test: cache.test_cache.TestCacheLocationHttp.test_prefix_bypassed Apr 26 11:35:25 192.168.122.209 [70276.619888] [tdb] Start Tempesta DB Apr 26 11:35:26 192.168.122.209 [70276.767524] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:35:27 192.168.122.209 [70278.639974] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70278.639974] Maybe that's fine, but it's worth checking the [70278.639974] config - if there is no relations between the [70278.639974] names, then host name confusion attack is possible. Apr 26 11:35:28 192.168.122.209 [70278.733540] [tempesta fw] Configuration processing is completed. Apr 26 11:35:28 192.168.122.209 [70278.794052] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:35:28 192.168.122.209 [70279.248764] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:35:28 192.168.122.209 [70279.278279] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:35:28 192.168.122.209 [70279.306825] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:35:28 192.168.122.209 [70279.357512] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:35:28 192.168.122.209 [70279.359249] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:35:28 192.168.122.209 [70279.397450] [tempesta fw] Tempesta FW is ready Apr 26 11:35:29 192.168.122.209 [70280.064840] [tdb] Close table 'client0.tdb' Apr 26 11:35:29 192.168.122.209 [70280.254338] [tdb] Close table 'sessions0.tdb' Apr 26 11:35:32 192.168.122.209 [70283.411016] [tdb] Close table 'cache0.tdb' Apr 26 11:35:32 192.168.122.209 [70283.656524] [tdb] Close table 'filter0.tdb' Apr 26 11:35:32 192.168.122.209 [70283.656967] [tempesta fw] modules are stopped Apr 26 11:35:33 192.168.122.209 [70283.894067] [tempesta fw] exiting... Apr 26 11:35:33 192.168.122.209 [70283.996231] [tdb] Shutdown Tempesta DB Apr 26 11:35:33 192.168.122.209 [70284.440469] End test: cache.test_cache.TestCacheLocationHttp.test_prefix_bypassed Apr 26 11:35:33 192.168.122.209 [70284.475254] Start test: cache.test_cache.TestCacheLocationHttp.test_suffix_cached Apr 26 11:35:35 192.168.122.209 [70285.876541] [tdb] Start Tempesta DB Apr 26 11:35:35 192.168.122.209 [70286.031243] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:35:37 192.168.122.209 [70287.890938] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70287.890938] Maybe that's fine, but it's worth checking the [70287.890938] config - if there is no relations between the [70287.890938] names, then host name confusion attack is possible. Apr 26 11:35:37 192.168.122.209 [70287.985517] [tempesta fw] Configuration processing is completed. Apr 26 11:35:37 192.168.122.209 [70288.037084] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:35:37 192.168.122.209 [70288.460835] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:35:37 192.168.122.209 [70288.488015] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:35:37 192.168.122.209 [70288.514353] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:35:37 192.168.122.209 [70288.573629] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:35:37 192.168.122.209 [70288.575425] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:35:37 192.168.122.209 [70288.613559] [tempesta fw] Tempesta FW is ready Apr 26 11:35:38 192.168.122.209 [70289.272254] [tdb] Close table 'client0.tdb' Apr 26 11:35:38 192.168.122.209 [70289.453289] [tdb] Close table 'sessions0.tdb' Apr 26 11:35:41 192.168.122.209 [70292.655933] [tdb] Close table 'cache0.tdb' Apr 26 11:35:42 192.168.122.209 [70292.930410] [tdb] Close table 'filter0.tdb' Apr 26 11:35:42 192.168.122.209 [70292.930860] [tempesta fw] modules are stopped Apr 26 11:35:42 192.168.122.209 [70293.134502] [tempesta fw] exiting... Apr 26 11:35:42 192.168.122.209 [70293.264109] [tdb] Shutdown Tempesta DB Apr 26 11:35:42 192.168.122.209 [70293.661967] End test: cache.test_cache.TestCacheLocationHttp.test_suffix_cached Apr 26 11:35:43 192.168.122.209 [70293.697899] Start test: cache.test_cache.TestCacheLocationHttp.test_suffix_cached_and_prefix_bypassed Apr 26 11:35:44 192.168.122.209 [70295.146486] [tdb] Start Tempesta DB Apr 26 11:35:44 192.168.122.209 [70295.273449] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:35:46 192.168.122.209 [70297.143136] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70297.143136] Maybe that's fine, but it's worth checking the [70297.143136] config - if there is no relations between the [70297.143136] names, then host name confusion attack is possible. Apr 26 11:35:46 192.168.122.209 [70297.245736] [tempesta fw] Configuration processing is completed. Apr 26 11:35:46 192.168.122.209 [70297.300102] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:35:47 192.168.122.209 [70297.705837] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:35:47 192.168.122.209 [70297.732134] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:35:47 192.168.122.209 [70297.757733] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:35:47 192.168.122.209 [70297.817757] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:35:47 192.168.122.209 [70297.819501] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:35:47 192.168.122.209 [70297.857673] [tempesta fw] Tempesta FW is ready Apr 26 11:35:47 192.168.122.209 [70298.531311] [tdb] Close table 'client0.tdb' Apr 26 11:35:48 192.168.122.209 [70298.716337] [tdb] Close table 'sessions0.tdb' Apr 26 11:35:51 192.168.122.209 [70301.848490] [tdb] Close table 'cache0.tdb' Apr 26 11:35:51 192.168.122.209 [70302.101763] [tdb] Close table 'filter0.tdb' Apr 26 11:35:51 192.168.122.209 [70302.102205] [tempesta fw] modules are stopped Apr 26 11:35:51 192.168.122.209 [70302.282322] [tempesta fw] exiting... Apr 26 11:35:51 192.168.122.209 [70302.404941] [tdb] Shutdown Tempesta DB Apr 26 11:35:52 192.168.122.209 [70302.780042] End test: cache.test_cache.TestCacheLocationHttp.test_suffix_cached_and_prefix_bypassed Apr 26 11:35:52 192.168.122.209 [70302.862239] Start test: cache.test_cache.TestCacheMultipleMethodsH2.test_GET_after_GET Apr 26 11:35:53 192.168.122.209 [70304.201178] [tdb] Start Tempesta DB Apr 26 11:35:53 192.168.122.209 [70304.323584] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:35:55 192.168.122.209 [70305.862987] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70305.862987] Maybe that's fine, but it's worth checking the [70305.862987] config - if there is no relations between the [70305.862987] names, then host name confusion attack is possible. Apr 26 11:35:55 192.168.122.209 [70305.929838] [tempesta fw] Configuration processing is completed. Apr 26 11:35:55 192.168.122.209 [70305.981611] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:35:55 192.168.122.209 [70306.452836] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:35:55 192.168.122.209 [70306.499539] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:35:55 192.168.122.209 [70306.532791] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:35:55 192.168.122.209 [70306.577850] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:35:55 192.168.122.209 [70306.579612] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:35:55 192.168.122.209 [70306.617728] [tempesta fw] Tempesta FW is ready Apr 26 11:35:56 192.168.122.209 [70307.315619] [tdb] Close table 'client0.tdb' Apr 26 11:35:56 192.168.122.209 [70307.497567] [tdb] Close table 'sessions0.tdb' Apr 26 11:36:00 192.168.122.209 [70310.731969] [tdb] Close table 'cache0.tdb' Apr 26 11:36:00 192.168.122.209 [70310.998758] [tdb] Close table 'filter0.tdb' Apr 26 11:36:00 192.168.122.209 [70310.999186] [tempesta fw] modules are stopped Apr 26 11:36:00 192.168.122.209 [70311.215835] [tempesta fw] exiting... Apr 26 11:36:00 192.168.122.209 [70311.327892] [tdb] Shutdown Tempesta DB Apr 26 11:36:01 192.168.122.209 [70311.720606] End test: cache.test_cache.TestCacheMultipleMethodsH2.test_GET_after_GET Apr 26 11:36:01 192.168.122.209 [70311.760396] Start test: cache.test_cache.TestCacheMultipleMethodsH2.test_GET_after_HEAD Apr 26 11:36:02 192.168.122.209 [70313.125599] [tdb] Start Tempesta DB Apr 26 11:36:02 192.168.122.209 [70313.260185] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:36:04 192.168.122.209 [70314.751192] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70314.751192] Maybe that's fine, but it's worth checking the [70314.751192] config - if there is no relations between the [70314.751192] names, then host name confusion attack is possible. Apr 26 11:36:04 192.168.122.209 [70314.817956] [tempesta fw] Configuration processing is completed. Apr 26 11:36:04 192.168.122.209 [70314.874411] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:36:04 192.168.122.209 [70315.336307] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:36:04 192.168.122.209 [70315.361872] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:36:04 192.168.122.209 [70315.387311] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:36:04 192.168.122.209 [70315.421959] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:36:04 192.168.122.209 [70315.423709] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:36:04 192.168.122.209 [70315.465938] [tempesta fw] Tempesta FW is ready Apr 26 11:36:05 192.168.122.209 [70316.134504] [tdb] Close table 'client0.tdb' Apr 26 11:36:05 192.168.122.209 [70316.305287] [tdb] Close table 'sessions0.tdb' Apr 26 11:36:08 192.168.122.209 [70319.506655] [tdb] Close table 'cache0.tdb' Apr 26 11:36:09 192.168.122.209 [70319.734368] [tdb] Close table 'filter0.tdb' Apr 26 11:36:09 192.168.122.209 [70319.734817] [tempesta fw] modules are stopped Apr 26 11:36:09 192.168.122.209 [70319.941042] [tempesta fw] exiting... Apr 26 11:36:09 192.168.122.209 [70320.050196] [tdb] Shutdown Tempesta DB Apr 26 11:36:09 192.168.122.209 [70320.448615] End test: cache.test_cache.TestCacheMultipleMethodsH2.test_GET_after_HEAD Apr 26 11:36:09 192.168.122.209 [70320.477927] Start test: cache.test_cache.TestCacheMultipleMethodsH2.test_HEAD_after_GET Apr 26 11:36:11 192.168.122.209 [70321.910330] [tdb] Start Tempesta DB Apr 26 11:36:11 192.168.122.209 [70322.038066] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:36:12 192.168.122.209 [70323.627436] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70323.627436] Maybe that's fine, but it's worth checking the [70323.627436] config - if there is no relations between the [70323.627436] names, then host name confusion attack is possible. Apr 26 11:36:13 192.168.122.209 [70323.706108] [tempesta fw] Configuration processing is completed. Apr 26 11:36:13 192.168.122.209 [70323.771369] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:36:13 192.168.122.209 [70324.190591] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:36:13 192.168.122.209 [70324.217857] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:36:13 192.168.122.209 [70324.245340] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:36:13 192.168.122.209 [70324.286079] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:36:13 192.168.122.209 [70324.287857] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:36:13 192.168.122.209 [70324.330022] [tempesta fw] Tempesta FW is ready Apr 26 11:36:14 192.168.122.209 [70325.009606] [tdb] Close table 'client0.tdb' Apr 26 11:36:14 192.168.122.209 [70325.194546] [tdb] Close table 'sessions0.tdb' Apr 26 11:36:17 192.168.122.209 [70328.334889] [tdb] Close table 'cache0.tdb' Apr 26 11:36:17 192.168.122.209 [70328.576393] [tdb] Close table 'filter0.tdb' Apr 26 11:36:17 192.168.122.209 [70328.576867] [tempesta fw] modules are stopped Apr 26 11:36:18 192.168.122.209 [70328.769073] [tempesta fw] exiting... Apr 26 11:36:18 192.168.122.209 [70328.916787] [tdb] Shutdown Tempesta DB Apr 26 11:36:18 192.168.122.209 [70329.340038] End test: cache.test_cache.TestCacheMultipleMethodsH2.test_HEAD_after_GET Apr 26 11:36:18 192.168.122.209 [70329.376436] Start test: cache.test_cache.TestCacheMultipleMethodsH2.test_HEAD_after_HEAD Apr 26 11:36:20 192.168.122.209 [70330.772163] [tdb] Start Tempesta DB Apr 26 11:36:20 192.168.122.209 [70330.906391] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:36:21 192.168.122.209 [70332.327438] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70332.327438] Maybe that's fine, but it's worth checking the [70332.327438] config - if there is no relations between the [70332.327438] names, then host name confusion attack is possible. Apr 26 11:36:21 192.168.122.209 [70332.394194] [tempesta fw] Configuration processing is completed. Apr 26 11:36:21 192.168.122.209 [70332.444971] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:36:22 192.168.122.209 [70332.849377] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:36:22 192.168.122.209 [70332.875195] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:36:22 192.168.122.209 [70332.900852] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:36:22 192.168.122.209 [70332.958157] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:36:22 192.168.122.209 [70332.959942] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:36:22 192.168.122.209 [70333.010128] [tempesta fw] Tempesta FW is ready Apr 26 11:36:22 192.168.122.209 [70333.661028] [tdb] Close table 'client0.tdb' Apr 26 11:36:23 192.168.122.209 [70333.849604] [tdb] Close table 'sessions0.tdb' Apr 26 11:36:26 192.168.122.209 [70337.002204] [tdb] Close table 'cache0.tdb' Apr 26 11:36:26 192.168.122.209 [70337.264400] [tdb] Close table 'filter0.tdb' Apr 26 11:36:26 192.168.122.209 [70337.264839] [tempesta fw] modules are stopped Apr 26 11:36:26 192.168.122.209 [70337.441703] [tempesta fw] exiting... Apr 26 11:36:26 192.168.122.209 [70337.599642] [tdb] Shutdown Tempesta DB Apr 26 11:36:27 192.168.122.209 [70337.989154] End test: cache.test_cache.TestCacheMultipleMethodsH2.test_HEAD_after_HEAD Apr 26 11:36:27 192.168.122.209 [70338.019446] Start test: cache.test_cache.TestCacheMultipleMethodsH2.test_POST_after_GET Apr 26 11:36:28 192.168.122.209 [70339.465294] [tdb] Start Tempesta DB Apr 26 11:36:28 192.168.122.209 [70339.605651] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:36:30 192.168.122.209 [70341.091543] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70341.091543] Maybe that's fine, but it's worth checking the [70341.091543] config - if there is no relations between the [70341.091543] names, then host name confusion attack is possible. Apr 26 11:36:30 192.168.122.209 [70341.166293] [tempesta fw] Configuration processing is completed. Apr 26 11:36:30 192.168.122.209 [70341.222443] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:36:30 192.168.122.209 [70341.659168] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:36:30 192.168.122.209 [70341.687548] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:36:31 192.168.122.209 [70341.714155] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:36:31 192.168.122.209 [70341.754683] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:36:31 192.168.122.209 [70341.756404] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:36:31 192.168.122.209 [70341.794254] [tempesta fw] Tempesta FW is ready Apr 26 11:36:31 192.168.122.209 [70342.476743] [tdb] Close table 'client0.tdb' Apr 26 11:36:31 192.168.122.209 [70342.670216] [tdb] Close table 'sessions0.tdb' Apr 26 11:36:35 192.168.122.209 [70345.806041] [tdb] Close table 'cache0.tdb' Apr 26 11:36:35 192.168.122.209 [70346.083528] [tdb] Close table 'filter0.tdb' Apr 26 11:36:35 192.168.122.209 [70346.083941] [tempesta fw] modules are stopped Apr 26 11:36:35 192.168.122.209 [70346.267031] [tempesta fw] exiting... Apr 26 11:36:35 192.168.122.209 [70346.400369] [tdb] Shutdown Tempesta DB Apr 26 11:36:36 192.168.122.209 [70346.749006] End test: cache.test_cache.TestCacheMultipleMethodsH2.test_POST_after_GET Apr 26 11:36:36 192.168.122.209 [70346.779719] Start test: cache.test_cache.TestCacheMultipleMethodsH2.test_POST_after_HEAD Apr 26 11:36:37 192.168.122.209 [70348.221532] [tdb] Start Tempesta DB Apr 26 11:36:37 192.168.122.209 [70348.357030] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:36:39 192.168.122.209 [70349.879801] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70349.879801] Maybe that's fine, but it's worth checking the [70349.879801] config - if there is no relations between the [70349.879801] names, then host name confusion attack is possible. Apr 26 11:36:39 192.168.122.209 [70349.946907] [tempesta fw] Configuration processing is completed. Apr 26 11:36:39 192.168.122.209 [70350.008338] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:36:39 192.168.122.209 [70350.420114] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:36:39 192.168.122.209 [70350.446415] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:36:39 192.168.122.209 [70350.474392] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:36:39 192.168.122.209 [70350.530425] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:36:39 192.168.122.209 [70350.532156] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:36:39 192.168.122.209 [70350.570369] [tempesta fw] Tempesta FW is ready Apr 26 11:36:40 192.168.122.209 [70351.243943] [tdb] Close table 'client0.tdb' Apr 26 11:36:40 192.168.122.209 [70351.436471] [tdb] Close table 'sessions0.tdb' Apr 26 11:36:43 192.168.122.209 [70354.626490] [tdb] Close table 'cache0.tdb' Apr 26 11:36:44 192.168.122.209 [70354.886937] [tdb] Close table 'filter0.tdb' Apr 26 11:36:44 192.168.122.209 [70354.887372] [tempesta fw] modules are stopped Apr 26 11:36:44 192.168.122.209 [70355.097910] [tempesta fw] exiting... Apr 26 11:36:44 192.168.122.209 [70355.253267] [tdb] Shutdown Tempesta DB Apr 26 11:36:44 192.168.122.209 [70355.638458] End test: cache.test_cache.TestCacheMultipleMethodsH2.test_POST_after_HEAD Apr 26 11:36:45 192.168.122.209 [70355.721204] Start test: cache.test_cache.TestCacheMultipleMethodsH2.test_cache_POST_request_not_cached_no_cache_control Apr 26 11:36:46 192.168.122.209 [70357.116265] [tdb] Start Tempesta DB Apr 26 11:36:46 192.168.122.209 [70357.239380] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:36:48 192.168.122.209 [70358.727767] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70358.727767] Maybe that's fine, but it's worth checking the [70358.727767] config - if there is no relations between the [70358.727767] names, then host name confusion attack is possible. Apr 26 11:36:48 192.168.122.209 [70358.802639] [tempesta fw] Configuration processing is completed. Apr 26 11:36:48 192.168.122.209 [70358.861802] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:36:48 192.168.122.209 [70359.272991] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:36:48 192.168.122.209 [70359.299889] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:36:48 192.168.122.209 [70359.327489] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:36:48 192.168.122.209 [70359.382526] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:36:48 192.168.122.209 [70359.384266] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:36:48 192.168.122.209 [70359.438504] [tempesta fw] Tempesta FW is ready Apr 26 11:36:49 192.168.122.209 [70360.068423] [tdb] Close table 'client0.tdb' Apr 26 11:36:49 192.168.122.209 [70360.240986] [tdb] Close table 'sessions0.tdb' Apr 26 11:36:52 192.168.122.209 [70363.427827] [tdb] Close table 'cache0.tdb' Apr 26 11:36:52 192.168.122.209 [70363.685964] [tdb] Close table 'filter0.tdb' Apr 26 11:36:52 192.168.122.209 [70363.686801] [tempesta fw] modules are stopped Apr 26 11:36:53 192.168.122.209 [70363.860104] [tempesta fw] exiting... Apr 26 11:36:53 192.168.122.209 [70363.981027] [tdb] Shutdown Tempesta DB Apr 26 11:36:53 192.168.122.209 [70364.440355] End test: cache.test_cache.TestCacheMultipleMethodsH2.test_cache_POST_request_not_cached_no_cache_control Apr 26 11:36:53 192.168.122.209 [70364.470962] Start test: cache.test_cache.TestCacheMultipleMethodsH2.test_cache_POST_request_not_cached_not_same_location Apr 26 11:36:55 192.168.122.209 [70365.875402] [tdb] Start Tempesta DB Apr 26 11:36:55 192.168.122.209 [70366.006712] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:36:56 192.168.122.209 [70367.555870] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70367.555870] Maybe that's fine, but it's worth checking the [70367.555870] config - if there is no relations between the [70367.555870] names, then host name confusion attack is possible. Apr 26 11:36:56 192.168.122.209 [70367.634634] [tempesta fw] Configuration processing is completed. Apr 26 11:36:56 192.168.122.209 [70367.688059] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:36:57 192.168.122.209 [70368.101319] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:36:57 192.168.122.209 [70368.128414] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:36:57 192.168.122.209 [70368.156100] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:36:57 192.168.122.209 [70368.194659] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:36:57 192.168.122.209 [70368.196399] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:36:57 192.168.122.209 [70368.258589] [tempesta fw] Tempesta FW is ready Apr 26 11:36:58 192.168.122.209 [70368.870504] [tdb] Close table 'client0.tdb' Apr 26 11:36:58 192.168.122.209 [70369.057041] [tdb] Close table 'sessions0.tdb' Apr 26 11:37:01 192.168.122.209 [70372.222733] [tdb] Close table 'cache0.tdb' Apr 26 11:37:01 192.168.122.209 [70372.460080] [tdb] Close table 'filter0.tdb' Apr 26 11:37:01 192.168.122.209 [70372.460493] [tempesta fw] modules are stopped Apr 26 11:37:01 192.168.122.209 [70372.654503] [tempesta fw] exiting... Apr 26 11:37:02 192.168.122.209 [70372.786919] [tdb] Shutdown Tempesta DB Apr 26 11:37:02 192.168.122.209 [70373.177871] End test: cache.test_cache.TestCacheMultipleMethodsH2.test_cache_POST_request_not_cached_not_same_location Apr 26 11:37:02 192.168.122.209 [70373.267498] Start test: cache.test_cache.TestCacheMultipleMethodsH2.test_cache_POST_request_with_location_GET Apr 26 11:37:03 192.168.122.209 [70374.637433] [tdb] Start Tempesta DB Apr 26 11:37:04 192.168.122.209 [70374.769511] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:37:05 192.168.122.209 [70376.371953] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70376.371953] Maybe that's fine, but it's worth checking the [70376.371953] config - if there is no relations between the [70376.371953] names, then host name confusion attack is possible. Apr 26 11:37:05 192.168.122.209 [70376.454750] [tempesta fw] Configuration processing is completed. Apr 26 11:37:05 192.168.122.209 [70376.511014] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:37:06 192.168.122.209 [70376.934208] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:37:06 192.168.122.209 [70376.960398] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:37:06 192.168.122.209 [70376.986375] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:37:06 192.168.122.209 [70377.026769] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:37:06 192.168.122.209 [70377.028492] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:37:06 192.168.122.209 [70377.066696] [tempesta fw] Tempesta FW is ready Apr 26 11:37:07 192.168.122.209 [70377.717030] [tdb] Close table 'client0.tdb' Apr 26 11:37:07 192.168.122.209 [70377.899542] [tdb] Close table 'sessions0.tdb' Apr 26 11:37:10 192.168.122.209 [70381.068228] [tdb] Close table 'cache0.tdb' Apr 26 11:37:10 192.168.122.209 [70381.312222] [tdb] Close table 'filter0.tdb' Apr 26 11:37:10 192.168.122.209 [70381.312647] [tempesta fw] modules are stopped Apr 26 11:37:10 192.168.122.209 [70381.503369] [tempesta fw] exiting... Apr 26 11:37:10 192.168.122.209 [70381.629917] [tdb] Shutdown Tempesta DB Apr 26 11:37:11 192.168.122.209 [70382.104557] End test: cache.test_cache.TestCacheMultipleMethodsH2.test_cache_POST_request_with_location_GET Apr 26 11:37:11 192.168.122.209 [70382.145219] Start test: cache.test_cache.TestCacheMultipleMethodsH2.test_cache_POST_request_with_location_HEAD Apr 26 11:37:12 192.168.122.209 [70383.579048] [tdb] Start Tempesta DB Apr 26 11:37:13 192.168.122.209 [70383.731754] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:37:14 192.168.122.209 [70385.260159] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70385.260159] Maybe that's fine, but it's worth checking the [70385.260159] config - if there is no relations between the [70385.260159] names, then host name confusion attack is possible. Apr 26 11:37:14 192.168.122.209 [70385.338868] [tempesta fw] Configuration processing is completed. Apr 26 11:37:14 192.168.122.209 [70385.392227] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:37:15 192.168.122.209 [70385.805551] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:37:15 192.168.122.209 [70385.830651] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:37:15 192.168.122.209 [70385.855720] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:37:15 192.168.122.209 [70385.910865] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:37:15 192.168.122.209 [70385.912615] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:37:15 192.168.122.209 [70385.950812] [tempesta fw] Tempesta FW is ready Apr 26 11:37:15 192.168.122.209 [70386.648431] [tdb] Close table 'client0.tdb' Apr 26 11:37:16 192.168.122.209 [70386.838583] [tdb] Close table 'sessions0.tdb' Apr 26 11:37:19 192.168.122.209 [70389.978694] [tdb] Close table 'cache0.tdb' Apr 26 11:37:19 192.168.122.209 [70390.207171] [tdb] Close table 'filter0.tdb' Apr 26 11:37:19 192.168.122.209 [70390.207593] [tempesta fw] modules are stopped Apr 26 11:37:19 192.168.122.209 [70390.398961] [tempesta fw] exiting... Apr 26 11:37:19 192.168.122.209 [70390.516708] [tdb] Shutdown Tempesta DB Apr 26 11:37:20 192.168.122.209 [70390.930010] End test: cache.test_cache.TestCacheMultipleMethodsH2.test_cache_POST_request_with_location_HEAD Apr 26 11:37:20 192.168.122.209 [70390.962981] Start test: cache.test_cache.TestCacheMultipleMethodsH2.test_cache_POST_request_with_location_POST Apr 26 11:37:21 192.168.122.209 [70392.358611] [tdb] Start Tempesta DB Apr 26 11:37:21 192.168.122.209 [70392.487196] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:37:23 192.168.122.209 [70394.044301] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70394.044301] Maybe that's fine, but it's worth checking the [70394.044301] config - if there is no relations between the [70394.044301] names, then host name confusion attack is possible. Apr 26 11:37:23 192.168.122.209 [70394.119131] [tempesta fw] Configuration processing is completed. Apr 26 11:37:23 192.168.122.209 [70394.176965] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:37:23 192.168.122.209 [70394.595750] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:37:23 192.168.122.209 [70394.622482] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:37:23 192.168.122.209 [70394.648877] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:37:24 192.168.122.209 [70394.694984] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:37:24 192.168.122.209 [70394.696721] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:37:24 192.168.122.209 [70394.738921] [tempesta fw] Tempesta FW is ready Apr 26 11:37:24 192.168.122.209 [70395.382816] [tdb] Close table 'client0.tdb' Apr 26 11:37:24 192.168.122.209 [70395.572255] [tdb] Close table 'sessions0.tdb' Apr 26 11:37:28 192.168.122.209 [70398.720345] [tdb] Close table 'cache0.tdb' Apr 26 11:37:28 192.168.122.209 [70398.940357] [tdb] Close table 'filter0.tdb' Apr 26 11:37:28 192.168.122.209 [70398.940830] [tempesta fw] modules are stopped Apr 26 11:37:28 192.168.122.209 [70399.148330] [tempesta fw] exiting... Apr 26 11:37:28 192.168.122.209 [70399.282196] [tdb] Shutdown Tempesta DB Apr 26 11:37:29 192.168.122.209 [70399.736321] End test: cache.test_cache.TestCacheMultipleMethodsH2.test_cache_POST_request_with_location_POST Apr 26 11:37:29 192.168.122.209 [70399.766621] Start test: cache.test_cache.TestCacheMultipleMethodsH2.test_several_entries_GET_GET Apr 26 11:37:30 192.168.122.209 [70401.164158] [tdb] Start Tempesta DB Apr 26 11:37:30 192.168.122.209 [70401.294487] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:37:32 192.168.122.209 [70402.860403] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70402.860403] Maybe that's fine, but it's worth checking the [70402.860403] config - if there is no relations between the [70402.860403] names, then host name confusion attack is possible. Apr 26 11:37:32 192.168.122.209 [70402.931124] [tempesta fw] Configuration processing is completed. Apr 26 11:37:32 192.168.122.209 [70402.994840] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:37:32 192.168.122.209 [70403.417394] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:37:32 192.168.122.209 [70403.443429] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:37:32 192.168.122.209 [70403.468917] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:37:32 192.168.122.209 [70403.507110] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:37:32 192.168.122.209 [70403.508838] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:37:32 192.168.122.209 [70403.547050] [tempesta fw] Tempesta FW is ready Apr 26 11:37:35 192.168.122.209 [70406.271262] [tdb] Close table 'client0.tdb' Apr 26 11:37:35 192.168.122.209 [70406.464253] [tdb] Close table 'sessions0.tdb' Apr 26 11:37:38 192.168.122.209 [70409.644564] [tdb] Close table 'cache0.tdb' Apr 26 11:37:39 192.168.122.209 [70409.862635] [tdb] Close table 'filter0.tdb' Apr 26 11:37:39 192.168.122.209 [70409.863079] [tempesta fw] modules are stopped Apr 26 11:37:39 192.168.122.209 [70410.088330] [tempesta fw] exiting... Apr 26 11:37:39 192.168.122.209 [70410.231540] [tdb] Shutdown Tempesta DB Apr 26 11:37:39 192.168.122.209 [70410.650229] End test: cache.test_cache.TestCacheMultipleMethodsH2.test_several_entries_GET_GET Apr 26 11:37:39 192.168.122.209 [70410.680748] Start test: cache.test_cache.TestCacheMultipleMethodsH2.test_several_entries_GET_HEAD Apr 26 11:37:41 192.168.122.209 [70412.029688] [tdb] Start Tempesta DB Apr 26 11:37:41 192.168.122.209 [70412.167226] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:37:43 192.168.122.209 [70413.688527] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70413.688527] Maybe that's fine, but it's worth checking the [70413.688527] config - if there is no relations between the [70413.688527] names, then host name confusion attack is possible. Apr 26 11:37:43 192.168.122.209 [70413.771379] [tempesta fw] Configuration processing is completed. Apr 26 11:37:43 192.168.122.209 [70413.841631] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:37:43 192.168.122.209 [70414.257675] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:37:43 192.168.122.209 [70414.284871] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:37:43 192.168.122.209 [70414.311119] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:37:43 192.168.122.209 [70414.363241] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:37:43 192.168.122.209 [70414.364995] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:37:43 192.168.122.209 [70414.403194] [tempesta fw] Tempesta FW is ready Apr 26 11:37:46 192.168.122.209 [70417.025498] [tdb] Close table 'client0.tdb' Apr 26 11:37:46 192.168.122.209 [70417.224849] [tdb] Close table 'sessions0.tdb' Apr 26 11:37:49 192.168.122.209 [70420.443130] [tdb] Close table 'cache0.tdb' Apr 26 11:37:49 192.168.122.209 [70420.682648] [tdb] Close table 'filter0.tdb' Apr 26 11:37:49 192.168.122.209 [70420.683062] [tempesta fw] modules are stopped Apr 26 11:37:50 192.168.122.209 [70420.848721] [tempesta fw] exiting... Apr 26 11:37:50 192.168.122.209 [70420.995741] [tdb] Shutdown Tempesta DB Apr 26 11:37:50 192.168.122.209 [70421.407031] End test: cache.test_cache.TestCacheMultipleMethodsH2.test_several_entries_GET_HEAD Apr 26 11:37:50 192.168.122.209 [70421.442505] Start test: cache.test_cache.TestCacheMultipleMethodsH2.test_several_entries_GET_POST Apr 26 11:37:52 192.168.122.209 [70422.782077] [tdb] Start Tempesta DB Apr 26 11:37:52 192.168.122.209 [70422.901942] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:37:53 192.168.122.209 [70424.472610] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70424.472610] Maybe that's fine, but it's worth checking the [70424.472610] config - if there is no relations between the [70424.472610] names, then host name confusion attack is possible. Apr 26 11:37:53 192.168.122.209 [70424.547432] [tempesta fw] Configuration processing is completed. Apr 26 11:37:53 192.168.122.209 [70424.599201] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:37:54 192.168.122.209 [70425.010645] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:37:54 192.168.122.209 [70425.036660] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:37:54 192.168.122.209 [70425.061583] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:37:54 192.168.122.209 [70425.107403] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:37:54 192.168.122.209 [70425.109123] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:37:54 192.168.122.209 [70425.155317] [tempesta fw] Tempesta FW is ready Apr 26 11:37:55 192.168.122.209 [70425.804085] [tdb] Close table 'client0.tdb' Apr 26 11:37:55 192.168.122.209 [70425.994616] [tdb] Close table 'sessions0.tdb' Apr 26 11:37:58 192.168.122.209 [70429.176508] [tdb] Close table 'cache0.tdb' Apr 26 11:37:58 192.168.122.209 [70429.402548] [tdb] Close table 'filter0.tdb' Apr 26 11:37:58 192.168.122.209 [70429.402969] [tempesta fw] modules are stopped Apr 26 11:37:58 192.168.122.209 [70429.596938] [tempesta fw] exiting... Apr 26 11:37:59 192.168.122.209 [70429.728763] [tdb] Shutdown Tempesta DB Apr 26 11:37:59 192.168.122.209 [70430.120088] End test: cache.test_cache.TestCacheMultipleMethodsH2.test_several_entries_GET_POST Apr 26 11:37:59 192.168.122.209 [70430.150814] Start test: cache.test_cache.TestCacheMultipleMethodsH2.test_several_entries_POST_GET Apr 26 11:38:00 192.168.122.209 [70431.513188] [tdb] Start Tempesta DB Apr 26 11:38:00 192.168.122.209 [70431.647706] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:38:02 192.168.122.209 [70433.132715] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70433.132715] Maybe that's fine, but it's worth checking the [70433.132715] config - if there is no relations between the [70433.132715] names, then host name confusion attack is possible. Apr 26 11:38:02 192.168.122.209 [70433.219566] [tempesta fw] Configuration processing is completed. Apr 26 11:38:02 192.168.122.209 [70433.271120] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:38:02 192.168.122.209 [70433.678821] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:38:03 192.168.122.209 [70433.705717] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:38:03 192.168.122.209 [70433.732088] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:38:03 192.168.122.209 [70433.771492] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:38:03 192.168.122.209 [70433.773300] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:38:03 192.168.122.209 [70433.811443] [tempesta fw] Tempesta FW is ready Apr 26 11:38:05 192.168.122.209 [70436.406380] [tdb] Close table 'client0.tdb' Apr 26 11:38:05 192.168.122.209 [70436.595080] [tdb] Close table 'sessions0.tdb' Apr 26 11:38:09 192.168.122.209 [70439.784676] [tdb] Close table 'cache0.tdb' Apr 26 11:38:09 192.168.122.209 [70440.004674] [tdb] Close table 'filter0.tdb' Apr 26 11:38:09 192.168.122.209 [70440.005098] [tempesta fw] modules are stopped Apr 26 11:38:09 192.168.122.209 [70440.212135] [tempesta fw] exiting... Apr 26 11:38:09 192.168.122.209 [70440.325715] [tdb] Shutdown Tempesta DB Apr 26 11:38:10 192.168.122.209 [70440.710658] End test: cache.test_cache.TestCacheMultipleMethodsH2.test_several_entries_POST_GET Apr 26 11:38:10 192.168.122.209 [70440.790239] Start test: cache.test_cache.TestCacheMultipleMethodsH2.test_several_entries_POST_HEAD Apr 26 11:38:11 192.168.122.209 [70442.156576] [tdb] Start Tempesta DB Apr 26 11:38:11 192.168.122.209 [70442.297179] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:38:13 192.168.122.209 [70443.754665] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70443.754665] Maybe that's fine, but it's worth checking the [70443.754665] config - if there is no relations between the [70443.754665] names, then host name confusion attack is possible. Apr 26 11:38:13 192.168.122.209 [70443.807859] [tempesta fw] Configuration processing is completed. Apr 26 11:38:13 192.168.122.209 [70443.861648] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:38:13 192.168.122.209 [70444.273822] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:38:13 192.168.122.209 [70444.300672] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:38:13 192.168.122.209 [70444.328635] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:38:13 192.168.122.209 [70444.371618] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:38:13 192.168.122.209 [70444.373358] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:38:13 192.168.122.209 [70444.415591] [tempesta fw] Tempesta FW is ready Apr 26 11:38:16 192.168.122.209 [70447.093892] [tdb] Close table 'client0.tdb' Apr 26 11:38:16 192.168.122.209 [70447.278178] [tdb] Close table 'sessions0.tdb' Apr 26 11:38:19 192.168.122.209 [70450.429551] [tdb] Close table 'cache0.tdb' Apr 26 11:38:20 192.168.122.209 [70450.702667] [tdb] Close table 'filter0.tdb' Apr 26 11:38:20 192.168.122.209 [70450.703079] [tempesta fw] modules are stopped Apr 26 11:38:20 192.168.122.209 [70450.912488] [tempesta fw] exiting... Apr 26 11:38:20 192.168.122.209 [70451.054215] [tdb] Shutdown Tempesta DB Apr 26 11:38:20 192.168.122.209 [70451.504582] End test: cache.test_cache.TestCacheMultipleMethodsH2.test_several_entries_POST_HEAD Apr 26 11:38:20 192.168.122.209 [70451.540600] Start test: cache.test_cache.TestCacheMultipleMethodsH2.test_several_entries_POST_POST Apr 26 11:38:22 192.168.122.209 [70452.896043] [tdb] Start Tempesta DB Apr 26 11:38:22 192.168.122.209 [70453.024941] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:38:23 192.168.122.209 [70454.588997] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70454.588997] Maybe that's fine, but it's worth checking the [70454.588997] config - if there is no relations between the [70454.588997] names, then host name confusion attack is possible. Apr 26 11:38:23 192.168.122.209 [70454.655780] [tempesta fw] Configuration processing is completed. Apr 26 11:38:24 192.168.122.209 [70454.722899] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:38:24 192.168.122.209 [70455.142074] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:38:24 192.168.122.209 [70455.167954] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:38:24 192.168.122.209 [70455.194325] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:38:24 192.168.122.209 [70455.239757] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:38:24 192.168.122.209 [70455.241490] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:38:24 192.168.122.209 [70455.279703] [tempesta fw] Tempesta FW is ready Apr 26 11:38:25 192.168.122.209 [70455.941404] [tdb] Close table 'client0.tdb' Apr 26 11:38:25 192.168.122.209 [70456.122256] [tdb] Close table 'sessions0.tdb' Apr 26 11:38:28 192.168.122.209 [70459.292675] [tdb] Close table 'cache0.tdb' Apr 26 11:38:28 192.168.122.209 [70459.567772] [tdb] Close table 'filter0.tdb' Apr 26 11:38:28 192.168.122.209 [70459.568198] [tempesta fw] modules are stopped Apr 26 11:38:29 192.168.122.209 [70459.776386] [tempesta fw] exiting... Apr 26 11:38:29 192.168.122.209 [70459.927090] [tdb] Shutdown Tempesta DB Apr 26 11:38:29 192.168.122.209 [70460.356752] End test: cache.test_cache.TestCacheMultipleMethodsH2.test_several_entries_POST_POST Apr 26 11:38:29 192.168.122.209 [70460.388419] Start test: cache.test_cache.TestCacheMultipleMethodsH2.test_update_cache_via_DELETE_request Apr 26 11:38:31 192.168.122.209 [70461.799224] [tdb] Start Tempesta DB Apr 26 11:38:31 192.168.122.209 [70461.933630] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:38:32 192.168.122.209 [70463.461108] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70463.461108] Maybe that's fine, but it's worth checking the [70463.461108] config - if there is no relations between the [70463.461108] names, then host name confusion attack is possible. Apr 26 11:38:32 192.168.122.209 [70463.532199] [tempesta fw] Configuration processing is completed. Apr 26 11:38:32 192.168.122.209 [70463.583998] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:38:33 192.168.122.209 [70464.012150] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:38:33 192.168.122.209 [70464.038248] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:38:33 192.168.122.209 [70464.064387] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:38:33 192.168.122.209 [70464.107832] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:38:33 192.168.122.209 [70464.109394] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:38:33 192.168.122.209 [70464.147850] [tempesta fw] Tempesta FW is ready Apr 26 11:38:34 192.168.122.209 [70464.810745] [tdb] Close table 'client0.tdb' Apr 26 11:38:34 192.168.122.209 [70464.984608] [tdb] Close table 'sessions0.tdb' Apr 26 11:38:37 192.168.122.209 [70468.150747] [tdb] Close table 'cache0.tdb' Apr 26 11:38:37 192.168.122.209 [70468.385469] [tdb] Close table 'filter0.tdb' Apr 26 11:38:37 192.168.122.209 [70468.386186] [tempesta fw] modules are stopped Apr 26 11:38:37 192.168.122.209 [70468.568424] [tempesta fw] exiting... Apr 26 11:38:38 192.168.122.209 [70468.696402] [tdb] Shutdown Tempesta DB Apr 26 11:38:38 192.168.122.209 [70469.127725] End test: cache.test_cache.TestCacheMultipleMethodsH2.test_update_cache_via_DELETE_request Apr 26 11:38:38 192.168.122.209 [70469.153821] Start test: cache.test_cache.TestCacheMultipleMethodsH2.test_update_cache_via_PUT_request Apr 26 11:38:39 192.168.122.209 [70470.539849] [tdb] Start Tempesta DB Apr 26 11:38:39 192.168.122.209 [70470.666715] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:38:41 192.168.122.209 [70472.173270] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70472.173270] Maybe that's fine, but it's worth checking the [70472.173270] config - if there is no relations between the [70472.173270] names, then host name confusion attack is possible. Apr 26 11:38:41 192.168.122.209 [70472.240003] [tempesta fw] Configuration processing is completed. Apr 26 11:38:41 192.168.122.209 [70472.290845] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:38:42 192.168.122.209 [70472.706670] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:38:42 192.168.122.209 [70472.732864] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:38:42 192.168.122.209 [70472.759120] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:38:42 192.168.122.209 [70472.800001] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:38:42 192.168.122.209 [70472.801736] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:38:42 192.168.122.209 [70472.839949] [tempesta fw] Tempesta FW is ready Apr 26 11:38:42 192.168.122.209 [70473.499570] [tdb] Close table 'client0.tdb' Apr 26 11:38:42 192.168.122.209 [70473.682696] [tdb] Close table 'sessions0.tdb' Apr 26 11:38:46 192.168.122.209 [70476.837341] [tdb] Close table 'cache0.tdb' Apr 26 11:38:46 192.168.122.209 [70477.093397] [tdb] Close table 'filter0.tdb' Apr 26 11:38:46 192.168.122.209 [70477.093843] [tempesta fw] modules are stopped Apr 26 11:38:46 192.168.122.209 [70477.268351] [tempesta fw] exiting... Apr 26 11:38:46 192.168.122.209 [70477.406972] [tdb] Shutdown Tempesta DB Apr 26 11:38:47 192.168.122.209 [70477.777642] End test: cache.test_cache.TestCacheMultipleMethodsH2.test_update_cache_via_PUT_request Apr 26 11:38:47 192.168.122.209 [70477.808304] Start test: cache.test_cache.TestCacheMultipleMethodsHttp.test_GET_after_GET Apr 26 11:38:48 192.168.122.209 [70479.179421] [tdb] Start Tempesta DB Apr 26 11:38:48 192.168.122.209 [70479.322914] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:38:50 192.168.122.209 [70480.877412] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70480.877412] Maybe that's fine, but it's worth checking the [70480.877412] config - if there is no relations between the [70480.877412] names, then host name confusion attack is possible. Apr 26 11:38:50 192.168.122.209 [70480.940536] [tempesta fw] Configuration processing is completed. Apr 26 11:38:50 192.168.122.209 [70480.998459] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:38:50 192.168.122.209 [70481.416000] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:38:50 192.168.122.209 [70481.442105] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:38:50 192.168.122.209 [70481.467483] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:38:50 192.168.122.209 [70481.508096] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:38:50 192.168.122.209 [70481.509842] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:38:50 192.168.122.209 [70481.548087] [tempesta fw] Tempesta FW is ready Apr 26 11:38:51 192.168.122.209 [70482.231056] [tdb] Close table 'client0.tdb' Apr 26 11:38:51 192.168.122.209 [70482.420171] [tdb] Close table 'sessions0.tdb' Apr 26 11:38:54 192.168.122.209 [70485.555443] [tdb] Close table 'cache0.tdb' Apr 26 11:38:55 192.168.122.209 [70485.821584] [tdb] Close table 'filter0.tdb' Apr 26 11:38:55 192.168.122.209 [70485.822006] [tempesta fw] modules are stopped Apr 26 11:38:55 192.168.122.209 [70485.993453] [tempesta fw] exiting... Apr 26 11:38:55 192.168.122.209 [70486.121623] [tdb] Shutdown Tempesta DB Apr 26 11:38:55 192.168.122.209 [70486.541868] End test: cache.test_cache.TestCacheMultipleMethodsHttp.test_GET_after_GET Apr 26 11:38:55 192.168.122.209 [70486.568091] Start test: cache.test_cache.TestCacheMultipleMethodsHttp.test_GET_after_HEAD Apr 26 11:38:57 192.168.122.209 [70487.977183] [tdb] Start Tempesta DB Apr 26 11:38:57 192.168.122.209 [70488.107655] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:38:58 192.168.122.209 [70489.597524] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70489.597524] Maybe that's fine, but it's worth checking the [70489.597524] config - if there is no relations between the [70489.597524] names, then host name confusion attack is possible. Apr 26 11:38:58 192.168.122.209 [70489.668261] [tempesta fw] Configuration processing is completed. Apr 26 11:38:59 192.168.122.209 [70489.726469] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:38:59 192.168.122.209 [70490.147089] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:38:59 192.168.122.209 [70490.181864] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:38:59 192.168.122.209 [70490.207671] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:38:59 192.168.122.209 [70490.252217] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:38:59 192.168.122.209 [70490.253946] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:38:59 192.168.122.209 [70490.292150] [tempesta fw] Tempesta FW is ready Apr 26 11:39:00 192.168.122.209 [70490.896936] [tdb] Close table 'client0.tdb' Apr 26 11:39:00 192.168.122.209 [70491.079775] [tdb] Close table 'sessions0.tdb' Apr 26 11:39:03 192.168.122.209 [70494.246425] [tdb] Close table 'cache0.tdb' Apr 26 11:39:03 192.168.122.209 [70494.505942] [tdb] Close table 'filter0.tdb' Apr 26 11:39:03 192.168.122.209 [70494.506341] [tempesta fw] modules are stopped Apr 26 11:39:04 192.168.122.209 [70494.699840] [tempesta fw] exiting... Apr 26 11:39:04 192.168.122.209 [70494.834094] [tdb] Shutdown Tempesta DB Apr 26 11:39:04 192.168.122.209 [70495.229256] End test: cache.test_cache.TestCacheMultipleMethodsHttp.test_GET_after_HEAD Apr 26 11:39:04 192.168.122.209 [70495.313074] Start test: cache.test_cache.TestCacheMultipleMethodsHttp.test_HEAD_after_GET Apr 26 11:39:06 192.168.122.209 [70496.703363] [tdb] Start Tempesta DB Apr 26 11:39:06 192.168.122.209 [70496.849769] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:39:07 192.168.122.209 [70498.329741] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70498.329741] Maybe that's fine, but it's worth checking the [70498.329741] config - if there is no relations between the [70498.329741] names, then host name confusion attack is possible. Apr 26 11:39:07 192.168.122.209 [70498.408324] [tempesta fw] Configuration processing is completed. Apr 26 11:39:07 192.168.122.209 [70498.474791] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:39:08 192.168.122.209 [70498.886449] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:39:08 192.168.122.209 [70498.912062] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:39:08 192.168.122.209 [70498.936750] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:39:08 192.168.122.209 [70498.976268] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:39:08 192.168.122.209 [70498.978000] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:39:08 192.168.122.209 [70499.016301] [tempesta fw] Tempesta FW is ready Apr 26 11:39:08 192.168.122.209 [70499.660285] [tdb] Close table 'client0.tdb' Apr 26 11:39:09 192.168.122.209 [70499.845084] [tdb] Close table 'sessions0.tdb' Apr 26 11:39:12 192.168.122.209 [70502.989861] [tdb] Close table 'cache0.tdb' Apr 26 11:39:12 192.168.122.209 [70503.222767] [tdb] Close table 'filter0.tdb' Apr 26 11:39:12 192.168.122.209 [70503.223206] [tempesta fw] modules are stopped Apr 26 11:39:12 192.168.122.209 [70503.411953] [tempesta fw] exiting... Apr 26 11:39:12 192.168.122.209 [70503.561329] [tdb] Shutdown Tempesta DB Apr 26 11:39:13 192.168.122.209 [70503.920568] End test: cache.test_cache.TestCacheMultipleMethodsHttp.test_HEAD_after_GET Apr 26 11:39:13 192.168.122.209 [70503.967441] Start test: cache.test_cache.TestCacheMultipleMethodsHttp.test_HEAD_after_HEAD Apr 26 11:39:14 192.168.122.209 [70505.386204] [tdb] Start Tempesta DB Apr 26 11:39:14 192.168.122.209 [70505.511143] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:39:16 192.168.122.209 [70506.969723] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70506.969723] Maybe that's fine, but it's worth checking the [70506.969723] config - if there is no relations between the [70506.969723] names, then host name confusion attack is possible. Apr 26 11:39:16 192.168.122.209 [70507.044502] [tempesta fw] Configuration processing is completed. Apr 26 11:39:16 192.168.122.209 [70507.102118] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:39:16 192.168.122.209 [70507.523139] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:39:16 192.168.122.209 [70507.551671] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:39:16 192.168.122.209 [70507.578649] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:39:16 192.168.122.209 [70507.628440] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:39:16 192.168.122.209 [70507.630170] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:39:16 192.168.122.209 [70507.688395] [tempesta fw] Tempesta FW is ready Apr 26 11:39:17 192.168.122.209 [70508.327387] [tdb] Close table 'client0.tdb' Apr 26 11:39:17 192.168.122.209 [70508.511323] [tdb] Close table 'sessions0.tdb' Apr 26 11:39:20 192.168.122.209 [70511.656697] [tdb] Close table 'cache0.tdb' Apr 26 11:39:21 192.168.122.209 [70511.908997] [tdb] Close table 'filter0.tdb' Apr 26 11:39:21 192.168.122.209 [70511.909427] [tempesta fw] modules are stopped Apr 26 11:39:21 192.168.122.209 [70512.092316] [tempesta fw] exiting... Apr 26 11:39:21 192.168.122.209 [70512.218935] [tdb] Shutdown Tempesta DB Apr 26 11:39:21 192.168.122.209 [70512.654702] End test: cache.test_cache.TestCacheMultipleMethodsHttp.test_HEAD_after_HEAD Apr 26 11:39:21 192.168.122.209 [70512.684585] Start test: cache.test_cache.TestCacheMultipleMethodsHttp.test_POST_after_GET Apr 26 11:39:23 192.168.122.209 [70513.991349] [tdb] Start Tempesta DB Apr 26 11:39:23 192.168.122.209 [70514.130978] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:39:25 192.168.122.209 [70515.705841] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70515.705841] Maybe that's fine, but it's worth checking the [70515.705841] config - if there is no relations between the [70515.705841] names, then host name confusion attack is possible. Apr 26 11:39:25 192.168.122.209 [70515.788508] [tempesta fw] Configuration processing is completed. Apr 26 11:39:25 192.168.122.209 [70515.846381] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:39:25 192.168.122.209 [70516.261097] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:39:25 192.168.122.209 [70516.287241] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:39:25 192.168.122.209 [70516.315183] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:39:25 192.168.122.209 [70516.364551] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:39:25 192.168.122.209 [70516.366268] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:39:25 192.168.122.209 [70516.408499] [tempesta fw] Tempesta FW is ready Apr 26 11:39:26 192.168.122.209 [70517.078089] [tdb] Close table 'client0.tdb' Apr 26 11:39:26 192.168.122.209 [70517.265137] [tdb] Close table 'sessions0.tdb' Apr 26 11:39:29 192.168.122.209 [70520.499236] [tdb] Close table 'cache0.tdb' Apr 26 11:39:30 192.168.122.209 [70520.756932] [tdb] Close table 'filter0.tdb' Apr 26 11:39:30 192.168.122.209 [70520.757376] [tempesta fw] modules are stopped Apr 26 11:39:30 192.168.122.209 [70520.925920] [tempesta fw] exiting... Apr 26 11:39:30 192.168.122.209 [70521.060053] [tdb] Shutdown Tempesta DB Apr 26 11:39:30 192.168.122.209 [70521.488345] End test: cache.test_cache.TestCacheMultipleMethodsHttp.test_POST_after_GET Apr 26 11:39:30 192.168.122.209 [70521.519383] Start test: cache.test_cache.TestCacheMultipleMethodsHttp.test_POST_after_HEAD Apr 26 11:39:32 192.168.122.209 [70522.866168] [tdb] Start Tempesta DB Apr 26 11:39:32 192.168.122.209 [70522.990090] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:39:33 192.168.122.209 [70524.521912] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70524.521912] Maybe that's fine, but it's worth checking the [70524.521912] config - if there is no relations between the [70524.521912] names, then host name confusion attack is possible. Apr 26 11:39:33 192.168.122.209 [70524.592653] [tempesta fw] Configuration processing is completed. Apr 26 11:39:33 192.168.122.209 [70524.644880] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:39:34 192.168.122.209 [70525.066887] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:39:34 192.168.122.209 [70525.092272] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:39:34 192.168.122.209 [70525.117010] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:39:34 192.168.122.209 [70525.160751] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:39:34 192.168.122.209 [70525.162370] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:39:34 192.168.122.209 [70525.212630] [tempesta fw] Tempesta FW is ready Apr 26 11:39:35 192.168.122.209 [70525.844705] [tdb] Close table 'client0.tdb' Apr 26 11:39:35 192.168.122.209 [70526.025087] [tdb] Close table 'sessions0.tdb' Apr 26 11:39:38 192.168.122.209 [70529.197227] [tdb] Close table 'cache0.tdb' Apr 26 11:39:38 192.168.122.209 [70529.441171] [tdb] Close table 'filter0.tdb' Apr 26 11:39:38 192.168.122.209 [70529.441587] [tempesta fw] modules are stopped Apr 26 11:39:38 192.168.122.209 [70529.644281] [tempesta fw] exiting... Apr 26 11:39:39 192.168.122.209 [70529.806971] [tdb] Shutdown Tempesta DB Apr 26 11:39:39 192.168.122.209 [70530.106713] End test: cache.test_cache.TestCacheMultipleMethodsHttp.test_POST_after_HEAD Apr 26 11:39:39 192.168.122.209 [70530.186141] Start test: cache.test_cache.TestCacheMultipleMethodsHttp.test_cache_POST_request_not_cached_no_cache_control Apr 26 11:39:40 192.168.122.209 [70531.571466] [tdb] Start Tempesta DB Apr 26 11:39:41 192.168.122.209 [70531.700945] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:39:42 192.168.122.209 [70533.242035] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70533.242035] Maybe that's fine, but it's worth checking the [70533.242035] config - if there is no relations between the [70533.242035] names, then host name confusion attack is possible. Apr 26 11:39:42 192.168.122.209 [70533.312801] [tempesta fw] Configuration processing is completed. Apr 26 11:39:42 192.168.122.209 [70533.363849] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:39:43 192.168.122.209 [70533.784527] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:39:43 192.168.122.209 [70533.810631] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:39:43 192.168.122.209 [70533.837239] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:39:43 192.168.122.209 [70533.876784] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:39:43 192.168.122.209 [70533.877959] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:39:43 192.168.122.209 [70533.916722] [tempesta fw] Tempesta FW is ready Apr 26 11:39:43 192.168.122.209 [70534.533925] [tdb] Close table 'client0.tdb' Apr 26 11:39:44 192.168.122.209 [70534.726482] [tdb] Close table 'sessions0.tdb' Apr 26 11:39:47 192.168.122.209 [70537.901332] [tdb] Close table 'cache0.tdb' Apr 26 11:39:47 192.168.122.209 [70538.151107] [tdb] Close table 'filter0.tdb' Apr 26 11:39:47 192.168.122.209 [70538.151540] [tempesta fw] modules are stopped Apr 26 11:39:47 192.168.122.209 [70538.347390] [tempesta fw] exiting... Apr 26 11:39:47 192.168.122.209 [70538.524269] [tdb] Shutdown Tempesta DB Apr 26 11:39:48 192.168.122.209 [70538.951971] End test: cache.test_cache.TestCacheMultipleMethodsHttp.test_cache_POST_request_not_cached_no_cache_control Apr 26 11:39:48 192.168.122.209 [70538.978811] Start test: cache.test_cache.TestCacheMultipleMethodsHttp.test_cache_POST_request_not_cached_not_same_location Apr 26 11:39:49 192.168.122.209 [70540.399506] [tdb] Start Tempesta DB Apr 26 11:39:49 192.168.122.209 [70540.540690] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:39:51 192.168.122.209 [70542.106131] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70542.106131] Maybe that's fine, but it's worth checking the [70542.106131] config - if there is no relations between the [70542.106131] names, then host name confusion attack is possible. Apr 26 11:39:51 192.168.122.209 [70542.192890] [tempesta fw] Configuration processing is completed. Apr 26 11:39:51 192.168.122.209 [70542.244765] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:39:51 192.168.122.209 [70542.654536] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:39:51 192.168.122.209 [70542.679880] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:39:52 192.168.122.209 [70542.704997] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:39:52 192.168.122.209 [70542.772894] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:39:52 192.168.122.209 [70542.774646] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:39:52 192.168.122.209 [70542.812854] [tempesta fw] Tempesta FW is ready Apr 26 11:39:52 192.168.122.209 [70543.483951] [tdb] Close table 'client0.tdb' Apr 26 11:39:52 192.168.122.209 [70543.665204] [tdb] Close table 'sessions0.tdb' Apr 26 11:39:56 192.168.122.209 [70546.824600] [tdb] Close table 'cache0.tdb' Apr 26 11:39:56 192.168.122.209 [70547.079199] [tdb] Close table 'filter0.tdb' Apr 26 11:39:56 192.168.122.209 [70547.079649] [tempesta fw] modules are stopped Apr 26 11:39:56 192.168.122.209 [70547.253608] [tempesta fw] exiting... Apr 26 11:39:56 192.168.122.209 [70547.374686] [tdb] Shutdown Tempesta DB Apr 26 11:39:57 192.168.122.209 [70547.746761] End test: cache.test_cache.TestCacheMultipleMethodsHttp.test_cache_POST_request_not_cached_not_same_location Apr 26 11:39:57 192.168.122.209 [70547.780545] Start test: cache.test_cache.TestCacheMultipleMethodsHttp.test_cache_POST_request_with_location_GET Apr 26 11:39:58 192.168.122.209 [70549.166838] [tdb] Start Tempesta DB Apr 26 11:39:58 192.168.122.209 [70549.304348] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:40:00 192.168.122.209 [70550.778248] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70550.778248] Maybe that's fine, but it's worth checking the [70550.778248] config - if there is no relations between the [70550.778248] names, then host name confusion attack is possible. Apr 26 11:40:00 192.168.122.209 [70550.849001] [tempesta fw] Configuration processing is completed. Apr 26 11:40:00 192.168.122.209 [70550.899731] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:40:00 192.168.122.209 [70551.316512] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:40:00 192.168.122.209 [70551.342894] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:40:00 192.168.122.209 [70551.368673] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:40:00 192.168.122.209 [70551.408999] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:40:00 192.168.122.209 [70551.410725] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:40:00 192.168.122.209 [70551.464972] [tempesta fw] Tempesta FW is ready Apr 26 11:40:01 192.168.122.209 [70552.078929] [tdb] Close table 'client0.tdb' Apr 26 11:40:01 192.168.122.209 [70552.247629] [tdb] Close table 'sessions0.tdb' Apr 26 11:40:04 192.168.122.209 [70555.406342] [tdb] Close table 'cache0.tdb' Apr 26 11:40:04 192.168.122.209 [70555.653024] [tdb] Close table 'filter0.tdb' Apr 26 11:40:04 192.168.122.209 [70555.653458] [tempesta fw] modules are stopped Apr 26 11:40:05 192.168.122.209 [70555.873207] [tempesta fw] exiting... Apr 26 11:40:05 192.168.122.209 [70555.986840] [tdb] Shutdown Tempesta DB Apr 26 11:40:05 192.168.122.209 [70556.370673] End test: cache.test_cache.TestCacheMultipleMethodsHttp.test_cache_POST_request_with_location_GET Apr 26 11:40:05 192.168.122.209 [70556.398958] Start test: cache.test_cache.TestCacheMultipleMethodsHttp.test_cache_POST_request_with_location_HEAD Apr 26 11:40:07 192.168.122.209 [70557.778125] [tdb] Start Tempesta DB Apr 26 11:40:07 192.168.122.209 [70557.910644] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:40:08 192.168.122.209 [70559.346359] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70559.346359] Maybe that's fine, but it's worth checking the [70559.346359] config - if there is no relations between the [70559.346359] names, then host name confusion attack is possible. Apr 26 11:40:08 192.168.122.209 [70559.405149] [tempesta fw] Configuration processing is completed. Apr 26 11:40:08 192.168.122.209 [70559.456942] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:40:09 192.168.122.209 [70559.881842] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:40:09 192.168.122.209 [70559.907516] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:40:09 192.168.122.209 [70559.932623] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:40:09 192.168.122.209 [70559.981110] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:40:09 192.168.122.209 [70559.982851] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:40:09 192.168.122.209 [70560.041063] [tempesta fw] Tempesta FW is ready Apr 26 11:40:10 192.168.122.209 [70560.704529] [tdb] Close table 'client0.tdb' Apr 26 11:40:10 192.168.122.209 [70560.889078] [tdb] Close table 'sessions0.tdb' Apr 26 11:40:13 192.168.122.209 [70564.022503] [tdb] Close table 'cache0.tdb' Apr 26 11:40:13 192.168.122.209 [70564.284783] [tdb] Close table 'filter0.tdb' Apr 26 11:40:13 192.168.122.209 [70564.285253] [tempesta fw] modules are stopped Apr 26 11:40:13 192.168.122.209 [70564.469544] [tempesta fw] exiting... Apr 26 11:40:13 192.168.122.209 [70564.631899] [tdb] Shutdown Tempesta DB Apr 26 11:40:14 192.168.122.209 [70564.991312] End test: cache.test_cache.TestCacheMultipleMethodsHttp.test_cache_POST_request_with_location_HEAD Apr 26 11:40:14 192.168.122.209 [70565.029446] Start test: cache.test_cache.TestCacheMultipleMethodsHttp.test_cache_POST_request_with_location_POST Apr 26 11:40:15 192.168.122.209 [70566.429631] [tdb] Start Tempesta DB Apr 26 11:40:15 192.168.122.209 [70566.551366] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:40:17 192.168.122.209 [70568.086614] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70568.086614] Maybe that's fine, but it's worth checking the [70568.086614] config - if there is no relations between the [70568.086614] names, then host name confusion attack is possible. Apr 26 11:40:17 192.168.122.209 [70568.157292] [tempesta fw] Configuration processing is completed. Apr 26 11:40:17 192.168.122.209 [70568.211626] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:40:17 192.168.122.209 [70568.624809] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:40:17 192.168.122.209 [70568.652057] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:40:17 192.168.122.209 [70568.678907] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:40:18 192.168.122.209 [70568.721223] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:40:18 192.168.122.209 [70568.724718] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:40:18 192.168.122.209 [70568.777133] [tempesta fw] Tempesta FW is ready Apr 26 11:40:18 192.168.122.209 [70569.394926] [tdb] Close table 'client0.tdb' Apr 26 11:40:18 192.168.122.209 [70569.584504] [tdb] Close table 'sessions0.tdb' Apr 26 11:40:22 192.168.122.209 [70572.751382] [tdb] Close table 'cache0.tdb' Apr 26 11:40:22 192.168.122.209 [70573.008186] [tdb] Close table 'filter0.tdb' Apr 26 11:40:22 192.168.122.209 [70573.008594] [tempesta fw] modules are stopped Apr 26 11:40:22 192.168.122.209 [70573.206187] [tempesta fw] exiting... Apr 26 11:40:22 192.168.122.209 [70573.541072] [tdb] Shutdown Tempesta DB Apr 26 11:40:23 192.168.122.209 [70574.402999] End test: cache.test_cache.TestCacheMultipleMethodsHttp.test_cache_POST_request_with_location_POST Apr 26 11:40:23 192.168.122.209 [70574.510737] Start test: cache.test_cache.TestCacheMultipleMethodsHttp.test_several_entries_GET_GET Apr 26 11:40:25 192.168.122.209 [70576.192334] [tdb] Start Tempesta DB Apr 26 11:40:25 192.168.122.209 [70576.367566] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:40:28 192.168.122.209 [70579.351970] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70579.351970] Maybe that's fine, but it's worth checking the [70579.351970] config - if there is no relations between the [70579.351970] names, then host name confusion attack is possible. Apr 26 11:40:28 192.168.122.209 [70579.401618] [tempesta fw] Configuration processing is completed. Apr 26 11:40:28 192.168.122.209 [70579.449758] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:40:29 192.168.122.209 [70579.887502] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:40:29 192.168.122.209 [70579.915090] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:40:29 192.168.122.209 [70579.942795] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:40:29 192.168.122.209 [70580.037339] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:40:29 192.168.122.209 [70580.039121] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:40:29 192.168.122.209 [70580.249403] [tempesta fw] Tempesta FW is ready Apr 26 11:40:32 192.168.122.209 [70582.975419] [tdb] Close table 'client0.tdb' Apr 26 11:40:32 192.168.122.209 [70583.155146] [tdb] Close table 'sessions0.tdb' Apr 26 11:40:35 192.168.122.209 [70586.389085] [tdb] Close table 'cache0.tdb' Apr 26 11:40:35 192.168.122.209 [70586.632098] [tdb] Close table 'filter0.tdb' Apr 26 11:40:35 192.168.122.209 [70586.632515] [tempesta fw] modules are stopped Apr 26 11:40:36 192.168.122.209 [70586.814894] [tempesta fw] exiting... Apr 26 11:40:36 192.168.122.209 [70586.931099] [tdb] Shutdown Tempesta DB Apr 26 11:40:36 192.168.122.209 [70587.381460] End test: cache.test_cache.TestCacheMultipleMethodsHttp.test_several_entries_GET_GET Apr 26 11:40:36 192.168.122.209 [70587.413522] Start test: cache.test_cache.TestCacheMultipleMethodsHttp.test_several_entries_GET_HEAD Apr 26 11:40:38 192.168.122.209 [70588.891190] [tdb] Start Tempesta DB Apr 26 11:40:38 192.168.122.209 [70589.018588] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:40:39 192.168.122.209 [70590.538760] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70590.538760] Maybe that's fine, but it's worth checking the [70590.538760] config - if there is no relations between the [70590.538760] names, then host name confusion attack is possible. Apr 26 11:40:39 192.168.122.209 [70590.610761] [tempesta fw] Configuration processing is completed. Apr 26 11:40:39 192.168.122.209 [70590.666326] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:40:40 192.168.122.209 [70591.082565] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:40:40 192.168.122.209 [70591.111129] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:40:40 192.168.122.209 [70591.137817] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:40:40 192.168.122.209 [70591.177549] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:40:40 192.168.122.209 [70591.179270] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:40:40 192.168.122.209 [70591.222758] [tempesta fw] Tempesta FW is ready Apr 26 11:40:43 192.168.122.209 [70593.916083] [tdb] Close table 'client0.tdb' Apr 26 11:40:43 192.168.122.209 [70594.084741] [tdb] Close table 'sessions0.tdb' Apr 26 11:40:46 192.168.122.209 [70597.254078] [tdb] Close table 'cache0.tdb' Apr 26 11:40:46 192.168.122.209 [70597.495602] [tdb] Close table 'filter0.tdb' Apr 26 11:40:46 192.168.122.209 [70597.496050] [tempesta fw] modules are stopped Apr 26 11:40:47 192.168.122.209 [70597.745916] [tempesta fw] exiting... Apr 26 11:40:47 192.168.122.209 [70597.853675] [tdb] Shutdown Tempesta DB Apr 26 11:40:47 192.168.122.209 [70598.286387] End test: cache.test_cache.TestCacheMultipleMethodsHttp.test_several_entries_GET_HEAD Apr 26 11:40:47 192.168.122.209 [70598.319303] Start test: cache.test_cache.TestCacheMultipleMethodsHttp.test_several_entries_GET_POST Apr 26 11:40:49 192.168.122.209 [70599.794268] [tdb] Start Tempesta DB Apr 26 11:40:49 192.168.122.209 [70599.929024] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:40:50 192.168.122.209 [70601.394955] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70601.394955] Maybe that's fine, but it's worth checking the [70601.394955] config - if there is no relations between the [70601.394955] names, then host name confusion attack is possible. Apr 26 11:40:50 192.168.122.209 [70601.469824] [tempesta fw] Configuration processing is completed. Apr 26 11:40:50 192.168.122.209 [70601.525861] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:40:51 192.168.122.209 [70601.945736] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:40:51 192.168.122.209 [70601.988593] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:40:51 192.168.122.209 [70602.014828] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:40:51 192.168.122.209 [70602.053670] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:40:51 192.168.122.209 [70602.055358] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:40:51 192.168.122.209 [70602.097613] [tempesta fw] Tempesta FW is ready Apr 26 11:40:52 192.168.122.209 [70602.756238] [tdb] Close table 'client0.tdb' Apr 26 11:40:52 192.168.122.209 [70602.925571] [tdb] Close table 'sessions0.tdb' Apr 26 11:40:55 192.168.122.209 [70606.106162] [tdb] Close table 'cache0.tdb' Apr 26 11:40:55 192.168.122.209 [70606.352825] [tdb] Close table 'filter0.tdb' Apr 26 11:40:55 192.168.122.209 [70606.353261] [tempesta fw] modules are stopped Apr 26 11:40:55 192.168.122.209 [70606.543150] [tempesta fw] exiting... Apr 26 11:40:56 192.168.122.209 [70606.696820] [tdb] Shutdown Tempesta DB Apr 26 11:40:56 192.168.122.209 [70607.073158] End test: cache.test_cache.TestCacheMultipleMethodsHttp.test_several_entries_GET_POST Apr 26 11:40:56 192.168.122.209 [70607.107699] Start test: cache.test_cache.TestCacheMultipleMethodsHttp.test_several_entries_POST_GET Apr 26 11:40:57 192.168.122.209 [70608.417923] [tdb] Start Tempesta DB Apr 26 11:40:57 192.168.122.209 [70608.561406] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:40:59 192.168.122.209 [70610.131257] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70610.131257] Maybe that's fine, but it's worth checking the [70610.131257] config - if there is no relations between the [70610.131257] names, then host name confusion attack is possible. Apr 26 11:40:59 192.168.122.209 [70610.197785] [tempesta fw] Configuration processing is completed. Apr 26 11:40:59 192.168.122.209 [70610.258069] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:41:00 192.168.122.209 [70610.702252] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:41:00 192.168.122.209 [70610.729745] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:41:00 192.168.122.209 [70610.757478] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:41:00 192.168.122.209 [70610.809795] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:41:00 192.168.122.209 [70610.811647] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:41:00 192.168.122.209 [70610.849737] [tempesta fw] Tempesta FW is ready Apr 26 11:41:02 192.168.122.209 [70613.523104] [tdb] Close table 'client0.tdb' Apr 26 11:41:03 192.168.122.209 [70613.712183] [tdb] Close table 'sessions0.tdb' Apr 26 11:41:06 192.168.122.209 [70616.986152] [tdb] Close table 'cache0.tdb' Apr 26 11:41:06 192.168.122.209 [70617.233126] [tdb] Close table 'filter0.tdb' Apr 26 11:41:06 192.168.122.209 [70617.233568] [tempesta fw] modules are stopped Apr 26 11:41:06 192.168.122.209 [70617.420649] [tempesta fw] exiting... Apr 26 11:41:06 192.168.122.209 [70617.537326] [tdb] Shutdown Tempesta DB Apr 26 11:41:07 192.168.122.209 [70617.896795] End test: cache.test_cache.TestCacheMultipleMethodsHttp.test_several_entries_POST_GET Apr 26 11:41:07 192.168.122.209 [70617.928859] Start test: cache.test_cache.TestCacheMultipleMethodsHttp.test_several_entries_POST_HEAD Apr 26 11:41:08 192.168.122.209 [70619.312947] [tdb] Start Tempesta DB Apr 26 11:41:08 192.168.122.209 [70619.456059] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:41:10 192.168.122.209 [70620.979191] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70620.979191] Maybe that's fine, but it's worth checking the [70620.979191] config - if there is no relations between the [70620.979191] names, then host name confusion attack is possible. Apr 26 11:41:10 192.168.122.209 [70621.049954] [tempesta fw] Configuration processing is completed. Apr 26 11:41:10 192.168.122.209 [70621.115212] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:41:10 192.168.122.209 [70621.538372] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:41:10 192.168.122.209 [70621.575391] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:41:10 192.168.122.209 [70621.602974] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:41:10 192.168.122.209 [70621.669917] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:41:10 192.168.122.209 [70621.671742] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:41:11 192.168.122.209 [70621.709918] [tempesta fw] Tempesta FW is ready Apr 26 11:41:13 192.168.122.209 [70624.416515] [tdb] Close table 'client0.tdb' Apr 26 11:41:13 192.168.122.209 [70624.606788] [tdb] Close table 'sessions0.tdb' Apr 26 11:41:17 192.168.122.209 [70627.763469] [tdb] Close table 'cache0.tdb' Apr 26 11:41:17 192.168.122.209 [70628.024567] [tdb] Close table 'filter0.tdb' Apr 26 11:41:17 192.168.122.209 [70628.025000] [tempesta fw] modules are stopped Apr 26 11:41:17 192.168.122.209 [70628.201109] [tempesta fw] exiting... Apr 26 11:41:17 192.168.122.209 [70628.345199] [tdb] Shutdown Tempesta DB Apr 26 11:41:18 192.168.122.209 [70628.706055] End test: cache.test_cache.TestCacheMultipleMethodsHttp.test_several_entries_POST_HEAD Apr 26 11:41:18 192.168.122.209 [70628.735973] Start test: cache.test_cache.TestCacheMultipleMethodsHttp.test_several_entries_POST_POST Apr 26 11:41:19 192.168.122.209 [70630.163479] [tdb] Start Tempesta DB Apr 26 11:41:19 192.168.122.209 [70630.303314] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:41:21 192.168.122.209 [70631.871294] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70631.871294] Maybe that's fine, but it's worth checking the [70631.871294] config - if there is no relations between the [70631.871294] names, then host name confusion attack is possible. Apr 26 11:41:21 192.168.122.209 [70631.938085] [tempesta fw] Configuration processing is completed. Apr 26 11:41:21 192.168.122.209 [70631.990550] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:41:21 192.168.122.209 [70632.413401] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:41:21 192.168.122.209 [70632.439850] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:41:21 192.168.122.209 [70632.475796] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:41:21 192.168.122.209 [70632.526079] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:41:21 192.168.122.209 [70632.527792] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:41:21 192.168.122.209 [70632.585993] [tempesta fw] Tempesta FW is ready Apr 26 11:41:22 192.168.122.209 [70633.244520] [tdb] Close table 'client0.tdb' Apr 26 11:41:22 192.168.122.209 [70633.436835] [tdb] Close table 'sessions0.tdb' Apr 26 11:41:25 192.168.122.209 [70636.570590] [tdb] Close table 'cache0.tdb' Apr 26 11:41:26 192.168.122.209 [70636.804947] [tdb] Close table 'filter0.tdb' Apr 26 11:41:26 192.168.122.209 [70636.805351] [tempesta fw] modules are stopped Apr 26 11:41:26 192.168.122.209 [70636.987465] [tempesta fw] exiting... Apr 26 11:41:26 192.168.122.209 [70637.115919] [tdb] Shutdown Tempesta DB Apr 26 11:41:26 192.168.122.209 [70637.531890] End test: cache.test_cache.TestCacheMultipleMethodsHttp.test_several_entries_POST_POST Apr 26 11:41:26 192.168.122.209 [70637.566884] Start test: cache.test_cache.TestCacheMultipleMethodsHttp.test_update_cache_via_DELETE_request Apr 26 11:41:28 192.168.122.209 [70638.941735] [tdb] Start Tempesta DB Apr 26 11:41:28 192.168.122.209 [70639.092425] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:41:29 192.168.122.209 [70640.647433] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70640.647433] Maybe that's fine, but it's worth checking the [70640.647433] config - if there is no relations between the [70640.647433] names, then host name confusion attack is possible. Apr 26 11:41:30 192.168.122.209 [70640.718163] [tempesta fw] Configuration processing is completed. Apr 26 11:41:30 192.168.122.209 [70640.771658] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:41:30 192.168.122.209 [70641.203232] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:41:30 192.168.122.209 [70641.230334] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:41:30 192.168.122.209 [70641.256795] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:41:30 192.168.122.209 [70641.298202] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:41:30 192.168.122.209 [70641.299909] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:41:30 192.168.122.209 [70641.334136] [tempesta fw] Tempesta FW is ready Apr 26 11:41:31 192.168.122.209 [70641.945668] [tdb] Close table 'client0.tdb' Apr 26 11:41:31 192.168.122.209 [70642.159331] [tdb] Close table 'sessions0.tdb' Apr 26 11:41:34 192.168.122.209 [70645.405406] [tdb] Close table 'cache0.tdb' Apr 26 11:41:34 192.168.122.209 [70645.656434] [tdb] Close table 'filter0.tdb' Apr 26 11:41:34 192.168.122.209 [70645.657126] [tempesta fw] modules are stopped Apr 26 11:41:35 192.168.122.209 [70645.844267] [tempesta fw] exiting... Apr 26 11:41:35 192.168.122.209 [70645.997138] [tdb] Shutdown Tempesta DB Apr 26 11:41:35 192.168.122.209 [70646.367699] End test: cache.test_cache.TestCacheMultipleMethodsHttp.test_update_cache_via_DELETE_request Apr 26 11:41:35 192.168.122.209 [70646.398384] Start test: cache.test_cache.TestCacheMultipleMethodsHttp.test_update_cache_via_PUT_request Apr 26 11:41:37 192.168.122.209 [70647.784533] [tdb] Start Tempesta DB Apr 26 11:41:37 192.168.122.209 [70647.940330] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:41:38 192.168.122.209 [70649.415657] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70649.415657] Maybe that's fine, but it's worth checking the [70649.415657] config - if there is no relations between the [70649.415657] names, then host name confusion attack is possible. Apr 26 11:41:38 192.168.122.209 [70649.494356] [tempesta fw] Configuration processing is completed. Apr 26 11:41:38 192.168.122.209 [70649.547335] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:41:39 192.168.122.209 [70649.994998] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:41:39 192.168.122.209 [70650.024044] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:41:39 192.168.122.209 [70650.060319] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:41:39 192.168.122.209 [70650.122315] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:41:39 192.168.122.209 [70650.124016] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:41:39 192.168.122.209 [70650.178216] [tempesta fw] Tempesta FW is ready Apr 26 11:41:40 192.168.122.209 [70650.843821] [tdb] Close table 'client0.tdb' Apr 26 11:41:40 192.168.122.209 [70651.011704] [tdb] Close table 'sessions0.tdb' Apr 26 11:41:43 192.168.122.209 [70654.158649] [tdb] Close table 'cache0.tdb' Apr 26 11:41:43 192.168.122.209 [70654.413764] [tdb] Close table 'filter0.tdb' Apr 26 11:41:43 192.168.122.209 [70654.414210] [tempesta fw] modules are stopped Apr 26 11:41:43 192.168.122.209 [70654.635158] [tempesta fw] exiting... Apr 26 11:41:44 192.168.122.209 [70654.772348] [tdb] Shutdown Tempesta DB Apr 26 11:41:44 192.168.122.209 [70655.128327] End test: cache.test_cache.TestCacheMultipleMethodsHttp.test_update_cache_via_PUT_request Apr 26 11:41:44 192.168.122.209 [70655.155017] Start test: cache.test_cache.TestCacheOverriddenHostH2.test Apr 26 11:41:45 192.168.122.209 [70656.496799] [tdb] Start Tempesta DB Apr 26 11:41:45 192.168.122.209 [70656.645300] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:41:47 192.168.122.209 [70658.219653] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70658.219653] Maybe that's fine, but it's worth checking the [70658.219653] config - if there is no relations between the [70658.219653] names, then host name confusion attack is possible. Apr 26 11:41:47 192.168.122.209 [70658.318439] [tempesta fw] Configuration processing is completed. Apr 26 11:41:47 192.168.122.209 [70658.378066] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:41:48 192.168.122.209 [70658.802391] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:41:48 192.168.122.209 [70658.830290] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:41:48 192.168.122.209 [70658.858384] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:41:48 192.168.122.209 [70658.898449] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:41:48 192.168.122.209 [70658.900146] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:41:48 192.168.122.209 [70658.942355] [tempesta fw] Tempesta FW is ready Apr 26 11:41:48 192.168.122.209 [70659.625059] [tdb] Close table 'client0.tdb' Apr 26 11:41:49 192.168.122.209 [70659.809367] [tdb] Close table 'sessions0.tdb' Apr 26 11:41:52 192.168.122.209 [70662.932429] [tdb] Close table 'cache0.tdb' Apr 26 11:41:52 192.168.122.209 [70663.182382] [tdb] Close table 'filter0.tdb' Apr 26 11:41:52 192.168.122.209 [70663.182818] [tempesta fw] modules are stopped Apr 26 11:41:52 192.168.122.209 [70663.368203] [tempesta fw] exiting... Apr 26 11:41:52 192.168.122.209 [70663.492616] [tdb] Shutdown Tempesta DB Apr 26 11:41:53 192.168.122.209 [70663.897520] End test: cache.test_cache.TestCacheOverriddenHostH2.test Apr 26 11:41:53 192.168.122.209 [70663.930714] Start test: cache.test_cache.TestCacheOverriddenHostHttp.test Apr 26 11:41:54 192.168.122.209 [70665.287728] [tdb] Start Tempesta DB Apr 26 11:41:54 192.168.122.209 [70665.429578] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:41:56 192.168.122.209 [70667.039801] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70667.039801] Maybe that's fine, but it's worth checking the [70667.039801] config - if there is no relations between the [70667.039801] names, then host name confusion attack is possible. Apr 26 11:41:56 192.168.122.209 [70667.142559] [tempesta fw] Configuration processing is completed. Apr 26 11:41:56 192.168.122.209 [70667.204333] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:41:56 192.168.122.209 [70667.630356] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:41:56 192.168.122.209 [70667.660506] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:41:56 192.168.122.209 [70667.685571] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:41:57 192.168.122.209 [70667.726534] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:41:57 192.168.122.209 [70667.728236] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:41:57 192.168.122.209 [70667.766461] [tempesta fw] Tempesta FW is ready Apr 26 11:41:57 192.168.122.209 [70668.424614] [tdb] Close table 'client0.tdb' Apr 26 11:41:57 192.168.122.209 [70668.612839] [tdb] Close table 'sessions0.tdb' Apr 26 11:42:01 192.168.122.209 [70671.767687] [tdb] Close table 'cache0.tdb' Apr 26 11:42:01 192.168.122.209 [70672.018569] [tdb] Close table 'filter0.tdb' Apr 26 11:42:01 192.168.122.209 [70672.019003] [tempesta fw] modules are stopped Apr 26 11:42:01 192.168.122.209 [70672.191165] [tempesta fw] exiting... Apr 26 11:42:01 192.168.122.209 [70672.309939] [tdb] Shutdown Tempesta DB Apr 26 11:42:02 192.168.122.209 [70672.708706] End test: cache.test_cache.TestCacheOverriddenHostHttp.test Apr 26 11:42:02 192.168.122.209 [70672.743922] Start test: cache.test_cache.TestCacheResponseWithCacheDifferentClients.test_GET_deproxy_deproxy_h2 Apr 26 11:42:03 192.168.122.209 [70674.133476] [tdb] Start Tempesta DB Apr 26 11:42:03 192.168.122.209 [70674.264447] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:42:05 192.168.122.209 [70675.816339] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70675.816339] Maybe that's fine, but it's worth checking the [70675.816339] config - if there is no relations between the [70675.816339] names, then host name confusion attack is possible. Apr 26 11:42:05 192.168.122.209 [70675.858948] [tempesta fw] Configuration processing is completed. Apr 26 11:42:05 192.168.122.209 [70675.915407] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:42:05 192.168.122.209 [70676.328914] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:42:05 192.168.122.209 [70676.355054] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:42:05 192.168.122.209 [70676.380896] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:42:05 192.168.122.209 [70676.422631] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:42:05 192.168.122.209 [70676.424331] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:42:05 192.168.122.209 [70676.462584] [tempesta fw] Tempesta FW is ready Apr 26 11:42:06 192.168.122.209 [70677.119467] [tdb] Close table 'client0.tdb' Apr 26 11:42:06 192.168.122.209 [70677.303320] [tdb] Close table 'sessions0.tdb' Apr 26 11:42:09 192.168.122.209 [70680.515250] [tdb] Close table 'cache0.tdb' Apr 26 11:42:10 192.168.122.209 [70680.791125] [tdb] Close table 'filter0.tdb' Apr 26 11:42:10 192.168.122.209 [70680.791550] [tempesta fw] modules are stopped Apr 26 11:42:10 192.168.122.209 [70680.966792] [tempesta fw] exiting... Apr 26 11:42:10 192.168.122.209 [70681.104134] [tdb] Shutdown Tempesta DB Apr 26 11:42:10 192.168.122.209 [70681.491738] End test: cache.test_cache.TestCacheResponseWithCacheDifferentClients.test_GET_deproxy_deproxy_h2 Apr 26 11:42:10 192.168.122.209 [70681.531782] Start test: cache.test_cache.TestCacheResponseWithCacheDifferentClients.test_GET_deproxy_h2_deproxy Apr 26 11:42:12 192.168.122.209 [70682.963693] [tdb] Start Tempesta DB Apr 26 11:42:12 192.168.122.209 [70683.096150] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:42:14 192.168.122.209 [70684.724493] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70684.724493] Maybe that's fine, but it's worth checking the [70684.724493] config - if there is no relations between the [70684.724493] names, then host name confusion attack is possible. Apr 26 11:42:14 192.168.122.209 [70684.790749] [tempesta fw] Configuration processing is completed. Apr 26 11:42:14 192.168.122.209 [70684.848361] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:42:14 192.168.122.209 [70685.278641] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:42:14 192.168.122.209 [70685.307007] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:42:14 192.168.122.209 [70685.334229] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:42:14 192.168.122.209 [70685.374739] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:42:14 192.168.122.209 [70685.376543] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:42:14 192.168.122.209 [70685.434675] [tempesta fw] Tempesta FW is ready Apr 26 11:42:15 192.168.122.209 [70686.081454] [tdb] Close table 'client0.tdb' Apr 26 11:42:15 192.168.122.209 [70686.268916] [tdb] Close table 'sessions0.tdb' Apr 26 11:42:18 192.168.122.209 [70689.407252] [tdb] Close table 'cache0.tdb' Apr 26 11:42:18 192.168.122.209 [70689.645746] [tdb] Close table 'filter0.tdb' Apr 26 11:42:18 192.168.122.209 [70689.646176] [tempesta fw] modules are stopped Apr 26 11:42:19 192.168.122.209 [70689.889001] [tempesta fw] exiting... Apr 26 11:42:19 192.168.122.209 [70690.002881] [tdb] Shutdown Tempesta DB Apr 26 11:42:19 192.168.122.209 [70690.463928] End test: cache.test_cache.TestCacheResponseWithCacheDifferentClients.test_GET_deproxy_h2_deproxy Apr 26 11:42:19 192.168.122.209 [70690.496051] Start test: cache.test_cache.TestCacheResponseWithCacheDifferentClients.test_HEAD_deproxy_deproxy_h2 Apr 26 11:42:21 192.168.122.209 [70691.976483] [tdb] Start Tempesta DB Apr 26 11:42:21 192.168.122.209 [70692.104490] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:42:22 192.168.122.209 [70693.652629] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70693.652629] Maybe that's fine, but it's worth checking the [70693.652629] config - if there is no relations between the [70693.652629] names, then host name confusion attack is possible. Apr 26 11:42:23 192.168.122.209 [70693.706868] [tempesta fw] Configuration processing is completed. Apr 26 11:42:23 192.168.122.209 [70693.768863] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:42:23 192.168.122.209 [70694.256496] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:42:23 192.168.122.209 [70694.289931] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:42:23 192.168.122.209 [70694.324511] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:42:23 192.168.122.209 [70694.362886] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:42:23 192.168.122.209 [70694.364594] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:42:23 192.168.122.209 [70694.410786] [tempesta fw] Tempesta FW is ready Apr 26 11:42:24 192.168.122.209 [70695.054353] [tdb] Close table 'client0.tdb' Apr 26 11:42:24 192.168.122.209 [70695.250008] [tdb] Close table 'sessions0.tdb' Apr 26 11:42:27 192.168.122.209 [70698.508708] [tdb] Close table 'cache0.tdb' Apr 26 11:42:28 192.168.122.209 [70698.804158] [tdb] Close table 'filter0.tdb' Apr 26 11:42:28 192.168.122.209 [70698.804575] [tempesta fw] modules are stopped Apr 26 11:42:28 192.168.122.209 [70698.979288] [tempesta fw] exiting... Apr 26 11:42:28 192.168.122.209 [70699.114048] [tdb] Shutdown Tempesta DB Apr 26 11:42:28 192.168.122.209 [70699.493870] End test: cache.test_cache.TestCacheResponseWithCacheDifferentClients.test_HEAD_deproxy_deproxy_h2 Apr 26 11:42:28 192.168.122.209 [70699.520565] Start test: cache.test_cache.TestCacheResponseWithCacheDifferentClients.test_HEAD_deproxy_h2_deproxy Apr 26 11:42:30 192.168.122.209 [70700.965364] [tdb] Start Tempesta DB Apr 26 11:42:30 192.168.122.209 [70701.114612] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:42:32 192.168.122.209 [70702.696611] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70702.696611] Maybe that's fine, but it's worth checking the [70702.696611] config - if there is no relations between the [70702.696611] names, then host name confusion attack is possible. Apr 26 11:42:32 192.168.122.209 [70702.758959] [tempesta fw] Configuration processing is completed. Apr 26 11:42:32 192.168.122.209 [70702.817469] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:42:32 192.168.122.209 [70703.242627] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:42:32 192.168.122.209 [70703.270080] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:42:32 192.168.122.209 [70703.297483] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:42:32 192.168.122.209 [70703.334990] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:42:32 192.168.122.209 [70703.336715] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:42:32 192.168.122.209 [70703.374900] [tempesta fw] Tempesta FW is ready Apr 26 11:42:33 192.168.122.209 [70704.048228] [tdb] Close table 'client0.tdb' Apr 26 11:42:33 192.168.122.209 [70704.231837] [tdb] Close table 'sessions0.tdb' Apr 26 11:42:36 192.168.122.209 [70707.416653] [tdb] Close table 'cache0.tdb' Apr 26 11:42:36 192.168.122.209 [70707.662604] [tdb] Close table 'filter0.tdb' Apr 26 11:42:36 192.168.122.209 [70707.663432] [tempesta fw] modules are stopped Apr 26 11:42:37 192.168.122.209 [70707.886045] [tempesta fw] exiting... Apr 26 11:42:37 192.168.122.209 [70708.057022] [tdb] Shutdown Tempesta DB Apr 26 11:42:37 192.168.122.209 [70708.421321] End test: cache.test_cache.TestCacheResponseWithCacheDifferentClients.test_HEAD_deproxy_h2_deproxy Apr 26 11:42:37 192.168.122.209 [70708.448243] Start test: cache.test_cache.TestCacheResponseWithTrailersH2.test_GET_GET Apr 26 11:42:39 192.168.122.209 [70709.909099] [tdb] Start Tempesta DB Apr 26 11:42:39 192.168.122.209 [70710.039569] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:42:40 192.168.122.209 [70711.648863] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70711.648863] Maybe that's fine, but it's worth checking the [70711.648863] config - if there is no relations between the [70711.648863] names, then host name confusion attack is possible. Apr 26 11:42:40 192.168.122.209 [70711.691471] [tempesta fw] Configuration processing is completed. Apr 26 11:42:41 192.168.122.209 [70711.752604] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:42:41 192.168.122.209 [70712.192782] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:42:41 192.168.122.209 [70712.219046] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:42:41 192.168.122.209 [70712.245259] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:42:41 192.168.122.209 [70712.291098] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:42:41 192.168.122.209 [70712.292852] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:42:41 192.168.122.209 [70712.331021] [tempesta fw] Tempesta FW is ready Apr 26 11:42:42 192.168.122.209 [70712.961733] [tdb] Close table 'client0.tdb' Apr 26 11:42:42 192.168.122.209 [70713.143608] [tdb] Close table 'sessions0.tdb' Apr 26 11:42:45 192.168.122.209 [70716.322758] [tdb] Close table 'cache0.tdb' Apr 26 11:42:45 192.168.122.209 [70716.575025] [tdb] Close table 'filter0.tdb' Apr 26 11:42:45 192.168.122.209 [70716.575451] [tempesta fw] modules are stopped Apr 26 11:42:46 192.168.122.209 [70716.760368] [tempesta fw] exiting... Apr 26 11:42:46 192.168.122.209 [70716.878729] [tdb] Shutdown Tempesta DB Apr 26 11:42:46 192.168.122.209 [70717.326552] End test: cache.test_cache.TestCacheResponseWithTrailersH2.test_GET_GET Apr 26 11:42:46 192.168.122.209 [70717.354227] Start test: cache.test_cache.TestCacheResponseWithTrailersH2.test_GET_HEAD Apr 26 11:42:48 192.168.122.209 [70718.741942] [tdb] Start Tempesta DB Apr 26 11:42:48 192.168.122.209 [70718.875846] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:42:49 192.168.122.209 [70720.444836] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70720.444836] Maybe that's fine, but it's worth checking the [70720.444836] config - if there is no relations between the [70720.444836] names, then host name confusion attack is possible. Apr 26 11:42:49 192.168.122.209 [70720.503179] [tempesta fw] Configuration processing is completed. Apr 26 11:42:49 192.168.122.209 [70720.560980] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:42:50 192.168.122.209 [70720.974850] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:42:50 192.168.122.209 [70721.000546] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:42:50 192.168.122.209 [70721.025928] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:42:50 192.168.122.209 [70721.075216] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:42:50 192.168.122.209 [70721.076920] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:42:50 192.168.122.209 [70721.115176] [tempesta fw] Tempesta FW is ready Apr 26 11:42:51 192.168.122.209 [70721.822566] [tdb] Close table 'client0.tdb' Apr 26 11:42:51 192.168.122.209 [70722.007796] [tdb] Close table 'sessions0.tdb' Apr 26 11:42:54 192.168.122.209 [70725.203397] [tdb] Close table 'cache0.tdb' Apr 26 11:42:54 192.168.122.209 [70725.422397] [tdb] Close table 'filter0.tdb' Apr 26 11:42:54 192.168.122.209 [70725.422827] [tempesta fw] modules are stopped Apr 26 11:42:54 192.168.122.209 [70725.639746] [tempesta fw] exiting... Apr 26 11:42:55 192.168.122.209 [70725.778279] [tdb] Shutdown Tempesta DB Apr 26 11:42:55 192.168.122.209 [70726.201176] End test: cache.test_cache.TestCacheResponseWithTrailersH2.test_GET_HEAD Apr 26 11:42:55 192.168.122.209 [70726.236795] Start test: cache.test_cache.TestCacheResponseWithTrailersH2.test_HEAD_GET Apr 26 11:42:56 192.168.122.209 [70727.617861] [tdb] Start Tempesta DB Apr 26 11:42:57 192.168.122.209 [70727.765310] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:42:58 192.168.122.209 [70729.260999] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70729.260999] Maybe that's fine, but it's worth checking the [70729.260999] config - if there is no relations between the [70729.260999] names, then host name confusion attack is possible. Apr 26 11:42:58 192.168.122.209 [70729.331310] [tempesta fw] Configuration processing is completed. Apr 26 11:42:58 192.168.122.209 [70729.392412] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:42:59 192.168.122.209 [70729.827318] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:42:59 192.168.122.209 [70729.854814] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:42:59 192.168.122.209 [70729.882390] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:42:59 192.168.122.209 [70729.923318] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:42:59 192.168.122.209 [70729.925014] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:42:59 192.168.122.209 [70729.963244] [tempesta fw] Tempesta FW is ready Apr 26 11:42:59 192.168.122.209 [70730.645279] [tdb] Close table 'client0.tdb' Apr 26 11:43:00 192.168.122.209 [70730.826656] [tdb] Close table 'sessions0.tdb' Apr 26 11:43:03 192.168.122.209 [70734.023486] [tdb] Close table 'cache0.tdb' Apr 26 11:43:03 192.168.122.209 [70734.259268] [tdb] Close table 'filter0.tdb' Apr 26 11:43:03 192.168.122.209 [70734.259697] [tempesta fw] modules are stopped Apr 26 11:43:03 192.168.122.209 [70734.457788] [tempesta fw] exiting... Apr 26 11:43:03 192.168.122.209 [70734.567412] [tdb] Shutdown Tempesta DB Apr 26 11:43:04 192.168.122.209 [70734.961112] End test: cache.test_cache.TestCacheResponseWithTrailersH2.test_HEAD_GET Apr 26 11:43:04 192.168.122.209 [70734.996232] Start test: cache.test_cache.TestCacheResponseWithTrailersH2.test_HEAD_HEAD Apr 26 11:43:05 192.168.122.209 [70736.435704] [tdb] Start Tempesta DB Apr 26 11:43:05 192.168.122.209 [70736.565124] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:43:07 192.168.122.209 [70738.173088] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70738.173088] Maybe that's fine, but it's worth checking the [70738.173088] config - if there is no relations between the [70738.173088] names, then host name confusion attack is possible. Apr 26 11:43:07 192.168.122.209 [70738.235421] [tempesta fw] Configuration processing is completed. Apr 26 11:43:07 192.168.122.209 [70738.292894] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:43:08 192.168.122.209 [70738.712242] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:43:08 192.168.122.209 [70738.738618] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:43:08 192.168.122.209 [70738.770211] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:43:08 192.168.122.209 [70738.811461] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:43:08 192.168.122.209 [70738.813180] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:43:08 192.168.122.209 [70738.851360] [tempesta fw] Tempesta FW is ready Apr 26 11:43:08 192.168.122.209 [70739.520038] [tdb] Close table 'client0.tdb' Apr 26 11:43:09 192.168.122.209 [70739.705101] [tdb] Close table 'sessions0.tdb' Apr 26 11:43:12 192.168.122.209 [70742.864098] [tdb] Close table 'cache0.tdb' Apr 26 11:43:12 192.168.122.209 [70743.113699] [tdb] Close table 'filter0.tdb' Apr 26 11:43:12 192.168.122.209 [70743.114107] [tempesta fw] modules are stopped Apr 26 11:43:12 192.168.122.209 [70743.340775] [tempesta fw] exiting... Apr 26 11:43:12 192.168.122.209 [70743.474747] [tdb] Shutdown Tempesta DB Apr 26 11:43:13 192.168.122.209 [70743.891587] End test: cache.test_cache.TestCacheResponseWithTrailersH2.test_HEAD_HEAD Apr 26 11:43:13 192.168.122.209 [70743.928833] Start test: cache.test_cache.TestCacheResponseWithTrailersH2.test_empty_body_head_to_get Apr 26 11:43:14 192.168.122.209 [70745.355395] [tdb] Start Tempesta DB Apr 26 11:43:14 192.168.122.209 [70745.506451] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:43:16 192.168.122.209 [70747.069249] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70747.069249] Maybe that's fine, but it's worth checking the [70747.069249] config - if there is no relations between the [70747.069249] names, then host name confusion attack is possible. Apr 26 11:43:16 192.168.122.209 [70747.123544] [tempesta fw] Configuration processing is completed. Apr 26 11:43:16 192.168.122.209 [70747.185064] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:43:16 192.168.122.209 [70747.597187] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:43:16 192.168.122.209 [70747.623502] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:43:16 192.168.122.209 [70747.649170] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:43:17 192.168.122.209 [70747.699575] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:43:17 192.168.122.209 [70747.701298] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:43:17 192.168.122.209 [70747.751472] [tempesta fw] Tempesta FW is ready Apr 26 11:43:17 192.168.122.209 [70748.400909] [tdb] Close table 'client0.tdb' Apr 26 11:43:17 192.168.122.209 [70748.593609] [tdb] Close table 'sessions0.tdb' Apr 26 11:43:21 192.168.122.209 [70751.804473] [tdb] Close table 'cache0.tdb' Apr 26 11:43:21 192.168.122.209 [70752.049201] [tdb] Close table 'filter0.tdb' Apr 26 11:43:21 192.168.122.209 [70752.049635] [tempesta fw] modules are stopped Apr 26 11:43:21 192.168.122.209 [70752.295971] [tempesta fw] exiting... Apr 26 11:43:21 192.168.122.209 [70752.423279] [tdb] Shutdown Tempesta DB Apr 26 11:43:22 192.168.122.209 [70752.808194] End test: cache.test_cache.TestCacheResponseWithTrailersH2.test_empty_body_head_to_get Apr 26 11:43:22 192.168.122.209 [70752.890921] Start test: cache.test_cache.TestCacheResponseWithTrailersH2.test_hbh_headers_hbp_GET Apr 26 11:43:23 192.168.122.209 [70754.282684] [tdb] Start Tempesta DB Apr 26 11:43:23 192.168.122.209 [70754.416770] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:43:25 192.168.122.209 [70755.949440] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70755.949440] Maybe that's fine, but it's worth checking the [70755.949440] config - if there is no relations between the [70755.949440] names, then host name confusion attack is possible. Apr 26 11:43:25 192.168.122.209 [70756.000263] [tempesta fw] Configuration processing is completed. Apr 26 11:43:25 192.168.122.209 [70756.058239] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:43:25 192.168.122.209 [70756.506467] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:43:25 192.168.122.209 [70756.534424] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:43:25 192.168.122.209 [70756.566218] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:43:25 192.168.122.209 [70756.607667] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:43:25 192.168.122.209 [70756.609381] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:43:25 192.168.122.209 [70756.647633] [tempesta fw] Tempesta FW is ready Apr 26 11:43:26 192.168.122.209 [70756.789476] [tempesta fw] Warning: Parser error: state=Resp_HdrConnectionV input(-8)=0x6b('ection: keep-alive [70756.789476] Keep-Alive: timeout=5, max=1') data_len=285 off=239 Apr 26 11:43:26 192.168.122.209 [70756.791051] [tempesta fw] Warning: response dropped: processing error: 192.168.122.196 Apr 26 11:43:26 192.168.122.209 [70757.274011] [tdb] Close table 'client0.tdb' Apr 26 11:43:26 192.168.122.209 [70757.449400] [tdb] Close table 'sessions0.tdb' Apr 26 11:43:29 192.168.122.209 [70760.637606] [tdb] Close table 'cache0.tdb' Apr 26 11:43:30 192.168.122.209 [70760.893726] [tdb] Close table 'filter0.tdb' Apr 26 11:43:30 192.168.122.209 [70760.894163] [tempesta fw] modules are stopped Apr 26 11:43:30 192.168.122.209 [70761.085520] [tempesta fw] exiting... Apr 26 11:43:30 192.168.122.209 [70761.203874] [tdb] Shutdown Tempesta DB Apr 26 11:43:30 192.168.122.209 [70761.573752] End test: cache.test_cache.TestCacheResponseWithTrailersH2.test_hbh_headers_hbp_GET Apr 26 11:43:30 192.168.122.209 [70761.609647] Start test: cache.test_cache.TestCacheResponseWithTrailersH2.test_hbh_headers_hbp_HEAD Apr 26 11:43:32 192.168.122.209 [70762.972463] [tdb] Start Tempesta DB Apr 26 11:43:32 192.168.122.209 [70763.106968] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:43:34 192.168.122.209 [70764.733476] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70764.733476] Maybe that's fine, but it's worth checking the [70764.733476] config - if there is no relations between the [70764.733476] names, then host name confusion attack is possible. Apr 26 11:43:34 192.168.122.209 [70764.791769] [tempesta fw] Configuration processing is completed. Apr 26 11:43:34 192.168.122.209 [70764.851033] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:43:34 192.168.122.209 [70765.268732] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:43:34 192.168.122.209 [70765.294721] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:43:34 192.168.122.209 [70765.320088] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:43:34 192.168.122.209 [70765.375779] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:43:34 192.168.122.209 [70765.377560] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:43:34 192.168.122.209 [70765.415647] [tempesta fw] Tempesta FW is ready Apr 26 11:43:34 192.168.122.209 [70765.610954] [tempesta fw] Warning: Parser error: state=Resp_HdrConnectionV input(-8)=0x6b('ection: keep-alive [70765.610954] Keep-Alive: timeout=5, max=1') data_len=285 off=239 Apr 26 11:43:34 192.168.122.209 [70765.615285] [tempesta fw] Warning: response dropped: processing error: 192.168.122.196 Apr 26 11:43:35 192.168.122.209 [70766.052240] [tdb] Close table 'client0.tdb' Apr 26 11:43:35 192.168.122.209 [70766.262386] [tdb] Close table 'sessions0.tdb' Apr 26 11:43:38 192.168.122.209 [70769.462947] [tdb] Close table 'cache0.tdb' Apr 26 11:43:39 192.168.122.209 [70769.706236] [tdb] Close table 'filter0.tdb' Apr 26 11:43:39 192.168.122.209 [70769.706659] [tempesta fw] modules are stopped Apr 26 11:43:39 192.168.122.209 [70769.895570] [tempesta fw] exiting... Apr 26 11:43:39 192.168.122.209 [70770.047802] [tdb] Shutdown Tempesta DB Apr 26 11:43:39 192.168.122.209 [70770.456510] End test: cache.test_cache.TestCacheResponseWithTrailersH2.test_hbh_headers_hbp_HEAD Apr 26 11:43:39 192.168.122.209 [70770.481833] Start test: cache.test_cache.TestCacheResponseWithTrailersH2.test_hbh_headers_mix_GET Apr 26 11:43:41 192.168.122.209 [70771.877242] [tdb] Start Tempesta DB Apr 26 11:43:41 192.168.122.209 [70772.028055] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:43:42 192.168.122.209 [70773.509550] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70773.509550] Maybe that's fine, but it's worth checking the [70773.509550] config - if there is no relations between the [70773.509550] names, then host name confusion attack is possible. Apr 26 11:43:42 192.168.122.209 [70773.556239] [tempesta fw] Configuration processing is completed. Apr 26 11:43:42 192.168.122.209 [70773.613605] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:43:43 192.168.122.209 [70774.075604] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:43:43 192.168.122.209 [70774.113113] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:43:43 192.168.122.209 [70774.147079] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:43:43 192.168.122.209 [70774.187893] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:43:43 192.168.122.209 [70774.189598] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:43:43 192.168.122.209 [70774.227814] [tempesta fw] Tempesta FW is ready Apr 26 11:43:43 192.168.122.209 [70774.423864] [tempesta fw] Warning: Parser error: state=Resp_HdrConnectionV input(-8)=0x6b('ection: keep-alive [70774.423864] X-Token1: value1 [70774.423864] [70774.423864] ') data_len=269 off=237 Apr 26 11:43:43 192.168.122.209 [70774.428729] [tempesta fw] Warning: response dropped: processing error: 192.168.122.196 Apr 26 11:43:44 192.168.122.209 [70774.859428] [tdb] Close table 'client0.tdb' Apr 26 11:43:44 192.168.122.209 [70775.034678] [tdb] Close table 'sessions0.tdb' Apr 26 11:43:47 192.168.122.209 [70778.158270] [tdb] Close table 'cache0.tdb' Apr 26 11:43:47 192.168.122.209 [70778.451494] [tdb] Close table 'filter0.tdb' Apr 26 11:43:47 192.168.122.209 [70778.451963] [tempesta fw] modules are stopped Apr 26 11:43:47 192.168.122.209 [70778.621547] [tempesta fw] exiting... Apr 26 11:43:48 192.168.122.209 [70778.771153] [tdb] Shutdown Tempesta DB Apr 26 11:43:48 192.168.122.209 [70779.129426] End test: cache.test_cache.TestCacheResponseWithTrailersH2.test_hbh_headers_mix_GET Apr 26 11:43:48 192.168.122.209 [70779.163355] Start test: cache.test_cache.TestCacheResponseWithTrailersH2.test_hbh_headers_mix_HEAD Apr 26 11:43:49 192.168.122.209 [70780.484734] [tdb] Start Tempesta DB Apr 26 11:43:49 192.168.122.209 [70780.623227] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:43:51 192.168.122.209 [70782.213628] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70782.213628] Maybe that's fine, but it's worth checking the [70782.213628] config - if there is no relations between the [70782.213628] names, then host name confusion attack is possible. Apr 26 11:43:51 192.168.122.209 [70782.260326] [tempesta fw] Configuration processing is completed. Apr 26 11:43:51 192.168.122.209 [70782.321062] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:43:52 192.168.122.209 [70782.764698] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:43:52 192.168.122.209 [70782.793102] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:43:52 192.168.122.209 [70782.820468] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:43:52 192.168.122.209 [70782.864005] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:43:52 192.168.122.209 [70782.865700] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:43:52 192.168.122.209 [70782.919994] [tempesta fw] Tempesta FW is ready Apr 26 11:43:52 192.168.122.209 [70783.131324] [tempesta fw] Warning: Parser error: state=Resp_HdrConnectionV input(-8)=0x6b('ection: keep-alive [70783.131324] X-Token1: value1 [70783.131324] [70783.131324] ') data_len=269 off=237 Apr 26 11:43:52 192.168.122.209 [70783.135955] [tempesta fw] Warning: response dropped: processing error: 192.168.122.196 Apr 26 11:43:52 192.168.122.209 [70783.611463] [tdb] Close table 'client0.tdb' Apr 26 11:43:53 192.168.122.209 [70783.802297] [tdb] Close table 'sessions0.tdb' Apr 26 11:43:56 192.168.122.209 [70786.950533] [tdb] Close table 'cache0.tdb' Apr 26 11:43:56 192.168.122.209 [70787.184841] [tdb] Close table 'filter0.tdb' Apr 26 11:43:56 192.168.122.209 [70787.185285] [tempesta fw] modules are stopped Apr 26 11:43:56 192.168.122.209 [70787.409354] [tempesta fw] exiting... Apr 26 11:43:56 192.168.122.209 [70787.517893] [tdb] Shutdown Tempesta DB Apr 26 11:43:57 192.168.122.209 [70787.944622] End test: cache.test_cache.TestCacheResponseWithTrailersH2.test_hbh_headers_mix_HEAD Apr 26 11:43:57 192.168.122.209 [70787.974554] Start test: cache.test_cache.TestCacheResponseWithTrailersH2.test_same_hdr_and_trailer_head_to_get Apr 26 11:43:58 192.168.122.209 [70789.317245] [tdb] Start Tempesta DB Apr 26 11:43:58 192.168.122.209 [70789.469951] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:44:00 192.168.122.209 [70791.085836] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70791.085836] Maybe that's fine, but it's worth checking the [70791.085836] config - if there is no relations between the [70791.085836] names, then host name confusion attack is possible. Apr 26 11:44:00 192.168.122.209 [70791.136318] [tempesta fw] Configuration processing is completed. Apr 26 11:44:00 192.168.122.209 [70791.194438] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:44:00 192.168.122.209 [70791.619269] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:44:00 192.168.122.209 [70791.645929] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:44:00 192.168.122.209 [70791.672795] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:44:01 192.168.122.209 [70791.744148] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:44:01 192.168.122.209 [70791.745935] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:44:01 192.168.122.209 [70791.788077] [tempesta fw] Tempesta FW is ready Apr 26 11:44:01 192.168.122.209 [70792.450259] [tdb] Close table 'client0.tdb' Apr 26 11:44:01 192.168.122.209 [70792.645132] [tdb] Close table 'sessions0.tdb' Apr 26 11:44:05 192.168.122.209 [70795.867516] [tdb] Close table 'cache0.tdb' Apr 26 11:44:05 192.168.122.209 [70796.137660] [tdb] Close table 'filter0.tdb' Apr 26 11:44:05 192.168.122.209 [70796.138104] [tempesta fw] modules are stopped Apr 26 11:44:05 192.168.122.209 [70796.335890] [tempesta fw] exiting... Apr 26 11:44:05 192.168.122.209 [70796.482895] [tdb] Shutdown Tempesta DB Apr 26 11:44:06 192.168.122.209 [70796.884103] End test: cache.test_cache.TestCacheResponseWithTrailersH2.test_same_hdr_and_trailer_head_to_get Apr 26 11:44:06 192.168.122.209 [70796.922408] Start test: cache.test_cache.TestCacheResponseWithTrailersH2.test_same_hdr_and_trailer_head_to_get_multiple_1 Apr 26 11:44:07 192.168.122.209 [70798.260401] [tdb] Start Tempesta DB Apr 26 11:44:07 192.168.122.209 [70798.405288] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:44:09 192.168.122.209 [70799.845905] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70799.845905] Maybe that's fine, but it's worth checking the [70799.845905] config - if there is no relations between the [70799.845905] names, then host name confusion attack is possible. Apr 26 11:44:09 192.168.122.209 [70799.896209] [tempesta fw] Configuration processing is completed. Apr 26 11:44:09 192.168.122.209 [70799.952762] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:44:09 192.168.122.209 [70800.389698] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:44:09 192.168.122.209 [70800.423959] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:44:09 192.168.122.209 [70800.457782] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:44:09 192.168.122.209 [70800.540241] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:44:09 192.168.122.209 [70800.541984] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:44:09 192.168.122.209 [70800.584099] [tempesta fw] Tempesta FW is ready Apr 26 11:44:10 192.168.122.209 [70801.251686] [tdb] Close table 'client0.tdb' Apr 26 11:44:10 192.168.122.209 [70801.428496] [tdb] Close table 'sessions0.tdb' Apr 26 11:44:14 192.168.122.209 [70804.712258] [tdb] Close table 'cache0.tdb' Apr 26 11:44:14 192.168.122.209 [70804.972048] [tdb] Close table 'filter0.tdb' Apr 26 11:44:14 192.168.122.209 [70804.972501] [tempesta fw] modules are stopped Apr 26 11:44:14 192.168.122.209 [70805.165571] [tempesta fw] exiting... Apr 26 11:44:14 192.168.122.209 [70805.298276] [tdb] Shutdown Tempesta DB Apr 26 11:44:15 192.168.122.209 [70805.715868] End test: cache.test_cache.TestCacheResponseWithTrailersH2.test_same_hdr_and_trailer_head_to_get_multiple_1 Apr 26 11:44:15 192.168.122.209 [70805.749447] Start test: cache.test_cache.TestCacheResponseWithTrailersH2.test_same_hdr_and_trailer_head_to_get_multiple_2 Apr 26 11:44:16 192.168.122.209 [70807.117654] [tdb] Start Tempesta DB Apr 26 11:44:16 192.168.122.209 [70807.236229] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:44:18 192.168.122.209 [70808.897969] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70808.897969] Maybe that's fine, but it's worth checking the [70808.897969] config - if there is no relations between the [70808.897969] names, then host name confusion attack is possible. Apr 26 11:44:18 192.168.122.209 [70808.944547] [tempesta fw] Configuration processing is completed. Apr 26 11:44:18 192.168.122.209 [70808.995193] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:44:18 192.168.122.209 [70809.412444] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:44:18 192.168.122.209 [70809.438757] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:44:18 192.168.122.209 [70809.464427] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:44:18 192.168.122.209 [70809.516354] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:44:18 192.168.122.209 [70809.518156] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:44:18 192.168.122.209 [70809.592344] [tempesta fw] Tempesta FW is ready Apr 26 11:44:19 192.168.122.209 [70810.248986] [tdb] Close table 'client0.tdb' Apr 26 11:44:19 192.168.122.209 [70810.436689] [tdb] Close table 'sessions0.tdb' Apr 26 11:44:22 192.168.122.209 [70813.660602] [tdb] Close table 'cache0.tdb' Apr 26 11:44:23 192.168.122.209 [70813.918165] [tdb] Close table 'filter0.tdb' Apr 26 11:44:23 192.168.122.209 [70813.918603] [tempesta fw] modules are stopped Apr 26 11:44:23 192.168.122.209 [70814.105751] [tempesta fw] exiting... Apr 26 11:44:23 192.168.122.209 [70814.236721] [tdb] Shutdown Tempesta DB Apr 26 11:44:23 192.168.122.209 [70814.608929] End test: cache.test_cache.TestCacheResponseWithTrailersH2.test_same_hdr_and_trailer_head_to_get_multiple_2 Apr 26 11:44:23 192.168.122.209 [70814.639450] Start test: cache.test_cache.TestCacheResponseWithTrailersH2.test_same_trailer_head_to_get Apr 26 11:44:25 192.168.122.209 [70815.943702] [tdb] Start Tempesta DB Apr 26 11:44:25 192.168.122.209 [70816.072050] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:44:26 192.168.122.209 [70817.670033] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70817.670033] Maybe that's fine, but it's worth checking the [70817.670033] config - if there is no relations between the [70817.670033] names, then host name confusion attack is possible. Apr 26 11:44:27 192.168.122.209 [70817.720426] [tempesta fw] Configuration processing is completed. Apr 26 11:44:27 192.168.122.209 [70817.773090] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:44:27 192.168.122.209 [70818.237891] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:44:27 192.168.122.209 [70818.270978] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:44:27 192.168.122.209 [70818.297065] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:44:27 192.168.122.209 [70818.336453] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:44:27 192.168.122.209 [70818.338150] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:44:27 192.168.122.209 [70818.376414] [tempesta fw] Tempesta FW is ready Apr 26 11:44:28 192.168.122.209 [70818.968004] [tdb] Close table 'client0.tdb' Apr 26 11:44:28 192.168.122.209 [70819.161346] [tdb] Close table 'sessions0.tdb' Apr 26 11:44:31 192.168.122.209 [70822.372805] [tdb] Close table 'cache0.tdb' Apr 26 11:44:31 192.168.122.209 [70822.631763] [tdb] Close table 'filter0.tdb' Apr 26 11:44:31 192.168.122.209 [70822.632168] [tempesta fw] modules are stopped Apr 26 11:44:32 192.168.122.209 [70822.846741] [tempesta fw] exiting... Apr 26 11:44:32 192.168.122.209 [70822.987237] [tdb] Shutdown Tempesta DB Apr 26 11:44:32 192.168.122.209 [70823.401198] End test: cache.test_cache.TestCacheResponseWithTrailersH2.test_same_trailer_head_to_get Apr 26 11:44:32 192.168.122.209 [70823.430914] Start test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_GET_GET Apr 26 11:44:34 192.168.122.209 [70824.778432] [tdb] Start Tempesta DB Apr 26 11:44:34 192.168.122.209 [70824.917943] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:44:35 192.168.122.209 [70826.530494] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70826.530494] Maybe that's fine, but it's worth checking the [70826.530494] config - if there is no relations between the [70826.530494] names, then host name confusion attack is possible. Apr 26 11:44:35 192.168.122.209 [70826.580936] [tempesta fw] Configuration processing is completed. Apr 26 11:44:35 192.168.122.209 [70826.633756] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:44:36 192.168.122.209 [70827.054829] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:44:36 192.168.122.209 [70827.090619] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:44:36 192.168.122.209 [70827.119136] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:44:36 192.168.122.209 [70827.172593] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:44:36 192.168.122.209 [70827.174387] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:44:36 192.168.122.209 [70827.220490] [tempesta fw] Tempesta FW is ready Apr 26 11:44:37 192.168.122.209 [70827.879128] [tdb] Close table 'client0.tdb' Apr 26 11:44:37 192.168.122.209 [70828.071302] [tdb] Close table 'sessions0.tdb' Apr 26 11:44:40 192.168.122.209 [70831.218903] [tdb] Close table 'cache0.tdb' Apr 26 11:44:40 192.168.122.209 [70831.481891] [tdb] Close table 'filter0.tdb' Apr 26 11:44:40 192.168.122.209 [70831.482345] [tempesta fw] modules are stopped Apr 26 11:44:40 192.168.122.209 [70831.680155] [tempesta fw] exiting... Apr 26 11:44:41 192.168.122.209 [70831.834089] [tdb] Shutdown Tempesta DB Apr 26 11:44:41 192.168.122.209 [70832.264685] End test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_GET_GET Apr 26 11:44:41 192.168.122.209 [70832.289437] Start test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_GET_HEAD Apr 26 11:44:42 192.168.122.209 [70833.686452] [tdb] Start Tempesta DB Apr 26 11:44:43 192.168.122.209 [70833.822883] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:44:44 192.168.122.209 [70835.394465] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70835.394465] Maybe that's fine, but it's worth checking the [70835.394465] config - if there is no relations between the [70835.394465] names, then host name confusion attack is possible. Apr 26 11:44:44 192.168.122.209 [70835.448648] [tempesta fw] Configuration processing is completed. Apr 26 11:44:44 192.168.122.209 [70835.498672] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:44:45 192.168.122.209 [70835.918201] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:44:45 192.168.122.209 [70835.954278] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:44:45 192.168.122.209 [70835.979675] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:44:45 192.168.122.209 [70836.028627] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:44:45 192.168.122.209 [70836.030380] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:44:45 192.168.122.209 [70836.068640] [tempesta fw] Tempesta FW is ready Apr 26 11:44:46 192.168.122.209 [70836.737182] [tdb] Close table 'client0.tdb' Apr 26 11:44:46 192.168.122.209 [70836.905696] [tdb] Close table 'sessions0.tdb' Apr 26 11:44:49 192.168.122.209 [70840.060492] [tdb] Close table 'cache0.tdb' Apr 26 11:44:49 192.168.122.209 [70840.314696] [tdb] Close table 'filter0.tdb' Apr 26 11:44:49 192.168.122.209 [70840.315093] [tempesta fw] modules are stopped Apr 26 11:44:49 192.168.122.209 [70840.494076] [tempesta fw] exiting... Apr 26 11:44:49 192.168.122.209 [70840.637961] [tdb] Shutdown Tempesta DB Apr 26 11:44:50 192.168.122.209 [70841.014215] End test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_GET_HEAD Apr 26 11:44:50 192.168.122.209 [70841.054935] Start test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_HEAD_GET Apr 26 11:44:51 192.168.122.209 [70842.415712] [tdb] Start Tempesta DB Apr 26 11:44:51 192.168.122.209 [70842.552815] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:44:53 192.168.122.209 [70844.174461] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70844.174461] Maybe that's fine, but it's worth checking the [70844.174461] config - if there is no relations between the [70844.174461] names, then host name confusion attack is possible. Apr 26 11:44:53 192.168.122.209 [70844.225089] [tempesta fw] Configuration processing is completed. Apr 26 11:44:53 192.168.122.209 [70844.276468] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:44:53 192.168.122.209 [70844.681487] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:44:54 192.168.122.209 [70844.708414] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:44:54 192.168.122.209 [70844.733493] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:44:54 192.168.122.209 [70844.776799] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:44:54 192.168.122.209 [70844.778522] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:44:54 192.168.122.209 [70844.816741] [tempesta fw] Tempesta FW is ready Apr 26 11:44:54 192.168.122.209 [70845.451383] [tdb] Close table 'client0.tdb' Apr 26 11:44:54 192.168.122.209 [70845.637295] [tdb] Close table 'sessions0.tdb' Apr 26 11:44:58 192.168.122.209 [70848.809212] [tdb] Close table 'cache0.tdb' Apr 26 11:44:58 192.168.122.209 [70849.050911] [tdb] Close table 'filter0.tdb' Apr 26 11:44:58 192.168.122.209 [70849.051329] [tempesta fw] modules are stopped Apr 26 11:44:58 192.168.122.209 [70849.246434] [tempesta fw] exiting... Apr 26 11:44:58 192.168.122.209 [70849.387464] [tdb] Shutdown Tempesta DB Apr 26 11:44:59 192.168.122.209 [70849.755748] End test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_HEAD_GET Apr 26 11:44:59 192.168.122.209 [70849.788177] Start test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_HEAD_HEAD Apr 26 11:45:00 192.168.122.209 [70851.189033] [tdb] Start Tempesta DB Apr 26 11:45:00 192.168.122.209 [70851.318068] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:45:02 192.168.122.209 [70852.846543] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70852.846543] Maybe that's fine, but it's worth checking the [70852.846543] config - if there is no relations between the [70852.846543] names, then host name confusion attack is possible. Apr 26 11:45:02 192.168.122.209 [70852.893153] [tempesta fw] Configuration processing is completed. Apr 26 11:45:02 192.168.122.209 [70852.952986] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:45:02 192.168.122.209 [70853.366027] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:45:02 192.168.122.209 [70853.392564] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:45:02 192.168.122.209 [70853.418554] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:45:02 192.168.122.209 [70853.456917] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:45:02 192.168.122.209 [70853.458643] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:45:02 192.168.122.209 [70853.496867] [tempesta fw] Tempesta FW is ready Apr 26 11:45:03 192.168.122.209 [70854.098551] [tdb] Close table 'client0.tdb' Apr 26 11:45:03 192.168.122.209 [70854.296189] [tdb] Close table 'sessions0.tdb' Apr 26 11:45:06 192.168.122.209 [70857.435854] [tdb] Close table 'cache0.tdb' Apr 26 11:45:06 192.168.122.209 [70857.661275] [tdb] Close table 'filter0.tdb' Apr 26 11:45:06 192.168.122.209 [70857.661675] [tempesta fw] modules are stopped Apr 26 11:45:07 192.168.122.209 [70857.872410] [tempesta fw] exiting... Apr 26 11:45:07 192.168.122.209 [70858.011765] [tdb] Shutdown Tempesta DB Apr 26 11:45:07 192.168.122.209 [70858.417156] End test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_HEAD_HEAD Apr 26 11:45:07 192.168.122.209 [70858.443395] Start test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_empty_body_head_to_get Apr 26 11:45:09 192.168.122.209 [70859.824669] [tdb] Start Tempesta DB Apr 26 11:45:09 192.168.122.209 [70859.952455] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:45:10 192.168.122.209 [70861.538719] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70861.538719] Maybe that's fine, but it's worth checking the [70861.538719] config - if there is no relations between the [70861.538719] names, then host name confusion attack is possible. Apr 26 11:45:10 192.168.122.209 [70861.597091] [tempesta fw] Configuration processing is completed. Apr 26 11:45:10 192.168.122.209 [70861.659157] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:45:11 192.168.122.209 [70862.084430] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:45:11 192.168.122.209 [70862.114839] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:45:11 192.168.122.209 [70862.141691] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:45:11 192.168.122.209 [70862.205029] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:45:11 192.168.122.209 [70862.206785] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:45:11 192.168.122.209 [70862.249006] [tempesta fw] Tempesta FW is ready Apr 26 11:45:12 192.168.122.209 [70862.918447] [tdb] Close table 'client0.tdb' Apr 26 11:45:12 192.168.122.209 [70863.105986] [tdb] Close table 'sessions0.tdb' Apr 26 11:45:15 192.168.122.209 [70866.288000] [tdb] Close table 'cache0.tdb' Apr 26 11:45:15 192.168.122.209 [70866.501499] [tdb] Close table 'filter0.tdb' Apr 26 11:45:15 192.168.122.209 [70866.501926] [tempesta fw] modules are stopped Apr 26 11:45:16 192.168.122.209 [70866.701751] [tempesta fw] exiting... Apr 26 11:45:16 192.168.122.209 [70866.813354] [tdb] Shutdown Tempesta DB Apr 26 11:45:16 192.168.122.209 [70867.203796] End test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_empty_body_head_to_get Apr 26 11:45:16 192.168.122.209 [70867.229649] Start test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_hbh_headers_hbp_GET Apr 26 11:45:17 192.168.122.209 [70868.695848] [tdb] Start Tempesta DB Apr 26 11:45:18 192.168.122.209 [70868.833631] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:45:19 192.168.122.209 [70870.406798] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70870.406798] Maybe that's fine, but it's worth checking the [70870.406798] config - if there is no relations between the [70870.406798] names, then host name confusion attack is possible. Apr 26 11:45:19 192.168.122.209 [70870.469119] [tempesta fw] Configuration processing is completed. Apr 26 11:45:19 192.168.122.209 [70870.525597] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:45:20 192.168.122.209 [70870.947723] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:45:20 192.168.122.209 [70870.987921] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:45:20 192.168.122.209 [70871.013583] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:45:20 192.168.122.209 [70871.053131] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:45:20 192.168.122.209 [70871.054835] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:45:20 192.168.122.209 [70871.109076] [tempesta fw] Tempesta FW is ready Apr 26 11:45:20 192.168.122.209 [70871.244917] [tempesta fw] Warning: Parser error: state=Resp_HdrConnectionV input(-8)=0x6b('ection: keep-alive [70871.244917] Keep-Alive: timeout=5, max=1') data_len=285 off=239 Apr 26 11:45:20 192.168.122.209 [70871.249333] [tempesta fw] Warning: response dropped: processing error: 192.168.122.196 Apr 26 11:45:20 192.168.122.209 [70871.674558] [tdb] Close table 'client0.tdb' Apr 26 11:45:21 192.168.122.209 [70871.860297] [tdb] Close table 'sessions0.tdb' Apr 26 11:45:24 192.168.122.209 [70875.043199] [tdb] Close table 'cache0.tdb' Apr 26 11:45:24 192.168.122.209 [70875.299711] [tdb] Close table 'filter0.tdb' Apr 26 11:45:24 192.168.122.209 [70875.300148] [tempesta fw] modules are stopped Apr 26 11:45:24 192.168.122.209 [70875.477372] [tempesta fw] exiting... Apr 26 11:45:24 192.168.122.209 [70875.646798] [tdb] Shutdown Tempesta DB Apr 26 11:45:25 192.168.122.209 [70876.088821] End test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_hbh_headers_hbp_GET Apr 26 11:45:25 192.168.122.209 [70876.128910] Start test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_hbh_headers_hbp_HEAD Apr 26 11:45:26 192.168.122.209 [70877.545689] [tdb] Start Tempesta DB Apr 26 11:45:26 192.168.122.209 [70877.679972] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:45:28 192.168.122.209 [70879.250904] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70879.250904] Maybe that's fine, but it's worth checking the [70879.250904] config - if there is no relations between the [70879.250904] names, then host name confusion attack is possible. Apr 26 11:45:28 192.168.122.209 [70879.301240] [tempesta fw] Configuration processing is completed. Apr 26 11:45:28 192.168.122.209 [70879.358409] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:45:29 192.168.122.209 [70879.783845] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:45:29 192.168.122.209 [70879.809904] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:45:29 192.168.122.209 [70879.835487] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:45:29 192.168.122.209 [70879.889276] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:45:29 192.168.122.209 [70879.891009] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:45:29 192.168.122.209 [70879.949814] [tempesta fw] Tempesta FW is ready Apr 26 11:45:29 192.168.122.209 [70880.143806] [tempesta fw] Warning: Parser error: state=Resp_HdrConnectionV input(-8)=0x6b('ection: keep-alive [70880.143806] Keep-Alive: timeout=5, max=1') data_len=285 off=239 Apr 26 11:45:29 192.168.122.209 [70880.148152] [tempesta fw] Warning: response dropped: processing error: 192.168.122.196 Apr 26 11:45:29 192.168.122.209 [70880.632487] [tdb] Close table 'client0.tdb' Apr 26 11:45:30 192.168.122.209 [70880.818004] [tdb] Close table 'sessions0.tdb' Apr 26 11:45:33 192.168.122.209 [70883.945864] [tdb] Close table 'cache0.tdb' Apr 26 11:45:33 192.168.122.209 [70884.182253] [tdb] Close table 'filter0.tdb' Apr 26 11:45:33 192.168.122.209 [70884.182672] [tempesta fw] modules are stopped Apr 26 11:45:33 192.168.122.209 [70884.373360] [tempesta fw] exiting... Apr 26 11:45:33 192.168.122.209 [70884.499695] [tdb] Shutdown Tempesta DB Apr 26 11:45:34 192.168.122.209 [70884.882962] End test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_hbh_headers_hbp_HEAD Apr 26 11:45:34 192.168.122.209 [70884.920880] Start test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_hbh_headers_mix_GET Apr 26 11:45:35 192.168.122.209 [70886.371398] [tdb] Start Tempesta DB Apr 26 11:45:35 192.168.122.209 [70886.498902] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:45:37 192.168.122.209 [70888.015028] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70888.015028] Maybe that's fine, but it's worth checking the [70888.015028] config - if there is no relations between the [70888.015028] names, then host name confusion attack is possible. Apr 26 11:45:37 192.168.122.209 [70888.077347] [tempesta fw] Configuration processing is completed. Apr 26 11:45:37 192.168.122.209 [70888.134070] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:45:37 192.168.122.209 [70888.546216] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:45:37 192.168.122.209 [70888.571330] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:45:37 192.168.122.209 [70888.597083] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:45:37 192.168.122.209 [70888.653355] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:45:37 192.168.122.209 [70888.655076] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:45:38 192.168.122.209 [70888.697297] [tempesta fw] Tempesta FW is ready Apr 26 11:45:38 192.168.122.209 [70888.873904] [tempesta fw] Warning: Parser error: state=Resp_HdrConnectionV input(-8)=0x6b('ection: keep-alive [70888.873904] X-Token1: value1 [70888.873904] [70888.873904] ') data_len=269 off=237 Apr 26 11:45:38 192.168.122.209 [70888.878891] [tempesta fw] Warning: response dropped: processing error: 192.168.122.196 Apr 26 11:45:38 192.168.122.209 [70889.315046] [tdb] Close table 'client0.tdb' Apr 26 11:45:38 192.168.122.209 [70889.520726] [tdb] Close table 'sessions0.tdb' Apr 26 11:45:41 192.168.122.209 [70892.648096] [tdb] Close table 'cache0.tdb' Apr 26 11:45:42 192.168.122.209 [70892.890101] [tdb] Close table 'filter0.tdb' Apr 26 11:45:42 192.168.122.209 [70892.890610] [tempesta fw] modules are stopped Apr 26 11:45:42 192.168.122.209 [70893.098030] [tempesta fw] exiting... Apr 26 11:45:42 192.168.122.209 [70893.222677] [tdb] Shutdown Tempesta DB Apr 26 11:45:42 192.168.122.209 [70893.591081] End test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_hbh_headers_mix_GET Apr 26 11:45:42 192.168.122.209 [70893.625122] Start test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_hbh_headers_mix_HEAD Apr 26 11:45:44 192.168.122.209 [70895.049187] [tdb] Start Tempesta DB Apr 26 11:45:44 192.168.122.209 [70895.181150] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:45:46 192.168.122.209 [70896.711097] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70896.711097] Maybe that's fine, but it's worth checking the [70896.711097] config - if there is no relations between the [70896.711097] names, then host name confusion attack is possible. Apr 26 11:45:46 192.168.122.209 [70896.777455] [tempesta fw] Configuration processing is completed. Apr 26 11:45:46 192.168.122.209 [70896.834332] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:45:46 192.168.122.209 [70897.259522] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:45:46 192.168.122.209 [70897.285084] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:45:46 192.168.122.209 [70897.309959] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:45:46 192.168.122.209 [70897.373466] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:45:46 192.168.122.209 [70897.375217] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:45:46 192.168.122.209 [70897.413425] [tempesta fw] Tempesta FW is ready Apr 26 11:45:46 192.168.122.209 [70897.604794] [tempesta fw] Warning: Parser error: state=Resp_HdrConnectionV input(-8)=0x6b('ection: keep-alive [70897.604794] X-Token1: value1 [70897.604794] [70897.604794] ') data_len=269 off=237 Apr 26 11:45:46 192.168.122.209 [70897.609662] [tempesta fw] Warning: response dropped: processing error: 192.168.122.196 Apr 26 11:45:47 192.168.122.209 [70898.052225] [tdb] Close table 'client0.tdb' Apr 26 11:45:47 192.168.122.209 [70898.242987] [tdb] Close table 'sessions0.tdb' Apr 26 11:45:50 192.168.122.209 [70901.380634] [tdb] Close table 'cache0.tdb' Apr 26 11:45:50 192.168.122.209 [70901.623043] [tdb] Close table 'filter0.tdb' Apr 26 11:45:50 192.168.122.209 [70901.623494] [tempesta fw] modules are stopped Apr 26 11:45:51 192.168.122.209 [70901.809104] [tempesta fw] exiting... Apr 26 11:45:51 192.168.122.209 [70901.982451] [tdb] Shutdown Tempesta DB Apr 26 11:45:51 192.168.122.209 [70902.413896] End test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_hbh_headers_mix_HEAD Apr 26 11:45:51 192.168.122.209 [70902.442942] Start test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_same_hdr_and_trailer_head_to_get Apr 26 11:45:53 192.168.122.209 [70903.875087] [tdb] Start Tempesta DB Apr 26 11:45:53 192.168.122.209 [70904.001555] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:45:54 192.168.122.209 [70905.535227] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70905.535227] Maybe that's fine, but it's worth checking the [70905.535227] config - if there is no relations between the [70905.535227] names, then host name confusion attack is possible. Apr 26 11:45:54 192.168.122.209 [70905.589585] [tempesta fw] Configuration processing is completed. Apr 26 11:45:54 192.168.122.209 [70905.655517] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:45:55 192.168.122.209 [70906.078450] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:45:55 192.168.122.209 [70906.118379] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:45:55 192.168.122.209 [70906.144195] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:45:55 192.168.122.209 [70906.197598] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:45:55 192.168.122.209 [70906.199338] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:45:55 192.168.122.209 [70906.237550] [tempesta fw] Tempesta FW is ready Apr 26 11:45:56 192.168.122.209 [70906.887061] [tdb] Close table 'client0.tdb' Apr 26 11:45:56 192.168.122.209 [70907.083946] [tdb] Close table 'sessions0.tdb' Apr 26 11:45:59 192.168.122.209 [70910.198232] [tdb] Close table 'cache0.tdb' Apr 26 11:45:59 192.168.122.209 [70910.463351] [tdb] Close table 'filter0.tdb' Apr 26 11:45:59 192.168.122.209 [70910.463750] [tempesta fw] modules are stopped Apr 26 11:45:59 192.168.122.209 [70910.637844] [tempesta fw] exiting... Apr 26 11:46:00 192.168.122.209 [70910.787467] [tdb] Shutdown Tempesta DB Apr 26 11:46:00 192.168.122.209 [70911.161806] End test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_same_hdr_and_trailer_head_to_get Apr 26 11:46:00 192.168.122.209 [70911.243095] Start test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_same_hdr_and_trailer_head_to_get_multiple_1 Apr 26 11:46:01 192.168.122.209 [70912.561415] [tdb] Start Tempesta DB Apr 26 11:46:01 192.168.122.209 [70912.681672] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:46:03 192.168.122.209 [70914.299304] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70914.299304] Maybe that's fine, but it's worth checking the [70914.299304] config - if there is no relations between the [70914.299304] names, then host name confusion attack is possible. Apr 26 11:46:03 192.168.122.209 [70914.353603] [tempesta fw] Configuration processing is completed. Apr 26 11:46:03 192.168.122.209 [70914.408183] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:46:04 192.168.122.209 [70914.819149] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:46:04 192.168.122.209 [70914.844637] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:46:04 192.168.122.209 [70914.869861] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:46:04 192.168.122.209 [70914.913753] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:46:04 192.168.122.209 [70914.915456] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:46:04 192.168.122.209 [70914.965648] [tempesta fw] Tempesta FW is ready Apr 26 11:46:04 192.168.122.209 [70915.626500] [tdb] Close table 'client0.tdb' Apr 26 11:46:05 192.168.122.209 [70915.809141] [tdb] Close table 'sessions0.tdb' Apr 26 11:46:08 192.168.122.209 [70918.956150] [tdb] Close table 'cache0.tdb' Apr 26 11:46:08 192.168.122.209 [70919.202180] [tdb] Close table 'filter0.tdb' Apr 26 11:46:08 192.168.122.209 [70919.202603] [tempesta fw] modules are stopped Apr 26 11:46:08 192.168.122.209 [70919.386304] [tempesta fw] exiting... Apr 26 11:46:08 192.168.122.209 [70919.517564] [tdb] Shutdown Tempesta DB Apr 26 11:46:09 192.168.122.209 [70919.935137] End test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_same_hdr_and_trailer_head_to_get_multiple_1 Apr 26 11:46:09 192.168.122.209 [70919.969603] Start test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_same_hdr_and_trailer_head_to_get_multiple_2 Apr 26 11:46:10 192.168.122.209 [70921.371548] [tdb] Start Tempesta DB Apr 26 11:46:10 192.168.122.209 [70921.487400] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:46:12 192.168.122.209 [70923.155423] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70923.155423] Maybe that's fine, but it's worth checking the [70923.155423] config - if there is no relations between the [70923.155423] names, then host name confusion attack is possible. Apr 26 11:46:12 192.168.122.209 [70923.206090] [tempesta fw] Configuration processing is completed. Apr 26 11:46:12 192.168.122.209 [70923.260006] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:46:12 192.168.122.209 [70923.669017] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:46:12 192.168.122.209 [70923.696171] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:46:13 192.168.122.209 [70923.722659] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:46:13 192.168.122.209 [70923.761805] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:46:13 192.168.122.209 [70923.763500] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:46:13 192.168.122.209 [70923.805697] [tempesta fw] Tempesta FW is ready Apr 26 11:46:13 192.168.122.209 [70924.491940] [tdb] Close table 'client0.tdb' Apr 26 11:46:13 192.168.122.209 [70924.666002] [tdb] Close table 'sessions0.tdb' Apr 26 11:46:17 192.168.122.209 [70927.833288] [tdb] Close table 'cache0.tdb' Apr 26 11:46:17 192.168.122.209 [70928.067996] [tdb] Close table 'filter0.tdb' Apr 26 11:46:17 192.168.122.209 [70928.068434] [tempesta fw] modules are stopped Apr 26 11:46:17 192.168.122.209 [70928.285533] [tempesta fw] exiting... Apr 26 11:46:17 192.168.122.209 [70928.455232] [tdb] Shutdown Tempesta DB Apr 26 11:46:18 192.168.122.209 [70928.881460] End test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_same_hdr_and_trailer_head_to_get_multiple_2 Apr 26 11:46:18 192.168.122.209 [70928.917290] Start test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_same_trailer_head_to_get Apr 26 11:46:19 192.168.122.209 [70930.307106] [tdb] Start Tempesta DB Apr 26 11:46:19 192.168.122.209 [70930.444981] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:46:21 192.168.122.209 [70931.983546] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70931.983546] Maybe that's fine, but it's worth checking the [70931.983546] config - if there is no relations between the [70931.983546] names, then host name confusion attack is possible. Apr 26 11:46:21 192.168.122.209 [70932.026200] [tempesta fw] Configuration processing is completed. Apr 26 11:46:21 192.168.122.209 [70932.081864] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:46:21 192.168.122.209 [70932.494050] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:46:21 192.168.122.209 [70932.520524] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:46:21 192.168.122.209 [70932.548173] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:46:21 192.168.122.209 [70932.585942] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:46:21 192.168.122.209 [70932.587647] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:46:21 192.168.122.209 [70932.625888] [tempesta fw] Tempesta FW is ready Apr 26 11:46:22 192.168.122.209 [70933.287327] [tdb] Close table 'client0.tdb' Apr 26 11:46:22 192.168.122.209 [70933.469860] [tdb] Close table 'sessions0.tdb' Apr 26 11:46:25 192.168.122.209 [70936.583986] [tdb] Close table 'cache0.tdb' Apr 26 11:46:26 192.168.122.209 [70936.822992] [tdb] Close table 'filter0.tdb' Apr 26 11:46:26 192.168.122.209 [70936.823415] [tempesta fw] modules are stopped Apr 26 11:46:26 192.168.122.209 [70937.028001] [tempesta fw] exiting... Apr 26 11:46:26 192.168.122.209 [70937.176672] [tdb] Shutdown Tempesta DB Apr 26 11:46:26 192.168.122.209 [70937.598280] End test: cache.test_cache.TestCacheResponseWithTrailersHttp.test_same_trailer_head_to_get Apr 26 11:46:26 192.168.122.209 [70937.628663] Start test: cache.test_cache.TestCacheUseStaleCfg.test_cache_use_stale_config_dupl Apr 26 11:46:28 192.168.122.209 [70939.106097] [tdb] Start Tempesta DB Apr 26 11:46:28 192.168.122.209 [70939.235912] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:46:30 192.168.122.209 [70940.716832] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70940.716832] Maybe that's fine, but it's worth checking the [70940.716832] config - if there is no relations between the [70940.716832] names, then host name confusion attack is possible. Apr 26 11:46:30 192.168.122.209 [70940.794089] [tempesta fw] ERROR: duplicate entry: 'cache_use_stale', only one such entry is allowed. Apr 26 11:46:30 192.168.122.209 [70940.796597] [tempesta fw] ERROR: configuration parsing error: [70940.796597] 15: cache_use_stale 5*;cache_use_stale 4*; [70940.796597] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Apr 26 11:46:30 192.168.122.209 [70940.801070] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 11:46:30 192.168.122.209 [70941.001491] [tempesta fw] exiting... Apr 26 11:46:30 192.168.122.209 [70941.146549] [tdb] Shutdown Tempesta DB Apr 26 11:46:31 192.168.122.209 [70941.934631] End test: cache.test_cache.TestCacheUseStaleCfg.test_cache_use_stale_config_dupl Apr 26 11:46:31 192.168.122.209 [70941.982604] Start test: cache.test_cache.TestCacheUseStaleCfg.test_cache_use_stale_config_wrong_code Apr 26 11:46:32 192.168.122.209 [70943.424362] [tdb] Start Tempesta DB Apr 26 11:46:32 192.168.122.209 [70943.549012] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:46:33 192.168.122.209 [70944.111709] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70944.111709] Maybe that's fine, but it's worth checking the [70944.111709] config - if there is no relations between the [70944.111709] names, then host name confusion attack is possible. Apr 26 11:46:33 192.168.122.209 [70944.178201] [tempesta fw] ERROR: Please specify status code above than 399. Apr 26 11:46:33 192.168.122.209 [70944.178213] [tempesta fw] ERROR: configuration parsing error: [70944.178213] 15: cache_use_stale 200; [70944.178213] ^^^^^^^^^^^^^^^^^^^^ Apr 26 11:46:33 192.168.122.209 [70944.183790] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 11:46:33 192.168.122.209 [70944.394531] [tempesta fw] exiting... Apr 26 11:46:33 192.168.122.209 [70944.538056] [tdb] Shutdown Tempesta DB Apr 26 11:46:34 192.168.122.209 [70945.209957] End test: cache.test_cache.TestCacheUseStaleCfg.test_cache_use_stale_config_wrong_code Apr 26 11:46:34 192.168.122.209 [70945.243361] Start test: cache.test_cache.TestCacheUseStaleCfg.test_cache_use_stale_config_wrong_mask Apr 26 11:46:36 192.168.122.209 [70946.786873] [tdb] Start Tempesta DB Apr 26 11:46:36 192.168.122.209 [70946.908180] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:46:36 192.168.122.209 [70947.483803] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70947.483803] Maybe that's fine, but it's worth checking the [70947.483803] config - if there is no relations between the [70947.483803] names, then host name confusion attack is possible. Apr 26 11:46:36 192.168.122.209 [70947.546316] [tempesta fw] ERROR: cache_use_stale Unsupported argument "3*" Apr 26 11:46:36 192.168.122.209 [70947.546328] [tempesta fw] ERROR: configuration parsing error: [70947.546328] 15: cache_use_stale 3*; [70947.546328] ^^^^^^^^^^^^^^^^^^^ Apr 26 11:46:36 192.168.122.209 [70947.551900] [tempesta fw] Warning: Configuration parsing has failed. Clean up... Apr 26 11:46:37 192.168.122.209 [70947.758794] [tempesta fw] exiting... Apr 26 11:46:37 192.168.122.209 [70947.888796] [tdb] Shutdown Tempesta DB Apr 26 11:46:37 192.168.122.209 [70948.574922] End test: cache.test_cache.TestCacheUseStaleCfg.test_cache_use_stale_config_wrong_mask Apr 26 11:46:37 192.168.122.209 [70948.612703] Start test: cache.test_cache.TestCacheVhost.test_h2 Apr 26 11:46:39 192.168.122.209 [70949.964197] [tdb] Start Tempesta DB Apr 26 11:46:39 192.168.122.209 [70950.092127] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:46:40 192.168.122.209 [70950.896283] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [70950.896283] Maybe that's fine, but it's worth checking the [70950.896283] config - if there is no relations between the [70950.896283] names, then host name confusion attack is possible. Apr 26 11:46:40 192.168.122.209 [70950.998278] [tempesta fw] Configuration processing is completed. Apr 26 11:46:40 192.168.122.209 [70951.061029] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:46:40 192.168.122.209 [70951.479516] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:46:40 192.168.122.209 [70951.505801] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:46:40 192.168.122.209 [70951.531998] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:46:40 192.168.122.209 [70951.602916] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:46:40 192.168.122.209 [70951.650128] [tempesta fw] Tempesta FW is ready Apr 26 11:46:41 192.168.122.209 [70952.526978] [tdb] Close table 'client0.tdb' Apr 26 11:46:42 192.168.122.209 [70952.709150] [tdb] Close table 'sessions0.tdb' Apr 26 11:46:45 192.168.122.209 [70955.859871] [tdb] Close table 'cache0.tdb' Apr 26 11:46:45 192.168.122.209 [70956.119008] [tdb] Close table 'filter0.tdb' Apr 26 11:46:45 192.168.122.209 [70956.119443] [tempesta fw] modules are stopped Apr 26 11:46:45 192.168.122.209 [70956.348219] [tempesta fw] exiting... Apr 26 11:46:45 192.168.122.209 [70956.460332] [tdb] Shutdown Tempesta DB Apr 26 11:46:46 192.168.122.209 [70956.885347] End test: cache.test_cache.TestCacheVhost.test_h2 Apr 26 11:46:46 192.168.122.209 [70956.924865] Start test: cache.test_cache.TestCacheVhost.test_https Apr 26 11:46:47 192.168.122.209 [70958.373309] [tdb] Start Tempesta DB Apr 26 11:46:47 192.168.122.209 [70958.499619] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:46:49 192.168.122.209 [70960.240283] [tempesta fw] Warning: Vhost tempesta-tech.com doesn't have certificate with matching SAN/CN. [70960.240283] Maybe that's fine, but it's worth checking the [70960.240283] config - if there is no relations between the [70960.240283] names, then host name confusion attack is possible. Apr 26 11:46:49 192.168.122.209 [70960.338379] [tempesta fw] Configuration processing is completed. Apr 26 11:46:49 192.168.122.209 [70960.394556] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:46:50 192.168.122.209 [70960.813089] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:46:50 192.168.122.209 [70960.838321] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:46:50 192.168.122.209 [70960.863222] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:46:50 192.168.122.209 [70960.938322] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:46:50 192.168.122.209 [70960.982266] [tempesta fw] Tempesta FW is ready Apr 26 11:46:51 192.168.122.209 [70961.851949] [tdb] Close table 'client0.tdb' Apr 26 11:46:51 192.168.122.209 [70962.041361] [tdb] Close table 'sessions0.tdb' Apr 26 11:46:54 192.168.122.209 [70965.224470] [tdb] Close table 'cache0.tdb' Apr 26 11:46:54 192.168.122.209 [70965.459477] [tdb] Close table 'filter0.tdb' Apr 26 11:46:54 192.168.122.209 [70965.459894] [tempesta fw] modules are stopped Apr 26 11:46:54 192.168.122.209 [70965.678356] [tempesta fw] exiting... Apr 26 11:46:55 192.168.122.209 [70965.805113] [tdb] Shutdown Tempesta DB Apr 26 11:46:55 192.168.122.209 [70966.231143] End test: cache.test_cache.TestCacheVhost.test_https Apr 26 11:46:55 192.168.122.209 [70966.264566] Start test: cache.test_cache.TestChunkedResponse.test_cached_data_equal_to_original Apr 26 11:46:56 192.168.122.209 [70967.662662] [tdb] Start Tempesta DB Apr 26 11:46:57 192.168.122.209 [70967.793835] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:46:58 192.168.122.209 [70969.171746] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70969.171746] Maybe that's fine, but it's worth checking the [70969.171746] config - if there is no relations between the [70969.171746] names, then host name confusion attack is possible. Apr 26 11:46:58 192.168.122.209 [70969.302456] [tempesta fw] Configuration processing is completed. Apr 26 11:46:58 192.168.122.209 [70969.362367] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:46:59 192.168.122.209 [70969.776477] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:46:59 192.168.122.209 [70969.802800] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:46:59 192.168.122.209 [70969.828671] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:46:59 192.168.122.209 [70969.878395] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:46:59 192.168.122.209 [70969.880177] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:46:59 192.168.122.209 [70969.922359] [tempesta fw] Tempesta FW is ready Apr 26 11:46:59 192.168.122.209 [70970.627706] [tdb] Close table 'client0.tdb' Apr 26 11:47:00 192.168.122.209 [70970.826325] [tdb] Close table 'sessions0.tdb' Apr 26 11:47:03 192.168.122.209 [70974.007674] [tdb] Close table 'cache0.tdb' Apr 26 11:47:03 192.168.122.209 [70974.266017] [tdb] Close table 'filter0.tdb' Apr 26 11:47:03 192.168.122.209 [70974.266805] [tempesta fw] modules are stopped Apr 26 11:47:03 192.168.122.209 [70974.474423] [tempesta fw] exiting... Apr 26 11:47:03 192.168.122.209 [70974.608309] [tdb] Shutdown Tempesta DB Apr 26 11:47:04 192.168.122.209 [70974.980299] End test: cache.test_cache.TestChunkedResponse.test_cached_data_equal_to_original Apr 26 11:47:04 192.168.122.209 [70975.013720] Start test: cache.test_cache.TestChunkedResponse.test_h2_cached_data_equal_to_original Apr 26 11:47:05 192.168.122.209 [70976.415095] [tdb] Start Tempesta DB Apr 26 11:47:05 192.168.122.209 [70976.540968] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:47:07 192.168.122.209 [70977.903767] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70977.903767] Maybe that's fine, but it's worth checking the [70977.903767] config - if there is no relations between the [70977.903767] names, then host name confusion attack is possible. Apr 26 11:47:07 192.168.122.209 [70978.042701] [tempesta fw] Configuration processing is completed. Apr 26 11:47:07 192.168.122.209 [70978.100302] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:47:07 192.168.122.209 [70978.520554] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:47:07 192.168.122.209 [70978.545922] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:47:07 192.168.122.209 [70978.571792] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:47:07 192.168.122.209 [70978.614545] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:47:07 192.168.122.209 [70978.616310] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:47:07 192.168.122.209 [70978.654475] [tempesta fw] Tempesta FW is ready Apr 26 11:47:08 192.168.122.209 [70979.386109] [tdb] Close table 'client0.tdb' Apr 26 11:47:08 192.168.122.209 [70979.571074] [tdb] Close table 'sessions0.tdb' Apr 26 11:47:12 192.168.122.209 [70982.768015] [tdb] Close table 'cache0.tdb' Apr 26 11:47:12 192.168.122.209 [70983.019393] [tdb] Close table 'filter0.tdb' Apr 26 11:47:12 192.168.122.209 [70983.019842] [tempesta fw] modules are stopped Apr 26 11:47:12 192.168.122.209 [70983.225243] [tempesta fw] exiting... Apr 26 11:47:12 192.168.122.209 [70983.348377] [tdb] Shutdown Tempesta DB Apr 26 11:47:13 192.168.122.209 [70983.739747] End test: cache.test_cache.TestChunkedResponse.test_h2_cached_data_equal_to_original Apr 26 11:47:13 192.168.122.209 [70983.822862] Start test: cache.test_cache.TestH2CacheDisable.test_cache_disable Apr 26 11:47:14 192.168.122.209 [70985.251284] [tdb] Start Tempesta DB Apr 26 11:47:14 192.168.122.209 [70985.382857] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:47:16 192.168.122.209 [70987.015891] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70987.015891] Maybe that's fine, but it's worth checking the [70987.015891] config - if there is no relations between the [70987.015891] names, then host name confusion attack is possible. Apr 26 11:47:16 192.168.122.209 [70987.194666] [tempesta fw] Configuration processing is completed. Apr 26 11:47:16 192.168.122.209 [70987.252833] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:47:16 192.168.122.209 [70987.675410] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:47:17 192.168.122.209 [70987.702571] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:47:17 192.168.122.209 [70987.728991] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:47:17 192.168.122.209 [70987.810630] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:47:17 192.168.122.209 [70987.812415] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:47:17 192.168.122.209 [70987.854571] [tempesta fw] Tempesta FW is ready Apr 26 11:47:17 192.168.122.209 [70988.532010] [tdb] Close table 'client0.tdb' Apr 26 11:47:18 192.168.122.209 [70988.721852] [tdb] Close table 'sessions0.tdb' Apr 26 11:47:21 192.168.122.209 [70991.905822] [tdb] Close table 'cache0.tdb' Apr 26 11:47:21 192.168.122.209 [70992.167508] [tdb] Close table 'filter0.tdb' Apr 26 11:47:21 192.168.122.209 [70992.167945] [tempesta fw] modules are stopped Apr 26 11:47:21 192.168.122.209 [70992.371395] [tempesta fw] exiting... Apr 26 11:47:21 192.168.122.209 [70992.496164] [tdb] Shutdown Tempesta DB Apr 26 11:47:22 192.168.122.209 [70992.938973] End test: cache.test_cache.TestH2CacheDisable.test_cache_disable Apr 26 11:47:22 192.168.122.209 [70992.975119] Start test: cache.test_cache.TestH2CacheDisable.test_cache_disable_0 Apr 26 11:47:23 192.168.122.209 [70994.374262] [tdb] Start Tempesta DB Apr 26 11:47:23 192.168.122.209 [70994.508733] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:47:25 192.168.122.209 [70996.136020] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [70996.136020] Maybe that's fine, but it's worth checking the [70996.136020] config - if there is no relations between the [70996.136020] names, then host name confusion attack is possible. Apr 26 11:47:25 192.168.122.209 [70996.298791] [tempesta fw] Configuration processing is completed. Apr 26 11:47:25 192.168.122.209 [70996.352921] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:47:26 192.168.122.209 [70996.776989] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:47:26 192.168.122.209 [70996.804835] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:47:26 192.168.122.209 [70996.830988] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:47:26 192.168.122.209 [70996.918766] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:47:26 192.168.122.209 [70996.920489] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:47:26 192.168.122.209 [70996.978740] [tempesta fw] Tempesta FW is ready Apr 26 11:47:26 192.168.122.209 [70997.644145] [tdb] Close table 'client0.tdb' Apr 26 11:47:27 192.168.122.209 [70997.831401] [tdb] Close table 'sessions0.tdb' Apr 26 11:47:30 192.168.122.209 [71000.977695] [tdb] Close table 'cache0.tdb' Apr 26 11:47:30 192.168.122.209 [71001.223630] [tdb] Close table 'filter0.tdb' Apr 26 11:47:30 192.168.122.209 [71001.224070] [tempesta fw] modules are stopped Apr 26 11:47:30 192.168.122.209 [71001.426864] [tempesta fw] exiting... Apr 26 11:47:30 192.168.122.209 [71001.572783] [tdb] Shutdown Tempesta DB Apr 26 11:47:31 192.168.122.209 [71001.921929] End test: cache.test_cache.TestH2CacheDisable.test_cache_disable_0 Apr 26 11:47:31 192.168.122.209 [71001.960741] Start test: cache.test_cache.TestH2CacheDisable.test_cache_disable_1 Apr 26 11:47:32 192.168.122.209 [71003.285157] [tdb] Start Tempesta DB Apr 26 11:47:32 192.168.122.209 [71003.400311] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:47:34 192.168.122.209 [71005.020122] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [71005.020122] Maybe that's fine, but it's worth checking the [71005.020122] config - if there is no relations between the [71005.020122] names, then host name confusion attack is possible. Apr 26 11:47:34 192.168.122.209 [71005.202932] [tempesta fw] Configuration processing is completed. Apr 26 11:47:34 192.168.122.209 [71005.266018] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:47:34 192.168.122.209 [71005.685703] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:47:35 192.168.122.209 [71005.712166] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:47:35 192.168.122.209 [71005.740086] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:47:35 192.168.122.209 [71005.778867] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:47:35 192.168.122.209 [71005.780585] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:47:35 192.168.122.209 [71005.822821] [tempesta fw] Tempesta FW is ready Apr 26 11:47:35 192.168.122.209 [71006.477268] [tdb] Close table 'client0.tdb' Apr 26 11:47:35 192.168.122.209 [71006.669955] [tdb] Close table 'sessions0.tdb' Apr 26 11:47:39 192.168.122.209 [71009.824171] [tdb] Close table 'cache0.tdb' Apr 26 11:47:39 192.168.122.209 [71010.056423] [tdb] Close table 'filter0.tdb' Apr 26 11:47:39 192.168.122.209 [71010.056818] [tempesta fw] modules are stopped Apr 26 11:47:39 192.168.122.209 [71010.275698] [tempesta fw] exiting... Apr 26 11:47:39 192.168.122.209 [71010.432339] [tdb] Shutdown Tempesta DB Apr 26 11:47:40 192.168.122.209 [71010.810139] End test: cache.test_cache.TestH2CacheDisable.test_cache_disable_1 Apr 26 11:47:40 192.168.122.209 [71010.836238] Start test: cache.test_cache.TestH2CacheDisable.test_cache_disable_with_override_http_chain Apr 26 11:47:41 192.168.122.209 [71012.410281] [tdb] Start Tempesta DB Apr 26 11:47:41 192.168.122.209 [71012.535369] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:47:43 192.168.122.209 [71014.068312] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [71014.068312] Maybe that's fine, but it's worth checking the [71014.068312] config - if there is no relations between the [71014.068312] names, then host name confusion attack is possible. Apr 26 11:47:43 192.168.122.209 [71014.259038] [tempesta fw] Configuration processing is completed. Apr 26 11:47:43 192.168.122.209 [71014.325774] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:47:44 192.168.122.209 [71014.757584] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:47:44 192.168.122.209 [71014.783306] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:47:44 192.168.122.209 [71014.808549] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:47:44 192.168.122.209 [71014.846959] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:47:44 192.168.122.209 [71014.848704] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:47:44 192.168.122.209 [71014.898943] [tempesta fw] Tempesta FW is ready Apr 26 11:47:44 192.168.122.209 [71015.577925] [tdb] Close table 'client0.tdb' Apr 26 11:47:45 192.168.122.209 [71015.770541] [tdb] Close table 'sessions0.tdb' Apr 26 11:47:48 192.168.122.209 [71019.000435] [tdb] Close table 'cache0.tdb' Apr 26 11:47:48 192.168.122.209 [71019.253283] [tdb] Close table 'filter0.tdb' Apr 26 11:47:48 192.168.122.209 [71019.253806] [tempesta fw] modules are stopped Apr 26 11:47:48 192.168.122.209 [71019.450078] [tempesta fw] exiting... Apr 26 11:47:48 192.168.122.209 [71019.571943] [tdb] Shutdown Tempesta DB Apr 26 11:47:49 192.168.122.209 [71019.992522] End test: cache.test_cache.TestH2CacheDisable.test_cache_disable_with_override_http_chain Apr 26 11:47:49 192.168.122.209 [71020.024733] Start test: cache.test_cache.TestH2CacheHdrDel.test_cache_bypass Apr 26 11:47:50 192.168.122.209 [71021.435795] [tdb] Start Tempesta DB Apr 26 11:47:50 192.168.122.209 [71021.567112] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:47:52 192.168.122.209 [71022.956352] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [71022.956352] Maybe that's fine, but it's worth checking the [71022.956352] config - if there is no relations between the [71022.956352] names, then host name confusion attack is possible. Apr 26 11:47:52 192.168.122.209 [71023.059145] [tempesta fw] Configuration processing is completed. Apr 26 11:47:52 192.168.122.209 [71023.117599] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:47:52 192.168.122.209 [71023.533955] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:47:52 192.168.122.209 [71023.559057] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:47:52 192.168.122.209 [71023.584679] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:47:52 192.168.122.209 [71023.623113] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:47:52 192.168.122.209 [71023.624861] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:47:52 192.168.122.209 [71023.663055] [tempesta fw] Tempesta FW is ready Apr 26 11:47:53 192.168.122.209 [71024.299054] [tdb] Close table 'client0.tdb' Apr 26 11:47:53 192.168.122.209 [71024.484881] [tdb] Close table 'sessions0.tdb' Apr 26 11:47:56 192.168.122.209 [71027.661989] [tdb] Close table 'cache0.tdb' Apr 26 11:47:57 192.168.122.209 [71027.904976] [tdb] Close table 'filter0.tdb' Apr 26 11:47:57 192.168.122.209 [71027.905407] [tempesta fw] modules are stopped Apr 26 11:47:57 192.168.122.209 [71028.095064] [tempesta fw] exiting... Apr 26 11:47:57 192.168.122.209 [71028.246651] [tdb] Shutdown Tempesta DB Apr 26 11:47:57 192.168.122.209 [71028.638842] End test: cache.test_cache.TestH2CacheHdrDel.test_cache_bypass Apr 26 11:47:57 192.168.122.209 [71028.666686] Start test: cache.test_cache.TestH2CacheHdrDel.test_cache_bypass_and_hdr_del Apr 26 11:47:59 192.168.122.209 [71030.111593] [tdb] Start Tempesta DB Apr 26 11:47:59 192.168.122.209 [71030.263395] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:48:01 192.168.122.209 [71031.716447] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [71031.716447] Maybe that's fine, but it's worth checking the [71031.716447] config - if there is no relations between the [71031.716447] names, then host name confusion attack is possible. Apr 26 11:48:01 192.168.122.209 [71031.839236] [tempesta fw] Configuration processing is completed. Apr 26 11:48:01 192.168.122.209 [71031.895255] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:48:01 192.168.122.209 [71032.310482] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:48:01 192.168.122.209 [71032.343355] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:48:01 192.168.122.209 [71032.368909] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:48:01 192.168.122.209 [71032.415200] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:48:01 192.168.122.209 [71032.416940] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:48:01 192.168.122.209 [71032.459146] [tempesta fw] Tempesta FW is ready Apr 26 11:48:02 192.168.122.209 [71033.143034] [tdb] Close table 'client0.tdb' Apr 26 11:48:02 192.168.122.209 [71033.333030] [tdb] Close table 'sessions0.tdb' Apr 26 11:48:05 192.168.122.209 [71036.484166] [tdb] Close table 'cache0.tdb' Apr 26 11:48:06 192.168.122.209 [71036.776838] [tdb] Close table 'filter0.tdb' Apr 26 11:48:06 192.168.122.209 [71036.777258] [tempesta fw] modules are stopped Apr 26 11:48:06 192.168.122.209 [71036.966970] [tempesta fw] exiting... Apr 26 11:48:06 192.168.122.209 [71037.094071] [tdb] Shutdown Tempesta DB Apr 26 11:48:06 192.168.122.209 [71037.509081] End test: cache.test_cache.TestH2CacheHdrDel.test_cache_bypass_and_hdr_del Apr 26 11:48:06 192.168.122.209 [71037.537183] Start test: cache.test_cache.TestH2CacheHdrDel.test_cache_bypass_no_cache_with_arg Apr 26 11:48:08 192.168.122.209 [71038.905881] [tdb] Start Tempesta DB Apr 26 11:48:08 192.168.122.209 [71039.035171] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:48:09 192.168.122.209 [71040.396536] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [71040.396536] Maybe that's fine, but it's worth checking the [71040.396536] config - if there is no relations between the [71040.396536] names, then host name confusion attack is possible. Apr 26 11:48:09 192.168.122.209 [71040.515580] [tempesta fw] Configuration processing is completed. Apr 26 11:48:09 192.168.122.209 [71040.566959] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:48:10 192.168.122.209 [71040.989235] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:48:10 192.168.122.209 [71041.015841] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:48:10 192.168.122.209 [71041.042237] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:48:10 192.168.122.209 [71041.099315] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:48:10 192.168.122.209 [71041.101054] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:48:10 192.168.122.209 [71041.139225] [tempesta fw] Tempesta FW is ready Apr 26 11:48:11 192.168.122.209 [71041.797488] [tdb] Close table 'client0.tdb' Apr 26 11:48:11 192.168.122.209 [71041.981766] [tdb] Close table 'sessions0.tdb' Apr 26 11:48:14 192.168.122.209 [71045.160335] [tdb] Close table 'cache0.tdb' Apr 26 11:48:14 192.168.122.209 [71045.416124] [tdb] Close table 'filter0.tdb' Apr 26 11:48:14 192.168.122.209 [71045.416556] [tempesta fw] modules are stopped Apr 26 11:48:14 192.168.122.209 [71045.612709] [tempesta fw] exiting... Apr 26 11:48:15 192.168.122.209 [71045.770391] [tdb] Shutdown Tempesta DB Apr 26 11:48:15 192.168.122.209 [71046.116714] End test: cache.test_cache.TestH2CacheHdrDel.test_cache_bypass_no_cache_with_arg Apr 26 11:48:15 192.168.122.209 [71046.148017] Start test: cache.test_cache.TestH2CacheHdrDel.test_cache_bypass_private_with_arg Apr 26 11:48:16 192.168.122.209 [71047.395262] [tdb] Start Tempesta DB Apr 26 11:48:16 192.168.122.209 [71047.525496] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:48:18 192.168.122.209 [71048.876662] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [71048.876662] Maybe that's fine, but it's worth checking the [71048.876662] config - if there is no relations between the [71048.876662] names, then host name confusion attack is possible. Apr 26 11:48:18 192.168.122.209 [71049.007434] [tempesta fw] Configuration processing is completed. Apr 26 11:48:18 192.168.122.209 [71049.062170] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:48:18 192.168.122.209 [71049.490964] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:48:18 192.168.122.209 [71049.517501] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:48:18 192.168.122.209 [71049.544514] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:48:18 192.168.122.209 [71049.631422] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:48:18 192.168.122.209 [71049.633138] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:48:18 192.168.122.209 [71049.683387] [tempesta fw] Tempesta FW is ready Apr 26 11:48:19 192.168.122.209 [71050.316870] [tdb] Close table 'client0.tdb' Apr 26 11:48:19 192.168.122.209 [71050.484911] [tdb] Close table 'sessions0.tdb' Apr 26 11:48:22 192.168.122.209 [71053.628672] [tdb] Close table 'cache0.tdb' Apr 26 11:48:23 192.168.122.209 [71053.870981] [tdb] Close table 'filter0.tdb' Apr 26 11:48:23 192.168.122.209 [71053.872519] [tempesta fw] modules are stopped Apr 26 11:48:23 192.168.122.209 [71054.088954] [tempesta fw] exiting... Apr 26 11:48:23 192.168.122.209 [71054.214706] [tdb] Shutdown Tempesta DB Apr 26 11:48:23 192.168.122.209 [71054.594215] End test: cache.test_cache.TestH2CacheHdrDel.test_cache_bypass_private_with_arg Apr 26 11:48:23 192.168.122.209 [71054.632702] Start test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfill Apr 26 11:48:25 192.168.122.209 [71056.039639] [tdb] Start Tempesta DB Apr 26 11:48:25 192.168.122.209 [71056.166357] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:48:27 192.168.122.209 [71057.700763] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [71057.700763] Maybe that's fine, but it's worth checking the [71057.700763] config - if there is no relations between the [71057.700763] names, then host name confusion attack is possible. Apr 26 11:48:27 192.168.122.209 [71057.807601] [tempesta fw] Configuration processing is completed. Apr 26 11:48:27 192.168.122.209 [71057.859249] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:48:27 192.168.122.209 [71058.270561] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:48:27 192.168.122.209 [71058.295609] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:48:27 192.168.122.209 [71058.320337] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:48:27 192.168.122.209 [71058.367534] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:48:27 192.168.122.209 [71058.369267] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:48:27 192.168.122.209 [71058.407479] [tempesta fw] Tempesta FW is ready Apr 26 11:48:28 192.168.122.209 [71059.021733] [tdb] Close table 'client0.tdb' Apr 26 11:48:28 192.168.122.209 [71059.202286] [tdb] Close table 'sessions0.tdb' Apr 26 11:48:31 192.168.122.209 [71062.378041] [tdb] Close table 'cache0.tdb' Apr 26 11:48:31 192.168.122.209 [71062.630964] [tdb] Close table 'filter0.tdb' Apr 26 11:48:31 192.168.122.209 [71062.631399] [tempesta fw] modules are stopped Apr 26 11:48:32 192.168.122.209 [71062.837300] [tempesta fw] exiting... Apr 26 11:48:32 192.168.122.209 [71062.948264] [tdb] Shutdown Tempesta DB Apr 26 11:48:32 192.168.122.209 [71063.351129] End test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfill Apr 26 11:48:32 192.168.122.209 [71063.371734] Start test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfill_and_hdr_del Apr 26 11:48:33 192.168.122.209 [71064.668743] [tdb] Start Tempesta DB Apr 26 11:48:34 192.168.122.209 [71064.790497] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:48:35 192.168.122.209 [71066.220878] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [71066.220878] Maybe that's fine, but it's worth checking the [71066.220878] config - if there is no relations between the [71066.220878] names, then host name confusion attack is possible. Apr 26 11:48:35 192.168.122.209 [71066.359661] [tempesta fw] Configuration processing is completed. Apr 26 11:48:35 192.168.122.209 [71066.411625] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:48:36 192.168.122.209 [71066.815694] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:48:36 192.168.122.209 [71066.840532] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:48:36 192.168.122.209 [71066.864542] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:48:36 192.168.122.209 [71066.911654] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:48:36 192.168.122.209 [71066.913373] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:48:36 192.168.122.209 [71066.951689] [tempesta fw] Tempesta FW is ready Apr 26 11:48:36 192.168.122.209 [71067.560521] [tdb] Close table 'client0.tdb' Apr 26 11:48:37 192.168.122.209 [71067.730374] [tdb] Close table 'sessions0.tdb' Apr 26 11:48:40 192.168.122.209 [71070.880871] [tdb] Close table 'cache0.tdb' Apr 26 11:48:40 192.168.122.209 [71071.109402] [tdb] Close table 'filter0.tdb' Apr 26 11:48:40 192.168.122.209 [71071.109805] [tempesta fw] modules are stopped Apr 26 11:48:40 192.168.122.209 [71071.315981] [tempesta fw] exiting... Apr 26 11:48:40 192.168.122.209 [71071.451189] [tdb] Shutdown Tempesta DB Apr 26 11:48:41 192.168.122.209 [71071.820288] End test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfill_and_hdr_del Apr 26 11:48:41 192.168.122.209 [71071.845749] Start test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfilll_multi_cache_control Apr 26 11:48:42 192.168.122.209 [71073.056096] [tdb] Start Tempesta DB Apr 26 11:48:42 192.168.122.209 [71073.193086] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:48:43 192.168.122.209 [71074.553064] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [71074.553064] Maybe that's fine, but it's worth checking the [71074.553064] config - if there is no relations between the [71074.553064] names, then host name confusion attack is possible. Apr 26 11:48:43 192.168.122.209 [71074.655763] [tempesta fw] Configuration processing is completed. Apr 26 11:48:44 192.168.122.209 [71074.716926] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:48:44 192.168.122.209 [71075.137173] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:48:44 192.168.122.209 [71075.163328] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:48:44 192.168.122.209 [71075.189747] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:48:44 192.168.122.209 [71075.231752] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:48:44 192.168.122.209 [71075.233472] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:48:44 192.168.122.209 [71075.271720] [tempesta fw] Tempesta FW is ready Apr 26 11:48:45 192.168.122.209 [71075.872803] [tdb] Close table 'client0.tdb' Apr 26 11:48:45 192.168.122.209 [71076.069590] [tdb] Close table 'sessions0.tdb' Apr 26 11:48:48 192.168.122.209 [71079.228750] [tdb] Close table 'cache0.tdb' Apr 26 11:48:48 192.168.122.209 [71079.481409] [tdb] Close table 'filter0.tdb' Apr 26 11:48:48 192.168.122.209 [71079.481815] [tempesta fw] modules are stopped Apr 26 11:48:48 192.168.122.209 [71079.660535] [tempesta fw] exiting... Apr 26 11:48:49 192.168.122.209 [71079.787042] [tdb] Shutdown Tempesta DB Apr 26 11:48:49 192.168.122.209 [71080.156217] End test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfilll_multi_cache_control Apr 26 11:48:49 192.168.122.209 [71080.179306] Start test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfilll_multi_cache_control_2 Apr 26 11:48:50 192.168.122.209 [71081.450984] [tdb] Start Tempesta DB Apr 26 11:48:50 192.168.122.209 [71081.584466] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:48:52 192.168.122.209 [71083.065107] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [71083.065107] Maybe that's fine, but it's worth checking the [71083.065107] config - if there is no relations between the [71083.065107] names, then host name confusion attack is possible. Apr 26 11:48:52 192.168.122.209 [71083.172045] [tempesta fw] Configuration processing is completed. Apr 26 11:48:52 192.168.122.209 [71083.231995] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:48:52 192.168.122.209 [71083.659560] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:48:52 192.168.122.209 [71083.691394] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:48:53 192.168.122.209 [71083.717970] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:48:53 192.168.122.209 [71083.767893] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:48:53 192.168.122.209 [71083.769963] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:48:53 192.168.122.209 [71083.807832] [tempesta fw] Tempesta FW is ready Apr 26 11:48:53 192.168.122.209 [71084.463262] [tdb] Close table 'client0.tdb' Apr 26 11:48:53 192.168.122.209 [71084.651471] [tdb] Close table 'sessions0.tdb' Apr 26 11:48:57 192.168.122.209 [71087.794607] [tdb] Close table 'cache0.tdb' Apr 26 11:48:57 192.168.122.209 [71088.039192] [tdb] Close table 'filter0.tdb' Apr 26 11:48:57 192.168.122.209 [71088.039594] [tempesta fw] modules are stopped Apr 26 11:48:57 192.168.122.209 [71088.216008] [tempesta fw] exiting... Apr 26 11:48:57 192.168.122.209 [71088.373432] [tdb] Shutdown Tempesta DB Apr 26 11:48:58 192.168.122.209 [71088.769627] End test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfilll_multi_cache_control_2 Apr 26 11:48:58 192.168.122.209 [71088.798512] Start test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfilll_no_cache_with_arg Apr 26 11:48:59 192.168.122.209 [71090.052756] [tdb] Start Tempesta DB Apr 26 11:48:59 192.168.122.209 [71090.186461] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:49:00 192.168.122.209 [71091.645232] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [71091.645232] Maybe that's fine, but it's worth checking the [71091.645232] config - if there is no relations between the [71091.645232] names, then host name confusion attack is possible. Apr 26 11:49:01 192.168.122.209 [71091.760008] [tempesta fw] Configuration processing is completed. Apr 26 11:49:01 192.168.122.209 [71091.810494] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:49:01 192.168.122.209 [71092.222421] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:49:01 192.168.122.209 [71092.248483] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:49:01 192.168.122.209 [71092.274401] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:49:01 192.168.122.209 [71092.319984] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:49:01 192.168.122.209 [71092.321696] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:49:01 192.168.122.209 [71092.367923] [tempesta fw] Tempesta FW is ready Apr 26 11:49:02 192.168.122.209 [71093.037771] [tdb] Close table 'client0.tdb' Apr 26 11:49:02 192.168.122.209 [71093.223508] [tdb] Close table 'sessions0.tdb' Apr 26 11:49:05 192.168.122.209 [71096.370662] [tdb] Close table 'cache0.tdb' Apr 26 11:49:05 192.168.122.209 [71096.627458] [tdb] Close table 'filter0.tdb' Apr 26 11:49:05 192.168.122.209 [71096.628305] [tempesta fw] modules are stopped Apr 26 11:49:06 192.168.122.209 [71096.826857] [tempesta fw] exiting... Apr 26 11:49:06 192.168.122.209 [71096.944595] [tdb] Shutdown Tempesta DB Apr 26 11:49:06 192.168.122.209 [71097.320437] End test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfilll_no_cache_with_arg Apr 26 11:49:06 192.168.122.209 [71097.348530] Start test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfilll_no_cache_with_arg_2 Apr 26 11:49:07 192.168.122.209 [71098.637678] [tdb] Start Tempesta DB Apr 26 11:49:08 192.168.122.209 [71098.772066] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:49:09 192.168.122.209 [71100.137324] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [71100.137324] Maybe that's fine, but it's worth checking the [71100.137324] config - if there is no relations between the [71100.137324] names, then host name confusion attack is possible. Apr 26 11:49:09 192.168.122.209 [71100.232225] [tempesta fw] Configuration processing is completed. Apr 26 11:49:09 192.168.122.209 [71100.296299] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:49:10 192.168.122.209 [71100.716917] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:49:10 192.168.122.209 [71100.742843] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:49:10 192.168.122.209 [71100.768590] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:49:10 192.168.122.209 [71100.808083] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:49:10 192.168.122.209 [71100.809809] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:49:10 192.168.122.209 [71100.852040] [tempesta fw] Tempesta FW is ready Apr 26 11:49:10 192.168.122.209 [71101.490710] [tdb] Close table 'client0.tdb' Apr 26 11:49:10 192.168.122.209 [71101.680250] [tdb] Close table 'sessions0.tdb' Apr 26 11:49:14 192.168.122.209 [71104.863783] [tdb] Close table 'cache0.tdb' Apr 26 11:49:14 192.168.122.209 [71105.098106] [tdb] Close table 'filter0.tdb' Apr 26 11:49:14 192.168.122.209 [71105.098505] [tempesta fw] modules are stopped Apr 26 11:49:14 192.168.122.209 [71105.271988] [tempesta fw] exiting... Apr 26 11:49:14 192.168.122.209 [71105.403702] [tdb] Shutdown Tempesta DB Apr 26 11:49:15 192.168.122.209 [71105.762640] End test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfilll_no_cache_with_arg_2 Apr 26 11:49:15 192.168.122.209 [71105.793057] Start test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfilll_no_cache_with_args Apr 26 11:49:16 192.168.122.209 [71107.165120] [tdb] Start Tempesta DB Apr 26 11:49:16 192.168.122.209 [71107.292312] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:49:17 192.168.122.209 [71108.685460] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [71108.685460] Maybe that's fine, but it's worth checking the [71108.685460] config - if there is no relations between the [71108.685460] names, then host name confusion attack is possible. Apr 26 11:49:18 192.168.122.209 [71108.788212] [tempesta fw] Configuration processing is completed. Apr 26 11:49:18 192.168.122.209 [71108.843694] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:49:18 192.168.122.209 [71109.271755] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:49:18 192.168.122.209 [71109.297577] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:49:18 192.168.122.209 [71109.324160] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:49:18 192.168.122.209 [71109.376222] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:49:18 192.168.122.209 [71109.377954] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:49:18 192.168.122.209 [71109.416141] [tempesta fw] Tempesta FW is ready Apr 26 11:49:19 192.168.122.209 [71110.042364] [tdb] Close table 'client0.tdb' Apr 26 11:49:19 192.168.122.209 [71110.230877] [tdb] Close table 'sessions0.tdb' Apr 26 11:49:22 192.168.122.209 [71113.391621] [tdb] Close table 'cache0.tdb' Apr 26 11:49:22 192.168.122.209 [71113.619050] [tdb] Close table 'filter0.tdb' Apr 26 11:49:22 192.168.122.209 [71113.619476] [tempesta fw] modules are stopped Apr 26 11:49:23 192.168.122.209 [71113.805791] [tempesta fw] exiting... Apr 26 11:49:23 192.168.122.209 [71113.912899] [tdb] Shutdown Tempesta DB Apr 26 11:49:23 192.168.122.209 [71114.270088] End test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfilll_no_cache_with_args Apr 26 11:49:23 192.168.122.209 [71114.297087] Start test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfilll_private_with_arg Apr 26 11:49:24 192.168.122.209 [71115.654609] [tdb] Start Tempesta DB Apr 26 11:49:25 192.168.122.209 [71115.781643] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:49:26 192.168.122.209 [71117.177539] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [71117.177539] Maybe that's fine, but it's worth checking the [71117.177539] config - if there is no relations between the [71117.177539] names, then host name confusion attack is possible. Apr 26 11:49:26 192.168.122.209 [71117.276325] [tempesta fw] Configuration processing is completed. Apr 26 11:49:26 192.168.122.209 [71117.337868] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:49:27 192.168.122.209 [71117.764624] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:49:27 192.168.122.209 [71117.790543] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:49:27 192.168.122.209 [71117.816888] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:49:27 192.168.122.209 [71117.872320] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:49:27 192.168.122.209 [71117.874024] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:49:27 192.168.122.209 [71117.924241] [tempesta fw] Tempesta FW is ready Apr 26 11:49:27 192.168.122.209 [71118.628000] [tdb] Close table 'client0.tdb' Apr 26 11:49:28 192.168.122.209 [71118.822357] [tdb] Close table 'sessions0.tdb' Apr 26 11:49:31 192.168.122.209 [71122.007962] [tdb] Close table 'cache0.tdb' Apr 26 11:49:31 192.168.122.209 [71122.231949] [tdb] Close table 'filter0.tdb' Apr 26 11:49:31 192.168.122.209 [71122.232402] [tempesta fw] modules are stopped Apr 26 11:49:31 192.168.122.209 [71122.436337] [tempesta fw] exiting... Apr 26 11:49:31 192.168.122.209 [71122.573946] [tdb] Shutdown Tempesta DB Apr 26 11:49:32 192.168.122.209 [71123.017665] End test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfilll_private_with_arg Apr 26 11:49:32 192.168.122.209 [71123.055911] Start test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfilll_private_with_arg_2 Apr 26 11:49:33 192.168.122.209 [71124.399733] [tdb] Start Tempesta DB Apr 26 11:49:33 192.168.122.209 [71124.528796] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:49:35 192.168.122.209 [71125.957628] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [71125.957628] Maybe that's fine, but it's worth checking the [71125.957628] config - if there is no relations between the [71125.957628] names, then host name confusion attack is possible. Apr 26 11:49:35 192.168.122.209 [71126.060426] [tempesta fw] Configuration processing is completed. Apr 26 11:49:35 192.168.122.209 [71126.114678] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:49:35 192.168.122.209 [71126.525627] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:49:35 192.168.122.209 [71126.551792] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:49:35 192.168.122.209 [71126.577786] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:49:35 192.168.122.209 [71126.640506] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:49:35 192.168.122.209 [71126.642237] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:49:35 192.168.122.209 [71126.680371] [tempesta fw] Tempesta FW is ready Apr 26 11:49:36 192.168.122.209 [71127.313597] [tdb] Close table 'client0.tdb' Apr 26 11:49:36 192.168.122.209 [71127.512155] [tdb] Close table 'sessions0.tdb' Apr 26 11:49:40 192.168.122.209 [71130.732916] [tdb] Close table 'cache0.tdb' Apr 26 11:49:40 192.168.122.209 [71130.995188] [tdb] Close table 'filter0.tdb' Apr 26 11:49:40 192.168.122.209 [71130.995628] [tempesta fw] modules are stopped Apr 26 11:49:40 192.168.122.209 [71131.201921] [tempesta fw] exiting... Apr 26 11:49:40 192.168.122.209 [71131.346975] [tdb] Shutdown Tempesta DB Apr 26 11:49:41 192.168.122.209 [71131.761036] End test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfilll_private_with_arg_2 Apr 26 11:49:41 192.168.122.209 [71131.796149] Start test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfilll_private_with_args Apr 26 11:49:42 192.168.122.209 [71133.252916] [tdb] Start Tempesta DB Apr 26 11:49:42 192.168.122.209 [71133.381264] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:49:44 192.168.122.209 [71134.777819] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [71134.777819] Maybe that's fine, but it's worth checking the [71134.777819] config - if there is no relations between the [71134.777819] names, then host name confusion attack is possible. Apr 26 11:49:44 192.168.122.209 [71134.892579] [tempesta fw] Configuration processing is completed. Apr 26 11:49:44 192.168.122.209 [71134.945308] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:49:44 192.168.122.209 [71135.368788] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:49:44 192.168.122.209 [71135.395194] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:49:44 192.168.122.209 [71135.420561] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:49:44 192.168.122.209 [71135.464550] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:49:44 192.168.122.209 [71135.466248] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:49:44 192.168.122.209 [71135.520497] [tempesta fw] Tempesta FW is ready Apr 26 11:49:45 192.168.122.209 [71136.222872] [tdb] Close table 'client0.tdb' Apr 26 11:49:45 192.168.122.209 [71136.408262] [tdb] Close table 'sessions0.tdb' Apr 26 11:49:48 192.168.122.209 [71139.567372] [tdb] Close table 'cache0.tdb' Apr 26 11:49:49 192.168.122.209 [71139.825166] [tdb] Close table 'filter0.tdb' Apr 26 11:49:49 192.168.122.209 [71139.825615] [tempesta fw] modules are stopped Apr 26 11:49:49 192.168.122.209 [71140.023505] [tempesta fw] exiting... Apr 26 11:49:49 192.168.122.209 [71140.177031] [tdb] Shutdown Tempesta DB Apr 26 11:49:49 192.168.122.209 [71140.605132] End test: cache.test_cache.TestH2CacheHdrDel.test_cache_fulfilll_private_with_args Apr 26 11:49:49 192.168.122.209 [71140.636565] Start test: cache.test_cache.TestH2CacheTtl.test_global_cache_ttl_3_sleep_0 Apr 26 11:49:51 192.168.122.209 [71142.056148] [tdb] Start Tempesta DB Apr 26 11:49:51 192.168.122.209 [71142.177143] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:49:53 192.168.122.209 [71143.809868] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [71143.809868] Maybe that's fine, but it's worth checking the [71143.809868] config - if there is no relations between the [71143.809868] names, then host name confusion attack is possible. Apr 26 11:49:53 192.168.122.209 [71143.992639] [tempesta fw] Configuration processing is completed. Apr 26 11:49:53 192.168.122.209 [71144.047399] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:49:53 192.168.122.209 [71144.510646] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:49:53 192.168.122.209 [71144.539065] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:49:53 192.168.122.209 [71144.567173] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:49:53 192.168.122.209 [71144.624659] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:49:53 192.168.122.209 [71144.626491] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:49:53 192.168.122.209 [71144.672618] [tempesta fw] Tempesta FW is ready Apr 26 11:49:54 192.168.122.209 [71145.295524] [tdb] Close table 'client0.tdb' Apr 26 11:49:54 192.168.122.209 [71145.503828] [tdb] Close table 'sessions0.tdb' Apr 26 11:49:58 192.168.122.209 [71148.725457] [tdb] Close table 'cache0.tdb' Apr 26 11:49:58 192.168.122.209 [71148.984194] [tdb] Close table 'filter0.tdb' Apr 26 11:49:58 192.168.122.209 [71148.984647] [tempesta fw] modules are stopped Apr 26 11:49:58 192.168.122.209 [71149.193463] [tempesta fw] exiting... Apr 26 11:49:58 192.168.122.209 [71149.340209] [tdb] Shutdown Tempesta DB Apr 26 11:49:59 192.168.122.209 [71149.723864] End test: cache.test_cache.TestH2CacheTtl.test_global_cache_ttl_3_sleep_0 Apr 26 11:49:59 192.168.122.209 [71149.761217] Start test: cache.test_cache.TestH2CacheTtl.test_global_cache_ttl_3_sleep_2_max_age_1 Apr 26 11:50:00 192.168.122.209 [71151.122877] [tdb] Start Tempesta DB Apr 26 11:50:00 192.168.122.209 [71151.251959] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:50:02 192.168.122.209 [71152.854101] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [71152.854101] Maybe that's fine, but it's worth checking the [71152.854101] config - if there is no relations between the [71152.854101] names, then host name confusion attack is possible. Apr 26 11:50:02 192.168.122.209 [71153.036760] [tempesta fw] Configuration processing is completed. Apr 26 11:50:02 192.168.122.209 [71153.096858] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:50:02 192.168.122.209 [71153.510652] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:50:02 192.168.122.209 [71153.536412] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:50:02 192.168.122.209 [71153.562608] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:50:02 192.168.122.209 [71153.600757] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:50:02 192.168.122.209 [71153.602487] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:50:02 192.168.122.209 [71153.640728] [tempesta fw] Tempesta FW is ready Apr 26 11:50:05 192.168.122.209 [71156.299454] [tdb] Close table 'client0.tdb' Apr 26 11:50:05 192.168.122.209 [71156.481975] [tdb] Close table 'sessions0.tdb' Apr 26 11:50:08 192.168.122.209 [71159.690599] [tdb] Close table 'cache0.tdb' Apr 26 11:50:09 192.168.122.209 [71159.936832] [tdb] Close table 'filter0.tdb' Apr 26 11:50:09 192.168.122.209 [71159.937259] [tempesta fw] modules are stopped Apr 26 11:50:09 192.168.122.209 [71160.169792] [tempesta fw] exiting... Apr 26 11:50:09 192.168.122.209 [71160.300001] [tdb] Shutdown Tempesta DB Apr 26 11:50:09 192.168.122.209 [71160.691330] End test: cache.test_cache.TestH2CacheTtl.test_global_cache_ttl_3_sleep_2_max_age_1 Apr 26 11:50:10 192.168.122.209 [71160.721151] Start test: cache.test_cache.TestH2CacheTtl.test_global_cache_ttl_3_sleep_2_s_maxage_1 Apr 26 11:50:11 192.168.122.209 [71162.079035] [tdb] Start Tempesta DB Apr 26 11:50:11 192.168.122.209 [71162.203469] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:50:13 192.168.122.209 [71163.758215] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [71163.758215] Maybe that's fine, but it's worth checking the [71163.758215] config - if there is no relations between the [71163.758215] names, then host name confusion attack is possible. Apr 26 11:50:13 192.168.122.209 [71163.945199] [tempesta fw] Configuration processing is completed. Apr 26 11:50:13 192.168.122.209 [71163.995856] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:50:13 192.168.122.209 [71164.415838] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:50:13 192.168.122.209 [71164.442182] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:50:13 192.168.122.209 [71164.467986] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:50:13 192.168.122.209 [71164.516907] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:50:13 192.168.122.209 [71164.518629] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:50:13 192.168.122.209 [71164.560867] [tempesta fw] Tempesta FW is ready Apr 26 11:50:16 192.168.122.209 [71167.255563] [tdb] Close table 'client0.tdb' Apr 26 11:50:16 192.168.122.209 [71167.438923] [tdb] Close table 'sessions0.tdb' Apr 26 11:50:19 192.168.122.209 [71170.575506] [tdb] Close table 'cache0.tdb' Apr 26 11:50:20 192.168.122.209 [71170.827190] [tdb] Close table 'filter0.tdb' Apr 26 11:50:20 192.168.122.209 [71170.827589] [tempesta fw] modules are stopped Apr 26 11:50:20 192.168.122.209 [71171.029997] [tempesta fw] exiting... Apr 26 11:50:20 192.168.122.209 [71171.190182] [tdb] Shutdown Tempesta DB Apr 26 11:50:20 192.168.122.209 [71171.609504] End test: cache.test_cache.TestH2CacheTtl.test_global_cache_ttl_3_sleep_2_s_maxage_1 Apr 26 11:50:20 192.168.122.209 [71171.647422] Start test: cache.test_cache.TestH2CacheTtl.test_global_cache_ttl_3_sleep_4 Apr 26 11:50:22 192.168.122.209 [71172.998654] [tdb] Start Tempesta DB Apr 26 11:50:22 192.168.122.209 [71173.139727] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:50:24 192.168.122.209 [71174.782296] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [71174.782296] Maybe that's fine, but it's worth checking the [71174.782296] config - if there is no relations between the [71174.782296] names, then host name confusion attack is possible. Apr 26 11:50:24 192.168.122.209 [71174.977063] [tempesta fw] Configuration processing is completed. Apr 26 11:50:24 192.168.122.209 [71175.028295] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:50:24 192.168.122.209 [71175.448514] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:50:24 192.168.122.209 [71175.478207] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:50:24 192.168.122.209 [71175.506232] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:50:24 192.168.122.209 [71175.545033] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:50:24 192.168.122.209 [71175.545986] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:50:24 192.168.122.209 [71175.597014] [tempesta fw] Tempesta FW is ready Apr 26 11:50:29 192.168.122.209 [71180.244017] [tdb] Close table 'client0.tdb' Apr 26 11:50:29 192.168.122.209 [71180.433721] [tdb] Close table 'sessions0.tdb' Apr 26 11:50:32 192.168.122.209 [71183.626999] [tdb] Close table 'cache0.tdb' Apr 26 11:50:33 192.168.122.209 [71183.878500] [tdb] Close table 'filter0.tdb' Apr 26 11:50:33 192.168.122.209 [71183.878927] [tempesta fw] modules are stopped Apr 26 11:50:33 192.168.122.209 [71184.078977] [tempesta fw] exiting... Apr 26 11:50:33 192.168.122.209 [71184.251492] [tdb] Shutdown Tempesta DB Apr 26 11:50:33 192.168.122.209 [71184.670916] End test: cache.test_cache.TestH2CacheTtl.test_global_cache_ttl_3_sleep_4 Apr 26 11:50:33 192.168.122.209 [71184.696700] Start test: cache.test_cache.TestH2CacheTtl.test_global_cache_ttl_3_sleep_4_max_age_10 Apr 26 11:50:35 192.168.122.209 [71186.120425] [tdb] Start Tempesta DB Apr 26 11:50:35 192.168.122.209 [71186.257022] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:50:37 192.168.122.209 [71187.874421] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [71187.874421] Maybe that's fine, but it's worth checking the [71187.874421] config - if there is no relations between the [71187.874421] names, then host name confusion attack is possible. Apr 26 11:50:37 192.168.122.209 [71188.065175] [tempesta fw] Configuration processing is completed. Apr 26 11:50:37 192.168.122.209 [71188.121638] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:50:37 192.168.122.209 [71188.555493] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:50:37 192.168.122.209 [71188.582715] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:50:37 192.168.122.209 [71188.608798] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:50:37 192.168.122.209 [71188.653200] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:50:37 192.168.122.209 [71188.654909] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:50:38 192.168.122.209 [71188.701176] [tempesta fw] Tempesta FW is ready Apr 26 11:50:42 192.168.122.209 [71193.354417] [tdb] Close table 'client0.tdb' Apr 26 11:50:42 192.168.122.209 [71193.539706] [tdb] Close table 'sessions0.tdb' Apr 26 11:50:46 192.168.122.209 [71197.141836] [tdb] Close table 'cache0.tdb' Apr 26 11:50:46 192.168.122.209 [71197.635240] [tdb] Close table 'filter0.tdb' Apr 26 11:50:46 192.168.122.209 [71197.635694] [tempesta fw] modules are stopped Apr 26 11:50:48 192.168.122.209 [71198.917590] [tempesta fw] exiting... Apr 26 11:50:48 192.168.122.209 [71199.566474] [tdb] Shutdown Tempesta DB Apr 26 11:50:49 192.168.122.209 [71200.377290] End test: cache.test_cache.TestH2CacheTtl.test_global_cache_ttl_3_sleep_4_max_age_10 Apr 26 11:50:49 192.168.122.209 [71200.418420] Start test: cache.test_cache.TestH2CacheTtl.test_priority_for_cache_control_header_no_cache Apr 26 11:50:51 192.168.122.209 [71201.991904] [tdb] Start Tempesta DB Apr 26 11:50:51 192.168.122.209 [71202.154236] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:50:53 192.168.122.209 [71203.750654] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [71203.750654] Maybe that's fine, but it's worth checking the [71203.750654] config - if there is no relations between the [71203.750654] names, then host name confusion attack is possible. Apr 26 11:50:53 192.168.122.209 [71203.937419] [tempesta fw] Configuration processing is completed. Apr 26 11:50:53 192.168.122.209 [71203.999240] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:50:53 192.168.122.209 [71204.407034] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:50:53 192.168.122.209 [71204.434231] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:50:53 192.168.122.209 [71204.461614] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:50:53 192.168.122.209 [71204.501408] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:50:53 192.168.122.209 [71204.503132] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:50:53 192.168.122.209 [71204.553382] [tempesta fw] Tempesta FW is ready Apr 26 11:50:54 192.168.122.209 [71205.168914] [tdb] Close table 'client0.tdb' Apr 26 11:50:54 192.168.122.209 [71205.362978] [tdb] Close table 'sessions0.tdb' Apr 26 11:50:57 192.168.122.209 [71208.497656] [tdb] Close table 'cache0.tdb' Apr 26 11:50:58 192.168.122.209 [71208.758607] [tdb] Close table 'filter0.tdb' Apr 26 11:50:58 192.168.122.209 [71208.759034] [tempesta fw] modules are stopped Apr 26 11:50:58 192.168.122.209 [71208.981646] [tempesta fw] exiting... Apr 26 11:50:58 192.168.122.209 [71209.128343] [tdb] Shutdown Tempesta DB Apr 26 11:50:58 192.168.122.209 [71209.507775] End test: cache.test_cache.TestH2CacheTtl.test_priority_for_cache_control_header_no_cache Apr 26 11:50:58 192.168.122.209 [71209.536391] Start test: cache.test_cache.TestH2CacheTtl.test_priority_for_cache_control_header_no_store Apr 26 11:51:00 192.168.122.209 [71210.877533] [tdb] Start Tempesta DB Apr 26 11:51:00 192.168.122.209 [71210.996374] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:51:01 192.168.122.209 [71212.638779] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [71212.638779] Maybe that's fine, but it's worth checking the [71212.638779] config - if there is no relations between the [71212.638779] names, then host name confusion attack is possible. Apr 26 11:51:02 192.168.122.209 [71212.821539] [tempesta fw] Configuration processing is completed. Apr 26 11:51:02 192.168.122.209 [71212.879208] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:51:02 192.168.122.209 [71213.292708] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:51:02 192.168.122.209 [71213.319047] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:51:02 192.168.122.209 [71213.346389] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:51:02 192.168.122.209 [71213.385525] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:51:02 192.168.122.209 [71213.387244] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:51:02 192.168.122.209 [71213.429469] [tempesta fw] Tempesta FW is ready Apr 26 11:51:03 192.168.122.209 [71214.086661] [tdb] Close table 'client0.tdb' Apr 26 11:51:03 192.168.122.209 [71214.282148] [tdb] Close table 'sessions0.tdb' Apr 26 11:51:06 192.168.122.209 [71217.458771] [tdb] Close table 'cache0.tdb' Apr 26 11:51:07 192.168.122.209 [71217.709464] [tdb] Close table 'filter0.tdb' Apr 26 11:51:07 192.168.122.209 [71217.709964] [tempesta fw] modules are stopped Apr 26 11:51:07 192.168.122.209 [71217.946719] [tempesta fw] exiting... Apr 26 11:51:07 192.168.122.209 [71218.087026] [tdb] Shutdown Tempesta DB Apr 26 11:51:07 192.168.122.209 [71218.448918] End test: cache.test_cache.TestH2CacheTtl.test_priority_for_cache_control_header_no_store Apr 26 11:51:07 192.168.122.209 [71218.482375] Start test: cache.test_cache.TestH2CacheTtl.test_priority_for_cache_control_header_private Apr 26 11:51:09 192.168.122.209 [71219.912705] [tdb] Start Tempesta DB Apr 26 11:51:09 192.168.122.209 [71220.063672] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:51:11 192.168.122.209 [71221.774974] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [71221.774974] Maybe that's fine, but it's worth checking the [71221.774974] config - if there is no relations between the [71221.774974] names, then host name confusion attack is possible. Apr 26 11:51:11 192.168.122.209 [71221.965664] [tempesta fw] Configuration processing is completed. Apr 26 11:51:11 192.168.122.209 [71222.022120] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:51:11 192.168.122.209 [71222.487828] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:51:11 192.168.122.209 [71222.517805] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:51:11 192.168.122.209 [71222.546672] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:51:11 192.168.122.209 [71222.613711] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:51:11 192.168.122.209 [71222.615436] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:51:11 192.168.122.209 [71222.661628] [tempesta fw] Tempesta FW is ready Apr 26 11:51:12 192.168.122.209 [71223.297897] [tdb] Close table 'client0.tdb' Apr 26 11:51:12 192.168.122.209 [71223.536357] [tdb] Close table 'sessions0.tdb' Apr 26 11:51:16 192.168.122.209 [71226.861295] [tdb] Close table 'cache0.tdb' Apr 26 11:51:16 192.168.122.209 [71227.114930] [tdb] Close table 'filter0.tdb' Apr 26 11:51:16 192.168.122.209 [71227.115374] [tempesta fw] modules are stopped Apr 26 11:51:16 192.168.122.209 [71227.322294] [tempesta fw] exiting... Apr 26 11:51:16 192.168.122.209 [71227.440655] [tdb] Shutdown Tempesta DB Apr 26 11:51:17 192.168.122.209 [71227.853028] End test: cache.test_cache.TestH2CacheTtl.test_priority_for_cache_control_header_private Apr 26 11:51:17 192.168.122.209 [71227.881975] Start test: cache.test_cache.TestH2CacheTtl.test_vhost_cache_ttl_1_sleep_2 Apr 26 11:51:18 192.168.122.209 [71229.303411] [tdb] Start Tempesta DB Apr 26 11:51:18 192.168.122.209 [71229.451427] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:51:20 192.168.122.209 [71231.135069] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [71231.135069] Maybe that's fine, but it's worth checking the [71231.135069] config - if there is no relations between the [71231.135069] names, then host name confusion attack is possible. Apr 26 11:51:20 192.168.122.209 [71231.329780] [tempesta fw] Configuration processing is completed. Apr 26 11:51:20 192.168.122.209 [71231.394182] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:51:21 192.168.122.209 [71231.876075] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:51:21 192.168.122.209 [71231.905630] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:51:21 192.168.122.209 [71231.935125] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:51:21 192.168.122.209 [71231.997777] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:51:21 192.168.122.209 [71231.999495] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:51:21 192.168.122.209 [71232.037730] [tempesta fw] Tempesta FW is ready Apr 26 11:51:23 192.168.122.209 [71234.626922] [tdb] Close table 'client0.tdb' Apr 26 11:51:24 192.168.122.209 [71234.822216] [tdb] Close table 'sessions0.tdb' Apr 26 11:51:27 192.168.122.209 [71238.010159] [tdb] Close table 'cache0.tdb' Apr 26 11:51:27 192.168.122.209 [71238.257957] [tdb] Close table 'filter0.tdb' Apr 26 11:51:27 192.168.122.209 [71238.258399] [tempesta fw] modules are stopped Apr 26 11:51:27 192.168.122.209 [71238.497796] [tempesta fw] exiting... Apr 26 11:51:27 192.168.122.209 [71238.616999] [tdb] Shutdown Tempesta DB Apr 26 11:51:28 192.168.122.209 [71238.995445] End test: cache.test_cache.TestH2CacheTtl.test_vhost_cache_ttl_1_sleep_2 Apr 26 11:51:28 192.168.122.209 [71239.021057] Start test: cache.test_cache.TestH2CacheTtl.test_vhost_cache_ttl_1_sleep_4 Apr 26 11:51:29 192.168.122.209 [71240.345202] [tdb] Start Tempesta DB Apr 26 11:51:29 192.168.122.209 [71240.487129] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:51:31 192.168.122.209 [71242.131177] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [71242.131177] Maybe that's fine, but it's worth checking the [71242.131177] config - if there is no relations between the [71242.131177] names, then host name confusion attack is possible. Apr 26 11:51:31 192.168.122.209 [71242.337903] [tempesta fw] Configuration processing is completed. Apr 26 11:51:31 192.168.122.209 [71242.403492] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:51:32 192.168.122.209 [71242.842301] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:51:32 192.168.122.209 [71242.870356] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:51:32 192.168.122.209 [71242.898077] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:51:32 192.168.122.209 [71242.941908] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:51:32 192.168.122.209 [71242.943421] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:51:32 192.168.122.209 [71242.997871] [tempesta fw] Tempesta FW is ready Apr 26 11:51:36 192.168.122.209 [71247.671190] [tdb] Close table 'client0.tdb' Apr 26 11:51:37 192.168.122.209 [71247.855735] [tdb] Close table 'sessions0.tdb' Apr 26 11:51:40 192.168.122.209 [71251.104887] [tdb] Close table 'cache0.tdb' Apr 26 11:51:40 192.168.122.209 [71251.341305] [tdb] Close table 'filter0.tdb' Apr 26 11:51:40 192.168.122.209 [71251.341727] [tempesta fw] modules are stopped Apr 26 11:51:40 192.168.122.209 [71251.552866] [tempesta fw] exiting... Apr 26 11:51:40 192.168.122.209 [71251.697189] [tdb] Shutdown Tempesta DB Apr 26 11:51:41 192.168.122.209 [71252.053279] End test: cache.test_cache.TestH2CacheTtl.test_vhost_cache_ttl_1_sleep_4 Apr 26 11:51:41 192.168.122.209 [71252.088834] Start test: cache.test_cache.TestQueryparamsAndRedirectH2.test_query_param_different_key Apr 26 11:51:42 192.168.122.209 [71253.494746] [tdb] Start Tempesta DB Apr 26 11:51:42 192.168.122.209 [71253.631479] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:51:44 192.168.122.209 [71255.027475] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [71255.027475] Maybe that's fine, but it's worth checking the [71255.027475] config - if there is no relations between the [71255.027475] names, then host name confusion attack is possible. Apr 26 11:51:44 192.168.122.209 [71255.110090] [tempesta fw] Configuration processing is completed. Apr 26 11:51:44 192.168.122.209 [71255.168008] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:51:44 192.168.122.209 [71255.659017] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:51:45 192.168.122.209 [71255.703051] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:51:45 192.168.122.209 [71255.736116] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:51:45 192.168.122.209 [71255.774062] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:51:45 192.168.122.209 [71255.775789] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:51:45 192.168.122.209 [71255.814012] [tempesta fw] Tempesta FW is ready Apr 26 11:51:45 192.168.122.209 [71256.551985] [tdb] Close table 'client0.tdb' Apr 26 11:51:46 192.168.122.209 [71256.744122] [tdb] Close table 'sessions0.tdb' Apr 26 11:51:49 192.168.122.209 [71260.170612] [tdb] Close table 'cache0.tdb' Apr 26 11:51:49 192.168.122.209 [71260.400141] [tdb] Close table 'filter0.tdb' Apr 26 11:51:49 192.168.122.209 [71260.400576] [tempesta fw] modules are stopped Apr 26 11:51:49 192.168.122.209 [71260.598366] [tempesta fw] exiting... Apr 26 11:51:50 192.168.122.209 [71260.739289] [tdb] Shutdown Tempesta DB Apr 26 11:51:50 192.168.122.209 [71261.180220] End test: cache.test_cache.TestQueryparamsAndRedirectH2.test_query_param_different_key Apr 26 11:51:50 192.168.122.209 [71261.212918] Start test: cache.test_cache.TestQueryparamsAndRedirectH2.test_query_param_different_value Apr 26 11:51:51 192.168.122.209 [71262.627011] [tdb] Start Tempesta DB Apr 26 11:51:52 192.168.122.209 [71262.764579] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:51:53 192.168.122.209 [71264.223619] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [71264.223619] Maybe that's fine, but it's worth checking the [71264.223619] config - if there is no relations between the [71264.223619] names, then host name confusion attack is possible. Apr 26 11:51:53 192.168.122.209 [71264.306228] [tempesta fw] Configuration processing is completed. Apr 26 11:51:53 192.168.122.209 [71264.368416] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:51:54 192.168.122.209 [71264.823589] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:51:54 192.168.122.209 [71264.851245] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:51:54 192.168.122.209 [71264.879942] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:51:54 192.168.122.209 [71264.918213] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:51:54 192.168.122.209 [71264.919969] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:51:54 192.168.122.209 [71264.958123] [tempesta fw] Tempesta FW is ready Apr 26 11:51:54 192.168.122.209 [71265.645374] [tdb] Close table 'client0.tdb' Apr 26 11:51:55 192.168.122.209 [71265.837421] [tdb] Close table 'sessions0.tdb' Apr 26 11:51:58 192.168.122.209 [71269.057749] [tdb] Close table 'cache0.tdb' Apr 26 11:51:58 192.168.122.209 [71269.303940] [tdb] Close table 'filter0.tdb' Apr 26 11:51:58 192.168.122.209 [71269.304374] [tempesta fw] modules are stopped Apr 26 11:51:58 192.168.122.209 [71269.488688] [tempesta fw] exiting... Apr 26 11:51:58 192.168.122.209 [71269.624369] [tdb] Shutdown Tempesta DB Apr 26 11:51:59 192.168.122.209 [71270.044018] End test: cache.test_cache.TestQueryparamsAndRedirectH2.test_query_param_different_value Apr 26 11:51:59 192.168.122.209 [71270.067796] Start test: cache.test_cache.TestQueryparamsAndRedirectH2.test_query_param_same_params Apr 26 11:52:00 192.168.122.209 [71271.575714] [tdb] Start Tempesta DB Apr 26 11:52:01 192.168.122.209 [71271.718624] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:52:02 192.168.122.209 [71273.199632] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [71273.199632] Maybe that's fine, but it's worth checking the [71273.199632] config - if there is no relations between the [71273.199632] names, then host name confusion attack is possible. Apr 26 11:52:02 192.168.122.209 [71273.290367] [tempesta fw] Configuration processing is completed. Apr 26 11:52:02 192.168.122.209 [71273.348362] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:52:03 192.168.122.209 [71273.796449] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:52:03 192.168.122.209 [71273.823333] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:52:03 192.168.122.209 [71273.849718] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:52:03 192.168.122.209 [71273.894287] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:52:03 192.168.122.209 [71273.896418] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:52:03 192.168.122.209 [71273.934263] [tempesta fw] Tempesta FW is ready Apr 26 11:52:03 192.168.122.209 [71274.658747] [tdb] Close table 'client0.tdb' Apr 26 11:52:04 192.168.122.209 [71274.845913] [tdb] Close table 'sessions0.tdb' Apr 26 11:52:07 192.168.122.209 [71278.003824] [tdb] Close table 'cache0.tdb' Apr 26 11:52:07 192.168.122.209 [71278.279935] [tdb] Close table 'filter0.tdb' Apr 26 11:52:07 192.168.122.209 [71278.280337] [tempesta fw] modules are stopped Apr 26 11:52:07 192.168.122.209 [71278.474480] [tempesta fw] exiting... Apr 26 11:52:07 192.168.122.209 [71278.626665] [tdb] Shutdown Tempesta DB Apr 26 11:52:08 192.168.122.209 [71279.051794] End test: cache.test_cache.TestQueryparamsAndRedirectH2.test_query_param_same_params Apr 26 11:52:08 192.168.122.209 [71279.076292] Start test: cache.test_cache.TestQueryparamsAndRedirectH2.test_query_param_with_new_param Apr 26 11:52:09 192.168.122.209 [71280.480200] [tdb] Start Tempesta DB Apr 26 11:52:09 192.168.122.209 [71280.610356] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:52:11 192.168.122.209 [71282.095667] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [71282.095667] Maybe that's fine, but it's worth checking the [71282.095667] config - if there is no relations between the [71282.095667] names, then host name confusion attack is possible. Apr 26 11:52:11 192.168.122.209 [71282.182456] [tempesta fw] Configuration processing is completed. Apr 26 11:52:11 192.168.122.209 [71282.238175] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:52:11 192.168.122.209 [71282.669391] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:52:11 192.168.122.209 [71282.695357] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:52:12 192.168.122.209 [71282.720972] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:52:12 192.168.122.209 [71282.770396] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:52:12 192.168.122.209 [71282.772120] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:52:12 192.168.122.209 [71282.810383] [tempesta fw] Tempesta FW is ready Apr 26 11:52:12 192.168.122.209 [71283.576520] [tdb] Close table 'client0.tdb' Apr 26 11:52:13 192.168.122.209 [71283.767140] [tdb] Close table 'sessions0.tdb' Apr 26 11:52:16 192.168.122.209 [71286.960085] [tdb] Close table 'cache0.tdb' Apr 26 11:52:16 192.168.122.209 [71287.224061] [tdb] Close table 'filter0.tdb' Apr 26 11:52:16 192.168.122.209 [71287.224468] [tempesta fw] modules are stopped Apr 26 11:52:16 192.168.122.209 [71287.438200] [tempesta fw] exiting... Apr 26 11:52:16 192.168.122.209 [71287.579558] [tdb] Shutdown Tempesta DB Apr 26 11:52:17 192.168.122.209 [71287.969981] End test: cache.test_cache.TestQueryparamsAndRedirectH2.test_query_param_with_new_param Apr 26 11:52:17 192.168.122.209 [71288.041082] Start test: cache.test_cache.TestQueryparamsAndRedirectH2.test_redirect_300_multiple_choices Apr 26 11:52:18 192.168.122.209 [71289.376969] [tdb] Start Tempesta DB Apr 26 11:52:18 192.168.122.209 [71289.518331] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:52:20 192.168.122.209 [71290.933402] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [71290.933402] Maybe that's fine, but it's worth checking the [71290.933402] config - if there is no relations between the [71290.933402] names, then host name confusion attack is possible. Apr 26 11:52:20 192.168.122.209 [71291.010949] [tempesta fw] Configuration processing is completed. Apr 26 11:52:20 192.168.122.209 [71291.066052] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:52:20 192.168.122.209 [71291.479918] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:52:20 192.168.122.209 [71291.505233] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:52:20 192.168.122.209 [71291.530761] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:52:20 192.168.122.209 [71291.574516] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:52:20 192.168.122.209 [71291.576235] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:52:20 192.168.122.209 [71291.622466] [tempesta fw] Tempesta FW is ready Apr 26 11:52:21 192.168.122.209 [71292.285491] [tdb] Close table 'client0.tdb' Apr 26 11:52:21 192.168.122.209 [71292.468240] [tdb] Close table 'sessions0.tdb' Apr 26 11:52:24 192.168.122.209 [71295.606098] [tdb] Close table 'cache0.tdb' Apr 26 11:52:25 192.168.122.209 [71295.839129] [tdb] Close table 'filter0.tdb' Apr 26 11:52:25 192.168.122.209 [71295.839556] [tempesta fw] modules are stopped Apr 26 11:52:25 192.168.122.209 [71296.055978] [tempesta fw] exiting... Apr 26 11:52:25 192.168.122.209 [71296.197557] [tdb] Shutdown Tempesta DB Apr 26 11:52:25 192.168.122.209 [71296.615325] End test: cache.test_cache.TestQueryparamsAndRedirectH2.test_redirect_300_multiple_choices Apr 26 11:52:25 192.168.122.209 [71296.644394] Start test: cache.test_cache.TestQueryparamsAndRedirectH2.test_redirect_301_moved_permanently Apr 26 11:52:27 192.168.122.209 [71298.106169] [tdb] Start Tempesta DB Apr 26 11:52:27 192.168.122.209 [71298.236732] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:52:28 192.168.122.209 [71299.635926] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [71299.635926] Maybe that's fine, but it's worth checking the [71299.635926] config - if there is no relations between the [71299.635926] names, then host name confusion attack is possible. Apr 26 11:52:29 192.168.122.209 [71299.726659] [tempesta fw] Configuration processing is completed. Apr 26 11:52:29 192.168.122.209 [71299.782875] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:52:29 192.168.122.209 [71300.197887] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:52:29 192.168.122.209 [71300.223908] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:52:29 192.168.122.209 [71300.254203] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:52:29 192.168.122.209 [71300.314648] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:52:29 192.168.122.209 [71300.316383] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:52:29 192.168.122.209 [71300.354591] [tempesta fw] Tempesta FW is ready Apr 26 11:52:30 192.168.122.209 [71301.067599] [tdb] Close table 'client0.tdb' Apr 26 11:52:30 192.168.122.209 [71301.247170] [tdb] Close table 'sessions0.tdb' Apr 26 11:52:33 192.168.122.209 [71304.351315] [tdb] Close table 'cache0.tdb' Apr 26 11:52:33 192.168.122.209 [71304.605841] [tdb] Close table 'filter0.tdb' Apr 26 11:52:33 192.168.122.209 [71304.606240] [tempesta fw] modules are stopped Apr 26 11:52:34 192.168.122.209 [71304.784332] [tempesta fw] exiting... Apr 26 11:52:34 192.168.122.209 [71304.921628] [tdb] Shutdown Tempesta DB Apr 26 11:52:34 192.168.122.209 [71305.356785] End test: cache.test_cache.TestQueryparamsAndRedirectH2.test_redirect_301_moved_permanently Apr 26 11:52:34 192.168.122.209 [71305.388944] Start test: cache.test_cache.TestQueryparamsAndRedirectH2.test_redirect_302_found Apr 26 11:52:36 192.168.122.209 [71306.775360] [tdb] Start Tempesta DB Apr 26 11:52:36 192.168.122.209 [71306.917386] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:52:37 192.168.122.209 [71308.359735] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [71308.359735] Maybe that's fine, but it's worth checking the [71308.359735] config - if there is no relations between the [71308.359735] names, then host name confusion attack is possible. Apr 26 11:52:37 192.168.122.209 [71308.447055] [tempesta fw] Configuration processing is completed. Apr 26 11:52:37 192.168.122.209 [71308.497464] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:52:38 192.168.122.209 [71308.926375] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:52:38 192.168.122.209 [71308.953113] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:52:38 192.168.122.209 [71308.979121] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:52:38 192.168.122.209 [71309.018741] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:52:38 192.168.122.209 [71309.020440] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:52:38 192.168.122.209 [71309.058697] [tempesta fw] Tempesta FW is ready Apr 26 11:52:39 192.168.122.209 [71309.755112] [tdb] Close table 'client0.tdb' Apr 26 11:52:39 192.168.122.209 [71309.955074] [tdb] Close table 'sessions0.tdb' Apr 26 11:52:42 192.168.122.209 [71313.090096] [tdb] Close table 'cache0.tdb' Apr 26 11:52:42 192.168.122.209 [71313.306885] [tdb] Close table 'filter0.tdb' Apr 26 11:52:42 192.168.122.209 [71313.307295] [tempesta fw] modules are stopped Apr 26 11:52:42 192.168.122.209 [71313.508098] [tempesta fw] exiting... Apr 26 11:52:42 192.168.122.209 [71313.631936] [tdb] Shutdown Tempesta DB Apr 26 11:52:43 192.168.122.209 [71314.042022] End test: cache.test_cache.TestQueryparamsAndRedirectH2.test_redirect_302_found Apr 26 11:52:43 192.168.122.209 [71314.081904] Start test: cache.test_cache.TestQueryparamsAndRedirectH2.test_redirect_303_see_other Apr 26 11:52:44 192.168.122.209 [71315.453062] [tdb] Start Tempesta DB Apr 26 11:52:44 192.168.122.209 [71315.594750] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:52:46 192.168.122.209 [71316.984091] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [71316.984091] Maybe that's fine, but it's worth checking the [71316.984091] config - if there is no relations between the [71316.984091] names, then host name confusion attack is possible. Apr 26 11:52:46 192.168.122.209 [71317.070883] [tempesta fw] Configuration processing is completed. Apr 26 11:52:46 192.168.122.209 [71317.121663] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:52:46 192.168.122.209 [71317.531039] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:52:46 192.168.122.209 [71317.557229] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:52:46 192.168.122.209 [71317.582697] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:52:46 192.168.122.209 [71317.646847] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:52:46 192.168.122.209 [71317.648565] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:52:46 192.168.122.209 [71317.694791] [tempesta fw] Tempesta FW is ready Apr 26 11:52:47 192.168.122.209 [71318.402439] [tdb] Close table 'client0.tdb' Apr 26 11:52:47 192.168.122.209 [71318.597430] [tdb] Close table 'sessions0.tdb' Apr 26 11:52:51 192.168.122.209 [71321.708345] [tdb] Close table 'cache0.tdb' Apr 26 11:52:51 192.168.122.209 [71321.973199] [tdb] Close table 'filter0.tdb' Apr 26 11:52:51 192.168.122.209 [71321.973644] [tempesta fw] modules are stopped Apr 26 11:52:51 192.168.122.209 [71322.163536] [tempesta fw] exiting... Apr 26 11:52:51 192.168.122.209 [71322.333293] [tdb] Shutdown Tempesta DB Apr 26 11:52:52 192.168.122.209 [71322.774552] End test: cache.test_cache.TestQueryparamsAndRedirectH2.test_redirect_303_see_other Apr 26 11:52:52 192.168.122.209 [71322.801330] Start test: cache.test_cache.TestQueryparamsAndRedirectH2.test_redirect_304_not_modified Apr 26 11:52:53 192.168.122.209 [71324.143934] [tdb] Start Tempesta DB Apr 26 11:52:53 192.168.122.209 [71324.273691] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:52:54 192.168.122.209 [71325.676217] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [71325.676217] Maybe that's fine, but it's worth checking the [71325.676217] config - if there is no relations between the [71325.676217] names, then host name confusion attack is possible. Apr 26 11:52:55 192.168.122.209 [71325.778965] [tempesta fw] Configuration processing is completed. Apr 26 11:52:55 192.168.122.209 [71325.830456] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:52:55 192.168.122.209 [71326.242841] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:52:55 192.168.122.209 [71326.270122] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:52:55 192.168.122.209 [71326.296919] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:52:55 192.168.122.209 [71326.367041] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:52:55 192.168.122.209 [71326.368769] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:52:55 192.168.122.209 [71326.406913] [tempesta fw] Tempesta FW is ready Apr 26 11:52:56 192.168.122.209 [71327.104281] [tdb] Close table 'client0.tdb' Apr 26 11:52:56 192.168.122.209 [71327.287759] [tdb] Close table 'sessions0.tdb' Apr 26 11:52:59 192.168.122.209 [71330.423148] [tdb] Close table 'cache0.tdb' Apr 26 11:52:59 192.168.122.209 [71330.679131] [tdb] Close table 'filter0.tdb' Apr 26 11:52:59 192.168.122.209 [71330.679550] [tempesta fw] modules are stopped Apr 26 11:53:00 192.168.122.209 [71330.856086] [tempesta fw] exiting... Apr 26 11:53:00 192.168.122.209 [71330.980448] [tdb] Shutdown Tempesta DB Apr 26 11:53:00 192.168.122.209 [71331.413471] End test: cache.test_cache.TestQueryparamsAndRedirectH2.test_redirect_304_not_modified Apr 26 11:53:00 192.168.122.209 [71331.498349] Start test: cache.test_cache.TestQueryparamsAndRedirectH2.test_redirect_305_user_proxy Apr 26 11:53:02 192.168.122.209 [71332.868074] [tdb] Start Tempesta DB Apr 26 11:53:02 192.168.122.209 [71332.993014] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:53:03 192.168.122.209 [71334.380324] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [71334.380324] Maybe that's fine, but it's worth checking the [71334.380324] config - if there is no relations between the [71334.380324] names, then host name confusion attack is possible. Apr 26 11:53:03 192.168.122.209 [71334.471063] [tempesta fw] Configuration processing is completed. Apr 26 11:53:03 192.168.122.209 [71334.527949] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:53:04 192.168.122.209 [71334.940888] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:53:04 192.168.122.209 [71334.966384] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:53:04 192.168.122.209 [71334.993519] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:53:04 192.168.122.209 [71335.043074] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:53:04 192.168.122.209 [71335.044811] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:53:04 192.168.122.209 [71335.095054] [tempesta fw] Tempesta FW is ready Apr 26 11:53:05 192.168.122.209 [71335.795427] [tdb] Close table 'client0.tdb' Apr 26 11:53:05 192.168.122.209 [71335.992922] [tdb] Close table 'sessions0.tdb' Apr 26 11:53:08 192.168.122.209 [71339.104381] [tdb] Close table 'cache0.tdb' Apr 26 11:53:08 192.168.122.209 [71339.354774] [tdb] Close table 'filter0.tdb' Apr 26 11:53:08 192.168.122.209 [71339.355235] [tempesta fw] modules are stopped Apr 26 11:53:08 192.168.122.209 [71339.573845] [tempesta fw] exiting... Apr 26 11:53:08 192.168.122.209 [71339.677677] [tdb] Shutdown Tempesta DB Apr 26 11:53:09 192.168.122.209 [71340.094448] End test: cache.test_cache.TestQueryparamsAndRedirectH2.test_redirect_305_user_proxy Apr 26 11:53:09 192.168.122.209 [71340.173672] Start test: cache.test_cache.TestQueryparamsAndRedirectH2.test_redirect_307_temporary_redirect Apr 26 11:53:10 192.168.122.209 [71341.585909] [tdb] Start Tempesta DB Apr 26 11:53:11 192.168.122.209 [71341.711863] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:53:12 192.168.122.209 [71343.156460] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [71343.156460] Maybe that's fine, but it's worth checking the [71343.156460] config - if there is no relations between the [71343.156460] names, then host name confusion attack is possible. Apr 26 11:53:12 192.168.122.209 [71343.239161] [tempesta fw] Configuration processing is completed. Apr 26 11:53:12 192.168.122.209 [71343.291539] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:53:13 192.168.122.209 [71343.711364] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:53:13 192.168.122.209 [71343.737929] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:53:13 192.168.122.209 [71343.763381] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:53:13 192.168.122.209 [71343.819180] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:53:13 192.168.122.209 [71343.820897] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:53:13 192.168.122.209 [71343.859140] [tempesta fw] Tempesta FW is ready Apr 26 11:53:13 192.168.122.209 [71344.583275] [tdb] Close table 'client0.tdb' Apr 26 11:53:14 192.168.122.209 [71344.773990] [tdb] Close table 'sessions0.tdb' Apr 26 11:53:17 192.168.122.209 [71347.942695] [tdb] Close table 'cache0.tdb' Apr 26 11:53:17 192.168.122.209 [71348.217976] [tdb] Close table 'filter0.tdb' Apr 26 11:53:17 192.168.122.209 [71348.218381] [tempesta fw] modules are stopped Apr 26 11:53:17 192.168.122.209 [71348.410482] [tempesta fw] exiting... Apr 26 11:53:17 192.168.122.209 [71348.559574] [tdb] Shutdown Tempesta DB Apr 26 11:53:18 192.168.122.209 [71349.000739] End test: cache.test_cache.TestQueryparamsAndRedirectH2.test_redirect_307_temporary_redirect Apr 26 11:53:18 192.168.122.209 [71349.036136] Start test: cache.test_cache.TestQueryparamsAndRedirectH2.test_redirect_308_permanent_redirect Apr 26 11:53:19 192.168.122.209 [71350.416964] [tdb] Start Tempesta DB Apr 26 11:53:19 192.168.122.209 [71350.545262] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:53:21 192.168.122.209 [71352.044608] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [71352.044608] Maybe that's fine, but it's worth checking the [71352.044608] config - if there is no relations between the [71352.044608] names, then host name confusion attack is possible. Apr 26 11:53:21 192.168.122.209 [71352.127337] [tempesta fw] Configuration processing is completed. Apr 26 11:53:21 192.168.122.209 [71352.183903] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:53:21 192.168.122.209 [71352.599843] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:53:21 192.168.122.209 [71352.624794] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:53:21 192.168.122.209 [71352.661575] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:53:22 192.168.122.209 [71352.707312] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:53:22 192.168.122.209 [71352.709040] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:53:22 192.168.122.209 [71352.751256] [tempesta fw] Tempesta FW is ready Apr 26 11:53:22 192.168.122.209 [71353.443459] [tdb] Close table 'client0.tdb' Apr 26 11:53:22 192.168.122.209 [71353.628805] [tdb] Close table 'sessions0.tdb' Apr 26 11:53:26 192.168.122.209 [71356.776120] [tdb] Close table 'cache0.tdb' Apr 26 11:53:26 192.168.122.209 [71357.017645] [tdb] Close table 'filter0.tdb' Apr 26 11:53:26 192.168.122.209 [71357.018047] [tempesta fw] modules are stopped Apr 26 11:53:26 192.168.122.209 [71357.203341] [tempesta fw] exiting... Apr 26 11:53:26 192.168.122.209 [71357.315070] [tdb] Shutdown Tempesta DB Apr 26 11:53:27 192.168.122.209 [71357.734123] End test: cache.test_cache.TestQueryparamsAndRedirectH2.test_redirect_308_permanent_redirect Apr 26 11:53:27 192.168.122.209 [71357.777249] Start test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_query_param_different_key Apr 26 11:53:28 192.168.122.209 [71359.200681] [tdb] Start Tempesta DB Apr 26 11:53:28 192.168.122.209 [71359.328042] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:53:30 192.168.122.209 [71360.880712] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [71360.880712] Maybe that's fine, but it's worth checking the [71360.880712] config - if there is no relations between the [71360.880712] names, then host name confusion attack is possible. Apr 26 11:53:30 192.168.122.209 [71360.983408] [tempesta fw] Configuration processing is completed. Apr 26 11:53:30 192.168.122.209 [71361.039937] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:53:30 192.168.122.209 [71361.462304] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:53:30 192.168.122.209 [71361.488565] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:53:30 192.168.122.209 [71361.513851] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:53:30 192.168.122.209 [71361.571425] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:53:30 192.168.122.209 [71361.573158] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:53:30 192.168.122.209 [71361.611360] [tempesta fw] Tempesta FW is ready Apr 26 11:53:31 192.168.122.209 [71362.311175] [tdb] Close table 'client0.tdb' Apr 26 11:53:31 192.168.122.209 [71362.486980] [tdb] Close table 'sessions0.tdb' Apr 26 11:53:34 192.168.122.209 [71365.615588] [tdb] Close table 'cache0.tdb' Apr 26 11:53:35 192.168.122.209 [71365.834109] [tdb] Close table 'filter0.tdb' Apr 26 11:53:35 192.168.122.209 [71365.834537] [tempesta fw] modules are stopped Apr 26 11:53:35 192.168.122.209 [71366.047349] [tempesta fw] exiting... Apr 26 11:53:35 192.168.122.209 [71366.191506] [tdb] Shutdown Tempesta DB Apr 26 11:53:35 192.168.122.209 [71366.614195] End test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_query_param_different_key Apr 26 11:53:35 192.168.122.209 [71366.641144] Start test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_query_param_different_value Apr 26 11:53:37 192.168.122.209 [71368.020758] [tdb] Start Tempesta DB Apr 26 11:53:37 192.168.122.209 [71368.156768] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:53:38 192.168.122.209 [71369.584797] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [71369.584797] Maybe that's fine, but it's worth checking the [71369.584797] config - if there is no relations between the [71369.584797] names, then host name confusion attack is possible. Apr 26 11:53:38 192.168.122.209 [71369.671542] [tempesta fw] Configuration processing is completed. Apr 26 11:53:39 192.168.122.209 [71369.735055] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:53:39 192.168.122.209 [71370.140197] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:53:39 192.168.122.209 [71370.165806] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:53:39 192.168.122.209 [71370.190861] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:53:39 192.168.122.209 [71370.235449] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:53:39 192.168.122.209 [71370.237177] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:53:39 192.168.122.209 [71370.283494] [tempesta fw] Tempesta FW is ready Apr 26 11:53:40 192.168.122.209 [71370.985525] [tdb] Close table 'client0.tdb' Apr 26 11:53:40 192.168.122.209 [71371.173116] [tdb] Close table 'sessions0.tdb' Apr 26 11:53:43 192.168.122.209 [71374.287623] [tdb] Close table 'cache0.tdb' Apr 26 11:53:43 192.168.122.209 [71374.560826] [tdb] Close table 'filter0.tdb' Apr 26 11:53:43 192.168.122.209 [71374.561285] [tempesta fw] modules are stopped Apr 26 11:53:44 192.168.122.209 [71374.772089] [tempesta fw] exiting... Apr 26 11:53:44 192.168.122.209 [71374.893729] [tdb] Shutdown Tempesta DB Apr 26 11:53:44 192.168.122.209 [71375.328504] End test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_query_param_different_value Apr 26 11:53:44 192.168.122.209 [71375.359174] Start test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_query_param_same_params Apr 26 11:53:46 192.168.122.209 [71376.791598] [tdb] Start Tempesta DB Apr 26 11:53:46 192.168.122.209 [71376.923711] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:53:47 192.168.122.209 [71378.292948] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [71378.292948] Maybe that's fine, but it's worth checking the [71378.292948] config - if there is no relations between the [71378.292948] names, then host name confusion attack is possible. Apr 26 11:53:47 192.168.122.209 [71378.379672] [tempesta fw] Configuration processing is completed. Apr 26 11:53:47 192.168.122.209 [71378.437788] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:53:48 192.168.122.209 [71378.863989] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:53:48 192.168.122.209 [71378.890642] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:53:48 192.168.122.209 [71378.916544] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:53:48 192.168.122.209 [71378.963637] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:53:48 192.168.122.209 [71378.965372] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:53:48 192.168.122.209 [71379.003592] [tempesta fw] Tempesta FW is ready Apr 26 11:53:49 192.168.122.209 [71379.706085] [tdb] Close table 'client0.tdb' Apr 26 11:53:49 192.168.122.209 [71379.892248] [tdb] Close table 'sessions0.tdb' Apr 26 11:53:52 192.168.122.209 [71383.018548] [tdb] Close table 'cache0.tdb' Apr 26 11:53:52 192.168.122.209 [71383.265760] [tdb] Close table 'filter0.tdb' Apr 26 11:53:52 192.168.122.209 [71383.266166] [tempesta fw] modules are stopped Apr 26 11:53:52 192.168.122.209 [71383.460261] [tempesta fw] exiting... Apr 26 11:53:52 192.168.122.209 [71383.581362] [tdb] Shutdown Tempesta DB Apr 26 11:53:53 192.168.122.209 [71383.898832] End test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_query_param_same_params Apr 26 11:53:53 192.168.122.209 [71383.978040] Start test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_query_param_with_new_param Apr 26 11:53:54 192.168.122.209 [71385.321582] [tdb] Start Tempesta DB Apr 26 11:53:54 192.168.122.209 [71385.463302] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:53:56 192.168.122.209 [71386.857042] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [71386.857042] Maybe that's fine, but it's worth checking the [71386.857042] config - if there is no relations between the [71386.857042] names, then host name confusion attack is possible. Apr 26 11:53:56 192.168.122.209 [71386.939786] [tempesta fw] Configuration processing is completed. Apr 26 11:53:56 192.168.122.209 [71386.996725] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:53:56 192.168.122.209 [71387.414526] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:53:56 192.168.122.209 [71387.441862] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:53:56 192.168.122.209 [71387.474250] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:53:56 192.168.122.209 [71387.523745] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:53:56 192.168.122.209 [71387.525478] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:53:56 192.168.122.209 [71387.563692] [tempesta fw] Tempesta FW is ready Apr 26 11:53:57 192.168.122.209 [71388.275450] [tdb] Close table 'client0.tdb' Apr 26 11:53:57 192.168.122.209 [71388.459125] [tdb] Close table 'sessions0.tdb' Apr 26 11:54:00 192.168.122.209 [71391.589677] [tdb] Close table 'cache0.tdb' Apr 26 11:54:01 192.168.122.209 [71391.804934] [tdb] Close table 'filter0.tdb' Apr 26 11:54:01 192.168.122.209 [71391.805330] [tempesta fw] modules are stopped Apr 26 11:54:01 192.168.122.209 [71392.004070] [tempesta fw] exiting... Apr 26 11:54:01 192.168.122.209 [71392.120355] [tdb] Shutdown Tempesta DB Apr 26 11:54:01 192.168.122.209 [71392.497442] End test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_query_param_with_new_param Apr 26 11:54:01 192.168.122.209 [71392.532078] Start test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_redirect_300_multiple_choices Apr 26 11:54:03 192.168.122.209 [71393.941086] [tdb] Start Tempesta DB Apr 26 11:54:03 192.168.122.209 [71394.077793] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:54:04 192.168.122.209 [71395.465198] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [71395.465198] Maybe that's fine, but it's worth checking the [71395.465198] config - if there is no relations between the [71395.465198] names, then host name confusion attack is possible. Apr 26 11:54:04 192.168.122.209 [71395.559899] [tempesta fw] Configuration processing is completed. Apr 26 11:54:04 192.168.122.209 [71395.617995] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:54:05 192.168.122.209 [71396.038728] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:54:05 192.168.122.209 [71396.070639] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:54:05 192.168.122.209 [71396.098258] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:54:05 192.168.122.209 [71396.139852] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:54:05 192.168.122.209 [71396.141568] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:54:05 192.168.122.209 [71396.183808] [tempesta fw] Tempesta FW is ready Apr 26 11:54:06 192.168.122.209 [71396.827555] [tdb] Close table 'client0.tdb' Apr 26 11:54:06 192.168.122.209 [71397.010659] [tdb] Close table 'sessions0.tdb' Apr 26 11:54:09 192.168.122.209 [71400.121301] [tdb] Close table 'cache0.tdb' Apr 26 11:54:09 192.168.122.209 [71400.382327] [tdb] Close table 'filter0.tdb' Apr 26 11:54:09 192.168.122.209 [71400.382762] [tempesta fw] modules are stopped Apr 26 11:54:09 192.168.122.209 [71400.572397] [tempesta fw] exiting... Apr 26 11:54:10 192.168.122.209 [71400.706922] [tdb] Shutdown Tempesta DB Apr 26 11:54:10 192.168.122.209 [71401.078722] End test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_redirect_300_multiple_choices Apr 26 11:54:10 192.168.122.209 [71401.112378] Start test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_redirect_301_moved_permanently Apr 26 11:54:11 192.168.122.209 [71402.484275] [tdb] Start Tempesta DB Apr 26 11:54:11 192.168.122.209 [71402.629768] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:54:13 192.168.122.209 [71404.089211] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [71404.089211] Maybe that's fine, but it's worth checking the [71404.089211] config - if there is no relations between the [71404.089211] names, then host name confusion attack is possible. Apr 26 11:54:13 192.168.122.209 [71404.175987] [tempesta fw] Configuration processing is completed. Apr 26 11:54:13 192.168.122.209 [71404.229758] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:54:13 192.168.122.209 [71404.641660] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:54:13 192.168.122.209 [71404.667133] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:54:13 192.168.122.209 [71404.692584] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:54:14 192.168.122.209 [71404.739964] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:54:14 192.168.122.209 [71404.741702] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:54:14 192.168.122.209 [71404.791917] [tempesta fw] Tempesta FW is ready Apr 26 11:54:14 192.168.122.209 [71405.454569] [tdb] Close table 'client0.tdb' Apr 26 11:54:14 192.168.122.209 [71405.637659] [tdb] Close table 'sessions0.tdb' Apr 26 11:54:18 192.168.122.209 [71408.788980] [tdb] Close table 'cache0.tdb' Apr 26 11:54:18 192.168.122.209 [71409.033821] [tdb] Close table 'filter0.tdb' Apr 26 11:54:18 192.168.122.209 [71409.034248] [tempesta fw] modules are stopped Apr 26 11:54:18 192.168.122.209 [71409.220912] [tempesta fw] exiting... Apr 26 11:54:18 192.168.122.209 [71409.371535] [tdb] Shutdown Tempesta DB Apr 26 11:54:19 192.168.122.209 [71409.772877] End test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_redirect_301_moved_permanently Apr 26 11:54:19 192.168.122.209 [71409.805517] Start test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_redirect_302_found Apr 26 11:54:20 192.168.122.209 [71411.100732] [tdb] Start Tempesta DB Apr 26 11:54:20 192.168.122.209 [71411.231242] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:54:21 192.168.122.209 [71412.629331] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [71412.629331] Maybe that's fine, but it's worth checking the [71412.629331] config - if there is no relations between the [71412.629331] names, then host name confusion attack is possible. Apr 26 11:54:22 192.168.122.209 [71412.712087] [tempesta fw] Configuration processing is completed. Apr 26 11:54:22 192.168.122.209 [71412.764664] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:54:22 192.168.122.209 [71413.175682] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:54:22 192.168.122.209 [71413.200714] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:54:22 192.168.122.209 [71413.226023] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:54:22 192.168.122.209 [71413.304073] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:54:22 192.168.122.209 [71413.305811] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:54:22 192.168.122.209 [71413.344028] [tempesta fw] Tempesta FW is ready Apr 26 11:54:23 192.168.122.209 [71414.024538] [tdb] Close table 'client0.tdb' Apr 26 11:54:23 192.168.122.209 [71414.208915] [tdb] Close table 'sessions0.tdb' Apr 26 11:54:26 192.168.122.209 [71417.395211] [tdb] Close table 'cache0.tdb' Apr 26 11:54:26 192.168.122.209 [71417.633666] [tdb] Close table 'filter0.tdb' Apr 26 11:54:26 192.168.122.209 [71417.634073] [tempesta fw] modules are stopped Apr 26 11:54:27 192.168.122.209 [71417.820426] [tempesta fw] exiting... Apr 26 11:54:27 192.168.122.209 [71417.958035] [tdb] Shutdown Tempesta DB Apr 26 11:54:27 192.168.122.209 [71418.329304] End test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_redirect_302_found Apr 26 11:54:27 192.168.122.209 [71418.370423] Start test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_redirect_303_see_other Apr 26 11:54:29 192.168.122.209 [71419.769460] [tdb] Start Tempesta DB Apr 26 11:54:29 192.168.122.209 [71419.896450] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:54:30 192.168.122.209 [71421.385434] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [71421.385434] Maybe that's fine, but it's worth checking the [71421.385434] config - if there is no relations between the [71421.385434] names, then host name confusion attack is possible. Apr 26 11:54:30 192.168.122.209 [71421.480213] [tempesta fw] Configuration processing is completed. Apr 26 11:54:30 192.168.122.209 [71421.536376] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:54:31 192.168.122.209 [71421.953495] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:54:31 192.168.122.209 [71421.979290] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:54:31 192.168.122.209 [71422.004583] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:54:31 192.168.122.209 [71422.044158] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:54:31 192.168.122.209 [71422.045858] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:54:31 192.168.122.209 [71422.092094] [tempesta fw] Tempesta FW is ready Apr 26 11:54:32 192.168.122.209 [71422.766422] [tdb] Close table 'client0.tdb' Apr 26 11:54:32 192.168.122.209 [71422.964259] [tdb] Close table 'sessions0.tdb' Apr 26 11:54:35 192.168.122.209 [71426.091595] [tdb] Close table 'cache0.tdb' Apr 26 11:54:35 192.168.122.209 [71426.362242] [tdb] Close table 'filter0.tdb' Apr 26 11:54:35 192.168.122.209 [71426.362681] [tempesta fw] modules are stopped Apr 26 11:54:35 192.168.122.209 [71426.538324] [tempesta fw] exiting... Apr 26 11:54:35 192.168.122.209 [71426.652381] [tdb] Shutdown Tempesta DB Apr 26 11:54:36 192.168.122.209 [71427.084546] End test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_redirect_303_see_other Apr 26 11:54:36 192.168.122.209 [71427.121526] Start test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_redirect_304_not_modified Apr 26 11:54:37 192.168.122.209 [71428.478184] [tdb] Start Tempesta DB Apr 26 11:54:37 192.168.122.209 [71428.617790] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:54:39 192.168.122.209 [71430.017569] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [71430.017569] Maybe that's fine, but it's worth checking the [71430.017569] config - if there is no relations between the [71430.017569] names, then host name confusion attack is possible. Apr 26 11:54:39 192.168.122.209 [71430.124322] [tempesta fw] Configuration processing is completed. Apr 26 11:54:39 192.168.122.209 [71430.181658] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:54:39 192.168.122.209 [71430.609356] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:54:39 192.168.122.209 [71430.636236] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:54:39 192.168.122.209 [71430.661356] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:54:40 192.168.122.209 [71430.704316] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:54:40 192.168.122.209 [71430.706052] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:54:40 192.168.122.209 [71430.740249] [tempesta fw] Tempesta FW is ready Apr 26 11:54:40 192.168.122.209 [71431.434306] [tdb] Close table 'client0.tdb' Apr 26 11:54:40 192.168.122.209 [71431.617520] [tdb] Close table 'sessions0.tdb' Apr 26 11:54:44 192.168.122.209 [71434.781999] [tdb] Close table 'cache0.tdb' Apr 26 11:54:44 192.168.122.209 [71435.056797] [tdb] Close table 'filter0.tdb' Apr 26 11:54:44 192.168.122.209 [71435.057234] [tempesta fw] modules are stopped Apr 26 11:54:44 192.168.122.209 [71435.254358] [tempesta fw] exiting... Apr 26 11:54:44 192.168.122.209 [71435.396612] [tdb] Shutdown Tempesta DB Apr 26 11:54:45 192.168.122.209 [71435.785823] End test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_redirect_304_not_modified Apr 26 11:54:45 192.168.122.209 [71435.875366] Start test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_redirect_305_user_proxy Apr 26 11:54:46 192.168.122.209 [71437.146314] [tdb] Start Tempesta DB Apr 26 11:54:46 192.168.122.209 [71437.274082] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:54:47 192.168.122.209 [71438.657684] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [71438.657684] Maybe that's fine, but it's worth checking the [71438.657684] config - if there is no relations between the [71438.657684] names, then host name confusion attack is possible. Apr 26 11:54:48 192.168.122.209 [71438.764463] [tempesta fw] Configuration processing is completed. Apr 26 11:54:48 192.168.122.209 [71438.825870] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:54:48 192.168.122.209 [71439.237364] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:54:48 192.168.122.209 [71439.263192] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:54:48 192.168.122.209 [71439.289956] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:54:48 192.168.122.209 [71439.328407] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:54:48 192.168.122.209 [71439.330128] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:54:48 192.168.122.209 [71439.376344] [tempesta fw] Tempesta FW is ready Apr 26 11:54:49 192.168.122.209 [71440.021870] [tdb] Close table 'client0.tdb' Apr 26 11:54:49 192.168.122.209 [71440.209224] [tdb] Close table 'sessions0.tdb' Apr 26 11:54:52 192.168.122.209 [71443.339076] [tdb] Close table 'cache0.tdb' Apr 26 11:54:52 192.168.122.209 [71443.609659] [tdb] Close table 'filter0.tdb' Apr 26 11:54:52 192.168.122.209 [71443.610069] [tempesta fw] modules are stopped Apr 26 11:54:53 192.168.122.209 [71443.804551] [tempesta fw] exiting... Apr 26 11:54:53 192.168.122.209 [71443.972169] [tdb] Shutdown Tempesta DB Apr 26 11:54:53 192.168.122.209 [71444.330181] End test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_redirect_305_user_proxy Apr 26 11:54:53 192.168.122.209 [71444.369331] Start test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_redirect_307_temporary_redirect Apr 26 11:54:55 192.168.122.209 [71445.764929] [tdb] Start Tempesta DB Apr 26 11:54:55 192.168.122.209 [71445.899504] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:54:56 192.168.122.209 [71447.321811] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [71447.321811] Maybe that's fine, but it's worth checking the [71447.321811] config - if there is no relations between the [71447.321811] names, then host name confusion attack is possible. Apr 26 11:54:56 192.168.122.209 [71447.408546] [tempesta fw] Configuration processing is completed. Apr 26 11:54:56 192.168.122.209 [71447.465083] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:54:57 192.168.122.209 [71447.883318] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:54:57 192.168.122.209 [71447.910039] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:54:57 192.168.122.209 [71447.937144] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:54:57 192.168.122.209 [71448.004544] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:54:57 192.168.122.209 [71448.006295] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:54:57 192.168.122.209 [71448.044489] [tempesta fw] Tempesta FW is ready Apr 26 11:54:58 192.168.122.209 [71448.784974] [tdb] Close table 'client0.tdb' Apr 26 11:54:58 192.168.122.209 [71448.985167] [tdb] Close table 'sessions0.tdb' Apr 26 11:55:01 192.168.122.209 [71452.167010] [tdb] Close table 'cache0.tdb' Apr 26 11:55:01 192.168.122.209 [71452.387060] [tdb] Close table 'filter0.tdb' Apr 26 11:55:01 192.168.122.209 [71452.387504] [tempesta fw] modules are stopped Apr 26 11:55:01 192.168.122.209 [71452.657153] [tempesta fw] exiting... Apr 26 11:55:02 192.168.122.209 [71452.776549] [tdb] Shutdown Tempesta DB Apr 26 11:55:02 192.168.122.209 [71453.125308] End test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_redirect_307_temporary_redirect Apr 26 11:55:02 192.168.122.209 [71453.163584] Start test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_redirect_308_permanent_redirect Apr 26 11:55:03 192.168.122.209 [71454.634856] [tdb] Start Tempesta DB Apr 26 11:55:04 192.168.122.209 [71454.762410] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:55:05 192.168.122.209 [71456.173988] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [71456.173988] Maybe that's fine, but it's worth checking the [71456.173988] config - if there is no relations between the [71456.173988] names, then host name confusion attack is possible. Apr 26 11:55:05 192.168.122.209 [71456.264658] [tempesta fw] Configuration processing is completed. Apr 26 11:55:05 192.168.122.209 [71456.326179] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:55:06 192.168.122.209 [71456.757183] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:55:06 192.168.122.209 [71456.784556] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:55:06 192.168.122.209 [71456.812203] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:55:06 192.168.122.209 [71456.872632] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 11:55:06 192.168.122.209 [71456.874357] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:55:06 192.168.122.209 [71456.920582] [tempesta fw] Tempesta FW is ready Apr 26 11:55:06 192.168.122.209 [71457.675121] [tdb] Close table 'client0.tdb' Apr 26 11:55:07 192.168.122.209 [71457.861575] [tdb] Close table 'sessions0.tdb' Apr 26 11:55:10 192.168.122.209 [71461.048198] [tdb] Close table 'cache0.tdb' Apr 26 11:55:10 192.168.122.209 [71461.273187] [tdb] Close table 'filter0.tdb' Apr 26 11:55:10 192.168.122.209 [71461.273612] [tempesta fw] modules are stopped Apr 26 11:55:10 192.168.122.209 [71461.478057] [tempesta fw] exiting... Apr 26 11:55:10 192.168.122.209 [71461.623954] [tdb] Shutdown Tempesta DB Apr 26 11:55:11 192.168.122.209 [71462.027838] End test: cache.test_cache.TestQueryparamsAndRedirectHttp.test_redirect_308_permanent_redirect Apr 26 11:55:11 192.168.122.209 [71462.059813] Start test: cache.test_cache_control.CCArgBothNoCacheCached.test Apr 26 11:55:12 192.168.122.209 [71463.423638] [tdb] Start Tempesta DB Apr 26 11:55:12 192.168.122.209 [71463.562509] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:55:14 192.168.122.209 [71465.092809] [tempesta fw] Configuration processing is completed. Apr 26 11:55:14 192.168.122.209 [71465.151036] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:55:14 192.168.122.209 [71465.572417] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:55:14 192.168.122.209 [71465.598947] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:55:14 192.168.122.209 [71465.624740] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:55:14 192.168.122.209 [71465.676730] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:55:15 192.168.122.209 [71465.720699] [tempesta fw] Tempesta FW is ready Apr 26 11:55:15 192.168.122.209 [71466.320165] [tdb] Close table 'client0.tdb' Apr 26 11:55:15 192.168.122.209 [71466.531039] [tdb] Close table 'sessions0.tdb' Apr 26 11:55:18 192.168.122.209 [71469.705042] [tdb] Close table 'cache0.tdb' Apr 26 11:55:19 192.168.122.209 [71469.946327] [tdb] Close table 'filter0.tdb' Apr 26 11:55:19 192.168.122.209 [71469.946759] [tempesta fw] modules are stopped Apr 26 11:55:19 192.168.122.209 [71470.128790] [tempesta fw] exiting... Apr 26 11:55:19 192.168.122.209 [71470.263724] [tdb] Shutdown Tempesta DB Apr 26 11:55:19 192.168.122.209 [71470.645598] End test: cache.test_cache_control.CCArgBothNoCacheCached.test Apr 26 11:55:19 192.168.122.209 [71470.683163] Start test: cache.test_cache_control.CCArgNoCacheBypass.test Apr 26 11:55:21 192.168.122.209 [71471.930575] [tdb] Start Tempesta DB Apr 26 11:55:21 192.168.122.209 [71472.055346] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:55:22 192.168.122.209 [71473.500910] [tempesta fw] Configuration processing is completed. Apr 26 11:55:22 192.168.122.209 [71473.552163] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:55:23 192.168.122.209 [71473.981589] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:55:23 192.168.122.209 [71474.008525] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:55:23 192.168.122.209 [71474.034939] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:55:23 192.168.122.209 [71474.084849] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:55:23 192.168.122.209 [71474.128798] [tempesta fw] Tempesta FW is ready Apr 26 11:55:24 192.168.122.209 [71474.789229] [tdb] Close table 'client0.tdb' Apr 26 11:55:24 192.168.122.209 [71474.991253] [tdb] Close table 'sessions0.tdb' Apr 26 11:55:27 192.168.122.209 [71478.142520] [tdb] Close table 'cache0.tdb' Apr 26 11:55:27 192.168.122.209 [71478.405186] [tdb] Close table 'filter0.tdb' Apr 26 11:55:27 192.168.122.209 [71478.405632] [tempesta fw] modules are stopped Apr 26 11:55:27 192.168.122.209 [71478.613126] [tempesta fw] exiting... Apr 26 11:55:28 192.168.122.209 [71478.759200] [tdb] Shutdown Tempesta DB Apr 26 11:55:28 192.168.122.209 [71479.193689] End test: cache.test_cache_control.CCArgNoCacheBypass.test Apr 26 11:55:28 192.168.122.209 [71479.222877] Start test: cache.test_cache_control.CCArgNoCacheCached.test Apr 26 11:55:29 192.168.122.209 [71480.526230] [tdb] Start Tempesta DB Apr 26 11:55:29 192.168.122.209 [71480.661957] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:55:31 192.168.122.209 [71482.160907] [tempesta fw] Configuration processing is completed. Apr 26 11:55:31 192.168.122.209 [71482.210368] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:55:31 192.168.122.209 [71482.624155] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:55:31 192.168.122.209 [71482.654126] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:55:31 192.168.122.209 [71482.680891] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:55:32 192.168.122.209 [71482.720958] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:55:32 192.168.122.209 [71482.760914] [tempesta fw] Tempesta FW is ready Apr 26 11:55:32 192.168.122.209 [71483.434725] [tdb] Close table 'client0.tdb' Apr 26 11:55:32 192.168.122.209 [71483.622689] [tdb] Close table 'sessions0.tdb' Apr 26 11:55:36 192.168.122.209 [71486.774349] [tdb] Close table 'cache0.tdb' Apr 26 11:55:36 192.168.122.209 [71487.066427] [tdb] Close table 'filter0.tdb' Apr 26 11:55:36 192.168.122.209 [71487.066869] [tempesta fw] modules are stopped Apr 26 11:55:36 192.168.122.209 [71487.267426] [tempesta fw] exiting... Apr 26 11:55:36 192.168.122.209 [71487.413704] [tdb] Shutdown Tempesta DB Apr 26 11:55:37 192.168.122.209 [71487.814737] End test: cache.test_cache_control.CCArgNoCacheCached.test Apr 26 11:55:37 192.168.122.209 [71487.843402] Start test: cache.test_cache_control.CCArgNoCacheCached2.test Apr 26 11:55:38 192.168.122.209 [71489.214103] [tdb] Start Tempesta DB Apr 26 11:55:38 192.168.122.209 [71489.352125] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:55:40 192.168.122.209 [71490.853109] [tempesta fw] Configuration processing is completed. Apr 26 11:55:40 192.168.122.209 [71490.905405] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:55:40 192.168.122.209 [71491.324280] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:55:40 192.168.122.209 [71491.350235] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:55:40 192.168.122.209 [71491.375920] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:55:40 192.168.122.209 [71491.409076] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:55:40 192.168.122.209 [71491.449051] [tempesta fw] Tempesta FW is ready Apr 26 11:55:41 192.168.122.209 [71492.095677] [tdb] Close table 'client0.tdb' Apr 26 11:55:41 192.168.122.209 [71492.283442] [tdb] Close table 'sessions0.tdb' Apr 26 11:55:44 192.168.122.209 [71495.466004] [tdb] Close table 'cache0.tdb' Apr 26 11:55:45 192.168.122.209 [71495.721008] [tdb] Close table 'filter0.tdb' Apr 26 11:55:45 192.168.122.209 [71495.721653] [tempesta fw] modules are stopped Apr 26 11:55:45 192.168.122.209 [71495.942854] [tempesta fw] exiting... Apr 26 11:55:45 192.168.122.209 [71496.046396] [tdb] Shutdown Tempesta DB Apr 26 11:55:45 192.168.122.209 [71496.473593] End test: cache.test_cache_control.CCArgNoCacheCached2.test Apr 26 11:55:45 192.168.122.209 [71496.498863] Start test: cache.test_cache_control.CCArgNoCacheCached3.test Apr 26 11:55:47 192.168.122.209 [71497.827452] [tdb] Start Tempesta DB Apr 26 11:55:47 192.168.122.209 [71497.953110] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:55:48 192.168.122.209 [71499.465318] [tempesta fw] Configuration processing is completed. Apr 26 11:55:48 192.168.122.209 [71499.518345] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:55:49 192.168.122.209 [71499.934162] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:55:49 192.168.122.209 [71499.960568] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:55:49 192.168.122.209 [71499.986827] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:55:49 192.168.122.209 [71500.033196] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:55:49 192.168.122.209 [71500.073143] [tempesta fw] Tempesta FW is ready Apr 26 11:55:49 192.168.122.209 [71500.696103] [tdb] Close table 'client0.tdb' Apr 26 11:55:50 192.168.122.209 [71500.891135] [tdb] Close table 'sessions0.tdb' Apr 26 11:55:53 192.168.122.209 [71504.084842] [tdb] Close table 'cache0.tdb' Apr 26 11:55:53 192.168.122.209 [71504.320442] [tdb] Close table 'filter0.tdb' Apr 26 11:55:53 192.168.122.209 [71504.320905] [tempesta fw] modules are stopped Apr 26 11:55:53 192.168.122.209 [71504.509749] [tempesta fw] exiting... Apr 26 11:55:53 192.168.122.209 [71504.662471] [tdb] Shutdown Tempesta DB Apr 26 11:55:54 192.168.122.209 [71505.029996] End test: cache.test_cache_control.CCArgNoCacheCached3.test Apr 26 11:55:54 192.168.122.209 [71505.064546] Start test: cache.test_cache_control.CCArgPrivateBypass.test Apr 26 11:55:55 192.168.122.209 [71506.414032] [tdb] Start Tempesta DB Apr 26 11:55:55 192.168.122.209 [71506.546932] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:55:57 192.168.122.209 [71508.009396] [tempesta fw] Configuration processing is completed. Apr 26 11:55:57 192.168.122.209 [71508.067457] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:55:57 192.168.122.209 [71508.489361] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:55:57 192.168.122.209 [71508.515799] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:55:57 192.168.122.209 [71508.541818] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:55:57 192.168.122.209 [71508.581292] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:55:57 192.168.122.209 [71508.629244] [tempesta fw] Tempesta FW is ready Apr 26 11:55:58 192.168.122.209 [71509.265031] [tdb] Close table 'client0.tdb' Apr 26 11:55:58 192.168.122.209 [71509.472146] [tdb] Close table 'sessions0.tdb' Apr 26 11:56:01 192.168.122.209 [71512.619654] [tdb] Close table 'cache0.tdb' Apr 26 11:56:02 192.168.122.209 [71512.842166] [tdb] Close table 'filter0.tdb' Apr 26 11:56:02 192.168.122.209 [71512.842602] [tempesta fw] modules are stopped Apr 26 11:56:02 192.168.122.209 [71513.042988] [tempesta fw] exiting... Apr 26 11:56:02 192.168.122.209 [71513.186284] [tdb] Shutdown Tempesta DB Apr 26 11:56:02 192.168.122.209 [71513.565254] End test: cache.test_cache_control.CCArgPrivateBypass.test Apr 26 11:56:02 192.168.122.209 [71513.595613] Start test: cache.test_cache_control.CCArgPrivateCached.test Apr 26 11:56:04 192.168.122.209 [71514.969470] [tdb] Start Tempesta DB Apr 26 11:56:04 192.168.122.209 [71515.099479] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:56:05 192.168.122.209 [71516.601484] [tempesta fw] Configuration processing is completed. Apr 26 11:56:05 192.168.122.209 [71516.661683] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:56:06 192.168.122.209 [71517.079462] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:56:06 192.168.122.209 [71517.105511] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:56:06 192.168.122.209 [71517.131217] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:56:06 192.168.122.209 [71517.169416] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:56:06 192.168.122.209 [71517.213419] [tempesta fw] Tempesta FW is ready Apr 26 11:56:07 192.168.122.209 [71517.856916] [tdb] Close table 'client0.tdb' Apr 26 11:56:07 192.168.122.209 [71518.039293] [tdb] Close table 'sessions0.tdb' Apr 26 11:56:10 192.168.122.209 [71521.188617] [tdb] Close table 'cache0.tdb' Apr 26 11:56:10 192.168.122.209 [71521.430321] [tdb] Close table 'filter0.tdb' Apr 26 11:56:10 192.168.122.209 [71521.430752] [tempesta fw] modules are stopped Apr 26 11:56:10 192.168.122.209 [71521.609753] [tempesta fw] exiting... Apr 26 11:56:11 192.168.122.209 [71521.749230] [tdb] Shutdown Tempesta DB Apr 26 11:56:11 192.168.122.209 [71522.150508] End test: cache.test_cache_control.CCArgPrivateCached.test Apr 26 11:56:11 192.168.122.209 [71522.231942] Start test: cache.test_cache_control.CCArgPrivateCached2.test Apr 26 11:56:12 192.168.122.209 [71523.527894] [tdb] Start Tempesta DB Apr 26 11:56:12 192.168.122.209 [71523.657600] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:56:14 192.168.122.209 [71525.185578] [tempesta fw] Configuration processing is completed. Apr 26 11:56:14 192.168.122.209 [71525.240071] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:56:14 192.168.122.209 [71525.662583] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:56:14 192.168.122.209 [71525.689793] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:56:15 192.168.122.209 [71525.716641] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:56:15 192.168.122.209 [71525.769558] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:56:15 192.168.122.209 [71525.809510] [tempesta fw] Tempesta FW is ready Apr 26 11:56:15 192.168.122.209 [71526.454703] [tdb] Close table 'client0.tdb' Apr 26 11:56:15 192.168.122.209 [71526.636303] [tdb] Close table 'sessions0.tdb' Apr 26 11:56:19 192.168.122.209 [71529.829611] [tdb] Close table 'cache0.tdb' Apr 26 11:56:19 192.168.122.209 [71530.062737] [tdb] Close table 'filter0.tdb' Apr 26 11:56:19 192.168.122.209 [71530.063169] [tempesta fw] modules are stopped Apr 26 11:56:19 192.168.122.209 [71530.250345] [tempesta fw] exiting... Apr 26 11:56:19 192.168.122.209 [71530.382497] [tdb] Shutdown Tempesta DB Apr 26 11:56:20 192.168.122.209 [71530.735185] End test: cache.test_cache_control.CCArgPrivateCached2.test Apr 26 11:56:20 192.168.122.209 [71530.767482] Start test: cache.test_cache_control.CacheHdrDelBypass.test Apr 26 11:56:21 192.168.122.209 [71532.067503] [tdb] Start Tempesta DB Apr 26 11:56:21 192.168.122.209 [71532.190383] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:56:23 192.168.122.209 [71533.709979] [tempesta fw] Configuration processing is completed. Apr 26 11:56:23 192.168.122.209 [71533.766610] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:56:23 192.168.122.209 [71534.186393] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:56:23 192.168.122.209 [71534.214004] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:56:23 192.168.122.209 [71534.243318] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:56:23 192.168.122.209 [71534.281639] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:56:23 192.168.122.209 [71534.321583] [tempesta fw] Tempesta FW is ready Apr 26 11:56:24 192.168.122.209 [71534.992144] [tdb] Close table 'client0.tdb' Apr 26 11:56:24 192.168.122.209 [71535.170632] [tdb] Close table 'sessions0.tdb' Apr 26 11:56:27 192.168.122.209 [71538.352370] [tdb] Close table 'cache0.tdb' Apr 26 11:56:27 192.168.122.209 [71538.602012] [tdb] Close table 'filter0.tdb' Apr 26 11:56:27 192.168.122.209 [71538.602458] [tempesta fw] modules are stopped Apr 26 11:56:28 192.168.122.209 [71538.814962] [tempesta fw] exiting... Apr 26 11:56:28 192.168.122.209 [71538.933953] [tdb] Shutdown Tempesta DB Apr 26 11:56:28 192.168.122.209 [71539.313751] End test: cache.test_cache_control.CacheHdrDelBypass.test Apr 26 11:56:28 192.168.122.209 [71539.348415] Start test: cache.test_cache_control.CacheHdrDelCached.test Apr 26 11:56:29 192.168.122.209 [71540.684855] [tdb] Start Tempesta DB Apr 26 11:56:30 192.168.122.209 [71540.834001] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:56:31 192.168.122.209 [71542.377767] [tempesta fw] Configuration processing is completed. Apr 26 11:56:31 192.168.122.209 [71542.440713] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:56:32 192.168.122.209 [71542.855380] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:56:32 192.168.122.209 [71542.882057] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:56:32 192.168.122.209 [71542.908220] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:56:32 192.168.122.209 [71542.945752] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:56:32 192.168.122.209 [71542.993711] [tempesta fw] Tempesta FW is ready Apr 26 11:56:32 192.168.122.209 [71543.669253] [tdb] Close table 'client0.tdb' Apr 26 11:56:33 192.168.122.209 [71543.860182] [tdb] Close table 'sessions0.tdb' Apr 26 11:56:36 192.168.122.209 [71547.042098] [tdb] Close table 'cache0.tdb' Apr 26 11:56:36 192.168.122.209 [71547.290709] [tdb] Close table 'filter0.tdb' Apr 26 11:56:36 192.168.122.209 [71547.291163] [tempesta fw] modules are stopped Apr 26 11:56:36 192.168.122.209 [71547.506115] [tempesta fw] exiting... Apr 26 11:56:36 192.168.122.209 [71547.655869] [tdb] Shutdown Tempesta DB Apr 26 11:56:37 192.168.122.209 [71548.019470] End test: cache.test_cache_control.CacheHdrDelCached.test Apr 26 11:56:37 192.168.122.209 [71548.055842] Start test: cache.test_cache_control.CacheHdrDelCached2.test Apr 26 11:56:38 192.168.122.209 [71549.332826] [tdb] Start Tempesta DB Apr 26 11:56:38 192.168.122.209 [71549.461788] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:56:40 192.168.122.209 [71550.973901] [tempesta fw] Configuration processing is completed. Apr 26 11:56:40 192.168.122.209 [71551.028931] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:56:40 192.168.122.209 [71551.483868] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:56:40 192.168.122.209 [71551.513005] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:56:40 192.168.122.209 [71551.541254] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:56:40 192.168.122.209 [71551.617864] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:56:40 192.168.122.209 [71551.657814] [tempesta fw] Tempesta FW is ready Apr 26 11:56:41 192.168.122.209 [71552.286661] [tdb] Close table 'client0.tdb' Apr 26 11:56:41 192.168.122.209 [71552.450223] [tdb] Close table 'sessions0.tdb' Apr 26 11:56:44 192.168.122.209 [71555.690874] [tdb] Close table 'cache0.tdb' Apr 26 11:56:45 192.168.122.209 [71555.949498] [tdb] Close table 'filter0.tdb' Apr 26 11:56:45 192.168.122.209 [71555.950082] [tempesta fw] modules are stopped Apr 26 11:56:45 192.168.122.209 [71556.139160] [tempesta fw] exiting... Apr 26 11:56:45 192.168.122.209 [71556.285103] [tdb] Shutdown Tempesta DB Apr 26 11:56:46 192.168.122.209 [71556.710193] End test: cache.test_cache_control.CacheHdrDelCached2.test Apr 26 11:56:46 192.168.122.209 [71556.736812] Start test: cache.test_cache_control.CacheTtlGlobalApplied.test Apr 26 11:56:47 192.168.122.209 [71558.018862] [tdb] Start Tempesta DB Apr 26 11:56:47 192.168.122.209 [71558.152361] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:56:48 192.168.122.209 [71559.681974] [tempesta fw] Configuration processing is completed. Apr 26 11:56:49 192.168.122.209 [71559.732866] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:56:49 192.168.122.209 [71560.171485] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:56:49 192.168.122.209 [71560.199971] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:56:49 192.168.122.209 [71560.227208] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:56:49 192.168.122.209 [71560.269970] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:56:49 192.168.122.209 [71560.317927] [tempesta fw] Tempesta FW is ready Apr 26 11:56:52 192.168.122.209 [71562.913980] [tdb] Close table 'client0.tdb' Apr 26 11:56:52 192.168.122.209 [71563.115483] [tdb] Close table 'sessions0.tdb' Apr 26 11:56:55 192.168.122.209 [71566.284353] [tdb] Close table 'cache0.tdb' Apr 26 11:56:55 192.168.122.209 [71566.548261] [tdb] Close table 'filter0.tdb' Apr 26 11:56:55 192.168.122.209 [71566.548717] [tempesta fw] modules are stopped Apr 26 11:56:56 192.168.122.209 [71566.722295] [tempesta fw] exiting... Apr 26 11:56:56 192.168.122.209 [71566.857090] [tdb] Shutdown Tempesta DB Apr 26 11:56:56 192.168.122.209 [71567.285279] End test: cache.test_cache_control.CacheTtlGlobalApplied.test Apr 26 11:56:56 192.168.122.209 [71567.324297] Start test: cache.test_cache_control.CacheTtlGlobalApplied2.test Apr 26 11:56:57 192.168.122.209 [71568.615214] [tdb] Start Tempesta DB Apr 26 11:56:58 192.168.122.209 [71568.759391] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:56:59 192.168.122.209 [71570.290362] [tempesta fw] Configuration processing is completed. Apr 26 11:56:59 192.168.122.209 [71570.353832] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:57:00 192.168.122.209 [71570.771294] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:57:00 192.168.122.209 [71570.797239] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:57:00 192.168.122.209 [71570.822854] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:57:00 192.168.122.209 [71570.862108] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:57:00 192.168.122.209 [71570.906085] [tempesta fw] Tempesta FW is ready Apr 26 11:57:03 192.168.122.209 [71574.573136] [tdb] Close table 'client0.tdb' Apr 26 11:57:04 192.168.122.209 [71574.738052] [tdb] Close table 'sessions0.tdb' Apr 26 11:57:07 192.168.122.209 [71577.933856] [tdb] Close table 'cache0.tdb' Apr 26 11:57:07 192.168.122.209 [71578.216712] [tdb] Close table 'filter0.tdb' Apr 26 11:57:07 192.168.122.209 [71578.217156] [tempesta fw] modules are stopped Apr 26 11:57:07 192.168.122.209 [71578.411732] [tempesta fw] exiting... Apr 26 11:57:07 192.168.122.209 [71578.526243] [tdb] Shutdown Tempesta DB Apr 26 11:57:08 192.168.122.209 [71578.953003] End test: cache.test_cache_control.CacheTtlGlobalApplied2.test Apr 26 11:57:08 192.168.122.209 [71578.988691] Start test: cache.test_cache_control.CacheTtlGlobalHonourMaxAge.test Apr 26 11:57:09 192.168.122.209 [71580.376714] [tdb] Start Tempesta DB Apr 26 11:57:09 192.168.122.209 [71580.518832] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:57:11 192.168.122.209 [71582.006299] [tempesta fw] Configuration processing is completed. Apr 26 11:57:11 192.168.122.209 [71582.066354] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:57:11 192.168.122.209 [71582.525894] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:57:11 192.168.122.209 [71582.554421] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:57:11 192.168.122.209 [71582.581627] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:57:11 192.168.122.209 [71582.626276] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:57:11 192.168.122.209 [71582.666216] [tempesta fw] Tempesta FW is ready Apr 26 11:57:15 192.168.122.209 [71586.323919] [tdb] Close table 'client0.tdb' Apr 26 11:57:15 192.168.122.209 [71586.523186] [tdb] Close table 'sessions0.tdb' Apr 26 11:57:19 192.168.122.209 [71589.764164] [tdb] Close table 'cache0.tdb' Apr 26 11:57:19 192.168.122.209 [71590.005840] [tdb] Close table 'filter0.tdb' Apr 26 11:57:19 192.168.122.209 [71590.006763] [tempesta fw] modules are stopped Apr 26 11:57:19 192.168.122.209 [71590.208385] [tempesta fw] exiting... Apr 26 11:57:19 192.168.122.209 [71590.334960] [tdb] Shutdown Tempesta DB Apr 26 11:57:20 192.168.122.209 [71590.736706] End test: cache.test_cache_control.CacheTtlGlobalHonourMaxAge.test Apr 26 11:57:20 192.168.122.209 [71590.774415] Start test: cache.test_cache_control.CacheTtlGlobalHonourMaxAge2.test Apr 26 11:57:21 192.168.122.209 [71592.141500] [tdb] Start Tempesta DB Apr 26 11:57:21 192.168.122.209 [71592.314090] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:57:23 192.168.122.209 [71593.898505] [tempesta fw] Configuration processing is completed. Apr 26 11:57:23 192.168.122.209 [71593.954928] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:57:23 192.168.122.209 [71594.426460] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:57:23 192.168.122.209 [71594.456409] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:57:23 192.168.122.209 [71594.487255] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:57:23 192.168.122.209 [71594.530300] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:57:23 192.168.122.209 [71594.570392] [tempesta fw] Tempesta FW is ready Apr 26 11:57:27 192.168.122.209 [71598.245590] [tdb] Close table 'client0.tdb' Apr 26 11:57:27 192.168.122.209 [71598.432776] [tdb] Close table 'sessions0.tdb' Apr 26 11:57:31 192.168.122.209 [71601.739818] [tdb] Close table 'cache0.tdb' Apr 26 11:57:31 192.168.122.209 [71602.004112] [tdb] Close table 'filter0.tdb' Apr 26 11:57:31 192.168.122.209 [71602.004580] [tempesta fw] modules are stopped Apr 26 11:57:31 192.168.122.209 [71602.186784] [tempesta fw] exiting... Apr 26 11:57:31 192.168.122.209 [71602.294423] [tdb] Shutdown Tempesta DB Apr 26 11:57:32 192.168.122.209 [71602.733996] End test: cache.test_cache_control.CacheTtlGlobalHonourMaxAge2.test Apr 26 11:57:32 192.168.122.209 [71602.813046] Start test: cache.test_cache_control.CacheTtlHonourNoCache.test Apr 26 11:57:33 192.168.122.209 [71604.007049] [tdb] Start Tempesta DB Apr 26 11:57:33 192.168.122.209 [71604.148441] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:57:35 192.168.122.209 [71605.942626] [tempesta fw] Configuration processing is completed. Apr 26 11:57:35 192.168.122.209 [71605.998492] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:57:35 192.168.122.209 [71606.417426] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:57:35 192.168.122.209 [71606.443881] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:57:35 192.168.122.209 [71606.470446] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:57:35 192.168.122.209 [71606.510564] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:57:35 192.168.122.209 [71606.554504] [tempesta fw] Tempesta FW is ready Apr 26 11:57:38 192.168.122.209 [71609.186888] [tdb] Close table 'client0.tdb' Apr 26 11:57:38 192.168.122.209 [71609.387804] [tdb] Close table 'sessions0.tdb' Apr 26 11:57:41 192.168.122.209 [71612.650905] [tdb] Close table 'cache0.tdb' Apr 26 11:57:42 192.168.122.209 [71612.881731] [tdb] Close table 'filter0.tdb' Apr 26 11:57:42 192.168.122.209 [71612.882152] [tempesta fw] modules are stopped Apr 26 11:57:42 192.168.122.209 [71613.094714] [tempesta fw] exiting... Apr 26 11:57:42 192.168.122.209 [71613.223432] [tdb] Shutdown Tempesta DB Apr 26 11:57:42 192.168.122.209 [71613.612542] End test: cache.test_cache_control.CacheTtlHonourNoCache.test Apr 26 11:57:42 192.168.122.209 [71613.637848] Start test: cache.test_cache_control.CacheTtlHttpChainHonourMaxAge.test Apr 26 11:57:44 192.168.122.209 [71614.992112] [tdb] Start Tempesta DB Apr 26 11:57:44 192.168.122.209 [71615.124192] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:57:46 192.168.122.209 [71616.790804] [tempesta fw] Configuration processing is completed. Apr 26 11:57:46 192.168.122.209 [71616.860901] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:57:46 192.168.122.209 [71617.367515] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:57:46 192.168.122.209 [71617.398854] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:57:46 192.168.122.209 [71617.432682] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:57:46 192.168.122.209 [71617.474688] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:57:46 192.168.122.209 [71617.514648] [tempesta fw] Tempesta FW is ready Apr 26 11:57:51 192.168.122.209 [71622.178073] [tdb] Close table 'client0.tdb' Apr 26 11:57:51 192.168.122.209 [71622.359061] [tdb] Close table 'sessions0.tdb' Apr 26 11:57:54 192.168.122.209 [71625.656633] [tdb] Close table 'cache0.tdb' Apr 26 11:57:55 192.168.122.209 [71625.917489] [tdb] Close table 'filter0.tdb' Apr 26 11:57:55 192.168.122.209 [71625.917931] [tempesta fw] modules are stopped Apr 26 11:57:55 192.168.122.209 [71626.115381] [tempesta fw] exiting... Apr 26 11:57:55 192.168.122.209 [71626.244495] [tdb] Shutdown Tempesta DB Apr 26 11:57:55 192.168.122.209 [71626.653118] End test: cache.test_cache_control.CacheTtlHttpChainHonourMaxAge.test Apr 26 11:57:56 192.168.122.209 [71626.738885] Start test: cache.test_cache_control.CacheTtlHttpChainOverride.test Apr 26 11:57:57 192.168.122.209 [71628.065944] [tdb] Start Tempesta DB Apr 26 11:57:57 192.168.122.209 [71628.226334] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:57:59 192.168.122.209 [71629.914912] [tempesta fw] Configuration processing is completed. Apr 26 11:57:59 192.168.122.209 [71629.967803] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:57:59 192.168.122.209 [71630.392824] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:57:59 192.168.122.209 [71630.418872] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:57:59 192.168.122.209 [71630.445221] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:57:59 192.168.122.209 [71630.494870] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:57:59 192.168.122.209 [71630.546791] [tempesta fw] Tempesta FW is ready Apr 26 11:58:02 192.168.122.209 [71633.197691] [tdb] Close table 'client0.tdb' Apr 26 11:58:02 192.168.122.209 [71633.384699] [tdb] Close table 'sessions0.tdb' Apr 26 11:58:05 192.168.122.209 [71636.559537] [tdb] Close table 'cache0.tdb' Apr 26 11:58:06 192.168.122.209 [71636.811286] [tdb] Close table 'filter0.tdb' Apr 26 11:58:06 192.168.122.209 [71636.811728] [tempesta fw] modules are stopped Apr 26 11:58:06 192.168.122.209 [71637.026196] [tempesta fw] exiting... Apr 26 11:58:06 192.168.122.209 [71637.139737] [tdb] Shutdown Tempesta DB Apr 26 11:58:06 192.168.122.209 [71637.510121] End test: cache.test_cache_control.CacheTtlHttpChainOverride.test Apr 26 11:58:06 192.168.122.209 [71637.535853] Start test: cache.test_cache_control.HttpChainCacheActionBypass.test Apr 26 11:58:08 192.168.122.209 [71638.881398] [tdb] Start Tempesta DB Apr 26 11:58:08 192.168.122.209 [71639.011160] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:58:09 192.168.122.209 [71640.667047] [tempesta fw] Configuration processing is completed. Apr 26 11:58:10 192.168.122.209 [71640.730753] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:58:10 192.168.122.209 [71641.158268] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:58:10 192.168.122.209 [71641.184547] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:58:10 192.168.122.209 [71641.210173] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:58:10 192.168.122.209 [71641.255005] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:58:10 192.168.122.209 [71641.298885] [tempesta fw] Tempesta FW is ready Apr 26 11:58:11 192.168.122.209 [71641.998680] [tdb] Close table 'client0.tdb' Apr 26 11:58:11 192.168.122.209 [71642.176270] [tdb] Close table 'sessions0.tdb' Apr 26 11:58:14 192.168.122.209 [71645.358026] [tdb] Close table 'cache0.tdb' Apr 26 11:58:14 192.168.122.209 [71645.588349] [tdb] Close table 'filter0.tdb' Apr 26 11:58:14 192.168.122.209 [71645.588774] [tempesta fw] modules are stopped Apr 26 11:58:15 192.168.122.209 [71645.803465] [tempesta fw] exiting... Apr 26 11:58:15 192.168.122.209 [71645.930090] [tdb] Shutdown Tempesta DB Apr 26 11:58:15 192.168.122.209 [71646.323721] End test: cache.test_cache_control.HttpChainCacheActionBypass.test Apr 26 11:58:15 192.168.122.209 [71646.358699] Start test: cache.test_cache_control.HttpChainCacheActionCached.test Apr 26 11:58:16 192.168.122.209 [71647.673764] [tdb] Start Tempesta DB Apr 26 11:58:17 192.168.122.209 [71647.803559] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:58:18 192.168.122.209 [71649.383159] [tempesta fw] Configuration processing is completed. Apr 26 11:58:18 192.168.122.209 [71649.441114] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:58:19 192.168.122.209 [71649.869106] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:58:19 192.168.122.209 [71649.897255] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:58:19 192.168.122.209 [71649.923084] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:58:19 192.168.122.209 [71649.971104] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:58:19 192.168.122.209 [71650.011070] [tempesta fw] Tempesta FW is ready Apr 26 11:58:19 192.168.122.209 [71650.697731] [tdb] Close table 'client0.tdb' Apr 26 11:58:20 192.168.122.209 [71650.891933] [tdb] Close table 'sessions0.tdb' Apr 26 11:58:23 192.168.122.209 [71654.075368] [tdb] Close table 'cache0.tdb' Apr 26 11:58:23 192.168.122.209 [71654.317919] [tdb] Close table 'filter0.tdb' Apr 26 11:58:23 192.168.122.209 [71654.318402] [tempesta fw] modules are stopped Apr 26 11:58:23 192.168.122.209 [71654.539845] [tempesta fw] exiting... Apr 26 11:58:23 192.168.122.209 [71654.653383] [tdb] Shutdown Tempesta DB Apr 26 11:58:24 192.168.122.209 [71655.089674] End test: cache.test_cache_control.HttpChainCacheActionCached.test Apr 26 11:58:24 192.168.122.209 [71655.124878] Start test: cache.test_cache_control.HttpChainCacheActionOverrideBypass.test Apr 26 11:58:25 192.168.122.209 [71656.498665] [tdb] Start Tempesta DB Apr 26 11:58:25 192.168.122.209 [71656.641913] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:58:27 192.168.122.209 [71658.323295] [tempesta fw] Configuration processing is completed. Apr 26 11:58:27 192.168.122.209 [71658.382369] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:58:28 192.168.122.209 [71658.811505] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:58:28 192.168.122.209 [71658.837502] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:58:28 192.168.122.209 [71658.866111] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:58:28 192.168.122.209 [71658.931233] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:58:28 192.168.122.209 [71658.971191] [tempesta fw] Tempesta FW is ready Apr 26 11:58:28 192.168.122.209 [71659.653672] [tdb] Close table 'client0.tdb' Apr 26 11:58:29 192.168.122.209 [71659.847124] [tdb] Close table 'sessions0.tdb' Apr 26 11:58:32 192.168.122.209 [71663.059149] [tdb] Close table 'cache0.tdb' Apr 26 11:58:32 192.168.122.209 [71663.317800] [tdb] Close table 'filter0.tdb' Apr 26 11:58:32 192.168.122.209 [71663.318247] [tempesta fw] modules are stopped Apr 26 11:58:32 192.168.122.209 [71663.527991] [tempesta fw] exiting... Apr 26 11:58:32 192.168.122.209 [71663.638831] [tdb] Shutdown Tempesta DB Apr 26 11:58:33 192.168.122.209 [71664.074803] End test: cache.test_cache_control.HttpChainCacheActionOverrideBypass.test Apr 26 11:58:33 192.168.122.209 [71664.106330] Start test: cache.test_cache_control.HttpChainCacheActionOverrideCached.test Apr 26 11:58:34 192.168.122.209 [71665.327937] [tdb] Start Tempesta DB Apr 26 11:58:34 192.168.122.209 [71665.458080] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:58:36 192.168.122.209 [71667.083417] [tempesta fw] Configuration processing is completed. Apr 26 11:58:36 192.168.122.209 [71667.142118] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:58:36 192.168.122.209 [71667.567639] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:58:36 192.168.122.209 [71667.593469] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:58:36 192.168.122.209 [71667.618801] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:58:36 192.168.122.209 [71667.659358] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:58:36 192.168.122.209 [71667.703300] [tempesta fw] Tempesta FW is ready Apr 26 11:58:37 192.168.122.209 [71668.378696] [tdb] Close table 'client0.tdb' Apr 26 11:58:37 192.168.122.209 [71668.566073] [tdb] Close table 'sessions0.tdb' Apr 26 11:58:41 192.168.122.209 [71671.738918] [tdb] Close table 'cache0.tdb' Apr 26 11:58:41 192.168.122.209 [71671.984996] [tdb] Close table 'filter0.tdb' Apr 26 11:58:41 192.168.122.209 [71671.985456] [tempesta fw] modules are stopped Apr 26 11:58:41 192.168.122.209 [71672.169118] [tempesta fw] exiting... Apr 26 11:58:41 192.168.122.209 [71672.306802] [tdb] Shutdown Tempesta DB Apr 26 11:58:41 192.168.122.209 [71672.684914] End test: cache.test_cache_control.HttpChainCacheActionOverrideCached.test Apr 26 11:58:42 192.168.122.209 [71672.715305] Start test: cache.test_cache_control.RequestMaxAge0NoCache.test Apr 26 11:58:43 192.168.122.209 [71674.029252] [tdb] Start Tempesta DB Apr 26 11:58:43 192.168.122.209 [71674.170344] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:58:44 192.168.122.209 [71675.663516] [tempesta fw] Configuration processing is completed. Apr 26 11:58:45 192.168.122.209 [71675.721496] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:58:45 192.168.122.209 [71676.143137] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:58:45 192.168.122.209 [71676.169504] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:58:45 192.168.122.209 [71676.196146] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:58:45 192.168.122.209 [71676.247446] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:58:45 192.168.122.209 [71676.291393] [tempesta fw] Tempesta FW is ready Apr 26 11:58:46 192.168.122.209 [71676.969530] [tdb] Close table 'client0.tdb' Apr 26 11:58:46 192.168.122.209 [71677.152033] [tdb] Close table 'sessions0.tdb' Apr 26 11:58:49 192.168.122.209 [71680.362250] [tdb] Close table 'cache0.tdb' Apr 26 11:58:49 192.168.122.209 [71680.601037] [tdb] Close table 'filter0.tdb' Apr 26 11:58:49 192.168.122.209 [71680.601478] [tempesta fw] modules are stopped Apr 26 11:58:50 192.168.122.209 [71680.787730] [tempesta fw] exiting... Apr 26 11:58:50 192.168.122.209 [71680.914308] [tdb] Shutdown Tempesta DB Apr 26 11:58:50 192.168.122.209 [71681.289388] End test: cache.test_cache_control.RequestMaxAge0NoCache.test Apr 26 11:58:50 192.168.122.209 [71681.319811] Start test: cache.test_cache_control.RequestMaxAge0NoCache2.test Apr 26 11:58:51 192.168.122.209 [71682.582028] [tdb] Start Tempesta DB Apr 26 11:58:52 192.168.122.209 [71682.722262] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:58:53 192.168.122.209 [71684.195544] [tempesta fw] Configuration processing is completed. Apr 26 11:58:53 192.168.122.209 [71684.262957] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:58:53 192.168.122.209 [71684.686137] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:58:54 192.168.122.209 [71684.712926] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:58:54 192.168.122.209 [71684.747496] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:58:54 192.168.122.209 [71684.791557] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:58:54 192.168.122.209 [71684.835511] [tempesta fw] Tempesta FW is ready Apr 26 11:58:54 192.168.122.209 [71685.495061] [tdb] Close table 'client0.tdb' Apr 26 11:58:54 192.168.122.209 [71685.664367] [tdb] Close table 'sessions0.tdb' Apr 26 11:58:58 192.168.122.209 [71688.935147] [tdb] Close table 'cache0.tdb' Apr 26 11:58:58 192.168.122.209 [71689.205682] [tdb] Close table 'filter0.tdb' Apr 26 11:58:58 192.168.122.209 [71689.206137] [tempesta fw] modules are stopped Apr 26 11:58:58 192.168.122.209 [71689.393320] [tempesta fw] exiting... Apr 26 11:58:58 192.168.122.209 [71689.528942] [tdb] Shutdown Tempesta DB Apr 26 11:58:59 192.168.122.209 [71689.946461] End test: cache.test_cache_control.RequestMaxAge0NoCache2.test Apr 26 11:58:59 192.168.122.209 [71689.981976] Start test: cache.test_cache_control.RequestMaxAgeCached.test Apr 26 11:59:00 192.168.122.209 [71691.257699] [tdb] Start Tempesta DB Apr 26 11:59:00 192.168.122.209 [71691.395844] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:59:02 192.168.122.209 [71692.843703] [tempesta fw] Configuration processing is completed. Apr 26 11:59:02 192.168.122.209 [71692.894856] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:59:02 192.168.122.209 [71693.312536] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:59:02 192.168.122.209 [71693.339278] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:59:02 192.168.122.209 [71693.365817] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:59:02 192.168.122.209 [71693.419677] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:59:02 192.168.122.209 [71693.459629] [tempesta fw] Tempesta FW is ready Apr 26 11:59:03 192.168.122.209 [71694.124234] [tdb] Close table 'client0.tdb' Apr 26 11:59:03 192.168.122.209 [71694.292314] [tdb] Close table 'sessions0.tdb' Apr 26 11:59:06 192.168.122.209 [71697.472659] [tdb] Close table 'cache0.tdb' Apr 26 11:59:07 192.168.122.209 [71697.743712] [tdb] Close table 'filter0.tdb' Apr 26 11:59:07 192.168.122.209 [71697.744154] [tempesta fw] modules are stopped Apr 26 11:59:07 192.168.122.209 [71697.921272] [tempesta fw] exiting... Apr 26 11:59:07 192.168.122.209 [71698.045602] [tdb] Shutdown Tempesta DB Apr 26 11:59:07 192.168.122.209 [71698.406469] End test: cache.test_cache_control.RequestMaxAgeCached.test Apr 26 11:59:07 192.168.122.209 [71698.434867] Start test: cache.test_cache_control.RequestMaxAgeMaxStaleCached.test Apr 26 11:59:09 192.168.122.209 [71699.806531] [tdb] Start Tempesta DB Apr 26 11:59:09 192.168.122.209 [71699.944300] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:59:10 192.168.122.209 [71701.428344] [tempesta fw] Configuration processing is completed. Apr 26 11:59:10 192.168.122.209 [71701.482555] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:59:11 192.168.122.209 [71701.896504] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:59:11 192.168.122.209 [71701.923440] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:59:11 192.168.122.209 [71701.951662] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:59:11 192.168.122.209 [71701.999784] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:59:11 192.168.122.209 [71702.047733] [tempesta fw] Tempesta FW is ready Apr 26 11:59:13 192.168.122.209 [71704.158850] [tdb] Close table 'client0.tdb' Apr 26 11:59:13 192.168.122.209 [71704.354171] [tdb] Close table 'sessions0.tdb' Apr 26 11:59:16 192.168.122.209 [71707.554487] [tdb] Close table 'cache0.tdb' Apr 26 11:59:17 192.168.122.209 [71707.807377] [tdb] Close table 'filter0.tdb' Apr 26 11:59:17 192.168.122.209 [71707.807820] [tempesta fw] modules are stopped Apr 26 11:59:17 192.168.122.209 [71708.020107] [tempesta fw] exiting... Apr 26 11:59:17 192.168.122.209 [71708.156040] [tdb] Shutdown Tempesta DB Apr 26 11:59:17 192.168.122.209 [71708.522377] End test: cache.test_cache_control.RequestMaxAgeMaxStaleCached.test Apr 26 11:59:17 192.168.122.209 [71708.554377] Start test: cache.test_cache_control.RequestMaxAgeMaxStaleNotCached.test Apr 26 11:59:19 192.168.122.209 [71709.877951] [tdb] Start Tempesta DB Apr 26 11:59:19 192.168.122.209 [71710.025296] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:59:20 192.168.122.209 [71711.523939] [tempesta fw] Configuration processing is completed. Apr 26 11:59:20 192.168.122.209 [71711.575328] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:59:21 192.168.122.209 [71712.011514] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:59:21 192.168.122.209 [71712.038141] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:59:21 192.168.122.209 [71712.064428] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:59:21 192.168.122.209 [71712.111965] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:59:21 192.168.122.209 [71712.163888] [tempesta fw] Tempesta FW is ready Apr 26 11:59:25 192.168.122.209 [71715.768684] [tdb] Close table 'client0.tdb' Apr 26 11:59:25 192.168.122.209 [71715.950752] [tdb] Close table 'sessions0.tdb' Apr 26 11:59:28 192.168.122.209 [71719.126899] [tdb] Close table 'cache0.tdb' Apr 26 11:59:28 192.168.122.209 [71719.382688] [tdb] Close table 'filter0.tdb' Apr 26 11:59:28 192.168.122.209 [71719.383129] [tempesta fw] modules are stopped Apr 26 11:59:28 192.168.122.209 [71719.580068] [tempesta fw] exiting... Apr 26 11:59:28 192.168.122.209 [71719.699866] [tdb] Shutdown Tempesta DB Apr 26 11:59:29 192.168.122.209 [71720.123608] End test: cache.test_cache_control.RequestMaxAgeMaxStaleNotCached.test Apr 26 11:59:29 192.168.122.209 [71720.150457] Start test: cache.test_cache_control.RequestMaxAgeNoCached.test Apr 26 11:59:30 192.168.122.209 [71721.367183] [tdb] Start Tempesta DB Apr 26 11:59:30 192.168.122.209 [71721.505922] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:59:32 192.168.122.209 [71722.912136] [tempesta fw] Configuration processing is completed. Apr 26 11:59:32 192.168.122.209 [71722.967029] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:59:32 192.168.122.209 [71723.388130] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:59:32 192.168.122.209 [71723.414486] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:59:32 192.168.122.209 [71723.439793] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:59:32 192.168.122.209 [71723.492060] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:59:32 192.168.122.209 [71723.540000] [tempesta fw] Tempesta FW is ready Apr 26 11:59:35 192.168.122.209 [71726.264658] [tdb] Close table 'client0.tdb' Apr 26 11:59:35 192.168.122.209 [71726.450263] [tdb] Close table 'sessions0.tdb' Apr 26 11:59:38 192.168.122.209 [71729.601663] [tdb] Close table 'cache0.tdb' Apr 26 11:59:39 192.168.122.209 [71729.878326] [tdb] Close table 'filter0.tdb' Apr 26 11:59:39 192.168.122.209 [71729.878770] [tempesta fw] modules are stopped Apr 26 11:59:39 192.168.122.209 [71730.057281] [tempesta fw] exiting... Apr 26 11:59:39 192.168.122.209 [71730.198418] [tdb] Shutdown Tempesta DB Apr 26 11:59:39 192.168.122.209 [71730.538260] End test: cache.test_cache_control.RequestMaxAgeNoCached.test Apr 26 11:59:39 192.168.122.209 [71730.577937] Start test: cache.test_cache_control.RequestMaxStaleCached.test Apr 26 11:59:41 192.168.122.209 [71731.946898] [tdb] Start Tempesta DB Apr 26 11:59:41 192.168.122.209 [71732.081961] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:59:42 192.168.122.209 [71733.524247] [tempesta fw] Configuration processing is completed. Apr 26 11:59:42 192.168.122.209 [71733.589946] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:59:43 192.168.122.209 [71734.010669] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:59:43 192.168.122.209 [71734.038022] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:59:43 192.168.122.209 [71734.063906] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:59:43 192.168.122.209 [71734.112188] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:59:43 192.168.122.209 [71734.152143] [tempesta fw] Tempesta FW is ready Apr 26 11:59:45 192.168.122.209 [71736.322179] [tdb] Close table 'client0.tdb' Apr 26 11:59:45 192.168.122.209 [71736.505669] [tdb] Close table 'sessions0.tdb' Apr 26 11:59:48 192.168.122.209 [71739.681456] [tdb] Close table 'cache0.tdb' Apr 26 11:59:49 192.168.122.209 [71739.924276] [tdb] Close table 'filter0.tdb' Apr 26 11:59:49 192.168.122.209 [71739.924692] [tempesta fw] modules are stopped Apr 26 11:59:49 192.168.122.209 [71740.142082] [tempesta fw] exiting... Apr 26 11:59:49 192.168.122.209 [71740.273122] [tdb] Shutdown Tempesta DB Apr 26 11:59:49 192.168.122.209 [71740.676580] End test: cache.test_cache_control.RequestMaxStaleCached.test Apr 26 11:59:50 192.168.122.209 [71740.710156] Start test: cache.test_cache_control.RequestMinFreshCached.test Apr 26 11:59:51 192.168.122.209 [71742.098652] [tdb] Start Tempesta DB Apr 26 11:59:51 192.168.122.209 [71742.230174] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 11:59:52 192.168.122.209 [71743.684352] [tempesta fw] Configuration processing is completed. Apr 26 11:59:53 192.168.122.209 [71743.737024] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 11:59:53 192.168.122.209 [71744.148253] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 11:59:53 192.168.122.209 [71744.177624] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 11:59:53 192.168.122.209 [71744.204062] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 11:59:53 192.168.122.209 [71744.248315] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 11:59:53 192.168.122.209 [71744.292260] [tempesta fw] Tempesta FW is ready Apr 26 11:59:54 192.168.122.209 [71744.919636] [tdb] Close table 'client0.tdb' Apr 26 11:59:54 192.168.122.209 [71745.114165] [tdb] Close table 'sessions0.tdb' Apr 26 11:59:57 192.168.122.209 [71748.313770] [tdb] Close table 'cache0.tdb' Apr 26 11:59:57 192.168.122.209 [71748.633505] [tdb] Close table 'filter0.tdb' Apr 26 11:59:57 192.168.122.209 [71748.633906] [tempesta fw] modules are stopped Apr 26 11:59:58 192.168.122.209 [71748.819904] [tempesta fw] exiting... Apr 26 11:59:58 192.168.122.209 [71748.950252] [tdb] Shutdown Tempesta DB Apr 26 11:59:58 192.168.122.209 [71749.339974] End test: cache.test_cache_control.RequestMinFreshCached.test Apr 26 11:59:58 192.168.122.209 [71749.418213] Start test: cache.test_cache_control.RequestMinFreshNotCached.test Apr 26 11:59:59 192.168.122.209 [71750.693632] [tdb] Start Tempesta DB Apr 26 12:00:00 192.168.122.209 [71750.837803] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:00:01 192.168.122.209 [71752.304416] [tempesta fw] Configuration processing is completed. Apr 26 12:00:01 192.168.122.209 [71752.356829] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:00:02 192.168.122.209 [71752.777931] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:00:02 192.168.122.209 [71752.803994] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:00:02 192.168.122.209 [71752.829566] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:00:02 192.168.122.209 [71752.868378] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:00:02 192.168.122.209 [71752.916350] [tempesta fw] Tempesta FW is ready Apr 26 12:00:04 192.168.122.209 [71755.551015] [tdb] Close table 'client0.tdb' Apr 26 12:00:05 192.168.122.209 [71755.754954] [tdb] Close table 'sessions0.tdb' Apr 26 12:00:08 192.168.122.209 [71758.986625] [tdb] Close table 'cache0.tdb' Apr 26 12:00:08 192.168.122.209 [71759.210336] [tdb] Close table 'filter0.tdb' Apr 26 12:00:08 192.168.122.209 [71759.210752] [tempesta fw] modules are stopped Apr 26 12:00:08 192.168.122.209 [71759.441709] [tempesta fw] exiting... Apr 26 12:00:08 192.168.122.209 [71759.605428] [tdb] Shutdown Tempesta DB Apr 26 12:00:09 192.168.122.209 [71760.038019] End test: cache.test_cache_control.RequestMinFreshNotCached.test Apr 26 12:00:09 192.168.122.209 [71760.066133] Start test: cache.test_cache_control.RequestNoChacheNotCached.test Apr 26 12:00:10 192.168.122.209 [71761.438722] [tdb] Start Tempesta DB Apr 26 12:00:10 192.168.122.209 [71761.574185] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:00:12 192.168.122.209 [71763.028574] [tempesta fw] Configuration processing is completed. Apr 26 12:00:12 192.168.122.209 [71763.088893] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:00:12 192.168.122.209 [71763.514227] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:00:12 192.168.122.209 [71763.541136] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:00:12 192.168.122.209 [71763.576531] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:00:12 192.168.122.209 [71763.620538] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:00:12 192.168.122.209 [71763.664485] [tempesta fw] Tempesta FW is ready Apr 26 12:00:13 192.168.122.209 [71764.308272] [tdb] Close table 'client0.tdb' Apr 26 12:00:13 192.168.122.209 [71764.497063] [tdb] Close table 'sessions0.tdb' Apr 26 12:00:17 192.168.122.209 [71767.713941] [tdb] Close table 'cache0.tdb' Apr 26 12:00:17 192.168.122.209 [71767.978779] [tdb] Close table 'filter0.tdb' Apr 26 12:00:17 192.168.122.209 [71767.979222] [tempesta fw] modules are stopped Apr 26 12:00:17 192.168.122.209 [71768.149196] [tempesta fw] exiting... Apr 26 12:00:17 192.168.122.209 [71768.305200] [tdb] Shutdown Tempesta DB Apr 26 12:00:18 192.168.122.209 [71768.709675] End test: cache.test_cache_control.RequestNoChacheNotCached.test Apr 26 12:00:18 192.168.122.209 [71768.738543] Start test: cache.test_cache_control.RequestNoStoreNotCached.test Apr 26 12:00:19 192.168.122.209 [71770.147236] [tdb] Start Tempesta DB Apr 26 12:00:19 192.168.122.209 [71770.299091] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:00:21 192.168.122.209 [71771.816719] [tempesta fw] Configuration processing is completed. Apr 26 12:00:21 192.168.122.209 [71771.875987] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:00:21 192.168.122.209 [71772.298159] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:00:21 192.168.122.209 [71772.324316] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:00:21 192.168.122.209 [71772.349919] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:00:21 192.168.122.209 [71772.388570] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:00:21 192.168.122.209 [71772.424573] [tempesta fw] Tempesta FW is ready Apr 26 12:00:22 192.168.122.209 [71773.102455] [tdb] Close table 'client0.tdb' Apr 26 12:00:22 192.168.122.209 [71773.285133] [tdb] Close table 'sessions0.tdb' Apr 26 12:00:25 192.168.122.209 [71776.440701] [tdb] Close table 'cache0.tdb' Apr 26 12:00:26 192.168.122.209 [71776.722178] [tdb] Close table 'filter0.tdb' Apr 26 12:00:26 192.168.122.209 [71776.722611] [tempesta fw] modules are stopped Apr 26 12:00:26 192.168.122.209 [71776.979229] [tempesta fw] exiting... Apr 26 12:00:26 192.168.122.209 [71777.106250] [tdb] Shutdown Tempesta DB Apr 26 12:00:26 192.168.122.209 [71777.532381] End test: cache.test_cache_control.RequestNoStoreNotCached.test Apr 26 12:00:26 192.168.122.209 [71777.561685] Start test: cache.test_cache_control.RequestOnlyIfCached504.test Apr 26 12:00:28 192.168.122.209 [71778.856912] [tdb] Start Tempesta DB Apr 26 12:00:28 192.168.122.209 [71778.997055] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:00:29 192.168.122.209 [71780.488785] [tempesta fw] Configuration processing is completed. Apr 26 12:00:29 192.168.122.209 [71780.539457] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:00:30 192.168.122.209 [71780.959780] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:00:30 192.168.122.209 [71780.985964] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:00:30 192.168.122.209 [71781.012344] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:00:30 192.168.122.209 [71781.052727] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:00:30 192.168.122.209 [71781.092681] [tempesta fw] Tempesta FW is ready Apr 26 12:00:33 192.168.122.209 [71783.784627] [tempesta fw] Warning: resource not cached, status 504: 192.168.122.196 Apr 26 12:00:33 192.168.122.209 [71784.241862] [tdb] Close table 'client0.tdb' Apr 26 12:00:33 192.168.122.209 [71784.430639] [tdb] Close table 'sessions0.tdb' Apr 26 12:00:36 192.168.122.209 [71787.570765] [tdb] Close table 'cache0.tdb' Apr 26 12:00:37 192.168.122.209 [71787.806620] [tdb] Close table 'filter0.tdb' Apr 26 12:00:37 192.168.122.209 [71787.807056] [tempesta fw] modules are stopped Apr 26 12:00:37 192.168.122.209 [71788.004810] [tempesta fw] exiting... Apr 26 12:00:37 192.168.122.209 [71788.118062] [tdb] Shutdown Tempesta DB Apr 26 12:00:37 192.168.122.209 [71788.541471] End test: cache.test_cache_control.RequestOnlyIfCached504.test Apr 26 12:00:37 192.168.122.209 [71788.580959] Start test: cache.test_cache_control.RequestOnlyIfCachedCached.test Apr 26 12:00:39 192.168.122.209 [71789.928992] [tdb] Start Tempesta DB Apr 26 12:00:39 192.168.122.209 [71790.069944] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:00:40 192.168.122.209 [71791.584881] [tempesta fw] Configuration processing is completed. Apr 26 12:00:40 192.168.122.209 [71791.640699] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:00:41 192.168.122.209 [71792.059283] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:00:41 192.168.122.209 [71792.096335] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:00:41 192.168.122.209 [71792.121444] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:00:41 192.168.122.209 [71792.164898] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:00:41 192.168.122.209 [71792.208788] [tempesta fw] Tempesta FW is ready Apr 26 12:00:42 192.168.122.209 [71792.851657] [tdb] Close table 'client0.tdb' Apr 26 12:00:42 192.168.122.209 [71793.030465] [tdb] Close table 'sessions0.tdb' Apr 26 12:00:45 192.168.122.209 [71796.210894] [tdb] Close table 'cache0.tdb' Apr 26 12:00:45 192.168.122.209 [71796.469068] [tdb] Close table 'filter0.tdb' Apr 26 12:00:45 192.168.122.209 [71796.469500] [tempesta fw] modules are stopped Apr 26 12:00:45 192.168.122.209 [71796.678681] [tempesta fw] exiting... Apr 26 12:00:46 192.168.122.209 [71796.830000] [tdb] Shutdown Tempesta DB Apr 26 12:00:46 192.168.122.209 [71797.229057] End test: cache.test_cache_control.RequestOnlyIfCachedCached.test Apr 26 12:00:46 192.168.122.209 [71797.258373] Start test: cache.test_cache_control.ResponseForAuthorizationUserMustRevalidateNotCached.test Apr 26 12:00:47 192.168.122.209 [71798.547934] [tdb] Start Tempesta DB Apr 26 12:00:47 192.168.122.209 [71798.682093] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:00:49 192.168.122.209 [71800.152979] [tempesta fw] Configuration processing is completed. Apr 26 12:00:49 192.168.122.209 [71800.204456] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:00:49 192.168.122.209 [71800.616481] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:00:49 192.168.122.209 [71800.642970] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:00:49 192.168.122.209 [71800.669172] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:00:50 192.168.122.209 [71800.712946] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:00:50 192.168.122.209 [71800.760898] [tempesta fw] Tempesta FW is ready Apr 26 12:00:52 192.168.122.209 [71803.424906] [tdb] Close table 'client0.tdb' Apr 26 12:00:52 192.168.122.209 [71803.609888] [tdb] Close table 'sessions0.tdb' Apr 26 12:00:56 192.168.122.209 [71806.780641] [tdb] Close table 'cache0.tdb' Apr 26 12:00:56 192.168.122.209 [71807.032073] [tdb] Close table 'filter0.tdb' Apr 26 12:00:56 192.168.122.209 [71807.032505] [tempesta fw] modules are stopped Apr 26 12:00:56 192.168.122.209 [71807.254722] [tempesta fw] exiting... Apr 26 12:00:56 192.168.122.209 [71807.397236] [tdb] Shutdown Tempesta DB Apr 26 12:00:57 192.168.122.209 [71807.843017] End test: cache.test_cache_control.ResponseForAuthorizationUserMustRevalidateNotCached.test Apr 26 12:00:57 192.168.122.209 [71807.873276] Start test: cache.test_cache_control.ResponseMaxAgeCached.test Apr 26 12:00:58 192.168.122.209 [71809.134139] [tdb] Start Tempesta DB Apr 26 12:00:58 192.168.122.209 [71809.261706] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:01:00 192.168.122.209 [71810.725115] [tempesta fw] Configuration processing is completed. Apr 26 12:01:00 192.168.122.209 [71810.780319] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:01:00 192.168.122.209 [71811.196389] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:01:00 192.168.122.209 [71811.222636] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:01:00 192.168.122.209 [71811.249007] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:01:00 192.168.122.209 [71811.301081] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:01:00 192.168.122.209 [71811.361025] [tempesta fw] Tempesta FW is ready Apr 26 12:01:01 192.168.122.209 [71812.026812] [tdb] Close table 'client0.tdb' Apr 26 12:01:01 192.168.122.209 [71812.214158] [tdb] Close table 'sessions0.tdb' Apr 26 12:01:04 192.168.122.209 [71815.360189] [tdb] Close table 'cache0.tdb' Apr 26 12:01:04 192.168.122.209 [71815.615624] [tdb] Close table 'filter0.tdb' Apr 26 12:01:04 192.168.122.209 [71815.616031] [tempesta fw] modules are stopped Apr 26 12:01:05 192.168.122.209 [71815.793038] [tempesta fw] exiting... Apr 26 12:01:05 192.168.122.209 [71815.930480] [tdb] Shutdown Tempesta DB Apr 26 12:01:05 192.168.122.209 [71816.330629] End test: cache.test_cache_control.ResponseMaxAgeCached.test Apr 26 12:01:05 192.168.122.209 [71816.360323] Start test: cache.test_cache_control.ResponseMaxAgeCached2.test Apr 26 12:01:06 192.168.122.209 [71817.658488] [tdb] Start Tempesta DB Apr 26 12:01:07 192.168.122.209 [71817.778227] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:01:09 192.168.122.209 [71820.213304] [tempesta fw] Configuration processing is completed. Apr 26 12:01:09 192.168.122.209 [71820.423355] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:01:10 192.168.122.209 [71820.848145] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:01:10 192.168.122.209 [71820.875406] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:01:10 192.168.122.209 [71820.904114] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:01:10 192.168.122.209 [71821.517252] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:01:11 192.168.122.209 [71821.929150] [tempesta fw] Tempesta FW is ready Apr 26 12:01:12 192.168.122.209 [71823.335706] [tdb] Close table 'client0.tdb' Apr 26 12:01:13 192.168.122.209 [71823.721010] [tdb] Close table 'sessions0.tdb' Apr 26 12:01:16 192.168.122.209 [71827.064323] [tdb] Close table 'cache0.tdb' Apr 26 12:01:16 192.168.122.209 [71827.342992] [tdb] Close table 'filter0.tdb' Apr 26 12:01:16 192.168.122.209 [71827.343410] [tempesta fw] modules are stopped Apr 26 12:01:16 192.168.122.209 [71827.520580] [tempesta fw] exiting... Apr 26 12:01:16 192.168.122.209 [71827.671305] [tdb] Shutdown Tempesta DB Apr 26 12:01:17 192.168.122.209 [71828.085606] End test: cache.test_cache_control.ResponseMaxAgeCached2.test Apr 26 12:01:17 192.168.122.209 [71828.117058] Start test: cache.test_cache_control.ResponseMaxAgeIgnore.test Apr 26 12:01:18 192.168.122.209 [71829.402995] [tdb] Start Tempesta DB Apr 26 12:01:18 192.168.122.209 [71829.553571] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:01:20 192.168.122.209 [71831.093351] [tempesta fw] Configuration processing is completed. Apr 26 12:01:20 192.168.122.209 [71831.144491] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:01:20 192.168.122.209 [71831.562403] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:01:20 192.168.122.209 [71831.589183] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:01:20 192.168.122.209 [71831.615620] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:01:20 192.168.122.209 [71831.669340] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:01:20 192.168.122.209 [71831.709266] [tempesta fw] Tempesta FW is ready Apr 26 12:01:23 192.168.122.209 [71833.777544] [tdb] Close table 'client0.tdb' Apr 26 12:01:23 192.168.122.209 [71833.979803] [tdb] Close table 'sessions0.tdb' Apr 26 12:01:26 192.168.122.209 [71837.192287] [tdb] Close table 'cache0.tdb' Apr 26 12:01:26 192.168.122.209 [71837.427926] [tdb] Close table 'filter0.tdb' Apr 26 12:01:26 192.168.122.209 [71837.428370] [tempesta fw] modules are stopped Apr 26 12:01:26 192.168.122.209 [71837.644558] [tempesta fw] exiting... Apr 26 12:01:27 192.168.122.209 [71837.755163] [tdb] Shutdown Tempesta DB Apr 26 12:01:27 192.168.122.209 [71838.193662] End test: cache.test_cache_control.ResponseMaxAgeIgnore.test Apr 26 12:01:27 192.168.122.209 [71838.222210] Start test: cache.test_cache_control.ResponseMaxAgeNotCached.test Apr 26 12:01:28 192.168.122.209 [71839.589086] [tdb] Start Tempesta DB Apr 26 12:01:29 192.168.122.209 [71839.710611] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:01:30 192.168.122.209 [71841.209501] [tempesta fw] Configuration processing is completed. Apr 26 12:01:30 192.168.122.209 [71841.268689] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:01:30 192.168.122.209 [71841.694904] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:01:31 192.168.122.209 [71841.722157] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:01:31 192.168.122.209 [71841.748620] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:01:31 192.168.122.209 [71841.789440] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:01:31 192.168.122.209 [71841.829387] [tempesta fw] Tempesta FW is ready Apr 26 12:01:33 192.168.122.209 [71844.459535] [tdb] Close table 'client0.tdb' Apr 26 12:01:33 192.168.122.209 [71844.655523] [tdb] Close table 'sessions0.tdb' Apr 26 12:01:37 192.168.122.209 [71847.772877] [tdb] Close table 'cache0.tdb' Apr 26 12:01:37 192.168.122.209 [71848.028339] [tdb] Close table 'filter0.tdb' Apr 26 12:01:37 192.168.122.209 [71848.028775] [tempesta fw] modules are stopped Apr 26 12:01:37 192.168.122.209 [71848.224719] [tempesta fw] exiting... Apr 26 12:01:37 192.168.122.209 [71848.355758] [tdb] Shutdown Tempesta DB Apr 26 12:01:38 192.168.122.209 [71848.748121] End test: cache.test_cache_control.ResponseMaxAgeNotCached.test Apr 26 12:01:38 192.168.122.209 [71848.775632] Start test: cache.test_cache_control.ResponseMaxAgeNotCached2.test Apr 26 12:01:39 192.168.122.209 [71850.030213] [tdb] Start Tempesta DB Apr 26 12:01:39 192.168.122.209 [71850.161200] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:01:40 192.168.122.209 [71851.629616] [tempesta fw] Configuration processing is completed. Apr 26 12:01:40 192.168.122.209 [71851.681732] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:01:41 192.168.122.209 [71852.099011] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:01:41 192.168.122.209 [71852.125136] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:01:41 192.168.122.209 [71852.151943] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:01:41 192.168.122.209 [71852.213545] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:01:41 192.168.122.209 [71852.253507] [tempesta fw] Tempesta FW is ready Apr 26 12:01:42 192.168.122.209 [71852.884942] [tdb] Close table 'client0.tdb' Apr 26 12:01:42 192.168.122.209 [71853.075701] [tdb] Close table 'sessions0.tdb' Apr 26 12:01:45 192.168.122.209 [71856.255885] [tdb] Close table 'cache0.tdb' Apr 26 12:01:45 192.168.122.209 [71856.530856] [tdb] Close table 'filter0.tdb' Apr 26 12:01:45 192.168.122.209 [71856.531290] [tempesta fw] modules are stopped Apr 26 12:01:46 192.168.122.209 [71856.738716] [tempesta fw] exiting... Apr 26 12:01:46 192.168.122.209 [71856.868143] [tdb] Shutdown Tempesta DB Apr 26 12:01:46 192.168.122.209 [71857.233913] End test: cache.test_cache_control.ResponseMaxAgeNotCached2.test Apr 26 12:01:46 192.168.122.209 [71857.314805] Start test: cache.test_cache_control.ResponseMultipleNoCacheIgnore.test Apr 26 12:01:47 192.168.122.209 [71858.571539] [tdb] Start Tempesta DB Apr 26 12:01:47 192.168.122.209 [71858.694804] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:01:49 192.168.122.209 [71860.289699] [tempesta fw] Configuration processing is completed. Apr 26 12:01:49 192.168.122.209 [71860.342239] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:01:50 192.168.122.209 [71860.790256] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:01:50 192.168.122.209 [71860.817830] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:01:50 192.168.122.209 [71860.845763] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:01:50 192.168.122.209 [71860.897683] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:01:50 192.168.122.209 [71860.945628] [tempesta fw] Tempesta FW is ready Apr 26 12:01:50 192.168.122.209 [71861.597867] [tdb] Close table 'client0.tdb' Apr 26 12:01:51 192.168.122.209 [71861.794909] [tdb] Close table 'sessions0.tdb' Apr 26 12:01:54 192.168.122.209 [71864.975047] [tdb] Close table 'cache0.tdb' Apr 26 12:01:54 192.168.122.209 [71865.237282] [tdb] Close table 'filter0.tdb' Apr 26 12:01:54 192.168.122.209 [71865.237769] [tempesta fw] modules are stopped Apr 26 12:01:54 192.168.122.209 [71865.435569] [tempesta fw] exiting... Apr 26 12:01:54 192.168.122.209 [71865.552499] [tdb] Shutdown Tempesta DB Apr 26 12:01:55 192.168.122.209 [71865.982934] End test: cache.test_cache_control.ResponseMultipleNoCacheIgnore.test Apr 26 12:01:55 192.168.122.209 [71866.012737] Start test: cache.test_cache_control.ResponseMustRevalidateCached.test Apr 26 12:01:56 192.168.122.209 [71867.407989] [tdb] Start Tempesta DB Apr 26 12:01:56 192.168.122.209 [71867.534654] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:01:58 192.168.122.209 [71869.037803] [tempesta fw] Configuration processing is completed. Apr 26 12:01:58 192.168.122.209 [71869.100808] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:01:58 192.168.122.209 [71869.524361] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:01:58 192.168.122.209 [71869.551288] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:01:58 192.168.122.209 [71869.577125] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:01:58 192.168.122.209 [71869.621756] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:01:58 192.168.122.209 [71869.665717] [tempesta fw] Tempesta FW is ready Apr 26 12:01:59 192.168.122.209 [71870.296634] [tdb] Close table 'client0.tdb' Apr 26 12:01:59 192.168.122.209 [71870.485730] [tdb] Close table 'sessions0.tdb' Apr 26 12:02:02 192.168.122.209 [71873.662636] [tdb] Close table 'cache0.tdb' Apr 26 12:02:03 192.168.122.209 [71873.918397] [tdb] Close table 'filter0.tdb' Apr 26 12:02:03 192.168.122.209 [71873.918849] [tempesta fw] modules are stopped Apr 26 12:02:03 192.168.122.209 [71874.143325] [tempesta fw] exiting... Apr 26 12:02:03 192.168.122.209 [71874.264469] [tdb] Shutdown Tempesta DB Apr 26 12:02:03 192.168.122.209 [71874.678545] End test: cache.test_cache_control.ResponseMustRevalidateCached.test Apr 26 12:02:04 192.168.122.209 [71874.714368] Start test: cache.test_cache_control.ResponseMustRevalidateHalfIgnore.test Apr 26 12:02:05 192.168.122.209 [71876.012288] [tdb] Start Tempesta DB Apr 26 12:02:05 192.168.122.209 [71876.144657] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:02:07 192.168.122.209 [71877.709985] [tempesta fw] Configuration processing is completed. Apr 26 12:02:07 192.168.122.209 [71877.776145] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:02:07 192.168.122.209 [71878.195436] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:02:07 192.168.122.209 [71878.223297] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:02:07 192.168.122.209 [71878.251706] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:02:07 192.168.122.209 [71878.305836] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:02:07 192.168.122.209 [71878.345816] [tempesta fw] Tempesta FW is ready Apr 26 12:02:09 192.168.122.209 [71880.502286] [tdb] Close table 'client0.tdb' Apr 26 12:02:09 192.168.122.209 [71880.682953] [tdb] Close table 'sessions0.tdb' Apr 26 12:02:13 192.168.122.209 [71883.871757] [tdb] Close table 'cache0.tdb' Apr 26 12:02:13 192.168.122.209 [71884.145978] [tdb] Close table 'filter0.tdb' Apr 26 12:02:13 192.168.122.209 [71884.146428] [tempesta fw] modules are stopped Apr 26 12:02:13 192.168.122.209 [71884.350653] [tempesta fw] exiting... Apr 26 12:02:13 192.168.122.209 [71884.491902] [tdb] Shutdown Tempesta DB Apr 26 12:02:14 192.168.122.209 [71884.919986] End test: cache.test_cache_control.ResponseMustRevalidateHalfIgnore.test Apr 26 12:02:14 192.168.122.209 [71884.958392] Start test: cache.test_cache_control.ResponseMustRevalidateIgnore.test Apr 26 12:02:15 192.168.122.209 [71886.281312] [tdb] Start Tempesta DB Apr 26 12:02:15 192.168.122.209 [71886.415977] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:02:17 192.168.122.209 [71887.950068] [tempesta fw] Configuration processing is completed. Apr 26 12:02:17 192.168.122.209 [71888.006455] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:02:17 192.168.122.209 [71888.414103] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:02:17 192.168.122.209 [71888.447075] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:02:17 192.168.122.209 [71888.473143] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:02:17 192.168.122.209 [71888.517982] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:02:17 192.168.122.209 [71888.573919] [tempesta fw] Tempesta FW is ready Apr 26 12:02:20 192.168.122.209 [71891.227989] [tdb] Close table 'client0.tdb' Apr 26 12:02:20 192.168.122.209 [71891.414462] [tdb] Close table 'sessions0.tdb' Apr 26 12:02:23 192.168.122.209 [71894.619021] [tdb] Close table 'cache0.tdb' Apr 26 12:02:24 192.168.122.209 [71894.871852] [tdb] Close table 'filter0.tdb' Apr 26 12:02:24 192.168.122.209 [71894.872266] [tempesta fw] modules are stopped Apr 26 12:02:24 192.168.122.209 [71895.102961] [tempesta fw] exiting... Apr 26 12:02:24 192.168.122.209 [71895.220841] [tdb] Shutdown Tempesta DB Apr 26 12:02:24 192.168.122.209 [71895.568680] End test: cache.test_cache_control.ResponseMustRevalidateIgnore.test Apr 26 12:02:24 192.168.122.209 [71895.607821] Start test: cache.test_cache_control.ResponseMustRevalidateMultiIgnore.test Apr 26 12:02:26 192.168.122.209 [71896.798843] [tdb] Start Tempesta DB Apr 26 12:02:26 192.168.122.209 [71896.942122] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:02:27 192.168.122.209 [71898.434161] [tempesta fw] Configuration processing is completed. Apr 26 12:02:27 192.168.122.209 [71898.498982] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:02:28 192.168.122.209 [71898.971189] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:02:28 192.168.122.209 [71899.000986] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:02:28 192.168.122.209 [71899.029731] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:02:28 192.168.122.209 [71899.070106] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:02:28 192.168.122.209 [71899.110007] [tempesta fw] Tempesta FW is ready Apr 26 12:02:30 192.168.122.209 [71901.254497] [tdb] Close table 'client0.tdb' Apr 26 12:02:30 192.168.122.209 [71901.437546] [tdb] Close table 'sessions0.tdb' Apr 26 12:02:33 192.168.122.209 [71904.641032] [tdb] Close table 'cache0.tdb' Apr 26 12:02:34 192.168.122.209 [71904.912481] [tdb] Close table 'filter0.tdb' Apr 26 12:02:34 192.168.122.209 [71904.912921] [tempesta fw] modules are stopped Apr 26 12:02:34 192.168.122.209 [71905.115234] [tempesta fw] exiting... Apr 26 12:02:34 192.168.122.209 [71905.253888] [tdb] Shutdown Tempesta DB Apr 26 12:02:34 192.168.122.209 [71905.609249] End test: cache.test_cache_control.ResponseMustRevalidateMultiIgnore.test Apr 26 12:02:34 192.168.122.209 [71905.640906] Start test: cache.test_cache_control.ResponseMustRevalidateNotCached.test Apr 26 12:02:36 192.168.122.209 [71906.921235] [tdb] Start Tempesta DB Apr 26 12:02:36 192.168.122.209 [71907.084874] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:02:37 192.168.122.209 [71908.530218] [tempesta fw] Configuration processing is completed. Apr 26 12:02:37 192.168.122.209 [71908.583646] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:02:38 192.168.122.209 [71909.045875] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:02:38 192.168.122.209 [71909.075807] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:02:38 192.168.122.209 [71909.106501] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:02:38 192.168.122.209 [71909.146247] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:02:38 192.168.122.209 [71909.198132] [tempesta fw] Tempesta FW is ready Apr 26 12:02:41 192.168.122.209 [71911.852986] [tdb] Close table 'client0.tdb' Apr 26 12:02:41 192.168.122.209 [71912.035675] [tdb] Close table 'sessions0.tdb' Apr 26 12:02:44 192.168.122.209 [71915.163644] [tdb] Close table 'cache0.tdb' Apr 26 12:02:44 192.168.122.209 [71915.410279] [tdb] Close table 'filter0.tdb' Apr 26 12:02:44 192.168.122.209 [71915.410934] [tempesta fw] modules are stopped Apr 26 12:02:44 192.168.122.209 [71915.647659] [tempesta fw] exiting... Apr 26 12:02:45 192.168.122.209 [71915.775274] [tdb] Shutdown Tempesta DB Apr 26 12:02:45 192.168.122.209 [71916.143011] End test: cache.test_cache_control.ResponseMustRevalidateNotCached.test Apr 26 12:02:45 192.168.122.209 [71916.176286] Start test: cache.test_cache_control.ResponseMustRevalidateStaleCached.test Apr 26 12:02:46 192.168.122.209 [71917.608354] [tdb] Start Tempesta DB Apr 26 12:02:47 192.168.122.209 [71917.761061] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:02:48 192.168.122.209 [71919.282372] [tempesta fw] Configuration processing is completed. Apr 26 12:02:48 192.168.122.209 [71919.344668] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:02:49 192.168.122.209 [71919.810884] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:02:49 192.168.122.209 [71919.839552] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:02:49 192.168.122.209 [71919.869070] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:02:49 192.168.122.209 [71919.922342] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:02:49 192.168.122.209 [71919.962254] [tempesta fw] Tempesta FW is ready Apr 26 12:02:49 192.168.122.209 [71920.632609] [tdb] Close table 'client0.tdb' Apr 26 12:02:50 192.168.122.209 [71920.821850] [tdb] Close table 'sessions0.tdb' Apr 26 12:02:53 192.168.122.209 [71924.019931] [tdb] Close table 'cache0.tdb' Apr 26 12:02:53 192.168.122.209 [71924.269095] [tdb] Close table 'filter0.tdb' Apr 26 12:02:53 192.168.122.209 [71924.269530] [tempesta fw] modules are stopped Apr 26 12:02:53 192.168.122.209 [71924.494354] [tempesta fw] exiting... Apr 26 12:02:53 192.168.122.209 [71924.627146] [tdb] Shutdown Tempesta DB Apr 26 12:02:54 192.168.122.209 [71925.009286] End test: cache.test_cache_control.ResponseMustRevalidateStaleCached.test Apr 26 12:02:54 192.168.122.209 [71925.034925] Start test: cache.test_cache_control.ResponseMustRevalidateStaleIgnore.test Apr 26 12:02:55 192.168.122.209 [71926.372325] [tdb] Start Tempesta DB Apr 26 12:02:55 192.168.122.209 [71926.507535] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:02:57 192.168.122.209 [71928.106541] [tempesta fw] Configuration processing is completed. Apr 26 12:02:57 192.168.122.209 [71928.167548] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:02:57 192.168.122.209 [71928.609607] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:02:57 192.168.122.209 [71928.637441] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:02:57 192.168.122.209 [71928.664389] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:02:57 192.168.122.209 [71928.706432] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:02:58 192.168.122.209 [71928.754366] [tempesta fw] Tempesta FW is ready Apr 26 12:03:00 192.168.122.209 [71930.922355] [tdb] Close table 'client0.tdb' Apr 26 12:03:00 192.168.122.209 [71931.131631] [tdb] Close table 'sessions0.tdb' Apr 26 12:03:03 192.168.122.209 [71934.348871] [tdb] Close table 'cache0.tdb' Apr 26 12:03:03 192.168.122.209 [71934.589450] [tdb] Close table 'filter0.tdb' Apr 26 12:03:03 192.168.122.209 [71934.589926] [tempesta fw] modules are stopped Apr 26 12:03:04 192.168.122.209 [71934.805356] [tempesta fw] exiting... Apr 26 12:03:04 192.168.122.209 [71934.933983] [tdb] Shutdown Tempesta DB Apr 26 12:03:04 192.168.122.209 [71935.375659] End test: cache.test_cache_control.ResponseMustRevalidateStaleIgnore.test Apr 26 12:03:04 192.168.122.209 [71935.413426] Start test: cache.test_cache_control.ResponseMustRevalidateStaleNotCached.test Apr 26 12:03:05 192.168.122.209 [71936.700198] [tdb] Start Tempesta DB Apr 26 12:03:06 192.168.122.209 [71936.850165] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:03:07 192.168.122.209 [71938.322585] [tempesta fw] Configuration processing is completed. Apr 26 12:03:07 192.168.122.209 [71938.375232] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:03:08 192.168.122.209 [71938.780466] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:03:08 192.168.122.209 [71938.807356] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:03:08 192.168.122.209 [71938.833119] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:03:08 192.168.122.209 [71938.874546] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:03:08 192.168.122.209 [71938.918466] [tempesta fw] Tempesta FW is ready Apr 26 12:03:10 192.168.122.209 [71941.545493] [tdb] Close table 'client0.tdb' Apr 26 12:03:11 192.168.122.209 [71941.752922] [tdb] Close table 'sessions0.tdb' Apr 26 12:03:14 192.168.122.209 [71944.896917] [tdb] Close table 'cache0.tdb' Apr 26 12:03:14 192.168.122.209 [71945.148082] [tdb] Close table 'filter0.tdb' Apr 26 12:03:14 192.168.122.209 [71945.148571] [tempesta fw] modules are stopped Apr 26 12:03:14 192.168.122.209 [71945.419967] [tempesta fw] exiting... Apr 26 12:03:14 192.168.122.209 [71945.547675] [tdb] Shutdown Tempesta DB Apr 26 12:03:15 192.168.122.209 [71945.929937] End test: cache.test_cache_control.ResponseMustRevalidateStaleNotCached.test Apr 26 12:03:15 192.168.122.209 [71945.958911] Start test: cache.test_cache_control.ResponseNoCache.test Apr 26 12:03:16 192.168.122.209 [71947.356045] [tdb] Start Tempesta DB Apr 26 12:03:16 192.168.122.209 [71947.478797] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:03:18 192.168.122.209 [71949.042745] [tempesta fw] Configuration processing is completed. Apr 26 12:03:18 192.168.122.209 [71949.099919] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:03:18 192.168.122.209 [71949.526193] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:03:18 192.168.122.209 [71949.553275] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:03:18 192.168.122.209 [71949.578547] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:03:18 192.168.122.209 [71949.654677] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:03:18 192.168.122.209 [71949.694609] [tempesta fw] Tempesta FW is ready Apr 26 12:03:19 192.168.122.209 [71950.329766] [tdb] Close table 'client0.tdb' Apr 26 12:03:19 192.168.122.209 [71950.522265] [tdb] Close table 'sessions0.tdb' Apr 26 12:03:22 192.168.122.209 [71953.687764] [tdb] Close table 'cache0.tdb' Apr 26 12:03:23 192.168.122.209 [71953.934447] [tdb] Close table 'filter0.tdb' Apr 26 12:03:23 192.168.122.209 [71953.934918] [tempesta fw] modules are stopped Apr 26 12:03:23 192.168.122.209 [71954.119273] [tempesta fw] exiting... Apr 26 12:03:23 192.168.122.209 [71954.267307] [tdb] Shutdown Tempesta DB Apr 26 12:03:23 192.168.122.209 [71954.644750] End test: cache.test_cache_control.ResponseNoCache.test Apr 26 12:03:23 192.168.122.209 [71954.680528] Start test: cache.test_cache_control.ResponseNoCacheIgnore.test Apr 26 12:03:25 192.168.122.209 [71956.040468] [tdb] Start Tempesta DB Apr 26 12:03:25 192.168.122.209 [71956.173553] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:03:26 192.168.122.209 [71957.671095] [tempesta fw] Configuration processing is completed. Apr 26 12:03:27 192.168.122.209 [71957.727594] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:03:27 192.168.122.209 [71958.285124] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:03:27 192.168.122.209 [71958.319615] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:03:27 192.168.122.209 [71958.353657] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:03:27 192.168.122.209 [71958.402762] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:03:27 192.168.122.209 [71958.446705] [tempesta fw] Tempesta FW is ready Apr 26 12:03:28 192.168.122.209 [71959.121355] [tdb] Close table 'client0.tdb' Apr 26 12:03:28 192.168.122.209 [71959.304786] [tdb] Close table 'sessions0.tdb' Apr 26 12:03:31 192.168.122.209 [71962.454151] [tdb] Close table 'cache0.tdb' Apr 26 12:03:32 192.168.122.209 [71962.746836] [tdb] Close table 'filter0.tdb' Apr 26 12:03:32 192.168.122.209 [71962.747281] [tempesta fw] modules are stopped Apr 26 12:03:32 192.168.122.209 [71962.942795] [tempesta fw] exiting... Apr 26 12:03:32 192.168.122.209 [71963.044367] [tdb] Shutdown Tempesta DB Apr 26 12:03:32 192.168.122.209 [71963.460514] End test: cache.test_cache_control.ResponseNoCacheIgnore.test Apr 26 12:03:32 192.168.122.209 [71963.493516] Start test: cache.test_cache_control.ResponseNoCacheIgnoreMulti.test Apr 26 12:03:34 192.168.122.209 [71964.773874] [tdb] Start Tempesta DB Apr 26 12:03:34 192.168.122.209 [71964.910983] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:03:35 192.168.122.209 [71966.458972] [tempesta fw] Configuration processing is completed. Apr 26 12:03:35 192.168.122.209 [71966.519297] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:03:36 192.168.122.209 [71966.962903] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:03:36 192.168.122.209 [71966.990927] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:03:36 192.168.122.209 [71967.018792] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:03:36 192.168.122.209 [71967.070909] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:03:36 192.168.122.209 [71967.114843] [tempesta fw] Tempesta FW is ready Apr 26 12:03:37 192.168.122.209 [71967.767263] [tdb] Close table 'client0.tdb' Apr 26 12:03:37 192.168.122.209 [71967.947827] [tdb] Close table 'sessions0.tdb' Apr 26 12:03:40 192.168.122.209 [71971.118979] [tdb] Close table 'cache0.tdb' Apr 26 12:03:40 192.168.122.209 [71971.360444] [tdb] Close table 'filter0.tdb' Apr 26 12:03:40 192.168.122.209 [71971.360845] [tempesta fw] modules are stopped Apr 26 12:03:40 192.168.122.209 [71971.550459] [tempesta fw] exiting... Apr 26 12:03:41 192.168.122.209 [71971.717236] [tdb] Shutdown Tempesta DB Apr 26 12:03:41 192.168.122.209 [71972.141876] End test: cache.test_cache_control.ResponseNoCacheIgnoreMulti.test Apr 26 12:03:41 192.168.122.209 [71972.179019] Start test: cache.test_cache_control.ResponseNoStore.test Apr 26 12:03:42 192.168.122.209 [71973.494553] [tdb] Start Tempesta DB Apr 26 12:03:42 192.168.122.209 [71973.630628] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:03:44 192.168.122.209 [71975.091325] [tempesta fw] Configuration processing is completed. Apr 26 12:03:44 192.168.122.209 [71975.142223] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:03:44 192.168.122.209 [71975.563190] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:03:44 192.168.122.209 [71975.590132] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:03:44 192.168.122.209 [71975.615853] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:03:44 192.168.122.209 [71975.658947] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:03:44 192.168.122.209 [71975.706897] [tempesta fw] Tempesta FW is ready Apr 26 12:03:45 192.168.122.209 [71976.345748] [tdb] Close table 'client0.tdb' Apr 26 12:03:45 192.168.122.209 [71976.535224] [tdb] Close table 'sessions0.tdb' Apr 26 12:03:48 192.168.122.209 [71979.654628] [tdb] Close table 'cache0.tdb' Apr 26 12:03:49 192.168.122.209 [71979.914861] [tdb] Close table 'filter0.tdb' Apr 26 12:03:49 192.168.122.209 [71979.915292] [tempesta fw] modules are stopped Apr 26 12:03:49 192.168.122.209 [71980.122988] [tempesta fw] exiting... Apr 26 12:03:49 192.168.122.209 [71980.277232] [tdb] Shutdown Tempesta DB Apr 26 12:03:49 192.168.122.209 [71980.660205] End test: cache.test_cache_control.ResponseNoStore.test Apr 26 12:03:50 192.168.122.209 [71980.746493] Start test: cache.test_cache_control.ResponsePrivate.test Apr 26 12:03:51 192.168.122.209 [71982.042136] [tdb] Start Tempesta DB Apr 26 12:03:51 192.168.122.209 [71982.182630] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:03:53 192.168.122.209 [71983.715134] [tempesta fw] Configuration processing is completed. Apr 26 12:03:53 192.168.122.209 [71983.771307] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:03:53 192.168.122.209 [71984.196731] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:03:53 192.168.122.209 [71984.232941] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:03:53 192.168.122.209 [71984.258271] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:03:53 192.168.122.209 [71984.299041] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:03:53 192.168.122.209 [71984.346992] [tempesta fw] Tempesta FW is ready Apr 26 12:03:54 192.168.122.209 [71985.004739] [tdb] Close table 'client0.tdb' Apr 26 12:03:54 192.168.122.209 [71985.167232] [tdb] Close table 'sessions0.tdb' Apr 26 12:03:57 192.168.122.209 [71988.356810] [tdb] Close table 'cache0.tdb' Apr 26 12:03:57 192.168.122.209 [71988.604109] [tdb] Close table 'filter0.tdb' Apr 26 12:03:57 192.168.122.209 [71988.604529] [tempesta fw] modules are stopped Apr 26 12:03:58 192.168.122.209 [71988.799513] [tempesta fw] exiting... Apr 26 12:03:58 192.168.122.209 [71988.939967] [tdb] Shutdown Tempesta DB Apr 26 12:03:58 192.168.122.209 [71989.343985] End test: cache.test_cache_control.ResponsePrivate.test Apr 26 12:03:58 192.168.122.209 [71989.374917] Start test: cache.test_cache_control.ResponseProxyRevalidateIgnore.test Apr 26 12:03:59 192.168.122.209 [71990.673211] [tdb] Start Tempesta DB Apr 26 12:04:00 192.168.122.209 [71990.813082] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:04:01 192.168.122.209 [71992.323183] [tempesta fw] Configuration processing is completed. Apr 26 12:04:01 192.168.122.209 [71992.374507] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:04:02 192.168.122.209 [71992.785473] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:04:02 192.168.122.209 [71992.810623] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:04:02 192.168.122.209 [71992.844307] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:04:02 192.168.122.209 [71992.895164] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:04:02 192.168.122.209 [71992.959105] [tempesta fw] Tempesta FW is ready Apr 26 12:04:04 192.168.122.209 [71995.541535] [tdb] Close table 'client0.tdb' Apr 26 12:04:05 192.168.122.209 [71995.741687] [tdb] Close table 'sessions0.tdb' Apr 26 12:04:08 192.168.122.209 [71998.903956] [tdb] Close table 'cache0.tdb' Apr 26 12:04:08 192.168.122.209 [71999.151321] [tdb] Close table 'filter0.tdb' Apr 26 12:04:08 192.168.122.209 [71999.151746] [tempesta fw] modules are stopped Apr 26 12:04:08 192.168.122.209 [71999.336583] [tempesta fw] exiting... Apr 26 12:04:08 192.168.122.209 [71999.496017] [tdb] Shutdown Tempesta DB Apr 26 12:04:09 192.168.122.209 [71999.930668] End test: cache.test_cache_control.ResponseProxyRevalidateIgnore.test Apr 26 12:04:09 192.168.122.209 [71999.976824] Start test: cache.test_cache_control.ResponseProxyRevalidateNotCached.test Apr 26 12:04:10 192.168.122.209 [72001.249171] [tdb] Start Tempesta DB Apr 26 12:04:10 192.168.122.209 [72001.379566] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:04:12 192.168.122.209 [72002.803315] [tempesta fw] Configuration processing is completed. Apr 26 12:04:12 192.168.122.209 [72002.854571] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:04:12 192.168.122.209 [72003.275538] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:04:12 192.168.122.209 [72003.302357] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:04:12 192.168.122.209 [72003.328968] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:04:12 192.168.122.209 [72003.371273] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:04:12 192.168.122.209 [72003.423216] [tempesta fw] Tempesta FW is ready Apr 26 12:04:15 192.168.122.209 [72006.071902] [tdb] Close table 'client0.tdb' Apr 26 12:04:15 192.168.122.209 [72006.260110] [tdb] Close table 'sessions0.tdb' Apr 26 12:04:18 192.168.122.209 [72009.403116] [tdb] Close table 'cache0.tdb' Apr 26 12:04:18 192.168.122.209 [72009.651732] [tdb] Close table 'filter0.tdb' Apr 26 12:04:18 192.168.122.209 [72009.652133] [tempesta fw] modules are stopped Apr 26 12:04:19 192.168.122.209 [72009.907412] [tempesta fw] exiting... Apr 26 12:04:19 192.168.122.209 [72010.023537] [tdb] Shutdown Tempesta DB Apr 26 12:04:19 192.168.122.209 [72010.437227] End test: cache.test_cache_control.ResponseProxyRevalidateNotCached.test Apr 26 12:04:19 192.168.122.209 [72010.477189] Start test: cache.test_cache_control.ResponseProxyRevalidateStaleIgnore.test Apr 26 12:04:21 192.168.122.209 [72011.784496] [tdb] Start Tempesta DB Apr 26 12:04:21 192.168.122.209 [72011.917693] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:04:22 192.168.122.209 [72013.431572] [tempesta fw] Configuration processing is completed. Apr 26 12:04:22 192.168.122.209 [72013.489611] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:04:23 192.168.122.209 [72013.901438] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:04:23 192.168.122.209 [72013.928889] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:04:23 192.168.122.209 [72013.955410] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:04:23 192.168.122.209 [72013.995398] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:04:23 192.168.122.209 [72014.039420] [tempesta fw] Tempesta FW is ready Apr 26 12:04:26 192.168.122.209 [72016.714963] [tdb] Close table 'client0.tdb' Apr 26 12:04:26 192.168.122.209 [72016.908313] [tdb] Close table 'sessions0.tdb' Apr 26 12:04:29 192.168.122.209 [72020.092538] [tdb] Close table 'cache0.tdb' Apr 26 12:04:29 192.168.122.209 [72020.336840] [tdb] Close table 'filter0.tdb' Apr 26 12:04:29 192.168.122.209 [72020.337274] [tempesta fw] modules are stopped Apr 26 12:04:29 192.168.122.209 [72020.515641] [tempesta fw] exiting... Apr 26 12:04:29 192.168.122.209 [72020.627342] [tdb] Shutdown Tempesta DB Apr 26 12:04:30 192.168.122.209 [72020.994255] End test: cache.test_cache_control.ResponseProxyRevalidateStaleIgnore.test Apr 26 12:04:30 192.168.122.209 [72021.036942] Start test: cache.test_cache_control.ResponseProxyRevalidateStaleNotCached.test Apr 26 12:04:31 192.168.122.209 [72022.380215] [tdb] Start Tempesta DB Apr 26 12:04:31 192.168.122.209 [72022.497584] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:04:33 192.168.122.209 [72023.931623] [tempesta fw] Configuration processing is completed. Apr 26 12:04:33 192.168.122.209 [72024.004863] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:04:33 192.168.122.209 [72024.434306] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:04:33 192.168.122.209 [72024.473256] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:04:33 192.168.122.209 [72024.499225] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:04:33 192.168.122.209 [72024.539516] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:04:33 192.168.122.209 [72024.583404] [tempesta fw] Tempesta FW is ready Apr 26 12:04:36 192.168.122.209 [72027.256957] [tdb] Close table 'client0.tdb' Apr 26 12:04:36 192.168.122.209 [72027.444943] [tdb] Close table 'sessions0.tdb' Apr 26 12:04:39 192.168.122.209 [72030.572395] [tdb] Close table 'cache0.tdb' Apr 26 12:04:40 192.168.122.209 [72030.818530] [tdb] Close table 'filter0.tdb' Apr 26 12:04:40 192.168.122.209 [72030.818960] [tempesta fw] modules are stopped Apr 26 12:04:40 192.168.122.209 [72031.029773] [tempesta fw] exiting... Apr 26 12:04:40 192.168.122.209 [72031.172120] [tdb] Shutdown Tempesta DB Apr 26 12:04:40 192.168.122.209 [72031.582544] End test: cache.test_cache_control.ResponseProxyRevalidateStaleNotCached.test Apr 26 12:04:40 192.168.122.209 [72031.613184] Start test: cache.test_cache_control.ResponsePublicCached.test Apr 26 12:04:42 192.168.122.209 [72032.892558] [tdb] Start Tempesta DB Apr 26 12:04:42 192.168.122.209 [72033.018703] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:04:43 192.168.122.209 [72034.519720] [tempesta fw] Configuration processing is completed. Apr 26 12:04:43 192.168.122.209 [72034.569640] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:04:44 192.168.122.209 [72035.004282] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:04:44 192.168.122.209 [72035.030653] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:04:44 192.168.122.209 [72035.056524] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:04:44 192.168.122.209 [72035.095636] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:04:44 192.168.122.209 [72035.135588] [tempesta fw] Tempesta FW is ready Apr 26 12:04:45 192.168.122.209 [72035.793259] [tdb] Close table 'client0.tdb' Apr 26 12:04:45 192.168.122.209 [72035.981363] [tdb] Close table 'sessions0.tdb' Apr 26 12:04:48 192.168.122.209 [72039.190775] [tdb] Close table 'cache0.tdb' Apr 26 12:04:48 192.168.122.209 [72039.473506] [tdb] Close table 'filter0.tdb' Apr 26 12:04:48 192.168.122.209 [72039.473900] [tempesta fw] modules are stopped Apr 26 12:04:48 192.168.122.209 [72039.669584] [tempesta fw] exiting... Apr 26 12:04:49 192.168.122.209 [72039.818733] [tdb] Shutdown Tempesta DB Apr 26 12:04:49 192.168.122.209 [72040.209122] End test: cache.test_cache_control.ResponsePublicCached.test Apr 26 12:04:49 192.168.122.209 [72040.245655] Start test: cache.test_cache_control.ResponsePublicCached2.test Apr 26 12:04:50 192.168.122.209 [72041.518882] [tdb] Start Tempesta DB Apr 26 12:04:50 192.168.122.209 [72041.649270] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:04:52 192.168.122.209 [72043.151777] [tempesta fw] Configuration processing is completed. Apr 26 12:04:52 192.168.122.209 [72043.206014] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:04:52 192.168.122.209 [72043.610148] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:04:52 192.168.122.209 [72043.636107] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:04:52 192.168.122.209 [72043.665614] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:04:52 192.168.122.209 [72043.707752] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:04:53 192.168.122.209 [72043.747705] [tempesta fw] Tempesta FW is ready Apr 26 12:04:53 192.168.122.209 [72044.384345] [tdb] Close table 'client0.tdb' Apr 26 12:04:53 192.168.122.209 [72044.564636] [tdb] Close table 'sessions0.tdb' Apr 26 12:04:56 192.168.122.209 [72047.711635] [tdb] Close table 'cache0.tdb' Apr 26 12:04:57 192.168.122.209 [72047.967331] [tdb] Close table 'filter0.tdb' Apr 26 12:04:57 192.168.122.209 [72047.967774] [tempesta fw] modules are stopped Apr 26 12:04:57 192.168.122.209 [72048.160865] [tempesta fw] exiting... Apr 26 12:04:57 192.168.122.209 [72048.261533] [tdb] Shutdown Tempesta DB Apr 26 12:04:57 192.168.122.209 [72048.659998] End test: cache.test_cache_control.ResponsePublicCached2.test Apr 26 12:04:57 192.168.122.209 [72048.693705] Start test: cache.test_cache_control.ResponsePublicIgnore.test Apr 26 12:04:59 192.168.122.209 [72049.928812] [tdb] Start Tempesta DB Apr 26 12:04:59 192.168.122.209 [72050.057922] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:05:00 192.168.122.209 [72051.603903] [tempesta fw] Configuration processing is completed. Apr 26 12:05:00 192.168.122.209 [72051.655674] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:05:01 192.168.122.209 [72052.081201] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:05:01 192.168.122.209 [72052.118322] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:05:01 192.168.122.209 [72052.143969] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:05:01 192.168.122.209 [72052.219842] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:05:01 192.168.122.209 [72052.259787] [tempesta fw] Tempesta FW is ready Apr 26 12:05:02 192.168.122.209 [72052.921527] [tdb] Close table 'client0.tdb' Apr 26 12:05:02 192.168.122.209 [72053.123443] [tdb] Close table 'sessions0.tdb' Apr 26 12:05:05 192.168.122.209 [72056.327815] [tdb] Close table 'cache0.tdb' Apr 26 12:05:05 192.168.122.209 [72056.578809] [tdb] Close table 'filter0.tdb' Apr 26 12:05:05 192.168.122.209 [72056.579259] [tempesta fw] modules are stopped Apr 26 12:05:06 192.168.122.209 [72056.743759] [tempesta fw] exiting... Apr 26 12:05:06 192.168.122.209 [72056.853448] [tdb] Shutdown Tempesta DB Apr 26 12:05:06 192.168.122.209 [72057.300651] End test: cache.test_cache_control.ResponsePublicIgnore.test Apr 26 12:05:06 192.168.122.209 [72057.329892] Start test: cache.test_cache_control.ResponsePublicIgnore2.test Apr 26 12:05:07 192.168.122.209 [72058.619631] [tdb] Start Tempesta DB Apr 26 12:05:08 192.168.122.209 [72058.757810] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:05:09 192.168.122.209 [72060.324020] [tempesta fw] Configuration processing is completed. Apr 26 12:05:09 192.168.122.209 [72060.390662] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:05:10 192.168.122.209 [72060.811657] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:05:10 192.168.122.209 [72060.838538] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:05:10 192.168.122.209 [72060.865901] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:05:10 192.168.122.209 [72060.903945] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:05:10 192.168.122.209 [72060.955894] [tempesta fw] Tempesta FW is ready Apr 26 12:05:10 192.168.122.209 [72061.613170] [tdb] Close table 'client0.tdb' Apr 26 12:05:11 192.168.122.209 [72061.805934] [tdb] Close table 'sessions0.tdb' Apr 26 12:05:14 192.168.122.209 [72064.989052] [tdb] Close table 'cache0.tdb' Apr 26 12:05:14 192.168.122.209 [72065.243901] [tdb] Close table 'filter0.tdb' Apr 26 12:05:14 192.168.122.209 [72065.244341] [tempesta fw] modules are stopped Apr 26 12:05:14 192.168.122.209 [72065.424198] [tempesta fw] exiting... Apr 26 12:05:14 192.168.122.209 [72065.546163] [tdb] Shutdown Tempesta DB Apr 26 12:05:15 192.168.122.209 [72065.908235] End test: cache.test_cache_control.ResponsePublicIgnore2.test Apr 26 12:05:15 192.168.122.209 [72065.943034] Start test: cache.test_cache_control.ResponsePublicNotCached.test Apr 26 12:05:16 192.168.122.209 [72067.248751] [tdb] Start Tempesta DB Apr 26 12:05:16 192.168.122.209 [72067.378288] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:05:18 192.168.122.209 [72068.816114] [tempesta fw] Configuration processing is completed. Apr 26 12:05:18 192.168.122.209 [72068.887568] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:05:18 192.168.122.209 [72069.299156] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:05:18 192.168.122.209 [72069.325504] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:05:18 192.168.122.209 [72069.351809] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:05:18 192.168.122.209 [72069.391979] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:05:18 192.168.122.209 [72069.439987] [tempesta fw] Tempesta FW is ready Apr 26 12:05:19 192.168.122.209 [72070.040028] [tdb] Close table 'client0.tdb' Apr 26 12:05:19 192.168.122.209 [72070.232866] [tdb] Close table 'sessions0.tdb' Apr 26 12:05:22 192.168.122.209 [72073.396157] [tdb] Close table 'cache0.tdb' Apr 26 12:05:22 192.168.122.209 [72073.657457] [tdb] Close table 'filter0.tdb' Apr 26 12:05:22 192.168.122.209 [72073.657863] [tempesta fw] modules are stopped Apr 26 12:05:23 192.168.122.209 [72073.850061] [tempesta fw] exiting... Apr 26 12:05:23 192.168.122.209 [72073.969455] [tdb] Shutdown Tempesta DB Apr 26 12:05:23 192.168.122.209 [72074.379418] End test: cache.test_cache_control.ResponsePublicNotCached.test Apr 26 12:05:23 192.168.122.209 [72074.408788] Start test: cache.test_cache_control.ResponseSMaxageCached.test Apr 26 12:05:25 192.168.122.209 [72075.725394] [tdb] Start Tempesta DB Apr 26 12:05:25 192.168.122.209 [72075.847105] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:05:26 192.168.122.209 [72077.420211] [tempesta fw] Configuration processing is completed. Apr 26 12:05:26 192.168.122.209 [72077.476476] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:05:27 192.168.122.209 [72077.899126] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:05:27 192.168.122.209 [72077.925779] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:05:27 192.168.122.209 [72077.951330] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:05:27 192.168.122.209 [72077.992139] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:05:27 192.168.122.209 [72078.032117] [tempesta fw] Tempesta FW is ready Apr 26 12:05:27 192.168.122.209 [72078.685868] [tdb] Close table 'client0.tdb' Apr 26 12:05:28 192.168.122.209 [72078.881496] [tdb] Close table 'sessions0.tdb' Apr 26 12:05:31 192.168.122.209 [72082.055299] [tdb] Close table 'cache0.tdb' Apr 26 12:05:31 192.168.122.209 [72082.309449] [tdb] Close table 'filter0.tdb' Apr 26 12:05:31 192.168.122.209 [72082.309878] [tempesta fw] modules are stopped Apr 26 12:05:31 192.168.122.209 [72082.524018] [tempesta fw] exiting... Apr 26 12:05:31 192.168.122.209 [72082.670558] [tdb] Shutdown Tempesta DB Apr 26 12:05:32 192.168.122.209 [72083.058273] End test: cache.test_cache_control.ResponseSMaxageCached.test Apr 26 12:05:32 192.168.122.209 [72083.096627] Start test: cache.test_cache_control.ResponseSMaxageIgnore.test Apr 26 12:05:33 192.168.122.209 [72084.440342] [tdb] Start Tempesta DB Apr 26 12:05:33 192.168.122.209 [72084.566421] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:05:35 192.168.122.209 [72086.120312] [tempesta fw] Configuration processing is completed. Apr 26 12:05:35 192.168.122.209 [72086.182959] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:05:35 192.168.122.209 [72086.621164] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:05:35 192.168.122.209 [72086.647650] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:05:35 192.168.122.209 [72086.673528] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:05:36 192.168.122.209 [72086.716249] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:05:36 192.168.122.209 [72086.764216] [tempesta fw] Tempesta FW is ready Apr 26 12:05:38 192.168.122.209 [72088.946868] [tdb] Close table 'client0.tdb' Apr 26 12:05:38 192.168.122.209 [72089.127243] [tdb] Close table 'sessions0.tdb' Apr 26 12:05:41 192.168.122.209 [72092.263585] [tdb] Close table 'cache0.tdb' Apr 26 12:05:41 192.168.122.209 [72092.501571] [tdb] Close table 'filter0.tdb' Apr 26 12:05:41 192.168.122.209 [72092.501991] [tempesta fw] modules are stopped Apr 26 12:05:41 192.168.122.209 [72092.693978] [tempesta fw] exiting... Apr 26 12:05:42 192.168.122.209 [72092.858066] [tdb] Shutdown Tempesta DB Apr 26 12:05:42 192.168.122.209 [72093.278129] End test: cache.test_cache_control.ResponseSMaxageIgnore.test Apr 26 12:05:42 192.168.122.209 [72093.317043] Start test: cache.test_cache_control.ResponseSMaxageMaxAgeIgnore.test Apr 26 12:05:43 192.168.122.209 [72094.636830] [tdb] Start Tempesta DB Apr 26 12:05:44 192.168.122.209 [72094.774413] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:05:45 192.168.122.209 [72096.304418] [tempesta fw] Configuration processing is completed. Apr 26 12:05:45 192.168.122.209 [72096.363287] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:05:46 192.168.122.209 [72096.804201] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:05:46 192.168.122.209 [72096.831802] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:05:46 192.168.122.209 [72096.859704] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:05:46 192.168.122.209 [72096.900384] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:05:46 192.168.122.209 [72096.956378] [tempesta fw] Tempesta FW is ready Apr 26 12:05:48 192.168.122.209 [72099.135295] [tdb] Close table 'client0.tdb' Apr 26 12:05:48 192.168.122.209 [72099.332273] [tdb] Close table 'sessions0.tdb' Apr 26 12:05:51 192.168.122.209 [72102.481824] [tdb] Close table 'cache0.tdb' Apr 26 12:05:52 192.168.122.209 [72102.737984] [tdb] Close table 'filter0.tdb' Apr 26 12:05:52 192.168.122.209 [72102.738391] [tempesta fw] modules are stopped Apr 26 12:05:52 192.168.122.209 [72102.930410] [tempesta fw] exiting... Apr 26 12:05:52 192.168.122.209 [72103.038814] [tdb] Shutdown Tempesta DB Apr 26 12:05:52 192.168.122.209 [72103.410062] End test: cache.test_cache_control.ResponseSMaxageMaxAgeIgnore.test Apr 26 12:05:52 192.168.122.209 [72103.443878] Start test: cache.test_cache_control.ResponseSMaxageMaxAgeNotCached.test Apr 26 12:05:54 192.168.122.209 [72104.858375] [tdb] Start Tempesta DB Apr 26 12:05:54 192.168.122.209 [72104.990814] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:05:55 192.168.122.209 [72106.552553] [tempesta fw] Configuration processing is completed. Apr 26 12:05:55 192.168.122.209 [72106.611920] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:05:56 192.168.122.209 [72107.036230] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:05:56 192.168.122.209 [72107.062935] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:05:56 192.168.122.209 [72107.090367] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:05:56 192.168.122.209 [72107.132495] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:05:56 192.168.122.209 [72107.172459] [tempesta fw] Tempesta FW is ready Apr 26 12:05:59 192.168.122.209 [72109.831606] [tdb] Close table 'client0.tdb' Apr 26 12:05:59 192.168.122.209 [72109.994172] [tdb] Close table 'sessions0.tdb' Apr 26 12:06:02 192.168.122.209 [72113.207553] [tdb] Close table 'cache0.tdb' Apr 26 12:06:02 192.168.122.209 [72113.473231] [tdb] Close table 'filter0.tdb' Apr 26 12:06:02 192.168.122.209 [72113.473669] [tempesta fw] modules are stopped Apr 26 12:06:02 192.168.122.209 [72113.673279] [tempesta fw] exiting... Apr 26 12:06:03 192.168.122.209 [72113.794608] [tdb] Shutdown Tempesta DB Apr 26 12:06:03 192.168.122.209 [72114.257348] End test: cache.test_cache_control.ResponseSMaxageMaxAgeNotCached.test Apr 26 12:06:03 192.168.122.209 [72114.283024] Start test: cache.test_cache_control.ResponseSMaxageNotCached.test Apr 26 12:06:04 192.168.122.209 [72115.580664] [tdb] Start Tempesta DB Apr 26 12:06:04 192.168.122.209 [72115.707524] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:06:06 192.168.122.209 [72117.268925] [tempesta fw] Configuration processing is completed. Apr 26 12:06:06 192.168.122.209 [72117.327463] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:06:07 192.168.122.209 [72117.779004] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:06:07 192.168.122.209 [72117.807523] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:06:07 192.168.122.209 [72117.835887] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:06:07 192.168.122.209 [72117.880553] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:06:07 192.168.122.209 [72117.924572] [tempesta fw] Tempesta FW is ready Apr 26 12:06:09 192.168.122.209 [72120.592302] [tdb] Close table 'client0.tdb' Apr 26 12:06:10 192.168.122.209 [72120.782401] [tdb] Close table 'sessions0.tdb' Apr 26 12:06:13 192.168.122.209 [72124.030893] [tdb] Close table 'cache0.tdb' Apr 26 12:06:13 192.168.122.209 [72124.258061] [tdb] Close table 'filter0.tdb' Apr 26 12:06:13 192.168.122.209 [72124.258513] [tempesta fw] modules are stopped Apr 26 12:06:13 192.168.122.209 [72124.454031] [tempesta fw] exiting... Apr 26 12:06:13 192.168.122.209 [72124.580740] [tdb] Shutdown Tempesta DB Apr 26 12:06:14 192.168.122.209 [72124.971000] End test: cache.test_cache_control.ResponseSMaxageNotCached.test Apr 26 12:06:14 192.168.122.209 [72125.002448] Start test: cache.test_cache_control.ResponseSMaxageNotCached2.test Apr 26 12:06:15 192.168.122.209 [72126.375430] [tdb] Start Tempesta DB Apr 26 12:06:15 192.168.122.209 [72126.523850] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:06:17 192.168.122.209 [72128.020796] [tempesta fw] Configuration processing is completed. Apr 26 12:06:17 192.168.122.209 [72128.080334] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:06:17 192.168.122.209 [72128.567760] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:06:17 192.168.122.209 [72128.597623] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:06:17 192.168.122.209 [72128.628094] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:06:17 192.168.122.209 [72128.692784] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:06:18 192.168.122.209 [72128.740698] [tempesta fw] Tempesta FW is ready Apr 26 12:06:20 192.168.122.209 [72131.383667] [tdb] Close table 'client0.tdb' Apr 26 12:06:20 192.168.122.209 [72131.573837] [tdb] Close table 'sessions0.tdb' Apr 26 12:06:24 192.168.122.209 [72134.768283] [tdb] Close table 'cache0.tdb' Apr 26 12:06:24 192.168.122.209 [72135.021567] [tdb] Close table 'filter0.tdb' Apr 26 12:06:24 192.168.122.209 [72135.021974] [tempesta fw] modules are stopped Apr 26 12:06:24 192.168.122.209 [72135.210884] [tempesta fw] exiting... Apr 26 12:06:24 192.168.122.209 [72135.337006] [tdb] Shutdown Tempesta DB Apr 26 12:06:24 192.168.122.209 [72135.704104] End test: cache.test_cache_control.ResponseSMaxageNotCached2.test Apr 26 12:06:25 192.168.122.209 [72135.737118] Start test: cache.test_cache_control.ResponseStaleCached.test Apr 26 12:06:26 192.168.122.209 [72137.031458] [tdb] Start Tempesta DB Apr 26 12:06:26 192.168.122.209 [72137.182788] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:06:27 192.168.122.209 [72138.688910] [tempesta fw] Configuration processing is completed. Apr 26 12:06:28 192.168.122.209 [72138.741837] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:06:28 192.168.122.209 [72139.213615] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:06:28 192.168.122.209 [72139.243788] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:06:28 192.168.122.209 [72139.274179] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:06:28 192.168.122.209 [72139.316918] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:06:28 192.168.122.209 [72139.360836] [tempesta fw] Tempesta FW is ready Apr 26 12:06:30 192.168.122.209 [72141.548513] [tdb] Close table 'client0.tdb' Apr 26 12:06:31 192.168.122.209 [72141.753977] [tdb] Close table 'sessions0.tdb' Apr 26 12:06:34 192.168.122.209 [72144.968480] [tdb] Close table 'cache0.tdb' Apr 26 12:06:34 192.168.122.209 [72145.216626] [tdb] Close table 'filter0.tdb' Apr 26 12:06:34 192.168.122.209 [72145.217086] [tempesta fw] modules are stopped Apr 26 12:06:34 192.168.122.209 [72145.437799] [tempesta fw] exiting... Apr 26 12:06:34 192.168.122.209 [72145.577817] [tdb] Shutdown Tempesta DB Apr 26 12:06:35 192.168.122.209 [72146.017223] End test: cache.test_cache_control.ResponseStaleCached.test Apr 26 12:06:35 192.168.122.209 [72146.053806] Start test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsDefaultCache.test Apr 26 12:06:36 192.168.122.209 [72147.371446] [tdb] Start Tempesta DB Apr 26 12:06:36 192.168.122.209 [72147.508673] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:06:38 192.168.122.209 [72149.037049] [tempesta fw] Configuration processing is completed. Apr 26 12:06:38 192.168.122.209 [72149.093965] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:06:38 192.168.122.209 [72149.529064] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:06:38 192.168.122.209 [72149.555525] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:06:38 192.168.122.209 [72149.581224] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:06:38 192.168.122.209 [72149.624996] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:06:38 192.168.122.209 [72149.676961] [tempesta fw] Tempesta FW is ready Apr 26 12:06:39 192.168.122.209 [72150.343764] [tdb] Close table 'client0.tdb' Apr 26 12:06:39 192.168.122.209 [72150.531429] [tdb] Close table 'sessions0.tdb' Apr 26 12:06:43 192.168.122.209 [72153.976472] [tdb] Close table 'cache0.tdb' Apr 26 12:06:43 192.168.122.209 [72154.223787] [tdb] Close table 'filter0.tdb' Apr 26 12:06:43 192.168.122.209 [72154.224218] [tempesta fw] modules are stopped Apr 26 12:06:43 192.168.122.209 [72154.421888] [tempesta fw] exiting... Apr 26 12:06:43 192.168.122.209 [72154.550128] [tdb] Shutdown Tempesta DB Apr 26 12:06:44 192.168.122.209 [72154.913453] End test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsDefaultCache.test Apr 26 12:06:44 192.168.122.209 [72154.940366] Start test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsMaxAgeCache.test Apr 26 12:06:45 192.168.122.209 [72156.270175] [tdb] Start Tempesta DB Apr 26 12:06:45 192.168.122.209 [72156.400910] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:06:47 192.168.122.209 [72157.961185] [tempesta fw] Configuration processing is completed. Apr 26 12:06:47 192.168.122.209 [72158.023525] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:06:47 192.168.122.209 [72158.460413] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:06:47 192.168.122.209 [72158.496177] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:06:47 192.168.122.209 [72158.529545] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:06:47 192.168.122.209 [72158.569141] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:06:47 192.168.122.209 [72158.605059] [tempesta fw] Tempesta FW is ready Apr 26 12:06:48 192.168.122.209 [72159.239984] [tdb] Close table 'client0.tdb' Apr 26 12:06:48 192.168.122.209 [72159.426340] [tdb] Close table 'sessions0.tdb' Apr 26 12:06:51 192.168.122.209 [72162.547216] [tdb] Close table 'cache0.tdb' Apr 26 12:06:52 192.168.122.209 [72162.791541] [tdb] Close table 'filter0.tdb' Apr 26 12:06:52 192.168.122.209 [72162.791981] [tempesta fw] modules are stopped Apr 26 12:06:52 192.168.122.209 [72162.998447] [tempesta fw] exiting... Apr 26 12:06:52 192.168.122.209 [72163.111738] [tdb] Shutdown Tempesta DB Apr 26 12:06:52 192.168.122.209 [72163.463361] End test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsMaxAgeCache.test Apr 26 12:06:52 192.168.122.209 [72163.492362] Start test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsMustRevalidateCache2.test Apr 26 12:06:54 192.168.122.209 [72164.760807] [tdb] Start Tempesta DB Apr 26 12:06:54 192.168.122.209 [72164.900840] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:06:55 192.168.122.209 [72166.377240] [tempesta fw] Configuration processing is completed. Apr 26 12:06:55 192.168.122.209 [72166.427962] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:06:56 192.168.122.209 [72166.854534] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:06:56 192.168.122.209 [72166.881810] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:06:56 192.168.122.209 [72166.907981] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:06:56 192.168.122.209 [72166.973216] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:06:56 192.168.122.209 [72167.017157] [tempesta fw] Tempesta FW is ready Apr 26 12:06:56 192.168.122.209 [72167.672001] [tdb] Close table 'client0.tdb' Apr 26 12:06:57 192.168.122.209 [72167.859640] [tdb] Close table 'sessions0.tdb' Apr 26 12:07:00 192.168.122.209 [72171.007669] [tdb] Close table 'cache0.tdb' Apr 26 12:07:00 192.168.122.209 [72171.276727] [tdb] Close table 'filter0.tdb' Apr 26 12:07:00 192.168.122.209 [72171.277155] [tempesta fw] modules are stopped Apr 26 12:07:00 192.168.122.209 [72171.462988] [tempesta fw] exiting... Apr 26 12:07:00 192.168.122.209 [72171.592969] [tdb] Shutdown Tempesta DB Apr 26 12:07:01 192.168.122.209 [72171.951049] End test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsMustRevalidateCache2.test Apr 26 12:07:01 192.168.122.209 [72171.978629] Start test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsNoCacheCache.test Apr 26 12:07:02 192.168.122.209 [72173.307938] [tdb] Start Tempesta DB Apr 26 12:07:02 192.168.122.209 [72173.437662] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:07:04 192.168.122.209 [72174.941344] [tempesta fw] Configuration processing is completed. Apr 26 12:07:04 192.168.122.209 [72174.993415] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:07:04 192.168.122.209 [72175.417826] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:07:04 192.168.122.209 [72175.444551] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:07:04 192.168.122.209 [72175.470255] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:07:04 192.168.122.209 [72175.513269] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:07:04 192.168.122.209 [72175.557264] [tempesta fw] Tempesta FW is ready Apr 26 12:07:05 192.168.122.209 [72176.170013] [tdb] Close table 'client0.tdb' Apr 26 12:07:05 192.168.122.209 [72176.358174] [tdb] Close table 'sessions0.tdb' Apr 26 12:07:08 192.168.122.209 [72179.551640] [tdb] Close table 'cache0.tdb' Apr 26 12:07:09 192.168.122.209 [72179.784134] [tdb] Close table 'filter0.tdb' Apr 26 12:07:09 192.168.122.209 [72179.784556] [tempesta fw] modules are stopped Apr 26 12:07:09 192.168.122.209 [72180.026052] [tempesta fw] exiting... Apr 26 12:07:09 192.168.122.209 [72180.151002] [tdb] Shutdown Tempesta DB Apr 26 12:07:09 192.168.122.209 [72180.549307] End test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsNoCacheCache.test Apr 26 12:07:09 192.168.122.209 [72180.585548] Start test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsNoStoreCache.test Apr 26 12:07:11 192.168.122.209 [72181.864459] [tdb] Start Tempesta DB Apr 26 12:07:11 192.168.122.209 [72181.999107] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:07:12 192.168.122.209 [72183.429472] [tempesta fw] Configuration processing is completed. Apr 26 12:07:12 192.168.122.209 [72183.481979] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:07:13 192.168.122.209 [72183.894896] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:07:13 192.168.122.209 [72183.922577] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:07:13 192.168.122.209 [72183.947705] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:07:13 192.168.122.209 [72183.989420] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:07:13 192.168.122.209 [72184.041317] [tempesta fw] Tempesta FW is ready Apr 26 12:07:13 192.168.122.209 [72184.713260] [tdb] Close table 'client0.tdb' Apr 26 12:07:14 192.168.122.209 [72184.905259] [tdb] Close table 'sessions0.tdb' Apr 26 12:07:17 192.168.122.209 [72188.082202] [tdb] Close table 'cache0.tdb' Apr 26 12:07:17 192.168.122.209 [72188.339508] [tdb] Close table 'filter0.tdb' Apr 26 12:07:17 192.168.122.209 [72188.339939] [tempesta fw] modules are stopped Apr 26 12:07:17 192.168.122.209 [72188.521087] [tempesta fw] exiting... Apr 26 12:07:17 192.168.122.209 [72188.653537] [tdb] Shutdown Tempesta DB Apr 26 12:07:18 192.168.122.209 [72189.016920] End test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsNoStoreCache.test Apr 26 12:07:18 192.168.122.209 [72189.050146] Start test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsNoTransformCache.test Apr 26 12:07:19 192.168.122.209 [72190.416282] [tdb] Start Tempesta DB Apr 26 12:07:19 192.168.122.209 [72190.548647] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:07:21 192.168.122.209 [72192.057874] [tempesta fw] Configuration processing is completed. Apr 26 12:07:21 192.168.122.209 [72192.107540] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:07:21 192.168.122.209 [72192.519021] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:07:21 192.168.122.209 [72192.544563] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:07:21 192.168.122.209 [72192.569986] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:07:21 192.168.122.209 [72192.617508] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:07:21 192.168.122.209 [72192.657459] [tempesta fw] Tempesta FW is ready Apr 26 12:07:22 192.168.122.209 [72193.304889] [tdb] Close table 'client0.tdb' Apr 26 12:07:22 192.168.122.209 [72193.493267] [tdb] Close table 'sessions0.tdb' Apr 26 12:07:25 192.168.122.209 [72196.631397] [tdb] Close table 'cache0.tdb' Apr 26 12:07:26 192.168.122.209 [72196.899197] [tdb] Close table 'filter0.tdb' Apr 26 12:07:26 192.168.122.209 [72196.899593] [tempesta fw] modules are stopped Apr 26 12:07:26 192.168.122.209 [72197.162910] [tempesta fw] exiting... Apr 26 12:07:26 192.168.122.209 [72197.302466] [tdb] Shutdown Tempesta DB Apr 26 12:07:26 192.168.122.209 [72197.672174] End test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsNoTransformCache.test Apr 26 12:07:26 192.168.122.209 [72197.712642] Start test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsPrivateCache.test Apr 26 12:07:28 192.168.122.209 [72198.979469] [tdb] Start Tempesta DB Apr 26 12:07:28 192.168.122.209 [72199.112695] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:07:29 192.168.122.209 [72200.613698] [tempesta fw] Configuration processing is completed. Apr 26 12:07:29 192.168.122.209 [72200.671055] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:07:30 192.168.122.209 [72201.100173] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:07:30 192.168.122.209 [72201.133509] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:07:30 192.168.122.209 [72201.160076] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:07:30 192.168.122.209 [72201.217613] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:07:30 192.168.122.209 [72201.257565] [tempesta fw] Tempesta FW is ready Apr 26 12:07:31 192.168.122.209 [72201.906671] [tdb] Close table 'client0.tdb' Apr 26 12:07:31 192.168.122.209 [72202.090951] [tdb] Close table 'sessions0.tdb' Apr 26 12:07:34 192.168.122.209 [72205.214308] [tdb] Close table 'cache0.tdb' Apr 26 12:07:34 192.168.122.209 [72205.453287] [tdb] Close table 'filter0.tdb' Apr 26 12:07:34 192.168.122.209 [72205.454139] [tempesta fw] modules are stopped Apr 26 12:07:34 192.168.122.209 [72205.666677] [tempesta fw] exiting... Apr 26 12:07:35 192.168.122.209 [72205.790955] [tdb] Shutdown Tempesta DB Apr 26 12:07:35 192.168.122.209 [72206.174158] End test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsPrivateCache.test Apr 26 12:07:35 192.168.122.209 [72206.205165] Start test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsProxyRevalidateCache.test Apr 26 12:07:36 192.168.122.209 [72207.566051] [tdb] Start Tempesta DB Apr 26 12:07:36 192.168.122.209 [72207.708721] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:07:38 192.168.122.209 [72209.153872] [tempesta fw] Configuration processing is completed. Apr 26 12:07:38 192.168.122.209 [72209.211315] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:07:38 192.168.122.209 [72209.649279] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:07:38 192.168.122.209 [72209.675972] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:07:38 192.168.122.209 [72209.703193] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:07:39 192.168.122.209 [72209.757724] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:07:39 192.168.122.209 [72209.793661] [tempesta fw] Tempesta FW is ready Apr 26 12:07:39 192.168.122.209 [72210.454058] [tdb] Close table 'client0.tdb' Apr 26 12:07:39 192.168.122.209 [72210.638124] [tdb] Close table 'sessions0.tdb' Apr 26 12:07:43 192.168.122.209 [72213.762698] [tdb] Close table 'cache0.tdb' Apr 26 12:07:43 192.168.122.209 [72214.020058] [tdb] Close table 'filter0.tdb' Apr 26 12:07:43 192.168.122.209 [72214.020462] [tempesta fw] modules are stopped Apr 26 12:07:43 192.168.122.209 [72214.213335] [tempesta fw] exiting... Apr 26 12:07:43 192.168.122.209 [72214.335098] [tdb] Shutdown Tempesta DB Apr 26 12:07:44 192.168.122.209 [72214.770981] End test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsProxyRevalidateCache.test Apr 26 12:07:44 192.168.122.209 [72214.804485] Start test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsPublicCache.test Apr 26 12:07:45 192.168.122.209 [72216.142874] [tdb] Start Tempesta DB Apr 26 12:07:45 192.168.122.209 [72216.279778] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:07:47 192.168.122.209 [72217.785890] [tempesta fw] Configuration processing is completed. Apr 26 12:07:47 192.168.122.209 [72217.845372] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:07:47 192.168.122.209 [72218.263912] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:07:47 192.168.122.209 [72218.290107] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:07:47 192.168.122.209 [72218.315848] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:07:47 192.168.122.209 [72218.361818] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:07:47 192.168.122.209 [72218.401771] [tempesta fw] Tempesta FW is ready Apr 26 12:07:48 192.168.122.209 [72219.057505] [tdb] Close table 'client0.tdb' Apr 26 12:07:48 192.168.122.209 [72219.235120] [tdb] Close table 'sessions0.tdb' Apr 26 12:07:51 192.168.122.209 [72222.408314] [tdb] Close table 'cache0.tdb' Apr 26 12:07:51 192.168.122.209 [72222.629447] [tdb] Close table 'filter0.tdb' Apr 26 12:07:51 192.168.122.209 [72222.629895] [tempesta fw] modules are stopped Apr 26 12:07:52 192.168.122.209 [72222.827529] [tempesta fw] exiting... Apr 26 12:07:52 192.168.122.209 [72222.951096] [tdb] Shutdown Tempesta DB Apr 26 12:07:52 192.168.122.209 [72223.305759] End test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsPublicCache.test Apr 26 12:07:52 192.168.122.209 [72223.391909] Start test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsSMaxAgeCache.test Apr 26 12:07:53 192.168.122.209 [72224.604672] [tdb] Start Tempesta DB Apr 26 12:07:54 192.168.122.209 [72224.735879] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:07:55 192.168.122.209 [72226.297989] [tempesta fw] Configuration processing is completed. Apr 26 12:07:55 192.168.122.209 [72226.353508] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:07:56 192.168.122.209 [72226.766960] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:07:56 192.168.122.209 [72226.793542] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:07:56 192.168.122.209 [72226.819064] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:07:56 192.168.122.209 [72226.861952] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:07:56 192.168.122.209 [72226.921898] [tempesta fw] Tempesta FW is ready Apr 26 12:07:56 192.168.122.209 [72227.548946] [tdb] Close table 'client0.tdb' Apr 26 12:07:57 192.168.122.209 [72227.734580] [tdb] Close table 'sessions0.tdb' Apr 26 12:08:00 192.168.122.209 [72230.875458] [tdb] Close table 'cache0.tdb' Apr 26 12:08:00 192.168.122.209 [72231.098095] [tdb] Close table 'filter0.tdb' Apr 26 12:08:00 192.168.122.209 [72231.098537] [tempesta fw] modules are stopped Apr 26 12:08:00 192.168.122.209 [72231.282579] [tempesta fw] exiting... Apr 26 12:08:00 192.168.122.209 [72231.409203] [tdb] Shutdown Tempesta DB Apr 26 12:08:01 192.168.122.209 [72231.778813] End test: cache.test_cache_control.StoringResponsesToAuthenticatedRequestsSMaxAgeCache.test Apr 26 12:08:01 192.168.122.209 [72231.811202] Start test: cache.test_cache_control.StoringResponsesWithSetCookieHeaderDefaultCache.test Apr 26 12:08:02 192.168.122.209 [72233.149820] [tdb] Start Tempesta DB Apr 26 12:08:02 192.168.122.209 [72233.286701] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:08:04 192.168.122.209 [72234.822070] [tempesta fw] Configuration processing is completed. Apr 26 12:08:04 192.168.122.209 [72234.877329] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:08:04 192.168.122.209 [72235.305651] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:08:04 192.168.122.209 [72235.331209] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:08:04 192.168.122.209 [72235.356226] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:08:04 192.168.122.209 [72235.402029] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:08:04 192.168.122.209 [72235.457987] [tempesta fw] Tempesta FW is ready Apr 26 12:08:05 192.168.122.209 [72236.087794] [tdb] Close table 'client0.tdb' Apr 26 12:08:05 192.168.122.209 [72236.265640] [tdb] Close table 'sessions0.tdb' Apr 26 12:08:08 192.168.122.209 [72239.408934] [tdb] Close table 'cache0.tdb' Apr 26 12:08:08 192.168.122.209 [72239.669667] [tdb] Close table 'filter0.tdb' Apr 26 12:08:08 192.168.122.209 [72239.670129] [tempesta fw] modules are stopped Apr 26 12:08:09 192.168.122.209 [72239.863413] [tempesta fw] exiting... Apr 26 12:08:09 192.168.122.209 [72239.990138] [tdb] Shutdown Tempesta DB Apr 26 12:08:09 192.168.122.209 [72240.382749] End test: cache.test_cache_control.StoringResponsesWithSetCookieHeaderDefaultCache.test Apr 26 12:08:09 192.168.122.209 [72240.417370] Start test: cache.test_cache_control.TestCache.test Apr 26 12:08:10 192.168.122.209 [72241.707479] [tdb] Start Tempesta DB Apr 26 12:08:11 192.168.122.209 [72241.835672] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:08:12 192.168.122.209 [72243.382192] [tempesta fw] Configuration processing is completed. Apr 26 12:08:12 192.168.122.209 [72243.433586] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:08:13 192.168.122.209 [72243.847941] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:08:13 192.168.122.209 [72243.873804] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:08:13 192.168.122.209 [72243.900193] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:08:13 192.168.122.209 [72243.942128] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:08:13 192.168.122.209 [72243.994023] [tempesta fw] Tempesta FW is ready Apr 26 12:08:13 192.168.122.209 [72244.660129] [tdb] Close table 'client0.tdb' Apr 26 12:08:14 192.168.122.209 [72244.844799] [tdb] Close table 'sessions0.tdb' Apr 26 12:08:17 192.168.122.209 [72248.007990] [tdb] Close table 'cache0.tdb' Apr 26 12:08:17 192.168.122.209 [72248.253914] [tdb] Close table 'filter0.tdb' Apr 26 12:08:17 192.168.122.209 [72248.254364] [tempesta fw] modules are stopped Apr 26 12:08:17 192.168.122.209 [72248.490104] [tempesta fw] exiting... Apr 26 12:08:17 192.168.122.209 [72248.636463] [tdb] Shutdown Tempesta DB Apr 26 12:08:18 192.168.122.209 [72249.006985] End test: cache.test_cache_control.TestCache.test Apr 26 12:08:18 192.168.122.209 [72249.038856] Start test: cache.test_cache_control.TestCache2.test Apr 26 12:08:19 192.168.122.209 [72250.356856] [tdb] Start Tempesta DB Apr 26 12:08:19 192.168.122.209 [72250.492604] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:08:21 192.168.122.209 [72251.982602] [tempesta fw] Configuration processing is completed. Apr 26 12:08:21 192.168.122.209 [72252.034641] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:08:21 192.168.122.209 [72252.448638] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:08:21 192.168.122.209 [72252.474821] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:08:21 192.168.122.209 [72252.500494] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:08:21 192.168.122.209 [72252.550229] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:08:21 192.168.122.209 [72252.594178] [tempesta fw] Tempesta FW is ready Apr 26 12:08:22 192.168.122.209 [72253.200593] [tdb] Close table 'client0.tdb' Apr 26 12:08:22 192.168.122.209 [72253.384944] [tdb] Close table 'sessions0.tdb' Apr 26 12:08:25 192.168.122.209 [72256.509762] [tdb] Close table 'cache0.tdb' Apr 26 12:08:26 192.168.122.209 [72256.761793] [tdb] Close table 'filter0.tdb' Apr 26 12:08:26 192.168.122.209 [72256.762265] [tempesta fw] modules are stopped Apr 26 12:08:26 192.168.122.209 [72256.943703] [tempesta fw] exiting... Apr 26 12:08:26 192.168.122.209 [72257.104684] [tdb] Shutdown Tempesta DB Apr 26 12:08:26 192.168.122.209 [72257.419388] End test: cache.test_cache_control.TestCache2.test Apr 26 12:08:26 192.168.122.209 [72257.501564] Start test: cache.test_cache_control.TestCacheBypass.test Apr 26 12:08:28 192.168.122.209 [72258.790271] [tdb] Start Tempesta DB Apr 26 12:08:28 192.168.122.209 [72258.918917] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:08:29 192.168.122.209 [72260.414323] [tempesta fw] Configuration processing is completed. Apr 26 12:08:29 192.168.122.209 [72260.477028] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:08:30 192.168.122.209 [72260.908675] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:08:30 192.168.122.209 [72260.936812] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:08:30 192.168.122.209 [72260.963371] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:08:30 192.168.122.209 [72261.018363] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:08:30 192.168.122.209 [72261.070282] [tempesta fw] Tempesta FW is ready Apr 26 12:08:30 192.168.122.209 [72261.673347] [tdb] Close table 'client0.tdb' Apr 26 12:08:31 192.168.122.209 [72261.879496] [tdb] Close table 'sessions0.tdb' Apr 26 12:08:34 192.168.122.209 [72265.028554] [tdb] Close table 'cache0.tdb' Apr 26 12:08:34 192.168.122.209 [72265.280143] [tdb] Close table 'filter0.tdb' Apr 26 12:08:34 192.168.122.209 [72265.280616] [tempesta fw] modules are stopped Apr 26 12:08:34 192.168.122.209 [72265.464267] [tempesta fw] exiting... Apr 26 12:08:34 192.168.122.209 [72265.590924] [tdb] Shutdown Tempesta DB Apr 26 12:08:35 192.168.122.209 [72265.959889] End test: cache.test_cache_control.TestCacheBypass.test Apr 26 12:08:35 192.168.122.209 [72266.040425] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_no_cache_in_request_and_cache_lvl_1 Apr 26 12:08:36 192.168.122.209 [72267.399769] [tdb] Start Tempesta DB Apr 26 12:08:36 192.168.122.209 [72267.524811] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:08:38 192.168.122.209 [72268.839819] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72268.839819] Maybe that's fine, but it's worth checking the [72268.839819] config - if there is no relations between the [72268.839819] names, then host name confusion attack is possible. Apr 26 12:08:38 192.168.122.209 [72268.926460] [tempesta fw] Configuration processing is completed. Apr 26 12:08:38 192.168.122.209 [72268.994729] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:08:38 192.168.122.209 [72269.414775] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:08:38 192.168.122.209 [72269.440613] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:08:38 192.168.122.209 [72269.467373] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:08:38 192.168.122.209 [72269.510463] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:08:38 192.168.122.209 [72269.512255] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:08:38 192.168.122.209 [72269.574406] [tempesta fw] Tempesta FW is ready Apr 26 12:08:39 192.168.122.209 [72270.210454] [tdb] Close table 'client0.tdb' Apr 26 12:08:39 192.168.122.209 [72270.408262] [tdb] Close table 'sessions0.tdb' Apr 26 12:08:42 192.168.122.209 [72273.500734] [tdb] Close table 'cache0.tdb' Apr 26 12:08:43 192.168.122.209 [72273.761390] [tdb] Close table 'filter0.tdb' Apr 26 12:08:43 192.168.122.209 [72273.761794] [tempesta fw] modules are stopped Apr 26 12:08:43 192.168.122.209 [72273.940381] [tempesta fw] exiting... Apr 26 12:08:43 192.168.122.209 [72274.083692] [tdb] Shutdown Tempesta DB Apr 26 12:08:43 192.168.122.209 [72274.453569] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_no_cache_in_request_and_cache_lvl_1 Apr 26 12:08:43 192.168.122.209 [72274.485967] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_no_cache_in_request_and_cache_lvl_2 Apr 26 12:08:45 192.168.122.209 [72275.852242] [tdb] Start Tempesta DB Apr 26 12:08:45 192.168.122.209 [72275.988853] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:08:46 192.168.122.209 [72277.323831] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72277.323831] Maybe that's fine, but it's worth checking the [72277.323831] config - if there is no relations between the [72277.323831] names, then host name confusion attack is possible. Apr 26 12:08:46 192.168.122.209 [72277.410588] [tempesta fw] Configuration processing is completed. Apr 26 12:08:46 192.168.122.209 [72277.461554] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:08:47 192.168.122.209 [72277.870132] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:08:47 192.168.122.209 [72277.904733] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:08:47 192.168.122.209 [72277.929782] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:08:47 192.168.122.209 [72277.974540] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:08:47 192.168.122.209 [72277.976273] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:08:47 192.168.122.209 [72278.014481] [tempesta fw] Tempesta FW is ready Apr 26 12:08:47 192.168.122.209 [72278.707802] [tdb] Close table 'client0.tdb' Apr 26 12:08:48 192.168.122.209 [72278.889792] [tdb] Close table 'sessions0.tdb' Apr 26 12:08:51 192.168.122.209 [72281.992056] [tdb] Close table 'cache0.tdb' Apr 26 12:08:51 192.168.122.209 [72282.250292] [tdb] Close table 'filter0.tdb' Apr 26 12:08:51 192.168.122.209 [72282.250771] [tempesta fw] modules are stopped Apr 26 12:08:51 192.168.122.209 [72282.446486] [tempesta fw] exiting... Apr 26 12:08:51 192.168.122.209 [72282.593209] [tdb] Shutdown Tempesta DB Apr 26 12:08:52 192.168.122.209 [72283.022848] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_no_cache_in_request_and_cache_lvl_2 Apr 26 12:08:52 192.168.122.209 [72283.052413] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_no_cache_in_response_and_cache_lvl_1 Apr 26 12:08:53 192.168.122.209 [72284.460156] [tdb] Start Tempesta DB Apr 26 12:08:53 192.168.122.209 [72284.600724] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:08:55 192.168.122.209 [72285.987899] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72285.987899] Maybe that's fine, but it's worth checking the [72285.987899] config - if there is no relations between the [72285.987899] names, then host name confusion attack is possible. Apr 26 12:08:55 192.168.122.209 [72286.062668] [tempesta fw] Configuration processing is completed. Apr 26 12:08:55 192.168.122.209 [72286.115583] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:08:55 192.168.122.209 [72286.538261] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:08:55 192.168.122.209 [72286.564934] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:08:55 192.168.122.209 [72286.590518] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:08:55 192.168.122.209 [72286.634650] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:08:55 192.168.122.209 [72286.636369] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:08:55 192.168.122.209 [72286.678597] [tempesta fw] Tempesta FW is ready Apr 26 12:08:56 192.168.122.209 [72287.321692] [tdb] Close table 'client0.tdb' Apr 26 12:08:56 192.168.122.209 [72287.521290] [tdb] Close table 'sessions0.tdb' Apr 26 12:08:59 192.168.122.209 [72290.641502] [tdb] Close table 'cache0.tdb' Apr 26 12:09:00 192.168.122.209 [72290.874286] [tdb] Close table 'filter0.tdb' Apr 26 12:09:00 192.168.122.209 [72290.874739] [tempesta fw] modules are stopped Apr 26 12:09:00 192.168.122.209 [72291.084727] [tempesta fw] exiting... Apr 26 12:09:00 192.168.122.209 [72291.199475] [tdb] Shutdown Tempesta DB Apr 26 12:09:00 192.168.122.209 [72291.635359] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_no_cache_in_response_and_cache_lvl_1 Apr 26 12:09:00 192.168.122.209 [72291.668406] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_no_cache_in_response_and_cache_lvl_2 Apr 26 12:09:02 192.168.122.209 [72293.003489] [tdb] Start Tempesta DB Apr 26 12:09:02 192.168.122.209 [72293.144840] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:09:03 192.168.122.209 [72294.531989] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72294.531989] Maybe that's fine, but it's worth checking the [72294.531989] config - if there is no relations between the [72294.531989] names, then host name confusion attack is possible. Apr 26 12:09:03 192.168.122.209 [72294.614772] [tempesta fw] Configuration processing is completed. Apr 26 12:09:03 192.168.122.209 [72294.665033] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:09:04 192.168.122.209 [72295.067526] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:09:04 192.168.122.209 [72295.092784] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:09:04 192.168.122.209 [72295.117390] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:09:04 192.168.122.209 [72295.162749] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:09:04 192.168.122.209 [72295.164508] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:09:04 192.168.122.209 [72295.198706] [tempesta fw] Tempesta FW is ready Apr 26 12:09:05 192.168.122.209 [72295.873137] [tdb] Close table 'client0.tdb' Apr 26 12:09:05 192.168.122.209 [72296.062229] [tdb] Close table 'sessions0.tdb' Apr 26 12:09:08 192.168.122.209 [72299.185567] [tdb] Close table 'cache0.tdb' Apr 26 12:09:08 192.168.122.209 [72299.421580] [tdb] Close table 'filter0.tdb' Apr 26 12:09:08 192.168.122.209 [72299.422003] [tempesta fw] modules are stopped Apr 26 12:09:08 192.168.122.209 [72299.620045] [tempesta fw] exiting... Apr 26 12:09:09 192.168.122.209 [72299.743725] [tdb] Shutdown Tempesta DB Apr 26 12:09:09 192.168.122.209 [72300.116370] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_no_cache_in_response_and_cache_lvl_2 Apr 26 12:09:09 192.168.122.209 [72300.143723] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_no_store_in_request_and_cache_lvl_1 Apr 26 12:09:10 192.168.122.209 [72301.442755] [tdb] Start Tempesta DB Apr 26 12:09:10 192.168.122.209 [72301.570841] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:09:12 192.168.122.209 [72302.936103] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72302.936103] Maybe that's fine, but it's worth checking the [72302.936103] config - if there is no relations between the [72302.936103] names, then host name confusion attack is possible. Apr 26 12:09:12 192.168.122.209 [72303.034902] [tempesta fw] Configuration processing is completed. Apr 26 12:09:12 192.168.122.209 [72303.091612] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:09:12 192.168.122.209 [72303.512963] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:09:12 192.168.122.209 [72303.539373] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:09:12 192.168.122.209 [72303.566212] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:09:12 192.168.122.209 [72303.606861] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:09:12 192.168.122.209 [72303.608575] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:09:12 192.168.122.209 [72303.654827] [tempesta fw] Tempesta FW is ready Apr 26 12:09:13 192.168.122.209 [72304.277305] [tdb] Close table 'client0.tdb' Apr 26 12:09:13 192.168.122.209 [72304.464601] [tdb] Close table 'sessions0.tdb' Apr 26 12:09:16 192.168.122.209 [72307.612857] [tdb] Close table 'cache0.tdb' Apr 26 12:09:17 192.168.122.209 [72307.846831] [tdb] Close table 'filter0.tdb' Apr 26 12:09:17 192.168.122.209 [72307.847262] [tempesta fw] modules are stopped Apr 26 12:09:17 192.168.122.209 [72308.051378] [tempesta fw] exiting... Apr 26 12:09:17 192.168.122.209 [72308.196547] [tdb] Shutdown Tempesta DB Apr 26 12:09:17 192.168.122.209 [72308.548231] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_no_store_in_request_and_cache_lvl_1 Apr 26 12:09:17 192.168.122.209 [72308.576409] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_no_store_in_request_and_cache_lvl_2 Apr 26 12:09:19 192.168.122.209 [72309.988324] [tdb] Start Tempesta DB Apr 26 12:09:19 192.168.122.209 [72310.117160] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:09:20 192.168.122.209 [72311.544290] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72311.544290] Maybe that's fine, but it's worth checking the [72311.544290] config - if there is no relations between the [72311.544290] names, then host name confusion attack is possible. Apr 26 12:09:20 192.168.122.209 [72311.631012] [tempesta fw] Configuration processing is completed. Apr 26 12:09:20 192.168.122.209 [72311.687399] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:09:21 192.168.122.209 [72312.109821] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:09:21 192.168.122.209 [72312.136197] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:09:21 192.168.122.209 [72312.161926] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:09:21 192.168.122.209 [72312.202969] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:09:21 192.168.122.209 [72312.204684] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:09:21 192.168.122.209 [72312.242912] [tempesta fw] Tempesta FW is ready Apr 26 12:09:22 192.168.122.209 [72312.875660] [tdb] Close table 'client0.tdb' Apr 26 12:09:22 192.168.122.209 [72313.081233] [tdb] Close table 'sessions0.tdb' Apr 26 12:09:25 192.168.122.209 [72316.183157] [tdb] Close table 'cache0.tdb' Apr 26 12:09:25 192.168.122.209 [72316.441706] [tdb] Close table 'filter0.tdb' Apr 26 12:09:25 192.168.122.209 [72316.442106] [tempesta fw] modules are stopped Apr 26 12:09:25 192.168.122.209 [72316.612216] [tempesta fw] exiting... Apr 26 12:09:26 192.168.122.209 [72316.736175] [tdb] Shutdown Tempesta DB Apr 26 12:09:26 192.168.122.209 [72317.120100] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_no_store_in_request_and_cache_lvl_2 Apr 26 12:09:26 192.168.122.209 [72317.153828] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_no_store_in_response_and_cache_lvl_1 Apr 26 12:09:27 192.168.122.209 [72318.615507] [tdb] Start Tempesta DB Apr 26 12:09:28 192.168.122.209 [72318.736003] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:09:29 192.168.122.209 [72320.044318] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72320.044318] Maybe that's fine, but it's worth checking the [72320.044318] config - if there is no relations between the [72320.044318] names, then host name confusion attack is possible. Apr 26 12:09:29 192.168.122.209 [72320.127110] [tempesta fw] Configuration processing is completed. Apr 26 12:09:29 192.168.122.209 [72320.184018] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:09:29 192.168.122.209 [72320.601727] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:09:29 192.168.122.209 [72320.628214] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:09:29 192.168.122.209 [72320.654336] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:09:29 192.168.122.209 [72320.695075] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:09:29 192.168.122.209 [72320.696804] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:09:30 192.168.122.209 [72320.747006] [tempesta fw] Tempesta FW is ready Apr 26 12:09:30 192.168.122.209 [72321.402817] [tdb] Close table 'client0.tdb' Apr 26 12:09:30 192.168.122.209 [72321.585589] [tdb] Close table 'sessions0.tdb' Apr 26 12:09:34 192.168.122.209 [72324.748551] [tdb] Close table 'cache0.tdb' Apr 26 12:09:34 192.168.122.209 [72325.015828] [tdb] Close table 'filter0.tdb' Apr 26 12:09:34 192.168.122.209 [72325.016249] [tempesta fw] modules are stopped Apr 26 12:09:34 192.168.122.209 [72325.195900] [tempesta fw] exiting... Apr 26 12:09:34 192.168.122.209 [72325.339978] [tdb] Shutdown Tempesta DB Apr 26 12:09:35 192.168.122.209 [72325.762880] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_no_store_in_response_and_cache_lvl_1 Apr 26 12:09:35 192.168.122.209 [72325.792508] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_no_store_in_response_and_cache_lvl_2 Apr 26 12:09:36 192.168.122.209 [72327.138572] [tdb] Start Tempesta DB Apr 26 12:09:36 192.168.122.209 [72327.278173] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:09:37 192.168.122.209 [72328.648399] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72328.648399] Maybe that's fine, but it's worth checking the [72328.648399] config - if there is no relations between the [72328.648399] names, then host name confusion attack is possible. Apr 26 12:09:38 192.168.122.209 [72328.751202] [tempesta fw] Configuration processing is completed. Apr 26 12:09:38 192.168.122.209 [72328.804410] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:09:38 192.168.122.209 [72329.226323] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:09:38 192.168.122.209 [72329.253773] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:09:38 192.168.122.209 [72329.282589] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:09:38 192.168.122.209 [72329.327175] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:09:38 192.168.122.209 [72329.328892] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:09:38 192.168.122.209 [72329.375120] [tempesta fw] Tempesta FW is ready Apr 26 12:09:39 192.168.122.209 [72330.027244] [tdb] Close table 'client0.tdb' Apr 26 12:09:39 192.168.122.209 [72330.198735] [tdb] Close table 'sessions0.tdb' Apr 26 12:09:42 192.168.122.209 [72333.303263] [tdb] Close table 'cache0.tdb' Apr 26 12:09:42 192.168.122.209 [72333.550538] [tdb] Close table 'filter0.tdb' Apr 26 12:09:42 192.168.122.209 [72333.550961] [tempesta fw] modules are stopped Apr 26 12:09:43 192.168.122.209 [72333.740850] [tempesta fw] exiting... Apr 26 12:09:43 192.168.122.209 [72333.861637] [tdb] Shutdown Tempesta DB Apr 26 12:09:43 192.168.122.209 [72334.246547] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_no_store_in_response_and_cache_lvl_2 Apr 26 12:09:43 192.168.122.209 [72334.274713] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_private_in_response_and_cache_lvl_1 Apr 26 12:09:44 192.168.122.209 [72335.614593] [tdb] Start Tempesta DB Apr 26 12:09:45 192.168.122.209 [72335.743684] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:09:46 192.168.122.209 [72337.100496] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72337.100496] Maybe that's fine, but it's worth checking the [72337.100496] config - if there is no relations between the [72337.100496] names, then host name confusion attack is possible. Apr 26 12:09:46 192.168.122.209 [72337.199285] [tempesta fw] Configuration processing is completed. Apr 26 12:09:46 192.168.122.209 [72337.250161] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:09:46 192.168.122.209 [72337.674469] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:09:46 192.168.122.209 [72337.702225] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:09:47 192.168.122.209 [72337.729552] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:09:47 192.168.122.209 [72337.783286] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:09:47 192.168.122.209 [72337.785049] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:09:47 192.168.122.209 [72337.843235] [tempesta fw] Tempesta FW is ready Apr 26 12:09:47 192.168.122.209 [72338.506479] [tdb] Close table 'client0.tdb' Apr 26 12:09:47 192.168.122.209 [72338.696437] [tdb] Close table 'sessions0.tdb' Apr 26 12:09:51 192.168.122.209 [72341.842467] [tdb] Close table 'cache0.tdb' Apr 26 12:09:51 192.168.122.209 [72342.092897] [tdb] Close table 'filter0.tdb' Apr 26 12:09:51 192.168.122.209 [72342.093290] [tempesta fw] modules are stopped Apr 26 12:09:51 192.168.122.209 [72342.274909] [tempesta fw] exiting... Apr 26 12:09:51 192.168.122.209 [72342.418538] [tdb] Shutdown Tempesta DB Apr 26 12:09:52 192.168.122.209 [72342.782768] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_private_in_response_and_cache_lvl_1 Apr 26 12:09:52 192.168.122.209 [72342.814177] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_private_in_response_and_cache_lvl_2 Apr 26 12:09:53 192.168.122.209 [72344.228736] [tdb] Start Tempesta DB Apr 26 12:09:53 192.168.122.209 [72344.359864] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:09:54 192.168.122.209 [72345.708624] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72345.708624] Maybe that's fine, but it's worth checking the [72345.708624] config - if there is no relations between the [72345.708624] names, then host name confusion attack is possible. Apr 26 12:09:55 192.168.122.209 [72345.791356] [tempesta fw] Configuration processing is completed. Apr 26 12:09:55 192.168.122.209 [72345.848724] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:09:55 192.168.122.209 [72346.272350] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:09:55 192.168.122.209 [72346.298667] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:09:55 192.168.122.209 [72346.324375] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:09:55 192.168.122.209 [72346.371396] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:09:55 192.168.122.209 [72346.373141] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:09:55 192.168.122.209 [72346.411274] [tempesta fw] Tempesta FW is ready Apr 26 12:09:56 192.168.122.209 [72346.993579] [tdb] Close table 'client0.tdb' Apr 26 12:09:56 192.168.122.209 [72347.176876] [tdb] Close table 'sessions0.tdb' Apr 26 12:09:59 192.168.122.209 [72350.343100] [tdb] Close table 'cache0.tdb' Apr 26 12:09:59 192.168.122.209 [72350.581502] [tdb] Close table 'filter0.tdb' Apr 26 12:09:59 192.168.122.209 [72350.581937] [tempesta fw] modules are stopped Apr 26 12:10:00 192.168.122.209 [72350.780381] [tempesta fw] exiting... Apr 26 12:10:00 192.168.122.209 [72350.918372] [tdb] Shutdown Tempesta DB Apr 26 12:10:00 192.168.122.209 [72351.344904] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_cc_private_in_response_and_cache_lvl_2 Apr 26 12:10:00 192.168.122.209 [72351.382444] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_pragma_no_cache_in_request_and_cache_lvl_1 Apr 26 12:10:02 192.168.122.209 [72352.731937] [tdb] Start Tempesta DB Apr 26 12:10:02 192.168.122.209 [72352.865828] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:10:03 192.168.122.209 [72354.180721] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72354.180721] Maybe that's fine, but it's worth checking the [72354.180721] config - if there is no relations between the [72354.180721] names, then host name confusion attack is possible. Apr 26 12:10:03 192.168.122.209 [72354.263498] [tempesta fw] Configuration processing is completed. Apr 26 12:10:03 192.168.122.209 [72354.314144] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:10:04 192.168.122.209 [72354.730554] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:10:04 192.168.122.209 [72354.757100] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:10:04 192.168.122.209 [72354.782337] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:10:04 192.168.122.209 [72354.827491] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:10:04 192.168.122.209 [72354.829247] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:10:04 192.168.122.209 [72354.871456] [tempesta fw] Tempesta FW is ready Apr 26 12:10:04 192.168.122.209 [72355.548495] [tdb] Close table 'client0.tdb' Apr 26 12:10:05 192.168.122.209 [72355.726698] [tdb] Close table 'sessions0.tdb' Apr 26 12:10:08 192.168.122.209 [72358.905719] [tdb] Close table 'cache0.tdb' Apr 26 12:10:08 192.168.122.209 [72359.192692] [tdb] Close table 'filter0.tdb' Apr 26 12:10:08 192.168.122.209 [72359.193121] [tempesta fw] modules are stopped Apr 26 12:10:08 192.168.122.209 [72359.384372] [tempesta fw] exiting... Apr 26 12:10:08 192.168.122.209 [72359.535125] [tdb] Shutdown Tempesta DB Apr 26 12:10:09 192.168.122.209 [72359.945852] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_pragma_no_cache_in_request_and_cache_lvl_1 Apr 26 12:10:09 192.168.122.209 [72359.973660] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_pragma_no_cache_in_request_and_cache_lvl_2 Apr 26 12:10:10 192.168.122.209 [72361.332421] [tdb] Start Tempesta DB Apr 26 12:10:10 192.168.122.209 [72361.474601] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:10:12 192.168.122.209 [72362.876805] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72362.876805] Maybe that's fine, but it's worth checking the [72362.876805] config - if there is no relations between the [72362.876805] names, then host name confusion attack is possible. Apr 26 12:10:12 192.168.122.209 [72362.975635] [tempesta fw] Configuration processing is completed. Apr 26 12:10:12 192.168.122.209 [72363.028260] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:10:12 192.168.122.209 [72363.449102] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:10:12 192.168.122.209 [72363.474969] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:10:12 192.168.122.209 [72363.501015] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:10:12 192.168.122.209 [72363.547601] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:10:12 192.168.122.209 [72363.549354] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:10:12 192.168.122.209 [72363.587538] [tempesta fw] Tempesta FW is ready Apr 26 12:10:13 192.168.122.209 [72364.207096] [tdb] Close table 'client0.tdb' Apr 26 12:10:13 192.168.122.209 [72364.416601] [tdb] Close table 'sessions0.tdb' Apr 26 12:10:16 192.168.122.209 [72367.578253] [tdb] Close table 'cache0.tdb' Apr 26 12:10:17 192.168.122.209 [72367.815647] [tdb] Close table 'filter0.tdb' Apr 26 12:10:17 192.168.122.209 [72367.816099] [tempesta fw] modules are stopped Apr 26 12:10:17 192.168.122.209 [72367.997313] [tempesta fw] exiting... Apr 26 12:10:17 192.168.122.209 [72368.142699] [tdb] Shutdown Tempesta DB Apr 26 12:10:17 192.168.122.209 [72368.581882] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_pragma_no_cache_in_request_and_cache_lvl_2 Apr 26 12:10:17 192.168.122.209 [72368.610378] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_pragma_no_cache_in_response_and_cache_lvl_1 Apr 26 12:10:19 192.168.122.209 [72369.932981] [tdb] Start Tempesta DB Apr 26 12:10:19 192.168.122.209 [72370.056689] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:10:20 192.168.122.209 [72371.376912] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72371.376912] Maybe that's fine, but it's worth checking the [72371.376912] config - if there is no relations between the [72371.376912] names, then host name confusion attack is possible. Apr 26 12:10:20 192.168.122.209 [72371.467703] [tempesta fw] Configuration processing is completed. Apr 26 12:10:20 192.168.122.209 [72371.521860] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:10:21 192.168.122.209 [72371.965977] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:10:21 192.168.122.209 [72371.995428] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:10:21 192.168.122.209 [72372.023953] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:10:21 192.168.122.209 [72372.067692] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:10:21 192.168.122.209 [72372.069465] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:10:21 192.168.122.209 [72372.107583] [tempesta fw] Tempesta FW is ready Apr 26 12:10:22 192.168.122.209 [72372.794657] [tdb] Close table 'client0.tdb' Apr 26 12:10:22 192.168.122.209 [72372.977720] [tdb] Close table 'sessions0.tdb' Apr 26 12:10:25 192.168.122.209 [72376.158000] [tdb] Close table 'cache0.tdb' Apr 26 12:10:25 192.168.122.209 [72376.438852] [tdb] Close table 'filter0.tdb' Apr 26 12:10:25 192.168.122.209 [72376.439260] [tempesta fw] modules are stopped Apr 26 12:10:25 192.168.122.209 [72376.663700] [tempesta fw] exiting... Apr 26 12:10:26 192.168.122.209 [72376.826908] [tdb] Shutdown Tempesta DB Apr 26 12:10:26 192.168.122.209 [72377.224723] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_pragma_no_cache_in_response_and_cache_lvl_1 Apr 26 12:10:26 192.168.122.209 [72377.256745] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_pragma_no_cache_in_response_and_cache_lvl_2 Apr 26 12:10:27 192.168.122.209 [72378.638737] [tdb] Start Tempesta DB Apr 26 12:10:28 192.168.122.209 [72378.770205] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:10:29 192.168.122.209 [72380.149040] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72380.149040] Maybe that's fine, but it's worth checking the [72380.149040] config - if there is no relations between the [72380.149040] names, then host name confusion attack is possible. Apr 26 12:10:29 192.168.122.209 [72380.235812] [tempesta fw] Configuration processing is completed. Apr 26 12:10:29 192.168.122.209 [72380.287930] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:10:29 192.168.122.209 [72380.702067] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:10:30 192.168.122.209 [72380.729066] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:10:30 192.168.122.209 [72380.755086] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:10:30 192.168.122.209 [72380.795784] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:10:30 192.168.122.209 [72380.797527] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:10:30 192.168.122.209 [72380.839731] [tempesta fw] Tempesta FW is ready Apr 26 12:10:30 192.168.122.209 [72381.477928] [tdb] Close table 'client0.tdb' Apr 26 12:10:30 192.168.122.209 [72381.658400] [tdb] Close table 'sessions0.tdb' Apr 26 12:10:34 192.168.122.209 [72384.853419] [tdb] Close table 'cache0.tdb' Apr 26 12:10:34 192.168.122.209 [72385.110949] [tdb] Close table 'filter0.tdb' Apr 26 12:10:34 192.168.122.209 [72385.111380] [tempesta fw] modules are stopped Apr 26 12:10:34 192.168.122.209 [72385.284397] [tempesta fw] exiting... Apr 26 12:10:34 192.168.122.209 [72385.387342] [tdb] Shutdown Tempesta DB Apr 26 12:10:35 192.168.122.209 [72385.765461] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttack.test_pragma_no_cache_in_response_and_cache_lvl_2 Apr 26 12:10:35 192.168.122.209 [72385.796761] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_no_cache_in_request_and_cache_lvl_1 Apr 26 12:10:36 192.168.122.209 [72387.169195] [tdb] Start Tempesta DB Apr 26 12:10:36 192.168.122.209 [72387.291215] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:10:37 192.168.122.209 [72388.689169] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72388.689169] Maybe that's fine, but it's worth checking the [72388.689169] config - if there is no relations between the [72388.689169] names, then host name confusion attack is possible. Apr 26 12:10:38 192.168.122.209 [72388.779947] [tempesta fw] Configuration processing is completed. Apr 26 12:10:38 192.168.122.209 [72388.841713] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:10:38 192.168.122.209 [72389.282889] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:10:38 192.168.122.209 [72389.308575] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:10:38 192.168.122.209 [72389.333697] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:10:38 192.168.122.209 [72389.375888] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:10:38 192.168.122.209 [72389.377629] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:10:38 192.168.122.209 [72389.423835] [tempesta fw] Tempesta FW is ready Apr 26 12:10:39 192.168.122.209 [72390.085799] [tdb] Close table 'client0.tdb' Apr 26 12:10:39 192.168.122.209 [72390.269915] [tdb] Close table 'sessions0.tdb' Apr 26 12:10:42 192.168.122.209 [72393.398795] [tdb] Close table 'cache0.tdb' Apr 26 12:10:42 192.168.122.209 [72393.627039] [tdb] Close table 'filter0.tdb' Apr 26 12:10:42 192.168.122.209 [72393.627442] [tempesta fw] modules are stopped Apr 26 12:10:43 192.168.122.209 [72393.817939] [tempesta fw] exiting... Apr 26 12:10:43 192.168.122.209 [72393.940153] [tdb] Shutdown Tempesta DB Apr 26 12:10:43 192.168.122.209 [72394.354496] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_no_cache_in_request_and_cache_lvl_1 Apr 26 12:10:43 192.168.122.209 [72394.396532] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_no_cache_in_request_and_cache_lvl_2 Apr 26 12:10:45 192.168.122.209 [72395.831480] [tdb] Start Tempesta DB Apr 26 12:10:45 192.168.122.209 [72395.964674] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:10:46 192.168.122.209 [72397.329289] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72397.329289] Maybe that's fine, but it's worth checking the [72397.329289] config - if there is no relations between the [72397.329289] names, then host name confusion attack is possible. Apr 26 12:10:46 192.168.122.209 [72397.404439] [tempesta fw] Configuration processing is completed. Apr 26 12:10:46 192.168.122.209 [72397.460493] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:10:47 192.168.122.209 [72397.882837] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:10:47 192.168.122.209 [72397.909038] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:10:47 192.168.122.209 [72397.935681] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:10:47 192.168.122.209 [72397.975948] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:10:47 192.168.122.209 [72397.977113] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:10:47 192.168.122.209 [72398.011953] [tempesta fw] Tempesta FW is ready Apr 26 12:10:47 192.168.122.209 [72398.664271] [tdb] Close table 'client0.tdb' Apr 26 12:10:48 192.168.122.209 [72398.859224] [tdb] Close table 'sessions0.tdb' Apr 26 12:10:51 192.168.122.209 [72401.999172] [tdb] Close table 'cache0.tdb' Apr 26 12:10:51 192.168.122.209 [72402.242137] [tdb] Close table 'filter0.tdb' Apr 26 12:10:51 192.168.122.209 [72402.242578] [tempesta fw] modules are stopped Apr 26 12:10:51 192.168.122.209 [72402.443973] [tempesta fw] exiting... Apr 26 12:10:51 192.168.122.209 [72402.591011] [tdb] Shutdown Tempesta DB Apr 26 12:10:52 192.168.122.209 [72402.981108] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_no_cache_in_request_and_cache_lvl_2 Apr 26 12:10:52 192.168.122.209 [72403.018947] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_no_cache_in_response_and_cache_lvl_1 Apr 26 12:10:53 192.168.122.209 [72404.453961] [tdb] Start Tempesta DB Apr 26 12:10:53 192.168.122.209 [72404.584318] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:10:55 192.168.122.209 [72405.945366] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72405.945366] Maybe that's fine, but it's worth checking the [72405.945366] config - if there is no relations between the [72405.945366] names, then host name confusion attack is possible. Apr 26 12:10:55 192.168.122.209 [72406.044164] [tempesta fw] Configuration processing is completed. Apr 26 12:10:55 192.168.122.209 [72406.106012] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:10:55 192.168.122.209 [72406.536763] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:10:55 192.168.122.209 [72406.563567] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:10:55 192.168.122.209 [72406.589962] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:10:55 192.168.122.209 [72406.628012] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:10:55 192.168.122.209 [72406.629744] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:10:55 192.168.122.209 [72406.668050] [tempesta fw] Tempesta FW is ready Apr 26 12:10:56 192.168.122.209 [72407.332170] [tdb] Close table 'client0.tdb' Apr 26 12:10:56 192.168.122.209 [72407.509189] [tdb] Close table 'sessions0.tdb' Apr 26 12:10:59 192.168.122.209 [72410.669961] [tdb] Close table 'cache0.tdb' Apr 26 12:11:00 192.168.122.209 [72410.904354] [tdb] Close table 'filter0.tdb' Apr 26 12:11:00 192.168.122.209 [72410.904779] [tempesta fw] modules are stopped Apr 26 12:11:00 192.168.122.209 [72411.128154] [tempesta fw] exiting... Apr 26 12:11:00 192.168.122.209 [72411.235295] [tdb] Shutdown Tempesta DB Apr 26 12:11:00 192.168.122.209 [72411.589531] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_no_cache_in_response_and_cache_lvl_1 Apr 26 12:11:00 192.168.122.209 [72411.615727] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_no_cache_in_response_and_cache_lvl_2 Apr 26 12:11:02 192.168.122.209 [72412.950466] [tdb] Start Tempesta DB Apr 26 12:11:02 192.168.122.209 [72413.089957] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:11:03 192.168.122.209 [72414.489438] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72414.489438] Maybe that's fine, but it's worth checking the [72414.489438] config - if there is no relations between the [72414.489438] names, then host name confusion attack is possible. Apr 26 12:11:03 192.168.122.209 [72414.576335] [tempesta fw] Configuration processing is completed. Apr 26 12:11:03 192.168.122.209 [72414.627750] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:11:04 192.168.122.209 [72415.047913] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:11:04 192.168.122.209 [72415.074260] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:11:04 192.168.122.209 [72415.100485] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:11:04 192.168.122.209 [72415.140230] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:11:04 192.168.122.209 [72415.141942] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:11:04 192.168.122.209 [72415.180173] [tempesta fw] Tempesta FW is ready Apr 26 12:11:05 192.168.122.209 [72415.842612] [tdb] Close table 'client0.tdb' Apr 26 12:11:05 192.168.122.209 [72416.032387] [tdb] Close table 'sessions0.tdb' Apr 26 12:11:08 192.168.122.209 [72419.147614] [tdb] Close table 'cache0.tdb' Apr 26 12:11:08 192.168.122.209 [72419.407024] [tdb] Close table 'filter0.tdb' Apr 26 12:11:08 192.168.122.209 [72419.407432] [tempesta fw] modules are stopped Apr 26 12:11:08 192.168.122.209 [72419.581842] [tempesta fw] exiting... Apr 26 12:11:08 192.168.122.209 [72419.707181] [tdb] Shutdown Tempesta DB Apr 26 12:11:09 192.168.122.209 [72420.129146] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_no_cache_in_response_and_cache_lvl_2 Apr 26 12:11:09 192.168.122.209 [72420.171516] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_no_store_in_request_and_cache_lvl_1 Apr 26 12:11:10 192.168.122.209 [72421.530030] [tdb] Start Tempesta DB Apr 26 12:11:10 192.168.122.209 [72421.677366] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:11:12 192.168.122.209 [72423.097561] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72423.097561] Maybe that's fine, but it's worth checking the [72423.097561] config - if there is no relations between the [72423.097561] names, then host name confusion attack is possible. Apr 26 12:11:12 192.168.122.209 [72423.180331] [tempesta fw] Configuration processing is completed. Apr 26 12:11:12 192.168.122.209 [72423.237814] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:11:12 192.168.122.209 [72423.684898] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:11:12 192.168.122.209 [72423.710913] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:11:13 192.168.122.209 [72423.736759] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:11:13 192.168.122.209 [72423.800316] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:11:13 192.168.122.209 [72423.802088] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:11:13 192.168.122.209 [72423.844271] [tempesta fw] Tempesta FW is ready Apr 26 12:11:13 192.168.122.209 [72424.505497] [tdb] Close table 'client0.tdb' Apr 26 12:11:13 192.168.122.209 [72424.710627] [tdb] Close table 'sessions0.tdb' Apr 26 12:11:17 192.168.122.209 [72427.873888] [tdb] Close table 'cache0.tdb' Apr 26 12:11:17 192.168.122.209 [72428.144109] [tdb] Close table 'filter0.tdb' Apr 26 12:11:17 192.168.122.209 [72428.144544] [tempesta fw] modules are stopped Apr 26 12:11:17 192.168.122.209 [72428.332842] [tempesta fw] exiting... Apr 26 12:11:17 192.168.122.209 [72428.465777] [tdb] Shutdown Tempesta DB Apr 26 12:11:18 192.168.122.209 [72428.849632] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_no_store_in_request_and_cache_lvl_1 Apr 26 12:11:18 192.168.122.209 [72428.877814] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_no_store_in_request_and_cache_lvl_2 Apr 26 12:11:19 192.168.122.209 [72430.312287] [tdb] Start Tempesta DB Apr 26 12:11:19 192.168.122.209 [72430.443004] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:11:21 192.168.122.209 [72431.869666] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72431.869666] Maybe that's fine, but it's worth checking the [72431.869666] config - if there is no relations between the [72431.869666] names, then host name confusion attack is possible. Apr 26 12:11:21 192.168.122.209 [72431.960471] [tempesta fw] Configuration processing is completed. Apr 26 12:11:21 192.168.122.209 [72432.015435] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:11:21 192.168.122.209 [72432.434346] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:11:21 192.168.122.209 [72432.459576] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:11:21 192.168.122.209 [72432.485158] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:11:21 192.168.122.209 [72432.536434] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:11:21 192.168.122.209 [72432.537989] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:11:21 192.168.122.209 [72432.576274] [tempesta fw] Tempesta FW is ready Apr 26 12:11:22 192.168.122.209 [72433.238734] [tdb] Close table 'client0.tdb' Apr 26 12:11:22 192.168.122.209 [72433.413289] [tdb] Close table 'sessions0.tdb' Apr 26 12:11:25 192.168.122.209 [72436.561980] [tdb] Close table 'cache0.tdb' Apr 26 12:11:26 192.168.122.209 [72436.824327] [tdb] Close table 'filter0.tdb' Apr 26 12:11:26 192.168.122.209 [72436.824755] [tempesta fw] modules are stopped Apr 26 12:11:26 192.168.122.209 [72437.029842] [tempesta fw] exiting... Apr 26 12:11:26 192.168.122.209 [72437.162448] [tdb] Shutdown Tempesta DB Apr 26 12:11:26 192.168.122.209 [72437.554025] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_no_store_in_request_and_cache_lvl_2 Apr 26 12:11:26 192.168.122.209 [72437.636971] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_no_store_in_response_and_cache_lvl_1 Apr 26 12:11:28 192.168.122.209 [72439.001905] [tdb] Start Tempesta DB Apr 26 12:11:28 192.168.122.209 [72439.127285] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:11:29 192.168.122.209 [72440.497742] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72440.497742] Maybe that's fine, but it's worth checking the [72440.497742] config - if there is no relations between the [72440.497742] names, then host name confusion attack is possible. Apr 26 12:11:29 192.168.122.209 [72440.588549] [tempesta fw] Configuration processing is completed. Apr 26 12:11:29 192.168.122.209 [72440.645399] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:11:30 192.168.122.209 [72441.062904] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:11:30 192.168.122.209 [72441.089176] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:11:30 192.168.122.209 [72441.114447] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:11:30 192.168.122.209 [72441.368521] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:11:30 192.168.122.209 [72441.370281] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:11:31 192.168.122.209 [72441.944865] [tempesta fw] Tempesta FW is ready Apr 26 12:11:32 192.168.122.209 [72443.586524] [tdb] Close table 'client0.tdb' Apr 26 12:11:33 192.168.122.209 [72443.860036] [tdb] Close table 'sessions0.tdb' Apr 26 12:11:37 192.168.122.209 [72448.383882] [tdb] Close table 'cache0.tdb' Apr 26 12:11:37 192.168.122.209 [72448.590816] [tdb] Close table 'filter0.tdb' Apr 26 12:11:37 192.168.122.209 [72448.591285] [tempesta fw] modules are stopped Apr 26 12:11:38 192.168.122.209 [72448.795120] [tempesta fw] exiting... Apr 26 12:11:38 192.168.122.209 [72448.937433] [tdb] Shutdown Tempesta DB Apr 26 12:11:38 192.168.122.209 [72449.320695] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_no_store_in_response_and_cache_lvl_1 Apr 26 12:11:38 192.168.122.209 [72449.351077] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_no_store_in_response_and_cache_lvl_2 Apr 26 12:11:40 192.168.122.209 [72450.920059] [tdb] Start Tempesta DB Apr 26 12:11:40 192.168.122.209 [72451.099884] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:11:41 192.168.122.209 [72452.481983] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72452.481983] Maybe that's fine, but it's worth checking the [72452.481983] config - if there is no relations between the [72452.481983] names, then host name confusion attack is possible. Apr 26 12:11:41 192.168.122.209 [72452.564711] [tempesta fw] Configuration processing is completed. Apr 26 12:11:41 192.168.122.209 [72452.613084] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:11:42 192.168.122.209 [72453.036403] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:11:42 192.168.122.209 [72453.064280] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:11:42 192.168.122.209 [72453.090507] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:11:42 192.168.122.209 [72453.136699] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:11:42 192.168.122.209 [72453.138446] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:11:42 192.168.122.209 [72453.176649] [tempesta fw] Tempesta FW is ready Apr 26 12:11:43 192.168.122.209 [72453.837352] [tdb] Close table 'client0.tdb' Apr 26 12:11:43 192.168.122.209 [72454.011086] [tdb] Close table 'sessions0.tdb' Apr 26 12:11:46 192.168.122.209 [72457.166925] [tdb] Close table 'cache0.tdb' Apr 26 12:11:46 192.168.122.209 [72457.411894] [tdb] Close table 'filter0.tdb' Apr 26 12:11:46 192.168.122.209 [72457.412378] [tempesta fw] modules are stopped Apr 26 12:11:46 192.168.122.209 [72457.648322] [tempesta fw] exiting... Apr 26 12:11:47 192.168.122.209 [72457.786683] [tdb] Shutdown Tempesta DB Apr 26 12:11:47 192.168.122.209 [72458.216698] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_no_store_in_response_and_cache_lvl_2 Apr 26 12:11:47 192.168.122.209 [72458.249628] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_private_in_response_and_cache_lvl_1 Apr 26 12:11:48 192.168.122.209 [72459.680813] [tdb] Start Tempesta DB Apr 26 12:11:49 192.168.122.209 [72459.814906] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:11:50 192.168.122.209 [72461.214087] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72461.214087] Maybe that's fine, but it's worth checking the [72461.214087] config - if there is no relations between the [72461.214087] names, then host name confusion attack is possible. Apr 26 12:11:50 192.168.122.209 [72461.300892] [tempesta fw] Configuration processing is completed. Apr 26 12:11:50 192.168.122.209 [72461.357526] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:11:51 192.168.122.209 [72461.795631] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:11:51 192.168.122.209 [72461.823928] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:11:51 192.168.122.209 [72461.850978] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:11:51 192.168.122.209 [72461.892781] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:11:51 192.168.122.209 [72461.894505] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:11:51 192.168.122.209 [72461.932827] [tempesta fw] Tempesta FW is ready Apr 26 12:11:51 192.168.122.209 [72462.604099] [tdb] Close table 'client0.tdb' Apr 26 12:11:52 192.168.122.209 [72462.794510] [tdb] Close table 'sessions0.tdb' Apr 26 12:11:55 192.168.122.209 [72465.983717] [tdb] Close table 'cache0.tdb' Apr 26 12:11:55 192.168.122.209 [72466.252357] [tdb] Close table 'filter0.tdb' Apr 26 12:11:55 192.168.122.209 [72466.252839] [tempesta fw] modules are stopped Apr 26 12:11:55 192.168.122.209 [72466.454827] [tempesta fw] exiting... Apr 26 12:11:55 192.168.122.209 [72466.622542] [tdb] Shutdown Tempesta DB Apr 26 12:11:56 192.168.122.209 [72467.047673] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_private_in_response_and_cache_lvl_1 Apr 26 12:11:56 192.168.122.209 [72467.077323] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_private_in_response_and_cache_lvl_2 Apr 26 12:11:57 192.168.122.209 [72468.516240] [tdb] Start Tempesta DB Apr 26 12:11:57 192.168.122.209 [72468.676975] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:11:59 192.168.122.209 [72470.098162] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72470.098162] Maybe that's fine, but it's worth checking the [72470.098162] config - if there is no relations between the [72470.098162] names, then host name confusion attack is possible. Apr 26 12:11:59 192.168.122.209 [72470.184934] [tempesta fw] Configuration processing is completed. Apr 26 12:11:59 192.168.122.209 [72470.242778] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:12:00 192.168.122.209 [72470.737965] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:12:00 192.168.122.209 [72470.769265] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:12:00 192.168.122.209 [72470.800984] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:12:00 192.168.122.209 [72470.848905] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:12:00 192.168.122.209 [72470.850620] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:12:00 192.168.122.209 [72470.892855] [tempesta fw] Tempesta FW is ready Apr 26 12:12:00 192.168.122.209 [72471.582737] [tdb] Close table 'client0.tdb' Apr 26 12:12:01 192.168.122.209 [72471.777695] [tdb] Close table 'sessions0.tdb' Apr 26 12:12:04 192.168.122.209 [72474.905323] [tdb] Close table 'cache0.tdb' Apr 26 12:12:04 192.168.122.209 [72475.175821] [tdb] Close table 'filter0.tdb' Apr 26 12:12:04 192.168.122.209 [72475.176259] [tempesta fw] modules are stopped Apr 26 12:12:04 192.168.122.209 [72475.367018] [tempesta fw] exiting... Apr 26 12:12:04 192.168.122.209 [72475.512576] [tdb] Shutdown Tempesta DB Apr 26 12:12:05 192.168.122.209 [72475.923549] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_cc_private_in_response_and_cache_lvl_2 Apr 26 12:12:05 192.168.122.209 [72475.956148] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_pragma_no_cache_in_request_and_cache_lvl_1 Apr 26 12:12:06 192.168.122.209 [72477.380777] [tdb] Start Tempesta DB Apr 26 12:12:06 192.168.122.209 [72477.521365] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:12:08 192.168.122.209 [72478.894265] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72478.894265] Maybe that's fine, but it's worth checking the [72478.894265] config - if there is no relations between the [72478.894265] names, then host name confusion attack is possible. Apr 26 12:12:08 192.168.122.209 [72478.985033] [tempesta fw] Configuration processing is completed. Apr 26 12:12:08 192.168.122.209 [72479.042483] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:12:08 192.168.122.209 [72479.461754] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:12:08 192.168.122.209 [72479.489217] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:12:08 192.168.122.209 [72479.516667] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:12:08 192.168.122.209 [72479.560984] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:12:08 192.168.122.209 [72479.562760] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:12:08 192.168.122.209 [72479.608941] [tempesta fw] Tempesta FW is ready Apr 26 12:12:09 192.168.122.209 [72480.262280] [tdb] Close table 'client0.tdb' Apr 26 12:12:09 192.168.122.209 [72480.444780] [tdb] Close table 'sessions0.tdb' Apr 26 12:12:12 192.168.122.209 [72483.611113] [tdb] Close table 'cache0.tdb' Apr 26 12:12:13 192.168.122.209 [72483.888119] [tdb] Close table 'filter0.tdb' Apr 26 12:12:13 192.168.122.209 [72483.888580] [tempesta fw] modules are stopped Apr 26 12:12:13 192.168.122.209 [72484.078354] [tempesta fw] exiting... Apr 26 12:12:13 192.168.122.209 [72484.232561] [tdb] Shutdown Tempesta DB Apr 26 12:12:13 192.168.122.209 [72484.619491] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_pragma_no_cache_in_request_and_cache_lvl_1 Apr 26 12:12:14 192.168.122.209 [72484.719578] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_pragma_no_cache_in_request_and_cache_lvl_2 Apr 26 12:12:15 192.168.122.209 [72486.151636] [tdb] Start Tempesta DB Apr 26 12:12:15 192.168.122.209 [72486.288886] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:12:16 192.168.122.209 [72487.666467] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72487.666467] Maybe that's fine, but it's worth checking the [72487.666467] config - if there is no relations between the [72487.666467] names, then host name confusion attack is possible. Apr 26 12:12:17 192.168.122.209 [72487.749269] [tempesta fw] Configuration processing is completed. Apr 26 12:12:17 192.168.122.209 [72487.807537] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:12:17 192.168.122.209 [72488.246333] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:12:17 192.168.122.209 [72488.273350] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:12:17 192.168.122.209 [72488.301115] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:12:17 192.168.122.209 [72488.341116] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:12:17 192.168.122.209 [72488.341266] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:12:17 192.168.122.209 [72488.381061] [tempesta fw] Tempesta FW is ready Apr 26 12:12:18 192.168.122.209 [72489.064068] [tdb] Close table 'client0.tdb' Apr 26 12:12:18 192.168.122.209 [72489.271318] [tdb] Close table 'sessions0.tdb' Apr 26 12:12:21 192.168.122.209 [72492.613016] [tdb] Close table 'cache0.tdb' Apr 26 12:12:22 192.168.122.209 [72492.892405] [tdb] Close table 'filter0.tdb' Apr 26 12:12:22 192.168.122.209 [72492.892810] [tempesta fw] modules are stopped Apr 26 12:12:22 192.168.122.209 [72493.081191] [tempesta fw] exiting... Apr 26 12:12:22 192.168.122.209 [72493.199644] [tdb] Shutdown Tempesta DB Apr 26 12:12:22 192.168.122.209 [72493.553164] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_pragma_no_cache_in_request_and_cache_lvl_2 Apr 26 12:12:22 192.168.122.209 [72493.583704] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_pragma_no_cache_in_response_and_cache_lvl_1 Apr 26 12:12:24 192.168.122.209 [72495.058280] [tdb] Start Tempesta DB Apr 26 12:12:24 192.168.122.209 [72495.214699] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:12:25 192.168.122.209 [72496.674632] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72496.674632] Maybe that's fine, but it's worth checking the [72496.674632] config - if there is no relations between the [72496.674632] names, then host name confusion attack is possible. Apr 26 12:12:26 192.168.122.209 [72496.761300] [tempesta fw] Configuration processing is completed. Apr 26 12:12:26 192.168.122.209 [72496.819954] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:12:26 192.168.122.209 [72497.256058] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:12:26 192.168.122.209 [72497.283983] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:12:26 192.168.122.209 [72497.312017] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:12:26 192.168.122.209 [72497.369245] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:12:26 192.168.122.209 [72497.371034] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:12:26 192.168.122.209 [72497.409164] [tempesta fw] Tempesta FW is ready Apr 26 12:12:27 192.168.122.209 [72498.070387] [tdb] Close table 'client0.tdb' Apr 26 12:12:27 192.168.122.209 [72498.252666] [tdb] Close table 'sessions0.tdb' Apr 26 12:12:30 192.168.122.209 [72501.456032] [tdb] Close table 'cache0.tdb' Apr 26 12:12:30 192.168.122.209 [72501.699272] [tdb] Close table 'filter0.tdb' Apr 26 12:12:30 192.168.122.209 [72501.699719] [tempesta fw] modules are stopped Apr 26 12:12:31 192.168.122.209 [72501.880379] [tempesta fw] exiting... Apr 26 12:12:31 192.168.122.209 [72501.991467] [tdb] Shutdown Tempesta DB Apr 26 12:12:31 192.168.122.209 [72502.410872] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_pragma_no_cache_in_response_and_cache_lvl_1 Apr 26 12:12:31 192.168.122.209 [72502.447256] Start test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_pragma_no_cache_in_response_and_cache_lvl_2 Apr 26 12:12:33 192.168.122.209 [72503.837471] [tdb] Start Tempesta DB Apr 26 12:12:33 192.168.122.209 [72503.976361] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:12:34 192.168.122.209 [72505.402572] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72505.402572] Maybe that's fine, but it's worth checking the [72505.402572] config - if there is no relations between the [72505.402572] names, then host name confusion attack is possible. Apr 26 12:12:34 192.168.122.209 [72505.489395] [tempesta fw] Configuration processing is completed. Apr 26 12:12:34 192.168.122.209 [72505.558010] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:12:35 192.168.122.209 [72505.982331] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:12:35 192.168.122.209 [72506.008162] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:12:35 192.168.122.209 [72506.033464] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:12:35 192.168.122.209 [72506.085332] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:12:35 192.168.122.209 [72506.087068] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:12:35 192.168.122.209 [72506.137269] [tempesta fw] Tempesta FW is ready Apr 26 12:12:36 192.168.122.209 [72506.777872] [tdb] Close table 'client0.tdb' Apr 26 12:12:36 192.168.122.209 [72506.978313] [tdb] Close table 'sessions0.tdb' Apr 26 12:12:39 192.168.122.209 [72510.122381] [tdb] Close table 'cache0.tdb' Apr 26 12:12:39 192.168.122.209 [72510.395291] [tdb] Close table 'filter0.tdb' Apr 26 12:12:39 192.168.122.209 [72510.395719] [tempesta fw] modules are stopped Apr 26 12:12:39 192.168.122.209 [72510.580286] [tempesta fw] exiting... Apr 26 12:12:39 192.168.122.209 [72510.698348] [tdb] Shutdown Tempesta DB Apr 26 12:12:40 192.168.122.209 [72511.089807] End test: cache.test_cache_deception_attack.TestCacheDeceptionAttackH2.test_pragma_no_cache_in_response_and_cache_lvl_2 Apr 26 12:12:40 192.168.122.209 [72511.124064] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_max_stale Apr 26 12:12:41 192.168.122.209 [72512.643414] [tdb] Start Tempesta DB Apr 26 12:12:42 192.168.122.209 [72512.777047] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:12:43 192.168.122.209 [72514.311220] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72514.311220] Maybe that's fine, but it's worth checking the [72514.311220] config - if there is no relations between the [72514.311220] names, then host name confusion attack is possible. Apr 26 12:12:43 192.168.122.209 [72514.409862] [tempesta fw] Configuration processing is completed. Apr 26 12:12:43 192.168.122.209 [72514.465488] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:12:44 192.168.122.209 [72514.884276] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:12:44 192.168.122.209 [72514.910646] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:12:44 192.168.122.209 [72514.936069] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:12:44 192.168.122.209 [72514.981424] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:12:44 192.168.122.209 [72515.025396] [tempesta fw] Tempesta FW is ready Apr 26 12:12:55 192.168.122.209 [72526.655670] [tdb] Close table 'client0.tdb' Apr 26 12:12:56 192.168.122.209 [72526.839251] [tdb] Close table 'sessions0.tdb' Apr 26 12:12:59 192.168.122.209 [72529.991183] [tdb] Close table 'cache0.tdb' Apr 26 12:12:59 192.168.122.209 [72530.253288] [tdb] Close table 'filter0.tdb' Apr 26 12:12:59 192.168.122.209 [72530.253752] [tempesta fw] modules are stopped Apr 26 12:12:59 192.168.122.209 [72530.444676] [tempesta fw] exiting... Apr 26 12:12:59 192.168.122.209 [72530.578915] [tdb] Shutdown Tempesta DB Apr 26 12:13:00 192.168.122.209 [72530.943557] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_max_stale Apr 26 12:13:00 192.168.122.209 [72530.977750] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_stale_if_error_not_use_304 Apr 26 12:13:01 192.168.122.209 [72532.325654] [tdb] Start Tempesta DB Apr 26 12:13:01 192.168.122.209 [72532.449213] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:13:03 192.168.122.209 [72533.995322] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72533.995322] Maybe that's fine, but it's worth checking the [72533.995322] config - if there is no relations between the [72533.995322] names, then host name confusion attack is possible. Apr 26 12:13:03 192.168.122.209 [72534.077956] [tempesta fw] Configuration processing is completed. Apr 26 12:13:03 192.168.122.209 [72534.132850] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:13:03 192.168.122.209 [72534.550291] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:13:03 192.168.122.209 [72534.576445] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:13:03 192.168.122.209 [72534.602358] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:13:03 192.168.122.209 [72534.657677] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:13:03 192.168.122.209 [72534.713641] [tempesta fw] Tempesta FW is ready Apr 26 12:13:06 192.168.122.209 [72537.438670] [tdb] Close table 'client0.tdb' Apr 26 12:13:06 192.168.122.209 [72537.623460] [tdb] Close table 'sessions0.tdb' Apr 26 12:13:10 192.168.122.209 [72540.777885] [tdb] Close table 'cache0.tdb' Apr 26 12:13:10 192.168.122.209 [72541.019058] [tdb] Close table 'filter0.tdb' Apr 26 12:13:10 192.168.122.209 [72541.019527] [tempesta fw] modules are stopped Apr 26 12:13:10 192.168.122.209 [72541.223740] [tempesta fw] exiting... Apr 26 12:13:10 192.168.122.209 [72541.354963] [tdb] Shutdown Tempesta DB Apr 26 12:13:10 192.168.122.209 [72541.714469] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_stale_if_error_not_use_304 Apr 26 12:13:11 192.168.122.209 [72541.737382] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_fresh_200 Apr 26 12:13:12 192.168.122.209 [72543.253274] [tdb] Start Tempesta DB Apr 26 12:13:12 192.168.122.209 [72543.386046] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:13:14 192.168.122.209 [72544.867483] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72544.867483] Maybe that's fine, but it's worth checking the [72544.867483] config - if there is no relations between the [72544.867483] names, then host name confusion attack is possible. Apr 26 12:13:14 192.168.122.209 [72544.966107] [tempesta fw] Configuration processing is completed. Apr 26 12:13:14 192.168.122.209 [72545.028815] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:13:14 192.168.122.209 [72545.465148] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:13:14 192.168.122.209 [72545.492059] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:13:14 192.168.122.209 [72545.519025] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:13:14 192.168.122.209 [72545.577803] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:13:14 192.168.122.209 [72545.621757] [tempesta fw] Tempesta FW is ready Apr 26 12:13:18 192.168.122.209 [72549.232615] [tdb] Close table 'client0.tdb' Apr 26 12:13:18 192.168.122.209 [72549.405651] [tdb] Close table 'sessions0.tdb' Apr 26 12:13:21 192.168.122.209 [72552.581663] [tdb] Close table 'cache0.tdb' Apr 26 12:13:22 192.168.122.209 [72552.825948] [tdb] Close table 'filter0.tdb' Apr 26 12:13:22 192.168.122.209 [72552.826353] [tempesta fw] modules are stopped Apr 26 12:13:22 192.168.122.209 [72553.027589] [tempesta fw] exiting... Apr 26 12:13:22 192.168.122.209 [72553.175039] [tdb] Shutdown Tempesta DB Apr 26 12:13:22 192.168.122.209 [72553.612726] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_fresh_200 Apr 26 12:13:22 192.168.122.209 [72553.647274] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_fresh_403 Apr 26 12:13:24 192.168.122.209 [72555.141254] [tdb] Start Tempesta DB Apr 26 12:13:24 192.168.122.209 [72555.267755] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:13:26 192.168.122.209 [72556.767692] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72556.767692] Maybe that's fine, but it's worth checking the [72556.767692] config - if there is no relations between the [72556.767692] names, then host name confusion attack is possible. Apr 26 12:13:26 192.168.122.209 [72556.858284] [tempesta fw] Configuration processing is completed. Apr 26 12:13:26 192.168.122.209 [72556.915118] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:13:26 192.168.122.209 [72557.350960] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:13:26 192.168.122.209 [72557.376499] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:13:26 192.168.122.209 [72557.401758] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:13:26 192.168.122.209 [72557.441948] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:13:26 192.168.122.209 [72557.481897] [tempesta fw] Tempesta FW is ready Apr 26 12:13:30 192.168.122.209 [72561.125710] [tdb] Close table 'client0.tdb' Apr 26 12:13:30 192.168.122.209 [72561.311511] [tdb] Close table 'sessions0.tdb' Apr 26 12:13:33 192.168.122.209 [72564.509584] [tdb] Close table 'cache0.tdb' Apr 26 12:13:34 192.168.122.209 [72564.753261] [tdb] Close table 'filter0.tdb' Apr 26 12:13:34 192.168.122.209 [72564.753667] [tempesta fw] modules are stopped Apr 26 12:13:34 192.168.122.209 [72564.953130] [tempesta fw] exiting... Apr 26 12:13:34 192.168.122.209 [72565.070088] [tdb] Shutdown Tempesta DB Apr 26 12:13:34 192.168.122.209 [72565.443262] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_fresh_403 Apr 26 12:13:34 192.168.122.209 [72565.477364] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_fresh_on_error_must_revalidate Apr 26 12:13:36 192.168.122.209 [72566.910212] [tdb] Start Tempesta DB Apr 26 12:13:36 192.168.122.209 [72567.036154] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:13:37 192.168.122.209 [72568.467757] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72568.467757] Maybe that's fine, but it's worth checking the [72568.467757] config - if there is no relations between the [72568.467757] names, then host name confusion attack is possible. Apr 26 12:13:37 192.168.122.209 [72568.574073] [tempesta fw] Configuration processing is completed. Apr 26 12:13:37 192.168.122.209 [72568.637640] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:13:38 192.168.122.209 [72569.071216] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:13:38 192.168.122.209 [72569.098285] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:13:38 192.168.122.209 [72569.124461] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:13:38 192.168.122.209 [72569.170104] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:13:38 192.168.122.209 [72569.218061] [tempesta fw] Tempesta FW is ready Apr 26 12:13:42 192.168.122.209 [72572.843930] [tdb] Close table 'client0.tdb' Apr 26 12:13:42 192.168.122.209 [72573.030754] [tdb] Close table 'sessions0.tdb' Apr 26 12:13:45 192.168.122.209 [72576.201905] [tdb] Close table 'cache0.tdb' Apr 26 12:13:45 192.168.122.209 [72576.443000] [tdb] Close table 'filter0.tdb' Apr 26 12:13:45 192.168.122.209 [72576.443424] [tempesta fw] modules are stopped Apr 26 12:13:45 192.168.122.209 [72576.636498] [tempesta fw] exiting... Apr 26 12:13:46 192.168.122.209 [72576.791540] [tdb] Shutdown Tempesta DB Apr 26 12:13:46 192.168.122.209 [72577.189330] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_fresh_on_error_must_revalidate Apr 26 12:13:46 192.168.122.209 [72577.223620] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_fresh_on_error_proxy_revalidate Apr 26 12:13:47 192.168.122.209 [72578.687143] [tdb] Start Tempesta DB Apr 26 12:13:48 192.168.122.209 [72578.834629] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:13:49 192.168.122.209 [72580.355894] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72580.355894] Maybe that's fine, but it's worth checking the [72580.355894] config - if there is no relations between the [72580.355894] names, then host name confusion attack is possible. Apr 26 12:13:49 192.168.122.209 [72580.450530] [tempesta fw] Configuration processing is completed. Apr 26 12:13:49 192.168.122.209 [72580.503955] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:13:50 192.168.122.209 [72580.900355] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:13:50 192.168.122.209 [72580.925274] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:13:50 192.168.122.209 [72580.950436] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:13:50 192.168.122.209 [72581.022244] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:13:50 192.168.122.209 [72581.062109] [tempesta fw] Tempesta FW is ready Apr 26 12:13:53 192.168.122.209 [72584.661578] [tdb] Close table 'client0.tdb' Apr 26 12:13:54 192.168.122.209 [72584.864799] [tdb] Close table 'sessions0.tdb' Apr 26 12:13:57 192.168.122.209 [72587.974556] [tdb] Close table 'cache0.tdb' Apr 26 12:13:57 192.168.122.209 [72588.233370] [tdb] Close table 'filter0.tdb' Apr 26 12:13:57 192.168.122.209 [72588.233805] [tempesta fw] modules are stopped Apr 26 12:13:57 192.168.122.209 [72588.424747] [tempesta fw] exiting... Apr 26 12:13:57 192.168.122.209 [72588.553163] [tdb] Shutdown Tempesta DB Apr 26 12:13:58 192.168.122.209 [72588.920377] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_fresh_on_error_proxy_revalidate Apr 26 12:13:58 192.168.122.209 [72588.954202] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_fresh_on_error_s_maxage Apr 26 12:13:59 192.168.122.209 [72590.472145] [tdb] Start Tempesta DB Apr 26 12:13:59 192.168.122.209 [72590.602655] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:14:01 192.168.122.209 [72592.008080] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72592.008080] Maybe that's fine, but it's worth checking the [72592.008080] config - if there is no relations between the [72592.008080] names, then host name confusion attack is possible. Apr 26 12:14:01 192.168.122.209 [72592.138290] [tempesta fw] Configuration processing is completed. Apr 26 12:14:01 192.168.122.209 [72592.207830] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:14:01 192.168.122.209 [72592.638426] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:14:01 192.168.122.209 [72592.665306] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:14:01 192.168.122.209 [72592.691338] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:14:02 192.168.122.209 [72592.730317] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:14:02 192.168.122.209 [72592.778365] [tempesta fw] Tempesta FW is ready Apr 26 12:14:05 192.168.122.209 [72596.392325] [tdb] Close table 'client0.tdb' Apr 26 12:14:05 192.168.122.209 [72596.562941] [tdb] Close table 'sessions0.tdb' Apr 26 12:14:08 192.168.122.209 [72599.710995] [tdb] Close table 'cache0.tdb' Apr 26 12:14:09 192.168.122.209 [72599.946233] [tdb] Close table 'filter0.tdb' Apr 26 12:14:09 192.168.122.209 [72599.947075] [tempesta fw] modules are stopped Apr 26 12:14:09 192.168.122.209 [72600.158910] [tempesta fw] exiting... Apr 26 12:14:09 192.168.122.209 [72600.273334] [tdb] Shutdown Tempesta DB Apr 26 12:14:09 192.168.122.209 [72600.671740] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_fresh_on_error_s_maxage Apr 26 12:14:09 192.168.122.209 [72600.703149] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_400 Apr 26 12:14:11 192.168.122.209 [72602.232796] [tdb] Start Tempesta DB Apr 26 12:14:11 192.168.122.209 [72602.358739] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:14:13 192.168.122.209 [72603.764213] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72603.764213] Maybe that's fine, but it's worth checking the [72603.764213] config - if there is no relations between the [72603.764213] names, then host name confusion attack is possible. Apr 26 12:14:13 192.168.122.209 [72603.859732] [tempesta fw] Configuration processing is completed. Apr 26 12:14:13 192.168.122.209 [72603.920615] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:14:13 192.168.122.209 [72604.348375] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:14:13 192.168.122.209 [72604.375016] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:14:13 192.168.122.209 [72604.401360] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:14:13 192.168.122.209 [72604.438547] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:14:13 192.168.122.209 [72604.486432] [tempesta fw] Tempesta FW is ready Apr 26 12:14:17 192.168.122.209 [72608.115494] [tdb] Close table 'client0.tdb' Apr 26 12:14:17 192.168.122.209 [72608.289650] [tdb] Close table 'sessions0.tdb' Apr 26 12:14:20 192.168.122.209 [72611.409323] [tdb] Close table 'cache0.tdb' Apr 26 12:14:20 192.168.122.209 [72611.656404] [tdb] Close table 'filter0.tdb' Apr 26 12:14:20 192.168.122.209 [72611.656885] [tempesta fw] modules are stopped Apr 26 12:14:21 192.168.122.209 [72611.840617] [tempesta fw] exiting... Apr 26 12:14:21 192.168.122.209 [72611.958160] [tdb] Shutdown Tempesta DB Apr 26 12:14:21 192.168.122.209 [72612.340535] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_400 Apr 26 12:14:21 192.168.122.209 [72612.423229] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_4xx_400 Apr 26 12:14:23 192.168.122.209 [72613.945562] [tdb] Start Tempesta DB Apr 26 12:14:23 192.168.122.209 [72614.075150] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:14:24 192.168.122.209 [72615.528208] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72615.528208] Maybe that's fine, but it's worth checking the [72615.528208] config - if there is no relations between the [72615.528208] names, then host name confusion attack is possible. Apr 26 12:14:24 192.168.122.209 [72615.622606] [tempesta fw] Configuration processing is completed. Apr 26 12:14:24 192.168.122.209 [72615.680285] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:14:25 192.168.122.209 [72616.114726] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:14:25 192.168.122.209 [72616.142377] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:14:25 192.168.122.209 [72616.171281] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:14:25 192.168.122.209 [72616.210710] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:14:25 192.168.122.209 [72616.262617] [tempesta fw] Tempesta FW is ready Apr 26 12:14:29 192.168.122.209 [72619.962172] [tdb] Close table 'client0.tdb' Apr 26 12:14:29 192.168.122.209 [72620.127703] [tdb] Close table 'sessions0.tdb' Apr 26 12:14:32 192.168.122.209 [72623.277609] [tdb] Close table 'cache0.tdb' Apr 26 12:14:32 192.168.122.209 [72623.552633] [tdb] Close table 'filter0.tdb' Apr 26 12:14:32 192.168.122.209 [72623.553032] [tempesta fw] modules are stopped Apr 26 12:14:33 192.168.122.209 [72623.724250] [tempesta fw] exiting... Apr 26 12:14:33 192.168.122.209 [72623.868018] [tdb] Shutdown Tempesta DB Apr 26 12:14:33 192.168.122.209 [72624.232262] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_4xx_400 Apr 26 12:14:33 192.168.122.209 [72624.261877] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_4xx_403 Apr 26 12:14:35 192.168.122.209 [72625.753400] [tdb] Start Tempesta DB Apr 26 12:14:35 192.168.122.209 [72625.879653] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:14:36 192.168.122.209 [72627.344504] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72627.344504] Maybe that's fine, but it's worth checking the [72627.344504] config - if there is no relations between the [72627.344504] names, then host name confusion attack is possible. Apr 26 12:14:36 192.168.122.209 [72627.454812] [tempesta fw] Configuration processing is completed. Apr 26 12:14:36 192.168.122.209 [72627.513227] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:14:37 192.168.122.209 [72627.942502] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:14:37 192.168.122.209 [72627.970337] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:14:37 192.168.122.209 [72627.997536] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:14:37 192.168.122.209 [72628.046831] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:14:37 192.168.122.209 [72628.106789] [tempesta fw] Tempesta FW is ready Apr 26 12:14:41 192.168.122.209 [72631.765298] [tdb] Close table 'client0.tdb' Apr 26 12:14:41 192.168.122.209 [72631.943504] [tdb] Close table 'sessions0.tdb' Apr 26 12:14:44 192.168.122.209 [72635.105897] [tdb] Close table 'cache0.tdb' Apr 26 12:14:44 192.168.122.209 [72635.341239] [tdb] Close table 'filter0.tdb' Apr 26 12:14:44 192.168.122.209 [72635.341672] [tempesta fw] modules are stopped Apr 26 12:14:44 192.168.122.209 [72635.541781] [tempesta fw] exiting... Apr 26 12:14:44 192.168.122.209 [72635.670038] [tdb] Shutdown Tempesta DB Apr 26 12:14:45 192.168.122.209 [72636.004797] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_4xx_403 Apr 26 12:14:45 192.168.122.209 [72636.036892] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_4xx_5xx Apr 26 12:14:46 192.168.122.209 [72637.562098] [tdb] Start Tempesta DB Apr 26 12:14:46 192.168.122.209 [72637.689878] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:14:48 192.168.122.209 [72639.136626] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72639.136626] Maybe that's fine, but it's worth checking the [72639.136626] config - if there is no relations between the [72639.136626] names, then host name confusion attack is possible. Apr 26 12:14:48 192.168.122.209 [72639.235337] [tempesta fw] Configuration processing is completed. Apr 26 12:14:48 192.168.122.209 [72639.286652] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:14:48 192.168.122.209 [72639.697758] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:14:49 192.168.122.209 [72639.723842] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:14:49 192.168.122.209 [72639.749166] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:14:49 192.168.122.209 [72639.794961] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:14:49 192.168.122.209 [72639.838931] [tempesta fw] Tempesta FW is ready Apr 26 12:14:52 192.168.122.209 [72643.485083] [tdb] Close table 'client0.tdb' Apr 26 12:14:52 192.168.122.209 [72643.669359] [tdb] Close table 'sessions0.tdb' Apr 26 12:14:56 192.168.122.209 [72646.851019] [tdb] Close table 'cache0.tdb' Apr 26 12:14:56 192.168.122.209 [72647.095548] [tdb] Close table 'filter0.tdb' Apr 26 12:14:56 192.168.122.209 [72647.095979] [tempesta fw] modules are stopped Apr 26 12:14:56 192.168.122.209 [72647.272927] [tempesta fw] exiting... Apr 26 12:14:56 192.168.122.209 [72647.401895] [tdb] Shutdown Tempesta DB Apr 26 12:14:57 192.168.122.209 [72647.792114] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_4xx_5xx Apr 26 12:14:57 192.168.122.209 [72647.827003] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_500 Apr 26 12:14:58 192.168.122.209 [72649.213055] [tdb] Start Tempesta DB Apr 26 12:14:58 192.168.122.209 [72649.356015] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:15:00 192.168.122.209 [72650.792830] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72650.792830] Maybe that's fine, but it's worth checking the [72650.792830] config - if there is no relations between the [72650.792830] names, then host name confusion attack is possible. Apr 26 12:15:00 192.168.122.209 [72650.887599] [tempesta fw] Configuration processing is completed. Apr 26 12:15:00 192.168.122.209 [72650.951212] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:15:00 192.168.122.209 [72651.364180] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:15:00 192.168.122.209 [72651.389854] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:15:00 192.168.122.209 [72651.415047] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:15:00 192.168.122.209 [72651.479144] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:15:00 192.168.122.209 [72651.519075] [tempesta fw] Tempesta FW is ready Apr 26 12:15:04 192.168.122.209 [72655.158212] [tdb] Close table 'client0.tdb' Apr 26 12:15:04 192.168.122.209 [72655.335790] [tdb] Close table 'sessions0.tdb' Apr 26 12:15:07 192.168.122.209 [72658.510882] [tdb] Close table 'cache0.tdb' Apr 26 12:15:08 192.168.122.209 [72658.766369] [tdb] Close table 'filter0.tdb' Apr 26 12:15:08 192.168.122.209 [72658.766799] [tempesta fw] modules are stopped Apr 26 12:15:08 192.168.122.209 [72658.936411] [tempesta fw] exiting... Apr 26 12:15:08 192.168.122.209 [72659.075274] [tdb] Shutdown Tempesta DB Apr 26 12:15:08 192.168.122.209 [72659.514573] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_500 Apr 26 12:15:08 192.168.122.209 [72659.562886] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_5xx_500 Apr 26 12:15:10 192.168.122.209 [72661.043527] [tdb] Start Tempesta DB Apr 26 12:15:10 192.168.122.209 [72661.180723] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:15:11 192.168.122.209 [72662.596881] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72662.596881] Maybe that's fine, but it's worth checking the [72662.596881] config - if there is no relations between the [72662.596881] names, then host name confusion attack is possible. Apr 26 12:15:11 192.168.122.209 [72662.687538] [tempesta fw] Configuration processing is completed. Apr 26 12:15:12 192.168.122.209 [72662.746611] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:15:12 192.168.122.209 [72663.158804] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:15:12 192.168.122.209 [72663.185104] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:15:12 192.168.122.209 [72663.210777] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:15:12 192.168.122.209 [72663.259246] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:15:12 192.168.122.209 [72663.315239] [tempesta fw] Tempesta FW is ready Apr 26 12:15:16 192.168.122.209 [72666.882172] [tdb] Close table 'client0.tdb' Apr 26 12:15:16 192.168.122.209 [72667.066689] [tdb] Close table 'sessions0.tdb' Apr 26 12:15:19 192.168.122.209 [72670.202558] [tdb] Close table 'cache0.tdb' Apr 26 12:15:19 192.168.122.209 [72670.469104] [tdb] Close table 'filter0.tdb' Apr 26 12:15:19 192.168.122.209 [72670.469578] [tempesta fw] modules are stopped Apr 26 12:15:19 192.168.122.209 [72670.667437] [tempesta fw] exiting... Apr 26 12:15:20 192.168.122.209 [72670.813939] [tdb] Shutdown Tempesta DB Apr 26 12:15:20 192.168.122.209 [72671.187843] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_5xx_500 Apr 26 12:15:20 192.168.122.209 [72671.258455] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_5xx_502 Apr 26 12:15:21 192.168.122.209 [72672.577653] [tdb] Start Tempesta DB Apr 26 12:15:21 192.168.122.209 [72672.714263] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:15:23 192.168.122.209 [72674.221100] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72674.221100] Maybe that's fine, but it's worth checking the [72674.221100] config - if there is no relations between the [72674.221100] names, then host name confusion attack is possible. Apr 26 12:15:23 192.168.122.209 [72674.319691] [tempesta fw] Configuration processing is completed. Apr 26 12:15:23 192.168.122.209 [72674.370786] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:15:24 192.168.122.209 [72674.788015] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:15:24 192.168.122.209 [72674.813725] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:15:24 192.168.122.209 [72674.839832] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:15:24 192.168.122.209 [72674.899401] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:15:24 192.168.122.209 [72674.943357] [tempesta fw] Tempesta FW is ready Apr 26 12:15:27 192.168.122.209 [72678.526605] [tdb] Close table 'client0.tdb' Apr 26 12:15:27 192.168.122.209 [72678.707769] [tdb] Close table 'sessions0.tdb' Apr 26 12:15:31 192.168.122.209 [72681.820271] [tdb] Close table 'cache0.tdb' Apr 26 12:15:31 192.168.122.209 [72682.069458] [tdb] Close table 'filter0.tdb' Apr 26 12:15:31 192.168.122.209 [72682.069886] [tempesta fw] modules are stopped Apr 26 12:15:31 192.168.122.209 [72682.300455] [tempesta fw] exiting... Apr 26 12:15:31 192.168.122.209 [72682.449653] [tdb] Shutdown Tempesta DB Apr 26 12:15:32 192.168.122.209 [72682.827977] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_5xx_502 Apr 26 12:15:32 192.168.122.209 [72682.876784] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_if_error_duplicated_req Apr 26 12:15:33 192.168.122.209 [72684.154169] [tdb] Start Tempesta DB Apr 26 12:15:33 192.168.122.209 [72684.292143] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:15:34 192.168.122.209 [72685.649174] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72685.649174] Maybe that's fine, but it's worth checking the [72685.649174] config - if there is no relations between the [72685.649174] names, then host name confusion attack is possible. Apr 26 12:15:35 192.168.122.209 [72685.727791] [tempesta fw] Configuration processing is completed. Apr 26 12:15:35 192.168.122.209 [72685.788574] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:15:35 192.168.122.209 [72686.190921] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:15:35 192.168.122.209 [72686.216558] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:15:35 192.168.122.209 [72686.242175] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:15:35 192.168.122.209 [72686.283544] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:15:35 192.168.122.209 [72686.383491] [tempesta fw] Tempesta FW is ready Apr 26 12:15:36 192.168.122.209 [72686.969694] [tdb] Close table 'client0.tdb' Apr 26 12:15:36 192.168.122.209 [72687.151492] [tdb] Close table 'sessions0.tdb' Apr 26 12:15:39 192.168.122.209 [72690.326691] [tdb] Close table 'cache0.tdb' Apr 26 12:15:39 192.168.122.209 [72690.583194] [tdb] Close table 'filter0.tdb' Apr 26 12:15:39 192.168.122.209 [72690.583656] [tempesta fw] modules are stopped Apr 26 12:15:40 192.168.122.209 [72690.772000] [tempesta fw] exiting... Apr 26 12:15:40 192.168.122.209 [72690.913583] [tdb] Shutdown Tempesta DB Apr 26 12:15:40 192.168.122.209 [72691.281905] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_if_error_duplicated_req Apr 26 12:15:40 192.168.122.209 [72691.312132] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_if_error_duplicated_resp Apr 26 12:15:41 192.168.122.209 [72692.634448] [tdb] Start Tempesta DB Apr 26 12:15:42 192.168.122.209 [72692.763905] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:15:43 192.168.122.209 [72694.169297] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72694.169297] Maybe that's fine, but it's worth checking the [72694.169297] config - if there is no relations between the [72694.169297] names, then host name confusion attack is possible. Apr 26 12:15:43 192.168.122.209 [72694.251948] [tempesta fw] Configuration processing is completed. Apr 26 12:15:43 192.168.122.209 [72694.309632] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:15:44 192.168.122.209 [72694.731652] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:15:44 192.168.122.209 [72694.758587] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:15:44 192.168.122.209 [72694.784581] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:15:44 192.168.122.209 [72694.831643] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:15:44 192.168.122.209 [72694.875593] [tempesta fw] Tempesta FW is ready Apr 26 12:15:44 192.168.122.209 [72695.072008] [tempesta fw] Warning: Parser error: state=Resp_HdrCache_CtrlV input(-0)=0x72('ror=20, stale-if-error=19 [72695.072008] date: Sat, 26 Apr 202') data_len=66 off=0 Apr 26 12:15:44 192.168.122.209 [72695.075739] [tempesta fw] Warning: response dropped: processing error: 192.168.122.196 Apr 26 12:15:44 192.168.122.209 [72695.524509] [tdb] Close table 'client0.tdb' Apr 26 12:15:44 192.168.122.209 [72695.715338] [tdb] Close table 'sessions0.tdb' Apr 26 12:15:48 192.168.122.209 [72698.862958] [tdb] Close table 'cache0.tdb' Apr 26 12:15:48 192.168.122.209 [72699.098906] [tdb] Close table 'filter0.tdb' Apr 26 12:15:48 192.168.122.209 [72699.099356] [tempesta fw] modules are stopped Apr 26 12:15:48 192.168.122.209 [72699.285188] [tempesta fw] exiting... Apr 26 12:15:48 192.168.122.209 [72699.418420] [tdb] Shutdown Tempesta DB Apr 26 12:15:49 192.168.122.209 [72699.817106] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_if_error_duplicated_resp Apr 26 12:15:49 192.168.122.209 [72699.851338] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_if_error_param_req Apr 26 12:15:50 192.168.122.209 [72701.158110] [tdb] Start Tempesta DB Apr 26 12:15:50 192.168.122.209 [72701.294053] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:15:52 192.168.122.209 [72702.765418] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72702.765418] Maybe that's fine, but it's worth checking the [72702.765418] config - if there is no relations between the [72702.765418] names, then host name confusion attack is possible. Apr 26 12:15:52 192.168.122.209 [72702.867724] [tempesta fw] Configuration processing is completed. Apr 26 12:15:52 192.168.122.209 [72702.932404] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:15:52 192.168.122.209 [72703.352712] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:15:52 192.168.122.209 [72703.378605] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:15:52 192.168.122.209 [72703.404160] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:15:52 192.168.122.209 [72703.451755] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:15:52 192.168.122.209 [72703.503692] [tempesta fw] Tempesta FW is ready Apr 26 12:15:56 192.168.122.209 [72707.166845] [tdb] Close table 'client0.tdb' Apr 26 12:15:56 192.168.122.209 [72707.340473] [tdb] Close table 'sessions0.tdb' Apr 26 12:15:59 192.168.122.209 [72710.515391] [tdb] Close table 'cache0.tdb' Apr 26 12:16:00 192.168.122.209 [72710.762006] [tdb] Close table 'filter0.tdb' Apr 26 12:16:00 192.168.122.209 [72710.762444] [tempesta fw] modules are stopped Apr 26 12:16:00 192.168.122.209 [72710.970121] [tempesta fw] exiting... Apr 26 12:16:00 192.168.122.209 [72711.116560] [tdb] Shutdown Tempesta DB Apr 26 12:16:00 192.168.122.209 [72711.542482] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_if_error_param_req Apr 26 12:16:00 192.168.122.209 [72711.581912] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_if_error_param_resp Apr 26 12:16:02 192.168.122.209 [72713.004058] [tdb] Start Tempesta DB Apr 26 12:16:02 192.168.122.209 [72713.144667] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:16:03 192.168.122.209 [72714.601593] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72714.601593] Maybe that's fine, but it's worth checking the [72714.601593] config - if there is no relations between the [72714.601593] names, then host name confusion attack is possible. Apr 26 12:16:03 192.168.122.209 [72714.680169] [tempesta fw] Configuration processing is completed. Apr 26 12:16:04 192.168.122.209 [72714.742908] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:16:04 192.168.122.209 [72715.176515] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:16:04 192.168.122.209 [72715.204957] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:16:04 192.168.122.209 [72715.231487] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:16:04 192.168.122.209 [72715.275897] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:16:04 192.168.122.209 [72715.323804] [tempesta fw] Tempesta FW is ready Apr 26 12:16:08 192.168.122.209 [72719.058224] [tdb] Close table 'client0.tdb' Apr 26 12:16:08 192.168.122.209 [72719.241251] [tdb] Close table 'sessions0.tdb' Apr 26 12:16:11 192.168.122.209 [72722.413092] [tdb] Close table 'cache0.tdb' Apr 26 12:16:11 192.168.122.209 [72722.647385] [tdb] Close table 'filter0.tdb' Apr 26 12:16:11 192.168.122.209 [72722.647833] [tempesta fw] modules are stopped Apr 26 12:16:12 192.168.122.209 [72722.863694] [tempesta fw] exiting... Apr 26 12:16:12 192.168.122.209 [72723.001822] [tdb] Shutdown Tempesta DB Apr 26 12:16:12 192.168.122.209 [72723.437281] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_if_error_param_resp Apr 26 12:16:12 192.168.122.209 [72723.466809] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_invalid_response Apr 26 12:16:14 192.168.122.209 [72725.062812] [tdb] Start Tempesta DB Apr 26 12:16:14 192.168.122.209 [72725.195188] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:16:16 192.168.122.209 [72726.765737] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72726.765737] Maybe that's fine, but it's worth checking the [72726.765737] config - if there is no relations between the [72726.765737] names, then host name confusion attack is possible. Apr 26 12:16:16 192.168.122.209 [72726.868006] [tempesta fw] Configuration processing is completed. Apr 26 12:16:16 192.168.122.209 [72726.929319] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:16:16 192.168.122.209 [72727.351661] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:16:16 192.168.122.209 [72727.378103] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:16:16 192.168.122.209 [72727.405556] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:16:16 192.168.122.209 [72727.444046] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:16:16 192.168.122.209 [72727.491996] [tempesta fw] Tempesta FW is ready Apr 26 12:16:19 192.168.122.209 [72730.707847] [tempesta fw] Warning: Parser error: state=RGen_HdrOtherN input(-8)=0x68('gth: 0 [72730.707847] hd>r: v [72730.707847] date: Sat,') data_len=62 off=43 Apr 26 12:16:20 192.168.122.209 [72731.144636] [tdb] Close table 'client0.tdb' Apr 26 12:16:20 192.168.122.209 [72731.332024] [tdb] Close table 'sessions0.tdb' Apr 26 12:16:23 192.168.122.209 [72734.520706] [tdb] Close table 'cache0.tdb' Apr 26 12:16:24 192.168.122.209 [72734.767235] [tdb] Close table 'filter0.tdb' Apr 26 12:16:24 192.168.122.209 [72734.767644] [tempesta fw] modules are stopped Apr 26 12:16:24 192.168.122.209 [72735.028001] [tempesta fw] exiting... Apr 26 12:16:24 192.168.122.209 [72735.159106] [tdb] Shutdown Tempesta DB Apr 26 12:16:24 192.168.122.209 [72735.585730] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_invalid_response Apr 26 12:16:24 192.168.122.209 [72735.618678] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_then_fresh_req Apr 26 12:16:26 192.168.122.209 [72736.999785] [tdb] Start Tempesta DB Apr 26 12:16:26 192.168.122.209 [72737.136549] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:16:27 192.168.122.209 [72738.537953] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72738.537953] Maybe that's fine, but it's worth checking the [72738.537953] config - if there is no relations between the [72738.537953] names, then host name confusion attack is possible. Apr 26 12:16:27 192.168.122.209 [72738.628168] [tempesta fw] Configuration processing is completed. Apr 26 12:16:27 192.168.122.209 [72738.686115] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:16:28 192.168.122.209 [72739.146119] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:16:28 192.168.122.209 [72739.174400] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:16:28 192.168.122.209 [72739.202200] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:16:28 192.168.122.209 [72739.260220] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:16:28 192.168.122.209 [72739.304149] [tempesta fw] Tempesta FW is ready Apr 26 12:16:35 192.168.122.209 [72746.013370] [tdb] Close table 'client0.tdb' Apr 26 12:16:35 192.168.122.209 [72746.196551] [tdb] Close table 'sessions0.tdb' Apr 26 12:16:38 192.168.122.209 [72749.391584] [tdb] Close table 'cache0.tdb' Apr 26 12:16:38 192.168.122.209 [72749.622838] [tdb] Close table 'filter0.tdb' Apr 26 12:16:38 192.168.122.209 [72749.623240] [tempesta fw] modules are stopped Apr 26 12:16:39 192.168.122.209 [72749.821147] [tempesta fw] exiting... Apr 26 12:16:39 192.168.122.209 [72749.920860] [tdb] Shutdown Tempesta DB Apr 26 12:16:39 192.168.122.209 [72750.334133] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_then_fresh_req Apr 26 12:16:39 192.168.122.209 [72750.416794] Start test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_then_fresh_resp Apr 26 12:16:41 192.168.122.209 [72751.858311] [tdb] Start Tempesta DB Apr 26 12:16:41 192.168.122.209 [72752.015548] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:16:42 192.168.122.209 [72753.526051] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72753.526051] Maybe that's fine, but it's worth checking the [72753.526051] config - if there is no relations between the [72753.526051] names, then host name confusion attack is possible. Apr 26 12:16:42 192.168.122.209 [72753.604691] [tempesta fw] Configuration processing is completed. Apr 26 12:16:42 192.168.122.209 [72753.664065] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:16:43 192.168.122.209 [72754.102416] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:16:43 192.168.122.209 [72754.128744] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:16:43 192.168.122.209 [72754.157003] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:16:43 192.168.122.209 [72754.192393] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:16:43 192.168.122.209 [72754.232322] [tempesta fw] Tempesta FW is ready Apr 26 12:16:50 192.168.122.209 [72760.856124] [tdb] Close table 'client0.tdb' Apr 26 12:16:50 192.168.122.209 [72761.045141] [tdb] Close table 'sessions0.tdb' Apr 26 12:16:53 192.168.122.209 [72764.245839] [tdb] Close table 'cache0.tdb' Apr 26 12:16:53 192.168.122.209 [72764.512404] [tdb] Close table 'filter0.tdb' Apr 26 12:16:53 192.168.122.209 [72764.512848] [tempesta fw] modules are stopped Apr 26 12:16:53 192.168.122.209 [72764.718007] [tempesta fw] exiting... Apr 26 12:16:54 192.168.122.209 [72764.855394] [tdb] Shutdown Tempesta DB Apr 26 12:16:54 192.168.122.209 [72765.283819] End test: cache.test_cache_stale.TestCacheUseStaleH2.test_use_stale_then_fresh_resp Apr 26 12:16:54 192.168.122.209 [72765.316427] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_max_stale Apr 26 12:16:56 192.168.122.209 [72766.879551] [tdb] Start Tempesta DB Apr 26 12:16:56 192.168.122.209 [72767.018422] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:16:57 192.168.122.209 [72768.406263] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72768.406263] Maybe that's fine, but it's worth checking the [72768.406263] config - if there is no relations between the [72768.406263] names, then host name confusion attack is possible. Apr 26 12:16:57 192.168.122.209 [72768.508851] [tempesta fw] Configuration processing is completed. Apr 26 12:16:57 192.168.122.209 [72768.568090] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:16:58 192.168.122.209 [72769.021507] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:16:58 192.168.122.209 [72769.049335] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:16:58 192.168.122.209 [72769.076843] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:16:58 192.168.122.209 [72769.128603] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:16:58 192.168.122.209 [72769.176528] [tempesta fw] Tempesta FW is ready Apr 26 12:17:10 192.168.122.209 [72780.862786] [tdb] Close table 'client0.tdb' Apr 26 12:17:10 192.168.122.209 [72781.046534] [tdb] Close table 'sessions0.tdb' Apr 26 12:17:13 192.168.122.209 [72784.284324] [tdb] Close table 'cache0.tdb' Apr 26 12:17:13 192.168.122.209 [72784.513272] [tdb] Close table 'filter0.tdb' Apr 26 12:17:13 192.168.122.209 [72784.513704] [tempesta fw] modules are stopped Apr 26 12:17:13 192.168.122.209 [72784.716012] [tempesta fw] exiting... Apr 26 12:17:14 192.168.122.209 [72784.871309] [tdb] Shutdown Tempesta DB Apr 26 12:17:14 192.168.122.209 [72785.313299] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_max_stale Apr 26 12:17:14 192.168.122.209 [72785.350477] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_stale_if_error_not_use_304 Apr 26 12:17:15 192.168.122.209 [72786.675045] [tdb] Start Tempesta DB Apr 26 12:17:16 192.168.122.209 [72786.810469] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:17:17 192.168.122.209 [72788.241785] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72788.241785] Maybe that's fine, but it's worth checking the [72788.241785] config - if there is no relations between the [72788.241785] names, then host name confusion attack is possible. Apr 26 12:17:17 192.168.122.209 [72788.332778] [tempesta fw] Configuration processing is completed. Apr 26 12:17:17 192.168.122.209 [72788.384481] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:17:18 192.168.122.209 [72788.800911] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:17:18 192.168.122.209 [72788.827637] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:17:18 192.168.122.209 [72788.853761] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:17:18 192.168.122.209 [72788.896817] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:17:18 192.168.122.209 [72788.948775] [tempesta fw] Tempesta FW is ready Apr 26 12:17:20 192.168.122.209 [72791.647647] [tdb] Close table 'client0.tdb' Apr 26 12:17:21 192.168.122.209 [72791.837346] [tdb] Close table 'sessions0.tdb' Apr 26 12:17:24 192.168.122.209 [72795.159137] [tdb] Close table 'cache0.tdb' Apr 26 12:17:24 192.168.122.209 [72795.428032] [tdb] Close table 'filter0.tdb' Apr 26 12:17:24 192.168.122.209 [72795.428463] [tempesta fw] modules are stopped Apr 26 12:17:24 192.168.122.209 [72795.617997] [tempesta fw] exiting... Apr 26 12:17:25 192.168.122.209 [72795.750210] [tdb] Shutdown Tempesta DB Apr 26 12:17:25 192.168.122.209 [72796.206049] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_stale_if_error_not_use_304 Apr 26 12:17:25 192.168.122.209 [72796.232040] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_fresh_200 Apr 26 12:17:27 192.168.122.209 [72797.740893] [tdb] Start Tempesta DB Apr 26 12:17:27 192.168.122.209 [72797.872229] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:17:28 192.168.122.209 [72799.430577] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72799.430577] Maybe that's fine, but it's worth checking the [72799.430577] config - if there is no relations between the [72799.430577] names, then host name confusion attack is possible. Apr 26 12:17:28 192.168.122.209 [72799.540910] [tempesta fw] Configuration processing is completed. Apr 26 12:17:28 192.168.122.209 [72799.592874] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:17:29 192.168.122.209 [72800.020065] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:17:29 192.168.122.209 [72800.047781] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:17:29 192.168.122.209 [72800.075373] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:17:29 192.168.122.209 [72800.124947] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:17:29 192.168.122.209 [72800.164899] [tempesta fw] Tempesta FW is ready Apr 26 12:17:33 192.168.122.209 [72803.786021] [tdb] Close table 'client0.tdb' Apr 26 12:17:33 192.168.122.209 [72803.981379] [tdb] Close table 'sessions0.tdb' Apr 26 12:17:36 192.168.122.209 [72807.159057] [tdb] Close table 'cache0.tdb' Apr 26 12:17:36 192.168.122.209 [72807.392459] [tdb] Close table 'filter0.tdb' Apr 26 12:17:36 192.168.122.209 [72807.392929] [tempesta fw] modules are stopped Apr 26 12:17:36 192.168.122.209 [72807.638314] [tempesta fw] exiting... Apr 26 12:17:37 192.168.122.209 [72807.775934] [tdb] Shutdown Tempesta DB Apr 26 12:17:37 192.168.122.209 [72808.158419] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_fresh_200 Apr 26 12:17:37 192.168.122.209 [72808.192782] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_fresh_403 Apr 26 12:17:38 192.168.122.209 [72809.658364] [tdb] Start Tempesta DB Apr 26 12:17:39 192.168.122.209 [72809.799977] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:17:40 192.168.122.209 [72811.222840] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72811.222840] Maybe that's fine, but it's worth checking the [72811.222840] config - if there is no relations between the [72811.222840] names, then host name confusion attack is possible. Apr 26 12:17:40 192.168.122.209 [72811.337456] [tempesta fw] Configuration processing is completed. Apr 26 12:17:40 192.168.122.209 [72811.386983] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:17:41 192.168.122.209 [72811.818011] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:17:41 192.168.122.209 [72811.844459] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:17:41 192.168.122.209 [72811.870419] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:17:41 192.168.122.209 [72811.913039] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:17:41 192.168.122.209 [72811.957041] [tempesta fw] Tempesta FW is ready Apr 26 12:17:44 192.168.122.209 [72815.604900] [tdb] Close table 'client0.tdb' Apr 26 12:17:45 192.168.122.209 [72815.790020] [tdb] Close table 'sessions0.tdb' Apr 26 12:17:48 192.168.122.209 [72818.965950] [tdb] Close table 'cache0.tdb' Apr 26 12:17:48 192.168.122.209 [72819.215609] [tdb] Close table 'filter0.tdb' Apr 26 12:17:48 192.168.122.209 [72819.216054] [tempesta fw] modules are stopped Apr 26 12:17:48 192.168.122.209 [72819.394120] [tempesta fw] exiting... Apr 26 12:17:48 192.168.122.209 [72819.520044] [tdb] Shutdown Tempesta DB Apr 26 12:17:49 192.168.122.209 [72819.922842] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_fresh_403 Apr 26 12:17:49 192.168.122.209 [72819.955343] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_fresh_on_error_must_revalidate Apr 26 12:17:50 192.168.122.209 [72821.519142] [tdb] Start Tempesta DB Apr 26 12:17:50 192.168.122.209 [72821.649360] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:17:52 192.168.122.209 [72823.122949] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72823.122949] Maybe that's fine, but it's worth checking the [72823.122949] config - if there is no relations between the [72823.122949] names, then host name confusion attack is possible. Apr 26 12:17:52 192.168.122.209 [72823.233240] [tempesta fw] Configuration processing is completed. Apr 26 12:17:52 192.168.122.209 [72823.286525] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:17:52 192.168.122.209 [72823.709481] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:17:53 192.168.122.209 [72823.735656] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:17:53 192.168.122.209 [72823.760995] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:17:53 192.168.122.209 [72823.805239] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:17:53 192.168.122.209 [72823.845215] [tempesta fw] Tempesta FW is ready Apr 26 12:17:56 192.168.122.209 [72827.531223] [tdb] Close table 'client0.tdb' Apr 26 12:17:56 192.168.122.209 [72827.717952] [tdb] Close table 'sessions0.tdb' Apr 26 12:18:00 192.168.122.209 [72830.903505] [tdb] Close table 'cache0.tdb' Apr 26 12:18:00 192.168.122.209 [72831.143290] [tdb] Close table 'filter0.tdb' Apr 26 12:18:00 192.168.122.209 [72831.143700] [tempesta fw] modules are stopped Apr 26 12:18:00 192.168.122.209 [72831.330403] [tempesta fw] exiting... Apr 26 12:18:00 192.168.122.209 [72831.460664] [tdb] Shutdown Tempesta DB Apr 26 12:18:01 192.168.122.209 [72831.882560] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_fresh_on_error_must_revalidate Apr 26 12:18:01 192.168.122.209 [72831.917060] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_fresh_on_error_proxy_revalidate Apr 26 12:18:02 192.168.122.209 [72833.519799] [tdb] Start Tempesta DB Apr 26 12:18:02 192.168.122.209 [72833.666745] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:18:04 192.168.122.209 [72835.111131] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72835.111131] Maybe that's fine, but it's worth checking the [72835.111131] config - if there is no relations between the [72835.111131] names, then host name confusion attack is possible. Apr 26 12:18:04 192.168.122.209 [72835.209360] [tempesta fw] Configuration processing is completed. Apr 26 12:18:04 192.168.122.209 [72835.267407] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:18:05 192.168.122.209 [72835.726690] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:18:05 192.168.122.209 [72835.754221] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:18:05 192.168.122.209 [72835.781879] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:18:05 192.168.122.209 [72835.833404] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:18:05 192.168.122.209 [72835.869274] [tempesta fw] Tempesta FW is ready Apr 26 12:18:08 192.168.122.209 [72839.505008] [tdb] Close table 'client0.tdb' Apr 26 12:18:08 192.168.122.209 [72839.719206] [tdb] Close table 'sessions0.tdb' Apr 26 12:18:12 192.168.122.209 [72842.958673] [tdb] Close table 'cache0.tdb' Apr 26 12:18:12 192.168.122.209 [72843.219463] [tdb] Close table 'filter0.tdb' Apr 26 12:18:12 192.168.122.209 [72843.219949] [tempesta fw] modules are stopped Apr 26 12:18:12 192.168.122.209 [72843.392787] [tempesta fw] exiting... Apr 26 12:18:12 192.168.122.209 [72843.537767] [tdb] Shutdown Tempesta DB Apr 26 12:18:13 192.168.122.209 [72843.962715] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_fresh_on_error_proxy_revalidate Apr 26 12:18:13 192.168.122.209 [72843.997861] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_fresh_on_error_s_maxage Apr 26 12:18:14 192.168.122.209 [72845.595912] [tdb] Start Tempesta DB Apr 26 12:18:15 192.168.122.209 [72845.760564] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:18:16 192.168.122.209 [72847.219308] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72847.219308] Maybe that's fine, but it's worth checking the [72847.219308] config - if there is no relations between the [72847.219308] names, then host name confusion attack is possible. Apr 26 12:18:16 192.168.122.209 [72847.313803] [tempesta fw] Configuration processing is completed. Apr 26 12:18:16 192.168.122.209 [72847.378391] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:18:17 192.168.122.209 [72847.848040] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:18:17 192.168.122.209 [72847.875775] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:18:17 192.168.122.209 [72847.904397] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:18:17 192.168.122.209 [72847.945427] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:18:17 192.168.122.209 [72847.989486] [tempesta fw] Tempesta FW is ready Apr 26 12:18:20 192.168.122.209 [72851.665265] [tdb] Close table 'client0.tdb' Apr 26 12:18:21 192.168.122.209 [72851.854466] [tdb] Close table 'sessions0.tdb' Apr 26 12:18:24 192.168.122.209 [72855.050078] [tdb] Close table 'cache0.tdb' Apr 26 12:18:24 192.168.122.209 [72855.282299] [tdb] Close table 'filter0.tdb' Apr 26 12:18:24 192.168.122.209 [72855.282744] [tempesta fw] modules are stopped Apr 26 12:18:24 192.168.122.209 [72855.487573] [tempesta fw] exiting... Apr 26 12:18:24 192.168.122.209 [72855.627254] [tdb] Shutdown Tempesta DB Apr 26 12:18:25 192.168.122.209 [72856.014766] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_fresh_on_error_s_maxage Apr 26 12:18:25 192.168.122.209 [72856.050358] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_400 Apr 26 12:18:26 192.168.122.209 [72857.638045] [tdb] Start Tempesta DB Apr 26 12:18:27 192.168.122.209 [72857.783360] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:18:28 192.168.122.209 [72859.231385] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72859.231385] Maybe that's fine, but it's worth checking the [72859.231385] config - if there is no relations between the [72859.231385] names, then host name confusion attack is possible. Apr 26 12:18:28 192.168.122.209 [72859.325961] [tempesta fw] Configuration processing is completed. Apr 26 12:18:28 192.168.122.209 [72859.382305] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:18:29 192.168.122.209 [72859.798735] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:18:29 192.168.122.209 [72859.825008] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:18:29 192.168.122.209 [72859.851255] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:18:29 192.168.122.209 [72859.889667] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:18:29 192.168.122.209 [72859.937645] [tempesta fw] Tempesta FW is ready Apr 26 12:18:32 192.168.122.209 [72863.558777] [tdb] Close table 'client0.tdb' Apr 26 12:18:33 192.168.122.209 [72863.745840] [tdb] Close table 'sessions0.tdb' Apr 26 12:18:36 192.168.122.209 [72866.953435] [tdb] Close table 'cache0.tdb' Apr 26 12:18:36 192.168.122.209 [72867.187886] [tdb] Close table 'filter0.tdb' Apr 26 12:18:36 192.168.122.209 [72867.188325] [tempesta fw] modules are stopped Apr 26 12:18:36 192.168.122.209 [72867.424033] [tempesta fw] exiting... Apr 26 12:18:36 192.168.122.209 [72867.554399] [tdb] Shutdown Tempesta DB Apr 26 12:18:37 192.168.122.209 [72867.887822] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_400 Apr 26 12:18:37 192.168.122.209 [72867.968080] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_4xx_400 Apr 26 12:18:38 192.168.122.209 [72869.504884] [tdb] Start Tempesta DB Apr 26 12:18:38 192.168.122.209 [72869.649608] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:18:40 192.168.122.209 [72871.115554] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72871.115554] Maybe that's fine, but it's worth checking the [72871.115554] config - if there is no relations between the [72871.115554] names, then host name confusion attack is possible. Apr 26 12:18:40 192.168.122.209 [72871.222151] [tempesta fw] Configuration processing is completed. Apr 26 12:18:40 192.168.122.209 [72871.286492] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:18:41 192.168.122.209 [72871.770830] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:18:41 192.168.122.209 [72871.800703] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:18:41 192.168.122.209 [72871.830980] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:18:41 192.168.122.209 [72871.873848] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:18:41 192.168.122.209 [72871.921826] [tempesta fw] Tempesta FW is ready Apr 26 12:18:44 192.168.122.209 [72875.589143] [tdb] Close table 'client0.tdb' Apr 26 12:18:45 192.168.122.209 [72875.772773] [tdb] Close table 'sessions0.tdb' Apr 26 12:18:48 192.168.122.209 [72878.983651] [tdb] Close table 'cache0.tdb' Apr 26 12:18:48 192.168.122.209 [72879.220988] [tdb] Close table 'filter0.tdb' Apr 26 12:18:48 192.168.122.209 [72879.221456] [tempesta fw] modules are stopped Apr 26 12:18:48 192.168.122.209 [72879.398984] [tempesta fw] exiting... Apr 26 12:18:48 192.168.122.209 [72879.558441] [tdb] Shutdown Tempesta DB Apr 26 12:18:49 192.168.122.209 [72879.981262] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_4xx_400 Apr 26 12:18:49 192.168.122.209 [72880.007863] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_4xx_403 Apr 26 12:18:50 192.168.122.209 [72881.613627] [tdb] Start Tempesta DB Apr 26 12:18:51 192.168.122.209 [72881.747908] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:18:52 192.168.122.209 [72883.223784] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72883.223784] Maybe that's fine, but it's worth checking the [72883.223784] config - if there is no relations between the [72883.223784] names, then host name confusion attack is possible. Apr 26 12:18:52 192.168.122.209 [72883.317973] [tempesta fw] Configuration processing is completed. Apr 26 12:18:52 192.168.122.209 [72883.377434] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:18:53 192.168.122.209 [72883.825551] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:18:53 192.168.122.209 [72883.854214] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:18:53 192.168.122.209 [72883.883304] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:18:53 192.168.122.209 [72883.918022] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:18:53 192.168.122.209 [72883.953936] [tempesta fw] Tempesta FW is ready Apr 26 12:18:56 192.168.122.209 [72887.552603] [tdb] Close table 'client0.tdb' Apr 26 12:18:57 192.168.122.209 [72887.764591] [tdb] Close table 'sessions0.tdb' Apr 26 12:19:00 192.168.122.209 [72890.929512] [tdb] Close table 'cache0.tdb' Apr 26 12:19:00 192.168.122.209 [72891.183851] [tdb] Close table 'filter0.tdb' Apr 26 12:19:00 192.168.122.209 [72891.184266] [tempesta fw] modules are stopped Apr 26 12:19:00 192.168.122.209 [72891.352479] [tempesta fw] exiting... Apr 26 12:19:00 192.168.122.209 [72891.477969] [tdb] Shutdown Tempesta DB Apr 26 12:19:01 192.168.122.209 [72891.922998] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_4xx_403 Apr 26 12:19:01 192.168.122.209 [72891.953299] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_4xx_5xx Apr 26 12:19:02 192.168.122.209 [72893.416108] [tdb] Start Tempesta DB Apr 26 12:19:02 192.168.122.209 [72893.538650] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:19:04 192.168.122.209 [72895.107816] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72895.107816] Maybe that's fine, but it's worth checking the [72895.107816] config - if there is no relations between the [72895.107816] names, then host name confusion attack is possible. Apr 26 12:19:04 192.168.122.209 [72895.210455] [tempesta fw] Configuration processing is completed. Apr 26 12:19:04 192.168.122.209 [72895.266910] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:19:04 192.168.122.209 [72895.685614] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:19:04 192.168.122.209 [72895.711376] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:19:05 192.168.122.209 [72895.736870] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:19:05 192.168.122.209 [72895.790067] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:19:05 192.168.122.209 [72895.838100] [tempesta fw] Tempesta FW is ready Apr 26 12:19:08 192.168.122.209 [72899.443922] [tdb] Close table 'client0.tdb' Apr 26 12:19:08 192.168.122.209 [72899.658736] [tdb] Close table 'sessions0.tdb' Apr 26 12:19:12 192.168.122.209 [72902.856963] [tdb] Close table 'cache0.tdb' Apr 26 12:19:12 192.168.122.209 [72903.101558] [tdb] Close table 'filter0.tdb' Apr 26 12:19:12 192.168.122.209 [72903.101999] [tempesta fw] modules are stopped Apr 26 12:19:12 192.168.122.209 [72903.280060] [tempesta fw] exiting... Apr 26 12:19:12 192.168.122.209 [72903.405711] [tdb] Shutdown Tempesta DB Apr 26 12:19:13 192.168.122.209 [72903.832789] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_4xx_5xx Apr 26 12:19:13 192.168.122.209 [72903.906136] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_500 Apr 26 12:19:14 192.168.122.209 [72905.494438] [tdb] Start Tempesta DB Apr 26 12:19:14 192.168.122.209 [72905.639616] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:19:16 192.168.122.209 [72907.191985] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72907.191985] Maybe that's fine, but it's worth checking the [72907.191985] config - if there is no relations between the [72907.191985] names, then host name confusion attack is possible. Apr 26 12:19:16 192.168.122.209 [72907.306272] [tempesta fw] Configuration processing is completed. Apr 26 12:19:16 192.168.122.209 [72907.376588] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:19:17 192.168.122.209 [72907.845340] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:19:17 192.168.122.209 [72907.874802] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:19:17 192.168.122.209 [72907.903998] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:19:17 192.168.122.209 [72907.946346] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:19:17 192.168.122.209 [72907.998258] [tempesta fw] Tempesta FW is ready Apr 26 12:19:20 192.168.122.209 [72911.686758] [tdb] Close table 'client0.tdb' Apr 26 12:19:21 192.168.122.209 [72911.871383] [tdb] Close table 'sessions0.tdb' Apr 26 12:19:24 192.168.122.209 [72915.059303] [tdb] Close table 'cache0.tdb' Apr 26 12:19:24 192.168.122.209 [72915.332948] [tdb] Close table 'filter0.tdb' Apr 26 12:19:24 192.168.122.209 [72915.333376] [tempesta fw] modules are stopped Apr 26 12:19:24 192.168.122.209 [72915.531539] [tempesta fw] exiting... Apr 26 12:19:24 192.168.122.209 [72915.646973] [tdb] Shutdown Tempesta DB Apr 26 12:19:25 192.168.122.209 [72916.074689] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_500 Apr 26 12:19:25 192.168.122.209 [72916.116600] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_5xx_500 Apr 26 12:19:26 192.168.122.209 [72917.596689] [tdb] Start Tempesta DB Apr 26 12:19:27 192.168.122.209 [72917.726727] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:19:28 192.168.122.209 [72919.212111] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72919.212111] Maybe that's fine, but it's worth checking the [72919.212111] config - if there is no relations between the [72919.212111] names, then host name confusion attack is possible. Apr 26 12:19:28 192.168.122.209 [72919.314427] [tempesta fw] Configuration processing is completed. Apr 26 12:19:28 192.168.122.209 [72919.379898] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:19:29 192.168.122.209 [72919.915896] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:19:29 192.168.122.209 [72919.949880] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:19:29 192.168.122.209 [72919.983627] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:19:29 192.168.122.209 [72920.030465] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:19:29 192.168.122.209 [72920.074390] [tempesta fw] Tempesta FW is ready Apr 26 12:19:33 192.168.122.209 [72923.727469] [tdb] Close table 'client0.tdb' Apr 26 12:19:33 192.168.122.209 [72923.935215] [tdb] Close table 'sessions0.tdb' Apr 26 12:19:36 192.168.122.209 [72927.069608] [tdb] Close table 'cache0.tdb' Apr 26 12:19:36 192.168.122.209 [72927.311027] [tdb] Close table 'filter0.tdb' Apr 26 12:19:36 192.168.122.209 [72927.311467] [tempesta fw] modules are stopped Apr 26 12:19:36 192.168.122.209 [72927.522437] [tempesta fw] exiting... Apr 26 12:19:36 192.168.122.209 [72927.669216] [tdb] Shutdown Tempesta DB Apr 26 12:19:37 192.168.122.209 [72928.069682] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_5xx_500 Apr 26 12:19:37 192.168.122.209 [72928.100995] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_5xx_502 Apr 26 12:19:38 192.168.122.209 [72929.538735] [tdb] Start Tempesta DB Apr 26 12:19:38 192.168.122.209 [72929.668911] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:19:40 192.168.122.209 [72931.124947] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72931.124947] Maybe that's fine, but it's worth checking the [72931.124947] config - if there is no relations between the [72931.124947] names, then host name confusion attack is possible. Apr 26 12:19:40 192.168.122.209 [72931.238724] [tempesta fw] Configuration processing is completed. Apr 26 12:19:40 192.168.122.209 [72931.303146] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:19:41 192.168.122.209 [72931.730362] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:19:41 192.168.122.209 [72931.756493] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:19:41 192.168.122.209 [72931.782478] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:19:41 192.168.122.209 [72931.830591] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:19:41 192.168.122.209 [72931.874536] [tempesta fw] Tempesta FW is ready Apr 26 12:19:44 192.168.122.209 [72935.593005] [tdb] Close table 'client0.tdb' Apr 26 12:19:45 192.168.122.209 [72935.770919] [tdb] Close table 'sessions0.tdb' Apr 26 12:19:48 192.168.122.209 [72939.019375] [tdb] Close table 'cache0.tdb' Apr 26 12:19:48 192.168.122.209 [72939.280834] [tdb] Close table 'filter0.tdb' Apr 26 12:19:48 192.168.122.209 [72939.281260] [tempesta fw] modules are stopped Apr 26 12:19:48 192.168.122.209 [72939.459727] [tempesta fw] exiting... Apr 26 12:19:48 192.168.122.209 [72939.611864] [tdb] Shutdown Tempesta DB Apr 26 12:19:49 192.168.122.209 [72940.049753] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_5xx_502 Apr 26 12:19:49 192.168.122.209 [72940.085054] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_if_error_duplicated_req Apr 26 12:19:50 192.168.122.209 [72941.540159] [tdb] Start Tempesta DB Apr 26 12:19:50 192.168.122.209 [72941.677457] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:19:52 192.168.122.209 [72943.164527] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72943.164527] Maybe that's fine, but it's worth checking the [72943.164527] config - if there is no relations between the [72943.164527] names, then host name confusion attack is possible. Apr 26 12:19:52 192.168.122.209 [72943.246719] [tempesta fw] Configuration processing is completed. Apr 26 12:19:52 192.168.122.209 [72943.307653] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:19:53 192.168.122.209 [72943.745214] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:19:53 192.168.122.209 [72943.772361] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:19:53 192.168.122.209 [72943.799274] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:19:53 192.168.122.209 [72943.842755] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:19:53 192.168.122.209 [72943.886687] [tempesta fw] Tempesta FW is ready Apr 26 12:19:53 192.168.122.209 [72944.514412] [tdb] Close table 'client0.tdb' Apr 26 12:19:53 192.168.122.209 [72944.704231] [tdb] Close table 'sessions0.tdb' Apr 26 12:19:57 192.168.122.209 [72947.840901] [tdb] Close table 'cache0.tdb' Apr 26 12:19:57 192.168.122.209 [72948.101174] [tdb] Close table 'filter0.tdb' Apr 26 12:19:57 192.168.122.209 [72948.101613] [tempesta fw] modules are stopped Apr 26 12:19:57 192.168.122.209 [72948.278964] [tempesta fw] exiting... Apr 26 12:19:57 192.168.122.209 [72948.466364] [tdb] Shutdown Tempesta DB Apr 26 12:19:58 192.168.122.209 [72948.847858] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_if_error_duplicated_req Apr 26 12:19:58 192.168.122.209 [72948.886400] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_if_error_duplicated_resp Apr 26 12:19:59 192.168.122.209 [72950.308429] [tdb] Start Tempesta DB Apr 26 12:19:59 192.168.122.209 [72950.455269] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:20:01 192.168.122.209 [72951.912828] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72951.912828] Maybe that's fine, but it's worth checking the [72951.912828] config - if there is no relations between the [72951.912828] names, then host name confusion attack is possible. Apr 26 12:20:01 192.168.122.209 [72951.998839] [tempesta fw] Configuration processing is completed. Apr 26 12:20:01 192.168.122.209 [72952.070845] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:20:01 192.168.122.209 [72952.576278] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:20:01 192.168.122.209 [72952.607912] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:20:01 192.168.122.209 [72952.640284] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:20:01 192.168.122.209 [72952.686845] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:20:02 192.168.122.209 [72952.750810] [tempesta fw] Tempesta FW is ready Apr 26 12:20:02 192.168.122.209 [72952.942503] [tempesta fw] Warning: Parser error: state=Resp_HdrCache_CtrlV input(-0)=0x72('ror=20, stale-if-error=19 [72952.942503] date: Sat, 26 Apr 202') data_len=66 off=0 Apr 26 12:20:02 192.168.122.209 [72952.946782] [tempesta fw] Warning: response dropped: processing error: 192.168.122.196 Apr 26 12:20:02 192.168.122.209 [72953.379839] [tdb] Close table 'client0.tdb' Apr 26 12:20:02 192.168.122.209 [72953.567048] [tdb] Close table 'sessions0.tdb' Apr 26 12:20:06 192.168.122.209 [72956.794607] [tdb] Close table 'cache0.tdb' Apr 26 12:20:06 192.168.122.209 [72957.064770] [tdb] Close table 'filter0.tdb' Apr 26 12:20:06 192.168.122.209 [72957.065176] [tempesta fw] modules are stopped Apr 26 12:20:06 192.168.122.209 [72957.256280] [tempesta fw] exiting... Apr 26 12:20:06 192.168.122.209 [72957.409096] [tdb] Shutdown Tempesta DB Apr 26 12:20:07 192.168.122.209 [72957.822287] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_if_error_duplicated_resp Apr 26 12:20:07 192.168.122.209 [72957.854194] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_if_error_param_req Apr 26 12:20:08 192.168.122.209 [72959.226274] [tdb] Start Tempesta DB Apr 26 12:20:08 192.168.122.209 [72959.372884] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:20:10 192.168.122.209 [72960.888678] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72960.888678] Maybe that's fine, but it's worth checking the [72960.888678] config - if there is no relations between the [72960.888678] names, then host name confusion attack is possible. Apr 26 12:20:10 192.168.122.209 [72960.971331] [tempesta fw] Configuration processing is completed. Apr 26 12:20:10 192.168.122.209 [72961.028033] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:20:10 192.168.122.209 [72961.460467] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:20:10 192.168.122.209 [72961.486329] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:20:10 192.168.122.209 [72961.511610] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:20:10 192.168.122.209 [72961.554955] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:20:10 192.168.122.209 [72961.594951] [tempesta fw] Tempesta FW is ready Apr 26 12:20:14 192.168.122.209 [72965.319022] [tdb] Close table 'client0.tdb' Apr 26 12:20:14 192.168.122.209 [72965.516204] [tdb] Close table 'sessions0.tdb' Apr 26 12:20:17 192.168.122.209 [72968.647029] [tdb] Close table 'cache0.tdb' Apr 26 12:20:18 192.168.122.209 [72968.914396] [tdb] Close table 'filter0.tdb' Apr 26 12:20:18 192.168.122.209 [72968.914820] [tempesta fw] modules are stopped Apr 26 12:20:18 192.168.122.209 [72969.127408] [tempesta fw] exiting... Apr 26 12:20:18 192.168.122.209 [72969.263495] [tdb] Shutdown Tempesta DB Apr 26 12:20:18 192.168.122.209 [72969.631518] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_if_error_param_req Apr 26 12:20:18 192.168.122.209 [72969.665308] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_if_error_param_resp Apr 26 12:20:20 192.168.122.209 [72971.029028] [tdb] Start Tempesta DB Apr 26 12:20:20 192.168.122.209 [72971.168340] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:20:21 192.168.122.209 [72972.644821] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72972.644821] Maybe that's fine, but it's worth checking the [72972.644821] config - if there is no relations between the [72972.644821] names, then host name confusion attack is possible. Apr 26 12:20:21 192.168.122.209 [72972.720648] [tempesta fw] Configuration processing is completed. Apr 26 12:20:22 192.168.122.209 [72972.775313] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:20:22 192.168.122.209 [72973.194180] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:20:22 192.168.122.209 [72973.221014] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:20:22 192.168.122.209 [72973.246925] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:20:22 192.168.122.209 [72973.283108] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:20:22 192.168.122.209 [72973.323050] [tempesta fw] Tempesta FW is ready Apr 26 12:20:26 192.168.122.209 [72977.027339] [tdb] Close table 'client0.tdb' Apr 26 12:20:26 192.168.122.209 [72977.214210] [tdb] Close table 'sessions0.tdb' Apr 26 12:20:29 192.168.122.209 [72980.431977] [tdb] Close table 'cache0.tdb' Apr 26 12:20:29 192.168.122.209 [72980.691651] [tdb] Close table 'filter0.tdb' Apr 26 12:20:29 192.168.122.209 [72980.692073] [tempesta fw] modules are stopped Apr 26 12:20:30 192.168.122.209 [72980.874641] [tempesta fw] exiting... Apr 26 12:20:30 192.168.122.209 [72981.010304] [tdb] Shutdown Tempesta DB Apr 26 12:20:30 192.168.122.209 [72981.436887] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_if_error_param_resp Apr 26 12:20:30 192.168.122.209 [72981.463387] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_invalid_response Apr 26 12:20:32 192.168.122.209 [72983.058860] [tdb] Start Tempesta DB Apr 26 12:20:32 192.168.122.209 [72983.194427] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:20:33 192.168.122.209 [72984.688919] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72984.688919] Maybe that's fine, but it's worth checking the [72984.688919] config - if there is no relations between the [72984.688919] names, then host name confusion attack is possible. Apr 26 12:20:34 192.168.122.209 [72984.795587] [tempesta fw] Configuration processing is completed. Apr 26 12:20:34 192.168.122.209 [72984.852459] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:20:34 192.168.122.209 [72985.271021] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:20:34 192.168.122.209 [72985.297544] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:20:34 192.168.122.209 [72985.324240] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:20:34 192.168.122.209 [72985.359278] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:20:34 192.168.122.209 [72985.407224] [tempesta fw] Tempesta FW is ready Apr 26 12:20:37 192.168.122.209 [72988.606254] [tempesta fw] Warning: Parser error: state=RGen_HdrOtherN input(-8)=0x68('gth: 0 [72988.606254] hd>r: v [72988.606254] date: Sat,') data_len=62 off=43 Apr 26 12:20:38 192.168.122.209 [72989.063337] [tdb] Close table 'client0.tdb' Apr 26 12:20:38 192.168.122.209 [72989.253633] [tdb] Close table 'sessions0.tdb' Apr 26 12:20:41 192.168.122.209 [72992.424835] [tdb] Close table 'cache0.tdb' Apr 26 12:20:41 192.168.122.209 [72992.693126] [tdb] Close table 'filter0.tdb' Apr 26 12:20:41 192.168.122.209 [72992.693549] [tempesta fw] modules are stopped Apr 26 12:20:42 192.168.122.209 [72992.884480] [tempesta fw] exiting... Apr 26 12:20:42 192.168.122.209 [72993.012212] [tdb] Shutdown Tempesta DB Apr 26 12:20:42 192.168.122.209 [72993.448064] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_invalid_response Apr 26 12:20:42 192.168.122.209 [72993.480527] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_then_fresh_req Apr 26 12:20:44 192.168.122.209 [72994.827780] [tdb] Start Tempesta DB Apr 26 12:20:44 192.168.122.209 [72994.956098] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:20:45 192.168.122.209 [72996.309058] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [72996.309058] Maybe that's fine, but it's worth checking the [72996.309058] config - if there is no relations between the [72996.309058] names, then host name confusion attack is possible. Apr 26 12:20:45 192.168.122.209 [72996.391706] [tempesta fw] Configuration processing is completed. Apr 26 12:20:45 192.168.122.209 [72996.457039] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:20:46 192.168.122.209 [72996.878903] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:20:46 192.168.122.209 [72996.905508] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:20:46 192.168.122.209 [72996.931795] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:20:46 192.168.122.209 [72996.995415] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:20:46 192.168.122.209 [72997.043362] [tempesta fw] Tempesta FW is ready Apr 26 12:20:53 192.168.122.209 [73003.731021] [tdb] Close table 'client0.tdb' Apr 26 12:20:53 192.168.122.209 [73003.914035] [tdb] Close table 'sessions0.tdb' Apr 26 12:20:56 192.168.122.209 [73007.097434] [tdb] Close table 'cache0.tdb' Apr 26 12:20:56 192.168.122.209 [73007.377594] [tdb] Close table 'filter0.tdb' Apr 26 12:20:56 192.168.122.209 [73007.378055] [tempesta fw] modules are stopped Apr 26 12:20:56 192.168.122.209 [73007.564160] [tempesta fw] exiting... Apr 26 12:20:56 192.168.122.209 [73007.673207] [tdb] Shutdown Tempesta DB Apr 26 12:20:57 192.168.122.209 [73008.092295] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_then_fresh_req Apr 26 12:20:57 192.168.122.209 [73008.118360] Start test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_then_fresh_resp Apr 26 12:20:58 192.168.122.209 [73009.585321] [tdb] Start Tempesta DB Apr 26 12:20:58 192.168.122.209 [73009.715958] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:21:00 192.168.122.209 [73011.181274] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73011.181274] Maybe that's fine, but it's worth checking the [73011.181274] config - if there is no relations between the [73011.181274] names, then host name confusion attack is possible. Apr 26 12:21:00 192.168.122.209 [73011.279555] [tempesta fw] Configuration processing is completed. Apr 26 12:21:00 192.168.122.209 [73011.345226] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:21:01 192.168.122.209 [73011.768166] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:21:01 192.168.122.209 [73011.794618] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:21:01 192.168.122.209 [73011.821088] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:21:01 192.168.122.209 [73011.859585] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:21:01 192.168.122.209 [73011.907538] [tempesta fw] Tempesta FW is ready Apr 26 12:21:07 192.168.122.209 [73018.568449] [tdb] Close table 'client0.tdb' Apr 26 12:21:08 192.168.122.209 [73018.758197] [tdb] Close table 'sessions0.tdb' Apr 26 12:21:11 192.168.122.209 [73021.947943] [tdb] Close table 'cache0.tdb' Apr 26 12:21:11 192.168.122.209 [73022.202304] [tdb] Close table 'filter0.tdb' Apr 26 12:21:11 192.168.122.209 [73022.202730] [tempesta fw] modules are stopped Apr 26 12:21:11 192.168.122.209 [73022.413067] [tempesta fw] exiting... Apr 26 12:21:11 192.168.122.209 [73022.557459] [tdb] Shutdown Tempesta DB Apr 26 12:21:12 192.168.122.209 [73022.900222] End test: cache.test_cache_stale.TestCacheUseStaleHttp.test_use_stale_then_fresh_resp Apr 26 12:21:12 192.168.122.209 [73022.978687] Start test: cache.test_cache_stale.TestCacheUseStaleTimeoutH2.test_timeout_no_stale Apr 26 12:21:13 192.168.122.209 [73024.592601] [tdb] Start Tempesta DB Apr 26 12:21:14 192.168.122.209 [73024.738528] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:21:15 192.168.122.209 [73026.141352] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73026.141352] Maybe that's fine, but it's worth checking the [73026.141352] config - if there is no relations between the [73026.141352] names, then host name confusion attack is possible. Apr 26 12:21:15 192.168.122.209 [73026.243735] [tempesta fw] Configuration processing is completed. Apr 26 12:21:15 192.168.122.209 [73026.301523] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:21:15 192.168.122.209 [73026.713075] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:21:16 192.168.122.209 [73026.738995] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:21:16 192.168.122.209 [73026.764638] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:21:16 192.168.122.209 [73026.803773] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:21:16 192.168.122.209 [73026.847749] [tempesta fw] Tempesta FW is ready Apr 26 12:21:19 192.168.122.209 [73030.056512] [tempesta fw] Warning: request evicted: the number of retries exceeded, status 504: 192.168.122.196 Apr 26 12:21:19 192.168.122.209 [73030.510097] [tdb] Close table 'client0.tdb' Apr 26 12:21:19 192.168.122.209 [73030.693602] [tdb] Close table 'sessions0.tdb' Apr 26 12:21:23 192.168.122.209 [73033.860409] [tdb] Close table 'cache0.tdb' Apr 26 12:21:23 192.168.122.209 [73034.098197] [tdb] Close table 'filter0.tdb' Apr 26 12:21:23 192.168.122.209 [73034.098602] [tempesta fw] modules are stopped Apr 26 12:21:23 192.168.122.209 [73034.280131] [tempesta fw] exiting... Apr 26 12:21:23 192.168.122.209 [73034.428203] [tdb] Shutdown Tempesta DB Apr 26 12:21:24 192.168.122.209 [73034.868349] End test: cache.test_cache_stale.TestCacheUseStaleTimeoutH2.test_timeout_no_stale Apr 26 12:21:24 192.168.122.209 [73034.901447] Start test: cache.test_cache_stale.TestCacheUseStaleTimeoutH2.test_use_stale_timeout Apr 26 12:21:25 192.168.122.209 [73036.513654] [tdb] Start Tempesta DB Apr 26 12:21:25 192.168.122.209 [73036.644351] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:21:27 192.168.122.209 [73038.093644] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73038.093644] Maybe that's fine, but it's worth checking the [73038.093644] config - if there is no relations between the [73038.093644] names, then host name confusion attack is possible. Apr 26 12:21:27 192.168.122.209 [73038.184309] [tempesta fw] Configuration processing is completed. Apr 26 12:21:27 192.168.122.209 [73038.242124] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:21:27 192.168.122.209 [73038.672367] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:21:27 192.168.122.209 [73038.698607] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:21:27 192.168.122.209 [73038.724122] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:21:28 192.168.122.209 [73038.771921] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:21:28 192.168.122.209 [73038.811880] [tempesta fw] Tempesta FW is ready Apr 26 12:21:31 192.168.122.209 [73042.004605] [tempesta fw] Warning: request evicted: the number of retries exceeded, status 504: 192.168.122.196 Apr 26 12:21:31 192.168.122.209 [73042.455639] [tdb] Close table 'client0.tdb' Apr 26 12:21:31 192.168.122.209 [73042.639506] [tdb] Close table 'sessions0.tdb' Apr 26 12:21:35 192.168.122.209 [73045.862236] [tdb] Close table 'cache0.tdb' Apr 26 12:21:35 192.168.122.209 [73046.095364] [tdb] Close table 'filter0.tdb' Apr 26 12:21:35 192.168.122.209 [73046.095791] [tempesta fw] modules are stopped Apr 26 12:21:35 192.168.122.209 [73046.312357] [tempesta fw] exiting... Apr 26 12:21:35 192.168.122.209 [73046.460511] [tdb] Shutdown Tempesta DB Apr 26 12:21:36 192.168.122.209 [73046.798240] End test: cache.test_cache_stale.TestCacheUseStaleTimeoutH2.test_use_stale_timeout Apr 26 12:21:36 192.168.122.209 [73046.879763] Start test: cache.test_cache_stale.TestCacheUseStaleTimeoutHttp.test_timeout_no_stale Apr 26 12:21:37 192.168.122.209 [73048.477232] [tdb] Start Tempesta DB Apr 26 12:21:37 192.168.122.209 [73048.605808] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:21:39 192.168.122.209 [73050.109757] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73050.109757] Maybe that's fine, but it's worth checking the [73050.109757] config - if there is no relations between the [73050.109757] names, then host name confusion attack is possible. Apr 26 12:21:39 192.168.122.209 [73050.216380] [tempesta fw] Configuration processing is completed. Apr 26 12:21:39 192.168.122.209 [73050.272179] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:21:39 192.168.122.209 [73050.690693] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:21:39 192.168.122.209 [73050.717323] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:21:40 192.168.122.209 [73050.743497] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:21:40 192.168.122.209 [73050.804069] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:21:40 192.168.122.209 [73050.844037] [tempesta fw] Tempesta FW is ready Apr 26 12:21:43 192.168.122.209 [73054.104752] [tempesta fw] Warning: request evicted: the number of retries exceeded, status 504: 192.168.122.196 Apr 26 12:21:43 192.168.122.209 [73054.567169] [tdb] Close table 'client0.tdb' Apr 26 12:21:44 192.168.122.209 [73054.760973] [tdb] Close table 'sessions0.tdb' Apr 26 12:21:47 192.168.122.209 [73057.972444] [tdb] Close table 'cache0.tdb' Apr 26 12:21:47 192.168.122.209 [73058.229186] [tdb] Close table 'filter0.tdb' Apr 26 12:21:47 192.168.122.209 [73058.229609] [tempesta fw] modules are stopped Apr 26 12:21:47 192.168.122.209 [73058.413618] [tempesta fw] exiting... Apr 26 12:21:47 192.168.122.209 [73058.540979] [tdb] Shutdown Tempesta DB Apr 26 12:21:48 192.168.122.209 [73058.892560] End test: cache.test_cache_stale.TestCacheUseStaleTimeoutHttp.test_timeout_no_stale Apr 26 12:21:48 192.168.122.209 [73058.969721] Start test: cache.test_cache_stale.TestCacheUseStaleTimeoutHttp.test_use_stale_timeout Apr 26 12:21:49 192.168.122.209 [73060.580300] [tdb] Start Tempesta DB Apr 26 12:21:49 192.168.122.209 [73060.715452] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:21:51 192.168.122.209 [73062.217936] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73062.217936] Maybe that's fine, but it's worth checking the [73062.217936] config - if there is no relations between the [73062.217936] names, then host name confusion attack is possible. Apr 26 12:21:51 192.168.122.209 [73062.320202] [tempesta fw] Configuration processing is completed. Apr 26 12:21:51 192.168.122.209 [73062.385068] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:21:52 192.168.122.209 [73062.818791] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:21:52 192.168.122.209 [73062.845099] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:21:52 192.168.122.209 [73062.870269] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:21:52 192.168.122.209 [73062.916241] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:21:52 192.168.122.209 [73062.964171] [tempesta fw] Tempesta FW is ready Apr 26 12:21:55 192.168.122.209 [73066.208634] [tempesta fw] Warning: request evicted: the number of retries exceeded, status 504: 192.168.122.196 Apr 26 12:21:56 192.168.122.209 [73067.307190] [tdb] Close table 'client0.tdb' Apr 26 12:21:56 192.168.122.209 [73067.597442] [tdb] Close table 'sessions0.tdb' Apr 26 12:22:00 192.168.122.209 [73071.483212] [tdb] Close table 'cache0.tdb' Apr 26 12:22:00 192.168.122.209 [73071.724741] [tdb] Close table 'filter0.tdb' Apr 26 12:22:00 192.168.122.209 [73071.725177] [tempesta fw] modules are stopped Apr 26 12:22:01 192.168.122.209 [73071.908430] [tempesta fw] exiting... Apr 26 12:22:01 192.168.122.209 [73072.029634] [tdb] Shutdown Tempesta DB Apr 26 12:22:01 192.168.122.209 [73072.381227] End test: cache.test_cache_stale.TestCacheUseStaleTimeoutHttp.test_use_stale_timeout Apr 26 12:22:01 192.168.122.209 [73072.407747] Start test: cache.test_conditional.TestConditionalH2.test_correct_none_match_and_modified_since Apr 26 12:22:03 192.168.122.209 [73073.790444] [tdb] Start Tempesta DB Apr 26 12:22:03 192.168.122.209 [73073.942471] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:22:04 192.168.122.209 [73075.413694] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73075.413694] Maybe that's fine, but it's worth checking the [73075.413694] config - if there is no relations between the [73075.413694] names, then host name confusion attack is possible. Apr 26 12:22:04 192.168.122.209 [73075.552386] [tempesta fw] Configuration processing is completed. Apr 26 12:22:04 192.168.122.209 [73075.606531] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:22:05 192.168.122.209 [73076.019169] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:22:05 192.168.122.209 [73076.044696] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:22:05 192.168.122.209 [73076.069965] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:22:05 192.168.122.209 [73076.132403] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:22:05 192.168.122.209 [73076.134154] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:22:05 192.168.122.209 [73076.176291] [tempesta fw] Tempesta FW is ready Apr 26 12:22:06 192.168.122.209 [73076.804684] [tdb] Close table 'client0.tdb' Apr 26 12:22:06 192.168.122.209 [73076.991516] [tdb] Close table 'sessions0.tdb' Apr 26 12:22:09 192.168.122.209 [73080.178234] [tdb] Close table 'cache0.tdb' Apr 26 12:22:09 192.168.122.209 [73080.414462] [tdb] Close table 'filter0.tdb' Apr 26 12:22:09 192.168.122.209 [73080.414914] [tempesta fw] modules are stopped Apr 26 12:22:09 192.168.122.209 [73080.612312] [tempesta fw] exiting... Apr 26 12:22:10 192.168.122.209 [73080.749576] [tdb] Shutdown Tempesta DB Apr 26 12:22:10 192.168.122.209 [73081.163832] End test: cache.test_conditional.TestConditionalH2.test_correct_none_match_and_modified_since Apr 26 12:22:10 192.168.122.209 [73081.199262] Start test: cache.test_conditional.TestConditionalH2.test_incorrect_none_match_and_correct_modified_since Apr 26 12:22:11 192.168.122.209 [73082.610000] [tdb] Start Tempesta DB Apr 26 12:22:12 192.168.122.209 [73082.750162] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:22:13 192.168.122.209 [73084.289814] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73084.289814] Maybe that's fine, but it's worth checking the [73084.289814] config - if there is no relations between the [73084.289814] names, then host name confusion attack is possible. Apr 26 12:22:13 192.168.122.209 [73084.420524] [tempesta fw] Configuration processing is completed. Apr 26 12:22:13 192.168.122.209 [73084.483307] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:22:14 192.168.122.209 [73085.055561] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:22:14 192.168.122.209 [73085.093917] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:22:14 192.168.122.209 [73085.120423] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:22:14 192.168.122.209 [73085.160517] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:22:14 192.168.122.209 [73085.162022] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:22:14 192.168.122.209 [73085.200543] [tempesta fw] Tempesta FW is ready Apr 26 12:22:15 192.168.122.209 [73085.864042] [tdb] Close table 'client0.tdb' Apr 26 12:22:15 192.168.122.209 [73086.060655] [tdb] Close table 'sessions0.tdb' Apr 26 12:22:18 192.168.122.209 [73089.280785] [tdb] Close table 'cache0.tdb' Apr 26 12:22:18 192.168.122.209 [73089.503677] [tdb] Close table 'filter0.tdb' Apr 26 12:22:18 192.168.122.209 [73089.504074] [tempesta fw] modules are stopped Apr 26 12:22:18 192.168.122.209 [73089.697708] [tempesta fw] exiting... Apr 26 12:22:19 192.168.122.209 [73089.806489] [tdb] Shutdown Tempesta DB Apr 26 12:22:19 192.168.122.209 [73090.196711] End test: cache.test_conditional.TestConditionalH2.test_incorrect_none_match_and_correct_modified_since Apr 26 12:22:19 192.168.122.209 [73090.226244] Start test: cache.test_conditional.TestConditionalH2.test_mod_since Apr 26 12:22:21 192.168.122.209 [73091.746947] [tdb] Start Tempesta DB Apr 26 12:22:21 192.168.122.209 [73091.892923] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:22:22 192.168.122.209 [73093.437890] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73093.437890] Maybe that's fine, but it's worth checking the [73093.437890] config - if there is no relations between the [73093.437890] names, then host name confusion attack is possible. Apr 26 12:22:22 192.168.122.209 [73093.576729] [tempesta fw] Configuration processing is completed. Apr 26 12:22:22 192.168.122.209 [73093.627852] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:22:23 192.168.122.209 [73094.034165] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:22:23 192.168.122.209 [73094.060493] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:22:23 192.168.122.209 [73094.086316] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:22:23 192.168.122.209 [73094.128630] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:22:23 192.168.122.209 [73094.130363] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:22:23 192.168.122.209 [73094.188588] [tempesta fw] Tempesta FW is ready Apr 26 12:22:24 192.168.122.209 [73094.917421] [tdb] Close table 'client0.tdb' Apr 26 12:22:24 192.168.122.209 [73095.103221] [tdb] Close table 'sessions0.tdb' Apr 26 12:22:27 192.168.122.209 [73098.437425] [tdb] Close table 'cache0.tdb' Apr 26 12:22:27 192.168.122.209 [73098.697543] [tdb] Close table 'filter0.tdb' Apr 26 12:22:27 192.168.122.209 [73098.697994] [tempesta fw] modules are stopped Apr 26 12:22:28 192.168.122.209 [73098.889956] [tempesta fw] exiting... Apr 26 12:22:28 192.168.122.209 [73099.040265] [tdb] Shutdown Tempesta DB Apr 26 12:22:28 192.168.122.209 [73099.429532] End test: cache.test_conditional.TestConditionalH2.test_mod_since Apr 26 12:22:28 192.168.122.209 [73099.461602] Start test: cache.test_conditional.TestConditionalH2.test_mod_since_nc Apr 26 12:22:30 192.168.122.209 [73101.009972] [tdb] Start Tempesta DB Apr 26 12:22:30 192.168.122.209 [73101.143811] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:22:32 192.168.122.209 [73102.753980] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73102.753980] Maybe that's fine, but it's worth checking the [73102.753980] config - if there is no relations between the [73102.753980] names, then host name confusion attack is possible. Apr 26 12:22:32 192.168.122.209 [73102.892729] [tempesta fw] Configuration processing is completed. Apr 26 12:22:32 192.168.122.209 [73102.955697] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:22:32 192.168.122.209 [73103.378976] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:22:32 192.168.122.209 [73103.405092] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:22:32 192.168.122.209 [73103.430447] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:22:32 192.168.122.209 [73103.508749] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:22:32 192.168.122.209 [73103.510493] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:22:32 192.168.122.209 [73103.548715] [tempesta fw] Tempesta FW is ready Apr 26 12:22:33 192.168.122.209 [73104.190611] [tdb] Close table 'client0.tdb' Apr 26 12:22:33 192.168.122.209 [73104.387850] [tdb] Close table 'sessions0.tdb' Apr 26 12:22:36 192.168.122.209 [73107.649466] [tdb] Close table 'cache0.tdb' Apr 26 12:22:37 192.168.122.209 [73107.919045] [tdb] Close table 'filter0.tdb' Apr 26 12:22:37 192.168.122.209 [73107.919469] [tempesta fw] modules are stopped Apr 26 12:22:37 192.168.122.209 [73108.108296] [tempesta fw] exiting... Apr 26 12:22:37 192.168.122.209 [73108.239524] [tdb] Shutdown Tempesta DB Apr 26 12:22:37 192.168.122.209 [73108.680246] End test: cache.test_conditional.TestConditionalH2.test_mod_since_nc Apr 26 12:22:37 192.168.122.209 [73108.717201] Start test: cache.test_conditional.TestConditionalH2.test_mod_since_nc_with_invalid_date Apr 26 12:22:39 192.168.122.209 [73110.303821] [tdb] Start Tempesta DB Apr 26 12:22:39 192.168.122.209 [73110.436845] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:22:41 192.168.122.209 [73111.961602] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73111.961602] Maybe that's fine, but it's worth checking the [73111.961602] config - if there is no relations between the [73111.961602] names, then host name confusion attack is possible. Apr 26 12:22:41 192.168.122.209 [73112.092856] [tempesta fw] Configuration processing is completed. Apr 26 12:22:41 192.168.122.209 [73112.152609] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:22:41 192.168.122.209 [73112.660688] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:22:41 192.168.122.209 [73112.688150] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:22:41 192.168.122.209 [73112.714973] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:22:42 192.168.122.209 [73112.768775] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:22:42 192.168.122.209 [73112.770511] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:22:42 192.168.122.209 [73112.812801] [tempesta fw] Tempesta FW is ready Apr 26 12:22:42 192.168.122.209 [73113.493645] [tdb] Close table 'client0.tdb' Apr 26 12:22:42 192.168.122.209 [73113.699890] [tdb] Close table 'sessions0.tdb' Apr 26 12:22:46 192.168.122.209 [73116.957676] [tdb] Close table 'cache0.tdb' Apr 26 12:22:46 192.168.122.209 [73117.210979] [tdb] Close table 'filter0.tdb' Apr 26 12:22:46 192.168.122.209 [73117.211408] [tempesta fw] modules are stopped Apr 26 12:22:46 192.168.122.209 [73117.396335] [tempesta fw] exiting... Apr 26 12:22:46 192.168.122.209 [73117.523468] [tdb] Shutdown Tempesta DB Apr 26 12:22:47 192.168.122.209 [73117.970103] End test: cache.test_conditional.TestConditionalH2.test_mod_since_nc_with_invalid_date Apr 26 12:22:47 192.168.122.209 [73118.002872] Start test: cache.test_conditional.TestConditionalH2.test_none_match Apr 26 12:22:48 192.168.122.209 [73119.603805] [tdb] Start Tempesta DB Apr 26 12:22:49 192.168.122.209 [73119.769729] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:22:50 192.168.122.209 [73121.270224] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73121.270224] Maybe that's fine, but it's worth checking the [73121.270224] config - if there is no relations between the [73121.270224] names, then host name confusion attack is possible. Apr 26 12:22:50 192.168.122.209 [73121.408958] [tempesta fw] Configuration processing is completed. Apr 26 12:22:50 192.168.122.209 [73121.464816] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:22:51 192.168.122.209 [73121.890594] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:22:51 192.168.122.209 [73121.917396] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:22:51 192.168.122.209 [73121.945418] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:22:51 192.168.122.209 [73121.988972] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:22:51 192.168.122.209 [73121.990712] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:22:51 192.168.122.209 [73122.028927] [tempesta fw] Tempesta FW is ready Apr 26 12:22:51 192.168.122.209 [73122.712891] [tdb] Close table 'client0.tdb' Apr 26 12:22:52 192.168.122.209 [73122.894573] [tdb] Close table 'sessions0.tdb' Apr 26 12:22:55 192.168.122.209 [73126.166579] [tdb] Close table 'cache0.tdb' Apr 26 12:22:55 192.168.122.209 [73126.402795] [tdb] Close table 'filter0.tdb' Apr 26 12:22:55 192.168.122.209 [73126.403225] [tempesta fw] modules are stopped Apr 26 12:22:55 192.168.122.209 [73126.576542] [tempesta fw] exiting... Apr 26 12:22:55 192.168.122.209 [73126.675045] [tdb] Shutdown Tempesta DB Apr 26 12:22:56 192.168.122.209 [73127.053399] End test: cache.test_conditional.TestConditionalH2.test_none_match Apr 26 12:22:56 192.168.122.209 [73127.085661] Start test: cache.test_conditional.TestConditionalH2.test_none_match_HEAD Apr 26 12:22:58 192.168.122.209 [73128.839342] [tdb] Start Tempesta DB Apr 26 12:22:58 192.168.122.209 [73128.969823] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:22:59 192.168.122.209 [73130.558594] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73130.558594] Maybe that's fine, but it's worth checking the [73130.558594] config - if there is no relations between the [73130.558594] names, then host name confusion attack is possible. Apr 26 12:22:59 192.168.122.209 [73130.693094] [tempesta fw] Configuration processing is completed. Apr 26 12:23:00 192.168.122.209 [73130.744464] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:23:00 192.168.122.209 [73131.165538] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:23:00 192.168.122.209 [73131.192146] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:23:00 192.168.122.209 [73131.217872] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:23:00 192.168.122.209 [73131.257080] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:23:00 192.168.122.209 [73131.258826] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:23:00 192.168.122.209 [73131.297081] [tempesta fw] Tempesta FW is ready Apr 26 12:23:01 192.168.122.209 [73131.990385] [tdb] Close table 'client0.tdb' Apr 26 12:23:01 192.168.122.209 [73132.176312] [tdb] Close table 'sessions0.tdb' Apr 26 12:23:04 192.168.122.209 [73135.401709] [tdb] Close table 'cache0.tdb' Apr 26 12:23:04 192.168.122.209 [73135.644912] [tdb] Close table 'filter0.tdb' Apr 26 12:23:04 192.168.122.209 [73135.646162] [tempesta fw] modules are stopped Apr 26 12:23:05 192.168.122.209 [73135.839375] [tempesta fw] exiting... Apr 26 12:23:05 192.168.122.209 [73135.982983] [tdb] Shutdown Tempesta DB Apr 26 12:23:05 192.168.122.209 [73136.379923] End test: cache.test_conditional.TestConditionalH2.test_none_match_HEAD Apr 26 12:23:05 192.168.122.209 [73136.458756] Start test: cache.test_conditional.TestConditionalH2.test_none_match_any Apr 26 12:23:07 192.168.122.209 [73138.068119] [tdb] Start Tempesta DB Apr 26 12:23:07 192.168.122.209 [73138.218734] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:23:09 192.168.122.209 [73139.726498] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73139.726498] Maybe that's fine, but it's worth checking the [73139.726498] config - if there is no relations between the [73139.726498] names, then host name confusion attack is possible. Apr 26 12:23:09 192.168.122.209 [73139.869346] [tempesta fw] Configuration processing is completed. Apr 26 12:23:09 192.168.122.209 [73139.928519] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:23:09 192.168.122.209 [73140.341209] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:23:09 192.168.122.209 [73140.367637] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:23:09 192.168.122.209 [73140.399056] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:23:09 192.168.122.209 [73140.449227] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:23:09 192.168.122.209 [73140.450967] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:23:09 192.168.122.209 [73140.497165] [tempesta fw] Tempesta FW is ready Apr 26 12:23:10 192.168.122.209 [73141.208647] [tdb] Close table 'client0.tdb' Apr 26 12:23:10 192.168.122.209 [73141.403849] [tdb] Close table 'sessions0.tdb' Apr 26 12:23:13 192.168.122.209 [73144.698002] [tdb] Close table 'cache0.tdb' Apr 26 12:23:14 192.168.122.209 [73144.937263] [tdb] Close table 'filter0.tdb' Apr 26 12:23:14 192.168.122.209 [73144.937680] [tempesta fw] modules are stopped Apr 26 12:23:14 192.168.122.209 [73145.162552] [tempesta fw] exiting... Apr 26 12:23:14 192.168.122.209 [73145.286741] [tdb] Shutdown Tempesta DB Apr 26 12:23:15 192.168.122.209 [73145.748848] End test: cache.test_conditional.TestConditionalH2.test_none_match_any Apr 26 12:23:15 192.168.122.209 [73145.784073] Start test: cache.test_conditional.TestConditionalH2.test_none_match_list Apr 26 12:23:16 192.168.122.209 [73147.422938] [tdb] Start Tempesta DB Apr 26 12:23:16 192.168.122.209 [73147.551786] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:23:18 192.168.122.209 [73149.046590] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73149.046590] Maybe that's fine, but it's worth checking the [73149.046590] config - if there is no relations between the [73149.046590] names, then host name confusion attack is possible. Apr 26 12:23:18 192.168.122.209 [73149.193360] [tempesta fw] Configuration processing is completed. Apr 26 12:23:18 192.168.122.209 [73149.244203] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:23:18 192.168.122.209 [73149.686926] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:23:18 192.168.122.209 [73149.713678] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:23:19 192.168.122.209 [73149.741129] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:23:19 192.168.122.209 [73149.781314] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:23:19 192.168.122.209 [73149.782857] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:23:19 192.168.122.209 [73149.825261] [tempesta fw] Tempesta FW is ready Apr 26 12:23:19 192.168.122.209 [73150.490793] [tdb] Close table 'client0.tdb' Apr 26 12:23:19 192.168.122.209 [73150.684506] [tdb] Close table 'sessions0.tdb' Apr 26 12:23:23 192.168.122.209 [73153.956718] [tdb] Close table 'cache0.tdb' Apr 26 12:23:23 192.168.122.209 [73154.210349] [tdb] Close table 'filter0.tdb' Apr 26 12:23:23 192.168.122.209 [73154.210851] [tempesta fw] modules are stopped Apr 26 12:23:23 192.168.122.209 [73154.396094] [tempesta fw] exiting... Apr 26 12:23:23 192.168.122.209 [73154.532281] [tdb] Shutdown Tempesta DB Apr 26 12:23:24 192.168.122.209 [73154.942564] End test: cache.test_conditional.TestConditionalH2.test_none_match_list Apr 26 12:23:24 192.168.122.209 [73154.975858] Start test: cache.test_conditional.TestConditionalH2.test_none_match_nc_GET Apr 26 12:23:25 192.168.122.209 [73156.559859] [tdb] Start Tempesta DB Apr 26 12:23:25 192.168.122.209 [73156.695025] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:23:27 192.168.122.209 [73158.362725] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73158.362725] Maybe that's fine, but it's worth checking the [73158.362725] config - if there is no relations between the [73158.362725] names, then host name confusion attack is possible. Apr 26 12:23:27 192.168.122.209 [73158.493491] [tempesta fw] Configuration processing is completed. Apr 26 12:23:27 192.168.122.209 [73158.550337] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:23:28 192.168.122.209 [73158.972373] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:23:28 192.168.122.209 [73158.998236] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:23:28 192.168.122.209 [73159.024313] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:23:28 192.168.122.209 [73159.069535] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:23:28 192.168.122.209 [73159.071311] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:23:28 192.168.122.209 [73159.117380] [tempesta fw] Tempesta FW is ready Apr 26 12:23:29 192.168.122.209 [73159.771754] [tdb] Close table 'client0.tdb' Apr 26 12:23:29 192.168.122.209 [73159.957898] [tdb] Close table 'sessions0.tdb' Apr 26 12:23:32 192.168.122.209 [73163.151923] [tdb] Close table 'cache0.tdb' Apr 26 12:23:32 192.168.122.209 [73163.381591] [tdb] Close table 'filter0.tdb' Apr 26 12:23:32 192.168.122.209 [73163.382005] [tempesta fw] modules are stopped Apr 26 12:23:32 192.168.122.209 [73163.572876] [tempesta fw] exiting... Apr 26 12:23:33 192.168.122.209 [73163.728660] [tdb] Shutdown Tempesta DB Apr 26 12:23:33 192.168.122.209 [73164.124072] End test: cache.test_conditional.TestConditionalH2.test_none_match_nc_GET Apr 26 12:23:33 192.168.122.209 [73164.213908] Start test: cache.test_conditional.TestConditionalH2.test_none_match_nc_HEAD Apr 26 12:23:35 192.168.122.209 [73165.800702] [tdb] Start Tempesta DB Apr 26 12:23:35 192.168.122.209 [73165.941186] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:23:36 192.168.122.209 [73167.558866] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73167.558866] Maybe that's fine, but it's worth checking the [73167.558866] config - if there is no relations between the [73167.558866] names, then host name confusion attack is possible. Apr 26 12:23:36 192.168.122.209 [73167.697631] [tempesta fw] Configuration processing is completed. Apr 26 12:23:37 192.168.122.209 [73167.762930] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:23:37 192.168.122.209 [73168.225939] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:23:37 192.168.122.209 [73168.256146] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:23:37 192.168.122.209 [73168.288534] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:23:37 192.168.122.209 [73168.325565] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:23:37 192.168.122.209 [73168.327321] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:23:37 192.168.122.209 [73168.373493] [tempesta fw] Tempesta FW is ready Apr 26 12:23:38 192.168.122.209 [73169.050283] [tdb] Close table 'client0.tdb' Apr 26 12:23:38 192.168.122.209 [73169.223822] [tdb] Close table 'sessions0.tdb' Apr 26 12:23:41 192.168.122.209 [73172.469125] [tdb] Close table 'cache0.tdb' Apr 26 12:23:41 192.168.122.209 [73172.726846] [tdb] Close table 'filter0.tdb' Apr 26 12:23:41 192.168.122.209 [73172.727290] [tempesta fw] modules are stopped Apr 26 12:23:42 192.168.122.209 [73172.951479] [tempesta fw] exiting... Apr 26 12:23:42 192.168.122.209 [73173.098919] [tdb] Shutdown Tempesta DB Apr 26 12:23:42 192.168.122.209 [73173.539064] End test: cache.test_conditional.TestConditionalH2.test_none_match_nc_HEAD Apr 26 12:23:42 192.168.122.209 [73173.575833] Start test: cache.test_conditional.TestConditionalH2.test_none_match_no_quotes_etag Apr 26 12:23:44 192.168.122.209 [73174.957103] [tdb] Start Tempesta DB Apr 26 12:23:44 192.168.122.209 [73175.107894] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:23:45 192.168.122.209 [73176.566991] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73176.566991] Maybe that's fine, but it's worth checking the [73176.566991] config - if there is no relations between the [73176.566991] names, then host name confusion attack is possible. Apr 26 12:23:45 192.168.122.209 [73176.697696] [tempesta fw] Configuration processing is completed. Apr 26 12:23:46 192.168.122.209 [73176.758288] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:23:46 192.168.122.209 [73177.261576] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:23:46 192.168.122.209 [73177.292498] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:23:46 192.168.122.209 [73177.323091] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:23:46 192.168.122.209 [73177.361609] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:23:46 192.168.122.209 [73177.362638] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:23:46 192.168.122.209 [73177.405637] [tempesta fw] Tempesta FW is ready Apr 26 12:23:47 192.168.122.209 [73178.085258] [tdb] Close table 'client0.tdb' Apr 26 12:23:47 192.168.122.209 [73178.263301] [tdb] Close table 'sessions0.tdb' Apr 26 12:23:50 192.168.122.209 [73181.532775] [tdb] Close table 'cache0.tdb' Apr 26 12:23:51 192.168.122.209 [73181.803499] [tdb] Close table 'filter0.tdb' Apr 26 12:23:51 192.168.122.209 [73181.803927] [tempesta fw] modules are stopped Apr 26 12:23:51 192.168.122.209 [73182.042176] [tempesta fw] exiting... Apr 26 12:23:51 192.168.122.209 [73182.176890] [tdb] Shutdown Tempesta DB Apr 26 12:23:51 192.168.122.209 [73182.554496] End test: cache.test_conditional.TestConditionalH2.test_none_match_no_quotes_etag Apr 26 12:23:51 192.168.122.209 [73182.584692] Start test: cache.test_conditional.TestConditionalH2.test_none_match_no_quotes_etag_with_extra_spaces Apr 26 12:23:53 192.168.122.209 [73183.964355] [tdb] Start Tempesta DB Apr 26 12:23:53 192.168.122.209 [73184.118365] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:23:54 192.168.122.209 [73185.551088] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73185.551088] Maybe that's fine, but it's worth checking the [73185.551088] config - if there is no relations between the [73185.551088] names, then host name confusion attack is possible. Apr 26 12:23:54 192.168.122.209 [73185.689793] [tempesta fw] Configuration processing is completed. Apr 26 12:23:55 192.168.122.209 [73185.752118] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:23:55 192.168.122.209 [73186.185595] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:23:55 192.168.122.209 [73186.221967] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:23:55 192.168.122.209 [73186.249144] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:23:55 192.168.122.209 [73186.301777] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:23:55 192.168.122.209 [73186.303516] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:23:55 192.168.122.209 [73186.353721] [tempesta fw] Tempesta FW is ready Apr 26 12:23:56 192.168.122.209 [73187.003398] [tdb] Close table 'client0.tdb' Apr 26 12:23:56 192.168.122.209 [73187.190302] [tdb] Close table 'sessions0.tdb' Apr 26 12:23:59 192.168.122.209 [73190.340250] [tdb] Close table 'cache0.tdb' Apr 26 12:23:59 192.168.122.209 [73190.608396] [tdb] Close table 'filter0.tdb' Apr 26 12:23:59 192.168.122.209 [73190.608815] [tempesta fw] modules are stopped Apr 26 12:24:00 192.168.122.209 [73190.809390] [tempesta fw] exiting... Apr 26 12:24:00 192.168.122.209 [73190.959918] [tdb] Shutdown Tempesta DB Apr 26 12:24:00 192.168.122.209 [73191.402813] End test: cache.test_conditional.TestConditionalH2.test_none_match_no_quotes_etag_with_extra_spaces Apr 26 12:24:00 192.168.122.209 [73191.437981] Start test: cache.test_conditional.TestConditionalH2.test_none_match_weak_all Apr 26 12:24:02 192.168.122.209 [73192.865966] [tdb] Start Tempesta DB Apr 26 12:24:02 192.168.122.209 [73193.005023] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:24:03 192.168.122.209 [73194.479230] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73194.479230] Maybe that's fine, but it's worth checking the [73194.479230] config - if there is no relations between the [73194.479230] names, then host name confusion attack is possible. Apr 26 12:24:03 192.168.122.209 [73194.617901] [tempesta fw] Configuration processing is completed. Apr 26 12:24:03 192.168.122.209 [73194.676291] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:24:04 192.168.122.209 [73195.146810] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:24:04 192.168.122.209 [73195.174544] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:24:04 192.168.122.209 [73195.201912] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:24:04 192.168.122.209 [73195.241912] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:24:04 192.168.122.209 [73195.243654] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:24:04 192.168.122.209 [73195.293860] [tempesta fw] Tempesta FW is ready Apr 26 12:24:05 192.168.122.209 [73195.904904] [tdb] Close table 'client0.tdb' Apr 26 12:24:05 192.168.122.209 [73196.103469] [tdb] Close table 'sessions0.tdb' Apr 26 12:24:08 192.168.122.209 [73199.344546] [tdb] Close table 'cache0.tdb' Apr 26 12:24:08 192.168.122.209 [73199.597174] [tdb] Close table 'filter0.tdb' Apr 26 12:24:08 192.168.122.209 [73199.597667] [tempesta fw] modules are stopped Apr 26 12:24:09 192.168.122.209 [73199.781321] [tempesta fw] exiting... Apr 26 12:24:09 192.168.122.209 [73199.918525] [tdb] Shutdown Tempesta DB Apr 26 12:24:09 192.168.122.209 [73200.370346] End test: cache.test_conditional.TestConditionalH2.test_none_match_weak_all Apr 26 12:24:09 192.168.122.209 [73200.400901] Start test: cache.test_conditional.TestConditionalH2.test_none_match_weak_clnt Apr 26 12:24:11 192.168.122.209 [73201.848881] [tdb] Start Tempesta DB Apr 26 12:24:11 192.168.122.209 [73201.985267] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:24:12 192.168.122.209 [73203.491383] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73203.491383] Maybe that's fine, but it's worth checking the [73203.491383] config - if there is no relations between the [73203.491383] names, then host name confusion attack is possible. Apr 26 12:24:12 192.168.122.209 [73203.630034] [tempesta fw] Configuration processing is completed. Apr 26 12:24:12 192.168.122.209 [73203.687533] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:24:13 192.168.122.209 [73204.198352] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:24:13 192.168.122.209 [73204.233212] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:24:13 192.168.122.209 [73204.270028] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:24:13 192.168.122.209 [73204.310016] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:24:13 192.168.122.209 [73204.311777] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:24:13 192.168.122.209 [73204.349939] [tempesta fw] Tempesta FW is ready Apr 26 12:24:14 192.168.122.209 [73205.053163] [tdb] Close table 'client0.tdb' Apr 26 12:24:14 192.168.122.209 [73205.242463] [tdb] Close table 'sessions0.tdb' Apr 26 12:24:17 192.168.122.209 [73208.572589] [tdb] Close table 'cache0.tdb' Apr 26 12:24:18 192.168.122.209 [73208.836244] [tdb] Close table 'filter0.tdb' Apr 26 12:24:18 192.168.122.209 [73208.836707] [tempesta fw] modules are stopped Apr 26 12:24:18 192.168.122.209 [73209.046883] [tempesta fw] exiting... Apr 26 12:24:18 192.168.122.209 [73209.219707] [tdb] Shutdown Tempesta DB Apr 26 12:24:18 192.168.122.209 [73209.585694] End test: cache.test_conditional.TestConditionalH2.test_none_match_weak_clnt Apr 26 12:24:18 192.168.122.209 [73209.612372] Start test: cache.test_conditional.TestConditionalH2.test_none_match_weak_srv Apr 26 12:24:20 192.168.122.209 [73211.005591] [tdb] Start Tempesta DB Apr 26 12:24:20 192.168.122.209 [73211.149173] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:24:21 192.168.122.209 [73212.567400] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73212.567400] Maybe that's fine, but it's worth checking the [73212.567400] config - if there is no relations between the [73212.567400] names, then host name confusion attack is possible. Apr 26 12:24:21 192.168.122.209 [73212.706107] [tempesta fw] Configuration processing is completed. Apr 26 12:24:22 192.168.122.209 [73212.758074] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:24:22 192.168.122.209 [73213.183378] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:24:22 192.168.122.209 [73213.210653] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:24:22 192.168.122.209 [73213.237292] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:24:22 192.168.122.209 [73213.294144] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:24:22 192.168.122.209 [73213.295923] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:24:22 192.168.122.209 [73213.338052] [tempesta fw] Tempesta FW is ready Apr 26 12:24:23 192.168.122.209 [73214.004049] [tdb] Close table 'client0.tdb' Apr 26 12:24:23 192.168.122.209 [73214.188973] [tdb] Close table 'sessions0.tdb' Apr 26 12:24:26 192.168.122.209 [73217.351140] [tdb] Close table 'cache0.tdb' Apr 26 12:24:26 192.168.122.209 [73217.601699] [tdb] Close table 'filter0.tdb' Apr 26 12:24:26 192.168.122.209 [73217.602151] [tempesta fw] modules are stopped Apr 26 12:24:27 192.168.122.209 [73217.806016] [tempesta fw] exiting... Apr 26 12:24:27 192.168.122.209 [73217.945542] [tdb] Shutdown Tempesta DB Apr 26 12:24:27 192.168.122.209 [73218.312862] End test: cache.test_conditional.TestConditionalH2.test_none_match_weak_srv Apr 26 12:24:27 192.168.122.209 [73218.395988] Start test: cache.test_conditional.TestConditionalH2.test_response_without_last_modified Apr 26 12:24:29 192.168.122.209 [73219.757522] [tdb] Start Tempesta DB Apr 26 12:24:29 192.168.122.209 [73219.914350] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:24:30 192.168.122.209 [73221.327511] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73221.327511] Maybe that's fine, but it's worth checking the [73221.327511] config - if there is no relations between the [73221.327511] names, then host name confusion attack is possible. Apr 26 12:24:30 192.168.122.209 [73221.462220] [tempesta fw] Configuration processing is completed. Apr 26 12:24:30 192.168.122.209 [73221.516199] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:24:31 192.168.122.209 [73221.936069] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:24:31 192.168.122.209 [73221.963248] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:24:31 192.168.122.209 [73221.990386] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:24:31 192.168.122.209 [73222.030216] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:24:31 192.168.122.209 [73222.031948] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:24:31 192.168.122.209 [73222.074161] [tempesta fw] Tempesta FW is ready Apr 26 12:24:32 192.168.122.209 [73222.745472] [tdb] Close table 'client0.tdb' Apr 26 12:24:32 192.168.122.209 [73222.933063] [tdb] Close table 'sessions0.tdb' Apr 26 12:24:35 192.168.122.209 [73226.063308] [tdb] Close table 'cache0.tdb' Apr 26 12:24:35 192.168.122.209 [73226.303702] [tdb] Close table 'filter0.tdb' Apr 26 12:24:35 192.168.122.209 [73226.304139] [tempesta fw] modules are stopped Apr 26 12:24:35 192.168.122.209 [73226.525989] [tempesta fw] exiting... Apr 26 12:24:35 192.168.122.209 [73226.652963] [tdb] Shutdown Tempesta DB Apr 26 12:24:36 192.168.122.209 [73227.020014] End test: cache.test_conditional.TestConditionalH2.test_response_without_last_modified Apr 26 12:24:36 192.168.122.209 [73227.061597] Start test: cache.test_conditional.TestConditionalH2.test_response_without_last_modified_and_date Apr 26 12:24:37 192.168.122.209 [73228.377604] [tdb] Start Tempesta DB Apr 26 12:24:37 192.168.122.209 [73228.510977] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:24:39 192.168.122.209 [73229.975624] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73229.975624] Maybe that's fine, but it's worth checking the [73229.975624] config - if there is no relations between the [73229.975624] names, then host name confusion attack is possible. Apr 26 12:24:39 192.168.122.209 [73230.114346] [tempesta fw] Configuration processing is completed. Apr 26 12:24:39 192.168.122.209 [73230.172974] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:24:39 192.168.122.209 [73230.592669] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:24:39 192.168.122.209 [73230.619066] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:24:39 192.168.122.209 [73230.644635] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:24:39 192.168.122.209 [73230.702378] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:24:39 192.168.122.209 [73230.704121] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:24:40 192.168.122.209 [73230.742283] [tempesta fw] Tempesta FW is ready Apr 26 12:24:40 192.168.122.209 [73231.417856] [tdb] Close table 'client0.tdb' Apr 26 12:24:40 192.168.122.209 [73231.604553] [tdb] Close table 'sessions0.tdb' Apr 26 12:24:44 192.168.122.209 [73234.791679] [tdb] Close table 'cache0.tdb' Apr 26 12:24:44 192.168.122.209 [73235.024053] [tdb] Close table 'filter0.tdb' Apr 26 12:24:44 192.168.122.209 [73235.024475] [tempesta fw] modules are stopped Apr 26 12:24:44 192.168.122.209 [73235.230995] [tempesta fw] exiting... Apr 26 12:24:44 192.168.122.209 [73235.343658] [tdb] Shutdown Tempesta DB Apr 26 12:24:45 192.168.122.209 [73235.732026] End test: cache.test_conditional.TestConditionalH2.test_response_without_last_modified_and_date Apr 26 12:24:45 192.168.122.209 [73235.762071] Start test: cache.test_conditional.TestConditionalH2.test_response_without_last_modified_and_date_nc Apr 26 12:24:46 192.168.122.209 [73237.178792] [tdb] Start Tempesta DB Apr 26 12:24:46 192.168.122.209 [73237.313022] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:24:48 192.168.122.209 [73238.771713] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73238.771713] Maybe that's fine, but it's worth checking the [73238.771713] config - if there is no relations between the [73238.771713] names, then host name confusion attack is possible. Apr 26 12:24:48 192.168.122.209 [73238.918475] [tempesta fw] Configuration processing is completed. Apr 26 12:24:48 192.168.122.209 [73238.974920] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:24:48 192.168.122.209 [73239.403568] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:24:48 192.168.122.209 [73239.429279] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:24:48 192.168.122.209 [73239.454634] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:24:48 192.168.122.209 [73239.510434] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:24:48 192.168.122.209 [73239.512184] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:24:48 192.168.122.209 [73239.550395] [tempesta fw] Tempesta FW is ready Apr 26 12:24:49 192.168.122.209 [73240.205141] [tdb] Close table 'client0.tdb' Apr 26 12:24:49 192.168.122.209 [73240.400688] [tdb] Close table 'sessions0.tdb' Apr 26 12:24:52 192.168.122.209 [73243.587051] [tdb] Close table 'cache0.tdb' Apr 26 12:24:53 192.168.122.209 [73243.829867] [tdb] Close table 'filter0.tdb' Apr 26 12:24:53 192.168.122.209 [73243.830308] [tempesta fw] modules are stopped Apr 26 12:24:53 192.168.122.209 [73244.022510] [tempesta fw] exiting... Apr 26 12:24:53 192.168.122.209 [73244.154060] [tdb] Shutdown Tempesta DB Apr 26 12:24:53 192.168.122.209 [73244.594300] End test: cache.test_conditional.TestConditionalH2.test_response_without_last_modified_and_date_nc Apr 26 12:24:53 192.168.122.209 [73244.629845] Start test: cache.test_conditional.TestConditionalH2.test_response_without_last_modified_nc Apr 26 12:24:55 192.168.122.209 [73246.019693] [tdb] Start Tempesta DB Apr 26 12:24:55 192.168.122.209 [73246.161748] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:24:56 192.168.122.209 [73247.667826] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73247.667826] Maybe that's fine, but it's worth checking the [73247.667826] config - if there is no relations between the [73247.667826] names, then host name confusion attack is possible. Apr 26 12:24:57 192.168.122.209 [73247.810613] [tempesta fw] Configuration processing is completed. Apr 26 12:24:57 192.168.122.209 [73247.871450] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:24:57 192.168.122.209 [73248.296555] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:24:57 192.168.122.209 [73248.323952] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:24:57 192.168.122.209 [73248.349001] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:24:57 192.168.122.209 [73248.430544] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:24:57 192.168.122.209 [73248.432296] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:24:57 192.168.122.209 [73248.478512] [tempesta fw] Tempesta FW is ready Apr 26 12:24:58 192.168.122.209 [73249.107700] [tdb] Close table 'client0.tdb' Apr 26 12:24:58 192.168.122.209 [73249.303637] [tdb] Close table 'sessions0.tdb' Apr 26 12:25:01 192.168.122.209 [73252.484526] [tdb] Close table 'cache0.tdb' Apr 26 12:25:01 192.168.122.209 [73252.722317] [tdb] Close table 'filter0.tdb' Apr 26 12:25:01 192.168.122.209 [73252.722773] [tempesta fw] modules are stopped Apr 26 12:25:02 192.168.122.209 [73252.949602] [tempesta fw] exiting... Apr 26 12:25:02 192.168.122.209 [73253.080066] [tdb] Shutdown Tempesta DB Apr 26 12:25:02 192.168.122.209 [73253.500527] End test: cache.test_conditional.TestConditionalH2.test_response_without_last_modified_nc Apr 26 12:25:02 192.168.122.209 [73253.589618] Start test: cache.test_conditional.TestConditionalHttp.test_correct_none_match_and_modified_since Apr 26 12:25:04 192.168.122.209 [73254.927072] [tdb] Start Tempesta DB Apr 26 12:25:04 192.168.122.209 [73255.066819] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:25:05 192.168.122.209 [73256.515950] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73256.515950] Maybe that's fine, but it's worth checking the [73256.515950] config - if there is no relations between the [73256.515950] names, then host name confusion attack is possible. Apr 26 12:25:05 192.168.122.209 [73256.646690] [tempesta fw] Configuration processing is completed. Apr 26 12:25:05 192.168.122.209 [73256.704618] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:25:06 192.168.122.209 [73257.117599] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:25:06 192.168.122.209 [73257.144251] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:25:06 192.168.122.209 [73257.171569] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:25:06 192.168.122.209 [73257.214698] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:25:06 192.168.122.209 [73257.216451] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:25:06 192.168.122.209 [73257.258630] [tempesta fw] Tempesta FW is ready Apr 26 12:25:07 192.168.122.209 [73257.879484] [tdb] Close table 'client0.tdb' Apr 26 12:25:07 192.168.122.209 [73258.064707] [tdb] Close table 'sessions0.tdb' Apr 26 12:25:10 192.168.122.209 [73261.208931] [tdb] Close table 'cache0.tdb' Apr 26 12:25:10 192.168.122.209 [73261.459904] [tdb] Close table 'filter0.tdb' Apr 26 12:25:10 192.168.122.209 [73261.460353] [tempesta fw] modules are stopped Apr 26 12:25:10 192.168.122.209 [73261.647843] [tempesta fw] exiting... Apr 26 12:25:11 192.168.122.209 [73261.764766] [tdb] Shutdown Tempesta DB Apr 26 12:25:11 192.168.122.209 [73262.197465] End test: cache.test_conditional.TestConditionalHttp.test_correct_none_match_and_modified_since Apr 26 12:25:11 192.168.122.209 [73262.238282] Start test: cache.test_conditional.TestConditionalHttp.test_incorrect_none_match_and_correct_modified_since Apr 26 12:25:12 192.168.122.209 [73263.688781] [tdb] Start Tempesta DB Apr 26 12:25:13 192.168.122.209 [73263.818137] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:25:14 192.168.122.209 [73265.196009] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73265.196009] Maybe that's fine, but it's worth checking the [73265.196009] config - if there is no relations between the [73265.196009] names, then host name confusion attack is possible. Apr 26 12:25:14 192.168.122.209 [73265.334794] [tempesta fw] Configuration processing is completed. Apr 26 12:25:14 192.168.122.209 [73265.391369] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:25:15 192.168.122.209 [73265.821746] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:25:15 192.168.122.209 [73265.847178] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:25:15 192.168.122.209 [73265.872181] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:25:15 192.168.122.209 [73265.906711] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:25:15 192.168.122.209 [73265.908454] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:25:15 192.168.122.209 [73265.946710] [tempesta fw] Tempesta FW is ready Apr 26 12:25:15 192.168.122.209 [73266.599543] [tdb] Close table 'client0.tdb' Apr 26 12:25:16 192.168.122.209 [73266.784857] [tdb] Close table 'sessions0.tdb' Apr 26 12:25:19 192.168.122.209 [73269.965766] [tdb] Close table 'cache0.tdb' Apr 26 12:25:19 192.168.122.209 [73270.215215] [tdb] Close table 'filter0.tdb' Apr 26 12:25:19 192.168.122.209 [73270.215669] [tempesta fw] modules are stopped Apr 26 12:25:19 192.168.122.209 [73270.414540] [tempesta fw] exiting... Apr 26 12:25:19 192.168.122.209 [73270.542770] [tdb] Shutdown Tempesta DB Apr 26 12:25:20 192.168.122.209 [73270.897551] End test: cache.test_conditional.TestConditionalHttp.test_incorrect_none_match_and_correct_modified_since Apr 26 12:25:20 192.168.122.209 [73270.931913] Start test: cache.test_conditional.TestConditionalHttp.test_mod_since Apr 26 12:25:21 192.168.122.209 [73272.381603] [tdb] Start Tempesta DB Apr 26 12:25:21 192.168.122.209 [73272.499892] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:25:23 192.168.122.209 [73273.892152] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73273.892152] Maybe that's fine, but it's worth checking the [73273.892152] config - if there is no relations between the [73273.892152] names, then host name confusion attack is possible. Apr 26 12:25:23 192.168.122.209 [73274.038905] [tempesta fw] Configuration processing is completed. Apr 26 12:25:23 192.168.122.209 [73274.103762] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:25:23 192.168.122.209 [73274.522892] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:25:23 192.168.122.209 [73274.548937] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:25:23 192.168.122.209 [73274.574877] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:25:23 192.168.122.209 [73274.642889] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:25:23 192.168.122.209 [73274.644735] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:25:23 192.168.122.209 [73274.690829] [tempesta fw] Tempesta FW is ready Apr 26 12:25:24 192.168.122.209 [73275.389264] [tdb] Close table 'client0.tdb' Apr 26 12:25:24 192.168.122.209 [73275.562158] [tdb] Close table 'sessions0.tdb' Apr 26 12:25:28 192.168.122.209 [73278.754391] [tdb] Close table 'cache0.tdb' Apr 26 12:25:28 192.168.122.209 [73278.990008] [tdb] Close table 'filter0.tdb' Apr 26 12:25:28 192.168.122.209 [73278.990439] [tempesta fw] modules are stopped Apr 26 12:25:28 192.168.122.209 [73279.199472] [tempesta fw] exiting... Apr 26 12:25:28 192.168.122.209 [73279.363892] [tdb] Shutdown Tempesta DB Apr 26 12:25:29 192.168.122.209 [73279.739858] End test: cache.test_conditional.TestConditionalHttp.test_mod_since Apr 26 12:25:29 192.168.122.209 [73279.780092] Start test: cache.test_conditional.TestConditionalHttp.test_mod_since_nc Apr 26 12:25:30 192.168.122.209 [73281.225810] [tdb] Start Tempesta DB Apr 26 12:25:30 192.168.122.209 [73281.361292] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:25:32 192.168.122.209 [73282.772309] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73282.772309] Maybe that's fine, but it's worth checking the [73282.772309] config - if there is no relations between the [73282.772309] names, then host name confusion attack is possible. Apr 26 12:25:32 192.168.122.209 [73282.902983] [tempesta fw] Configuration processing is completed. Apr 26 12:25:32 192.168.122.209 [73282.959537] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:25:32 192.168.122.209 [73283.381994] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:25:32 192.168.122.209 [73283.417663] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:25:32 192.168.122.209 [73283.443602] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:25:32 192.168.122.209 [73283.490985] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:25:32 192.168.122.209 [73283.492747] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:25:32 192.168.122.209 [73283.530933] [tempesta fw] Tempesta FW is ready Apr 26 12:25:33 192.168.122.209 [73284.158067] [tdb] Close table 'client0.tdb' Apr 26 12:25:33 192.168.122.209 [73284.331991] [tdb] Close table 'sessions0.tdb' Apr 26 12:25:36 192.168.122.209 [73287.493266] [tdb] Close table 'cache0.tdb' Apr 26 12:25:37 192.168.122.209 [73287.746597] [tdb] Close table 'filter0.tdb' Apr 26 12:25:37 192.168.122.209 [73287.747025] [tempesta fw] modules are stopped Apr 26 12:25:37 192.168.122.209 [73287.931127] [tempesta fw] exiting... Apr 26 12:25:37 192.168.122.209 [73288.071587] [tdb] Shutdown Tempesta DB Apr 26 12:25:37 192.168.122.209 [73288.451301] End test: cache.test_conditional.TestConditionalHttp.test_mod_since_nc Apr 26 12:25:37 192.168.122.209 [73288.481669] Start test: cache.test_conditional.TestConditionalHttp.test_mod_since_nc_with_invalid_date Apr 26 12:25:39 192.168.122.209 [73289.914244] [tdb] Start Tempesta DB Apr 26 12:25:39 192.168.122.209 [73290.051341] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:25:40 192.168.122.209 [73291.504367] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73291.504367] Maybe that's fine, but it's worth checking the [73291.504367] config - if there is no relations between the [73291.504367] names, then host name confusion attack is possible. Apr 26 12:25:40 192.168.122.209 [73291.639122] [tempesta fw] Configuration processing is completed. Apr 26 12:25:40 192.168.122.209 [73291.694312] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:25:41 192.168.122.209 [73292.109452] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:25:41 192.168.122.209 [73292.135518] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:25:41 192.168.122.209 [73292.161183] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:25:41 192.168.122.209 [73292.203095] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:25:41 192.168.122.209 [73292.205170] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:25:41 192.168.122.209 [73292.243058] [tempesta fw] Tempesta FW is ready Apr 26 12:25:42 192.168.122.209 [73292.845291] [tdb] Close table 'client0.tdb' Apr 26 12:25:42 192.168.122.209 [73293.044693] [tdb] Close table 'sessions0.tdb' Apr 26 12:25:45 192.168.122.209 [73296.233591] [tdb] Close table 'cache0.tdb' Apr 26 12:25:45 192.168.122.209 [73296.467786] [tdb] Close table 'filter0.tdb' Apr 26 12:25:45 192.168.122.209 [73296.468215] [tempesta fw] modules are stopped Apr 26 12:25:45 192.168.122.209 [73296.715884] [tempesta fw] exiting... Apr 26 12:25:46 192.168.122.209 [73296.840310] [tdb] Shutdown Tempesta DB Apr 26 12:25:46 192.168.122.209 [73297.227864] End test: cache.test_conditional.TestConditionalHttp.test_mod_since_nc_with_invalid_date Apr 26 12:25:46 192.168.122.209 [73297.251547] Start test: cache.test_conditional.TestConditionalHttp.test_none_match Apr 26 12:25:47 192.168.122.209 [73298.671939] [tdb] Start Tempesta DB Apr 26 12:25:48 192.168.122.209 [73298.798417] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:25:49 192.168.122.209 [73300.240450] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73300.240450] Maybe that's fine, but it's worth checking the [73300.240450] config - if there is no relations between the [73300.240450] names, then host name confusion attack is possible. Apr 26 12:25:49 192.168.122.209 [73300.383211] [tempesta fw] Configuration processing is completed. Apr 26 12:25:49 192.168.122.209 [73300.435608] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:25:50 192.168.122.209 [73300.875351] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:25:50 192.168.122.209 [73300.903667] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:25:50 192.168.122.209 [73300.932976] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:25:50 192.168.122.209 [73300.991124] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:25:50 192.168.122.209 [73300.992837] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:25:50 192.168.122.209 [73301.031178] [tempesta fw] Tempesta FW is ready Apr 26 12:25:50 192.168.122.209 [73301.718210] [tdb] Close table 'client0.tdb' Apr 26 12:25:51 192.168.122.209 [73301.899825] [tdb] Close table 'sessions0.tdb' Apr 26 12:25:54 192.168.122.209 [73305.122587] [tdb] Close table 'cache0.tdb' Apr 26 12:25:54 192.168.122.209 [73305.367830] [tdb] Close table 'filter0.tdb' Apr 26 12:25:54 192.168.122.209 [73305.368258] [tempesta fw] modules are stopped Apr 26 12:25:54 192.168.122.209 [73305.564476] [tempesta fw] exiting... Apr 26 12:25:54 192.168.122.209 [73305.680064] [tdb] Shutdown Tempesta DB Apr 26 12:25:55 192.168.122.209 [73306.038807] End test: cache.test_conditional.TestConditionalHttp.test_none_match Apr 26 12:25:55 192.168.122.209 [73306.063476] Start test: cache.test_conditional.TestConditionalHttp.test_none_match_HEAD Apr 26 12:25:56 192.168.122.209 [73307.471560] [tdb] Start Tempesta DB Apr 26 12:25:56 192.168.122.209 [73307.637392] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:25:58 192.168.122.209 [73309.053035] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73309.053035] Maybe that's fine, but it's worth checking the [73309.053035] config - if there is no relations between the [73309.053035] names, then host name confusion attack is possible. Apr 26 12:25:58 192.168.122.209 [73309.187314] [tempesta fw] Configuration processing is completed. Apr 26 12:25:58 192.168.122.209 [73309.244160] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:25:58 192.168.122.209 [73309.724806] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:25:59 192.168.122.209 [73309.753653] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:25:59 192.168.122.209 [73309.782745] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:25:59 192.168.122.209 [73309.835747] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:25:59 192.168.122.209 [73309.837535] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:25:59 192.168.122.209 [73309.875304] [tempesta fw] Tempesta FW is ready Apr 26 12:25:59 192.168.122.209 [73310.512622] [tdb] Close table 'client0.tdb' Apr 26 12:25:59 192.168.122.209 [73310.718232] [tdb] Close table 'sessions0.tdb' Apr 26 12:26:03 192.168.122.209 [73313.925596] [tdb] Close table 'cache0.tdb' Apr 26 12:26:03 192.168.122.209 [73314.189203] [tdb] Close table 'filter0.tdb' Apr 26 12:26:03 192.168.122.209 [73314.189627] [tempesta fw] modules are stopped Apr 26 12:26:03 192.168.122.209 [73314.365984] [tempesta fw] exiting... Apr 26 12:26:03 192.168.122.209 [73314.473512] [tdb] Shutdown Tempesta DB Apr 26 12:26:04 192.168.122.209 [73314.891107] End test: cache.test_conditional.TestConditionalHttp.test_none_match_HEAD Apr 26 12:26:04 192.168.122.209 [73314.923277] Start test: cache.test_conditional.TestConditionalHttp.test_none_match_any Apr 26 12:26:05 192.168.122.209 [73316.331878] [tdb] Start Tempesta DB Apr 26 12:26:05 192.168.122.209 [73316.476102] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:26:07 192.168.122.209 [73317.896692] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73317.896692] Maybe that's fine, but it's worth checking the [73317.896692] config - if there is no relations between the [73317.896692] names, then host name confusion attack is possible. Apr 26 12:26:07 192.168.122.209 [73318.039427] [tempesta fw] Configuration processing is completed. Apr 26 12:26:07 192.168.122.209 [73318.093278] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:26:07 192.168.122.209 [73318.564379] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:26:07 192.168.122.209 [73318.593790] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:26:07 192.168.122.209 [73318.623878] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:26:07 192.168.122.209 [73318.667451] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:26:07 192.168.122.209 [73318.669165] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:26:07 192.168.122.209 [73318.715379] [tempesta fw] Tempesta FW is ready Apr 26 12:26:08 192.168.122.209 [73319.379713] [tdb] Close table 'client0.tdb' Apr 26 12:26:08 192.168.122.209 [73319.563394] [tdb] Close table 'sessions0.tdb' Apr 26 12:26:12 192.168.122.209 [73322.809385] [tdb] Close table 'cache0.tdb' Apr 26 12:26:12 192.168.122.209 [73323.070309] [tdb] Close table 'filter0.tdb' Apr 26 12:26:12 192.168.122.209 [73323.070732] [tempesta fw] modules are stopped Apr 26 12:26:12 192.168.122.209 [73323.280810] [tempesta fw] exiting... Apr 26 12:26:12 192.168.122.209 [73323.415895] [tdb] Shutdown Tempesta DB Apr 26 12:26:13 192.168.122.209 [73323.834268] End test: cache.test_conditional.TestConditionalHttp.test_none_match_any Apr 26 12:26:13 192.168.122.209 [73323.864605] Start test: cache.test_conditional.TestConditionalHttp.test_none_match_empty_etag Apr 26 12:26:14 192.168.122.209 [73325.341428] [tdb] Start Tempesta DB Apr 26 12:26:14 192.168.122.209 [73325.507330] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:26:16 192.168.122.209 [73326.956022] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73326.956022] Maybe that's fine, but it's worth checking the [73326.956022] config - if there is no relations between the [73326.956022] names, then host name confusion attack is possible. Apr 26 12:26:16 192.168.122.209 [73327.095546] [tempesta fw] Configuration processing is completed. Apr 26 12:26:16 192.168.122.209 [73327.146313] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:26:16 192.168.122.209 [73327.591302] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:26:16 192.168.122.209 [73327.619558] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:26:16 192.168.122.209 [73327.646711] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:26:16 192.168.122.209 [73327.703625] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:26:16 192.168.122.209 [73327.705389] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:26:17 192.168.122.209 [73327.743498] [tempesta fw] Tempesta FW is ready Apr 26 12:26:17 192.168.122.209 [73328.433123] [tdb] Close table 'client0.tdb' Apr 26 12:26:17 192.168.122.209 [73328.624889] [tdb] Close table 'sessions0.tdb' Apr 26 12:26:21 192.168.122.209 [73331.759676] [tdb] Close table 'cache0.tdb' Apr 26 12:26:21 192.168.122.209 [73332.011904] [tdb] Close table 'filter0.tdb' Apr 26 12:26:21 192.168.122.209 [73332.012549] [tempesta fw] modules are stopped Apr 26 12:26:21 192.168.122.209 [73332.201717] [tempesta fw] exiting... Apr 26 12:26:21 192.168.122.209 [73332.334811] [tdb] Shutdown Tempesta DB Apr 26 12:26:22 192.168.122.209 [73332.772579] End test: cache.test_conditional.TestConditionalHttp.test_none_match_empty_etag Apr 26 12:26:22 192.168.122.209 [73332.812167] Start test: cache.test_conditional.TestConditionalHttp.test_none_match_list Apr 26 12:26:23 192.168.122.209 [73334.275501] [tdb] Start Tempesta DB Apr 26 12:26:23 192.168.122.209 [73334.409227] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:26:25 192.168.122.209 [73335.780920] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73335.780920] Maybe that's fine, but it's worth checking the [73335.780920] config - if there is no relations between the [73335.780920] names, then host name confusion attack is possible. Apr 26 12:26:25 192.168.122.209 [73335.943651] [tempesta fw] Configuration processing is completed. Apr 26 12:26:25 192.168.122.209 [73336.003299] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:26:25 192.168.122.209 [73336.525743] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:26:25 192.168.122.209 [73336.559214] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:26:25 192.168.122.209 [73336.592792] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:26:25 192.168.122.209 [73336.635664] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:26:25 192.168.122.209 [73336.637394] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:26:25 192.168.122.209 [73336.675599] [tempesta fw] Tempesta FW is ready Apr 26 12:26:26 192.168.122.209 [73337.323134] [tdb] Close table 'client0.tdb' Apr 26 12:26:26 192.168.122.209 [73337.514139] [tdb] Close table 'sessions0.tdb' Apr 26 12:26:30 192.168.122.209 [73340.737902] [tdb] Close table 'cache0.tdb' Apr 26 12:26:30 192.168.122.209 [73340.985924] [tdb] Close table 'filter0.tdb' Apr 26 12:26:30 192.168.122.209 [73340.986384] [tempesta fw] modules are stopped Apr 26 12:26:30 192.168.122.209 [73341.155731] [tempesta fw] exiting... Apr 26 12:26:30 192.168.122.209 [73341.288971] [tdb] Shutdown Tempesta DB Apr 26 12:26:30 192.168.122.209 [73341.652469] End test: cache.test_conditional.TestConditionalHttp.test_none_match_list Apr 26 12:26:30 192.168.122.209 [73341.677948] Start test: cache.test_conditional.TestConditionalHttp.test_none_match_nc_GET Apr 26 12:26:32 192.168.122.209 [73342.999069] [tdb] Start Tempesta DB Apr 26 12:26:32 192.168.122.209 [73343.140324] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:26:33 192.168.122.209 [73344.589033] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73344.589033] Maybe that's fine, but it's worth checking the [73344.589033] config - if there is no relations between the [73344.589033] names, then host name confusion attack is possible. Apr 26 12:26:34 192.168.122.209 [73344.731774] [tempesta fw] Configuration processing is completed. Apr 26 12:26:34 192.168.122.209 [73344.783794] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:26:34 192.168.122.209 [73345.206482] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:26:34 192.168.122.209 [73345.233734] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:26:34 192.168.122.209 [73345.260464] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:26:34 192.168.122.209 [73345.351759] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:26:34 192.168.122.209 [73345.353572] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:26:34 192.168.122.209 [73345.391727] [tempesta fw] Tempesta FW is ready Apr 26 12:26:35 192.168.122.209 [73346.031021] [tdb] Close table 'client0.tdb' Apr 26 12:26:35 192.168.122.209 [73346.221058] [tdb] Close table 'sessions0.tdb' Apr 26 12:26:38 192.168.122.209 [73349.382139] [tdb] Close table 'cache0.tdb' Apr 26 12:26:38 192.168.122.209 [73349.623246] [tdb] Close table 'filter0.tdb' Apr 26 12:26:38 192.168.122.209 [73349.623673] [tempesta fw] modules are stopped Apr 26 12:26:39 192.168.122.209 [73349.825364] [tempesta fw] exiting... Apr 26 12:26:39 192.168.122.209 [73349.957866] [tdb] Shutdown Tempesta DB Apr 26 12:26:39 192.168.122.209 [73350.331810] End test: cache.test_conditional.TestConditionalHttp.test_none_match_nc_GET Apr 26 12:26:39 192.168.122.209 [73350.367054] Start test: cache.test_conditional.TestConditionalHttp.test_none_match_nc_HEAD Apr 26 12:26:41 192.168.122.209 [73351.767454] [tdb] Start Tempesta DB Apr 26 12:26:41 192.168.122.209 [73351.906831] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:26:42 192.168.122.209 [73353.393156] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73353.393156] Maybe that's fine, but it's worth checking the [73353.393156] config - if there is no relations between the [73353.393156] names, then host name confusion attack is possible. Apr 26 12:26:42 192.168.122.209 [73353.535889] [tempesta fw] Configuration processing is completed. Apr 26 12:26:42 192.168.122.209 [73353.596466] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:26:43 192.168.122.209 [73353.996242] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:26:43 192.168.122.209 [73354.021750] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:26:43 192.168.122.209 [73354.054877] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:26:43 192.168.122.209 [73354.107894] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:26:43 192.168.122.209 [73354.109624] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:26:43 192.168.122.209 [73354.147839] [tempesta fw] Tempesta FW is ready Apr 26 12:26:44 192.168.122.209 [73354.782548] [tdb] Close table 'client0.tdb' Apr 26 12:26:44 192.168.122.209 [73354.966126] [tdb] Close table 'sessions0.tdb' Apr 26 12:26:47 192.168.122.209 [73358.130098] [tdb] Close table 'cache0.tdb' Apr 26 12:26:47 192.168.122.209 [73358.364476] [tdb] Close table 'filter0.tdb' Apr 26 12:26:47 192.168.122.209 [73358.364893] [tempesta fw] modules are stopped Apr 26 12:26:47 192.168.122.209 [73358.550816] [tempesta fw] exiting... Apr 26 12:26:47 192.168.122.209 [73358.678424] [tdb] Shutdown Tempesta DB Apr 26 12:26:48 192.168.122.209 [73359.074814] End test: cache.test_conditional.TestConditionalHttp.test_none_match_nc_HEAD Apr 26 12:26:48 192.168.122.209 [73359.104116] Start test: cache.test_conditional.TestConditionalHttp.test_none_match_no_quotes_empty_etag Apr 26 12:26:49 192.168.122.209 [73360.485903] [tdb] Start Tempesta DB Apr 26 12:26:49 192.168.122.209 [73360.609864] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:26:51 192.168.122.209 [73362.045368] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73362.045368] Maybe that's fine, but it's worth checking the [73362.045368] config - if there is no relations between the [73362.045368] names, then host name confusion attack is possible. Apr 26 12:26:51 192.168.122.209 [73362.183973] [tempesta fw] Configuration processing is completed. Apr 26 12:26:51 192.168.122.209 [73362.246469] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:26:51 192.168.122.209 [73362.659228] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:26:51 192.168.122.209 [73362.686201] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:26:51 192.168.122.209 [73362.711902] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:26:52 192.168.122.209 [73362.752013] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:26:52 192.168.122.209 [73362.753736] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:26:52 192.168.122.209 [73362.795927] [tempesta fw] Tempesta FW is ready Apr 26 12:26:52 192.168.122.209 [73363.390932] [tdb] Close table 'client0.tdb' Apr 26 12:26:52 192.168.122.209 [73363.583899] [tdb] Close table 'sessions0.tdb' Apr 26 12:26:56 192.168.122.209 [73366.748178] [tdb] Close table 'cache0.tdb' Apr 26 12:26:56 192.168.122.209 [73366.990334] [tdb] Close table 'filter0.tdb' Apr 26 12:26:56 192.168.122.209 [73366.990750] [tempesta fw] modules are stopped Apr 26 12:26:56 192.168.122.209 [73367.167640] [tempesta fw] exiting... Apr 26 12:26:56 192.168.122.209 [73367.333754] [tdb] Shutdown Tempesta DB Apr 26 12:26:56 192.168.122.209 [73367.725295] End test: cache.test_conditional.TestConditionalHttp.test_none_match_no_quotes_empty_etag Apr 26 12:26:57 192.168.122.209 [73367.811638] Start test: cache.test_conditional.TestConditionalHttp.test_none_match_no_quotes_empty_etag_with_extra_spaces Apr 26 12:26:58 192.168.122.209 [73369.176228] [tdb] Start Tempesta DB Apr 26 12:26:58 192.168.122.209 [73369.318406] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:26:59 192.168.122.209 [73370.713382] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73370.713382] Maybe that's fine, but it's worth checking the [73370.713382] config - if there is no relations between the [73370.713382] names, then host name confusion attack is possible. Apr 26 12:27:00 192.168.122.209 [73370.856106] [tempesta fw] Configuration processing is completed. Apr 26 12:27:00 192.168.122.209 [73370.913390] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:27:00 192.168.122.209 [73371.351799] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:27:00 192.168.122.209 [73371.387460] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:27:00 192.168.122.209 [73371.413975] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:27:00 192.168.122.209 [73371.472097] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:27:00 192.168.122.209 [73371.473836] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:27:00 192.168.122.209 [73371.520051] [tempesta fw] Tempesta FW is ready Apr 26 12:27:01 192.168.122.209 [73372.197013] [tdb] Close table 'client0.tdb' Apr 26 12:27:01 192.168.122.209 [73372.383781] [tdb] Close table 'sessions0.tdb' Apr 26 12:27:04 192.168.122.209 [73375.588086] [tdb] Close table 'cache0.tdb' Apr 26 12:27:05 192.168.122.209 [73375.816925] [tdb] Close table 'filter0.tdb' Apr 26 12:27:05 192.168.122.209 [73375.817350] [tempesta fw] modules are stopped Apr 26 12:27:05 192.168.122.209 [73376.021500] [tempesta fw] exiting... Apr 26 12:27:05 192.168.122.209 [73376.138914] [tdb] Shutdown Tempesta DB Apr 26 12:27:05 192.168.122.209 [73376.525287] End test: cache.test_conditional.TestConditionalHttp.test_none_match_no_quotes_empty_etag_with_extra_spaces Apr 26 12:27:05 192.168.122.209 [73376.558192] Start test: cache.test_conditional.TestConditionalHttp.test_none_match_no_quotes_etag Apr 26 12:27:07 192.168.122.209 [73377.998402] [tdb] Start Tempesta DB Apr 26 12:27:07 192.168.122.209 [73378.140482] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:27:08 192.168.122.209 [73379.581486] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73379.581486] Maybe that's fine, but it's worth checking the [73379.581486] config - if there is no relations between the [73379.581486] names, then host name confusion attack is possible. Apr 26 12:27:08 192.168.122.209 [73379.720247] [tempesta fw] Configuration processing is completed. Apr 26 12:27:09 192.168.122.209 [73379.776216] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:27:09 192.168.122.209 [73380.190429] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:27:09 192.168.122.209 [73380.217220] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:27:09 192.168.122.209 [73380.245360] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:27:09 192.168.122.209 [73380.284125] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:27:09 192.168.122.209 [73380.285434] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:27:09 192.168.122.209 [73380.328166] [tempesta fw] Tempesta FW is ready Apr 26 12:27:10 192.168.122.209 [73381.003502] [tdb] Close table 'client0.tdb' Apr 26 12:27:10 192.168.122.209 [73381.182928] [tdb] Close table 'sessions0.tdb' Apr 26 12:27:13 192.168.122.209 [73384.363118] [tdb] Close table 'cache0.tdb' Apr 26 12:27:13 192.168.122.209 [73384.608555] [tdb] Close table 'filter0.tdb' Apr 26 12:27:13 192.168.122.209 [73384.608980] [tempesta fw] modules are stopped Apr 26 12:27:14 192.168.122.209 [73384.796748] [tempesta fw] exiting... Apr 26 12:27:14 192.168.122.209 [73384.940616] [tdb] Shutdown Tempesta DB Apr 26 12:27:14 192.168.122.209 [73385.364958] End test: cache.test_conditional.TestConditionalHttp.test_none_match_no_quotes_etag Apr 26 12:27:14 192.168.122.209 [73385.399832] Start test: cache.test_conditional.TestConditionalHttp.test_none_match_no_quotes_etag_with_extra_spaces Apr 26 12:27:16 192.168.122.209 [73386.824745] [tdb] Start Tempesta DB Apr 26 12:27:16 192.168.122.209 [73386.978122] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:27:17 192.168.122.209 [73388.393609] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73388.393609] Maybe that's fine, but it's worth checking the [73388.393609] config - if there is no relations between the [73388.393609] names, then host name confusion attack is possible. Apr 26 12:27:17 192.168.122.209 [73388.536358] [tempesta fw] Configuration processing is completed. Apr 26 12:27:17 192.168.122.209 [73388.596949] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:27:18 192.168.122.209 [73389.057932] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:27:18 192.168.122.209 [73389.087501] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:27:18 192.168.122.209 [73389.121581] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:27:18 192.168.122.209 [73389.168330] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:27:18 192.168.122.209 [73389.170075] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:27:18 192.168.122.209 [73389.220254] [tempesta fw] Tempesta FW is ready Apr 26 12:27:19 192.168.122.209 [73389.902386] [tdb] Close table 'client0.tdb' Apr 26 12:27:19 192.168.122.209 [73390.084585] [tdb] Close table 'sessions0.tdb' Apr 26 12:27:22 192.168.122.209 [73393.215600] [tdb] Close table 'cache0.tdb' Apr 26 12:27:22 192.168.122.209 [73393.468871] [tdb] Close table 'filter0.tdb' Apr 26 12:27:22 192.168.122.209 [73393.469310] [tempesta fw] modules are stopped Apr 26 12:27:22 192.168.122.209 [73393.662298] [tempesta fw] exiting... Apr 26 12:27:23 192.168.122.209 [73393.808017] [tdb] Shutdown Tempesta DB Apr 26 12:27:23 192.168.122.209 [73394.193999] End test: cache.test_conditional.TestConditionalHttp.test_none_match_no_quotes_etag_with_extra_spaces Apr 26 12:27:23 192.168.122.209 [73394.277395] Start test: cache.test_conditional.TestConditionalHttp.test_none_match_weak_all Apr 26 12:27:24 192.168.122.209 [73395.687495] [tdb] Start Tempesta DB Apr 26 12:27:25 192.168.122.209 [73395.810507] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:27:26 192.168.122.209 [73397.237855] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73397.237855] Maybe that's fine, but it's worth checking the [73397.237855] config - if there is no relations between the [73397.237855] names, then host name confusion attack is possible. Apr 26 12:27:26 192.168.122.209 [73397.396523] [tempesta fw] Configuration processing is completed. Apr 26 12:27:26 192.168.122.209 [73397.456996] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:27:27 192.168.122.209 [73397.890379] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:27:27 192.168.122.209 [73397.917095] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:27:27 192.168.122.209 [73397.949179] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:27:27 192.168.122.209 [73397.988421] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:27:27 192.168.122.209 [73397.990176] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:27:27 192.168.122.209 [73398.028370] [tempesta fw] Tempesta FW is ready Apr 26 12:27:27 192.168.122.209 [73398.625983] [tdb] Close table 'client0.tdb' Apr 26 12:27:28 192.168.122.209 [73398.832598] [tdb] Close table 'sessions0.tdb' Apr 26 12:27:31 192.168.122.209 [73401.978943] [tdb] Close table 'cache0.tdb' Apr 26 12:27:31 192.168.122.209 [73402.215126] [tdb] Close table 'filter0.tdb' Apr 26 12:27:31 192.168.122.209 [73402.215550] [tempesta fw] modules are stopped Apr 26 12:27:31 192.168.122.209 [73402.449587] [tempesta fw] exiting... Apr 26 12:27:31 192.168.122.209 [73402.561804] [tdb] Shutdown Tempesta DB Apr 26 12:27:32 192.168.122.209 [73402.930422] End test: cache.test_conditional.TestConditionalHttp.test_none_match_weak_all Apr 26 12:27:32 192.168.122.209 [73402.966928] Start test: cache.test_conditional.TestConditionalHttp.test_none_match_weak_clnt Apr 26 12:27:33 192.168.122.209 [73404.408854] [tdb] Start Tempesta DB Apr 26 12:27:33 192.168.122.209 [73404.540558] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:27:35 192.168.122.209 [73405.965817] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73405.965817] Maybe that's fine, but it's worth checking the [73405.965817] config - if there is no relations between the [73405.965817] names, then host name confusion attack is possible. Apr 26 12:27:35 192.168.122.209 [73406.096572] [tempesta fw] Configuration processing is completed. Apr 26 12:27:35 192.168.122.209 [73406.155602] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:27:35 192.168.122.209 [73406.584639] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:27:35 192.168.122.209 [73406.611446] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:27:35 192.168.122.209 [73406.637727] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:27:35 192.168.122.209 [73406.676548] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:27:35 192.168.122.209 [73406.678295] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:27:35 192.168.122.209 [73406.716490] [tempesta fw] Tempesta FW is ready Apr 26 12:27:36 192.168.122.209 [73407.378959] [tdb] Close table 'client0.tdb' Apr 26 12:27:36 192.168.122.209 [73407.563649] [tdb] Close table 'sessions0.tdb' Apr 26 12:27:40 192.168.122.209 [73410.787765] [tdb] Close table 'cache0.tdb' Apr 26 12:27:40 192.168.122.209 [73411.023951] [tdb] Close table 'filter0.tdb' Apr 26 12:27:40 192.168.122.209 [73411.024423] [tempesta fw] modules are stopped Apr 26 12:27:40 192.168.122.209 [73411.218086] [tempesta fw] exiting... Apr 26 12:27:40 192.168.122.209 [73411.316717] [tdb] Shutdown Tempesta DB Apr 26 12:27:40 192.168.122.209 [73411.690669] End test: cache.test_conditional.TestConditionalHttp.test_none_match_weak_clnt Apr 26 12:27:40 192.168.122.209 [73411.723351] Start test: cache.test_conditional.TestConditionalHttp.test_none_match_weak_srv Apr 26 12:27:42 192.168.122.209 [73413.167314] [tdb] Start Tempesta DB Apr 26 12:27:42 192.168.122.209 [73413.296645] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:27:44 192.168.122.209 [73414.741332] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73414.741332] Maybe that's fine, but it's worth checking the [73414.741332] config - if there is no relations between the [73414.741332] names, then host name confusion attack is possible. Apr 26 12:27:44 192.168.122.209 [73414.872669] [tempesta fw] Configuration processing is completed. Apr 26 12:27:44 192.168.122.209 [73414.927721] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:27:44 192.168.122.209 [73415.343864] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:27:44 192.168.122.209 [73415.370554] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:27:44 192.168.122.209 [73415.396136] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:27:44 192.168.122.209 [73415.436662] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:27:44 192.168.122.209 [73415.438374] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:27:44 192.168.122.209 [73415.480591] [tempesta fw] Tempesta FW is ready Apr 26 12:27:45 192.168.122.209 [73416.129700] [tdb] Close table 'client0.tdb' Apr 26 12:27:45 192.168.122.209 [73416.307932] [tdb] Close table 'sessions0.tdb' Apr 26 12:27:48 192.168.122.209 [73419.498577] [tdb] Close table 'cache0.tdb' Apr 26 12:27:49 192.168.122.209 [73419.750633] [tdb] Close table 'filter0.tdb' Apr 26 12:27:49 192.168.122.209 [73419.751060] [tempesta fw] modules are stopped Apr 26 12:27:49 192.168.122.209 [73419.939756] [tempesta fw] exiting... Apr 26 12:27:49 192.168.122.209 [73420.046200] [tdb] Shutdown Tempesta DB Apr 26 12:27:49 192.168.122.209 [73420.477791] End test: cache.test_conditional.TestConditionalHttp.test_none_match_weak_srv Apr 26 12:27:49 192.168.122.209 [73420.505981] Start test: cache.test_conditional.TestConditionalHttp.test_response_without_last_modified Apr 26 12:27:51 192.168.122.209 [73421.875174] [tdb] Start Tempesta DB Apr 26 12:27:51 192.168.122.209 [73422.008028] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:27:52 192.168.122.209 [73423.458216] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73423.458216] Maybe that's fine, but it's worth checking the [73423.458216] config - if there is no relations between the [73423.458216] names, then host name confusion attack is possible. Apr 26 12:27:52 192.168.122.209 [73423.604800] [tempesta fw] Configuration processing is completed. Apr 26 12:27:52 192.168.122.209 [73423.662142] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:27:53 192.168.122.209 [73424.084520] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:27:53 192.168.122.209 [73424.129881] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:27:53 192.168.122.209 [73424.163450] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:27:53 192.168.122.209 [73424.216795] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:27:53 192.168.122.209 [73424.218542] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:27:53 192.168.122.209 [73424.256725] [tempesta fw] Tempesta FW is ready Apr 26 12:27:54 192.168.122.209 [73424.918650] [tdb] Close table 'client0.tdb' Apr 26 12:27:54 192.168.122.209 [73425.121623] [tdb] Close table 'sessions0.tdb' Apr 26 12:27:57 192.168.122.209 [73428.271774] [tdb] Close table 'cache0.tdb' Apr 26 12:27:57 192.168.122.209 [73428.544642] [tdb] Close table 'filter0.tdb' Apr 26 12:27:57 192.168.122.209 [73428.545255] [tempesta fw] modules are stopped Apr 26 12:27:58 192.168.122.209 [73428.737877] [tempesta fw] exiting... Apr 26 12:27:58 192.168.122.209 [73428.894184] [tdb] Shutdown Tempesta DB Apr 26 12:27:58 192.168.122.209 [73429.298487] End test: cache.test_conditional.TestConditionalHttp.test_response_without_last_modified Apr 26 12:27:58 192.168.122.209 [73429.322081] Start test: cache.test_conditional.TestConditionalHttp.test_response_without_last_modified_and_date Apr 26 12:28:00 192.168.122.209 [73430.780598] [tdb] Start Tempesta DB Apr 26 12:28:00 192.168.122.209 [73430.926219] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:28:01 192.168.122.209 [73432.326134] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73432.326134] Maybe that's fine, but it's worth checking the [73432.326134] config - if there is no relations between the [73432.326134] names, then host name confusion attack is possible. Apr 26 12:28:01 192.168.122.209 [73432.500940] [tempesta fw] Configuration processing is completed. Apr 26 12:28:01 192.168.122.209 [73432.558771] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:28:02 192.168.122.209 [73433.020038] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:28:02 192.168.122.209 [73433.050345] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:28:02 192.168.122.209 [73433.079817] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:28:02 192.168.122.209 [73433.136879] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:28:02 192.168.122.209 [73433.138717] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:28:02 192.168.122.209 [73433.180820] [tempesta fw] Tempesta FW is ready Apr 26 12:28:03 192.168.122.209 [73433.848206] [tdb] Close table 'client0.tdb' Apr 26 12:28:03 192.168.122.209 [73434.033041] [tdb] Close table 'sessions0.tdb' Apr 26 12:28:06 192.168.122.209 [73437.190654] [tdb] Close table 'cache0.tdb' Apr 26 12:28:06 192.168.122.209 [73437.437160] [tdb] Close table 'filter0.tdb' Apr 26 12:28:06 192.168.122.209 [73437.437597] [tempesta fw] modules are stopped Apr 26 12:28:06 192.168.122.209 [73437.625971] [tempesta fw] exiting... Apr 26 12:28:07 192.168.122.209 [73437.778693] [tdb] Shutdown Tempesta DB Apr 26 12:28:07 192.168.122.209 [73438.186916] End test: cache.test_conditional.TestConditionalHttp.test_response_without_last_modified_and_date Apr 26 12:28:07 192.168.122.209 [73438.213702] Start test: cache.test_conditional.TestConditionalHttp.test_response_without_last_modified_and_date_nc Apr 26 12:28:08 192.168.122.209 [73439.675288] [tdb] Start Tempesta DB Apr 26 12:28:09 192.168.122.209 [73439.819151] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:28:10 192.168.122.209 [73441.326242] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73441.326242] Maybe that's fine, but it's worth checking the [73441.326242] config - if there is no relations between the [73441.326242] names, then host name confusion attack is possible. Apr 26 12:28:10 192.168.122.209 [73441.485003] [tempesta fw] Configuration processing is completed. Apr 26 12:28:10 192.168.122.209 [73441.555789] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:28:11 192.168.122.209 [73441.963763] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:28:11 192.168.122.209 [73441.989548] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:28:11 192.168.122.209 [73442.015102] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:28:11 192.168.122.209 [73442.056981] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:28:11 192.168.122.209 [73442.058710] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:28:11 192.168.122.209 [73442.096926] [tempesta fw] Tempesta FW is ready Apr 26 12:28:11 192.168.122.209 [73442.724489] [tdb] Close table 'client0.tdb' Apr 26 12:28:12 192.168.122.209 [73442.917530] [tdb] Close table 'sessions0.tdb' Apr 26 12:28:15 192.168.122.209 [73446.093158] [tdb] Close table 'cache0.tdb' Apr 26 12:28:15 192.168.122.209 [73446.334323] [tdb] Close table 'filter0.tdb' Apr 26 12:28:15 192.168.122.209 [73446.334741] [tempesta fw] modules are stopped Apr 26 12:28:15 192.168.122.209 [73446.503303] [tempesta fw] exiting... Apr 26 12:28:15 192.168.122.209 [73446.640713] [tdb] Shutdown Tempesta DB Apr 26 12:28:16 192.168.122.209 [73447.030704] End test: cache.test_conditional.TestConditionalHttp.test_response_without_last_modified_and_date_nc Apr 26 12:28:16 192.168.122.209 [73447.062030] Start test: cache.test_conditional.TestConditionalHttp.test_response_without_last_modified_nc Apr 26 12:28:17 192.168.122.209 [73448.428305] [tdb] Start Tempesta DB Apr 26 12:28:17 192.168.122.209 [73448.566199] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:28:19 192.168.122.209 [73449.950440] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73449.950440] Maybe that's fine, but it's worth checking the [73449.950440] config - if there is no relations between the [73449.950440] names, then host name confusion attack is possible. Apr 26 12:28:19 192.168.122.209 [73450.069387] [tempesta fw] Configuration processing is completed. Apr 26 12:28:19 192.168.122.209 [73450.124132] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:28:19 192.168.122.209 [73450.574766] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:28:19 192.168.122.209 [73450.608490] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:28:19 192.168.122.209 [73450.635889] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:28:19 192.168.122.209 [73450.689232] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:28:19 192.168.122.209 [73450.690994] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:28:20 192.168.122.209 [73450.737050] [tempesta fw] Tempesta FW is ready Apr 26 12:28:20 192.168.122.209 [73451.375955] [tdb] Close table 'client0.tdb' Apr 26 12:28:20 192.168.122.209 [73451.557807] [tdb] Close table 'sessions0.tdb' Apr 26 12:28:23 192.168.122.209 [73454.682756] [tdb] Close table 'cache0.tdb' Apr 26 12:28:24 192.168.122.209 [73454.944229] [tdb] Close table 'filter0.tdb' Apr 26 12:28:24 192.168.122.209 [73454.944753] [tempesta fw] modules are stopped Apr 26 12:28:24 192.168.122.209 [73455.146478] [tempesta fw] exiting... Apr 26 12:28:24 192.168.122.209 [73455.300882] [tdb] Shutdown Tempesta DB Apr 26 12:28:24 192.168.122.209 [73455.668870] End test: cache.test_conditional.TestConditionalHttp.test_response_without_last_modified_nc Apr 26 12:28:24 192.168.122.209 [73455.706972] Start test: cache.test_conditional.TestNotModifiedResponseHeadersH2.test_cachable_headers_cache_control Apr 26 12:28:26 192.168.122.209 [73457.100218] [tdb] Start Tempesta DB Apr 26 12:28:26 192.168.122.209 [73457.217979] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:28:27 192.168.122.209 [73458.622425] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73458.622425] Maybe that's fine, but it's worth checking the [73458.622425] config - if there is no relations between the [73458.622425] names, then host name confusion attack is possible. Apr 26 12:28:28 192.168.122.209 [73458.753210] [tempesta fw] Configuration processing is completed. Apr 26 12:28:28 192.168.122.209 [73458.805178] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:28:28 192.168.122.209 [73459.220600] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:28:28 192.168.122.209 [73459.245657] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:28:28 192.168.122.209 [73459.271136] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:28:28 192.168.122.209 [73459.309124] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:28:28 192.168.122.209 [73459.310304] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:28:28 192.168.122.209 [73459.349051] [tempesta fw] Tempesta FW is ready Apr 26 12:28:29 192.168.122.209 [73460.000328] [tdb] Close table 'client0.tdb' Apr 26 12:28:29 192.168.122.209 [73460.202177] [tdb] Close table 'sessions0.tdb' Apr 26 12:28:32 192.168.122.209 [73463.334106] [tdb] Close table 'cache0.tdb' Apr 26 12:28:32 192.168.122.209 [73463.560583] [tdb] Close table 'filter0.tdb' Apr 26 12:28:32 192.168.122.209 [73463.560986] [tempesta fw] modules are stopped Apr 26 12:28:33 192.168.122.209 [73463.746517] [tempesta fw] exiting... Apr 26 12:28:33 192.168.122.209 [73463.892292] [tdb] Shutdown Tempesta DB Apr 26 12:28:33 192.168.122.209 [73464.343555] End test: cache.test_conditional.TestNotModifiedResponseHeadersH2.test_cachable_headers_cache_control Apr 26 12:28:33 192.168.122.209 [73464.375889] Start test: cache.test_conditional.TestNotModifiedResponseHeadersH2.test_cachable_headers_content_location Apr 26 12:28:34 192.168.122.209 [73465.687381] [tdb] Start Tempesta DB Apr 26 12:28:35 192.168.122.209 [73465.803214] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:28:36 192.168.122.209 [73467.318587] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73467.318587] Maybe that's fine, but it's worth checking the [73467.318587] config - if there is no relations between the [73467.318587] names, then host name confusion attack is possible. Apr 26 12:28:36 192.168.122.209 [73467.449331] [tempesta fw] Configuration processing is completed. Apr 26 12:28:36 192.168.122.209 [73467.500730] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:28:37 192.168.122.209 [73467.912545] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:28:37 192.168.122.209 [73467.938644] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:28:37 192.168.122.209 [73467.963855] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:28:37 192.168.122.209 [73468.005241] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:28:37 192.168.122.209 [73468.006527] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:28:37 192.168.122.209 [73468.045272] [tempesta fw] Tempesta FW is ready Apr 26 12:28:37 192.168.122.209 [73468.684582] [tdb] Close table 'client0.tdb' Apr 26 12:28:38 192.168.122.209 [73468.872614] [tdb] Close table 'sessions0.tdb' Apr 26 12:28:41 192.168.122.209 [73472.041103] [tdb] Close table 'cache0.tdb' Apr 26 12:28:41 192.168.122.209 [73472.287623] [tdb] Close table 'filter0.tdb' Apr 26 12:28:41 192.168.122.209 [73472.288059] [tempesta fw] modules are stopped Apr 26 12:28:41 192.168.122.209 [73472.489482] [tempesta fw] exiting... Apr 26 12:28:41 192.168.122.209 [73472.604090] [tdb] Shutdown Tempesta DB Apr 26 12:28:42 192.168.122.209 [73473.038406] End test: cache.test_conditional.TestNotModifiedResponseHeadersH2.test_cachable_headers_content_location Apr 26 12:28:42 192.168.122.209 [73473.070399] Start test: cache.test_conditional.TestNotModifiedResponseHeadersH2.test_cachable_headers_etag Apr 26 12:28:43 192.168.122.209 [73474.433609] [tdb] Start Tempesta DB Apr 26 12:28:43 192.168.122.209 [73474.568132] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:28:45 192.168.122.209 [73476.074748] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73476.074748] Maybe that's fine, but it's worth checking the [73476.074748] config - if there is no relations between the [73476.074748] names, then host name confusion attack is possible. Apr 26 12:28:45 192.168.122.209 [73476.209418] [tempesta fw] Configuration processing is completed. Apr 26 12:28:45 192.168.122.209 [73476.266227] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:28:45 192.168.122.209 [73476.695369] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:28:45 192.168.122.209 [73476.721602] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:28:46 192.168.122.209 [73476.747608] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:28:46 192.168.122.209 [73476.797413] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:28:46 192.168.122.209 [73476.799022] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:28:46 192.168.122.209 [73476.841355] [tempesta fw] Tempesta FW is ready Apr 26 12:28:46 192.168.122.209 [73477.445649] [tdb] Close table 'client0.tdb' Apr 26 12:28:46 192.168.122.209 [73477.634386] [tdb] Close table 'sessions0.tdb' Apr 26 12:28:50 192.168.122.209 [73480.805576] [tdb] Close table 'cache0.tdb' Apr 26 12:28:50 192.168.122.209 [73481.029717] [tdb] Close table 'filter0.tdb' Apr 26 12:28:50 192.168.122.209 [73481.030166] [tempesta fw] modules are stopped Apr 26 12:28:50 192.168.122.209 [73481.280891] [tempesta fw] exiting... Apr 26 12:28:50 192.168.122.209 [73481.414959] [tdb] Shutdown Tempesta DB Apr 26 12:28:50 192.168.122.209 [73481.725245] End test: cache.test_conditional.TestNotModifiedResponseHeadersH2.test_cachable_headers_etag Apr 26 12:28:51 192.168.122.209 [73481.813445] Start test: cache.test_conditional.TestNotModifiedResponseHeadersH2.test_cachable_headers_expires Apr 26 12:28:52 192.168.122.209 [73483.179965] [tdb] Start Tempesta DB Apr 26 12:28:52 192.168.122.209 [73483.312383] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:28:54 192.168.122.209 [73484.782756] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73484.782756] Maybe that's fine, but it's worth checking the [73484.782756] config - if there is no relations between the [73484.782756] names, then host name confusion attack is possible. Apr 26 12:28:54 192.168.122.209 [73484.933530] [tempesta fw] Configuration processing is completed. Apr 26 12:28:54 192.168.122.209 [73484.985022] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:28:54 192.168.122.209 [73485.403593] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:28:54 192.168.122.209 [73485.429727] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:28:54 192.168.122.209 [73485.456874] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:28:54 192.168.122.209 [73485.509538] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:28:54 192.168.122.209 [73485.511285] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:28:54 192.168.122.209 [73485.561475] [tempesta fw] Tempesta FW is ready Apr 26 12:28:55 192.168.122.209 [73486.176850] [tdb] Close table 'client0.tdb' Apr 26 12:28:55 192.168.122.209 [73486.356334] [tdb] Close table 'sessions0.tdb' Apr 26 12:28:58 192.168.122.209 [73489.507339] [tdb] Close table 'cache0.tdb' Apr 26 12:28:59 192.168.122.209 [73489.759299] [tdb] Close table 'filter0.tdb' Apr 26 12:28:59 192.168.122.209 [73489.759725] [tempesta fw] modules are stopped Apr 26 12:28:59 192.168.122.209 [73489.987749] [tempesta fw] exiting... Apr 26 12:28:59 192.168.122.209 [73490.129293] [tdb] Shutdown Tempesta DB Apr 26 12:28:59 192.168.122.209 [73490.493688] End test: cache.test_conditional.TestNotModifiedResponseHeadersH2.test_cachable_headers_expires Apr 26 12:28:59 192.168.122.209 [73490.517363] Start test: cache.test_conditional.TestNotModifiedResponseHeadersH2.test_cachable_headers_vary Apr 26 12:29:01 192.168.122.209 [73491.907083] [tdb] Start Tempesta DB Apr 26 12:29:01 192.168.122.209 [73492.031528] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:29:02 192.168.122.209 [73493.506938] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73493.506938] Maybe that's fine, but it's worth checking the [73493.506938] config - if there is no relations between the [73493.506938] names, then host name confusion attack is possible. Apr 26 12:29:02 192.168.122.209 [73493.641661] [tempesta fw] Configuration processing is completed. Apr 26 12:29:02 192.168.122.209 [73493.694485] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:29:03 192.168.122.209 [73494.114402] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:29:03 192.168.122.209 [73494.150862] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:29:03 192.168.122.209 [73494.176236] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:29:03 192.168.122.209 [73494.241650] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:29:03 192.168.122.209 [73494.243405] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:29:03 192.168.122.209 [73494.289581] [tempesta fw] Tempesta FW is ready Apr 26 12:29:04 192.168.122.209 [73494.929094] [tdb] Close table 'client0.tdb' Apr 26 12:29:04 192.168.122.209 [73495.112471] [tdb] Close table 'sessions0.tdb' Apr 26 12:29:07 192.168.122.209 [73498.290730] [tdb] Close table 'cache0.tdb' Apr 26 12:29:07 192.168.122.209 [73498.539379] [tdb] Close table 'filter0.tdb' Apr 26 12:29:07 192.168.122.209 [73498.539784] [tempesta fw] modules are stopped Apr 26 12:29:08 192.168.122.209 [73498.742670] [tempesta fw] exiting... Apr 26 12:29:08 192.168.122.209 [73498.863587] [tdb] Shutdown Tempesta DB Apr 26 12:29:08 192.168.122.209 [73499.312851] End test: cache.test_conditional.TestNotModifiedResponseHeadersH2.test_cachable_headers_vary Apr 26 12:29:08 192.168.122.209 [73499.346802] Start test: cache.test_conditional.TestNotModifiedResponseHeadersH2.test_non_cachable_header Apr 26 12:29:09 192.168.122.209 [73500.707665] [tdb] Start Tempesta DB Apr 26 12:29:10 192.168.122.209 [73500.839190] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:29:11 192.168.122.209 [73502.295032] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73502.295032] Maybe that's fine, but it's worth checking the [73502.295032] config - if there is no relations between the [73502.295032] names, then host name confusion attack is possible. Apr 26 12:29:11 192.168.122.209 [73502.445803] [tempesta fw] Configuration processing is completed. Apr 26 12:29:11 192.168.122.209 [73502.497009] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:29:12 192.168.122.209 [73502.908681] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:29:12 192.168.122.209 [73502.935950] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:29:12 192.168.122.209 [73502.961900] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:29:12 192.168.122.209 [73503.029744] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:29:12 192.168.122.209 [73503.031476] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:29:12 192.168.122.209 [73503.089691] [tempesta fw] Tempesta FW is ready Apr 26 12:29:13 192.168.122.209 [73503.761666] [tdb] Close table 'client0.tdb' Apr 26 12:29:13 192.168.122.209 [73503.927954] [tdb] Close table 'sessions0.tdb' Apr 26 12:29:16 192.168.122.209 [73507.106488] [tdb] Close table 'cache0.tdb' Apr 26 12:29:16 192.168.122.209 [73507.374585] [tdb] Close table 'filter0.tdb' Apr 26 12:29:16 192.168.122.209 [73507.375003] [tempesta fw] modules are stopped Apr 26 12:29:16 192.168.122.209 [73507.562561] [tempesta fw] exiting... Apr 26 12:29:16 192.168.122.209 [73507.691794] [tdb] Shutdown Tempesta DB Apr 26 12:29:17 192.168.122.209 [73508.103525] End test: cache.test_conditional.TestNotModifiedResponseHeadersH2.test_non_cachable_header Apr 26 12:29:17 192.168.122.209 [73508.135742] Start test: cache.test_conditional.TestNotModifiedResponseHeadersHttp.test_cachable_headers_cache_control Apr 26 12:29:18 192.168.122.209 [73509.470498] [tdb] Start Tempesta DB Apr 26 12:29:18 192.168.122.209 [73509.591418] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:29:20 192.168.122.209 [73511.047198] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73511.047198] Maybe that's fine, but it's worth checking the [73511.047198] config - if there is no relations between the [73511.047198] names, then host name confusion attack is possible. Apr 26 12:29:20 192.168.122.209 [73511.185828] [tempesta fw] Configuration processing is completed. Apr 26 12:29:20 192.168.122.209 [73511.242587] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:29:20 192.168.122.209 [73511.662608] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:29:20 192.168.122.209 [73511.689431] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:29:20 192.168.122.209 [73511.714516] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:29:21 192.168.122.209 [73511.765871] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:29:21 192.168.122.209 [73511.767611] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:29:21 192.168.122.209 [73511.813813] [tempesta fw] Tempesta FW is ready Apr 26 12:29:21 192.168.122.209 [73512.460873] [tdb] Close table 'client0.tdb' Apr 26 12:29:21 192.168.122.209 [73512.632217] [tdb] Close table 'sessions0.tdb' Apr 26 12:29:25 192.168.122.209 [73515.870994] [tdb] Close table 'cache0.tdb' Apr 26 12:29:25 192.168.122.209 [73516.126868] [tdb] Close table 'filter0.tdb' Apr 26 12:29:25 192.168.122.209 [73516.127298] [tempesta fw] modules are stopped Apr 26 12:29:25 192.168.122.209 [73516.326034] [tempesta fw] exiting... Apr 26 12:29:25 192.168.122.209 [73516.457392] [tdb] Shutdown Tempesta DB Apr 26 12:29:26 192.168.122.209 [73516.884781] End test: cache.test_conditional.TestNotModifiedResponseHeadersHttp.test_cachable_headers_cache_control Apr 26 12:29:26 192.168.122.209 [73516.915061] Start test: cache.test_conditional.TestNotModifiedResponseHeadersHttp.test_cachable_headers_content_location Apr 26 12:29:27 192.168.122.209 [73518.335026] [tdb] Start Tempesta DB Apr 26 12:29:27 192.168.122.209 [73518.466831] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:29:29 192.168.122.209 [73519.899215] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73519.899215] Maybe that's fine, but it's worth checking the [73519.899215] config - if there is no relations between the [73519.899215] names, then host name confusion attack is possible. Apr 26 12:29:29 192.168.122.209 [73520.050035] [tempesta fw] Configuration processing is completed. Apr 26 12:29:29 192.168.122.209 [73520.108606] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:29:29 192.168.122.209 [73520.544305] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:29:29 192.168.122.209 [73520.570825] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:29:29 192.168.122.209 [73520.602864] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:29:29 192.168.122.209 [73520.642003] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:29:29 192.168.122.209 [73520.643866] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:29:29 192.168.122.209 [73520.685835] [tempesta fw] Tempesta FW is ready Apr 26 12:29:30 192.168.122.209 [73521.318170] [tdb] Close table 'client0.tdb' Apr 26 12:29:30 192.168.122.209 [73521.520301] [tdb] Close table 'sessions0.tdb' Apr 26 12:29:33 192.168.122.209 [73524.658542] [tdb] Close table 'cache0.tdb' Apr 26 12:29:34 192.168.122.209 [73524.899578] [tdb] Close table 'filter0.tdb' Apr 26 12:29:34 192.168.122.209 [73524.900036] [tempesta fw] modules are stopped Apr 26 12:29:34 192.168.122.209 [73525.098820] [tempesta fw] exiting... Apr 26 12:29:34 192.168.122.209 [73525.206099] [tdb] Shutdown Tempesta DB Apr 26 12:29:34 192.168.122.209 [73525.622764] End test: cache.test_conditional.TestNotModifiedResponseHeadersHttp.test_cachable_headers_content_location Apr 26 12:29:34 192.168.122.209 [73525.651959] Start test: cache.test_conditional.TestNotModifiedResponseHeadersHttp.test_cachable_headers_etag Apr 26 12:29:36 192.168.122.209 [73527.059955] [tdb] Start Tempesta DB Apr 26 12:29:36 192.168.122.209 [73527.186813] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:29:37 192.168.122.209 [73528.599480] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73528.599480] Maybe that's fine, but it's worth checking the [73528.599480] config - if there is no relations between the [73528.599480] names, then host name confusion attack is possible. Apr 26 12:29:38 192.168.122.209 [73528.734086] [tempesta fw] Configuration processing is completed. Apr 26 12:29:38 192.168.122.209 [73528.795037] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:29:38 192.168.122.209 [73529.257895] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:29:38 192.168.122.209 [73529.286428] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:29:38 192.168.122.209 [73529.314368] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:29:38 192.168.122.209 [73529.382094] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:29:38 192.168.122.209 [73529.383898] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:29:38 192.168.122.209 [73529.430030] [tempesta fw] Tempesta FW is ready Apr 26 12:29:39 192.168.122.209 [73530.078518] [tdb] Close table 'client0.tdb' Apr 26 12:29:39 192.168.122.209 [73530.260190] [tdb] Close table 'sessions0.tdb' Apr 26 12:29:42 192.168.122.209 [73533.366747] [tdb] Close table 'cache0.tdb' Apr 26 12:29:42 192.168.122.209 [73533.650356] [tdb] Close table 'filter0.tdb' Apr 26 12:29:42 192.168.122.209 [73533.650805] [tempesta fw] modules are stopped Apr 26 12:29:43 192.168.122.209 [73533.840094] [tempesta fw] exiting... Apr 26 12:29:43 192.168.122.209 [73533.957297] [tdb] Shutdown Tempesta DB Apr 26 12:29:43 192.168.122.209 [73534.353501] End test: cache.test_conditional.TestNotModifiedResponseHeadersHttp.test_cachable_headers_etag Apr 26 12:29:43 192.168.122.209 [73534.434444] Start test: cache.test_conditional.TestNotModifiedResponseHeadersHttp.test_cachable_headers_expires Apr 26 12:29:45 192.168.122.209 [73535.895789] [tdb] Start Tempesta DB Apr 26 12:29:45 192.168.122.209 [73536.031716] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:29:46 192.168.122.209 [73537.459460] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73537.459460] Maybe that's fine, but it's worth checking the [73537.459460] config - if there is no relations between the [73537.459460] names, then host name confusion attack is possible. Apr 26 12:29:46 192.168.122.209 [73537.602206] [tempesta fw] Configuration processing is completed. Apr 26 12:29:46 192.168.122.209 [73537.660662] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:29:47 192.168.122.209 [73538.142352] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:29:47 192.168.122.209 [73538.185793] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:29:47 192.168.122.209 [73538.217791] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:29:47 192.168.122.209 [73538.274236] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:29:47 192.168.122.209 [73538.276055] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:29:47 192.168.122.209 [73538.314137] [tempesta fw] Tempesta FW is ready Apr 26 12:29:48 192.168.122.209 [73538.939011] [tdb] Close table 'client0.tdb' Apr 26 12:29:48 192.168.122.209 [73539.112851] [tdb] Close table 'sessions0.tdb' Apr 26 12:29:51 192.168.122.209 [73542.311889] [tdb] Close table 'cache0.tdb' Apr 26 12:29:51 192.168.122.209 [73542.555122] [tdb] Close table 'filter0.tdb' Apr 26 12:29:51 192.168.122.209 [73542.555567] [tempesta fw] modules are stopped Apr 26 12:29:52 192.168.122.209 [73542.760479] [tempesta fw] exiting... Apr 26 12:29:52 192.168.122.209 [73542.887047] [tdb] Shutdown Tempesta DB Apr 26 12:29:52 192.168.122.209 [73543.329985] End test: cache.test_conditional.TestNotModifiedResponseHeadersHttp.test_cachable_headers_expires Apr 26 12:29:52 192.168.122.209 [73543.368531] Start test: cache.test_conditional.TestNotModifiedResponseHeadersHttp.test_cachable_headers_vary Apr 26 12:29:54 192.168.122.209 [73544.757587] [tdb] Start Tempesta DB Apr 26 12:29:54 192.168.122.209 [73544.901718] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:29:55 192.168.122.209 [73546.383678] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73546.383678] Maybe that's fine, but it's worth checking the [73546.383678] config - if there is no relations between the [73546.383678] names, then host name confusion attack is possible. Apr 26 12:29:55 192.168.122.209 [73546.514332] [tempesta fw] Configuration processing is completed. Apr 26 12:29:55 192.168.122.209 [73546.576598] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:29:56 192.168.122.209 [73547.064073] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:29:56 192.168.122.209 [73547.096984] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:29:56 192.168.122.209 [73547.130733] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:29:56 192.168.122.209 [73547.222354] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:29:56 192.168.122.209 [73547.224096] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:29:56 192.168.122.209 [73547.266288] [tempesta fw] Tempesta FW is ready Apr 26 12:29:57 192.168.122.209 [73547.930376] [tdb] Close table 'client0.tdb' Apr 26 12:29:57 192.168.122.209 [73548.111481] [tdb] Close table 'sessions0.tdb' Apr 26 12:30:00 192.168.122.209 [73551.279348] [tdb] Close table 'cache0.tdb' Apr 26 12:30:00 192.168.122.209 [73551.560158] [tdb] Close table 'filter0.tdb' Apr 26 12:30:00 192.168.122.209 [73551.560600] [tempesta fw] modules are stopped Apr 26 12:30:01 192.168.122.209 [73551.736589] [tempesta fw] exiting... Apr 26 12:30:01 192.168.122.209 [73551.862806] [tdb] Shutdown Tempesta DB Apr 26 12:30:01 192.168.122.209 [73552.328878] End test: cache.test_conditional.TestNotModifiedResponseHeadersHttp.test_cachable_headers_vary Apr 26 12:30:01 192.168.122.209 [73552.365198] Start test: cache.test_conditional.TestNotModifiedResponseHeadersHttp.test_non_cachable_header Apr 26 12:30:02 192.168.122.209 [73553.681101] [tdb] Start Tempesta DB Apr 26 12:30:03 192.168.122.209 [73553.831864] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:30:04 192.168.122.209 [73555.299740] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73555.299740] Maybe that's fine, but it's worth checking the [73555.299740] config - if there is no relations between the [73555.299740] names, then host name confusion attack is possible. Apr 26 12:30:04 192.168.122.209 [73555.446447] [tempesta fw] Configuration processing is completed. Apr 26 12:30:04 192.168.122.209 [73555.502548] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:30:05 192.168.122.209 [73555.933663] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:30:05 192.168.122.209 [73555.961284] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:30:05 192.168.122.209 [73555.988944] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:30:05 192.168.122.209 [73556.042423] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:30:05 192.168.122.209 [73556.044173] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:30:05 192.168.122.209 [73556.082383] [tempesta fw] Tempesta FW is ready Apr 26 12:30:06 192.168.122.209 [73556.741973] [tdb] Close table 'client0.tdb' Apr 26 12:30:06 192.168.122.209 [73556.928651] [tdb] Close table 'sessions0.tdb' Apr 26 12:30:09 192.168.122.209 [73560.100956] [tdb] Close table 'cache0.tdb' Apr 26 12:30:09 192.168.122.209 [73560.365252] [tdb] Close table 'filter0.tdb' Apr 26 12:30:09 192.168.122.209 [73560.365708] [tempesta fw] modules are stopped Apr 26 12:30:09 192.168.122.209 [73560.536292] [tempesta fw] exiting... Apr 26 12:30:09 192.168.122.209 [73560.647699] [tdb] Shutdown Tempesta DB Apr 26 12:30:10 192.168.122.209 [73561.082660] End test: cache.test_conditional.TestNotModifiedResponseHeadersHttp.test_non_cachable_header Apr 26 12:30:10 192.168.122.209 [73561.111230] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_authorization_in_first_request_must_revalidate_in_response Apr 26 12:30:11 192.168.122.209 [73562.510146] [tdb] Start Tempesta DB Apr 26 12:30:11 192.168.122.209 [73562.655438] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:30:13 192.168.122.209 [73564.055860] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73564.055860] Maybe that's fine, but it's worth checking the [73564.055860] config - if there is no relations between the [73564.055860] names, then host name confusion attack is possible. Apr 26 12:30:13 192.168.122.209 [73564.182542] [tempesta fw] Configuration processing is completed. Apr 26 12:30:13 192.168.122.209 [73564.246700] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:30:14 192.168.122.209 [73564.790975] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:30:14 192.168.122.209 [73564.823903] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:30:14 192.168.122.209 [73564.856022] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:30:14 192.168.122.209 [73564.914555] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:30:14 192.168.122.209 [73564.916290] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:30:14 192.168.122.209 [73564.974472] [tempesta fw] Tempesta FW is ready Apr 26 12:30:14 192.168.122.209 [73565.656305] [tdb] Close table 'client0.tdb' Apr 26 12:30:15 192.168.122.209 [73565.854277] [tdb] Close table 'sessions0.tdb' Apr 26 12:30:18 192.168.122.209 [73568.954652] [tdb] Close table 'cache0.tdb' Apr 26 12:30:18 192.168.122.209 [73569.247027] [tdb] Close table 'filter0.tdb' Apr 26 12:30:18 192.168.122.209 [73569.247467] [tempesta fw] modules are stopped Apr 26 12:30:18 192.168.122.209 [73569.426310] [tempesta fw] exiting... Apr 26 12:30:18 192.168.122.209 [73569.563180] [tdb] Shutdown Tempesta DB Apr 26 12:30:19 192.168.122.209 [73569.936014] End test: cache.test_h2_cache_control.TestH2CacheControl.test_authorization_in_first_request_must_revalidate_in_response Apr 26 12:30:19 192.168.122.209 [73569.976489] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_authorization_in_first_request_proxy_revalidate_in_response Apr 26 12:30:20 192.168.122.209 [73571.385745] [tdb] Start Tempesta DB Apr 26 12:30:20 192.168.122.209 [73571.533018] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:30:22 192.168.122.209 [73572.915900] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73572.915900] Maybe that's fine, but it's worth checking the [73572.915900] config - if there is no relations between the [73572.915900] names, then host name confusion attack is possible. Apr 26 12:30:22 192.168.122.209 [73573.022657] [tempesta fw] Configuration processing is completed. Apr 26 12:30:22 192.168.122.209 [73573.082132] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:30:22 192.168.122.209 [73573.530652] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:30:22 192.168.122.209 [73573.566708] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:30:22 192.168.122.209 [73573.593035] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:30:22 192.168.122.209 [73573.646639] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:30:22 192.168.122.209 [73573.648421] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:30:22 192.168.122.209 [73573.686579] [tempesta fw] Tempesta FW is ready Apr 26 12:30:23 192.168.122.209 [73574.400143] [tdb] Close table 'client0.tdb' Apr 26 12:30:23 192.168.122.209 [73574.588928] [tdb] Close table 'sessions0.tdb' Apr 26 12:30:27 192.168.122.209 [73577.788136] [tdb] Close table 'cache0.tdb' Apr 26 12:30:27 192.168.122.209 [73578.045347] [tdb] Close table 'filter0.tdb' Apr 26 12:30:27 192.168.122.209 [73578.045782] [tempesta fw] modules are stopped Apr 26 12:30:27 192.168.122.209 [73578.231880] [tempesta fw] exiting... Apr 26 12:30:27 192.168.122.209 [73578.359295] [tdb] Shutdown Tempesta DB Apr 26 12:30:27 192.168.122.209 [73578.721541] End test: cache.test_h2_cache_control.TestH2CacheControl.test_authorization_in_first_request_proxy_revalidate_in_response Apr 26 12:30:28 192.168.122.209 [73578.749567] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_authorization_in_first_request_public_in_response Apr 26 12:30:29 192.168.122.209 [73580.211230] [tdb] Start Tempesta DB Apr 26 12:30:29 192.168.122.209 [73580.345838] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:30:31 192.168.122.209 [73581.760041] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73581.760041] Maybe that's fine, but it's worth checking the [73581.760041] config - if there is no relations between the [73581.760041] names, then host name confusion attack is possible. Apr 26 12:30:31 192.168.122.209 [73581.878758] [tempesta fw] Configuration processing is completed. Apr 26 12:30:31 192.168.122.209 [73581.940562] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:30:31 192.168.122.209 [73582.377232] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:30:31 192.168.122.209 [73582.404197] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:30:31 192.168.122.209 [73582.431144] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:30:31 192.168.122.209 [73582.498768] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:30:31 192.168.122.209 [73582.500515] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:30:31 192.168.122.209 [73582.542695] [tempesta fw] Tempesta FW is ready Apr 26 12:30:32 192.168.122.209 [73583.194649] [tdb] Close table 'client0.tdb' Apr 26 12:30:32 192.168.122.209 [73583.394595] [tdb] Close table 'sessions0.tdb' Apr 26 12:30:35 192.168.122.209 [73586.514260] [tdb] Close table 'cache0.tdb' Apr 26 12:30:36 192.168.122.209 [73586.747518] [tdb] Close table 'filter0.tdb' Apr 26 12:30:36 192.168.122.209 [73586.748114] [tempesta fw] modules are stopped Apr 26 12:30:36 192.168.122.209 [73586.995236] [tempesta fw] exiting... Apr 26 12:30:36 192.168.122.209 [73587.133262] [tdb] Shutdown Tempesta DB Apr 26 12:30:36 192.168.122.209 [73587.515402] End test: cache.test_h2_cache_control.TestH2CacheControl.test_authorization_in_first_request_public_in_response Apr 26 12:30:36 192.168.122.209 [73587.547108] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_authorization_in_first_request_s_maxage_in_response Apr 26 12:30:38 192.168.122.209 [73588.937793] [tdb] Start Tempesta DB Apr 26 12:30:38 192.168.122.209 [73589.063080] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:30:39 192.168.122.209 [73590.500090] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73590.500090] Maybe that's fine, but it's worth checking the [73590.500090] config - if there is no relations between the [73590.500090] names, then host name confusion attack is possible. Apr 26 12:30:39 192.168.122.209 [73590.614846] [tempesta fw] Configuration processing is completed. Apr 26 12:30:39 192.168.122.209 [73590.673744] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:30:40 192.168.122.209 [73591.086662] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:30:40 192.168.122.209 [73591.114314] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:30:40 192.168.122.209 [73591.141965] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:30:40 192.168.122.209 [73591.186852] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:30:40 192.168.122.209 [73591.188593] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:30:40 192.168.122.209 [73591.226833] [tempesta fw] Tempesta FW is ready Apr 26 12:30:41 192.168.122.209 [73591.879468] [tdb] Close table 'client0.tdb' Apr 26 12:30:41 192.168.122.209 [73592.074427] [tdb] Close table 'sessions0.tdb' Apr 26 12:30:44 192.168.122.209 [73595.224444] [tdb] Close table 'cache0.tdb' Apr 26 12:30:44 192.168.122.209 [73595.464244] [tdb] Close table 'filter0.tdb' Apr 26 12:30:44 192.168.122.209 [73595.464674] [tempesta fw] modules are stopped Apr 26 12:30:44 192.168.122.209 [73595.671251] [tempesta fw] exiting... Apr 26 12:30:45 192.168.122.209 [73595.786577] [tdb] Shutdown Tempesta DB Apr 26 12:30:45 192.168.122.209 [73596.197458] End test: cache.test_h2_cache_control.TestH2CacheControl.test_authorization_in_first_request_s_maxage_in_response Apr 26 12:30:45 192.168.122.209 [73596.228053] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_authorization_in_second_request Apr 26 12:30:46 192.168.122.209 [73597.727947] [tdb] Start Tempesta DB Apr 26 12:30:47 192.168.122.209 [73597.864253] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:30:48 192.168.122.209 [73599.308300] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73599.308300] Maybe that's fine, but it's worth checking the [73599.308300] config - if there is no relations between the [73599.308300] names, then host name confusion attack is possible. Apr 26 12:30:48 192.168.122.209 [73599.434989] [tempesta fw] Configuration processing is completed. Apr 26 12:30:48 192.168.122.209 [73599.487727] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:30:49 192.168.122.209 [73599.910642] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:30:49 192.168.122.209 [73599.937281] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:30:49 192.168.122.209 [73599.963430] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:30:49 192.168.122.209 [73600.018965] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:30:49 192.168.122.209 [73600.020698] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:30:49 192.168.122.209 [73600.058939] [tempesta fw] Tempesta FW is ready Apr 26 12:30:49 192.168.122.209 [73600.718342] [tdb] Close table 'client0.tdb' Apr 26 12:30:50 192.168.122.209 [73600.902036] [tdb] Close table 'sessions0.tdb' Apr 26 12:30:53 192.168.122.209 [73604.073879] [tdb] Close table 'cache0.tdb' Apr 26 12:30:53 192.168.122.209 [73604.294394] [tdb] Close table 'filter0.tdb' Apr 26 12:30:53 192.168.122.209 [73604.294862] [tempesta fw] modules are stopped Apr 26 12:30:53 192.168.122.209 [73604.506042] [tempesta fw] exiting... Apr 26 12:30:53 192.168.122.209 [73604.625792] [tdb] Shutdown Tempesta DB Apr 26 12:30:54 192.168.122.209 [73605.036553] End test: cache.test_h2_cache_control.TestH2CacheControl.test_authorization_in_second_request Apr 26 12:30:54 192.168.122.209 [73605.068210] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_max_age_0_in_request Apr 26 12:30:55 192.168.122.209 [73606.520367] [tdb] Start Tempesta DB Apr 26 12:30:55 192.168.122.209 [73606.646635] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:30:57 192.168.122.209 [73608.088256] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73608.088256] Maybe that's fine, but it's worth checking the [73608.088256] config - if there is no relations between the [73608.088256] names, then host name confusion attack is possible. Apr 26 12:30:57 192.168.122.209 [73608.219028] [tempesta fw] Configuration processing is completed. Apr 26 12:30:57 192.168.122.209 [73608.278315] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:30:57 192.168.122.209 [73608.697667] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:30:57 192.168.122.209 [73608.723786] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:30:58 192.168.122.209 [73608.750225] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:30:58 192.168.122.209 [73608.786989] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:30:58 192.168.122.209 [73608.787971] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:30:58 192.168.122.209 [73608.831015] [tempesta fw] Tempesta FW is ready Apr 26 12:30:58 192.168.122.209 [73609.480883] [tdb] Close table 'client0.tdb' Apr 26 12:30:58 192.168.122.209 [73609.668085] [tdb] Close table 'sessions0.tdb' Apr 26 12:31:02 192.168.122.209 [73612.840096] [tdb] Close table 'cache0.tdb' Apr 26 12:31:02 192.168.122.209 [73613.064034] [tdb] Close table 'filter0.tdb' Apr 26 12:31:02 192.168.122.209 [73613.064464] [tempesta fw] modules are stopped Apr 26 12:31:02 192.168.122.209 [73613.271890] [tempesta fw] exiting... Apr 26 12:31:02 192.168.122.209 [73613.404720] [tdb] Shutdown Tempesta DB Apr 26 12:31:03 192.168.122.209 [73613.758020] End test: cache.test_h2_cache_control.TestH2CacheControl.test_max_age_0_in_request Apr 26 12:31:03 192.168.122.209 [73613.789546] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_max_age_0_in_response Apr 26 12:31:04 192.168.122.209 [73615.098746] [tdb] Start Tempesta DB Apr 26 12:31:04 192.168.122.209 [73615.240230] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:31:05 192.168.122.209 [73616.688435] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73616.688435] Maybe that's fine, but it's worth checking the [73616.688435] config - if there is no relations between the [73616.688435] names, then host name confusion attack is possible. Apr 26 12:31:06 192.168.122.209 [73616.811189] [tempesta fw] Configuration processing is completed. Apr 26 12:31:06 192.168.122.209 [73616.862168] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:31:06 192.168.122.209 [73617.282299] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:31:06 192.168.122.209 [73617.308283] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:31:06 192.168.122.209 [73617.333749] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:31:06 192.168.122.209 [73617.383217] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:31:06 192.168.122.209 [73617.385007] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:31:06 192.168.122.209 [73617.435124] [tempesta fw] Tempesta FW is ready Apr 26 12:31:07 192.168.122.209 [73618.055901] [tdb] Close table 'client0.tdb' Apr 26 12:31:07 192.168.122.209 [73618.243957] [tdb] Close table 'sessions0.tdb' Apr 26 12:31:10 192.168.122.209 [73621.385701] [tdb] Close table 'cache0.tdb' Apr 26 12:31:10 192.168.122.209 [73621.620124] [tdb] Close table 'filter0.tdb' Apr 26 12:31:10 192.168.122.209 [73621.620552] [tempesta fw] modules are stopped Apr 26 12:31:11 192.168.122.209 [73621.837562] [tempesta fw] exiting... Apr 26 12:31:11 192.168.122.209 [73621.977820] [tdb] Shutdown Tempesta DB Apr 26 12:31:11 192.168.122.209 [73622.346841] End test: cache.test_h2_cache_control.TestH2CacheControl.test_max_age_0_in_response Apr 26 12:31:11 192.168.122.209 [73622.376457] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_max_age_1_in_request_sleep_2 Apr 26 12:31:13 192.168.122.209 [73623.755606] [tdb] Start Tempesta DB Apr 26 12:31:13 192.168.122.209 [73623.889953] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:31:14 192.168.122.209 [73625.272562] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73625.272562] Maybe that's fine, but it's worth checking the [73625.272562] config - if there is no relations between the [73625.272562] names, then host name confusion attack is possible. Apr 26 12:31:14 192.168.122.209 [73625.387322] [tempesta fw] Configuration processing is completed. Apr 26 12:31:14 192.168.122.209 [73625.447422] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:31:15 192.168.122.209 [73625.855732] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:31:15 192.168.122.209 [73625.880635] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:31:15 192.168.122.209 [73625.905422] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:31:15 192.168.122.209 [73625.955294] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:31:15 192.168.122.209 [73625.957024] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:31:15 192.168.122.209 [73625.995273] [tempesta fw] Tempesta FW is ready Apr 26 12:31:17 192.168.122.209 [73628.642460] [tdb] Close table 'client0.tdb' Apr 26 12:31:18 192.168.122.209 [73628.834772] [tdb] Close table 'sessions0.tdb' Apr 26 12:31:21 192.168.122.209 [73631.970813] [tdb] Close table 'cache0.tdb' Apr 26 12:31:21 192.168.122.209 [73632.216954] [tdb] Close table 'filter0.tdb' Apr 26 12:31:21 192.168.122.209 [73632.217363] [tempesta fw] modules are stopped Apr 26 12:31:21 192.168.122.209 [73632.415959] [tempesta fw] exiting... Apr 26 12:31:21 192.168.122.209 [73632.568025] [tdb] Shutdown Tempesta DB Apr 26 12:31:22 192.168.122.209 [73632.903182] End test: cache.test_h2_cache_control.TestH2CacheControl.test_max_age_1_in_request_sleep_2 Apr 26 12:31:22 192.168.122.209 [73632.988583] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_max_age_1_in_request_sleep_2_from_hpack_dynamic_table Apr 26 12:31:23 192.168.122.209 [73634.430247] [tdb] Start Tempesta DB Apr 26 12:31:23 192.168.122.209 [73634.559276] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:31:25 192.168.122.209 [73636.008766] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73636.008766] Maybe that's fine, but it's worth checking the [73636.008766] config - if there is no relations between the [73636.008766] names, then host name confusion attack is possible. Apr 26 12:31:25 192.168.122.209 [73636.127409] [tempesta fw] Configuration processing is completed. Apr 26 12:31:25 192.168.122.209 [73636.188083] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:31:25 192.168.122.209 [73636.619521] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:31:25 192.168.122.209 [73636.646155] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:31:25 192.168.122.209 [73636.672133] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:31:25 192.168.122.209 [73636.711422] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:31:25 192.168.122.209 [73636.713158] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:31:26 192.168.122.209 [73636.751372] [tempesta fw] Tempesta FW is ready Apr 26 12:31:28 192.168.122.209 [73639.400240] [tdb] Close table 'client0.tdb' Apr 26 12:31:28 192.168.122.209 [73639.584252] [tdb] Close table 'sessions0.tdb' Apr 26 12:31:32 192.168.122.209 [73642.752548] [tdb] Close table 'cache0.tdb' Apr 26 12:31:32 192.168.122.209 [73642.977614] [tdb] Close table 'filter0.tdb' Apr 26 12:31:32 192.168.122.209 [73642.978062] [tempesta fw] modules are stopped Apr 26 12:31:32 192.168.122.209 [73643.213172] [tempesta fw] exiting... Apr 26 12:31:32 192.168.122.209 [73643.353207] [tdb] Shutdown Tempesta DB Apr 26 12:31:32 192.168.122.209 [73643.686109] End test: cache.test_h2_cache_control.TestH2CacheControl.test_max_age_1_in_request_sleep_2_from_hpack_dynamic_table Apr 26 12:31:32 192.168.122.209 [73643.720264] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_max_age_1_in_response_sleep_2 Apr 26 12:31:34 192.168.122.209 [73645.031984] [tdb] Start Tempesta DB Apr 26 12:31:34 192.168.122.209 [73645.165443] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:31:35 192.168.122.209 [73646.560801] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73646.560801] Maybe that's fine, but it's worth checking the [73646.560801] config - if there is no relations between the [73646.560801] names, then host name confusion attack is possible. Apr 26 12:31:35 192.168.122.209 [73646.699467] [tempesta fw] Configuration processing is completed. Apr 26 12:31:36 192.168.122.209 [73646.749907] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:31:36 192.168.122.209 [73647.154392] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:31:36 192.168.122.209 [73647.179065] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:31:36 192.168.122.209 [73647.204359] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:31:36 192.168.122.209 [73647.259554] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:31:36 192.168.122.209 [73647.261291] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:31:36 192.168.122.209 [73647.307519] [tempesta fw] Tempesta FW is ready Apr 26 12:31:39 192.168.122.209 [73649.980521] [tdb] Close table 'client0.tdb' Apr 26 12:31:39 192.168.122.209 [73650.160830] [tdb] Close table 'sessions0.tdb' Apr 26 12:31:42 192.168.122.209 [73653.275210] [tdb] Close table 'cache0.tdb' Apr 26 12:31:42 192.168.122.209 [73653.499900] [tdb] Close table 'filter0.tdb' Apr 26 12:31:42 192.168.122.209 [73653.500333] [tempesta fw] modules are stopped Apr 26 12:31:42 192.168.122.209 [73653.696875] [tempesta fw] exiting... Apr 26 12:31:43 192.168.122.209 [73653.802814] [tdb] Shutdown Tempesta DB Apr 26 12:31:43 192.168.122.209 [73654.246398] End test: cache.test_h2_cache_control.TestH2CacheControl.test_max_age_1_in_response_sleep_2 Apr 26 12:31:43 192.168.122.209 [73654.274852] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_max_age_2_in_request_sleep_0 Apr 26 12:31:44 192.168.122.209 [73655.725978] [tdb] Start Tempesta DB Apr 26 12:31:45 192.168.122.209 [73655.853751] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:31:46 192.168.122.209 [73657.304962] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73657.304962] Maybe that's fine, but it's worth checking the [73657.304962] config - if there is no relations between the [73657.304962] names, then host name confusion attack is possible. Apr 26 12:31:46 192.168.122.209 [73657.423719] [tempesta fw] Configuration processing is completed. Apr 26 12:31:46 192.168.122.209 [73657.480611] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:31:47 192.168.122.209 [73657.903126] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:31:47 192.168.122.209 [73657.928548] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:31:47 192.168.122.209 [73657.953248] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:31:47 192.168.122.209 [73657.991698] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:31:47 192.168.122.209 [73657.993424] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:31:47 192.168.122.209 [73658.035634] [tempesta fw] Tempesta FW is ready Apr 26 12:31:47 192.168.122.209 [73658.663582] [tdb] Close table 'client0.tdb' Apr 26 12:31:48 192.168.122.209 [73658.848658] [tdb] Close table 'sessions0.tdb' Apr 26 12:31:51 192.168.122.209 [73662.028448] [tdb] Close table 'cache0.tdb' Apr 26 12:31:51 192.168.122.209 [73662.284397] [tdb] Close table 'filter0.tdb' Apr 26 12:31:51 192.168.122.209 [73662.284822] [tempesta fw] modules are stopped Apr 26 12:31:51 192.168.122.209 [73662.467746] [tempesta fw] exiting... Apr 26 12:31:51 192.168.122.209 [73662.612632] [tdb] Shutdown Tempesta DB Apr 26 12:31:52 192.168.122.209 [73663.048199] End test: cache.test_h2_cache_control.TestH2CacheControl.test_max_age_2_in_request_sleep_0 Apr 26 12:31:52 192.168.122.209 [73663.085666] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_max_age_2_in_response_sleep_0 Apr 26 12:31:53 192.168.122.209 [73664.505184] [tdb] Start Tempesta DB Apr 26 12:31:53 192.168.122.209 [73664.646372] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:31:55 192.168.122.209 [73666.061064] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73666.061064] Maybe that's fine, but it's worth checking the [73666.061064] config - if there is no relations between the [73666.061064] names, then host name confusion attack is possible. Apr 26 12:31:55 192.168.122.209 [73666.183760] [tempesta fw] Configuration processing is completed. Apr 26 12:31:55 192.168.122.209 [73666.240699] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:31:55 192.168.122.209 [73666.672285] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:31:55 192.168.122.209 [73666.699312] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:31:55 192.168.122.209 [73666.725925] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:31:56 192.168.122.209 [73666.763829] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:31:56 192.168.122.209 [73666.765593] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:31:56 192.168.122.209 [73666.803767] [tempesta fw] Tempesta FW is ready Apr 26 12:31:56 192.168.122.209 [73667.477498] [tdb] Close table 'client0.tdb' Apr 26 12:31:56 192.168.122.209 [73667.643132] [tdb] Close table 'sessions0.tdb' Apr 26 12:32:00 192.168.122.209 [73670.784399] [tdb] Close table 'cache0.tdb' Apr 26 12:32:00 192.168.122.209 [73671.049112] [tdb] Close table 'filter0.tdb' Apr 26 12:32:00 192.168.122.209 [73671.049536] [tempesta fw] modules are stopped Apr 26 12:32:00 192.168.122.209 [73671.227362] [tempesta fw] exiting... Apr 26 12:32:00 192.168.122.209 [73671.346336] [tdb] Shutdown Tempesta DB Apr 26 12:32:01 192.168.122.209 [73671.775773] End test: cache.test_h2_cache_control.TestH2CacheControl.test_max_age_2_in_response_sleep_0 Apr 26 12:32:01 192.168.122.209 [73671.806344] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_max_stale_1_in_request_sleep_3 Apr 26 12:32:02 192.168.122.209 [73673.168254] [tdb] Start Tempesta DB Apr 26 12:32:02 192.168.122.209 [73673.296596] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:32:04 192.168.122.209 [73674.733200] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73674.733200] Maybe that's fine, but it's worth checking the [73674.733200] config - if there is no relations between the [73674.733200] names, then host name confusion attack is possible. Apr 26 12:32:04 192.168.122.209 [73674.855936] [tempesta fw] Configuration processing is completed. Apr 26 12:32:04 192.168.122.209 [73674.914831] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:32:04 192.168.122.209 [73675.334211] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:32:04 192.168.122.209 [73675.361926] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:32:04 192.168.122.209 [73675.387166] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:32:04 192.168.122.209 [73675.427907] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:32:04 192.168.122.209 [73675.429624] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:32:04 192.168.122.209 [73675.467877] [tempesta fw] Tempesta FW is ready Apr 26 12:32:08 192.168.122.209 [73679.114368] [tdb] Close table 'client0.tdb' Apr 26 12:32:08 192.168.122.209 [73679.286815] [tdb] Close table 'sessions0.tdb' Apr 26 12:32:11 192.168.122.209 [73682.419297] [tdb] Close table 'cache0.tdb' Apr 26 12:32:11 192.168.122.209 [73682.637296] [tdb] Close table 'filter0.tdb' Apr 26 12:32:11 192.168.122.209 [73682.637695] [tempesta fw] modules are stopped Apr 26 12:32:12 192.168.122.209 [73682.835013] [tempesta fw] exiting... Apr 26 12:32:12 192.168.122.209 [73682.981568] [tdb] Shutdown Tempesta DB Apr 26 12:32:12 192.168.122.209 [73683.383321] End test: cache.test_h2_cache_control.TestH2CacheControl.test_max_stale_1_in_request_sleep_3 Apr 26 12:32:12 192.168.122.209 [73683.412960] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_max_stale_5_in_request_sleep_2 Apr 26 12:32:14 192.168.122.209 [73684.805140] [tdb] Start Tempesta DB Apr 26 12:32:14 192.168.122.209 [73684.939516] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:32:16 192.168.122.209 [73686.971488] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73686.971488] Maybe that's fine, but it's worth checking the [73686.971488] config - if there is no relations between the [73686.971488] names, then host name confusion attack is possible. Apr 26 12:32:17 192.168.122.209 [73687.984393] [tempesta fw] Configuration processing is completed. Apr 26 12:32:17 192.168.122.209 [73688.228860] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:32:17 192.168.122.209 [73688.707896] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:32:18 192.168.122.209 [73688.735399] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:32:18 192.168.122.209 [73688.760850] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:32:18 192.168.122.209 [73689.336271] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:32:18 192.168.122.209 [73689.338054] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:32:19 192.168.122.209 [73689.932038] [tempesta fw] Tempesta FW is ready Apr 26 12:32:22 192.168.122.209 [73692.753866] [tdb] Close table 'client0.tdb' Apr 26 12:32:22 192.168.122.209 [73692.939549] [tdb] Close table 'sessions0.tdb' Apr 26 12:32:25 192.168.122.209 [73696.084227] [tdb] Close table 'cache0.tdb' Apr 26 12:32:25 192.168.122.209 [73696.311194] [tdb] Close table 'filter0.tdb' Apr 26 12:32:25 192.168.122.209 [73696.311622] [tempesta fw] modules are stopped Apr 26 12:32:25 192.168.122.209 [73696.508697] [tempesta fw] exiting... Apr 26 12:32:25 192.168.122.209 [73696.646373] [tdb] Shutdown Tempesta DB Apr 26 12:32:26 192.168.122.209 [73697.085299] End test: cache.test_h2_cache_control.TestH2CacheControl.test_max_stale_5_in_request_sleep_2 Apr 26 12:32:26 192.168.122.209 [73697.114678] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_max_stale_5_in_request_sleep_2_from_dynamic_table Apr 26 12:32:27 192.168.122.209 [73698.516460] [tdb] Start Tempesta DB Apr 26 12:32:27 192.168.122.209 [73698.660527] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:32:29 192.168.122.209 [73700.057555] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73700.057555] Maybe that's fine, but it's worth checking the [73700.057555] config - if there is no relations between the [73700.057555] names, then host name confusion attack is possible. Apr 26 12:32:29 192.168.122.209 [73700.188275] [tempesta fw] Configuration processing is completed. Apr 26 12:32:29 192.168.122.209 [73700.244834] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:32:29 192.168.122.209 [73700.666599] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:32:29 192.168.122.209 [73700.692772] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:32:29 192.168.122.209 [73700.718634] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:32:30 192.168.122.209 [73700.760171] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:32:30 192.168.122.209 [73700.761217] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:32:30 192.168.122.209 [73700.804204] [tempesta fw] Tempesta FW is ready Apr 26 12:32:32 192.168.122.209 [73703.460159] [tdb] Close table 'client0.tdb' Apr 26 12:32:32 192.168.122.209 [73703.665465] [tdb] Close table 'sessions0.tdb' Apr 26 12:32:36 192.168.122.209 [73706.808724] [tdb] Close table 'cache0.tdb' Apr 26 12:32:36 192.168.122.209 [73707.051690] [tdb] Close table 'filter0.tdb' Apr 26 12:32:36 192.168.122.209 [73707.052130] [tempesta fw] modules are stopped Apr 26 12:32:36 192.168.122.209 [73707.279822] [tempesta fw] exiting... Apr 26 12:32:36 192.168.122.209 [73707.414284] [tdb] Shutdown Tempesta DB Apr 26 12:32:37 192.168.122.209 [73707.826820] End test: cache.test_h2_cache_control.TestH2CacheControl.test_max_stale_5_in_request_sleep_2_from_dynamic_table Apr 26 12:32:37 192.168.122.209 [73707.849493] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_max_stale_in_request_sleep_2 Apr 26 12:32:38 192.168.122.209 [73709.247824] [tdb] Start Tempesta DB Apr 26 12:32:38 192.168.122.209 [73709.378716] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:32:40 192.168.122.209 [73710.749593] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73710.749593] Maybe that's fine, but it's worth checking the [73710.749593] config - if there is no relations between the [73710.749593] names, then host name confusion attack is possible. Apr 26 12:32:40 192.168.122.209 [73710.868374] [tempesta fw] Configuration processing is completed. Apr 26 12:32:40 192.168.122.209 [73710.927602] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:32:40 192.168.122.209 [73711.338492] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:32:40 192.168.122.209 [73711.365612] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:32:40 192.168.122.209 [73711.391744] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:32:40 192.168.122.209 [73711.448371] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:32:40 192.168.122.209 [73711.450114] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:32:40 192.168.122.209 [73711.496323] [tempesta fw] Tempesta FW is ready Apr 26 12:32:43 192.168.122.209 [73714.164098] [tdb] Close table 'client0.tdb' Apr 26 12:32:43 192.168.122.209 [73714.350584] [tdb] Close table 'sessions0.tdb' Apr 26 12:32:46 192.168.122.209 [73717.536682] [tdb] Close table 'cache0.tdb' Apr 26 12:32:47 192.168.122.209 [73717.783037] [tdb] Close table 'filter0.tdb' Apr 26 12:32:47 192.168.122.209 [73717.783479] [tempesta fw] modules are stopped Apr 26 12:32:47 192.168.122.209 [73717.979968] [tempesta fw] exiting... Apr 26 12:32:47 192.168.122.209 [73718.111005] [tdb] Shutdown Tempesta DB Apr 26 12:32:47 192.168.122.209 [73718.482949] End test: cache.test_h2_cache_control.TestH2CacheControl.test_max_stale_in_request_sleep_2 Apr 26 12:32:47 192.168.122.209 [73718.516036] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_min_fresh_1_in_request_sleep_0 Apr 26 12:32:49 192.168.122.209 [73719.825810] [tdb] Start Tempesta DB Apr 26 12:32:49 192.168.122.209 [73719.950916] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:32:50 192.168.122.209 [73721.405789] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73721.405789] Maybe that's fine, but it's worth checking the [73721.405789] config - if there is no relations between the [73721.405789] names, then host name confusion attack is possible. Apr 26 12:32:50 192.168.122.209 [73721.544548] [tempesta fw] Configuration processing is completed. Apr 26 12:32:50 192.168.122.209 [73721.596517] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:32:51 192.168.122.209 [73722.004808] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:32:51 192.168.122.209 [73722.032213] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:32:51 192.168.122.209 [73722.057762] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:32:51 192.168.122.209 [73722.112509] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:32:51 192.168.122.209 [73722.114257] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:32:51 192.168.122.209 [73722.160466] [tempesta fw] Tempesta FW is ready Apr 26 12:32:52 192.168.122.209 [73722.806606] [tdb] Close table 'client0.tdb' Apr 26 12:32:52 192.168.122.209 [73722.989658] [tdb] Close table 'sessions0.tdb' Apr 26 12:32:55 192.168.122.209 [73726.110062] [tdb] Close table 'cache0.tdb' Apr 26 12:32:55 192.168.122.209 [73726.370408] [tdb] Close table 'filter0.tdb' Apr 26 12:32:55 192.168.122.209 [73726.370853] [tempesta fw] modules are stopped Apr 26 12:32:55 192.168.122.209 [73726.578171] [tempesta fw] exiting... Apr 26 12:32:55 192.168.122.209 [73726.707057] [tdb] Shutdown Tempesta DB Apr 26 12:32:56 192.168.122.209 [73727.047594] End test: cache.test_h2_cache_control.TestH2CacheControl.test_min_fresh_1_in_request_sleep_0 Apr 26 12:32:56 192.168.122.209 [73727.087263] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_min_fresh_1_in_request_sleep_0_from_dynamic_table Apr 26 12:32:57 192.168.122.209 [73728.547941] [tdb] Start Tempesta DB Apr 26 12:32:57 192.168.122.209 [73728.693919] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:32:59 192.168.122.209 [73730.105862] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73730.105862] Maybe that's fine, but it's worth checking the [73730.105862] config - if there is no relations between the [73730.105862] names, then host name confusion attack is possible. Apr 26 12:32:59 192.168.122.209 [73730.236646] [tempesta fw] Configuration processing is completed. Apr 26 12:32:59 192.168.122.209 [73730.298740] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:32:59 192.168.122.209 [73730.718053] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:33:00 192.168.122.209 [73730.744136] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:33:00 192.168.122.209 [73730.769380] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:33:00 192.168.122.209 [73730.808608] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:33:00 192.168.122.209 [73730.810344] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:33:00 192.168.122.209 [73730.864580] [tempesta fw] Tempesta FW is ready Apr 26 12:33:00 192.168.122.209 [73731.511039] [tdb] Close table 'client0.tdb' Apr 26 12:33:00 192.168.122.209 [73731.725746] [tdb] Close table 'sessions0.tdb' Apr 26 12:33:04 192.168.122.209 [73734.832405] [tdb] Close table 'cache0.tdb' Apr 26 12:33:04 192.168.122.209 [73735.123850] [tdb] Close table 'filter0.tdb' Apr 26 12:33:04 192.168.122.209 [73735.124261] [tempesta fw] modules are stopped Apr 26 12:33:04 192.168.122.209 [73735.300618] [tempesta fw] exiting... Apr 26 12:33:04 192.168.122.209 [73735.436291] [tdb] Shutdown Tempesta DB Apr 26 12:33:05 192.168.122.209 [73735.861532] End test: cache.test_h2_cache_control.TestH2CacheControl.test_min_fresh_1_in_request_sleep_0_from_dynamic_table Apr 26 12:33:05 192.168.122.209 [73735.896889] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_min_fresh_2_in_request_sleep_2 Apr 26 12:33:06 192.168.122.209 [73737.298765] [tdb] Start Tempesta DB Apr 26 12:33:06 192.168.122.209 [73737.432745] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:33:08 192.168.122.209 [73738.926051] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73738.926051] Maybe that's fine, but it's worth checking the [73738.926051] config - if there is no relations between the [73738.926051] names, then host name confusion attack is possible. Apr 26 12:33:08 192.168.122.209 [73739.044819] [tempesta fw] Configuration processing is completed. Apr 26 12:33:08 192.168.122.209 [73739.102330] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:33:08 192.168.122.209 [73739.529976] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:33:08 192.168.122.209 [73739.556989] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:33:08 192.168.122.209 [73739.583427] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:33:08 192.168.122.209 [73739.640714] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:33:08 192.168.122.209 [73739.642464] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:33:08 192.168.122.209 [73739.680694] [tempesta fw] Tempesta FW is ready Apr 26 12:33:11 192.168.122.209 [73742.277551] [tdb] Close table 'client0.tdb' Apr 26 12:33:11 192.168.122.209 [73742.457785] [tdb] Close table 'sessions0.tdb' Apr 26 12:33:14 192.168.122.209 [73745.612386] [tdb] Close table 'cache0.tdb' Apr 26 12:33:15 192.168.122.209 [73745.859069] [tdb] Close table 'filter0.tdb' Apr 26 12:33:15 192.168.122.209 [73745.860247] [tempesta fw] modules are stopped Apr 26 12:33:15 192.168.122.209 [73746.281380] [tempesta fw] exiting... Apr 26 12:33:15 192.168.122.209 [73746.396184] [tdb] Shutdown Tempesta DB Apr 26 12:33:16 192.168.122.209 [73746.788491] End test: cache.test_h2_cache_control.TestH2CacheControl.test_min_fresh_2_in_request_sleep_2 Apr 26 12:33:16 192.168.122.209 [73746.821363] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_must_revalidate_in_response_from_cache Apr 26 12:33:17 192.168.122.209 [73748.151847] [tdb] Start Tempesta DB Apr 26 12:33:17 192.168.122.209 [73748.287759] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:33:18 192.168.122.209 [73749.638098] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73749.638098] Maybe that's fine, but it's worth checking the [73749.638098] config - if there is no relations between the [73749.638098] names, then host name confusion attack is possible. Apr 26 12:33:19 192.168.122.209 [73749.760875] [tempesta fw] Configuration processing is completed. Apr 26 12:33:19 192.168.122.209 [73749.817948] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:33:19 192.168.122.209 [73750.229273] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:33:19 192.168.122.209 [73750.255351] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:33:19 192.168.122.209 [73750.281140] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:33:19 192.168.122.209 [73750.344853] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:33:19 192.168.122.209 [73750.346600] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:33:19 192.168.122.209 [73750.400798] [tempesta fw] Tempesta FW is ready Apr 26 12:33:20 192.168.122.209 [73751.057278] [tdb] Close table 'client0.tdb' Apr 26 12:33:20 192.168.122.209 [73751.232075] [tdb] Close table 'sessions0.tdb' Apr 26 12:33:23 192.168.122.209 [73754.363231] [tdb] Close table 'cache0.tdb' Apr 26 12:33:23 192.168.122.209 [73754.596931] [tdb] Close table 'filter0.tdb' Apr 26 12:33:23 192.168.122.209 [73754.597363] [tempesta fw] modules are stopped Apr 26 12:33:24 192.168.122.209 [73754.784731] [tempesta fw] exiting... Apr 26 12:33:24 192.168.122.209 [73754.904445] [tdb] Shutdown Tempesta DB Apr 26 12:33:24 192.168.122.209 [73755.307352] End test: cache.test_h2_cache_control.TestH2CacheControl.test_must_revalidate_in_response_from_cache Apr 26 12:33:24 192.168.122.209 [73755.341393] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_must_revalidate_in_response_max_stale_in_request_from_cache Apr 26 12:33:25 192.168.122.209 [73756.628286] [tdb] Start Tempesta DB Apr 26 12:33:26 192.168.122.209 [73756.768610] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:33:27 192.168.122.209 [73758.210219] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73758.210219] Maybe that's fine, but it's worth checking the [73758.210219] config - if there is no relations between the [73758.210219] names, then host name confusion attack is possible. Apr 26 12:33:27 192.168.122.209 [73758.336974] [tempesta fw] Configuration processing is completed. Apr 26 12:33:27 192.168.122.209 [73758.388095] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:33:28 192.168.122.209 [73758.811711] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:33:28 192.168.122.209 [73758.838248] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:33:28 192.168.122.209 [73758.864760] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:33:28 192.168.122.209 [73758.908970] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:33:28 192.168.122.209 [73758.910727] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:33:28 192.168.122.209 [73758.960920] [tempesta fw] Tempesta FW is ready Apr 26 12:33:28 192.168.122.209 [73759.627388] [tdb] Close table 'client0.tdb' Apr 26 12:33:29 192.168.122.209 [73759.824883] [tdb] Close table 'sessions0.tdb' Apr 26 12:33:32 192.168.122.209 [73762.973876] [tdb] Close table 'cache0.tdb' Apr 26 12:33:32 192.168.122.209 [73763.242430] [tdb] Close table 'filter0.tdb' Apr 26 12:33:32 192.168.122.209 [73763.242857] [tempesta fw] modules are stopped Apr 26 12:33:32 192.168.122.209 [73763.445137] [tempesta fw] exiting... Apr 26 12:33:32 192.168.122.209 [73763.584266] [tdb] Shutdown Tempesta DB Apr 26 12:33:33 192.168.122.209 [73763.929744] End test: cache.test_h2_cache_control.TestH2CacheControl.test_must_revalidate_in_response_max_stale_in_request_from_cache Apr 26 12:33:33 192.168.122.209 [73764.018485] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_must_revalidate_in_response_max_stale_in_request_not_from_cache Apr 26 12:33:34 192.168.122.209 [73765.311176] [tdb] Start Tempesta DB Apr 26 12:33:34 192.168.122.209 [73765.448304] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:33:36 192.168.122.209 [73766.794325] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73766.794325] Maybe that's fine, but it's worth checking the [73766.794325] config - if there is no relations between the [73766.794325] names, then host name confusion attack is possible. Apr 26 12:33:36 192.168.122.209 [73766.921097] [tempesta fw] Configuration processing is completed. Apr 26 12:33:36 192.168.122.209 [73766.973396] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:33:36 192.168.122.209 [73767.395860] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:33:36 192.168.122.209 [73767.422334] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:33:36 192.168.122.209 [73767.449237] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:33:36 192.168.122.209 [73767.533091] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:33:36 192.168.122.209 [73767.534836] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:33:36 192.168.122.209 [73767.573013] [tempesta fw] Tempesta FW is ready Apr 26 12:33:39 192.168.122.209 [73770.213362] [tdb] Close table 'client0.tdb' Apr 26 12:33:39 192.168.122.209 [73770.400050] [tdb] Close table 'sessions0.tdb' Apr 26 12:33:42 192.168.122.209 [73773.518337] [tdb] Close table 'cache0.tdb' Apr 26 12:33:42 192.168.122.209 [73773.724929] [tdb] Close table 'filter0.tdb' Apr 26 12:33:42 192.168.122.209 [73773.725378] [tempesta fw] modules are stopped Apr 26 12:33:43 192.168.122.209 [73773.913415] [tempesta fw] exiting... Apr 26 12:33:43 192.168.122.209 [73774.063019] [tdb] Shutdown Tempesta DB Apr 26 12:33:43 192.168.122.209 [73774.484673] End test: cache.test_h2_cache_control.TestH2CacheControl.test_must_revalidate_in_response_max_stale_in_request_not_from_cache Apr 26 12:33:43 192.168.122.209 [73774.523306] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_must_revalidate_in_response_not_from_cache Apr 26 12:33:45 192.168.122.209 [73775.897050] [tdb] Start Tempesta DB Apr 26 12:33:45 192.168.122.209 [73776.039516] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:33:46 192.168.122.209 [73777.394534] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73777.394534] Maybe that's fine, but it's worth checking the [73777.394534] config - if there is no relations between the [73777.394534] names, then host name confusion attack is possible. Apr 26 12:33:46 192.168.122.209 [73777.517238] [tempesta fw] Configuration processing is completed. Apr 26 12:33:46 192.168.122.209 [73777.579331] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:33:47 192.168.122.209 [73778.010878] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:33:47 192.168.122.209 [73778.036859] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:33:47 192.168.122.209 [73778.062305] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:33:47 192.168.122.209 [73778.109201] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:33:47 192.168.122.209 [73778.110963] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:33:47 192.168.122.209 [73778.149171] [tempesta fw] Tempesta FW is ready Apr 26 12:33:50 192.168.122.209 [73780.811856] [tdb] Close table 'client0.tdb' Apr 26 12:33:50 192.168.122.209 [73780.998379] [tdb] Close table 'sessions0.tdb' Apr 26 12:33:53 192.168.122.209 [73784.146629] [tdb] Close table 'cache0.tdb' Apr 26 12:33:53 192.168.122.209 [73784.398324] [tdb] Close table 'filter0.tdb' Apr 26 12:33:53 192.168.122.209 [73784.398733] [tempesta fw] modules are stopped Apr 26 12:33:53 192.168.122.209 [73784.605699] [tempesta fw] exiting... Apr 26 12:33:53 192.168.122.209 [73784.723171] [tdb] Shutdown Tempesta DB Apr 26 12:33:54 192.168.122.209 [73785.141457] End test: cache.test_h2_cache_control.TestH2CacheControl.test_must_revalidate_in_response_not_from_cache Apr 26 12:33:54 192.168.122.209 [73785.181736] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_no_cache_in_first_request Apr 26 12:33:55 192.168.122.209 [73786.502042] [tdb] Start Tempesta DB Apr 26 12:33:55 192.168.122.209 [73786.622427] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:33:57 192.168.122.209 [73788.014580] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73788.014580] Maybe that's fine, but it's worth checking the [73788.014580] config - if there is no relations between the [73788.014580] names, then host name confusion attack is possible. Apr 26 12:33:57 192.168.122.209 [73788.137349] [tempesta fw] Configuration processing is completed. Apr 26 12:33:57 192.168.122.209 [73788.190138] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:33:57 192.168.122.209 [73788.603936] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:33:57 192.168.122.209 [73788.630178] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:33:57 192.168.122.209 [73788.656161] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:33:57 192.168.122.209 [73788.733346] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:33:58 192.168.122.209 [73788.735072] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:33:58 192.168.122.209 [73788.773305] [tempesta fw] Tempesta FW is ready Apr 26 12:33:58 192.168.122.209 [73789.446882] [tdb] Close table 'client0.tdb' Apr 26 12:33:58 192.168.122.209 [73789.628284] [tdb] Close table 'sessions0.tdb' Apr 26 12:34:02 192.168.122.209 [73792.748414] [tdb] Close table 'cache0.tdb' Apr 26 12:34:02 192.168.122.209 [73792.976957] [tdb] Close table 'filter0.tdb' Apr 26 12:34:02 192.168.122.209 [73792.977414] [tempesta fw] modules are stopped Apr 26 12:34:02 192.168.122.209 [73793.190671] [tempesta fw] exiting... Apr 26 12:34:02 192.168.122.209 [73793.303391] [tdb] Shutdown Tempesta DB Apr 26 12:34:03 192.168.122.209 [73793.761295] End test: cache.test_h2_cache_control.TestH2CacheControl.test_no_cache_in_first_request Apr 26 12:34:03 192.168.122.209 [73793.791319] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_no_cache_in_response Apr 26 12:34:04 192.168.122.209 [73795.127221] [tdb] Start Tempesta DB Apr 26 12:34:04 192.168.122.209 [73795.262842] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:34:05 192.168.122.209 [73796.690808] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73796.690808] Maybe that's fine, but it's worth checking the [73796.690808] config - if there is no relations between the [73796.690808] names, then host name confusion attack is possible. Apr 26 12:34:06 192.168.122.209 [73796.809478] [tempesta fw] Configuration processing is completed. Apr 26 12:34:06 192.168.122.209 [73796.864351] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:34:06 192.168.122.209 [73797.268615] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:34:06 192.168.122.209 [73797.295090] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:34:06 192.168.122.209 [73797.322669] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:34:06 192.168.122.209 [73797.361454] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:34:06 192.168.122.209 [73797.363186] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:34:06 192.168.122.209 [73797.405388] [tempesta fw] Tempesta FW is ready Apr 26 12:34:07 192.168.122.209 [73798.055073] [tdb] Close table 'client0.tdb' Apr 26 12:34:07 192.168.122.209 [73798.238941] [tdb] Close table 'sessions0.tdb' Apr 26 12:34:10 192.168.122.209 [73801.449682] [tdb] Close table 'cache0.tdb' Apr 26 12:34:10 192.168.122.209 [73801.704938] [tdb] Close table 'filter0.tdb' Apr 26 12:34:10 192.168.122.209 [73801.705412] [tempesta fw] modules are stopped Apr 26 12:34:11 192.168.122.209 [73801.874952] [tempesta fw] exiting... Apr 26 12:34:11 192.168.122.209 [73802.004310] [tdb] Shutdown Tempesta DB Apr 26 12:34:11 192.168.122.209 [73802.416531] End test: cache.test_h2_cache_control.TestH2CacheControl.test_no_cache_in_response Apr 26 12:34:11 192.168.122.209 [73802.440080] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_no_cache_in_second_request Apr 26 12:34:13 192.168.122.209 [73803.810840] [tdb] Start Tempesta DB Apr 26 12:34:13 192.168.122.209 [73803.954088] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:34:14 192.168.122.209 [73805.354834] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73805.354834] Maybe that's fine, but it's worth checking the [73805.354834] config - if there is no relations between the [73805.354834] names, then host name confusion attack is possible. Apr 26 12:34:14 192.168.122.209 [73805.497585] [tempesta fw] Configuration processing is completed. Apr 26 12:34:14 192.168.122.209 [73805.553586] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:34:15 192.168.122.209 [73805.980751] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:34:15 192.168.122.209 [73806.015646] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:34:15 192.168.122.209 [73806.041754] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:34:15 192.168.122.209 [73806.093573] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:34:15 192.168.122.209 [73806.095315] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:34:15 192.168.122.209 [73806.133499] [tempesta fw] Tempesta FW is ready Apr 26 12:34:16 192.168.122.209 [73806.798932] [tdb] Close table 'client0.tdb' Apr 26 12:34:16 192.168.122.209 [73806.983651] [tdb] Close table 'sessions0.tdb' Apr 26 12:34:19 192.168.122.209 [73810.096569] [tdb] Close table 'cache0.tdb' Apr 26 12:34:19 192.168.122.209 [73810.345104] [tdb] Close table 'filter0.tdb' Apr 26 12:34:19 192.168.122.209 [73810.345565] [tempesta fw] modules are stopped Apr 26 12:34:19 192.168.122.209 [73810.520060] [tempesta fw] exiting... Apr 26 12:34:19 192.168.122.209 [73810.669004] [tdb] Shutdown Tempesta DB Apr 26 12:34:20 192.168.122.209 [73811.054266] End test: cache.test_h2_cache_control.TestH2CacheControl.test_no_cache_in_second_request Apr 26 12:34:20 192.168.122.209 [73811.141847] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_no_store_in_first_and_second_request_from_dynamic_table Apr 26 12:34:21 192.168.122.209 [73812.562519] [tdb] Start Tempesta DB Apr 26 12:34:21 192.168.122.209 [73812.691493] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:34:23 192.168.122.209 [73814.026984] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73814.026984] Maybe that's fine, but it's worth checking the [73814.026984] config - if there is no relations between the [73814.026984] names, then host name confusion attack is possible. Apr 26 12:34:23 192.168.122.209 [73814.141715] [tempesta fw] Configuration processing is completed. Apr 26 12:34:23 192.168.122.209 [73814.198969] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:34:23 192.168.122.209 [73814.622956] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:34:23 192.168.122.209 [73814.650368] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:34:23 192.168.122.209 [73814.676542] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:34:23 192.168.122.209 [73814.721536] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:34:23 192.168.122.209 [73814.722418] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:34:24 192.168.122.209 [73814.765559] [tempesta fw] Tempesta FW is ready Apr 26 12:34:24 192.168.122.209 [73815.484276] [tdb] Close table 'client0.tdb' Apr 26 12:34:24 192.168.122.209 [73815.672479] [tdb] Close table 'sessions0.tdb' Apr 26 12:34:28 192.168.122.209 [73818.816181] [tdb] Close table 'cache0.tdb' Apr 26 12:34:28 192.168.122.209 [73819.052178] [tdb] Close table 'filter0.tdb' Apr 26 12:34:28 192.168.122.209 [73819.052590] [tempesta fw] modules are stopped Apr 26 12:34:28 192.168.122.209 [73819.242062] [tempesta fw] exiting... Apr 26 12:34:28 192.168.122.209 [73819.363969] [tdb] Shutdown Tempesta DB Apr 26 12:34:29 192.168.122.209 [73819.801360] End test: cache.test_h2_cache_control.TestH2CacheControl.test_no_store_in_first_and_second_request_from_dynamic_table Apr 26 12:34:29 192.168.122.209 [73819.831916] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_no_store_in_first_request Apr 26 12:34:30 192.168.122.209 [73821.248543] [tdb] Start Tempesta DB Apr 26 12:34:30 192.168.122.209 [73821.393283] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:34:32 192.168.122.209 [73822.731070] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73822.731070] Maybe that's fine, but it's worth checking the [73822.731070] config - if there is no relations between the [73822.731070] names, then host name confusion attack is possible. Apr 26 12:34:32 192.168.122.209 [73822.845833] [tempesta fw] Configuration processing is completed. Apr 26 12:34:32 192.168.122.209 [73822.910273] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:34:32 192.168.122.209 [73823.331176] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:34:32 192.168.122.209 [73823.358811] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:34:32 192.168.122.209 [73823.384950] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:34:32 192.168.122.209 [73823.441777] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:34:32 192.168.122.209 [73823.443513] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:34:32 192.168.122.209 [73823.477747] [tempesta fw] Tempesta FW is ready Apr 26 12:34:33 192.168.122.209 [73824.163631] [tdb] Close table 'client0.tdb' Apr 26 12:34:33 192.168.122.209 [73824.347154] [tdb] Close table 'sessions0.tdb' Apr 26 12:34:36 192.168.122.209 [73827.455733] [tdb] Close table 'cache0.tdb' Apr 26 12:34:36 192.168.122.209 [73827.701475] [tdb] Close table 'filter0.tdb' Apr 26 12:34:36 192.168.122.209 [73827.701918] [tempesta fw] modules are stopped Apr 26 12:34:37 192.168.122.209 [73827.901965] [tempesta fw] exiting... Apr 26 12:34:37 192.168.122.209 [73828.043873] [tdb] Shutdown Tempesta DB Apr 26 12:34:37 192.168.122.209 [73828.419119] End test: cache.test_h2_cache_control.TestH2CacheControl.test_no_store_in_first_request Apr 26 12:34:37 192.168.122.209 [73828.444398] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_no_store_in_response Apr 26 12:34:39 192.168.122.209 [73829.805621] [tdb] Start Tempesta DB Apr 26 12:34:39 192.168.122.209 [73829.936495] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:34:40 192.168.122.209 [73831.239233] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73831.239233] Maybe that's fine, but it's worth checking the [73831.239233] config - if there is no relations between the [73831.239233] names, then host name confusion attack is possible. Apr 26 12:34:40 192.168.122.209 [73831.357971] [tempesta fw] Configuration processing is completed. Apr 26 12:34:40 192.168.122.209 [73831.423934] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:34:41 192.168.122.209 [73831.844642] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:34:41 192.168.122.209 [73831.870832] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:34:41 192.168.122.209 [73831.896934] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:34:41 192.168.122.209 [73831.937904] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:34:41 192.168.122.209 [73831.939655] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:34:41 192.168.122.209 [73831.989835] [tempesta fw] Tempesta FW is ready Apr 26 12:34:41 192.168.122.209 [73832.575567] [tdb] Close table 'client0.tdb' Apr 26 12:34:42 192.168.122.209 [73832.772986] [tdb] Close table 'sessions0.tdb' Apr 26 12:34:45 192.168.122.209 [73835.894966] [tdb] Close table 'cache0.tdb' Apr 26 12:34:45 192.168.122.209 [73836.130280] [tdb] Close table 'filter0.tdb' Apr 26 12:34:45 192.168.122.209 [73836.130705] [tempesta fw] modules are stopped Apr 26 12:34:45 192.168.122.209 [73836.307504] [tempesta fw] exiting... Apr 26 12:34:45 192.168.122.209 [73836.433050] [tdb] Shutdown Tempesta DB Apr 26 12:34:46 192.168.122.209 [73836.823107] End test: cache.test_h2_cache_control.TestH2CacheControl.test_no_store_in_response Apr 26 12:34:46 192.168.122.209 [73836.850943] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_no_store_in_second_request Apr 26 12:34:47 192.168.122.209 [73838.214335] [tdb] Start Tempesta DB Apr 26 12:34:47 192.168.122.209 [73838.354058] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:34:49 192.168.122.209 [73839.747736] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73839.747736] Maybe that's fine, but it's worth checking the [73839.747736] config - if there is no relations between the [73839.747736] names, then host name confusion attack is possible. Apr 26 12:34:49 192.168.122.209 [73839.890024] [tempesta fw] Configuration processing is completed. Apr 26 12:34:49 192.168.122.209 [73839.946070] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:34:49 192.168.122.209 [73840.349326] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:34:49 192.168.122.209 [73840.375233] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:34:49 192.168.122.209 [73840.400289] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:34:49 192.168.122.209 [73840.445943] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:34:49 192.168.122.209 [73840.447668] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:34:49 192.168.122.209 [73840.493959] [tempesta fw] Tempesta FW is ready Apr 26 12:34:50 192.168.122.209 [73841.143046] [tdb] Close table 'client0.tdb' Apr 26 12:34:50 192.168.122.209 [73841.330959] [tdb] Close table 'sessions0.tdb' Apr 26 12:34:53 192.168.122.209 [73844.473611] [tdb] Close table 'cache0.tdb' Apr 26 12:34:53 192.168.122.209 [73844.735478] [tdb] Close table 'filter0.tdb' Apr 26 12:34:53 192.168.122.209 [73844.735878] [tempesta fw] modules are stopped Apr 26 12:34:54 192.168.122.209 [73844.942237] [tempesta fw] exiting... Apr 26 12:34:54 192.168.122.209 [73845.074707] [tdb] Shutdown Tempesta DB Apr 26 12:34:54 192.168.122.209 [73845.537268] End test: cache.test_h2_cache_control.TestH2CacheControl.test_no_store_in_second_request Apr 26 12:34:54 192.168.122.209 [73845.566493] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_only_if_cached_in_request_from_cache Apr 26 12:34:56 192.168.122.209 [73846.992400] [tdb] Start Tempesta DB Apr 26 12:34:56 192.168.122.209 [73847.124383] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:34:57 192.168.122.209 [73848.563339] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73848.563339] Maybe that's fine, but it's worth checking the [73848.563339] config - if there is no relations between the [73848.563339] names, then host name confusion attack is possible. Apr 26 12:34:57 192.168.122.209 [73848.682115] [tempesta fw] Configuration processing is completed. Apr 26 12:34:57 192.168.122.209 [73848.732529] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:34:58 192.168.122.209 [73849.142426] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:34:58 192.168.122.209 [73849.168228] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:34:58 192.168.122.209 [73849.193428] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:34:58 192.168.122.209 [73849.234110] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:34:58 192.168.122.209 [73849.235828] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:34:58 192.168.122.209 [73849.278080] [tempesta fw] Tempesta FW is ready Apr 26 12:34:59 192.168.122.209 [73849.933671] [tdb] Close table 'client0.tdb' Apr 26 12:34:59 192.168.122.209 [73850.115871] [tdb] Close table 'sessions0.tdb' Apr 26 12:35:02 192.168.122.209 [73853.257237] [tdb] Close table 'cache0.tdb' Apr 26 12:35:02 192.168.122.209 [73853.511906] [tdb] Close table 'filter0.tdb' Apr 26 12:35:02 192.168.122.209 [73853.512308] [tempesta fw] modules are stopped Apr 26 12:35:02 192.168.122.209 [73853.702730] [tempesta fw] exiting... Apr 26 12:35:03 192.168.122.209 [73853.846372] [tdb] Shutdown Tempesta DB Apr 26 12:35:03 192.168.122.209 [73854.211781] End test: cache.test_h2_cache_control.TestH2CacheControl.test_only_if_cached_in_request_from_cache Apr 26 12:35:03 192.168.122.209 [73854.240314] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_only_if_cached_in_request_from_cache_from_dynamic_table Apr 26 12:35:04 192.168.122.209 [73855.612102] [tdb] Start Tempesta DB Apr 26 12:35:05 192.168.122.209 [73855.754092] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:35:06 192.168.122.209 [73857.159460] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73857.159460] Maybe that's fine, but it's worth checking the [73857.159460] config - if there is no relations between the [73857.159460] names, then host name confusion attack is possible. Apr 26 12:35:06 192.168.122.209 [73857.278212] [tempesta fw] Configuration processing is completed. Apr 26 12:35:06 192.168.122.209 [73857.328986] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:35:07 192.168.122.209 [73857.762270] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:35:07 192.168.122.209 [73857.788351] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:35:07 192.168.122.209 [73857.813925] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:35:07 192.168.122.209 [73857.862246] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:35:07 192.168.122.209 [73857.864000] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:35:07 192.168.122.209 [73857.910175] [tempesta fw] Tempesta FW is ready Apr 26 12:35:07 192.168.122.209 [73858.538995] [tdb] Close table 'client0.tdb' Apr 26 12:35:07 192.168.122.209 [73858.719035] [tdb] Close table 'sessions0.tdb' Apr 26 12:35:11 192.168.122.209 [73861.875224] [tdb] Close table 'cache0.tdb' Apr 26 12:35:11 192.168.122.209 [73862.129496] [tdb] Close table 'filter0.tdb' Apr 26 12:35:11 192.168.122.209 [73862.129940] [tempesta fw] modules are stopped Apr 26 12:35:11 192.168.122.209 [73862.306589] [tempesta fw] exiting... Apr 26 12:35:11 192.168.122.209 [73862.425740] [tdb] Shutdown Tempesta DB Apr 26 12:35:12 192.168.122.209 [73862.838685] End test: cache.test_h2_cache_control.TestH2CacheControl.test_only_if_cached_in_request_from_cache_from_dynamic_table Apr 26 12:35:12 192.168.122.209 [73862.867351] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_only_if_cached_in_request_not_from_cache Apr 26 12:35:13 192.168.122.209 [73864.269978] [tdb] Start Tempesta DB Apr 26 12:35:13 192.168.122.209 [73864.401688] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:35:15 192.168.122.209 [73865.783569] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73865.783569] Maybe that's fine, but it's worth checking the [73865.783569] config - if there is no relations between the [73865.783569] names, then host name confusion attack is possible. Apr 26 12:35:15 192.168.122.209 [73865.922349] [tempesta fw] Configuration processing is completed. Apr 26 12:35:15 192.168.122.209 [73865.972829] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:35:15 192.168.122.209 [73866.386939] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:35:15 192.168.122.209 [73866.413196] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:35:15 192.168.122.209 [73866.439801] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:35:15 192.168.122.209 [73866.482353] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:35:15 192.168.122.209 [73866.483686] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:35:15 192.168.122.209 [73866.526282] [tempesta fw] Tempesta FW is ready Apr 26 12:35:17 192.168.122.209 [73868.720777] [tempesta fw] Warning: resource not cached, status 504: 192.168.122.196 Apr 26 12:35:18 192.168.122.209 [73869.189895] [tdb] Close table 'client0.tdb' Apr 26 12:35:18 192.168.122.209 [73869.392478] [tdb] Close table 'sessions0.tdb' Apr 26 12:35:21 192.168.122.209 [73872.513596] [tdb] Close table 'cache0.tdb' Apr 26 12:35:22 192.168.122.209 [73872.779109] [tdb] Close table 'filter0.tdb' Apr 26 12:35:22 192.168.122.209 [73872.779517] [tempesta fw] modules are stopped Apr 26 12:35:22 192.168.122.209 [73872.971088] [tempesta fw] exiting... Apr 26 12:35:22 192.168.122.209 [73873.132488] [tdb] Shutdown Tempesta DB Apr 26 12:35:22 192.168.122.209 [73873.495874] End test: cache.test_h2_cache_control.TestH2CacheControl.test_only_if_cached_in_request_not_from_cache Apr 26 12:35:22 192.168.122.209 [73873.524202] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_private_in_response Apr 26 12:35:24 192.168.122.209 [73874.976571] [tdb] Start Tempesta DB Apr 26 12:35:24 192.168.122.209 [73875.113998] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:35:25 192.168.122.209 [73876.495759] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73876.495759] Maybe that's fine, but it's worth checking the [73876.495759] config - if there is no relations between the [73876.495759] names, then host name confusion attack is possible. Apr 26 12:35:25 192.168.122.209 [73876.606499] [tempesta fw] Configuration processing is completed. Apr 26 12:35:25 192.168.122.209 [73876.662816] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:35:26 192.168.122.209 [73877.084368] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:35:26 192.168.122.209 [73877.120178] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:35:26 192.168.122.209 [73877.144834] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:35:26 192.168.122.209 [73877.186475] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:35:26 192.168.122.209 [73877.188228] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:35:26 192.168.122.209 [73877.226416] [tempesta fw] Tempesta FW is ready Apr 26 12:35:27 192.168.122.209 [73877.924040] [tdb] Close table 'client0.tdb' Apr 26 12:35:27 192.168.122.209 [73878.109794] [tdb] Close table 'sessions0.tdb' Apr 26 12:35:30 192.168.122.209 [73881.236257] [tdb] Close table 'cache0.tdb' Apr 26 12:35:30 192.168.122.209 [73881.487127] [tdb] Close table 'filter0.tdb' Apr 26 12:35:30 192.168.122.209 [73881.487553] [tempesta fw] modules are stopped Apr 26 12:35:30 192.168.122.209 [73881.666818] [tempesta fw] exiting... Apr 26 12:35:31 192.168.122.209 [73881.803405] [tdb] Shutdown Tempesta DB Apr 26 12:35:31 192.168.122.209 [73882.246342] End test: cache.test_h2_cache_control.TestH2CacheControl.test_private_in_response Apr 26 12:35:31 192.168.122.209 [73882.325601] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_proxy_revalidate_in_response_from_cache Apr 26 12:35:33 192.168.122.209 [73883.743651] [tdb] Start Tempesta DB Apr 26 12:35:33 192.168.122.209 [73883.872586] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:35:34 192.168.122.209 [73885.252074] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73885.252074] Maybe that's fine, but it's worth checking the [73885.252074] config - if there is no relations between the [73885.252074] names, then host name confusion attack is possible. Apr 26 12:35:34 192.168.122.209 [73885.366634] [tempesta fw] Configuration processing is completed. Apr 26 12:35:34 192.168.122.209 [73885.425499] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:35:35 192.168.122.209 [73885.879438] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:35:35 192.168.122.209 [73885.907587] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:35:35 192.168.122.209 [73885.935181] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:35:35 192.168.122.209 [73885.974621] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:35:35 192.168.122.209 [73885.976354] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:35:35 192.168.122.209 [73886.018525] [tempesta fw] Tempesta FW is ready Apr 26 12:35:35 192.168.122.209 [73886.695965] [tdb] Close table 'client0.tdb' Apr 26 12:35:36 192.168.122.209 [73886.887486] [tdb] Close table 'sessions0.tdb' Apr 26 12:35:39 192.168.122.209 [73890.008236] [tdb] Close table 'cache0.tdb' Apr 26 12:35:39 192.168.122.209 [73890.302586] [tdb] Close table 'filter0.tdb' Apr 26 12:35:39 192.168.122.209 [73890.303028] [tempesta fw] modules are stopped Apr 26 12:35:39 192.168.122.209 [73890.489483] [tempesta fw] exiting... Apr 26 12:35:39 192.168.122.209 [73890.661366] [tdb] Shutdown Tempesta DB Apr 26 12:35:40 192.168.122.209 [73891.008437] End test: cache.test_h2_cache_control.TestH2CacheControl.test_proxy_revalidate_in_response_from_cache Apr 26 12:35:40 192.168.122.209 [73891.043811] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_proxy_revalidate_in_response_max_stale_in_request_from_cache Apr 26 12:35:41 192.168.122.209 [73892.462168] [tdb] Start Tempesta DB Apr 26 12:35:41 192.168.122.209 [73892.608682] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:35:43 192.168.122.209 [73894.067978] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73894.067978] Maybe that's fine, but it's worth checking the [73894.067978] config - if there is no relations between the [73894.067978] names, then host name confusion attack is possible. Apr 26 12:35:43 192.168.122.209 [73894.190738] [tempesta fw] Configuration processing is completed. Apr 26 12:35:43 192.168.122.209 [73894.248697] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:35:43 192.168.122.209 [73894.696866] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:35:43 192.168.122.209 [73894.724365] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:35:44 192.168.122.209 [73894.751320] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:35:44 192.168.122.209 [73894.802723] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:35:44 192.168.122.209 [73894.804476] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:35:44 192.168.122.209 [73894.842652] [tempesta fw] Tempesta FW is ready Apr 26 12:35:44 192.168.122.209 [73895.516819] [tdb] Close table 'client0.tdb' Apr 26 12:35:44 192.168.122.209 [73895.708928] [tdb] Close table 'sessions0.tdb' Apr 26 12:35:48 192.168.122.209 [73898.957388] [tdb] Close table 'cache0.tdb' Apr 26 12:35:48 192.168.122.209 [73899.192765] [tdb] Close table 'filter0.tdb' Apr 26 12:35:48 192.168.122.209 [73899.193170] [tempesta fw] modules are stopped Apr 26 12:35:48 192.168.122.209 [73899.400391] [tempesta fw] exiting... Apr 26 12:35:48 192.168.122.209 [73899.517494] [tdb] Shutdown Tempesta DB Apr 26 12:35:49 192.168.122.209 [73899.964886] End test: cache.test_h2_cache_control.TestH2CacheControl.test_proxy_revalidate_in_response_max_stale_in_request_from_cache Apr 26 12:35:49 192.168.122.209 [73900.003246] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_proxy_revalidate_in_response_max_stale_in_request_not_from_cache Apr 26 12:35:50 192.168.122.209 [73901.411249] [tdb] Start Tempesta DB Apr 26 12:35:50 192.168.122.209 [73901.553161] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:35:52 192.168.122.209 [73903.012122] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73903.012122] Maybe that's fine, but it's worth checking the [73903.012122] config - if there is no relations between the [73903.012122] names, then host name confusion attack is possible. Apr 26 12:35:52 192.168.122.209 [73903.135357] [tempesta fw] Configuration processing is completed. Apr 26 12:35:52 192.168.122.209 [73903.195633] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:35:52 192.168.122.209 [73903.619452] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:35:52 192.168.122.209 [73903.646375] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:35:52 192.168.122.209 [73903.674413] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:35:52 192.168.122.209 [73903.722804] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:35:52 192.168.122.209 [73903.724519] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:35:53 192.168.122.209 [73903.762749] [tempesta fw] Tempesta FW is ready Apr 26 12:35:55 192.168.122.209 [73906.376392] [tdb] Close table 'client0.tdb' Apr 26 12:35:55 192.168.122.209 [73906.565539] [tdb] Close table 'sessions0.tdb' Apr 26 12:35:58 192.168.122.209 [73909.708544] [tdb] Close table 'cache0.tdb' Apr 26 12:35:59 192.168.122.209 [73909.936256] [tdb] Close table 'filter0.tdb' Apr 26 12:35:59 192.168.122.209 [73909.936677] [tempesta fw] modules are stopped Apr 26 12:35:59 192.168.122.209 [73910.132011] [tempesta fw] exiting... Apr 26 12:35:59 192.168.122.209 [73910.263255] [tdb] Shutdown Tempesta DB Apr 26 12:35:59 192.168.122.209 [73910.657041] End test: cache.test_h2_cache_control.TestH2CacheControl.test_proxy_revalidate_in_response_max_stale_in_request_not_from_cache Apr 26 12:36:00 192.168.122.209 [73910.739276] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_proxy_revalidate_in_response_not_from_cache Apr 26 12:36:01 192.168.122.209 [73912.094144] [tdb] Start Tempesta DB Apr 26 12:36:01 192.168.122.209 [73912.229785] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:36:02 192.168.122.209 [73913.644186] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73913.644186] Maybe that's fine, but it's worth checking the [73913.644186] config - if there is no relations between the [73913.644186] names, then host name confusion attack is possible. Apr 26 12:36:03 192.168.122.209 [73913.758977] [tempesta fw] Configuration processing is completed. Apr 26 12:36:03 192.168.122.209 [73913.811858] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:36:03 192.168.122.209 [73914.226377] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:36:03 192.168.122.209 [73914.251639] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:36:03 192.168.122.209 [73914.277054] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:36:03 192.168.122.209 [73914.346942] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:36:03 192.168.122.209 [73914.348708] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:36:03 192.168.122.209 [73914.386890] [tempesta fw] Tempesta FW is ready Apr 26 12:36:06 192.168.122.209 [73917.059763] [tdb] Close table 'client0.tdb' Apr 26 12:36:06 192.168.122.209 [73917.250458] [tdb] Close table 'sessions0.tdb' Apr 26 12:36:09 192.168.122.209 [73920.443165] [tdb] Close table 'cache0.tdb' Apr 26 12:36:09 192.168.122.209 [73920.693414] [tdb] Close table 'filter0.tdb' Apr 26 12:36:09 192.168.122.209 [73920.693841] [tempesta fw] modules are stopped Apr 26 12:36:10 192.168.122.209 [73920.879402] [tempesta fw] exiting... Apr 26 12:36:10 192.168.122.209 [73921.019181] [tdb] Shutdown Tempesta DB Apr 26 12:36:10 192.168.122.209 [73921.396804] End test: cache.test_h2_cache_control.TestH2CacheControl.test_proxy_revalidate_in_response_not_from_cache Apr 26 12:36:10 192.168.122.209 [73921.432316] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_s_maxage_0_in_response Apr 26 12:36:12 192.168.122.209 [73922.862985] [tdb] Start Tempesta DB Apr 26 12:36:12 192.168.122.209 [73922.989980] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:36:13 192.168.122.209 [73924.448440] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73924.448440] Maybe that's fine, but it's worth checking the [73924.448440] config - if there is no relations between the [73924.448440] names, then host name confusion attack is possible. Apr 26 12:36:13 192.168.122.209 [73924.591116] [tempesta fw] Configuration processing is completed. Apr 26 12:36:13 192.168.122.209 [73924.651867] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:36:14 192.168.122.209 [73925.107748] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:36:14 192.168.122.209 [73925.137520] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:36:14 192.168.122.209 [73925.165845] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:36:14 192.168.122.209 [73925.203079] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:36:14 192.168.122.209 [73925.204825] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:36:14 192.168.122.209 [73925.243041] [tempesta fw] Tempesta FW is ready Apr 26 12:36:15 192.168.122.209 [73925.901943] [tdb] Close table 'client0.tdb' Apr 26 12:36:15 192.168.122.209 [73926.087735] [tdb] Close table 'sessions0.tdb' Apr 26 12:36:18 192.168.122.209 [73929.221801] [tdb] Close table 'cache0.tdb' Apr 26 12:36:18 192.168.122.209 [73929.456423] [tdb] Close table 'filter0.tdb' Apr 26 12:36:18 192.168.122.209 [73929.456857] [tempesta fw] modules are stopped Apr 26 12:36:18 192.168.122.209 [73929.669720] [tempesta fw] exiting... Apr 26 12:36:19 192.168.122.209 [73929.816012] [tdb] Shutdown Tempesta DB Apr 26 12:36:19 192.168.122.209 [73930.213490] End test: cache.test_h2_cache_control.TestH2CacheControl.test_s_maxage_0_in_response Apr 26 12:36:19 192.168.122.209 [73930.245051] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_s_maxage_1_in_response_sleep_2 Apr 26 12:36:20 192.168.122.209 [73931.707220] [tdb] Start Tempesta DB Apr 26 12:36:21 192.168.122.209 [73931.846350] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:36:22 192.168.122.209 [73933.260455] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73933.260455] Maybe that's fine, but it's worth checking the [73933.260455] config - if there is no relations between the [73933.260455] names, then host name confusion attack is possible. Apr 26 12:36:22 192.168.122.209 [73933.371236] [tempesta fw] Configuration processing is completed. Apr 26 12:36:22 192.168.122.209 [73933.429574] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:36:23 192.168.122.209 [73933.863134] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:36:23 192.168.122.209 [73933.891243] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:36:23 192.168.122.209 [73933.918685] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:36:23 192.168.122.209 [73933.959200] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:36:23 192.168.122.209 [73933.960927] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:36:23 192.168.122.209 [73934.003137] [tempesta fw] Tempesta FW is ready Apr 26 12:36:25 192.168.122.209 [73936.700554] [tdb] Close table 'client0.tdb' Apr 26 12:36:26 192.168.122.209 [73936.888422] [tdb] Close table 'sessions0.tdb' Apr 26 12:36:29 192.168.122.209 [73940.049100] [tdb] Close table 'cache0.tdb' Apr 26 12:36:29 192.168.122.209 [73940.288427] [tdb] Close table 'filter0.tdb' Apr 26 12:36:29 192.168.122.209 [73940.288829] [tempesta fw] modules are stopped Apr 26 12:36:29 192.168.122.209 [73940.455860] [tempesta fw] exiting... Apr 26 12:36:29 192.168.122.209 [73940.597080] [tdb] Shutdown Tempesta DB Apr 26 12:36:30 192.168.122.209 [73940.988337] End test: cache.test_h2_cache_control.TestH2CacheControl.test_s_maxage_1_in_response_sleep_2 Apr 26 12:36:30 192.168.122.209 [73941.024661] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_s_maxage_1_max_age_5_in_response_sleep_2 Apr 26 12:36:31 192.168.122.209 [73942.429990] [tdb] Start Tempesta DB Apr 26 12:36:31 192.168.122.209 [73942.566726] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:36:33 192.168.122.209 [73943.988621] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73943.988621] Maybe that's fine, but it's worth checking the [73943.988621] config - if there is no relations between the [73943.988621] names, then host name confusion attack is possible. Apr 26 12:36:33 192.168.122.209 [73944.111352] [tempesta fw] Configuration processing is completed. Apr 26 12:36:33 192.168.122.209 [73944.164749] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:36:33 192.168.122.209 [73944.602047] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:36:33 192.168.122.209 [73944.628751] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:36:33 192.168.122.209 [73944.654915] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:36:33 192.168.122.209 [73944.695342] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:36:33 192.168.122.209 [73944.697081] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:36:34 192.168.122.209 [73944.751286] [tempesta fw] Tempesta FW is ready Apr 26 12:36:36 192.168.122.209 [73947.410199] [tdb] Close table 'client0.tdb' Apr 26 12:36:36 192.168.122.209 [73947.609402] [tdb] Close table 'sessions0.tdb' Apr 26 12:36:40 192.168.122.209 [73950.768721] [tdb] Close table 'cache0.tdb' Apr 26 12:36:40 192.168.122.209 [73950.992311] [tdb] Close table 'filter0.tdb' Apr 26 12:36:40 192.168.122.209 [73950.992742] [tempesta fw] modules are stopped Apr 26 12:36:40 192.168.122.209 [73951.186645] [tempesta fw] exiting... Apr 26 12:36:40 192.168.122.209 [73951.301306] [tdb] Shutdown Tempesta DB Apr 26 12:36:40 192.168.122.209 [73951.689208] End test: cache.test_h2_cache_control.TestH2CacheControl.test_s_maxage_1_max_age_5_in_response_sleep_2 Apr 26 12:36:40 192.168.122.209 [73951.712062] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_s_maxage_2_in_response_sleep_0 Apr 26 12:36:42 192.168.122.209 [73953.148612] [tdb] Start Tempesta DB Apr 26 12:36:42 192.168.122.209 [73953.303881] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:36:44 192.168.122.209 [73954.772861] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73954.772861] Maybe that's fine, but it's worth checking the [73954.772861] config - if there is no relations between the [73954.772861] names, then host name confusion attack is possible. Apr 26 12:36:44 192.168.122.209 [73954.891500] [tempesta fw] Configuration processing is completed. Apr 26 12:36:44 192.168.122.209 [73954.951399] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:36:44 192.168.122.209 [73955.372171] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:36:44 192.168.122.209 [73955.398309] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:36:44 192.168.122.209 [73955.424416] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:36:44 192.168.122.209 [73955.471470] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:36:44 192.168.122.209 [73955.473238] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:36:44 192.168.122.209 [73955.511414] [tempesta fw] Tempesta FW is ready Apr 26 12:36:45 192.168.122.209 [73956.149577] [tdb] Close table 'client0.tdb' Apr 26 12:36:45 192.168.122.209 [73956.354152] [tdb] Close table 'sessions0.tdb' Apr 26 12:36:48 192.168.122.209 [73959.516846] [tdb] Close table 'cache0.tdb' Apr 26 12:36:49 192.168.122.209 [73959.759370] [tdb] Close table 'filter0.tdb' Apr 26 12:36:49 192.168.122.209 [73959.759823] [tempesta fw] modules are stopped Apr 26 12:36:49 192.168.122.209 [73959.949119] [tempesta fw] exiting... Apr 26 12:36:49 192.168.122.209 [73960.067684] [tdb] Shutdown Tempesta DB Apr 26 12:36:49 192.168.122.209 [73960.436541] End test: cache.test_h2_cache_control.TestH2CacheControl.test_s_maxage_2_in_response_sleep_0 Apr 26 12:36:49 192.168.122.209 [73960.478191] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_s_maxage_in_request Apr 26 12:36:51 192.168.122.209 [73961.833326] [tdb] Start Tempesta DB Apr 26 12:36:51 192.168.122.209 [73961.962843] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:36:52 192.168.122.209 [73963.416904] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73963.416904] Maybe that's fine, but it's worth checking the [73963.416904] config - if there is no relations between the [73963.416904] names, then host name confusion attack is possible. Apr 26 12:36:52 192.168.122.209 [73963.543630] [tempesta fw] Configuration processing is completed. Apr 26 12:36:52 192.168.122.209 [73963.600532] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:36:53 192.168.122.209 [73964.032723] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:36:53 192.168.122.209 [73964.060994] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:36:53 192.168.122.209 [73964.087102] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:36:53 192.168.122.209 [73964.135575] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:36:53 192.168.122.209 [73964.137323] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:36:53 192.168.122.209 [73964.183516] [tempesta fw] Tempesta FW is ready Apr 26 12:36:54 192.168.122.209 [73964.815222] [tdb] Close table 'client0.tdb' Apr 26 12:36:54 192.168.122.209 [73964.995559] [tdb] Close table 'sessions0.tdb' Apr 26 12:36:57 192.168.122.209 [73968.126586] [tdb] Close table 'cache0.tdb' Apr 26 12:36:57 192.168.122.209 [73968.395106] [tdb] Close table 'filter0.tdb' Apr 26 12:36:57 192.168.122.209 [73968.395569] [tempesta fw] modules are stopped Apr 26 12:36:57 192.168.122.209 [73968.613285] [tempesta fw] exiting... Apr 26 12:36:58 192.168.122.209 [73968.747768] [tdb] Shutdown Tempesta DB Apr 26 12:36:58 192.168.122.209 [73969.146962] End test: cache.test_h2_cache_control.TestH2CacheControl.test_s_maxage_in_request Apr 26 12:36:58 192.168.122.209 [73969.187176] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_s_maxage_in_response_and_max_stale_in_request Apr 26 12:36:59 192.168.122.209 [73970.661999] [tdb] Start Tempesta DB Apr 26 12:37:00 192.168.122.209 [73970.783058] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:37:01 192.168.122.209 [73972.101018] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73972.101018] Maybe that's fine, but it's worth checking the [73972.101018] config - if there is no relations between the [73972.101018] names, then host name confusion attack is possible. Apr 26 12:37:01 192.168.122.209 [73972.235786] [tempesta fw] Configuration processing is completed. Apr 26 12:37:01 192.168.122.209 [73972.297933] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:37:01 192.168.122.209 [73972.727386] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:37:02 192.168.122.209 [73972.754016] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:37:02 192.168.122.209 [73972.780709] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:37:02 192.168.122.209 [73972.855713] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:37:02 192.168.122.209 [73972.857485] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:37:02 192.168.122.209 [73972.903673] [tempesta fw] Tempesta FW is ready Apr 26 12:37:04 192.168.122.209 [73975.569482] [tdb] Close table 'client0.tdb' Apr 26 12:37:05 192.168.122.209 [73975.753376] [tdb] Close table 'sessions0.tdb' Apr 26 12:37:08 192.168.122.209 [73979.010290] [tdb] Close table 'cache0.tdb' Apr 26 12:37:08 192.168.122.209 [73979.271332] [tdb] Close table 'filter0.tdb' Apr 26 12:37:08 192.168.122.209 [73979.271983] [tempesta fw] modules are stopped Apr 26 12:37:08 192.168.122.209 [73979.464381] [tempesta fw] exiting... Apr 26 12:37:08 192.168.122.209 [73979.613190] [tdb] Shutdown Tempesta DB Apr 26 12:37:09 192.168.122.209 [73980.003274] End test: cache.test_h2_cache_control.TestH2CacheControl.test_s_maxage_in_response_and_max_stale_in_request Apr 26 12:37:09 192.168.122.209 [73980.041205] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_same_authorization_in_requests Apr 26 12:37:10 192.168.122.209 [73981.472962] [tdb] Start Tempesta DB Apr 26 12:37:10 192.168.122.209 [73981.600614] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:37:12 192.168.122.209 [73982.969068] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73982.969068] Maybe that's fine, but it's worth checking the [73982.969068] config - if there is no relations between the [73982.969068] names, then host name confusion attack is possible. Apr 26 12:37:12 192.168.122.209 [73983.087818] [tempesta fw] Configuration processing is completed. Apr 26 12:37:12 192.168.122.209 [73983.138711] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:37:12 192.168.122.209 [73983.612276] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:37:12 192.168.122.209 [73983.645648] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:37:12 192.168.122.209 [73983.678474] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:37:12 192.168.122.209 [73983.731842] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:37:12 192.168.122.209 [73983.733565] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:37:13 192.168.122.209 [73983.787774] [tempesta fw] Tempesta FW is ready Apr 26 12:37:13 192.168.122.209 [73984.435026] [tdb] Close table 'client0.tdb' Apr 26 12:37:13 192.168.122.209 [73984.650176] [tdb] Close table 'sessions0.tdb' Apr 26 12:37:17 192.168.122.209 [73987.852972] [tdb] Close table 'cache0.tdb' Apr 26 12:37:17 192.168.122.209 [73988.107050] [tdb] Close table 'filter0.tdb' Apr 26 12:37:17 192.168.122.209 [73988.107471] [tempesta fw] modules are stopped Apr 26 12:37:17 192.168.122.209 [73988.280880] [tempesta fw] exiting... Apr 26 12:37:17 192.168.122.209 [73988.430605] [tdb] Shutdown Tempesta DB Apr 26 12:37:18 192.168.122.209 [73988.810022] End test: cache.test_h2_cache_control.TestH2CacheControl.test_same_authorization_in_requests Apr 26 12:37:18 192.168.122.209 [73988.835579] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_same_authorization_in_requests_from_dynamic_table Apr 26 12:37:19 192.168.122.209 [73990.132822] [tdb] Start Tempesta DB Apr 26 12:37:19 192.168.122.209 [73990.256331] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:37:20 192.168.122.209 [73991.653225] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [73991.653225] Maybe that's fine, but it's worth checking the [73991.653225] config - if there is no relations between the [73991.653225] names, then host name confusion attack is possible. Apr 26 12:37:21 192.168.122.209 [73991.767942] [tempesta fw] Configuration processing is completed. Apr 26 12:37:21 192.168.122.209 [73991.819415] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:37:21 192.168.122.209 [73992.255273] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:37:21 192.168.122.209 [73992.285804] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:37:21 192.168.122.209 [73992.313624] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:37:21 192.168.122.209 [73992.356012] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:37:21 192.168.122.209 [73992.357835] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:37:21 192.168.122.209 [73992.407817] [tempesta fw] Tempesta FW is ready Apr 26 12:37:22 192.168.122.209 [73993.053125] [tdb] Close table 'client0.tdb' Apr 26 12:37:22 192.168.122.209 [73993.234390] [tdb] Close table 'sessions0.tdb' Apr 26 12:37:25 192.168.122.209 [73996.371170] [tdb] Close table 'cache0.tdb' Apr 26 12:37:25 192.168.122.209 [73996.628421] [tdb] Close table 'filter0.tdb' Apr 26 12:37:25 192.168.122.209 [73996.628852] [tempesta fw] modules are stopped Apr 26 12:37:26 192.168.122.209 [73996.816511] [tempesta fw] exiting... Apr 26 12:37:26 192.168.122.209 [73996.945284] [tdb] Shutdown Tempesta DB Apr 26 12:37:26 192.168.122.209 [73997.361510] End test: cache.test_h2_cache_control.TestH2CacheControl.test_same_authorization_in_requests_from_dynamic_table Apr 26 12:37:26 192.168.122.209 [73997.392287] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_same_authorization_in_requests_max_age_in_response Apr 26 12:37:28 192.168.122.209 [73998.819451] [tdb] Start Tempesta DB Apr 26 12:37:28 192.168.122.209 [73998.954586] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:37:29 192.168.122.209 [74000.361369] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [74000.361369] Maybe that's fine, but it's worth checking the [74000.361369] config - if there is no relations between the [74000.361369] names, then host name confusion attack is possible. Apr 26 12:37:29 192.168.122.209 [74000.484067] [tempesta fw] Configuration processing is completed. Apr 26 12:37:29 192.168.122.209 [74000.537528] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:37:30 192.168.122.209 [74000.936638] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:37:30 192.168.122.209 [74000.962514] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:37:30 192.168.122.209 [74000.989044] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:37:30 192.168.122.209 [74001.032077] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:37:30 192.168.122.209 [74001.033798] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:37:30 192.168.122.209 [74001.076006] [tempesta fw] Tempesta FW is ready Apr 26 12:37:30 192.168.122.209 [74001.675268] [tdb] Close table 'client0.tdb' Apr 26 12:37:31 192.168.122.209 [74001.874324] [tdb] Close table 'sessions0.tdb' Apr 26 12:37:34 192.168.122.209 [74004.990214] [tdb] Close table 'cache0.tdb' Apr 26 12:37:34 192.168.122.209 [74005.240164] [tdb] Close table 'filter0.tdb' Apr 26 12:37:34 192.168.122.209 [74005.240587] [tempesta fw] modules are stopped Apr 26 12:37:34 192.168.122.209 [74005.475242] [tempesta fw] exiting... Apr 26 12:37:34 192.168.122.209 [74005.599030] [tdb] Shutdown Tempesta DB Apr 26 12:37:35 192.168.122.209 [74006.027842] End test: cache.test_h2_cache_control.TestH2CacheControl.test_same_authorization_in_requests_max_age_in_response Apr 26 12:37:35 192.168.122.209 [74006.055835] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_same_authorization_in_requests_no_transform_in_response Apr 26 12:37:36 192.168.122.209 [74007.455735] [tdb] Start Tempesta DB Apr 26 12:37:36 192.168.122.209 [74007.593983] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:37:38 192.168.122.209 [74009.009453] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [74009.009453] Maybe that's fine, but it's worth checking the [74009.009453] config - if there is no relations between the [74009.009453] names, then host name confusion attack is possible. Apr 26 12:37:38 192.168.122.209 [74009.136488] [tempesta fw] Configuration processing is completed. Apr 26 12:37:38 192.168.122.209 [74009.192877] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:37:38 192.168.122.209 [74009.612893] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:37:38 192.168.122.209 [74009.640194] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:37:38 192.168.122.209 [74009.666619] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:37:38 192.168.122.209 [74009.720167] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:37:38 192.168.122.209 [74009.721932] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:37:39 192.168.122.209 [74009.760115] [tempesta fw] Tempesta FW is ready Apr 26 12:37:39 192.168.122.209 [74010.353380] [tdb] Close table 'client0.tdb' Apr 26 12:37:39 192.168.122.209 [74010.537689] [tdb] Close table 'sessions0.tdb' Apr 26 12:37:42 192.168.122.209 [74013.706873] [tdb] Close table 'cache0.tdb' Apr 26 12:37:43 192.168.122.209 [74013.920756] [tdb] Close table 'filter0.tdb' Apr 26 12:37:43 192.168.122.209 [74013.921157] [tempesta fw] modules are stopped Apr 26 12:37:43 192.168.122.209 [74014.125685] [tempesta fw] exiting... Apr 26 12:37:43 192.168.122.209 [74014.240735] [tdb] Shutdown Tempesta DB Apr 26 12:37:43 192.168.122.209 [74014.668337] End test: cache.test_h2_cache_control.TestH2CacheControl.test_same_authorization_in_requests_no_transform_in_response Apr 26 12:37:43 192.168.122.209 [74014.697426] Start test: cache.test_h2_cache_control.TestH2CacheControl.test_set_cookie_no_cached Apr 26 12:37:45 192.168.122.209 [74016.081929] [tdb] Start Tempesta DB Apr 26 12:37:45 192.168.122.209 [74016.223675] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:37:46 192.168.122.209 [74017.657611] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [74017.657611] Maybe that's fine, but it's worth checking the [74017.657611] config - if there is no relations between the [74017.657611] names, then host name confusion attack is possible. Apr 26 12:37:47 192.168.122.209 [74017.792295] [tempesta fw] Configuration processing is completed. Apr 26 12:37:47 192.168.122.209 [74017.849944] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:37:47 192.168.122.209 [74018.268998] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:37:47 192.168.122.209 [74018.299256] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:37:47 192.168.122.209 [74018.326381] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:37:47 192.168.122.209 [74018.384265] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:37:47 192.168.122.209 [74018.386279] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:37:47 192.168.122.209 [74018.440257] [tempesta fw] Tempesta FW is ready Apr 26 12:37:48 192.168.122.209 [74019.039451] [tdb] Close table 'client0.tdb' Apr 26 12:37:48 192.168.122.209 [74019.222326] [tdb] Close table 'sessions0.tdb' Apr 26 12:37:51 192.168.122.209 [74022.329609] [tdb] Close table 'cache0.tdb' Apr 26 12:37:51 192.168.122.209 [74022.587538] [tdb] Close table 'filter0.tdb' Apr 26 12:37:51 192.168.122.209 [74022.587959] [tempesta fw] modules are stopped Apr 26 12:37:52 192.168.122.209 [74022.778119] [tempesta fw] exiting... Apr 26 12:37:52 192.168.122.209 [74022.893423] [tdb] Shutdown Tempesta DB Apr 26 12:37:52 192.168.122.209 [74023.328259] End test: cache.test_h2_cache_control.TestH2CacheControl.test_set_cookie_no_cached Apr 26 12:37:52 192.168.122.209 [74023.359525] Start test: cache.test_h2_cache_control.TestH2CacheControlIgnore.test_ignore_max_age_not_ignore_s_maxage Apr 26 12:37:54 192.168.122.209 [74024.744210] [tdb] Start Tempesta DB Apr 26 12:37:54 192.168.122.209 [74024.876417] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:37:55 192.168.122.209 [74026.249624] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [74026.249624] Maybe that's fine, but it's worth checking the [74026.249624] config - if there is no relations between the [74026.249624] names, then host name confusion attack is possible. Apr 26 12:37:55 192.168.122.209 [74026.404411] [tempesta fw] Configuration processing is completed. Apr 26 12:37:55 192.168.122.209 [74026.460274] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:37:56 192.168.122.209 [74026.867802] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:37:56 192.168.122.209 [74026.893142] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:37:56 192.168.122.209 [74026.918417] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:37:56 192.168.122.209 [74026.968389] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:37:56 192.168.122.209 [74026.970133] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:37:56 192.168.122.209 [74027.008347] [tempesta fw] Tempesta FW is ready Apr 26 12:37:58 192.168.122.209 [74029.664263] [tdb] Close table 'client0.tdb' Apr 26 12:37:59 192.168.122.209 [74029.850844] [tdb] Close table 'sessions0.tdb' Apr 26 12:38:02 192.168.122.209 [74033.013391] [tdb] Close table 'cache0.tdb' Apr 26 12:38:02 192.168.122.209 [74033.278603] [tdb] Close table 'filter0.tdb' Apr 26 12:38:02 192.168.122.209 [74033.279037] [tempesta fw] modules are stopped Apr 26 12:38:02 192.168.122.209 [74033.482117] [tempesta fw] exiting... Apr 26 12:38:02 192.168.122.209 [74033.596225] [tdb] Shutdown Tempesta DB Apr 26 12:38:03 192.168.122.209 [74034.003551] End test: cache.test_h2_cache_control.TestH2CacheControlIgnore.test_ignore_max_age_not_ignore_s_maxage Apr 26 12:38:03 192.168.122.209 [74034.041066] Start test: cache.test_h2_cache_control.TestH2CacheControlIgnore.test_ignore_max_age_s_maxage Apr 26 12:38:04 192.168.122.209 [74035.500000] [tdb] Start Tempesta DB Apr 26 12:38:04 192.168.122.209 [74035.632699] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:38:06 192.168.122.209 [74037.061801] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [74037.061801] Maybe that's fine, but it's worth checking the [74037.061801] config - if there is no relations between the [74037.061801] names, then host name confusion attack is possible. Apr 26 12:38:06 192.168.122.209 [74037.204526] [tempesta fw] Configuration processing is completed. Apr 26 12:38:06 192.168.122.209 [74037.254311] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:38:06 192.168.122.209 [74037.662712] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:38:06 192.168.122.209 [74037.699644] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:38:06 192.168.122.209 [74037.725485] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:38:07 192.168.122.209 [74037.764512] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:38:07 192.168.122.209 [74037.765424] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:38:07 192.168.122.209 [74037.804456] [tempesta fw] Tempesta FW is ready Apr 26 12:38:09 192.168.122.209 [74040.460585] [tdb] Close table 'client0.tdb' Apr 26 12:38:09 192.168.122.209 [74040.666305] [tdb] Close table 'sessions0.tdb' Apr 26 12:38:13 192.168.122.209 [74043.818761] [tdb] Close table 'cache0.tdb' Apr 26 12:38:13 192.168.122.209 [74044.057622] [tdb] Close table 'filter0.tdb' Apr 26 12:38:13 192.168.122.209 [74044.058063] [tempesta fw] modules are stopped Apr 26 12:38:13 192.168.122.209 [74044.252845] [tempesta fw] exiting... Apr 26 12:38:13 192.168.122.209 [74044.384240] [tdb] Shutdown Tempesta DB Apr 26 12:38:14 192.168.122.209 [74044.780312] End test: cache.test_h2_cache_control.TestH2CacheControlIgnore.test_ignore_max_age_s_maxage Apr 26 12:38:14 192.168.122.209 [74044.810074] Start test: cache.test_h2_cache_control.TestH2CacheControlIgnore.test_ignore_max_stale_in_request Apr 26 12:38:15 192.168.122.209 [74046.209047] [tdb] Start Tempesta DB Apr 26 12:38:15 192.168.122.209 [74046.343351] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:38:17 192.168.122.209 [74047.733944] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [74047.733944] Maybe that's fine, but it's worth checking the [74047.733944] config - if there is no relations between the [74047.733944] names, then host name confusion attack is possible. Apr 26 12:38:17 192.168.122.209 [74047.864687] [tempesta fw] Configuration processing is completed. Apr 26 12:38:17 192.168.122.209 [74047.930116] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:38:17 192.168.122.209 [74048.352663] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:38:17 192.168.122.209 [74048.379567] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:38:17 192.168.122.209 [74048.406863] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:38:17 192.168.122.209 [74048.468657] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:38:17 192.168.122.209 [74048.470410] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:38:17 192.168.122.209 [74048.508596] [tempesta fw] Tempesta FW is ready Apr 26 12:38:20 192.168.122.209 [74051.159610] [tdb] Close table 'client0.tdb' Apr 26 12:38:20 192.168.122.209 [74051.358843] [tdb] Close table 'sessions0.tdb' Apr 26 12:38:23 192.168.122.209 [74054.489708] [tdb] Close table 'cache0.tdb' Apr 26 12:38:24 192.168.122.209 [74054.759640] [tdb] Close table 'filter0.tdb' Apr 26 12:38:24 192.168.122.209 [74054.760038] [tempesta fw] modules are stopped Apr 26 12:38:24 192.168.122.209 [74054.949954] [tempesta fw] exiting... Apr 26 12:38:24 192.168.122.209 [74055.064584] [tdb] Shutdown Tempesta DB Apr 26 12:38:24 192.168.122.209 [74055.433443] End test: cache.test_h2_cache_control.TestH2CacheControlIgnore.test_ignore_max_stale_in_request Apr 26 12:38:24 192.168.122.209 [74055.461330] Start test: cache.test_h2_cache_control.TestH2CacheControlIgnore.test_ignore_must_revalidate Apr 26 12:38:26 192.168.122.209 [74056.847890] [tdb] Start Tempesta DB Apr 26 12:38:26 192.168.122.209 [74056.983841] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:38:27 192.168.122.209 [74058.395816] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [74058.395816] Maybe that's fine, but it's worth checking the [74058.395816] config - if there is no relations between the [74058.395816] names, then host name confusion attack is possible. Apr 26 12:38:27 192.168.122.209 [74058.528808] [tempesta fw] Configuration processing is completed. Apr 26 12:38:27 192.168.122.209 [74058.580732] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:38:28 192.168.122.209 [74058.998728] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:38:28 192.168.122.209 [74059.024435] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:38:28 192.168.122.209 [74059.050080] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:38:28 192.168.122.209 [74059.088784] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:38:28 192.168.122.209 [74059.090522] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:38:28 192.168.122.209 [74059.128747] [tempesta fw] Tempesta FW is ready Apr 26 12:38:31 192.168.122.209 [74061.801597] [tdb] Close table 'client0.tdb' Apr 26 12:38:31 192.168.122.209 [74061.983894] [tdb] Close table 'sessions0.tdb' Apr 26 12:38:34 192.168.122.209 [74065.143697] [tdb] Close table 'cache0.tdb' Apr 26 12:38:34 192.168.122.209 [74065.360614] [tdb] Close table 'filter0.tdb' Apr 26 12:38:34 192.168.122.209 [74065.361090] [tempesta fw] modules are stopped Apr 26 12:38:34 192.168.122.209 [74065.562370] [tempesta fw] exiting... Apr 26 12:38:34 192.168.122.209 [74065.680107] [tdb] Shutdown Tempesta DB Apr 26 12:38:35 192.168.122.209 [74066.035601] End test: cache.test_h2_cache_control.TestH2CacheControlIgnore.test_ignore_must_revalidate Apr 26 12:38:35 192.168.122.209 [74066.116536] Start test: cache.test_h2_cache_control.TestH2CacheControlIgnore.test_ignore_public_with_authorization Apr 26 12:38:36 192.168.122.209 [74067.472152] [tdb] Start Tempesta DB Apr 26 12:38:36 192.168.122.209 [74067.607957] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:38:38 192.168.122.209 [74068.954231] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [74068.954231] Maybe that's fine, but it's worth checking the [74068.954231] config - if there is no relations between the [74068.954231] names, then host name confusion attack is possible. Apr 26 12:38:38 192.168.122.209 [74069.096945] [tempesta fw] Configuration processing is completed. Apr 26 12:38:38 192.168.122.209 [74069.157458] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:38:38 192.168.122.209 [74069.566821] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:38:38 192.168.122.209 [74069.592693] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:38:38 192.168.122.209 [74069.618136] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:38:38 192.168.122.209 [74069.668943] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:38:38 192.168.122.209 [74069.670688] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:38:38 192.168.122.209 [74069.708881] [tempesta fw] Tempesta FW is ready Apr 26 12:38:39 192.168.122.209 [74070.371238] [tdb] Close table 'client0.tdb' Apr 26 12:38:39 192.168.122.209 [74070.557798] [tdb] Close table 'sessions0.tdb' Apr 26 12:38:42 192.168.122.209 [74073.714309] [tdb] Close table 'cache0.tdb' Apr 26 12:38:43 192.168.122.209 [74073.971961] [tdb] Close table 'filter0.tdb' Apr 26 12:38:43 192.168.122.209 [74073.972360] [tempesta fw] modules are stopped Apr 26 12:38:43 192.168.122.209 [74074.165245] [tempesta fw] exiting... Apr 26 12:38:43 192.168.122.209 [74074.296298] [tdb] Shutdown Tempesta DB Apr 26 12:38:43 192.168.122.209 [74074.650348] End test: cache.test_h2_cache_control.TestH2CacheControlIgnore.test_ignore_public_with_authorization Apr 26 12:38:43 192.168.122.209 [74074.733627] Start test: cache.test_h2_cache_control.TestH2CacheControlIgnore.test_multi_ignore_private_no_cache_no_store Apr 26 12:38:45 192.168.122.209 [74076.056313] [tdb] Start Tempesta DB Apr 26 12:38:45 192.168.122.209 [74076.190862] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:38:46 192.168.122.209 [74077.534372] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [74077.534372] Maybe that's fine, but it's worth checking the [74077.534372] config - if there is no relations between the [74077.534372] names, then host name confusion attack is possible. Apr 26 12:38:46 192.168.122.209 [74077.673055] [tempesta fw] Configuration processing is completed. Apr 26 12:38:46 192.168.122.209 [74077.724355] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:38:47 192.168.122.209 [74078.138691] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:38:47 192.168.122.209 [74078.164116] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:38:47 192.168.122.209 [74078.189261] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:38:47 192.168.122.209 [74078.245025] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:38:47 192.168.122.209 [74078.246757] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:38:47 192.168.122.209 [74078.292990] [tempesta fw] Tempesta FW is ready Apr 26 12:38:48 192.168.122.209 [74078.934979] [tdb] Close table 'client0.tdb' Apr 26 12:38:48 192.168.122.209 [74079.120250] [tdb] Close table 'sessions0.tdb' Apr 26 12:38:51 192.168.122.209 [74082.261183] [tdb] Close table 'cache0.tdb' Apr 26 12:38:51 192.168.122.209 [74082.505628] [tdb] Close table 'filter0.tdb' Apr 26 12:38:51 192.168.122.209 [74082.506055] [tempesta fw] modules are stopped Apr 26 12:38:51 192.168.122.209 [74082.689920] [tempesta fw] exiting... Apr 26 12:38:52 192.168.122.209 [74082.841724] [tdb] Shutdown Tempesta DB Apr 26 12:38:52 192.168.122.209 [74083.199201] End test: cache.test_h2_cache_control.TestH2CacheControlIgnore.test_multi_ignore_private_no_cache_no_store Apr 26 12:38:52 192.168.122.209 [74083.227934] Start test: cache.test_h2_cache_control.TestH2CacheType.test_cache_is_shared Apr 26 12:38:53 192.168.122.209 [74084.569308] [tdb] Start Tempesta DB Apr 26 12:38:53 192.168.122.209 [74084.702260] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:38:55 192.168.122.209 [74086.126392] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [74086.126392] Maybe that's fine, but it's worth checking the [74086.126392] config - if there is no relations between the [74086.126392] names, then host name confusion attack is possible. Apr 26 12:38:55 192.168.122.209 [74086.245161] [tempesta fw] Configuration processing is completed. Apr 26 12:38:55 192.168.122.209 [74086.301920] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:38:55 192.168.122.209 [74086.710001] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:38:55 192.168.122.209 [74086.735822] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:38:56 192.168.122.209 [74086.760857] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:38:56 192.168.122.209 [74086.809133] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:38:56 192.168.122.209 [74086.810530] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:38:56 192.168.122.209 [74086.869097] [tempesta fw] Tempesta FW is ready Apr 26 12:38:58 192.168.122.209 [74089.540468] [tdb] Close table 'client0.tdb' Apr 26 12:38:58 192.168.122.209 [74089.727339] [tdb] Close table 'sessions0.tdb' Apr 26 12:39:02 192.168.122.209 [74092.879285] [tdb] Close table 'cache0.tdb' Apr 26 12:39:02 192.168.122.209 [74093.094154] [tdb] Close table 'filter0.tdb' Apr 26 12:39:02 192.168.122.209 [74093.094592] [tempesta fw] modules are stopped Apr 26 12:39:02 192.168.122.209 [74093.293895] [tempesta fw] exiting... Apr 26 12:39:02 192.168.122.209 [74093.435362] [tdb] Shutdown Tempesta DB Apr 26 12:39:03 192.168.122.209 [74093.834253] End test: cache.test_h2_cache_control.TestH2CacheType.test_cache_is_shared Apr 26 12:39:03 192.168.122.209 [74093.924547] Start test: cache.test_purge_hch.HeavyChunkedPurgeTest.test_0_purge_non_hch Apr 26 12:39:04 192.168.122.209 [74095.216712] [tdb] Start Tempesta DB Apr 26 12:39:04 192.168.122.209 [74095.347627] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:39:06 192.168.122.209 [74096.893405] [tempesta fw] Configuration processing is completed. Apr 26 12:39:06 192.168.122.209 [74096.956193] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:39:06 192.168.122.209 [74097.363019] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:39:06 192.168.122.209 [74097.390132] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:39:06 192.168.122.209 [74097.415523] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:39:06 192.168.122.209 [74097.461314] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:39:06 192.168.122.209 [74097.513154] [tempesta fw] Tempesta FW is ready Apr 26 12:39:07 192.168.122.209 [74098.219230] [tdb] Close table 'client0.tdb' Apr 26 12:39:07 192.168.122.209 [74098.402867] [tdb] Close table 'sessions0.tdb' Apr 26 12:39:10 192.168.122.209 [74101.619510] [tdb] Close table 'cache0.tdb' Apr 26 12:39:11 192.168.122.209 [74101.896487] [tdb] Close table 'filter0.tdb' Apr 26 12:39:11 192.168.122.209 [74101.896923] [tempesta fw] modules are stopped Apr 26 12:39:11 192.168.122.209 [74102.074001] [tempesta fw] exiting... Apr 26 12:39:11 192.168.122.209 [74102.204771] [tdb] Shutdown Tempesta DB Apr 26 12:39:11 192.168.122.209 [74102.586148] End test: cache.test_purge_hch.HeavyChunkedPurgeTest.test_0_purge_non_hch Apr 26 12:39:11 192.168.122.209 [74102.670045] Start test: cache.test_purge_hch.HeavyChunkedPurgeTest.test_1_purge_hch Apr 26 12:39:13 192.168.122.209 [74103.854026] [tdb] Start Tempesta DB Apr 26 12:39:13 192.168.122.209 [74103.980197] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:39:14 192.168.122.209 [74105.373438] [tempesta fw] Configuration processing is completed. Apr 26 12:39:14 192.168.122.209 [74105.429752] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:39:15 192.168.122.209 [74105.855037] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:39:15 192.168.122.209 [74105.882389] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:39:15 192.168.122.209 [74105.910946] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:39:15 192.168.122.209 [74105.953378] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:39:15 192.168.122.209 [74105.993302] [tempesta fw] Tempesta FW is ready Apr 26 12:39:15 192.168.122.209 [74106.646102] [tdb] Close table 'client0.tdb' Apr 26 12:39:16 192.168.122.209 [74106.829066] [tdb] Close table 'sessions0.tdb' Apr 26 12:39:19 192.168.122.209 [74109.981477] [tdb] Close table 'cache0.tdb' Apr 26 12:39:19 192.168.122.209 [74110.233098] [tdb] Close table 'filter0.tdb' Apr 26 12:39:19 192.168.122.209 [74110.233554] [tempesta fw] modules are stopped Apr 26 12:39:19 192.168.122.209 [74110.430779] [tempesta fw] exiting... Apr 26 12:39:19 192.168.122.209 [74110.552670] [tdb] Shutdown Tempesta DB Apr 26 12:39:20 192.168.122.209 [74110.934897] End test: cache.test_purge_hch.HeavyChunkedPurgeTest.test_1_purge_hch Apr 26 12:39:20 192.168.122.209 [74110.959015] Start test: cache.test_purge_resp_hch.HeavyChunkedPurgeRespTest.test_0_purge_resp_non_hch Apr 26 12:39:21 192.168.122.209 [74112.274524] [tdb] Start Tempesta DB Apr 26 12:39:21 192.168.122.209 [74112.405905] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:39:23 192.168.122.209 [74114.017509] [tempesta fw] Configuration processing is completed. Apr 26 12:39:23 192.168.122.209 [74114.073991] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:39:23 192.168.122.209 [74114.492474] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:39:23 192.168.122.209 [74114.519150] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:39:23 192.168.122.209 [74114.545411] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:39:23 192.168.122.209 [74114.629496] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:39:23 192.168.122.209 [74114.673445] [tempesta fw] Tempesta FW is ready Apr 26 12:39:24 192.168.122.209 [74115.315485] [tdb] Close table 'client0.tdb' Apr 26 12:39:24 192.168.122.209 [74115.504406] [tdb] Close table 'sessions0.tdb' Apr 26 12:39:27 192.168.122.209 [74118.677635] [tdb] Close table 'cache0.tdb' Apr 26 12:39:28 192.168.122.209 [74118.944637] [tdb] Close table 'filter0.tdb' Apr 26 12:39:28 192.168.122.209 [74118.945044] [tempesta fw] modules are stopped Apr 26 12:39:28 192.168.122.209 [74119.106156] [tempesta fw] exiting... Apr 26 12:39:28 192.168.122.209 [74119.223814] [tdb] Shutdown Tempesta DB Apr 26 12:39:28 192.168.122.209 [74119.641673] End test: cache.test_purge_resp_hch.HeavyChunkedPurgeRespTest.test_0_purge_resp_non_hch Apr 26 12:39:28 192.168.122.209 [74119.725777] Start test: encoding.test_encoding.TestH1BothTEAndCE.test Apr 26 12:39:30 192.168.122.209 [74120.927991] [tdb] Start Tempesta DB Apr 26 12:39:30 192.168.122.209 [74121.054738] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:39:31 192.168.122.209 [74122.189968] [tempesta fw] Configuration processing is completed. Apr 26 12:39:31 192.168.122.209 [74122.243017] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:39:31 192.168.122.209 [74122.656902] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:39:31 192.168.122.209 [74122.682979] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:39:31 192.168.122.209 [74122.708427] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:39:32 192.168.122.209 [74122.753605] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:39:32 192.168.122.209 [74122.793572] [tempesta fw] Tempesta FW is ready Apr 26 12:39:32 192.168.122.209 [74122.988183] [tempesta fw] Warning: Content-Encoding and Transfer-Encoding other than chunked not allowed to be in same response. Apr 26 12:39:32 192.168.122.209 [74122.991352] [tempesta fw] Warning: response dropped: processing error: 192.168.122.196 Apr 26 12:39:32 192.168.122.209 [74123.453587] [tdb] Close table 'client0.tdb' Apr 26 12:39:32 192.168.122.209 [74123.636736] [tdb] Close table 'sessions0.tdb' Apr 26 12:39:36 192.168.122.209 [74126.797350] [tdb] Close table 'cache0.tdb' Apr 26 12:39:36 192.168.122.209 [74127.042092] [tdb] Close table 'filter0.tdb' Apr 26 12:39:36 192.168.122.209 [74127.042532] [tempesta fw] modules are stopped Apr 26 12:39:36 192.168.122.209 [74127.218925] [tempesta fw] exiting... Apr 26 12:39:36 192.168.122.209 [74127.318770] [tdb] Shutdown Tempesta DB Apr 26 12:39:36 192.168.122.209 [74127.635847] End test: encoding.test_encoding.TestH1BothTEAndCE.test Apr 26 12:39:36 192.168.122.209 [74127.671993] Start test: encoding.test_encoding.TestH1ChunkedNonCacheable.test Apr 26 12:39:38 192.168.122.209 [74128.793024] [tdb] Start Tempesta DB Apr 26 12:39:38 192.168.122.209 [74128.920885] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:39:39 192.168.122.209 [74130.102059] [tempesta fw] Configuration processing is completed. Apr 26 12:39:39 192.168.122.209 [74130.157224] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:39:39 192.168.122.209 [74130.188464] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=00000000ff102b60 Apr 26 12:39:39 192.168.122.209 [74130.217319] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000089d8eaf Apr 26 12:39:39 192.168.122.209 [74130.257696] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:39:39 192.168.122.209 [74130.297639] [tempesta fw] Tempesta FW is ready Apr 26 12:39:40 192.168.122.209 [74130.936155] [tdb] Close table 'client0.tdb' Apr 26 12:39:40 192.168.122.209 [74131.133540] [tdb] Close table 'sessions0.tdb' Apr 26 12:39:40 192.168.122.209 [74131.364771] [tdb] Close table 'filter0.tdb' Apr 26 12:39:40 192.168.122.209 [74131.365180] [tempesta fw] modules are stopped Apr 26 12:39:40 192.168.122.209 [74131.530691] [tempesta fw] exiting... Apr 26 12:39:40 192.168.122.209 [74131.663551] [tdb] Shutdown Tempesta DB Apr 26 12:39:41 192.168.122.209 [74132.100812] End test: encoding.test_encoding.TestH1ChunkedNonCacheable.test Apr 26 12:39:41 192.168.122.209 [74132.138246] Start test: encoding.test_encoding.TestH1ChunkedWithLongBodyAndTrailer.test Apr 26 12:39:42 192.168.122.209 [74133.550655] [tdb] Start Tempesta DB Apr 26 12:39:42 192.168.122.209 [74133.683459] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:39:43 192.168.122.209 [74134.335016] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [74134.335016] Maybe that's fine, but it's worth checking the [74134.335016] config - if there is no relations between the [74134.335016] names, then host name confusion attack is possible. Apr 26 12:39:43 192.168.122.209 [74134.417762] [tempesta fw] Configuration processing is completed. Apr 26 12:39:43 192.168.122.209 [74134.468021] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:39:44 192.168.122.209 [74134.866268] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:39:44 192.168.122.209 [74134.891281] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:39:44 192.168.122.209 [74134.916764] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:39:44 192.168.122.209 [74134.965749] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:39:44 192.168.122.209 [74134.967484] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:39:44 192.168.122.209 [74135.005733] [tempesta fw] Tempesta FW is ready Apr 26 12:39:44 192.168.122.209 [74135.713972] [tdb] Close table 'client0.tdb' Apr 26 12:39:45 192.168.122.209 [74135.907299] [tdb] Close table 'sessions0.tdb' Apr 26 12:39:48 192.168.122.209 [74139.091591] [tdb] Close table 'cache0.tdb' Apr 26 12:39:48 192.168.122.209 [74139.318646] [tdb] Close table 'filter0.tdb' Apr 26 12:39:48 192.168.122.209 [74139.319066] [tempesta fw] modules are stopped Apr 26 12:39:48 192.168.122.209 [74139.506192] [tempesta fw] exiting... Apr 26 12:39:48 192.168.122.209 [74139.654935] [tdb] Shutdown Tempesta DB Apr 26 12:39:49 192.168.122.209 [74140.074922] End test: encoding.test_encoding.TestH1ChunkedWithLongBodyAndTrailer.test Apr 26 12:39:49 192.168.122.209 [74140.111458] Start test: encoding.test_encoding.TestH2BodyDechunking.test Apr 26 12:39:50 192.168.122.209 [74141.504239] [tdb] Start Tempesta DB Apr 26 12:39:50 192.168.122.209 [74141.642285] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:39:52 192.168.122.209 [74142.995166] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [74142.995166] Maybe that's fine, but it's worth checking the [74142.995166] config - if there is no relations between the [74142.995166] names, then host name confusion attack is possible. Apr 26 12:39:52 192.168.122.209 [74143.090202] [tempesta fw] Configuration processing is completed. Apr 26 12:39:52 192.168.122.209 [74143.146360] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:39:52 192.168.122.209 [74143.570488] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:39:52 192.168.122.209 [74143.596437] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:39:52 192.168.122.209 [74143.621783] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:39:52 192.168.122.209 [74143.665822] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:39:52 192.168.122.209 [74143.705760] [tempesta fw] Tempesta FW is ready Apr 26 12:39:53 192.168.122.209 [74144.397575] [tdb] Close table 'client0.tdb' Apr 26 12:39:53 192.168.122.209 [74144.576987] [tdb] Close table 'sessions0.tdb' Apr 26 12:39:57 192.168.122.209 [74147.743512] [tdb] Close table 'cache0.tdb' Apr 26 12:39:57 192.168.122.209 [74148.001595] [tdb] Close table 'filter0.tdb' Apr 26 12:39:57 192.168.122.209 [74148.002049] [tempesta fw] modules are stopped Apr 26 12:39:57 192.168.122.209 [74148.193907] [tempesta fw] exiting... Apr 26 12:39:57 192.168.122.209 [74148.335982] [tdb] Shutdown Tempesta DB Apr 26 12:39:58 192.168.122.209 [74148.751662] End test: encoding.test_encoding.TestH2BodyDechunking.test Apr 26 12:39:58 192.168.122.209 [74148.786147] Start test: encoding.test_encoding.TestH2ChunkedExtensionRemoved.test Apr 26 12:39:59 192.168.122.209 [74150.214575] [tdb] Start Tempesta DB Apr 26 12:39:59 192.168.122.209 [74150.348884] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:40:00 192.168.122.209 [74151.543328] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [74151.543328] Maybe that's fine, but it's worth checking the [74151.543328] config - if there is no relations between the [74151.543328] names, then host name confusion attack is possible. Apr 26 12:40:00 192.168.122.209 [74151.630542] [tempesta fw] Configuration processing is completed. Apr 26 12:40:00 192.168.122.209 [74151.698925] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:40:01 192.168.122.209 [74152.125730] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:40:01 192.168.122.209 [74152.161640] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:40:01 192.168.122.209 [74152.188075] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:40:01 192.168.122.209 [74152.249969] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:40:01 192.168.122.209 [74152.297927] [tempesta fw] Tempesta FW is ready Apr 26 12:40:02 192.168.122.209 [74152.934750] [tdb] Close table 'client0.tdb' Apr 26 12:40:02 192.168.122.209 [74153.116980] [tdb] Close table 'sessions0.tdb' Apr 26 12:40:05 192.168.122.209 [74156.286086] [tdb] Close table 'cache0.tdb' Apr 26 12:40:05 192.168.122.209 [74156.535426] [tdb] Close table 'filter0.tdb' Apr 26 12:40:05 192.168.122.209 [74156.535849] [tempesta fw] modules are stopped Apr 26 12:40:05 192.168.122.209 [74156.730701] [tempesta fw] exiting... Apr 26 12:40:06 192.168.122.209 [74156.873149] [tdb] Shutdown Tempesta DB Apr 26 12:40:06 192.168.122.209 [74157.233478] End test: encoding.test_encoding.TestH2ChunkedExtensionRemoved.test Apr 26 12:40:06 192.168.122.209 [74157.261043] Start test: encoding.test_encoding.TestH2ChunkedIsNotLast.test Apr 26 12:40:07 192.168.122.209 [74158.637589] [tdb] Start Tempesta DB Apr 26 12:40:08 192.168.122.209 [74158.778108] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:40:09 192.168.122.209 [74160.188148] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [74160.188148] Maybe that's fine, but it's worth checking the [74160.188148] config - if there is no relations between the [74160.188148] names, then host name confusion attack is possible. Apr 26 12:40:09 192.168.122.209 [74160.271007] [tempesta fw] Configuration processing is completed. Apr 26 12:40:09 192.168.122.209 [74160.329006] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:40:10 192.168.122.209 [74160.761104] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:40:10 192.168.122.209 [74160.787682] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:40:10 192.168.122.209 [74160.814053] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:40:10 192.168.122.209 [74160.850015] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:40:10 192.168.122.209 [74160.890040] [tempesta fw] Tempesta FW is ready Apr 26 12:40:10 192.168.122.209 [74161.079183] [tempesta fw] Warning: Parser error: state=Resp_HdrTransfer_EncodingV input(-8)=0x63('coding: chunked, gzip [74161.079183] [74161.079183] 3 [74161.079183] 123 [74161.079183] 0 [74161.079183] [74161.079183] ') data_len=136 off=106 Apr 26 12:40:10 192.168.122.209 [74161.084103] [tempesta fw] Warning: response dropped: processing error: 192.168.122.196 Apr 26 12:40:10 192.168.122.209 [74161.529476] [tdb] Close table 'client0.tdb' Apr 26 12:40:10 192.168.122.209 [74161.717310] [tdb] Close table 'sessions0.tdb' Apr 26 12:40:14 192.168.122.209 [74164.892797] [tdb] Close table 'cache0.tdb' Apr 26 12:40:14 192.168.122.209 [74165.150336] [tdb] Close table 'filter0.tdb' Apr 26 12:40:14 192.168.122.209 [74165.150757] [tempesta fw] modules are stopped Apr 26 12:40:14 192.168.122.209 [74165.350011] [tempesta fw] exiting... Apr 26 12:40:14 192.168.122.209 [74165.466653] [tdb] Shutdown Tempesta DB Apr 26 12:40:15 192.168.122.209 [74165.883925] End test: encoding.test_encoding.TestH2ChunkedIsNotLast.test Apr 26 12:40:15 192.168.122.209 [74165.910252] Start test: encoding.test_encoding.TestH2ChunkedWithLongBodyAndTrailer.test Apr 26 12:40:16 192.168.122.209 [74167.415461] [tdb] Start Tempesta DB Apr 26 12:40:16 192.168.122.209 [74167.560341] [tempesta fw] Initializing Tempesta FW kernel module... Apr 26 12:40:18 192.168.122.209 [74168.947456] [tempesta fw] Warning: Vhost default doesn't have certificate with matching SAN/CN. [74168.947456] Maybe that's fine, but it's worth checking the [74168.947456] config - if there is no relations between the [74168.947456] names, then host name confusion attack is possible. Apr 26 12:40:18 192.168.122.209 [74169.034264] [tempesta fw] Configuration processing is completed. Apr 26 12:40:18 192.168.122.209 [74169.090613] [tdb] Opened table /opt/tempesta/db/filter0.tdb: size=16777216 rec_size=20 base=00000000a1ec113b Apr 26 12:40:18 192.168.122.209 [74169.501233] [tdb] Opened table /opt/tempesta/db/cache0.tdb: size=268435456 rec_size=0 base=00000000d6f20111 Apr 26 12:40:18 192.168.122.209 [74169.527013] [tdb] Opened table /opt/tempesta/db/sessions0.tdb: size=16777216 rec_size=312 base=000000000bcf9318 Apr 26 12:40:18 192.168.122.209 [74169.553579] [tdb] Opened table /opt/tempesta/db/client0.tdb: size=16777216 rec_size=624 base=00000000aff1e057 Apr 26 12:40:18 192.168.122.209 [74169.614190] [tempesta fw] Open listen socket on: 0.0.0.0:443 Apr 26 12:40:18 192.168.122.209 [74169.615912] [tempesta fw] Open listen socket on: 0.0.0.0 Apr 26 12:40:18 192.168.122.209 [74169.658144] [tempesta fw] Tempesta FW is ready Apr 26 12:40:19 192.168.122.209 [74169.951723] BUG: unable to handle page fault for address: ffff88802f889000 Apr 26 12:40:19 192.168.122.209 [74169.952373] #PF: supervisor read access in kernel mode Apr 26 12:40:19 192.168.122.209 [74169.952836] #PF: error_code(0x0000) - not-present page Apr 26 12:40:19 192.168.122.209 [74169.953292] PGD 175001067 P4D 175001067 PUD 175002067 PMD 17fd8c067 PTE 800fffffd0776060 Apr 26 12:40:19 192.168.122.209 [74169.954024] Oops: 0000 [#1] SMP DEBUG_PAGEALLOC KASAN NOPTI Apr 26 12:40:19 192.168.122.209 [74169.954527] CPU: 2 PID: 26 Comm: ksoftirqd/2 Tainted: G OE 5.10.35.tfw-39c65d3-debug #1 Apr 26 12:40:19 192.168.122.209 [74169.955342] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 Apr 26 12:40:19 192.168.122.209 [74169.956202] RIP: 0010:key_128_enc_update+0x23/0x29 [aesni_intel] Apr 26 12:40:19 192.168.122.209 [74169.956739] Code: 41 5e 41 5d 41 5c c3 c5 7a 6f 06 c5 7a 6f 6e 60 4c 01 46 18 45 31 db 4c 8b 6e 50 4d 85 ed 0f 84 c6 01 00 00 49 83 f8 10 7c 06 fa 6f 09 eb 52 4e 8d 14 19 4d 89 c4 c5 f1 ef c9 49 83 fc 08 7c Apr 26 12:40:19 192.168.122.209 [74169.958367] RSP: 0018:ffff888100feea80 EFLAGS: 00010206 Apr 26 12:40:19 192.168.122.209 [74169.958841] RAX: 0000000000000010 RBX: ffff88802f889000 RCX: ffff88802f889000 Apr 26 12:40:19 192.168.122.209 [74169.959465] RDX: ffff88802f889000 RSI: ffff888100feed60 RDI: ffff88810d90a830 Apr 26 12:40:19 192.168.122.209 [74169.960111] RBP: ffff888100feef58 R08: 00000000000003d9 R09: 000000000000000d Apr 26 12:40:19 192.168.122.209 [74169.960751] R10: 00000000000001a3 R11: 0000000000000000 R12: ffff888100fdb388 Apr 26 12:40:19 192.168.122.209 [74169.961375] R13: 0000000000000003 R14: ffff888100feeb38 R15: ffff888100fef2d8 Apr 26 12:40:19 192.168.122.209 [74169.962005] FS: 0000000000000000(0000) GS:ffff888147f00000(0000) knlGS:0000000000000000 Apr 26 12:40:19 192.168.122.209 [74169.962727] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Apr 26 12:40:19 192.168.122.209 [74169.963237] CR2: ffff88802f889000 CR3: 000000010e400003 CR4: 0000000000770ee0 Apr 26 12:40:19 192.168.122.209 [74169.963867] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Apr 26 12:40:19 192.168.122.209 [74169.964494] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Apr 26 12:40:19 192.168.122.209 [74169.965122] PKRU: 55555554 Apr 26 12:40:19 192.168.122.209 [74169.965374] Call Trace: Apr 26 12:40:19 192.168.122.209 [74169.965644] ? sg_next+0x20/0x50 Apr 26 12:40:19 192.168.122.209 [74169.965952] ? scatterwalk_ffwd+0x2e/0x150 Apr 26 12:40:19 192.168.122.209 [74169.966338] ? gcmaes_crypt_by_sg+0x7cd/0xcf0 [aesni_intel] Apr 26 12:40:19 192.168.122.209 [74169.966856] ? common_rfc4106_set_key+0x80/0x80 [aesni_intel] Apr 26 12:40:19 192.168.122.209 [74169.967384] ? static_protections+0x183/0x2b0 Apr 26 12:40:19 192.168.122.209 [74169.967788] ? create_prof_cpu_mask+0x30/0x30 Apr 26 12:40:19 192.168.122.209 [74169.968178] ? lookup_address+0xb0/0xb0 Apr 26 12:40:19 192.168.122.209 [74169.968535] ? ret_from_fork+0x1f/0x30 Apr 26 12:40:19 192.168.122.209 [74169.968884] ? lookup_address_in_pgd.part.0.constprop.0+0x215/0x280 Apr 26 12:40:19 192.168.122.209 [74169.969440] ? __change_page_attr_set_clr+0xb8d/0x14b0 Apr 26 12:40:19 192.168.122.209 [74169.969914] ? __kasan_check_read+0x11/0x20 Apr 26 12:40:19 192.168.122.209 [74169.970314] ? _raw_spin_trylock+0x6e/0xe0 Apr 26 12:40:19 192.168.122.209 [74169.970697] generic_gcmaes_encrypt+0xe0/0x110 [aesni_intel] Apr 26 12:40:19 192.168.122.209 [74169.971207] ? helper_rfc4106_decrypt+0x200/0x200 [aesni_intel] Apr 26 12:40:19 192.168.122.209 [74169.971752] ? __dev_queue_xmit+0x6e9/0xf90 Apr 26 12:40:19 192.168.122.209 [74169.972137] crypto_aead_encrypt+0x78/0xa0 Apr 26 12:40:19 192.168.122.209 [74169.972511] simd_aead_encrypt+0xcf/0x120 [crypto_simd] Apr 26 12:40:19 192.168.122.209 [74169.972992] crypto_aead_encrypt+0x78/0xa0 Apr 26 12:40:19 192.168.122.209 [74169.973371] ttls_encrypt+0x2a3/0x360 [tempesta_tls] Apr 26 12:40:19 192.168.122.209 [74169.973860] tfw_tls_encrypt+0x8f1/0xce0 [tempesta_fw] Apr 26 12:40:19 192.168.122.209 [74169.974348] ? tfw_tls_connection_recv+0x730/0x730 [tempesta_fw] Apr 26 12:40:19 192.168.122.209 [74169.974886] ? memcpy_fast+0xe/0x10 [tempesta_lib] Apr 26 12:40:19 192.168.122.209 [74169.975340] ? ss_skb_get_room_w_frag+0x8f/0xf0 [tempesta_fw] Apr 26 12:40:19 192.168.122.209 [74169.975857] ? __kasan_check_write+0x14/0x20 Apr 26 12:40:19 192.168.122.209 [74169.976243] ? _raw_spin_lock+0x7b/0xd0 Apr 26 12:40:19 192.168.122.209 [74169.976615] ? tfw_h2_insert_frame_header+0x722/0x9a0 [tempesta_fw] Apr 26 12:40:19 192.168.122.209 [74169.977179] ? skb_zerocopy_clone+0x63/0x280 Apr 26 12:40:19 192.168.122.209 [74169.977570] ? __kasan_check_write+0x14/0x20 Apr 26 12:40:19 192.168.122.209 [74169.977986] ? tfw_h2_stream_sched_insert_active+0x99/0xc0 [tempesta_fw] Apr 26 12:40:19 192.168.122.209 [74169.978582] ? __asan_loadN+0xf/0x20 Apr 26 12:40:19 192.168.122.209 [74169.978915] ? pvclock_clocksource_read+0xe1/0x1a0 Apr 26 12:40:19 192.168.122.209 [74169.979359] tcp_tfw_sk_write_xmit+0x148/0x1d0 Apr 26 12:40:19 192.168.122.209 [74169.979790] ? tfw_tls_connection_recv+0x730/0x730 [tempesta_fw] Apr 26 12:40:19 192.168.122.209 [74169.980326] tcp_write_xmit+0x768/0x2a50 Apr 26 12:40:19 192.168.122.209 [74169.980688] ? tcp_rearm_rto+0x220/0x220 Apr 26 12:40:19 192.168.122.209 [74169.981059] ? __cgroup_bpf_run_filter_skb+0x397/0x720 Apr 26 12:40:19 192.168.122.209 [74169.981518] __tcp_push_pending_frames+0x5f/0x1a0 Apr 26 12:40:19 192.168.122.209 [74169.981943] tcp_push_pending_frames+0xbc/0x200 Apr 26 12:40:19 192.168.122.209 [74169.982352] tcp_rcv_established+0x986/0xb40 Apr 26 12:40:19 192.168.122.209 [74169.982742] ? tcp_data_queue+0x1d80/0x1d80 Apr 26 12:40:19 192.168.122.209 [74169.983122] ? __kasan_check_read+0x11/0x20 Apr 26 12:40:19 192.168.122.209 [74169.983499] tcp_v4_do_rcv+0x25f/0x360 Apr 26 12:40:19 192.168.122.209 [74169.983843] tcp_v4_rcv+0x1600/0x1770 Apr 26 12:40:19 192.168.122.209 [74169.984231] ? tcp_new+0x420/0x420 [nf_conntrack] Apr 26 12:40:19 192.168.122.209 [74169.984653] ? tcp_v4_early_demux+0x2f0/0x2f0 Apr 26 12:40:19 192.168.122.209 [74169.985053] ip_protocol_deliver_rcu+0x46/0x2e0 Apr 26 12:40:19 192.168.122.209 [74169.985459] ip_local_deliver_finish+0xc6/0xe0 Apr 26 12:40:19 192.168.122.209 [74169.985863] ip_local_deliver+0x1f5/0x210 Apr 26 12:40:19 192.168.122.209 [74169.986225] ? ip_local_deliver_finish+0xe0/0xe0 Apr 26 12:40:19 192.168.122.209 [74169.986638] ? tcp_v4_early_demux+0x297/0x2f0 Apr 26 12:40:19 192.168.122.209 [74169.987036] ? ip_protocol_deliver_rcu+0x2e0/0x2e0 Apr 26 12:40:19 192.168.122.209 [74169.987467] ? ip_rcv_finish_core.constprop.0+0x17c/0x890 Apr 26 12:40:19 192.168.122.209 [74169.987950] ip_rcv_finish+0xcf/0xf0 Apr 26 12:40:19 192.168.122.209 [74169.988274] ip_rcv+0x16d/0x180 Apr 26 12:40:19 192.168.122.209 [74169.988559] ? ip_local_deliver+0x210/0x210 Apr 26 12:40:19 192.168.122.209 [74169.988944] ? ip_rcv_finish_core.constprop.0+0x890/0x890 Apr 26 12:40:19 192.168.122.209 [74169.989435] ? virtqueue_poll+0xbb/0xd0 Apr 26 12:40:19 192.168.122.209 [74169.989787] ? ip_local_deliver+0x210/0x210 Apr 26 12:40:19 192.168.122.209 [74169.990163] __netif_receive_skb_one_core+0x132/0x140 Apr 26 12:40:19 192.168.122.209 [74169.990618] ? napi_gro_receive+0x260/0x260 Apr 26 12:40:19 192.168.122.209 [74169.990997] ? __kasan_check_write+0x14/0x20 Apr 26 12:40:19 192.168.122.209 [74169.991380] ? _raw_spin_lock+0x7b/0xd0 Apr 26 12:40:19 192.168.122.209 [74169.991728] __netif_receive_skb+0x26/0xb0 Apr 26 12:40:19 192.168.122.209 [74169.992109] ? generic_exec_single+0xb1/0x170 Apr 26 12:40:19 192.168.122.209 [74169.992499] process_backlog+0xfe/0x290 Apr 26 12:40:19 192.168.122.209 [74169.992850] net_rx_action+0x287/0x6b0 Apr 26 12:40:19 192.168.122.209 [74169.993191] ? napi_complete_done+0x2c0/0x2c0 Apr 26 12:40:19 192.168.122.209 [74169.993592] ? switch_fpu_return+0x120/0x120 Apr 26 12:40:19 192.168.122.209 [74169.993981] __do_softirq+0xfe/0x383 Apr 26 12:40:19 192.168.122.209 [74169.994311] ? tasklet_hi_action+0x30/0x30 Apr 26 12:40:19 192.168.122.209 [74169.994684] run_ksoftirqd+0x2b/0x40 Apr 26 12:40:19 192.168.122.209 [74169.995016] smpboot_thread_fn+0x1ba/0x2f0 Apr 26 12:40:19 192.168.122.209 [74169.995384] ? smpboot_register_percpu_thread+0x190/0x190 Apr 26 12:40:19 192.168.122.209 [74169.995868] ? __kasan_check_read+0x11/0x20 Apr 26 12:40:19 192.168.122.209 [74169.996248] ? __kthread_parkme+0x83/0xa0 Apr 26 12:40:19 192.168.122.209 [74169.996614] ? smpboot_register_percpu_thread+0x190/0x190 Apr 26 12:40:19 192.168.122.209 [74169.997095] kthread+0x1d9/0x200 Apr 26 12:40:19 192.168.122.209 [74169.997390] ? __kthread_bind_mask+0x70/0x70 Apr 26 12:40:19 192.168.122.209 [74169.997779] ret_from_fork+0x1f/0x30 Apr 26 12:40:19 192.168.122.209 [74169.998112] Modules linked in: tempesta_fw(OE) tempesta_db(OE) tempesta_tls(OE) tempesta_lib(OE) xt_mark tcp_diag inet_diag xt_nat xt_tcpudp veth ib_core sha256_ssse3 sha512_ssse3 nvme_tcp nvme_fabrics nvme_core vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock tls xt_conntrack xt_MASQUERADE nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype nft_compat nft_masq nft_counter nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 bridge stp llc nf_tables overlay cfg80211 intel_rapl_msr intel_rapl_common isst_if_common sch_fq_codel nfit kvm_intel kvm i2c_i801 rapl i2c_smbus binfmt_misc lpc_ich joydev input_leds mac_hid serio_raw dm_multipath netconsole msr efi_pstore nfnetlink dmi_sysfs qemu_fw_cfg ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear cirrus drm_kms_helper syscopyarea crct10dif_pclmul crc32_pclmul sysfillre Apr 26 12:40:19 192.168.122.209 ct Apr 26 12:40:19 192.168.122.209 [74169.998238] sysimgblt ghash_clmulni_intel fb_sys_fops aesni_intel crypto_simd cryptd glue_helper cec psmouse ahci drm libahci virtio_net net_failover virtio_rng virtio_blk failover [last unloaded: tempesta_lib] Apr 26 12:40:19 192.168.122.209 [74170.007354] CR2: ffff88802f889000 Apr 26 12:40:19 192.168.122.209 [74170.007691] ---[ end trace 6898ec846442ef0a ]--- Apr 26 12:40:19 192.168.122.209 [74170.008123] RIP: 0010:key_128_enc_update+0x23/0x29 [aesni_intel] Apr 26 12:40:19 192.168.122.209 [74170.008650] Code: 41 5e 41 5d 41 5c c3 c5 7a 6f 06 c5 7a 6f 6e 60 4c 01 46 18 45 31 db 4c 8b 6e 50 4d 85 ed 0f 84 c6 01 00 00 49 83 f8 10 7c 06 fa 6f 09 eb 52 4e 8d 14 19 4d 89 c4 c5 f1 ef c9 49 83 fc 08 7c Apr 26 12:40:19 192.168.122.209 [74170.010267] RSP: 0018:ffff888100feea80 EFLAGS: 00010206 Apr 26 12:40:19 192.168.122.209 [74170.010733] RAX: 0000000000000010 RBX: ffff88802f889000 RCX: ffff88802f889000 Apr 26 12:40:19 192.168.122.209 [74170.011353] RDX: ffff88802f889000 RSI: ffff888100feed60 RDI: ffff88810d90a830 Apr 26 12:40:19 192.168.122.209 [74170.011981] RBP: ffff888100feef58 R08: 00000000000003d9 R09: 000000000000000d Apr 26 12:40:19 192.168.122.209 [74170.012609] R10: 00000000000001a3 R11: 0000000000000000 R12: ffff888100fdb388 Apr 26 12:40:19 192.168.122.209 [74170.013235] R13: 0000000000000003 R14: ffff888100feeb38 R15: ffff888100fef2d8 Apr 26 12:40:19 192.168.122.209 [74170.013860] FS: 0000000000000000(0000) GS:ffff888147f00000(0000) knlGS:0000000000000000 Apr 26 12:40:19 192.168.122.209 [74170.014560] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Apr 26 12:40:19 192.168.122.209 [74170.015071] CR2: ffff88802f889000 CR3: 000000010e400003 CR4: 0000000000770ee0 Apr 26 12:40:19 192.168.122.209 [74170.015697] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Apr 26 12:40:19 192.168.122.209 [74170.016319] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Apr 26 12:40:19 192.168.122.209 [74170.016947] PKRU: 55555554 Apr 26 12:40:19 192.168.122.209 [74170.017199] Kernel panic - not syncing: Fatal exception in interrupt Apr 26 12:40:19 192.168.122.209 [74170.018014] Kernel Offset: 0x34000000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff) Apr 26 12:40:19 192.168.122.209 [74170.018995] Rebooting in 1 seconds.. Apr 26 12:40:20 192.168.122.209 [74171.011556] ACPI MEMORY or I/O RESET_REG. Apr 26 12:40:44 192.168.122.209 [ 5.688736] shpchp 0000:07:00.0: pci_hp_register failed with error -16 Apr 26 12:40:44 192.168.122.209 [ 5.689360] shpchp 0000:07:00.0: Slot initialization failed